Processed: Re: Bug#1010958: sscg FTBFS with OpenSSL 3.0.3

2022-05-16 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 openssl 3.0.2-1 Bug #1010958 [src:sscg] sscg FTBFS with OpenSSL 3.0.3 Bug reassigned from package 'src:sscg' to 'openssl'. No longer marked as found in versions sscg/3.0.2-1. Ignoring request to alter fixed versions of bug #1010958 to the same values

Bug#1010958: sscg FTBFS with OpenSSL 3.0.3

2022-05-16 Thread Martin Pitt
Control: reassign -1 openssl 3.0.2-1 Control: affects -1 sscg 3.0.2-1 Control: tag -1 fixed-upstream Kurt Roeckx [2022-05-15 23:05 +0200]: > It looks like it's fixed here: https://github.com/openssl/openssl/pull/18247 Indeed, thank you! Updating bug status. I see openssl 3.0.3-4 is supposed to

Bug#1010904: marked as done (jquery-at.js: replace node-gulp-util build dependency with node-fancy-log)

2022-05-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 May 2022 05:33:46 + with message-id and subject line Bug#1010904: fixed in jquery-at.js 1.5.4+dfsg.1-4 has caused the Debian Bug report #1010904, regarding jquery-at.js: replace node-gulp-util build dependency with node-fancy-log to be marked as done. This means

Bug#1009471: marked as done (luma.oled: FTBFS: ModuleNotFoundError: No module named 'luma.oled')

2022-05-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 May 2022 05:18:46 + with message-id and subject line Bug#1009471: fixed in luma.oled 3.8.1+ds1-3 has caused the Debian Bug report #1009471, regarding luma.oled: FTBFS: ModuleNotFoundError: No module named 'luma.oled' to be marked as done. This means that you claim

Bug#1009404: marked as done (luma.lcd: FTBFS: ModuleNotFoundError: No module named 'luma.lcd')

2022-05-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 May 2022 05:03:47 + with message-id and subject line Bug#1009404: fixed in luma.lcd 2.9.0+ds1-3 has caused the Debian Bug report #1009404, regarding luma.lcd: FTBFS: ModuleNotFoundError: No module named 'luma.lcd' to be marked as done. This means that you claim

Bug#1010703: marked as done (haskell-devscripts: Shell expansion breaks nested quotes in GHC arguments)

2022-05-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 May 2022 03:34:12 + with message-id and subject line Bug#1010703: fixed in haskell-devscripts 0.16.15 has caused the Debian Bug report #1010703, regarding haskell-devscripts: Shell expansion breaks nested quotes in GHC arguments to be marked as done. This means

Bug#1010703: marked as pending in haskell-devscripts

2022-05-16 Thread Scott Talbert
Control: tag -1 pending Hello, Bug #1010703 in haskell-devscripts 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:

Processed: Bug#1010703 marked as pending in haskell-devscripts

2022-05-16 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1010703 [haskell-devscripts] haskell-devscripts: Shell expansion breaks nested quotes in GHC arguments Added tag(s) pending. -- 1010703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010703 Debian Bug Tracking System Contact

Bug#1011108: ftbfs: forces std=c++14

2022-05-16 Thread Steve Langasek
Package: macromoleculebuilder Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic ubuntu-patch Dear maintainers, The macromoleculebuilder source package fails to

Bug#1011107: binary packages should conflict/replace older ones

2022-05-16 Thread Thadeu Lima de Souza Cascardo
Source: waylandpp Version: 1.0.0-1 Severity: serious Perhaps libwayland-client++1 should conflict/replace libwayland-client++0, and the same for cursor and egl packages? Preparing to unpack .../libwayland-client++1_1.0.0-2_amd64.deb ... Unpacking libwayland-client++1:amd64 (1.0.0-2) ... dpkg:

Bug#1007744: dovecot: FTBFS on ppc64el

