| 2010-09-08 19:08:10 |
RussianNeuroMancer |
bug |
|
|
added bug |
| 2010-09-08 19:10:45 |
RussianNeuroMancer |
bug task added |
|
apt |
|
| 2010-09-08 19:10:58 |
RussianNeuroMancer |
tags |
|
maverick |
|
| 2010-09-16 23:07:55 |
Jeremy Foshee |
tags |
maverick |
maverick needs-kernel-logs |
|
| 2010-09-16 23:08:00 |
Jeremy Foshee |
tags |
maverick needs-kernel-logs |
maverick needs-kernel-logs needs-upstream-testing |
|
| 2010-09-16 23:08:03 |
Jeremy Foshee |
tags |
maverick needs-kernel-logs needs-upstream-testing |
kj-triage maverick needs-kernel-logs needs-upstream-testing |
|
| 2010-09-16 23:08:08 |
Jeremy Foshee |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2010-09-16 23:52:39 |
RussianNeuroMancer |
description |
Binary package hint: linux-headers-2.6.35-20
After latest kernel update (2.6.35-20) installed only updated kernel image, but header packages is still 2.6.35-19.
Now I have:
linux-headers-2.6.35-19
linux-headers-2.6.35-19-generic
linux-image-2.6.35-19-generic
linux-image-2.6.35-20-generic
But, if I understand situation right, this two packages must be installed too:
linux-headers-2.6.35-20
linux-headers-2.6.35-20-generic
There is apt bug, or something missed in 2.6.35-20 header packages description what not allow to install this packages automatically while kernel update? |
Typical user do this:
1. Install Lucid release or Maverick Beta.
2. Update. New headers will be download and installed without problems, as expected.
But Launchpad users sometimes do this, because developers and contributors ask test upstream kernel:
1. Install Lucid release or Maverick Beta.
2. Install upstream kernel from this link: https://wiki.ubuntu.com/KernelMainlineBuilds
3. Do something with upstream kernel - check some bug for example.
4. So, after that upstream kernel not no need anymore (and its' not comfortably - it' not updated automatically) and user remove it.
5. Try update after that - headers of new kernel, what available in repositories, not installed automatically. It's a big problem for all, who user additional kernel modules (VirtualBox modules, proprietary video driver modules, etc.), because after kernel update without headers update system can not boot.
I conclude there is problem no problem with APT or Linux, but problem with testing of upstream kernel process (Installing/Uninstalling) for Launchpad users.
Xorg team already have PPA and ppa-purge for testing fresh X.org and FOSS drivers. Maybe need create something similar for upstream kernel testing process? |
|
| 2010-09-16 23:52:46 |
RussianNeuroMancer |
linux (Ubuntu): status |
Incomplete |
New |
|
| 2010-09-16 23:53:22 |
RussianNeuroMancer |
tags |
kj-triage maverick needs-kernel-logs needs-upstream-testing |
kj-triage |
|
| 2010-09-16 23:56:11 |
RussianNeuroMancer |
description |
Typical user do this:
1. Install Lucid release or Maverick Beta.
2. Update. New headers will be download and installed without problems, as expected.
But Launchpad users sometimes do this, because developers and contributors ask test upstream kernel:
1. Install Lucid release or Maverick Beta.
2. Install upstream kernel from this link: https://wiki.ubuntu.com/KernelMainlineBuilds
3. Do something with upstream kernel - check some bug for example.
4. So, after that upstream kernel not no need anymore (and its' not comfortably - it' not updated automatically) and user remove it.
5. Try update after that - headers of new kernel, what available in repositories, not installed automatically. It's a big problem for all, who user additional kernel modules (VirtualBox modules, proprietary video driver modules, etc.), because after kernel update without headers update system can not boot.
I conclude there is problem no problem with APT or Linux, but problem with testing of upstream kernel process (Installing/Uninstalling) for Launchpad users.
Xorg team already have PPA and ppa-purge for testing fresh X.org and FOSS drivers. Maybe need create something similar for upstream kernel testing process? |
Typical user do this:
1. Install Lucid release or Maverick Beta.
2. Update. New headers will be downloaded and installed without problems, as expected.
But Launchpad users sometimes do this, because developers and contributors ask test upstream kernel:
1. Install Lucid release or Maverick Beta.
2. Install upstream kernel from this link: https://wiki.ubuntu.com/KernelMainlineBuilds
3. Do something with upstream kernel - check some bug for example.
4. So, after that upstream kernel not no need anymore (and its' not comfortably - it' not updated automatically) - user remove it.
5. Try update after that - headers of new kernel, what available in repositories, not installed automatically. It's a big problem for all, who use additional kernel modules (VirtualBox modules, proprietary video driver modules, etc.), because after kernel update without headers update system can not run graphical mode or work incorrect (VirtualBox can not run virtual machines).
I conclude there is no problem with APT or Linux, but problem with testing of upstream kernel process (Installing/Uninstalling) for Launchpad users.
Xorg team already have PPA and ppa-purge for testing fresh X.org and FOSS drivers. Maybe need create something similar for upstream kernel testing process?
|
|
| 2010-09-17 05:17:05 |
RussianNeuroMancer |
summary |
2.6.35-20 headers not installed automatically with 2.6.35-20 kernel image |
Header files of new builds of the Kernel not installed automatically while update after install and remove packages with upstream kernel from kernel-ppa |
|
| 2010-11-03 18:07:42 |
Christian Stöveken |
bug |
|
|
added subscriber Christian Stöveken |
| 2011-09-17 17:14:26 |
Brad Figg |
linux (Ubuntu): status |
New |
Incomplete |
|
