Bug#1004843: debina bullseye: ping (from iputils-ping) throwing inappropriate error message if IPv6 is disabled

[Binarus]

Package: iputils-ping
Version: 3:20210202-1
Severity: critical
Tags: fixed-upstream ipv6 bullseye
Owner: no...@debian.org

O/S: Debian bullseye 11.2
Kernel: Linux binkg-vpn01 5.10.0-11-amd64 #1 SMP Debian 5.10.92-1 (2022-01-18) 
x86_64 GNU/Linux

When I invoke ping, it throws an inappropriate error message. The message is "ping: 
socket: Address family not supported by protocol". Please consider the following 
excerpt from a terminal session:

root@binkg-vpn01 /etc/ssh # ping www.google.de
ping: socket: Address family not supported by protocol
PING www.google.de (142.251.37.3) 56(84) bytes of data.
64 bytes from muc11s23-in-f3.1e100.net (142.251.37.3): icmp_seq=1 ttl=118 
time=7.30 ms
...

The error message occurs because I have disabled IPv6 *via kernel command line*; that is, 
my *kernel command line* includes the option "ipv6.disable=1".

In this situation, ping obviously insists on obtaining an IPv6 socket although 
IPv6 is disabled.

IMPORTANT NOTE:
According to other reports of the same problem, ping behaves correctly when 
IPv6 is *not* disabled at the kernel command line, but *is* instead disabled 
via sysctl (e.g. sysctl -w net.ipv6.conf.all.disable_ipv6=1). The problem 
occurs only when IPv6 is disabled at the kernel command line. Please note also 
that disabling it via sysctl *in addition* to disabling it at the kernel 
command line does not solve the problem. Actually, it does not change anything, 
because the respective sysctl option does not have any effect if IPv6 is 
already disabled at the kernel command line.

ping's misbehavior in this situation is not acceptable. Many people have IPv6 disabled at 
the kernel command line, and ping's misbehavior breaks a lot of Nagios scripts for them, 
which is why I have assigned the "critical" severity level.

Please fix this as soon as possible. This bug is well-known and has been fixed 
upstream 4 (yes: four!) months ago. Please refer to the following discussion:

https://github.com/iputils/iputils/issues/293

Thank you very much, and best regards,

Binarus

Processed: tagging 1004223

[Debian Bug Tracking System]

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

> tags 1004223 + upstream fixed-upstream
Bug #1004223 {Done: Salvatore Bonaccorso } [minetest-server] 
minetest-server: ItemStack meta injection vulnerability in Minetest 
(CVE-2022-24300)
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.

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

Processed: retitle 1004223 to minetest-server: ItemStack meta injection vulnerability in Minetest (CVE-2022-24300)

[Debian Bug Tracking System]

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

> retitle 1004223 minetest-server: ItemStack meta injection vulnerability in 
> Minetest (CVE-2022-24300)
Bug #1004223 {Done: Salvatore Bonaccorso } [minetest-server] 
minetest-server: ItemStack meta injection vulnerability in Minetest 5.3
Changed Bug title to 'minetest-server: ItemStack meta injection vulnerability 
in Minetest (CVE-2022-24300)' from 'minetest-server: ItemStack meta injection 
vulnerability in Minetest 5.3'.
> thanks
Stopping processing here.

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

Processed: Re: Bug#989384: acpi-call-dkms: new version of linux-call-dkms in https://github.com/nix-community/acpi_call

[Debian Bug Tracking System]

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

> severity 989384 important
Bug #989384 [acpi-call-dkms] acpi-call-dkms: new version of linux-call-dkms in 
https://github.com/nix-community/acpi_call
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Processed: glurp: diff for NMU version 0.12.3-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 96 + patch
Bug #96 [src:glurp] glurp: Removal of obsolete debhelper compat 5 and 6 in 
bookworm
Added tag(s) patch.
> tags 96 + pending
Bug #96 [src:glurp] glurp: Removal of obsolete debhelper compat 5 and 6 in 
bookworm
Added tag(s) pending.

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

Bug#965555: glurp: diff for NMU version 0.12.3-1.1

[Joao Eriberto Mota Filho]

Control: tags 96 + patch
Control: tags 96 + pending

Dear maintainer,

I've prepared an NMU for glurp (versioned as 0.12.3-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer or cancel the upload.

Regards,

Eriberto

diff -u glurp-0.12.3/debian/changelog glurp-0.12.3/debian/changelog
--- glurp-0.12.3/debian/changelog
+++ glurp-0.12.3/debian/changelog
@@ -1,3 +1,19 @@
+glurp (0.12.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+   * Using new DH level format. Consequently:
+   - debian/compat: removed.
+   - debian/control: changed from 'debhelper' to 'debhelper-compat' in
+ Build-Depends field and bumped level to 13.
+   - Closes: #96
+   * Dropped CDBS in favor of the debhelper to allow the build system to use
+ DH level greater than 11. Consequently:
+   - debian/control: removed no longer needed cdbs from Build-Depends
+ field.
+   - debian/rules: changed from CDBS to DH.
+
+ -- Joao Eriberto Mota Filho   Tue, 01 Feb 2022 23:55:04 
-0300
+
 glurp (0.12.3-1) unstable; urgency=medium
 
   * New upstream release (Closes: #333640, #379667, #385088, #359096, #581933).
reverted:
--- glurp-0.12.3/debian/compat
+++ glurp-0.12.3.orig/debian/compat
@@ -1 +0,0 @@
-5
diff -u glurp-0.12.3/debian/rules glurp-0.12.3/debian/rules
--- glurp-0.12.3/debian/rules
+++ glurp-0.12.3/debian/rules
@@ -3,4 +3,4 @@
 
-include /usr/share/cdbs/1/rules/debhelper.mk
-include /usr/share/cdbs/1/class/autotools.mk
+%:
+   dh $@
 
diff -u glurp-0.12.3/debian/control glurp-0.12.3/debian/control
--- glurp-0.12.3/debian/control
+++ glurp-0.12.3/debian/control
@@ -2,7 +2,7 @@
 Section: x11
 Priority: optional
 Maintainer: Stanislav Maslovski 
-Build-Depends: debhelper (>= 5), libgtk2.0-dev (>= 2.4), libglib2.0-dev (>= 
2.4), libmpd-dev, cdbs
+Build-Depends: debhelper-compat (= 13), libgtk2.0-dev (>= 2.4), libglib2.0-dev 
(>= 2.4), libmpd-dev
 Standards-Version: 3.8.4
 Homepage: http://sourceforge.net/projects/glurp/
 

Processed: tagging 1002367

[Debian Bug Tracking System]

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

> tags 1002367 + pending
Bug #1002367 [src:python-pygal] python-pygal: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit 
code 13
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1004780: marked as done (gnome-initial-setup: FTBFS in unstable)

[Debian Bug Tracking System]

Your message dated Tue, 01 Feb 2022 23:33:55 +
with message-id 
and subject line Bug#1004780: fixed in gnome-initial-setup 41.2-2
has caused the Debian Bug report #1004780,
regarding gnome-initial-setup: FTBFS in unstable
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.)


-- 
1004780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004780
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-initial-setup
Version: 41.2-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs

gnome-initial-setup FTBFS in unstable:

Configuring config.h using configuration
Configuring gnome-initial-setup-copy-worker.desktop.in using configuration

../data/meson.build:33:9: ERROR: Function does not take positional arguments.

A full log can be found at 
/<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt


Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: gnome-initial-setup
Source-Version: 41.2-2
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gnome-initial-setup 
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, 01 Feb 2022 23:03:00 +
Source: gnome-initial-setup
Architecture: source
Version: 41.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 1004780
Changes:
 gnome-initial-setup (41.2-2) unstable; urgency=medium
 .
   * Team upload
   * d/patches: Update to upstream gnome-41 branch commit 41.2-2-g916995f0
 - Update Icelandic translation
   * d/p/build-Fix-Meson-deprecation-warning.patch:
 Add patch from upstream to fix FTBFS with recent Meson
 (Closes: #1004780)
Checksums-Sha1:
 9dbde275c69676b6e8a1977521b81e34e705970b 3200 gnome-initial-setup_41.2-2.dsc
 b27114a630558d3473c74507bea2c2a2e009ca3c 15556 
gnome-initial-setup_41.2-2.debian.tar.xz
 74e958a7b53a162475c23f970eec4cd3e0ee69f7 28542 
gnome-initial-setup_41.2-2_source.buildinfo
Checksums-Sha256:
 685f60f1c04be3aed146d18f83edacdb05e839550e357ad3ed73e148aeb8f273 3200 
gnome-initial-setup_41.2-2.dsc
 051f3ce3e396b25bfefde99ab2e6cb1459dbd6e9c6b0571b0da4868f46fef3a7 15556 
gnome-initial-setup_41.2-2.debian.tar.xz
 74dbe6d5ff0401d9523cc1aac4a703132f4e7c09a8ced2565e6ad899bd279043 28542 
gnome-initial-setup_41.2-2_source.buildinfo
Files:
 de0fc10c4b2a32d63865d1470d5f1b23 3200 gnome optional 
gnome-initial-setup_41.2-2.dsc
 0aef3c25a2118f0fae3da35abaf768e3 15556 gnome optional 
gnome-initial-setup_41.2-2.debian.tar.xz
 cb23b315d28b1f7e88bdd71a5d7941b1 28542 gnome optional 
gnome-initial-setup_41.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmH5wH8ACgkQ4FrhR4+B
TE+95xAAsTs+dfxwTPoW0U+KaIE1vr06SnaKRKwOXTXXyEbEBfpVdTnKnpDf5g7j
3P5cdq6OPKX/O3MMBU9JoGK5FIlb4u1/tnOGJPqj3MWbDi/E5qd4RI5XzBXMwdUU
h+XfjFQKcET4s/AJTQXVbRYxnymXNhp+rbnLYOoUvZRPLN+y5Fxp5kREuFyKmEjb
O4APxxIzj2PMUNRukQozFOWjWXI58BdYnfYpIDIuiK3R5epWq0GgmEWVdxVzD9Wl
Obnv5C6wwIbP36Jb8rLA/6hKfBU1qnMXmsRTX8RmsgZOLe55iz+UdzmyMRbSyVv8
QMOFfVhTKXMGmzX2/Y29ummx8sLUGlCSGpTy+pPwe3xk3mld/htZS2qKmO4nLShP
BkEKeVF8/uURjEY59YgSmP7j7UnGjdIMbV9LBjPaoN0Q03SMYH4ahJvLwpUD7zy6
T75OOdT+R0t++0ccMWq0DRNVphSVM3GNaRGuKXhzQBjbUTZ0sef4Q/Fb625ZMLSF
BFJBoVLcMXCunaE/D2cpxcaXXSMYciYtUiJYtGwSmdCrWSElpFCSwSDF4XUzzfDF
7NpAco/eBh4avCwphOdwyuKv2GeLItTwSJzdh5Imu+1V73SzVjsBtbBl9DOhO+L9
TyhxXvmPFgdYM7BKEbIX6h+v8ShPsse6RLBPWp+0wndPJ22UoW0=
=0MyC
-END PGP SIGNATURE End Message ---

Bug#1004761: marked as done (gnome-control-center: FTBFS)

[Debian Bug Tracking System]

Your message dated Tue, 01 Feb 2022 23:33:48 +
with message-id 
and subject line Bug#1004761: fixed in gnome-control-center 1:41.2-2
has caused the Debian Bug report #1004761,
regarding gnome-control-center: FTBFS
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.)


-- 
1004761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004761
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-control-center
Version: 1:41.2-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs

gnome-control-center FTBFS in unstable:
| Configuring gnome-applications-panel.desktop.in using configuration
|
| ../panels/applications/meson.build:10:5: ERROR: Function does not take 
positional arguments.
|
| A full log can be found at 
/<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: gnome-control-center
Source-Version: 1:41.2-2
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gnome-control-center 
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, 01 Feb 2022 22:56:12 +
Source: gnome-control-center
Architecture: source
Version: 1:41.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 1004761
Changes:
 gnome-control-center (1:41.2-2) unstable; urgency=medium
 .
   * Team upload
   * d/patches: Update to gnome-41 branch commit 41.2-19-g600b0a014
 - Fix build with recent meson versions (Closes: #1004761)
 - Do not invert order of video modes, which can result in a lower
   than intended refresh rate being selected for a non-preferred mode
 - Adjust icon for default applications panel
 - Ensure sound recording level indicator is cleared when microphone
   is unplugged
 - Translation updates
Checksums-Sha1:
 b2ed0d130d97415c0e80a03cc01331c26cfb42d7 3890 gnome-control-center_41.2-2.dsc
 1d7856d9ed62f97dafad497fe3c0ad06a0f700a3 116628 
gnome-control-center_41.2-2.debian.tar.xz
 a6b9b0404b1090e6a97e67cd03620468729d9f3b 30022 
gnome-control-center_41.2-2_source.buildinfo
Checksums-Sha256:
 0c950c59fdef5267f802c293e45c4f32c2de2b342c013b533f185816f60d7348 3890 
gnome-control-center_41.2-2.dsc
 8358b5f180c464548a57bfdd4314dcc66042fa013f83f8feb45da0ce781de6da 116628 
gnome-control-center_41.2-2.debian.tar.xz
 f14a5e4eb9804088e426b48a920cae0bd15d40c6978cbea5d749d5bee5b2dbeb 30022 
gnome-control-center_41.2-2_source.buildinfo
Files:
 148f72a2275061c7c527d2e12b172ce7 3890 gnome optional 
gnome-control-center_41.2-2.dsc
 2c511aabe5ad6351b2eb5f7605fb5426 116628 gnome optional 
gnome-control-center_41.2-2.debian.tar.xz
 b95c4477310ee2acae55b489c9b372b7 30022 gnome optional 
gnome-control-center_41.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmH5v7IACgkQ4FrhR4+B
TE8HuRAAodYyptRTCIb2gkuAoJZA8QTVQ280xs9IDvtSGJYfbSDf2u6+OdPQ7EyO
K9AlGmlAyhTMs3axmrqtgUbBXLslQjSMSMjIgUTKr00YcQOJ3Ru3rImL8ZlZjGCJ
YpW/T66QGl1U/WFIln7p7oh5VupYDBdxKwrIcSUtQGDEvWjgyGmkYvxcEjWvPvcw
lJzmHq2hM9ijC+bDH5UGWWEcjAJHXfHiCsiqL5vl1g7Hevi5mfXC2l4pB3cc33q4
KM5O6cXCsdKZ0tqNnC+VMOIGcAGV7QbKwyyvEj/Ymc4dBstZzZnC1rVtSF6wwGTC
7xGStEjOutJF/i3xWpNf7TM5uufYE0lNGO6jx91hseRqUwgv4Zmckdwgdn5TzrPs
ct76O1mbkVMfFA+vtPVQtU9xEY+AzsQlJiP9Fsrhrdi22xYtBVZFn3en8BEuPgWb
hy56mCw9lIWX+zHAsWxyJobmVcLrx4T2bPbOyYOV0pW5xK+JLdOiqsKS7cmU3zXW
BP1irbR50P5MyrNGWLgK50tf3BuYmpokD24+fknJ4W6/PWuav1g9sri9mu9YSx8y
YDa6QrozDZrB6d/Y24GpiNsSa/yvC08xUd5+zwmLFRtT4E6grO4iTCzDVWBKl0Ws
T7bZVg5IPH9Lb2mXDks3ZYVTjVvh3bmonYM8Ccy+vgL+hy0qjuw=
=H3MK
-END PGP SIGNATURE End Message ---

Processed: Bug#1004780 marked as pending in gnome-initial-setup

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1004780 [src:gnome-initial-setup] gnome-initial-setup: FTBFS in unstable
Added tag(s) pending.

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

Bug#1004780: marked as pending in gnome-initial-setup

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #1004780 in gnome-initial-setup reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/gnome-initial-setup/-/commit/47167435866b812a154a5b0bbce552e573a18cb9


Add patch from upstream to fix FTBFS with recent Meson

Closes: #1004780


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1004780

Bug#1004212: closing 1004212

[Daniel Gröber]

close 1004212 1.01+20211229git48498af+dfsg-2
thanks

Fixe by 
https://salsa.debian.org/science-team/berkeley-abc/-/commit/cf6ed6eb2ce4b9ea0494d4d145f8bc1a6d47d2f5

Thanks,
--Daniel

Processed: closing 1004212

[Debian Bug Tracking System]

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

> close 1004212 1.01+20211229git48498af+dfsg-2
Bug #1004212 [src:berkeley-abc] berkeley-abc: autopkgtest regression on arm64, 
i386 and ppc64el: Segmentation fault
Marked as fixed in versions berkeley-abc/1.01+20211229git48498af+dfsg-2.
Bug #1004212 [src:berkeley-abc] berkeley-abc: autopkgtest regression on arm64, 
i386 and ppc64el: Segmentation fault
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Re: [Pkg-shadow-devel] Bug#1004710: passwd: 4.11.1 breaks mmdebstrap testsuite by empty directories in /var/mail and /var/spool/mail

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1004710 [passwd] passwd: 4.11.1 breaks mmdebstrap testsuite by empty 
directories in /var/mail and /var/spool/mail
Severity set to 'serious' from 'normal'

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

Bug#1004662: prosody: postinst keeps messing with snakeoil certs

[Martin]

On 2022-01-31 12:21, Julien Cristau wrote:
> prosody's postinst seems to insist on creating
> /etc/prosody/certs/localhost.{crt,key}, but does this in a fragile way.

There have been a number of prosody package bugs related to snakeoil
certs. I wonder, if it is worth the trouble?

For most real world installations, people get LE certs or buy them or
they have their own CA.

Maybe prosody package should just drop the whole snakeoil stuff?

Bug#997558: marked as done (golang-github-mattermost-xml-roundtrip-validator: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/mattermost/xml-roundtrip-valida

[Debian Bug Tracking System]

Your message dated Tue, 01 Feb 2022 23:04:45 +
with message-id 
and subject line Bug#997558: fixed in 
golang-github-mattermost-xml-roundtrip-validator 0.1.0-3
has caused the Debian Bug report #997558,
regarding golang-github-mattermost-xml-roundtrip-validator: FTBFS: 
dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
github.com/mattermost/xml-roundtrip-validator 
github.com/mattermost/xml-roundtrip-validator/cmd 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.)


-- 
997558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-mattermost-xml-roundtrip-validator
Version: 0.1.0-2
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):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
> github.com/mattermost/xml-roundtrip-validator 
> github.com/mattermost/xml-roundtrip-validator/cmd
> internal/unsafeheader
> internal/goexperiment
> internal/cpu
> internal/abi
> runtime/internal/atomic
> runtime/internal/sys
> runtime/internal/math
> internal/race
> sync/atomic
> internal/bytealg
> unicode
> unicode/utf8
> encoding
> internal/itoa
> math/bits
> math
> runtime
> internal/reflectlite
> sync
> internal/testlog
> errors
> sort
> io
> internal/oserror
> strconv
> syscall
> path
> strings
> bytes
> reflect
> bufio
> time
> internal/syscall/execenv
> internal/syscall/unix
> io/fs
> internal/poll
> internal/fmtsort
> os
> fmt
> flag
> encoding/xml
> github.com/mattermost/xml-roundtrip-validator
> github.com/mattermost/xml-roundtrip-validator/cmd
>dh_auto_test -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
> github.com/mattermost/xml-roundtrip-validator 
> github.com/mattermost/xml-roundtrip-validator/cmd
> === RUN   TestValidateZippedReader
> reader_test.go:42: 
>   Error Trace:reader_test.go:42
>   Error:  An error is expected but got nil.
>   Test:   TestValidateZippedReader
>   Messages:   Should error on an invalid XML document
> --- FAIL: TestValidateZippedReader (0.00s)
> === RUN   TestValidXML
> --- PASS: TestValidXML (0.00s)
> === RUN   TestColonsInLocalNames
> validator_test.go:41: 
>   Error Trace:validator_test.go:41
>   Error:  An error is expected but got nil.
>   Test:   TestColonsInLocalNames
>   Messages:   Should error on input with colons in the root 
> element's name
> --- FAIL: TestColonsInLocalNames (0.00s)
> === RUN   TestEmptyNames
> validator_test.go:73: 
>   Error Trace:validator_test.go:73
>   Error:  An error is expected but got nil.
>   Test:   TestEmptyNames
>   Messages:   Should error on start element with no local name
> --- FAIL: TestEmptyNames (0.00s)
> === RUN   TestEmptyAttributes
> validator_test.go:83: 
>   Error Trace:validator_test.go:83
>   Error:  An error is expected but got nil.
>   Test:   TestEmptyAttributes
>   Messages:   Should error on input with empty attribute names
> --- FAIL: TestEmptyAttributes (0.00s)
> === RUN   TestDirectives
> validator_test.go:115: 
>   Error Trace:validator_test.go:115
>   Error:  An error is expected but got nil.
>   Test:   TestDirectives
>   Messages:   Should error on bad directive
> --- FAIL: TestDirectives (0.00s)
> === RUN   TestUnparseableXML
> validator_test.go:151: 
>   Error Trace:validator_test.go:151
>   Error:  "[XML syntax error on line 1: unescaped ]]> not 
> in CDATA section]" should have 2 item(s), but has 1
>   Test:   TestUnparseableXML
>   Messages:   Should return exactly two errors
> --- FAIL: TestUnparseableXML (0.00s)
> === RUN   TestValidateAll
> validator_test.go:162: 
>   Error Trace:validator_test.go:162
>   

