Re: Disabling whoopsie by default in the 12.04.1 release
Le 13/08/2012 17:20, Evan Dandrea a écrit : In the most common problems table: - If a linked bug report is marked as completed, the entire row will be greyed out (but still clickable). - If there is no linked bug report or the linked bug report is not marked as completed, but the version in Last seen column is *not* the most recent, just the Last seen column will be greyed out. This implies that because we have not seen a newer version with the problem, it is no longer present. - If the linked bug is marked as completed, but the Last seen column contains the most recent published version of the package, the Last seen column will be marked red. This is to indicate a *possible* regression. I'm still playing with this. Because Invalid bugs are also interpreted as complete, and because we only consider a bug complete when all of its bug tasks are complete, this is currently wrong in a few places. I was more interested in seeing how it presented, however. Hey Evan, Those are excellent news, the improvements make a real difference to the side usability, we finally can easily sort out what issues on the main page got addressed and those that still need work! Thanks, Sebastien Bacher -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Disabling whoopsie by default in the 12.04.1 release
Le 13/08/2012 17:20, Evan Dandrea a écrit : - If the linked bug is marked as completed, but the Last seen column contains the most recent published version of the package, the Last seen column will be marked red. This is to indicate a *possible* regression. I'm still playing with this. Because Invalid bugs are also interpreted as complete, and because we only consider a bug complete when all of its bug tasks are complete, this is currently wrong in a few places. I was more interested in seeing how it presented, however. There seems to be a bug in that code, takes sessioninstaller: https://launchpad.net/bugs/848605 - the issue got fixed in 0.20+bzr128-0ubuntu1.1 - precise-updates has that version, same for quantal - the last seen column has 0.20+bzr128-0ubuntu1, the detailled report page confirms that but it's marked in red? Cheers, Sebastien Bacher -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
New component-mismatches for source universe - main
The following universe packages have new reverse dependencies in main or got seeded. They need to get a MainInclusionReport and be promoted, or the reverse dependencies in main need to be dropped: o google-perftools: libgoogle-perftools-dev libgoogle-perftools4 libgoogle-perftools4-dbg libtcmalloc-minimal4 libtcmalloc-minimal4-dbg MIR: #1017972 (Fix Committed) [Reverse-Depends: Rescued from google-perftools, libgoogle-perftools-dev, libgoogle-perftools4] [Reverse-Build-Depends: ceph (MAIN)] o libunwind: libunwind-setjmp0 libunwind-setjmp0-dev libunwind8 libunwind8-dev MIR: #1017972 (Fix Committed) [Reverse-Depends: Rescued from libunwind, libunwind-setjmp0-dev, libunwind8-dev] [Reverse-Build-Depends: google-perftools] Please see http://people.canonical.com/~ubuntu-archive/component-mismatches.txt for the full report. Please contact https://launchpad.net/~ubuntu-archive for problems with this notification. -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
