Bug#1074071: marked as done (libkf6screen-bin has an undeclared file conflict)
Your message dated Sat, 22 Jun 2024 22:19:13 + with message-id and subject line Bug#1074071: fixed in libkscreen 4:6.1.0-2 has caused the Debian Bug report #1074071, regarding libkf6screen-bin has an undeclared file conflict 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.) -- 1074071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074071 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libkf6screen-bin Version: 4:6.1.0-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libkf5screen-bin libkf6screen-bin has an undeclared file conflict. This may result in an unpack error from dpkg. The files * /usr/bin/kscreen-doctor * /usr/lib/systemd/user/plasma-kscreen.service are contained in the packages * libkf5screen-bin * 4:5.27.11-1 as present in trixie|unstable * 4:5.27.5-2 as present in bookworm * libkf6screen-bin/4:6.1.0-1 as present in experimental These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected files. 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: libkscreen Source-Version: 4:6.1.0-2 Done: Patrick Franz We believe that the bug you reported is fixed in the latest version of libkscreen, 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 1074...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patrick Franz (supplier of updated libkscreen 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: Sun, 23 Jun 2024 00:12:34 +0200 Source: libkscreen Architecture: source Version: 4:6.1.0-2 Distribution: experimental Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Patrick Franz Closes: 1074071 Changes: libkscreen (4:6.1.0-2) experimental; urgency=medium . [ Patrick Franz ] * Add missing Breaks+Replaces for libkf6screen-bin against libkf5screen-bin (Closes: #1074071). Checksums-Sha1: cfd1ba0c1d44082cc8045bcf106fad2fb9de7a07 2966 libkscreen_6.1.0-2.dsc 73b51303b7f24a5c0b4a655d84616fbc48f66369 23692 libkscreen_6.1.0-2.debian.tar.xz a02ae0efeb4c287306990cfe1f99f2efb566f023 13021 libkscreen_6.1.0-2_source.buildinfo Checksums-Sha256: 24fa67037d65965a18c3608a5cfd186e833d2c9a52ea19bef3e091c38ecb6ec0 2966 libkscreen_6.1.0-2.dsc 2e681403813a34a294eeed85d51b2b4bc5f41302bd15560845103089d0785b7d 23692 libkscreen_6.1.0-2.debian.tar.xz b887d648880949812319b9173c3afd88597a5a1dfde67ab476a92069a8de7793 13021 libkscreen_6.1.0-2_source.buildinfo Files: c2f7f04876c6d41fc6b016de89c52632 2966 libs optional libkscreen_6.1.0-2.dsc 80869fbc594c933914600b60cbc30856 23692 libs optional libkscreen_6.1.0-2.debian.tar.xz 80ec3fe0856f155b776a2956b08e190f 13021 libs optional libkscreen_6.1.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEYodBXDR68cxZHu3Knp96YDB3/lYFAmZ3TF8ACgkQnp96YDB3 /lY1JA//RDWNUADieWaG9+UxMXiD6PzcG7Da5uGqlpGpP2TcwNFAmuxvdusANV7+ nOu8UE/sQM9mi98ZoPZVhbPFnv0n/r5Sg4rPMujamICrGbuIu1/EyR4T8cnKEEct NKtJiqO9teKIiqqONahrFnl5fHwNI4vKWhQNwl1vN3nommzkL5toA7Glu+My4flO wJFeqI0aXtpX9Kd2Vd7+gvSE46KgY39K9qBJ9oqU45IKCWhCxAz8IB8DAtayHY9M BtbuBoCGMBCUCd+1eBEbzUBrS/MpffJYDi0GZMtAFbEfjGKxUF0fXg6TzTvnls2/ RgudVmljudZXxotH25AmwXmy+a/SZ7KfOIQCIGEuBlr0uLSYQpAH5MPqWJrzoOm0 Ttz9jZek+UV5wuGNb/fgQuQIPs2d6Dxxdm4byHoYMalfIkkmnm/+rfreqpIn4XsO jKVZ1czQH+QLW7JgCosEypXS6fMoGadtQXnfiZ109MoZqdnJrIuOt06hGG2+CsQP v0FiTVuZqaiyENmmDJFvrTa5EhmCXKg2gfTlJw7zCPqMrOna6LPUessy34Cwe1zW BJ/rDgKRQH2fqzmz/DnbS3t+Fb60Y+tEqGKZ+F541usll9s3Y36xMLBwbpFCOw0I nJz63gw5ecUFcmWlnj5F39GfNgy72g1EKV0Xn0qUKma2V0D8zSw= =uz1G -END PGP SIGNATURE- pgpe9oMsB7aIB.pgp Description: PGP signature --- End Message ---
Processed: Bug#1074071 marked as pending in libkscreen
Processing control commands: > tag -1 pending Bug #1074071 [libkf6screen-bin] libkf6screen-bin has an undeclared file conflict Added tag(s) pending. -- 1074071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074071 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074071: marked as pending in libkscreen
Control: tag -1 pending Hello, Bug #1074071 in libkscreen reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/qt-kde-team/kde/libkscreen/-/commit/db2b3255dd90db720fbb5512dc195394327ebf9e Add missing Breaks+Replaces for libkf6screen-bin against libkf5screen-bin (Closes: #1074071). (this message was generated automatically) -- Greetings https://bugs.debian.org/1074071
Processed: limit source to linux, tagging 1071378
Processing commands for cont...@bugs.debian.org: > limit source linux Limiting to bugs with field 'source' containing at least one of 'linux' Limit currently set to 'source':'linux' > tags 1071378 + pending Bug #1071378 [src:linux] linux-image-6.7.12-686-pae: Crash during early boot Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1071378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1072885
Processing commands for cont...@bugs.debian.org: > close 1072885 8.2.20-2 Bug #1072885 [src:php8.2] php8.2: CVE-2024-5458 The source 'php8.2' and version '8.2.20-2' do not appear to match any binary packages Marked as fixed in versions php8.2/8.2.20-2. Bug #1072885 [src:php8.2] php8.2: CVE-2024-5458 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1072885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072885: closing 1072885
close 1072885 8.2.20-2 thanks
Bug#1071860: marked as done (fis-gtm: Searches for libgcrypt with libgcrypt-config)
Your message dated Sat, 22 Jun 2024 20:35:22 + with message-id and subject line Bug#1071860: fixed in fis-gtm 7.0-005-2 has caused the Debian Bug report #1071860, regarding fis-gtm: Searches for libgcrypt with libgcrypt-config 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.) -- 1071860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071860 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fis-gtm Version: 7.0-005-1 Severity: important User: ametz...@debian.org Usertags: libgcrypt-config-removal Control: block 714589 by -1 fis-gtm relies on libgcrypt-config to locate libgcrypt. libgcrypt-config is scheduled for removal and will be dropped in libgcrypt 1.11. Please use pkg-config/pkgconf instead. A development snapshot of the yet-unreleased libgcrypt 1.11 is available in experimental. cu Andreas --- End Message --- --- Begin Message --- Source: fis-gtm Source-Version: 7.0-005-2 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of fis-gtm, 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. Andreas Tille (supplier of updated fis-gtm 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: Sat, 22 Jun 2024 21:59:20 +0200 Source: fis-gtm Architecture: source Version: 7.0-005-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 1071860 Changes: fis-gtm (7.0-005-2) unstable; urgency=medium . * Build-Depends: s/libgcrypt20-dev | //, pkgconf Closes: #1071860 * Fix libncurses-dev Build-Depends * Use secure URI in debian/watch Checksums-Sha1: 8dd690f4eb57a6ce41b1beb81a5fe063cd69 2264 fis-gtm_7.0-005-2.dsc a58107efd25d65cdf8d181944e97c90d79b7a421 24284 fis-gtm_7.0-005-2.debian.tar.xz 4756ca41f84be3b9a894751f598beac1e24d5471 9227 fis-gtm_7.0-005-2_amd64.buildinfo Checksums-Sha256: 1fb32388f58cebd8c4fdcfc1079caf71519a014b8b9961f125ce18d5a415f224 2264 fis-gtm_7.0-005-2.dsc 81db41bda9039c2b5a15ee11cbf6307b306d59443745caa0677f64f8f0541474 24284 fis-gtm_7.0-005-2.debian.tar.xz 2b3e2c432f72efdd7061339856d50c897b9a7db51eb645408b26dd3e87e4467d 9227 fis-gtm_7.0-005-2_amd64.buildinfo Files: d46820063de2dfd0f774a930ceecc951 2264 database optional fis-gtm_7.0-005-2.dsc d13fd581ce1239a601b4127cc7f79c49 24284 database optional fis-gtm_7.0-005-2.debian.tar.xz a081bdf90d46068096e621a36b19fe68 9227 database optional fis-gtm_7.0-005-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmZ3LmMRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtHRGQ//csMFfHC4M4LH0igI/jBE4x+E8HRoJOAJ jiKW/cCn8ZUWnpubChK5AZ/0n9uX3MbnAM6FWMAMblDP67oWTlZWwKKP5XqCZjXE sP65pH/7mqAPbqOd97Z8fiiLngIPbMmrARyzy1uMaj0Jqxgo/s/pdHQTH408GdPd F3GBa5IZ+YIDjjBphLrYS6e1tK7jlyWHq3Xo2YGJwiCKIjh9uExtu9n2v2qKhWrf bJUqYQKwGRHi6+CGQ8CzxuqQT9ULlZTe0RfKjFAReOyzqxon/VrclTHiirHjI/9d 5q4rxfYzvTvb7uu3aXYkIOmsRaxgifx7cB6yyxTuU1I9+p8PTZNcIsgh1OrOTP6z in6rX4WONHs7TxU9sJuwNpeXdLtosrDUwD7nPPGBDaDZos1BHY1ql1S9LHzJzl4M 85aErmECAd0hrVTL9RyGVzFjH99H3JPVSKig6CDvvsExlOflUq+qVpX2Ovb1kwGk yGdRnoadLcuNYEg5RjnZO5uSUT6K479eM/aetb4M7L5jphmQRJNMFXrP+A3p1Ih4 vp5vvcaj8nAOMBBDTBAbeelvyxU0ERt01pVAw1lluzEZZnDZd0gUGwh9ABPE+F42 j4QxXZDteZVGvRGgll+PcR2F2B265cE/9LfGdyyvCIYdDefn5WLu1lejX8/f6NBs Iz2tVz9UrHQ= =FUNO -END PGP SIGNATURE- pgpQTtAKD4DYz.pgp Description: PGP signature --- End Message ---
Bug#1065385: marked as done (btrfs-progs: Please switch Build-Depends to systemd-dev)
Your message dated Sat, 22 Jun 2024 20:34:26 + with message-id and subject line Bug#1065385: fixed in btrfs-progs 6.6.3-1.2 has caused the Debian Bug report #1065385, regarding btrfs-progs: 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.) -- 1065385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: btrfs-progs Version: 6.6.3-1 Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: systemd-dev Hi, your package btrfs-progs 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: btrfs-progs Source-Version: 6.6.3-1.2 Done: Chris Hofstaedtler We believe that the bug you reported is fixed in the latest version of btrfs-progs, 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 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Hofstaedtler (supplier of updated btrfs-progs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 12 Jun 2024 21:22:17 +0200 Source: btrfs-progs Architecture: source Version: 6.6.3-1.2 Distribution: unstable Urgency: medium Maintainer: Adam Borowski Changed-By: Chris Hofstaedtler Closes: 1065385 1071297 1073073 Changes: btrfs-progs (6.6.3-1.2) unstable; urgency=medium . * Non-maintainer upload. * Switch Build-Depends from udev to systemd-dev (Closes: #1065385) * Install files into UsrMerged layout (DEP17 M2) (Closes: #1073073) . [ Peter Michael Green ] * Change inode_includes to ext2fs_inode_includes (Closes: #1071297) * Bump dependency on libext2fs-dev. Checksums-Sha1: 4556c83df9958d651fdb13c1f235a42963abc9c7 2584 btrfs-progs_6.6.3-1.2.dsc d26abdd9b35ab621a5196618b3241af1700b2eb9 17792 btrfs-progs_6.6.3-1.2.debian.tar.xz 9bcd0c10940fa54644c34527b64ae82c75278ecd 11336 btrfs-progs_6.6.3-1.2_arm64.buildinfo Checksums-Sha256: cdf3618e085e688f31e8747791a706ad939d8229d5bf3b622bd10a61b71d2da6 2584 btrfs-progs_6.6.3-1.2.dsc 91c56c7ff9a45a8ab0143aa033a2866da893723195eb259c406becb4482c5b68 17792 btrfs-progs_6.6.3-1.2.debian.tar.xz 2130457c18555324ac686da65c173252d7f4cbfac5b4949963103ce529f7502a 11336 btrfs-progs_6.6.3-1.2_arm64.buildinfo Files: f15e12418f755c1d30ac04f205dbfe66 2584 admin optional btrfs-progs_6.6.3-1.2.dsc 4df5dfd995729bc3d0f5be635a435fdc 17792 admin optional btrfs-progs_6.6.3-1.2.debian.tar.xz 9454bb51fc1d51768ebe9911a9c85991 11336 admin optional btrfs-progs_6.6.3-1.2_arm64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmZp+Z4ACgkQXBPW25MF LgPq4BAAjXrnMoO0NCw28bdR8OS0fbsd2fV0NGYv5cwbbkXqX0FxWci87B3TnwXg qKsWYPmTTWNm6JjtPlh5j/cxZFngrVw0KQ7gPvEZijZsPz/DG/ZiZjWQUWY3wOMr
Processed: imgcrypt has an undeclared file conflict on /usr/bin/ctr
Processing control commands: > affects -1 + containerd Bug #1074070 [imgcrypt] imgcrypt has an undeclared file conflict on /usr/bin/ctr Added indication that 1074070 affects containerd -- 1074070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074070: imgcrypt has an undeclared file conflict on /usr/bin/ctr
Package: imgcrypt Version: 1.1.11-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + containerd imgcrypt has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/bin/ctr is contained in the packages * containerd * 1.4.13~ds1-1~deb11u2 as present in bullseye-security * 1.4.13~ds1-1~deb11u4 as present in bullseye * 1.6.20~ds1-1+b1 as present in bookworm * 1.6.24~ds1-2 as present in trixie|unstable * imgcrypt/1.1.11-1 as present in experimental These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected file. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance.
Processed: libkf6screen-bin has an undeclared file conflict
Processing control commands: > affects -1 + libkf5screen-bin Bug #1074071 [libkf6screen-bin] libkf6screen-bin has an undeclared file conflict Added indication that 1074071 affects libkf5screen-bin -- 1074071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074071 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074071: libkf6screen-bin has an undeclared file conflict
Package: libkf6screen-bin Version: 4:6.1.0-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libkf5screen-bin libkf6screen-bin has an undeclared file conflict. This may result in an unpack error from dpkg. The files * /usr/bin/kscreen-doctor * /usr/lib/systemd/user/plasma-kscreen.service are contained in the packages * libkf5screen-bin * 4:5.27.11-1 as present in trixie|unstable * 4:5.27.5-2 as present in bookworm * libkf6screen-bin/4:6.1.0-1 as present in experimental These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected files. 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.
Bug#1071775: marked as done (plotpy: FTBFS: plotpy/tests/benchmarks/test_benchmarks.py Fatal Python error: Aborted)
Your message dated Sat, 22 Jun 2024 19:34:08 + with message-id and subject line Bug#1071775: fixed in plotpy 2.3.5-1 has caused the Debian Bug report #1071775, regarding plotpy: FTBFS: plotpy/tests/benchmarks/test_benchmarks.py Fatal Python error: Aborted 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.) -- 1071775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071775 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:plotpy Version: 2.2.0-3 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --with=python3 --with=numpy3 --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:311: python3.12 setup.py config [05/24/24 19:15:06] WARNING pyproject.toml does not contain a setuptools.py:119 tool.setuptools_scm section WARNING pyproject.toml does not contain a setuptools.py:119 tool.setuptools_scm section I: pybuild base:311: python3.11 setup.py config [05/24/24 19:15:08] WARNING pyproject.toml does not contain a setuptools.py:119 tool.setuptools_scm section WARNING pyproject.toml does not contain a setuptools.py:119 tool.setuptools_scm section dh_auto_build -O--buildsystem=pybuild I: pybuild base:311: /usr/bin/python3.12 setup.py build [05/24/24 19:15:10] WARNING pyproject.toml does not contain a setuptools.py:119 tool.setuptools_scm section WARNING pyproject.toml does not contain a setuptools.py:119 tool.setuptools_scm section cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ In file included from ./src/pcolor.cpp:23: ./src/arrays.hpp:50:34: warning: ‘template struct std::iterator’ is deprecated [-Wdeprecated-declarations] 50 | class iterator : public std::iterator | ^~~~ In file included from /usr/include/c++/13/bits/stl_algobase.h:65, from /usr/include/c++/13/bits/specfun.h:43, from /usr/include/c++/13/cmath:3699, from /usr/include/c++/13/math.h:36, from /usr/include/python3.12/pyport.h:195, from /usr/include/python3.12/Python.h:38, from ./src/pcolor.cpp:6: /usr/include/c++/13/bits/stl_iterator_base_types.h:127:34: note: declared here 127 | struct _GLIBCXX17_DEPRECATED iterator | ^~~~ cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ In file included from ./src/scaler.cpp:37: ./src/arrays.hpp:50:34: warning: ‘template struct std::iterator’ is deprecated [-Wdeprecated-declarations] 50 | class iterator : public std::iterator | ^~~~ In file included from /usr/include/c++/13/bits/stl_algobase.h:65, from /usr/include/c++/13/bits/specfun.h:43, from /usr/include/c++/13/cmath:3699, from /usr/include/c++/13/math.h:36, from /usr/include/python3.12/pyport.h:195, from /usr/include/python3.12/Python.h:38, from ./src/scaler.cpp:6: /usr/include/c++/13/bits/stl_iterator_base_types.h:127:34: note: declared here 127 | struct _GLIBCXX17_DEPRECATED iterator | ^~~~ I: pybuild base:311: /usr/bin/python3 setup.py build [05/24/24 19:15:31] WARNING pyproject.toml does not contain a setuptools.py:119 tool.setuptools_scm section [05/24/24 19:15:32] WARNING pyproject.toml does not contain a setuptools.py:119 tool.setuptools_scm section cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ In file included from ./src/pcolor.cpp:23: ./src/arrays.hpp:50:34: warning: ‘template struct std::iterator’ is deprecated [-Wdeprecated-declarations] 50 | class iterator : public std::iterator | ^~~~ In file included
Processed: Re: Bug#1073176: gramps: Error with loss of data: TypeError: '<' not supported between instances of 'str' and 'NoneType'
Processing control commands: > tag -1 unreproducible Bug #1073176 [gramps] gramps: Error with loss of data: TypeError: '<' not supported between instances of 'str' and 'NoneType' Added tag(s) unreproducible. > severity -1 normal Bug #1073176 [gramps] gramps: Error with loss of data: TypeError: '<' not supported between instances of 'str' and 'NoneType' Severity set to 'normal' from 'grave' -- 1073176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1073176: gramps: Error with loss of data: TypeError: '<' not supported between instances of 'str' and 'NoneType'
control: tag -1 unreproducible control: severity -1 normal On Fri, 14 Jun 2024 19:39:23 +1200 Mark Robinson wrote: On completing the database migration I created a new person, added birth and death information including a new death location and notes, and clicked OK. This resulted in the python error referred to in the headline which left the new person with the OK button greyed out and no way to save it. The record was lost. Hi Mark, sorry about that. I've tried to reproduce this bug, using the steps you've described above. It worked without any problem on my system, so I'm not able to reproduce the faulty behaviour of gramps. I'm therefore lowering the severity, because otherwise gramps would be removed from testing. I currently don't think that this would be necessary. However, there should be an automatic backup of your database, as printed in the status messages: 11723: WARNING: upgrade.py: line 2218: If upgrade and loading the Family Tree works, you can delete the zip file at /home/mark/.gramps/ROBINSON__Mark_Gregory_2024-06-14_12-07-04.zip Could you try to extract that database version of your family tree and open it with gramps? The program should then ask you again to convert the tree to the new database format. Afterwards, could you repeat the steps above, i. e. creating a new person, adding birth and death information etc.? Then please report back if the error still occurs. Regards, Tobias OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: fixed 1072885 in 8.2.20-1~deb12u1
Processing commands for cont...@bugs.debian.org: > fixed 1072885 8.2.20-1~deb12u1 Bug #1072885 [src:php8.2] php8.2: CVE-2024-5458 Marked as fixed in versions php8.2/8.2.20-1~deb12u1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1072885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072214: marked as done (python3-proto-plus declares Conflicts: nanopb in violation of Debian policy 10.1)
Your message dated Sat, 22 Jun 2024 16:35:05 + with message-id and subject line Bug#1072214: fixed in python-proto-plus 1.23.0-3 has caused the Debian Bug report #1072214, regarding python3-proto-plus declares Conflicts: nanopb in violation of Debian policy 10.1 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.) -- 1072214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-proto-plus Version: 1.23.0-2 Severity: serious Justification: policy 10.1 python3-proto-plus declares a conflict with nanopb. Doing so violates Debian policy section 10.1. More background can be found in #1072073. Helmut --- End Message --- --- Begin Message --- Source: python-proto-plus Source-Version: 1.23.0-3 Done: Yogeswaran Umasankar We believe that the bug you reported is fixed in the latest version of python-proto-plus, 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 1072...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yogeswaran Umasankar (supplier of updated python-proto-plus package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 18 Jun 2024 15:30:00 + Source: python-proto-plus Architecture: source Version: 1.23.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Yogeswaran Umasankar Closes: 1072214 Changes: python-proto-plus (1.23.0-3) unstable; urgency=medium . * d/control: removed file Conflicts for python3-proto-plus binary. (Closes: #1072214) Checksums-Sha1: 2b6d2969bbe5595821ada609edd3f7fb8b80de9f 2372 python-proto-plus_1.23.0-3.dsc 8899809de9fc2810c91aa34571da444b832f025e 4332 python-proto-plus_1.23.0-3.debian.tar.xz 11883fff8bda24c47045448988fe0418af3a697c 8075 python-proto-plus_1.23.0-3_arm64.buildinfo Checksums-Sha256: 9060675c655d5ce3b27b45b2b5e19df085a18bf74b3ddb2df1ffa3d66af5c99e 2372 python-proto-plus_1.23.0-3.dsc 860d515d4cbfb614ebab0104230ad41d02be1facccde6390a4b5da1c5206492b 4332 python-proto-plus_1.23.0-3.debian.tar.xz 6b65b71c162ec3695665732dc35be4e90b33295eca0e1dd0e54e0e531bbf428c 8075 python-proto-plus_1.23.0-3_arm64.buildinfo Files: 0ae01aea517b3f7ebf55b6df75f223d7 2372 python optional python-proto-plus_1.23.0-3.dsc 138345cef468e12d6ddd4846282685da 4332 python optional python-proto-plus_1.23.0-3.debian.tar.xz 237b32abcac3bb718767fb72706df346 8075 python optional python-proto-plus_1.23.0-3_arm64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE/qLi99g13V/he2oYtIOKvyeCVXsFAmZ29vAACgkQtIOKvyeC VXvm5w//XImTBW7MCWCHO1HvpmO5aCeX2kY2mnlqgOm/ox/t/7K+hitq8nvGQZ4D lpdaJihkhyJ7jZ58DRs/Bp0+lq/uGk4WORQPdatWo+0/uJKeVhCdO6XqDccJ8qvS 2xTtpXhqfIQea3SyrfOsuKn3fRPETfDU/UjMcdqLFPWVIQRqj4DjXZuZGzDleiJv +a4/tc9qqQhLw8ykybljIzVtcBQ+Qsr7qLkQokU/txpkXXoROInMRsAXk7Dr94lD LrrywmgUkbtUqUwrhuHcgUaELfTEv3HxLcM44lte08pPxJfEblPwUXJ8YwmqmY6K tx0gt4755hh0H4lffLAUQdza5+O89YbBfpogej60EXo881j/AzNkncAC11wzPlUY S0l1k5urrZycR8BRzwgZ06qSUATP0H6BoPZpD+SRmUGnZC0ihYcitqYJ6k0H9vy8 0AEyob1jWUXeq4zoCLEmtFNZT1MPSR6bjFKBcLdBrQlt0XRwM1F3UcXzXPky4PB4 9fFLVpwLp0v6EosWn7f7MS37XDEts84YNVlE5UYuhGOSPa6qqN8AsCcgZZOmU/C8 2GVzs/8FNsTbzLcCO5CXoGT3/be6V03OaFkVVHA0MABBoONE2KTyYQ53XS9FJ5z9 Je31rqmm6MQOVHIafHWqAupSIErWwtWgl0du7moHJbjdw0A2Plk= =2EeA -END PGP SIGNATURE- pgpAi9MgH8oqJ.pgp Description: PGP signature --- End Message ---
Bug#1066963: marked as done (xmorph: FTBFS with -Werror=implicit-function-declaration)
Your message dated Sat, 22 Jun 2024 16:35:16 + with message-id and subject line Bug#1066963: fixed in xmorph 1:20150712-5.1 has caused the Debian Bug report #1066963, regarding xmorph: FTBFS with -Werror=implicit-function-declaration to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066963 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xmorph Version: 1:20150712-5 Severity: serious Tags: ftbfs Hello, there are multiple implicit function errors when trying to build xmorph, some trivial, but also an API issue: 8X-- In file included from RgbaImage.c:935: RgbaImage.c: In function 'rgbaImageWarp': warp.h:19:20: error: implicit declaration of function 'warp_image_inv_new'; did you mean 'warp_image_inv_old'? [-Werror=implicit-function-declaration] 19 | #define warp_image warp_image_inv_new |^~ RgbaImage.c:963:3: note: in expansion of macro 'warp_image' 963 | warp_image(img_orig->ri, img_warp->ri, img_orig->ncols, | ^~ 8X-- warp.h contains #define warp_image warp_image_inv_new with warp_image_inv_new being defined in warp2.h. i.e. #include without including warp2.h first triggers an implicit declaration of function error. OTOH warp2.h #includes warp.h so if everything switched to warp.h we would be fine, but then there is no point in having a separate warp.h. Perhaps the proper fix would be to stop shipping an (unused) library. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' --- End Message --- --- Begin Message --- Source: xmorph Source-Version: 1:20150712-5.1 Done: Francisco Vilmar Cardoso Ruviaro We believe that the bug you reported is fixed in the latest version of xmorph, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Francisco Vilmar Cardoso Ruviaro (supplier of updated xmorph 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: Wed, 19 Jun 2024 15:42:19 + Source: xmorph Architecture: source Version: 1:20150712-5.1 Distribution: unstable Urgency: medium Maintainer: Debian PhotoTools Maintainers Changed-By: Francisco Vilmar Cardoso Ruviaro Closes: 1066963 Changes: xmorph (1:20150712-5.1) unstable; urgency=medium . * Non-maintainer upload. * Add debian/patches/Fix-implicit-function-declaration.patch. Thanks to Shengjing Zhu . (Closes: #1066963) Checksums-Sha1: 38939a1130181dbb874455ac8ea8d6fa37001996 2279 xmorph_20150712-5.1.dsc ba38884e3efb3cf8f20ab228b65e6c9ae24569bc 12732 xmorph_20150712-5.1.debian.tar.xz 6207827d45ec1b643a4bb38e08e73d3263628e70 9220 xmorph_20150712-5.1_amd64.buildinfo Checksums-Sha256: 786f44ac6bdfa5dc54cf274b2c505e798f3b7218c359b6d202151543115cd3e5 2279 xmorph_20150712-5.1.dsc acabc38d64c08e16b8ccfe5f742384ba6b6b521ad1d1c6225eb1c4b84a0ad7d6 12732 xmorph_20150712-5.1.debian.tar.xz 45d3b3e58c0ffed75e1a5e2136a1a0d58b1a166c430072a468a083e47f96a8f0 9220 xmorph_20150712-5.1_amd64.buildinfo Files: 09edbbf601426b1f0c52a5b848813728 2279 graphics optional xmorph_20150712-5.1.dsc 2c58aec314e9454dcf915bf70ff9783d 12732 graphics optional xmorph_20150712-5.1.debian.tar.xz f699d974e836069f48b97d7f35f78133 9220 graphics optional xmorph_20150712-5.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEG4z2Vu87hEcvSPDngvv3BgsvfQAFAmZy/bgSHHZpbG1hckBk ZWJpYW4ub3JnAAoJEIL79wYLL30AwgUP/0rSrig4SfQtur2m2KzN38w9uny+GQlE 5XB7TBrnbMCm9KwvKsFiw3HRAbLOwMe19fvFMeIg28fzJaPuwa3DT9d9p94ldcCS l1wNhLD6jYz+qC/Yff5ewbRpZK+jJ45C3ynLI6cv2Dr+sEl8dZ76vDTmhbzcEi67 dRSFmRvbnpzCoqhVJU+nw+co9GO0USdbIAaMO0CT0aIqJZBZa0wbvORuMMAEnfnb rXnBdN16c8ouHjiDJg/ySQxad5qaUBZ2cXGSAVvUM4irkzQsTFWvfgO+nQCm6DDG hcQCaymE0gdYULtu829a2bkpnCLb+7hkN969O0ttDkrrxfFHw3qhGuW2HVWe+bNU zYnF1aPx1vYPh9KEY3Xl1AiHNBITY4lkfbdKm1vleN6MvXpL0WFLvEfAXh5Kiz5u QCrvgXuXtVs6fl9Vb+VAabnKhlaPKJDKtB0tLtmKlToGUlXsFNq0V7p/n1rY8y++
Processed: src:git: fails to migrate to testing for too long: triggers autopkgtest issues
Processing control commands: > close -1 1:2.45.2-1 Bug #1074064 [src:git] src:git: fails to migrate to testing for too long: triggers autopkgtest issues Marked as fixed in versions git/1:2.45.2-1. Bug #1074064 [src:git] src:git: fails to migrate to testing for too long: triggers autopkgtest issues Marked Bug as done -- 1074064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074064: src:git: fails to migrate to testing for too long: triggers autopkgtest issues
Source: git Version: 1:2.43.0-1 Severity: serious Control: close -1 1:2.45.2-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:git has been trying to migrate for 32 days [2]. Hence, I am filing this bug. The version in unstable causes issues for at least two reverse (test) dependencies. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=git OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:bambam: fails to migrate to testing for too long: autopkgtest regression
Processing control commands: > close -1 1.3.0+dfsg-1 Bug #1074063 [src:bambam] src:bambam: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions bambam/1.3.0+dfsg-1. Bug #1074063 [src:bambam] src:bambam: fails to migrate to testing for too long: autopkgtest regression Marked Bug as done -- 1074063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074063: src:bambam: fails to migrate to testing for too long: autopkgtest regression
Source: bambam Version: 1.2.1+dfsg-1 Severity: serious Control: close -1 1.3.0+dfsg-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:bambam has been trying to migrate for 32 days [2]. Hence, I am filing this bug. The version in unstable fails its own autopkgtest. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=bambam OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:node-nock: fails to migrate to testing for too long: autopkgtest regression
Processing control commands: > close -1 13.5.4-1 Bug #1074062 [src:node-nock] src:node-nock: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions node-nock/13.5.4-1. Bug #1074062 [src:node-nock] src:node-nock: fails to migrate to testing for too long: autopkgtest regression Marked Bug as done -- 1074062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074062 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074062: src:node-nock: fails to migrate to testing for too long: autopkgtest regression
Source: node-nock Version: 13.3.3-1 Severity: serious Control: close -1 13.5.4-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:node-nock has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable fails its own autopkgtest. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=node-nock OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1073108: marked as done (tools-nrepl-clojure: replace to-be-removed markdown build-dependency)
Your message dated Sat, 22 Jun 2024 10:45:00 -0400 with message-id <9929576f-7a36-41a5-837b-c622fa1ba...@debian.org> and subject line Close 1073108 has caused the Debian Bug report #1073108, regarding tools-nrepl-clojure: replace to-be-removed markdown build-dependency 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.) -- 1073108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tools-nrepl-clojure Version: 0.2.13-2 Severity: serious Control: block 1072958 by -1 Your package build-depends on markdown. Per bug #1063645, markdown is not maintained upstream or in Debian and should be removed. Drop-in alternatives, for examples the suggested `discount` or `python3-markdown` or `libtext-markdown-perl`. `discount` and `libtext-markdown-perl` provide a `markdown` program if your package needs that. --- End Message --- --- Begin Message --- This has been fixed in 0.2.13-3. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ --- End Message ---
Bug#1072764: node-multiparty: FTBFS: autobuilder hangs
Hi, On Fri, 7 Jun 2024 17:23:17 +0200 Santiago Vila wrote: During a rebuild of all packages in unstable, your package failed to build: The same seems to happen on ci.d.n on all architectures. The timeout there is 1 seconds (or 2:47h). I'm going to add node-multiparty to the ci.d.n reject_list, I'll remove it once this bug is fixed. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: tagging 1074051
Processing commands for cont...@bugs.debian.org: > tags 1074051 + trixie sid Bug #1074051 [libpam-pgsql] libpam-pgsql: remove from Debian? Added tag(s) sid and trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1074051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074051 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074051: libpam-pgsql: remove from Debian?
Package: libpam-pgsql Version: 0.7.3.2-1+b1 Severity: serious pam-pgsql's last upload was in 2014. This was a maintainer upload. There are currently open release-critical bugs, preventing pam-pgsql from being released with Debian, since 2017 - 6+ years already. PAM modules should IMO be held to high standards of being up to date and maintained. I propose removing pam-pgsql from Debian, as it seems to be effectively unmaintained for a very long time already and it looks like interest has vanished over time. I propose reassigning this bug to ftp.debian.org on or after July 9th. Chris
Bug#1050805: marked as done (dhcpcd-base: DoS: zero-length packet cause eventual lease expiration)
Your message dated Sat, 22 Jun 2024 10:32:08 + with message-id and subject line Bug#1050805: fixed in dhcpcd5 9.4.1-24~deb12u4 has caused the Debian Bug report #1050805, regarding dhcpcd-base: DoS: zero-length packet cause eventual lease expiration 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.) -- 1050805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dhcpcd-base Version: 9.4.1-22 Severity: critical Tags: security Justification: breaks unrelated software X-Debbugs-Cc: Debian Security Team When the dhcpcd DHCPv4 client receives a zero-length UDP packet on port 68, the "network proxy" dhcpcd process exits with status 0. dhcpcd then stops all network activity: It does not renew leases and eventually expires the current lease (unless it has infinite duration) and removes the IP address, leaving the system without networking. This bug can be triggered remotely over the internet from any UDP port and is critical on an internet-facing system that needs DHCP to get an IP address, such as a gateway, a dedicated server or a VM. This affects version 9.4.1-22 (stable) and 1:9.4.1-24~deb12u2 (stable proposed update) but not 1:10.0.2-4 (testing/unstable) as upstream fixed it in 10.0.2: Upstream Bug report: https://github.com/NetworkConfiguration/dhcpcd/issues/179 Upstream Fix: https://github.com/NetworkConfiguration/dhcpcd/commit/8b29c0ddf026c1c5647c3b8c6cfe21699c4056ae This patch does not apply cleanly to 9.4.1 because the privsep structure changed in 10.0.2. It's likely that only the src/privsep.c hunks about len == 0 and eloop_exit() needs to be backported, the other changes are just here to avoid compiler warnings about unused parameters. -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-11-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dhcpcd-base depends on: ii adduser 3.134 ii libc6 2.36-9+deb12u1 ii libudev1 252.12-1~deb12u1 Versions of packages dhcpcd-base recommends: pn wpasupplicant Versions of packages dhcpcd-base suggests: ii openresolv [resolvconf] 3.12.0-3 -- Configuration Files: /etc/dhcpcd.conf changed [not included] -- no debconf information --- End Message --- --- Begin Message --- Source: dhcpcd5 Source-Version: 9.4.1-24~deb12u4 Done: Martin-Éric Racine We believe that the bug you reported is fixed in the latest version of dhcpcd5, 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 1050...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin-Éric Racine (supplier of updated dhcpcd5 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: Sat, 15 Jun 2024 12:37:49 +0300 Source: dhcpcd5 Architecture: source Version: 9.4.1-24~deb12u4 Distribution: bookworm Urgency: medium Maintainer: Martin-Éric Racine Changed-By: Martin-Éric Racine Closes: 1050805 1057959 Changes: dhcpcd5 (9.4.1-24~deb12u4) bookworm; urgency=medium . * Add --no-stop-on-upgrade --no-restart-after-upgrade (Closes: #1057959). * Cherry-pick upstream backported fixes for RC bug (Closes: #1050805). * Update dhcpcd.preinst version check to match current one. Checksums-Sha1: d340bbdb4418776198fa2ecb5f7e2d2a5ef32885 2103 dhcpcd5_9.4.1-24~deb12u4.dsc 9c8144f43c155835aafaf909efdc0c0beaa6ddc1 25832 dhcpcd5_9.4.1-24~deb12u4.debian.tar.xz 53a00f8285d60e2b0ca8660b1e58b74292dcc48b 5350 dhcpcd5_9.4.1-24~deb12u4_source.buildinfo Checksums-Sha256: bf82ad59a697f1019a51905c9c930ffb001b228666a4ea2f1845c1d9ebcc81b6 2103 dhcpcd5_9.4.1-24~deb12u4.dsc aef79207e682132b92167f63a7ca02f06efeb5bcd06da3cdf165fe9750b88ac2 25832 dhcpcd5_9.4.1-24~deb12u4.debian.tar.xz 2f1061dc8078ead2dee5c6a74cc89ccd5de62445635cfbad36dcf14dabaab91b 5350
Processed: user maytha8the...@gmail.com, usertagging 1074048, usertagging 1074049, usertagging 1074050 ...
Processing commands for cont...@bugs.debian.org: > user maytha8the...@gmail.com Setting user to maytha8the...@gmail.com (was maytha8the...@gmail.com). > usertags 1074048 - todo + pending-upload Usertags were: todo. There are now no usertags set. > usertags 1074049 + pending-upload There were no usertags set. Usertags are now: pending-upload. > usertags 1074050 + pending-upload There were no usertags set. Usertags are now: pending-upload. > tags 1074048 + pending Bug #1074048 [src:nwg-hello] nwg-hello: new upstream version available Added tag(s) pending. > tags 1074049 + pending Bug #1074049 [nwg-hello] nwg-hello: update dependencies Added tag(s) pending. > tags 1074050 + pending Bug #1074050 [nwg-clipman] nwg-clipman: update dependencies Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1074048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074048 1074049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074049 1074050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074050: nwg-clipman: update dependencies
Package: nwg-clipman Severity: serious Should depend on gir1.2-* libs instead of development headers, and should have python3-gi in Depends as well. -- Maytham Alsudany Debian Maintainer maytham @ OFTC maytha8 @ Libera signature.asc Description: This is a digitally signed message part
Bug#1074049: nwg-hello: update dependencies
Package: nwg-hello Severity: serious Should depend on gir1.2-* libs instead of development headers, and should have python3-gi in Depends as well. -- Maytham Alsudany Debian Maintainer maytham @ OFTC maytha8 @ Libera signature.asc Description: This is a digitally signed message part
Bug#1033210: marked as done (cairomm FTBFS with nocheck profile: missing boost test)
Your message dated Sat, 22 Jun 2024 08:34:52 + with message-id and subject line Bug#1033210: fixed in cairomm 1.14.5-2 has caused the Debian Bug report #1033210, regarding cairomm FTBFS with nocheck profile: missing boost test 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.) -- 1033210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cairomm Version: 1.14.4-2 Severity: serious Tags: ftbfs trixie sid cairomm fails to build from source when built with the nocheck build profile, because the Boost Test dependency is annotated , but actually required. Such build failures are considered release critical in trixie and later. This is not an rc bug in bookworm and earlier. Helmut --- End Message --- --- Begin Message --- Source: cairomm Source-Version: 1.14.5-2 Done: Jeremy Bícha We believe that the bug you reported is fixed in the latest version of cairomm, 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 1033...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bícha (supplier of updated cairomm 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, 20 Jun 2024 16:45:06 -0400 Source: cairomm Built-For-Profiles: noudeb Architecture: source Version: 1.14.5-2 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bícha Closes: 1033210 Changes: cairomm (1.14.5-2) unstable; urgency=medium . * Fix nocheck build (Closes: #1033210) Checksums-Sha1: 7b9eb2d5ef8ef60f6f61c016184232111e039284 2248 cairomm_1.14.5-2.dsc 3db504c877c63f465dcfe3eb1d32f3eff6ea8d94 5204 cairomm_1.14.5-2.debian.tar.xz d168e1008c3db57538575e49e0f1d376df917eb7 11438 cairomm_1.14.5-2_source.buildinfo Checksums-Sha256: 57aeaab53ef23b93ed2bffc5ffce0657772be3b5027fa7aec12bf9e7f6668b96 2248 cairomm_1.14.5-2.dsc 5913dcdd4552121fbf0d9da55b5936d31378e7ca3d549d80b4bdfa06a5e6a0a1 5204 cairomm_1.14.5-2.debian.tar.xz 217562ae7ec46159ad297c906afb9154947deab5d6249ad871632d3fc07bd260 11438 cairomm_1.14.5-2_source.buildinfo Files: d5f80510f3a6b22ae34efbe77c2c45a2 2248 libs optional cairomm_1.14.5-2.dsc 6f7fc160b36f41ba7bb6cc4edc21f576 5204 libs optional cairomm_1.14.5-2.debian.tar.xz 9251d94ebc8ecab54ff0304fc68f463e 11438 libs optional cairomm_1.14.5-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmZ2hs4ACgkQ5mx3Wuv+ bH39RRAAtHOzw9UCUkESy2wS+9FTMqEs7EGEdNk7/Qu5LWRQcEOxNajEGMzj/mXH G6/VZgUQu07/kLhw6CsrLcIclMhM/h0KYTH+n7c2ZNIm9wpT5WIbdoatTyI9UjyM 9+iHz5duOhKCwNA9OH2r6Qwg8f4aTi3Ec7ifx58YvrSTX0+IXM8+9GsCnHmnmpKX OlUH7MRj8LKV6CnW6azW93/xCDfmydbrryEidXG5vVA65HCrj8HyEbfGS+qG7eGO 1l8DuIxFzzvtj/SYxgz32prYq4R4GMXv67zaslSk/sDW0dgpqXSL+tQSyEJVmgSF C7UZsZKwv8uuikWZU2eYCFZJkEz5T9mkkgzZlAA07SBaG8pJP3aIZ2NxdxbnUNov eLgz/Kl50wlBMNbdXhV9v38XalDgUmvxV8KVUT/RXzaDfuWBFUCiaUtMChIsD71f wBLvWj0G5CuPCHDPLN6UtDmTPgR3bgcqEiqXhJ6HAKcxZLxCkY7qP3JebFB4hgKR RY9A86Cx0kY+r1zEG1CmJxcCz13WOYu+ldzy2gANenCGGatqBgtm76YbgrwWhxpF u2DbSz0T4fKlvHAzjnPtOGZOjyTC9z7IMYzbYB5hsjSSsT7hjVc4NtvPCxhWOGpC 3z2G0G6V9FDyfCYQsejaqmuBpI9IcrZGKABiFcBJNlEEncjTgsQ= =f3QQ -END PGP SIGNATURE- pgpZzSOfUs2o4.pgp Description: PGP signature --- End Message ---
Processed: Re: gtk-d: FTBFS on armel: unsatisfiable build-dependencies: dh-dlang (>= 0.6.6), gir-to-d
Processing control commands: > severity -1 important Bug #1069555 [src:gtk-d] gtk-d: FTBFS on armel: unsatisfiable build-dependencies: dh-dlang (>= 0.6.6), gir-to-d Severity set to 'important' from 'serious' -- 1069555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069555 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069555: gtk-d: FTBFS on armel: unsatisfiable build-dependencies: dh-dlang (>= 0.6.6), gir-to-d
Control: severity -1 important I'm demoting because I consider it acceptable for gtk-d to not be available on armel. Thank you, Jeremy Bícha
Bug#1069544: marked as done (mame: FTBFS on armel: collect2: error: ld returned 1 exit status)
Your message dated Sat, 22 Jun 2024 03:45:59 -0400 with message-id and subject line Re: mame: FTBFS on armel: collect2: error: ld returned 1 exit status has caused the Debian Bug report #1069544, regarding mame: FTBFS on armel: collect2: error: ld returned 1 exit status 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.) -- 1069544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069544 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mame Version: 0.264+dfsg.1-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. Relevant part (hopefully): > g++ -o ../../../../../mame obj/Release/src/mame/mame.o > obj/Release/generated/mame/mame/drivlist.o obj/Release/generated/version.o > -fuse-ld=gold -Wl,--no-keep-memory -Wl,-z,relro -Wl,-z,now -Wl,--long-plt > -L"../../../../../../../../usr/X11/lib" > -L"../../../../../../../../usr/X11R6/lib" > -L"../../../../../../../../usr/openwin/lib" -L"." > -L"../../../../../scripts/mame_mame" -L"../../../../../scripts/src/mame" > -L"../../../../../scripts/src" -L"../../../../../scripts/src/osd/mame_mame" > -L"../../../../../scripts/src/osd" -L/usr/lib/arm-linux-gnueabi > -Wl,--start-group ../../../../../scripts/mame_mame/libitech.a > ../../../../../scripts/mame_mame/libsubsino.a > ../../../../../scripts/mame_mame/libmidw8080.a > ../../../../../scripts/mame_mame/libericsson.a > ../../../../../scripts/mame_mame/libzpa.a > ../../../../../scripts/mame_mame/libtecfri.a > ../../../../../scripts/mame_mame/libfairchild.a > ../../../../../scripts/mame_mame/libcompugraphic.a > ../../../../../scripts/mame_mame/libchromatics.a > ../../../../../scripts/mame_mame/libwyse.a > ../../../../../scripts/mame_mame/libtatsumi.a > ../../../../../scripts/mame_mame/libgridcomp.a > ../../../../../scripts/mame_mame/libces.a > ../../../../../scripts/mame_mame/libupl.a > ../../../../../scripts/mame_mame/libadp.a > ../../../../../scripts/mame_mame/libfuuki.a > ../../../../../scripts/mame_mame/libsnk.a > ../../../../../scripts/mame_mame/libbarcrest.a > ../../../../../scripts/mame_mame/libzenith.a > ../../../../../scripts/mame_mame/libbondwell.a > ../../../../../scripts/mame_mame/libfalco.a > ../../../../../scripts/mame_mame/libsynertek.a > ../../../../../scripts/mame_mame/libsamsung.a > ../../../../../scripts/mame_mame/libunicard.a > ../../../../../scripts/mame_mame/libmips.a > ../../../../../scripts/mame_mame/libdg.a > ../../../../../scripts/mame_mame/libhomebrew.a > ../../../../../scripts/mame_mame/libcasio.a > ../../../../../scripts/mame_mame/libgalaxian.a > ../../../../../scripts/mame_mame/libosi.a > ../../../../../scripts/mame_mame/libelektron.a > ../../../../../scripts/mame_mame/libkyocera.a > ../../../../../scripts/mame_mame/libarcadia.a > ../../../../../scripts/mame_mame/libibm.a > ../../../../../scripts/mame_mame/libnintendo.a > ../../../../../scripts/mame_mame/libensoniq.a > ../../../../../scripts/mame_mame/libunisonic.a > ../../../../../scripts/mame_mame/libepson.a > ../../../../../scripts/mame_mame/libunico.a > ../../../../../scripts/mame_mame/libbandai.a > ../../../../../scripts/mame_mame/libtatung.a > ../../../../../scripts/mame_mame/libtiger.a > ../../../../../scripts/mame_mame/libmetro.a > ../../../../../scripts/mame_mame/libexcellent.a > ../../../../../scripts/mame_mame/libpacman.a > ../../../../../scripts/mame_mame/libtoshiba.a > ../../../../../scripts/mame_mame/libtoaplan.a > ../../../../../scripts/mame_mame/libfidelity.a > ../../../../../scripts/mame_mame/libxerox.a > ../../../../../scripts/mame_mame/libverifone.a > ../../../../../scripts/mame_mame/libeaca.a > ../../../../../scripts/mame_mame/libheathkit.a > ../../../../../scripts/mame_mame/libamiga.a > ../../../../../scripts/mame_mame/libphilips.a > ../../../../../scripts/mame_mame/libausnz.a > ../../../../../scripts/mame_mame/libmatic.a > ../../../../../scripts/mame_mame/libwing.a > ../../../../../scripts/mame_mame/libnichibutsu.a > ../../../../../scripts/mame_mame/libsharp.a > ../../../../../scripts/mame_mame/libfunworld.a > ../../../../../scripts/mame_mame/libsanritsu.a > ../../../../../scripts/mame_mame/libbitcorp.a > ../../../../../scripts/mame_mame/libmit.a > ../../../../../scripts/mame_mame/libtomy.a > ../../../../../scripts/mame_mame/libmicroterm.a > ../../../../../scripts/mame_mame/libampro.a > ../../../../../scripts/mame_mame/libliberty.a >
