From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:49133) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h5drh-0002mP-B6 for guix-patches@gnu.org; Sun, 17 Mar 2019 18:02:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h5dgM-0002ke-Gl for guix-patches@gnu.org; Sun, 17 Mar 2019 17:51:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:34298) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1h5dgM-0002kQ-7S for guix-patches@gnu.org; Sun, 17 Mar 2019 17:51:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1h5dgM-0004nr-0G for guix-patches@gnu.org; Sun, 17 Mar 2019 17:51: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> From: Christopher Lemmer Webber In-reply-to: <87d0mt71ab.fsf@ambrevar.xyz> Date: Sun, 17 Mar 2019 17:50:25 -0400 Message-ID: <87h8c1maqm.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 pushed the patch on the wip-ring branch, it seems to work. > Let me know if you think it's read to merge onto master. I've compiled and run this. I was able to install ring-client-gnome and get it up and running (I rebased against git master and it's fine) via `ring.cx`. However, when I run it, it complains that it can't find the daemon and shuts down. Any idea how to run that so I can test further? Also, there's a few TODOs that I'm not sure are still relevant in the ring-client-gnome definition: ;; TODO: Don't prompt for root password on build? ;; TODO: We must wrap ring-client-gnome to use ;; sqlite-with-column-metadata or else it will fail with: ;; ;; /gnu/store/...-qtbase-5.11.2/lib/qt5/plugins/sqldrivers/libqsqlite.so: ;; undefined symbol: sqlite3_column_table_name16 ;; ;; qtbase is built against sqlite-with-column-metadata but somehow ;; ring-client-gnome ends up with both sqlite and ;; sqlite-with-column-metadata as inputs and it seems that ;; libqsqlite.so gets confused. I haven't run into these alleged problems. Are they still a concern?