Differences between revisions 35 and 36
Revision 35 as of 2022-01-12 14:52:20
Size: 3234
Editor: ThiagoPezzo
Comment: make translation header easy to include in translations
Revision 36 as of 2022-08-18 03:37:13
Size: 3497
Editor: PaulWise
Comment: document the experimental psuedo-excuses, cleanup
Deletions are marked like this. Additions are marked like this.
Line 17: Line 17:
Line 24: Line 25:
An {{{/etc/apt/sources.list}}} entry for experimental is:{{{
deb http://deb.debian.org/debian experimental main

An {{{/etc/apt/sources.list}}} entry for experimental is:

{{{
deb https://deb.debian.org/debian experimental main
Line 29: Line 33:
To install an experimental package, do:{{{
To install an experimental package, do:

{{{
Line 35: Line 42:
if the package has changed in experimental and you want to upgrade it, do:{{{
I
f the package has changed in experimental and you want to upgrade it, do:

{{{
Line 40: Line 50:
== APT pinning ==
Line 41: Line 52:
== APT pinning ==
Line 43: Line 53:
Line 51: Line 62:
To check which experimental packages are currently installed on your system, do:  To check which experimental packages are currently installed on your system, do:
Line 57: Line 69:
Line 59: Line 72:
== Package checking for experimental ==

The Debian release team [[https://release.debian.org/britney/pseudo-excuses-experimental.html|monitor]] problems that would cause problems when migrating packages from experimental to unstable
Line 60: Line 77:

Translation(s): English - español - Français - Italiano - Português (Brasil) - Svenska

DebianReleases > Debian Experimental


The experimental repository

Introduction

Quoting the Debian FAQ:"project/experimental/: This directory contains packages and tools which are still being developed, and are still in the alpha testing stage. Users shouldn't be using packages from here, because they can be dangerous and harmful even for the most experienced people."

You have been warned

Unlike the Debian Releases unstable and testing, experimental isn't a complete distribution, it can work only as an extension of unstable. So packages in experimental can depend on packages in unstable but packages in unstable cannot depend on packages in experimental. Experimental is a staging/collaboration/experimental area for development, when it is known that a package has problems or may have problems. Some packages/developers don't use experimental, they just put the new versions in unstable. The migration of packages from experimental to unstable is entirely at discretion of the packagers. Even if there are a lot less consistency requirements for packages in experimental, they are autobuilt on the best effort basis by official Debian Package Auto-Building infrastructure.

To configure APT

An /etc/apt/sources.list entry for experimental is:

deb https://deb.debian.org/debian experimental main

To install an experimental package

To install an experimental package, do:

apt update
apt -t experimental install packagename

To upgrade an experimental package

If the package has changed in experimental and you want to upgrade it, do:

apt update
apt -t experimental install packagename

APT pinning

Optionally, if you want to track a given package from experimental, add the following to /etc/apt/preferences (and see AptPreferences):

Package: dash
Pin: release a=experimental
Pin-Priority: 800

Listing all packages installed from experimental

To check which experimental packages are currently installed on your system, do:

aptitude search ~S~i~Aexperimental

Building packages for experimental

See sbuild#Enabling_experimental for building packages for experimental using sbuild.

Package checking for experimental

The Debian release team monitor problems that would cause problems when migrating packages from experimental to unstable


CategoryRelease