Re: GStreamer, PulseAudio and libvpx update

[iyzsong@member.fsf.org (宋文武)]

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...