[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#1065625: libmtp9t64 / libmtp-runtime dependency problem makes dpkg fail with attempt of removal of libmtp-common

[Facundo Gaich]

Hi,

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

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

[Aptitude-devel] Bug#1070028: aptitude: Extremely alarming warning when pkgs for a foreign architecture will be removed (2 or 3 bugs)

[Manny]

Package: aptitude
Version: 0.8.13-3
Severity: normal
X-Debbugs-Cc: debbug.aptit...@sideload.33mail.com

Aptitude gives a quite extreme warning if it is tasked with removing
packages from a foreign architecture. Packages for i386 were
originally installed to support wine32. The following transcript shows
an upgrade from Bullseye to Bookworm.

===8<
$ aptitude full-upgrade --show-resolver-actions

The following NEW packages will be installed:
  …
The following packages will be REMOVED:
  …
The following packages will be upgraded:
  …
The following packages are RECOMMENDED but will NOT be installed:
  e2fsprogs-l10n exfatprogs laptop-detect libatm1 libnss-systemd libpam-cap 
os-prober thin-provisioning-tools
2130 packages upgraded, 384 newly installed, 451 to remove and 0 not upgraded.
Need to get 0 B/5,556 MB of archives. After unpacking 1,720 MB will be used.
The following packages have unmet dependencies:
  virtualbox : Depends: python3 (< 3.10) but 3.11.2-1+b1 is to be installed
  asymptote : Depends: libgsl27 (>= 2.7.1) but it is not going to be installed
  python3-virtualenv : Depends: python3-pip-whl but it is not going to be 
installed
   Depends: python3-setuptools-whl but it is not going to 
be installed
  filezilla : Depends: libfilezilla34 (>= 0.41.0) but it is not going to be 
installed
  libsemanage1 : Depends: libsemanage-common (= 3.1-1) but 3.4-1 is to be 
installed
The following actions will resolve these dependencies:

  Remove the following packages:
1)  libsemanage1 [3.1-1+b2 (now)]
2)  virtualbox [6.1.26-dfsg-3 (now)]
3)  virtualbox-ext-pack [6.1.26-1 (now)]
4)  virtualbox-qt [6.1.26-dfsg-3 (now)]

  Install the following packages:
5)  libfilezilla-common [0.41.0-2 (stable)]
6)  libfilezilla34 [0.41.0-2 (stable)]
7)  libgsl27 [2.7.1+dfsg-5 (stable)]
8)  python3-pip-whl [23.0.1+dfsg-1 (stable)]
9)  python3-setuptools-whl [66.1.1-1 (stable)]

  Upgrade the following packages:
10) libgslcblas0 [2.6+dfsg-2 (now) -> 2.7.1+dfsg-5 (stable)]

  Leave the following dependencies unresolved:
11) virtualbox-dkms recommends virtualbox (>= 6.1.26-dfsg-3)
12) virtualbox-guest-additions-iso recommends virtualbox (>= 6.1.22)



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

The following NEW packages will be installed:
  …
The following packages will be REMOVED:
  …
The following packages will be upgraded:
  …
The following packages are RECOMMENDED but will NOT be installed:
  e2fsprogs-l10n exfatprogs laptop-detect libatm1 libnss-systemd libpam-cap 
os-prober thin-provisioning-tools
2130 packages upgraded, 389 newly installed, 464 to remove and 0 not upgraded.
Need to get 0 B/5,560 MB of archives. After unpacking 1,526 MB will be used.
Do you want to continue? [Y/n/?] y

The following ESSENTIAL packages will be REMOVED!
  libcrypt1:i386 libgcc-s1:i386

WARNING: Performing this action will probably cause your system to break!
 Do NOT continue unless you know EXACTLY what you are doing!
To continue, type the phrase "I am aware that this is a very bad idea": yikes!

$ aptitude remove wine32:i386; # I would have liked to keep this to manage a 
Garmin satnav but it’s apparently causing the extreme messaging

$ aptitude full-upgrade --show-resolver-actions
  …
  WARNING: Performing this action will probably cause your system to break!
   Do NOT continue unless you know EXACTLY what you are doing!
  To continue, type the phrase "I am aware that this is a very bad idea": wtf

$ aptitude why libcrypt1:i386
i A libcrypt1:i386 Depends libc6:i386 (>= 2.25)
i A libc6:i386 Depends libgcc-s1:i386

$ aptitude why libgcc-s1:i386
i   libwine:i386 Depends libc6:i386 (>= 2.29)
i A libc6:i386   Depends libgcc-s1:i386

$ aptitude why libwine:i386
Manually installed, current version 5.0.3-3, priority optional
No dependencies require to install libwine:i386

$ aptitude remove libwine:i386

$ aptitude why libcrypt1:i386
Automatically installed, current version 1:4.4.18-4, priority optional
No dependencies require to install libcrypt1:i386

$ aptitude why libc6:i386
Automatically installed, current version 2.31-13+deb11u8, priority optional
No dependencies require to install libc6:i386

$ aptitude why zlib1g:i386
Automatically installed, current version 1:1.2.11.dfsg-2+deb11u2, priority 
required
No dependencies require to install zlib1g:i386

$ aptitude why libgcc-s1:i386
Automatically installed, current version 10.2.1-6, priority optional
No dependencies require to install libgcc-s1:i386

$ aptitude remove libcrypt1:i386 libc6:i386 zlib1g:i386 libgcc-s1:i386
The following packages will be REMOVED:
  libc6:i386 libcom-err2:i386{u} libcrypt1:i386 libgcc-s1:i386{u} 
libgssapi-krb5-2:i386{u} libidn2-0:i386{u} libk5crypto3:i386{u} 
libkeyutils1:i386{u} libkrb5-3:i386{u} libkrb5support0:i386{u}
  libnsl2:i386{u} libnss-nis:i386{u} libnss-nisplus:i386{u} libssl1.1:i386{u} 
libtirpc3:i386{u} libunistring2

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

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 aptitude 0.8.13-6
Bug #1065625 [libmtp9t64] libmtp9t64 / libmtp-runtime dependency problem makes 
dpkg fail with attempt of removal of libmtp-common
Bug reassigned from package 'libmtp9t64' to 'aptitude'.
No longer marked as found in versions libmtp/1.1.21-3.1.
Ignoring request to alter fixed versions of bug #1065625 to the same values 
previously set
Bug #1065625 [aptitude] libmtp9t64 / libmtp-runtime dependency problem makes 
dpkg fail with attempt of removal of libmtp-common
Marked as found in versions aptitude/0.8.13-6.

-- 
1065625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065625
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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