Those two are indeed authoritative:

Done at the console, but DNS records aren't instantaneously updated, and I'm not even sure those are authoritative (they are for poneytelecom.eu):

2024-10 plan:

Choose to only support FreeBSD:14:amd64 ABI or to use /${ABI}/ in path

We also need a monitoring script to detect those cases:

I've tested poudriered but bump on {"type":"error","message":"Expecting a string for the arguments"} with testport

In T2037#30771, @dereckson wrote:

❌ https://windriver.nasqueron.org/poudriere/base14-dereckson_dev/2024-10-05_12h25m58s/logs/errors/roll-2.6.1.log

❌ https://windriver.nasqueron.org/poudriere/base14-dereckson_dev/2024-10-05_12h25m58s/logs/errors/roll-2.6.1.log

Taking db-A-001.

Message from acme.sh-3.0.9:

https://github.com/acmesh-official/acme.sh/wiki/Stateless-Mode

Yes, it's a fork from Vault 1.14 so we've all the features of token generation. back to the shorter s. tokens).

• about the UI it could be usefull managing secrets more easyly

What about a fork of woof called wurf, for Web upload receive files?

https://github.com/simon-budig/woof/pull/21/files takes care of that

Note we've still a case for deploying poudriere itself, but that can be tracked in a new task, T2039.

Speaking of geo, I've updated hyper-001 firewall rules to allow WindRiver IP to connect for management.

Packaged. Can be published on Nasqueron repository, but I'm going to submit it upstream too.

Build instructions

Mitigated by restoring pg_hba.conf from old WindRiver, but we should check if roles/dbserver-pgsql provisions correctly that file on WindRiver.

Indeed there is no pg_hba.conf in /var/db/postgres/data

Bug has been reported upstream 2024-06-24 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279939