Bug#670756: Tuxguitar does not start
On 05/15/2012 09:40 AM, Jakub Adam wrote: On 15.5.2012 07:52, Niels Thykier wrote: 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. Sorry, I was wrong with my statement. I thought libswt-cairo-gtk-3555.so was for some reason not built in swt-gtk 3.5, but I missed it is packaged separately in libswt-cairo-gtk-3.5-jni. 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-jninone [...] un libswt-gnome-gtk-3.6-jninone [...] [...] 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. I'd like to note that even the most recent libswt-gtk-3-java doesn't have a strong dependency on all its -jni packages. For example libswt-cairo-gtk-3-jni is neither a dependency nor a suggestion in any other package created from swt-gtk (except -gcj which is not relevant in this case I suppose). If it was meant to be changed in the past, presumably it wasn't done. I don't think this is something wrong, as it allows to install only what is really needed, as long as applications list all the -jni packages they require. Tuxguitar does this, but only for libswt-gtk-3-java and doesn't expect that any alternative can be present, therefore it may crash. So I think we would have to change its Depends to something like: Depends: libswt-gtk-3-java | libswt-gtk-3.5-java, libswt-cairo-gtk-3-jni | libswt-cairo-gtk-3.5-jni, ... etc ... or get rid of the alternatives. That change to depends won't have the desired effect. All that expresses is either libswt-gtk-3-java or libswt-gtk-3.5-java or both which is what we are trying to avoid. I believe you want to express an exclusive (XOR) in there - one or other, but not both. When you say get rid of the alternatives, I'm not sure what you mean. Tuxguitar only lists the following swt dependencies: libswt-gtk-3-java, libswt-cairo-gtk-3-jni, and libswt-webkit-gtk-3-jni. It sounds like we might be back to conflicting with libswt-gtk-3.5-java. In any event, I'm still able to run tuxguitar on sid with both 3.5 and 3 packages installed, so I'm not convinced we've ironed out the precise cause of the bug. Regards, tony signature.asc Description: OpenPGP digital signature __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#670756: Tuxguitar does not start
Hi Tony, On 16.5.2012 17:01, tony mancill wrote: In any event, I'm still able to run tuxguitar on sid with both 3.5 and 3 packages installed, so I'm not convinced we've ironed out the precise cause of the bug. Ok, I will try to describe it more thoroughly: The direct cause of crash is that required JNI library libswt-cairo-gtk-3555.so (from package libswt-cairo-gtk-3.5-jni) is not installed when it has to be. On a clean system where neither SWT nor tuxguitar is installed we can get into this situation with following sequence of events: (1) Install tuxguitar: $ apt-get install tuxguitar Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libswt-cairo-gtk-3-jni libswt-gtk-3-java Suggested packages: libswt-gtk-3-java-gcj tuxguitar-jsa lilypond Recommended packages: tuxguitar-alsa tuxguitar-oss The following NEW packages will be installed: libswt-cairo-gtk-3-jni libswt-gtk-3-java tuxguitar 0 upgraded, 3 newly installed, 0 to remove and 15 not upgraded. ... Setting up libswt-gtk-3-java (3.7.2-2) ... update-alternatives: using /usr/share/java/swt-gtk-3.7.jar to provide /usr/share/java/swt.jar (swt.jar) in auto mode. ... Now we have libswt-gtk-3-java, libswt-cairo-gtk-3-jni and /usr/share/java/swt.jar is provided by swt-gtk-3.7.jar. So far good, we can successfully launch tuxguitar and it will use SWT 3.7 (2) Now let's add libswt-gtk-3.5-java to the installation $ apt-get install libswt-gtk-3.5-java Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libswt-gtk-3.5-jni Suggested packages: libswt-gtk-3.5-java-gcj libswt-gnome-gtk-3.5-jni The following NEW packages will be installed: libswt-gtk-3.5-java libswt-gtk-3.5-jni 0 upgraded, 2 newly installed, 0 to remove and 15 not upgraded. ... We have libswt-gtk-3.5-java installed, *BUT NOT* libswt-cairo-gtk-3.5-jni and /usr/share/java/swt.jar is symlinked to swt-gtk-3.5.1.jar. When you now try to start tuxguitar, it will use SWT 3.5 and crashes with exception we already know from Grant: Exception in thread main org.eclipse.swt.SWTException: Unable to load graphics library [Cairo is required] (java.lang.UnsatisfiedLinkError: no swt-cairo-gtk-3555 or swt-cairo-gtk in swt.library.path, java.library.path or the jar file) (3) To fix this, we can manually install libswt-cairo-gtk-3.5-jni. Then tuxguitar finally runs also with SWT 3.5 - this is most probably your (Tony's) situation, when you have both SWTs and application is working: ||/ NameVersion Description +++-===-===- ii libswt-cairo-gtk-3-jni 3.7.2-2 Standard Widget Toolkit for GTK+ Cairo JNI library ii libswt-cairo-gtk-3.5-jni3.5.1-2.1 Standard Widget Toolkit for GTK+ Cairo JNI library un libswt-gnome-gtk-3-jni none (no description available) un libswt-gnome-gtk-3.5-jninone (no description available) ii libswt-gtk-3-java 3.7.2-2 Standard Widget Toolkit for GTK+ Java library un libswt-gtk-3-java-gcj none (no description available) ii libswt-gtk-3-jni3.7.2-2 Standard Widget Toolkit for GTK+ JNI library ii libswt-gtk-3.5-java 3.5.1-2.1 Standard Widget Toolkit for GTK+ Java library un libswt-gtk-3.5-java-gcj none (no description available) ii libswt-gtk-3.5-jni 3.5.1-2.1 Standard Widget Toolkit for GTK+ JNI library ii libswt-webkit-gtk-3-jni 3.7.2-2 Standard Widget Toolkit for GTK+ WebKit JNI library It's that tuxguitar sometimes needs libswt-cairo-gtk-3.5-jni, but it's not depending on it in any way. Do you see where is the problem now or did I confuse you even more? :) So I think we would have to change its Depends to something like: Depends: libswt-gtk-3-java | libswt-gtk-3.5-java, libswt-cairo-gtk-3-jni | libswt-cairo-gtk-3.5-jni, ... etc That change to depends won't have the desired effect. All that expresses is either libswt-gtk-3-java or libswt-gtk-3.5-java or both which is what we are trying to avoid. I believe you want to express an exclusive (XOR) in there - one or other, but not both. You are right, my change is not sufficient. XOR might work, but I'm not sure if this can be expressed in Depends. When you say get rid of the alternatives, I'm not sure what you mean. Tuxguitar only lists the following swt dependencies: libswt-gtk-3-java, libswt-cairo-gtk-3-jni, and libswt-webkit-gtk-3-jni. It sounds like we might be back to conflicting with
Bug#670756: Tuxguitar does not start
On 15.5.2012 07:52, Niels Thykier wrote: 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. Sorry, I was wrong with my statement. I thought libswt-cairo-gtk-3555.so was for some reason not built in swt-gtk 3.5, but I missed it is packaged separately in libswt-cairo-gtk-3.5-jni. 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-jninone [...] un libswt-gnome-gtk-3.6-jninone [...] [...] 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. I'd like to note that even the most recent libswt-gtk-3-java doesn't have a strong dependency on all its -jni packages. For example libswt-cairo-gtk-3-jni is neither a dependency nor a suggestion in any other package created from swt-gtk (except -gcj which is not relevant in this case I suppose). If it was meant to be changed in the past, presumably it wasn't done. I don't think this is something wrong, as it allows to install only what is really needed, as long as applications list all the -jni packages they require. Tuxguitar does this, but only for libswt-gtk-3-java and doesn't expect that any alternative can be present, therefore it may crash. So I think we would have to change its Depends to something like: Depends: libswt-gtk-3-java | libswt-gtk-3.5-java, libswt-cairo-gtk-3-jni | libswt-cairo-gtk-3.5-jni, ... etc ... or get rid of the alternatives. 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 support this __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#670756: Tuxguitar does not start
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). On 14.5.2012 06:08, Grant Diffey wrote: so my installed package list is nevyn@cetacea:~$ dpkg -l libswt* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Description +++-===-===-== ii libswt-cairo-gtk-3-jni 3.7.2-2 Standard Widget Toolkit for GTK+ Cairo JNI library ii libswt-glx-gtk-3-jni3.7.2-2 Standard Widget Toolkit for GTK+ GLX JNI library ii libswt-gnome-gtk-3-jni 3.7.2-2 Standard Widget Toolkit for GTK+ GNOME JNI library un libswt-gnome-gtk-3.5-jni none (no description available) un libswt-gnome-gtk-3.6-jni none (no description available) ii libswt-gtk-3-java 3.7.2-2 Standard Widget Toolkit for GTK+ Java library un libswt-gtk-3-java-gcj none (no description available) ii libswt-gtk-3-jni3.7.2-2 Standard Widget Toolkit for GTK+ JNI library un libswt-gtk-3.4-java none (no description available) un libswt-gtk-3.4-jni none (no description available) ii libswt-gtk-3.5-java 3.5.1-5 Standard Widget Toolkit for GTK+ Java library un libswt-gtk-3.5-java-gcj none (no description available) ii libswt-gtk-3.5-jni 3.5.1-5 Standard Widget Toolkit for GTK+ JNI library ii libswt-gtk-3.6-java 3.6.2-1 Standard Widget Toolkit for GTK+ Java library un libswt-gtk-3.6-java-gcj none (no description available) ii libswt-gtk-3.6-jni 3.6.2-1 Standard Widget Toolkit for GTK+ JNI library ii libswt-webkit-gtk-3-jni 3.7.2-2 Standard Widget Toolkit for GTK+ WebKit JNI library un libswt3.2-gtk-gcj none (no description available) un libswt3.2-gtk-java none (no description available) un libswt3.2-gtk-jni none (no description available) so yes ii libswt-gtk-3.5-jni 3.5.1-5 Standard Widget Toolkit for GTK+ JNI library is installed. if this breaks with the new version of libswt-3-gtk-java should it not conflict? __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#670756: Tuxguitar does not start
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 signature.asc Description: OpenPGP digital signature __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#670756: Tuxguitar does not start
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-jninone [...] un libswt-gnome-gtk-3.6-jninone [...] [...] 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. ~Niels __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#670756: Tuxguitar does not start
On 2012-04-29 12:38, Jakub Adam wrote: Hi Grant, from the fact that SWT is looking for swt-cairo-gtk-3555 I suspect you have still libswt-gtk-3.5-java and libswt-gtk-3.5-java-jni installed. Removing these packages should solve the problem. Regards, Jakub __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions. Hi Grant, I am not sure if you saw the mail above[1], but could you please confirm whether the above is true? ~Niels [1] As far as I can tell, you were not CC'ed and the BTS does not send follow ups to reporters by default. __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#670756: Tuxguitar does not start
so my installed package list is nevyn@cetacea:~$ dpkg -l libswt* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Description +++-===-===-== ii libswt-cairo-gtk-3-jni 3.7.2-2 Standard Widget Toolkit for GTK+ Cairo JNI library ii libswt-glx-gtk-3-jni3.7.2-2 Standard Widget Toolkit for GTK+ GLX JNI library ii libswt-gnome-gtk-3-jni 3.7.2-2 Standard Widget Toolkit for GTK+ GNOME JNI library un libswt-gnome-gtk-3.5-jninone (no description available) un libswt-gnome-gtk-3.6-jninone (no description available) ii libswt-gtk-3-java 3.7.2-2 Standard Widget Toolkit for GTK+ Java library un libswt-gtk-3-java-gcj none (no description available) ii libswt-gtk-3-jni3.7.2-2 Standard Widget Toolkit for GTK+ JNI library un libswt-gtk-3.4-java none (no description available) un libswt-gtk-3.4-jni none (no description available) ii libswt-gtk-3.5-java 3.5.1-5 Standard Widget Toolkit for GTK+ Java library un libswt-gtk-3.5-java-gcj none (no description available) ii libswt-gtk-3.5-jni 3.5.1-5 Standard Widget Toolkit for GTK+ JNI library ii libswt-gtk-3.6-java 3.6.2-1 Standard Widget Toolkit for GTK+ Java library un libswt-gtk-3.6-java-gcj none (no description available) ii libswt-gtk-3.6-jni 3.6.2-1 Standard Widget Toolkit for GTK+ JNI library ii libswt-webkit-gtk-3-jni 3.7.2-2 Standard Widget Toolkit for GTK+ WebKit JNI library un libswt3.2-gtk-gcj none (no description available) un libswt3.2-gtk-java none (no description available) un libswt3.2-gtk-jni none (no description available) so yes ii libswt-gtk-3.5-jni 3.5.1-5 Standard Widget Toolkit for GTK+ JNI library is installed. if this breaks with the new version of libswt-3-gtk-java should it not conflict? __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#670756: Tuxguitar does not start
Hi Grant, from the fact that SWT is looking for swt-cairo-gtk-3555 I suspect you have still libswt-gtk-3.5-java and libswt-gtk-3.5-java-jni installed. Removing these packages should solve the problem. Regards, Jakub __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
