Language Selection

English French German Italian Portuguese Spanish

How I mix Debian testing, unstable and experimental

Filed under
HowTos

Apart from the stable Debian Sarge, I'm now using Debian testing/unstable for my desktop. After the latest adventures in SuSEland, what could be more thrilling? (Nothing, except for Gentoo Stage 1 or Linux From Scratch.)

Using Debian Etch (testing) is not for the typical user of SuSE, Mandriva, or PCLOS. But it's much easier to get things fixed than in Slackware, and it's definitely a way to (apt-)get binary packages of almost anything, no compile time needed.

While Debian 'testing' is rather stable, it's not a release per se, but a living version of Debian. Therefore, when a package migrates from 'unstable' to 'testing', nobody could really guarantee you will be able to install it on your own Debian testing machine with all the dependencies met!

That's why you will occasionally have to met dependencies from 'unstable'. (Maybe this is the reason for /etc/debian_version to state: testing/unstable).

But this is also the reason this shouldn't be done with a production server, unless you can physically be close to the server to fix problems, should they arise.

One you accepted to use Debian testing/unstable, why shouldn't you be able to use 'experimental' repositories as well? Only with selected packages, of course, like the latest GIMP 2.3.x Wink

The whole idea is actually explained in the manual, but let's make it simpler.

Full Story.

More in Tux Machines

Kernel Space/Linux

Red Hat News

openSUSE Tumbleweed: A Linux distribution on the leading edge

So, to summarize: openSUSE Tumbleweed is a good, solid, stable Linux distribution with a wide range of desktops available. It is not anything particularly exotic or unstable, and it does not require an unusual amount of Linux expertise to install and use on an everyday system. To make a very simple comparison, in my experience installing and using Tumbleweed is much less difficult and much less risky than using the Debian "testing" distribution, and it is kept much (much much) more up to date than openSUSE Leap, Debian "stable", Linux Mint or Ubuntu. I don't say that to demean any of those other distributions. As I said at the end of my recent post about point-release vs. rolling-release distributions, if your hardware is fully supported by one of those point-release distributions, and you are satisfied with the applications included in them, then they are certainly a good choice. But if you like staying on the leading edge, or if you have very new hardware which requires the latest Linux kernel and drivers, or you just want/need the latest version of some application (in my case this would be digiKam), then openSuSE could be just what you want. Read more Also: Google Summer of Code 2017

Graphics in Linux

  • 17 Fresh AMDGPU DC Patches Posted Today
    Seventeen more "DC" display code patches were published today for the AMDGPU DRM driver, but it's still not clear if it will be ready -- or accepted -- for Linux 4.12. AMD developers posted 17 new DC (formerly known as DAL) patches today to provide small fixes for Vega10/GFX9 hardware, various internal code changes, CP2520 DisplayPort compliance, and various small fixes.
  • libinput 1.7.0
  • Libinput 1.7 Released With Support For Lid Switches, Scroll Wheel Improvements
    Peter Hutterer has announced the new release of libinput 1.7.0 as the input handling library most commonly associated with Wayland systems but also with Ubuntu's Mir as well as the X.Org Server via the xf86-input-libinput driver.
  • Nouveau TGSI Shader Cache Enabled In Mesa 17.1 Git
    Building off the work laid by Timothy Arceri and others for enabling a TGSI (and hardware) shader cache in the RadeonSI Gallium3D driver as well as R600g TGSI shader cache due ot the common infrastructure work, the Nouveau driver is now leveraging it to enable the TGSI shader cache for Nouveau Gallium3D drivers.