Re: Bug#474949: debsign: deals badly with Format: 1.8 .changes files and new Checksums-* headers
Guillem Jover wrote:
> Hi,
Hi
> On Tue, 2008-04-08 at 20:16:58 +0200, Luk Claes wrote:
>> Raphael Hertzog wrote:
>>> On Tue, 08 Apr 2008, Raphael Hertzog wrote:
>>>> dpkg >= 1.14.17 generates *.changes files with Format: 1.8. They provide
>>>> new Checksums-*: fields which are similar to the Files: field. And debsign
>>>> edits in place the Files: field of changes file and leaves the Checksums-*
>>>> fields alone.
>>> Here's a patch that fixes the issue. I would highly appreciate if you
>>> could upload a fixed package today because it's blocking the upload of dpkg
>>> to unstable currently. (And we're tight on schedule with dpkg because of
>>> the base freeze and there are many features in this version of dpkg that
>>> we really want for lenny).
>> A freeze date is not a date to target major uploads at...
>
> I don't see any problem with adding features up to the point of the
> freeze, and I think others on the team share the same opinion.
It's a problem as the package would still need to migrate while being
frozen...
>> You might be aware that dpkg is currently already frozen and a release
>> update posting is pending...
>
> I don't think anyone on the team was aware of this until now, neither of
> any exact date this would be happening (and I try to keep an eye on the
> irc channel and release mailing list).
It was announced very early that the toolchain freeze would be early
april...
>> Note that in particular the triggers support and any RC bug fixes are
>> still candidates for migration to testing, though other features might
>> not be depending on their impact...
>
> I can understand that the freeze imposes a feature freeze on those
> packages, but not that it restricts to only RC bug fixes at this point
> when there's still 5-6 months to the target release date.
Please read again...
Cheers
Luk
Reply to: