Assuming no one else is already working on your prospective package, you must
then submit a bug report (<xref linkend="submit-bug"/>) against the
pseudo-package <systemitem role="package">wnpp</systemitem> describing your
-plan to create a new package, including, but not limiting yourself to, a
-description of the package, the license of the prospective package, and the
+plan to create a new package, including, but not limiting yourself to, the
+description of the package (so that others can review it),
+the license of the prospective package, and the
current URL where it can be downloaded from.
</para>
<para>
</listitem>
</itemizedlist>
<para>
-Please see <ulink url="http://&ftp-master-host;/REJECT-FAQ.html"></ulink>
+Please see <ulink url="https://&ftp-master-host;/REJECT-FAQ.html"></ulink>
for common rejection reasons for a new package.
</para>
</section>
<para>
An upload to the delayed directory keeps the package in
-<ulink url="http://ftp-master.debian.org/deferred.html">the deferred uploads queue</ulink>.
+<ulink url="https://ftp-master.debian.org/deferred.html">the deferred uploads queue</ulink>.
When the specified waiting time is over, the package is moved into
the regular incoming directory for processing.
This is done through automatic uploading to
url="&url-bts;">Debian bug tracking system (BTS)</ulink> for
your packages. The BTS contains all the open bugs against your packages. You
can check them by browsing this page:
-<literal>http://&bugs-host;/<replaceable>yourlogin</replaceable>@debian.org</literal>.
+<literal>https://&bugs-host;/<replaceable>yourlogin</replaceable>@debian.org</literal>.
</para>
<para>
Maintainers interact with the BTS via email addresses at
<title>The Security Tracker</title>
<para>
The security team maintains a central database, the
-<ulink url="http://security-tracker.debian.org/">Debian Security Tracker</ulink>.
+<ulink url="https://security-tracker.debian.org/">Debian Security Tracker</ulink>.
This contains all public information that is known about security issues:
which packages and versions are affected or fixed, and thus whether stable,
testing and/or unstable are vulnerable. Information that is still confidential
</para>
<para>
The Security Team has a PGP-key to enable encrypted communication about
-sensitive issues. See the <ulink url="http://www.debian.org/security/faq#contact">Security Team FAQ</ulink> for details.
+sensitive issues. See the <ulink url="https://www.debian.org/security/faq#contact">Security Team FAQ</ulink> for details.
</para>
</section>
<listitem>
<para>
References to upstream advisories, <ulink
-url="http://cve.mitre.org">CVE</ulink> identifiers, and any other information
+url="https://cve.mitre.org">CVE</ulink> identifiers, and any other information
useful in cross-referencing the vulnerability
</para>
</listitem>
If you want to remove a package you maintain, you should note this in
the bug title by prepending <literal>ROM</literal> (Request Of Maintainer).
There are several other standard acronyms used in the reasoning for a package
-removal, see <ulink url="http://&ftp-master-host;/removals.html"></ulink>
+removal, see <ulink url="https://&ftp-master-host;/removals.html"></ulink>
for a complete list. That page also provides a convenient overview of
pending removal requests.
</para>
</para>
<para>
Further information relating to these and other package removal related topics
-may be found at <ulink url="http://wiki.debian.org/ftpmaster_Removals"></ulink>
+may be found at <ulink url="https://wiki.debian.org/ftpmaster_Removals"></ulink>
and <ulink url="&url-debian-qa;howto-remove.html"></ulink>.
</para>
<para>
You should check why the package was removed in the first place. This
information can be found in the removal item in the news section of the PTS
page for the package or by browsing the log of
-<ulink url="http://&ftp-master-host;/#removed">removals</ulink>.
+<ulink url="https://&ftp-master-host;/#removed">removals</ulink>.
The removal bug will tell you why the package was removed and will give some
indication of what you will need to work on in order to reintroduce the package.
It may indicate that the best way forward is to switch to some other piece of
</para>
<para>
Some further dependency analysis is shown on <ulink
-url="http://release.debian.org/migration/"></ulink> — but be warned, this page also
+url="https://release.debian.org/migration/"></ulink> — but be warned, this page also
shows build dependencies which are not considered by britney.
</para>
<section id="outdated">
</para>
<para>
If you want to see more details, you can look it up on <ulink
-url="http://&ftp-master-host;/testing/update_output/"></ulink>.
+url="https://&ftp-master-host;/testing/update_output/"></ulink>.
</para>
<para>
The hints are available via <ulink
-url="http://&ftp-master-host;/testing/hints/"></ulink>, where you can find
+url="https://&ftp-master-host;/testing/hints/"></ulink>, where you can find
the
-<ulink url="http://&ftp-master-host;/testing/hints/README">description</ulink>
+<ulink url="https://&ftp-master-host;/testing/hints/README">description</ulink>
as well. With the hints, the Debian Release team can block or unblock
packages, ease or force packages into <literal>testing</literal>, remove
packages from <literal>testing</literal>, approve uploads to
~ianmdlvl / developers-reference.git / blobdiff