Description of problem: There is actually no up to date package for F16. Standard boot (/etc/init.d/tinyproxy) fail and there is no systemd config file. Version-Release number of selected component (if applicable): tinyproxy-1.8.2-2.fc15.i686 How reproducible: Installing tinyproxy and try to launch. Steps to Reproduce: 1. yum install tinyproxy 2. /etc/init.d/tinyproxy Actual results: The daemon fail boot. Expected results: The daemon boot whit systemd Additional info: I propose to build a new package for F16 with the correction: - Remove file /etc/init.d/tiniyproxy + Add file : /lib/systemd/system/tinyproxy.service : [Unit] Description=Tinyproxy Web Proxy Server After=network.target [Service] PIDFile=/var/run/tinyproxy/tinyproxy.pid ExecStart=/usr/sbin/tinyproxy -c /etc/tinyproxy/tinyproxy.conf -d [Install] WantedBy=multi-user.target + Add file /etc/tmpfiles.d/tinyproxy.conf : D /var/run/tinyproxy 0750 tinyproxy tinyproxy - And after that it works with the command : chkconfig tinyproxy on
Is there any estimate for when this bug will be fixed? Will an update for F16 be pushed?
I can confirm that simply adding /etc/tmpfiles.d/tinyproxy.conf with the recommended contents above, and restarting, solved the problems of tinyproxy starting in F17.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
(In reply to comment #0) > + Add file : /lib/systemd/system/tinyproxy.service : This is not critical > + Add file /etc/tmpfiles.d/tinyproxy.conf : > > D /var/run/tinyproxy 0750 tinyproxy tinyproxy - but this is and it's still missing F17
This is still a problem with F19...
Created attachment 766021 [details] fixes to spec Will the ProvenPackager please stand up?
I'm happy to give the package to anyone, and I apologize for effectively abandoning this package. I'll make time to get this applied next week if no one steps up first.
Is this applied to F19/F20 ? Need a test ?
tinyproxy-1.8.3-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/tinyproxy-1.8.3-1.fc19
tinyproxy-1.8.3-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/tinyproxy-1.8.3-1.fc20
Package tinyproxy-1.8.3-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing tinyproxy-1.8.3-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-16165/tinyproxy-1.8.3-1.fc20 then log in and leave karma (feedback).
tinyproxy-1.8.3-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
tinyproxy-1.8.3-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.