Confirmed for recent package:

In T2185#33876, @dereckson wrote:

Each test run produces this:

Nov 11 02:29:33 windriver postgres[63389]: [19-1] 2025-11-11 02:29:33.804 UTC [63389] ERROR:  relation "nonexisting" does not exist at character 13
Nov 11 02:29:33 windriver postgres[63389]: [19-2] 2025-11-11 02:29:33.804 UTC [63389] STATEMENT:  DELETE FROM nonexisting
Nov 11 02:29:34 windriver postgres[63402]: [19-1] 2025-11-11 02:29:34.181 UTC [63402] ERROR:  relation "nonexisting" does not exist at character 15
Nov 11 02:29:34 windriver postgres[63402]: [19-2] 2025-11-11 02:29:34.181 UTC [63402] STATEMENT:  SELECT * FROM nonexisting
Nov 11 02:29:34 windriver postgres[63403]: [19-1] 2025-11-11 02:29:34.209 UTC [63403] ERROR:  relation "nonexisting" does not exist at character 15
Nov 11 02:29:34 windriver postgres[63403]: [19-2] 2025-11-11 02:29:34.209 UTC [63403] STATEMENT:  SELECT * FROM nonexisting
Nov 11 02:29:34 windriver postgres[63408]: [19-1] 2025-11-11 02:29:34.357 UTC [63408] ERROR:  relation "not_existing_table" does not exist
Nov 11 02:29:34 windriver postgres[63408]: [19-2] 2025-11-11 02:29:34.357 UTC [63408] STATEMENT:  TRUNCATE not_existing_table
Nov 11 02:29:34 windriver postgres[63409]: [19-1] 2025-11-11 02:29:34.385 UTC [63409] ERROR:  relation "not_existing" does not exist
Nov 11 02:29:34 windriver postgres[63409]: [19-2] 2025-11-11 02:29:34.385 UTC [63409] STATEMENT:  TRUNCATE not_existing
Nov 11 02:29:34 windriver postgres[63416]: [19-1] 2025-11-11 02:29:34.591 UTC [63416] FATAL:  password authentication failed for user "notexisting"
Nov 11 02:29:34 windriver postgres[63416]: [19-2] 2025-11-11 02:29:34.591 UTC [63416] DETAIL:  Role "notexisting" does not exist.
Nov 11 02:29:34 windriver postgres[63416]: [19-3]       Connection matched pg_hba.conf line 22: "host    all             all             127.0.0.1/32            scram-sha-256"

I guess we could avoid to post PostgreSQL logs directly in /var/log/messages.

Did a run this night to update Certbot files, states are currently correct:

Alkane doesn't need any new account. We can send a request to an URL and it will be run by the deploy user.

Here we are with D3812 build:

That builds properly: https://eglide.org/~dereckson/shroudbnc.log

In T1098#21963, @dereckson wrote:

Tested a build manually successfully with:

$ git clone https://github.com/Learath2/sBNC.git
$ cd sBNC
$ cc *.c -o sbnc
$ sudo cp sbnc /usr/local/bin

Claude Sonnet artifacts

We switched to a dynamic approach for init.sls in D3334.

The full /etc/nginx directories on both docker-002 and dwellers use httpd_config_t for every file.

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

Could have been interesting to add more context on this.

Pending new build of 15.9 version.

Same thing for Dwellers:

During WindRiver reprovisioning, the network unit behaved correctly.

Consolidation recent works occurred at T1828 to further unify nginx configurations.

Some context about this staging repository:

[Moved to T1620]

That's an issue for Chrome to report upstream.

Priority is high as it can affect our certificate renewal process.

Portsnap is deprecated, we'll switch to a Git repository.

Are we going to keep the rSTAGING repository?

Crossed-out files no longer needing Shellcheck.

Per previous comment, I'd advice to downgrade to 3006 LTS for paas-docker servers too.

I've also discovered we can't deploy secrets to Salt 3007+ anymore from a Salt 3006 server: