Re: dpkg error
On Thu, Mar 27, 2008 at 10:34 PM, Damon L. Chesser <firstname.lastname@example.org> wrote:
> Michael Marsh wrote:
> > If you've gotten to that point, presumably you have partially updated
> > packages that depend on those (such as evince). What worked for me
> > was to do a
> > $ dpkg -r libdjvulibre15
> > followed by a normal run of aptitude. Removing the old library
> > doesn't cause evince to be removed, because the new version is already
> > there, just broken.
> Really? I would have done this:
> dpkg -i --force-overwrite
> which ignores the fact that another file also wants to "own" that
Good to know. I hardly ever use dpkg, so I was just looking for a way
to force the removal of a no-longer-needed and update-blocking
you are updating to libjvulibre21.
> However, if anything is deping on libdjvulibre15, you just un-installed it.
Yes, I verified that in aptitude first.
> Note to Ron Johnson: is this happening a lot? I did not see any posts on this.
querybts shows 4 distinct bug reports for the same problem, with
almost identical subjects. Do people even *read* the listings in
reportbug? (Check that -- I know the answer.)
Michael A. Marsh