Your message dated Fri, 06 Sep 2019 23:19:17 +0000 with message-id <[email protected]> and subject line Bug#935802: fixed in dgit 9.8 has caused the Debian Bug report #935802, regarding want to detect need to bump version 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 [email protected] immediately.) -- 935802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935802 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: dgit Version: 9.7 Hi. IOhannes, I think you won't mind me copying this private mail of yours to the bug system. IOhannes m zmölnig (Debian/GNU) writes ("Re: dgit with backports"): > On 8/22/19 1:58 PM, IOhannes m zmölnig (Debian/GNU) wrote: > > it refuses with > >> package appears to be new in this suite; if this is intentional, > >> use --new > > > > is this normal? > > so figuring that my package is indeed not yet in "buster-backports" and > thus might be considered 'new in this suite', i went ahead and did a > "dgit -N push-source" and everything went fine so far. > > so i guess the solution wsa that simple. > > however: when interacting with the repository i tend to be overcareful > (at least, if i don't forget to), and "dgit" is a tool in which my > confidence has yet to grow (not because it has shown to be > untrustworthy, but because it is new for me). > > it might be a good idea to mention "--new" in dgit-maint-bpo(7), as when > working with the "normal" suites (unstable->testing->stable) the package > is usually only "new" at special times (e.g. before the first upload; or > because a package has dropped out of the suite). whereas with backports > you get a new and empty suite with every Debian release. What you say makes sense. I think this is a fine suggestion. When uploading to experimental, needing --new is quite common too, because there often isn't a version in experimental. I'm not sure if this needs to be mentioned anywhere. Out of interest, did you read the description of --new in dgit(1) ? I ask because I want to know if improving it would have helped. I just reread it myself and it definitely should be more reassuring. Thanks, Ian.
--- End Message ---
--- Begin Message ---Source: dgit Source-Version: 9.8 We believe that the bug you reported is fixed in the latest version of dgit, 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 [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ian Jackson <[email protected]> (supplier of updated dgit 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 [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Fri, 06 Sep 2019 23:42:15 +0100 Source: dgit Binary: dgit git-debrebase git-debpush dgit-infrastructure Architecture: source Version: 9.8 Distribution: unstable Urgency: medium Maintainer: Ian Jackson <[email protected]> Changed-By: Ian Jackson <[email protected]> Description: dgit - git interoperability with the Debian archive dgit-infrastructure - dgit server backend infrastructure git-debpush - client script for git pushing to Debian-style archives git-debrebase - rebasing git workflow tool for Debian packaging Closes: 931212 934807 935802 935874 939280 939504 939564 Changes: dgit (9.8) unstable; urgency=medium . dgit, important bugfixes for bugs introduced in 9.6: * Once again cope with archive skew. Closes:#935874. [Initial report from Colin Watson] * Follow http[s] redirects again. Closes:#939564. . dgit, useful new behaviours and fixes: * Use distro-info-data to resolve unknown suites. Closes:#931212. [Suggestion from Simon McVittie] * Try to warn about misplacement of dgit options. Closes:#934807. [Useability report from Félix Sipma] * Fail early when the archive/ tag already exists, ie when version needs to be not reused. Closes:#935802. [Useability report from IOhannes m zmölnig] * Do not mistakely reject .asc and .sig files with push-source -C. Closes:#939280. [Report from Simon McVittie] . docs: * dgit-maint-{merge,debrebase}(7): Suggest git fetch --all --tags as it handles tags better. [Sean Whitton] Closes:#939504. * git-debrebase(5): Tiny typo fix. * dgit(1): Some semantic linefeeds (no change to rendered output) . Supporting changes: * test suite: New test for http mirror and archive skew * test suite: Test already-tagged check * test suite: Add --force-reusing-version to many tests as now needed * Dgit: Minor refactoring of a regexp. Checksums-Sha1: 9e04a99e734a0e23dd5a8d9a8c90c3434019b1da 1821 dgit_9.8.dsc 8ddb3136e6a59dbdc89a742c0644ab530d9f1d92 695751 dgit_9.8.tar.gz Checksums-Sha256: 3166b8e7f5b6b99d729c2b491c616b3e4a420e0e5420fbb96df43373db1ad36a 1821 dgit_9.8.dsc e85dd18b28c6c8dbb355c8d21312639810917f60e5d53c35fb1ec6e44072c2c9 695751 dgit_9.8.tar.gz Files: f78e30a02fb25d31d3652018a0aa3c8f 1821 devel optional dgit_9.8.dsc 692ed56f1a2a809781a46c367ae8b402 695751 devel optional dgit_9.8.tar.gz -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEVZrkbC1rbTJl58uh4+M5I0i1DTkFAl1y5K8ACgkQ4+M5I0i1 DTlj0Qf9E/SGIIkN+OBs6EFtkd+9NhVRKqPdW6igCDFstDcMMqA5cSPjzYXVHr+M FOFshta6NVeCqlxLTyUZQ272hWrJtncBbZm648QfQQF3HWbXG3GHs7BhENL35FTB 2aOm0q6/UHTBv7nZoc5Sl409fd9ak8Z1KiDSLk8B5T8xH431s23GsqX8f+DYGh+F ZFGtESZ0M67nLmVFnhk8dJfBFarVPcY2HfGnf/LYLKkZCXFoOYUtnJ8kRiKsMXQR DHGncnd3MeBUHCaUajPsb03qfU2NtTYj6oFT5evSUCAc5uVbxyDvwR5KDxz5MYag 1vo8+Fa3H3AEBqb4ifHzCX/ilQqt8w== =Amue -----END PGP SIGNATURE-----
--- End Message ---
