Keeping -CURRENT up to date with Poudriere

Ultima ultima1252 at
Sun Jun 18 19:56:22 UTC 2017

Poudriere will update based on how it initially was created
unless it was modified in
/usr/local/etc/poudriere.d/jails/$JAIL/method. For the
-STABLE and -CURRENT branch, It *may* somehow be
obtained another way, but usually it has to be compiled
from the respected branch. So it needs to be manually
compiled in /usr/src before doing a poudriere update.

The way I handle multiple branches is adding adding
multiple in /usr/src, eg /usr/src/head, /usr/src/11-stable,
then setting the src in that directory with obj in it as well.

/usr/src/head/src and obj /usr/src/head/obj the method
will need to be set to src=/usr/src/head/src and object
export MAKEOBJDIRPREFIX=/usr/src/head/obj in the

I also make a dataset for each target branch so it can
be zfs send/received.

I hope this helps

On Sun, Jun 18, 2017 at 9:49 AM, Ben Lavery-Griffiths <
ben.lavery at> wrote:

> Hi all,
> I’ve got a 12.0-CURRENT Poudriere jail for ports testing.  Am I right in
> thinking that when Poudriere updates a jail it uses freebsd-update?  In
> which case, -STABLE and -CURRENT jails can’t be updated - correct?
> In this case, if I want to get the latest -STABLE or -CURRENT snapshot,
> will I need to recreate my jail?  Or can Poudriere do it a different way?
> Currently when I try to update I get this:
> > [00:00:00] ====>> Upgrading using ftp
> > /etc/resolv.conf -> /poudriere/jails/12Ci386/etc/resolv.conf
> > mount: /poudriere/jails/12Ci386/compat: No such file or directory
> > Bad system call (core dumped)
> > 12.0-CURRENT
> > [00:00:01] ====>> Recording filesystem state for clean… done
> Many thanks,
> Ben
> _______________________________________________
> freebsd-ports at mailing list
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at"

More information about the freebsd-ports mailing list