Description of problem: Missing dependency /sbin/portrelease for spamassassin.service. Version-Release number of selected component (if applicable): spamassassin-3.4.0-12.fc21.x86_64 How reproducible: On spamassassin.service restart. Steps to Reproduce: 1. systemctl restart spamassassin.service Actual results: # systemctl status spamassassin.service ● spamassassin.service - Spamassassin daemon Loaded: loaded (/usr/lib/systemd/system/spamassassin.service; enabled) Active: active (running) since Чт 2014-12-18 18:40:09 MSK; 2s ago Process: 7173 ExecStartPre=/sbin/portrelease spamd (code=exited, status=203/EXEC) Main PID: 7176 (spamd) CGroup: /system.slice/spamassassin.service └─7176 /usr/bin/perl -T -w /usr/bin/spamd -c -m5 -H дек 18 18:40:09 arcfi-server.aetera.net systemd[7173]: Failed at step EXEC spawning /sbin/portrelease: No such file or directory Expected results: No errors on restart. Additional info: # dnf provides /sbin/portrelease portreserve-0.0.5-11.fc21.x86_64 : TCP port reservation utility
Workaround: # dnf install /sbin/portrelease
This was deliberately dropped in https://bugzilla.redhat.com/show_bug.cgi?id=1128708 because most people don't have other rpc services. The service does start ok right? Just the cosmetic failed for execpre?
(In reply to Kevin Fenzi from comment #2) > The service does start ok right? Yes, it starts and works. But there're confusing failure messages in service status and journal. So may be there's no more reason to use portreserve/portrelease? As far as I can see amavisd-new does not depend on portreserve since F21. Looks like CUPS dropped the dependency even earlier: https://lists.fedoraproject.org/pipermail/scm-commits/2011-June/621886.html
Petr: You were the one that removed the dep. What do you think here? Should we just drop the postreserve entirely? Or re-add the dep? Or somehow make it handle the case of portreserve not being installed better?
Lets drop it completely. It seems to have no usage these days.
We/I seem to have dropped the ball here. ;( Petr: Do you want to push an update for this in rawhide/f21? Or I will do so when I get time...
Kevin, I guess it is on you to push the update, since we are just watchers. If Pert believes there is no use for it, we should drop it. If someone really needs it, he can add it into his own service file.
spamassassin-3.4.0-13.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/spamassassin-3.4.0-13.fc22
spamassassin-3.4.0-13.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/spamassassin-3.4.0-13.fc21
Package spamassassin-3.4.0-13.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing spamassassin-3.4.0-13.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-5518/spamassassin-3.4.0-13.fc22 then log in and leave karma (feedback).
spamassassin-3.4.0-13.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.