Check whether our mirror packages are up to date.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

94 lines
6.2 KiB

# Mirror Checker
This mirror status checker determines whether CSC mirror is up-to-date with upstream.
## How To Run
A configuration file may be provided through standard input. Without a configuration file, execute `python`. By default, all the available distributions will be checked. With a configuration file, execute `python <`, for example, `python <`. In this case, only the distributions listed in the configuration file will be checked.
## Dev Notes
How the program works: We first have a general mirror check class called which checks whether the timestamp in the directory of the mirror is in-sync with the upstream. Then, for each CSC mirror, a class is built which inherits from the general class but often overrides the original check function with a check function specific to the mirror. A few big themes are: some check a mirror status tracker provided by the project mirrored; some check all the Release files for each version in a distro etc. website information which all the mirror checker classes need is stored in the data.json file.
Future notes: Because many of the mirror checkers are built very specific to each mirror. A slight change in the way the project manages their mirror-related websites, public repos etc. can drastically influence whether the mirror checker works correctly or not. These problems are also unfortunately very hard to detect, so it's important that CSC actively maintain the mirror checker so that it works as intended in the long term.
Extra notes: A test client for individual mirror checker classes is provided as To use it, simply change all occurrences of the imported project class
## Resources
- [CSC Mirror](
- [Debian Mirror Status Checker](
- [Debian Mirror Status Checker Code](
if we can just view their repo online, we only have to remember the link for their repo and then check the latest timestamp in their repo the same way we check ours
even if the date relies on a specific file in their repo, we can still find the right link for it
to find repos of the mirrored projects to check, just search "projectName mirrors"
## Checker Information
1 year ago
1 year ago
CRAN: has a mirror tracker
csclub: for now, this is the upstream itself, so it needs not to be checked
1 year ago
CTAN: has a mirror tracker
damnsmalllinux: not checking this, since it's abandoned
debian-backports: this is a legacy thing, no longer have to check
debian-volatile: this is a legacy thing, no longer have to check
emacsconf: for now, this is the upstream itself, so it needs not to be checked
linuxmint: candidate for brute force looping
linuxmint-packages: Checking the timestamp of either the Release file or the Packages file should suffice.
1 year ago
macPorts: only distfiles has public repo, no timestamp, too large to loop through, comparing ports.tar.gz in distfiles
1 year ago
mxlinux-iso: this one seems out of sync on the official tracker for 134 days, which is weird
1 year ago
NetBSD: checking timestamps of change files in different versions, and SHA512, MD5 files in the isos of different versions
1 year ago
1 year ago
opensuse: check Update.repo files in folders inside the update folder, not checking tumbleweed-non-oss/ and tumbleweed/ temporarily
1 year ago
1 year ago
puppylinux: check the ISO files or htm files in the folders starting with puppy
racket: make sure that we have the latest version number under racket-installers
raspberry pi: Checking the timestamp of either the Release file or the Packages file should suffice.
raspbian: snapshotindex.txt is most likely a timestamp, tho i'm not sure. also i think our mirror is completely outdated, it's not listed on official mirror list
sagemath: same source tarballs as them (the sage-*.tar.gz files under 'Source Code')
salt stack: checking the "Latest release" text under the 'About' header
scientific: not checking this one since it's abandoned
slackware: check whether we have each release and whether the timestamp for CHECKSUMS.md5 in each release is the same, for slackware-iso, just make sure that our list of directories is the same
trisquel: checking Release file for all versions in packages/dist and md5sum.txt in iso/ with two other mirrors
ubuntu-ports: checking the Release files in dists
ubuntu-ports-releases: has public repo, no timestamp, no status tracker, brute force looped it
1 year ago check all of the files under each directory under /, and make sure that we have all of the files which the upstream has, ignoring the xcb folder
1 year ago
Xiph: loop through each directory in xiph/releases/ and trying to compare the timestamp of the checksum files
xubuntu-releases: candidate for brute force looping since it has few folders