Activity log for bug #1171340

Date Who What changed Old value New value Message
2013-04-22 07:49:07 Maarten Lankhorst bug added bug
2013-04-22 07:49:29 Maarten Lankhorst bug task added libdrm (Ubuntu)
2013-04-22 07:49:35 Maarten Lankhorst bug task deleted mesa (Ubuntu)
2013-04-22 07:50:17 Maarten Lankhorst bug task added dh-exec (Ubuntu)
2013-04-22 07:50:27 Maarten Lankhorst bug task added llvm-3.2 (Ubuntu)
2013-04-22 07:50:36 Maarten Lankhorst nominated for series Ubuntu Precise
2013-04-22 07:50:36 Maarten Lankhorst bug task added libdrm (Ubuntu Precise)
2013-04-22 07:50:36 Maarten Lankhorst bug task added dh-exec (Ubuntu Precise)
2013-04-22 07:50:36 Maarten Lankhorst bug task added llvm-3.2 (Ubuntu Precise)
2013-04-22 07:50:48 Maarten Lankhorst dh-exec (Ubuntu): status New Invalid
2013-04-22 07:50:54 Maarten Lankhorst dh-exec (Ubuntu Precise): status New In Progress
2013-04-22 07:50:58 Maarten Lankhorst dh-exec (Ubuntu Precise): assignee Maarten Lankhorst (mlankhorst)
2013-04-22 07:51:01 Maarten Lankhorst libdrm (Ubuntu Precise): assignee Maarten Lankhorst (mlankhorst)
2013-04-22 07:51:03 Maarten Lankhorst llvm-3.2 (Ubuntu Precise): assignee Maarten Lankhorst (mlankhorst)
2013-04-22 07:51:09 Maarten Lankhorst llvm-3.2 (Ubuntu): status New Invalid
2013-04-22 07:51:12 Maarten Lankhorst libdrm (Ubuntu): status New Invalid
2013-04-22 07:51:16 Maarten Lankhorst libdrm (Ubuntu Precise): status New In Progress
2013-04-22 07:51:19 Maarten Lankhorst llvm-3.2 (Ubuntu Precise): status New In Progress
2013-04-22 07:51:24 Maarten Lankhorst llvm-3.2 (Ubuntu Precise): milestone ubuntu-12.04.3
2013-04-22 07:51:26 Maarten Lankhorst libdrm (Ubuntu Precise): milestone ubuntu-12.04.3
2013-04-22 07:51:29 Maarten Lankhorst dh-exec (Ubuntu Precise): milestone ubuntu-12.04.3
2013-04-22 08:51:05 Maarten Lankhorst description In order to land llvm-3.2, dh-exec needs to be upgraded to 0.4 or newer. dh-exec is a build helper, and should have no backwards compatability issues. llvm-3.2 will be a new package only to be used for mesa-lts-raring, so there is no regression potential for that. Updating libdrm will require more thought. While the API is stable and I haven't noticed any new bugs being introduced, I fear that bumping the version number to beyond what quantal provides will make upgrading to quantal harder. Unfortunately, I think this is the only solution. The ubuntu-x-swat/x-updates ppa was recommended to be enabled for steam, and was already providing a newer libdrm: https://launchpad.net/~ubuntu-x-swat/+archive/x-updates/+packages The only way out I see is removing libdrm from that ppa, pushing a newer libdrm version to precise, removing libdrm from that ppa, and make update-manager downgrade libdrm during an upgrade to quantal. [Impact] * libdrm versioning is a mess, and lying about the version will lead to all kinds of problems. * Changes between 2.4.39 in precise/quantal and 2.4.43: - some tiling changes for radeon SI and multisampled surfaces (SI support is not available on precise xserver, so this is harmless.) - Adding PCI ID's for newer chipsets on radeon. - Some fixes for intel, and adding support for newer chipsets. - A few small nouveau fixes, and adding support for selecting kepler engines - manpages no longer formatted with troff, using xml instead - adding support for freedreno (disabled in our package) - Exynos fixes (disabled too) - A small omap fix, which the pandaboard ppa already included. * Renaming libdrm hasn't worked correctly, it has been attempted before in LP #1086345 * Lying about version numbers will break, there is a version in x-updates ppa that's the same version as quantal, so doing an upload with a version that's lower than what's available in quantal will break for anyone that followed the steam install instructions. * libdrm-nouveau1a should be patched in again, and re-enabled for precise and quantal. - plymouth needs this on quantal and precise - precise xserver and mesa require this, too * [Test Case] * Testing should be performed on quantal, precise lts-quantal, and precise original stack, with intel, radeon and nouveau. * Plymouth should still work correctly on precise and quantal with all the 3 kinds of cards * system should boot correctly, xserver, compiz and opengl applications must still work. [Regression Potential] * I believe the regression potential is low, raring has been mostly on a stack similar to quantal for most of the release, with the bump to new mesa 9.1 only happening right before final freeze, so a lot of testing has already been done. * old nouveau abi has not been tested however, with the plymouth update finally using the 'dumb' kms api instead of nouveau/intel/radeon directly. * The core libdrm api hasn't been changed however, libdrm-nouveau1a was only using that subset. * So if something breaks, it's likely going to be in a form similar to #1086345 * It would be very unlikely to introduce new crashes in opengl applications, or xserver [Other Info] * Pending MRE. [Original bug report] In order to land llvm-3.2, dh-exec needs to be upgraded to 0.4 or newer. dh-exec is a build helper, and should have no backwards compatability issues. llvm-3.2 will be a new package only to be used for mesa-lts-raring, so there is no regression potential for that. Updating libdrm will require more thought. While the API is stable and I haven't noticed any new bugs being introduced, I fear that bumping the version number to beyond what quantal provides will make upgrading to quantal harder. Unfortunately, I think this is the only solution. The ubuntu-x-swat/x-updates ppa was recommended to be enabled for steam, and was already providing a newer libdrm: https://launchpad.net/~ubuntu-x-swat/+archive/x-updates/+packages The only way out I see is removing libdrm from that ppa, pushing a newer libdrm version to precise, removing libdrm from that ppa, and make update-manager downgrade libdrm during an upgrade to quantal.
2013-04-22 11:01:51 Maarten Lankhorst description [Impact] * libdrm versioning is a mess, and lying about the version will lead to all kinds of problems. * Changes between 2.4.39 in precise/quantal and 2.4.43: - some tiling changes for radeon SI and multisampled surfaces (SI support is not available on precise xserver, so this is harmless.) - Adding PCI ID's for newer chipsets on radeon. - Some fixes for intel, and adding support for newer chipsets. - A few small nouveau fixes, and adding support for selecting kepler engines - manpages no longer formatted with troff, using xml instead - adding support for freedreno (disabled in our package) - Exynos fixes (disabled too) - A small omap fix, which the pandaboard ppa already included. * Renaming libdrm hasn't worked correctly, it has been attempted before in LP #1086345 * Lying about version numbers will break, there is a version in x-updates ppa that's the same version as quantal, so doing an upload with a version that's lower than what's available in quantal will break for anyone that followed the steam install instructions. * libdrm-nouveau1a should be patched in again, and re-enabled for precise and quantal. - plymouth needs this on quantal and precise - precise xserver and mesa require this, too * [Test Case] * Testing should be performed on quantal, precise lts-quantal, and precise original stack, with intel, radeon and nouveau. * Plymouth should still work correctly on precise and quantal with all the 3 kinds of cards * system should boot correctly, xserver, compiz and opengl applications must still work. [Regression Potential] * I believe the regression potential is low, raring has been mostly on a stack similar to quantal for most of the release, with the bump to new mesa 9.1 only happening right before final freeze, so a lot of testing has already been done. * old nouveau abi has not been tested however, with the plymouth update finally using the 'dumb' kms api instead of nouveau/intel/radeon directly. * The core libdrm api hasn't been changed however, libdrm-nouveau1a was only using that subset. * So if something breaks, it's likely going to be in a form similar to #1086345 * It would be very unlikely to introduce new crashes in opengl applications, or xserver [Other Info] * Pending MRE. [Original bug report] In order to land llvm-3.2, dh-exec needs to be upgraded to 0.4 or newer. dh-exec is a build helper, and should have no backwards compatability issues. llvm-3.2 will be a new package only to be used for mesa-lts-raring, so there is no regression potential for that. Updating libdrm will require more thought. While the API is stable and I haven't noticed any new bugs being introduced, I fear that bumping the version number to beyond what quantal provides will make upgrading to quantal harder. Unfortunately, I think this is the only solution. The ubuntu-x-swat/x-updates ppa was recommended to be enabled for steam, and was already providing a newer libdrm: https://launchpad.net/~ubuntu-x-swat/+archive/x-updates/+packages The only way out I see is removing libdrm from that ppa, pushing a newer libdrm version to precise, removing libdrm from that ppa, and make update-manager downgrade libdrm during an upgrade to quantal. [Impact]  * libdrm versioning is a mess, and lying about the version will lead to all kinds of problems.  * Changes between 2.4.39 in precise/quantal and 2.4.43:    - some tiling changes for radeon SI and multisampled surfaces (SI support is not available on precise xserver, so this is harmless.)    - Adding PCI ID's for newer chipsets on radeon.    - Some fixes for intel, and adding support for newer chipsets.    - A few small nouveau fixes, and adding support for selecting kepler engines    - manpages no longer formatted with troff, using xml instead    - adding support for freedreno (disabled in our package)    - Exynos fixes (disabled too)    - A small omap fix, which the pandaboard ppa already included.  * Renaming libdrm hasn't worked correctly, it has been attempted before in LP #1086345  * Lying about version numbers will break, there is a version in x-updates ppa that's the same version as quantal, so doing an upload with a version that's lower than what's available in quantal will break for anyone that followed the steam install instructions.  * libdrm-nouveau1a should be patched in again, and re-enabled for precise and quantal.    - plymouth needs this on quantal and precise    - precise xserver and mesa require this, too [Test Case]  * Testing should be performed on quantal, precise lts-quantal, and precise original stack, with intel, radeon and nouveau.  * Plymouth should still work correctly on precise and quantal with all the 3 kinds of cards  * system should boot correctly, xserver, compiz and opengl applications must still work. [Regression Potential]  * I believe the regression potential is low, raring has been mostly on a stack similar to quantal for most of the release, with the bump to new mesa 9.1 only happening right  before final freeze, so a lot of testing has already been done.  * Old nouveau abi has not been tested however, with the plymouth update finally using the 'dumb' kms api instead of nouveau/intel/radeon directly.  * The core libdrm api hasn't been changed however, libdrm-nouveau1a was only using that subset.  * So if something breaks, it's likely going to be in a form similar to #1086345  * It would be very unlikely to introduce new crashes in opengl applications, or xserver [Other Info]  * Provisional MRE granted, for updating libdrm in quantal and precise to the raring version. [Original bug report] For the lts-raring backports stack libdrm needs to be backported to quantal and precise. While the API is stable and I haven't noticed any new bugs being introduced, I fear that bumping the version number to beyond what quantal provides will make upgrading to quantal harder. Unfortunately, I think this is the only solution. The ubuntu-x-swat/x-updates ppa was recommended to be enabled for steam, and was already providing a newer libdrm: https://launchpad.net/~ubuntu-x-swat/+archive/x-updates/+packages The only way out I see is removing libdrm from that ppa, pushing a newer libdrm version to precise, removing libdrm from that ppa, and make update-manager downgrade libdrm during an upgrade to quantal.
2013-04-22 11:02:02 Maarten Lankhorst bug task deleted llvm-3.2 (Ubuntu)
2013-04-22 11:02:05 Maarten Lankhorst bug task deleted dh-exec (Ubuntu)
2013-04-22 11:02:20 Maarten Lankhorst summary Please update dh-exec, llvm-3.2 and libdrm for lts-raring Please update libdrm for lts-raring
2013-04-22 11:04:28 Maarten Lankhorst bug task deleted dh-exec (Ubuntu Precise)
2013-04-22 11:04:34 Maarten Lankhorst bug task deleted llvm-3.2 (Ubuntu Precise)
2013-04-22 14:55:01 Adam Conrad nominated for series Ubuntu Quantal
2013-04-22 14:55:01 Adam Conrad bug task added libdrm (Ubuntu Quantal)
2013-04-22 14:55:44 Adam Conrad libdrm (Ubuntu Precise): status In Progress Fix Committed
2013-04-22 14:55:46 Adam Conrad bug added subscriber Ubuntu Stable Release Updates Team
2013-04-22 14:55:48 Adam Conrad bug added subscriber SRU Verification
2013-04-22 14:55:50 Adam Conrad tags verification-needed
2013-04-22 14:56:01 Adam Conrad libdrm (Ubuntu Quantal): status New Fix Committed
2013-04-22 14:56:48 Adam Conrad libdrm (Ubuntu Quantal): assignee Maarten Lankhorst (mlankhorst)
2013-04-22 15:23:56 Launchpad Janitor branch linked lp:ubuntu/precise-proposed/libdrm
2013-04-22 15:23:59 Launchpad Janitor branch linked lp:ubuntu/quantal-proposed/libdrm
2013-04-23 14:43:15 Maarten Lankhorst tags verification-needed verification-done
2013-05-04 15:45:35 madbiologist bug added subscriber madbiologist
2013-05-08 06:55:58 Chris Halse Rogers removed subscriber Ubuntu Stable Release Updates Team
2013-05-08 06:56:13 Launchpad Janitor libdrm (Ubuntu Quantal): status Fix Committed Fix Released
2013-05-08 06:58:15 Launchpad Janitor libdrm (Ubuntu Precise): status Fix Committed Fix Released
2013-05-08 07:09:21 Launchpad Janitor branch linked lp:ubuntu/precise-updates/libdrm