Your message dated Sat, 19 Sep 2015 01:42:32 +0100
with message-id <[email protected]>
and subject line Re: aptitude: dist-upgrading Lenny/Gnome to squeeze causes
failure while apt-get work
has caused the Debian Bug report #590604,
regarding aptitude: dist-upgrading Lenny/Gnome to squeeze causes failure while
apt-get work
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 [email protected]
immediately.)
--
590604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590604
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.4.11.11-1~lenny1
My automatic test of upgrades of Gnome and KDE from Lenny to Squeeze
started failing for Gnome recently with aptitude, and the problem is
rather strange. The complete installation and upgrade log is at
<URL:
http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-gnome-aptitude.txt
>,
and in it one can see that the packages deskbar-applet and hplip fail
to upgrade because python 2.6 are missing. But python 2.6 is
available in Squeeze, and should have been upgraded before these two
applications.
The script for doing this upgrade testing is available from the
directory where the log is located, and I am happy to help with
setting up a test environment if you want to reproduce this problem.
The problem seem to start when update-notifier fail to unpack:
Unpacking replacement update-notifier ...
dpkg: error processing
/var/cache/apt/archives/update-notifier_0.99.3debian4_i386
.deb (--unpack):
trying to overwrite '/etc/xdg/autostart/update-notifier.desktop', which is
also
in package update-notifier-common 0.70.7.debian-5
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/update-notifier_0.99.3debian4_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up libfftw3-3 (3.2.2-1) ...
Then the recovery phase fail, first for deskbar-applet then for hplip:
Setting up libschroedinger-1.0-0 (1.0.9-2) ...
dpkg: dependency problems prevent configuration of deskbar-applet:
deskbar-applet depends on python (>= 2.6); however:
Version of python on system is 2.5.2-3.
dpkg: error processing deskbar-applet (--configure):
dependency problems - leaving unconfigured
Setting up libofa0 (0.9.3-3.1) ...
The apt-get dist-upgrade was successful, so perhaps aptitude should be
changed to do the upgrade differently?
Is there some circular dependency at work here causing the recovery
phase to fail?
Happy hacking,
--
Petter Reinholdtsen
--- End Message ---
--- Begin Message ---
Hi Petter,
2010-07-27 19:49 Petter Reinholdtsen:
Package: aptitude
Version: 0.4.11.11-1~lenny1
My automatic test of upgrades of Gnome and KDE from Lenny to Squeeze
started failing for Gnome recently with aptitude, and the problem is
rather strange. The complete installation and upgrade log is at
<URL:
http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-gnome-aptitude.txt
>,
and in it one can see that the packages deskbar-applet and hplip fail
to upgrade because python 2.6 are missing. But python 2.6 is
available in Squeeze, and should have been upgraded before these two
applications.
[...]
The apt-get dist-upgrade was successful, so perhaps aptitude should be
changed to do the upgrade differently?
Sorry that this bug report was not handled until now.
There are still similar problems with current versions of aptitude in
the default configuration -- the first suggestion of aptitude often
prefers to keep packages requested to install/upgrade uninstalled or at
the same version, or even remove them, rather than install/upgrade the
necessary dependencies.
There are multiple reports about the different manifestations of the
problem in its current form; with more information about the state of
the resolver and in general better conditions to try to tackle the
problem.
The resolver implementation changed significantly in versions 0.6.*, so
in my opinion it doesn't make sense to try to reproduce the old
behaviour which caused this problem (with the old aptitude version, and
packages and versions to install/upgrade involved at the time), and
keeping it open doesn't help to investigate the problems with the
current implementation that we should attempt to fix -- symptons are
similar, but algorithms and behaviours causing it are different.
Similarly, I think that merging with other bug reports with similar
symptoms but different underlying causes would not help -- it adds to
the noise and increases the number of things to take into account when
dealing with those bug reports; but it does not add valuable information
on top of what other bugs provide.
So I think that it's better to close this particular bug report, rather
than merge or keep it open, and probably be unattended for another few
years.
I hope that you understand and that it's OK with you, if not, please
reopen.
Cheers.
--
Manuel A. Fernandez Montecelo <[email protected]>
--- End Message ---
_______________________________________________
Aptitude-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
