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

Rémy Oudompheng remyoudompheng at gmail.com
Fri Apr 1 15:54:30 EDT 2011

On 2011/4/1 Pierre Schmitz <pierre at archlinux.de> wrote:
> 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.

Then I'm also confused by our current handling of signatures.
Do we have decided anything about that?
Why did Allan suggest this patch?
How can repo-add put signatures in db files if signatures are not
available in the package pool? (we probably don't want to extract the
signature and copy it when moving packages between repos)

In my current understanding:
* package pool holds packages and their signature files, and serves as
the basis for generating databases
* repo directories ($repo/os/$arch) contain symlinks to packages,
databases which are generated by repo-add, and the signature file for
the database.


More information about the arch-dev-public mailing list