On Sun, Apr 16, 2017 at 06:55:34PM +0200, b...@debian.org wrote: > After several tests (and then more) I eventually tracked it to HOME > being invariably non-existant in reprotest > (HOME=/nonexistent/first-build and HOME=/nonexistent/second-build), > while my normal compilation environment has an existing home (duh!).
Consider that both sbuild and pbuilder have HOME pointing to something
non-existent.
> - non-existing home: ./configure attempts to run conftest.exe, wine
> can't create '.wine', conftest.exe fails, configure assumes:
> checking whether we are cross compiling... yes
This feels quite buggy behaviour. I suggest you consider this another
bug in your package.
> To detect this issue, and probably others, I'd suggest making the
> control build's HOME point to an existing directory.
By all means, I suggest instead having one build with an existent and
writable HOME, and one with a non-existent one (this leaves out the case
of an existent but not writable, though).
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
