X-Debbugs-CC: codehelp@debian.org, jwilk@debian.org, locutusofborg@debian.org Hi, Thanks everyone for the feedback and comments, especially the explanations regarding symbol versionning. Sorry for the time it took to reply in here, DebConf kept me away from my inbox (though I got quite a lot of things done). > what does this mean? do reverse-dependencies needs a rebuild then? No, there was no ABI-incompatible change, and no soname change is required. However, future builds would pickup a dependency on libu2f-host (>= 1.0) if I'm not mistaken. This was done because codehelp (who initially reviewed my patch) told me that the version 0.0 was not valid, and that I may use 1.0. Interestingly, the previous .symbols file was probably not doing the right thing, because it refered to libu2f-host instead of libu2f-host0, and Lintian was complaining that the Debian version number was appearing in those symbols. > Uploading on deferred/1 Thanks for the subsequent fix, Gianfranco. I included it in the Git history. > No, ACKing a NMU is not a blanket permission to do further further > NMUs. And if the maintainers were actually happy with any NMUs > whatsoever, then they could put the package on the lowNMU list, > or orphan the package. For what it's worth, I asked to join the pkg-auth team to take care of those specific packages, and suggested filing RFAs for the other Yubico-related packages if upstream cannot maintain them. Best, nicoo
Attachment:
signature.asc
Description: PGP signature