Commit fbe52abf authored by Alexander Wirt's avatar Alexander Wirt

Update to stretch

parent ec8035cd
......@@ -19,8 +19,8 @@ tracker](https://rt.debian.org/Ticket/Create.html?Queue=20)
request tracker). Once your UID is added, wait an hour for the cronjob to import your upload rights and you can start uploading.
The upload happens in the same way as normal uploads to the archive happens,
just the distribution have to match one of the backports distributions (wheezy-backports,
wheezy-backports-sloppy, jessie-backports)
just the distribution have to match one of the backports distributions (jessie-backports,
jessie-backports-sloppy, stretch-backports)
**The special host in dupload/dput that was needed in the past is now obsolete and doesn't work
anymore.**
......@@ -69,15 +69,15 @@ unstable or stable as target distribution.
| Source Distribution | Backports Distribution | Version suffix |
|---------------------|---------------------------------------------|----------------------|
| jessie | wheezy-backports | ~bpo70+1 |
| stretch | jessie-backports or wheezy-backports-sloppy | ~bpo8+1 or ~bpo7+1 |
| stretch | jessie-backports | ~bpo8+1 |
| buster | stretch-backports or jessie-backports-sloppy | ~bpo9+1 or ~bpo8+1 |
###Basic Rules
* [Subscribe to the backports mailing list](https://lists.debian.org/debian-backports/). Every announcement and bug report should come over this mailing list, so this is a must.
* Make sure that you have a proper build environment that only contains the suite for which the backport is for (e.g. jessie if you want to upload to jessie-backports) and no unneeded backports. Maybe you want to consider pbuilder or cowbuilder for building packages.
* Append "~bpo${debian_release}+${build_int}" to the version number, e.g. "1.2.3-4" now becomes "1.2.3-4~bpo8+1", or for native packages, "1.2.3" becomes "1.2.3~bpo8+1". For packages to wheezy-backports stick to 70 for the debian_release, which would become 1.2.3~bpo70+1 in our example. wheezy-backports-sloppy also uses 7 instead of 70.
* Append "~bpo${debian_release}+${build_int}" to the version number, e.g. "1.2.3-4" now becomes "1.2.3-4~bpo8+1", or for native packages, "1.2.3" becomes "1.2.3~bpo8+1".
* Please only upload package with a notable userbase. User request for the package may be an indicator.
* Don't backport minor version changes without any user visible changes or bugfixes
* To guarantee an upgrade path from stable+backports to the next stable, the
......@@ -115,8 +115,8 @@ If you feel you would need to diverge from these rules, either discuss it on the
With the release of a new stable version uploading packages with versions greater than in new stable or
new stable-security are not allowed. If you want newer package versions in old-stable-backports we created a
new suite for that: oldstable-backports-sloppy. So if you want to upload a package from stretch to wheezy-backports
use wheezy-backports-sloppy as target distribution.
new suite for that: oldstable-backports-sloppy. So if you want to upload a package from buster to jessie-backports
use jessie-backports-sloppy as target distribution.
###Additionally
......@@ -130,12 +130,15 @@ to make it run on stable.
##Security Uploads
If you upload a package which fixes security related problems please send a gpg inline signed
mail to the [debian-backports-announce mailing list](https://lists.debian.org/debian-backports-announce).
In advance ask <backports-team@debian.org> for a new BSA number.
If you upload a package which fixes security related problem please create a
ticket in the debian [request tracker](https://rt.debian.org/Ticket/Create.html?Queue=20)
- please use the backports queue for the ticket. (See
[wiki](https://wiki.debian.org/rt.debian.org) for more information about the
request tracker).
Your mail should follow this template:
Please follow the following template and provide us with the required
information to write a BSA. Please don't wait for the BSA and upload
immediatly.
Subject: [BSA-XXX] Security Update for <packagename>
......@@ -148,14 +151,11 @@ Your mail should follow this template:
CVE-....
....
For the jessie-backports distribution the problems have been fixed in
For the stretch-backports distribution the problems have been fixed in
version <packageversion>.
<other distributions if any>
The mailing list is moderated so please be a little bit patient if your post does not appear immediately on the list.
##Best Practice
###Check NEW queue
......@@ -178,7 +178,7 @@ to update the backports.
###Inform the Backporter
If there is already a backport of your package of choice but it's outdated and you want to update it please inform the person who backported the last accepted version about your intentions. You can get the information from <https://backports.debian.org/changes/jessie-backports.html>
If there is already a backport of your package of choice but it's outdated and you want to update it please inform the person who backported the last accepted version about your intentions. You can get the information from <https://backports.debian.org/changes/stretch-backports.html>
###Uploaders
......
......@@ -16,14 +16,14 @@ getting signed by the buildd admins. Those are often enough also busy with
other work (or if time permits real life), which might also add to a delay in
the uploads. You can check the status on the [Buildd Information
Page](https://buildd.debian.org/status/) of the used buildd network, just enter
your $package and don't forget to select the wheezy-backports suite from the
your $package and don't forget to select the jessie-backports suite from the
dropdown list.
**Q: What about dist-upgrade from wheezy-backports to jessie?**
**Q: What about dist-upgrade from jessie-backports to stretch?**
A: In general, backports.debian.org only has backports made from testing but with
reduced version numbers (apt considers ~ lower than -), therefore the upgrade
path from wheezy-backports to jessie is safe.
path from jessie-backports to stretch is safe.
**Q: Is there security support for packages from backports.debian.org?**
......@@ -32,7 +32,7 @@ track the package, usually the ones who originally did upload the package into
backports. When security related bugs are fixed in Debian unstable the
backporter is permitted to upload the package from directly there instead of
having to wait until the fix hits testing. You can see the open issues for
[wheezy-backports](https://security-tracker.debian.org/tracker/status/release/stable-backports)
[jessie-backports](https://security-tracker.debian.org/tracker/status/release/stable-backports)
in the [security tracker](https://security-tracker.debian.org/) (though there
may be false positives too, the version compare isn't perfect yet)
......@@ -40,7 +40,7 @@ may be false positives too, the version compare isn't perfect yet)
A: Something like the following solutions should work:
dpkg -l |awk '/^ii/ && $3 ~ /bpo[6-8]/ {print $2}'
dpkg -l |awk '/^ii/ && $3 ~ /bpo[7-9]/ {print $2}'
or
......
......@@ -17,14 +17,14 @@ your needs, and not use all available backports.
##Add backports to your sources.list
1. For wheezy add this line
<pre>deb http://ftp.debian.org/debian wheezy-backports main</pre> to your **sources.list**
1. For jessie add this line
<pre>deb http://ftp.debian.org/debian jessie-backports main</pre> to your **sources.list**
(or add a new file with the ".list" extension to /etc/apt/sources.list.d/)
You can also find a list of other mirrors at
<https://www.debian.org/mirror/list>
For jessie add this line
<pre>deb http://ftp.debian.org/debian jessie-backports main</pre> to your **sources.list**
For stretch add this line
<pre>deb http://ftp.debian.org/debian stretch-backports main</pre> to your **sources.list**
(or add a new file with the ".list" extension to /etc/apt/sources.list.d/)
You can also find a list of other mirrors at
<https://www.debian.org/mirror/list>
......@@ -35,26 +35,26 @@ your needs, and not use all available backports.
All backports are deactivated by default (i.e. the packages are pinned to 100 by using ButAutomaticUpgrades: yes in the Release files. If you want to install something from backports run:
apt-get -t jessie-backports install "package"
apt-get -t stretch-backports install "package"
of course you can use aptitude as well:
aptitude -t jessie-backports install "package"
aptitude -t stretch-backports install "package"
##sloppy distributions
To guarantee a clean upgrade path from a previously stable distribution to the
next stable it is not allowed to upload packages from the current testing to
that backport distribution. To allow some newer packages for those systems we
create so called sloppy distributions. For oldstable (wheezy) packages from
create so called sloppy distributions. For oldstable (jessie) packages from
the current testing (stretch) are allowed to be uploaded to
wheezy-backports-sloppy.
jessie-backports-sloppy.
You can use it exactly as the current backports distribution, just add another line to your **sources.list** and install
new packages via
apt-get -t wheezy-backports-sloppy install <packages>
apt-get -t jessie-backports-sloppy install <packages>
or
apt-get -t jessie-backports install <packages>
apt-get -t stretch-backports install <packages>
##Subscribe to the security announce mailing list
......
......@@ -2,9 +2,9 @@
If you are interested in a browseable directory included in debian-backports, you can use these overviews:
<ul>
<li><a href="http://packages.debian.org/stretch-backports/">jessie-backports</a></li>
<li><a href="http://packages.debian.org/jessie-backports/">jessie-backports</a></li>
<li><a href="http://packages.debian.org/wheezy-backports/">wheezy-backports</a></li>
<li><a href="http://packages.debian.org/wheezy-backports-sloppy/">wheezy-backports-sloppy</a></li>
<li><a href="http://packages.debian.org/jessie-backports-sloppy/">jessie-backports-sloppy</a></li>
<p />
If you rather want to search for an individual package, please use the forms below.
......@@ -30,9 +30,9 @@ Section:
Distribution:
<select name="suite">
<option value="jessie-backports" selected="selected">jessie-backports</option>
<option value="wheezy-backports-sloppy">wheezy-backports-sloppy</option>
<option value="wheezy-backports">wheezy-backports</option>
<option value="stretch-backports" selected="selected">jessie-backports</option>
<option value="jessie-backports-sloppy">jessie-backports-sloppy</option>
<option value="jessie-backports">jessie-backports</option>
</select>
</form>
......
......@@ -14,12 +14,12 @@
#Miscellaneous
* Uploaders
* [Wheezy](/changes/wheezy-backports.html)
* [Wheezy-sloppy](/changes/wheezy-backports-sloppy.html)
* [Jessie](/changes/jessie-backports.html)
* [Jessie-sloppy](/changes/jessie-backports-sloppy.html)
* [Stretch](/changes/stretch-backports.html)
* [NEW Queue](https://ftp-master.debian.org/backports-new.html)
* Diffstats
* [[wheezy|wheezy-backports/overview]]
* [[wheezy-sloppy|wheezy-backports-sloppy/overview]]
* [[jessie|jessie-backports/overview]]
* [[jessie-sloppy|jessie-backports-sloppy/overview]]
* [[stretch|jessie-backports/overview]]
* [Feedback](mailto:backports-team@debian.org)
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment