<para>
Make sure the bug is not already filed against a package. Each package has a
bug list easily reachable at
-<literal>http://&bugs-host;/<replaceable>packagename</replaceable></literal>.
+<literal>https://&bugs-host;/<replaceable>packagename</replaceable></literal>.
Utilities like <citerefentry> <refentrytitle>querybts</refentrytitle>
<manvolnum>1</manvolnum> </citerefentry> can also provide you with this
information (and <command>reportbug</command> will usually invoke
reports that you submitted. Take this opportunity to close those that you
can't reproduce anymore. To find out all the bugs you submitted, you just have
to visit
-<literal>http://&bugs-host;/from:<replaceable>your-email-addr</replaceable></literal>.
+<literal>https://&bugs-host;/from:<replaceable>your-email-addr</replaceable></literal>.
</para>
<section id="submit-many-bugs">
<title>Reporting lots of bugs at once (mass bug filing)</title>
</para>
<para>
To view bugs tagged with a specific usertag, visit
-<literal>http://&bugs-host;/cgi-bin/pkgreport.cgi?users=<replaceable>email-addr</replaceable>&tag=<replaceable>tag-name</replaceable></literal>.
+<literal>https://&bugs-host;/cgi-bin/pkgreport.cgi?users=<replaceable>email-addr</replaceable>&tag=<replaceable>tag-name</replaceable></literal>.
</para>
</section>
</section>
<footnote>
<para>
You can find more checks in the wiki where several developers share their own
-<ulink url="http://wiki.debian.org/SponsorChecklist">sponsorship checklists</ulink>.
+<ulink url="https://wiki.debian.org/SponsorChecklist">sponsorship checklists</ulink>.
</para>
</footnote>
</para>