RE: naming problem with make-kpkg and pcmcia-modules?
Didn't work for me either way. I've got to either reinstall my older kpkg'd
pcmcia-modules or re-kpkg them. It's a bit annoying, but I haven't a better
suggestion, alas.
glen
-----Original Message-----
From: Lee Bradshaw [mailto:lee@sectionIV.com]
Sent: Tuesday, February 15, 2000 11:34 AM
To: debian-devel@lists.debian.org
Cc: debian-devel@lists.debian.org
Subject: naming problem with make-kpkg and pcmcia-modules?
When I updated my frozen system last night, there was a new
pcmcia-modules package which seemed to replace my local custom one. My
kernel-image itself wasn't modified. Both the kernel image and modules
image .deb files were generated with make-kpkg.
new download: pcmcia-modules-2.2.14_3.1.8-6k1_i386.deb
local compiled version:
pcmcia-modules-2.2.14_3.1.8-6+freeswan.1.0_i386.deb
For the kernel-images, the first thing after the first _ in the package
name is whatever the user specified with --revision which should
start with alpha chars and appear to be more recent than any debian
distributed kernel-image for that version. Is there a sorting issue
where the new debian pcmcia-modules seemed to be newer than my version
and automatically updated it?
When building the module image with make-kpkg, should the pcmcia number
go after the --revision field to keep the sorting order correct?
new download: pcmcia-modules-2.2.14_3.1.8-6k1_i386.deb
suggested local version:
pcmcia-modules-2.2.14_freeswan.1.0+3.1.8-6_i386.deb
Could someone who understands the ordering better confirm what happened
and whether changing the name of the locally generated module image .deb
would fix it.
Thanks,
Lee
--
Lee Bradshaw lee@sectionIV.com (preferred)
Alantro Communications lee@alantro.com
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
Reply to: