FS#12866 - Pacman -Qu bug

Attached to Project: Pacman
Opened by Henrik Enblom (Novus) - Tuesday, 20 January 2009, 11:07 GMT
Last edited by Dan McGee (toofishes) - Tuesday, 19 May 2009, 12:29 GMT
Task Type Bug Report
Category Output
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version 3.2.2
Due in Version 3.3.0
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

When running packman -Qu it sais, in the end

Total Download Size: 0.00 MB
Total Installed Size: 725.92 MB

when running pacman -Su it tells me the actuall download size

Total Download Size: 248.30 MB
Total Installed Size: 725.92 MB

pacman.conf is the default except ShowSize and TotalDownload is enabled


My architecture is x86_64 but Im gonna guess i686 users also will be able to reproduce this.
This task depends upon

Closed by  Dan McGee (toofishes)
Tuesday, 19 May 2009, 12:29 GMT
Reason for closing:  Fixed
Additional comments about closing:  Commit 882bff36acad5c47df5b35fd3afb411dc4f092b0
Comment by Xavier (shining) - Tuesday, 20 January 2009, 13:23 GMT
I think this bug is invalid in 3.3 where pacman -Qu simply prints the outdated packages.
Example :
$ pacman -Qu
msmtp 1.4.16-2
Comment by Dan McGee (toofishes) - Tuesday, 20 January 2009, 13:43 GMT
Yeah, that is correct, although we still have the problem where warnings about ignores are printed in the -Qu output.
Comment by Dan McGee (toofishes) - Wednesday, 15 April 2009, 04:22 GMT
Do we want to address the warnings issue before closing this out, or is that not happening anymore?
Comment by Nagy Gabor (combo) - Wednesday, 15 April 2009, 12:04 GMT
It is still happening. But my proposed "Remove find_replacements()" patch fixes that issue: http://www.archlinux.org/pipermail/pacman-dev/2009-April/008574.html

I requested closure because Novus' problem is not a bug any more. But I see now, that we use this bug report to indicate "-Qu warning" issue. ;-)
Comment by Dan McGee (toofishes) - Tuesday, 28 April 2009, 00:04 GMT
Do not close my bugs, especially without reading the comments. We still have an issue with -Qu and warnings output here that needs to be resolved. Just because there is a request for closure does not mean it is valid; I'm sorry I didn't reject it.
Comment by Nagy Gabor (combo) - Tuesday, 19 May 2009, 12:20 GMT
Dan, after commit 882bff36acad5c47df5b35fd3afb411dc4f092b0, we can finally close this bug imho. ;-)

Loading...