Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#39628 - [dante] Removal of /etc/conf.d/sockd.conf in 1.4.0-2 breaks service file
Attached to Project:
Community Packages
Opened by Federico Quagliata (quaqo) - Wednesday, 26 March 2014, 09:00 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 26 March 2014, 15:36 GMT
Opened by Federico Quagliata (quaqo) - Wednesday, 26 March 2014, 09:00 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 26 March 2014, 15:36 GMT
|
DetailsIn 1.4.0-1 during the build() the PKGBUILD added the line:
echo 'SOCKD_OPTS="-D"' >${pkgdir}/etc/conf.d/sockd.conf Thus creating the file. In 1.4.0-2 this is not the case anymore, so systemctl complains about it because EnvironmentFile=/etc/conf.d/sockd.conf is listed in /usr/lib/systemd/system/sockd.service, but the file doesn't come with the package anymore: systemd[1]: Starting SOCKS v4 and v5 compatible proxy server and client... systemd[1]: Failed to load environment files: No such file or directory systemd[1]: sockd.service failed to run 'start' task: No such file or directory systemd[1]: Failed to start SOCKS v4 and v5 compatible proxy server and client. My solution was just to: # echo > /etc/conf.d/sockd.conf but I think the PKGBUILD should be changed accordingly. |
This task depends upon
removed from .service