jami-project issueshttps://git.jami.net/savoirfairelinux/jami-project/-/issues2018-05-22T00:18:51Zhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/168compression uses too much data2018-05-22T00:18:51ZJami Botcompression uses too much dataIssue generated from Tuleap's migration script.
**Originally submitted by: Adrien Béraud (adrienberaud)**
<p>Zlib compression often leaves trailing zeroes, making the compressed data larger than it should be.</p>Issue generated from Tuleap's migration script.
**Originally submitted by: Adrien Béraud (adrienberaud)**
<p>Zlib compression often leaves trailing zeroes, making the compressed data larger than it should be.</p>Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/167Jenkins 16.04 packaging stuck during configure2018-05-22T00:18:34ZJami BotJenkins 16.04 packaging stuck during configureIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Viau (aviau)**
dpkg configure is asking questions.Issue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Viau (aviau)**
dpkg configure is asking questions.https://git.jami.net/savoirfairelinux/jami-project/-/issues/163Failing packaging jenkins job2018-05-22T00:15:16ZJami BotFailing packaging jenkins jobIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Viau (aviau)**
The new jenkins jobs for Debian packaging failsIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Viau (aviau)**
The new jenkins jobs for Debian packaging failshttps://git.jami.net/savoirfairelinux/jami-project/-/issues/155[ringdht] cannot build on armel architecture2018-05-22T00:07:07ZJami Bot[ringdht] cannot build on armel architectureIssue generated from Tuleap's migration script.
**Originally submitted by: Simon Désaulniers (sim590)**
<p>As explained here:&nbsp;<a href="https://github.com/savoirfairelinux/opendht/issues/87">https://github.com/savoirfairelinux/opend...Issue generated from Tuleap's migration script.
**Originally submitted by: Simon Désaulniers (sim590)**
<p>As explained here: <a href="https://github.com/savoirfairelinux/opendht/issues/87">https://github.com/savoirfairelinux/opendht/issues/87</a> [1], OpenDHT won't build on armel because of the usage of std::future templates. Therefor, Ring cannot build either. A simple fix on OpenDHT's side has been written here: <a href="https://github.com/savoirfairelinux/opendht/issues/89">https://github.com/savoirfairelinux/opendht/issues/89</a> [2] and is waiting for approuval. Ring should then also integrate a fix for armel support. Actually, only writing code according to [2] is straightforward.</p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/154Remove IAX2018-05-22T00:06:07ZJami BotRemove IAXIssue generated from Tuleap's migration script.
**Originally submitted by: Dorina Mosku (dmosku15)**
<p>IAX needs to be removed</p>Issue generated from Tuleap's migration script.
**Originally submitted by: Dorina Mosku (dmosku15)**
<p>IAX needs to be removed</p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/150Linking error when building ring-daemon: /lib64/libz.so.1: error adding symbo...2018-05-22T00:01:19ZJami BotLinking error when building ring-daemon: /lib64/libz.so.1: error adding symbols: DSO missing from command lineIssue generated from Tuleap's migration script.
**Originally submitted by: George Diamantopoulos (gedia)**
<p>Building ring-daemon from master has been failing consistently for me for the past month (can't say about before, this is my f...Issue generated from Tuleap's migration script.
**Originally submitted by: George Diamantopoulos (gedia)**
<p>Building ring-daemon from master has been failing consistently for me for the past month (can't say about before, this is my first attempt). There seems to be a linking problem with libz:</p>
<blockquote>
<p>libtool: link: x86\_64-pc-linux-gnu-g++ -std=gnu++11 -I../src -DDBUS\_API\_SUBJECT\_TO\_CHANGE -I/usr/include/dbus-c++-1 -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I../src/dring -DTOP\_BUILDDIR=\\"/var/tmp/portage/net-voip/ring-daemon-9999/work/ring-daemon-9999\\" -march=broadwell -O2 -pipe -Wl,-O1 -Wl,-Bsymbolic -o dring dring-main.o -Wl,--as-needed dbus/.libs/libclient\_dbus.a /usr/lib64/libdbus-c++-1.so -ldbus-1 ../src/.libs/libring.a -L/usr/lib -lpjsua2-x86\_64-unknown-linux-gnu -lpjsua-x86\_64-unknown-linux-gnu -lpjsip-ua-x86\_64-unknown-linux-gnu -lpjsip-simple-x86\_64-unknown-linux-gnu -lpjsip-x86\_64-unknown-linux-gnu -lpjmedia-codec-x86\_64-unknown-linux-gnu -lpjmedia-videodev-x86\_64-unknown-linux-gnu -lpjmedia-audiodev-x86\_64-unknown-linux-gnu -lpjmedia-x86\_64-unknown-linux-gnu -lpjnath-x86\_64-unknown-linux-gnu -lpjlib-util-x86\_64-unknown-linux-gnu -lsrtp-x86\_64-unknown-linux-gnu -lresample-x86\_64-unknown-linux-gnu -lg7221codec-x86\_64-unknown-linux-gnu -lpj-x86\_64-unknown-linux-gnu -luuid -lrt -lpthread -lSDL2 -lv4l2 -lopus -lasound -lpulse -lsamplerate -lsndfile -lyaml-cpp -ljsoncpp -lgnutls -lpcre -lopendht -lspeexdsp -lavcodec -lavformat -lavdevice -lswscale -lavutil -ldl -ludev -lgsm<br />
/usr/lib/gcc/x86\_64-pc-linux-gnu/5.3.0/../../../../x86\_64-pc-linux-gnu/bin/ld: ../src/.libs/libring.a(libring\_la-archiver.o): undefined reference to symbol 'compressBound@@ZLIB\_1.2.0'<br />
/lib64/libz.so.1: error adding symbols: DSO missing from command line</p>
</blockquote>
<p>I'm attaching the full build log and some environment information. I'm also attaching a patch I had to use in order to make it build with pjsip-2.5, but I think it's unrelated.</p>
[build.log](/uploads/b71f0af633ef05c2882e4dfdb965b91f/build.log)
[emerge-info.txt](/uploads/f6426d5094e379e97b19a98c7306c9dd/emerge-info.txt)
[pjsip25.patch](/uploads/b78458b763f5780f817d333cd8c3e07c/pjsip25.patch)https://git.jami.net/savoirfairelinux/jami-project/-/issues/149daemon: build using speex in contribution are non-reproductible2018-05-21T23:59:25ZJami Botdaemon: build using speex in contribution are non-reproductibleIssue generated from Tuleap's migration script.
**Originally submitted by: Guillaume Roguez (guillaume)**
The rules.mak uses HEAD as git commit-id.
This is not fixed in time and must be changed by a SHA1 or an annoted-tag.Issue generated from Tuleap's migration script.
**Originally submitted by: Guillaume Roguez (guillaume)**
The rules.mak uses HEAD as git commit-id.
This is not fixed in time and must be changed by a SHA1 or an annoted-tag.Guillaume RoguezGuillaume Roguezhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/148ring-project: docs are not properly cleaned2018-05-21T23:54:50ZJami Botring-project: docs are not properly cleanedIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Viau (aviau)**
The clean target uses the sphinx-provided makefile but the build target no longer uses that makefile, so we are not cleaning the right d...Issue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Viau (aviau)**
The clean target uses the sphinx-provided makefile but the build target no longer uses that makefile, so we are not cleaning the right directories.https://git.jami.net/savoirfairelinux/jami-project/-/issues/147SVG on Ring.cx frontpage eats CPU (100%)2018-05-21T23:53:50ZJami BotSVG on Ring.cx frontpage eats CPU (100%)Issue generated from Tuleap's migration script.
**Originally submitted by: Yonas Yanfa (yonas)**
<p>Hi,</p>
<p>The animated SVG on Ring.cx makes my CPU load go to 100% on all 4 cores.</p>
<p>Tested with Chromium 49.0.2623.112 ...Issue generated from Tuleap's migration script.
**Originally submitted by: Yonas Yanfa (yonas)**
<p>Hi,</p>
<p>The animated SVG on Ring.cx makes my CPU load go to 100% on all 4 cores.</p>
<p>Tested with Chromium 49.0.2623.112 (64-bit) and Firefox 46.0.1, on FreeBSD 10.3 and Debain 8.</p>
<p>Cheers,</p>
<p>Yonas</p>Guillaume RoguezGuillaume Roguezhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/146Ring cannot be built with GnuTLS disabled2018-05-21T23:50:59ZJami BotRing cannot be built with GnuTLS disabledIssue generated from Tuleap's migration script.
**Originally submitted by: szotsaki (szotsaki)**
<p>The error message is:</p>
<pre>
[ 64s] configurationmanager.cpp:60:18: error: 'ring::tls::TlsValidator' has not been declared ...Issue generated from Tuleap's migration script.
**Originally submitted by: szotsaki (szotsaki)**
<p>The error message is:</p>
<pre>
[ 64s] configurationmanager.cpp:60:18: error: 'ring::tls::TlsValidator' has not been declared
[ 64s] using ring::tls::TlsValidator;
[ 64s] \^
[ 65s] Makefile:520: recipe for target 'libclient\_la-configurationmanager.lo' failed
[ 65s] make[3]: \*\*\* [libclient\_la-configurationmanager.lo] Error 1
[ 65s] make[3]: Leaving directory '/home/abuild/rpmbuild/BUILD/ring-daemon/src/client'
[ 65s] Makefile:924: recipe for target 'all-recursive' failed
[ 65s] make[2]: \*\*\* [all-recursive] Error 1
[ 65s] make[2]: Leaving directory '/home/abuild/rpmbuild/BUILD/ring-daemon/src'
[ 65s] Makefile:514: recipe for target 'all-recursive' failed
[ 65s] make[1]: \*\*\* [all-recursive] Error 1
[ 65s] make[1]: Leaving directory '/home/abuild/rpmbuild/BUILD/ring-daemon'
[ 65s] Makefile:444: recipe for target 'all' failed
[ 65s] make: \*\*\* [all] Error 2
[ 65s] error: Bad exit status from /var/tmp/rpm-tmp.EjfvZU (%build)</pre>
<p>Please, check the rest usage, too.</p>
<p>Thank you!</p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/145BootstrapModel ouf of sync with HostName2018-05-21T23:49:17ZJami BotBootstrapModel ouf of sync with HostNameIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Viau (aviau)**
When creating an account, the BootstrapModel is out of sync with the HostNameIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Viau (aviau)**
When creating an account, the BootstrapModel is out of sync with the HostNamehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/144Headers include problem in opendht2018-05-21T23:48:00ZJami BotHeaders include problem in opendhtIssue generated from Tuleap's migration script.
**Originally submitted by: Yuri (yurivict)**
<p>utils.h uses&nbsp;<em>sockaddr\_storage</em>&nbsp;which is defined in&nbsp;<em>netinet/in.h&nbsp;</em>but&nbsp;<em>netinet/in.h&nbsp;</em>is...Issue generated from Tuleap's migration script.
**Originally submitted by: Yuri (yurivict)**
<p>utils.h uses <em>sockaddr\_storage</em> which is defined in <em>netinet/in.h </em>but <em>netinet/in.h </em>is only included in <em>include/opendht/value.h. src/utils.cpp </em>includes <em>utils.h </em>without <em>value.h </em>and fails to compile.</p>
<p> </p>
<p>Previous verson didn't have this problem.</p>
<p> </p>
<p>The safest way to solve the problem is to include the needed headers into every header that uses them.</p>
<p> </p>
<p>opendht-0.6.0</p>Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/141dht logs not working in dring2018-05-21T23:45:16ZJami Botdht logs not working in dringIssue generated from Tuleap's migration script.
**Originally submitted by: Adrien Béraud (adrienberaud)**Issue generated from Tuleap's migration script.
**Originally submitted by: Adrien Béraud (adrienberaud)**Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/139daemon: contrib fails to build when path contains dir with spaces2018-05-21T23:40:25ZJami Botdaemon: contrib fails to build when path contains dir with spacesIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>Some or all contrib dependencies will fail to build if the contrib path contains a dir name with a whitespace in it, for exam...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>Some or all contrib dependencies will fail to build if the contrib path contains a dir name with a whitespace in it, for example:</p>
<p> </p>
<pre>
cd gmp && CC="gcc" CXX="g++" LD="ld" AR="ar" CCAS="gcc -c" RANLIB="ranlib" STRIP="strip" PATH="/home/ssalenikovich/projects/test daemon/ring-daemon/contrib/x86\_64-linux-gnu/bin:/home/ssalenikovich/projects/test daemon/ring-daemon/extras/tools/build/bin:/home/ssalenikovich/bin:/usr/lib/ccache:/home/ssalenikovich/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/local/java-oracle/jdk1.7.0\_79/bin" CPPFLAGS=" -I/home/ssalenikovich/projects/test daemon/ring-daemon/contrib/x86\_64-linux-gnu/include -fPIC" CFLAGS=" -I/home/ssalenikovich/projects/test daemon/ring-daemon/contrib/x86\_64-linux-gnu/include -fPIC" CXXFLAGS=" -I/home/ssalenikovich/projects/test daemon/ring-daemon/contrib/x86\_64-linux-gnu/include -fPIC" LDFLAGS=" -L/home/ssalenikovich/projects/test daemon/ring-daemon/contrib/x86\_64-linux-gnu/lib" ./configure --prefix="/home/ssalenikovich/projects/test daemon/ring-daemon/contrib/x86\_64-linux-gnu" --datarootdir="/home/ssalenikovich/projects/test daemon/ring-daemon/contrib/x86\_64-linux-gnu/share" --includedir="/home/ssalenikovich/projects/test daemon/ring-daemon/contrib/x86\_64-linux-gnu/include" --libdir="/home/ssalenikovich/projects/test daemon/ring-daemon/contrib/x86\_64-linux-gnu/lib" --build="x86\_64-linux-gnu" --host="x86\_64-linux-gnu" --target="x86\_64-linux-gnu" --program-prefix="" --disable-dependency-tracking --enable-static --disable-shared --with-pic
configure: WARNING: unrecognized options: --disable-dependency-tracking
checking build system type... x86\_64-pc-linux-gnu
checking host system type... x86\_64-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking ABI=64
checking compiler gcc -I/home/ssalenikovich/projects/test daemon/ring-daemon/contrib/x86\_64-linux-gnu/include -fPIC -I/home/ssalenikovich/projects/test daemon/ring-daemon/contrib/x86\_64-linux-gnu/include -fPIC... no
checking ABI=x32
checking compiler gcc -I/home/ssalenikovich/projects/test daemon/ring-daemon/contrib/x86\_64-linux-gnu/include -fPIC -I/home/ssalenikovich/projects/test daemon/ring-daemon/contrib/x86\_64-linux-gnu/include -fPIC... no
checking ABI=32
checking compiler gcc -I/home/ssalenikovich/projects/test daemon/ring-daemon/contrib/x86\_64-linux-gnu/include -fPIC -I/home/ssalenikovich/projects/test daemon/ring-daemon/contrib/x86\_64-linux-gnu/include -fPIC... no
configure: error: could not find a working compiler, see config.log for details
../../contrib/src/gmp/rules.mak:19: recipe for target '.gmp' failed
make: \*\*\* [.gmp] Error 1
</pre>
<p> </p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/134Some print generate Warning at compile time2018-05-21T23:36:00ZJami BotSome print generate Warning at compile timeIssue generated from Tuleap's migration script.
**Originally submitted by: Edric Milaret (edric)**
<p>uint64\_t is a platform dependant type</p>
<p>On Linux:</p>
<p>32bit: long long unsigned&nbsp;int</p>
<p>64bit: long un...Issue generated from Tuleap's migration script.
**Originally submitted by: Edric Milaret (edric)**
<p>uint64\_t is a platform dependant type</p>
<p>On Linux:</p>
<p>32bit: long long unsigned int</p>
<p>64bit: long unsigned int</p>
<p>On Windows:</p>
<p>32bit & 64bit: long long unsigned int</p>
<p>On OS X: </p>
<p>32bit & 64bit: long long unsigned int</p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/133Contacts added from the gnome client don't have the 'ring:' prefix2018-05-21T23:33:16ZJami BotContacts added from the gnome client don't have the 'ring:' prefixIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Viau (aviau)**
Contacts created from the gnome client don't have the 'ring:' prefix for their phone numbers.
It is best to keep the ring: prefix a...Issue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Viau (aviau)**
Contacts created from the gnome client don't have the 'ring:' prefix for their phone numbers.
It is best to keep the ring: prefix at all times so that we don't have to guess the protocol based on the number of characters. Other protocols could look like ring.https://git.jami.net/savoirfairelinux/jami-project/-/issues/130can't call peer number with zero-width space around number2018-05-21T23:32:08ZJami Botcan't call peer number with zero-width space around numberIssue generated from Tuleap's migration script.
**Originally submitted by: Adrien Béraud (adrienberaud)**
<p>Example case: Andreas fedora number on:</p>
<p>https://wiki.savoirfairelinux.com/wiki/Ring\_contacts</p>
<p>has leadi...Issue generated from Tuleap's migration script.
**Originally submitted by: Adrien Béraud (adrienberaud)**
<p>Example case: Andreas fedora number on:</p>
<p>https://wiki.savoirfairelinux.com/wiki/Ring\_contacts</p>
<p>has leading unicode zero-width spaces.</p>Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/129Document setting up Ring for authentication with a Turn server2018-05-21T23:31:51ZJami BotDocument setting up Ring for authentication with a Turn serverIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Viau (aviau)**
Document the setup of a turn server and ring to authenticate with it.Issue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Viau (aviau)**
Document the setup of a turn server and ring to authenticate with it.https://git.jami.net/savoirfairelinux/jami-project/-/issues/128ring-daemon build instructions don't work2018-05-21T23:31:33ZJami Botring-daemon build instructions don't workIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Viau (aviau)**
Build instructions ask to ``cd ../contrib`` while it should be ``cd contrib``.Issue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Viau (aviau)**
Build instructions ask to ``cd ../contrib`` while it should be ``cd contrib``.https://git.jami.net/savoirfairelinux/jami-project/-/issues/127Simple ring-project build instructions are not available easily2018-05-21T23:31:08ZJami BotSimple ring-project build instructions are not available easilyIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Viau (aviau)**
Ring-project build instructions are not available easily. The user has to access to a website or build docs.Issue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Viau (aviau)**
Ring-project build instructions are not available easily. The user has to access to a website or build docs.