Ewoud Kohl van Wijngaarden

> Asciidoctor docs site has that: https://docs.asciidoctor.org/ See "Edit this Page" in the top right corner. That would be cool but the question is how to implement this. I really...

> This convention becomes difficult to maintain because RHEL docs get restructured which breaks the links. Getting links to all versions up-to-date again is tedious, not to mention temporary (because...

Looks like we need to remove the files from the spec file too: ``` error: File not found: /builddir/build/BUILDROOT/rubygem-foreman_remote_execution-13.2.1-1.20240624154646537200.pr908.1.gbcd1648.el9.x86_64/usr/share/gems/gems/foreman_remote_execution-13.2.1/Gemfile error: File not found: /builddir/build/BUILDROOT/rubygem-foreman_remote_execution-13.2.1-1.20240624154646537200.pr908.1.gbcd1648.el9.x86_64/usr/share/gems/gems/foreman_remote_execution-13.2.1/foreman_remote_execution.gemspec error: File not found: /builddir/build/BUILDROOT/rubygem-foreman_remote_execution-13.2.1-1.20240624154646537200.pr908.1.gbcd1648.el9.x86_64/usr/share/gems/gems/foreman_remote_execution-13.2.1/test File...

Sadly the same bug also affects EL9. I'll update the bug to also mention EL9 and point to https://gitlab.com/redhat/centos-stream/rpms/keycloak-httpd-client-install/-/merge_requests/8.

> This requires a procedure change to start tagging develop versions when we branch to be useful. Looking at https://github.com/theforeman/foreman/commit/b1c05b878e7d7c63a28db8261e971333a0ea7c7a is what we now do during branching. This is the...

Interesting failure: we do a shallow clone so `git describe` can't work. We'll probably need to special case that in `version.rb`.

> Interesting idea. Getting something visible early is certainly important for motivation. That motivation was indeed my reason. > Because a one-day workshop is often not sufficient to go through...

Some notes: it was introduced in e28a51998be06ab97ce4d56b5fa16f1d2024ee33 and we shouldn't store `--certs-regenerate` but it should be passed to Puppet. I'm now debating options, but can't think of any right now....

My issue with the current implementation is that `--noop` or `--dont-save-answers` isn't respected: it always saves the answers. I'm looking at https://github.com/theforeman/kafo/blob/master/doc/kafo_run.png and I'm wondering if we should take a...

ok to test