package reprepro
notfound 406023 1.3.1-1
thanks
* Vagrant Cascadian <[EMAIL PROTECTED]> [070108 02:40]:
> i was wondering if it would be possible to include some sort of
> mechanism to verify gpg-signed .changes or .dsc files when using the
> include or includedsc commands.
>
> i.e. reprepro include local foo_version_arch.changes
There already is something like that, though I've not yet used it myself
much, so there might still some bugs hidden in it.
Please try (don't be confused by it being "allow" while the manpage says
it's "accept", that is a bug in the manpage already fixed in CVS):
cat >conf/somename <<EOF
allow * by key 1DB114E0
allow * by key 4F368D5D
allow * by key B5F5BBED
allow * by key 2D230C5F
EOF
and add a line
Uploaders: somename
to the appropriate chunk in conf/distributions.
Currently there is only "allow *" and no more fine tuned permissions,
mostly because I do not yet know what kind of control would be wanted.
(I thought of things like only allowing things with override entry,
or only allowing things with a key-specific maintainer override, or
things like specific packages or sections, but I'm yet undecided what
to support).
The keyring cannot be specified (as libgpgme is missing some way to set
it, or I have not found it). In general the GNUPGHOME environment
variable is used by gpg (which is called by libgpgme) and it uses the
pubring.gpg in that directory. (This of course effects all checking
and signing then).
> this would make it much easier to implement a simple upload queue for
> reprepro.
I'm currently working on a import command to make reprepro scan a
directory for changes and include them. As that has quite different
requirements than including from local files, its quite some
refactorisation of some code and will need some time before it is
finished. (Current CVS version seems to work, but it missing support
for tracking, and some more testcases (and most likely bugfixes) for
strange combinations or graciously coping with errors in dsc files.
Hochachtungsvoll,
Bernhard R. Link
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
