Bug#1009733: marked as done (src:exempi: fails to migrate to testing for too long: FTBFS on armel and armhf)

[Debian Bug Tracking System]

Your message dated Wed, 15 Jun 2022 04:48:58 +
with message-id 
and subject line Bug#1009733: fixed in exempi 2.6.1-2
has caused the Debian Bug report #1009733,
regarding src:exempi: fails to migrate to testing for too long: FTBFS on armel 
and armhf
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.)


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

Source: exempi
Version: 2.5.2-1
Severity: serious
Control: close -1 2.6.1-1
Tags: sid bookworm ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:exempi has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. You package failed to build from 
source on armel and armhf where it built successfully in the past.


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


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


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


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: exempi
Source-Version: 2.6.1-2
Done: Michael Biebl 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 15 Jun 2022 06:13:07 +0200
Source: exempi
Architecture: source
Version: 2.6.1-2
Distribution: unstable
Urgency: medium
Maintainer: Michael Biebl 
Changed-By: Michael Biebl 
Closes: 1009733
Changes:
 exempi (2.6.1-2) unstable; urgency=medium
 .
   * XMPFiles/source/XMPFiles_Impl.cpp: fix arm build with gcc 10
 (Closes: #1009733)
Checksums-Sha1:
 d8eec9ecd38419c4cf46e8ef0fb037d7083f2c43 2206 exempi_2.6.1-2.dsc
 f5ad20078839348e5f98fbd1b138d05fa90d8f35 10864 exempi_2.6.1-2.debian.tar.xz
 7b67599a7b910d1a6a3d2d66608f4103ea0a7382 5686 exempi_2.6.1-2_source.buildinfo
Checksums-Sha256:
 d0402ce06fcf3dc7ba901141f7b6a7dceb1c3c0b50f38701120f6122be27d730 2206 
exempi_2.6.1-2.dsc
 d11c644f6a51183ec74113183682d663c2a107c4d07f406286ad73b14926c85c 10864 
exempi_2.6.1-2.debian.tar.xz
 41e20b3cbdbec13ea2aef8ce4a38ee4029a9641bb001dc3940f181dc659e5646 5686 
exempi_2.6.1-2_source.buildinfo
Files:
 738d1f5e33e76f7f6d0a7578939ea992 2206 libs optional exempi_2.6.1-2.dsc
 64277235352e28e05bcd923b077c1d77 10864 libs optional 
exempi_2.6.1-2.debian.tar.xz
 7374073c40228efff044a17a9bcd3550 5686 libs optional 
exempi_2.6.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAmKpX7oACgkQauHfDWCP
ItxQKw/8D7gfYcY7+6UODptTDGZsS8eojrcJ3oOdbP1vugFdCejtEnJPuJtiRzSJ
RLKEPoe5PEIZL4ZWXw0NRoyHV7xZl46HE7aHneowFNCByqCf2enmdeKEqIKDVXLy
flqFFJtJepDNFgxXm5AE0OWHeHl62U2iuKIqwxs7FmCe7mJ46Hq+dTeKyCmkR+XB
21cJx0vZzc38OXMd6I0rsg8EStOc12fAd87TkfeWp8puTtM3KQLQWl7sGkvtkEzb

Bug#997678: marked as done (rust-kmon: FTBFS because of a recent upload of a dep)

[Debian Bug Tracking System]

Your message dated Wed, 15 Jun 2022 01:45:19 +0100
with message-id 
and subject line re: rust-kmon: FTBFS because of a recent upload of a dep
has caused the Debian Bug report #997678,
regarding rust-kmon: FTBFS because of a recent upload of a dep
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.)


-- 
997678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-kmon
Severity: important

Dear Maintainer,

This package currently FTBFS with:

report:
 -
  package: sbuild-build-depends-main-dummy
  version: 0.invalid.0
  architecture: amd64
  status: broken
  reasons:
   -
missing:
 pkg:
  package: librust-tui-dev
  version: 0.9.0-1
  architecture: amd64
  unsat-dependency: librust-itertools-0.9+default-dev:amd64
 depchains:
  -
   depchain:
-
 package: sbuild-build-depends-main-dummy
 version: 0.invalid.0
 architecture: amd64
 depends: librust-tui-0.9+default-dev:amd64 | 
librust-tui-0.9+default-dev:amd64
-
 package: librust-tui+default-dev
 version: 0.9.0-1
 architecture: amd64
 depends: librust-tui-dev:amd64 (= 0.9.0-1)
 

Cheers,
Sylvestre
--- End Message ---
--- Begin Message ---

version: 1.6.0-1

The new upload fixes the build-dependencies.--- End Message ---

Bug#984865: marked as done (rust-tui: depends on multiple unavailable packages)

[Debian Bug Tracking System]

Your message dated Wed, 15 Jun 2022 01:43:24 +0100
with message-id <4c278189-5a62-7c70-1d4d-1d984d198...@debian.org>
and subject line Fixed in new upload
has caused the Debian Bug report #984865,
regarding rust-tui: depends on multiple unavailable packages
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.)


-- 
984865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984865
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-tui
Version: 0.9.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + librust-tui+crossterm-dev librust-tui+curses-dev 
librust-tui+easycurses-dev librust-tui+pancurses-dev librust-tui+rustbox-dev

Hi,

the binary packages built from src:rust-tui depend on several no
longer available packages, e.g.

The following packages have unmet dependencies:
 librust-tui+crossterm-dev : Depends: librust-crossterm-0.17+default-dev but it 
is not installable


Andreas
--- End Message ---
--- Begin Message ---

Version: 0.18.0-1

The new upstream version fixes the dependency issues.--- End Message ---

Bug#1012789: Can you check if Img works at all?

[Vector Hasting]

Package: linuxcnc-uspace

Thank you Jeff for suggesting this is an OpenGL issue.

Indeed, I went looking and I cannot run glxgears on my system, so I think
it would be fair to say that OpenGL is a dependency beyond the 'package
dependencies,' and that without it I can't run the plain vanilla, prettier
interface of LinuxCNC.

It was particularly helpful for you to mention tklinuxcnc, because I had no
idea it was there.

I followed the instructions at
http://linuxcnc.org/docs/2.7/html/gui/tklinuxcnc.html

(one finds the ini files, as of this writing, located at
~/linuxcnc/configs/sim.axis, and modifies/copies one to have a line DISPLAY
= tklinuxcnc  )

Therefore, by using the tklinuxcnc interface, my problem is solve: I have a
working copy of LinuxCNC!

This is as Jeff said an unusual attempt to get a Single Board Computer to
run LinuxCNC, but it may become a more common problem for folks
onceLinuxCNC becomes available in Debian Bookworm.

Therefore, a more fulsome message would probably reduce support work
downstream, but I'm not sure how to implement that myself. I'm happy to be
pointed in the right direction, either on this board or off.

Thanks again for everyone's help.

Bug#1012827: libwine-dev: libwine.so is a dangling symlink

[Adrian Bunk]

Package: libwine-dev
Version: 7.0~repack-1
Severity: serious
Control: affects -1 src:lmms

lrwxrwxrwx 1 root root 12 Jun  5 21:54 
/usr/lib/x86_64-linux-gnu/wine/libwine.so -> libwine.so.1

libwine-dev: /usr/lib/x86_64-linux-gnu/wine/libwine.so
libwine:amd64: /usr/lib/x86_64-linux-gnu/wine/x86_64-unix/libwine.so.1
libwine:amd64: /usr/lib/x86_64-linux-gnu/wine/x86_64-unix/libwine.so.1.0


lrwxrwxrwx 1 root root 12 Jun  5 21:54 /usr/lib/i386-linux-gnu/wine/libwine.so 
-> libwine.so.1

libwine-dev: /usr/lib/i386-linux-gnu/wine/libwine.so
libwine:i386: /usr/lib/i386-linux-gnu/wine/i386-unix/libwine.so.1
libwine:i386: /usr/lib/i386-linux-gnu/wine/i386-unix/libwine.so.1.0

Processed: libwine-dev: libwine.so is a dangling symlink

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:lmms
Bug #1012827 [libwine-dev] libwine-dev: libwine.so is a dangling symlink
Added indication that 1012827 affects src:lmms

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

Processed: Bug#960576 marked as pending in pyfg

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #960576 {Done: Sandro Tosi } [src:pyfg] pyfg FTBFS with 
python3-pip 20.1
Added tag(s) pending.

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

Bug#960576: marked as pending in pyfg

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #960576 in pyfg 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/pyfg/-/commit/1bee765d5352345fb3784391147dfae9749662ce


additional fixes to setup.py for a recent pip releases; Closes: #960576


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/960576

Bug#960576: marked as done (pyfg FTBFS with python3-pip 20.1)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jun 2022 23:09:04 +
with message-id 
and subject line Bug#960576: fixed in pyfg 0.50-3
has caused the Debian Bug report #960576,
regarding pyfg FTBFS with python3-pip 20.1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pyfg

...
   dh_auto_clean -O--buildsystem=pybuild
dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 9 
in use)
I: pybuild base:217: python3.8 setup.py clean 
Traceback (most recent call last):
  File "setup.py", line 16, in 
reqs = [str(ir.req) for ir in install_reqs]
  File "setup.py", line 16, in 
reqs = [str(ir.req) for ir in install_reqs]
AttributeError: 'ParsedRequirement' object has no attribute 'req'
E: pybuild pybuild:352: clean: plugin distutils failed with: exit code=1: 
python3.8 setup.py clean 
dh_auto_clean: error: pybuild --clean -i python{version} -p 3.8 returned exit 
code 13
make: *** [debian/rules:5: clean] Error 25
--- End Message ---
--- Begin Message ---
Source: pyfg
Source-Version: 0.50-3
Done: Sandro Tosi 

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated pyfg 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, 14 Jun 2022 18:29:50 -0400
Source: pyfg
Architecture: source
Version: 0.50-3
Distribution: unstable
Urgency: medium
Maintainer: Vincent Bernat 
Changed-By: Sandro Tosi 
Closes: 960576
Changes:
 pyfg (0.50-3) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Sandro Tosi ]
   * Use the new Debian Python Team contact name and address
   * debian/patches/further-modern-pip-fixes.patch
 - additional fixes to setup.py for a recent pip releases; Closes: #960576
Checksums-Sha1:
 219aefd66ad6c2ee8494543d81232ebd2b6220e3 1945 pyfg_0.50-3.dsc
 107a79e66eae6bfe2d725c53331d1b7094518e75 2952 pyfg_0.50-3.debian.tar.xz
 5db74ade0a53aa262e5ec4f1242442733916b3d6 7071 pyfg_0.50-3_source.buildinfo
Checksums-Sha256:
 a90922d09e8506191bbe7bb7ec4926a617c6a34d017c23380acf146023201275 1945 
pyfg_0.50-3.dsc
 5b572381186bc4c7401b19ee07421b6d700caecc703d99ca1652e9e979005e85 2952 
pyfg_0.50-3.debian.tar.xz
 7d4cc0ffa39bc4761d6332d9a13f967e367e1dbd6b01ee4c3ef1084cf8061a9c 7071 
pyfg_0.50-3_source.buildinfo
Files:
 ea6f60b1e71d7db8e079e6798f3a0a1c 1945 python optional pyfg_0.50-3.dsc
 acdeb895e8502a84ca27cb8bb14f0450 2952 python optional pyfg_0.50-3.debian.tar.xz
 41b906a9194c630da86fa7871f35e3db 7071 python optional 
pyfg_0.50-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAmKpC+wACgkQh588mTgB
qU9eMA//ftEkYS0yo5ntw4ONuWGhjChDq3ErbSLoX087aNTnAHz0Nkn56WmfbdNB
XzXr2lRbWCo6wJfKBzTmFPYyXI4XjfzjgRauF/kR2BlevyNw9Fv9NPzNHW7x2+n3
8mOLH7Q2r/7ZLgJ/eAOtfJbRz2dFBx1EmNTr2YgQiTJiHQjZ+lP5qgPb1+y/lJzz
re1Ftgk37qc5i+20qqvF1JSEtJtZzm+29faoXy9RXXg3LLDYnlv5Vgd6qS/DBE8Z
00wwd9npRVyhxHCsB6fdauuR5eOPCiJP4Rgb29QlVnJoOJB81bBHPuJC2ZlHjZeA
r33VhPbnZS747il2g9owrUZmSi5AnavZcUD3VVb3bVMUuXIUxwEIlMyfGtGl5IpC
41ZwlWADLtUfyP2dRhpuMyeEF1cKGJNwKvz3/jKi2QQuTlHCeMZcfB+fNy0c1Lvk
J0OHWxBEdcwHLMVptmmD9s1XexUX38/AlMUb1aNWtSgtFmtHhkrVialtxO7alttW
BtV/CHYlbwAerqZDI/tphpKzZOExzmXWBUirrofIZiokAg2OSY5spCHJQR+iny5/
kY0fgYPw9AOqZLoKGmRzop2VQlqJ+xBPnEevxEVCu8FCyC9CnbACK24zAvW4rHbG
9YQMUFS9ynriIYDxeAj5Kec/1k8f8sm8qmSVmaBp7if2cQzSZdM=
=yLu4
-END PGP SIGNATURE End Message ---

Bug#1012789: Can you check if Img works at all?

[Vector Hasting]

Package: linuxcnc-uspace

I started wish from the Terminal.
It brings up a % prompt and launches a small grey window
Typed linuxcnc  (inside the terminal, at the % prompt)
The initial configuration selection window opens, I chose the "axis_mm"
configuration and clicked OK.
It thinks for a while, and then sends the same error message ending in
"undefined symbol: _TIFFsetString, version LIBTIFF_4.0"

Thanks again for your time.

Vector Hasting

Bug#1012789: Can you check if Img works at all?

[Vector Hasting]

I started wish from the Terminal.
It brings up a % prompt and launches a small grey window
Typed linuxcnc  (inside the terminal, at the % prompt)
The initial configuration selection window opens, I chose the "axis_mm"
configuration and clicked OK.
It thinks for a while, and then sends the same error message ending in
"undefined symbol: _TIFFsetString, version LIBTIFF_4.0"

Thanks again for your time.



Vector Hasting

Bug#1007134: marked as done (nzbget: wrong architecture target for source files on armhf)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jun 2022 22:14:16 +
with message-id 
and subject line Bug#1007134: fixed in nzbget 21.0+dfsg-2.1
has caused the Debian Bug report #1007134,
regarding nzbget: wrong architecture target for source files on armhf
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.)


-- 
1007134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nzbget
Version: 21.0+dfsg-2
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch

Hi Andreas,

The nzbget package is failing to build from source in Ubuntu on armhf,
because Ubuntu's compiler is currently stricter with compiler options than
Debian's:

[...]
g++ -DHAVE_CONFIG_H -I.  -I./daemon/connect -I./daemon/extension 
-I./daemon/feed -I./daemon/frontend -I./daemon/main -I./daemon/nntp 
-I./daemon/postprocess -I./daemon/queue -I./daemon/remote -I./daemon/util 
-I./daemon/nserv -I./lib/par2 -I./lib/yencode  -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/libxml2 -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600-g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fpermissive -march=armv8-a+crc -fpermissive -c -o 
lib/yencode/AcleCrc.o lib/yencode/AcleCrc.cpp
cc1plus: error: ‘-mfloat-abi=hard’: selected architecture lacks an FPU
make[2]: *** [Makefile:1774: lib/yencode/AcleCrc.o] Error 1
[...]

  
(https://launchpad.net/ubuntu/+source/nzbget/21.0+dfsg-2ubuntu1/+build/22597345)

The compiler doesn't like the use of -march=armv8-a+crc as a target because
this override of a default target doesn't specify the presence of an FPU,
which is required for hard-float (the 'hf' in armhf).

However, the correct fix here is NOT to pass -march=armv8-a+crc+fp, because
armv8 code is not guaranteed to run on the armhf architecture!  The baseline
for armhf in Debian is armv6 and in Ubuntu is armv7, so having code that
doesn't do CPU detection but is built for armv8 (or neon/simd, as appears
elsewhere in the build scripts) will generate SIGILL on various hardware
that is supposed to be supported.

I therefore think the simplest correct fix is to disable these optimizations
for armhf - if someone wants better performance on the hardware in question
they can use the arm64 build instead.

Attached is the patch I've uploaded to Ubuntu to solve this there.  Please
consider applying it in Debian as well.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru nzbget-21.0+dfsg/debian/patches/armv7-only.patch 
nzbget-21.0+dfsg/debian/patches/armv7-only.patch
--- nzbget-21.0+dfsg/debian/patches/armv7-only.patch1969-12-31 
16:00:00.0 -0800
+++ nzbget-21.0+dfsg/debian/patches/armv7-only.patch2022-03-11 
10:19:23.0 -0800
@@ -0,0 +1,24 @@
+Description: don't use NEON, armv8 instructions on armhf
+ The guaranteed ISA for armhf is armv7+fpu and does not include SIMD or
+ armv8.  Do not try to optimize the armhf binary with these extensions;
+ users who want this should run the arm64 port.
+Author: Steve Langasek 
+Last-Update: 2022-03-11
+Forwarded: no
+
+Index: nzbget-21.0+dfsg/configure.ac
+===
+--- nzbget-21.0+dfsg.orig/configure.ac
 nzbget-21.0+dfsg/configure.ac
+@@ -572,11 +572,6 @@
+   PCLMUL_CXXFLAGS="-msse4.1 -mpclmul"
+   USE_SIMD=yes
+   ;;
+-  arm*)
+-  NEON_CXXFLAGS="-mfpu=neon"
+-  ACLECRC_CXXFLAGS="-march=armv8-a+crc -fpermissive"
+-  USE_SIMD=yes
+-  ;;
+   aarch64)
+   ACLECRC_CXXFLAGS="-march=armv8-a+crc -fpermissive"
+   USE_SIMD=yes
diff -Nru nzbget-21.0+dfsg/debian/patches/series 
nzbget-21.0+dfsg/debian/patches/series
--- nzbget-21.0+dfsg/debian/patches/series  2021-12-07 04:28:18.0 
-0800
+++ nzbget-21.0+dfsg/debian/patches/series  2022-03-11 10:17:49.0 
-0800
@@ -1,2 +1,3 @@
 0001-dont-embed-libraries.patch
 fips_mode.patch
