> this failure is most likely because your build environment is buggy
It's always a fresh, clean container image that I recreate entirely (not
dist-upgrade) at 07:00 UTC on my laptop from the latest sid. I run build-dep
and then build with debuild; nothing special.
Other systems -- including the reproducible builds servers -- can reproduce the
FTBFS, so I am not convinced at this point that my environment is buggy.
> One way that can happen is if your environment blocks network access not
> only during build but also during installation of build-dependencies.
I don't block internet access. I really should though!
> apt-file initializes its database when installed, and d-shlibs rely on that.
Ah, smells like the bug is there - d-shlibs does not depend on apt-file and,
clearly, I should not have to manage that dependency manually or have it
installed in my minimal chroots. :)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
_______________________________________________
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
