Commit e60f5b6c authored by Alexander Wirt's avatar Alexander Wirt

Upgrade several urls to https

parent 673ab82c
......@@ -15,7 +15,7 @@ All Debian Developers (DD) can get their uid into the backports ACL. If
you want to get include please open 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](http://wiki.debian.org/rt.debian.org) for more information about the
[wiki](https://wiki.debian.org/rt.debian.org) for more information about the
request tracker). Once your key is imported, you can start uploading.
The upload happens in the same way as normal uploads to the archive happens,
......@@ -42,7 +42,7 @@ create and maintain the backport.
###Basic Rules
* [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.
* [Subscribe to the backports mailinglist](https://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.
* 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".
......@@ -63,7 +63,7 @@ include the changelog entrys (but you are free to do so).
users and if you want to support the package until support for the distribution
you uploaded ends.
If you feel you would need to diverge from these rules, either discuss it on the [mailinglist](http://lists.debian.org/debian-backports/) or bring it up with the [Backports Team](mailto:backports-team@debian.org) for an exception.
If you feel you would need to diverge from these rules, either discuss it on the [mailinglist](https://lists.debian.org/debian-backports/) or bring it up with the [Backports Team](mailto:backports-team@debian.org) for an exception.
###Uploads for old-stable backports
......@@ -86,7 +86,7 @@ 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 mailinglist](http://lists.debian.org/debian-backports-announce).
mail to the [debian-backports-announce mailinglist](https://lists.debian.org/debian-backports-announce).
In advance ask <backports-team@debian.org> for a new BSA number.
......@@ -116,7 +116,7 @@ Your mail should follow this template:
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository to
200 so that new versions of installed backports will be installed
......@@ -134,7 +134,7 @@ The Mailinglist is moderated so please be a little bit patient if your post does
###Check NEW queue
Check the NEW queue at <http://ftp-master.debian.org/backports-new.html> to avoid
Check the NEW queue at <https://ftp-master.debian.org/backports-new.html> to avoid
double efforts before you start to backport something.
###Inform the Maintainer
......@@ -142,22 +142,22 @@ double efforts before you start to backport something.
It is a good idea to contact the maintainer of the package in Debian prior to
your upload to let them know or even share ideas and common pitfalls (like
special dependencies). If you are not already
[subscribed](http://lists.debian.org/debian-backports) to
[subscribed](https://lists.debian.org/debian-backports) to
<debian-backports@lists.debian.org>, please do so. There might be
questions/problems from users regarding your backport(s) which you can answer
best and hopefully solve. Also it is adviced to subscribe to the bugreports for
the package through the [PTS](http://packages.qa.debian.org/) to be notified
the package through the [PTS](https://packages.qa.debian.org/) to be notified
about issues that potential affect the backport too and would be a good reason
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 intensions. You can get the information from <http://backports.debian.org/changes/squeeze-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 intensions. You can get the information from <https://backports.debian.org/changes/squeeze-backports.html>
###Uploaders
If you put yourself into the Uploaders: field in debian/control you can easily
track your backports on the package overview at
<http://qa.debian.org/developer.php>. Alternatively you can use the
[subscribe feature](http://qa.debian.org/developer.php#subscribe) of the DDPO
<https://qa.debian.org/developer.php>. Alternatively you can use the
[subscribe feature](https://qa.debian.org/developer.php#subscribe) of the DDPO
to have them listed.
......@@ -3,7 +3,7 @@
**Q: Where shall I report bugs I found in packages from backports to?**
A: Please report them to the
[debian-backports mailinglist](http://lists.debian.org/debian-backports/). The
[debian-backports mailinglist](https://lists.debian.org/debian-backports/). The
Debian bugtracking system doesn't know anything about backports versions, and
sometimes the backporter isn't in the Debian packaging team so they might miss
the report.
......@@ -15,7 +15,7 @@ The rest of the architectures have to go through the build network and the logs
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
Page](https://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
dropdown list.
......@@ -32,8 +32,8 @@ 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)
in the [security tracker](http://security-tracker.debian.org/) (though there
[squeeze-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)
**Q: How to get a list of all installed backports?**
......
......@@ -46,8 +46,8 @@ new packages via
##Subscribe to the security announce mailinglist
If you want to get announcements about security updates on backports.debian.org subscribe to the [debian-backports-announce mailinglist](http://lists.debian.org/debian-backports-announce/).
If you want to get announcements about security updates on backports.debian.org subscribe to the [debian-backports-announce mailinglist](https://lists.debian.org/debian-backports-announce/).
##Report Bugs
Please report bugs that you found in the packages to the [backports mailinglist](http://lists.debian.org/debian-backports/) and **NOT** to the Debian BTS!
Please report bugs that you found in the packages to the [backports mailinglist](https://lists.debian.org/debian-backports/) and **NOT** to the Debian BTS!
We have the following mailinglists for debian-backports:
* [Debian Backports](http://lists.debian.org/debian-backports/) - For bugreporting and discussions about debian-backports
* [Debian Backports Announce](http://lists.debian.org/debian-backports-announce/) - (Security) Announces for backports.debian.org
* [Debian Backports Changes](http://lists.debian.org/debian-backports-changes/) - Messages from the backports queued and the Repository (DAK)
* [Debian Backports](https://lists.debian.org/debian-backports/) - For bugreporting and discussions about debian-backports
* [Debian Backports Announce](https://lists.debian.org/debian-backports-announce/) - (Security) Announces for backports.debian.org
* [Debian Backports Changes](https://lists.debian.org/debian-backports-changes/) - Messages from the backports queued and the Repository (DAK)
**Search for packages in debian-backports:**
<form method="GET" action="http://packages.debian.org/search">
<form method="GET" action="https://packages.debian.org/search">
Keyword: <input type="text" size="30" name="keywords" id="kw">
<input type="submit" value="search"> <input type="reset" value="reset"><br>
<input type="radio" name="searchon" value="names" checked="checked">Package names only <input type="radio" name="searchon" value="all">Descriptions
......@@ -26,4 +26,4 @@ Distribution:
</form>
----
Thanks to the [packages.debian.org](http://packages.debian.org) team for providing this service.
Thanks to the [packages.debian.org](https://packages.debian.org) team for providing this service.
......@@ -28,7 +28,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install openoffice.org" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions/>
[1] <https://backports.debian.org/Instructions/>
We recommend to pin the backports repository to 200 so that new
versions of installed backports will be installed automatically.
......
......@@ -119,7 +119,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin the backports repository to 200 so that new
versions of installed backports will be installed automatically.
......
......@@ -21,7 +21,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin the backports repository to 200 so that new
versions of installed backports will be installed automatically.
......
......@@ -22,7 +22,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin the backports repository to 200 so that new
versions of installed backports will be installed automatically.
......
......@@ -27,7 +27,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin the backports repository to 200 so that new
versions of installed backports will be installed automatically.
......
......@@ -53,7 +53,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin the backports repository to 200 so that new
versions of installed backports will be installed automatically.
......
......@@ -35,7 +35,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin the backports repository to 200 so that new
versions of installed backports will be installed automatically.
......
......@@ -19,7 +19,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin the backports repository to 200 so that new
versions of installed backports will be installed automatically.
......
......@@ -25,7 +25,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository
to 200 so that new versions of installed backports will be installed
......
......@@ -51,7 +51,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository
to 200 so that new versions of installed backports will be installed
......
......@@ -22,7 +22,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository
to 200 so that new versions of installed backports will be installed
......
......@@ -17,7 +17,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository to
200 so that new versions of installed backports will be installed
......
......@@ -107,7 +107,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository to
200 so that new versions of installed backports will be installed
......
......@@ -23,7 +23,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository to
200 so that new versions of installed backports will be installed
......
......@@ -14,7 +14,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository to
200 so that new versions of installed backports will be installed
......
......@@ -27,7 +27,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository to
200 so that new versions of installed backports will be installed
......
......@@ -7,14 +7,14 @@
httpd module for the Subversion server, when listing of repositories
(SVNListParentPath directive) is enabled. A remote user could use
this flaw to cause denial of service (particular httpd thread crash).
http://security-tracker.debian.org/tracker/CVE-2010-4539
https://security-tracker.debian.org/tracker/CVE-2010-4539
CVE-2010-4644
A server-side memory leak allows remote users to cause a denial
of service (memory consumption and daemon outage or crash) via
Subversion client "blame" or "log" operations, when the "-g" option
(request to display additional merge history) is used.
http://security-tracker.debian.org/tracker/CVE-2010-4644
https://security-tracker.debian.org/tracker/CVE-2010-4644
For the lenny-backports distribution, the problems have been fixed in
version 1.6.12dfsg-4~bpo50+1.
......@@ -28,7 +28,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository
to 200 so that new versions of installed backports will be installed
......
......@@ -77,7 +77,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository to
200 so that new versions of installed backports will be installed
......
......@@ -8,7 +8,7 @@
hashing method. If an attacker would have access to the password
database, he could decode the passwords stored in it.
http://security-tracker.debian.org/tracker/CVE-2011-0009
https://security-tracker.debian.org/tracker/CVE-2011-0009
For the lenny-backports distribution the problems have been fixed in
version 3.8.8-7~bpo50+1.
......@@ -22,7 +22,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin the backports repository to 200 so that new
versions of installed backports will be installed automatically.
......
......@@ -79,7 +79,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin the backports repository to 200 so that new
versions of installed backports will be installed automatically.
......
......@@ -22,7 +22,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin the backports repository to 200 so that new
versions of installed backports will be installed automatically.
......
......@@ -38,7 +38,7 @@
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository to
200 so that new versions of installed backports will be installed
......
......@@ -21,7 +21,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository
to 200 so that new versions of installed backports will be installed
......
......@@ -51,7 +51,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository
to 200 so that new versions of installed backports will be installed
......
......@@ -27,7 +27,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository to
200 so that new versions of installed backports will be installed
......
......@@ -20,7 +20,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository
to 200 so that new versions of installed backports will be installed
......
......@@ -20,7 +20,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository
to 200 so that new versions of installed backports will be installed
......
......@@ -25,7 +25,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository
to 200 so that new versions of installed backports will be installed
......
......@@ -9,20 +9,20 @@
request forgery attack. (External custom fields are disabled by
default.)
http://security-tracker.debian.org/tracker/CVE-2011-1685
https://security-tracker.debian.org/tracker/CVE-2011-1685
CVE-2011-1686
Multiple SQL injection attacks allow authenticated users to obtain
data from the database in an unauthorized way.
http://security-tracker.debian.org/tracker/CVE-2011-1686
https://security-tracker.debian.org/tracker/CVE-2011-1686
CVE-2011-1687
An information leak allows an authenticated privileged user to
obtain sensitive information, such as encrypted passwords, via the
search interface.
http://security-tracker.debian.org/tracker/CVE-2011-1687
https://security-tracker.debian.org/tracker/CVE-2011-1687
CVE-2011-1688
When running under certain web servers (such as Lighttpd), Request
......@@ -30,19 +30,19 @@
attackers to read any files accessible to the web server. Request
Tracker instances running under Apache or Nginx are not affected.
http://security-tracker.debian.org/tracker/CVE-2011-1688
https://security-tracker.debian.org/tracker/CVE-2011-1688
CVE-2011-1689
Request Tracker contains multiple cross-site scripting
vulnerabilities.
http://security-tracker.debian.org/tracker/CVE-2011-1689
https://security-tracker.debian.org/tracker/CVE-2011-1689
CVE-2011-1690
Request Tracker enables attackers to redirect authentication
credentials supplied by legitimate users to third-party servers.
http://security-tracker.debian.org/tracker/CVE-2011-1690
https://security-tracker.debian.org/tracker/CVE-2011-1690
For the lenny-backports distribution the problems have been fixed in
version 3.8.8-7+squeeze1~bpo50+1.
......@@ -60,20 +60,20 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
http://security-tracker.debian.org/tracker/CVE-2011-1688
[1] <https://backports.debian.org/Instructions>
https://security-tracker.debian.org/tracker/CVE-2011-1688
CVE-2011-1689
Request Tracker contains multiple cross-site scripting
vulnerabilities.
http://security-tracker.debian.org/tracker/CVE-2011-1689
https://security-tracker.debian.org/tracker/CVE-2011-1689
CVE-2011-1690
Request Tracker enables attackers to redirect authentication
credentials supplied by legitimate users to third-party servers.
http://security-tracker.debian.org/tracker/CVE-2011-1690
https://security-tracker.debian.org/tracker/CVE-2011-1690
For the lenny-backports distribution the problems have been fixed in
version 3.8.8-7+squeeze1~bpo50+1.
......@@ -91,7 +91,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin the backports repository to 200 so that new
versions of installed backports will be installed automatically.
......
......@@ -43,7 +43,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository
to 200 so that new versions of installed backports will be installed
......
......@@ -17,7 +17,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository
to 200 so that new versions of installed backports will be installed
......
......@@ -17,7 +17,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository to
200 so that new versions of installed backports will be installed
......
......@@ -29,7 +29,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository to
200 so that new versions of installed backports will be installed
......
......@@ -40,7 +40,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository
to 200 so that new versions of installed backports will be installed
......
......@@ -56,7 +56,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository to
200 so that new versions of installed backports will be installed
......
......@@ -19,7 +19,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository
to 200 so that new versions of installed backports will be installed
......
......@@ -14,7 +14,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository
to 200 so that new versions of installed backports will be installed
......
......@@ -22,7 +22,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository
to 200 so that new versions of installed backports will be installed
......
......@@ -31,7 +31,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository
to 200 so that new versions of installed backports will be installed
......
......@@ -51,7 +51,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository
to 200 so that new versions of installed backports will be installed
......
......@@ -19,7 +19,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository
to 200 so that new versions of installed backports will be installed
......
......@@ -35,7 +35,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository
to 200 so that new versions of installed backports will be installed
......
......@@ -28,7 +28,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository
to 200 so that new versions of installed backports will be installed
......
......@@ -27,7 +27,7 @@
If you don't use pinning (see [1]) you have to update the package
manually via "apt-get -t lenny-backports install <packagelist>" with
the packagelist of your installed packages affected by this update.
[1] <http://backports.debian.org/Instructions>
[1] <https://backports.debian.org/Instructions>
We recommend to pin (in /etc/apt/preferences) the backports repository
to 200 so that new versions of installed backports will be installed
......
......@@ -14,7 +14,7 @@
sources.list entry will be different, a simple substitute of squeeze
for wheezy won't work. The new format is:
deb http://ftp.debian.org/debian/ wheezy-backports main
deb https://ftp.debian.org/debian/ wheezy-backports main
So it is debian instead of debian-backports, and offered through the
regular mirror network. Feel invited to check your regular mirror if
......@@ -22,7 +22,7 @@
For squeeze nothing changed.
deb http://backports.debian.org/debian-backports/ squeeze-backports(-sloppy) main
deb https://backports.debian.org/debian-backports/ squeeze-backports(-sloppy) main
continues to work for the whole squeeze lifetime.
......
......@@ -3,9 +3,9 @@ After several years of slacking :) by everybody involved it finally happened: ba
We are happy to welcome a new ftpmaster, Gerfried Fuchs (rhonda) joined our team.
The website [1] and the mirror moved to <http://backports.debian.org/> and the archive is now available below *debian-backports/*. Even though we expect the old entries to continue to work for a while, you might still want to update your sources.list entry to:
The website [1] and the mirror moved to <https://backports.debian.org/> and the archive is now available below *debian-backports/*. Even though we expect the old entries to continue to work for a while, you might still want to update your sources.list entry to:
deb http://backports.debian.org/debian-backports lenny-backports main contrib non-free
deb https://backports.debian.org/debian-backports lenny-backports main contrib non-free
or one of the mirrors[2] that do carry the backports archive.
......@@ -33,17 +33,17 @@ the debian-backports ftpmasters (ftpmaster@backports.debian.org),
Jörg Jaspert.
[1] <http://backports.debian.org/>
[2] <http://backports-master.debian.org/Mirrors/>
[2] <http://backports.debian.org/Contribute/>
[3] <http://backports.debian.org/Instructions/>
[3] <http://www.debian.org/mirrors/ftpmirror>
[4] <http://www.debian.org/mirrors/submit>
[5] <http://ftp-master.debian.org/ftpsync.tar.gz>
[6] <http://ftp-master.debian.org/git/archvsync.git/>
[7] <http://lists.debian.org/debian-backports>
[8] <http://lists.debian.org/debian-backports-announce>
[9] <http://lists.debian.org/debian-backports-changes>
[1] <https://backports.debian.org/>
[2] <https://backports-master.debian.org/Mirrors/>
[2] <https://backports.debian.org/Contribute/>
[3] <https://backports.debian.org/Instructions/>
[3] <https://www.debian.org/mirrors/ftpmirror>
[4] <https://www.debian.org/mirrors/submit>
[5] <https://ftp-master.debian.org/ftpsync.tar.gz>
[6] <https://ftp-master.debian.org/git/archvsync.git/>
[7] <https://lists.debian.org/debian-backports>
[8] <https://lists.debian.org/debian-backports-announce>
[9] <https://lists.debian.org/debian-backports-changes>
[10] <http://www.ece.ubc.ca>
[11] <http://www.teamix.net>