Bug#1004761: marked as pending in gnome-control-center

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #1004761 in gnome-control-center reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/gnome-control-center/-/commit/38c7f687d697021f34b4d7213e5978503a06eb49


d/patches: Update to gnome-41 branch commit 41.2-19-g600b0a014

  - Fix build with recent meson versions (Closes: #1004761)
  - Do not invert order of video modes, which can result in a lower
than intended refresh rate being selected for a non-preferred mode
  - Adjust icon for default applications panel
  - Ensure sound recording level indicator is cleared when microphone
is unplugged
  - Translation updates


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1004761

Processed: Bug#1004761 marked as pending in gnome-control-center

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1004761 [src:gnome-control-center] gnome-control-center: FTBFS
Added tag(s) pending.

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

Bug#997558: marked as pending in golang-github-mattermost-xml-roundtrip-validator

[Thorsten Alteholz]

Control: tag -1 pending

Hello,

Bug #997558 in golang-github-mattermost-xml-roundtrip-validator reported by you 
has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/go-team/packages/golang-github-mattermost-xml-roundtrip-validator/-/commit/69ab54e8eaee03542f113f2fdb940b00768f394b


Import Debian changes 0.1.0-3

golang-github-mattermost-xml-roundtrip-validator (0.1.0-3) unstable; 
urgency=medium
.
  [Janitor]
  * Bump debhelper from old 12 to 13.
  * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
.
  [Thorsten Alteholz]
  * cherry pick patch from upstream (Closes: #997558)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997558

Processed: Bug#997558 marked as pending in golang-github-mattermost-xml-roundtrip-validator

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997558 [src:golang-github-mattermost-xml-roundtrip-validator] 
golang-github-mattermost-xml-roundtrip-validator: FTBFS: dh_auto_test: error: 
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
github.com/mattermost/xml-roundtrip-validator 
github.com/mattermost/xml-roundtrip-validator/cmd returned exit code 1
Added tag(s) pending.

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

Bug#1004818: os-autoinst: FTBFS: test failure

[Sebastian Ramacher]

Source: os-autoinst
Version: 4.6.1632799442.f77d4e1-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs

os-autoinst FTBFS in unstable:

Start 3: test-perl-testsuite

3: Test command: /<>/tools/invoke-tests "--prove-tool" 
"/usr/bin/prove" "--make-tool" "/usr/bin/ninja" "--build-directory" 
"/<>/build"
3: Test timeout computed to be: 1000
3: [12:23:12] ./00-compile-check-all.t . ok30351 ms ( 0.05 
usr  0.00 sys + 26.74 cusr  3.13 csys = 29.92 CPU)
3: [12:23:13] ./01-test_needle.t ... ok 1246 ms ( 0.02 
usr  0.00 sys +  1.28 cusr  0.11 csys =  1.41 CPU)
3: [12:23:14] ./02-test_ocr.t .. ok  707 ms ( 0.00 
usr  0.00 sys +  0.73 cusr  0.09 csys =  0.82 CPU)
3: [12:23:14] ./03-testapi.t ... ok  486 ms ( 0.01 
usr  0.00 sys +  0.46 cusr  0.02 csys =  0.49 CPU)
3: [12:23:15] ./04-check_vars_docu.t ... ok   77 ms ( 0.00 
usr  0.00 sys +  0.07 cusr  0.01 csys =  0.08 CPU)
3: [12:23:15] ./04-testapi-python.t  ok  362 ms ( 0.00 
usr  0.00 sys +  0.33 cusr  0.02 csys =  0.35 CPU)
3: [12:23:15] ./05-distribution.t .. ok  276 ms ( 0.00 
usr  0.00 sys +  0.26 cusr  0.02 csys =  0.28 CPU)
3: Useless use of a constant ("can load python test module at a"...) in void 
context at ./08-autotest.t line 342.
3: [2022-02-01T12:23:16.070 UTC] [debug] scheduling test tests/test.py
3: [12:23:16] ./08-autotest.t .. ok  377 ms ( 
0.01 usr  0.00 sys +  0.35 cusr  0.03 csys =  0.39 CPU)
3: [12:23:17] ./10-terminal.t .. ok 1418 ms ( 0.01 
usr  0.00 sys +  0.28 cusr  0.08 csys =  0.37 CPU)
3: [12:23:18] ./10-test-image-conversion-benchmark.t ... ok 1435 ms ( 0.01 
usr  0.00 sys +  1.37 cusr  0.06 csys =  1.44 CPU)
3: 
[12:23:19]
 ./10-virtio_terminal.t ... ok  379 ms ( 0.00 usr  0.00 sys 
+  0.32 cusr  0.06 csys =  0.38 CPU)
3: [12:23:19] ./11-image-ppm.t . ok  309 ms ( 0.00 
usr  0.00 sys +  0.29 cusr  0.03 csys =  0.32 CPU)
3: [12:23:19] ./12-bmwqemu.t ... ok  248 ms ( 0.00 
usr  0.00 sys +  0.23 cusr  0.01 csys =  0.24 CPU)
3: [12:23:20] ./15-logging.t ... ok  234 ms ( 0.00 
usr  0.00 sys +  0.22 cusr  0.02 csys =  0.24 CPU)
3: [12:23:20] ./16-send_with_fd.t .. ok  320 ms ( 0.00 
usr  0.00 sys +  0.27 cusr  0.05 csys =  0.32 CPU)
3: [12:23:20] ./17-basetest.t .. ok  298 ms ( 0.00 
usr  0.00 sys +  0.28 cusr  0.03 csys =  0.31 CPU)
3: [12:23:22] ./18-qemu.t .. ok 1382 ms ( 0.01 
usr  0.00 sys +  0.29 cusr  0.09 csys =  0.39 CPU)
3: [12:23:22] ./19-isotovideo-command-processing.t . ok  298 ms ( 0.00 
usr  0.00 sys +  0.27 cusr  0.03 csys =  0.30 CPU)
3: [12:23:22] ./20-openqa-benchmark-stopwatch-utils.t .. ok  117 ms ( 0.00 
usr  0.00 sys +  0.09 cusr  0.03 csys =  0.12 CPU)
3: 
3: #   Failed test 'no (unexpected) warnings (via done_testing)'
3: #   at ./21-needle-downloader.t line 126.
3: # Got the following unexpected warnings:
3: #   1: Mojo::Reactor::Poll: Timer failed: Label not found for "last 
T2_SUBTEST_WRAPPER" at /usr/share/perl/5.32/Test2/Hub/Subtest.pm line 67.
3: # Looks like you failed 1 test of 5.
3: [12:23:40] ./21-needle-downloader.t . 
3: Dubious, test returned 1 (wstat 256, 0x100)
3: Failed 1/5 subtests 
3: [12:23:40] ./22-svirt.t . ok  457 ms ( 0.01 
usr  0.01 sys +  0.41 cusr  0.06 csys =  0.49 CPU)
3: [12:23:41] ./23-baseclass.t . ok  292 ms ( 0.00 
usr  0.00 sys +  0.23 cusr  0.06 csys =  0.29 CPU)
3: [12:23:41] ./24-myjsonrpc-debug.t ... ok  231 ms ( 0.01 
usr  0.00 sys +  0.22 cusr  0.01 csys =  0.24 CPU)
3: [12:23:41] ./24-myjsonrpc.t . ok  233 ms ( 0.00 
usr  0.00 sys +  0.23 cusr  0.01 csys =  0.24 CPU)
3: [12:23:41] ./25-spvm.t .. ok  297 ms ( 0.00 
usr  0.00 sys +  0.27 cusr  0.02 csys =  0.29 CPU)
3: [12:23:41] ./26-serial_screen.t . ok  117 ms ( 0.00 
usr  0.00 sys +  0.09 cusr  0.03 csys =  0.12 CPU)
3: [12:23:42] ./26-ssh_screen.t  ok  131 ms ( 0.00 
usr  0.00 sys +  0.12 cusr  0.01 csys =  0.13 CPU)
3: [12:23:42] ./28-signalblocker.t . ok  447 ms ( 0.00 
usr  0.00 sys +  0.32 cusr  0.14 csys =  0.46 CPU)
3: [12:23:42] ./29-backend-generalhw.t . ok  369 ms ( 0.00 
usr  0.00 sys +  0.29 cusr  0.03 csys =  0.32 CPU)
3: [12:23:43] ./29-backend-ipmi.t .. ok  388 ms ( 0.01 
usr  0.00 sys +  0.35 cusr  0.04 csys =  0.40 CPU)
3: [12:23:43] ./29-backend-s390x.t . ok  288 ms 

Bug#1003847: binutils breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and others)

[Aurelien Jarno]

On 2022-02-01 16:02, Tulio Magno Quites Machado Filho wrote:
> Aurelien Jarno  writes:
> 
> > On 2022-01-19 22:08, John Paul Adrian Glaubitz wrote:
> >> Hi Aurelien!
> >> 
> >> Unfortunately, glibc no longer builds with this change on powerpc and ppc64
> >> and kernel builds still fails on both targets:
> >> 
> >> > https://buildd.debian.org/status/fetch.php?pkg=glibc=powerpc=2.33-3=1642542048=0
> >> > https://buildd.debian.org/status/fetch.php?pkg=glibc=ppc64=2.33-3=1642542055=0
> >
> > The ppc64el fix is not the cause for those failures. Previous glibc
> > versions also do not build on powerpc and ppc64 following the binutils
> > snapshot upload to sid. It's just that more code got broken on powerpc
> > and ppc64 than on ppc64el. I have queued the backported fixes from
> > upstream for the next upload.
> 
> Are these issues happening when building glibc upstream too?

No, upstream built fine, and same now for the 2.33 and 2.34 branches
after I backported ee874f44fd55988808a4a162ef21bfa2cc8dc6f7.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#1004216: marked as done (missing directory: /usr/share/fonts/truetype/)

[Debian Bug Tracking System]

Your message dated Tue, 01 Feb 2022 22:04:38 +
with message-id 
and subject line Bug#1004216: fixed in fonts-ipaexfont 00401-4.1
has caused the Debian Bug report #1004216,
regarding missing directory: /usr/share/fonts/truetype/
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.)


-- 
1004216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fonts-ipaexfont
Version: 00401-3
Severity: serious
Control: close -1 00401-4
Tags: sid bookworm
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:fonts-ipaexfont has been trying to migrate
for 61 days [2] due to a piuparts regression which to my eye looks
genuine. Hence, I am filing this bug.

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

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

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

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

Paul

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




OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: fonts-ipaexfont
Source-Version: 00401-4.1
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated fonts-ipaexfont package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 22 Jan 2022 22:25:47 +0100
Source: fonts-ipaexfont
Architecture: source
Version: 00401-4.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Fonts Task Force 
Changed-By: Paul Gevers 
Closes: 1004216
Changes:
 fonts-ipaexfont (00401-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Ensure that /usr/share/fonts/truetype/ exists when update-alternatives
 runs (Closes: #1004216)
Checksums-Sha1:
 d4ac15515e0688ad08b66896f504d878c502f1c8 1912 fonts-ipaexfont_00401-4.1.dsc
 f976905a73e0ba4ab7343568843aa226076afd88 11612 
fonts-ipaexfont_00401-4.1.debian.tar.xz
Checksums-Sha256:
 8ed6a2f4a159ee9d4ab5f8b6bfc9f3ff4566a1aaa5d39967c3afa583130dbd0a 1912 
fonts-ipaexfont_00401-4.1.dsc
 c28e0d7cf4f626fdce75fc8f4b5d7cb3f739ea4b2e905dfe0814431ed70f4aa9 11612 
fonts-ipaexfont_00401-4.1.debian.tar.xz
Files:
 05a602bcda95fd23fc8b3236bce78c82 1912 fonts optional 
fonts-ipaexfont_00401-4.1.dsc
 96a137e4f26a0f0ea54ec19297831244 11612 fonts optional 
fonts-ipaexfont_00401-4.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmHsd0sACgkQnFyZ6wW9
dQpevwf/SP85iQRyZdQH2xZ5imsoKhkFlBzU/SsCf4Lu8GdxkDVRbnOJI1W9m53R
KOQfUEUGHHLkzsvhV4P7FeJz8pmFcJTPQAb1Kdloi2jxA2eZM8Zr1bPEh53Ebui1
BFmx+Epous3HNREfDOCprxhvoY5nIcYl6DdRX4dgyL02oORVdStJJuNHwRTYiTbg
dzcO3AvOHU1RU9luPQU8olj8bnbwW/6gtRwI/ZigoGX/IvljulPRfa7LA/W9wA2f
fdI0L+b6f5m/DhyrpuvsxOwf3Jue+oFDDkM2UiwNkfbg1umvQHzOaC7x+r39h4K+
X3pd5ruDT0yjinSzRz591HmCLePDpg==
=cm/b
-END PGP SIGNATURE End Message ---

Bug#1004781: marked as done (ros-perception-pcl: FTBFS in unstable)

[Debian Bug Tracking System]

Your message dated Tue, 01 Feb 2022 21:50:54 +
with message-id 
and subject line Bug#1004781: fixed in ros-perception-pcl 1.7.3-3
has caused the Debian Bug report #1004781,
regarding ros-perception-pcl: FTBFS in unstable
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.)


-- 
1004781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-perception-pcl
Version: 1.7.3-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs

ros-perception-pcl FTBFS in unstable:

cd /<>/obj-x86_64-linux-gnu/pcl_ros && /usr/lib/ccache/c++ 
-DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK -DBOOST_DATE_TIME_DYN_LINK 
-DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK 
-DBOOST_SERIALIZATION_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DBOOST_THREAD_DYN_LINK 
-DDISABLE_PCAP -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB 
-DQT_WIDGETS_LIB -DROSCONSOLE_BACKEND_LOG4CXX -DROS_BUILD_SHARED_LIBS=1 
-DROS_PACKAGE_NAME=\"pcl_ros\" -Dkiss_fft_scalar=double 
-Dpcl_ros_surface_EXPORTS -I/<>/pcl_ros/include -isystem 
/<>/obj-x86_64-linux-gnu/devel/include -isystem 
/<>/pcl_conversions/include -isystem /usr/include/xmlrpcpp 
-isystem /usr/include/eigen3 -isystem /usr/include/pcl-1.12 -isystem 
/usr/include/ni -isystem /usr/include/openni2 -isystem /usr/include/vtk-9.1 
-isystem /usr/include/jsoncpp -isystem /usr/include/freetype2 -isystem 
/usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtOpenGL -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -std=c++14 -fPIC 
-MD -MT 
pcl_ros/CMakeFiles/pcl_ros_surface.dir/src/pcl_ros/surface/convex_hull.cpp.o 
-MF CMakeFiles/pcl_ros_surface.dir/src/pcl_ros/surface/convex_hull.cpp.o.d -o 
CMakeFiles/pcl_ros_surface.dir/src/pcl_ros/surface/convex_hull.cpp.o -c 
/<>/pcl_ros/src/pcl_ros/surface/convex_hull.cpp
In file included from /usr/include/log4cxx/log4cxx.h:45,
 from /usr/include/log4cxx/logstring.h:28,
 from /usr/include/log4cxx/level.h:22,
 from /usr/include/ros/console.h:46,
 from /usr/include/ros/ros.h:40,
 from 
/<>/pcl_ros/tools/convert_pcd_to_image.cpp:49:
/usr/include/log4cxx/boost-std-configuration.h:10:18: error: ‘shared_mutex’ in 
namespace ‘std’ does not name a type
   10 | typedef std::shared_mutex shared_mutex;
  |  ^~~~
/usr/include/log4cxx/boost-std-configuration.h:10:13: note: ‘std::shared_mutex’ 
is only available from C++17 onwards
   10 | typedef std::shared_mutex shared_mutex;
  | ^~~
make[3]: *** [pcl_ros/CMakeFiles/convert_pcd_to_image.dir/build.make:79: 
pcl_ros/CMakeFiles/convert_pcd_to_image.dir/tools/convert_pcd_to_image.cpp.o] 
Error 1
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'


Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ros-perception-pcl
Source-Version: 1.7.3-3
Done: Jochen Sprickerhof 

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated 
ros-perception-pcl 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, 01 Feb 2022 22:35:57 +0100
Source: ros-perception-pcl
Architecture: source
Version: 1.7.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Closes: 1004781
Changes:
 ros-perception-pcl (1.7.3-3) unstable; urgency=medium
 .
   * Add patch for new log4cxx (Closes: #1004781)
Checksums-Sha1:
 6a949d481c3a20f1ee9324753967a8b2000447e3 3213 ros-perception-pcl_1.7.3-3.dsc
 

Bug#1004798: libpdb-redo FTBFS with libcifpp 2.0.4

[Adrian Bunk]

Source: libpdb-redo
Version: 1.0.2-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=libpdb-redo=1.0.2-3%2Bb2

...
src/BondMap.cpp: In function ‘void mmcif::createBondInfoFile(const 
std::filesystem::__cxx11::path&, const std::filesystem::__cxx11::path&)’:
src/BondMap.cpp:246:103: error: no matching function for call to 
‘cif::Category::rows()’
  246 | for (const auto& [atom_id_1, atom_id_2]: 
chem_comp_bond->rows({"atom_id_1", "atom_id_2"}))
  |  
~^~~~
In file included from src/BondMap.cpp:37:
/usr/include/cif++/Cif++.hpp:1850:42: note: candidate: 
‘cif::iterator_proxy cif::Category::rows(Ns ...) const 
[with Ts = {std::__cxx11::basic_string, 
std::allocator >, std::__cxx11::basic_string, std::allocator >}; Ns = {}]’
 1850 | iterator_proxy rows(Ns... names) const
  |  ^~~~
/usr/include/cif++/Cif++.hpp:1850:42: note:   candidate expects 0 arguments, 1 
provided
/usr/include/cif++/Cif++.hpp:1857:41: note: candidate: 
‘cif::iterator_proxy cif::Category::rows(Ns ...) [with 
Ts = {std::__cxx11::basic_string, 
std::allocator >, std::__cxx11::basic_string, std::allocator >}; Ns = {}]’
 1857 | iterator_proxy rows(Ns... names)
  | ^~~~
...

Bug#1004790: avifile: should this package be removed?

[Sebastian Ramacher]

Source: avifile
Version: 1:0.7.48~20090503.ds-21
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm

Upstream development of avifile has ceased over a decode ago. Given that
avifile fails to build with ffmpeg 5.0 (see ##1004789) as it did with
all the previous major releases of ffmpeg, I wonder if is still
sustainable to keep this package in Debian. Should this package be
removed from unstable?

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1004765: marked as done (ros-image-pipeline: FTBFS)

[Debian Bug Tracking System]

Your message dated Tue, 01 Feb 2022 21:19:42 +
with message-id 
and subject line Bug#1004765: fixed in ros-image-pipeline 1.16.0-2
has caused the Debian Bug report #1004765,
regarding ros-image-pipeline: FTBFS
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.)


-- 
1004765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-image-pipeline
Version: 1.16.0-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs

ros-image-pipeline fails to build:
| cd /<>/obj-x86_64-linux-gnu/image_view && /usr/lib/ccache/c++ 
-DROSCONSOLE_BACKEND_LOG4CXX -DROS_BUILD_SHARED_LIBS=1 
-DROS_PACKAGE_NAME=\"image_view\" -I/usr/include/xmlrpcpp -isystem 
/<>/obj-x86_64-linux-gnu/devel/include -isystem 
/usr/include/opencv4 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -MD -MT 
image_view/CMakeFiles/extract_images.dir/src/nodes/extract_images.cpp.o -MF 
CMakeFiles/extract_images.dir/src/nodes/extract_images.cpp.o.d -o 
CMakeFiles/extract_images.dir/src/nodes/extract_images.cpp.o -c 
/<>/image_view/src/nodes/extract_images.cpp
| In file included from /usr/include/log4cxx/log4cxx.h:45,
|  from /usr/include/log4cxx/logstring.h:28,
|  from /usr/include/log4cxx/level.h:22,
|  from /usr/include/ros/console.h:46,
|  from /usr/include/ros/ros.h:40,
|  from 
/<>/depth_image_proc/src/nodelets/disparity.cpp:39:
| /usr/include/log4cxx/boost-std-configuration.h:10:18: error: ‘shared_mutex’ 
in namespace ‘std’ does not name a type
|10 | typedef std::shared_mutex shared_mutex;
|   |  ^~~~
| /usr/include/log4cxx/boost-std-configuration.h:10:13: note: 
‘std::shared_mutex’ is only available from C++17 onwards
|10 | typedef std::shared_mutex shared_mutex;
|   | ^~~
| /usr/include/log4cxx/boost-std-configuration.h:12:30: error: ‘shared_lock’ in 
namespace ‘std’ does not name a template type
|12 | using shared_lock = std::shared_lock;
|   |  ^~~
| /usr/include/log4cxx/boost-std-configuration.h:12:25: note: 
‘std::shared_lock’ is only available from C++14 onwards
|12 | using shared_lock = std::shared_lock;
|   | ^~~
| make[3]: *** 
[depth_image_proc/CMakeFiles/depth_image_proc.dir/build.make:107: 
depth_image_proc/CMakeFiles/depth_image_proc.dir/src/nodelets/disparity.cpp.o] 
Error 1
| make[3]: *** Waiting for unfinished jobs

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ros-image-pipeline
Source-Version: 1.16.0-2
Done: Jochen Sprickerhof 

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated 
ros-image-pipeline 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, 01 Feb 2022 22:00:24 +0100
Source: ros-image-pipeline
Architecture: source
Version: 1.16.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Closes: 1004765
Changes:
 ros-image-pipeline (1.16.0-2) unstable; urgency=medium
 .
   * Fix compilation with new log4cxx (Closes: #1004765)
Checksums-Sha1:
 bb3e1c4d19078075289abfb6ee007afdb85abaa5 4574 ros-image-pipeline_1.16.0-2.dsc
 d2a8e004c31985c5383e4b8104ff47d9b4d143c0 10412 
ros-image-pipeline_1.16.0-2.debian.tar.xz
 85253a79973c7d31e2d5b11431aaa07890b19c5d 22931 
ros-image-pipeline_1.16.0-2_source.buildinfo
Checksums-Sha256:
 dc8188f62838df34694b40fa26e4a14816fb0aea448a9f7c839f0e27e9aebcf2 4574 
ros-image-pipeline_1.16.0-2.dsc
 13d49432984b3578a7db42798563e224612aaa2f34442f4fa94da854015295cb 10412 
ros-image-pipeline_1.16.0-2.debian.tar.xz
 30d24a3f7e3746a4b0e812e22c37fbccd55f00e6c6b3df7819d44c8e53b97cec 22931 

Processed: found 1004752 in 2:3.2.11-2, found 1004752 in 2:3.2.10-2, found 1004752 in 2:2.2.25-1~deb11u1 ...

[Debian Bug Tracking System]

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

> found 1004752 2:3.2.11-2
Bug #1004752 {Done: Chris Lamb } [python-django] 
python-django: CVE-2022-22818 CVE-2022-23833
There is no source info for the package 'python-django' at version '2:3.2.11-2' 
with architecture ''
Unable to make a source version for version '2:3.2.11-2'
Marked as found in versions 2:3.2.11-2.
> found 1004752 2:3.2.10-2
Bug #1004752 {Done: Chris Lamb } [python-django] 
python-django: CVE-2022-22818 CVE-2022-23833
There is no source info for the package 'python-django' at version '2:3.2.10-2' 
with architecture ''
Unable to make a source version for version '2:3.2.10-2'
Marked as found in versions 2:3.2.10-2.
> found 1004752 2:2.2.25-1~deb11u1
Bug #1004752 {Done: Chris Lamb } [python-django] 
python-django: CVE-2022-22818 CVE-2022-23833
There is no source info for the package 'python-django' at version 
'2:2.2.25-1~deb11u1' with architecture ''
Unable to make a source version for version '2:2.2.25-1~deb11u1'
Marked as found in versions 2:2.2.25-1~deb11u1.
> found 1004752 1:1.11.29-1~deb10u1
Bug #1004752 {Done: Chris Lamb } [python-django] 
python-django: CVE-2022-22818 CVE-2022-23833
Marked as found in versions python-django/1:1.11.29-1~deb10u1.
> thanks
Stopping processing here.

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

Bug#996414: python-fastimport: autopkgtest regression: 2 failures + lots of RuntimeError: maximum recursion depth exceeded

[Paul Gevers]

Hi,

On 31-01-2022 21:19, Paul Gevers wrote:
If nobody beats me to it, I'll upload an NMU dropping the pypy based 
autopkgtest in a couple of days.


I have created a MR [1] and have uploaded to DELAYED/5.

Paul

[1] 
https://salsa.debian.org/python-team/packages/python-fastimport/-/merge_requests/2


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1004781: ros-perception-pcl: FTBFS in unstable

[Sebastian Ramacher]

Source: ros-perception-pcl
Version: 1.7.3-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs

ros-perception-pcl FTBFS in unstable:

cd /<>/obj-x86_64-linux-gnu/pcl_ros && /usr/lib/ccache/c++ 
-DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK -DBOOST_DATE_TIME_DYN_LINK 
-DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK 
-DBOOST_SERIALIZATION_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DBOOST_THREAD_DYN_LINK 
-DDISABLE_PCAP -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB 
-DQT_WIDGETS_LIB -DROSCONSOLE_BACKEND_LOG4CXX -DROS_BUILD_SHARED_LIBS=1 
-DROS_PACKAGE_NAME=\"pcl_ros\" -Dkiss_fft_scalar=double 
-Dpcl_ros_surface_EXPORTS -I/<>/pcl_ros/include -isystem 
/<>/obj-x86_64-linux-gnu/devel/include -isystem 
/<>/pcl_conversions/include -isystem /usr/include/xmlrpcpp 
-isystem /usr/include/eigen3 -isystem /usr/include/pcl-1.12 -isystem 
/usr/include/ni -isystem /usr/include/openni2 -isystem /usr/include/vtk-9.1 
-isystem /usr/include/jsoncpp -isystem /usr/include/freetype2 -isystem 
/usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtOpenGL -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -std=c++14 -fPIC 
-MD -MT 
pcl_ros/CMakeFiles/pcl_ros_surface.dir/src/pcl_ros/surface/convex_hull.cpp.o 
-MF CMakeFiles/pcl_ros_surface.dir/src/pcl_ros/surface/convex_hull.cpp.o.d -o 
CMakeFiles/pcl_ros_surface.dir/src/pcl_ros/surface/convex_hull.cpp.o -c 
/<>/pcl_ros/src/pcl_ros/surface/convex_hull.cpp
In file included from /usr/include/log4cxx/log4cxx.h:45,
 from /usr/include/log4cxx/logstring.h:28,
 from /usr/include/log4cxx/level.h:22,
 from /usr/include/ros/console.h:46,
 from /usr/include/ros/ros.h:40,
 from 
/<>/pcl_ros/tools/convert_pcd_to_image.cpp:49:
/usr/include/log4cxx/boost-std-configuration.h:10:18: error: ‘shared_mutex’ in 
namespace ‘std’ does not name a type
   10 | typedef std::shared_mutex shared_mutex;
  |  ^~~~
/usr/include/log4cxx/boost-std-configuration.h:10:13: note: ‘std::shared_mutex’ 
is only available from C++17 onwards
   10 | typedef std::shared_mutex shared_mutex;
  | ^~~
make[3]: *** [pcl_ros/CMakeFiles/convert_pcd_to_image.dir/build.make:79: 
pcl_ros/CMakeFiles/convert_pcd_to_image.dir/tools/convert_pcd_to_image.cpp.o] 
Error 1
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'


Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1004780: gnome-initial-setup: FTBFS in unstable

[Sebastian Ramacher]

Source: gnome-initial-setup
Version: 41.2-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs

gnome-initial-setup FTBFS in unstable:

Configuring config.h using configuration
Configuring gnome-initial-setup-copy-worker.desktop.in using configuration

../data/meson.build:33:9: ERROR: Function does not take positional arguments.

A full log can be found at 
/<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt


Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1004765: ros-image-pipeline: FTBFS

[Sebastian Ramacher]

Source: ros-image-pipeline
Version: 1.16.0-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs

ros-image-pipeline fails to build:
| cd /<>/obj-x86_64-linux-gnu/image_view && /usr/lib/ccache/c++ 
-DROSCONSOLE_BACKEND_LOG4CXX -DROS_BUILD_SHARED_LIBS=1 
-DROS_PACKAGE_NAME=\"image_view\" -I/usr/include/xmlrpcpp -isystem 
/<>/obj-x86_64-linux-gnu/devel/include -isystem 
/usr/include/opencv4 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -MD -MT 
image_view/CMakeFiles/extract_images.dir/src/nodes/extract_images.cpp.o -MF 
CMakeFiles/extract_images.dir/src/nodes/extract_images.cpp.o.d -o 
CMakeFiles/extract_images.dir/src/nodes/extract_images.cpp.o -c 
/<>/image_view/src/nodes/extract_images.cpp
| In file included from /usr/include/log4cxx/log4cxx.h:45,
|  from /usr/include/log4cxx/logstring.h:28,
|  from /usr/include/log4cxx/level.h:22,
|  from /usr/include/ros/console.h:46,
|  from /usr/include/ros/ros.h:40,
|  from 
/<>/depth_image_proc/src/nodelets/disparity.cpp:39:
| /usr/include/log4cxx/boost-std-configuration.h:10:18: error: ‘shared_mutex’ 
in namespace ‘std’ does not name a type
|10 | typedef std::shared_mutex shared_mutex;
|   |  ^~~~
| /usr/include/log4cxx/boost-std-configuration.h:10:13: note: 
‘std::shared_mutex’ is only available from C++17 onwards
|10 | typedef std::shared_mutex shared_mutex;
|   | ^~~
| /usr/include/log4cxx/boost-std-configuration.h:12:30: error: ‘shared_lock’ in 
namespace ‘std’ does not name a template type
|12 | using shared_lock = std::shared_lock;
|   |  ^~~
| /usr/include/log4cxx/boost-std-configuration.h:12:25: note: 
‘std::shared_lock’ is only available from C++14 onwards
|12 | using shared_lock = std::shared_lock;
|   | ^~~
| make[3]: *** 
[depth_image_proc/CMakeFiles/depth_image_proc.dir/build.make:107: 
depth_image_proc/CMakeFiles/depth_image_proc.dir/src/nodelets/disparity.cpp.o] 
Error 1
| make[3]: *** Waiting for unfinished jobs

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1004562: libguestfs: autopkgtest regression

[Paul Gevers]

Hi,

On Sun, 30 Jan 2022 17:07:53 +0200 Adrian Bunk  wrote:

https://ci.debian.net/data/autopkgtest/testing/amd64/libg/libguestfs/18786402/log.gz

...
+ ssh -oUserKnownHostsFile=/dev/null -oStrictHostKeyChecking=no -i id_rsa -T -p 
10022 -o ConnectTimeout=5 root@localhost echo success
Connection timed out during banner exchange
Connection to 127.0.0.1 port 10022 timed out
+ rv=1
+ [ 1 -eq 0 ]
+ sleepenh 1643405863.414064 5
+ [ 1 -eq 1 ]
+ TIMESTAMP=1643405868.414064
+ i=39
+ [ 39 -ge 40 ]
+ true
+ rv=0
+ ssh -oUserKnownHostsFile=/dev/null -oStrictHostKeyChecking=no -i id_rsa -T -p 
10022 -o ConnectTimeout=5 root@localhost echo success
Connection timed out during banner exchange
Connection to 127.0.0.1 port 10022 timed out
+ rv=1
+ [ 1 -eq 0 ]
+ sleepenh 1643405868.414064 5
+ [ 1 -eq 1 ]
+ TIMESTAMP=1643405873.414064
+ i=40
+ [ 40 -ge 40 ]
+ break
+ [ 40 -eq 40 ]
+ echo timeout reached: unable to connect to qemu via ssh
+ exit 1
+ cat --show-nonprinting qemu.log
+ kill 26114
autopkgtest [21:37:54]:  summary
extlinux FAIL non-zero exit status 1


On top of this, your test depends on linux-image-amd64 which is only 
available on amd64. Hence, the test fails on all other architectures.


So, apart from an "Architecture" field in d/t/control, I'm pretty sure 
you also need a "isolation-machine" restriction, because depending on a 
linux image package is futile in other environments. You're starting 
qemu inside your test. That doesn't go well in lxc.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1004761: gnome-control-center: FTBFS

[Sebastian Ramacher]

Source: gnome-control-center
Version: 1:41.2-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs

gnome-control-center FTBFS in unstable:
| Configuring gnome-applications-panel.desktop.in using configuration
|
| ../panels/applications/meson.build:10:5: ERROR: Function does not take 
positional arguments.
|
| A full log can be found at 
/<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: tagging 1004654, tagging 1004299, tagging 1004517, tagging 1004532, tagging 1004531, tagging 1004463 ...

[Debian Bug Tracking System]

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

> tags 1004654 + sid bookworm
Bug #1004654 [ruby-rack-mount] ruby-rack-mount: FTBFS with ruby-rack 2.2.3 
"http://josh.backpackit.com/host;>(UTF-8) expected but was 
<"http://example.org/host;>(ASCII-8BIT)
Added tag(s) sid and bookworm.
> tags 1004299 + sid bookworm
Bug #1004299 [ruby-net-ssh] ruby-net-ssh: FTBFS in sid
Added tag(s) sid and bookworm.
> tags 1004517 + sid bookworm
Bug #1004517 [src:pyvo] [pyvo] CI failure with astropy 5.0.1; please update to 
version 1.2.1
Added tag(s) bookworm and sid.
> tags 1004532 + sid bookworm
Bug #1004532 [php-markdown] php-markdown: PHP message: PHP Fatal error:  Array 
and string offset access syntax with curly braces
Added tag(s) sid and bookworm.
> tags 1004531 + sid bookworm
Bug #1004531 [php-net-ipv6] php-net-ipv6: PHP Fatal error:  Array and string 
offset access syntax with curly braces is no longer supported
Added tag(s) sid and bookworm.
> tags 1004463 + sid bookworm
Bug #1004463 [python3-jsondiff,cbmc] python3-jsondiff,cbmc: File conflict for 
/usr/bin/jdiff
Added tag(s) sid and bookworm.
> notfixed 985864 15.0.0-2
Bug #985864 {Done: Thomas Goirand } [trove-common] 
trove-common: fails to install: install: cannot stat 
'/usr/share/trove-common/trove-guestagent.conf': No such file or directory
There is no source info for the package 'trove-common' at version '15.0.0-2' 
with architecture ''
Unable to make a source version for version '15.0.0-2'
No longer marked as fixed in versions 15.0.0-2.
> fixed 985864 1:15.0.0-2
Bug #985864 {Done: Thomas Goirand } [trove-common] 
trove-common: fails to install: install: cannot stat 
'/usr/share/trove-common/trove-guestagent.conf': No such file or directory
Marked as fixed in versions openstack-trove/1:15.0.0-2.
> fixed 1003790 6.12.1+dfsg4-9
Bug #1003790 {Done: Jose Luis Rivero } [dart] dart: 
FTBFS on i386: test_SkelParser hangs
There is no source info for the package 'dart' at version '6.12.1+dfsg4-9' with 
architecture ''
Unable to make a source version for version '6.12.1+dfsg4-9'
Marked as fixed in versions 6.12.1+dfsg4-9.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1003790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003790
1004299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004299
1004463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004463
1004517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004517
1004531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004531
1004532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004532
1004654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004654
985864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985864
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1003847: binutils breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and others)

[Tulio Magno Quites Machado Filho]

Aurelien Jarno  writes:

> On 2022-01-19 22:08, John Paul Adrian Glaubitz wrote:
>> Hi Aurelien!
>> 
>> Unfortunately, glibc no longer builds with this change on powerpc and ppc64
>> and kernel builds still fails on both targets:
>> 
>> > https://buildd.debian.org/status/fetch.php?pkg=glibc=powerpc=2.33-3=1642542048=0
>> > https://buildd.debian.org/status/fetch.php?pkg=glibc=ppc64=2.33-3=1642542055=0
>
> The ppc64el fix is not the cause for those failures. Previous glibc
> versions also do not build on powerpc and ppc64 following the binutils
> snapshot upload to sid. It's just that more code got broken on powerpc
> and ppc64 than on ppc64el. I have queued the backported fixes from
> upstream for the next upload.

Are these issues happening when building glibc upstream too?

-- 
Tulio Magno

Bug#1004729: bind9-dyndb-ldap: fails to load dyndb-ldap backend

[Timo Aaltonen]

l3mm.0x kirjoitti 1.2.2022 klo 12.35:
> Package: bind9-dyndb-ldap
> Version: 11.6-3
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> after an upgrade from buster to bullseye my previously working 
> bind9-dyndb-ldap
> installation dosn't work anymore.
> 
> It seems that there is something wrong with the dependencies to the package
> bind9-libs.
> 
> named log:
> ...
> Feb 01 07:53:19 testing named[4485]: loading DynDB instance 'ldap-db' driver
> '/usr/lib/bind/ldap.so'
> Feb 01 07:53:19 testing named[4485]: failed to dynamically load instance 
> 'ldap-
> db' driver '/usr/lib/bind/ldap.so': libdns-9.16.15-Debian.so: cannot open
> shared object file: No such file or directory (failure)
> Feb 01 07:53:19 testing named[4485]: dynamic database 'ldap-db' configuration
> failed: failure
> Feb 01 07:53:19 testing named[4485]: loading configuration: failure
> Feb 01 07:53:19 testing named[4485]: exiting (due to fatal error)
> 
> 
> The package bind9-libs lists a newer version about the shared object file.
> 
> /usr/lib/x86_64-linux-gnu
> /usr/lib/x86_64-linux-gnu/libbind9-9.16.22-Debian.so
> /usr/lib/x86_64-linux-gnu/libdns-9.16.22-Debian.so
> /usr/lib/x86_64-linux-gnu/libirs-9.16.22-Debian.so
> /usr/lib/x86_64-linux-gnu/libisc-9.16.22-Debian.so
> /usr/lib/x86_64-linux-gnu/libisccc-9.16.22-Debian.so
> /usr/lib/x86_64-linux-gnu/libisccfg-9.16.22-Debian.so
> /usr/lib/x86_64-linux-gnu/libns-9.16.22-Debian.so

Oh nice, a rather big version bump disguised as a CVE update.. You'd
need the version from unstable to have some hope of it working with
bind9 9.16.17+.

Bug#984171: marked as done (haskell-gtk: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Tue, 01 Feb 2022 18:48:46 +
with message-id 
and subject line Bug#984167: fixed in c2hs 0.28.8-1
has caused the Debian Bug report #984167,
regarding haskell-gtk: ftbfs with GCC-11
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.)


-- 
984167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:haskell-gtk
Version: 0.15.5-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/haskell-gtk_0.15.5-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
Ready component graph:
definite gtk-0.15.5-EP55RaZuhluFS9C9sjlGcY
depends array-0.5.4.0
depends base-4.13.0.0
depends bytestring-0.10.10.1
depends cairo-0.13.8.1-9ROOXD4as1uLn8sCpDXiTi
depends containers-0.6.2.1
depends gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W
depends glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx
depends mtl-2.2.2
depends pango-0.13.8.1-J6ZPsrZFOIY2Xy7NzhFm7o
depends text-1.2.4.0
Using Cabal-3.0.1.0 compiled by ghc-8.8
Using compiler: ghc-8.8.4
Using install prefix: /usr
Executables installed in: /usr/bin
Libraries installed in:
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4/gtk-0.15.5-EP55RaZuhluFS9C9sjlGcY
Dynamic Libraries installed in:
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4
Private executables installed in: /usr/lib/x86_64-linux-ghc-8.8.4/gtk-0.15.5
Data files installed in: /usr/share/gtk
Documentation installed in: /usr/share/doc/x86_64-linux-ghc-8.8.4/gtk-0.15.5
Configuration files installed in: /usr/etc
No alex found
Using ar found on system at: /usr/bin/x86_64-linux-gnu-ar
No c2hs found
No cpphs found
No doctest found
Using gcc version 11 found on system at: /usr/bin/x86_64-linux-gnu-gcc
Using ghc version 8.8.4 found on system at: /usr/bin/ghc
Using ghc-pkg version 8.8.4 found on system at: /usr/bin/ghc-pkg
No ghcjs found
No ghcjs-pkg found
No greencard found
Using gtk2hsC2hs version 0.13.13 found on system at: /usr/bin/gtk2hsC2hs
Using gtk2hsHookGenerator found on system at: /usr/bin/gtk2hsHookGenerator
Using gtk2hsTypeGen found on system at: /usr/bin/gtk2hsTypeGen
Using haddock version 2.23.0 found on system at: /usr/bin/haddock
No happy found
Using haskell-suite found on system at: haskell-suite-dummy-location
Using haskell-suite-pkg found on system at: haskell-suite-pkg-dummy-location
No hmake found
Using hpc version 0.67 found on system at: /usr/bin/hpc
Using hsc2hs version 0.68.7 found on system at: /usr/bin/hsc2hs
Using hscolour version 1.24 found on system at: /usr/bin/HsColour
No jhc found
Using ld found on system at: /usr/bin/x86_64-linux-gnu-ld.gold
Using pkg-config version 0.29.2 found on system at: /usr/bin/pkg-config
Using runghc version 8.8.4 found on system at: /usr/bin/runghc
Using strip version 2.35 found on system at: /usr/bin/strip
Using tar found on system at: /bin/tar
No uhc found
/usr/bin/pkg-config --modversion gthread-2.0
/usr/bin/pkg-config --modversion 'gtk+-2.0'
Ensuring that class hierarchy in Graphics/UI/Gtk/Types.chs is up-to-date.
Ensuring that callback hooks in Graphics/UI/Gtk/Signals.chs 

Bug#984176: marked as done (haskell-pango: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Tue, 01 Feb 2022 18:48:46 +
with message-id 
and subject line Bug#984167: fixed in c2hs 0.28.8-1
has caused the Debian Bug report #984167,
regarding haskell-pango: ftbfs with GCC-11
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.)


-- 
984167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:haskell-pango
Version: 0.13.8.1-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/haskell-pango_0.13.8.1-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
depends glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx
depends mtl-2.2.2
depends pretty-1.1.3.6
depends process-1.6.9.0
depends text-1.2.4.0
Using Cabal-3.0.1.0 compiled by ghc-8.8
Using compiler: ghc-8.8.4
Using install prefix: /usr
Executables installed in: /usr/bin
Libraries installed in:
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4/pango-0.13.8.1-J6ZPsrZFOIY2Xy7NzhFm7o
Dynamic Libraries installed in:
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4
Private executables installed in:
/usr/lib/x86_64-linux-ghc-8.8.4/pango-0.13.8.1
Data files installed in: /usr/share/pango
Documentation installed in:
/usr/share/doc/x86_64-linux-ghc-8.8.4/pango-0.13.8.1
Configuration files installed in: /usr/etc
No alex found
Using ar found on system at: /usr/bin/x86_64-linux-gnu-ar
No c2hs found
No cpphs found
No doctest found
Using gcc version 11 found on system at: /usr/bin/x86_64-linux-gnu-gcc
Using ghc version 8.8.4 found on system at: /usr/bin/ghc
Using ghc-pkg version 8.8.4 found on system at: /usr/bin/ghc-pkg
No ghcjs found
No ghcjs-pkg found
No greencard found
Using gtk2hsC2hs version 0.13.13 found on system at: /usr/bin/gtk2hsC2hs
Using gtk2hsHookGenerator found on system at: /usr/bin/gtk2hsHookGenerator
Using gtk2hsTypeGen found on system at: /usr/bin/gtk2hsTypeGen
Using haddock version 2.23.0 found on system at: /usr/bin/haddock
No happy found
Using haskell-suite found on system at: haskell-suite-dummy-location
Using haskell-suite-pkg found on system at: haskell-suite-pkg-dummy-location
No hmake found
Using hpc version 0.67 found on system at: /usr/bin/hpc
Using hsc2hs version 0.68.7 found on system at: /usr/bin/hsc2hs
Using hscolour version 1.24 found on system at: /usr/bin/HsColour
No jhc found
Using ld found on system at: /usr/bin/x86_64-linux-gnu-ld.gold
Using pkg-config version 0.29.2 found on system at: /usr/bin/pkg-config
Using runghc version 8.8.4 found on system at: /usr/bin/runghc
Using strip version 2.35 found on system at: /usr/bin/strip
Using tar found on system at: /bin/tar
No uhc found
/usr/bin/pkg-config --modversion cairo
/usr/bin/pkg-config --modversion pangocairo
/usr/bin/pkg-config --modversion pango
creating dist-ghc/build/global-autogen
/usr/bin/pkg-config --modversion cairo
/usr/bin/pkg-config --modversion pangocairo
/usr/bin/pkg-config --modversion pango
Ensuring that class hierarchy in Graphics/Rendering/Pango/Types.chs is
up-to-date.
touch configure-ghc-stamp
. /usr/share/haskell-devscripts/Dh_Haskell.sh && \
build_recipe
Running debian/hlibrary.setup build 

Bug#984174: marked as done (haskell-glib: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Tue, 01 Feb 2022 18:48:46 +
with message-id 
and subject line Bug#984167: fixed in c2hs 0.28.8-1
has caused the Debian Bug report #984167,
regarding haskell-glib: ftbfs with GCC-11
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.)


-- 
984167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:haskell-glib
Version: 0.13.8.1-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/haskell-glib_0.13.8.1-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
include bytestring-0.10.10.1
include containers-0.6.2.1
include text-1.2.4.0
include utf8-string-1.0.1.1-K3Cc2i5eeGM49mkpXdBKoc

System.Glib=glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx:System.Glib,System.Glib.Attributes=glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx:System.Glib.Attributes,System.Glib.FFI=glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx:System.Glib.FFI,System.Glib.Flags=glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx:System.Glib.Flags,System.Glib.GDateTime=glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx:System.Glib.GDateTime,System.Glib.GError=glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx:System.Glib.GError,System.Glib.GList=glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx:System.Glib.GList,System.Glib.GObject=glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx:System.Glib.GObject,System.Glib.GParameter=glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx:System.Glib.GParameter,System.Glib.GString=glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx:System.Glib.GString,System.Glib.GType=glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx:System.Glib.GType,System.Glib.GTypeConstants=glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx:System.Glib.GTypeConstants,System.Glib.GValue=glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx:System.Glib.GValue
 
,System.Glib.GValueTypes=glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx:System.Glib.GValueTypes,System.Glib.MainLoop=glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx:System.Glib.MainLoop,System.Glib.Properties=glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx:System.Glib.Properties,System.Glib.Signals=glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx:System.Glib.Signals,System.Glib.StoreValue=glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx:System.Glib.StoreValue,System.Glib.Types=glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx:System.Glib.Types,System.Glib.UTFString=glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx:System.Glib.UTFString,System.Glib.Utils=glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx:System.Glib.Utils
Ready component graph:
definite glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx
depends base-4.13.0.0
depends bytestring-0.10.10.1
depends containers-0.6.2.1
depends text-1.2.4.0
depends utf8-string-1.0.1.1-K3Cc2i5eeGM49mkpXdBKoc
Using Cabal-3.0.1.0 compiled by ghc-8.8
Using compiler: ghc-8.8.4
Using install prefix: /usr
Executables installed in: /usr/bin
Libraries installed in:
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4/glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx
Dynamic Libraries installed in:
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4
Private executables installed in:
/usr/lib/x86_64-linux-ghc-8.8.4/glib-0.13.8.1
Data files installed in: /usr/share/glib
Documentation installed in:

