Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#47998 - [gnome-packagekit] Doesn't work with unsigned repos

Attached to Project: Community Packages
Opened by Justin Dray (justin8) - Tuesday, 02 February 2016, 23:18 GMT
Last edited by Christian Hesse (eworm) - Tuesday, 09 February 2016, 07:10 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When using repo-add to create a repository, I get '[repo]: Invalid or corrupted database (PGP signature)' error when opening the package updater. I can install packages from the same repo without issue via pacman, or even via the gnome-packagekit package viewer, but the updater fails every time.

Additional info:
* package version(s)
pacman: 4.2.1-4
gnome-packagekit: 3.18.0-1
* config and/or log files etc.


Steps to reproduce:
Add a repo without signing to pacman.conf:
[dray.be]
SigLevel = Optional TrustAll
Server = https://repo.dray.be/

Open package updater.
   Screenshot from 2016-02-03 09... (33.9 KiB)
This task depends upon

Closed by  Christian Hesse (eworm)
Tuesday, 09 February 2016, 07:10 GMT
Reason for closing:  Works for me
Comment by Justin Dray (justin8) - Tuesday, 02 February 2016, 23:19 GMT
The screenshot on the bug report is before running pacman -Sy after clearing out the sync database. After a pacman -Sy is run, I get the error here
   Screenshot from 2016-02-03 09... (36.1 KiB)
Comment by Christian Hesse (eworm) - Monday, 08 February 2016, 07:42 GMT
Please update your system to latest versions. Does this still happen with

pacman 5.0.0-1
packagekit 1.0.11-4
Comment by Christian Hesse (eworm) - Monday, 08 February 2016, 16:02 GMT
Tried several times, but your repository server times out.
Just to be sure... Is your issue caused by missing signature or the fact that db file can not be retrieved? The latter would explain why update fails but install succeeds.
Comment by Justin Dray (justin8) - Tuesday, 09 February 2016, 02:29 GMT
Sorry, it was hosted on my home connection, and I replaced my router recently and it was only working internally. It should be up again now.

It appears to have been resolved with the update to pacman and packagekit. Thanks.

Loading...