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.

FS#48085 - [pacman] repo-add -v stricter argument checking, or expanded functionality

Attached to Project: Pacman
Opened by Johannes Ernst (jernst) - Monday, 08 February 2016, 05:19 GMT
Last edited by Allan McRae (Allan) - Wednesday, 02 March 2016, 04:09 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To Allan McRae (Allan)
Architecture All
Severity Medium
Priority Normal
Reported Version 5.0.0
Due in Version 5.1.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


repo-add -v something.db.tar.xz

(no packages to add) works without complaint. But then if I run it again, it says “bad signature”. This is quite befuddling.

Suggestion: disallow the invocation above, on the grounds that -v is not a standalone verify operation (which I originally thought it was) but one that is supposed to verify the db before actually adding something.

Or allow the invocation, and make it a standalone verification operation that does not change the tar file or the signature.

Additional info:
* 5.0.0 and probably earlier
This task depends upon

Closed by  Allan McRae (Allan)
Wednesday, 02 March 2016, 04:09 GMT
Reason for closing:  Fixed
Additional comments about closing:  git commit f363cf78
Comment by Xyne (Xyne) - Sunday, 14 February 2016, 05:59 GMT
I found this confusing as well. If there is nothing to change then it should just leave the existing signed database alone.
Comment by Allan McRae (Allan) - Sunday, 21 February 2016, 09:08 GMT