can't update from kernel 2.6.28.12.16 to 2.6.28.13.17

Bug #384447 reported by Sergey
36
This bug affects 6 people
Affects Status Importance Assigned to Milestone
linux-meta (Ubuntu)
Fix Released
Undecided
Andy Whitcroft

Bug Description

Binary package hint: linux-image-generic

I can't update from kernel 2.6.28.12.16 to 2.6.28.13.17 :
http://img194.imageshack.us/img194/6074/83601345.png

Revision history for this message
Technowizard (technowizard) wrote :

I have the same problem with my Kubuntu 9.04.

Revision history for this message
Ernst (ernst-blaauw) wrote :

I'm also affected. ;sudo aptitude safe-upgrade -v -V' gives me:

The following packages are BROKEN:
  linux-backports-modules-jaunty-generic [2.6.28.12.16 -> 2.6.28.13.17] linux-headers-generic [2.6.28.12.16 -> 2.6.28.13.17]
  linux-image-generic [2.6.28.12.16 -> 2.6.28.13.17] linux-restricted-modules-generic [2.6.28.12.16 -> 2.6.28.13.17]
The following packages will be upgraded:
  linux-backports-modules-jaunty [2.6.28.12.16 -> 2.6.28.13.17]
5 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 17.4kB of archives. After unpacking 0B will be used.
The following packages have unmet dependencies:
  linux-headers-generic: Depends: linux-headers-2.6.28-13-generic which is a virtual package.
  linux-image-generic: Depends: linux-image-2.6.28-13-generic which is a virtual package.
  linux-backports-modules-jaunty-generic: Depends: linux-backports-modules-2.6.28-13-generic which is a virtual package.
  linux-restricted-modules-generic: Depends: linux-restricted-modules-2.6.28-13-generic which is a virtual package.
Unable to resolve dependencies for the upgrade (no solution found).The following packages have been kept back:
  linux-backports-modules-jaunty linux-backports-modules-jaunty-generic linux-headers-generic linux-image-generic linux-restricted-modules-generic

Revision history for this message
Erwin Junge (erwin-junge) wrote :

I am also affected, Jaunty 64bit. sudo aptitude safe-upgrade -v -V output:

The following packages are BROKEN:
  linux-headers-generic [2.6.28.12.16 -> 2.6.28.13.17]
  linux-image-generic [2.6.28.12.16 -> 2.6.28.13.17]
  linux-restricted-modules-generic [2.6.28.12.16 -> 2.6.28.13.17]
The following packages will be upgraded:
  linux-generic [2.6.28.12.16 -> 2.6.28.13.17]
4 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 13.9kB of archives. After unpacking 0B will be used.
The following packages have unmet dependencies:
  linux-restricted-modules-generic: Depends: linux-restricted-modules-2.6.28-13-generic which is a virtual package.
  linux-headers-generic: Depends: linux-headers-2.6.28-13-generic which is a virtual package.
  linux-image-generic: Depends: linux-image-2.6.28-13-generic which is a virtual package.
Unable to resolve dependencies for the upgrade (no solution found).The following packages have been kept back:
  linux-generic linux-headers-generic linux-image-generic
  linux-restricted-modules-generic

Revision history for this message
Past (artem-pastukhov) wrote :

The same:
The following packages are BROKEN:
  linux-backports-modules-jaunty-generic linux-headers-generic linux-image-generic linux-restricted-modules-generic
The following NEW packages will be installed:
  linux linux-backports-modules-jaunty linux-generic linux-image linux-restricted-modules
0 packages upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
Need to get 31.3kB of archives. After unpacking 295kB will be used.
The following packages have unmet dependencies:
  linux-headers-generic: Depends: linux-headers-2.6.28-13-generic which is a virtual package.
  linux-image-generic: Depends: linux-image-2.6.28-13-generic which is a virtual package.
  linux-backports-modules-jaunty-generic: Depends: linux-backports-modules-2.6.28-13-generic which is a virtual package.
  linux-restricted-modules-generic: Depends: linux-restricted-modules-2.6.28-13-generic which is a virtual package.

