From: Andreas Enge <andreas@enge.fr>
To: 宋文武 <iyzsong@member.fsf.org>
Cc: guix-devel@gnu.org
Subject: Re: GStreamer, PulseAudio and libvpx update
Date: Wed, 3 Feb 2016 18:43:09 +0100 [thread overview]
Message-ID: <20160203174309.GA14395@debian> (raw)
In-Reply-To: <87io263v0g.fsf@member.fsf.org>
Hello,
On Wed, Feb 03, 2016 at 07:15:11PM +0800, 宋文武 wrote:
> Yes, they're independent. I update gstreamer and add gst-plugins-bad,
> the other are from Efraim Flashner's work. Due to gst-plugins-good
> failed to pass some tests with the update of libvpx and pulseaudio,
> I think put them together may bring some luck.
> well, it seem the test failure of gst-plugins-good is unreleated to
> the update...
thanks for getting back to this! I actually had forgotten to mention that
I would be willing to work on this, sorry.
So far, I tried the following: On x86_64, gst-plugins-good builds without
problem with the new version of ao that Efraim already pushed to master
and the new pulseaudio version. One test fails if I also apply the libvpx
update.
So it looks like we could also update pulseaudio in master; according to
"guix refresh -l" there are 168 dependent packages. Is this too much?
In any case, we should now wait for security-updates to be applied to
master, and probably keep the old version of libvpx until after the
gstreamer update.
Andreas
next prev parent reply other threads:[~2016-02-03 17:43 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 ` 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 [this message]
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=20160203174309.GA14395@debian \
--to=andreas@enge.fr \
--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).