Your message dated Mon, 01 May 2006 11:32:01 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#365562: libjack0.100.0-0: libjack0.100 and 0.80 don't
co-exist, yet many packages depend on 0.80
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: libjack0.100.0-0
Version: 0.100.7-1
Severity: important
Hello,
I'm trying to use the latest verison of jack (including libjack0.100) and so
far things are working fine. However, my package dependencies aren't terribly
happy with me right now and I want to fix it up. I suspect there's a
dependency problem somewhere, so I'm opening up a bug for discussion.
In brief, libjack0.80 and libjack0.100 conflict with any other version of jackd
except theirs. Meanwhile, KDE/stable and other packages depend on libjack0.80.
(Specifically, basket kdelibs4 konq-plugins kpresenter kscreensaver
kwifimanager ladccad libarts1 libbio2jack0 libkonq4 libxxf86vm1 mplayer-586.)
Granted, this isn't exactly jack's fault. However, given the number of
packages that depend on jack, I'm hoping for a jack solution as a starting
point.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (650, 'testing'), (600, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.16.10
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages libjack0.100.0-0 depends on:
ii libasound2 1.0.10-2 ALSA library
ii libc6 2.3.6-7 GNU C Library: Shared libraries
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, 2006-04-30 at 23:37 -0400, Geoff Oakham wrote:
> In brief, libjack0.80 and libjack0.100 conflict with any other version of
> jackd
> except theirs.
That is correct, since there is another hidden API version (apart from
the 0.80.0/0.100.0 between apps and libjack) between jackd and libjack.
To express that API dependency, all I can do is put that conflict to
ensure you will never runn a libjack with a wrong jackd. If you want
coexistence of apps using different libjacks, you have to uninstall
jackd.
> Meanwhile, KDE/stable and other packages depend on libjack0.80.
> (Specifically, basket kdelibs4 konq-plugins kpresenter kscreensaver
> kwifimanager ladccad libarts1 libbio2jack0 libkonq4 libxxf86vm1 mplayer-586.)
You are trying to mix stable and a testing packages. There are no
packages in stable (sarge) that depend on libjack0.100.0-0 and no
packages in testing/unstable that depend on libjack0.80.0-0. Unless you
mix stable and testing you will not see a problem since the 0.80.0-0 ->
0.100.0-0 transition has happened.
> Granted, this isn't exactly jack's fault. However, given the number of
> packages that depend on jack, I'm hoping for a jack solution as a starting
> point.
I (and many others) couldnnt come up with a nicer solution than the one
present.
I think the problem is well-known and pretty much insolvable since you
never won't be able to _use_ apps compiled against different sonames of
libjack at the same time.
Since there is already a bug describing this (tagged wont-fix), I'm
closing this one.
Robert.
--- End Message ---