+armv7-only.patch
--- End Message ---
--- Begin Message ---
Source: nzbget
Source-Version: 21.0+dfsg-2.1
Done: Håvard F. Aasen 

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

A summary of the changes 

Bug#1005717: marked as done (nzbget: FTBFS with OpenSSL 3.0)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jun 2022 22:14:16 +
with message-id 
and subject line Bug#1005717: fixed in nzbget 21.0+dfsg-2.1
has caused the Debian Bug report #1005717,
regarding nzbget: 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.)


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

Source: nzbget
Version: 21.0+dfsg-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:

| daemon/connect/TlsSocket.cpp: In static member function ‘static void 
TlsSocket::Final()’:
| daemon/connect/TlsSocket.cpp:192:9: error: ‘FIPS_mode_set’ was not declared 
in this scope
|   192 | FIPS_mode_set(0);
|   | ^
| daemon/connect/TlsSocket.cpp: In member function ‘bool TlsSocket::Start()’:
| daemon/connect/TlsSocket.cpp:392:56: warning: ‘EC_KEY* 
EC_KEY_new_by_curve_name(int)’ is deprecated: Since OpenSSL 3.0 
[-Wdeprecated-declara tions]
|   392 | EC_KEY* ecdh = 
EC_KEY_new_by_curve_name(NID_X9_62_prime256v1);
|   |
^~
| In file included from /usr/include/openssl/x509.h:33,
|  from /usr/include/openssl/ssl.h:31,
|  from ./daemon/main/nzbget.h:257,
|  from daemon/connect/TlsSocket.cpp:21:
| /usr/include/openssl/ec.h:996:31: note: declared here
|   996 | OSSL_DEPRECATEDIN_3_0 EC_KEY *EC_KEY_new_by_curve_name(int nid);
|   |   ^~~~
| daemon/connect/TlsSocket.cpp:402:36: warning: ‘void EC_KEY_free(EC_KEY*)’ is 
deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
|   402 | EC_KEY_free(ecdh);
|   | ~~~^~
| In file included from /usr/include/openssl/x509.h:33,
|  from /usr/include/openssl/ssl.h:31,
|  from ./daemon/main/nzbget.h:257,
|  from daemon/connect/TlsSocket.cpp:21:
| /usr/include/openssl/ec.h:1001:28: note: declared here
|  1001 | OSSL_DEPRECATEDIN_3_0 void EC_KEY_free(EC_KEY *key);
|   |^~~
| daemon/connect/TlsSocket.cpp:406:28: warning: ‘void EC_KEY_free(EC_KEY*)’ is 
deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
|   406 | EC_KEY_free(ecdh);
|   | ~~~^~
| In file included from /usr/include/openssl/x509.h:33,
|  from /usr/include/openssl/ssl.h:31,
|  from ./daemon/main/nzbget.h:257,
|  from daemon/connect/TlsSocket.cpp:21:
| /usr/include/openssl/ec.h:1001:28: note: declared here
|  1001 | OSSL_DEPRECATEDIN_3_0 void EC_KEY_free(EC_KEY *key);
|   |^~~
| daemon/connect/Connection.cpp: In function ‘hostent* 
android_read_hostent(FILE*, hostent*, char*, size_t)’:
| daemon/connect/Connection.cpp:1196:22: warning: ignoring return value of 
‘size_t fread(void*, size_t, size_t, FILE*)’ declared with attribut e 
‘warn_unused_result’ [-Wunused-result]
|  1196 | fread(, 1, sizeof(size), proxy);
|   | ~^~~
| make[2]: *** [Makefile:1774: daemon/connect/TlsSocket.o] Error 1

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

Sebastian
--- End Message ---
--- Begin Message ---
Source: nzbget
Source-Version: 21.0+dfsg-2.1
Done: Håvard F. Aasen 

We believe that the bug you reported is fixed in the latest version of
nzbget, 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.
Håvard F. Aasen  (supplier of updated nzbget package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 07 Jun 2022 15:16:11 +0200
Source: nzbget
Architecture: source
Version: 21.0+dfsg-2.1
Distribution: unstable
Urgency: medium
Maintainer: Andreas Moog 
Changed-By: 

Bug#1012789: [Emc-developers] Bug#1012789: linuxcnc-uspace: Linux CNC will not start

[Vector Hasting]

Thank you for looking at this!

(My purpose reporting here is the understanding that we're trying to debug
to get sid into stable Bookworm with LinuxCNC, and I also want LinuxCNC
working on my little SBC.)

This is potentially helpful, but doesn't immediately clear things up for
me...

Here's what I did after getting this email:

I found the following libtiff packages on my SBC:
libtiff-dev  4.4.0-2
libtiff5 4.4.0-2
libtiffxx5  4.4.0-2

When I search the debian repository, it lists these as unstable (I presume
because we're on sid).
But it also lists them as the most recent releases, not the releases from
Buster (4.2.0-1).

Trying to follow the threads further, I went after the error message you
pointed out and saw it's trying to get:   libtifftcl4.1.0.so

I searched the debian repository and nothing by the name of libtiffcl4
exists:

"You have searched for packages that names contain libtifftcl in all
suites, all sections, and all architectures.
Sorry, your search gave no results"

Interestingly, the Sourceforge branches for tkImg does not have a *branch*
for 1.4 (which appears to be what the line above is looking for)
https://sourceforge.net/p/tkimg/code/HEAD/tree/branches/

But there *is* a version 1.4.13 under tags:
https://sourceforge.net/p/tkimg/code/HEAD/tree/tags/1.4.13/

I downloaded that 1.4.13 source and used MS Code to search the downloaded
source and found a piece of code compat/libtiff/libtiff/libtiff.map that
has the string " LIBTIFF_4.0" in it.

I found 8 files that have _TIFFsetString in it.

But I don't understand the compiling setup well enough to see how those
files get compiled to create an object named libtifftcl4.1.0.so  (??)

(there is no string in the source for libtifftcl4)

I'm happy to try and dig further, but I'm also at a stop point.

Vector Hasting



On Tue, 14 Jun 2022 at 07:31, andy pugh  wrote:

> On Tue, 14 Jun 2022 at 14:49, Vector Hasting 
> wrote:
>
> > _tkinter.TclError: couldn't load file
> "/usr/lib/tcltk/aarch64-linux-gnu/Img1.4.13/libtifftcl4.1.0.so":
> /usr/lib/tcltk/aarch64-linux-gnu/Img1.4.13/libtifftcl4.1.0.so: undefined
> symbol: _TIFFsetString, version LIBTIFF_4.0
>
> This looks to be a dependency (hard coded?) on the version of libtiff
> that shipped with Buster (4.1).
>
> But it also seems to be in a package that LinuxCNC depends on, but
> doesn't control?
> https://sourceforge.net/projects/tkimg/files/tkimg/1.4/tkimg%201.4.13/
> (From the file path being searched)
>
> For me, the trail dries up there. I guess this is due to a Tcl/Tk
> dependency?
>
> --
> atp
> "A motorcycle is a bicycle with a pandemonium attachment and is
> designed for the especial use of mechanical geniuses, daredevils and
> lunatics."
> — George Fitch, Atlanta Constitution Newspaper, 1912
>

Bug#1012407: marked as done (libsingular4m2n1: changes SONAME without changing package name)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jun 2022 22:00:16 +
with message-id 
and subject line Bug#1012407: fixed in singular 1:4.3.0-p1+ds-3
has caused the Debian Bug report #1012407,
regarding libsingular4m2n1: changes SONAME without changing package name
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.)


-- 
1012407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsingular4m2n1
Version: 1:4.3.0-p1+ds-2
Severity: serious
Justification: violates policy MUST: section 8.1, first paragraph

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Version 4.3.0 of libsingular4m2n1 has an SONAME of 

libsingular-Singular-4.3.0.so

Version 4.2.1 has SONAME

libsingular-Singular-4.2.1.so

This means the package name has to change, otherwise packages built
against 4.2.1 will break on systems with 4.3.0 installed.

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

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

Versions of packages libsingular4m2n1 depends on:
ii  libc6   2.33-7
ii  libflint-2.8.5  2.8.5-2
ii  libgmp102:6.2.1+dfsg-3
ii  libmpfr64.1.0-3
ii  libntl4411.5.1-1+b1
ii  libreadline88.1.2-1.2
ii  libstdc++6  12.1.0-2

libsingular4m2n1 recommends no packages.

libsingular4m2n1 suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmKeDmMACgkQA0U5G1Wq
FSGHzw//UV7FGyvisGdYJaHpl+OVZyvQ/lPrWZyelFM2U94o8hB+E4Mi6ZKvxX7/
jJ1G7U8yR5GSgkAmzNwrUTL2rO+F0db/qnQV7i5IgTOmtCOrSoDUKvf08daTTUMl
5/Fe1y7VrESL6aFljigYLf2HuO+uoXqQRmIP8hmr7Io4N4s01ipBojrQ1Kuj10PP
VaRi3hPX/FzkVk6exA6W8sVxh36mMu1S6tAy9kWjpF3asnmy7dks/byjBwei88rL
RKHVle59pjGghY3LscEesgHV05EiH1AFsc7h5XWpxKqaNpUtgunz0KSEsX3iAVqK
jg76WErZAgzmclXsGPqgtdtxUYs7qa28Yf51X2PUhsYNpcXhr7lsOn+VT0GxXIEm
Hp3T9QzNwXl51hXqy11ajPn2uZENUXF66UxAuxbTqbmuyxg8uCPg6s4i1UeLcYUI
HDT38SVBj44dHdO8DrzrLTuCxxHx0cUKqX7Jq/Ie/1++JRkEUFyVr6Ls60szhKKs
XPYLeRAZMtxk9Rg1Vbbsqnn7GAiq8C9OeiCgpBFGbXo9m2gMZkjrHOQjexT12vVw
5/my1wm3jpx8eGoJ+Trkz61aFqU0ohG+PWH0lwGnrkBahogdFMWkL6SKfS5r1bfO
c7mJ7FIjO0Sxtu/HQ3KUaOhLv0jxw1bENV3gfPFyid37Xo1eetg=
=IVAe
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: singular
Source-Version: 1:4.3.0-p1+ds-3
Done: Jerome Benoit 

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

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

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

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated singular 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, 12 Jun 2022 12:59:04 +
Source: singular
Binary: libsingular4-dev libsingular4-dev-common libsingular4m3n0 
libsingular4m3n0-dbgsym singular singular-data singular-dev-doc singular-doc 
singular-modules singular-modules-dbgsym singular-ui singular-ui-dbgsym 
singular-ui-emacs singular-ui-emacs-dbgsym singular-ui-xterm 
singular-ui-xterm-dbgsym
Architecture: source all amd64
Version: 1:4.3.0-p1+ds-3
Distribution: experimental
Urgency: medium
Maintainer: Debian Math Team 
Changed-By: Jerome Benoit 
Description:
 libsingular4-dev - Computer Algebra System for Polynomial Computations -- 
developmen
 libsingular4-dev-common - Computer Algebra System for Polynomial Computations 
-- common dev
 libsingular4m3n0 - Computer Algebra System for Polynomial Computations -- 
library pa
 singular   - Computer Algebra System for Polynomial Computations
 singular-data - Computer Algebra System for Polynomial Computations -- shared 
dat
 singular-dev-doc - Computer Algebra System for Polynomial Computations -- 
developer
 singular-doc - Computer Algebra System 

Bug#1010582: marked as done (varnish: New upstream release 7.1.0)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jun 2022 22:00:17 +
with message-id 
and subject line Bug#1010582: fixed in varnish 7.1.0-4
has caused the Debian Bug report #1010582,
regarding varnish: New upstream release 7.1.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.)


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

Package: varnish
Version: 6.6.1-1
Severity: serious

Dear Maintainer,

A new upstream release 7.1.0 is available, that fixes CVE-2022-23959.

I need this version for it to be automatically synced into Ubuntu 
Kinetic

