I'm currently on the following git commit state: cli: pakfire: Implement --yes (dd34b7441956ce6ed3159a459c1199706cfbc885) The newer one's implement the pakfire-builder command as a c binary which is not finished yet and therefore not useable. In case a build runs through without any troubles, there is eveything okay with the pakfire builder. But if there is any kind of error, usually the debug/failure shell will be prompted. This feature currently does not work, because the main process will be halted/interruped after the first keyboard input, followed by a "logout"... Also the "pakfire-builder shell" command is affected by this issue. LOG: [ 02.0623] + exit 1 [ 02.0623] ++ echo 'Bye bye.' [ 02.0623] Bye bye. Build stage 'install' failed with status 1 pakfire-jail /> cd [1]+ Angehalten pakfire-builder build beep/beep.nm root@tuxedo:/home/ipfire-3.x# root@tuxedo:/home/ipfire-3.x# logout Bye bye. root@tuxedo:/home/ipfire-3.x#
I am also on the same commit stage. I added an exit1 line into the beep.nm file at the end of the install section to make the build fail and got the following :- [ 03.0699] + install -m 0755 beep /var/tmp/pakfire-buildroot.sM9F9J/usr/bin [ 03.0700] + cp beep.1.gz /var/tmp/pakfire-buildroot.sM9F9J/usr/share/man/man1 [ 03.0702] + exit1 [ 03.0702] /var/tmp/pakfire-script.bjnYcP: line 16: exit1: command not found Build stage 'install' failed with status 127 pakfire-jail /> I then entered cd as you showed but I got the following pakfire-jail /> cd pakfire-jail ~> So I don't see the same as you have experienced.
Also don't see the effect if I run the pakfire-builder shell command sudo pakfire-builder shell Scanning local 21/21 Restoring Snapshot 117.2MB/s 100% pakfire-jail /> cd pakfire-jail ~>
Could you please post a trace of this?