Christian Perrier wrote: > Thanks for the simple hint and patch. I asked the release managers > about a possible upload (which could also fix the stupid #503849).
Another reason to get this fixed before lenny: while playing around I actually managed to destroy a test database by applying the cleanup from gwsetup on it twice. The first one moved the database to old/ and failed without recreating it, the second one first ran a cleanup up old (removing the only remaining copy) and failed as well. Is corruption of user data enough for raising the severity of this bug? (There should be another bugreport, for upstream too, that gwsetup should abort operations after the first failed command.) Andreas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