Revision history for this message
Ernst (ernst-blaauw) wrote :

The linux-image became available. Still 3 packages have been kept back. sudo aptitude safe-upgrade -v -V:

The following packages are BROKEN:
  linux-backports-modules-jaunty-generic [2.6.28.12.16 -> 2.6.28.13.17] linux-restricted-modules-generic [2.6.28.12.16 -> 2.6.28.13.17]
The following packages will be upgraded:
  linux-backports-modules-jaunty [2.6.28.12.16 -> 2.6.28.13.17]
3 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 10.5kB of archives. After unpacking 0B will be used.
The following packages have unmet dependencies:
  linux-backports-modules-jaunty-generic: Depends: linux-backports-modules-2.6.28-13-generic which is a virtual package.
  linux-restricted-modules-generic: Depends: linux-restricted-modules-2.6.28-13-generic which is a virtual package.
Unable to resolve dependencies for the upgrade (no solution found).The following packages have been kept back:
  linux-backports-modules-jaunty linux-backports-modules-jaunty-generic linux-restricted-modules-generic
0 packages upgraded, 0 newly installed, 0 to remove and 3 not upgraded.

Revision history for this message
hara (harak-iitm) wrote :

Works for me now

Revision history for this message
Erwin Junge (erwin-junge) wrote :

Works for me now as well

Revision history for this message
Past (artem-pastukhov) wrote :

Agree. Fixed.

Revision history for this message
Jefferson H. Xavier (jeffersonx) wrote :

I had the same error in my laptop, but I think it was fixed.

Revision history for this message
Andy Whitcroft (apw) wrote :

This is likely a by product of the manual package accept processing. We expect this to be resolved now. Also reported good here. Closing.

Changed in linux-meta (Ubuntu):
assignee: nobody → Andy Whitcroft (apw)
status: New → Confirmed
status: Confirmed → Fix Released
Revision history for this message
timesarehard4dreamers (timesarehard4dreamers) wrote :

I'm getting same problem on two of my ubuntu-server 8.0.4 machines.

sudo aptitude safe-upgrade -v -V:

The following packages have been automatically kept back:
  libdns35 [1:9.4.2.dfsg.P2-2ubuntu0.2 -> 1:9.4.2.dfsg.P2-2ubuntu0.4]
  libisc35 [1:9.4.2.dfsg.P2-2ubuntu0.2 -> 1:9.4.2.dfsg.P2-2ubuntu0.4]
The following packages have been kept back:
  bind9-host [1:9.4.2.dfsg.P2-2ubuntu0.2 -> 1:9.4.2.dfsg.P2-2ubuntu0.4]
  dnsutils [1:9.4.2.dfsg.P2-2ubuntu0.2 -> 1:9.4.2.dfsg.P2-2ubuntu0.4]
  libbind9-30 [1:9.4.2.dfsg.P2-2ubuntu0.2 -> 1:9.4.2.dfsg.P2-2ubuntu0.4]
  libisccfg30 [1:9.4.2.dfsg.P2-2ubuntu0.2 -> 1:9.4.2.dfsg.P2-2ubuntu0.4]
  liblwres30 [1:9.4.2.dfsg.P2-2ubuntu0.2 -> 1:9.4.2.dfsg.P2-2ubuntu0.4]
  linux-generic [2.6.24.25.27 -> 2.6.24.26.28]
  linux-headers-generic [2.6.24.25.27 -> 2.6.24.26.28]
  linux-image-generic [2.6.24.25.27 -> 2.6.24.26.28]
  linux-restricted-modules-generic [2.6.24.25.27 -> 2.6.24.26.28]
0 packages upgraded, 0 newly installed, 0 to remove and 11 not upgraded.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu:
status: New → Confirmed
Mathew Hodson (mhodson)
affects: proposed-tracking → ubuntu
no longer affects: ubuntu
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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