From 6ae4e1ddb4354f75e21a44882ee9d3c041634e79 Mon Sep 17 00:00:00 2001 From: Adam Williamson Date: Sep 15 2023 14:52:13 +0000 Subject: Clean up after 36bbc39 renames, fix 404s on bugzilla-file-a-bug 36bbc39 renamed some pages but did not update the references to them, and did not uncomment the page-aliases line for the 'how to file a bug' page, so attempting to access it by its old name (either from an external link or from the table of contents) ended in a 404. This should fix everything up, tested locally. Signed-off-by: Adam Williamson --- diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index 9950f68..a663e35 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -3,7 +3,7 @@ * xref:getting-started-guide.adoc[Getting started with Fedora] * xref:bugzilla/index.adoc[Bugs] -** xref:howto-file-a-bug.adoc[How to file a bug] +** xref:bugzilla-file-a-bug.adoc[How to file a bug] ** xref:bugzilla/query.adoc[Bugzilla queries] ** xref:bugzilla/find-duplicates.adoc[Finding duplicate bugs] ** xref:bugzilla/correct-component.adoc[Finding the correct component] @@ -61,7 +61,7 @@ ** xref:grub2-bootloader.adoc[The GRUB2 Bootloader] ** xref:samba.adoc[How to create a Samba share] ** xref:join-active-directory-freeipa.adoc[How to join an Active Directory or FreeIPA domain] -** xref:how-to-set-nvidia-as-primary-gpu-on-optimus-based-laptops.adoc[How to Set NVIDIA as Primary GPU on Optimus-based Laptops] +** xref:set-nvidia-as-primary-gpu-on-optimus-based-laptops.adoc[How to Set NVIDIA as Primary GPU on Optimus-based Laptops] ** xref:debug-systemd-problems.adoc[How to debug systemd problems] ** xref:enable-touchpad-click.adoc[How to enable touchpad click] ** xref:installing-and-running-vlc.adoc[Installing and running the VLC player] diff --git a/modules/ROOT/pages/bugzilla-file-a-bug.adoc b/modules/ROOT/pages/bugzilla-file-a-bug.adoc index efb0335..14a2c3e 100644 --- a/modules/ROOT/pages/bugzilla-file-a-bug.adoc +++ b/modules/ROOT/pages/bugzilla-file-a-bug.adoc @@ -4,7 +4,7 @@ Ankur Sinha; Joe Walker :revdate: 2023-05-15 :category: Bugs :tags: How-to, Bug-Report -//:page-aliases: howto-file-a-bug.adoc +:page-aliases: howto-file-a-bug.adoc //:imagesdir: ./images include::partial$attributes.adoc[] diff --git a/modules/ROOT/pages/virtualization-howto-debug-issues.adoc b/modules/ROOT/pages/virtualization-howto-debug-issues.adoc index c78a97d..db95e3d 100644 --- a/modules/ROOT/pages/virtualization-howto-debug-issues.adoc +++ b/modules/ROOT/pages/virtualization-howto-debug-issues.adoc @@ -23,7 +23,7 @@ Reporting bugs effectively is an important skill for any Fedora user or develope Narrowing down the possible causes of the bug and providing the right information in the bug report allows a bug to be resolved quickly. Filing a bug report with little useful information can mean that your bug lays unresolved, possibly until it is closed automatically when the distribution version reaches "end of life". -See xref:howto-file-a-bug.adoc[how to file a bug report] for generic information on filing bugs. This page contains information specific to virtualization bugs. +See xref:bugzilla-file-a-bug.adoc[how to file a bug report] for generic information on filing bugs. This page contains information specific to virtualization bugs. // Note: if you're filing a virtualization related bug against a package which isn't on [[Virtualization#Relevant_Packages|this list]], then please cc the [mailto:fedora-virt-maint@redhat.com fedora-virt-maint@redhat.com] alias in bugzilla to ensure virt developers see the bug.