Skip to content

Problem with tlmgr pakageinstaller #4

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

Closed
nsbionix opened this issue Oct 25, 2023 · 3 comments
Closed

Problem with tlmgr pakageinstaller #4

nsbionix opened this issue Oct 25, 2023 · 3 comments
Labels

Comments

@nsbionix
Copy link

Hello,
I tried installing additional packages with the tlmgr command, but all it dows is saying that "tlmgr: Local TeX Live (2022) is older than remote repository (2023)."

I also tried updating over the command seen in the snippet below.

latex ➜ /workspaces/VSCode-LaTeX-Container (main ✗) $ tlmgr update --self --all
(running on Debian, switching to user mode!)
(see /usr/share/doc/texlive-base/README.tlmgr-on-Debian.md)

tlmgr: Local TeX Live (2022) is older than remote repository (2023).
Cross release updates are only supported with
  update-tlmgr-latest(.sh/.exe) --update
See https://tug.org/texlive/upgrade.html for details.

Updating via the given "update-tlmgr-latest,sh" seems kinda difficult (at least for me) inside the WSL Docker container. I may have found the right folder/path to it but it kinda did nothing I think.

- root ➜ /usr/share/texlive $ ./update-tlmgr-latest.sh
- Verifying archive integrity... All good.
- Uncompressing TeX Live Manager Updater  100%
- ./runme.sh: Cannot find TeX Live root using kpsewhich --var-value=SELFAUTOPARENT.
- ./runme.sh: (no tlpkg/texlive.tlpdb and/or tlpkg/tlpobj/.)
- ./runme.sh: Please set your PATH as needed, otherwise it's hopeless.

Is it possible to update TeXLive inside the WSL Docker container? (If thats the solution)
Or did I mess up some configuration step or something?

Tanks in advance,
David

@github-actions
Copy link

Hi, thank for reporting an issue, we will check it out very soon

Copy link

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 14 days.

@github-actions github-actions bot added the Stale label Jan 29, 2024
Copy link

This issue was closed because it has been stalled for 14 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant