Bug#1037364: nextcloud-desktop: TLS initilization failed
Control: tags -1 moreinfo Control: severity -1 important Hey, I never had issues with using Nextcloud desktop to connect to my server, that's why I downgrade the serverity, as it has something to do with your specific setup. I expect that the issue is that your server only accepts TLS < 1.3. The last years a lot of ciphers are not trusted anymore by default. You can check your servers certificate with online tools e.g. https://www.ssllabs.com/ssltest/. regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#1037364: nextcloud-desktop: TLS initilization failed
Control: tags -1 moreinfo Control: serverity -1 important Hey, I never had issues with using Nextcloud desktop to connect to my server, that's why I downgrade the serverity, as it has something to do with your specific setup. I expect that the issue is that your server only accepts TLS < 1.3. The last years a lot of ciphers are not trusted anymore by default. You can check your servers certificate with online tools e.g. https://www.ssllabs.com/ssltest/. regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#1034688: [Pkg-privacy-maintainers] Bug#1034688: onionshare: flaky autopkgtest
Hey, I have no real idea why we see only a problem in the chat_server test. It is a problem in the shutdown... I can mark it as superficial so the failing test does not block the CI. But is only a workaround. Can you enable the verbose flag by hand, so we can see what function triggers this segmentation fault? Test-Command: XDG_CONFIG_HOME="$AUTOPKGTEST_TMP" onionshare-cli -v --local- only --chat --auto-stop-timer 2 Or can you give me the the back trace of the segmentation fault? On my system, I don't see the segmentation fault, so hard to taggle down. Properly it is https://github.com/onionshare/onionshare/issues/1408#issuecomment-908150292 and it is harmless. But without verbose log I cannot be sure. > The autopkgtests from onionshare are flaky and have been failing roughly > half the time over the last couple of weeks. Does that mean, that it run successfully before? Regards, hefee -- On Freitag, 21. April 2023 20:53:03 CEST Sebastian Ramacher wrote: > Source: onionshare > Version: 2.6-1 > Severity: serious > > > https://ci.debian.net/data/autopkgtest/testing/amd64/o/onionshare/32901091/l > og.gz > > Give this address and private key to the recipient: > http://127.0.0.1:17632 > Private key: E2GOT5LTUTP3OAMRCRXO4GSH6VKJEUOXZQUC336SRKAHTTT5OVSA > > Press Ctrl+C to stop the server > Stopped because auto-stop timer ran out > Segmentation fault > autopkgtest [22:20:10]: test chat_server: ---] > autopkgtest [22:20:10]: test chat_server: - - - - - - - - - - results - - - > - - - - - - - chat_server FAIL non-zero exit status 139 signature.asc Description: This is a digitally signed message part.
Bug#1027547: onionshare: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 --dir cli returned exit code 13
Control: reassign -1 flask-socketio 5.0.1-1
Control: forcemerge -1 1023568
Hey,
the bug is not inside onionshare but in flask-socketio.
regards,
hefee
On Sonntag, 1. Januar 2023 15:16:09 CET Lucas Nussbaum wrote:
> Source: onionshare
> Version: 2.5-2
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20230101 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > PYBUILD_NAME=onionshare-cli HOME=/tmp dh_auto_test --buildsystem=pybuild
> > --sourcedirectory cli>
> > pybuild --test --test-pytest -i python{version} -p 3.10 --dir cli
> >
> > I: pybuild base:240: cd
> > /<>/.pybuild/cpython3_3.10_onionshare-cli/build; python3.10
> > -m pytest tests ImportError while loading conftest
> > '/<>/.pybuild/cpython3_3.10_onionshare-cli/build/tests/conft
> > est.py'. tests/conftest.py:8: in
> >
> > from onionshare_cli import common, web
> >
> > onionshare_cli/__init__.py:30: in
> >
> > from .web import Web
> >
> > onionshare_cli/web/__init__.py:21: in
> >
> > from .web import Web
> >
> > onionshare_cli/web/web.py:38: in
> >
> > from flask_socketio import SocketIO
> >
> > /usr/lib/python3/dist-packages/flask_socketio/__init__.py:24: in
> >
> > from werkzeug.serving import run_with_reloader
> >
> > E ImportError: cannot import name 'run_with_reloader' from
> > 'werkzeug.serving' (/usr/lib/python3/dist-packages/werkzeug/serving.py)
> > E: pybuild pybuild:388: test: plugin pyproject failed with: exit code=4:
> > cd /<>/.pybuild/cpython3_3.10_onionshare-cli/build;
> > python3.10 -m pytest tests>
> > rm -fr -- /tmp/dh-xdg-rundir-UYdeNRLC
> >
> > dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p
> > 3.10 --dir cli returned exit code 13
> The full build log is available from:
> http://qa-logs.debian.net/2023/01/01/onionshare_2.5-2_unstable.log
>
> All bugs filed during this archive rebuild are listed at:
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lucas
> @debian.org or:
> https://udd.debian.org/bugs/?release=na=ign=7=7
> =only=ftbfs-20230101=lu...@debian.org
> ugs=1=1=1=1#results
>
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
>
> If you reassign this bug to another package, please mark it as 'affects'-ing
> this package. See https://www.debian.org/Bugs/server-control#affects
>
> If you fail to reproduce this, please provide a build log and diff it with
> mine so that we can identify if something relevant changed in the meantime.
signature.asc
Description: This is a digitally signed message part.
Bug#1018198: modemmanager: FTBFS test failing with common_test_ccwa_response: assertion failed: (result)
Package: modemmanager Version: 1.18.10-1 Severity: serious Tags: upstream patch bookworm sid ftbfs Justification: FTBFS Forwarded: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/870 X-Debbugs-Cc: he...@debian.org Hey, when I try a recompiliation of ModemManager, the tests are failing with: /test_ccwa_response: ** ERROR:test-modem-helpers.c:4204:common_test_ccwa_response: assertion failed: (result) FAIL GTester: last random seed: R02S1c9c8a2a8c689230b60594a14f54dc63 make[5]: *** [Makefile:889: test-nonrecursive] Terminated make[5]: Leaving directory '/<>/src/tests' make[4]: *** [Makefile:736: check-am] Error 2 make[4]: Leaving directory '/<>/src/tests' make[3]: *** [Makefile:1991: check-recursive] Error 1 make[3]: Leaving directory '/<>/src' make[2]: *** [Makefile:2142: check] Error 2 make[2]: Leaving directory '/<>/src' make[1]: *** [Makefile:540: check-recursive] Error 1 make[1]: Leaving directory '/<>' dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 returned exit code 2 make: *** [debian/rules:12: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 This bug is also reported upstream https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/601 It seems like the issue is that with new glibc >= 2.73.2 PCRE1 is replaced with PCRE2. There is also a first patch for it, but this does not fix this issue completly. I initally wanted to fix my breakage of my UMTS stick failing https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/621 I will not open a second bug report as the bugfix is don with same MR. regards, hefee -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages modemmanager depends on: ii libc6 2.34-6 ii libglib2.0-0 2.73.3-2 ii libgudev-1.0-0 237-2 ii libmbim-glib4 1.26.4-1 ii libmbim-proxy 1.26.4-1 ii libmm-glib01.18.10-1 ii libpolkit-gobject-1-0 0.105-33 ii libqmi-glib5 1.30.8-1 ii libqmi-proxy 1.30.8-1 ii libqrtr-glib0 1.2.2-1 ii libsystemd0251.4-1 ii policykit-10.105-33 Versions of packages modemmanager recommends: ii usb-modeswitch 2.6.1-3+b1 modemmanager suggests no packages. -- no debconf information
Bug#1008829: pysrs-bin: envfrom2srs and srs2envtol fails with ModuleNotFoundError: No module named 'ConfigParser'
Control: severity -1 normal Hey, > # envfrom2srs > Traceback (most recent call last): > File "/usr/bin/envfrom2srs", line 14, in > from ConfigParser import ConfigParser, DuplicateSectionError > ModuleNotFoundError: No module named 'ConfigParser' > > # srs2envtol > Traceback (most recent call last): > File "/usr/bin/srs2envtol", line 14, in > from ConfigParser import ConfigParser, DuplicateSectionError > ModuleNotFoundError: No module named 'ConfigParser' > > No need to clutter the archive with broken and untested packages. > Please remove can you please use a less offensive language. It is only the two example scripts, that are not properly ported to Python 3. With a big warning in the top of the file: # Use only if absolutely necessary. It is *very* inefficient and # a security risk. This was fixed upstream, but they not have released a new version. Regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#1007743: kldap: BD-Uninstallable on s390x
Control: reassign -1 qtkeychain/0.13.2-4 Control: affects -1 kldap Control: tags -1 +patch That is more an issue of qtkeychain than of kldap ;) Qtkeychain does not build on s390x because of misssing Qt6 for s390x: https://tracker.debian.org/pkg/qtkeychain Ubuntu has already the needed patches to disable Qt6 for s390x: https://patches.ubuntu.com/q/qtkeychain/qtkeychain_0.13.2-4ubuntu1.patch So it should be easy to adopt it for Debian. hefee On Dienstag, 15. März 2022 23:20:32 CET Sebastian Ramacher wrote: > Source: kldap > Version: 21.08.1-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the > past) > > > kldap build-depends on missing: > - qt5keychain-dev:s390x > > Please get this fixed or request the removal of the s390x binaries of > kldap. > > Cheers signature.asc Description: This is a digitally signed message part.
Bug#964695: marked as pending in ktexteditor
Control: tag -1 pending Hello, Bug #964695 in ktexteditor reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/qt-kde-team/kde/ktexteditor/-/commit/b4a4cedfeba8366ea6f04f93c7dea81c2741cfd8 Make version to close 964695 and 946650. Closes: #964695 Closes: #946650 (this message was generated automatically) -- Greetings https://bugs.debian.org/964695
Bug#970900: marked as pending in nextcloud-desktop
Control: tag -1 pending Hello, Bug #970900 in nextcloud-desktop reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/owncloud-team/nextcloud-desktop/-/commit/5bc3fcd39b4b2bba1e3997859438fc0fd536eb58 Fix typo: qml-module-qtqml-modules2 -> qml-module-qtqml-models2. Closes: #970900 (this message was generated automatically) -- Greetings https://bugs.debian.org/970900
Bug#969576: marked as pending in nextcloud-desktop
Control: tag -1 pending Hello, Bug #969576 in nextcloud-desktop reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/owncloud-team/nextcloud-desktop/-/commit/6b967d6e691dd16f127f26087b185cbe04d89bc3 Add missing qml dependencies. Closes: #969576 (this message was generated automatically) -- Greetings https://bugs.debian.org/969576
