[website/master] Use https://.
---
NEW-checklist.html | 2 +-
REJECT-FAQ.html | 12 ++++++------
index.html | 6 +++---
reject.html | 2 +-
unmet-deps/index.html | 2 +-
5 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/NEW-checklist.html b/NEW-checklist.html
index ddb1791..8db4d5f 100644
--- a/NEW-checklist.html
+++ b/NEW-checklist.html
@@ -169,7 +169,7 @@
<li>Does copyright file mention every license for every file in the
source code?</li>
<li>Does it comply with
- <a href="http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/";>
+ <a href="https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/";>
machine readable copyright file</a>, if applicable?</li>
</ul>
</li>
diff --git a/REJECT-FAQ.html b/REJECT-FAQ.html
index e205608..c20d958 100644
--- a/REJECT-FAQ.html
+++ b/REJECT-FAQ.html
@@ -104,7 +104,7 @@
<td>
You have a cdbs package and for whatever reason turned on the
<i>play with my debian/control in a bad way</i> option. See
- <a href="http://bugs.debian.org/311724";>#311724</a> for a long text
+ <a href="https://bugs.debian.org/311724";>#311724</a> for a long text
on that matter.<br />
Small overview: The <i>DEB_AUTO_UPDATE_DEBIAN_CONTROL</i> option
turned on modifies Build-Depends, which doesn't affect the build
@@ -226,7 +226,7 @@
<td>FTBFSIASW</td>
<td>Your package <b>fails to build from source in a sane way</b>. A
- good example is behind <a href="http://bugs.debian.org/300683";>#300683</a>,
+ good example is behind <a href="https://bugs.debian.org/300683";>#300683</a>,
but I can think of more creative ways to do it. Basically you need be able
to build all .debs with only one call to debian/rules. Not two, not three.
Not an extra script.<br />
@@ -247,7 +247,7 @@
source). This mostly happens to kernel-module packages.<br />
In Debian Policy we have
- <a href="http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-sourcecontrolfiles";>
+ <a href="https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-sourcecontrolfiles";>
Section 5.2 (Source package control files -- debian/control)</a>
which says
@@ -482,8 +482,8 @@
with a compressed tarball embedded as a binary blob, where
it is not obvious how to get the actual source. As that's not
considered to be the prefered form of modification, it fails
- the DFSG. See <a href="http://bugs.debian.org/645190";>#645190</a> and
- <a href="https://wiki.debian.org/UnpackWaf";>http://wiki.debian.org/UnpackWaf</a>
+ the DFSG. See <a href="https://bugs.debian.org/645190";>#645190</a> and
+ <a href="https://wiki.debian.org/UnpackWaf";>https://wiki.debian.org/UnpackWaf</a>
for details.</td>
<td>January 2012</td>
</tr>
@@ -579,7 +579,7 @@
<td>Write manpages. Yes. Really. Write them. Well. It's basically: If
your program/tool has a --help and --version commandline option you
can simply run
- <a href="http://packages.debian.org/help2man";>help2man</a> and have a working
+ <a href="https://packages.debian.org/help2man";>help2man</a> and have a working
start. Such easy ones are near to a reject. Yes, there are things in
the archive where it's hard to write manpages.</td>
diff --git a/index.html b/index.html
index 7a1353c..dfd2a4e 100644
--- a/index.html
+++ b/index.html
@@ -100,7 +100,7 @@
</ul>
<p>This information (and more like it) is available from
- <a href="http://www.debian.org/intro/organization";>Debian's Organizational Structure</a>.</p>
+ <a href="https://www.debian.org/intro/organization";>Debian's Organizational Structure</a>.</p>
<p>The FTP Master role, unix group <tt>debadmin</tt>, is responsible for:</p>
<ul>
@@ -201,7 +201,7 @@
<h1>Pending removals</h1>
<p>Packages which are scheduled to be removed from Debian
are <a href="removals.html">shown here</a> and also on the
- <a href="http://bugs.debian.org/ftp.debian.org";>ftp bug page</a>.
+ <a href="https://bugs.debian.org/ftp.debian.org";>ftp bug page</a>.
</p>
</div>
@@ -351,7 +351,7 @@
<div id="contact">
<h1>Contact</h1>
<p>Email contact: ftpmaster@debian.org</p>
- <p>Request tracker: <a href="http://bugs.debian.org/ftp.debian.org";>http://bugs.debian.org/ftp.debian.org (pseudo package)</a></p>
+ <p>Request tracker: <a href="https://bugs.debian.org/ftp.debian.org";>https://bugs.debian.org/ftp.debian.org (pseudo package)</a></p>
<p>Public IRC channel: #debian-ftp on irc.debian.org (OFTC)</p>
</div>
diff --git a/reject.html b/reject.html
index 489f07e..a022a81 100644
--- a/reject.html
+++ b/reject.html
@@ -96,7 +96,7 @@ Rejected: Unknown distribution `woody'.
<dd>Specify a valid distribution/suite and reupload.</dd>
<dt>Notes</dt>
- <dd>Valid target suites are: 'stable', 'unstable' and 'experimental'. You can't upload to 'testing' as it's controlled by it's own scripts and does not accept direct uploads. If your package is not updating in testing, check the <a href="http://ftp-master.debian.org/testing/index.html";>testing pages</a> to see why. You can't upload to 'proposed-updates' directly, instead, upload to 'stable' and your package will be redirected to 'proposed-updates' automatically. Suite/distribution aliases (e.g. 'woody', 'potato') are not supported due to potential problems with their meaning changing between the time the source upload is done and the package is recompiled for some architecture.</dd>
+ <dd>Valid target suites are: 'stable', 'unstable' and 'experimental'. You can't upload to 'testing' as it's controlled by it's own scripts and does not accept direct uploads. If your package is not updating in testing, check the <a href="https://ftp-master.debian.org/testing/index.html";>testing pages</a> to see why. You can't upload to 'proposed-updates' directly, instead, upload to 'stable' and your package will be redirected to 'proposed-updates' automatically. Suite/distribution aliases (e.g. 'woody', 'potato') are not supported due to potential problems with their meaning changing between the time the source upload is done and the package is recompiled for some architecture.</dd>
</dl>
diff --git a/unmet-deps/index.html b/unmet-deps/index.html
index 90a3f8a..a640042 100644
--- a/unmet-deps/index.html
+++ b/unmet-deps/index.html
@@ -5,7 +5,7 @@
<body>
<h1>Historic</h1>
The information on this page is fairly outdated. Depending on what you
- have been looking for, you might consult <a href="http://qa.debian.org/debcheck.php";>QA debcheck</a>.
+ have been looking for, you might consult <a href="https://qa.debian.org/debcheck.php";>QA debcheck</a>.
<h1>Unmet/illegal dependencies</h1>
The following are reports of unmet and/or illegal dependencies within the
--
1.7.10.4
Reply to: