The same happens to me since a few days. Before everything was ok, and my custom version was considered as newer by dselect.
I put it on hold, and this works fine, but I don't understand what's the reason. What is the "epoch"? Thanks Alessandro On Thu, 21 Sep 2000, Sean 'Shaleh' Perry wrote: > > > > So. How can I convince apt-get to cleave only unto my customized kernel > > package, forever forsaking all others, as long as we both shall live? > > Is there any way other than rebuilding and reinstalling my kernel > > package with an even _higher_ epoch, in a veritable arms race of package > > version numbering? > > > > not sure why this is happening to you, but an easy solution is to set the > package on hold. You can do this using dselect or on the command line with > echo "kernel-image-2.2.17 hold" |dpkg --set-selections. > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > >
