On വെ, ഒക്ടോ 7 2022 at 01:29:50 വൈകു +02:00:00
+02:00:00, Timo Röhling <roehl...@debian.org> wrote:
Hi,
* Pirate Praveen <prav...@onenetbeyond.org> [2022-10-03 12:06]:
Thanks for working on libgit2 update.
Next time, remember to file bugs against all reverse (build)
dependencies. There was no bug filed against
golang-github-libgit2-git2go (may be others too).
reverse-depends src:libgit2
reverse-depends -b src:libgit2
These two commands can get you the list of reverse (build)
dependencies.
I'm sorry I missed that package; I relied on the transition tracker,
which doesn't really work that well for static linkage.
I usually use salsa.debian.org/ruby-team/meta (build script from there)
which runs autopkgtests for all reverse dependencies and rebuilds all
reverse build dependencies.
I'm not very proficient with Go and its packaging policies, but I
updated golang-github-libgti2-git2go locally to v35, which is
pretty straight-forward, and it builds and passes autopkgtests.
did you mean v34? I can see upstream released 34.0 yesterday
https://github.com/libgit2/git2go/releases/tag/v34.0.0
Just verify the binary package name matches the import path in go.mod.
You can upload it to unstable.
How do you propose we should deal with the old API,
golang-github-libgit2-git2go-v32?
We can request removal of -v32 source package (which does not work
anyway). Going forward, with a constant source package, the removals of
binary packages will happen automatically.
