From: Efraim Flashner <efraim@flashner.co.il>
To: 宋文武 <iyzsong@member.fsf.org>
Cc: guix-devel@gnu.org
Subject: Re: gst-plugins-good
Date: Mon, 25 Jan 2016 08:47:18 +0200 [thread overview]
Message-ID: <20160125084718.24edbd9e@debian-netbook> (raw)
In-Reply-To: <87oacfae9a.fsf@member.fsf.org>
[-- Attachment #1: Type: text/plain, Size: 1816 bytes --]
On Thu, 21 Jan 2016 09:54:25 +0800
iyzsong@member.fsf.org (宋文武) wrote:
> 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.
Against my local gstreamer- and gst-plugin-*-1.7.1 I updated libvpx to 1.5.0
and pulseaudio to 8.0 and gst-plugins-good-1.7.1 built with no issues. When I
compiled gst-plugins-good-1.6.3 against libvpx-1.5.0 and pulseaudio-8.0 I got
the same failure as before (which I forgot to write down), so I'm thinking
this will mostly resolve itself when the gstreamer-1.8 release comes out.
As a side note, I think the interaction between debian's pulseaudio and
guix's pulseaudio where I have no sound from my speakers might be solved with
updating guix's pulseaudio to 8.0. Now to leave sound playing for a while and
see if that's the case.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-01-25 6:47 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 ` gst-plugins-good 宋文武
2016-01-21 7:17 ` gst-plugins-good Efraim Flashner
2016-01-25 6:47 ` Efraim Flashner [this message]
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=20160125084718.24edbd9e@debian-netbook \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=iyzsong@member.fsf.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).