Re: make-kpkg and 2.2.12
I used --revision=custom.1.0 kernel_image with 2.2.11 and it worked fine.
I applied an ac patch at a later time and when using make-kpkg with the
same as above gave an "not in control info" error. But with 2.2.12 did not
get this error as it did with someone else. Im using a frequently
updated potato.
meridian
me@NOSPAM.tha.net
all that busts well ends loosely.
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.
>
> Bob
>
> --
> Bob Nielsen Internet: nielsen@primenet.com
> Tucson, AZ AMPRnet: w6swe@w6swe.ampr.org
> DM42nh http://www.primenet.com/~nielsen
>
>
> --
> Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
>
Reply to: