Processed (with 2 errors): Re: Bug#1065625: libmtp9t64 / libmtp-runtime dependency problem makes dpkg fail with attempt of removal of libmtp-common

2024-04-30 Thread Debian Bug Tracking System 
Processing control commands:

> severity -1 important
Bug #1065625 [aptitude] libmtp9t64 / libmtp-runtime dependency problem makes 
dpkg fail with attempt of removal of libmtp-common
Severity set to 'important' from 'serious'
> user release.debian@packages.debian.org
Unknown command or malformed arguments to command.

> usertags -1 time-t-downgrade
Unknown command or malformed arguments to command.


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

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

2024-04-30 Thread Julian Andres Klode 
Control: severity -1 important
Control: user release.debian@packages.debian.org
Control: usertags -1 time-t-downgrade

On Thu, Mar 07, 2024 at 04:00:35PM +0100, Vincent Lefevre wrote:
> Package: libmtp9t64
> Version: 1.1.21-3.1
> Severity: serious
> 
> During an upgrade with aptitude:
> 
> dpkg: dependency problems prevent removal of libmtp-common:
>  libmtp9t64:amd64 depends on libmtp-common.
>  libmtp-runtime depends on libmtp-common.
> 
> dpkg: error processing package libmtp-common (--purge):
>  dependency problems - not removing
> Errors were encountered while processing:
>  libmtp-common
> 
> Note that "apt install -f" has nothing to fix; this upgrade just
> triggered a dpkg error (similar to bug 1065603).
> 
> Moreover, like in bug 1065603, aptitude did not propose the removal
> of libmtp-common:
> 
> Aptitude 0.8.13: log report
> Thu, Mar  7 2024 15:49:03 +0100
> 
>   IMPORTANT: this log only lists intended actions; actions which fail
>   due to dpkg problems may not be completed.
> 
> Will install 11 packages, and remove 3 packages.
> 8192 B of disk space will be used
> 
> [...]
> [HOLD, DEPENDENCIES] libmtp-common:amd64 1.1.21-3
> [...]
> [INSTALL, DEPENDENCIES] libgphoto2-6t64:amd64 2.5.31-2.1
> [INSTALL, DEPENDENCIES] libgphoto2-port12t64:amd64 2.5.31-2.1
> [INSTALL, DEPENDENCIES] libmtp9t64:amd64 1.1.21-3.1
> [REMOVE, DEPENDENCIES] libgphoto2-6:amd64 2.5.31-2
> [REMOVE, DEPENDENCIES] libgphoto2-port12:amd64 2.5.31-2
> [REMOVE, DEPENDENCIES] libmtp9:amd64 1.1.21-3
> [...]
> [UPGRADE] gvfs:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] gvfs-backends:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] gvfs-common:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] gvfs-daemons:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] gvfs-fuse:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] gvfs-libs:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] libgphoto2-l10n:amd64 2.5.31-2 -> 2.5.31-2.1
> [UPGRADE] libmtp-runtime:amd64 1.1.21-3 -> 1.1.21-3.1
> 

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.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

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

2024-04-28 Thread 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)

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

2024-04-28 Thread 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

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

2024-04-28 Thread 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

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

2024-04-28 Thread Sebastian Ramacher 
Control: reassign -1 aptitude 0.8.13-6 

On 2024-03-07 16:34:45 +0100, Vincent Lefevre wrote:
> On 2024-03-07 16:00:35 +0100, Vincent Lefevre wrote:
> > Will install 11 packages, and remove 3 packages.
> > 8192 B of disk space will be used
> > 
> > [...]
> > [HOLD, DEPENDENCIES] libmtp-common:amd64 1.1.21-3
> > [...]
> > [INSTALL, DEPENDENCIES] libgphoto2-6t64:amd64 2.5.31-2.1
> > [INSTALL, DEPENDENCIES] libgphoto2-port12t64:amd64 2.5.31-2.1
> > [INSTALL, DEPENDENCIES] libmtp9t64:amd64 1.1.21-3.1
> > [REMOVE, DEPENDENCIES] libgphoto2-6:amd64 2.5.31-2
> > [REMOVE, DEPENDENCIES] libgphoto2-port12:amd64 2.5.31-2
> > [REMOVE, DEPENDENCIES] libmtp9:amd64 1.1.21-3
> > [...]
> > [UPGRADE] gvfs:amd64 1.53.90-2 -> 1.53.90-3
> > [UPGRADE] gvfs-backends:amd64 1.53.90-2 -> 1.53.90-3
> > [UPGRADE] gvfs-common:amd64 1.53.90-2 -> 1.53.90-3
> > [UPGRADE] gvfs-daemons:amd64 1.53.90-2 -> 1.53.90-3
> > [UPGRADE] gvfs-fuse:amd64 1.53.90-2 -> 1.53.90-3
> > [UPGRADE] gvfs-libs:amd64 1.53.90-2 -> 1.53.90-3
> > [UPGRADE] libgphoto2-l10n:amd64 2.5.31-2 -> 2.5.31-2.1
> > [UPGRADE] libmtp-runtime:amd64 1.1.21-3 -> 1.1.21-3.1
> > 
> 
> Note that libmtp-common:amd64 1.1.21-3.1 was available, but for
> some unknown reason, aptitude did not propose its upgrade.

