On Thu, Mar 06, 2008 at 04:00:41PM +0100, Marc Haber wrote:
> I would prefer having an option to have reprepro stop after the .new
> files were written (while the old files are still in place), and to
> have a new reprepro command to finish the work after the .new files
> were signed by some magic
* Marc Haber <[EMAIL PROTECTED]> [080306 16:15]:
> > As it is just taking the Release file and sign them, that itself is not
> > that complicated, though the question is how to properly integrate that.
>
> Would a temporary solution for me be to accept the repository being
> inconsistent for a sho
On Thu, Mar 06, 2008 at 02:58:34PM +0100, Bernhard R. Link wrote:
> * Marc Haber <[EMAIL PROTECTED]> [080306 13:02]:
> > Thus, there is a need to offline
> > sign the Release file after reprepro has created the file.
> >
> > I'd like the mechanism to work like the -r option of the debsign
> > comma
* Marc Haber <[EMAIL PROTECTED]> [080306 13:02]:
> I would like to sign my archive with a key that should never be stored
> on the server holding the archive.
Already on my TODO list (though quite at the end) is having reprepro run
on one host (where database and keys are stored) and the dists/ an
Package: reprepro
Severity: wishlist
Hi,
I would like to sign my archive with a key that should never be stored
on the server holding the archive. Thus, there is a need to offline
sign the Release file after reprepro has created the file.
I'd like the mechanism to work like the -r option of the
5 matches
Mail list logo
