All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nate Bargmann <n0nb@n0nb.us>
To: debian-hams@lists.debian.org,
	Hamlib Developers <hamlib-developer@lists.sourceforge.net>,
	Linux Hams <linux-hams@vger.kernel.org>,
	Ubuntu Hams Group <ubuntu-hams@lists.launchpad.net>
Subject: Re: Hamlib 3.0 release announcement
Date: Sat, 26 Mar 2016 08:26:03 -0500	[thread overview]
Message-ID: <20160326132603.GL21590@n0nb.us> (raw)
In-Reply-To: <56F683FB.3080702@debian.org>

* On 2016 26 Mar 07:46 -0500, Colin Tuckley wrote:
> On 19/09/15 15:28, Nate Bargmann wrote:
> 
> > The Hamlib Group is pleased to announce the release of Hamlib 3.0.
> 
> <big snip>
> 
> > TODO:
> 
> > Due to the apparent lack of a libusb package for Windows 64 bit, trial
> > builds of the current Hamlib for W64 lack support for the USB backends.
> > The project should transition these backends to the newer libusb 1.0
> > series.  Target: 3.1.
> 
> We have a Debian bug about this:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810423
> 
> Is there any progress?

Yes, the forthcoming 3.1 now uses libusb 1.0.  I just merged the changes
into the master branch this past week.

73, Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140

      reply	other threads:[~2016-03-26 13:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-19 14:28 Hamlib 3.0 release announcement Nate Bargmann
2016-03-26 12:43 ` Colin Tuckley
2016-03-26 13:26   ` Nate Bargmann [this message]

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=20160326132603.GL21590@n0nb.us \
    --to=n0nb@n0nb.us \
    --cc=debian-hams@lists.debian.org \
    --cc=hamlib-developer@lists.sourceforge.net \
    --cc=linux-hams@vger.kernel.org \
    --cc=ubuntu-hams@lists.launchpad.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.