Debian 13.3 is now available for download as a new point release to Debian 13 “Trixie” with 108 bug fixes and 37 security updates.

The post Debian 13.3 “Trixie” Released with 108 Bug Fixes and 37 Security Updates appeared first on 9to5Linux - do not reproduce this article without permission. This RSS feed is intended for readers, not scrapers.

Raspberry Pi OS 2025-10-01 is now available for download with based on Debian 13 "Trixie" and featuring new GTK and icon themes, as well as numerous other improvements.

The post Raspberry Pi OS Is Now Based on Debian 13 “Trixie” with Fresh New Look appeared first on 9to5Linux - do not reproduce this article without permission. This RSS feed is intended for readers, not scrapers.

MX Linux 25 distribution is now available for public beta testing based on the Debian 13 "Trixie" operating system series. Here's what's new!

The post MX Linux 25 “Infinity” Enters Public Beta Testing Based on Debian 13 “Trixie” appeared first on 9to5Linux - do not reproduce this article without permission. This RSS feed is intended for readers, not scrapers.

MX Linux 23.5 distribution is now available for download based on Debian GNU/Linux 12.9 “Bookworm” and powered by Linux kernel 6.12 LTS. Here’s what’s new!

The post MX Linux 23.5 Released with Xfce 4.20 and Linux 6.12 LTS, Based on Debian 12.9 appeared first on 9to5Linux - do not reproduce this article without permission. This RSS feed is intended for readers, not scrapers.

Debian 12.9 is now available for download with 72 bug fixes and 38 security updates for the Debian GNU/Linux 12 “Bookworm” operating system series.

The post Debian 12.9 “Bookworm” Arrives with 72 Bug Fixes and 38 Security Updates appeared first on 9to5Linux - do not reproduce this article without permission. This RSS feed is intended for readers, not scrapers.

The next Debian/Ubuntu releases will likely no longer allow pip install outside a virtual environment or separate Python installs because of conflicts between pip and the OS package manager. It can still be forced, but that's strongly not recommended.

Software shipped with a Linux distribution can be (quite easily, I might add) broken by installing packages using pip. All the user has to do is install a package (or some of its dependencies) that's newer and backwards-incompatible with a version that was installed from the Linux distribution official repositories. And this isn't even about breaking some application—because Python is so widely used nowadays, users can easily break critical distro packages.

The breakage can occur for both system-wide pip installations (sudo pip install), as well as user installations (pip install --user), but especially the latter, since trying to recover from this might result in removing (using pip, not the distro package manager) packages installed using the Linux distribution's package manager.

For this reason, the next Debian (Debian 12 Bookworm) and Ubuntu (Ubuntu 23.04 Lunar Lobster) releases will likely adopt PEP668 (PEP = Python Enhancement Proposal), marking the Python base environments as "externally managed", and no longer allowing regular pip install usage for both user and system installations. This can still be forced though, and obviously, there are alternatives—see below.

The change is already live in Debian Testing and Ubuntu 23.04 Lunar Lobster (which will have a beta release on March 30, with the final release expected on April 20). There's also a proposal to include this in Fedora 38 (which had a beta release today), but this has not landed in Fedora 38 for now.

I said "likely adopt" because, even though this change is already present in Debian Testing and Ubuntu 23.04 Lunar Lobster, Stefano Rivera, one of the Debian/Ubuntu Python maintainers, mentioned that "if necessary, we can roll back EXTERNALLY-MANAGED in our python3.11 for bookworm’s release, but I’d like to make this happen…". 

[[Edit]] This change has made it into the Ubuntu 23.04 Lunar Lobster release! When trying to install a Python package using pip, users will now see this message: "error: externally-managed-environment" / "This environment is externally managed".

So what are the alternatives to using pip install directly and solve this externally managed environment pip error? Take a look below: