On 01.03.2018 19:31, Uwe Stöhr wrote:
Am 28.02.2018 um 10:25 schrieb racoon:
Strange. I just ran the installer again and now it works.
Have you run MiKTeX update on every run of the installer as the
installer suggested? If so your virus scanner is not to blame.
I have not yet a solution for this other than to reinstall MiKTeX. That
MiKTeX changed 3 weeks ago (therefore the RC2 installer has no issues)
the packaging system one can describe the problem like this:
The LyX installer uses a "key" for the "lock" of the package handling.
Since the lock was replaced, the installer needs a new key. This key
works for an updated MiKTeX but not for the old one. On top of this
problem comes that one needs 2 runs of the MiKTeX update to get the new
packaging system (lock). And even more there is a bug in the new
packaging system of MiKTeX and the MiKTeX maintainer is currently away.
The LyX installer has no chance to detect what MiKTeX packaging system
is used on the PC. I think the only way is to build a special installer
for LyX 2.3.0 that forces 2 update runs of MiKTeX. This will assure the
success but annoys the user since maybe they already updated and 2 dry
update runs can consume up to 4 minutes installation time in which
nothing happens. I know how annoyed users are by every single button
click they have to do unnecessarily. They will be confronted with 8
additional clicks because of the mentioned bug in MiKTeX. I think
assuring a working installation is more important but if they refuse to
do all the clicks I cannot force 2 update runs.
Give me some time to think about this.
I am quite sure that MiKTeX wasn't the problem in my case. In my first
run of the installer I did not even get to the point where MiKTeX is
searching for updates. And I just cancelled the installation before
MiKTeX update was invoked. And I did not update MiKTeX between the first
and second run and still, on the second, MiKTeX was found even before
the updating by the installer.
Daniel
