[RPKI] Krill install-and-run doc update

[Ximon Eighteen]

Hi John,

Apologies for the delay in replying.

The doc that you linked to refers to "amd64/x86_64 architecture running Debian 9, 10 or 11” and Krill DEB packages are indeed available for the amd64 architecture on those operating system versions. I quickly verified this using Docker like so (based on the instructions in that document):

> docker run --rm -it debian:N
# apt update
# apt install -y ca-certificates curl gnupg lsb-release
# curl -fsSL https://packages.nlnetlabs.nl/aptkey.asc | gpg --dearmor -o /usr/share/keyrings/nlnetlabs-archive-keyring.gpg
# echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/nlnetlabs-archive-keyring.gpg] https://packages.nlnetlabs.nl/linux/debian $(lsb_release -cs) main" | tee /etc/apt/sources.list.d/nlnetlabs.list > /dev/null
# apt update
# apt install -y krill

Where N is 9, 10 or 11. Note: on Debian 9 some extra steps are needed to work around no longer found Debian repositories and the missing apt-transport-https package.

For Debian 9, 10 and 11 this installs respectively the packages krill_0.13.1-1stretch_amd64.deb, krill_0.13.1-1buster_amd64.deb and krill_0.13.1-1bullseye_amd64.deb.

At the time of writing there is not yet a package available specifically for the Debian 12 Bookworm O/S version, though that will be remedied with the upcoming Krill 0.14 release. Unfortunately you can’t use the Bullseye package on Bookworm due to an unmet dependency on the libssl1.1 package, which is why the upcoming Bookworm package will depend on libssl3 instead.

We don’t have standalone Debian sources per se, our DEB packages are built using the cargo-deb tool [1] based on metadata in the Cargo.toml file and some supporting files in the Krill Git repository. An alternative installation method if needed would be to build using Rust Cargo as described in the document you linked to.

If I have misunderstood what you are trying to do and there is in fact a problem with the documentation I’d be happy to try and help resolve the issue if you could point out the misunderstanding, otherwise I hope the above helps.

Ximon
NLnet Labs

--

[1]: https://github.com/kornelski/cargo-deb

> Op 26 sep 2023, om 00:30 heeft John Kristoff via RPKI <rpki at lists.nlnetlabs.nl> het volgende geschreven:
> 
> Hello NLnet Labs,
> 
> Apparently the doc here:
> 
>  <https://krill.docs.nlnetlabs.nl/en/stable/install-and-run.html>
> 
> has some problems.  There doesn't appear to be any actual Debian amd64
> packages for example.
> 
> I'd submit a doc patch, but this might be a little more involved for me
> to figure out exactly what you should say.  Maybe just point to your
> standalone Debian sources or is there another preferred method for this
> architecture?
> 
> Thank you,
> 
> John
> -- 
> RPKI mailing list
> RPKI at lists.nlnetlabs.nl
> https://lists.nlnetlabs.nl/mailman/listinfo/rpki

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/rpki/attachments/20230928/9a4dcd51/attachment.htm>