On Fri, 18 May 2018 at 21:18:49 +0530, Pirate Praveen wrote:
> libgit2 0.27 is now available in experimental. Please make sure your package
> is ready for this version by the time we upload this package to unstable in
> one to two weeks.
Have you tried building reverse-dependencies like gitg against the
new libgit2?
How extensive are the API/ABI breaks in the new version of libgit2?
> The severity of this report will be raised to serious once
> libgit2 0.27 is uploaded to unstable.
This is not how transitions work. "This package is involved in
a transition" is not a release-critical bug: packages affected by
transitions are normally rebuilt by binNMUs scheduled by the release
team, which cannot usefully close bugs. You should only open or escalate
release-critical bugs if something is known to be wrong, such as gitg
failing to build from source against the new version of libgit2.
The release team are unlikely to give you a transition slot for uploading
the new libgit version to unstable until/unless you can estimate how much
breakage it will cause and how much effort is involved in fixing it.
Thanks,
smcv
