Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalidate cache on new version of texlive #9

Open
1 task done
apriljunge opened this issue Mar 6, 2022 · 0 comments · May be fixed by #10
Open
1 task done

Invalidate cache on new version of texlive #9

apriljunge opened this issue Mar 6, 2022 · 0 comments · May be fixed by #10
Assignees
Labels
enhancement New feature or request

Comments

@apriljunge
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Original problem

The cache-key is generated by profile-path and packages-path.
When these are not changed the texlive version is fixed.

On a long term this can break texlive (tlmgr) with the following error

tlmgr itself needs to be updated.
Please do this via either
  tlmgr update --self
or by getting the latest updater for Unix-ish systems:
  https://mirror.ctan.org/systems/texlive/tlnet/update-tlmgr-latest.sh
and/or Windows systems:
  https://mirror.ctan.org/systems/texlive/tlnet/update-tlmgr-latest.exe
Then continue with other updates as usual.
===============================================================================
tlmgr: Terminating; please see warning above!
tlmgr: package repository https://ctan.mirrors.hoobly.com/systems/texlive/tlnet (verified)

Proposed solution

The cache-key should consider the version or hash of the texlive installer.
As not updating will break the github action it's not needed to have this configurable.

Alternatives considered

One could generate the hash keys in the repos itself and pass it to this action or deactivate caching completely.
I think we should prevent people from deactivationg caches so I think this should be a package feature.

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants