Bug#828761: hours_since should not update flag file after an error

2019-11-12 Thread Paul Wise
On Tue, 2019-11-12 at 09:54 +0100, Marc Haber wrote: > Check hours_since > Do command, bail out if unsuccessful > update flag file Hmm, I suppose that could work, but right now there is no way for hours_since to communicate to the parent mr process that the flag file should be updated and which f

Bug#828761: hours_since should not update flag file after an error

2019-11-12 Thread Marc Haber
On Tue, Nov 12, 2019 at 03:12:34PM +0800, Paul Wise wrote: > On Mon, 27 Jun 2016 16:46:03 +0200 Marc Haber wrote: > > The flag should not be touched if there was an error so that one can > > immediately retry the operation. > > There doesn't appear to be any way to fix this, because the skip > com

Bug#828761: hours_since should not update flag file after an error

2019-11-11 Thread Paul Wise
On Mon, 27 Jun 2016 16:46:03 +0200 Marc Haber wrote: > The flag should not be touched if there was an error so that one can > immediately retry the operation. There doesn't appear to be any way to fix this, because the skip command that runs hours_since which touches the flag file runs before the

Bug#828761: hours_since should not update flag file after an error

2016-06-27 Thread Marc Haber
Package: myrepos Version: 1.20160123 Severity: normal Hi, if hours_since is used, and an mr command fails with an error, the flag is still touched, so a retry will not try again: $ mr update mr update: /home/e13itfe/.config/vcsh/repo.d/repo.git mr update: command failed mr update: finished (1 f