Bug#984173: marked as done (haskell-gtk3: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Tue, 01 Feb 2022 18:48:46 +
with message-id 
and subject line Bug#984167: fixed in c2hs 0.28.8-1
has caused the Debian Bug report #984167,
regarding haskell-gtk3: ftbfs with GCC-11
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.)


-- 
984167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:haskell-gtk3
Version: 0.15.5-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/haskell-gtk3_0.15.5-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
Ready component graph:
definite gtk3-0.15.5-7uv6caKJQrvHKk75JRMzUH
depends array-0.5.4.0
depends base-4.13.0.0
depends bytestring-0.10.10.1
depends cairo-0.13.8.1-9ROOXD4as1uLn8sCpDXiTi
depends containers-0.6.2.1
depends gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W
depends glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx
depends mtl-2.2.2
depends pango-0.13.8.1-J6ZPsrZFOIY2Xy7NzhFm7o
depends text-1.2.4.0
Using Cabal-3.0.1.0 compiled by ghc-8.8
Using compiler: ghc-8.8.4
Using install prefix: /usr
Executables installed in: /usr/bin
Libraries installed in:
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4/gtk3-0.15.5-7uv6caKJQrvHKk75JRMzUH
Dynamic Libraries installed in:
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4
Private executables installed in: /usr/lib/x86_64-linux-ghc-8.8.4/gtk3-0.15.5
Data files installed in: /usr/share/gtk3
Documentation installed in: /usr/share/doc/x86_64-linux-ghc-8.8.4/gtk3-0.15.5
Configuration files installed in: /usr/etc
No alex found
Using ar found on system at: /usr/bin/x86_64-linux-gnu-ar
No c2hs found
No cpphs found
No doctest found
Using gcc version 11 found on system at: /usr/bin/x86_64-linux-gnu-gcc
Using ghc version 8.8.4 found on system at: /usr/bin/ghc
Using ghc-pkg version 8.8.4 found on system at: /usr/bin/ghc-pkg
No ghcjs found
No ghcjs-pkg found
No greencard found
Using gtk2hsC2hs version 0.13.13 found on system at: /usr/bin/gtk2hsC2hs
Using gtk2hsHookGenerator found on system at: /usr/bin/gtk2hsHookGenerator
Using gtk2hsTypeGen found on system at: /usr/bin/gtk2hsTypeGen
Using haddock version 2.23.0 found on system at: /usr/bin/haddock
No happy found
Using haskell-suite found on system at: haskell-suite-dummy-location
Using haskell-suite-pkg found on system at: haskell-suite-pkg-dummy-location
No hmake found
Using hpc version 0.67 found on system at: /usr/bin/hpc
Using hsc2hs version 0.68.7 found on system at: /usr/bin/hsc2hs
Using hscolour version 1.24 found on system at: /usr/bin/HsColour
No jhc found
Using ld found on system at: /usr/bin/x86_64-linux-gnu-ld.gold
Using pkg-config version 0.29.2 found on system at: /usr/bin/pkg-config
Using runghc version 8.8.4 found on system at: /usr/bin/runghc
Using strip version 2.35 found on system at: /usr/bin/strip
Using tar found on system at: /bin/tar
No uhc found
/usr/bin/pkg-config --modversion gthread-2.0
/usr/bin/pkg-config --modversion 'gtk+-3.0'
Ensuring that class hierarchy in Graphics/UI/Gtk/Types.chs is up-to-date.
Ensuring that callback hooks in 

