Description of problem: Version 0.4 of stapler is available: https://github.com/hellerbarde/stapler/archive/0.4.tar.gz Version-Release number of selected component (if applicable): 0.3.3 (unofficial?) How reproducible: yes Steps to Reproduce: 1. dnf install pdf-stapler 2. 3. Actual results: Old version. Expected results: Current version. Additional info: One and only change is official switch to PyPDF2 (instead of PyPDF). https://github.com/hellerbarde/stapler/commit/cdf1fd3d28facf92c97895fe623b4cb2e20dd5ef
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
Ping? Any news here? Latest rebuild from releng from 2018-02-08 FTBFS.
Another friendly reminder. What's the state here?
Sorry for the delay in getting to this but I was hoping that some of the issues would be fixed upstream. Is there really anything new in 0.4? Mysteriously, the version on PyPi is down to 0.3.2 and the file at https://github.com/hellerbarde/stapler/archive/0.4.tar.gz is wrongly archived, in that it does not contain the setup.py. Btw, I would not mind having a co-maintainer.
(In reply to Ranjan Maitra from comment #4) > Sorry for the delay in getting to this but I was hoping that some of the > issues would be fixed upstream. No problem. Most of us do the hard work in our spare time, so we shouldn't expect anything. :-) Pinging is generally recommended to see if package maintainers are still active. > Is there really anything new in 0.4? Additional info: One and only change is official switch to PyPDF2 (instead of PyPDF). https://github.com/hellerbarde/stapler/commit/cdf1fd3d28facf92c97895fe623b4cb2e20dd5ef > Mysteriously, the version on PyPi is > down to 0.3.2 and the file at > https://github.com/hellerbarde/stapler/archive/0.4.tar.gz is wrongly > archived, in that it does not contain the setup.py. I'd suggest to report this as an issue to upstream. > Btw, I would not mind having a co-maintainer. Would a pull request help, at least?
Btw, I noticed that you already have commit privileges. I think that you have had it for a while.
(In reply to Ranjan Maitra from comment #6) > Btw, I noticed that you already have commit privileges. I think that you > have had it for a while. Result of some experiments done with python3 but pagure doesn't tell about any commit. Maybe something imported from those PkgDB times. Anyways, I'm going to build a new version when there's some free time slot. Thanks.
Well, there's still no official support from upstream for Python3.
Currently no time available for me to continue with this.
At least, upstream is aware of the python3 request. https://github.com/hellerbarde/stapler/pull/20
*** Bug 1738053 has been marked as a duplicate of this bug. ***
Merged by upstream. https://github.com/hellerbarde/stapler/commit/ee85df8ef0629197cbc52d915167c6c4787b8964
To avoid a removal of the package, could someone apply the patch from upstream?
Upstream merged the PR. https://github.com/hellerbarde/stapler/pull/55/files
Created attachment 1638981 [details] Patch for python3 https://patch-diff.githubusercontent.com/raw/hellerbarde/stapler/pull/55.patch
Reassing as recent commits indicate.
Ping. Meanwhile version 1.0.0 is released. https://github.com/hellerbarde/stapler/releases/tag/1.0.0
*** Bug 1804545 has been marked as a duplicate of this bug. ***
Current version is 1.0.0-0.7.20191215git8753251.fc34, is this different from the one in #17?
(In reply to Ranjan Maitra from comment #19) > Current version is 1.0.0-0.7.20191215git8753251.fc34, is this different from > the one in #17? yes, see https://github.com/hellerbarde/stapler/commit/d3f091ab0e50cf7dcce69ac722908cdc83779a7b
Propably then 1.0.0-1.fc36 etc.