[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1099677: marked as done (transition: libgit2)



Your message dated Fri, 11 Apr 2025 08:35:20 +0200
with message-id <Z_i4KNDl-BibFI2M@ramacher.at>
and subject line Re: Bug#1099677: transition: libgit2
has caused the Debian Bug report #1099677,
regarding transition: libgit2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1099677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099677
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: libgit2@packages.debian.org, ruby-rugged@packages.debian.org, python-pygit2@packages.debian.org, cargo@packages.debian.org
Control: affects -1 + src:libgit2
User: release.debian.org@packages.debian.org
Usertags: transition

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Dear Release Team,

I would like to transition the latest libgit2 for the trixie release if 
you agree that there is still enough time. In my experience, rebuilding 
rustc and cargo creates the most work for the transition, but the Rust 
Team signaled that they have the capacity to support this.


The Ben tracker looks fine:

https://release.debian.org/transitions/html/auto-libgit2.html


Cheers
Timo



-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEmwPruYMA35fCsSO/zIxr3RQD9MoFAmfJy44ACgkQzIxr3RQD
9MpFgw/+PByBHu0zyukwwlvce1T/tuOsXO1PVkKX7UOVzX/THm48YLEecycsBgkO
PlJgrZnT4wHalo90FOMoGbuuE9jXOGwMHmG28E/79N9lLq/K96+0vu6lRa3ldz5i
2xFDGkNWCMjPzLzBqwevPhQlL1g0/VTU035h9HIlZhqHOrcdcmQ3sv5Sm+2ftVd0
aweo3VRXfV5ggHxXvtl1sRpBHNU284zDsbutK3l7Zs25wq291xpHjD0/xHYmCBKO
ulRcSyxlfj1T7zsLOO4+24IP5/JdN1nhqFK/ZlTOOJfJpvLt+7J7ocSnhXrFnkpw
6ljGs/vTXQiTDLpumMCnupwMO3ZnDJuDjmotN74uFvHRfkDdROHPFX34mJSW37uM
pfBMFDErH/ed8t593IPdy8iM7eGfoeceUj6XTfX2/gfBijTG1A1M58AtUw9/tiL8
Flmf9Iy9Mswqr6OjSWYwV32xqYRpxrGzSmsiSjowOOFy+GucSEVb+bmz7ZVxEEKI
QLccYAdfXISQYywiA7cjbML48NZwlM0/A8gIYdyvENTU4/E2QjpyCozZ++AdYrQZ
OLLrfgASIXMpfyyx+9hx73RLJyVjL1oLYfqpLExMGjL4bTP5PlS3IuZLuscoWFPz
bG/EgLtRgFnfYDqKx9UZZW1uNN3qv/nKGUUvwlE2k03phozpRs8=
=eIos
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message ---
On 2025-04-03 16:42:11 +0200, Sebastian Ramacher wrote:
> Control: tags -1 confirmed
> 
> On 2025-03-28 18:46:05 +0100, Fabian Grünbichler wrote:
> > On Fri, Mar 28, 2025, at 1:48 AM, Jordan Justen wrote:
> > > I guess it is starting to look like libgit2 1.9 is not going to make
> > > it in for the next release.
> > 
> 
> Assuming that the upload of libgit2 and the reverse dependencies happens
> in a timely manner, please go ahead.

The old binaries got removed from testing. Closing.

Cheers
-- 
Sebastian Ramacher

--- End Message ---

Reply to: