cross-posted from: https://lemmy.g97.top/post/56902

Hi, I’ve this situation when I apt upgrade. There are many pipewire-related packages kept back. Why? How can I solve it?

Thank you!

EDIT: dist-upgrade summary

EDIT2: Ok I solved it with

apt autoremove # only to remove old packages. it didn't solved the problem

apt update

apt dist-upgrade

    • @[email protected]
      9•1 year ago

      Yep, I see this problem every time I upgrade full versions. Always finish off your upgrades with a dist-upgrade and the packages will get cleared up.

        • @[email protected]OP
          3•1 year ago

          You say that because they are listed as removable? If so because I updated from 515 to 525 months ago and today from 525 to 535. I think they are still there but are not used anymore and are safe

    • @[email protected]OPEnglish
      6•1 year ago

      Sorry, I forgot to mention that it’s Pop OS. And I think it started to be stuck in this mode 2 weeks ago

      • Arthur BesseMEnglish
        8•1 year ago

        PopOS is based on Ubuntu, so the Phased Updates answer above most likely explains what you’re seeing.

        If you want to force the immediate upgrading of a given package that is being delayed by phased updates, you can apt install it. (However, note that this will also mark the package as manually installed if it wasn’t already, which means that if you later remove everything else that depended on it, it won’t join the list of “no longer needed” packages which get removed by apt autoremove).

        Typically updates that are being phased should be relatively unimportant, but if you want to know what you’re missing you can also say apt changelog and apt policy (supplying a package name as an argument) to find out what has changed.

        imo phased updates make sense, but ubuntu’s current implementation of them is terribly confusing for commandline users who aren’t aware of them.

        edit: actually according to this and this PopOS disabled phased updates in their focal (20.04) branch back in March. Maybe they’ve come back in jammy (22.04)? Or maybe you actually have some other conflict causing packages to be held back.

        edit2: I see ubuntu lists all of their currently phased updates here and there are far fewer of them currently so this actually does not explain what is in your screenshot. I would guess that you perhaps have installed some non-standard package that conflicts with the pipewire upgrades; perhaps you can find out what it is by saying apt install pipewire-bin and seeing if it asks to remove something in order to upgrade that.

      • @[email protected]English
        4•1 year ago

        The Ubuntu based distros may have this phased update thing. That AskUbuntu link has a command to override APT package manager to install the held-back packages.

        Ubuntu tends to hold back system critical packages in case there are issues. Systems with certain install UUIDs will be ‘guinea pigs’ and install these packages before everyone else. You can override this behavior and disable phased updates on that particular computer.

      • Arthur BesseMEnglish
        1•1 year ago

        see my edits to my previous reply, in case you got the notification about it prior to me editing it.

  • @[email protected]
    5•1 year ago

    So it looks like your old linux headers are causing dependency issues that are preventing upgrades. The dist-upgrade will delete the conflicting packages and update the dependencies. You should be good after that.

  • @hardcoreufo
    3•1 year ago

    You could also try aptitude upgrade instead of apt-get. It tends to handle packages that are kept back better.

  • patchwork
    2•1 year ago

    not sure about apt, but with apt-get the default behavior for upgrade is to hold back packages with new dependencies that are not currently installed. in that case, running sudo apt-get upgrade --with-new-pkgs should get those packages upgraded as well, assuming that dependency conflicts aren’t a factor, too

  • @[email protected]
    2•1 year ago

    Maybe some other packages might have problems with the newer versions. Or it could be one package being kept back due to such reasons and others are its dependencies which also gets kept back to make sure it does not break.

  • style99
    -2•1 year ago

    nVidia drivers are a serious pain. You could brick your system if you aren’t careful.

    • @[email protected]
      5•1 year ago

      Brick is a big word. Nothing that can’t be fix by booting a rescue image and chrooting into your OS.

    • melroy
      2•1 year ago

      you can always run: rmmod nvidia and rmod nouveau. And then buy an AMD videocard. This works always! Thank me later!

    • @[email protected]OP
      1•1 year ago

      You say that because they are listed as removable? If so because I updated from 515 to 525 months ago and today from 525 to 535. I think they are still there but are not used anymore and are safe

    • @wmassingham
      1•1 year ago

      At most I think you’d have to blacklist the module from loading at boot time.