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

MiKTeX windows deprecation information can be interpreted as an error #1579

Open
1 task done
dsjoho opened this issue Jan 10, 2025 · 2 comments
Open
1 task done

MiKTeX windows deprecation information can be interpreted as an error #1579

dsjoho opened this issue Jan 10, 2025 · 2 comments

Comments

@dsjoho
Copy link

dsjoho commented Jan 10, 2025

Using MiKTeX 24.1 the emitted information/warning about windows <10 deprecation is not clearly stated as being info/warning, leading me and at least another user to interpret it as an error. I thought my TeX installation was broken when running pdftocairo.exe in order to convert a pdf, as the deprecation notice was the only information emitted to the console.

Example emitted output:

C:\Users\User>pdftocairo.exe -jpeg -scale-to-x 1920 -scale-to-y 1080 -W 1920 -H 1080 "my_poster.pdf"

MiKTeX requires Windows 10 (or greater): https://miktex.org/announcement/legacy-windows-deprecation

C:\Users\User>

Since this wasn't prefixed with warn/info, I erroneously interpreted it as an error and that my installation was broken. Everything worked as it should however and my output file was there.
This message is emitted despite being on Windows 10/11. I would have expected either no emission of it due to fulfilling the requirements, or some kind of prefix indicating that it's information only.

Example of another user with the same confusion:
https://tex.stackexchange.com/questions/710109/error-message-about-windows-10-even-though-im-on-windows-10

miktex-report.txt

Copy link

This issue has been marked as stale due to inactivity.

@StefanSpieker
Copy link

I guess it is because MikTex is targeting Windows 11, so you will also get the error even if you are on Windows 10. I would see this as an issue of the lib, more details can be found here

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

No branches or pull requests

2 participants