Closed whentojump closed 1 year ago
I tried another way to update the packages in order to update miktex-misc
as well:
root@fd92fcba0368:/miktex/work# mpm --admin --find-updates # Find the outdated packages
biber-linux-x86_64
miktex-config-2.9
miktex-misc
root@fd92fcba0368:/miktex/work# mpm --admin --update --verbose # Update these packages
...
Sorry, but "MiKTeX Package Manager" did not succeed.
The log file hopefully contains the information to get MiKTeX going again:
/var/log/miktex/mpmcli_admin.log
root@fd92fcba0368:/miktex/work# cat /var/log/miktex/mpmcli_admin.log
/var/log/miktex/mpmcli_admin.log
2022-12-24 17:03:26,234Z FATAL mpmcli - The executed process did not succeed.
2022-12-24 17:03:26,234Z FATAL mpmcli - Info: exitCode="1", fileName="/usr/bin/mkfntmap"
root@fd92fcba0368:/miktex/work# mkfntmap --admin
Sorry, but mkfntmap did not succeed.
The log file hopefully contains the information to get MiKTeX going again:
/var/log/miktex/mkfntmap_admin.log
root@fd92fcba0368:/miktex/work# cat /var/log/miktex/mkfntmap_admin.log
/var/log/miktex/mkfntmap_admin.log
2022-12-24 17:05:29,099Z INFO mkfntmap - Parsing config file /usr/local/share/miktex-texmf/miktex/config/updmap.cfg...
2022-12-24 17:05:29,100Z FATAL mkfntmap - invalid configuration setting
2022-12-24 17:05:29,100Z FATAL mkfntmap - cfg file: /usr/local/share/miktex-texmf/miktex/config/updmap.cfg
2022-12-24 17:05:29,100Z FATAL mkfntmap - line: 87
Refer to https://github.com/MiKTeX/miktex/commit/af6c6d08156d8d49200f9bc680ff9a9225a9f856 , updmap.cfg
is now removed. But the image is one year old, so the bug remains. What's worse, after this, initexmf
will always fail and no document could be compiled.
It is afraid that the only way to make biber
happy is to downgrade biblatex
to version 3.16 manually. The ultimate way to fix this is to refresh the image.
I reproduced your results. Great research and report!!
About this bit --
Refer to https://github.com/MiKTeX/miktex/commit/af6c6d08156d8d49200f9bc680ff9a9225a9f856 ,
updmap.cfg
is now removed.
I think that commit only removes the documentation. updmap.cfg
itself is still shipped along with the package miktex-misc
. See this page. Looks like this configuration file is maintained separately outside the tree?
I also found this: https://github.com/MiKTeX/miktex/issues/1047, which is quite similar to your results. According to the discussion therein, I guess here's the thing: the latest updmap.cfg
from miktex-misc
package doesn't play well with old MiKTeX (21.6, the same as the linked issue's reporter) from Docker Hub. And I agree --
The ultimate way to fix this is to refresh the image.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Platform
baeda1f
sha256:ebd838f3f402f8e027bc68df01d1de2fa31a724b5b0d0c8da0cae109ed18301e
(latest as of this posting)Behavior
Example files (taken from this comment):
I can produce the desired PDF from these files with TeX Live by issuing
latexmk
.Now do the same thing but with a MiKTeX docker container:
which would fail, with the following
example.blg
:According the package repository, the current version of
biber-linux-x86_64
should be2.18
, instead of2.16
.If I try to update this package by running
mpm --update=biber-linux-x86_64
, it will prompt:with
mpm
log (/miktex/.miktex/texmfs/data/miktex/log/mpmcli.log
) looking like this:Sorry I don't really understand every part of this log. It looks to me that the downloaded manifest already contains a correct version
2.18
forbiber-linux-x86_64
package, but it just won't proceed to download and update the binary itself, possibly due to the failure in verifyingmiktex-misc
? which seems a recurring problem (https://github.com/MiKTeX/miktex/issues/855).(And btw, I haven't figured out how that digest is computed. If anyone can give some hints, it will be appreciated and I perhaps can provide more diagnosis information.)
Thanks for your effort in addressing this! Ask me if you need any further information.