Re: jack 0.94.0-2

> "rj" == Robert Joerdens <[EMAIL PROTECTED]> writes: >> I ask this because I'd like the differences between Debian and >> DeMuDi package sets to be as few as possible, hopefully nearly >> anything. rj> As someone else already pointed out: that would be "hardly rj> anythin

Re: jack 0.94.0-2

Hello! > rj> From 0.94.0-1 to 0.94.0-2 there are no changes that should > rj> affect applications. > > Ok, now I see. The next upload of the jack package will contain Debian > only changes, so no incompatibility is going to be introduce. > > Are these the only kind of uploads which

Re: jack 0.94.0-2

> Opinions? > Robert, as stated in my previous post, I'd like to keep synchronized DeMuDi with Debian with respect to the jack library. Is there a time line which maintainers of jack dependent packages are supposed to respect when a new version of the jack library is uploaded and all

Re: jack 0.94.0-2

> "rj" == Robert Jordens <[EMAIL PROTECTED]> writes: rj> [1 ] Hello! rj> [Fri, 27 Feb 2004] Free Ekanayaka wrote: >> Given that I don't know this issue in depth, I thought it was >> necessary to rebuild all jack related applications against this >> new release. If I am

Re: jack 0.94.0-2

Hello! [Fri, 27 Feb 2004] Free Ekanayaka wrote: > Given that I don't know this issue indepth, I thought it was > necessary to rebuild all jack related applications against this new > release. If I am wrong, that is no ABI/API changes were introduced and From 0.75.0 (or something like

Re: jack 0.94.0-2

Hello! [Fri, 27 Feb 2004] guenter geiger wrote: > Taking into account that theoretically all applications that support > jack in a given (reasonabley stable) system will support the same > version (ABI-wise), I think we could live with ppl having to update their > whole jack - system, not just a

Re: jack 0.94.0-2

> > I'd like the conflicts added so that only one version of libjack > > can be installed at the same time. > > > And a provides: line so that future version of libjack can > > provides: and conflicts: that virtual package to ensure > > incompatible libjack/jackd combinations aren't installed > >

Re: jack 0.94.0-2

On Fri, 27 Feb 2004, Robert Joerdens wrote: > So if for example hydrogen is removed from testing during a libjack > transition, it can _not_ stay installed anymore and will be removed by apt, > if all libjacks conflict with each other (or depend on a versioned > jackd, what comes out to be the sa

Re: jack 0.94.0-2

> "rj" == Robert Joerdens <[EMAIL PROTECTED]> writes: rj> On Fri, 27 Feb 2004, Free Ekanayaka wrote: >> Robert, as stated in my previous post, I'd like to keep >> synchronized DeMuDi with Debian with respect to the jack >> library. Is there a time line whic

Re: jack 0.94.0-2

On Fri, 27 Feb 2004, Free Ekanayaka wrote: > Robert, as stated in my previous post, I'd like to keep synchronized > DeMuDi with Debian with respect to the jack library. Is there a time > line which maintainers of jack dependent packages are supposed to > respect when a new version of the

Re: jack 0.94.0-2

Hi, > Opinions? I'd like the conflicts added so that only one version of libjack can be installed at the same time. And a provides: line so that future version of libjack can provides: and conflicts: that virtual package to ensure incompatible libjack/jackd combinations aren't installed at the

jack 0.94.0-2

Hello! I'm preparing jack-audio-connection-kit_0.94.0-2. Available from: jack-audio-connection-kit (0.94.0-2) unstable; urgency=low . * debian/control: libjack0.80.0-dev is Section: libdevel * debian/jackd.README.Debian, debian/rules: add a lot of