Nathan Rebours

You can use `dune-release tag -d` to remove the tag. That works fairly well since at that point the tag only exists locally. I agree it is unfortunate though, we...

Also note that you can run `distrib` without tagging, you should only get a warning!

One thing worth noting is that we'll have to make sure we can create a branch on top of the target repository's default branch. I'm sure this will be possible...

Have you tried removing the packages from your opam switch before running this? I.e. run: ``` opam remove happy-eyeballs happy-eyeballs-lwt happy-eyeballs-mirage ``` Since the packages are interdependent I think it...

Ah my bad I missed the intermediate `dns-client` package here. Do you still get the error if you pin `happy-eyeballs`' repo before running the release?

I assume the pinning won't solve your problem here unfortunately. The "interleaved" structure of the `happy-eyeball` and `ocaml-dns` multi-opam repos is a bit of a problem here. The only viable...

To be entirely fair I think this kind of testing would also be better handled in a CI than locally but I guess we'll have to settle for baby steps...

That's because dune-release uses the content of the tarball to run the builds, which likely doesn't include your local copy of `ocaml-dns` since it is built using the git revision...

Yeah we definitely need to do something about this, in particular it should fallback to github if the dev-repo is on github

I totally agree, we have a plan to get rid of delegates by the way so this should soon be a problem of the past: https://github.com/ocamllabs/dune-release/issues/188