I guess it's time to make the final switch since 3rd party apps have started using the debugging facilities which are specific to libusbx -- and every other distribution has already done the switch Please test and stabilize: =dev-libs/libusbx-1.0.17
In fact, please test and stabilize: =dev-libs/libusbx-1.0.17 =dev-libs/libusb-compat-0.1.5-r2 =virtual/libusb-0-r1 =virtual/libusb-1-r1
Stable for HPPA.
alpha stable.
arm stable
ppc64 stable
amd64 stable
Created attachment 367150 [details] full output of emerge command Output from emerge command including std err.
Hi Ross, I'm the libusb upstream maintainer who also tries to help manage the libusbx mess for Gentoo. (In reply to Ross Drummond from comment #7) > Output from emerge command including std err. It looks like you run into this error because there is restructuring of the libusb ebuilds going on with regard to multilib, in a way which isn't backwards compatible and where portage doesn't seem to find the way to resolve the dependencies. Try: emerge =dev-libs/libusb-1.0.9-r2 That should satisfy the new requirement of virtual/libusb-1-r1. I do think that it is completely broken to require only the very latest rev in the virtual. Sad face.
(In reply to Peter Stuge from comment #8) I resolved this block by; removing libusb and virtual/libusb, then installed libusbx, and installed virtual/libusb I then ran revdep-rebuild which reported no errors Peter, thank you for your assistance.
ia64 stable
ppc stable
sparc stable
x86 stable. Closing.