On Thu, 08 Dec 2005 08:15:58 +0100, Harald Dunkel <[EMAIL PROTECTED]> said:
> Hi Manoj, Sorry, but I did neither tell kernel-package to use
> "kernel-image" as a package name, nor did I tell the new version to
> change the name to "linux-image". The naming conflict was introduced
> by kernel-package, AFAICS.
And you were told about this when you installed the new
kernel-package, via NEW,Debian. (You do have apt-listchanges and
stuff, since you are following Sid, right?)
And the .deb file produced was definitely different -- it said
linux-image-foo and not kernel-image-foo.
> The only warning I got was that I was trying to replace a running
> kernel.
And that was the time to think about what can go wrong.
> AFAIK control provides the means to introduce new packages replacing
> old ones with a different name. See
> http://www.debian.org/doc/debian-policy/ch-relationships.html
Err, the control file in this case is autogenerated, and the
corner case of people using Sid who try an install a version built
by the new kernel package _and_ overwriting /lib/modulez is not worth
complicating the code with,
As I said, Caceat Emptor.
manoj
--
The older you get, the better you realize you were. George Carlin
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
