Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#79935 - [pacman] Broken pacman documentation website links
Attached to Project:
Arch Linux
Opened by Marek Temnyak (temnyak.marek) - Thursday, 12 October 2023, 18:46 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:22 GMT
Opened by Marek Temnyak (temnyak.marek) - Thursday, 12 October 2023, 18:46 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:22 GMT
|
DetailsDescription:
Links to libalpm(3) are broken on https://archlinux.org/pacman/ and https://archlinux.org/pacman/pacman.8.html websites. They lead to https://archlinux.org/pacman/libalpm.3.html which is a 404. I believe they should lead to https://man.archlinux.org/man/libalpm.3.html. |
This task depends upon
Closed by Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:22 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/pacman/issues/5
Saturday, 25 November 2023, 20:22 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/pacman/issues/5
Comment by Jelle van der Waa (jelly) -
Friday, 13 October 2023, 08:19 GMT
I don't believe it should. Neither should this be hosted under archweb, this is a manual deployed website which is very suboptimal and requires building pacman. This has to become a Gitlab action in the pacman project on release publishing it as a Gitlab page.