Bug#984172: marked as done (haskell-gio: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Tue, 01 Feb 2022 18:48:46 +
with message-id 
and subject line Bug#984167: fixed in c2hs 0.28.8-1
has caused the Debian Bug report #984167,
regarding haskell-gio: ftbfs with GCC-11
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.)


-- 
984167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:haskell-gio
Version: 0.13.8.1-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/haskell-gio_0.13.8.1-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
include bytestring-0.10.10.1
include containers-0.6.2.1
include glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx
include mtl-2.2.2

System.GIO=gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W:System.GIO,System.GIO.Async.AsyncResult=gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W:System.GIO.Async.AsyncResult,System.GIO.Async.Cancellable=gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W:System.GIO.Async.Cancellable,System.GIO.Enums=gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W:System.GIO.Enums,System.GIO.File.AppInfo=gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W:System.GIO.File.AppInfo,System.GIO.File.ContentType=gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W:System.GIO.File.ContentType,System.GIO.File.File=gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W:System.GIO.File.File,System.GIO.File.FileAttribute=gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W:System.GIO.File.FileAttribute,System.GIO.File.FileEnumerator=gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W:System.GIO.File.FileEnumerator,System.GIO.File.FileInfo=gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W:System.GIO.File.FileInfo,System.GIO.File.FileMonitor=gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W:System.GIO.File.FileMonitor,System.GIO.File.IOError=gio-0.13.8.1-HiLx4rVjKnS
 
7eInnEzgc9W:System.GIO.File.IOError,System.GIO.File.MountOperation=gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W:System.GIO.File.MountOperation,System.GIO.Icons.Emblem=gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W:System.GIO.Icons.Emblem,System.GIO.Icons.EmblemedIcon=gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W:System.GIO.Icons.EmblemedIcon,System.GIO.Icons.FileIcon=gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W:System.GIO.Icons.FileIcon,System.GIO.Icons.Icon=gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W:System.GIO.Icons.Icon,System.GIO.Icons.ThemedIcon=gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W:System.GIO.Icons.ThemedIcon,System.GIO.Types=gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W:System.GIO.Types,System.GIO.Volumes.Drive=gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W:System.GIO.Volumes.Drive,System.GIO.Volumes.Mount=gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W:System.GIO.Volumes.Mount,System.GIO.Volumes.Volume=gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W:System.GIO.Volumes.Volume,System.GIO.Volumes.VolumeMonitor=gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W:System.GIO.Volumes.Volum
 eMonitor
Ready component graph:
definite gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W
depends array-0.5.4.0
depends base-4.13.0.0
depends bytestring-0.10.10.1
depends containers-0.6.2.1
depends glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx
depends mtl-2.2.2
Using Cabal-3.0.1.0 compiled by ghc-8.8
Using compiler: ghc-8.8.4
Using install prefix: /usr
Executables installed in: /usr/bin
Libraries 

Bug#984170: marked as done (haskell-cairo: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Tue, 01 Feb 2022 18:48:46 +
with message-id 
and subject line Bug#984167: fixed in c2hs 0.28.8-1
has caused the Debian Bug report #984167,
regarding haskell-cairo: ftbfs with GCC-11
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.)


-- 
984167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:haskell-cairo
Version: 0.13.8.1-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/haskell-cairo_0.13.8.1-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
Libraries installed in:
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4/cairo-0.13.8.1-9ROOXD4as1uLn8sCpDXiTi
Dynamic Libraries installed in:
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4
Private executables installed in:
/usr/lib/x86_64-linux-ghc-8.8.4/cairo-0.13.8.1
Data files installed in: /usr/share/cairo
Documentation installed in:
/usr/share/doc/x86_64-linux-ghc-8.8.4/cairo-0.13.8.1
Configuration files installed in: /usr/etc
No alex found
Using ar found on system at: /usr/bin/x86_64-linux-gnu-ar
No c2hs found
No cpphs found
No doctest found
Using gcc version 11 found on system at: /usr/bin/x86_64-linux-gnu-gcc
Using ghc version 8.8.4 found on system at: /usr/bin/ghc
Using ghc-pkg version 8.8.4 found on system at: /usr/bin/ghc-pkg
No ghcjs found
No ghcjs-pkg found
No greencard found
Using gtk2hsC2hs version 0.13.13 found on system at: /usr/bin/gtk2hsC2hs
Using gtk2hsHookGenerator found on system at: /usr/bin/gtk2hsHookGenerator
Using gtk2hsTypeGen found on system at: /usr/bin/gtk2hsTypeGen
Using haddock version 2.23.0 found on system at: /usr/bin/haddock
No happy found
Using haskell-suite found on system at: haskell-suite-dummy-location
Using haskell-suite-pkg found on system at: haskell-suite-pkg-dummy-location
No hmake found
Using hpc version 0.67 found on system at: /usr/bin/hpc
Using hsc2hs version 0.68.7 found on system at: /usr/bin/hsc2hs
Using hscolour version 1.24 found on system at: /usr/bin/HsColour
No jhc found
Using ld found on system at: /usr/bin/x86_64-linux-gnu-ld.gold
Using pkg-config version 0.29.2 found on system at: /usr/bin/pkg-config
Using runghc version 8.8.4 found on system at: /usr/bin/runghc
Using strip version 2.35 found on system at: /usr/bin/strip
Using tar found on system at: /bin/tar
No uhc found
/usr/bin/pkg-config --modversion cairo
/usr/bin/pkg-config --modversion cairo-pdf
/usr/bin/pkg-config --modversion cairo-ps
/usr/bin/pkg-config --modversion cairo-svg
touch configure-ghc-stamp
. /usr/share/haskell-devscripts/Dh_Haskell.sh &&\
haddock_recipe
Running debian/hlibrary.setup haddock --builddir=dist-ghc 
--with-haddock=/usr/bin/haddock --with-ghc=ghc --verbose=2 --html --hoogle 
--haddock-options=\"--mathjax=file:///usr/share/javascript/mathjax/MathJax.js\" 
--hyperlink-source
/usr/bin/haddock --version
/usr/bin/ghc --numeric-version
/usr/bin/haddock --ghc-version 
'--mathjax=file:///usr/share/javascript/mathjax/MathJax.js'
/usr/bin/ghc --print-libdir
/usr/bin/ghc-pkg init dist-ghc/package.conf.inplace
creating dist-ghc/build
creating dist-ghc/build/autogen
creating 

Bug#984168: marked as done (haskell-bz2: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Tue, 01 Feb 2022 18:48:46 +
with message-id 
and subject line Bug#984167: fixed in c2hs 0.28.8-1
has caused the Debian Bug report #984167,
regarding haskell-bz2: ftbfs with GCC-11
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.)


-- 
984167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:haskell-bz2
Version: 1.0.0.1-2
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/haskell-bz2_1.0.0.1-2_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
include deepseq-1.4.4.0
include directory-1.3.6.0
include filepath-1.4.2.1
include tasty-1.2.3-AZt8xI2xlno8v5hDADqrNN
include tasty-golden-2.3.3.2-6sJb7oXGG78cNUBuhO2MY
include tasty-hunit-0.10.0.2-BqZUGn5O6hLEnVSlkj273H
Ready component graph:
definite bz2-1.0.0.1-6nxzksin47k5tsH0wSuJKl
depends base-4.13.0.0
depends bytestring-0.10.10.1
definite bz2-1.0.0.1-1kvSrlJqb0iAhQ9t5u3rGW-bz2-test
depends base-4.13.0.0
depends bytestring-0.10.10.1
depends bz2-1.0.0.1-6nxzksin47k5tsH0wSuJKl
depends deepseq-1.4.4.0
depends directory-1.3.6.0
depends filepath-1.4.2.1
depends tasty-1.2.3-AZt8xI2xlno8v5hDADqrNN
depends tasty-golden-2.3.3.2-6sJb7oXGG78cNUBuhO2MY
depends tasty-hunit-0.10.0.2-BqZUGn5O6hLEnVSlkj273H
Using Cabal-3.0.1.0 compiled by ghc-8.8
Using compiler: ghc-8.8.4
Using install prefix: /usr
Executables installed in: /usr/bin
Libraries installed in:
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4/bz2-1.0.0.1-6nxzksin47k5tsH0wSuJKl
Dynamic Libraries installed in:
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4
Private executables installed in: /usr/lib/x86_64-linux-ghc-8.8.4/bz2-1.0.0.1
Data files installed in: /usr/share/bz2
Documentation installed in: /usr/share/doc/x86_64-linux-ghc-8.8.4/bz2-1.0.0.1
Configuration files installed in: /usr/etc
No alex found
Using ar found on system at: /usr/bin/x86_64-linux-gnu-ar
Using c2hs version 0.28.6 found on system at: /usr/bin/c2hs
No cpphs found
No doctest found
Using gcc version 11 found on system at: /usr/bin/x86_64-linux-gnu-gcc
Using ghc version 8.8.4 found on system at: /usr/bin/ghc
Using ghc-pkg version 8.8.4 found on system at: /usr/bin/ghc-pkg
No ghcjs found
No ghcjs-pkg found
No greencard found
Using haddock version 2.23.0 found on system at: /usr/bin/haddock
No happy found
Using haskell-suite found on system at: haskell-suite-dummy-location
Using haskell-suite-pkg found on system at: haskell-suite-pkg-dummy-location
No hmake found
Using hpc version 0.67 found on system at: /usr/bin/hpc
Using hsc2hs version 0.68.7 found on system at: /usr/bin/hsc2hs
No hscolour found
No jhc found
Using ld found on system at: /usr/bin/x86_64-linux-gnu-ld.gold
No pkg-config found
Using runghc version 8.8.4 found on system at: /usr/bin/runghc
Using strip version 2.35 found on system at: /usr/bin/strip
Using tar found on system at: /bin/tar
No uhc found
touch configure-ghc-stamp
. /usr/share/haskell-devscripts/Dh_Haskell.sh && \
build_recipe
Running 

Bug#984169: marked as done (haskell-gi-cairo-render: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Tue, 01 Feb 2022 18:48:46 +
with message-id 
and subject line Bug#984167: fixed in c2hs 0.28.8-1
has caused the Debian Bug report #984167,
regarding haskell-gi-cairo-render: ftbfs with GCC-11
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.)


-- 
984167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:haskell-gi-cairo-render
Version: 0.0.1-4
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/haskell-gi-cairo-render_0.0.1-4_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
depends mtl-2.2.2
depends text-1.2.4.0
depends utf8-string-1.0.1.1-K3Cc2i5eeGM49mkpXdBKoc
Using Cabal-3.0.1.0 compiled by ghc-8.8
Using compiler: ghc-8.8.4
Using install prefix: /usr
Executables installed in: /usr/bin
Libraries installed in:
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4/gi-cairo-render-0.0.1-BEDfByqAkJrDv737GOKx7o
Dynamic Libraries installed in:
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4
Private executables installed in:
/usr/lib/x86_64-linux-ghc-8.8.4/gi-cairo-render-0.0.1
Data files installed in: /usr/share/gi-cairo-render
Documentation installed in:
/usr/share/doc/x86_64-linux-ghc-8.8.4/gi-cairo-render-0.0.1
Configuration files installed in: /usr/etc
No alex found
Using ar found on system at: /usr/bin/x86_64-linux-gnu-ar
Using c2hs version 0.28.6 found on system at: /usr/bin/c2hs
No cpphs found
No doctest found
Using gcc version 11 found on system at: /usr/bin/x86_64-linux-gnu-gcc
Using ghc version 8.8.4 found on system at: /usr/bin/ghc
Using ghc-pkg version 8.8.4 found on system at: /usr/bin/ghc-pkg
No ghcjs found
No ghcjs-pkg found
No greencard found
Using haddock version 2.23.0 found on system at: /usr/bin/haddock
No happy found
Using haskell-suite found on system at: haskell-suite-dummy-location
Using haskell-suite-pkg found on system at: haskell-suite-pkg-dummy-location
No hmake found
Using hpc version 0.67 found on system at: /usr/bin/hpc
Using hsc2hs version 0.68.7 found on system at: /usr/bin/hsc2hs
Using hscolour version 1.24 found on system at: /usr/bin/HsColour
No jhc found
Using ld found on system at: /usr/bin/x86_64-linux-gnu-ld.gold
Using pkg-config version 0.29.2 found on system at: /usr/bin/pkg-config
Using runghc version 8.8.4 found on system at: /usr/bin/runghc
Using strip version 2.35 found on system at: /usr/bin/strip
Using tar found on system at: /bin/tar
No uhc found
touch configure-ghc-stamp
. /usr/share/haskell-devscripts/Dh_Haskell.sh &&\
haddock_recipe
Running debian/hlibrary.setup haddock --builddir=dist-ghc 
--with-haddock=/usr/bin/haddock --with-ghc=ghc --verbose=2 --html --hoogle 
--haddock-options=\"--mathjax=file:///usr/share/javascript/mathjax/MathJax.js\" 
--hyperlink-source
/usr/bin/haddock --version
/usr/bin/ghc --numeric-version
/usr/bin/haddock --ghc-version 
'--mathjax=file:///usr/share/javascript/mathjax/MathJax.js'
/usr/bin/ghc --print-libdir
/usr/bin/ghc-pkg init dist-ghc/package.conf.inplace
creating dist-ghc/build
creating dist-ghc/build/autogen
creating dist-ghc/build/autogen
Preprocessing library 

Bug#984167: marked as done (c2hs fails with code preprocessed by gcc-11)

[Debian Bug Tracking System]

Your message dated Tue, 01 Feb 2022 18:48:46 +
with message-id 
and subject line Bug#984167: fixed in c2hs 0.28.8-1
has caused the Debian Bug report #984167,
regarding c2hs fails with code preprocessed by gcc-11
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.)


-- 
984167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:haskell-alsa-mixer
Version: 0.3.0-2
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/haskell-alsa-mixer_0.3.0-2_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
depends alsa-core-0.5.0.1-K0SXio6EcM1GW9NwssjHIV
depends base-4.13.0.0
depends unix-2.7.2.2
Using Cabal-3.0.1.0 compiled by ghc-8.8
Using compiler: ghc-8.8.4
Using install prefix: /usr
Executables installed in: /usr/bin
Libraries installed in:
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4/alsa-mixer-0.3.0-1I5T9An2neOISzuUiVqd6Y
Dynamic Libraries installed in:
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4
Private executables installed in:
/usr/lib/x86_64-linux-ghc-8.8.4/alsa-mixer-0.3.0
Data files installed in: /usr/share/alsa-mixer
Documentation installed in:
/usr/share/doc/x86_64-linux-ghc-8.8.4/alsa-mixer-0.3.0
Configuration files installed in: /usr/etc
No alex found
Using ar found on system at: /usr/bin/x86_64-linux-gnu-ar
Using c2hs version 0.28.6 found on system at: /usr/bin/c2hs
No cpphs found
No doctest found
Using gcc version 11 found on system at: /usr/bin/x86_64-linux-gnu-gcc
Using ghc version 8.8.4 found on system at: /usr/bin/ghc
Using ghc-pkg version 8.8.4 found on system at: /usr/bin/ghc-pkg
No ghcjs found
No ghcjs-pkg found
No greencard found
Using haddock version 2.23.0 found on system at: /usr/bin/haddock
No happy found
Using haskell-suite found on system at: haskell-suite-dummy-location
Using haskell-suite-pkg found on system at: haskell-suite-pkg-dummy-location
No hmake found
Using hpc version 0.67 found on system at: /usr/bin/hpc
Using hsc2hs version 0.68.7 found on system at: /usr/bin/hsc2hs
No hscolour found
No jhc found
Using ld found on system at: /usr/bin/x86_64-linux-gnu-ld.gold
No pkg-config found
Using runghc version 8.8.4 found on system at: /usr/bin/runghc
Using strip version 2.35 found on system at: /usr/bin/strip
Using tar found on system at: /bin/tar
No uhc found
touch configure-ghc-stamp
. /usr/share/haskell-devscripts/Dh_Haskell.sh &&\
haddock_recipe
Running debian/hlibrary.setup haddock --builddir=dist-ghc 
--with-haddock=/usr/bin/haddock --with-ghc=ghc --verbose=2 --html --hoogle 
--haddock-options=\"--mathjax=file:///usr/share/javascript/mathjax/MathJax.js\" 
--hyperlink-source
/usr/bin/haddock --version
/usr/bin/ghc --numeric-version
/usr/bin/haddock --ghc-version 
'--mathjax=file:///usr/share/javascript/mathjax/MathJax.js'
/usr/bin/ghc --print-libdir
/usr/bin/ghc-pkg init dist-ghc/package.conf.inplace
creating dist-ghc/build
creating dist-ghc/build/autogen
creating dist-ghc/build/autogen
Preprocessing library for alsa-mixer-0.3.0..
creating dist-ghc/build/Sound/ALSA/Mixer
creating dist-ghc/build/Sound/ALSA
creating 

