Russell Sim: > [..] > > Thank you for the in depth description it was very helpful. I was thinking > the same, but just wanted to clarify. > > I have tried to upload a new version, but was blocked because of the same > FTP ACL as before. I think I should probably look at beginning the DD > process. In the meantime it would be great if you could sponsor my upload > I have pushed it to git [0]. > > 0. https://anonscm.debian.org/cgit/collab-maint/libgit2.git/ >
In d/changelog you said this is for unstable, but since other packages in Debian still link against libgit2 0.24 I think we are supposed to do a transition: https://wiki.debian.org/Teams/ReleaseTeam/Transitions which means I should upload this to experimental first. However I also notice you already did that previously - did you also already check that the reverse dependencies also build correctly against 0.25? i.e. these packages: $ echo $(aptitude search --disable-columns -F "%p" '~Dlibgit2-24 ~rnative !~e^libgit2$') eeshow fritzing geany-plugin-git-changebar gnome-builder gnuastro kate kup-backup libgit2-glib-1.0-0 libgnuastro1 libgnuastro2 libkf5texteditor5 lua-gall python-pygit2 python3-pygit2 ruby-rugged If you did the check already, we might be able to upload directly to unstable, otherwise I think we are supposed to upload to experimental first and go through the process listed in the "Transitions" page I linked. This somewhat lengthy process, is also why I suggested to just package 0.26 directly and skip 0.25. Sorry, perhaps I should have explained it earlier. (I am fairly new to this process as well, despite me being a DD for several years I have not maintained a library package myself, that needs these sorts of rebuilds.) X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git
