From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:52946) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h8ROO-0007wy-UW for guix-patches@gnu.org; Mon, 25 Mar 2019 11:20:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h8RON-0005tl-8t for guix-patches@gnu.org; Mon, 25 Mar 2019 11:20:04 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:45001) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1h8ROM-0005tW-Kl for guix-patches@gnu.org; Mon, 25 Mar 2019 11:20:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1h8ROM-0001Yo-FF for guix-patches@gnu.org; Mon, 25 Mar 2019 11:20:02 -0400 Subject: [bug#34044] Packaging Jami (ex GNU Ring) Resent-Message-ID: References: <87h8efvx6e.fsf@ambrevar.xyz> <871s3a6cq6.fsf@elephly.net> <87a7hyty0x.fsf@ambrevar.xyz> <87sgvq4ngh.fsf@elephly.net> <877ed1uadt.fsf@ambrevar.xyz> <87va0lseec.fsf@ambrevar.xyz> <87tvg5se8q.fsf@ambrevar.xyz> <87d0mt2wq3.fsf@elephly.net> <87pnqts6ei.fsf@ambrevar.xyz> <877ed12v3s.fsf@elephly.net> <87ef79726z.fsf@ambrevar.xyz> <87d0mt71ab.fsf@ambrevar.xyz> <87h8c1maqm.fsf@dustycloud.org> <87imwg1vfs.fsf@bababa.i-did-not-set--mail-host-address--so-tickle-me> <87r2avcq1d.fsf@bababa.i-did-not-set--mail-host-address--so-tickle-me> From: Christopher Lemmer Webber In-reply-to: <87r2avcq1d.fsf@bababa.i-did-not-set--mail-host-address--so-tickle-me> Date: Mon, 25 Mar 2019 11:19:31 -0400 Message-ID: <87d0mfx9q4.fsf@dustycloud.org> MIME-Version: 1.0 Content-Type: text/plain List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Pierre Neidhardt Cc: 34044@debbugs.gnu.org Pierre Neidhardt writes: > I've reported the issue with the daemon not starting automatically > upstream: > > https://git.jami.net/savoirfairelinux/ring-client-gnome/issues/999 > > Anyways, did anyone have time to test this package? > > I think the package is in good enough shape at this point, I'll probably > merge tomorrow and should there be more issues, the rest of the > community will be able to test and report more easily. > > Cheers! I got it open even though I didn't successfully make a call. My suspicion is that the package works fine and I was hitting some issue I haven't yet debugged. So, it has approval from me!