unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Christopher Lemmer Webber <cwebber@dustycloud.org>
Cc: 34044@debbugs.gnu.org
Subject: [bug#34044] Packaging Jami (ex GNU Ring)
Date: Mon, 18 Mar 2019 08:41:11 +0100	[thread overview]
Message-ID: <87imwg1vfs.fsf@bababa.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87h8c1maqm.fsf@dustycloud.org>

[-- Attachment #1: Type: text/plain, Size: 1927 bytes --]

Christopher Lemmer Webber <cwebber@dustycloud.org> writes:

> 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?

If you run Gnome or KDE, the daemon should be started for you.
Otherwise, you've got to start it manually:

/gnu/store/...-libring.../lib/dring -dcp

This is a bit involved for the casual user, but arguably this should be
fixed upstream in the ring.cx script: I don't see why you need a desktop
environment to automate this.

> 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?

I had this once but could not reproduce, so I guess it's safe to remove now.

>        ;; 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.

This is still valid, if you look at the LD_LIBRARY_PATH wrapper around gnome-ring.
The thing is, it seems that qtbase is loading it's libraries at runtime
and gets confused between which one to pick as opposed to the libraries
it was linked against.  This doesn't make much sense to me.  I'd like to
understand more what's going on.

The wrappers works, but I'd rather leave the TODO: (or at least the
comment) until this has been properly fixed.

Thanks for testing!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2019-03-18  7:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87h8efvx6e.fsf@ambrevar.xyz>
2019-03-13 15:00 ` [bug#34044] Packaging Jami (ex GNU Ring) Ricardo Wurmus
2019-03-13 18:44   ` Pierre Neidhardt
2019-03-13 18:51     ` Ricardo Wurmus
2019-03-14  8:29       ` Pierre Neidhardt
2019-03-14 14:45         ` Pierre Neidhardt
2019-03-14 14:49           ` Pierre Neidhardt
2019-03-14 17:26             ` Ricardo Wurmus
2019-03-14 17:38               ` Pierre Neidhardt
2019-03-14 17:40                 ` Pierre Neidhardt
2019-03-14 18:00                   ` Ricardo Wurmus
2019-03-14 18:01                 ` Ricardo Wurmus
2019-03-14 18:15                   ` Pierre Neidhardt
2019-03-14 18:34                     ` Pierre Neidhardt
2019-03-17 21:50                       ` Christopher Lemmer Webber
2019-03-18  7:41                         ` Pierre Neidhardt [this message]
2019-03-25  8:32                           ` Pierre Neidhardt
2019-03-25 15:19                             ` Christopher Lemmer Webber
2019-03-26 18:26                               ` Pierre Neidhardt
2019-03-26 18:41                                 ` Ricardo Wurmus
2019-03-27  1:52                                   ` Brett Gilio
2019-03-27  7:45                                     ` Pierre Neidhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87imwg1vfs.fsf@bababa.i-did-not-set--mail-host-address--so-tickle-me \
    --to=mail@ambrevar.xyz \
    --cc=34044@debbugs.gnu.org \
    --cc=cwebber@dustycloud.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).