Bug#1138207: tex-common: failure for hilatex.fmt

Control: severity -1 serious

Lowering to serious as in an expected installation, there are
no issues, but I don't know which is the culprit package. This
could be a missing Depends, Breaks, and/or Conflicts, or perhaps
a valid (but unusual) situation not expected by tex-common.

On 2026-05-30 00:09:30 +0200, Preuße, Hilmar wrote:
> Am 29.05.2026 um 13:41 schrieb Vincent Lefevre:
> 
> Hello Vincent,
> 
> > Building format(s) --all.
> >          This may take some time...
> > fmtutil failed. Output has been stored in
> > /tmp/fmtutil.wa6bvEAf.bz2
> > Please include this file if you report a bug.
> > 
> > dpkg: error processing package tex-common (--configure):
> >   old tex-common package postinst maintainer script subprocess failed with exit status 1
> > Processing triggers for install-info (7.3-2) ...
> > install-info: warning: no info dir entry in `/usr/share/info/maxima-index-html.lisp.gz'
> > Errors were encountered while processing:
> >   tex-common
> > 
> > I've attached this /tmp/fmtutil.wa6bvEAf.bz2 file.
> 
> A failing setup of tex-common is seldom an issue in tex-common itself Until
> now I failed to reproduce the issue, even when calling fmtutil-sys --all
> that format is not created, I'll try to have a closer look tomorrow.

Note that "apt install -f" was still giving the same error.

The packages of texlive-bin source were upgraded from
  2025.20250727.75242+ds-5+b2
to
  2026.20260303.78225+ds-4
but the packages of texlive-base and of texlive-extra sources
were still at 2025.20260124-1.

Upgrading the remaining to the 2026.* versions made the error
disappear.

If the mixed 2025 + 2026 packages cannot be handled, the situation
should be disallowed via some Depends, Breaks, and/or Conflicts
declaration in particular to ensure that dependency resolution
cannot yield such a situation.