@Andreas, from reading the upstream discussion it seems they want (until they reach 1.0) to stick with main soname 0 and only bump minor versions within it.
Only once a transition to 1.0 happens it would go to binary package libcbor1 then.
Version 0 comes with no guarantees, that means you don't need a rebuild to pick up a new dependency as it was and will stay libcbor0. But we should do a libfido2-1 rebuild against it in a ppa to ensure it works still - since no guarantees also means "there could be unexpected breakage".
Please reach out to me once you are online, I want to make sure we are on the same page here (not that I misses an important detail in your request or so).
@Andreas, from reading the upstream discussion it seems they want (until they reach 1.0) to stick with main soname 0 and only bump minor versions within it.
That in mind the new build should IMHO look like:
libcbor.so -> libcbor.so.0.6.0
libcbor.so.0 -> libcbor.so.0.6.0
libcbor.so.0.6.0
And the binary package would still be libcbor0
Only once a transition to 1.0 happens it would go to binary package libcbor1 then.
Version 0 comes with no guarantees, that means you don't need a rebuild to pick up a new dependency as it was and will stay libcbor0. But we should do a libfido2-1 rebuild against it in a ppa to ensure it works still - since no guarantees also means "there could be unexpected breakage".
Please reach out to me once you are online, I want to make sure we are on the same page here (not that I misses an important detail in your request or so).