From: Felix Lechner via <help-guix@gnu.org>
To: Chris Keschnat <chris@catsu.it>
Cc: GUIX help list <help-guix@gnu.org>
Subject: Re: Conflict with ffmpeg and mpv
Date: Fri, 04 Oct 2024 06:42:34 -0700 [thread overview]
Message-ID: <87ttdsf0hh.fsf@lease-up.com> (raw)
In-Reply-To: <87cykgfci4.fsf@catsu.it> (Chris Keschnat's message of "Fri, 04 Oct 2024 11:22:59 +0200")
Hi Chris,
On Fri, Oct 04 2024, Chris Keschnat wrote:
> guix package: error: profile contains conflicting entries for ffmpeg
> guix package: error: first entry: ffmpeg@7.0.2 [...]
> guix package: error: second entry: ffmpeg@6.1.1 [...]
> guix package: error: ... propagated from mpv@0.38.0
I believe your profile refers to both 'ffmpeg-7' and 'mpv'. The latter
also propagates Ffmpeg but a lower version, namely 6.1.1. [1]
The versions cannot be used together in the same profile. It's a simple
restriction because the /bin/ffmpeg path is already taken.
This is why many of us think that propagated inputs are "evil." Mpv
should instead replace all invocations to Ffpmeg with the actual store
path to the version it requires.
As a solution, I would change "ffmpeg-7"---if that's what you have in
your profile---to "ffmpeg." Alternatively, you could drop Ffmpeg from
your profile and rely on the version propagated by Mpv.
You can still use ffmpeg-7 via 'guix shell' if needed.
Kind regards
Felix
[1] https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/video.scm#n1890
next prev parent reply other threads:[~2024-10-04 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 9:22 Conflict with ffmpeg and mpv Chris Keschnat
2024-10-04 13:42 ` Felix Lechner via [this message]
2024-10-04 15:15 ` Luis Felipe
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=87ttdsf0hh.fsf@lease-up.com \
--to=help-guix@gnu.org \
--cc=chris@catsu.it \
--cc=felix.lechner@lease-up.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.
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).