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#18859 - [pacman-contrib] paclist does not print packages correctly
Attached to Project:
Community Packages
Opened by Robert (theapodan) - Saturday, 27 March 2010, 16:34 GMT
Last edited by Allan McRae (Allan) - Sunday, 28 March 2010, 09:25 GMT
Opened by Robert (theapodan) - Saturday, 27 March 2010, 16:34 GMT
Last edited by Allan McRae (Allan) - Sunday, 28 March 2010, 09:25 GMT
|
DetailsDescription:
paclist does not print packages for which the installed version and sync version differ when printing the list of packages in the core repo using: 'paclist core' Steps to reproduce: example: installed binutils is 2.20-3 sync binutils is 2.20.1-1 'paclist core' output is: bash 4.1.002-2 bin86 0.16.17-4 bison 2.4.1-1 This patch seems to work for me, but I don't know if it is the best way: 48c48 < $output = `pacman -Sl $ARGV[0]`; --- > $output = `pacman -Sl $ARGV[0] | cut --delimiter=' ' -f 2`; 54c54 < # testing foobar 1.0-1 --- > # foobar 56,59c56 < my @info = split(/ /); < # we only want to store 'foobar 1.0-1' in our hash table < my $pkg = $info[1] . " " . $info[2]; < $packages{$pkg}++; --- > $packages{$_}++; 62c59 < $output = `pacman -Q`; --- > $output = `pacman -Q | cut --delimiter=' ' -f 1`; 67c64 < # foobar 1.0-1 --- > # foobar 70d66 < # store 'foobar 1.0-1' in our hash table |
This task depends upon
Closed by Allan McRae (Allan)
Sunday, 28 March 2010, 09:25 GMT
Reason for closing: Not a bug
Additional comments about closing: See comment
Sunday, 28 March 2010, 09:25 GMT
Reason for closing: Not a bug
Additional comments about closing: See comment
Comment by Allan McRae (Allan) -
Saturday, 27 March 2010, 18:27 GMT
That is by design. A different version number means that you do not have the package from the repo installed anymore. Just an old version. That also means that packages installed from [testing] will only show in the list for [testing] and not e.g. [core].