KDE neon’s semi-rolling model: latest KDE on a frozen base
KDE neon pairs an Ubuntu LTS base with rolling KDE packages, but base upgrades require reinstall and PPAs can break apt pinning.
Loading…
ReadMeFeed / Community knowledge
#apt-pinning
Real questions. Useful conversations. Find the people who know your stack.
kdeneonKDE Neon's Hybrid Package Model: When to Use Apt and When to Use Flatpak
KDE Neon splits its package sources between Ubuntu LTS and KDE repositories. Deciding where to install software—apt or Flatpak—determines whether you get stability or freshness.
Controlling Ubuntu LTS Point-Release Updates with APT Pinning and Unattended-Upgrades
Learn how to combine APT pinning with unattended-upgrades to keep Ubuntu LTS servers stable while still receiving automatic security patches—without letting point releases override your pinned dependencies.
ubuntuUsing APT Pinning to Control Package Versions in Debian
Learn how to use APT pinning in Debian to lock specific package versions or prioritize repositories, with step‑by‑step configuration, verification, and rollback steps.
debianChoosing a Debian Release Channel: Stable, Testing, Unstable, and Safe Mixing with APT Pinning
A decision guide for picking a Debian release channel — stable, testing, unstable, or backports — with a concrete APT pinning setup that keeps testing opt-in and validation steps to catch libc-cascade drift.
KDE Neon: Staying on the Ubuntu LTS Base vs Chasing the Latest Plasma Repo
On a single KDE Neon machine I want to decide between two documented approaches: keeping the Ubuntu LTS base as the stable core with apt pinning preferring base packages, versus leaning harder on the KDE Neon user repository for the newest Plasma and KDE apps. The constraint is one machine that must balance security update cadence against feature freshness.
APT pinning priority and dpkg hold interaction across Debian releases
Goal Determine whether an APT pin priority defined in /etc/apt/preferences.d can override a dpkg hold flag when the same package version is available from multiple repositories during a distribution upgrade. Constraints and uncertainty APT evaluates repository pin priorities before selecting a candidate version, while dpkg independently enforces hold status
User Edition APT pinning vs Developer Edition Docker images for repeatable KDE Neon dev with custom Qt PPA
Goal Create a repeatable KDE Neon development environment that includes a custom Qt build from a third‑party PPA while keeping the Plasma stack stable and reproducible across CI runs. Constraint KDE Neon offers two documented paths: pinning the User Edition APT repositories to a specific Plasma release, or using exact‑tag Developer Edition Docker images. Nei