Re: make-kpkg and 2.2.12
-----BEGIN PGP SIGNED MESSAGE-----
On Fri, 27 Aug 1999, Bob Nielsen wrote:
> On Thu, Aug 26, 1999 at 11:22:02PM -0700, Eric G . Miller wrote:
> > On Fri, Aug 27, 1999 at 12:22:23AM -0500, Brad wrote:
> > | I've always used, for example, "--revision=2.2.12-hostname.1" because
> > | dselect always wanted to replace my custom kernels with the stock ones
> > | once that version went up on the mirrors if i used just "custom.1"...
> > |
> > | Anyway, 2.2.12-* is the proper version format ;)
> >
> > I haven't had this problem of dselect trying to replace kernels with a
> > "custom.n.n" in the name. My kernels always come out with the version
> > number before the custom part "kernel-image-2.2.10_custom.1.9_i386.deb".
> > Maybe this reflects changes in dselect and make-kpkg?
>
> I've seen it happen once. I think it was with a kernel-image which used
> epochs. The kernel-package documentation recommends using epochs to
> avoid this: make-kpkg --revision=1:custom.1.0 kernel_image.
Looking back, i think you're right. IIRC it was 2.2.5 that made me change,
and the kernel-image-2.2.5 package on the mirrors does have an epoch.
- --
finger for PGP public key.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv
iQCVAwUBN8cvCL7M/9WKZLW5AQHprAQAoJ1bV1lBrDnJOktZIcU8TmeaUoHhOP+f
+yQt3M8JJ47eoAi6RZ+MHUS2SVs/9JF9IW+3DUm8h7pBaOTu4zzi/kBZa1cYGsnl
C0ScAxNK5arZb3nnGJmHLoZDq5MQXdJKnL2OZZPaFgGzV81NvwTQaZOdDASTEj6J
hHPp2LzAkp4=
=v/zH
-----END PGP SIGNATURE-----
Reply to: