From: Chris Keschnat <chris@catsu.it>
To: GUIX help list <help-guix@gnu.org>
Subject: Conflict with ffmpeg and mpv
Date: Fri, 04 Oct 2024 11:22:59 +0200 [thread overview]
Message-ID: <87cykgfci4.fsf@catsu.it> (raw)
Hello,
when upgrading a profile containing both mpv and ffmpeg, I get this
error:
#+begin_src sh
guix package: error: profile contains conflicting entries for ffmpeg
guix package: error: first entry: ffmpeg@7.0.2 /gnu/store/xrllv211xv66hcyg19l3p9cd21yi9506-ffmpeg-7.0.2
guix package: error: second entry: ffmpeg@6.1.1 /gnu/store/0i6f7jaxs47yr0qk2l4dsm7ik0ag7w8d-ffmpeg-6.1.1
guix package: error: ... propagated from mpv@0.38.0
hint: Try upgrading both `ffmpeg' and `mpv', or remove one of them from the profile.
#+end_src
This commit looks like it could be responsible, although I think I upgraded after 2024-09-07:
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=1ac27c7a66097cc5a3d445539bd45556a433e062
I am unsure about what the hint wants to tell me, because "upgrading
both" is exactly what I am trying to do.
Thank you
next reply other threads:[~2024-10-04 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 9:22 Chris Keschnat [this message]
2024-10-04 13:42 ` Conflict with ffmpeg and mpv Felix Lechner via
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=87cykgfci4.fsf@catsu.it \
--to=chris@catsu.it \
--cc=help-guix@gnu.org \
/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).