- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jan 8 2023
Oct 19 2022
Oct 4 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
Deployed. And alerts are no longer now [1]
Jan 6 2022
Jan 3 2022
Nov 22 2021
Nov 18 2021
Nov 17 2021
Nov 10 2021
@ardumont For production, drop the / at the end of the url, in staging, it's duplicated...
This got added to the staging infrastructure which lead to some surprises.
This mostly got fixed in the commits ^.
Nov 8 2021
Oct 8 2021
(this task is a dependency of T3638, because author != committer in revisions created by opam, and releases don't have a "committer" field, so switching to releases would lose this data)
Oct 2 2021
Sep 29 2021
And it's now deployed.
Closing.
Deployed.
Remains to add the origin show up on the main archive page.
@anlambert I've asked antoine to do it.
It's been deployed for a while and the first ingestion on production has been done.
Archive changelog got updated as well.
Sep 28 2021
That's done. The remaining part is about optimization. So closing.
Sep 27 2021
First listing and loading done in production.
I'll update the archive changelog about this.
Sep 24 2021
Sep 23 2021
Sep 22 2021
Sep 21 2021
Sep 20 2021
Deployed the multiple fixes we did with @anlambert.
That and @mclovin's upstream fixes. We should be good.