Mattia Rizzolo wrote:
> After some deliberation between pbuilder maintainers, sbuild
> maintainers, d-policy people, interested 3rd parties, etc, we came to
> the conclusion that is the chroot's manager job to provide a useful
> /etc/hosts, i.e. pbuilder's job in this case.
Ah, getcha, so build s
[ OT: why do you seem to label the mailing list with the name "Apple"? ]
On Fri, Jul 26, 2019 at 03:08:47PM -0300, Chris Lamb wrote:
> > whilst it's true that in the past localhost would not always resolv to
> > 127.0.0.1, I now fixed it in pbuilder itself
>
> Ah, that was it? This resolves (get
Mattia Rizzolo wrote:
> > Not 100% sure but I thnk the second build also has a slightly
> > different networking setup […]
>
> Not afaik, we don't do any kind of changes to the network setup, and
> whilst it's true that in the past localhost would not always resolv to
> 127.0.0.1, I now fixed
On Thu, Jul 25, 2019 at 06:17:23PM -0300, wf...@niif.hu wrote:
> As
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/kronosnet.html
> shows, the first build succeeds, but the second one hits a failure in
> the build time unit tests. This has been rather consistent for several
>
Mattia Rizzolo writes:
> On Thu, Jul 25, 2019 at 11:10:51PM -0300, Chris Lamb wrote:
>
>>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/kronosnet.html
>>> shows, the first build succeeds, but the second one hits a failure in
>>> the build time unit tests. This has been rathe
On Thu, Jul 25, 2019 at 11:10:51PM -0300, Chris Lamb wrote:
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/kronosnet.html
> > shows, the first build succeeds, but the second one hits a failure in
> > the build time unit tests. This has been rather consistent for several
> >
