Your message dated Sun, 17 Feb 2019 13:34:11 +0000 with message-id <e1gvmab-0005ln...@fasolo.debian.org> and subject line Bug#775740: fixed in developers-reference 3.4.23 has caused the Debian Bug report #775740, regarding developers-reference: please clarify the recipients when sending to 123-submitter@b.d.o to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 775740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775740 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: developers-reference Version: 3.4.14 Severity: wishlist Hi, in the d-devel thread starting here [1] I learned that 123-submitter@b.d.o is only sent to the bts and the submitter but *not* to the maintainer. This came as a surprise to me after reading section 5.8.2. of devref which currently says: > When responding to bugs, make sure that any discussion you have about > bugs is sent both to the original submitter of the bug, and to the bug > itself (e.g., <1...@bugs.debian.org>). If you're writing a new mail and > you don't remember the submitter email address, you can use the > <123-submit...@bugs.debian.org> email to contact the submitter and to > record your mail within the bug log (that means you don't need to send > a copy of the mail to <1...@bugs.debian.org>). So the above paragraph suggests that sending an email to 123@b.d.o and the submitter email is the same as sending it to 123-submitter@b.d.o while in fact the latter will not send the mail to the package maintainer. The last sentence even says that I don't need to send a copy to 123@b.d.o while in fact I should such that the maintainer of the package gets a copy. So this paragraph should either: - clarify that this course of action is only the right one for packages where *I* am the submitter (as in this cases there is no need to also send the email to myself) - or explicitly state to whom email is sent in each case Maybe the paragraph should be completely reformulated like this: > When responding to bugs, make sure that any discussion you have about > bugs is sent to the original submitter of the bug, the bug itself and > (if you are not the maintainer of the package) the maintainer. Sending > an email to 1...@bugs.debian.org will send the mail to the maintainer > of the package and record your email with the bug log. If you don't > remember the submitter email address, you can use > 123-submit...@bugs.debian.org to also contact the submitter of the > bug. The latter address also records the email with the bug log, so if > you are the maintainer of the package in question, it is enough to > send the reply to 123-submit...@bugs.debian.org. Otherwise you should > include 1...@bugs.debian.org so that you also reach the package > maintainer. Thanks! cheers, josch [1] http://lists.debian.org/54bc1734.5050...@sourcepole.ch
--- End Message ---
--- Begin Message ---Source: developers-reference Source-Version: 3.4.23 We believe that the bug you reported is fixed in the latest version of developers-reference, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 775...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Holger Levsen <hol...@debian.org> (supplier of updated developers-reference package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sun, 17 Feb 2019 13:44:03 +0100 Source: developers-reference Architecture: source Version: 3.4.23 Distribution: unstable Urgency: medium Maintainer: Developers Reference Maintainers <debian-policy@lists.debian.org> Changed-By: Holger Levsen <hol...@debian.org> Closes: 376590 430889 483232 494470 775740 817914 839885 855320 908155 Changes: developers-reference (3.4.23) unstable; urgency=medium . [ Holger Wansing ] * Globally change "new maintainer" into "new member". Closes: #817914. . [ Holger Levsen ] * scope.dbk: extend: s#Debian developers#Debian developers and maintainers# * tools.dbk: - stop recommending remote signing of packages, especially using debrsign. Closes: #855320. Thanks to Daniel Kahn Gillmor. - slightly reword existing paragraph about dch and debchange. Closes: #494470. * best-pkging-practices.dbk: add another example of a multi binary source package. Closes: #430889. * l10n.dbk: drop paragraph about Debian specific manpages maintained in cvs. * developer-duties.dbk: improve paragraph about coordinating with upstreams. Closes: #908155. Thanks to Ian Jackson and Wouter Verhelst for the wording. * pkgs.dbk: - clarify the recipients of 123-submitter@b.d.o. Closes: #775740. Thanks to Josch Schauer for the wording. - don't suggest to test downgrading packages. Closes: #376590. Thanks to Justin Pryzby. - add a paragraph to the section about reintroducing packages to check and update the security tracker metadata. Closes: #839885. Thanks to Paul Wise. * beyond-pkging.dbk: mention mass-bugs for reporting bugs against many packages. Closes: #483232. Thanks to Sandro Tosi for the suggestion. * common.ent: - drop url-cvsweb. - switch five http urls to https, leaving one http url. * d/control: mark all binary packages as multiarch: foreign. * Update po4a/po/developers-reference.pot and po4a/po/*.po for the new and changed strings. * README.contributing: - renamed from README-contrib. - update instructions how to update .po files. * d/TODO: remove some ancient entries and clarify that only the BTS should be used in the long term. Checksums-Sha1: dba327e74fe2ec51e98c6bf7a72c4c8ed742a78a 2398 developers-reference_3.4.23.dsc b83a10cf5cb15bd841e2d8bcb2787d286f85199c 671300 developers-reference_3.4.23.tar.xz 4962327916996a353f4efcd7cad927c31c02fdd6 5187 developers-reference_3.4.23_source.buildinfo Checksums-Sha256: b88ea3b436d735fdaaf022c9c26c099f374f2bcf9dd89db6a2813ddfd76ce90f 2398 developers-reference_3.4.23.dsc 9abe6d60c2975bcf7cd25e930d6d0f1b0f6d150a41f41d09d3cd36115dde2477 671300 developers-reference_3.4.23.tar.xz 013c4eccc6a890552db717cd51cd555de56705dbede2c78644f821b86db14bc1 5187 developers-reference_3.4.23_source.buildinfo Files: 8c01664a739cc087e8f72d5aa3d394ef 2398 doc optional developers-reference_3.4.23.dsc fb58bbc7005b1138a860805fdb8e76da 671300 doc optional developers-reference_3.4.23.tar.xz 136e8bd2cdf29eeb8cae33094c999338 5187 doc optional developers-reference_3.4.23_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAlxpW1UACgkQCRq4Vgaa qhwoOw/8C5bb4KxQuciKRuTJIQ4ns4H76V8UFHJafR8iVym/iXIgm2xf9XRaHrz1 psRIZVroGJiyDjLy7ZaFaePgsod/aLAlGeerx2hEH1niWJDj0lItR+6UcCvDJuV+ mpWb/3565dbb78n5C/lhgg2E7D2AqGq4WcUHU8UxGH67+/oetG0yo0WJ/SMdcB6E scHXk53byImiridkPiOnCtKlHb+UMy0/Llm7MZX9/tSTj+mASo3fjy/LGoaQpzFk hdxKr+hAumAxbzTD8ohyi7dPq9fe5zNvMJ6eVgO46SNnYDwXGFTxC5yia/58m3Vm ky1e2fY7vdPEdABTXlVp+2FJ0jacjIBljdkm2C+d0571ZgjADBZ128u3D6t2xw7g hMzGNnOD7glqZyz/Nq1H4srMWNhTQf3q9D8cFdmIYfHW+7bmrGvqvL6PblghKCJg ntX4t23utp/tOWI8SiaPyKjrH2ZuK/ibJ1/X836/I+b6Js4jVaU9haLyPS2J9kMy FO8slTAtqir7CU5CDcDf7jJ8VuFpJ0lkys7NS0L5bH0eEkrvd0yP3GVq0zoM73Ib k02QETc/TRzqIjlPeMpn9zIwWV7SgWDNLCxYO8lOksHaSWv4Yt0nEcd3eDhYp5G+ OFuU8acYQiMhwpht8pDTXSMFoqdTUNzaj90FqzbXHyuU/m3Df1Q= =l6/N -----END PGP SIGNATURE-----
--- End Message ---
