From: John Darrington <john@darrington.wattle.id.au>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add ffmpeg.
Date: Sun, 1 Dec 2013 08:06:26 +0100 [thread overview]
Message-ID: <20131201070625.GB4803@intra> (raw)
In-Reply-To: <20131130204426.GA4174@debian>
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
On Sat, Nov 30, 2013 at 09:44:26PM +0100, Andreas Enge wrote:
On Wed, Nov 27, 2013 at 11:50:54PM +0100, Andreas Enge wrote:
> I just submitted a bug report for the failure on i686:
> https://trac.ffmpeg.org/ticket/3177#no1
Well, it looks as if "make check" is not the preferred way of testing ffmpeg.
Rather, one should download about 750 MB of video samples and run a specific
test program on them (that can be built and run with "make fate"); see the
replies to the bug report.
For Guix, it does not seem to be reasonable to either download 750 MB of
test data, or to package them, so I would suggest to disable the tests
for now.
What do you think?
I think you should phone the mental health department and suggest the ffmpeg
developers be sectioned, on by reason of public safety!
J'
--
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2013-12-01 7:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 22:19 [PATCH] gnu: Add ffmpeg Andreas Enge
2013-11-01 11:38 ` Ludovic Courtès
2013-11-01 13:06 ` Andreas Enge
2013-11-01 23:37 ` Ludovic Courtès
2013-11-02 7:47 ` Andreas Enge
2013-11-27 22:50 ` Andreas Enge
2013-11-30 20:44 ` Andreas Enge
2013-11-30 23:12 ` Ludovic Courtès
2013-12-01 14:51 ` Andreas Enge
2013-12-02 12:38 ` Ludovic Courtès
2013-12-02 17:12 ` Jason Self
2013-12-01 7:06 ` John Darrington [this message]
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=20131201070625.GB4803@intra \
--to=john@darrington.wattle.id.au \
--cc=andreas@enge.fr \
--cc=guix-devel@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).