Marcello Seri
Marcello Seri
I am not against this. In this case, I think you should release it as version `1.1.3~unreleased`. In this way, once 1.1.3 is released, if there are changes, version `1.1.3`...
I will send a pr with the upper bounds of smtml and then publish. Can you look at the failure on debian-unstable? Is that expected?
Feel free to submit a patch to https://raw.githubusercontent.com/ocaml/opam-source-archives/main/patches/conf-python-3-7/configure.sh and then update the file checksum here
@jmid thanks! I have merged the other PR
Thanks! The lint is expected, "usual" conf packages do not have sources. This does not apply to this package but it is fine
I am trying a PR to mitigate this, but it is a known problem. from an opam PR: > In the meantime, you can fix your setup by telling to...
That's a bit delicate though, changes to conf-gmp cripple through lots of packages and usually appear as hard to track bugs. This is why the similar draft PR is taking...
Why can't one use pkg-config instead and fallback to some educated guesses if that is not present? That would automatically work for macos, bsd and many other systems, and be...
It is absolutely no problem to split your release to multiple packages, many other packages (probably even most of the larger ones) do this. As long as we don’t talk...