poudriere

Giving poudriere a jump start

Leave a Comment / poudriere / By /

From time to time, I build my ports for a different version of MySQL, or Python, or, as in tonights case, PHP. My usual build command is: [23:43 pkg01 dvl ~] % sudo poudriere bulk -j 150amd64 -p default -z primary -f /usr/local/etc/poudriere.d/buildlists/primary In this post: FreeBSD 15.0 poudriere-3.4.8 For me to build against PHP85, I first created this file: [23:56 pkg01 dvl /usr/local/etc/poudriere.d] % cat 150amd64-default-php85-make.conf DEFAULT_VERSIONS+= php=85 With that file in […]

Giving poudriere a jump start Read More »

How changes to poudriere.conf affect the build time

Leave a Comment / FreeBSD, Open Source, poudriere / By /

NOTE: I was starting my 6th build when I realized the log links are not publicly accessible. Sorry about that: https://pkg02.int.unixathome.org/ should not resolve for you. I have a new server in the basement, known as r7425-01 – it’s beefy. It’s newer than the other hosts I have. Should I retire one of the older servers? First, let’s see if it’s faster. My primary use case: building packages via poudriere. In this post:

How changes to poudriere.conf affect the build time Read More »

Migrating my hosts from Python 3.11 to Python 3.12

Leave a Comment / FreeBSD, General, pkg, poudriere / By /

This post probably won’t help you much. It is mostly just me saving stuff I may want to refer to later. Also, this post covers only the initial hosts. It is the first step. I’ll also post it to my Mastodon toot. In this post: FreeBSD 14.3 poudriere-3.4.4 the FreeBSD ports tree on head as of 2026-01-20 I’m also moving from PostgreSQL 16 client to PostgreSQL 18 client Building Python 3.12 via poudriere

Migrating my hosts from Python 3.11 to Python 3.12 Read More »

Configuration for running poudriere in a jail on FreeBSD 14

Leave a Comment / FreeBSD, Jails, Open Source, Ports, poudriere / By /

I run poudriere in a jail on FreeBSD – it really is becoming the thing-to-do with all the cool kids. Everyone’s doing it. It is nifty. I will provide only the jail configuration, and not any file system configuration. That is left for you. I think these links might be most helpful: Using poudriere to create a custom FreeBSD repository for package installation Moving poudriere from the host into a jail In this

Configuration for running poudriere in a jail on FreeBSD 14 Read More »

kernel: pid 4900 (conftest), jid 968, uid 65534: exited on signal 11 (core dumped)

Leave a Comment / FreeBSD, Open Source, poudriere / By /

I see see these log messages on a regular basis. There is no distinct pattern. Some nights there might be 1, others 2. Today there were three: r730-01 is my main server in the basement. It runs a jail named pkg01, which does my nightly poudriere builds. Those jobs are launched from this crontab: That UID relates to nobody and matches up with what poudriere does (runs as nobody). [11:46 pkg01 dan ~]

kernel: pid 4900 (conftest), jid 968, uid 65534: exited on signal 11 (core dumped) Read More »

Moving the poudriere jail from slocum to r730-01

Leave a Comment / FreeBSD, Jails, Open Source, poudriere / By /

NOTE: If you’re looking for a jail configuration for poudriere, please refer to Configuration for running poudriere in a jail on FreeBSD 14. I recently moved the pkg01 jail from one host to another. I’m having trouble getting it to build packages. [pkg01 dan ~] % sudo poudriere testport -j 131amd64 -p dvl -z primary -i devel/py-pip [00:00:00] Error: Please load the linux module on the host using “kldload linux” On the host:

Moving the poudriere jail from slocum to r730-01 Read More »

Making my pkg.conf configuration version independent

Leave a Comment / FreeBSD, Open Source, pkg, poudriere / By /

In this post, I will talk about how I modified my pkg configuration so I don’t have to modify it after upgrading a host/jail from one version of FreeBSD to another. You might say that you don’t have to do that. Perhaps you have a different configuration and aren’t doing what I’m doing. HEADS UP: I hit a problem with this approach when updating a jail using mkjail: see https://github.com/mkjail/mkjail/issues/30 In this post:

Making my pkg.conf configuration version independent Read More »

Turning off SASLCLIENT for databases/mysql57-client

Leave a Comment / poudriere / By /

This started off as a Twitter thread earlier this morning. databases/mysql57-client has an optional dependency on security/cyrus-sasl2 which defaults to on. Let’s try turning that off and see if it also removes openldap-client from the dependency list. Why? I install net-mgmt/nagios-plugins in just above every jail and host. Even hosts which don’t use MySQL. I use poudriere to build all my own packages. I added this entry: # Trying to avoid pulling in

Turning off SASLCLIENT for databases/mysql57-client Read More »

poudriere: when renaming sets, also rename *-make.conf files etc

Leave a Comment / nginx, poudriere / By /

Last last night, after renaming some buildlists, which were actually setnames, for poudriere, I realized that files in /usr/local/etc/poudriere.d also needed to be renamed. In this post: poudriere 3.3.7 nginx 1.20.1_2,2 Both running on FreeBSD 13.0-RELEASE-p4 These are my renamed files: [dan@pkg01:/usr/local/etc/poudriere.d]: $ ls *primary* primary-make.conf primary-poudriere.conf primaryi386-make.conf primaryi386-poudriere.conf The output of svn status illustrates the changes I made: [dan@pkg01:/usr/local/etc/poudriere.d]: $ svn st D master-list-i386-make.conf > moved to primaryi386-make.conf D master-list-i386-poudriere.conf > moved

poudriere: when renaming sets, also rename *-make.conf files etc Read More »

poudriere: Warning: Using ‘-‘ in a SETNAME is not recommended as it causes ambiguities with parsing the build name of 122amd64-default-master-list

Leave a Comment / poudriere / By /

I like readability. I like it in variable names. I prefer something descriptive and easy to ready. In in this post: FreeBSD 13.0-RELEASE-p4 poudriere 3.3.7 I recently started getting messages like this from my daily poudiere build: I could just rename the sets, everything would be rebuilt, but then clients would be stuck pointing at the old no-longer built trees. To fix this easily, I will use symlinks. This is what clients use

poudriere: Warning: Using ‘-‘ in a SETNAME is not recommended as it causes ambiguities with parsing the build name of 122amd64-default-master-list Read More »

Scroll to Top