On Wed, Jun 1, 2016 at 2:48 AM, John Paul Adrian Glaubitz
wrote:
> Control: reopen -1
> Control: severity -1 normal
>
>> Closing because liblo is no longer in sparc, and will not be built again
>> there.
>
> Re-opening because in Debian we don't "fix bugs" by sweeping them under the
> carpet. Als
On Wed, Feb 17, 2016 at 12:34 PM, Felipe Sateler wrote:
> On 17 February 2016 at 12:02, Stephen Sinclair wrote:
>> Thanks very much Felipe, that clarifies things immensely.
>
> :)
>
>>
>> A last question, is there a difference between using this -release
>>
lways seem to be libraries.. god...
:P), thanks.
Steve
On Mon, Feb 15, 2016 at 7:44 PM, Felipe Sateler wrote:
> On 15 February 2016 at 16:38, Stephen Sinclair wrote:
>> On Mon, Feb 15, 2016 at 12:05 PM, Felipe Sateler wrote:
>>> Hi Stephen
>>>
>>> On 10 Februa
On Mon, Feb 15, 2016 at 12:05 PM, Felipe Sateler wrote:
> Hi Stephen
>
> On 10 February 2016 at 14:21, Stephen Sinclair wrote:
>>
>> Hello,
>>
>> I am helping to update RtMidi, a C++ class for cross-platform MIDI
>> support. There is a Debian librtmidi p
Hello,
I am helping to update RtMidi, a C++ class for cross-platform MIDI
support. There is a Debian librtmidi package. Although this is just
a bug-fix release, and is planned to go from 2.1.0 to 2.1.1, we have
added some automake/libtool infrastructure, and a last debate is
whether to properly
On Tue, Sep 3, 2013 at 2:42 AM, Felipe Sateler wrote:
> On Mon, Sep 2, 2013 at 8:16 PM, Felipe Sateler wrote:
>> On Mon, Sep 2, 2013 at 7:33 PM, Felipe Sateler wrote:
>>> Hi liblo devs,
>>>
>>> The python liblo wrapper has a test suite that has uncovered a bug in
>>> liblo.
>>
>> I just tried cu
Thanks for your quick response!
On Thu, Mar 14, 2013 at 2:37 PM, Felipe Sateler wrote:
> On Thu, Mar 14, 2013 at 3:01 PM, Stephen Sinclair wrote:
>> Hello,
>
> Hi Stephen,
>
>>
>> It was suggested I write to this address for questions about packaging
>> li
Hello,
It was suggested I write to this address for questions about packaging
liblo. I am the liblo maintainer, and I'm starting to prepare for a
new upstream release 0.27 of this library. I just wanted to verify a
few things before doing the release.
My goal for this release is to ensure that t
