[Aptitude-devel] Bug#1072620: aptitude: discrepancy between TUI and command line when not all packages of the same source can be upgraded

[Vincent Lefevre]

Package: aptitude
Version: 0.8.13-6
Severity: normal

Normally, when one chooses to upgrade some package, all the other
packages of the same source are selected for upgrade (even when
there are no dependencies to force that).

But when the requested package can be upgraded and other packages
of the same source cannot, the behavior is the following:
  * with the TUI, this is signaled;
  * the command-line aptitude invocation just installs the
requested package, without any warning (possibly yielding
minor inconsistencies, e.g. with the doc).

Note that apt has a 3rd behavior, as seen below.

I think that the command-line aptitude invocation should behave
like the TUI, giving the user the choice to upgrade when proposing
a second resolution.

Currently, for openssl, I have the following installed:

$ apt list --installed \*ssl\* | grep 3.2.1-3
libssl-dev/testing,now 3.2.1-3 amd64 [installed,upgradable to: 3.2.2-1]
libssl-doc/testing,testing,unstable,now 3.2.1-3 all [installed,upgradable to: 
3.2.2-1]
libssl3t64/testing,now 3.2.1-3 amd64 [installed,upgradable to: 3.2.2-1]
libssl3t64/testing,unstable,now 3.2.1-3 i386 [installed,automatic]
openssl/testing,now 3.2.1-3 amd64 [installed,upgradable to: 3.2.2-1]

*** What apt does:

$ apt install -s openssl
[...]
Upgrading:  
  libssl-doc  openssl

Summary:
  Upgrading: 2, Installing: 0, Removing: 0, Not Upgrading: 60
Inst libssl-doc [3.2.1-3] (3.2.2-1 Debian:unstable [all])
Inst openssl [3.2.1-3] (3.2.2-1 Debian:unstable [amd64])
Conf libssl-doc (3.2.2-1 Debian:unstable [all])
Conf openssl (3.2.2-1 Debian:unstable [amd64])

*** With the command-line aptitude invocation:

$ aptitude install -s openssl
The following packages will be upgraded: 
  openssl 
1 packages upgraded, 0 newly installed, 0 to remove and 61 not upgraded.
Need to get 1364 kB of archives. After unpacking 1024 B will be used.

Note: Using 'Simulate' mode.
Do you want to continue? [Y/n/?] 
Would download/install/remove packages.

Note that contrary to apt, libssl-doc is not even proposed for
upgrade.

*** With the TUI, if I type '+' over "openssl", I get in the
dependency resolution:

  --\ Keep the following packages at their current version: 
libssl-dev[3.2.1-3 (now, testing)]
libssl3t64[3.2.1-3 (now, testing)]

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

aptitude version information:
aptitude 0.8.13
Compiler: g++ 13.2.0
Compiled against:
  apt version 6.0.0
  NCurses version 6.4
  libsigc++ version: 2.12.1
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.5.20240427
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7ffe05f4d000)
libapt-pkg.so.6.0 => /lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7f27fc00)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7f27fc8a7000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7f27fc872000)
libsigc-2.0.so.0 => /lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f27fc869000)
libcwidget.so.4 => /lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7f27fc2fe000)
libsqlite3.so.0 => /lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f27fbe88000)
libboost_iostreams.so.1.83.0 => 
/lib/x86_64-linux-gnu/libboost_iostreams.so.1.83.0 (0x7f27fc84d000)
libxapian.so.30 => /lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f27fbc0)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f27fb80)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f27fbb1e000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f27fc2d1000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f27fb61b000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f27fc2b2000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f27fc29f000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f27fc26f000)
liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x7f27fbe62000)
libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x7f27fb55a000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f27fbaeb000)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7f27fb478000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7f27fb33)
libxxhash.so.0 => /lib/x86_64-linux-gnu/libxxhash.so.0 
(0x7f27fc25c000)
/lib64/ld-linux-x86-64.so.2 (0x7f27fc905000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f27fc252000)
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7f27fbe56000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7f27fbac2000)

-- System Information:
Debian Release: trixie/sid
  

[Aptitude-devel] Bug#1065625: libmtp9t64 / libmtp-runtime dependency problem makes dpkg fail with attempt of removal of libmtp-common

[Vincent Lefevre]

On 2024-04-30 11:49:57 +0200, Julian Andres Klode wrote:
> This bug has since been reassigned to aptitude. Solver limitations
> in aptitude wrt t64 handling should not be considered release critical,
> it makes no sense to remove aptitude from testing for it; there are
> still plenty of other valid use cases that are unaffected by these
> particular bugs, so I am downgrading it to important.

OK, but note that this is a rather serious bug somewhere (perhaps
in aptitude, but really, I'm not sure since according to aptitude's
debug log, everything is fine on its side), not just a solver
limitation: if this were a solver limitation, aptitude would have
at least said that the upgrade was not possible because some
dependency could not be satisfied (this is what it usually does);
but this is not what happened.

In short, something attempts to remove a package that has *not*
been marked as to be removed. Fortunately, when trying to remove
the package, dpkg detects a dependency issue. But I fear, that in
some cases (e.g. when the unannounced package to be removed would
not have a dependency on it), this could potentially completely
break the system.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1065625: libmtp9t64 / libmtp-runtime dependency problem makes dpkg fail with attempt of removal of libmtp-common

[Vincent Lefevre]

Hi,

On 2024-04-28 19:21:18 -0300, Facundo Gaich wrote:
> Today I upgraded one of my unstable machines and saw several instances of
> something I believe is the same bug. The resolver seems to be failing to
> choose to upgrade certain dependencies. What's more, in the aptitude GUI
> I can see the rightmost "latest available version" column change on the fly
> when I select certain packages for upgrade.
> 
> For example, I currently have libnm0 and libnm0:i386 installed at 1.46.0-1
> and I can see the latest version is 1.46.0-2. If I go into the GUI and
> choose
> to "Install" libnm0, the latest version column for libnm0:i386 will change
> from 1.46.0-2 to 1.46.0-1. Choosing "Install" on libnm0:i386 will then
> effectively
> do a keep of libnm0 at 1.46.0-1. To fix this, I can either go into
> libnm0:i386 and
> explicitly choose the newest version or I can restart the GUI and then it
> will
> list and choose the latest version correctly when I do Install libnm0:i386.
> 
> aptitude version: 0.8.13-6

This is not the same bug. In my case, the resolver chose to do exactly
what I was asking to. This is also what appears in the aptitude logs.
However, what really happened is something completely different:
libmtp-common was attempted to be removed while no such removal was
shown on the aptitude side (not even in its debug logs). This is not
an issue with the resolver, but what happens somewhere between aptitude
and dpkg.

The "the latest version column for libnm0:i386 will change from
1.46.0-2 to 1.46.0-1" with the TUI corresponds to

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979186

which I had reported 3 years ago and still occurs regularly.

Concerning the buggy dependency resolutions (showing that aptitude
does not favor the most obvious solutions, whether the TUI is used
or not):

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064969

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1064969: aptitude: broken dependency resolution

[Vincent Lefevre]

Control: found -1 0.8.13-6
Control: retitle -1 aptitude: broken dependency resolution

Bug still present.

For instance, the following works as expected:

cventin:~> aptitude install -s grub-common libefiboot1t64 libefivar1t64
The following NEW packages will be installed:
  libefiboot1t64 libefivar1t64 
The following packages will be REMOVED:
  libefiboot1{a} libefivar1{a} 
The following packages will be upgraded:
  grub-common 
1 packages upgraded, 2 newly installed, 2 to remove and 53 not upgraded.
Need to get 2981 kB of archives. After unpacking 6144 B will be used.
The following packages have unmet dependencies:
 grub-pc-bin : Depends: grub-common (= 2.12-1) but 2.12-1.1 is to be installed
 grub2-common : Depends: grub-common (= 2.12-1) but 2.12-1.1 is to be installed
 grub-pc : Depends: grub-common (= 2.12-1) but 2.12-1.1 is to be installed
The following actions will resolve these dependencies:

 Upgrade the following packages:  
1) grub-pc [2.12-1 (now, testing) -> 2.12-1.1 (unstable)] 
2) grub-pc-bin [2.12-1 (now, testing) -> 2.12-1.1 (unstable)] 
3) grub2-common [2.12-1 (now, testing) -> 2.12-1.1 (unstable)]

But just "aptitude install -s grub-common" does not. This is
surprising because the new grub-common package depends on both
libefiboot1t64 and libefivar1t64, so that one should expect a
similar result.

"aptitude install -s grub-common" does not propose *any* acceptable
solution. The first solution is to do nothing, which is obviously
not helpful. The fifth solution is correct concerning the libraries,
but aptitude wants to remove grub-pc and grub2-common instead of
upgrading them:

 Remove the following packages:   
1) grub-pc [2.12-1 (now, testing)]
2) grub2-common [2.12-1 (now, testing)]   
3) libefiboot1 [38-3 (now, testing, unstable)]
4) libefivar1 [38-3 (now, testing, unstable)] 

 Install the following packages:  
5) libefiboot1t64 [38-3.1 (unstable)] 
6) libefivar1t64 [38-3.1 (unstable)]  

This is silly.

Going further, aptitude wants to remove more and more packages.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1065626: libgtk2.0-0t64 / libgtk2.0-bin dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common

[Vincent Lefevre]

And on a 3rd machine, where I used

  aptitude --log-file=/tmp/aptitude.log --log-level=info


dpkg: dependency problems prevent removal of libb2-1:amd64:
 libqt6core6t64:amd64 depends on libb2-1 (>= 0.98.1).

dpkg: error processing package libb2-1:amd64 (--purge):
 dependency problems - not removing
(Reading database ... 795189 files and directories currently installed.)
Purging configuration files for libts0:amd64 (1.22-1+b1) ...
Errors were encountered while processing:
 libb2-1:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)


In the logs, this package libb2-1 appears only twice:

2024-03-13 01:33:14 [140549832112320] aptcache.cc:2323 INFO aptitude.apt.cache 
- aptitudeDepCache::sweep(): reinstating libb2-1:amd64

2024-03-13 01:34:48 [140549832112320] aptcache.cc:2323 INFO aptitude.apt.cache 
- aptitudeDepCache::sweep(): reinstating libb2-1:amd64

I've attached the compressed log file corresponding to this upgrade.

The packages that appear as REMOVE/INSTALL/UPGRADE in /var/log/aptitude:

[REMOVE, NOT USED] libatrildocument3:amd64 1.26.2-1
[REMOVE, NOT USED] libatrilview3:amd64 1.26.2-1
[REMOVE, NOT USED] libgxps2:amd64 0.3.2-3
[INSTALL, DEPENDENCIES] libatrildocument3t64:amd64 1.26.2-1.1+b1
[INSTALL, DEPENDENCIES] libatrilview3t64:amd64 1.26.2-1.1+b1
[INSTALL, DEPENDENCIES] libgxps2t64:amd64 0.3.2-4+b1
[INSTALL, DEPENDENCIES] libpoppler-cpp0t64:amd64 22.12.0-2.2
[INSTALL, DEPENDENCIES] libpoppler-glib8t64:amd64 22.12.0-2.2
[INSTALL, DEPENDENCIES] libpoppler-qt5-1t64:amd64 22.12.0-2.2
[INSTALL, DEPENDENCIES] libpoppler-qt6-3t64:amd64 22.12.0-2.2
[INSTALL, DEPENDENCIES] libpoppler126t64:amd64 22.12.0-2.2
[INSTALL, DEPENDENCIES] libqt6core6t64:amd64 6.4.2+dfsg-21.1+b1
[INSTALL, DEPENDENCIES] libqt6dbus6t64:amd64 6.4.2+dfsg-21.1+b1
[INSTALL, DEPENDENCIES] libqt6gui6t64:amd64 6.4.2+dfsg-21.1+b1
[INSTALL, DEPENDENCIES] libts0t64:amd64 1.22-1.1
[REMOVE, DEPENDENCIES] libpoppler-cpp0v5:amd64 22.12.0-2+b1
[REMOVE, DEPENDENCIES] libpoppler-glib8:amd64 22.12.0-2+b1
[REMOVE, DEPENDENCIES] libpoppler-glib8-dbgsym:amd64 22.12.0-2+b1
[REMOVE, DEPENDENCIES] libpoppler-qt5-1:amd64 22.12.0-2+b1
[REMOVE, DEPENDENCIES] libpoppler-qt6-3:amd64 22.12.0-2+b1
[REMOVE, DEPENDENCIES] libpoppler126:amd64 22.12.0-2+b1
[REMOVE, DEPENDENCIES] libpoppler126-dbgsym:amd64 22.12.0-2+b1
[REMOVE, DEPENDENCIES] libqt6core6:amd64 6.4.2+dfsg-21
[REMOVE, DEPENDENCIES] libqt6dbus6:amd64 6.4.2+dfsg-21
[REMOVE, DEPENDENCIES] libqt6gui6:amd64 6.4.2+dfsg-21
[REMOVE, DEPENDENCIES] libts0:amd64 1.22-1+b1
[UPGRADE] atril:amd64 1.26.2-1 -> 1.26.2-1.1+b1
[UPGRADE] atril-common:amd64 1.26.2-1 -> 1.26.2-1.1
[UPGRADE] libpoppler-dev:amd64 22.12.0-2+b1 -> 22.12.0-2.2
[UPGRADE] libpoppler-private-dev:amd64 22.12.0-2+b1 -> 22.12.0-2.2
[UPGRADE] poppler-utils:amd64 22.12.0-2+b1 -> 22.12.0-2.2

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


aptitude.log.xz
Description: Binary data
___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1065626: libgtk2.0-0t64 / libgtk2.0-bin dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common

[Vincent Lefevre]

The same problem occurred on another machine, with other packages:

dpkg: dependency problems prevent removal of libjte2:amd64:
 libisofs6t64:amd64 depends on libjte2.

dpkg: error processing package libjte2:amd64 (--purge):
 dependency problems - not removing
(Reading database ... 708510 files and directories currently installed.)
Purging configuration files for libts0:amd64 (1.22-1+b1) ...
dpkg: dependency problems prevent removal of libid3tag0:amd64:
 libimlib2t64:amd64 depends on libid3tag0 (>= 0.15.1b).

dpkg: error processing package libid3tag0:amd64 (--purge):
 dependency problems - not removing
Errors were encountered while processing:
 libjte2:amd64
 libid3tag0:amd64

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1065626: libgtk2.0-0t64 / libgtk2.0-bin dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common

[Vincent Lefevre]

On 2024-03-07 17:15:05 +, Simon McVittie wrote:
> I can confirm that version 2.24.33-4 of libgtk2.0-common, libgtk2.0-0t64
> and libgtk2.0-bin are, in fact, installable (I have them installed
> right now). I can't see any dependency relationships between them that
> look suspicious.
> 
> If dpkg is removing libgtk2.0-common, then something must surely be
> asking dpkg to remove it?

But if it were aptitude, I would assume that it would have
a REMOVE line with this package in its logs.

> I notice that you have reported at least three bugs that are "the same
> shape" with three unrelated libraries, which suggests that this might
> be more of an aptitude problem than a GTK problem.

Some aptitude developer told me that installation issues were
in general due to declarations by packages.

> Other logs, in particular /var/log/apt/term.log, might provide more
> information about what actually happened.

I've attached the corresponding part of this file.
Note that libgtk2.0-common is mentioned only at the end
(what I had already given).

> Alternatively, if there is some heuristic about "try to keep packages
> from the same source at the same version" being applied, perhaps waiting
> for libgtk2.0-common_2.24.33-4 to become available from the
> Architecture: all buildd would help?

It was already available. And I installed it just after the error.
aptitude should obviously have proposed it for upgrade. I don't
know whether this is a bug in aptitude or something wrong in the
dependencies.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Log started: 2024-03-07  16:01:43
(Reading database ...  (Reading database ... 5% (Reading database ... 10% 
(Reading database ... 15% (Reading database ... 20% (Reading database ... 25% 
(Reading database ... 30% (Reading database ... 35% (Reading database ... 40% 
(Reading database ... 45% (Reading database ... 50% (Reading database ... 55% 
(Reading database ... 60% (Reading database ... 65% (Reading database ... 70% 
(Reading database ... 75% (Reading database ... 80% (Reading database ... 85% 
(Reading database ... 90% (Reading database ... 95% (Reading database ... 100% 
(Reading database ... 655929 files and directories currently installed.)
Preparing to unpack .../libgtk2.0-bin_2.24.33-4_amd64.deb ...
Unpacking libgtk2.0-bin (2.24.33-4) over (2.24.33-3) ...
Preparing to unpack .../libgail-common_2.24.33-4_amd64.deb ...
Unpacking libgail-common:amd64 (2.24.33-4) over (2.24.33-3) ...
dpkg: libgail18:amd64: dependency problems, but removing anyway as you 
requested:
 libgnomecanvas2-0:amd64 depends on libgail18 (>= 1.18.0).

(Reading database ...  (Reading database ... 5% (Reading database ... 10% 
(Reading database ... 15% (Reading database ... 20% (Reading database ... 25% 
(Reading database ... 30% (Reading database ... 35% (Reading database ... 40% 
(Reading database ... 45% (Reading database ... 50% (Reading database ... 55% 
(Reading database ... 60% (Reading database ... 65% (Reading database ... 70% 
(Reading database ... 75% (Reading database ... 80% (Reading database ... 85% 
(Reading database ... 90% (Reading database ... 95% (Reading database ... 100% 
(Reading database ... 655928 files and directories currently installed.)
Removing libgail18:amd64 (2.24.33-3) ...
Selecting previously unselected package libgail18t64:amd64.
(Reading database ...  (Reading database ... 5% (Reading database ... 10% 
(Reading database ... 15% (Reading database ... 20% (Reading database ... 25% 
(Reading database ... 30% (Reading database ... 35% (Reading database ... 40% 
(Reading database ... 45% (Reading database ... 50% (Reading database ... 55% 
(Reading database ... 60% (Reading database ... 65% (Reading database ... 70% 
(Reading database ... 75% (Reading database ... 80% (Reading database ... 85% 
(Reading database ... 90% (Reading database ... 95% (Reading database ... 100% 
(Reading database ... 655923 files and directories currently installed.)
Preparing to unpack .../libgail18t64_2.24.33-4_amd64.deb ...
Unpacking libgail18t64:amd64 (2.24.33-4) ...
dpkg: libgtk2.0-0:amd64: dependency problems, but removing anyway as you 
requested:
 xournal depends on libgtk2.0-0 (>= 2.14.0).
 pinentry-gtk2 depends on libgtk2.0-0 (>= 2.18.0).
 pavumeter depends on libgtk2.0-0 (>= 2.8.0).
 libgtkmm-2.4-1v5:amd64 depends on libgtk2.0-0 (>= 2.24.0).
 libgnomecanvas2-0:amd64 depends on libgtk2.0-0 (>= 2.8.17).
 libgimp2.0:amd64 depends on libgtk2.0-0 (>= 2.24.10).
 ibus-gtk:amd64 depends on libgtk2.0-0 (>= 2.24.0).
 gromit depends on libgtk2.0-0 (>= 2.24.0).
 gkrellweather depends on libgtk2.0-0 (>= 2.8.0).
 gkrellm-volume depends on libgtk2.0-0 (>= 2.8.0).
 gkrellm depends on libgtk2.0-0 (>= 2.24.0).
 gimp depends on libgtk2.0-0 (>= 2.24.10).

(Reading database ...  (Reading database ... 5% (Reading database ... 10% 
(Reading database ... 15% 

[Aptitude-devel] Bug#1065605: aptitude: useless backup of pkgstates

[Vincent Lefevre]

Package: aptitude
Version: 0.8.13-5+b2
Severity: minor

I ran aptitude to do an upgrade from the TUI (dpkg failed), then
quit just after it. This was before 11:28, since I reported this
failure at this time.

But /var/lib/aptitude contains

-rw-r--r-- 1 root root 10438852 2024-03-07 11:29:40 pkgstates
-rw-r--r-- 1 root root 10438852 2024-03-07 11:29:39 pkgstates.old

and these files have the same contents, which is useless.

I don't see what could have modified pkgstates... or perhaps from
the journalctl output:

Mar 07 11:22:25 qaa systemd[1]: Started packagekit.service - PackageKit Daemon.
[...]
Mar 07 11:30:11 qaa systemd[1]: packagekit.service: Deactivated successfully.

I could see nothing else.

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

aptitude version information:
aptitude 0.8.13
Compiler: g++ 13.2.0
Compiled against:
  apt version 6.0.0
  NCurses version 6.4
  libsigc++ version: 2.12.1
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.4.20240113
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7fff813f9000)
libgtk3-nocsd.so.0 => /lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 
(0x7f8fcf2bd000)
libapt-pkg.so.6.0 => /lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7f8fcea0)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7f8fcf283000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7f8fcf24e000)
libsigc-2.0.so.0 => /lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f8fcf245000)
libcwidget.so.4 => /lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7f8fcecfc000)
libsqlite3.so.0 => /lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f8fce88a000)
libboost_iostreams.so.1.83.0 => 
/lib/x86_64-linux-gnu/libboost_iostreams.so.1.83.0 (0x7f8fcece2000)
libxapian.so.30 => /lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f8fce60)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f8fce20)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f8fce521000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f8fcecb3000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f8fce01e000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f8fcecae000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f8fceca9000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f8fcec8a000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f8fcec77000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f8fce4e4000)
liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x7f8fcec4f000)
libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x7f8fcdf5d000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f8fce857000)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7f8fcde7b000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7f8fcdd33000)
libxxhash.so.0 => /lib/x86_64-linux-gnu/libxxhash.so.0 
(0x7f8fcec3a000)
/lib64/ld-linux-x86-64.so.2 (0x7f8fcf2e5000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f8fce4da000)
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7f8fce4ce000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7f8fce4a5000)

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), 
(500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aptitude depends on:
ii  aptitude-common   0.8.13-5
ii  libapt-pkg6.0t64  2.7.13+b1
ii  libboost-iostreams1.83.0  1.83.0-2.1
ii  libc6 2.37-15.1
ii  libcwidget4   0.5.18-6+b1
ii  libgcc-s1 14-20240303-1
ii  libncursesw6  6.4+20240113-1
ii  libsigc++-2.0-0v5 2.12.1-1
ii  libsqlite3-0  3.45.1-1
ii  libstdc++614-20240303-1
ii  libtinfo6 6.4+20240113-1
ii  libxapian30   1.4.22-1+b1

Versions of packages aptitude recommends:
ii  libdpkg-perl1.22.5
ii  sensible-utils  0.0.22

Versions of packages aptitude suggests:
ii  apt-xapian-index0.55
ii  aptitude-doc-en [aptitude-doc]  0.8.13-5
pn  debtags 
ii  tasksel 3.75

-- no debconf information

-- 
Vincent Lefèvre  - Web: 

[Aptitude-devel] Bug#1065554: Bug#1065554: aptitude: the TUI silently breaks a "Recommends"

[Vincent Lefevre]

On 2024-03-06 21:36:09 +0100, Axel Beckert wrote:
> Hi Vincent,
> 
> Vincent Lefevre wrote:
> > Do you need the bundle?
> 
> Actually that would be interesting, as I have a vague idea how it
> might have been triggered and would like to experiment a bit if I can
> find a simpler reproducer.

[link sent in a private reply]

> BTW, do I remember right that you have APT::Install-Recommends set
> "false"?

AFAIK, perhaps except on a very old laptop (due to the lack of
disk space), I've always chosen to install recommends, which is
the default.

I usually have

  Aptitude::ProblemResolver::SolutionCost "safety, removals";

but this is not the case on this machine yet.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1065554: Bug#1065554: aptitude: the TUI silently breaks a "Recommends"

[Vincent Lefevre via Aptitude-devel]

On 2024-03-06 16:47:47 +0100, Axel Beckert wrote:
> Hi Vincent,
> 
> Vincent Lefevre wrote:
> > The aptitude TUI silently breaks a "Recommends":
> 
> I've seen also already seen this, but so far it always was for a
> reason here:
> 
> * On multiarch hosts, amd64 and i386 weren't in sync and there were
>   Breaks against any version not being the same version.

This is not a multiarch host yet.

> * An initial solution pulls in a package which Breaks the package in
>   question and that pulled in package later (manually or due to other
>   conflicts by manual changes) gets set to "keep uninstalled", but the
>   effect of its Breaks is not reverted.

I cannot see any Breaks of at-spi2-core.

Note that with the command line, I get

The following packages will be upgraded: 
  gtk-update-icon-cache libgtk-3-bin{b} libgtk-3-common 
The following packages are RECOMMENDED but will NOT be installed:
  libgtk-3-0t64 
3 packages upgraded, 0 newly installed, 0 to remove and 48 not upgraded.
Need to get 4763 kB of archives. After unpacking 3072 B will be used.
The following packages have unmet dependencies:
 libgtk-3-bin : Depends: libgtk-3-0t64 (>= 3.24.41-1.1) but it is not going to 
be installed
The following actions will resolve these dependencies:

 Keep the following packages at their current version:
1) libgtk-3-bin [3.24.41-1 (now, testing)]

Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

 Remove the following packages: 
1) libatk-bridge2.0-0 [2.50.0-1+b1 (now, testing, unstable)]
2) libatk1.0-0 [2.50.0-1+b1 (now, testing, unstable)]   
3) libatspi2.0-0 [2.50.0-1+b1 (now, testing, unstable)] 
4) libgtk-3-0 [3.24.41-1 (now, testing, unstable)]  

 Install the following packages:
5) libatk-bridge2.0-0t64 [2.51.90-2 (unstable)] 
6) libatk1.0-0t64 [2.51.90-2 (unstable)]
7) libatspi2.0-0t64 [2.51.90-2 (unstable)]  
8) libgtk-3-0t64 [3.24.41-1.1 (unstable)]   

 Upgrade the following packages:
9) at-spi2-core [2.50.0-1+b1 (now, testing) -> 2.51.90-2 (unstable)]

Accept this solution? [Y/n/q/?] y
The following packages have unmet dependencies:
 libgtk-3-0t64 : Depends: libgtk-3-common (>= 3.24.41-1.1) but it is not going 
to be installed
The following actions will resolve these dependencies:

 Upgrade the following packages:
 
1) libgtk-3-common [3.24.41-1 (now, testing, unstable) -> 3.24.41-1.1 
(unstable)]

 Leave the following dependencies unresolved:   
 
2) libgtk-3-0t64 recommends libgtk-3-bin
 

Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

 Keep the following packages at their current version:  
  
1) libgtk-3-0 [3.24.41-1 (now, testing, unstable)]  
  
2) libgtk-3-0t64 [Not Installed]
  

 Upgrade the following packages:
  
3) libgtk-3-common [3.24.41-1 (now, testing, unstable) -> 3.24.41-1.1~exp1 
(experimental)]

 Leave the following dependencies unresolved:   
  
4) libgtk-3-0 recommends libgtk-3-bin   
  
5) libgtk-3-0t64 recommends libgtk-3-bin
  

(Note: an upgrade to experimental is bad. BTW, no experimental
packages are currently installed.)

Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

 Keep the following packages at their current version: 
1) libgtk-3-0 [3.24.41-1 (now, testing, unstable)] 
2) libgtk-3-0t64 [Not Installed]   
3) libgtk-3-common [3.24.41-1 (now, testing, unstable)]

 Leave the following dependencies unresolved:  
4) libgtk-3-0 recommends libgtk-3-bin  
5) libgtk-3-0t64 recommends libgtk-3-bin   

and then this is worse and worse. If I type 'y' for this solution,
I get:

The following NEW packages will be installed:
  libatk-bridge2.0-0t64{a} libatk1.0-0t64{a} libatspi2.0-0t64{a} 
The following packages will be REMOVED:
  at-spi2-core{u} libatk-bridge2.0-0{a} libatk1.0-0{a} libatspi2.0-0{a} 
libgtk-3-bin{u} 
The following packages will be upgraded:
  gtk-update-icon-cache 

Similarly, at-spi2-core gets removed without any warning on
the Recommends.

> But in your case neither of that se

[Aptitude-devel] Bug#1064969: apt: can't upgrade with aptitude

[Vincent Lefevre]

And even in a simple case line cnee:

qaa:~> aptitude install -s cnee
The following packages will be REMOVED:  
  libxnee0{u} 
The following packages will be upgraded:
  cnee{b} 
1 packages upgraded, 0 newly installed, 1 to remove and 263 not upgraded.
Need to get 50.4 kB of archives. After unpacking 324 kB will be freed.
The following packages have unmet dependencies:
 cnee : Depends: libxnee0t64 but it is not going to be installed
The following actions will resolve these dependencies:

 Install the following packages:
1) libxnee0t64 [3.19-9.1 (unstable)]



Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

 Keep the following packages at their current version:
1) cnee [3.19-9 (now, stable, testing)]   
2) libxnee0 [3.19-9 (now, stable, testing)]   



Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

 Remove the following packages:
1) cnee [3.19-9 (now, stable, testing)]



Accept this solution? [Y/n/q/?] n

*** No more solutions available ***

No solutions are found, while with apt:

qaa:~> apt install -s cnee
[...]
The following additional packages will be installed:
  libxnee0t64
Suggested packages:
  xnee-doc
The following packages will be REMOVED:
  libxnee0
The following NEW packages will be installed:
  libxnee0t64
The following packages will be upgraded:
  cnee
1 upgraded, 1 newly installed, 1 to remove and 263 not upgraded.
Inst cnee [3.19-9] (3.19-9.1 Debian:unstable [amd64]) []
Remv libxnee0 [3.19-9] []
Inst libxnee0t64 (3.19-9.1 Debian:unstable [amd64])
Conf cnee (3.19-9.1 Debian:unstable [amd64])
Conf libxnee0t64 (3.19-9.1 Debian:unstable [amd64])

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1064969: apt: can't upgrade with aptitude

[Vincent Lefevre via Aptitude-devel]

On 2024-02-28 17:28:51 +0100, Sven Joachim wrote:
> No, in this case it is a problem with aptitude's resolver which
> manifests itself due to the following configuration setting:
> 
> > Aptitude::ProblemResolver::SolutionCost "safety, removals";
> 
> This does cause aptitude to hold apt back by default, rather than remove
> libapt-pkg6.0.  You can press 'n' at the prompt, the next solution
> aptitude then suggests is to upgrade apt.

Well, this is really stupid! aptitude sometimes wants to remove
lots of packages just to avoid the package renames, while apt
proposes a right solution (with some easy help)!

For instance, with apt:

cventin:~> apt install -s gir1.2-atk-1.0 libwine:i386
[...]
libwine:i386 is already the newest version (9.0~repack-4).
libwine:i386 set to manually installed.
The following additional packages will be installed:
  at-spi2-common at-spi2-core gir1.2-atspi-2.0 gir1.2-girepository-2.0-dev
  gobject-introspection gobject-introspection-bin libatk-adaptor
  libatk-bridge2.0-0t64 libatk-bridge2.0-dev libatk1.0-0t64 libatk1.0-dev
  libatspi2.0-0t64 libatspi2.0-dev libgirepository-1.0-dev
  libgirepository1.0-dev libglib2.0-0t64 libglib2.0-0t64:i386 libglib2.0-bin
  libglib2.0-data libglib2.0-dev libglib2.0-dev-bin python3-mako
  python3-markdown python3-markupsafe
Suggested packages:
  libgirepository1.0-doc low-memory-monitor low-memory-monitor:i386
  libglib2.0-doc python-mako-doc python3-beaker python-markdown-doc
The following packages will be REMOVED:
  libatk-bridge2.0-0 libatk1.0-0 libatspi2.0-0 libglib2.0-0 libglib2.0-0:i386
The following NEW packages will be installed:
  gir1.2-girepository-2.0-dev gobject-introspection gobject-introspection-bin
  libatk-bridge2.0-0t64 libatk1.0-0t64 libatspi2.0-0t64
  libgirepository-1.0-dev libgirepository1.0-dev libglib2.0-0t64
  libglib2.0-0t64:i386 python3-mako python3-markdown python3-markupsafe
The following packages will be upgraded:
  at-spi2-common at-spi2-core gir1.2-atk-1.0 gir1.2-atspi-2.0 libatk-adaptor
  libatk-bridge2.0-dev libatk1.0-dev libatspi2.0-dev libglib2.0-bin
  libglib2.0-data libglib2.0-dev libglib2.0-dev-bin
12 upgraded, 13 newly installed, 5 to remove and 263 not upgraded.
[...]

Note that all the removes correspond to package renames.

I had to provide libwine:i386, otherwise apt wanted to remove it.

With aptitude, I need to use 'n' 21 times until I reach the right
solution (with an unmet dependency after that, which can be resolved,
though).

cventin:~> aptitude install -s gir1.2-atk-1.0 libwine:i386
libwine:i386 is already installed at the requested version (9.0~repack-4)
libwine:i386 is already installed at the requested version (9.0~repack-4)
The following packages will be upgraded:
  at-spi2-common gir1.2-atk-1.0{b} 
2 packages upgraded, 0 newly installed, 0 to remove and 273 not upgraded.
Need to get 190 kB of archives. After unpacking 0 B will be used.
The following packages have unmet dependencies:
 libatk1.0-dev : Depends: gir1.2-atk-1.0 (= 2.50.0-1+b1) but 2.51.90-1 is to be 
installed
 gir1.2-atk-1.0 : Depends: libatk1.0-0t64 (>= 2.51.90) but it is not going to 
be installed
The following actions will resolve these dependencies:

 Keep the following packages at their current version:
1) gir1.2-atk-1.0 [2.50.0-1+b1 (now, testing)]



Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

  Remove the following packages: 
1)  libatk-bridge2.0-dev [2.50.0-1+b1 (now, testing)]
2)  libatk1.0-0 [2.50.0-1+b1 (now, testing, unstable)]   
3)  libatk1.0-dev [2.50.0-1+b1 (now, testing)]   
4)  libglib2.0-0 [2.78.4-1 (now, testing, unstable)] 
5)  libglib2.0-0:i386 [2.78.4-1 (now, testing, unstable)]
6)  libgtk-3-dev [3.24.41-1 (now, testing)]  
7)  libgtk2.0-dev [2.24.33-3 (now, testing)] 

  Install the following packages:
8)  libatk1.0-0t64 [2.51.90-1 (unstable)]
9)  libglib2.0-0t64 [2.78.4-2.1 (unstable)]  
10) libglib2.0-0t64:i386 [2.78.4-2.1 (unstable)] 

  Upgrade the following packages:
11) libglib2.0-bin [2.78.4-1 (now, testing) -> 2.78.4-2.1 (unstable)]
12) libglib2.0-dev [2.78.4-1 (now, testing) -> 2.78.4-2.1 (unstable)]
13) libglib2.0-dev-bin [2.78.4-1 (now, testing) -> 2.78.4-2.1 (unstable)]



Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

  Remove the following packages: 
1)  libatk-bridge2.0-dev [2.50.0-1+b1 (now, testing)]
2)  libatk1.0-0 [2.50.0-1+b1 (now, testing, unstable)]   
3)  libatk1.0-dev 

[Aptitude-devel] Bug#1064969: apt: can't upgrade with aptitude

[Vincent Lefevre]

On 2024-02-29 14:11:41 +0900, Simon Richter wrote:
> Hi,
> 
> On 2/28/24 23:49, Vincent Lefevre wrote:
> 
> > # aptitude install apt
> > The following packages will be upgraded:
> >apt{b} apt-doc
> > 2 packages upgraded, 0 newly installed, 0 to remove and 180 not upgraded.
> > Need to get 1622 kB of archives. After unpacking 0 B will be used.
> > The following packages have unmet dependencies:
> >   apt : Depends: libapt-pkg6.0t64 (>= 2.7.12+nmu1) but it is not going to 
> > be installed
> >   apt-utils : Depends: apt (= 2.7.12) but 2.7.12+nmu1 is to be installed
> > The following actions will resolve these dependencies:
> > 
> >   Keep the following packages at their current version:
> > 1) apt [2.7.12 (now, testing)]
> 
> That is a valid possible resolution. Presumably, if you reject this
> resolution, it will instead propose to upgrade apt-utils, install
> libapt-pkg6.0t64 and remove libapt-pkg6.0.
> 
> Since that is a larger change, the conservative proposal comes first.
> 
> apt-utils has a versioned dependency on apt, which means upgrading
> apt alone (which you requested)

No, this requests to upgrade *all* packages of the same source
(well, at least in the TUI, which I normally use, but there is
the same issue in the TUI).

> breaks another "unrelated" package. There has been some debate that
> resolvers should favour upgrading all binaries that are built from
> the same source together, but that has not been implemented yet, and
> it is unclear if that would have changed anything here.

See above, but in any case...

> > So, I suppose that this is also the case for aptitude: if aptitude
> > cannot upgrade just because of a rename, then this is a problem in
> > the involved packages.
> 
> Note that you haven't requested an "upgrade" (which would likely have
> worked, because it would have switched both apt and apt-utils to the new
> version, and the remaining involved packages were automatically installed as
> dependencies of the packages being upgraded).

This doesn't work with an upgrade either:

qaa:~> aptitude upgrade -s
Resolving dependencies...
The following NEW packages will be installed:
  libatrildocument3t64{a} libatrilview3t64{a} libboost-chrono1.83.0t64{a} 
  libcupsfilters1t64{a} libevdocument3-4t64{a} libevemu3t64{a} 
  libevview3-3t64{a} libfontembed1t64{a} libgxps2t64{a} 
  libtss2-mu-4.0.1-0t64{a} 
The following packages will be REMOVED:
  libatrildocument3{u} libatrilview3{u} libboost-chrono1.83.0{u} 
  libcupsfilters1{u} libevdocument3-4{u} libevemu3{u} libevview3-3{u} 
  libfontembed1{u} libgxps2{u} libtss2-mu0{u} 
The following packages will be upgraded:
  apt-doc at-spi2-common atril atril-common cups-browsed cups-filters 
  cups-filters-core-drivers evemu-tools evince evince-common 
  evolution-data-server-common gir1.2-pango-1.0 glib-networking 
  glib-networking-common glib-networking-services glibc-doc-reference 
  gnome-calendar gnome-remote-desktop gnome-settings-daemon 
  gnome-settings-daemon-common gnome-text-editor libboost-atomic1.83-dev 
  libboost-atomic1.83.0 libboost-chrono1.83-dev libboost-date-time1.83-dev 
  libboost-date-time1.83.0 libboost-filesystem1.83-dev 
  libboost-filesystem1.83.0 libboost-iostreams1.83.0 libboost-locale1.83.0 
  libboost-program-options1.83-dev libboost-program-options1.83.0 
  libboost-regex1.83-dev libboost-regex1.83.0 
  libboost-serialization1.83-dev libboost-serialization1.83.0 
  libboost-system1.83-dev libboost-system1.83.0 libboost-thread1.83-dev 
  libboost-thread1.83.0 libboost1.83-dev libglib2.0-data liblzma-dev 
  liblzma5 libnss-myhostname libnss-systemd libpam-runtime libpam-systemd 
  libpango-1.0-0 libpango1.0-dev libpangocairo-1.0-0 libpangoft2-1.0-0 
  libpangoxft-1.0-0 libsystemd-shared libsystemd0 libtss2-esys-3.0.2-0 
  libtss2-rc0 libtss2-sys1 libtss2-tcti-cmd0 libtss2-tcti-device0 
  libtss2-tcti-libtpms0 libtss2-tcti-mssim0 libtss2-tcti-spi-helper0 
  libtss2-tcti-swtpm0 libtss2-tctildr0 libudev1 pango1.0-tools sa-compile 
  spamassassin spamc spamd systemd systemd-dev systemd-sysv 
  systemd-timesyncd udev xz-utils 
The following packages are RECOMMENDED but will NOT be installed:
  evolution-data-server 
77 packages upgraded, 10 newly installed, 10 to remove and 22 not upgraded.
Need to get 37.2 MB/43.6 MB of archives. After unpacking 728 kB will be used.

apt-doc is proposed for upgrade, but not apt.

What's strange is that it appears to work for some packages, e.g.
libatrildocument3 replaced by libatrildocument3t64, but not for
other ones (e.g. libapt-pkg6.0 replaced by libapt-pkg6.0t64).

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1064969: apt: can't upgrade with aptitude

[Vincent Lefevre]

On 2024-02-28 18:32:20 +0100, Vincent Lefevre wrote:
> OK, but it appears that now, there are *many* other packages in
> a similar situation, and sometimes, aptitude wants to remove a
> potentially important package (see below). The resolution should
> be automatic in case of package rename.
> 
> # aptitude install libglib2.0-dev

I would add that in this apparently more complex case, apt
(e.g. "apt install libglib2.0-dev" or "apt dist-upgrade") is
far worse than aptitude as it wants to remove wine32:i386.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1064969: apt: can't upgrade with aptitude

[Vincent Lefevre]

On 2024-02-28 17:28:51 +0100, Sven Joachim wrote:
> On 2024-02-28 15:49 +0100, Vincent Lefevre wrote:
> > So, I suppose that this is also the case for aptitude: if aptitude
> > cannot upgrade just because of a rename, then this is a problem in
> > the involved packages.
> 
> No, in this case it is a problem with aptitude's resolver which
> manifests itself due to the following configuration setting:
> 
> > Aptitude::ProblemResolver::SolutionCost "safety, removals";
> 
> This does cause aptitude to hold apt back by default, rather than
> remove libapt-pkg6.0.

The goal of this configuration setting (which was given in the
debian-user list in the past) was to prevent aptitude from removing
packages with no replacement (e.g. firefox, libreoffice, and so on).
Here, the libapt-pkg6.0 package has been renamed. I hope that you
can understand that this is a completely different situation.

> You can press 'n' at the prompt, the next solution aptitude then
> suggests is to upgrade apt.

OK, but it appears that now, there are *many* other packages in
a similar situation, and sometimes, aptitude wants to remove a
potentially important package (see below). The resolution should
be automatic in case of package rename.

# aptitude install libglib2.0-dev
The following packages will be REMOVED:
  libglib2.0-dev-bin{u}
The following packages will be upgraded:
  libglib2.0-data libglib2.0-dev{b}
2 packages upgraded, 0 newly installed, 1 to remove and 61 not upgraded.
Need to get 2865 kB of archives. After unpacking 716 kB will be freed.
The following packages have unmet dependencies:
 libglib2.0-dev : Depends: libglib2.0-0t64 (= 2.78.4-2) but it is not going to 
be installed
  Depends: libglib2.0-bin (= 2.78.4-2) but 2.78.4-1 is 
installed and it is kept back
  Depends: libglib2.0-dev-bin (= 2.78.4-2) but it is not going 
to be installed
The following actions will resolve these dependencies:

 Keep the following packages at their current version:
1) libglib2.0-dev [2.78.4-1 (now, testing)]
2) libglib2.0-dev-bin [2.78.4-1 (now, testing)]

Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

 Remove the following packages:
1) libglib2.0-0 [2.78.4-1 (now, testing, unstable)]
2) libglib2.0-0:i386 [2.78.4-1 (now, testing, unstable)]
3) libglib2.0-bin [2.78.4-1 (now, testing)]

 Install the following packages:
4) libglib2.0-0t64 [2.78.4-2 (unstable)]
5) libglib2.0-0t64:i386 [2.78.4-2 (unstable)]
6) libglib2.0-bin:i386 [2.78.4-2 (unstable)]

 Upgrade the following packages:
7) libglib2.0-dev-bin [2.78.4-1 (now, testing) -> 2.78.4-2 (unstable)]

AFAIK, replacing libglib2.0-bin by libglib2.0-bin:i386 is not
equivalent.

With an explicit package list, aptitude immediately gives an
acceptable solution:

$ aptitude install -s libglib2.0-dev libglib2.0-bin libglib2.0-dev-bin 
libglib2.0-0t64 libglib2.0-0t64:i386
The following NEW packages will be installed:
  libglib2.0-0t64 libglib2.0-0t64:i386 
The following packages will be REMOVED:
  libglib2.0-0{a} libglib2.0-0:i386{a} 
The following packages will be upgraded:
  libglib2.0-bin libglib2.0-data libglib2.0-dev libglib2.0-dev-bin 

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1064969: apt: can't upgrade with aptitude

[Vincent Lefevre via Aptitude-devel]

On 2024-02-28 15:56:56 +0100, Julian Andres Klode wrote:
> aptitude is not our chosen tool for distribution upgrades, as such
> failures there are not release critical for the packages. So while
> this is release critical for aptitude, it's a wishlist bug for apt
> that probably would end up being closed.
> 
> I do believe the correct syntax for aptitude would be to use
> 
> aptitude upgrade apt
> 
> though

OK, though this is much slower. But still, apt is not upgraded
with this solution (and there is no way to choose another action
manually):

# aptitude upgrade apt
Resolving dependencies...
The following packages have been kept back:
  apt
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 182 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1061734: aptitude: in TUI, incorrect "will be automatically removed because of dependency errors" message

[Vincent Lefevre]

Note that there was a similar bug in the past (2005, fixed in 2016):

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=342835

with title:

  aptitude: "X will be automatically removed because of dependency errors:"
  then no errors shown

On 2024-01-29 11:20:45 +0100, Vincent Lefevre wrote:
> When I choose to upgrade swig from the TUI, I get the incorrect message
> 
> 
> swig4.0 (remove, 4.1.0-0.3) will be automatically removed because of
> dependency errors:
> 
> 
> with nothing else.

I cannot reproduce this issue on another machine, which doesn't have
a foreign architecture. I get just after 'g' and putting the cursor
over the swig4.0 line:


swig4.0 (remove, 4.1.0-0.3) will be automatically removed because of dependency
errors:

  * swig (upgrade, 4.1.0-0.3 -> 4.2.0-1) conflicts with swig4.0


However, AFAIK, it will be automatically removed not because of the
conflict, but because the new swig package no longer depends on it
(on both machines, swig4.0 is marked as automatically installed).

This is a different message from

> Then, when I type ':' over the swig4.0 line, this message changes to:
> 
> 
> swig4.0 (remove, 4.1.0-0.3) was installed automatically; it is being removed
> because all of the packages which depend upon it are being removed:
> 
>   * swig (upgrade, 4.1.0-0.3 -> 4.2.0-1) depends on swig4.0 (>= 4.1.0-0.3)
> (provided by swig4.0:i386 4.1.0-0.3)
> 

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1061734: aptitude: in TUI, incorrect "will be automatically removed because of dependency errors" message

[Vincent Lefevre]

Package: aptitude
Version: 0.8.13-5+b1
Severity: normal

When I choose to upgrade swig from the TUI, I get the incorrect message


swig4.0 (remove, 4.1.0-0.3) will be automatically removed because of dependency
errors:


with nothing else.

With more details:

I currently have

i   swig   4.1.0-0.34.2.0-1

Over this line, I type '+', so that I get:

aptitude 0.8.13 @ cventinDisk: -184 kB   DL: 1429 kB
[...]
iu  swig +5509 kB  4.1.0-0.34.2.0-1

Now, I type 'g', and I get:

--\ Packages to be upgraded (1) 
iu  swig +5509 kB  4.1.0-0.34.2.0-1 
--\ Packages being deleted due to unsatisfied dependencies (1)
idA swig4.0  -5693 kB  4.1.0-0.34.1.0-0.3   
--\ Packages being held back (15)
[...]

Over the swig line, I get:


swig (upgrade, 4.1.0-0.3 -> 4.2.0-1) will be upgraded from version 4.1.0-0.3 to
version 4.2.0-1.


Over the swig4.0 line, I get:


swig4.0 (remove, 4.1.0-0.3) will be automatically removed because of dependency
errors:


with nothing else. Without any error message, this doesn't make sense.

Then, when I type ':' over the swig4.0 line, this message changes to:


swig4.0 (remove, 4.1.0-0.3) was installed automatically; it is being removed
because all of the packages which depend upon it are being removed:

  * swig (upgrade, 4.1.0-0.3 -> 4.2.0-1) depends on swig4.0 (>= 4.1.0-0.3)
(provided by swig4.0:i386 4.1.0-0.3)


Now this is almost correct. I don't understand the ":i386". This is
a configured foreign architecture on this machine, but this package
is not installed:

cventin:~> dpkg -l | grep swig
ii  swig   4.1.0-0.3
all  Generate scripting interfaces to C/C++ code
ii  swig4.04.1.0-0.3
amd64Generate scripting interfaces to C/C++ code

Note that with the currently installed swig package:

Package: swig
Version: 4.1.0-0.3
[...]
Architecture: all
Replaces: swig2.0
Depends: swig4.0 (>= 4.1.0-0.3)
Suggests: swig-doc, swig-examples
Conflicts: swig2.0

and with the new version:

Package: swig
Version: 4.2.0-1
[...]
Architecture: amd64
Replaces: swig4.0
Depends: libc6 (>= 2.34), libgcc-s1 (>= 3.0), libpcre2-8-0 (>= 10.22), 
libstdc++6 (>= 13.1)
Suggests: swig-doc, swig-examples
Conflicts: swig4.0

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

aptitude version information:
aptitude 0.8.13
Compiler: g++ 13.2.0
Compiled against:
  apt version 6.0.0
  NCurses version 6.4
  libsigc++ version: 2.12.1
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.4.20240113
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7ffeeaddb000)
libgtk3-nocsd.so.0 => /lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 
(0x7fa687a8f000)
libapt-pkg.so.6.0 => /lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7fa68720)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7fa687a55000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7fa6875cb000)
libsigc-2.0.so.0 => /lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7fa687a4c000)
libcwidget.so.4 => /lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7fa6874c9000)
libsqlite3.so.0 => /lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7fa68708a000)
libboost_iostreams.so.1.83.0 => 
/lib/x86_64-linux-gnu/libboost_iostreams.so.1.83.0 (0x7fa6874af000)
libxapian.so.30 => /lib/x86_64-linux-gnu/libxapian.so.30 
(0x7fa686e0)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fa686a0)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fa686d21000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fa687482000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fa68681e000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fa687a43000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fa68747d000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fa68745e000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7fa68744b000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 

[Aptitude-devel] Bug#1059071: aptitude: wants to remove a package, breaking a dependency

[Vincent Lefevre]

I've noticed that this isn't included by default. I'm using

Aptitude::ProblemResolver::SolutionCost "safety, removals";

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1056959: aptitude: can't upgrade wireshark to 4.2.0-1 without explicitly upgrading wireshark-common or removing wireshark-qt

[Vincent Lefevre]

Package: aptitude
Version: 0.8.13-5
Severity: normal

With the aptitude TUI or command line, it is not possible to upgrade
wireshark to 4.2.0-1 without explicitly upgrading wireshark-common
too or removing wireshark-qt. With both interfaces, the proposed
default is to keep both wireshark and wireshark-qt at their current
version, and for the alternative actions, aptitude never proposes to
upgrade wireshark.

Note that the wireshark package now has:

Replaces: wireshark-gtk (<< 3.0.0~), wireshark-qt
Breaks: wireshark-gtk (<< 3.0.0~), wireshark-qt

That's why wireshark-qt is no longer useful and could be safely
removed.

For instance, with the command line:

# aptitude install wireshark
The following NEW packages will be installed:
  libnghttp3-3{a} libopencore-amrnb0{a} libqt6dbus6{a} libqt6gui6{a} 
  libqt6multimedia6{a} libqt6network6{a} libqt6opengl6{a} 
  libqt6printsupport6{a} libqt6qml6{a} libqt6qmlmodels6{a} libqt6quick6{a} 
  libqt6waylandclient6{a} libqt6waylandcompositor6{a} 
  libqt6waylandeglclienthwintegration6{a} 
  libqt6waylandeglcompositorhwintegration6{a} libqt6widgets6{a} 
  libqt6wlshellintegration6{a} libts0{a} libwireshark17{a} libwiretap14{a} 
  libwsutil15{a} qt6-gtk-platformtheme{a} qt6-qpa-plugins{a} qt6-wayland{a} 
The following packages will be REMOVED:
  wireshark-qt{a} 
The following packages will be upgraded:
  libwireshark-data wireshark{b} wireshark-doc 
3 packages upgraded, 24 newly installed, 1 to remove and 74 not upgraded.
Need to get 48.7 MB of archives. After unpacking 172 MB will be used.
The following packages have unmet dependencies:
 wireshark : Depends: wireshark-common (= 4.2.0-1) but 4.0.11-1 is installed 
and it is kept back
The following actions will resolve these dependencies:

 Keep the following packages at their current version:
1) wireshark [4.0.11-1 (now)] 
2) wireshark-qt [4.0.11-1 (now, unstable)]

Accept this solution? [Y/n/q/?]

BTW, concerning the unmet dependency

 wireshark : Depends: wireshark-common (= 4.2.0-1) but 4.0.11-1 is installed 
and it is kept back

why doesn't aptitude propose to upgrade wireshark-common?
That's the obvious solution!

Indeed, the following works:

# aptitude install wireshark wireshark-common
The following NEW packages will be installed:
  libnghttp3-3{a} libopencore-amrnb0{a} libqt6dbus6{a} libqt6gui6{a} 
  libqt6multimedia6{a} libqt6network6{a} libqt6opengl6{a} 
  libqt6printsupport6{a} libqt6qml6{a} libqt6qmlmodels6{a} libqt6quick6{a} 
  libqt6waylandclient6{a} libqt6waylandcompositor6{a} 
  libqt6waylandeglclienthwintegration6{a} 
  libqt6waylandeglcompositorhwintegration6{a} libqt6widgets6{a} 
  libqt6wlshellintegration6{a} libts0{a} libwireshark17{a} libwiretap14{a} 
  libwsutil15{a} qt6-gtk-platformtheme{a} qt6-qpa-plugins{a} qt6-wayland{a} 
The following packages will be REMOVED:
  libwireshark16{u} libwiretap13{u} libwsutil14{u} wireshark-qt{a} 
The following packages will be upgraded:
  libwireshark-data wireshark wireshark-common wireshark-doc 
4 packages upgraded, 24 newly installed, 4 to remove and 73 not upgraded.
Need to get 49.4 MB of archives. After unpacking 57.3 MB will be used.
Do you want to continue? [Y/n/?] 

and so does

# aptitude install wireshark wireshark-qt-
The following NEW packages will be installed:
  libnghttp3-3{a} libopencore-amrnb0{a} libqt6dbus6{a} libqt6gui6{a} 
  libqt6multimedia6{a} libqt6network6{a} libqt6opengl6{a} 
  libqt6printsupport6{a} libqt6qml6{a} libqt6qmlmodels6{a} libqt6quick6{a} 
  libqt6waylandclient6{a} libqt6waylandcompositor6{a} 
  libqt6waylandeglclienthwintegration6{a} 
  libqt6waylandeglcompositorhwintegration6{a} libqt6widgets6{a} 
  libqt6wlshellintegration6{a} libts0{a} libwireshark17{a} libwiretap14{a} 
  libwsutil15{a} qt6-gtk-platformtheme{a} qt6-qpa-plugins{a} qt6-wayland{a} 
The following packages will be REMOVED:
  libwireshark16{u} libwiretap13{u} libwsutil14{u} wireshark-qt 
The following packages will be upgraded:
  libwireshark-data wireshark wireshark-common wireshark-doc 
4 packages upgraded, 24 newly installed, 4 to remove and 73 not upgraded.
Need to get 49.4 MB of archives. After unpacking 57.3 MB will be used.
Do you want to continue? [Y/n/?] 

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

aptitude version information:
aptitude 0.8.13
Compiler: g++ 12.1.0
Compiled against:
  apt version 6.0.0
  NCurses version 6.3
  libsigc++ version: 2.10.8
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.4.20231121
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7ffdb77dd000)
libgtk3-nocsd.so.0 => /lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 
(0x7f8a75fd5000)
libapt-pkg.so.6.0 => /lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7f8a7560)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7f8a75f9b000)

[Aptitude-devel] Bug#1051923: aptitude: incorrect dependency resolution for ghostscript vs virtual package ghostscript-x

[Vincent Lefevre]

And ghostscript 10.02.0~dfsg-2 has just appeared. Its changelog says

  * declare that ghostscript replaces older ghostscript-x

so that now

Package: ghostscript
Version: 10.02.0~dfsg-2
Installed-Size: 180
Maintainer: Debian QA Group 
Architecture: amd64
Replaces: ghostscript-x (<< 10.02.0~dfsg-1)
Provides: ghostscript-x (= 10.02.0~dfsg-2), postscript-viewer

but this has no effect on aptitude.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1051923: aptitude: incorrect dependency resolution for ghostscript vs virtual package ghostscript-x

[Vincent Lefevre]

Note that just in case this would matter, I have several packages
that depend on ghostscript-x: gv pspresent xournal

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1051923: aptitude: incorrect dependency resolution for ghostscript vs virtual package ghostscript-x

[Vincent Lefevre]

Package: aptitude
Version: 0.8.13-5
Severity: normal

I have the following ghostscript-related packages installed:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture Description
+++-===-==--===
ii  ghostscript 10.01.2~dfsg-1 amd64interpreter for the 
PostScript language and for PDF
ii  ghostscript-doc 10.01.2~dfsg-1 all  interpreter for the 
PostScript language and for PDF - Documentation
ii  ghostscript-x:amd64 10.01.2~dfsg-1 amd64transitional package for 
ghostscript
ii  libgs-common10.01.2~dfsg-1 all  interpreter for the 
PostScript language and for PDF - ICC profiles
ii  libgs10:amd64   10.01.2~dfsg-1 amd64interpreter for the 
PostScript language and for PDF - Library
ii  libgs10-common  10.01.2~dfsg-1 all  interpreter for the 
PostScript language and for PDF - common files

Version 10.02.0~dfsg-1 is available, but if I try '+' over "ghostscript"
in the aptitude TUI to ask for an upgrade of this package, I get:

iu  ghostscript10.01.2~dfsg-1   10.02.0~dfsg-1
[...]
ghostscript (upgrade, 10.01.2~dfsg-1 -> 10.02.0~dfsg-1) will be upgraded from  ▒
version 10.01.2~dfsg-1 to version 10.02.0~dfsg-1.  ▒
   ▒
The following packages depend on version 10.01.2~dfsg-1 of ghostscript, and▒
will be broken if it is upgraded.  ▒
   ▒
  * ghostscript-x (held/unchanged, 10.01.2~dfsg-1) depends on ghostscript (=   ▒
10.01.2~dfsg-1) (provided by ghostscript:i386 10.01.2~dfsg-1)  ▒

though ghostscript:i386 isn't installed; so, this doesn't make sense.
Since ghostscript-x is now provided by ghostscript, aptitude should
have proposed to remove this package as it would still be there as a
virtual package.

Package: ghostscript
Version: 10.02.0~dfsg-1
Installed-Size: 180
Maintainer: Debian QA Group 
Architecture: amd64
Provides: ghostscript-x (= 10.02.0~dfsg-1), postscript-viewer
  ^

and in the ghostscript changelog:

ghostscript (10.02.0~dfsg-1) unstable; urgency=medium
[...]
  * drop obsolete binary packages ghostscript-x libgs9-common;
have binary package ghostscript provide ghostscript-x

Note that I have:

Aptitude::ProblemResolver::SolutionCost "safety, removals";

And from the command line:

# aptitude install ghostscript
The following packages will be upgraded: 
  ghostscript ghostscript-doc libgs-common libgs10 libgs10-common 
5 packages upgraded, 0 newly installed, 0 to remove and 59 not upgraded.
Need to get 14.8 MB of archives. After unpacking 335 kB will be freed.
The following packages have unmet dependencies:
 ghostscript-x : Depends: ghostscript (= 10.01.2~dfsg-1) but 10.02.0~dfsg-1 is 
to be installed
The following actions will resolve these dependencies:

 Keep the following packages at their current version: 
1) ghostscript [10.01.2~dfsg-1 (now, testing)] 
2) libgs10 [10.01.2~dfsg-1 (now, testing)] 
3) libgs10-common [10.01.2~dfsg-1 (now, testing, unstable)]

Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

 Remove the following packages:   
1) ghostscript-x [10.01.2~dfsg-1 (now, testing, unstable)]

Note that this solution would be OK only because ghostscript-x will
become a virtual package, but aptitude doesn't give this information,
so that this is misleading.

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