2022-05-16 Thread Adrian Bunk
On Wed, Apr 13, 2022 at 09:33:58PM +0200, Christian Göttsche wrote: > It looks like the ppc64el build was retried and succeeded. > > Maybe the timeouts should be increased for slow build systems, similar > what upstream did for running under valgrind with commit 2d12409a > ("lib-smtp: Adjust test

Bug#1011101: nodejs: FTBFS on mipsel: multiple failures with openssl 3.0

2022-05-16 Thread Jérémy Lal
Package: nodejs Version: 16.14.2+dfsg1-1+b1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Last time so many openssl-related test failures happened, OPENSSL_CONF env was set to a relative path, and nodejs/openssl3 expected an absolute

Bug#1011045: marked as done (hubicfuse FTBFS: error: expected identifier before numeric constant)

2022-05-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 May 2022 20:39:46 + with message-id and subject line Bug#1011045: fixed in hubicfuse 3.0.1-5 has caused the Debian Bug report #1011045, regarding hubicfuse FTBFS: error: expected identifier before numeric constant to be marked as done. This means that you claim

Bug#1011097: [Pkg-javascript-devel] Bug#1011097: webpack fails with nodejs compiled with OpenSSL 3.0

2022-05-16 Thread Jérémy Lal
Le lun. 16 mai 2022 à 22:09, Adrian Bunk a écrit : > Package: webpack > Version: 4.43.0-7 > Severity: serious > Tags: ftbfs > Control: affects -1 src:macaulay2 > > https://buildd.debian.org/status/logs.php?pkg=macaulay2=all > > ... > > build > > webpack > > node:internal/crypto/hash:67 >

Processed: found 996273 in 1:2.3.16+dfsg1-3

2022-05-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 996273 1:2.3.16+dfsg1-3 Bug #996273 [src:dovecot] dovecot: FTBFS with OpenSSL 3.0 Marked as found in versions dovecot/1:2.3.16+dfsg1-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 996273:

Bug#1011097: webpack fails with nodejs compiled with OpenSSL 3.0

2022-05-16 Thread Adrian Bunk
Package: webpack Version: 4.43.0-7 Severity: serious Tags: ftbfs Control: affects -1 src:macaulay2 https://buildd.debian.org/status/logs.php?pkg=macaulay2=all ... > build > webpack node:internal/crypto/hash:67 this[kHandle] = new _Hash(algorithm, xofLen); ^ Error:

Processed: webpack fails with nodejs compiled with OpenSSL 3.0

2022-05-16 Thread Debian Bug Tracking System
Processing control commands: > affects -1 src:macaulay2 Bug #1011097 [webpack] webpack fails with nodejs compiled with OpenSSL 3.0 Added indication that 1011097 affects src:macaulay2 -- 1011097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011097 Debian Bug Tracking System Contact

Processed: Re: Bug#1011078: chromium: arm64 package not available in bullseye-security

2022-05-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 1011078 -1 Bug #1011078 [chromium] chromium: arm64 package not available in bullseye-security Bug 1011078 cloned as bug 1011096 > retitle -1 chromium: i386 and armhf packages FTBFS in bullseye Bug #1011096 [chromium] chromium: arm64

Bug#1011044: marked as done (libtiledb2.8 needs Breaks+Replaces: libtiledb2.7)

2022-05-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 May 2022 14:40:40 -0500 with message-id <25218.43192.211302.67...@rob.eddelbuettel.com> and subject line Re: Bug#1011044: libtiledb2.8 needs Breaks+Replaces: libtiledb2.7 has caused the Debian Bug report #1011044, regarding libtiledb2.8 needs Breaks+Replaces:

Processed: reassign 1010623 to src:dracut

2022-05-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1010623 src:dracut Bug #1010623 [linux-image-amd64] linux-image-amd64: Missing Crypto Modules Bug reassigned from package 'linux-image-amd64' to 'src:dracut'. No longer marked as found in versions linux-signed-amd64/5.10.106+1. Ignoring

Bug#994855: zfs-dkms: Panic when receiving, fixed upstream

2022-05-16 Thread Antoine Beaupré
Is there a plan to fix this in bullseye as well?

Bug#1011092: src:herbstluftwm: fails to migrate to testing for too long: ftbfs on most archs

2022-05-16 Thread Paul Gevers
Source: herbstluftwm Version: 0.9.3-2 Severity: serious Control: close -1 0.9.4-2 Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than

Processed: src:herbstluftwm: fails to migrate to testing for too long: ftbfs on most archs

2022-05-16 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.9.4-2 Bug #1011092 [src:herbstluftwm] src:herbstluftwm: fails to migrate to testing for too long: ftbfs on most archs Marked as fixed in versions herbstluftwm/0.9.4-2. Bug #1011092 [src:herbstluftwm] src:herbstluftwm: fails to migrate to testing for too

Processed: found 1009872 in 1:2.3.4.1-5+deb10u6

2022-05-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1009872 1:2.3.4.1-5+deb10u6 Bug #1009872 [dovecot-core] dovecot-core: postinst fails when snakeoil cert is removed Marked as found in versions dovecot/1:2.3.4.1-5+deb10u6. > thanks Stopping processing here. Please contact me if you need

Bug#929165: How to use rm_conffile to remove files that contain empty " ", comma "," and wildcard "*"?

2022-05-16 Thread Antoine Beaupré
On 2022-05-16 19:13:45, Andreas Metzler wrote: > On 2022-05-16 Antoine Beaupré wrote: >> Sorry for jumping in, but this bug report has been open for more than >> three years now, and blocked this package from shipping with >> bullseye. It's still blocking it from bookworm as well... > >> On

Bug#965744: marked as done (nat: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-05-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 May 2022 17:50:20 + with message-id and subject line Bug#965744: fixed in nat 1:1.0-6.1 has caused the Debian Bug report #965744, regarding nat: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the

Bug#1004018: marked as done (Is smb-nat still useful?)

2022-05-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 May 2022 17:50:20 + with message-id and subject line Bug#1004018: fixed in nat 1:1.0-6.1 has caused the Debian Bug report #1004018, regarding Is smb-nat still useful? to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: [bts-link] source package src:vitables

2022-05-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:vitables > # 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

Processed: [bts-link] source package src:python-quamash

2022-05-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:python-quamash > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user

Processed: [bts-link] source package gnome-shell-extension-dashtodock

2022-05-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package > gnome-shell-extension-dashtodock > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user

Bug#929165: How to use rm_conffile to remove files that contain empty " ", comma "," and wildcard "*"?

2022-05-16 Thread Andreas Metzler
On 2022-05-16 Antoine Beaupré wrote: > Sorry for jumping in, but this bug report has been open for more than > three years now, and blocked this package from shipping with > bullseye. It's still blocking it from bookworm as well... > On 2021-03-14 13:53:17, Andreas Metzler wrote: > [...] >>

Bug#1011084: cargo: FTBFS on mips64el

2022-05-16 Thread Sebastian Ramacher
Source: cargo Version: 0.57.0-7 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=cargo=mips64el=0.57.0-7%2Bb1=1652695874=0 [cargo 0.57.0]

Bug#1011083: cargo: FTBFS on armel

2022-05-16 Thread Sebastian Ramacher
Source: cargo Version: 0.57.0-7 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=cargo=armel=0.57.0-7%2Bb1=1652696082=0

Bug#1010970: marked as done (nacl: autopkgtest regression on armhf and i386: bus error)

2022-05-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 May 2022 16:54:40 + with message-id and subject line Bug#1010970: fixed in nacl 20110221-9 has caused the Debian Bug report #1010970, regarding nacl: autopkgtest regression on armhf and i386: bus error to be marked as done. This means that you claim that the

Bug#1006008: python-cryptography: FTBFS with OpenSSL 3.0

2022-05-16 Thread Agathe Porte
Hi, On Fri, 18 Feb 2022 22:13:59 +0100 Sebastian Andrzej Siewior wrote: > Source: python-cryptography > Version: 3.4.8-1 > Severity: important > Tags: bookworm sid > User: pkg-openssl-de...@lists.alioth.debian.org > Usertags: ftbfs-3.0 > control: forwarded -1

Processed: closing 1009450

2022-05-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1009450 1.29.1-1 Bug #1009450 [src:r-bioc-grohmm] r-bioc-grohmm: FTBFS: DecayAlgorithm.c:33:10: fatal error: S.h: No such file or directory The source 'r-bioc-grohmm' and version '1.29.1-1' do not appear to match any binary packages

Bug#1008416: marked as done (libqtxdg: FTBFS: Could NOT find GLIB (missing: GLIB_GIO_UNIX_INCLUDE_DIR) (found suitable version "2.72.0", minimum required is "2.41.0"))

2022-05-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 May 2022 14:45:47 + with message-id and subject line Bug#1008416: fixed in lxqt-build-tools 0.11.0-0.1 has caused the Debian Bug report #1008416, regarding libqtxdg: FTBFS: Could NOT find GLIB (missing: GLIB_GIO_UNIX_INCLUDE_DIR) (found suitable version "2.72.0",

Bug#1010657: google-oauth-client-java: CVE-2021-22573 - IdTokenVerifier does not verify the signature of ID Token

2022-05-16 Thread tony mancill
Hi Markus, On Mon, May 16, 2022 at 12:52:59AM +0200, Markus Koschany wrote: > Hi tony, > > Am Sonntag, dem 15.05.2022 um 11:17 -0700 schrieb tony mancill: > > > [...] > > Any thoughts?  It's a tad messy either way, but using current versions > > simplifies the porting of patches. > > I haven't

Bug#929165: How to use rm_conffile to remove files that contain empty " ", comma "," and wildcard "*"?

2022-05-16 Thread Antoine Beaupré
Hi everyone! Sorry for jumping in, but this bug report has been open for more than three years now, and blocked this package from shipping with bullseye. It's still blocking it from bookworm as well... On 2021-03-14 13:53:17, Andreas Metzler wrote: [...] > Hello is using debhelper compat 9

Bug#1011048: marked as done (firmware-nonfree: Fails to build without linux-support but linux-support isn't listed in Build-Depends)

2022-05-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 May 2022 16:01:49 +0200 with message-id and subject line Re: Bug#1011048: firmware-nonfree: Fails to build without linux-support but linux-support isn't listed in Build-Depends has caused the Debian Bug report #1011048, regarding firmware-nonfree: Fails to build

Bug#1008754: marked as done (r-cran-loo: autopkgtest regression on arm64, armhf and i386: missing value where TRUE/FALSE needed)

2022-05-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 May 2022 12:22:20 + with message-id and subject line Bug#1008754: fixed in r-cran-loo 2.5.1-1 has caused the Debian Bug report #1008754, regarding r-cran-loo: autopkgtest regression on arm64, armhf and i386: missing value where TRUE/FALSE needed to be marked as

Bug#1009467: [Bioconductor/Biostrings] S.h seems to be deprecated (Issue #66)

2022-05-16 Thread Andreas Tille
Hi again Hervé, > @tillea And most importantly, it seems that Debian is building the wrong > version of Bioconductor. The `S.h` file was removed from R 4.2 and they are > reporting a bug for **Biostrings** 2.62.0, which belongs to Bioconductor 3.14 > (the current release). BioC 3.14 should only

Bug#1009741: mercurial: flaky autopkgtest which times out on amd64 regularly

2022-05-16 Thread Julien Cristau
Control: severity -1 normal On Fri, Apr 15, 2022 at 10:36:54PM +0200, Paul Gevers wrote: > I looked at the results of the autopkgtest of you package because it was > showing up as a regression for the upload of python3-defaults. I noticed > that the test regularly fails on several architectures.

Processed: Re: Bug#1009741: mercurial: flaky autopkgtest which times out on amd64 regularly

2022-05-16 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #1009741 [src:mercurial] mercurial: flaky autopkgtest which times out on amd64 regularly Severity set to 'normal' from 'serious' -- 1009741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009741 Debian Bug Tracking System Contact

Bug#1009410: marked as done (r-bioc-genefilter: FTBFS: nd.c:24:10: fatal error: S.h: No such file or directory)

2022-05-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 May 2022 12:05:28 + with message-id and subject line Bug#1009410: fixed in r-bioc-genefilter 1.78.0-1 has caused the Debian Bug report #1009410, regarding r-bioc-genefilter: FTBFS: nd.c:24:10: fatal error: S.h: No such file or directory to be marked as done. This

Processed: Re: r-bioc-rtracklayer: FTBFS: chain_io.c:1:10: fatal error: S.h: No such file or directory

2022-05-16 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 1.56.0-1 Bug #1009454 [src:r-bioc-rtracklayer] r-bioc-rtracklayer: FTBFS: chain_io.c:1:10: fatal error: S.h: No such file or directory Marked as fixed in versions r-bioc-rtracklayer/1.56.0-1. > close -1 Bug #1009454 [src:r-bioc-rtracklayer]

Bug#1009454: r-bioc-rtracklayer: FTBFS: chain_io.c:1:10: fatal error: S.h: No such file or directory

2022-05-16 Thread Nilesh Patra
Control: fixed -1 1.56.0-1 Control: close -1 > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > gcc -I"/usr/share/R/include" -DNDEBUG -D_FILE_OFFSET_BITS=64 > > -I'/usr/lib/R/site-library/S4Vectors/include' > >

Bug#1010991: marked as done (google-guest-agent: hangs installation on ci.d.n on armhf and s390x)

2022-05-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 May 2022 10:19:24 + with message-id and subject line Bug#1010991: fixed in google-guest-agent 2026.00-6 has caused the Debian Bug report #1010991, regarding google-guest-agent: hangs installation on ci.d.n on armhf and s390x to be marked as done. This means

Bug#1006516: marked as done (nordugrid-arc: FTBFS with OpenSSL 3.0)

2022-05-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 May 2022 09:54:49 + with message-id and subject line Bug#1006516: fixed in nordugrid-arc 6.15.1-2 has caused the Debian Bug report #1006516, regarding nordugrid-arc: FTBFS with OpenSSL 3.0 to be marked as done. This means that you claim that the problem has been

Bug#1010061: marked as done (git-buildpackage: FTBFS on bookworm and sid: multiple issues)

2022-05-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 May 2022 09:50:57 + with message-id and subject line Bug#1010061: fixed in git-buildpackage 0.9.26 has caused the Debian Bug report #1010061, regarding git-buildpackage: FTBFS on bookworm and sid: multiple issues to be marked as done. This means that you claim that

Bug#996276: marked as done (foxeye: FTBFS with OpenSSL 3.0)

2022-05-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 May 2022 09:01:27 + with message-id and subject line Bug#996276: fixed in foxeye 0.12.1-4 has caused the Debian Bug report #996276, regarding foxeye: FTBFS with OpenSSL 3.0 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1009387: marked as done (fbset: FTBFS: modes.tab.c:132:3: error: expected identifier at end of input)

2022-05-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 May 2022 10:10:11 +0200 with message-id and subject line Re: fbset: FTBFS: modes.tab.c:132:3: error: expected identifier at end of input has caused the Debian Bug report #1009387, regarding fbset: FTBFS: modes.tab.c:132:3: error: expected identifier at end of input to

Bug#1011051: libssl3: upgrade to libssl3 broke my dovecot setup

2022-05-16 Thread Skibbi
Package: libssl3 Version: 3.0.3-3 Severity: grave Justification: renders package unusable After upgrading to libssl3 broke my dovecot setup with following error: imap-login: Error: Failed to initialize SSL server context: Can't load SSL certificate (ssl_cert setting): error:25066067:DSO support