On Thu, 29 Sep 2005, Florian Ernst wrote:
Well, so this error is triggered by installing uni2ascii, but it's in no way caused by it.
Right, thanks so much for your explanation. It is a distribution upgrade issue, which I realized after sending the bug report in. I also tried to see if I could cancel the bug report after noticing that a bug report against e2fsprogs had already been made, but the processing of the bug report had not occurred yet.
I've been using Debian since 1996 or so, and this was my first formal bug report. I don't know if this is because Debian is so good, or because I am so lazy, but surely both play a role. Since uni2ascii was a new package, I decided (erroneously) to report the bug.
This specific box is running an original Debian install from summer 1998. I've obviously not yet upgraded to etch on it, which caused the problem. I set apt's preferences to 'testing' a few release cycles ago and had forgotten about it. However, this helps explain a few other odd behaviors recently on this box.
As this report doesn't cover any bug in uni2ascii I'm reassigning it to e2fsprogs for now and merge it with another similar bugreport. If you want to follow-up to this particular Conflicts/Pre-Depends loop please provide some additional info to Theodore just as he mentioned in <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=325834>.
Well, I did tell apt to remove the e2fsprogs package and reinstall it, and things seem to be working all right.
Regards, -Don -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
