On Wed, 16 Feb 2005 00:32:38 -0800, Joshua Kwan <[EMAIL PROTECTED]> said:
> Manoj Srivastava wrote:
>> So the next time you break official kernel packages, talk to the
>> kernel-package maintainer _first_. I'll put a kludge in around the
>> fuckup in a future upload.
> It's not a major bug, dud
Manoj Srivastava wrote:
So the next time you break official kernel packages, talk to
the kernel-package maintainer _first_. I'll put a kludge in around
the fuckup in a future upload.
It's not a major bug, dude. Nor is it breakage at all; it's a feature.
The build symlink is meant to allo
On Tue, 15 Feb 2005 23:52:07 -0800, Joshua Kwan <[EMAIL PROTECTED]> said:
> Manoj Srivastava wrote:
>> Since the headers package produced by kernel-package does not have
>> any such link, it is not surprising that kernel-package is not
>> aware of such links introduced by other parties.
> Fine.
Manoj Srivastava wrote:
Since the headers package produced by kernel-package does not
have any such link, it is not surprising that kernel-package is not
aware of such links introduced by other parties.
Fine.
So create an exception. Or make kernel-package build kernel-headers with
that sy
On Tue, 15 Feb 2005 12:59:35 -0800, Joshua Kwan <[EMAIL PROTECTED]> said:
> IMHO it should not warn if only the build symlink is present, which
> is standard for all subarch-specific kernel-headers packages.
Since the headers package produced by kernel-package does not
have any such lin
Package: kernel-package
Version: 8.121
Severity: minor
Hi,
I was testing some kernel-headers packages today and so at first things
looked like this:
$ tree /lib/modules/2.4.27-2-sparc64
/lib/modules/2.4.27-2-sparc64
`-- build -> /usr/src/kernel-headers-2.4.27-2-sparc64
I then decided to test th
6 matches
Mail list logo
