On 2010-05-19 20:00 +0200, Hugo Vanwoerkom wrote:

> I have my own kernel installed:
>
> hugo@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...

Do you have mindi installed? Otherwise I cannot see a package in
sid/experimental that would pull in linux-image-2.6-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?

No, but please run "aptitude -s -D full-upgrade" to figure out why
linux-image-2.6-486 gets installed.

Sven


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87ocgb3gjs.fsf@turtle.gmx.de">http://lists.debian.org/87ocgb3gjs.fsf@turtle.gmx.de

Sven Joachim wrote:

On 2010-05-19 20:00 +0200, Hugo Vanwoerkom wrote:


I have my own kernel installed:

hugo@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...


Do you have mindi installed? Otherwise I cannot see a package in
sid/experimental that would pull in linux-image-2.6-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?


No, but please run "aptitude -s -D full-upgrade" to figure out why
linux-image-2.6-486 gets installed.



Bingo. It's mindi. The funny thing is I install mondo(with mindi) from
upstream because its support on Debian has fallen by the wayside:

current is 2.2.9.3-1 and debian still has 1:2.2.7-2.1.

Thanks a lot!

Hugo


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: ht1b12$it7$1@dough.gmane.org">http://lists.debian.org/ht1b12$it7$1@dough.gmane.org

On Wednesday 19 May 2010 13:35:13 Hugo Vanwoerkom wrote:
> Sven Joachim wrote:
> > On 2010-05-19 20:00 +0200, Hugo Vanwoerkom wrote:
> >> I have my own kernel installed:
> >>
> >> hugo@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...
> >
> > Do you have mindi installed? Otherwise I cannot see a package in
> > sid/experimental that would pull in linux-image-2.6-486.
>
> Bingo. It's mindi. The funny thing is I install mondo(with mindi) from
> upstream because its support on Debian has fallen by the wayside:
> current is 2.2.9.3-1 and debian still has 1:2.2.7-2.1.

Two patch levels (2.2.9 vs. 2.2.7) is fallen by the wayside? Really? It
looks like some of those changes even got integrated into the package -- there
was an NMU for it (Debian revision 2.1).

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.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
bss@iguanasuicide.net ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/ \_/

Boyd Stephen Smith Jr. wrote:

On Wednesday 19 May 2010 13:35:13 Hugo Vanwoerkom wrote:

Sven Joachim wrote:

On 2010-05-19 20:00 +0200, Hugo Vanwoerkom wrote:

I have my own kernel installed:

hugo@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...

Do you have mindi installed? Otherwise I cannot see a package in
sid/experimental that would pull in linux-image-2.6-486.

Bingo. It's mindi. The funny thing is I install mondo(with mindi) from
upstream because its support on Debian has fallen by the wayside:
current is 2.2.9.3-1 and debian still has 1:2.2.7-2.1.


Two patch levels (2.2.9 vs. 2.2.7) is fallen by the wayside? Really? It
looks like some of those changes even got integrated into the package -- there
was an NMU for it (Debian revision 2.1).


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@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.




--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: ht444f$gl5$1@dough.gmane.org">http://lists.debian.org/ht444f$gl5$1@dough.gmane.org

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@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

Hi, Hugo:

On Wednesday 19 May 2010 20:00:24 Hugo Vanwoerkom wrote:
> Hi,
>
> Another apt question.
>
> I have my own kernel installed:
>
> hugo@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@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201005220317.31102.jesus.navarro@undominio.net">ht tp://lists.debian.org/201005220317.31102.jesus.navarro@undominio.net