buildreq for "localhost works"

[Roland McGrath]

With recent changes to the implicit buildreq set, my package broke in the
mass-rebuild-in-mock tests.  It needs an environment in which "localhost"
resolves properly.  i.e., the canonical dummy /etc/hosts or whatever.
This used to be implicitly supplied, and apparently no longer is.
I can't figure out off hand what buildrequire would supply this.


Thanks,
Roland

[Matt Domsch]

On Tue, Sep 25, 2007 at 05:29:02PM -0700, Roland McGrath wrote:
>  With recent changes to the implicit buildreq set, my package broke in
> the
>  mass-rebuild-in-mock tests.  It needs an environment in which "localhost"
>  resolves properly.  i.e., the canonical dummy /etc/hosts or whatever.
>  This used to be implicitly supplied, and apparently no longer is.
>  I can't figure out off hand what buildrequire would supply this. 
It was a bug in mock for a while, not creating /etc/hosts.  I've
upgraded mock to the latest from rawhide on all my buildhosts and am
rerunning the whole run.  Will post new results when they're
available.

Thanks,
Matt

-- 
Matt Domsch
Linux Technology Strategist, Dell Office of the CTO
linux.dell.com & www.dell.com/linux

[Lubomir Kundrak]

On Tue, 2007-09-25 at 17:29 -0700, Roland McGrath wrote:
>  With recent changes to the implicit buildreq set, my package broke
> in
>  the
>  mass-rebuild-in-mock tests.  It needs an environment in which
>  "localhost"
>  resolves properly.  i.e., the canonical dummy /etc/hosts or whatever.
>  This used to be implicitly supplied, and apparently no longer is.
>  I can't figure out off hand what buildrequire would supply this.  
Apart from the other reply to this post; I can't imagine why would a
build system need to be this much tied to the build host. I would call
it a bug in the build system and patch around it.

-- 
Lubomir Kundrak (Red Hat Security Response Team)

[Roland McGrath]

>  Apart from the other reply to this post; I can't imagine why
> would a
>  build system need to be this much tied to the build host. I would call
>  it a bug in the build system and patch around it. 
Oh, please.  Using free TCP ports on loopback is "tied to the build host"?
It's a universal presumption that "localhost" means 127.0.0.1 and/or ::1,
depending what protocols you are speaking at the instant in question.
There's anal, there's draconian, and then there's butthead pointless.

[Alexander Boström]

ons 2007-09-26 klockan 03:32 -0700 skrev Roland McGrath:
>  "localhost" means 127.0.0.1 and/or ::1 
Actually, I remember some breakage a while back when "::1 localhost" was
put in /etc/hosts. Nowadays it's localhost6(.localdomain6) instead.

/abo