unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Jason Self <jself@gnu.org>
Cc: 18814@debbugs.gnu.org
Subject: bug#18814: ffmpeg 2.4.2 upgrade broke vlc
Date: Fri, 24 Oct 2014 04:57:23 -0400	[thread overview]
Message-ID: <87siidc0b0.fsf@netris.org> (raw)
In-Reply-To: <E1XgIhE-0000WJ-Vl@vcs.savannah.gnu.org> (Jason Self's message of "Mon, 20 Oct 2014 19:32:49 +0000")

Jason Self <jself@gnu.org> writes:

> commit 7947a05439cc26d93bd93300f38d216dbb93c76d
> Author: Jason Self <j@jxself.org>
> Date:   Mon Oct 20 12:32:42 2014 -0700
>
>     gnu: ffmpeg: Update to 2.4.2.
>     
>     * gnu/packages/video.scm (ffmpeg): Update to version 2.4.2.

This broke the vlc build with the following error:

  checking for AVCODEC... yes
  configure: error: libavcodec versions 56 and later are not supported yet.

See:

  http://hydra.gnu.org/job/gnu/master/vlc-2.1.4.x86_64-linux
  http://hydra.gnu.org/job/gnu/master/vlc-2.1.4.i686-linux

I tried upgrading vlc to the latest release (2.1.5), but it didn't help:

  http://hydra.gnu.org/job/gnu/master/vlc-2.1.5.x86_64-linux
  http://hydra.gnu.org/job/gnu/master/vlc-2.1.5.i686-linux

Two solutions come to mind:

* Add an alternate 'ffmpeg-2.3' package (in addition to 2.4.x) for use
  by vlc.

* Look for upstream vlc patches that fix this problem.

Jason, would you like to look into it?

     Mark

       reply	other threads:[~2014-10-24  8:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1XgIhE-0000WJ-Vl@vcs.savannah.gnu.org>
2014-10-24  8:57 ` Mark H Weaver [this message]
2014-10-26  0:08   ` bug#18814: ffmpeg 2.4.2 upgrade broke vlc Mark H Weaver

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=87siidc0b0.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=18814@debbugs.gnu.org \
    --cc=jself@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.
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).