Bug#996422: marked as done (golang-github-mendersoftware-openssl: FTBFS with OpenSSL 3.0)

[Debian Bug Tracking System]

Your message dated Mon, 16 May 2022 05:24:45 +
with message-id 
and subject line Bug#996422: fixed in golang-github-mendersoftware-openssl 
1.1.0-3
has caused the Debian Bug report #996422,
regarding golang-github-mendersoftware-openssl: 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.)


-- 
996422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-mendersoftware-openssl
Version: 1.1.0-2
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:
github.com/mendersoftware/openssl
# github.com/mendersoftware/openssl
src/github.com/mendersoftware/openssl/fips.go:31:7: could not determine kind of 
name for C.FIPS_mode_set
dh_auto_build: error: cd _build && go install -trimpath -v -p 1 
github.com/mendersoftware/openssl github.com/mendersoftware/openssl/utils 
returned exit code 2
make: *** [debian/rules:4: binary] Error 25

For more information see:
https://www.openssl.org/docs/man3.0/man7/migration_guide.html


Kurt
--- End Message ---
--- Begin Message ---
Source: golang-github-mendersoftware-openssl
Source-Version: 1.1.0-3
Done: Nilesh Patra 

We believe that the bug you reported is fixed in the latest version of
golang-github-mendersoftware-openssl, 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 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated 
golang-github-mendersoftware-openssl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 16 May 2022 09:55:59 +0530
Source: golang-github-mendersoftware-openssl
Architecture: source
Version: 1.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Nilesh Patra 
Closes: 996422
Changes:
 golang-github-mendersoftware-openssl (1.1.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Add patches from Ubuntu to fix compatibility with
 openSSLv3 and skip a network test (Closes: #996422)
   * Bump Standards-Version to 4.6.1 (no changes needed)
   * Bump debhelper compatibility level to 13
   * Add Versioned B-D and dep on libssl-dev
Checksums-Sha1:
 4672ace0e85c8544dfd653c2008e095f747e9926 2405 
golang-github-mendersoftware-openssl_1.1.0-3.dsc
 61efff951017d482f2c80383e0bc0a3089d84550 6796 
golang-github-mendersoftware-openssl_1.1.0-3.debian.tar.xz
 124c61d6b9f47a1faa927072ddf210ccf9d3d394 6099 
golang-github-mendersoftware-openssl_1.1.0-3_amd64.buildinfo
Checksums-Sha256:
 c2ad9099971bd34d5997bc6f0b266541fe73d486ec28831cc9226dd444268281 2405 
golang-github-mendersoftware-openssl_1.1.0-3.dsc
 b52c925861cceaaad5ff720260aff9fced16bc3ccc84715583e6e355b9dfbbd2 6796 
golang-github-mendersoftware-openssl_1.1.0-3.debian.tar.xz
 adb6b529fe55bd4819112ecdad98ecec6507f323f01c15e254dfa2422b9482c6 6099 
golang-github-mendersoftware-openssl_1.1.0-3_amd64.buildinfo
Files:
 081facb4abde64a04f6bbc3898c79ab0 2405 devel optional 
golang-github-mendersoftware-openssl_1.1.0-3.dsc
 f010ea6b84d14cbf163458db8ca91293 6796 devel optional 
golang-github-mendersoftware-openssl_1.1.0-3.debian.tar.xz
 c339d62b0ea74113b08e2d21201efc14 6099 devel optional 
golang-github-mendersoftware-openssl_1.1.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmKB1vYSHG5pbGVzaEBk
ZWJpYW4ub3JnAAoJEAC650s0M2nxiywP/imwUgjfPbO/l3cnF8gO8VOPRusLN3gk
FgYk5jMvtLNj7eubjr8F0ZQmi/TxoGDaLHMnG4qZQHXfpRq7bfsQe0FRafx/JK91
nLWmlVgKfFvoIhoqAAGzCVXxVUlcnQsifUmHe4Wo5UQ4wnJWNWrzU0n6laUW/5aP
UU84GJaQtTskVlOlgTgksD8LY1kK70wMXMaZwUG4jKkp7u/2OtkugcqQs1Ss4ggx
hJykqvlkhbmqw31bllujaHhrYGCz4rnZ0uC6q9yMCjiJ+sm0oAqwn7FzcYvurmg7
vY4yKEaJeid3gEm0UAXCtwc5S9GX1T8YHOHKn5EKoNWF7NTddqJvzQC28lPOUyqC
JpAa6T0ZIO+NgOHRGM7VqttmNy/MFNPZi/6H0jnO+3yZHP4NmTQAUiC94Fr3uz9X
7eRrC7dFzftM5R4kwtBrMC3G4QyzwvB0dNCQlQXNRQu4tfoy5p80jGYEtXlFataA
4YaUYxybbMDPHsd9DrcsjlWenCnqpU7FTHV6HaGTAd12KkWfKfWd40TQrHKsc/hL
cMLYDQZPNbiRDocP6necl0r3WFlb032DGVcxqyVtJT+HizDNHcgB9mXf3jYd2kFV

Bug#1004740: exim4: SIGSEGV (maybe attempt to write to immutable memory) when sending a mail; message frozen

[Matt Corallo]

On 5/11/22 8:09 AM, Gedalya wrote:

I'm a little dazzled by the variety of crashes I've seen so far: smtp_setup_conn > 
tls_client_start > verify_certificate, and during ARC signing, but it could be 
just noise so I'll leave it alone for now.



As a passer-by might I suggest valgrind or building with address/undefined-behavior sanitizer? I 
don't see any mention of it in this issue, and "it keeps crashing in random places that may or may 
not be related" screams "memory corruption".


Matt

Processed: Bug#996422 marked as pending in golang-github-mendersoftware-openssl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #996422 [src:golang-github-mendersoftware-openssl] 
golang-github-mendersoftware-openssl: FTBFS with OpenSSL 3.0
Added tag(s) pending.

-- 
996422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#996422: marked as pending in golang-github-mendersoftware-openssl

[Nilesh Patra]

Control: tag -1 pending

Hello,

Bug #996422 in golang-github-mendersoftware-openssl 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/go-team/packages/golang-github-mendersoftware-openssl/-/commit/2c7b1af69b476966bf7eb8fc3980d443365bc2e7


Add patches from Ubuntu to fix compatibility with openSSLv3 and skip a network 
test (Closes: #996422)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996422

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

[Charles Huber]

Package: firmware-nonfree
Version: 20210818
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: genpfa...@gmail.com

Dear Maintainer,

While trying to backport firmware-nonfree/unstable in a bullseye amd64 schroot:

user@host:~/firmware-nonfree/firmware-nonfree-20210818$ dpkg-buildpackage 
--unsigned-source --unsigned-changes   

...the build fails when trying to load the debian_linux Python module from 
linux-support:

dpkg-buildpackage: info: source package firmware-nonfree
dpkg-buildpackage: info: source version 20210818-1~bpo11+1
dpkg-buildpackage: info: source distribution bullseye-backports
dpkg-buildpackage: info: source changed by  
dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build .
 fakeroot debian/rules clean
md5sum --check debian/control.md5sum --status || \
/usr/bin/make -f debian/rules debian/control-real
make[1]: Entering directory 
'/home/user/firmware-nonfree/firmware-nonfree-20210818'
./copy-firmware.sh debian/build/install
debian/bin/gencontrol.py /usr/src/linux-support-5.10.0-8
Traceback (most recent call last):
  File 
"/home/user/firmware-nonfree/firmware-nonfree-20210818/debian/bin/gencontrol.py",
 line 13, in 
from config import Config
  File "debian/lib/python/config.py", line 1, in 
from debian_linux.config import ConfigParser, SchemaItemList
ModuleNotFoundError: No module named 'debian_linux'
make[1]: *** [debian/rules:53: debian/control-real] Error 1
make[1]: Leaving directory 
'/home/user/firmware-nonfree/firmware-nonfree-20210818'
make: *** [debian/rules:45: debian/control] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2

...despite not listing linux-support in the Build-Depends list in the DSC or in 
the debian/control file.


-- System Information:
Debian Release: 11.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.17.4 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Processed: tagging 1006736

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1006736 + fixed-upstream
Bug #1006736 [src:pytest-mock] python-pytest-asyncio breaks pytest-mock 
autopkgtest: nomatch: '* 1 passed in *'
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1006736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 1006736 is forwarded to https://github.com/pytest-dev/pytest-mock/issues/272

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1006736 https://github.com/pytest-dev/pytest-mock/issues/272
Bug #1006736 [src:pytest-mock] python-pytest-asyncio breaks pytest-mock 
autopkgtest: nomatch: '* 1 passed in *'
Set Bug forwarded-to-address to 
'https://github.com/pytest-dev/pytest-mock/issues/272'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1006736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1011044: libtiledb2.8 needs Breaks+Replaces: libtiledb2.7

[Dirk Eddelbuettel]

On 16 May 2022 at 04:48, Adrian Bunk wrote:
| Package: libtiledb2.8
| Version: 2.8.3-2
| Severity: serious
| 
| Unpacking libtiledb2.8:amd64 (2.8.3-2) ...
| dpkg: error processing archive 
/var/cache/apt/archives/libtiledb2.8_2.8.3-2_amd64.deb (--unpack):
|  trying to overwrite '/usr/lib/x86_64-linux-gnu/libtiledb.so.2.8', which is 
also in package libtiledb2.7:amd64 2.8.2-1
| dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

Something I overlooked.

Version 2.9.0-1 is already in NEW and, with some luck, should be in unstable
soon followed by 2.9.0-2 (source upload) which won't have this issue.

Dirk

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1006511: net-snmp: FTBFS with OpenSSL 3.0

[Craig Small]

Upstream should have a new version of net-snmp that compiles with
OpenSSL v3.0 in May.  I've tested the RC1 release and it compiles
fine.

https://sourceforge.net/p/net-snmp/mailman/message/37642006/

 - Craig

Bug#1011045: hubicfuse FTBFS: error: expected identifier before numeric constant

[Adrian Bunk]

Source: hubicfuse
Version: 3.0.1-4
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/logs.php?pkg=hubicfuse=3.0.1-4%2Bb1

...
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 cloudfsapi.c:17:
commonfs.h:6:16: error: expected identifier before numeric constant
6 | typedef enum { false, true } bool;
  |^
commonfs.h:6:30: error: expected ‘;’, identifier or ‘(’ before ‘_Bool’
6 | typedef enum { false, true } bool;
  |  ^~~~
...

Processed: affects 1006511

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 1006511 src:pdns-recursor
Bug #1006511 [src:net-snmp] net-snmp: FTBFS with OpenSSL 3.0
Added indication that 1006511 affects src:pdns-recursor
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1006511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1011044: libtiledb2.8 needs Breaks+Replaces: libtiledb2.7

[Adrian Bunk]

Package: libtiledb2.8
Version: 2.8.3-2
Severity: serious

Unpacking libtiledb2.8:amd64 (2.8.3-2) ...
dpkg: error processing archive 
/var/cache/apt/archives/libtiledb2.8_2.8.3-2_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libtiledb.so.2.8', which is 
also in package libtiledb2.7:amd64 2.8.2-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

Bug#999822: marked as done (netopeer2: FBTFS: error: invalid use of undefined type ‘struct nc_reply_error’)

[Debian Bug Tracking System]

Your message dated Mon, 16 May 2022 04:26:03 +0300
with message-id <20220516012603.GA30497@localhost>
and subject line Fixed in 2.0.35-1
has caused the Debian Bug report #999822,
regarding netopeer2: FBTFS: error: invalid use of undefined type ‘struct 
nc_reply_error’
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.)


-- 
999822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netopeer2
Version: 1.1.39-1+b1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

netopeer2 fails to build from source:
|   |  ^~
| [ 55%] Building C object 
cli/CMakeFiles/netopeer2-cli.dir/linenoise/linenoise.c.o
| /<>/cli/commands.c:466:58: error: invalid use of undefined type 
‘struct nc_reply_error’
|   466 | fprintf(output, "\tSID:  %s\n", 
error->err[i].sid);
|   |  ^~
| /<>/cli/commands.c:468:34: error: invalid use of undefined type 
‘struct nc_reply_error’
|   468 | for (j = 0; j < error->err[i].attr_count; ++j) {
|   |  ^~
| /<>/cli/commands.c:469:69: error: invalid use of undefined type 
‘struct nc_reply_error’
|   469 | fprintf(output, "\tbad-attr #%d: %s\n", j + 1, 
error->err[i].attr[j]);
|   | ^~
| cd /<>/obj-x86_64-linux-gnu/cli && /usr/bin/cc  
-I/<>/obj-x86_64-linux-gnu 
-I/<>/obj-x86_64-linux-gnu/cli -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time 
-D_FORTIFY_SOURCE=2 -DHAVE_MKSTEMPS -Wall -Wextra -std=gnu99 -MD -MT 
cli/CMakeFiles/netopeer2-cli.dir/linenoise/linenoise.c.o -MF 
CMakeFiles/netopeer2-cli.dir/linenoise/linenoise.c.o.d -o 
CMakeFiles/netopeer2-cli.dir/linenoise/linenoise.c.o -c 
/<>/cli/linenoise/linenoise.c
| /<>/cli/commands.c:471:34: error: invalid use of undefined type 
‘struct nc_reply_error’
|   471 | for (j = 0; j < error->err[i].elem_count; ++j) {
|   |  ^~
| /<>/cli/commands.c:472:69: error: invalid use of undefined type 
‘struct nc_reply_error’
|   472 | fprintf(output, "\tbad-elem #%d: %s\n", j + 1, 
error->err[i].elem[j]);
|   | ^~
| /<>/cli/commands.c:474:34: error: invalid use of undefined type 
‘struct nc_reply_error’
|   474 | for (j = 0; j < error->err[i].ns_count; ++j) {
|   |  ^~
| /<>/cli/commands.c:475:69: error: invalid use of undefined type 
‘struct nc_reply_error’
|   475 | fprintf(output, "\tbad-ns #%d:   %s\n", j + 1, 
error->err[i].ns[j]);
|   | ^~
| /<>/cli/commands.c:477:34: error: invalid use of undefined type 
‘struct nc_reply_error’
|   477 | for (j = 0; j < error->err[i].other_count; ++j) {
|   |  ^~
| /<>/cli/commands.c:478:44: error: invalid use of undefined type 
‘struct nc_reply_error’
|   478 | lyxml_print_mem(, error->err[i].other[j], 0);
|   |^~
| /<>/cli/commands.c: In function ‘cmd_version’:
| /<>/cli/commands.c:2586:47: warning: macro "__DATE__" might 
prevent reproducible builds [-Wdate-time]
|  2586 | fprintf(stdout, "Compile time: %s, %s\n", __DATE__, __TIME__);
|   |   ^~~~
| /<>/cli/commands.c:2586:57: warning: macro "__TIME__" might 
prevent reproducible builds [-Wdate-time]
|  2586 | fprintf(stdout, "Compile time: %s, %s\n", __DATE__, __TIME__);
|   | ^~~~
| /<>/cli/commands.c: In function ‘cmd_subscribe’:
| /<>/cli/commands.c:4522:25: warning: implicit declaration of 
function ‘nc_time2datetime’ [-Wimplicit-function-declaration]
|  4522 | start = nc_time2datetime(t, NULL, NULL);
|   | ^~~~
| /<>/cli/commands.c:4522:23: warning: assignment to ‘char *’ from 
‘int’ makes pointer from integer without a cast [-Wint-conversion]
|  4522 | start = nc_time2datetime(t, NULL, NULL);
|   |   ^
| /<>/cli/commands.c:4524:22: warning: assignment to ‘char *’ from 
‘int’ makes pointer from integer without a cast 

Processed: severity of 1001796 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1001796 serious
Bug #1001796 [netopeer2] netopeer2: test_rpc fails on 32bits arches, fails 
package build
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1001796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001796
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1011042: libica FTBFS with OpenSSL 3.0

[Adrian Bunk]

Source: libica
Version: 3.2.0-4
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/fetch.php?pkg=libica=s390x=3.2.0-4%2Bb1=1652517971=0

...
libica_keygen_test.c: In function ‘main’:
libica_keygen_test.c:228:21: warning: implicit declaration of function 
‘FIPS_mode’ [-Wimplicit-function-declaration]
  228 | if (FIPS_mode())
  | ^
gcc -O0 -g -Wall -D_LINUX_S390_ -D_GNU_SOURCE -pthread  -o 
libica_aes_gcm_kma_test libica_aes_gcm_kma_test.c -L../.libs -I. -I../include 
-I../../include -lica -lcrypto
/usr/bin/ld: /tmp/ccXlAKmW.o: in function `main':
/<>/src/tests/libica_keygen_test.c:228: undefined reference to 
`FIPS_mode'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:483: libica_keygen_test] Error 1

Bug#1011041: freeradius FTBFS with OpenSSL 3.0

[Adrian Bunk]

Source: freeradius
Version: 3.0.25+dfsg-1.1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=freeradius=3.0.25%2Bdfsg-1.1%2Bb1

...
src/main/tls.c: In function ‘load_dh_params’:
src/main/tls.c:1701:13: warning: implicit declaration of function ‘FIPS_mode’ 
[-Wimplicit-function-declaration]
 1701 | if (FIPS_mode() > 0) {
  | ^
...
LINK build/bin/radwho
build/make/jlibtool --silent --mode=link gcc -o build/bin/radwho -rpath 
/usr/lib/freeradius   -Wl,-z,relro -Wl,-z,now   build/objs/src/main/radwho.lo 
build/lib/libfreeradius-server.la build/lib/libfreeradius-radius.la  -lcrypto 
-lssl -ltalloc -latomic  -lpcre  -lcap -lnsl -lresolv -ldl -lpthread  -lreadline
/usr/bin/ld: build/objs/src/main/tls.o: in function `load_dh_params':
./src/main/tls.c:1701: undefined reference to `FIPS_mode'
collect2: error: ld returned 1 exit status
make[2]: *** [scripts/boiler.mk:639: build/bin/radiusd] Error 1

Bug#1010232: Processed: severity of 1010232 is serious

[Ricardo Mones]

On Fri, 13 May 2022 18:13:36 +0200
Axel Beckert  wrote:

> BTW, https://tracker.debian.org/pkg/claws-mail also argues:
> 
> ∙ Not built on buildd: arch amd64 binaries uploaded by mones
> ∙ Not built on buildd: arch all binaries uploaded by mones, a new
> source-only upload is needed to allow migration
> 
> Looks like an oversight when doing the upload. (Occasionally happens
> to me, too. Old habits… ;-)

Yep, it happened to me too. But not this time: is not possible to do a
source-only upload when there's new binary packages ;-)

regards,
-- 
 Ricardo Mones
 http://people.debian.org/~mones
 «Not only Guinness - Linux is good for you, too. -- Banzai on IRC»


pgpeotG2pNOXb.pgp
Description: Firma digital OpenPGP

Processed: Merge duplicates

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 996424 libghc-hsopenssl-dev
Bug #996424 [src:haskell-blogliterately] haskell-blogliterately: FTBFS with 
OpenSSL 3.0
Bug reassigned from package 'src:haskell-blogliterately' to 
'libghc-hsopenssl-dev'.
No longer marked as found in versions haskell-blogliterately/0.8.7-1.
Ignoring request to alter fixed versions of bug #996424 to the same values 
previously set
> forcemerge 1011032 996424
Bug #1011032 [libghc-hsopenssl-dev] libghc-hsopenssl-dev needs update for 
OpenSSL 3.0
Bug #1011032 [libghc-hsopenssl-dev] libghc-hsopenssl-dev needs update for 
OpenSSL 3.0
Added tag(s) sid and bookworm.
Bug #996424 [libghc-hsopenssl-dev] haskell-blogliterately: FTBFS with OpenSSL 
3.0
Added indication that 996424 affects 
src:haskell-haxr,src:glirc,src:haskell-openssl-streams,src:haskell-hsopenssl-x509-system,src:haskell-hookup,src:haskell-http-streams
Marked as found in versions haskell-hsopenssl/0.11.4.18-1.
Merged 996424 1011032
> retitle 996424 libghc-hsopenssl-dev needs update for OpenSSL 3.0
Bug #996424 [libghc-hsopenssl-dev] haskell-blogliterately: FTBFS with OpenSSL 
3.0
Bug #1011032 [libghc-hsopenssl-dev] libghc-hsopenssl-dev needs update for 
OpenSSL 3.0
Changed Bug title to 'libghc-hsopenssl-dev needs update for OpenSSL 3.0' from 
'haskell-blogliterately: FTBFS with OpenSSL 3.0'.
Ignoring request to change the title of bug#1011032 to the same title
> affects 996424 src:haskell-blogliterately
Bug #996424 [libghc-hsopenssl-dev] libghc-hsopenssl-dev needs update for 
OpenSSL 3.0
Bug #1011032 [libghc-hsopenssl-dev] libghc-hsopenssl-dev needs update for 
OpenSSL 3.0
Added indication that 996424 affects src:haskell-blogliterately
Added indication that 1011032 affects src:haskell-blogliterately
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1011032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011032
996424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[Markus Koschany]

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 investigated the CVE closely enough but the current reverse-
dependencies in Bullseye don't seem to be severely affected by it. bazel-
bootstrap and libgoogle-api-client-java are more like leaf packages unless we
take openrefine in bullseye-backports into consideration as well. 

We could also mark the CVE as ignored for Bullseye because of the minor impact,
or just upload the new google-http-client-java package to bullseye after
approval by the release team and then update google-oauth-java-client as well.
We just have to check if this breaks the two other packages in Bullseye (bazel-
bootstrap and google-api-client-java).

So yes, a newer upstream version is fine, if it does not break any existing
packages and there is no other way or the alternative would be way too time
consuming and inconvenient. 

Cheers,

Markus



signature.asc
Description: This is a digitally signed message part

Bug#1011035: vlc: breaks pulseaudio

[Sebastian Ramacher]

Control: severity -1 normal
Control: reassign -1 pipewire 0.3.51-1
Control: retitle -1 pipewire: should pipewire depend/recommend 
libspa-0.2-bluetooth?

On 2022-05-15 23:51:47 +0200, Vincent Lefevre wrote:
> Control: reopen -1
> 
> On 2022-05-15 22:49:18 +0200, Sebastian Ramacher wrote:
> > On 2022-05-15 22:43:09 +0200, Vincent Lefevre wrote:
> > > After the upgrade to vlc 3.0.17.4-2, I can no longer use the
> > > bluetooth speakers with VLC. In pavucontrol, the stream doesn't
> > > appear in "Playback". So I suspect that it badly interacts
> > > with pulseaudio.
> > 
> > Don't install pipewire if you don't want it. vlc-plugin-pipewire is only
> > recommended and that package again only pulls in shared library packages
> > via Depends.
> 
> This is ridiculous. I've *NEVER* installed pipewire explicitly.
> It is automatically installed via library dependencies. So you
> need to handle that.

vlc doesn't. vlc is a meta package. There is a question to the pipewire
maintainers whether pipewire should depend or recommend
libspa-0.2-bluetooth to have a smoother transition from pulseaudio to
pipewire. Hence, reassigning there.

In any case, this bug hardly qualifies as grave.

Cheers
-- 
Sebastian Ramacher

Processed: Re: Bug#1011035: vlc: breaks pulseaudio

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1011035 [vlc] vlc: breaks pulseaudio
Severity set to 'normal' from 'grave'
> reassign -1 pipewire 0.3.51-1
Bug #1011035 [vlc] vlc: breaks pulseaudio
Bug reassigned from package 'vlc' to 'pipewire'.
No longer marked as found in versions vlc/3.0.17.4-2.
Ignoring request to alter fixed versions of bug #1011035 to the same values 
previously set
Bug #1011035 [pipewire] vlc: breaks pulseaudio
Marked as found in versions pipewire/0.3.51-1.
> retitle -1 pipewire: should pipewire depend/recommend libspa-0.2-bluetooth?
Bug #1011035 [pipewire] vlc: breaks pulseaudio
Changed Bug title to 'pipewire: should pipewire depend/recommend 
libspa-0.2-bluetooth?' from 'vlc: breaks pulseaudio'.

-- 
1011035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1010904: jquery-at.js: replace node-gulp-util build dependency with node-fancy-log

[Debian Bug Tracking System]

Processing control commands:

> summary -1 0
Summary recorded from message bug 1010904 message 22
> tags -1 - patch
Bug #1010904 [jquery-at.js] jquery-at.js: replace node-gulp-util build 
dependency with node-fancy-log
Removed tag(s) patch.

-- 
1010904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010904
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1010904: jquery-at.js: replace node-gulp-util build dependency with node-fancy-log

[Ben Finney]

Control: summary -1 0
Control: tags -1 - patch

The ‘gulp-util’ source fails to build in Debian; that package will
drop its ‘util’ module and dependent packages are advised to migrate
to other libraries. For ‘jquery-at.js’, the API ‘util.log’ needs a
replacement.

On 12-May-2022, Pirate Praveen wrote:
> Control: tags -1 patch
> 
> Please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010895 for
> details about removing node-gulp-util from the archive

Thanks for the report.

As far as I can determine, the relevant infromation for this package
is:

* Debian ‘node-gulp-util’ is dropping its ‘util’ module.

* The ‘jquery-at.js’ source package uses ‘util.log’, which will no
  longer be provided by ‘node-gulp-util’.

* The ‘node-fancy-log’ Debian package provides a ‘fancylog’ API which
  is a sufficient replacement.

> I have sent a merge request with a patch
> https://salsa.debian.org/debian/pkg-jquery-at.js/-/merge_requests/2

Thank you; that merge request does not contain the changes needed. I
have posted a review on that merge request.

Meanwhile I will work on implementing a fix for this bug.

-- 
 \  “Now Maggie, I’ll be watching you too, in case God is busy |
  `\   creating tornadoes or not existing.” —Homer, _The Simpsons_ |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Processed: Re: Bug#1011035: vlc: breaks pulseaudio

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1011035 {Done: Sebastian Ramacher } [vlc] vlc: 
breaks pulseaudio
Bug reopened
Ignoring request to alter fixed versions of bug #1011035 to the same values 
previously set

-- 
1011035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1011035: vlc: breaks pulseaudio

[Vincent Lefevre]

Control: reopen -1

On 2022-05-15 22:49:18 +0200, Sebastian Ramacher wrote:
> On 2022-05-15 22:43:09 +0200, Vincent Lefevre wrote:
> > After the upgrade to vlc 3.0.17.4-2, I can no longer use the
> > bluetooth speakers with VLC. In pavucontrol, the stream doesn't
> > appear in "Playback". So I suspect that it badly interacts
> > with pulseaudio.
> 
> Don't install pipewire if you don't want it. vlc-plugin-pipewire is only
> recommended and that package again only pulls in shared library packages
> via Depends.

This is ridiculous. I've *NEVER* installed pipewire explicitly.
It is automatically installed via library dependencies. So you
need to handle that.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1010958: sscg FTBFS with OpenSSL 3.0.3

[Kurt Roeckx]

It looks like it's fixed here: https://github.com/openssl/openssl/pull/18247

Bug#1011035: marked as done (vlc: breaks pulseaudio)

[Debian Bug Tracking System]

Your message dated Sun, 15 May 2022 22:49:18 +0200
with message-id 
and subject line Re: Bug#1011035: vlc: breaks pulseaudio
has caused the Debian Bug report #1011035,
regarding vlc: breaks pulseaudio
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.)


-- 
1011035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vlc
Version: 3.0.17.4-2
Severity: grave
Justification: renders package unusable

After the upgrade to vlc 3.0.17.4-2, I can no longer use the
bluetooth speakers with VLC. In pavucontrol, the stream doesn't
appear in "Playback". So I suspect that it badly interacts
with pulseaudio.

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.17.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages vlc depends on:
ii  vlc-bin  3.0.17.4-2
ii  vlc-plugin-base  3.0.17.4-2
ii  vlc-plugin-qt3.0.17.4-2
ii  vlc-plugin-video-output  3.0.17.4-2

Versions of packages vlc recommends:
ii  vlc-l10n   3.0.17.4-2
ii  vlc-plugin-access-extra3.0.17.4-2
ii  vlc-plugin-notify  3.0.17.4-2
ii  vlc-plugin-pipewire2-1+b1
ii  vlc-plugin-samba   3.0.17.4-2
ii  vlc-plugin-skins2  3.0.17.4-2
ii  vlc-plugin-video-splitter  3.0.17.4-2
ii  vlc-plugin-visualization   3.0.17.4-2

Versions of packages vlc suggests:
pn  vlc-plugin-fluidsynth  
pn  vlc-plugin-jack
pn  vlc-plugin-svg 

Versions of packages libvlc-bin depends on:
ii  libc62.33-7
ii  libvlc5  3.0.17.4-2

Versions of packages libvlc5 depends on:
ii  libc62.33-7
ii  libvlccore9  3.0.17.4-2

Versions of packages libvlc5 recommends:
ii  libvlc-bin  3.0.17.4-2

Versions of packages vlc-bin depends on:
ii  libc6   2.33-7
ii  libvlc-bin  3.0.17.4-2
ii  libvlc5 3.0.17.4-2

Versions of packages vlc-plugin-access-extra depends on:
ii  libc62.33-7
ii  libsrt1.4-gnutls 1.4.4-4
ii  libvlccore9 [vlc-plugin-abi-3-0-0f]  3.0.17.4-2
ii  libvncclient10.9.13+dfsg-3
ii  libxcb-composite01.14-3
ii  libxcb-shm0  1.14-3
ii  libxcb1  1.14-3

Versions of packages vlc-plugin-base depends on:
ii  liba52-0.7.4 0.7.4-20
ii  libarchive13 3.6.0-1
ii  libaribb24-0 1.0.3-2
ii  libasound2   1.2.6.1-2+b1
ii  libass9  1:0.16.0-1
ii  libavahi-client3 0.8-5
ii  libavahi-common3 0.8-5
ii  libavc1394-0 0.5.4-5
ii  libavcodec58 7:4.4.2-1
ii  libavformat587:4.4.2-1
ii  libavutil56  7:4.4.2-1
ii  libbluray2   1:1.3.1-1
ii  libc62.33-7
ii  libcairo21.16.0-5
ii  libcddb2 1.3.2-7
ii  libchromaprint1  1.5.1-2
ii  libdav1d50.9.2-1+b1
ii  libdbus-1-3  1.14.0-1
ii  libdc1394-25 2.2.6-4
ii  libdca0  0.0.7-2
ii  libdvbpsi10  1.3.3-1
ii  libdvdnav4   6.1.1-1
ii  libdvdread8  6.1.2-1
ii  libebml5 1.4.2-2
ii  libfaad2 2.10.0-2
ii  libflac8 1.3.4-1
ii  libfontconfig1   2.13.1-4.4
ii  libfreetype6 2.12.1+dfsg-1
ii  libfribidi0  1.0.8-2.1
ii  libgcc-s112.1.0-2
ii  libgcrypt20  1.10.1-2
ii  libglib2.0-0 2.72.1-1
ii  libgnutls30  3.7.4-2
ii  libgpg-error01.45-2
ii  libharfbuzz0b2.7.4-1+b1
ii  libixml101:1.8.4-2
ii  

Bug#1007732: marked as done (ccache: autopkgtest regression: cannot execute 'cc1plus')

[Debian Bug Tracking System]

Your message dated Sun, 15 May 2022 20:41:11 +
with message-id 
and subject line Bug#1007732: fixed in ccache 4.6.1-1
has caused the Debian Bug report #1007732,
regarding ccache: autopkgtest regression: cannot execute 'cc1plus'
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.)


-- 
1007732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007732
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: ccache
Version: 4.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of ccache the autopkgtest of ccache fails in 
testing when that autopkgtest is run with the binary packages of ccache 
from unstable. It passes when run with only packages from testing. In 
tabular form:


   passfail
ccache from testing4.6-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Are you 
missing a new test dependency?


Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=ccache

https://ci.debian.net/data/autopkgtest/testing/amd64/c/ccache/19983906/log.gz

Compiler: gcc (/usr/bin/gcc)
Compiler version: gcc (Debian 11.2.0-16) 11.2.0
CUDA compiler:not available

Running test suite 
basegcc: 
fatal error: cannot execute 'cc1plus': execvp: No such file or directory

compilation terminated.

FAILED

Test suite: base (line 1457)
Test case:  .incbin
Failure reason: Expected cache_miss to be 1, actual 0

Actual statistics counters
==
autoconf_test0
bad_compiler_arguments   0
bad_output_file  0
cache_miss   0
cache_size_kibibyte  0
called_for_link  0
called_for_preprocessing 0
cleanups_performed   0
compile_failed   0
compiler_check_failed0
compiler_produced_empty_output   0
compiler_produced_no_output  0
compiler_produced_stdout 0
could_not_find_compiler  0
could_not_use_modules0
could_not_use_precompiled_header 0
direct_cache_hit 0
direct_cache_miss0
error_hashing_extra_file 0
files_in_cache   0
internal_error   0
missing_cache_file   0
multiple_source_files0
no_input_file0
output_to_stdout 0
preprocessed_cache_hit   0
preprocessed_cache_miss  0
preprocessor_error   1
primary_storage_hit  0
primary_storage_miss 0
recache  0
secondary_storage_error  0
secondary_storage_hit0
secondary_storage_miss   0
secondary_storage_timeout0
unsupported_code_directive   2
unsupported_compiler_option  0
unsupported_source_language  0

Test data and log file have been left in testdir/1139 / testdir/failed
autopkgtest [02:56:37]: test run-testsuites



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ccache
Source-Version: 4.6.1-1
Done: Joel Rosdahl 

We believe that the bug you reported is fixed in the latest version of
ccache, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1007...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joel Rosdahl  (supplier of updated ccache package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 15 May 2022 21:48:25 +0200
Source: ccache
Architecture: source
Version: 4.6.1-1
Distribution: unstable
Urgency: medium
Maintainer: Joel Rosdahl 
Changed-By: Joel Rosdahl 
Closes: 1007732
Changes:
 ccache (4.6.1-1) unstable; urgency=medium
 .
   * New upstream release 4.6.1 

Bug#1011035: vlc: breaks pulseaudio

[Vincent Lefevre]

Package: vlc
Version: 3.0.17.4-2
Severity: grave
Justification: renders package unusable

After the upgrade to vlc 3.0.17.4-2, I can no longer use the
bluetooth speakers with VLC. In pavucontrol, the stream doesn't
appear in "Playback". So I suspect that it badly interacts
with pulseaudio.

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.17.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages vlc depends on:
ii  vlc-bin  3.0.17.4-2
ii  vlc-plugin-base  3.0.17.4-2
ii  vlc-plugin-qt3.0.17.4-2
ii  vlc-plugin-video-output  3.0.17.4-2

Versions of packages vlc recommends:
ii  vlc-l10n   3.0.17.4-2
ii  vlc-plugin-access-extra3.0.17.4-2
ii  vlc-plugin-notify  3.0.17.4-2
ii  vlc-plugin-pipewire2-1+b1
ii  vlc-plugin-samba   3.0.17.4-2
ii  vlc-plugin-skins2  3.0.17.4-2
ii  vlc-plugin-video-splitter  3.0.17.4-2
ii  vlc-plugin-visualization   3.0.17.4-2

Versions of packages vlc suggests:
pn  vlc-plugin-fluidsynth  
pn  vlc-plugin-jack
pn  vlc-plugin-svg 

Versions of packages libvlc-bin depends on:
ii  libc62.33-7
ii  libvlc5  3.0.17.4-2

Versions of packages libvlc5 depends on:
ii  libc62.33-7
ii  libvlccore9  3.0.17.4-2

Versions of packages libvlc5 recommends:
ii  libvlc-bin  3.0.17.4-2

Versions of packages vlc-bin depends on:
ii  libc6   2.33-7
ii  libvlc-bin  3.0.17.4-2
ii  libvlc5 3.0.17.4-2

Versions of packages vlc-plugin-access-extra depends on:
ii  libc62.33-7
ii  libsrt1.4-gnutls 1.4.4-4
ii  libvlccore9 [vlc-plugin-abi-3-0-0f]  3.0.17.4-2
ii  libvncclient10.9.13+dfsg-3
ii  libxcb-composite01.14-3
ii  libxcb-shm0  1.14-3
ii  libxcb1  1.14-3

Versions of packages vlc-plugin-base depends on:
ii  liba52-0.7.4 0.7.4-20
ii  libarchive13 3.6.0-1
ii  libaribb24-0 1.0.3-2
ii  libasound2   1.2.6.1-2+b1
ii  libass9  1:0.16.0-1
ii  libavahi-client3 0.8-5
ii  libavahi-common3 0.8-5
ii  libavc1394-0 0.5.4-5
ii  libavcodec58 7:4.4.2-1
ii  libavformat587:4.4.2-1
ii  libavutil56  7:4.4.2-1
ii  libbluray2   1:1.3.1-1
ii  libc62.33-7
ii  libcairo21.16.0-5
ii  libcddb2 1.3.2-7
ii  libchromaprint1  1.5.1-2
ii  libdav1d50.9.2-1+b1
ii  libdbus-1-3  1.14.0-1
ii  libdc1394-25 2.2.6-4
ii  libdca0  0.0.7-2
ii  libdvbpsi10  1.3.3-1
ii  libdvdnav4   6.1.1-1
ii  libdvdread8  6.1.2-1
ii  libebml5 1.4.2-2
ii  libfaad2 2.10.0-2
ii  libflac8 1.3.4-1
ii  libfontconfig1   2.13.1-4.4
ii  libfreetype6 2.12.1+dfsg-1
ii  libfribidi0  1.0.8-2.1
ii  libgcc-s112.1.0-2
ii  libgcrypt20  1.10.1-2
ii  libglib2.0-0 2.72.1-1
ii  libgnutls30  3.7.4-2
ii  libgpg-error01.45-2
ii  libharfbuzz0b2.7.4-1+b1
ii  libixml101:1.8.4-2
ii  libjpeg62-turbo  1:2.1.2-1
ii  libkate1 0.4.1-11
ii  liblirc-client0  0.10.1-7
ii  liblua5.2-0  5.2.4-2
ii  libmad0  0.15.1b-10
ii  libmatroska7 1.6.3-2
ii  libmpcdec6   2:0.1~r495-2
ii  libmpeg2-4   0.5.1-9
ii  libmpg123-0  1.29.3-1
ii  libmtp9  1.1.19-1
ii  libncursesw6 6.3+20220423-2
ii  libnfs13 4.0.0-1
ii  libogg0  1.3.4-0.1
ii  libopenmpt-modplug1  0.8.9.0-openmpt1-2
ii  libopus0 1.3.1-0.1
ii  libpng16-16 

Bug#1011033: onnx: flaky autopkgtest on armhf: Arrays are not almost equal to 7 decimals

[Paul Gevers]

Source: onnx
Version: 1.7.0+dfsg-3
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package on armhf 
because it was showing up as a regression for the upload of gcc-12. I 
noticed that the test regularly fails, it seems to be restricted to this 
architecture.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/packages/o/onnx/

https://ci.debian.net/data/autopkgtest/testing/armhf/o/onnx/21152474/log.gz

=== FAILURES 
===
_ TestOptimizer.test_fuse_bn_into_conv_simple 
__


self = testMethod=test_fuse_bn_into_conv_simple>


def test_fuse_bn_into_conv_simple(self):  # type: () -> None
for (tensor_type, np_type) in [(TensorProto.FLOAT, np.float32), 
(TensorProto.DOUBLE, np.float64)]:

conv = helper.make_node("Conv", ["X", "W", "B"], ["Y"])
bn = helper.make_node("BatchNormalization", [
  "Y", "scale", "b", "mean", "var"], ["Z"])

W = np.random.randn(3, 2, 5, 5).astype(np_type) + 2
B = np.random.randn(3,).astype(np_type) + 2
scale = np.random.randn(3,).astype(np_type) + 2
b = np.random.randn(3,).astype(np_type) + 2
mean = np.random.randn(3,).astype(np_type) + 2
var = np.abs(np.random.randn(3,).astype(np_type)) + 2

initializers = [
helper.make_tensor(name, tensor_type,
   npa.shape, npa.tobytes(), raw=True)
for name, npa in [('W', W), ('B', B), ('scale', scale), 
('b', b), ('mean', mean), ('var', var)]

]
graph = helper.make_graph(
[conv, bn],
"test",
[helper.make_tensor_value_info("X", tensor_type, (5, 2, 
28, 28)),
 helper.make_tensor_value_info("W", tensor_type, (3, 2, 
5, 5)),

 helper.make_tensor_value_info("B", tensor_type, (3,)),
 helper.make_tensor_value_info("scale", tensor_type, (3,)),
 helper.make_tensor_value_info("b", tensor_type, (3,)),
 helper.make_tensor_value_info("mean", tensor_type, (3,)),
 helper.make_tensor_value_info("var", tensor_type, (3,))],
[helper.make_tensor_value_info(
"Z", tensor_type, (5, 3, 24, 24))],
initializer=initializers,
value_info=[
helper.make_tensor_value_info(
"Y", tensor_type, (5, 3, 24, 24))
]
)
optimized_model = self._optimized(graph, ["fuse_bn_into_conv"])

self.assertEqual(len(optimized_model.graph.node), 1)
self.assertEqual(optimized_model.graph.node[0].op_type, 'Conv')
self.assertEqual(len(optimized_model.graph.initializer), 2)
new_W = 
numpy_helper.to_array(optimized_model.graph.initializer[0])
new_b = 
numpy_helper.to_array(optimized_model.graph.initializer[1])


f = scale / np.sqrt(var + 1e-5)
np.testing.assert_almost_equal((B - mean) * f + b, new_b)
>   np.testing.assert_almost_equal(
W * f[:, np.newaxis, np.newaxis, np.newaxis], new_W)
E   AssertionError:
E   Arrays are not almost equal to 7 decimals
E
E   Mismatched elements: 2 / 150 (1.33%)
E   Max absolute difference: 2.3841858e-07
E   Max relative difference: 1.1832779e-07
Ex: array( 1.3602041,  0.6074747,  0.5127016, 
1.3461237,  0.3262223],
E[ 1.1601448,  1.40072  ,  2.0301225,  1.1147949, 
1.3020884],
E[ 0.6207906,  1.1024365,  1.3334007,  1.5556062, 
1.4650011],...
Ey: array( 1.3602041,  0.6074747,  0.5127015, 
1.3461237,  0.326],
E[ 1.1601447,  1.40072  ,  2.0301223,  1.1147949, 
1.3020883],
E[ 0.6207906,  1.1024364,  1.3334006,  1.5556061, 
1.465001 ],...


onnx/test/optimizer_test.py:1510: AssertionError
=== warnings summary 
===


OpenPGP_signature
Description: OpenPGP digital signature

Bug#997434: xpaint: FTBFS: -q: invalid option -- '.'

[Vagrant Cascadian]

Control: notfound 997434 2.9.1.4-4

On 2022-05-14, Vagrant Cascadian wrote:
> Version: 2.9.1.4-4

Given that the fixed version and the originally reported version are the
same... mark this as notfound in the original version. Hopefully that
actually works.

Seems like it was a transient toolchain issue.

live well,
  vagrant


signature.asc
Description: PGP signature

Processed: Re: Bug#997434: xpaint: FTBFS: -q: invalid option -- '.'

[Debian Bug Tracking System]

Processing control commands:

> notfound 997434 2.9.1.4-4
Bug #997434 {Done: Vagrant Cascadian } [src:xpaint] xpaint: 
FTBFS: -q: invalid option -- '.'
No longer marked as found in versions xpaint/2.9.1.4-4.

-- 
997434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#999725: marked as done (ruby-omniauth-saml: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_d

[Debian Bug Tracking System]

Your message dated Sun, 15 May 2022 19:22:41 +
with message-id 
and subject line Bug#999725: fixed in ruby-omniauth-saml 2.1.0-1
has caused the Debian Bug report #999725,
regarding ruby-omniauth-saml: FTBFS with ruby-omniauth 2.0.x: ERROR: Test 
"ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in 
`rescue in block in activate_dependencies': Could not find 'omniauth' (~> 1.3, 
>= 1.3.2) among 77 total gem(s) (Gem::MissingSpecError)
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.)


-- 
999725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-omniauth-saml
Version: 1.10.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-omniauth-2.0

Hi,

I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test
rebuild, ruby-omniauth-saml was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-omniauth from experimental
on an unstable system or build chroot. I would expect a new upstream version to
work against the latest ruby-omniauth just fine.

Relevant part (hopefully):
> /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block 
> in activate_dependencies': Could not find 'omniauth' (~> 1.3, >= 1.3.2) among 
> 77 total gem(s) (Gem::MissingSpecError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-omniauth-saml/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
>  at: 
> /<>/debian/ruby-omniauth-saml/usr/share/rubygems-integration/all/specifications/omniauth-saml-1.10.0.gemspec,
>  execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not 
> find 'omniauth' (~> 1.3, >= 1.3.2) - did find: [omniauth-2.0.4] 
> (Gem::MissingSpecVersionError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-omniauth-saml/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
>  , execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> benchmark (default: 0.1.0)
> bigdecimal (default: 2.0.0)
> bundler (default: 2.1.4)
> cgi (default: 0.1.0)
> csv (default: 3.1.2)
> date (default: 3.0.0)
> dbm (default: 1.1.0)
> delegate (default: 0.1.0)
> did_you_mean (default: 1.4.0)
> diff-lcs (1.4.4)
> docile (1.1.5)
> etc (default: 1.1.0)
> fcntl (default: 1.0.0)
> fiddle (default: 1.0.0)
> fileutils (default: 1.4.1)
> forwardable (default: 1.3.1)
> gdbm (default: 2.1.0)
> getoptlong (default: 0.1.0)
> hashie (3.5.5)
> io-console (default: 0.5.6)
> ipaddr (default: 1.2.2)
> irb (default: 1.2.6)
> json (default: 2.3.0)
> logger (default: 1.4.2)
> macaddr (1.7.1)
> matrix (default: 0.2.0)
> minitest (5.13.0)
> mutex_m (default: 0.1.0)
> net-pop (default: 0.1.0)
> net-smtp (default: 0.1.0)
> 

Processed: affects 1011032

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 1011032 src:haskell-haxr src:haskell-hookup 
> src:haskell-hsopenssl-x509-system src:haskell-http-streams 
> src:haskell-openssl-streams
Bug #1011032 [libghc-hsopenssl-dev] libghc-hsopenssl-dev needs update for 
OpenSSL 3.0
Added indication that 1011032 affects src:haskell-haxr, src:haskell-hookup, 
src:haskell-hsopenssl-x509-system, src:haskell-http-streams, and 
src:haskell-openssl-streams
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1011032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: libghc-hsopenssl-dev needs update for OpenSSL 3.0

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:glirc
Bug #1011032 [libghc-hsopenssl-dev] libghc-hsopenssl-dev needs update for 
OpenSSL 3.0
Added indication that 1011032 affects src:glirc

-- 
1011032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1011032: libghc-hsopenssl-dev needs update for OpenSSL 3.0

[Adrian Bunk]

Package: libghc-hsopenssl-dev
Version: 0.11.4.18-1
Severity: serious
Tags: ftbfs
Control: affects -1 src:glirc

https://buildd.debian.org/status/logs.php?pkg=glirc=2.36-3%2Bb2

...
Linking dist-ghc/build/glirc/glirc ...
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4/HsOpenSSL-0.11.4.18-6UnNvQ306xc6HmhIhGM8NK/libHSHsOpenSSL-0.11.4.18-6UnNvQ306xc6HmhIhGM8NK.a(PKey.o):function
 
HsOpenSSLzm0zi11zi4zi18zm6UnNvQ306xc6HmhIhGM8NK_OpenSSLziEVPziPKey_zdwzdsrsaFromPKey1_info:
 error: undefined reference to 'EVP_PKEY_base_id'
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4/HsOpenSSL-0.11.4.18-6UnNvQ306xc6HmhIhGM8NK/libHSHsOpenSSL-0.11.4.18-6UnNvQ306xc6HmhIhGM8NK.a(PKey.o):function
 
HsOpenSSLzm0zi11zi4zi18zm6UnNvQ306xc6HmhIhGM8NK_OpenSSLziEVPziPKey_zdwzdsrsaFromPKey_info:
 error: undefined reference to 'EVP_PKEY_base_id'
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4/HsOpenSSL-0.11.4.18-6UnNvQ306xc6HmhIhGM8NK/libHSHsOpenSSL-0.11.4.18-6UnNvQ306xc6HmhIhGM8NK.a(PKey.o):function
 
HsOpenSSLzm0zi11zi4zi18zm6UnNvQ306xc6HmhIhGM8NK_OpenSSLziEVPziPKey_zdwzdsdsaFromPKey1_info:
 error: undefined reference to 'EVP_PKEY_base_id'
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4/HsOpenSSL-0.11.4.18-6UnNvQ306xc6HmhIhGM8NK/libHSHsOpenSSL-0.11.4.18-6UnNvQ306xc6HmhIhGM8NK.a(PKey.o):function
 
HsOpenSSLzm0zi11zi4zi18zm6UnNvQ306xc6HmhIhGM8NK_OpenSSLziEVPziPKey_zdwzdsdsaFromPKey_info:
 error: undefined reference to 'EVP_PKEY_base_id'
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4/HsOpenSSL-0.11.4.18-6UnNvQ306xc6HmhIhGM8NK/libHSHsOpenSSL-0.11.4.18-6UnNvQ306xc6HmhIhGM8NK.a(Session.o):function
 HsOpenSSLzm0zi11zi4zi18zm6UnNvQ306xc6HmhIhGM8NK_OpenSSLziSession_zdwio_info: 
error: undefined reference to 'SSL_get_peer_certificate'
collect2: error: ld returned 1 exit status
`x86_64-linux-gnu-gcc' failed in phase `Linker'. (Exit code: 1)
 at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 106.

Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
 "build", "--builddir=dist-ghc") called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 130

Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup", 
"build", "--builddir=dist-ghc") called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 649
Debian::Debhelper::Buildsystem::Haskell::Recipes::build_recipe() called 
at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25


The Ubuntu diff seems to contain a fix.

Bug#1005674: marked as done (apertium-mk-en: FTBFS: wrong parameters to apertium-gen-modes)

[Debian Bug Tracking System]

Your message dated Sun, 15 May 2022 19:00:09 +
with message-id 
and subject line Bug#1005674: fixed in apertium-mkd-eng 0.1.3-1
has caused the Debian Bug report #1005674,
regarding apertium-mk-en: FTBFS: wrong parameters to apertium-gen-modes
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.)


-- 
1005674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apertium-mk-en
Version: 0.1.1~r57554-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> make[2]: Nothing to be done for 'install-exec-am'.
> mv modes modes.bak
>  /bin/mkdir -p 
> '/<>/debian/apertium-mk-en/usr/share/apertium/apertium-mk-en/'
> apertium-gen-modes modes.xml apertium-mk-en
>  /usr/bin/install -c -m 644 mk-en.automorf.bin en-mk.automorf.bin 
> mk-en.autobil.bin mk-en.autogen.bin mk-en.prob mk-en.t1x.bin mk-en.t2x.bin 
> mk-en.t3x.bin mk-en.rlx.bin mk-en.lex.bin lexchoicebil.xsl mk-en.alpha.bin 
> apertium-mk-en.mk-en.t1x apertium-mk-en.mk-en.t2x apertium-mk-en.mk-en.t3x 
> mk-en.autopgen.bin modes.xml 
> '/<>/debian/apertium-mk-en/usr/share/apertium/apertium-mk-en/'
> apertium-gen-modes: 
> USAGE: apertium-gen-modes [-fvh] modes.xml [install_path]
>   -f, --full:  expect absolute installation path
>   -v, --verbose:   print more detailed messages
>   -h, --help:  display this help
> make[2]: *** [Makefile:721: install-data-local] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/02/12/apertium-mk-en_0.1.1~r57554-3_unstable.log

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: apertium-mkd-eng
Source-Version: 0.1.3-1
Done: Kartik Mistry 

We believe that the bug you reported is fixed in the latest version of
apertium-mkd-eng, 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.
Kartik Mistry  (supplier of updated apertium-mkd-eng package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 10 May 2022 21:43:50 +0530
Source: apertium-mkd-eng
Binary: apertium-mk-en apertium-mkd-eng
Architecture: source all
Version: 0.1.3-1
Distribution: experimental
Urgency: low
Maintainer: Debian Science Team 

Changed-By: Kartik Mistry 
Description:
 apertium-mk-en - Transitional dummy package for apertium-mkd-eng
 apertium-mkd-eng - Apertium translation data for the Macedonian-English pair
Closes: 1005674
Changes:
 apertium-mkd-eng (0.1.3-1) experimental; urgency=low
 .
   [ Tino Didriksen ]
   * Update to latest release (Closes: #1005674)
   * Renamed to apertium-mkd-eng, with transitional package apertium-mk-en
Checksums-Sha1:
 5ec726d388ec8e99fb3450ff7a08d76971935e78 2191 apertium-mkd-eng_0.1.3-1.dsc
 7457bc97c982486a16eb388483e8f193a32d30c8 1053021 
apertium-mkd-eng_0.1.3.orig.tar.bz2
 c4e8a919e24b5feeddc72bc626a6372af6dc8401 2624 
apertium-mkd-eng_0.1.3-1.debian.tar.xz
 05e64a842df47afe10d3ed280fee3b0d3ac75c85 2736 apertium-mk-en_0.1.3-1_all.deb
 d758b89bc3ae332c8682bd960725f4fc02c13557 1037936 
apertium-mkd-eng_0.1.3-1_all.deb
 c1152d30edcb682550ac00941ce3fd57a5304f1c 7121 
apertium-mkd-eng_0.1.3-1_amd64.buildinfo
Checksums-Sha256:
 b5e84a0b291c791eb2af8a4682dab88134d276ccab9ee23f70dee41495522fe6 2191 
apertium-mkd-eng_0.1.3-1.dsc
 6bd93d351faf9e86dec19d81b0b51e6cb6b1d3dfc7a218c519ba5f2e751e1320 1053021 
apertium-mkd-eng_0.1.3.orig.tar.bz2
 98fa4e479ca4f86c2bc9177abaf4cd5ca45f6eccbf43b6d7957e506073eea4bd 2624 

Processed: Re: tagging 1009406

[Debian Bug Tracking System]

Processing control commands:

> tag -1 - confirmed
Bug #1009406 [src:libzonemaster-perl] libzonemaster-perl: FTBFS: dh_auto_test: 
error: make -j1 test TEST_VERBOSE=1 returned exit code 2
Removed tag(s) confirmed.
> tag -1 + unreproducible
Bug #1009406 [src:libzonemaster-perl] libzonemaster-perl: FTBFS: dh_auto_test: 
error: make -j1 test TEST_VERBOSE=1 returned exit code 2
Added tag(s) unreproducible.
> severity -1 important
Bug #1009406 [src:libzonemaster-perl] libzonemaster-perl: FTBFS: dh_auto_test: 
error: make -j1 test TEST_VERBOSE=1 returned exit code 2
Severity set to 'important' from 'serious'

-- 
1009406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009406
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1009406: tagging 1009406

[gregor herrmann]

Control: tag -1 - confirmed
Control: tag -1 + unreproducible
Control: severity -1 important

On Wed, 13 Apr 2022 18:22:27 +0200, gregor herrmann wrote:

> tags 1009406 + confirmed
> thanks

Looking again a month later, I can't reproduce the test failure
anymore. (Even after trying a cpuple of times.)

As I don't know yet what has changed, I'm not closing the bug but lower
the severity.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#1010958: sscg FTBFS with OpenSSL 3.0

[Martin Pitt]

Control: tag -1 upstream confirmed
Control: retitle -1 sscg FTBFS with OpenSSL 3.0.3

Adrian Bunk [2022-05-14  9:48 +0300]:
> https://buildd.debian.org/status/logs.php?pkg=sscg=3.0.2-1%2Bb1
> 
> ...
>  1/10 generate_rsa_key_test FAIL  0.01s   killed by signal 11 
> SIGSEGV
> 04:32:21 MALLOC_PERTURB_=87 
> /<>/obj-x86_64-linux-gnu/generate_rsa_key_test

Trivially reproducible locally, see below. It still works with the previous
3.0.2-1 version, so this is a very recent regression.

I can't tell yet whether this is a bug in sscg or OpenSSL. Fedora still has
3.0.2, so Debian is just the first distro where we noticed.

I confirm this also still happens with current upstream main (02f0a22769a6).

| ❱❱❱ gdb ./generate_rsa_key_test
| Starting program: /var/home/martin/debian/sscg/b/generate_rsa_key_test
| [Thread debugging using libthread_db enabled]
| Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
| 
| Program received signal SIGSEGV, Segmentation fault.
| __strcasecmp_l_avx () at ../sysdeps/x86_64/multiarch/strcmp-sse42.S:141
| 141   ../sysdeps/x86_64/multiarch/strcmp-sse42.S: No such file or directory.
| (gdb) bt full
| #0  __strcasecmp_l_avx () at ../sysdeps/x86_64/multiarch/strcmp-sse42.S:141
| No locals.
| #1  0x77d471df in EVP_PKEY_Q_keygen (libctx=libctx@entry=0x0, 
propq=propq@entry=0x0, type=type@entry=0x60ef "RSA")
| at ../crypto/evp/evp_lib.c:1172
| args = {{gp_offset = 24, fp_offset = 32767, overflow_arg_area = 
0x7fffe6a0, reg_save_area = 0x7fffe650}}
| bits = 93824992239747
| name = 
| params = {{key = 0x0, data_type = 0, data = 0x0, data_size = 0, 
return_size = 0}, {key = 0x0, data_type = 0, data = 0x0,
| data_size = 0, return_size = 0}}
| ret = 0x0
| __func__ = "EVP_PKEY_Q_keygen"
| #2  0x537f in sscg_generate_rsa_key 
(mem_ctx=mem_ctx@entry=0x9300, bits=bits@entry=512,
| _key=_key@entry=0x7fffe6c8) at ../src/key.c:48
| ret = 
| pkey = 0x0
| tmp_ctx = 0x0
| #3  0x51b6 in main (argc=, argv=) 
at ../test/generate_rsa_key_test.c:46
| ret = 
| pkey = 0x
| j = 
| bits = {512, , , , 
}
| tmp_ctx = 0x9300
| (gdb)

Thanks,

Martin

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

[Debian Bug Tracking System]

Processing control commands:

> tag -1 upstream confirmed
Bug #1010958 [src:sscg] sscg FTBFS with OpenSSL 3.0
Added tag(s) confirmed and upstream.
> retitle -1 sscg FTBFS with OpenSSL 3.0.3
Bug #1010958 [src:sscg] sscg FTBFS with OpenSSL 3.0
Changed Bug title to 'sscg FTBFS with OpenSSL 3.0.3' from 'sscg FTBFS with 
OpenSSL 3.0'.

-- 
1010958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010958
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[tony mancill]

On Mon, May 09, 2022 at 09:23:36PM -0700, tony mancill wrote:
> On Fri, May 06, 2022 at 09:46:24AM +0100, Neil Williams wrote:
> > Source: google-oauth-client-java
> > Version: 1.28.0-2
> > Severity: grave
> > Tags: security
> > Justification: user security hole
> > 
> > Fixed in upstream release 1.33.3
> > 
> > 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-2021-22573
> > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22573
> > 
> > Please adjust the affected versions in the BTS as needed.
> 
> Upstream version 1.33.3 requires a minor update to the Debian packaging
> of google-http-client-java that I am working on now.
> 
> I will upload a package for 1.33.3 in the next day or so.

In order to backport this patch for bullseye, we will need a version of
google-http-client-java in bullseye that includes
google-http-client-gson.jar (as was added in [1]).  I'm not sure how
this works if a security update for package requires an update to its
build-deps.

Based on the limited set of reverse-dependencies of
libgoogle-oauth-client-java in bullseye - that is:

$ reverse-depends --build --list --release=bullseye libgoogle-oauth-client-java
google-api-client-java

$ reverse-depends --list --release=bullseye libgoogle-oauth-client-java 
(nothing) 

$ reverse-depends --list --release=bullseye libgoogle-api-client-java
bazel-bootstrap

$ reverse-depends --build --list --release=bullseye libgoogle-api-client-java
bazel-bootstrap

$ reverse-depends --build --list --release=bullseye bazel-bootstrap
(nothing)

And the chain seems to end there.  As I understand it, getting
bazel-bootstrap into bullseye was in preparation for bookworm, but there
aren't any packages with build-deps on it bullseye.

For that reason, I'm wondering whether we wouldn't be better off
updating instead backporting to address this CVE.  Related to this,
Markus has already created a backport of google-http-client-java [2].
(That is, there are other reasons for a newer versions in bullseye.)

Any thoughts?  It's a tad messy either way, but using current versions
simplifies the porting of patches.

Thank you,
tony

[1] 
https://tracker.debian.org/news/1323863/accepted-google-http-client-java-1418-2-source-into-unstable/
[2] 
https://tracker.debian.org/news/1292692/accepted-google-http-client-java-1401-1bpo111-source-all-into-bullseye-backports-bullseye-backports/


signature.asc
Description: PGP signature

Bug#1006512: marked as done (ocaml-cohttp: FTBFS with OpenSSL 3.0)

[Debian Bug Tracking System]

Your message dated Sun, 15 May 2022 19:52:03 +0300
with message-id <20220515165203.GA30916@localhost>
and subject line Re: Bug#1006512: ocaml-cohttp: FTBFS with OpenSSL 3.0
has caused the Debian Bug report #1006512,
regarding ocaml-cohttp: 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.)


-- 
1006512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ocaml-cohttp
Version: 4.0.0-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
control: forwarded -1

Your package is failing to build using OpenSSL 3.0 with the
following error:

| OCAMLPATH=/<>/_tmp/usr/lib/ocaml dune build -p cohttp-lwt-unix
| ocamlopt cohttp-lwt-unix/bin/cohttp_curl_lwt.exe (exit 2)
| (cd _build/default && /usr/bin/ocamlopt.opt -w -40 -g -o 
cohttp-lwt-unix/bin/cohttp_curl_lwt.exe /usr/lib/ocaml/fmt/fmt.cmxa 
/usr/lib/ocaml/logs/logs.cmxa /usr/lib/ocaml/result/result.cmxa 
/usr/lib/ocaml/lwt/lwt.cmxa /usr/lib/ocaml/logs/logs_lwt.cmxa 
/usr/lib/ocaml/unix.cmxa -I /usr/lib/ocaml /usr/lib/ocaml/bigarray.cmxa -I 
/usr/lib/ocaml /usr/lib/ocaml/sexplib0/sexplib0.cmxa 
/usr/lib/ocaml/base/caml/caml.cmxa /usr/lib/ocaml/parsexp/parsexp.cmxa 
/usr/lib/ocaml/sexplib/sexplib.cmxa /usr/lib/ocaml/macaddr/macaddr.cmxa 
/usr/lib/ocaml/domain-name/domain_name.cmxa /usr/lib/ocaml/ipaddr/ipaddr.cmxa 
/usr/lib/ocaml/ppx_sexp_conv/runtime-lib/ppx_sexp_conv_lib.cmxa 
/usr/lib/ocaml/ipaddr-sexp/ipaddr_sexp.cmxa 
/usr/lib/ocaml/stringext/stringext.cmxa 
/usr/lib/ocaml/bigarray-compat/bigarray_compat.cmxa 
/usr/lib/ocaml/bigstringaf/bigstringaf.cmxa -I /usr/lib/ocaml/bigstringaf 
/usr/lib/ocaml/angstrom/angstrom.cmxa /usr/lib/ocaml/uri/uri.cmxa 
/usr/lib/ocaml/astring/astring.cmxa /usr/lib/ocaml/conduit/conduit.cmxa 
/usr/lib/ocaml/conduit-lwt/conduit_lwt.cmxa 
/usr/lib/ocaml/magic-mime/magic_mime_library.cmxa /usr/lib/ocaml/mmap/mmap.cmxa 
/usr/lib/ocaml/ocplib-endian/ocplib_endian.cmxa 
/usr/lib/ocaml/ocplib-endian/bigstring/ocplib_endian_bigstring.cmxa 
/usr/lib/ocaml/threads/threads.cmxa -I /usr/lib/ocaml 
/usr/lib/ocaml/lwt/unix/lwt_unix.cmxa -I /usr/lib/ocaml/lwt/unix 
/usr/lib/ocaml/uri/services/uri_services.cmxa 
/usr/lib/ocaml/ipaddr/unix/ipaddr_unix.cmxa /usr/lib/ocaml/ssl/ssl.cmxa -I 
/usr/lib/ocaml/ssl /usr/lib/ocaml/lwt_ssl/lwt_ssl.cmxa 
/usr/lib/ocaml/conduit-lwt-unix/conduit_lwt_unix.cmxa /usr/lib/ocaml/re/re.cmxa 
/usr/lib/ocaml/uri-sexp/uri_sexp.cmxa /usr/lib/ocaml/base64/base64.cmxa 
/<>/_tmp/usr/lib/ocaml/cohttp/cohttp.cmxa 
/<>/_tmp/usr/lib/ocaml/cohttp-lwt/cohttp_lwt.cmxa 
/usr/lib/ocaml/logs/logs_fmt.cmxa cohttp-lwt-unix/src/cohttp_lwt_unix.cmxa 
cohttp_server/cohttp_server.cmxa /usr/lib/ocaml/cmdliner/cmdliner.cmxa 
/usr/lib/ocaml/logs/logs_cli.cmxa 
cohttp-lwt-unix/bin/.cohttp_curl_lwt.eobjs/native/dune__exe.cmx 
cohttp-lwt-unix/bin/.cohttp_curl_lwt.eobjs/native/dune__exe__Cohttp_curl_lwt.cmx)
| /usr/bin/ld: /usr/lib/ocaml/ssl/libssl_stubs.a(ssl_stubs.o): in function 
`ocaml_ssl_get_certificate':
| (.text+0x1c91): undefined reference to `SSL_get_peer_certificate'
| collect2: error: ld returned 1 exit status
| File "caml_startup", line 1:
| Error: Error during linking (exit code 1)
| ocamlopt cohttp-lwt-unix/bin/cohttp_proxy_lwt.exe (exit 2)
| (cd _build/default && /usr/bin/ocamlopt.opt -w -40 -g -o 
cohttp-lwt-unix/bin/cohttp_proxy_lwt.exe /usr/lib/ocaml/fmt/fmt.cmxa 
/usr/lib/ocaml/logs/logs.cmxa /usr/lib/ocaml/result/result.cmxa 
/usr/lib/ocaml/lwt/lwt.cmxa /usr/lib/ocaml/logs/logs_lwt.cmxa 
/usr/lib/ocaml/unix.cmxa -I /usr/lib/ocaml /usr/lib/ocaml/bigarray.cmxa -I 
/usr/lib/ocaml /usr/lib/ocaml/sexplib0/sexplib0.cmxa 
/usr/lib/ocaml/base/caml/caml.cmxa /usr/lib/ocaml/parsexp/parsexp.cmxa 
/usr/lib/ocaml/sexplib/sexplib.cmxa /usr/lib/ocaml/macaddr/macaddr.cmxa 
/usr/lib/ocaml/domain-name/domain_name.cmxa /usr/lib/ocaml/ipaddr/ipaddr.cmxa 
/usr/lib/ocaml/ppx_sexp_conv/runtime-lib/ppx_sexp_conv_lib.cmxa 
/usr/lib/ocaml/ipaddr-sexp/ipaddr_sexp.cmxa 
/usr/lib/ocaml/stringext/stringext.cmxa 
/usr/lib/ocaml/bigarray-compat/bigarray_compat.cmxa 
/usr/lib/ocaml/bigstringaf/bigstringaf.cmxa -I /usr/lib/ocaml/bigstringaf 
/usr/lib/ocaml/angstrom/angstrom.cmxa /usr/lib/ocaml/uri/uri.cmxa 
/usr/lib/ocaml/astring/astring.cmxa /usr/lib/ocaml/conduit/conduit.cmxa 
/usr/lib/ocaml/conduit-lwt/conduit_lwt.cmxa 
/usr/lib/ocaml/magic-mime/magic_mime_library.cmxa /usr/lib/ocaml/mmap/mmap.cmxa 
/usr/lib/ocaml/ocplib-endian/ocplib_endian.cmxa 

Bug#1011011: marked as done (thrift FTBFS on IPV6-only buildds)

[Debian Bug Tracking System]

Your message dated Sun, 15 May 2022 16:50:44 +
with message-id 
and subject line Bug#1011011: fixed in thrift 0.16.0-5
has caused the Debian Bug report #1011011,
regarding thrift FTBFS on IPV6-only buildds
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.)


-- 
1011011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: thrift
Version: 0.16.0-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=thrift=all
https://buildd.debian.org/status/logs.php?pkg=thrift=amd64

...
[1;31;49m*** 3 failures are detected in the test module "TNonblockingServerTest"
FAIL: TNonblockingServerTest
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: Serving with 1 io threads.
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: using libevent 
2.1.12-stable method epoll
Thrift: Sun May 15 10:06:02 2022 TNonblocking: IO thread #0 registered for 
listen.
Thrift: Sun May 15 10:06:02 2022 TNonblocking: IO thread #0 registered for 
notify.
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: IO thread #0 entering 
loop...
Thrift: Sun May 15 10:06:02 2022 TSocket::open() connect() : Connection refused
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: IO thread #0 run() done!
Thrift: Sun May 15 10:06:02 2022 TNonblocking: join done for IO thread #0
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: Serving with 1 io threads.
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: using libevent 
2.1.12-stable method epoll
Thrift: Sun May 15 10:06:02 2022 TNonblocking: IO thread #0 registered for 
listen.
Thrift: Sun May 15 10:06:02 2022 TNonblocking: IO thread #0 registered for 
notify.
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: IO thread #0 entering 
loop...
Thrift: Sun May 15 10:06:02 2022 TSocket::open() connect() : Connection refused
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: IO thread #0 run() done!
Thrift: Sun May 15 10:06:02 2022 TNonblocking: join done for IO thread #0
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: Serving with 1 io threads.
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: using libevent 
2.1.12-stable method epoll
Thrift: Sun May 15 10:06:02 2022 TNonblocking: IO thread #0 registered for 
listen.
Thrift: Sun May 15 10:06:02 2022 TNonblocking: IO thread #0 registered for 
notify.
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: IO thread #0 entering 
loop...
Thrift: Sun May 15 10:06:02 2022 TSocket::open() connect() : Connection refused
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: IO thread #0 run() done!
Thrift: Sun May 15 10:06:02 2022 TNonblocking: join done for IO thread #0

*** 3 failures are detected in the test module 
"TNonblockingSSLServerTest"
FAIL: TNonblockingSSLServerTest

3 of 21 tests failed

make[7]: *** [Makefile:1467: check-TESTS] Error 1
--- End Message ---
--- Begin Message ---
Source: thrift
Source-Version: 0.16.0-5
Done: Laszlo Boszormenyi (GCS) 

We believe that the bug you reported is fixed in the latest version of
thrift, 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.
Laszlo Boszormenyi (GCS)  (supplier of updated thrift package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 15 May 2022 14:42:11 +0200
Source: thrift
Architecture: source
Version: 0.16.0-5
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 1011011
Changes:
 thrift (0.16.0-5) unstable; urgency=medium
 .
   * Disable IPv4 tests for not working on IPv6 only hosts (closes: #1011011).
Checksums-Sha1:
 c3b094c13ac41e375986243bcbc8b362e99587da 2910 thrift_0.16.0-5.dsc
 dca151f40ce3245593d53c6904b401785fef3f78 15988 thrift_0.16.0-5.debian.tar.xz
Checksums-Sha256:
 a5155404b8a587dee478db5630d6670bf7bb9e2099708a1c448bfde5ce51bc20 2910 
thrift_0.16.0-5.dsc
 33495071a70270b92f711c76bd6ea268919acd4024d6d7c50f5bd50154d97fa2 15988 
thrift_0.16.0-5.debian.tar.xz
Files:
 d097c7384d854a9b6e5488ef073ad1f8 

Processed: Re: jquery-at.js: replace node-gulp-util build dependency with node-fancy-log

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1010904 [jquery-at.js] jquery-at.js: replace node-gulp-util build 
dependency with node-fancy-log
Severity set to 'serious' from 'important'

-- 
1010904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010904
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1011019: marked as done (telegram-desktop FTBFS with libkf5wayland-dev 5.93.0)

[Debian Bug Tracking System]

Your message dated Sun, 15 May 2022 16:34:23 +
with message-id 
and subject line Bug#1011019: fixed in telegram-desktop 3.7.3+ds-2
has caused the Debian Bug report #1011019,
regarding telegram-desktop FTBFS with libkf5wayland-dev 5.93.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.)


-- 
1011019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libkf5wayland-dev
Version: 4:5.93.0-1
Severity: serious
Tags: ftbfs
Control: affects -1 src:peony src:telegram-desktop

https://buildd.debian.org/status/logs.php?pkg=peony=3.2.4-2%2Bb1

...
In file included from main.cpp:24:
waylandoutputmanager.h:28:10: fatal error: KWayland/Client/xdgoutput.h: No such 
file or directory
   28 | #include 
  |  ^
...


https://buildd.debian.org/status/logs.php?pkg=telegram-desktop=3.7.3%2Bds-1%2Bb1

...
/<>/Telegram/lib_base/base/platform/linux/base_linux_wayland_integration.cpp:16:10:
 fatal error: connection_thread.h: No such file or directory
   16 | #include 
  |  ^
compilation terminated.
make[3]: *** [Telegram/lib_base/CMakeFiles/lib_base.dir/build.make:224: 
Telegram/lib_base/CMakeFiles/lib_base.dir/base/platform/linux/base_linux_wayland_integration.cpp.o]
 Error 1



Both issues can be "fixed" by downgrading libkf5wayland-dev to 4:5.90.0-1
--- End Message ---
--- Begin Message ---
Source: telegram-desktop
Source-Version: 3.7.3+ds-2
Done: Nicholas Guriev 

We believe that the bug you reported is fixed in the latest version of
telegram-desktop, 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.
Nicholas Guriev  (supplier of updated telegram-desktop package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 15 May 2022 19:04:08 +0300
Source: telegram-desktop
Architecture: source
Version: 3.7.3+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Nicholas Guriev 
Changed-By: Nicholas Guriev 
Closes: 1011019
Changes:
 telegram-desktop (3.7.3+ds-2) unstable; urgency=medium
 .
   * New Include-KWayland.patch fixes build against the updated dependency.
 (Closes: #1011019)
Checksums-Sha1:
 5776883871a482c7f5771c02106d440d97b636c0 2567 telegram-desktop_3.7.3+ds-2.dsc
 a42b33d796c3ce811d76b5d172b3fd8fe6ddfa87 28200 
telegram-desktop_3.7.3+ds-2.debian.tar.xz
Checksums-Sha256:
 4510d1b14e7d73dbf5b22ab8ae27ec160e4b6fc285aba0d60d4125005bb98b43 2567 
telegram-desktop_3.7.3+ds-2.dsc
 e9497e85b8c703292648160be42fee51c2f40e07109eb69719ba4e6d06fddbe4 28200 
telegram-desktop_3.7.3+ds-2.debian.tar.xz
Files:
 497b4a07b838f1f78c40d64e7fb5fd08 2567 net optional 
telegram-desktop_3.7.3+ds-2.dsc
 f3b2c01010a9f74efd5013c4d60874d6 28200 net optional 
telegram-desktop_3.7.3+ds-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iIYEARYIAC4WIQQRm7llN8yxifaG60cF2qh9JI3wlQUCYoEn0BAcZ3VyaWV2LW5z
QHlhLnJ1AAoJEAXaqH0kjfCVAg4A/3cZ2zwtOyKGT86nfAmBF790ZroJmndMcH9J
DhLYTDTpAPwJmoUj32JlfBndfzUnNhoa95eGY0mHldpNfpVQLUM0Dw==
=ZnVw
-END PGP SIGNATURE End Message ---

Bug#1011025: golang-github-containerd-stargz-snapshotter FTBFS: cannot find package "github.com/ipfs/go-cid"

[Adrian Bunk]

Source: golang-github-containerd-stargz-snapshotter
Version: 0.11.4-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=golang-github-containerd-stargz-snapshotter=0.11.4-1

...
   dh_auto_build -a -O--builddirectory=_build -O--buildsystem=golang
cd _build && go install -trimpath -v -p 4 
github.com/containerd/stargz-snapshotter/analyzer 
github.com/containerd/stargz-snapshotter/analyzer/fanotify 
github.com/containerd/stargz-snapshotter/analyzer/fanotify/conn 
github.com/containerd/stargz-snapshotter/analyzer/fanotify/service 
github.com/containerd/stargz-snapshotter/analyzer/recorder 
github.com/containerd/stargz-snapshotter/cache 
github.com/containerd/stargz-snapshotter/cmd/ctr-remote 
github.com/containerd/stargz-snapshotter/cmd/ctr-remote/commands 
github.com/containerd/stargz-snapshotter/estargz 
github.com/containerd/stargz-snapshotter/estargz/errorutil 
github.com/containerd/stargz-snapshotter/estargz/zstdchunked 
github.com/containerd/stargz-snapshotter/fs 
github.com/containerd/stargz-snapshotter/fs/config 
github.com/containerd/stargz-snapshotter/fs/layer 
github.com/containerd/stargz-snapshotter/fs/metrics/common 
github.com/containerd/stargz-snapshotter/fs/metrics/layer 
github.com/containerd/stargz-snapshotter/fs/reader 
github.com/containerd/stargz-snapshotter/fs/remote 
github.com/containerd/stargz-snapshotter/fs/source 
github.com/containerd/stargz-snapshotter/ipfs 
github.com/containerd/stargz-snapshotter/metadata 
github.com/containerd/stargz-snapshotter/metadata/memory 
github.com/containerd/stargz-snapshotter/nativeconverter 
github.com/containerd/stargz-snapshotter/nativeconverter/estargz 
github.com/containerd/stargz-snapshotter/nativeconverter/zstdchunked 
github.com/containerd/stargz-snapshotter/recorder 
github.com/containerd/stargz-snapshotter/script/benchmark/hello-bench/src/go 
github.com/containerd/stargz-snapshotter/snapshot 
github.com/containerd/stargz-snapshotter/snapshot/overlayutils 
github.com/containerd/stargz-snapshotter/store 
github.com/containerd/stargz-snapshotter/task 
github.com/containerd/stargz-snapshotter/util/cacheutil 
github.com/containerd/stargz-snapshotter/util/containerdutil 
github.com/containerd/stargz-snapshotter/util/ioutils 
github.com/containerd/stargz-snapshotter/util/namedmutex 
github.com/containerd/stargz-snapshotter/util/testutil 
github.com/containerd/stargz-snapshotter/version
src/github.com/containerd/stargz-snapshotter/ipfs/converter.go:29:2: cannot 
find package "github.com/ipfs/go-cid" in any of:
/usr/lib/go-1.18/src/github.com/ipfs/go-cid (from $GOROOT)
/<>/_build/src/github.com/ipfs/go-cid (from $GOPATH)
src/github.com/containerd/stargz-snapshotter/ipfs/converter.go:30:2: cannot 
find package "github.com/ipfs/go-ipfs-files" in any of:
/usr/lib/go-1.18/src/github.com/ipfs/go-ipfs-files (from $GOROOT)
/<>/_build/src/github.com/ipfs/go-ipfs-files (from $GOPATH)
src/github.com/containerd/stargz-snapshotter/cmd/ctr-remote/commands/ipfs-push.go:28:2:
 cannot find package "github.com/ipfs/go-ipfs-http-client" in any of:
/usr/lib/go-1.18/src/github.com/ipfs/go-ipfs-http-client (from $GOROOT)
/<>/_build/src/github.com/ipfs/go-ipfs-http-client (from 
$GOPATH)
src/github.com/containerd/stargz-snapshotter/ipfs/converter.go:31:2: cannot 
find package "github.com/ipfs/interface-go-ipfs-core" in any of:
/usr/lib/go-1.18/src/github.com/ipfs/interface-go-ipfs-core (from 
$GOROOT)
/<>/_build/src/github.com/ipfs/interface-go-ipfs-core 
(from $GOPATH)
src/github.com/containerd/stargz-snapshotter/ipfs/converter.go:32:2: cannot 
find package "github.com/ipfs/interface-go-ipfs-core/options" in any of:
/usr/lib/go-1.18/src/github.com/ipfs/interface-go-ipfs-core/options 
(from $GOROOT)

/<>/_build/src/github.com/ipfs/interface-go-ipfs-core/options 
(from $GOPATH)
src/github.com/containerd/stargz-snapshotter/ipfs/converter.go:33:2: cannot 
find package "github.com/ipfs/interface-go-ipfs-core/path" in any of:
/usr/lib/go-1.18/src/github.com/ipfs/interface-go-ipfs-core/path (from 
$GOROOT)
/<>/_build/src/github.com/ipfs/interface-go-ipfs-core/path 
(from $GOPATH)
dh_auto_build: error: cd _build && go install -trimpath -v -p 4 
github.com/containerd/stargz-snapshotter/analyzer 
github.com/containerd/stargz-snapshotter/analyzer/fanotify 
github.com/containerd/stargz-snapshotter/analyzer/fanotify/conn 
github.com/containerd/stargz-snapshotter/analyzer/fanotify/service 
github.com/containerd/stargz-snapshotter/analyzer/recorder 
github.com/containerd/stargz-snapshotter/cache 
github.com/containerd/stargz-snapshotter/cmd/ctr-remote 
github.com/containerd/stargz-snapshotter/cmd/ctr-remote/commands 
github.com/containerd/stargz-snapshotter/estargz 
github.com/containerd/stargz-snapshotter/estargz/errorutil 
github.com/containerd/stargz-snapshotter/estargz/zstdchunked 
github.com/containerd/stargz-snapshotter/fs 

Processed: unblock 1010813 with 1010838

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # src:gtk4 now works around this
> unblock 1010813 with 1010838
Bug #1010813 [src:mutter] mutter: Let gtk4 4.6.3+ds1-2 migrate to testing first
1010813 was blocked by: 1010838
1010813 was not blocking any bugs.
Removed blocking bug(s) of 1010813: 1010838
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1010813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1006574: marked as done (sendmail: FTBFS with OpenSSL 3.0)

[Debian Bug Tracking System]

Your message dated Sun, 15 May 2022 14:58:55 +
with message-id 
and subject line Bug#1006574: fixed in sendmail 8.17.1-2
has caused the Debian Bug report #1006574,
regarding sendmail: 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.)


-- 
1006574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sendmail
Version: 8.16.1-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 with the
following error:

| gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -fPIC -I. -I../../include   
-I/usr/include/tirpc  -DSOCKETMAP -DMAP_REGEX -DNEWDB -DNIS -DNISPLUS -DLDAPMAP 
 -DHASFCHMOD=1 -DHASSETRLIMIT=1 -DHASFLOCK=0 -DUSESETEUID=1 -DHASGETUSERSHELL=1 
-DHAS_GETHOSTBYNAME2=1 -DNETINET6  
-D_PATH_SENDMAILPID=\"/var/run/sendmail/mta/sendmail.pid\" -DIP_SRCROUTE=1 
-DMILTER -DLDAP_REFERRALS -DLDAP_DEPRECATED  -DTCPWRAPPERS -DSASL 
-I/usr/include/sasl -DSTARTTLS  -D_FFR_QUEUE_SCHED_DBG -D_FFR_SKIP_DOMAINS 
-D_FFR_NO_PIPE -D_FFR_SHM_STATUS -D_FFR_RHS -D_FFR_MAIL_MACRO 
-D_FFR_QUEUEDELAY=1 -D_FFR_BADRCPT_SHUTDOWN -D_FFR_RESET_MACRO_GLOBALS 
-D_FFR_TLS_EC   -Wdate-time -D_FORTIFY_SOURCE=2  -c -o tls.o tls.c
| tls.c: In function ‘get_dh512’:
| tls.c:87:9: warning: ‘DH_new’ is deprecated: Since OpenSSL 3.0 
[-Wdeprecated-declarations]
|87 | if ((dh = DH_new()) == NULL)
|   | ^~
| In file included from /usr/include/openssl/dsa.h:51,
|  from /usr/include/openssl/x509.h:37,
|  from /usr/include/openssl/ssl.h:31,
|  from ./sendmail.h:46,
|  from tls.c:11:
| /usr/include/openssl/dh.h:199:27: note: declared here
|   199 | OSSL_DEPRECATEDIN_3_0 DH *DH_new(void);
|   |   ^~
| tls.c:99:11: error: invalid use of incomplete typedef ‘DH’ {aka ‘struct 
dh_st’}
|99 | dh->p = BN_bin2bn(dh512_p, sizeof(dh512_p), NULL);
|   |   ^~
| tls.c:100:11: error: invalid use of incomplete typedef ‘DH’ {aka 
‘struct dh_st’}
|   100 | dh->g = BN_bin2bn(dh512_g, sizeof(dh512_g), NULL);
|   |   ^~
| tls.c:101:16: error: invalid use of incomplete typedef ‘DH’ {aka 
‘struct dh_st’}
|   101 | if ((dh->p == NULL) || (dh->g == NULL))
|   |^~
| tls.c:101:35: error: invalid use of incomplete typedef ‘DH’ {aka 
‘struct dh_st’}
|   101 | if ((dh->p == NULL) || (dh->g == NULL))
|   |   ^~
| tls.c:103:17: warning: ‘DH_free’ is deprecated: Since OpenSSL 3.0 
[-Wdeprecated-declarations]
|   103 | DH_free(dh);
|   | ^~~
| In file included from /usr/include/openssl/dsa.h:51,
|  from /usr/include/openssl/x509.h:37,
|  from /usr/include/openssl/ssl.h:31,
|  from ./sendmail.h:46,
|  from tls.c:11:
| /usr/include/openssl/dh.h:200:28: note: declared here
|   200 | OSSL_DEPRECATEDIN_3_0 void DH_free(DH *dh);
|   |^~~
| tls.c: In function ‘get_dh2048’:
| tls.c:157:9: warning: ‘DH_new’ is deprecated: Since OpenSSL 3.0 
[-Wdeprecated-declarations]
|   157 | if ((dh=DH_new()) == NULL)
|   | ^~
| In file included from /usr/include/openssl/dsa.h:51,
|  from /usr/include/openssl/x509.h:37,
|  from /usr/include/openssl/ssl.h:31,
|  from ./sendmail.h:46,
|  from tls.c:11:
| /usr/include/openssl/dh.h:199:27: note: declared here
|   199 | OSSL_DEPRECATEDIN_3_0 DH *DH_new(void);
|   |   ^~
| tls.c:169:11: error: invalid use of incomplete typedef ‘DH’ {aka 
‘struct dh_st’}
|   169 | dh->p=BN_bin2bn(dh2048_p,sizeof(dh2048_p),NULL);
|   |   ^~
| tls.c:170:11: error: invalid use of incomplete typedef ‘DH’ {aka 
‘struct dh_st’}
|   170 | dh->g=BN_bin2bn(dh2048_g,sizeof(dh2048_g),NULL);
|   |   ^~
| tls.c:171:16: error: invalid use of incomplete typedef ‘DH’ {aka 
‘struct dh_st’}
|   171 | if ((dh->p == NULL) || (dh->g == NULL))
|   |^~
| tls.c:171:35: error: invalid use of incomplete typedef ‘DH’ {aka 
‘struct dh_st’}
|   171 | if ((dh->p == NULL) || (dh->g == NULL))
|   |  

Processed: Re: Bug#1011015: libkf5wayland-dev 4:5.93.0-1 breaks the include search of reverse dependencies

[Debian Bug Tracking System]

Processing control commands:

> retitle 1011019 telegram-desktop FTBFS with libkf5wayland-dev 5.93.0
Bug #1011019 [src:telegram-desktop] libkf5wayland-dev 4:5.93.0-1 breaks the 
include search of reverse dependencies
Changed Bug title to 'telegram-desktop FTBFS with libkf5wayland-dev 5.93.0' 
from 'libkf5wayland-dev 4:5.93.0-1 breaks the include search of reverse 
dependencies'.

-- 
1011015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011015
1011019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1011015: libkf5wayland-dev 4:5.93.0-1 breaks the include search of reverse dependencies

[Adrian Bunk]

Control: retitle 1011019 telegram-desktop FTBFS with libkf5wayland-dev 5.93.0

On Sun, May 15, 2022 at 03:07:13PM +0300, Nicholas Guriev wrote:
> Control: clone -1 -2
> Control: reassign -2 src:telegram-desktop 3.7.3+ds-1
> 
> 
> Hello!
> 
> On Sun, 15 May 2022 14:27:01 +0300 Adrian Bunk  wrote:
> > https://buildd.debian.org/status/logs.php?pkg=telegram-desktop=3.7.3%2Bds-1%2Bb1
> > 
> > ...
> > /<>/Telegram/lib_base/base/platform/linux/base_linux_wayland_integration.cpp:16:10:
> >  fatal error: connection_thread.h: No such file or directory
> >    16 | #include 
> >   |  ^
> > compilation terminated.
> > make[3]: *** [Telegram/lib_base/CMakeFiles/lib_base.dir/build.make:224: 
> > Telegram/lib_base/CMakeFiles/lib_base.dir/base/platform/linux/base_linux_wayland_integration.cpp.o]
> >  Error 1
> > 
> > 
> > 
> > Both issues can be "fixed" by downgrading libkf5wayland-dev to 4:5.90.0-1
> 
> I do not believe this is a KWayland issue. Short paths were
> intentionally removed from there.
> https://invent.kde.org/frameworks/kwayland/-/commit/de442e4a94e249a29cf2e005db8e0a5e4a6a13ed
> 
> As for Telegram Desktop I could provide a patch including the
>  header.

OK, then there seem to be two different issues:

https://tracker.debian.org/news/1325100/accepted-kwayland-45930-2-source-into-unstable/
fixed peony

telegram-desktop still needs fixing.

cu
Adrian

Bug#1011012: marked as done (tiledb-r FTBFS with tiledb 2.8.3)

[Debian Bug Tracking System]

Your message dated Sun, 15 May 2022 13:52:56 +
with message-id 
and subject line Bug#1011012: fixed in tiledb-r 0.12.0-2
has caused the Debian Bug report #1011012,
regarding tiledb-r FTBFS with tiledb 2.8.3
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.)


-- 
1011012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011012
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tiledb-r
Version: 0.12.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=tiledb-r=0.12.0-1%2Bb1

...
g++ -std=gnu++17 -I"/usr/share/R/include" -DNDEBUG -I../inst/include/ 
-I/usr/include/tiledb -I'/usr/lib/R/site-library/Rcpp/include'-fpic  -g -O2 
-ffile-prefix-map=/build/r-base-eH67wr/r-base-4.2.0=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c 
libtiledb.cpp -o libtiledb.o
libtiledb.cpp: In function ‘Rcpp::XPtr 
libtiledb_group(Rcpp::XPtr, const string&, const string&)’:
libtiledb.cpp:4401:47: error: no matching function for call to 
‘tiledb::Group::Group()’
 4401 | XPtr ptr(new tiledb::Group()); // placeholder
  |   ^
In file included from /usr/include/tiledb/tiledb_experimental:37,
 from ../inst/include/tiledb.h:7,
 from libtiledb.h:27,
 from libtiledb.cpp:23:
/usr/include/tiledb/group_experimental.h:73:3: note: candidate: 
‘tiledb::Group::Group(tiledb::Group&&)’
   73 |   Group(Group&&) = default;
  |   ^
/usr/include/tiledb/group_experimental.h:73:3: note:   candidate expects 1 
argument, 0 provided
/usr/include/tiledb/group_experimental.h:72:3: note: candidate: 
‘tiledb::Group::Group(const tiledb::Group&)’
   72 |   Group(const Group&) = default;
  |   ^
/usr/include/tiledb/group_experimental.h:72:3: note:   candidate expects 1 
argument, 0 provided
/usr/include/tiledb/group_experimental.h:60:3: note: candidate: 
‘tiledb::Group::Group(const tiledb::Context&, const string&, 
tiledb_query_type_t)’
   60 |   Group(
  |   ^
/usr/include/tiledb/group_experimental.h:60:3: note:   candidate expects 3 
arguments, 0 provided
make[2]: *** [/usr/lib/R/etc/Makeconf:177: libtiledb.o] Error 1
--- End Message ---
--- Begin Message ---
Source: tiledb-r
Source-Version: 0.12.0-2
Done: Dirk Eddelbuettel 

We believe that the bug you reported is fixed in the latest version of
tiledb-r, 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.
Dirk Eddelbuettel  (supplier of updated tiledb-r package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 15 May 2022 08:18:54 -0500
Source: tiledb-r
Architecture: source
Version: 0.12.0-2
Distribution: unstable
Urgency: medium
Maintainer: Dirk Eddelbuettel 
Changed-By: Dirk Eddelbuettel 
Closes: 1011012
Changes:
 tiledb-r (0.12.0-2) unstable; urgency=medium
 .
   * debian/patches/: Relax constraints for '>= 2.8.0 && < 2.9.0' which was
 needed briefly upstream and is now a blocker (Closes: #1011012)
Checksums-Sha1:
 b67e39e074c7a5bbef493c36a2d2223ff39fc8af 1885 tiledb-r_0.12.0-2.dsc
 68f647652aa683f71fda1d1732c9506e354e59b3 4776 tiledb-r_0.12.0-2.debian.tar.xz
 82f4c88f8ef845426d6eddd574c1cb4526f4f468 10989 
tiledb-r_0.12.0-2_amd64.buildinfo
Checksums-Sha256:
 05c6515ea2b30b5a097caa0fe0bd31b054f1b20ace1667d3782b3629eaf09594 1885 
tiledb-r_0.12.0-2.dsc
 617c46bafc703f1647e0814c79c7cbf256c095c51848efb924e01f31d75078f1 4776 
tiledb-r_0.12.0-2.debian.tar.xz
 72b5cb35dd327a0b6008398f8389cca2ac40b7cb79f90296027f7c4a98e1ec5c 10989 
tiledb-r_0.12.0-2_amd64.buildinfo
Files:
 087cf41a24868b7350284b0c055fd939 1885 gnu-r optional tiledb-r_0.12.0-2.dsc
 911252a41258e0bce0c8d29cfcdb69ce 4776 gnu-r optional 
tiledb-r_0.12.0-2.debian.tar.xz
 f4b0bffc9d0e3ffcefd85ec69835de62 10989 gnu-r optional 
tiledb-r_0.12.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIVAwUBYoD+TKFIn+KrmaIaAQhLGRAAreaZVvImYzY0PhJJVI54baK1vE6qZozG
kisKw9UqgLYfGTEiDvvhb1dhjm9E/Eo6aoQfrR1Q7cx8Qp/cdc2E3Cmy73qWvInr
78kMAVwd3CT3XGmUkSvH6UZDX8xPbqdimLhqupTmkXkSzgPSfaqODgsnoZkP9Jyn

Processed: bug 1011019 is not forwarded, tagging 1011019

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notforwarded 1011019
Bug #1011019 [src:telegram-desktop] libkf5wayland-dev 4:5.93.0-1 breaks the 
include search of reverse dependencies
Unset Bug forwarded-to-address
> tags 1011019 = ftbfs
Bug #1011019 [src:telegram-desktop] libkf5wayland-dev 4:5.93.0-1 breaks the 
include search of reverse dependencies
Removed tag(s) upstream, fixed-upstream, and pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1011019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: affects 1011019

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 1011019 =
Bug #1011019 [src:telegram-desktop] libkf5wayland-dev 4:5.93.0-1 breaks the 
include search of reverse dependencies
Removed indication that 1011019 affects src:telegram-desktop and src:peony
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1011019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1006519: marked as done (openvpn: FTBFS with OpenSSL 3.0)

[Debian Bug Tracking System]

Your message dated Sun, 15 May 2022 16:02:48 +0300
with message-id <20220515130248.GA27942@localhost>
and subject line Already fixed in 2.6.0~git20220510+dco-1 in experimental
has caused the Debian Bug report #1006519,
regarding openvpn: 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.)


-- 
1006519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openvpn
Version: 2.5.5-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
control: forwarded -1

Your package is failing to build using OpenSSL 3.0 with the
following error:

| Testing cipher CHACHA20-POLY1305... OK
| Testing cipher SEED-CBC... FAILED
| 2022-02-26 17:17:22 Cipher negotiation is disabled since neither P2MP client 
nor server mode is enabled
| 2022-02-26 17:17:22 OpenVPN 2.5.5 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] 
[LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 21 2022
| 2022-02-26 17:17:22 library versions: OpenSSL 3.0.1 14 Dec 2021, LZO 2.10
| 2022-02-26 17:17:22 OpenVPN 2.5.5 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] 
[LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 21 2022
| 2022-02-26 17:17:22 OpenSSL: error:0308010C:digital envelope 
routines::unsupported
| 2022-02-26 17:17:22 EVP cipher init #1
| 2022-02-26 17:17:22 Exiting due to fatal error
| Testing cipher SEED-CFB... FAILED
| 2022-02-26 17:17:22 Cipher negotiation is disabled since neither P2MP client 
nor server mode is enabled
| 2022-02-26 17:17:22 OpenVPN 2.5.5 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] 
[LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 21 2022
| 2022-02-26 17:17:22 library versions: OpenSSL 3.0.1 14 Dec 2021, LZO 2.10
| 2022-02-26 17:17:22 OpenVPN 2.5.5 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] 
[LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 21 2022
| 2022-02-26 17:17:22 OpenSSL: error:0308010C:digital envelope 
routines::unsupported
| 2022-02-26 17:17:22 EVP cipher init #1
| 2022-02-26 17:17:22 Exiting due to fatal error
| Testing cipher SEED-OFB... FAILED
| 2022-02-26 17:17:22 Cipher negotiation is disabled since neither P2MP client 
nor server mode is enabled
| 2022-02-26 17:17:22 OpenVPN 2.5.5 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] 
[LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 21 2022
| 2022-02-26 17:17:22 library versions: OpenSSL 3.0.1 14 Dec 2021, LZO 2.10
| 2022-02-26 17:17:22 OpenVPN 2.5.5 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] 
[LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 21 2022
| 2022-02-26 17:17:22 OpenSSL: error:0308010C:digital envelope 
routines::unsupported
| 2022-02-26 17:17:22 EVP cipher init #1
| 2022-02-26 17:17:22 Exiting due to fatal error
|Testing cipher SM4-CBC... OK
| Testing cipher SM4-CFB... OK
| Testing cipher SM4-OFB... OK
| Testing cipher BF-CBC... FAILED
| 2022-02-26 17:17:22 Cipher negotiation is disabled since neither P2MP client 
nor server mode is enabled
| 2022-02-26 17:17:22 OpenVPN 2.5.5 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] 
[LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 21 2022
| 2022-02-26 17:17:22 library versions: OpenSSL 3.0.1 14 Dec 2021, LZO 2.10
| 2022-02-26 17:17:22 OpenVPN 2.5.5 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] 
[LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 21 2022
| 2022-02-26 17:17:22 WARNING: INSECURE cipher (BF-CBC) with block size less 
than 128 bit (64 bit).  This allows attacks like SWEET32.  Mitiga te by using a 
--cipher with a larger block size (e.g. AES-256-CBC). Support for these 
insecure ciphers will be removed in OpenVPN 2.7.
| 2022-02-26 17:17:22 OpenSSL: error:0308010C:digital envelope 
routines::unsupported
| 2022-02-26 17:17:22 EVP cipher init #1
| 2022-02-26 17:17:22 Exiting due to fatal error
| Testing cipher BF-CFB... FAILED
| 2022-02-26 17:17:22 Cipher negotiation is disabled since neither P2MP client 
nor server mode is enabled
| 2022-02-26 17:17:22 OpenVPN 2.5.5 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] 
[LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 21 2022
| 2022-02-26 17:17:22 library versions: OpenSSL 3.0.1 14 Dec 2021, LZO 2.10
| 2022-02-26 17:17:22 OpenVPN 2.5.5 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] 
[LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 21 2022
| 2022-02-26 17:17:22 WARNING: INSECURE cipher (BF-CFB) with block size less 
than 128 bit (64 bit).  This allows attacks like SWEET32.  Mitiga te by using a 
--cipher with a larger block size (e.g. AES-256-CBC). Support for these 
insecure ciphers will be removed 

Bug#1011012: tiledb-r FTBFS with tiledb 2.8.3

[Dirk Eddelbuettel]

Adrian,

On 15 May 2022 at 13:38, Adrian Bunk wrote:
| Source: tiledb-r
| Version: 0.12.0-1
| Severity: serious
| Tags: ftbfs
| 
| https://buildd.debian.org/status/logs.php?pkg=tiledb-r=0.12.0-1%2Bb1
| 
| ...
| g++ -std=gnu++17 -I"/usr/share/R/include" -DNDEBUG -I../inst/include/ 
-I/usr/include/tiledb -I'/usr/lib/R/site-library/Rcpp/include'-fpic  -g -O2 
-ffile-prefix-map=/build/r-base-eH67wr/r-base-4.2.0=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c 
libtiledb.cpp -o libtiledb.o
| libtiledb.cpp: In function ‘Rcpp::XPtr 
libtiledb_group(Rcpp::XPtr, const string&, const string&)’:
| libtiledb.cpp:4401:47: error: no matching function for call to 
‘tiledb::Group::Group()’
|  4401 | XPtr ptr(new tiledb::Group()); // placeholder
|   |   ^
| In file included from /usr/include/tiledb/tiledb_experimental:37,
|  from ../inst/include/tiledb.h:7,
|  from libtiledb.h:27,
|  from libtiledb.cpp:23:
| /usr/include/tiledb/group_experimental.h:73:3: note: candidate: 
‘tiledb::Group::Group(tiledb::Group&&)’
|73 |   Group(Group&&) = default;
|   |   ^
| /usr/include/tiledb/group_experimental.h:73:3: note:   candidate expects 1 
argument, 0 provided
| /usr/include/tiledb/group_experimental.h:72:3: note: candidate: 
‘tiledb::Group::Group(const tiledb::Group&)’
|72 |   Group(const Group&) = default;
|   |   ^
| /usr/include/tiledb/group_experimental.h:72:3: note:   candidate expects 1 
argument, 0 provided
| /usr/include/tiledb/group_experimental.h:60:3: note: candidate: 
‘tiledb::Group::Group(const tiledb::Context&, const string&, 
tiledb_query_type_t)’
|60 |   Group(
|   |   ^
| /usr/include/tiledb/group_experimental.h:60:3: note:   candidate expects 3 
arguments, 0 provided
| make[2]: *** [/usr/lib/R/etc/Makeconf:177: libtiledb.o] Error 1

I know -- it also happend a few days to CRAN which uses Debian testing on one 
box.

This is temporary. I work at TileDB, and we had a lot of upstream work going
on with the 'dev', 2.7 and 2.8 branches that made me accientally use and
'equal to 2.8.0' test where 'equal or greater to 2.8.0' would have avoided
this.

We just release 2.9.0 so this is a little moot anyway but I think I will just
do a quick fix while working on some CMake changes I need to make for the
2.9.0 package.

Dirk


-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1011015: marked as done (libkf5wayland-dev 4:5.93.0-1 breaks the include search of reverse dependencies)

[Debian Bug Tracking System]

Your message dated Sun, 15 May 2022 12:34:19 +
with message-id 
and subject line Bug#1011015: fixed in kwayland 4:5.93.0-2
has caused the Debian Bug report #1011015,
regarding libkf5wayland-dev 4:5.93.0-1 breaks the include search of reverse 
dependencies
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.)


-- 
1011015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libkf5wayland-dev
Version: 4:5.93.0-1
Severity: serious
Tags: ftbfs
Control: affects -1 src:peony src:telegram-desktop

https://buildd.debian.org/status/logs.php?pkg=peony=3.2.4-2%2Bb1

...
In file included from main.cpp:24:
waylandoutputmanager.h:28:10: fatal error: KWayland/Client/xdgoutput.h: No such 
file or directory
   28 | #include 
  |  ^
...


https://buildd.debian.org/status/logs.php?pkg=telegram-desktop=3.7.3%2Bds-1%2Bb1

...
/<>/Telegram/lib_base/base/platform/linux/base_linux_wayland_integration.cpp:16:10:
 fatal error: connection_thread.h: No such file or directory
   16 | #include 
  |  ^
compilation terminated.
make[3]: *** [Telegram/lib_base/CMakeFiles/lib_base.dir/build.make:224: 
Telegram/lib_base/CMakeFiles/lib_base.dir/base/platform/linux/base_linux_wayland_integration.cpp.o]
 Error 1



Both issues can be "fixed" by downgrading libkf5wayland-dev to 4:5.90.0-1
--- End Message ---
--- Begin Message ---
Source: kwayland
Source-Version: 4:5.93.0-2
Done: Pino Toscano 

We believe that the bug you reported is fixed in the latest version of
kwayland, 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.
Pino Toscano  (supplier of updated kwayland package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 15 May 2022 14:12:33 +0200
Source: kwayland
Architecture: source
Version: 4:5.93.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Pino Toscano 
Closes: 1011015
Changes:
 kwayland (4:5.93.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Bump Standards-Version to 4.6.1, no changes required.
   * Modernize building:
 - add the dh-sequence-kf5 build dependency to use the kf5 addon
   automatically
 - drop all the manually specified addons and buildsystem for dh
   * Remove inactive Uploaders.
   * CI: enable again the blhc job.
   * Apply the upstream patches before the Debian ones (reduces potential
 conflicts).
   * Backport upstream commit 70eb1df5a14c668879443a853069af750920035b to fix
 the KWaylandClient include directory in the qmake .pri file; patch
 upstream_Fix-include-dir-in-the-generated-pri-file.patch. (Closes: 
#1011015)
Checksums-Sha1:
 8d1de7d4e28e6f99c722e653b6ccaad3e2dcb835 2967 kwayland_5.93.0-2.dsc
 026ef9e21a99a383920fb80c02da771fada45830 43448 kwayland_5.93.0-2.debian.tar.xz
 42465eb319a597bab25706d27c87d3c7c597f492 13390 
kwayland_5.93.0-2_source.buildinfo
Checksums-Sha256:
 8cc3de50b4b2912aa5bd834b66185f5fbe808df1f8d679587fce7917d5a670e7 2967 
kwayland_5.93.0-2.dsc
 d3653d7b9fb2d809137d725a52f267443f9fff9b8c95e1aa46c46e067965fe27 43448 
kwayland_5.93.0-2.debian.tar.xz
 35ff280f3126d80bc4925546fd48271bce1b7d8b03fad7744fadba3d249367c9 13390 
kwayland_5.93.0-2_source.buildinfo
Files:
 c446cfdb1a9c6f781b277f18641ff221 2967 libs optional kwayland_5.93.0-2.dsc
 1fe58537c333917940a993f1fd552ae2 43448 libs optional 
kwayland_5.93.0-2.debian.tar.xz
 b45a4e8563b427f6f07f638d26606522 13390 libs optional 
kwayland_5.93.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAmKA7l0ACgkQLRkciEOx
P03Kgg/9F0g/EmornsOnhahyzYlrINJ5k4cO2fBbSoQS8bfDgQ1Nl1nLqt7tgV2p
+TxVDCEA/Goi9QOp7Y/rY3ngNXTQ9j4rEAkQwBctqcRnR+5/LRlk3CRUCPdjVzZz
se55f/F+7PBHb1U0tjBku9TCNgPVrvXiC7GBdKAebwXO08PgH8eswIJ20n7L68B6
hC/r3HDzycQXK50B+ps7Dtie/R0W22CI0ErGUeApN1BSnShEVgnkNoiSOxPN19Rp
tWRpn7RjnYGTuXsxw+4o+LlPsD+f3JJVboPG0xRH4kT+Iibu40Qmg3KK7Tw66zoY
gFdvE3RGdsULrNb7ah9kru9c4fHYoiM3jqR2NKzU/1ETxp2PCSagUU1UK4TpEE1m

Processed (with 2 errors): tagging 999720, tagging 999719, tagging 1009417, reassign 1010079 to djtools ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 999720 + experimental
Bug #999720 {Done: Mohammed Bilal } 
[src:ruby-omniauth-oauth] ruby-omniauth-oauth: FTBFS with ruby-omniauth 2.0.x: 
ERROR: Test "ruby2.7" failed: 
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in 
activate_dependencies': Could not find 'omniauth' (~> 1.0) among 78 total 
gem(s) (Gem::MissingSpecError)
Added tag(s) experimental.
> tags 999719 + experimental
Bug #999719 {Done: Mohammed Bilal } 
[src:ruby-omniauth-multipassword] ruby-omniauth-multipassword: FTBFS with 
ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed:  NoMethodError:
Added tag(s) experimental.
> tags 1009417 - sid bookworm
Bug #1009417 {Done: Bas Couwenberg } [src:saga] saga: 
FTBFS: configure: error: cannot import Python module "distutils".
Removed tag(s) sid and bookworm.
> reassign 1010079 djtools 1.2.8
Bug #1010079 [djscript] djscript: Typo in man page hpset(1)
Warning: Unknown package 'djscript'
Bug reassigned from package 'djscript' to 'djtools'.
No longer marked as found in versions 1.2.8.
Ignoring request to alter fixed versions of bug #1010079 to the same values 
previously set
Bug #1010079 [djtools] djscript: Typo in man page hpset(1)
Marked as found in versions djtools/1.2.8.
> reassign 1010078 djtools 1.2.8
Bug #1010078 [djscript] djscript: Typo in man page djscript(1)
Warning: Unknown package 'djscript'
Bug reassigned from package 'djscript' to 'djtools'.
No longer marked as found in versions 1.2.8.
Ignoring request to alter fixed versions of bug #1010078 to the same values 
previously set
Bug #1010078 [djtools] djscript: Typo in man page djscript(1)
Marked as found in versions djtools/1.2.8.
> reassign 699328 src:libav 6:9~beta1-1
Failed to clear fixed versions and reopen on 699328: Bug 699328 mergedwith 
differs from bug 691088: (691088: '') vs. ('699328') (691088 699328).

> fixed 699328 6:9~beta2-1
Failed to add fixed on 699328: Bug 699328 mergedwith differs from bug 691088: 
(691088: '') vs. ('699328') (691088 699328).

> fixed 1006574 8.17.1-1
Bug #1006574 [src:sendmail] sendmail: FTBFS with OpenSSL 3.0
Marked as fixed in versions sendmail/8.17.1-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1006574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006574
1009417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009417
1010078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010078
1010079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010079
999719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999719
999720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[Debian Bug Tracking System]

Your message dated Sun, 15 May 2022 12:20:57 +
with message-id 
and subject line Bug#1009478: fixed in luma.emulator 1.4.0-3
has caused the Debian Bug report #1009478,
regarding luma.emulator: FTBFS: ModuleNotFoundError: No module named 
'luma.emulator'
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.)


-- 
1009478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: luma.emulator
Version: 1.4.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> sphinx-build -b html -d _build/doctrees   . _build/html
> Running Sphinx v4.5.0
> 
> Configuration error:
> There is a programmable error in your configuration file:
> 
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/sphinx/config.py", line 332, in 
> eval_config_file
> exec(code, namespace)
>   File "/<>/doc/conf.py", line 28, in 
> from luma.emulator import __version__ as version
> ModuleNotFoundError: No module named 'luma.emulator'
> 
> make[2]: *** [Makefile:53: html] Error 2


The full build log is available from:
http://qa-logs.debian.net/2022/04/12/luma.emulator_1.4.0-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220412=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: luma.emulator
Source-Version: 1.4.0-3
Done: Anton Gladky 

We believe that the bug you reported is fixed in the latest version of
luma.emulator, 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 1009...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated luma.emulator package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 15 May 2022 13:44:25 +0200
Source: luma.emulator
Architecture: source
Version: 1.4.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Anton Gladky 
Closes: 1009478
Changes:
 luma.emulator (1.4.0-3) unstable; urgency=medium
 .
   * [05b6194] Fix ModuleNotFoundError. (Closes: #1009478)
   * [fae08e9] Apply cme fix dpkg. Set Standards-Version to 4.6.0 (no changes)
   * [20822a4] Replace license name MIT->EXPAT
Checksums-Sha1:
 96601e8fc40d7603c6ff6e90c4beff8118aa5b0d  luma.emulator_1.4.0-3.dsc
 fecc0354061ef131719125e6f2403ea558f6333a 3104 
luma.emulator_1.4.0-3.debian.tar.xz
 3e8be09451da5b5f8df57e3a67359b36e6128819 11855 
luma.emulator_1.4.0-3_source.buildinfo
Checksums-Sha256:
 525e1e08bcf1c2ca67fbddb9326ab68042f06028854674f1a829901e19e4a6f9  
luma.emulator_1.4.0-3.dsc
 8347949c34078994077b6c75bec56d2b2a62c3bfa32146a80c37e638f1ee9110 3104 
luma.emulator_1.4.0-3.debian.tar.xz
 822337a97ed2c0624f23c2fa5210964d470f5293d3607ce7f4d4f8f04ee07b03 11855 
luma.emulator_1.4.0-3_source.buildinfo
Files:
 e310f8302db544a4dfd251e8356f7fbd  libs optional luma.emulator_1.4.0-3.dsc
 782450262d4971ca63159e3837d24081 3104 libs optional 
luma.emulator_1.4.0-3.debian.tar.xz
 38210edc035a97fd879bdd830c25842b 11855 libs optional 
luma.emulator_1.4.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAmKA57cACgkQ0+Fzg8+n
/wZpuA/9FwSvDXK83Ro07DopZb35AyvDggAAjrfnN3XvNoW9hQ0Qbyy8iZYWGSxk
d1xAZ6nKsawIZdntRW6deech8gVjx664I6Ru/J6SiowhsZpTAgnNsjjBO3K6YHrr

Processed: Re: libkf5wayland-dev 4:5.93.0-1 breaks the include search of reverse dependencies

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #1011015 [libkf5wayland-dev] libkf5wayland-dev 4:5.93.0-1 breaks the 
include search of reverse dependencies
Bug 1011015 cloned as bug 1011019
> reassign -2 src:telegram-desktop 3.7.3+ds-1
Bug #1011019 [libkf5wayland-dev] libkf5wayland-dev 4:5.93.0-1 breaks the 
include search of reverse dependencies
Bug reassigned from package 'libkf5wayland-dev' to 'src:telegram-desktop'.
No longer marked as found in versions kwayland/4:5.93.0-1.
Ignoring request to alter fixed versions of bug #1011019 to the same values 
previously set
Bug #1011019 [src:telegram-desktop] libkf5wayland-dev 4:5.93.0-1 breaks the 
include search of reverse dependencies
Marked as found in versions telegram-desktop/3.7.3+ds-1.

-- 
1011015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011015
1011019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1011015: libkf5wayland-dev 4:5.93.0-1 breaks the include search of reverse dependencies

[Nicholas Guriev]

Control: clone -1 -2
Control: reassign -2 src:telegram-desktop 3.7.3+ds-1


Hello!

On Sun, 15 May 2022 14:27:01 +0300 Adrian Bunk  wrote:
> https://buildd.debian.org/status/logs.php?pkg=telegram-desktop=3.7.3%2Bds-1%2Bb1
> 
> ...
> /<>/Telegram/lib_base/base/platform/linux/base_linux_wayland_integration.cpp:16:10:
>  fatal error: connection_thread.h: No such file or directory
>    16 | #include 
>   |  ^
> compilation terminated.
> make[3]: *** [Telegram/lib_base/CMakeFiles/lib_base.dir/build.make:224: 
> Telegram/lib_base/CMakeFiles/lib_base.dir/base/platform/linux/base_linux_wayland_integration.cpp.o]
>  Error 1
> 
> 
> 
> Both issues can be "fixed" by downgrading libkf5wayland-dev to 4:5.90.0-1

I do not believe this is a KWayland issue. Short paths were
intentionally removed from there.
https://invent.kde.org/frameworks/kwayland/-/commit/de442e4a94e249a29cf2e005db8e0a5e4a6a13ed

As for Telegram Desktop I could provide a patch including the
 header.



signature.asc
Description: This is a digitally signed message part

Processed: bug 1011015 is forwarded to https://invent.kde.org/frameworks/kwayland/-/merge_requests/62 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1011015 
> https://invent.kde.org/frameworks/kwayland/-/merge_requests/62
Bug #1011015 [libkf5wayland-dev] libkf5wayland-dev 4:5.93.0-1 breaks the 
include search of reverse dependencies
Set Bug forwarded-to-address to 
'https://invent.kde.org/frameworks/kwayland/-/merge_requests/62'.
> tags 1011015 + upstream fixed-upstream pending
Bug #1011015 [libkf5wayland-dev] libkf5wayland-dev 4:5.93.0-1 breaks the 
include search of reverse dependencies
Added tag(s) pending, fixed-upstream, and upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1011015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1011015: libkf5wayland-dev 4:5.93.0-1 breaks the include search of reverse dependencies

[Adrian Bunk]

Package: libkf5wayland-dev
Version: 4:5.93.0-1
Severity: serious
Tags: ftbfs
Control: affects -1 src:peony src:telegram-desktop

https://buildd.debian.org/status/logs.php?pkg=peony=3.2.4-2%2Bb1

...
In file included from main.cpp:24:
waylandoutputmanager.h:28:10: fatal error: KWayland/Client/xdgoutput.h: No such 
file or directory
   28 | #include 
  |  ^
...


https://buildd.debian.org/status/logs.php?pkg=telegram-desktop=3.7.3%2Bds-1%2Bb1

...
/<>/Telegram/lib_base/base/platform/linux/base_linux_wayland_integration.cpp:16:10:
 fatal error: connection_thread.h: No such file or directory
   16 | #include 
  |  ^
compilation terminated.
make[3]: *** [Telegram/lib_base/CMakeFiles/lib_base.dir/build.make:224: 
Telegram/lib_base/CMakeFiles/lib_base.dir/base/platform/linux/base_linux_wayland_integration.cpp.o]
 Error 1



Both issues can be "fixed" by downgrading libkf5wayland-dev to 4:5.90.0-1

Processed: libkf5wayland-dev 4:5.93.0-1 breaks the include search of reverse dependencies

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:peony src:telegram-desktop
Bug #1011015 [libkf5wayland-dev] libkf5wayland-dev 4:5.93.0-1 breaks the 
include search of reverse dependencies
Added indication that 1011015 affects src:peony and src:telegram-desktop

-- 
1011015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1009939: marked as done (sip6: AttributeError: 'YaccProduction' object has no attribute 'parser_manager')

[Debian Bug Tracking System]

Your message dated Sun, 15 May 2022 11:22:57 +
with message-id 
and subject line Bug#1009939: fixed in sip6 6.6.1+dfsg-2
has caused the Debian Bug report #1009939,
regarding sip6: AttributeError: 'YaccProduction' object has no attribute 
'parser_manager'
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.)


-- 
1009939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sip6
Version: 6.6.1+dfsg-1
Severity: serious
Control: affects -1 src:qgis

Dear Maintainer,

Since the upgrade to 6.6.1+dfsg-1 qgis FTBFS:

 FAILED: python/analysis/build/_analysis/sip_analysispart0.cpp 
python/analysis/build/_analysis/sip_analysispart1.cpp 
python/analysis/build/_analysis/sip_analysispart2.cpp 
python/analysis/build/_analysis/sip_analysispart3.cpp 
python/analysis/build/_analysis/sip_analysispart4.cpp 
python/analysis/build/_analysis/sip_analysispart5.cpp 
python/analysis/build/_analysis/sip_analysispart6.cpp 
python/analysis/build/_analysis/sip_analysispart7.cpp 
python/analysis/build/_analysis/sip_analysispart8.cpp 
python/analysis/build/_analysis/sip_analysispart9.cpp 
python/analysis/build/_analysis/sip_analysispart10.cpp 
python/analysis/build/_analysis/sip_analysispart11.cpp 
python/analysis/build/_analysis/sip_analysispart12.cpp 
python/analysis/build/_analysis/sip_analysispart13.cpp 
python/analysis/build/_analysis/sip_analysispart14.cpp 
python/analysis/build/_analysis/sip_analysispart15.cpp 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart0.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart1.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart2.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart3.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart4.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart5.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart6.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart7.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart8.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart9.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart10.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart11.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart12.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart13.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart14.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart15.cpp
 
 cd /<>/debian/build/python/analysis && /usr/bin/cmake -E echo && 
/usr/bin/sip-build --no-protected-is-public --pep484-pyi --no-make 
--concatenate=16 --qmake=/usr/lib/i386-linux-gnu/qt5/bin/qmake 
--include-dir=/<>/debian/build/python 
--include-dir=/usr/lib/python3/dist-packages/PyQt5/bindings && /usr/bin/cmake 
-E touch 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart0.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart1.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart2.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart3.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart4.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart5.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart6.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart7.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart8.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart9.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart10.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart11.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart12.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart13.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart14.cpp
 
/<>/debian/build/python/analysis/build/_analysis/sip_analysispart15.cpp
 
 Querying qmake about your Qt installation...
 These bindings will be built: analysis.
 Generating the analysis bindings...
 sip-build: An internal error occurred...
 Traceback (most recent call last):
   File "/usr/bin/sip-build", line 33, in 
 sys.exit(load_entry_point('sip==6.6.1', 'console_scripts', 'sip-build')())
   File "/usr/lib/python3/dist-packages/sipbuild/tools/build.py", line 37, in 
main
 

Bug#1009939: sip6: AttributeError: 'YaccProduction' object has no attribute 'parser_manager'

[Dmitry Shachnev]

Hi Sebastiaan!

On Fri, May 13, 2022 at 03:23:07PM +0200, Sebastiaan Couwenberg wrote:
> On 4/21/22 05:39, Bas Couwenberg wrote:
> > Since the upgrade to 6.6.1+dfsg-1 qgis FTBFS:
> According to [0] the current hg tip enables successfull building of QGIS
> again.
>
> That's quite a number of additional changes which I doubt is a good idea to
> add as patches. That is unless it's going to take a long time until 6.6.2
> release.
>
> Do you have any insight when to expect the next sip6 upstream release?

According to [1] it is “hopefully before the end of this month”. But given
that this bug is RC, and there is another bug [2] affecting another package,
then I don't have much choice. So doing a new upload with 27 patches added.

[1]: https://www.riverbankcomputing.com/pipermail/pyqt/2022-May/044649.html
[2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010910

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#1009939: marked as pending in sip6

[Dmitry Shachnev]

Control: tag -1 pending

Hello,

Bug #1009939 in sip6 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/python-team/packages/sip6/-/commit/0ede128e111aaf94e535cacb96828fef4506ee6f


Add upstream changes up to 2022-05-13.

Except one commit which changes runtime module ABI.

Closes: #1009939, #1010910.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1009939

Processed: Bug#1009939 marked as pending in sip6

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1009939 [src:sip6] sip6: AttributeError: 'YaccProduction' object has no 
attribute 'parser_manager'
Ignoring request to alter tags of bug #1009939 to the same tags previously set

-- 
1009939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1011012: tiledb-r FTBFS with tiledb 2.8.3

[Adrian Bunk]

Source: tiledb-r
Version: 0.12.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=tiledb-r=0.12.0-1%2Bb1

...
g++ -std=gnu++17 -I"/usr/share/R/include" -DNDEBUG -I../inst/include/ 
-I/usr/include/tiledb -I'/usr/lib/R/site-library/Rcpp/include'-fpic  -g -O2 
-ffile-prefix-map=/build/r-base-eH67wr/r-base-4.2.0=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c 
libtiledb.cpp -o libtiledb.o
libtiledb.cpp: In function ‘Rcpp::XPtr 
libtiledb_group(Rcpp::XPtr, const string&, const string&)’:
libtiledb.cpp:4401:47: error: no matching function for call to 
‘tiledb::Group::Group()’
 4401 | XPtr ptr(new tiledb::Group()); // placeholder
  |   ^
In file included from /usr/include/tiledb/tiledb_experimental:37,
 from ../inst/include/tiledb.h:7,
 from libtiledb.h:27,
 from libtiledb.cpp:23:
/usr/include/tiledb/group_experimental.h:73:3: note: candidate: 
‘tiledb::Group::Group(tiledb::Group&&)’
   73 |   Group(Group&&) = default;
  |   ^
/usr/include/tiledb/group_experimental.h:73:3: note:   candidate expects 1 
argument, 0 provided
/usr/include/tiledb/group_experimental.h:72:3: note: candidate: 
‘tiledb::Group::Group(const tiledb::Group&)’
   72 |   Group(const Group&) = default;
  |   ^
/usr/include/tiledb/group_experimental.h:72:3: note:   candidate expects 1 
argument, 0 provided
/usr/include/tiledb/group_experimental.h:60:3: note: candidate: 
‘tiledb::Group::Group(const tiledb::Context&, const string&, 
tiledb_query_type_t)’
   60 |   Group(
  |   ^
/usr/include/tiledb/group_experimental.h:60:3: note:   candidate expects 3 
arguments, 0 provided
make[2]: *** [/usr/lib/R/etc/Makeconf:177: libtiledb.o] Error 1

Bug#1010214: marked as done (paramiko breaks libcloud autopkgtest: SSHException not raised by connect)

[Debian Bug Tracking System]

Your message dated Sun, 15 May 2022 10:35:06 +
with message-id 
and subject line Bug#1010214: fixed in libcloud 3.4.1-3
has caused the Debian Bug report #1010214,
regarding paramiko breaks libcloud autopkgtest: SSHException not raised by 
connect
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.)


-- 
1010214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010214
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: paramiko, libcloud
Control: found -1 paramiko/2.10.3-1
Control: found -1 libcloud/3.4.1-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of paramiko the autopkgtest of libcloud fails in 
testing when that autopkgtest is run with the binary packages of 
paramiko from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
paramiko   from testing2.10.3-1
libcloud   from testing3.4.1-2
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of paramiko to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=paramiko

https://ci.debian.net/data/autopkgtest/testing/amd64/libc/libcloud/21182944/log.gz


=== FAILURES 
===
__ ParamikoSSHClientTests.test_key_file_non_pem_format_error 
___


self = testMethod=test_key_file_non_pem_format_error>


@patch('paramiko.SSHClient', Mock)
@unittest.skipIf(paramiko_version >= '2.7.0',
 'New versions of paramiko support OPENSSH key format')
def test_key_file_non_pem_format_error(self):
path = os.path.join(os.path.dirname(__file__),
'fixtures', 'misc',
'test_rsa_non_pem_format.key')
# Supplied as key_material
with open(path, 'r') as fp:
private_key = fp.read()
conn_params = {'hostname': 'dummy.host.org',
   'username': 'ubuntu',
   'key_material': private_key}
mock = ParamikoSSHClient(**conn_params)
expected_msg = 'Invalid or unsupported key type'

  assertRaisesRegex(self, paramiko.ssh_exception.SSHException,

  expected_msg, mock.connect)

test/compute/test_ssh_client.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/libcloud/utils/py3.py:145: in 
assertRaisesRegex

return getattr(self, 'assertRaisesRegex')(*args, **kwargs)
E   AssertionError: SSHException not raised by connect
-- Captured log call 
---

DEBUGlibcloud.compute.ssh:ssh.py:365 Connecting to server


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libcloud
Source-Version: 3.4.1-3
Done: Håvard F. Aasen 

We believe that the bug you reported is fixed in the latest version of
libcloud, 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 1010...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Håvard F. Aasen  (supplier of updated libcloud package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 15 May 2022 07:37:29 +
Source: libcloud
Architecture: source
Version: 3.4.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Håvard F. Aasen 
Closes: 1010214 1010891
Changes:
 libcloud (3.4.1-3) unstable; urgency=medium
 .
   * Team upload.
   [ Debian Janitor ]
   * Remove constraints unnecessary since buster:
 + Build-Depends: Drop 

Bug#964138: marked as done (src:sec: fails to migrate to testing for too long: maintainer built arch:all binary)

[Debian Bug Tracking System]

Your message dated Sun, 15 May 2022 13:32:43 +0300
with message-id 

and subject line Closing 964138
has caused the Debian Bug report #964138,
regarding src:sec: fails to migrate to testing for too long: maintainer built 
arch:all binary
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.)


-- 
964138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sec
Version: 2.8.2-1.1
Severity: serious
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:sec in its
current version in unstable has been trying to migrate for 60 days [2].
Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

Your package is only blocked because the arch:all binary package(s)
aren't built on a buildd. Unfortunately the Debian infrastructure
doesn't allow arch:all packages to be properly binNMU'ed. Because this
is the second time this happens to src:sec, I will not do a no-changes
source-only upload.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=sec




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 2.9.1-1
Closing this, since it is the only thing preventing migration to testing.

2.9.1-1 is a source-only upload which should resolve the issue, as per the bug.

-Jaakko--- End Message ---

Bug#1011011: thrift FTBFS on IPV6-only buildds

[Adrian Bunk]

Source: thrift
Version: 0.16.0-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=thrift=all
https://buildd.debian.org/status/logs.php?pkg=thrift=amd64

...
[1;31;49m*** 3 failures are detected in the test module "TNonblockingServerTest"
FAIL: TNonblockingServerTest
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: Serving with 1 io threads.
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: using libevent 
2.1.12-stable method epoll
Thrift: Sun May 15 10:06:02 2022 TNonblocking: IO thread #0 registered for 
listen.
Thrift: Sun May 15 10:06:02 2022 TNonblocking: IO thread #0 registered for 
notify.
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: IO thread #0 entering 
loop...
Thrift: Sun May 15 10:06:02 2022 TSocket::open() connect() : Connection refused
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: IO thread #0 run() done!
Thrift: Sun May 15 10:06:02 2022 TNonblocking: join done for IO thread #0
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: Serving with 1 io threads.
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: using libevent 
2.1.12-stable method epoll
Thrift: Sun May 15 10:06:02 2022 TNonblocking: IO thread #0 registered for 
listen.
Thrift: Sun May 15 10:06:02 2022 TNonblocking: IO thread #0 registered for 
notify.
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: IO thread #0 entering 
loop...
Thrift: Sun May 15 10:06:02 2022 TSocket::open() connect() : Connection refused
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: IO thread #0 run() done!
Thrift: Sun May 15 10:06:02 2022 TNonblocking: join done for IO thread #0
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: Serving with 1 io threads.
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: using libevent 
2.1.12-stable method epoll
Thrift: Sun May 15 10:06:02 2022 TNonblocking: IO thread #0 registered for 
listen.
Thrift: Sun May 15 10:06:02 2022 TNonblocking: IO thread #0 registered for 
notify.
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: IO thread #0 entering 
loop...
Thrift: Sun May 15 10:06:02 2022 TSocket::open() connect() : Connection refused
Thrift: Sun May 15 10:06:02 2022 TNonblockingServer: IO thread #0 run() done!
Thrift: Sun May 15 10:06:02 2022 TNonblocking: join done for IO thread #0

*** 3 failures are detected in the test module 
"TNonblockingSSLServerTest"
FAIL: TNonblockingSSLServerTest

3 of 21 tests failed

make[7]: *** [Makefile:1467: check-TESTS] Error 1

Bug#1010956: marked as done (kodi: Kodi crashes on startup with "error while loading shared libraries: libwayland-client++)

[Debian Bug Tracking System]

Your message dated Sun, 15 May 2022 10:00:24 +
with message-id 
and subject line Bug#1010956: fixed in waylandpp 1.0.0-2
has caused the Debian Bug report #1010956,
regarding kodi: Kodi crashes on startup with "error while loading shared 
libraries: libwayland-client++
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.)


-- 
1010956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010956
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kodi
Version: 2:19.4+dfsg2-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: markcook...@yahoo.com

Dear Maintainer,

On Debian Unstable, running KDE X11, in the past few days an upgrade has led to 
Kodi failing to start for me.

The error message is:
/usr/lib/x86_64-linux-gnu/kodi/kodi.bin: error while loading shared libraries: 
libwayland-client++.so.0: cannot open shared object file: No such file or 
directory

when starting kodi from the command line - expected result is for Kodi to start.

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.17.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kodi depends on:
ii  kodi-bin   2:19.4+dfsg2-1
ii  kodi-data  2:19.4+dfsg2-1

Versions of packages kodi recommends:
ii  kodi-repository-kodi [kodi-repository]  2:19.4+dfsg2-1
ii  kodi-visualization-spectrum 19.0.1+ds1-1

kodi suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: waylandpp
Source-Version: 1.0.0-2
Done: Georges Khaznadar 

We believe that the bug you reported is fixed in the latest version of
waylandpp, 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 1010...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated waylandpp package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 14 May 2022 17:23:01 +0200
Source: waylandpp
Binary: libwayland-client++1 libwayland-client++1-dbgsym 
libwayland-client-extra++1 libwayland-client-extra++1-dbgsym 
libwayland-cursor++1 libwayland-cursor++1-dbgsym libwayland-egl++1 
libwayland-egl++1-dbgsym libwayland-server++1 libwayland-server++1-dbgsym 
wayland-scanner++ wayland-scanner++-dbgsym waylandpp-dev waylandpp-doc
Architecture: source amd64 all
Version: 1.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Description:
 libwayland-client++1 - wayland compositor infrastructure - client library C++ 
bindings
 libwayland-client-extra++1 - wayland compositor infrastructure - client 
library extra C++ bind
 libwayland-cursor++1 - wayland compositor infrastructure - cursor library C++ 
bindings
 libwayland-egl++1 - wayland compositor infrastructure - EGL library C++ 
bindings
 libwayland-server++1 - wayland compositor infrastructure - EGL library C++ 
bindings
 wayland-scanner++ - wayland compositor infrastructure - C++ protocol code 
generator
 waylandpp-dev - wayland compositor infrastructure - C++ development files
 waylandpp-doc - wayland compositor documentation
Closes: 1010921 1010956
Changes:
 waylandpp (1.0.0-2) unstable; urgency=medium
 .
   * used Vasyl Gello's debdiff, thanks!
 Closes: #1010921
 Closes: #1010956
Checksums-Sha1:
 e9d453414b619d197959802822830ecc37e97248 2498 waylandpp_1.0.0-2.dsc
 2508c1228d2026f90b79b75dc35e6093269d1184 5948 waylandpp_1.0.0-2.debian.tar.xz
 5670ca03a65a5ef136d7c248c28c89c4059ce955 596160 
libwayland-client++1-dbgsym_1.0.0-2_amd64.deb
 

Bug#1010921: marked as done (kodi FTBFS due to outdated shlibs)

[Debian Bug Tracking System]

Your message dated Sun, 15 May 2022 10:00:24 +
with message-id 
and subject line Bug#1010921: fixed in waylandpp 1.0.0-2
has caused the Debian Bug report #1010921,
regarding kodi FTBFS due to outdated shlibs
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.)


-- 
1010921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: waylandpp
Version: 1.0.0-1
Severity: important
Tags: ftbfs patch
X-Debbugs-Cc: vasek.ge...@gmail.com

Dear Maintainer,

Recent upload of new waylandpp 1.0.0 broke kodi build
with "dpkg-shlibdeps: can not find dependency info..."
error message.

I took the responsibility to bump ABI versions in d/control
and fix the shlibs so they are now ++1 rather than ++0.

Kodi builds and runs fine with it.

I have attached the debdiff for your convenience.

Sincerely,
Vasyl

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-7-amd64 (SMP w/32 CPU threads)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

waylandpp.debdiff
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: waylandpp
Source-Version: 1.0.0-2
Done: Georges Khaznadar 

We believe that the bug you reported is fixed in the latest version of
waylandpp, 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 1010...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated waylandpp package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 14 May 2022 17:23:01 +0200
Source: waylandpp
Binary: libwayland-client++1 libwayland-client++1-dbgsym 
libwayland-client-extra++1 libwayland-client-extra++1-dbgsym 
libwayland-cursor++1 libwayland-cursor++1-dbgsym libwayland-egl++1 
libwayland-egl++1-dbgsym libwayland-server++1 libwayland-server++1-dbgsym 
wayland-scanner++ wayland-scanner++-dbgsym waylandpp-dev waylandpp-doc
Architecture: source amd64 all
Version: 1.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Description:
 libwayland-client++1 - wayland compositor infrastructure - client library C++ 
bindings
 libwayland-client-extra++1 - wayland compositor infrastructure - client 
library extra C++ bind
 libwayland-cursor++1 - wayland compositor infrastructure - cursor library C++ 
bindings
 libwayland-egl++1 - wayland compositor infrastructure - EGL library C++ 
bindings
 libwayland-server++1 - wayland compositor infrastructure - EGL library C++ 
bindings
 wayland-scanner++ - wayland compositor infrastructure - C++ protocol code 
generator
 waylandpp-dev - wayland compositor infrastructure - C++ development files
 waylandpp-doc - wayland compositor documentation
Closes: 1010921 1010956
Changes:
 waylandpp (1.0.0-2) unstable; urgency=medium
 .
   * used Vasyl Gello's debdiff, thanks!
 Closes: #1010921
 Closes: #1010956
Checksums-Sha1:
 e9d453414b619d197959802822830ecc37e97248 2498 waylandpp_1.0.0-2.dsc
 2508c1228d2026f90b79b75dc35e6093269d1184 5948 waylandpp_1.0.0-2.debian.tar.xz
 5670ca03a65a5ef136d7c248c28c89c4059ce955 596160 
libwayland-client++1-dbgsym_1.0.0-2_amd64.deb
 cdc719ed5b28e7e444189d11d83fc29484c5fff4 69104 
libwayland-client++1_1.0.0-2_amd64.deb
 274dcb1f7fe9456e5071bfadbb0b73cae9d63019 252684 
libwayland-client-extra++1-dbgsym_1.0.0-2_amd64.deb
 624a80c6422c1ac6573442a6e857df55afbcd0c2 30712 
libwayland-client-extra++1_1.0.0-2_amd64.deb
 9ee388cad2063ebb5a5fd965b394a8609223c836 49744 
libwayland-cursor++1-dbgsym_1.0.0-2_amd64.deb
 ce99f12b8477f9f45f85cc107d79abf04c0c6916 10536 
libwayland-cursor++1_1.0.0-2_amd64.deb
 0640efbe893eb35f6de2fbfa4cdff229fcf83859 43288 
libwayland-egl++1-dbgsym_1.0.0-2_amd64.deb
 a7490b5656906b534320baef56fd3e2603aef9ac 8884 
libwayland-egl++1_1.0.0-2_amd64.deb
 e3285aba4620a7efa1ddd8d2709ae5d14c872a35 1388612 
libwayland-server++1-dbgsym_1.0.0-2_amd64.deb
 220259445355fc251a57b173019cfab86cabf39a 170012 

Bug#1011009: kitinerary FTBFS: test failure

[Adrian Bunk]

Source: kitinerary
Version: 21.12.3-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=kitinerary=21.12.3-2%2Bb1

...
test 31
  Start 31: calendarhandlertest

31: Test command: /<>/obj-x86_64-linux-gnu/bin/calendarhandlertest
31: Environment variables: 
31:  QT_PLUGIN_PATH=/<>/obj-x86_64-linux-gnu/bin:
31: Test timeout computed to be: 1000
31: * Start testing of CalendarHandlerTest *
31: Config: Using QtTest library 5.15.2, Qt 5.15.2 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 11.3.0), debian unknown
31: PASS   : CalendarHandlerTest::initTestCase()
31: PASS   : CalendarHandlerTest::testCreateEvent(canceled.json)
31: QDEBUG : CalendarHandlerTest::testCreateEvent(event.json) Actual:  
BEGIN:VCALENDAR
31: PRODID:-//K Desktop Environment//NONSGML libkcal 4.3//EN
31: VERSION:2.0
31: X-KDE-ICAL-IMPLEMENTATION-VERSION:1.0
31: BEGIN:VTIMEZONE
31: TZID:Europe/Rome
31: BEGIN:DAYLIGHT
31: TZNAME:CEST
31: TZOFFSETFROM:+
31: TZOFFSETTO:+0200
31: DTSTART:19700530T23
31: RDATE:19700530T23
31: END:DAYLIGHT
31: BEGIN:STANDARD
31: TZNAME:CET
31: TZOFFSETFROM:+0200
31: TZOFFSETTO:+0100
31: DTSTART:19810927T03
31: RRULE:FREQ=YEARLY;UNTIL=19961027T03;BYDAY=-1SU;BYMONTH=9
31: END:STANDARD
31: BEGIN:STANDARD
31: TZNAME:CET
31: TZOFFSETFROM:+0200
31: TZOFFSETTO:+0100
31: DTSTART:19971026T03
31: RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
31: END:STANDARD
31: BEGIN:STANDARD
31: TZNAME:CET
31: TZOFFSETFROM:+0200
31: TZOFFSETTO:+0100
31: DTSTART:19700927T01
31: RRULE:FREQ=YEARLY;UNTIL=19800928T03;BYDAY=-1SA;BYMONTH=9
31: RDATE:19790930T01
31: RDATE:19950924T03
31: END:STANDARD
31: BEGIN:DAYLIGHT
31: TZNAME:CEST
31: TZOFFSETFROM:+0100
31: TZOFFSETTO:+0200
31: DTSTART:19810329T02
31: RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
31: END:DAYLIGHT
31: BEGIN:DAYLIGHT
31: TZNAME:CEST
31: TZOFFSETFROM:+0100
31: TZOFFSETTO:+0200
31: DTSTART:19710523T00
31: RDATE:19710523T00
31: RDATE:19720528T00
31: RDATE:19730603T00
31: RDATE:19740526T00
31: RDATE:19750601T00
31: RDATE:19760530T00
31: RDATE:19770522T00
31: RDATE:19780528T00
31: RDATE:19790527T00
31: RDATE:19800406T02
31: END:DAYLIGHT
31: END:VTIMEZONE
31: BEGIN:VEVENT
31: DTSTAMP:20171227T111649Z
31: X-KDE-KITINERARY-RESERVATION:[{"@context":"http://schema.org"\,"@type":
31:  "Event"\,"description":"For most of the year\, KDE—one of the largest 
31:  free and open software communities in the world — works on-line by 
31:  email\, IRC\, forums and mailing lists. Akademy provides all KDE 
31:  contributors the opportunity to meet in person to foster social bonds\, 
31:  work on concrete technology issues\, consider new ideas\, and reinforce 
31:  the innovative\, dynamic culture of KDE. Akademy brings together 
31:  artists\, designers\, developers\, translators\, users\, writers\, 
31:  sponsors and many other types of KDE contributors to celebrate the 
31:  achievements of the past year and help determine the direction for the 
31:  next year. Hands-on sessions offer the opportunity for intense work 
31:  bringing those plans to reality. The KDE community welcomes companies 
31:  building on KDE technology\, and those that are looking for 
31:  opportunities. For more information\, please contact the Akademy 
31:  Team."\,"doorTime":{"@type":"QDateTime"\,"@value":"2019-07-13T08:30:00+02:
31:  00"\,"timezone":"Europe/Rome"}\,"endDate":{"@type":"QDateTime"\,"@value":
31:  "2019-07-13T16:30:00+02:00"\,"timezone":"Europe/Rome"}\,"image":"https:
31:  //akademy.kde.org/sites/akademy.kde.org/files/2019/milanpanoramic.jpg"\,"l
31:  ocation":{"@type":"Place"\,"address":{"@type":
31:  "PostalAddress"\,"addressCountry":"IT"\,"addressLocality":
31:  "Milan"\,"addressRegion":"Lombardy"\,"postalCode":
31:  "20126"\,"streetAddress":"Piazza dell'Ateneo Nuovo\, 1"}\,"name":
31:  "University of Milano-Bicocca"}\,"name":"Akademy 2019"\,"startDate":
31:  {"@type":"QDateTime"\,"@value":"2019-09-07T09:30:00+02:00"\,"timezone":
31:  "Europe/Rome"}\,"url":"https://akademy.kde.org/2019"}]
31: CREATED:20171227T111649Z
31: UID:KIT-1234567890-1b22236a-21ff-4885-8c99-b3b2bbca062c
31: LAST-MODIFIED:20171227T111649Z
31: DESCRIPTION:Piazza dell'Ateneo Nuovo\, 1\n20126 MILAN\n\nITALY\n
31: SUMMARY:Akademy 2019
31: LOCATION:University of Milano-Bicocca
31: DTSTART;TZID=Europe/Rome:20190907T093000
31: DTEND;TZID=Europe/Rome:20190713T163000
31: TRANSP:OPAQUE
31: BEGIN:VALARM
31: DESCRIPTION:Entrance for Akademy 2019
31: ACTION:DISPLAY
31: TRIGGER:-P56DT1H
31: X-KDE-KCALCORE-ENABLED:TRUE
31: END:VALARM
31: END:VEVENT
31: END:VCALENDAR
31: 
31: QDEBUG : CalendarHandlerTest::testCreateEvent(event.json) Expected:  
BEGIN:VCALENDAR
31: PRODID:-//K Desktop Environment//NONSGML libkcal 4.3//EN
31: VERSION:2.0
31: X-KDE-ICAL-IMPLEMENTATION-VERSION:1.0
31: BEGIN:VTIMEZONE
31: TZID:Europe/Rome
31: BEGIN:DAYLIGHT
31: TZNAME:CEST
31: TZOFFSETFROM:+
31: TZOFFSETTO:+0200
31: 

Bug#1006580: marked as done (xrdp: FTBFS with OpenSSL 3.0)

[Debian Bug Tracking System]

Your message dated Sun, 15 May 2022 09:04:25 +0200
with message-id 
and subject line xrdp: FTBFS with OpenSSL 3.0
has caused the Debian Bug report #1006580,
regarding xrdp: 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.)


-- 
1006580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xrdp
Version: 0.9.17-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 with the
following error:

| libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -DXRDP_CFG_PATH=\"/etc/xrdp\" 
-DXRDP_SBIN_PATH=\"/usr/sbin\" -DXRDP_SHARE_PATH=\"/usr/share/xrdp\" 
-DXRDP_PID_PATH=\"/var/run/xrdp\" -DXRDP_LOG_PATH=\"/var/log\" 
-DXRDP_SOCKET_PATH=\"/run/xrdp/sockdir\" -include config_ac.h -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -Wwrite-strings 
-Werror -c ssl_calls.c  -fPIC -DPIC -o .libs/ssl_calls.o
| ssl_calls.c: In function ‘ssl_rc4_set_key’:
| ssl_calls.c:145:5: error: ‘RC4_set_key’ is deprecated: Since OpenSSL 3.0 
[-Werror=deprecated-declarations]
|   145 | RC4_set_key((RC4_KEY *)rc4_info, len, (tui8 *)key);
|   | ^~~
| In file included from ssl_calls.c:29:
| /usr/include/openssl/rc4.h:35:28: note: declared here
|35 | OSSL_DEPRECATEDIN_3_0 void RC4_set_key(RC4_KEY *key, int len,
|   |^~~
| ssl_calls.c: In function ‘ssl_rc4_crypt’:
| ssl_calls.c:152:5: error: ‘RC4’ is deprecated: Since OpenSSL 3.0 
[-Werror=deprecated-declarations]
|   152 | RC4((RC4_KEY *)rc4_info, len, (tui8 *)data, (tui8 *)data);
|   | ^~~
| In file included from ssl_calls.c:29:
| /usr/include/openssl/rc4.h:37:28: note: declared here
|37 | OSSL_DEPRECATEDIN_3_0 void RC4(RC4_KEY *key, size_t len,
|   |^~~
| ssl_calls.c: In function ‘ssl_sha1_clear’:
| ssl_calls.c:175:5: error: ‘SHA1_Init’ is deprecated: Since OpenSSL 3.0 
[-Werror=deprecated-declarations]
|   175 | SHA1_Init((SHA_CTX *)sha1_info);
|   | ^
| In file included from /usr/include/openssl/x509.h:41,
|  from /usr/include/openssl/ssl.h:31,
|  from ssl_calls.c:27:
| /usr/include/openssl/sha.h:49:27: note: declared here
|49 | OSSL_DEPRECATEDIN_3_0 int SHA1_Init(SHA_CTX *c);
|   |   ^
| ssl_calls.c: In function ‘ssl_sha1_transform’:
| ssl_calls.c:182:5: error: ‘SHA1_Update’ is deprecated: Since OpenSSL 3.0 
[-Werror=deprecated-declarations]
|   182 | SHA1_Update((SHA_CTX *)sha1_info, data, len);
|   | ^~~
| In file included from /usr/include/openssl/x509.h:41,
|  from /usr/include/openssl/ssl.h:31,
|  from ssl_calls.c:27:
| /usr/include/openssl/sha.h:50:27: note: declared here
|50 | OSSL_DEPRECATEDIN_3_0 int SHA1_Update(SHA_CTX *c, const void *data, 
size_t len);
|   |   ^~~
| ssl_calls.c: In function ‘ssl_sha1_complete’:
| ssl_calls.c:189:5: error: ‘SHA1_Final’ is deprecated: Since OpenSSL 3.0 
[-Werror=deprecated-declarations]
|   189 | SHA1_Final((tui8 *)data, (SHA_CTX *)sha1_info);
|   | ^~
| In file included from /usr/include/openssl/x509.h:41,
|  from /usr/include/openssl/ssl.h:31,
|  from ssl_calls.c:27:
| /usr/include/openssl/sha.h:51:27: note: declared here
|51 | OSSL_DEPRECATEDIN_3_0 int SHA1_Final(unsigned char *md, SHA_CTX *c);
|   |   ^~
| ssl_calls.c: In function ‘ssl_md5_clear’:
| ssl_calls.c:212:5: error: ‘MD5_Init’ is deprecated: Since OpenSSL 3.0 
[-Werror=deprecated-declarations]
|   212 | MD5_Init((MD5_CTX *)md5_info);
|   | ^~~~
| In file included from ssl_calls.c:30:
| /usr/include/openssl/md5.h:49:27: note: declared here
|49 | OSSL_DEPRECATEDIN_3_0 int MD5_Init(MD5_CTX *c);
|   |   ^~~~
| ssl_calls.c: In function ‘ssl_md5_transform’:
| ssl_calls.c:219:5: error: ‘MD5_Update’ is deprecated: Since OpenSSL 3.0 
[-Werror=deprecated-declarations]
|   219 | MD5_Update((MD5_CTX *)md5_info, data, len);
|   | ^~
| In file included from ssl_calls.c:30:
| /usr/include/openssl/md5.h:50:27: note: declared here
|50 | OSSL_DEPRECATEDIN_3_0 int MD5_Update(MD5_CTX *c, const void *data, 
size_t len);
|