Adding Norbert (texlive maintainer) to the discussion, short summary: There was a jessie->stretch upgrade issue reported regarding dblatex: dblatex.postrm failed due to missing mktexlsr. See #863890 for the discussion and logs.
As I did not observe such a problem during my piuparts tests, I have a few questions. If I read the upgrade log correct, dblatex got first deconfigured and later *removed* during the distupgrade. Actually most of the texlive stack seems to get removed (including texlive-binaries, which ships mktexlsr). Why did this happen? What was the actual command you used to perform the upgrade? What was the set of packages installed before the upgrade? dpkg spews a lot of warnings about dependency problems, so it's not dblatex's fault if its postrm failed due to dependency violations. More likely apt (from jessie) is at fault here for choosing a broken upgrade path. On Sat, 03 Jun 2017 19:27:10 +0200 Andreas Hoenen <andr...@hoenen-terstappen.de> wrote: > mktexlsr needs to be called in dblatex postrm/postinst, as documented > there: > > # A call to 'mktexlsr' is needed to register the dblatex TeX files > # in the TeX database '/var/lib/texmf/ls-R-TEXMFMAIN'. That sounds like a very generic requirement for *all* tex packages. dblatex doesn't seem to use dh_installtex? That creates maintainer scripts capable of running mktexlsr etc. and maybe have automatic error handling. I don't see a point of updating dblatex in jessie to make its postrm handle "invalid states", at least not until the underlying cause has been identified. Andreas
