You are not logged in.
Hi!
pikaur doesn't output any build messages anymore. I jut get no output after
:: Starting the build:
I' really puzzled, because I think I messed out some config, but can't find anything in the manpage. I appreciate if anybody can push me in the right direction.
Last edited by Henry78 (2020-04-04 11:02:41)
Offline
I am having the same issue.
Offline
I rebuilt and reinstalled pikaur and that fixed the issue for me.
Offline
I'm having the same issue: when I try to install any package, pikaur hangs and the package doesn't get installed at all.
Using the verbose pikaur -Sv minecraft-launcher (it doesn't work with any aur package) command, I get:
Do you want to edit PKGBUILD for minecraft-launcher package? [y/N]
n
=> systemd-run --service-type=oneshot --pipe --wait --pty -p DynamicUser=yes -p CacheDirectory=pikaur -E HOME=/tmp mkdir -p /var/cache/private/pikaur/build/minecraft-launcher
=> systemd-run --service-type=oneshot --pipe --wait --pty -p DynamicUser=yes -p CacheDirectory=pikaur -E HOME=/tmp cp -r /var/cache/private/pikaur/aur_repos/minecraft-launcher/PKGBUILD /var/cache/private/pikaur/aur_repos/minecraft-launcher/last_installed.txt /var/cache/private/pikaur/aur_repos/minecraft-launcher/minecraft-launcher.desktop /var/cache/private/pikaur/aur_repos/minecraft-launcher/.gitignore /var/cache/private/pikaur/aur_repos/minecraft-launcher/.SRCINFO /var/cache/private/pikaur/build/minecraft-launcher/
=> systemd-run --service-type=oneshot --pipe --wait --pty -p DynamicUser=yes -p CacheDirectory=pikaur -E HOME=/tmp -p WorkingDirectory=/var/cache/pikaur/build/minecraft-launcher makepkg --packagelist
:: Starting the build:
=> systemd-run --service-type=oneshot --pipe --wait --pty -p DynamicUser=yes -p CacheDirectory=pikaur -E HOME=/tmp -p WorkingDirectory=/var/cache/pikaur/build/minecraft-launcher makepkg --force
in pikaur and in journalctl:
Starting /usr/bin/makepkg --force...
...
run-u157.service: Main process exited, code=killed, status=1/HUP
run-u157.service: Failed with result 'signal'.
Failed to start /usr/bin/makepkg --force.
SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=run-u157 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
I hope someone has an idea, or more knowledge about systemd-run and the way pikaur works.
Offline
I rebuilt and reinstalled pikaur and that fixed the issue for me.
Yeah same thanks ^^
Offline
I rebuilt and reinstalled pikaur and that fixed the issue for me.
I am having this issue again. I need to do more investigation.
EDIT: well that was a quick investigation. Running it with sudo up the front with an alias one one of my machines was causing the issue (i.e. sudo pikaur -S sompackage). Running it as the user fixed it entirely.
Last edited by henno (2020-04-02 21:38:11)
Offline
Running it with sudo up the front with an alias one one of my machines was causing the issue (i.e. sudo pikaur -S sompackage). Running it as the user fixed it entirely.
Thank you! Had an bash alias with sudo, completeley forgot about that.
Offline