Pacman

Welcome to the Pacman bug tracker. Please search the current bugs and feature requests before filing a new one! Use advanced search and select "Search in Comments".

* Please select the correct category and version.
* Write a descriptive summary, background info, and provide a reproducible test case whenever possible.
Tasklist

FS#72500 - Total package download percentage more than 100%

Attached to Project: Pacman
Opened by Christian Cornelssen (ccorn) - Thursday, 21 October 2021, 13:10 GMT
Task Type Bug Report
Category General
Status Unconfirmed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 6.0.0
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Pacman version: 6.0.1-2-x86_64

The Total package download percentage can become significantly more than 100%.
In the output snippet below it is 329% and increasing.

vim-runtime-8.2.3441-1-x86_64 is up to date
vim-8.2.3441-1-x86_64 is up to date
virtualbox-host-dkms-6.1.28-2-x86_64 708.6 KiB 118 KiB/s 00:06 [#######################################] 100%
virtualbox-6.1.28-2-x86_64 26.5 MiB 49.7 KiB/s 03:01 [#############################----------] 75%
Total (519/534) 565.4 MiB 49.7 KiB/s --:-- [#######################################] 329%

This observation contradicts my expectation that the total percentage represents a fraction of two sizes approaching 1 = 100% from below.

Perhaps that is related to some packages having been downloaded already but not installed yet.
This task depends upon

Comment by morganamilo (morganamilo) - Thursday, 21 October 2021, 14:20 GMT
Is this reproducible? Can you get the full output with --dubug?
Comment by Andrew Gregory (andrewgregory) - Thursday, 21 October 2021, 18:19 GMT
Do you have multiple cache directories?
Comment by Christian Cornelssen (ccorn) - Friday, 22 October 2021, 05:30 GMT
@andrewgregory: Yes, I have a custom repo dir added as a CacheDir, as described for the [aurutils]:

[aurutils]: https://github.com/AladW/aurutils/blob/master/man1/aur.1#L201
Comment by Allan McRae (Allan) - Friday, 22 October 2021, 05:43 GMT
Set that repo to "SigLevel = Never", or sign the packages in that repo. Then the issue will disappear.

Loading...