Hm, did something change how #poudriere remembers progress? Normally, I rsync poudriere/data from one machine to the other, but now the new machine says "pkg bootstrap missing: unable to inspect existing packages, cleaning all packages... done", what am I missing? #FreeBSD
Hm, did something change how #poudriere remembers progress? Normally, I rsync poudriere/data from one machine to the other, but now the new machine says "pkg bootstrap missing: unable to inspect existing packages, cleaning all packages... done", what am I missing? #FreeBSD
#FreeBSD users behind a proxy who also use #Poudriere: what are your tips for configuring an HTTP/HTTPS (non-SOCKS as far as I can tell) proxy for package builds?
#FreeBSD users behind a proxy who also use #Poudriere: what are your tips for configuring an HTTP/HTTPS (non-SOCKS as far as I can tell) proxy for package builds?
#Poudriere build started last night. #curl failed. 310 packages skipped. That kind of sucks.
On that note, has anyone done a writeup on building pkgbase with poudriere?
I had a thought about my existing #poudriere deployment.
It has several ports trees, one of which I use for updating FreeBSD ports.
My idea: create a new jail (pkg01), install poudriere there, move that tree into that jail, and do all my FreeBSD ports work over there.
The only downside I see: after I work on a net-mgmt/librenms instance, I usually do a `sudo cp Makefile distinfo /usr/local/poudriere/ports/mylocalcopy/net-mgmt/librenms`, then (for testing) I build and install locally before committing the work.
That step would be one extra copy (scp to the existing jail, then a sudo cp into the ports tree).
I suppose I could ease that then-two-step-process by a nullfs (and read-only) copy of the first ports tree into the new pkg02 jail.
Why a separate jail for poudriere? It just keeps my #FreeBSD work separate from my personal stuff.
House is freezing this morning because we left the windows open last night.
Solution: Fire up the #poudriere server!
#FreeBSD will keep me warm.
House is freezing this morning because we left the windows open last night.
Solution: Fire up the #poudriere server!
#FreeBSD will keep me warm.
New 𝗣𝗼𝘂𝗱𝗿𝗶𝗲𝗿𝗲 𝗜𝗻𝘀𝗶𝗱𝗲 𝗙𝗿𝗲𝗲𝗕𝗦𝗗 𝗩𝗡𝗘𝗧 𝗝𝗮𝗶𝗹 [Poudriere Inside FreeBSD VNET Jail] article available.
https://vermaden.wordpress.com/2025/07/03/poudriere-inside-freebsd-vnet-jail/
#verblog #containers #freebsd #jails #pkg #poudriere #server
Pilot compiling with #poudriere for #FreeBSD #ports went well! It did seem a bit complicated to configure at first but sing ports made easy with #poudriere and #jail. It was so simple and straightforward to actually run #poudriere that I secretly thought it took out all the fun of seeing scrolling screens of compling! #BSD #Unix #UseBSD #RunBSD #FOSS
And here's the "real world" usage 😎
So now I can give ppl a #login for #swad with a monthly changing password to access my #poudriere logs. Hopefully still keeps the #bot hordes out.
