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

Re: trying to do an upgrade to my debian etch system



On Monday 24 September 2007 14:30, Andrew Sackville-West wrote:
> On Mon, Sep 24, 2007 at 01:56:59PM -0700, tom arnall wrote:
> > On Monday 24 September 2007 13:19, Andrew Sackville-West wrote:
> > > On Mon, Sep 24, 2007 at 01:06:16PM -0700, tom arnall wrote:
> > > > I am trying to do an upgrade to my debian etch system and get the
> > > > following error message. What should I do about it. (i did an update
> > > > just before the upgrade attempt.)
> > > >
> > > >
> > > > Unpacking replacement x11-common ...
> > > > dpkg: error
> > > > processing /var/cache/apt/archives/x11-common_1%3a7.1.0-19_i386.deb
> > > > (--unpack):
> > > >  trying to overwrite `/usr/X11R6/bin', which is also in package
> > > > pythonol
> > >
> > > it looks like pythonol is a spanish language learning tool written in
> > > python, but its not in the debian repositories. Where did it come from
> > > and why the heck does it muck around in /usr/X11R6/bin? It definitely
> > > shouldn't do that, but being outside of standard debian, who
> > > knows. You can force it with
> > >
> > > dpkg --force-overwrite <package>
> > >
> > > but be forewarned that forcing anything is bad and you should try to
> > > find what's going on with pythonol.
> >
> > is there any way to have the update ignore pythonol? I don't recognize
> > it. And def'ly don't want to do a force.
>
> well, that's exactly what the force does -- it ignores the fact that
> pythonol claims to own that directory and goes ahead and lets
> x11-common overwrite it, which is surely a good thing in this
> case. There is a more fundamental issue here though: namely, where did
> pythonol come from if you don't recognise it.
>
> you should be looking at things like:
>
> dpkg -l python\*
>
> apt-cache search pythonol
>
> apt-cache show pythonol
>
> dpkg -L pythonol
>
> etc and see if you can figure that one out.
>
> A

Andrew,

Thanks very much for the prodding to deal with pythonol directly. Actually, I 
just removed it from the system and the upgrade went fine.

tom




Reply to: