use of 7.2 host fails on build packages

[huub]

I followed
www.wirelessleiden.nl/projects/nodefactory/wiki/NanoBSD, trying to use
FreeBSD 7.2 instead of 7.1. I got stuck on the build
packages stage: packages could not be fetched. Did not investigate further but started again with 7.1 (for which the procedure was written).
Using 7.1 there were no problems with the packages build script.

[rick]

Some follow-up steps are not compatible with 7.2-RELEASE. So wonder what is going wrong here. Could you provide me some debug info?

[rick]

Could you try setting setenv FTP_PASSIVE_MODE=YES before the pkg_add commands. Will that fix it?

[huub]

Replying to rick:

Could you try setting setenv FTP_PASSIVE_MODE=YES before the pkg_add commands. Will that fix it?

FTP_PASSIVE_MODE is already set to YES, apparently this is the default (?).
Log file of package-build.sh run in mail.

[huub]

Replying to rick:

Some follow-up steps are not compatible with 7.2-RELEASE. So wonder what is going wrong here. Could you provide me some debug info?

After running the nanobsd.sh script some usefull info is available in the _.cust.cust_pkg log file (attached). Several of the packages are not available on ftp.org.freebsd/pub/FreeBSD/ports/i386/packages-7.2-release/Latest.

[rick]

Your package/source directory does not seems to be in sync, as mine lists on a fresh build (see all py26-* instead of py25-*), this is most likely caused by the pkg_add -r which existed in the previous version of the manual.

# ls /root/nanobsd/pkg/All/
gettext-0.17_1.tbz		lvrouted-7051.tbz		pen-0.18.0.tbz			py26-setuptools-0.6c9.tbz
iperf-2.0.4.tbz			nagios-plugins-1.4.13,1.tbz	perl-5.8.9_3.tbz		python26-2.6.2.tbz
isc-dhcp30-server-3.0.7_5.tbz	net-snmp-5.4.2.1_5.tbz		py26-cheetah-2.2.1.tbz		tproxy-2.tbz
libiconv-1.13.1.tbz		nrpe-2.12_1.tbz			py26-cherrypy-3.1.2.tbz		vim-lite-7.2.209.tbz

Could you run the following commands to clean all and start over again, that will properly fix it.

$ pkg_delete /var/db/pkg/*
$ portsnap fetch update
$ /root/nanobsd/tools/package-build.sh

[rick]

Any luck? I was able to build successfull if I deleted the wrongly fetched packages first.

[huub]

Replying to rick:

Any luck? I was able to build successfull if I deleted the wrongly fetched packages first.

Yes that worked here as well.

In order to test the procedure as written I have started all over again from scratch. Everything works fine now, up to writing an image. Image now on test in NodeHuub. This ticket can be closed.

[rick]

In 14089/hybrid:

Fix DNS reply from unexpected source

dig for example will give warning:

;; reply from unexpected source: x.x.x.x#53, expected y.y.y.y#53

as it looks like an attack of some kind.