[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1006782: marked as done (apt: libwacom9 : Depends: libwacom-common (= 2.1.0-2) but 1.12-1 is to be installed)

Your message dated Sat, 5 Mar 2022 13:00:21 +0100
with message-id <20220305120021.dsmv7tkeef3vfmdv@crossbow>
and subject line Re: Bug#1006782: apt: libwacom9 : Depends: libwacom-common (= 2.1.0-2) but 1.12-1 is to be installed
has caused the Debian Bug report #1006782,
regarding apt: libwacom9 : Depends: libwacom-common (= 2.1.0-2) but 1.12-1 is to be installed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1006782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006782
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apt
Version: 2.4.0
Severity: important
X-Debbugs-Cc: clinton.winant@gmail.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
attempting routine apt upgrade
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
Don't know enough to attempt fix
   * What was the outcome of this action?
   * What outcome did you expect instead?



-- Package-specific info:

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.16.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 apt depends on:
ii  adduser                 3.118
ii  debian-archive-keyring  2021.1.1
ii  gpgv                    2.2.27-3
ii  libapt-pkg6.0           2.4.0
ii  libc6                   2.33-7
ii  libgcc-s1               11.2.0-16
ii  libgnutls30             3.7.3-4+b1
ii  libseccomp2             2.5.3-2
ii  libstdc++6              11.2.0-16
ii  libsystemd0             250.3-2

Versions of packages apt recommends:
ii  ca-certificates  20211016

Versions of packages apt suggests:
pn  apt-doc         <none>
ii  dpkg-dev        1.21.1
ii  gnupg           2.2.27-3
ii  powermgmt-base  1.36
ii  synaptic        0.90.2+b1

-- no debconf information

On 2 systems running recently installed bookworm, when attempting
routine update/upgrade the following error is thrown:

abraca@XPSGTV:~$ sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libwacom9 : Depends: libwacom-common (= 2.1.0-2) but 1.12-1 is to be installed
E: Broken packages

--- End Message ---
--- Begin Message --- 
Control: forcemerge -1 1006781

On Fri, Mar 04, 2022 at 12:46:39PM -0800, Clinton wrote:
> On 2 systems running recently installed bookworm, when attempting
> routine update/upgrade the following error is thrown:

The information you provided is sparse, but such problems are to be
expected in testing, especially early in the development process.
APTs output makes explicit references to unstable and incoming here, but
testing is faced with similar issues even if much reduced.


> The following packages have unmet dependencies:
>  libwacom9 : Depends: libwacom-common (= 2.1.0-2) but 1.12-1 is to be installed
> E: Broken packages

libwacom had a soname bump recently, it was libwacom2 now it is libwacom9.
Looks like some packages you have still installed (and possibly on hold
or otherwise being considered untouchables by apt) have not been updated
and/or require additional changes.

Note that upgrade isn't allowed to remove packages, which it very
likely wants to do here to a couple of packages, but can't. Compare
with what full-upgrade wants to do to get an idea.


You can investigate why with debug options for apt, our README gives
some pointers [0]. It also mentions what we would need to really look
into this. You will want to talk about anything you find with
the wacom maintainers though as the tiny apt team can't be responsible
for ensuring upgradability of 60.000+ binary packages in Debian and
many more beyond that. That is the job of the package maintainers.

We can provide assistance in particular hard cases, but even in that
case the changes are very seldom done in apt itself for – wait for it –
upgrade reasons, so we need the package maintainers involved anyhow.
I am therefore closing these bugreport(s) as unactionable in apt.

I suggest continuing in #1006437 if you want to convince the maintainer
that this situation is more common and should be fixed. As a sidenote,
I haven't seen this on my unstable machine(s), but that just proves that
to work on such things a lot more details and insight into the
individual packages involved are required.


Best regards

David Kalnischkies

[0] https://salsa.debian.org/apt-team/apt#dependency-resolution

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: