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

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

Your message dated Fri, 9 Dec 2022 08:05:33 +0100
with message-id <Y5LePbOM0pyW6vaC@ramacher.at>
and subject line Re: Bug#1021092: transition: libgit2
has caused the Debian Bug report #1021092,
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.)


-- 
1021092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021092
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition

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

Dear release team,

I'd like to transition libgit2 after a SONAME bump.
I've rebuilt most of the reverse dependencies successfully, some
dependencies need special attention though:

python3-pygit2 needs to be updated to be compatible with libgit2 1.5;
as I am the maintainer I got this covered.

ruby-rugged also needs to be updated; I have filed bug #1020632 for
this.

The Rust toolchain looks a bit weird in the Ben tracker at
https://release.debian.org/transitions/html/auto-libgit2.html
and I've had some issues rebuilding stuff following the dependency
levels.


Cheers
Timo


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

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmM4vdoACgkQ+C8H+466
LVkwkwwA732Uf+Y/RX8Haou/QRcSA8kLFnKYANuoPATslY4ak5qbwC6b7JWTpaoj
6KB1oyHsWtOp4+52AHA3AQwEh+Ri5xZ2EkwMkxPgcGaV94YSaOfmFjt8TptXrUX9
WxPFkDAZGkvbKQL7ywzUAlDfQ0jOnEwOXDRL1gEmMtxWh29rBSmdPLYoYgUhQ3aC
Bbjh7fvXMfy1UY04aLdo8oVxkU8SnsRkj/bRygIBI3lAuf+Dr8k2QsKkyREEhmYg
nIlMVezZHXtkjqylxTfjKnE9Jl1aTCZhVn9neVqVz+5rNckiZWOxEwXxbPw4+IYa
mcvUhE4iuNpDZnCHOMYMtW6jJwI9T0vC1j2NIOC0a56OLzhI8U431dd+uA/nNQZk
/ib3y2Inx8c7SRlTJLd26RItEAOwmE5+y0hLXwZQvS4WgTQ0AwWy4nam0kngtZ7x
0C93cO6sqGzDye7I4LldTwLohQcc6AxlKq/EEmfuE/gtWuSBzBh4EJPdsoPHjGKB
XLN1qQj5
=lLrw
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
On 2022-10-02 15:57:21 +0200, Sebastian Ramacher wrote:
> Control: tags -1 confirmed
> Control: forwarded -1 https://release.debian.org/transitions/html/auto-libgit2.html
> 
> On 2022-10-02 00:23:25 +0200, Timo Röhling wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian.org@packages.debian.org
> > Usertags: transition
> > 
> > Dear release team,
> > 
> > I'd like to transition libgit2 after a SONAME bump.
> 
> Please go ahead.
> 
> > I've rebuilt most of the reverse dependencies successfully, some
> > dependencies need special attention though:
> > 
> > python3-pygit2 needs to be updated to be compatible with libgit2 1.5;
> > as I am the maintainer I got this covered.
> > 
> > ruby-rugged also needs to be updated; I have filed bug #1020632 for
> > this.
> > 
> > The Rust toolchain looks a bit weird in the Ben tracker at
> > https://release.debian.org/transitions/html/auto-libgit2.html
> > and I've had some issues rebuilding stuff following the dependency
> > levels.
> 
> As far as I am aware, a new cargo version with all the necessary updates
> for those rust packages is currently being prepared in experimental.
> Those packages will need source uploads anyway.

With cargo finally fixed, the old binaries got removed from testing.
Closing

Cheers
-- 
Sebastian Ramacher

--- End Message ---
Reply to: