Hi Daniel,
* Daniel Burrows <dburr...@debian.org> [18. Nov. 2009]:
> I just noticed that you're running an 0.4 release of aptitude. Can
> you reproduce this with 0.6 from unstable?
This was when I reported the problem the first time: 2009-10-21
(Message-ID: <20091021131032.ga11...@shi.workgroup>) but later
(2009-11-11) it -- the segfault -- happend again and I produced a
backtrace (Message-ID: <20091111205350.ge12...@shi.workgroup>).
In the meantime I did a full-upgrade and therefore the bugreport
with the backtrace and the state-bundle
GuLWWb8iiNcrYLI30SJARoEEwECAA-aptitude-state-bundle-2009-11-11.tar.bz2
are made with aptitude 0.6.
But only now I realize that the initial bug report was a
... safe-upgrade command while the backtrace and segfault problem from
2009-11-11 was a ... install command. Since in both cases this
happend while resolving the dependencies I think this difference
isn't that important, is ist?
ATM:
sudo nice ionice -c3 sh -c "aptitude update ; aptitude -W --allow-new-upgrades
--allow-new-installs --purge-unused -f safe-upgrade "
does not segfault while resolving the dependencies.
g...@shi:/tmp$ apt-cache policy aptitude
aptitude:
Installed: 0.6.0.1-1
Candidate: 0.6.0.1-1
Version table:
*** 0.6.0.1-1 0
500 http://ftp.de.debian.org unstable/main Packages
100 /var/lib/dpkg/status
g...@shi:/tmp$ aptitude --version
aptitude 0.6.0.1 compiled at Oct 25 2009 19:26:02
Compiler: g++ 4.3.4
Compiled against:
apt version 4.8.1
NCurses version 5.7
libsigc++ version: 2.0.18
Ept support enabled.
Gtk+ support disabled.
Current library versions:
NCurses version: ncurses 5.7.20090803
cwidget version: 0.5.13
Apt version: 4.8.1
Ciao, Gregor
--
-... --- .-. . -.. ..--.. ...-.-
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
