Bug#1069841: marked as done (python-icalendar: FTBFS with tzdata 2024a: UnknownTimeZoneError: 'America/Godthab')
Your message dated Fri, 26 Apr 2024 05:04:24 + with message-id and subject line Bug#1069841: fixed in python-icalendar 5.0.12-1 has caused the Debian Bug report #1069841, regarding python-icalendar: FTBFS with tzdata 2024a: UnknownTimeZoneError: 'America/Godthab' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1069841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069841 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-icalendar Version: 5.0.11-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild dh_auto_build -O--buildsystem=pybuild I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" module I: pybuild base:311: python3.12 -m build --skip-dependency-check --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12_icalendar * Building wheel... running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/icalendar copying src/icalendar/__init__.py -> build/lib/icalendar copying src/icalendar/windows_to_olson.py -> build/lib/icalendar copying src/icalendar/timezone_cache.py -> build/lib/icalendar copying src/icalendar/prop.py -> build/lib/icalendar copying src/icalendar/caselessdict.py -> build/lib/icalendar copying src/icalendar/tools.py -> build/lib/icalendar copying src/icalendar/parser.py -> build/lib/icalendar copying src/icalendar/cli.py -> build/lib/icalendar copying src/icalendar/cal.py -> build/lib/icalendar copying src/icalendar/parser_tools.py -> build/lib/icalendar creating build/lib/icalendar/tests copying src/icalendar/tests/test_issue_322_single_strings_characters_split_into_multiple_categories.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_unit_parser_tools.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_recurrence.py -> build/lib/icalendar/tests copying src/icalendar/tests/__init__.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_issue_348_exception_parsing_value.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_cli_tool.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_issue_500_vboolean_for_parameter.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_unit_tools.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_time.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_unit_cal.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_issue_318_skip_default_parameters.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_issue_168_parsing_invalid_calendars_no_warning.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_icalendar.py -> build/lib/icalendar/tests copying src/icalendar/tests/conftest.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_fixed_issues.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_issue_557_encode_native_parameters.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_unit_caselessdict.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_issue_27_period.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_issue_165_missing_event.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_examples.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_property_params.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_timezoned.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_with_doctest.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_equality.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_multiple.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_components_break_on_bad_ics.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_parsing.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_encoding.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_unit_prop.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_period.py -> build/lib/icalendar/tests creating build/lib/icalendar/tests/hypothesis copying src/icalendar/tests/hypothesis/test_fuzzing.py -> build/lib/icalendar/tests/hypothesis running egg_info creating
Bug#1069357: cpp-httplib: FTBFS on arm64: dh_auto_test: error: cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test --timeout-multiplier=3 --test-arg
On Sat, Apr 20, 2024 at 01:59:57PM +0200, Lucas Nussbaum wrote: > Source: cpp-httplib > Version: 0.14.3+ds-1.1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64 > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on arm64. > > > Relevant part (hopefully): > > make[1]: Entering directory '/<>' > > dh_auto_test -- \ > > --timeout-multiplier=3 \ > > --test-args='--gtest_filter=-*_Online' > > cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb > > LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test --timeout-multiplier=3 > > --test-args=--gtest_filter=-\*_Online > > ninja: Entering directory `/<>/obj-aarch64-linux-gnu' > > ninja: no work to do. > > 1/1 main TIMEOUT900.12s killed by signal 15 SIGTERM Hi Andrea, It looks like it's just that arm64 is slow (as are several other archs). Changing the command to read --timeout-multiplier=30 should fix this FTBFS serious bug and allow cpp-httplib to migrate to testing. Best wishes, Julian
Bug#1060939: marked as done (python-workalendar: FTBFS: CalendarError: Need configure 2024 for China.)
Your message dated Fri, 26 Apr 2024 04:19:14 + with message-id and subject line Bug#1069827: Removed package(s) from unstable has caused the Debian Bug report #1060939, regarding python-workalendar: FTBFS: CalendarError: Need configure 2024 for China. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1060939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-workalendar Version: 17.0.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:305: python3.12 setup.py config > running config > I: pybuild base:305: python3.11 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:305: /usr/bin/python3.12 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar > copying workalendar/__init__.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar > copying workalendar/exceptions.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar > copying workalendar/astronomy.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar > copying workalendar/registry_tools.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar > copying workalendar/registry.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar > copying workalendar/precomputed_astronomy.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar > copying workalendar/core.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar > copying workalendar/skyfield_astronomy.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar > creating > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar/tests > copying workalendar/tests/test_global_registry.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar/tests > copying workalendar/tests/test_registry_europe.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar/tests > copying workalendar/tests/test_germany.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar/tests > copying workalendar/tests/test_canada.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar/tests > copying workalendar/tests/__init__.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar/tests > copying workalendar/tests/test_asia.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar/tests > copying workalendar/tests/test_spain.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar/tests > copying workalendar/tests/test_precomputed_astronomy.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar/tests > copying workalendar/tests/test_registry.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar/tests > copying workalendar/tests/test_africa.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar/tests > copying workalendar/tests/test_mozambique.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar/tests > copying workalendar/tests/test_registry_oceania.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar/tests > copying workalendar/tests/test_registry_asia.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar/tests > copying workalendar/tests/test_turkey.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar/tests > copying workalendar/tests/test_oceania.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar/tests > copying workalendar/tests/test_brazil.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar/tests > copying workalendar/tests/test_registry_usa.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar/tests > copying workalendar/tests/test_europe.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar/tests > copying workalendar/tests/test_usa.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar/tests > copying workalendar/tests/test_scotland.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar/tests > copying workalendar/tests/test_core.py -> > /<>/.pybuild/cpython3_3.12_workalendar/build/workalendar/tests > copying
Bug#1069381: marked as done (sslh: FTBFS on arm64: cat: /tmp/bZv3B_U_mJ/sslh.pid: No such file or directory)
Your message dated Fri, 26 Apr 2024 04:19:22 + with message-id and subject line Bug#1069381: fixed in sslh 2.1.1-1 has caused the Debian Bug report #1069381, regarding sslh: FTBFS on arm64: cat: /tmp/bZv3B_U_mJ/sslh.pid: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1069381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069381 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sslh Version: 1.22c-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64 Hi, During a rebuild of all packages in sid, your package failed to build on arm64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > Makefile:68: warning: ignoring prerequisites on suffix rule definition > ./t > ./echosrv --listen localhost:42037 --prefix 'ssh: ' > ./echosrv --listen localhost:37521 --prefix 'socks5: ' > ./echosrv --listen localhost:41387 --prefix 'http: ' > Listening to: > 3:localhost:42037 > error localhost:42037:bind: No such file or directory > udp: 0 > prefix: ssh: > listen [1]: > host: localhost > port: 42037 > Listening to: > ./echosrv --listen localhost:37407 --prefix 'tinc: ' > 3:localhost:37521 > error localhost:37521:bind: No such file or directory > udp: 0 > prefix: socks5: > listen [1]: > host: localhost > port: 37521 > ./echosrv --listen localhost:37379 --prefix 'openvpn: ' > Listening to: > 3:localhost:41387 > error localhost:41387:bind: No such file or directory > udp: 0 > prefix: http: > listen [1]: > host: localhost > port: 41387 > ./echosrv --listen localhost:41687 --prefix 'xmpp: ' > Listening to: > 3:localhost:37407 > error localhost:37407:bind: No such file or directory > udp: 0 > prefix: tinc: > listen [1]: > host: localhost > port: 37407 > ./echosrv --listen localhost:38787 --prefix 'adb: ' > Listening to: > 3:localhost:37379 > error localhost:37379:bind: No such file or directory > udp: 0 > prefix: openvpn: > listen [1]: > host: localhost > port: 37379 > ./echosrv --listen localhost:42537 --prefix 'syslog: ' > Listening to: > 3:localhost:41687 > error localhost:41687:bind: No such file or directory > udp: 0 > prefix: xmpp: > listen [1]: > host: localhost > port: 41687 > ./echosrv --listen localhost:42707 --prefix 'regex: ' > Listening to: > 3:localhost:38787 > error localhost:38787:bind: No such file or directory > udp: 0 > prefix: adb: > listen [1]: > host: localhost > port: 38787 > ./echosrv --listen localhost:38823 --prefix 'tls:sni1;alpn1,alpn2: ' > Listening to: > 3:localhost:42537 > error localhost:42537:bind: No such file or directory > udp: 0 > prefix: syslog: > listen [1]: > host: localhost > port: 42537 > ./echosrv --listen localhost:44879 --prefix 'tls:sni2,sni3;alpn1,alpn2: ' > Listening to: > 3:localhost:42707 > error localhost:42707:bind: No such file or directory > udp: 0 > prefix: regex: > listen [1]: > host: localhost > port: 42707 > ./echosrv --listen localhost:35705 --prefix 'tls:;alpn3: ' > Listening to: > 3:localhost:38823 > error localhost:38823:bind: No such file or directory > udp: 0 > prefix: tls:sni1;alpn1,alpn2: > listen [1]: > host: localhost > port: 38823 > ./echosrv --listen localhost:34001 --prefix 'tls:sni3;: ' > Listening to: > 3:localhost:44879 > error localhost:44879:bind: No such file or directory > udp: 0 > prefix: tls:sni2,sni3;alpn1,alpn2: > listen [1]: > host: localhost > port: 44879 > ./echosrv --listen localhost:39839 --prefix 'tls: ' > Listening to: > 3:localhost:35705 > error localhost:35705:bind: No such file or directory > udp: 0 > prefix: tls:;alpn3: > listen [1]: > host: localhost > port: 35705 > ./echosrv --listen localhost:39397 --prefix 'anyprot: ' > Listening to: > 3:localhost:34001 > error localhost:34001:bind: No such file or directory > udp: 0 > prefix: tls:sni3;: > listen [1]: > host: localhost > port: 34001 > Testing sslh-select > spawned 2073264 > Listening to: > ./sslh-select -v 4 -f -u user42 -F test.cfg > 3:localhost:39839 > error localhost:39839:bind: No such file or directory > udp: 0 > prefix: tls: > listen [1]: > host: localhost > port: 39839 > Listening to: > 3:localhost:39397 > error localhost:39397:bind: No such file or directory > udp: 0 > prefix: anyprot: > listen [1]: > host: localhost > port: 39397 > Unknown settings: > /protocols[8]/test_patterns[0]/pattern:foo >
Bug#1068414: marked as done (obs-advanced-scene-switcher - still depends on old libcurl after binnmu)
Your message dated Thu, 25 Apr 2024 22:34:42 + with message-id and subject line Bug#1068414: fixed in obs-advanced-scene-switcher 1.25.5-1 has caused the Debian Bug report #1068414, regarding obs-advanced-scene-switcher - still depends on old libcurl after binnmu to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1068414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: obs-advances-scene-switcher Version: 1.23.1-2 Severity: grave User: debian-...@lists.debian.org Usertag: time-t After being rebuilt for the time64 transition, obs-advanced-scene-switcher still depends on libcurl4, rather than libcurl4t64. As a result it is uninstallable on architectures that are undergoing the time64 transition (armel, armhf and some debian-ports architectures). Ubuntu has applied a fix for this. https://launchpadlibrarian.net/720928573/obs-advanced-scene-switcher_1.23.1-2build2_1.23.1-2ubuntu1.diff.gz --- End Message --- --- Begin Message --- Source: obs-advanced-scene-switcher Source-Version: 1.25.5-1 Done: Joao Eriberto Mota Filho We believe that the bug you reported is fixed in the latest version of obs-advanced-scene-switcher, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joao Eriberto Mota Filho (supplier of updated obs-advanced-scene-switcher package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 23 Apr 2024 18:35:29 -0300 Source: obs-advanced-scene-switcher Architecture: source Version: 1.25.5-1 Distribution: unstable Urgency: medium Maintainer: Joao Eriberto Mota Filho Changed-By: Joao Eriberto Mota Filho Closes: 1068414 Changes: obs-advanced-scene-switcher (1.25.5-1) unstable; urgency=medium . * New upstream version 1.25.5. * Fixed a dependency of old libcurl. Consequently: - debian/control: dropped libcurl from Depends field from the binary obs-advanced-scene-switcher. - debian/rules: added the target override_dh_gencontrol to select a right libcurl from the system. - Thanks to Matthias Klose . (Closes: #1068414) * debian/control: updated Build-Depends field: - Added libxkbcommon-dev and nlohmann-json3-dev. - Replaced qtbase5-dev by qt6-base-dev. * debian/copyright: updated upstream and packaging copyright years. * debian/patches/010_fix-cmake.patch: created to make building process compliant with Debian. Thanks to WarmUpTill . * debian/rules: - Removed a workaround no longer needed about libremidi. - Removed no longer needed 'export QT_SELECT = qt5'. * debian/tests/control: added a workaround to ignore a false positive message 'Tried to call obs_frontend_add_event_callback with no callbacks'. Checksums-Sha1: 4058337a1092299eeaf9dae0d06f9c2000faaebe 2445 obs-advanced-scene-switcher_1.25.5-1.dsc 62c65c6e6b5232b0833064d2fc73625d86be4c89 13225325 obs-advanced-scene-switcher_1.25.5.orig.tar.gz 6794063801d1b4ee058d096eed06e8edaaf1421a 7900 obs-advanced-scene-switcher_1.25.5-1.debian.tar.xz 4466f040864f36950a0fa4b63f2890506b833f9b 21285 obs-advanced-scene-switcher_1.25.5-1_source.buildinfo Checksums-Sha256: a53aed124a0f3c3558de3ad385313e1cc283cfc1936365a754122f6d59c756b1 2445 obs-advanced-scene-switcher_1.25.5-1.dsc 8c7ae9c8757c9f6c5bbb2144f1422127704331d8a95b434dfbcafc174a451abe 13225325 obs-advanced-scene-switcher_1.25.5.orig.tar.gz 3904744e1a6fdb7bce42f14db38b832940607a03c80d60bbc5425bf2eceaafb8 7900 obs-advanced-scene-switcher_1.25.5-1.debian.tar.xz 5448f55e14fcc8c5cddc916b8c325556c94cd2429f9ba53fe6b9c01c10992e31 21285 obs-advanced-scene-switcher_1.25.5-1_source.buildinfo Files: e50d97b5fdbeeaf1db6cb56f6583c978 2445 video optional obs-advanced-scene-switcher_1.25.5-1.dsc 4cd04fb3421062b849675bfb7b6406fc 13225325 video optional obs-advanced-scene-switcher_1.25.5.orig.tar.gz 8cd2f2ded1f0ca127e5fb6b08d656d81 7900 video optional obs-advanced-scene-switcher_1.25.5-1.debian.tar.xz 1de5122f32fb1513aa903bbb5cd90d9b 21285 video optional
Bug#1069624: marked as done (rapidfuzz: Fails to build on arch: all)
Your message dated Thu, 25 Apr 2024 21:48:49 + with message-id and subject line Bug#1069624: fixed in rapidfuzz 3.6.2+ds-3 has caused the Debian Bug report #1069624, regarding rapidfuzz: Fails to build on arch: all to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1069624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069624 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rapidfuzz Version: 3.6.2+ds-2 Severity: serious Tags: ftbfs The arch: all build for rapidfuzz is failing: https://buildd.debian.org/status/package.php?p=rapidfuzz If you use sbuild, I believe you can test this with sbuild -arch-all --no-arch-any Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Source: rapidfuzz Source-Version: 3.6.2+ds-3 Done: Julian Gilbey We believe that the bug you reported is fixed in the latest version of rapidfuzz, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julian Gilbey (supplier of updated rapidfuzz package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 25 Apr 2024 21:02:09 +0100 Source: rapidfuzz Architecture: source Version: 3.6.2+ds-3 Distribution: unstable Urgency: medium Maintainer: Julian Gilbey Changed-By: Julian Gilbey Closes: 1069624 Changes: rapidfuzz (3.6.2+ds-3) unstable; urgency=medium . * Fix arch-all build; we need to build the package to build the documentation (closes: #1069624) Checksums-Sha1: 0f24337875c015a733145b40e91584c2d73cff30 3195 rapidfuzz_3.6.2+ds-3.dsc 069ae0cff0d358ba43b085c75d1bb07bc995095e 3520 rapidfuzz_3.6.2+ds-3.debian.tar.xz 60d2ad24f78b6f7db859cf4bf4eebe878e16c065 10994 rapidfuzz_3.6.2+ds-3_amd64.buildinfo Checksums-Sha256: e2ea0064de93e868235f06c23a3d440b9902f9bf890a307769c1ab6e32c199cd 3195 rapidfuzz_3.6.2+ds-3.dsc 5861a06c8c38d7846d6c812ab4baa4ad6edb7b2a369e9b33a1bf1679a63e7c21 3520 rapidfuzz_3.6.2+ds-3.debian.tar.xz a7eb2a2da29be825273c6e86655adb34f4da3f6a3b4608cfc9ab3d704bb2d9fc 10994 rapidfuzz_3.6.2+ds-3_amd64.buildinfo Files: 0a0d36ade8bf3aa858263dc6fa16cad9 3195 python optional rapidfuzz_3.6.2+ds-3.dsc 8059c3dd8dbd7c8b069ddfb252851a1a 3520 python optional rapidfuzz_3.6.2+ds-3.debian.tar.xz 120b745a426c1050dc249edc490e321f 10994 python optional rapidfuzz_3.6.2+ds-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEfhrD+iemSShMMj72aVxCkxbAe/4FAmYqwjMPHGpkZ0BkZWJp YW4ub3JnAAoJEGlcQpMWwHv+z8gP/igUXRBOH4U41/bKb992t1Ym/dWYU6zoNECI pb+pxynWYXkim/GNQFjiSMXZXisjsHQChqTlKhBBmJ+OckTBh6DXWMnbsJlQn6oO SNyYciE+wVkDWswpul5HrXoUknJaBcFe4ULNEpIgn1u7XOdYk0iFcpdJB5vC/L1l 5em/x23LuemG2y2LpG3epIBCf5iZgmPNKW5DyE9nWjs7eXtpff5Nib06smAJ4zU8 OKU6FgyD1lm5wG+Lfo6SZ/DMHOGId/1GQf/BweauypvtiV3VP0MshgbS11a06W4U Be568VpyLe65/wOciNRSOD3MKYhFRTJwslZCk8IibxldZrtGxSI12/WgF2vEtsV/ qjCI7H1sOBQW9TW/bXuUZhvQSFDVUZlQzXML0hKODeHCWxgE3xREPcSQ0fwolGSn PNepwQKL8oO0+9vcSBV7HPagbHeYlWtoxTd2rLZl/mRtacCxWiPiPE2vrT5XQKjm ztNCDi9w+8FvrhYXx7dncIZKGxJq4EfRj4yO1oJ78oQXAHRdN6QLLMznCuOXLm78 bOsBvxTzro15zs+e/KQbqQnmX+PH44+v18B5SVWDGjeKxsUNexk84TUaTu0evLI9 rQIjhHUwNXli9pBO4BkvYgow8nGUf0q9HjBKXZAB2Vo/GvCD8qYjfSommm8h5p76 RLgRjsJj =6XQo -END PGP SIGNATURE- pgpBkQJIZYVr7.pgp Description: PGP signature --- End Message ---
Bug#1069586: marked as done (Chromium native Wayland support broken)
Your message dated Thu, 25 Apr 2024 21:48:05 + with message-id and subject line Bug#1069586: fixed in chromium 124.0.6367.60-2 has caused the Debian Bug report #1069586, regarding Chromium native Wayland support broken to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1069586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: chromium Version: 124.0.6367.60-1~deb12u1 Since the last update, Chromium does work with native Wayland. It is starting up, but it is displaying an invisible window. It is listed in the window switchers (Alt+Tab), Gnome Shell etc., but invisible. Note: The default configuration uses X11 via XWayland and is working. The setting can be managed via command line arguments or by typing chrome://flags into the URL bar (filter for ozone). Available settings: default -> X11works auto-> Wayland if available does not work x11 works wayland does not work I have been using Chromium with native Wayland for many months without problems until the last update. I reproduced this with a completely new browser profile. Regards Stephan --- End Message --- --- Begin Message --- Source: chromium Source-Version: 124.0.6367.60-2 Done: Timothy Pearson We believe that the bug you reported is fixed in the latest version of chromium, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timothy Pearson (supplier of updated chromium package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 25 Apr 2024 15:21:00 -0500 Source: chromium Binary: chromium Architecture: source Version: 124.0.6367.60-2 Distribution: unstable Urgency: high Maintainer: Debian Chromium Team Changed-By: Timothy Pearson Closes: 1069586 Changes: chromium (124.0.6367.60-2) unstable; urgency=high . * d/patches/ppc64le: - third_party/0001-Add-PPC64-support-for-boringssl.patch: update for upstream boringssl changes and reenable - third_party/0003-third_party-ffmpeg-Add-ppc64-generated-config.patch: regenerate from new ffmpeg source tree - third_party/skia-vsx-instructions.patch: update for upstream changes . [ Andres Salomon ] * d/patches: - fixes/arm64-ftbfs.patch: add arm64-specific ftbfs fix for libdav1d. - upstream/ozone1.patch, upstream/ozone2.patch: backport fixes for broken wayland support (closes: #1069586). Checksums-Sha1: f51303f7a57dc3421d4c8e4c1817ff7ae3685fc8 3677 chromium_124.0.6367.60-2.dsc 2cc0dded258c8f3c623e10e330195e1e3f9c40a5 847907384 chromium_124.0.6367.60.orig.tar.xz bc8fb4e0a0cb4d213d9235f92556642dd4a3f1c6 417184 chromium_124.0.6367.60-2.debian.tar.xz 517b1e958e3c947c106dbf671063904c9d84e644 22342 chromium_124.0.6367.60-2_source.buildinfo Checksums-Sha256: 5d9b43eb88896bdb4c9b086d3e486e4624114ba0e0d49490177f3fcb65f2b74d 3677 chromium_124.0.6367.60-2.dsc b382eaade5057c56ca257bdf6a78c2c59116b56ce6c1ab166220cea1f5d950d2 847907384 chromium_124.0.6367.60.orig.tar.xz 8f6f9adfa5a2281570255833ccb80a86412e2bdd3f91203fe5f3706546878747 417184 chromium_124.0.6367.60-2.debian.tar.xz 7d397348428374edb3809f0c8057d591609f2287206ce82d7d1d1080c1ebecb5 22342 chromium_124.0.6367.60-2_source.buildinfo Files: 20bddcb7050ee2850c632b5aabca020b 3677 web optional chromium_124.0.6367.60-2.dsc c229f60fab61eb4d55c385e2131236e5 847907384 web optional chromium_124.0.6367.60.orig.tar.xz 63a825214d11441c46d952ec4f5c3b80 417184 web optional chromium_124.0.6367.60-2.debian.tar.xz 7f7bcd7b62e774796ce53d4970d19e42 22342 web optional chromium_124.0.6367.60-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEbljKSL6u8RwDRSBe7DyAvFcxm34FAmYqv7AACgkQ7DyAvFcx m34/5xAAgpDQOXpkQTVpWRV2T2KApZQh3O3loSnfY2r2bZKdiMSHPG9myGhrYP8T 6jDiXvolYlVItgADuJhytMChG9kZApJrRLxWRn70xEry+aLtNsOXcHmG68TUje2j 2deU2wF+q7DSQFxdz7xAXQ653t/uOuA+jMxatNIubC5808hGOHG17frEiW0f+c7b VJlAktyuGzGXXIRelUk0Asai/hfKTywvc/hwllWJyll2iLkQA1jlKwfNlaxzP5WQ
Bug#1068936: marked as pending in libcanberra
Control: tag -1 pending Hello, Bug #1068936 in libcanberra 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/gnome-team/libcanberra/-/commit/eaae0b24b9aaa36345235f31f2f0912e93fe36d6 Drop hard-coded dependency on libgtk-3-0 (>= 3.2.2-3) Closes: #1068936 (this message was generated automatically) -- Greetings https://bugs.debian.org/1068936
Processed: Bug#1068936 marked as pending in libcanberra
Processing control commands: > tag -1 pending Bug #1068936 [libcanberra-gtk3-module] libcanberra-gtk3-module: hard-coded dependency on libgtk-3-0 Added tag(s) pending. -- 1068936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068936 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069859: atop: Fix atop for 64-bit time_t on arm
Package: atop Version: 2.10.0-2 Severity: grave Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch Hi Marc, Although atop currently builds successfully on armhf and armel, it is broken at runtime because it tries to use a time_t in a format string which now no longer uses the correct size for the data. This was found in Ubuntu via autopkgtests (unfortunately, Debian does not run autopkgtests for binNMUs): 358s /tmp/autopkgtest.Nzaczp/build.Xps/src/debian/tests/01-numcpus: line 15: 1136 Segmentation fault (core dumped) atop -P cpu 5 1 1>&2 Please see attached a patch that fixes this issue. It has been uploaded to Ubuntu. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru atop-2.10.0/debian/patches/64-bit-time-t-compat.patch atop-2.10.0/debian/patches/64-bit-time-t-compat.patch --- atop-2.10.0/debian/patches/64-bit-time-t-compat.patch 1969-12-31 16:00:00.0 -0800 +++ atop-2.10.0/debian/patches/64-bit-time-t-compat.patch 2024-03-22 11:11:06.0 -0700 @@ -0,0 +1,22 @@ +Description: compatibility with 64-bit time_t +Author: Steve Langasek +Forwarded: no +Last-Update: 2024-03-22 + +Index: atop-2.10.0/parseable.c +=== +--- atop-2.10.0.orig/parseable.c atop-2.10.0/parseable.c +@@ -214,10 +214,10 @@ + convdate(curtime, datestr); + convtime(curtime, timestr); + +- snprintf(header, sizeof header, "%s %s %ld %s %s %d", ++ snprintf(header, sizeof header, "%s %s %lld %s %s %d", + labeldef[i].label, + utsname.nodename, +- curtime, ++ (long long)curtime, + datestr, timestr, numsecs); + + /* diff -Nru atop-2.10.0/debian/patches/series atop-2.10.0/debian/patches/series --- atop-2.10.0/debian/patches/series 2024-01-14 12:18:53.0 -0800 +++ atop-2.10.0/debian/patches/series 2024-03-22 11:10:13.0 -0700 @@ -15,3 +15,4 @@ no-atopgpud handle-default-file default +64-bit-time-t-compat.patch
Bug#1069800: marked as done (FTBFS: test failures in buildd environment)
Your message dated Thu, 25 Apr 2024 20:45:04 + with message-id and subject line Bug#1069800: fixed in cloud-init 24.1.4-2 has caused the Debian Bug report #1069800, regarding FTBFS: test failures in buildd environment to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1069800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069800 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cloud-init Version: 21.1.4-1 Severity: serious Tags: ftbfs upstream Justification: fails to build from source Cloud-init's test fails in a non-networked build environment, as visible in recent buildd logs, e.g. https://buildd.debian.org/status/fetch.php?pkg=cloud-init=all=24.1.4-1=1714007718=0 This appears to be an upstream issue, as it occurs in pristine upstream source tree. -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-20-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: cloud-init Source-Version: 24.1.4-2 Done: Noah Meyerhans We believe that the bug you reported is fixed in the latest version of cloud-init, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Noah Meyerhans (supplier of updated cloud-init package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 25 Apr 2024 11:37:10 -0700 Source: cloud-init Architecture: source Version: 24.1.4-2 Distribution: unstable Urgency: medium Maintainer: Debian Cloud Team Changed-By: Noah Meyerhans Closes: 1051421 1066802 1069800 Changes: cloud-init (24.1.4-2) unstable; urgency=medium . * Disable broken upstream test (Closes: #1069800) * Remove obsolete python3-mock builddep (Closes: #1066802) * Prefer udhcpc as the DHCP client for pre-network boot configuration (Closes: #1051421) * dh/rules: remove more artifacts during clean Checksums-Sha1: 2757edbf3494c1fd8e9b713aaaf940dde7aa03ad 2434 cloud-init_24.1.4-2.dsc 7abbae479cb73c4a7b4110dcb8f7790a54df 26828 cloud-init_24.1.4-2.debian.tar.xz bdd7ca16ac7961a8c51b402f1ae6b9febd93c984 7370 cloud-init_24.1.4-2_source.buildinfo Checksums-Sha256: f43b7267725feafd5568d1a063798cbeb7f27786ea39c939363cb3244dd62026 2434 cloud-init_24.1.4-2.dsc 2358563382a860071f76c4ff281e5c78ee7d9983dcc103b42d9b22fbc8f299fd 26828 cloud-init_24.1.4-2.debian.tar.xz 110932885ae5bd65064cfca04d76b73d4d4aa65f9f3ecf0541c2e95364b01e02 7370 cloud-init_24.1.4-2_source.buildinfo Files: 504dfaa40aaa4b93de29be19ec95c424 2434 admin optional cloud-init_24.1.4-2.dsc f6e3bf9ccb35a727bd0bcdefa4ef407a 26828 admin optional cloud-init_24.1.4-2.debian.tar.xz 073dfe57366569aefb28b78304901691 7370 admin optional cloud-init_24.1.4-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE5G+E0xEKhJuZ7RJ34+c1IpshdTUFAmYqvEcRHG5vYWhtQGRl Ymlhbi5vcmcACgkQ4+c1IpshdTXajA//Q+KkFjdhi/Q/KtYzGiaohmxMjz3ZGWwC xou38cX/MHKkOK31jXoY4vxJqh2g2tk4aKPOYANuMEYdWkwOUpBm2j8kmJEZm352 ZyoEwUdeMHtJV9WCjJSaw64Sb2/IFHFRuA4vja/3c0LgAkurOifcxfURMB5xChq6 fzJx/FTYJsrZH0VrQWQavUnnzeLqk8i131ZgftNvskz9WnrCvVCAf4ODPPToS9Cm PaqWALZo33utJKjdzUIf3JTVBwmwo+S01YvFOrjOvigHWylq2ffIv8Jhxs6ByBG3 tIH9B64WVvQvtQymJNt3rN/IRfve6rVTvaGXmPTezuYbHTrB3L0g9Z2KJzjYoDD3 bNUJArCYMHOcDdpH00b5nTpC7D+VX1lYvv/M28ucQKrrkCinp4xtuczGs7wwlXwH Ox7z37IO2asdzFlxw+QyFV9nc6e5uge6O1nlQBOgGSZK0aVdbbBRteADNpw4tBkc keAclHmqIujYt6T+Y8Ol26Np08Yurrin9KbI1FXTEd5hh3Vx8hOVCg68lASg9dU+ WE+Ulog/hWYyzQlLtVyLrEheVsJSLDaC6cPEOJswam1Jde8m1Vq53M6yxte6okyq 12MXx69v8XOwQ1wk3lu3NxxGd0Qpp6ZWiXSbQkCNcBEkUnqUkaTulCAOec+E7hSq R5YtRb0TUgw= =a4ei -END PGP SIGNATURE- pgpukahOiZXBF.pgp Description: PGP signature --- End Message ---
Processed: Re: Bug#1069842: rjava: FTBFS: /usr/bin/ld: cannot find -ldeflate: No such file or directory
Processing commands for cont...@bugs.debian.org: > found 1069842 4.4.0-1 Bug #1069842 [r-base] rjava: FTBFS: /usr/bin/ld: cannot find -ldeflate: No such file or directory Marked as found in versions r-base/4.4.0-1. > affects 1069842 + src:rjava Bug #1069842 [r-base] rjava: FTBFS: /usr/bin/ld: cannot find -ldeflate: No such file or directory Added indication that 1069842 affects src:rjava > thanks Stopping processing here. Please contact me if you need assistance. -- 1069842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069842 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069842: rjava: FTBFS: /usr/bin/ld: cannot find -ldeflate: No such file or directory
found 1069842 4.4.0-1 affects 1069842 + src:rjava thanks Thanks for the quick reply! [ I'm adding the affects so that the bug is shown on the web page for src:rjava. This helps to avoid duplicates, as there are more people reporting FTBFS bugs ] Thanks.
Bug#1069844: More debug info
Alex Bennée writes: > Julian Andres Klode writes: > >> On Thu, Apr 25, 2024 at 06:30:52PM +0100, Alex Bennée wrote: >>> >>> Continuing to debug on QEMU it seems there is an incompatibility with >>> the images and the peloader (which overrides the normal efi loader): >>> > >> In the error case you can see though, that one of the section >> addresses in the Xen binary to be relocated points into the (PE) >> header of the binary, which obviously seems wrong. >> >> So go check your PE sections and check which one is wrong? > > Is there any tooling for examining PE sections? Nothing really jumps out from objdump: 1:08:50 [root@debian-arm64:~] # objdump -h /boot/xen /boot/xen: file format pei-aarch64-little Sections: Idx Name Size VMA LMA File off Algn 0 .reloc 2**0 ALLOC, LOAD, READONLY, DATA 1 .text 00107ea8 0160 0160 0160 2**4 CONTENTS, ALLOC, LOAD, CODE 21:08:53 [root@debian-arm64:~] # objdump -h /boot/vmlinuz /boot/vmlinuz: file format pei-aarch64-little Sections: Idx Name Size VMA LMA File off Algn 0 .text 018c 0001 0001 0001 2**2 CONTENTS, ALLOC, LOAD, READONLY, CODE 1 .data 0090a200 018d 018d 018d 2**2 CONTENTS, ALLOC, LOAD, DATA -- Alex Bennée Virtualisation Tech Lead @ Linaro
Bug#1069334: marked as done (Not installable due to hardcoded pre-t64 library deps)
Your message dated Thu, 25 Apr 2024 19:49:29 + with message-id and subject line Bug#1069334: fixed in nautilus-wipe 0.4.alpha2-0.2 has caused the Debian Bug report #1069334, regarding Not installable due to hardcoded pre-t64 library deps to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1069334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nautilus-wipe Version: 0.4.alpha2-0.1+b4 Severity: grave nautilus-wipe explicitly Depends: libgtk-3-0. It should be changed to the t64 name if it's really needed. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nautilus-wipe depends on: ii libc6 2.37-18 ii libglib2.0-0t64 [libglib2.0-0] 2.78.4-6 pn libgsecuredelete0 ii libgtk-3-0t64 [libgtk-3-0] 3.24.41-4 pn libnautilus-extension4 nautilus-wipe recommends no packages. nautilus-wipe suggests no packages. --- End Message --- --- Begin Message --- Source: nautilus-wipe Source-Version: 0.4.alpha2-0.2 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of nautilus-wipe, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated nautilus-wipe package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 23 Apr 2024 21:19:59 +0200 Source: nautilus-wipe Architecture: source Version: 0.4.alpha2-0.2 Distribution: unstable Urgency: medium Maintainer: Debian Privacy Tools Maintainers Changed-By: Sebastian Ramacher Closes: 1069334 Changes: nautilus-wipe (0.4.alpha2-0.2) unstable; urgency=medium . * Non-maintainer upload. * debian/control: Remove hard-coded dependency on libgtk-3-0 (Closes: #1069334) Checksums-Sha1: 79ec57cd4575ee84bd8fab5b646785858bb75500 1585 nautilus-wipe_0.4.alpha2-0.2.dsc 0e96e13762a870c20c3bcaf26c2b4c45eda93269 6972 nautilus-wipe_0.4.alpha2-0.2.debian.tar.xz ef974758e1cedbd06e8d31039de8b7198780ae63 15930 nautilus-wipe_0.4.alpha2-0.2_amd64.buildinfo Checksums-Sha256: 7fcdb6188aacbe926b60ae6bae67ac3b4ce88b37347540228058fdd27888e582 1585 nautilus-wipe_0.4.alpha2-0.2.dsc c7faad70104c2c0fd772962be3c3a76d3c5a776006c02ff0af832054e30b1619 6972 nautilus-wipe_0.4.alpha2-0.2.debian.tar.xz 31822f61cf93473e6b5fe31a3efb35939d481eb1d9856c9f9d7cd86f26f1327e 15930 nautilus-wipe_0.4.alpha2-0.2_amd64.buildinfo Files: 6fe7c0a5bfb89b90c5af65f346b6d3e7 1585 utils optional nautilus-wipe_0.4.alpha2-0.2.dsc 8f5f459bed211a6de71da5871e250dd0 6972 utils optional nautilus-wipe_0.4.alpha2-0.2.debian.tar.xz 48d48c44722723b42b298903fd179584 15930 utils optional nautilus-wipe_0.4.alpha2-0.2_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZigKiwAKCRAhk2s2YA/N iYFlAQDe/m76fckxYjjzFy2jXkI85Hi1j/RIM+dK6XNA++YkhgEA9JM0SDC9yPmc GPOMYwzCp6HJLEnf+kJMdYgocsO5Gg4= =YOmx -END PGP SIGNATURE- pgpqBhjfUAZ1h.pgp Description: PGP signature --- End Message ---
Bug#1069844: More debug info
Julian Andres Klode writes: > On Thu, Apr 25, 2024 at 06:30:52PM +0100, Alex Bennée wrote: >> >> Continuing to debug on QEMU it seems there is an incompatibility with >> the images and the peloader (which overrides the normal efi loader): >> >> Thread 1 hit Breakpoint 3.2, grub_load_normal_mode () at >> ../../../grub-core/kern/main.c:241 >> 241 in ../../../grub-core/kern/main.c >> >> >> (grub gdb) hbreak do_load_image >> >> >> Hardware assisted breakpoint 4 at 0x23bdf0e00: do_load_image. (2 >> locations) >> >> (grub gdb) c >> >> >> Continuing. >> >> >> add symbol table from file "bli.module" at >> >> >> .text_addr = 0x23ba772e0 >> >> >> .bss_addr = 0x0 >> >> >> .module_license_addr = 0x23ba7764a >> .data_addr = 0x0 >> >> >> .rodata.str1.1_addr = 0x23ba77560 >> >> >> .rodata_addr = 0x23ba77550 >> >> >> add symbol table from file "xen_boot.module" at >> >> >> .text_addr = 0x23bcef3c0 >> >> >> .bss_addr = 0x23bcf0370 >> >> >> .module_license_addr = 0x23bcf035e >> >> .data_addr = 0x0 >> >> .rodata.str1.1_addr = 0x23bcefff8 >> >> Thread 1 hit Breakpoint 4.1, do_load_image (boot_policy=0 '\000', >> parent_image_handle=0x23e889f18, file_path=0x237d1bce0, >> source_buffer=0x239f0, source_size=1081352, >> image_handle=0x4766c498) at ../../../grub-core/loader/efi/peimage.c:745 >> warning: 745../../../grub-core/loader/efi/peimage.c: No such file or >> directory >> (grub gdb) hbreak grub_error >> Hardware assisted breakpoint 5 at 0x6db0: grub_error. (2 locations) >> (grub gdb) c >> Continuing. >> >> Thread 1 hit Breakpoint 4.2, 0x00023bdf0e4c in do_load_image >> (boot_policy=, parent_image_handle=, >> image_handle=, >> source_size=, source_buffer=, >> file_path=) at ../../../grub-core/loader/efi/peimage.c:751 >> 751 in ../../../grub-core/loader/efi/peimage.c >> (grub gdb) c >> Continuing. >> >> Thread 1 hit Breakpoint 5.2, grub_error (n=GRUB_ERR_BAD_OS, >> fmt=0x23bdf1703 "section inside header") at ../../../grub-core/kern/err.c:41 >> warning: 41 ../../../grub-core/kern/err.c: No such file or directory >> (grub gdb) bt >> #0 grub_error (n=GRUB_ERR_BAD_OS, fmt=0x23bdf1703 "section inside >> header") at ../../../grub-core/kern/err.c:41 >> #1 0x00023bdf0e34 in do_load_image (boot_policy=, >> parent_image_handle=, file_path=, >> source_buffer=, >> source_size=, image_handle=) at >> ../../../grub-core/loader/efi/peimage.c:747 >> #2 0x00023bedabdc in grub_arch_efi_linux_boot_image (addr=9561964544, >> size=1081352, >> args=0x23bbb8b00 "placeholder dom0_mem=4G,max:4G loglvl=all >> guest_loglvl=all no-real-mode edd=off") at >> ../../../grub-core/loader/efi/linux.c:210 >> #3 0x00023bff41bc in grub_loader_boot
Bug#1067623: FTBFS: error: format ‘%ld’ expects argument of type ‘long int’, but argument 2 has type ‘__time64_t’ {aka ‘long long int’}
Control: tags -1 + pending I have NMU'd this package fixing this bug with Steve's patch - Thanks Steve! I have uploaded this to DELAYED/2 - please let me know if I should delay it further. Debdiff attached. best /Andreas Rönnquist gus...@debian.org acm_time_t64.debdiff Description: Binary data
Processed: Re: FTBFS: error: format ‘%ld’ expects argument of type ‘long int’, but argument 2 has type ‘__time64_t’ {aka ‘long long int’}
Processing control commands:
> tags -1 + pending
Bug #1067623 [src:acm] FTBFS: error: format ‘%ld’ expects argument of type
‘long int’, but argument 2 has type ‘__time64_t’ {aka ‘long long int’}
Added tag(s) pending.
--
1067623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:strace
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:strace > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1068758 (http://bugs.debian.org/1068758) > # Bug title: strace fails to build it's tests on arm-linux-gnueabihf with > 64bit time_t > # * https://github.com/strace/strace/issues/296 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1068758 + fixed-upstream Bug #1068758 [src:strace] strace fails to build it's tests on arm-linux-gnueabihf with 64bit time_t Added tag(s) fixed-upstream. > usertags 1068758 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1068758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:freebayes
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:freebayes > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1067271 (http://bugs.debian.org/1067271) > # Bug title: freebayes: FTBFS: dh_auto_test: error: cd build && > DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test > -v --timeout-multiplier 100 returned exit code 5 > # * https://github.com/freebayes/freebayes/issues/786 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1067271 + fixed-upstream Bug #1067271 [src:freebayes] freebayes: FTBFS: dh_auto_test: error: cd build && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test -v --timeout-multiplier 100 returned exit code 5 Added tag(s) fixed-upstream. > usertags 1067271 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1067271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:libapache2-mod-auth-cas
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:libapache2-mod-auth-cas > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #168 (http://bugs.debian.org/168) > # Bug title: libapache2-mod-auth-cas: depends on obsolete pcre3 library > # * https://github.com/apereo/mod_auth_cas/issues/208 > # * remote status changed: open -> closed > # * closed upstream > tags 168 + fixed-upstream Bug #168 [src:libapache2-mod-auth-cas] libapache2-mod-auth-cas: depends on obsolete pcre3 library Added tag(s) fixed-upstream. > usertags 168 - status-open Usertags were: status-open. There are now no usertags set. > usertags 168 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package nomacs
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package nomacs > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #974616 (http://bugs.debian.org/974616) > # Bug title: nomacs uses internal libexiv2 functions to get the user comment > # * https://github.com/nomacs/nomacs/pull/1049 > # * remote status changed: (?) -> closed > # * closed upstream > tags 974616 + fixed-upstream Bug #974616 [nomacs] nomacs uses internal libexiv2 functions to get the user comment Added tag(s) fixed-upstream. > usertags 974616 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 974616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974616 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:azure-cli
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:azure-cli > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1057393 (http://bugs.debian.org/1057393) > # Bug title: FTBFS: object has no attribute 'assertDictContainsSubset' > # * https://github.com/Azure/azure-cli/issues/28194 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1057393 + fixed-upstream Bug #1057393 [src:azure-cli] FTBFS: object has no attribute 'assertDictContainsSubset' Added tag(s) fixed-upstream. > usertags 1057393 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1057393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:pybdsf
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:pybdsf > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1063407 (http://bugs.debian.org/1063407) > # Bug title: pybdsf fails to build with Python 3.12 as default > # * https://github.com/lofar-astron/PyBDSF/issues/214 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1063407 + fixed-upstream Bug #1063407 [src:pybdsf] pybdsf fails to build with Python 3.12 as default Added tag(s) fixed-upstream. > usertags 1063407 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1063407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063407 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:jupyter-client
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:jupyter-client > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1059658 (http://bugs.debian.org/1059658) > # Bug title: jupyter-client: autopkgtest failure with Python 3.12 > # * https://github.com/jupyter/jupyter_client/pull/978 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1059658 + fixed-upstream Bug #1059658 [src:jupyter-client] jupyter-client: autopkgtest failure with Python 3.12 Added tag(s) fixed-upstream. > usertags 1059658 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1059658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:procdump
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:procdump > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1064137 (http://bugs.debian.org/1064137) > # Bug title: procdump no longer builds on mips64el/ppc64el/riscv64 > # * https://github.com/Sysinternals/ProcDump-for-Linux/pull/217 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1064137 + fixed-upstream Bug #1064137 [src:procdump] procdump no longer builds on mips64el/ppc64el/riscv64 Added tag(s) fixed-upstream. > usertags 1064137 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1064137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064137 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package hyperspy
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package hyperspy > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1041803 (http://bugs.debian.org/1041803) > # Bug title: hyperspy: FTBFS test_image fails > # * https://github.com/hyperspy/hyperspy/issues/3217 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1041803 + fixed-upstream Bug #1041803 [hyperspy] hyperspy: FTBFS test_image fails Added tag(s) fixed-upstream. > usertags 1041803 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1041803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041803 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:python-bottle
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:python-bottle > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1058087 (http://bugs.debian.org/1058087) > # Bug title: python-bottle: FTBFS: ImportError: cannot import name 'test' > from 'bottle.ext' (/<>/bottle.py) > # * https://github.com/bottlepy/bottle/issues/1378 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1058087 + fixed-upstream Bug #1058087 [src:python-bottle] python-bottle: FTBFS: ImportError: cannot import name 'test' from 'bottle.ext' (/<>/bottle.py) Added tag(s) fixed-upstream. > usertags 1058087 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:tracker
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:tracker > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1068468 (http://bugs.debian.org/1068468) > # Bug title: tracker: failing autopkgtest > # * https://gitlab.gnome.org/GNOME/tracker/-/issues/434 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1068468 + fixed-upstream Bug #1068468 [src:tracker] tracker: failing autopkgtest Added tag(s) fixed-upstream. > usertags 1068468 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1068468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069841: python-icalendar: FTBFS with tzdata 2024a: UnknownTimeZoneError: 'America/Godthab'
On Thu, 2024-04-25 at 18:13 +0100, Simon McVittie wrote: > Control: retitle -1 python-icalendar: FTBFS with tzdata 2024a: > UnknownTimeZoneError: 'America/Godthab' > > On Thu, 25 Apr 2024 at 18:27:15 +0200, Santiago Vila wrote: > > E pytz.exceptions.UnknownTimeZoneError: 'America/Godthab' > > This was presumably triggered by this change in tzdata 2024a-2: > > tzdata (2024a-2) unstable; urgency=medium > ... > * Replace America/Godthab by America/Nuuk > > which appears to have been an intentional compatibility break? America/Godthab has been moved to tzdata-legacy. The package could depend on tzdata-legacy or better do this replacement in WINDOWS_TO_OLSON as well. -- Benjamin Drung Debian & Ubuntu Developer
Processed (with 2 errors): Re: ncl: FTBFS (ld: cannot find -lNGras: No such file or directory)
Processing control commands: > tags -1 upstream Bug #1069845 [src:ncl] ncl: FTBFS (ld: cannot find -lNGras: No such file or directory) Added tag(s) upstream. > user debian-...@lists.debian.org Unknown command or malformed arguments to command. > usertag -1 hdf-4.3 Unknown command or malformed arguments to command. -- 1069845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069845: ncl: FTBFS (ld: cannot find -lNGras: No such file or directory)
Control: tags -1 upstream Control: user debian-...@lists.debian.org Control: usertag -1 hdf-4.3 On 4/25/24 7:35 PM, Bas Couwenberg wrote: The buildlogs shows many instances of these: /usr/bin/ld: cannot find -lNGctrans: No such file or directory /usr/bin/ld: cannot find -lNGras: No such file or directory The full buildlog is attached. It also shows: hdf.c:56:10: fatal error: dfgr.h: No such file or directory 56 | #include | ^~~~ This header is no longer provided by hdf 4.3.0, see: https://github.com/HDFGroup/hdf4/blob/hdf4.3.0/doc/HDF-4.2-to-4.3-migration.md#appendix-list-of-removed-header-files Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1069844: More debug info
On Thu, Apr 25, 2024 at 06:30:52PM +0100, Alex Bennée wrote: > > Continuing to debug on QEMU it seems there is an incompatibility with > the images and the peloader (which overrides the normal efi loader): > > Thread 1 hit Breakpoint 3.2, grub_load_normal_mode () at > ../../../grub-core/kern/main.c:241 > 241 in ../../../grub-core/kern/main.c > > > (grub gdb) hbreak do_load_image > > > Hardware assisted breakpoint 4 at 0x23bdf0e00: do_load_image. (2 locations) > > > (grub gdb) c > > > Continuing. > > > add symbol table from file "bli.module" at > > > .text_addr = 0x23ba772e0 > > > .bss_addr = 0x0 > > > .module_license_addr = 0x23ba7764a > .data_addr = 0x0 > > > .rodata.str1.1_addr = 0x23ba77560 > > > .rodata_addr = 0x23ba77550 > > > add symbol table from file "xen_boot.module" at > > > .text_addr = 0x23bcef3c0 > > > .bss_addr = 0x23bcf0370 > > > .module_license_addr = 0x23bcf035e > > .data_addr = 0x0 > > .rodata.str1.1_addr = 0x23bcefff8 > > Thread 1 hit Breakpoint 4.1, do_load_image (boot_policy=0 '\000', > parent_image_handle=0x23e889f18, file_path=0x237d1bce0, > source_buffer=0x239f0, source_size=1081352, > image_handle=0x4766c498) at ../../../grub-core/loader/efi/peimage.c:745 > warning: 745../../../grub-core/loader/efi/peimage.c: No such file or > directory > (grub gdb) hbreak grub_error > Hardware assisted breakpoint 5 at 0x6db0: grub_error. (2 locations) > (grub gdb) c > Continuing. > > Thread 1 hit Breakpoint 4.2, 0x00023bdf0e4c in do_load_image > (boot_policy=, parent_image_handle=, > image_handle=, > source_size=, source_buffer=, > file_path=) at ../../../grub-core/loader/efi/peimage.c:751 > 751 in ../../../grub-core/loader/efi/peimage.c > (grub gdb) c > Continuing. > > Thread 1 hit Breakpoint 5.2, grub_error (n=GRUB_ERR_BAD_OS, fmt=0x23bdf1703 > "section inside header") at ../../../grub-core/kern/err.c:41 > warning: 41 ../../../grub-core/kern/err.c: No such file or directory > (grub gdb) bt > #0 grub_error (n=GRUB_ERR_BAD_OS, fmt=0x23bdf1703 "section inside header") > at ../../../grub-core/kern/err.c:41 > #1 0x00023bdf0e34 in do_load_image (boot_policy=, > parent_image_handle=, file_path=, > source_buffer=, > source_size=, image_handle=) at > ../../../grub-core/loader/efi/peimage.c:747 > #2 0x00023bedabdc in grub_arch_efi_linux_boot_image (addr=9561964544, > size=1081352, > args=0x23bbb8b00 "placeholder dom0_mem=4G,max:4G loglvl=all > guest_loglvl=all no-real-mode edd=off") at > ../../../grub-core/loader/efi/linux.c:210 > #3 0x00023bff41bc in grub_loader_boot () at > ../../../grub-core/commands/boot.c:211 > #4 grub_loader_boot () at ../../../grub-core/commands/boot.c:190 > #5
Bug#1069844: More debug info
Continuing to debug on QEMU it seems there is an incompatibility with the images and the peloader (which overrides the normal efi loader): Thread 1 hit Breakpoint 3.2, grub_load_normal_mode () at ../../../grub-core/kern/main.c:241 241 in ../../../grub-core/kern/main.c (grub gdb) hbreak do_load_image Hardware assisted breakpoint 4 at 0x23bdf0e00: do_load_image. (2 locations) (grub gdb) c Continuing. add symbol table from file "bli.module" at .text_addr = 0x23ba772e0 .bss_addr = 0x0 .module_license_addr = 0x23ba7764a .data_addr = 0x0 .rodata.str1.1_addr = 0x23ba77560 .rodata_addr = 0x23ba77550 add symbol table from file "xen_boot.module" at .text_addr = 0x23bcef3c0 .bss_addr = 0x23bcf0370 .module_license_addr = 0x23bcf035e .data_addr = 0x0 .rodata.str1.1_addr = 0x23bcefff8 Thread 1 hit Breakpoint 4.1, do_load_image (boot_policy=0 '\000', parent_image_handle=0x23e889f18, file_path=0x237d1bce0, source_buffer=0x239f0, source_size=1081352, image_handle=0x4766c498) at ../../../grub-core/loader/efi/peimage.c:745 warning: 745../../../grub-core/loader/efi/peimage.c: No such file or directory (grub gdb) hbreak grub_error Hardware assisted breakpoint 5 at 0x6db0: grub_error. (2 locations) (grub gdb) c Continuing. Thread 1 hit Breakpoint 4.2, 0x00023bdf0e4c in do_load_image (boot_policy=, parent_image_handle=, image_handle=, source_size=, source_buffer=, file_path=) at ../../../grub-core/loader/efi/peimage.c:751 751 in ../../../grub-core/loader/efi/peimage.c (grub gdb) c Continuing. Thread 1 hit Breakpoint 5.2, grub_error (n=GRUB_ERR_BAD_OS, fmt=0x23bdf1703 "section inside header") at ../../../grub-core/kern/err.c:41 warning: 41 ../../../grub-core/kern/err.c: No such file or directory (grub gdb) bt #0 grub_error (n=GRUB_ERR_BAD_OS, fmt=0x23bdf1703 "section inside header") at ../../../grub-core/kern/err.c:41 #1 0x00023bdf0e34 in do_load_image (boot_policy=, parent_image_handle=, file_path=, source_buffer=, source_size=, image_handle=) at ../../../grub-core/loader/efi/peimage.c:747 #2 0x00023bedabdc in grub_arch_efi_linux_boot_image (addr=9561964544, size=1081352, args=0x23bbb8b00 "placeholder dom0_mem=4G,max:4G loglvl=all guest_loglvl=all no-real-mode edd=off") at ../../../grub-core/loader/efi/linux.c:210 #3 0x00023bff41bc in grub_loader_boot () at ../../../grub-core/commands/boot.c:211 #4 grub_loader_boot () at ../../../grub-core/commands/boot.c:190 #5 0x00023bf42158 in grub_command_execute (name=0x23bf4e72c "boot", argc=0, argv=0x0 <_start>) at ../../../include/grub/command.h:126 #6 grub_menu_execute_entry (entry=entry@entry=0x23bd17660, auto_boot=auto_boot@entry=0) at
Processed: found 1069630 in 2.0.0-1, notfound 1069800 in 21.1.4-1, found 1069800 in 24.1.4-1, tagging 1069790
Processing commands for cont...@bugs.debian.org: > found 1069630 2.0.0-1 Bug #1069630 [libcupsfilters2-dev] libcupsfilters-dev and libcupsfilters2-dev have an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libcupsfilters.a, /usr/lib/x86_64-linux-gnu/libcupsfilters.so and /usr/lib/x86_64-linux-gnu/pkgconfig/libcupsfilters.pc Marked as found in versions libcupsfilters/2.0.0-1. > notfound 1069800 21.1.4-1 Bug #1069800 [src:cloud-init] FTBFS: test failures in buildd environment The source 'cloud-init' and version '21.1.4-1' do not appear to match any binary packages No longer marked as found in versions cloud-init/21.1.4-1. > found 1069800 24.1.4-1 Bug #1069800 [src:cloud-init] FTBFS: test failures in buildd environment The source 'cloud-init' and version '24.1.4-1' do not appear to match any binary packages Marked as found in versions cloud-init/24.1.4-1. > tags 1069790 + sid trixie Bug #1069790 [librust-err-derive-dev] librust-err-derive-dev: impossible to install Added tag(s) sid and trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069630 1069790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069790 1069800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069800 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1069841: python-icalendar: FTBFS with tzdata 2024a: UnknownTimeZoneError: 'America/Godthab'
Processing control commands: > retitle -1 python-icalendar: FTBFS with tzdata 2024a: UnknownTimeZoneError: > 'America/Godthab' Bug #1069841 [src:python-icalendar] python-icalendar: FTBFS: pytz.exceptions.UnknownTimeZoneError: 'America/Godthab' Changed Bug title to 'python-icalendar: FTBFS with tzdata 2024a: UnknownTimeZoneError: 'America/Godthab'' from 'python-icalendar: FTBFS: pytz.exceptions.UnknownTimeZoneError: 'America/Godthab''. -- 1069841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069841 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069841: python-icalendar: FTBFS with tzdata 2024a: UnknownTimeZoneError: 'America/Godthab'
Control: retitle -1 python-icalendar: FTBFS with tzdata 2024a: UnknownTimeZoneError: 'America/Godthab' On Thu, 25 Apr 2024 at 18:27:15 +0200, Santiago Vila wrote: > E pytz.exceptions.UnknownTimeZoneError: 'America/Godthab' This was presumably triggered by this change in tzdata 2024a-2: tzdata (2024a-2) unstable; urgency=medium ... * Replace America/Godthab by America/Nuuk which appears to have been an intentional compatibility break? smcv
Processed: Re: Bug#1069835: libreoffice-kf5: documents may get lost on SMB shares
Processing control commands:
> found -1 libreoffice/4:24.2.3~rc1-3
Bug #1069835 {Done: Rene Engelhard } [libreoffice-kf5]
libreoffice-kf5: documents may get lost on SMB shares
Marked as found in versions libreoffice/4:24.2.3~rc1-3 and reopened.
> notfixed -1 libreoffice/4:24.2.2-1
Bug #1069835 [libreoffice-kf5] libreoffice-kf5: documents may get lost on SMB
shares
No longer marked as fixed in versions libreoffice/4:24.2.2-1.
> reopen -1
Bug #1069835 [libreoffice-kf5] libreoffice-kf5: documents may get lost on SMB
shares
Bug 1069835 is not marked as done; doing nothing.
> tags -1 - moreinfo
Bug #1069835 [libreoffice-kf5] libreoffice-kf5: documents may get lost on SMB
shares
Removed tag(s) moreinfo.
--
1069835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069835
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1069835: libreoffice-kf5: documents may get lost on SMB shares
Control: found -1 libreoffice/4:24.2.3~rc1-3 Control: notfixed -1 libreoffice/4:24.2.2-1 Control: reopen -1 Control: tags -1 - moreinfo Hi again, On Thu, Apr 25, 2024 at 06:43:17PM +0200, Rene Engelhard wrote: > Am 25.04.24 um 18:37 schrieb Andreas B. Mundt: > > On Thu, Apr 25, 2024 at 05:43:29PM +0200, Rene Engelhard wrote: > > > Am 25.04.24 um 17:03 schrieb Andreas B. Mundt: > > > > For now, we traced the issue back to libreoffice-kf5. If this package > > > > is removed, neither the document disappears on closing libreoffice nor > > > > the popup is shown when 'nobrl' is removed from the mount options. > > > Which doesn't do IO itself though? But maybe the KDE file picker (over > > > kio) > > > does something weird? But saving (ttbomk) isn't done by the file picker > > > itself? > > I just tried a trixie XFCE desktop and cannot reproduce the issue > > there. Then I installed KDE and switched the DE. In KDE again the > > issue is reproducable, removing libreoffice-kf5 makes the problem go > > away. Installing libreoffice-kf5 again: Issue is back. > Shrugs. > > However, back in XFCE, even with libreoffice-kf5 installed, the issue > > does not show up. > > Because in XFCE you don't get the KDE File Picker but the Gtk one. > > Unless you force kf5, which I don't think you do. Right. > > The different file chooser GUIs seem to trigger the > > issue. > Interesting. > > Removing libreoffice-kf5 or switching to XFCE results in a > > different file chooser, which somehow causes the problem. So the bug > > is probably not in libreoffice-kf5 … > > -kf5 does contain the KDE file picker used in LibreOffice. > > > In any case, try with >= 24.2.2 (so sid). If that commit was it (which I > somehow doubt, see my previous reply) sid should work. I upgraded libreoffice to the version in sid now -- it seems not to happen as often as before, but I could reproduce it still a few more times. Not sure which package to reassign the bug to. Best regards, Andi
Bug#1069804: marked as done (rust-mio-0.6 accesses network resources during the build)
Your message dated Thu, 25 Apr 2024 17:04:33 +
with message-id
and subject line Bug#1069804: fixed in rust-mio-0.6 0.6.23-4
has caused the Debian Bug report #1069804,
regarding rust-mio-0.6 accesses network resources during the build
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1069804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-mio-0.6
Version: 0.6.23-3
Severity: serious
Tags: sid trixie ftbfs
rust-mio-0.6 accesses network resources during the build:
Test executable failed (exit status: 101).
stderr:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os {
code: 101, kind: NetworkUnreachable, message: "Network is unreachable" }',
src/sys/unix/ready.rs:22:16
stack backtrace:
0: rust_begin_unwind
at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5
1: core::panicking::panic_fmt
at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14
2: core::result::unwrap_failed
at /usr/src/rustc-1.70.0/library/core/src/result.rs:1687:5
3: core::result::Result::unwrap
4: rust_out::main
5: core::ops::function::FnOnce::call_once
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose
backtrace.
failures:
src/poll.rs - poll::Poll (line 267)
src/poll.rs - poll::Poll::deregister (line 877)
src/poll.rs - poll::Poll::register (line 735)
src/poll.rs - poll::Poll::reregister (line 820)
src/sys/unix/ready.rs - sys::unix::ready::UnixReady (line 66)
test result: FAILED. 74 passed; 5 failed; 0 ignored; 0 measured; 0 filtered
out; finished in 4.37s
--- End Message ---
--- Begin Message ---
Source: rust-mio-0.6
Source-Version: 0.6.23-4
Done: Peter Michael Green
We believe that the bug you reported is fixed in the latest version of
rust-mio-0.6, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1069...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Peter Michael Green (supplier of updated rust-mio-0.6
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 25 Apr 2024 16:47:57 +
Source: rust-mio-0.6
Architecture: source
Version: 0.6.23-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers
Changed-By: Peter Michael Green
Closes: 1069804
Changes:
rust-mio-0.6 (0.6.23-4) unstable; urgency=medium
.
* Team upload.
* Package mio 0.6.23 from crates.io using debcargo 2.6.1
* Don't fail build due to compiler warnings.
* Skip tests that require internet (Closes: #1069804)
Checksums-Sha1:
7f2683a079312744eb8570eb8471a79d7aaa761e 2714 rust-mio-0.6_0.6.23-4.dsc
0b6712c4e05f9973bd43aaf8e8fc8aa84b8f3cfa 4232
rust-mio-0.6_0.6.23-4.debian.tar.xz
d60bf89089e6e5ce931e01b21c740d64ef523672 10731
rust-mio-0.6_0.6.23-4_source.buildinfo
Checksums-Sha256:
43b1e54817cbd8b28f646a28b6b7430cd84698155b7bc555219e643cd1d4d289 2714
rust-mio-0.6_0.6.23-4.dsc
d5fd8fdb87f26abaa0d4f540568fda30568bfa42d48e8cd40400785b94a007cb 4232
rust-mio-0.6_0.6.23-4.debian.tar.xz
dd35036fc711ec1f794b39a44f1e3f3d1055fb43b59285f20a5ce00daa99feae 10731
rust-mio-0.6_0.6.23-4_source.buildinfo
Files:
5e64b42fd5b75c6ace0827cdccf89067 2714 rust optional rust-mio-0.6_0.6.23-4.dsc
c64fdc533b45bd1e0a27d6a3c58fb645 4232 rust optional
rust-mio-0.6_0.6.23-4.debian.tar.xz
45ef0bc46a7964aa34b973b5871b04c7 10731 rust optional
rust-mio-0.6_0.6.23-4_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmYqiVEUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XubUQ/9Fxe4/LUdQN/kA1qtboxtWhdM6PRo
8crTBusrV+6CCNnV9nvD5b1BhUwx6xHP/rvOe2RyB0+r2KMMAq8GcdhbmHYmJFGZ
45pPhV4E1ZpNWoni6jnFqImQnmOhkrwAXhsVMoMJf4/n/HW3ZDsL2G+fLltWvNwT
b5C/VN/10UGwmrvTngLSrV12broMZxe/3fuGQKajAHFhk/5Gi3wtPbyCJLKaWkkn
Yq0EjxIPeDnX7xnQ8u4mzDtZ1mBBE6d1ZI4S9TAKddV5Kd3TwzfjPcQfPi33u7V1
Yhefnob+J+kHjL8hNw7zDAVu4f2fdqha6cUx+n3G32Eg/keDmtD6ZWdDVKIePrOY
Q6lvBLtUctRRUKaUZBJTkqsaLHq7XBMfL+MbhFIvFpggQu14kCn8qSW6BeWSoXqQ
k19Qt3WrSbOHO+Tz7bQQZ6M2cSLT8JYJzcRx9RHINyZmmaTwJ+CmvJ0uAGdQzLTM
Bug#1069842: rjava: FTBFS: /usr/bin/ld: cannot find -ldeflate: No such file or directory
reassign 1069842 r-base thanks On 25 April 2024 at 18:27, Santiago Vila wrote: | Package: src:rjava | Version: 1.0-11-1 | Severity: serious | Tags: ftbfs | | Dear maintainer: | | During a rebuild of all packages in unstable, your package failed to build: Thanks for this. It is caused by the just released R 4.4.0 which now uses libdeflate, gets it somehow already via its Build-Depends but then does not implicitly pass it on via its virtual (child) package r-base-dev and its depends. (Both have a list of lib*-dev compression packages.) I will make a r-base 4.4.0-2 either today or tomorrow to correct this and have r-base-dev explicitly list libdeflate-dev. Dirk | | | [...] | debian/rules build | dh build --buildsystem R | dh_update_autotools_config -O--buildsystem=R | cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead | cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead | dh_autoreconf -O--buildsystem=R | dh_auto_configure -O--buildsystem=R | dh_auto_build -O--buildsystem=R | dh_auto_test -O--buildsystem=R | create-stamp debian/debhelper-build-stamp | fakeroot debian/rules binary | dh binary --buildsystem R | dh_testroot -O--buildsystem=R | dh_prep -O--buildsystem=R | dh_auto_install --destdir=debian/r-cran-rjava/ -O--buildsystem=R | I: R Package: rJava Version: 1.0-11 | I: Building using R version 4.4.0-1 | I: R API version: r-api-4.0 | I: Using built-time from d/changelog: Fri, 26 Jan 2024 11:10:09 -0600 | mkdir -p /<>/debian/r-cran-rjava/usr/lib/R/site-library | R CMD INSTALL -l /<>/debian/r-cran-rjava/usr/lib/R/site-library --clean . "--built-timestamp='Fri, 26 Jan 2024 11:10:09 -0600'" | * installing *source* package ‘rJava’ ... | files ‘configure’, ‘jri/tools/config.guess’, ‘jri/tools/config.sub’, ‘src/config.h.in’ have the wrong MD5 checksums | ** using staged installation | checking for gcc... gcc | checking whether the C compiler works... yes | checking for C compiler default output file name... a.out | checking for suffix of executables... | checking whether we are cross compiling... no | checking for suffix of object files... o | checking whether the compiler supports GNU C... yes | checking whether gcc accepts -g... yes | checking for gcc option to enable C11 features... none needed | checking for sys/wait.h that is POSIX.1 compatible... yes | checking for stdio.h... yes | checking for stdlib.h... yes | checking for string.h... yes | checking for inttypes.h... yes | checking for stdint.h... yes | checking for strings.h... yes | checking for sys/stat.h... yes | checking for sys/types.h... yes | checking for unistd.h... yes | checking for string.h... (cached) yes | checking for sys/time.h... yes | checking for unistd.h... (cached) yes | checking for an ANSI C-conforming const... yes | configure: checking whether gcc supports static inline... | yes | checking whether setjmp.h is POSIX.1 compatible... yes | checking for gcc options needed to detect all undeclared functions... none needed | checking whether sigsetjmp is declared... yes | checking whether siglongjmp is declared... yes | checking Java support in R... present: | interpreter : '/usr/lib/jvm/default-java/bin/java' | archiver: '/usr/lib/jvm/default-java/bin/jar' | compiler: '/usr/lib/jvm/default-java/bin/javac' | header prep.: '' | cpp flags : '-I/usr/lib/jvm/default-java/include -I/usr/lib/jvm/default-java/include/linux' | java libs : '-L/usr/lib/jvm/default-java/lib/server -ljvm' | checking whether Java run-time works... yes | checking whether -Xrs is supported... yes | checking whether -Xrs will be used... yes | checking whether JVM will be loaded dynamically... no | checking whether JNI programs can be compiled... yes | checking whether JNI programs run... yes | checking JNI data types... ok | checking whether JRI should be compiled (autodetect)... yes | checking whether debugging output should be enabled... no | checking whether memory profiling is desired... no | checking whether threads support is requested... no | checking whether callbacks support is requested... no | checking whether JNI cache support is requested... no | checking whether headless init is enabled... no | checking whether JRI is requested... yes | configure: creating ./config.status | config.status: creating src/Makevars | config.status: creating R/zzz.R | config.status: creating src/config.h | === configuring in jri (/<>/jri) | configure: running /bin/bash ./configure --disable-option-checking '--prefix=/usr/local' 'CC=gcc' 'CFLAGS=-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection' 'LDFLAGS=-Wl,-z,relro' 'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2' --cache-file=/dev/null --srcdir=. | checking
Processed: Re: Bug#1069842: rjava: FTBFS: /usr/bin/ld: cannot find -ldeflate: No such file or directory
Processing commands for cont...@bugs.debian.org: > reassign 1069842 r-base Bug #1069842 [src:rjava] rjava: FTBFS: /usr/bin/ld: cannot find -ldeflate: No such file or directory Bug reassigned from package 'src:rjava' to 'r-base'. No longer marked as found in versions rjava/1.0-11-1. Ignoring request to alter fixed versions of bug #1069842 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1069842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069842 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1069835: libreoffice-kf5: documents may get lost on SMB shares
Processing control commands:
> found -1 libreoffice/4:24.2.0-1
Bug #1069835 {Done: Rene Engelhard } [libreoffice-kf5]
libreoffice-kf5: documents may get lost on SMB shares
Marked as found in versions libreoffice/4:24.2.0-1.
--
1069835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069835
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1069835: libreoffice-kf5: documents may get lost on SMB shares
Control: found -1 libreoffice/4:24.2.0-1 Hi Rene, thanks for your quick reply and sorry for not providing detailed version information! On Thu, Apr 25, 2024 at 05:43:29PM +0200, Rene Engelhard wrote: > > Am 25.04.24 um 17:03 schrieb Andreas B. Mundt: > > For now, we traced the issue back to libreoffice-kf5. If this package > > is removed, neither the document disappears on closing libreoffice nor > > the popup is shown when 'nobrl' is removed from the mount options. > > Which doesn't do IO itself though? But maybe the KDE file picker (over kio) > does something weird? But saving (ttbomk) isn't done by the file picker > itself? I just tried a trixie XFCE desktop and cannot reproduce the issue there. Then I installed KDE and switched the DE. In KDE again the issue is reproducable, removing libreoffice-kf5 makes the problem go away. Installing libreoffice-kf5 again: Issue is back. However, back in XFCE, even with libreoffice-kf5 installed, the issue does not show up. The different file chooser GUIs seem to trigger the issue. Removing libreoffice-kf5 or switching to XFCE results in a different file chooser, which somehow causes the problem. So the bug is probably not in libreoffice-kf5 … Best regards, Andi
Bug#1069835: libreoffice-kf5: documents may get lost on SMB shares
Hi, Am 25.04.24 um 18:37 schrieb Andreas B. Mundt: On Thu, Apr 25, 2024 at 05:43:29PM +0200, Rene Engelhard wrote: Am 25.04.24 um 17:03 schrieb Andreas B. Mundt: For now, we traced the issue back to libreoffice-kf5. If this package is removed, neither the document disappears on closing libreoffice nor the popup is shown when 'nobrl' is removed from the mount options. Which doesn't do IO itself though? But maybe the KDE file picker (over kio) does something weird? But saving (ttbomk) isn't done by the file picker itself? I just tried a trixie XFCE desktop and cannot reproduce the issue there. Then I installed KDE and switched the DE. In KDE again the issue is reproducable, removing libreoffice-kf5 makes the problem go away. Installing libreoffice-kf5 again: Issue is back. Shrugs. However, back in XFCE, even with libreoffice-kf5 installed, the issue does not show up. Because in XFCE you don't get the KDE File Picker but the Gtk one. Unless you force kf5, which I don't think you do. The different file chooser GUIs seem to trigger the issue. Interesting. Removing libreoffice-kf5 or switching to XFCE results in a different file chooser, which somehow causes the problem. So the bug is probably not in libreoffice-kf5 … -kf5 does contain the KDE file picker used in LibreOffice. In any case, try with >= 24.2.2 (so sid). If that commit was it (which I somehow doubt, see my previous reply) sid should work. Regards, Rene
Bug#1069844: grub-efi-arm64: grub fails to load Xen hypervisor on arm64 EFI systems (AVA & QEMU)
Package: grub-efi-arm64 Version: 2.12-2~deb13u1 Severity: serious Attempting to boot Xen on an arm64 EFI system fails. Further attempts to select another boot entry fails and the system needs to be rebooted before you can load the kernel without Xen. This is likely due to boot services having been unloaded. Running on the Ampere AVA platform with additional diagnostics (xen,xen_loader,efiemu,fdt,linux) gets the following: loader/arm64/xen_boot.c:116:xen_loader: Xen Hypervisor cmdline : placeholder no-real-mode edd=off @ 0x807ff98a6e0 size:33 loader/arm64/xen_boot.c:224:xen_loader: Module @ 0xf283b000 size:0x1f2c75b loader/arm64/xen_boot.c:139:xen_loader: Module node name module@f283b000 loader/arm64/xen_boot.c:161:xen_loader: Module loader/arm64/xen_boot.c:183:xen_loader: Module has no bootargs! loader/arm64/xen_boot.c:224:xen_loader: Module @ 0xef17d000 size:0x3514a00 loader/arm64/xen_boot.c:139:xen_loader: Module node name module@ef17d000 loader/arm64/xen_boot.c:161:xen_loader: Module loader/arm64/xen_boot.c:172:xen_loader: Module cmdline : placeholder root=UUID=06e49159-b374-445c-bf5f-2bf93e3f4d6b ro @ 0x807ffa1a3a0 size:62 loader/arm64/xen_boot.c:224:xen_loader: Module @ 0xf4769000 size:0x3514a00 loader/arm64/xen_boot.c:139:xen_loader: Module node name module@f4769000 loader/arm64/xen_boot.c:161:xen_loader: Module loader/arm64/xen_boot.c:172:xen_loader: Module cmdline : placeholder root=UUID=06e49159-b374-445c-bf5f-2bf93e3f4d6b ro @ 0x807fd65a280 size:62 loader/efi/fdt.c:136:fdt: Installed/updated FDT configuration table @ 0xef16 error: cannot load image. So it appears EFI boot services can successfully stat the various bits and pieces but once it gets to the stage of grub_arch_efi_linux_boot_image it fails. As debugging grub on the AVA platform is hard I replicated the setup in QEMU. At which point I obtained the following backtrace: Thread 1 hit Breakpoint 6.2, grub_error (n=GRUB_ERR_BAD_OS, fmt=0x23bedbbbd "cannot load image") at ../../../grub-core/kern/err.c:41 41grub_errno = n; (grub gdb) bt #0 grub_error (n=GRUB_ERR_BAD_OS, fmt=0x23bedbbbd "cannot load image") at ../../../grub-core/kern/err.c:41 #1 0x00023bedabf0 in grub_arch_efi_linux_boot_image (addr=9561964544, size=1081352, args=0x23bbb8b00 "placeholder dom0_mem=4G,max:4G loglvl=all guest_loglvl=all no-real-mode edd=off") at ../../../grub-core/loader/efi/linux.c:214 #2 0x00023bff41bc in grub_loader_boot () at ../../../grub-core/commands/boot.c:211 #3 grub_loader_boot () at ../../../grub-core/commands/boot.c:190 #4 0x00023bf42158 in grub_command_execute (name=0x23bf4e72c "boot", argc=0, argv=0x0 <_start>) at ../../../include/grub/command.h:126 #5 grub_menu_execute_entry (entry=entry@entry=0x23bd17660, auto_boot=auto_boot@entry=0) at ../../../grub-core/normal/menu.c:306 #6 0x00023bf41e2c in show_menu (autobooted=, nested=, menu=) at ../../../grub-core/normal/menu.c:925 #7 grub_show_menu (menu=menu@entry=0x23bd1a940, nested=nested@entry=1, autoboot=autoboot@entry=0) at ../../../grub-core/normal/menu.c:940 #8 0x00023bf408a8 in grub_normal_execute (config=, nested=nested@entry=1, batch=batch@entry=0) at ../../../grub-core/normal/main.c:291 #9 0x00023bf32260 in grub_cmd_source (cmd=, argc=1, args=0x23bd1fcc8) at ../../../grub-core/commands/configfile.c:48 #10 grub_cmd_source (cmd=, argc=, args=0x23bd1fcc8) at ../../../grub-core/commands/configfile.c:30 #11 0x00023bf48d0c in grub_script_execute_cmdline (cmd=) at ../../../grub-core/script/execute.c:1034 #12 0x00023bf478c0 in grub_script_execute_cmd (cmd=cmd@entry=0x23bd190c8) at ../../../grub-core/script/execute.c:819 #13 0x00023bf4874c in grub_script_execute_cmdlist (list=) at ../../../grub-core/script/execute.c:1079 #14 0x00023bf478c0 in grub_script_execute_cmd (cmd=) at ../../../grub-core/script/execute.c:819 #15 0x00023bf489b4 in grub_script_execute (script=) at ../../../grub-core/script/execute.c:1191 #16 0x00023bf497fc in grub_normal_parse_line (line=line@entry=0x23bd20060 "configfile $prefix/grub.cfg", getline=getline@entry=0x23bf40430 , getline_data=getline_data@entry=0x23bd20380) at ../../../grub-core/script/main.c:36 #17 0x00023bf409a0 in read_config_file (config=0x23bd20780 "(hd0,gpt1)/EFI/debian/grub.cfg") at ../../../grub-core/normal/main.c:179 #18 grub_normal_execute (config=config@entry=0x23bd20780 "(hd0,gpt1)/EFI/debian/grub.cfg", nested=nested@entry=0, batch=batch@entry=0) at ../../../grub-core/normal/main.c:277 #19 0x00023bf40ca4 in grub_enter_normal_mode (config=config@entry=0x23bd20780 "(hd0,gpt1)/EFI/debian/grub.cfg") at ../../../grub-core/normal/main.c:304 #20 0x00023bf40da0 in grub_try_normal_prefix (prefix=0x23bd209a0 "(hd0,gpt1)/EFI/debian") at ../../../grub-core/normal/main.c:356 #21 0x00023bf40ea0 in grub_try_normal (variable=0x23bf4e492
Bug#1069843: zarr: FTBFS: failing tests
Package: src:zarr Version: 2.17.2+ds-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild dh_auto_build -O--buildsystem=pybuild I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" module I: pybuild base:311: python3.12 -m build --skip-dependency-check --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12_zarr * Building wheel... running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/zarr copying zarr/hierarchy.py -> build/lib/zarr copying zarr/__init__.py -> build/lib/zarr copying zarr/storage.py -> build/lib/zarr copying zarr/meta_v1.py -> build/lib/zarr copying zarr/creation.py -> build/lib/zarr copying zarr/types.py -> build/lib/zarr copying zarr/util.py -> build/lib/zarr copying zarr/core.py -> build/lib/zarr copying zarr/indexing.py -> build/lib/zarr copying zarr/codecs.py -> build/lib/zarr copying zarr/convenience.py -> build/lib/zarr copying zarr/errors.py -> build/lib/zarr copying zarr/version.py -> build/lib/zarr copying zarr/attrs.py -> build/lib/zarr copying zarr/n5.py -> build/lib/zarr copying zarr/context.py -> build/lib/zarr copying zarr/sync.py -> build/lib/zarr copying zarr/meta.py -> build/lib/zarr creating build/lib/zarr/_storage copying zarr/_storage/__init__.py -> build/lib/zarr/_storage copying zarr/_storage/absstore.py -> build/lib/zarr/_storage copying zarr/_storage/v3.py -> build/lib/zarr/_storage copying zarr/_storage/store.py -> build/lib/zarr/_storage copying zarr/_storage/v3_storage_transformers.py -> build/lib/zarr/_storage creating build/lib/zarr/tests copying zarr/tests/test_sync.py -> build/lib/zarr/tests copying zarr/tests/__init__.py -> build/lib/zarr/tests copying zarr/tests/test_meta.py -> build/lib/zarr/tests copying zarr/tests/test_core.py -> build/lib/zarr/tests copying zarr/tests/test_dim_separator.py -> build/lib/zarr/tests copying zarr/tests/test_storage_v3.py -> build/lib/zarr/tests copying zarr/tests/test_convenience.py -> build/lib/zarr/tests copying zarr/tests/test_n5.py -> build/lib/zarr/tests copying zarr/tests/test_storage.py -> build/lib/zarr/tests copying zarr/tests/test_hierarchy.py -> build/lib/zarr/tests copying zarr/tests/util.py -> build/lib/zarr/tests copying zarr/tests/test_attrs.py -> build/lib/zarr/tests copying zarr/tests/test_creation.py -> build/lib/zarr/tests copying zarr/tests/conftest.py -> build/lib/zarr/tests copying zarr/tests/test_info.py -> build/lib/zarr/tests copying zarr/tests/test_filters.py -> build/lib/zarr/tests copying zarr/tests/test_util.py -> build/lib/zarr/tests copying zarr/tests/test_indexing.py -> build/lib/zarr/tests copying zarr/tests/test_meta_array.py -> build/lib/zarr/tests running egg_info creating zarr.egg-info writing zarr.egg-info/PKG-INFO writing dependency_links to zarr.egg-info/dependency_links.txt writing requirements to zarr.egg-info/requires.txt writing top-level names to zarr.egg-info/top_level.txt writing manifest file 'zarr.egg-info/SOURCES.txt' reading manifest file 'zarr.egg-info/SOURCES.txt' adding license file 'LICENSE.txt' writing manifest file 'zarr.egg-info/SOURCES.txt' installing to build/bdist.linux-x86_64/wheel running install running install_lib creating build/bdist.linux-x86_64 creating build/bdist.linux-x86_64/wheel creating build/bdist.linux-x86_64/wheel/zarr copying build/lib/zarr/hierarchy.py -> build/bdist.linux-x86_64/wheel/zarr copying build/lib/zarr/__init__.py -> build/bdist.linux-x86_64/wheel/zarr copying build/lib/zarr/storage.py -> build/bdist.linux-x86_64/wheel/zarr creating build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/test_sync.py -> build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/__init__.py -> build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/test_meta.py -> build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/test_core.py -> build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/test_dim_separator.py -> build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/test_storage_v3.py -> build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/test_convenience.py -> build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/test_n5.py -> build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/test_storage.py -> build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/test_hierarchy.py -> build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/util.py -> build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/test_attrs.py ->
Bug#1069841: python-icalendar: FTBFS: pytz.exceptions.UnknownTimeZoneError: 'America/Godthab'
Package: src:python-icalendar Version: 5.0.11-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild dh_auto_build -O--buildsystem=pybuild I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" module I: pybuild base:311: python3.12 -m build --skip-dependency-check --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12_icalendar * Building wheel... running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/icalendar copying src/icalendar/__init__.py -> build/lib/icalendar copying src/icalendar/windows_to_olson.py -> build/lib/icalendar copying src/icalendar/timezone_cache.py -> build/lib/icalendar copying src/icalendar/prop.py -> build/lib/icalendar copying src/icalendar/caselessdict.py -> build/lib/icalendar copying src/icalendar/tools.py -> build/lib/icalendar copying src/icalendar/parser.py -> build/lib/icalendar copying src/icalendar/cli.py -> build/lib/icalendar copying src/icalendar/cal.py -> build/lib/icalendar copying src/icalendar/parser_tools.py -> build/lib/icalendar creating build/lib/icalendar/tests copying src/icalendar/tests/test_issue_322_single_strings_characters_split_into_multiple_categories.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_unit_parser_tools.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_recurrence.py -> build/lib/icalendar/tests copying src/icalendar/tests/__init__.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_issue_348_exception_parsing_value.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_cli_tool.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_issue_500_vboolean_for_parameter.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_unit_tools.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_time.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_unit_cal.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_issue_318_skip_default_parameters.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_issue_168_parsing_invalid_calendars_no_warning.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_icalendar.py -> build/lib/icalendar/tests copying src/icalendar/tests/conftest.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_fixed_issues.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_issue_557_encode_native_parameters.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_unit_caselessdict.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_issue_27_period.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_issue_165_missing_event.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_examples.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_property_params.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_timezoned.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_with_doctest.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_equality.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_multiple.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_components_break_on_bad_ics.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_parsing.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_encoding.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_unit_prop.py -> build/lib/icalendar/tests copying src/icalendar/tests/test_period.py -> build/lib/icalendar/tests creating build/lib/icalendar/tests/hypothesis copying src/icalendar/tests/hypothesis/test_fuzzing.py -> build/lib/icalendar/tests/hypothesis running egg_info creating src/icalendar.egg-info writing src/icalendar.egg-info/PKG-INFO writing dependency_links to src/icalendar.egg-info/dependency_links.txt writing entry points to src/icalendar.egg-info/entry_points.txt writing requirements to src/icalendar.egg-info/requires.txt writing top-level names to src/icalendar.egg-info/top_level.txt writing manifest file 'src/icalendar.egg-info/SOURCES.txt' reading manifest file 'src/icalendar.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files matching '*.pyc' found under directory 'src/icalendar' warning: no previously-included files matching '*~' found under directory 'src/icalendar' adding license file 'LICENSE.rst' writing manifest file 'src/icalendar.egg-info/SOURCES.txt' copying src/icalendar/tests/test_create_release.sh -> build/lib/icalendar/tests creating
Bug#1069842: rjava: FTBFS: /usr/bin/ld: cannot find -ldeflate: No such file or directory
Package: src:rjava Version: 1.0-11-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules build dh build --buildsystem R dh_update_autotools_config -O--buildsystem=R cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead dh_autoreconf -O--buildsystem=R dh_auto_configure -O--buildsystem=R dh_auto_build -O--buildsystem=R dh_auto_test -O--buildsystem=R create-stamp debian/debhelper-build-stamp fakeroot debian/rules binary dh binary --buildsystem R dh_testroot -O--buildsystem=R dh_prep -O--buildsystem=R dh_auto_install --destdir=debian/r-cran-rjava/ -O--buildsystem=R I: R Package: rJava Version: 1.0-11 I: Building using R version 4.4.0-1 I: R API version: r-api-4.0 I: Using built-time from d/changelog: Fri, 26 Jan 2024 11:10:09 -0600 mkdir -p /<>/debian/r-cran-rjava/usr/lib/R/site-library R CMD INSTALL -l /<>/debian/r-cran-rjava/usr/lib/R/site-library --clean . "--built-timestamp='Fri, 26 Jan 2024 11:10:09 -0600'" * installing *source* package ‘rJava’ ... files ‘configure’, ‘jri/tools/config.guess’, ‘jri/tools/config.sub’, ‘src/config.h.in’ have the wrong MD5 checksums ** using staged installation checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether the compiler supports GNU C... yes checking whether gcc accepts -g... yes checking for gcc option to enable C11 features... none needed checking for sys/wait.h that is POSIX.1 compatible... yes checking for stdio.h... yes checking for stdlib.h... yes checking for string.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for strings.h... yes checking for sys/stat.h... yes checking for sys/types.h... yes checking for unistd.h... yes checking for string.h... (cached) yes checking for sys/time.h... yes checking for unistd.h... (cached) yes checking for an ANSI C-conforming const... yes configure: checking whether gcc supports static inline... yes checking whether setjmp.h is POSIX.1 compatible... yes checking for gcc options needed to detect all undeclared functions... none needed checking whether sigsetjmp is declared... yes checking whether siglongjmp is declared... yes checking Java support in R... present: interpreter : '/usr/lib/jvm/default-java/bin/java' archiver: '/usr/lib/jvm/default-java/bin/jar' compiler: '/usr/lib/jvm/default-java/bin/javac' header prep.: '' cpp flags : '-I/usr/lib/jvm/default-java/include -I/usr/lib/jvm/default-java/include/linux' java libs : '-L/usr/lib/jvm/default-java/lib/server -ljvm' checking whether Java run-time works... yes checking whether -Xrs is supported... yes checking whether -Xrs will be used... yes checking whether JVM will be loaded dynamically... no checking whether JNI programs can be compiled... yes checking whether JNI programs run... yes checking JNI data types... ok checking whether JRI should be compiled (autodetect)... yes checking whether debugging output should be enabled... no checking whether memory profiling is desired... no checking whether threads support is requested... no checking whether callbacks support is requested... no checking whether JNI cache support is requested... no checking whether headless init is enabled... no checking whether JRI is requested... yes configure: creating ./config.status config.status: creating src/Makevars config.status: creating R/zzz.R config.status: creating src/config.h === configuring in jri (/<>/jri) configure: running /bin/bash ./configure --disable-option-checking '--prefix=/usr/local' 'CC=gcc' 'CFLAGS=-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection' 'LDFLAGS=-Wl,-z,relro' 'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2' --cache-file=/dev/null --srcdir=. checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether the compiler supports GNU C... yes checking whether gcc accepts -g... yes checking for gcc option to enable C11 features... none needed checking for stdio.h... yes checking for stdlib.h... yes checking for string.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for strings.h... yes checking for
Bug#1069838: khard: FTBFS: ERROR: test_query (unittest.loader._FailedTest.test_query)
Package: src:khard Version: 0.19.1-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules build dh build --with python3 --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:311: python3.12 setup.py config running config I: pybuild base:311: python3.11 setup.py config running config debian/rules override_dh_auto_build make[1]: Entering directory '/<>' cd doc && \ make html && \ make text && \ make man make[2]: Entering directory '/<>/doc' Running Sphinx v7.2.6 making output directory... done [2K[AutoAPI] Reading files... [ 7%] /<>/khard/__init__.py [2K[AutoAPI] Reading files... [ 14%] /<>/khard/khard.py [2K[AutoAPI] Reading files... [ 21%] /<>/khard/__main__.py [2K[AutoAPI] Reading files... [ 29%] /<>/khard/actions.py [2K[AutoAPI] Reading files... [ 36%] /<>/khard/query.py [2K[AutoAPI] Reading files... [ 43%] /<>/khard/carddav_object.py [2K[AutoAPI] Reading files... [ 50%] /<>/khard/address_book.py [2K[AutoAPI] Reading files... [ 57%] /<>/khard/version.py [2K[AutoAPI] Reading files... [ 64%] /<>/khard/cli.py [2K[AutoAPI] Reading files... [ 71%] /<>/khard/formatter.py [2K[AutoAPI] Reading files... [ 79%] /<>/khard/config.py [2K[AutoAPI] Reading files... [ 86%] /<>/khard/helpers/__init__.py [2K[AutoAPI] Reading files... [ 93%] /<>/khard/helpers/typing.py [2K[AutoAPI] Reading files... [100%] /<>/khard/helpers/interactive.py [2K[AutoAPI] Mapping Data... [ 7%] /<>/khard/__init__.py [2K[AutoAPI] Mapping Data... [ 14%] /<>/khard/khard.py [2K[AutoAPI] Mapping Data... [ 21%] /<>/khard/__main__.py [2K[AutoAPI] Mapping Data... [ 29%] /<>/khard/actions.py [2K[AutoAPI] Mapping Data... [ 36%] /<>/khard/query.py [2K[AutoAPI] Mapping Data... [ 43%] /<>/khard/carddav_object.py [2K[AutoAPI] Mapping Data... [ 50%] /<>/khard/address_book.py [2K[AutoAPI] Mapping Data... [ 57%] /<>/khard/version.py [2K[AutoAPI] Mapping Data... [ 64%] /<>/khard/cli.py [2K[AutoAPI] Mapping Data... [ 71%] /<>/khard/formatter.py [2K[AutoAPI] Mapping Data... [ 79%] /<>/khard/config.py [2K[AutoAPI] Mapping Data... [ 86%] /<>/khard/helpers/__init__.py [2K[AutoAPI] Mapping Data... [ 93%] /<>/khard/helpers/typing.py [2K[AutoAPI] Mapping Data... [100%] /<>/khard/helpers/interactive.py [AutoAPI] Rendering Data... [ 7%] khard [AutoAPI] Rendering Data... [ 14%] khard.khard [AutoAPI] Rendering Data... [ 21%] khard.__main__ [AutoAPI] Rendering Data... [ 29%] khard.actions [AutoAPI] Rendering Data... [ 36%] khard.query [AutoAPI] Rendering Data... [ 43%] khard.carddav_object [AutoAPI] Rendering Data... [ 50%] khard.address_book [AutoAPI] Rendering Data... [ 57%] khard.version [AutoAPI] Rendering Data... [ 64%] khard.cli [AutoAPI] Rendering Data... [ 71%] khard.formatter [AutoAPI] Rendering Data... [ 79%] khard.config [AutoAPI] Rendering Data... [ 86%] khard.helpers [AutoAPI] Rendering Data... [ 93%] khard.helpers.typing [AutoAPI] Rendering Data... [100%] khard.helpers.interactive [autosummary] generating autosummary for: bench.rst, commandline.rst, contributing.rst, davcontroller.rst, index.rst, indices.rst, man.rst, man/khard.conf.rst, man/khard.rst, scripting.rst building [mo]: targets for 0 po files that are out of date writing output... building [html]: targets for 10 source files that are out of date updating environment: [new config] 25 added, 0 changed, 0 removed [2Kreading sources... [ 4%] autoapi/index [2Kreading sources... [ 8%] autoapi/khard/__main__/index [2Kreading sources... [ 12%] autoapi/khard/actions/index [2Kreading sources... [ 16%] autoapi/khard/address_book/index [2Kreading sources... [ 20%] autoapi/khard/carddav_object/index [2Kreading sources... [ 24%] autoapi/khard/cli/index [2Kreading sources... [ 28%] autoapi/khard/config/index [2Kreading sources... [ 32%] autoapi/khard/formatter/index [2Kreading sources... [ 36%] autoapi/khard/helpers/index [2Kreading sources... [ 40%] autoapi/khard/helpers/interactive/index [2Kreading sources... [ 44%] autoapi/khard/helpers/typing/index [2Kreading sources... [ 48%] autoapi/khard/index [2Kreading sources... [ 52%] autoapi/khard/khard/index [2Kreading sources... [ 56%] autoapi/khard/query/index [2Kreading sources... [ 60%] autoapi/khard/version/index [2Kreading sources... [ 64%] bench [2Kreading sources... [ 68%] commandline [2Kreading sources... [ 72%] contributing [2Kreading sources... [ 76%] davcontroller [2Kreading sources... [ 80%] index [AutoAPI] Adding AutoAPI TOCTree [autoapi/index] to index.rst [2Kreading sources... [ 84%] indices [2Kreading sources... [ 88%] man [2Kreading sources... [ 92%] man/khard [2Kreading sources... [ 96%] man/khard.conf [2Kreading sources... [100%] scripting
Bug#1069839: libcommons-fileupload-java: FTBFS: failing tests
Package: src:libcommons-fileupload-java Version: 1.5-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config dh_autoreconf dh_auto_configure mh_patchpoms -plibcommons-fileupload-java --debian-build --keep-pom-version --maven-repo=/<>/debian/maven-repo dh_auto_build /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<>/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release. [INFO] Scanning for projects... [WARNING] The POM for org.apache.maven.plugins:maven-antrun-plugin:jar:1.3 is missing, no dependency information available [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-antrun-plugin:1.3: Plugin org.apache.maven.plugins:maven-antrun-plugin:1.3 or one of its dependencies could not be resolved: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.apache.maven.plugins:maven-antrun-plugin:jar:1.3 has not been downloaded from it before. [WARNING] The artifact org.apache.maven.plugins:maven-clean-plugin:jar:2.5 has been relocated to org.apache.maven.plugins:maven-clean-plugin:jar:3.2.0 [WARNING] The artifact org.apache.maven.plugins:maven-resources-plugin:jar:2.6 has been relocated to org.apache.maven.plugins:maven-resources-plugin:jar:3.3.0 [WARNING] The artifact org.apache.maven.plugins:maven-jar-plugin:jar:2.4 has been relocated to org.apache.maven.plugins:maven-jar-plugin:jar:3.3.0 [WARNING] The artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.1 has been relocated to org.apache.maven.plugins:maven-compiler-plugin:jar:3.10.1 [WARNING] The artifact org.apache.maven.plugins:maven-surefire-plugin:jar:2.12.4 has been relocated to org.apache.maven.plugins:maven-surefire-plugin:jar:2.22.3 [WARNING] The POM for org.apache.maven.plugins:maven-install-plugin:jar:2.4 is missing, no dependency information available [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-install-plugin:2.4: Plugin org.apache.maven.plugins:maven-install-plugin:2.4 or one of its dependencies could not be resolved: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.apache.maven.plugins:maven-install-plugin:jar:2.4 has not been downloaded from it before. [WARNING] The POM for org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 is missing, no dependency information available [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-deploy-plugin:2.7: Plugin org.apache.maven.plugins:maven-deploy-plugin:2.7 or one of its dependencies could not be resolved: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 has not been downloaded from it before. [WARNING] The POM for org.apache.maven.plugins:maven-site-plugin:jar:3.3 is missing, no dependency information available [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-site-plugin:3.3: Plugin org.apache.maven.plugins:maven-site-plugin:3.3 or one of its dependencies could not be resolved: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.apache.maven.plugins:maven-site-plugin:jar:3.3 has not been downloaded from it before. [WARNING] The POM for org.apache.maven.plugins:maven-antrun-plugin:jar:1.3 is missing, no dependency information available [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-antrun-plugin:1.3: Plugin org.apache.maven.plugins:maven-antrun-plugin:1.3 or one of its dependencies could not be resolved: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.apache.maven.plugins:maven-antrun-plugin:jar:1.3 has not been downloaded from it before. [WARNING] The POM for org.apache.maven.plugins:maven-assembly-plugin:jar:2.2-beta-5 is missing, no dependency information available [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5: Plugin org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5 or one of its dependencies could not be resolved: Cannot access central
Bug#1069840: maven-dependency-analyzer: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.10.1:testCompile (default-testCompile) on project maven-dependency-analyz
Package: src:maven-dependency-analyzer Version: 1.13.0-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules build dh build dh_update_autotools_config dh_autoreconf dh_auto_configure mh_patchpoms -plibmaven-dependency-analyzer-java --debian-build --keep-pom-version --maven-repo=/<>/debian/maven-repo dh_auto_build /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<>/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package -DskipTests -Dnotimestamp=true -Dlocale=en_US OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release. [INFO] Scanning for projects... [INFO] [INFO] -< org.apache.maven.shared:maven-dependency-analyzer >-- [INFO] Building Apache Maven Dependency Analyzer 1.13.0 [INFO] [ jar ]- [WARNING] The artifact org.apache.maven.plugins:maven-resources-plugin:jar:2.6 has been relocated to org.apache.maven.plugins:maven-resources-plugin:jar:3.3.0 [WARNING] The artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.1 has been relocated to org.apache.maven.plugins:maven-compiler-plugin:jar:3.10.1 [WARNING] The artifact org.apache.maven.plugins:maven-surefire-plugin:jar:2.12.4 has been relocated to org.apache.maven.plugins:maven-surefire-plugin:jar:2.22.3 [WARNING] The artifact org.apache.maven.plugins:maven-jar-plugin:jar:2.4 has been relocated to org.apache.maven.plugins:maven-jar-plugin:jar:3.3.0 [INFO] [INFO] --- maven-resources-plugin:3.3.0:resources (default-resources) @ maven-dependency-analyzer --- [INFO] skip non existing resourceDirectory /<>/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:3.10.1:compile (default-compile) @ maven-dependency-analyzer --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 19 source files to /<>/target/classes [INFO] /<>/src/main/java/org/apache/maven/shared/dependency/analyzer/DefaultProjectDependencyAnalyzer.java: /<>/src/main/java/org/apache/maven/shared/dependency/analyzer/DefaultProjectDependencyAnalyzer.java uses or overrides a deprecated API. [INFO] /<>/src/main/java/org/apache/maven/shared/dependency/analyzer/DefaultProjectDependencyAnalyzer.java: Recompile with -Xlint:deprecation for details. [INFO] [INFO] --- sisu-maven-plugin:0.3.5:main-index (index-project) @ maven-dependency-analyzer --- [INFO] [INFO] --- maven-resources-plugin:3.3.0:testResources (default-testResources) @ maven-dependency-analyzer --- [INFO] skip non existing resourceDirectory /<>/src/test/resources [INFO] [INFO] --- maven-compiler-plugin:3.10.1:testCompile (default-testCompile) @ maven-dependency-analyzer --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 11 source files to /<>/target/test-classes [INFO] /<>/src/test/java/org/apache/maven/shared/dependency/analyzer/ProjectDependencyAnalysisTest.java: /<>/src/test/java/org/apache/maven/shared/dependency/analyzer/ProjectDependencyAnalysisTest.java uses unchecked or unsafe operations. [INFO] /<>/src/test/java/org/apache/maven/shared/dependency/analyzer/ProjectDependencyAnalysisTest.java: Recompile with -Xlint:unchecked for details. [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /<>/src/test/java/org/apache/maven/shared/dependency/analyzer/ClassFileVisitorUtilsTest.java:[67,13] exception java.io.IOException is never thrown in body of corresponding try statement [INFO] 1 error [INFO] - [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2.735 s [INFO] Finished at: 2024-04-25T13:27:25Z [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.10.1:testCompile (default-testCompile) on project maven-dependency-analyzer: Compilation failure [ERROR] /<>/src/test/java/org/apache/maven/shared/dependency/analyzer/ClassFileVisitorUtilsTest.java:[67,13] exception java.io.IOException is never thrown in body of corresponding try statement [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
Processed: Re: antlr4-maven-plugin: please provide debian-versioned maven coordinates
Processing commands for cont...@bugs.debian.org: > severity 1065660 serious Bug #1065660 [antlr4-maven-plugin] antlr4-maven-plugin: please provide debian-versioned maven coordinates Severity set to 'serious' from 'normal' > tags 1065660 + ftbfs Bug #1065660 [antlr4-maven-plugin] antlr4-maven-plugin: please provide debian-versioned maven coordinates Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1065660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065660 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Pending
Processing control commands: > tags -1 pending Bug #1024889 [src:pplacer] pplacer: build-depends on dropped package Added tag(s) pending. > block -1 by 1064596 Bug #1024889 [src:pplacer] pplacer: build-depends on dropped package 1024889 was not blocked by any bugs. 1024889 was not blocking any bugs. Added blocking bug(s) of 1024889: 1064596 -- 1024889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024889: Pending
Control: tags -1 pending Control: block -1 by 1064596 thanks Pplacer needs to be build against the old version of MCL which is featuring some OCAML patch. This old version was just uploaded to new. Kind regards Andreas. -- https://fam-tille.de
Bug#1069835: libreoffice-kf5: documents may get lost on SMB shares
Hi, Am 25.04.24 um 17:03 schrieb Andreas B. Mundt: For now, we traced the issue back to libreoffice-kf5. If this package is removed, neither the document disappears on closing libreoffice nor the popup is shown when 'nobrl' is removed from the mount options. Which doesn't do IO itself though? But maybe the KDE file picker (over kio) does something weird? But saving (ttbomk) isn't done by the file picker itself? There also is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935182 since some time. It looks a bit like the issue found in [2]. Which doesn't touch any KDE stuff either. In fact it caused 32bit builds to fail[1] and I don't know what more regressions this caused. I would be wary of "just" backporting it in a point release... Regards, Rene [1] by relying on internal glibc/kernel types, see https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/-/blob/libreoffice_24.2.2_rc1-2/patches/fix-32bit-build.diff?ref_type=tags - later updated upstream for https://cgit.freedesktop.org/libreoffice/core/commit/sal/osl/unx/file.cxx?id=434065478d35fe8e144aec916ac06438c0150270
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> found 1069835 4:7.4.7-1
Bug #1069835 {Done: Rene Engelhard } [libreoffice-kf5]
libreoffice-kf5: documents may get lost on SMB shares
Marked as found in versions libreoffice/4:7.4.7-1.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1069835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069835
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1069835: libreoffice-kf5: documents may get lost on SMB shares
Processing commands for cont...@bugs.debian.org:
> close 1069835 4:24.2.2-1
Bug #1069835 [libreoffice-kf5] libreoffice-kf5: documents may get lost on SMB
shares
Marked as fixed in versions libreoffice/4:24.2.2-1.
Bug #1069835 [libreoffice-kf5] libreoffice-kf5: documents may get lost on SMB
shares
Marked Bug as done
> forwarded 1069835 https://bugs.documentfoundation.org/show_bug.cgi?id=55004
Bug #1069835 {Done: Rene Engelhard } [libreoffice-kf5]
libreoffice-kf5: documents may get lost on SMB shares
Set Bug forwarded-to-address to
'https://bugs.documentfoundation.org/show_bug.cgi?id=55004'.
> tag 1069835 + moreinfo
Bug #1069835 {Done: Rene Engelhard } [libreoffice-kf5]
libreoffice-kf5: documents may get lost on SMB shares
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1069835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069835
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1069835: libreoffice-kf5: documents may get lost on SMB shares
close 1069835 4:24.2.2-1 forwarded 1069835 https://bugs.documentfoundation.org/show_bug.cgi?id=55004 tag 1069835 + moreinfo thanks Am 25.04.24 um 17:03 schrieb Andreas B. Mundt: Package: libreoffice-kf5 Version? Severity: grave Come on... Not downgrading just yet, but I don't believe it's grave. we run Debian bookworm KDE plasma clients with home directories mounted from an SMB share. From time to time, users reported that Ah, bookworm. You should have mentioned it in Version: libreoffice documents have disappeared completely when closing libreoffice. We were now able to reproduce the issue on both, the current bookworm and bookworm-backports version of libreoffice. Mount an SMB share. I use the following in fstab: //SHARE/DIR /media/share cifs user,nobrl,user=USER,password=PASS 0 0 Open/create an ODT document, write some text, save the file and check it's appearance on the share. Then click Insert → Image and (perhaps with the image still selected in the document) close libreoffice. The file disappears on the share. This is almost always reproducible (we tested multiple SMB servers) if not, just open the file again, insert another image, Ctrl-S, Ctrl-Q, the file is gone! If 'nobrl' is removed from the mount options (but we need it for other programs to work properly), instead of the file disappearing, a popup shows: Error saving the document Untitled 1: Error creating object. Could not create backup copy. This looks like already reported upstream [1]. For now, we traced the issue back to libreoffice-kf5. If this package is removed, neither the document disappears on closing libreoffice nor the popup is shown when 'nobrl' It looks a bit like the issue found in [2]. So fixed in sid? (If I only could update the bookworm backport to 24.2.2+, but given it's sstill stuck behind time_t...) Regards, Rene
Bug#1066618: marked as done (libt3key: FTBFS: .config.c:8:13: error: implicit declaration of function ‘setupterm’; did you mean ‘set_term’? [-Werror=implicit-function-declaration])
Your message dated Thu, 25 Apr 2024 15:21:03 +
with message-id
and subject line Bug#1066618: fixed in libt3key 0.2.10-1.1
has caused the Debian Bug report #1066618,
regarding libt3key: FTBFS: .config.c:8:13: error: implicit declaration of
function ‘setupterm’; did you mean ‘set_term’?
[-Werror=implicit-function-declaration]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1066618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libt3key
Version: 0.2.10-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> gcc -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> `pkg-config --cflags tinfo` -c -o .config.o .config.c
> .config.c: In function ‘main’:
> .config.c:8:13: error: implicit declaration of function ‘setupterm’; did you
> mean ‘set_term’? [-Werror=implicit-function-declaration]
> 8 | if (setupterm(NULL, fd, ) == OK) {
> | ^
> | set_term
> .config.c:12:17: error: implicit declaration of function ‘tputs’; did you
> mean ‘puts’? [-Werror=implicit-function-declaration]
>12 | tputs("\033[0m", 1, putchar);
> | ^
> | puts
> cc1: some warnings being treated as errors
> make[2]: *** [.Makefile:19: .config.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/libt3key_0.2.10-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=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.
--- End Message ---
--- Begin Message ---
Source: libt3key
Source-Version: 0.2.10-1.1
Done: Bo YU
We believe that the bug you reported is fixed in the latest version of
libt3key, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bo YU (supplier of updated libt3key package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 25 Apr 2024 10:54:51 +0800
Source: libt3key
Architecture: source
Version: 0.2.10-1.1
Distribution: unstable
Urgency: medium
Maintainer: Gertjan Halkes
Changed-By: Bo YU
Closes: 1066618
Changes:
libt3key (0.2.10-1.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Add 00-fix-impfuncdef-issue.patch to fix ftbfs issue.
(Closes: #1066618)
Checksums-Sha1:
a802dee84f592faf23c9cb9bb2c1d2ed175be17e 2188 libt3key_0.2.10-1.1.dsc
1584cfb3e9240dd7aef0677a7fbe99f5c1792ede 4852 libt3key_0.2.10-1.1.debian.tar.xz
65406c3ab673ee0c7243f367d985ef7fe6e83525 7474
libt3key_0.2.10-1.1_amd64.buildinfo
Checksums-Sha256:
58ac7317575c0dfa8c242d795bbe88a9e9a9fe001d8d463ac9c8328a3a15cc39 2188
libt3key_0.2.10-1.1.dsc
a774e2336560f84e839b18a62a64021d45f130e4cab3cbcd03ed3ff3b22b21ed 4852
libt3key_0.2.10-1.1.debian.tar.xz
bf3db5e3d2e6322d7c4e99c73109e82d2fdf97a4368a88c2c3900e546a4e0c3e 7474
libt3key_0.2.10-1.1_amd64.buildinfo
Files:
81660378b24aeb5a5b045287b43352d2 2188 libs optional
Bug#1069835: libreoffice-kf5: documents may get lost on SMB shares
Package: libreoffice-kf5 Severity: grave Dear Rene, everybody, we run Debian bookworm KDE plasma clients with home directories mounted from an SMB share. From time to time, users reported that libreoffice documents have disappeared completely when closing libreoffice. We were now able to reproduce the issue on both, the current bookworm and bookworm-backports version of libreoffice. Mount an SMB share. I use the following in fstab: //SHARE/DIR /media/share cifs user,nobrl,user=USER,password=PASS 0 0 Open/create an ODT document, write some text, save the file and check it's appearance on the share. Then click Insert → Image and (perhaps with the image still selected in the document) close libreoffice. The file disappears on the share. This is almost always reproducible (we tested multiple SMB servers) if not, just open the file again, insert another image, Ctrl-S, Ctrl-Q, the file is gone! If 'nobrl' is removed from the mount options (but we need it for other programs to work properly), instead of the file disappearing, a popup shows: Error saving the document Untitled 1: Error creating object. Could not create backup copy. This looks like already reported upstream [1]. For now, we traced the issue back to libreoffice-kf5. If this package is removed, neither the document disappears on closing libreoffice nor the popup is shown when 'nobrl' is removed from the mount options. It looks a bit like the issue found in [2]. Thanks for maintaining libreoffice, best regards, Andi [1] https://bugs.documentfoundation.org/show_bug.cgi?id=160315 [2] https://bugs.documentfoundation.org/show_bug.cgi?id=55004#c56
Bug#950372: marked as done (Is radare2 suitable for stable Debian releases?)
Your message dated Thu, 25 Apr 2024 14:52:15 + with message-id and subject line Bug#950372: fixed in radare2 5.9.0+dfsg-1 has caused the Debian Bug report #950372, regarding Is radare2 suitable for stable Debian releases? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 950372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950372 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: radare2 Severity: grave Tags: security It is understandable (and normal for most software) that upstream is not able or willing to provide security support for the old version shipped in stable distribution releases. But below seems to be upstream actively encouraging exploiting the version in stable. AFAIK Debian in general tries to avoid shipping software when upstream strongly objects to it, or is openly hostile towards Debian. <-- snip --> https://rada.re/con/2019/ PwnDebian Since the very begining of radare development we had people complaining of bugs because they were using the 3-4 year old version shipped in their distro. We tried to work with everyone who ships builds of r2 to always get updates and merge back their patches upstream so everyone gets benefit out of it. But that has been not enough. In github/radare2 we can check out most of known/used Linux and BSD distros and the shipped r2 version, and it's pretty clear that Debian/Ubuntu stopped updating those packages long time ago (3.2.1). Yes, the 0.9.6 drama is over. The aim of this competition is to publish a working exploit for radare2 on Debian stable (nowadays, unstable keeps the same version). To show that debian-security and backporting patches is not solving enough when distributing such state-of-the-art packages. In order to win this competition. We will accept only 1 working exploit (the first one to submit it) for radare2-3.2.1 (built for x86-64 debian/stable). Additional points will be given for writing some notes or presenting at r2con the way the vuln was found and how the exploit was developed. --- End Message --- --- Begin Message --- Source: radare2 Source-Version: 5.9.0+dfsg-1 Done: Alex Myczko We believe that the bug you reported is fixed in the latest version of radare2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 950...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alex Myczko (supplier of updated radare2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 25 Apr 2024 15:46:50 +0200 Source: radare2 Architecture: source Version: 5.9.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Alex Myczko Closes: 950372 1014478 1014490 1016979 1027144 1029037 1032667 1034180 1034862 1051898 1054908 1055854 1056930 1060127 Changes: radare2 (5.9.0+dfsg-1) unstable; urgency=medium . * New upstream version. (Closes: #1034862, #1060127, #950372) (Closes: #1056930) (CVE-2023-47016) (Closes: #1032667) (CVE-2023-27114) (Closes: #1055854) (CVE-2023-5686) (Closes: #1054908) (CVE-2023-46570) (CVE-2023-46569) (Closes: #1051898) (CVE-2023-4322) (Closes: #1034180) (CVE-2023-1605) (Closes: #1029037) (CVE-2023-0302) (Closes: #1027144) (CVE-2022-4398) (Closes: #1016979) (CVE-2022-34502) (CVE-2022-34520) (Closes: #1014490) (CVE-2021-44975) (CVE-2021-44974) (CVE-2021-4021) (Closes: #1014478) (CVE-2022-1714 CVE-2022-1809 CVE-2022-1899 CVE-2022-0849 CVE-2022-1052 CVE-2022-1061 CVE-2022-1207 CVE-2022-1237 CVE-2022-1238 CVE-2022-1240 CVE-2022-1244 CVE-2022-0476 CVE-2022-0518 CVE-2022-0519 CVE-2022-0521 CVE-2022-0523 CVE-2022-0559 CVE-2022-0676 CVE-2022-0695 CVE-2022-0712 CVE-2022-0713 CVE-2022-0139 CVE-2022-0173 CVE-2022-0419 CVE-2022-1031 CVE-2022-1283 CVE-2022-1284 CVE-2022-1296 CVE-2022-1297 CVE-2022-1382 CVE-2022-1444 CVE-2022-1437 CVE-2022-1451 CVE-2022-1452 CVE-2022-1649 CVE-2022-1383) Checksums-Sha1:
Bug#1014478: marked as done (radare2: CVE-2022-1714 CVE-2022-1809 CVE-2022-1899 CVE-2022-0849 CVE-2022-1052 CVE-2022-1061 CVE-2022-1207 CVE-2022-1237 CVE-2022-1238 CVE-2022-1240 CVE-2022-1244 CVE-2022
Your message dated Thu, 25 Apr 2024 14:52:15 + with message-id and subject line Bug#1014478: fixed in radare2 5.9.0+dfsg-1 has caused the Debian Bug report #1014478, regarding radare2: CVE-2022-1714 CVE-2022-1809 CVE-2022-1899 CVE-2022-0849 CVE-2022-1052 CVE-2022-1061 CVE-2022-1207 CVE-2022-1237 CVE-2022-1238 CVE-2022-1240 CVE-2022-1244 CVE-2022-0476 CVE-2022-0518 CVE-2022-0519 CVE-2022-0521 CVE-2022-0523 CVE-2022-0559 CVE-2022-0676 CVE-2022-0695 CVE-2022-0712 CVE-2022-0713 CVE-2022-0139 CVE-2022-0173 CVE-2022-0419 CVE-2022-1031 CVE-2022-1283 CVE-2022-1284 CVE-2022-1296 CVE-2022-1297 CVE-2022-1382 CVE-2022-1444 CVE-2022-1437 CVE-2022-1451 CVE-2022-1452 CVE-2022-1649 CVE-2022-1383 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1014478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: radare2 X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for radare2. CVE-2022-1714[0]: | Heap-based Buffer Overflow in GitHub repository radareorg/radare2 | prior to 5.7.0. The bug causes the program reads data past the end of | the intented buffer. Typically, this can allow attackers to read | sensitive information from other memory locations or cause a crash. https://huntr.dev/bounties/1c22055b-b015-47a8-a57b-4982978751d0 https://github.com/radareorg/radare2/commit/3ecdbf8e21186a9c5a4d3cfa3b1e9fd27045340e CVE-2022-1809[1]: | Access of Uninitialized Pointer in GitHub repository radareorg/radare2 | prior to 5.7.0. https://huntr.dev/bounties/0730a95e-c485-4ff2-9a5d-bb3abfda0b17 https://github.com/radareorg/radare2/commit/919e3ac1a13f753c73e7a8e8d8bb4a143218732d CVE-2022-1899[2]: | Out-of-bounds Read in GitHub repository radareorg/radare2 prior to | 5.7.0. https://huntr.dev/bounties/8a3dc5cb-08b3-4807-82b2-77f08c137a04 https://github.com/radareorg/radare2/commit/193f4fe01d7f626e2ea937450f2e0c4604420e9d CVE-2022-0849[3]: | Use After Free in r_reg_get_name_idx in GitHub repository | radareorg/radare2 prior to 5.6.6. https://huntr.dev/bounties/29c5f76e-5f1f-43ab-a0c8-e31951e407b6 https://github.com/radareorg/radare2/commit/10517e3ff0e609697eb8cde60ec8dc999ee5ea24 CVE-2022-1052[4]: | Heap Buffer Overflow in iterate_chained_fixups in GitHub repository | radareorg/radare2 prior to 5.6.6. https://huntr.dev/bounties/3b3b7f77-ab8d-4de3-999b-eeec0a3eebe7 https://github.com/radareorg/radare2/commit/0052500c1ed5bf8263b26b9fd7773dbdc6f170c4 CVE-2022-1061[5]: | Heap Buffer Overflow in parseDragons in GitHub repository | radareorg/radare2 prior to 5.6.8. https://huntr.dev/bounties/a7546dae-01c5-4fb0-8a8e-c04ea4e9bac7 https://github.com/radareorg/radare2/commit/d4ce40b516ffd70cf2e9e36832d8de139117d522 CVE-2022-1207[6]: | Out-of-bounds read in GitHub repository radareorg/radare2 prior to | 5.6.8. This vulnerability allows attackers to read sensitive | information from outside the allocated buffer boundary. https://huntr.dev/bounties/7b979e76-ae54-4132-b455-0833e45195eb https://github.com/radareorg/radare2/commit/605785b65dd356d46d4487faa41dbf90943b8bc1 CVE-2022-1237[7]: | Improper Validation of Array Index in GitHub repository | radareorg/radare2 prior to 5.6.8. This vulnerability is heap overflow | and may be exploitable. For more general description of heap buffer | overflow, see [CWE](https://cwe.mitre.org/data/definitions/122.html). https://huntr.dev/bounties/ad3c9c4c-76e7-40c8-bd4a-c095acd8bb40 https://github.com/radareorg/radare2/commit/2d782cdaa2112c10b8dd5e7a93c134b2ada9c1a6 CVE-2022-1238[8]: | Heap-based Buffer Overflow in libr/bin/format/ne/ne.c in GitHub | repository radareorg/radare2 prior to 5.6.8. This vulnerability is | heap overflow and may be exploitable. For more general description of | heap buffer overflow, see | [CWE](https://cwe.mitre.org/data/definitions/122.html). https://huntr.dev/bounties/47422cdf-aad2-4405-a6a1-6f63a3a93200 https://github.com/radareorg/radare2/commit/c40a4f9862104ede15d0ba05ccbf805923070778 CVE-2022-1240[9]: | Heap buffer overflow in libr/bin/format/mach0/mach0.c in GitHub | repository radareorg/radare2 prior to 5.8.6. If address sanitizer is | disabled during the compiling, the program should executes into the | `r_str_ncpy` function. Therefore I think it is very likely to be | exploitable. For more general description of heap buffer overflow, see | [CWE](https://cwe.mitre.org/data/definitions/122.html). https://huntr.dev/bounties/e589bd97-4c74-4e79-93b5-0951a281facc
Bug#1069834: sccache FTBFS with itoa != 0.3.4
Source: sccache Version: 0.8.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=sccache=0.8.0-1 ... test test_rust_cargo_cmd_readonly_preemtive_block ... FAILED failures: test_rust_cargo_cmd_readonly_preemtive_block stdout Error: Unexpected failure. code=101 stderr=`` error: failed to select a version for the requirement `itoa = \"^0.3.4\"` (locked to 0.3.4) candidate versions found which didn\'t match: 1.0.9 location searched: directory source `/<>/debian/cargo_registry` (which is replacing registry `crates-io`) required by package `test-crate v0.1.0 (/<>/tests/test-crate)` perhaps a crate was updated and forgotten to be re-vendored? ``` ``` command=`cd "tests/test-crate" && CARGO_INCREMENTAL="0" CARGO_TARGET_DIR="/<>/debian/sccache_test_rust_cargoG4h5iT/cargo" RUSTC_WRAPPER="/<>/target/x86_64-unknown-linux-gnu/release/sccache" TEST_ENV_VAR="1" "/usr/bin/cargo" "build" "--color=never"` code=101 stdout="" stderr=``` error: failed to select a version for the requirement `itoa = \"^0.3.4\"` (locked to 0.3.4) candidate versions found which didn\'t match: 1.0.9 location searched: directory source `/<>/debian/cargo_registry` (which is replacing registry `crates-io`) required by package `test-crate v0.1.0 (/<>/tests/test-crate)` perhaps a crate was updated and forgotten to be re-vendored? ``` Stack backtrace: 0: 1: 2: 3: 4: 5: 6: 7: 8: 9: 10: failures: test_rust_cargo_cmd_readonly_preemtive_block test result: FAILED. 2 passed; 1 failed; 5 ignored; 0 measured; 0 filtered out; finished in 11.18s error: test failed, to rerun pass `--test sccache_cargo` dh_auto_test: error: env DEB_BUILDDIR= /<>/debian/dh-cargo/bin/cargo test returned exit code 101 make[1]: *** [debian/rules:29: override_dh_auto_test] Error 25
Processed: severity of 1067047 is wishlist
Processing commands for cont...@bugs.debian.org: > severity 1067047 wishlist Bug #1067047 [src:gnucash] Buildng the package removes debian/.gitlab-ci.yml Severity set to 'wishlist' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1067047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1069551 marked as pending in numpy
Processing control commands:
> tag -1 pending
Bug #1069551 [src:numpy] numpy: FTBFS on armel: dh_auto_test: error: pybuild
--test -i python{version} -p "3.12 3.11" returned exit code 13
Added tag(s) pending.
--
1069551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1067047: Buildng the package removes debian/.gitlab-ci.yml
Processing control commands:
> reopen -1
Bug #1067047 {Done: Dmitry Smirnov } [src:gnucash] Buildng
the package removes debian/.gitlab-ci.yml
Bug reopened
Ignoring request to alter fixed versions of bug #1067047 to the same values
previously set
--
1067047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1069551: marked as pending in numpy
Control: tag -1 pending Hello, Bug #1069551 in numpy 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/python-team/packages/numpy/-/commit/33bbdaaea407c52e0f6ba4422eeb6d73644c8e33 Skip TestErrState::test_invalid on armel Closes: #1069551 (this message was generated automatically) -- Greetings https://bugs.debian.org/1069551
Bug#1067047: Buildng the package removes debian/.gitlab-ci.yml
Control: reopen -1 On Fri, Apr 26, 2024 at 12:12:06AM +1000, Dmitry Smirnov wrote: > > Source: gnucash > > Version: 1:5.5-1.1 > > Severity: serious > > > > Simply build the package from source produces a source package that doesn't > > contain debian/.gitlab-ci.yml in debian.tar, one needs to rebuild the > > source package separately, skipping the clean target. The reason for that > > is that the file is listed debian/clean for some reason (alternatively, if > > it shouldn't be in the package, please remove it from the package). > > This is ridiculous. I agree. > Obviously '.gitlab-ci.yml' is a repository-specific file with > configuration of Gitlab CI on Salsa. There is no reason to ship it with > source package Yet you are shipping it, maybe you should reconsider that? $ tar tvf gnucash_5.5-1.2.debian.tar.xz debian/.gitlab-ci.yml -rw-rw-r-- 0/0 759 2024-02-23 22:55 debian/.gitlab-ci.yml -- WBR, wRAR signature.asc Description: PGP signature
Bug#1067047: marked as done (Buildng the package removes debian/.gitlab-ci.yml)
Your message dated Fri, 26 Apr 2024 00:12:06 +1000 with message-id <3341693.tJ1Z21uVQO@deblab> and subject line Re: Bug#1067047: Buildng the package removes debian/.gitlab-ci.yml has caused the Debian Bug report #1067047, regarding Buildng the package removes debian/.gitlab-ci.yml to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1067047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnucash Version: 1:5.5-1.1 Severity: serious Simply build the package from source produces a source package that doesn't contain debian/.gitlab-ci.yml in debian.tar, one needs to rebuild the source package separately, skipping the clean target. The reason for that is that the file is listed debian/clean for some reason (alternatively, if it shouldn't be in the package, please remove it from the package). -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- On Monday, 18 March 2024 3:29:18 AM AEST Andrey Rahmatullin wrote: > Source: gnucash > Version: 1:5.5-1.1 > Severity: serious > > Simply build the package from source produces a source package that doesn't > contain debian/.gitlab-ci.yml in debian.tar, one needs to rebuild the > source package separately, skipping the clean target. The reason for that > is that the file is listed debian/clean for some reason (alternatively, if > it shouldn't be in the package, please remove it from the package). This is ridiculous. Obviously '.gitlab-ci.yml' is a repository-specific file with configuration of Gitlab CI on Salsa. There is no reason to ship it with source package (where it is useless) and it should remain committed to repository where it serves an important function. '.gitlab-ci.yml' is listed in "debian/clean" intentionally and no change is necessary. -- Best wishes, Dmitry Smirnov GPG key : 4096R/52B6BBD953968D1B --- Unthinking adherence to any "authority" constitutes the greatest betrayal to humanity that there could possibly be, as it seeks to discard the free will and individual judgment that make us human and make us capable of morality, in favor of blind obedience, which reduces human beings to irresponsible robots. -- Larken Rose, The Most Dangerous Superstition signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#1066745: marked as done (pytest-mpl: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Thu, 25 Apr 2024 13:34:54 +
with message-id
and subject line Bug#1066745: fixed in pytest-mpl 0.17.0-1
has caused the Debian Bug report #1066745,
regarding pytest-mpl: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p "3.12 3.11" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1066745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066745
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytest-mpl
Version: 0.16.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:305: python3.12 setup.py config
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293:
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
>
>
>
> The license_file parameter is deprecated, use license_files instead.
>
> This deprecation is overdue, please update your project and remove
> deprecated
> calls to avoid build errors in the future.
>
> See
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for
> details.
>
>
>
> !!
> parsed = self.parsers.get(option_name, lambda x: x)(value)
> /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:265:
> UserWarning: Unknown distribution option: 'use_scm_version'
> warnings.warn(msg)
> running config
> I: pybuild base:305: python3.11 setup.py config
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293:
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
>
>
>
> The license_file parameter is deprecated, use license_files instead.
>
> This deprecation is overdue, please update your project and remove
> deprecated
> calls to avoid build errors in the future.
>
> See
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for
> details.
>
>
>
> !!
> parsed = self.parsers.get(option_name, lambda x: x)(value)
> /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:265:
> UserWarning: Unknown distribution option: 'use_scm_version'
> warnings.warn(msg)
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3.12 setup.py build
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293:
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
>
>
>
> The license_file parameter is deprecated, use license_files instead.
>
> This deprecation is overdue, please update your project and remove
> deprecated
> calls to avoid build errors in the future.
>
> See
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for
> details.
>
>
>
> !!
> parsed = self.parsers.get(option_name, lambda x: x)(value)
> /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:265:
> UserWarning: Unknown distribution option: 'use_scm_version'
> warnings.warn(msg)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_pytest-mpl/build/pytest_mpl
> copying pytest_mpl/__init__.py ->
> /<>/.pybuild/cpython3_3.12_pytest-mpl/build/pytest_mpl
> copying pytest_mpl/plugin.py ->
> /<>/.pybuild/cpython3_3.12_pytest-mpl/build/pytest_mpl
> creating
> /<>/.pybuild/cpython3_3.12_pytest-mpl/build/pytest_mpl/summary
> copying pytest_mpl/summary/__init__.py ->
> /<>/.pybuild/cpython3_3.12_pytest-mpl/build/pytest_mpl/summary
> copying pytest_mpl/summary/html.py ->
> /<>/.pybuild/cpython3_3.12_pytest-mpl/build/pytest_mpl/summary
> running egg_info
> creating pytest_mpl.egg-info
> writing pytest_mpl.egg-info/PKG-INFO
> writing dependency_links to
Bug#1063963: marked as done (pytest-mpl: autopkgtest regression with pytest 8)
Your message dated Thu, 25 Apr 2024 13:34:54 +
with message-id
and subject line Bug#1063963: fixed in pytest-mpl 0.17.0-1
has caused the Debian Bug report #1063963,
regarding pytest-mpl: autopkgtest regression with pytest 8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1063963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063963
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pytest-mpl
Version: 0.16.1-2
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: pytest-8
Dear maintainer,
your package has a autopkgtest regression with pytest 8.
Typically, packages will start failing if they
- have deprecation warnings of type PytestRemovedIn8Warning, or
- assume a particular pytest stdout/stderr output which might have
changed, or
- rely on implementation details of the pytest test collector, in
particular the pytest.Package class, which has been redesigned for
pytest 8.
Please refer to the upstream changelog [1] for a complete list of
breaking changes and the pytest (pseudo-)excuses [2] related to your
package for details of the regression.
It is possible that the autopkgtest regression is not directly caused
by pytest-mpl, but by one of its dependencies. In that case, feel
free to reassign the bug and mark your package as affected, but do
not close the bug until the autopkgtest passes.
Cheers Timo
[1]
https://docs.pytest.org/en/8.0.x/changelog.html#pytest-8-0-0rc1-2023-
12-30 [2]
https://qa.debian.org/excuses.php?experimental=1=pytest
--- End Message ---
--- Begin Message ---
Source: pytest-mpl
Source-Version: 0.17.0-1
Done: Michael R. Crusoe
We believe that the bug you reported is fixed in the latest version of
pytest-mpl, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael R. Crusoe (supplier of updated pytest-mpl package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 25 Apr 2024 14:02:10 +0300
Source: pytest-mpl
Architecture: source
Version: 0.17.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers
Changed-By: Michael R. Crusoe
Closes: 1018456 1063963 1066745
Changes:
pytest-mpl (0.17.0-1) unstable; urgency=medium
.
* Team upload.
* New upstream version. Closes: #1063963, #1066745
* Standards-Version: 4.6.2 (routine-update)
* Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update)
* d/{control,copyright}: point to new upstream location
* Refreshed patches.
* d/control: remove references to python3-nose (Closes: #1018456)
* Added patch to fix many PytestReturnNotNoneWarnings
* d/rules: run the tests the same way upstream does
Checksums-Sha1:
b0b495fae43f6b59504318733e55f188714a11de 2197 pytest-mpl_0.17.0-1.dsc
6d5bfe6bcc6ec32ae57d111ecff88fc7fff2f5a9 885613 pytest-mpl_0.17.0.orig.tar.gz
6b1f6deb62418d2196b82f377d87f6accc077204 6732 pytest-mpl_0.17.0-1.debian.tar.xz
5407ebc8ba3da67a4fc429629dc278d04d3d7786 10053
pytest-mpl_0.17.0-1_source.buildinfo
Checksums-Sha256:
bda137a50e21808440b5def233bbb3a6dd7e4a64346e2af0a7ce07cb324dd8ee 2197
pytest-mpl_0.17.0-1.dsc
fbef05d7e664b4b33452fb698ac188e522791f327de34e7ea37dbdfe9d52cac6 885613
pytest-mpl_0.17.0.orig.tar.gz
0c689681440edf06f8b40f0bdeb8fbce7ea45dda01570e43978acb8449f9be17 6732
pytest-mpl_0.17.0-1.debian.tar.xz
ef19a6655112fe2b20dc15a94cb239193177aa336a126a9d09d0fe01e6647a04 10053
pytest-mpl_0.17.0-1_source.buildinfo
Files:
2e7de5558c3c7929c8bc9703da72fcb4 2197 python optional pytest-mpl_0.17.0-1.dsc
5c021e0c9715eb2e8dc73739ec734ee8 885613 python optional
pytest-mpl_0.17.0.orig.tar.gz
cafe1b307dc2807bb65025f04010e102 6732 python optional
pytest-mpl_0.17.0-1.debian.tar.xz
9841bfb2306b86af8dcb908af8e9acac 10053 python optional
pytest-mpl_0.17.0-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAmYqWxAACgkQPCZ2P2xn
5uIOQw//Zy/SGyeavn7p8p6OigBiqSlm1+yGGKyRfjlPmAjh8Jlj5X4crUqE0PBC
vrfRv8jbyLwIBoIwmmc5u4kOXcg2J2I6ZC9YvzkyvMaLyYrZZfgfRJ85XkWdlmfD
FBlxmlS+azLAKcSbCDUSkqKRLNC8ZIC08tV0z3EBSzSvN3DBGGX/p4UE9jvRIxy9
Bug#1069688: marked as done (libsequoia-octopus-librnp has an undeclared file conflict on /usr/lib/thunderbird/librnp.so)
Your message dated Thu, 25 Apr 2024 13:19:29 + with message-id and subject line octopus file conflict resolved has caused the Debian Bug report #1069688, regarding libsequoia-octopus-librnp has an undeclared file conflict on /usr/lib/thunderbird/librnp.so to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1069688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069688 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libsequoia-octopus-librnp Version: 1.8.1-3 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + thunderbird libsequoia-octopus-librnp has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/thunderbird/librnp.so is contained in the packages * libsequoia-octopus-librnp/1.8.1-3 as present in unstable * thunderbird/1:122.0~b2-1 as present in experimental These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected file. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance. --- End Message --- --- Begin Message --- version: 1.8.1-4 from #debian-devel just now: helmut: do you still see #1069688 in dumat? zwiebelbot- | (#debian-devel) Debian#1069688: libsequoia-octopus-librnp has an undeclared file conflict on /usr/lib/thunderbird/librnp.so - https://bugs.debian.org/1069688 h01ger: I do not helmut: nice so i can close that bug -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ In Europe there are people prosecuted by courts because they saved other people from drowning in the Mediterranean Sea. That is almost as absurd as if there were people being prosecuted because they save humans from drowning in the sea. signature.asc Description: PGP signature --- End Message ---
Processed: Re: Bug#1069258: ruby-curb: test regression with curl 8.7.1: client read function EOF fail, only only 4/5 of needed bytes read
Processing control commands: > retitle -1 ruby-curb: test regression with curl 8.7.1: client read function > EOF fail, only only 4/5 of needed bytes read Bug #1069258 [src:ruby-curb] ruby-curb: FTBFS: 178 tests, 699 assertions, 0 failures, 7 errors, 0 pendings, 0 omissions, 0 notifications Changed Bug title to 'ruby-curb: test regression with curl 8.7.1: client read function EOF fail, only only 4/5 of needed bytes read' from 'ruby-curb: FTBFS: 178 tests, 699 assertions, 0 failures, 7 errors, 0 pendings, 0 omissions, 0 notifications'. -- 1069258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069258: ruby-curb: test regression with curl 8.7.1: client read function EOF fail, only only 4/5 of needed bytes read
Control: retitle -1 ruby-curb: test regression with curl 8.7.1: client read function EOF fail, only only 4/5 of needed bytes read User: debian...@lists.debian.org Usertags: breaks needs-update On Thu, 18 Apr 2024 at 22:42:11 +0200, Sebastian Ramacher wrote: > Error: test_easy_http_verbs(TestCurbCurlEasy): Curl::Err::ReadError: Failed > to open/read local data from file/application: client read function EOF fail, > only only 4/5 of needed bytes read ... > Error: test_put_data(TestCurbCurlEasy): Curl::Err::ReadError: Failed to > open/read local data from file/application: client read function EOF fail, > only only 6/7 of needed bytes read ... > Error: test_put_data_null_bytes(TestCurbCurlEasy): Curl::Err::ReadError: > Failed to open/read local data from file/application: client read function > EOF fail, only only 2/3 of needed bytes read These messages with "only only (n)/(n+1) of needed bytes read" seem to be characteristic. As well as being a FTBFS, this is also an autopkgtest regression when upgrading curl, which is one of several factors preventing curl from migrating; that, in turn, blocks elfutils, which blocks GLib, which will likely be blocking a significant chunk of the 64-bit time_t transition. This could either be a regression in curl, or a pre-existing bug in ruby-curb that was exposed by a behaviour change in curl (for example maybe curl started applying stricter checks). I don't know curl well enough to say which, but perhaps the curl maintainers can help? This upstream commit introduced the new error message and seems relevant: https://github.com/curl/curl/commit/9369c30cd87c041cf983bcdfabd1570980abbaf6 Here is a convenient reproducer in an unprivileged container: $ podman run -v $(pwd):$(pwd):rw -w $(pwd) -it debian:trixie-slim # sed -i -e 's/Types: deb/& deb-src/' /etc/apt/sources.list.d/debian.sources # apt update # apt upgrade # apt install --no-install-recommends build-essential # apt source ruby-curb # cd ruby-curb-* # apt --no-install-recommends build-dep . # dpkg-buildpackage -us -uc -B ... succeeds ... # sed -i -e 's/Suites: trixie /Suites: sid /' # apt --no-install-recommends install curl ... The following additional packages will be installed: libcurl3t64-gnutls libcurl4-gnutls-dev libcurl4t64 Suggested packages: libcurl4-doc libgnutls28-dev libidn-dev libkrb5-dev libldap2-dev librtmp-dev libssh2-1-dev pkgconf zlib1g-dev The following packages will be REMOVED: libcurl3-gnutls The following NEW packages will be installed: curl libcurl3t64-gnutls libcurl4t64 The following packages will be upgraded: libcurl4-gnutls-dev ... # dpkg-buildpackage -us -uc -B ... fails as seen in the buildd log ... Thanks, smcv
Bug#1069830: libccrtp-doc: missing Breaks+Replaces: libccrtp-dev (<< 2.0.9-3)
Package: libccrtp-doc Version: 2.0.9-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts fileconflict Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces This test intentionally skipped 'testing' to find file overwrite problems before packages migrate from 'unstable' to 'testing'. >From the attached log (scroll to the bottom...): Preparing to unpack .../libccrtp-doc_2.0.9-3_all.deb ... Unpacking libccrtp-doc (2.0.9-3) ... dpkg: error processing archive /var/cache/apt/archives/libccrtp-doc_2.0.9-3_all.deb (--unpack): trying to overwrite '/usr/share/doc/libccrtp-dev/NEWS.gz', which is also in package libccrtp-dev 2.0.9-2.3 Errors were encountered while processing: /var/cache/apt/archives/libccrtp-doc_2.0.9-3_all.deb This is probably caused by a behavior change of dh_installdocs (w.r.t. the doc main package) in newer compat levels. cheers, Andreas libccrtp-dev=2.0.9-2.3_libccrtp-doc=2.0.9-3.log.gz Description: application/gzip
Processed: Re: Bug#1065626: libgtk2.0-0t64 / libgtk2.0-bin dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common
Processing control commands: > severity -1 important Bug #1065626 [aptitude,libgtk2.0-0t64] libgtk2.0-0t64 / libgtk2.0-bin dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common Severity set to 'important' from 'serious' -- 1065626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065626 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1065626: libgtk2.0-0t64 / libgtk2.0-bin dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common
Control: severity -1 important Control: user release.debian@packages.debian.org Control: usertags -1 time-t-downgrade On Thu, Mar 07, 2024 at 04:10:17PM +0100, Vincent Lefevre wrote: > Package: libgtk2.0-0t64 > Version: 2.24.33-4 > Severity: serious > > During an upgrade with aptitude: > > dpkg: dependency problems prevent removal of libgtk2.0-common: > libgtk2.0-bin depends on libgtk2.0-common. > libgtk2.0-0t64:amd64 depends on libgtk2.0-common. > > dpkg: error processing package libgtk2.0-common (--purge): > dependency problems - not removing > Errors were encountered while processing: > libgtk2.0-common > > Note that "apt install -f" has nothing to fix; this upgrade just > triggered a dpkg error (similar to bugs 1065603 and 1065625). > > Moreover, like in these bugs, aptitude did not propose the removal > of libgtk2.0-common: > > Aptitude 0.8.13: log report > Thu, Mar 7 2024 16:01:36 +0100 > > IMPORTANT: this log only lists intended actions; actions which fail > due to dpkg problems may not be completed. > > Will install 5 packages, and remove 2 packages. > 2048 B of disk space will be used > > [...] > [HOLD, DEPENDENCIES] libgtk2.0-common:amd64 2.24.33-3 > [...] > [INSTALL, DEPENDENCIES] libgail18t64:amd64 2.24.33-4 > [INSTALL, DEPENDENCIES] libgtk2.0-0t64:amd64 2.24.33-4 > [REMOVE, DEPENDENCIES] libgail18:amd64 2.24.33-3 > [REMOVE, DEPENDENCIES] libgtk2.0-0:amd64 2.24.33-3 > [...] > [UPGRADE] gtk2-engines-pixbuf:amd64 2.24.33-3 -> 2.24.33-4 > [UPGRADE] libgail-common:amd64 2.24.33-3 -> 2.24.33-4 > [UPGRADE] libgtk2.0-bin:amd64 2.24.33-3 -> 2.24.33-4 > Downgrading this bug to important as it is currently a blocker for aptitude migration due to the dual assignment, and even for libgtk2.0-0t64, I'd argue getting it migrated is more important than a aptitude ordering issue. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Bug#1069793: wrong package name mnt-reform-setup-wizard -- should be reform-setup-wizard
Followup-For: Bug #1069793 reform-setup-wizard misses Breaks+Replaces: mnt-reform-setup-wizard (<< 0.1.0-3) for the package rename. Andreas
Bug#1069826: stravalib: FTBFS: tests fail with ModuleNotFoundError: No module named 'pytz'
Source: stravalib Version: 1.3.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source stravalib recently started to FTBFS, probably due to a change in on eof its (transitive) build-depends: ERRORS __ ERROR collecting stravalib/tests/unit/test_client_utils.py __ ImportError while importing test module '/build/stravalib-1.3.0/stravalib/tests/unit/test_client_utils.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.11/importlib/__init__.py:126: in import_module return _bootstrap._gcd_import(name[level:], package, level) stravalib/__init__.py:1: in from stravalib.client import Client stravalib/client.py:19: in import pytz E ModuleNotFoundError: No module named 'pytz' ... Comparing the current build log with the last successful one from March 16, I noticed that python3-tz does no longer get installed. Andreas stravalib_1.3.0-1.log.gz Description: application/gzip
Bug#1065425: marked as done (Does not upgrade from libpam0t64)
Your message dated Thu, 25 Apr 2024 13:49:54 +0200 with message-id and subject line Re: Bug#1065425: Does not upgrade from libpam0t64 has caused the Debian Bug report #1065425, regarding Does not upgrade from libpam0t64 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1065425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpam0g Version: 1.5.3-6 Severity: serious On my sid system, libpam0g doesn't get upgraded because apt thinks the libpam0t64 package is good enough: $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ apt-cache policy libpam0t64 libpam0t64: Installed: 1.5.3-4 Candidate: 1.5.3-4 Version table: *** 1.5.3-4 100 100 /var/lib/dpkg/status $ apt-cache policy libpam0g libpam0g: Installed: (none) Candidate: 1.5.3-6 Version table: 1.5.3-6 500 500 http://deb.debian.org/debian sid/main amd64 Packages 1.5.2-9.1+b1 -1 100 /var/lib/dpkg/status Christoph --- End Message --- --- Begin Message --- Re: To Debian Bug Tracking System > On my sid system, libpam0g doesn't get upgraded because apt thinks the > libpam0t64 package is good enough: On #debian-devel, helmut and I concluded we'd just close this bug. libpam0t64 never entered testing, and people on unstable should be prepared to sometimes have to manually beat things in shape. Christoph--- End Message ---
Processed: netavark: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101
Processing commands for cont...@bugs.debian.org: > # also happens on amd64 > retitle 1069350 netavark: FTBFS: dh_auto_test: error: > /usr/share/cargo/bin/cargo build returned exit code 101 Bug #1069350 [src:netavark] netavark: FTBFS on arm64: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101 Changed Bug title to 'netavark: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101' from 'netavark: FTBFS on arm64: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069350 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tag
Processing commands for cont...@bugs.debian.org:
> tags 1068730 + ftbfs
Bug #1068730 {Done: Luca Boccassi } [src:systemd] Fails to
build from source since removal of liblz4-tool
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1068730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tag
Processing commands for cont...@bugs.debian.org: > tags 1068389 + ftbfs Bug #1068389 [src:pcp] src:pcp: unsatisfied build dependency in testing: python3-bpfcc Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1068389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068389 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 1069821 to satpy: FTBFS: tests failed
Processing commands for cont...@bugs.debian.org: > retitle 1069821 satpy: FTBFS: tests failed Bug #1069821 [src:satpy] FTBFS: tests failed Changed Bug title to 'satpy: FTBFS: tests failed' from 'FTBFS: tests failed'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069821 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999922: marked as done (xneur: depends on obsolete pcre3 library)
Your message dated Thu, 25 Apr 2024 10:54:43 + with message-id and subject line Bug#22: fixed in xneur 0.20.0-3.1 has caused the Debian Bug report #22, regarding xneur: depends on obsolete pcre3 library to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 22: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=22 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xneur Severity: important User: matthew-pcre...@debian.org Usertags: obsolete-pcre3 Dear maintainer, Your package still depends on the old, obsolete PCRE3[0] libraries (i.e. libpcre3-dev). This has been end of life for a while now, and upstream do not intend to fix any further bugs in it. Accordingly, I would like to remove the pcre3 libraries from Debian, preferably in time for the release of Bookworm. The newer PCRE2 library was first released in 2015, and has been in Debian since stretch. Upstream's documentation for PCRE2 is available here: https://pcre.org/current/doc/html/ Many large projects that use PCRE have made the switch now (e.g. git, php); it does involve some work, but we are now at the stage where PCRE3 should not be used, particularly if it might ever be exposed to untrusted input. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00176.html Regards, Matthew [0] Historical reasons mean that old PCRE is packaged as pcre3 in Debian --- End Message --- --- Begin Message --- Source: xneur Source-Version: 0.20.0-3.1 Done: Andreas Rönnquist We believe that the bug you reported is fixed in the latest version of xneur, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Rönnquist (supplier of updated xneur package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 24 Apr 2024 23:52:01 +0200 Source: xneur Architecture: source Version: 0.20.0-3.1 Distribution: unstable Urgency: medium Maintainer: Alexander GQ Gerasiov Changed-By: Andreas Rönnquist Closes: 22 1037902 Changes: xneur (0.20.0-3.1) unstable; urgency=medium . [ Andreas Rönnquist ] * Non-maintainer upload. * Add patch to port to PCRE2 - Thanks to Yavor Doganov (Closes: #22) * Build depend on pcre2 . [ Bastian Germann ] * Build with -Wno-error=stringop-overflow (Closes: #1037902) Checksums-Sha1: 4eb28a1a51096bd45fbac2b4d14f04c6342a79d5 2070 xneur_0.20.0-3.1.dsc 3cdfd5c28ba18f6b9d99f39a2598a2f90035cdeb 11520 xneur_0.20.0-3.1.debian.tar.xz e22697b019d8cf11c3cebb760bce283412066de0 11060 xneur_0.20.0-3.1_source.buildinfo Checksums-Sha256: 5e26c28246a18c20795ff713c5ffe52f75eaf44ba3386a0131163a26e805321e 2070 xneur_0.20.0-3.1.dsc dee21e92b62b52ac57d0a2343f5dd885861f4e995c588d75ed1c5d20acd3f9bc 11520 xneur_0.20.0-3.1.debian.tar.xz 2be07740b497005601679bc7136403e46f7bec06fe51f21b72889df6882b5e10 11060 xneur_0.20.0-3.1_source.buildinfo Files: 44723681aadb04c498a11b75f9afed13 2070 x11 optional xneur_0.20.0-3.1.dsc 76ff057f71df96ca5607701fe74cd208 11520 x11 optional xneur_0.20.0-3.1.debian.tar.xz 95a2c8c7e5e869b11629abe31d5b3fec 11060 x11 optional xneur_0.20.0-3.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEETq74h7WfgJdjc9ALCHsqoZ75O8IFAmYqL48ACgkQCHsqoZ75 O8LA7A/+NWBg6CyPrxQ7Ucju+rtB9sz7xyuZdcOWfh3lyGsQh1r6oMAEZpRhlTDj JU0Jc8nrOfuOMkLziM5Xpr4jDbT3GooZ+uISMlnOfZ7Rsxqo5NvXB2hdY52saRK4 lk6CwXj+X9nwDEg9QWd3PgLIaFfSTitQ9v7gPTBZGoEMrq20xmwS2v1IHG9DBUSR pMZLGtJAxyEMWpdjbwf59oFi9eM9uqZYI/utsEgVcmnEYnYqaVGFKREXOBn3iMoP QJi/N8Ck8lb96CMo8dUmyehST4hs5BGrWxMorJYOwT6tty0nEFJ9lGuWIFOkEOKi rAOAf6Ttv9BiRtdf8bojAHZ+b4nP8gl5Ln/b8ZBrgOHdCpM+yk2AdZrMfvx3d+d6 gqcuNGJvONuQzrsxYa1NK2KAqau909V6683HFQLxa1ThiQZCyLrgZmNIRts1Llkm 2CzxcoRTHzPUBrjjjncQO2bXL/BH+bZUGBj8Sc5baxSc6K4lLHvMH64JetGxRY2a xHNN327lAbxXv9A/Al/Uc+ULBLbUbB6thQPJhK0che47q6UYdmZ1kW3/ifm20EYu ixobuw2hk73qN3O230nHc61rr1r7w3ygjiuA11yB21YqzwJEgvcKkZZcpPx5uOHH nQ26mHYTzyuafjyh1E4qTeAyZm0KhrhZzyxvwggixpoeErMyjV4= =axWK -END PGP SIGNATURE- pgpkECK7hZi_7.pgp Description: PGP signature --- End Message ---
Bug#1037902: marked as done (xneur: ftbfs with GCC-13)
Your message dated Thu, 25 Apr 2024 10:54:43 + with message-id and subject line Bug#1037902: fixed in xneur 0.20.0-3.1 has caused the Debian Bug report #1037902, regarding xneur: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:xneur Version: 0.20.0-3 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/xneur_0.20.0-3_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] Libnotify linker flags: -lnotify -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 dh_auto_build make -j8 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in lib make[3]: Entering directory '/<>/lib' Making all in notify make[4]: Entering directory '/<>/lib/notify' /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../../lib/config -I../../lib/misc -I../../lib/lib -Wall -Wextra -Werror -g0 -std=gnu99 -fPIC -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/x86_64-linux-gnu -g -O2 -Wall -I/usr/include -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libpng16 -I/usr/include/x86_64-linux-gnu -I/usr/include/libmount -I/usr/include/blkid -pthread -I/usr/include/enchant-2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o libxnnotify_la-notify.lo `test -f 'notify.c' || echo './'`notify.c /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../../lib/config -I../../lib/misc -I../../lib/lib -Wall -Wextra -Werror -g0 -std=gnu99 -fPIC -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/x86_64-linux-gnu -g -O2 -Wall -I/usr/include -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libpng16 -I/usr/include/x86_64-linux-gnu -I/usr/include/libmount -I/usr/include/blkid -pthread -I/usr/include/enchant-2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o libxnnotify_la-osd.lo `test -f 'osd.c' || echo './'`osd.c /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../../lib/config -I../../lib/misc -I../../lib/lib -Wall -Wextra -Werror -g0 -std=gnu99 -fPIC -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/x86_64-linux-gnu -g -O2 -Wall -I/usr/include -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libpng16 -I/usr/include/x86_64-linux-gnu -I/usr/include/libmount -I/usr/include/blkid -pthread -I/usr/include/enchant-2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o libxnnotify_la-popup.lo `test -f 'popup.c' || echo
Bug#1069030: marked as done (subread FTBFS on 32bit architectures: -Werror=implicit-function-declaration)
Your message dated Thu, 25 Apr 2024 10:54:32 + with message-id and subject line Bug#1069030: fixed in subread 2.0.6+dfsg-3 has caused the Debian Bug report #1069030, regarding subread FTBFS on 32bit architectures: -Werror=implicit-function-declaration to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1069030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069030 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: subread Version: 2.0.6+dfsg-2 Severity: serious Tags: ftbfs subread fails to build from source on 32bit architectures: A non-parallel build contains: | i686-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -mtune=generic -msse3 -O3 -fsigned-char -Wall -DMAKE_FOR_EXON -D MAKE_STANDALONE -D SUBREAD_VERSION=\""2.0.6"\" -D_FILE_OFFSET_BITS=64 -fmessage-length=0 -ggdb -Wdate-time -D_FORTIFY_SOURCE=2 -c -o input-files.o input-files.c | input-files.c: In function ‘f_subr_open’: | input-files.c:54:24: error: implicit declaration of function ‘fopen64’; did you mean ‘gzopen64’? [-Werror=implicit-function-declaration] |54 | return fopen64(fname, mode); | |^~~ | |gzopen64 Helmut --- End Message --- --- Begin Message --- Source: subread Source-Version: 2.0.6+dfsg-3 Done: Michael R. Crusoe We believe that the bug you reported is fixed in the latest version of subread, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael R. Crusoe (supplier of updated subread package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 25 Apr 2024 13:38:39 +0300 Source: subread Architecture: source Version: 2.0.6+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Michael R. Crusoe Closes: 1049300 1069030 Changes: subread (2.0.6+dfsg-3) unstable; urgency=medium . * Team upload. * d/control: simplify architecture specification by using the provisions from the architecture-properties package. * d/rules: preserve original mm39_RefSeq_exon.txt.gz to enable building twice. Closes: #1049300 * d/control: update description of subread-data to include the gene annotations for both the hh39 and mm39 genomes. * d/patches/arch_specific_flags.patch: since -D_FILE_OFFSET_BITS=64 is set, use fopen() even on 32-bit systems. Closes: #1069030 Thanks to blhc "E-pointer-trouble-at-implicit" for pointing this out. * d/patches/cross.patch: deleted, as it was unused and incorporated into arch_specific_flags.patch by Alexandre Mestiashvili. * d/upstream/metadata: add publications, bug info, changelog, link to user guide PDF. * d/test/control: python3 is needed Checksums-Sha1: 911efa347ed6f9aed9ecd38ad8e7ab0a952c1ace 2185 subread_2.0.6+dfsg-3.dsc e405e199da83f5223e77fe028b32fa7d29b020f0 19600 subread_2.0.6+dfsg-3.debian.tar.xz 3ced8d5d27afa1d1fdca50afed811903de30c058 6772 subread_2.0.6+dfsg-3_source.buildinfo Checksums-Sha256: 1d048843afd48e20a54f636e208a0c18cfd2d7547942b9f1cf90e99f3332e396 2185 subread_2.0.6+dfsg-3.dsc 2c0bcc064e2ceee01c53cdf91508f10931030580b33a4da9d4fcfc9ec8fd5519 19600 subread_2.0.6+dfsg-3.debian.tar.xz 899d9e5e94691a3dfd0b696569e8a08c21a49ffc44f1e797cb7c63f17a53320b 6772 subread_2.0.6+dfsg-3_source.buildinfo Files: e3a1b82606ea03e1a39f1be926eb30d9 2185 science optional subread_2.0.6+dfsg-3.dsc f4a898483ea601dda3f2334cfcd7be98 19600 science optional subread_2.0.6+dfsg-3.debian.tar.xz 95b3982fdabad195069509b7fc6a97e8 6772 science optional subread_2.0.6+dfsg-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAmYqMwsACgkQPCZ2P2xn 5uIckw/8CY0g0X16oZ71LnaYHsLgPgbiChzcP1j8KVTM2FMv1w3Yam3err0d7wug kZwotnG0GoQjfoMYfbcQGdWjzXEGiehaQmmrMPnJ4NaOMkgNlDKq+JFIFVO3S4JD ROgxemcDxL4Jl0/5NgyKrU/z9M4VE/WbsJ4oqXlE6orup0ai+yYvIOLyFDfT4xHh RhwUg/tiE/dhBk6rnyASdQ08dE6vP4NND8vczuxHXKQtlCIIP1UIKpb7bvooh05r
Bug#1069821: FTBFS: tests failed
Source: satpy Version: 0.47.0-2 Severity: serious Tags: ftbfs ERRORS ___ ERROR collecting satpy/tests/reader_tests/test_viirs_edr_active_fires.py ___ satpy/tests/reader_tests/test_viirs_edr_active_fires.py:30: in import dask.dataframe as dd /usr/lib/python3/dist-packages/dask/dataframe/__init__.py:81: in from dask.dataframe import backends, dispatch, rolling /usr/lib/python3/dist-packages/dask/dataframe/backends.py:15: in from dask.dataframe.core import DataFrame, Index, Scalar, Series, _Frame /usr/lib/python3/dist-packages/dask/dataframe/core.py:36: in from dask.dataframe import methods /usr/lib/python3/dist-packages/dask/dataframe/methods.py:34: in from dask.dataframe.utils import is_dataframe_like, is_index_like, is_series_like /usr/lib/python3/dist-packages/dask/dataframe/utils.py:20: in from dask.dataframe import ( # noqa: F401 register pandas extension types /usr/lib/python3/dist-packages/dask/dataframe/_dtypes.py:9: in from dask.dataframe.extensions import make_array_nonempty, make_scalar /usr/lib/python3/dist-packages/dask/dataframe/extensions.py:8: in from dask.dataframe.accessor import ( /usr/lib/python3/dist-packages/dask/dataframe/accessor.py:126: in class DatetimeAccessor(Accessor): /usr/lib/python3/dist-packages/dask/dataframe/accessor.py:81: in __init_subclass__ _bind_property(cls, pd_cls, attr, min_version) /usr/lib/python3/dist-packages/dask/dataframe/accessor.py:35: in _bind_property setattr(cls, attr, property(derived_from(pd_cls, version=min_version)(func))) /usr/lib/python3/dist-packages/dask/utils.py:858: in wrapper method.__doc__ = _derived_from( /usr/lib/python3/dist-packages/dask/utils.py:811: in _derived_from method_args = get_named_args(method) /usr/lib/python3/dist-packages/dask/utils.py:572: in get_named_args s = inspect.signature(func) /usr/lib/python3.11/inspect.py:3263: in signature return Signature.from_callable(obj, follow_wrapped=follow_wrapped, /usr/lib/python3.11/inspect.py:3011: in from_callable return _signature_from_callable(obj, sigcls=cls, /usr/lib/python3.11/inspect.py:2599: in _signature_from_callable call = _descriptor_get(call, obj) /usr/lib/python3.11/inspect.py:2432: in _descriptor_get return get(descriptor, obj, type(obj)) E TypeError: descriptor '__call__' for 'type' objects doesn't apply to a 'property' object -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1069818: FTBFS: tests failed
Source: toolz Version: 0.12.0-2 Severity: serious Tags: ftbfs === FAILURES === test_inspect_wrapped_property _ def test_inspect_wrapped_property(): class Wrapped(object): def __init__(self, func): self.func = func def __call__(self, *args, **kwargs): return self.func(*args, **kwargs) @property def __wrapped__(self): return self.func func = lambda x: x wrapped = Wrapped(func) assert inspect.signature(func) == inspect.signature(wrapped) > assert num_required_args(Wrapped) is None E AssertionError: assert 1 is None E+ where 1 = num_required_args(.Wrapped'>) toolz/tests/test_inspect_args.py:485: AssertionError -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1069819: FTBFS: tests failed
Source: python-tooz Version: 4.2.0-2 Severity: serious Tags: ftbfs == FAIL: tooz.tests.test_mysql.TestMySQLDriver.test_parsing_blocking_settings tooz.tests.test_mysql.TestMySQLDriver.test_parsing_blocking_settings -- testtools.testresult.real._StringException: Traceback (most recent call last): File "/usr/lib/python3.12/unittest/mock.py", line 1390, in patched return func(*newargs, **newkeywargs) ^ File "/<>/tooz/tests/test_mysql.py", line 113, in test_parsing_blocking_settings with lock(blocking_value): File "/<>/tooz/locking.py", line 29, in __enter__ return self.lock.__enter__(*self.args, **self.kwargs) ^^ File "/<>/tooz/locking.py", line 49, in __enter__ acquired = self.acquire(*args, **kwargs) ^ File "", line 3, in acquire File "/usr/lib/python3.12/unittest/mock.py", line 1134, in __call__ return self._mock_call(*args, **kwargs) File "/usr/lib/python3.12/unittest/mock.py", line 1138, in _mock_call return self._execute_mock_call(*args, **kwargs) File "/usr/lib/python3.12/unittest/mock.py", line 1211, in _execute_mock_call return self._mock_wraps(*args, **kwargs) ^ TypeError: 'bool' object is not callable == FAIL: tooz.tests.test_mysql.TestMySQLDriver.test_parsing_timeout_settings tooz.tests.test_mysql.TestMySQLDriver.test_parsing_timeout_settings -- testtools.testresult.real._StringException: Traceback (most recent call last): File "/usr/lib/python3.12/unittest/mock.py", line 1390, in patched return func(*newargs, **newkeywargs) ^ File "/<>/tooz/tests/test_mysql.py", line 100, in test_parsing_timeout_settings with lock(blocking_value, timeout): File "/<>/tooz/locking.py", line 29, in __enter__ return self.lock.__enter__(*self.args, **self.kwargs) ^^ File "/<>/tooz/locking.py", line 49, in __enter__ acquired = self.acquire(*args, **kwargs) ^ File "", line 3, in acquire File "/usr/lib/python3.12/unittest/mock.py", line 1134, in __call__ return self._mock_call(*args, **kwargs) File "/usr/lib/python3.12/unittest/mock.py", line 1138, in _mock_call return self._execute_mock_call(*args, **kwargs) File "/usr/lib/python3.12/unittest/mock.py", line 1211, in _execute_mock_call return self._mock_wraps(*args, **kwargs) ^ TypeError: 'bool' object is not callable == FAIL: tooz.tests.test_coordination.TestAPI.test_lock_context_manager_acquire_argument tooz.tests.test_coordination.TestAPI.test_lock_context_manager_acquire_argument -- testtools.testresult.real._StringException: Traceback (most recent call last): File "/<>/tooz/tests/__init__.py", line 35, in skip_if_not_implemented return func(*args, **kwargs) ^ File "/<>/tooz/tests/test_coordination.py", line 928, in test_lock_context_manager_acquire_argument with lock(blocking_value): File "/<>/tooz/locking.py", line 29, in __enter__ return self.lock.__enter__(*self.args, **self.kwargs) ^^ File "/<>/tooz/locking.py", line 49, in __enter__ acquired = self.acquire(*args, **kwargs) ^ File "", line 3, in acquire File "/usr/lib/python3.12/unittest/mock.py", line 1134, in __call__ return self._mock_call(*args, **kwargs) File "/usr/lib/python3.12/unittest/mock.py", line 1138, in _mock_call return self._execute_mock_call(*args, **kwargs) File "/usr/lib/python3.12/unittest/mock.py", line 1211, in _execute_mock_call return self._mock_wraps(*args, **kwargs) ^ TypeError: 'bool' object is not callable -- Ran 148 tests in 6.368s FAILED (failures=3, skipped=51) -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental')
Bug#1069816: Autopkgtests fail
Package: python3-argcomplete
Version: 3.1.4-1
Severity: serious
https://ci.debian.net/packages/p/python-argcomplete/unstable/amd64/45886560/
102s ==
102s ERROR: test_repl_parse_after_complete
(__main__.TestArgcompleteREPL.test_repl_parse_after_complete)
102s --
102s Traceback (most recent call last):
102s File "/tmp/autopkgtest-
lxc.q4aft1il/downtmp/autopkgtest_tmp/test/test.py", line 925, in
test_repl_parse_after_complete
102s args = p.parse_args(["--foo", "spam", "bar"])
102s^^
102s File "/usr/lib/python3.12/argparse.py", line 1908, in parse_args
102s args, argv = self.parse_known_args(args, namespace)
102s ^^
102s File "/usr/lib/python3.12/argparse.py", line 1941, in parse_known_args
102s namespace, args = self._parse_known_args(args, namespace)
102s ^^^
102s File "/usr/lib/python3/dist-packages/argcomplete/packages/_argparse.py",
line 299, in _parse_known_args
102s start_index = consume_optional(start_index)
102s ^
102s File "/usr/lib/python3/dist-packages/argcomplete/packages/_argparse.py",
line 165, in consume_optional
102s action, option_string, explicit_arg = option_tuple
102s ^^^
102s ValueError: too many values to unpack (expected 3)
102s
102s ==
102s FAIL: test_choices (__main__.TestArgcomplete.test_choices)
102s --
102s Traceback (most recent call last):
102s File "/tmp/autopkgtest-
lxc.q4aft1il/downtmp/autopkgtest_tmp/test/test.py", line 170, in test_choices
102s self.assertEqual(set(self.run_completer(make_parser(), cmd)),
set(output))
102s AssertionError: Items in the first set but not the second:
102s '-h'
102s '--help'
102s '--ship'
102s Items in the second set but not the first:
102s 'speedboat'
102s 'submarine'
102s
102s ==
102s FAIL: test_completers (__main__.TestArgcomplete.test_completers)
102s --
102s Traceback (most recent call last):
102s File "/tmp/autopkgtest-
lxc.q4aft1il/downtmp/autopkgtest_tmp/test/test.py", line 291, in
test_completers
102s self.assertEqual(set(self.run_completer(make_parser(), cmd)),
set(output))
102s AssertionError: Items in the first set but not the second:
102s '--url'
102s '--email'
102s '-h'
102s '--help'
102s Items in the second set but not the first:
102s 'http://url1'
102s 'http://url2'
102s
102s ==
102s FAIL: test_default_completer
(__main__.TestArgcomplete.test_default_completer)
102s --
102s Traceback (most recent call last):
102s File "/tmp/autopkgtest-
lxc.q4aft1il/downtmp/autopkgtest_tmp/test/test.py", line 415, in
test_default_completer
102s self.assertEqual(set(self.run_completer(make_parser(), cmd)),
set(output))
102s AssertionError: Items in the first set but not the second:
102s '--one'
102s '--many'
102s Items in the second set but not the first:
102s 'test/'
102s
102s ==
102s FAIL: test_escape_special_chars
(__main__.TestArgcomplete.test_escape_special_chars)
102s --
102s Traceback (most recent call last):
102s File "/tmp/autopkgtest-
lxc.q4aft1il/downtmp/autopkgtest_tmp/test/test.py", line 823, in
test_escape_special_chars
102s self.assertEqual(set(self.run_completer(make_parser(), "prog -1 ")),
{r"bar\<\$\>baz "})
102s AssertionError: Items in the first set but not the second:
102s '-1'
102s '-2'
102s '-3'
102s Items in the second set but not the first:
102s 'bar\\<\\$\\>baz '
102s
102s ==
102s FAIL: test_exclusive (__main__.TestArgcomplete.test_exclusive)
102s --
102s Traceback (most recent call last):
102s File "/tmp/autopkgtest-
lxc.q4aft1il/downtmp/autopkgtest_tmp/test/test.py", line 764, in test_exclusive
102s self.assertEqual(set(self.run_completer(make_parser(), cmd)),
set(output))
102s AssertionError: Items in the first set but not the second:
102s '--no-bar'
102s
102s ==
102s FAIL: test_exclusive_class (__main__.TestArgcomplete.test_exclusive_class)
102s --
102s Traceback (most recent call
Bug#1069815: wesnoth-1.8-server: new package installs systemd unit in aliased location
Package: wesnoth-1.18-server Version: 1:1.17.26-1 Severity: serious Justification: do not introduce aliased files into Debian Hi, I noticed that wesnoth-1.18-server is a new package and installs a file below /lib, which is an aliased location that we try to empty to complete the /usr-move transition via DEP17. I am filing this bug at RC-severity to stop it from migrating to trixie and hope you agree with this. Please downgrade if you disagree though note that this kind of issue will become an RC-bug for all packages later in the trixie cycle. The simplest fix to this problem is changing SYSTEMD_SERVICE = debian/wesnoth-$(BRANCH_VERSION)-server/lib/systemd/system/wesnoth-$(BRANCH_VERSION)-server.service in debian/rules and move the file to /usr/lib. This is mostly safe for backports, except that bookworm's debhelper will fail to generate necessary maintainer scripts. Please bump your debhelper dependency to 13.11.6 (available in bookworm-backports). Alternatively, adding dh-sequence-movetousr to Build-Depends should also resolve the matter, but for a new package I'd prefer to fix this right from the start. Both solutions are likely applicable to other wesnoth versions as well, though we don't consider those RC-bugs yet. Helmut
Processed: Bug#1069030 marked as pending in subread
Processing control commands: > tag -1 pending Bug #1069030 [src:subread] subread FTBFS on 32bit architectures: -Werror=implicit-function-declaration Added tag(s) pending. -- 1069030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069030 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069030: marked as pending in subread
Control: tag -1 pending Hello, Bug #1069030 in subread 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/med-team/subread/-/commit/dcce3f3c1dc10acfeac38ae9e3c0449d9de9187e we already fixed this. Closes: #1069030 (this message was generated automatically) -- Greetings https://bugs.debian.org/1069030
Bug#1069814: golang-github-aydinnyunus-blockchain: FTBFS: Tries network access during build
Package: src:golang-github-aydinnyunus-blockchain Version: 0.0~git20220623.647ebea-1 Severity: serious Tags: ftbfs Dear maintainer: This package tries network access during build: = TESTING ADDRESSES = querying...https://blockchain.info/multiaddr?active=162FjqU7RYdojnejCDe6zrPDUpaLcv9Hhq|1K3Vs8tPu2YkAoWmrkjUQVJuxr7wgPP 3Wf Get "https://blockchain.info/multiaddr?active=162FjqU7RYdojnejCDe6zrPDUpaLcv9Hhq|1K3Vs8tPu2YkAoWmrkjUQVJuxr7wgPP3Wf": dial tcp: lookup blockchain.info on [::1]:53: read udp [::1]:44899->[::1]:53: read: connection refused--- PASS: TestGe tAddresses (0.00s) This is why it fails to build in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-aydinnyunus-blockchain.html Thanks.
Bug#1053334: galera-4: FTBFS because of expired certificates
El 25/4/24 a las 7:15, Otto Kekäläinen escribió: Bullseye oldstable update request filed in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069802 You can +1 it if you want to show support. Thanks a lot! We don't +1 because this is not twitter/facebook :-) but I have just made a comment to explain why the update is important. Thanks.
Bug#1064311: rdkit: NMU diff for 64-bit time_t transition
Hi Chris, On 2024-04-25 00:57, Chris Hofstaedtler wrote: t64 is already in unstable and making its way to testing. So you are a bit late with getting rdkit fixed for t64. An upload with t64 binaries is required as soon as possible. Given the packages have to go to binary-NEW, you must upload with binaries, and then probably follow up with a source-only upload once they are ACCEPTed. Thanks for the information. I will upload rdkit ASAP. Best, Andrius
Bug#1066753: marked as done (python-django-extensions: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Thu, 25 Apr 2024 08:43:32 +
with message-id
and subject line Bug#1066753: fixed in python-django-extensions 3.2.3-2
has caused the Debian Bug report #1066753,
regarding python-django-extensions: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1066753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-extensions
Version: 3.2.3-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir docs/images
> ln debian/images/* docs/images
> PYTHONPATH=. python3 -m sphinx -b html -N docs docs/.build/html
> Running Sphinx v7.2.6
> making output directory... done
> WARNING: html_static_path entry '_static' does not exist
> building [mo]: targets for 0 po files that are out of date
> writing output...
> building [html]: targets for 35 source files that are out of date
> updating environment: [new config] 35 added, 0 changed, 0 removed
> [2Kreading sources... [ 3%] admin_extensions
> [2Kreading sources... [ 6%] admin_generator
> [2Kreading sources... [ 9%] command_extensions
> [2Kreading sources... [ 11%] command_signals
> [2Kreading sources... [ 14%] create_template_tags
> [2Kreading sources... [ 17%] debugger_tags
> [2Kreading sources... [ 20%] delete_squashed_migrations
> [2Kreading sources... [ 23%] dumpscript
> [2Kreading sources... [ 26%] export_emails
> [2Kreading sources... [ 29%] field_extensions
> [2Kreading sources... [ 31%] generate_password
> [2Kreading sources... [ 34%] graph_models
> [2Kreading sources... [ 37%] index
> [2Kreading sources... [ 40%] installation_instructions
> [2Kreading sources... [ 43%] jobs_scheduling
> [2Kreading sources... [ 46%] list_model_info
> [2Kreading sources... [ 49%] list_signals
> [2Kreading sources... [ 51%] managestate
> [2Kreading sources... [ 54%] merge_model_instances
> [2Kreading sources... [ 57%] model_extensions
> [2Kreading sources... [ 60%] permissions
> [2Kreading sources... [ 63%] print_settings
> [2Kreading sources... [ 66%] reset_db
> [2Kreading sources... [ 69%] runprofileserver
> [2Kreading sources... [ 71%] runscript
> [2Kreading sources... [ 74%] runserver_plus
> [2Kreading sources... [ 77%] shell_plus
> [2Kreading sources... [ 80%] sqlcreate
> [2Kreading sources... [ 83%] sqldiff
> [2Kreading sources... [ 86%] sqldsn
> [2Kreading sources... [ 89%] sync_s3
> [2Kreading sources... [ 91%] syncdata
> [2Kreading sources... [ 94%] utilities
> [2Kreading sources... [ 97%] validate_templates
> [2Kreading sources... [100%] validators
>
> /<>/docs/managestate.rst:2: WARNING: Title underline too short.
>
> managestate
> ==
> /<>/docs/managestate.rst:53: WARNING: Title underline too short.
>
> Examples
>
> /<>/docs/managestate.rst:53: WARNING: Title underline too short.
>
> Examples
>
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> copying assets... copying static files... done
> copying extra files... done
> done
> [2Kwriting output... [ 3%] admin_extensions
> [2Kwriting output... [ 6%] admin_generator
> [2Kwriting output... [ 9%] command_extensions
> [2Kwriting output... [ 11%] command_signals
> [2Kwriting output... [ 14%] create_template_tags
> [2Kwriting output... [ 17%] debugger_tags
> [2Kwriting output... [ 20%] delete_squashed_migrations
> [2Kwriting output... [ 23%] dumpscript
> [2Kwriting output... [ 26%] export_emails
> [2Kwriting output... [ 29%] field_extensions
> [2Kwriting output... [ 31%] generate_password
> [2Kwriting output... [ 34%] graph_models
> [2Kwriting output... [ 37%] index
> [2Kwriting output... [ 40%] installation_instructions
> [2Kwriting output... [ 43%] jobs_scheduling
> [2Kwriting output... [ 46%] list_model_info
> [2Kwriting output... [ 49%] list_signals
> [2Kwriting output... [ 51%] managestate
> [2Kwriting output... [ 54%] merge_model_instances
> [2Kwriting output... [ 57%] model_extensions
> [2Kwriting output... [ 60%] permissions
> [2Kwriting output... [ 63%] print_settings
> [2Kwriting output... [ 66%] reset_db
> [2Kwriting output... [ 69%] runprofileserver
> [2Kwriting output... [ 71%] runscript
>
Bug#1069762: pdns-recursor: CVE-2024-25583 - 4.8.8 for stable
* Moritz Muehlenhoff [240425 08:44]: > On Thu, Apr 25, 2024 at 08:37:14AM +0200, Chris Hofstaedtler wrote: > > Hi Moritz, > > > > could we once again use the upstream release for stable? > > debdiff 4.8.7-1 -> 4.8.8-1 is attached. > > Ack. Following the 4.8 releases has served us well. debdiff looks fine, > please build with -sa and upload to security-master. Done. Thanks, Chris
