Summary: | pakfire-builder: Unable to use the failure shell/shell | ||
---|---|---|---|
Product: | Pakfire | Reporter: | Stefan Schantl <stefan.schantl> |
Component: | Base | Assignee: | Michael Tremer <michael.tremer> |
Status: | NEW --- | QA Contact: | |
Severity: | - Unknown - | ||
Priority: | - Unknown - | CC: | adolf.belka |
Version: | unspecified | ||
Hardware: | unspecified | ||
OS: | Unspecified |
Description
Stefan Schantl
2023-09-30 18:00:45 UTC
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? |