Description of problem:/usr/sbin/racoon2: line 2: /usr/sbin/spmd: No such file or directory when attempting to start racoon2 It would seem that in the script: #!/bin/sh /usr/sbin/spmd && /usr/sbin/iked Yet, rpm -ql shows that racoon2 provides: /usr/sbin/racoon2-iked /usr/sbin/racoon2-spmd Is this perhaps meant to be: #!/bin/sh /usr/sbin/racoon2-spmd && /usr/sbin/racoon2-iked
Thanks.
This is still a problem. Pavel, if you want mean to deal with this let me know. I'm using this package for interop testing.
Hi Paul. I'm going to go through bugs for all of my IPsec-related packages as soon as I get familiar with my new tasks [in the new team]. Which version of the package did you test?
I'm using the racoon2 package on f17 but i believe i used the f19/rawhide one to fix mine. I'm more then happy to fixup the package myself, as I'm actually running and using racoon2 to test interop with libreswan. So feel free to make me co-maintainer or tell me to use provenpackager powers to fix up the package.
Please request commit access in pkgdb (feel free to use provenpackager powers in the meanwhile).
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
I guess this is a very old bug that doesn't apply any more. Can anyone confirm?
I haven't used racoon2 in sometime, as I have swapped to libreswan, so I cannot confirm if this issue still exists.
I _am_ picking this up. sorry for the delay. It is still a real bug in some branches
(In reply to Paul Wouters from comment #10) > I _am_ picking this up. sorry for the delay. It is still a real bug in some > branches Thanks. Could you please be more specific? My intention is to push updates for all branches.
Pavel: I just know the problem in the /usr/sbin/racoon2 script was still there in the latest package, and this bug was closed. So I re-opened it, as it is a confirmed bug and the package that I got installed had the bug. If you already fixed it in git and are going to push updates, that's fine. Just wait with closing the bug until the package update is out there
Could you please specify the n-v-r of the affected f20 build (non-f20 builds are welcome as well, of course)?
# yumdownloader racoon2 [...] racoon2-20100526a-18.fc18.x86_64.rpm # cat /etc/fedora-release Fedora release 20 (Heisenbug)
Thanks. By the way, I just got docker running and started a f20 image, so I was just going to post the results myself. Good then, let's update.
racoon2-20100526a-27.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/racoon2-20100526a-27.fc20
Package racoon2-20100526a-27.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 racoon2-20100526a-27.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-3608/racoon2-20100526a-27.fc20 then log in and leave karma (feedback).
Package racoon2-20100526a-28.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 racoon2-20100526a-28.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-3608/racoon2-20100526a-28.fc20 then log in and leave karma (feedback).
racoon2-20100526a-28.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.