- Ubuntu Documentation
- What are Backports
- Security Support for Backports
- Stability of Backports
- Using Backports
- Enabling Backports
- Enabling Backports on Ubuntu Desktop
- Enabling Backports on Kubuntu
- Enabling Backports Manually
- When Backports Are Installed
- Configuring Backports for Manual Install
- Configuring Backports for Automatic Install
- Installing Backports
- Requesting New Backports
- ru Backports
- Настройка системы
- Добавление репозитория
- С помощью Synaptic
- С помощью командной строки
- Использование backports
- Поиск backports
- Установка backports из командной строки
- Отправка ошибок
- Переход с backports.org на backports.debian.org
- Список установленных пакетов из Backports
- Ссылки
- Backports
- Configuring your stable system
- Adding the repository
- Using Synaptic
- Using the command line
- Using backports
- Finding backports
- Installing backports on the command line
- Reporting bugs
- Migrate from backports.org to backports.debian.org
- List installed backports
- External links
Ubuntu Documentation
What are Backports
When Ubuntu releases a new version of its OS every 6 months, that release is largely frozen in time. While the software that is part of that release will get bug fixes and security patches, new major releases of software and the new features that come with them will not be available.
That’s where Ubuntu Backports comes in. Backports offers a way to selectively provide newer versions of software for older Ubuntu releases. Most commonly, the Backports team will provide new versions of standalone applications which can be safely updated without impacting the rest of the system.
Security Support for Backports
Unlike the packages released with Ubuntu, Backports do not come with any security support guarantee. The Ubuntu Security Team does not update packages in Backports. When a package which has been backported receives a security update, the Ubuntu Backporters will make a best-effort attempt to update the backport.
Stability of Backports
When using Backports, it is important to understand that there is an inherent risk in backporting software. Although backported packages are tested by the community before they are included in the repository, there are very occasionally bad interactions with the older software on your system that are overlooked.
Additionally, the very nature of Backports means that backported packages will change the behavior of the package in ways that may be unfamiliar to users of the older versions, and may be incompatible with configuration format and other options of the older versions.
For this reason, the Backports Team recommends configuring the package manager to only install backported packages when they are explicitly requested, which is the default for all Ubuntu releases after and including Ubuntu 11.04 (Natty Narwhal).
Using Backports
There are two steps to configuring Ubuntu Backports; due to changes in Ubuntu, each step may or may not be necessary on a given release.
First, you must ensure that apt is configured with Backports enabled. On releases after and including Ubuntu 11.10 (Oneiric Ocelot), this is not necessary, as apt is configured with Backports enabled by default.
Second, you must determine whether apt should automatically install packages from Backports, or only install packages from Backports when they are manually requested. The Ubuntu Backporters Team recommends the latter option, and this was made the default for all releases after and including Ubuntu 11.04 (Natty Narwhal). The default for releases prior to Ubuntu 11.04 was to automatically install packages from Backports.
Enabling Backports
Backports were not enabled by default for all releases before (but not including) Ubuntu 11.10 (Oneiric Ocelot). On these releases, backports must be manually enabled before you can install packages from Backports.
Enabling Backports on Ubuntu Desktop
Open the Software Sources control applet. On Ubuntu 10.10 and earlier, click System -> Administration -> Software Sources. On Ubuntu 11.04 and later, search for Software Sources in the Dash.
You will be asked to enter your password. Once you have done that, switch to the Updates tab.
Make sure Unsupported updates is checked.
Enabling Backports on Kubuntu
Search for and start the Muon Package Manager in the KMenu.
Once the Muon Package Manager opens, click Settings -> Configure Software Sources
You will be asked to enter your password. Once you have done that, switch to the Updates tab.
Make sure Unsupported updates is checked.
Enabling Backports Manually
Make sure the following line is in your /etc/apt/sources.list (substituting your release for trusty):
For the Ubuntu armhf or arm64 ports use this line instead:
When Backports Are Installed
Once Backports have been enabled, there are two primary configurations for when the Ubuntu package manager will install packages from Ubuntu Backports. You can configure apt either to always install packages from Ubuntu Backports, or you can configure apt to only install packages from Ubuntu Backports when they are explicitly requested.
On releases before (but not including) Ubuntu 11.04 (Natty Narwhal), apt defaulted to always installing packages from Backports. On later releases, apt only installs packages from Backports when they are explicitly requested.
Because of the potential for unexpected changes when upgrading to a backported package, the Ubuntu Backporters Team recommends configuring apt to only install backported packages on request.
Configuring Backports for Manual Install
Note: This is only necessary on Ubuntu releases before (but not including) Ubuntu 11.04 (Natty Narwhal); releases after and including Ubuntu 11.04 are configured in this mode by default.
As root, edit /etc/apt/preferences. You can do this by pressing Alt+F2, typing gksu gedit /etc/apt/preferences in the Dash, and pressing Enter (the file may not already exist, in which case this will create it)
Add the following text (substituting your release for trusty):
Configuring Backports for Automatic Install
Note: This is only necessary on releases after and including Ubuntu 11.04 (Natty Narwhal); releases before Ubuntu 11.04 are configured in this mode by default.
As root, edit /etc/apt/preferences. You can do this by pressing Alt+F2, typing gksu gedit /etc/apt/preferences in the Dash, and pressing Enter (the file may not already exist, in which case this will create it)
Add the following text (substituting your release for trusty):
Installing Backports
If Backports are configured for automatic install, simply install packages as you normally would, using Ubuntu Software Center, Muon, apt-get, or any other tool. The dependencies of the packages being installed will be resolved from Backports.
If Backports are configured for manual install, you have two options.
Option 1: install the package from Backports, resolve its dependencies from Main.
To do that append /trusty-backports to the package name. For example:
Option 2: install both the package and its dependencies from Backports.
To do that specify -t trusty-backports option. For example:
Requesting New Backports
If you would like to request a new backport, please see our documentation on the backport process.
UbuntuBackports (последним исправлял пользователь madkinder 2015-11-29 11:12:23)
The material on this wiki is available under a free license, see Copyright / License for details
You can contribute to this wiki, see Wiki Guide for details
Источник
- ru
- Backports
Debian Backports — официальный репозиторий пакетов из testing (в основном) и unstable (в некоторых случаях, например, для обновления безопасности) версии Debian, адаптированных для работы в стабильной (stable) версии, иными словами предоставляет свежие версии программ. Рекомендуется устанавливать конкретные пакеты, а не использовать все пакеты из данного репозитория, без нужной необходимости.
В данной статье описано как:
- настроить Debian stable для использования Backports
- найти конкретный backport
- установить пакет из репозитория
- как обновлять выбранный backports автоматически
Настройка системы
Добавление репозитория
С помощью Synaptic
В зависимости от установленных пакетов/версии, внешний вид Synaptic может отличаться. Например, чтобы настройка репозиториев была, как показано ниже, нужно установить пакет software-properties-gtk.
- Откройте Synaptic
Перейдите: Настройки > Репозитории:
- Добавьте репозиторий, нажав кнопку «Добавить»:
deb http://deb.debian.org/debian jessie-backports main contrib non-free
deb http://deb.debian.org/debian jessie-backports-sloppy main contrib non-free
С помощью командной строки
От имени администратора (root) откройте файл /etc/apt/sources.list в текстовом редакторе:
Добавьте следующую строку:
Обновите список пакетов:
Использование backports
Поиск backports
Очень удобно использовать веб-поиск deb пакетов(packages.debian.org). Если Вы запустили Iceweasel, удобнее будет использовать специальный поисковый плагин (Deb Search).
Установка backports из командной строки
Репозиторий Backports ниже основного по приоритету, поэтому нужно указать целевой релиз с помощью опции -t
Данная команд позволит установить более новую версию Iceweasel из Backports вместо версии, предоставляемым стабильным репозиторием. (Примечание: Iceweasel не обязательно должен присутствовать в Backports, но у его майнтейнеров (maintainers) есть свой репозиторий.)
Отправка ошибок
В связи с ограничениями в системе Debian Bug Tracking, любые ошибки, связанные с пакетами backports, по-прежнему должны быть доведены до сведения в списке debian-backports.
Переход с backports.org на backports.debian.org
5 сентября 2010 года Backports стал официальным сервисом (См. объявление).
Система должна быть перестроена с backports.org на использование нового адреса репозитория (в /etc/apt/source.list*), т.к сервис backports.org через некоторое время будет остановлен.
замените backports.org на backports.debian.org в /etc/apt/source.list*.
запустите apt-get update
удалите ключ backports.org. В зависимости от того как вы установили его.
apt-get purge debian-backports-keyring
или
Список установленных пакетов из Backports
Как понять, какие установленные пакеты являются Backports? Один из способов это посмотреть на версию пакета: все пакеты из backports помечены
bpo, например, 24.5+1-6
bpo8+1, следовательно в командной строке можно выполнить следующие:
Ссылки
backports.debian.org Для получение дополнительной информации
Статья о Backports на cliss21.com: В статье содержится информация как backport`ировать пакеты, а также простые примеры.
Источник
- Backports
You are running Debian stable because you prefer the stable Debian tree. It runs great, there is just one problem: The software is a little bit outdated compared to other distributions. That is where backports come in.
Backports are recompiled packages from testing (mostly) and unstable (in a few cases only, e.g. security updates), so they will run without new libraries (wherever it is possible) on a stable Debian distribution. It is recommended to pick out single backports which fit your needs, and not to use all backports available.
This article illustrates how to:
- configure your stable system to use the Backports repository
- find a specific backport
- install packages from the repository
- have your backports upgraded automatically
For official instructions on how to use Debian Backports, visit https://backports.debian.org/Instructions/.
If you want to create a non-official backport of a package you need, have a look at SimpleBackportCreation.
If you want to build a backport with the intent of sharing it with others within Debian, see the BuildingFormalBackports page.
Configuring your stable system
In the following example, we will use bullseye as the current codename for Debian Stable. Please adjust the codename accordingly if you are using a different version of Debian.
If you’re setting up backports for a system that isn’t running the latest version of Debian (e.g. a buster system while the latest is bullseye) then you will also want to add a line for the «sloppy» backports section. Currently that is buster-backports-sloppy, but after the release of bookworm, you’ll want to add a line for bullseye-backports-sloppy.
Adding the repository
Using Synaptic
Go to «Settings -> Repositories«:
In the following dialog box, select the tab «Third-Party Software» and click on the «Add. » button in the lower left corner:
Copy the repository below, then hit the «Add Source» button:
deb http://deb.debian.org/debian bullseye-backports main contrib non-free
Finally, hit the «Reload» button in Synaptic’s main panel to update the repository information on your system.
Using the command line
As root, or using sudo, open your sources.list file (Nano is the recommended editor for new users):
Append the following line to the bottom of the file:
If you are a free software enthusiast, you might want to remove the contrib and non-free sections. (See Debian package management for details.)
Now that you have added the repository, update APT’s cache to include the backports in the list of available packages:
Using backports
Finding backports
There are a several different ways to find out if a backport of a certain Debian package exists. A pretty convenient one is using Debian’s web-based package search (packages.debian.org).
Backported versions of packages will also appear when searching their names with the apt search command, or one can view all available versions of a package by running:
Replacing package-name with the name of the package you wish to view.
Installing backports on the command line
The backports repository is deactivated by default. So, if you want to install a backported package, you will have to state that explicitly.
The -t option here specifies bullseye-backports as the target release. This would install a newer version of Cockpit and all its reverse dependencies from bullseye-backports instead of the older one from Debian stable release.
Reporting bugs
Because of limitations in the Debian Bug Tracking System, any bugs relevant to backported packages still have to be reported to the debian-backports list.
Migrate from backports.org to backports.debian.org
On Sept. 5th, 2010, Backports became an official service (see announcement).
Systems configured to use backports.org should be reconfigured to use the new repository/URL (in /etc/apt/sources.list*), since backports.org service is already stopped.
replace backports.org with http://deb.debian.org/debian in /etc/apt/sources.list*.
run apt update
remove the backports.org key from your keyring. Depending how you installed it.
apt purge debian-backports-keyring
or
List installed backports
Out of all installed packages, which ones are backports? One way to tell is by version: all backports are tagged with
bpo, for example, 24.5+1-6
bpo8+1, so at the command line you might say:
External links
Article about backports on cliss21.com: The article contains information on how to backport packages as well as some step-by-step simple examples to start with.
Diffs between bullseye-backports and bookworm: A useful comparison of package versions in bullseye-backports and bookworm.
Источник