aptitude version information:
aptitude 0.8.13
Compiler: g++ 12.1.0
Compiled against:
  apt version 6.0.0
  NCurses version 6.3
  libsigc++ version: 2.10.8
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.4.20230625
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7fffc21a2000)
libgtk3-nocsd.so.0 => /usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 
(0x7f37ec46d000)
libapt-pkg.so.6.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7f37ebc0)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7f37ec434000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7f37ebfcb000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f37ec42b000)
libcwidget.so.4 => /usr/lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7f37ebed9000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 

[Aptitude-devel] Bug#1042897: aptitude: viewing a package's changelog from the TUI outputs a warning that is immediately erased

[Vincent Lefevre]

On 2023-08-05 13:04:56 +0200, Sven Joachim wrote:
> Ah yes, Guillem implemented the "verbose" option three years ago in
> reaction to #967911.  And it could not be used back then because the
> dpkg version offering it was only uploaded several months later, but now
> it certainly can be used. :-)
> 
> Would you like to submit a merge request on salsa for the master branch?

OK, done here:
  https://salsa.debian.org/apt-team/aptitude/-/merge_requests/21

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1042897: aptitude: viewing a package's changelog from the TUI outputs a warning that is immediately erased

[Vincent Lefevre]

On 2023-08-04 18:06:24 +0200, Sven Joachim wrote:
> On 2023-08-04 01:57 +0200, Vincent Lefevre wrote:
> 
> > On 2023-08-03 16:52:07 +0200, Sven Joachim wrote:
[...]
> >> It should prevent these errors from showing up in the first place.
> >
> > If aptitude knows what to do (or may ignore the issue), yes.
> 
> I was a bit imprecise, actually I meant that aptitude-changelog-parser
> should not emit these warnings to stderr, which is what #967911 is about.
> 
> >> See #967911, which has been tagged "pending" almost three years ago. :-(
> >
> > I forgot about this one.
> 
> Since the screen flashes created by aptitude-changelog-parser's warnings
> have been annoying me for so long, I have now created a merge request to
> cherry-pick the fix for unstable:
> 
> https://salsa.debian.org/apt-team/aptitude/-/merge_requests/20

First, I don't understand

  But we cannot currently change that verbose default when using
  changelog_parse() from Dpkg::Changelog::Parse.

in the patch. The following works as expected:

--- a/aptitude-changelog-parser 2022-08-06 05:45:53.0 +0200
+++ b/aptitude-changelog-parser 2023-08-05 10:55:39.291911672 +0200
@@ -15,6 +15,7 @@
 # Usage: aptitude-changelog-parser [ []]
 
 my %opts;
+$opts{verbose} = 0;
 if (scalar @ARGV >= 1) {
 $opts{file} = shift @ARGV;
 }

This silences warnings from

sub parse_error {
my ($self, $file, $line_nr, $error, $line) = @_;

push @{$self->{parse_errors}}, [ $file, $line_nr, $error, $line ];

if ($self->{verbose}) {
if ($line) {
warning("%20s(l$line_nr): $error\nLINE: $line", $file);
} else {
warning("%20s(l$line_nr): $error", $file);
}
}
}

in /usr/share/perl5/Dpkg/Changelog.pm.

Now, silenting such warnings for changelog_parse() will fix issues
like this one, but it will not fix the general problem with warnings
and errors.

For instance, aptitude-changelog-parser has

eval {
require Dpkg::Changelog::Parse;
Dpkg::Changelog::Parse->import();
1;
} or do {
warn "warning: Dpkg::Changelog::Parse not present, install libdpkg-perl\n";
exit 0;
};

at the beginning, and this warning, which is important and must still
be output, will still quickly disappear. BTW, the "exit 0;" is also
incorrect, but that's another issue (bug 1043050, which I've just
reported).

And concerning errors, /usr/share/perl5/Dpkg/Changelog/Parse.pm has

error(g_('changelog format %s is unknown: %s'), $format, $@) if $@;
error(g_('changelog format %s is not a Dpkg::Changelog class'), $format)
unless $changes->isa('Dpkg::Changelog');

and

error(g_('unknown output format %s'), $options{format});

In /usr/share/perl5/Dpkg/ErrorHandling.pm, this corresponds to

sub error($;@)
{
die report(REPORT_ERROR, @_);
}

This will not be silenced by "$SIG{__WARN__} = sub {};" like in your
patch. I don't think these fatal errors should be silenced at all,
but currently, they will also quickly disappear.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1043050: aptitude: incorrect exit value in aptitude-changelog-parser

[Vincent Lefevre]

Package: aptitude
Version: 0.8.13-5
Severity: normal
Tags: patch

/usr/bin/aptitude-changelog-parser has:

eval {
require Dpkg::Changelog::Parse;
Dpkg::Changelog::Parse->import();
1;
} or do {
warn "warning: Dpkg::Changelog::Parse not present, install libdpkg-perl\n";
exit 0;
};

But in case the second part is executed, aptitude displays nothing,
and the user has the impression that it is still waiting for data.
Changing the exit value to 1 makes aptitude display the old (cached?)
logs. See attached patch.

Note: there's still the issue that the warning disappears immediately
(this is similar to bug 1042897).

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

aptitude version information:
aptitude 0.8.13
Compiler: g++ 12.1.0
Compiled against:
  apt version 6.0.0
  NCurses version 6.3
  libsigc++ version: 2.10.8
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.4.20230625
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7ffc1f9ed000)
libgtk3-nocsd.so.0 => /usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 
(0x7fc184ae6000)
libapt-pkg.so.6.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7fc18420)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7fc184aad000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7fc184a78000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7fc184a6f000)
libcwidget.so.4 => /usr/lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7fc18450e000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7fc184099000)
libboost_iostreams.so.1.74.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.74.0 (0x7fc184a55000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7fc183e0)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fc184a5)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fc183a0)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fc18442f000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fc184a2a000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fc18381e000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fc184a25000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fc18407a000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7fc18441c000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fc18404b000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7fc183dda000)
libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 
(0x7fc183d1a000)
libudev.so.1 => /usr/lib/x86_64-linux-gnu/libudev.so.1 
(0x7fc183ce8000)
libsystemd.so.0 => /usr/lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7fc18373f000)
libgcrypt.so.20 => /usr/lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7fc1835f9000)
libxxhash.so.0 => /usr/lib/x86_64-linux-gnu/libxxhash.so.0 
(0x7fc184036000)
/lib64/ld-linux-x86-64.so.2 (0x7fc184b17000)
libuuid.so.1 => /usr/lib/x86_64-linux-gnu/libuuid.so.1 
(0x7fc183cde000)
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7fc183cd2000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7fc183caa000)

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aptitude depends on:
ii  aptitude-common   0.8.13-5
ii  libapt-pkg6.0 2.7.3
ii  libboost-iostreams1.74.0  1.74.0+ds1-22
ii  libc6 2.37-6
ii  libcwidget4   0.5.18-6
ii  libgcc-s1 13.2.0-1
ii  libncursesw6  6.4+20230625-2
ii  libsigc++-2.0-0v5 2.12.0-1
ii  libsqlite3-0  3.42.0-1
ii  libstdc++613.2.0-1
ii  libtinfo6 6.4+20230625-2
ii  libxapian30   1.4.22-1

Versions of packages aptitude recommends:
ii  libdpkg-perl1.21.22
ii  sensible-utils  0.0.20

Versions of packages aptitude suggests:
ii  apt-xapian-index0.53
ii  aptitude-doc-en [aptitude-doc]  0.8.13-5
pn  debtags 
ii  tasksel 3.73

-- no debconf information

-- 
Vincent 

[Aptitude-devel] Bug#1042897: aptitude: viewing a package's changelog from the TUI outputs a warning that is immediately erased

[Vincent Lefevre]

On 2023-08-03 16:52:07 +0200, Sven Joachim wrote:
> On 2023-08-02 15:51 +0200, Vincent Lefevre wrote:
> > Package: aptitude
> > Version: 0.8.13-5
> > Severity: normal
> >
> > When I use "C" (View a package's changelog) on clang-15 from the
> > aptitude TUI, I get a warning that is immediately erased, so that
> > it is impossible to read it.
> >
> > I suppose that aptitude should redirect stderr from
> > aptitude-changelog-parser so that it can display its contents
> > (when non empty) in a clear way.
> 
> It should prevent these errors from showing up in the first place.

If aptitude knows what to do (or may ignore the issue), yes.

> See #967911, which has been tagged "pending" almost three years ago. :-(

I forgot about this one.

> Yes, the clang-15 changelog entry for version 1:15.0.7-2 is not properly
> terminated.

OK, I've just reported a bug for this:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042997

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1042897: aptitude: viewing a package's changelog from the TUI outputs a warning that is immediately erased

[Vincent Lefevre]

Package: aptitude
Version: 0.8.13-5
Severity: normal

When I use "C" (View a package's changelog) on clang-15 from the
aptitude TUI, I get a warning that is immediately erased, so that
it is impossible to read it.

I suppose that aptitude should redirect stderr from
aptitude-changelog-parser so that it can display its contents
(when non empty) in a clear way.

Enabling the terminal's logs allows me to get the text of this
warning:

aptitude-changelog-parser: warning: 
/tmp/aptitude-root.7707:EXkCUB/aptitude-download-4-bORTciGPJi,..uo2EeQnZD7WBcD+L6_aptitude-download-cbF3RCIRNjR7d%D7+V.DiRimX__YaCHL(l105):
 found start of entry where expected more change data or trailer

This text seems to come from /usr/share/perl5/Dpkg/Changelog/Debian.pm:

unless ($expect eq FIRST_HEADING || $expect eq NEXT_OR_EOF) {
$self->parse_error($file, $.,
sprintf(g_('found start of entry where expected %s'),
$expect), "$_");
}

About this unexpected warning, there may be some other bug.
But note that "apt changelog clang-15" is fine.

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

aptitude version information:
aptitude 0.8.13
Compiler: g++ 12.1.0
Compiled against:
  apt version 6.0.0
  NCurses version 6.3
  libsigc++ version: 2.10.8
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.4.20230625
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7fff953a4000)
libgtk3-nocsd.so.0 => /usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 
(0x7f4eb8d16000)
libapt-pkg.so.6.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7f4eb840)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7f4eb8cdd000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7f4eb8ca8000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f4eb8c9f000)
libcwidget.so.4 => /usr/lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7f4eb870e000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f4eb8299000)
libboost_iostreams.so.1.74.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.74.0 (0x7f4eb8c85000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f4eb800)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f4eb8c8)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f4eb7c0)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f4eb862f000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f4eb8c5a000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f4eb7a1e000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f4eb8c55000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f4eb8c36000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f4eb8c23000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f4eb826a000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7f4eb8244000)
libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 
(0x7f4eb7f4)
libudev.so.1 => /usr/lib/x86_64-linux-gnu/libudev.so.1 
(0x7f4eb7f0e000)
libsystemd.so.0 => /usr/lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7f4eb793f000)
libgcrypt.so.20 => /usr/lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7f4eb77f9000)
libxxhash.so.0 => /usr/lib/x86_64-linux-gnu/libxxhash.so.0 
(0x7f4eb861a000)
/lib64/ld-linux-x86-64.so.2 (0x7f4eb8d43000)
libuuid.so.1 => /usr/lib/x86_64-linux-gnu/libuuid.so.1 
(0x7f4eb861)
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7f4eb8238000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7f4eb7ee6000)

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.3.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aptitude depends on:
ii  aptitude-common   0.8.13-5
ii  libapt-pkg6.0 2.7.2
ii  libboost-iostreams1.74.0  1.74.0+ds1-22
ii  libc6 2.37-6
ii  libcwidget4   0.5.18-6
ii  libgcc-s1 13.2.0-1
ii  libncursesw6  6.4+20230625-2
ii  libsigc++-2.0-0v5 2.12.0-1
ii  

[Aptitude-devel] Bug#933335: aptitude: Please add support for dpkg frontend lock

[Vincent Lefevre]

Control: found -1 0.8.13-5

Just to say that this still occurs.

The error message is now

[...]
Setting up apt (2.6.1) ...
dpkg: error: dpkg frontend lock was locked by another process with pid 4191235
Note: removing the lock file is always wrong, can damage the locked area
and the entire system. See .
E: Sub-process /usr/bin/dpkg returned an error code (2)
[...]

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1033558: aptitude-common: aptitude-curses.8.gz man page: unclear/wrong text for Example 12

[Vincent Lefevre]

Package: aptitude-common
Version: 0.8.13-5
Severity: minor

When searching for "Example" in the aptitude-curses(8) man page,
I get:

Example 12. Usage of --show-summary --show-summary used with -v to
display all the reasons a package is installed:

There are several issues.

1. Why "12" while this is the only example in this man page?

2. There is a duplicate of "--show-summary".

3. The sentence is not well formed.

-- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-security'), (500, 
'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 
'testing'), (500, 'stable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-7-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

aptitude-common depends on no packages.

Versions of packages aptitude-common recommends:
ii  aptitude  0.8.13-5

aptitude-common suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1033556: aptitude: "aptitude --show-summary=all-packages why ..." outputs the wrong package for Provides

[Vincent Lefevre]

Package: aptitude
Version: 0.8.13-5
Severity: normal

Consider for instance:

$ aptitude why mailutils
i   muttprint Recommends mutt | sylpheed | gnus | xfmail | exmh | mail-reader
i A mailutils Provides   mail-reader

Here, one can see that mailutils provides mail-reader.

$ aptitude --show-summary=all-packages why mailutils
Packages requiring mailutils:
  muttprint R: mail-reader P<- mail-reader

But here one has mail-reader on both sides of "P<-". I suppose that
this should have been

  muttprint R: mail-reader P<- mailutils

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

aptitude version information:
aptitude 0.8.13
Compiler: g++ 12.1.0
Compiled against:
  apt version 6.0.0
  NCurses version 6.3
  libsigc++ version: 2.10.8
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.4.20221231
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7fff29f63000)
libgtk3-nocsd.so.0 => /usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 
(0x7f1a978c8000)
libapt-pkg.so.6.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7f1a97205000)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7f1a9788e000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7f1a9785c000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f1a97853000)
libcwidget.so.4 => /usr/lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7f1a97113000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f1a96fb4000)
libboost_iostreams.so.1.74.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.74.0 (0x7f1a97839000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f1a96c0)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f1a97834000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f1a9680)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f1a96ed5000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f1a96eb5000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f1a96a1f000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f1a9782d000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f1a96e96000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f1a9781a000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f1a96e65000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7f1a96e3f000)
libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 
(0x7f1a96744000)
libudev.so.1 => /usr/lib/x86_64-linux-gnu/libudev.so.1 
(0x7f1a96717000)
libsystemd.so.0 => /usr/lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7f1a96648000)
libgcrypt.so.20 => /usr/lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7f1a96501000)
libxxhash.so.0 => /usr/lib/x86_64-linux-gnu/libxxhash.so.0 
(0x7f1a964ec000)
/lib64/ld-linux-x86-64.so.2 (0x7f1a978f5000)
libuuid.so.1 => /usr/lib/x86_64-linux-gnu/libuuid.so.1 
(0x7f1a96e33000)
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7f1a964e)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7f1a964b8000)

-- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-security'), (500, 
'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 
'testing'), (500, 'stable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-7-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aptitude depends on:
ii  aptitude-common   0.8.13-5
ii  libapt-pkg6.0 2.6.0
ii  libboost-iostreams1.74.0  1.74.0+ds1-20
ii  libc6 2.36-8
ii  libcwidget4   0.5.18-6
ii  libgcc-s1 12.2.0-14
ii  libncursesw6  6.4-2
ii  libsigc++-2.0-0v5 2.12.0-1
ii  libsqlite3-0  3.40.1-2
ii  libstdc++612.2.0-14
ii  libtinfo6 6.4-2
ii  libxapian30   1.4.22-1

Versions of packages aptitude recommends:
ii  libdpkg-perl1.21.21
ii  sensible-utils  0.0.17+nmu1

Versions of packages aptitude suggests:
pn  apt-xapian-index
ii  aptitude-doc-en [aptitude-doc]  0.8.13-5
pn  debtags 
ii  tasksel 3.72

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated 

[Aptitude-devel] Bug#1033357: Bug#1033357: aptitude: TUI does not display all error messages

[Vincent Lefevre]

On 2023-03-23 19:23:58 +0100, Axel Beckert wrote:
> Ran into this today, too. I think we had this already when bullseye
> switched from testing to stable or so and I think there's a bug report
> for this, too, already. Will search later for that one.

I don't remember about this one, but there was one (still open)
for stretch to buster:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931619

> Interestingly compared to your last bug repoirt this time I think the
> severity is higher, as this is an error which doesn't let you to
> properly continue without proper explanation.

The difference is that at least, one has here an error message, so
that one can investigate and fix the issue; and despite this error,
one can still upgrade everything except experimental, which is the
only one affected by the error. For the other bug report, aptitude
didn't report anything, so that it didn't leave the chance for the
user to find and fix the issue, which is much more problematic
(note that I became aware of the issue only by chance, due to some
random discussion in a Debian mailing-list); moreover, it involved
firmware upgrades, which, AFAIK, often have security fixes.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1033359: aptitude: should propose to update the Codename value, like apt

[Vincent Lefevre]

Package: aptitude
Version: 0.8.13-5
Severity: wishlist

With "aptitude update", I get:

[...]
Get: 31 https://ftp.debian.org/debian experimental InRelease [101 kB]
E: Repository 'https://ftp.debian.org/debian experimental InRelease' changed 
its 'Codename' value from 'experimental' to 'rc-buggy'
E: Failed to download some files
W: Failed to fetch https://ftp.debian.org/debian/dists/experimental/InRelease: 
E: Some index files failed to download. They have been ignored, or old ones 
used instead.

while "apt update" proposes to update the Codename value:

[...]
Get:15 https://ftp.debian.org/debian experimental InRelease [101 kB]
E: Repository 'https://ftp.debian.org/debian experimental InRelease' changed 
its 'Codename' value from 'experimental' to 'rc-buggy'
N: This must be accepted explicitly before updates for this repository can be 
applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? 
[y/N] 

It would be nice if aptitude could do the same thing
(both on the command line and with the TUI).

See bug 1033357 for the missing error message in the TUI.

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

aptitude version information:
aptitude 0.8.13
Compiler: g++ 12.1.0
Compiled against:
  apt version 6.0.0
  NCurses version 6.3
  libsigc++ version: 2.10.8
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.4.20221231
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7fff481c9000)
libgtk3-nocsd.so.0 => /usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 
(0x7f83fe0a3000)
libapt-pkg.so.6.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7f83fda05000)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7f83fe069000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7f83fe037000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f83fe02e000)
libcwidget.so.4 => /usr/lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7f83fd913000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f83fd7b4000)
libboost_iostreams.so.1.74.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.74.0 (0x7f83fd79c000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f83fd40)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f83fe027000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f83fd00)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f83fd6bd000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f83fd69d000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f83fd21f000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f83fe02)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f83fd67e000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f83fd66b000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f83fd63c000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7f83fcfda000)
libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 
(0x7f83fcf1e000)
libudev.so.1 => /usr/lib/x86_64-linux-gnu/libudev.so.1 
(0x7f83fcef1000)
libsystemd.so.0 => /usr/lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7f83fce22000)
libgcrypt.so.20 => /usr/lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7f83fccdb000)
libxxhash.so.0 => /usr/lib/x86_64-linux-gnu/libxxhash.so.0 
(0x7f83fccc6000)
/lib64/ld-linux-x86-64.so.2 (0x7f83fe0d4000)
libuuid.so.1 => /usr/lib/x86_64-linux-gnu/libuuid.so.1 
(0x7f83fd632000)
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7f83fccba000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7f83fcc92000)

-- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-security'), (500, 
'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 
'testing'), (500, 'stable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-7-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aptitude depends on:
ii  aptitude-common   0.8.13-5
ii  libapt-pkg6.0 2.6.0
ii  libboost-iostreams1.74.0  1.74.0+ds1-20
ii  libc6 2.36-8
ii  libcwidget4   0.5.18-6
ii  libgcc-s1 12.2.0-14
ii  libncursesw6  6.4-2
ii  libsigc++-2.0-0v5

[Aptitude-devel] Bug#1033357: aptitude: TUI does not display all error messages

[Vincent Lefevre]

Package: aptitude
Version: 0.8.13-5
Severity: minor

I've got the following error message from the TUI (with 'u' to update):

┌──┐
│E: Failed to download some files ▒│
│W: Failed to fetch   ▒│
│   https://ftp.debian.org/debian/dists/experimental/InRelease:   ▒│
│E: Some index files failed to download. They have been ignored, or old ones  ▒│
│   used instead. ▒│
│[ Ok ]│
└──┘

However, "aptitude update" (like "apt update") is more informative:

[...]
Get: 31 https://ftp.debian.org/debian experimental InRelease [101 kB]
E: Repository 'https://ftp.debian.org/debian experimental InRelease' changed 
its 'Codename' value from 'experimental' to 'rc-buggy'
E: Failed to download some files
W: Failed to fetch https://ftp.debian.org/debian/dists/experimental/InRelease: 
E: Some index files failed to download. They have been ignored, or old ones 
used instead.

I suspect that the cause is that the first message disappeared
in the TUI.

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

aptitude version information:
aptitude 0.8.13
Compiler: g++ 12.1.0
Compiled against:
  apt version 6.0.0
  NCurses version 6.3
  libsigc++ version: 2.10.8
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.4.20221231
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7ffde1bf1000)
libgtk3-nocsd.so.0 => /usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 
(0x7ff717ea8000)
libapt-pkg.so.6.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7ff717805000)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7ff717e6e000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7ff717e3c000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7ff717e33000)
libcwidget.so.4 => /usr/lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7ff717713000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7ff7175b4000)
libboost_iostreams.so.1.74.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.74.0 (0x7ff717e19000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7ff71720)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7ff7175af000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7ff716e0)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7ff7174ce000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7ff7174ae000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7ff71701f000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7ff7174a9000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7ff71748a000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7ff717477000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7ff717446000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7ff716dda000)
libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 
(0x7ff716d1e000)
libudev.so.1 => /usr/lib/x86_64-linux-gnu/libudev.so.1 
(0x7ff716cf1000)
libsystemd.so.0 => /usr/lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7ff716c22000)
libgcrypt.so.20 => /usr/lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7ff716adb000)
libxxhash.so.0 => /usr/lib/x86_64-linux-gnu/libxxhash.so.0 
(0x7ff716ac6000)
/lib64/ld-linux-x86-64.so.2 (0x7ff717ed9000)
libuuid.so.1 => /usr/lib/x86_64-linux-gnu/libuuid.so.1 
(0x7ff71743a000)
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7ff716aba000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7ff716a92000)

-- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-security'), (500, 
'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 
'testing'), (500, 'stable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-7-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aptitude depends on:
ii  aptitude-common   0.8.13-5
ii  libapt-pkg6.0 2.6.0
ii  libboost-iostreams1.74.0  

[Aptitude-devel] Bug#1032654: Bug#1032654: aptitude: missing message about the Debian bookworm change concerning non-free-firmware

[Vincent Lefevre]

On 2023-03-11 19:16:52 +0100, Axel Beckert wrote:
> > This message should have been displayed by aptitude.
> 
> Did you test "aptitude update" or "aptitude -u" or both?

I've tried 'u' from the aptitude TUI, "aptitude update" and
"aptitude -u". No messages.

> > Without it, the user who uses aptitude only may never be aware of
> > this change […]
> 
> This is wrong. Without doubt this type of information will be part of
> the release notes — which is usually the _primary_ source for these
> type of changes. I'm actually surprised that apt added such a message.

A sid user is not concerned by the stable releases, thus is not
supposed to read the release notes (and there would potentially
much duplicate information with past changes). The announces of
the main changes for sid (and testing) are normally done via the
NEWS.Debian files, and nothing has been announced there about
non-free-firmware.

> Besides that, the apt developers decided to output this only as LOW
> severity message on the "notice" level (prefix by "N:" and in normal
> font face; AFAIK the lowest level).
> 
> Aptitude shows "error" messages from apt to the user, but only those
> at the "WARNING" level or above (or at least only from somewhere above
> the "NOTICE" level). It is currently unclear to me if this is
> historically grown as apt (not aptitude) defines the _default_ message
> threshold by apt in /usr/include/apt-pkg/error.h as "WARNING" in at
> least three places. I at least currently assume that this is what
> aptitude uses when it calls DumpErrors. According the apt's changelog,
> "WARNING" was for quite some time also the lowest possible message
> level. ("NOTICE" and "DEBUG" levels got added in 0.7.26~exp8.)
> 
> I also do see some sense to suppress some less important messages in
> aptitude: All those messages would cause popup window in the TUI mode
> which the user has to acknowledge (aka "to click away"). That can get
> very annoying if there are too many low severity messages. So IMHO
> it's not so bad that aptitude only shows more important messages.

But do "NOTICE" messages occur often?

> Besides, it's the default threshold from apt.

What do you mean? There doesn't seem to be any default in
the "apt-config dump" output. So I get "NOTICE" messages
from apt by default.

> Then again, "aptitude -u" does not show any of the warnings (or
> notices) I currently get with "aptitude update", so "aptitude -u" only
> seems to cause popups of warnings which are caused directly during the
> download and not after a successful download. Cloning this as a
> separate bug report.
> 
> Anyway, back to the original topic. So I edited
> /usr/include/apt-pkg/error.h temporarily and replaced all but the
> first occurence (which is the definition) of WARNING with NOTICE and
> then compiled aptitude against it. aptitude update indeed
> showed notices now. But to my surprise not all of them, just this one:
> 
>   N: Skipping acquire of configured file 'main/binary-i386/Packages' as 
> repository 'file:/var/cache/apt-build/repository apt-build InRelease' doesn't 
> support architecture 'i386'
> 
> Not yet sure if this is a bug in the way how the missing notices are
> generated in apt or if it is a bug in aptitude not coping with the
> changed default message threshold. Likely needs deeper investigation
> (or better overview of the code), probably by Manuel. (I already put
> hours in investigating this IMHO rather minor issue, just to
> understand a bit how the innards of messages inside apt and aptitude
> are working.) Filing as yet another separate bug report against
> aptitude (for now at least), but with severity minor, as it currently
> does only show up after a hypothetical modification in apt.
[...]

FYI, the implementation is apt seems to have been done by this commit:

https://salsa.debian.org/apt-team/apt/-/commit/9712edf6151308148518058bfbd5ccd937509143

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1032654: aptitude: missing message about the Debian bookworm change concerning non-free-firmware

[Vincent Lefevre]

Package: aptitude
Version: 0.8.13-5
Severity: important

I'm using testing+unstable, and Debian changed the non-free component
to "non-free non-free-firmware" some time ago, and nothing has been
announced. I've recently learnt that with apt 2.6, a message is output
about that with "apt update", but I got nothing with updates from the
aptitude UI.

I have just tried "apt update" and got:

15 packages can be upgraded. Run 'apt list --upgradable' to see them.
N: Repository 'Debian bookworm' changed its 'non-free component' value from 
'non-free' to 'non-free non-free-firmware'
N: More information about this can be found online in the Release notes at: 
https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.html#non-free-split

This message should have been displayed by aptitude. Without it, the
user who uses aptitude only may never be aware of this change and will
miss future updates of the concerned packages (which are important for
security reasons).

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

aptitude version information:
aptitude 0.8.13
Compiler: g++ 12.1.0
Compiled against:
  apt version 6.0.0
  NCurses version 6.3
  libsigc++ version: 2.10.8
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.4.20221231
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7ffdc6f9e000)
libgtk3-nocsd.so.0 => /usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 
(0x7f381c337000)
libapt-pkg.so.6.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7f381bc05000)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7f381c2fd000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7f381c2cb000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f381c2c2000)
libcwidget.so.4 => /usr/lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7f381bb13000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f381b9b4000)
libboost_iostreams.so.1.74.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.74.0 (0x7f381c2a8000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f381b60)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f381c2a3000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f381b20)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f381b8d5000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f381c281000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f381b41f000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f381c27c000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f381c25d000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f381c24a000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f381c219000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7f381b8af000)
libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 
(0x7f381b144000)
libudev.so.1 => /usr/lib/x86_64-linux-gnu/libudev.so.1 
(0x7f381b882000)
libsystemd.so.0 => /usr/lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7f381b075000)
libgcrypt.so.20 => /usr/lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7f381af2e000)
libxxhash.so.0 => /usr/lib/x86_64-linux-gnu/libxxhash.so.0 
(0x7f381b86b000)
/lib64/ld-linux-x86-64.so.2 (0x7f381c364000)
libuuid.so.1 => /usr/lib/x86_64-linux-gnu/libuuid.so.1 
(0x7f381b861000)
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7f381b855000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7f381af06000)

-- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-6-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aptitude depends on:
ii  aptitude-common   0.8.13-5
ii  libapt-pkg6.0 2.6.0
ii  libboost-iostreams1.74.0  1.74.0+ds1-20
ii  libc6 2.36-8
ii  libcwidget4   0.5.18-6
ii  libgcc-s1 12.2.0-14
ii  libncursesw6  6.4-2
ii  libsigc++-2.0-0v5 2.12.0-1
ii  libsqlite3-0  3.40.1-1
ii  libstdc++612.2.0-14
ii  libtinfo6 6.4-2
ii  libxapian30   

[Aptitude-devel] Bug#1030643: aptitude: buggy handling of "Provides:" when trying to remove a package

[Vincent Lefevre]

Package: aptitude
Version: 0.8.13-5
Severity: normal

When I want to remove the libldap2-dev transitional package from the
command line, I get:

cventin:~> aptitude remove -s libldap2-dev
The following packages will be REMOVED:  
  libldap-dev{u} libldap2-dev 
0 packages upgraded, 0 newly installed, 2 to remove and 27 not upgraded.
Need to get 0 B of archives. After unpacking 1655 kB will be freed.
The following packages have unmet dependencies:
 libaprutil1-dev : Depends: libldap2-dev but it is not going to be installed
The following actions will resolve these dependencies:

 Keep the following packages at their current version: 
1) libldap-dev [2.5.13+dfsg-3 (now, testing, unstable)]

It appears that aptitude wants to remove libldap-dev too soon,
as this will break the dependencies: libaprutil1-dev depends on
libldap2-dev, which is provided by libldap-dev.

The other proposed solutions are not OK as they want to install or
remove other packages.

And from the TUI, if I type '-' on libldap2-dev, I get:

libldap2-dev (remove, 2.5.13+dfsg-3) will be removed.  ▒
   ▒
The following packages depend on libldap2-dev (remove, 2.5.13+dfsg-3) and will ▒
be broken by its removal:  ▒
   ▒
  * libaprutil1-dev (held/unchanged, 1.6.3-1) depends on libldap2-dev (provided▒
by libldap-dev 2.5.13+dfsg-3)  ▒

This is incorrect too, and the message is even buggy, as it correctly
says that libldap2-dev is provided by libldap-dev, but I'm not asking
to remove libldap-dev. So this doesn't make sense.

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

aptitude version information:
aptitude 0.8.13
Compiler: g++ 12.1.0
Compiled against:
  apt version 6.0.0
  NCurses version 6.3
  libsigc++ version: 2.10.8
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.4.20221231
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7ffd371cc000)
libapt-pkg.so.6.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7f6f7b805000)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7f6f7be2a000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7f6f7b7d3000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f6f7be21000)
libcwidget.so.4 => /usr/lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7f6f7b6e1000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f6f7b582000)
libboost_iostreams.so.1.74.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.74.0 (0x7f6f7b56a000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f6f7b20)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f6f7be1a000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f6f7ae0)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f6f7b48b000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f6f7b469000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f6f7b01f000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f6f7b44a000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f6f7b437000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f6f7add1000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7f6f7adab000)
libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 
(0x7f6f7acf2000)
libudev.so.1 => /usr/lib/x86_64-linux-gnu/libudev.so.1 
(0x7f6f7acc5000)
libsystemd.so.0 => /usr/lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7f6f7abf6000)
libgcrypt.so.20 => /usr/lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7f6f7aaaf000)
libxxhash.so.0 => /usr/lib/x86_64-linux-gnu/libxxhash.so.0 
(0x7f6f7aa9a000)
/lib64/ld-linux-x86-64.so.2 (0x7f6f7be88000)
libuuid.so.1 => /usr/lib/x86_64-linux-gnu/libuuid.so.1 
(0x7f6f7aa9)
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7f6f7aa84000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7f6f7aa5c000)

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-3-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, 

[Aptitude-devel] Bug#979186: Bug#979186: Bug#979186: aptitude: in the TUI, "+" changes the version of some packages in an inconsistent way

[Vincent Lefevre]

Control: found -1 0.8.13-5

On 2021-02-14 12:28:00 +0100, Vincent Lefevre wrote:
> On 2021-01-04 11:35:46 +0100, Axel Beckert wrote:
> > Will have a closer look later, earliest this evening.
> 
> Any news?

This occurred again:

i   libc-bin   2.35-1   2.36-4
i A libc6  2.35-1   2.35-1
i A libc6-i386 2.35-1   2.36-4
i A libc6-x32  2.35-1   2.36-4

but

zira:~> apt-show-versions -a libc6
libc6:amd64 2.35-1 install ok installed
libc6:amd64 2.31-13+deb11u4 stable ftp.debian.org
libc6:amd64 2.31-13+deb11u5 stable-updates ftp.debian.org
libc6:amd64 2.35-4  testingftp.debian.org
libc6:amd64 2.36-4  unstable   ftp.debian.org
No experimental version
libc6:amd64/unstable 2.35-1 upgradeable to 2.36-4

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1019465: Bug#1019465: aptitude: wants to remove the required package lsb-base with a broken reason

[Vincent Lefevre]

Hi Axel,

On 2022-09-10 15:34:50 +0200, Axel Beckert wrote:
> Vincent Lefevre wrote:
> > After marking some packages for upgrade, I get:
> > 
> > --\ Packages being deleted due to unsatisfied dependencies (1)
> > id  lsb-base -50.2 kB  11.2 11.2
> 
> which is correct, yes.
> 
> > Linux Standard Base init script functionality
> > lsb-base (remove, 11.2) will be automatically removed because of dependency 
> >▒
> > errors: 
> >▒
> 
> Where did this show up? I didn't get this. Or at least can't remember
> it. Was this a pop-up message?

After typing 'g' (to "perform all pending installations, removals,
and upgrades") and putting the cursor over the

id  lsb-base -50.2 kB  11.2 11.2

line (in order to learn why this package is removed). This is what
the bottom part of the window shows.

> > but no errors shown!!!
> 
> Because they were resolved.

OK, so the real reason should be given.

> > It seems to be triggered by the upgrade of sysvinit packages from
> > 3.04-1 to 3.05-2. In the sysvinit 3.05-1 log message:
> > 
> >   * Take over library scripts from lsb-base.
> 
> Yes, but because of this:
> 
> Conflicts: lsb-base

Normally conflicts produce an error on packages that must not be
removed. Here, I suppose that this is OK because of

Provides: lsb-base (= 11.1.0)

(by default, this is not shown by aptitude in the package description).

> So from my point of view aptitude did everything correctly and I don't
> see a bug here.

Well, the "because of dependency errors" in the above message is
incorrect and very confusing. Since there are no dependency errors,
this cannot be because of dependency errors.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#1019465: aptitude: wants to remove the required package lsb-base with a broken reason

[Vincent Lefevre]

Package: aptitude
Version: 0.8.13-5
Severity: important

After marking some packages for upgrade, I get:

--\ Packages being deleted due to unsatisfied dependencies (1)
id  lsb-base -50.2 kB  11.2 11.2

with

Linux Standard Base init script functionality
lsb-base (remove, 11.2) will be automatically removed because of dependency▒
errors:▒

but no errors shown!!!

It seems to be triggered by the upgrade of sysvinit packages from
3.04-1 to 3.05-2. In the sysvinit 3.05-1 log message:

  * Take over library scripts from lsb-base.

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

aptitude version information:
aptitude 0.8.13
Compiler: g++ 12.1.0
Compiled against:
  apt version 6.0.0
  NCurses version 6.3
  libsigc++ version: 2.10.8
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.3.20220423
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7ffe315ee000)
libgtk3-nocsd.so.0 => /usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 
(0x7f2dac7b1000)
libapt-pkg.so.6.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7f2dac009000)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7f2dac776000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7f2dac744000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f2dac73b000)
libcwidget.so.4 => /usr/lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7f2dac647000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f2dabeaa000)
libboost_iostreams.so.1.74.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.74.0 (0x7f2dac62f000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f2dabc0)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f2dac62a000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f2dab80)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f2dabb25000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f2dabe8a000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f2dab40)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f2dac623000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7f2dabe77000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f2dabe5a000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f2dabe47000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f2dabafd000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7f2dabad7000)
libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 
(0x7f2daba1e000)
libudev.so.1 => /usr/lib/x86_64-linux-gnu/libudev.so.1 
(0x7f2dab7d6000)
libsystemd.so.0 => /usr/lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7f2dab705000)
libgcrypt.so.20 => /usr/lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7f2dab2b9000)
libxxhash.so.0 => /usr/lib/x86_64-linux-gnu/libxxhash.so.0 
(0x7f2dabe32000)
/lib64/ld-linux-x86-64.so.2 (0x7f2dac7dc000)
libuuid.so.1 => /usr/lib/x86_64-linux-gnu/libuuid.so.1 
(0x7f2dabe29000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f2dac61a000)
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7f2dab6fa000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7f2dab6d1000)

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 5.19.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aptitude depends on:
ii  aptitude-common   0.8.13-5
ii  libapt-pkg6.0 2.5.2
ii  libboost-iostreams1.74.0  1.74.0-17
ii  libc6 2.34-7
ii  libcwidget4   0.5.18-6
ii  libgcc-s1 12.2.0-1
ii  libncursesw6  6.3+20220423-2
ii  libsigc++-2.0-0v5 2.10.8-1
ii  libsqlite3-0  3.39.3-1
ii  libstdc++612.2.0-1
ii  libtinfo6 6.3+20220423-2
ii  libxapian30   1.4.20-2

Versions of packages aptitude recommends:
ii  libdpkg-perl1.21.9
ii  sensible-utils  0.0.17

Versions of packages aptitude suggests:
ii  apt-xapian-index0.53
ii  

[Aptitude-devel] Bug#1013075: aptitude: "aptitude why" outputs a chain with a package that is not installed

[Vincent Lefevre]

Package: aptitude
Version: 0.8.13-4
Severity: normal

zira:~> aptitude why gobject-introspection
i   libglib2.0-dev Suggests libgirepository1.0-dev (>= 1.62) 
p   libgirepository1.0-dev Depends  gobject-introspection (= 1.72.0-1+b1)

while libgirepository1.0-dev isn't installed. So this doesn't give an
explanation of why gobject-introspection is automatically installed.

FYI, this is after

Start-Date: 2022-06-16  14:53:32
Commandline: apt install dh-sequence-gir gtk-doc-tools libgirepository1.0-dev 
libnss3-dev libglib2.0-doc libcairo2-doc
Install: libglib2.0-doc:amd64 (2.72.2-2), libnspr4-dev:amd64 (2:4.34-1, 
automatic), libnss3-dev:amd64 (2:3.79-1), python3-mako:amd64 (1.1.3+ds1-3, 
automatic), gobject-introspection:amd64 (1.72.0-1+b1), docbook:amd64 (4.5-10, 
automatic), python3-markdown:amd64 (3.3.7-1, automatic), gtk-doc-tools:amd64 
(1.33.2-1), libcairo2-doc:amd64 (1.16.0-5), libgirepository1.0-dev:amd64 
(1.72.0-1+b1), docbook-to-man:amd64 (1:2.0.0-45, automatic)
End-Date: 2022-06-16  14:53:36

Start-Date: 2022-06-16  15:01:07
Commandline: apt remove --purge dh-sequence-gir gtk-doc-tools 
libgirepository1.0-dev libnss3-dev libglib2.0-doc libcairo2-doc docbook-to-man 
libnspr4-dev
Purge: libglib2.0-doc:amd64 (2.72.2-2), libnspr4-dev:amd64 (2:4.34-1), 
libnss3-dev:amd64 (2:3.79-1), gtk-doc-tools:amd64 (1.33.2-1), 
libcairo2-doc:amd64 (1.16.0-5), libgirepository1.0-dev:amd64 (1.72.0-1+b1), 
docbook-to-man:amd64 (1:2.0.0-45)
End-Date: 2022-06-16  15:01:09

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

