Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#35134 - Wrong bug report mentioned in pacman 4.1 news
Attached to Project:
Pacman
Opened by Karol Błażewicz (karol) - Tuesday, 07 May 2013, 15:27 GMT
Last edited by Allan McRae (Allan) - Wednesday, 29 May 2013, 04:37 GMT
Opened by Karol Błażewicz (karol) - Tuesday, 07 May 2013, 15:27 GMT
Last edited by Allan McRae (Allan) - Wednesday, 29 May 2013, 04:37 GMT
|
Details https://projects.archlinux.org/pacman.git/tree/NEWS#n32
display repo in VerbosePkgLists output (FS#26334) https://bugs.archlinux.org/task/26334 talks about something else. Bug report number is IMHO wrong, but I don't know which one should it be. VerbosePkgLists shows repo for some time, but it used to show it in a different way https://bugs.archlinux.org/task/13364 I have reported this to the ML a couple days ago: https://mailman.archlinux.org/pipermail/arch-general/2013-May/033467.html News have since been updated for pacman 4.1.1 but the issue I reported has not been fixed. |
This task depends upon
Closed by Allan McRae (Allan)
Wednesday, 29 May 2013, 04:37 GMT
Reason for closing: Fixed
Additional comments about closing: git commit 8335e169
Wednesday, 29 May 2013, 04:37 GMT
Reason for closing: Fixed
Additional comments about closing: git commit 8335e169
No idea what the correct bug is so just removing it...
(BTW, arch-general is never a place to report bugs, especially for pacman.)