[arch-dev-public] [dbscripts] [PATCH] Add signature files to update/move/remove targets

Pierre Schmitz pierre at archlinux.de
Fri Apr 1 15:44:37 EDT 2011


On Fri, 1 Apr 2011 00:54:57 +0200, Rémy Oudompheng wrote:
> Signature files are optional and the previous behaviour
> is unchanged when signatures files do not exist.
> 
> Signed-off-by: Rémy Oudompheng <remy at archlinux.org>
> ---
> This patch was already posted with very slight differences
> on the mailing-list by Allan. It needed several changes to
> fit the current state of dbscripts. I hope this one will
> allow to move forward.
> 
> Still nothing in the test suite: we would need to run
> gpg after the extra-*-build invocation and extra checks
> for the presence/absence of signature files in the repos.

I am a little confused by this patch. If I get the current repo-add
code right, gpg signatures will be base64 encoded and added to the db
files. So there should be no need to provide .sig files for every single
package.

-- 
Pierre Schmitz, https://users.archlinux.de/~pierre


More information about the arch-dev-public mailing list