Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
- - ALL UNSTABLE / TESTING THREADS SHOULD BE POSTED HERE - - This sub-forum is the dedicated area for the ongoing Unstable/Testing releases of Debian. Advanced, or Experienced User support only. Use the software, give, and take advice with caution.
Can you please help me to resolve this error the completion of installing the tex-common package post-installation process? I have tried alll the usual suspects: trying to remove/purge the package, trying to reinstall the package, and even trying to complete the installation by hand.
not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up tex-common (6.18) ...
Running mktexlsr. This may take some time... done.
Running mtxrun --generate. This may take some time...
mtxrun --generate failed. Output has been stored in
/tmp/mtxrun.tzCTMXFD
Please include this file if you report a bug.
dpkg: error processing package tex-common (--configure):
installed tex-common package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
tex-common
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@debian12:/etc/apt#
Setting up tex-common (6.18) ...
Running mktexlsr. This may take some time... done.
Running mtxrun --generate. This may take some time...
mtxrun --generate failed. Output has been stored in
/tmp/mtxrun.vb0zrNRO
Please include this file if you report a bug.
dpkg: error processing package tex-common (--configure):
installed tex-common package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
tex-common
E: Sub-process /usr/bin/dpkg returned an error code (1)
Today (6 March 2024) I made an upgrade and the tex-common package (6.18) got configured without an error after trying the last 3 day. Seems that someone solved the problem. Thanks!