Fedora Account System
Red Hat Associate
Red Hat Customer
Build of recent version of pdf-stapler (official 1.0 with latest patches) fails to build. See attached logs. Reproducible: Always Steps to Reproduce: 1. fedpkg scratch-build 2. 3. Actual Results: FTBFS Expected Results: build success.
Created attachment 2129096 [details] root.log
Created attachment 2129097 [details] build.log
Created attachment 2129098 [details] patch to bump spec file to official 1.0
*** Bug 1518829 has been marked as a duplicate of this bug. ***
(In reply to Raphael Groner from comment #3) > Created attachment 2129098 [details] > patch to bump spec file to official 1.0 Just a note: The official 1.0.0 release is commit d3f091ab0e50cf7dcce69ac722908cdc83779a7b, see: https://github.com/hellerbarde/stapler/releases/tag/1.0.0 Also, perhaps it would make sense to bump to the latest commit in the master branch which is 382f1edc62296e071093a5419811a2fca9d78d93: https://github.com/hellerbarde/stapler/compare/1.0.0...master Unfortunately, the upstream appears to be unmaintained since Mar 2022: https://github.com/hellerbarde/stapler/issues/99
Thanks for status update. Maybe worth to orphan this package or anyone else should take responsibility. Not sure what available fork to choose instead as upstream, current development seems somehow confusing. https://github.com/hellerbarde/stapler/network
(In reply to Raphael Groner from comment #6) > Thanks for status update. Maybe worth to orphan this package or anyone else > should take responsibility. Not sure what available fork to choose instead > as upstream, current development seems somehow confusing. > https://github.com/hellerbarde/stapler/network I don't see any "alive" successor in terms of forks. Given the situation, I think it would make sense to retire pdf-stapler.
I packaged this long ago. It was my first package for Fedora. Is there any alternative we could point users to?
(In reply to Ranjan Maitra from comment #8) > I packaged this long ago. It was my first package for Fedora. I know it's probably hard to let go, but I think retiring it for rawhide/Fedora 45+ is the best way forward here. It should be relatively straightforward, just use the 'fedpkg retire' command. See https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/ for the current guidelines. > Is there any alternative we could point users to? I think there are many maintained options. I will mention 2: - pdfly (https://github.com/py-pdf/pdfly) - a pure-Python CLI built directly on pypdf - not (yet) packaged for Fedora - a bit different command syntax than pdf-stapler - qpdf (https://github.com/qpdf/qpdf) - written in C++ - started in 2008, still active, very robust - packaged in Fedora
(In reply to Tadej Janež from comment #9) > (In reply to Ranjan Maitra from comment #8) > > I packaged this long ago. It was my first package for Fedora. > > I know it's probably hard to let go, but I think retiring it for > rawhide/Fedora 45+ is the best way forward here. > > It should be relatively straightforward, just use the 'fedpkg retire' > command. > @itsme_410, do you need help retiring pdf-stapler?
@itsme_410, a nudge to proceed with retiring pdf-stapler.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 45 development cycle. Changing version to 45.
https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/ According to src.fp.org the maintainer is actually aarem.