Bug#1036929: mmdebstrap: Feature request: "mmdebstrap --anything-failed-commands '%s'" should exist, like in sbuild

2023-06-01 Thread Dima Kogan
Johannes Schauer Marin Rodrigues writes: > let me tell you about another trick. Instead of running > > --customize-hook='chroot "$1" i-might-fail || chroot "$1" bash' > > you can also run: > > --chrooted-customize-hook='i-might-fail || bash' > > In contrast to the --X-hook options, the

Bug#1036929: mmdebstrap: Feature request: "mmdebstrap --anything-failed-commands '%s'" should exist, like in sbuild

2023-05-30 Thread Johannes Schauer Marin Rodrigues
Hi, Quoting Dima Kogan (2023-05-30 20:48:59) > Johannes Schauer Marin Rodrigues writes: > > ah I see our main difference might be that I run mmdebstrap mostly > > from other scripts whereas you are running it interactively and thus > > you want a shell if something goes wrong. > I usually run it

Bug#1036929: mmdebstrap: Feature request: "mmdebstrap --anything-failed-commands '%s'" should exist, like in sbuild

2023-05-30 Thread Dima Kogan
Johannes Schauer Marin Rodrigues writes: > ah I see our main difference might be that I run mmdebstrap mostly > from other scripts whereas you are running it interactively and thus > you want a shell if something goes wrong. I usually run it from scripts too. But if something goes wrong, I

Bug#1036929: mmdebstrap: Feature request: "mmdebstrap --anything-failed-commands '%s'" should exist, like in sbuild

2023-05-30 Thread Johannes Schauer Marin Rodrigues
Hi, Quoting Dima Kogan (2023-05-30 05:34:20) > > Since all hooks have the MMDEBSTRAP_HOOK variable set, whatever is run in > > the > > hook would have access to the type of hook that failed. > > > > The information that would be missing would be *which* hook of a certain > > type > > was the

Bug#1036929: mmdebstrap: Feature request: "mmdebstrap --anything-failed-commands '%s'" should exist, like in sbuild

2023-05-29 Thread Dima Kogan
Johannes Schauer Marin Rodrigues writes: > how about an option like this: > > --failure-hook='chroot "$1" bash' I don't care about the exact command, as long as it's documented. This suggestion sounds reasonable. > Since all hooks have the MMDEBSTRAP_HOOK variable set, whatever is run in the

Bug#1036929: mmdebstrap: Feature request: "mmdebstrap --anything-failed-commands '%s'" should exist, like in sbuild

2023-05-29 Thread Johannes Schauer Marin Rodrigues
Hi Dima, I'm putting Helmut in CC who is in favour of such an option as well and who might have more ideas. Quoting Dima Kogan (2023-05-29 18:42:57) > Hi. Currently it's possible to do > > sbuild --anything-failed-commands '%s' > > to get an interactive shell in response to any step of the

Bug#1036929: mmdebstrap: Feature request: "mmdebstrap --anything-failed-commands '%s'" should exist, like in sbuild

2023-05-29 Thread Dima Kogan
Package: mmdebstrap Version: 1.3.3-6.1 Severity: wishlist X-Debbugs-Cc: none, Dima Kogan Hi. Currently it's possible to do sbuild --anything-failed-commands '%s' to get an interactive shell in response to any step of the process failing. This makes it much easier to debug problems. It would