Latest upstream release: 0.4 Current version/release in rawhide: 0.3.3-6.fc24 URL: https://github.com/hellerbarde/stapler Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.
Failed to kick off scratch build. cmd: spectool -g /var/tmp/thn-zHmpOw/pdf-stapler.spec return code: 22 stdout: Getting https://pypi.python.org/packages/source/s/stapler/stapler-0.4.tar.gz to ./stapler-0.4.tar.gz stderr: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (22) The requested URL returned error: 404 Not Found
Ping? Any news here? I could help with the package as co-maintainer, please approve ACL in PkgDB.
As you see in the Upstream Release Monitoring, the package upstream can not be found. I am not sure where to find this updated package. Please provide correct and updated links.
You should let monitor for new releases on GitHub. Maybe the tarball got removed from PyPI afterwards. https://github.com/hellerbarde/stapler/archive/0.4.tar.gz
Funny, I was told early on when I packaged pdf-stapler that the github release was not valid for use and another upstream source was merited. I will find out and repackage as needed.
You were misinformed then ;)
(In reply to Raphael Groner from comment #2) > Ping? Any news here? I could help with the package as co-maintainer, please > approve ACL in PkgDB. Btw, I am happy to include you as co-maintainer. Perhaps best for the package. Let me know what has to be done?
Please approve my request in PkgDB. https://admin.fedoraproject.org/pkgdb/acl/pending/
Approved. Btw, you may want to also package for F23 since it is not going to be EOL for a while. Separately, have you considered co-maintaining other packages? Sylpheed needs an update for the past five months but there has been no movement there. It perhaps needs a new co-maintainer.
Can you explain why 0.4 is older than 0.3.2? > on 20 Sep 2015 0.3.2 ce2df8a > on 13 Feb 2014 0.4 02d8086 Hash 02d8086 is not found in commit history, neither for master nor python3port branch. Maybe upstrem generated release tarball by accident and we can close this bug as invalid?
(In reply to Raphael Groner from comment #10) > Can you explain why 0.4 is older than 0.3.2? > > > on 20 Sep 2015 0.3.2 ce2df8a > > on 13 Feb 2014 0.4 02d8086 No idea. Where does 0.4 come from? From upstream? One of the issues with stapler is that there was a fork which moved further ahead faster and that fork is now coming back into stapler. (This what I understood at the time.)
I got an e-mail that pdf-stapler has a broken dependency "and will be retired on 2016-05-31 (Final Freeze for Fedora 24) unless someone fixes them." I persume that this has to do with python-PDF2. Any knowledge of what is wrong with the dependency? I think that that is on F24 updates-tesing https://bugzilla.redhat.com/show_bug.cgi?id=1337559 so this will go away perhaps? Were you able to package 0.4 for pdf-stapler? We need to do this for F23 also and also EPEL 7. (Maybe a new package there.)
The dependency problem should be fixed when https://bodhi.fedoraproject.org/updates/FEDORA-2016-55f32f0ba2 goes to stable. I just requested pushing to stable, so it should be fixed tonight.
(In reply to Ranjan Maitra from comment #11) > (In reply to Raphael Groner from comment #10) > > Can you explain why 0.4 is older than 0.3.2? > > > > > on 20 Sep 2015 0.3.2 ce2df8a > > > on 13 Feb 2014 0.4 02d8086 > > No idea. Where does 0.4 come from? From upstream? One of the issues with > stapler is that there was a fork which moved further ahead faster and that > fork is now coming back into stapler. (This what I understood at the time.) See https://github.com/hellerbarde/stapler/releases What about 0.3.3 as in the changelog? But no 0.4 there and no 0.3.3 in releases. https://github.com/hellerbarde/stapler#change-log-sorta There's also some effort with a port to python3. https://github.com/hellerbarde/stapler/pull/20 Maybe we should just close this bug and wait for upstream.
Similar to my point earlier. I will close the bug and wait for upstream. Btw, upstream means writing to Philip Stark if you are curious about this anomaly.
Agreed. It's confusing with current releases at upstream.
Changed Anitya to monitor on PyPI.