[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Packaging Jami progress
From: |
Jan |
Subject: |
Re: Packaging Jami progress |
Date: |
Sat, 28 Dec 2019 12:57:45 +0100 |
On Sat, 28 Dec 2019 10:40:09 +0100
Pierre Neidhardt <address@hidden> wrote:
> This is indeed your problem, I suspect that something broke the
> wrapper somehow.
> Can you share your patch set again? I can have a look.
I didn't really break anything - it works when launching Jami normally
or using the ring.cx script or the jami-gnome script manually. ring.cx
starts both the daemon and the client using "jami-gnome", jami-gnome is
also a script, which exports the path and then starts
".jami-gnome-real". Jami works during normal use, but I couldn't debug
like this, because by passing only ".jami-gnome-real" which is a
binary, to gdb, the needed path wasn't exported.
> P.S.: Have you managed to set up a public Git clone of Guix to share
> you patches?
>
Not yet, but can try today.
Jan Wielkiewicz
- Re: Packaging Jami progress, (continued)
- Re: Packaging Jami progress, Jan Wielkiewicz, 2019/12/15
- Re: Packaging Jami progress, Jan Wielkiewicz, 2019/12/21
- Re: Packaging Jami progress, Ricardo Wurmus, 2019/12/22
- Re: Packaging Jami progress, Jan, 2019/12/23
- Re: Packaging Jami progress, Jan, 2019/12/24
- Re: Packaging Jami progress, Efraim Flashner, 2019/12/25
- Re: Packaging Jami progress, Jan Wielkiewicz, 2019/12/27
- Re: Packaging Jami progress, Gábor Boskovits, 2019/12/27
- Re: Packaging Jami progress, Jan Wielkiewicz, 2019/12/27
- Re: Packaging Jami progress, Pierre Neidhardt, 2019/12/28
- Re: Packaging Jami progress,
Jan <=
- Re: Packaging Jami progress, Jan Wielkiewicz, 2019/12/28
- Re: Packaging Jami progress, Pierre Neidhardt, 2019/12/28
- Re: Packaging Jami progress, Jan, 2019/12/28
Re: Packaging Jami progress, Jan Wielkiewicz, 2019/12/15