Bug#480723: developers-reference: Please update section 5.11.6 (Acknowledging an NMU)
tags 480723 + patch thanks Francesco Namuri [EMAIL PROTECTED] writes: I propose the change of this part: Once this is done, you have to close the bugs that have been tagged fixed by the NMU. The easiest way is to use the -v option of dpkg-buildpackage, as this allows you to include just all changes since your last maintainer upload. Alternatively, you can close them manually by sending the required mails to the BTS or by adding the required closes: # in the changelog entry of your next upload. Yep, this is wrong nowadays. I would propose to apply the following diff to update this part: Index: pkgs.dbk === --- pkgs.dbk(revision 5203) +++ pkgs.dbk(working copy) @@ -2016,13 +2016,12 @@ para If one of your packages has been NMU'ed, you have to incorporate the changes in your copy of the sources. This is easy, you just have to apply the patch that -has been sent to you. Once this is done, you have to close the bugs that have -been tagged fixed by the NMU. The easiest way is to use the -literal-v/literal option of commanddpkg-buildpackage/command, as this -allows you to include just all changes since your last maintainer upload. -Alternatively, you can close them manually by sending the required mails to the -BTS or by adding the required literalcloses: #/literal in the changelog -entry of your next upload. +has been sent to you. +Once this is done, you have to check if the bug has been already closed +by the author of the NMU. If this has been done, you just need to keep the +changelog entry of the NMU in your filenamedebian/changelog/filename. +Should the bugs still be open, use the mail interface of the BTS to +mark them closed in the version of the NMU. /para para In any case, you should not be upset by the NMU. An NMU is not a personal Reasoning to drop the -v hint: It's wrong. If the bug has been closed in the NMU version, the BTS should know about it. If the NMUer screwed things up and didn't close the (right) bug, the maintainer should just fix the versioning information, nothing more. Using -v as originally described will close the bug with the next version of the maintainer upload. Marc -- BOFH #435: Internet shut down due to maintainance pgp1pZTawyqAy.pgp Description: PGP signature
Bug#480723: developers-reference: Please update section 5.11.6 (Acknowledging an NMU)
On 03/06/08 at 10:21 +0200, Marc 'HE' Brockschmidt wrote: tags 480723 + patch thanks Francesco Namuri [EMAIL PROTECTED] writes: I propose the change of this part: Once this is done, you have to close the bugs that have been tagged fixed by the NMU. The easiest way is to use the -v option of dpkg-buildpackage, as this allows you to include just all changes since your last maintainer upload. Alternatively, you can close them manually by sending the required mails to the BTS or by adding the required closes: # in the changelog entry of your next upload. Yep, this is wrong nowadays. I would propose to apply the following diff to update this part: Hi, I think that the NMU DEP will be ready 2-3 weeks. I'll address all the NMU-related bugs at that point. I really don't think that it's necessary to fix those bugs now. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | signature.asc Description: Digital signature
Bug#480723: developers-reference: Please update section 5.11.6 (Acknowledging an NMU)
Package: developers-reference Version: 3.3.9 Severity: normal Hi, looking at Colin Watson message [1] the section regarding the acknowledging of an NMU is outdated. With the new BTS version tracking if a package has been NMU'ed it is supposed that the author of the NMU closes the bug directly so from the maintainer is only required the incorporation of the changes in its copy of the sources. I propose the change of this part: Once this is done, you have to close the bugs that have been tagged fixed by the NMU. The easiest way is to use the -v option of dpkg-buildpackage, as this allows you to include just all changes since your last maintainer upload. Alternatively, you can close them manually by sending the required mails to the BTS or by adding the required closes: # in the changelog entry of your next upload. in something like this: Once this is done, you have to check if the bug has been already closed by the author of the NMU, in such case you have nothing else to do, in the other case you have to close the bugs that have been tagged fixed by the NMU. The easiest way is to use the -v option of dpkg-buildpackage, as this allows you to include just all changes since your last maintainer upload. Alternatively, you can close them manually by sending the required mails to the BTS or by adding the required closes: # in the changelog entry of your next upload. Best Regards, francesco [1] http://lists.debian.org/debian-devel-announce/2005/07/msg00010.html -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (850, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash developers-reference depends on no packages. Versions of packages developers-reference recommends: ii debian-policy 3.7.3.0Debian Policy Manual and related d -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
