Frank Küster fr...@debian.org wrote:
First of all, the follow-up mail to my original bug report #60012 was
misdirected,
and this bug seems to have been bogus from the beginning. I have no
idea what I did back then, but I _cannot_ reproduce it in squeeze or
sid. There's also no indication in
Norbert Preining prein...@logic.at wrote:
On Do, 16 Dez 2010, Frank Küster wrote:
So there is no checking whether there is already an old version
installed. Even in postinst, we have a
case $1 in
configure)
before the resurrect code. We should at least have a check whether we
are
On Do, 16 Dez 2010, Frank Küster wrote:
So there is no checking whether there is already an old version
installed. Even in postinst, we have a
case $1 in
configure)
before the resurrect code. We should at least have a check whether we
are uprgrading, and what the previous version
On 13.12.10 Robert Bihlmeyer (ro...@orcus.priv.at) wrote:
Hi,
Summary: breaks lenny-sid upgrade; probably RC
This also happens during an upgrade from lenny. Why? I guess
because this conffile was previously associated with
texlive-base-bin, which got removed (and the unchanged
Hilmar Preusse hill...@web.de wrote:
On 13.12.10 Robert Bihlmeyer (ro...@orcus.priv.at) wrote:
Hi,
Summary: breaks lenny-sid upgrade; probably RC
This also happens during an upgrade from lenny. Why? I guess
because this conffile was previously associated with
texlive-base-bin, which got
Summary: breaks lenny-sid upgrade; probably RC
This also happens during an upgrade from lenny. Why? I guess because this
conffile was previously associated with texlive-base-bin, which got removed
(and the unchanged pdftexconfig.tex with it).
The original report is about a harmless message.
6 matches
Mail list logo