FreeBSD ports collection – Trond's place

Commit 0b7f1af804f06a285717b490bef80e24648adcbe for src/main and commit 6e1fe6d26ea2939656c8286ccbd105a89d3349a3 for src/stable/13 bumped the version number for gnu/lib/libdialog from 8 to 9. Software such as ports-mgmt/dialog4ports complain when run, but make config doesn’t care when dialog4ports is being run around in the ports tree.

Mailman 2.1 has served its purpose at work for several years. Python 2 is at its end of life in FreeBSD. It’s time to move on to Mailman 3 and Python 3, or to Sympa if I’m unsuccessful in getting Mailman 3 up & running. I’ll try and document each step along the way.

r554306 fixed the problem, as users of Poudriere was equally affected.

I recently discovered Starship cross-shell prompt, available in the FreeBSD ports collections as shells/starship. Since there’s no dedicated module for handling Subversion working copies, I added three custom modules to my configuration file. This way I can see the global and the local revision numbers, and a summary of the status flags of the files […]

Update 2020-05-06 Python 2.7.18 was officially added to the ports collection in r534040. I didn’t even bother searching for a PR on the matter, and sure enough, PR 245776 exists and did a more thorough job than my own efforts. While Python 2.x.y is EoL, Python 2.7.18 was released a week ago, on 2020-04-20.

Building devel/bitkeeper on stable/12 using ports-mgmt/synth isn’t straight forward as of r532246.

I’ve been experimenting with net/ntopng and net/geoipupdate. The former comes with a shell script, ntopng-geoip2update.sh, which is stuck in the past. Instead, run these commands, creating the necessary symlinks:

Read More → net/ntopng and net/geoipupdate

Somewhere between r357572 and r358062 something changed so dramatically in base/head that sysutils/htop didn’t display anything useful other than CPU and memory usage.

If you use synth from ports-mgmt/synth and switch from Python 3.6 to 3.7 after having updated the ports tree and after synth have updated its own flavour index, you might see strange error messages such as:

In my infinite (and possibly questionable) wisdom, I usually lock down various software to particular versions. This time I wanted to change the main Python from version 2.7 to version 3.6 on the FreeBSD builder at ${WORK}.

Category: FreeBSD ports collection

libdialog.so.8 → libdialog.so.9

Migrating to Mailman 3

`devel/git` and `make config-conditional`

`shells/starship` and `custom` modules for SVN

Python 2.7.18 on FreeBSD

Building `devel/bitkeeper` on `stable/12` using `ports-mgmt/synth`

`net/ntopng` and `net/geoipupdate`

Recompile `sysutils/htop` after upgrading to `base/head` r358063

Lessons learned switching from Python 3.6 to 3.7

Switching main Python versions in FreeBSD