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

Rémy Oudompheng remyoudompheng at gmail.com
Fri Apr 1 16:05:40 EDT 2011

On 2011/4/1 Pierre Schmitz <pierre at archlinux.de> wrote:
> On Fri, 1 Apr 2011 21:54:30 +0200, Rémy Oudompheng wrote:
>> 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)
> I think it will work this way:
> * you upload the package and its separate signature into your staging
> dir
> * repo-add will add the pacakge's meta data and signature into the
> database file

In the current setting (arch_repo_add) in db-functions, repo-add is
run from the repo directory ($repo/os/$arch) and would not have access
to the signature files. A progress would be to run it from the package
pool, so that we don't have to link signature files to repo folders.

But not having the signature files in the package pool would make it
problematic to use db-move correctly, since signatures would have been
deleted from $HOME/staging directories in the meanwhile.


More information about the arch-dev-public mailing list