Bug#1002113: gr-gsm: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create'

[Adrian Bunk]

On Sat, Jan 29, 2022 at 02:33:25PM +0100, Petter Reinholdtsen wrote:
> [Lucas Nussbaum]
> > Relevant part (hopefully):
> > > /usr/bin/ld: CMakeFiles/cmTC_af046.dir/src.c.o: in function `main':
> > > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference 
> > > to `pthread_create'
> > > /usr/bin/ld: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:12: 
> > > undefined reference to `pthread_detach'
> > > /usr/bin/ld: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:13: 
> > > undefined reference to `pthread_cancel'
> > > /usr/bin/ld: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:14: 
> > > undefined reference to `pthread_join'
> > > collect2: error: ld returned 1 exit status
> 
> Look like something, somewhere, is missing -lpthread to find the
> required functions.  Anyone got a patch to fix it?

Blindly dumping the end of the build log is often not helpful.

The actual problem is:

...
CMake Error at swig/CMakeLists.txt:37 (include):
  include could not find requested file:

GrSwig


CMake Error at swig/CMakeLists.txt:51 (GR_SWIG_MAKE):
  Unknown CMake command "GR_SWIG_MAKE".


-- Configuring incomplete, errors occurred!
...


AFAIK this is due to a change in gnuradio 3.9.


> Happy hacking
> Petter Reinholdtsen

cu
Adrian

Processed: Re: Bug#1004900: zim-tools: FTBFS on slow buildds

[Debian Bug Tracking System]

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

> forwarded 1004900 https://github.com/openzim/zim-tools/issues/287
Bug #1004900 [src:zim-tools] zim-tools: FTBFS on slow buildds
Set Bug forwarded-to-address to 
'https://github.com/openzim/zim-tools/issues/287'.
> thanks
Stopping processing here.

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

Bug#1004330: makes the package useless with PHP 8

[Axel Beckert]

Hi Francesco,

Francesco Potortì wrote:
> I hope the package gets upgraded soon, because dokuwiki simply
> stopped working with PHP 8

I have a more or less working package of the most recent upstream
release plus one or two patches at
https://salsa.debian.org/abe/dokuwiki

It runs in production on https://swissmk.ch/

Actually I'd be happy if someone else could try it out as well as
Dokuwiki is a rather huge chunk of code and I'm not sure if I got
everything right.

I intend to do an NMU (due to no reaction of the maintainer on either
RC bug for over a week), but for that the package still needs a bit
more fine-tuning (like handling the other RC bug which actually no
more is one after the recent TC decision on that topic).

I also still have some strange behaviour with regards to mail
notifications (notifications for changes which either never happaned
or which happened years ago — at least they're not visible in the web
interface at the time the mails were sent) where I'm not sure what
part of the upgrade caused them.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#994186: marked as done (libvkd3d1 uninstallable in experimental)

[Debian Bug Tracking System]

Your message dated Fri, 04 Feb 2022 01:48:37 +
with message-id 
and subject line Bug#994186: fixed in vkd3d 1.2-7
has caused the Debian Bug report #994186,
regarding libvkd3d1 uninstallable in experimental
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.)


-- 
994186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994186
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvkd3d1
Severity: normal
Version: 1.2-6

Vesion 1.2-6 is currently uninstallable on debian experimental due to
the mesa-vulkan-drivers (< 21) dependency.

I assume this should have been >=.

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

Kernel: Linux 5.13.0-trunk-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libvkd3d1 depends on:
ii  libc62.32-2
pn  libvkd3d-shader1 
ii  libvulkan1   1.2.189.0-2
ii  mesa-vulkan-drivers  21.2.1-2

libvkd3d1 recommends no packages.

libvkd3d1 suggests no packages.
--- End Message ---
--- Begin Message ---
Source: vkd3d
Source-Version: 1.2-7
Done: Michael Gilbert 

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated vkd3d 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: Fri, 04 Feb 2022 01:16:25 +
Source: vkd3d
Architecture: source
Version: 1.2-7
Distribution: experimental
Urgency: medium
Maintainer: Debian Wine Party 
Changed-By: Michael Gilbert 
Closes: 993570 994186
Changes:
 vkd3d (1.2-7) experimental; urgency=medium
 .
   * Update standards to 4.6.0.
   * Fix stringop-overread warnings.
   * Skip failing tests when using nvidia devices.
   * Skip failing tests when using llvmpipe from mesa 21 (closes: #994186).
   * Fix file conflict between libvkd3d-doc and libvkd3d-dev (closes: #993570).
Checksums-Sha1:
 619bc530ec23966965b31a30f8eb0f546fe020bf 3331 vkd3d_1.2-7.dsc
 76d073289aa2943b97c3b4b7c854a4356148 11596 vkd3d_1.2-7.debian.tar.xz
 df58e80d4bbea622455022960497f69eb41250bb 7368 vkd3d_1.2-7_source.buildinfo
Checksums-Sha256:
 2a22f10bc0d2450512535725dd71d6e8c9c26a927f739336684181903ad28252 3331 
vkd3d_1.2-7.dsc
 375928a797d294ca07ed29d508e623a26b7dcffe20ed2cd68a7bc685b4702e00 11596 
vkd3d_1.2-7.debian.tar.xz
 53ef1fc5e7e51fc8f4191d4161baa93d5e7120b4ff2127406881305c775f5e60 7368 
vkd3d_1.2-7_source.buildinfo
Files:
 7462b7e8c4dfa6efdcf182820e68c6ac 3331 libs optional vkd3d_1.2-7.dsc
 faeaf399364eca951689741dd0f42a53 11596 libs optional vkd3d_1.2-7.debian.tar.xz
 ed3aa3456ac5faa94e6e752d0ace1eee 7368 libs optional 
vkd3d_1.2-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQQzBAEBCgAdFiEEIwTlZiOEpzUxIyp4mD40ZYkUaygFAmH8f/cACgkQmD40ZYkU
ayhBXR//ZRE0o/LRjxFPGCKKD7YwdMqsZddAHcfzRlJAZMJ5EbhQxFDBAoMikrUV
jcwcGabxboMhqNuw5ABVHJ5BbUShHMXEXTYY30N53UcWzGibCfqq46NsW6NY2Hpn
BO788xlXdYuLZNwcdNIjXpvBC1idrr7Qbrt8VSJpFOKz93kQJu+hfcAhcQih/xkU
zcO/oT/jOewmvDyUFRjoumqe0jus7eYpQpcqpG9YZiHOeO5XiogSNRtPZYd+oKza
K0/fZvyyFeDKCbXhfk7Hwhmk9tSyeFnJStYnxwqHt69o5JVtpo9dm5ykKAUS/Djr
unzrOIq08RtbAlqhe2tykBB5cxMmUOqTNc3Yf28TJk8/NL3BJ0FhG9T/ojLShnk3
Lw+etatLpMGQJo+DyWo7/aiI/EfsHMrQ+HvwVC8NdKsx9ZUSRV+Sv8FpV5i5kvDV
hNBtMLwRN3wJBZL9yfR8DiU4MnuIqcC8Uxo1fiWGVjy7j/0T4AWU5MgB5NxOZA/R
OicI5o2AILafnrGznbA5S++GgZJAfZ+dw1IxY9sKUkfVzcpJkU3uwFxUcZUMQazH
3v9oUCIn0NE774Kt73dlMGRz3Cdw1slKkw40FkGu/N5/s93nwIs3I7aiRirGE6gS
84o0Z2VVJYzvHVXNoezGOWiX8l6u7BnlO7HrOyHSEIjaUW8n5oyhUgajfi0wwgA8
3F7FwbyFGWJ80BHsxyKqsjV/rIVX0aanI3Mcr9RwWjATMIx7ODl7KY1+Vk8cUur+
hf3e5frGcXSfkrvzgZG7XpKiOmxns0D24Os9BRqHqljk/lDanxz+OklkQ7rvf2fw
bI0ul0za30rKC3u7cduC64Xz1fFP4AmF3YUp+kO10fp1lOk9JNTAgSenbtuHPC21
TX0Gs1pHONE1byp62VVWlZc64lmKjrs4Nm53+KOAemW3QKf7KgmeERkZmlqB2A5s
wmpSO0GpJmwsp+4Nfc4FMUK4inLhvY4BMTO7CjrXw5RjZS0xOKnODRIwYkKUPaIt

Bug#1004847: marked as done (nvidia-graphics-drivers: CVE-2022-21813, CVE-2022-21814)

[Debian Bug Tracking System]

Your message dated Fri, 04 Feb 2022 00:50:17 +
with message-id 
and subject line Bug#1004847: fixed in nvidia-graphics-drivers-tesla-470 
470.103.01-1
has caused the Debian Bug report #1004847,
regarding nvidia-graphics-drivers: CVE-2022-21813, CVE-2022-21814
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.)


-- 
1004847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004847
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
Control: clone -1 -2 -3 -4 -5 -6 -7
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-21813, 
CVE-2022-21814
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-21813, 
CVE-2022-21814
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-21813, 
CVE-2022-21814
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-21813, 
CVE-2022-21814
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-21813, 
CVE-2022-21814
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-21813, 
CVE-2022-21814
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 450.51-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1

https://nvidia.custhelp.com/app/answers/detail/a_id/5312

CVE‑2022‑21813  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel driver, where improper handling of
insufficient permissions or privileges may allow an unprivileged
local user limited write access to protected memory, which can
lead to denial of service.

CVE‑2022‑21814  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel driver package, where improper
handling of insufficient permissions or privileges may allow an
unprivileged local user limited write access to protected memory,
which can lead to denial of service.

Driver Branch   CVE IDs Addressed
R510, R470  CVE-2022-21813, CVE-2022-21814

Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla-470
Source-Version: 470.103.01-1
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers-tesla-470, 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.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-tesla-470 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: Fri, 04 Feb 2022 01:11:13 +0100
Source: nvidia-graphics-drivers-tesla-470
Architecture: source
Version: 470.103.01-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 999670 1004847 1004853
Changes:
 nvidia-graphics-drivers-tesla-470 (470.103.01-1) unstable; urgency=medium
 .
   * Rebuild as Tesla 470 driver.  (Closes: #1004853)
 .
 nvidia-graphics-drivers (470.103.01-1) unstable; urgency=medium
 .
   * New upstream production branch release 470.103.01 (2022-01-31).
 * Fixed CVE‑2022‑21813, CVE‑2022‑21814.  (Closes: #1004847)
   https://nvidia.custhelp.com/app/answers/detail/a_id/5312
 - Added support for the following GPUs: NVIDIA GeForce MX550,
   NVIDIA GeForce MX570, NVIDIA GeForce RTX 2050.
 .
   [ Andreas Beckmann ]
   * Refresh patches.
   * Update nv-readme.ids.
 .
 nvidia-graphics-drivers (470.94-1) unstable; urgency=medium
 .
   * New upstream production branch release 470.94 (2021-12-13).
 - Added support for the following GPU: NVIDIA PG509-210.
 - Worked around an issue that prevented some games from 

Bug#1004853: marked as done (nvidia-graphics-drivers-tesla-470: CVE-2022-21813, CVE-2022-21814)

[Debian Bug Tracking System]

Your message dated Fri, 04 Feb 2022 00:50:17 +
with message-id 
and subject line Bug#1004853: fixed in nvidia-graphics-drivers-tesla-470 
470.103.01-1
has caused the Debian Bug report #1004853,
regarding nvidia-graphics-drivers-tesla-470: CVE-2022-21813, CVE-2022-21814
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.)


-- 
1004853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
Control: clone -1 -2 -3 -4 -5 -6 -7
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-21813, 
CVE-2022-21814
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-21813, 
CVE-2022-21814
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-21813, 
CVE-2022-21814
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-21813, 
CVE-2022-21814
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-21813, 
CVE-2022-21814
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-21813, 
CVE-2022-21814
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 450.51-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1

https://nvidia.custhelp.com/app/answers/detail/a_id/5312

CVE‑2022‑21813  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel driver, where improper handling of
insufficient permissions or privileges may allow an unprivileged
local user limited write access to protected memory, which can
lead to denial of service.

CVE‑2022‑21814  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel driver package, where improper
handling of insufficient permissions or privileges may allow an
unprivileged local user limited write access to protected memory,
which can lead to denial of service.

Driver Branch   CVE IDs Addressed
R510, R470  CVE-2022-21813, CVE-2022-21814

Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla-470
Source-Version: 470.103.01-1
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers-tesla-470, 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.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-tesla-470 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: Fri, 04 Feb 2022 01:11:13 +0100
Source: nvidia-graphics-drivers-tesla-470
Architecture: source
Version: 470.103.01-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 999670 1004847 1004853
Changes:
 nvidia-graphics-drivers-tesla-470 (470.103.01-1) unstable; urgency=medium
 .
   * Rebuild as Tesla 470 driver.  (Closes: #1004853)
 .
 nvidia-graphics-drivers (470.103.01-1) unstable; urgency=medium
 .
   * New upstream production branch release 470.103.01 (2022-01-31).
 * Fixed CVE‑2022‑21813, CVE‑2022‑21814.  (Closes: #1004847)
   https://nvidia.custhelp.com/app/answers/detail/a_id/5312
 - Added support for the following GPUs: NVIDIA GeForce MX550,
   NVIDIA GeForce MX570, NVIDIA GeForce RTX 2050.
 .
   [ Andreas Beckmann ]
   * Refresh patches.
   * Update nv-readme.ids.
 .
 nvidia-graphics-drivers (470.94-1) unstable; urgency=medium
 .
   * New upstream production branch release 470.94 (2021-12-13).
 - Added support for the following GPU: NVIDIA PG509-210.
 - Worked around an issue that prevented some 

Processed: tagging 1002173

[Debian Bug Tracking System]

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

> tags 1002173 + fixed-upstream
Bug #1002173 [src:pympler] pympler: FTBFS: ImportError: cannot import name 
'MutableMapping' from 'collections' 
(/usr/lib/python3.10/collections/__init__.py)
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: postfix-mta-sts-resolver: diff for NMU version 1.0.0-4.1

[Debian Bug Tracking System]

Processing control commands:

> tags 996048 + patch
Bug #996048 [postfix-mta-sts-resolver] postfix-mta-sts-resolver: autopkgtest 
doesn't handle new version of ca-certificates nicely: rehash: warning: skipping 
ca-certificates.crt,it does not contain exactly one certificate or CRL
Added tag(s) patch.
> tags 996048 + pending
Bug #996048 [postfix-mta-sts-resolver] postfix-mta-sts-resolver: autopkgtest 
doesn't handle new version of ca-certificates nicely: rehash: warning: skipping 
ca-certificates.crt,it does not contain exactly one certificate or CRL
Added tag(s) pending.

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

Bug#996048: postfix-mta-sts-resolver: diff for NMU version 1.0.0-4.1

[Adrian Bunk]

Control: tags 996048 + patch
Control: tags 996048 + pending

Dear maintainer,

I've prepared an NMU for postfix-mta-sts-resolver (versioned as 1.0.0-4.1)
and uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru postfix-mta-sts-resolver-1.0.0/debian/changelog postfix-mta-sts-resolver-1.0.0/debian/changelog
--- postfix-mta-sts-resolver-1.0.0/debian/changelog	2020-12-05 21:24:01.0 +0200
+++ postfix-mta-sts-resolver-1.0.0/debian/changelog	2022-02-04 02:21:27.0 +0200
@@ -1,3 +1,11 @@
+postfix-mta-sts-resolver (1.0.0-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/tests/control: Add allow-stderr restriction.
+(Closes: #996048)
+
+ -- Adrian Bunk   Fri, 04 Feb 2022 02:21:27 +0200
+
 postfix-mta-sts-resolver (1.0.0-4) unstable; urgency=low
 
   [ Debian Janitor ]
diff -Nru postfix-mta-sts-resolver-1.0.0/debian/tests/control postfix-mta-sts-resolver-1.0.0/debian/tests/control
--- postfix-mta-sts-resolver-1.0.0/debian/tests/control	2020-12-05 21:24:01.0 +0200
+++ postfix-mta-sts-resolver-1.0.0/debian/tests/control	2022-02-04 02:21:27.0 +0200
@@ -1,3 +1,3 @@
 Tests: run
 Depends: @, dnsmasq, nginx-extras, postfix, python3-cryptography
-Restrictions: breaks-testbed, isolation-container, needs-root
+Restrictions: breaks-testbed, isolation-container, needs-root, allow-stderr

Processed: Re: Bug#984209: libsynthesis: diff for NMU version 3.4.0.47.5+syncevolution-1.5.3-1.1

[Debian Bug Tracking System]

Processing control commands:

> forcemerge -1 1002146
Bug #984209 [src:libsynthesis] libsynthesis: ftbfs with GCC-11
Bug #1002146 [src:libsynthesis] libsynthesis: FTBFS: 
sysync_SDK/Sources/san.h:264:5: error: reference to ‘byte’ is ambiguous
Severity set to 'important' from 'serious'
Added tag(s) pending and patch.
Merged 984209 1002146

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

Bug#1004330: makes the package useless with PHP 8

[Francesco Potortì]

I hope the package gets upgraded soon, because dokuwiki simply stopped working 
with PHP 8

I used a stopgap, by looking at the Apache errors end modifying the php source 
files generating the error, but that's long and tedious.  And I cannot be sure 
that everything works...

-- 
Francesco Potortì (ricercatore)Voice:  +39.050.621.3058
ISTI - Area della ricerca CNR  Mobile: +39.348.8283.107
via G. Moruzzi 1, I-56124 Pisa Skype:  wnlabisti
(gate 20, 1st floor, room C71) Web:http://fly.isti.cnr.it

Bug#1004940: gr-iio seems to be integrated into gnuradio now

[Adrian Bunk]

Package: gr-iio
Version: 0.3-9
Severity: serious
Tags: bookworm sid

https://www.gnuradio.org/news/2022-01-17-gnuradio-v3.10.0.0-release/

- New in-tree module gr-iio

Bug#987689: marked as done (Upgrade to 2021.03)

[Debian Bug Tracking System]

Your message dated Fri, 04 Feb 2022 00:00:09 +
with message-id 
and subject line Bug#987689: fixed in onetbb 2021.5.0-1
has caused the Debian Bug report #987689,
regarding Upgrade to 2021.03
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.)


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

Severity: normal

libtbb2 is of obsolete version that dropped by numba in master branch.
--- End Message ---
--- Begin Message ---
Source: onetbb
Source-Version: 2021.5.0-1
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated onetbb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 03 Feb 2022 17:14:25 +0100
Source: onetbb
Binary: libtbb-dev libtbb-doc libtbb12 libtbb12-dbgsym
Architecture: source amd64 all
Version: 2021.5.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Andreas Tille 
Description:
 libtbb-dev - parallelism library for C++ - development files
 libtbb-doc - parallelism library for C++ - documentation
 libtbb12   - parallelism library for C++ - runtime files
Closes: 987689 997115
Changes:
 onetbb (2021.5.0-1) experimental; urgency=medium
 .
   * Team upload
 .
   [ Mo Zhou ]
   * New upstream version 2021.4.0 (Closes: #987689)
   * Source rename following upstream. The new upstream Git URL is
 https://github.com/oneapi-src/oneTBB
   * d/rules: Switch build system to cmake+ninja.
 + Remove OS detection flags for old buildsystem.
 + Update buildflags in favor of new CMake buildsystem.
 + No longer need to manually install pkg-config and cmake files.
   * d/patches: Remove patches for old build system.
 + And temporarily disable all remaining patches.
   * Bump SOVERSION to 12 and refresh symbols control file. (Closes: #997115)
   * Migrate to Sphinx for building documentation.
   * d/*.{install,docs,examples}: Reflect upstream file changes.
   * Remove unnecessary links and lintian overrides.
   * Migrate to new API for d/tests/test.cc for autopkgtest.
   * Use upstream examples for autopkgtest.
   * Upload to experimental.
 .
   [ Andreas Tille ]
   * Do not repack upstream source
   * DEP5
   * Drop uupdate from watch file
   * Standards-Version: 4.6.0 (routine-update)
   * debhelper-compat 13 (routine-update)
   * Add salsa-ci file (routine-update)
   * No need to use dh-exec
Checksums-Sha1:
 3b2b7dce56cdc43700f1f458bcdae08f33463b1e 2414 onetbb_2021.5.0-1.dsc
 71750727bd1436f4047342d0adb827c25d7bc2b0 2463218 onetbb_2021.5.0.orig.tar.gz
 1fb685bbb31299327d3240e31347bc38f9cda474 13148 onetbb_2021.5.0-1.debian.tar.xz
 4ded0fd342015dfe1862bdaa8c8f23e80df064e3 194324 libtbb-dev_2021.5.0-1_amd64.deb
 b0c012f91449faabf64ce29c946f336af954566d 1250600 libtbb-doc_2021.5.0-1_all.deb
 9fdaa1b49b9bf372bc1b9ac458b79e3fd6d5e0c5 1254324 
libtbb12-dbgsym_2021.5.0-1_amd64.deb
 12285522ec6b619852926c5eea9a53e0750dda34 115636 libtbb12_2021.5.0-1_amd64.deb
 cd8c0c7e35ce76b2620a77a0dbb7831f57f09775 11145 
onetbb_2021.5.0-1_amd64.buildinfo
Checksums-Sha256:
 52c5ea7fcf93222adef4a97363cb2997f8ab500348b7f312961997a375298a2e 2414 
onetbb_2021.5.0-1.dsc
 e5b57537c741400cf6134b428fc1689a649d7d38d9bb9c1b6d64f092ea28178a 2463218 
onetbb_2021.5.0.orig.tar.gz
 6217c74d4935d8b163fe03090f4e3f61eb1b2eebc9a5798e2181e887527cd9c9 13148 
onetbb_2021.5.0-1.debian.tar.xz
 8486e99e251715ec38317e1eb8fa15f51d672af0b72c8bb02de76e22b4692f30 194324 
libtbb-dev_2021.5.0-1_amd64.deb
 691e796bf6b5fb180003b83c8340765322f3d3883b41fa923922fe58d7b878b1 1250600 
libtbb-doc_2021.5.0-1_all.deb
 56b0102c50aea5b98ea8ea6d207a68ed834edd2cfceb072dc2efe6ffd410a08c 1254324 
libtbb12-dbgsym_2021.5.0-1_amd64.deb
 487b854dc777077164d17c6c53dccf39da7781a6ea3a270ede5e6f146f465c87 115636 
libtbb12_2021.5.0-1_amd64.deb
 56cbc07ba4f4594d4578d1287557ab6edb08c00c5c76dafd08982153442febf5 11145 

Bug#997115: marked as done (tbb: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Fri, 04 Feb 2022 00:00:09 +
with message-id 
and subject line Bug#997115: fixed in onetbb 2021.5.0-1
has caused the Debian Bug report #997115,
regarding tbb: FTBFS: dpkg-gensymbols: error: some symbols or patterns 
disappeared in the symbols file: see diff output below
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.)


-- 
997115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tbb
Version: 2020.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_compress -X*/examples/*
> make[1]: Leaving directory '/<>'
>dh_compress -Nlibtbb-doc
>dh_fixperms
>dh_missing
>dh_dwz
>dh_strip
>dh_makeshlibs
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libtbb2/DEBIAN/symbols doesn't match 
> completely debian/libtbb2.symbols.amd64
> --- debian/libtbb2.symbols.amd64 (libtbb2_2020.3-1_amd64)
> +++ dpkg-gensymbolslnBnd5 2021-10-23 07:12:29.027488689 +
> @@ -302,8 +302,8 @@
>   MallocInitializeITT@Base 2017~U7
>   _Z9parseFileILi100ELi1EEvPKcRAT0__K13parseFileItem@Base 2018~U6
>   _Z9parseFileILi100ELi2EEvPKcRAT0__K13parseFileItem@Base 2018~U6
> - _ZN11MallocMutex11scoped_lockD1Ev@Base 2020.3
> - _ZN11MallocMutex11scoped_lockD2Ev@Base 2020.3
> +#MISSING: 2020.3-1# _ZN11MallocMutex11scoped_lockD1Ev@Base 2020.3
> +#MISSING: 2020.3-1# _ZN11MallocMutex11scoped_lockD2Ev@Base 2020.3
>   _ZN3rml10pool_msizeEPNS_10MemoryPoolEPv@Base 2019~U4
>   _ZN3rml10pool_resetEPNS_10MemoryPoolE@Base 2017~U7
>   _ZN3rml11pool_createElPKNS_13MemPoolPolicyE@Base 2017~U7
> dh_makeshlibs: error: failing due to earlier errors
> make: *** [debian/rules:49: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/tbb_2020.3-1_unstable.log

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

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated onetbb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 03 Feb 2022 17:14:25 +0100
Source: onetbb
Binary: libtbb-dev libtbb-doc libtbb12 libtbb12-dbgsym
Architecture: source amd64 all
Version: 2021.5.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Andreas Tille 
Description:
 libtbb-dev - parallelism library for C++ - development files
 libtbb-doc - parallelism library for C++ - documentation
 libtbb12   - parallelism library for C++ - runtime files
Closes: 987689 997115
Changes:
 onetbb (2021.5.0-1) experimental; urgency=medium
 .
   * Team upload
 .
   [ Mo Zhou ]
   * New upstream version 2021.4.0 (Closes: #987689)
   * Source rename following upstream. The new upstream Git URL is
 https://github.com/oneapi-src/oneTBB
   * d/rules: Switch build system to cmake+ninja.
 + Remove OS detection flags for old buildsystem.
 + Update buildflags in favor of new CMake buildsystem.
 + No longer need to manually install pkg-config and cmake files.
   * d/patches: Remove patches for old build system.
 + And temporarily disable all remaining patches.
   * Bump SOVERSION to 12 and refresh symbols control file. (Closes: #997115)
   * Migrate to Sphinx for building 

Bug#965759: marked as done (opus-tools: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Thu, 03 Feb 2022 21:50:00 +
with message-id 
and subject line Bug#965759: fixed in opus-tools 0.1.10-1.1
has caused the Debian Bug report #965759,
regarding opus-tools: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


-- 
965759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opus-tools
Version: 0.1.10-1
Severity: normal
Usertags: compat-5-6-removal

Hi,

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

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

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

  * Compat 7 is the bare minimum


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

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


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


Thanks,
~Niels


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

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

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

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: opus-tools
Source-Version: 0.1.10-1.1
Done: Adrian Bunk 

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated opus-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Jan 2022 16:18:25 +0200
Source: opus-tools
Architecture: source
Version: 0.1.10-1.1
Distribution: unstable
Urgency: low
Maintainer: Ron Lee 
Changed-By: Adrian Bunk 
Closes: 965759
Changes:
 opus-tools (0.1.10-1.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * debian/compat: 5 -> 7. (Closes: #965759)
Checksums-Sha1:
 c106bd3f465cca0334db68ff06cdfcd38d74c525 1953 opus-tools_0.1.10-1.1.dsc
 11236fc825d8ea61c1c408812a6264aed2e1c41c 3114 opus-tools_0.1.10-1.1.diff.gz
Checksums-Sha256:
 e3a950f29939c9dbf5679a57c33eeb8db633fbb9ab4b9e6eedd1a33a9689a342 1953 
opus-tools_0.1.10-1.1.dsc
 414237bf0c816abe87d0321851144699c5bd5db57a87c2af6276824731031bcc 3114 
opus-tools_0.1.10-1.1.diff.gz
Files:
 45c5ac072aea9fb35de7282b280ef4c0 1953 sound optional opus-tools_0.1.10-1.1.dsc
 5bb5f279fe3daebd9141476d6a10b00c 3114 sound optional 
opus-tools_0.1.10-1.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHoHmsACgkQiNJCh6LY
mLGDmBAAvgLzNXPwX+8W5DyPxEQ/1Qp4WLzvcpUBMxo2tz+sxU64nYxGxs7mGrq7
5swR+nUAs/fvUJISC5yBe66lVIi9aAj7QVLfs0u7YAC+0uL8x5CzGzwi+fVo/6xC
yaIReBMC2sotlEsSt3AD66pd9hHbsapkYBjxBBlKjkynbbRGIey44jZcv3lCVK3s
JWksXwHNM9zvANAsZW9RyyAelum7jr3F3GJ3KGpr/pNZB+jPTBND5C8pQpAClpaJ
UkA7iPiZg3COuJZ5qq04Y6dah5qnIZ2dd4yp87K2GuHM92PqvFn/GFQJudC/1e6G
UoR47sEaXUYAiTAoTCIljqUAbiVt7g15NSvJhLhfrnH5ske3jjF12xgOUXAuQFVa
MhfLM2QV+PtCljDwFvcPsBh/yRXMru3YCurV5EVpcAtorfprxrIqtNWlzMb3+/yt
CfK4pyd7sX+VDGKS3BL0UpGcug9STbdQezwujxDwAQGQSB5hUv2HXg4AIeQZ9u4v
giKyBuiPx19PWS2OOcMBTIeqB9af0LFLdc8XbYACLr3CJ31WZSHgeve8z1zhIzKL
R17GcA6ZcdQK5F7MSo/Y7kNw7QKZPKIRFA3W/M0eSsMGxXcH7bxNjggHqhsJuYts
paXjiuqaUNidnjxh27wCv6ley766y+OVdJgqRj0u/oPMQ7pCoXM=
=bhYS
-END PGP SIGNATURE End Message ---

Bug#965538: marked as done (gcc-h8300-hms: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Thu, 03 Feb 2022 21:49:14 +
with message-id 
and subject line Bug#965538: fixed in gcc-h8300-hms 1:3.4.6+dfsg2-4.2
has caused the Debian Bug report #965538,
regarding gcc-h8300-hms: Removal of obsolete debhelper compat 5 and 6 in 
bookworm
to be marked as done.

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

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


-- 
965538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-h8300-hms
Version: 1:3.4.6+dfsg2-4.1
Severity: normal
Usertags: compat-5-6-removal

Hi,

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

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

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

  * Compat 7 is the bare minimum


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

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


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


Thanks,
~Niels


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

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

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

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: gcc-h8300-hms
Source-Version: 1:3.4.6+dfsg2-4.2
Done: Adrian Bunk 

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated gcc-h8300-hms package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Jan 2022 16:12:47 +0200
Source: gcc-h8300-hms
Architecture: source
Version: 1:3.4.6+dfsg2-4.2
Distribution: unstable
Urgency: low
Maintainer: Michael Tautschnig 
Changed-By: Adrian Bunk 
Closes: 965538
Changes:
 gcc-h8300-hms (1:3.4.6+dfsg2-4.2) unstable; urgency=low
 .
   * Non-maintainer upload.
   * debian/compat: 5 -> 7. (Closes: #965538)
Checksums-Sha1:
 a56cde3b4400a311435ff325ab78810e73588177 1861 gcc-h8300-hms_3.4.6+dfsg2-4.2.dsc
 76968f0091042de427a46966c3f65bb03044a6f3 58668 
gcc-h8300-hms_3.4.6+dfsg2-4.2.debian.tar.xz
Checksums-Sha256:
 fe2671812856acb40caf6a260f19e8d5080a79fc9f1903b3eb2cc34b6c649679 1861 
gcc-h8300-hms_3.4.6+dfsg2-4.2.dsc
 75a0d563251e48ca990d11969c5882675cc19ed9a76162442f0cff4193fd39bb 58668 
gcc-h8300-hms_3.4.6+dfsg2-4.2.debian.tar.xz
Files:
 7e8ce3b7c7550b0c6d05f576764d2bb4 1861 devel extra 
gcc-h8300-hms_3.4.6+dfsg2-4.2.dsc
 81924ac5d30876d42718e115bbe3e211 58668 devel extra 
gcc-h8300-hms_3.4.6+dfsg2-4.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHoHSsACgkQiNJCh6LY
mLHKbw/+JoT9RIm9BbnJ9IbMnFUZthMXhrj4HoBzS5/ItKgqhvQuP6VQzfFuAmVn
+SzVcbKsv+sMWhjGLALQhDHjKb9D2bry7KGE5FOVN74ilRikzkqQ2AGk5o+OmhQf
Y3KcK8VIwrddvGllPjsIOIo0RxEFLbug61x0AZZrLHIVnaAKAiua+i3DjEpquY9w
4O2ZyLOpLSo9OJzbL3/YmNxwEgBpUlrXZw03FCyHDuyccZXivvbzctnR7AWtsmwU
Uyi2txpB4Ng1tTavCCCun8jRMFDevGkNPAH2enrtw/SYdWiN7EQ/4/9SqrOgxHed
0KeiHjdnkBayDspmzFJgqskjbmJtdo6Bd83I6PPGXSv6tOLBVO+C9bppLlCf6pFP
OWUzTP0un/ncVH9SgqzTW67HqAJw74Lbk+DYuynvLv9X7F/aNAVH3/JzVDsqM5Wc
cScrjXFsF6rmiLg/k6SH5gfTzDAn/8G0UUxS+bpiajT/Yv/UlM5YSl6wKpsj0Evr
HNv73JtVLw3jaVqr+xjQJiyQ8s6BbimqgNwwpxHMrFQEl/4otA1NKNYmYfMmmiYr
XG7b3qeMLG98cx9sQT23i7cAqt1Dmji7oZwNt0Yqis98EsgLzNM8izdUTrcKoLnm
As6IEu/aCnzlnzOftptcX8AAmgwcBreimdDtLWCkw8fOYQfUY/E=
=H7XY
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Thu, 03 Feb 2022 21:48:57 +
with message-id 
and subject line Bug#965491: fixed in dictconv 0.2-7.1
has caused the Debian Bug report #965491,
regarding dictconv: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


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

Hi,

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

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

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

  * Compat 7 is the bare minimum


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

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


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


Thanks,
~Niels


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

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

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

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: dictconv
Source-Version: 0.2-7.1
Done: Adrian Bunk 

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated dictconv package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Jan 2022 16:23:08 +0200
Source: dictconv
Architecture: source
Version: 0.2-7.1
Distribution: unstable
Urgency: low
Maintainer: Francesco Namuri 
Changed-By: Adrian Bunk 
Closes: 581630 965491
Changes:
 dictconv (0.2-7.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * debian/compat: 5 -> 7. (Closes: #965491)
   * Spelling fix in the package description. (Closes: #581630)
Checksums-Sha1:
 1a9c9734dbe298cfbafef783084b451677acfb4d 1739 dictconv_0.2-7.1.dsc
 926216064eeaa8cdfbcdb1820d5ebc834f3efc05 3191 dictconv_0.2-7.1.diff.gz
Checksums-Sha256:
 3ca3773080c45595bf28041ee79cf873c15a4caa0cc70fa218e0d9c4f109dec2 1739 
dictconv_0.2-7.1.dsc
 77b5d518dd3c085cbb7268b4e881209c4fd4da53eb819fbb0a0d213553d4e71f 3191 
dictconv_0.2-7.1.diff.gz
Files:
 24f325239c17fe67e1dc7c59dba9096d 1739 utils optional dictconv_0.2-7.1.dsc
 7f4b8890c218063226d7ad8c177b28a0 3191 utils optional dictconv_0.2-7.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHoH2sACgkQiNJCh6LY
mLHGqBAAm5CHGW6qv5gMUK9wr0g2pAzpdqxego122R9ADLMG9eRpJWp6EOpoJ8SL
jOMv0NHThRIzUiSp8HwEQxxSJYhfcKHShrDq1mPe4WQDWjTPFimJP6gXVKLTxV25
m3B5yqhtLGZRP899gxDxvydky/yWTtG75XAJNTWUKSBcCvkJKYKgQRlAcU86H2pd
XvIo/dL/cVxUuCrvzHVv6l/lYPw2nvus9zo8Ot9KjbMHgsfkypwOhEloX02OCNeA
pbr7NmEBv/Ft3mUL+usFxCPuZvxxk1aag35h9waB3Jp1EUQJanHuCIpjcgeSX8Up
/c83AfyQrGX5AFsuW7a2WAqq2vBcd/cl5aC0kSV4RQOCzHUCz0t9yy5CJdcDhHCZ
F7M0wHyzloSJooPhWDf43UtT/nfBlC6nmBmvybI4TBsNDDdGZbSJFXrUWeH803+f
ztstBldJaKnSGzEjewlXakZT3pAjpg0FwJGF9Q9Ky5Kvr8J+4NYA25RZAHkWExs+
85BIlNYv/CmmAiGP10BcbOKSGBUrCrhUOFKKCUG/kbpVhO1aj+x0Dhq2L23jbCny
SUFQ9vnKrD2jw09it4JdJnL0rqWIsH0sTjIGBwqCM6J1ACtS1MAgP9Z6hTmHElT6
k2+TizhEdM4wGFkuLBF/LSAkkV8cKIHyifbYYPcYNsK2lGTbFnI=
=GRdP
-END PGP SIGNATURE End Message ---

Bug#1004847: marked as done (nvidia-graphics-drivers: CVE-2022-21813, CVE-2022-21814)

[Debian Bug Tracking System]

Your message dated Thu, 03 Feb 2022 21:49:49 +
with message-id 
and subject line Bug#1004847: fixed in nvidia-graphics-drivers 470.103.01-1
has caused the Debian Bug report #1004847,
regarding nvidia-graphics-drivers: CVE-2022-21813, CVE-2022-21814
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.)


-- 
1004847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004847
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
Control: clone -1 -2 -3 -4 -5 -6 -7
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-21813, 
CVE-2022-21814
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-21813, 
CVE-2022-21814
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-21813, 
CVE-2022-21814
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-21813, 
CVE-2022-21814
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-21813, 
CVE-2022-21814
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-21813, 
CVE-2022-21814
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 450.51-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1

https://nvidia.custhelp.com/app/answers/detail/a_id/5312

CVE‑2022‑21813  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel driver, where improper handling of
insufficient permissions or privileges may allow an unprivileged
local user limited write access to protected memory, which can
lead to denial of service.

CVE‑2022‑21814  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel driver package, where improper
handling of insufficient permissions or privileges may allow an
unprivileged local user limited write access to protected memory,
which can lead to denial of service.

Driver Branch   CVE IDs Addressed
R510, R470  CVE-2022-21813, CVE-2022-21814

Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 470.103.01-1
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers, 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.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
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: Thu, 03 Feb 2022 22:27:11 +0100
Source: nvidia-graphics-drivers
Architecture: source
Version: 470.103.01-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1004847
Changes:
 nvidia-graphics-drivers (470.103.01-1) unstable; urgency=medium
 .
   * New upstream production branch release 470.103.01 (2022-01-31).
 * Fixed CVE‑2022‑21813, CVE‑2022‑21814.  (Closes: #1004847)
   https://nvidia.custhelp.com/app/answers/detail/a_id/5312
 - Added support for the following GPUs: NVIDIA GeForce MX550,
   NVIDIA GeForce MX570, NVIDIA GeForce RTX 2050.
 .
   [ Andreas Beckmann ]
   * Refresh patches.
   * Update nv-readme.ids.
Checksums-Sha1:
 a089e8c54a460f363b3f41b597662b267c825dd4 6743 
nvidia-graphics-drivers_470.103.01-1.dsc
 08cd8e5326fdc77a755fda1eb8f63df1d62c910e 272473978 
nvidia-graphics-drivers_470.103.01.orig-amd64.tar.gz
 6531d3a249e2d9d8ef584cb1659b06454f8e4a0d 184473786 
nvidia-graphics-drivers_470.103.01.orig-arm64.tar.gz
 3bb42b02e44737b82039eb3d821453c8112c2c77 140 
nvidia-graphics-drivers_470.103.01.orig.tar.gz
 4727eec9630c7fb70215d02162a345b569217402 

Bug#1002429: marked as done (openems: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: 'debian/control')

[Debian Bug Tracking System]

Your message dated Thu, 03 Feb 2022 21:49:55 +
with message-id 
and subject line Bug#1002429: fixed in openems 
0.0.35+git20190103.6a75e98+dfsg.1-3.1
has caused the Debian Bug report #1002429,
regarding openems: FTBFS: FileNotFoundError: [Errno 2] No such file or 
directory: 'debian/control'
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.)


-- 
1002429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002429
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openems
Version: 0.0.35+git20190103.6a75e98+dfsg.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_clean
> rm -f -r CSXCAD/build || true
> rm -f -r QCSXCAD/build || true
> rm -f -r openEMS/build || true
> rm -f -r AppCSXCAD/build || true
> rm -f debian/man/*.1
> cd CSXCAD/python && PYBUILD_VERSIONS="3.10 3.9" pybuild --clean
> Traceback (most recent call last):
>   File "/usr/share/dh-python/dhpython/debhelper.py", line 72, in __init__
> with open('debian/control', 'r', encoding='utf-8') as fp:
> FileNotFoundError: [Errno 2] No such file or directory: 'debian/control'
> 
> During handling of the above exception, another exception occurred:
> 
> Traceback (most recent call last):
>   File "/usr/bin/pybuild", line 572, in 
> main(cfg)
>   File "/usr/bin/pybuild", line 107, in main
> tmp_certainty = tmp_plugin.detect(tmp_context)
>   File "/usr/share/dh-python/dhpython/build/plugin_pep517.py", line 69, in 
> detect
> dh = DebHelper(build_options())
>   File "/usr/share/dh-python/dhpython/debhelper.py", line 94, in __init__
> raise Exception('cannot find debian/control file')
> Exception: cannot find debian/control file
> make[1]: *** [debian/rules:63: override_dh_auto_clean] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/openems_0.0.35+git20190103.6a75e98+dfsg.1-3_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: openems
Source-Version: 0.0.35+git20190103.6a75e98+dfsg.1-3.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated openems package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 20 Jan 2022 13:19:49 +0200
Source: openems
Architecture: source
Version: 0.0.35+git20190103.6a75e98+dfsg.1-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Adrian Bunk 
Closes: 1002429
Changes:
 openems (0.0.35+git20190103.6a75e98+dfsg.1-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/rules: PYBUILD_SYSTEM = distutils to workaround FTBFS
 with new dh-python. (Closes: #1002429)
Checksums-Sha1:
 61d44f2d3bafe39ca25df54714bf271e29411511 2742 
openems_0.0.35+git20190103.6a75e98+dfsg.1-3.1.dsc
 0265749ffe4fc81266ac95c556f092c5d3c95a6d 14936 
openems_0.0.35+git20190103.6a75e98+dfsg.1-3.1.debian.tar.xz
Checksums-Sha256:
 40526a753725fd7ddf6e882b84b85db6cfa2e324106887df98a84d22273d8baa 2742 
openems_0.0.35+git20190103.6a75e98+dfsg.1-3.1.dsc
 be8c5c3f82c25f7f484840281e8b50151d1da96e64d8bc33821aff4675135d19 14936 
openems_0.0.35+git20190103.6a75e98+dfsg.1-3.1.debian.tar.xz
Files:
 cb2fd2eeade76b9814d2f11f6024daaf 2742 electronics optional 
openems_0.0.35+git20190103.6a75e98+dfsg.1-3.1.dsc
 21d36f0d6f7911151fd3538b21722d97 14936 electronics optional 

Bug#1002180: marked as done (clamfs: FTBFS: stats.cxx:73:34: error: ‘mallinfo mallinfo()’ is deprecated [-Werror=deprecated-declarations])

[Debian Bug Tracking System]

Your message dated Thu, 03 Feb 2022 21:48:46 +
with message-id 
and subject line Bug#1002180: fixed in clamfs 1.2.0-2.1
has caused the Debian Bug report #1002180,
regarding clamfs: FTBFS: stats.cxx:73:34: error: ‘mallinfo mallinfo()’ is 
deprecated [-Werror=deprecated-declarations]
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> g++ -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror 
> -Wextra -I/usr/include -I/usr/include/fuse3 -pthread -D_FILE_OFFSET_BITS=64 
> -DFUSE_USE_VERSION=31 -DRLOG_COMPONENT=clamfs -O2 -DNDEBUG  -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o stats.o stats.cxx
> stats.cxx: In member function ‘void clamfs::Stats::dumpMemoryStatsToLog()’:
> stats.cxx:73:34: error: ‘mallinfo mallinfo()’ is deprecated 
> [-Werror=deprecated-declarations]
>73 | struct mallinfo mi = mallinfo();
>   |  ^~
> In file included from stats.hxx:33,
>  from stats.cxx:25:
> /usr/include/malloc.h:118:24: note: declared here
>   118 | extern struct mallinfo mallinfo (void) __THROW __MALLOC_DEPRECATED;
>   |^~~~
> cc1plus: all warnings being treated as errors
> make[3]: *** [Makefile:407: stats.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/clamfs_1.2.0-2_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: clamfs
Source-Version: 1.2.0-2.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated clamfs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Jan 2022 18:35:36 +0200
Source: clamfs
Architecture: source
Version: 1.2.0-2.1
Distribution: unstable
Urgency: medium
Maintainer: Krzysztof Burghardt 
Changed-By: Adrian Bunk 
Closes: 1002180
Changes:
 clamfs (1.2.0-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Don't build with -Werror. (Closes: #1002180)
Checksums-Sha1:
 2ebfa065a14845177bdee42d874ba3902cb8e2ba 2023 clamfs_1.2.0-2.1.dsc
 9e161259a95cb34bbccf6b1c78f366edf4fbda71 7724 clamfs_1.2.0-2.1.debian.tar.xz
Checksums-Sha256:
 abd5feebff331ed025630666bf6a67efe01a7dcaee45005b15c8f787fc9ed923 2023 
clamfs_1.2.0-2.1.dsc
 20258ebbf57abc9875f9478bce5e4ead263de1af2cc6a0d7804c2c8aceb89d87 7724 
clamfs_1.2.0-2.1.debian.tar.xz
Files:
 aeedc6f028858aa41ede9962f71989fc 2023 utils optional clamfs_1.2.0-2.1.dsc
 09b94fbdb3f357e4626e62e81a91aece 7724 utils optional 
clamfs_1.2.0-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHoPoYACgkQiNJCh6LY
mLHQcBAApPNLCLRmTnwgBM0IEVA+E3RQ2Z08qHpr8UPcEUOBg5IYxoevtlMoTYls
hGG0FabvzSjk/W8Wm2/qXNXCmU39j6VjgamBIQOjN0BV77q1I9Q9/pXeiumupipa
szlVH2jB9dxmF1qteo3BYHVBbJJCbZ9IEC+LS6kma+PbsJ+1OS9wCg3YziP2xvbE
6XZ5b+SuON2vtZqomDKr3MG/qVFF8JRkq3EIjcaxEHTlOju9IxpFszHzXT8GcstH
oXPRR7ZdX4NsqMJmTCN920F33dnfmQkCBtywc3AK+8KfnFZdGWqTGeFIfOep3Igo
tTe+UvbcuZv+q91vVNupvkqZP1pfN6QjkaiiW60bFPodemaVJ8IoI3KYnDqjoawP
3wrKIjzktBzF+qrghtpY8IK5urE9M4dpRKP8+e8zC0YB/h84QSvJOQD5aOouZDdk

Bug#1002167: marked as done (hmat-oss: FTBFS: memory_instrumentation.cpp:145:39: error: ‘mallinfo mallinfo()’ is deprecated [-Werror=deprecated-declarations])

[Debian Bug Tracking System]

Your message dated Thu, 03 Feb 2022 21:49:19 +
with message-id 
and subject line Bug#1002167: fixed in hmat-oss 1.2.0-2.2
has caused the Debian Bug report #1002167,
regarding hmat-oss: FTBFS: memory_instrumentation.cpp:145:39: error: ‘mallinfo 
mallinfo()’ is deprecated [-Werror=deprecated-declarations]
to be marked as done.

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

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


-- 
1002167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hmat-oss
Version: 1.2.0-2.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/bin/c++ -D_GNU_SOURCE -Dhmat_oss_EXPORTS -I/<>/include 
> -I/<>/obj-x86_64-linux-gnu -I/<>/src -fopenmp 
> -Werror -Wall -Wno-unused-result -Wno-sign-compare -Wno-literal-suffix  -g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -ffast-math 
> -funsafe-math-optimizations -fopenmp -fPIC -MD -MT 
> CMakeFiles/hmat-oss.dir/src/common/memory_instrumentation.cpp.o -MF 
> CMakeFiles/hmat-oss.dir/src/common/memory_instrumentation.cpp.o.d -o 
> CMakeFiles/hmat-oss.dir/src/common/memory_instrumentation.cpp.o -c 
> /<>/src/common/memory_instrumentation.cpp
> /<>/src/common/memory_instrumentation.cpp: In member function 
> ‘void hmat::MemoryInstrumenter::allocImpl(hmat::MemoryInstrumenter::mem_t, 
> char)’:
> /<>/src/common/memory_instrumentation.cpp:145:39: error: 
> ‘mallinfo mallinfo()’ is deprecated [-Werror=deprecated-declarations]
>   145 | global_mallinfo = mallinfo();
>   |   ^~
> In file included from 
> /<>/src/common/memory_instrumentation.cpp:32:
> /usr/include/malloc.h:118:24: note: declared here
>   118 | extern struct mallinfo mallinfo (void) __THROW __MALLOC_DEPRECATED;
>   |^~~~
> [ 40%] Building CXX object CMakeFiles/hmat-oss.dir/src/compression.cpp.o
> /usr/bin/c++ -D_GNU_SOURCE -Dhmat_oss_EXPORTS -I/<>/include 
> -I/<>/obj-x86_64-linux-gnu -I/<>/src -fopenmp 
> -Werror -Wall -Wno-unused-result -Wno-sign-compare -Wno-literal-suffix  -g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -ffast-math 
> -funsafe-math-optimizations -fopenmp -fPIC -MD -MT 
> CMakeFiles/hmat-oss.dir/src/compression.cpp.o -MF 
> CMakeFiles/hmat-oss.dir/src/compression.cpp.o.d -o 
> CMakeFiles/hmat-oss.dir/src/compression.cpp.o -c 
> /<>/src/compression.cpp
> cc1plus: all warnings being treated as errors
> make[3]: *** [CMakeFiles/hmat-oss.dir/build.make:163: 
> CMakeFiles/hmat-oss.dir/src/common/memory_instrumentation.cpp.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/hmat-oss_1.2.0-2.1_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: hmat-oss
Source-Version: 1.2.0-2.2
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated hmat-oss package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Jan 2022 18:14:34 +0200
Source: hmat-oss
Architecture: source
Version: 1.2.0-2.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Adrian Bunk 
Closes: 1002167
Changes:
 hmat-oss (1.2.0-2.2) unstable; urgency=medium
 .
   * 

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

[Debian Bug Tracking System]

Your message dated Thu, 03 Feb 2022 21:34:56 +
with message-id 
and subject line Bug#965713: fixed in makedev 2.3.1-95
has caused the Debian Bug report #965713,
regarding makedev: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


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

Hi,

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

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

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

  * Compat 7 is the bare minimum


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

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


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


Thanks,
~Niels


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

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

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

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: makedev
Source-Version: 2.3.1-95
Done: Joao Eriberto Mota Filho 

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

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

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated makedev 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 03 Feb 2022 01:51:59 -0300
Source: makedev
Architecture: source
Version: 2.3.1-95
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Joao Eriberto Mota Filho 
Closes: 965713
Changes:
 makedev (2.3.1-95) unstable; urgency=medium
 .
   * QA upload.
   * Migrations:
   - DebSrc to 3.0.
   - debian/copyright to 1.0 format. Consequently:
   ~ debian/dirs: removed no longer needed line
 usr/share/lintian/overrides.
   ~ debian/makedev.lintian: no longer needed. Removed.
   - debian/rules to new (reduced) format.
   * 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: #965713
   * debian/control:
   - Added 'Rules-Requires-Root: binary-targets' to source stanza.
   - Bumped Standards-Version to 4.6.0.
   - Changed Vcs-* URLs to salsa.debian.org.
   * debian/gbp.conf: removed.
   * debian/lintian-overrides: created to override a false-positive about a
 device name.
   * debian/patches/:
   - 010_patches-from-1.0: created to gather old patches from DebSrc 1.0.
   - 020_fix-typos-manpage.patch: created to fix some typos in manpage.
   * debian/postinst: added 'set -e'.
   * debian/salsa-ci.yml: added to provide CI tests for Salsa.
Checksums-Sha1:
 95ae0d4018567ec338d4f565ca62cffc92a4923f 1774 makedev_2.3.1-95.dsc
 3586643421849855796027f966c1c7530c48b4c5 44644 makedev_2.3.1-95.debian.tar.xz
 67b50e9f3df219bd344356c9f730c2e5ab72d25e  makedev_2.3.1-95_source.buildinfo
Checksums-Sha256:
 7d41c9764c453a01b2daf40be78b4ad29834d45629e009326d30f5f5513da4d5 1774 
makedev_2.3.1-95.dsc
 0e88b3cd7042c89e6093fa4a80da32356ab185325f1486c3db11cb8676b71737 44644 
makedev_2.3.1-95.debian.tar.xz
 58f5d1fd3255653a846ab2bde0222fefd1ef1f6e5c2879be95f0c2da078377a9  
makedev_2.3.1-95_source.buildinfo
Files:
 5f416aa48b99745c9886bd95ac91966c 1774 admin optional makedev_2.3.1-95.dsc
 ce4af12b8f339f04aa5cc82ba683cdc9 44644 

Bug#1000872: marked as done (parl-desktop-world depends on removed package.)

[Debian Bug Tracking System]

Your message dated Thu, 03 Feb 2022 21:18:42 +
with message-id 
and subject line Bug#1000872: fixed in debian-parl 1.9.30
has caused the Debian Bug report #1000872,
regarding parl-desktop-world depends on removed package.
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.)


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

Package: parl-desktop-world
Version: 1.9.29
Severity: serious

parl-desktop-world depends on thunderbird-l10n-si which is no longer built from 
the thunderbird source
package, it is still present in unstable as a cruft package but is completely 
gone from testing.
--- End Message ---
--- Begin Message ---
Source: debian-parl
Source-Version: 1.9.30
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated debian-parl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 03 Feb 2022 22:07:23 +0100
Source: debian-parl
Architecture: source
Version: 1.9.30
Distribution: unstable
Urgency: medium
Maintainer: DebianParl team 
Changed-By: Jonas Smedegaard 
Closes: 1000872
Changes:
 debian-parl (1.9.30) unstable; urgency=medium
 .
   * rebuild using newer boxer-data
 + stop include thunderbird-l10n-si, gone from Debian;
   closes: bug#1000872, thanks to Peter Green
   * update blends snippet:
 + relax shellcheck to tolerate stylistic-only warning SC2129
   * declare compliance with Debian Policy 4.6.0
   * tighten lintian overrides
Checksums-Sha1:
 053ef5d8678db7ca16864786fe877abf73e2d07d 1967 debian-parl_1.9.30.dsc
 dca72b6f0b557d34aa1d14c487e3ae8f4d16 10940 debian-parl_1.9.30.tar.xz
 b291e50029b79cc0f5a2914b8697b1e5d83fc093 9138 
debian-parl_1.9.30_amd64.buildinfo
Checksums-Sha256:
 e311a993141ac191099bbcd451e10b1bed6ecbfaec6ac244690d4f510ed431f6 1967 
debian-parl_1.9.30.dsc
 f9246b763011fda9fa45fe4b11cfdc05f50af9ad5fbfceb4da3fcbd0f23f664a 10940 
debian-parl_1.9.30.tar.xz
 b9b173154d76667d78a0f5f161faf65323c5a935dc87f4792d080a0f9641631c 9138 
debian-parl_1.9.30_amd64.buildinfo
Files:
 e4876470f932ea92f4e88fa533b934e5 1967 misc optional debian-parl_1.9.30.dsc
 9a3a001df0161fb6f9e08e1491095e15 10940 misc optional debian-parl_1.9.30.tar.xz
 6d5f57ac4d29072c3140e4fda1b3f78e 9138 misc optional 
debian-parl_1.9.30_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmH8RQ4ACgkQLHwxRsGg
ASHQYQ/+MsHUkRQa6vwfEO1mShhQQQsziJiKc8wP5EnV48to79aHvR3kHw40pgn9
k/XIKjyM95hEhoCDHm1P9+c5qS+OO8uVhNPy9fM/mMfn0Q8kyL1c1H4qSoEZQH0W
ySjdA/9rSQbixDVG3RxzZitZxYatwjfZFiaaJ6SRPyp9WAKGzVy3W3BG6zszYtJL
FA261AW0A2NQcSLRluQXerl/4jjTh4Akx8LqSU2Fm9rc+g74jqoqd6UsFUT9b7/o
mcjGBqB9lD3aWnB0whq7abF1d+NsY/1s86rKd6W7YRwHxJG26d5Ky9c6Fz6xQT6c
UYH0bbP/j0uLTb2VX9Ht0B6DuKogpzc7D5mQk8kc0Ly+ANjCoUjROHXOR/0aRwHl
Lui3YbOsEDJPrLJIwpFDFe49zDbBG6CTPfY2wNtVrq6tPA05FapvBYCY0uyzyQqs
dm0T8j+GBQKIOspIMg1Cb8G+PlBebGjFocutUgiqY5NNNMUTd49QJpO3kT2s5iqR
246hTD6580rKa8REyaHDzHaNkFqQFI8Ck1NIEiIW90glMtCuR38ocqjTQwFwcAJT
hhoZTQOmFpbinQVDOQIVI+Wr2KowiWV7ijF6d3HZTViHsF+IzF85VydK6ZgtDwJj
cZBZepL/YhJJGaFge3/toOtDKvnkFVdyOOLLMrne1RyIRRDtCQA=
=XJZS
-END PGP SIGNATURE End Message ---

Bug#1001068: samba: Missing upstream commit 0a546be0 on bullseye, bookworm and sid (part of CVE-2020-25717)

[Salvatore Bonaccorso]

Hi Jörg,

On Fri, Dec 03, 2021 at 03:44:02PM +0100, Jörg Behrmann wrote:
> Package: samba
> Version: 2:4.13.13+dfsg-1~deb11u2
> Severity: important
> X-Debbugs-Cc: t...@security.debian.org
> 
> The upstream samba commit 0a546be0 is included in the buster security release
> 2:4.9.5+dfsg-5+deb10u2 via the patch file bug-14901-v4-9.patch, but is missing
> in the bullseye security release 2:4.13.13+dfsg-1~deb11u2.
> 
> Pleae apply that patch in bullseye as well, so that the idmap_nss fallback via
> SID mapping works.

In case you have the possiblity, can you test the packages from
https://people.debian.org/~carnil/tmp/samba/2022-01-31/bullseye/ ?

Regards,
Salvatore

Processed: severity of 1001068 is serious, found 1001068 in 2:4.13.14+dfsg-1

[Debian Bug Tracking System]

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

> severity 1001068 serious
Bug #1001068 [samba] samba: Missing upstream commit 0a546be0 on bullseye, 
bookworm and sid (part of CVE-2020-25717)
Severity set to 'serious' from 'important'
> found 1001068 2:4.13.14+dfsg-1
Bug #1001068 [samba] samba: Missing upstream commit 0a546be0 on bullseye, 
bookworm and sid (part of CVE-2020-25717)
Marked as found in versions samba/2:4.13.14+dfsg-1.
> thanks
Stopping processing here.

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

Processed: bug 1001068 is forwarded to https://bugzilla.samba.org/show_bug.cgi?id=14901#c9

[Debian Bug Tracking System]

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

> forwarded 1001068 https://bugzilla.samba.org/show_bug.cgi?id=14901#c9
Bug #1001068 [samba] samba: Missing upstream commit 0a546be0 on bullseye, 
bookworm and sid (part of CVE-2020-25717)
Set Bug forwarded-to-address to 
'https://bugzilla.samba.org/show_bug.cgi?id=14901#c9'.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

Your message dated Thu, 03 Feb 2022 20:36:44 +
with message-id 
and subject line Bug#999240: fixed in sc 7.16-4.1
has caused the Debian Bug report #999240,
regarding sc: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: sc
Source-Version: 7.16-4.1
Done: Ying-Chun Liu (PaulLiu) 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 26 Jan 2022 01:22:23 +0800
Source: sc
Architecture: source
Version: 7.16-4.1
Distribution: unstable
Urgency: low
Maintainer: Adam Majer 
Changed-By: Ying-Chun Liu (PaulLiu) 
Closes: 815936 884727 999240
Changes:
 sc (7.16-4.1) unstable; urgency=low
 .
   [ Ying-Chun Liu (PaulLiu)  ]
   * Non-maintainer upload.
   * Change debhelper compat version from 5 to 11. (Closes: #999240)
 - Update debian/rules.
   + This also fixes FTCBFS (Closes: #884727)
 - Clean files by debian/clean
   * Add debian/patches/hardening: hardening format strings.
   * Merge patches from Ubuntu. (Closes: #815936)
   * Add autopkgtest
 .
   [ Serge Hallyn  ]
   * lex.c: do not set notimeout (LP: #1549665)
Checksums-Sha1:
 3bedaf38ba0dc5bdd494c8263f21b01de7dac368 1803 sc_7.16-4.1.dsc
 aedcf9c2919f3c97d75b27dd17c9ca20c25fde71 11040 sc_7.16-4.1.debian.tar.xz
 26120004598a279a63de3173fa83e63ac6776d90 6319 sc_7.16-4.1_source.buildinfo
Checksums-Sha256:
 aa0ebe39cac31b2053bfd4e320ada9fb2a1b2ced16ae05f8732b84110988ab60 1803 
sc_7.16-4.1.dsc
 7db779e11d1517e18ec7d93e83c57ccdca782c620faba5aa7e8cbbfd1c53fe2e 11040 
sc_7.16-4.1.debian.tar.xz
 d34060883223506c1c573efc40e234ebc2ef393cda69dca075726b128e57490e 6319 
sc_7.16-4.1_source.buildinfo
Files:
 10ea75e0dbf82eee1fee1fd59fdf1d1a 1803 math optional sc_7.16-4.1.dsc
 e35caba6703e217765caba2039dfaf12 11040 math optional sc_7.16-4.1.debian.tar.xz
 9ff7ff1cea439a34e2e8979e256e50c8 6319 math optional 
sc_7.16-4.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmH8NAoTHHBhdWxsaXVA
ZGViaWFuLm9yZwAKCRBEFz+hPQWIiOOWEACe2SRQTNdWf8v/xawh3qHUZY8dyvQk
jU7DhsPf5+5LSCoYDD+tNkyQFEghCWW3nTXJXLhTXHuiBHOWDqny7P4husnPLe8A
zXJIORDH1mNgIf7UKI1PDUr/mpzcwooR9BPNKqVclwFGJ3aH6oi6kYrqPGnx6C4w
0S+7P+6DxeYTFftXZOHHCzGWpZLgP9lpMNQoMc8tzKPs5JGOMFwt5JG9GZeJ3Yav
svuSNkKji56CXvDgQacVhMrRWu0enucFPHHGN01XNHNSdPG5aiH5nLuJyERG0+ZN
xNccAYsKkveDCDmBizo3n0rfX7ZYd4K6QZ//K5HAWZpGL9lhojirdA7PQAB6Xj7r
xdx3o7V1NES/xxUwyqDrf8BOoyOfXw7Zxfu8fyJ5yHqv2PZPnFNnarY4e6HchhDr
SaNP0B5EbCsz5ZT8281OLdb/u9lmSoWcs8cRVb6iAC1tc1GCKGwdliZdfPSEU/2G
bctmREYZrAhY5s27FLX27rpBgHKUtpFPsYvnxo0SQRYGuXIFQ4ROXI/dlVh5DEbm
sPh4ONfQJnMo5VDLmeI8lCqj4TdRpSlBsSHXLRS0P74TdELEAehGMlyVxicBuEPc
DFd6o5h0e7XoE8PAUcPCJp7z8imYpXqIamyOK6x0YR2MEaViM7ka7wSVieu+5SKO
rTMPTEhe3hiuKA==
=BaIU
-END PGP SIGNATURE End Message ---

Bug#1004935: connman: CVE-2022-23096 CVE-2022-23097 CVE-2022-23098

[Salvatore Bonaccorso]

Source: connman
Version: 1.36-2.3
Severity: grave
Tags: security upstream
Forwarded: https://lore.kernel.org/connman/20220125090026.5108-1-w...@monom.org/
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1.36-2.2
Control: found -1 1.36-2.1~deb10u1
Control: found -1 1.36-2.1~deb10u2

Hi,

The following vulnerabilities were published for connman.

CVE-2022-23096[0]:
| An issue was discovered in the DNS proxy in Connman through 1.40. The
| TCP server reply implementation lacks a check for the presence of
| sufficient Header Data, leading to an out-of-bounds read.


CVE-2022-23097[1]:
| An issue was discovered in the DNS proxy in Connman through 1.40.
| forward_dns_reply mishandles a strnlen call, leading to an out-of-
| bounds read.


CVE-2022-23098[2]:
| An issue was discovered in the DNS proxy in Connman through 1.40. The
| TCP server reply implementation has an infinite loop if no data is
| received.


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-23096
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23096
[1] https://security-tracker.debian.org/tracker/CVE-2022-23097
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23097
[2] https://security-tracker.debian.org/tracker/CVE-2022-23098
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23098

Regards,
Salvatore

Processed: connman: CVE-2022-23096 CVE-2022-23097 CVE-2022-23098

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.36-2.2
Bug #1004935 [src:connman] connman: CVE-2022-23096 CVE-2022-23097 CVE-2022-23098
Marked as found in versions connman/1.36-2.2.
> found -1 1.36-2.1~deb10u1
Bug #1004935 [src:connman] connman: CVE-2022-23096 CVE-2022-23097 CVE-2022-23098
Marked as found in versions connman/1.36-2.1~deb10u1.
> found -1 1.36-2.1~deb10u2
Bug #1004935 [src:connman] connman: CVE-2022-23096 CVE-2022-23097 CVE-2022-23098
Marked as found in versions connman/1.36-2.1~deb10u2.

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

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

[Ying-Chun Liu (PaulLiu)]

Hi Sebastian,

I've maintained onscripter, which uses avifile to play animation in game.
So it is still needed for me for that package.
I think I can spend my time fixing #1004789 - forward porting to ffmpeg 5.0.

Will fix #1004789 and then close this bug too on next upload.

Yours,
Paul

Sebastian Ramacher 於 2022/2/2 05:25 寫道:

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


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#1004748: guestfs-tools ftbfs with new ocaml

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1004748 [src:guestfs-tools] guestfs-tools ftbfs with new ocaml
Added tag(s) patch.

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

Bug#1004748: guestfs-tools ftbfs with new ocaml

[Sergio Durigan Junior]

Control: tags -1 + patch

On Tuesday, February 01 2022, Matthias Klose wrote:

> 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

Upstream already has a fix:

https://github.com/rwmjones/guestfs-tools/commit/577f7aee4b1c720f4c4826115b49a0c3870b149e

The following debdiff should fix it on Debian (feel free to
remove/rewrite the changelog entry).

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/

diff --git a/debian/changelog b/debian/changelog
index a849c22..67427d8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+guestfs-tools (1.46.1-5) UNRELEASED; urgency=medium
+
+  [ Hilko Bengen ]
+  * Run tests on more architectures: ppc64el, s390x
+
+  [ Sergio Durigan Junior ]
+  * d/p/Disable-OCaml-warning-6-completely.patch:
+Disable OCaml warning 6 completely, fixing FTBFS with new ocaml.
+(Closes: #1004748)
+
+ -- Sergio Durigan Junior   Thu, 03 Feb 2022 14:14:11 
-0500
+
 guestfs-tools (1.46.1-4) unstable; urgency=medium
 
   * Add missing build-dependencies
diff --git a/debian/patches/Disable-OCaml-warning-6-completely.patch 
b/debian/patches/Disable-OCaml-warning-6-completely.patch
new file mode 100644
index 000..0c0e427
--- /dev/null
+++ b/debian/patches/Disable-OCaml-warning-6-completely.patch
@@ -0,0 +1,41 @@
+From: "Richard W.M. Jones" 
+Date: Fri, 10 Dec 2021 10:20:34 +
+Subject: Disable OCaml warning 6 completely
+
+Warning 6 "labels-omitted" is not useful.  It's fine to omit labels on
+positional arguments.
+
+Example:
+
+  File "perl_edit.ml", line 30, characters 2-13:
+  30 |   c_edit_file (verbose ()) g (Guestfs.c_pointer g) file expr
+ ^^^
+  Warning 6 [labels-omitted]: label verbose was omitted in the application of 
this function.
+
+The function is specified as:
+
+  external c_edit_file : verbose:bool -> Guestfs.t -> int64 -> string -> 
string -> unit
+
+The complaint is that the verbose: label has been omitted from the
+first argument when the function is called, but IMO this is a
+stylistic thing, not a bug.
+
+Origin: backport, 
https://github.com/rwmjones/guestfs-tools/commit/577f7aee4b1c720f4c4826115b49a0c3870b149e
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004748
+---
+ m4/guestfs-ocaml.m4 | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/m4/guestfs-ocaml.m4 b/m4/guestfs-ocaml.m4
+index f5ac7ef..bc80e0f 100644
+--- a/m4/guestfs-ocaml.m4
 b/m4/guestfs-ocaml.m4
+@@ -166,7 +166,7 @@ EOF
+ ])
+ 
+ dnl Flags we want to pass to every OCaml compiler call.
+-OCAML_WARN_ERROR="-warn-error CDEFLMPSUVYZX+52-3"
++OCAML_WARN_ERROR="-warn-error +C+D+E+F+L+M+P+S+U+V+Y+Z+X+52-3-6 -w -6"
+ AC_SUBST([OCAML_WARN_ERROR])
+ OCAML_FLAGS="-g -annot $safe_string_option"
+ AC_SUBST([OCAML_FLAGS])
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..1e2c7c0
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+Disable-OCaml-warning-6-completely.patch


signature.asc
Description: PGP signature

Processed: Re: Bug#1004071 closed by Debian FTP Masters (Bug#1004075: Removed package(s) from unstable)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1004071 {Done: Debian FTP Masters } 
[google-guest-agent,python3-google-compute-engine] 
google-guest-agent,python3-google-compute-engine: both ship 
/usr/bin/google_metadata_script_runner
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 20190916-1+rm.
> reassign -1 google-guest-agent 2026.00-1
Bug #1004071 [google-guest-agent,python3-google-compute-engine] 
google-guest-agent,python3-google-compute-engine: both ship 
/usr/bin/google_metadata_script_runner
Bug reassigned from package 'google-guest-agent,python3-google-compute-engine' 
to 'google-guest-agent'.
No longer marked as found in versions google-compute-image-packages/20190916-1 
and google-guest-agent/2026.00-1.
Ignoring request to alter fixed versions of bug #1004071 to the same values 
previously set
Bug #1004071 [google-guest-agent] 
google-guest-agent,python3-google-compute-engine: both ship 
/usr/bin/google_metadata_script_runner
Marked as found in versions google-guest-agent/2026.00-1.

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

Bug#1004071: closed by Debian FTP Masters (Bug#1004075: Removed package(s) from unstable)

[Andreas Beckmann]

Control: reopen -1
Control: reassign -1 google-guest-agent 2026.00-1

With python3-google-compute-engine gone, you should add

  Breaks+Replaces: python3-google-compute-engine

to google-guest-agent, to ensure there are no upgrade issues if 
python3-google-compute-engine from oldstable is still installed.



Andreas

Bug#1002259: marked as done (nodejs: FTBFS: TypeError: marked is not a function)

[Debian Bug Tracking System]

Your message dated Thu, 3 Feb 2022 20:13:57 +0100
with message-id 

and subject line Re: [Pkg-javascript-devel] Bug#1002259: nodejs: FTBFS: 
TypeError: marked is not a function
has caused the Debian Bug report #1002259,
regarding nodejs: FTBFS: TypeError: marked is not a function
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.)


-- 
1002259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002259
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nodejs
Version: 12.22.7~dfsg-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> mkdir -p out/doc
> mkdir -p out/doc/api
> cp -r doc/api out/doc/
> rm -f out/doc/api/*.html
> rm -f out/doc/api/*.json
> if [ -x /<>/./node ] && [ -e /<>/./node ]; then 
> /<>/./node  tools/doc/generate.js --node-version=v12.22.7 
> --format=html doc/api/addons.md > out/doc/api/addons.html; elif [ -x `which 
> node` ] && [ -e `which node` ] && [ `which node` ]; then `which node`  
> tools/doc/generate.js --node-version=v12.22.7 --format=html doc/api/addons.md 
> > out/doc/api/addons.html; else echo "No available node, cannot run \"node  
> tools/doc/generate.js --node-version=v12.22.7 --format=html doc/api/addons.md 
> > out/doc/api/addons.html\""; exit 1; fi;
> /<>/tools/doc/html.js:43
> const gtocHTML = marked(gtocMD).replace(
>  ^
> 
> TypeError: marked is not a function
> at Object. (/<>/tools/doc/html.js:43:18)
> at Module._compile (internal/modules/cjs/loader.js:999:30)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
> at Module.load (internal/modules/cjs/loader.js:863:32)
> at Function.Module._load (internal/modules/cjs/loader.js:708:14)
> at Module.require (internal/modules/cjs/loader.js:887:19)
> at require (internal/modules/cjs/helpers.js:74:18)
> at /<>/tools/doc/generate.js:63:7
> at FSReqCallback.readFileAfterClose [as oncomplete] 
> (internal/fs/read_file_context.js:63:3)
> make[3]: *** [Makefile:746: out/doc/api/addons.html] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/nodejs_12.22.7~dfsg-2_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: nodejs
Version: 12.22.9~dfsg-1


Le mar. 21 déc. 2021 à 17:48, Lucas Nussbaum  a écrit :

> Source: nodejs
> Version: 12.22.7~dfsg-2
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20211220 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
> > make[2]: Entering directory '/<>'
> > mkdir -p out/doc
> > mkdir -p out/doc/api
> > cp -r doc/api out/doc/
> > rm -f out/doc/api/*.html
> > rm -f out/doc/api/*.json
> > if [ -x /<>/./node ] && [ -e /<>/./node ];
> then /<>/./node  tools/doc/generate.js --node-version=v12.22.7
> --format=html doc/api/addons.md > out/doc/api/addons.html; elif [ -x `which
> node` ] && [ -e `which node` ] && [ `which node` ]; then `which node`
> tools/doc/generate.js --node-version=v12.22.7 --format=html
> doc/api/addons.md > out/doc/api/addons.html; else echo "No available node,
> cannot run \"node  tools/doc/generate.js --node-version=v12.22.7
> --format=html doc/api/addons.md > out/doc/api/addons.html\""; exit 1; fi;
> > /<>/tools/doc/html.js:43
> > const gtocHTML = marked(gtocMD).replace(
> >  ^
> >
> > TypeError: marked is not a function
> > at Object. (/<>/tools/doc/html.js:43:18)
> > at Module._compile (internal/modules/cjs/loader.js:999:30)
> > at Object.Module._extensions..js
> (internal/modules/cjs/loader.js:1027:10)
> > at Module.load (internal/modules/cjs/loader.js:863:32)
> > at Function.Module._load (internal/modules/cjs/loader.js:708:14)
> > at Module.require (internal/modules/cjs/loader.js:887:19)
> > at require (internal/modules/cjs/helpers.js:74:18)
> > at 

Bug#1004926: libgd-graph-perl: FTBFS with libgd-perl >= 2.75

[gregor herrmann]

Source: libgd-graph-perl
Version: 1.48-2
Severity: serious
Tags: upstream ftbfs sid bookworm
Justification: fails to build from source
Forwarded: https://rt.cpan.org/Ticket/Display.html?id=140940

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As noticed by ci.d.n, libgd-graph-perl has test failures with recent
versions of libgd-perl (first 2.75-1, now 2.76-1).

The current failure is:

Problems reading t/images/logo_xbm_noext (tried: libgd best-guess) at 
t/bugfixes.t line 46.

#   Failed test '_read_logo_file succeeds for xbm without file extension'
#   at t/bugfixes.t line 46.

#   Failed test 'undef isa 'GD::Image''
#   at t/bugfixes.t line 48.
# undef isn't defined
# Looks like you failed 2 tests of 33.
t/bugfixes.t ... 
1..33
ok 1 - use GD::Graph;
ok 2 - Got an object from new()
ok 3 - An object of class 'GD::Graph' isa 'GD::Graph'
ok 4 - _read_logo_file succeeds for gif with file extension
ok 5 - An object of class 'GD::Image' isa 'GD::Image'
ok 6 - _read_logo_file succeeds for gif without file extension
ok 7 - An object of class 'GD::Image' isa 'GD::Image'
ok 8 - _read_logo_file succeeds for jpeg with file extension
ok 9 - An object of class 'GD::Image' isa 'GD::Image'
ok 10 - _read_logo_file succeeds for jpeg without file extension
ok 11 - An object of class 'GD::Image' isa 'GD::Image'
ok 12 - _read_logo_file succeeds for jpeg with alternate extension
ok 13 - An object of class 'GD::Image' isa 'GD::Image'
ok 14 - _read_logo_file succeeds for png with file extension
ok 15 - An object of class 'GD::Image' isa 'GD::Image'
ok 16 - _read_logo_file succeeds for png without file extension
ok 17 - An object of class 'GD::Image' isa 'GD::Image'
ok 18 - _read_logo_file succeeds for png with alternate extension
ok 19 - An object of class 'GD::Image' isa 'GD::Image'
ok 20 - _read_logo_file succeeds for xbm with file extension
ok 21 - An object of class 'GD::Image' isa 'GD::Image'
not ok 22 - _read_logo_file succeeds for xbm without file extension
not ok 23 - undef isa 'GD::Image'
ok 24 - Skipping: GD *really* doesn't support importing XPM files
ok 25 - Skipping: GD *really* doesn't support importing XPM files
ok 26 - Skipping: GD *really* doesn't support importing XPM files
ok 27 - Skipping: GD *really* doesn't support importing XPM files
ok 28 - use GD::Graph::bars;
ok 29 - freakish divide-by-zero trick
ok 30 - No fatalities on the above
ok 31 - Survived 20792
ok 32 - and got a result
ok 33 - No timeout
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/33 subtests 


This is tracked upstream at https://rt.cpan.org/Ticket/Display.html?id=140940
and https://rt.cpan.org/Ticket/Display.html?id=140910


Cheers,
gregor


-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmH8Hw9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbsZhAAurp7E0WDXHqB1PTcwOcOjHhUp8nvJDUlSxZyIFaoHAisJ9XFNynvRbs3
Z3qTSk50jmsQtEnUjAfQoW1QWnyRv2GCCiohcPx/8BPLjFL8/PLVhkIEX26QMTsh
nVlxwxlYeEWZxLTFyThWdlzHm49xOxAov4Iexe3vvyf5JZN3HcVsqYe3nprDW+8H
2QNL//Di12HRubFOGnkkYtDjOGuin7sDD+e083+CUabZHRlL/u9euOknZU2FvFh3
12SglgjdR4SOiJOOQ7OPUqwBJlllX0NYU629iILCwfJNDXJHTZUWZgqLt99vL2hm
NLYd9dMT1ZIqrtw4wNE1jC2JQbPh9+W1+PofcGltp+8ykgrc5mtqaz20tlgaP8I0
N8ts8LDxENVY5iFI0VweyQDeTG4wsG522v3WCRlpNqAuVJp7LxP9pDxY3CufDVS9
y09xKwznr6waDM8S4CnL4GCqOyQZw7D2TvEtl0hT/JwmsDcGgDEjD2wK2dgMiC6K
wn+DHSeDSvKt2m9MvFaA1QDiu9Ir0W78q0kLFosUyIcxUUy6UAthGOkSQ1NZpH3N
nl2+dX/S0bdksClNt5ir5hbuFYAJ/neJwv2n9hdmsRa3wRwS5ViPA76XZ1qLZkw7
ZkK2iOTc3YRwnU9mvxbUevExNFjQ2fjS2BmzW7jEz505xRXmrvE=
=9COu
-END PGP SIGNATURE-

Bug#987353: marked as done (CVE-2020-8903 CVE-2020-8907 CVE-2020-8933)

[Debian Bug Tracking System]

Your message dated Thu, 03 Feb 2022 18:03:07 +
with message-id 
and subject line Bug#1004075: Removed package(s) from unstable
has caused the Debian Bug report #987353,
regarding CVE-2020-8903 CVE-2020-8907 CVE-2020-8933
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.)


-- 
987353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: google-compute-image-packages
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team 

https://cloud.google.com/compute/docs/security-bulletins#2020619 seems unfixed
unstable/bullseye still.

Patches:
https://github.com/GoogleCloudPlatform/guest-oslogin/pull/29

Cheers,
Moritz  

--- End Message ---
--- Begin Message ---
Version: 20190916-1+rm

Dear submitter,

as the package google-compute-image-packages has just been removed from the 
Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1004075

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1004071: marked as done (google-guest-agent,python3-google-compute-engine: both ship /usr/bin/google_metadata_script_runner)

[Debian Bug Tracking System]

Your message dated Thu, 03 Feb 2022 18:03:07 +
with message-id 
and subject line Bug#1004075: Removed package(s) from unstable
has caused the Debian Bug report #1004071,
regarding google-guest-agent,python3-google-compute-engine: both ship 
/usr/bin/google_metadata_script_runner
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.)


-- 
1004071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: google-guest-agent,python3-google-compute-engine
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 2026.00-1
Control: found -1 20190916-1

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package python3-google-compute-engine.
  Preparing to unpack .../5-python3-google-compute-engine_20190916-1_all.deb ...
  Unpacking python3-google-compute-engine (20190916-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-8A9en2/5-python3-google-compute-engine_20190916-1_all.deb 
(--unpack):
   trying to overwrite '/usr/bin/google_metadata_script_runner', which is also 
in package google-guest-agent 2026.00-1
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-8A9en2/5-python3-google-compute-engine_20190916-1_all.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/bin/google_metadata_script_runner

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


google-guest-agent=2026.00-1_python3-google-compute-engine=20190916-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 20190916-1+rm

Dear submitter,

as the package google-compute-image-packages has just been removed from the 
Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1004075

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

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

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:datalad
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1002359 (http://bugs.debian.org/1002359)
> # Bug title: datalad: FTBFS: dh_auto_test: error: pybuild --test --test-nose 
> -i python{version} -p "3.10 3.9" --test-nose returned exit code 13
> #  * https://github.com/datalad/datalad/issues/6362
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1002359 + fixed-upstream
Bug #1002359 [src:datalad] datalad: FTBFS: dh_auto_test: error: pybuild --test 
--test-nose -i python{version} -p "3.10 3.9" --test-nose returned exit code 13
Added tag(s) fixed-upstream.
> usertags 1002359 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:ruby-redis, src:ruby-fakeredis

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:ruby-redis, 
> src:ruby-fakeredis
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1002985 (http://bugs.debian.org/1002985)
> # Bug title: ruby-redis breaks ruby-fakeredis autopkgtest
> #  * https://github.com/guilleiguaran/fakeredis/pull/247
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1002985 + fixed-upstream
Bug #1002985 [src:ruby-redis, src:ruby-fakeredis] ruby-redis breaks 
ruby-fakeredis autopkgtest
Added tag(s) fixed-upstream.
> usertags 1002985 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1002985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002985
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-03 17:30:28 +0100, Marc Haber wrote:
> Do you see this TLS error with other remotes?

No, but the machine only has 11 days of logs, while I don't use it
much in these times. So that's almost nothing.

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

Bug#1004923: autopkgtest failure due to removed libRemoteIndex*.a

[Sergio Durigan Junior]

Source: llvm-toolchain-12
Version: 1:12.0.1-19
Severity: serious

Hi,

The following commit:

https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/commit/87ee3c332f9b0736064a588bdf974bbda0288d58

is causing an autopkgtest failure because the build system still
requires the libraries libRemoteIndex{ServiceProto,Proto}.a to exist
when running the command1 unittest, as can be seen in the logs:

--8<---cut here---start->8---
# "Test: CMake find LLVM and Clang in default path"
(cd cmaketest/standard && CC=clang-$VERSION CXX=clang++-$VERSION cmake .. > 
/dev/null)
CMake Error at /usr/lib/llvm-12/lib/cmake/clang/ClangTargets.cmake:720 
(message):
  The imported target "RemoteIndexProto" references the file

 "/usr/lib/llvm-12/lib/libRemoteIndexProto.a"

  but this file does not exist.  Possible reasons include:

  * The file was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

 "/usr/lib/llvm-12/lib/cmake/clang/ClangTargets.cmake"

  but not all the files it references.

Call Stack (most recent call first):
  /usr/lib/cmake/clang-12/ClangConfig.cmake:20 (include)
  CMakeLists.txt:9 (find_package)


autopkgtest [16:06:06]: test command1: ---]
autopkgtest [16:06:06]: test command1:  - - - - - - - - - - results - - - - - - 
- - - -
command1 FAIL non-zero exit status 1
--8<---cut here---end--->8---

I don't know the details regarding why these libraries are being removed
(according to the comment on d/rules, it's just because they're unused),
so maybe the solution here is to just revert the change.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


signature.asc
Description: PGP signature

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

[Marc Haber]

On Thu, Feb 03, 2022 at 02:51:10PM +0100, Vincent Lefevre wrote:
> On 2022-02-03 14:21:58 +0100, Marc Haber wrote:
> > Is the bug repeatable by unfreezing the message and forcing a delivery
> > attempt? If so, you might be able to get a core dump from the delivering
> > exim.
> 
> The delivery was successful. There was still a "TLS error on
> connection (recv): The TLS connection was non-properly terminated."
> error, but no 450:
> 
> 2022-02-02 13:42:28 Start queue run: pid=150965 -qff
> 2022-02-02 13:42:28 1nEt2b-0008jG-97 Unfrozen by forced delivery
> 2022-02-02 13:42:31 1nEt2b-0008jG-97 H=mx1.mailchannels.net [54.189.39.249] 
> TLS error on connection (recv): The TLS connection was non-properly 
> terminated.

Just for the protocol: gnutls-cli --insecure -s -p 25 54.189.39.249
allows me to simulate an EHLO/STARTTLS/EHLO/QUIT session that gets
properly terminated. Andreas as GnuTLS maintainer might make more sense
from that finding.

> 2022-02-02 13:42:31 1nEt2b-0008jG-97 => xxx@yyy R=dnslookup T=remote_smtp 
> H=mx1.mailchannels.net [54.189.39.249] 
> X=TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256 CV=yes 
> DN="CN=*.mailchannels.net" C="250 2.0.0 Ok: queued as 6D9D5201EF"
> 2022-02-02 13:42:31 1nEt2b-0008jG-97 Completed
> 2022-02-02 13:42:31 End queue run: pid=150965 -qff

That doesn't help though, we neeed the error to happen ;-)

Do you see this TLS error with other remotes?

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#961834: Any updates?

[Zbynek Michl]

Hello,

is reported issue still valid? I use this theme in Debian Bookworm (Xfce
4.16) and I can't see any trouble with it.

I would appreciate returning the package to the repo if there is no real
blocker anymore.

Thank you
Zbynek

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 1004461 https://github.com/agronholm/anyio/issues/417
Bug #1004461 [src:python-anyio] python-anyio FTBFS on IPV6-only buildds
Set Bug forwarded-to-address to 'https://github.com/agronholm/anyio/issues/417'.
> thanks
Stopping processing here.

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

Bug#1004902: openrct2: FTBFS TTF.cpp:358:32: error: invalid conversion from 'const TTF_Font*' to 'TTF_Font*'

[Mathias Gibbens]

tags 1004902 + pending
thanks

  Thanks for the report! I've fixed the error locally and plan to get a
new version uploaded in the near future.

Mathias

On Thu, 2022-02-03 at 11:13 +0100, Andreas Beckmann wrote:
> Source: openrct2
> Version: 0.3.5.1+ds-2
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in
> the past)
> 
> Hi,
> 
> openrct2 recently started to FTBFS, probably due to a change in a
> build
> dependency:
> 
> /build/openrct2-0.3.5.1+ds/src/openrct2/drawing/TTF.cpp: In function
> 'bool ttf_provides_glyph(const TTF_Font*, codepoint_t)':
> /build/openrct2-0.3.5.1+ds/src/openrct2/drawing/TTF.cpp:358:32:
> error: invalid conversion from 'const TTF_Font*' to 'TTF_Font*' [-
> fpermissive]
>   358 | return TTF_GlyphIsProvided(font, codepoint);
>   |    ^~~~
>   |    |
>   |    const TTF_Font*
> In file included from /build/openrct2-
> 0.3.5.1+ds/src/openrct2/drawing/../config/../drawing/Font.h:10,
>  from /build/openrct2-
> 0.3.5.1+ds/src/openrct2/drawing/../config/../drawing/Drawing.h:16,
>  from /build/openrct2-
> 0.3.5.1+ds/src/openrct2/drawing/../config/Config.h:13,
>  from /build/openrct2-
> 0.3.5.1+ds/src/openrct2/drawing/TTF.cpp:21:
> /usr/include/SDL2/SDL_ttf.h:184:59: note:   initializing argument 1
> of 'int TTF_GlyphIsProvided(TTF_Font*, Uint16)'
>   184 | extern DECLSPEC int SDLCALL TTF_GlyphIsProvided(TTF_Font
> *font, Uint16 ch);
>   |
> ~~^~~~
> make[3]: *** [CMakeFiles/libopenrct2.dir/build.make:2347:
> CMakeFiles/libopenrct2.dir/src/openrct2/drawing/TTF.cpp.o] Error 1
> 
> 
> I have a successful build from Jan 07, the most "promising" build
> dependency
> change since then seems to be
> 
> -Setting up libsdl2-ttf-2.0-0:amd64 (2.0.15+dfsg1-2) ...^M
> +Setting up libsdl2-ttf-2.0-0:amd64 (2.0.18+dfsg-2) ...^M
> 
> -Setting up libsdl2-ttf-dev:amd64 (2.0.15+dfsg1-2) ...^M
> +Setting up libsdl2-ttf-dev:amd64 (2.0.18+dfsg-2) ...^M
> 
> 
> Andreas



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

Processed: Re: Bug#1004902: openrct2: FTBFS TTF.cpp:358:32: error: invalid conversion from 'const TTF_Font*' to 'TTF_Font*'

[Debian Bug Tracking System]

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

> tags 1004902 + pending
Bug #1004902 [src:openrct2] openrct2: FTBFS TTF.cpp:358:32: error: invalid 
conversion from 'const TTF_Font*' to 'TTF_Font*'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: bug #1002325 forwarded upstream

[Debian Bug Tracking System]

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

> forwarded 1002325 https://github.com/enthought/envisage/issues/396
Bug #1002325 [src:python-envisage] python-envisage: FTBFS: dh_auto_test: error: 
pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13
Set Bug forwarded-to-address to 
'https://github.com/enthought/envisage/issues/396'.
> --
Stopping processing here.

Please contact me if you need assistance.
-- 
1002325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002325
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-03 14:21:58 +0100, Marc Haber wrote:
> Is the bug repeatable by unfreezing the message and forcing a delivery
> attempt? If so, you might be able to get a core dump from the delivering
> exim.

The delivery was successful. There was still a "TLS error on
connection (recv): The TLS connection was non-properly terminated."
error, but no 450:

2022-02-02 13:42:28 Start queue run: pid=150965 -qff
2022-02-02 13:42:28 1nEt2b-0008jG-97 Unfrozen by forced delivery
2022-02-02 13:42:31 1nEt2b-0008jG-97 H=mx1.mailchannels.net [54.189.39.249] TLS 
error on connection (recv): The TLS connection was non-properly terminated.
2022-02-02 13:42:31 1nEt2b-0008jG-97 => xxx@yyy R=dnslookup T=remote_smtp 
H=mx1.mailchannels.net [54.189.39.249] 
X=TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256 CV=yes 
DN="CN=*.mailchannels.net" C="250 2.0.0 Ok: queued as 6D9D5201EF"
2022-02-02 13:42:31 1nEt2b-0008jG-97 Completed
2022-02-02 13:42:31 End queue run: pid=150965 -qff

> If the 450 is casued by greylisting on the remote side, that debugging
> attempt must be close to the first time of sending the message so that
> the 450 is still there.

Unfortunately, I can't control that.

Perhaps the bug is due to the combination of both a "TLS error on
connection (recv): The TLS connection was non-properly terminated."
error and a 450, e.g. in case exim does something valid only if
there were no errors. A potential security issue?

If I understand correctly, the error comes from

  record_io_error(state, (int)inbytes, US"recv", NULL);

in src/tls-gnu.c, tls_read().

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

Processed: Bug#994866 marked as pending in gmerlin

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #994866 [gmerlin-data,libgmerlin-dev] gmerlin-data,libgmerlin-dev: both 
ship /usr/share/gmerlin/plugin.sym
Added tag(s) pending.

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

Bug#994866: marked as pending in gmerlin

[IOhannes zmölnig]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/gmerlin/-/commit/789c80728a39ba61e76ecf6c4917ea1b91f2bb8e


Remove /usr/share/gmerlin/plugin.sym from gmerlin-data

it's in libgmerlin-dev

Closes: #994866


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/994866

Bug#1003785: marked as pending in gmerlin

[IOhannes zmölnig]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/gmerlin/-/commit/a12530d0abef87fcffeadcf013cacfabae63ad9f


Add patch to fix FTBFS with format-security

Closes: #1003785


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1003785

Processed: Bug#1003785 marked as pending in gmerlin

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1003785 [src:gmerlin] gmerlin: FTBFS: format not a string literal and no 
format arguments
Added tag(s) pending.

-- 
1003785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003785
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

[Marc Haber]

On Thu, Feb 03, 2022 at 03:46:22AM +0100, Vincent Lefevre wrote:
> On 2022-02-03 03:29:24 +0100, Vincent Lefevre wrote:
> > On 2022-02-02 18:20:48 +0100, Andreas Metzler wrote:
> > > Any chance of getting a coredump?
> > 
> > exim didn't leave a coredump. I could see that Mutt disables coredumps
> > after some time. I don't know under which condition.
> 
> I've eventually found that coredumps are disabled when I start Mutt
> from my window manager (FVWM), but not from a terminal (actually,
> that's the same wrapper in both cases). The reason seems that
> disabled coredumps is the default (according to /proc/.../limits),
> but I re-enable them in my shell.

Is the bug repeatable by unfreezing the message and forcing a delivery
attempt? If so, you might be able to get a core dump from the delivering
exim.

If the 450 is casued by greylisting on the remote side, that debugging
attempt must be close to the first time of sending the message so that
the 450 is still there.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#997786: marked as done (python-cymruwhois: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 176))

[Debian Bug Tracking System]

Your message dated Thu, 03 Feb 2022 13:19:09 +
with message-id 
and subject line Bug#997786: fixed in python-cymruwhois 1.6-4
has caused the Debian Bug report #997786,
regarding python-cymruwhois: FTBFS: There is a syntax error in your 
configuration file: invalid syntax (conf.py, line 176)
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.)


-- 
997786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cymruwhois
Version: 1.6-3.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):
> make[1]: Entering directory '/<>'
> PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml docs/ 
> docs/_build/html # HTML generator
> Running Sphinx v4.2.0
> 
> Configuration error:
> There is a syntax error in your configuration file: invalid syntax (conf.py, 
> line 176)
> 
> make[1]: *** [debian/rules:11: override_dh_auto_build] Error 2


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-cymruwhois_1.6-3.2_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-cymruwhois
Source-Version: 1.6-4
Done: Ana Custura 

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

Debian distribution maintenance software
pp.
Ana Custura  (supplier of updated python-cymruwhois 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 02 Feb 2022 14:49:23 +
Source: python-cymruwhois
Architecture: source
Version: 1.6-4
Distribution: unstable
Urgency: medium
Maintainer: Ana Custura 
Changed-By: Ana Custura 
Closes: 997786
Changes:
 python-cymruwhois (1.6-4) unstable; urgency=medium
 .
   * Drop support for python2
   * Patch docs to python3 (Closes: #997786)
   * Bump debhelper-compat version to 13
   * Add Rules-Requires-Root: no to debian/control
Checksums-Sha1:
 cf25f04e6506cfef1b3632150c169a21e186702c 2101 python-cymruwhois_1.6-4.dsc
 7bfc5732959397241064af18c549f401bf920bdc 3896 
python-cymruwhois_1.6-4.debian.tar.xz
 e338bcef83f4bfc6f39ee7a38c87d4ec30a13116 7956 
python-cymruwhois_1.6-4_amd64.buildinfo
Checksums-Sha256:
 22205ad84d951123ae30f8f4ba646d42766175a81fde183fb806aa5b75f79a76 2101 
python-cymruwhois_1.6-4.dsc
 b835166132371fb76fd896dd9e3567ed7551e7c304ff61dc7c4914af443e32c7 3896 
python-cymruwhois_1.6-4.debian.tar.xz
 66d43608a80ce2015a861fc3cc24e59a57feaaa04a3d2ae5f4f6b6a914268a15 7956 
python-cymruwhois_1.6-4_amd64.buildinfo
Files:
 a93c04cff5e4e73f72bf06427e7fb735 2101 python optional 
python-cymruwhois_1.6-4.dsc
 4c5097f7b69a85844e1826ac0bf7d8fb 3896 python optional 
python-cymruwhois_1.6-4.debian.tar.xz
 4740be8eaaf75e94176297af5ac66525 7956 python optional 
python-cymruwhois_1.6-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEMEVxS8/NmLlMBvgk0AURaWEueyoFAmH70uoACgkQ0AURaWEu
eyqdOQ//V7cCFUzpJ2TwLqkTbdo2c6069J9DgkdR7t3/047iXF+Taa1c/sobqvNJ
o4NZd4nwFZNjuld67HkZp+cs9++CLCUnOmPG/Ju3FAYPCJxEO6j3Q8VAb6py6nFf
CY14XFWZl+JaKRZiO7SNexzR4GrQJ8dkUZnXJbrfpM6kv2PrGw7kHqRbRsaUr7qo
XnBja4OvuBPvgLwpJ+jCXEWjy9+aMULj44CxhBbJ+10lTxz6uERSPXJmMsOkKplW
YEewnIuY0FTIhktGMxw/iUuwPzmcSkZiwSd5v1GvubcLhzPxfgKnYQRJy4m4heLE
U07yIJYmgIKkDFkDNDlE3PaG2o/+kSR0wq+/2KSBJpK4jNmc73pd/icZCaP+8rK3
Zb/fKIE+eDDdkMLMVSA+4ZVKYjDF/UhmgUCXmJ5wBNNObN88vtwilFLp48O7raTR
kyS0RdiXOfH2SQvfHKwylbTnDqJWFz0BNM5k+/tk+JKOI+y+d4UQlhjQ2VmA1DwX
+N4xUCcCFylPPPrLqKtCsoW1SNrQboM5qEAaWu3KfDHy+QN8kPcWKPPh2iv6BZD4

Bug#1004870: python-xarray: autopkgtest regression on s390x

[Rajendra Kharat1]

We are having a look. Will check and update.
 
Thanks,
Rajendra
 
- Original message -From: "Graham Inggs" To: "Debian Bug Tracking System" Cc:Subject: [EXTERNAL] Bug#1004870: python-xarray: autopkgtest regression on s390xDate: Thu, Feb 3, 2022 1:06 AM 
Source: python-xarrayVersion: 0.21.0-1X-Debbugs-CC: debian...@lists.debian.org, debian-s...@lists.debian.orgSeverity: seriousUser: debian...@lists.debian.orgUsertags: regressionHi Maintainerpython-xarray's autopkgtests are failing on the big-endian s390xarchitecture [1].I've copied what I hope is the relevant part of the log below.RegardsGraham[1] https://ci.debian.net/packages/p/python-xarray/unstable/s390x/ === FAILURES ===___ test_calendar_cftime_2D[365_day] ___data = "" 'data' (lon: 10, lat: 10, time: 100)>array([[[0.25602205, 0.47375523, 0.88418655, ..., 0.19579452,...0.0 2.222 4.444 6.667 ... 13.33 15.56 17.78 20.0  * time     (time) object 2000-01-01 00:00:00 ... 2000-01-05 03:00:00    @requires_cftime    def test_calendar_cftime_2D(data) -> None:        # 2D np datetime:>       data = "">            np.random.randint(1, 100, size=(4,5)).astype("        )/usr/lib/python3/dist-packages/xarray/tests/test_accessor_dt.py:426:_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _/usr/lib/python3/dist-packages/xarray/core/dataarray.py:400: in __init__    data = "">/usr/lib/python3/dist-packages/xarray/core/variable.py:232: inas_compatible_data    data = "">/usr/lib/python3/dist-packages/xarray/core/variable.py:176: in_possibly_convert_objects    return np.asarray(pd.Series(values.ravel())).reshape(values.shape)/usr/lib/python3/dist-packages/pandas/core/series.py:439: in __init__    data = "" index, dtype, copy)/usr/lib/python3/dist-packages/pandas/core/construction.py:545: insanitize_array    subarr = _try_cast(data, dtype, copy, raise_cast_failure)/usr/lib/python3/dist-packages/pandas/core/construction.py:704: in _try_cast    return sanitize_to_nanoseconds(arr, copy=copy)/usr/lib/python3/dist-packages/pandas/core/dtypes/cast.py:1740: insanitize_to_nanoseconds    values = conversion.ensure_datetime64ns(values)pandas/_libs/tslibs/conversion.pyx:256: inpandas._libs.tslibs.conversion.ensure_datetime64ns    ???_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _>   ???E   pandas._libs.tslibs.np_datetime.OutOfBoundsDatetime: Out of boundsnanosecond timestamp: -259805407763208-03-07 00:00:00pandas/_libs/tslibs/np_datetime.pyx:120: OutOfBoundsDatetime___ test_calendar_cftime_2D[360_day] ___data = "" 'data' (lon: 10, lat: 10, time: 100)>array([[[0.3348676 , 0.8813548 , 0.07158625, ..., 0.12469613,...0.0 2.222 4.444 6.667 ... 13.33 15.56 17.78 20.0  * time     (time) object 2000-01-01 00:00:00 ... 2000-01-05 03:00:00    @requires_cftime    def test_calendar_cftime_2D(data) -> None:        # 2D np datetime:>       data = "">            np.random.randint(1, 100, size=(4,5)).astype("        )/usr/lib/python3/dist-packages/xarray/tests/test_accessor_dt.py:426:_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _/usr/lib/python3/dist-packages/xarray/core/dataarray.py:400: in __init__    data = "">/usr/lib/python3/dist-packages/xarray/core/variable.py:232: inas_compatible_data    data = "">/usr/lib/python3/dist-packages/xarray/core/variable.py:176: in_possibly_convert_objects    return np.asarray(pd.Series(values.ravel())).reshape(values.shape)/usr/lib/python3/dist-packages/pandas/core/series.py:439: in __init__    data = "" index, dtype, copy)/usr/lib/python3/dist-packages/pandas/core/construction.py:545: insanitize_array    subarr = _try_cast(data, dtype, copy, raise_cast_failure)/usr/lib/python3/dist-packages/pandas/core/construction.py:704: in _try_cast    return sanitize_to_nanoseconds(arr, copy=copy)/usr/lib/python3/dist-packages/pandas/core/dtypes/cast.py:1740: insanitize_to_nanoseconds    values = conversion.ensure_datetime64ns(values)pandas/_libs/tslibs/conversion.pyx:256: inpandas._libs.tslibs.conversion.ensure_datetime64ns    ???_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _>   ???E   pandas._libs.tslibs.np_datetime.OutOfBoundsDatetime: Out of boundsnanosecond timestamp: 768533895196513-09-16 16:00:00pandas/_libs/tslibs/np_datetime.pyx:120: OutOfBoundsDatetime___ test_calendar_cftime_2D[julian] data = "" 'data' (lon: 10, lat: 10, time: 100)>array([[[0.05513783, 0.72362925, 0.78967474, ..., 0.8560986 ,...0.0 2.222 4.444 6.667 ... 13.33 15.56 17.78 20.0  * time     (time) object 2000-01-01 00:00:00 ... 2000-01-05 03:00:00    @requires_cftime    def test_calendar_cftime_2D(data) -> None:        # 2D np datetime:>       data = "">            np.random.randint(1, 100, size=(4,5)).astype("        

Bug#1004902: openrct2: FTBFS TTF.cpp:358:32: error: invalid conversion from 'const TTF_Font*' to 'TTF_Font*'

[Andreas Beckmann]

Source: openrct2
Version: 0.3.5.1+ds-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

openrct2 recently started to FTBFS, probably due to a change in a build
dependency:

/build/openrct2-0.3.5.1+ds/src/openrct2/drawing/TTF.cpp: In function 'bool 
ttf_provides_glyph(const TTF_Font*, codepoint_t)':
/build/openrct2-0.3.5.1+ds/src/openrct2/drawing/TTF.cpp:358:32: error: invalid 
conversion from 'const TTF_Font*' to 'TTF_Font*' [-fpermissive]
  358 | return TTF_GlyphIsProvided(font, codepoint);
  |^~~~
  ||
  |const TTF_Font*
In file included from 
/build/openrct2-0.3.5.1+ds/src/openrct2/drawing/../config/../drawing/Font.h:10,
 from 
/build/openrct2-0.3.5.1+ds/src/openrct2/drawing/../config/../drawing/Drawing.h:16,
 from 
/build/openrct2-0.3.5.1+ds/src/openrct2/drawing/../config/Config.h:13,
 from 
/build/openrct2-0.3.5.1+ds/src/openrct2/drawing/TTF.cpp:21:
/usr/include/SDL2/SDL_ttf.h:184:59: note:   initializing argument 1 of 'int 
TTF_GlyphIsProvided(TTF_Font*, Uint16)'
  184 | extern DECLSPEC int SDLCALL TTF_GlyphIsProvided(TTF_Font *font, Uint16 
ch);
  | ~~^~~~
make[3]: *** [CMakeFiles/libopenrct2.dir/build.make:2347: 
CMakeFiles/libopenrct2.dir/src/openrct2/drawing/TTF.cpp.o] Error 1


I have a successful build from Jan 07, the most "promising" build dependency
change since then seems to be

-Setting up libsdl2-ttf-2.0-0:amd64 (2.0.15+dfsg1-2) ...^M
+Setting up libsdl2-ttf-2.0-0:amd64 (2.0.18+dfsg-2) ...^M

-Setting up libsdl2-ttf-dev:amd64 (2.0.15+dfsg1-2) ...^M
+Setting up libsdl2-ttf-dev:amd64 (2.0.18+dfsg-2) ...^M


Andreas


openrct2_0.3.5.1+ds-2.log.gz
Description: application/gzip

Bug#1004900: zim-tools: FTBFS on slow buildds

[Adrian Bunk]

Source: zim-tools
Version: 3.1.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=zim-tools=riscv64
https://buildd.debian.org/status/logs.php?pkg=zim-tools=mips64el

...
Expected equality of these values:
...
-[INFO] Total time taken by zimcheck: 0 seconds.\n
+[INFO] Total time taken by zimcheck: 1 seconds.\n
...

Bug#1004517: marked as done ([pyvo] CI failure with astropy 5.0.1; please update to version 1.2.1)

[Debian Bug Tracking System]

Your message dated Thu, 03 Feb 2022 08:38:58 +
with message-id 
and subject line Bug#1004517: fixed in pyvo 1.2.1-1
has caused the Debian Bug report #1004517,
regarding [pyvo] CI failure with astropy 5.0.1; please update to version 1.2.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.)


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

Source: pyvo
Version: 1.1-1
Severity: serious
Control: affects -1 astropy

Dear maintainer,

I just uploaded astropy-5.0.1 to unstable. It appears that pyvo 1.1 is 
no longer compatible and now leads to a CI test error:


https://ci.debian.net/data/autopkgtest/testing/amd64/p/pyvo/18800419/log.gz

Relevant lines:

  File "/usr/lib/python3/dist-packages/pyvo/utils/decorators.py", line 
4, in 

from astropy.utils.decorators import wraps
ImportError: cannot import name 'wraps' from 'astropy.utils.decorators' 
(/usr/lib/python3/dist-packages/astropy/utils/decorators.py)

autopkgtest [15:19:32]:  summary
python3-pyvo FAIL non-zero exit status 1


This is fixed upstream in pyvo 1.2.1:

https://github.com/astropy/pyvo/pull/283

so the easiest would be to upload the new version.

Best regards

Ole
--- End Message ---
--- Begin Message ---
Source: pyvo
Source-Version: 1.2.1-1
Done: Ole Streicher 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 03 Feb 2022 08:51:09 +0100
Source: pyvo
Architecture: source
Version: 1.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers 

Changed-By: Ole Streicher 
Closes: 1004517
Changes:
 pyvo (1.2.1-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
 .
   [ Ole Streicher ]
   * New upstream version 1.2.1. Closes: #1004517
Checksums-Sha1:
 bdafb7c8f9ae7dbd8d9ae64ac7736aadacf7e9b9 2136 pyvo_1.2.1-1.dsc
 0deace41d6dcc31eab7e9d768eb1244f324cd2b9 797412 pyvo_1.2.1.orig.tar.gz
 c76e9a1b1217ec17e3841ae60a5c3b3df4fd516a 4104 pyvo_1.2.1-1.debian.tar.xz
Checksums-Sha256:
 247a7cd158f001942dce4e998d827317d81ac27d6c802fa3194814a099a3f35d 2136 
pyvo_1.2.1-1.dsc
 8459ee8a78358077d480fd78a4d8c89fd0f243f46ec08c19bdd01f6fe87cdc3d 797412 
pyvo_1.2.1.orig.tar.gz
 4e018fe3cea675bce8f2d90a3a4e8c751b495e05e5c5cc3d2767a15d41d5baaf 4104 
pyvo_1.2.1-1.debian.tar.xz
Files:
 4b71e46f556e56d2870eb1ef2969e415 2136 python optional pyvo_1.2.1-1.dsc
 8eaa271c176e93924b840de1e486f4bf 797412 python optional pyvo_1.2.1.orig.tar.gz
 9c8fa20ace5af8c92d43100c8129f297 4104 python optional 
pyvo_1.2.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmH7ixAACgkQcRWv0HcQ
3Pd51xAAnIhVN4bP68vUI4ayjHedwhSt4ZHeFDlrOd8exwDBUQiofhagrCrrO2/4
eGK2rZSOEwILUvBlMvj/u7OpeZ6GTXkp65gXxGo4GOyLtVtl7MSp/tbjNFWckEUB
bPIXG6V4mARFs8sQSFKqgXFuLpnZaCzqdoonkC17vxMdV8qcHVuiTHIrevMuos4B
AZG4jniuGyCgcp0XLwpgKbKbUS1VD3CgbvJxGySj5vjsRINIA1Qxr60c198njPYV
4HwlDShntl98wYX1iRTJq3c9/yX/OqDpRVoJ0lCkS8Crt+awTZe5OTwbVk/fcWmx
f86cMe16IwSh9ZBtyJxXxzAqSJt71PgtSGusydZARWvruW66AzmWGvWPAfN4Pye7
lkrF7XcN9h59ZVSCkG1UKQ2e6EoAto0FfiGspgjKbWRspZ/EXn/mgO8w419PpFmt
tVUdyb0OCMqTzYjIWqSIAFR9LRO0gz+QxeIBlcSd9h0AJREUIrqBhrwtzWq9qBUi
VmXRa7VkDxRgh6WTAfEz+55dU3Irv08v/08D4kp0EOE8qBjp/FUdePxIw3ejP+iW
0uTFB8Lo4yPcq5V5d09/R6SjTnrXe1tKHPTLscgRwCqLzWp14oP8KVuf/Sb205VR
AIV0o87DPMPAoKvvxu6/Lle+OwRSMKjCO/XoeyhHOYvo4GW0Nrc=
=PK8o
-END PGP SIGNATURE End Message ---