Mosè Giordano
Mosè Giordano
> I don't believe we can do that in a minor release? JLLs stdlibs have been removed before, and barely anyone noticed.
Looks to me like a breaking change in Pkg, reproducer is: ```julia using Pkg Pkg.add(Pkg.Types.Context(), [PackageSpec(; name = "Box2D_jll", uuid = "6756b63d-2e54-5dc6-816b-1fc83e1ae834", url = "https://github.com/cirocavani/Box2D_jll.jl")]) ``` Please open an issue...
> Is this something that can be removed from the internal calls of BinaryBuilder.jl or not? No
That's not very automatic though. Problem is that the [`LibGit2.jl`](https://docs.julialang.org/en/v1/stdlib/LibGit2/) standard library doesn't support submodules at all, and we use that for cloning repositories.
Just don't use the wizard. I honestly have no clue why the wizard has this problem (and I also rarely use it).
Yes: https://docs.binarybuilder.org/stable/#Manually-create-or-edit-build_tarballs.jl
For the record, a fix should use the same logic as #1223
> I also tried to bypass it by doing deploy="local" then push by hand but the sha end up completely messed up so it doesn't work neither. Delete the local...
I presume this would be an audit pass, adding the corresponding label
> Seems like it was due to me forgetting to use `compilers=[:c]`, adding that makes it at least start compilation in CI. Probably just needs docs then. You basically always...