From: Jon Turney <jon.turney@dronecode.org.uk>
To: kaptain.biwouak@gmail.com,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: setup 2.906 release candidate - please test
Date: Thu, 1 Apr 2021 16:53:23 +0100 [thread overview]
Message-ID: <f1104115-5730-14c5-527d-741cfbde9eac@dronecode.org.uk> (raw)
In-Reply-To: <182029171.1352421.1616703758747.JavaMail.administrator@n5.nabble.com>
On 25/03/2021 20:22, kaptain.biwouak@gmail.com wrote:
>>
>> I have tested version 2.906 of setup and I am facing one issue on windows
>> 10:
>
> Thanks for testing.
>
>> I got this message: In order to use libusb0, you must download and rune
>> the LibUSB-Win32 driver from:
>> https://sourceforge.net/projects/libusb-win32/files.../libusb-win32-devel-filter-1.2.6.0.exe
>
> It's unclear if you mean that this message is new with this version of
> setup, or has always been a problem.
>
> This message is correct (and expected) if you are installing libusb0.
>
> (this is the package for the deprecated 0.1 libUSB API, so we shouldn't
> have any packages which require it, but it seems we still have a few...)
>
> Quoted from:
> http://cygwin.1069669.n5.nabble.com/setup-2-906-release-candidate-please-test-tp157282p157374.html
>
> It is new with this version.
> I have never seen this kind of message by the past.
I'm not able to reproduce this problem.
Can you tell me:
- are you using the 32- or 64-bit version of setup 2.906?
- is the libusb0 package installed?
- do you get this message every time you run setup 2.906?
next parent reply other threads:[~2021-04-01 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <182029171.1352421.1616703758747.JavaMail.administrator@n5.nabble.com>
2021-04-01 15:53 ` Jon Turney [this message]
[not found] <822157107.1286425.1616430946694.JavaMail.administrator@n5.nabble.com>
2021-03-25 19:11 ` Jon Turney
2021-03-17 20:02 Jon Turney
2021-03-17 20:08 ` Jon Turney
2021-04-26 12:00 ` Jon Turney
2021-03-17 21:16 ` Thomas Wolff
2021-03-17 21:29 ` Ken Brown
2021-03-21 0:33 ` Brian Inglis
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=f1104115-5730-14c5-527d-741cfbde9eac@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=kaptain.biwouak@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).