I don't understand the SRU justification here for pixman and libdrm.
What does "breaking dist-upgrade" mean in this context? Why should
*not* SRUing these libraries result in any dist-upgrade breakage at all?
If these libraries are not needed to be SRUed again for enablement
purposes (as dependencies), then I don't believe we should be updating
them.
** Changed in: libdrm (Ubuntu Precise)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1253041
Title:
lts-saucy enablement in precise
Status in “libdrm” package in Ubuntu:
Invalid
Status in “mesa” package in Ubuntu:
Invalid
Status in “pixman” package in Ubuntu:
Invalid
Status in “libdrm” source package in Precise:
Incomplete
Status in “mesa” source package in Precise:
New
Status in “pixman” source package in Precise:
New
Status in “libdrm” source package in Quantal:
New
Status in “mesa” source package in Quantal:
Invalid
Status in “pixman” source package in Quantal:
New
Status in “libdrm” source package in Raring:
New
Status in “mesa” source package in Raring:
Invalid
Status in “pixman” source package in Raring:
New
Bug description:
Bug #1242633 only deals with the packages related to pointer barriers. More
packages need to be backported to enable building saucy xserver on precise:
- Pixman, should be copied to precise, quantal and raring, to not
deliberately break dist-upgrading too hard.
- libdrm, to precise, quantal and raring too, for same reason. Bug #1171340
shows why renaming is unfeasible.
Mesa in precise needs a small update to recognise -lts-saucy and lts-
trusty renamed packages.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1253041/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
