Package: release.debian.org Severity: normal User: release.debian....@packages.debian.org Usertags: unblock
Hello, could you please unblock the soprano package? the latest upload workarounds a problem which makes the default installation of virtuoso as standalone server hang. To reproduce the problem you can just do: apt-get install virtuoso-opensource-6.1 while using kde; without the fix the virtuoso postinst script will hang. Thank you.
diff -Nru soprano-2.7.6+dfsg.1/debian/changelog soprano-2.7.6+dfsg.1/debian/changelog --- soprano-2.7.6+dfsg.1/debian/changelog 2012-11-27 22:34:30.000000000 +0100 +++ soprano-2.7.6+dfsg.1/debian/changelog 2013-02-05 11:38:21.000000000 +0100 @@ -1,3 +1,11 @@ +soprano (2.7.6+dfsg.1-3) unstable; urgency=low + + * Team upload. + * Add dont_use_virtuoso_default_port.diff, prevents hangs when installing or + running virtuoso as a standalone server. + + -- José Manuel Santamaría Lema <panfa...@gmail.com> Tue, 05 Feb 2013 11:38:17 +0100 + soprano (2.7.6+dfsg.1-2) unstable; urgency=low * Team upload. diff -Nru soprano-2.7.6+dfsg.1/debian/patches/dont_use_virtuoso_default_port.diff soprano-2.7.6+dfsg.1/debian/patches/dont_use_virtuoso_default_port.diff --- soprano-2.7.6+dfsg.1/debian/patches/dont_use_virtuoso_default_port.diff 1970-01-01 01:00:00.000000000 +0100 +++ soprano-2.7.6+dfsg.1/debian/patches/dont_use_virtuoso_default_port.diff 2013-02-05 16:01:00.000000000 +0100 @@ -0,0 +1,33 @@ +Author: José Manuel Santamaría Lema <panfa...@gmail.com> +Forwarded: https://projects.kde.org/projects/kdesupport/soprano/repository/revisions/3482b5fe +Description: If possible, don't use the default virtuso port (1111) + Soprano launches a Virtuoso server using an unix socket (/tmp/virt_XXXX where + XXXX is the tcp port specified in the configuration file). It tries first with + the /tmp/virt_1111 port if it's availaible, and if it's not, keeps trying with + above ports one by one until it finds an usuable /tmp/virt_XXXX. Starting with + 1111 is a very unfortunate choice, because if you start other virtuoso server + configured to use the same port (note that 1111 is the default), then it would + fail to start. It should fail and return, but currently it hangs. + . + When installing virtuoso-opensource-6.1, the postinst script will try to start + Virtuoso using the default 1111 port in order to change the admin password. So + the problem is the following: since the unix socket /tmp/virt_1111 is + (probably) already being used by the Virtuoso instance started by Soprano, the + Virtuoso instance started by the postinst script would hang (as explained in + the paragraph above), breaking the installation. +--- a/backends/virtuoso/virtuosocontroller.cpp ++++ b/backends/virtuoso/virtuosocontroller.cpp +@@ -56,11 +56,11 @@ namespace { + // } + #ifdef Q_OS_WIN + static QMutex portNumberMutex; +- static quint16 p = 1111; ++ static quint16 p = 1113; + QMutexLocker l(&portNumberMutex); + return p++; + #else +- int p = 1111; ++ int p = 1113; + while ( QFile::exists( QString( "/tmp/virt_%1" ).arg( p ) ) ) { + ++p; + } diff -Nru soprano-2.7.6+dfsg.1/debian/patches/series soprano-2.7.6+dfsg.1/debian/patches/series --- soprano-2.7.6+dfsg.1/debian/patches/series 2012-11-25 15:06:51.000000000 +0100 +++ soprano-2.7.6+dfsg.1/debian/patches/series 2012-12-27 15:32:27.000000000 +0100 @@ -1,3 +1,4 @@ +dont_use_virtuoso_default_port.diff x11_not_required.diff disable_usr_lib_install_rpath.diff doxyfile_generate_tagfile.diff
signature.asc
Description: This is a digitally signed message part.
