On Sun, 15 Jul 2007 18:32:23 +0300 > On Sunday 15 July 2007, martin f krafft wrote: > > Yes, exactly. Each packaging attempt gets a separate changelog entry > > and when it's final, you merge them all, effectively erasing the > > history. Martin - my only problem with this collapsing of the changes is that debian/changelog would need to be edited by the sponsor to achieve this without causing yet another rebuild and upload to mentors.d.n cycle. dpkg can collapse the changes from multiple versions into the .changes file automatically and with no need to either edit package files or cause another build/upload cycle. The only difference is that the timestamps are retained. IMHO that is preferable to a whole new cycle or sponsors editing the package directly. > packagename (1.0-1~unreleased.1) unstable; urgency=low > -- John Doe <johndoe@debian.org> Sun, 06 May 2007 21:52:26 +0200 > packagename (1.0-1~unreleased.1) unstable; urgency=low > -- John Doe <johndoe@debian.org> Sun, 07 May 2007 21:52:26 +0200 > // merging all changelog rows in one changelog entry > packagename (1.0-1) unstable; urgency=low It's easy when it is your package but sponsors aren't supposed to be changing the package between mentors.d.n and ftp-master.d.o I'm not sure that just losing the history is sufficient benefit for losing the direct link between mentors.d.n and packages.d.o. I thought that sponsors should only be adding a signature, not changing fundamental files like debian/changelog. Plus the sponsor can't use any debchange type command to do the work because that will put their name into the final timestamp, causing lintian errors of an NMU and another rebuild. IMHO it would be better to keep the ~unreleased or ~rfs change entries intact - with timestamps - into the final package. However, this still means either the sponsor edits debian/changelog and rebuilds prior to the upload OR the sponsor gives the green light to the maintainer to rebuild without the ~rfs suffix on the latest changelog entry (or create yet another), reupload to mentors.d.n and the sponsor has to again check the package and make sure that this is all that has been changed. With timezone issues etc., it can take an appreciable amount of time to complete a full cycle through mentors.d.n. I'm happier with: packagename (1.0-2) unstable; urgency=low -- John Doe <johndoe@debian.org> Sun, 08 May 2007 14:52:26 +0200 packagename (1.0-1) unstable; urgency=low -- John Doe <johndoe@debian.org> Sun, 07 May 2007 21:52:26 +0200 (p)?debuild -sa -v 1.0-1 That could even fit into an alias sponsornew='debuild -sa' and psponsornew etc. Then continue thus until the sponsor is happy with the package, at which point it can be uploaded with only a signature added or modified by the sponsor. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
Attachment:
pgpxQt6_gHmm_.pgp
Description: PGP signature