[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: SOLVED - Re: Safely Upgrading Packages



----- Original Message ----- 
From: "Carlos Sousa" <csousa@tvtel.pt>
To: <debian-user@lists.debian.org>
Cc: "John Fleming" <john@wa9als.com>
Sent: Monday, July 26, 2004 9:36 PM
Subject: Re: SOLVED - Re: Safely Upgrading Packages


>
> Please don't email me directly, I'm subscribed to the list. I hope you
> don't mind me taking this back to the list, since others could provide
> better advice, or profit by our exchange.
>
> On Mon, 26 Jul 2004 20:10:23 -0500 John Fleming wrote:
> > > That said, if you are willing to take your chances, you can always try
> > > 'dpkg -i --force-overwrite /path/to/package.deb'.
> >
> > I can appreciate this may be an endless problem.
>
> Not really. I've had my share of troubles with apt/dpkg, but I've
> always been able to understand where the problem was, and deal with
> it. Debian's package management is truly amazing in this respect.
>
> > Now I have a similar
> > problem trying to get rid of  a frozen-bubble error, only this time the
> > above command doesn't work like it did for the ntfsprogs files:
> >
> > ...
> > Preparing to replace frozen-bubble-data 1.0.0-4 (using
> > .../frozen-bubble-data_1.0.0-6_all.deb) ...
> > Unpacking replacement frozen-bubble-data ...
> > mv: cannot stat `/usr/games/frozen-bubble.wav': No such file or
directory
> > dpkg: warning - old post-removal script returned error exit status 1
> > ...
> >
> > dpkg -i --force-overwrite
>
> man dpkg. This doesn't make sense here, because the problem is not a file
> belonging to 2 different packages.

I see that in retrospect, and this problem ended up easier to fix.

>
> Once again, I don't recall a problem with my frozen-bubble upgrades...
> Actually, there is no /usr/games/frozen-bubble.wav file listed in the
> frozen-bubble-data 1.0.0-4 package. Very strange...
>
> You could start by doing a 'touch /usr/games/frozen-bubble.wav' and
> see if that solves the problem.

That's exactly what I ended up doing last night prior to seeing this email
this morning, and that did solve it!  The error was saying that wav file
didn't exist, so I just created one.  At this point, all my dist-upgrade
problems are gone.  Thanks!





Reply to: