unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 37942@debbugs.gnu.org
Subject: bug#37942: Insufficient environment wrappers
Date: Sun, 27 Oct 2019 19:06:33 +0100	[thread overview]
Message-ID: <87v9sam5au.fsf@nckx> (raw)
In-Reply-To: <018ca52f9498ea0762604dce80ecf31084c95df3.camel@student.tugraz.at>

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

Leo,

Leo Prikler 写道:
> Some packages -- such as meld after the startup fix -- fail to 
> use
> important resources when simply called from their build 
> directory.

This is… true, and has been a source of personal annoyance for 
years :-)

As it is, this bug report is a bit vague, almost a meta-bug (‘many 
packages have bugs’).  Because *many* packages have this problem, 
for different reasons.  Most instances are pretty easy to fix once 
you find out the exact problem, but there's no one-size-fits-all 
solution.

Do you have any ideas to make it more actionable?

> For instance, meld aborts inside a call to `g_log` by
> `g_settings_set_property`. In the case of meld, it is sufficient 
> to run
> the program inside an ad-hoc environment -- other packages may 
> require
> to be installed in the user profile.

I fixed this specific example in 
3a428dd63af0bec23861a8ed1c76665e8f424265.

Thanks for the report!

T G-R

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

  reply	other threads:[~2019-10-27 18:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-27 11:11 bug#37942: Insufficient environment wrappers Leo Prikler
2019-10-27 18:06 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2021-05-11 15:19 ` Leo Prikler

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=87v9sam5au.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=37942@debbugs.gnu.org \
    --cc=leo.prikler@student.tugraz.at \
    --cc=me@tobias.gr \
    /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).