Re: Probably something stupid -- cannot find SRV records and fails
- In reply to: Ronald Klop : "Re: Probably something stupid -- cannot find SRV records and fails"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 16 Jul 2024 12:38:56 UTC
On 7/16/2024 03:25, Ronald Klop wrote: > > *Van:* Ronald Klop <ronald-lists@klop.ws> > *Datum:* dinsdag, 16 juli 2024 08:46 > *Aan:* Karl Denninger <karl@denninger.net> > *CC:* "freebsd-pkg@freebsd.org" <freebsd-pkg@freebsd.org> > *Onderwerp:* Re: Probably something stupid -- cannot find SRV records > and fails > > > Further, a "fetch" against the first requested file > (meta.conf) that the pkg command complains about succeeds: > > # fetch > https://pkg.FreeBSD.org/FreeBSD:14:aarch64/latest/meta.conf > <https://pkg.FreeBSD.org/FreeBSD:14:aarch64/latest/meta.conf> > meta.conf 178 B > 1687 kBps 00s > > Any ideas on where to look? I turned debugging on with "-d" > because the original build was not giving me any idea of what > was happening, but this appears to imply there's no > connectivity out of the VM in that it can't resolve the > hostname -- but there is, obviously. > > Pkg against the base installed system works properly and have > a decent number of packages installed (specifically git and > its dependencies, which was loaded to grab the source tree of > course.) > > Thanks in advance. > > -- > Karl Denninger > karl@denninger.net > /The Market Ticker/ > /[S/MIME encrypted email preferred]/ > ------------------------------------------------------------------------ > > Pkg -c . > This does chroot. Did you configure /etc/resolv.conf in the arm64 > mount? > try chroot . ping pkg.freebsd.org in that same directory. > Regards, > Ronald > That makes sense -- there has to be some difference between the two that winds up without a resolver control file in the target on one, but not the other..... (in theory everything required got copied over but we all know how theory sometimes doesn't translate....) -- Karl Denninger karl@denninger.net /The Market Ticker/ /[S/MIME encrypted email preferred]/