Upgrade failure and corrupted installation ?

[Zdenek Wagner]

Hello,

if I had an array of computers, I would choose another scenario. There
are several possibilities:

1. Make a TL server, i.e. the installaton will be on one computer only
and shared as read/only via nfs or davfs or whatever. Other computers
will just mount it and set PATH. You will maintain one computer only.

2. Use rsync to make a copy of tlnet and then run tlmgr using your
local repository

3. Maintain only one computer and then use rsync to update other
computer. This method is quite cumbersome so the previous method
should probably be preserved.

Zdeněk Wagner
https://www.zdenek-wagner.eu/

st 30. 8. 2023 v 10:32 odesílatel Yann Salmon via tex-live
<tex-live at tug.org> napsal:
>
> Hello,
>
> to conclude with this : I just reinstalled the whole thing, which gave
> the occasion of stripping many packages I was not actually using (the
> install GUI is nicer than in my memories from 2017, btw).
>
> What bugs me still is : what if this happens in a context of an array of
> computers where texlive is managed to do scripted, unattended upgrades
> (which I will likely be confronted to in the future) ?
>
> Surely, one cannot let tlmgr update go on "foerever" if a mirror is not
> responding adequately.
>
> What would be a correct (scripted) procedure to harden things a little ?
> Is making a backup of the tlpdb before running tlmgr update a good idea
> ? And how to use that to restore the whole installation in case tlmgr
> update had to be aborted, or exited with an error ?
>
> (à la git checkout -f backupPoint &&  git clean -fd && git reset --hard)
>
> --
> Cordialement,
>
> Yann Salmon
>
>