On 2025-03-16 23:57:33, Fabian Grünbichler wrote: > On Thu, Mar 13, 2025, at 9:43 PM, Fabian Grünbichler wrote: > > On Thu, Mar 13, 2025, at 5:59 PM, Timo Röhling wrote: > >> > >> According to sources.d.o, the functions are only used in rust/cargo and > >> libgit2 itself. There have been a number of additions and a few > >> constants have changed values (notably GIT_CHECKOUT_SAFE and > >> GIT_CHECKOUT_NONE), but all this affects the ABI only. > > > > yes, but only in the (low and high level) libgit2 bindings used by > > cargo (rust-libgit2-sys / rust-git2 and their vendored copies in the > > rustc/cargo package), not in cargo itself. I can prepare the > > corresponding updates for those in experimental on the weekend. > > rust-bat, rust-broot, rust-cargo, rust-git-absorb, rust-ripasso, > rust-shadow-rs, rust-tokei all uploaded to unstable to support both > old and new bindings. > > rust-libgit2-sys, rust-git2, rust-git2-curl uploaded to experimental > rust itself built with the new libgit2 will be uploaded to > experimental later today (covered by the toolchain freeze - should I > file a separate unblock request or is this covered by the issue > here?) > rust-debcargo supporting both variants uploaded to experimental as well (same) > > still open on the rust side: > - rust-sequoia-git (currently being updated for other reasons, > compat change committed to git so that the next upload should > build with either old or new bindings) > - rust-auth-git2 (not maintained by the Rust team) >
Are these still open issues? And, they are the main block for updating libgit2 to 1.9? I have a (low priority) package which is stuck at an older release since the newer version requires new API from libgit2 1.9. I guess it is starting to look like libgit2 1.9 is not going to make it in for the next release. -Jordan
signature.asc
Description: signature
