On Mon, Jan 28, 2013 at 9:56 PM, Xyne
Hi Magnus,
How are you generating database signatures? I regularly have to issue "pacman -Syyu" to force Pacman to download newer signature files. In general, the signature should be generated and uploaded at the same time as the database to avoid the invalid signature error. It is admittedly a bug that Pacman fails to check for newer signatures but it is avoidable.
I use the '--sign' argument to tell `repo-add` to sign the database as I add packages. I've seen this myself, ever. Which repo are you using? If you use the xsounds repo then there could be an issue with the rsync'ing.
Was the repo-add_and_sign script that I wrote not useful? That should completely avoid all mismatched signature errors in the repo.
I'm not using it, no. I don't remember why, it might just have been that I wanted to understand how pacman works with signing for myself first. At the moment I have two short scripts, one for signing the packages and one for adding packages to the database. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus