unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Felix Gruber <felgru@posteo.net>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>,
	51280@debbugs.gnu.org, Efraim Flashner <efraim@flashner.co.il>
Subject: [bug#51280] [PATCH v2 4/5] gnu: openttd-openmsx: Update to 0.4.2.
Date: Sun,  7 Nov 2021 20:06:46 +0000	[thread overview]
Message-ID: <feb3fb5b-79f0-8f3e-74c5-66109ea474c6@posteo.net> (raw)
In-Reply-To: <47c06752fa8cc7376347c3b783ad1ade07d9300d.camel@gmail.com>

Hi Liliana,

On 11/6/21 1:34 PM, Liliana Marie Prikler wrote:
> OpenTTD fails to find this version of opensmx (as opposed to failing to
> play any sound for it, which is the current behaviour on master).  Do
> you have a guess as to why this is the case?

It looks like the script that generates the midi files in openmsx
silently failed after I've replaced the python2 native-input with
python, because the Python scripts in openmsx refer in their #! to
Python as python and not python3. When I instead use the native-input
python-wrapper, the midi files are correctly built and we are back to
the old behaviour with openttd showing the midi tracks but being unable
to play them.

I'll send an updated patch for openmsx.

Best,
Felix




  parent reply	other threads:[~2021-11-07 20:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19  6:58 [bug#51280] [PATCH 0/5] Update openttd to 12.0 Felix Gruber
2021-10-19  7:01 ` [bug#51280] [PATCH 1/5] gnu: openttd-engine: Update " Felix Gruber
2021-10-19  7:01   ` [bug#51280] [PATCH 2/5] gnu: openttd-opengfx: Update to 7.1 Felix Gruber
2021-10-19  7:01   ` [bug#51280] [PATCH 3/5] gnu: openttd-opensfx: Update to 1.0.2 Felix Gruber
2021-10-19  7:02   ` [bug#51280] [PATCH 4/5] gnu: openttd-openmsx: Update to 0.4.2 Felix Gruber
2021-11-03 14:20     ` Efraim Flashner
2021-11-06 10:21       ` Felix Gruber
2021-11-06 10:40       ` [bug#51280] [PATCH v2 0/5] Update openttd to 12.0 Felix Gruber
2021-11-08 20:50         ` bug#51280: " Liliana Marie Prikler
2021-11-06 10:40       ` [bug#51280] [PATCH v2 1/5] gnu: openttd-engine: Update " Felix Gruber
2021-11-06 10:40       ` [bug#51280] [PATCH v2 2/5] gnu: openttd-opengfx: Update to 7.1 Felix Gruber
2021-11-06 10:40       ` [bug#51280] [PATCH v2 3/5] gnu: openttd-opensfx: Update to 1.0.2 Felix Gruber
2021-11-06 10:40       ` [bug#51280] [PATCH v2 4/5] gnu: openttd-openmsx: Update to 0.4.2 Felix Gruber
2021-11-06 12:34         ` Liliana Marie Prikler
2021-11-06 12:34           ` Liliana Marie Prikler
2021-11-07 20:06           ` Felix Gruber [this message]
2021-11-07 20:11             ` [bug#51280] [PATCH v3 " Felix Gruber
2021-11-06 10:40       ` [bug#51280] [PATCH v2 5/5] gnu: openttd: Fix build failure Felix Gruber
2021-10-19  7:02   ` [bug#51280] [PATCH " Felix Gruber

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=feb3fb5b-79f0-8f3e-74c5-66109ea474c6@posteo.net \
    --to=felgru@posteo.net \
    --cc=51280@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    --cc=liliana.prikler@gmail.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 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).