You are not logged in.
Pages: 1
Hello,
Following an issue with mesa I reported on GitLab, I want to bisect the package to make an upstream report.
However, building the mesa-git package requires a ton of makedepends packages, so I tried to build it in a chroot to not trash my system with these dependencies. This is not the first time I make packages this way (using extra-x86_64-build), and the Bisecting bugs with Git wiki page even suggests it as an alternative.
The issue is that the $srcdir exists only in the chroot, and I don't find a way to tell extra-x86_64-build / makearchpkg to not throw away the chroot when rebuilding a second time.
So... how can I make a bisect while building inside a chroot? I've tried using this command, but it still throw away and recreates the chroot as the first step:
extra-x86_64-build -- -- -ef
(-ef is supposed to be passed to makepkg)
According to extra-x86_64-build --help (the command doesn't have a man page), -c (clean the chroot before build) is passed as a default arg to makechrootpkg, but I provide my own args, so it shouldn't use it?
PS: Out of caution, I tried to use makechrootpkg directly, but I can't make it install dependencies (it doesn't find the dependencies on the repo during the first build, I believe extra-x86_64-build is doing something additional to install them).
Offline
I would just use a container instead. If you download the Arch bootstrap image it only needs pacman configured and a user added.
Jin, Jîyan, Azadî
Offline
I track the bisection progress outside the chroot after `makepkg -Codd --noprepare` fetches the source. Set the commit for each step in the PKGBUILD, update the checksum and then build in the chroot.
Offline
I use a similar method as loqs .
It's a bit more work but easy to follow/doublecheck .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Pages: 1