(SOLVED) Sid – Dependency hell for wacom updates to 2.0.0-1

Forum Forums New users New Users and General Questions (SOLVED) Sid – Dependency hell for wacom updates to 2.0.0-1

  • This topic has 4 replies, 3 voices, and was last updated Feb 7-4:34 pm by stevesr0.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #76962
    Member
    stevesr0

      Hi,

      I just did an apt update and full upgrade and found two packages were held back libwacom-bin and libwacom-common. I checked in aptitude and found that libwacom-bin was dependent on libwacom9 and libwacom9 is dependent on libwacom-common. Libwacom-bin and libwacom-common (version 1.12) are installed, but libwacom9 ISN’T installed and requires libwacom-common version 2.0.0-1.

      Libwacom-common is not said to have any dependencies, SO I simulated it’s upgrade with apt.

      This resulted in a note that 70+ packages would no longer be needed and could be removed by sudo apt autoremove, 27 packages would be removed and libwacom-common, libwacom-common and libwacom9 (all version 2.0.0-1) would be installed.

      I searched for a report of a problem with upgrading the wacom library files, but haven’t seen any.

      Since I don’t need to use the wacom tools on this laptop, I am not going to upgrade. Perhaps there will be another upgrade that will resolve this.

      I am posting in case anyone else is having a problem with this wacom upgrade or how to fix it (being a curious sort).

      stevesr0

      • This topic was modified 1 year, 3 months ago by christophe. Reason: added "sid" to the title for clarification
      • This topic was modified 1 year, 3 months ago by stevesr0.
      #76963
      Anonymous
        Helpful
        Up
        0
        ::

        Libwacom-bin and libwacom-common (version 1.12) are installed, but

        packages.debian.org/search?keywords=libwacom&searchon=names&suite=all&section=all

        Package libwacom-common

        stretch (oldoldstable) (libs): Wacom model feature query library (common files)
        0.22-1: all
        buster (oldstable) (libs): Wacom model feature query library (common files)
        0.32-1: all
        bullseye (stable) (libs): Wacom model feature query library (common files)
        1.8-2: all
        bookworm (testing) (libs): Wacom model feature query library (common files)
        1.12-1: all
        sid (unstable) (libs): Wacom model feature query library (common files)
        2.0.0-1: all

        ??? You are using bookworm aka testing repository, and hoped to install 2.0.0.-1 from sid//unstable ?

        • This reply was modified 1 year, 2 months ago by Brian Masinick. Reason: From skidoo
        #76965
        Forum Admin
        anticapitalista
          Helpful
          Up
          0
          ::

          Be patient and wait for it to be fixed upstream.
          The joys of using sid.

          Philosophers have interpreted the world in many ways; the point is to change it.

          antiX with runit - leaner and meaner.

          #76985
          Member
          stevesr0
            Helpful
            Up
            0
            ::

            Hi skidoo and anticapitalista,

            Thanks for responses.

            Skidoo, No I am using Sid. I believe the previous version for Sid was 1.12-1 which I have installed. This latest upgrade went to 2.0.0-1. I imagine that this is a temporary glitch that might be fixed by the developers in an update. I emailed this story to the developer.

            Anticapitalista, Waiting is my plan <g>.

            stevesr0

            #76992
            Member
            stevesr0
              Helpful
              Up
              0
              ::

              As anticapitalista said, wait for them to fix it. I think it took less than 24 hours. My update today went smoothly without hold back or massive removals <g>.

              Sid is fun (so far, as long as I don’t depend on this computer.)

              stevesr0

            Viewing 5 posts - 1 through 5 (of 5 total)
            • You must be logged in to reply to this topic.