Processed: src:scm: fails to migrate to testing for too long: FTBFS on armel, armhf and mipsel

[Debian Bug Tracking System]

Processing control commands:

> close -1 5f3-1
Bug #1004757 [src:scm] src:scm: fails to migrate to testing for too long: FTBFS 
on armel, armhf and mipsel
Marked as fixed in versions scm/5f3-1.
Bug #1004757 [src:scm] src:scm: fails to migrate to testing for too long: FTBFS 
on armel, armhf and mipsel
Marked Bug as done

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

Bug#1004757: src:scm: fails to migrate to testing for too long: FTBFS on armel, armhf and mipsel

[Paul Gevers]

Source: scm
Version: 5f2-2
Severity: serious
Control: close -1 5f3-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:scm has been trying to migrate for 61 days 
[2]. Hence, I am filing this bug. Your package fails to build from 
source on armel, armhf and mipsel, where it built 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=scm



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:python-confluent-kafka: fails to migrate to testing for too long: FTBFS on s390x

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.7.0-1
Bug #1004756 [src:python-confluent-kafka] src:python-confluent-kafka: fails to 
migrate to testing for too long: FTBFS on s390x
Marked as fixed in versions python-confluent-kafka/1.7.0-1.
Bug #1004756 [src:python-confluent-kafka] src:python-confluent-kafka: fails to 
migrate to testing for too long: FTBFS on s390x
Marked Bug as done

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

Bug#1004756: src:python-confluent-kafka: fails to migrate to testing for too long: FTBFS on s390x

[Paul Gevers]

Source: python-confluent-kafka
Version: 1.3.0-2
Severity: serious
Control: close -1 1.7.0-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:python-confluent-kafka has been trying to 
migrate for 61 days [2]. Hence, I am filing this bug. Your package fails 
to build from source on s390x while it built there 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=python-confluent-kafka



OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#984167: Possibly fixed upstream

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #984167 [c2hs] c2hs fails with code preprocessed by gcc-11
Bug #984168 [c2hs] haskell-bz2: ftbfs with GCC-11
Bug #984169 [c2hs] haskell-gi-cairo-render: ftbfs with GCC-11
Bug #984170 [c2hs] haskell-cairo: ftbfs with GCC-11
Bug #984171 [c2hs] haskell-gtk: ftbfs with GCC-11
Bug #984172 [c2hs] haskell-gio: ftbfs with GCC-11
Bug #984173 [c2hs] haskell-gtk3: ftbfs with GCC-11
Bug #984174 [c2hs] haskell-glib: ftbfs with GCC-11
Bug #984176 [c2hs] haskell-pango: ftbfs with GCC-11
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.

-- 
984167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984167
984168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984168
984169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984169
984170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984170
984171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984171
984172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984172
984173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984173
984174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984174
984176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984176
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#984167: Possibly fixed upstream

[Apollon Oikonomopoulos]

Control: tags -1 pending

Verified this and the fix, pending upload.

Also, I should have read the instructions better and add a blocking bug 
rather than reassign/merge. Apologies for the inconvenience doko and 
company, I'll do verification builds myself and I promise I'll be more 
careful next time :-)

Regards,
Apollon

Bug#1004752: marked as done (python-django: CVE-2022-22818 CVE-2022-23833)

[Debian Bug Tracking System]

Your message dated Tue, 01 Feb 2022 17:49:41 +
with message-id 
and subject line Bug#1004752: fixed in python-django 2:3.2.12-1
has caused the Debian Bug report #1004752,
regarding python-django: CVE-2022-22818 CVE-2022-23833
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.)


-- 
1004752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004752
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-django
Version: 1:1.10.7-2+deb9u14
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for python-django:

* CVE-2022-22818: Possible XSS via {% debug %} template tag

  The {% debug %} template tag didn't properly encode the current
  context, posing an XSS attack vector.

  In order to avoid this vulnerability, {% debug %} no longer outputs
  information when the DEBUG setting is False, and it ensures all
  context variables are correctly escaped when the DEBUG setting is
  True.

* CVE-2022-23833: Denial-of-service possibility in file uploads

  Passing certain inputs to multipart forms could result in an
  infinite loop when parsing files.

This issue has severity "medium" according to the Django security policy.
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-22818
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-22818
[1] https://security-tracker.debian.org/tracker/CVE-2022-23833
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23833


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: python-django
Source-Version: 2:3.2.12-1
Done: Chris Lamb 

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated python-django 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, 01 Feb 2022 09:28:58 -0800
Source: python-django
Built-For-Profiles: nocheck
Architecture: source
Version: 2:3.2.12-1
Distribution: unstable
Urgency: high
Maintainer: Debian Python Team 
Changed-By: Chris Lamb 
Closes: 1004752
Changes:
 python-django (2:3.2.12-1) unstable; urgency=high
 .
   * New upstream security release:
 .
 - CVE-2022-22818: Possible XSS via {% debug %} template tag.
 .
   The {% debug %} template tag didn't properly encode the current context,
   posing an XSS attack vector.
 .
   In order to avoid this vulnerability, {% debug %} no longer outputs
   information when the DEBUG setting is False, and it ensures all context
   variables are correctly escaped when the DEBUG setting is True.
 .
 - CVE-2022-23833: Denial-of-service possibility in file uploads.
 .
   Passing certain inputs to multipart forms could result in an
   infinite loop when parsing files.
 .
 See 
 for more information. (Closes: #1004752)
Checksums-Sha1:
 cdc813e579d51018d8416c449d14219479d931c2 2807 python-django_3.2.12-1.dsc
 93f6c3f0fd89f5c5a44dee688e752a258900a54e 9812448 
python-django_3.2.12.orig.tar.gz
 8f3bfe43385673b8ae937169c395c5dfba8de2fb 35060 
python-django_3.2.12-1.debian.tar.xz
 d215015572a9dd6e89c8a97b30fb63f9692033db 8089 
python-django_3.2.12-1_amd64.buildinfo
Checksums-Sha256:
 c33aa89544c0b0a5971df3cb18f1fd1deb9ed41035cade5364cda7f3f7f956cc 2807 
python-django_3.2.12-1.dsc
 9772e6935703e59e993960832d66a614cf0233a1c5123bc6224ecc6ad69e41e2 9812448 
python-django_3.2.12.orig.tar.gz
 7f1bf88141e5e9e06cbf1bc60606ed53b6cb629c384a3dde5a0068aa46eb3591 35060 
python-django_3.2.12-1.debian.tar.xz
 b99d78aab5699dbd4b57bdc704c4d980118b2df22b303d35d033741e67698a62 8089 
python-django_3.2.12-1_amd64.buildinfo
Files:
 350062ea51fb57ddd8a0b72744d808ef 2807 python optional 

Bug#1004752: marked as done (python-django: CVE-2022-22818 CVE-2022-23833)

[Debian Bug Tracking System]

Your message dated Tue, 01 Feb 2022 17:34:19 +
with message-id 
and subject line Bug#1004752: fixed in python-django 2:4.0.2-1
has caused the Debian Bug report #1004752,
regarding python-django: CVE-2022-22818 CVE-2022-23833
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.)


-- 
1004752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004752
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-django
Version: 1:1.10.7-2+deb9u14
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for python-django:

* CVE-2022-22818: Possible XSS via {% debug %} template tag

  The {% debug %} template tag didn't properly encode the current
  context, posing an XSS attack vector.

  In order to avoid this vulnerability, {% debug %} no longer outputs
  information when the DEBUG setting is False, and it ensures all
  context variables are correctly escaped when the DEBUG setting is
  True.

* CVE-2022-23833: Denial-of-service possibility in file uploads

  Passing certain inputs to multipart forms could result in an
  infinite loop when parsing files.

This issue has severity "medium" according to the Django security policy.
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-22818
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-22818
[1] https://security-tracker.debian.org/tracker/CVE-2022-23833
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23833


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: python-django
Source-Version: 2:4.0.2-1
Done: Chris Lamb 

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated python-django 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, 01 Feb 2022 09:02:51 -0800
Source: python-django
Built-For-Profiles: nocheck
Architecture: source
Version: 2:4.0.2-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Chris Lamb 
Closes: 1004752
Changes:
 python-django (2:4.0.2-1) experimental; urgency=medium
 .
   * New upstream security release:
 .
 - CVE-2022-22818: Possible XSS via {% debug %} template tag.
   The {% debug %} template tag didn't properly encode the current context,
   posing an XSS attack vector.
 .
   In order to avoid this vulnerability, {% debug %} no longer outputs
   information when the DEBUG setting is False, and it ensures all context
   variables are correctly escaped when the DEBUG setting is True.
 .
 - CVE-2022-23833: Denial-of-service possibility in file uploads
 .
   Passing certain inputs to multipart forms could result in an
   infinite loop when parsing files.
 .
 See 

Bug#1004752: python-django: CVE-2022-22818 CVE-2022-23833

[Chris Lamb]

Package: python-django
Version: 1:1.10.7-2+deb9u14
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for python-django:

* CVE-2022-22818: Possible XSS via {% debug %} template tag

  The {% debug %} template tag didn't properly encode the current
  context, posing an XSS attack vector.

  In order to avoid this vulnerability, {% debug %} no longer outputs
  information when the DEBUG setting is False, and it ensures all
  context variables are correctly escaped when the DEBUG setting is
  True.

* CVE-2022-23833: Denial-of-service possibility in file uploads

  Passing certain inputs to multipart forms could result in an
  infinite loop when parsing files.

This issue has severity "medium" according to the Django security policy.
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-22818
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-22818
[1] https://security-tracker.debian.org/tracker/CVE-2022-23833
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23833


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Processed: closing 1002183

[Debian Bug Tracking System]

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

> close 1002183 8.2.0-1
Bug #1002183 [src:minexpert2] minexpert2: FTBFS: 
MzIntegrationParamsDlg.cpp:181:27: error: ‘class pappso::MzIntegrationParams’ 
has no member named ‘isApplySavGolFilter’
Marked as fixed in versions minexpert2/8.2.0-1.
Bug #1002183 [src:minexpert2] minexpert2: FTBFS: 
MzIntegrationParamsDlg.cpp:181:27: error: ‘class pappso::MzIntegrationParams’ 
has no member named ‘isApplySavGolFilter’
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Merge all Haskell GCC-11 FTBFS bugs under c2hs

[Debian Bug Tracking System]

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

> reassign 984168 c2hs
Bug #984168 [src:haskell-bz2] haskell-bz2: ftbfs with GCC-11
Bug reassigned from package 'src:haskell-bz2' to 'c2hs'.
No longer marked as found in versions haskell-bz2/1.0.0.1-2.
Ignoring request to alter fixed versions of bug #984168 to the same values 
previously set
> reassign 984169 c2hs
Bug #984169 [src:haskell-gi-cairo-render] haskell-gi-cairo-render: ftbfs with 
GCC-11
Bug reassigned from package 'src:haskell-gi-cairo-render' to 'c2hs'.
No longer marked as found in versions haskell-gi-cairo-render/0.0.1-4.
Ignoring request to alter fixed versions of bug #984169 to the same values 
previously set
> reassign 984170 c2hs
Bug #984170 [src:haskell-cairo] haskell-cairo: ftbfs with GCC-11
Bug reassigned from package 'src:haskell-cairo' to 'c2hs'.
No longer marked as found in versions haskell-cairo/0.13.8.1-1.
Ignoring request to alter fixed versions of bug #984170 to the same values 
previously set
> reassign 984171 c2hs
Bug #984171 [src:haskell-gtk] haskell-gtk: ftbfs with GCC-11
Bug reassigned from package 'src:haskell-gtk' to 'c2hs'.
No longer marked as found in versions haskell-gtk/0.15.5-1.
Ignoring request to alter fixed versions of bug #984171 to the same values 
previously set
> reassign 984172 c2hs
Bug #984172 [src:haskell-gio] haskell-gio: ftbfs with GCC-11
Bug reassigned from package 'src:haskell-gio' to 'c2hs'.
No longer marked as found in versions haskell-gio/0.13.8.1-1.
Ignoring request to alter fixed versions of bug #984172 to the same values 
previously set
> reassign 984173 c2hs
Bug #984173 [src:haskell-gtk3] haskell-gtk3: ftbfs with GCC-11
Bug reassigned from package 'src:haskell-gtk3' to 'c2hs'.
No longer marked as found in versions haskell-gtk3/0.15.5-1.
Ignoring request to alter fixed versions of bug #984173 to the same values 
previously set
> reassign 984174 c2hs
Bug #984174 [src:haskell-glib] haskell-glib: ftbfs with GCC-11
Bug reassigned from package 'src:haskell-glib' to 'c2hs'.
No longer marked as found in versions haskell-glib/0.13.8.1-1.
Ignoring request to alter fixed versions of bug #984174 to the same values 
previously set
> reassign 984176 c2hs
Bug #984176 [src:haskell-pango] haskell-pango: ftbfs with GCC-11
Bug reassigned from package 'src:haskell-pango' to 'c2hs'.
No longer marked as found in versions haskell-pango/0.13.8.1-1.
Ignoring request to alter fixed versions of bug #984176 to the same values 
previously set
> forcemerge 984167 984168 984169 984170 984171 984172 984173 984174 984176
Bug #984167 [c2hs] c2hs fails with code preprocessed by gcc-11
Bug #984172 [c2hs] haskell-gio: ftbfs with GCC-11
Set Bug forwarded-to-address to 'https://github.com/haskell/c2hs/issues/268'.
Marked as found in versions c2hs/0.28.6-1.
Added tag(s) upstream and fixed-upstream.
Bug #984176 [c2hs] haskell-pango: ftbfs with GCC-11
Set Bug forwarded-to-address to 'https://github.com/haskell/c2hs/issues/268'.
Marked as found in versions c2hs/0.28.6-1.
Added tag(s) upstream and fixed-upstream.
Bug #984173 [c2hs] haskell-gtk3: ftbfs with GCC-11
Set Bug forwarded-to-address to 'https://github.com/haskell/c2hs/issues/268'.
Marked as found in versions c2hs/0.28.6-1.
Added tag(s) upstream and fixed-upstream.
Bug #984169 [c2hs] haskell-gi-cairo-render: ftbfs with GCC-11
Set Bug forwarded-to-address to 'https://github.com/haskell/c2hs/issues/268'.
Marked as found in versions c2hs/0.28.6-1.
Added tag(s) upstream and fixed-upstream.
Bug #984170 [c2hs] haskell-cairo: ftbfs with GCC-11
Set Bug forwarded-to-address to 'https://github.com/haskell/c2hs/issues/268'.
Marked as found in versions c2hs/0.28.6-1.
Added tag(s) fixed-upstream and upstream.
Bug #984171 [c2hs] haskell-gtk: ftbfs with GCC-11
Set Bug forwarded-to-address to 'https://github.com/haskell/c2hs/issues/268'.
Marked as found in versions c2hs/0.28.6-1.
Added tag(s) upstream and fixed-upstream.
Bug #984174 [c2hs] haskell-glib: ftbfs with GCC-11
Set Bug forwarded-to-address to 'https://github.com/haskell/c2hs/issues/268'.
Marked as found in versions c2hs/0.28.6-1.
Added tag(s) upstream and fixed-upstream.
Bug #984168 [c2hs] haskell-bz2: ftbfs with GCC-11
Set Bug forwarded-to-address to 'https://github.com/haskell/c2hs/issues/268'.
Marked as found in versions c2hs/0.28.6-1.
Added tag(s) upstream and fixed-upstream.
Merged 984167 984168 984169 984170 984171 984172 984173 984174 984176
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
984167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984167
984168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984168
984169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984169
984170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984170
984171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984171
984172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984172
984173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984173
984174: 

Bug#1004748: guestfs-tools ftbfs with new ocaml

[Matthias Klose]

Package: src:guestfs-tools
Version: 1.46.1-4
Severity: serious
Tags: sid bookworm

guestfs-tools ftbfs with new ocaml

[...]
Use the equivalent signed form: +C+D+E+F+L+M+P+S+U+V+Y+Z+X+52-3.
Hint: Enabling or disabling a warning by its mnemonic name requires a + or - 
prefix.
Hint: Did you make a spelling mistake when using a mnemonic name?
File "perl_edit.ml", line 30, characters 2-13:
30 |   c_edit_file (verbose ()) g (Guestfs.c_pointer g) file expr
   ^^^
Error (warning 6 [labels-omitted]): label verbose was omitted in the application
of this function.
make[4]: *** [Makefile:1806: perl_edit.cmx] Error 2
make[4]: *** Waiting for unfinished jobs
touch stamp-virt-customize.pod
make[4]: Leaving directory '/packages/tmp/guestfs-tools-1.46.1/customize'
make[3]: *** [Makefile:939: all] Error 2
make[3]: Leaving directory '/packages/tmp/guestfs-tools-1.46.1/customize'
make[2]: *** [Makefile:855: all-recursive] Error 1
make[2]: Leaving directory '/packages/tmp/guestfs-tools-1.46.1'
make[1]: *** [Makefile:769: all] Error 2
make[1]: Leaving directory '/packages/tmp/guestfs-tools-1.46.1'
dh_auto_build: error: make -j64 returned exit code 2
make: *** [debian/rules:19: binary-arch] Error 25

