Bug#493036: marked as done (upgrade-reports: apt-get can't upgrade due to debconf failing to upgrade)
Your message dated Wed, 20 Aug 2008 09:51:52 +0200
with message-id <20080820075152.GE4725@yellowpig>
and subject line Re: Bug#493036: Additional Info
has caused the Debian Bug report #493036,
regarding upgrade-reports: apt-get can't upgrade due to debconf failing to upgrade
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
493036: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493036
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: upgrade-reports: apt-get can't upgrade due to debconf failing to upgrade
- From: Justin Hartman <justin@hartmanlife.com>
- Date: Wed, 30 Jul 2008 23:22:44 +0200
- Message-id: <20080730212244.18964.31489.reportbug@static.88-198-18-252.clients.your-server.de>
Package: upgrade-reports
Severity: normal
When trying to run "apt-get upgrade" I get the following error:
apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
The following packages have been kept back:
wordpress
The following packages will be upgraded:
apache2 apache2-mpm-prefork apache2-utils apache2.2-common debconf-utils initscripts libkrb53 linux-image-2.6.18-6-amd64 locales sysv-rc
trac
11 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
1 not fully installed or removed.
Need to get 0B/23.6MB of archives.
After unpacking 4096B of additional disk space will be used.
Do you want to continue [Y/n]?
Preconfiguring packages ...
Setting up debconf (1.5.11etch2) ...
Compiling /usr/lib/python2.4/site-packages/Beaker-0.9.4-py2.4.egg/beaker/ext/google.py ...
SyntaxError: ('future feature absolute_import is not defined',)
dpkg: error processing debconf (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
debconf
E: Sub-process /usr/bin/dpkg returned an error code (1)
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (990, 'stable'), (500, 'testing')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-amd64
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
--- End Message ---
--- Begin Message ---
On Tue, Aug 19, 2008 at 11:01:21PM +0200, Justin Hartman wrote:
> On Tue, Aug 19, 2008 at 10:32 PM, Bill Allombert
> <Bill.Allombert@math.u-bordeaux1.fr> wrote:
> > Try to move /usr/lib/python2.4/site-packages/Beaker-0.9.4-py2.4.egg
> > elsewhere and see what happen.
>
> Thanks Bill, this worked perfectly when I moved it out. I've now
> upgraded and installed python-beaker 0.6.1-1 from the stable stream.
> Once again, thanks for your help!!!
so accordingly, I close this bug.
Maybe scan your system to find other traces of Beaker-0.9.4-py2.4.egg
that could get in the way.
Cheers,
--
Bill. <ballombe@debian.org>
Imagine a large red swirl here.
--- End Message ---
Reply to: