On Mon, Jan 10, 2005 at 05:52:20PM -0500, Adam C Powell IV wrote: > On Mon, 2005-01-10 at 19:08 +0100, Bill Allombert wrote: > > On Mon, Jan 10, 2005 at 11:00:57AM -0500, Adam C Powell IV wrote: > > > During a woody->sarge upgrade, the new menu unpacked before the old > > > ghostview was removed, resulting in the following breakage: > > > > Thanks to notifying me! > > May I ask why ghostview was removed here ? > > I don't remember, I think out of a habit of removing obsolete packages.
Hmm. How come ghostview was removed between the time menu was unpacked and the time it was configured ? Could you check if menu is 'configured' and that /usr/bin/update-menus is executable ? I have experimented with a user-mode-linux testbox and could not reproduce your problem, so I could not check whether a conflict would solve it. > It's annoying to have to work around past brokenness in order to make a > current upgrade work. And the list of broken packages in your followup > email is quite long. :-( Not too long if we can treat all the vim* packages at once. > > I am afraid apt prefer to keep ghostview than removing it, making hard > > to upgrade. What do you think ? > > Hmm, hard to say. Do we want to support people still using an obsolete > package (by not conflicting with it), or force them to get rid of a > broken one? Since alternatives are readily available, I'd lean toward > the latter. > > Maybe I should wishlist bug gv to conflict/replace ghostview? Independently of this bug, it might be nice if gv provided an upgrade path for ghostview, but that will not fix the problem with the other packages. Cheers, -- Bill. <[EMAIL PROTECTED]> Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
