Ok, I just want to verify: the system that runs the jobs hasn't been changed in the last few days that might have effected this? The version of Ocaml I'm running and Alpine are pinned to specific versions so those have not changed but started failing.
All of a sudden I'm seeing failures on building on Alpine. My code hasn't changed nor my build. The error I'm getting is below. I can investigate more, but I wanted to verify this doesn't reflect a known change.
Processing 4/12: [ocaml-system: ocaml gen_ocaml_config.ml] [ERROR] The compilation of ocaml-system failed at "/home/build/.opam/opam-init/hooks/sandbox.sh build ocaml gen_ocaml_config.ml". -> installed base-bigarray.base -> installed base-threads.base -> installed base-unix.base #=== ERROR while compiling ocaml-system.4.08.1 ================================# # context 2.0.5 | linux/x86_64 | | https://opam.ocaml.org#959fadce # path ~/.opam/default/.opam-switch/build/ocaml-system.4.08.1 # command ~/.opam/opam-init/hooks/sandbox.sh build ocaml gen_ocaml_config.ml # exit-code 1 # env-file /tmp/opam-build-2405/ocaml-system-2405-ad6566.env # output-file /tmp/opam-build-2405/ocaml-system-2405-ad6566.out ### output ### # bwrap: Can't bind mount oldroot/proc on /newroot/proc: No such file or directory # bwrap: Can't read from privileged_op_socket
Ah ok, apologies if I misinterpreted what you said. My understanding was that you were not interested in showing hg at all until hg became more popular, and at that point you'd consider a dropdown.
That doesn't really answer my initial question: what metric(s) can someone present to you where you would say that hg is worth putting in the navbar, whatever that particular solution looks like?
I think the concern of someone accidentally making a hg repo is unlikely but at this point its your belief against mine. On the other hand, as someone trying to promote hg use, when people ask me where they can host repos I have to say sourcehut and then quickly explain that it's only supported if you know where to find it (there is a link to it on sourcehut.org but I don't think most users would expect to have to click that link, and only that link). And I can't even say "but if we get to 1000 hg repos, Drew has committed to put it on the front page".
Is there any metric you can commit to for when you will agree to put hg in the navbar? Otherwise it's a goal without an end.
My personal opinion is that:
- It's not going to confuse many people. Maybe they'll click it out of curiosity and then click back to git, what they really want to use.
- sourcehut is happy to accept the BitBucket refugees but not happy to display the support with the other features. I don't know how to describe that but it doesn't feel quite right to me. It feels like a bit of a catch-22, the likely best service to support hg won't display it until hg becomes more relevant but it's also probably a vector for making hg more relevant if it did display it.
FWIW, the only reason I am paying for sourcehut is because of hg support. I get that hg is not as popular as git, and it's unlikely to be anytime soon. The reasoning in this ticket seems to have no objective solution, though.
~ludovicchabant I added you with browse permissions
I also noticed on that link, the diff coloring isn't showing up.
If you look at other patches on that list, they are diffed properly and they were generated using
hg emailas well.
I've added you as having the ability to browse on the list. The thread is:
This was generated using
I just discovered the Patch view in lists today, and while it shows my older patches I'm not seeing one I sent around 1 hour ago in there.
Is this because it runs on a cron of some kind? Or is it just so new it still has some bugs? Or something else?
If there are subscribers to a list and the owner modifies the list to be more restrictive (as in subscribers cannot browse or post messages) the permissions of existing subscribers does not change.
As permissions change, existing subscribers should have those permissions be applied to them. For example, if the Browse permissions is removed from Subscribers, existing subscribers should not longer be able to browser the list.