aptitude version information:
aptitude 0.8.13
Compiler: g++ 11.3.0
Compiled against:
  apt version 6.0.0
  NCurses version 6.3
  libsigc++ version: 2.10.4
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.3.20220423
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7ffe39dfe000)
libgtk3-nocsd.so.0 => /usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 
(0x7faba6b3b000)
libapt-pkg.so.6.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7faba6946000)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7faba690b000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7faba68d9000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7faba68d)
libcwidget.so.4 => /usr/lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7faba67c8000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7faba666c000)
libboost_iostreams.so.1.74.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.74.0 (0x7faba6653000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7faba643)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7faba640f000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7faba61f4000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7faba60b)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7faba608e000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7faba5eb5000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7faba5eaf000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7faba5e95000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7faba5e78000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7faba5e65000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7faba5e3b000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7faba5e18000)
libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 
(0x7faba5d5f000)
libudev.so.1 => /usr/lib/x86_64-linux-gnu/libudev.so.1 
(0x7faba5d35000)
libsystemd.so.0 => /usr/lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7faba5c62000)
libgcrypt.so.20 => /usr/lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7faba5b1b000)
libxxhash.so.0 => /usr/lib/x86_64-linux-gnu/libxxhash.so.0 
(0x7faba5b04000)
/lib64/ld-linux-x86-64.so.2 (0x7faba6f79000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7faba5afa000)
libuuid.so.1 => /usr/lib/x86_64-linux-gnu/libuuid.so.1 
(0x7faba5af1000)
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7faba5ae6000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7faba5abb000)

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.17.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, 

[Aptitude-devel] Bug#940819: aptitude: meaningless message "it is being removed because..." / issue with ORed dependency

[Vincent Lefevre]

Control: found -1 0.8.13-3

This time with:

--\ Packages being automatically installed to satisfy dependencies (1)
piA rlfe +50.2 kB 8.1-2
--\ Packages being removed because they are no longer used (2)
idA ledit-313 kB   2.04-5   2.04-5  
idA libfindlib-ocaml -938 kB   1.8.1-2  1.8.1-2 

where for rlfe it is said:

rlfe (install, 8.1-2) will be automatically installed to satisfy the following ▒
dependencies:  ▒
   ▒
  * ocaml-interp (held/unchanged, 4.11.1-4) recommends ledit | readline-editor ▒
(provided by ledit 2.04-5, rlfe 8.1-1, rlfe 8.1-2, rlwrap 0.43-1+b2)   ▒
  * coq (held/unchanged, 8.12.0-3+b3) suggests ledit | readline-editor ▒
(provided by ledit 2.04-5, rlfe 8.1-1, rlfe 8.1-2, rlwrap 0.43-1+b2)   ▒

and for ledit:

ledit (remove, 2.04-5) was installed automatically; it is being removed because▒
all of the packages which depend upon it are being removed:▒

without any package listed.

BTW, I don't know why aptitude wants to switch to the second ORed
choice.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#999766: aptitude: in the TUI, with "+m" on a piA package, aptitude doesn't remember the manually installed state

[Vincent Lefevre]

On 2021-11-16 14:53:15 +0100, Vincent Lefevre wrote:
> I've output debug information with the following two cases, quitting
> after step 6:
>   * '+' is used (before 'm');
>   * '+' is not used.
> 
> The only differences with --log-level=debug (after filtering out
> the prefix of each log line) except a PID difference in the name
> of the temporary file:
[...]

And with --log-level=trace, the first difference changes to:

@@ -2798559,7 +2798559,8 @@
 aptitude_resolver.cc:1762 DEBUG aptitude.resolver.scores - ** Score: +1 for 
gcc-sh4-linux-gnu:amd64 4:10.2.1-1 (aptitude::ProblemResolver::OptionalScore).
 aptitude_resolver.cc:1762 DEBUG aptitude.resolver.scores - ** Score: +1 for 
gcc-sh4-linux-gnu:i386 4:11.2.0--1 (aptitude::ProblemResolver::OptionalScore).
 aptitude_resolver.cc:1762 DEBUG aptitude.resolver.scores - ** Score: +1 for 
gcc-sh4-linux-gnu:i386 4:10.2.1-1 (aptitude::ProblemResolver::OptionalScore).
-resolver_manager.cc:581 DEBUG aptitude.resolver.thread - Resolver thread: got 
a new job { solution number = 0, max steps = 50, continuation = 
0x5588ba253ed0 }
+resolver_manager.cc:565 TRACE aptitude.resolver.thread - Resolver thread: 
waiting for a job.
+resolver_manager.cc:581 DEBUG aptitude.resolver.thread - Resolver thread: got 
a new job { solution number = 0, max steps = 50, continuation = 
0x55c4f59b2ed0 }
 problemresolver.h:4592 INFO aptitude.resolver.search - Starting a new search.
 problemresolver.h:3239 TRACE aptitude.resolver.search - Marking the dependency 
why3-coq:amd64 1.3.3-3 -> {coq:amd64 8.12.0-3+b3} as unresolved in step 0
 problemresolver.h:2634 TRACE aptitude.resolver.search - Adding the solver 
Install(coq:amd64 8.12.0-3+b3  {coq:amd64 
8.12.0-3+b3}>) with initial cost (nop)

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#999766: aptitude: in the TUI, with "+m" on a piA package, aptitude doesn't remember the manually installed state

[Vincent Lefevre]

Package: aptitude
Version: 0.8.13-3
Severity: normal

With ksh 2020.0.0+really93u+20120801-10 installed and ksh93u+m not yet
installed, I have the following issue (always reproducible):

# aptitude

1. I type 'U' to upgrade. I get

aptitude 0.8.13 @ cventin   #Broken: 1   Disk: -151 MB DL: 123 MB/123 MB

[1(1)/...] Actions: 7 keeps
e: Examine  !: Apply  .: Next  ,: Previous

2. I type 'g' to perform the pending operations, keeping these
unrelated packages. This gives:

--\ Packages to be upgraded (1)
iu  ksh  -3312 kB  2020.0.0+really93u+20120 20210511
--\ Packages being automatically installed to satisfy dependencies (1)
piA ksh93u+m +3284 kB 1.0.0~beta.1-1

3. Over ksh93u+m, I type '+m' (the '+' does nothing but it is actually
important to reproduce the bug), where 'm' now declares ksh93u+m as to
be manually installed.

4. Over ksh, I type '_' to purge this package (now a transitional
package to ksh93u+m). This gives:

--\ Packages to be upgraded (1)
ip  ksh  -3359 kB  2020.0.0+really93u+20120 20210511
--\ Packages being automatically installed to satisfy dependencies (1)
pi  ksh93u+m +3284 kB 1.0.0~beta.1-1

5. I type 'g' to perform the pending operations. This succeeds,
and I get:

Press Return to continue, 'q' followed by Return to quit.

6. I press Return to continue. But I get:

aptitude 0.8.13 @ cventinDisk: -3284 kB

7. I type 'g', which gives:

--\ Packages being removed because they are no longer used (1)
idA ksh93u+m -3284 kB  1.0.0~beta.1-1   1.0.0~beta.1-1

while this package should have been considered manually installed
due to step 3.

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

aptitude version information:
aptitude 0.8.13
Compiler: g++ 10.2.1 20210110
Compiled against:
  apt version 6.0.0
  NCurses version 6.2
  libsigc++ version: 2.10.4
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.3.20211021
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7ffed30f9000)
libapt-pkg.so.6.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7fbe6a81f000)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7fbe6a7e4000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7fbe6a7b3000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7fbe6a7aa000)
libcwidget.so.4 => /usr/lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7fbe6a6a4000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7fbe6a559000)
libboost_iostreams.so.1.74.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.74.0 (0x7fbe6a53e000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7fbe6a31b000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fbe6a2fa000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fbe6a0ee000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fbe69fa9000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fbe69f8f000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fbe69dc8000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7fbe69dae000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fbe69d91000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7fbe69d7e000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fbe69d56000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7fbe69d33000)
libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 
(0x7fbe69c56000)
libudev.so.1 => /usr/lib/x86_64-linux-gnu/libudev.so.1 
(0x7fbe69c1f000)
libsystemd.so.0 => /usr/lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7fbe69b4)
libgcrypt.so.20 => /usr/lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7fbe69a04000)
libxxhash.so.0 => /usr/lib/x86_64-linux-gnu/libxxhash.so.0 
(0x7fbe699eb000)
/lib64/ld-linux-x86-64.so.2 (0x7fbe6ae54000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fbe699e5000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fbe699d8000)
libuuid.so.1 => /usr/lib/x86_64-linux-gnu/libuuid.so.1 
(0x7fbe699cf000)
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7fbe699c4000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7fbe6999d000)

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.14.0-4-amd64 (SMP 

[Aptitude-devel] Bug#979186: Bug#979186: Bug#979186: aptitude: in the TUI, "+" changes the version of some packages in an inconsistent way

[Vincent Lefevre]

Control: found -1 0.8.13-3

(reproducible with the bundle)

Hi,

On 2021-01-04 11:35:46 +0100, Axel Beckert wrote:
> Will have a closer look later, earliest this evening.

Any news?

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#980035: Bug#980035: aptitude: segmentation fault when starting aptitude

[Vincent Lefevre]

On 2021-01-14 02:14:29 +0100, Axel Beckert wrote:
> Since Julian has uploaded a fix as apt/2.1.18, would you mind checking
> if you can still reproduce the issue in any way?

I couldn't manage to reproduce it with apt 2.1.18.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#980053: Bug#980035: Bug#980035: aptitude: segmentation fault when starting aptitude

[Vincent Lefevre]

[moved to Cc: 980053]

Hi,

On 2021-01-13 15:33:00 +0100, Axel Beckert wrote:
> Vincent Lefevre wrote:
> > Hmm... I think that you should forget that test. I thought
> > that aptitude-run-state-bundle would only depend on files from
> > aptitude-segv.bundle, but it still reads some other files from
> > /var/lib according to strace. And now I get
> > 
> > --- Upgradable Packages (65)
> > 
> > instead of
> > 
> > --- Upgradable Packages (61)
> > 
> > Since the crashes are very sensitive to the system status, the
> > above test might not be reliable.
> 
> Ack. That's now https://bugs.debian.org/980053 :-)

Well, 980053 is about aptitude-create-state-bundle. The above issue
is about aptitude-run-state-bundle. Perhaps this is due to the
aptitude-create-state-bundle bug, but I think that if a file is
missing, aptitude-run-state-bundle should fail, not fall back to
/var/lib files.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#980035: Bug#980035: Bug#980035: aptitude: segmentation fault when starting aptitude

[Vincent Lefevre]

On 2021-01-13 15:07:26 +0100, Axel Beckert wrote:
> Vincent: Got the bundle, thanks! Wasn't able to provoke a segfault
> with it, even not after pressing "u".

With the bundle, the crash occurs while the UI isn't displayed yet.
But I can see in particular:

2300077 stat("/var/lib/dpkg/status", {st_mode=S_IFREG|0644, st_size=3777850, 
...}) = 0
2300081 openat(AT_FDCWD, "/var/lib/dpkg/arch", O_RDONLY) = -1 ENOENT (No such 
file or directory)
2300082 openat(AT_FDCWD, "/var/lib/dpkg/arch", O_RDONLY) = -1 ENOENT (No such 
file or directory)
2300083 openat(AT_FDCWD, "/var/lib/dpkg/arch", O_RDONLY) = -1 ENOENT (No such 
file or directory)
2300077 stat("/var/lib/apt-xapian-index/index", {st_mode=S_IFREG|0644, 
st_size=41, ...}) = 0
2300077 openat(AT_FDCWD, "/var/lib/apt-xapian-index/index", O_RDONLY) = 36
2300077 openat(AT_FDCWD, "/var/lib/aptitude//pkgstates", O_RDONLY) = 36
2300077 openat(AT_FDCWD, "/var/lib/debtags/package-tags", O_RDONLY) = -1 ENOENT 
(No such file or directory)
222 symlinkat("/var/local/apt/./Packages", 4, 
".//var/lib/apt/lists/_var_local_apt_._Packages") = 0

while most files are read from the /tmp version.

So, as this seems to depend on the system, this is not surprising.
When I look in detail:

--\ Upgradable Packages (65)
  --\ admin  Administrative utilities (install software, manage users, e
--\ main   The main Debian archive (3)
i   apt2.1.17   2.1.17+local1
i   apt-utils  2.1.17   2.1.17+local1
[...]

The 2.1.17+local1 packages are the newly reinstalled patched versions
(now listed in /var/local/apt/Packages).

They do not exist in the bundle!!!

> But as mentioned in #980037 this seems normal in such a case without
> a special kernel. So thanks for the bug report!

Note that I do *not* have a special kernel. So this is unrelated.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#980035: aptitude: segmentation fault when starting aptitude

[Vincent Lefevre]

On 2021-01-13 12:04:57 +0100, Vincent Lefevre wrote:
> On 2021-01-13 11:24:33 +0100, Vincent Lefevre wrote:
> > A bundle is available for a limited time:
> > 
> >   https://www.vinc17.net/aptitude-segv.bundle
> > 
> > I can reproduce the crash (but not always) with
> > 
> >   aptitude-run-state-bundle aptitude-segv.bundle
> > 
> > on this machine and on another one.
> 
> When it doesn't crash, aptitude doesn't suggest any action.
> 
> But on a 3rd machine, which has the same aptitude version, but older
> versions of dependencies, aptitude never crashes, and I get:
> 
> [1(1)/...] Actions: 2 keeps, 1 upgrade
> e: Examine  !: Apply  .: Next  ,: Previous
> 
> and 'e' says:
> 
> Packages  Resolve Dependencies
>   --\ Keep the following packages at their current version:   
>   
> desktop-file-utils [0.26-1 (now, testing, 
> unstable)]
> gvfs-common  [1.46.1-2 (now, testing, 
> unstable)]
>   --\ Upgrade the following packages:
> libmtp-common [1.1.17-3 now, testing, unstable -> 1.1.18-1 
> experimental]
> 
> (suggesting to upgrade a package to experimental like that is
> incorrect, unless aptitude already broke the system).

The cause of this issue seems to be that aptitude-run-state-bundle
depends on the current system status, not just aptitude-segv.bundle.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#980035: Bug#980035: aptitude: segmentation fault when starting aptitude

[Vincent Lefevre]

On 2021-01-13 14:46:21 +0100, Vincent Lefevre wrote:
> On 2021-01-13 12:31:05 +0100, Julian Andres Klode wrote:
> > Smells like 980037? Bug in APT's cache building upon mremap() in new
> > code path in 2.1.16/17.
> 
> Yes, I first rebuilt apt, and
> 
>   aptitude-run-state-bundle aptitude-segv.bundle
> 
> was still crashing, then applied the patch suggested at
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980037#10
> 
> and I no longer get any crash.

Hmm... I think that you should forget that test. I thought
that aptitude-run-state-bundle would only depend on files from
aptitude-segv.bundle, but it still reads some other files from
/var/lib according to strace. And now I get

--- Upgradable Packages (65)

instead of

--- Upgradable Packages (61)

Since the crashes are very sensitive to the system status, the
above test might not be reliable.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#980035: Bug#980035: aptitude: segmentation fault when starting aptitude

[Vincent Lefevre]

On 2021-01-13 12:31:05 +0100, Julian Andres Klode wrote:
> Smells like 980037? Bug in APT's cache building upon mremap() in new
> code path in 2.1.16/17.

Yes, I first rebuilt apt, and

  aptitude-run-state-bundle aptitude-segv.bundle

was still crashing, then applied the patch suggested at

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980037#10

and I no longer get any crash.

But I don't have a patched kernel, just the one provided by Debian,
and the crashes were almost 100% reproducible when "aptitude" was
run alone.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#980035: aptitude: segmentation fault when starting aptitude

[Vincent Lefevre]

On 2021-01-13 11:24:33 +0100, Vincent Lefevre wrote:
> A bundle is available for a limited time:
> 
>   https://www.vinc17.net/aptitude-segv.bundle
> 
> I can reproduce the crash (but not always) with
> 
>   aptitude-run-state-bundle aptitude-segv.bundle
> 
> on this machine and on another one.

When it doesn't crash, aptitude doesn't suggest any action.

But on a 3rd machine, which has the same aptitude version, but older
versions of dependencies, aptitude never crashes, and I get:

[1(1)/...] Actions: 2 keeps, 1 upgrade
e: Examine  !: Apply  .: Next  ,: Previous

and 'e' says:

Packages  Resolve Dependencies
  --\ Keep the following packages at their current version: 
desktop-file-utils [0.26-1 (now, testing, unstable)]
gvfs-common  [1.46.1-2 (now, testing, unstable)]
  --\ Upgrade the following packages:
libmtp-common [1.1.17-3 now, testing, unstable -> 1.1.18-1 experimental]

(suggesting to upgrade a package to experimental like that is
incorrect, unless aptitude already broke the system).

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#980035: aptitude: segmentation fault when starting aptitude

[Vincent Lefevre]

A bundle is available for a limited time:

  https://www.vinc17.net/aptitude-segv.bundle

I can reproduce the crash (but not always) with

  aptitude-run-state-bundle aptitude-segv.bundle

on this machine and on another one.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#980035: aptitude: segmentation fault when starting aptitude

[Vincent Lefevre]

On 2021-01-13 10:29:17 +0100, Vincent Lefevre wrote:
> However, if I run "strace -f -o str.out aptitude", I don't always
> get a segmentation fault. So there may be another reason.

When it crashes, this seems to be at the same place:

[...]
2237416 read(3, "ym_19981025-8_amd64.deb\nSize: 11"..., 32324) = 32324
2237416 read(3, "ds: libcolorhug2 (= 1.4.5-3)\nDes"..., 32604) = 32604
2237416 read(3, "62e8f4b0 baeda553779dac49b00a6b2"..., 32336) = 32336
2237416 read(3, "83243673985ebc90635ba4337487ab 9"..., 17767) = 17767
2237416 read(3, "256: 588bb0e2a387be5494af07d9909"..., 32237) = 32237
2237416 read(3, "5688ba1f31dcc90cda9499 14b2ffe0c"..., 32391) = 32391
2237416 read(3, "2ecd4ea9d8b9d23afa9d5b67d7b8f2a3"..., 32481) = 32481
2237416 read(3, "fbef99d590e1cac8f0801e2fbcd2835e"..., 32449) = 32449
2237416 mremap(0x7fc6dc60, 60817408, 61865984, MREMAP_MAYMOVE) = 
0x7fc6d450
2237416 --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, 
si_addr=0x7fc6dffef750} ---
[...]

[...]
223 read(3, "ym_19981025-8_amd64.deb\nSize: 11"..., 32324) = 32324
223 read(3, "ds: libcolorhug2 (= 1.4.5-3)\nDes"..., 32604) = 32604
223 read(3, "62e8f4b0 baeda553779dac49b00a6b2"..., 32336) = 32336
223 read(3, "83243673985ebc90635ba4337487ab 9"..., 17767) = 17767
223 read(3, "256: 588bb0e2a387be5494af07d9909"..., 32237) = 32237
223 read(3, "5688ba1f31dcc90cda9499 14b2ffe0c"..., 32391) = 32391
223 read(3, "2ecd4ea9d8b9d23afa9d5b67d7b8f2a3"..., 32481) = 32481
223 read(3, "fbef99d590e1cac8f0801e2fbcd2835e"..., 32449) = 32449
223 mremap(0x7fad2860, 60817408, 61865984, MREMAP_MAYMOVE) = 
0x7fad2050
223 --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, 
si_addr=0x7fad2bfef750} ---
[...]

