Bug#1002257: marked as done (rust-os-info: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101)
Your message dated Fri, 03 Jun 2022 05:04:20 +
with message-id
and subject line Bug#1002257: fixed in rust-os-info 3.4.0-1
has caused the Debian Bug report #1002257,
regarding rust-os-info: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo
build returned exit code 101
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.)
--
1002257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002257
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-os-info
Version: 1.3.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --buildsystem cargo
>dh_update_autotools_config -O--buildsystem=cargo
>dh_autoreconf -O--buildsystem=cargo
>dh_auto_configure -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: linking /usr/share/cargo/registry/* into
> /<>/debian/cargo_registry/
>dh_auto_build -O--buildsystem=cargo
>dh_auto_test -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose',
> '-j4', '--target', 'x86_64-unknown-linux-gnu'],) {}
>Compiling proc-macro2 v1.0.28
>Compiling unicode-xid v0.2.0
>Compiling memchr v2.4.1
>Compiling syn v1.0.76
> Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=build_script_build
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/proc-macro2-1.0.28
> CARGO_PKG_AUTHORS='Alex Crichton :David Tolnay
> ' CARGO_PKG_DESCRIPTION='A substitute implementation of
> the compiler'\''s `proc_macro` API to decouple
> token-based libraries from the procedural macro use case.
> ' CARGO_PKG_HOMEPAGE='' CARGO_PKG_LICENSE='MIT OR Apache-2.0'
> CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=proc-macro2
> CARGO_PKG_REPOSITORY='https://github.com/alexcrichton/proc-macro2'
> CARGO_PKG_VERSION=1.0.28 CARGO_PKG_VERSION_MAJOR=1 CARGO_PKG_VERSION_MINOR=0
> CARGO_PKG_VERSION_PATCH=28 CARGO_PKG_VERSION_PRE=''
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc
> --crate-name build_script_build --edition=2018
> /<>/debian/cargo_registry/proc-macro2-1.0.28/build.rs
> --error-format=json --json=diagnostic-rendered-ansi --crate-type bin
> --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 --cfg
> 'feature="default"' --cfg 'feature="proc-macro"' -C metadata=e0c680855105df2d
> -C extra-filename=-e0c680855105df2d --out-dir
> /<>/target/debug/build/proc-macro2-e0c680855105df2d -L
> dependency=/<>/target/debug/deps --cap-lints warn`
> Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=unicode_xid
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/unicode-xid-0.2.0
> CARGO_PKG_AUTHORS='erick.tryzelaar :kwantam
> ' CARGO_PKG_DESCRIPTION='Determine whether characters have
> the XID_Start
> or XID_Continue properties according to
> Unicode Standard Annex #31.
> ' CARGO_PKG_HOMEPAGE='https://github.com/unicode-rs/unicode-xid'
> CARGO_PKG_LICENSE='MIT OR Apache-2.0' CARGO_PKG_LICENSE_FILE=''
> CARGO_PKG_NAME=unicode-xid
> CARGO_PKG_REPOSITORY='https://github.com/unicode-rs/unicode-xid'
> CARGO_PKG_VERSION=0.2.0 CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_VERSION_MINOR=2
> CARGO_PKG_VERSION_PATCH=0 CARGO_PKG_VERSION_PRE=''
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc
> --crate-name unicode_xid
> /<>/debian/cargo_registry/unicode-xid-0.2.0/src/lib.rs
> --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type
> lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 --cfg
> 'feature="default"' -C metadata=046b391f7047a9b4 -C
> extra-filename=-046b391f7047a9b4 --out-dir /<>/target/debug/deps
> -L dependency=/<>/target/debug/deps --cap-lints warn`
> Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=build_script_build
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/memchr-2.4.1
> CARGO_PKG_AUTHORS='Andrew Gallant :bluss'
> CARGO_PKG_DESCRIPTION='Safe interface to memchr.'
> CARGO_PKG_HOMEPAGE='https://github.com/BurntSushi/memchr'
> CARGO_PKG_LICENSE=Unlicense/MIT CARGO_PKG_LICENSE_FILE=''
> CARGO_PKG_NAME=memchr
>
Bug#1012244: marked as done (autopkgtest fails)
Your message dated Fri, 03 Jun 2022 03:24:00 + with message-id and subject line Bug#1012244: fixed in lime-forensics 1.9.1-4 has caused the Debian Bug report #1012244, regarding autopkgtest fails 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.) -- 1012244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012244 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: limewire Severity: serious Version: 1.9.1-3 Control: clone -1 -2 Control: reassign -2 src:nvidia-graphics-drivers-tesla-470 Control: version -2 470.129.06-3 Control: tag -1 patch Control: forwarded -1 https://salsa.debian.org/pkg-security-team/lime-forensics/-/merge_requests/2 Control: retitle -2 fails on ppc64el due to transitive GPL symbol usage Hi, [This bug report is a follow up from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010883#59, a bug in the dkms autopkgtest framework] On 02-06-2022 04:12, Andreas Beckmann wrote: On 27/05/2022 16.22, Andreas Beckmann wrote: On 27/05/2022 10.59, Paul Gevers wrote: My guess is that apt pinning comes into play here, installing That aligns with my suspicion that it's related to the mixing of unstable and testing. Uploaded a first attempt on the fix. Works for me, let's see how ci.d.o likes it. There are probably still corner cases to be handled ... Looks not too bad. Current problems: lime-forensics: used dkms-autopkgtest manually, not via Testsuite: autopkgtest-pkg-dkms merge-request !2 (only autopkgtest buggy, module builds fine) Let's also track this in a bug report. r8125: bug #1012014 - r8125: fails to build module for Linux 5.17 (new upstream release available) nvidia-graphics-drivers-tesla-470: fails on ppc64el due to transitive GPL symbol usage, reported upstream Ditto. nvidia-graphics-drivers-tesla-510: improved version in experimental, but has the same problem on ppc64el as 470 (not yet in sid due to moving a package from nvidia-graphics-drivers to -tesla-510) feel free to temporarily remove from testing Since these bugs (modules failing to build) are already present in testing and only exposed by the new dkms by making the autopkgtest run no longer a no-op, perhaps you could just ignore the failing tests and hint dkms into testing? Ack. (-tesla-510 would need some forced hint for reintroduction into testing as well, since I don't think an upstream fix for ppc64el will be available in time when I move nvidia-graphics-drivers from 470 to 510 as default in sid) Please ping us when the time comes. Paul OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: lime-forensics Source-Version: 1.9.1-4 Done: Joao Eriberto Mota Filho We believe that the bug you reported is fixed in the latest version of lime-forensics, 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 1012...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joao Eriberto Mota Filho (supplier of updated lime-forensics package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 Jun 2022 23:15:28 -0300 Source: lime-forensics Architecture: source Version: 1.9.1-4 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Joao Eriberto Mota Filho Closes: 1012244 Changes: lime-forensics (1.9.1-4) unstable; urgency=medium . [ Andreas Beckmann ] * Switch to dh-sequence-dkms. * Switch to Testsuite: autopkgtest-pkg-dkms. * Closes: #1012244 . [ Joao Eriberto Mota Filho ] * debian/control: bumped Standards-Version to 4.6.0. * debian/copyright: - Added packaging rights for Andreas Backmann. - Updated packaging copyright years. * debian/salsa-ci.yml: added allow_failure to reprotest until the issue isn't solved. Checksums-Sha1: 78e81fc44981e30f981e7afac53d0f172f70b8d2 2056 lime-forensics_1.9.1-4.dsc ba42567f621a86f0f128b6444c11f69e669c5754 6196 lime-forensics_1.9.1-4.debian.tar.xz 28daf588e1e4a35942119809e14e03677d718dcb 6237 lime-forensics_1.9.1-4_source.buildinfo Checksums-Sha256: 80d9dfcdf150a66f48748f25239ad058fb8ef2e9ed71fa64d7d8b2d4edabb53a 2056
Bug#1012284: elan - FTBFS unsatisfiable cargo dependencies
Package: elan
Version: 1.3.1-3
Severity: serious
Tags: patch
A number of rust crates have been updated recently, as a result your
package no longer builds, I have updated the patches to relax the
dependencies and was able to succesfully build the package, I have not
tested it beyond that.
From: Christopher Hoskin
Date: Wed, 26 Jan 2022 19:46:47 +
Subject: Revert "feat: support tar.zst archives"
This reverts commit 3241c307cfcff08f02ae9856aa505c05fc14fcd7.
---
Cargo.lock | 39 --
src/elan-dist/Cargo.toml | 1 -
src/elan-dist/src/component/package.rs | 16 --
src/elan-dist/src/download.rs | 4 ++--
src/elan-dist/src/manifestation.rs | 25 +++---
5 files changed, 15 insertions(+), 70 deletions(-)
Index: elan-1.3.1/Cargo.lock
===
--- elan-1.3.1.orig/Cargo.lock
+++ elan-1.3.1/Cargo.lock
@@ -394,7 +394,6 @@ dependencies = [
"winapi 0.3.9",
"winreg 0.8.0",
"zip",
- "zstd",
]
[[package]]
@@ -778,15 +777,6 @@ source = "registry+https://github.com/ru
checksum = "b71991ff56294aa922b450139ee08b3bfc70982c6b2c7562771375cf73542dd4"
[[package]]
-name = "jobserver"
-version = "0.1.24"
-source = "registry+https://github.com/rust-lang/crates.io-index;
-checksum = "af25a77299a7f711a01975c35a6a424eb6862092cc2d6c72c4ed6cbc56dfc1fa"
-dependencies = [
- "libc",
-]
-
-[[package]]
name = "js-sys"
version = "0.3.55"
source = "registry+https://github.com/rust-lang/crates.io-index;
@@ -1873,32 +1863,3 @@ dependencies = [
"thiserror",
"time 0.1.43",
]
-
-[[package]]
-name = "zstd"
-version = "0.9.0+zstd.1.5.0"
-source = "registry+https://github.com/rust-lang/crates.io-index;
-checksum = "07749a5dc2cb6b36661290245e350f15ec3bbb304e493db54a1d354480522ccd"
-dependencies = [
- "zstd-safe",
-]
-
-[[package]]
-name = "zstd-safe"
-version = "4.1.1+zstd.1.5.0"
-source = "registry+https://github.com/rust-lang/crates.io-index;
-checksum = "c91c90f2c593b003603e5e0493c837088df4469da25aafff8bce42ba48caf079"
-dependencies = [
- "libc",
- "zstd-sys",
-]
-
-[[package]]
-name = "zstd-sys"
-version = "1.6.1+zstd.1.5.0"
-source = "registry+https://github.com/rust-lang/crates.io-index;
-checksum = "615120c7a2431d16cf1cf979e7fc31ba7a5b5e5707b29c8a99e5dbf8a8392a33"
-dependencies = [
- "cc",
- "libc",
-]
Index: elan-1.3.1/src/elan-dist/Cargo.toml
===
--- elan-1.3.1.orig/src/elan-dist/Cargo.toml
+++ elan-1.3.1/src/elan-dist/Cargo.toml
@@ -14,7 +14,6 @@ itertools = "0.10.0"
url = "2.2.1"
tar = "0.4.33"
flate2 = "1.0.14"
-zstd = "0.9"
walkdir = "2.3.1"
toml = "0.5.8"
sha2 = ">= 0.9.2, <0.11"
Index: elan-1.3.1/src/elan-dist/src/component/package.rs
===
--- elan-1.3.1.orig/src/elan-dist/src/component/package.rs
+++ elan-1.3.1/src/elan-dist/src/component/package.rs
@@ -4,7 +4,6 @@
extern crate filetime;
extern crate flate2;
-extern crate zstd;
extern crate tar;
use errors::*;
@@ -140,21 +139,6 @@ impl<'a> TarGzPackage<'a> {
TarPackage::unpack(stream, path)
}
-pub fn unpack_file(path: , into: ) -> Result<()> {
-let file = File::open(path).chain_err(|| ErrorKind::ExtractingPackage)?;
-Self::unpack(file, into)
-}
-}
-
-#[derive(Debug)]
-pub struct TarZstdPackage<'a>(TarPackage<'a>);
-
-impl<'a> TarZstdPackage<'a> {
-pub fn unpack(stream: R, path: ) -> Result<()> {
-let stream = zstd::stream::read::Decoder::new(stream)?;
-
-TarPackage::unpack(stream, path)
-}
pub fn unpack_file(path: , into: ) -> Result<()> {
let file = File::open(path).chain_err(|| ErrorKind::ExtractingPackage)?;
Self::unpack(file, into)
Index: elan-1.3.1/src/elan-dist/src/download.rs
===
--- elan-1.3.1.orig/src/elan-dist/src/download.rs
+++ elan-1.3.1/src/elan-dist/src/download.rs
@@ -99,9 +99,9 @@ impl<'a> DownloadCfg<'a> {
Ok(())
}
-pub fn download_and_check(, url_str: ) -> Result> {
+pub fn download_and_check(, url_str: , ext: ) -> Result> {
let url = utils::parse_url(url_str)?;
-let file = self.temp_cfg.new_file()?;
+let file = self.temp_cfg.new_file_with_ext("", ext)?;
utils::download_file(, , None, &|n| (self.notify_handler)(n.into()))?;
Index: elan-1.3.1/src/elan-dist/src/manifestation.rs
===
--- elan-1.3.1.orig/src/elan-dist/src/manifestation.rs
+++ elan-1.3.1/src/elan-dist/src/manifestation.rs
@@ -1,6 +1,6 @@
//! Manifest a particular Lean version by installing it from a distribution server.
-use component::{TarGzPackage, TarZstdPackage, ZipPackage};
+use component::{TarGzPackage, ZipPackage};
use download::DownloadCfg;
use elan_utils::utils;
use errors::*;
@@
Bug#1007929: netcfg: FTBFS on s390x
Control: tags -1 + pending
> Samuel Thibault wrote (Sun, 20 Mar 2022 01:01:07
> +0100):
> > Cyril Brulebois, le sam. 19 mars 2022 16:32:06 +0100, a ecrit:
> > > > Running suite(s): inet_mton
> > > > 95%: Checks: 24, Failures: 1, Errors: 0
> > > > test/test_netcfg_gateway_reachable.c:94:F:netcfg_gateway_reachable:test_netcfg_gateway_reachable_v6_fe80:0:
> > > > Gateway erroneously unreachable
> > > > make[1]: *** [test/tests.mk:19: test] Error 1
> > > > make[1]: Leaving directory '/<>'
> > > > dh_auto_test: error: make -j1 test returned exit code 2
> > > > make: *** [debian/rules:6: build-arch] Error 25
> > >
> > > Paging Samuel & Igor, hunch says this might be related:
> > >
> > > commit 3549f77c39c06e7dfcfd59fce01ff2d4a0622058
> > > Merge: 90e52aed 6bff2dee
> > > Author: Samuel Thibault
> > > Date: Sun Sep 5 14:59:46 2021 +
> > >
> > > Merge branch 'ipv6-link-local-gateway' into 'master'
> > >
> > > Add support for fe80::/10 addresses as IPv6 gateway, closes
> > > #901255
> > >
> > > See merge request installer-team/netcfg!3
> >
> > I committed
> >
> > -if ((ntohs(gw_addr.in6.s6_addr32[0]) & 0xffc0) == (0xfe80 &
> > 0xffc0)) {
> > +if ((ntohl(gw_addr.in6.s6_addr32[0]) & 0xffc0) == (0xfe80 &
> > 0xffc0)) {
> >
> > which is required for the test to work at all indeed. I guess that'll
> > just fix the issue.
>
> I intended to upload netcfg, but build still fails, apparently with the same
> error:
Oh, now I see it: it was indeed intended to be a ntohs since it's a
16bit value which it was compared to. It's the field name that was
bogus, now fixed.
Samuel
Processed: Re: Bug#1007929: netcfg: FTBFS on s390x
Processing control commands: > tags -1 + pending Bug #1007929 [src:netcfg] netcfg: FTBFS on s390x Added tag(s) pending. -- 1007929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1012275
Processing commands for cont...@bugs.debian.org: > tags 1012275 - ftbfs Bug #1012275 [firefox] firefox: new upstream version fixes possible RCE security holes Removed tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1007929: netcfg: FTBFS on s390x
Processing control commands: > tags -1 - pending Bug #1007929 [src:netcfg] netcfg: FTBFS on s390x Removed tag(s) pending. -- 1007929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 1012275 with 1012197
Processing commands for cont...@bugs.debian.org: > block 1012275 with 1012197 Bug #1012275 [firefox] firefox: new upstream version fixes possible RCE security holes 1012275 was not blocked by any bugs. 1012275 was not blocking any bugs. Added blocking bug(s) of 1012275: 1012197 > thanks Stopping processing here. Please contact me if you need assistance. -- 1012275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012279: php-horde-turba: CVE-2022-30287
Source: php-horde-turba Version: 4.2.25-5 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for php-horde-turba, CVE-2022-30287[0]. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-30287 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-30287 [1] https://blog.sonarsource.com/horde-webmail-rce-via-email/ [2] https://lists.horde.org/archives/horde/Week-of-Mon-20220530/059225.html [3] https://github.com/horde/turba/pull/7 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1004913: closing 1004913
close 1004913 2.1.6-1 thanks
Processed: closing 1004913
Processing commands for cont...@bugs.debian.org: > close 1004913 2.1.6-1 Bug #1004913 [python-fysom] python-fysom: incompatible import from collections in py3.10 There is no source info for the package 'python-fysom' at version '2.1.6-1' with architecture '' Unable to make a source version for version '2.1.6-1' Marked as fixed in versions 2.1.6-1. Bug #1004913 [python-fysom] python-fysom: incompatible import from collections in py3.10 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1004913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1004913
Processing commands for cont...@bugs.debian.org: > tags 1004913 = pending Bug #1004913 [python-fysom] python-fysom: incompatible import from collections in py3.10 Added tag(s) pending; removed tag(s) bookworm and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 1004913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008361: marked as done (rubygems: FTBFS: ERROR: Test "ruby3.0" failed.)
Your message dated Thu, 02 Jun 2022 19:49:46 + with message-id and subject line Bug#1008361: fixed in rubygems 3.3.15-1 has caused the Debian Bug report #1008361, regarding rubygems: FTBFS: ERROR: Test "ruby3.0" 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.) -- 1008361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rubygems Version: 3.3.5-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.0 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-bundler/usr/share/rubygems-integration/all:/<>/debian/ruby-rubygems/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"rubygems-update\" > GEM_PATH=/<>/debian/ruby-bundler/usr/share/rubygems-integration/all:/<>/debian/ruby-rubygems/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"bundler\" > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=. > GEM_PATH=/<>/debian/ruby-bundler/usr/share/rubygems-integration/all:/<>/debian/ruby-rubygems/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -S rake -f debian/ruby-tests.rake > mv bundler/spec/realworld/fixtures/warbler/Gemfile.lock > bundler/spec/realworld/fixtures/warbler/.gem2deb.Gemfile.lock > Loaded suite > /usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader > Started > ... > ... > .P > === > Pending: test_extract_symlink_parent_doesnt_delete_user_dir(TestGemPackage): > TMPDIR seems too long to add it as symlink into tar > /<>/test/rubygems/test_gem_package.rb:605:in > `test_extract_symlink_parent_doesnt_delete_user_dir' > 602: destination_user_subdir = File.join destination_user_dir, 'dir' > 603: FileUtils.mkdir_p destination_user_subdir > 604: > => 605: pend "TMPDIR seems too long to add it as symlink into tar" if > destination_user_dir.size > 90 > 606: > 607: tgz_io = util_tar_gz do |tar| > 608: tar.add_symlink 'link', destination_user_dir, 16877 > === > ... > ... > ... > ... > ... > ... > ... >
Bug#1011308: (no subject)
The bug is currently fixed in trafficserver 9.1.2+ds-7 into unstable. Due to the ongoing openssl transition, its migration to testing is however blocked. I'll continue to monitor package status to prevent it from being removed from testing if possible. Best, Jean Baptiste OpenPGP_signature Description: OpenPGP digital signature
Processed: severity of 1010764 is serious
Processing commands for cont...@bugs.debian.org: > severity 1010764 serious Bug #1010764 [openafs-modules-dkms] openafs-modules-dkms: module fails to build for kernel 5.17.0-1-amd64 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1010764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:mumble
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:mumble > # 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 #1005719 (http://bugs.debian.org/1005719) > # Bug title: mumble: FTBFS with OpenSSL 3.0 > # * https://github.com/mumble-voip/mumble/pull/5354 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1005719 + fixed-upstream Bug #1005719 [src:mumble] mumble: FTBFS with OpenSSL 3.0 Added tag(s) fixed-upstream. > usertags 1005719 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1005719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012277: hipspy fails with astropy 5.1
Source: hipspy Version: 0.2-3 Severity: serious Tags: upstream ftbfs Since the installation of astropy 5.1, hipspy fails its tests. The first error is ImportError while loading conftest '/usr/lib/python3/dist- packages/hips/conftest.py'. /usr/lib/python3/dist-packages/hips/conftest.py:6: in from astropy.tests.plugins.display import PYTEST_HEADER_MODULES, TESTED_VERSIONS E ModuleNotFoundError: No module named 'astropy.tests.plugins' however after fixing this, other appear. The same happens now when hipspy is compiled on unstable. Since it is unclear whether hipspy still gets upstream support in the future (and therefore it is worth fixing), this bug is to autoremove hipspy from testing and let astropy migrate. Discussion about hipspys future: https://github.com/hipspy/hips/issues/153
Bug#1012275: firefox: new upstream version fixes possible RCE security holes
Package: firefox Version: 100.0.2-1 Severity: serious Tags: security ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: Debian Security Team Hi. Would be good to see 101 packaged ASAP, as it fixes numerous issues, including some which are apparently thought to allow remote code execution. Cheers, Chris.
Bug#1011884: [Pkg-javascript-devel] Bug#1011884: coffeescript: FTBFS: /bin/sh: 1: /usr/bin/licensecheck: not found
On 02/06/2022 14:31, Jonas Smedegaard wrote:
Quoting Yadd (2022-06-02 12:39:07)
can I switch this package from cdbs to debhelper+dh-sequence-nodejs ?
Please remove my name as maintainer, and maintain it however you like.
...or if you have no need for the package yourself either, then consider
dropping it: I suspect ot is obsolete nowadays.
I updated it, thanks:
* just fix build in unstable
* updated to last version in experimental (upstream renamed its module
from coffee-script to coffeescript). I added a transitional
coffee-script module, just a simple:
module.exports=require("coffeescript")
Only these packages need a little fix for coffeescript 2.7:
* node-cson-parser
* node-grunt-contrib-coffee
* node-turbolinks
* node-xml2js
Cheers,
Yadd
$ rdepends coffeescript
Reverse-Testsuite-Triggers
* node-transformers (for coffeescript)
Reverse-Build-Depends
* backbone (for coffeescript)
* camo (for coffeescript)
* jquery-caret.js (for coffeescript)
* libjs-chosen (for coffeescript)
* node-bootstrap-tour (for coffeescript)
* node-browserify (for coffeescript)
* node-bufferjs (for coffeescript)
* node-coffee-loader(for coffeescript)
* node-coffeeify(for coffeescript)
* node-cson-parser (for coffeescript)
* node-error-ex (for coffeescript)
* node-esutils (for coffeescript)
* node-fuzzaldrin-plus (for coffeescript)
* node-grunt-contrib-coffee (for coffeescript)
* node-gulp-coffee (for coffeescript)
* node-iferr(for coffeescript)
* node-is-arrayish (for coffeescript)
* node-js-tokens(for coffeescript)
* node-node-localstorage(for coffeescript)
* node-performance-now (for coffeescript)
* node-require-dir (for coffeescript)
* node-rewire (for coffeescript)
* node-shelljs (for coffeescript)
* node-simple-swizzle (for coffeescript)
* node-sockjs (for coffeescript)
* node-transformers (for coffeescript)
* node-turbolinks (for coffeescript)
* node-xml2js (for coffeescript)
* ntopng(for coffeescript)
* roundcube-plugins-extra (for coffeescript)
* ruby-execjs (for libjs-coffeescript)
* sockjs-client (for coffeescript)
Reverse-Recommends
* node-jake (for coffeescript)
Reverse-Depends
* node-coffee-loader(for coffeescript)
* node-coffeeify(for coffeescript)
* node-cson-parser (for coffeescript)
* node-grunt-contrib-coffee (for coffeescript)
* node-gulp-coffee (for coffeescript)
* ruby-coffee-script-source (for libjs-coffeescript)
Bug#1012254: libtesseract5: FTBFS armel architecture
>> On Thu, 02 Jun 2022 11:47:36 +0200 Christian Marillat >> wrote: >> BTW the debian/rules is completely outdated (Still use the deprecated >> debhelper 9). You must not use configure/autotools build but cmake. > That is a bit of a strong statement. As long as upstream keeps the autotools > build > systems you can still use that. The concern about debhelper is valid though. The configure script doesnt have an option to unset neon when a simple -DHAVE_NEON=FALSE work with cmake. Christian
Bug#1011884: marked as done (coffeescript: FTBFS: /bin/sh: 1: /usr/bin/licensecheck: not found)
Your message dated Thu, 02 Jun 2022 15:18:56 +
with message-id
and subject line Bug#1011884: fixed in coffeescript 1.12.8~dfsg-7
has caused the Debian Bug report #1011884,
regarding coffeescript: FTBFS: /bin/sh: 1: /usr/bin/licensecheck: not found
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.)
--
1011884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011884
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: coffeescript
Version: 1.12.8~dfsg-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> CDBS WARNING: copyright-check disabled - licensecheck is missing.
> test -x debian/rules
> dh_testroot
> dh_prep
> dh_installdirs -A
> mkdir -p "."
>
> Scanning upstream source for new/changed copyright notices...
>
> set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive
> --copyright --deb-fmt --ignore
> '^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 -- * |
> /usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
> /bin/sh: 1: /usr/bin/licensecheck: not found
> 0 combinations of copyright and licensing found.
> No new copyright notices found - assuming no news is good news...
> touch debian/stamp-copyright-check
> mkdir -p "debian/upstream-cruft"
> cp -a "lib" "debian/upstream-cruft/lib";
> touch debian/stamp-upstream-cruft
> mkdir -p docs/v1/browser-compiler
> chmod +x bin/cake
> bin/cake build
> bin/cake build
> MINIFY=false bin/cake build:browser
> bin/cake test
> [0;31mfailed 1 and passed 855 tests in 1.87 seconds[0m[0m
>
> [0;31m reads history file[0m
> [0;31m TypeError: Cannot read properties of undefined (reading 'history')
> at /<>/test/repl.coffee:1:1
> at Function. (/<>/test/repl.coffee:1:1)
> at global.test (/<>/Cakefile:1:1)
> at testRepl (/<>/test/repl.coffee:1:1)
> at Object. (/<>/test/repl.coffee:1:1)
> at Object. (/<>/test/repl.coffee:1:1)
> at Module._compile (node:internal/modules/cjs/loader:1:1)
> at Object.exports.run
> (/<>/lib/coffee-script/coffee-script.js:1:1)
> at runTests (/<>/Cakefile:1:1)
> at Object.action (/<>/Cakefile:1:1)
> at invoke (/<>/lib/coffee-script/cake.js:1:1)
> at Object.exports.run (/<>/lib/coffee-script/cake.js:1:1)
> at Object. (/<>/bin/cake:1:1)
> at Module._compile (node:internal/modules/cjs/loader:1:1)
> at Object.Module._extensions..js (node:internal/modules/cjs/loader:1:1)
> at Module.load (node:internal/modules/cjs/loader:1:1)
> at Function.Module._load (node:internal/modules/cjs/loader:1:1)
> at Function.executeUserEntryPoint [as runMain]
> (node:internal/modules/run_main:1:1)
> at node:internal/main/run_main_module:1:1
> [0m
> function() {
> return fn(input, output, repl);
> }
> make: *** [debian/rules:37: debian/stamp-build] Error 1
The full build log is available from:
http://qa-logs.debian.net/2022/05/25/coffeescript_1.12.8~dfsg-6_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: coffeescript
Source-Version: 1.12.8~dfsg-7
Done: Yadd
We believe that the bug you reported is fixed in the latest version of
coffeescript, 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 1011...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yadd (supplier of updated coffeescript package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the
Bug#1010140: aqsis: FTBFS on arm{el,hf}
Package: aqsis Version: 1.8.2+git20210815 Followup-For: Bug #1010140 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic ubuntu-patch Control: tags -1 patch Dear Maintainer, In Ubuntu, we fixed this FTBFS with the following patch, it was published successfully (https://launchpad.net/ubuntu/+source/aqsis/1.8.2+git20210815-1ubuntu1) Thanks for considering the patch. -- System Information: Debian Release: bookworm/sid APT prefers jammy-updates APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'), (100, 'jammy-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-30-generic (SMP w/16 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru aqsis-1.8.2+git20210815/debian/rules aqsis-1.8.2+git20210815/debian/rules --- aqsis-1.8.2+git20210815/debian/rules2022-03-05 22:02:59.0 +0100 +++ aqsis-1.8.2+git20210815/debian/rules2022-05-27 09:24:01.0 +0200 @@ -17,10 +17,16 @@ %: dh $@ --buildsystem=cmake +ifeq ($(DEB_HOST_ARCH), armhf) +AQSIS_USE_QT=OFF +else +AQSIS_USE_QT=ON +endif + override_dh_auto_configure: dh_auto_configure -- \ -DSYSCONFDIR=/etc/aqsis \ - -DAQSIS_USE_QT:BOOL=ON \ + -DAQSIS_USE_QT:BOOL=$(AQSIS_USE_QT) \ -DAQSIS_USE_EXTERNAL_TINYXML:BOOL=ON \ -DAQSIS_USE_PDIFF:BOOL=OFF \ -DAQSIS_USE_RPATH:BOOL=OFF
Processed: Re: aqsis: FTBFS on arm{el,hf}
Processing control commands:
> tags -1 patch
Bug #1010140 [src:aqsis] aqsis: FTBFS on arm{el,hf}
Added tag(s) patch.
--
1010140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010140
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1005650: marked as done (squid: FTBFS with OpenSSL 3.0)
Your message dated Thu, 02 Jun 2022 14:39:07 + with message-id and subject line Bug#1005650: fixed in squid 5.5-1.1 has caused the Debian Bug report #1005650, regarding squid: FTBFS with OpenSSL 3.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1005650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: squid Version: 5.2-1 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 control: forwarded -1 https://bugs.squid-cache.org/show_bug.cgi?id=5133 Your package is failing to build using OpenSSL 3.0 with the following error: | ../../src/security/forward.h: In function ‘void Security::DH_free_cpp(DH*)’: | ../../src/security/LockingPointer.h:34:21: error: ‘void DH_free(DH*)’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] |34 | function(a); \ | ../../src/security/forward.h:96:1: note: in expansion of macro ‘CtoCpp1’ |96 | CtoCpp1(DH_free, DH *); | | ^~~ | In file included from ../../compat/openssl.h:33, | from ../../src/security/Context.h:15, | from ../../src/security/forward.h:14, | from ../../src/SquidConfig.h:26, | from old_api.cc:24: | /usr/include/openssl/dh.h:200:28: note: declared here | 200 | OSSL_DEPRECATEDIN_3_0 void DH_free(DH *dh); | |^~~ | In file included from ../../src/ssl/support.h:21, | from ../../src/SquidConfig.h:29, | from old_api.cc:24: | ../../src/ssl/gadgets.h:60:51: error: ‘void RSA_free(RSA*)’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] |60 | typedef std::unique_ptr> RSA_Pointer; | | ^~~~ | In file included from /usr/include/openssl/x509.h:36, | from /usr/include/openssl/ssl.h:31, | from ../../compat/openssl.h:42, | from ../../src/security/Context.h:15, | from ../../src/security/forward.h:14, | from ../../src/SquidConfig.h:26, | from old_api.cc:24: For more information see: https://www.openssl.org/docs/man3.0/man7/migration_guide.html Sebastian --- End Message --- --- Begin Message --- Source: squid Source-Version: 5.5-1.1 Done: Nicholas Guriev We believe that the bug you reported is fixed in the latest version of squid, 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 1005...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicholas Guriev (supplier of updated squid package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 31 May 2022 23:13:38 +0300 Source: squid Architecture: source Version: 5.5-1.1 Distribution: unstable Urgency: medium Maintainer: Luigi Gangitano Changed-By: Nicholas Guriev Closes: 1005650 Changes: squid (5.5-1.1) unstable; urgency=medium . * Non-maintainer upload. . [ Nicholas Guriev ] * Fixing build against OpenSSL 3.0 (Closes: #1005650, LP: #1946205) . * debian/rules - Do not fail on errors about deprecated declarations from OpenSSL. - Remove -Wall in CFLAGS from the debian/rules file since upstream build scripts already pass this flag. . * debian/patches/ - New 0006-Fix-build-against-OpenSSL-3-0.patch . [ Simon Deziel ] * apparmor: allow reading /etc/ssl/openssl.cnf Checksums-Sha1: 2b58259c8997f049674d9f34be8e96f4ca05cec7 2801 squid_5.5-1.1.dsc 94bdeb7a22c4dba1f05629df804f26929b195d82 44024 squid_5.5-1.1.debian.tar.xz 017d9b6d96174cf1fc4724b514825761c779c275 6398 squid_5.5-1.1_source.buildinfo Checksums-Sha256: 1c58123666a9fdd667643c6fcaf6d0db6ae30f43af568f4f3862ae7c8b284a95 2801 squid_5.5-1.1.dsc 62eadbf0df4eb162a9d3a453ea474cbd936498e88cd4b2a988313755ecacd3fd 44024 squid_5.5-1.1.debian.tar.xz 0c03d3ce132396b28cf9194665d102bd5e27d253adbc0f7f982d78bee093e7c5 6398 squid_5.5-1.1_source.buildinfo Files: cc130680af6cf760b6ab8f2d0cbf912e 2801 web optional squid_5.5-1.1.dsc
Bug#995659: marked as done (coturn: FTBFS with OpenSSL 3.0)
Your message dated Thu, 02 Jun 2022 14:34:00 +
with message-id
and subject line Bug#995659: fixed in coturn 4.5.2-3.1
has caused the Debian Bug report #995659,
regarding coturn: FTBFS with OpenSSL 3.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
995659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: coturn
Version: 4.5.2-3
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
src/client/ns_turn_msg.c: In function stun_produce_integrity_key_str:
src/client/ns_turn_msg.c:260:7: warning: implicit declaration of function
FIPS_mode [-Wimplicit-function-declaration]
260 | if (FIPS_mode()) {
| ^
[...]
/usr/bin/ld: lib/libturnclient.a(ns_turn_msg.o): in function
`stun_produce_integrity_key_str':
./src/client/ns_turn_msg.c:260: undefined reference to `FIPS_mode'
collect2: error: ld returned 1 exit status
For more information see:
https://www.openssl.org/docs/man3.0/man7/migration_guide.html
Kurt
--- End Message ---
--- Begin Message ---
Source: coturn
Source-Version: 4.5.2-3.1
Done: Nicholas Guriev
We believe that the bug you reported is fixed in the latest version of
coturn, 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 995...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nicholas Guriev (supplier of updated coturn package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 02 Jun 2022 13:36:34 +0300
Source: coturn
Architecture: source
Version: 4.5.2-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team
Changed-By: Nicholas Guriev
Closes: 995659
Changes:
coturn (4.5.2-3.1) unstable; urgency=medium
.
* Non-maintainer upload.
* [518094e] New No-FIPS-140-mode.patch fixes build against OpenSSL 3.0
(Closes: #995659, LP: #1967018)
Checksums-Sha1:
d2a4ff5c809007f69f78acbd858d790c41329d6a 2053 coturn_4.5.2-3.1.dsc
9890542f228e8b863a0452c1de43b025825ac677 15256 coturn_4.5.2-3.1.debian.tar.xz
b1ce8181590b3f61cc853e6826df3c457fa84704 5630 coturn_4.5.2-3.1_source.buildinfo
Checksums-Sha256:
38a37b86a632cf788a7ca07e182f117f97ac538560c105c2f7103fa273b7de17 2053
coturn_4.5.2-3.1.dsc
a833e8e6af59044b1ddc884fab846aebcc211149e5e55e0edf0e35fcb21946bd 15256
coturn_4.5.2-3.1.debian.tar.xz
c0cd53d41ba8e8b639621e34e852f27899effee83081a177d3b33640c6be3db7 5630
coturn_4.5.2-3.1_source.buildinfo
Files:
75f1f5e0dc935a6957f9a3f2c8d86780 2053 net optional coturn_4.5.2-3.1.dsc
fe20266085570976f90b182fc973156c 15256 net optional
coturn_4.5.2-3.1.debian.tar.xz
9c22794519c58f9b5188a7a37b2de9a2 5630 net optional
coturn_4.5.2-3.1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmKYyV0QHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFFzGDACPMkXSA84KA/bFh2wOz+yLk/DG7CMgg0eD
yvvc/1UXMP6R52njVhLe0g/tSRCvOvTKDMnpI6ehF6+mhqT4wxDtmFYhAprS0GoD
CMu8qXkdCZqDhr/fi1s4HGoIctUHaC/MyFnv+5HyQ226GqRGbmBnAsTiHkvVuXQ5
EtRFoBfHmeI0elzmd30pgtCplLkv16Oepm4cfcnxEbmEfg2U7f3cfO3zOj4e3zC3
7cWmRIScHLo5BHWA8im69WvWpC7ChOpAGwMyKQ3BsyoVhmZTCT8F7TjMW+ZVKKS5
NJrde654o83Ru+Dda/JUvEE1Grmr73/sWJsYY4amPQJ5VF2kllsbxuaCRZYfZlyh
VqWr3d4iqst3J24Whq22LBW7/S0UAfCUmbQOZa7QDqHyQ53A+gwWXUcICeq5BWG2
BoPSEp+dTwnajRtNNvILjOJxnpjNnUfYvrrCx+ccv9/oMhYJ1E3qod/ejYuHfBWb
5HWBinxc43hCJfTgA2PPelqRgDfYPkU=
=fOfi
-END PGP SIGNATURE End Message ---
Bug#995659: NMU: coturn: FTBFS with OpenSSL 3.0
On Thu, 02 Jun 2022 13:10:27 +0300 Nicholas Guriev wrote:
Please consider to apply my patch fixing build against newest OpenSSL.
The patch refers to the OPENSSL_FIPS macro that used to be in ancient
OpenSSL source code. This fix does not change behaviour because
the FIPS_mode() function always returned zero.
I am sponsoring this. Please find the debdiff attached.diff -Nru coturn-4.5.2/debian/changelog coturn-4.5.2/debian/changelog
--- coturn-4.5.2/debian/changelog 2021-03-24 20:30:23.0 +0100
+++ coturn-4.5.2/debian/changelog 2022-06-02 12:36:34.0 +0200
@@ -1,3 +1,11 @@
+coturn (4.5.2-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * [518094e] New No-FIPS-140-mode.patch fixes build against OpenSSL 3.0
+(Closes: #995659, LP: #1967018)
+
+ -- Nicholas Guriev Thu, 02 Jun 2022 13:36:34 +0300
+
coturn (4.5.2-3) unstable; urgency=medium
[ Ferenc Wágner ]
diff -Nru coturn-4.5.2/debian/patches/No-FIPS-140-mode.patch
coturn-4.5.2/debian/patches/No-FIPS-140-mode.patch
--- coturn-4.5.2/debian/patches/No-FIPS-140-mode.patch 1970-01-01
01:00:00.0 +0100
+++ coturn-4.5.2/debian/patches/No-FIPS-140-mode.patch 2022-06-02
12:36:34.0 +0200
@@ -0,0 +1,31 @@
+From: Nicholas Guriev
+Date: Thu, 02 Jun 2022 12:34:17 +0300
+Subject: Do not check FIPS 140 mode
+ It is not available in OpenSSL as packaged in Debian. The OPENSSL_FIPS macro
+ appeared in ancient OpenSSL sources but was never defined.
+ https://sources.debian.org/src/openssl/1.1.1n-0%2Bdeb11u2/crypto/o_fips.c/
+
+---
+ src/client/ns_turn_msg.c |4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+--- a/src/client/ns_turn_msg.c
b/src/client/ns_turn_msg.c
+@@ -244,7 +244,7 @@ int stun_produce_integrity_key_str(const
+ unsigned int keylen = 0;
+ EVP_MD_CTX ctx;
+ EVP_MD_CTX_init();
+-#if defined EVP_MD_CTX_FLAG_NON_FIPS_ALLOW &&
!defined(LIBRESSL_VERSION_NUMBER)
++#ifdef OPENSSL_FIPS
+ if (FIPS_mode()) {
+
EVP_MD_CTX_set_flags(,EVP_MD_CTX_FLAG_NON_FIPS_ALLOW);
+ }
+@@ -256,7 +256,7 @@ int stun_produce_integrity_key_str(const
+ #else
+ unsigned int keylen = 0;
+ EVP_MD_CTX *ctx = EVP_MD_CTX_new();
+-#if defined EVP_MD_CTX_FLAG_NON_FIPS_ALLOW && !
defined(LIBRESSL_VERSION_NUMBER)
++#ifdef OPENSSL_FIPS
+ if (FIPS_mode()) {
+ EVP_MD_CTX_set_flags(ctx,
EVP_MD_CTX_FLAG_NON_FIPS_ALLOW);
+ }
diff -Nru coturn-4.5.2/debian/patches/series coturn-4.5.2/debian/patches/series
--- coturn-4.5.2/debian/patches/series 2021-02-10 20:05:50.0 +0100
+++ coturn-4.5.2/debian/patches/series 2022-06-02 12:36:34.0 +0200
@@ -1,2 +1,3 @@
Set-logging-to-syslog.patch
Fix-undefinded-OPENSSL_VERSION_1_1_1.patch
+No-FIPS-140-mode.patch
Bug#1005650: NMU: squid: FTBFS with OpenSSL 3.0
On Wed, 01 Jun 2022 20:17:52 +0300 Nicholas Guriev wrote:
To fix FTBFS of the squid package, I offer to apply my changes with the
-Wno-error=deprecated-declarations flag and an original patch. This will
allow us to proceed with the OpenSSL transition.
See also my MR on Salsa.
https://salsa.debian.org/squid-team/squid/-/merge_requests/20
I am sponsoring this. Please find a debdiff attached.diff -Nru squid-5.5/debian/changelog squid-5.5/debian/changelog
--- squid-5.5/debian/changelog 2022-04-15 14:39:54.0 +0200
+++ squid-5.5/debian/changelog 2022-05-31 22:13:38.0 +0200
@@ -1,3 +1,23 @@
+squid (5.5-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Nicholas Guriev ]
+ * Fixing build against OpenSSL 3.0 (Closes: #1005650, LP: #1946205)
+
+ * debian/rules
+- Do not fail on errors about deprecated declarations from OpenSSL.
+- Remove -Wall in CFLAGS from the debian/rules file since upstream build
+ scripts already pass this flag.
+
+ * debian/patches/
+- New 0006-Fix-build-against-OpenSSL-3-0.patch
+
+ [ Simon Deziel ]
+ * apparmor: allow reading /etc/ssl/openssl.cnf
+
+ -- Nicholas Guriev Tue, 31 May 2022 23:13:38 +0300
+
squid (5.5-1) unstable; urgency=medium
[ Amos Jeffries ]
diff -Nru squid-5.5/debian/patches/0006-Fix-build-against-OpenSSL-3-0.patch
squid-5.5/debian/patches/0006-Fix-build-against-OpenSSL-3-0.patch
--- squid-5.5/debian/patches/0006-Fix-build-against-OpenSSL-3-0.patch
1970-01-01 01:00:00.0 +0100
+++ squid-5.5/debian/patches/0006-Fix-build-against-OpenSSL-3-0.patch
2022-05-31 21:31:08.0 +0200
@@ -0,0 +1,210 @@
+From: Nicholas Guriev
+Date: Tue, 31 May 2022 22:31:08 +0300
+Subject: Make build against OpenSSL-3.0 possible
+ In OpenSSL, the SSL_get_ex_new_index macro (substituted to
+ CRYPTO_get_ex_new_index) requires CRYPTO_EX_dup as the second callback. This
+ typedef, for some reason, has got an extra asterisk near void* within
+ arguments into the third version. Freely conversions from void* to void** is
+ okay in C but prohibited in C++. So I've updated the callback prototype to
+ match the last OpenSSL version.
+ .
+ OpenSSL pre-3.0 defined all of the SSL_OP_* macros with numeric hexadecimal
+ literals. However, the third version uses there casting expressions with
+ shifts which preprocessor is unable to compute. So I check only macros
+ existence, this lets Squid accept obsolete options. But it's nothing,
+ OpenSSL should ignore them anyway.
+
+---
+ acinclude/lib-checks.m4 |2 -
+ src/security/PeerOptions.cc | 50
++--
+ src/ssl/support.cc |2 -
+ 3 files changed, 27 insertions(+), 27 deletions(-)
+
+--- a/acinclude/lib-checks.m4
b/acinclude/lib-checks.m4
+@@ -236,7 +236,7 @@ AC_DEFUN([SQUID_CHECK_OPENSSL_CONST_CRYP
+ AC_COMPILE_IFELSE([AC_LANG_PROGRAM([
+ #include
+
+-int const_dup_func(CRYPTO_EX_DATA *, const CRYPTO_EX_DATA *, void *, int,
long, void *) {
++int const_dup_func(CRYPTO_EX_DATA *, const CRYPTO_EX_DATA *, void **, int,
long, void *) {
+ return 0;
+ }
+ ],[
+--- a/src/security/PeerOptions.cc
b/src/security/PeerOptions.cc
+@@ -297,130 +297,130 @@ static struct ssl_option {
+
+ } ssl_options[] = {
+
+-#if SSL_OP_NETSCAPE_REUSE_CIPHER_CHANGE_BUG
++#ifdef SSL_OP_NETSCAPE_REUSE_CIPHER_CHANGE_BUG
+ {
+ "NETSCAPE_REUSE_CIPHER_CHANGE_BUG",
SSL_OP_NETSCAPE_REUSE_CIPHER_CHANGE_BUG
+ },
+ #endif
+-#if SSL_OP_SSLREF2_REUSE_CERT_TYPE_BUG
++#ifdef SSL_OP_SSLREF2_REUSE_CERT_TYPE_BUG
+ {
+ "SSLREF2_REUSE_CERT_TYPE_BUG", SSL_OP_SSLREF2_REUSE_CERT_TYPE_BUG
+ },
+ #endif
+-#if SSL_OP_MICROSOFT_BIG_SSLV3_BUFFER
++#ifdef SSL_OP_MICROSOFT_BIG_SSLV3_BUFFER
+ {
+ "MICROSOFT_BIG_SSLV3_BUFFER", SSL_OP_MICROSOFT_BIG_SSLV3_BUFFER
+ },
+ #endif
+-#if SSL_OP_SSLEAY_080_CLIENT_DH_BUG
++#ifdef SSL_OP_SSLEAY_080_CLIENT_DH_BUG
+ {
+ "SSLEAY_080_CLIENT_DH_BUG", SSL_OP_SSLEAY_080_CLIENT_DH_BUG
+ },
+ #endif
+-#if SSL_OP_TLS_D5_BUG
++#ifdef SSL_OP_TLS_D5_BUG
+ {
+ "TLS_D5_BUG", SSL_OP_TLS_D5_BUG
+ },
+ #endif
+-#if SSL_OP_TLS_BLOCK_PADDING_BUG
++#ifdef SSL_OP_TLS_BLOCK_PADDING_BUG
+ {
+ "TLS_BLOCK_PADDING_BUG", SSL_OP_TLS_BLOCK_PADDING_BUG
+ },
+ #endif
+-#if SSL_OP_TLS_ROLLBACK_BUG
++#ifdef SSL_OP_TLS_ROLLBACK_BUG
+ {
+ "TLS_ROLLBACK_BUG", SSL_OP_TLS_ROLLBACK_BUG
+ },
+ #endif
+-#if SSL_OP_ALL
++#ifdef SSL_OP_ALL
+ {
+ "ALL", (long)SSL_OP_ALL
+ },
+ #endif
+-#if SSL_OP_SINGLE_DH_USE
++#ifdef SSL_OP_SINGLE_DH_USE
+ {
+ "SINGLE_DH_USE", SSL_OP_SINGLE_DH_USE
+ },
+ #endif
+-#if SSL_OP_EPHEMERAL_RSA
++#ifdef SSL_OP_EPHEMERAL_RSA
+ {
+ "EPHEMERAL_RSA", SSL_OP_EPHEMERAL_RSA
+ },
+ #endif
+-#if SSL_OP_PKCS1_CHECK_1
++#ifdef SSL_OP_PKCS1_CHECK_1
+ {
+ "PKCS1_CHECK_1", SSL_OP_PKCS1_CHECK_1
+ },
+ #endif
+-#if SSL_OP_PKCS1_CHECK_2
++#ifdef SSL_OP_PKCS1_CHECK_2
+ {
Bug#1011867: marked as done (node-cbor: FTBFS: Error: Can't resolve 'stream' in '/<>/node_modules/nofilter/lib')
Your message dated Thu, 02 Jun 2022 13:05:11 +
with message-id
and subject line Bug#1011867: fixed in node-cbor 8.1.0+dfsg+~cs5.2.0-3
has caused the Debian Bug report #1011867,
regarding node-cbor: FTBFS: Error: Can't resolve 'stream' in
'/<>/node_modules/nofilter/lib'
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.)
--
1011867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011867
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-cbor
Version: 8.1.0+dfsg+~cs5.2.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 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_build --buildsystem=nodejs
> ./lerna.json found
>
> Found debian/nodejs/additional_components
> Found debian/nodejs/sovpro-delimited-stream/build
> cd ./sovpro-delimited-stream && sh -ex
> ../debian/nodejs/sovpro-delimited-stream/build
> + tsc
> Found debian/nodejs/packages/cbor-web/build
> cd ./packages/cbor-web && sh -ex
> ../../debian/nodejs/packages/cbor-web/build
> + webpack
> assets by status 41.8 KiB [cached] 1 asset
> runtime modules 670 bytes 3 modules
> modules by path ../cbor/lib/*.js 96.2 KiB
> ../cbor/lib/cbor.js 2.54 KiB [built] [code generated]
> ../cbor/lib/commented.js 8.7 KiB [built] [code generated]
> ../cbor/lib/decoder.js 20.1 KiB [built] [code generated]
> ../cbor/lib/tagged.js 10.5 KiB [built] [code generated]
> ../cbor/lib/simple.js 2.63 KiB [built] [code generated]
> ../cbor/lib/diagnose.js 6.46 KiB [built] [code generated]
> ../cbor/lib/encoder.js 30.9 KiB [built] [code generated]
> ../cbor/lib/map.js 5.06 KiB [built] [code generated]
> ../cbor/lib/utils.js 8.02 KiB [built] [code generated]
> ../cbor/lib/constants.js 1.32 KiB [built] [code generated]
> ./lib/cbor.js 21 bytes [built] [code generated]
> ../../node_modules/nofilter/lib/index.js 27.9 KiB [built] [code generated]
> ../cbor/vendor/binary-parse-stream/index.js 2.63 KiB [built] [code generated]
>
> ERROR in ../../node_modules/nofilter/lib/index.js 3:15-32
> Module not found: Error: Can't resolve 'stream' in
> '/<>/node_modules/nofilter/lib'
>
> BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core
> modules by default.
> This is no longer the case. Verify if you need this module and configure a
> polyfill for it.
>
> If you want to include a polyfill, you need to:
> - add a fallback 'resolve.fallback: { "stream":
> require.resolve("stream-browserify") }'
> - install 'stream-browserify'
> If you don't want to include a polyfill, you can use an empty module like
> this:
> resolve.fallback: { "stream": false }
> @ ../cbor/lib/commented.js 6:17-36
> @ ../cbor/lib/cbor.js 3:0-42
> @ ./lib/cbor.js 1:0-20 1:0-20
>
> ERROR in ../../node_modules/nofilter/lib/index.js 4:17-34
> Module not found: Error: Can't resolve 'buffer' in
> '/<>/node_modules/nofilter/lib'
>
> BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core
> modules by default.
> This is no longer the case. Verify if you need this module and configure a
> polyfill for it.
>
> If you want to include a polyfill, you need to:
> - add a fallback 'resolve.fallback: { "buffer":
> require.resolve("buffer/") }'
> - install 'buffer'
> If you don't want to include a polyfill, you can use an empty module like
> this:
> resolve.fallback: { "buffer": false }
> @ ../cbor/lib/commented.js 6:17-36
> @ ../cbor/lib/cbor.js 3:0-42
> @ ./lib/cbor.js 1:0-20 1:0-20
>
> ERROR in ../cbor/lib/commented.js 3:15-32
> Module not found: Error: Can't resolve 'stream' in
> '/<>/packages/cbor/lib'
>
> BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core
> modules by default.
> This is no longer the case. Verify if you need this module and configure a
> polyfill for it.
>
> If you want to include a polyfill, you need to:
> - add a fallback 'resolve.fallback: { "stream":
> require.resolve("stream-browserify") }'
> - install 'stream-browserify'
> If you don't want to include a polyfill, you can use an empty module like
> this:
> resolve.fallback: { "stream": false }
> @ ../cbor/lib/cbor.js 3:0-42
> @ ./lib/cbor.js 1:0-20 1:0-20
>
> ERROR in ../cbor/lib/commented.js 8:17-34
> Module not found: Error: Can't resolve 'buffer' in
> '/<>/packages/cbor/lib'
>
> BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core
> modules by
Processed: Bug#1011867 marked as pending in node-cbor
Processing control commands: > tag -1 pending Bug #1011867 [src:node-cbor] node-cbor: FTBFS: Error: Can't resolve 'stream' in '/<>/node_modules/nofilter/lib' Added tag(s) pending. -- 1011867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011867 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011867: marked as pending in node-cbor
Control: tag -1 pending Hello, Bug #1011867 in node-cbor 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/node-cbor/-/commit/00fb4ac7a87223255855d5a45a7dea9c7b506388 Fix configuration for webpack 5, add build dependencies to node-buffer and node-stream-browserify Closes: #1011867 (this message was generated automatically) -- Greetings https://bugs.debian.org/1011867
Bug#1012221: [Pkg-rust-maintainers] Bug#1012221: rust-stdweb-internal-macros (build-)depends on old version of rust-sha1.
fixed 1012221 thanks Le 01/06/2022 à 18:33, Peter Green a écrit : Package: rust-stdweb-internal-macros Version: 0.2.9-1 Severity: serious 4. Remove the stdweb features in instant and parking-lot and allow stdweb to be removed from testing. I think I implemented this solution. I opened #1012261 for the removal of the packages. Cheers, Sylvestre
Bug#1012221: marked as done (rust-stdweb-internal-macros (build-)depends on old version of rust-sha1.)
Your message dated Thu, 2 Jun 2022 14:29:45 +0200 with message-id <0c531c04-c678-052c-9309-7e28447ef...@debian.org> and subject line Re: [Pkg-rust-maintainers] Bug#1012221: rust-stdweb-internal-macros (build-)depends on old version of rust-sha1. has caused the Debian Bug report #1012221, regarding rust-stdweb-internal-macros (build-)depends on old version of rust-sha1. 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.) -- 1012221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012221 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rust-stdweb-internal-macros Version: 0.2.9-1 Severity: serious rust-stdweb-internal-macros depends on version 0.6 of rust-sha1 As I understand it the new version of rust-sha1 is a completely different code base with the old rust-sha1 having been renamed to sha1-smol stdweb appears to be unmaintained upstream https://rustsec.org/advisories/RUSTSEC-2020-0056.html and has an open soundness issue https://github.com/koute/stdweb/issues/411 No applications in Debian appear to use stdweb, Nevertheless this issue is blocking the migration of the new version of rust-sha1 to testing. Thanks to the use of collapse_features in instant and parking-lot it is also making the build-dependencies of debcargo unsatisfiable. Possible ways forward: 1. Attempt to port stdweb to the rustcrypto version of sha1 2. Introduce a sha1-0.6 package 3. Package sha1-smol and patch stdweb to use it 4. Remove the stdweb features in instant and parking-lot and allow stdweb to be removed from testing. Given the lack of upstream maintinance of stdweb i'm inclined towards option 4, does anyone else have any opinions before I go ahead and do it? --- End Message --- --- Begin Message --- fixed 1012221 thanks Le 01/06/2022 à 18:33, Peter Green a écrit : Package: rust-stdweb-internal-macros Version: 0.2.9-1 Severity: serious 4. Remove the stdweb features in instant and parking-lot and allow stdweb to be removed from testing. I think I implemented this solution. I opened #1012261 for the removal of the packages. Cheers, Sylvestre--- End Message ---
Bug#1012254: libtesseract5: FTBFS armel architecture
On Thu, 02 Jun 2022 11:47:36 +0200 Christian Marillat wrote: BTW the debian/rules is completely outdated (Still use the deprecated debhelper 9). You must not use configure/autotools build but cmake. That is a bit of a strong statement. As long as upstream keeps the autotools build systems you can still use that. The concern about debhelper is valid though. Please file a RFH if you do not have the time to keep the package in an acceptable shape.
Bug#1011884: [Pkg-javascript-devel] Bug#1011884: coffeescript: FTBFS: /bin/sh: 1: /usr/bin/licensecheck: not found
Quoting Yadd (2022-06-02 12:39:07) > can I switch this package from cdbs to debhelper+dh-sequence-nodejs ? Please remove my name as maintainer, and maintain it however you like. ...or if you have no need for the package yourself either, then consider dropping it: I suspect ot is obsolete nowadays. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Processed: severity of 1008992 is important, tagging 1008992
Processing commands for cont...@bugs.debian.org: > severity 1008992 important Bug #1008992 [xwayland] xwayland: all X clients hang indefinitely waiting for /tmp/.X11-unix/X0 Severity set to 'important' from 'grave' > tags 1008992 + moreinfo Bug #1008992 [xwayland] xwayland: all X clients hang indefinitely waiting for /tmp/.X11-unix/X0 Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 1008992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006343: marked as done (erlang-p1-tls: FTBFS with OpenSSL 3.0)
Your message dated Thu, 02 Jun 2022 12:04:29 +
with message-id
and subject line Bug#1006343: fixed in erlang-p1-tls 1.1.15-1
has caused the Debian Bug report #1006343,
regarding erlang-p1-tls: FTBFS with OpenSSL 3.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1006343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-p1-tls
Version: 1.1.13-2
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Your package is failing to build using OpenSSL 3.0. This was once filled
as #996274 and then closed "tried to reproduce this bug the package
built and tested successfully with OpenSSL 3.0.0.". I'm just double
checking that it was indeed tested against the OpenSSL version in
experimental. Below the build error and the links to the build logs:
| EUnit
| module 'fast_tls'
| fast_tls: transmission_with_client_certificate_test...*failed*
| in function fast_tls:transmission_test_with_opts/2 (fast_tls.erl, line 492)
| in call from eunit_test:'-mf_wrapper/2-fun-0-'/2 (eunit_test.erl, line 273)
| in call from eunit_test:run_testfun/1 (eunit_test.erl, line 71)
| in call from eunit_proc:run_test/1 (eunit_proc.erl, line 531)
| in call from eunit_proc:with_timeout/3 (eunit_proc.erl, line 356)
| in call from eunit_proc:handle_test/2 (eunit_proc.erl, line 514)
| in call from eunit_proc:tests_inorder/3 (eunit_proc.erl, line 456)
| in call from eunit_proc:with_timeout/3 (eunit_proc.erl, line 346)
| **error:{assertEqual,[{module,fast_tls},
| {line,492},
| {expression,"Msg"},
| {expected,<<"abcdefghi">>},
| {value,{error,<<"SSL_do_handshake failed: error:1"...>>,<<>>}}]}
| output:<<"">>
|
| fast_tls: transmission_without_client_certificate_test...[0.413 s] ok
| fast_tls: transmission_without_server_cert_fails_test...ok
| fast_tls: not_compatible_protocol_options_test...*failed*
| in function fast_tls:not_compatible_protocol_options_test/0 (fast_tls.erl,
line 510)
| in call from eunit_test:'-mf_wrapper/2-fun-0-'/2 (eunit_test.erl, line 273)
| in call from eunit_test:run_testfun/1 (eunit_test.erl, line 71)
| in call from eunit_proc:run_test/1 (eunit_proc.erl, line 531)
| in call from eunit_proc:with_timeout/3 (eunit_proc.erl, line 356)
| in call from eunit_proc:handle_test/2 (eunit_proc.erl, line 514)
| in call from eunit_proc:tests_inorder/3 (eunit_proc.erl, line 456)
| in call from eunit_proc:with_timeout/3 (eunit_proc.erl, line 346)
| **error:{assertMatch,[{module,fast_tls},
| {line,510},
| {expression,"Res"},
| {pattern,"{ badmatch , { error , _ } }"},
| {value,ok}]}
| output:<<"">>
|
| [done in 1.261 s]
| module 'p1_sha'
| p1_sha: sha1_test...ok
| p1_sha: sha224_test...ok
| p1_sha: sha256_test...ok
| p1_sha: sha384_test...ok
| p1_sha: sha512_test...ok
| p1_sha: to_hexlist_test...ok
| [done in 0.018 s]
| ===
| Failed: 2. Skipped: 0. Passed: 8.
Full build with OpenSSL 3.0.1 (experimental):
https://people.debian.org/~bigeasy/openssl-rebuild-3/attempted/erlang-p1-tls_1.1.13-2_amd64-2022-02-14T23:32:39Z
Full build with OpenSSL 1.1.1m (unstable):
https://people.debian.org/~bigeasy/openssl-rebuild-3/successful/erlang-p1-tls_1.1.13-2_amd64-2022-02-14T23:35:31Z
For more information see:
https://www.openssl.org/docs/man3.0/man7/migration_guide.html
Sebastian
--- End Message ---
--- Begin Message ---
Source: erlang-p1-tls
Source-Version: 1.1.15-1
Done: Philipp Huebner
We believe that the bug you reported is fixed in the latest version of
erlang-p1-tls, 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.
Philipp Huebner (supplier of updated erlang-p1-tls
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 02 Jun 2022 12:26:07 +0200
Source: erlang-p1-tls
Architecture: source
Version:
Bug#1012014: r8125: fails to build module for Linux 5.17
Followup-For: Bug #1012014 Control: tag -1 fixed-upstream A new upstream release is available since yesterday which is supposed to fix this. Andreas
Processed: Re: r8125: fails to build module for Linux 5.17
Processing control commands: > tag -1 fixed-upstream Bug #1012014 [src:r8125] r8125: fails to build module for Linux 5.17 Added tag(s) fixed-upstream. -- 1012014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012014 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011849: marked as done (node-change-case: FTBFS: error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type declarations.)
Your message dated Thu, 02 Jun 2022 10:50:47 + with message-id and subject line Bug#1011849: fixed in node-change-case 0.0~git20210510.c24a0e1-6 has caused the Debian Bug report #1011849, regarding node-change-case: FTBFS: error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type declarations. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1011849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-change-case Version: 0.0~git20210510.c24a0e1-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220525 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_build --buildsystem=nodejs > ./lerna.json found > > set -e; for c in `cat debian/nodejs/build_order;pkgjs-utils > components_list|grep -v -x -f debian/nodejs/build_order`; do \ > echo "# Building $c with tsc"; \ > (cd $c && tsc && tsc -P tsconfig.es2015.json); \ > done > # Building packages/lower-case with tsc > ../../node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find > module 'jest-matcher-utils' or its corresponding type declarations. > make[1]: *** [debian/rules:12: override_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2022/05/25/node-change-case_0.0~git20210510.c24a0e1-5_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: node-change-case Source-Version: 0.0~git20210510.c24a0e1-6 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-change-case, 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 1011...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-change-case package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 Jun 2022 12:19:55 +0200 Source: node-change-case Built-For-Profiles: nocheck Architecture: source Version: 0.0~git20210510.c24a0e1-6 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1011849 Changes: node-change-case (0.0~git20210510.c24a0e1-6) unstable; urgency=medium . * Team upload * Declare compliance with policy 4.6.1 * Fix build links (Closes: #1011849) Checksums-Sha1: dadfeecaa8f5123663faaf38cb41c34e8a36f418 2307 node-change-case_0.0~git20210510.c24a0e1-6.dsc fee0945f6c24bd6331eb8587a8a741db29318cb1 3280 node-change-case_0.0~git20210510.c24a0e1-6.debian.tar.xz Checksums-Sha256: 5159c69c4dd8801f8de8424895e24477746105437ea7391a17bc8f7add8404f3 2307 node-change-case_0.0~git20210510.c24a0e1-6.dsc 300852a40a12d3823bd4a2502224466a388e61b8b1758e98463a1276bf7525f5 3280 node-change-case_0.0~git20210510.c24a0e1-6.debian.tar.xz Files: d5f539537a5c2815c48320921266998f 2307 javascript optional node-change-case_0.0~git20210510.c24a0e1-6.dsc 322a23ac96a200c03964fe935e4a53ac 3280 javascript optional node-change-case_0.0~git20210510.c24a0e1-6.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmKYj5sACgkQ9tdMp8mZ 7unRyQ//SefA1dHh99aDzNy1A+91G/oaI8t25NSWz6k2kpFjuMzhuCFy/2XCDMPK RUrYw4C1WAlZfSmJSg8DbcxtOBI3YMq3aqRQ0ibbjpg0AIxegr1Lm3MNgVFh2pcC QEuZSHke3TiaBQUgdwlnQF2GCGrPr2YOElvKXxBG09UdXqIeWPjuqjY7bQuNywVO
Bug#1011796: marked as done (node-node-rsa: FTBFS: make[1]: *** [debian/rules:19: override_dh_auto_test] Error 10)
Your message dated Thu, 02 Jun 2022 10:50:52 + with message-id and subject line Bug#1011796: fixed in node-node-rsa 1.1.1-2 has caused the Debian Bug report #1011796, regarding node-node-rsa: FTBFS: make[1]: *** [debian/rules:19: override_dh_auto_test] Error 10 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.) -- 1011796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-node-rsa Version: 1.1.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220525 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 '/<>' > mocha --no-timeout --reporter tap test/*.js > ok 1 NodeRSA Setup options should use browser environment > ok 2 NodeRSA Setup options should use io.js environment > ok 3 NodeRSA Setup options should make empty key pair with default options > ok 4 NodeRSA Setup options should make key pair with pkcs1-md5 signing scheme > ok 5 NodeRSA Setup options should make key pair with pss-sha512 signing scheme > ok 6 NodeRSA Setup options should make key pair with pkcs1 encryption scheme, > and pss-sha1 signing scheme > ok 7 NodeRSA Setup options change options > ok 8 NodeRSA Setup options advanced options change > ok 9 NodeRSA Setup options should throw 'unsupported hashing algorithm' > exception > ok 10 NodeRSA Base methods importKey() should throw exception if key data not > specified > ok 11 NodeRSA Base methods importKey() should return this > ok 12 NodeRSA Work with keys Generating keys should make key pair 512-bit > length and public exponent is 3 > ok 13 NodeRSA Work with keys Generating keys should make key pair 512-bit > length and public exponent is 5 > ok 14 NodeRSA Work with keys Generating keys should make key pair 512-bit > length and public exponent is 257 > ok 15 NodeRSA Work with keys Generating keys should make key pair 512-bit > length and public exponent is 65537 > ok 16 NodeRSA Work with keys Generating keys should make key pair 768-bit > length and public exponent is undefined and should be 65537 > ok 17 NodeRSA Work with keys Generating keys should make key pair 1024-bit > length and public exponent is undefined and should be 65537 > ok 18 NodeRSA Work with keys Generating keys should make key pair 2048-bit > length and public exponent is undefined and should be 65537 > ok 19 NodeRSA Work with keys Import/Export keys Good cases Common cases > should load private key from (not trimmed) PKCS1-PEM string > ok 20 NodeRSA Work with keys Import/Export keys Good cases Common cases > should load public key from (not trimmed) PKCS8-PEM string > ok 21 NodeRSA Work with keys Import/Export keys Good cases Common cases > .exportKey() should return private PEM string > ok 22 NodeRSA Work with keys Import/Export keys Good cases Common cases > .exportKey() from public key should return pkcs8 public PEM string > ok 23 NodeRSA Work with keys Import/Export keys Good cases Common cases > .exportKey() from private key should return pkcs8 public PEM string > ok 24 NodeRSA Work with keys Import/Export keys Good cases Common cases > should create and load key from buffer/fs.readFileSync output > ok 25 NodeRSA Work with keys Import/Export keys Good cases Common cases > should gracefully handle data outside of encapsulation boundaries for pkcs1 > private keys > ok 26 NodeRSA Work with keys Import/Export keys Good cases Common cases > should gracefully handle data outside of encapsulation boundaries for pkcs1 > public keys > ok 27 NodeRSA Work with keys Import/Export keys Good cases Common cases > should gracefully handle data outside of encapsulation boundaries for pkcs8 > private keys > ok 28 NodeRSA Work with keys Import/Export keys Good cases Common cases > should gracefully handle data outside of encapsulation boundaries for pkcs8 > public keys > ok 29 NodeRSA Work with keys Import/Export keys Good cases Common cases > should handle data without begin/end encapsulation boundaries for pkcs1 > private keys > ok 30 NodeRSA Work with keys Import/Export keys Good cases Common cases > should handle data without begin/end encapsulation boundaries for pkcs1 > public keys > ok 31 NodeRSA Work with keys Import/Export keys Good cases Common cases > should handle data without begin/end encapsulation boundaries for pkcs8 > private keys > ok 32 NodeRSA Work with keys Import/Export keys Good cases Common cases > should handle data without
Bug#1011884: coffeescript: FTBFS: /bin/sh: 1: /usr/bin/licensecheck: not found
Hi @jonas, can I switch this package from cdbs to debhelper+dh-sequence-nodejs ? Cheers, Yadd
Bug#1011809: marked as done (node-entities: FTBFS: node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type declarations.)
Your message dated Thu, 02 Jun 2022 10:34:03 + with message-id and subject line Bug#1011809: fixed in node-entities 4.3.0+dfsg-4 has caused the Debian Bug report #1011809, regarding node-entities: FTBFS: node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type declarations. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1011809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-entities Version: 4.3.0+dfsg-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220525 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs > Link ./node_modules/pretty-format -> /usr/share/nodejs/pretty-format > Link ./node_modules/ts-jest -> /usr/share/nodejs/ts-jest > Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node > Copy /usr/share/nodejs/jest-diff -> ./node_modules/ > Copy /usr/share/nodejs/@types/jest -> ./node_modules/@types >debian/rules override_dh_auto_build > make[1]: Entering directory '/<>' > tsc --downlevelIteration scripts/trie/trie.ts > node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module > 'jest-matcher-utils' or its corresponding type declarations. > make[1]: *** [debian/rules:17: scripts/trie/trie.js] Error 2 The full build log is available from: http://qa-logs.debian.net/2022/05/25/node-entities_4.3.0+dfsg-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: node-entities Source-Version: 4.3.0+dfsg-4 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-entities, 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 1011...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-entities package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 Jun 2022 12:10:44 +0200 Source: node-entities Built-For-Profiles: nocheck Architecture: source Version: 4.3.0+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1011809 Changes: node-entities (4.3.0+dfsg-4) unstable; urgency=medium . * Team upload * Declare compliance with policy 4.6.1 * Fix build links (Closes: #1011809) Checksums-Sha1: 4ce2df094a5d44d58e5cc812c04e0c8cbd7f1369 2341 node-entities_4.3.0+dfsg-4.dsc d5faef826f8de7293296c4da6769faa4cec34808 4468 node-entities_4.3.0+dfsg-4.debian.tar.xz Checksums-Sha256: 7727287791394e56bc94ab70e18bf6904c8dcb80daddfdb38a70ccd2957d3d23 2341 node-entities_4.3.0+dfsg-4.dsc 7a2e60b86578492f79d0242e31533d7fd03743a9609cc07905912073a4d8502c 4468 node-entities_4.3.0+dfsg-4.debian.tar.xz Files: 4ee42ce3371b3d16ba23aa4ce399c628 2341 javascript optional node-entities_4.3.0+dfsg-4.dsc 6bf1415e5eb1cae22e9cf96e44346639 4468 javascript optional node-entities_4.3.0+dfsg-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmKYjR0ACgkQ9tdMp8mZ 7unj9xAAhN23Z9IXo5KvZAA4wD6HTqh2Cx2FedA3AmbMfqlzuEvKwOo1S2MHylov 2k5h4GOYhTUisu2xGKCRzl3fSUtYb24AiUyvsVNcy/CbpoDpiSfVb2NE+pep1q3P
Bug#1011830: marked as done (node-get-caller-file: FTBFS: ../node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type declarations.)
Your message dated Thu, 02 Jun 2022 10:34:10 + with message-id and subject line Bug#1011830: fixed in node-get-caller-file 2.0.5+~cs1.1.1-3 has caused the Debian Bug report #1011830, regarding node-get-caller-file: FTBFS: ../node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type declarations. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1011830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011830 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-get-caller-file Version: 2.0.5+~cs1.1.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220525 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs > Copy /usr/share/nodejs/chai -> ./node_modules/ > Copy /usr/share/nodejs/@types/jest -> ./node_modules/@types > Copy /usr/share/nodejs/@types/node -> ./node_modules/@types > Copy /usr/share/nodejs/@types/chai -> ./node_modules/@types > Copy /usr/share/nodejs/jest-diff -> ./node_modules/ > Copy /usr/share/nodejs/pretty-format -> ./node_modules/ > Link node_modules/ensure-posix-path -> ../ensure-posix-path >dh_auto_build --buildsystem=nodejs > Found debian/nodejs/ensure-posix-path/build > cd ./ensure-posix-path && sh -ex > ../debian/nodejs/ensure-posix-path/build > + tsc -b . > ../node_modules/pretty-format/build/types.d.ts(7,37): error TS2307: Cannot > find module '@jest/schemas' or its corresponding type declarations. > ../node_modules/pretty-format/build/types.d.ts(38,37): error TS2339: Property > 'theme' does not exist on type 'Required'. > ../node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find > module 'jest-matcher-utils' or its corresponding type declarations. > dh_auto_build: error: cd ./ensure-posix-path && sh -ex > ../debian/nodejs/ensure-posix-path/build returned exit code 1 > make: *** [debian/rules:8: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2022/05/25/node-get-caller-file_2.0.5+~cs1.1.1-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: node-get-caller-file Source-Version: 2.0.5+~cs1.1.1-3 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-get-caller-file, 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 1011...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-get-caller-file package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 Jun 2022 12:01:30 +0200 Source: node-get-caller-file Architecture: source Version: 2.0.5+~cs1.1.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1011830 Changes: node-get-caller-file (2.0.5+~cs1.1.1-3) unstable; urgency=medium . * Team upload * Declare compliance with policy 4.6.1 * Fix build links (Closes: #1011830) * Drop useless debian/nodejs/files Checksums-Sha1: 33274a86d27653d24ee726a374af2935944c77be 2560 node-get-caller-file_2.0.5+~cs1.1.1-3.dsc 8d44757b7d9c11001c5dfa7500c2d6e8361981b8 3656 node-get-caller-file_2.0.5+~cs1.1.1-3.debian.tar.xz Checksums-Sha256:
Processed: Bug#1011849 marked as pending in node-change-case
Processing control commands: > tag -1 pending Bug #1011849 [src:node-change-case] node-change-case: FTBFS: error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type declarations. Added tag(s) pending. -- 1011849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012225: src:xwayland: fails to migrate to testing for too long: unresolved RC bug
Hi On 02-06-2022 10:53, Michel Dänzer wrote: On 2022-06-01 21:14, Paul Gevers wrote: Hi, upstream Xwayland developer here. Great. I always love it when upstream watches Debian bugs. AFAICT this is about https://bugs.debian.org/1008992 . It's very unlikely that this bug affects all users of xwayland, or there would have been a lot more noise about it. Therefore I don't think this should be RC. Than I suggest to discuss that on that bug. If the maintainer of xwaylang agrees that the bug isn't correctly classified according to https://www.debian.org/Bugs/Developer#severities the severity can be lower. (It's not clear that it's an xwayland bug at all. There was just a handful of small fixes upstream between 22.1.0 and 22.1.1, and there has been no similar report upstream) Well, the bug could be present in other versions too, if that's the case, adding "found" information will also unblock the migration (as the bug is then no longer considered a regression. 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. Removing xwayland from testing would most certainly be much worse than letting the newer version migrate. xwayland is a key-package (but I didn't check that when I filed this bug, hence "when appropriate" in my message). It's difficult to remove and will not be done automatically. One of the key reasons of this class of bug reports is to trigger somebody to look at the real causes and take the right actions. Your reply is much appreciated by me. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 995659 patch Bug #995659 [src:coturn] coturn: FTBFS with OpenSSL 3.0 Added tag(s) patch. > End of message, stopping processing here. Please contact me if you need assistance. -- 995659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995659 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011849: marked as pending in node-change-case
Control: tag -1 pending Hello, Bug #1011849 in node-change-case 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/node-change-case/-/commit/592e0db988f6bc3e3cc33fe04f57208608a4f892 Fix build links Closes: #1011849 (this message was generated automatically) -- Greetings https://bugs.debian.org/1011849
Processed: unarchive for reintroduction
Processing commands for cont...@bugs.debian.org:
> unarchive 785897
Bug #785897 {Done: Debian FTP Masters }
[src:exaile] exaile: Please update to GStreamer 1.x
Unarchived Bug 785897
> reopen 785897
Bug #785897 {Done: Debian FTP Masters }
[src:exaile] exaile: Please update to GStreamer 1.x
'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 3.4.5-1+rm.
> unarchive 498524
Bug #498524 {Done: Debian FTP Masters }
[exaile] exaile: is crashing while playing
Unarchived Bug 498524
> reopen 498524
Bug #498524 {Done: Debian FTP Masters }
[exaile] exaile: is crashing while playing
'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 3.4.5-1+rm.
> unarchive 506154
Bug #506154 {Done: Debian FTP Masters }
[exaile] exaile: crashes on exit
Unarchived Bug 506154
> reopen 506154
Bug #506154 {Done: Debian FTP Masters }
[exaile] exaile: crashes on exit
'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 3.4.5-1+rm.
> unarchive 506169
Bug #506169 {Done: Debian FTP Masters }
[exaile] exaile: fetching album cover art fails
Unarchived Bug 506169
> reopen 506169
Bug #506169 {Done: Debian FTP Masters }
[exaile] exaile: fetching album cover art fails
'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 3.4.5-1+rm.
> unarchive 589971
Bug #589971 {Done: Debian FTP Masters }
[exaile] Frontend crashes when running a second exaile command
Unarchived Bug 589971
> reopen 589971
Bug #589971 {Done: Debian FTP Masters }
[exaile] Frontend crashes when running a second exaile command
'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 3.4.5-1+rm.
> unarchive 594926
Bug #594926 {Done: Debian FTP Masters }
[exaile] exaile: crashes on startup
Bug #602583 {Done: Debian FTP Masters }
[exaile] exaile: Exaile do not start
Unarchived Bug 594926
Unarchived Bug 602583
> reopen 594926
Bug #594926 {Done: Debian FTP Masters }
[exaile] exaile: crashes on startup
Bug #602583 {Done: Debian FTP Masters }
[exaile] exaile: Exaile do not start
'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 3.4.5-1+rm.
No longer marked as fixed in versions 3.4.5-1+rm.
> unarchive 596905
Bug #596905 {Done: Debian FTP Masters }
[exaile] exaile: cannot configure hotkeys
Unarchived Bug 596905
> reopen 596905
Bug #596905 {Done: Debian FTP Masters }
[exaile] exaile: cannot configure hotkeys
'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 3.4.5-1+rm.
> unarchive 604547
Bug #604547 {Done: Debian FTP Masters }
[exaile] does exaile include an embedded copy of python-simplejson under
/usr/share/exaile/plugins/jamendo ?
Unarchived Bug 604547
> reopen 604547
Bug #604547 {Done: Debian FTP Masters }
[exaile] does exaile include an embedded copy of python-simplejson under
/usr/share/exaile/plugins/jamendo ?
'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 3.4.5-1+rm.
> unarchive 668900
Bug #668900 {Done: Debian FTP Masters }
[exaile-plugin-ipod] exaile-plugin-ipod: iPod plugin not working
Unarchived Bug 668900
> reopen 668900
Bug #668900 {Done: Debian FTP Masters }
[exaile-plugin-ipod] exaile-plugin-ipod: iPod plugin not working
'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 3.4.5-1+rm.
> unarchive 726559
Bug #726559 {Done: Debian FTP Masters }
[exaile] exaile: Segmentation fault after a second of playing
Unarchived Bug 726559
> reopen 726559
Bug #726559 {Done: Debian FTP Masters }
[exaile] exaile: Segmentation fault after a second of playing
'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 3.4.5-1+rm.
> unarchive 468205
Bug #468205 {Done: Debian FTP Masters }
[exaile] exaile will not run
Unarchived Bug 468205
> reopen 468205
Bug #468205 {Done: Debian FTP Masters }
Processed: closing 1012024
Processing commands for cont...@bugs.debian.org:
> close 1012024 0.9.27
Bug #1012024 {Done: Guido Günther } [git-buildpackage] Please
declare Breaks: dgit (<< 9.16~)
Marked as fixed in versions git-buildpackage/0.9.27.
Bug #1012024 {Done: Guido Günther } [git-buildpackage] Please
declare Breaks: dgit (<< 9.16~)
Bug 1012024 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1012024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1012255: hatari: FTBFS for RISC-V due to RISC-V system header
Package: hatari
Version: 2.3.1+dfsg
Severity: serious
Tags: ftbfs patch upstream
Justification: fails to build from source
X-Debbugs-Cc: tienhock@starfivetech.com
Dear Maintainer,
hatari is FTBFS due to a header conflict with REG_A0 that is already
defined in RISC-V's header.
Patch to fix the build is attached. Build test run on StarFive's
VisionFive board.
-- System Information:
Debian Release: 11.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: riscv64
Kernel: Linux 5.10.0-14-amd64 (SMP w/1 CPU thread)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages hatari depends on:
ii gir1.2-gtk-3.0 3.24.24-4+deb11u2
ii libc6 2.31-13+deb11u3
ii libpng16-16 1.6.37-3
pn libportaudio2
ii libreadline88.1-1
ii libsdl2-2.0-0 2.0.14+dfsg2-3
ii libudev1247.3-7
ii libx11-62:1.7.2-1
ii python3 3.9.2-3
ii python3-gi 3.38.0-2
ii zlib1g 1:1.2.11.dfsg-2+deb11u1
Versions of packages hatari recommends:
ii binfmt-support 2.2.1-1
Versions of packages hatari suggests:
ii dosfstools 4.2-1
pn mtools
ii unzip 6.0-26
01-fix-conftypes-py-build-path.diff fix-rega0-for-riscv.patch
07-fix-python-ui-doc-install.patch series
09-fix-hconsole-doc-install.patch
root@v5:~/hatari/hatari-2.3.1+dfsg# cat debian/patches/fix-rega0-for-riscv.patch
Fix issue where REG_A0 is already defined by riscv64 platform
Index: hatari-2.3.1+dfsg/src/includes/m68000.h
===
--- hatari-2.3.1+dfsg.orig/src/includes/m68000.h2020-12-26
21:50:12.0 +
+++ hatari-2.3.1+dfsg/src/includes/m68000.h 2022-05-26 01:37:55.028838540
+
@@ -26,6 +26,9 @@
#include "cycInt.h"
#include "log.h"
+#ifdef REG_A0
+#undef REG_A0
+#endif
/* 68000 Register defines */
enum {
Processed: Bug#1011809 marked as pending in node-entities
Processing control commands: > tag -1 pending Bug #1011809 [src:node-entities] node-entities: FTBFS: node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type declarations. Added tag(s) pending. -- 1011809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011809: marked as pending in node-entities
Control: tag -1 pending Hello, Bug #1011809 in node-entities 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/node-entities/-/commit/106d1b9366bc5b3b28bde76284482f97e7b745dd Fix build links Closes: #1011809 (this message was generated automatically) -- Greetings https://bugs.debian.org/1011809
Bug#1012254: libtesseract5: FTBFS armel architecture
Package: libtesseract5 Version: 5.1.0-1 Severity: serious Dear Maintainer, The build fail for armel : https://buildd.debian.org/status/fetch.php?pkg=tesseract=armel=5.1.0-1=1654113171=0 The main reason is that armel do not have neon FPu and the build should disbale neon. BTW the debian/rules is completely outdated (Still use the deprecated debhelper 9). You must not use configure/autotools build but cmake. Christian -- System Information: Debian Release: bookworm/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.1-2 (SMP w/24 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libtesseract5 depends on: ii libarchive13 3.6.0-1 ii libc6 2.33-7 ii libcurl4 7.83.1-1+b1 ii libgcc-s1 12.1.0-2 ii libgomp1 12.1.0-2 ii liblept5 1.82.0-3+b2 ii libstdc++612.1.0-2 libtesseract5 recommends no packages. libtesseract5 suggests no packages. -- no debconf information
Bug#1011830: marked as pending in node-get-caller-file
Control: tag -1 pending Hello, Bug #1011830 in node-get-caller-file 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/node-get-caller-file/-/commit/bc3c9d8804aee58be88a2d0c9c68363b150ef6a6 Fix build links Closes: #1011830 (this message was generated automatically) -- Greetings https://bugs.debian.org/1011830
Bug#995659: coturn: FTBFS with OpenSSL 3.0
Hello!
On Sun, 3 Oct 2021 20:12:20 +0200 Kurt Roeckx wrote:
> src/client/ns_turn_msg.c: In function stun_produce_integrity_key_str:
> src/client/ns_turn_msg.c:260:7: warning: implicit declaration of function
> FIPS_mode [-Wimplicit-function-declaration]
> 260 | if (FIPS_mode()) {
> | ^
> [...]
> /usr/bin/ld: lib/libturnclient.a(ns_turn_msg.o): in function
> `stun_produce_integrity_key_str':
> ./src/client/ns_turn_msg.c:260: undefined reference to `FIPS_mode'
> collect2: error: ld returned 1 exit status
Please consider to apply my patch fixing build against newest OpenSSL.
The patch refers to the OPENSSL_FIPS macro that used to be in ancient
OpenSSL source code. This fix does not change behaviour because
the FIPS_mode() function always returned zero.
diffstat for coturn-4.5.2 coturn-4.5.2
changelog |8
patches/No-FIPS-140-mode.patch | 31 +++
patches/series |1 +
3 files changed, 40 insertions(+)
diff -Nru coturn-4.5.2/debian/changelog coturn-4.5.2/debian/changelog
--- coturn-4.5.2/debian/changelog 2021-03-24 22:30:23.0 +0300
+++ coturn-4.5.2/debian/changelog 2022-06-02 12:41:25.0 +0300
@@ -1,3 +1,11 @@
+coturn (4.5.2-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * New No-FIPS-140-mode.patch fixes build against OpenSSL 3.0
+(Closes: #995659, LP: #1967018)
+
+ -- Nicholas Guriev Thu, 02 Jun 2022 12:41:25 +0300
+
coturn (4.5.2-3) unstable; urgency=medium
[ Ferenc Wágner ]
diff -Nru coturn-4.5.2/debian/patches/No-FIPS-140-mode.patch
coturn-4.5.2/debian/patches/No-FIPS-140-mode.patch
--- coturn-4.5.2/debian/patches/No-FIPS-140-mode.patch 1970-01-01
03:00:00.0 +0300
+++ coturn-4.5.2/debian/patches/No-FIPS-140-mode.patch 2022-06-02
12:34:17.0 +0300
@@ -0,0 +1,31 @@
+From: Nicholas Guriev
+Date: Thu, 02 Jun 2022 12:34:17 +0300
+Subject: Do not check FIPS 140 mode
+ It is not available in OpenSSL as packaged in Debian. The OPENSSL_FIPS macro
+ appeared in ancient OpenSSL sources but was never defined.
+ https://sources.debian.org/src/openssl/1.1.1n-0%2Bdeb11u2/crypto/o_fips.c/
+
+---
+ src/client/ns_turn_msg.c |4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+--- a/src/client/ns_turn_msg.c
b/src/client/ns_turn_msg.c
+@@ -244,7 +244,7 @@ int stun_produce_integrity_key_str(const
+ unsigned int keylen = 0;
+ EVP_MD_CTX ctx;
+ EVP_MD_CTX_init();
+-#if defined EVP_MD_CTX_FLAG_NON_FIPS_ALLOW &&
!defined(LIBRESSL_VERSION_NUMBER)
++#ifdef OPENSSL_FIPS
+ if (FIPS_mode()) {
+
EVP_MD_CTX_set_flags(,EVP_MD_CTX_FLAG_NON_FIPS_ALLOW);
+ }
+@@ -256,7 +256,7 @@ int stun_produce_integrity_key_str(const
+ #else
+ unsigned int keylen = 0;
+ EVP_MD_CTX *ctx = EVP_MD_CTX_new();
+-#if defined EVP_MD_CTX_FLAG_NON_FIPS_ALLOW && !
defined(LIBRESSL_VERSION_NUMBER)
++#ifdef OPENSSL_FIPS
+ if (FIPS_mode()) {
+ EVP_MD_CTX_set_flags(ctx,
EVP_MD_CTX_FLAG_NON_FIPS_ALLOW);
+ }
diff -Nru coturn-4.5.2/debian/patches/series coturn-4.5.2/debian/patches/series
--- coturn-4.5.2/debian/patches/series 2021-02-10 22:05:50.0 +0300
+++ coturn-4.5.2/debian/patches/series 2022-06-02 12:34:17.0 +0300
@@ -1,2 +1,3 @@
Set-logging-to-syslog.patch
Fix-undefinded-OPENSSL_VERSION_1_1_1.patch
+No-FIPS-140-mode.patch
signature.asc
Description: This is a digitally signed message part
Processed: autoremoval is not fixed yet
Processing commands for cont...@bugs.debian.org: > # to avoid people getting mad at me for not fixing the autoremovals > # script > merge 1012245 1012246 Bug #1012245 [src:nvidia-graphics-drivers-tesla-470] fails on ppc64el due to transitive GPL symbol usage Bug #1012245 [src:nvidia-graphics-drivers-tesla-470] fails on ppc64el due to transitive GPL symbol usage Marked as found in versions nvidia-graphics-drivers-tesla-470/470.129.06-3. Added tag(s) bookworm and sid. Bug #1012246 [src:nvidia-graphics-drivers-tesla-470] fails on ppc64el due to transitive GPL symbol usage Merged 1012245 1012246 > tag 1012245 bookworm-ignore Bug #1012245 [src:nvidia-graphics-drivers-tesla-470] fails on ppc64el due to transitive GPL symbol usage Bug #1012246 [src:nvidia-graphics-drivers-tesla-470] fails on ppc64el due to transitive GPL symbol usage Added tag(s) bookworm-ignore. Added tag(s) bookworm-ignore. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012245 1012246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012246 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012252: debhelper: execute_after not executed for binary-indep build
Package: debhelper Version: 13.7.1 Severity: Serious Justification: FTBFS Control: block 1012022 by -1 fenics-basix 0.4.2-1exp1 is currently failing to build in a binary-indep build, see https://buildd.debian.org/status/logs.php?pkg=fenics-basix=all The problem occurs when building docs in an execute_before_dh_install-indep rule. The doc build (via sphinx) expects the basix python module to have been built. The rules file is available at https://tracker.debian.org/media/packages/f/fenics-basix/rules-0.4.2-1exp1 The python module build is supposed to have been performed already in an execute_after_dh_auto_install rule (after dh_auto_install has put the libbasix.so shared library in place). We can see in the binary-indep log at https://buildd.debian.org/status/fetch.php?pkg=fenics-basix=all=0.4.2-1exp1=1654102080=0 that libbasix.so did get built by the override_dh_auto_build rule, and got installed by dh_auto_install -i. But after dh_auto_install -i, the next rule that gets run is execute_before_dh_install-indep. execute_after_dh_auto_install never gets run. This doesn't meet the intention of the rules file. execute_after_dh_auto_install should be run after dh_auto_install, with or without the -i flag, shouldn't it? In particular, dh --no-act indicates it should have been executed: $ dh binary-indep --no-act dh_testroot -i dh_prep -i dh_installdirs -i dh_auto_install -i debian/rules execute_after_dh_auto_install debian/rules execute_before_dh_install-indep dh_install -i dh_installdocs -i ... So it looks like a bug in dh during actual execution, that the execute_after_dh_auto_install rule is not getting executed. This bug is blocking #1012022, which is Severity: serious (FTBFS), hence I'm marking this bug Severity: serious (FTBFS) to match. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-3-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debhelper depends on: ii autotools-dev20220109.1 ii dh-autoreconf20 ii dh-strip-nondeterminism 1.13.0-1 ii dpkg 1.21.8 ii dpkg-dev 1.21.8 ii dwz 0.14-1 ii file 1:5.41-4 ii libdebhelper-perl13.7.1 ii libdpkg-perl 1.21.8 ii man-db 2.10.2-1 ii perl 5.34.0-4 ii po-debconf 1.0.21+nmu1 debhelper recommends no packages. Versions of packages debhelper suggests: ii dh-make 2.202201 -- no debconf information
Processed: Bug#1011830 marked as pending in node-get-caller-file
Processing control commands: > tag -1 pending Bug #1011830 [src:node-get-caller-file] node-get-caller-file: FTBFS: ../node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type declarations. Added tag(s) pending. -- 1011830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011830 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010331: src:vkd3d: fails to migrate to testing for too long: FTBFS on s390x
Dear s390x porters, As a Release Manager, I'm asking your help with the FTBFS of vkd3d on s390x. The failure is blocking migration of the key package vkd3d. Paul On Fri, 29 Apr 2022 08:54:51 +0200 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:vkd3d has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package fails to build from source on s390x while it built successfully there in the past. OpenPGP_signature Description: OpenPGP digital signature
Processed: debhelper: execute_after not executed for binary-indep build
Processing control commands: > block 1012022 by -1 Bug #1012022 [src:fenics-basix] fenics-basix: FTBFS during separate binary-indep build 1012022 was not blocked by any bugs. 1012022 was not blocking any bugs. Added blocking bug(s) of 1012022: 1012252 -- 1012022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012022 1012252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012252 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012250: gscan2pdf: flaky autopkgtest: regularly times out
Source: gscan2pdf Version: 2.12.6-1 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of you package on s390x because it was showing up on our alert page [1]. I noticed that there were several runs that took 27h before timing out, while successful runs only take about 15 to 20 minutes. This is not limited to s390x, also other architectures fail regularly. In stable, the test also fails once in a while, but I didn't spot the timeouts there. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. On top of that, when a test just hangs that's not good for our infrastructure. I'll put gscan2pdf on our reject_list for amd64, armhf, i386, and s390x. Don't hesitate to reach out if you need help and some more information from our infrastructure. Paul [1] https://ci.debian.net/status/alerts/ Examples of 27h time out https://ci.debian.net/data/autopkgtest/unstable/amd64/g/gscan2pdf/21000327/log.gz https://ci.debian.net/data/autopkgtest/testing/armhf/g/gscan2pdf/22210007/log.gz https://ci.debian.net/data/autopkgtest/unstable/i386/g/gscan2pdf/21000345/log.gz https://ci.debian.net/data/autopkgtest/testing/s390x/g/gscan2pdf/2205/log.gz OpenPGP_signature Description: OpenPGP digital signature
Processed (with 2 errors): Re: autopkgtest fails
Processing commands for cont...@bugs.debian.org:
> reopen 1012246
Bug #1012246 {Done: Andreas Beckmann }
[src:nvidia-graphics-drivers-tesla-470] fails on ppc64el due to transitive GPL
symbol usage
Bug reopened
Ignoring request to alter fixed versions of bug #1012246 to the same values
previously set
> found 1012246 470.129.06-3
Bug #1012246 [src:nvidia-graphics-drivers-tesla-470] fails on ppc64el due to
transitive GPL symbol usage
Marked as found in versions nvidia-graphics-drivers-tesla-470/470.129.06-3.
> forwarded 1012244
Unknown command or malformed arguments to command.
> https://salsa.debian.org/pkg-security-team/lime-forensics/-/merge_requests/2
Unknown command or malformed arguments to command.
> reassign 1012244 src:lime-forensics
Bug #1012244 [src:limewire] autopkgtest fails
Warning: Unknown package 'src:limewire'
Bug reassigned from package 'src:limewire' to 'src:lime-forensics'.
No longer marked as found in versions limewire/1.9.1-3.
Ignoring request to alter fixed versions of bug #1012244 to the same values
previously set
> tag 1012244 patch
Bug #1012244 [src:lime-forensics] autopkgtest fails
Ignoring request to alter tags of bug #1012244 to the same tags previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1012244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012244
1012246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012246
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1010883: autopkgtest fails
reopen 1012246 found 1012246 470.129.06-3 forwarded 1012244 https://salsa.debian.org/pkg-security-team/lime-forensics/-/merge_requests/2 reassign 1012244 src:lime-forensics tag 1012244 patch thanks grr, I mixed up submit commands and in-line commands unintentionally and got the source package wrong I need coffee, sorry for the noise. Paul On 02-06-2022 09:10, Paul Gevers wrote: Source: limewire Severity: serious Version: 1.9.1-3 Control: clone -1 -2 Control: reassign -2 src:nvidia-graphics-drivers-tesla-470 Control: version -2 470.129.06-3 Control: tag -1 patch Control: forwarded -1 https://salsa.debian.org/pkg-security-team/lime-forensics/-/merge_requests/2 OpenPGP_signature Description: OpenPGP digital signature
Bug#1012244: autopkgtest fails
Source: limewire Severity: serious Version: 1.9.1-3 Control: clone -1 -2 Control: reassign -2 src:nvidia-graphics-drivers-tesla-470 Control: version -2 470.129.06-3 Control: tag -1 patch Control: forwarded -1 https://salsa.debian.org/pkg-security-team/lime-forensics/-/merge_requests/2 Control: retitle -2 fails on ppc64el due to transitive GPL symbol usage Hi, [This bug report is a follow up from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010883#59, a bug in the dkms autopkgtest framework] On 02-06-2022 04:12, Andreas Beckmann wrote: On 27/05/2022 16.22, Andreas Beckmann wrote: On 27/05/2022 10.59, Paul Gevers wrote: My guess is that apt pinning comes into play here, installing That aligns with my suspicion that it's related to the mixing of unstable and testing. Uploaded a first attempt on the fix. Works for me, let's see how ci.d.o likes it. There are probably still corner cases to be handled ... Looks not too bad. Current problems: lime-forensics: used dkms-autopkgtest manually, not via Testsuite: autopkgtest-pkg-dkms merge-request !2 (only autopkgtest buggy, module builds fine) Let's also track this in a bug report. r8125: bug #1012014 - r8125: fails to build module for Linux 5.17 (new upstream release available) nvidia-graphics-drivers-tesla-470: fails on ppc64el due to transitive GPL symbol usage, reported upstream Ditto. nvidia-graphics-drivers-tesla-510: improved version in experimental, but has the same problem on ppc64el as 470 (not yet in sid due to moving a package from nvidia-graphics-drivers to -tesla-510) feel free to temporarily remove from testing Since these bugs (modules failing to build) are already present in testing and only exposed by the new dkms by making the autopkgtest run no longer a no-op, perhaps you could just ignore the failing tests and hint dkms into testing? Ack. (-tesla-510 would need some forced hint for reintroduction into testing as well, since I don't think an upstream fix for ppc64el will be available in time when I move nvidia-graphics-drivers from 470 to 510 as default in sid) Please ping us when the time comes. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed (with 2 errors): autopkgtest fails
Processing control commands:
> clone -1 -2
Bug #1010883 {Done: Andreas Beckmann } [dkms] dkms:
autopkgtest mixes headers from sid and testing
Bug 1010883 cloned as bug 1012246
> reassign -2 src:nvidia-graphics-drivers-tesla-470
Bug #1012246 {Done: Andreas Beckmann } [dkms] dkms:
autopkgtest mixes headers from sid and testing
Bug reassigned from package 'dkms' to 'src:nvidia-graphics-drivers-tesla-470'.
No longer marked as found in versions dkms/3.0.3-1 and limewire/1.9.1-3.
No longer marked as fixed in versions dkms/3.0.3-2.
> version -2 470.129.06-3
Unknown command or malformed arguments to command.
> tag -1 patch
Bug #1010883 {Done: Andreas Beckmann } [dkms] dkms:
autopkgtest mixes headers from sid and testing
Added tag(s) patch.
> forwarded -1
Unknown command or malformed arguments to command.
> retitle -2 fails on ppc64el due to transitive GPL symbol usage
Bug #1012246 {Done: Andreas Beckmann }
[src:nvidia-graphics-drivers-tesla-470] dkms: autopkgtest mixes headers from
sid and testing
Changed Bug title to 'fails on ppc64el due to transitive GPL symbol usage' from
'dkms: autopkgtest mixes headers from sid and testing'.
--
1010883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010883
1012246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012246
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 2 errors): autopkgtest fails
Processing control commands: > clone -1 -2 Bug #1012244 [src:limewire] autopkgtest fails Warning: Unknown package 'src:limewire' Bug 1012244 cloned as bug 1012245 Warning: Unknown package 'src:limewire' > reassign -2 src:nvidia-graphics-drivers-tesla-470 Bug #1012245 [src:limewire] autopkgtest fails Warning: Unknown package 'src:limewire' Bug reassigned from package 'src:limewire' to 'src:nvidia-graphics-drivers-tesla-470'. No longer marked as found in versions limewire/1.9.1-3. Ignoring request to alter fixed versions of bug #1012245 to the same values previously set > version -2 470.129.06-3 Unknown command or malformed arguments to command. > tag -1 patch Bug #1012244 [src:limewire] autopkgtest fails Warning: Unknown package 'src:limewire' Added tag(s) patch. Warning: Unknown package 'src:limewire' > forwarded -1 Unknown command or malformed arguments to command. > retitle -2 fails on ppc64el due to transitive GPL symbol usage Bug #1012245 [src:nvidia-graphics-drivers-tesla-470] autopkgtest fails Changed Bug title to 'fails on ppc64el due to transitive GPL symbol usage' from 'autopkgtest fails'. -- 1012244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012244 1012245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012245 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#980957: llvm-toolchain-11 autopkgtest segfaults on armhf
Processing control commands: > severity -1 normal Bug #1011312 [src:llvm-toolchain-14] llvm-toolchain-14 autopkgtest segfaults on armhf Severity set to 'normal' from 'serious' -- 1011312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011312: Bug#980957: llvm-toolchain-11 autopkgtest segfaults on armhf
Control: severity -1 normal On Thu, 19 May 2022 23:48:52 +0300 Adrian Bunk wrote: This issue is also present in llvm-toolchain-14, and currently blocking testing migration there: https://ci.debian.net/packages/l/llvm-toolchain-14/unstable/armhf/ The issue is now worked around by not running the failing test on armhf, so it no longer blocks the migration. I'm lowering the severity to enable migration, but I'm not closing this bug as I don't know the plans of the maintainer. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1012231: marked as done (tinyows: FTBFS: problems with boolean types and constants)
Your message dated Thu, 02 Jun 2022 06:19:00 + with message-id and subject line Bug#1012231: fixed in tinyows 1.2.0-2 has caused the Debian Bug report #1012231, regarding tinyows: FTBFS: problems with boolean types and constants 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.) -- 1012231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012231 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tinyows Version: 1.2.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, tinyows recently started to FTBFS after some build-dependency got updated: dh_auto_build make -j3 make[1]: Entering directory '/build/tinyows-1.2.0' gcc -g -O2 -ffile-prefix-map=/build/tinyows-1.2.0=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -pedantic -Wall -I/usr/include/postgre sql -I/usr/include/libxml2 src/fe/fe_comparison_ops.c src/fe/fe_error.c src/fe/fe_filter.c src/fe/fe_filter_capabilities.c src/fe/fe_function.c src/fe/fe_logical_ops.c src/fe/fe_spatial_ops.c src/mapfile/mapfile .c src/ows/ows_bbox.c src/ows/ows.c src/ows/ows_config.c src/ows/ows_error.c src/ows/ows_geobbox.c src/ows/ows_get_capabilities.c src/ows/ows_layer.c src/ows/ows_metadata.c src/ows/ows_psql.c src/ows/ows_request.c src/ows/ows_srs.c src/ows/ows_storage.c src/ows/ows_version.c src/struct/alist.c src/struct/array.c src/struct/buffer.c src/struct/cgi_request.c src/struct/list.c src/struct/mlist.c src/struct/regexp.c src/wfs/wf s_describe.c src/wfs/wfs_error.c src/wfs/wfs_get_capabilities.c src/wfs/wfs_get_feature.c src/wfs/wfs_request.c src/wfs/wfs_transaction.c src/ows/ows_libxml.c -o tinyows -lfl -L/usr/lib/x86_64-linux-gnu -lpq -lxml 2 -lfcgi In file included from /usr/include/unicode/umachine.h:52, from /usr/include/unicode/utypes.h:38, from /usr/include/unicode/ucnv_err.h:88, from /usr/include/unicode/ucnv.h:51, from /usr/include/libxml2/libxml/encoding.h:31, from /usr/include/libxml2/libxml/parser.h:812, from /usr/include/libxml2/libxml/globals.h:18, from /usr/include/libxml2/libxml/threads.h:35, from /usr/include/libxml2/libxml/xmlmemory.h:218, from /usr/include/libxml2/libxml/tree.h:1307, from /usr/include/libxml2/libxml/xmlreader.h:14, from src/fe/../ows/ows.h:30, from src/fe/fe_comparison_ops.c:29: src/fe/../ows/../ows_struct.h:33:3: error: expected identifier before numeric constant 33 | false, | ^ src/fe/../ows/../ows_struct.h:37:19: error: two or more data types in declaration specifiers 37 | typedef enum Bool bool; | ^~~~ In file included from src/fe/../ows/ows.h:38, from src/fe/fe_comparison_ops.c:29: src/fe/../ows/../ows_struct.h:37:14: warning: empty declaration with storage class specifier does not redeclare tag 37 | typedef enum Bool bool; | ^~~~ [...] Andreas tinyows_1.2.0-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: tinyows Source-Version: 1.2.0-2 Done: Bas Couwenberg We believe that the bug you reported is fixed in the latest version of tinyows, 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 1012...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bas Couwenberg (supplier of updated tinyows package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 Jun 2022 07:45:56 +0200 Source: tinyows Binary: tinyows tinyows-dbgsym Architecture: source amd64 Version: 1.2.0-2 Distribution: unstable Urgency: medium Maintainer: Debian GIS Project Changed-By: Bas Couwenberg Description: tinyows- lightweight and fast WFS-T server Closes: 1012231 Changes: tinyows (1.2.0-2) unstable; urgency=medium . * Bump Standards-Version to 4.6.0, no changes. * Bump debhelper compat to 12, changes: - Drop --list-missing from dh_install * Add patch to fix FTBFS with
