[SOLVED] Sigs not found for xyne repos

Question

edit: -facepalm-
Changing
SigLevel = Required
to
SigLevel = PackageRequired
in pacman.conf did the trick
As the title suggests I'm having problems with a lack of signatures for Xyne's repos (not sure if this topic belongs here for unofficial repos?). It was working fine last night when I last upgraded the computer
[11:59:25] $ sudo \pacman -Syu
error: xyne-x86_64: missing required signature
error: xyne-any: missing required signature
:: Synchronizing package databases...
core is up to date
extra is up to date
xyne-x86_64 is up to date
xyne-any is up to date
community is up to date
error: database 'xyne-x86_64' is not valid (invalid or corrupted database (PGP signature))
error: database 'xyne-any' is not valid (invalid or corrupted database (PGP signature))
When I attempt to refresh the mirrors
[12:00:31] $ sudo \pacman -Syy
error: xyne-x86_64: missing required signature
error: xyne-any: missing required signature
:: Synchronizing package databases...
core 107.8 KiB 175K/s 00:01 [--------------------------------------------------------------------------] 100%
extra 1408.5 KiB 183K/s 00:08 [--------------------------------------------------------------------------] 100%
xyne-x86_64 2.7 KiB 330K/s 00:00 [--------------------------------------------------------------------------] 100%
error: failed retrieving file 'xyne-x86_64.db.sig' from xyne.archlinux.ca : The requested URL returned error: 404
error: xyne-x86_64: missing required signature
error: failed to update xyne-x86_64 (invalid or corrupted database (PGP signature))
xyne-any 15.1 KiB 41.1K/s 00:00 [--------------------------------------------------------------------------] 100%
error: failed retrieving file 'xyne-any.db.sig' from xyne.archlinux.ca : The requested URL returned error: 404
error: xyne-any: missing required signature
error: failed to update xyne-any (invalid or corrupted database (PGP signature))
community 1765.0 KiB 181K/s 00:10 [--------------------------------------------------------------------------] 100%
error: database 'xyne-x86_64' is not valid (invalid or corrupted database (PGP signature))
error: database 'xyne-any' is not valid (invalid or corrupted database (PGP signature))
Updating the package keys manually
$ sudo \pacman-key --refresh-keys
gpg: key C2E5C0D2: "Xyne. <[email protected]>" not changed
That key is the same as the one on Xyne's site and the TU page
pacman.conf
[12:10:41] $ cat /etc/pacman.conf
# /etc/pacman.conf
# See the pacman.conf(5) manpage for option and repository directives
# GENERAL OPTIONS
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir = /
#DBPath = /var/lib/pacman/
CacheDir = /mnt/Packages/
#LogFile = /var/log/pacman.log
#GPGDir = /etc/pacman.d/gnupg/
HoldPkg = pacman glibc
# If upgrades are available for these packages they will be asked for first
SyncFirst = pacman
#XferCommand = /usr/bin/curl -C - -f %u > %o
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
Architecture = auto
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg =
#IgnoreGroup =
#NoUpgrade =
#NoExtract =
# Misc options
#UseSyslog
UseDelta
TotalDownload
CheckSpace
#VerbosePkgLists
ILoveCandy
# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
#SigLevel = Optional TrustedOnly
# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Arch Linux
# packagers with `pacman-key --populate archlinux`.
# REPOSITORIES
# - can be defined here or included from another file
# - pacman will search repositories in the order defined here
# - local/custom mirrors can be added here or in separate files
# - repositories listed first will take precedence when packages
# have identical names, regardless of version number
# - URLs will have $repo replaced by the name of the current repo
# - URLs will have $arch replaced by the name of the architecture
# Repository entries are of the format:
# [repo-name]
# Server = ServerName
# Include = IncludePath
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.
#[kde-unstable]
#SigLevel = PackageRequired
#Include = /etc/pacman.d/mirrorlist
#[testing]
#SigLevel = PackageRequired
#Include = /etc/pacman.d/mirrorlist
[core]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist
[extra]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist
[xyne-x86_64]
SigLevel = Required
Server = http://xyne.archlinux.ca/repos/xyne-x86_64
[xyne-any]
SigLevel = Required
Server = http://xyne.archlinux.ca/repos/xyne-any
#[community-testing]
#SigLevel = PackageRequired
#Include = /etc/pacman.d/mirrorlist
[community]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist
# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.
#[multilib-testing]
#SigLevel = PackageRequired
#Include = /etc/pacman.d/mirrorlist
#[multilib]
#SigLevel = PackageRequired
#Include = /etc/pacman.d/mirrorlist
# An example of a custom package repository. See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs
Last edited by SS4 (2012-07-25 13:53:50)

Answer 1

Xyne wrote:
SS4 wrote:
edit: -facepalm-
Changing
SigLevel = Required
to
SigLevel = PackageRequired
in pacman.conf did the trick
No, that was my fault. I updated my release scripts yesterday and the new ones did not create the database signature symlink. I just fixed it about 10 minutes ago.
Change the SigLevel back to Required, otherwise Pacman will not verify the databases. Everything should be working again.
Cheers, upgrading is back to normal (good work on the repo btw)