On Saturday 06 February 2016 21:03:05 Diederik de Haas wrote:
> On Saturday 06 February 2016 14:35:56 Scott Kitterman wrote:
> > >Maybe the 'issue' is that libindi is the source package name?
> > >Another explanation could be that there is a version 0.9.7-1 for
> > >libindi0b and libindi-dev on hur
On Saturday 06 February 2016 14:35:56 Scott Kitterman wrote:
> >Maybe the 'issue' is that libindi is the source package name?
> >Another explanation could be that there is a version 0.9.7-1 for
> >libindi0b and libindi-dev on hurd-i386.
>
> That would do it. You might want to file a architecture
On February 6, 2016 2:31:02 PM EST, Diederik de Haas
wrote:
>On Fri, 5 Feb 2016 12:23:27 +0100 Maximiliano Curia
>
>wrote:
>> Version: 0.9.8-4
>>
>> On 08/01/16 19:37, Aurelien Jarno wrote:
>> > Package: libindi
>> > Version: 0.9.7-1
>> > Severity: wishlist
>> >
>> > libindi has a build-depen
On Fri, 5 Feb 2016 12:23:27 +0100 Maximiliano Curia
wrote:
> Version: 0.9.8-4
>
> On 08/01/16 19:37, Aurelien Jarno wrote:
> > Package: libindi
> > Version: 0.9.7-1
> > Severity: wishlist
> >
> > libindi has a build-depends on libusb-dev. A few years ago upstream
> > has released a new major ver
Package: libindi
Version: 0.9.7-1
Severity: wishlist
Dear Maintainer,
libindi has a build-depends on libusb-dev. A few years ago upstream
has released a new major version libusb 1.0 with a different API which
aims to fix design deficiencies with USB 2.0 and 3.0 in mind.
The old libusb 0.1 packag
5 matches
Mail list logo