Hi All, Giving some content why this shc package ends up like this --
Eriberto Mota <[email protected]> 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 > if there's a program you use which you think is looking a bit shabby and 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? On Sun, Jun 2, 2024 at 9:46 AM Santiago Vila <[email protected]> wrote: > Package: src:shc > Version: 4.0.3-1 > Severity: serious > Tags: ftbfs patch > > 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.
