Bug#966707: debhelper: dh not keeping command log results in package rebuild

2021-04-11 Thread Niels Thykier
On Fri, 16 Oct 2020 17:57:26 +0200 Alex wrote: > Hi, > > Samuel is not alone in this issue. As I frequently rebuild packages with > small changes, I fully recognise the reported problem occurring since > compat 10. I would very welcome a solution to get the behaviour of > compat<10 back as

Bug#966707: debhelper: dh not keeping command log results in package rebuild

2020-10-16 Thread Alex
Hi, Samuel is not alone in this issue. As I frequently rebuild packages with small changes, I fully recognise the reported problem occurring since compat 10. I would very welcome a solution to get the behaviour of compat<10 back as waiting half an hour per build, just to find an error in some

Bug#966707: debhelper: dh not keeping command log results in package rebuild

2020-09-13 Thread Niels Thykier
Control: tags -1 moreinfo Samuel Thibault: > Niels Thykier, le sam. 12 sept. 2020 17:46:03 +0200, a ecrit: >> It occurs to me that this can be done via a custom dh addon using >> something like: > > That's not exactly simple :) > True. > [...] That's why I'm looking for a solution that people

Bug#966707: debhelper: dh not keeping command log results in package rebuild

2020-09-12 Thread Samuel Thibault
Niels Thykier, le sam. 12 sept. 2020 17:46:03 +0200, a ecrit: > It occurs to me that this can be done via a custom dh addon using > something like: That's not exactly simple :) My general concern is about making free software contribution as simple as possible. When discussing with people about

Bug#966707: debhelper: dh not keeping command log results in package rebuild

2020-09-12 Thread Niels Thykier
Samuel Thibault: > [...] >> The devil in the detail here is that I suspect that you also want to >> re-run dh_auto_test and that is on the "wrong" side of that "restart >> point". > > That may happen, yes, although way less often. > > Could there perhaps be a way to specify at which point we

Bug#966707: debhelper: dh not keeping command log results in package rebuild

2020-09-12 Thread Samuel Thibault
Niels Thykier, le sam. 12 sept. 2020 16:49:17 +0200, a ecrit: > Samuel Thibault: > > Niels Thykier, le sam. 12 sept. 2020 14:12:55 +0200, a ecrit: > >> It occurs to me that you need this for debugging. Would it help you if > >> debhelper provided a way for you to intercept the failure and resume

Bug#966707: debhelper: dh not keeping command log results in package rebuild

2020-09-12 Thread Niels Thykier
Samuel Thibault: > Hello, > > Niels Thykier, le sam. 12 sept. 2020 14:12:55 +0200, a ecrit: >> It occurs to me that you need this for debugging. Would it help you if >> debhelper provided a way for you to intercept the failure and resume the >> build from there? > > That can be a start yes,

Bug#966707: debhelper: dh not keeping command log results in package rebuild

2020-09-12 Thread Samuel Thibault
Hello, Niels Thykier, le sam. 12 sept. 2020 14:12:55 +0200, a ecrit: > It occurs to me that you need this for debugging. Would it help you if > debhelper provided a way for you to intercept the failure and resume the > build from there? That can be a start yes, indeed. It happens that another

Bug#966707: debhelper: dh not keeping command log results in package rebuild

2020-09-12 Thread Niels Thykier
Samuel Thibault: > Package: debhelper > Version: 13.2 > Severity: normal > > Hello, > Hi, > Since debhelper compat 10, "The dh command will no longer use log files > to track which commands have been run. The dh command still keeps track > of whether it already ran the "build" sequence and

Bug#966707: debhelper: dh not keeping command log results in package rebuild

2020-08-02 Thread Samuel Thibault
Package: debhelper Version: 13.2 Severity: normal Hello, Since debhelper compat 10, "The dh command will no longer use log files to track which commands have been run. The dh command still keeps track of whether it already ran the "build" sequence and skip it if it did." How does it keep track