Wojtek Porczyk

Maybe we need some real templating solution in place of that `sed` hack, which is duplicated everywhere in `Examples/`. In theory we shouldn't really need this in production, because signed...

After #2593/#2644 `fs.mount` also should be an array and that would pretty much be it I think.

This is almost certainly this thing: https://github.com/sphinx-doc/sphinx/issues/10121 (and a duplicate: https://github.com/sphinx-doc/sphinx/issues/9923). It's a regression between Sphinx and Docutils, and it was triggered by updating to docutils>=0.18 without updating to Sphinx...

Because it will cause a situation, where you can't simply `apt-get install` all dependencies that will reflect what RTD is doing when building our docs, so you won't really be...

#1784 is a draft that fixes the rendering issue and also drops older distros. The downside is, it cannot be iterated on Ubuntu. If we agree on it, we can...

> reason why it is not possible to execute the “which” command and shell scripts in gramine is what? The usual reason for such problem is misconfiguration on part of...

Yes, apart from testing gramine from packages. I've unpinned this ticket from the issue tracker.

`bullseye` base, with `bullseye-backports` and this intel repo exactly as in CI. Here's a `.buildinfo` for you (sorry for `.txt` suffix, github doesn't accept arbitrary files): [gramine_1.4_amd64.buildinfo.txt](https://github.com/gramineproject/gramine/files/10824018/gramine_1.4_amd64.buildinfo.txt) Please share yours,...

> However, I it would be a more sensible approach if the Gramine devs could agree to use a nix environment for their binary releases. It might be easier, but...

I mean meson and everything that we put in `meson.build` files. It's one of the ingredients that matters, but there are others. "Reproducible builds" is not something that you can...