all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: 43797@debbugs.gnu.org
Subject: bug#43797: astromenace does not work
Date: Mon, 5 Oct 2020 13:33:53 +0200	[thread overview]
Message-ID: <CAJ3okZ2p7NN-OYAnBE7a+driGsVf4OB9svwr2XAq364rst2Btw@mail.gmail.com> (raw)
In-Reply-To: <YVcwsVitCl1VRpi7NCuiHRBMoUEqNQjqsPlFEo3C0_Q8kg5fbYnHNuPyH1M6gBD0TI0pAW2FmrTyBUg6GlvMaea8nOOA0_MvMszDhrBJTk0=@protonmail.com>

Dear,

Thank you for the report.

First, there is no substitute; which is often a bad sign.  If Cuirass
wizard reads, is it possible to trigger again the build of
'astromenace'.

<https://data.guix.gnu.org/repository/1/branch/master/package/astromenace/output-history>


On Sun, 4 Oct 2020 at 23:16, Luis Felipe via Bug reports for GNU Guix
<bug-guix@gnu.org> wrote:
>
> Hi, I'm using guix b61e057. Just installed AstroMenace and it does not start. Trying to launch it from a terminal prints the following error:
>
> AstroMenace 1.4.1
> VFS version 190427
> Compiled against SDL version 2.0.12
> Linking against SDL version 2.0.12
> vw_OpenVFS(): Can't find VFS file share/astromenace/gamedata.vfs
> main(): gamedata.vfs file not found or corrupted.

Well, the file 'gamedata.vfs' seems to be a file which needs to be
built (it does not appear in the upstream source).  And I am not sure
this file is compliant with "free" licenses; Debian locates it in
'non-free', for example.

All the best,
simon




  reply	other threads:[~2020-10-05 11:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-04 16:37 bug#43797: astromenace does not work Luis Felipe via Bug reports for GNU Guix
2020-10-05 11:33 ` zimoun [this message]
2020-10-05 11:44   ` Efraim Flashner
2020-10-05 12:03     ` Efraim Flashner
2020-10-05 15:04       ` zimoun
2020-10-05 11:41 ` Efraim Flashner

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

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

  git send-email \
    --in-reply-to=CAJ3okZ2p7NN-OYAnBE7a+driGsVf4OB9svwr2XAq364rst2Btw@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=43797@debbugs.gnu.org \
    --cc=luis.felipe.la@protonmail.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.