[meego-packaging] pulseaudio reversion plan
sami.sirkia at cybercom.com
Tue Dec 28 09:02:27 PST 2010
On 12/27/2010 09:07 AM, Zhang, Vivian wrote:
> Hi, all:
> Pulseaudio will be downgraded to 0.9.19 due to integrating patches for policy framework and voice call features. We plan to integrate the new PA package after the holiday (Jan 3) for QA's testing.
> I will do the sanity test before submitting the new package. However, for the owner of packages which requires PA, you'd better do the check beforehand to avoid any potential issues. Here lists the packages (20) which depends on PA.
> * Trunk:Testing : 12
> audiomanager phonon pavucontrol tone-generator libcanberra qt-mobility pulseaudio-modules-meego monitor-call-audio-setting-mid alsa-plugins gst-plugins-good libao SDL
> * Trunk:Netbook : 3
> gnome-media gnome-settings-daemon meego-panel-devices
> * Trunk:Handset : 2
> meego-handset-statusindicators meegotouchcp-bluetooth
> * Trunk:IVI : 3
> hfdialer audio_management speech-dispatcher
> MeeGo-packaging mailing list
> MeeGo-packaging at meego.com
There are a lot of bug fixes in:
Some of them are already integrated into devel:multimedia/pulseaudio.
About integrating (some of) those:
Should we follow the normal process, or could a lighter process be
concidered for them? Waiting for some segfaults to appear _in_MeeGo_,
before submitting an already existing patch for it, sounds inefficient.
Maybe the ones that are purely fixes and contain no new features could
be gathered into one submit, which then describes all the things they
are supposed to fix. I mean without confirming each bug on meego, filing
a bug and going though the usual.
For example, here is a very simple typo fix, that fixes audio input for
resource policy(not yet integrated):
Do we need a bug for it BTW, this not being in T:T yet?
Sami Sirkiä, N900 adaptation.
More information about the MeeGo-packaging