Re: Call for testing ...

[Frank Küster <frank@debian.org>]

Norbert Preining <preining@logic.at> wrote:

> I would be interested in knowing whether a *successfull* upgrade at
> least *did* install the xdvi.cfg file. If yes, then we have only to look
> into the error unwind procedure.

If done with --force-overwrite, the xdvi.cfg file is properly created.

I patched the postrm locally to see what's going on, here's the result:

- postrm is called with abort-upgrade, which makes sense; since it
  failed I do not know whether "old-postinst configure" would have been
  called after that

- The abort-upgrade code in handle_conffile_postrm didn't consider the
  fact that at this point /etc/texmf/xdvi/xdvi.cfg might not exist,
  fixed in SVN

- I forgot to investigate why it wasn't there after the upgrade from
  etch+texlive, I have to repeat the whole thing to find that out.

Regards, Frank
-- 
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)