Bug#403641: Is this RC: "postrm remove" assumes Depended-on packages are configured and fails (was: Bug#403641: tetex-base: postrm fails if just unpackaged.)

2006-12-19 Thread Steve Langasek
severity 403641 important thanks On Mon, Dec 18, 2006 at 07:36:10PM +0100, Frank Küster wrote: > do you consider the following scenario release-critical? If yes, we > have more than one RC bug: > - $packagemanager install B X > - package A is unpacked > - package B which Depends: A is unpacked >

Bug#403641: tetex-base: postrm fails if just unpackaged.

2006-12-19 Thread Florent Rougon
Frank Küster <[EMAIL PROTECTED]> wrote: > Why is --quiet only used for update-updmap? It's the same script behind > the three, and with "-v" it always says IMHO, it's a bug that --quiet isn't used for all three calls. But this --quiet here dates from before we introduced dhit_check_run_without_e

Bug#403641: tetex-base: postrm fails if just unpackaged.

2006-12-19 Thread Frank Küster
Florent Rougon <[EMAIL PROTECTED]> wrote: > In fact, this problem is taken care of by the dh_installtex snippets, > and the approach is closer to "ignore errors but display a warning" than > to "run the commands iff tex-common is configured, not ignoring errors": > > ,[ From lmodern's current

Bug#403641: tetex-base: postrm fails if just unpackaged.

2006-12-18 Thread Florent Rougon
In fact, this problem is taken care of by the dh_installtex snippets, and the approach is closer to "ignore errors but display a warning" than to "run the commands iff tex-common is configured, not ignoring errors": ,[ From lmodern's current postrm ] | case "$1" in | remove|disappear) |

Bug#403641: tetex-base: postrm fails if just unpackaged.

2006-12-18 Thread Florent Rougon
Frank Küster <[EMAIL PROTECTED]> wrote: > On the other hand, I'm not sure how to fix this. There's a reason why > the update-* scripts fail (with an understandable error message) when > the basic file is missing - so this shouldn't be changed. Should we > really ignore all errors of update-* in

Bug#403641: Is this RC: "postrm remove" assumes Depended-on packages are configured and fails (was: Bug#403641: tetex-base: postrm fails if just unpackaged.)

2006-12-18 Thread Frank Küster
Dear Release Managers, do you consider the following scenario release-critical? If yes, we have more than one RC bug: - $packagemanager install B X - package A is unpacked - package B which Depends: A is unpacked - package X which is unrelated is tried to unpack, but fails (e.g. a file conflic

Bug#403641: tetex-base: postrm fails if just unpackaged.

2006-12-18 Thread Kurt Roeckx
On Mon, Dec 18, 2006 at 06:33:21PM +0100, Frank Küster wrote: > Kurt Roeckx <[EMAIL PROTECTED]> wrote: > > > Package: tetex-base > > Version: 3.0.dfsg.3-3 > > Severity: serious > > > > Hi, > > > > It seems that you can't uninstall the package if things aren't set up > > properly. > > Hm, yes. Wh

Bug#403641: tetex-base: postrm fails if just unpackaged.

2006-12-18 Thread Frank Küster
Kurt Roeckx <[EMAIL PROTECTED]> wrote: > Package: tetex-base > Version: 3.0.dfsg.3-3 > Severity: serious > > Hi, > > It seems that you can't uninstall the package if things aren't set up > properly. Hm, yes. What happens is: - tex-common is unpacked - tetex-base is unpacked - the install run fa

Bug#403641: tetex-base: postrm fails if just unpackaged.

2006-12-18 Thread Kurt Roeckx
Package: tetex-base Version: 3.0.dfsg.3-3 Severity: serious Hi, It seems that you can't uninstall the package if things aren't set up properly. >From the buildd log I see: Selecting previously deselected package tetex-base. Unpacking tetex-base (from .../tetex-base_3.0.dfsg.3-3_all.deb) ... [...