ocaml / opam.ocaml.org Goto Github PK

In https://github.com/ocaml/opam.ocaml.org/blob/master/update-opam-repo.sh#L162

# Add symlink to bulk builds
ln -s /logs/builds

ln command misses the destination argument here. Since I don't know which one was intended, I can't send a patch for this.

Also, shouldn't be BRANCH=1.2 be BRANCH=2.0 by default now, when opam 1.2 is deprecated?

In https://github.com/ocaml/opam.ocaml.org/blob/master/zip-logs.sh#L5
the line

for f in "$BASE/access-*.log"; do

will run only once because it is double quoted, to it will be not a word split

Screen shot below. error circled in yellow.

I got there using the menu Documentation->Development version (2.0). The url is http://opam.ocaml.org/doc/2.0/

Is something wrong with my browser?

The link opam dev team does not work and leads to an empty page.

The opam subdomain is now very integrated into ocaml.org from an end-user perspective. Yaron reported in ocaml/ocaml.org#218 that it is jarring to have such a different design. Also, even within the opam subdomain, the front page and the pkg/ pages have a different design. Ideally, all of *.ocaml.org pages would use the main ocaml.org style sheets.

moving ocaml/opam-repository#7804 to this repo

I would speculate that maybe https://github.com/ocaml/opam.ocaml.org/blob/master/nginx.conf#L39 should be changed to

   rewrite ^/pkg/((?U).+)/(.+)    /packages/$1/$1.$2 permanent;

Documentation mentions tags field when describing opam file format. It will be great to have a link there to the page where all used tags are listed. For example, I want to add some tags to my opam package and I don't know which to use to be in sync with packages with related functionality (for example, should I write gui or UI and etc.)

The OpenPGP key fingerpint mentioned in the release notes matches the released binaries, but the linked key returns a 404 Not Found response. See:

https://github.com/ocaml/opam/releases/tag/2.1.2

> curl -I https://opam.ocaml.org/opam-dev-pubkey.pgp
HTTP/2 404 
server: Caddy
date: Wed, 09 Feb 2022 20:15:06 GMT

Since opam-2.0 rocks the ocamlverse for a couple years already, maybe it makes sense to drop the unnecessary code from the maintenance scripts?

See also #15

ref: ocaml/opam#1005

No reason really to keep this private, unless we want to obfuscate the inner configuration of the server for "security" ? :)

Hi! it seems the opam dev team public key (mentioned in the releases) is not available currently:

$ curl -fsSL https://opam.ocaml.org/opam-dev-pubkey.pgp
curl: (22) The requested URL returned error: 404

Would its URL have changed?

Cc @AltGr @rjbou

I was sure someone (possibly me) had brought this up before, but I can't find anything about it, so filing a new issue: going to opam.ocaml.org uses the http protocol and does not redirect to https. Expected behaviour: going to http://... should 301 redirect to https://....