>
> As I said: Jack does not get in because that applications that use it
> need the glibc bugs and gcc bugs fixed. So you would have to remove
> _all_ jack applications from testing to let jack in because the ones in
> testing break if the old jack library disappears and the new
> applications break because they need a newer glibc. That wouldn't help.
> You can't force jack in.
I'm rather convinced that there should be a new version.
I'm moving this discussion to multimedia, but I think most of this is
summed up now
[New Version of Jack to hit unstable]
The new version of Jack 0.75 will be uploaded RSN.
They are binary-compatible (modulo bugs).
We won't wait for 0.71.2 to enter testing before uploading, since we
probably need a bit more time before other things like glibc to hit testing,
and applications are requiring bugfixes provided by later jack.
The new version of jack library will be called libjack0.71.2-0
(although it is of version 0.75.0-1)
The upstream is still experimenting with what soname to put for jack,
and they will be putting a different soname to ours.
We shall resync with what the upstream is giving for the soname when they
release jack 1.0.
[Maintainers]
The new maintainer for 'jack' is:
Junichi Uekawa <[EMAIL PROTECTED]>
Robert Jordens <[EMAIL PROTECTED]>
guenter geiger <[EMAIL PROTECTED]>
Instead of one (myself), since jack is an important part of Debian multimedia
that more activity is benefitial.
regards,
junichi
