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

[Debian Bug Tracking System]

Your message dated Fri, 18 Mar 2022 03:16:11 +
with message-id 
and subject line Bug#998930: fixed in xemacs21-packages 2009.02.17.dfsg.3-1
has caused the Debian Bug report #998930,
regarding xemacs21-packages: 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.)


-- 
998930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xemacs21-packages
Version: 2009.02.17.dfsg.2-5
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: xemacs21-packages
Source-Version: 2009.02.17.dfsg.3-1
Done: Mark Brown 

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

Debian distribution maintenance software
pp.
Mark Brown  (supplier of updated xemacs21-packages 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, 18 Mar 2022 01:40:42 +
Source: xemacs21-packages
Architecture: source
Version: 2009.02.17.dfsg.3-1
Distribution: unstable
Urgency: low
Maintainer: Mark Brown 
Changed-By: Mark Brown 
Closes: 965888 992089 998930
Changes:
 xemacs21-packages (2009.02.17.dfsg.3-1) unstable; urgency=low
 .
   * Drop LValue.java with non-free disparaging to Sun license
 condition (closes: #992089).
   * Drop xoobr binary from source.
   * Add build-indep and build-arch targets (closes: #998930).
   * debhelper 13, dh_prep (closes: #965888).
   * Policy 4.5.1 (no changes).
Checksums-Sha1:
 e0d118a6f12f48e08d3f3babb65006c27eabc5f9 1855 
xemacs21-packages_2009.02.17.dfsg.3-1.dsc
 022bb675fb10f9f79961e492e589adf4fa78ee54 28876139 
xemacs21-packages_2009.02.17.dfsg.3.orig.tar.gz
 f5e765aff822f4b2047463875396f0177616d270 25484 
xemacs21-packages_2009.02.17.dfsg.3-1.debian.tar.xz
 75fa712dd0dfd70f35efd185d37159a397ae099d 6955 
xemacs21-packages_2009.02.17.dfsg.3-1_source.buildinfo
Checksums-Sha256:
 7ccad1f2beca9203e27a959a48f935fd4210e5789f8cbe210695e44a589d6253 1855 
xemacs21-packages_2009.02.17.dfsg.3-1.dsc
 bed6b788ef0e1082f33a9c56ea1b4aa23bc2bf8bea7630f9815e731b1132ea43 28876139 
xemacs21-packages_2009.02.17.dfsg.3.orig.tar.gz
 dd06379976d3f22810838554e77b07d2cc2fe42954d6ffa6665a215cc0bc8c77 25484 
xemacs21-packages_2009.02.17.dfsg.3-1.debian.tar.xz
 253589b29adf7db16c062e7d6a8c3abe93cdb38b4690c3d7505ad13fba983a2a 6955 
xemacs21-packages_2009.02.17.dfsg.3-1_source.buildinfo
Files:
 a710050e7c9992c3072f04e7c14909d8 1855 editors optional 
xemacs21-packages_2009.02.17.dfsg.3-1.dsc
 1f4d0e5270fd111fbb05bb2c44554621 28876139 editors optional 
xemacs21-packages_2009.02.17.dfsg.3.orig.tar.gz
 ccfea7a9fc5e467ce68cee7510f95432 25484 editors optional 
xemacs21-packages_2009.02.17.dfsg.3-1.debian.tar.xz
 52544793c5efee2aceca4d7beb703ca7 6955 editors optional 
xemacs21-packages_2009.02.17.dfsg.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFHBAEBCgAxFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmIz7hMTHGJyb29uaWVA
ZGViaWFuLm9yZwAKCRAk1otyXVSH0OOPB/9z7StwprL52mQtiUPahT7XBBDPTQnf
tSRawH/A6aIs1y0U6VhCYgq09uXHFowN9e/x3wZ+1pb+af7rRu/mhpkqUxgVwaqI
2BmOEeZFoQheek0Zk4REOQzDGkv8TG/26k+Zv1VYMhzY+vSneWQUYmHmHBazTUT2
s7L+GDP6iZhW9aSVPHLcRlqhvZFxlTizZ45agC0nsCSCjQEQLmzH4f9nt85yKM4P
a4LDXl5NJmWMQWYZkT9+H71sMhPkrvZhTtscNrUcKmupYm9Cs1ZD2bsnc47Uxjfy
2ViHzfDn0FMjgbqxNjZMFKOrqmG74XFg

Bug#992089: marked as done (xemacs21-packages: contains a file with a non-free "disparaging to Sun" license)

[Debian Bug Tracking System]

Your message dated Fri, 18 Mar 2022 03:16:11 +
with message-id 
and subject line Bug#992089: fixed in xemacs21-packages 2009.02.17.dfsg.3-1
has caused the Debian Bug report #992089,
regarding xemacs21-packages: contains a file with a non-free "disparaging to 
Sun" license
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.)


-- 
992089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xemacs21-packages
Version: 2009.02.17.dfsg.2-4
Severity: serious
Tags: stretch buster bullseye sid
Justification: Policy 2.2.1

Dear Maintainer,

The file
xemacs-packages/jde/java/src/jde/debugger/expr/LValue.java
incorporates a non-free license, stating 

Sun grants you ("Licensee") a non-exclusive, royalty free, license to use,
modify and redistribute this software in source and binary code form,
provided that i) this copyright notice and license appear on all copies of
the software; and ii) Licensee does not utilize the software in a manner
which is disparaging to Sun.

This breaks at least DFSG-6, due to the "disparaging to Sun Microsystems"
clause.

Best regards,

-- 
Pierre Gruet
--- End Message ---
--- Begin Message ---
Source: xemacs21-packages
Source-Version: 2009.02.17.dfsg.3-1
Done: Mark Brown 

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

Debian distribution maintenance software
pp.
Mark Brown  (supplier of updated xemacs21-packages 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, 18 Mar 2022 01:40:42 +
Source: xemacs21-packages
Architecture: source
Version: 2009.02.17.dfsg.3-1
Distribution: unstable
Urgency: low
Maintainer: Mark Brown 
Changed-By: Mark Brown 
Closes: 965888 992089 998930
Changes:
 xemacs21-packages (2009.02.17.dfsg.3-1) unstable; urgency=low
 .
   * Drop LValue.java with non-free disparaging to Sun license
 condition (closes: #992089).
   * Drop xoobr binary from source.
   * Add build-indep and build-arch targets (closes: #998930).
   * debhelper 13, dh_prep (closes: #965888).
   * Policy 4.5.1 (no changes).
Checksums-Sha1:
 e0d118a6f12f48e08d3f3babb65006c27eabc5f9 1855 
xemacs21-packages_2009.02.17.dfsg.3-1.dsc
 022bb675fb10f9f79961e492e589adf4fa78ee54 28876139 
xemacs21-packages_2009.02.17.dfsg.3.orig.tar.gz
 f5e765aff822f4b2047463875396f0177616d270 25484 
xemacs21-packages_2009.02.17.dfsg.3-1.debian.tar.xz
 75fa712dd0dfd70f35efd185d37159a397ae099d 6955 
xemacs21-packages_2009.02.17.dfsg.3-1_source.buildinfo
Checksums-Sha256:
 7ccad1f2beca9203e27a959a48f935fd4210e5789f8cbe210695e44a589d6253 1855 
xemacs21-packages_2009.02.17.dfsg.3-1.dsc
 bed6b788ef0e1082f33a9c56ea1b4aa23bc2bf8bea7630f9815e731b1132ea43 28876139 
xemacs21-packages_2009.02.17.dfsg.3.orig.tar.gz
 dd06379976d3f22810838554e77b07d2cc2fe42954d6ffa6665a215cc0bc8c77 25484 
xemacs21-packages_2009.02.17.dfsg.3-1.debian.tar.xz
 253589b29adf7db16c062e7d6a8c3abe93cdb38b4690c3d7505ad13fba983a2a 6955 
xemacs21-packages_2009.02.17.dfsg.3-1_source.buildinfo
Files:
 a710050e7c9992c3072f04e7c14909d8 1855 editors optional 
xemacs21-packages_2009.02.17.dfsg.3-1.dsc
 1f4d0e5270fd111fbb05bb2c44554621 28876139 editors optional 
xemacs21-packages_2009.02.17.dfsg.3.orig.tar.gz
 ccfea7a9fc5e467ce68cee7510f95432 25484 editors optional 
xemacs21-packages_2009.02.17.dfsg.3-1.debian.tar.xz
 52544793c5efee2aceca4d7beb703ca7 6955 editors optional 
xemacs21-packages_2009.02.17.dfsg.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFHBAEBCgAxFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmIz7hMTHGJyb29uaWVA
ZGViaWFuLm9yZwAKCRAk1otyXVSH0OOPB/9z7StwprL52mQtiUPahT7XBBDPTQnf
tSRawH/A6aIs1y0U6VhCYgq09uXHFowN9e/x3wZ+1pb+af7rRu/mhpkqUxgVwaqI
2BmOEeZFoQheek0Zk4REOQzDGkv8TG/26k+Zv1VYMhzY+vSneWQUYmHmHBazTUT2
s7L+GDP6iZhW9aSVPHLcRlqhvZFxlTizZ45agC0nsCSCjQEQLmzH4f9nt85yKM4P
a4LDXl5NJmWMQWYZkT9+H71sMhPkrvZhTtscNrUcKmupYm9Cs1ZD2bsnc47Uxjfy
2ViHzfDn0FMjgbqxNjZMFKOrqmG74XFg4BdOByesr9OGRuazgxCWpEPU
=jY/l
-END PGP SIGNATURE End Message ---

Bug#1005992: marked as done (FTBFS: 'sys_siglist' undeclared)

[Debian Bug Tracking System]

Your message dated Fri, 18 Mar 2022 03:16:01 +
with message-id 
and subject line Bug#1005992: fixed in xemacs21 21.4.24-10
has caused the Debian Bug report #1005992,
regarding FTBFS: 'sys_siglist' undeclared
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.)


-- 
1005992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005992
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xemacs21
Version: 21.4.24-9
Severity: serious
Tags: ftbfs

Dear Maintainer,

xemacs21 fails to build from source on amd64:

process.c:1314:27: error: 'sys_siglist' undeclared (first use in this function)
 1314 | return (const char *) sys_siglist[signum];
  |   ^~~
process.c:1314:27: note: each undeclared identifier is reported only once for 
each function it appears in
make[3]: *** [GNUmakefile:58: process.o] Error 1

The glibc 2.32 release notes mention sys_siglist:

* The deprecated arrays sys_siglist, _sys_siglist, and sys_sigabbrev
  are no longer available to newly linked binaries, and their declarations
  have been removed from .  They are exported solely as
  compatibility symbols to support old binaries.  All programs should use
  strsignal instead.

https://lists.gnu.org/archive/html/info-gnu/2020-08/msg2.html

The complete build log is attached.

thank you,
Ryan
sbuild (Debian sbuild) 0.81.2 (31 January 2021) on w500.nardis.ca

+==+
| xemacs21 (amd64) Thu, 17 Feb 2022 21:40:17 + |
+==+

Package: xemacs21
Distribution: sid
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/sid-amd64-sbuild-638405a7-026f-4a93-8dd2-fe6f3baafde8' 
with '<>'
I: NOTICE: Log filtering will replace 'build/xemacs21-bajcVO/resolver-2uPGW7' 
with '<>'

+--+
| Update chroot|
+--+

Get:1 http://ftp.ca.debian.org/debian sid InRelease [165 kB]
Get:2 http://ftp.ca.debian.org/debian sid/contrib Sources.diff/Index [63.3 kB]
Get:3 http://ftp.ca.debian.org/debian sid/main Sources.diff/Index [63.6 kB]
Get:4 http://ftp.ca.debian.org/debian sid/main amd64 Packages.diff/Index [63.6 
kB]
Get:5 http://ftp.ca.debian.org/debian sid/contrib Sources 
T-2022-02-17-2005.30-F-2022-02-17-2005.30.pdiff [663 B]
Get:6 http://ftp.ca.debian.org/debian sid/main Sources 
T-2022-02-17-2005.30-F-2022-02-17-2005.30.pdiff [24.4 kB]
Get:5 http://ftp.ca.debian.org/debian sid/contrib Sources 
T-2022-02-17-2005.30-F-2022-02-17-2005.30.pdiff [663 B]
Get:7 http://ftp.ca.debian.org/debian sid/main amd64 Packages 
T-2022-02-17-2005.30-F-2022-02-17-2005.30.pdiff [26.1 kB]
Get:6 http://ftp.ca.debian.org/debian sid/main Sources 
T-2022-02-17-2005.30-F-2022-02-17-2005.30.pdiff [24.4 kB]
Get:7 http://ftp.ca.debian.org/debian sid/main amd64 Packages 
T-2022-02-17-2005.30-F-2022-02-17-2005.30.pdiff [26.1 kB]
Fetched 407 kB in 6s (70.0 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

+--+
| Fetch source files   |
+--+


Check APT
-

Checking available source versions...

Download source files with APT
--

Reading package lists...
Need to get 7233 kB of source archives.
Get:1 http://ftp.ca.debian.org/debian sid/main xemacs21 21.4.24-9 (dsc) [2142 B]
Get:2 http://ftp.ca.debian.org/debian sid/main xemacs21 21.4.24-9 (tar) [7198 
kB]
Get:3 http://ftp.ca.debian.org/debian sid/main xemacs21 21.4.24-9 (diff) [33.4 
kB]
Fetched 7233 kB in 0s (30.4 MB/s)
Download complete and in download only mode
I: NOTICE: Log filtering will replace 'build/xemacs21-bajcVO/xemacs21-21.4.24' 
with '<>'
I: NOTICE: Log filtering will replace 'build/xemacs21-bajcVO' with 
'<>'

+--+
| Install package build dependencies   |
+--

Bug#965888: marked as done (xemacs21-packages: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Fri, 18 Mar 2022 03:16:11 +
with message-id 
and subject line Bug#965888: fixed in xemacs21-packages 2009.02.17.dfsg.3-1
has caused the Debian Bug report #965888,
regarding xemacs21-packages: 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.)


-- 
965888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965888
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xemacs21-packages
Version: 2009.02.17.dfsg.2-5
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package xemacs21-packages 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: xemacs21-packages
Source-Version: 2009.02.17.dfsg.3-1
Done: Mark Brown 

We believe that the bug you reported is fixed in the latest version of
xemacs21-packages, 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.
Mark Brown  (supplier of updated xemacs21-packages 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, 18 Mar 2022 01:40:42 +
Source: xemacs21-packages
Architecture: source
Version: 2009.02.17.dfsg.3-1
Distribution: unstable
Urgency: low
Maintainer: Mark Brown 
Changed-By: Mark Brown 
Closes: 965888 992089 998930
Changes:
 xemacs21-packages (2009.02.17.dfsg.3-1) unstable; urgency=low
 .
   * Drop LValue.java with non-free disparaging to Sun license
 condition (closes: #992089).
   * Drop xoobr binary from source.
   * Add build-indep and build-arch targets (closes: #998930).
   * debhelper 13, dh_prep (closes: #965888).
   * Policy 4.5.1 (no changes).
Checksums-Sha1:
 e0d118a6f12f48e08d3f3babb65006c27eabc5f9 1855 
xemacs21-packages_2009.02.17.dfsg.3-1.dsc
 022bb675fb10f9f79961e492e589adf4fa78ee54 28876139 
xemacs21-packages_2009.02.17.dfsg.3.orig.tar.gz
 f5e765aff822f4b2047463875396f0177616d270 25484 
xemacs21-packages_2009.02.17.dfsg.3-1.debian.tar.xz
 75fa712dd0dfd70f35efd185d37159a397ae099d 6955 
xemacs21-packages_2009.02.17.dfsg.3-1_source.buildinfo
Checksums-Sha256:
 7ccad1f2beca9203e27a959a48f935fd4210e5789f8cbe210695e44a589d6253 1855 
xemacs21-packages_2009.02.17.dfsg.3-1.dsc
 bed6b788ef0e1082f33a9c56ea1b4aa23bc2bf8bea7630f9815e731b1132ea43 28876139 
xemacs21-packages_2009.02.17.dfsg.3.orig.tar.gz
 dd06379976d3f22810838554e77b07d2cc2fe42954d6ffa6665a215cc0bc8c77 25484 
xemacs21-packages_2009.02.17.dfsg.3-1.debian.tar.xz
 253589b29adf7db16c062e7d6a8c3abe93cdb38b4690c3d7505ad13fba983a2a 6955 
xemacs21-packages_2009.02.17.dfsg.3-1_source.buildinfo
Files:
 a710050e7c9992c3072f04e7c14909d8 1855 editors optional 
xemacs21-packages_2009.02.17.dfsg.3-1.dsc
 1f4d0e5270fd111fbb05bb2c44554621 28876139 editors optional 
xemacs21-packages_2009.02.17.dfsg.3.orig.tar.gz
 ccfea7a9fc5e467ce68cee7510f95432 25484 editors optional 
xemacs21-packages_2009.02.17.dfsg.3-1.debian.tar.xz
 52544793c5efee2aceca4d7beb703ca7 6955 editors optional 
xemacs21-packages_2009.02.17.dfsg.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFHBAEBCgAxFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmIz7hMTHGJyb29uaW

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

[Debian Bug Tracking System]

Your message dated Fri, 18 Mar 2022 02:02:07 +
with message-id 
and subject line [ftpmas...@ftp-master.debian.org: 
zlib_1.2.11.dfsg-3_source.changes ACCEPTED into unstable]
has caused the Debian Bug report #999292,
regarding zlib: 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.)


-- 
999292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zlib
Version: 1:1.2.11.dfsg-2
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 ---
--- Begin Message ---


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 18 Mar 2022 00:21:37 +
Source: zlib
Architecture: source
Version: 1:1.2.11.dfsg-3
Distribution: unstable
Urgency: low
Maintainer: Mark Brown 
Changed-By: Mark Brown 
Closes: 919598 1006799
Changes:
 zlib (1:1.2.11.dfsg-3) unstable; urgency=low
 .
   * Add build-arch and build-indep (#999292).
   * Bump debhelper requirement to current.
   * Add win32 to the list of files excluded from the DFSG
 tarball (closes: #919598).
   * Tighten matching for 32 bit architectures using patch from
 Helmut Grohne (closes: #1006799).
   * Policy 4.0.0 (no changes).
Checksums-Sha1:
 456e3a468792adbac0f0197c98f2292a4b13573f 2397 zlib_1.2.11.dfsg-3.dsc
 861fef48ca90e88eaddce83ad52f918ead4dcb1d 19380 zlib_1.2.11.dfsg-3.debian.tar.xz
 5f0d1357b6c3be8aecfcdb908c287c5f5d0a6107 7497 
zlib_1.2.11.dfsg-3_source.buildinfo
Checksums-Sha256:
 477f9aab100e0cd9690fbc577911c3d5907ddbbf1e8e89a0c16b1f88708eca32 2397 
zlib_1.2.11.dfsg-3.dsc
 4c1609b975b36712cfefb592f5a29b04c18ef2b46aded1e615772c386daa5bb6 19380 
zlib_1.2.11.dfsg-3.debian.tar.xz
 ae2852667ec8faf955f7dc051bba5a89f2c47289588e78ef4dc548ecf4b9ebd3 7497 
zlib_1.2.11.dfsg-3_source.buildinfo
Files:
 98ccd0f62d4dd58036a6d972259135a8 2397 libs optional zlib_1.2.11.dfsg-3.dsc
 c160f3de263f1abf7e6beeacc962b64a 19380 libs optional 
zlib_1.2.11.dfsg-3.debian.tar.xz
 a2ee5241f58957cb194cb8a8e4bed376 7497 libs optional 
zlib_1.2.11.dfsg-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFHBAEBCgAxFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmIz2EITHGJyb29uaWVA
ZGViaWFuLm9yZwAKCRAk1otyXVSH0BgYB/9kzoKHTBwwd7h8NmP2jhhsLQOoasFb
jc5/FOPA1ggCFlg1BUrwDLbB9gy83N7Lc3NCtGgnklgflfDrg/Xn+7fWgzPBe5xd
qiLHfYIHWCR/JkDgnIE1hpbupF3Agt9Xy7G27oGMsanV7pBlSQ+qemdw0MWrxmmI
6bjrTtLIQAC1lvmi36HN1qnpdyiwiU5IuEivZe5dRTzWiKo15rlh96K1kZ6X9P71
kL7VxB+PwFZEeRYgKU30F9lyURkU/fHOh0tnd+AaBkxUF9vB+W/VkHtDiR1b/0+M
BRrr7TjzphSkHnaRdPHdGy7UgdJzJc9ztezR1SXDYEYA8mnCuHmxfEv+
=/RMm
-END PGP SIGNATURE-


Thank you for your contribution to Debian.
--- End Message ---


signature.asc
Description: PGP signature
--- End Message ---

Bug#997750: marked as done (fort77: FTBFS: Total 1 error(s) encountered.)

[Debian Bug Tracking System]

Your message dated Fri, 18 Mar 2022 01:49:03 +
with message-id 
and subject line Bug#997750: fixed in fort77 1.15-12
has caused the Debian Bug report #997750,
regarding fort77: FTBFS: Total 1 error(s) encountered.
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.)


-- 
997750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997750
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fort77
Version: 1.15-11.1
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):
>  fakeroot debian/rules binary
> dh_testdir
> dh_testroot
> dh_prep
> dh_installdirs
> dh_installdirs: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
> make install DESTDIR=`pwd`/debian/fort77
> make[1]: Entering directory '/<>'
> (cd tests; ./test.pl -v)
> ../fort77 -c foo.f ... test successful.
> ../fort77 -c bar.F ..."bar.o" not generated by "( ../fort77 -c bar.F ) 
> >/dev/null 2>&1"
> ../fort77 -c -o gargle.o foo.f ./fort77 foo.f ./fort77 baz/bazfoo.f 
> ./fort77 -c baz/bazfoo.f ./fort77 -o bar.o -c baz/bazfoo.f 
> ./fort77 -o tscht foo.f ./fort77 -k foo.f ./fort77 -g -k foo.f 
> ./fort77 -c -f long.f ./fort77 -c foo.f && ../fort77 -c mainmiss.f && 
> ../fort77 -o foo foo.o mainmiss.o ./fort77 -c foo.f && ../fort77 -o foo 
> foo.o mainmiss.f ./fort77 synerr.f && touch gna ./fort77 ishift.f 
> ...if test ! -d subtest; then mkdir subtest; fi && cd subtest && ../../fort77 
> -g -c -o fooinclude.o -I ../ ../fooinclude.f ...Total 1 error(s) encountered.
> make[1]: *** [Makefile:17: test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/fort77_1.15-11.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: fort77
Source-Version: 1.15-12
Done: Mark Brown 

We believe that the bug you reported is fixed in the latest version of
fort77, 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.
Mark Brown  (supplier of updated fort77 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, 18 Mar 2022 01:16:57 +
Source: fort77
Architecture: source
Version: 1.15-12
Distribution: unstable
Urgency: low
Maintainer: Mark Brown 
Changed-By: Mark Brown 
Closes: 997750
Changes:
 fort77 (1.15-12) unstable; urgency=low
 .
   * Drop bar.F test, the version of cpp in unstable has some bad
 interaction with the test (closes: #997750).
   * debhelper 13 (no changes).
   * Policy 4.5.1 (no changes).
Checksums-Sha1:
 2ae2ccbf9305846f34020219681814b01290ce32 1295 fort77_1.15-12.dsc
 7d8c5b3189e35e76e442873fff5c95ab05bd9681 4553 fort77_1.15-12.diff.gz
 6517755a0a227602a9277b6c88826c528c9c0c2d 6938 fort77_1.15-12_source.buildinfo
Checksums-Sha256:
 50574bb7ad45a50ada77d9724b56eb934df183c1693ad304d9755de170d3787d 1295 
fort77_1.15-12.dsc
 fe8c43bfa53d3bdba6a45600a81e93992a5925651bded645d2cd37407be4bf5c 4553 
fort77_1.15-12.diff.gz
 19d3fc2c88758d241637f56434f86db1f85203939df7290f5e5753ab7c8f2aeb 6938 
fort77_1.15-12_source.buildinfo
Files:
 e53b9df4b6d30f91259a641e0a75d56e 1295 devel optional fort77_1.15-12.dsc
 3c4a7f5255fb363a5e8ce3d19fcc01a8 4553 devel optional fort77_1.15-12.diff.gz
 a7fa737fef58204eb9b8ba2226ff7530 6938 devel optional 
fort77_1.15-12_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFHBAEBCgAxFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmIz4PkTHGJyb29uaWVA
ZGViaWFuLm9yZwAKCRAk1otyXVSH0AxZB/9+0KH+bK+3piHc0DOOmhLGUNMMOHhg
W4XcnGl17+HmB5rCfPAkFqYyTXid4uCAXVs

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

[Debian Bug Tracking System]

Your message dated Fri, 18 Mar 2022 01:33:41 +
with message-id 
and subject line Bug#999007: fixed in ftnchek 3.3.1-6
has caused the Debian Bug report #999007,
regarding ftnchek: 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.)


-- 
999007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ftnchek
Version: 3.3.1-5
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: ftnchek
Source-Version: 3.3.1-6
Done: Mark Brown 

We believe that the bug you reported is fixed in the latest version of
ftnchek, 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.
Mark Brown  (supplier of updated ftnchek 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, 18 Mar 2022 01:09:37 +
Source: ftnchek
Architecture: source
Version: 3.3.1-6
Distribution: unstable
Urgency: low
Maintainer: Mark Brown 
Changed-By: Mark Brown 
Closes: 999007
Changes:
 ftnchek (3.3.1-6) unstable; urgency=low
 .
   * Add build-arch and build indep targets (closes: #999007).
   * Policy 4.5.1 (no changes).
   * debhelper 13 (no changes).
Checksums-Sha1:
 7a8c01b53047ddfe463b38e9d2134dda196d516d 1354 ftnchek_3.3.1-6.dsc
 d61193564d70851ca31cd34944f3cd53638e41c5 6135 ftnchek_3.3.1-6.diff.gz
 4964600351c089d92a5a32b9127ae35aca5ca469 6867 ftnchek_3.3.1-6_source.buildinfo
Checksums-Sha256:
 ff2fa3f60a43b0fcfbac3908a42e69faa4850d047a7647ce1d85c601adbac0da 1354 
ftnchek_3.3.1-6.dsc
 a7b710ba773f22bebad6ee1ac90c5426db5d6b4fde3c961cc4c20ed123182744 6135 
ftnchek_3.3.1-6.diff.gz
 d3e1cbea47c9c8322d170ee6bf9ec16d52acc19d9d492d2ff0d3417d0fb85ec5 6867 
ftnchek_3.3.1-6_source.buildinfo
Files:
 49954d15642a8d0a13f0e63f8598b691 1354 devel extra ftnchek_3.3.1-6.dsc
 6fd12e83d4dcb9707f8fd4b943368931 6135 devel extra ftnchek_3.3.1-6.diff.gz
 561b99514dc64758c86403246665e1f3 6867 devel extra 
ftnchek_3.3.1-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFHBAEBCgAxFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmIz3UgTHGJyb29uaWVA
ZGViaWFuLm9yZwAKCRAk1otyXVSH0KWtB/9ZOjsE6VuF/Yo3SlFMnm6BAt1C0fIh
+znmL1+1dk1IPyEmINQHEzfZDp3Njh9AoG6NCIZVEFPQFxLRW39NlGDn0Hbr/r2N
fhonTFPdwYPjUqL0qkf+UzxVf/g67usTEuc0Pz66e/oGQhYudb4QeBW/V38Gwa8A
Xr5cgD86viGkCaeYrFgJFqcZA23x8hs7o1oQLgO9nf8SOqHt3FIUti/dejoJ1Pkq
E32fBgiooJXjazvkg81HzPR6Lp2u9EdTrS3oxpMdhRUqnR6iiUpWDNuxZ38HDKtO
0IqiFC5fRk/O3X08KJQpjlxir44S6Mf62ow5kC6yjcDnweoQft6ilvg+
=AvTG
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Fri, 18 Mar 2022 01:19:25 +
with message-id 
and subject line Bug#999155: fixed in mm 1.4.2-7
has caused the Debian Bug report #999155,
regarding mm: 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.)


-- 
999155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mm
Version: 1.4.2-6
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: mm
Source-Version: 1.4.2-7
Done: Mark Brown 

We believe that the bug you reported is fixed in the latest version of
mm, 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.
Mark Brown  (supplier of updated mm 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, 18 Mar 2022 00:55:28 +
Source: mm
Architecture: source
Version: 1.4.2-7
Distribution: unstable
Urgency: low
Maintainer: Mark Brown 
Changed-By: Mark Brown 
Closes: 999155
Changes:
 mm (1.4.2-7) unstable; urgency=low
 .
   * Add build-indep and build-arch targets (closes: #999155).
   * debhelper 13 (no changes).
Checksums-Sha1:
 b861b1e8c93404acc8c80d5114608d37974d8ee5 1359 mm_1.4.2-7.dsc
 c0d0c2beda7dece838b9d546ecd6e87ac385d2ef 4551 mm_1.4.2-7.diff.gz
 6c9470593d0abed77f26bbb6c558f456cf9d874c 6847 mm_1.4.2-7_source.buildinfo
Checksums-Sha256:
 ebb554948b2320bef2394ee541a680f2fd3822fac576a5a6a4a6b431a9ccbc9c 1359 
mm_1.4.2-7.dsc
 d50464161e5be14956ee012681721b39a54b36fae274b1609d79282256253a55 4551 
mm_1.4.2-7.diff.gz
 d2eefb83fa90a40a52ede444a7ea23c0cb78d11943d46aaade8ee206ced839e4 6847 
mm_1.4.2-7_source.buildinfo
Files:
 eb9965f7a9d61988ee840298774a6de2 1359 devel optional mm_1.4.2-7.dsc
 8b47050fcdac4d54afa3b13ef9b4b231 4551 devel optional mm_1.4.2-7.diff.gz
 119100d197596436567210ecadb60599 6847 devel optional 
mm_1.4.2-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFHBAEBCgAxFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmIz2kgTHGJyb29uaWVA
ZGViaWFuLm9yZwAKCRAk1otyXVSH0DInCACF2+/E3z9H6x4LadpO2Ze3YXj+fecK
IXEA0YUtkXLot9kyJfeCNoeGIJKrYqqX4Jqpqesvt49ucoqzknWruXytc8tbTVKM
vehoC0Nz5Sd4o8pFmAFm2N08Ea6RMKMjC+s3otdcsMJ3Ma/KBxRE/Oi2AzjsFK1d
hjxIky1dgRJnlhYm4IGxL5/0mLXo2f9yY5OkEHeT0f+VhnozwOgriFs3AZEsNm1g
W/Pn39KlkG97b311KdsIsKmS3136H/KhlqEhLKOO76SWP8ebpDo5Eb0RkZlgDT6r
75T8GvjQ8yQzQd0wgc1LhxHECn50mK7b+JndVJLqTAwobA+cg4oBbZsJ
=ISlb
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Fri, 18 Mar 2022 00:34:21 +
with message-id 
and subject line Bug#965885: fixed in x86info 
1.31~pre0.8052aabdd159bc9050e7dc264f33782c5acce05f-2
has caused the Debian Bug report #965885,
regarding x86info: 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.)


-- 
965885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: x86info
Version: 1.31~pre0.8052aabdd159bc9050e7dc264f33782c5acce05f-1
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package x86info 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: x86info
Source-Version: 1.31~pre0.8052aabdd159bc9050e7dc264f33782c5acce05f-2
Done: Mark Brown 

We believe that the bug you reported is fixed in the latest version of
x86info, 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.
Mark Brown  (supplier of updated x86info 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, 18 Mar 2022 00:09:08 +
Source: x86info
Architecture: source
Version: 1.31~pre0.8052aabdd159bc9050e7dc264f33782c5acce05f-2
Distribution: unstable
Urgency: low
Maintainer: Mark Brown 
Changed-By: Mark Brown 
Closes: 965885
Changes:
 x86info (1.31~pre0.8052aabdd159bc9050e7dc264f33782c5acce05f-2) unstable; 
urgency=low
 .
   * Update to debhelper 13 (closes: #965885).
   * Update to Python 3.
Checksums-Sha1:
 f351c4064fc67771711f37a3b7d74255240ea6bf 1766 
x86info_1.31~pre0.8052aabdd159bc9050e7dc264f33782c5acce05f-2.dsc
 eacce6c3bb9bebae4ee185fe526b85d2d5c8bf01 4339 
x86info_1.31~pre0.8052aabdd159bc9050e7dc264f33782c5acce05f-2.diff.gz
 46ae9e40b317f0a0637041769497860d3ed4 8273 
x86info_1.31~pre0.8052aabdd159bc9050e7dc264f33782c5acce05f-2_source.buildinfo
Checksums-Sha256:
 707be95af3eb955689c2f4ba8500207f7a5eb934fd7f6b187b09abccb076aed6 1766 
x86info_1.31~pre0.8052aabdd159bc9050e7dc264f33782c5acce05f-2.dsc
 f1963c142bc9ed461ae3b001eb667b59fabcec748e35fa03ac740058a9f2481e 4339 
x86info_1.31~pre0.8052aabdd159bc9050e7dc264f33782c5acce05f-2.diff.gz
 27a0c9868569b5a8b2d8b58cd0275978aaca5ee3373e9004e0b04516ab612d9d 8273 
x86info_1.31~pre0.8052aabdd159bc9050e7dc264f33782c5acce05f-2_source.buildinfo
Files:
 7498a0d1c972160db4a0f0bd074c600a 1766 admin extra 
x86info_1.31~pre0.8052aabdd159bc9050e7dc264f33782c5acce05f-2.dsc
 71b0fe295225cc27a39b2e835c8c98f2 4339 admin extra 
x86info_1.31~pre0.8052aabdd159bc9050e7dc264f33782c5acce05f-2.diff.gz
 09850be6dea8bd89cda5771fe0006bde 8273 admin extra 
x86info_1.31~pre0.8052aabdd159bc9050e7dc264f33782c5acce05f-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFHBAEBCgAxFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmIzz2QTHGJyb29uaWVA
ZGViaWFuLm9yZwAKCRAk1otyXVSH0IhcCACCKlDYbwPAKwhAzT8sPqIpZFK7Sek3
tQPJWYuGbcEBBxur2oEaJjPV+jgd2mK6O6PZ0YhTsam1Ac7GIkZ2YNr0BQl1MtaT
qKTeCYaCuK2pWaquU9d76hhda/B2skuDmfhz8UffMup85qgO5m8ZSNkCSceBSCKO
UjuNEyenp2jmIgj96pU2FHva1smCZa/k1QlOaJZaA5D6zBsAnyMVQqc/TANsasts
vjoChYrha3FbZoeEDune+pHZhJL9sl2PblPQKvJ

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

[Debian Bug Tracking System]

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

> severity 953530 serious
Bug #953530 [samba-common-bin] samba-common-bin: post-install fails with "lock 
directory /run/samba does not exist"
Severity set to 'serious' from 'normal'
> found 953530 2:4.13.14+dfsg-1+b2
Bug #953530 [samba-common-bin] samba-common-bin: post-install fails with "lock 
directory /run/samba does not exist"
Marked as found in versions samba/2:4.13.14+dfsg-1.
> thanks
Stopping processing here.

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

Processed: tagging 1005840

[Debian Bug Tracking System]

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

> tags 1005840 + fixed-upstream
Bug #1005840 [claws-mail-themes] claws-mail-themes: includes non-free content 
(CC-by-nc-sa-v3.0)
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#1007880: python-xarray: FTBFS generating docs: nbsphinx no module named ipython_genutils

[Jérémy Lal]

Source: python-xarray
Version: 2022.03.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

It fails in a clean sid chroot with:

Could not import extension nbsphinx (exception: No module named 
'ipython_genutils')


Jérémy

Bug#1007823: scotch breaks opm-grid autopkgtest: Failed to build dune-autopkgtest

[Markus Blatt]

Hi,

will look into this in more detail tomorrow, but it seems like the problem
might be in dune-common. The error is triggered during a CMake run that
uses FindMETIS.cmake (shipped with libdune-common-dev) and that fails.

Markus

Processed: coinor-ipopt: diff for NMU version 3.11.9-2.3

[Debian Bug Tracking System]

Processing control commands:

> tags 965459 + patch
Bug #965459 [src:coinor-ipopt] coinor-ipopt: Removal of obsolete debhelper 
compat 5 and 6 in bookworm
Added tag(s) patch.

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

Bug#965459: coinor-ipopt: diff for NMU version 3.11.9-2.3

[Adrian Bunk]

Control: tags 965459 + patch

Dear maintainer,

I've prepared an NMU for coinor-ipopt (versioned as 3.11.9-2.3) and 
uploaded it to DELAYED/15. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru coinor-ipopt-3.11.9/debian/changelog coinor-ipopt-3.11.9/debian/changelog
--- coinor-ipopt-3.11.9/debian/changelog	2019-06-16 13:51:12.0 +0300
+++ coinor-ipopt-3.11.9/debian/changelog	2022-03-17 23:41:30.0 +0200
@@ -1,3 +1,10 @@
+coinor-ipopt (3.11.9-2.3) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/compat: 5 -> 7. (Closes: #965459)
+
+ -- Adrian Bunk   Thu, 17 Mar 2022 23:41:30 +0200
+
 coinor-ipopt (3.11.9-2.2) unstable; urgency=medium
 
   * Non-maintainer upload
diff -Nru coinor-ipopt-3.11.9/debian/compat coinor-ipopt-3.11.9/debian/compat
--- coinor-ipopt-3.11.9/debian/compat	2014-10-01 15:42:17.0 +0300
+++ coinor-ipopt-3.11.9/debian/compat	2022-03-17 23:41:30.0 +0200
@@ -1 +1 @@
-5
+7

Processed: closing 1004748

[Debian Bug Tracking System]

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

> close 1004748 1.48.0-1
Bug #1004748 [src:guestfs-tools] guestfs-tools ftbfs with new ocaml
Marked as fixed in versions guestfs-tools/1.48.0-1.
Bug #1004748 [src:guestfs-tools] guestfs-tools ftbfs with new ocaml
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1007773: uwsgi: FTBS with /usr/bin/ld: cannot find -lpcre2-8

[Adrian Bunk]

On Thu, Mar 17, 2022 at 10:25:06AM +0100, Alexandre Rossi wrote:
> Hi,
> 
> > /usr/bin/ld: cannot find -lpcre2-8: No such file or directory
> 
> I've pushed the necessary fix.
> https://salsa.debian.org/uwsgi-team/uwsgi/-/commit/0955366dcf19b7ec9a0134eab1e81ec216d12a96

This change wasn't necessary (but is harmless).

The actual bug (#1007254) was fixed in apache2-dev.

> Thanks,
> 
> Alex

cu
Adrian

Bug#1005570: marked as done (gnome-sudoku: FTBFS: ../data/meson.build:5:0: ERROR: Function does not take positional arguments.)

[Debian Bug Tracking System]

Your message dated Thu, 17 Mar 2022 21:19:22 +
with message-id 
and subject line Bug#1005570: fixed in gnome-sudoku 1:42.0-1
has caused the Debian Bug report #1005570,
regarding gnome-sudoku: FTBFS: ../data/meson.build:5:0: ERROR: Function does 
not take positional arguments.
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.)


-- 
1005570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-sudoku
Version: 1:40.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- --bindir=games
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu --bindir=games
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-sudoku
> Project version: 40.2
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) 
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.38
> C++ compiler for the host machine: c++ (gcc 11.2.0 "c++ (Debian 11.2.0-16) 
> 11.2.0")
> C++ linker for the host machine: c++ ld.bfd 2.38
> Vala compiler for the host machine: valac (valac 0.54.6)
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency gee-0.8 found: YES 0.20.5
> Run-time dependency gio-2.0 found: YES 2.70.3
> Run-time dependency glib-2.0 found: YES 2.70.3
> Run-time dependency gtk+-3.0 found: YES 3.24.31
> Run-time dependency json-glib-1.0 found: YES 1.6.6
> Run-time dependency qqwing found: YES 1.3.4
> Run-time dependency threads found: YES
> Configuring config.h using configuration
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources)
> 
> ../data/meson.build:5:0: ERROR: Function does not take positional arguments.
> 
> A full log can be found at 
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
> ==> meson-logs/meson-log.txt <==
> Build started at 2022-02-12T22:46:33.332771
> Main binary: /usr/bin/python3
> Build Options: -Dprefix=/usr -Dbindir=games -Dlibdir=lib/x86_64-linux-gnu 
> -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain 
> -Dwrap_mode=nodownload
> Python system: Linux
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-sudoku
> Project version: 40.2
> Sanity testing C compiler: cc
> Is cross compiler: False.
> Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,-z,defs
> Sanity check compile stdout:
> 
> -
> Sanity check compile stderr:
> 
> -
> Running test binary command: 
> /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) 
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.38
> Sanity testing C++ compiler: c++
> Is cross compiler: False.
> Sanity check compiler command line: c++ sanitycheckcpp.cc -o 
> sanitycheckcpp.exe -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-O1 
> -Wl,-z,defs
> Sanity check compile stdout:
> 
> -
> Sanity check compile stderr:
> 
> -
> Running test binary command: 
> /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckcpp.exe
> C++ compiler for the host machine: c++ (gcc 11.2.0 "c++ (Debian 11.2.0-16) 
> 11.2.0")
> C++ linker for the host machine: c++ ld.bfd 2.38
> Running compile:
> Working directory:  /tmp/tmp_xu92z0u
> Command line:  valac /tmp/tmp_xu92z0u/testfile.vala -C 
> 
> Code:
>  class MesonSanityCheck : Object { }
> Compiler stdout:
>  
> Compiler stderr:
>  
> Vala compiler for the host machine: valac (valac 0.54.6)
> Sanity testing C compiler: cc
> Is cross compiler: False.
> Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g 
> -O2 -ffi

Bug#1007149: marked as done (texmaker 5.1.2+dfsg-1 has file that is also in texmaker-data)

[Debian Bug Tracking System]

Your message dated Thu, 17 Mar 2022 20:51:02 +
with message-id 
and subject line Bug#1007149: fixed in texmaker 5.1.2+dfsg-2
has caused the Debian Bug report #1007149,
regarding texmaker 5.1.2+dfsg-1 has file that is also in texmaker-data
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.)


-- 
1007149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texmaker
Version: 5.0.3-1+b4
Severity: important

Dear Maintainer,

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

   * What led up to the situation?

Preparing to unpack .../09-texmaker_5.1.2+dfsg-1_amd64.deb ...
Unpacking texmaker (5.1.2+dfsg-1) over (5.0.3-1+b4) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-2ZQBqC/09-texmaker_5.1.2+dfsg-1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/pixmaps/texmaker.png', which is also in 
package texmaker-data 5.0.3-1

Preparing to unpack .../texmaker-data_5.1.2+dfsg-1_all.deb ...
Unpacking texmaker-data (5.1.2+dfsg-1) ...
Preparing to unpack .../texmaker_5.1.2+dfsg-1_amd64.deb ...
Unpacking texmaker (5.1.2+dfsg-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/texmaker_5.1.2+dfsg-1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/pixmaps/texmaker.png', which is also in 
package texmaker-data 5.1.2+dfsg-1
Errors were encountered while processing:
 /var/cache/apt/archives/texmaker_5.1.2+dfsg-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)



   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Downgrading texmaker and texmaker-data solved the issue temporarily

   * What was the outcome of this action?
   * What outcome did you expect instead?

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


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

Kernel: Linux 5.17.0-rc7+ (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages texmaker depends on:
ii  libc6 2.33-7
ii  libqt5core5a [qtbase-abi-5-15-2]  5.15.2+dfsg-15
ii  libqt5gui55.15.2+dfsg-15
ii  libqt5network55.15.2+dfsg-15
ii  libqt5printsupport5   5.15.2+dfsg-15
ii  libqt5script5 5.15.2+dfsg-2
ii  libqt5widgets55.15.2+dfsg-15
ii  libqt5xml55.15.2+dfsg-15
ii  libstdc++612-20220302-1
ii  libsynctex2   2021.20210626.59705-1
ii  texmaker-data 5.0.3-1

Versions of packages texmaker recommends:
ii  aspell0.60.8-4
ii  asymptote 2.79+ds-1
ii  ghostscript   9.55.0~dfsg-3
ii  hunspell-en-au [hunspell-dictionary]  1:2020.12.07-2
ii  hunspell-en-gb [hunspell-dictionary]  1:7.2.0-2
pn  latex-beamer  
ii  netpbm2:10.0-15.4
ii  psutils   1.17.dfsg-4
ii  texlive-lang-english  2021.20220204-1
ii  texlive-latex-extra   2021.20220204-1

Versions of packages texmaker suggests:
pn  texlive-lang-all  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: texmaker
Source-Version: 5.1.2+dfsg-2
Done: Andreas Tille 

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated texmaker 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, 17 Mar 2022 18:07:54 +0100
Source: texmaker
Architecture: source
Version: 5.1.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Andreas Tille 
Closes: 1007149
Changes:
 texmaker (5.1.2+dfsg-2)

Bug#997231: marked as done (nfstrace: FTBFS: header_window.cpp:77:82: error: format ‘%d’ expects argument of type ‘int’, but argument 5 has type ‘time_t’ {aka ‘long int’} [-Werror=format=])

[Debian Bug Tracking System]

Your message dated Thu, 17 Mar 2022 19:49:59 +
with message-id 
and subject line Bug#997231: fixed in nfstrace 0.4.3.2+git20200805+b220d04-2.1
has caused the Debian Bug report #997231,
regarding nfstrace: FTBFS: header_window.cpp:77:82: error: format ‘%d’ expects 
argument of type ‘int’, but argument 5 has type ‘time_t’ {aka ‘long int’} 
[-Werror=format=]
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.)


-- 
997231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nfstrace
Version: 0.4.3.2+git20200805+b220d04-2
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):
> cd /<>/obj-x86_64-linux-gnu/analyzers/src/watch && /usr/bin/c++ 
> -Dwatch_EXPORTS -I/<>/src -I/usr/include/tirpc 
> -I/<>/analyzers/src/watch -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 -pedantic 
> -Wall -Werror -Wextra -Wno-invalid-offsetof 
> -Wno-error=address-of-packed-member -fPIC -fvisibility=hidden -fPIC -MD -MT 
> analyzers/src/watch/CMakeFiles/watch.dir/nc_windows/header_window.cpp.o -MF 
> CMakeFiles/watch.dir/nc_windows/header_window.cpp.o.d -o 
> CMakeFiles/watch.dir/nc_windows/header_window.cpp.o -c 
> /<>/analyzers/src/watch/nc_windows/header_window.cpp
> /<>/analyzers/src/watch/nc_windows/header_window.cpp: In member 
> function ‘void HeaderWindow::update()’:
> /<>/analyzers/src/watch/nc_windows/header_window.cpp:77:82: 
> error: format ‘%d’ expects argument of type ‘int’, but argument 5 has type 
> ‘time_t’ {aka ‘long int’} [-Werror=format=]
>77 | mvwprintw(_window, HEADER::ELAPSED_LINE, FIRST_CHAR_POS, "Elapsed 
> time:  \t %d days; %d:%d:%d times",
>   |   
>   ~^
>   |   
>|
>   |   
>int
>   |   
>   %ld
>78 |   shift_time / SECINDAY, shift_time % SECINDAY / 
> SECINHOUR, shift_time % SECINHOUR / SECINMIN, shift_time % SECINMIN);
>   |   ~   
> 
>   |  |
>   |  time_t {aka long int}
> /<>/analyzers/src/watch/nc_windows/header_window.cpp:77:91: 
> error: format ‘%d’ expects argument of type ‘int’, but argument 6 has type 
> ‘time_t’ {aka ‘long int’} [-Werror=format=]
>77 | mvwprintw(_window, HEADER::ELAPSED_LINE, FIRST_CHAR_POS, "Elapsed 
> time:  \t %d days; %d:%d:%d times",
>   |   
>~^
>   |   
> |
>   |   
> int
>   |   
>%ld
>78 |   shift_time / SECINDAY, shift_time % SECINDAY / 
> SECINHOUR, shift_time % SECINHOUR / SECINMIN, shift_time % SECINMIN);
>   |  
> ~ 
>   ||
>   |time_t 
> {aka long int}
> /<>/analyzers/src/watch/nc_windows/header_window.cpp:77:94: 
> error: format ‘%d’ expects argument of type ‘int’, but argument 7 has type 
> ‘time_t’ {aka ‘long int’} [-Werror=format=]
>77 | mvwprintw(_window, HEADER::ELAPSED_LINE, FIRST_CHAR_POS, "Elapsed 
> time:  \t %d days; %d:%d:%d times",
>   |   
>   ~^
>   |   
>|
>   |   
>int
>   |   
>   %ld
>78 |   shift_time / SECINDAY, shift_time % SECINDAY / 
> SECINHOUR, shift_time % SECINHOUR / SECINMIN, 

Processed: Re: nfstrace: FTBFS: header_window.cpp:77:82: error: format ‘%d’ expects argument of type ‘int’, but argument 5 has type ‘time_t’ {aka ‘long int’} [-Werror=format=]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch pending
Bug #997231 [src:nfstrace] nfstrace: FTBFS: header_window.cpp:77:82: error: 
format ‘%d’ expects argument of type ‘int’, but argument 5 has type ‘time_t’ 
{aka ‘long int’} [-Werror=format=]
Added tag(s) patch and pending.

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

Bug#997231: nfstrace: FTBFS: header_window.cpp:77:82: error: format ‘%d’ expects argument of type ‘int’, but argument 5 has type ‘time_t’ {aka ‘long int’} [-Werror=format=]

[Gianfranco Costamagna]

control: tags -1 patch pending

The attached debdiff from Ubuntu is going in.

G.diff -Nru nfstrace-0.4.3.2+git20200805+b220d04/debian/changelog 
nfstrace-0.4.3.2+git20200805+b220d04/debian/changelog
--- nfstrace-0.4.3.2+git20200805+b220d04/debian/changelog   2021-08-26 
06:08:31.0 -0400
+++ nfstrace-0.4.3.2+git20200805+b220d04/debian/changelog   2022-03-17 
13:21:02.0 -0400
@@ -1,3 +1,11 @@
+nfstrace (0.4.3.2+git20200805+b220d04-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * debian/patches/0001-analyzers-fix-a-couple-format-errors.patch: Fix
+-Werror=format build errors (LP: #1965155, Closes: #997231).
+
+ -- Nick Rosbrook   Thu, 17 Mar 2022 13:21:02 
-0400
+
 nfstrace (0.4.3.2+git20200805+b220d04-2) unstable; urgency=medium
 
   [ Aurelien Jarno ]
diff -Nru 
nfstrace-0.4.3.2+git20200805+b220d04/debian/patches/0001-analyzers-fix-a-couple-format-errors.patch
 
nfstrace-0.4.3.2+git20200805+b220d04/debian/patches/0001-analyzers-fix-a-couple-format-errors.patch
--- 
nfstrace-0.4.3.2+git20200805+b220d04/debian/patches/0001-analyzers-fix-a-couple-format-errors.patch
 1969-12-31 19:00:00.0 -0500
+++ 
nfstrace-0.4.3.2+git20200805+b220d04/debian/patches/0001-analyzers-fix-a-couple-format-errors.patch
 2022-03-16 12:08:15.0 -0400
@@ -0,0 +1,45 @@
+Description: Fix -Werror=format build errors
+Author: Nick Rosbrook 
+Forwarded: https://github.com/epam/nfstrace/pull/51
+Last-Update: 2022-03-16
+---
+From af1472cfd88a724e7208e0c2534a47d7f40ff2ab Mon Sep 17 00:00:00 2001
+From: Nick Rosbrook 
+Date: Wed, 16 Mar 2022 11:31:00 -0400
+Subject: [PATCH] analyzers: fix a couple format errors
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+A couple mvwprintw() calls result in build errors like:
+
+error: format ‘%d’ expects argument of type ‘int’, but argument 5 has type 
‘time_t’ {aka ‘long int’} [-Werror=format=]
+
+Update these calls to use the correct format specifiers.
+---
+ analyzers/src/watch/nc_windows/header_window.cpp | 2 +-
+ analyzers/src/watch/nc_windows/statistics_window.cpp | 2 +-
+ 2 files changed, 2 insertions(+), 2 deletions(-)
+
+--- a/analyzers/src/watch/nc_windows/header_window.cpp
 b/analyzers/src/watch/nc_windows/header_window.cpp
+@@ -74,7 +74,7 @@
+ time_t shift_time  = actual_time - _start_time;
+ /* tm starts with 0 month and 1900 year*/
+ mvwprintw(_window, HEADER::DATE_LINE, FIRST_CHAR_POS, "Date: \t %d.%d.%d 
\t Time: %d:%d:%d  ", t->tm_mday, t->tm_mon + 1, t->tm_year + 1900, t->tm_hour, 
t->tm_min, t->tm_sec);
+-mvwprintw(_window, HEADER::ELAPSED_LINE, FIRST_CHAR_POS, "Elapsed time:  
\t %d days; %d:%d:%d times",
++mvwprintw(_window, HEADER::ELAPSED_LINE, FIRST_CHAR_POS, "Elapsed time:  
\t %ld days; %ld:%ld:%ld times",
+   shift_time / SECINDAY, shift_time % SECINDAY / SECINHOUR, 
shift_time % SECINHOUR / SECINMIN, shift_time % SECINMIN);
+ wrefresh(_window);
+ }
+--- a/analyzers/src/watch/nc_windows/statistics_window.cpp
 b/analyzers/src/watch/nc_windows/statistics_window.cpp
+@@ -153,7 +153,7 @@
+ }
+ if(canWrite(line))
+ {
+-mvwprintw(_window, line - (_scrollOffset.at(_activeProtocol)), 
FIRST_CHAR_POS + 25, "%d", m);
++mvwprintw(_window, line - (_scrollOffset.at(_activeProtocol)), 
FIRST_CHAR_POS + 25, "%ld", m);
+ }
+ line++;
+ for(unsigned int j = _activeProtocol->getGroupBegin(i); j < 
_activeProtocol->getGroupBegin(i + 1); j++)
diff -Nru nfstrace-0.4.3.2+git20200805+b220d04/debian/patches/series 
nfstrace-0.4.3.2+git20200805+b220d04/debian/patches/series
--- nfstrace-0.4.3.2+git20200805+b220d04/debian/patches/series  2021-08-26 
06:08:31.0 -0400
+++ nfstrace-0.4.3.2+git20200805+b220d04/debian/patches/series  2022-03-16 
11:59:13.0 -0400
@@ -1 +1,2 @@
+0001-analyzers-fix-a-couple-format-errors.patch
 tirpc.patch

Bug#1006052: haskell-*: FTBFS: * Lexical error! The character '#' does not fit here.

[Gianfranco Costamagna]

control: close -1
control: archive -1

Hello, all these bugs are fixed by gtk2hs-buildtools/0.13.8.0-2

Gianfranco

Processed: Re: haskell-*: FTBFS: * Lexical error! The character '#' does not fit here.

[Debian Bug Tracking System]

Processing control commands:

> close -1
Bug #1006052 [src:haskell-pango] haskell-pango: FTBFS: hspango.i:1: (column 1) 
[FATAL] Lexical error!  The character '#' does not fit here.
Marked Bug as done
> archive -1
Bug #1006052 {Done: Gianfranco Costamagna } 
[src:haskell-pango] haskell-pango: FTBFS: hspango.i:1: (column 1) [FATAL] 
Lexical error!  The character '#' does not fit here.
archived 1006052 to archive/52 (from 1006052)

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

Bug#1007820: marked as done (python-xmlschema: autopkgtest needs update for new version of elementpath: output changed)

[Debian Bug Tracking System]

Your message dated Thu, 17 Mar 2022 19:19:19 +
with message-id 
and subject line Bug#1007820: fixed in python-xmlschema 1.10.0-1
has caused the Debian Bug report #1007820,
regarding python-xmlschema: autopkgtest needs update for new version of 
elementpath: output changed
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.)


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

Source: python-xmlschema
Version: 1.4.2-1
Severity: serious
X-Debbugs-CC: elementp...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:elementpath

Dear maintainer(s),

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


   passfail
elementpathfrom testing2.5.0-1
python-xmlschema   from testing1.4.2-1
all others from testingfrom testing

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

Currently this regression is blocking the migration of elementpath to 
testing [1]. Of course, elementpath shouldn't just break your 
autopkgtest (or even worse, your package), but it seems to me that the 
change in elementpath was intended and your package needs to update to 
the new situation.


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from elementpath should really 
add a versioned Breaks on the unfixed version of (one of your) 
package(s). Note: the Breaks is nice even if the issue is only in the 
autopkgtest as it helps the migration software to figure out the right 
versions to combine in the tests.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-xmlschema/20034165/log.gz

==
FAIL: test_assertion_facet 
(tests.validators.test_simple_types.TestXsd11SimpleTypes)

--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.46fb83c0/downtmp/build.V4y/src/tests/validators/test_simple_types.py", 
line 201, in test_assertion_facet
self.assertIn("wrong type  for operand", 
str(ctx.exception))
AssertionError: "wrong type  for operand" not found in 
'failed validating DateTime(2000, 1, 1, 12, 0, 0) with 
XsdAssertionFacet(test="$value > \'1999-12-31T23:59:59\'"):\n\nReason: 
\'>\' operator at line 1, column 8: [err:XPTY0004] \'>\' not supported 
between instances of \'DateTime\' and \'str\'\n\nSchema:\n\n 
http://www.w3.org/2001/XMLSchema"; test="$value 
> \'1999-12-31T23:59:59\'" />\n'


--
Ran 850 tests in 26.223s

FAILED (failures=1, skipped=4)
autopkgtest [08:10:57]: test command1



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-xmlschema
Source-Version: 1.10.0-1
Done: Christian Kastner 

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

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

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

Debian distribution maintenance software
pp.
Christian Kastner  (supplier of updated python-xmlschema 
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, 17 Feb 2022 16:11:28 +0100
Source: python-xmlschema
Architecture: source
Version: 1.10.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Christian Kastner 
Closes: 1007820
Changes:
 python-xmlschema (1.10.0-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #1007820)
 - Add python3-jinja2 to dependencies
 - Update package des

Bug#995178: glib2.0: autopkgtest failure: glib/memory-monitor-dbus.test (sometimes) times out

[Simon McVittie]

Control: severity -1 normal

On Thu, 17 Mar 2022 at 19:32:39 +0100, Paul Gevers wrote:
> On Mon, 27 Sep 2021 15:47:52 +0100 Simon McVittie  wrote:
> > I'm reporting this with a non-RC severity to avoid disrupting the libffi
> > transition, because if a retry succeeds, we will be able to nudge that
> > transition through without uploading a new version of glib2.0 and resetting
> > the migration countdown. However, it's really RC (as per the release team's
> > RC criteria) so we should fix this after the transition has gone through.
> 
> That transition finished some time ago. So let's raise the severity.

I marked the affected test as flaky in glib 2.70.0-2, so if it sometimes
fails, it's still a bug but should not be disrupting buildd builds or
autopkgtest gating.

It seems to be succeeding in practice, but I haven't looked into whether
anything has changed that would fix it, so leaving it open.

smcv

Processed: Re: Bug#995178: glib2.0: autopkgtest failure: glib/memory-monitor-dbus.test (sometimes) times out

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #995178 [src:glib2.0] glib2.0: autopkgtest failure: 
glib/memory-monitor-dbus.test (sometimes) times out
Severity set to 'normal' from 'serious'

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

Processed: bug 1006779 is forwarded to https://github.com/fredrik-johansson/arb/issues/404

[Debian Bug Tracking System]

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

> forwarded 1006779 https://github.com/fredrik-johansson/arb/issues/404
Bug #1006779 [src:flint-arb] flint-arb: FTBFS on mips64el: erfinvException 
(FLINT memory_manager). Unable to allocate memory (145776024000).
Set Bug forwarded-to-address to 
'https://github.com/fredrik-johansson/arb/issues/404'.
> thanks
Stopping processing here.

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

Bug#1007829: [pkg-netfilter-team] Bug#1007829: arptables - Fails to install: Too many levels of symbolic links

[Alberto Molina Coballes]

Thanks for reporting Bastian,

I've reproduced the issue, but it seems not related to dpkg, arptables
fails to install when iptables isn't installed. I must review and
update arptables postinst script where alternatives are used.

Alberto

Processed: Re: glib2.0: autopkgtest failure: glib/memory-monitor-dbus.test (sometimes) times out

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #995178 [src:glib2.0] glib2.0: autopkgtest failure: 
glib/memory-monitor-dbus.test (sometimes) times out
Severity set to 'serious' from 'important'

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

Bug#984359: marked as done (systemc: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Thu, 17 Mar 2022 17:33:59 +
with message-id 
and subject line Bug#984359: fixed in systemc 2.3.3-5.1
has caused the Debian Bug report #984359,
regarding systemc: ftbfs with GCC-11
to be marked as done.

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

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


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

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

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

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

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

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

  apt-get -t=experimental install g++ 

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

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

[...]
  _ZN5sc_dt10sc_lv_baseC1ERKS0_@Base 2.3.3
- _ZN5sc_dt10sc_lv_baseC1Ei@Base 2.3.3
+#MISSING: 2.3.3-5# _ZN5sc_dt10sc_lv_baseC1Ei@Base 2.3.3
  _ZN5sc_dt10sc_lv_baseC1INS_10sc_bv_baseEEERKNS_8sc_proxyIT_EE@Base 2.3.3
  _ZN5sc_dt10sc_lv_baseC2EPKc@Base 2.3.3
  _ZN5sc_dt10sc_lv_baseC2EPKci@Base 2.3.3
  _ZN5sc_dt10sc_lv_baseC2ERKS0_@Base 2.3.3
- _ZN5sc_dt10sc_lv_baseC2Ei@Base 2.3.3
+#MISSING: 2.3.3-5# _ZN5sc_dt10sc_lv_baseC2Ei@Base 2.3.3
  _ZN5sc_dt10sc_lv_baseC2INS_10sc_bv_baseEEERKNS_8sc_proxyIT_EE@Base 2.3.3
  _ZN5sc_dt10sc_lv_baseD0Ev@Base 2.3.3
  _ZN5sc_dt10sc_lv_baseD1Ev@Base 2.3.3
@@ -160,7 +160,7 @@
  _ZN5sc_dt11sc_unsigned10concat_setEyi@Base 2.3.3
  _ZN5sc_dt11sc_unsigned14set_packed_repEPj@Base 2.3.3
  (arch-bits=64)_ZN5sc_dt11sc_unsigned16convert_2C_to_SMEv@Base 2.3.3
- (arch-bits=64)_ZN5sc_dt11sc_unsigned22convert_SM_to_2C_to_SMEv@Base 2.3.3
+#MISSING: 2.3.3-5# 
(arch-bits=64)_ZN5sc_dt11sc_unsigned22convert_SM_to_2C_to_SMEv@Base 2.3.3
  _ZN5sc_dt11sc_unsigned3setEi@Base 2.3.3
  _ZN5sc_dt11sc_unsigned4scanERSi@Base 2.3.3
  _ZN5sc_dt11sc_unsigned5clearEi@Base 2.3.3
@@ -351,7 +351,7 @@
  _ZN5sc_dt12vec_from_strEiiPjPKcNS_9sc_numrepE@Base 2.3.3
  
_ZN5sc_dt13b_and_assign_INS_10sc_bv_baseENS_10sc_lv_baseEEERT_RNS_8sc_proxyIS3_EERKNS5_IT0_EE@Base
 2.3.3
  
_ZN5sc_dt13b_and_assign_INS_10sc_lv_baseES1_EERT_RNS_8sc_proxyIS2_EERKNS4_IT0_EE@Base
 2.3.3
- 
_ZN5sc_dt13b_xor_assign_INS_10sc_bv_baseENS_10sc_lv_baseEEERT_RNS_8sc_proxyIS3_EERKNS5_IT0_EE@Base
 2.3.3
+#MISSING: 2.3.3-5# 
_ZN5sc_dt13b_xor_assign_INS_10sc_bv_baseENS_10sc_lv_baseEEERT_RNS_8sc_proxyIS3_EERKNS5_IT0_EE@Base
 2.3.3
  
_ZN5sc_dt13b_xor_assign_INS_10sc_lv_baseES1_EERT_RNS_8sc_proxyIS2_EERKNS4_IT0_EE@Base
 2.3.3
  _ZN5sc_dt13sc_fxnum_fast4castEv@Base 2.3.3
  _ZN5sc_dt13sc_fxnum_fast4scanERSi@Base 2.3.3
@@ -2854,8 +2854,10 @@
  _ZN7sc_core31SC_ID_SIMULATION_TIME_OVERFLOW_E@Base 2.3.3
  _ZN7sc_core31SC_ID_TRACING_CLOSE_EMPTY_FILE_E@Base 2.3.3
  _ZN7sc_core31SC_ID_VECTOR_INIT_CALLED_TWICE_E@Base 2.3.3
- 
_ZN7sc_core31sc_api_version_2_3_3_cxx201402LIXadL_ZNS_34SC_DISABLE_VIRTUAL_BIND_UNDEFINED_C1ENS_16sc_writer_policyE@Base
 2.3.3
- 
_ZN7sc_core31sc_api_version_2_3_3_cxx201402LIXadL_ZNS_34SC_DISABLE_VIRTUAL_BIND_UNDEFINED_C2ENS_16sc_writer_policyE@Base
 2.3.3
+#MISSING: 2.3.3-5# 
_ZN7sc_core31sc_api_version_2_3_3_cxx201402LIXadL_ZNS_34SC_DISABLE_VIRTUAL_BIND_UNDEFINED_C1ENS_16sc_writer_policyE@Base
 2.3.3
+#MISSING: 2.3.3-5# 
_ZN7sc_core31sc_api_version_2_3_3_cxx201402LIXadL_ZNS_34SC_DISABLE_VIRTUAL_BIND_UNDEFINED_C2ENS_16sc_writer_policyE@Base
 2.3.3
+ 
_ZN7sc_core31sc_api_versi

Bug#942502: src:isc-dhcp: please switch to bundled BIND 9 libraries

[Santiago Ruano Rincón]

El 17/03/22 a las 15:50, Ondřej Surý escribió:
> Thank you,
> 
> you are probably also aware of the fact that 4.4.3 is the last isc-dhcp 
> release
> that will contain client and relay part and all releases after that will 
> contain
> only the server component. But I thought it won’t hurt to mention this...

Yes, I am aware of that. I'll include a note about this on the NEWS
files.

Cheers,

 -- S


signature.asc
Description: PGP signature

Processed: tagging 974117

[Debian Bug Tracking System]

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

> tags 974117 + ftbfs
Bug #974117 [src:rust-image] rust-image: FTBFS build-depends on 
librust-tiff-0.3+default-dev
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: Re: haskell-*: FTBFS: * Lexical error! The character '#' does not fit here.

[Debian Bug Tracking System]

Processing control commands:

> close -1
Bug #1006072 [src:haskell-glib] haskell-glib: FTBFS: glib-object.i:1: (column 
1) [FATAL] Lexical error!  The character '#' does not fit here.
Marked Bug as done
> archive -1
Bug #1006072 {Done: Gianfranco Costamagna } 
[src:haskell-glib] haskell-glib: FTBFS: glib-object.i:1: (column 1) [FATAL] 
Lexical error!  The character '#' does not fit here.
archived 1006072 to archive/72 (from 1006072)

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

Processed: Re: haskell-*: FTBFS: * Lexical error! The character '#' does not fit here.

[Debian Bug Tracking System]

Processing control commands:

> close -1
Bug #1006070 [src:haskell-gtk3] haskell-gtk3: FTBFS: hsgtk.i:1: (column 1) 
[FATAL] Lexical error!  The character '#' does not fit here.
Marked Bug as done
> archive -1
Bug #1006070 {Done: Gianfranco Costamagna } 
[src:haskell-gtk3] haskell-gtk3: FTBFS: hsgtk.i:1: (column 1) [FATAL] Lexical 
error!  The character '#' does not fit here.
archived 1006070 to archive/70 (from 1006070)

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

Processed: Re: haskell-*: FTBFS: * Lexical error! The character '#' does not fit here.

[Debian Bug Tracking System]

Processing control commands:

> close -1
Bug #1006059 [src:haskell-gtk] haskell-gtk: FTBFS: hsgtk.i:1: (column 1) 
[FATAL] Lexical error!  The character '#' does not fit here.
Marked Bug as done
> archive -1
Bug #1006059 {Done: Gianfranco Costamagna } 
[src:haskell-gtk] haskell-gtk: FTBFS: hsgtk.i:1: (column 1) [FATAL] Lexical 
error!  The character '#' does not fit here.
archived 1006059 to archive/59 (from 1006059)

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

Processed: Re: haskell-*: FTBFS: * Lexical error! The character '#' does not fit here.

[Debian Bug Tracking System]

Processing control commands:

> close -1
Bug #1005657 [src:haskell-gio] haskell-gio: FTBFS: gio.i:1: (column 1) [FATAL] 
Lexical error!  The character '#' does not fit here.
Marked Bug as done
> archive -1
Bug #1005657 {Done: Gianfranco Costamagna } 
[src:haskell-gio] haskell-gio: FTBFS: gio.i:1: (column 1) [FATAL] Lexical 
error!  The character '#' does not fit here.
archived 1005657 to archive/57 (from 1005657)

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

Processed: Re: haskell-*: FTBFS: * Lexical error! The character '#' does not fit here.

[Debian Bug Tracking System]

Processing control commands:

> close -1
Bug #1005676 [src:haskell-cairo] haskell-cairo: FTBFS: cairo-gtk2hs.i:1: 
(column 1) [FATAL] Lexical error!  The character '#' does not fit here.
Marked Bug as done
> archive -1
Bug #1005676 {Done: Gianfranco Costamagna } 
[src:haskell-cairo] haskell-cairo: FTBFS: cairo-gtk2hs.i:1: (column 1) [FATAL] 
Lexical error!  The character '#' does not fit here.
archived 1005676 to archive/76 (from 1005676)

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

Bug#1005657: haskell-*: FTBFS: * Lexical error! The character '#' does not fit here.

[Gianfranco Costamagna]

control: close -1
control: archive -1

Hello, all these bugs are fixed by gtk2hs-buildtools/0.13.8.0-2 

Gianfranco

Bug#942502: src:isc-dhcp: please switch to bundled BIND 9 libraries

[Ondřej Surý]

Thank you,

you are probably also aware of the fact that 4.4.3 is the last isc-dhcp release
that will contain client and relay part and all releases after that will contain
only the server component. But I thought it won’t hurt to mention this...

Cheers,
Ondrej
--
Ondřej Surý (He/Him)
ond...@sury.org

> On 17. 3. 2022, at 15:43, Santiago Ruano Rincón  wrote:
> 
> Control: tags -1 + pending
> 
> On Mon, 24 Jan 2022 10:53:06 +0100 =?utf-8?b?T25kxZllaiBTdXLDvQ==?= 
>  wrote:
>> Source: isc-dhcp
>> Followup-For: Bug #942502
>> Control: severity -1 serious
>> 
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA512
>> 
>> Dear Maintainer,
>> 
>> BIND 9.11 will go EOL with the next release and ISC DHCP team is making 
>> switch
>> to maintain the bundled libraries in ISC DHCP on their own.  This means there
>> will be only option now - use the bundled libraries as they will be 
>> maintained
>> inside the ISC DHCP project.
> …
> 
> Thanks for the input Ondřej,
> 
> I am doing the relevant changes in the master-pre-4.4.3 git branch. This
> should be part of the next upload.
> 
> Cheers,
> 
> -- S



signature.asc
Description: Message signed with OpenPGP

Bug#1007821: marked as done (node-fs-extra: autopkgtest regression: No test files found: "lib/empty/__tests__/")

[Debian Bug Tracking System]

Your message dated Thu, 17 Mar 2022 14:46:23 +
with message-id 
and subject line Bug#1007821: fixed in node-fs-extra 10.0.1+~9.0.13-2
has caused the Debian Bug report #1007821,
regarding node-fs-extra: autopkgtest regression: No test files found: 
"lib/empty/__tests__/"
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.)


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

Source: node-fs-extra
Version: 10.0.1+~9.0.13-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
node-fs-extra  from testing10.0.1+~9.0.13-1
all others from testingfrom testing

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

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


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

Paul

[1] https://qa.debian.org/excuses.php?package=node-fs-extra

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-fs-extra/20034176/log.gz

# Using ./package.(json|yaml)
# Node module name is fs-extra
# Build files found: # Test files found: test
test.js
# Files/dir to be installed from source: test
test.js # Copy test files
# Copy debian/tests/pkg-js content
'debian/tests/pkg-js' -> 
'/tmp/autopkgtest-lxc.35e10ml4/downtmp/autopkgtest_tmp/smokepWshiG/debian/tests/pkg-js'
'debian/tests/pkg-js/test' -> 
'/tmp/autopkgtest-lxc.35e10ml4/downtmp/autopkgtest_tmp/smokepWshiG/debian/tests/pkg-js/test'

'@types/fs-extra' linked into node_modules
# Searching module in /usr/lib/nodejs/fs-extra
# Searching module in /usr/lib/*/nodejs/fs-extra
# Searching module in /usr/share/nodejs/fs-extra
# Found /usr/share/nodejs/fs-extra
# Searching files to link in /usr/share/nodejs/fs-extra
'./lib' -> '/usr/share/nodejs/fs-extra/lib'
'./package.json' -> '/usr/share/nodejs/fs-extra/package.json'
# Launch debian/tests/pkg-js/test with sh -ex
+ set -e
+ OK=lib/empty lib/mkdirs lib lib/output-file lib/json lib/ensure 
lib/util lib/path-exists lib/remove

+ mocha lib/empty/__tests__/
Error: No test files found: "lib/empty/__tests__/"
autopkgtest [08:12:05]: test pkg-js-autopkgtest



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-fs-extra
Source-Version: 10.0.1+~9.0.13-2
Done: Yadd 

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

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

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-fs-extra 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, 17 Mar 2022 15:16:32 +0100
Source: node-fs-extra
Architecture: source
Version: 10.0.1+~9.0.13-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1007821
Changes:
 node-fs-extra (10.0.1+~9.0.13-2) unstable; urgency=medium
 .
   * Team upload
   * Add test directories in debian/tests/pkg-js/files, fixes autopkgtest
 (Closes: #1007821)
Checksums-Sha1: 
 5bc8ea176b11149f69570a5221b01526475af52e 2587 
node-fs-extra_10.0.1+~9.0.13-2.dsc
 9e5d8a37c8bfba3ba5fd1595d8a98ad3dc055874 4588 
node-fs-extra_10.0.1+~9.0.13-2.debian.tar.xz
Checksums-Sha256: 
 2e4a386aa129b88851c1bbed2727fab8e70ab97eebd856f7fbfb7a281c85c397 2587 
node-fs-extra_10.0.1+~9.0.13-2.dsc
 35662bf7f010c35c41320cc6f4b7dce8f5fafc5b21b5d03c53849415356744e1 4588 
node-fs-extra_10.0.1+~9.0.13-2.debian.tar.xz
Files: 
 2fa8e62398e991b865303b6c7df949af 2587 javascript optional 
node-fs-extra_10.0.1+~9.0.13-2.dsc
 e612789b64d4e283ca445d28ca2350e9 4588 javascript optional 
nod

Bug#942502: src:isc-dhcp: please switch to bundled BIND 9 libraries

[Santiago Ruano Rincón]

Control: tags -1 + pending

On Mon, 24 Jan 2022 10:53:06 +0100 =?utf-8?b?T25kxZllaiBTdXLDvQ==?= 
 wrote:
> Source: isc-dhcp
> Followup-For: Bug #942502
> Control: severity -1 serious
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Dear Maintainer,
> 
> BIND 9.11 will go EOL with the next release and ISC DHCP team is making switch
> to maintain the bundled libraries in ISC DHCP on their own.  This means there
> will be only option now - use the bundled libraries as they will be maintained
> inside the ISC DHCP project.
…

Thanks for the input Ondřej,

I am doing the relevant changes in the master-pre-4.4.3 git branch. This
should be part of the next upload.

Cheers,

 -- S


signature.asc
Description: PGP signature

Processed: Re: src:isc-dhcp: please switch to bundled BIND 9 libraries

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #942502 [src:isc-dhcp] src:isc-dhcp: please switch to bundled BIND 9 
libraries
Added tag(s) pending.

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

Processed: Bug#1007821 marked as pending in node-fs-extra

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1007821 [src:node-fs-extra] node-fs-extra: autopkgtest regression: No test 
files found: "lib/empty/__tests__/"
Added tag(s) pending.

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

Bug#1007821: marked as pending in node-fs-extra

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-fs-extra/-/commit/1cea46e604ff608744b952e2ab98730a63d8e58c


Fix autopkgtest

Closes: #1007821


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1007821

Bug#1005505: accountsservice: FTBFS: ./obj-x86_64-linux-gnu/meson-private/tmpvj3vxj0b/testfile.c:17: undefined reference to `setutxdb'

[s3v]

Dear Maintainer,

actual error is:

> ...
> ../data/meson.build:31:5: ERROR: Function does not take positional arguments.
> ...

recent upload of accountservice/22.07.5-1 contains the upstream fix for this 
[1][2]
I've built successfully your package in a sid chroot environement and
reproducible-builds confirm that this FTBFS is gone away [3]

Kind Regards

[1]
https://cgit.freedesktop.org/accountsservice/commit/?id=ac9b14f1c1bbca413987d0bbfeaad05804107e9a
[2] 
https://sources.debian.org/src/accountsservice/22.07.5-1/data/meson.build/#L35
[3] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/accountsservice.html

Bug#1007829: arptables - Fails to install: Too many levels of symbolic links

[Bastian Blank]

Package: arptables
Version: 0.0.5-3
Severity: grave

arptables fails to install, using dpkg 1.21.2:

| Unpacking arptables (0.0.5-3) ...
| Setting up arptables (0.0.5-3) ...
| update-alternatives: using /usr/sbin/arptables-legacy to provide 
/usr/sbin/arptables (arptables) in auto mode
| update-alternatives: error: cannot stat file '/usr/sbin/arptables': Too many 
levels of symbolic links
| dpkg: error processing package arptables (--configure):
|  installed arptables package post-installation script subprocess returned 
error exit status 2
| Processing triggers for man-db (2.10.1-1) ...
| Errors were encountered while processing:
|  arptables
| E: Sub-process /usr/bin/dpkg returned an error code (1)

In the end we have some self-links:

| lrwxrwxrwx 1 root root19 Mar 17 12:32 /usr/sbin/arptables -> 
/usr/sbin/arptables
| lrwxrwxrwx 1 root root27 Mar 17 12:32 /usr/sbin/arptables-restore -> 
/usr/sbin/arptables-restore
| lrwxrwxrwx 1 root root24 Mar 17 12:32 /usr/sbin/arptables-save -> 
/usr/sbin/arptables-save

Bastian

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

Kernel: Linux 5.16.0-3-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 arptables depends on:
ii  libc6  2.33-7

arptables recommends no packages.

arptables suggests no packages.

Bug#1007773: marked as done (uwsgi: FTBS with /usr/bin/ld: cannot find -lpcre2-8)

[Debian Bug Tracking System]

Your message dated Thu, 17 Mar 2022 12:49:51 +
with message-id 
and subject line Bug#1007773: fixed in uwsgi 2.0.20-3
has caused the Debian Bug report #1007773,
regarding uwsgi: FTBS with /usr/bin/ld: cannot find -lpcre2-8
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.)


-- 
1007773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007773
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uwsgi
Version: 2.0.20-2.2
Severity: serious
Tags: ftbfs
Justification: Policy 4.9

Dear Maintainer,

uwsgi fails to build from source in a sbuild chroot with the following error.

/usr/share/apr-1.0/build/libtool  --mode=link --tag=disable-static 
x86_64-linux-gnu-gcc -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -lpcre2-8 
-L/usr/lib/x86_64-linux-gnu/libpcre2-8.so.0-o apache2/mod_Ruwsgi.la  
-L/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux-gnu -lapr-1 -laprutil-1 
-rpath /usr/lib/apache2/modules -module -avoid-versionapache2/mod_Ruwsgi.lo
libtool: link: x86_64-linux-gnu-gcc -shared  -fPIC -DPIC  
apache2/.libs/mod_Ruwsgi.o   -lpcre2-8 
-L/usr/lib/x86_64-linux-gnu/libpcre2-8.so.0 -L/usr/lib/x86_64-linux-gnu 
/usr/lib/x86_64-linux-gnu/libapr-1.so /usr/lib/x86_64-linux-gnu/libaprutil-1.so 
 -Wl,--as-needed -Wl,-z -Wl,relro -Wl,-z -Wl,now   -pthread -Wl,-soname 
-Wl,mod_Ruwsgi.so -o apache2/.libs/mod_Ruwsgi.so
/usr/bin/ld: cannot find -lpcre2-8: No such file or directory
collect2: error: ld returned 1 exit status
apxs:Error: Command failed with rc=65536
.
make: *** [debian/rules:517: debian/stamp-libapache2-mod-ruwsgi] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Thanks,

Alex

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

Kernel: Linux 5.10.0-12-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: uwsgi
Source-Version: 2.0.20-3
Done: Jonas Smedegaard 

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

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

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated uwsgi 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, 17 Mar 2022 13:20:51 +0100
Source: uwsgi
Architecture: source
Version: 2.0.20-3
Distribution: unstable
Urgency: medium
Maintainer: uWSGI packaging team 
Changed-By: Jonas Smedegaard 
Closes: 1007773
Changes:
 uwsgi (2.0.20-3) unstable; urgency=medium
 .
   [ Alexandre Rossi ]
   * fix building apache plugin following apache move to pcre2;
 closes: bug#1007773
 .
   [ Jonas Smedegaard ]
   * acknowledge NMUs;
 thanks to Antonio Terceiro
   * tighten lintian overrides
Checksums-Sha1:
 5bbdd150454db8aa0d5f7372d9aef06a9ffa46aa 7043 uwsgi_2.0.20-3.dsc
 89adce8066135d5d5f47b8f6d4a90842015a61cd 62588 uwsgi_2.0.20-3.debian.tar.xz
 ee953897a91e7771503db12a3b1777820b270a06 37782 uwsgi_2.0.20-3_amd64.buildinfo
Checksums-Sha256:
 99368f3dd82df283b8a5f648b74a00616283db72cdbdf9a10ac01b42e61a0e56 7043 
uwsgi_2.0.20-3.dsc
 a269ce889e51ecdc1eb40a948f122e257c51273df233d48f13fc539b9908719d 62588 
uwsgi_2.0.20-3.debian.tar.xz
 87afee06bacfef76a31e166f4e92ccb621491804a7a5fd9e5be152e132f8003a 37782 
uwsgi_2.0.20-3_amd64.buildinfo
Files:
 541aebb77a64355fd6d6d8d7921085ee 7043 httpd optional uwsgi_2.0.20-3.dsc
 32e1da436d041d69019fbbdb67501c04 62588 httpd optional 
uwsgi_2.0.20-3.debian.tar.xz
 24dc643acfb21d31c5fdaaa5d2ec2e9b 37782 httpd optional 
uwsgi_2.0.20-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmIzK3UACgkQLHwxRsGg
ASFF+g/9FpLMUesvwIEN6co/BedXZIQIdTcT3yJ2GzYyY8ptew8v+fnl1Kuy39U6
D4N1AvIyzLR+uUkRvwhOATH1E11NORJEdisZMAlsy7tlkNuCkHYrQxo4POxiAw8t
5B5t3F7sjjE7oRBjM6UBRTw5bGGOuJIu0bAUI+z81Ga+DGMCclzsp7hbGp06eXkF
IHZ6Ip9wyK5sX8VzpdW/7uGNXznh/RhpWPvQ80XrTSkh4uSi/8qoItlTYYI9/geC
9LZBofjqUhOAIGRjPQfOMlcwuUh4dDjZl44rQDyIP1y3mvSqbJ6bu8L4

Bug#1001801: marked as done (dogtag-pki: hits autopkgtest timeout on powerful workers)

[Debian Bug Tracking System]

Your message dated Thu, 17 Mar 2022 12:33:42 +
with message-id 
and subject line Bug#1001801: fixed in dogtag-pki 11.0.3-3
has caused the Debian Bug report #1001801,
regarding dogtag-pki: hits autopkgtest timeout on powerful workers
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.)


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

Source: dogtag-pk
Version: 11.0.0-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky timeout

Dear maintainer(s),

Your package has an autopkgtest, great. However, because of some failure
"caused" by another package, I looked into the history of your 
autopkgtest [1] and I noticed it fails regularly on amd64 and armhf 
because it hits the autopkgtest timeout after 2:47 hours.


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

In this case I noticed that at least the failures on amd64 that I looked 
at all happened on ci-worker13, which is our 48 core, 256 GB machine, 
while the test on other amd64 workers passed (as far as I checked). 
Similar, our armhf worker is also powerful: 160 core, 255 GB. Is there 
anything in the test that you can think of that can't handle so much 
resources?


The last entry in one of the amd64 logs is this (maybe add at least a 
timeout on calls like that):

INFO: Creating /etc/pki/pki-tomcat/Catalina/localhost/kra.xml
INFO: Waiting for web application to start

If you need help to investigate this on the workers in question, don't 
hesitate to reach out.


Paul

[1] https://ci.debian.net/packages/d/dogtag-pki/


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: dogtag-pki
Source-Version: 11.0.3-3
Done: Timo Aaltonen 

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated dogtag-pki 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, 17 Mar 2022 14:10:45 +0200
Source: dogtag-pki
Built-For-Profiles: noudeb
Architecture: source
Version: 11.0.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Closes: 1001801
Changes:
 dogtag-pki (11.0.3-3) unstable; urgency=medium
 .
   * force-request-timeout-default.diff: Another attempt to set
 request_timeout. (Closes: #1001801)
Checksums-Sha1:
 88ab77c154ea44d434d9a3687271908eab0a4073 3789 dogtag-pki_11.0.3-3.dsc
 861f6ec620a980b7f71e104a3f18d77642588346 42972 
dogtag-pki_11.0.3-3.debian.tar.xz
 908b28e17d97ec9a8a1995eb65e5483680e99ae8 13254 
dogtag-pki_11.0.3-3_source.buildinfo
Checksums-Sha256:
 bfc77f6f228fb246ae5addce4ca8e5ad9140c02c6c93d530688551d6390f52b6 3789 
dogtag-pki_11.0.3-3.dsc
 5f0e5f56c4f1510068733bae980ee1ae5687fc7c62cf3b8ee02dc55cbf7910ae 42972 
dogtag-pki_11.0.3-3.debian.tar.xz
 c1811d6e1ab40aca52483a4936d06653eeb1759fb97ffb87d71139411af6df9a 13254 
dogtag-pki_11.0.3-3_source.buildinfo
Files:
 3a62eb286edd262c60e4641656bf2c69 3789 java optional dogtag-pki_11.0.3-3.dsc
 2d40d02392aba42281aec48d361c5825 42972 java optional 
dogtag-pki_11.0.3-3.debian.tar.xz
 fab90242678ecb10ce114d82dada8494 13254 java optional 
dogtag-pki_11.0.3-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmIzJVgACgkQy3AxZaiJ
hNx0MA//fXtXKQlr5aJCYKKS7V3pj+PKBClOqpqmangr7excI/5D9xBjSqD8uR5w
QMRPM2iI2vHFDpPO3xxxWLkTmDtUzQRP6P4oAs7v8/vfqHdnjR87+aYeFavoRDFp
2blKdrL+VcHQhUHogGrijiTVCu4zGGXvvyZjeiI46h2rVUxDyEpu1vzdg/8YvuC4
L0wHiQEaJpNHPKWwl3WDCogih+qZ7b2+iU7ZTS7VsIZPMwX2y9sR7bvOW3PoNEQL
KoAzKT3otYwEv5qOzoznY2Xn76TAKFXFBhx4GWbKg6D9K/In2hyk22qyFAHQTuym
kxAWBcapoToyMQzxwLsIse3Hz8mF0NdF7Yvg/Z7YPUqfnwo6CdxafA8dwj/RxifA
Cx3joDjNxW+Mz0vj

Bug#1007828: faketime: autopkgtest regression

[Paul Gevers]

Source: faketime
Version: 0.9.10-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
faketime   from testing0.9.10-1
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/f/faketime/20035213/log.gz

Running the test program with no faked time specified
$ LD_PRELOAD=/usr/lib/x86_64-linux-gnu/faketime/libfaketime.so.1 ./timetest
pthread_cond_timedwait: CLOCK_REALTIME test
(Intentionally sleeping 1 second...)
pthread_cond_timedwait: CLOCK_MONOTONIC test
(Intentionally sleeping 1 second...)
(If this test hangs for more than a few seconds, please report
 your glibc version and system details as FORCE_MONOTONIC_FIX
 issue at https://github.com/wolfcw/libfaketime)
Blocking signal 10
time() : Current date and time: Wed Mar 16 09:11:31 2022
time(NULL) : Seconds since Epoch  : 1647421891
ftime(): Current date and time: Wed Mar 16 09:11:31 2022
(Intentionally sleeping 2 seconds...)
gettimeofday() : Current date and time: Wed Mar 16 09:11:33 2022
Caught signal 10
clock_gettime(): Current date and time: Wed Mar 16 09:11:33 2022
stat(): mod. time of file './timetest': Wed Mar 16 09:11:27 2022

=

Running the test program with absolute date 2003-01-01 10:00:05 specified
$ LD_PRELOAD=/usr/lib/x86_64-linux-gnu/faketime/libfaketime.so.1 
FAKETIME="2003-01-01 10:00:05" ./timetest

pthread_cond_timedwait: CLOCK_REALTIME test
(Intentionally sleeping 1 second...)
pthread_cond_timedwait: CLOCK_MONOTONIC test
(Intentionally sleeping 1 second...)
(If this test hangs for more than a few seconds, please report
 your glibc version and system details as FORCE_MONOTONIC_FIX
 issue at https://github.com/wolfcw/libfaketime)
Blocking signal 10
time() : Current date and time: Wed Jan  1 10:00:05 2003
time(NULL) : Seconds since Epoch  : 1041415205
ftime(): Current date and time: Wed Jan  1 10:00:05 2003
(Intentionally sleeping 2 seconds...)
gettimeofday() : Current date and time: Wed Jan  1 10:00:05 2003
Caught signal 10
Caught signal 10
clock_gettime(): Current date and time: Wed Jan  1 10:00:05 2003
stat(): mod. time of file './timetest': Wed Jan  1 10:00:05 2003

=

Running the test program with START date @2005-03-29 14:14:14 specified
$ LD_PRELOAD=/usr/lib/x86_64-linux-gnu/faketime/libfaketime.so.1 
FAKETIME="@2005-03-29 14:14:14" ./timetest

pthread_cond_timedwait: CLOCK_REALTIME test
(Intentionally sleeping 1 second...)
pthread_cond_timedwait: CLOCK_MONOTONIC test
(Intentionally sleeping 1 second...)
(If this test hangs for more than a few seconds, please report
 your glibc version and system details as FORCE_MONOTONIC_FIX
 issue at https://github.com/wolfcw/libfaketime)
Blocking signal 10
time() : Current date and time: Tue Mar 29 14:14:16 2005
time(NULL) : Seconds since Epoch  : 1112105656
ftime(): Current date and time: Tue Mar 29 14:14:16 2005
(Intentionally sleeping 2 seconds...)
gettimeofday() : Current date and time: Tue Mar 29 14:14:18 2005
Caught signal 10
clock_gettime(): Current date and time: Tue Mar 29 14:14:18 2005
stat(): mod. time of file './timetest': Tue Mar 29 14:14:03 2005

=

Running the test program with 10 days negative offset specified
LD_PRELOAD=/usr/lib/x86_64-linux-gnu/faketime/libfaketime.so.1 
FAKETIME="-10d" ./timetest

pthread_cond_timedwait: CLOCK_REALTIME test
(Intentionally sleeping 1 second...)
pthread_cond_timedwait: CLOCK_MONOTONIC test
(Intentionally sleeping 1 second...)
(If this test hangs for more than a few seconds, please report
 your glibc version and system details as FORCE_MONOTONIC_FIX
 issue at https://github.com/wolfcw/libfaketime)
Blocking signal 10
time() : Current date and time: Sun Mar  6 09:11:43 2022
time(NULL) : Seconds since Epoch  : 1646557903
ftime(): Current date and time: Sun Mar  6 09:11:43 2022
(Intentionally sleeping 2 seconds...)
gettimeofday() : Current date and time: Sun Mar  6 09:11:45 2022
Caught signal 10
clock_gettime(): Current date and time: Sun Mar  6 09:11:45 2022
stat(): mod. time of fi

Bug#1007827: asdf-astropy breaks gwcs autopkgtest: cannot import name 'assert_models_equal' from 'asdf_astropy.converters.transform.tests.test_transform'

[Paul Gevers]

Source: asdf-astropy, gwcs
Control: found -1 asdf-astropy/0.2.0-1
Control: found -1 gwcs/0.18.0-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
asdf-astropy   from testing0.2.0-1
gwcs   from testing0.18.0-2
all others from testingfrom testing

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

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


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

Paul

[1] https://qa.debian.org/excuses.php?package=asdf-astropy

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gwcs/20058761/log.gz

= test session starts 
==

platform linux -- Python 3.9.10, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
rootdir: /tmp/autopkgtest-lxc.788b562b/downtmp/autopkgtest_tmp
plugins: remotedata-0.3.3, openfiles-0.5.0, astropy-header-0.2.0, 
cov-3.0.0, filter-subpackage-0.1.1, asdf-2.10.1, arraydiff-0.5.0, 
doctestplus-0.12.0, mock-3.6.1, hypothesis-6.36.0

collected 971 items / 1 error / 970 selected

 ERRORS 

 ERROR collecting converters/tests/test_wcs.py 
_
ImportError while importing test module 
'/usr/lib/python3/dist-packages/gwcs/converters/tests/test_wcs.py'.

Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.9/importlib/__init__.py:127: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
/usr/lib/python3/dist-packages/gwcs/converters/tests/test_wcs.py:15: in 

from asdf_astropy.converters.transform.tests.test_transform import 
(  # noqa: E402
E   ImportError: cannot import name 'assert_models_equal' from 
'asdf_astropy.converters.transform.tests.test_transform' 
(/usr/lib/python3/dist-packages/asdf_astropy/converters/transform/tests/test_transform.py)
=== short test summary info 


ERROR converters/tests/test_wcs.py
 Interrupted: 1 error during collection 

=== 1 error in 1.32s 
===

autopkgtest [06:00:01]: test command1



OpenPGP_signature
Description: OpenPGP digital signature

Processed: asdf-astropy breaks gwcs autopkgtest: cannot import name 'assert_models_equal' from 'asdf_astropy.converters.transform.tests.test_transform'

[Debian Bug Tracking System]

Processing control commands:

> found -1 asdf-astropy/0.2.0-1
Bug #1007827 [src:asdf-astropy, src:gwcs] asdf-astropy breaks gwcs autopkgtest: 
cannot import name 'assert_models_equal' from 
'asdf_astropy.converters.transform.tests.test_transform'
Marked as found in versions asdf-astropy/0.2.0-1.
> found -1 gwcs/0.18.0-2
Bug #1007827 [src:asdf-astropy, src:gwcs] asdf-astropy breaks gwcs autopkgtest: 
cannot import name 'assert_models_equal' from 
'asdf_astropy.converters.transform.tests.test_transform'
Marked as found in versions gwcs/0.18.0-2.

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

Bug#1007826: asdf-astropy: autopkgtest regression: 'cannot represent an object',

[Paul Gevers]

Source: asdf-astropy
Version: 0.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
asdf-astropy   from testing0.2.0-1
all others from testingfrom testing

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

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


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

Paul

[1] https://qa.debian.org/excuses.php?package=asdf-astropy

https://ci.debian.net/data/autopkgtest/testing/amd64/a/asdf-astropy/20034163/log.gz


=== FAILURES 
===
__ test_single_model[model35] 
__


tmpdir = local('/tmp/pytest-of-debci/pytest-0/test_single_model_model35_0')
model = 

@pytest.mark.parametrize("model", create_single_models())
def test_single_model(tmpdir, model):

  assert_model_roundtrip(model, tmpdir)


/usr/lib/python3/dist-packages/asdf_astropy/converters/transform/tests/test_transform.py:383: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ 
/usr/lib/python3/dist-packages/asdf_astropy/converters/transform/tests/test_transform.py:37: 
in assert_model_roundtrip

af.write_to(path)
/usr/lib/python3/dist-packages/asdf/asdf.py:1313: in write_to
self._serial_write(fd, pad_blocks, include_block_index)
/usr/lib/python3/dist-packages/asdf/asdf.py:1065: in _serial_write
self._write_tree(self._tree, fd, pad_blocks)
/usr/lib/python3/dist-packages/asdf/asdf.py:1038: in _write_tree
yamlutil.dump_tree(
/usr/lib/python3/dist-packages/asdf/yamlutil.py:402: in dump_tree
yaml.dump_all(
/usr/lib/python3/dist-packages/yaml/__init__.py:278: in dump_all
dumper.represent(data)
/usr/lib/python3/dist-packages/yaml/representer.py:27: in represent
node = self.represent_data(data)
/usr/lib/python3/dist-packages/asdf/yamlutil.py:43: in represent_data
node = super(AsdfDumper, self).represent_data(data)
/usr/lib/python3/dist-packages/yaml/representer.py:48: in represent_data
node = self.yaml_representers[data_types[0]](self, data)
/usr/lib/python3/dist-packages/asdf/yamlutil.py:63: in represent_mapping
node = super(AsdfDumper, dumper).represent_mapping(None, 
mapping.data, flow_style)

/usr/lib/python3/dist-packages/yaml/representer.py:118: in represent_mapping
node_value = self.represent_data(item_value)
/usr/lib/python3/dist-packages/asdf/yamlutil.py:43: in represent_data
node = super(AsdfDumper, self).represent_data(data)
/usr/lib/python3/dist-packages/yaml/representer.py:58: in represent_data
node = self.yaml_representers[None](self, data)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

self = 
data = 

def represent_undefined(self, data):

  raise RepresenterError("cannot represent an object", data)
E   yaml.representer.RepresenterError: ('cannot represent an 
object', )


/usr/lib/python3/dist-packages/yaml/representer.py:231: RepresenterError
__ test_single_model[model36] 
__


tmpdir = local('/tmp/pytest-of-debci/pytest-0/test_single_model_model36_0')
model = 

@pytest.mark.parametrize("model", create_single_models())
def test_single_model(tmpdir, model):

  assert_model_roundtrip(model, tmpdir)


/usr/lib/python3/dist-packages/asdf_astropy/converters/transform/tests/test_transform.py:383: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ 
/usr/lib/python3/dist-packages/asdf_astropy/converters/transform/tests/test_transform.py:37: 
in assert_model_roundtrip

af.write_to(path)
/usr/lib/python3/dist-packages/asdf/asdf.py:1313: in write_to
self._serial_write(fd, pad_blocks, include_block_index)
/usr/lib/python3/dist-packages/asdf/asdf.py:1065: in _serial_write
self._write_tree(self._tree, fd, pad_blocks)
/usr/lib/python3/dist-packages/asdf/asdf.py:1038: in _write_tree
yamlutil.dump_tree(
/usr/lib/python3/dist-packages/asdf/yamlutil.py:402: in dump_tree
yaml.dump_all(
/usr/lib/python3/dist-packages/yaml/__init__.py:278: in dump_all
dumper.represent(data)
/usr/lib/python3/dist-packages/yaml/representer.py:27: in represent
node = self.represent_data(data)
/usr/lib/python3/dist-packages/asdf/yamlutil.py:43: in represent_data
node = super(AsdfDumper, self).represent_data(data)
/usr/lib/python3/dist-packages/yaml/representer.py:48: in represent_data
node = self.yaml_representers[data_types[0]](self

Bug#1007824: chemeq: autopkgtest failure on i386 (but no information)

[Paul Gevers]

Source: chemeq
Version: 2.22-2
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package chemeq, great. 
However, it fails on i386. Currently this failure is blocking the 
migration to testing [1]. Can you please investigate the situation and 
fix it?


I copied all of the output of the test itself at the bottom of this 
report. There's nothing to see though.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/i386/c/chemeq/19841417/log.gz

autopkgtest [21:09:59]: test command1



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1007823: scotch breaks opm-grid autopkgtest: Failed to build dune-autopkgtest

[Paul Gevers]

Source: scotch, opm-grid
Control: found -1 scotch/7.0.1-2
Control: found -1 opm-grid/2021.10-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
scotch from testing7.0.1-2
opm-grid   from testing2021.10-2
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/o/opm-grid/20035246/log.gz


== Dune project/module generator ==

duneproject will assist you in the creation of a new Dune application.
During this process a new directory with the name of your project will be
created. This directory will hold all configuration and Makefiles and a
simple example application.

2) Which modules should this module depend on?
   The following modules have been found:
   dune-common dune-geometry dune-uggrid dune-grid dune-istl opm-common 
opm-grid
creating Project "dune-autopkgtest", version 0.0.1 which depends on 
"opm-grid"

with maintainer "DUNE autopkgtest "

A sample code dune-autopkgtest.cc is generated in the "dune-autopkgtest" 
directory.

Look at the README and dune.module files there.
Now you can run the dunecontrol script which will setup the new module.
Sometimes you may have to tweak CMakeLists.txt a bit.
--
writing initial files:
- dune-autopkgtest/README
- dune-autopkgtest/CMakeLists.txt
- dune-autopkgtest/dune-autopkgtest.pc.in
Please remember to update your dune-autopkgtest/dune-autopkgtest.pc.in,
Description and URL are missing right now.
- dune-autopkgtest/config.h.cmake
- dune-autopkgtest/src/CMakeLists.txt
- dune-autopkgtest/src/dune-autopkgtest.cc
- dune-autopkgtest/dune/autopkgtest
- dune-autopkgtest/dune/CMakeLists.txt
- dune-autopkgtest/dune/autopkgtest/CMakeLists.txt
- dune-autopkgtest/dune/autopkgtest/autopkgtest.hh
- dune-autopkgtest/doc/CMakeLists.txt
- dune-autopkgtest/doc/doxygen/Doxylocal
Doxygen is not installed! Your documentation will not work without it.
- dune-autopkgtest/doc/doxygen/CMakeLists.txt
- dune-autopkgtest/cmake/modules/CMakeLists.txt
- dune-autopkgtest/cmake/modules/DuneAutopkgtestMacros.cmake

done.
--
For further details read the Dune build system documentation at
https://www.dune-project.org/buildsystem/
- using default flags $CONFIGURE_FLAGS from environment -
--- going to build dune-autopkgtest  ---
--- calling all for dune-autopkgtest ---
--- calling vcsetup for dune-autopkgtest ---
--- calling cmake for dune-autopkgtest ---
cmake"-Ddune-common_DIR=/usr" "-Ddune-geometry_DIR=/usr" 
"-Ddune-uggrid_DIR=/usr" "-Ddune-grid_DIR=/usr" "-Dopm-common_DIR=/usr" 
"-Ddune-istl_DIR=/usr/lib//cmake/dune-istl" "-Dopm-grid_DIR=/usr" 
"/tmp/autopkgtest-lxc._4o3y13e/downtmp/autopkgtest_tmp/dune-autopkgtest"

-- The CXX compiler identification is GNU 11.2.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- The C compiler identification is GNU 11.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Dependencies for dune-autopkgtest: opm-grid
-- Performing Test HAVE_C99
-- Performing Test HAVE_C99 - Success
-- Found C99: -std=c99  -- Found MPI_C: 
/usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so (found version "3.1") -- 
Found MPI_CXX: /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so 
(found version "3.1") -- Found MPI: TRUE (found version "3.1")  -- Found 
dune-geometry: /usr/include  -- Version 2.8.0 of dune-geometry from 
/usr/lib/x86_64-linux-gnu/cmake/dune-geometry
-- Found dune-uggrid: /usr/include  -- Version 2.8.0 of dune-uggrid from 
/usr/lib/x86_64-linux-gnu/cmake/dune-uggrid
-- Found dune-grid: 
/usr/include;/usr/lib/x86_64-linux-gnu/openmpi/include;/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi 
 -- Version 2.8.0 of dune-grid from 
/usr/lib/x86_64-linux-gnu/cmake/dune-grid
-- Found METIS: /usr/lib/x86_64-linux-gnu/libmetis.so  -- 

Processed: scotch breaks opm-grid autopkgtest: Failed to build dune-autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> found -1 scotch/7.0.1-2
Bug #1007823 [src:scotch, src:opm-grid] scotch breaks opm-grid autopkgtest: 
Failed to build dune-autopkgtest
Marked as found in versions scotch/7.0.1-2.
> found -1 opm-grid/2021.10-2
Bug #1007823 [src:scotch, src:opm-grid] scotch breaks opm-grid autopkgtest: 
Failed to build dune-autopkgtest
Marked as found in versions opm-grid/2021.10-2.

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

Processed: Re: Bug#1006917: kpcli: "not well-formed (invalid token)" when opening a file

[Debian Bug Tracking System]

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

> package kpcli
Limiting to bugs with field 'package' containing at least one of 'kpcli'
Limit currently set to 'package':'kpcli'

> severity 1006917 minor
Bug #1006917 [kpcli] kpcli: "not well-formed (invalid token)" when opening a 
file
Severity set to 'minor' from 'grave'
> close 1006917
Bug #1006917 [kpcli] kpcli: "not well-formed (invalid token)" when opening a 
file
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: severity of 1006953 is normal

[Debian Bug Tracking System]

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

> severity 1006953 normal
Bug #1006953 [fonts-creep2] fonts-creep2: Font does not install correctly, so 
does not show up in GUI font lists
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#1007821: node-fs-extra: autopkgtest regression: No test files found: "lib/empty/__tests__/"

[Paul Gevers]

Source: node-fs-extra
Version: 10.0.1+~9.0.13-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
node-fs-extra  from testing10.0.1+~9.0.13-1
all others from testingfrom testing

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

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


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

Paul

[1] https://qa.debian.org/excuses.php?package=node-fs-extra

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-fs-extra/20034176/log.gz

# Using ./package.(json|yaml)
# Node module name is fs-extra
# Build files found: # Test files found: test
test.js
# Files/dir to be installed from source: test
test.js # Copy test files
# Copy debian/tests/pkg-js content
'debian/tests/pkg-js' -> 
'/tmp/autopkgtest-lxc.35e10ml4/downtmp/autopkgtest_tmp/smokepWshiG/debian/tests/pkg-js'
'debian/tests/pkg-js/test' -> 
'/tmp/autopkgtest-lxc.35e10ml4/downtmp/autopkgtest_tmp/smokepWshiG/debian/tests/pkg-js/test'

'@types/fs-extra' linked into node_modules
# Searching module in /usr/lib/nodejs/fs-extra
# Searching module in /usr/lib/*/nodejs/fs-extra
# Searching module in /usr/share/nodejs/fs-extra
# Found /usr/share/nodejs/fs-extra
# Searching files to link in /usr/share/nodejs/fs-extra
'./lib' -> '/usr/share/nodejs/fs-extra/lib'
'./package.json' -> '/usr/share/nodejs/fs-extra/package.json'
# Launch debian/tests/pkg-js/test with sh -ex
+ set -e
+ OK=lib/empty lib/mkdirs lib lib/output-file lib/json lib/ensure 
lib/util lib/path-exists lib/remove

+ mocha lib/empty/__tests__/
Error: No test files found: "lib/empty/__tests__/"
autopkgtest [08:12:05]: test pkg-js-autopkgtest



OpenPGP_signature
Description: OpenPGP digital signature

Processed: python-xmlschema: autopkgtest needs update for new version of elementpath: output changed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:elementpath
Bug #1007820 [src:python-xmlschema] python-xmlschema: autopkgtest needs update 
for new version of elementpath: output changed
Added indication that 1007820 affects src:elementpath

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

Bug#1007820: python-xmlschema: autopkgtest needs update for new version of elementpath: output changed

[Paul Gevers]

Source: python-xmlschema
Version: 1.4.2-1
Severity: serious
X-Debbugs-CC: elementp...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:elementpath

Dear maintainer(s),

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


   passfail
elementpathfrom testing2.5.0-1
python-xmlschema   from testing1.4.2-1
all others from testingfrom testing

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

Currently this regression is blocking the migration of elementpath to 
testing [1]. Of course, elementpath shouldn't just break your 
autopkgtest (or even worse, your package), but it seems to me that the 
change in elementpath was intended and your package needs to update to 
the new situation.


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from elementpath should really 
add a versioned Breaks on the unfixed version of (one of your) 
package(s). Note: the Breaks is nice even if the issue is only in the 
autopkgtest as it helps the migration software to figure out the right 
versions to combine in the tests.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-xmlschema/20034165/log.gz

==
FAIL: test_assertion_facet 
(tests.validators.test_simple_types.TestXsd11SimpleTypes)

--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.46fb83c0/downtmp/build.V4y/src/tests/validators/test_simple_types.py", 
line 201, in test_assertion_facet
self.assertIn("wrong type  for operand", 
str(ctx.exception))
AssertionError: "wrong type  for operand" not found in 
'failed validating DateTime(2000, 1, 1, 12, 0, 0) with 
XsdAssertionFacet(test="$value > \'1999-12-31T23:59:59\'"):\n\nReason: 
\'>\' operator at line 1, column 8: [err:XPTY0004] \'>\' not supported 
between instances of \'DateTime\' and \'str\'\n\nSchema:\n\n 
http://www.w3.org/2001/XMLSchema"; test="$value 
> \'1999-12-31T23:59:59\'" />\n'


--
Ran 850 tests in 26.223s

FAILED (failures=1, skipped=4)
autopkgtest [08:10:57]: test command1



OpenPGP_signature
Description: OpenPGP digital signature

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

[Debian Bug Tracking System]

Your message dated Thu, 17 Mar 2022 12:18:38 +
with message-id 
and subject line Bug#999315: fixed in apwal 0.4.5-1.2
has caused the Debian Bug report #999315,
regarding apwal: 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.)


-- 
999315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999315
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apwal
Version: 0.4.5-1.1
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: apwal
Source-Version: 0.4.5-1.2
Done: Hugh McMaster 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 14 Mar 2022 22:04:23 +1100
Source: apwal
Architecture: source
Version: 0.4.5-1.2
Distribution: unstable
Urgency: medium
Maintainer: Sam Hocevar (Debian packages) 
Changed-By: Hugh McMaster 
Closes: 436940 929646 949051 999315
Changes:
 apwal (0.4.5-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Switch package to 3.0 (quilt) format.
   * Use 'dh' format to avoid missing build-arch and/or build-indep
 targets in debian/rules (Closes: #999315).
   * debian/changelog: Remove trailing whitespace.
   * debian/control:
 - Use debian-compat v13.
 - Raise Standards-Version to 4.6.0 (no changes needed).
 - Declare Rules-Requires-Root: no.
 - Drop duplicate Section field.
 - Declare package Multi-Arch: foreign.
   * debian/copyright: Use DEP-5 format and update for 2022.
   * debian/patches:
 - Fix cross-building and other issues (Closes: #929646).
   Thanks to Helmut Grohne for supplying a patch.
 - Don't override build system CFLAGS, CPPFLAGS or LDFLAGS.
 - Use pkg-config to detect libxml2 (Closes: #949051).
 - Don't manually strip the binary (Closes: #436940).
 - Fix install path to work with dh_auto_install.
 - Multiple spelling fixes (Lintian).
   * debian/rules:
 - Switch to `dh' format.
 - Export hardening flags.
Checksums-Sha1:
 1e3c9b8ee68d4bc6008a0a544be0f02f3f9f16ff 1571 apwal_0.4.5-1.2.dsc
 8863cda8e3dc7e08488d9388feaf3c460cdc3051 6088 apwal_0.4.5-1.2.debian.tar.xz
 8f4a836b0aa9c2444d4cb32d32740312751b872e 10761 apwal_0.4.5-1.2_source.buildinfo
Checksums-Sha256:
 2a136b34b2e6f1c61abd3fac0c192f043a3e72cb1f45bd651f7bb79acbf59ee9 1571 
apwal_0.4.5-1.2.dsc
 ef806b451ca5923a26bb09653ee3ae71c8a0db8feab65eaf49bde003a40eadd8 6088 
apwal_0.4.5-1.2.debian.tar.xz
 ae4dce97ac8711ce14568f38bde504312c995b538388e8b093da872bfa8fc1d7 10761 
apwal_0.4.5-1.2_source.buildinfo
Files:
 5b2e0abac0e5d11915f3902e72c0957c 1571 gnome optional apwal_0.4.5-1.2.dsc
 f78f4ee8edcc8b1e5b672be77d9f9c82 6088 gnome optional 
apwal_0.4.5-1.2.debian.tar.xz
 10789cc69f800a6c5e59222c53fd549d 10761 gnome optional 
apwal_0.4.5-1.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmIzJAwQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFNRYC/94doKtIDbqbVLbuIE5MjzcLIl54VyJkSmB
cWN5ieeEnNVJggSn2pixbiMgrT+YrrQ/JB1kSvHn2OfRMN1qs5nzrv+oNd7cYp6+
TCDjaaJkoRGKW2UtLWietllXxMNFmISyIL7wU36xNqcfv9zscxU9h4H4Bqq0Ynig
eKjj4PDAKx2wndMZV/xv/GxOfs+C+3rikMFPFIarjiYegPWt3ulId5Ou

Bug#1007773: [pkg-uWSGI-devel] Bug#1007773: Bug#1007773: uwsgi: FTBS with /usr/bin/ld: cannot find -lpcre2-8

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2022-03-17 10:49:45)
> Quoting Alexandre Rossi (2022-03-17 10:25:06)
> > > /usr/bin/ld: cannot find -lpcre2-8: No such file or directory
> > 
> > I've pushed the necessary fix. 
> > https://salsa.debian.org/uwsgi-team/uwsgi/-/commit/0955366dcf19b7ec9a0134eab1e81ec216d12a96
> 
> Thanks, both for reporting the bug and for pushing the patch.
> 
> Please, however, share the patch as a file attachement here in the 
> bugreport: We use Salsa only for git storage (other Salsa features are 
> enabled by default and apparently I forgot to disable them, sorry 
> about that).

Oh, stupid me: Wasn't a merge/pull request but was pushed directly to 
main branch, and I had totally forgotten that you are maintainer as 
well.

Sorry!

Please consider adding yourself to the Uploaders field on control file, 
to make it more visible (yes, regardless if technically you are 
permitted to upload - the name of that field is confusing, as it 
nowadays really means "Maintainers-when-Maintainer-is-a-team").


Regards,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#990026: Aaargh!

[Georges Khaznadar]

Hello Christian,

Uploading to ftp-master [DELAYED/3] ... done.

Best regards,   Georges.

Christian Kastner a écrit :
> On 2022-03-08 21:58, Christian Kastner wrote:
> > I'll upload an NMU.
> 
> Ah, pulling the newest source from Salsa, I saw Georges' @debian.org
> address. Apologies!
> 
> In that case, please NMU it yourself (as you've already prepared the
> changelog).
> 
> Best,
> Christian

-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70



signature.asc
Description: PGP signature

Bug#1005806: marked as done (gtk2hs-buildtools: gtk2hsC2hs fails with code preprocessed by GCC-11)

[Debian Bug Tracking System]

Your message dated Thu, 17 Mar 2022 11:03:58 +
with message-id 
and subject line Bug#1005806: fixed in gtk2hs-buildtools 0.13.8.0-2
has caused the Debian Bug report #1005806,
regarding gtk2hs-buildtools: gtk2hsC2hs fails with code preprocessed by GCC-11
to be marked as done.

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

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


-- 
1005806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005806
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gtk2hs-buildtools
Version: 0.13.8.0-1
Severity: serious
Tags: upstream fixed-upstream
Justification: Other packages FTBFS
Control: block 1005657 by -1
Control: block 1005676 by -1

gtk2hsC2hs fails when fed with code preprocessed by GCC-11, as it 
doesn't expect zeros in line numbers. This is similar to #984167 and
has been fixed upstream in https://github.com/gtk2hs/gtk2hs/pull/304.

Regards,
Apollon
--- End Message ---
--- Begin Message ---
Source: gtk2hs-buildtools
Source-Version: 0.13.8.0-2
Done: Gianfranco Costamagna 

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

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

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
gtk2hs-buildtools 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, 17 Mar 2022 11:48:35 +0100
Source: gtk2hs-buildtools
Architecture: source
Version: 0.13.8.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Gianfranco Costamagna 
Closes: 1005806
Changes:
 gtk2hs-buildtools (0.13.8.0-2) unstable; urgency=medium
 .
   * debian/patches/304.patch:
 - cherry-pick upstream fix for gcc-11 (Closes: #1005806)
Checksums-Sha1:
 ac600d23f751dab49a3c28dfe48d0d2e7753e749 2606 gtk2hs-buildtools_0.13.8.0-2.dsc
 b93e8bfaa108d11dff0e9a2fa521b84aa4bd6f45 8052 
gtk2hs-buildtools_0.13.8.0-2.debian.tar.xz
 73cdec7ff9ea18e23fd513dc07c6fb4953f10bf7 10689 
gtk2hs-buildtools_0.13.8.0-2_source.buildinfo
Checksums-Sha256:
 8a40ef85045fb4886fc82e7dcdcf0be50b6b194edbe0fd946fee2df81142 2606 
gtk2hs-buildtools_0.13.8.0-2.dsc
 3a613909a7ead06a3a789514642a50c5d588390d2327586428348bc2b51d02be 8052 
gtk2hs-buildtools_0.13.8.0-2.debian.tar.xz
 982b543119b5ef4019c50974a4d6695bbc9863c14168c1772f275336d8386f8a 10689 
gtk2hs-buildtools_0.13.8.0-2_source.buildinfo
Files:
 36c0d7b2653a4ec421d0922eb717a9fa 2606 haskell optional 
gtk2hs-buildtools_0.13.8.0-2.dsc
 4c61585e11024502001d96bea639f75a 8052 haskell optional 
gtk2hs-buildtools_0.13.8.0-2.debian.tar.xz
 0b578b0b7cb62427309a221d535684c2 10689 haskell optional 
gtk2hs-buildtools_0.13.8.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmIzEocACgkQ808JdE6f
XdlNGQ//TbyQ6k2C/vi107GYPL/c8AjNptiMryfGCmfJngG3zz10SYFOmn8aUTLu
RX6DqqRyOV6ADlKldz1X6nvOiBnJ7CLkJsKd0raZ+jgacJD8bzqBPsIogNwfgM2C
olT1fU5PCNtSyhOb7YFS3NxtpzoAsTL+SQm+zQIiQZD+NRbt+2ZZ9gZBDEzK3r5l
tYihOv4wm+zJEtEcVZDWkrrCP+/WmHSIuIXF6utwM+oIP+jNMA/GH1zudb3bLXuj
E7X10wjZpaztEzMm0TaphIO2qbVevYOtMZqFTnqAeKvxwQfVJ3UHq7MlUjWXXksb
TqVFG/N+lCsG1tKZ1LcnKWpkqG9+6bUjDcMpxSxA4YVpMpdHX8cmZepQhVVRm5SV
AcHy7vv6MXISCzQM841JVy0gTFQP4MMQIipM2cUvsUSe99gBjJ3yI08DUNdgUtTN
5/u+gKWC0R3llmS+3K+8h7SfcLX/guo9Jhjy+0yk4DRjiPlCVnBSbMhxFfUb2p2V
ZJ1YFGHkD2H4Uaog9YhdCTzifz8s6OquE2c4FWu1Bmd6fhvkGlMDWBmzdBVkacbN
GInqI/rykKQN9Dxet8RryHhzB6yZU5MJgWeEAAmhQVuNDnPaF0fwtMdG+Eeo3l52
dYce1Iz47iu+KCOPv3oreebIeBAw7V+7n8EyewYBpSoVkRULIsw=
=frsY
-END PGP SIGNATURE End Message ---

Bug#1007773: [pkg-uWSGI-devel] Bug#1007773: uwsgi: FTBS with /usr/bin/ld: cannot find -lpcre2-8

[Jonas Smedegaard]

Quoting Alexandre Rossi (2022-03-17 10:25:06)
> Hi,
> 
> > /usr/bin/ld: cannot find -lpcre2-8: No such file or directory
> 
> I've pushed the necessary fix.
> https://salsa.debian.org/uwsgi-team/uwsgi/-/commit/0955366dcf19b7ec9a0134eab1e81ec216d12a96

Thanks, both for reporting the bug and for pushing the patch.

Please, however, share the patch as a file attachement here in the 
bugreport: We use Salsa only for git storage (other Salsa features are 
enabled by default and apparently I forgot to disable them, sorry about 
that).

Kind regards,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Processed: tagging 1007773

[Debian Bug Tracking System]

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

> tags 1007773 + patch
Bug #1007773 [src:uwsgi] uwsgi: FTBS with /usr/bin/ld: cannot find -lpcre2-8
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1007773: uwsgi: FTBS with /usr/bin/ld: cannot find -lpcre2-8

[Alexandre Rossi]

Hi,

> /usr/bin/ld: cannot find -lpcre2-8: No such file or directory

I've pushed the necessary fix.
https://salsa.debian.org/uwsgi-team/uwsgi/-/commit/0955366dcf19b7ec9a0134eab1e81ec216d12a96

Thanks,

Alex

Processed: tagging 967228, tagging 966988, tagging 997115, found 998280 in 1.22.3-1 ...

[Debian Bug Tracking System]

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

> tags 967228 + experimental
Bug #967228 {Done: Gürkan Myczko } [src:uftrace] uftrace: 
Unversioned Python removal in sid/bullseye
Added tag(s) experimental.
> tags 966988 + experimental
Bug #966988 {Done: Gürkan Myczko } [src:uftrace] uftrace: 
FTBFS: test failed
Added tag(s) experimental.
> tags 997115 + fixed-in-experimental
Bug #997115 {Done: Andreas Tille } [src:tbb] tbb: FTBFS: 
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
Added tag(s) fixed-in-experimental.
> found 998280 1.22.3-1
Bug #998280 {Done: Ross Vandegrift } [efl-doc] Please 
switch the dependency from ttf-bitstream-vera to fonts-dejavu-core
Marked as found in versions efl/1.22.3-1.
> notfound 942377 1:9.18.0-2
Bug #942377 {Done: Ondřej Surý } [bind9] /etc/bind/db.root 
should be removed on upgrades
No longer marked as found in versions bind9/1:9.18.0-2.
> notfound 1005038 4.2.6-1
Bug #1005038 {Done: Micha Lenk } [src:oidc-agent] oidc-agent: 
Backport for bullseye
No longer marked as found in versions oidc-agent/4.2.6-1.
> fixed 1005038 4.2.6-1
Bug #1005038 {Done: Micha Lenk } [src:oidc-agent] oidc-agent: 
Backport for bullseye
Marked as fixed in versions oidc-agent/4.2.6-1.
> thanks
Stopping processing here.

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

Bug#1005500: argh: FTBFS: doctest.h:1398:92: error: use of deleted function ‘doctest::detail::Expression_lhs >::Expression_lhs(doctest::detail::Expression

[Andreas Tille]

Control: tags -1 help
Control: tags -1 upstream
Control: forwarded -1 https://github.com/adishavit/argh/issues/72

Processed: Re: argh: FTBFS: doctest.h:1398:92: error: use of deleted function ‘doctest::detail::Expression_lhs >::Expression_lhs(doctest::detail::Expressi

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #1005500 [src:argh] argh: FTBFS: doctest.h:1398:92: error: use of deleted 
function ‘doctest::detail::Expression_lhs 
>::Expression_lhs(doctest::detail::Expression_lhs >&&)’
Added tag(s) help.
> tags -1 upstream
Bug #1005500 [src:argh] argh: FTBFS: doctest.h:1398:92: error: use of deleted 
function ‘doctest::detail::Expression_lhs 
>::Expression_lhs(doctest::detail::Expression_lhs >&&)’
Added tag(s) upstream.
> forwarded -1 https://github.com/adishavit/argh/issues/72
Bug #1005500 [src:argh] argh: FTBFS: doctest.h:1398:92: error: use of deleted 
function ‘doctest::detail::Expression_lhs 
>::Expression_lhs(doctest::detail::Expression_lhs >&&)’
Set Bug forwarded-to-address to 'https://github.com/adishavit/argh/issues/72'.

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

Bug#1006384: closed by Debian FTP Masters (reply to Olivier Sallou ) (Bug#1006384: fixed in logol 1.7.9+dfsg-2)

[Paul Gevers]

Dear Tobias, Michael,

Can be please have an answer to the question below? Your lack of answer 
is blocking migration to testing of multiple packages.


On 07-03-2022 17:28, dogs...@riseup.net wrote:

Paul Gevers писал 2022-03-06 21:36:

On 06-03-2022 11:30, dogs...@riseup.net wrote:

As I can see, there is only one reverse build-dependency on swi-prolog
apart from eye and logol, that is ppl. It is a C++ library providing
SWI-Prolog interface. I tried to build it against swi-prolog from
unstable on amd64 porterbox and the build was successful (including
tests, which are unfortunately not autopkgtest-ready).


Is this enough to say the ABI change doesn't effect ppl?


I'm not sure whether ppl depends and/or somehow uses some particular
swi-prolog ABI, I tried to run tests from ppl source package with
ppl and swi-prolog binary packages installed (from unstable), but
with no success. I just don't know right now how to run them
correctly (these are C++ source code, as far as I can tell). So,
CCing uploaders of ppl.

Tobias, Michael, is it possible that ABI changes in swi-prolog may
break binaries of ppl in unstable? How can we test it? As quoted
above, I already tried to build ppl against the newest swi-prolog
in unstable, and ppl was built successfully.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:freetds: fails to migrate to testing for too long: uploader built arch:all binaries

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.3.6-1
Bug #1007811 [src:freetds] src:freetds: fails to migrate to testing for too 
long: uploader built arch:all binaries
Marked as fixed in versions freetds/1.3.6-1.
Bug #1007811 [src:freetds] src:freetds: fails to migrate to testing for too 
long: uploader built arch:all binaries
Marked Bug as done

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

Bug#1007811: src:freetds: fails to migrate to testing for too long: uploader built arch:all binaries

[Paul Gevers]

Source: freetds
Version: 1.2.3-1
Severity: serious
Control: close -1 1.3.6-1
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:freetds has been trying to migrate for 61 
days [2]. Hence, I am filing this bug.


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


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


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


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1007783: marked as done (Breaks containerd)

[Debian Bug Tracking System]

Your message dated Thu, 17 Mar 2022 08:24:08 +0100
with message-id <20220317072408.g6u4pv26zzg52...@fatal.se>
and subject line oops, forgot to close in changelog
has caused the Debian Bug report #1007783,
regarding Breaks containerd
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.)


-- 
1007783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-gogottrpc
Version: 1.1.0-1
Severity: serious
X-Debbugs-Cc: z...@debian.org

Rebuilding containerd with golang-gogottrpc/1.1.0-1, then install it.

Now we get:

$ sudo ctr run --rm -t docker.io/library/alpine:latest test1
ctr: failed to create shim task: ttrpc: cannot marshal unknown type: 
*task.CreateTaskRequest: unknown

$ docker run --rm -it ubuntu:20.04 bash
docker: Error response from daemon: failed to create shim task: ttrpc: cannot 
marshal unknown type: *task.CreateTaskRequest: unknown.
--- End Message ---
--- Begin Message ---
Version: 1.1.0-2

Forgot to close this is the just uploaded new revisien of the package
which drops the backported patches from upstream which apparently
containerd, et.al aren't yet ready to handle.

This also reopens #975431

Regards,
Andreas Henriksson--- End Message ---

Processed (with 1 error): reopen 975431

[Debian Bug Tracking System]

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

> reopen 975431 1.1.0-2
Failed to reopen 975431: New submitter address '1.1.0-2' is not a valid e-mail 
address.

> block 975431 by 1007783
Bug #975431 {Done: Andreas Henriksson } 
[src:golang-gogottrpc] Not compatible with golang/protobuf 1.4.x
975431 was not blocked by any bugs.
975431 was not blocking any bugs.
Added blocking bug(s) of 975431: 1007783
> thanks
Stopping processing here.

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