Thunderbird 38.7.2 has been released today (April 4): https://www.mozilla.org/en-US/thunderbird/38.7.2/releasenotes/ The release notes say the same thing as did 38.7.1. I don't know if they're incorrect/incomplete or if the change wasn't fully done correctly in the last update.
Status: NEW => ASSIGNEDCC: (none) => doktor5000
Pushed thunderbird-38.7.2-1.mga6 to cauldron, will push later today for mga5.
@David: Would be appreciated if you could help out with the advisory part as usual, thanks in advance :) Pushed thunderbird-38.7.2-1.mga5 and the -l10n packages to core/updates_testing, please test the following packages. i586 ================ thunderbird-38.7.2-1.mga5.i586 thunderbird-enigmail-38.7.2-1.mga5.i586 noarch ================ thunderbird-ar-38.7.2-1.mga5.noarch thunderbird-ast-38.7.2-1.mga5.noarch thunderbird-be-38.7.2-1.mga5.noarch thunderbird-bg-38.7.2-1.mga5.noarch thunderbird-bn_BD-38.7.2-1.mga5.noarch thunderbird-br-38.7.2-1.mga5.noarch thunderbird-ca-38.7.2-1.mga5.noarch thunderbird-cs-38.7.2-1.mga5.noarch thunderbird-cy-38.7.2-1.mga5.noarch thunderbird-da-38.7.2-1.mga5.noarch thunderbird-de-38.7.2-1.mga5.noarch thunderbird-el-38.7.2-1.mga5.noarch thunderbird-en_GB-38.7.2-1.mga5.noarch thunderbird-en_US-38.7.2-1.mga5.noarch thunderbird-es_AR-38.7.2-1.mga5.noarch thunderbird-es_ES-38.7.2-1.mga5.noarch thunderbird-et-38.7.2-1.mga5.noarch thunderbird-eu-38.7.2-1.mga5.noarch thunderbird-fi-38.7.2-1.mga5.noarch thunderbird-fr-38.7.2-1.mga5.noarch thunderbird-fy_NL-38.7.2-1.mga5.noarch thunderbird-ga_IE-38.7.2-1.mga5.noarch thunderbird-gd-38.7.2-1.mga5.noarch thunderbird-gl-38.7.2-1.mga5.noarch thunderbird-he-38.7.2-1.mga5.noarch thunderbird-hr-38.7.2-1.mga5.noarch thunderbird-hsb-38.7.2-1.mga5.noarch thunderbird-hu-38.7.2-1.mga5.noarch thunderbird-hy_AM-38.7.2-1.mga5.noarch thunderbird-id-38.7.2-1.mga5.noarch thunderbird-is-38.7.2-1.mga5.noarch thunderbird-it-38.7.2-1.mga5.noarch thunderbird-ja-38.7.2-1.mga5.noarch thunderbird-ko-38.7.2-1.mga5.noarch thunderbird-lt-38.7.2-1.mga5.noarch thunderbird-nb_NO-38.7.2-1.mga5.noarch thunderbird-nl-38.7.2-1.mga5.noarch thunderbird-nn_NO-38.7.2-1.mga5.noarch thunderbird-pa_IN-38.7.2-1.mga5.noarch thunderbird-pl-38.7.2-1.mga5.noarch thunderbird-pt_BR-38.7.2-1.mga5.noarch thunderbird-pt_PT-38.7.2-1.mga5.noarch thunderbird-ro-38.7.2-1.mga5.noarch thunderbird-ru-38.7.2-1.mga5.noarch thunderbird-si-38.7.2-1.mga5.noarch thunderbird-sk-38.7.2-1.mga5.noarch thunderbird-sl-38.7.2-1.mga5.noarch thunderbird-sq-38.7.2-1.mga5.noarch thunderbird-sv_SE-38.7.2-1.mga5.noarch thunderbird-ta_LK-38.7.2-1.mga5.noarch thunderbird-tr-38.7.2-1.mga5.noarch thunderbird-uk-38.7.2-1.mga5.noarch thunderbird-vi-38.7.2-1.mga5.noarch thunderbird-zh_CN-38.7.2-1.mga5.noarch thunderbird-zh_TW-38.7.2-1.mga5.noarch x86_64 ================ thunderbird-38.7.2-1.mga5.x86_64 thunderbird-enigmail-38.7.2-1.mga5.x86_64 src ================ thunderbird-38.7.2-1.mga5.src
Assignee: doktor5000 => qa-bugs
Advisory: ================ The thunderbird package has been updated to version 38.7.2, which fixes several bugs, including a potential crash in the handling of SSL certificates. References: https://www.mozilla.org/en-US/thunderbird/38.7.2/releasenotes/
Working fine on Mageia 5 i586.
Whiteboard: (none) => MGA5-32-OK
English version appears to work fine on Mageia 5 x86_64.
CC: (none) => andrewsfarmWhiteboard: MGA5-32-OK => MGA5-32-OK MGA5-64-OK
Validating. Advisory uploaded.
Keywords: (none) => validated_updateWhiteboard: MGA5-32-OK MGA5-64-OK => advisory MGA5-32-OK MGA5-64-OKCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. http://advisories.mageia.org/MGASA-2016-0139.html
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED
thunderbird-l10n srpm not listed so was missed from the advisory. Added now, please push as soon as possible. Thanks
thunderbird-l10n pushed
CC: (none) => tmb
Thanks Thomas :)
(In reply to claire robinson from comment #8) > thunderbird-l10n srpm not listed so was missed from the advisory. sorry :/ Need to check my scriptlet why it didn't list the other src.rpm, or I simply missed to copy the dang last line, didn't know that prevents to push the binary packages ... @Thomas: Is is intended like this, if only the src.rpm is not listed here or in the advisory, resulting in the respective binary packages not getting pushed?
It's a matter of what's listed in the advisory in SVN. Those are usually committed by QA team members based on what we packagers list here in the bug report. Packagers also have access to commit the advisory to SVN themselves.
Yes I'm aware, but what is the relation between listing the src.rpm and the binary packages? Binaries were listed, src.rpm forgotten, so there must be some automated check that does not upload binaries when their src.rpm is not listed? I'd just like to understand the relation.
Binaries are not listed in the SVN advisory, so there's nothing to check there. Those are only listed by packagers in the bug reports so that the QA team knows what actual packages to test.
(In reply to Florian Hubold from comment #13) > Yes I'm aware, but what is the relation between listing the src.rpm and the > binary packages? Binaries were listed, src.rpm forgotten, so there must be > some automated check that does not upload binaries when their src.rpm is not > listed? > > I'd just like to understand the relation. The upload / package move process only tracks srpms, and moves all packages built from the listed srpm(s) (that way we get all the packages including the debuginfo packages moved)