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#61043 - [pacstrap] pacstrap -c -d $dir base command fails executing
Attached to Project:
Arch Linux
Opened by Jelle van der Waa (jelly) - Wednesday, 12 December 2018, 10:51 GMT
Opened by Jelle van der Waa (jelly) - Wednesday, 12 December 2018, 10:51 GMT
|
DetailsDescription:
Additional info: ( 8/13) Creating system user accounts... ( 9/13) Creating temporary files... error: command failed to execute correctly (10/13) Reloading device manager configuration... Skipped: Device manager is not running. (11/13) Arming ConditionNeedsUpdate... (12/13) Updating the info directory file... Steps to reproduce: pacstrap -c -d foo base |
This task depends upon
( 6/11) Creating temporary files...
Detected unsafe path transition / → /etc during canonicalization of /etc.
<many more of those>
error: command failed to execute correctly
( 7/11) Reloading device manager configuration...
As pointed out in this Github issue: https://github.com/systemd/systemd/issues/11282#issuecomment-450347268 this is probably an issue with permissions.
I can reproduce the error when I run `sudo pacstrap -c -d foo base` where `foo` is a directory owned by my regular user. If i create it with `sudo mkdir foo` and then run `sudo pacstrap -c -d foo base` then systemd is happy and all is well.
Can you confirm? If so, I think this bug could be closed? Or should pacstrap be printing a warning in this case?