Also, thanks to Florian Hubold for packaging this.

CC: (none) => doktor5000

FWIW, I'm already using thunderbird 31.1.0 since a few days without issues. If you notice anything, please consolidate it and let me know.

I didn't saw this mail before updating (yesterday ?), but:

it's only me or firefox-l10n provide old lang file from firefox 28 instead of the 31 one ?

(In reply to Manuel Hiebel from comment #3)
> it's only me or firefox-l10n provide old lang file from firefox 28 instead
> of the 31 one ?

Good catch, this is (again) due to https://bugs.mageia.org/show_bug.cgi?id=2868
Uploaded the changed files again manually:

[doktor5000@Mageia4 firefox-l10n]$ mgarepo upload SOURCES/*.xpi
User doktor5000 uploaded file f8353da0494fc8c0f16c62d7ff06db1e287b1e5a: ach.xpi
User doktor5000 uploaded file 7f544e2cd0717b8419e8fec6fd290b0ada8ffae4: an.xpi
User doktor5000 uploaded file 9899a86dd006ee23d50808b26ec5438fe7484dc2: en-US.xpi
User doktor5000 uploaded file 72133ed7a70413335783b251b42a697340c6fcfc: es-AR.xpi
User doktor5000 uploaded file 3a1c4b19ad7e53080f42f57ff2f3dc81d7add4b3: hsb.xpi
User doktor5000 uploaded file 4d0f41c90a5d9ecc8889246e2e0e34abe289e15c: id.xpi
User doktor5000 uploaded file 7450ebdc7b5b9e6ccd5c63254086f95cddf4fe34: ku.xpi
User doktor5000 uploaded file 2fbdde0eb957f5cfd8b553527103993f53ade80a: ms.xpi
User doktor5000 uploaded file 185ca040d352f0f0c11b0d45deb81969af06a238: rm.xpi
User doktor5000 uploaded file 1e7b5d1673e8be1e276e9dcda65a5880fb149cfb: son.xpi
User doktor5000 uploaded file 4893638a747213e259319eb427697b99a6a7c6cc: xh.xpi

The others did not change, it seems ...

Just submitted firefox-l10n-31.1.0-2.mga4

Just installed, but we'll need a lightning update as well.

CC: (none) => wrw105

Tested on Mageia 4 64-bits. Everything works as before up to now.

CC: (none) => olivier.delaune

I was speaking about firefox. I di not tested Thunderbird.

(In reply to Bill Wilkinson from comment #5)
> Just installed, but we'll need a lightning update as well.

Indeed, it needs to be updated to 3.3.

CC: (none) => mageia

(In reply to Bill Wilkinson from comment #5)
> Just installed, but we'll need a lightning update as well.

If you cannot wait install it from thunderbird addons.
https://addons.mozilla.org/en/thunderbird/addon/lightning/

CC: (none) => ozkyster

Regarding firefox, don't forget to test with a new profile too, check that the first page is ok, etc.

CC: (none) => stormi

(In reply to David Walser from comment #8)
> (In reply to Bill Wilkinson from comment #5)
> > Just installed, but we'll need a lightning update as well.
> 
> Indeed, it needs to be updated to 3.3.

Just sent thunderbird-lightning-3.3-1.mga4 to mga4 updates_testing, may take a few hours to make it through the buildsystem.

Tested mga4-64 with the usual battery: 
TB: send/receive/move/delete over IMAP/SMTP, lightning add calendar change an entry, joined IRC and had a chat on #mageia-qa

ff:
acid3, sunspider, javatester, youtube, heavy usage of tabs under general surfing, all behaving normally.

Just for the record (I doubt anything can be done about it):

FF: there are some leftovers from old language packs (must have been included in some firefox-*-24.5.0 packages)

Sesotho sa lebowa Language Pack 24.5.0 and 
Tamil (Sri Lanka) Language Pack 24.5.0 

are disabled after updating all FF-* packages from 24.8.0-1 to 31.1.0-2, because they are no longer compatible

CC: (none) => marja11

Tested mga4_64,

Testing complete for the new firefox-31.1.0-1.mga4, for me it's Ok and nothing to report.
All seems to work properly.

firefox-31.1.0-1.mga4
firefox-fr-31.1.0-2.mga4

CC: (none) => geiger.david68210

Florian, since we have some successful testing here, would you mind also packaging these for Mageia 3?

(In reply to David Walser from comment #15)
> Florian, since we have some successful testing here, would you mind also
> packaging these for Mageia 3?

No I don't mind, but not before next week when I'm on vacation.

Tested firefox-31.1.0-1 on mga4_64.

Everything seems to be working as expected. Browsed to a few different test sites like http://html5test.com and http://peacekeeper.futuremark.com as well as a list of sites I commonly use, all without any issues.

CC: (none) => dpremy

31.1.0-? was crashing in a few seconds on mga5a2_64 but 31.1.0-5 seems stable after browsing several sites for 30 minutes or more and opening several tabs from sync list.

CC: (none) => petel123123

Pete, this bug is only about the Mageia 4 build right now.  For Cauldron, IINM, Florian got it to build with gcc, which should have solved the crashing.

(In reply to David Walser from comment #19)
> For Cauldron, IINM, Florian got it to build with gcc, which should have solved
> the crashing.

Exactly. That was tracked in https://bugs.mageia.org/show_bug.cgi?id=14062 and the current version in core/release is firefox-31.1.0-6.mga5


_note to self_: enable webRTC for mga4 build and backport 31.1.0 to mga3

Status: NEW => ASSIGNED
Assignee: qa-bugs => doktor5000

@QA: FWIW, seems nobody noticed yet that the KDE integration has been disabled, as firefox doesn't build anymore with the patches enabled. This is still not fixed in cauldron, and the same applies for mga4 and mga3 ...

So currently you get the default GTK filepicker instead of the KDE one, and also no more plasma notifications (download progress and such).

(In reply to Florian Hubold from comment #20)
> (In reply to David Walser from comment #19)
> > For Cauldron, IINM, Florian got it to build with gcc, which should have solved
> > the crashing.
> 
> Exactly. That was tracked in https://bugs.mageia.org/show_bug.cgi?id=14062
> and the current version in core/release is firefox-31.1.0-6.mga5
> 
> 
> _note to self_: enable webRTC for mga4 build and backport 31.1.0 to mga3

I saw you mention it on IRC, but FF is now at 31.1.1 and TB is now at 31.1.2.  It's not the most critical thing, as there's no changes between FF 31.1.0 and FF 31.1.1 and between TB 31.1.1 and TB 31.1.2, but I think there were some bugfixes between TB 31.1.0 and TB 31.1.1.  Why were there no changes in the latest update?  Because the changes were only in the bundled nss, and we build against the system one.

BTW, before your next Mageia 3 and Mageia 4 builds would probably be a good time to update libpng and sqlite3 the rest of the way.

First things first :)
As you suggested, pushed libpng and sqlite3:
libpng-1.6.12-1.1.mga4
sqlite3-3.8.6-1.mga4

In the meantime, I'll work on FF/TB 31.1 for mga3, and when sqlite3 and libpng are through, I'll push another build of FF 31.1 for mga4 which reenables the KDE integration.

@qa: FWIW, I've added a short section in your updates procedure about firefox and the KDE integration which I've mentioned, so you know what I'm talking about :)
https://wiki.mageia.org/en/Updates_Firefox#KDE_integration_patches

(In reply to Florian Hubold from comment #24)
> @qa: FWIW, I've added a short section in your updates procedure about
> firefox and the KDE integration which I've mentioned, so you know what I'm
> talking about :)
> https://wiki.mageia.org/en/Updates_Firefox#KDE_integration_patches

Haha, the top half of that page is totally invalid info now.  I guess I should rewrite it someday.

Instead of breaking the mga3 distro by pushing new sqlite3 and libpng you could instead make FF/TB build with its bundled copies.

sqlite3 3.8.6 in mga3 updates_testing is currently blocking https://bugs.mageia.org/show_bug.cgi?id=14177

CC: (none) => oe

(In reply to Oden Eriksson from comment #26)
> Instead of breaking the mga3 distro by pushing new sqlite3 and libpng you
> could instead make FF/TB build with its bundled copies.
> 
> sqlite3 3.8.6 in mga3 updates_testing is currently blocking
> https://bugs.mageia.org/show_bug.cgi?id=14177

We could, but that's not how we've done it before.  I know this is a bit of an annoyance right now because of the build conflicts, but other than that I don't know of a real strong reason to build it bundled.  Once the FF/TB 31.2 update is pushed, it shouldn't cause any issues.

(In reply to Oden Eriksson from comment #26)
> Instead of breaking the mga3 distro by pushing new sqlite3 and libpng you
> could instead make FF/TB build with its bundled copies.

That's why I've asked David before if we really want such version upgrades, as IIRC we did use bundled versions in the past in some similar cases. E.g. for the switch to TB 10.x in mga1 we had to use bundled libpng and libxul ...

I don't know about libpng, but I do remember that we've upgraded sqlite3 in the past.

Okay, I've pushed a fixed libpng16 to updates_testing for mga3, see http://svnweb.mageia.org/packages?view=revision&revision=733689

- For mga4, ff and tb 31.1 should be complete and have already been built.

- For mga3, I'just pushed firefox after new sqlite3 has been built, and need to see if anything else needs updating (libvpx ...). And then I'll do thunderbird for mga3.

Thanks Florian.

I noticed some other minor issues.  The libpng16 in mga3 still says "Name: libpng" in the SPEC, and the filename is still libpng.spec.  Those should both be renamed to libpng16.  Also, the Provides: png-devel should be removed.  Then, the Firefox spec should have BuildRequires: libpng16-devel >= 2:1.6 instead of libpng-devel.

Also, I just wanted to double-check and be sure that the enigmail updates for TB are commited to SVN, as well as the changes you were going to make for WebRTC (in both Mageia 3 and Mageia 4 SVN).  Basically, such that the 31.2 update won't require anything else other than updating to 31.2.

Thanks again for your work on this.

webRTC - check :)
enigmail - check :)

For libpng, I'll have a look again. For name: libpng, isn't that renaming? Also, why remove png-devel as provide? I've already bumped the buildrequires in firefox to >= 1.6.10. Different name is not required there, but if you like that I'd propose pkgconfig(png16) >= 1.6

The idea is not to replace the current libpng, that's why it's called libpng16 in SVN.  Other packages shouldn't pull it in as a BR unless they explicitly request it.  As for how you write that BR, if you want to use pkgconfig (which is only technically correct if the package uses pkg-config to locate the lib), it would be pkgconfig(libpng16) I believe.

Tested on Mageia4 X86_64.

Thunderbird and Firefox running for a few hours now (continuously) no bug detected till now.

I just noticed a slightly increase of memory and RAM consumption compared to FF24. Nothing important.

CC: (none) => christophe

FYI: With iceape I use the mga3 libpng 1.5.x. The libpng version in mozilla's configure.in appears to be the version of the bundled libpng, not really a requirement.

CC: (none) => cjw

If all goes well, firefox-31.2.0-1.mga4 should be available soon on mirrors, including firefox-l10n-31.2.0-1.mga4. Feel free to test already, now we have to switch to 31 soon.

Will also push for mga3 once initial tests are OK.

I start to testing it and changed summary to 31.2.

Summary: Firefox and Thunderbird 31.1 => Firefox and Thunderbird 31.2

Thanks Christiaan.  We'll have to do that for Firefox as well, because this libpng16 thing is just not working.  Maybe some of the other BRs are built against libpng15 so they still want to pull that one in.

I'm closing this bug as its only purpose was preliminary 31.1 testing (which unfortunately we never got to for mga3).  I'll open a new bug for 31.2.

Status: ASSIGNED => RESOLVED
Resolution: (none) => OLD
Summary: Firefox and Thunderbird 31.2 => Firefox and Thunderbird 31.1