From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] dev-libs/libusbx:1 the default provider for virtual/libusb:1 (for ~arch)
Date: Mon, 28 May 2012 13:50:48 -0700 [thread overview]
Message-ID: <4FC3E528.8030000@gentoo.org> (raw)
In-Reply-To: <1338195747.6537.1.camel@belkin4>
On 05/28/2012 02:02 AM, Pacho Ramos wrote:
> El dom, 27-05-2012 a las 17:16 -0700, Zac Medico escribió:
>> On 05/27/2012 11:12 AM, Samuli Suominen wrote:
>>> Fedora rawhide and ArchLinux switched to libusbx and followed suit in
>>> our virtual/libusb:1.
>>> Debian is considering the switch also. We'll see...
>>>
>>> I've been in contact with the new maintainer, and he assured me the
>>> compability will be kept for libusb-compat.
>>>
>>> Happy testing,
>>>
>>> # emerge -C dev-libs/libusb:1
>>> # emerge -1 dev-libs/libusbx:1
>>
>> I've tried this on my laptop, and afterwards it wouldn't suspend to ram
>> when it was supposed to. I didn't do any real troubleshooting, so I'm
>> just mentioning it here in case it helps someone else recognize the
>> source of the problem. This was with sys-power/upower-0.9.16 and
>> dev-libs/libusbx-1.0.11 (I didn't try to rebuild upower after switching
>> from dev-libs/libusb-1.0.9 to dev-libs/libusbx-1.0.11).
>
> Maybe you should open a bug report for it to not forget that problem
> (now that finally my laptop suspends even with upstream kernel and
> without TOI wouldn't like to see it magically failing again without
> remember the real culprit ;))
I've got it working now. The first time, when I had the suspend to ram
issue, I did `emerge -1 dev-libs/libusbx:1` without unmerging libusb:1
first. The second time, I unmerged libusb:1 first (like Samuli's
instructions said), and since then suspend to ram works fine.
--
Thanks,
Zac
next prev parent reply other threads:[~2012-05-28 20:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-27 18:12 [gentoo-dev] dev-libs/libusbx:1 the default provider for virtual/libusb:1 (for ~arch) Samuli Suominen
2012-05-28 0:16 ` Zac Medico
2012-05-28 9:02 ` Pacho Ramos
2012-05-28 20:50 ` Zac Medico [this message]
2012-05-30 21:20 ` Mike Frysinger
2012-05-30 21:41 ` Peter Stuge
2012-05-30 21:56 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FC3E528.8030000@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox