[Pkg-alsa-devel] Bug#483918: alsa-driver 1.0.16

[Elimar Riesebieter]

Hello Jordi,

On Thu, 28 Aug 2008 the mental interface of
Jordi Mallach told:

> Elimar,
> 
> On Thu, Aug 28, 2008 at 08:01:03PM +0200, Elimar Riesebieter wrote:
> > at the moment I am very busy and the bug management is very inertial
> > from my side. Could one please point me on how to create a
> > alsa-driver_1.0.16.dfsg package in a svn lenny branch.? Or could the
> > prepared alsa-driver_1.0.17.dfsg package exist beside the 1.0.16
> > libs and tools? Any help from the _team_ would be *very helpful*!
> 
> Would you foresee any problem with having alsa-source 1.0.17 and alsa-lib
> 1.0.16 in lenny? I don't, and in fact I think having 1.0.17 would be better as
> it would match the ALSA in 2.6.26 (it would actually compile).

ACK

> Furthermore, is there any problem with having kernel 2.6.26 (which includes
> alsa drivers version 1.0.17) and alsa-lib 1.0.16 in lenny as we have now, or
> would it be desirable to have 1.0.17 just to match the kernel version? (I'm
> thinking about configuration file missmatches and so on, mostly).

I didn't recognized any missconf or similar at
CM8738, EMU10k1, ES1371, snd_aoa_codec_tas and intel-amd64.

> Regarding creating a branch, it should be as easy as a cp of trunk to
> branches/lenny using the revision with the last changes to 1.0.16, and I'll be
> able to handle that, don't worry.

If 1.0.17.dfsg, do we really need a lenny branch? Let's distribute
as usual ;)

> 
> Sorry for the lack of action, I'm also quite a bit busy and regret that need to
> be pinged by you constantly to take action. :/

Thanks.

> Depending on what you think about these questions, I'll do something or the
> other.

I'll extend the prepared 1.0.17.dfsg with some more fixes tommorow.
Let us upload alsa-driver 1.0.17 to sid then.

HANN
Elimar

-- 
    .~.
    /V\   L   I   N   U   X
   /( )\ >Phear the Penguin<
   ^^-^^