On Mon, Feb 09, 2009 at 12:14:49AM -0600, Manoj Srivastava wrote:
> Hi,
>
> This is a heads up for a major change in kernel-package, the
> tool to create user packaged kernel images and headers; which will
> make the make-kpkg script far less error prone, and far more
> deterministic.
>
> a. Every invocation of kernel-package will remove ./debian directory,
> and regenerate the changelog and control files. This will get rid
> of any remaining issues with the ./debian directory getting out of
> sync with the kernel sources; and will allow people to make small
> tweaks to the kernel sources and have make-kpkg reflect those
> changes.

Is there going to be a way for people to replace the changelog with
one that contains useful information in that case? I've been doing
this by doing a make-kpkg configure and then editing the
debian/changelog file afterwards...

BTW, I have a set of patches you might want to consider. I'll file
them in BTS if you're currently making make-kpkg.

- Ted


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Feb 09, 2009 at 12:14:49AM -0600, Manoj Srivastava wrote:
> Hi,
>
> This is a heads up for a major change in kernel-package, the
> tool to create user packaged kernel images and headers; which will
> make the make-kpkg script far less error prone, and far more
> deterministic.
>
> a. Every invocation of kernel-package will remove ./debian directory,
> and regenerate the changelog and control files. This will get rid
> of any remaining issues with the ./debian directory getting out of
> sync with the kernel sources; and will allow people to make small
> tweaks to the kernel sources and have make-kpkg reflect those
> changes.

Is there going to be a way for people to replace the changelog with
one that contains useful information in that case? I've been doing
this by doing a make-kpkg configure and then editing the
debian/changelog file afterwards...

BTW, I have a set of patches you might want to consider. I'll file
them in BTS if you're currently making make-kpkg.

- Ted


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Wed, Feb 18 2009, Theodore Tso wrote:

> On Mon, Feb 09, 2009 at 12:14:49AM -0600, Manoj Srivastava wrote:
>> Hi,
>>
>> This is a heads up for a major change in kernel-package, the
>> tool to create user packaged kernel images and headers; which will
>> make the make-kpkg script far less error prone, and far more
>> deterministic.
>>
>> a. Every invocation of kernel-package will remove ./debian directory,
>> and regenerate the changelog and control files. This will get rid
>> of any remaining issues with the ./debian directory getting out of
>> sync with the kernel sources; and will allow people to make small
>> tweaks to the kernel sources and have make-kpkg reflect those
>> changes.
>
> Is there going to be a way for people to replace the changelog with
> one that contains useful information in that case? I've been doing
> this by doing a make-kpkg configure and then editing the
> debian/changelog file afterwards...>

I have a plan for something like this, though currently there is
no code. I was thinking of doing an "overlay" for ./debian, kind of
like what ikiwiki and request-tracker do; so /usr/share/kernel-package
contain the information that goes into ./debian; but if there is a user
specified overlay, then files present in the overlay are used instead
(files not in the overlay dir still come from the default location).

I have not yet written the code, since there are several places
in the build where we look for files in ./debian; and currently there
is a fallback to /usr/share/kernel-package if ./debian does not exist;
either I have to remove the fallback, or enhance the fallback mechanism
(at potentially significant run-time cost).

The cleaner solution would be for make-kpkg to always remove and
re-create ./debian (with overlays), but make -f ./debian/rules never
have to deal with anything outside (so to remove the fallback code that
has sprouted all over the rules files). It might take a few iterations
to do these changes, but I think it is worth it, for robstness' sake if
nothing else.

> BTW, I have a set of patches you might want to consider. I'll file
> them in BTS if you're currently making make-kpkg.

Please. I have been thinking about the request you made for
debugging symbols being packaged, and now I do have some time to play
with building kernels again, I would like to see that in Squeeze.

manoj
--
Men are from Earth, women are from Earth. Deal with it. George Carlin
Manoj Srivastava <srivasta@acm.org> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Wed, Feb 18 2009, Theodore Tso wrote:

> On Mon, Feb 09, 2009 at 12:14:49AM -0600, Manoj Srivastava wrote:
>> Hi,
>>
>> This is a heads up for a major change in kernel-package, the
>> tool to create user packaged kernel images and headers; which will
>> make the make-kpkg script far less error prone, and far more
>> deterministic.
>>
>> a. Every invocation of kernel-package will remove ./debian directory,
>> and regenerate the changelog and control files. This will get rid
>> of any remaining issues with the ./debian directory getting out of
>> sync with the kernel sources; and will allow people to make small
>> tweaks to the kernel sources and have make-kpkg reflect those
>> changes.
>
> Is there going to be a way for people to replace the changelog with
> one that contains useful information in that case? I've been doing
> this by doing a make-kpkg configure and then editing the
> debian/changelog file afterwards...>

I have a plan for something like this, though currently there is
no code. I was thinking of doing an "overlay" for ./debian, kind of
like what ikiwiki and request-tracker do; so /usr/share/kernel-package
contain the information that goes into ./debian; but if there is a user
specified overlay, then files present in the overlay are used instead
(files not in the overlay dir still come from the default location).

I have not yet written the code, since there are several places
in the build where we look for files in ./debian; and currently there
is a fallback to /usr/share/kernel-package if ./debian does not exist;
either I have to remove the fallback, or enhance the fallback mechanism
(at potentially significant run-time cost).

The cleaner solution would be for make-kpkg to always remove and
re-create ./debian (with overlays), but make -f ./debian/rules never
have to deal with anything outside (so to remove the fallback code that
has sprouted all over the rules files). It might take a few iterations
to do these changes, but I think it is worth it, for robstness' sake if
nothing else.

> BTW, I have a set of patches you might want to consider. I'll file
> them in BTS if you're currently making make-kpkg.

Please. I have been thinking about the request you made for
debugging symbols being packaged, and now I do have some time to play
with building kernels again, I would like to see that in Squeeze.

manoj
--
Men are from Earth, women are from Earth. Deal with it. George Carlin
Manoj Srivastava <srivasta@acm.org> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Fri, Feb 20, 2009 at 12:56:30PM -0600, Manoj Srivastava wrote:
> On Wed, Feb 18 2009, Theodore Tso wrote:
>
> > On Mon, Feb 09, 2009 at 12:14:49AM -0600, Manoj Srivastava wrote:
> >> Hi,
> >>
> >> This is a heads up for a major change in kernel-package, the
> >> tool to create user packaged kernel images and headers; which will
> >> make the make-kpkg script far less error prone, and far more
> >> deterministic.
> >>
> >> a. Every invocation of kernel-package will remove ./debian directory,
> >> and regenerate the changelog and control files. This will get rid
> >> of any remaining issues with the ./debian directory getting out of
> >> sync with the kernel sources; and will allow people to make small
> >> tweaks to the kernel sources and have make-kpkg reflect those
> >> changes.
> >
> > Is there going to be a way for people to replace the changelog with
> > one that contains useful information in that case? I've been doing
> > this by doing a make-kpkg configure and then editing the
> > debian/changelog file afterwards...>
>
> I have a plan for something like this, though currently there is
> no code. I was thinking of doing an "overlay" for ./debian, kind of
> like what ikiwiki and request-tracker do; so /usr/share/kernel-package
> contain the information that goes into ./debian; but if there is a user
> specified overlay, then files present in the overlay are used instead
> (files not in the overlay dir still come from the default location).
>
> I have not yet written the code, since there are several places
> in the build where we look for files in ./debian; and currently there
> is a fallback to /usr/share/kernel-package if ./debian does not exist;
> either I have to remove the fallback, or enhance the fallback mechanism
> (at potentially significant run-time cost).
>
> The cleaner solution would be for make-kpkg to always remove and
> re-create ./debian (with overlays), but make -f ./debian/rules never
> have to deal with anything outside (so to remove the fallback code that
> has sprouted all over the rules files). It might take a few iterations
> to do these changes, but I think it is worth it, for robstness' sake if
> nothing else.
>
> > BTW, I have a set of patches you might want to consider. I'll file
> > them in BTS if you're currently making make-kpkg.
>
> Please. I have been thinking about the request you made for
> debugging symbols being packaged, and now I do have some time to play
> with building kernels again, I would like to see that in Squeeze.

I know Troy Heber had submitted some patches for debug/kdump support -
those would be interesting as well

--
dann frazier


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Manoj Srivastava <srivasta@ieee.org> writes:

> On Wed, Feb 18 2009, Theodore Tso wrote:
>
>> On Mon, Feb 09, 2009 at 12:14:49AM -0600, Manoj Srivastava wrote:
>>> Hi,
>>>
>>> This is a heads up for a major change in kernel-package, the
>>> tool to create user packaged kernel images and headers; which will
>>> make the make-kpkg script far less error prone, and far more
>>> deterministic.
>>>
>>> a. Every invocation of kernel-package will remove ./debian directory,
>>> and regenerate the changelog and control files. This will get rid
>>> of any remaining issues with the ./debian directory getting out of
>>> sync with the kernel sources; and will allow people to make small
>>> tweaks to the kernel sources and have make-kpkg reflect those
>>> changes.
>>
>> Is there going to be a way for people to replace the changelog with
>> one that contains useful information in that case? I've been doing
>> this by doing a make-kpkg configure and then editing the
>> debian/changelog file afterwards...>
>
> I have a plan for something like this, though currently there is
> no code. I was thinking of doing an "overlay" for ./debian, kind of
> like what ikiwiki and request-tracker do; so /usr/share/kernel-package
> contain the information that goes into ./debian; but if there is a user
> specified overlay, then files present in the overlay are used instead
> (files not in the overlay dir still come from the default location).

