mirror of
https://github.com/aptly-dev/aptly.git
synced 2026-06-02 04:50:49 +00:00
Andrey Smirnov
7a5be6736d
This replaces `panic` which aborts aptly execution with warning message on console. So aptly continues publishing actions, but `Contents` indexes might be incomplete. Error will be printed every time contents generation is triggered.
15 lines
801 B
Plaintext
15 lines
801 B
Plaintext
Loading packages...
|
|
Generating metadata files and linking package files...
|
|
[!] Failed to generate package contents: unable to read .tar archive from ${HOME}/.aptly/pool/3a/0a/libboost-broken-program-options-dev_1.49.0.1_i386.deb: unexpected EOF
|
|
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 main
|
|
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.
|