So there is absolutely no chance that libusb-0.1 will be fixed or replaced with libusb-compat which also means that there is absolutely no support for years now for libusb-0.1 neither from native developers nor canonical?
By the way this bug is only the top of the iceberg caused by deprecated libusb-0.1
So there is absolutely no chance that libusb-0.1 will be fixed or replaced with libusb-compat which also means that there is absolutely no support for years now for libusb-0.1 neither from native developers nor canonical?
By the way this bug is only the top of the iceberg caused by deprecated libusb-0.1