On Fri, Mar 16, 2007 at 07:56:31PM +0100, Wouter Verhelst wrote: > On Fri, Mar 16, 2007 at 09:27:04AM -0700, Kapil Hari Paranjape wrote:
>> screen (4.0.3-0.3+b1) unstable; urgency=low >> * Binary-only non-maintainer upload for i386; no source changes. >> * Rebuild to fix a bug of indeterminate origin that causes screen to >> switch >> -- Debian/i386 Build Daemon <buildd_i386-saens> Tue, 6 Mar 2007 >> 17:06:12 -0600 > When a binNMU is necessary, someone with appropriate access to the right > machine will run this: > wanna-build -b <arch>/build-db -d unstable -m "Rebuild for the GCC10 > transition" --binNMU=1 foobar_1.2-3 > which will result in the buildd host downloading the source, adding a > changelog entry, compiling it, and the human behind the curtains signing > the log. > Since the buildd host generates the changelog entry, it's only natural > that it's also the buildd host which is listed in the changelog > entry. Since it is acting on behalf of the "someone with appropriate access to the right machine", and that is the person providing the "rebuild for the GCCC10 transition" message, it would seem natural to me that that's the name the changelog is signed with. After all, my changelog entries are not signed by my Emacs or my debchange. -- Lionel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
