It's now available on bash by default, but still missing for zsh.

Wiki documentation added to Devserver reference: https://agora.nasqueron.org/index.php?title=Devserver_reference&diff=2037&oldid=1966

Wurf is configured to use port 8080, most of the table can be added to PORTS file.

Could have been interesting to add more context on this.

Alternatively, we made a lot of progress on this in T2124.

Installed and working fine.

Dorian and me meet this evening to do the switch.

Merged D3469 so we can have secrets.

We're testing OpenTofu and Terraform. We've a problem with providers: opentofu registry doesn't compile everything for FreeBSD...

AGPLv3 is an open source, we don't see any objection to it.

So, there is a new reason to do the upgrade.

The port now depends of ImageMagick 7. ImageMagick provides compatibility commands:

Activity done, not upgraded machines will be done with all others as part of T2103.

Not spot anymore. Python 3.11 is used on every FreeBSD systems now.

Closing as a duplicate, as with T1217 task, automation is there:

• new records can be submitted as a commit against zone file
• new zones can be added by creating a new file and pillar entry

Per T2105, current solution is to use an external provider (Hurricane Electric?) to host our secondary zone.

In T2123#32403, @dereckson wrote:

Tests fix commits will be aggregated in datacube T2123-improve-tests-suite branch, so we can have a look of what's remaining to fix.

Tests fix commits will be aggregated in datacube T2123-improve-tests-suite branch, so we can have a look of what's remaining to fix.

Going to take this, as I wrote the tests suite, @DorianWinty will review, so at least two of us will be familiar with the tests.

Why not port encrypt to FreeBSD?

Support for PHP 8.4 is still there.

Uninstalled certbot.
Pruned old Python 3 dependencies.
Updated EPEL repo to epel-release-10-6
Updated packages
Reinstalled certbot, now running under Python 3.12 too.

Just for information, working on T2113, I've first updated the packages non related to that conflict, so I had fresh packages for both systemd and selinux config.

https://snapcraft.io/starship - last update: 27 April 2023 - latest/edge

Was looking to offer a fix upstream, like read hostname from /proc/sys/kernel/hostname on Linux, but then I've realised this is an interaction issue with snap, starship, systemd and SELinux.

Decreasing priority, as it only occurs with Starship.

Normal behavior observed with the policy:

Still an error with last packages versions.

audit2allow policy