Re: http://backports.debian.org website squeeze-backports ~bpo60+1 -> wheezy-backports ~bpo70+1 rewrites

[anarcat <anarcat@debian.org>]

On 2013-05-18 02:15:34, Alexander Wirt wrote:
> There is a copy on https://github.com/formorer/backports.debian.org

And here's a patch to update to wheezy, or to say "stable" instead to
avoid having to do this every two years (and forgetting to). :)

diff --git a/Contribute.mdwn b/Contribute.mdwn
index e0748df..2f73346 100644
--- a/Contribute.mdwn
+++ b/Contribute.mdwn
@@ -44,7 +44,7 @@ create and maintain the backport.
 
 * [Subscribe to the backports mailinglist](http://lists.debian.org/debian-backports/). Every announcement and bugreport should come over this mailinglist, so this is a must.
 * Use "squeeze-backports", "squeeze-backports-sloppy" or "wheezy-backports" as distribution, neither "stable" nor "unstable".
-* Make sure that you have a proper build environment which only contains squeeze and no unneeded backports. Maybe you want to consider pbuilder or cowbuilder for building packages.
+* Make sure that you have a proper build environment which only contains stable 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~bpo60+1", or for native packages, "1.2.3" becomes "1.2.3~bpo60+1".
 * Please only upload package with a noteable userbase. User request for the package may be an indicator.
 * Don't backport minor version changes without any user visible changes or bugfixes
@@ -103,7 +103,7 @@ Your mail should follow this template:
     CVE-.... 
       ....
 
-    For the squeeze-backports distribution the problems have been fixed in
+    For the wheezy-backports distribution the problems have been fixed in
     version <packageversion>.
 
     <other distributions if any> 
diff --git a/FAQ.mdwn b/FAQ.mdwn
index df33c68..1cfa794 100644
--- a/FAQ.mdwn
+++ b/FAQ.mdwn
@@ -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](http://buildd.debian.org/status/) of the used buildd network, just enter
-your $package and don't forget to select the squeeze-backports suite from the
+your $package and don't forget to select the wheezy-backports suite from the
 dropdown list. 
 
-**Q: What about dist-upgrade from lenny-backports to squeeze?**
+**Q: What about dist-upgrade from $oldstable-backports to stable?**
 
 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 lenny-backports to squeeze is safe.
+path from an old stable version and backports to the current stable version 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
-[squeeze-backports](http://security-tracker.debian.org/tracker/status/release/stable-backports)
+[stable-backports](http://security-tracker.debian.org/tracker/status/release/stable-backports)
 in the [security tracker](http://security-tracker.debian.org/) (though there
 may be false positives too, the version compare isn't perfect yet) 
 
diff --git a/Instructions.mdwn b/Instructions.mdwn
index 9a206a6..f83e6ff 100644
--- a/Instructions.mdwn
+++ b/Instructions.mdwn
@@ -30,19 +30,20 @@ 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 squeeze-backports install "package"
+    apt-get -t wheezy-backports install "package"
 
 of course you can use aptitude as well:
 
-    aptitude -t squeeze-backports install "package"
+    aptitude -t wheezy-backports install "package"
 
-##squeeze-backports-sloppy
+## stable-backports-sloppy
 
-To guarantee a clean upload path from squeeze-backports to wheezy it is not allowed to upload backports from jessie to squeeze-backports. 
-To allow new backports also in squeeze we created a new suite for everybody that prefer newer packages above a clean upgrade path:
-**squeeze-backports-sloppy**. You can use it exactly as squeeze-backports, just add another line to your **sources.list** and install 
+To guarantee a clean upload path from `stable-backports` to `testing` it is not allowed to upload backports from `testing` to `stable-backports`. 
+To allow new backports also in stable we created a new suite for everybody that prefer newer packages above a clean upgrade path:
+**stable-backports-sloppy**. You can use it exactly as `stable-backports`, just add another line to your **sources.list** and install 
 new packages via
-	apt-get -t squeeze-backports-sloppy install <packages>
+
+	apt-get -t wheezy-backports-sloppy install <packages>
 
 ##Subscribe to the security announce mailinglist
 

Cheers,

A.

PS: why isn't that repository hosted on debian.org infrastructure and
accessible to DDs?

-- 
Si l'image donne l'illusion de savoir
C'est que l'adage pretend que pour croire,
L'important ne serait que de voir
                        - Lofofora