Hi Antoine,
On 2022-05-25 17:40, Antoine Beaupre wrote:
> Setting up dose-distcheck (7.0.0-1+b1) ...
> Setting up sbuild-build-depends-dose3-dummy (0.invalid.0) ...
> (I)Doseparse: Parsing and normalizing...
> (I)Dose_deb: Parsing Packages file -...
>
> ... and then it's just *stuck* there forever. In fact, even getting
> rid of that thing is hard: just one good old control-c doesn't cut
> it. You need to ^C the *heck* out of it and it eventually succeeds.
>
> I would expect this to fail early. In fact, there *is* an error in apt
> earlier, but it seems the error is ignored as it just carries on from
> there:
>
> The following packages have unmet dependencies:
> sbuild-build-depends-main-dummy : Depends: python (>= 2.7) but it is not
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.
> E: Package installation failed
I've seen this super-hard-to-kill hang with dose encountering
uninstallable packages before (although it seems that I didn't file a
bug about this).
The simple solution that I found was to use apt as the build dependency
resolver. To this end, sbuild-qemu passes
--bd-uninstallable-explainer apt
to sbuild. And on my host, gbp cloning userdir-ldap and running
$ sbuild-qemu *.dsc
terminates just fine with an error message.
What's odd is that this sbuild option seems to get lost on your end. Are
you perhaps overriding this option somehow?
Otherwise, I would suspect an option parsing issue similar to the
--overlay-dir issue that we have been discussing privately.
Will look into this, but if you have any info on a possible override of
--bd-uninstallable-explainer to share, please do.
Best,
Christian
