Control: reopen -1 Control: severity -1 important Hi Antoine!
Thank you for your quick response! On Tue, May 31, 2022 at 9:58 AM Antoine Beaupré <anar...@debian.org> wrote: > > Hum. Now I'm a little confused: why did you do this? > > * Add diversion for /usr/bin/gh to allow concurrent install with gitsome > and remove Conflicts with gitsome. This is inspired by the conflict > resolution between the moreutils and parallel packages where both > contain /usr/bin/parallel. See discussions in #749355. This is an idea that has been brewing in my mind some weeks ever since I came to realize Debian has two "parallel" programs while working on <https://github.com/OpenDRR/earthquake-scenarios/pull/61>, and thought to myself, if moreutils and (GNU) parallel can do it, why can't gitsome and (GitHub's) gh? But I was too busy with work, and also not sure how to break the file conflict deadlock in #1005858 (especially with the manual block to both packages), so I didn't act on it. Many thanks to you for getting us out of that embarrassing situation! So, as I was dealing with this new bug that you opened, my old idea came back to me again, I decided to give it a try, for better or for worse. The changelog is a reflection of the Git commits that I made in that order... <grin> > This seems like it's the opposite of what I was suggesting in the bug > report (#1011545). And you even refer to that bug report in the > changelog: > > * Limit "Conflicts: gitsome" to older (<< 0.8.0+ds-7.1) versions. > Thanks to Antoine Beaupre for the suggestion, and for resolving the > file conflict with gitsome (#1005858) so amicably! (Closes: #1011545) > > What actually happened, from what I can tell, is that you just removed > the Conflicts... I don't think that's the right resolution here: gitsome > has been fixed, in unstable, and gh doesn't need to go around with fancy > diversion stuff, because we're *precisely* not in a situation like > moreutils and parallel... Thank you for clarifying to me that it is a different situation than moreutils and parallel. >From my understanding of the gitsome, the "gitsome" command itself is mostly just a wrapper that calls xonsh, and gitsome's main functionalities are actually in the "/usr/bin/gh" Python executable, so perhaps removing /usr/bin/gh altogether in some sense cripples the gitsome package, and a rename to /usr/bin/gh.gitsome or something else would be more appropriate. That said, I now agree with you that renaming gitsome's /usr/bin/gh via dpkg-divert from GitHub CLI gh package is not the right way to go, particularly because the /usr/bin/gh meaning different things depending on which packages are installed (just gitsome or both gitsome and gh) can be very confusing.) > Could this change be reverted? Yes, most definitely! I will do it ASAP. After that, I will probably try to work on the gitsome package too and install its gh as /usr/bin/gh.gitsome and hopefully get its command-line completion to work with the name change, but that's unrelated to this particular bug report and to GitHub CLI gh. Let's keep this package clean and free of the fancy and confusing diversion stuff. :-) Thanks again for writing to me and put some common sense back into me! Cheers, Anthony Fok > -- > When I came back to the United States, I decided that if you could use > propaganda for war, you could certainly use it for peace. And > "propaganda" got to be a bad word because of the Germans using it, so > what I did was to try and find some other words so we found the words > "public relations". - Edward Bernays > > > > > > ---------- Forwarded message ---------- > From: Debian Bug Tracking System <ow...@bugs.debian.org> > To: Antoine Beaupre <anar...@debian.org> > Cc: > Bcc: > Date: Tue, 31 May 2022 15:51:05 +0000 > Subject: Bug#1011545 closed by Debian FTP Masters > <ftpmas...@ftp-master.debian.org> (reply to Anthony Fok <f...@debian.org>) > (Bug#1011545: fixed in gh 2.4.0+dfsg1-3) > This is an automatic notification regarding your Bug report > which was filed against the gh package: > > #1011545: please version the Conflicts: with gitsome > > It has been closed by Debian FTP Masters <ftpmas...@ftp-master.debian.org> > (reply to Anthony Fok <f...@debian.org>). > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Debian FTP Masters > <ftpmas...@ftp-master.debian.org> (reply to Anthony Fok <f...@debian.org>) by > replying to this email. > > > -- > 1011545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011545 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > > ---------- Forwarded message ---------- > From: Debian FTP Masters <ftpmas...@ftp-master.debian.org> > To: 1011545-cl...@bugs.debian.org > Cc: > Bcc: > Date: Tue, 31 May 2022 15:49:21 +0000 > Subject: Bug#1011545: fixed in gh 2.4.0+dfsg1-3 > Source: gh > Source-Version: 2.4.0+dfsg1-3 > Done: Anthony Fok <f...@debian.org> > > We believe that the bug you reported is fixed in the latest version of > gh, 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 1011...@bugs.debian.org, > and the maintainer will reopen the bug report if appropriate. > > Debian distribution maintenance software > pp. > Anthony Fok <f...@debian.org> (supplier of updated gh 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: SHA256 > > Format: 1.8 > Date: Tue, 31 May 2022 01:58:33 -0600 > Source: gh > Architecture: source > Version: 2.4.0+dfsg1-3 > Distribution: unstable > Urgency: medium > Maintainer: Debian Go Packaging Team <team+pkg...@tracker.debian.org> > Changed-By: Anthony Fok <f...@debian.org> > Closes: 1008761 1011545 > Changes: > gh (2.4.0+dfsg1-3) unstable; urgency=medium > . > * Limit "Conflicts: gitsome" to older (<< 0.8.0+ds-7.1) versions. > Thanks to Antoine Beaupre for the suggestion, and for resolving the > file conflict with gitsome (#1005858) so amicably! (Closes: #1011545) > * Change default editor from nano to /usr/bin/editor as per Debian Policy > §11.4. Thanks to Jakub Wilk for the bug report. (Closes: #1008761) > * Rename "Build-Using" field to "Static-Build-Using" in debian/control > * Add diversion for /usr/bin/gh to allow concurrent install with gitsome > and remove Conflicts with gitsome. This is inspired by the conflict > resolution between the moreutils and parallel packages where both > contain /usr/bin/parallel. See discussions in #749355. > Checksums-Sha1: > 1092d879dbffd7d271b7fea3191a511b8b721086 3914 gh_2.4.0+dfsg1-3.dsc > c563c649ee6d53af12f8f0b3aa96ed7ffd38e449 940048 > gh_2.4.0+dfsg1-3.debian.tar.xz > 22ce340f153035ba9c31b4caee0303686279d6d2 12875 > gh_2.4.0+dfsg1-3_amd64.buildinfo > Checksums-Sha256: > 80c5e5b02c9c08368844d664be37d0efa8dd3042a94aa9fec21245ae8bc7bf19 3914 > gh_2.4.0+dfsg1-3.dsc > 73bc2982038e0591645b097206394ce0c9cf8ec76bea81bac7ecc3f98d3b04d6 940048 > gh_2.4.0+dfsg1-3.debian.tar.xz > 338bbbcbb80aedd05607ae6c2a7c8f5e93bb8d74be6e713b3329d6c71b158725 12875 > gh_2.4.0+dfsg1-3_amd64.buildinfo > Files: > faf8dbe284cccd7fc02d4c4d749450ef 3914 golang optional gh_2.4.0+dfsg1-3.dsc > 28794e83d36e6b935976254736cdfcbd 940048 golang optional > gh_2.4.0+dfsg1-3.debian.tar.xz > 7e1b70f938b6d7f4f0fe3ccdc86cb1ae 12875 golang optional > gh_2.4.0+dfsg1-3_amd64.buildinfo > > -----BEGIN PGP SIGNATURE----- > > iQJEBAEBCAAuFiEEFCQhsZrUqVmW+VBy6iUAtBLFms8FAmKWNO4QHGZva2FAZGVi > aWFuLm9yZwAKCRDqJQC0EsWaz/xAD/9RtxjOETIInSGTEbCNDE4U/k/F2y5T11Ki > zUMk0bF6O8zXMwWGsDI8zo35WIMA8O1SHQj2tD/Odr1gDs6CN4YZE7fMCnRBxYWe > HPgkPv+rUIHnsAdvQI1ER+grqb8uytvnd+baBIolr/7z+Br2kKAHFN5Qst7l3Et6 > QOwa4uPbPVc6iMI6l0ETK6GSqGhRsOkmU39xnqPeKBU6qreqnYTJ5SOwLFRq6xaJ > vdPq4jlSuniodv2SjEcNgB4bPbjOvU83/4fm2GDMGzJUsM/wEe6dBqaxQ1Yuuo9U > 69o1aoL7vq2rStm3Xd5l3q8SMYv1m3g/wji2QzqwAoecFwrC9tYwcOjQBxIoCHIb > Rv+x9QG+J9LUkVAGML7fhpl319ciiyLKw/P7vr2koUTUZSivpVLclf5iE+QxTZ3B > mfprVAtSHsMoqC/7r6H+C4jxa478J+GJ7vHs5byXoTplV0kUagESLhIFfydll5h9 > 72vhgFvFwQNmcZkQDADbKNs6nNXdd1x2wNm7EIlNSNDUm0Pcs6qxyvzF0U8ehbUd > v7ruZeNaZNX4sihCNQ4lXXzUfisnLa83AffFK7E2d3/ST7GuvAbQRRy9W8EBh2yB > 4La7biR6p3WTW5yWA9U8Y/ARV0LmZG7BOO1hEYWOHsTVknjQhqwODDFcz241cd1o > UvseDk8lrw== > =93Ze > -----END PGP SIGNATURE----- > > > ---------- Forwarded message ---------- > From: Antoine Beaupre <anar...@debian.org> > To: Debian Bug Tracking System <sub...@bugs.debian.org> > Cc: > Bcc: > Date: Tue, 24 May 2022 15:46:39 -0400 > Subject: please version the Conflicts: with gitsome > Package: gh > Version: 2.4.0+dfsg1-2 > Severity: serious > > I have fixed gitsome so that it doesn't ship a /usr/bin/gh binary in > gitsome/0.8.0+ds-7.1 (which closed #1005858). Please fix the > Conflicts: so that it is versioned << 0.8.0+ds-7.1. > > This is marked as "serious" because I believe that conflicting with an > unrelated package is a policy violation. I understand this is somewhat > open to interpretation, but since this package has been added to the > blocking hints anyways, I figured it was better to file an RC bug, > remove the hint, and fix this, than keeping things kind of hidden the > way they are now. :) > > -- System Information: > Debian Release: 11.3 > APT prefers stable-security > APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, > 'stable'), (1, 'unstable'), (1, 'testing') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.10.0-14-amd64 (SMP w/4 CPU threads) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, > TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE not > set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages gh depends on: > ii libc6 2.31-13+deb11u3 > > gh recommends no packages. > > gh suggests no packages.
