view the rest of the comments
Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
Yeah the whole reason for packages being kept back is because they are rolling them out slowly to ensure that no major bugs affect the great majority of users of those packages.
You wouldn't want your whole Ubuntu or Debian user base getting stuck with the same problem and having to roll back all at the same time. availa roll out certain packages slowly so only a small portion have to do it, and also save your reputation, and finally give the package maintainers to fix the problem.
Thanks! I was wondering why that was. I looked at pipewire and it had been updated. That's smart. Very happy to be on a stable base of Debian.
That's an Ubuntu extension to APT. I don't think Debian adopted it, and even if they had, this particular "kept back" message probably comes from a different mechanism.
EDIT: OP is trying to install a backport of a package with a version-specific dependency; I'll address that situation in a top-level comment.
I dunno. Sounds like a repo-specific thing. OP is on Debian 12 and what I'm understanding is they're also seeing this message for a third party repo.