It might be nice to have a changelog.d/ directory in the source with
sniplets for the debian/changelog. All files would be cated together
and used as the text for the current changelog entry.

This would have two use cases:

1) Patch packages can drop a file in there (when the user applies the
patch) saying what got applied.

2) Users can add their own files there detailing what they changed.
E.g. ' * added CONFIG_SCSI_DISK=y'

As I write this I notice that (2) doesn't quite work. For my manual
entries I would like to specify a version. E.g. in 2.6.26-1 I added
CONFIG_SCSI_DISK=y, in 2.6.26-2 I added CONFIG_SCSI_CDROM=y and in
2.6.26-3 I removed it again.

But maybe that goes too far. Just being able to add to the current
entry would be a good start already.

MfG
Goswin


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Wed, Feb 25 2009, Goswin von Brederlow wrote:

> Manoj Srivastava <srivasta@ieee.org> writes:
>
>> On Wed, Feb 18 2009, Theodore Tso wrote:
>>
>>> On Mon, Feb 09, 2009 at 12:14:49AM -0600, Manoj Srivastava wrote:
>>>> Hi,
>>>>
>>>> This is a heads up for a major change in kernel-package, the
>>>> tool to create user packaged kernel images and headers; which will
>>>> make the make-kpkg script far less error prone, and far more
>>>> deterministic.
>>>>
>>>> a. Every invocation of kernel-package will remove ./debian directory,
>>>> and regenerate the changelog and control files. This will get rid
>>>> of any remaining issues with the ./debian directory getting out of
>>>> sync with the kernel sources; and will allow people to make small
>>>> tweaks to the kernel sources and have make-kpkg reflect those
>>>> changes.
>>>
>>> Is there going to be a way for people to replace the changelog with
>>> one that contains useful information in that case? I've been doing
>>> this by doing a make-kpkg configure and then editing the
>>> debian/changelog file afterwards...>
>>
>> I have a plan for something like this, though currently there is
>> no code. I was thinking of doing an "overlay" for ./debian, kind of
>> like what ikiwiki and request-tracker do; so /usr/share/kernel-package
>> contain the information that goes into ./debian; but if there is a user
>> specified overlay, then files present in the overlay are used instead
>> (files not in the overlay dir still come from the default location).
>
> It might be nice to have a changelog.d/ directory in the source with
> sniplets for the debian/changelog. All files would be cated together
> and used as the text for the current changelog entry.
>
> This would have two use cases:
>
> 1) Patch packages can drop a file in there (when the user applies the
> patch) saying what got applied.
>
> 2) Users can add their own files there detailing what they changed.
> E.g. ' * added CONFIG_SCSI_DISK=y'
>
> As I write this I notice that (2) doesn't quite work. For my manual
> entries I would like to specify a version. E.g. in 2.6.26-1 I added
> CONFIG_SCSI_DISK=y, in 2.6.26-2 I added CONFIG_SCSI_CDROM=y and in
> 2.6.26-3 I removed it again.
>
> But maybe that goes too far. Just being able to add to the current
> entry would be a good start already.

Both these options are far more complex than anything I had
planned on doing; since while they are laudable goals, the effort
required seems to be kind of high based on the return -- espescially
now that the official kernels are not built with kernel-package; the
audience of kernel-package created images is lower.

However, I'll be happy to incorporate any patches people submit
to get this feature into kernel-package.

manoj
--
People think love is an emotion. Love is good sense. Ken Kesey
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/~srivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Fri, Feb 20, 2009 at 12:56:30PM -0600, Manoj Srivastava wrote:
> > BTW, I have a set of patches you might want to consider. I'll file
> > them in BTS if you're currently making make-kpkg.
>
> Please. I have been thinking about the request you made for
> debugging symbols being packaged, and now I do have some time to play
> with building kernels again, I would like to see that in Squeeze.

Sorry for the delay; I've sent you the private patches I've been using
for make-kpkg. Some of them are quite hackish, and some of they you
may have fixed in other ways, so I won't feel bad at all if you need
to significantly rework them before you can merge them into your
master sources.

The BTS bug numbers are #517290, #517291, #517292, and #517293.

Best regards,

- Ted


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org