Bug#984167: Possibly fixed upstream

[Apollon Oikonomopoulos]

Control: reassign -1 c2hs
Control: retitle -1 c2hs fails with code preprocessed by gcc-11
Control: found -1 0.28.6-1
Control: tags -1 upstream fixed-upstream
Control: forwarded -1 https://github.com/haskell/c2hs/issues/268

Hi Rob,

On 15:57 Fri 03 Dec , Rob Moss wrote:
> I believe this is caused by a specific c2hs issue
> (https://github.com/haskell/c2hs/issues/268) which has been fixed in
> c2hs 0.28.8.

Thanks for bringing this up, indeed it looks like a valid issue. I'm 
reassigning to c2hs and tagging accordingly.

It also looks like this issue has been reported against multiple Haskell 
packages, I will proceed to merge all bugs under this one.

Cheers,
Apollon

Processed: Re: Bug#984167: Possibly fixed upstream

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 c2hs
Bug #984167 [src:haskell-alsa-mixer] haskell-alsa-mixer: ftbfs with GCC-11
Bug reassigned from package 'src:haskell-alsa-mixer' to 'c2hs'.
No longer marked as found in versions haskell-alsa-mixer/0.3.0-2.
Ignoring request to alter fixed versions of bug #984167 to the same values 
previously set
> retitle -1 c2hs fails with code preprocessed by gcc-11
Bug #984167 [c2hs] haskell-alsa-mixer: ftbfs with GCC-11
Changed Bug title to 'c2hs fails with code preprocessed by gcc-11' from 
'haskell-alsa-mixer: ftbfs with GCC-11'.
> found -1 0.28.6-1
Bug #984167 [c2hs] c2hs fails with code preprocessed by gcc-11
Marked as found in versions c2hs/0.28.6-1.
> tags -1 upstream fixed-upstream
Bug #984167 [c2hs] c2hs fails with code preprocessed by gcc-11
Added tag(s) fixed-upstream and upstream.
> forwarded -1 https://github.com/haskell/c2hs/issues/268
Bug #984167 [c2hs] c2hs fails with code preprocessed by gcc-11
Set Bug forwarded-to-address to 'https://github.com/haskell/c2hs/issues/268'.

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

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

[Vincent Lefevre]

On 2022-02-01 14:44:21 +0100, Vincent Lefevre wrote:
> 2022-02-01 14:23:23 1nEt2b-0008jG-97 SIGSEGV (maybe attempt to write to 
> immutable memory)
> 2022-02-01 14:23:23 1nEt2b-0008jG-97 Delivery status for xxx@yyy: got 0 of 7 
> bytes (pipeheader) from transport process 35015 for transport smtp
> 
> 2022-02-01 14:23:23 1nEt2b-0008jG-97 == xxx@yyy R=dnslookup T=remote_smtp 
> defer (-1): smtp transport process returned non-zero status 0x000b: 
> terminated by signal 11
> 2022-02-01 14:23:23 1nEt7z-00096o-IX <= <> R=1nEt2b-0008jG-97 U=Debian-exim 
> P=local S=783
> 2022-02-01 14:23:23 1nEt2b-0008jG-97 Frozen
> 2022-02-01 14:23:23 1nEt7z-00096o-IX => vlefevre 
>  R=local_user T=maildir_home
> 2022-02-01 14:23:23 1nEt7z-00096o-IX Completed
> 2022-02-01 14:23:23 End queue run: pid=35012
> 2022-02-01 14:28:19 Start queue run: pid=35460
> 2022-02-01 14:28:19 1nEt2b-0008jG-97 Message is frozen
> 2022-02-01 14:28:19 End queue run: pid=35460
> [...]
> 
> The consequence is that the mail is not sent, there are no retries,
> and the end user is not warned. So, from the end user point of view,
> the message is *silently lost*.

Some clarification: by "end user", I mean the author of the message.
There is an error message sent to postmaster, but not to the address
of the author of the message.

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

Processed: block 965518 with 1004024

[Debian Bug Tracking System]

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

> block 965518 with 1004024
Bug #965518 [src:fig2sxd] fig2sxd: Removal of obsolete debhelper compat 5 and 6 
in bookworm
965518 was not blocked by any bugs.
965518 was not blocking any bugs.
Added blocking bug(s) of 965518: 1004024
> thanks
Stopping processing here.

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

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

[Vincent Lefevre]

Package: exim4
Version: 4.95-3
Severity: serious

When sending a mail:

[...]
2022-02-01 14:23:22 1nEt2b-0008jG-97 H=mx2.mailchannels.net [34.214.163.59]: 
SMTP error from remote mail server after DATA: 450 [S09] Try Again Later
2022-02-01 14:23:22 1nEt2b-0008jG-97 H=mx2.mailchannels.net [34.214.163.59] TLS 
error on connection (recv): The TLS connection was non-properly terminated.
2022-02-01 14:23:23 1nEt2b-0008jG-97 SIGSEGV (maybe attempt to write to 
immutable memory)
2022-02-01 14:23:23 1nEt2b-0008jG-97 Delivery status for xxx@yyy: got 0 of 7 
bytes (pipeheader) from transport process 35015 for transport smtp

2022-02-01 14:23:23 1nEt2b-0008jG-97 == xxx@yyy R=dnslookup T=remote_smtp defer 
(-1): smtp transport process returned non-zero status 0x000b: terminated by 
signal 11
2022-02-01 14:23:23 1nEt7z-00096o-IX <= <> R=1nEt2b-0008jG-97 U=Debian-exim 
P=local S=783
2022-02-01 14:23:23 1nEt2b-0008jG-97 Frozen
2022-02-01 14:23:23 1nEt7z-00096o-IX => vlefevre 
 R=local_user T=maildir_home
2022-02-01 14:23:23 1nEt7z-00096o-IX Completed
2022-02-01 14:23:23 End queue run: pid=35012
2022-02-01 14:28:19 Start queue run: pid=35460
2022-02-01 14:28:19 1nEt2b-0008jG-97 Message is frozen
2022-02-01 14:28:19 End queue run: pid=35460
[...]

The consequence is that the mail is not sent, there are no retries,
and the end user is not warned. So, from the end user point of view,
the message is *silently lost*.

-- Package-specific info:
Exim version 4.95 #2 built 16-Dec-2021 18:26:32
Copyright (c) University of Cambridge, 1995 - 2018
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2020
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS TLS_resume move_frozen_messages DANE 
DKIM DNSSEC Event I18N OCSP PIPE_CONNECT PRDR Experimental_Queue_Ramp SOCKS SRS 
TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz 
dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 external plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Configuration file search path is 
/etc/exim4/exim4.conf:/var/lib/exim4/config.autogenerated
Configuration file is /var/lib/exim4/config.autogenerated
# /etc/exim4/update-exim4.conf.conf
#
# Edit this file and /etc/mailname by hand and execute update-exim4.conf
# yourself or use 'dpkg-reconfigure exim4-config'
#
# Please note that this is _not_ a dpkg-conffile and that automatic changes
# to this file might happen. The code handling this will honor your local
# changes, so this is usually fine, but will break local schemes that mess
# around with multiple versions of the file.
#
# update-exim4.conf uses this file to determine variable values to generate
# exim configuration macros for the configuration file.
#
# Most settings found in here do have corresponding questions in the
# Debconf configuration, but not all of them.
#
# This is a Debian specific file

dc_eximconfig_configtype='internet'
dc_other_hostnames='cventin.lip.ens-lyon.fr'
dc_local_interfaces='127.0.0.1 ; ::1'
dc_readhost=''
dc_relay_domains=''
dc_minimaldns='false'
dc_relay_nets=''
dc_smarthost=''
CFILEMODE='644'
dc_use_split_config='false'
dc_hide_mailname=''
dc_mailname_in_oh='true'
dc_localdelivery='maildir_home'
mailname:cventin.lip.ens-lyon.fr
# /etc/default/exim4
EX4DEF_VERSION=''

# 'combined' -   one daemon running queue and listening on SMTP port
# 'no'   -   no daemon running the queue
# 'separate' -   two separate daemons
# 'ppp'  -   only run queue with /etc/ppp/ip-up.d/exim4.
# 'nodaemon' - no daemon is started at all.
# 'queueonly' - only a queue running daemon is started, no SMTP listener.
# setting this to 'no' will also disable queueruns from /etc/ppp/ip-up.d/exim4
QUEUERUNNER='combined'
# how often should we run the queue
QUEUEINTERVAL='5m'
# options common to quez-runner and listening daemon
COMMONOPTIONS=''
# more options for the daemon/process running the queue (applies to the one
# started in /etc/ppp/ip-up.d/exim4, too.
QUEUERUNNEROPTIONS=''
# special flags given to exim directly after the -q. See exim(8)
QFLAGS=''
# Options for the SMTP listener daemon. By default, it is listening on
# port 25 only. To listen on more ports, it is recommended to use
# -oX 25:587:10025 -oP /var/run/exim4/exim.pid
SMTPLISTENEROPTIONS=''

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

Kernel: Linux 5.15.0-3-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked 

Bug#1004736: marked as done (libgupnp-dlna-2.0-4: missing Breaks+Replaces: libgupnp-dlna-2.0-3 (<< 0.12))

[Debian Bug Tracking System]

Your message dated Tue, 01 Feb 2022 13:18:50 +
with message-id 
and subject line Bug#1004736: fixed in gupnp-dlna 0.12.0-2
has caused the Debian Bug report #1004736,
regarding libgupnp-dlna-2.0-4: missing Breaks+Replaces: libgupnp-dlna-2.0-3 (<< 
0.12)
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.)


