| 2008-04-22 21:05:55 |
Conn O Griofa |
bug |
|
|
added bug |
| 2008-05-06 01:46:09 |
Conn O Griofa |
linux-meta: status |
New |
Fix Released |
|
| 2008-12-20 13:24:45 |
Bogdan Butnaru |
linux-meta: status |
Fix Released |
Confirmed |
|
| 2008-12-20 13:24:45 |
Bogdan Butnaru |
linux-meta: statusexplanation |
Fixed in linux-meta 2.6.24.17.19 |
Still happening on Intrepid. |
|
| 2008-12-20 13:25:03 |
Bogdan Butnaru |
title |
linux-restricted-modules-server metapackage not present in repository |
[intrepid] linux-restricted-modules-server metapackage not present in repository |
|
| 2008-12-20 13:26:21 |
Bogdan Butnaru |
description |
System: Hardy x86 (fresh install from RC, latest updates & using main repository)
Test case:
install -server kernel via: sudo apt-get install linux-server
Expected results:
All necessary packages are installed, including linux-restricted-modules-server and the actual restricted modules package, linux-restricted-modules-2.6.24-16-server.
Actual results:
The linux-restricted-modules-server metapackage does not exist in the repository, and thus linux-restricted-modules-2.6.24-16-server will not get installed.
Note: my system uses the nvidia driver via nvidia-glx-new which requires restricted modules, and so the -server kernel will boot to the failsafe X configuration, unless I remember to manually install linux-restricted-modules-2.6.24-16-server. |
Edit: This is still happening in Intrepid (in my case, up-to-date Intrepid x86_64). I'm leaving the description below for history.
===
System: Hardy x86 (fresh install from RC, latest updates & using main repository)
Test case:
install -server kernel via: sudo apt-get install linux-server
Expected results:
All necessary packages are installed, including linux-restricted-modules-server and the actual restricted modules package, linux-restricted-modules-2.6.24-16-server.
Actual results:
The linux-restricted-modules-server metapackage does not exist in the repository, and thus linux-restricted-modules-2.6.24-16-server will not get installed.
Note: my system uses the nvidia driver via nvidia-glx-new which requires restricted modules, and so the -server kernel will boot to the failsafe X configuration, unless I remember to manually install linux-restricted-modules-2.6.24-16-server. |
|
| 2009-03-11 17:19:54 |
Stefan Bader |
linux-meta: assignee |
|
stefan-bader-canonical |
|
| 2009-03-11 17:19:54 |
Stefan Bader |
linux-meta: statusexplanation |
Still happening on Intrepid. |
Not sure how this is an issue with Intrepid. The only drivers still in restricted are wireless drivers and ltmodem. The binary gfx drivers are in separate DKMS package which will get rebuild when a new kernel is installed. |
|
| 2009-04-05 23:48:37 |
Stefan Bader |
nominated for series |
|
Ubuntu Intrepid |
|
| 2009-04-05 23:52:51 |
Stefan Bader |
description |
Edit: This is still happening in Intrepid (in my case, up-to-date Intrepid x86_64). I'm leaving the description below for history.
===
System: Hardy x86 (fresh install from RC, latest updates & using main repository)
Test case:
install -server kernel via: sudo apt-get install linux-server
Expected results:
All necessary packages are installed, including linux-restricted-modules-server and the actual restricted modules package, linux-restricted-modules-2.6.24-16-server.
Actual results:
The linux-restricted-modules-server metapackage does not exist in the repository, and thus linux-restricted-modules-2.6.24-16-server will not get installed.
Note: my system uses the nvidia driver via nvidia-glx-new which requires restricted modules, and so the -server kernel will boot to the failsafe X configuration, unless I remember to manually install linux-restricted-modules-2.6.24-16-server. |
SRU justification:
Impact: Missing dependency causes lrm not to be upgraded when the Linux server image is ABI bumped. Since Intrepid this won't affect the binary gfx drivers but some wireless modules still provided through lrm.
Fix: Simple addition to the meta-package to include the missing dependency
---
Edit: This is still happening in Intrepid (in my case, up-to-date Intrepid x86_64). I'm leaving the description below for history.
===
System: Hardy x86 (fresh install from RC, latest updates & using main repository)
Test case:
install -server kernel via: sudo apt-get install linux-server
Expected results:
All necessary packages are installed, including linux-restricted-modules-server and the actual restricted modules package, linux-restricted-modules-2.6.24-16-server.
Actual results:
The linux-restricted-modules-server metapackage does not exist in the repository, and thus linux-restricted-modules-2.6.24-16-server will not get installed.
Note: my system uses the nvidia driver via nvidia-glx-new which requires restricted modules, and so the -server kernel will boot to the failsafe X configuration, unless I remember to manually install linux-restricted-modules-2.6.24-16-server. |
|
| 2009-04-05 23:53:29 |
Stefan Bader |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2009-04-15 15:05:49 |
Martin Pitt |
bug task added |
|
linux-meta (Ubuntu Intrepid) |
|
| 2009-04-15 15:07:18 |
Martin Pitt |
bug task added |
|
linux-meta (Ubuntu Jaunty) |
|
| 2009-04-15 15:07:45 |
Martin Pitt |
linux-meta (Ubuntu Jaunty): status |
Confirmed |
Triaged |
|
| 2009-04-15 15:08:53 |
Martin Pitt |
linux-meta (Ubuntu Intrepid): status |
New |
Fix Committed |
|
| 2009-04-15 15:09:03 |
Martin Pitt |
tags |
|
verification-needed |
|
| 2009-04-15 16:34:31 |
Stefan Bader |
linux-meta (Ubuntu Jaunty): status |
Triaged |
Fix Committed |
|
| 2009-04-16 08:34:48 |
Nexus |
removed subscriber Nexus |
|
|
|
| 2009-04-17 15:27:05 |
Colin Watson |
linux-meta (Ubuntu Jaunty): status |
Fix Committed |
Fix Released |
|
| 2009-05-12 16:19:27 |
Launchpad Janitor |
linux-meta (Ubuntu Intrepid): status |
Fix Committed |
Fix Released |
|
| 2009-07-03 01:58:18 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-branches/ubuntu/intrepid/linux-meta/intrepid-proposed |
|
