- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jan 8 2023
Oct 19 2022
Sep 23 2022
This perimeter enters the scope of T3781.
Jun 29 2022
Feb 25 2022
In T3976#79630, @olasd wrote:https://opam.ocaml.org/doc/FAQ.html#Why-does-opam-require-bwrap
"If needed, for special cases like unprivileged containers, sandboxing can be disabled on opam init with the --disable-sandboxing flag (only for non-initialised opam)".
I think that would make sense, as we never execute code from the opam root, we only read metadata files.
"If needed, for special cases like unprivileged containers, sandboxing can be disabled on opam init with the --disable-sandboxing flag (only for non-initialised opam)".
Jan 7 2022
That may be superseded by the task T3781 which proposes to rewrite that loader as a lister.
And then delegate the origins listed by it to loaders (git, archive, etc...)
Dec 17 2021
Dec 16 2021
Dec 13 2021
Dec 12 2021
Nixguix loader is ok.
Dec 10 2021
Dec 9 2021
Now the loader nixguix fails with [1]
So the update scheduler metrics routine the graph (mentioned in the description)
relies upon is taking some time to finish (investigation ongoing [3]) hence the apparent
stale.
Dec 8 2021
Scheduling has been done [1]. The listing process happened [2]. Now let the debian
loaders do its job (ongoing) [3].
All ongoing ingestions [1] are now only doing 'uneventful' events.
So that means we did finalize the re-ingestions.