Dan Langille’s Other Diary

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

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 […]

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

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 […]

snapshot ; ls ; destroy; dataset is busy – WTF?

I have found this bizarre situation where a FreeBSD 12.2 snapshot cannot be destroyed. This is the simple example, which works: [dan@pkg01:~] $ sudo zfs snapshot tank_fast/poudriere@snapshot-for-backup [dan@pkg01:~] $ sudo zfs destroy tank_fast/poudriere@snapshot-for-backup [dan@pkg01:~] $ This is the simple example, which fails: [dan@pkg01:~] $ sudo zfs snapshot tank_fast/poudriere@snapshot-for-backup [dan@pkg01:~] $ ls /usr/local/poudriere/.zfs/snapshot/snapshot-for-backup cache data jails […]