Re: Futur status of RoarAudio packages

2012-07-06 Thread Neil McGovern
On Fri, Jul 06, 2012 at 02:18:58PM +0200, Philipp Schafft wrote: > I will file RM requests (also for unstable as I don't see how the > situation could be resolved this way) as soon (still wating for the-me > to be back from holidays). If there's no r-depends, and the package is removed from unstab

Re: Futur status of RoarAudio packages

2012-07-06 Thread Philipp Schafft
reflum, On Wed, 2012-06-27 at 10:30 +0100, Neil McGovern wrote: > On Tue, Jun 26, 2012 at 09:06:12PM +0200, Philipp Schafft wrote: > > > I have no preference either way, as long as the package complies with > > > release > > > policy, then it may be included in the release. > > > > > Your an

Re: Futur status of RoarAudio packages

2012-06-27 Thread Neil McGovern
Hi, On Tue, Jun 26, 2012 at 09:06:12PM +0200, Philipp Schafft wrote: > > I have no preference either way, as long as the package complies with > > release > > policy, then it may be included in the release. > > > Your answer isn't very helpfull to me as it is. So I have some > questions: I

Re: Futur status of RoarAudio packages

2012-06-26 Thread Philipp Schafft
reflum, On Fri, 2012-06-15 at 11:23 +0100, Neil McGovern wrote: > Hi, > > On Thu, Jun 14, 2012 at 10:41:42PM +0200, Philipp Schafft wrote: > > I want to ask if the release team decided anything in this direction. > > Does the release team want a useful version of the package in wheezy? > > [...]

Re: Futur status of RoarAudio packages

2012-06-15 Thread Neil McGovern
Hi, On Thu, Jun 14, 2012 at 10:41:42PM +0200, Philipp Schafft wrote: > I want to ask if the release team decided anything in this direction. > Does the release team want a useful version of the package in wheezy? > > I'm not interested in any discussion but a plain offical statement from > the Re

Futur status of RoarAudio packages

2012-06-14 Thread Philipp Schafft
Dear Release Team, Ron Lee recently asked every maintainer with a package depending on one of our libs to remove them. It is not clear to me why he did that. All problem with our packages relevant for the new stable release have been solved (I have only one wishlist ticket left on my QA page). By