jack for lenny

Free Ekanayaka freee at debian.org
Mon Jan 12 09:14:25 UTC 2009


Hi Reinhard,

|--==> On Mon, 12 Jan 2009 09:59:39 +0100, Reinhard Tartler <siretart at tauware.de> said:

  RT> hi Free,
  RT> I'm wondering what's the best move for jack. In there is a newer version
  RT> in unstable which includes a shlibs bump. This causes a lot of grief in
  RT> packages that build against jack, like xine-libe. Read: the new jack
  RT> prevents them from entering testing via unstable.

  RT> At this point I see 3 approaches:

  RT>  1. ask the release team to migrate the newer version to lenny
  RT>  2. revert the version in unstable to the version in lenny
  RT>  3. stick our heads in the sand and do nothing.

  RT> If we were to vote on this, I'd vote 2>1>3, TBH.

  RT> Could you perhaps state your opinion on this matter?

Even before your latest upload I've tried to go for 1, asking the
release team to migrate jack to lenny. That's something we would
really need because the current version in lenny it's deprecated, and
should not be used, as it behaves bad on many hardware combinations
(I've experienced that myself). See also:

http://jackaudio.org/node/20

"This is an important release, because it fixes all the problems
reported with 0.115.6 and now makes 0.109.2 completely
obsolete. *Nobody* should be using 0.109.2 within a few weeks, and even
that is only to allow for distributions to update."

I exchanged a few mails with some members of the release team, but
didn't get a reply yet to my last one, in which I quote the sentence
above. They are concerned that the new jackd version can possibly
break other packages, but I'm pretty sure it won't, because both the
API and the ABI haven't changed since a long time now, and according
to mine and other people's tests the newer jackd works much better
than the buggy one in lenny.

Ciao!

Free



More information about the pkg-multimedia-maintainers mailing list