Thunderbird was upgraded on release 45 since few days. Is it possible to have this upgrade on rpm base please ?
(In reply to Sylvain HEMONET from comment #0) > Thunderbird was upgraded on release 45 since few days. Is it possible to > have this upgrade on rpm base please ? It'll take time, see https://ml.mageia.org/l/arc/dev/2016-04/msg00347.html
CC: (none) => marja11Component: New RPM package request => RPM PackagesAssignee: bugsquad => doktor5000
FWIW, thunderbird-45.0-1.mga6 and -l10n packages have been pushed already to cauldron, and tests on mga5 look fine too. Will try to look for the backported upstream patches that fedora has, and then push to mga5 too.
Status: NEW => ASSIGNEDCC: (none) => doktor5000
Blocks: (none) => 18264
Now that you got 45.0 to build, I see that 45.1.0 is available.
FWIW, the fedora patches for updating bundled harfbuzz and some others are only relevant for ppc arch, and some more for ggc6 which are not relevant for us yet. Will update to 45.1.0 and submit to QA.
Cool. Since we missed the 38.8 release of Thunderbird, I think once 45.1.1 lands, we can actually ship this. We'll let QA test 45.1.0 to make sure the transition to 45 is OK. https://mail.mozilla.org/pipermail/tb-planning/2016-May/004747.html
Submitted a new candidate to core/updates_testing, list of packages below: i586 ================ thunderbird-45.1.0-1.mga5.i586 thunderbird-enigmail-45.1.0-1.mga5.i586 x86_64 ================ thunderbird-45.1.0-1.mga5.x86_64 thunderbird-enigmail-45.1.0-1.mga5.x86_64 noarch ================ thunderbird-ar-45.1.0-1.mga5.noarch thunderbird-ast-45.1.0-1.mga5.noarch thunderbird-be-45.1.0-1.mga5.noarch thunderbird-bg-45.1.0-1.mga5.noarch thunderbird-bn_BD-45.1.0-1.mga5.noarch thunderbird-br-45.1.0-1.mga5.noarch thunderbird-ca-45.1.0-1.mga5.noarch thunderbird-cs-45.1.0-1.mga5.noarch thunderbird-cy-45.1.0-1.mga5.noarch thunderbird-da-45.1.0-1.mga5.noarch thunderbird-de-45.1.0-1.mga5.noarch thunderbird-el-45.1.0-1.mga5.noarch thunderbird-en_GB-45.1.0-1.mga5.noarch thunderbird-en_US-45.1.0-1.mga5.noarch thunderbird-es_AR-45.1.0-1.mga5.noarch thunderbird-es_ES-45.1.0-1.mga5.noarch thunderbird-et-45.1.0-1.mga5.noarch thunderbird-eu-45.1.0-1.mga5.noarch thunderbird-fi-45.1.0-1.mga5.noarch thunderbird-fr-45.1.0-1.mga5.noarch thunderbird-fy_NL-45.1.0-1.mga5.noarch thunderbird-ga_IE-45.1.0-1.mga5.noarch thunderbird-gd-45.1.0-1.mga5.noarch thunderbird-gl-45.1.0-1.mga5.noarch thunderbird-he-45.1.0-1.mga5.noarch thunderbird-hr-45.1.0-1.mga5.noarch thunderbird-hsb-45.1.0-1.mga5.noarch thunderbird-hu-45.1.0-1.mga5.noarch thunderbird-hy_AM-45.1.0-1.mga5.noarch thunderbird-id-45.1.0-1.mga5.noarch thunderbird-is-45.1.0-1.mga5.noarch thunderbird-it-45.1.0-1.mga5.noarch thunderbird-ja-45.1.0-1.mga5.noarch thunderbird-ko-45.1.0-1.mga5.noarch thunderbird-lt-45.1.0-1.mga5.noarch thunderbird-nb_NO-45.1.0-1.mga5.noarch thunderbird-nl-45.1.0-1.mga5.noarch thunderbird-nn_NO-45.1.0-1.mga5.noarch thunderbird-pa_IN-45.1.0-1.mga5.noarch thunderbird-pl-45.1.0-1.mga5.noarch thunderbird-pt_BR-45.1.0-1.mga5.noarch thunderbird-pt_PT-45.1.0-1.mga5.noarch thunderbird-ro-45.1.0-1.mga5.noarch thunderbird-ru-45.1.0-1.mga5.noarch thunderbird-si-45.1.0-1.mga5.noarch thunderbird-sk-45.1.0-1.mga5.noarch thunderbird-sl-45.1.0-1.mga5.noarch thunderbird-sq-45.1.0-1.mga5.noarch thunderbird-sv_SE-45.1.0-1.mga5.noarch thunderbird-ta_LK-45.1.0-1.mga5.noarch thunderbird-tr-45.1.0-1.mga5.noarch thunderbird-uk-45.1.0-1.mga5.noarch thunderbird-vi-45.1.0-1.mga5.noarch thunderbird-zh_CN-45.1.0-1.mga5.noarch thunderbird-zh_TW-45.1.0-1.mga5.noarch src ================ thunderbird-45.1.0-1.mga5.src thunderbird-l10n-45.1.0-1.mga5.src
Assignee: doktor5000 => qa-bugs
Version: Cauldron => 5
When we do ship 45.1.1, assuming they don't add any more security fixes in 45.1.1 vs. 45.1.0, we'll only be fixing one MFSA (two CVEs). So that's all we're missing by not shipping 38.8 right now. Also, for those interested, here's the release notes for 45.1.0: https://www.mozilla.org/en-US/thunderbird/45.1.0/releasenotes/ Security references: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2805 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2807 https://www.mozilla.org/en-US/security/advisories/mfsa2016-39/ https://rhn.redhat.com/errata/RHSA-2016-1041.html https://www.mozilla.org/en-US/security/known-vulnerabilities/thunderbird/
tested it x86_64 with -de package and everything works: enigmail updated as well (installed but not in use here). lightning and other manually installed add-ons will be automatically checked and updated at first start. Sending, receiving mails, syncing contacts and calender with owncloud is still working - no issues detected in two days of standard work... However while looking with urpmq -ayf thunderbird with activated testing sources I found some localizations are getting new names - Intended or not? eg: thunderbird-fy-31.7.0-1.mga5.noarch thunderbird-fy_NL-45.1.0-1.mga5.noarch thunderbird-ga-31.7.0-1.mga5.noarch thunderbird-ga_IE-45.1.0-1.mga5.noarch thunderbird-hy-31.7.0-1.mga5.noarch thunderbird-hy_AM-45.1.0-1.mga5.noarch
(In reply to Marc Lattemann from comment #8) > However while looking with urpmq -ayf thunderbird with activated testing > sources I found some localizations are getting new names - Intended or not? We only bump the version number and donwload new language .xpi's - that was an upstream change then.
See also http://svnweb.mageia.org/packages/updates/5/thunderbird-l10n/current/SPECS/thunderbird-l10n.spec?view=log for the recent changes.
Tested English version x86_64, updated Firefox at the same time. Thunderbird wanted to update Lightning from 4.0.5.2 to 4.7 upon first running it. I did, although I never use it, and it appears to be OK. The only reason I did that is someone in the discuss ml is having a problem with T-bird 38.7.x and Lightning 4.0.7.2. All appears OK with T-bird.
CC: (none) => andrewsfarm
updated Mageia-5-i586 thunderbird on real hardware to: thunderbird 45.1.0 1.mga5 i586 thunderbird-en_GB 45.1.0 1.mga5 noarch downloaded some mail from pop3 -ok, sent mail to pop3 -ok no other issues noted
CC: (none) => westelWhiteboard: (none) => Mga5 32 ok |
MGA5-32 on Acer D620 Xfce No installation issues. This laptop did not have thunderbird before. I added my gmail account to it and could send to and receive from my hotmail account on my main machine.
CC: (none) => herman.viaeneWhiteboard: Mga5 32 ok | => MGA5-32-OK
(In reply to Thomas Andrews from comment #11) > Tested English version x86_64, updated Firefox at the same time. > > Thunderbird wanted to update Lightning from 4.0.5.2 to 4.7 upon first > running it. I did, although I never use it, and it appears to be OK. The > only reason I did that is someone in the discuss ml is having a problem with > T-bird 38.7.x and Lightning 4.0.7.2. > > All appears OK with T-bird. Same strange behaviour here, as I thought that Lightning was embedded now...
CC: (none) => lists.jjorge
(In reply to José Jorge from comment #14) > (In reply to Thomas Andrews from comment #11) > > Tested English version x86_64, updated Firefox at the same time. > > > > Thunderbird wanted to update Lightning from 4.0.5.2 to 4.7 upon first > > running it. I did, although I never use it, and it appears to be OK. The > > only reason I did that is someone in the discuss ml is having a problem with > > T-bird 38.7.x and Lightning 4.0.7.2. > > > > All appears OK with T-bird. > > Same strange behaviour here, as I thought that Lightning was embedded now... Apparently, if you had an extension version of Lightning installed before it was embedded, it carried over through the updates and took precedence over the embedded version of Lightning. That is what happened to me. I never really noticed it, because after installing Lightning I decided I had no use for it, and ignored it thereafter. However, there appears to be a bug in Thunderbird 38.7, at least the one we provide, where the embedded version of Lightning can't be accessed. There is no tab for it in Preferences. This is what came up in the discuss ml. I tried removing a carried-over version of Lightning from T-bird on my secondary computer, and I saw that bug, too. But, when I updated that one to T-bird 45, Lightning 4.7 is included, and that one DOES have a preferences tab.
Whiteboard: MGA5-32-OK => MGA5-32-OK MGA-64-OK
(In reply to Thomas Andrews from comment #15) > (In reply to José Jorge from comment #14) > Apparently, if you had an extension version of Lightning installed before it > was embedded, it carried over through the updates and took precedence over > the embedded version of Lightning. That is what happened to me. I never > really noticed it, because after installing Lightning I decided I had no use > for it, and ignored it thereafter. > > However, there appears to be a bug in Thunderbird 38.7, at least the one we > provide, where the embedded version of Lightning can't be accessed. There is > no tab for it in Preferences. This is what came up in the discuss ml. There has been no such bug reported for the older version of lightning, and I definitely have the preferences tab with the older TB 38.7 and our packaged lightning version 4.0.7, so cannot reproduce. In any case, issues resulting from user using upstream addons instead of our packaged version cannot be fixed by us, that's the users responsibility then. And the user on discuss ML used the upstream addon for a few years, so this is not an issue resulting from our packaged version, and also nothing we can or should try to fix - if the user wants to use a specific version he wants, then we should not enforce an upgrade. In any case that's something that should be reported to upstream lightning developers, if at all. But that's all totally OT for this update request here.
(In reply to Florian Hubold from comment #16) > There has been no such bug reported for the older version of lightning, and > I definitely have the preferences tab with the older TB 38.7 and our > packaged lightning version 4.0.7, so cannot reproduce. > > In any case, issues resulting from user using upstream addons instead of our > packaged version cannot be fixed by us, that's the users responsibility then. > > And the user on discuss ML used the upstream addon for a few years, so this > is not an issue resulting from our packaged version, and also nothing we can > or should try to fix - if the user wants to use a specific version he wants, > then we should not enforce an upgrade. In any case that's something that > should be reported to upstream lightning developers, if at all. > > But that's all totally OT for this update request here. TOTALLY OT? I respectfully disagree. I agree that it's an upstream problem, one that we shouldn't attempt to repair, but I didn't think it was totally OT to bring it up. I was able to reproduce the problem, by removing an old version of Lightning that carried through the update, I assume in the user's already-existing .thunderbird directory. I have no idea how or when it got there - this .thunderbird directory has been carried through many, many updates. The embedded Lightning was still listed, but could not be accessed. However, the problem went away for my user after this update. The embedded Lightning is now accessible. Perhaps that's because I didn't have an older non-embedded version of Lightning in place at the time of the update, perhaps not, but that's only speculation on my part. The point is, it went away.
Thunderbird 45.1.1 is out: https://www.mozilla.org/en-US/thunderbird/45.1.1/releasenotes/ Let's make a new bug for that when it's packaged and I'll make an advisory.
45.1.1 updated by tmb in Cauldron, now we just need it for Mageia 5. Firefox 45.2 should be out next Tuesday, so we should be able to get both of those updated soon.
CC: (none) => tmb
Thanks everyone. Thunderbird update moved to Bug 18616 for actual release.
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED