Closed deadmeu closed 1 month ago
Indeed, I can reproduce. There's no "configuration" on your part, it's all happening in the container.
@garrett can you please have a look? Thanks!
Apologies for the 2 week delay! It's holiday time in Europe so workdays are limited this month. As a result, I've been focused on various designs and PRs for two different teams (Cockpit included), so I've been mostly ignoring my GitHub notifications as to be able to get some specific tasks done. No one pinged me specifically about this issue, so I'm just getting around to it now. :wink:
We inherit from GitHub Pages (on purpose) and stack a few Gems on top, locking them in place (as to be reproducible) and the containers help with that.
However, the container for GitHub Pages is at :latest
, as GitHub is also using the latest container for building. I suspect that something changed in their container or in a minor version of a gem (probably the later, where they didn't test a combination of gems that we happened to use). I'd dig into the exact reason, except that I found a fix that works. I've nuked the Gemfile.lock
and generated a new dependency of gems and the bug doesn't show up.
Updating our gem dependency tree is good to do from time to time (and we do this from time to time anyway). As we're generating a static site, it isn't as important as code running in production, but still a good idea nonetheless. Updating to the latest sets of gem dependencies fixes this bug, so the gems are all actually fully compatible again with Jekyll (instead of just saying they are).
I'll be pushing up a PR in a couple minutes that fixes this. Thanks for your patience! Apologies again for being away to fix this!
I'm trying to run an instance of the website in an EndeavourOS VM but am getting the following error:
It may be due to a configuration error on my part but I'm not sure.