I am waiting for a package update to become available on TeX Live. Think
In this process, I noticed I had no idea how many steps are required for a package update to be visible by tlmgr update
. So far, I have identified the following, using siunitx
v3.0.3 as an example:
A release is made on GitHub (Optional, I guess). Timestamp is "2021-05-20T14:56:29Z". Conveniently, one asset is named
siunitx-ctan.zip
.The update appears on CTAN, which say "3.0.3 2021-05-20" (I don't find a timestamp.)
The update appears on the TeX Live SVN. Interestingly, as of now (Friday, 21 May 2021, 06:14 GMT), that newest version is v3.0.2, with a commit time of "Thu May 20 20:17:51 2021 UTC". (So that commit was later than the GitHub release - still, there's a only lower version number.)
The update appears on the TeX Live package repository (hosted by CTAN, it seems). That one hosts
siunitx.tar.xz
which is identical tosiunitx.r59239.tar.xz
, timestamped "2021-05-18 01:52". This is v3.0.0.Consequently,
tlmgr show siunitx
says:
package: siunitx
[...]
revision: 59239
[...]
cat-version: 3.0.0
So I am confident that, had I done the same overview before the update in step 2, I might have seen v3.0.3, v3.0.2, v3.0.1 and v3.0.0 at different stages of this pipeline. This seems to take a lot of time. Aren't these steps automated? Are these all relevant steps, anyway, or what am I missing?
circuitikz
) I send manually a release to CTAN when I think it's worth it. I try to keep GitHub and CTAN in sync, but that's a manual thing. The nice people at CTAN check my submission and the it's out in a couple of days and it got picked by TeXLive. So you can think that there is a kind of sync with a two-day time granularity...