From: Tuomas Ahola <taahol@utu.fi>
To: Junio C Hamano <gitster@pobox.com>
Cc: <git@vger.kernel.org>
Subject: jk/ci-use-system-asciidoctor
Date: Fri, 11 Sep 2026 09:50:43 +0300 [thread overview]
Message-ID: <20260911065043.0SiOV%taahol@utu.fi> (raw)
In-Reply-To: <xmqqa4ppf1l5.fsf@gitster.g>
Junio C Hamano <gitster@pobox.com> wrote:
> * ps/ci-depends-on-ruby (2026-09-01) 1 commit
> (merged to 'next' on 2026-09-08 at d0859510f8)
> + ci: fix missing Ruby dependency in "documentation" job
>
This seems to be duplicated...
> * jk/ci-use-system-asciidoctor (2026-09-02) 2 commits
> (merged to 'next' on 2026-09-08 at e7621b4bad)
> + ci: drop ALREADY_HAVE_ASCIIDOCTOR variable
> + ci: fix missing Ruby dependency in "documentation" job
>
...here---perhaps we would like to fix that when those topics graduate.
$ git describe --contains --all 7918bd7d08 691dc53e2a
remotes/origin/next~6^2~1
remotes/origin/next~7^2
$ git range-diff 7918bd7d08...691dc53e2a
1: 7918bd7d08 ! 1: 691dc53e2a ci: fix missing Ruby dependency in "documentation" job
@@ Commit message
./ci/install-dependencies.sh: 23: gem: not found
The root cause of this is that we never explicitly install Ruby, and
- consequently gem(1) isn't explicitly pulled inus, either. This used to
+ consequently gem(1) isn't explicitly pulled in, either. This used to
work alright because we transitively pulled in Ruby via asciidoc. But
due to an update it seems that we stopped pulling in the transitive
dependency, and consequently we don't have gem(1) available anymore.
It's always good not to immortalize typos in 'master' if we can choose.
next prev parent reply other threads:[~2026-09-11 6:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 17:39 What's cooking in git.git (Sep 2026, #04) Junio C Hamano
2026-09-11 6:01 ` Patrick Steinhardt
2026-09-11 15:53 ` Junio C Hamano
2026-09-11 19:01 ` Patrick Steinhardt
2026-09-11 6:50 ` Tuomas Ahola [this message]
2026-09-11 15:56 ` jk/ci-use-system-asciidoctor Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260911065043.0SiOV%taahol@utu.fi \
--to=taahol@utu.fi \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.