Bug#670756: Tuxguitar does not start

Niels Thykier niels at thykier.net
Tue May 15 05:52:46 UTC 2012

On 2012-05-15 06:38, tony mancill wrote:
> On 05/14/2012 08:18 AM, Jakub Adam wrote:
>> In my opinion libswt-gtk-3.5-java and libswt-3-gtk-java are not in
>> conflict,
>> generally it's ok to have them installed both. The problem is in tuxguitar
>> package itself which will not work with SWT 3.5.
>> So I suggest that we make tuxguitar to conflict with libswt-gtk-3.5-java
>> (and maybe also with libswt-gtk-3.4-java and libswt-gtk-3.6-java I see
>> in Grant's package list too).
> Hi Jakub,
> There are times in the past when tuxguitar explicitly depended on
> libswt-gtk-3.5-jar, so it seems odd to say that tuxguitar won't work
> with it.  What seems to be the case is that tuxguitar won't work when
> both -3.5 and -3 packages are install.
> Could it be due to the version of libswt-gtk-3-java that was used when
> the tuxguitar binary was built?  (That is, should it be a versioned
> dependency on libswt-gtk-3-java?)  Also, I'm able to install both
> libswt-gtk-3.5-java and libswt-3-gtk-java in a clean chroot and still
> run tuxguitar without a problem.  In any event, I'm not trying to
> contradict your assertion; merely understand it.
> Cheers,
> tony

I believe that swt uses alternatives for the swt.jar, so if you have an
older version of libswt-*-java providing the alternative without (all)
the relevant -jni package => "boom".  Now that should not be possible to
do, but it is...

un  libswt-gnome-gtk-3.5-jni        <none>  [...]
un  libswt-gnome-gtk-3.6-jni        <none>  [...]
ii  libswt-gtk-3.5-java             3.5.1-5 [...]
ii  libswt-gtk-3.6-java             3.6.2-1 [...]

Presumably the dependency relations on the old -jni packages (or on the
old -java packages) are not strong enough.

Personally, I think the swt alternatives is... "weird" at best.  So I
would vote for breaking the old packages to force their removal and then
remove the usage of alternatives in Wheezy+1.
  I think the original idea was to allow co-installation of two
(API/ABI) incompatiable swt jars to smoothing transitions - however they
are not going to enabled at the same time, so we would end up breaking
some programs during a transition anyway.


More information about the pkg-java-maintainers mailing list