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#75977 - [archlinux-keyring] Double slash in file path
Attached to Project:
Arch Linux
Opened by Richard Neumann (rne) - Thursday, 22 September 2022, 22:21 GMT
Last edited by Toolybird (Toolybird) - Friday, 23 September 2022, 06:37 GMT
Opened by Richard Neumann (rne) - Thursday, 22 September 2022, 22:21 GMT
Last edited by Toolybird (Toolybird) - Friday, 23 September 2022, 06:37 GMT
|
DetailsDescription:
In /usr/lib/systemd/system/archlinux-keyring-wkd-sync.service the path to the executable contains a double slash in the ExecStart= file path. This is due to the fact that in the *.in file, the placeholder and the binary name are separated via a slash as well as in the Makefile the default install directory ends with a slash. One of them should be removed Additional info: * 20220828-1 Steps to reproduce: grep ExecStart /usr/lib/systemd/system/archlinux-keyring-wkd-sync.service I would have made a pull request to the repo on gitlab on this trivial issue, but normal users are shut out from doing so. |
This task depends upon
diff --git a/Makefile b/Makefile
index 7bbbb75..6ea53db 100644
--- a/Makefile
+++ b/Makefile
@@ -2,7 +2,7 @@ SHELL = /bin/bash
PREFIX ?= /usr/local
BUILD_DIR ?= build
KEYRING_TARGET_DIR ?= $(PREFIX)/share/pacman/keyrings/
-SCRIPT_TARGET_DIR ?= $(PREFIX)/bin/
+SCRIPT_TARGET_DIR ?= $(PREFIX)/bin
SYSTEMD_SYSTEM_UNIT_DIR ?= $(shell pkgconf --variable systemd_system_unit_dir systemd)
WKD_FQDN ?= archlinux.org
WKD_BUILD_DIR ?= $(BUILD_DIR)/wkd
```
As I mentioned in the forum [1], I still wonder why systemd ignores the double slashes without any sort of error message. ls utility also ignores more slashes for a given path, the only expected "not found" error is if a full path is given to the script, i.e.: ./usr/bin//archlinux-keyring-wkd-sync (tested with different shells).
May anyone enlighten me or point me to any material explaining what's going on. Sorry if this is slightly off-topic.
[1]: https://bbs.archlinux.org/viewtopic.php?pid=2058090#p2058090
This is also the reason why I tagged "general gripe" rather than "bug", as this is strictly speaking not a bug, but just an imperfection.