From: iyzsong@member.fsf.org (宋文武)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: GStreamer, PulseAudio and libvpx update
Date: Wed, 03 Feb 2016 19:15:11 +0800 [thread overview]
Message-ID: <87io263v0g.fsf@member.fsf.org> (raw)
In-Reply-To: <20160203102522.GA4556@debian.eduroam.u-bordeaux.fr> (Andreas Enge's message of "Wed, 3 Feb 2016 11:25:22 +0100")
Andreas Enge <andreas@enge.fr> writes:
> Hello,
>
> On Wed, Feb 03, 2016 at 12:23:24PM +0800, 宋文武 wrote:
>> In the 'gstreamer-update' branch we have following updates:
>> libvpx -> 1.5.0
>> pulseaudio -> 8.0
>> ao -> 1.2.0
>> gstreamer (and plugins) -> 1.6.3
>
> I noticed you merged master into the branch. My opinion is that merging
> instead of rebasing messes up the history and makes it rather unclear
> what the differences in this branch are. So I would suggest the following:
> Delete the branch, create a branch "wip-gstreamer" from security-updates
> (not master!), try to build a few packages; after security-updates has been
> applied to master, rebase wip-gstreamer and have it built by hydra.
Sure, merge does look weird. Done as you said, thanks for the guide :)
>
> Right now, the priority clearly is to finish security-updates, and we
> cannot afford to build a second branch in parallel.
OK.
>
> Are these four updates independent? Should they all be built together,
> or should we do them one by one? Only 19 packages depend on ao, only 29 on
> libvpx, so these could be done separately. Could they even go to master,
> or do they depend on gstreamer (or pulseaudio) being updated first?
> pulseaudio has 162 dependent packages, so even these could maybe be built
> separately (where by "separately" I mean in a different evaluation).
>
> What do you think?
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...
next prev parent reply other threads:[~2016-02-03 11:15 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 ` 宋文武 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87io263v0g.fsf@member.fsf.org \
--to=iyzsong@member.fsf.org \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.