Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: -------------------------------------------------------------------------------- [...] Install main build dependencies (apt-based resolver) ---------------------------------------------------- Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-main-dummy : Depends: ash but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. E: Package installation failed Not removing build depends: cloned chroot in use-------------------------------------------------------------------------------- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202406/ About the archive rebuild: The build was made on virtual machines of type m6a.large and r6a.large from AWS, using sbuild and a reduced chroot with only build-essential packages. If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Note: This happens because ash (which used to be a dummy package depending on dash) no longer exists. The trivial fix is to build-depend on dash instead, as in the attached patch. Thanks.
Hi, I also noticed the reverse build dependency of shc on ash in Ubuntu (see: https://bugs.launchpad.net/debian/+source/shc/+bug/2073141). Even though this technically works, test/ttest.sh fails the build, because of failing test cases for /bin/ash, which is to be expected when it no longer gets installed. I submitted a fix for - Debian (https://salsa.debian.org/debian/shc/-/merge_requests/3) and - Upstream (https://github.com/neurobin/shc/pull/167) Best regards, Dominik P.S.: This is the first time that I use the Debian BTS E-Mail interface. Feel free to educate me if I did something wrong.
Hi All, Giving some content why this shc package ends up like this -- Eriberto Mota <eriberto@debian.org> is the only one that I know of that uses this Debian package while I was maintaining the package. He doesn't have much time to maintain it, yet he blocked me from maintaining it either, claiming that I "don't know how to package", whereas I've been packaging shc for nearly 10 years, and also have about a dozen of other Debian packages that I maintain. This is not the first time that "shc is marked for autoremoval from testing". Last time, I made some noise and the problem was fixed. This time, I planned to do so at first but then decided to wait and see what would happen. As I had suspected, things fell through the cracks under Eriberto Mota' care after he blocked me. While I've been packaging shc for nearly 10 years, the only time that Eriberto Mota laid his hand on shc, he did it without a single communication with me, the package maintainer. Not only he did the NMU without any prior notification, he even messed up with the shc gitlab repo, hiding all my efforts of package maintenance, leaving the impression in the master branch that he is the only hero in package maintenance, then walked away, leaving the package is such a lingering stage. He has successfully ruin the shc packaging. I lost a powerful machine I used to use for Debian build, and my DD request was blocked by Eriberto Mota despite that I've been managing Debian packages for over a decade. I.e., now I don't even have a proper build machine to start with. Lastly, let me end my message with a quote from Debian Faq https://wiki.debian.org/DebianMentorsFaq#Packaging might benefit from a new maintainer (you!) bring it to d-mentors or the debian-qa mailing list with your reasoning, and someone will try and help you out. Please Note: Don't go e-mailing maintainers with e-mails like "Your package looks unmaintained, I'm going to hijack your package". It helps nobody, and ensures that you will have at least one very unhappy Debian developer. Does Eriberto Mota not know such FAQ, or he doesn't give a damn?
Hi All, Giving some content why this shc package ends up like this -- Eriberto Mota <eriberto@debian.org> is the only one that I know of that uses this Debian package while I was maintaining the package. He doesn't have much time to maintain it, yet he blocked me from maintaining it either, claiming that I "don't know how to package", whereas I've been packaging shc for nearly 10 years, and also have about a dozen of other Debian packages that I maintain. This is not the first time that "shc is marked for autoremoval from testing". Last time, I made some noise and the problem was fixed. This time, I planned to do so at first but then decided to wait and see what would happen. As I had suspected, things fell through the cracks under Eriberto Mota' care after he blocked me. While I've been packaging shc for nearly 10 years, the only time that Eriberto Mota laid his hand on shc, he did it without a single communication with me, the package maintainer. Not only he did the NMU without any prior notification, he even messed up with the shc gitlab repo, hiding all my efforts of package maintenance, leaving the impression in the master branch that he is the only hero in package maintenance, then walked away, leaving the package is such a lingering stage. He has successfully ruin the shc packaging. I lost a powerful machine I used to use for Debian build, and my DD request was blocked by Eriberto Mota despite that I've been managing Debian packages for over a decade. I.e., now I don't even have a proper build machine to start with. Lastly, let me end my message with a quote from Debian Faq https://wiki.debian.org/DebianMentorsFaq#Packaging might benefit from a new maintainer (you!) bring it to d-mentors or the debian-qa mailing list with your reasoning, and someone will try and help you out. Please Note: Don't go e-mailing maintainers with e-mails like "Your package looks unmaintained, I'm going to hijack your package". It helps nobody, and ensures that you will have at least one very unhappy Debian developer. Does Eriberto Mota not know such FAQ, or he doesn't give a damn?
As this is a RC issue that has kept the package from entering testing (which made it not release with trixie) and it is now 1 year that the maintainer claimed not to fix it I am going to NMU it.
We believe that the bug you reported is fixed in the latest version of
shc, 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 1072469@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dominik Viererbe <dominik.viererbe@canonical.com> (supplier of updated shc 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 ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Tue, 16 Jul 2024 14:47:28 +0300
Source: shc
Architecture: source
Version: 4.0.3-1.1
Distribution: unstable
Urgency: medium
Maintainer: Tong Sun <suntong001@users.sourceforge.net>
Changed-By: Dominik Viererbe <dominik.viererbe@canonical.com>
Closes: 1072469
Changes:
shc (4.0.3-1.1) unstable; urgency=medium
.
* Remove ash dependency (Closes: #1072469):
- debian/control: Replace ash Build-Depends with dash
- debian/patches/001_remove-ash.patch: Remove ash dependencies
.
[ Bastian Germann ]
* debian/patches/010_fix-rc-path.patch: Drop unnecessary patch (after UsrMerge)
Checksums-Sha1:
1085625bd3a64db1d82bfda71d2cf0d11f679c1b 1699 shc_4.0.3-1.1.dsc
1041a4520e0cf3c6db1aeeb1079ee4ac1a3c81e5 4256 shc_4.0.3-1.1.debian.tar.xz
68bcf13387f3c758968ec5f8cecb9f721333f6a3 5680 shc_4.0.3-1.1_source.buildinfo
Checksums-Sha256:
43e2127079fa54699ce889619ee3179528c092dea1dc2632482164e3407a4cae 1699 shc_4.0.3-1.1.dsc
10641dad2de97778fa6e9220416334ac45205a84ba0cb9b1cc4c15d5a7a1e07f 4256 shc_4.0.3-1.1.debian.tar.xz
b9cbe01a5b0e9992ea5cbd9a5165707a2ef1011be3b081a91ac382318227b69c 5680 shc_4.0.3-1.1_source.buildinfo
Files:
3952e463bea3702e2c96ad333aa2e58f 1699 devel optional shc_4.0.3-1.1.dsc
0f422724b07fdc40e46ae5a3a7bba8ef 4256 devel optional shc_4.0.3-1.1.debian.tar.xz
136ae2f014a918111d5f102b03481708 5680 devel optional shc_4.0.3-1.1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmqFosUQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFOsFC/4i0Eec7hQ7eoSFHYw80jtw3unDtKCTQ/er
Ky9vX/WPWBPxLxoUnZ4IcUMdeO6lYKLhV8sQFDPbL8BzRJUIXL6De21/e2/W5Hfr
OTX61YHN4p6326JNE7qcKLDNxJQQlgY6S5toqFeR7rMT9/VjhNMljkG1y44GJGxk
jIqNzHjp2CRCVAbs3ZDU4B3kPshUGf32IbBV5n2G5er0AHw09Sa0EKvkEQ1itvUT
G6vhfwjupfOKMxmz57hoZ/UqfWrknN6JkQimVRZ/8IN7zqwpwQVdmqowCHouC2wY
qBNXznB4dJORiiWQvN4bIhbyKetxnG81Ih4cLshAQHngzkzWcdOpqbksczLXp4MW
jYVfknDFmaqbc5sHHRwwcxrVo0fmdZUbSWOVGwG4Bpzjf8eLYO5fLF8IGKz2ptkq
x5lir+OYEQWn/MhZDIrcOXXm5sqpMajPX+e/My7BJcFYoRgbschiDEdQ6/lDOSi+
6ioxn3jcJ+uenU9i8Rg6KX6uEadGqhc=
=Afvd
-----END PGP SIGNATURE-----
Thank you Dominik & Bastian.