Control: reopen -1
On Sat, 26 Dec 2015 17:10:13 +0100 Johannes Schauer wrote:
> whoops, forgot to close this in the upload of 0.67.0-1
it's a bad idea to close bugs manually. Apparently I never pushed the patch for
this one...
signature.asc
Description: signature
Control: retitle -1 Commands for chroot update failed stage
Control: severity -1 wishlist
2015-10-31 8:32 GMT+01:00 Johannes Schauer :
> if you run multiple concurrent sbuild instances, would it not be a better idea
> to always run sbuild with --no-apt-update and instead run
Hi Luca,
Quoting Luca Falavigna (2015-11-01 13:36:24)
> Unfortunately my use case is a special (and therefore quite uncommon) one,
> and everytime a build is scheduled there is always need to update the APT
> cache because the local repository changes so often.
>
> Anyway, I think you're right
Hi!
2015-10-30 22:00 GMT+01:00 Johannes Schauer :
> What would the benefit be to have a --apt-get-update-failed-commands hook?
> Which hook would one like to run when "apt-get update" failed?
I have a local repository of built packages linked to my sbuild
instances. Everytime a
Hi,
Quoting Luca Falavigna (2015-10-31 08:28:58)
> 2015-10-30 22:00 GMT+01:00 Johannes Schauer :
> > What would the benefit be to have a --apt-get-update-failed-commands hook?
> > Which hook would one like to run when "apt-get update" failed?
>
> I have a local repository of
Hi,
Quoting Luca Falavigna (2015-10-30 20:43:05)
> sometimes my builds fail because of issues during apt-get-update phase. To
> handle these cases, I would like to use --build-deps-failed-commands (or
> alternatively --anything-failed-commands), but it seems neither of them are
> triggered on
Source: sbuild
Version: 0.66.0-5
Severity: normal
Dear Maintainer,
sometimes my builds fail because of issues during apt-get-update phase. To
handle these cases, I would like to use --build-deps-failed-commands (or
alternatively --anything-failed-commands), but it seems neither of them are
7 matches
Mail list logo