[xml/sgml-pkgs] Bug#482140: Processed: tagging 482140
daniel.leidert at wgdd.de
Mon Oct 6 21:35:32 UTC 2008
severity 482140 serious
Am Sonntag, den 05.10.2008, 23:16 +0200 schrieb Luk Claes:
> Daniel Leidert wrote:
> > Two entities are not removed. But the maintainer scripts *remove* them.
> > So there must be a reason, why these two entities are not removed and I
> > cannot reproduce this behaviour. I think, that the Perl upgrade maybe
> > leave the system in a broken state, so the removal command fails. But I
> > cannot reproduce it and I tried several upgrade orders! Another
> > possibility is, that the package was shipped wih a CD and was broken on
> > this CD. But reporters told me, that the maintainer scripts on their
> > system were ok. However, re-installing the package also seems to solve
> > the problem.
> If downgrading does not reproduce it, it certainly looks like the
> removal command fails for some reason.
But why does it fail for 2 entities out of >20? I still think, that
there are maybe broken packages on the installation media the reporters
used. The 2 entities are not at the beginning nor the end of the long
list of commands.
> > And now you better shut up and try to reproduce it yourself instead
> > trying to teach me about things, I already examined! I gave you a lot of
> > information, which all did not help me to reproduce it. If you think, I
> > try to *not* solve it: Well show me, how bad I maintain the package!
> Well, it's you who doesn't downgrade the severity even if you are sure
> most people are not affected and you're not able to reproduce the bug.
When did I say, that "most people are not affected"? I simply cannot
reproduce it and I did not yet get any useful information. Downgrading
is like "not having to solve it".
> Btw, I downgraded the severity to important.
Sorry, I cannot agree to this. If I don't get useful information I still
have the choice to add the two removal commands manually to the preinst
script to try to workaround it. Because I don't have the necessary
information I don't know, if this will workaround the issue, but it's
better than nothing.
Setting severity back.
More information about the debian-xml-sgml-pkgs