poudriere amassing fetch errors
wolfgang at riegler.homeip.net
Fri Nov 2 16:52:22 UTC 2012
unfortunately I have the same problem. A lot of fetch and checksum errors. I have set RESOLV_CONF=/etc/resolv.conf in /usr/local/etc/poudriere.conf, resolv.conf is copied to the poudriere jail and manual fetching of the ports is working.
On every run of poudriere bulk different ports are failing due to fetch or checksum errors. Sometimes no file is fetched, sometimes a small one and then I get a checksum failure, sometimes the file is about two times bigger and I get a checksum failure, too.
Normal make install clean is running fine on that machine.
I'm using FreeBSD 9.1-rc2 and poudriere 2.2 (2.1. had the same issue)
I have some other problems as well:
- poudriere bulk doesn't exit; after building all pkgs it sleeps forever
- I have two errors several times, but I don't know to which ports they belong:
perl: not found
"Makefile", line 86: warning: "/bin/sh -c 'case `perl --version` in *freebsd-thread*) echo yes ;; esac'" returned non-zero status
/usr/local/bin/apr-1-config: not found
"Makefile.common", line 115: warning: "/usr/local/bin/apr-1-config --includedir" returned non-zero status
Could anybody help me?
Am Samstag, 20. Oktober 2012, 16:14:28 schrieb Christopher J. Ruwe:
> On Fri, 19 Oct 2012 22:29:51 +0200
> Patrick Lamaiziere <patfbsd at davenulle.org> wrote:
> > Le Sun, 14 Oct 2012 03:57:20 +0200,
> > "Christopher J. Ruwe" <cjr at cruwe.de> a écrit :
> > Hello,
> > > for some time I have noticed that poudriere bulk build amass fetch
> > > errors, i.e., the corresponding distfile(s) cannot be fetched by the
> > > build jail and I have to fetch these manually.
> > >
> > > Does anybody know a fix to this unnerving condition?
> > I don't see this problem.
> > Missing resolv.conf ?
> > /usr/local/etc/poudriere.conf
> > # By default the jails have no /etc/resolv.conf, you will need to set
> > # REVOLV_CONF to a file on your hosts system that will be copied has
> > # /etc/resolv.conf for the jail, except if you don't need it (using an
> > http # proxy for example)
> > RESOLV_CONF=/etc/resolv.conf
> My apolgies for that absolutly crappy discription of the error I was
> witnessing. Upon reading my post anew, I just do not know what hit me
> posting that.
> Anyways, I did not have a /etc/resolv.conf entry in my poudriere.conf,
> as it has been working for some time without. The error was rather
> byzanthine ... sometimes, the sources were fetched correctly, sometimes
> not. Regrettably, I do not have any fetch error messages around any
> more, so I cannot supply the information I should have included in my
> first post.
> Anyways, setting the entry in poudriere.conf seems to have solved the
> issue. Interesting how any fetching could have occured without ...
> Thanks and cheers,
More information about the freebsd-ports