[SCM] pulseaudio packaging branch, master, updated. debian/4.0-6-9-g303163b

[Sjoerd Simons]

On Wed, 2014-03-26 at 20:19 -0100, Bálint Réczey wrote:
> Hi Sjoerd,
> 
> 
> Thanks for the quick response!
> 2014-03-26 21:57 GMT+01:00 Sjoerd Simons <sjoerd at luon.net>:
> > On Sun, 2014-03-23 at 22:54 +0000, rbalint at users.alioth.debian.org
> >> ff1c626 Move ALSA mixer configuration files under /etc/pulse (Closes: #736708)
> >
> > This really isn't user configuration as such, so imho should _not_ be
> > under /etc/pulse. If you want to take that path pulse should probably be
> > extended to look in /etc/pulse in addition to the current path
> I think this makes them configuration files which should reside under /etc:
> ....
> In order to get 7.1 sound working over HDMI, you must edit files in
> /usr/share/pulseaudio/alsa-mixer/profile-sets.
> ....

I would recommend against editting them in any case. A better solution
is to add a custom profile for your card with the 7.1 channel map and
tell pulse to use that instead of editting a common one.


> I maintain Wireshark as well and do symlinking to /etc. It seems to be
> a pretty standard way of packaging of config files oddly placed by
> upstreams.

In this case, imho it pollutes /etc with files that a user really
shouldn't be editting.


> Since 5.0 has just been released fixing it in upstream would take very
> long time.

Heh, the time it takes to fix something upstream != when a new release
is done though :). We can always carry patches.

> BTW I would like to upload 5.0 to experimental after uploading 4.0-7. :-)

I've just uploaded 5.0 to unstable ;)

> >> ceb5bf1 Exit PA with X session closing when PA is started by the session (Closes: 594001)
> >> 8cf07d5 Use channel 2 for raop sink (Closes: #658733)
> >
> > Unsure about this patch, should get more information about the actual
> > environment (Is raop really meant to just be used with stereo channel,
> > if not you're likely breaking some use-cases).
> I'm not an expert on this, but this may support the change:
> https://xmms2.org/wiki/Technical_note_to_describe_the_Remote_Audio_Access_Protocol_%28RAOP%29_as_used_in_Apple_iTunes_to_stream_music_to_the_Airport_Express_%28ApEx%29.
> ....
> RAOP:
> RAOP uses two channels for streaming music: a control channel which
> uses RTSP and
> a data channel for sending the raw data. Upon startup, iTunes initiates a RTSP
> connection to the Airport on port 5000. This exchange is shown below:
> ....

Channels in the module argument is audio channels (so 2 is stereo
sound.. It's not about network data channels which is something
completely orthogonal ;) 

I left the patch in for the last upload, but sounds like we need to
check with upstream what's going on here. In general i tend to be quite
careful with what patches i apply especially if it's not clear if it's a
good general change rather then fixing one specific users issue (but may
regress others)



-- 
Sjoerd Simons <sjoerd at luon.net>