unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: 53591@debbugs.gnu.org
Cc: liliana.prikler@gmail.com
Subject: bug#53591: closed (Re: [PATCH] gnu: audacity: Add fallback to locate ffmpeg via pkg-config.)
Date: Fri, 4 Feb 2022 17:32:30 -0500	[thread overview]
Message-ID: <Yf2pfst+mWfNjECo@jasmine.lan> (raw)
In-Reply-To: <handler.53591.D53591.1643527130607.notifdone@debbugs.gnu.org>

On Sun, Jan 30, 2022 at 07:19:02AM +0000, GNU bug Tracking System wrote:
> From: Liliana Marie Prikler <liliana.prikler@gmail.com>
> Am Samstag, dem 29.01.2022 um 14:53 -0500 schrieb Leo Famulari:
> > Well, this is fantastic Liliana! It works great.
> > 
> > Can you add a comment to 'audacity-ffmpeg-fallback.patch' with a link
> > to <https://issues.guix.gnu.org/53591>?
> Done and pushed.

I'm not sure what happened, but it seems I failed to test this fix
properly.

Audacity still does not keep a reference to FFmpeg, and it cannot
Opus-encoded files (among many other types of encodings):

------
$ git describe
v1.3.0-15695-gba60aede97
$ $(./pre-inst-env guix build --no-grafts audacity) | grep ffmpeg 
$
------

This is the file to test with:

https://dl.espressif.com/dl/audio/ff-16b-2c-44100hz.opus

I've reopened this bug.




  parent reply	other threads:[~2022-02-04 22:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 23:14 bug#53591: Audacity can't find FFmpeg Leo Famulari
2022-01-27 23:43 ` Leo Famulari
2022-01-28  3:21   ` Leo Famulari
2022-01-29 17:54 ` bug#53591: [PATCH] gnu: audacity: Add fallback to locate ffmpeg via pkg-config Liliana Marie Prikler
2022-01-29 19:53   ` Leo Famulari
2022-01-30  7:18     ` Liliana Marie Prikler
     [not found] ` <handler.53591.D53591.1643527130607.notifdone@debbugs.gnu.org>
2022-02-04 22:32   ` Leo Famulari [this message]
2022-02-04 23:49     ` bug#53591: closed (Re: [PATCH] gnu: audacity: Add fallback to locate ffmpeg via pkg-config.) Leo Famulari

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=Yf2pfst+mWfNjECo@jasmine.lan \
    --to=leo@famulari.name \
    --cc=53591@debbugs.gnu.org \
    --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).