Your message dated Sat, 26 Dec 2015 17:10:13 +0100
with message-id <20151226161013.31899.72877@localhost>
and subject line Re: [buildd-tools-devel] Bug#803505: sbuild: Run
build-deps-failed-commands on apt-get-update fail stage too
has caused the Debian Bug report #803505,
regarding sbuild: [PATCH] Added --chroot-update-failed-commands
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
803505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803505
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sbuild
Version: 0.66.0-5
Severity: normal
Hi. I just tried to use sbuild for something, and it failed at the
chroot-update step. This isn't sbuild's fault. But then I tried to use
--anything-failed-commands to peek at the failure, and was unable to do
that. That IS sbuild's fault. Here's a git tree with 2 patches that add
an extra --...-failed-commands option to let us look at this error.
http://anonscm.debian.org/cgit/users/dkogan-guest/sbuild.git/?h=added_chroot_update_failed
Thanks!
--- End Message ---
--- Begin Message ---
Version: 0.67.0-1
On Sun, 01 Nov 2015 14:10:54 +0100 Johannes Schauer <[email protected]> wrote:
> 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 saying update and build-dep phases must be
> > handled separately because it is possible to install build-deps without
> > updating the chroot, but it would be nice to have a command for update
> > failures anyway. If you think this is not worth the burden, feel free to
> > close the bug, and I'll handle my use case in a different way :)
>
> patches appreciated :)
whoops, forgot to close this in the upload of 0.67.0-1
signature.asc
Description: signature
--- End Message ---
