Processed: Bug#1071641 marked as pending in openscap
Processing control commands: > tag -1 pending Bug #1071641 [openscap] openscap: requires internet during build Added tag(s) pending. -- 1071641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071641 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071641: marked as pending in openscap
Control: tag -1 pending Hello, Bug #1071641 in openscap 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/debian/openscap/-/commit/5b18226a7864a4c2d4f35960059198b79c1becf0 Add patch to skip tests that require internet The upstream solution is flaky at best, the patch comments out the tests that needs internet. Closes: #1071641 (this message was generated automatically) -- Greetings https://bugs.debian.org/1071641
Bug#1068190: marked as done (telegram-desktop: FTBFS with abseil 20230802: (.text+0x270): undefined reference to `absl::debian3::base_internal::ThrowStdOutOfRange(char const*)')
Your message dated Fri, 24 May 2024 10:32:44 +0500 with message-id and subject line Re: Bug#1068190: telegram-desktop: FTBFS with abseil 20230802: (.text+0x270): undefined reference to `absl::debian3::base_internal::ThrowStdOutOfRange(char const*)' has caused the Debian Bug report #1068190, regarding telegram-desktop: FTBFS with abseil 20230802: (.text+0x270): undefined reference to `absl::debian3::base_internal::ThrowStdOutOfRange(char const*)' 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.) -- 1068190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068190 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: telegram-desktop Version: 4.14.9+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=telegram-desktop=arm64=4.14.9%2Bds-1%2Bb2=1711978921=0 cd /<>/obj-aarch64-linux-gnu/Telegram && /usr/bin/cmake -E cmake_link_script CMakeFiles/Telegram.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -ftemplate-backtrace-limit=0 -Wdate-time -D_FORTIFY_SOURCE=2 -Werror=invalid-pch -Wl,-z,relro -Wl,-z,now -Wno-alloc-size-larger-than -Wno-stringop-overflow -Wno-odr -Wno-inline -pthread -Wl,--as-needed @CMakeFiles/Telegram.dir/objects1.rsp -o ../telegram-desktop liblib_tgcalls_legacy.a liblib_tgcalls.a lib_base/liblib_base.a lib_ui/liblib_ui.a lib_spellcheck/liblib_spellcheck.a lib_webview/liblib_webview.a liblib_tgvoip_bundled.a /usr/lib/aarch64-linux-gnu/libminizip.so liblib_tgcalls.a /usr/lib/aarch64-linux-gnu/libopenal.so /usr/lib/aarch64-linux-gnu/libtg_owt.a /usr/lib/aarch64-linux-gnu/libsrtp2.so /usr/lib/aarch64-linux-gnu/libprotobuf.so /usr/lib/aarch64-linux-gnu/libssl.so /usr/lib/aarch64-linux-gnu/libcrypto.so /usr/lib/aarch64-linux-gnu/libopus.so /usr/lib/aarch64-linux-gnu/libabsl_flags_parse.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_flags_usage.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_flags_usage_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_flags_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_flags_marshalling.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_flags_reflection.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_cord.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_cordz_info.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_cord_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_cordz_functions.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_cordz_handle.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_crc_cord_state.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_crc32c.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_str_format_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_crc_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_crc_cpu_detect.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_raw_hash_set.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_hash.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_city.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_low_level_hash.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_hashtablez_sampler.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_exponential_biased.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_flags_config.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_flags_private_handle_accessor.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_flags_commandlineflag.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_flags_commandlineflag_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_flags_program_name.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_bad_optional_access.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_synchronization.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_graphcycles_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_kernel_timeout_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_stacktrace.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_symbolize.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_malloc_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_debugging_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_demangle_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_time.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_strings.so.20230802.0.1
Bug#1070302: marked as done (Not installable (depends on removed libabsl20220623t64))
Your message dated Fri, 24 May 2024 10:39:40 +0500 with message-id and subject line Re: Bug#1070302: Not installable (depends on removed libabsl20220623t64) has caused the Debian Bug report #1070302, regarding Not installable (depends on removed libabsl20220623t64) 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.) -- 1070302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070302 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: telegram-desktop Version: 4.14.9+ds-1+b1 Severity: grave Control: block -1 by 1068190 telegram-desktop wasn't rebuilt with new libabsl because of #1068190 and so it's no longer installable in unstable: Unsatisfied dependencies: telegram-desktop : Depends: libabsl20220623t64 (>= 0~20220623.0-1) but it is not installable -- Package-specific info: -- 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.12-amd64 (SMP w/16 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 Versions of packages telegram-desktop depends on: ii libabsl20220623t64 20220623.1-3.1 ii libavcodec60 7:6.1.1-4 ii libavfilter9 7:6.1.1-4 ii libavformat607:6.1.1-4 ii libavutil58 7:6.1.1-4 ii libc62.37-19 ii libgcc-s114-20240429-1 ii libglib2.0-0t64 2.78.4-7 ii libglibmm-2.68-1t64 2.78.1-2.2 ii libhunspell-1.7-01.7.2+really1.7.2-10+b2 ii libjpeg62-turbo 1:2.1.5-3 ii libkf5coreaddons55.107.0-1+b2 ii liblz4-1 1.9.4-2 ii libminizip1t64 1:1.3.dfsg-3.1 ii libopenal1 1:1.23.1-4+b1 ii libopus0 1.4-1+b1 ii libqrcodegencpp1 1.8.0-1.2+b1 ii libqt5core5t64 [qtbase-abi-5-15-10] 5.15.10+dfsg-7.2+b1 ii libqt5gui5t645.15.10+dfsg-7.2+b1 ii libqt5network5t645.15.10+dfsg-7.2+b1 ii libqt5qml5 5.15.10+dfsg-2+b2 ii libqt5quick5 5.15.10+dfsg-2+b2 ii libqt5quickwidgets5 5.15.10+dfsg-2+b2 ii libqt5svg5 5.15.10-2+b2 ii libqt5waylandcompositor5 5.15.10-2+b2 ii libqt5widgets5t645.15.10+dfsg-7.2+b1 ii librlottie0-10.1+dfsg-4+b2 ii libsigc++-3.0-0 3.6.0-2 ii libsrtp2-1 2.5.0-3+b1 ii libssl3t64 3.2.1-3 ii libstdc++6 14-20240429-1 ii libswresample4 7:6.1.1-4 ii libswscale7 7:6.1.1-4 ii libvpx8 1.13.1-2+b1 ii libx11-6 2:1.8.7-1+b1 ii libxcb-keysyms1 0.4.0-1+b2 ii libxcb-record0 1.17.0-1 ii libxcb-screensaver0 1.17.0-1 ii libxcb1 1.17.0-1 ii libxcomposite1 1:0.4.5-1+b1 ii libxdamage1 1:1.1.6-1+b1 ii libxext6 2:1.3.4-1+b1 ii libxfixes3 1:6.0.0-2+b1 ii libxrandr2 2:1.5.4-1 ii libxtst6 2:1.2.3-1.1+b1 ii libxxhash0 0.8.2-2+b1 ii libyuv0 0.0~git202401110.af6ac82-1 ii qt5-image-formats-plugins5.15.10-2+b2 ii zlib1g 1:1.3.dfsg-3.1 Versions of packages telegram-desktop recommends: ii fonts-open-sans 1.11-2 ii libwebkit2gtk-4.1-0 2.44.1-1+b1 telegram-desktop suggests no packages. Versions of packages telegram-desktop is related to: ii xdg-desktop-portal 1.18.4-1 ii xdg-desktop-portal-kde [xdg-desktop-portal-backend] 5.27.10-1+b1 -- debconf-show failed [2024.05.03 17:50:51] Launched version: 4014009, install beta: [FALSE], alpha: 0, debug mode: [FALSE]
Bug#1071007: marked as done (sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py)
Your message dated Fri, 24 May 2024 03:04:11 + with message-id and subject line Bug#1071007: fixed in sherlock 0.14.3+git20240522.ab5fcbb-1 has caused the Debian Bug report #1071007, regarding sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py 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.) -- 1071007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071007 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sherlock Version: 0.14.3+git20240511.b83f5be-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + pycrc sherlock has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/python3/dist-packages/__init__.py is contained in the packages * pycrc/0.10.0-2 as present in trixie|unstable * sherlock/0.14.3+git20240511.b83f5be-1 as present in unstable 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 --- Source: sherlock Source-Version: 0.14.3+git20240522.ab5fcbb-1 Done: Josenilson Ferreira da Silva We believe that the bug you reported is fixed in the latest version of sherlock, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josenilson Ferreira da Silva (supplier of updated sherlock 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, 23 May 2024 23:15:16 -0300 Source: sherlock Architecture: source Version: 0.14.3+git20240522.ab5fcbb-1 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Josenilson Ferreira da Silva Closes: 1071007 Changes: sherlock (0.14.3+git20240522.ab5fcbb-1) unstable; urgency=medium . * New upstream version 0.14.3+git20240522.ab5fcbb * debian/control: Removed sessoion Conflicts and Replaces * debian/rules: Removed usr/lib directory * debian/sherlock.install: Package moved to usr/share (Closes: #1071007) Checksums-Sha1: 1e14b64be7fbbf6b645136357e0ef1b7756db424 2431 sherlock_0.14.3+git20240522.ab5fcbb-1.dsc ba18fcbbf6fe2c418e9857f5dd522614b145eb85 186296 sherlock_0.14.3+git20240522.ab5fcbb.orig.tar.xz 84b9ac6d5f3ccf57f551134342d340afd03e321b 5444 sherlock_0.14.3+git20240522.ab5fcbb-1.debian.tar.xz 37bb24a0fc4b8671f7e2852175b98dae363948f5 9439 sherlock_0.14.3+git20240522.ab5fcbb-1_source.buildinfo Checksums-Sha256: 0d7862bfb1cecb42ab7e0499072d76ca5b252ed5fbfc154ed4ead0ef46ea2fe7 2431 sherlock_0.14.3+git20240522.ab5fcbb-1.dsc 2a594204ce58ad8ce261f3e58942e946a29848b0eafb8ea540b659c65329897d 186296 sherlock_0.14.3+git20240522.ab5fcbb.orig.tar.xz 487f948ef9f03ea2c2e89dc02c3c5b2312ede4d85ed8468053762df0fbcaf2d4 5444 sherlock_0.14.3+git20240522.ab5fcbb-1.debian.tar.xz 53d2e291d4642a2d841c9a2c47dd719cf3f15329b0c68dbbffc438c4a3adc1f7 9439 sherlock_0.14.3+git20240522.ab5fcbb-1_source.buildinfo Files: 96a963916ad0df7f58871ecb7525742f 2431 misc optional sherlock_0.14.3+git20240522.ab5fcbb-1.dsc a04a7a3daabaf3648d66fb652783a60b 186296 misc optional sherlock_0.14.3+git20240522.ab5fcbb.orig.tar.xz 1843c197e006492da7dbcba85118106f 5444 misc optional sherlock_0.14.3+git20240522.ab5fcbb-1.debian.tar.xz 376fef7ffe31841a4a681f4cce510e6b 9439 misc optional sherlock_0.14.3+git20240522.ab5fcbb-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEqBlNXRF+LQLfMNMNB6n1YjE0Rs0FAmZP/bsACgkQB6n1YjE0 Rs0fDhAArXEyjBhpSjJE0SK7eJ0QALW55IwLebLEABn2LvtRCK9Wcp2yMchqK3Sm dLkOD6ch0wVIbCa0orJuwrLnV9b5/mRcOvAM6RtNvpi7OwDKhHdr4wGQBqitmi1v lzc9pjV+D4zqFUHAKb1RrBMCvhP9QWKtEo0Q0cFtDpPolckQleiJrJGw6Kg54s3i
Bug#1071007:
Hi! As Sherlock is a private module, I moved it to usr/share according to this policy here: https://www.debian.org/doc/packaging-manuals/python-policy/#programs-shipping-private-modules It is not necessary to __init__py of the package as suggested by Samuel. Thank you everyone for your help! Nilson F. Silva
Bug#1071521: ukui-screensaver: predictable filenames under /tmp with system()
Hi. This bug is same as1064340. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064340 We will fix it and upload at soon. Thanks. xibowen
Processed: tags
Processing commands for cont...@bugs.debian.org: > tags 1061526 + ftbfs Bug #1061526 [src:astroidmail] astroidmail: Stop using webkit2gtk 4.0 Added tag(s) ftbfs. > tags 1063232 + ftbfs Bug #1063232 [src:gamehub] gamehub: Stop using webkit2gtk 4.0 Added tag(s) ftbfs. > tags 1061406 + ftbfs Bug #1061406 [src:geany-plugins] geany-plugins: Stop using webkit2gtk 4.0 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1061406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061406 1061526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061526 1063232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071311: marked as done (gpsd: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file)
Your message dated Thu, 23 May 2024 21:05:33 +
with message-id
and subject line Bug#1071311: fixed in gpsd 3.25-4
has caused the Debian Bug report #1071311,
regarding gpsd: FTBFS: dpkg-gensymbols: error: some symbols or patterns
disappeared in the symbols file
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.)
--
1071311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gpsd
Version: 3.25-3
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
if [ ! -f SConscript.deb_revision ]; then \
cp SConscript SConscript.deb_revision ;\
sed -i '/^revision=/s/%(.*)/%("3.25-3",)/' SConscript ;\
fi
touch SConscript.deb_revision
set -e ; export LDFLAGS="-Wl,-z,relro -Wl,-z,now" ; export CFLAGS="-g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security
-fcf-protection" ; export CXXFLAGS="-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection" ; export CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2";
python3 /usr/bin/scons shared=no prefix=/usr systemd=yes nostrip=yes dbus_export=yes docdir=/usr/share/doc/gpsd
libdir=/usr/lib/x86_64-linux-gnu gpsd_user=gpsd gpsd_group=dialout qt_versioned=5 python_libdir=/usr/lib/python3/dist-packages manbuild=yes
debug=no target_python=python3 -j2
scons: Reading SConscript files ...
scons version: 4.5.2
scons is running under Python version: 3.11.9.final.0
gpsd version: 3.25
This system is: linux
cc is gcc, version 13.2.0
Checking whether the C compiler works... yes
[... snipped ...]
cd gpsd-3.25; ./regress-driver -q -o -t test/daemon/venus634lp.log
Processing test/daemon/venus634lp.log
Regression test test/daemon/udp-test.log successful
cd gpsd-3.25; ./regress-driver -q -o -t test/daemon/zodiac.log
Processing test/daemon/zodiac.log
Regression test test/daemon/venus634lp.log successful
Regression test test/daemon/zodiac.log successful
scons: done building targets.
Ensure your PYTHONPATH includes /usr/lib/python3/dist-packages/
touch build-stamp
for source in debian/libgpsLIBGPSSONAME.install
debian/libgpsLIBGPSSONAME.lintian-overrides debian/libgpsLIBGPSSONAME.symbols
debian/libqgpsmmLIBGPSSONAME.install
debian/libqgpsmmLIBGPSSONAME.lintian-overrides
debian/libqgpsmmLIBGPSSONAME.symbols; do \
target=$(echo "$source" | sed 's,LIBGPSSONAME,30t64,g') ;\
sed 's,LIBGPSSONAME,30,g; s,LIBGPS_PKG_SUFFIX,30t64,g' "$source" >
"$target" ;\
done
dh_testdir
dh_testroot
dh_prep
set -e ; export LDFLAGS="-Wl,-z,relro -Wl,-z,now" ; export CFLAGS="-g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security
-fcf-protection" ; export CXXFLAGS="-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection" ; export CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2";
DESTDIR=`pwd`/debian/tmp python3 /usr/bin/scons install prefix=/usr systemd=yes nostrip=yes dbus_export=yes docdir=/usr/share/doc/gpsd
libdir=/usr/lib/x86_64-linux-gnu gpsd_user=gpsd gpsd_group=dialout qt_versioned=5 python_libdir=/usr/lib/python3/dist-packages manbuild=yes
debug=no target_python=python3
scons: Reading SConscript files ...
scons version: 4.5.2
scons is running under Python version: 3.11.9.final.0
gpsd version: 3.25
This system is: linux
cc is gcc, version 13.2.0
Checking whether the C compiler works... (cached) yes
Checking if compiler accepts -pthread... (cached) yes
Checking whether the C++ compiler works... (cached) yes
Checking for C header file curses.h... (cached) yes
Checking pkg-config for ncurses... (cached) yes
Checking pkg-config for tinfo... (cached) yes
Checking pkg-config for libusb-1.0... (cached) yes
Checking for C library librt... (cached) yes
Checking for C library libnsl... (cached) no
Checking for C library libsocket... (cached) no
Checking for C library libm... (cached) yes
Checking for C library libthr... (cached) no
Checking pkg-config for dbus-1... (cached) yes
Checking pkg-config for bluez... (cached) yes
Checking for C type in_port_t... (cached) yes
Checking whether SUN_LEN is declared... (cached) yes
Checking for C header file linux/can.h... (cached) yes
You have kernel
Bug#1067705: marked as done (src:siridb-server: flaky autopkgtest: curl: (7) Failed to connect to localhost port 9020 after 0 ms: Couldn't connect to server)
Your message dated Thu, 23 May 2024 20:50:07 + with message-id and subject line Bug#1067705: fixed in siridb-server 2.0.51-3 has caused the Debian Bug report #1067705, regarding src:siridb-server: flaky autopkgtest: curl: (7) Failed to connect to localhost port 9020 after 0 ms: Couldn't connect to server 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.) -- 1067705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067705 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: siridb-server Version: 2.0.51-2 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of your package. I noticed that it regularly fails. From a distance, this looks like a race condition. Should the test ensure the server is started? Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Don't hesitate to reach out if you need help and some more information from our infrastructure. Paul [1] https://ci.debian.net/packages/s/siridb-server/testing/amd64/44324499/ 19s autopkgtest [11:10:05]: test http-api: [--- 19s * fixing /etc/siridb/siridb.conf 19s * restarting siridb-server 19s * run queries 19s get-version 19s curl: (7) Failed to connect to localhost port 9020 after 0 ms: Couldn't connect to server 19s cat: res.txt: No such file or directory 19s autopkgtest [11:10:05]: test http-api: ---] OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: siridb-server Source-Version: 2.0.51-3 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of siridb-server, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated siridb-server 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, 23 May 2024 22:34:09 +0200 Source: siridb-server Architecture: source Version: 2.0.51-3 Distribution: unstable Urgency: medium Maintainer: SiriDB Maintainers Changed-By: Paul Gevers Closes: 1067705 Changes: siridb-server (2.0.51-3) unstable; urgency=medium . * tests: add --retry to first curl to avoid failing if siridb-server isn't ready yet (Closes: #1067705) Checksums-Sha1: 28b15a02ad189e8331a620f439f8a224e141d454 2002 siridb-server_2.0.51-3.dsc 69a1e1ab269448a02056fbfc984cef696aaa64c9 5680 siridb-server_2.0.51-3.debian.tar.xz Checksums-Sha256: 950b0cebaf51a6fff37a058c49a6e1ad4695e7d5a7c15dfc61b76056225ada22 2002 siridb-server_2.0.51-3.dsc 01d2854a1962e9c20ca5e8a541784e1f69c3641ca66ac5c75e18510f74bb3947 5680 siridb-server_2.0.51-3.debian.tar.xz Files: 88ba64c03939a2311b0d7a46b657d995 2002 database optional siridb-server_2.0.51-3.dsc 708f720f190ed6fe6a7ec20db08d5d5c 5680 database optional siridb-server_2.0.51-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmZPqJEACgkQnFyZ6wW9 dQrkowgAiB9gOK3jeL+UTMxpBAVlybJp1eWnM4rGbrhP8zaJaIXXQz18TmmWIpd0 M6fsup3lucU5DUK4u8wc5z/QUfqExAVDkrzDBmR/VVNnYC3TD0hP/dNIlbLxIHHo PPk9J/nu2SbchhlcTFuStpS60nLvr0jmcgeHoO1750Jm+fnEvOJcGlqBuoKu7iy9 1wKPtNh3Om4ODKPIlSV6gBhs6WoTqJ/EeO7n6RlBsvJczHUIJwdSmqiphz7SWmCl jkoZ3dxaOLbuDLJqbSd5ppOGkpwGaRc/OMx3nmv9dsi8JBzO9q8Z1IUZT3IsojSt V8o4CNw78EOcgyr3nn+r4Jxsc/5W6Q== =4djY -END PGP SIGNATURE- pgp25pW6AJLUT.pgp Description: PGP signature --- End Message ---
Bug#1064938: isospec - maintainer does not access email from ftp-master
Hi Bastian, > It seems to be fixed. My mailbox contains the last bounce on > March, 8th. On Mar 10 I rolled back the changes I did some weeks before to reduce the debichem-devel moderation queue: https://salsa.debian.org/alioth-lists-team/support/-/issues/27 Sorry for not following up on this bug, and thanks for confirming that it's already fixed. Cheers, Alex -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Alex Muntada ⢿⡄⠘⠷⠚⠋ Debian Developer log.alexm.org ⠈⠳⣄ signature.asc Description: PGP signature
Bug#1071328: lomiri-indicator-network: FTBFS: unit-tests failed
Control: block -1 by 1071690
On Fr 17 Mai 2024 22:39:15 CEST, Santiago Vila wrote:
Package: src:lomiri-indicator-network
Version: 1.0.2-4
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
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DENABLE_TESTS=ON \
cd obj-x86_64-linux-gnu &&
DEB_PYTHON_INSTALL_LAYOUT=deb cmake -DCMAKE_INSTALL_PREFIX=/usr
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc
-DCMAKE_INSTALL_LOCALSTATEDIR=/var
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
-DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON
-DFETCHCONTENT_FULLY_DISCONNECTED=ON
-DCMAKE_INSTALL_RUNSTATEDIR=/run
-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles"
-DCMAKE_VERBOSE_MAKEFILE=ON
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DENABLE_TESTS=ON ..
-- The C compiler identification is GNU 13.2.0
-- The CXX compiler identification is GNU 13.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
[... snipped ...]
1: 1715965979.445 GetAll /org/freedesktop/NetworkManager
org.freedesktop.NetworkManager
1: 1715965979.445 Get
/org/freedesktop/NetworkManager/ActiveConnection/0
org.freedesktop.NetworkManager.Connection.Active.Id
1: 1715965979.445 GetAll
/org/freedesktop/NetworkManager/ActiveConnection/0
org.freedesktop.NetworkManager.Connection.Active
1: 1715965979.445 Get
/org/freedesktop/NetworkManager/ActiveConnection/0
org.freedesktop.NetworkManager.Connection.Active.Type
1: 1715965979.445 GetAll
/org/freedesktop/NetworkManager/ActiveConnection/0
org.freedesktop.NetworkManager.Connection.Active
1: 1715965979.446 Get
/org/freedesktop/NetworkManager/ActiveConnection/0
org.freedesktop.NetworkManager.VPN.Connection.VpnState
1: 1715965979.446 GetAll
/org/freedesktop/NetworkManager/ActiveConnection/0
org.freedesktop.NetworkManager.VPN.Connection
1: 1715965979.446 Get
/org/freedesktop/NetworkManager/ActiveConnection/0
org.freedesktop.NetworkManager.Connection.Active.State
1: 1715965979.446 GetAll
/org/freedesktop/NetworkManager/ActiveConnection/0
org.freedesktop.NetworkManager.Connection.Active
1: 1715965979.446 Get
/org/freedesktop/NetworkManager/ActiveConnection/0
org.freedesktop.NetworkManager.Connection.Active.Connection
1: 1715965979.446 GetAll
/org/freedesktop/NetworkManager/ActiveConnection/0
org.freedesktop.NetworkManager.Connection.Active
1: [ OK ] TestConnectivityApiVpn.UpdatesVpnState (691 ms)
1: [ RUN ] TestConnectivityApiVpn.ReadsOpenvpnProperties
1: Debug: /<>/tests/data/networkmanager.py ((null):0, (null))
1: 1715965979.896 AddModem "ril_0" {"Powered": False}
1: 1715965979.898 GetAll /ril_0 org.ofono.Modem
1: 1715965979.898 emit / org.ofono.Manager.ModemAdded "/ril_0"
{"Online": True, "Powered": True, "Lockdown": False, "Emergency":
False, "Manufacturer": "Fakesys", "Model": "Mock Modem", "Revision":
"0815.42", "Serial": "12345678-1234-1234-1234-", "Type":
"hardware", "Interfaces": ["org.ofono.CallVolume",
"org.ofono.VoiceCallManager", "org.ofono.NetworkRegistration",
"org.ofono.SimManager", "org.ofono.ConnectionManager"], "Features":
["gprs", "net"]}
1: 1715965979.898 SetProperty "Bearer" "none"
1: 1715965979.899 Set /ril_0 org.ofono.ConnectionManager.Bearer "none"
1: 1715965979.899 emit /ril_0
org.freedesktop.DBus.Properties.PropertiesChanged
"org.ofono.ConnectionManager" {"Bearer": "none"} []
1: 1715965979.899 emit /ril_0
org.ofono.ConnectionManager.PropertyChanged "Bearer" "none"
1: 1715965979.899 SetProperty "Powered" False
1: 1715965979.899 Set /ril_0 org.ofono.ConnectionManager.Powered False
1: 1715965979.899 emit /ril_0
org.freedesktop.DBus.Properties.PropertiesChanged
"org.ofono.ConnectionManager" {"Powered": False} []
1: 1715965979.899 emit /ril_0
org.ofono.ConnectionManager.PropertyChanged "Powered" False
1: 1715965979.900 SetProperty "Attached" False
1: 1715965979.900 Set /ril_0 org.ofono.ConnectionManager.Attached False
1: 1715965979.900 emit /ril_0
org.freedesktop.DBus.Properties.PropertiesChanged
"org.ofono.ConnectionManager" {"Attached": False} []
1: 1715965979.900 emit /ril_0
org.ofono.ConnectionManager.PropertyChanged "Attached" False
1: 1715965979.901 AddConnection {"connection": {"id": "apple",
"timestamp": 1441979296, "type": "vpn", "uuid":
"b81a1cf4-37de-4497-925a-9d4e0e22ba76"}, "ipv4": {"addresses": [],
"dns": [], "method": "auto", "never-default": True, "routes": []},
"ipv6": {"addresses": [], "dns": [], "ip6-privacy": 0, "method":
"auto", "never-default": True, "routes": []}, "vpn": {"data": {"ca":
"/my/ca.crt", "cert": "/my/cert.crt",
Processed: Re: Bug#1071328: lomiri-indicator-network: FTBFS: unit-tests failed
Processing control commands: > block -1 by 1071690 Bug #1071328 [src:lomiri-indicator-network] lomiri-indicator-network: FTBFS: unit-tests failed 1071328 was not blocked by any bugs. 1071328 was not blocking any bugs. Added blocking bug(s) of 1071328: 1071690 -- 1071328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070965: xmlrpc
Hi, Per request, the "util" library was split out in it's own package. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071465 It was an act of balancing between the easy & clean solution. Greetings
Processed: BTS housekeeping
Processing commands for cont...@bugs.debian.org:
> reassign 1050355 libbtas-dev
Bug #1050355 [src:tiledarray] tiledarray has unfulfilled build dependencies
Bug reassigned from package 'src:tiledarray' to 'libbtas-dev'.
No longer marked as found in versions tiledarray/1.0.0-1.
Ignoring request to alter fixed versions of bug #1050355 to the same values
previously set
> forcemerge 1028634 1050355
Bug #1028634 [libbtas-dev] libbtas-dev requires blaspp
Bug #1028634 [libbtas-dev] libbtas-dev requires blaspp
Added tag(s) trixie and sid.
Bug #1050355 [libbtas-dev] tiledarray has unfulfilled build dependencies
Added indication that 1050355 affects src:tiledarray
Marked as found in versions btas/0.0+git20221014.147bf4d4-1.
Merged 1028634 1050355
> close 1064747
Bug #1064747 [src:libpappsomspp] libpappsomspp: FTBFS: build-dependency not
installable: libodsstream-dev (>= 0.9.7)
Marked Bug as done
> close 1064769
Bug #1064769 [src:minexpert2] minexpert2: FTBFS: unsatisfiable
build-dependencies: libpappsomspp-dev (>= 0.9.24), libpappsomspp-widget-dev (>=
0.9.24)
Marked Bug as done
> reassign 1069516 src:openmpi
Bug #1069516 [src:abinit] abinit: FTBFS on armhf: tests fail
Bug reassigned from package 'src:abinit' to 'src:openmpi'.
No longer marked as found in versions abinit/9.10.4-3.
Ignoring request to alter fixed versions of bug #1069516 to the same values
previously set
> forcemerge 1070300 1069516
Bug #1070300 {Done: Samuel Thibault } [src:openmpi]
pmix_psquash_base_select failed during MPI_INIT on 32bit architectures
Bug #1069460 {Done: Samuel Thibault } [src:openmpi]
bitshuffle: FTBFS on armhf: tests fail
Bug #1069516 [src:openmpi] abinit: FTBFS on armhf: tests fail
Marked Bug as done
Added indication that 1069516 affects src:bitshuffle,src:dune-grid
Marked as fixed in versions openmpi/4.1.6-13.1.
Marked as found in versions openmpi/4.1.6-13.
Bug #1069460 {Done: Samuel Thibault } [src:openmpi]
bitshuffle: FTBFS on armhf: tests fail
Merged 1069460 1069516 1070300
> affects 1070300 src:abinit
Bug #1070300 {Done: Samuel Thibault } [src:openmpi]
pmix_psquash_base_select failed during MPI_INIT on 32bit architectures
Bug #1069460 {Done: Samuel Thibault } [src:openmpi]
bitshuffle: FTBFS on armhf: tests fail
Bug #1069516 {Done: Samuel Thibault } [src:openmpi]
abinit: FTBFS on armhf: tests fail
Added indication that 1070300 affects src:abinit
Added indication that 1069460 affects src:abinit
Added indication that 1069516 affects src:abinit
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1028634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028634
1050355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050355
1064747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064747
1064769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064769
1069460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069460
1069516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069516
1070300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 1071288
Processing commands for cont...@bugs.debian.org: > close 1071288 0.0.96.1-1 Bug #1071288 [src:quaternion] quaternion: FTBFS: /<>/client/roomdialogs.cpp:30:10: fatal error: logging.h: No such file or directory Marked as fixed in versions quaternion/0.0.96.1-1. Bug #1071288 [src:quaternion] quaternion: FTBFS: /<>/client/roomdialogs.cpp:30:10: fatal error: logging.h: No such file or directory Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1071288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071288 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071302: marked as done (cppgir: FTBFS: Segmentation fault while "Generating wrapper code for: GObject-2.0;Gio-2.0;Gst-1.0;Gtk-3.0")
Your message dated Thu, 23 May 2024 19:04:10 + with message-id and subject line Bug#1071302: fixed in cppgir 2.0-2.1 has caused the Debian Bug report #1071302, regarding cppgir: FTBFS: Segmentation fault while "Generating wrapper code for: GObject-2.0;Gio-2.0;Gst-1.0;Gtk-3.0" 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.) -- 1071302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071302 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:cppgir Version: 2.0-2 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 debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' dh_auto_configure -- -DCMAKE_INSTALL_LIBDIR=lib -DINTERNAL_EXPECTED=OFF -DGENERATED_DIR=/<>/debian/tmp cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_INSTALL_LIBDIR=lib -DINTERNAL_EXPECTED=OFF -DGENERATED_DIR=/<>/debian/tmp .. -- The C compiler identification is GNU 13.2.0 -- The CXX compiler identification is GNU 13.2.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features [... snipped ...] [ 24%] Linking CXX executable gi-test /usr/bin/cmake -E cmake_link_script CMakeFiles/gi-test.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now "CMakeFiles/gi-test.dir/test/main.cpp.o" -o gi-test libltest.a -L/usr/lib/x86_64-linux-gnu -lgobject-2.0 -lglib-2.0 make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' [ 24%] Built target gi-test make -f CMakeFiles/gi-test-17.dir/build.make CMakeFiles/gi-test-17.dir/depend make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<> /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/CMakeFiles/gi-test-17.dir/DependInfo.cmake "--color=" make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f CMakeFiles/gi-test-17.dir/build.make CMakeFiles/gi-test-17.dir/build make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' [ 27%] Building CXX object CMakeFiles/gi-test-17.dir/test/main.cpp.o /usr/bin/c++ -I/<>/obj-x86_64-linux-gnu -I/<> -I/<>/gi -I/<>/override -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++23 -Wall -Wextra -Wnon-virtual-dtor -I/usr/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -pthread -MD -MT CMakeFiles/gi-test-17.dir/test/main.cpp.o -MF CMakeFiles/gi-test-17.dir/test/main.cpp.o.d -o CMakeFiles/gi-test-17.dir/test/main.cpp.o -c /<>/test/main.cpp In file included from /<>/gi/gi.hpp:31, from /<>/test/main.cpp:10: /<>/gi/container.hpp:451:21: warning: ‘template struct std::iterator’ is deprecated [-Wdeprecated-declarations] 451 | : public std::iterator>/test/main.cpp:1: /usr/include/c++/13/bits/stl_iterator_base_types.h:127:34: note: declared here 127 | struct _GLIBCXX17_DEPRECATED iterator | ^~~~ /<>/gi/container.hpp:771:34: warning: ‘template struct std::iterator’ is deprecated [-Wdeprecated-declarations] 771 | class iterator_t : public std::iterator>/gi/container.hpp:11: /<>/test/main.cpp: In function ‘void test_collection()’: /<>/test/main.cpp:1092:21: warning: suggest parentheses around assignment used as truth value [-Wparentheses] 1092 | assert(uac[i] = a[i]); /<>/test/main.cpp:1108:21: warning: suggest parentheses around assignment used as truth value [-Wparentheses] 1108 | assert(uac[i] = a[i]); [ 29%] Building CXX object CMakeFiles/cppgir.dir/tools/genutils.cpp.o
Processed: cppgir: diff for NMU version 2.0-2.1
Processing control commands: > tags 1071302 + patch Bug #1071302 [src:cppgir] cppgir: FTBFS: Segmentation fault while "Generating wrapper code for: GObject-2.0;Gio-2.0;Gst-1.0;Gtk-3.0" Added tag(s) patch. > tags 1071302 + pending Bug #1071302 [src:cppgir] cppgir: FTBFS: Segmentation fault while "Generating wrapper code for: GObject-2.0;Gio-2.0;Gst-1.0;Gtk-3.0" Added tag(s) pending. -- 1071302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071302 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071302: cppgir: diff for NMU version 2.0-2.1
Control: tags 1071302 + patch
Control: tags 1071302 + pending
Dear maintainer,
I've prepared an NMU for cppgir (versioned as 2.0-2.1) and
uploaded it to unstable.
Regards.
--
WBR, wRAR
diff -Nru cppgir-2.0/debian/changelog cppgir-2.0/debian/changelog
--- cppgir-2.0/debian/changelog 2024-01-08 13:48:52.0 +0500
+++ cppgir-2.0/debian/changelog 2024-05-23 23:50:03.0 +0500
@@ -1,3 +1,11 @@
+cppgir (2.0-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix crashing on Gio-2.0 (Closes: #1071302).
+ * Fix several other FTBFS reasons.
+
+ -- Andrey Rakhmatullin Thu, 23 May 2024 23:50:03 +0500
+
cppgir (2.0-2) unstable; urgency=medium
* Add gi-restrict-string-template-conversion-operator.patch from upstream Git.
diff -Nru cppgir-2.0/debian/patches/9a0dcf3ae382f153f20e483bd80f3dea97d98ee1.patch cppgir-2.0/debian/patches/9a0dcf3ae382f153f20e483bd80f3dea97d98ee1.patch
--- cppgir-2.0/debian/patches/9a0dcf3ae382f153f20e483bd80f3dea97d98ee1.patch 1970-01-01 05:00:00.0 +0500
+++ cppgir-2.0/debian/patches/9a0dcf3ae382f153f20e483bd80f3dea97d98ee1.patch 2024-05-23 22:25:45.0 +0500
@@ -0,0 +1,33 @@
+From 9a0dcf3ae382f153f20e483bd80f3dea97d98ee1 Mon Sep 17 00:00:00 2001
+From: Mark Nauwelaerts
+Date: Sat, 20 Jan 2024 14:33:29 +0100
+Subject: [PATCH] tools: avoid null pointer access
+
+Fixes issue #67
+---
+ tools/repository.cpp | 7 +--
+ 1 file changed, 5 insertions(+), 2 deletions(-)
+
+diff --git a/tools/repository.cpp b/tools/repository.cpp
+index 9d54743..fcffcbe 100644
+--- a/tools/repository.cpp
b/tools/repository.cpp
+@@ -129,10 +129,13 @@ Repository::add(const key_type , const mapped_type::tree_type )
+ auto it = self.index.find(qualified);
+ bool registered = false;
+
+- if (it != self.index.end()) {
++ if (girname.empty()) {
++// should not make it here
++assert(false);
++ } else if (it != self.index.end()) {
+ auto = it->second;
+ // merge in tree data for predefined
+-if (e.info->flags & TYPE_PREDEFINED) {
++if (e.info && (e.info->flags & TYPE_PREDEFINED)) {
+ e.tree = std::make_unique(n);
+ } else {
+ throw std::runtime_error(
+--
+GitLab
+
diff -Nru cppgir-2.0/debian/patches/a262132e608170142cebd10896d6679b4fe1f3cb.patch cppgir-2.0/debian/patches/a262132e608170142cebd10896d6679b4fe1f3cb.patch
--- cppgir-2.0/debian/patches/a262132e608170142cebd10896d6679b4fe1f3cb.patch 1970-01-01 05:00:00.0 +0500
+++ cppgir-2.0/debian/patches/a262132e608170142cebd10896d6679b4fe1f3cb.patch 2024-05-23 23:13:28.0 +0500
@@ -0,0 +1,33 @@
+From a262132e608170142cebd10896d6679b4fe1f3cb Mon Sep 17 00:00:00 2001
+From: Mark Nauwelaerts
+Date: Sun, 21 Jan 2024 12:58:23 +0100
+Subject: [PATCH] data: ignore some private glib symbols
+
+---
+ data/cppgir.ignore | 10 ++
+ 1 file changed, 10 insertions(+)
+
+diff --git a/data/cppgir.ignore b/data/cppgir.ignore
+index 17de080..3d7f569 100644
+--- a/data/cppgir.ignore
b/data/cppgir.ignore
+@@ -52,6 +52,16 @@ Gio:function:g_networking_init
+ Gio:method:g_io_module_(load|unload)
+ Gio:function:g_io_module_query
+
++# private parts of the above; these should not make into the GIRs
++# but they might if gobject-introspection was built with embedded glib (meson wrapper)
++GModule:constant:MODULE_IMPL_.*
++GLib:constant:TRACE_.*
++GLib:function:trace_.*
++GLib:function:set_prgname_once
++Gio:function:to_rrtype
++Gio:class:ThreadedResolver
++GObject:bitfield:IOCondition
++
+ # Gst
+ Gst:constant:ERROR_SYSTEM
+ Gst:callback:DebugFuncPtr
+--
+GitLab
+
diff -Nru cppgir-2.0/debian/patches/b4642d32c04c082aa48874320d49a602077f8d84.patch cppgir-2.0/debian/patches/b4642d32c04c082aa48874320d49a602077f8d84.patch
--- cppgir-2.0/debian/patches/b4642d32c04c082aa48874320d49a602077f8d84.patch 1970-01-01 05:00:00.0 +0500
+++ cppgir-2.0/debian/patches/b4642d32c04c082aa48874320d49a602077f8d84.patch 2024-05-23 23:02:56.0 +0500
@@ -0,0 +1,29 @@
+From b4642d32c04c082aa48874320d49a602077f8d84 Mon Sep 17 00:00:00 2001
+From: Mark Nauwelaerts
+Date: Sat, 20 Jan 2024 14:35:14 +0100
+Subject: [PATCH] tools: discard entries without name
+
+... such as glib:boxed entries
+---
+ tools/genns.cpp | 5 -
+ 1 file changed, 4 insertions(+), 1 deletion(-)
+
+diff --git a/tools/genns.cpp b/tools/genns.cpp
+index cc5336c..4d0db78 100644
+--- a/tools/genns.cpp
b/tools/genns.cpp
+@@ -1271,7 +1271,10 @@ public:
+ const auto = get_name(n.second, std::nothrow);
+ auto = n.first;
+ // redirect to oblivion
+- if (ctx.match_ignore.matches(ns, el, {name})) {
++ // empty name might originate from a glib:boxed with glib:name attribute
++ // discard those as well, as that is a glib type without C-type
++ // (which are not really useful in our situation)
++ if (name.empty() || ctx.match_ignore.matches(ns, el, {name})) {
+ logger(Log::INFO, "ignoring {} {}", el, name);
+ } else {
+ ctx.repo.add(name, n);
+--
Bug#1071691: nim: (build)-depends on obsolete pcre3 library
Source: nim Version: 1.6.10-1 Severity: serious Dear maintainer, Your package still (build-)depends on the old, obsolete PCRE library (i.e. libpcre3). This has been end of life for a while now, and upstream do not intend to fix any further bugs in it. Accordingly, the pcre3 library is being removed from Debian. 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/ Maybe think of dropping nimgrep to get rid of the dependency or ask upstream to port to PCRE2. This is an add-on to the mass bug filing that was discussed on debian-devel in https://lists.debian.org/debian-devel/2021/11/msg00176.html
Bug#1064938: isospec - maintainer does not access email from ftp-master
Hi On Thu, May 23, 2024 at 08:55:46PM +0300, Adrian Bunk wrote: > Was this any misconfiguration on the debian.org side, > or is/was this any issue at alioth-lists.debian.net, > or what else might have gone wrong here? It seems to be fixed. My mailbox contains the last bounce on March, 8th. Bastian -- Totally illogical, there was no chance. -- Spock, "The Galileo Seven", stardate 2822.3
Bug#1071689: cpl-plugin-visir-calib: visir-kit-4.4.2*.tar.gz is no longer downloadable
Package: cpl-plugin-visir-calib Version: 4.4.2+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up cpl-plugin-visir-calib (4.4.2+dfsg-1) ... --2024-05-23 12:16:55-- ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.4.2.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:16:55 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:16:55-- ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.4.2-1.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:16:56 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:16:56-- ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.4.2-2.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:16:56 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:16:56-- ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.4.2-3.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:16:57 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:16:57-- ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.4.2-4.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:16:57 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:16:58-- ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.4.2-5.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:16:58 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:16:58-- ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.4.2-6.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:16:58 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:16:58-- ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.4.2-7.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:16:59 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:16:59-- ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.4.2-8.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:16:59 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:16:59-- ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.4.2-9.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:17:00 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now dpkg: error processing package cpl-plugin-visir-calib (--configure): installed cpl-plugin-visir-calib package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.38-11) ... Errors were encountered while processing: cpl-plugin-visir-calib cheers, Andreas cpl-plugin-visir-calib_4.4.2+dfsg-1.log.gz Description: application/gzip
Bug#1071688: cpl-plugin-vimos-calib: vimos-kit-4.1.7*.tar.gz is no longer downloadable
Package: cpl-plugin-vimos-calib Version: 4.1.7+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up cpl-plugin-vimos-calib (4.1.7+dfsg-2) ... --2024-05-23 12:21:00-- ftp://ftp.eso.org/pub/dfs/pipelines/vimos/vimos-kit-4.1.7.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:21:01 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:21:01-- ftp://ftp.eso.org/pub/dfs/pipelines/vimos/vimos-kit-4.1.7-1.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:21:02 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:21:02-- ftp://ftp.eso.org/pub/dfs/pipelines/vimos/vimos-kit-4.1.7-2.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:21:02 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:21:02-- ftp://ftp.eso.org/pub/dfs/pipelines/vimos/vimos-kit-4.1.7-3.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:21:03 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:21:03-- ftp://ftp.eso.org/pub/dfs/pipelines/vimos/vimos-kit-4.1.7-4.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:21:03 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:21:03-- ftp://ftp.eso.org/pub/dfs/pipelines/vimos/vimos-kit-4.1.7-5.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:21:04 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:21:04-- ftp://ftp.eso.org/pub/dfs/pipelines/vimos/vimos-kit-4.1.7-6.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:21:04 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:21:04-- ftp://ftp.eso.org/pub/dfs/pipelines/vimos/vimos-kit-4.1.7-7.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:21:05 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:21:05-- ftp://ftp.eso.org/pub/dfs/pipelines/vimos/vimos-kit-4.1.7-8.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:21:05 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:21:05-- ftp://ftp.eso.org/pub/dfs/pipelines/vimos/vimos-kit-4.1.7-9.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:21:06 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now dpkg: error processing package cpl-plugin-vimos-calib (--configure): installed cpl-plugin-vimos-calib package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.38-11) ... Errors were encountered while processing: cpl-plugin-vimos-calib cheers, Andreas cpl-plugin-vimos-calib_4.1.7+dfsg-2.log.gz Description: application/gzip
Bug#1071686: php-mockery: depends on obsolete pcre3 library
Package: php-mockery Severity: serious Dear maintainer, Your package still depends on the old, obsolete PCRE library (i.e. libpcre3). This has been end of life for a while now, and upstream do not intend to fix any further bugs in it. Accordingly, the pcre3 library is being removed from Debian. 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/ One of the patches already removes the composer dependency, so please also drop it from debian/control. This is an add-on to the mass bug filing that was discussed on debian-devel in https://lists.debian.org/debian-devel/2021/11/msg00176.html
Bug#1071685: cpl-plugin-uves-calib: uves-kit-6.1.8*.tar.gz is no longer downloadable
Package: cpl-plugin-uves-calib Version: 6.1.8+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up cpl-plugin-uves-calib (6.1.8+dfsg-2) ... --2024-05-23 12:18:15-- ftp://ftp.eso.org/pub/dfs/pipelines/uves/uves-kit-6.1.8.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:18:16 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:18:16-- ftp://ftp.eso.org/pub/dfs/pipelines/uves/uves-kit-6.1.8-1.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:18:17 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:18:17-- ftp://ftp.eso.org/pub/dfs/pipelines/uves/uves-kit-6.1.8-2.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:18:17 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:18:17-- ftp://ftp.eso.org/pub/dfs/pipelines/uves/uves-kit-6.1.8-3.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:18:18 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:18:18-- ftp://ftp.eso.org/pub/dfs/pipelines/uves/uves-kit-6.1.8-4.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:18:18 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:18:18-- ftp://ftp.eso.org/pub/dfs/pipelines/uves/uves-kit-6.1.8-5.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:18:19 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:18:19-- ftp://ftp.eso.org/pub/dfs/pipelines/uves/uves-kit-6.1.8-6.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:18:19 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:18:19-- ftp://ftp.eso.org/pub/dfs/pipelines/uves/uves-kit-6.1.8-7.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:18:20 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:18:20-- ftp://ftp.eso.org/pub/dfs/pipelines/uves/uves-kit-6.1.8-8.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:18:20 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:18:20-- ftp://ftp.eso.org/pub/dfs/pipelines/uves/uves-kit-6.1.8-9.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:18:21 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now dpkg: error processing package cpl-plugin-uves-calib (--configure): installed cpl-plugin-uves-calib package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.38-11) ... Errors were encountered while processing: cpl-plugin-uves-calib cheers, Andreas cpl-plugin-uves-calib_6.1.8+dfsg-2.log.gz Description: application/gzip
Processed: Re: Bug#1070256 closed by Debian FTP Masters (reply to Alec Leamas ) (Bug#1070256: fixed in libcxx-serial 1.2.1-6)
Processing control commands:
> reopen -1
Bug #1070256 {Done: Alec Leamas } [src:libcxx-serial]
libcxx-serial FTBFS with the nocheck build profile
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libcxx-serial/1.2.1-6.
--
1070256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1070256: closed by Debian FTP Masters (reply to Alec Leamas ) (Bug#1070256: fixed in libcxx-serial 1.2.1-6)
Control: reopen -1 On Sun, May 12, 2024 at 07:09:07PM +, Debian Bug Tracking System wrote: >... > Changes: > libcxx-serial (1.2.1-6) trixie; urgency=medium > . >* Avoid crash when running with nocheck profile. Closes: #1070256 >... 1.2.1-7 does still FTBFS: https://buildd.debian.org/status/fetch.php?pkg=libcxx-serial=sh4=1.2.1-7=1715548569=0 ifeq (,$(findstring nocheck,$(DEB_BUILD_PROFILES))) ENABLE_TESTS := ON else ENABLE_TESTS := OFF endif This should be DEB_BUILD_OPTIONS, not DEB_BUILD_PROFILES. cu Adrian
Bug#1071683: confget: autopkgtest regression in testing
Source: confget Version: 5.1.2-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer Sometime around 2024-02-27, confget's autopkgtest regressed in testing [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/c/confget/testing/amd64/ 95s autopkgtest [19:08:12]: test feature-check: [--- 95s error: unexpected argument '-q' found 95s 95s tip: to pass '-q' as a value, use '-- -q' 95s 95s Usage: feature-check [OPTIONS] [EXPRESSIONS]... 95s autopkgtest [19:08:12]: test feature-check: ---]
Bug#1071682: cpl-plugin-muse-calib: muse-kit-2.8.7*.tar.gz is no longer downloadable
Package: cpl-plugin-muse-calib Version: 2.8.7+dfsg-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up cpl-plugin-muse-calib (2.8.7+dfsg-3) ... --2024-05-23 12:19:37-- ftp://ftp.eso.org/pub/dfs/pipelines/muse/muse-kit-2.8.7.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:19:38 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:19:38-- ftp://ftp.eso.org/pub/dfs/pipelines/muse/muse-kit-2.8.7-1.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:19:38 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:19:38-- ftp://ftp.eso.org/pub/dfs/pipelines/muse/muse-kit-2.8.7-2.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:19:39 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:19:39-- ftp://ftp.eso.org/pub/dfs/pipelines/muse/muse-kit-2.8.7-3.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:19:39 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:19:39-- ftp://ftp.eso.org/pub/dfs/pipelines/muse/muse-kit-2.8.7-4.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:19:40 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:19:40-- ftp://ftp.eso.org/pub/dfs/pipelines/muse/muse-kit-2.8.7-5.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:19:40 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:19:40-- ftp://ftp.eso.org/pub/dfs/pipelines/muse/muse-kit-2.8.7-6.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:19:41 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:19:41-- ftp://ftp.eso.org/pub/dfs/pipelines/muse/muse-kit-2.8.7-7.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:19:41 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:19:41-- ftp://ftp.eso.org/pub/dfs/pipelines/muse/muse-kit-2.8.7-8.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:19:42 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:19:42-- ftp://ftp.eso.org/pub/dfs/pipelines/muse/muse-kit-2.8.7-9.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:19:42 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now dpkg: error processing package cpl-plugin-muse-calib (--configure): installed cpl-plugin-muse-calib package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.38-11) ... Errors were encountered while processing: cpl-plugin-muse-calib cheers, Andreas cpl-plugin-muse-calib_2.8.7+dfsg-3.log.gz Description: application/gzip
Bug#1071618: marked as done (kannel-dev: depends on obsolete libpcre3-dev)
Your message dated Thu, 23 May 2024 18:04:16 + with message-id and subject line Bug#1071618: fixed in kannel 1.4.5-17 has caused the Debian Bug report #1071618, regarding kannel-dev: depends on obsolete libpcre3-dev 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.) -- 1071618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kannel-dev Version: 1.4.5-16 Severity: serious Hi, kannel-dev depends on libpcre3-dev, which is going to be removed. Given pcre3 support was removed in 1.4.5-13, that dependency can probably just go away. Cheers, Emilio --- End Message --- --- Begin Message --- Source: kannel Source-Version: 1.4.5-17 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of kannel, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated kannel 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, 23 May 2024 18:43:57 +0200 Source: kannel Architecture: source Version: 1.4.5-17 Distribution: unstable Urgency: medium Maintainer: Debian VoIP Team Changed-By: Bastian Germann Closes: 1071618 Changes: kannel (1.4.5-17) unstable; urgency=medium . * Team upload. * Drop unused dependency. (Closes: #1071618) Checksums-Sha1: 00bd507be2c4be5b9438beba39d5454de7ad0330 2213 kannel_1.4.5-17.dsc d1986e584e144718cac3031a8975f73d68d3e256 24108 kannel_1.4.5-17.debian.tar.xz c66785be40df78b7caf55f83ff1abd9154fa9c83 5648 kannel_1.4.5-17_source.buildinfo Checksums-Sha256: 0e32baa7fd1aab2abb2c15fbaa1c023db3949e8057c5c45ba9984193832e044f 2213 kannel_1.4.5-17.dsc cc32195d1d66cb7c9d91a86e9196dce960c99e0108d2dc0526e11bdc02b8d1c5 24108 kannel_1.4.5-17.debian.tar.xz 199d6be83131289b165b5c30153b4be6be30ebcbce9173028612d2f68bcf51b1 5648 kannel_1.4.5-17_source.buildinfo Files: f89444d2cd7ddc7ba4042d82b323e575 2213 net optional kannel_1.4.5-17.dsc 81d46c47b4ab55a2f6c0af32a6a95bc7 24108 net optional kannel_1.4.5-17.debian.tar.xz 86d85f81285ddcdbe8aae2849aec794c 5648 net optional kannel_1.4.5-17_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmZPgLYQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFBbqC/96jabyuH7GjFRkvwe/P4LFz77UsqRM6iC5 NwYH0qALBP/Gma82yFPuQWs865CWvPzX5JLIJipGjW3TXMBrh9x2BdGtV6/6Pv/2 qPX+gU3tH8aJknEt06vxrzHIWFO2k2KhXGOoZWyoJboq0FMiXNkChGAmU5wBocn1 kC7bBEGhinF/6shA8HsrennBj1ixnXo0zoCoX17ZZELbbp5lhQqsUBj2WKQZex/f iVhnVFlHFS0WeCQCLYX6f7aMXK38HZOeTlWCWvW7eAFzSgNIKAkLAMITCtZDRWdK UCJUOf2s1FXII+yAWTjTXLHXkf4nAWUpIqDfcyk3f8flLGynnkEiSw73RYf+RqqI /hQpK0LbQMF1ML5lA7nWWjfRmvqt8Sq2KpOfMhbY3+Lz5AljfhcRNf0cT43hIPD1 LrBQ3s9RNbQ5mBFfvha3di9ODrPNivR0Yi3Zn/dDhPGBf8VFflDBb6bCd5YG0RyK vudnkTKy6RB4VgMYdhP8kGtG4/Aeuv8= =8Z/c -END PGP SIGNATURE- pgpYi9cqpBMgE.pgp Description: PGP signature --- End Message ---
Bug#1064938: isospec - maintainer does not access email from ftp-master
Hi, given neither debian.org nor ftp-master.debian.org have a DMARC policy, it should be a configuration error on alioth-lists.debian.net. (Arguably mailing lists should not impersonate other domains outside their control and set "From:" to an address controlled by the mailing list operator.) Ansgar On Thu, 2024-05-23 at 20:55 +0300, Adrian Bunk wrote: > Hi Bastian, > > The Debichem Group maintains ~ 140 packages with this maintainer > address > at lists.alioth.debian.org. > > Was this any misconfiguration on the debian.org side, > or is/was this any issue at alioth-lists.debian.net, > or what else might have gone wrong here? > > Thanks > Adrian > > > > On Tue, Feb 27, 2024 at 11:23:14PM +0100, Bastian Blank wrote: > > Package: isospec > > Severity: serious > > > > - Forwarded message from > > debichem-devel-ow...@alioth-lists.debian.net - > > > > From: debichem-devel-ow...@alioth-lists.debian.net > > To: ftpmas...@ftp-master.debian.org > > Subject: Processing of isospec_2.2.1-4.1~exp2_source.changes > > > > You are not allowed to post to this mailing list From: a domain > > which > > publishes a DMARC policy of reject or quarantine, and your message > > has > > been automatically rejected. If you think that your messages are > > being rejected in error, contact the mailing list owner at > > debichem-devel-ow...@alioth-lists.debian.net. > > > > > > Date: Sat, 24 Feb 2024 02:03:38 + > > From: Debian FTP Masters > > To: debichem-de...@lists.alioth.debian.org > > Subject: Processing of isospec_2.2.1-4.1~exp2_source.changes > > > > isospec_2.2.1-4.1~exp2_source.changes uploaded successfully to > > localhost > > along with the files: > > isospec_2.2.1-4.1~exp2.dsc > > isospec_2.2.1-4.1~exp2.debian.tar.xz > > isospec_2.2.1-4.1~exp2_source.buildinfo > > > > Greetings, > > > > Your Debian queue daemon (running on host usper.debian.org) > > > > > > > > - End forwarded message - > > > > -- > > Hailing frequencies open, Captain. >
Bug#1071681: php-ml-iri: depends on obsolete pcre3 library
Package: php-ml-iri Severity: serious Dear maintainer, Your package still depends on the old, obsolete PCRE library (i.e. libpcre3). This has been end of life for a while now, and upstream do not intend to fix any further bugs in it. Accordingly, the pcre3 library is being removed from Debian. 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/ The dependency is auto-generated by dh-sequence-phpcomposer. I do not see it actually being used and the php interpreter has long moved to pcre2. This is an add-on to the mass bug filing that was discussed on debian-devel in https://lists.debian.org/debian-devel/2021/11/msg00176.html
Bug#1064938: isospec - maintainer does not access email from ftp-master
Hi Bastian, The Debichem Group maintains ~ 140 packages with this maintainer address at lists.alioth.debian.org. Was this any misconfiguration on the debian.org side, or is/was this any issue at alioth-lists.debian.net, or what else might have gone wrong here? Thanks Adrian On Tue, Feb 27, 2024 at 11:23:14PM +0100, Bastian Blank wrote: > Package: isospec > Severity: serious > > - Forwarded message from debichem-devel-ow...@alioth-lists.debian.net > - > > From: debichem-devel-ow...@alioth-lists.debian.net > To: ftpmas...@ftp-master.debian.org > Subject: Processing of isospec_2.2.1-4.1~exp2_source.changes > > You are not allowed to post to this mailing list From: a domain which > publishes a DMARC policy of reject or quarantine, and your message has > been automatically rejected. If you think that your messages are > being rejected in error, contact the mailing list owner at > debichem-devel-ow...@alioth-lists.debian.net. > > > Date: Sat, 24 Feb 2024 02:03:38 + > From: Debian FTP Masters > To: debichem-de...@lists.alioth.debian.org > Subject: Processing of isospec_2.2.1-4.1~exp2_source.changes > > isospec_2.2.1-4.1~exp2_source.changes uploaded successfully to localhost > along with the files: > isospec_2.2.1-4.1~exp2.dsc > isospec_2.2.1-4.1~exp2.debian.tar.xz > isospec_2.2.1-4.1~exp2_source.buildinfo > > Greetings, > > Your Debian queue daemon (running on host usper.debian.org) > > > > - End forwarded message - > > -- > Hailing frequencies open, Captain.
Processed: Re: Bug#1059133: dogecoin: FTBFS: error: invalid ‘static_cast’ from type ‘boost::detail::function::function_buffer_members::obj_ptr_t’ {aka ‘void*’} to type ‘void (*)(bool, const CBlockInde
Processing control commands:
> reassign -1 libboost1.83-dev 1.83.0-2.1
Bug #1059133 [src:dogecoin] dogecoin: FTBFS: error: invalid ‘static_cast’ from
type ‘boost::detail::function::function_buffer_members::obj_ptr_t’ {aka
‘void*’} to type ‘void (*)(bool, const CBlockIndex*)’
Bug reassigned from package 'src:dogecoin' to 'libboost1.83-dev'.
No longer marked as found in versions dogecoin/1.14.6-4.
Ignoring request to alter fixed versions of bug #1059133 to the same values
previously set
Bug #1059133 [libboost1.83-dev] dogecoin: FTBFS: error: invalid ‘static_cast’
from type ‘boost::detail::function::function_buffer_members::obj_ptr_t’ {aka
‘void*’} to type ‘void (*)(bool, const CBlockIndex*)’
Marked as found in versions boost1.83/1.83.0-2.1.
> retitle -1 libboost1.83-dev: Please add upstream fix needed for dogecoin
Bug #1059133 [libboost1.83-dev] dogecoin: FTBFS: error: invalid ‘static_cast’
from type ‘boost::detail::function::function_buffer_members::obj_ptr_t’ {aka
‘void*’} to type ‘void (*)(bool, const CBlockIndex*)’
Changed Bug title to 'libboost1.83-dev: Please add upstream fix needed for
dogecoin' from 'dogecoin: FTBFS: error: invalid ‘static_cast’ from type
‘boost::detail::function::function_buffer_members::obj_ptr_t’ {aka ‘void*’} to
type ‘void (*)(bool, const CBlockIndex*)’'.
> affects -1 src:dogecoin
Bug #1059133 [libboost1.83-dev] libboost1.83-dev: Please add upstream fix
needed for dogecoin
Added indication that 1059133 affects src:dogecoin
> tags -1 patch
Bug #1059133 [libboost1.83-dev] libboost1.83-dev: Please add upstream fix
needed for dogecoin
Added tag(s) patch.
> forwarded -1 https://github.com/boostorg/function/pull/47
Bug #1059133 [libboost1.83-dev] libboost1.83-dev: Please add upstream fix
needed for dogecoin
Set Bug forwarded-to-address to 'https://github.com/boostorg/function/pull/47'.
--
1059133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1059133: dogecoin: FTBFS: error: invalid ‘static_cast’ from type ‘boost::detail::function::function_buffer_members::obj_ptr_t’ {aka ‘void*’} to type ‘void (*)(bool, const CBlockIndex*)’
Control: reassign -1 libboost1.83-dev 1.83.0-2.1 Control: retitle -1 libboost1.83-dev: Please add upstream fix needed for dogecoin Control: affects -1 src:dogecoin Control: tags -1 patch Control: forwarded -1 https://github.com/boostorg/function/pull/47 On Tue, Jan 09, 2024 at 06:37:44PM -0500, Chad Jacob Milios wrote: > Please see https://github.com/boostorg/function/pull/47 and let us know if > that minor modification helps you out. Yes, it does. cu Adrian
Processed: [bts-link] source package ukui-screensaver
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package ukui-screensaver > # 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 #1071521 (http://bugs.debian.org/1071521) > # Bug title: ukui-screensaver: predictable filenames under /tmp with system() > # * https://github.com/ukui/kylin-nm/issues/154 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1071521 + fixed-upstream Bug #1071521 [ukui-screensaver] ukui-screensaver: predictable filenames under /tmp with system() Added tag(s) fixed-upstream. > usertags 1071521 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1071521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071679: eclipse-titan: depends on obsolete pcre3 library
Package: eclipse-titan Severity: serious Dear maintainer, Your package still depends on the old, obsolete PCRE library (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, the pcre3 library is being removed from Debian. 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/ The dependency seems to be unused, so it should be fine to drop it. This is an add-on to the mass bug filing that was discussed on debian-devel in https://lists.debian.org/debian-devel/2021/11/msg00176.html
Bug#1071677: cpl-plugin-amber-calib: amber-kit-4.4.3*.tar.gz is no longer downloadable
Package: cpl-plugin-amber-calib Version: 4.4.3+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up cpl-plugin-amber-calib (4.4.3+dfsg-1) ... --2024-05-23 12:17:50-- ftp://ftp.eso.org/pub/dfs/pipelines/amber/amber-kit-4.4.3.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:17:50 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:17:50-- ftp://ftp.eso.org/pub/dfs/pipelines/amber/amber-kit-4.4.3-1.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:17:51 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:17:51-- ftp://ftp.eso.org/pub/dfs/pipelines/amber/amber-kit-4.4.3-2.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:17:51 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:17:51-- ftp://ftp.eso.org/pub/dfs/pipelines/amber/amber-kit-4.4.3-3.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:17:52 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:17:52-- ftp://ftp.eso.org/pub/dfs/pipelines/amber/amber-kit-4.4.3-4.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:17:52 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:17:52-- ftp://ftp.eso.org/pub/dfs/pipelines/amber/amber-kit-4.4.3-5.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:17:53 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:17:53-- ftp://ftp.eso.org/pub/dfs/pipelines/amber/amber-kit-4.4.3-6.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:17:54 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:17:54-- ftp://ftp.eso.org/pub/dfs/pipelines/amber/amber-kit-4.4.3-7.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:17:54 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:17:54-- ftp://ftp.eso.org/pub/dfs/pipelines/amber/amber-kit-4.4.3-8.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:17:55 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:17:55-- ftp://ftp.eso.org/pub/dfs/pipelines/amber/amber-kit-4.4.3-9.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:17:55 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now dpkg: error processing package cpl-plugin-amber-calib (--configure): installed cpl-plugin-amber-calib package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.38-11) ... Errors were encountered while processing: cpl-plugin-amber-calib cheers, Andreas cpl-plugin-amber-calib_4.4.3+dfsg-1.log.gz Description: application/gzip
Processed: affects 1071302
Processing commands for cont...@bugs.debian.org: > affects 1071302 src:telegram-desktop Bug #1071302 [src:cppgir] cppgir: FTBFS: Segmentation fault while "Generating wrapper code for: GObject-2.0;Gio-2.0;Gst-1.0;Gtk-3.0" Added indication that 1071302 affects src:telegram-desktop > thanks Stopping processing here. Please contact me if you need assistance. -- 1071302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071302 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071678: cpl-plugin-fors-calib: fors-kit-5.5.7*.tar.gz is no longer downloadable
Package: cpl-plugin-fors-calib Version: 5.5.7+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up cpl-plugin-fors-calib (5.5.7+dfsg-2) ... --2024-05-23 12:19:11-- ftp://ftp.eso.org/pub/dfs/pipelines/fors/fors-kit-5.5.7.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:19:12 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:19:12-- ftp://ftp.eso.org/pub/dfs/pipelines/fors/fors-kit-5.5.7-1.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:19:13 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:19:13-- ftp://ftp.eso.org/pub/dfs/pipelines/fors/fors-kit-5.5.7-2.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:19:13 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:19:13-- ftp://ftp.eso.org/pub/dfs/pipelines/fors/fors-kit-5.5.7-3.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:19:14 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:19:14-- ftp://ftp.eso.org/pub/dfs/pipelines/fors/fors-kit-5.5.7-4.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:19:14 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:19:14-- ftp://ftp.eso.org/pub/dfs/pipelines/fors/fors-kit-5.5.7-5.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:19:15 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:19:15-- ftp://ftp.eso.org/pub/dfs/pipelines/fors/fors-kit-5.5.7-6.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:19:15 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:19:15-- ftp://ftp.eso.org/pub/dfs/pipelines/fors/fors-kit-5.5.7-7.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:19:16 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:19:16-- ftp://ftp.eso.org/pub/dfs/pipelines/fors/fors-kit-5.5.7-8.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:19:17 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2024-05-23 12:19:17-- ftp://ftp.eso.org/pub/dfs/pipelines/fors/fors-kit-5.5.7-9.tar.gz Connecting to 10.99.36.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2024-05-23 12:19:17 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now dpkg: error processing package cpl-plugin-fors-calib (--configure): installed cpl-plugin-fors-calib package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.38-11) ... Errors were encountered while processing: cpl-plugin-fors-calib cheers, Andreas cpl-plugin-fors-calib_5.5.7+dfsg-2.log.gz Description: application/gzip
Bug#1053004: CVE-2019-10784 and CVE-2023-40619
On Wed, May 22, 2024 at 3:00 PM Moritz Muehlenhoff wrote: > > On Wed, May 22, 2024 at 02:42:58PM -0300, Leandro Cunha wrote: > > Hi everyone, > > > > On Wed, May 22, 2024 at 12:39 PM Moritz Mühlenhoff wrote: > > > > > > Am Wed, Mar 06, 2024 at 06:39:01AM -0300 schrieb Leandro Cunha: > > > > Hi Christoph Berg, > > > > > > > > On Wed, Mar 6, 2024 at 5:42 AM Christoph Berg wrote: > > > > > > > > > > Re: Leandro Cunha > > > > > > The > > > > > > next job would be to make it available through backports and I would > > > > > > choose to remove this package from stable. But I would only leave > > > > > > bookworm backports due to other bugs found (this CVEs too) and fixed > > > > > > in 7.14.7. > > > > > > I have to search about the status of backports to oldstable. But I'm > > > > > > also studying the possibility of working with patches for these two > > > > > > versions. > > > > > > > > > > Why would you want to remove it from stable? In closed environments, > > > > > CVEs are often not a problem. > > > > > > > > > > Christoph > > > > > > > > In addition to the CVEs, phppgadmin which is present in stable does > > > > not connect to PostgreSQL 15 and 16 without a patch I inserted in > > > > 7.13.0+dfsg-3, but I can add the same patch by reopening bug #1029516 > > > > or opening another important bug (I am aware that the bug must have a > > > > severity greater than important)[3] for the stable and submission of > > > > new bug to the release team for approval. That way it would be > > > > released in a future release a version with this issue fixed (if > > > > approved). But CVE-2023-40619 is treated with critical severity and > > > > CVE-2019-10784 is also critical according to the NVD[1][2]. The Debian > > > > LTS team handled this with DLA-3644-1 (CVE-2023-40619)[4] in buster > > > > (oldoldstable) and of OpenSUSE team also handled both CVEs in > > > > Leap[5][6]. > > > > Removing this package in stable will not leave users without them and > > > > we can release it in backports. > > > > I can treat this as a job of ensuring the quality of what is > > > > distributed by Debian. > > > > > > Agreed, if the package is actually broken with the version of PostgreSQL > > > in stable and if there's no sensible backport for the open security > > > issues, > > > then let's rather remove it by the next point release. > > > > > > Cheers, > > > Moritz > > > > It's the best thing to do, the package with the necessary corrections > > is already present in bookworm-backports and the user just needs to > > run apt install -t bookworm-backports phppgadmin[1][2][3] with > > sponsorship of Christoph Berg (thank you for that) and thanks also to > > the Debian Security Team. > > Ack, will you do the removal request? You can do that with > "reportbug release.debian.org" and then selecting the > "rm stable/testing removal requests" option. > > Cheers, > Moritz Already in draft. Once it's ready, I'll send it to BTS and using the template of the reportbug. I'll get some DD to review it before sending it too tonight on a video call. https://wiki.debian.org/reportbug -- Cheers, Leandro Cunha
Bug#1066822: linuxtv-dvb-apps: diff for NMU version 1.1.1+rev1500-1.5
Control: tags 961967 + patch
Control: tags 961967 + pending
Control: tags 1066822 + patch
Control: tags 1066822 + pending
Dear maintainer,
I've prepared an NMU for linuxtv-dvb-apps (versioned as
1.1.1+rev1500-1.5) and uploaded it to DELAYED/5. Please feel free to
tell me if I should delay it longer.
I would have sent these as git merge requests of some form, but
Vcs-Git/Vcs-Browser are still set to the obsolete anonscm.debian.org and
I couldn't find any corresponding repositories on salsa, so this was the
best I could do; you should be able to find more detailed history via
"dgit clone linuxtv-dvb-apps" if you need it.
Regards,
--
Colin Watson (he/him) [cjwat...@debian.org]
diff -Nru linuxtv-dvb-apps-1.1.1+rev1500/debian/changelog linuxtv-dvb-apps-1.1.1+rev1500/debian/changelog
--- linuxtv-dvb-apps-1.1.1+rev1500/debian/changelog 2020-07-26 19:42:38.0 +0100
+++ linuxtv-dvb-apps-1.1.1+rev1500/debian/changelog 2024-05-23 16:49:59.0 +0100
@@ -1,3 +1,11 @@
+linuxtv-dvb-apps (1.1.1+rev1500-1.5) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Work around UAPI break in Linux input events (Closes: #1066822).
+ * Set Architecture to linux-any (Closes: #961967).
+
+ -- Colin Watson Thu, 23 May 2024 16:49:59 +0100
+
linuxtv-dvb-apps (1.1.1+rev1500-1.4) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru linuxtv-dvb-apps-1.1.1+rev1500/debian/control linuxtv-dvb-apps-1.1.1+rev1500/debian/control
--- linuxtv-dvb-apps-1.1.1+rev1500/debian/control 2016-04-07 17:11:50.0 +0100
+++ linuxtv-dvb-apps-1.1.1+rev1500/debian/control 2024-05-23 16:49:59.0 +0100
@@ -11,7 +11,7 @@
Homepage: http://www.linuxtv.org/wiki/index.php/LinuxTV_dvb-apps
Package: dvb-apps
-Architecture: any
+Architecture: linux-any
Depends:
${shlibs:Depends},
makedev | udev,
diff -Nru linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/series linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/series
--- linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/series 2020-07-26 19:38:59.0 +0100
+++ linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/series 2024-05-23 16:49:59.0 +0100
@@ -11,3 +11,4 @@
dst_test-no-set-id.patch
glibc-stime.patch
gcc-10-sid-redefinition.patch
+work-around-uapi-break-in-linux-input-ev.patch
diff -Nru linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/work-around-uapi-break-in-linux-input-ev.patch linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/work-around-uapi-break-in-linux-input-ev.patch
--- linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/work-around-uapi-break-in-linux-input-ev.patch 1970-01-01 01:00:00.0 +0100
+++ linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/work-around-uapi-break-in-linux-input-ev.patch 2024-05-23 16:49:59.0 +0100
@@ -0,0 +1,25 @@
+From: Colin Watson
+Date: Thu, 23 May 2024 16:38:37 +0100
+X-Dgit-Generated: 1.1.1+rev1500-1.5 5d2fca4cdce8ddcdf7e13a0681da7b381301
+Subject: Work around UAPI break in Linux input events
+
+See
+https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=152194fe9c3f.
+
+Closes: #1066822
+
+---
+
+diff --git a/test/evtest.c b/test/evtest.c
+index a61593e..73fb5af 100644
+--- a/test/evtest.c
b/test/evtest.c
+@@ -241,7 +241,7 @@ int main (int argc, char **argv)
+
+ for (i = 0; i < rd / (int) sizeof(struct input_event); i++)
+ printf("Event: time %ld.%06ld, type %d (%s), code %d (%s), value %d\n",
+-ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].type,
++ev[i].input_event_sec, ev[i].input_event_usec, ev[i].type,
+ events[ev[i].type] ? events[ev[i].type] : "?",
+ ev[i].code,
+ names[ev[i].type] ? (names[ev[i].type][ev[i].code] ? names[ev[i].type][ev[i].code] : "?") : "?",
Processed: linuxtv-dvb-apps: diff for NMU version 1.1.1+rev1500-1.5
Processing control commands:
> tags 961967 + patch
Bug #961967 [src:linuxtv-dvb-apps] linuxtv-dvb-apps: Please change to
Architecture: linux-any
Ignoring request to alter tags of bug #961967 to the same tags previously set
> tags 961967 + pending
Bug #961967 [src:linuxtv-dvb-apps] linuxtv-dvb-apps: Please change to
Architecture: linux-any
Ignoring request to alter tags of bug #961967 to the same tags previously set
> tags 1066822 + patch
Bug #1066822 [src:linuxtv-dvb-apps] linuxtv-dvb-apps: FTBFS on arm{el,hf}:
evtest.c:244:38: error: ‘struct input_event’ has no member named ‘time’
Ignoring request to alter tags of bug #1066822 to the same tags previously set
> tags 1066822 + pending
Bug #1066822 [src:linuxtv-dvb-apps] linuxtv-dvb-apps: FTBFS on arm{el,hf}:
evtest.c:244:38: error: ‘struct input_event’ has no member named ‘time’
Ignoring request to alter tags of bug #1066822 to the same tags previously set
--
1066822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066822
961967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: linuxtv-dvb-apps: diff for NMU version 1.1.1+rev1500-1.5
Processing control commands:
> tags 961967 + patch
Bug #961967 [src:linuxtv-dvb-apps] linuxtv-dvb-apps: Please change to
Architecture: linux-any
Added tag(s) patch.
> tags 961967 + pending
Bug #961967 [src:linuxtv-dvb-apps] linuxtv-dvb-apps: Please change to
Architecture: linux-any
Added tag(s) pending.
> tags 1066822 + patch
Bug #1066822 [src:linuxtv-dvb-apps] linuxtv-dvb-apps: FTBFS on arm{el,hf}:
evtest.c:244:38: error: ‘struct input_event’ has no member named ‘time’
Added tag(s) patch.
> tags 1066822 + pending
Bug #1066822 [src:linuxtv-dvb-apps] linuxtv-dvb-apps: FTBFS on arm{el,hf}:
evtest.c:244:38: error: ‘struct input_event’ has no member named ‘time’
Added tag(s) pending.
--
1066822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066822
961967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1069477: marked as done (octave-stk: FTBFS on armhf: make: *** [debian/rules:5: binary] Error 134)
Your message dated Thu, 23 May 2024 15:06:49 + with message-id and subject line Bug#1069477: fixed in octave-stk 2.8.1-2 has caused the Debian Bug report #1069477, regarding octave-stk: FTBFS on armhf: make: *** [debian/rules:5: binary] Error 134 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.) -- 1069477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: octave-stk Version: 2.8.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf Hi, During a rebuild of all packages in sid, your package failed to build on armhf. Relevant part (hopefully): > make[1]: Entering directory '/<>/src' > /usr/bin/mkoctfile --verbose --mex --output __stk_dist_pairwise__.mex > stk_dist_pairwise.c > /usr/bin/mkoctfile --verbose --mex --output __get_column_number__.mex > get_column_number.c > /usr/bin/mkoctfile --verbose --mex --output __stk_dist_matrixy__.mex > stk_dist_matrixy.c > /usr/bin/mkoctfile --verbose --mex --output __stk_filldist_discr_mex__.mex > stk_filldist_discr_mex.c > gcc -c -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time > -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/octave-8.4.0/octave/.. > -I/usr/include/octave-8.4.0/octave -pthread -fopenmp -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -I. -DMEX_DEBUG stk_dist_pairwise.c -o > /tmp/oct-UF3qW1.o > gcc -c -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time > -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/octave-8.4.0/octave/.. > -I/usr/include/octave-8.4.0/octave -pthread -fopenmp -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -I. -DMEX_DEBUG get_column_number.c -o > /tmp/oct-G2cJZa.o > gcc -c -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time > -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/octave-8.4.0/octave/.. > -I/usr/include/octave-8.4.0/octave -pthread -fopenmp -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -I. -DMEX_DEBUG stk_dist_matrixy.c -o > /tmp/oct-EqvG1R.o > gcc -c -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time > -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/octave-8.4.0/octave/.. > -I/usr/include/octave-8.4.0/octave -pthread -fopenmp -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -I. -DMEX_DEBUG stk_filldist_discr_mex.c -o > /tmp/oct-uUnPP3.o > g++ -I/usr/include/octave-8.4.0/octave/.. -I/usr/include/octave-8.4.0/octave > -pthread -fopenmp -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -o __stk_dist_pairwise__.mex /tmp/oct-UF3qW1.o > -shared -Wl,-Bsymbolic -Wl,-z,relro -L/usr/lib/arm-linux-gnueabihf -shared > -Wl,-Bsymbolic -flto=auto -ffat-lto-objects -Wl,-z,relro > g++ -I/usr/include/octave-8.4.0/octave/.. -I/usr/include/octave-8.4.0/octave > -pthread -fopenmp -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -o __stk_dist_matrixy__.mex /tmp/oct-EqvG1R.o > -shared -Wl,-Bsymbolic -Wl,-z,relro -L/usr/lib/arm-linux-gnueabihf -shared > -Wl,-Bsymbolic -flto=auto -ffat-lto-objects -Wl,-z,relro > g++ -I/usr/include/octave-8.4.0/octave/.. -I/usr/include/octave-8.4.0/octave > -pthread -fopenmp -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -o __stk_filldist_discr_mex__.mex /tmp/oct-uUnPP3.o > -shared -Wl,-Bsymbolic -Wl,-z,relro -L/usr/lib/arm-linux-gnueabihf -shared > -Wl,-Bsymbolic -flto=auto -ffat-lto-objects -Wl,-z,relro > g++ -I/usr/include/octave-8.4.0/octave/.. -I/usr/include/octave-8.4.0/octave > -pthread -fopenmp -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -o __get_column_number__.mex /tmp/oct-G2cJZa.o > -shared -Wl,-Bsymbolic -Wl,-z,relro -L/usr/lib/arm-linux-gnueabihf -shared > -Wl,-Bsymbolic -flto=auto -ffat-lto-objects -Wl,-z,relro > /usr/bin/mkoctfile --verbose --mex --output
Processed: Bug#1069477 marked as pending in octave-stk
Processing control commands: > tag -1 pending Bug #1069477 [src:octave-stk] octave-stk: FTBFS on armhf: make: *** [debian/rules:5: binary] Error 134 Added tag(s) pending. -- 1069477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069477: marked as pending in octave-stk
Control: tag -1 pending Hello, Bug #1069477 in octave-stk 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/pkg-octave-team/octave-stk/-/commit/a9bd03a4eda9ba5b900d39e8ce29f9417804b2f0 d/rules: Add -fexceptions to CFLAGS Closes: #1069477 (this message was generated automatically) -- Greetings https://bugs.debian.org/1069477
Bug#1071017: marked as done (FTBFS: source-copy.cpp:615:31: error: ‘void obs_sceneitem_get_info(const obs_sceneitem_t*, obs_transform_info*)’ is deprecated [-Werror=deprecated-declarations])
Your message dated Thu, 23 May 2024 14:37:09 + with message-id and subject line Bug#1071017: fixed in obs-source-copy 0.2.2-8 has caused the Debian Bug report #1071017, regarding FTBFS: source-copy.cpp:615:31: error: ‘void obs_sceneitem_get_info(const obs_sceneitem_t*, obs_transform_info*)’ is deprecated [-Werror=deprecated-declarations] 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.) -- 1071017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: obs-source-copy Version: 0.2.2-5 Severity: serious Tags: upstream Justification: FTBFS When rebuilding the source code, we got: /usr/bin/c++ -DHAVE_OBSCONFIG_H -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_WIDGETS_LIB -Dsource_copy_EXPORTS -I/PKGS/obs-source-copy/1/obs-source-copy-0.2.2/obj-x86_64-linux-gnu/source-copy_autogen/include -isystem /usr/include/obs -isystem /usr/include/x86_64-linux-gnu/qt6/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt6 -isystem /usr/include/x86_64-linux-gnu/qt6/QtCore -isystem /usr/lib/x86_64-linux-gnu/qt6/mkspecs/linux-g++ -isystem /usr/include/x86_64-linux-gnu/qt6/QtGui -g -O2 -ffile-prefix-map=/PKGS/obs-source-copy/1/obs-source-copy-0.2.2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Werror -Wextra -Wvla -Wformat -Wformat-security -Wswitch -Wunused-parameter -Wno-unused-function -Wno-missing-field-initializers -fno-strict-aliasing -Wconversion-null -fPIC -mmmx -msse -msse2 -MD -MT CMakeFiles/source-copy.dir/source-copy.cpp.o -MF CMakeFiles/source-copy.dir/source-copy.cpp.o.d -o CMakeFiles/source-copy.dir/source-copy.cpp.o -c /PKGS/obs-source-copy/1/obs-source-copy-0.2.2/source-copy.cpp /PKGS/obs-source-copy/1/obs-source-copy-0.2.2/source-copy.cpp: In function ‘obs_data_t* GetTransformData(obs_sceneitem_t*)’: /PKGS/obs-source-copy/1/obs-source-copy-0.2.2/source-copy.cpp:595:31: error: ‘void obs_sceneitem_get_info(const obs_sceneitem_t*, obs_transform_info*)’ is deprecated [-Werror=deprecated-declarations] 595 | obs_sceneitem_get_info(item, ); | ~~^ In file included from /PKGS/obs-source-copy/1/obs-source-copy-0.2.2/source-copy.hpp:3, from /PKGS/obs-source-copy/1/obs-source-copy-0.2.2/source-copy.cpp:1: /usr/include/obs/obs.h:1889:1: note: declared here 1889 | obs_sceneitem_get_info(const obs_sceneitem_t *item, | ^~ /PKGS/obs-source-copy/1/obs-source-copy-0.2.2/source-copy.cpp: In function ‘void LoadTransform(obs_sceneitem_t*, obs_data_t*)’: /PKGS/obs-source-copy/1/obs-source-copy-0.2.2/source-copy.cpp:615:31: error: ‘void obs_sceneitem_get_info(const obs_sceneitem_t*, obs_transform_info*)’ is deprecated [-Werror=deprecated-declarations] 615 | obs_sceneitem_get_info(item, ); | ~~^ /usr/include/obs/obs.h:1889:1: note: declared here 1889 | obs_sceneitem_get_info(const obs_sceneitem_t *item, | ^~ /PKGS/obs-source-copy/1/obs-source-copy-0.2.2/source-copy.cpp:624:31: error: ‘void obs_sceneitem_set_info(obs_sceneitem_t*, const obs_transform_info*)’ is deprecated [-Werror=deprecated-declarations] 624 | obs_sceneitem_set_info(item, ); | ~~^ /usr/include/obs/obs.h:1892:1: note: declared here 1892 | obs_sceneitem_set_info(obs_sceneitem_t *item, | ^~ cc1plus: all warnings being treated as errors make[3]: *** [CMakeFiles/source-copy.dir/build.make:100: CMakeFiles/source-copy.dir/source-copy.cpp.o] Error 1 make[3]: Leaving directory '/PKGS/obs-source-copy/1/obs-source-copy-0.2.2/obj-x86_64-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:89: CMakeFiles/source-copy.dir/all] Error 2 make[2]: Leaving directory '/PKGS/obs-source-copy/1/obs-source-copy-0.2.2/obj-x86_64-linux-gnu' make[1]: *** [Makefile:159: all] Error 2 make[1]: Leaving directory '/PKGS/obs-source-copy/1/obs-source-copy-0.2.2/obj-x86_64-linux-gnu' dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j16 "INSTALL=install --strip-program=true" VERBOSE=1 returned exit code 2 make: *** [debian/rules:14: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 debuild: fatal error at line 1184: dpkg-buildpackage -us -uc -ui failed Eriberto --- End Message --- --- Begin Message --- Source: obs-source-copy Source-Version: 0.2.2-8 Done: Joao Eriberto Mota Filho We
Bug#1062645: libsysstat: NMU diff for 64-bit time_t transition
Hi Steve,
We has fixed lxqt-panel uninstallable issue [0] and now libsysstat is
ready for 64-bit time_t transition. Do we need to do anything to make it
happens?
[0] https://bugs.debian.org/1071145, https://bugs.debian.org/1071146
--
ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
Key fingerprint = BA04 346D C2E1 FE63 C790 8793 CC65 B0CD EC27 5D5B
signature.asc
Description: PGP signature
Processed: reopening 1028634
Processing commands for cont...@bugs.debian.org:
> reopen 1028634
Bug #1028634 {Done: Sergio Durigan Junior }
[libbtas-dev] libbtas-dev requires blaspp
Bug reopened
Ignoring request to alter fixed versions of bug #1028634 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1028634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1028634: closed by Sergio Durigan Junior (Re: Bug#1028634: tiledarray: FTBFS: Could not find a package configuration file provided by "blaspp")
On Wed, Jan 24, 2024 at 08:09:03PM +, Debian Bug Tracking System wrote: >... > Date: Wed, 24 Jan 2024 14:59:30 -0500 > From: Sergio Durigan Junior > To: 1028634-cl...@bugs.debian.org > Subject: Re: Bug#1028634: tiledarray: FTBFS: Could not find a package > configuration file provided by "blaspp" > > On Tuesday, January 24 2023, Adrian Bunk wrote: > > > On Fri, Jan 13, 2023 at 11:59:48PM +0100, Sebastian Ramacher wrote: > >> Source: tiledarray > >> Version: 1.0.0-1 > >> Severity: serious > >> Tags: ftbfs > >>... > >> blasppConfig.cmake > >> blaspp-config.cmake > >> > >> Add the installation prefix of "blaspp" to CMAKE_PREFIX_PATH or set > >> "blaspp_DIR" to a directory containing one of the above files. If > >> "blaspp" > >> provides a separate development package or SDK, be sure it has been > >> installed. > >> Call Stack (most recent call first): > >> /usr/lib/cmake/BTAS/btas-config.cmake:104 (find_dependency) > >> cmake/modules/FindOrFetchBTAS.cmake:1 (find_package) > >> CMakeLists.txt:279 (include) > > > > This looks like a problem in libbtas-dev (unpackaged dependency blaspp?). > > The package is building correctly now. Closing the bug. >... It does still FTBFS: https://buildd.debian.org/status/logs.php?pkg=tiledarray=1.0.0-1 cu Adrian
Processed: unarchiving 1028634
Processing commands for cont...@bugs.debian.org:
> unarchive 1028634
Bug #1028634 {Done: Sergio Durigan Junior }
[libbtas-dev] libbtas-dev requires blaspp
Unarchived Bug 1028634
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1028634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#999646: How can I help move this forward?
Hello, This seems to have a fix and a patch and How does one get it incorporated into bookworm? Thanks.
Bug#1071664: opencollada: Includes non-free ConvertUTF.c
Source: opencollada Severity: serious Externals/UTF/src/ConvertUTF.c includes material under a non-free license from Unicode Inc. Therefore, it is not possible to ship this in main or contrib. This license does not grant any permission to modify the files (thus failing DFSG#3). Moreover, the license grant seems to attempt to restrict use to "products supporting the Unicode Standard" (thus failing DFSG#6). Please refer to Bug#823100 for details.
Bug#1071544: marked as done (tla: FTBFS on arm64/ppc64el/riscv64: config.guess: unable to guess system type)
Your message dated Thu, 23 May 2024 12:09:24 + with message-id and subject line Bug#1071544: fixed in tla 1.3.5+dfsg2-1 has caused the Debian Bug report #1071544, regarding tla: FTBFS on arm64/ppc64el/riscv64: config.guess: unable to guess system type 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.) -- 1071544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071544 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tla Version: 1.3.5+dfsg1-4 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, The tla packages fails to build on a few "recent" architectures due to outdated config.guess/sub: | cd debian/build && \ | CFLAGS='-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wall' CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2' LDFLAGS='-Wl,-z,relro' \ | AUTOCONF_CROSS='--build aarch64-linux-gnu' AUTOCONF_CFLAGS='-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wall' \ | AUTOCONF_CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2' AUTOCONF_LDFLAGS='-Wl,-z,relro' \ | ../../src/configure --prefix=/usr --with cc gcc | /<>/src/build-tools/gnu/config.guess: unable to guess system type | | This script, last modified 2006-06-06, has failed to recognize | the operating system you are using. It is advised that you | download the most up to date version of the config scripts from | | http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/config.guess | and | http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/config.sub | | If the version you run (/<>/src/build-tools/gnu/config.guess) is already up to date, please | send the following data and any information you think might be | pertinent to in order to provide the needed | information to handle your system. | | config.guess timestamp = 2006-06-06 | | uname -m = aarch64 | uname -r = 6.1.0-21-arm64 | uname -s = Linux | uname -v = #1 SMP Debian 6.1.90-1 (2024-05-03) | | /usr/bin/uname -p = unknown | /bin/uname -X = | | hostinfo = | /bin/universe = | /usr/bin/arch -k = | /bin/arch = aarch64 | /usr/bin/oslevel = | /usr/convex/getsysinfo = | | UNAME_MACHINE = aarch64 | UNAME_RELEASE = 6.1.0-21-arm64 | UNAME_SYSTEM = Linux | UNAME_VERSION = #1 SMP Debian 6.1.90-1 (2024-05-03) | make: *** [debian/rules:26: configure-stamp] Error 1 | dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 The full build logs are available here: https://buildd.debian.org/status/fetch.php?pkg=tla=arm64=1.3.5%2Bdfsg1-4=1715943782=0 https://buildd.debian.org/status/fetch.php?pkg=tla=ppc64el=1.3.5%2Bdfsg1-4=1715943032=0 https://buildd.debian.org/status/fetch.php?pkg=tla=riscv64=1.3.5%2Bdfsg1-4=1715953860=0 It appears that code for updating config.guess/sub from autotools-dev has been dropped, while it is still necessary. Regards Aurelien [1] https://salsa.debian.org/debian/tla/-/commit/6cea8b94c34768268a7a03538d11e1ecc508eb46 --- End Message --- --- Begin Message --- Source: tla Source-Version: 1.3.5+dfsg2-1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of tla, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated tla 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, 23 May 2024 13:36:38 +0200 Source: tla Architecture: source Version: 1.3.5+dfsg2-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Bastian Germann Closes: 1071544 Changes: tla (1.3.5+dfsg2-1) unstable; urgency=medium . * QA upload. * Repack via Files-Excluded. . [ Bo YU ] * Use dh_update_autotools_config/dh_autoreconf_clean to update config correctly. (Closes:
Bug#1000074: gsmartcontrol: depends on obsolete pcre3 library
It looks like upstream has remove the pcre dependency entirely in their main development branch, but this change isn’t yet part of a stable release. https://github.com/ashaduri/gsmartcontrol/issues/40[1] -- Soren Stoutner so...@debian.org [1] https://github.com/ashaduri/gsmartcontrol/issues/40 signature.asc Description: This is a digitally signed message part.
Bug#1022311: python-stdnum: FTBFS: AssertionError: Failed doctest test for test_no_fodselsnummer.doctest
I wrote: But what would be the proper fix in bullseye? Nevermind. Arthur already answered to that here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022311#15 Arthur: Would be ok for you if I fix this in bullseye via team upload? Thanks.
Bug#1022311: marked as done (python-stdnum: FTBFS: AssertionError: Failed doctest test for test_no_fodselsnummer.doctest)
Your message dated Thu, 23 May 2024 13:32:55 +0200
with message-id
and subject line Re: Bug#1022311: python-stdnum: FTBFS: AssertionError: Failed
doctest test for test_no_fodselsnummer.doctest
has caused the Debian Bug report #1022311,
regarding python-stdnum: FTBFS: AssertionError: Failed doctest test for
test_no_fodselsnummer.doctest
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.)
--
1022311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-stdnum
Version: 1.17-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --system=custom --test-args='TZ=Europe/Amsterdam
> {interpreter} setup.py nosetests'
> I: pybuild base:240: TZ=Europe/Amsterdam python3.10 setup.py nosetests
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508:
> SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use
> license_files instead.
> warnings.warn(msg, warning_class)
> running nosetests
> running egg_info
> writing python_stdnum.egg-info/PKG-INFO
> writing dependency_links to python_stdnum.egg-info/dependency_links.txt
> writing requirements to python_stdnum.egg-info/requires.txt
> writing top-level names to python_stdnum.egg-info/top_level.txt
> reading manifest file 'python_stdnum.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'COPYING'
> writing manifest file 'python_stdnum.egg-info/SOURCES.txt'
> nose.plugins.cover: ERROR: Coverage not available: unable to import coverage
> module
> .SSS.S.SS...SS...F
> ==
> FAIL: Doctest: test_no_fodselsnummer.doctest
> --
> Traceback (most recent call last):
> File "/usr/lib/python3.10/doctest.py", line 2221, in runTest
> raise self.failureException(self.format_failure(new.getvalue()))
> AssertionError: Failed doctest test for test_no_fodselsnummer.doctest
> File "/<>/tests/test_no_fodselsnummer.doctest", line 0
>
> --
> File "/<>/tests/test_no_fodselsnummer.doctest", line 94, in
> test_no_fodselsnummer.doctest
> Failed example:
> fodselsnummer.validate('19102270846')
> Expected:
> Traceback (most recent call last):
> ...
> InvalidComponent: The birth date information is valid, but this person
> has not been born yet.
> Got:
> '19102270846'
>
>
> --
> Ran 342 tests in 1.408s
>
> FAILED (SKIP=8, failures=1)
> E: pybuild pybuild:379: test: plugin custom failed with: exit code=1:
> TZ=Europe/Amsterdam python3.10 setup.py nosetests
> dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.10
> --system=custom "--test-args=TZ=Europe/Amsterdam {interpreter} setup.py
> nosetests" returned exit code 13
The full build log is available from:
http://qa-logs.debian.net/2022/10/23/python-stdnum_1.17-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=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 marking 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 ---
El 23/5/24 a las 12:39, Petter Reinholdtsen escribió:
Is there still any reason to keep this RC BTS report open?
It's not actually RC for trixie because version tracking says trixie is not
affected.
Bug#1022311: python-stdnum: FTBFS: AssertionError: Failed doctest test for test_no_fodselsnummer.doctest
El 23/5/24 a las 12:39, Petter Reinholdtsen escribió: Is there still any reason to keep this RC BTS report open? It's not actually RC for trixie because version tracking says trixie is not affected. However, I'm closing the bug so that people who insist on following version tracking strictly do not complain about it being still open. In theory, bullseye is still oldstable and it's still a supported distribution. If I were the maintainer, I would try to fix this in bullseye, for posterity. In fact, I am a member of python team, so in theory I could fix this myself (via team upload). But what would be the proper fix in bullseye? Thanks.
Bug#1069557: libkdumpfile: FTBFS on armel: dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 returned exit code 2
On Wed, 22 May 2024 14:46:12 +0200 Petr =?UTF-8?B?VGVzYcWZw61r?= wrote: > On Wed, 1 May 2024 11:59:13 -0500 Michel Lind wrote: > > Hi Lucas, > > > > On 4/20/24 8:23 AM, Lucas Nussbaum wrote: > > > Source: libkdumpfile > > > Version: 0.5.4-1 > > > Severity: serious > > > Justification: FTBFS > > > Tags: trixie sid ftbfs > > > User: lu...@debian.org > > > Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel > > > > > > Hi, > > > > > > During a rebuild of all packages in sid, your package failed to build > > > on armel. > > Thanks for filing. I've notified upstream: > > https://github.com/ptesarik/libkdumpfile/issues/80 > > > > and will try and reproduce and fix this. > > FYI I am able to reproduce the failure, and it seems to be related to > some sort of link-time remapping of mmap() to mmap64(). I don't have > time to look into the details, but to prvent removal of the package > from Debian testing, you can add CFLAGS=-D_FILE_OFFSET_BITS=64 as > parameter to ./configure. This fixed it by pure luck for me. Correct fix is here: https://github.com/ptesarik/libkdumpfile/commit/16c73b83a78c1bfb55f3e9823b09fce549c8ec11 I'm sorry for the noise. Petr T
Bug#1063754: fat-modules: SD corruption upon opening file on Linux desktop
I apologize, I misinterpreted "report back here" but I did not look at the distribution list or grab "reply all". I prepared to follow the suggestions, although I was not going to risk that particular microSD unless it was clearly needed. As I prepared to dd to new a new SD, I realized that asking a desktop computer to copy many files was already taking us out the reasonable possibility of replicating the error, because that required (1) an external filesystem (2) thumbnails on and (3) letting Linux copy the files while the thumbnails are being updated. As I was writing the bug report, I tried turning thumbnails off and noted that was a workaround. As far as the bug itself, it looks like a race condition or maybe a buffer collision. One can literally watch the corruption in action. It is likely to succeed if there are only a few files to copy. In order to validate the SD's size, I used dd to copy the raw image to /dev/null, reporting: 331914983424 bytes (32 GB, 30 GiB) copied, 815 s, 39.1 MB/s.This and the other SD I bought with it are on a well-known brand and I have used them extensively. I delete the offending files, rescan, give it to Windows or Linux without thumbnails on, and the files are intact. I can insert the SD into the laptop's slot and the same problem occurs. If I move the files (in a folder) through the network, or any manner other than on the SD's FAT32 filesystem, all is well. As I wrote, the compressed raw image (starting on a new microSD) was still almost 500MB and I was unable to upload it. On Wed, May 15, 2024 at 4:18 PM Ben Hutchings wrote: > Control: tag -1 moreinfo > > On Mon, 12 Feb 2024 03:47:14 -0500 Bud Heal > wrote: > [...] > > I scanned a few pages, then plugged into the USB cable, at which > point > > the wand shows "USB" and Bullseye mounts the SD as a USB disk. The > first > > time on Bullseye, it worked okay. The second and afterwards, not so > > okay. > > > > The key before Bullseye was the thumbnails would show all black, > usually > > at the bottom of a folder. The images before the all black ones, > usually > > were apparently unaffected. By memory, there were screwy problems but > > nothing like now. > > > > Under Bullseye, just inserting or mounting the SD leads to > corruption. > > The files are are "readable" but not as proper images. When I insert > the > > SD into a Windows (10) laptop, it asks to check the filesystem and > will > > toss the unreadable images and leave the ones that are all black. > [...] > > If I experienced these problems, I would assume that my SD card was > faulty (or even a counterfeit that has less storage than it claims to). > > Since the card appeared to work under Windows, please could you test it > more thoroughly under Windows: > > 1. Copy files onto the card to fill it up. > 2. Remove and reinsert the card. > 3. Compare the files on the card with the files you copied from. > > and report back here. > > Ben. > > -- > Ben Hutchings > Anthony's Law of Force: Don't force it, get a larger hammer. > >
Bug#1022311: python-stdnum: FTBFS: AssertionError: Failed doctest test for test_no_fodselsnummer.doctest
Is there still any reason to keep this RC BTS report open? -- Happy hacking Petter Reinholdtsen
Bug#1060477: marked as done (udftools: Please switch Build-Depends to systemd-dev)
Your message dated Thu, 23 May 2024 10:07:59 + with message-id and subject line Bug#1060477: fixed in udftools 2.3-2 has caused the Debian Bug report #1060477, regarding udftools: Please switch Build-Depends to systemd-dev 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.) -- 1060477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: udftools Version: 2.3-1 Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: systemd-dev Hi, your package udftools declares a Build-Depends on systemd and/or udev. In most cases, this build dependency is added to get the paths that are defined in udev.pc or systemd.pc (via pkgconfig). Since systemd_253-2 [1], these two pkgconfig files have been split into a separate package named systemd-dev. This package is arch:all, so even available on non-Linux architectures, which will simplify the installation of upstream provided service files / udev rules. To not make existing source packages FTBFS, the systemd and udev package have a Depends: systemd-dev. This dependency will be removed at some point though before trixie is released. Once this happens, this issue will be bumped to RC. Please update your build dependencies accordingly at your earliest convenience. If all you need is the systemd.pc or udev.pc pkgconfig file, please replace any systemd or udev Build-Depends with systemd-dev. In most cases that should be sufficient. If your package needs further resources from systemd or udev to build successfully, it's fine to keep those Build-Depends in addition to systemd-dev. To ease stable backports, a version of systemd with those changes is provided via bookworm-backports. In case you have further questions, please contact the systemd team at . On behalf of the systemd team, Michael [1] https://salsa.debian.org/systemd-team/systemd/-/merge_requests/196 --- End Message --- --- Begin Message --- Source: udftools Source-Version: 2.3-2 Done: Pali Rohár We believe that the bug you reported is fixed in the latest version of udftools, 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 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pali Rohár (supplier of updated udftools 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, 16 May 2024 20:10:10 +0200 Source: udftools Architecture: source Version: 2.3-2 Distribution: unstable Urgency: medium Maintainer: Pali Rohár Changed-By: Pali Rohár Closes: 1060477 Changes: udftools (2.3-2) unstable; urgency=medium . * Change Build-Depends from udev to systemd-dev (Closes: #1060477) Checksums-Sha1: ef935368617d71571b9c4b540befa3a6b6765c49 1602 udftools_2.3-2.dsc 0cbe3fc705bceb8b54f27320e5c38c9bdbfc3826 8216 udftools_2.3-2.debian.tar.xz 0475eb676a6323e9c13cfb26afde1cde956ce64e 5662 udftools_2.3-2_source.buildinfo Checksums-Sha256: 475aa9c59e9796fa0b2217736c70acbd3045e0b95ba2cb856e3e95ff78ea47e7 1602 udftools_2.3-2.dsc ff5941f54ceb7636384c025ff5bd3b09a66f62fb87e80f519c154fd6ad0ae4bf 8216 udftools_2.3-2.debian.tar.xz a759203917af173d419b5c79dc6336137d38cb315c16d7a2535e413c470e0890 5662 udftools_2.3-2_source.buildinfo Files: 1e668bb693807124c16c9d5562fe2903 1602 otherosfs optional udftools_2.3-2.dsc 20f4658d3c674a64d734f07e9e8c548d 8216 otherosfs optional udftools_2.3-2.debian.tar.xz da79de09556cea748fce5ea2b21cc0ff 5662 otherosfs optional udftools_2.3-2_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmZPD2kQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFFmjDACn6d8J2zueFoFzJ+gEwSNF9ifhAfCO8QSZ vnZB3lfB+65WsEKkdoq04P4ixw80taf5+by2Pd8KdKigorSUT3lRjaCmiNoGiZDw NIGApsw/NSGu6r++JJa18vf8Jdbcm/SbeOK8arn1oYi5GBKphSAgllCheSaYJjUX 4nUoOIbB6P4GijQ+zZdsMuVjFEljc/fZK9f0rfkn9fBTltYYjA5wVU43wZtOg6/Y Fzmc9jru8Dt/APRR+/V8pBohsE/A2KouYWfo56hsUrtzVWyWd7Gy6bG1IPusBY/H dxijtqfTKRgyNkGYVIOsQpdd/K84Q3v5Fxs/j5S4G9dy4IAmK9PJQfUtSPhTCygX cBp2QPPka86nPkwNixAirS54LJFTJFYUqqcSO1fxQ8FB5ltCkdGSd+UyJAivz++1 ir6HqavCLImaneU/wzN//O6FpqvekRPM+gZiWvKhC/c4WSrUozpjdGYEOr6uwDNE LcYndk8dn5xSavuB1a8Eh6EkMjRorAc=
Processed: tagging 1071305
Processing commands for cont...@bugs.debian.org: > tags 1071305 + pending Bug #1071305 [src:elisa-player] elisa-player: FTBFS: error: ‘class OrgKdeBalooMainInterface’ has no member named ‘registerBalooWatcher’ Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1071305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071305 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reopen 1071220
Processing commands for cont...@bugs.debian.org:
> reopen 1071220
Bug #1071220 {Done: Luca Boccassi } [src:netplan.io]
netplan.io: autopkgtest fails with systemd 256
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions netplan.io/1.0-2.1.
> retitle 1071220 netplan.io: missing '--action add' in udevadm command
Bug #1071220 [src:netplan.io] netplan.io: autopkgtest fails with systemd 256
Changed Bug title to 'netplan.io: missing '--action add' in udevadm command'
from 'netplan.io: autopkgtest fails with systemd 256'.
> severity 1071220 important
Bug #1071220 [src:netplan.io] netplan.io: missing '--action add' in udevadm
command
Severity set to 'important' from 'serious'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1071220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1071334: marked as done (pixz: FTBFS: FAIL cppcheck-src.sh)
Your message dated Thu, 23 May 2024 09:10:52 +
with message-id
and subject line Bug#1071334: fixed in pixz 1.0.7-3
has caused the Debian Bug report #1071334,
regarding pixz: FTBFS: FAIL cppcheck-src.sh
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.)
--
1071334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071334
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pixz
Version: 1.0.7-2
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
configure.ac:14: warning: The macro `AC_PROG_CC_STDC' is obsolete.
configure.ac:14: You should run autoupdate.
./lib/autoconf/c.m4:1666: AC_PROG_CC_STDC is expanded from...
configure.ac:14: the top level
configure.ac:14: installing './compile'
configure.ac:47: installing './config.guess'
configure.ac:47: installing './config.sub'
configure.ac:11: installing './install-sh'
configure.ac:11: installing './missing'
src/Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'
dh_auto_configure
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports the include directive... yes (GNU style)
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 whether gcc understands -c and -o together... yes
checking dependency style of gcc... none
checking for src/pixz.1... no
checking for a2x... a2x
checking for ceil in -lm... yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking if compiler needs -Werror to reject unknown flags... no
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if more special flags are required for pthreads... no
checking for PTHREAD_PRIO_INHERIT... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for libarchive... yes
checking for liblzma... 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 fcntl.h... yes
checking for stdint.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking for off_t... yes
checking for size_t... yes
checking for ssize_t... yes
checking for uint16_t... yes
checking for uint32_t... yes
checking for uint64_t... yes
checking for uint8_t... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking for GNU libc compatible malloc... yes
checking for GNU libc compatible realloc... yes
checking for working strtod... yes
checking for memchr... yes
checking for memmove... yes
checking for memset... yes
checking for strerror... yes
checking for strtol... yes
checking for gcc options needed to detect all undeclared functions... none
needed
checking for sys/endian.h... no
checking for endian.h... yes
checking whether htole64 is declared... yes
checking whether le64toh is declared... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
Bug#1071643: horizon-eda: Missing build dependency on cppzmq-dev
On Thu, May 23, 2024 at 09:34:48AM +0200, Uwe Steinmann wrote: > Thanks Adrian! > > Quite strange. It does have a build depend on cppzmq-dev ... No, it does not: https://tracker.debian.org/media/packages/h/horizon-eda/control-2.6.0-2 >... > So I restarted from ground in pbuilder and > 1. copied >horizon-eda_2.6.0-3.debian.tar.xz, >... 2.6.0-3 is not in the archive. cu Adrian
Bug#1071643: horizon-eda: Missing build dependency on cppzmq-dev
Thanks Adrian! Quite strange. It does have a build depend on cppzmq-dev and compiling it in my local pbuilder environment just works. I just did another compile run after removing libzmq5 without an error. Though, if I remember propperly the first compilation after setting up pbuilder shew the same error, but only once. So I restarted from ground in pbuilder and 1. copied horizon-eda_2.6.0-3.debian.tar.xz, horizon-eda_2.6.0-3.dsc and horizon-eda_2.6.0.orig.tar.xz into /tmp 2. Run pbuilder sudo pbuilder --login --bindmounts /tmp 3. Unpacked the source and went into horizon-eda-2.6.0 dpkg-source -x horizon-eda_2.6.0-3.dsc cd horizon-eda-2.6.0 4. Install all build dependencies and devscripts apt-get build-dep . apt-get install devscripts 5. Run debuild Well, no problem so far, so I will try to upload a new version unless you see something obvious that is missing. Uwe Am Thu, May 23, 2024 at 12:45:06AM +0300 schrieb Adrian Bunk: > Source: horizon-eda > Version: 2.6.0-2 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/logs.php?pkg=horizon-eda=2.6.0-2 > > ... > Has header "zmq.hpp" : NO > > ../meson.build:46:8: ERROR: Problem encountered: cppzmq not found > > > > I haven't checked whether this is the only missing build dependency. > > BTW: > The build dependency on libzmq5 looks wrong and is already covered > by the build dependency on libzmq3-dev, please remove libzmq5 since > this will break with the next soname change of libzmq. -- MMK GmbH, Fleyer Str. 196, 58097 Hagen uwe.steinm...@mmk-hagen.de Tel: 02331 840446Fax: 02331 843920 signature.asc Description: PGP signature
Bug#1071298: marked as done (canna: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file)
Your message dated Thu, 23 May 2024 07:51:00 +
with message-id
and subject line Bug#1071298: fixed in canna 3.7p3-22
has caused the Debian Bug report #1071298,
regarding canna: FTBFS: dpkg-gensymbols: error: some symbols or patterns
disappeared in the symbols file
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.)
--
1071298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:canna
Version: 3.7p3-21
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
cp -an --reflink=auto canuum/config.guess
debian/.debhelper/bucket/files/5b6877e0d2db2a7ef37611a0c5dfb81eabbe34519bd648bf71f8b7d4e3847850.tmp
cp: warning: behavior of -n is non-portable and may change in future; use
--update=none instead
mv
debian/.debhelper/bucket/files/5b6877e0d2db2a7ef37611a0c5dfb81eabbe34519bd648bf71f8b7d4e3847850.tmp
debian/.debhelper/bucket/files/5b6877e0d2db2a7ef37611a0c5dfb81eabbe34519bd648bf71f8b7d4e3847850
cp -f /usr/share/misc/config.guess ./canuum/config.guess
cp -an --reflink=auto canuum/config.sub
debian/.debhelper/bucket/files/86b363ca4362b5f2562a0a6f0c5f9d445de3ab67de34c3e4a7dc0ca1f854e17a.tmp
cp: warning: behavior of -n is non-portable and may change in future; use
--update=none instead
mv
debian/.debhelper/bucket/files/86b363ca4362b5f2562a0a6f0c5f9d445de3ab67de34c3e4a7dc0ca1f854e17a.tmp
debian/.debhelper/bucket/files/86b363ca4362b5f2562a0a6f0c5f9d445de3ab67de34c3e4a7dc0ca1f854e17a
cp -f /usr/share/misc/config.sub ./canuum/config.sub
dh_autoreconf
find . canuum ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path
'*/.hg/*' -o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a -type f -exec
md5sum {} + -o -type l -printf "symlink %p
" > debian/autoreconf.before
[... snipped ...]
mv debian/canna-utils/usr/share/man/ja/man1/delwords.1.dh-new
debian/canna-utils/usr/share/man/ja/man1/delwords.1
mv debian/canna-utils/usr/share/man/ja/man1/lsdic.1.dh-new
debian/canna-utils/usr/share/man/ja/man1/lsdic.1
mv debian/canna-utils/usr/share/man/ja/man1/mkdic.1.dh-new
debian/canna-utils/usr/share/man/ja/man1/mkdic.1
mv debian/canna-utils/usr/share/man/ja/man1/mkromdic.1.dh-new
debian/canna-utils/usr/share/man/ja/man1/mkromdic.1
mv debian/canna-utils/usr/share/man/ja/man1/mvdic.1.dh-new
debian/canna-utils/usr/share/man/ja/man1/mvdic.1
mv debian/canna-utils/usr/share/man/ja/man1/rmdic.1.dh-new
debian/canna-utils/usr/share/man/ja/man1/rmdic.1
mv debian/canna-utils/usr/share/man/man1/addwords.1.dh-new
debian/canna-utils/usr/share/man/man1/addwords.1
mv debian/canna-utils/usr/share/man/man1/cannacheck.1.dh-new
debian/canna-utils/usr/share/man/man1/cannacheck.1
mv debian/canna-utils/usr/share/man/man1/cannastat.1.dh-new
debian/canna-utils/usr/share/man/man1/cannastat.1
mv debian/canna-utils/usr/share/man/man1/catdic.1.dh-new
debian/canna-utils/usr/share/man/man1/catdic.1
mv debian/canna-utils/usr/share/man/man1/chkconc.1.dh-new
debian/canna-utils/usr/share/man/man1/chkconc.1
mv debian/canna-utils/usr/share/man/man1/cpdic.1.dh-new
debian/canna-utils/usr/share/man/man1/cpdic.1
mv debian/canna-utils/usr/share/man/man1/cshost.1.dh-new
debian/canna-utils/usr/share/man/man1/cshost.1
mv debian/canna-utils/usr/share/man/man1/delwords.1.dh-new
debian/canna-utils/usr/share/man/man1/delwords.1
mv debian/canna-utils/usr/share/man/man1/lsdic.1.dh-new
debian/canna-utils/usr/share/man/man1/lsdic.1
mv debian/canna-utils/usr/share/man/man1/mkdic.1.dh-new
debian/canna-utils/usr/share/man/man1/mkdic.1
mv debian/canna-utils/usr/share/man/man1/mkromdic.1.dh-new
debian/canna-utils/usr/share/man/man1/mkromdic.1
mv debian/canna-utils/usr/share/man/man1/mvdic.1.dh-new
debian/canna-utils/usr/share/man/man1/mvdic.1
mv debian/canna-utils/usr/share/man/man1/rmdic.1.dh-new
debian/canna-utils/usr/share/man/man1/rmdic.1
mv debian/libcanna1g-dev/usr/share/man/ja/man3/RkBgnBun.3.dh-new
debian/libcanna1g-dev/usr/share/man/ja/man3/RkBgnBun.3
mv debian/libcanna1g-dev/usr/share/man/ja/man3/RkCloseRoma.3.dh-new
debian/libcanna1g-dev/usr/share/man/ja/man3/RkCloseRoma.3
mv
Bug#1060540: marked as done (thinkfan: Please switch Build-Depends to systemd-dev)
Your message dated Thu, 23 May 2024 09:48:42 +0200 with message-id <52892d84-c631-4504-87bf-4bd202b12...@debian.org> and subject line Re: thinkfan: Please switch Build-Depends to systemd-dev has caused the Debian Bug report #1060540, regarding thinkfan: Please switch Build-Depends to systemd-dev 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.) -- 1060540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: thinkfan Version: 1.3.1-4 Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: systemd-dev Hi, your package thinkfan declares a Build-Depends on systemd and/or udev. In most cases, this build dependency is added to get the paths that are defined in udev.pc or systemd.pc (via pkgconfig). Since systemd_253-2 [1], these two pkgconfig files have been split into a separate package named systemd-dev. This package is arch:all, so even available on non-Linux architectures, which will simplify the installation of upstream provided service files / udev rules. To not make existing source packages FTBFS, the systemd and udev package have a Depends: systemd-dev. This dependency will be removed at some point though before trixie is released. Once this happens, this issue will be bumped to RC. Please update your build dependencies accordingly at your earliest convenience. If all you need is the systemd.pc or udev.pc pkgconfig file, please replace any systemd or udev Build-Depends with systemd-dev. In most cases that should be sufficient. If your package needs further resources from systemd or udev to build successfully, it's fine to keep those Build-Depends in addition to systemd-dev. To ease stable backports, a version of systemd with those changes is provided via bookworm-backports. In case you have further questions, please contact the systemd team at . On behalf of the systemd team, Michael [1] https://salsa.debian.org/systemd-team/systemd/-/merge_requests/196 --- End Message --- --- Begin Message --- Version: 1.3.1-5 Am 23.05.2024 um 07:25 schrieb Petter Reinholdtsen: [Michael Biebl] your package thinkfan declares a Build-Depends on systemd and/or udev. As far as I can tell, this issue was fixed in version 1.3.1-4. Perhaps this issue should be closed before the package is removed from testing? It looks like it has been addressed in 1.3.1-5 https://tracker.debian.org/news/1530377/accepted-thinkfan-131-5-source-into-unstable/ thinkfan (1.3.1-5) unstable; urgency=medium . * The "Greetings from Mini-Debconf Berlin!" release * Move package to DEP-14 layout * d/control: Remove systemd build-dep (Fixes: #1060540) Due to the wrong syntax (Fixes: instead of Closes:) the bug report was not closed properly. That said, the changes in https://salsa.debian.org/debian/thinkfan/-/commit/1d8cf8c675e83c7e75aad946d27264462ad5e30d look broken from a cursory glance: Both the openrc and sysv init script are installed as /etc/init.d/thinkfan, so you can't have both installed simultaneously. Michael OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#1071655: pytorch: FTBFS on ppc64el
Source: pytorch
Version: 2.1.2+dfsg-4
Severity: serious
Tags: ftbfs
Hello,
pytorch FTBFS on ppc64el:
FAILED:
caffe2/CMakeFiles/torch_cpu.dir/__/aten/src/ATen/native/Col2Im.cpp.o
/usr/bin/c++ -DAT_PER_OPERATOR_HEADERS -DCAFFE2_BUILD_MAIN_LIB
-DFMT_HEADER_ONLY=1 -DHAVE_MALLOC_USABLE_SIZE=1 -DHAVE_MMAP=1
-DHAVE_SHM_OPEN=1 -DHAVE_SHM_UNLINK=1
-DMINIZ_DISABLE_ZIP_READER_CRC32_CHECKS -DONNXIFI_ENABLE_EXT=1
-DONNX_ML=1 -DONNX_NAMESPACE=onnx -DTORCH_ENABLE_LLVM -DUSE_C10D_GLOO
-DUSE_DISTRIBUTED -DUSE_EXTERNAL_MZCRC -DUSE_RPC -DUSE_TENSORPIPE
-D_FILE_OFFSET_BITS=64 -Dtorch_cpu_EXPORTS
-I/home/merkys/pytorch-2.1.2+dfsg/build/aten/src
-I/home/merkys/pytorch-2.1.2+dfsg/aten/src
-I/home/merkys/pytorch-2.1.2+dfsg/build
-I/home/merkys/pytorch-2.1.2+dfsg
-I/home/merkys/pytorch-2.1.2+dfsg/cmake/../third_party/benchmark/include
-I/usr/lib/llvm-16/include -I/home/merkys/pytorch-2.1.2+dfsg/debian/foxi
-I/home/merkys/pytorch-2.1.2+dfsg/build/debian/foxi
-I/home/merkys/pytorch-2.1.2+dfsg/torch/csrc/api
-I/home/merkys/pytorch-2.1.2+dfsg/torch/csrc/api/include
-I/home/merkys/pytorch-2.1.2+dfsg/caffe2/aten/src/TH
-I/home/merkys/pytorch-2.1.2+dfsg/build/caffe2/aten/src/TH
-I/home/merkys/pytorch-2.1.2+dfsg/build/caffe2/aten/src
-I/home/merkys/pytorch-2.1.2+dfsg/build/caffe2/../aten/src
-I/home/merkys/pytorch-2.1.2+dfsg/torch/csrc
-I/home/merkys/pytorch-2.1.2+dfsg/third_party/miniz-2.1.0
-I/home/merkys/pytorch-2.1.2+dfsg/debian/kineto/libkineto/include
-I/home/merkys/pytorch-2.1.2+dfsg/debian/kineto/libkineto/src
-I/home/merkys/pytorch-2.1.2+dfsg/aten/src/ATen/..
-I/home/merkys/pytorch-2.1.2+dfsg/c10/..
-I/home/merkys/pytorch-2.1.2+dfsg/third_party/flatbuffers/include
-isystem /home/merkys/pytorch-2.1.2+dfsg/build/third_party/gloo -isystem
/home/merkys/pytorch-2.1.2+dfsg/cmake/../third_party/gloo -isystem
/home/merkys/pytorch-2.1.2+dfsg/cmake/../third_party/googletest/googlemock/include
-isystem
/home/merkys/pytorch-2.1.2+dfsg/cmake/../third_party/googletest/googletest/include
-isystem /usr/include/opencv4 -isystem /usr/include/eigen3 -isystem
/home/merkys/pytorch-2.1.2+dfsg/caffe2 -Wdate-time -D_FORTIFY_SOURCE=2
-g -O2 -ffile-prefix-map=/home/merkys/pytorch-2.1.2+dfsg=.
-fstack-protector-strong -Wformat -Werror=format-security -gsplit-dwarf
-Wno-dangling-reference -I/usr -D_GLIBCXX_USE_CXX11_ABI=1
-fvisibility-inlines-hidden -DUSE_KINETO -DLIBKINETO_NOCUPTI
-DLIBKINETO_NOROCTRACER -DSYMBOLICATE_MOBILE_DEBUG_HANDLE -O2 -fPIC
-Wall -Wextra -Werror=return-type -Werror=non-virtual-dtor
-Werror=range-loop-construct -Werror=bool-operation -Wnarrowing
-Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds
-Wno-unknown-pragmas -Wno-unused-parameter -Wno-unused-function
-Wno-unused-result -Wno-strict-overflow -Wno-strict-aliasing
-Wno-stringop-overflow -Wno-psabi -Wno-error=pedantic
-Wno-error=old-style-cast -Wno-invalid-partial-specialization
-Wno-unused-private-field -Wno-aligned-allocation-unavailable
-Wno-missing-braces -fdiagnostics-color=always -faligned-new
-Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno
-fno-trapping-math -Werror=format -Werror=cast-function-type
-Wno-stringop-overflow -O2 -g -DNDEBUG -std=gnu++17 -fPIC
-DCAFFE2_USE_GLOO -DTH_HAVE_THREAD -Wall -Wextra -Wno-unused-parameter
-Wno-unused-function -Wno-unused-result -Wno-missing-field-initializers
-Wno-unknown-pragmas -Wno-type-limits -Wno-array-bounds
-Wno-strict-overflow -Wno-strict-aliasing -Wno-missing-braces
-Wno-maybe-uninitialized -fvisibility=hidden -O2 -fopenmp -MD -MT
caffe2/CMakeFiles/torch_cpu.dir/__/aten/src/ATen/native/Col2Im.cpp.o -MF
caffe2/CMakeFiles/torch_cpu.dir/__/aten/src/ATen/native/Col2Im.cpp.o.d
-o caffe2/CMakeFiles/torch_cpu.dir/__/aten/src/ATen/native/Col2Im.cpp.o
-c /home/merkys/pytorch-2.1.2+dfsg/aten/src/ATen/native/Col2Im.cpp
In file included from
/home/merkys/pytorch-2.1.2+dfsg/aten/src/ATen/cpu/vec/vec256/vsx/vec256_common_vsx.h:8,
from
/home/merkys/pytorch-2.1.2+dfsg/aten/src/ATen/cpu/vec/vec256/vec256.h:19,
from
/home/merkys/pytorch-2.1.2+dfsg/aten/src/ATen/cpu/vec/vec.h:6,
from
/home/merkys/pytorch-2.1.2+dfsg/aten/src/ATen/native/cpu/utils.h:4,
from
/home/merkys/pytorch-2.1.2+dfsg/aten/src/ATen/native/im2col.h:7,
from
/home/merkys/pytorch-2.1.2+dfsg/aten/src/ATen/native/Col2Im.cpp:6:
/home/merkys/pytorch-2.1.2+dfsg/aten/src/ATen/cpu/vec/vec256/vsx/vec256_double_vsx.h:
In member function ‘at::vec::CPU_CAPABILITY::Vectorized
at::vec::CPU_CAPABILITY::Vectorized::acos() const’:
/home/merkys/pytorch-2.1.2+dfsg/aten/src/ATen/cpu/vec/vec256/vsx/vec256_double_vsx.h:220:14:
error: ‘Sleef_acosd2_u10’ was not declared in this scope; did you mean
‘Sleef_acoshf_u10’?
220 | return {Sleef_acosd2_u10(_vec0), Sleef_acosd2_u10(_vec1)};
| ^~~~
| Sleef_acoshf_u10
