unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Leo Famulari <leo@famulari.name>, Vinicius Monego <monego@posteo.net>
Cc: 46669@debbugs.gnu.org
Subject: bug#46669: Godot fails to start
Date: Sun, 21 Feb 2021 10:05:53 +0100	[thread overview]
Message-ID: <30e0568aea1af4e8f01b13259c5befe836c5db65.camel@telenet.be> (raw)
In-Reply-To: <YDGrS5qYOlg641pX@jasmine.lan>

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

Hi,

On Sat, 2021-02-20 at 19:37 -0500, Leo Famulari wrote:
> [...]
> It will be while before libx11 is updated in Guix, because changing it
> causes a huge number of packages to be rebuilt:
> 
> $ guix refresh --list-dependent libx11
> Building the following 5793 packages would ensure 12459 dependent packages are rebuilt:
> 
> Is there anything we can change in godot, in the meantime?

Is there any reason the ("libx11" ,libx11) cannot simply be replaced with
("libx11" ,libx11-fixed) in the package inputs for godot, where libx11 is
the updated libx11?  Or alternatively, could the ‘grafts’ mechanism be used?
Or is that reserved for security updates?

Commenting out the line in
  https://github.com/godotengine/godot/issues/40966#issuecomment-667686370
might also work.

Greetings,
Maxime

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2021-02-21  9:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-20 23:35 bug#46669: Godot fails to start Vinicius Monego
2021-02-21  0:37 ` Leo Famulari
2021-02-21  9:05   ` Maxime Devos [this message]
2021-02-21 11:07     ` Leo Prikler
2021-02-24 17:03     ` Leo Famulari
2021-02-24 17:47       ` Maxime Devos
2021-02-24 20:02         ` Leo Famulari
2021-03-18 14:10 ` Vinicius Monego

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=30e0568aea1af4e8f01b13259c5befe836c5db65.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=46669@debbugs.gnu.org \
    --cc=leo@famulari.name \
    --cc=monego@posteo.net \
    /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).