Gentoo Archives: gentoo-dev

From: Zac Medico <zmedico@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] dev-libs/libusbx:1 the default provider for virtual/libusb:1 (for ~arch)
Date: Mon, 28 May 2012 20:51:58
Message-Id: 4FC3E528.8030000@gentoo.org
In Reply to: Re: [gentoo-dev] dev-libs/libusbx:1 the default provider for virtual/libusb:1 (for ~arch) by Pacho Ramos
1 On 05/28/2012 02:02 AM, Pacho Ramos wrote:
2 > El dom, 27-05-2012 a las 17:16 -0700, Zac Medico escribió:
3 >> On 05/27/2012 11:12 AM, Samuli Suominen wrote:
4 >>> Fedora rawhide and ArchLinux switched to libusbx and followed suit in
5 >>> our virtual/libusb:1.
6 >>> Debian is considering the switch also. We'll see...
7 >>>
8 >>> I've been in contact with the new maintainer, and he assured me the
9 >>> compability will be kept for libusb-compat.
10 >>>
11 >>> Happy testing,
12 >>>
13 >>> # emerge -C dev-libs/libusb:1
14 >>> # emerge -1 dev-libs/libusbx:1
15 >>
16 >> I've tried this on my laptop, and afterwards it wouldn't suspend to ram
17 >> when it was supposed to. I didn't do any real troubleshooting, so I'm
18 >> just mentioning it here in case it helps someone else recognize the
19 >> source of the problem. This was with sys-power/upower-0.9.16 and
20 >> dev-libs/libusbx-1.0.11 (I didn't try to rebuild upower after switching
21 >> from dev-libs/libusb-1.0.9 to dev-libs/libusbx-1.0.11).
22 >
23 > Maybe you should open a bug report for it to not forget that problem
24 > (now that finally my laptop suspends even with upstream kernel and
25 > without TOI wouldn't like to see it magically failing again without
26 > remember the real culprit ;))
27
28 I've got it working now. The first time, when I had the suspend to ram
29 issue, I did `emerge -1 dev-libs/libusbx:1` without unmerging libusb:1
30 first. The second time, I unmerged libusb:1 first (like Samuli's
31 instructions said), and since then suspend to ram works fine.
32 --
33 Thanks,
34 Zac