unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Fulbert <fulbert@bluewin.ch>
To: 50433@debbugs.gnu.org
Cc: Sarah Morgensen <iskarian@mgsn.dev>
Subject: bug#50433: shotcut 21.06.29 missing bin files
Date: Tue, 7 Sep 2021 14:27:09 +0200	[thread overview]
Message-ID: <YTdanfi2s4UTHiEg@bluewin.ch> (raw)
In-Reply-To: <86h7exi1g8.fsf@mgsn.dev>

Le Mon, Sep 06, 2021 at 07:06:31PM -0700, Sarah Morgensen a écrit :
> Hello,
> 
> Thanks for your report.

Hello and thanks to you,

> I compared this to the release binaries and there really is just the one
> 'shotcut' executable.  I think you're correct that the '127' error is
> due to it not finding an executable, but I think that's happening
> because shotcut got double-wrapped (or wrapped incorrectly).
> 
> Unfortunately I'm not knowledgeable with qt-wrapping so I can't help any
> further, but I hope that helps!

So for a little recap, taking your message into account :

* The first wrapper 'bin/shotcut' does have some 'export' including :
  export MLT_PREFIX="/gnu/store/<>-mlt-7.0.1"
* The second wrapper (called by the first) misses this export and 3
  others (No idea if this "intermediate" wrapper causes any problem.
  Looks harmless to me… which doesnt mean much ^^).
* 'shotcut' depends on 'mlt' and there sits the 'melt-7' binary :
  /gnu/store/<>-mlt-7.0.1/bin/melt-7
* but when using the export function from within shotcut GUI, the
  program calls for 'mlt-7' with the absolute path inside shotcut
  directory : /gnu/store/<>-shotcut-21.06.29/bin/melt-7, where it fails.

regards,
Fulbert




  reply	other threads:[~2021-09-07 12:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-06 16:39 bug#50433: shotcut 21.06.29 missing bin files Fulbert
2021-09-07  2:06 ` Sarah Morgensen
2021-09-07 12:27   ` Fulbert [this message]
2021-11-10  2:07 ` Leo Famulari
2021-11-17  2:43 ` Vinicius Monego
2021-12-27  0: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=YTdanfi2s4UTHiEg@bluewin.ch \
    --to=fulbert@bluewin.ch \
    --cc=50433@debbugs.gnu.org \
    --cc=iskarian@mgsn.dev \
    /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).