asterisk into unstable

[Mark Purcell]

On Monday 16 February 2009 20:57:16 Tzafrir Cohen wrote:
> So how do we move forward with getting Asterisk into Unstable?
>
> The newer libpri and the DAHDI packages are prerequirements.

Lets upload these first especially as dahdi needs to clear NEW as well.
We are allowed to break unstable at the moment, but we have been asked to 
coordinate soname bumps with debian-release.

Are we going to depreciate bristuff while we work on asterisk 1.6?

> As it has to spend time in the new queue anyway, I wonder if it won't be
> best to go for Asterisk 1.6.1 and experiment with the alternative timing
> sources. I guess that even if they don't really work well on 1.6.1, they
> will work well by the time 1.6.2 is released,

asterisk 1.4 is still available so we can work around 1.6 to converge on a 
working solution.

> and hence it may be useful
> to add the following two subpackages:
 [...]
> Both packages will provide "asterisk-timing" and the main asterisk
> package will depend on:
>
>   asterisk-dahdi | asterisk-timing

Sounds like a reasonable break out.

In svn I suppose we should also make asterisk/branches/lenny	and then merge 
asterisk/branches/experimental into trunk.

Mark

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20090216/80189f4d/attachment.pgp