public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Barry Pollock <barryp@mail.hurontel.on.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: debian problems, please help
Date: Sun, 23 Nov 2003 18:16:20 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0311231810190.22204@box> (raw)
In-Reply-To: <20031123220714.GA10886@romuald.net.eu.org>

I usually try delete the file that it can't overwrite. or I force the
pacage with one of the dpkg--forse-options
dpkg --help-force |more.a
Then If I can't get one of those options to work
I send the information directly to the author of the package
You can find the package in question
in
/var/lib/dpkg/availavle
Barry

On Sun, 23 Nov 2003, Gregory Nowak wrote:

> Hi all.
>
> I know that a debian mirrors problem was posted about recently on this
> list, but I decided to do an apt-get update
> and apt-get -u dist-upgrade on my play box, since I haven't done that
> for a week, and am using debian unstable.
>
> After running apt-get -u dist-upgrade for the first time, and then for
> a second time, I got the
> below errors.
>
> apt-get -u dist-upgrade
> Reading Package Lists... Done
> Building Dependency Tree... Done
> Calculating Upgrade... Done
> The following packages will be upgraded
>   python python2.3
> 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> 16 not fully installed or removed.
> Need to get 0B/2897kB of archives.
> After unpacking 16.4kB of additional disk space will be used.
> Do you want to continue? [Y/n] y
> (Reading database ... 20978 files and directories currently
> installed.)
> Preparing to replace python 2.3.2-3 (using .../python_2.3.2-6_all.deb)
> ...
> Unpacking replacement python ...
> dpkg: error processing /var/cache/apt/archives/python_2.3.2-6_all.deb
> (--unpack):
>  trying to overwrite `/usr/share/doc/python2.3/python-policy.html',
>  which is also in package python2.3
> dpkg: considering removing python in favour of python2.3 ...
> dpkg: no, cannot remove python (--auto-deconfigure will help):
>  python-newt depends on python (<< 2.4)
>   python is to be removed.
> dpkg: regarding .../python2.3_2.3.2-6_i386.deb containing python2.3:
>  python2.3 conflicts with python (<= 2.3.2-5)
>   python (version 2.3.2-3) is installed.
> dpkg: error processing
> /var/cache/apt/archives/python2.3_2.3.2-6_i386.deb (--unpack):
>  conflicting packages - not installing python2.3
> Errors were encountered while processing:
>  /var/cache/apt/archives/python_2.3.2-6_all.deb
>  /var/cache/apt/archives/python2.3_2.3.2-6_i386.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> I then tried dpkg --auto-deconfigure as suggested above, but got a
> message saying that no action was specified, or something like that.
>
> Then, I ran apt-get -u dist-upgrade for the third time, and got the
> same error messages as above.
>
> Can someone please help get me out of this mess?
> Thanks.
>
> Greg
>
>
> --
> Free domains: http://www.eu.org/ or mail dns-manager@EU.org
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>


      reply	other threads:[~ UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Gregory Nowak
 ` Barry Pollock [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.58.0311231810190.22204@box \
    --to=barryp@mail.hurontel.on.ca \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).