Bug#1004177: marked as done (nodejs: CVE-2021-44531 CVE-2021-44532 CVE-2021-44533 CVE-2022-21824)
Your message dated Tue, 22 Mar 2022 06:54:16 +0100 with message-id and subject line [ftpmas...@ftp-master.debian.org: Accepted nodejs 12.22.9~dfsg-1 (source) into unstable] has caused the Debian Bug report #1004177, regarding nodejs: CVE-2021-44531 CVE-2021-44532 CVE-2021-44533 CVE-2022-21824 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.) -- 1004177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004177 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nodejs Version: 12.22.7~dfsg-2 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 12.22.5~dfsg-2~11u1 Hi, The following vulnerabilities were published for nodejs. CVE-2021-44531[0]: | Improper handling of URI Subject Alternative Names CVE-2021-44532[1]: | Certificate Verification Bypass via String Injection CVE-2021-44533[2]: | Incorrect handling of certificate subject and issuer fields CVE-2022-21824[3]: | Prototype pollution via console.table properties If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-44531 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44531 [1] https://security-tracker.debian.org/tracker/CVE-2021-44532 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44532 [2] https://security-tracker.debian.org/tracker/CVE-2021-44533 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44533 [3] https://security-tracker.debian.org/tracker/CVE-2022-21824 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21824 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: nodejs Source-Version: 12.22.9~dfsg-1 This should fix #1004177 and the four open CVEs. - Forwarded message from Debian FTP Masters - -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 27 Jan 2022 13:42:36 +0100 Source: nodejs Architecture: source Version: 12.22.9~dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jérémy Lal Changes: nodejs (12.22.9~dfsg-1) unstable; urgency=medium . [ Yadd ] * Team upload * Add fix for node-js-yaml ≥ 4 * Clean unneeded versioned dependency contraints . [ Jérémy Lal ] * New upstream version 12.22.9~dfsg * Fix make-doc patch for marked 4 * Depends on libuv >= 1.38.0 * Apply js-yaml compatibility before make-doc patch Checksums-Sha1: dc662f5a0242f5d9153819cad3dad2fbf9669f90 3585 nodejs_12.22.9~dfsg-1.dsc d34ba34e53c3bc8598b2c163e43a9c2e9fb3fa38 86416 nodejs_12.22.9~dfsg.orig-types-node.tar.xz c9cec5626868335ae420881721a35d19f0c83a98 19022540 nodejs_12.22.9~dfsg.orig.tar.xz be46f3b758351924d7a6cc9430e88d67078db225 137232 nodejs_12.22.9~dfsg-1.debian.tar.xz 477f3d797dac59ca91c572e312023c358bb3c765 8769 nodejs_12.22.9~dfsg-1_source.buildinfo Checksums-Sha256: d94dcb28644d30cbd07f225f5374a9364863f70a02a4bdeea45ed653792c9cf7 3585 nodejs_12.22.9~dfsg-1.dsc dd84dca45bae69dc6d8d6064f901ef59eef5394222c1b3218874caf87479085c 86416 nodejs_12.22.9~dfsg.orig-types-node.tar.xz e7980415c9bfc69e707bbe65a889a86e79f884d59f87df3f7d79daf00e6c6cac 19022540 nodejs_12.22.9~dfsg.orig.tar.xz 84a4eabbe63f8d74a475ad899144676348e71c59084ee4fbcb4750e45d928a8b 137232 nodejs_12.22.9~dfsg-1.debian.tar.xz 983126e12043b1f94bcea72371cad3265e0e004b6d3a703e3ad3a5f5a5072927 8769 nodejs_12.22.9~dfsg-1_source.buildinfo Files: 680bb2c159069a0620d16034a7635069 3585 javascript optional nodejs_12.22.9~dfsg-1.dsc 455e1daa2ed80b184330e006f34466f5 86416 javascript optional nodejs_12.22.9~dfsg.orig-types-node.tar.xz abc1fab8d774f87a51cb0c694c8dfbb0 19022540 javascript optional nodejs_12.22.9~dfsg.orig.tar.xz 1175caaa8e3c6a17af50176758d0f4e3 137232 javascript optional nodejs_12.22.9~dfsg-1.debian.tar.xz 6e8181fdba412b539bb86fafdaf29437 8769 javascript optional nodejs_12.22.9~dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAmHyneQSHGthcG91ZXJA bWVsaXgub3JnAAoJEGYRwF7dOfN0cjkP/0Tmv8krbZG49cbAIABbpKb3a0nxSWqI FQ402BNJO4QMbxHEDwUernRqecOGSd2o50W9Uwd/bKGB6K8kp+ixOlaNVk7yc7ma COK+pZDaJ6V6x/EsaaHi1mDYfqyczLUR+Ig7bYvh92OLTDYjnY/zxQkXkXtWKMwW XaqA/A3fYsHda4X8kIw2/muBCmhUxDtyGicNlr26AwT7q5hg5/2p/ZE+n/uSjnS5 yo+zqMuLQ2epr04I+izHeAkq0jpkNHjOpIqh7jU0XtrcLssF9DviPTF8ofgXGmfV VipjyDjjLZPhjWDET7JbQNNV/JiwiW+ho3UoSyhBg5oO+TVBEE5n9UTgspI+3nYS
Bug#1007234: Test suite fails on all but amd64 arches
I haven't heard of this before. I'm sure this is easy to diagnose for someone who can reproduce it. I can't, since I don't have access to a system other than AMD64. I can tell from reading the code that what is happening is there is a a negative number somewhere that there shouldn't be. My best guess is that the 2's complement arithmetic hack for interpreting the run-length-encoding in the function 'readPackBitsRow16' in converter/other/pnmtopalm/palmtopnm.c isn't doing what it's expected to do. In particular, the line int const signedIncount = (signed char)incountByte might be declaring a positive number, whereas it's supposed to be negative (which means -signedIncount below is negative whereas it is expected to be positive). -- Bryan Henderson San Jose, California
Bug#991541: Related merge request
Dear maintainer, I have added a related merge request on salsa fast-forwarding the related git sub-module to the fixed version. https://salsa.debian.org/php-team/pear/php-pear/-/merge_requests/3 Not entirely sure if gitlab is the best route to help in this package case, but since I saw a couple of MRs closed, I decided to go that way. Let me know if other changes would be needed, or any other feedback, Best, -Marco
Bug#1007167: Already fixed upstream
This issue was fixed in 1.4.2 via this commit: https://github.com/synfig/synfig/commit/e68ca6ff55a6d6f86220d187bc5df27633382397
Bug#1007992: libigdgmm12: new version causes segfaults
kodi is affected, too. Attached you can find kodi's log file. AFAICT it *does* try vdpau first, but then it exits. Regards Harri kodi.log.gz Description: GNU Zip compressed data
Bug#1004563: (no subject)
Still the same issueSubject: Re: enblend and enfuse depend on libgsl25 that is nonexistent and replaced by libgsl27 Message-ID: <164789523968.487488.17880797647457551802.report...@data.zuhause.xx> X-Mailer: reportbug 11.4.1 Date: Mon, 21 Mar 2022 21:40:39 +0100 Package: enblend Version: 4.2-8 Followup-For: Bug #1004563 X-Debbugs-Cc: bts.debian@schaefer-home.eu -- System Information: Debian Release: bookworm/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-5-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de:en_GB:en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages enblend depends on: ii libc62.33-7 ii libgcc-s112-20220319-1 ii libgomp1 12-20220319-1 ii libgsl25 2.7+dfsg-2 ii liblcms2-2 2.12~rc1-2 ii libstdc++6 12-20220319-1 ii libtiff5 4.3.0-6 ii libvigraimpex11 1.11.1+dfsg-8 Versions of packages enblend recommends: ii hugin 2021.0~beta1+dfsg-1 enblend suggests no packages. -- no debconf information
Bug#998353: Bug#1007707: Update Indonesian translation
Hi Holger, On Fri, 18 Mar 2022 21:38:11 +0100 Holger Wansing wrote: Andika Triwidada wrote (Tue, 15 Mar 2022 11:26:40 +): > > Attached is update to Indonesian translation. Just applied to GIT. Thanks Shall we have an upload of this soon and do the ftp-master dance with this package to have it finally migrate to testing (#998353)? Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1005833: src:ruby-redis: fails to migrate to testing for too long: autopkgtest regression
Hi, On Tue, 15 Feb 2022 19:49:08 +0100 Paul Gevers wrote: The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:ruby-redis has been trying to migrate for 61 days [2]. Hence, I am filing this bug. There is already a bug about the autopkgtest failure. This seems like it really needs to be solved between ruby-redis and ruby-fakeredis. Is there any progress on this issue? Is no progress is there another way to move the problem forward? E.g. revert ruby-redis to the previous version if redis and fakeredis can agree on the change in behavior? Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1001595: src:gcc-defaults-mipsen: fails to migrate to testing for too long
Hi mips porters, On Sun, 12 Dec 2021 21:51:28 +0100 Paul Gevers wrote: The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:gcc-defaults-mipsen has been trying to migrate for 62 days [2]. It's been 161 days now. We expect from you to solve these kind of issues, especially if they have been brought to your attention. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: src:luajit: fails to migrate to testing for too long: SEGFAULT on ppc64el
Processing control commands:
> close -1 2.1.0~beta3+git20210112+dfsg-2
Bug #1008069 [src:luajit] src:luajit: fails to migrate to testing for too long:
SEGFAULT on ppc64el
Marked as fixed in versions luajit/2.1.0~beta3+git20210112+dfsg-2.
Bug #1008069 [src:luajit] src:luajit: fails to migrate to testing for too long:
SEGFAULT on ppc64el
Marked Bug as done
> block -1 by 1004511
Bug #1008069 {Done: Paul Gevers } [src:luajit] src:luajit:
fails to migrate to testing for too long: SEGFAULT on ppc64el
1008069 was not blocked by any bugs.
1008069 was not blocking any bugs.
Added blocking bug(s) of 1008069: 1004511
--
1008069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1008069: src:luajit: fails to migrate to testing for too long: SEGFAULT on ppc64el
Source: luajit Version: 2.1.0~beta3+dfsg-6 Severity: serious Control: close -1 2.1.0~beta3+git20210112+dfsg-2 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1004511 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:luajit has been trying to migrate for 61 days [2]. Hence, I am filing this bug. 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 bookworm, 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/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=luajit OpenPGP_signature Description: OpenPGP digital signature
Bug#1008068: src:ocrad: fails to migrate to testing for too long: autopkgtest regression
Source: ocrad Version: 0.27-2 Severity: serious Control: close -1 0.28-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1004508 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:ocrad has been trying to migrate for 61 days [2]. Hence, I am filing this bug. 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 bookworm, 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/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=ocrad OpenPGP_signature Description: OpenPGP digital signature
Processed: src:ocrad: fails to migrate to testing for too long: autopkgtest regression
Processing control commands:
> close -1 0.28-1
Bug #1008068 [src:ocrad] src:ocrad: fails to migrate to testing for too long:
autopkgtest regression
Marked as fixed in versions ocrad/0.28-1.
Bug #1008068 [src:ocrad] src:ocrad: fails to migrate to testing for too long:
autopkgtest regression
Marked Bug as done
> block -1 by 1004508
Bug #1008068 {Done: Paul Gevers } [src:ocrad] src:ocrad:
fails to migrate to testing for too long: autopkgtest regression
1008068 was not blocked by any bugs.
1008068 was not blocking any bugs.
Added blocking bug(s) of 1008068: 1004508
--
1008068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1005542: marked as done (gnome-tetravex: FTBFS: ../data/meson.build:37:2: ERROR: Function does not take positional arguments.)
Your message dated Mon, 21 Mar 2022 18:49:08 +
with message-id
and subject line Bug#1005542: fixed in gnome-tetravex 1:3.38.2-3
has caused the Debian Bug report #1005542,
regarding gnome-tetravex: FTBFS: ../data/meson.build:37:2: ERROR: Function does
not take positional arguments.
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.)
--
1005542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-tetravex
Version: 1:3.38.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 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_configure -- --bindir=games
> cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson ..
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu --bindir=games
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-tetravex
> Project version: 3.38.2
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16)
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.38
> Vala compiler for the host machine: valac (valac 0.54.6)
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency gio-2.0 found: YES 2.70.3
> Run-time dependency glib-2.0 found: YES 2.70.3
> Run-time dependency gtk+-3.0 found: YES 3.24.31
> Program appstream-util found: YES (/usr/bin/appstream-util)
> Program desktop-file-validate found: YES (/usr/bin/desktop-file-validate)
> Program glib-compile-schemas found: YES (/usr/bin/glib-compile-schemas)
> Library m found: YES
> Configuring org.gnome.Tetravex.service using configuration
>
> ../data/meson.build:37:2: ERROR: Function does not take positional arguments.
>
> A full log can be found at
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
> cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
> ==> meson-logs/meson-log.txt <==
> Build started at 2022-02-12T22:49:44.207478
> Main binary: /usr/bin/python3
> Build Options: -Dprefix=/usr -Dbindir=games -Dlibdir=lib/x86_64-linux-gnu
> -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain
> -Dwrap_mode=nodownload
> Python system: Linux
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-tetravex
> Project version: 3.38.2
> Sanity testing C compiler: cc
> Is cross compiler: False.
> Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
> -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,-z,defs
> Sanity check compile stdout:
>
> -
> Sanity check compile stderr:
>
> -
> Running test binary command:
> /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16)
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.38
> Running compile:
> Working directory: /tmp/tmpt2q23e36
> Command line: valac /tmp/tmpt2q23e36/testfile.vala -C
>
> Code:
> class MesonSanityCheck : Object { }
> Compiler stdout:
>
> Compiler stderr:
>
> Vala compiler for the host machine: valac (valac 0.54.6)
> Sanity testing C compiler: cc
> Is cross compiler: False.
> Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
> -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,-z,defs
> Sanity check compile stdout:
>
> -
> Sanity check compile stderr:
>
> -
> Running test binary command:
> /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe
> C compiler for the build machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16)
> 11.2.0")
> C linker for the build machine: cc ld.bfd 2.38
> Using cached compile:
> Cached command line:
>
> Code:
> class MesonSanityCheck : Object { }
> Cached compiler stdout:
>
> Cached compiler stderr:
>
> Vala compiler for the build machine: valac (valac 0.54.6)
> Build machine cpu family: x86_64
> Build machine cpu: x86_64
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
>
Bug#1005590: marked as done (gnome-user-share: FTBFS: ../data/meson.build:9:5: ERROR: Function does not take positional arguments.)
Your message dated Mon, 21 Mar 2022 18:35:01 + with message-id and subject line Bug#1005590: fixed in gnome-user-share 3.34.0-5 has caused the Debian Bug report #1005590, regarding gnome-user-share: FTBFS: ../data/meson.build:9:5: ERROR: Function does not take positional arguments. 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.) -- 1005590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-user-share Version: 3.34.0-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220212 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_configure -- \ > -Dnautilus_extension=true \ > -Dmodules_path=/usr/lib/apache2/modules/ \ > -Dsystemduserunitdir=/usr/lib/systemd/user \ > > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dnautilus_extension=true > -Dmodules_path=/usr/lib/apache2/modules/ > -Dsystemduserunitdir=/usr/lib/systemd/user > The Meson build system > Version: 0.61.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: gnome-user-share > Project version: 3.34.0 > C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) > 11.2.0") > C linker for the host machine: cc ld.bfd 2.38 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Run-time dependency gio-2.0 found: YES 2.70.3 > Run-time dependency gio-unix-2.0 found: YES 2.70.3 > Run-time dependency glib-2.0 found: YES 2.70.3 > Run-time dependency gtk+-3.0 found: YES 3.24.31 > Program apache2 found: YES (/usr/sbin/apache2) > Checking for function "socket" : YES > Run-time dependency libselinux found: YES 3.3 > Checking for function "is_selinux_enabled" with dependency libselinux: YES > Run-time dependency libnautilus-extension found: YES 41.2 > Message: installing nautilus plugin in: > /usr/lib/x86_64-linux-gnu/nautilus/extensions-3.0 > Configuring gnome-user-share-webdav.desktop.in using configuration > > ../data/meson.build:9:5: ERROR: Function does not take positional arguments. > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2022-02-12T22:49:30.182768 > Main binary: /usr/bin/python3 > Build Options: -Dnautilus_extension=true > -Dmodules_path=/usr/lib/apache2/modules/ > -Dsystemduserunitdir=/usr/lib/systemd/user -Dprefix=/usr > -Dlibdir=lib/x86_64-linux-gnu -Dlocalstatedir=/var -Dsysconfdir=/etc > -Dbuildtype=plain -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.61.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: gnome-user-share > Project version: 3.34.0 > Sanity testing C compiler: cc > Is cross compiler: False. > Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 > -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,-z,defs > -Wl,--as-needed > Sanity check compile stdout: > > - > Sanity check compile stderr: > > - > Running test binary command: > /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe > C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) > 11.2.0") > C linker for the host machine: cc ld.bfd 2.38 > Sanity testing C compiler: cc > Is cross compiler: False. > Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 > -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,-z,defs > -Wl,--as-needed > Sanity check compile stdout: > > - > Sanity check compile stderr: > > - > Running test binary command: > /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe > C compiler for the build machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) > 11.2.0") > C linker for the build machine: cc ld.bfd 2.38 > Build machine cpu family: x86_64 > Build machine cpu: x86_64 > Host machine cpu family: x86_64 > Host
Bug#1005603: marked as done (gnome-2048: FTBFS: ../data/meson.build:19:0: ERROR: Function does not take positional arguments.)
Your message dated Mon, 21 Mar 2022 18:33:43 +
with message-id
and subject line Bug#1005603: fixed in gnome-2048 3.38.2-2
has caused the Debian Bug report #1005603,
regarding gnome-2048: FTBFS: ../data/meson.build:19:0: ERROR: Function does not
take positional arguments.
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.)
--
1005603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-2048
Version: 3.38.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 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_configure -- --bindir=games
> cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson ..
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu --bindir=games
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-2048
> Project version: 3.38.2
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16)
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.38
> Vala compiler for the host machine: valac (valac 0.54.6)
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> ../meson.build:12: WARNING: Project targeting '>= 0.37.1' but tried to use
> feature introduced in '0.38.0': python3 module.
> Library posix found: YES
> Library m found: YES
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency gio-2.0 found: YES 2.70.3
> Run-time dependency glib-2.0 found: YES 2.70.3
> Run-time dependency gtk+-3.0 found: YES 3.24.31
> Run-time dependency clutter-1.0 found: YES 1.26.4
> Run-time dependency clutter-gtk-1.0 found: YES 1.8.4
> Run-time dependency gee-0.8 found: YES 0.20.5
> Run-time dependency libgnome-games-support-1 found: YES 1.8.2
> Program appstream-util found: YES (/usr/bin/appstream-util)
> Program desktop-file-validate found: YES (/usr/bin/desktop-file-validate)
>
> ../data/meson.build:19:0: ERROR: Function does not take positional arguments.
>
> A full log can be found at
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
> cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
> ==> meson-logs/meson-log.txt <==
> Build started at 2022-02-12T22:49:27.792759
> Main binary: /usr/bin/python3
> Build Options: -Dprefix=/usr -Dbindir=games -Dlibdir=lib/x86_64-linux-gnu
> -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain
> -Dwrap_mode=nodownload
> Python system: Linux
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-2048
> Project version: 3.38.2
> Sanity testing C compiler: cc
> Is cross compiler: False.
> Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
> -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,-z,defs
> Sanity check compile stdout:
>
> -
> Sanity check compile stderr:
>
> -
> Running test binary command:
> /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16)
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.38
> Running compile:
> Working directory: /tmp/tmpk920t7pg
> Command line: valac /tmp/tmpk920t7pg/testfile.vala -C
>
> Code:
> class MesonSanityCheck : Object { }
> Compiler stdout:
>
> Compiler stderr:
>
> Vala compiler for the host machine: valac (valac 0.54.6)
> Sanity testing C compiler: cc
> Is cross compiler: False.
> Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
> -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,-z,defs
> Sanity check compile stdout:
>
> -
> Sanity check compile stderr:
>
> -
> Running test binary command:
> /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe
> C compiler for the build machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16)
> 11.2.0")
> C linker for the build machine: cc ld.bfd 2.38
> Using cached compile:
> Cached command line:
>
> Code:
> class MesonSanityCheck : Object { }
> Cached compiler stdout:
>
>
Bug#1005587: marked as done (gnome-mahjongg: FTBFS: ../data/meson.build:24:0: ERROR: Function does not take positional arguments.)
Your message dated Mon, 21 Mar 2022 18:33:50 +
with message-id
and subject line Bug#1005587: fixed in gnome-mahjongg 1:3.38.3-2
has caused the Debian Bug report #1005587,
regarding gnome-mahjongg: FTBFS: ../data/meson.build:24:0: ERROR: Function does
not take positional arguments.
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.)
--
1005587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005587
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-mahjongg
Version: 1:3.38.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 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_configure -- --bindir=games -Dcompile-schemas=disabled
> -Dupdate-icon-cache=disabled
> cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson ..
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu --bindir=games
> -Dcompile-schemas=disabled -Dupdate-icon-cache=disabled
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-mahjongg
> Project version: 3.38.3
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16)
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.38
> Vala compiler for the host machine: valac (valac 0.54.6)
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency glib-2.0 found: YES 2.70.3
> Run-time dependency gio-2.0 found: YES 2.70.3
> Run-time dependency gtk+-3.0 found: YES 3.24.31
> Run-time dependency librsvg-2.0 found: YES 2.52.5
>
> ../data/meson.build:24:0: ERROR: Function does not take positional arguments.
>
> A full log can be found at
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
> cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
> ==> meson-logs/meson-log.txt <==
> Build started at 2022-02-12T22:37:25.553081
> Main binary: /usr/bin/python3
> Build Options: -Dcompile-schemas=disabled -Dupdate-icon-cache=disabled
> -Dprefix=/usr -Dbindir=games -Dlibdir=lib/x86_64-linux-gnu
> -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain
> -Dwrap_mode=nodownload
> Python system: Linux
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-mahjongg
> Project version: 3.38.3
> Sanity testing C compiler: cc
> Is cross compiler: False.
> Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
> -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,-z,defs
> Sanity check compile stdout:
>
> -
> Sanity check compile stderr:
>
> -
> Running test binary command:
> /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16)
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.38
> Running compile:
> Working directory: /tmp/tmp0iskrsmz
> Command line: valac /tmp/tmp0iskrsmz/testfile.vala -C
>
> Code:
> class MesonSanityCheck : Object { }
> Compiler stdout:
>
> Compiler stderr:
>
> Vala compiler for the host machine: valac (valac 0.54.6)
> Sanity testing C compiler: cc
> Is cross compiler: False.
> Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
> -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,-z,defs
> Sanity check compile stdout:
>
> -
> Sanity check compile stderr:
>
> -
> Running test binary command:
> /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe
> C compiler for the build machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16)
> 11.2.0")
> C linker for the build machine: cc ld.bfd 2.38
> Using cached compile:
> Cached command line:
>
> Code:
> class MesonSanityCheck : Object { }
> Cached compiler stdout:
>
> Cached compiler stderr:
>
> Vala compiler for the build machine: valac (valac 0.54.6)
> Build machine cpu family: x86_64
> Build machine cpu: x86_64
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Target machine cpu family: x86_64
> Target machine cpu: x86_64
>
Processed: Bug#1005542 marked as pending in gnome-tetravex
Processing control commands: > tag -1 pending Bug #1005542 [src:gnome-tetravex] gnome-tetravex: FTBFS: ../data/meson.build:37:2: ERROR: Function does not take positional arguments. Added tag(s) pending. -- 1005542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005542: marked as pending in gnome-tetravex
Control: tag -1 pending Hello, Bug #1005542 in gnome-tetravex reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/gnome-tetravex/-/commit/5e0d3396c607518fc51e50d4ec1f6c81968b5e13 Cherry-pick proposed patch to fix build with latest meson Closes: #1005542 (this message was generated automatically) -- Greetings https://bugs.debian.org/1005542
Bug#1005603: marked as pending in gnome-2048
Control: tag -1 pending Hello, Bug #1005603 in gnome-2048 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/gnome-2048/-/commit/afaa844603eae046df4844a77f74c53617a12186 Cherry-pick proposed patch to fix build with latest meson Closes: #1005603 (this message was generated automatically) -- Greetings https://bugs.debian.org/1005603
Processed: Bug#1005603 marked as pending in gnome-2048
Processing control commands: > tag -1 pending Bug #1005603 [src:gnome-2048] gnome-2048: FTBFS: ../data/meson.build:19:0: ERROR: Function does not take positional arguments. Added tag(s) pending. -- 1005603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005603 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1005587 marked as pending in gnome-mahjongg
Processing control commands: > tag -1 pending Bug #1005587 [src:gnome-mahjongg] gnome-mahjongg: FTBFS: ../data/meson.build:24:0: ERROR: Function does not take positional arguments. Added tag(s) pending. -- 1005587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005587 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005587: marked as pending in gnome-mahjongg
Control: tag -1 pending Hello, Bug #1005587 in gnome-mahjongg reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/gnome-mahjongg/-/commit/6ac7223e740b479de5d7d5f607a507ece2db106a Cherry-pick patch to fix build with latest meson Closes: #1005587 (this message was generated automatically) -- Greetings https://bugs.debian.org/1005587
Processed: Bug#1005590 marked as pending in gnome-user-share
Processing control commands: > tag -1 pending Bug #1005590 [src:gnome-user-share] gnome-user-share: FTBFS: ../data/meson.build:9:5: ERROR: Function does not take positional arguments. Added tag(s) pending. -- 1005590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005590: marked as pending in gnome-user-share
Control: tag -1 pending Hello, Bug #1005590 in gnome-user-share reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/gnome-user-share/-/commit/30c680d6ace2203f38a31227f71e274a4f133943 Cherry-pick patch to fix build with latest meson Closes: #1005590 (this message was generated automatically) -- Greetings https://bugs.debian.org/1005590
Bug#1007843: FTBFS with nodejs experimental/14.19.0
On Mon, Mar 21, 2022 at 4:27 PM PaulLiu wrote: > > Question: is this package useful ? No reverse dependencies in Debian, no > > new version for 2 years even if there are 116 open bugs, low and > > decreasing weekly downloads > > Hi Yadd, > > This package is used by me for a personal project. That project is not worth > being packed in Debian. I think opencv is quite a leaf library that is used > by users to make their own customized project. > > I picked this library just because it works. There are some other nodejs > opencv bindings but they have different problems that need to be solved for > packaging in Debian. If you have any better replacement I can package it and > migrate my personal project to it. > > I think I can migrate the deprecated API calls to "Maybe" ones and fix this > bug. I'll do it soon. > > Hi, you're probably going to postpone the inevitable: opencv is now being packaged as a webassembly, in another project. Maybe you could use that other project directly (through npm) instead ? If you plan to really do something for this package, i suggest porting it to napi (the C interface), much easier to deal with in the long term.
Processed: [bts-link] source package src:ldc
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:ldc > # 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 #1000919 (http://bugs.debian.org/1000919) > # Bug title: ldc: FTBFS with llvm-toolchain-13 > # * https://github.com/ldc-developers/ldc/pull/3842 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1000919 + fixed-upstream Bug #1000919 [src:ldc] ldc: FTBFS with llvm-toolchain-13 Added tag(s) fixed-upstream. > usertags 1000919 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package sane-backends
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package sane-backends > # 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 #993350 (http://bugs.debian.org/993350) > # Bug title: sane-epson2: unable to start scanner (Perfection 1650) > # * https://gitlab.com/sane-project/backends/-/issues/445 > # * remote status changed: (?) -> closed > # * closed upstream > tags 993350 + fixed-upstream Bug #993350 [libsane1] sane-epson2: unable to start scanner (Perfection 1650) Added tag(s) fixed-upstream. > usertags 993350 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 993350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993350 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:renpy
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:renpy > # 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 #938351 (http://bugs.debian.org/938351) > # Bug title: renpy: Python2 removal in sid/bullseye > # * https://github.com/renpy/renpy/issues/1098 > # * remote status changed: open -> closed > # * closed upstream > tags 938351 + fixed-upstream Bug #938351 [src:renpy] renpy: Python2 removal in sid/bullseye Added tag(s) fixed-upstream. > usertags 938351 - status-open Usertags were: status-open. There are now no usertags set. > usertags 938351 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 938351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006102: marked as done (txtorcon: FTBFS: tests failed)
Your message dated Mon, 21 Mar 2022 16:51:26 + with message-id and subject line Bug#1006102: fixed in txtorcon 22.0.0-1 has caused the Debian Bug report #1006102, regarding txtorcon: FTBFS: tests failed 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.) -- 1006102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: txtorcon Version: 20.0.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > PYTHONPATH=. trial3 --reporter=text test > ./<>/txtorcon/onion.py:156: > UserWarning: Onions service directory > (test.test_controller/FilesystemOnionFactoryTests/test_happy_path/g5n3qgjr/temp) > is relative and has been resolved to > '/<>/_trial_temp/test.test_controller/FilesystemOnionFactoryTests/test_happy_path/g5n3qgjr/temp' > ../<>/txtorcon/onion.py:156: > UserWarning: Onions service directory > (test.test_endpoints/EndpointTests/test_basic_auth/fb__tuyd/temp) is relative > and has been resolved to > '/<>/_trial_temp/test.test_endpoints/EndpointTests/test_basic_auth/fb__tuyd/temp' > ./<>/txtorcon/onion.py:156: UserWarning: Onions service > directory > (test.test_endpoints/EndpointTests/test_explit_dir_not_readable_ver/ccd70tcc/temp) > is relative and has been resolved to > '/<>/_trial_temp/test.test_endpoints/EndpointTests/test_explit_dir_not_readable_ver/ccd70tcc/temp' > ../<>/txtorcon/onion.py:156: UserWarning: Onions service > directory > (test.test_endpoints/EndpointTests/test_multiple_disk/1pmqwjhn/temp) is > relative and has been resolved to > '/<>/_trial_temp/test.test_endpoints/EndpointTests/test_multiple_disk/1pmqwjhn/temp' > ../<>/txtorcon/onion.py:156: > UserWarning: Onions service directory > (test.test_endpoints/EndpointTests/test_stealth_auth/1a0wt5bs/temp) is > relative and has been resolved to > '/<>/_trial_temp/test.test_endpoints/EndpointTests/test_stealth_auth/1a0wt5bs/temp' > .../<>/txtorcon/onion.py:156: UserWarning: Onions service > directory > (test.test_endpoints/EndpointTests/test_system_tor_explit_dir_not_e/vvk145cn/temp) > is relative and has been resolved to > '/<>/_trial_temp/test.test_endpoints/EndpointTests/test_system_tor_explit_dir_not_e/vvk145cn/temp' > ./<>/txtorcon/onion.py:156: UserWarning: Onions service > directory > (test.test_endpoints/EndpointTests/test_system_tor_explit_dir_not_r/iur_ai_c/temp) > is relative and has been resolved to > '/<>/_trial_temp/test.test_endpoints/EndpointTests/test_system_tor_explit_dir_not_r/iur_ai_c/temp' > ./<>/txtorcon/onion.py:156: UserWarning: Onions service > directory > (test.test_endpoints/EndpointTests/test_system_tor_explit_dir_not_r/0wucd1m4/temp) > is relative and has been resolved to > '/<>/_trial_temp/test.test_endpoints/EndpointTests/test_system_tor_explit_dir_not_r/0wucd1m4/temp' > ../<>/txtorcon/onion.py:156: > UserWarning: Onions service directory > (test.test_onion/OnionServiceTest/test_dir_ioerror/9aunebf9/temp) is relative > and has been resolved to > '/<>/_trial_temp/test.test_onion/OnionServiceTest/test_dir_ioerror/9aunebf9/temp' > ./<>/txtorcon/onion.py:156: UserWarning: Onions service > directory > (test.test_onion/OnionServiceTest/test_dir_ioerror_v3/krj1vt1d/temp) is > relative and has been resolved to > '/<>/_trial_temp/test.test_onion/OnionServiceTest/test_dir_ioerror_v3/krj1vt1d/temp' > ./<>/txtorcon/onion.py:156: > UserWarning: Onions service directory > (test.test_onion/OnionServiceTest/test_old_tor_version/51fxp6pb/temp) is > relative and has been resolved to > '/<>/_trial_temp/test.test_onion/OnionServiceTest/test_old_tor_version/51fxp6pb/temp' > ./<>/txtorcon/onion.py:156: UserWarning: Onions service > directory > (test.test_onion/OnionServiceTest/test_prop224_private_key/oldzz6yk/temp) is > relative and has been resolved to > '/<>/_trial_temp/test.test_onion/OnionServiceTest/test_prop224_private_key/oldzz6yk/temp' > ./<>/txtorcon/onion.py:156: UserWarning: Onions service > directory (test.test_onion/OnionServiceTest/test_set_dir/3lq964u2/temp) is > relative and has been resolved to > '/<>/_trial_temp/test.test_onion/OnionServiceTest/test_set_dir/3lq964u2/temp' >
Processed: found 1007890 in 1.0.5+dfsg-4, found 1007890 in 0.5.6-2, reassign 1002332 to fish, affects 1002332 ...
Processing commands for cont...@bugs.debian.org:
> found 1007890 1.0.5+dfsg-4
Bug #1007890 [python3-nbclient,src:theano] FTBFS: No module named
'ipython_genutils'
There is no source info for the package 'python3-nbclient' at version
'1.0.5+dfsg-4' with architecture ''
Marked as found in versions theano/1.0.5+dfsg-4.
> found 1007890 0.5.6-2
Bug #1007890 [python3-nbclient,src:theano] FTBFS: No module named
'ipython_genutils'
The source 'theano' and version '0.5.6-2' do not appear to match any binary
packages
Marked as found in versions theano/0.5.6-2 and nbclient/0.5.6-2.
> reassign 1002332 fish 3.3.1+ds-2
Bug #1002332 {Done: Mo Zhou } [src:python-argcomplete]
python-argcomplete: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p "3.10 3.9" returned exit code 13
Bug reassigned from package 'src:python-argcomplete' to 'fish'.
No longer marked as found in versions python-argcomplete/1.12.3-0.1.
No longer marked as fixed in versions fish/3.3.1+ds-3.
Bug #1002332 {Done: Mo Zhou } [fish] python-argcomplete:
FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9"
returned exit code 13
Marked as found in versions fish/3.3.1+ds-2.
> affects 1002332 + src:python-argcomplete
Bug #1002332 {Done: Mo Zhou } [fish] python-argcomplete:
FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9"
returned exit code 13
Added indication that 1002332 affects src:python-argcomplete
> fixed 1002332 3.3.1+ds-3
Bug #1002332 {Done: Mo Zhou } [fish] python-argcomplete:
FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9"
returned exit code 13
Marked as fixed in versions fish/3.3.1+ds-3.
> notfixed 968402 1.30.2-1
Bug #968402 {Done: Michael Biebl } [network-manager] Cannot
connect in WPA3-sae mode, using WPA2-psk instead
There is no source info for the package 'network-manager' at version '1.30.2-1'
with architecture ''
Unable to make a source version for version '1.30.2-1'
No longer marked as fixed in versions 1.30.2-1.
> fixed 968402 1.30.6-1
Bug #968402 {Done: Michael Biebl } [network-manager] Cannot
connect in WPA3-sae mode, using WPA2-psk instead
Marked as fixed in versions network-manager/1.30.6-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1002332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002332
1007890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007890
968402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968402
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: libnet-ssleay-perl/buster FTBFS and autopkgtest failure with OpenSSL 1.1.1n
Processing control commands: > close -1 1.88-1 Bug #1008055 [src:libnet-ssleay-perl] libnet-ssleay-perl/buster FTBFS and autopkgtest failure with OpenSSL 1.1.1n Marked as fixed in versions libnet-ssleay-perl/1.88-1. Bug #1008055 [src:libnet-ssleay-perl] libnet-ssleay-perl/buster FTBFS and autopkgtest failure with OpenSSL 1.1.1n Marked Bug as done -- 1008055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008055: libnet-ssleay-perl/buster FTBFS and autopkgtest failure with OpenSSL 1.1.1n
Source: libnet-ssleay-perl Version: 1.85-2 Severity: serious Tags: ftbfs Forwarded: https://github.com/radiator-software/p5-net-ssleay/commit/a3d40e9a7d89903be20de7c0973da90ebb3293bf Control: close -1 1.88-1 https://ci.debian.net/data/autopkgtest/oldstable/amd64/libn/libnet-ssleay-perl/20203562/log.gz ... Test Summary Report --- t/local/40_npn_support.t (Wstat: 512 Tests: 7 Failed: 4) Failed tests: 2-3, 5-6 Non-zero exit status: 2 t/local/41_alpn_support.t(Wstat: 256 Tests: 6 Failed: 3) Failed tests: 2-3, 5 Non-zero exit status: 1 t/local/42_info_callback.t (Wstat: 512 Tests: 2 Failed: 2) Failed tests: 1-2 Non-zero exit status: 2 Files=32, Tests=2993, 5 wallclock secs ( 0.25 usr 0.07 sys + 4.37 cusr 0.51 csys = 5.20 CPU) Result: FAIL
Bug#1007843: FTBFS with nodejs experimental/14.19.0
> Question: is this package useful ? No reverse dependencies in Debian, no > new version for 2 years even if there are 116 open bugs, low and > decreasing weekly downloads Hi Yadd, This package is used by me for a personal project. That project is not worth being packed in Debian. I think opencv is quite a leaf library that is used by users to make their own customized project. I picked this library just because it works. There are some other nodejs opencv bindings but they have different problems that need to be solved for packaging in Debian. If you have any better replacement I can package it and migrate my personal project to it. I think I can migrate the deprecated API calls to "Maybe" ones and fix this bug. I'll do it soon. Yours, Paul
Bug#1008052: python-pecan FTBFS: build tests fail with python3.10
Package: python-pecan
Version: 1.3.3-4
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to fix the build tests when
using python3.10:
* debian/patches/fix-tests-on-python-3.10.patch: Pull in upstream patch to
fix build tests on python3.10 (LP: #1965132).
Thanks,
Nick
diff -Nru python-pecan-1.3.3/debian/patches/fix-tests-on-python-3.10.patch
python-pecan-1.3.3/debian/patches/fix-tests-on-python-3.10.patch
--- python-pecan-1.3.3/debian/patches/fix-tests-on-python-3.10.patch
1969-12-31 19:00:00.0 -0500
+++ python-pecan-1.3.3/debian/patches/fix-tests-on-python-3.10.patch
2022-03-18 15:41:48.0 -0400
@@ -0,0 +1,87 @@
+Description: Fix tests to work on Python 3.10
+Origin: upstream,
https://github.com/pecan/pecan/pull/131/commits/f189d0eafbaacc5b5093bb8854cd2068e22b6c08
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/python-pecan/+bug/1965132
+---
+From f189d0eafbaacc5b5093bb8854cd2068e22b6c08 Mon Sep 17 00:00:00 2001
+From: Evangelos Foutras
+Date: Wed, 8 Dec 2021 07:01:16 +0200
+Subject: [PATCH] Fix tests to work on Python 3.10
+
+Python 3.10 adds the class name to the exception; adjust four tests
+affected by this change.
+
+Fixes: https://github.com/pecan/pecan/issues/130
+---
+ pecan/tests/test_base.py | 18 +-
+ pecan/tests/test_no_thread_locals.py | 20 ++--
+ 2 files changed, 27 insertions(+), 11 deletions(-)
+--- a/pecan/tests/test_base.py
b/pecan/tests/test_base.py
+@@ -456,8 +456,12 @@
+ assert type(ex) == TypeError
+ assert ex.args[0] in (
+ "index() takes exactly 2 arguments (1 given)",
+-"index() missing 1 required positional argument: 'id'"
+-) # this messaging changed in Python 3.3
++"index() missing 1 required positional argument: 'id'",
++(
++"TestControllerArguments.app_..RootController."
++"index() missing 1 required positional argument: 'id'"
++),
++) # this messaging changed in Python 3.3 and again in Python 3.10
+
+ def test_single_argument(self):
+ r = self.app_.get('/1')
+@@ -994,9 +998,13 @@
+ except Exception as ex:
+ assert type(ex) == TypeError
+ assert ex.args[0] in (
+-"eater() takes at least 2 arguments (1 given)",
+-"eater() missing 1 required positional argument: 'id'"
+-) # this messaging changed in Python 3.3
++"eater() takes exactly 2 arguments (1 given)",
++"eater() missing 1 required positional argument: 'id'",
++(
++"TestControllerArguments.app_..RootController."
++"eater() missing 1 required positional argument: 'id'"
++),
++) # this messaging changed in Python 3.3 and again in Python 3.10
+
+ def test_one_remainder(self):
+ r = self.app_.get('/eater/1')
+--- a/pecan/tests/test_no_thread_locals.py
b/pecan/tests/test_no_thread_locals.py
+@@ -361,9 +361,13 @@
+ except Exception as ex:
+ assert type(ex) == TypeError
+ assert ex.args[0] in (
+-"index() takes exactly 4 arguments (3 given)",
+-"index() missing 1 required positional argument: 'id'"
+-) # this messaging changed in Python 3.3
++"index() takes exactly 2 arguments (1 given)",
++"index() missing 1 required positional argument: 'id'",
++(
++"TestControllerArguments.app_..RootController."
++"index() missing 1 required positional argument: 'id'"
++),
++) # this messaging changed in Python 3.3 and again in Python 3.10
+
+ def test_single_argument(self):
+ r = self.app_.get('/1')
+@@ -763,9 +767,13 @@
+ except Exception as ex:
+ assert type(ex) == TypeError
+ assert ex.args[0] in (
+-"eater() takes at least 4 arguments (3 given)",
+-"eater() missing 1 required positional argument: 'id'"
+-) # this messaging changed in Python 3.3
++"eater() takes exactly 2 arguments (1 given)",
++"eater() missing 1 required positional argument: 'id'",
++(
++"TestControllerArguments.app_..RootController."
++"eater() missing 1 required positional argument: 'id'"
++),
++) # this messaging changed in Python 3.3 and again in Python 3.10
+
+ def test_one_remainder(self):
+ r = self.app_.get('/eater/1')
diff -Nru python-pecan-1.3.3/debian/patches/series
Bug#997847: golang-github-hashicorp-go-slug: autopkgtest regression: testdata/archive-dir: no such file or directory
Package: golang-github-hashicorp-go-slug
Version: 0.7.0-1
Followup-For: Bug #997847
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Control: tags -1 patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to fix autopkgtest
regressions:
* debian/patches/disable-strange-tests.patch: Refresh the patch to include
new tests that try to access testdata/archive-dir. This fixes an
autopkgtest failure (LP: #1965429).
Thanks,
Nick
diff -Nru
golang-github-hashicorp-go-slug-0.7.0/debian/patches/disable-strange-tests.patch
golang-github-hashicorp-go-slug-0.7.0/debian/patches/disable-strange-tests.patch
---
golang-github-hashicorp-go-slug-0.7.0/debian/patches/disable-strange-tests.patch
2021-10-05 14:31:50.0 -0400
+++
golang-github-hashicorp-go-slug-0.7.0/debian/patches/disable-strange-tests.patch
2022-03-17 14:36:15.0 -0400
@@ -1,11 +1,20 @@
Description: some tests require files in paths that are not compatible with
Debian packaging
in order to make life easier, these tests are disabled
Author: Thorsten Alteholz
-Index: golang-github-hashicorp-go-slug-0.7.0/slug_test.go
-===
golang-github-hashicorp-go-slug-0.7.0.orig/slug_test.go2021-10-06
06:10:32.879315260 +
-+++ golang-github-hashicorp-go-slug-0.7.0/slug_test.go 2021-10-06
06:13:39.728065809 +
-@@ -14,231 +14,231 @@
+--- a/slug_test.go
b/slug_test.go
+@@ -2,10 +2,8 @@
+
+ import (
+ "archive/tar"
+- "bytes"
+ "compress/gzip"
+ "errors"
+- "io"
+ "io/ioutil"
+ "os"
+ "path/filepath"
+@@ -14,338 +12,338 @@
"testing"
)
@@ -234,6 +243,113 @@
- t.Fatalf("\nexpect:\n%#v\n\nactual:\n%#v", expect, meta)
- }
-}
+-
+-func TestPackWithoutIgnoring(t *testing.T) {
+- slug := bytes.NewBuffer(nil)
+-
+- // By default NewPacker() creates a Packer that does not use
+- // .terraformignore or dereference symlinks.
+- p, err := NewPacker()
+- if err != nil {
+- t.Fatalf("err: %v", err)
+- }
+-
+- meta, err := p.Pack("testdata/archive-dir", slug)
+- if err != nil {
+- t.Fatalf("err: %v", err)
+- }
+-
+- gzipR, err := gzip.NewReader(slug)
+- if err != nil {
+- t.Fatalf("err: %v", err)
+- }
+-
+- tarR := tar.NewReader(gzipR)
+- var (
+- fileList []string
+- slugSize int64
+- )
+-
+- for {
+- hdr, err := tarR.Next()
+- if err == io.EOF {
+- break
+- }
+- if err != nil {
+- t.Fatalf("err: %v", err)
+- }
+-
+- fileList = append(fileList, hdr.Name)
+- if hdr.Typeflag == tar.TypeReg || hdr.Typeflag == tar.TypeRegA {
+- slugSize += hdr.Size
+- }
+- }
+-
+- // baz.txt would normally be ignored, but should not be
+- var bazFound bool
+- for _, file := range fileList {
+- if file == "baz.txt" {
+- bazFound = true
+- }
+- }
+- if !bazFound {
+- t.Fatal("expected file baz.txt to be present, but not found")
+- }
+-
+- // .terraform/file.txt would normally be ignored, but should not be
+- var dotTerraformFileFound bool
+- for _, file := range fileList {
+- if file == ".terraform/file.txt" {
+- dotTerraformFileFound = true
+- }
+- }
+- if !dotTerraformFileFound {
+- t.Fatal("expected file .terraform/file.txt to be present, but
not found")
+- }
+-
+- // Check the metadata
+- expect := {
+- Files: fileList,
+- Size: slugSize,
+- }
+- if !reflect.DeepEqual(meta, expect) {
+- t.Fatalf("\nexpect:\n%#v\n\nactual:\n%#v", expect, meta)
+- }
+-}
+-
+-func TestUnpack(t *testing.T) {
+- // First create the slug file so we can try to unpack it.
+- slug := bytes.NewBuffer(nil)
+-
+- if _, err := Pack("testdata/archive-dir", slug, true); err != nil {
+- t.Fatalf("err: %v", err)
+- }
+-
+- // Create a dir to unpack into.
+- dst, err := ioutil.TempDir("", "slug")
+- if err != nil {
+- t.Fatalf("err: %v", err)
+- }
+- defer os.RemoveAll(dst)
+-
+- // Now try unpacking it.
+- if err := Unpack(slug, dst); err != nil {
+- t.Fatalf("err: %v", err)
+- }
+-
+- // Verify all the files
+- verifyFile(t, filepath.Join(dst, "foo.txt"), 0, "foo\n")
+- verifyFile(t, filepath.Join(dst, "bar.txt"), 0, "bar\n")
+- verifyFile(t, filepath.Join(dst, "sub", "bar.txt"), os.ModeSymlink,
"../bar.txt")
+- verifyFile(t, filepath.Join(dst, "sub", "zip.txt"), 0, "zip\n")
+-
+- // Check that we can
Processed: Re: pktstat FTBFS: error: format not a string literal and no format arguments [-Werror=format-security]
Processing control commands: > tags -1 patch Bug #995624 [src:pktstat] pktstat FTBFS: error: format not a string literal and no format arguments [-Werror=format-security] Ignoring request to alter tags of bug #995624 to the same tags previously set -- 995624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995624 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995624: pktstat FTBFS: error: format not a string literal and no format arguments [-Werror=format-security]
Package: pktstat
Version: 1.8.5-7
Followup-For: Bug #995624
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Control: tags -1 patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to fix the pktstat build.
* debian/patches/0001-Fix-format-string-error-with-recent-ncurses.patch:
Add patch to fix -Werror=format-security build error (LP: #1965174).
Thanks,
Nick
diff -Nru
pktstat-1.8.5/debian/patches/0001-Fix-format-string-error-with-recent-ncurses.patch
pktstat-1.8.5/debian/patches/0001-Fix-format-string-error-with-recent-ncurses.patch
---
pktstat-1.8.5/debian/patches/0001-Fix-format-string-error-with-recent-ncurses.patch
1969-12-31 19:00:00.0 -0500
+++
pktstat-1.8.5/debian/patches/0001-Fix-format-string-error-with-recent-ncurses.patch
2022-03-17 13:23:20.0 -0400
@@ -0,0 +1,26 @@
+Description: Fix format string error with recent ncurses
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995624
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/pktstat/+bug/1965174
+Author: Sven Joachim
+Last-Update: 2022-03-16
+---
+From f3368493fe0365f7f37064fb0ae5fd1fba50fc36 Mon Sep 17 00:00:00 2001
+From: Sven Joachim
+Date: Thu, 14 Oct 2021 19:40:32 +0200
+Subject: [PATCH] Fix format string error with recent ncurses
+
+---
+ display.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+--- a/display.c
b/display.c
+@@ -669,7 +669,7 @@
+ attron(A_REVERSE);
+ printw("%c", h->name[0]);
+ attroff(A_UNDERLINE);
+- printw((char *)h->name + 1);
++ printw("%s", (char *)h->name + 1);
+ attrset(0);
+ printw(" ");
+ }
diff -Nru pktstat-1.8.5/debian/patches/series
pktstat-1.8.5/debian/patches/series
--- pktstat-1.8.5/debian/patches/series 2021-08-24 15:20:56.0 -0400
+++ pktstat-1.8.5/debian/patches/series 2022-03-16 15:17:07.0 -0400
@@ -1 +1,2 @@
10-CVE-2013-0350-bug-701211-no-tmp.patch
+0001-Fix-format-string-error-with-recent-ncurses.patch
Processed: Re: golang-github-hashicorp-go-slug: autopkgtest regression: testdata/archive-dir: no such file or directory
Processing control commands: > tags -1 patch Bug #997847 [src:golang-github-hashicorp-go-slug] golang-github-hashicorp-go-slug: autopkgtest regression: testdata/archive-dir: no such file or directory Added tag(s) patch. -- 997847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997847 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008041: marked as done (wmforecast: invalid Uploaders field: missing comma between Doug Torrance and Andreas Metzler)
Your message dated Mon, 21 Mar 2022 12:10:45 + with message-id and subject line Bug#1008041: fixed in wmforecast 1.8.1-1 has caused the Debian Bug report #1008041, regarding wmforecast: invalid Uploaders field: missing comma between Doug Torrance and Andreas Metzler 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.) -- 1008041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wmforecast Version: 1.8-1 Severity: serious Usertags: uploaders wmforecast 1.8-1 introduced an invalid Uploaders field, that is missing a comma between Doug Torrance and Andreas Metzler. $ apt-cache showsrc wmforecast | grep -E '^$|^Version|^Uploaders' Version: 1.7-1.1 Uploaders: Doug Torrance , Andreas Metzler Version: 1.8-1 Uploaders: Doug Torrance Andreas Metzler According to Debian policy 5.6.3 the Uploaders field must separate individual uploaders using commas: List of the names and email addresses of co-maintainers of the package, if any. ... The format of each entry is the same as that of the Maintainer field, and multiple entries must be comma separated. https://www.debian.org/doc/debian-policy/ch-controlfields.html#uploaders This is causing the DDPO and BLS cron jobs to send error mails, please fix it as soon as possible. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: wmforecast Source-Version: 1.8.1-1 Done: Doug Torrance We believe that the bug you reported is fixed in the latest version of wmforecast, 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 1008...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Doug Torrance (supplier of updated wmforecast 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: Mon, 21 Mar 2022 07:34:11 -0400 Source: wmforecast Built-For-Profiles: noudeb Architecture: source Version: 1.8.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Window Maker Team Changed-By: Doug Torrance Closes: 1008041 Changes: wmforecast (1.8.1-1) unstable; urgency=medium . * New upstream release. * debian/control - Use a comma in Uploaders (Closes: #1008041). Checksums-Sha1: d585e8f9c9897e0fe6a5669e4773f1437d2f3b4b 2324 wmforecast_1.8.1-1.dsc 15f4407c857aa5a37faf7606074575bd8426e66f 150855 wmforecast_1.8.1.orig.tar.gz 025f78adad027930d9896e81a8a683e29c34a4db 833 wmforecast_1.8.1.orig.tar.gz.asc a35f93e58e7d63cd5f15c2a915b5d982759c627d 15112 wmforecast_1.8.1-1.debian.tar.xz b4bc51e69874ca2fabf26042eb2fea18b0fd1d1c 14105 wmforecast_1.8.1-1_source.buildinfo Checksums-Sha256: c50f396c49d8a3f8cf44af3d3534cb20d9e49d0f5f0ec68f81e7e77c9c216367 2324 wmforecast_1.8.1-1.dsc fd80ccd0d3924abe14dba13081c1aa8f993f39d4da1f99ee323753390e6c1c5f 150855 wmforecast_1.8.1.orig.tar.gz 0b9199f663a4e7858902e649b5162e0423b0ae4d21b3417b0b20c75d45e410c8 833 wmforecast_1.8.1.orig.tar.gz.asc f612c25d8f30d9bfc91fa33aa531ab57eb3941ba6c74bce4e3b834c43d9508be 15112 wmforecast_1.8.1-1.debian.tar.xz 3654daa42ca44d1a44c31ba24180d538f2f1af3221caeb4c3353443eed7b126a 14105 wmforecast_1.8.1-1_source.buildinfo Files: 3c3ec6b16ce84195e976aa327871fc89 2324 utils optional wmforecast_1.8.1-1.dsc fa4c75910db0eafb75de2aebadf9e68c 150855 utils optional wmforecast_1.8.1.orig.tar.gz 40057ef0f0f1ee43e3c4ab6862341b7b 833 utils optional wmforecast_1.8.1.orig.tar.gz.asc a0f3e691616d6bce9c1030d54056c2d0 15112 utils optional wmforecast_1.8.1-1.debian.tar.xz be0eeda7fe4cbb9bff5ae01a39fb9c69 14105 utils optional wmforecast_1.8.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCgAzFiEEupghwS4HiU+y5K0AkdxKd57FyRAFAmI4ZF8VHGR0b3JyYW5j ZUBkZWJpYW4ub3JnAAoJEJHcSneexckQxcwP/1iYTl6WbdNkQ3WjnHZoYqrpkpSM 99paQtop3tR4JY8KylwPnMHU/EsCa6sZGRDeRc9wvM4etcld1KEPYTV0G2rToz2d 8OX+KkBteekab9dlY1+wGgl8ngMWwvvwNSef+z69nTZogvz9JOWshjv8Mq95kzZ+ zOFqLTJEnfnkC8K0AzIkj3z9LDosF0YkWpIiuPgfgDJitvoxRRjNDlyX+a0p8FJE s5qt0LVtgNhYIuUL/Ln6hFzjb7WYFA4j6qdQ1x9NktgFBLEyW0jts3oZ3ig4YL8A
Bug#1008041: wmforecast: invalid Uploaders field: missing comma between Doug Torrance and Andreas Metzler
On Mon 21 Mar 2022 06:28:52 AM EDT, Paul Wise wrote: wmforecast 1.8-1 introduced an invalid Uploaders field, that is missing a comma between Doug Torrance and Andreas Metzler. $ apt-cache showsrc wmforecast | grep -E '^$|^Version|^Uploaders' Version: 1.7-1.1 Uploaders: Doug Torrance , Andreas Metzler Version: 1.8-1 Uploaders: Doug Torrance Andreas Metzler According to Debian policy 5.6.3 the Uploaders field must separate individual uploaders using commas: List of the names and email addresses of co-maintainers of the package, if any. ... The format of each entry is the same as that of the Maintainer field, and multiple entries must be comma separated. https://www.debian.org/doc/debian-policy/ch-controlfields.html#uploaders This is causing the DDPO and BLS cron jobs to send error mails, please fix it as soon as possible. Oops, sorry about introducing this bug with my last upload! I'll upload a new version with a comma here shortly. Doug signature.asc Description: PGP signature
Processed: Bug#1008034 marked as pending in pkg-js-tools
Processing control commands: > tag -1 pending Bug #1008034 [dh-nodejs] ftbfs: bad line in substvars Added tag(s) pending. -- 1008034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008034: marked as pending in pkg-js-tools
Control: tag -1 pending Hello, Bug #1008034 in pkg-js-tools 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/js-team/pkg-js-tools/-/commit/7c0b53fdfc00d6b93bd284601b93fd1032536577 debhelper: fix substvars names Closes: #1008034 (this message was generated automatically) -- Greetings https://bugs.debian.org/1008034
Processed: reassign 1008034 to dh-nodejs, found 1008034 in 0.14.5
Processing commands for cont...@bugs.debian.org: > reassign 1008034 dh-nodejs Bug #1008034 [src:node-chart.js] ftbfs: bad line in substvars Bug reassigned from package 'src:node-chart.js' to 'dh-nodejs'. No longer marked as found in versions node-chart.js/3.7.1+~0.1.9-1. Ignoring request to alter fixed versions of bug #1008034 to the same values previously set > found 1008034 0.14.5 Bug #1008034 [dh-nodejs] ftbfs: bad line in substvars Marked as found in versions pkg-js-tools/0.14.5. > thanks Stopping processing here. Please contact me if you need assistance. -- 1008034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008037: marked as done (FTBFS: No such file or directory at /usr/bin/dh_nodejs_substvars line 21)
Your message dated Mon, 21 Mar 2022 10:51:25 + with message-id and subject line Bug#1008037: fixed in pkg-js-tools 0.14.6 has caused the Debian Bug report #1008037, regarding FTBFS: No such file or directory at /usr/bin/dh_nodejs_substvars line 21 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.) -- 1008037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008037 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sax.js Version: 1.2.4+~1.2.4-1 Severity: serious Tags: ftbfs Justification: fails to build from source This happened during rebuild of this package: dh_nodejs_substvars No such file or directory at /usr/bin/dh_nodejs_substvars line 21. make: *** [debian/rules:8: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Jérémy -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable'), (101, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-5-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: pkg-js-tools Source-Version: 0.14.6 Done: Yadd We believe that the bug you reported is fixed in the latest version of pkg-js-tools, 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 1008...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated pkg-js-tools 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: Mon, 21 Mar 2022 11:20:47 +0100 Source: pkg-js-tools Architecture: source Version: 0.14.6 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1008037 Changes: pkg-js-tools (0.14.6) unstable; urgency=medium . * debhelper: + Don't fail when subsvars were not generated, just warn (Closes: #1008037) Checksums-Sha1: 5d6c75f362c00d7fb1caceff0b289ddef22ad072 2624 pkg-js-tools_0.14.6.dsc 29cdd5e807d3def163a2e0fd3ad285d0ea4db340 73908 pkg-js-tools_0.14.6.tar.xz Checksums-Sha256: f14c13582d30b586ba126f7d05b25a3d8250013e594e08121c4c384b8dd9f22c 2624 pkg-js-tools_0.14.6.dsc a3e592e313da1d7b3a7067da562f4b9740be9a9b74db187d54ddfab1d397792b 73908 pkg-js-tools_0.14.6.tar.xz Files: d53e71aa1e96baa1cb998b35b14845b7 2624 devel optional pkg-js-tools_0.14.6.dsc dfe8ebe7808438afb54cbc8ad76f98f5 73908 devel optional pkg-js-tools_0.14.6.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmI4U+YACgkQ9tdMp8mZ 7un87Q/+KArbFaKKlFWk4ZBXSn3soFin1cFyJJHlyLxJY1QVfr7z+mHpNOiW44Dq zqdUTqq0e2utKVE5Iwf5mk1Ka+ELMwEJnKEOcNGS00+Jdr4QGDZXZsnQ7QR47ugQ T93E6zFKma8vALyAuUK4FKGJeGrDsEPrCAFvgPQsIJ2LzY9+OEAUKwQ+qcJZJmrv RLmMedIIGv8cdZ3G/h5HjTKv5//lifCcY1tV5wmtfOAkJfTKeaktdJkzFr9wbVlb TriDeHR7qz7rRVj0RMBTM5TMTa1V/AWWOdJ6v7JUfoDLNkEjL363rGDvnD7OA6Bq ArJsmng+OI7xOMKzIyxaUmuB5mHMb1JvZ5e/J81qaAZMjO1TkhbyqV1rTuXJqqRQ MZ4OPg+CnyZY1vuKjOjJ8/bH6z9ZobycXWKsNFg0js9VI1Rqi8lmnwU7Xu7iYJCR EjJ0iih/F1jtVa+VXraXLNOlh6pm4uNgyaZJANT6ZYUQRdnsy9SlCWNHFohbnJai S4N+Pbf9eZfwLqhBtQRrXq92jUXQVRrYXcHMzBab1SZktKvL2tfuyrirSJvhoTbD brxczWlyUYlwXUIiOrVTyeGFKzeMF06UqlBqZ8LQjGF9PVsBgz7TERFXBUQybvsY PFUGfe0Rrj3I0ShFXlhk1LIilQxXOpOdEYyt+gwI1SzhDIZzZHk= =pQ6G -END PGP SIGNATURE End Message ---
Bug#1007827: marked as done (asdf-astropy breaks gwcs autopkgtest: cannot import name 'assert_models_equal' from 'asdf_astropy.converters.transform.tests.test_transform')
Your message dated Mon, 21 Mar 2022 10:50:00 + with message-id and subject line Bug#1007827: fixed in gwcs 0.18.1-1 has caused the Debian Bug report #1007827, regarding asdf-astropy breaks gwcs autopkgtest: cannot import name 'assert_models_equal' from 'asdf_astropy.converters.transform.tests.test_transform' 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.) -- 1007827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: asdf-astropy, gwcs Control: found -1 asdf-astropy/0.2.0-1 Control: found -1 gwcs/0.18.0-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of asdf-astropy the autopkgtest of gwcs fails in testing when that autopkgtest is run with the binary packages of asdf-astropy from unstable. It passes when run with only packages from testing. In tabular form: passfail asdf-astropy from testing0.2.0-1 gwcs from testing0.18.0-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of asdf-astropy to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=asdf-astropy https://ci.debian.net/data/autopkgtest/testing/amd64/g/gwcs/20058761/log.gz = test session starts == platform linux -- Python 3.9.10, pytest-6.2.5, py-1.10.0, pluggy-0.13.0 rootdir: /tmp/autopkgtest-lxc.788b562b/downtmp/autopkgtest_tmp plugins: remotedata-0.3.3, openfiles-0.5.0, astropy-header-0.2.0, cov-3.0.0, filter-subpackage-0.1.1, asdf-2.10.1, arraydiff-0.5.0, doctestplus-0.12.0, mock-3.6.1, hypothesis-6.36.0 collected 971 items / 1 error / 970 selected ERRORS ERROR collecting converters/tests/test_wcs.py _ ImportError while importing test module '/usr/lib/python3/dist-packages/gwcs/converters/tests/test_wcs.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.9/importlib/__init__.py:127: in import_module return _bootstrap._gcd_import(name[level:], package, level) /usr/lib/python3/dist-packages/gwcs/converters/tests/test_wcs.py:15: in from asdf_astropy.converters.transform.tests.test_transform import ( # noqa: E402 E ImportError: cannot import name 'assert_models_equal' from 'asdf_astropy.converters.transform.tests.test_transform' (/usr/lib/python3/dist-packages/asdf_astropy/converters/transform/tests/test_transform.py) === short test summary info ERROR converters/tests/test_wcs.py Interrupted: 1 error during collection === 1 error in 1.32s === autopkgtest [06:00:01]: test command1 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: gwcs Source-Version: 0.18.1-1 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of gwcs, 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 1007...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ole Streicher (supplier of updated gwcs 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: Mon, 21 Mar 2022 11:12:45 +0100 Source: gwcs Architecture: source Version: 0.18.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Astro Team Changed-By: Ole Streicher Closes: 1007827 Changes: gwcs (0.18.1-1) unstable; urgency=medium . * New upstream
Bug#1008037: marked as done (FTBFS: No such file or directory at /usr/bin/dh_nodejs_substvars line 21)
Your message dated Mon, 21 Mar 2022 10:39:18 + with message-id and subject line Bug#1008037: fixed in sax.js 1.2.4+~1.2.4-2 has caused the Debian Bug report #1008037, regarding FTBFS: No such file or directory at /usr/bin/dh_nodejs_substvars line 21 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.) -- 1008037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008037 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sax.js Version: 1.2.4+~1.2.4-1 Severity: serious Tags: ftbfs Justification: fails to build from source This happened during rebuild of this package: dh_nodejs_substvars No such file or directory at /usr/bin/dh_nodejs_substvars line 21. make: *** [debian/rules:8: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Jérémy -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable'), (101, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-5-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: sax.js Source-Version: 1.2.4+~1.2.4-2 Done: Yadd We believe that the bug you reported is fixed in the latest version of sax.js, 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 1008...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated sax.js 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: Mon, 21 Mar 2022 11:08:25 +0100 Source: sax.js Architecture: source Version: 1.2.4+~1.2.4-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1008037 Changes: sax.js (1.2.4+~1.2.4-2) unstable; urgency=medium . * Team upload * Fix test for tap >= 15 (--no-cov) * Use dh-sequence-nodejs auto install (Closes: #1008037) Checksums-Sha1: c9062fb244f18ec06c63300a80528935ea66aa19 2416 sax.js_1.2.4+~1.2.4-2.dsc 222ce78510c6f3e955f8b28879b6dba072211918 5012 sax.js_1.2.4+~1.2.4-2.debian.tar.xz Checksums-Sha256: 142e13e6b234edfe521d2973b42f034319504657df4089eaa9563b2af4b8849f 2416 sax.js_1.2.4+~1.2.4-2.dsc c770ef4a511bbc7c5be2b1c472a762b252c61813fce865ba18fbc69181ca0927 5012 sax.js_1.2.4+~1.2.4-2.debian.tar.xz Files: d20c29b1dddff6d7737e1a81a4195ff4 2416 javascript optional sax.js_1.2.4+~1.2.4-2.dsc 81b97308c1cd4172c899bc47e2ed8dd5 5012 javascript optional sax.js_1.2.4+~1.2.4-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmI4TvIACgkQ9tdMp8mZ 7ulcJw/+M5ZVRytY0aD6IY5XF4exrSJ20UpSJObSxU3GVxpKW71BKdh0kRMuOLpK j4lvIKDmAMSO6J8ISqN+1rICY9PTo10XhiFbLAxo+U7ONMusbrEGwDD406TCqhT5 ZR4SYKUXSbigZl+VEuW2ACrhDPbxu6l9HrEnqdPwcABB+SBaS81SIVdQAvblo9b4 zikKjBBFKa7TDugr5FkI1LUGe9OEa23zCsZEcSUzQoh55erhLwuTMw9dwgYiMzNr 1wMeqb1R/OWx0jiXS3Ez+Cs13hHwbXSwYw/ztynvd6hMJXBfSmDZHEHRmFDOMXTp 2FPhCZa0tGSYrZL8JxV+sT4USuCvK9YnM1PTCxcPT134l/Ztqstz7oN1e2J/m3OF KMIpFymNvErQV0LtqciYcMsIQBbExncVwYookbmFv/5NBlfzivgwsyxRWCfFDvjH jthcd9Hdl7eVdg86EhUB4fU2LFQMRh948KcShayoMSCAxK2dUBrh992HC4F/qFfW AFnYWi//1rNQ/6AHHMsFAiacmZcUBBhKqil2w1AKiF0M5m2+Qc8DdAxhCJZw90lw S7vtuTDKOm6dc9COBTRUUnFb6XuzoMiipTfV7+5PVLIpWr+tQwBfp1C/5J4fDalk 2tfxTzyEbbKiNlAym9eMPLx2kbpH6RXUPHsytFCSAh8ZI1CLjgM= =Q5KX -END PGP SIGNATURE End Message ---
Bug#1008041: wmforecast: invalid Uploaders field: missing comma between Doug Torrance and Andreas Metzler
Source: wmforecast Version: 1.8-1 Severity: serious Usertags: uploaders wmforecast 1.8-1 introduced an invalid Uploaders field, that is missing a comma between Doug Torrance and Andreas Metzler. $ apt-cache showsrc wmforecast | grep -E '^$|^Version|^Uploaders' Version: 1.7-1.1 Uploaders: Doug Torrance , Andreas Metzler Version: 1.8-1 Uploaders: Doug Torrance Andreas Metzler According to Debian policy 5.6.3 the Uploaders field must separate individual uploaders using commas: List of the names and email addresses of co-maintainers of the package, if any. ... The format of each entry is the same as that of the Maintainer field, and multiple entries must be comma separated. https://www.debian.org/doc/debian-policy/ch-controlfields.html#uploaders This is causing the DDPO and BLS cron jobs to send error mails, please fix it as soon as possible. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#978882: marked as done (pike8.0: ftbfs with autoconf 2.70)
Your message dated Mon, 21 Mar 2022 10:22:26 + with message-id and subject line Bug#978882: fixed in pike8.0 8.0.1116-1.1 has caused the Debian Bug report #978882, regarding pike8.0: ftbfs with autoconf 2.70 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.) -- 978882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pike8.0 Version: 8.0.702-1 Severity: normal Tags: sid bookworm User: d...@debian.org Usertags: ftbfs-ac270 [This bug report is not targeted to the upcoming bullseye release] The package fails to build in a test rebuild on at least amd64 with autoconf 2.70, but succeeds to build with autoconf 2.69. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://qa-logs.debian.net/2020/09/26.ac270/pike8.0_8.0.702-1_unstable_ac270.log The last lines of the build log are at the end of this report. To build with autoconf 2.70, please install the autoconf package from experimental: apt-get -t=experimental install autoconf [...] Running autoconf in ./post_modules/_ADT Running autoconf in ./post_modules/Unicode Running autoconf in ./post_modules/ZXID Running autoconf in ./post_modules/Shuffler Running autoconf in ./post_modules/_Image_WebP Running autoconf in ./post_modules/_Sass Running autoconf in ./post_modules/_Regexp_PCRE /usr/bin/make force_configure CONFIGUREARGS="--with-cdebug --with-copt --without-rtldebug --with-cflags='`dpkg-buildflags --get CFLAGS`' --with-cppflags='`dpkg-buildflags --get CPPFLAGS`' --with-ldflags='`dpkg-buildflags --get LDFLAGS`' --prefix=/usr --with-bignums --with-gmp --with-poll --with-zlib --with-freetype --without-ttflib --with-libnettle --without-sybase --without-java --with-odbc --with-sane --with-postgres --with-postgres-include-dir=`pg_config --includedir` --with-libpq-dir=/usr/lib --with-sass --with-sqlite --without-com --without-ffmpeg --without-fftw --without-libpdf --without-libpanda --without-GTK --without-GTK2 --without-bundles --without-oracle --without-dvb --disable-rpath --without-vcdiff --without-zxid --disable-smartlink_binary --without-machine-code " make[1]: Entering directory '/<>' builddir="build/`if [ -n \"$PIKE_BUILD_OS\" ]; then echo \"$PIKE_BUILD_OS\"; else uname -s -r -m|sed \"s/ /-/g\"|tr \"[A-Z]\" \"[a-z]\"|tr \"/()\" \"___\"; fi`"; rm -f "$builddir/Makefile" Creating build... Creating build/linux-4.19.0-6-cloud-amd64-x86_64... Configure arguments: --with-cdebug --with-copt --without-rtldebug --with-cflags='-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security' --with-cppflags='-Wdate-time -D_FORTIFY_SOURCE=2 -DDEBIAN' --with-ldflags='-Wl,-z,relro -Wl,--as-needed' --prefix=/usr --with-bignums --with-gmp --with-poll --with-zlib --with-freetype --without-ttflib --with-libnettle --without-sybase --without-java --with-odbc --with-sane --with-postgres --with-postgres-include-dir=/usr/include/postgresql --with-libpq-dir=/usr/lib --with-sass --with-sqlite --without-com --without-ffmpeg --without-fftw --without-libpdf --without-libpanda --without-GTK --without-GTK2 --without-bundles --without-oracle --without-dvb --disable-rpath --without-vcdiff --without-zxid --disable-smartlink_binary --without-machine-code Use `make CONFIGUREARGS="..." ...' to change them. They will be retained in the build directory. Running /bin/bash -norc /<>/src/configure --with-cdebug --with-copt --without-rtldebug --with-cflags='-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security' --with-cppflags='-Wdate-time -D_FORTIFY_SOURCE=2 -DDEBIAN' --with-ldflags='-Wl,-z,relro -Wl,--as-needed' --prefix=/usr --with-bignums --with-gmp --with-poll --with-zlib --with-freetype --without-ttflib --with-libnettle --without-sybase --without-java --with-odbc --with-sane --with-postgres --with-postgres-include-dir=/usr/include/postgresql --with-libpq-dir=/usr/lib --with-sass --with-sqlite --without-com --without-ffmpeg --without-fftw --without-libpdf --without-libpanda --without-GTK --without-GTK2 --without-bundles --without-oracle --without-dvb --disable-rpath --without-vcdiff --without-zxid --disable-smartlink_binary --without-machine-code in build/linux-4.19.0-6-cloud-amd64-x86_64 checking whether /usr/bin/make sets $(MAKE)... yes checking whether /usr/bin/make supports VPATH... yes checking whether we need an icc workaround... no checking for gcc... gcc checking whether the C compiler
Bug#1001669: closed by Debian FTP Masters (reply to Aniol Martí ) (Bug#1001669: fixed in openvpn-auth-ldap 2.0.4-2)
Hi, unfortunately this is still happening in 2.0.4-2 https://ci.debian.net/packages/o/openvpn-auth-ldap/unstable/amd64/ Right now this would be preventing the new version of openvpn to migrate (I can retry of course). Bernhard
Processed: Reassign package
Processing commands for cont...@bugs.debian.org: > reassign 1007827 python3-gwcs 0.18.0-2 Bug #1007827 [src:asdf-astropy, src:gwcs] asdf-astropy breaks gwcs autopkgtest: cannot import name 'assert_models_equal' from 'asdf_astropy.converters.transform.tests.test_transform' Bug reassigned from package 'src:asdf-astropy, src:gwcs' to 'python3-gwcs'. No longer marked as found in versions gwcs/0.18.0-2. Ignoring request to alter fixed versions of bug #1007827 to the same values previously set Bug #1007827 [python3-gwcs] asdf-astropy breaks gwcs autopkgtest: cannot import name 'assert_models_equal' from 'asdf_astropy.converters.transform.tests.test_transform' Marked as found in versions gwcs/0.18.0-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1007827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003907: fails to successfully associate
Some more data points:
Disabling NetworkManager completely and using wpasupplicant alone with
the following config:
network={
ssid="wgrouter"
psk=""
key_mgmt=WPA-PSK
id_str="wgrouter"
}
does indeed work.
As soon as I enable NetworkManager though, my connection fails, even
though /etc/NetworkManager/system-connections/wgrouter.nmconnection
contains
[wifi-security]
key-mgmt=wpa-psk
psk=
In journalctl -u NetworkManager I see
Mär 21 11:15:07 pluto NetworkManager[2450]: [1647857707.7752]
Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Ľubomír, is there a way how I can tell NetworkManager to *not* use SAE?
Am 21.03.22 um 09:38 schrieb Andrej Shadura:
Hi,
On Sun, 20 Mar 2022, at 00:23, Masashi Honma wrote:
In my opinion, this issue could be closed.
These are reasons.
1) It is not wpa_supplicant issue but AP issue.
2) Users affected by this issue have some workarounds.
It’s true, but I’m not quite happy about not being able to fix this.
Ľubomír (cc'ed), how did you deal with this issue in Fedora? I assume you must
also have received reports from Fritzbox users.
Details of the 1)
The investigation has revealed that the AP is in violation of "2.3
WPA3-Personal transition mode" of the "WPA3 Specification v3.0", which
is causing the issue. Specifically, the target AP is setting MFPR to 1
even though it implicitly requires IEEE 802.11w. By "implicitly" we
mean that the Assocation Request fails with WLAN_STATUS_INVALID_IE
when using a Wi-Fi NIC with IEEE 802.11w disabled.
Details of the 2)
We know that users who meet the following conditions are affected by this issue.
- Using FRITZ!Box 7580/7590 with WPA2+WPA3 mode
I've tested it with both 7490 and 7530 AX, fwiw.
- Using wpa_supplicant with wpa_key_mgmt=SAE WPA-PSK
- Local Wi-Fi NIC does not support IEEE802.11w
Users affected by this issue can work around the issue in one of the
following ways.
- Use wpa_supplicant with WPA2 only mode (specify wpa_key_mgmt=WPA-PSK)
- Use FRITZ!Box 7580/7590 with WPA2 only mode
- Use IEEE 802.11w supporting Wi-Fi NIC
Masashi, if I understand you correctly, you argue that this is an issue
with the AP (or its firmware).
If so, should the company AVM be contacted about this?
I'm afraid I'm not too knowledgeable in that regard.
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1008037: marked as pending in pkg-js-tools
Control: tag -1 pending Hello, Bug #1008037 in pkg-js-tools 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/js-team/pkg-js-tools/-/commit/c82ee17a977de383478d2d4c8f1e87d700bc1c02 debhelper: Don't fail when subsvars were not generated, just warn Closes: #1008037 (this message was generated automatically) -- Greetings https://bugs.debian.org/1008037
Processed: Bug#1008037 marked as pending in pkg-js-tools
Processing control commands: > tag -1 pending Bug #1008037 [src:sax.js] FTBFS: No such file or directory at /usr/bin/dh_nodejs_substvars line 21 Ignoring request to alter tags of bug #1008037 to the same tags previously set -- 1008037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008037 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Reassign package
Processing commands for cont...@bugs.debian.org: > reassign 1007827 python3-gwcs/0.18.0-2 Unknown command or malformed arguments to command. > notfound 1007827 asdf-astropy/0.2.0-1 Bug #1007827 [src:asdf-astropy, src:gwcs] asdf-astropy breaks gwcs autopkgtest: cannot import name 'assert_models_equal' from 'asdf_astropy.converters.transform.tests.test_transform' No longer marked as found in versions asdf-astropy/0.2.0-1. > affects 1007827 python3-asdf-astropy Bug #1007827 [src:asdf-astropy, src:gwcs] asdf-astropy breaks gwcs autopkgtest: cannot import name 'assert_models_equal' from 'asdf_astropy.converters.transform.tests.test_transform' Added indication that 1007827 affects python3-asdf-astropy > thanks Stopping processing here. Please contact me if you need assistance. -- 1007827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1007983: node-puppeteer: broken autopkgtest keeping chromium from migrating to testing
Hi Andres, Thanks for your report, puppeteer will need to be updated to match the new version of chromium right away. It seems there are also some flaky tests, which caused the sporadic failures... On 21/03/2022 01:55, Andres Salomon wrote: On Sat, 19 Mar 2022 17:44:02 -0400 Andres Salomon wrote: > Source: node-puppeteer > Control: found -1 node-puppeteer/13.1.0+dfsg-6 > Control: affects -1 chromium > Severity: serious > Tags: sid bookworm > > node-puppeteer is keeping chromium from migrating; as > https://tracker.debian.org/pkg/chromium describes, It looks like the tests also failed in testing with chromium v98 (https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-puppeteer/20151806/log.gz), which did actually allow chromium v99 to migrate to testing, so you can ignore that part of this bug report. -- Martina Ferrari (Tina)
Bug#1008037: marked as pending in sax.js
Control: tag -1 pending Hello, Bug #1008037 in sax.js 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/js-team/sax.js/-/commit/58df2a2237de969c18f195af1317f1dd8ee7a7a1 Use dh-sequence-nodejs auto install Closes: #1008037 (this message was generated automatically) -- Greetings https://bugs.debian.org/1008037
Processed: Bug#1008037 marked as pending in sax.js
Processing control commands: > tag -1 pending Bug #1008037 [src:sax.js] FTBFS: No such file or directory at /usr/bin/dh_nodejs_substvars line 21 Added tag(s) pending. -- 1008037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008037 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008037: [Pkg-javascript-devel] Bug#1008037: FTBFS: No such file or directory at /usr/bin/dh_nodejs_substvars line 21
On Mon, Mar 21, 2022 at 10:54 AM Yadd wrote: > Control: tags -1 + moreinfo > > On 21/03/2022 09:02, Jérémy Lal wrote: > > Source: sax.js > > Version: 1.2.4+~1.2.4-1 > > Severity: serious > > Tags: ftbfs > > Justification: fails to build from source > > > > This happened during rebuild of this package: > > > > > > dh_nodejs_substvars > > No such file or directory at /usr/bin/dh_nodejs_substvars line 21. > > make: *** [debian/rules:8: binary] Error 2 > > dpkg-buildpackage: error: debian/rules binary subprocess returned exit > status 2 > > Hi, > > dh_nodejs_substvars is part of dh-nodejs (pkg-js-tools) and called by > dh-nodejs. I'm unable to reproduce this issue. > > However sax.js test is broken by node-tap update (needs --no-cov). I'm > going to fix that > The full log: https://salsa.debian.org/js-team/nodejs/-/jobs/2591950 This is probably the culprit: > dh: command-omitted: The call to "dh_auto_test" was omitted due to "DEB_BUILD_OPTIONS=nocheck" It shouldn't fail with that option. Jérémy
Processed: Re: [Pkg-javascript-devel] Bug#1008037: Bug#1008037: FTBFS: No such file or directory at /usr/bin/dh_nodejs_substvars line 21
Processing control commands: > tags -1 - moreinfo + confirmed Bug #1008037 [src:sax.js] FTBFS: No such file or directory at /usr/bin/dh_nodejs_substvars line 21 Removed tag(s) moreinfo. Bug #1008037 [src:sax.js] FTBFS: No such file or directory at /usr/bin/dh_nodejs_substvars line 21 Added tag(s) confirmed. -- 1008037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008037 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008037: [Pkg-javascript-devel] Bug#1008037: Bug#1008037: FTBFS: No such file or directory at /usr/bin/dh_nodejs_substvars line 21
Control: tags -1 - moreinfo + confirmed On 21/03/2022 10:54, Yadd wrote: Control: tags -1 + moreinfo On 21/03/2022 09:02, Jérémy Lal wrote: Source: sax.js Version: 1.2.4+~1.2.4-1 Severity: serious Tags: ftbfs Justification: fails to build from source This happened during rebuild of this package: dh_nodejs_substvars No such file or directory at /usr/bin/dh_nodejs_substvars line 21. make: *** [debian/rules:8: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Hi, dh_nodejs_substvars is part of dh-nodejs (pkg-js-tools) and called by dh-nodejs. I'm unable to reproduce this issue. However sax.js test is broken by node-tap update (needs --no-cov). I'm going to fix that Sorry, problem is that there is an override_dh_auto_install which drops substvars generation.
Processed: reopening 1001669
Processing commands for cont...@bugs.debian.org:
> reopen 1001669
Bug #1001669 {Done: Aniol Martí } [src:openvpn-auth-ldap]
openvpn-auth-ldap: flaky autopkgtest on amd64
'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 openvpn-auth-ldap/2.0.4-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1001669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: found 1001669 in 2.0.4-2
Processing commands for cont...@bugs.debian.org: > found 1001669 2.0.4-2 Bug #1001669 [src:openvpn-auth-ldap] openvpn-auth-ldap: flaky autopkgtest on amd64 Marked as found in versions openvpn-auth-ldap/2.0.4-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1001669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001669 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1007992: libigdgmm12: new version causes segfaults
* Paul Menzel , 2022-03-20, 07:22: Control: forward -1 https://github.com/intel/gmmlib/issues/95 I thought it was `forwarded`, but changed after reading the example in *How to report a bug in Debian using reportbug* [2], which turned out to be wrong. This documentation bug is tracked as #863069. -- Jakub Wilk
Processed: Re: [Pkg-javascript-devel] Bug#1008037: FTBFS: No such file or directory at /usr/bin/dh_nodejs_substvars line 21
Processing control commands: > tags -1 + moreinfo Bug #1008037 [src:sax.js] FTBFS: No such file or directory at /usr/bin/dh_nodejs_substvars line 21 Added tag(s) moreinfo. -- 1008037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008037 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008037: [Pkg-javascript-devel] Bug#1008037: FTBFS: No such file or directory at /usr/bin/dh_nodejs_substvars line 21
Control: tags -1 + moreinfo On 21/03/2022 09:02, Jérémy Lal wrote: Source: sax.js Version: 1.2.4+~1.2.4-1 Severity: serious Tags: ftbfs Justification: fails to build from source This happened during rebuild of this package: dh_nodejs_substvars No such file or directory at /usr/bin/dh_nodejs_substvars line 21. make: *** [debian/rules:8: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Hi, dh_nodejs_substvars is part of dh-nodejs (pkg-js-tools) and called by dh-nodejs. I'm unable to reproduce this issue. However sax.js test is broken by node-tap update (needs --no-cov). I'm going to fix that
Bug#1003907: fails to successfully associate
On 21/03/2022 09:38, Andrej Shadura wrote: Hi, On Sun, 20 Mar 2022, at 00:23, Masashi Honma wrote: In my opinion, this issue could be closed. These are reasons. 1) It is not wpa_supplicant issue but AP issue. 2) Users affected by this issue have some workarounds. It’s true, but I’m not quite happy about not being able to fix this. Ľubomír (cc'ed), how did you deal with this issue in Fedora? I assume you must also have received reports from Fritzbox users. Details of the 1) The investigation has revealed that the AP is in violation of "2.3 WPA3-Personal transition mode" of the "WPA3 Specification v3.0", which is causing the issue. Specifically, the target AP is setting MFPR to 1 even though it implicitly requires IEEE 802.11w. By "implicitly" we mean that the Assocation Request fails with WLAN_STATUS_INVALID_IE when using a Wi-Fi NIC with IEEE 802.11w disabled. (I assume Masashi meant "the target AP is setting MFPC to 0"). Details of the 2) We know that users who meet the following conditions are affected by this issue. - Using FRITZ!Box 7580/7590 with WPA2+WPA3 mode - Using wpa_supplicant with wpa_key_mgmt=SAE WPA-PSK - Local Wi-Fi NIC does not support IEEE802.11w Users affected by this issue can work around the issue in one of the following ways. - Use wpa_supplicant with WPA2 only mode (specify wpa_key_mgmt=WPA-PSK) - Use FRITZ!Box 7580/7590 with WPA2 only mode - Use IEEE 802.11w supporting Wi-Fi NIC The WPA3 spec also indicate that when a non-AP STA uses WPA3, it must use 802.11w. A strict interpretation of this spec would indicate that SAE should not be used by hardware without 802.11w support. Complying to this spec could be a workaround: "if WPA-PSK and SAE are advertised, MFPR is not set and local hardware does not support MFP, do not use SAE". This could however degrade security to APs that comply to the 802.11 specifications without complying to Wi-Fi specifications (i.e. which do not advertise themselves as "Wi-Fi").
Processed: reopening 1006910, reopening 1007126
Processing commands for cont...@bugs.debian.org:
> reopen 1006910
Bug #1006910 {Done: Gürkan Myczko } [src:pdal] pdal: Should
not be included in bookworm
'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 cloudcompare/2.11.3-5.
> reopen 1007126
Bug #1007126 {Done: Gürkan Myczko } [src:laszip] laszip:
Should not be included in bookworm
'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 cloudcompare/2.11.3-5.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1006910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006910
1007126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1007234: Test suite fails on all but amd64 arches
Dear Bryan, Could you comment on the buildds failures at: * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007234 For example on ppc64el (little endian system): * https://buildd.debian.org/status/fetch.php?pkg=netpbm-free=ppc64el=2%3A10.97.00-1=1647179729=0 [...] == palm-roundtrip.test == pamdepth: promoting from black and white to grayscale palmtopnm: Invalid Palm image input. Header says 30 bytes per row after uncompressing from 8-bit Packbits, but we counted 4294967069 bytes in a row, before we stopped processing the row pnmcolormap: making histogram... pnmcolormap: Scanning image 0 pnmcolormap: 20314 colors so far pnmcolormap: 20314 colors found pnmcolormap: choosing 256 colors... pnmremap: 256 colors found in colormap palmtopnm: Invalid Palm image input. Header says 228 bytes per row after uncompressing from 8-bit Packbits, but we counted 4294967044 bytes in a row, before we stopped processing the row palm-roundtrip.test: FAILURE == palm-roundtrip2.test == pnmremap: 231 colors found in colormap palmtopnm: Invalid Palm image input. Header says 228 bytes per row after uncompressing from 8-bit Packbits, but we counted 4294967088 bytes in a row, before we stopped processing the row palm-roundtrip2.test: FAILURE [...] Thanks !
Bug#1003907: fails to successfully associate
Hi, On Sun, 20 Mar 2022, at 00:23, Masashi Honma wrote: > In my opinion, this issue could be closed. > > These are reasons. > 1) It is not wpa_supplicant issue but AP issue. > 2) Users affected by this issue have some workarounds. It’s true, but I’m not quite happy about not being able to fix this. Ľubomír (cc'ed), how did you deal with this issue in Fedora? I assume you must also have received reports from Fritzbox users. > Details of the 1) > The investigation has revealed that the AP is in violation of "2.3 > WPA3-Personal transition mode" of the "WPA3 Specification v3.0", which > is causing the issue. Specifically, the target AP is setting MFPR to 1 > even though it implicitly requires IEEE 802.11w. By "implicitly" we > mean that the Assocation Request fails with WLAN_STATUS_INVALID_IE > when using a Wi-Fi NIC with IEEE 802.11w disabled. > > > Details of the 2) > We know that users who meet the following conditions are affected by this > issue. > - Using FRITZ!Box 7580/7590 with WPA2+WPA3 mode > - Using wpa_supplicant with wpa_key_mgmt=SAE WPA-PSK > - Local Wi-Fi NIC does not support IEEE802.11w > > Users affected by this issue can work around the issue in one of the > following ways. > - Use wpa_supplicant with WPA2 only mode (specify wpa_key_mgmt=WPA-PSK) > - Use FRITZ!Box 7580/7590 with WPA2 only mode > - Use IEEE 802.11w supporting Wi-Fi NIC -- Cheers, Andrej
Bug#1007126: marked as done (laszip: Should not be included in bookworm)
Your message dated Mon, 21 Mar 2022 08:33:55 + with message-id and subject line Bug#1007126: fixed in cloudcompare 2.11.3-5 has caused the Debian Bug report #1007126, regarding laszip: Should not be included in bookworm 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.) -- 1007126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: laszip Version: 3.4.3-2 Severity: serious Tags: bookworm sid Justification: in the maintainer's opinion, makes the package unsuitable for release Control: block -1 by 1006910 LASzip is dead upstream, literally. It should not be included in bookworm, but cannot be removed before PDAL is. --- End Message --- --- Begin Message --- Source: cloudcompare Source-Version: 2.11.3-5 Done: Gürkan Myczko We believe that the bug you reported is fixed in the latest version of cloudcompare, 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 1007...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gürkan Myczko (supplier of updated cloudcompare 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: Mon, 21 Mar 2022 08:24:58 +0100 Source: cloudcompare Architecture: source Version: 2.11.3-5 Distribution: unstable Urgency: medium Maintainer: Gürkan Myczko Changed-By: Gürkan Myczko Closes: 1006910 1007126 1007127 Changes: cloudcompare (2.11.3-5) unstable; urgency=medium . * Drop PDAL & LASzip from build dependencies, the packages will be removed. Thanks for the patches Bas Couwenberg. (Closes: #1006910, #1007126, #1007127) Checksums-Sha1: 3d15a8ff6b744efc8d3db293b506c2e3ed3ffb64 2088 cloudcompare_2.11.3-5.dsc 6c1e7f45edb0a442f249d967023cd9595aa50ca9 10692 cloudcompare_2.11.3-5.debian.tar.xz b75cb3888fc458d3a31e708817d5279ff958e9f3 24882 cloudcompare_2.11.3-5_source.buildinfo Checksums-Sha256: 9a0fe6b435a60edbab92c9694d3980b22f5fe0079e45e33a2d3a704290d8 2088 cloudcompare_2.11.3-5.dsc eba655919cc581300c6fd9a182d5b262fb6abef0a0d26b8bcbff759d921c2c81 10692 cloudcompare_2.11.3-5.debian.tar.xz faaf6afc887f8a00fdb738272cb0ce6432da126f29ea9f020f5abceeebfcc60e 24882 cloudcompare_2.11.3-5_source.buildinfo Files: f7e4a5e699055545d46745a272dc3e7c 2088 graphics optional cloudcompare_2.11.3-5.dsc b7a464b12779892abbc21855a06f4ce5 10692 graphics optional cloudcompare_2.11.3-5.debian.tar.xz 0f74ae849fe9ad954266217f665d8d15 24882 graphics optional cloudcompare_2.11.3-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmI4L38ACgkQEWhSvN91 FcAHpQ//WX1wsfD8yVk7Juj1X7OW1qawBa8hY6ea7/7T/FAO7/+d3fHfhua9YkeF V6jMkl13EznH9hOjFgFs6gp3G/FmvFgGSRnd+Hk4Pzy4Qq7RJ6MCkCBj8vJhhn6S C91mqsmPBlW25KNpFS92YYs6bcEv+m4+hgVbpB0fDXapN9sm767vZpRNFzl0NkPj 94m4N2WOVcsMw+gU2zzH4v9ZaKaiBa1NJ5Gw6yNV43+FnQln59rOD/9RabRKJYxm wd6V/0SV55M26JXea7EPqfv5fPy4yW6aOyAd3I75kp6QvE4ySy48osIak0ELYD+r 2Yme745+omF7UrYp5IHrePT9QyZSx9eBNYyQJea+26J6KsSXCJBQvdeYRG1xNRVZ uSIU3HLn62LyfT5FlYSFrBm7ljdDfObprgpVQlDO9qkQfjES/0iJYK568DbbFoG+ lFeKeC9wd4Sz86fMpwA0CW7o3dKuX/Z2vAtuaYozu/J048JhkBGyn0r0qNAiPq7Z PnZZ8cZhpLSrfFV+vuCUTebe6aunNVAVaUFNQKyK72BmJYheAbPlw6+IEGGoMGGG m8GFlV7DA500kZpsSe28wz7OSyCTm5+iFfARjQ7nLjaK7cRSOjLvFj4ILVZFCX7g ZUwHuv/ASFhCgKKOv1VbP+1sJhalOch2eijEjZtzl7Agthd4cDk= =m5aC -END PGP SIGNATURE End Message ---
Bug#1006910: marked as done (pdal: Should not be included in bookworm)
Your message dated Mon, 21 Mar 2022 08:33:55 + with message-id and subject line Bug#1006910: fixed in cloudcompare 2.11.3-5 has caused the Debian Bug report #1006910, regarding pdal: Should not be included in bookworm 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.) -- 1006910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pdal Version: 2.3.0+ds-2 Severity: serious Tags: upstream Justification: in the maintainer's opinion, makes the package unsuitable for release PDAL upstream has exhausted my tolerance of his combative attitude. I am no longer willing to spend time on maintaining this package. The package should be removed from Debian, as others should not be subjected to his attitude either. At time of writing cloudcompare and facet-analyser have pdal as a build dependency, and paraview also has it in its binary package dependencies. These packages will need to remove their pdal support. Once that's done pdal can be removed from Debian. If anyone wants to take over maintenance of the pdal package despite a combative upstream, that will need to happen outside the GIS team. --- End Message --- --- Begin Message --- Source: cloudcompare Source-Version: 2.11.3-5 Done: Gürkan Myczko We believe that the bug you reported is fixed in the latest version of cloudcompare, 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 1006...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gürkan Myczko (supplier of updated cloudcompare 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: Mon, 21 Mar 2022 08:24:58 +0100 Source: cloudcompare Architecture: source Version: 2.11.3-5 Distribution: unstable Urgency: medium Maintainer: Gürkan Myczko Changed-By: Gürkan Myczko Closes: 1006910 1007126 1007127 Changes: cloudcompare (2.11.3-5) unstable; urgency=medium . * Drop PDAL & LASzip from build dependencies, the packages will be removed. Thanks for the patches Bas Couwenberg. (Closes: #1006910, #1007126, #1007127) Checksums-Sha1: 3d15a8ff6b744efc8d3db293b506c2e3ed3ffb64 2088 cloudcompare_2.11.3-5.dsc 6c1e7f45edb0a442f249d967023cd9595aa50ca9 10692 cloudcompare_2.11.3-5.debian.tar.xz b75cb3888fc458d3a31e708817d5279ff958e9f3 24882 cloudcompare_2.11.3-5_source.buildinfo Checksums-Sha256: 9a0fe6b435a60edbab92c9694d3980b22f5fe0079e45e33a2d3a704290d8 2088 cloudcompare_2.11.3-5.dsc eba655919cc581300c6fd9a182d5b262fb6abef0a0d26b8bcbff759d921c2c81 10692 cloudcompare_2.11.3-5.debian.tar.xz faaf6afc887f8a00fdb738272cb0ce6432da126f29ea9f020f5abceeebfcc60e 24882 cloudcompare_2.11.3-5_source.buildinfo Files: f7e4a5e699055545d46745a272dc3e7c 2088 graphics optional cloudcompare_2.11.3-5.dsc b7a464b12779892abbc21855a06f4ce5 10692 graphics optional cloudcompare_2.11.3-5.debian.tar.xz 0f74ae849fe9ad954266217f665d8d15 24882 graphics optional cloudcompare_2.11.3-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmI4L38ACgkQEWhSvN91 FcAHpQ//WX1wsfD8yVk7Juj1X7OW1qawBa8hY6ea7/7T/FAO7/+d3fHfhua9YkeF V6jMkl13EznH9hOjFgFs6gp3G/FmvFgGSRnd+Hk4Pzy4Qq7RJ6MCkCBj8vJhhn6S C91mqsmPBlW25KNpFS92YYs6bcEv+m4+hgVbpB0fDXapN9sm767vZpRNFzl0NkPj 94m4N2WOVcsMw+gU2zzH4v9ZaKaiBa1NJ5Gw6yNV43+FnQln59rOD/9RabRKJYxm wd6V/0SV55M26JXea7EPqfv5fPy4yW6aOyAd3I75kp6QvE4ySy48osIak0ELYD+r 2Yme745+omF7UrYp5IHrePT9QyZSx9eBNYyQJea+26J6KsSXCJBQvdeYRG1xNRVZ uSIU3HLn62LyfT5FlYSFrBm7ljdDfObprgpVQlDO9qkQfjES/0iJYK568DbbFoG+ lFeKeC9wd4Sz86fMpwA0CW7o3dKuX/Z2vAtuaYozu/J048JhkBGyn0r0qNAiPq7Z PnZZ8cZhpLSrfFV+vuCUTebe6aunNVAVaUFNQKyK72BmJYheAbPlw6+IEGGoMGGG m8GFlV7DA500kZpsSe28wz7OSyCTm5+iFfARjQ7nLjaK7cRSOjLvFj4ILVZFCX7g ZUwHuv/ASFhCgKKOv1VbP+1sJhalOch2eijEjZtzl7Agthd4cDk= =m5aC -END PGP SIGNATURE End Message ---
Bug#1008037: FTBFS: No such file or directory at /usr/bin/dh_nodejs_substvars line 21
Source: sax.js Version: 1.2.4+~1.2.4-1 Severity: serious Tags: ftbfs Justification: fails to build from source This happened during rebuild of this package: dh_nodejs_substvars No such file or directory at /usr/bin/dh_nodejs_substvars line 21. make: *** [debian/rules:8: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Jérémy -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable'), (101, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-5-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Processed: severity of 1007200 is serious
Processing commands for cont...@bugs.debian.org: > severity 1007200 serious Bug #1007200 [src:pytorch] pytorch: FTBFS with glog 0.6.0+ Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1007200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1007200
Processing commands for cont...@bugs.debian.org: > tags 1007200 + bookworm Bug #1007200 [src:pytorch] pytorch: FTBFS with glog 0.6.0+ Added tag(s) bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 1007200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004756: src:python-confluent-kafka: fails to migrate to testing for too long: FTBFS on s390x
This issue with python-confluent-kafka just caused a lot of packages to be removed from testing. Examples includes gnocci, heat-dashboard, freezer, cloudkitty, barbican, aodh, cinder, keystone and magnum. Any hope to get the s390x build fixed? I notice there is a new upstream available too. -- Happy hacking Petter Reinholdtsen
Processed: limit source to frama-c, tagging 1000491
Processing commands for cont...@bugs.debian.org: > limit source frama-c Limiting to bugs with field 'source' containing at least one of 'frama-c' Limit currently set to 'source':'frama-c' > tags 1000491 + pending Bug #1000491 [src:frama-c] FTBFS with Why3 1.4.0 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: gajim in Debian stretch does not start anymore
Processing control commands: > severity -1 normal Bug #930991 [gajim] gajim in Debian stretch does not start anymore Severity set to 'normal' from 'grave' -- 930991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930991 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#930991: gajim in Debian stretch does not start anymore
Control: severity -1 normal Hello, there was no feedback on this bugreport. I will set the severity to normal, because: * I was not able to reproduce this bug * The bug is reported on o-o-stable * There was no feedback See: https://www.debian.org/Bugs/Developer.en#severities -- Stefan Kropp
