Latest upstream release: 3.0.16. Current version in Fedora Rawhide: 3.0.16 URL: http://sourceforge.net/projects/ijbswa/files/ Please consult the package update guidelines before you issue an update to a stable branch: https://fedoraproject.org/wiki/Package_update_guidelines More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_Release_Monitoring
Latest upstream release: 3.0.17 Current version in Fedora Rawhide: 3.0.16 URL: http://sourceforge.net/projects/ijbswa/files/ Please consult the package update guidelines before you issue an update to a stable branch: https://fedoraproject.org/wiki/Package_update_guidelines More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_Release_Monitoring
Karsten - Could you get 3.0.17 into Fedora 15? There's a useful bug fix in it I'd like to have. Thanks ...
I built a package with the 3.0.17 source, and it's working much better. But version 3.0.17 should be pushed out.
FYI - there appears to be a non-trivial bug in 3.0.16, which is supposedly fixed in 3.0.17. http://sourceforge.net/tracker/?func=detail&atid=460288&aid=3427045&group_id=11118
I've packaged 3.0.17. The package appears to be working for me. I'll attach the RPMs and spec file. Is there any way to nominate get this into the Fedora update process, or nominate it for inclusion?
Created attachment 530895 [details] Source RPM I created
Created attachment 530896 [details] The corresponding x86_64 build
Created attachment 530897 [details] debuginfo
Created attachment 530898 [details] spec file I used (based upon specfile from 3.0.16-3 source rpm)
P.S. I want to thank Brad the Mad. His tutorial on how to edit a RPM and specfile was a handy reference to remind me how to do this (it's been a while since I last edited RPMs). http://bradthemad.org/tech/notes/patching_rpms.php
(In reply to comment #5) > I've packaged 3.0.17. The package appears to be working for me. I'll attach > the RPMs and spec file. Is there any way to nominate get this into the Fedora > update process, or nominate it for inclusion? Karsten was asking for someone to help with privoxy in Fedora, you might want to email him directly and ask about it (though he is assigned to this bug), I don't have time nor nor do I know how to actually get packages into Fedora. http://lists.fedoraproject.org/pipermail/users/2011-August/403324.html
Latest upstream release: 3.0.18 Current version in Fedora Rawhide: 3.0.16 URL: http://sourceforge.net/api/file/index/project-name/ijbswa/mtime/desc/limit/20/rss 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
Latest upstream release: 3.0.19 Current version in Fedora Rawhide: 3.0.16 URL: http://sourceforge.net/api/file/index/project-name/ijbswa/mtime/desc/limit/20/rss 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
ping!