-- 
1004736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgupnp-dlna-2.0-4
Version: 0.12.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid 'installed while installing the package from 'experimental'.

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

  Preparing to unpack .../libgupnp-dlna-2.0-4_0.12.0-1_amd64.deb ...
  Unpacking libgupnp-dlna-2.0-4 (0.12.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgupnp-dlna-2.0-4_0.12.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/gupnp-dlna/libgstreamer.so', 
which is also in package libgupnp-dlna-2.0-3 0.10.5-4
  Errors were encountered while processing:
   /var/cache/apt/archives/libgupnp-dlna-2.0-4_0.12.0-1_amd64.deb

The following files are shipped by both packages:

usr/lib/x86_64-linux-gnu/gupnp-dlna/libgstreamer.so
usr/share/gupnp-dlna-2.0/dlna-profiles/aac.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/ac3.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/amr.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/avc.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/common.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/dlna-profiles.rng
usr/share/gupnp-dlna-2.0/dlna-profiles/jpeg.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/lpcm.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/mp3.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/mpeg-common.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/mpeg-ps.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/mpeg-ts.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/mpeg1.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/mpeg4.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/png.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/wma.xml


cheers,

Andreas


libgupnp-dlna-2.0-3=0.10.5-4_libgupnp-dlna-2.0-4=0.12.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gupnp-dlna
Source-Version: 0.12.0-2
Done: Jeremy Bicha 

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated gupnp-dlna 
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, 01 Feb 2022 08:09:12 -0500
Source: gupnp-dlna
Built-For-Profiles: noudeb
Architecture: source
Version: 0.12.0-2
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Closes: 1004736
Changes:
 gupnp-dlna (0.12.0-2) experimental; urgency=medium
 .
   * Add missing Breaks/Replaces (Closes: #1004736)
Checksums-Sha1:
 7b61a1b1f905af14d1c81a6a04995415ba273045 2477 gupnp-dlna_0.12.0-2.dsc
 7dc7bb415d1c9d38ec6484a882c3abce6cfcc872 6668 gupnp-dlna_0.12.0-2.debian.tar.xz
 294cbe7175aa17ebc79b48a7eef2c4f60f304fbb 7960 
gupnp-dlna_0.12.0-2_source.buildinfo
Checksums-Sha256:
 796a1aea5ac6bb69adc44922df2bc6465f7287aa6cf13740a9161ca3cd6ed21f 2477 
gupnp-dlna_0.12.0-2.dsc
 a220281a97831df6a15bbf0ca8594ec77a707ff5ed4dfe00834955e40e873daf 6668 
gupnp-dlna_0.12.0-2.debian.tar.xz
 66aea8e6e49779e34062b0bdd920cd67088dcaebdb4afd3fe1f1b9097809eeb2 7960 
gupnp-dlna_0.12.0-2_source.buildinfo
Files:
 166b63d299facd5f58d53f632d1100d4 2477 libs optional gupnp-dlna_0.12.0-2.dsc
 ff08b967ecd0e4a5cd43b7875a524603 6668 libs 

Bug#1004735: marked as done (libgupnp-av-1.0-3: missing Breaks+Replaces: libgupnp-av-1.0-2 (<< 0.14))

[Debian Bug Tracking System]

Your message dated Tue, 01 Feb 2022 13:18:44 +
with message-id 
and subject line Bug#1004735: fixed in gupnp-av 0.14.0-2
has caused the Debian Bug report #1004735,
regarding libgupnp-av-1.0-3: missing Breaks+Replaces: libgupnp-av-1.0-2 (<< 
0.14)
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.)


-- 
1004735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004735
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgupnp-av-1.0-3
Version: 0.14.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid 'installed while installing the package from 'experimental'.

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

  Preparing to unpack .../libgupnp-av-1.0-3_0.14.0-1_amd64.deb ...
  Unpacking libgupnp-av-1.0-3 (0.14.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgupnp-av-1.0-3_0.14.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/gupnp-av/av.xsd', which is also in package 
libgupnp-av-1.0-2 0.12.11-3
  Errors were encountered while processing:
   /var/cache/apt/archives/libgupnp-av-1.0-3_0.14.0-1_amd64.deb

The following files are part of both packages:

usr/share/gupnp-av/av.xsd
usr/share/gupnp-av/didl-lite-v2.xsd
usr/share/gupnp-av/simpledc20021212.xsd
usr/share/gupnp-av/upnp.xsd
usr/share/gupnp-av/xml.xsd

  Preparing to unpack .../libgupnp-dlna-2.0-4_0.12.0-1_amd64.deb ...
  Unpacking libgupnp-dlna-2.0-4 (0.12.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgupnp-dlna-2.0-4_0.12.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/gupnp-dlna/libgstreamer.so', 
which is also in package libgupnp-dlna-2.0-3 0.10.5-4
  Errors were encountered while processing:
   /var/cache/apt/archives/libgupnp-dlna-2.0-4_0.12.0-1_amd64.deb


cheers,

Andreas


libgupnp-av-1.0-2=0.12.11-3_libgupnp-av-1.0-3=0.14.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gupnp-av
Source-Version: 0.14.0-2
Done: Jeremy Bicha 

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated gupnp-av 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, 01 Feb 2022 08:05:40 -0500
Source: gupnp-av
Built-For-Profiles: noudeb
Architecture: source
Version: 0.14.0-2
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Closes: 1004735
Changes:
 gupnp-av (0.14.0-2) experimental; urgency=medium
 .
   * Add missing Breaks/Replaces (Closes: #1004735)
Checksums-Sha1:
 44d1a2710a34de88639040d616ee88be7d223aac 2303 gupnp-av_0.14.0-2.dsc
 487610b35e3b61baebcf37d6091aa3369a0fd137 7632 gupnp-av_0.14.0-2.debian.tar.xz
 28666d4a157621ad0e79fb5521494e3d7c9bb355 7952 
gupnp-av_0.14.0-2_source.buildinfo
Checksums-Sha256:
 5127735ab35eedee0716ed481f7e3863fdc1cc5b549e0b035c6356a994820b42 2303 
gupnp-av_0.14.0-2.dsc
 d7ff0e996ffe3ff3bdb59f473ed7138f9c450fecfa4911d9984192d141f50e8e 7632 
gupnp-av_0.14.0-2.debian.tar.xz
 08b2046d4d9a1300082c4c5f20ed1f07685e2652805dcb3a3ba1686544b3af67 7952 
gupnp-av_0.14.0-2_source.buildinfo
Files:
 ed97f03a184244c045214d9635fbff6a 2303 libs optional gupnp-av_0.14.0-2.dsc
 aec0ae98cddb1226b226e1f65df50cd7 7632 libs optional 
gupnp-av_0.14.0-2.debian.tar.xz
 3b228c6d20c2520b0758cfb57258 7952 libs optional 
gupnp-av_0.14.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmH5MEgACgkQ5mx3Wuv+
bH3fdA/+KwT1o5r2YsP0jPr1e6oXpN8u8fzcXK5+t6RU9K7OOYP4xnys/B+PqT4l

Processed: Bug#1004736 marked as pending in gupnp-dlna

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1004736 [libgupnp-dlna-2.0-4] libgupnp-dlna-2.0-4: missing 
Breaks+Replaces: libgupnp-dlna-2.0-3 (<< 0.12)
Added tag(s) pending.

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

Bug#1004736: marked as pending in gupnp-dlna

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #1004736 in gupnp-dlna reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/gupnp-dlna/-/commit/f10a1fc4e8405e7af6bb55aac38bcf5c658c2314


Add missing Breaks/Replaces

Closes: #1004736


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1004736

Bug#1004735: marked as pending in gupnp-av

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #1004735 in gupnp-av reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/gupnp-av/-/commit/6a682c7c6a306ea519edac4716c46c8438e476c4


Add missing Breaks/Replaces

Closes: #1004735


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1004735

Processed: Bug#1004735 marked as pending in gupnp-av

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1004735 [libgupnp-av-1.0-3] libgupnp-av-1.0-3: missing Breaks+Replaces: 
libgupnp-av-1.0-2 (<< 0.14)
Added tag(s) pending.

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

Processed: Re: Bug#1004540: node-graphql build failure with current babel (passed with an older babel)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1004540 [node-babel7] node-graphql build failure with current babel 
(passed with an older babel)
Severity set to 'important' from 'grave'

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

Bug#1004540: node-graphql build failure with current babel (passed with an older babel)

[Yadd]

Control: severity -1 important

On 01/02/2022 13:56, Yadd wrote:

On 01/02/2022 13:12, Pirate Praveen wrote:

Control: severity -1 grave

On ഞാ, ജനു 30 2022 at 02:48:39 വൈകു +0530 +0530, Pirate Praveen 
 wrote:


Error: Cannot find module './resources/add-extension-to-import-paths'



This is caused by this patch to load modules from system,
https://salsa.debian.org/js-team/node-babel/-/blob/master/debian/patches/load-plugins-from-system-libraries.diff 



This breaks plugins specified as relative paths.


Hi,

fixed in 7.16.12+~cs214.260.189-2, I fixed also your package 
(auto_install + test)


Cheers,
Yadd


Note: package isn't totally broken as it is able to rebuild itself, so 
changing severity to important from grave (only partially broken)

Bug#1004540: marked as pending in node-babel

[Yadd]

Control: tag -1 pending

Hello,

Bug #1004540 in node-babel reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/js-team/node-babel/-/commit/de2e3ed00f1f113a1b9dea4114c962d454cd5369


Fix load-plugins-from-system-libraries patch

Closes: #1004540


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1004540

Processed: Bug#1004540 marked as pending in node-babel

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1004540 [node-babel7] node-graphql build failure with current babel 
(passed with an older babel)
Added tag(s) pending.

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

Bug#1004540: [Pkg-javascript-devel] Bug#1004540: Bug#1004540: node-graphql build failure with current babel (passed with an older babel)

[Yadd]

On 01/02/2022 13:12, Pirate Praveen wrote:

Control: severity -1 grave

On ഞാ, ജനു 30 2022 at 02:48:39 വൈകു +0530 +0530, Pirate Praveen 
 wrote:


Error: Cannot find module './resources/add-extension-to-import-paths'



This is caused by this patch to load modules from system,
https://salsa.debian.org/js-team/node-babel/-/blob/master/debian/patches/load-plugins-from-system-libraries.diff 



This breaks plugins specified as relative paths.


Hi,

fixed in 7.16.12+~cs214.260.189-2, I fixed also your package 
(auto_install + test)


Cheers,
Yadd

Bug#1004736: libgupnp-dlna-2.0-4: missing Breaks+Replaces: libgupnp-dlna-2.0-3 (<< 0.12)

[Andreas Beckmann]

Package: libgupnp-dlna-2.0-4
Version: 0.12.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid 'installed while installing the package from 'experimental'.

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

  Preparing to unpack .../libgupnp-dlna-2.0-4_0.12.0-1_amd64.deb ...
  Unpacking libgupnp-dlna-2.0-4 (0.12.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgupnp-dlna-2.0-4_0.12.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/gupnp-dlna/libgstreamer.so', 
which is also in package libgupnp-dlna-2.0-3 0.10.5-4
  Errors were encountered while processing:
   /var/cache/apt/archives/libgupnp-dlna-2.0-4_0.12.0-1_amd64.deb

The following files are shipped by both packages:

usr/lib/x86_64-linux-gnu/gupnp-dlna/libgstreamer.so
usr/share/gupnp-dlna-2.0/dlna-profiles/aac.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/ac3.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/amr.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/avc.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/common.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/dlna-profiles.rng
usr/share/gupnp-dlna-2.0/dlna-profiles/jpeg.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/lpcm.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/mp3.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/mpeg-common.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/mpeg-ps.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/mpeg-ts.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/mpeg1.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/mpeg4.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/png.xml
usr/share/gupnp-dlna-2.0/dlna-profiles/wma.xml


cheers,

Andreas


libgupnp-dlna-2.0-3=0.10.5-4_libgupnp-dlna-2.0-4=0.12.0-1.log.gz
Description: application/gzip

Bug#1004735: libgupnp-av-1.0-3: missing Breaks+Replaces: libgupnp-av-1.0-2 (<< 0.14)

[Andreas Beckmann]

Package: libgupnp-av-1.0-3
Version: 0.14.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid 'installed while installing the package from 'experimental'.

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

  Preparing to unpack .../libgupnp-av-1.0-3_0.14.0-1_amd64.deb ...
  Unpacking libgupnp-av-1.0-3 (0.14.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgupnp-av-1.0-3_0.14.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/gupnp-av/av.xsd', which is also in package 
libgupnp-av-1.0-2 0.12.11-3
  Errors were encountered while processing:
   /var/cache/apt/archives/libgupnp-av-1.0-3_0.14.0-1_amd64.deb

The following files are part of both packages:

usr/share/gupnp-av/av.xsd
usr/share/gupnp-av/didl-lite-v2.xsd
usr/share/gupnp-av/simpledc20021212.xsd
usr/share/gupnp-av/upnp.xsd
usr/share/gupnp-av/xml.xsd

  Preparing to unpack .../libgupnp-dlna-2.0-4_0.12.0-1_amd64.deb ...
  Unpacking libgupnp-dlna-2.0-4 (0.12.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgupnp-dlna-2.0-4_0.12.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/gupnp-dlna/libgstreamer.so', 
which is also in package libgupnp-dlna-2.0-3 0.10.5-4
  Errors were encountered while processing:
   /var/cache/apt/archives/libgupnp-dlna-2.0-4_0.12.0-1_amd64.deb


cheers,

Andreas


libgupnp-av-1.0-2=0.12.11-3_libgupnp-av-1.0-3=0.14.0-1.log.gz
Description: application/gzip

Processed: Re: [Pkg-javascript-devel] Bug#1004540: node-graphql build failure with current babel (passed with an older babel)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #1004540 [node-babel7] node-graphql build failure with current babel 
(passed with an older babel)
Severity set to 'grave' from 'normal'

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

Bug#1004703: marked as done (ruby-pygments.rb: autopkgtest regression: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 01 Feb 2022 12:06:44 +
with message-id 
and subject line Bug#1004703: fixed in ruby-pygments.rb 2.3.0+ds-2
has caused the Debian Bug report #1004703,
regarding ruby-pygments.rb: autopkgtest regression: No such file or directory
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.)


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

Source: ruby-pygments.rb
Version: 2.3.0+ds-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of ruby-pygments.rb the autopkgtest of 
ruby-pygments.rb fails in testing when that autopkgtest is run with the 
binary packages of ruby-pygments.rb from unstable. It passes when run 
with only packages from testing. It fails in the same way in a pure 
unstable environment, so it's not version skew. In tabular form:


   passfail
ruby-pygments.rb   from testing2.3.0+ds-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=ruby-pygments.rb

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-pygments.rb/18819910/log.gz


┌──┐
│ Checking Rubygems dependency resolution on ruby2.7 
   │

└──┘

GEM_PATH= ruby2.7 -e gem\ \"pygments.rb\"

┌──┐
│ Run tests for ruby2.7 from debian/ruby-tests.rake 
   │

└──┘

mv lib ./.gem2deb.lib
RUBYLIB=. GEM_PATH= ruby2.7 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.7 -w -I"test" 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
"test/test_pygments.rb" -v
/tmp/autopkgtest-lxc.9r2fsd4_/downtmp/build.ktY/src/test/test_pygments.rb:13:in 
`read': No such file or directory @ rb_sysopen - 
/tmp/autopkgtest-lxc.9r2fsd4_/downtmp/build.ktY/src/test/../lib/pygments/mentos.py 
(Errno::ENOENT)
	from 
/tmp/autopkgtest-lxc.9r2fsd4_/downtmp/build.ktY/src/test/test_pygments.rb:13:in 
`'
	from 
/tmp/autopkgtest-lxc.9r2fsd4_/downtmp/build.ktY/src/test/test_pygments.rb:10:in 
`'
	from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in 
`require'
	from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in 
`require'
	from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in 
`block in '
	from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in 
`select'
	from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in 
`'

rake aborted!
Command failed with status (1): [ruby -w -I"test" 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
"test/test_pygments.rb" -v]
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in 
`'

Tasks: TOP => default
(See full trace by running task with --trace)
mv ./.gem2deb.lib lib
autopkgtest [01:10:58]: test gem2deb-test-runner



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ruby-pygments.rb
Source-Version: 2.3.0+ds-2
Done: Mattia Rizzolo 

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated ruby-pygments.rb 
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, 01 

Bug#1004614: marked as done (odpic: fails to clean after successful build: rm: cannot remove './debian/doctrees': Is a directory)

[Debian Bug Tracking System]

Your message dated Tue, 01 Feb 2022 11:19:20 +
with message-id 
and subject line Bug#1004614: fixed in odpic 4.3.0-3
has caused the Debian Bug report #1004614,
regarding odpic: fails to clean after successful build: rm: cannot remove 
'./debian/doctrees': Is a directory
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.)


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

Hi,

odpic fails to clean after a successful build:

 debian/rules clean
dh clean --with sphinxdoc
   dh_auto_clean
make -j3 clean
make[1]: Entering directory '/build/odpic-4.3.0'
rm -rf build lib
make[1]: Leaving directory '/build/odpic-4.3.0'
   dh_clean
rm -f debian/debhelper-build-stamp
rm -rf debian/.debhelper/
rm -f debian/libodpic4.debhelper.log debian/odpic-dev.debhelper.log 
debian/odpic-doc.debhelper.log
rm -f -- debian/odpic-dev.substvars debian/libodpic4.substvars 
debian/odpic-doc.substvars ./debian/doctrees debian/files
rm: cannot remove './debian/doctrees': Is a directory
dh_clean: error: rm -f -- debian/odpic-dev.substvars debian/libodpic4.substvars 
debian/odpic-doc.substvars ./debian/doctrees debian/files returned exit code 1
make: *** [debian/rules:14: clean] Error 25
dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2

Without checking the package, I'd guess you are missing a trailing / (to denote
a directory) on the debian/doctrees entry in debian/clean.


Andreas


odpic_4.3.0-2_twice.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: odpic
Source-Version: 4.3.0-3
Done: Joseph Nahmias 

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

Debian distribution maintenance software
pp.
Joseph Nahmias  (supplier of updated odpic 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, 01 Feb 2022 06:02:48 -0500
Source: odpic
Architecture: source
Version: 4.3.0-3
Distribution: unstable
Urgency: medium
Maintainer: Joseph Nahmias 
Changed-By: Joseph Nahmias 
Closes: 1004614
Changes:
 odpic (4.3.0-3) unstable; urgency=medium
 .
   * [a773491] fix Vcs URLs
   * [1e1bc40] clean doctrees as a dir.
 Thanks to Andreas Beckmann  (Closes: 1004614)
   * [c9b1882] drop libaio1 from Dep to Rec.
 This is just a convenience dep as libodpic doesn't directly use libaio1,
 but it is needed by the (unpackagable) Oracle Instant Client -- which is
 needed by libodpic.
   * [980534d] add more info about Oracle client installation to README.Debian
Checksums-Sha1:
 ee3ad0b4adf7e951f0407f4418aeff07ae606bfb 1946 odpic_4.3.0-3.dsc
 0cd9437e96a9d7c7d50ed5f29dd0aecf6dcaba01 9112 odpic_4.3.0-3.debian.tar.xz
 6fa8ee7ff54d7a24bf30686bbb0dbc21ee52afea 8033 odpic_4.3.0-3_amd64.buildinfo
Checksums-Sha256:
 2ac37cb533feead366ef57ee7697bb8e047de3c8246431a0f5d60a0e68697049 1946 
odpic_4.3.0-3.dsc
 2277db14e652283d92db5e1fb59fa520fc717d431e27ec16fdd2e77a2d56b38d 9112 
odpic_4.3.0-3.debian.tar.xz
 36c0cadefa4d7f7c7b2bd83635f52e96dbd85707848e4b5911613b7dbaca64a8 8033 
odpic_4.3.0-3_amd64.buildinfo
Files:
 8b396bd955b5a0b030cb37d637af1936 1946 contrib/libs optional odpic_4.3.0-3.dsc
 871943605e8d807be4d75b59675abe8d 9112 contrib/libs optional 
odpic_4.3.0-3.debian.tar.xz
 56dd42f692099b8866c0e64b954d0b5d 8033 contrib/libs optional 
odpic_4.3.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEcxc7CTsDz7hRCK0UsRvZGQeaO5gFAmH5FG0ACgkQsRvZGQea
O5gYuhAAlaDSjUzPAWoFPY614utuTRH8TH2zhtFP5LS8lNL3wg457Q/h88fQ1Jxj
TplZzQVH0lrAx5apZH8GoX5okg/tKdHL93JdlzOct9in9A2nQMfAoG+KjafdPXiG
HRFX795L9lqI8iKXEFAF9LVB2BO6zsdXd9klGQ/ypihUYGOH7PwhEqt6l3A+m0hT
jWdv3JHc0Pb/xujfXtgLNWwVVjl7EVQFHX737xNVe6AEaOcpGUfJkM+5KMA64Q+I
WCSuRHFHfq5UI8nSUv+IxoaLLHzwrW6RzeGzMVoD02bD7CeZy4NuJqdKZP1dMj3q
eyEvTGJRHPDba2LK5RPR9Xayye3y8XOUQT6bNXf18Yy7KoszpOvQEP2ukW4Hj1MG

Bug#1004693: vfs_fruit module is in the binary package samba-vfs-modules

[Jonathan Dowland]

From what I can determine, the affected module is distributed in the
samba-vfs-modules package, so any worried users trying to figure out
whether they are vulnerable or not, check whether this package is
installed: if not, you likely aren't.


--
Please do not CC me for listmail.

  Jonathan Dowland
✎j...@debian.org
   https://jmtd.net

Processed: Re: Bug#1004671: incompatible with current biblatex version

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/plk/biblatex/issues/1202
Bug #1004671 [biber] incompatible with current biblatex version
Set Bug forwarded-to-address to 'https://github.com/plk/biblatex/issues/1202'.

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

Bug#1004671: incompatible with current biblatex version

[Hilmar Preuße]

Control: forwarded -1 https://github.com/plk/biblatex/issues/1202

Am 31.01.2022 um 15:53 teilte Ryan Kavanagh mit:

Hi,


I'm not sure if this should instead be filed against
texlive-bibtex-extra, but the current version of biber is incompatible
with the biblatex package currently in Debian unstable. This effectively
renders biber useless and makes it impossible to compile documents that
use biblatex.



Yes, that was a mistake to upload a new biber. Sorry!

The issue will be solved by a new biblatex. I asked upstream 
(biber/biblatex) when there will be an upload to CTAN [1], the answer 
was "just waiting for a missing biber build for FreeBSD.". Once this is 
done I'll package the new biblatex to solve the issue. I mark this bug 
as forwarded although it is not really an upstream issue.


Hope this is acceptable for now.

Hilmar

[1] https://github.com/plk/biblatex/issues/1202
--
sigfault



OpenPGP_signature
Description: OpenPGP digital signature

Processed: severity of 1000958 is normal

[Debian Bug Tracking System]

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

> severity 1000958 normal
Bug #1000958 [exim4-daemon-light] /etc/aliases dosn't work since bullseye
Severity set to 'normal' from 'critical'
> thanks
Stopping processing here.

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

Bug#1000958: /etc/aliases dosn't work since bullseye

[Marc Haber]

tags #1000958 
thanks

On Thu, Dec 02, 2021 at 09:21:23AM +0100, Marc Haber wrote:
> It will probably be easier to send that un-obfuscated, you can do that
> in private if you prefer that.

For the protocol: We had a short e-mail exchange, I had to ask for
additional debug input and then the conversation stalled. Since no other
bug report about this misbehavior came in and noone else commented here,
I suggest that this is most probably a local issue and thus not an RC
bug. Lowering severity.

Feel free to return to the conversation, I'm still eager to help. This
bug report will be closed by end of February 2022 if I don't see more
evidence about this being a problem with exim or the packaging.

Greetings
Marc

Processed (with 1 error): Re: Bug#949519: sudo-ldap: Fails to connect to LDAP : "ldap_sasl_bind_s(): Can't contact LDAP server"

[Debian Bug Tracking System]

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

> packsge sudo-ldap
Unknown command or malformed arguments to command.
> severity #949519 normal
Bug #949519 [sudo-ldap] sudo-ldap: Fails to connect to LDAP : 
"ldap_sasl_bind_s(): Can't contact LDAP server"
Severity set to 'normal' from 'grave'
> outlook #949519 close after 2022-02-28
Outlook recorded from message bug 949519 message 
> thanks
Stopping processing here.

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

Bug#949519: sudo-ldap: Fails to connect to LDAP : "ldap_sasl_bind_s(): Can't contact LDAP server"

[Marc Haber]

packsge sudo-ldap
severity #949519 normal
outlook #949519 close after 2022-02-28
thanks

Lowering severity as this seems to affect just a few users.

Greetings
Marc

Bug#994178: libnginx-mod-http-lua - init_worker_by_lua_block segfaults

[Anton Tolchanov]

> The nginx source bundles the http-lua module in a version incompatible
> with nginx 1.18.  It segfaults immediately with a minimal config if a
> "init_worker_by_lua_block" block is defined.  (I haven't looked much
> further.)

I have submitted a merge request to upgrade lua-nginx-module version to 0.10.15:
https://salsa.debian.org/nginx-team/nginx/-/merge_requests/15

After updating to 0.10.15 I am no longer seeing nginx segfault when 
init_worker_by_lua_block is used.

A similar update is being discussed in the corresponding Ubuntu bug:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1893753

Regards,
Anton