Bug#1099677: transition: libgit2
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:
>> Hi,
>>
>> * Emilio Pozuelo Monfort <pochu@debian.org> [2025-03-13 16:18]:
>>>How are the API breaks in this release? Did you rebuild the rdeps
>>>against the new version? I'm all for updating libgit2, but only if it
>>>doesn't break half the rdeps.
>> There are three API breaks:
>>
>> 1. the git_email_create_from_diff() function has been deprecated and
>> moved to the git2/deprecated.h header.
>> 2. the git_indexer_new() function has lost one argument.
>> 3. the git2/sys/reflog.h header (which is not part of the public API,
>> but included by the public headers and therefore publicly accessible)
>> has been removed
>>
>> 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)
Reply to: