Closed ButteredCats closed 2 years ago
Got the same issue:
/chrootbuild: line 3: 3 Segmentation fault (core dumped) sudo --preserve-env=SOURCE_DATE_EPOCH -iu builduser bash -c 'cd /startdir; makepkg "$@"' -bash "$@"
I'm not seeing this myself. I'd ensure aurutils & devtools are at their latest version & maybe try removing the chroot files so they get regenerated sudo rm -rf /var/lib/aurbuild/
?
If that doesn't help we can ask upstream.
devtools appears to be up to date (20210202-3) and aurutils too (3.1.2-2). Unfortunately removing all of /var/lib/aurbuild/
and rerunning aurto add gzdoom
produces the same error.
Presumably using makepkg directly works ok?
Yeah, I've tried other packages too and the only fail when using aurto. gzdoom was just what I've been trying to add.
You can report this upstream (https://github.com/AladW/aurutils) aurto add
prints the aur sync ...
command it runs which you can report as failing (and you should be able to reproduce the issue just running that command without aurto).
Running aur sync gzdoom
doesn't reproduce the error, just gave it a shot. If I check aurto status
now I can see the package is added into the repo and everything.
Use the full command that aurto add ...
prints, e.g.
aur sync --no-view --no-confirm --chroot --database=aurto --makepkg-conf=/etc/aurto/makepkg-chroot.conf --pacman-conf=/etc/aurto/pacman-chroot.conf gzdoom
Important in this case this is the --chroot
arg.
Ah, my bad. That does cause it again, I'll report it.
sudo
has been updated to 1.9.8.p2-1 and seems to have fixed it.
Yeah that's fixed it for me as well, I'll close this
Hi. I've found that when trying to add something to aurto a segmentation fault occurs when
sudo --preserve-env=SOURCE_DATE_EPOCH -iu builduser bash -c 'cd /startdir; makepkg "$@"' -bash "$@"
is run in the chroot (I think that's the right term). I chrooted in and found that downgrading to sudo 1.9.7.p2-1 seems to fix this.