FS#60880 - [pacman] throws ambiguous error without gnupg support and having repo with SigLevel configured
Attached to Project:
Pacman
Opened by Mark Vainomaa (mikroskeem) - Wednesday, 21 November 2018, 16:38 GMT
Last edited by Allan McRae (Allan) - Friday, 11 October 2019, 10:28 GMT
Opened by Mark Vainomaa (mikroskeem) - Wednesday, 21 November 2018, 16:38 GMT
Last edited by Allan McRae (Allan) - Friday, 11 October 2019, 10:28 GMT
|
Details
Summary and Info:
When pacman is compiled without gnupg support, then specifying SigLevel in server section causes pacman to throw ambiguous error: error: could not register 'core' database (wrong or NULL argument passed) This does not provide anything useful into logs either, so without any knowledge one has to dig in pacman codebase to figure out the cause of this error. Ideally, SigLevel should be ignored when pacman hasn't been compiled with gnupg support Steps to Reproduce: Configure pacman without gnupg (not being present compile time - that's my case; or using appropriate ./configure flag) Try to add a server section into pacman.conf with SigLevel, like: [core] Server = https://foo.bar/baz/$repo/os/$arch SigLevel = Never Get this error message: error: could not register 'core' database (wrong or NULL argument passed) |
This task depends upon
Comment by
Mark Vainomaa (mikroskeem) -
Wednesday, 21 November 2018, 18:58 GMT
Comment by
Andrew Gregory (andrewgregory) -
Tuesday, 25 December 2018, 18:17 GMT
s/unambiguous/ambiguous/g, i suck at english today :(
The error should no longer be thrown for SigLevel = Never as of
v5.1.2. Leaving this open as a reminder about the ambiguous error
message for other SigLevels.