Am 22.06.2014 20:55, schrieb Marius Kotsbak:
> 2014-06-19 0:02 GMT+02:00 Michael Biebl :
>
>> Am 14.06.2014 01:28, schrieb Marius Kotsbak:
>>
>>> No, I think it is ready to be uploaded now.
>>>
>>
>> Should I or Guido sponsor the upload?
>>
>> I'm fine with sponsoring the upload. In that case, cou
2014-06-19 0:02 GMT+02:00 Michael Biebl :
> Am 14.06.2014 01:28, schrieb Marius Kotsbak:
>
> > No, I think it is ready to be uploaded now.
> >
>
> Should I or Guido sponsor the upload?
>
> I'm fine with sponsoring the upload. In that case, could you point me to
> a .dsc. I'd be happy to make the u
Am 14.06.2014 01:28, schrieb Marius Kotsbak:
> No, I think it is ready to be uploaded now.
>
Should I or Guido sponsor the upload?
I'm fine with sponsoring the upload. In that case, could you point me to
a .dsc. I'd be happy to make the upload.
Cheers,
Michael
--
Why is it that all of the in
❦ 20 avril 2014 11:38 +0200, Marius Kotsbak :
> Any progres here. I'd be awesome to have an updated package in
> Debian.
>
> I pushed an update now. Will test if qmi-proxy is working. It could
> probably be done by running qmicli when Mobile radio monitor
> (http://sigquit.wordpress.com/
2014-04-13 12:33 GMT+02:00 Guido Günther :
> Hi,
> On Tue, Feb 04, 2014 at 10:21:43AM +0100, Marius Kotsbak wrote:
> > Hi
> >
> > It is actually almost ready in the git repo I have pushed.
>
> Any progres here. I'd be awesome to have an updated package in Debian.
>
I pushed an update now. Will te
Hi,
On Tue, Feb 04, 2014 at 10:21:43AM +0100, Marius Kotsbak wrote:
> Hi
>
> It is actually almost ready in the git repo I have pushed.
Any progres here. I'd be awesome to have an updated package in Debian.
Cheers,
-- Guido
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
On Wed, Feb 12, 2014 at 11:00:52PM +0100, Marius Kotsbak wrote:
[..snip..]
> > I still don't understand why you can't leave it in /usr/lib/?
> >
>
> Done it like that and pushed now. Then it will be up to the user to avoid
> conflicts between different qmi-proxy running at the same time against t
2014-02-11 8:04 GMT+01:00 Guido Günther :
> Hi,
> On Mon, Feb 10, 2014 at 11:36:46PM +0100, Marius B. Kotsbak wrote:
> > On 07. feb. 2014 08:14, Guido Günther wrote:
> > > blocks 737572 731851
> > > thanks
> > >
> > > Hi,
> > > On Tue, Feb 04, 2014 at 10:21:43AM +0100, Marius Kotsbak wrote:
> > >>
Hi,
On Mon, Feb 10, 2014 at 11:36:46PM +0100, Marius B. Kotsbak wrote:
> On 07. feb. 2014 08:14, Guido Günther wrote:
> > blocks 737572 731851
> > thanks
> >
> > Hi,
> > On Tue, Feb 04, 2014 at 10:21:43AM +0100, Marius Kotsbak wrote:
> >> Hi
> >>
> >> It is actually almost ready in the git repo I
On 07. feb. 2014 08:14, Guido Günther wrote:
> blocks 737572 731851
> thanks
>
> Hi,
> On Tue, Feb 04, 2014 at 10:21:43AM +0100, Marius Kotsbak wrote:
>> Hi
>>
>> It is actually almost ready in the git repo I have pushed.
>>
>> The remaining thing is to find out how to handle the qmi-proxy binary,
blocks 737572 731851
thanks
Hi,
On Tue, Feb 04, 2014 at 10:21:43AM +0100, Marius Kotsbak wrote:
> Hi
>
> It is actually almost ready in the git repo I have pushed.
>
> The remaining thing is to find out how to handle the qmi-proxy binary,
> which is used by the lib.
The binary is libexecdir so
On 4 February 2014 21:33, Marius Kotsbak wrote:
> Yes, there are other clients, like qmicli. Okay, and how to ensure
> conflicting between architectures? Stop it being multiarch, or is it a
> better way?
I think for the moment it can be non-multiarch and a bug can be added
for it. I'm not familia
Yes, there are other clients, like qmicli. Okay, and how to ensure
conflicting between architectures? Stop it being multiarch, or is it a
better way?
Hey Marius,
>From my point of view it should conflict - I wasn't aware that it was
used in things other than modemmanager, but that makes sense. I am
hoping to help get a newer version of modemmanager into Debian
eventually.
--Adam
On 4 February 2014 20:21, Marius Kotsbak wrote:
> Hi
>
> It is a
Hi
It is actually almost ready in the git repo I have pushed.
The remaining thing is to find out how to handle the qmi-proxy binary,
which is used by the lib.
As only one can be running at the same time, I am unsure how we should
handle multiarch and different major ABI versions. Either conflict
Package: libqmi-glib-dev
Version: 1.4.0-1
Severity: normal
Hi,
git-buildpackage works fine against upstream 1.8.0 and it will be required for
new modemmanager packages.
How can I help here?
Thanks,
Adam
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500
16 matches
Mail list logo
