Hi -
There's a bug in privoxy I'm hitting that's fixed with the latest version 3.0.17, that version has been out since last November.
How can I get the new version picked up for Fedora 15?
There's already a bug for it:
https://bugzilla.redhat.com/show_bug.cgi?id=594003
I don't know who the package maintainer is for it in Fedora (or if there is even one).
Thanks ...
-- Patrick Mansfield
On 07/30/2011 10:34 PM, Patrick wrote:
How can I get the new version picked up for Fedora 15?
There's already a bug for it:
https://bugzilla.redhat.com/show_bug.cgi?id=594003
I don't know who the package maintainer is for it in Fedora (or if there is even one).
One way to see who a maintainer is is to check the ACL[1] for the package. It seems the package is still maintained.
You should add a "ping" comment to the bug requesting a status on the update. The maintainer may be waiting to release the update for dependencies or another reason. If you don't hear back from the maintainer in the bug in a week or so, try a direct e-mail. As a last resort you can invoke the non-responsive maintainer process[2].
[1] https://admin.fedoraproject.org/pkgdb/acls/name/privoxy [2] http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers
On Sun, Jul 31, 2011 at 01:08:03AM -0500, Michael Cronenworth wrote:
On 07/30/2011 10:34 PM, Patrick wrote:
How can I get the new version picked up for Fedora 15?
There's already a bug for it:
https://bugzilla.redhat.com/show_bug.cgi?id=594003
I don't know who the package maintainer is for it in Fedora (or if there is even one).
One way to see who a maintainer is is to check the ACL[1] for the package. It seems the package is still maintained.
You should add a "ping" comment to the bug requesting a status on the update. The maintainer may be waiting to release the update for dependencies or another reason. If you don't hear back from the maintainer in the bug in a week or so, try a direct e-mail. As a last resort you can invoke the non-responsive maintainer process[2].
[1] https://admin.fedoraproject.org/pkgdb/acls/name/privoxy [2] http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers
I added a comment to the bug (back on July 31), and emailed Karsten (on Aug 13, I'm cc-ing him here too), and have gotten no responses.
In the meantime, I created an rpm for my own use with 3.0.17 privoxy source, it's working much better.
-- Patrick Mansfield
Oops ... cc-ing Karsten.
On Wed, Aug 24, 2011 at 08:49:51AM -0700, Patrick wrote:
On Sun, Jul 31, 2011 at 01:08:03AM -0500, Michael Cronenworth wrote:
On 07/30/2011 10:34 PM, Patrick wrote:
How can I get the new version picked up for Fedora 15?
There's already a bug for it:
https://bugzilla.redhat.com/show_bug.cgi?id=594003
I don't know who the package maintainer is for it in Fedora (or if there is even one).
One way to see who a maintainer is is to check the ACL[1] for the package. It seems the package is still maintained.
You should add a "ping" comment to the bug requesting a status on the update. The maintainer may be waiting to release the update for dependencies or another reason. If you don't hear back from the maintainer in the bug in a week or so, try a direct e-mail. As a last resort you can invoke the non-responsive maintainer process[2].
[1] https://admin.fedoraproject.org/pkgdb/acls/name/privoxy [2] http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers
I added a comment to the bug (back on July 31), and emailed Karsten (on Aug 13, I'm cc-ing him here too), and have gotten no responses.
In the meantime, I created an rpm for my own use with 3.0.17 privoxy source, it's working much better.
-- Patrick Mansfield
Am 24.08.2011 17:51, schrieb Patrick:
Oops ... cc-ing Karsten.
On Wed, Aug 24, 2011 at 08:49:51AM -0700, Patrick wrote:
On Sun, Jul 31, 2011 at 01:08:03AM -0500, Michael Cronenworth wrote:
On 07/30/2011 10:34 PM, Patrick wrote:
How can I get the new version picked up for Fedora 15?
There's already a bug for it:
https://bugzilla.redhat.com/show_bug.cgi?id=594003
I don't know who the package maintainer is for it in Fedora (or if there is even one).
One way to see who a maintainer is is to check the ACL[1] for the package. It seems the package is still maintained.
You should add a "ping" comment to the bug requesting a status on the update. The maintainer may be waiting to release the update for dependencies or another reason. If you don't hear back from the maintainer in the bug in a week or so, try a direct e-mail. As a last resort you can invoke the non-responsive maintainer process[2].
[1] https://admin.fedoraproject.org/pkgdb/acls/name/privoxy [2] http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers
I added a comment to the bug (back on July 31), and emailed Karsten (on Aug 13, I'm cc-ing him here too), and have gotten no responses.
In the meantime, I created an rpm for my own use with 3.0.17 privoxy source, it's working much better.
-- Patrick Mansfield
I saw your comment, but I'm currently quite busy with secondary arch. I'f you'd like to either take over or co-maintain privoxy, I'll orphan the package or approve commit access for you.
Karsten