Please review package naming and source hints
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
Please investigate the package naming, and naming relations between the linux and linux-meta source packages. There are a few behaviours I've observed in the last couple days that I found a little odd:
1) The descriptions for the "linux" and "linux-generic" meta-packages appear identical, except that the words "complete generic" and "generic complete" are interchanged. How is a user to determine which is appropriate for their system?
2) Running `apt-get source linux` oddly downloads the source for linux-meta, rather than the source for linux.
3) Downloading the source for linux does not provide a Vcs-* pointer to indicate that someone may be more interested in looking at the git repository if proposing changes to the package.
I suspect there are likely a few more little naming and packaging bits that would benefit from a review, and am not sure that any of these are in themselves a significant bug. Please feel free to close this bug after a review of namespaces, packaging, and the like, without regard for whether any of the specific issues raised are resolved.
Changed in linux: | |
assignee: | nobody → ubuntu-kernel-team |
importance: | Undecided → Low |
status: | New → Triaged |
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:
1) If you are comfortable installing packages on your own, the linux-image- 2.6.27- * package is currently available for you to install and test.
--or--
2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http:// www.ubuntu. com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.
Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.