unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Raghav Gururajan via Guix-patches via <guix-patches@gnu.org>
To: 47274@debbugs.gnu.org
Cc: "Danny Milosavljevic" <dannym@scratchpost.org>,
	"Léo Le Bouter" <lle-bout@zaclys.net>,
	"Maxim Cournoyer" <maxim.cournoyer@gmail.com>
Subject: [bug#47274] Linphone Packages
Date: Mon, 22 Mar 2021 00:59:46 -0400	[thread overview]
Message-ID: <26fe14fd-bd97-44fd-5101-26fe608e2e2a@raghavgururajan.name> (raw)
In-Reply-To: <cf75f6a8-fd76-cb05-0a46-903de3e882f6@raghavgururajan.name>


[-- Attachment #1.1: Type: text/plain, Size: 1304 bytes --]

Hello Guix!

> Fixed it in the attached patch-set. The app works now. \o/

Spoke too soon. :/

New error now.

> Anyway, I think we can do something for the following, w.r.t 
> linphone-desktop:
> [1] Warnings. Fixing them might prevent them to become errors.
> [2] Better solution than symlinks in 'post-install phase. Because 
> linphone-desktop should be able to read files in /lib and /share of 
> *all* of its dependencies. Not just for those we made symlinks for, 
> which is a temporary fix.
> 
> Regarding [1], for one of the warnings, I tried creating symlink 
> "{linphone-desktop}/lib" --> "{liblinphone}/lib", which worked. But is 
> it the correct way?
> Regarding [2], I tried wrapping the program with XDG_DATA_DIRS, but 
> didn't work.

Looks like we need to do something about the [2]. The new error is 
because of that. I can fix this new error with another symlink, but new 
ones will keep happening.

Context:
The old error that I mentioned and fixed in my previous email is, 
"[Error]Core:linphone: Could not load grammar vcard_grammar because the 
file could not be located.".
The new error I am mentioning in this email is, "[Error]Core:linphone: 
Could not load grammar identity_grammar because the file could not be 
located."

Regards,
RG.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2021-03-22  5:00 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-20  4:26 [bug#47274] Linphone Packages Raghav Gururajan via Guix-patches via
2021-03-21  6:13 ` Raghav Gururajan via Guix-patches via
2021-03-22  1:48   ` Raghav Gururajan via Guix-patches via
2021-03-22  4:44     ` Raghav Gururajan via Guix-patches via
2021-03-22  4:59       ` Raghav Gururajan via Guix-patches via [this message]
2021-03-29  4:03         ` Maxim Cournoyer
2021-03-29  6:05           ` Raghav Gururajan via Guix-patches via
2021-03-29 18:38             ` Maxim Cournoyer
2021-03-29 18:47               ` Raghav Gururajan via Guix-patches via
2021-03-24  4:12       ` Maxim Cournoyer
2021-03-25 13:07       ` Maxim Cournoyer
2021-03-29  5:16         ` Raghav Gururajan via Guix-patches via
2021-03-27  2:13       ` Maxim Cournoyer
2021-03-29  5:52         ` Raghav Gururajan via Guix-patches via
2021-03-27  5:05       ` Maxim Cournoyer
2021-03-29  5:53         ` Raghav Gururajan via Guix-patches via
2021-03-27  5:11       ` Maxim Cournoyer
2021-03-28  4:05         ` Raghav Gururajan via Guix-patches via
2021-03-28  4:43           ` Maxim Cournoyer
2021-03-29  6:02             ` Raghav Gururajan via Guix-patches via
2021-03-29  5:53         ` Raghav Gururajan via Guix-patches via
2021-03-28  0:52       ` Maxim Cournoyer
2021-03-29  5:55         ` Raghav Gururajan via Guix-patches via
2021-03-29  5:44       ` bug#47274: " Maxim Cournoyer
2021-03-29  6:13         ` [bug#47274] " Raghav Gururajan via Guix-patches via
2021-03-29 18:39           ` Maxim Cournoyer
2021-03-25  1:55     ` Maxim Cournoyer
2021-03-29  5:13       ` Raghav Gururajan via Guix-patches via
2021-03-28  4:01     ` Maxim Cournoyer
2021-03-29  6:01       ` Raghav Gururajan via Guix-patches via
2021-03-29  5:19     ` Maxim Cournoyer
2021-03-29  6:12       ` Raghav Gururajan via Guix-patches via
2021-03-24  2:25 ` Maxim Cournoyer
2021-03-29  5:07   ` Raghav Gururajan via Guix-patches via

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=26fe14fd-bd97-44fd-5101-26fe608e2e2a@raghavgururajan.name \
    --to=guix-patches@gnu.org \
    --cc=47274@debbugs.gnu.org \
    --cc=dannym@scratchpost.org \
    --cc=lle-bout@zaclys.net \
    --cc=maxim.cournoyer@gmail.com \
    --cc=rg@raghavgururajan.name \
    /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).