On Sun, Aug 19, 2007 at 04:41:50PM +0200, Helge Kreutzmann wrote:
> I now worked on the package as well. I looked at the changes and also
> the changes in respect to the latest tarball from SF. Pushing (read:
> committing[1]) things upstream is deferred though until the version in
> Debian stabilized again.

Sounds good :)

> My first round of changes is now done:
>   * Fix minor typos in German man pages.
>   * Update my e-mail address in debian related files
>   * Do not ignore errors in clean targets (thanks, lintian)
>   * Bump standards version to 3.7.2.2
>   * Bump dephelper level to 5

These all look fine to me!

>   * Use linux-libc-dev now as build dependency (instead of
>     linux-kernel-headers)

This, though, is a bug, because linux-kernel-headers and linux-libc-dev are
both virtually build-essential (dependencies of libc6.1-dev). :)  The
correct fix is to just drop this entry from the build-deps.  I've just
committed this change now.

> I think you should upload our changes now. Since I am no kernel developer,
> I cannot really judge some of your/upstream changes, so I leave it up
> to you whether you upload to experimental or unstable (depends on the
> pressure from 2.6.23 as well, of course).

I would prefer to get someone to proactively test it with 2.6.23 before
uploading to the archive, to save on round-trips if the current patch
doesn't actually fix the PT_LOAD bug.  But if nothing else, I'll upload it
when 2.6.23 becomes available in unstable and I've had a chance to test it
myself...

> I have more changes (mostly in the documentatian/build area) in the
> pipeline, I will see if I've time next weekend.

> Thanks for your swift help on getting aboot in shape again!

N/p, thanks for keeping an eye on its status. :)

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[EMAIL PROTECTED]                                   http://www.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to