Steinar H. Gunderson <sgunder...@bigfoot.com> wrote:

> Package: dblatex
> Version: 0.3.5-2
> Severity: serious
>
> Hi,
>
> When dist-upgrading from jessie to stretch, I've seen this happen on a number
> of systems:
>
> Removing dblatex (0.3.5-2) ...
> /var/lib/dpkg/info/dblatex.postrm: 44: /var/lib/dpkg/info/dblatex.postrm: 
> mktexlsr: not found
> dpkg: error processing package dblatex (--remove):
>  subprocess installed post-removal script returned error exit status 127
> Removing texlive-math-extra (2014.20141024-1) ...
> Processing triggers for man-db (2.7.0.2-5) ...
> Errors were encountered while processing:
>  dblatex
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> This breaks the upgrade. It might be that we need a fix in jessie,
> but I don't honestly know the best fix, as it seems to be about
> removing the old package, not installing the new one. I've included a full

Hi,

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'.

Unfortunately in this special case the texlive packages (providing
mktexlsr) are not present when calling dblatex postrm:

> Versions of packages dblatex depends on:
> ii  docbook-xml           4.5-8
> ii  python                2.7.13-2
> ii  python-apt            1.4.0~beta3
> pn  texlive               <none>
> pn  texlive-bibtex-extra  <none>
> pn  texlive-extra-utils   <none>
> pn  texlive-latex-extra   <none>
> pn  texlive-math-extra    <none>
> ii  xsltproc              1.1.29-2.1

A possible solution would be to check for the availability of mktexlsr
in dblatex postrm/postinst and to call it only when found.

Changing this in stretch dblatex is easy (with a new version 0.3.9-3),
but I'm not sure how a corresponding change in jessie dblatex (with a
new version 0.3.5-3) would reach the jessie installations out there: is
there any mechanism that upgrades jessie installations to the most
recent jessie packages first before upgrading to stretch in a second
step?  Or is it something that the users are told in the release notes?
The only requirement I'm able to find there is upgrading to the latest
stable point release [1].  Are there plans for a final jessie point
release?

Another question: after releasing new dblatex jessie version 0.3.5-3, I
need to incorporate the new jessie changelog entry into the changelog of
the new dblatex stretch version 0.3.9-3, don't I?  Although this will
add to the differences between 0.3.9-2 and 0.3.9-3, which the release
managers request to keep as minimal as possible.

BTW, as usual I would need sponsorship for the two new releases as I
have no upload rights.

Any advice is highly appreciated.

[1] 
https://www.debian.org/releases/testing/amd64/release-notes/ch-upgrading.en.html#system-status

Regards, Andreas
-- 
Andreas Hoenen <andr...@hoenen-terstappen.de>
GPG: 1024D/B888D2CE
     A4A6 E8B5 593A E89B 496B
     82F0 728D 8B7E B888 D2CE

Attachment: signature.asc
Description: PGP signature

Reply via email to