With the "--repo" option, paru does synchronization operations twice

[refola]

Affected Version

I first encountered this a while ago (possibly when I first used paru), but didn't take note at the time.

paru -V paru v2.0.4 - libalpm v15.0.0

Description

Running a paru sync operation with --repo performs the sync operation twice. I expect that, e.g., paru --repo -Sy should only sync the mirrors once.

Have you checked previous issues? I searched for any issue with "--repo" in it, but GitHub's search ate the -- and the 15 pages of results seemed to all be generic references to some "repo" or another. I did Ctrl+F search each page of results for --repo, and it's not in any of the titles.

Output

Include the FULL output of any relevant commands/configs I'm scripting it a bit to show how it's the same with --repo before and after the pacman operation, and applies the same to -Sy, -Syu, and -Syuw.

Don't cut parts of the input always include the FULL thing

> PS1='> '; sudo -v; for op in '-Sy' '-Syu' '-Syuw'; do for ops in "$op --repo" "--repo $op"; do cmd="paru $ops"; echo; echo "$PS1$cmd"; $cmd; done; done

> paru -Sy --repo
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date

> paru --repo -Sy
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date

> paru -Syu --repo
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
 there is nothing to do
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
 there is nothing to do

> paru --repo -Syu
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
 there is nothing to do
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
 there is nothing to do

> paru -Syuw --repo
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
 there is nothing to do
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
 there is nothing to do

> paru --repo -Syuw
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
 there is nothing to do
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
 there is nothing to do

paru.conf and pacman.conf are usually always relevant I don't think i changed them, but here they are (copied with names edited to comply with GitHub's file extension filter). pacman.conf.txt paru.conf.txt