dist-upgrade wants to install linux-image-2.6.32-5-686
in [Debian]
|
Prev: ~/.xsession-errors file grows way too big
Next: xorg-server failing on IBM NetVista with Intel 82815 video; was Re (6): Re^n: Grub vs. linux-image-2.6.32 conundrum
From: Andrei Popescu on 21 May 2010 04:30 On Thu,20.May.10, 14:55:57, Hugo Vanwoerkom wrote: > Boyd Stephen Smith Jr. wrote: > > > >Depending on the scope of patch level changes on this project > >(x.y.z -> x = Major, y = Minor, z = Patch level), I don't think > >missing a few is a big deal. > > -- Rogério Brito <rbrito(a)ime.usp.br> Sat, 29 Aug 2009 03:45:43 -0300 > is the last Debian update from upstream. > 2.2.9.3-1 was announced April 16, 2010, which I use. That is 7.5 > months without activity. Depending on what the change is from 2.2.7 > to 2.2.9 that might be a big deal. ^^^^^^^ Instead of speculating, why not look up the changelog/release notes? ;) Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
From: Jesús M. Navarro on 21 May 2010 21:20
Hi, Hugo: On Wednesday 19 May 2010 20:00:24 Hugo Vanwoerkom wrote: > Hi, > > Another apt question. > > I have my own kernel installed: > > hugo(a)debian:~/.fvwm$ dpkg -l | grep linux-image > ii linux-image-2.6.33.3-hvw 1 > Linux kernel binary image for version 2.6.33.3-hvw > ii linux-image-2.6.33.4-hvw 1 > Linux kernel binary image for version 2.6.33.4-hvw > > no headers and no other debian images. > > When I do a apt-get dist-upgrade though I see: > > The following NEW packages will be installed: > ...linux-image-2.6-486 linux-image-2.6.32-5-486... > > which I want to avoid, because it adds to the time to do the upgrade and > I am only interested in Debian's 2.6.33, which is still in experimental. > > Can anyone think of a way around this? I bet you already have installed the linux-image-2.6-486 package which is a virtual one which points to "whatever is the highest current linux-image for the 2.6-486 branch". This is usually quite usefull since it avoids you to know what such current package is. Since you don't want to get such a "most current package", remove the linux-image-2.6-486 one if it's in fact already installed. From then on you'll need to specifically look for and manually install any new higher kernel on that series, but that's exactly what you want, isn't it? Cheers. -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/201005220317.31102.jesus.navarro(a)undominio.net |