Unrelated upates (eg hardware support) are pushed to feisty-security

Bug #159717 reported by laga
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Invalid
Undecided
Unassigned
linux-source-2.6.15 (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I have enabled the feisty-security repository in order to receive security updates (as implied by the name). However, I had to find out the hard way that not only security updates are released, but also new hardware support and other unrelated additions. See https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/139767

Similar releases can be found in Dapper, eg 2.6.15-26.47 which was released to dapper-security. The changelog includes items like "sound/pci{,/emu10k1}: Miscellaneous cleanups" which doesn't seem security-related to me.

I'm not sure of a better way to handle updates. There could be a special security-fixes-only tree for <release>-security and a normal tree with other changes (including the security fixes of course) for <release>-updates. Of course, this creates more work for the developers :( I'm sure someone can come up with a better workflow (if my bug doesn't get rejected).
I just find it hardly acceptable that package releases tagged as "security" break drivers. Of course, it's just me complaining right now about a rather obscure piece of hardware breaking but I'd be surprised if other users haven't been caught by similar regression in the past.

Tags: lp-soyuz
Revision history for this message
Caroline Ford (secretlondon) wrote :

None of these are actual bugs on the kernel.

Changed in linux-source-2.6.15:
status: New → Invalid
Changed in linux-source-2.6.20:
status: New → Invalid
Revision history for this message
Caroline Ford (secretlondon) wrote :

Soyuz?

Revision history for this message
Julian Edwards (julian-edwards) wrote :

Not a Soyuz bug, it's really up to the package developers to only put the relevant fixes in -security.

Changed in soyuz:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.