This looks like another instance of 1065626. Reassigning to aptitude.

Cheers
-- 
Sebastian Ramacher

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

2024-03-07 Thread Vincent Lefevre 
On 2024-03-07 16:00:35 +0100, Vincent Lefevre wrote:
> Will install 11 packages, and remove 3 packages.
> 8192 B of disk space will be used
> 
> [...]
> [HOLD, DEPENDENCIES] libmtp-common:amd64 1.1.21-3
> [...]
> [INSTALL, DEPENDENCIES] libgphoto2-6t64:amd64 2.5.31-2.1
> [INSTALL, DEPENDENCIES] libgphoto2-port12t64:amd64 2.5.31-2.1
> [INSTALL, DEPENDENCIES] libmtp9t64:amd64 1.1.21-3.1
> [REMOVE, DEPENDENCIES] libgphoto2-6:amd64 2.5.31-2
> [REMOVE, DEPENDENCIES] libgphoto2-port12:amd64 2.5.31-2
> [REMOVE, DEPENDENCIES] libmtp9:amd64 1.1.21-3
> [...]
> [UPGRADE] gvfs:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] gvfs-backends:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] gvfs-common:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] gvfs-daemons:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] gvfs-fuse:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] gvfs-libs:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] libgphoto2-l10n:amd64 2.5.31-2 -> 2.5.31-2.1
> [UPGRADE] libmtp-runtime:amd64 1.1.21-3 -> 1.1.21-3.1
> 

Note that libmtp-common:amd64 1.1.21-3.1 was available, but for
some unknown reason, aptitude did not propose its upgrade.

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

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

2024-03-07 Thread Vincent Lefevre 
Package: libmtp9t64
Version: 1.1.21-3.1
Severity: serious

During an upgrade with aptitude:

dpkg: dependency problems prevent removal of libmtp-common:
 libmtp9t64:amd64 depends on libmtp-common.
 libmtp-runtime depends on libmtp-common.

dpkg: error processing package libmtp-common (--purge):
 dependency problems - not removing
Errors were encountered while processing:
 libmtp-common

Note that "apt install -f" has nothing to fix; this upgrade just
triggered a dpkg error (similar to bug 1065603).

Moreover, like in bug 1065603, aptitude did not propose the removal
of libmtp-common:

Aptitude 0.8.13: log report
Thu, Mar  7 2024 15:49:03 +0100

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

Will install 11 packages, and remove 3 packages.
8192 B of disk space will be used

[...]
[HOLD, DEPENDENCIES] libmtp-common:amd64 1.1.21-3
[...]
[INSTALL, DEPENDENCIES] libgphoto2-6t64:amd64 2.5.31-2.1
[INSTALL, DEPENDENCIES] libgphoto2-port12t64:amd64 2.5.31-2.1
[INSTALL, DEPENDENCIES] libmtp9t64:amd64 1.1.21-3.1
[REMOVE, DEPENDENCIES] libgphoto2-6:amd64 2.5.31-2
[REMOVE, DEPENDENCIES] libgphoto2-port12:amd64 2.5.31-2
[REMOVE, DEPENDENCIES] libmtp9:amd64 1.1.21-3
[...]
[UPGRADE] gvfs:amd64 1.53.90-2 -> 1.53.90-3
[UPGRADE] gvfs-backends:amd64 1.53.90-2 -> 1.53.90-3
[UPGRADE] gvfs-common:amd64 1.53.90-2 -> 1.53.90-3
[UPGRADE] gvfs-daemons:amd64 1.53.90-2 -> 1.53.90-3
[UPGRADE] gvfs-fuse:amd64 1.53.90-2 -> 1.53.90-3
[UPGRADE] gvfs-libs:amd64 1.53.90-2 -> 1.53.90-3
[UPGRADE] libgphoto2-l10n:amd64 2.5.31-2 -> 2.5.31-2.1
[UPGRADE] libmtp-runtime:amd64 1.1.21-3 -> 1.1.21-3.1


-- 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 libmtp9t64 depends on:
ii  libc6  2.37-15.1
ii  libgcrypt201.10.3-2
pn  libmtp-common  
ii  libusb-1.0-0   2:1.0.27-1

Versions of packages libmtp9t64 recommends:
ii  libmtp-runtime  1.1.21-3.1
ii  udev255.3-2

libmtp9t64 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)