Your message dated Tue, 5 Apr 2016 15:16:30 +0100
with message-id <[email protected]>
and subject line Re: Bug#809655: aptitude: harrowing upgrade for the perl 
transition
has caused the Debian Bug report #809655,
regarding aptitude: harrowing upgrade for the perl transition
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.)


-- 
809655: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809655
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.7.5-3
Severity: normal
X-Debbugs-CC: [email protected]

I had a very harrowing upgrade for the perl transition. The first
upgrade managed to remove perl-base somehow and failed spectacularly.
The second and third upgrades also failed but less so and the fourth
upgrade succeeded. I was doing the upgrade in the aptitude console UI
and didn't (AFAIR) select the removal of perl-base.

I've attached aptitude, apt, dpkg and upgrade logs.

If this bug report isn't useful, please close it.

-- Package-specific info:
Terminal: xterm-256color
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.7.5
Compiler: g++ 5.3.1 20151207
Compiled against:
  apt version 5.0.0
  NCurses version 6.0
  libsigc++ version: 2.6.2
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.0.20151024
  cwidget version: 0.5.17
  Apt version: 5.0.0

aptitude linkage:
        linux-vdso.so.1 (0x00007ffc84d64000)
        libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 
(0x00007f271ceca000)
        libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x00007f271cc9a000)
        libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x00007f271ca6f000)
        libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x00007f271c869000)
        libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 
(0x00007f271c56c000)
        libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x00007f271c295000)
        libboost_iostreams.so.1.58.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.58.0 (0x00007f271c07b000)
        libboost_filesystem.so.1.58.0 => 
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.58.0 (0x00007f271be62000)
        libboost_system.so.1.58.0 => 
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.58.0 (0x00007f271bc5d000)
        libxapian.so.22 => /usr/lib/libxapian.so.22 (0x00007f271b85b000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x00007f271b63e000)
        libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x00007f271b2c2000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f271afbd000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x00007f271ada7000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f271aa02000)
        libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007f271a7ff000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f271a5fb000)
        libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x00007f271a3e3000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f271a1c8000)
        libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x00007f2719fb8000)
        liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f2719d94000)
        librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f2719b8c000)
        libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007f2719986000)
        /lib64/ld-linux-x86-64.so.2 (0x000055e79b7c1000)

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (860, 'testing-proposed-updates'), (850, 
'buildd-testing-proposed-updates'), (800, 'unstable'), (790, 
'buildd-unstable'), (700, 'experimental'), (690, 'buildd-experimental'), (500, 
'unstable-debug'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages aptitude depends on:
ii  aptitude-common            0.7.5-3
ii  libapt-pkg5.0              1.1.10
ii  libboost-filesystem1.58.0  1.58.0+dfsg-4.1
ii  libboost-iostreams1.58.0   1.58.0+dfsg-4.1
ii  libboost-system1.58.0      1.58.0+dfsg-4.1
ii  libc6                      2.21-6
ii  libcwidget3v5              0.5.17-4+b1
ii  libgcc1                    1:5.3.1-4
ii  libncursesw5               6.0+20151024-2
ii  libsigc++-2.0-0v5          2.6.2-1
ii  libsqlite3-0               3.9.2-1
ii  libstdc++6                 5.3.1-4
ii  libtinfo5                  6.0+20151024-2
ii  libxapian22v5              1.2.21-1.2

Versions of packages aptitude recommends:
pn  aptitude-doc-en | aptitude-doc  <none>
ii  libparse-debianchangelog-perl   1.2.0-8
ii  sensible-utils                  0.0.9

Versions of packages aptitude suggests:
ii  apt-xapian-index  0.47+nmu2
ii  debtags           2.0.1
ii  tasksel           3.34

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


Attachment: apt.log.gz
Description: application/gzip

Attachment: aptitude.log.gz
Description: application/gzip

Attachment: dpkg.log.gz
Description: application/gzip

Attachment: upgrade.log.gz
Description: application/gzip

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
--- Begin Message ---
tags 809655 - moreinfo
stop


2016-02-17 12:24 To Paul Wise:

In any case, as I said in the previous e-mail, aptitude doesn't
communicate directly with dpkg nor decides the order of the actions, and
aptitude decided in the first iteration that the program should be
"upgraded" and not "removed + installed", so I don't think that we can
do much from this side.

So I am wondering if we should do as Paul said in the original report:

"If this bug report isn't useful, please close it."

It's not exactly useless, it's useful if only to learn about this
problem happening, but I really don't think that we can do much more
from aptitude's side.

So closing the bug now.  Thanks for reporting, in any case.


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

Reply via email to