On Sun, May 16, 2010 22:13, Joerg Pietschmann wrote: > On 16.05.2010 21:18, Thijs Kinkhorst wrote: >> What exactly did you try before you concluded that you were in a loop >> (the log >> you submitted shows two iterations only)? Did you choose 'abort' more >> than 4 >> times? > > I first tried the usual upgrade, then retried a few times, then choose > "abort" twice (or even three times, got a bit nervous at this point).
Thanks. Then I guess I have reproduced the issue. > Nevertheless, I think a fatal problem like a missing database should > cause an immediate abort, and the possibility to retry the upgrade > should not be offered to the user. Note that the UI says something like > "An error happened ..., would you like to [retry] [...] [abort]", while > the more detailed error in the console is obscured, so the user can't > easily judge what happened until the upgrade has already been aborted. > Perhaps the UI should suggest reconfiguring the package, if this > helps. Right, I agree about the most desirable situation but for now I just need to pinpoint the exact behaviour so that I'm sure we're talking about the same issue. cheers, Thijs -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
