Hi,
Am Mittwoch, den 26.08.2015, 07:18 +0200 schrieb Johannes Schauer:
> Quoting Julien Cristau (2015-08-25 23:34:55)
> > On Tue, Aug 25, 2015 at 16:31:34 +0200, Joachim Breitner wrote:
> > > Does anyone have a good idea on how to solve that?
> > Talk to the aptitude people?
well, there are open bugs, and even if they could fix it quickly, it
would take a while until the buildd’s would benefit from that. I’m
wondering if there is a work-around to the problem.
> Maybe a conservative solution would be to make sbuild run one of the quick
> resolvers like apt and aptitude first, and only try running apt with an
> external resolver if they cannot find a solution? After all, the job is only
> sent to the buildds if dose3 found that there exists a solution, so this step
> should really never fail on the buildds, no?
Using aspcud on the experimental buildds sounds like an elegant way
out. It would however require patching sbuild to support it in its
--build-dep-resolver=resolver
flag. Johannes, you don’t happen to have such a patch already for your
personal sbuild/aspcud needs? :-)
Greetings,
Joachim
--
Joachim "nomeata" Breitner
Debian Developer
nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F
JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata
Attachment:
signature.asc
Description: This is a digitally signed message part