Re: [gentoo-user] Can't fetch distfiles in chroot

[Peter Humphrey]

On Thursday, 26 April 2018 08:59:22 BST Peter Humphrey wrote:
> On Tuesday, 24 April 2018 09:43:35 BST Peter Humphrey wrote:
> > On Sunday, 22 April 2018 06:13:30 BST Peter Humphrey wrote:
> > > I've been NFS-exporting the portage treee from a 32-bit atom box to a
> > > chroot on my workstation, and it's worked well for years, if slowly.
> > >
> > > Now when I try to do the same with a 64-bit celeron machine I'm having a
> > > problem getting portage to work. If the required distfile is already
> > > present, no problem, but otherwise, trying to fetch it just hangs. No
> > > errors, no status, no fetch log, no progress.
> > >
> > > Www-client/links works in the chroot as expected, so the network is set
> > > up
> > > all right; portage just can't use it.
> > >
> > > I've compared /etc/exports on the two clients; also the chroot setup
> > > scripts, /usr/portage permissions, the USE flags of nfs-utils and
> > > everything else I can think of. All identical apart from obvious things
> > > like 32/64 bits and network names and IPs. Google hasn't helped either.
> > >
> > > Any ideas, anyone?
> >
> > Never mind. I've rebuilt the chroot from stage 3 and it seems to be
> > working
> > fine.
>
> The appearance was deceptive; all the distfiles needed must have been
> present already. Today, one wasn't and the fetching process hung and had to
> be killed.
>
> So, again, what could possibly prevent portage from seeing the network
> inside a chroot, while other programs use it just the same as always?

So, again, I went off half-cocked (sorry about the noise). The problem is that 
the NFS mount in the chroot picks different ports each time, so the client's 
firewall drops all NFS packets.

Now I just have to find out why that happens.

-- 
Regards,
Peter.