(see https://bugs.launchpad.net/ubuntu/+source/varnish/+bug/1971504).

Kind regards,
Luís Infante da Câmara
--- End Message ---
--- Begin Message ---
Source: varnish
Source-Version: 7.1.0-4
Done: Stig Sandbeck Mathisen 

We believe that the bug you reported is fixed in the latest version of
varnish, 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.
Stig Sandbeck Mathisen  (supplier of updated varnish 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, 12 Jun 2022 19:33:56 +0200
Binary: libvarnishapi-dev libvarnishapi3 libvarnishapi3-dbgsym varnish 
varnish-dbgsym varnish-doc
Source: varnish
Architecture: all amd64 source
Version: 7.1.0-4
Distribution: experimental
Urgency: medium
Maintainer: Varnish Package Maintainers 
Changed-By: Stig Sandbeck Mathisen 
Closes: 1010582
Description: 
 libvarnishapi-dev - development files for Varnish
 libvarnishapi3 - shared libraries for Varnish
 varnish- state of the art, high-performance web accelerator
 varnish-doc - documentation for Varnish Cache
Changes:
 varnish (7.1.0-4) experimental; urgency=medium
 .
   * New upstream release (Closes: #1010582)
   * Bump soname for libvarnishapi
   * Depend on libpcre2-dev instead of libpcre3-dev
   * Drop superflous file patterns from debian/copyright
   * Update lintian overrides for embedded, modified zlib
   * Update lintian overrides for compiled javascript included in the
 documentation source tarball
Checksums-Sha1: 
 5251d9f96cd1816467822584727e97321523eb5b 2519 varnish_7.1.0-4.dsc
 f678f15f3b4eab0a5663e3878955a72bf4fe0957 3787588 varnish_7.1.0.orig.tar.gz
 b9143c31a74e98b7cdf5b293c83130e24172b759 24044 varnish_7.1.0-4.debian.tar.xz
 ba3f7a102b713463afbbbed5ab66fdf596124570 182820 
libvarnishapi-dev_7.1.0-4_amd64.deb
 055ca6ac7b0a6f581966bd4657b77b928b5cb480 233692 
libvarnishapi3-dbgsym_7.1.0-4_amd64.deb
 a680c4fa49820f7e9a12e38473b53755b73e479b 177388 
libvarnishapi3_7.1.0-4_amd64.deb
 53b6b5f9555277cc8a876b6317e97b501cc69825 2055576 
varnish-dbgsym_7.1.0-4_amd64.deb
 fa5fb06d7a43680de3b7cb3b973cddd569bd 818120 varnish-doc_7.1.0-4_all.deb
 041e0d9c6a63391e9986db5cbd2133fc7628b984 10698 varnish_7.1.0-4_amd64.buildinfo
 9747bd95e67d22f5f49b769434208c3d75f12a82 1047524 varnish_7.1.0-4_amd64.deb
Checksums-Sha256: 
 45cb65838a38d2343652dac7b68bced963b318dad786f9859063abd43bef69ca 2519 
varnish_7.1.0-4.dsc
 f54ab88685667664e5b3c39eb56ac8c624b6c1093436a7f8c555491144c69eba 3787588 
varnish_7.1.0.orig.tar.gz
 dacfd3637989e3e04fbc2cb8db0fd7f6d02b03aa903116f96f6986f48227c6e4 24044 
varnish_7.1.0-4.debian.tar.xz
 183ae566171c6270d201a254c191553b2acb406150cbe2357ff9f95110580021 182820 
libvarnishapi-dev_7.1.0-4_amd64.deb
 691bd4251fb5b37822017a3b91231c842983833bbca204b6e11cd8a9cac4e26e 233692 
libvarnishapi3-dbgsym_7.1.0-4_amd64.deb
 92381d123dd7d4897a52007dc3cc5876379cfeb62099b888d0f7bbbe7352faa2 177388 
libvarnishapi3_7.1.0-4_amd64.deb
 099913621d22507ccfd6894ee1809b4f0ced0f59df1052278ab11c65047a9a9c 2055576 
varnish-dbgsym_7.1.0-4_amd64.deb
 bc3380a42109b9e740df61184958f0aea820ec6eefa7c4499e2297a559ac7ff6 818120 
varnish-doc_7.1.0-4_all.deb
 bb47a629a24d1fc893678c2fb90eb411d6e3b6e019665c7e915281f7f2d2cb61 10698 
varnish_7.1.0-4_amd64.buildinfo
 e00ee2dff55599ebc8725b9e84e77a1337e884828b99af1fb639747e124c101a 1047524 
varnish_7.1.0-4_amd64.deb
Files: 
 078528839b70844c633c38209686b941 2519 web optional varnish_7.1.0-4.dsc
 785f9b70632b25deab5b0f92cb7b4d1e 3787588 

Processed: Re: forcemerge lein test bug

[Debian Bug Tracking System]

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

> forcemerge 1012824 1011766 1011854 1011827 1011791 1011785 1011840 1011797 
> 1011821 1011882 1011882 1011853 1011819 1011901 1011859 1011822 1011842 
> 1011874 1011893 1011813 1011880 1011788 1011832 1011835 1011841 1011801 
> 1011862 1011870 1011789 1011799 1011829 1011969
Bug #1012824 [leiningen] leiningen: "lein test" requires unavailable hard-coded 
librepl-clojure version 0.6.0
Bug #1012824 [leiningen] leiningen: "lein test" requires unavailable hard-coded 
librepl-clojure version 0.6.0
Added tag(s) bookworm, sid, and ftbfs.
Bug #1011788 [leiningen] ring-codec-clojure: FTBFS: Cannot access clojars 
(https://repo.clojars.org/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Severity set to 'important' from 'serious'
Marked as found in versions leiningen-clojure/2.9.1-5.
Added tag(s) patch.
Bug #1011842 [leiningen] puppetlabs-i18n-clojure: FTBFS: Cannot access clojars 
(https://repo.clojars.org/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Severity set to 'important' from 'serious'
Marked as found in versions leiningen-clojure/2.9.1-5.
Added tag(s) patch.
Bug #1011840 [leiningen] crypto-equality-clojure: FTBFS: Cannot access clojars 
(https://repo.clojars.org/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Severity set to 'important' from 'serious'
Marked as found in versions leiningen-clojure/2.9.1-5.
Added tag(s) patch.
Bug #1011822 [leiningen] puppetlabs-http-client-clojure: FTBFS: Cannot access 
clojars (https://repo.clojars.org/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Severity set to 'important' from 'serious'
Marked as found in versions leiningen-clojure/2.9.1-5.
Added tag(s) patch.
Bug #1011766 [leiningen] bidi-clojure: FTBFS: Cannot access central 
(https://repo1.maven.org/maven2/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Severity set to 'important' from 'serious'
Marked as found in versions leiningen-clojure/2.9.1-5.
Added tag(s) patch.
Bug #1011874 [leiningen] puppetlabs-ring-middleware-clojure: FTBFS: Cannot 
access clojars (https://repo.clojars.org/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Severity set to 'important' from 'serious'
Marked as found in versions leiningen-clojure/2.9.1-5.
Added tag(s) patch.
Bug #1011785 [leiningen] core-match-clojure: FTBFS: Cannot access clojars 
(https://repo.clojars.org/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Severity set to 'important' from 'serious'
Marked as found in versions leiningen-clojure/2.9.1-5.
Added tag(s) patch.
Bug #1011835 [leiningen] ssl-utils-clojure: FTBFS: Cannot access clojars 
(https://repo.clojars.org/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Severity set to 'important' from 'serious'
Marked as found in versions leiningen-clojure/2.9.1-5.
Added tag(s) patch.
Bug #1011799 [leiningen] url-clojure: FTBFS: Cannot access clojars 
(https://repo.clojars.org/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Severity set to 'important' from 'serious'
Marked as found in versions leiningen-clojure/2.9.1-5.
Added tag(s) patch.
Bug #1011789 [leiningen] trapperkeeper-webserver-jetty9-clojure: FTBFS: Cannot 
access clojars (https://repo.clojars.org/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Severity set to 'important' from 'serious'
Marked as found in versions leiningen-clojure/2.9.1-5.
Added tag(s) patch.
Bug #1011821 [leiningen] nrepl-clojure: FTBFS: Cannot access clojars 
(https://repo.clojars.org/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Severity set to 'important' from 'serious'
Marked as found in versions leiningen-clojure/2.9.1-5.
Added tag(s) patch.
Bug #1011827 [leiningen] clj-time-clojure: FTBFS: Cannot access clojars 
(https://repo.clojars.org/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Severity set to 'important' from 'serious'
Marked as found in versions leiningen-clojure/2.9.1-5.
Added tag(s) patch.
Bug #1011882 [leiningen] ordered-clojure: FTBFS: Cannot access clojars 
(https://repo.clojars.org/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Severity set to 'important' from 'serious'
Marked as found in versions leiningen-clojure/2.9.1-5.
Added tag(s) patch.
Bug #1011841 [leiningen] trapperkeeper-authorization-clojure: FTBFS: Cannot 
access clojars (https://repo.clojars.org/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Severity set to 'important' from 

Processed: reassign bugs to lein

[Debian Bug Tracking System]

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

> reassign 1011766 leiningen
Bug #1011766 [src:bidi-clojure] bidi-clojure: FTBFS: Cannot access central 
(https://repo1.maven.org/maven2/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Bug reassigned from package 'src:bidi-clojure' to 'leiningen'.
No longer marked as found in versions bidi-clojure/2.1.6-1.
Ignoring request to alter fixed versions of bug #1011766 to the same values 
previously set
> reassign 1011854 leiningen
Bug #1011854 [src:clj-digest-clojure] clj-digest-clojure: FTBFS: Cannot access 
clojars (https://repo.clojars.org/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Bug reassigned from package 'src:clj-digest-clojure' to 'leiningen'.
No longer marked as found in versions clj-digest-clojure/1.4.9+dfsg-1.
Ignoring request to alter fixed versions of bug #1011854 to the same values 
previously set
> reassign 1011827 leiningen
Bug #1011827 [src:clj-time-clojure] clj-time-clojure: FTBFS: Cannot access 
clojars (https://repo.clojars.org/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Bug reassigned from package 'src:clj-time-clojure' to 'leiningen'.
No longer marked as found in versions clj-time-clojure/0.15.2-1.
Ignoring request to alter fixed versions of bug #1011827 to the same values 
previously set
> reassign 1011791 leiningen
Bug #1011791 [src:core-async-clojure] core-async-clojure: FTBFS: Cannot access 
clojars (https://repo.clojars.org/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Bug reassigned from package 'src:core-async-clojure' to 'leiningen'.
No longer marked as found in versions core-async-clojure/1.3.610-5.
Ignoring request to alter fixed versions of bug #1011791 to the same values 
previously set
> reassign 1011785 leiningen
Bug #1011785 [src:core-match-clojure] core-match-clojure: FTBFS: Cannot access 
clojars (https://repo.clojars.org/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Bug reassigned from package 'src:core-match-clojure' to 'leiningen'.
No longer marked as found in versions core-match-clojure/1.0.0-1.
Ignoring request to alter fixed versions of bug #1011785 to the same values 
previously set
> reassign 1011840 leiningen
Bug #1011840 [src:crypto-equality-clojure] crypto-equality-clojure: FTBFS: 
Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Bug reassigned from package 'src:crypto-equality-clojure' to 'leiningen'.
No longer marked as found in versions crypto-equality-clojure/1.0.0-2.
Ignoring request to alter fixed versions of bug #1011840 to the same values 
previously set
> reassign 1011797 leiningen
Bug #1011797 [src:kitchensink-clojure] kitchensink-clojure: FTBFS: Cannot 
access clojars (https://repo.clojars.org/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Bug reassigned from package 'src:kitchensink-clojure' to 'leiningen'.
No longer marked as found in versions kitchensink-clojure/3.1.1-3.
Ignoring request to alter fixed versions of bug #1011797 to the same values 
previously set
> reassign 1011821 leiningen
Bug #1011821 [src:nrepl-clojure] nrepl-clojure: FTBFS: Cannot access clojars 
(https://repo.clojars.org/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Bug reassigned from package 'src:nrepl-clojure' to 'leiningen'.
No longer marked as found in versions nrepl-clojure/0.9.0-1.
Ignoring request to alter fixed versions of bug #1011821 to the same values 
previously set
> reassign 1011882 leiningen
Bug #1011882 [src:ordered-clojure] ordered-clojure: FTBFS: Cannot access 
clojars (https://repo.clojars.org/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Bug reassigned from package 'src:ordered-clojure' to 'leiningen'.
No longer marked as found in versions ordered-clojure/1.5.9-3.
Ignoring request to alter fixed versions of bug #1011882 to the same values 
previously set
> reassign 1011882 leiningen
Bug #1011882 [leiningen] ordered-clojure: FTBFS: Cannot access clojars 
(https://repo.clojars.org/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Ignoring request to reassign bug #1011882 to the same package
> reassign 1011853 leiningen
Bug #1011853 [src:pathetic-clojure] pathetic-clojure: FTBFS: Cannot access 
clojars (https://repo.clojars.org/) in offline mode and the artifact 
nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Bug reassigned from package 'src:pathetic-clojure' to 'leiningen'.
No longer marked as found in versions pathetic-clojure/0.5.1-2.
Ignoring request to alter fixed versions of bug #1011853 to the same values 
previously set
> reassign 

Processed (with 1 error): forcemerge lein test bug

[Debian Bug Tracking System]

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

> forcemerge 1012824 1011766 1011854 1011827 1011791 1011785 1011840 1011797 
> 1011821 1011882 1011882 1011853 1011819 1011901 1011859 1011822 1011842 
> 1011874 1011893 1011813 1011880 1011788 1011832 1011835 1011841 1011801 
> 1011862 1011870 1011789 1011799 1011829 1011969
Bug #1012824 [leiningen] leiningen: "lein test" requires unavailable hard-coded 
librepl-clojure version 0.6.0
Unable to merge bugs because:
package of #1011766 is 'src:bidi-clojure' not 'leiningen'
package of #1011801 is 'src:trapperkeeper-filesystem-watcher-clojure' not 
'leiningen'
package of #1011870 is 'src:trapperkeeper-status-clojure' not 'leiningen'
package of #1011829 is 'src:useful-clojure' not 'leiningen'
package of #1011841 is 'src:trapperkeeper-authorization-clojure' not 'leiningen'
package of #1011827 is 'src:clj-time-clojure' not 'leiningen'
package of #1011854 is 'src:clj-digest-clojure' not 'leiningen'
package of #1011813 is 'src:riddley-clojure' not 'leiningen'
package of #1011853 is 'src:pathetic-clojure' not 'leiningen'
package of #1011893 is 'src:rbac-client-clojure' not 'leiningen'
package of #1011901 is 'src:prismatic-plumbing-clojure' not 'leiningen'
package of #1011822 is 'src:puppetlabs-http-client-clojure' not 'leiningen'
package of #1011791 is 'src:core-async-clojure' not 'leiningen'
package of #1011835 is 'src:ssl-utils-clojure' not 'leiningen'
package of #1011789 is 'src:trapperkeeper-webserver-jetty9-clojure' not 
'leiningen'
package of #1011788 is 'src:ring-codec-clojure' not 'leiningen'
package of #1011832 is 'src:shell-utils-clojure' not 'leiningen'
package of #1011840 is 'src:crypto-equality-clojure' not 'leiningen'
package of #1011882 is 'src:ordered-clojure' not 'leiningen'
package of #1011862 is 'src:trapperkeeper-metrics-clojure' not 'leiningen'
package of #1011785 is 'src:core-match-clojure' not 'leiningen'
package of #1011874 is 'src:puppetlabs-ring-middleware-clojure' not 'leiningen'
package of #1011797 is 'src:kitchensink-clojure' not 'leiningen'
package of #1011842 is 'src:puppetlabs-i18n-clojure' not 'leiningen'
package of #1011880 is 'src:ring-basic-authentication-clojure' not 'leiningen'
package of #1011799 is 'src:url-clojure' not 'leiningen'
package of #1011969 is 'src:cljx-clojure' not 'leiningen'
package of #1011821 is 'src:nrepl-clojure' not 'leiningen'
package of #1011819 is 'src:potemkin-clojure' not 'leiningen'
package of #1011859 is 'src:prismatic-schema-clojure' not 'leiningen'
Failed to forcibly merge 1012824: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1011766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011766
1011785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011785
1011788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011788
1011789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011789
1011791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011791
1011797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011797
1011799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011799
1011801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011801
1011813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011813
1011819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011819
1011821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011821
1011822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011822
1011827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011827
1011829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011829
1011832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011832
1011835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011835
1011840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011840
1011841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011841
1011842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011842
1011853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011853
1011854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011854
1011859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011859
1011862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011862
1011870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011870
1011874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011874
1011880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011880
1011882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011882
1011893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011893
1011901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011901
1011969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011969
1012824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1011800: marked as done (leiningen-clojure: FTBFS: Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the

[Debian Bug Tracking System]

Your message dated Tue, 14 Jun 2022 17:37:07 -0400
with message-id <573bb877-25c3-cc53-ea9f-8ea95abd7...@debian.org>
and subject line Re: Bug#1011800: leiningen-clojure: FTBFS: Caused by: 
org.eclipse.aether.transfer.ArtifactNotFoundException: Cannot access central 
(https://repo1.maven.org/maven2/) in offline mode and the artifact 
com.cemerick:pomegranate:jar:debian has not been downloaded from it before.
has caused the Debian Bug report #1011800,
regarding leiningen-clojure: FTBFS: Caused by: 
org.eclipse.aether.transfer.ArtifactNotFoundException: Cannot access central 
(https://repo1.maven.org/maven2/) in offline mode and the artifact 
com.cemerick:pomegranate:jar:debian has not been downloaded from it before.
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.)


-- 
1011800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: leiningen-clojure
Version: 2.9.1-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd leiningen-core && lein bootstrap
> Leiningen's classpath: :/usr/share/java/leiningen-2.9.1.jar
> Applying task [with-profile base do install, classpath .lein-bootstrap] to []
> Applying task do to (install, classpath .lein-bootstrap)
> Applying task install to []
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact com.cemerick:pomegranate:jar:debian has not been downloaded from 
> it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact com.cemerick:pomegranate:jar:debian has not been downloaded from it 
> before.
> This could be due to a typo in :dependencies, file system permissions, or 
> network issues.
> If you are behind a proxy, try setting the 'http_proxy' environment variable.
> Error encountered performing task 'do' with profile(s): 'base'
> clojure.lang.ExceptionInfo: Could not resolve dependencies {:suppress-msg 
> true, :exit-code 1}
>   at 
> leiningen.core.classpath$get_dependencies_STAR_.invokeStatic(classpath.clj:312)
>   at 
> leiningen.core.classpath$get_dependencies_STAR_.invoke(classpath.clj:266)
>   at clojure.lang.AFn.applyToHelper(AFn.java:165)
>   at clojure.lang.AFn.applyTo(AFn.java:144)
>   at clojure.core$apply.invokeStatic(core.clj:665)
>   at clojure.core$memoize$fn__6877.doInvoke(core.clj:6353)
>   at clojure.lang.RestFn.invoke(RestFn.java:457)
>   at 
> leiningen.core.classpath$get_dependencies$fn__6444.invoke(classpath.clj:333)
>   at 
> leiningen.core.classpath$get_dependencies.invokeStatic(classpath.clj:331)
>   at leiningen.core.classpath$get_dependencies.doInvoke(classpath.clj:325)
>   at clojure.lang.RestFn.invoke(RestFn.java:445)
>   at clojure.lang.AFn.applyToHelper(AFn.java:160)
>   at clojure.lang.RestFn.applyTo(RestFn.java:132)
>   at clojure.core$apply.invokeStatic(core.clj:671)
>   at clojure.core$apply.invoke(core.clj:660)
>   at 
> leiningen.core.classpath$resolve_managed_dependencies.invokeStatic(classpath.clj:444)
>   at 
> leiningen.core.classpath$resolve_managed_dependencies.doInvoke(classpath.clj:431)
>   at clojure.lang.RestFn.invoke(RestFn.java:445)
>   at leiningen.core.eval$prep.invokeStatic(eval.clj:85)
>   at leiningen.core.eval$prep.invoke(eval.clj:73)
>   at leiningen.jar$build_jar.invokeStatic(jar.clj:286)
>   at leiningen.jar$build_jar.invoke(jar.clj:283)
>   at leiningen.jar$main_jar.invokeStatic(jar.clj:295)
>   at leiningen.jar$main_jar.invoke(jar.clj:291)
>   at leiningen.jar$jar.invokeStatic(jar.clj:346)
>   at leiningen.jar$jar.invoke(jar.clj:328)
>   at leiningen.jar$jar.invokeStatic(jar.clj:348)
>   at leiningen.jar$jar.invoke(jar.clj:328)
>   at leiningen.install$install.invokeStatic(install.clj:21)
>   at leiningen.install$install.invoke(install.clj:12)
>   at clojure.lang.AFn.applyToHelper(AFn.java:154)
>   at clojure.lang.AFn.applyTo(AFn.java:144)
>   at clojure.lang.Var.applyTo(Var.java:705)
>   at clojure.core$apply.invokeStatic(core.clj:667)
>   at clojure.core$apply.invoke(core.clj:660)
>   at leiningen.core.main$partial_task$fn__6931.doInvoke(main.clj:284)
>   at clojure.lang.RestFn.invoke(RestFn.java:410)
>   at clojure.lang.AFn.applyToHelper(AFn.java:154)
>   at 

Processed: Re: Bug#1012816: reportbug: Failed to insert module 'firewire_sbp2': Key was rejected by service

[Debian Bug Tracking System]

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

> reassign 1012816 src:linux-signed-i386
Bug #1012816 [src:linux] reportbug: Failed to insert module 'firewire_sbp2': 
Key was rejected by service
Bug reassigned from package 'src:linux' to 'src:linux-signed-i386'.
No longer marked as found in versions linux/5.10.120-1.
Ignoring request to alter fixed versions of bug #1012816 to the same values 
previously set
> merge 1012816 1012741
Bug #1012816 [src:linux-signed-i386] reportbug: Failed to insert module 
'firewire_sbp2': Key was rejected by service
Bug #1012816 [src:linux-signed-i386] reportbug: Failed to insert module 
'firewire_sbp2': Key was rejected by service
Marked as found in versions linux-signed-i386/5.10.120+1.
Added tag(s) confirmed.
Bug #1012741 [src:linux-signed-i386] modprobe: ERROR: could not insert 
'crc_itu_t': Key was rejected by service
Merged 1012741 1012816
>
End of message, stopping processing here.

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

Processed: tagging 1010582

[Debian Bug Tracking System]

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

> tags 1010582 + confirmed pending
Bug #1010582 [varnish] varnish: New upstream release 7.1.0
Added tag(s) confirmed and pending.
> thanks
Stopping processing here.

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

Bug#1012821: guzzle: CVE-2022-31042 CVE-2022-31043

[Salvatore Bonaccorso]

Source: guzzle
Version: 7.4.1-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for guzzle.

CVE-2022-31042[0]:
| Guzzle is an open source PHP HTTP client. In affected versions the
| `Cookie` headers on requests are sensitive information. On making a
| request using the `https` scheme to a server which responds with a
| redirect to a URI with the `http` scheme, or on making a request to a
| server which responds with a redirect to a a URI to a different host,
| we should not forward the `Cookie` header on. Prior to this fix, only
| cookies that were managed by our cookie middleware would be safely
| removed, and any `Cookie` header manually added to the initial request
| would not be stripped. We now always strip it, and allow the cookie
| middleware to re-add any cookies that it deems should be there.
| Affected Guzzle 7 users should upgrade to Guzzle 7.4.4 as soon as
| possible. Affected users using any earlier series of Guzzle should
| upgrade to Guzzle 6.5.7 or 7.4.4. Users unable to upgrade may consider
| an alternative approach to use your own redirect middleware, rather
| than ours. If you do not require or expect redirects to be followed,
| one should simply disable redirects all together.


CVE-2022-31043[1]:
| Guzzle is an open source PHP HTTP client. In affected versions
| `Authorization` headers on requests are sensitive information. On
| making a request using the `https` scheme to a server which responds
| with a redirect to a URI with the `http` scheme, we should not forward
| the `Authorization` header on. This is much the same as to how we
| don't forward on the header if the host changes. Prior to this fix,
| `https` to `http` downgrades did not result in the `Authorization`
| header being removed, only changes to the host. Affected Guzzle 7
| users should upgrade to Guzzle 7.4.4 as soon as possible. Affected
| users using any earlier series of Guzzle should upgrade to Guzzle
| 6.5.7 or 7.4.4. Users unable to upgrade may consider an alternative
| approach which would be to use their own redirect middleware.
| Alternately users may simply disable redirects all together if
| redirects are not expected or required.


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-31042
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31042
https://github.com/guzzle/guzzle/security/advisories/GHSA-f2wf-25xc-69c9
[1] https://security-tracker.debian.org/tracker/CVE-2022-31043
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31043
https://github.com/guzzle/guzzle/security/advisories/GHSA-w248-ffj2-4v5q
[2] 
https://github.com/guzzle/guzzle/commit/e3ff079b22820c2029d4c2a87796b6a0b8716ad8

Regards,
Salvatore

Processed: notfound 1011000 in 1.2-0.2

[Debian Bug Tracking System]

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

> notfound 1011000 1.2-0.2
Bug #1011000 {Done: gregor herrmann } [python3-pymetar] 
python3-pymetar: fails with default url and oepnssl 3
No longer marked as found in versions python-pymetar/1.2-0.2.
> thanks
Stopping processing here.

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

Bug#999174: marked as done (gtkpool: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jun 2022 19:19:36 +
with message-id 
and subject line Bug#999174: fixed in gtkpool 0.5.0-9.1
has caused the Debian Bug report #999174,
regarding gtkpool: missing required debian/rules targets build-arch and/or 
build-indep
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.)


-- 
999174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtkpool
Version: 0.5.0-9
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: gtkpool
Source-Version: 0.5.0-9.1
Done: Ying-Chun Liu (PaulLiu) 

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

Debian distribution maintenance software
pp.
Ying-Chun Liu (PaulLiu)  (supplier of updated gtkpool 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 25 May 2022 10:13:20 +0800
Source: gtkpool
Architecture: source
Version: 0.5.0-9.1
Distribution: unstable
Urgency: low
Maintainer: Josip Rodin 
Changed-By: Ying-Chun Liu (PaulLiu) 
Closes: 930831 965575 999174
Changes:
 gtkpool (0.5.0-9.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Migrate to DebSrc3.0
   * Port to debhelper version 13 (Closes: #965575)
 - Adjust debian/rules targets (Closes: #999174, #930831)
 - Add gtkpool.manpages to install manpages
 - Add gtkpool.docs to install docs
Checksums-Sha1:
 b963d5d781c47ae2b90b5dd7b1f3f9f8fc08bd7a 1746 gtkpool_0.5.0-9.1.dsc
 6db43e2068045f34395ec30a62ecfefadd9b84be 14116 gtkpool_0.5.0-9.1.debian.tar.xz
 544e07ae1f40ddc1e4ded40cd12bae1d5a10d9b5 11757 
gtkpool_0.5.0-9.1_source.buildinfo
Checksums-Sha256:
 dc81d270296102118371ddaed7dde1977d9587f788c8885e9034770b102a9a47 1746 
gtkpool_0.5.0-9.1.dsc
 f5d365cc7ef28b308ffcbbc415ff46dbf3d6505caad298980996bfdce72698f2 14116 
gtkpool_0.5.0-9.1.debian.tar.xz
 b9ed5c7a26649e05f6d53583d8234eda44d23c30ad187cfd6bd44dfab212fca9 11757 
gtkpool_0.5.0-9.1_source.buildinfo
Files:
 2ee8efddb76d83b9746d2788a9612e35 1746 games optional gtkpool_0.5.0-9.1.dsc
 7b68507f696965b555c7703cbd25c239 14116 games optional 
gtkpool_0.5.0-9.1.debian.tar.xz
 9398b577e4fb91632c3e6e1be8a326e9 11757 games optional 
gtkpool_0.5.0-9.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmKbpHMTHHBhdWxsaXVA
ZGViaWFuLm9yZwAKCRBEFz+hPQWIiLYaEADAK8PG7znoxif2Dxcenwp909IMhZzX
Y6qNPIfgBMWDURCnG+zwK9b7PRJY5UbXzOB+x/3EZO7K3k790GqbAw6dsOeJ4R9s
4HZn0hecgkcqPUkMC5seaOVCeh0Qd0ZdxnHpbY7VipboEGxioWJ/L2a/uVk3eypf
+7D33GcO+3vMd92bp+ihPV2eMuch+hJn5S+hN7wYY8LLVC51GvxB1JcO7/4oZTPL
cql4iIHYulb/59jTtg5dwqn4Sc5gfx3+spj+EpWAXuTTpMYss2yrT+SXs2AM8Z4G
vj4qAfFlPEwOHjD7tvOeSkZnakb4txFE0yYR376PIKfPuXed1UxtQIiy00F/GRm5
zAGaqWkWWrgb7WpvVSe1DGS4Oqbvcrp2wQk93ACgM2tH/mqVVsYmPp6X2rMbMRjD
08RSreo5A7F4bEDHxpZ39C8qJYTApAJXZ+MK7s6FuBWkk3ZPt0R9uxx8LvpPLtvf
5P1cmSPFwKPN+0yVe/PcGINfAnzMffkHc75NEY5I9B1hrMVxiHZYrO2DmAR3F1wm
zCsJ6Q/EsqGHj4jkqCKqksAHYQYsprO+iIjaopF6vN7It6lMFd6tLi7lE8B5uYus
1CXiMpQTp3ldrhxKbFlT01VayfBcoRBxvHsg1es3BOM7ZILhAheXC3sVD44E0dZY
afRtYiJQu72/9A==
=ALCJ
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Tue, 14 Jun 2022 19:19:36 +
with message-id 
and subject line Bug#965575: fixed in gtkpool 0.5.0-9.1
has caused the Debian Bug report #965575,
regarding gtkpool: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
965575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtkpool
Version: 0.5.0-9
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package gtkpool uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: gtkpool
Source-Version: 0.5.0-9.1
Done: Ying-Chun Liu (PaulLiu) 

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

Debian distribution maintenance software
pp.
Ying-Chun Liu (PaulLiu)  (supplier of updated gtkpool 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 25 May 2022 10:13:20 +0800
Source: gtkpool
Architecture: source
Version: 0.5.0-9.1
Distribution: unstable
Urgency: low
Maintainer: Josip Rodin 
Changed-By: Ying-Chun Liu (PaulLiu) 
Closes: 930831 965575 999174
Changes:
 gtkpool (0.5.0-9.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Migrate to DebSrc3.0
   * Port to debhelper version 13 (Closes: #965575)
 - Adjust debian/rules targets (Closes: #999174, #930831)
 - Add gtkpool.manpages to install manpages
 - Add gtkpool.docs to install docs
Checksums-Sha1:
 b963d5d781c47ae2b90b5dd7b1f3f9f8fc08bd7a 1746 gtkpool_0.5.0-9.1.dsc
 6db43e2068045f34395ec30a62ecfefadd9b84be 14116 gtkpool_0.5.0-9.1.debian.tar.xz
 544e07ae1f40ddc1e4ded40cd12bae1d5a10d9b5 11757 
gtkpool_0.5.0-9.1_source.buildinfo
Checksums-Sha256:
 dc81d270296102118371ddaed7dde1977d9587f788c8885e9034770b102a9a47 1746 
gtkpool_0.5.0-9.1.dsc
 f5d365cc7ef28b308ffcbbc415ff46dbf3d6505caad298980996bfdce72698f2 14116 
gtkpool_0.5.0-9.1.debian.tar.xz
 b9ed5c7a26649e05f6d53583d8234eda44d23c30ad187cfd6bd44dfab212fca9 11757 
gtkpool_0.5.0-9.1_source.buildinfo
Files:
 2ee8efddb76d83b9746d2788a9612e35 1746 games optional gtkpool_0.5.0-9.1.dsc
 7b68507f696965b555c7703cbd25c239 14116 games optional 
gtkpool_0.5.0-9.1.debian.tar.xz
 9398b577e4fb91632c3e6e1be8a326e9 11757 games optional 
gtkpool_0.5.0-9.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmKbpHMTHHBhdWxsaXVA
ZGViaWFuLm9yZwAKCRBEFz+hPQWIiLYaEADAK8PG7znoxif2Dxcenwp909IMhZzX
Y6qNPIfgBMWDURCnG+zwK9b7PRJY5UbXzOB+x/3EZO7K3k790GqbAw6dsOeJ4R9s
4HZn0hecgkcqPUkMC5seaOVCeh0Qd0ZdxnHpbY7VipboEGxioWJ/L2a/uVk3eypf
+7D33GcO+3vMd92bp+ihPV2eMuch+hJn5S+hN7wYY8LLVC51GvxB1JcO7/4oZTPL
cql4iIHYulb/59jTtg5dwqn4Sc5gfx3+spj+EpWAXuTTpMYss2yrT+SXs2AM8Z4G
vj4qAfFlPEwOHjD7tvOeSkZnakb4txFE0yYR376PIKfPuXed1UxtQIiy00F/GRm5
zAGaqWkWWrgb7WpvVSe1DGS4Oqbvcrp2wQk93ACgM2tH/mqVVsYmPp6X2rMbMRjD
08RSreo5A7F4bEDHxpZ39C8qJYTApAJXZ+MK7s6FuBWkk3ZPt0R9uxx8LvpPLtvf
5P1cmSPFwKPN+0yVe/PcGINfAnzMffkHc75NEY5I9B1hrMVxiHZYrO2DmAR3F1wm

Processed: closing 1011750

[Debian Bug Tracking System]

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

> close 1011750 11.10.2+dfsg-1
Bug #1011750 [src:gazebo] gazebo: FTBFS with onetbb/2021.5.0-9 in experimental
Marked as fixed in versions gazebo/11.10.2+dfsg-1.
Bug #1011750 [src:gazebo] gazebo: FTBFS with onetbb/2021.5.0-9 in experimental
Marked Bug as done
> thanks
Stopping processing here.

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

Processed (with 2 errors): Re: Bug#1012816: reportbug: Failed to insert module 'firewire_sbp2': Key was rejected by service

[Debian Bug Tracking System]

Processing control commands:

> reassign reassign -1 src:linux-signed-i386
Unknown command or malformed arguments to command.

> severity -1 serious
Bug #1012816 [src:linux] reportbug: Failed to insert module 'firewire_sbp2': 
Key was rejected by service
Severity set to 'serious' from 'normal'
> merge -1 1012741
Bug #1012816 [src:linux] reportbug: Failed to insert module 'firewire_sbp2': 
Key was rejected by service
Unable to merge bugs because:
package of #1012741 is 'src:linux-signed-i386' not 'src:linux'
Failed to merge 1012816: Did not alter merged bugs.


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

Bug#1012263: marked as done (curl: Multi-line header support is broken)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jun 2022 17:33:58 +
with message-id 
and subject line Bug#1012263: fixed in curl 7.83.1-2
has caused the Debian Bug report #1012263,
regarding curl: Multi-line header support is broken
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.)


-- 
1012263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: curl
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch

Dear Maintainer,

In version 7.83.1, the support for multi-line headers is broken.
This causes autopkgtest regressions in python-tornado:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012224

In Ubuntu, the attached patch was applied to achieve the following:

  * Apply upstream patch to fix multi-line header support (LP: #1976619)

Thanks for considering the patch.


-- System Information:
Debian Release: bookworm/sid
  APT prefers jammy-updates
  APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'), 
(100, 'jammy-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.0-33-generic (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru 
curl-7.83.1/debian/patches/12-http-restore-header-folding-behavior.patch 
curl-7.83.1/debian/patches/12-http-restore-header-folding-behavior.patch
--- curl-7.83.1/debian/patches/12-http-restore-header-folding-behavior.patch
1970-01-01 01:00:00.0 +0100
+++ curl-7.83.1/debian/patches/12-http-restore-header-folding-behavior.patch
2022-06-02 13:44:50.0 +0200
@@ -0,0 +1,268 @@
+Description: restore header folding behavior
+ Folded header lines will now get passed through like before. The headers
+ API is adapted and will get and provide the content "un-folded".
+ Added test 1274 and extended test 1940 to verify.
+Origin: upstream, https://github.com/curl/curl/pull/8899
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1976619
+Applied-Upstream: 
https://github.com/curl/curl/commit/c9b60f005358a364cbcddbebd8d12593acffdd84
+Last-Update: 2022-06-02
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+Index: b/docs/libcurl/curl_easy_header.3
+===
+--- a/docs/libcurl/curl_easy_header.3  2022-06-02 13:39:23.698800691 +0200
 b/docs/libcurl/curl_easy_header.3  2022-06-02 13:39:23.694800445 +0200
+@@ -95,7 +95,9 @@
+ 
+ The data \fBvalue\fP field points to, comes exactly as delivered over the
+ network but with leading and trailing whitespace and newlines stripped
+-off. The `value` data is nul-terminated.
++off. The `value` data is nul-terminated. For legacy HTTP/1 "folded headers",
++this API provides the full single value in an unfolded manner with a single
++whitespace between the lines.
+ 
+ \fBamount\fP is how many headers using this name that exist, within the origin
+ and request scope asked for.
+Index: b/lib/headers.c
+===
+--- a/lib/headers.c2022-06-02 13:39:23.698800691 +0200
 b/lib/headers.c2022-06-02 13:39:23.694800445 +0200
+@@ -216,6 +216,54 @@
+   return CURLE_OK;
+ }
+ 
++static CURLcode append_value(struct Curl_easy *data, const char *value,
++ size_t vlen)  /* length of the incoming header */
++{
++  struct Curl_header_store *hs;
++  struct Curl_header_store *newhs;
++  size_t olen; /* length of the old value */
++  size_t offset;
++  DEBUGASSERT(data->state.prevhead);
++  hs = data->state.prevhead;
++  olen = strlen(hs->value);
++  offset = hs->value - hs->buffer;
++
++  /* skip all trailing space letters */
++  while(vlen && ISSPACE(value[vlen - 1]))
++vlen--;
++
++  /* save only one leading space */
++  while((vlen > 1) && ISSPACE(value[0]) && ISSPACE(value[1])) {
++vlen--;
++value++;
++  }
++
++  /* since this header block might move in the realloc below, it needs to
++ first be unlinked from the list and then re-added again after the
++ realloc */
++  Curl_llist_remove(>state.httphdrs, >node, NULL);
++
++  newhs = Curl_saferealloc(hs, sizeof(*hs) + vlen + olen + 1);
++  if(!newhs)
++return CURLE_OUT_OF_MEMORY;
++  /* ->name' and ->value point into ->buffer (to keep the header allocation
++ in a single memory 

Bug#1010355: marked as forwarded (CVE-2022-0530: null pointer dereference on invalid UTF-8 input)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jun 2022 19:06:37 +0200
with message-id <98742dec-d0de-d79e-9447-070f83709...@unex.es>
has caused the   report #1010355,
regarding CVE-2022-0530: null pointer dereference on invalid UTF-8 input
to be marked as having been forwarded to the upstream software
author(s) "Steven M. Schweda" 

(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.)


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

Hello.

I received this from the Debian bug system.

There are actually two problems here. One of them is CVE-2022-0530
which is what the reported bug is about. For that I have the proposed 
patch by Enrico Zini which seems to fix the issue.


But the github repository containing the test cases, namely this:

https://github.com/ByteHackr/unzip_poc

contains a test case for yet another problem called CVE-2022-0529
which I would like to fix as well.

This is what I've done to reproduce the bug:

export LC_ALL=C
cd CVE-2022-0529
unzip testcase

and I get this:

Archive:  testcase
warning [testcase]:  303 extra bytes at beginning or within zipfile
  (attempting to process anyway)
error [testcase]:  reported length of central directory is
  -303 bytes too long (Atari STZip zipfile?  J.H.Holm ZIPSPLIT 1.1
  zipfile?).  Compensating...
double free or corruption (out)

Any help will be appreciated.

Thanks.

 Forwarded Message 
Subject: Bug#1010355: CVE-2022-0530: null pointer dereference on invalid 
UTF-8 input

Date: Fri, 29 Apr 2022 13:27:33 +0200
From: Enrico Zini 
Reply-To: Enrico Zini , 1010...@bugs.debian.org
To: Debian Bug Tracking System 

Package: unzip
Version: 6.0-21+deb9u2
Severity: serious
Tags: security upstream patch
X-Debbugs-Cc: Debian Security Team 

Fixed: 6.0-26

Hello,

details are at https://security-tracker.debian.org/tracker/CVE-2022-0530

stretch and buster segfault:

  $ unzip testcase-0530   Archive:  testcase-0530
  warning [testcase-0530]:  16 extra bytes at beginning or within zipfile
(attempting to process anyway)
  error [testcase-0530]:  reported length of central directory is
-16 bytes too long (Atari STZip zipfile?  J.H.Holm ZIPSPLIT 1.1
zipfile?).  Compensating...
  error:  zipfile probably corrupt (segmentation violation)

bullseye errors out without valgrind issues reported:

  $ unzip testcase-0530
  Archive:  testcase-0530
  warning [testcase-0530]:  16 extra bytes at beginning or within zipfile
(attempting to process anyway)
  error [testcase-0530]:  reported length of central directory is
-16 bytes too long (Atari STZip zipfile?  J.H.Holm ZIPSPLIT 1.1
zipfile?).  Compensating...
  mp/zip-unzip-0/7/source/workdir 
/��6a9f01ad36a4ac3b68815bf6f83b3ff_inpu㉴�瑥:  mismatching 
"local" filename 
(mp/zip-unzip-0/7/source/workdir/��6a9f01ad36a4ac3b6881PK^G^HQ�V�^Q),

   continuing with "central" filename version
 skipping: mp/zip-unzip-0/7/source/workdir 
/��6a9f01ad36a4ac3b68815bf6f83b3ff_inpu㉴�瑥  unable to get password


The main issue here seems to be at utf8_to_local_string, defined in
process.c:2606, which doesn't check the result of utf8_to_wide_string
for a NULL value.

I'm attaching a proposed patch that adds the missing error handling.


Enrico


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

Kernel: Linux 5.10.0-13-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE:en

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages unzip depends on:
ii  libbz2-1.0  1.0.8-4
ii  libc6   2.31-13+deb11u3

unzip recommends no packages.

Versions of packages unzip suggests:
ii  zip  3.0-12

-- no debconf informationdiff --git a/fileio.c b/fileio.c
index 6290824..77e4b5f 100644
--- a/fileio.c
+++ b/fileio.c
@@ -2361,6 +2361,9 @@ int do_string(__G__ length, option)   /* return PK-type 
error code */
   /* convert UTF-8 to local character set */
   fn = utf8_to_local_string(G.unipath_filename,
 G.unicode_escape_all);
+  if (fn == NULL)
+return PK_ERR;
+
   /* make sure filename is short enough */
   if (strlen(fn) >= FILNAMSIZ) {
 fn[FILNAMSIZ - 1] = '\0';
diff --git a/process.c b/process.c
index d2a846e..715bc0f 100644
--- a/process.c
+++ b/process.c
@@ -2605,6 +2605,8 @@ char *utf8_to_local_string(utf8_string, escape_all)
   int escape_all;
 {
   zwchar *wide = utf8_to_wide_string(utf8_string);
+  if (wide == NULL)
+return NULL;
   

Bug#1010355: Fwd: Bug#1010355: CVE-2022-0530: null pointer dereference on invalid UTF-8 input

[Santiago Vila]

Hello.

I received this from the Debian bug system.

There are actually two problems here. One of them is CVE-2022-0530
which is what the reported bug is about. For that I have the proposed 
patch by Enrico Zini which seems to fix the issue.


But the github repository containing the test cases, namely this:

https://github.com/ByteHackr/unzip_poc

contains a test case for yet another problem called CVE-2022-0529
which I would like to fix as well.

This is what I've done to reproduce the bug:

export LC_ALL=C
cd CVE-2022-0529
unzip testcase

and I get this:

Archive:  testcase
warning [testcase]:  303 extra bytes at beginning or within zipfile
  (attempting to process anyway)
error [testcase]:  reported length of central directory is
  -303 bytes too long (Atari STZip zipfile?  J.H.Holm ZIPSPLIT 1.1
  zipfile?).  Compensating...
double free or corruption (out)

Any help will be appreciated.

Thanks.

 Forwarded Message 
Subject: Bug#1010355: CVE-2022-0530: null pointer dereference on invalid 
UTF-8 input

Date: Fri, 29 Apr 2022 13:27:33 +0200
From: Enrico Zini 
Reply-To: Enrico Zini , 1010...@bugs.debian.org
To: Debian Bug Tracking System 

Package: unzip
Version: 6.0-21+deb9u2
Severity: serious
Tags: security upstream patch
X-Debbugs-Cc: Debian Security Team 

Fixed: 6.0-26

Hello,

details are at https://security-tracker.debian.org/tracker/CVE-2022-0530

stretch and buster segfault:

  $ unzip testcase-0530   Archive:  testcase-0530
  warning [testcase-0530]:  16 extra bytes at beginning or within zipfile
(attempting to process anyway)
  error [testcase-0530]:  reported length of central directory is
-16 bytes too long (Atari STZip zipfile?  J.H.Holm ZIPSPLIT 1.1
zipfile?).  Compensating...
  error:  zipfile probably corrupt (segmentation violation)

bullseye errors out without valgrind issues reported:

  $ unzip testcase-0530
  Archive:  testcase-0530
  warning [testcase-0530]:  16 extra bytes at beginning or within zipfile
(attempting to process anyway)
  error [testcase-0530]:  reported length of central directory is
-16 bytes too long (Atari STZip zipfile?  J.H.Holm ZIPSPLIT 1.1
zipfile?).  Compensating...
  mp/zip-unzip-0/7/source/workdir 
/��6a9f01ad36a4ac3b68815bf6f83b3ff_inpu㉴�瑥:  mismatching 
"local" filename 
(mp/zip-unzip-0/7/source/workdir/��6a9f01ad36a4ac3b6881PK^G^HQ�V�^Q),

   continuing with "central" filename version
 skipping: mp/zip-unzip-0/7/source/workdir 
/��6a9f01ad36a4ac3b68815bf6f83b3ff_inpu㉴�瑥  unable to get password


The main issue here seems to be at utf8_to_local_string, defined in
process.c:2606, which doesn't check the result of utf8_to_wide_string
for a NULL value.

I'm attaching a proposed patch that adds the missing error handling.


Enrico


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

Kernel: Linux 5.10.0-13-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE:en

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages unzip depends on:
ii  libbz2-1.0  1.0.8-4
ii  libc6   2.31-13+deb11u3

unzip recommends no packages.

Versions of packages unzip suggests:
ii  zip  3.0-12

-- no debconf informationdiff --git a/fileio.c b/fileio.c
index 6290824..77e4b5f 100644
--- a/fileio.c
+++ b/fileio.c
@@ -2361,6 +2361,9 @@ int do_string(__G__ length, option)   /* return PK-type 
error code */
   /* convert UTF-8 to local character set */
   fn = utf8_to_local_string(G.unipath_filename,
 G.unicode_escape_all);
+  if (fn == NULL)
+return PK_ERR;
+
   /* make sure filename is short enough */
   if (strlen(fn) >= FILNAMSIZ) {
 fn[FILNAMSIZ - 1] = '\0';
diff --git a/process.c b/process.c
index d2a846e..715bc0f 100644
--- a/process.c
+++ b/process.c
@@ -2605,6 +2605,8 @@ char *utf8_to_local_string(utf8_string, escape_all)
   int escape_all;
 {
   zwchar *wide = utf8_to_wide_string(utf8_string);
+  if (wide == NULL)
+return NULL;
   char *loc = wide_to_local_string(wide, escape_all);
   free(wide);
   return loc;

Bug#1010355: Wrong upstream

[Santiago Vila]

notforwarded 1010355
thanks

Wrong upstream, this is unzip, not procmail.

Processed: Wrong upstream

[Debian Bug Tracking System]

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

> notforwarded 1010355
Bug #1010355 [unzip] CVE-2022-0530: null pointer dereference on invalid UTF-8 
input
Unset Bug forwarded-to-address
> thanks
Stopping processing here.

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

Bug#1012795: libengine-gost-openssl1.1: Shared library file in /

[Wartan Hachaturow]

This seems to be caused by last NMU :(
libengine-gost-openssl 3.0.1-1, which fixes that (and other) problem, and
also deprecates libengine-gost-openssl1.1, is in the NEW queue.
I will leave the bug open, though, until it installs in the archive, as a
reminder.

Thanks for the report!

On Tue, Jun 14, 2022, 11:39 Cédric Hannotier 
wrote:

> Package: libengine-gost-openssl1.1
> Version: 1.1.0.3-1.1
> Severity: important
>
> Dear Maintainer,
>
> The package is ill-configured and end up
> putting gost.so in the root of the filesystem (/gost.so),
> as shown in [1].
> The source of the issue is [2], which is empty...
>
> [1]
> https://packages.debian.org/sid/amd64/libengine-gost-openssl1.1/filelist
> [2]
> https://sources.debian.org/src/libengine-gost-openssl1.1/1.1.0.3-1.1/debian/rules/#L22
>
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
> 'testing-debug'), (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.17.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
> Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US:en
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages libengine-gost-openssl1.1 depends on:
> ii  libc62.33-7
> ii  libssl3  3.0.3-7
>
> libengine-gost-openssl1.1 recommends no packages.
>
> libengine-gost-openssl1.1 suggests no packages.
>
> --
>
> Cédric Hannotier
>

Bug#1011964: marked as done (ipykernel: autopkgtest regression: ERROR at setup of test_asyncio_interrupt)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jun 2022 15:35:16 +
with message-id 
and subject line Bug#1011964: fixed in ipykernel 6.13.1-2
has caused the Debian Bug report #1011964,
regarding ipykernel: autopkgtest regression: ERROR at setup of 
test_asyncio_interrupt
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.)


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

Source: ipykernel
Version: 6.13.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
ipykernel  from testing6.13.0-1
all others from testingfrom testing

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

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=ipykernel

https://ci.debian.net/data/autopkgtest/testing/amd64/i/ipykernel/22160991/log.gz

[31m___ ERROR at setup of test_asyncio_interrupt 
___


cls = 
func = . at 0x7fdd6d273b50>
when = 'setup'
reraise = (, )

@classmethod
def from_call(
cls,
func: "Callable[[], 
TResult]",
when: 
"Literal['collect', 
'setup', 'call', 
'teardown']",

reraise: Optional[
Union[Type[BaseException], 
Tuple[Type[BaseException], ...]]

] = None,
) -> 
"CallInfo[TResult]":

excinfo = None
start = timing.time()
precise_start = timing.perf_counter()
try:

  result: Optional[TResult] = func()


/usr/lib/python3/dist-packages/_pytest/runner.py:311: _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ 
/usr/lib/python3/dist-packages/_pytest/runner.py:255: in 

lambda: ihook(item=item, **kwds), when=when, 
reraise=reraise
/usr/lib/python3/dist-packages/pluggy/_hooks.py:265: in 
__call__
return 
self._hookexec(self.name, 
self.get_hookimpls(), kwargs, firstresult)
/usr/lib/python3/dist-packages/pluggy/_manager.py:80: in 
_hookexec
return 
self._inner_hookexec(hook_name, methods, kwargs, 
firstresult)
/usr/lib/python3/dist-packages/_pytest/unraisableexception.py:83: 
in pytest_runtest_setup

yield from unraisable_exception_runtest_hook()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _
def 
unraisable_exception_runtest_hook() -> 
Generator[None, None, None]:
with catch_unraisable_exception() 
as cm:

yield
if cm.unraisable:
if cm.unraisable.err_msg 
is not None:

err_msg = cm.unraisable.err_msg
else:
err_msg = "Exception 
ignored in"
msg = 
f"{err_msg}: 
{cm.unraisable.object!r}\n\n"

msg += "".join(
traceback.format_exception(

Bug#1012786: libcamera: Fails to build from source

[Christopher Obbard]

On 14/06/2022 15:35, Lisandro Damián Nicanor Pérez Meyer wrote:

Hi!

On Tue, 14 Jun 2022 at 05:26, Christopher Obbard
 wrote:



Hi!

I propose a patch to potentially fix this:
https://salsa.debian.org/multimedia-team/libcamera/-/merge_requests/6

The use of the depreciated function could even be fixed in upstream, it
could be worth updating the package from upstream?


No, upstream is doing the right thing. Their builds ought to fail in
this case. We are the ones that should disable this flag, as done.

What you really need to do is take this issue to upstream so they use
the newer interfaces if possible (ie, avoid the deprecation warning).



Right, what I originally meant was: "perhaps upstream have fixed this by 
using the correct gstreamer function instead of a depreciated one, maybe 
we should check if upstream have done that".


For the record, it turns out that upstream have: 
https://git.libcamera.org/libcamera/libcamera.git/commit/test/gstreamer/gstreamer_multi_stream_test.cpp?id=4085372c517e1527114dc4098194c3ae3b973ba0


So, if we update to the latest version of libcamera, everything is fine 
again for future :-). I don't mind doing an update to libcamera HEAD, if 
Andrew would like some help.


Cheers!

Chris

Bug#1004109: xdg-utils-cxx FTBFS on !amd64/arm64: symbol differences

[Benjamin Drung]

Hi,

Instead of disabling the symbols that are not present when building with
LTO, mark them as optional instead. Attached is a patch applied to
Ubuntu.

-- 
Benjamin Drung
Debian & Ubuntu Developer
diff -Nru xdg-utils-cxx-1.0.1/debian/changelog xdg-utils-cxx-1.0.1/debian/changelog
--- xdg-utils-cxx-1.0.1/debian/changelog	2021-03-11 20:24:59.0 +0100
+++ xdg-utils-cxx-1.0.1/debian/changelog	2022-06-14 16:49:46.0 +0200
@@ -1,3 +1,10 @@
+xdg-utils-cxx (1.0.1-4) UNRELEASED; urgency=medium
+
+  * Mark symbols as optional not seen when building with lto.
+(Closes: #1004109)
+
+ -- Benjamin Drung   Tue, 14 Jun 2022 16:49:46 +0200
+
 xdg-utils-cxx (1.0.1-3) unstable; urgency=medium
 
   * Add patches provided by Assassin to fix issues with targets and
diff -Nru xdg-utils-cxx-1.0.1/debian/libxdgutilsdesktopentry1.0.1.symbols xdg-utils-cxx-1.0.1/debian/libxdgutilsdesktopentry1.0.1.symbols
--- xdg-utils-cxx-1.0.1/debian/libxdgutilsdesktopentry1.0.1.symbols	2021-03-11 20:24:59.0 +0100
+++ xdg-utils-cxx-1.0.1/debian/libxdgutilsdesktopentry1.0.1.symbols	2022-06-14 16:49:39.0 +0200
@@ -1,14 +1,14 @@
 # SymbolsHelper-Confirmed: 1.0.1 amd64
 libXdgUtilsDesktopEntry.so.1.0.1 libxdgutilsdesktopentry1.0.1 #MINVER#
 * Build-Depends-Package: xdg-utils-cxx-dev
- _ZN8XdgUtils12DesktopEntry10ParseErrorD0Ev@Base 1.0.1
- _ZN8XdgUtils12DesktopEntry10ParseErrorD1Ev@Base 1.0.1
- _ZN8XdgUtils12DesktopEntry10ParseErrorD2Ev@Base 1.0.1
+ (optional=lto)_ZN8XdgUtils12DesktopEntry10ParseErrorD0Ev@Base 1.0.1
+ (optional=lto)_ZN8XdgUtils12DesktopEntry10ParseErrorD1Ev@Base 1.0.1
+ (optional=lto)_ZN8XdgUtils12DesktopEntry10ParseErrorD2Ev@Base 1.0.1
  _ZN8XdgUtils12DesktopEntry12DesktopEntry3setERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES9_@Base 1.0.1
- _ZN8XdgUtils12DesktopEntry12DesktopEntry4Priv11createEntryERKNS0_19DesktopEntryKeyPathERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.1
- _ZN8XdgUtils12DesktopEntry12DesktopEntry4Priv11createGroupERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.1
- _ZN8XdgUtils12DesktopEntry12DesktopEntry4Priv11removeEntryERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.1
- _ZN8XdgUtils12DesktopEntry12DesktopEntry4Priv11updatePathsEv@Base 1.0.1
+ (optional=lto)_ZN8XdgUtils12DesktopEntry12DesktopEntry4Priv11createEntryERKNS0_19DesktopEntryKeyPathERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.1
+ (optional=lto)_ZN8XdgUtils12DesktopEntry12DesktopEntry4Priv11createGroupERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.1
+ (optional=lto)_ZN8XdgUtils12DesktopEntry12DesktopEntry4Priv11removeEntryERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.1
+ (optional=lto)_ZN8XdgUtils12DesktopEntry12DesktopEntry4Priv11updatePathsEv@Base 1.0.1
  _ZN8XdgUtils12DesktopEntry12DesktopEntry6removeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.1
  _ZN8XdgUtils12DesktopEntry12DesktopEntryC1EOS1_@Base 1.0.1
  _ZN8XdgUtils12DesktopEntry12DesktopEntryC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.1
@@ -27,13 +27,13 @@
  _ZN8XdgUtils12DesktopEntry12DesktopEntryaSERKS1_@Base 1.0.1
  _ZN8XdgUtils12DesktopEntry12DesktopEntryixERKNS0_19DesktopEntryKeyPathE@Base 1.0.1
  _ZN8XdgUtils12DesktopEntry12DesktopEntryixERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.1
- _ZN8XdgUtils12DesktopEntry17DesktopEntryErrorD0Ev@Base 1.0.1
- _ZN8XdgUtils12DesktopEntry17DesktopEntryErrorD1Ev@Base 1.0.1
- _ZN8XdgUtils12DesktopEntry17DesktopEntryErrorD2Ev@Base 1.0.1
- _ZN8XdgUtils12DesktopEntry18MalformedPathErrorD0Ev@Base 1.0.1
- _ZN8XdgUtils12DesktopEntry18MalformedPathErrorD1Ev@Base 1.0.1
- _ZN8XdgUtils12DesktopEntry18MalformedPathErrorD2Ev@Base 1.0.1
- _ZN8XdgUtils12DesktopEntry19DesktopEntryKeyPath4Priv5parseERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.1
+ (optional=lto)_ZN8XdgUtils12DesktopEntry17DesktopEntryErrorD0Ev@Base 1.0.1
+ (optional=lto)_ZN8XdgUtils12DesktopEntry17DesktopEntryErrorD1Ev@Base 1.0.1
+ (optional=lto)_ZN8XdgUtils12DesktopEntry17DesktopEntryErrorD2Ev@Base 1.0.1
+ (optional=lto)_ZN8XdgUtils12DesktopEntry18MalformedPathErrorD0Ev@Base 1.0.1
+ (optional=lto)_ZN8XdgUtils12DesktopEntry18MalformedPathErrorD1Ev@Base 1.0.1
+ (optional=lto)_ZN8XdgUtils12DesktopEntry18MalformedPathErrorD2Ev@Base 1.0.1
+ (optional=lto)_ZN8XdgUtils12DesktopEntry19DesktopEntryKeyPath4Priv5parseERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.1
  _ZN8XdgUtils12DesktopEntry19DesktopEntryKeyPath6setKeyERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.1
  _ZN8XdgUtils12DesktopEntry19DesktopEntryKeyPath8setGroupERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.1
  _ZN8XdgUtils12DesktopEntry19DesktopEntryKeyPath9setLocaleERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.1
@@ -65,8 +65,8 @@
  _ZN8XdgUtils12DesktopEntry20DesktopEntryKeyValuecvbEv@Base 1.0.1
  

Bug#1011187: marked as done (redis: FTBFS: killed due to inactivity)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jun 2022 15:09:07 +
with message-id 
and subject line Bug#1011187: fixed in redis 5:7.0.1-2
has caused the Debian Bug report #1011187,
regarding redis: FTBFS: killed due to inactivity
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.)


-- 
1011187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: redis
Version: 5:6.0.16-2
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=redis=amd64=5%3A6.0.16-2%2Bb1=1652566704=0

--- Iteration 16 ---
19:48:12> Cluster is writable before failover: OK
19:48:12> Killing node #7: OK
19:48:12> Cluster should eventually be up again: OK
19:48:12> Cluster is writable again: OK
19:48:12> Restarting node #7: OK
19:48:12> Instance #7 is now a slave: OK
19:48:12> We can read back the value we set before: OK
--- Iteration 15 ---
19:48:13> Wait for slave of #1 to sync: OK
19:48:13> Cluster is writable before failover: OK
19:48:13> Killing node #1: OK
19:48:13> Wait failover by #6 with old epoch 2: OK
19:48:18> Cluster should eventually be up again: OK
19:48:18> Cluster is writable again: Expected error reading "sock562250dc96c0": 
software caused connection abort eq {OK} (context: type eval line 4 cmd {assert 
{$err eq {OK}}} proc ::test)
(Jumping to next unit after error)
--- Iteration 14 ---
19:48:18> Cluster is writable before failover: 
E: Build killed with signal TERM after 150 minutes of inactivity

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: redis
Source-Version: 5:7.0.1-2
Done: Chris Lamb 

We believe that the bug you reported is fixed in the latest version of
redis, 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.
Chris Lamb  (supplier of updated redis 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, 14 Jun 2022 15:41:53 +0100
Source: redis
Built-For-Profiles: nocheck
Architecture: source
Version: 5:7.0.1-2
Distribution: experimental
Urgency: medium
Maintainer: Chris Lamb 
Changed-By: Chris Lamb 
Closes: 1011187 1012658
Changes:
 redis (5:7.0.1-2) experimental; urgency=medium
 .
   * Drop support (in patches, etc.) for using the systemwide hiredis and Lua,
 reverting to using the built-in cjson (etc.). (Closes: #1012658)
   * Add an internal timeout for the cluster tests to prevent FTBFS.
 (Closes: #1011187)
   * Drop a duplicate comment in debian/rules.
Checksums-Sha1:
 ee2957bb690a79e450977235b819c9731330d602 2266 redis_7.0.1-2.dsc
 c98c9047296d32adb097592cba2813b2e3d3beaf 27004 redis_7.0.1-2.debian.tar.xz
 e07adf4b6025add9fd0963ac4d1a28c209aba6dd 7391 redis_7.0.1-2_amd64.buildinfo
Checksums-Sha256:
 b6845e0e4e7003100afb24552bb8534dc59aa493df0c08d3f23aa7c19155dff4 2266 
redis_7.0.1-2.dsc
 f8f72b6faa66476fa237998b537222121ef45e3baa0c8c67e2c4c80ecfaa6fcd 27004 
redis_7.0.1-2.debian.tar.xz
 15df11ea4fccd30d3095fe9faf5513b201c1e0df0a72c57d707b828b00061f59 7391 
redis_7.0.1-2_amd64.buildinfo
Files:
 94572d0ba307c8571ade5a468f89dbeb 2266 database optional redis_7.0.1-2.dsc
 e8622fda1fc6c0951e27abd1ebbc5666 27004 database optional 
redis_7.0.1-2.debian.tar.xz
 25d94da29fe4354456c7ce63f56b7314 7391 database optional 
redis_7.0.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAmKonvwACgkQHpU+J9Qx
HlhFnQ//dkGFafHILTYCgoV1YH+3SH5l2OORIdx/67p4slZG/6yjJR+So7qDCPVM
/AtJUZKo8L6S72t+Fiw2qWJhyFDJep3o7Y/a7fpf+s9sfOk5bmNFvhaYbewumvQl
NxRlQ1ip+HOVOTkLCzZFcztVX1ewpUvmT/G2zdroC3i2r2+hgnMPZx6OEYDI6MjY
ZvbIWxZLmAoNJVFsHVg6DuJwHYtEtEqOt4t1UYCvJugIu5RQINrgis107cp2o2Nx
krSGQ8QKhHNlxKnPjj/z41/RnBpSzBnjrWNpfk6nwRbdPTiSkEwa+dsB4PYlgPcx
yHzoWPZ7bBVTWtYqzULO59O9x6Xhsn0lEiwqsFuQbrTHScXhdAnQb5+VJoIg+vOL
t4GCuZWVVwIYir9Ks8c5gguZYh690jMDJgWgV78FRS6RqkuxObKSPZ7yUPM7UI5F
r3BE4g1do7WyS+tdHl3rgRjJVfssaugFRHH8S1IqqrSxy9WqSD3KWpFGgiNAm13E
VIfZfF6ZYxZN7Xzaj5sE9SnUlyxwo2xc3FeBZz8fdwoGT037WPKgM3+4khsul8KE

Bug#1011964: marked as pending in ipykernel

[Julien Puydt]

Control: tag -1 pending

Hello,

Bug #1011964 in ipykernel 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/ipykernel/-/commit/db93b2b4ba526c756039655a4d65e45b3447be88


Unbreak the compilation (Closes: #1011964)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1011964

Processed: Bug#1011964 marked as pending in ipykernel

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1011964 [src:ipykernel] ipykernel: autopkgtest regression: ERROR at setup 
of test_asyncio_interrupt
Added tag(s) pending.

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

Bug#1011000: marked as done (python3-pymetar: fails with default url and oepnssl 3)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jun 2022 16:43:08 +0200
with message-id 
and subject line Re: Bug#1011000: python3-pymetar: fails with default url and 
oepnssl 3
has caused the Debian Bug report #1011000,
regarding python3-pymetar: fails with default url and oepnssl 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.)


-- 
1011000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pymetar
Version: 1.2-0.2
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Since the upgrade to OpenSSL 3.x in Debian pymetar fails against the
default URL 
baseurl="https://tgftp.nws.noaa.gov/data/observations/;

% /usr/bin/pymetar LOWI
Something went wrong when fetching the report.
These usually are transient problems if the station ID is valid. 
The error encountered was:



Cheers,
gregor

- -- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
'stable-security'), (500, 'oldoldstable'), (500, 'experimental'), (500, 
'testing'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages python3-pymetar depends on:
ii  ca-certificates  20211016
ii  python3  3.10.4-1+b1

python3-pymetar recommends no packages.

python3-pymetar suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmKAOWNfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYpLhAAr+XFkiG9Wp8XXj8vdF8M/T2aEXVYI1DOkPcmpcT0db4XVpY81KVK0c+w
/QYMBmGgEE3yR3IDXyJ7UU6Tuoh0VW9QrOxC7VF5qaX+7x2txO8iCWXmVl5ncRUR
26M3KO/KgtXiR0eS6bpjoAxOFKsFmVYCp4Ghllx1Di+8fxbWNfXpdv7tsgngOG+T
kokmZ/zYtbrtoaRJAmRQBx9mlgnzcTb2kxQ2VfYjbKJEI7CIEuzZtyJogEjUwUEH
UlYm7AMXcr66nEpFq54A3ysa9MQBL5r2BIx1U42cVD30gxYGS/u9DMbwRLpOprb1
YO5v7FLu67BAG2m44p4/7i/uUpR+iRzFl7KjeO2ypx3L0iZSoftSk+sT2BCaniDo
1EvE/HCMoYmRHK68FIV4bEIA07ZjbSCvSkkfqzgS+q9QpjvYUOQ/KUqmF1UHt6Ce
lF3CsmGMiRo6frBq9ikfAJ7WvNEOtQWD/eBUczBMgZyOSCYyi6fO4yWz0+PDRSF9
JxLcmGHKMoQHvjdh7aP2N/QvOaTk32MlyZXsnjJRJ4F+YlSVQYbUUTdalUSCHeyt
sx5k7T5hJ1EBdu/nMupgY0XQDZl5sIhsOuGoplev5KBImGXMxc1mJvRWwBwE4tzv
PngOBMoccyTAt8EZpbPTSDy+k2RL8/epIujytB1LIrlAnQIPmwE=
=i4dd
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
On Sun, 15 May 2022 01:21:07 +0200, gregor herrmann wrote:

> Since the upgrade to OpenSSL 3.x in Debian pymetar fails against the
> default URL 
> baseurl="https://tgftp.nws.noaa.gov/data/observations/;
> 
> % /usr/bin/pymetar LOWI
> Something went wrong when fetching the report.
> These usually are transient problems if the station ID is valid. 
> The error encountered was:
>  renegotiation disabled (_ssl.c:997)>

This seems to be fixed on the server side, hence closing.

% /usr/bin/pymetar LOWI | head -n 1
Weather report for Innsbruck-Flughafen, Austria (LOWI) as of 2022-06-14 
14:20:00Z


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
--- End Message ---

Bug#1012786: libcamera: Fails to build from source

[Lisandro Damián Nicanor Pérez Meyer]

Hi!

On Tue, 14 Jun 2022 at 05:26, Christopher Obbard
 wrote:
>
>
> Hi!
>
> I propose a patch to potentially fix this:
> https://salsa.debian.org/multimedia-team/libcamera/-/merge_requests/6
>
> The use of the depreciated function could even be fixed in upstream, it
> could be worth updating the package from upstream?

No, upstream is doing the right thing. Their builds ought to fail in
this case. We are the ones that should disable this flag, as done.

What you really need to do is take this issue to upstream so they use
the newer interfaces if possible (ie, avoid the deprecation warning).

-- 
Lisandro Damián Nicanor Pérez Meyer
https://perezmeyer.com.ar/

Processed: ruby-uglifier: FTBFS: tests fail: uglifier_spec.rb:383, uglifier_spec.rb:751

[Debian Bug Tracking System]

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

> found 981224 2.7.2+dfsg-2
Bug #981224 [src:ruby-uglifier] ruby-uglifier: FTBFS: tests fail: 
uglifier_spec.rb:383, uglifier_spec.rb:751
Marked as found in versions ruby-uglifier/2.7.2+dfsg-2.
> thanks
Stopping processing here.

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

Bug#1012789: [Emc-developers] Bug#1012789: linuxcnc-uspace: Linux CNC will not start

[andy pugh]

On Tue, 14 Jun 2022 at 14:49, Vector Hasting  wrote:

> _tkinter.TclError: couldn't load file 
> "/usr/lib/tcltk/aarch64-linux-gnu/Img1.4.13/libtifftcl4.1.0.so": 
> /usr/lib/tcltk/aarch64-linux-gnu/Img1.4.13/libtifftcl4.1.0.so: undefined 
> symbol: _TIFFsetString, version LIBTIFF_4.0

This looks to be a dependency (hard coded?) on the version of libtiff
that shipped with Buster (4.1).

But it also seems to be in a package that LinuxCNC depends on, but
doesn't control?
https://sourceforge.net/projects/tkimg/files/tkimg/1.4/tkimg%201.4.13/
(From the file path being searched)

For me, the trail dries up there. I guess this is due to a Tcl/Tk dependency?

-- 
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1912

Bug#1012789: Can you check if Img works at all?

[Jeff Epler]

Thanks for tryting LinuxCNC on aarch64. I don't know of anyone presently
using such a configuration.

As far as the "undefined symbol" message:

Please check whether in "wish", it works to "package require Img" or
whether the same error occurs. If it's the same error then may point to a
general problem between libtk-img and libtiff.

As far as the "LIBGL: Error while gathering supported extension
(eglInitialize: EGL_BAD_DISPLAY), default to none" message:

Most UIs for LinuxCNC require working OpenGL. You can try a different UI
such as tklinuxcnc, it doesn't use OpenGL and probably also doesn't use
Img. However, it's much less friendly (IMO)

Jeff

Bug#1012804: rocksdb: Please build against liblz4-dev

[Benjamin Drung]

Package: rocksdb
Version: 7.2.2-3
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch
X-Debbugs-Cc: bdr...@ubuntu.com

Dear Maintainer,

The autopkgtest for balboa fails against rocksdb 7.2.2-3 with:

rocksdb_open() failed: `Invalid argument: Compression type LZ4 is not
linked with the binary.`

In Ubuntu, the attached patch was applied to achieve the following:

  * Enable LZ4 support (Closes: #1012629)


Thanks for considering the patch.

-- 
Benjamin Drung
Debian & Ubuntu Developer
diff -Nru rocksdb-7.2.2/debian/control rocksdb-7.2.2/debian/control
--- rocksdb-7.2.2/debian/control2022-05-19 23:16:32.0 +0200
+++ rocksdb-7.2.2/debian/control2022-06-14 15:22:00.0 +0200
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Laszlo Boszormenyi (GCS) 
 Build-Depends: debhelper-compat (= 13), cmake, libgflags-dev, libsnappy-dev,
- libbz2-dev, zlib1g-dev, libzstd-dev
+ libbz2-dev, zlib1g-dev, libzstd-dev, liblz4-dev
 Standards-Version: 4.6.0
 Homepage: https://rocksdb.org/
 
diff -Nru rocksdb-7.2.2/debian/rules rocksdb-7.2.2/debian/rules
--- rocksdb-7.2.2/debian/rules  2022-05-21 19:47:37.0 +0200
+++ rocksdb-7.2.2/debian/rules  2022-06-14 14:31:59.0 +0200
@@ -26,6 +26,7 @@
dh_auto_configure -O--buildsystem=cmake \
 -- \
 -DWITH_BZ2=ON \
+-DWITH_LZ4=ON \
 -DWITH_ZLIB=ON \
 -DWITH_ZSTD=ON \
 -DWITH_SNAPPY=ON \

Bug#1012802: python3-ipykernel: breaks jupyter notebook

[Jörg-Volker Peetz]

Package: python3-ipykernel
Version: 6.13.1-1
Severity: serious

Dear Debian Python Modules Team,

trying to load a jupyter notebook fails with the message

/usr/bin/python3: No module named ipykernel_launcher

Indeed, in the package there is no file
`/usr/lib/python3/dist-packages/ipykernel_launcher.py`
any more. Not any file in `/usr/lib/`.

Regards,
Jörg.


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

Kernel: Linux 5.18.3 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages python3-ipykernel depends on:
ii  python33.9.8-1
ii  python3-ipython7.31.1-1
ii  python3-jupyter-client 7.3.4-1
ii  python3-matplotlib-inline  0.1.3-1
ii  python3-nest-asyncio   1.5.4-1
ii  python3-packaging  21.3-1
ii  python3-psutil 5.9.0-1
ii  python3-tornado6.1.0-3
ii  python3-traitlets  5.2.2-1

python3-ipykernel recommends no packages.

python3-ipykernel suggests no packages.

-- no debconf information

Bug#1006575: marked as done (sbsigntool: FTBFS with OpenSSL 3.0)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jun 2022 12:39:07 +
with message-id 
and subject line Bug#1006575: fixed in sbsigntool 0.9.4-3.1
has caused the Debian Bug report #1006575,
regarding sbsigntool: 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.)


-- 
1006575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sbsigntool
Version: 0.9.4-3
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 -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra 
--std=gnu99 -I../lib/ccan/ -Werror -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o sbsign-sbsign.o 
`test -f 'sbsign.c' || echo './'`sbsign.c
| sbsign.c: In function ‘main’:
| sbsign.c:234:9: error: ‘ERR_load_BIO_strings’ is deprecated: Since 
OpenSSL 3.0 [-Werror=deprecated-declarations]
|   234 | ERR_load_BIO_strings();
|   | ^~~~
| In file included from /usr/include/openssl/cryptoerr.h:17,
|  from /usr/include/openssl/crypto.h:38,
|  from /usr/include/openssl/bio.h:30,
|  from /usr/include/openssl/conf.h:24,
|  from sbsign.c:45:
| /usr/include/openssl/cryptoerr_legacy.h:31:27: note: declared here
|31 | OSSL_DEPRECATEDIN_3_0 int ERR_load_BIO_strings(void);
|   |   ^~~~
| cc1: all warnings being treated as errors
| make[3]: *** [Makefile:693: sbsign-sbsign.o] Error 1

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

Sebastian
--- End Message ---
--- Begin Message ---
Source: sbsigntool
Source-Version: 0.9.4-3.1
Done: Bastian Germann 

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

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

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated sbsigntool package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 04 Jun 2022 11:37:27 +
Source: sbsigntool
Architecture: source
Version: 0.9.4-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian EFI Team 
Changed-By: Bastian Germann 
Closes: 1006575
Changes:
 sbsigntool (0.9.4-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload
 .
   [ Simon Chopin ]
   * Disable -Werror on deprecation warnings for the OpenSSL transition
 (Closes: #1006575)
   * Apply patch to fix the OpenSSL3 build (LP: #1946193)
Checksums-Sha1:
 66491a7aca7aea07e7044491ccb907e6a5a1a6fe 1846 sbsigntool_0.9.4-3.1.dsc
 5a5748eaba65e50d18898b56c48563d73fbe8870 8784 
sbsigntool_0.9.4-3.1.debian.tar.xz
 50f4a1daa9437f5b22394d83eda3f06e0c400e1f 6145 
sbsigntool_0.9.4-3.1_source.buildinfo
Checksums-Sha256:
 ad144c4a21fae66d05eb818d4a3cbd9bb32204f16956fee0530bcee1e2e71fb9 1846 
sbsigntool_0.9.4-3.1.dsc
 4ca67de7dbda322c5538b93cfcb70010e3c23d408b1afd6d426effd6d7a68fb0 8784 
sbsigntool_0.9.4-3.1.debian.tar.xz
 d6bf5f2b85ec9c68ab7dd22e0292a9540df5113fe1c75b043da59a84f76dd526 6145 
sbsigntool_0.9.4-3.1_source.buildinfo
Files:
 45cce2cc86b2b2bd52e7574e861ecfa7 1846 utils optional sbsigntool_0.9.4-3.1.dsc
 57094878f8554cb897bb2c70fad5e7c6 8784 utils optional 
sbsigntool_0.9.4-3.1.debian.tar.xz
 9596cddec80b7700688fdb28fac6b56a 6145 utils optional 
sbsigntool_0.9.4-3.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmKbRWkQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFAzjC/0YQMDzVHRLM2oOF7Ri2bEgtqL4+tCqtkpe
EIUM3eyVATbNAFyD1fPS8KdXKdvEGMqtnSDoqkkYUkBRnhXYYhVpnDBxaxBUkcKf
/zxDACFcvhLvBA9JibDtM2+F+/+YaV+JlyzGgTgMAW5AjTemBhSu25Ycp2JQNMYl
STZV2dLeOp0t1SIKokuPEEokLF9TLNtOXmoYUdDJpuZ1xrNLOzaQlgErzB1EnWk2
qvFV/UQz8Qms4ya97OQ6pEAI14UbxVBOw6Ea6o3GkEORu97y6NR8JcyLxSzRomuW
EdHKHnT9zltJ+k96BEBZLjDyi5W7m0whME/xMTcn4HP1VRTdqjTHCGbe7USwK7mE
7Kw+1UAL53Qj8mLBfeMbHcv/CY9todCZPgu2S2QM65NYkFdPhRptXx58se1uUO/w

Processed: Re: golang-github-komkom-toml: autopkgtest regression on armhf/i386: -{"hex3":3735928559}, +{"hex3":-559038737}

[Debian Bug Tracking System]

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

> forwarded 1004048 https://github.com/komkom/toml/issues/5
Bug #1004048 [src:golang-github-komkom-toml] golang-github-komkom-toml: 
autopkgtest regression on armhf/i386: -{"hex3":3735928559}, +{"hex3":-559038737}
Set Bug forwarded-to-address to 'https://github.com/komkom/toml/issues/5'.
> thanks
Stopping processing here.

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

Bug#1012786: marked as done (libcamera: Fails to build from source)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jun 2022 12:19:35 +
with message-id 
and subject line Bug#1012786: fixed in libcamera 0~git20211108+1b30992b623e-4
has caused the Debian Bug report #1012786,
regarding libcamera: Fails to build from source
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.)


-- 
1012786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcamera
Version: 0~git20200629+e7aa92a-8
Severity: serious
Justification: Fails to build form source
X-Debbugs-Cc: lisan...@debian.org

Trying to fix a bug in libcamera I found it's currently failing to build
from source. Seems it's taking deprecation warnings as errors.

Log follows. Kinds regards, Lisandro.

../test/gstreamer/gstreamer_multi_stream_test.cpp: In member function ‘virtual 
int GstreamerMultiStreamTest::run()’:
../test/gstreamer/gstreamer_multi_stream_test.cpp:90:76: error: ‘GstPad* 
gst_element_get_request_pad(GstElement*, const gchar*)’ is deprecated: Use 
'gst_element_request_pad_simple' instead [-Werror=deprecated-declarations]
   90 | g_autoptr(GstPad) request_pad = 
gst_element_get_request_pad(libcameraSrc_, "src_%u");
  | 
~~~^
In file included from /usr/include/gstreamer-1.0/gst/gstbin.h:27,
 from /usr/include/gstreamer-1.0/gst/gst.h:35,
 from ../test/gstreamer/gstreamer_multi_stream_test.cpp:13:
/usr/include/gstreamer-1.0/gst/gstelement.h:1042:25: note: declared here
 1042 | GstPad* gst_element_get_request_pad (GstElement 
*element, const gchar *name);
  | ^~~
cc1plus: all warnings being treated as errors
[246/390] /usr/bin/meson --internal symbolextractor 
'/<>/obj-x86_64-linux-gnu' 
src/libcamera/base/libcamera-base.so.0.0.0 
src/libcamera/base/libcamera-base.so.0.0.0 
src/libcamera/base/libcamera-base.so.0.0.0.p/libcamera-base.so.0.0.0.symbols
[247/390] ccache c++ -Itest/stream/stream_formats.p -Itest/stream 
-I../test/stream -Itest/libtest -I../test/libtest -Iinclude -I../include 
-Iinclude/libcamera -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall 
-Winvalid-pch -Wnon-virtual-dtor -Wextra -Werror -std=c++17 -O0 -Wshadow 
-include config.h -g -O2 '-ffile-prefix-map=/<>=.' 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -MD -MQ test/stream/stream_formats.p/stream_formats.cpp.o 
-MF test/stream/stream_formats.p/stream_formats.cpp.o.d -o 
test/stream/stream_formats.p/stream_formats.cpp.o -c 
../test/stream/stream_formats.cpp
[248/390] ccache c++ -Itest/serialization/control_serialization.p 
-Itest/serialization -I../test/serialization -Itest/libtest -I../test/libtest 
-Iinclude -I../include -Iinclude/libcamera/ipa -Iinclude/libcamera 
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch 
-Wnon-virtual-dtor -Wextra -Werror -std=c++17 -O0 -Wshadow -include config.h -g 
-O2 '-ffile-prefix-map=/<>=.' -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-DLIBCAMERA_BASE_PRIVATE -MD -MQ 
test/serialization/control_serialization.p/serialization_test.cpp.o -MF 
test/serialization/control_serialization.p/serialization_test.cpp.o.d -o 
test/serialization/control_serialization.p/serialization_test.cpp.o -c 
../test/serialization/serialization_test.cpp
[249/390] ccache c++ -Itest/serialization/ipa_data_serializer_test.p 
-Itest/serialization -I../test/serialization -Itest/libtest -I../test/libtest 
-Iinclude -I../include -Iinclude/libcamera/ipa -Iinclude/libcamera 
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch 
-Wnon-virtual-dtor -Wextra -Werror -std=c++17 -O0 -Wshadow -include config.h -g 
-O2 '-ffile-prefix-map=/<>=.' -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-DLIBCAMERA_BASE_PRIVATE -MD -MQ 
test/serialization/ipa_data_serializer_test.p/serialization_test.cpp.o -MF 
test/serialization/ipa_data_serializer_test.p/serialization_test.cpp.o.d -o 
test/serialization/ipa_data_serializer_test.p/serialization_test.cpp.o -c 
../test/serialization/serialization_test.cpp
[250/390] ccache c++ -Itest/serialization/control_serialization.p 
-Itest/serialization -I../test/serialization -Itest/libtest -I../test/libtest 
-Iinclude -I../include -Iinclude/libcamera/ipa -Iinclude/libcamera 
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch 
-Wnon-virtual-dtor -Wextra -Werror 

Bug#1012786: marked as pending in libcamera

[Andrej Shadura]

Control: tag -1 pending

Hello,

Bug #1012786 in libcamera 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/multimedia-team/libcamera/-/commit/f8682fadc114d5e75d1205c3329c961703314cd1


Don't treat compilation warnings as errors (Closes: #1012786)

Signed-off-by: Christopher Obbard 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1012786

Processed: Bug#1012786 marked as pending in libcamera

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1012786 [src:libcamera] libcamera: Fails to build from source
Added tag(s) pending.

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

Bug#997589: marked as done (panicparse: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 github.com/maruel/panicparse github.com/maruel/panicparse/cmd/panic github.com/maruel/panicpar

[Debian Bug Tracking System]

Your message dated Tue, 14 Jun 2022 11:34:43 +
with message-id 
and subject line Bug#997589: fixed in panicparse 2.2.2-1
has caused the Debian Bug report #997589,
regarding panicparse: FTBFS: dh_auto_test: error: cd _build && go test -vet=off 
-v -p 4 github.com/maruel/panicparse github.com/maruel/panicparse/cmd/panic 
github.com/maruel/panicparse/cmd/panic/internal 
github.com/maruel/panicparse/cmd/panic/internal/incorrect 
github.com/maruel/panicparse/cmd/panic/internal/utf8 
github.com/maruel/panicparse/cmd/panicweb 
github.com/maruel/panicparse/cmd/panicweb/internal 
github.com/maruel/panicparse/cmd/pp github.com/maruel/panicparse/internal 
github.com/maruel/panicparse/internal/htmlstack 
github.com/maruel/panicparse/internal/internaltest 
github.com/maruel/panicparse/stack github.com/maruel/panicparse/stack/webstack 
returned exit code 1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
997589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: panicparse
Version: 1.6.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package panicparse
> dpkg-buildpackage: info: source version 1.6.1-3
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Anthony Fok 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --builddirectory=_build --buildsystem=golang --with=golang
>dh_auto_clean -O--builddirectory=_build -O--buildsystem=golang
>dh_autoreconf_clean -O--builddirectory=_build -O--buildsystem=golang
>dh_clean -O--builddirectory=_build -O--buildsystem=golang
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building panicparse using existing 
> ./panicparse_1.6.1.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building panicparse in panicparse_1.6.1-3.debian.tar.xz
> dpkg-source: info: building panicparse in panicparse_1.6.1-3.dsc
>  debian/rules binary
> dh binary --builddirectory=_build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang
>dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_build -O--builddirectory=_build -O--buildsystem=golang
>   cd _build && go install -trimpath -v -p 4 github.com/maruel/panicparse 
> github.com/maruel/panicparse/cmd/panic 
> github.com/maruel/panicparse/cmd/panic/internal 
> github.com/maruel/panicparse/cmd/panic/internal/incorrect 
> github.com/maruel/panicparse/cmd/panic/internal/utf8 
> github.com/maruel/panicparse/cmd/panicweb 
> github.com/maruel/panicparse/cmd/panicweb/internal 
> github.com/maruel/panicparse/cmd/pp github.com/maruel/panicparse/internal 
> github.com/maruel/panicparse/internal/htmlstack 
> github.com/maruel/panicparse/internal/internaltest 
> github.com/maruel/panicparse/stack github.com/maruel/panicparse/stack/webstack
> internal/unsafeheader
> internal/goexperiment
> internal/abi
> internal/cpu
> runtime/internal/atomic
> runtime/internal/sys
> internal/itoa
> runtime/internal/math
> math/bits
> unicode/utf8
> internal/race
> internal/bytealg
> sync/atomic
> unicode
> math
> encoding
> unicode/utf16
> runtime
> golang.org/x/sys/internal/unsafeheader
> github.com/maruel/panicparse/cmd/panic/internal
> github.com/maruel/panicparse/cmd/panic/internal/incorrect
> github.com/maruel/panicparse/cmd/panic/internal/utf8
> container/list
> crypto/internal/subtle
> crypto/subtle
> vendor/golang.org/x/crypto/cryptobyte/asn1
> internal/nettrace
> vendor/golang.org/x/crypto/internal/subtle
> internal/reflectlite
> sync
> internal/testlog
> math/rand
> runtime/cgo
> internal/singleflight
> errors
> sort
> io
> strconv
> internal/oserror
> path
> syscall
> bytes
> reflect
> strings
> html
> regexp/syntax
> internal/syscall/unix
> time
> internal/syscall/execenv
> bufio
> regexp
> hash
> internal/fmtsort
> encoding/binary
> internal/poll
> io/fs
> encoding/base64
> golang.org/x/sys/unix
> context
> hash/crc32
> os
> crypto/cipher
> crypto
> crypto/elliptic/internal/fiat
> crypto/aes

Bug#1012596: marked as done (cron-daemon-common: missing versioned Breaks+Replaces against bcron, systemd-cron)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jun 2022 09:48:57 +
with message-id 
and subject line Bug#1012596: fixed in cron 3.0pl1-144
has caused the Debian Bug report #1012596,
regarding cron-daemon-common: missing versioned Breaks+Replaces against bcron, 
systemd-cron
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.)


-- 
1012596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cron-daemon-common
Version: 3.0pl1-143
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package cron-daemon-common.
  Preparing to unpack .../cron-daemon-common_3.0pl1-143_all.deb ...
  Unpacking cron-daemon-common (3.0pl1-143) ...
  dpkg: error processing archive 
/var/cache/apt/archives/cron-daemon-common_3.0pl1-143_all.deb (--unpack):
   trying to overwrite '/etc/crontab', which is also in package bcron 0.11-9
  Errors were encountered while processing:
   /var/cache/apt/archives/cron-daemon-common_3.0pl1-143_all.deb

  Selecting previously unselected package cron-daemon-common.
  Preparing to unpack .../cron-daemon-common_3.0pl1-143_all.deb ...
  Unpacking cron-daemon-common (3.0pl1-143) ...
  dpkg: error processing archive 
/var/cache/apt/archives/cron-daemon-common_3.0pl1-143_all.deb (--unpack):
   trying to overwrite '/etc/cron.d/.placeholder', which is also in package 
systemd-cron 1.15.18-1
  Errors were encountered while processing:
   /var/cache/apt/archives/cron-daemon-common_3.0pl1-143_all.deb

For bcron the conflicting file is only
  /etc/crontab

For systemd-cron the conflicting files are
  /etc/cron.d/.placeholder
  /etc/cron.daily/.placeholder
  /etc/cron.hourly/.placeholder
  /etc/cron.monthly/.placeholder
  /etc/cron.weekly/.placeholder
  /etc/crontab
 
These two alternative cron implementations need to start using
cron-daemon-common for these shared files first before you can
add the corresponding Breaks+Replaces against them.


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: cron
Source-Version: 3.0pl1-144
Done: Georges Khaznadar 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Jun 2022 18:33:28 +0200
Source: cron
Architecture: source
Version: 3.0pl1-144
Distribution: unstable
Urgency: medium
Maintainer: Javier Fernández-Sanguino Peña 
Changed-By: Georges Khaznadar 
Closes: 1012596
Changes:
 cron (3.0pl1-144) unstable; urgency=medium
 .
   * added versioned Conflicts/Replaces clauses for bcron and systemd-cron
 Closes: #1012596
   * added Conflicts/Replaces clauses between cron and other packages providing
 cron-daemon.
Checksums-Sha1:
 f706cbf7a403ee563911ccefb87766b5b630f2d2 2114 cron_3.0pl1-144.dsc
 6c5ced065bfd0e99359fef8d6a1d05d9401e5eab 110572 cron_3.0pl1-144.debian.tar.xz
 b5dbbb5418642c11be924ad22d80a1d0910a5c34 5994 cron_3.0pl1-144_source.buildinfo
Checksums-Sha256:
 acf9a3da6bdb92f6996e878043e384186fadd6359c71e03c2609604c7050 2114 
cron_3.0pl1-144.dsc
 fa5a83f9b133cfef4cb6717b85d63ff39708f9778e09bb5702e37530fcfa32ff 110572 
cron_3.0pl1-144.debian.tar.xz
 cb80e239ab5b9ffb57cc838ba55ceaa1ed3e8fb38a390eefcb8a4b08782c3f81 5994 
cron_3.0pl1-144_source.buildinfo
Files:
 c0c039bd994ff630c87084488e487511 2114 admin important cron_3.0pl1-144.dsc
 022068ad27f75bc75c1aca71fd659806 110572 admin important 
cron_3.0pl1-144.debian.tar.xz
 41a72236ec94e5654777cb9bdbf219ff 5994 admin important 
cron_3.0pl1-144_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1012793: libpyside2-py3-5.15 uninstallable on unstable: unsatisfiable Depends

[Julian Gilbey]

On Tue, Jun 14, 2022 at 10:43:34AM +0300, Dmitry Shachnev wrote:
> Hi Julian!
> 
> On Tue, Jun 14, 2022 at 08:37:38AM +0100, Julian Gilbey wrote:
> > Package: libpyside2-py3-5.15
> > Version: 5.15.2-2.1
> > Severity: serious
> > 
> > This package depends on qtbase-abi-5-15-2 and
> > qtdeclarative-abi-5-15-2, but libqt5core5a now Provides:
> > qtbase-abi-5-15-4 and libqt5qml5 now Provides:
> > qtdeclarative-abi-5-15-4.  The dependencies of this package need
> > updating to bring them into sync.
> 
> We are now in a middle of Qt 5.15.4 transition [1][2]. Wait a couple of days,
> pyside2 will be rebuilt by the Release team.
> 
> [1]: https://release.debian.org/transitions/html/qtbase-abi-5-15-4.html
> [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007170

Hi Dmitry,

Amazing, thanks!

   Julian

Processed: severity of 1012795 is grave

[Debian Bug Tracking System]

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

> severity 1012795 grave
Bug #1012795 [libengine-gost-openssl1.1] libengine-gost-openssl1.1: Shared 
library file in /
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#1012485: marked as done (barbican: autopkgtests fail under OpenSSL 3)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jun 2022 09:33:55 +
with message-id 
and subject line Bug#1012485: fixed in barbican 1:14.0.0-3
has caused the Debian Bug report #1012485,
regarding barbican: autopkgtests fail under OpenSSL 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.)


-- 
1012485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: barbican
Version: 1:14.0.0-2
Severity: normal

In sid, with OpenSSL 3, the following barbican test fails in the
autopkgtest:

==
FAIL: 
barbican.tests.common.test_validators.WhenTestingSimpleCMCOrderValidator.test_should_raise_with_unsigned_pkcs10_data
barbican.tests.common.test_validators.WhenTestingSimpleCMCOrderValidator.test_should_raise_with_unsigned_pkcs10_data
--
testtools.testresult.real._StringException: Traceback (most recent call last):
  File 
"/tmp/autopkgtest.QMCrjK/build.2Gf/src/barbican/tests/common/test_validators.py",
 line 1435, in test_should_raise_with_unsigned_pkcs10_data
certs.create_csr_that_has_not_been_signed())
  File 
"/tmp/autopkgtest.QMCrjK/build.2Gf/src/barbican/tests/certificate_utils.py", 
line 53, in create_csr_that_has_not_been_signed
pem = crypto.dump_certificate_request(crypto.FILETYPE_PEM, csr)
  File "/usr/lib/python3/dist-packages/OpenSSL/crypto.py", line 2969, in 
dump_certificate_request
_openssl_assert(result_code != 0)
  File "/usr/lib/python3/dist-packages/OpenSSL/_util.py", line 71, in 
openssl_assert
exception_from_error_queue(error)
  File "/usr/lib/python3/dist-packages/OpenSSL/_util.py", line 57, in 
exception_from_error_queue
raise exception_type(errors)
OpenSSL.crypto.Error: [('asn1 encoding routines', '', 'illegal zero content'), 
('PEM routines', '', 'ASN1 lib')]


--
Ran 1488 tests in 38.966s

FAILED (failures=1, skipped=56)

Looks like the test was relying on unsupported behaviour in OpenSSL to
create at unsigned CSR in the past.

SR
--- End Message ---
--- Begin Message ---
Source: barbican
Source-Version: 1:14.0.0-3
Done: Thomas Goirand 

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

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

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated barbican 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, 14 Jun 2022 10:58:03 +0200
Source: barbican
Architecture: source
Version: 1:14.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 1012485
Changes:
 barbican (1:14.0.0-3) unstable; urgency=medium
 .
   * Also blacklist test_should_raise_with_unsigned_pkcs10_data() in
 autopkgtest (Closes: #1012485).
Checksums-Sha1:
 6d6c8ce5e9d31655c90c5ce1dd092021d04fe828 3660 barbican_14.0.0-3.dsc
 7b6524196c23a3e7e653069f158770f4baaeeffa 10048 barbican_14.0.0-3.debian.tar.xz
 9f298c05edfce290ab9c03b2ccc4bd0c998e717a 21640 
barbican_14.0.0-3_amd64.buildinfo
Checksums-Sha256:
 5e29b14d255bc8a31f883f518293a73def151c2bf55f4d77863bae46ea6f0bb3 3660 
barbican_14.0.0-3.dsc
 79547dbd62cfb268223f30df6e5eace370cbe2c2cdb161fd7e586b3027b2bffd 10048 
barbican_14.0.0-3.debian.tar.xz
 73f7c734fb3c4bc97850135892fc0e2cf491ca67ed745a2d5e91421e8a784637 21640 
barbican_14.0.0-3_amd64.buildinfo
Files:
 e3b995621de558afee4fc7638278955c 3660 net optional barbican_14.0.0-3.dsc
 032edc48164f8c6b0cedb304fc7ae438 10048 net optional 
barbican_14.0.0-3.debian.tar.xz
 148b523e8f1cc7a3d74647ae73f7bce7 21640 net optional 
barbican_14.0.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmKoUxoACgkQ1BatFaxr
Q/5Y5RAAkm069+G6fq28muxNAxUqqHQ+oCwB6LWEPAwciLDOXKl8H2G1gWl9ZI+B
W/8gVeVZThUwruiWu39A570pkhYlvIwhJxA7O9UWHZe34t6PU5R7nn73yiXH7inZ
Bo1fpcUCg9nSkQcNrxQSZCVl05b82lehGII6shxNRx0qP/nbfFQ+kw2ZMZXeuNaP

Processed: Bug#1012485 marked as pending in barbican

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1012485 [src:barbican] barbican: autopkgtests fail under OpenSSL 3
Added tag(s) pending.

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

Bug#1012485: marked as pending in barbican

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1012485 in barbican 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/openstack-team/services/barbican/-/commit/f2c7b9aa8b4be6fd1d0fece40ecdf85a6e51f5bd


* Also blacklist test_should_raise_with_unsigned_pkcs10_data() in
autopkgtest (Closes: #1012485).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1012485

Bug#1011838: marked as done (xonsh: FTBFS: ModuleNotFoundError: No module named 'attr')

[Debian Bug Tracking System]

Your message dated Tue, 14 Jun 2022 03:04:41 -0600
with message-id 

and subject line Bug#1011838: markexonsh: FTBFS: ModuleNotFoundError: No module 
named 'attr'
has caused the Debian Bug report #1011838,
regarding xonsh: FTBFS: ModuleNotFoundError: No module named 'attr'
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.)


-- 
1011838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xonsh
Version: 0.12.4+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/docs'
> sphinx-build -b html -d _build/doctrees   . _build/html
> Running Sphinx v4.5.0
> 
> Exception occurred:
>   File "/usr/lib/python3/dist-packages/myst_parser/main.py", line 3, in 
> 
> import attr
> ModuleNotFoundError: No module named 'attr'
> The full traceback has been saved in /tmp/sphinx-err-f46ojpq1.log, if you 
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error 
> message can be provided next time.
> A bug report can be filed in the tracker at 
> . Thanks!
> make[2]: *** [Makefile:39: html] Error 2


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/xonsh_0.12.4+dfsg-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: myst-parser
Source-Version: 0.17.2-1
Done: Emmanuel Arias 

This FTBFS in xonsh, which was caused by myst-parser introduction of
"from attr import Attribute" without the corresponding dependency on
python3-attr, was fixed by the upload of myst-parser/0.17.2-1 where
`attrs` was replaced with `dataclasses` (part of
libpython3.10-stdlib).

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.

Cheers!

myst-parser (0.17.2-1) unstable; urgency=medium

  * New upstream version.
  * d/patches: Remove patches, all of them are in the new upstream release.
  * d/control: Bump Standards-Version to 4.6.1 (from 4.6.0.1; no further
changes).
  * d/control: Use flit instead of python3-setuptools to build package.
  * d/control: Add python3-typing-extensions as Build Depends.
  * d/rules: Ignore tests that use pytest_param_files that is not in Debian
yet.
- d/tests/unittests: Also ignore them in autopkgtest run.
  * d/tests/control: Write explicitly the packages that are need for run
autopkgtest instead of use @builddeps@.

 -- Emmanuel Arias   Sat, 28 May 2022 10:45:26 -0300--- End Message ---

Processed: closing 1011203

[Debian Bug Tracking System]

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

> close 1011203 0.8.9-1
Bug #1011203 [src:r-cran-markovchain] r-cran-markovchain: FTBFS with 
onetbb/2021.5.0-8 in experimental
Marked as fixed in versions r-cran-markovchain/0.8.9-1.
Bug #1011203 [src:r-cran-markovchain] r-cran-markovchain: FTBFS with 
onetbb/2021.5.0-8 in experimental
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: tagging 1011222

[Debian Bug Tracking System]

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

> tags 1011222 + bookworm sid
Bug #1011222 [src:r-cran-rstanarm] r-cran-rstanarm: FTBFS with 
onetbb/2021.5.0-8 in experimental
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

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

Processed: ruby-uglifier: FTBFS: tests fail: uglifier_spec.rb:383, uglifier_spec.rb:751

[Debian Bug Tracking System]

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

> tags 981224 + bookworm sid
Bug #981224 [src:ruby-uglifier] ruby-uglifier: FTBFS: tests fail: 
uglifier_spec.rb:383, uglifier_spec.rb:751
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1011838: xonsh: FTBFS: ModuleNotFoundError: No module named 'attr'

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python3-myst-parser
Bug #1011838 [src:xonsh] xonsh: FTBFS: ModuleNotFoundError: No module named 
'attr'
Bug reassigned from package 'src:xonsh' to 'python3-myst-parser'.
No longer marked as found in versions xonsh/0.12.4+dfsg-1.
Ignoring request to alter fixed versions of bug #1011838 to the same values 
previously set
> affects -1 + xonsh
Bug #1011838 [python3-myst-parser] xonsh: FTBFS: ModuleNotFoundError: No module 
named 'attr'
Added indication that 1011838 affects xonsh
> found -1 python3-myst-parser/0.16.1-1
Bug #1011838 [python3-myst-parser] xonsh: FTBFS: ModuleNotFoundError: No module 
named 'attr'
The source python3-myst-parser and version 0.16.1-1 do not appear to match any 
binary packages
Marked as found in versions python3-myst-parser/0.16.1-1.
> found -1 python3-myst-parser/0.16.1-2
Bug #1011838 [python3-myst-parser] xonsh: FTBFS: ModuleNotFoundError: No module 
named 'attr'
The source python3-myst-parser and version 0.16.1-2 do not appear to match any 
binary packages
Marked as found in versions python3-myst-parser/0.16.1-2.
> found -1 python3-myst-parser/0.16.1-3
Bug #1011838 [python3-myst-parser] xonsh: FTBFS: ModuleNotFoundError: No module 
named 'attr'
The source python3-myst-parser and version 0.16.1-3 do not appear to match any 
binary packages
Marked as found in versions python3-myst-parser/0.16.1-3.
> found -1 python3-myst-parser/0.16.1-4
Bug #1011838 [python3-myst-parser] xonsh: FTBFS: ModuleNotFoundError: No module 
named 'attr'
The source python3-myst-parser and version 0.16.1-4 do not appear to match any 
binary packages
Marked as found in versions python3-myst-parser/0.16.1-4.
> fixed -1 python3-myst-parser/0.17.2-1
Bug #1011838 [python3-myst-parser] xonsh: FTBFS: ModuleNotFoundError: No module 
named 'attr'
The source python3-myst-parser and version 0.17.2-1 do not appear to match any 
binary packages
Marked as fixed in versions python3-myst-parser/0.17.2-1.

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

Bug#1011838: xonsh: FTBFS: ModuleNotFoundError: No module named 'attr'

[Anthony Fok]

Control: reassign -1 python3-myst-parser
Control: affects -1 + xonsh
Control: found -1 python3-myst-parser/0.16.1-1
Control: found -1 python3-myst-parser/0.16.1-2
Control: found -1 python3-myst-parser/0.16.1-3
Control: found -1 python3-myst-parser/0.16.1-4
Control: fixed -1 python3-myst-parser/0.17.2-1

On Thu, May 26, 2022 at 1:26 PM Lucas Nussbaum  wrote:
>
> Source: xonsh
> Version: 0.12.4+dfsg-1
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20220525 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
> > make[2]: Entering directory '/<>/docs'
> > sphinx-build -b html -d _build/doctrees   . _build/html
> > Running Sphinx v4.5.0
> >
> > Exception occurred:
> >   File "/usr/lib/python3/dist-packages/myst_parser/main.py", line 3, in 
> > 
> > import attr
> > ModuleNotFoundError: No module named 'attr'
> > The full traceback has been saved in /tmp/sphinx-err-f46ojpq1.log, if you 
> > want to report the issue to the developers.
> > Please also report this if it was a user error, so that a better error 
> > message can be provided next time.
> > A bug report can be filed in the tracker at 
> > . Thanks!
> > make[2]: *** [Makefile:39: html] Error 2
>
>
> The full build log is available from:
> http://qa-logs.debian.net/2022/05/25/xonsh_0.12.4+dfsg-1_unstable.log
>
> All bugs filed during this archive rebuild are listed at:
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org
> or:
> https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=lu...@debian.org=1=1=1=1#results
>
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
>
> If you reassign this bug to another package, please marking it as 
> 'affects'-ing
> this package. See https://www.debian.org/Bugs/server-control#affects
>
> If you fail to reproduce this, please provide a build log and diff it with 
> mine
> so that we can identify if something relevant changed in the meantime.

As it turns out, this is not a bug in xonsh, but rather in
python3-myst-parser 0.16.1 where
the line "from attr import Attribute" was added, but without
dependency on the python3-attr.
xonsh became a "victim" of that missing dependency.

The good news is that the xonsh FTBFS problem is fixed with the upload
of python3-myst-parser 0.17.2-1 where upstream did this:

- ♻️ REFACTOR: Replace `attrs` by `dataclasses` for configuration (#557)

The 'attr' module is no longer needed, hence no more FTBFS for xonsh!

Special thanks to Emmanuel Arias and Bastian Germann for the upload of
myst-parser 0.17.2-1 which resolves this bug.

I am hereby reassigning this bug to python3-myst-parser, and will
close the bug shortly after.

Cheers,

Anthony Fok

Bug#1012786: libcamera: Fails to build from source

[Christopher Obbard]

Hi!

I propose a patch to potentially fix this: 
https://salsa.debian.org/multimedia-team/libcamera/-/merge_requests/6


The use of the depreciated function could even be fixed in upstream, it 
could be worth updating the package from upstream?


@Andrew: can you review the patch above? Also, I can help with updating 
from upstream if you would like.


Chris

On 14/06/2022 03:02, Lisandro Damián Nicanor Pérez Meyer wrote:

Source: libcamera
Version: 0~git20200629+e7aa92a-8
Severity: serious
Justification: Fails to build form source
X-Debbugs-Cc: lisan...@debian.org

Trying to fix a bug in libcamera I found it's currently failing to build
from source. Seems it's taking deprecation warnings as errors.

Log follows. Kinds regards, Lisandro.

../test/gstreamer/gstreamer_multi_stream_test.cpp: In member function ‘virtual 
int GstreamerMultiStreamTest::run()’:
../test/gstreamer/gstreamer_multi_stream_test.cpp:90:76: error: ‘GstPad* 
gst_element_get_request_pad(GstElement*, const gchar*)’ is deprecated: Use 
'gst_element_request_pad_simple' instead [-Werror=deprecated-declarations]
90 | g_autoptr(GstPad) request_pad = 
gst_element_get_request_pad(libcameraSrc_, "src_%u");
   | 
~~~^
In file included from /usr/include/gstreamer-1.0/gst/gstbin.h:27,
  from /usr/include/gstreamer-1.0/gst/gst.h:35,
  from ../test/gstreamer/gstreamer_multi_stream_test.cpp:13:
/usr/include/gstreamer-1.0/gst/gstelement.h:1042:25: note: declared here
  1042 | GstPad* gst_element_get_request_pad (GstElement 
*element, const gchar *name);
   | ^~~
cc1plus: all warnings being treated as errors
[246/390] /usr/bin/meson --internal symbolextractor 
'/<>/obj-x86_64-linux-gnu' 
src/libcamera/base/libcamera-base.so.0.0.0 src/libcamera/base/libcamera-base.so.0.0.0 
src/libcamera/base/libcamera-base.so.0.0.0.p/libcamera-base.so.0.0.0.symbols
[247/390] ccache c++ -Itest/stream/stream_formats.p -Itest/stream -I../test/stream 
-Itest/libtest -I../test/libtest -Iinclude -I../include -Iinclude/libcamera 
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor 
-Wextra -Werror -std=c++17 -O0 -Wshadow -include config.h -g -O2 
'-ffile-prefix-map=/<>=.' -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ 
test/stream/stream_formats.p/stream_formats.cpp.o -MF 
test/stream/stream_formats.p/stream_formats.cpp.o.d -o 
test/stream/stream_formats.p/stream_formats.cpp.o -c ../test/stream/stream_formats.cpp
[248/390] ccache c++ -Itest/serialization/control_serialization.p -Itest/serialization 
-I../test/serialization -Itest/libtest -I../test/libtest -Iinclude -I../include 
-Iinclude/libcamera/ipa -Iinclude/libcamera -fdiagnostics-color=always 
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -Wextra -Werror -std=c++17 
-O0 -Wshadow -include config.h -g -O2 '-ffile-prefix-map=/<>=.' 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-DLIBCAMERA_BASE_PRIVATE -MD -MQ 
test/serialization/control_serialization.p/serialization_test.cpp.o -MF 
test/serialization/control_serialization.p/serialization_test.cpp.o.d -o 
test/serialization/control_serialization.p/serialization_test.cpp.o -c 
../test/serialization/serialization_test.cpp
[249/390] ccache c++ -Itest/serialization/ipa_data_serializer_test.p -Itest/serialization 
-I../test/serialization -Itest/libtest -I../test/libtest -Iinclude -I../include 
-Iinclude/libcamera/ipa -Iinclude/libcamera -fdiagnostics-color=always 
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -Wextra -Werror -std=c++17 
-O0 -Wshadow -include config.h -g -O2 '-ffile-prefix-map=/<>=.' 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-DLIBCAMERA_BASE_PRIVATE -MD -MQ 
test/serialization/ipa_data_serializer_test.p/serialization_test.cpp.o -MF 
test/serialization/ipa_data_serializer_test.p/serialization_test.cpp.o.d -o 
test/serialization/ipa_data_serializer_test.p/serialization_test.cpp.o -c 
../test/serialization/serialization_test.cpp
[250/390] ccache c++ -Itest/serialization/control_serialization.p -Itest/serialization 
-I../test/serialization -Itest/libtest -I../test/libtest -Iinclude -I../include 
-Iinclude/libcamera/ipa -Iinclude/libcamera -fdiagnostics-color=always 
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -Wextra -Werror -std=c++17 
-O0 -Wshadow -include config.h -g -O2 '-ffile-prefix-map=/<>=.' 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-DLIBCAMERA_BASE_PRIVATE -MD -MQ 
test/serialization/control_serialization.p/control_serialization.cpp.o -MF 
test/serialization/control_serialization.p/control_serialization.cpp.o.d -o 

Bug#1012793: libpyside2-py3-5.15 uninstallable on unstable: unsatisfiable Depends

[Dmitry Shachnev]

Hi Julian!

On Tue, Jun 14, 2022 at 08:37:38AM +0100, Julian Gilbey wrote:
> Package: libpyside2-py3-5.15
> Version: 5.15.2-2.1
> Severity: serious
> 
> This package depends on qtbase-abi-5-15-2 and
> qtdeclarative-abi-5-15-2, but libqt5core5a now Provides:
> qtbase-abi-5-15-4 and libqt5qml5 now Provides:
> qtdeclarative-abi-5-15-4.  The dependencies of this package need
> updating to bring them into sync.

We are now in a middle of Qt 5.15.4 transition [1][2]. Wait a couple of days,
pyside2 will be rebuilt by the Release team.

[1]: https://release.debian.org/transitions/html/qtbase-abi-5-15-4.html
[2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007170

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#1012793: libpyside2-py3-5.15 uninstallable on unstable: unsatisfiable Depends

[Julian Gilbey]

Package: libpyside2-py3-5.15
Version: 5.15.2-2.1
Severity: serious

This package depends on qtbase-abi-5-15-2 and
qtdeclarative-abi-5-15-2, but libqt5core5a now Provides:
qtbase-abi-5-15-4 and libqt5qml5 now Provides:
qtdeclarative-abi-5-15-4.  The dependencies of this package need
updating to bring them into sync.

Best wishes,

   Julian