Bug#473518: dupload: Fails to parse the .changes file with latest dpkg-dev
On Mon, 31 Mar 2008, Frank Lichtenheld wrote: On Mon, Mar 31, 2008 at 08:00:34AM +0300, Guillem Jover wrote: It fails to work with dpkg-dev 1.14.17 from experimental. This is due to the new Checksums fields, I think. Would be nice to get fixed before we upload a new dpkg version to unstable, and people can no longer properly use dupload. Urgs, that code is horrid. It assumes that the Files: field will always be last in the .changes file. The unstable version should obviously be fixed. But we might be able to work around it for the etch version by just assuring that the Files: field is indeed listed last. Indeed, I just pushed such a change in dpkg's master branch. sbuild also has the same bug so it's definitely worth it. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/
Bug#473518: dupload: Fails to parse the .changes file with latest dpkg-dev
On Mon, Mar 31, 2008 at 08:27:05PM +0200, Frank Lichtenheld wrote: On Mon, Mar 31, 2008 at 08:00:34AM +0300, Guillem Jover wrote: It fails to work with dpkg-dev 1.14.17 from experimental. This is due to the new Checksums fields, I think. Would be nice to get fixed before we upload a new dpkg version to unstable, and people can no longer properly use dupload. Urgs, that code is horrid. It assumes that the Files: field will always be last in the .changes file. The unstable version should obviously be fixed. But we might be able to work around it for the etch version by just assuring that the Files: field is indeed listed last. Yep, the parser works when you move the two new Checksums-* fields before Files, I just tested it. -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#473518: dupload: Fails to parse the .changes file with latest dpkg-dev
On Mon, Mar 31, 2008 at 08:00:34AM +0300, Guillem Jover wrote: Package: dupload Version: 2.6.3.3 Severity: important It fails to work with dpkg-dev 1.14.17 from experimental. This is due to the new Checksums fields, I think. Would be nice to get fixed before we upload a new dpkg version to unstable, and people can no longer properly use dupload. Please note that the build daemons are using dupload to upload packages. Moreover, they are using the version from Etch. That's why I think dpkg should not add those Checksums fields until at least dupload is fixed and a package is uploaded to the debian-admin repository. -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#473518: dupload: Fails to parse the .changes file with latest dpkg-dev
On Mon, Mar 31, 2008 at 08:00:34AM +0300, Guillem Jover wrote: It fails to work with dpkg-dev 1.14.17 from experimental. This is due to the new Checksums fields, I think. Would be nice to get fixed before we upload a new dpkg version to unstable, and people can no longer properly use dupload. Urgs, that code is horrid. It assumes that the Files: field will always be last in the .changes file. The unstable version should obviously be fixed. But we might be able to work around it for the etch version by just assuring that the Files: field is indeed listed last. Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#473518: dupload: Fails to parse the .changes file with latest dpkg-dev
Package: dupload Version: 2.6.3.3 Severity: important It fails to work with dpkg-dev 1.14.17 from experimental. This is due to the new Checksums fields, I think. Would be nice to get fixed before we upload a new dpkg version to unstable, and people can no longer properly use dupload. thanks, guillem -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
