Merge pull request #240 from s-makin/housekeeping

Update broken and redirecting links

Author: s-makin

docs/contributors/advanced/resolve-a-migration-issue.md

@@ -177,7 +177,7 @@ release=<RELEASE>&arch=<ARCH>&package=<SRCPKG>&trigger=<SRCPKG>/<VERSION>&ppa=<L
 You must have upload rights for the package (`<SRCPKG>` above) for the test request to be successful.
 :::
 
-The test is then displayed at [autopkgtest.ubuntu.com/running](http://autopkgtest.ubuntu.com/running). Upon completion, the test result is available at an index page at `https://autopkgtest.ubuntu.com/results/autopkgtest-<RELEASE>-<LPUSER>-<PPA>/?format=plain`. The index contains the results for each autopkgtest run against this particular `<PPA>` for this `<RELEASE>`. To see a particular test, append the appropriate path from the index to
+The test is then displayed at [`autopkgtest.ubuntu.com/running`](https://autopkgtest.ubuntu.com/running). Upon completion, the test result is available at an index page at `https://autopkgtest.ubuntu.com/results/autopkgtest-<RELEASE>-<LPUSER>-<PPA>/?format=plain`. The index contains the results for each autopkgtest run against this particular `<PPA>` for this `<RELEASE>`. To see a particular test, append the appropriate path from the index to
 
 ```none
 https://autopkgtest.ubuntu.com/results/autopkgtest-<RELEASE>-<LPUSER>-<PPA>/

docs/contributors/bug-fix/bug-fixing-checklist.md

@@ -136,7 +136,7 @@ to the version you need before getting the tarball.
 
 - [ ] {ref}`mir-reporters-template`
 
-- [ ] [FFe](https://wiki.ubuntu.com/FreezeExceptionProcess#FeatureFreeze_Exceptions):
+- [ ] {ref}`FFe <feature-freeze-exceptions>`:
 
   ```
   [[ Feature Freeze Exception ]]

docs/contributors/bug-fix/fix-a-bug-in-a-package.md

@@ -26,11 +26,12 @@ It is strongly recommended that you read the following resources before you
 continue, to make sure you are familiar with the concepts:
 
 * [git-ubuntu-clone](https://ubuntu.com/blog/git-ubuntu-clone)
-* [DEP-3](http://dep.debian.net/deps/dep3)
+* [DEP-3](https://dep-team.pages.debian.net/deps/dep3/)
 * {ref}`version-strings`
 * [Stable Release Updates (SRUs)](https://documentation.ubuntu.com/sru/en/latest/)
 
 
+(evaluate-the-bug)=
 ## Evaluate the Bug
 
 Let's look at an example:
@@ -241,7 +242,7 @@ versions for each distribution version will be under `pkg/ubuntu/version`.
 
 Notes:
 
-* Due to [this bug](https://launchpad.net/bugs/1761821), you may get:
+* Due to {lpbug}`this bug <1761821>`, you may get:
   `fatal: could not read Username for 'https://git.launchpad.net': terminal prompts disabled.` 
   It's safe to ignore this.
  * The first time you run this command, a git-ubuntu entry will be added to
@@ -380,8 +381,8 @@ CommitDate: Mon Jun 26 10:18:26 2017 +0100
 Our issue would be the same as Debian bug #865770.
 
 It's also possible to search for commits via Debian's web front-end for git,
-[Salsa](https://salsa.debian.org). Doing so in this case would bring you to
-[this commit](https://salsa.debian.org/ssh-team/openssh/commit/d4181e15b03171d1363cd9d7a50b209697a80b01)
+[Salsa](https://salsa.debian.org/public). Doing so in this case would bring you to
+[this commit](https://salsa.debian.org/ssh-team/openssh/-/commit/d4181e15b03171d1363cd9d7a50b209697a80b01)
 
 Either way, you should also mention the Salsa link in the fixed-up bug report,
 and you should also include it in your fix commit message.

docs/contributors/bug-fix/propose-changes.rst

@@ -28,20 +28,16 @@ Once you find a bug report on Launchpad that you want to work on, evaluate the b
 
 Read the bug description carefully and look for:
 
-.. TODO link UMH
-
 - steps to reproduce the problem
 - crash logs or terminal output
 - details about the affected version and package
-- attached ``.crash`` files or `Apport crash files <https://github.com/canonical/ubuntu-maintainers-handbook/blob/main/PackageFixing.md#evaluate-the-bug>`_
+- attached ``.crash`` files or :ref:`Apport crash files <evaluate-the-bug>`
 
 For example, the `Postconf segfaults every 5 minutes <https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1753470>`_ bug report shows a segmentation fault in ``postconf`` on Ubuntu 18.04. It includes logs from ``/var/log/kern.log``, shell commands that reproduce the issue, and metadata about the system environment. This information helps confirm whether the bug still affects current versions and if the report is complete.
 
 If the bug includes a ``.crash`` file, extract and inspect the stack trace. Use the information to better understand where the failure occurred in the code.
 
-.. TODO link UMH
-
-For more details, see `Evaluate the bug <https://github.com/canonical/ubuntu-maintainers-handbook/blob/main/PackageFixing.md#evaluate-the-bug>`_.
+For more details, see :ref:`Evaluate the bug <evaluate-the-bug>`.
 
 Identify the source package
 ---------------------------
@@ -226,7 +222,7 @@ You can also use PPA-based method whenever possible. It produces results closest
 
 .. TODO UMH link
 
-To learn how to set up and run these test methods, see `Running package tests <https://github.com/canonical/ubuntu-maintainers-handbook/blob/main/PackageTests.md>`_.
+To learn how to set up and run these test methods, see :ref:`Running package tests <how-to-run-package-tests>`.
 
 
 .. _submitting-the-fix:
@@ -240,9 +236,7 @@ Once you've documented and saved your changes in a new changelog entry, run ``de
 
     debuild -S -d
 
-.. TODO UMH link
-
-The command signs the changes in the file. After that, submit your fix by opening a merge proposal. For details on how to do this, see the section on `Merge proposal <https://github.com/canonical/ubuntu-maintainers-handbook/blob/main/MergeProposal.md>`_ in the Ubuntu Maintainer's Handbook.
+The command signs the changes in the file. After that, submit your fix by opening a merge proposal. For details on how to do this, see the section on :ref:`Merge proposal <how-to-submit-a-merge-proposal>`.
 
 In many cases, Debian would benefit from the fix as well. Submitting to Debian is considered best practice because it ensures that a wider audience receives the fix. You can submit the fix to Debian by running:
 

docs/contributors/bug-triage/bug-responses.md

@@ -4,7 +4,7 @@
 It is common when triaging bugs that you need to respond to the original reporter -- perhaps to request more information, or to redirect their request, etc.
 Over time, a set of curated standard responses has been created, and you can use these when you correspond with the reporter.
 
-These standard responses (and other amazing scripts) are available as a FireFox extension [in a PPA](https://launchpad.net/~gm-dev-launchpad/+archive/ppa).
+These standard responses (and other amazing scripts) are available as a FireFox extension [in a PPA](https://launchpad.net/~gm-dev-launchpad/+archive/ubuntu/ppa).
 
 When you update one of these responses, you should also update the response used by the Firefox extension.
 These responses can be found in the bazaar branch [lp:ubuntu-bugcontrol-tools](https://code.launchpad.net/ubuntu-bugcontrol-tools) in the `gm-xml-files/bugsquad-replies.xml` file.
@@ -796,7 +796,7 @@ Please seek support and bug reporting solutions from your distribution. Thank yo
 
 Other projects have standard responses as well:
 
-* [GNOME](http://live.gnome.org/Bugsquad/TriageGuide/StockResponses)  
+* [GNOME](https://wiki.gnome.org/Bugsquad/TriageGuide/StockResponses)  
 * [Mozilla Team](https://wiki.ubuntu.com/MozillaTeam/Bugs/Triage/Responses)
 
 

docs/contributors/bug-triage/bug-tags.md

@@ -37,7 +37,7 @@ Here we outline some standard tags with information about when to use them while
 | [`likely-dup`](https://launchpad.net/ubuntu/+bugs?field.tag=likely-dup) | The bug is likely a duplicate of another bug (maybe an upstream bug) but you can't find it |
 | [`manpage`](https://launchpad.net/ubuntu/+bugs?field.tag=manpage) | This bug is about a package's manual page being incorrect |
 | [`metabug`](https://launchpad.net/ubuntu/+bugs?field.tag=metabug) | This bug has a high probability of duplicate reports being filed |
-| [`multiarch`](https://launchpad.net/ubuntu/+bugs?field.tag=multiarch) | This bug is due to an issue with [multiarch triplet paths](http://wiki.debian.org/Multiarch); this could be build time, install time, or run time issues |
+| [`multiarch`](https://launchpad.net/ubuntu/+bugs?field.tag=multiarch) | This bug is due to an issue with [multiarch triplet paths](https://wiki.debian.org/Multiarch); this could be build time, install time, or run time issues |
 | [`nautilus-desktop-icons`](https://launchpad.net/ubuntu/+bugs?field.tag=nautilus-desktop-icons) | Bugs related to the Nautilus desktop; especially the alignment, display, and grid of icons |
 | [`needs-devrelease-testing`](https://launchpad.net/ubuntu/+bugs?orderby=-importance&field.status%3Alist=New&field.status%3Alist=Incomplete&field.status%3Alist=Invalid&field.status%3Alist=Won%27t+Fix&field.status%3Alist=Confirmed&field.status%3Alist=Triaged&field.status%3Alist=In+Progress&field.status%3Alist=Fix+Committed&field.status%3Alist=Fix+Released&field.tag=needs-devrelease-testing&search=Search) | A bug that existed in a previous release of Ubuntu and needs to be tested in the latest development release |
 | [`needs-reassignment`](https://launchpad.net/ubuntu/+bugs?field.tag=needs-reassignment) | A bug reported about the wrong package but the package maintainer isn't sure which package it belongs to |
@@ -93,10 +93,10 @@ Specific bugs concerning parts of the [Ayatana project](https://launchpad.net/ay
 
 | Tag | Use case |
 | :---- | :---- |
-| [`app-menu`](https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=app-menu) | Bugs related to the [App Menu](https://wiki.ubuntu.com/DesktopExperienceTeam/ApplicationMenu) |
-| [`indicator-applet`](https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=indicator-applet) | Bugs related to the use of the Indicator Applet that are not in the `indicator-applet` package (no Application Indicators) |
-| [`indicator-application`](https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=indicator-application) | Bugs related to the use of Indicator Application that are not in the `indicator-application` package |
-| [`trayaway`](https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=trayaway) | Bugs related to the [Notification Area transition](https://wiki.ubuntu.com/NotificationAreaTransition) |
+| [`app-menu`](https://bugs.launchpad.net/ubuntu/+bugs?field.tag=app-menu) | Bugs related to the [App Menu](https://wiki.ubuntu.com/DesktopExperienceTeam/ApplicationMenu) |
+| [`indicator-applet`](https://bugs.launchpad.net/ubuntu/+bugs?field.tag=indicator-applet) | Bugs related to the use of the Indicator Applet that are not in the `indicator-applet` package (no Application Indicators) |
+| [`indicator-application`](https://bugs.launchpad.net/ubuntu/+bugs?field.tag=indicator-application) | Bugs related to the use of Indicator Application that are not in the `indicator-application` package |
+| [`trayaway`](https://bugs.launchpad.net/ubuntu/+bugs?field.tag=trayaway) | Bugs related to the [Notification Area transition](https://wiki.ubuntu.com/NotificationAreaTransition) |
 
 
 ### Hardware-specific
@@ -211,7 +211,8 @@ See the [regression tracker](http://qa.ubuntu.com/reports/regression/regression_
 
 | Tag | Use case |
 | :---- | :---- |
-| [`update-excuse`](https://launchpad.net/ubuntu/+bugs?field.tag=update-excuse) | A bug tracking a cause of a package not being migrated to the `-release` pocket (this tag causes the bug to appear on the [update excuses report](https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html)) |
+| [`update-excuse`](https://launchpad.net/ubuntu/+bugs?field.tag=update-excuse) | A bug tracking a cause of a package not being migrated to the `-release` pocket (this tag causes the bug to appear on the [update excuses report](https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses.html
+)) |
 | [`block-proposed`](https://launchpad.net/ubuntu/+bugs?field.tag=block-proposed) | A bug that should be held back from migrating into the `-release` pocket |
 
 

docs/contributors/bug-triage/bug-types.md

@@ -74,7 +74,7 @@ If the bug report is actually a feature request, there are two possibilities.
    *Triaged*. Only the members of the
    [Ubuntu Bug Control](https://launchpad.net/~ubuntu-bugcontrol) team can do
    so. If you're not a member you need to ask someone who is to do it for you.
-   Paste the bug number in the `#ubuntu-devel` Matrix channel and say you think
+   Paste the bug number in the {matrix}`ubuntu-devel` Matrix channel and say you think
    the bug should be set to *Wishlist*. Someone will notice and set it for you,
    although not necessarily immediately.
 
@@ -187,13 +187,13 @@ used to track software requested for inclusion in Ubuntu. For these bugs:
 
 * Read and follow the instructions on [Sponsor Queue](https://wiki.ubuntu.com/MOTU/Sponsorship/SponsorsQueue).
 
-* Check if it is already in Ubuntu via [`packages.ubuntu.com`](http://packages.ubuntu.com),
+* Check if it is already in Ubuntu via [`packages.ubuntu.com`](https://packages.ubuntu.com/),
   or by running `rmadison <package>`.
 
   * If it **is** in the Archive, mark it as *Invalid*, and add a comment
     explaining your action.
 
-  * If it **is not** in Ubuntu, then check Debian via [`packages.debian.org`](http://packages.debian.org),
+  * If it **is not** in Ubuntu, then check Debian via [`packages.debian.org`](https://www.debian.org/distrib/packages),
     or by running `rmadison -u debian <package>`.
 
     * If it is in Debian, mark it as *Invalid*, and add a comment stating:
@@ -204,8 +204,8 @@ used to track software requested for inclusion in Ubuntu. For these bugs:
       likely appear in the next Ubuntu release.
       ```
 
-* Next, check [the Debian bug tracker](http://bugs.debian.org) or
-  [Work-Needing and Prospective Packages](http://www.debian.org/devel/wnpp/)
+* Next, check [the Debian bug tracker](https://www.debian.org/Bugs/) or
+  [Work-Needing and Prospective Packages](https://www.debian.org/devel/wnpp/)
   for an Intent To Package (ITP) or Request For Package (RFP) for this package.
   If you find such a request, add an upstream bug watch for it, and continue on.