[...]
2238354 read(3, "ym_19981025-8_amd64.deb\nSize: 11"..., 32324) = 32324
2238354 read(3, "ds: libcolorhug2 (= 1.4.5-3)\nDes"..., 32604) = 32604
2238354 read(3, "62e8f4b0 baeda553779dac49b00a6b2"..., 32336) = 32336
2238354 read(3, "83243673985ebc90635ba4337487ab 9"..., 17767) = 17767
2238354 read(3, "256: 588bb0e2a387be5494af07d9909"..., 32237) = 32237
2238354 read(3, "5688ba1f31dcc90cda9499 14b2ffe0c"..., 32391) = 32391
2238354 read(3, "2ecd4ea9d8b9d23afa9d5b67d7b8f2a3"..., 32481) = 32481
2238354 read(3, "fbef99d590e1cac8f0801e2fbcd2835e"..., 32449) = 32449
2238354 mremap(0x7f975460, 60817408, 61865984, MREMAP_MAYMOVE) = 
0x7f974c50
2238354 --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, 
si_addr=0x7f9757fef750} ---
[...]

And when it doesn't:

[...]
2237967 read(3, "ym_19981025-8_amd64.deb\nSize: 11"..., 32324) = 32324
2237967 read(3, "ds: libcolorhug2 (= 1.4.5-3)\nDes"..., 32604) = 32604
2237967 read(3, "62e8f4b0 baeda553779dac49b00a6b2"..., 32336) = 32336
2237967 read(3, "83243673985ebc90635ba4337487ab 9"..., 17767) = 17767
2237967 read(3, "256: 588bb0e2a387be5494af07d9909"..., 32237) = 32237
2237967 read(3, "5688ba1f31dcc90cda9499 14b2ffe0c"..., 32391) = 32391
2237967 read(3, "2ecd4ea9d8b9d23afa9d5b67d7b8f2a3"..., 32481) = 32481
2237967 read(3, "fbef99d590e1cac8f0801e2fbcd2835e"..., 32449) = 32449
2237967 mremap(0x7ff909d0, 60817408, 61865984, MREMAP_MAYMOVE) = 
0x7ff909d0
2237967 read(3, "b\n\nPackage: cue2toc-dbgsym\nSourc"..., 32156) = 32156
2237967 read(3, "fc5e9475f8ea1996ad1d1\nDescriptio"..., 32468) = 32468
2237967 read(3, "noit \nArch"..., 32635) = 32635
2237967 read(3, "446f87a121ed255bd081 e3830a9a187"..., 26866) = 26866
[...]

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#980035: aptitude: segmentation fault when starting aptitude

[Vincent Lefevre]

Package: aptitude
Version: 0.8.13-2+b1
Severity: grave
Justification: renders package unusable
Tags: security

I got a first "segmentation fault" just after updating ('u' in the TUI).
Now, each time I run aptitude, a segmentation occurs one second after
starting it.

I suppose that it doesn't like some data that have been fetched.
Tagging security for this reason.

The backtrace:

(gdb) bt
#0  0x7f4149ad4f1c in ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#1  0x7f4149ad64c4 in ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#2  0x7f4149ad87f6 in ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#3  0x7f4149ab96bd in pkgDebianIndexFile::Merge(pkgCacheGenerator&, 
OpProgress*) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#4  0x7f4149ad33b6 in ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#5  0x7f4149ad9c30 in ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#6  0x7f4149adbd05 in ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#7  0x5579892393ff in ?? ()
#8  0x557989242c83 in ?? ()
#9  0x5579890dc9f6 in ?? ()
#10 0x7f4148f5cd0a in __libc_start_main (main=0x5579890daae0, argc=1, 
argv=0x7fffbe441bf8, init=, fini=, 
rtld_fini=, stack_end=0x7fffbe441be8) at ../csu/libc-start.c:308
#11 0x5579890e5f2a in ?? ()

However, if I run "strace -f -o str.out aptitude", I don't always
get a segmentation fault. So there may be another reason.

It may be a bug in libapt-pkg6.0, or perhaps a change in the upgrade
to apt 2.1.17 triggered an existing issue in aptitude.

Here's the end of the str.out file when "strace -f -o str.out aptitude"
crashed:

2237416 
stat("/var/lib/apt/lists/ftp.fr.debian.org_debian_dists_experimental_main_binary-all_Packages",
 0x7ffdb54ba240) = -1 ENOENT (No such file or directory)
2237416 
stat("/var/lib/apt/lists/ftp.fr.debian.org_debian_dists_experimental_main_binary-all_Packages.xz",
 0x7ffdb54ba240) = -1 ENOENT (No such file or directory)
2237416 
stat("/var/lib/apt/lists/ftp.fr.debian.org_debian_dists_experimental_main_binary-all_Packages.bz2",
 0x7ffdb54ba240) = -1 ENOENT (No such file or directory)
2237416 
stat("/var/lib/apt/lists/ftp.fr.debian.org_debian_dists_experimental_main_binary-all_Packages.lzma",
 0x7ffdb54ba240) = -1 ENOENT (No such file or directory)
2237416 
stat("/var/lib/apt/lists/ftp.fr.debian.org_debian_dists_experimental_main_binary-all_Packages.gz",
 0x7ffdb54ba240) = -1 ENOENT (No such file or directory)
2237416 
stat("/var/lib/apt/lists/ftp.fr.debian.org_debian_dists_experimental_main_binary-all_Packages.lz4",
 0x7ffdb54ba240) = -1 ENOENT (No such file or directory)
2237416 
stat("/var/lib/apt/lists/ftp.fr.debian.org_debian_dists_experimental_main_binary-all_Packages.zst",
 0x7ffdb54ba240) = -1 ENOENT (No such file or directory)
2237416 
stat("/var/lib/apt/lists/ftp.fr.debian.org_debian_dists_experimental_main_binary-all_Packages.uncompressed",
 0x7ffdb54ba240) = -1 ENOENT (No such file or directory)
2237416 
stat("/var/lib/apt/lists/ftp.fr.debian.org_debian_dists_experimental_main_binary-all_Packages",
 0x7ffdb54ba330) = -1 ENOENT (No such file or directory)
2237416 
stat("/var/lib/apt/lists/ftp.fr.debian.org_debian_dists_experimental_main_i18n_Translation-en",
 {st_mode=S_IFREG|0644, st_size=1187463, ...}) = 0
2237416 
stat("/var/lib/apt/lists/ftp.fr.debian.org_debian_dists_experimental_main_i18n_Translation-en",
 {st_mode=S_IFREG|0644, st_size=1187463, ...}) = 0
2237416 
stat("/var/lib/apt/lists/ftp.fr.debian.org_debian_dists_experimental_main_i18n_Translation-en",
 {st_mode=S_IFREG|0644, st_size=1187463, ...}) = 0
2237416 
stat("/var/lib/apt/lists/ftp.fr.debian.org_debian_dists_experimental_main_i18n_Translation-en",
 {st_mode=S_IFREG|0644, st_size=1187463, ...}) = 0
2237416 
stat("/var/lib/apt/lists/ftp.fr.debian.org_debian_dists_experimental_main_i18n_Translation-en",
 {st_mode=S_IFREG|0644, st_size=1187463, ...}) = 0
2237416 
stat("/var/lib/apt/lists/ftp.fr.debian.org_debian_dists_experimental_main_i18n_Translation-en",
 {st_mode=S_IFREG|0644, st_size=1187463, ...}) = 0
2237416 openat(AT_FDCWD, 
"/var/lib/apt/lists/ftp.fr.debian.org_debian_dists_experimental_main_i18n_Translation-en",
 O_RDONLY) = 3
2237416 fcntl(3, F_SETFD, FD_CLOEXEC)   = 0
2237416 fstat(3, {st_mode=S_IFREG|0644, st_size=1187463, ...}) = 0
2237416 close(3)= 0
2237416 rt_sigaction(SIGTSTP, {sa_handler=SIG_IGN, sa_mask=[], 
sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7fc6f0289140}, 
{sa_handler=0x7fc6f0772ce0, sa_mask=[], sa_flags=SA_RESTORER|SA_RESTART, 
sa_restorer=0x7fc6f0289140}, 8) = 0
2237416 poll([{fd=0, events=POLLIN}], 1, 0) = 0 (Timeout)
2237416 poll([{fd=0, events=POLLIN}], 1, 0) = 0 (Timeout)
2237416 rt_sigaction(SIGTSTP, {sa_handler=0x7fc6f0772ce0, sa_mask=[], 
sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7fc6f0289140}, NULL, 8) = 0
2237416 rt_sigaction(SIGTSTP, {sa_handler=SIG_IGN, sa_mask=[], 
sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7fc6f0289140}, 

[Aptitude-devel] Bug#979186: Bug#979186: aptitude: in the TUI, "+" changes the version of some packages in an inconsistent way

[Vincent Lefevre]

On 2021-01-04 08:42:53 +0100, Axel Beckert wrote:
> Can you do an aptitude-create-state-bundle either before (preferred)
> or after that situation and upload it somewhere?

It's available here for a short period:

  https://www.vinc17.net/aptitude.bundle

(I created it at about the same time as my bug report; the bug is
also reproducible when running aptitude as a normal user, so that
I could test in a non-destructive way).

> Oh, and what is your setting of aptitude::Auto-Install (aka
> "Automatically resolve dependencies of a package when it is selected")
> and maybe other settings which might play a role here?

My only settings concerning aptitude:

Aptitude::UI::Package-Display-Format "%c%a%M %p %Z %24v %24V";

Aptitude::UI::Styles {
  // Add bold to avoid a readability issue.
  SolutionActionApproved { fg white; bg green; set bold; };
};

Aptitude::ProblemResolver::SolutionCost "safety, removals";

> Do you have any special /etc/apt/preferences* settings which might
> play a role here, too?

Only:

Explanation: For security, make sure that the Flash plugin is never installed.
Package: flashplugin-nonfree:any
Pin: version *
Pin-Priority: -1

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#966488: aptitude corrupts package install selection after dpkg error

[Vincent Lefevre]

On 2020-07-29 11:06:16 +0200, Vincent Lefevre wrote:
> An upgrade with aptitude failed due to a dpkg lock error (bug 95).
> Then I noticed that not all packages were upgraded, so that I started
> aptitude again to complete the upgrade. I typed 'g', but got:
> 
> [1(1)/...] Actions: no changes
> e: Examine  !: Apply  .: Next  ,: Previous
> 
> and 'e' gives:
> 
>   --\ Leave the following recommendations unresolved: 
>   
> lcov recommends libgd-gd2-perl
> 
> Since lcov recommends libgd-gd2-perl, this means that it was in
> the package install selection before the initial upgrade (note
> that I didn't have such a warning in the initial upgrade). But
> now libgd-gd2-perl is no longer proposed for installation!

Actually I don't even understand this message as libgd-perl is
already installed and provides libgd-gd2-perl:

cventin:~> dpkg -s libgd-perl
Package: libgd-perl
Status: purge ok installed
Priority: optional
Section: perl
Installed-Size: 392
Maintainer: Debian Perl Group 
Architecture: amd64
Source: libgd-perl (2.71-2)
Version: 2.71-2+b1
Replaces: libgd-gd2-noxpm-perl (<= 1:2.46-2.1), libgd-gd2-perl (<= 1:2.46-3.1)
Provides: libgd-gd2-noxpm-perl, libgd-gd2-perl
[...]

But in the aptitude log (see below), I see that aptitude wanted to
remove libgd-perl (this package is still installed as the upgrade
did not complete due to the dpkg error).

Now, the real issue may be that in its initial dependency resolution,
aptitude missed the Recommends satisfied by the "Provides:", and chose
to remove libgd-perl, breaking the "Recommends:" by doing that.

Aptitude 0.8.13: log report
Wed, Jul 29 2020 10:44:18 +0200

  IMPORTANT: this log only lists intended actions; actions which fail
  due to dpkg problems may not be completed.

Will install 340 packages, and remove 10 packages.
583 MB of disk space will be freed

[REMOVE, NOT USED] g++-9:amd64 9.3.0-15
[REMOVE, NOT USED] gfortran-9:amd64 9.3.0-15
[REMOVE, NOT USED] libflint-2.6.0:amd64 2.6.0-3
[REMOVE, NOT USED] libgc1c2:amd64 1:7.6.4-0.4
[REMOVE, NOT USED] libgd-perl:amd64 2.71-2+b1
[REMOVE, NOT USED] libgfortran-9-dev:amd64 9.3.0-15
[REMOVE, NOT USED] libre2-7:amd64 20200601+dfsg-1
[REMOVE, NOT USED] libssl1.0.2:amd64 1.0.2s-1~deb9u1
[REMOVE, NOT USED] libx264-159:amd64 2:0.159.2999+git296494a-2
[REMOVE, NOT USED] libx264-159:i386 2:0.159.2999+git296494a-2
[HOLD, DEPENDENCIES] linux-compiler-gcc-9-x86:amd64 5.7.6-1
[HOLD, DEPENDENCIES] linux-doc-5.7:amd64 5.7.6-1
[HOLD, DEPENDENCIES] linux-kbuild-5.7:amd64 5.7.6-1
[HOLD, DEPENDENCIES] linux-libc-dev:amd64 5.7.6-1
[INSTALL, DEPENDENCIES] fonts-unifont:amd64 1:13.0.03-1
[INSTALL, DEPENDENCIES] g++-10:amd64 10.2.0-3
[INSTALL, DEPENDENCIES] gfortran-10:amd64 10.2.0-3
[INSTALL, DEPENDENCIES] libaliased-perl:amd64 0.34-1
[INSTALL, DEPENDENCIES] libcompress-raw-bzip2-perl:amd64 2.095-1
[INSTALL, DEPENDENCIES] libcompress-raw-lzma-perl:amd64 2.095-1
[INSTALL, DEPENDENCIES] libcompress-raw-zlib-perl:amd64 2.095-1
[INSTALL, DEPENDENCIES] libdata-dpath-perl:amd64 0.58-1
[INSTALL, DEPENDENCIES] libflint-2.6.1:amd64 2.6.1-1
[INSTALL, DEPENDENCIES] libgc1:amd64 1:8.0.4-1
[INSTALL, DEPENDENCIES] libgfortran-10-dev:amd64 10.2.0-3
[INSTALL, DEPENDENCIES] libio-compress-lzma-perl:amd64 2.095-1
[INSTALL, DEPENDENCIES] libio-compress-perl:amd64 2.095-1
[INSTALL, DEPENDENCIES] libiterator-perl:amd64 0.03+ds1-1
[INSTALL, DEPENDENCIES] libiterator-util-perl:amd64 0.02+ds1-1
[INSTALL, DEPENDENCIES] libre2-8:amd64 20200706+dfsg-2
[INSTALL, DEPENDENCIES] libstdc++-10-dev:amd64 10.2.0-3
[INSTALL, DEPENDENCIES] libtirpc-common:amd64 1.2.6-1
[INSTALL, DEPENDENCIES] libtirpc3:amd64 1.2.6-1
[INSTALL, DEPENDENCIES] libx264-160:amd64 2:0.160.3011+gitcde9a93-2
[INSTALL, DEPENDENCIES] libx264-160:i386 2:0.160.3011+gitcde9a93-2
[HOLD] firefox-esr:amd64 52.9.0esr-1~deb9u1
[HOLD] linux-doc:amd64 5.7.6-1
[HOLD] linux-headers-amd64:amd64 5.7.6-1
[HOLD] linux-image-amd64:amd64 5.7.6-1
[HOLD] linux-libc-dev:i386 5.7.6-1
[HOLD] unison:amd64 2.48.4-1+b1
[HOLD] xterm:amd64 351-1+local1
[UPGRADE] asymptote:amd64 2.66-1 -> 2.66-1+b1
[UPGRADE] binutils:amd64 2.34.90.20200706-1 -> 2.35-1
[UPGRADE] binutils-common:amd64 2.34.90.20200706-1 -> 2.35-1
[UPGRADE] binutils-doc:amd64 2.34.90.20200706-1 -> 2.35-1
[UPGRADE] binutils-i686-linux-gnu:amd64 2.34.90.20200706-1 -> 2.35-1
[UPGRADE] binutils-x86-64-linux-gnu:amd64 2.34.90.20200706-1 -> 2.35-1
[UPGRADE] bison:amd64 2:3.6.3+dfsg-1 -> 2:3.7+dfsg-1
[UPGRADE] bsdextrautils:amd64 2.35.2-7 -> 2.36-1
[UPGRADE] bsdutils:amd64 1:2.35.2-7 -> 1:2.36-1
[UPGRADE] bzip2:amd64 1.0.8-3 -> 1.0.8-4
[UPGRADE] bzip2-doc:amd64 1.0.8-3 -> 1.0.8-4
[UPGRADE] calendar:amd64 12.1.5 -> 12.1.6
[UPGRADE] coreutils:amd64 8.32-2 -> 8.32-3
[UPGRADE] cpp:amd64 4:9.2.1-3.1 -> 4:10.1.0-1
[UPGRADE] cpp-10:amd64 10.1.0-6 -> 10.2.0-3
[UPGRADE] cpp-9:amd

[Aptitude-devel] Bug#966488: aptitude corrupts package install selection after dpkg error

[Vincent Lefevre]

Package: aptitude
Version: 0.8.13-1+b1
Severity: grave
Justification: causes non-serious data loss

An upgrade with aptitude failed due to a dpkg lock error (bug 95).
Then I noticed that not all packages were upgraded, so that I started
aptitude again to complete the upgrade. I typed 'g', but got:

[1(1)/...] Actions: no changes
e: Examine  !: Apply  .: Next  ,: Previous

and 'e' gives:

  --\ Leave the following recommendations unresolved:   
lcov recommends libgd-gd2-perl

Since lcov recommends libgd-gd2-perl, this means that it was in
the package install selection before the initial upgrade (note
that I didn't have such a warning in the initial upgrade). But
now libgd-gd2-perl is no longer proposed for installation!

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

aptitude version information:
aptitude 0.8.13
Compiler: g++ 9.3.0
Compiled against:
  apt version 6.0.0
  NCurses version 6.2
  libsigc++ version: 2.10.2
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.2.20200212
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7ffd39bec000)
libapt-pkg.so.6.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7f0d243ae000)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7f0d24373000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7f0d24344000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f0d2433b000)
libcwidget.so.4 => /usr/lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7f0d24235000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f0d24109000)
libboost_iostreams.so.1.71.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.71.0 (0x7f0d240e)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f0d23ec6000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f0d23ea4000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f0d23cd7000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f0d23b93000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f0d23b79000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f0d239b2000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7f0d23998000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f0d2397b000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f0d23968000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f0d2393f000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7f0d2391d000)
libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 
(0x7f0d2383e000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f0d23812000)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7f0d23764000)
libgcrypt.so.20 => /usr/lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7f0d23646000)
/lib64/ld-linux-x86-64.so.2 (0x7f0d24a06000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f0d2364)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f0d23633000)
libuuid.so.1 => /usr/lib/x86_64-linux-gnu/libuuid.so.1 
(0x7f0d2362a000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7f0d23604000)

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.7.0-1-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aptitude depends on:
ii  aptitude-common   0.8.13-1
ii  libapt-pkg6.0 2.1.7
ii  libboost-iostreams1.71.0  1.71.0-6+b2
ii  libc6 2.31-2
ii  libcwidget4   0.5.18-5
ii  libgcc-s1 10.2.0-3
ii  libncursesw6  6.2-1
ii  libsigc++-2.0-0v5 2.10.2-1
ii  libsqlite3-0  3.32.3-1
ii  libstdc++610.2.0-3
ii  libtinfo6 6.2-1
ii  libxapian30   1.4.15-1

Versions of packages aptitude recommends:
ii  libdpkg-perl1.20.5
ii  sensible-utils  0.0.12+nmu1

Versions of packages aptitude suggests:
pn  apt-xapian-index
ii  aptitude-doc-en [aptitude-doc]  0.8.13-1
pn  debtags 
ii  tasksel 3.59

-- no debconf information

-- 
Vincent Lefèvre  - Web: 

[Aptitude-devel] Bug#960811: aptitude: unreadable text with default SolutionActionApproved UI style

[Vincent Lefevre]

Package: aptitude
Version: 0.8.12-3
Severity: normal

With the default SolutionActionApproved UI style, the text for
"Leave the following recommendations unresolved" is unreadable
due to the poor choice of color (see attached screenshot).
Adding "set bold" solves the issue.

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

aptitude version information:
aptitude 0.8.12
Compiler: g++ 9.2.1 20200224
Compiled against:
  apt version 6.0.0
  NCurses version 6.2
  libsigc++ version: 2.10.2
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.2.20200212
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7ffe6d539000)
libapt-pkg.so.6.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7f414563e000)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7f4145603000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7f41455d4000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f41455cb000)
libcwidget.so.4 => /usr/lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7f41454c5000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f414539b000)
libboost_iostreams.so.1.67.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.67.0 (0x7f414537b000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f4145161000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f414514)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f4144f73000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f4144e2e000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f4144e14000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f4144c4f000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7f4144c37000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f4144c1a000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f4144c07000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f4144bde000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7f4144bbc000)
libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 
(0x7f4144b1)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f4144ae4000)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7f4144a36000)
libgcrypt.so.20 => /usr/lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7f4144919000)
/lib64/ld-linux-x86-64.so.2 (0x7f4145c9)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f4144914000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f4144907000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f41448fe000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7f41448db000)

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-4-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aptitude depends on:
ii  aptitude-common   0.8.12-3
ii  libapt-pkg6.0 2.1.2
ii  libboost-iostreams1.67.0  1.67.0-17+b1
ii  libc6 2.30-4
ii  libcwidget4   0.5.18-5
ii  libgcc-s1 10-20200502-1
ii  libncursesw6  6.2-1
ii  libsigc++-2.0-0v5 2.10.2-1
ii  libsqlite3-0  3.31.1-5
ii  libstdc++610-20200502-1
ii  libtinfo6 6.2-1
ii  libxapian30   1.4.15-1

Versions of packages aptitude recommends:
ii  libparse-debianchangelog-perl  1.2.0-13
ii  sensible-utils 0.0.12+nmu1

Versions of packages aptitude suggests:
pn  apt-xapian-index
ii  aptitude-doc-en [aptitude-doc]  0.8.12-3
pn  debtags 
ii  tasksel 3.59

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#959869: Bug#959869: aptitude: "aptitude why" should take Provides into account

[Vincent Lefevre]

On 2020-05-06 13:17:11 +0200, Julian Andres Klode wrote:
> On Wed, May 06, 2020 at 12:43:54PM +0200, Vincent Lefevre wrote:
> > zira% aptitude why x11proto-core-dev
> > i   tk8.5-dev Depends x11proto-core-dev
> > 
> > but I can remove the package without breaking the dependency:
> > 
> > zira% apt remove -s x11proto-core-dev
> > NOTE: This is only a simulation!
> >   apt needs root privileges for real execution.
> >   Keep also in mind that locking is deactivated,
> >   so don't depend on the relevance to the real current situation!
> > Reading package lists... Done
> > Building dependency tree   
> > Reading state information... Done
> > The following packages will be REMOVED:
> >   x11proto-core-dev
> > 0 upgraded, 0 newly installed, 1 to remove and 10 not upgraded.
> > Remv x11proto-core-dev [2020.1-1]
> > 
> > Here, x11proto-core-dev is a transitional dummy package to x11proto-dev,
> > and x11proto-dev has:
> 
> IMO: why does not answer the question if there are any blockers to removal,
> it tells you why something was installed, and gives you the shortest path,
> and hence the answer is correct.

But IMHO, not much useful.

> It also follows Recommends or Suggests, and you can still remove
> those packages.

Yes, and this is a good thing. That's precisely the reason why
I use "aptitude why ..." to know whether it would be safe to
remove a package.

BTW, at the same time, the spurious "tk8.5-dev Depends x11proto-core-dev"
can hide real Recommends or Suggests.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#959869: aptitude: "aptitude why" should take Provides into account

[Vincent Lefevre]

Package: aptitude
Version: 0.8.12-3
Severity: wishlist

zira% aptitude why x11proto-core-dev
i   tk8.5-dev Depends x11proto-core-dev

but I can remove the package without breaking the dependency:

zira% apt remove -s x11proto-core-dev
NOTE: This is only a simulation!
  apt needs root privileges for real execution.
  Keep also in mind that locking is deactivated,
  so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be REMOVED:
  x11proto-core-dev
0 upgraded, 0 newly installed, 1 to remove and 10 not upgraded.
Remv x11proto-core-dev [2020.1-1]

Here, x11proto-core-dev is a transitional dummy package to x11proto-dev,
and x11proto-dev has:

Provides: x11proto-bigreqs-dev, x11proto-composite-dev, x11proto-core-dev, 
x11proto-damage-dev, x11proto-dmx-dev, x11proto-dri2-dev, x11proto-dri3-dev, 
x11proto-fixes-dev, x11proto-fonts-dev, x11proto-gl-dev, x11proto-input-dev, 
x11proto-kb-dev, x11proto-present-dev, x11proto-randr-dev, x11proto-record-dev, 
x11proto-render-dev, x11proto-resource-dev, x11proto-scrnsaver-dev, 
x11proto-video-dev, x11proto-xcmisc-dev, x11proto-xext-dev, 
x11proto-xf86bigfont-dev, x11proto-xf86dga-dev, x11proto-xf86dri-dev, 
x11proto-xf86vidmode-dev, x11proto-xinerama-dev

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

aptitude version information:
aptitude 0.8.12
Compiler: g++ 9.2.1 20200224
Compiled against:
  apt version 6.0.0
  NCurses version 6.2
  libsigc++ version: 2.10.2
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.2.20200212
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7ffc727e5000)
libgtk3-nocsd.so.0 => /usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 
(0x7f510d178000)
libapt-pkg.so.6.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7f510cf98000)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7f510cf5d000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7f510cf2e000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f510cf25000)
libcwidget.so.4 => /usr/lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7f510ce1f000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f510ccf3000)
libboost_iostreams.so.1.67.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.67.0 (0x7f510ccd5000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f510cabb000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f510ca9a000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f510c8cd000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f510c788000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f510c76c000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f510c5a9000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f510c5a4000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7f510c58c000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f510c56f000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f510c55c000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f510c531000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7f510c50f000)
libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 
(0x7f510c465000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f510c439000)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7f510c38b000)
libgcrypt.so.20 => /usr/lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7f510c26e000)
/lib64/ld-linux-x86-64.so.2 (0x7f510d5ed000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f510c261000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f510c258000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7f510c235000)

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aptitude depends on:
ii  aptitude-common   0.8.12-3
ii  libapt-pkg6.0 2.1.0
ii  libboost-iostreams1.67.0  1.67.0-17+b1
ii  libc6 2.30-5
ii  libcwidget4   0.5.18-5
ii  libgcc-s1 10-20200502-1

[Aptitude-devel] Bug#934541: aptitude: upgraded a package to experimental without notice, though SolutionCost has "safety" first

[Vincent Lefevre]

On 2020-02-24 09:45:46 +0100, Vincent Lefevre wrote:
> Control: found -1 0.8.12-1
> 
> This bug still occurs. During an upgrade last month:
> 
> Aptitude 0.8.12: log report
> Mon, Jan 27 2020 13:16:20 +0100
> [...]
> [UPGRADE] bash-completion:amd64 1:2.9-1 -> 1:2.10-1
> [UPGRADE] dict-wn:amd64 1:3.0-35 -> 1:3.0-36
> [UPGRADE] ksh:amd64 2020.0.0-2.1 -> 2020.0.0-4
> [UPGRADE] lzip:amd64 1.21-5 -> 1.21-6
> [UPGRADE] mksh:amd64 57-4 -> 57-5
> [UPGRADE] opera-stable:amd64 66.0.3515.36 -> 66.0.3515.44
> [UPGRADE] python-apt:amd64 1.8.5 -> 1.8.6
> [UPGRADE] python-apt-common:amd64 1.8.5 -> 1.9.5
> [UPGRADE] python3-apt:amd64 1.8.5 -> 1.8.6
> [UPGRADE] qpdf:amd64 9.1.0-1 -> 9.1.1-1
> 
> but python-apt-common comes from experimental:
[...]

And note that there is only an unversioned dependency from
python-apt and python3-apt to python-apt-common. Thus there
are 2 (possibly related) issues:

1. A bug in the resolver, which proposed the experimental version,
   though this was not requested by a dependency.

2. A missing warning about the upgrade of an unstable package to
   experimental.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#934541: aptitude: upgraded a package to experimental without notice, though SolutionCost has "safety" first

[Vincent Lefevre]

Control: found -1 0.8.12-1

This bug still occurs. During an upgrade last month:

Aptitude 0.8.12: log report
Mon, Jan 27 2020 13:16:20 +0100
[...]
[UPGRADE] bash-completion:amd64 1:2.9-1 -> 1:2.10-1
[UPGRADE] dict-wn:amd64 1:3.0-35 -> 1:3.0-36
[UPGRADE] ksh:amd64 2020.0.0-2.1 -> 2020.0.0-4
[UPGRADE] lzip:amd64 1.21-5 -> 1.21-6
[UPGRADE] mksh:amd64 57-4 -> 57-5
[UPGRADE] opera-stable:amd64 66.0.3515.36 -> 66.0.3515.44
[UPGRADE] python-apt:amd64 1.8.5 -> 1.8.6
[UPGRADE] python-apt-common:amd64 1.8.5 -> 1.9.5
[UPGRADE] python3-apt:amd64 1.8.5 -> 1.8.6
[UPGRADE] qpdf:amd64 9.1.0-1 -> 9.1.1-1

but python-apt-common comes from experimental:

python-apt (1.9.5) experimental; urgency=medium

  [ Marc Deslauriers ]
  * SECURITY REGRESSION: crash with ubuntu-release-upgrader (LP: #1860606)
- apt/cache.py: make allow_unauthenticated argument to
  fetch_archives() optional.

  [ Julian Andres Klode ]
  * Really bump aptdaemon break (to 1.1.1+bzr982-0ubuntu31)

 -- Julian Andres Klode   Thu, 23 Jan 2020 10:55:46 +0100

while both python-apt and python3-apt were upgraded to unstable
as expected.

AFAIK, I did the upgrade of these packages via the TUI.

Note with "apt-show-versions -u", currently:

python-apt-common:all/experimental *manually* upgradeable from 1.9.5 to 1.9.7

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#940819: aptitude: meaningless message "it is being removed because..." / issue with ORed dependency

[Vincent Lefevre]

On 2019-09-20 11:48:53 +0200, Vincent Lefevre wrote:
> During an upgrade, a package is automatically marked as to be removed
> and the corresponding reason is meaningless:
> 
> xserver-xorg-video-tdfx (remove, 1:1.4.7-1+b1) was installed automatically; 
> it ▒
> is being removed because all of the packages which depend upon it are being   
>  ▒
> removed:  
>  ▒
> 
> but there are no removed packages (no packages are listed).
> 
> FYI:
> 
> zira:~> aptitude why xserver-xorg-video-tdfx
> i   xserver-xorgDepends  xserver-xorg-video-all | 
> xorg-driver-video
> i A xserver-xorg-video-tdfx Provides xorg-driver-video
>  
> 
> and xserver-xorg-video-all is installed. I don't think that this
> output is correct either because as xserver-xorg-video-all is installed,
> the xorg-driver-video dependency should be ignored. Thus this is not the
> reason why xserver-xorg-video-tdfx is installed.

It seems that the real reason is that xserver-xorg-video-tdfx 1:1.4.7-1+b1
(which was installed on my machine) had

Provides: xorg-driver-video

but the new version xserver-xorg-video-tdfx 1:1.5.0-1 no longer has it.

aptitude should detect when the "all of the packages which depend upon
it are being removed" list is empty and output an alternate message
instead, because the reason is different.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

[Aptitude-devel] Bug#934541: aptitude: upgraded a package to experimental without notice, though SolutionCost has "safety" first

[Vincent Lefevre]

Package: aptitude
Version: 0.8.11-7
Severity: important

In /etc/apt/apt.conf.d/10aptitude I have

Aptitude::ProblemResolver::SolutionCost "safety, removals";

but in an upgrade on 2019-07-08, aptitude upgraded a package to
experimental while I did not ask it explicitly and without any
warning. In the logs of the upgrade:

[UPGRADE] gdal-data:amd64 2.4.0+dfsg-1 -> 3.0.1+dfsg-1~exp1

That was perhaps to satisfy a dependency for the upgrade

[UPGRADE] libgdal20:amd64 2.4.0+dfsg-1+b1 -> 2.4.2+dfsg-1

in case gdal-data:amd64 2.4.2+dfsg-1 was not yet in the archives
(though libgdal20:amd64 2.4.2+dfsg-1 was already there).

But I would have never upgraded if I knew that there was an
experimental package there (I occasionally upgrade packages
to experimental, but only for a specific reason).

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

aptitude version information:
aptitude 0.8.11
Compiler: g++ 8.2.0
Compiled against:
  apt version 5.0.2
  NCurses version 6.1
  libsigc++ version: 2.10.1
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.1.20190803
  cwidget version: 0.5.17
  Apt version: 5.0.2

aptitude linkage:
linux-vdso.so.1 (0x7ffdcaf8d000)
libgtk3-nocsd.so.0 => /usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 
(0x7f5982e1c000)
libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 
(0x7f5982c46000)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7f5982c0b000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7f5982bdb000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f5982bd2000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 
(0x7f5982acc000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f59829a6000)
libboost_iostreams.so.1.67.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.67.0 (0x7f5982988000)
libboost_system.so.1.67.0 => 
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.67.0 (0x7f5982981000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f5982755000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f5982734000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f598255c000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f59823d7000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f59823bd000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f59821fc000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f59821f7000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7f59821dd000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f59821c)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f59821ab000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f5982183000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7f5982164000)
libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 
(0x7f59820c4000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f598209e000)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7f5981ffd000)
/lib64/ld-linux-x86-64.so.2 (0x7f598347f000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f5981ff1000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f5981fe8000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7f5981eca000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7f5981ea7000)

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aptitude depends on:
ii  aptitude-common   0.8.11-7
ii  libapt-pkg5.0 1.8.3
ii  libboost-iostreams1.67.0  1.67.0-13
ii  libboost-system1.67.0 1.67.0-13
ii  libc6 2.28-10
ii  libcwidget3v5 0.5.17-11
ii  libgcc1   1:9.1.0-10
ii  libncursesw6  6.1+20190803-1
ii  libsigc++-2.0-0v5 2.10.1-2
ii  libsqlite3-0  3.29.0-1
ii  libstdc++69.1.0-10
ii  libtinfo6 6.1+20190803-1
ii  libxapian30   1.4.11-1

Versions of packages aptitude recommends:
ii  libparse-debianchangelog-perl  1.2.0-13
ii  sensible-utils

[Aptitude-devel] Bug#931619: aptitude: InRelease fetch errors for stable, stable-updates and testing

[Vincent Lefevre]

Package: aptitude
Version: 0.8.11-7
Severity: normal

I get the following obscure error messages when updating from the UI:

┌──┐
│E: Failed to download some files ▒│
│W: Failed to fetch http://ftp.fr.debian.org/debian/dists/stable/InRelease:   ▒│
│W: Failed to fetch http://security.debian.org/dists/stable/updates/InRelease:▒│
│W: Failed to fetch   ▒│
│   http://ftp.fr.debian.org/debian/dists/stable-updates/InRelease:   ▒│
│W: Failed to fetch http://ftp.fr.debian.org/debian/dists/testing/InRelease:  ▒│
│E: Some index files failed to download. They have been ignored, or old ones  ▒│
│   used instead. ▒│
│[ Ok ]│
└──┘

"apt update" has no issues, but it has asked me some questions,
that aptitude didn't do:

N: Repository 'http://security.debian.org stable/updates InRelease' changed its 
'Version' value from '9' to '10'
E: Repository 'http://security.debian.org stable/updates InRelease' changed its 
'Codename' value from 'stretch' to 'buster'
N: This must be accepted explicitly before updates for this repository can be 
applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? 
[y/N] y

etc.

I've attached my /etc/apt/sources.list file.

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

aptitude version information:
aptitude 0.8.11
Compiler: g++ 8.2.0
Compiled against:
  apt version 5.0.2
  NCurses version 6.1
  libsigc++ version: 2.10.1
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.1.20181013
  cwidget version: 0.5.17
  Apt version: 5.0.2

aptitude linkage:
linux-vdso.so.1 (0x7ffe36966000)
libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 
(0x7ff231d99000)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7ff231d5f000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7ff231d31000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7ff231d28000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 
(0x7ff231c22000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7ff231b0)
libboost_iostreams.so.1.67.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.67.0 (0x7ff231ae)
libboost_system.so.1.67.0 => 
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.67.0 (0x7ff231ad9000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7ff2318ad000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7ff23188c000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7ff231709000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7ff231586000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7ff23156a000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7ff2313a9000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7ff23138f000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7ff231171000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7ff23115e000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7ff231136000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7ff231115000)
libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 
(0x7ff231075000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7ff23104f000)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7ff230fae000)
/lib64/ld-linux-x86-64.so.2 (0x7ff2323cf000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7ff230fa9000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7ff230f9d000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7ff230f94000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7ff230e76000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7ff230e53000)

-- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

[Aptitude-devel] Bug#922735: aptitude truncates the version number in the visual interface

[Vincent Lefevre]

Package: aptitude
Version: 0.8.11-7
Severity: normal

aptitude truncates the version number of packages, even when the
window width is large:

i A --\ wpasupplicant   

 
2:2.7+git20190128+0c1e29 2:2.7+git20190128+0c1e29

They should be respectively:
  2:2.7+git20190128+0c1e29f-1
  2:2.7+git20190128+0c1e29f-2

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

aptitude version information:
aptitude 0.8.11
Compiler: g++ 8.2.0
Compiled against:
  apt version 5.0.2
  NCurses version 6.1
  libsigc++ version: 2.10.1
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.1.20181013
  cwidget version: 0.5.17
  Apt version: 5.0.2

aptitude linkage:
linux-vdso.so.1 (0x7ffcb51dc000)
libgtk3-nocsd.so.0 => /usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 
(0x7f0e7ca93000)
libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 
(0x7f0e7c8bd000)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7f0e7c883000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7f0e7c855000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f0e7c84c000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 
(0x7f0e7c746000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f0e7c622000)
libboost_iostreams.so.1.67.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.67.0 (0x7f0e7c604000)
libboost_system.so.1.67.0 => 
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.67.0 (0x7f0e7c5fd000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f0e7c3d2000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f0e7c3b1000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f0e7c22d000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f0e7c0a8000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f0e7c08e000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f0e7becd000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f0e7bec8000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7f0e7beae000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f0e7bc9)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f0e7bc7b000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f0e7bc53000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7f0e7bc34000)
libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 
(0x7f0e7bb94000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f0e7bb6e000)
/lib64/ld-linux-x86-64.so.2 (0x7f0e7d0f6000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f0e7bb62000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f0e7bb59000)

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aptitude depends on:
ii  aptitude-common   0.8.11-7
ii  libapt-pkg5.0 1.8.0~rc3
ii  libboost-iostreams1.67.0  1.67.0-13
ii  libboost-system1.67.0 1.67.0-13
ii  libc6 2.28-7
ii  libcwidget3v5 0.5.17-11
ii  libgcc1   1:8.2.0-21
ii  libncursesw6  6.1+20181013-2
ii  libsigc++-2.0-0v5 2.10.1-2
ii  libsqlite3-0  3.27.1-1
ii  libstdc++68.2.0-21
ii  libtinfo6 6.1+20181013-2
ii  libxapian30   1.4.10-1

Versions of packages aptitude recommends:
ii  libparse-debianchangelog-perl  1.2.0-13
ii  sensible-utils 0.0.12

Versions of packages aptitude suggests:
ii  apt-xapian-index0.49
ii  aptitude-doc-en [aptitude-doc]  0.8.11-7
pn  debtags 
ii  tasksel 3.50

-- no debconf information

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

Re: [Aptitude-devel] Bug#686346: dpkg is wrong about the install state of docbook-mathml, making the system in inconsistent state

[Vincent Lefevre]

On 2012-09-03 21:05:06 +0200, Guillem Jover wrote:
> Control: clone -1 aptitude
> 
> [ CCing aptitude due to the clone, please see the bug report for more
>   details, also about it probably deserving to be serious. ]

The clone still isn't in the BTS while there are more recent bugs
than 2012-09-03 21:05:06 +0200. Did the command succeed?

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Aptitude-devel mailing list
Aptitude-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel