Closed uli-heller closed 3 years ago
I got this: https://github.com/Yubico/python-fido2/issues/109
0.9 is not backwards compatible with 0.8. You'll have to open an issue with the python-solo project about updating their code to support 0.9, or to pin the dependency version to 0.8.1.
Any plans for porting to python-fido2 0.9.x? I packaged solo-python for Debian (https://tracker.debian.org/pkg/solo-python) but as python-fido2 was updated to 0.9.1 it's broken at the moment, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985462 :-/
There are no immediate plans on SoloKeys side due to limited dev resources, however @pilou- has announced work being done (https://github.com/solokeys/solo-python/pull/118#issuecomment-797655040).
Is the Debian freeze in effect? I was not aware. If not, is there a realistic timeline? I understand python-fido2 is trying to move to a 1.0 next, at which point we'd revisit at the latest.
Independently, I'd be interested in a chat with you, as the new key will have a Rust CLI that would be great to package - and I don't understand the Debian process for that. I'm @nicolas:solokeys.com
on Matrix and @nickray
on Freenode.
@nickray Sorry for coming back to you so late. Concerning Rust packaging in Debian, I think the Rust Packaging Team is the best starting point: https://wiki.debian.org/Teams/RustPackaging.
Debian is frozen (see https://release.debian.org/bullseye/freeze_policy.html) but bug fixes are still possible - so we would need a patch that just makes the needed changes to work with python-fido2 0.9.x but I fear @pilou- lost interest / doesn't has time to complete his patch (see https://github.com/solokeys/solo-python/pull/118#issuecomment-808721750)
Just a short update: If there is no fix within the next 14 days solo-python will not be part of Debian Bullseye unfortunately :-/ (@nickray @pilou- )
@innir Thanks for the heads-up, I'll try and give it a go.
@innir this update on our side would be much simplified if https://github.com/Yubico/python-fido2/pull/113 got a release in. Is there any chance of that happening? Presumably not since even if upstream releases, it wouldn't be a bugfix?
@nickray I don't think it is possible to get a new version of python-fido2 into Debian Bullseye - as you said, it's not a bugfix but a new release :-/
We're looking into it. This 0.8 to 0.9 update is really totally breaking on the internals, and it's not 1.0 :/ Meanwhile, as ultima ratio... is pipx going to be in Debian Bullseye?
Thanks for your effort! Unfortunately pipx will not be part of Bullseye: https://tracker.debian.org/pkg/python-pipx
@innir Can you check if release 0.0.28 integrates with Debian as expected?
I made a new release, 0.0.28, that uses 0.9.1.
Wow, thanks, that was quick! I tested 0.0.28 (from PyPi) and it works on Debian testing (the to be Bullseye) :-) Great work! To have a chance to get it into Bullseye we now need a patch that just implements the changes for fido2 0.9.1 compatibility on top of 0.0.27. I already tried a little but was not successful :-/ Seems like a lot from client.py got moved to devices/* which makes the patch look huge and seems a little unrelated to the fido2 changes ... The release team is very picky at things like that - they review the whole patches and only want stuff in there that's needed to fix the bug (crashing with fido2 0.9.1). I can understand that's kind of frustrating for you as it's extra work with no clear benefit :-/
@innir: Given it's a leaf package, and the patch isn't easily backportable, you can try asking the release team for a pre-emptive unblock of the new upstream release. Worst case scenario, it doesn't make it into bullseye.
I tried to install on an ubuntu-20.04 box. I'm doing this:
I'm getting this error:
Downgrading to 0.8.1 fixes the issue: