unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: iyzsong@member.fsf.org (宋文武)
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: gst-plugins-good
Date: Thu, 21 Jan 2016 09:54:25 +0800	[thread overview]
Message-ID: <87oacfae9a.fsf@member.fsf.org> (raw)
In-Reply-To: <20160120205308.GA8066@debian> (Andreas Enge's message of "Wed, 20 Jan 2016 21:53:08 +0100")

Andreas Enge <andreas@enge.fr> writes:

> On Wed, Jan 20, 2016 at 10:23:20PM +0200, Efraim Flashner wrote:
>> ANYWAY, it turns out gstreamer 1.7.x is an unstable release, and 1.8.x should
>> be coming out "soon". Extremely frusterating to bang my head against this for
>> so long and find out this is why.
>
> Yes, this is why I had decided against updating it in Guix, the test failures
> on non-x86 notwithstanding. I think we should wait for the stable release.
> What do you and others think?
Sure, we should use stable releases of GStreamer, and 1.6.3 is just
comming out.  I'll do the update later.


Sorry I didn't follow the issue.  What break on master due to the update
of libvpx?  Since hydra is busy with core-updates, I think we can work
on a separate branch, and pick it later after core-updates merged.

  parent reply	other threads:[~2016-01-21  1:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-20 20:23 gst-plugins-good Efraim Flashner
2016-01-20 20:53 ` gst-plugins-good Andreas Enge
2016-01-20 20:56   ` gst-plugins-good Andreas Enge
2016-01-21  1:54   ` 宋文武 [this message]
2016-01-21  7:17     ` gst-plugins-good Efraim Flashner
2016-01-25  6:47     ` gst-plugins-good Efraim Flashner
2016-02-03  4:23       ` GStreamer, PulseAudio and libvpx update 宋文武
2016-02-03  8:59         ` Efraim Flashner
2016-02-03 10:25         ` Andreas Enge
2016-02-03 11:07           ` Efraim Flashner
2016-02-03 11:15           ` 宋文武
2016-02-03 17:43             ` Andreas Enge
2016-02-03 19:38               ` Efraim Flashner

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=87oacfae9a.fsf@member.fsf.org \
    --to=iyzsong@member.fsf.org \
    --cc=efraim@flashner.co.il \
    --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).