Well, I believe the "red screen of non-death" as you put it behaves exactly as it was intended in the interactive side of aptitude. From the command-line, the error message makes sense as well. Aptitude is recognizing that your sources don't match up with what packages that are currently listed, and it's letting you know something is screwy and that you should update.
However, I do believe it's a bug that updating from the command-line fails...especially when that's what they tell you to do to fix it heh. I'm not that familiar with aptitude from the command-line. If there's another aptitude update command you're supposed to use to fix that problem, then it's not necessarily a bug, but they should mention that in the error message. However, if there's only the one update command then I'd definitly say it's a bug. You shouldn't have to use another APT interface to fix aptitude's error message...it just doesn't make sense. And yes, I had the same problem when trying to update via the command-line with an adjusted sources.list. Ben On Wed, 22 Dec 2004 16:52:37 +0100, Jonathan Kaye <[EMAIL PROTECTED]> wrote: > Ben Bettin wrote: > > I see, didn't realize you were using it on the command-line. I > > usually use it interactively. > > > > When I adjust my sources.list and run 'aptitude' from the > > command-line, a big nasty red window pops up and lists the errors you > > describe. At the bottom is an 'ok' button or some-such, you just hit > > enter and it loads up aptitude. Then i hit 'u' for update. You can > > see it getting the new package lists from the sources. After it's > > done, everything is happy and working great. > > > > I'm not sure what the difference is between 'aptitude update' and > > hitting 'u' when in aptitude's interactive console menus. Perhaps > > it's a bug in the program that's causing you to have this problem? > > > > Sorry for the confusion, hope this helps. > > > > Ben > > Hi Ben, > You are spot on! I tried an experiment of putting a new source into > sources list and hitting "u" and exactly what you described happened. > And yes, carrying on and hitting "u" again caused no further problem. I > hestitated about reporting it as a bug without confirmation. Would you > agree that the "red screen of non-death" that appears in the gui version > is not what the devs intended? If anyone else has had this experience > I'll volunteer to report it as a bug. My first impulse is self-doubt. > Would you mind doing the same experiment on the command line after > adding a new entry to sources.list and see if what happened to me also > happens to you? Then we can be pretty sure it's a bug. Yes,? > Thanks again. > Jonathan > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
