@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).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864439

Title:
  [MIR] libfido2, libcbor (dependencies of openssh)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcbor/+bug/1864439/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to