Bug#807046: pbuilder: how does name resolution work
Mattia Rizzolo
mattia at debian.org
Fri Dec 4 15:30:56 UTC 2015
On Fri, Dec 04, 2015 at 07:55:37PM +0530, Ritesh Raj Sarraf wrote:
> To start with, this bug report is mostly a question. I'm not sure if
> this is really a bug, and if so, is it warranted against pbuilder.
Yeah, I got a bug, I made a quite important error :\
https://bugs.debian.org/806386
> Currently, the way pbuilder works is that it looks into the
> /etc/resolv.conf in its chroot. From it, it determines its name
> resolver.
>
> To keep things simple, for years I ran the dnsmasq caching server locally on my box.
> It helped me to have a static name server, localhost, for that puprose.
>
> If not using a caching nameserver, how are users supposed to use
> pbuilder ? Are they expected to ensure valid name servers are defined ?
> I can't see any way to relate the host's nameserver listing into the
> chroot.
The idea is to use whatever is on the host's /etc/resolv.conf (unless
you want something fancy and then maybe you use CONFDIR and whatnot you
like to use)
I plan to do what I described in comment #10 as soon as I've some time
(I was in the reproducible meeting in Athens this week).
Do you have something to add or maybe point out something I should take
in consideration before that?
If you agree that's actually the same bug please merge them.
Sorry for the inconvincience and thanks for reaching out! :)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pbuilder-maint/attachments/20151204/f18bfdc4/attachment.sig>
More information about the Pbuilder-maint
mailing list