Fix cron warnings for tom #150
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Mmmyes, python2 electric bogaloo
email sample
Symptom:
Salt is failing, on the letter "æ"
Cause 1:
Python3 defaults to utf-8, python2.7 does not. People have æøå in their names.
Cause 2:
Tom is running Debian 9 (stretch), Debian 9 (stretch) uses python2.7, and Debian 9 (stretch) is going out of support everywhere real soon.
Solution suggestion 1:
Upgrade tom inplace to Debian 10, 11 and 12, potentially skipping some steps.
Solution suggestion 2:
Start reimplementing tom on an entirely different box.
I really prefer solution 2, but there are many problems that can arise when upgrading absolutely everything from where we store home directories, to apache-, php-, wsgi-, python-, and debian-versions.
A good place to start is probably to identify the things that can break, and how important they are. Testing/verifying different user pages could be useful, but we could probably also just ask people who have active pages to please check them on a new system?
We don't have an SLA or any real obligations, but preserving historical computing stuff is fun!
we could rebuild tom with nixos and add a shitton of fhs paths
We could start by
wget -r
all of the home pages, make the new tom, crawl it, and diff the result