| Summary: | Thunderbird 45.7.1 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | David Walser <luigiwalser> |
| Component: | RPM Packages | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | davidwhodgins, mageia, nathan95, sysadmin-bugs |
| Version: | 5 | Keywords: | validated_update |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | advisory MGA5-64-OK MGA5-32-OK | ||
| Source RPM: | thunderbird | CVE: | |
| Status comment: | |||
|
Description
David Walser
2017-02-12 02:12:12 CET
I have committed it to SVN for Cauldron and Mageia 5 and asked for a freeze push. Suggested advisory: ======================== The updated packages fix a crash regression introduced in version 45.7.0. References: https://www.mozilla.org/en-US/thunderbird/45.7.1/releasenotes/ ======================== Updated packages in core/updates_testing: ======================== thunderbird-45.7.1-1.mga5 thunderbird-enigmail-45.7.1-1.mga5 thunderbird-ar-45.7.1-1.mga5 thunderbird-ast-45.7.1-1.mga5 thunderbird-be-45.7.1-1.mga5 thunderbird-bg-45.7.1-1.mga5 thunderbird-bn_BD-45.7.1-1.mga5 thunderbird-br-45.7.1-1.mga5 thunderbird-ca-45.7.1-1.mga5 thunderbird-cs-45.7.1-1.mga5 thunderbird-cy-45.7.1-1.mga5 thunderbird-da-45.7.1-1.mga5 thunderbird-de-45.7.1-1.mga5 thunderbird-el-45.7.1-1.mga5 thunderbird-en_GB-45.7.1-1.mga5 thunderbird-en_US-45.7.1-1.mga5 thunderbird-es_AR-45.7.1-1.mga5 thunderbird-es_ES-45.7.1-1.mga5 thunderbird-et-45.7.1-1.mga5 thunderbird-eu-45.7.1-1.mga5 thunderbird-fi-45.7.1-1.mga5 thunderbird-fr-45.7.1-1.mga5 thunderbird-fy_NL-45.7.1-1.mga5 thunderbird-ga_IE-45.7.1-1.mga5 thunderbird-gd-45.7.1-1.mga5 thunderbird-gl-45.7.1-1.mga5 thunderbird-he-45.7.1-1.mga5 thunderbird-hr-45.7.1-1.mga5 thunderbird-hsb-45.7.1-1.mga5 thunderbird-hu-45.7.1-1.mga5 thunderbird-hy_AM-45.7.1-1.mga5 thunderbird-id-45.7.1-1.mga5 thunderbird-is-45.7.1-1.mga5 thunderbird-it-45.7.1-1.mga5 thunderbird-ja-45.7.1-1.mga5 thunderbird-ko-45.7.1-1.mga5 thunderbird-lt-45.7.1-1.mga5 thunderbird-nb_NO-45.7.1-1.mga5 thunderbird-nl-45.7.1-1.mga5 thunderbird-nn_NO-45.7.1-1.mga5 thunderbird-pa_IN-45.7.1-1.mga5 thunderbird-pl-45.7.1-1.mga5 thunderbird-pt_BR-45.7.1-1.mga5 thunderbird-pt_PT-45.7.1-1.mga5 thunderbird-ro-45.7.1-1.mga5 thunderbird-ru-45.7.1-1.mga5 thunderbird-si-45.7.1-1.mga5 thunderbird-sk-45.7.1-1.mga5 thunderbird-sl-45.7.1-1.mga5 thunderbird-sq-45.7.1-1.mga5 thunderbird-sv_SE-45.7.1-1.mga5 thunderbird-ta_LK-45.7.1-1.mga5 thunderbird-tr-45.7.1-1.mga5 thunderbird-uk-45.7.1-1.mga5 thunderbird-vi-45.7.1-1.mga5 thunderbird-zh_CN-45.7.1-1.mga5 thunderbird-zh_TW-45.7.1-1.mga5 from SRPMS: thunderbird-45.7.1-1.mga5.src.rpm thunderbird-l10n-45.7.1-1.mga5.src.rpm Thanks to: http://www.linuxfromscratch.org/blfs/view/cvs/xsoft/firefox.html To fix the build in Cauldron: sed -e s/_EVENT_SIZEOF/EVENT__SIZEOF/ \ -i ipc/chromium/src/base/message_pump_libevent.cc
Nicolas Salguero
2017-02-15 09:32:58 CET
Status:
NEW =>
ASSIGNED Linux version 4.4.49-desktop-1.mga5 (iurt@ecosse.mageia.org) (gcc version 4.9.2 (GCC) ) #1 SMP Wed Feb 15 22:55:34 UTC 2017 Thunderbird: version 45.7.1-1.mga5 No regression noted the program works correctly mga5-64 CC:
(none) =>
nathan95 Thunderbird: version 45.7.1-1.mga5 No regression noted the program works correctly mga5-32
nathan giovannini
2017-02-18 12:29:37 CET
Whiteboard:
(none) =>
MGA5-64-OK MGA5-32-OK
nathan giovannini
2017-02-18 14:18:31 CET
Keywords:
(none) =>
validated_update
nathan giovannini
2017-02-18 14:39:01 CET
Whiteboard:
MGA5-64-OK MGA5-32-OK =>
advisory MGA5-64-OK MGA5-32-OK Hi, i do not see any advisory yet on the svn. Can someone please add one ? CC:
(none) =>
mageia (In reply to nathan giovannini from comment #4) > Thunderbird: version 45.7.1-1.mga5 > No regression noted the program works correctly > mga5-32 Nathan, I see from https://bugs.mageia.org/show_activity.cgi?id=20267 that you added the advisory whiteboard entry yesterday. That should not be done until the advisory has actually been added to svn. I've now added it ... http://svnweb.mageia.org/advisories/20267.adv?revision=5413&view=markup There are two parts to the advisory. The first, is in the bug report, comment 1 in this case. That's used by the qa team to know what needs to be tested, and to provide the information used to create the second part, the svn advisory. As shown by the above link, the advisory in svn has a very specific format. It's used the utilities that push updates from the updates testing repository to the updates repo, to select which srpm packages to include in the update, and to create the advisory that end users will see when viewing the update in rpmdrake. When the advisory whiteboard entry has been added, http://madb.mageia.org/tools/updates will show an asterisk after the bug number. It's the missing asterisk, that I or others adding the advisories to svn look for to know it needs to be done. In this case, I was notified of the need by being referred to comment 5 on irc. This is not intended as a lecture, and I'm glad you're taking initiative. I'm going through the details of how advisories work, both for you, and as I intend to refer to this comment in the next qa team irc meeting. I'll also review the wiki to see if it needs to be clarified. Been a while since I've looked at it. CC:
(none) =>
davidwhodgins (In reply to Dave Hodgins from comment #6) > (In reply to nathan giovannini from comment #4) > > Thunderbird: version 45.7.1-1.mga5 > > No regression noted the program works correctly > > mga5-32 > > Nathan, I see from https://bugs.mageia.org/show_activity.cgi?id=20267 that > you > added the advisory whiteboard entry yesterday. That should not be done until > the > advisory has actually been added to svn. I've now added it ... > http://svnweb.mageia.org/advisories/20267.adv?revision=5413&view=markup > > There are two parts to the advisory. The first, is in the bug report, > comment 1 > in this case. That's used by the qa team to know what needs to be tested, and > to provide the information used to create the second part, the svn advisory. > As shown by the above link, the advisory in svn has a very specific format. > It's > used the utilities that push updates from the updates testing repository to > the > updates repo, to select which srpm packages to include in the update, and to > create the advisory that end users will see when viewing the update in > rpmdrake. > > When the advisory whiteboard entry has been added, > http://madb.mageia.org/tools/updates will show an asterisk after the bug > number. It's the missing asterisk, that > I or others adding the advisories to svn look for to know it needs to be > done. > > In this case, I was notified of the need by being referred to comment 5 on > irc. > > This is not intended as a lecture, and I'm glad you're taking initiative. > I'm going through the details of how advisories work, both for you, and as I > intend to refer to this comment in the next qa team irc meeting. I'll also > review the wiki to see if it needs to be clarified. Been a while since I've > looked at it. OK I apologize for the mistake I won't be more careful next time:( An update for this issue has been pushed to the Mageia Updates repository. http://advisories.mageia.org/MGAA-2017-0006.html Status:
ASSIGNED =>
RESOLVED |