Debusine projects in GSoC, incus backend landing in Debian CI and other updates, Salsa CI maintenance. #Freexian collaborators worked on these and many more contributions to #Debian in March 2026.
Read all the details at https://www.freexian.com/blog/debian-contributions-03-2026/?utm_source=mastodon&utm_medium=social
We thank the organizations subscribing to our Long Term Support contracts (https://www.freexian.com/lts/?utm_source=mastodon&utm_medium=social) and consulting services (https://www.freexian.com/services/?utm_source=mastodon&utm_medium=social) for making this possible.
PSA: Did you know that it’s **unsafe** to put code diffs into your commit messages?
Like https://github.com/i3/i3/pull/6564 for example
Such diffs will be applied by patch(1) (also git-am(1)) as part of the code change!
This is how a sleep(1) made it into i3 4.25-2 in Debian unstable.
https://github.com/prometheus-community/node-exporter-textfile-collector-scripts/issues/124
I think that settles it.
Je ne sais pas si il y a une bonne pratique à ce niveau, peut être avec debconf, pour éviter les accès indésirables et demander aux utilisateurices de faire attention
Peut-être écouter sur localhost par défaut.
L'avantage du serveur contre les tâches cron c'est aussi de pouvoir changer la fréquence de rafraîchissement directement en modifiant le polling time dans Prometheus
C'est surtout le premier point qui risque de me faire continuer je pense
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126079
https://people.debian.org/~gagath/posts/2025/10/13/opentracker-10-in-debian-now-with-fifos/
@fabi1cazenave