mirror of
https://github.com/aptly-dev/aptly.git
synced 2026-01-11 03:11:50 +00:00
a4cc9211d6
https://wiki.debian.org/DebianRepository/Format#Signed-By says: > **Signed-By** > An optional field containing a comma separated list of > OpenPGP key fingerprints to be used for validating > the next Release file. The fingerprints must consist > only of hex digits and may not contain spaces. > The fingerprint specifies either the key the Release file > must be signed with or the key the signature key must be > a subkey of. The later match can be disabled by appending > an exclamation mark to the fingerprint. > > If the field is present, a client should only accept future updates > to the repository that are signed with keys listed in the field. > The field should be ignored if the Valid-Until field is not present > or if it is expired. For both the CLI tools and JSON, the field is taken as a string verbatim. When specified, we must also provide `Valid-Until` field, and i'm not sure there is an 'infinity' value for it, so 100 years will have to do? Fixes https://github.com/aptly-dev/aptly/issues/1497
15 lines
680 B
Plaintext
15 lines
680 B
Plaintext
Loading packages...
|
|
Generating metadata files and linking package files...
|
|
Finalizing metadata files...
|
|
Signing file 'Release' with gpg, please enter your passphrase when prompted:
|
|
Clearsigning file 'Release' with gpg, please enter your passphrase when prompted:
|
|
|
|
Local repo local-repo has been successfully published.
|
|
Please setup your webserver to serve directory '${HOME}/.aptly/public' with autoindexing.
|
|
Now you can add following line to apt sources:
|
|
deb http://your-server/ maverick contrib
|
|
deb-src http://your-server/ maverick contrib
|
|
Don't forget to add your GPG key to apt with apt-key.
|
|
|
|
You can also use `aptly serve` to publish your repositories over HTTP quickly.
|