Bug#965902: bump xom debhelper compat from 5 to 7

[Andrius Merkys]

Control: tags -1 + patch

Hello,

I have locally bumped debhelper compat to 7, rebuilt the package and ran
diffoscope between archive-provided and locally built
libxom-java_1.2.10-2_all.deb. The single change is in
META-INF/MANIFEST.MF of the JAR file:

│ │ │ │ -Ant-Version: Apache Ant 1.10.9
│ │ │ │ -Created-By: 11.0.12+7-post-Debian-2 (Debian)
│ │ │ │ +Ant-Version: Apache Ant 1.10.11
│ │ │ │ +Created-By: 11.0.13+8-post-Debian-1 (Debian)

I assume this is safe to upload, but I would like someone else to
confirm the change. Bumping compat level from 5 to 7 which is also
deprecated is a sloppy fix, but would probably do for now.

Best,
Andrius

Processed: Bug#965902: bump xom debhelper compat from 5 to 7

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

[Andres Salomon]

On 12/13/21 5:31 PM, Moritz Muehlenhoff wrote:

On Sun, Dec 12, 2021 at 08:11:00PM -0500, Andres Salomon wrote:

On 12/5/21 6:41 AM, Moritz Mühlenhoff wrote:

Am Sun, Dec 05, 2021 at 10:53:56AM +0100 schrieb Paul Gevers:
Exactly that.

I'd suggest anyone who's interested in seeing Chromium supported to first
update it in unstable (and then work towards updated in bullseye-security).

I started doing just that: https://salsa.debian.org/dilinger/chromium (v96
and misc-fixes branches).

As a side note: If any of the system/* patches cause issues, feel free to switch
to the vendored copies. Vendoring in general is frowned upon since it requires 
that
a fix in a libraries spreads out to all vendored copies, but for Chromium 
there's
a steady stream of Chromium-internal security issues anyway, so for all
practical purposes it doesn't make a difference if the Chromium security 
releases
also include a fix for a vendored lib like ICU.

Cheers,
 Moritz



I've got 96.0.4664.110 building on both bullseye and sid, and am currently

debugging some crashes. The only thing I had to vendor was some nodejs

libraries, although it's very tempting to take a chainsaw through the 
various


patches and re-vendor a bunch of other libraries as Jeff suggested. Still on

the v96 branch of https://salsa.debian.org/dilinger/chromium

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

[Debian Bug Tracking System]

Your message dated Thu, 23 Dec 2021 06:33:29 +
with message-id 
and subject line Bug#965590: fixed in icom 20120228-4
has caused the Debian Bug report #965590,
regarding icom: 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.)


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

Hi,

The package icom 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: icom
Source-Version: 20120228-4
Done: tony mancill 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 22 Dec 2021 22:11:52 -0800
Source: icom
Architecture: source
Version: 20120228-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: tony mancill 
Closes: 929220 965590 990599
Changes:
 icom (20120228-4) unstable; urgency=medium
 .
   * Add Vcs fields for repo on Salsa
   * Update Uploaders field, removing Colin Tuckley (Closes: #990599)
   * Use debhelper-compat 13 (Closes: #965590)
   * Change package Priority from extra to optional
   * Fix FTCBFS: Let dh_auto_build pass cross tools to make.
 Thank you to Helmut Grohne for the patch.  (Closes: #929220)
   * Use dh sequencer
Checksums-Sha1:
 b18deef618118ccde800347f70c4d29ba1cdb198 1984 icom_20120228-4.dsc
 2a74035775270f2a799629c3980b8010660c24aa 11368 icom_20120228-4.debian.tar.xz
 6a496985a6bccaef4190eec7875a4e810fe3d68d 6031 icom_20120228-4_amd64.buildinfo
Checksums-Sha256:
 3f65e0e00f78a6be909a0d7591103730e96c83285a0b001e79a5d3c7704f3cf7 1984 
icom_20120228-4.dsc
 4746bfc13c1d155c072d63380f82d5648bda2d7fd3574e65d1497aac1e9832fb 11368 
icom_20120228-4.debian.tar.xz
 d56e367179503472144cbc89273e1730e7ce0b3cce3ec628ab02d3298ee7335a 6031 
icom_20120228-4_amd64.buildinfo
Files:
 4b29c2ad5ece95fe1d68c3876d280733 1984 hamradio optional icom_20120228-4.dsc
 326e2b2282909eb5e654dd756119fcb8 11368 hamradio optional 
icom_20120228-4.debian.tar.xz
 9b678188358766970751cf5db70aca36 6031 hamradio optional 
icom_20120228-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmHEE+8UHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpbcdw//YxyfX6/mCdMQky3yzFJnFz7+qdph
nJvGH0jP54uKULtDfwWtzP54w4JK881aOhj9Y99bpK087wc3W3h4m+az9ih4p/t+
s6VBbZypViun5OBHeCagRtANYRW6CcCL8CSMPlCYm4vfFRpb5/c+X93syVxO0Rsk
2dZwG5GIopvoIySyhOA62tkTt0i8gQQcpe4gVlvcosMuQF9dMvJLN2OGgKbmxGM2
wXMZJ/BiGl8k3Lqh6BXcg3ofHRTfYNM2QF877WRu6GT9yX9rEe6+MZSlt05/Em0e
TFMp7W/uzhWM2tMu68afH3E0Rm8wKBo84VNvc61QjWEFiGBoJgAYICXWJeoaFDIW
plzfYUbrYk8Yk/648wFahc81zzAbdIEzp7k80NMKsdppBgJlq6iu1nivjNJnMWTO
UcDtfiIhn7VLBfBvsQ6kF3G8xM4a+DVlWwhIHGVNGpszQn0qLKPhQXlkzUxCGdfp

Bug#1002155: libgoby-java: FTBFS: [WARNING] /<>/goby-io/../goby-distribution/src/main/java/org/campagnelab/goby/modes/FastaToCompactMode.java:23: error: package edu.rit.pj does not exist

[Pierre Gruet]

Hi Andreas,

On 22/12/2021 19:45, Andreas Tille wrote:

Hi,

Am Wed, Dec 22, 2021 at 06:17:21PM +0100 schrieb Pierre Gruet:


The warning mentioned in the bug title is issued by the Javadoc builder,
which we do not use. It does not trigger the failure of the build.
The real issue is in the tests: for some reason, a FileNotFoundException is
raised by the FileOutputStream constructor when being called on files in the
test-results/ directory.


The "can not reproduce" in combination with "file not found" rings somehow
a bell that this could be a case for a --no-parallel build.



Thanks for your advice, I will look toward this today. Probably I will 
make an upload with this fix if nothing else comes up.



Kind regards

   Andreas.



Best regards,

--
Pierre

Processed: Bug#965590 marked as pending in icom

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #965590 [src:icom] icom: Removal of obsolete debhelper compat 5 and 6 in 
bookworm
Added tag(s) pending.

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

Bug#965590: marked as pending in icom

[Tony Mancill]

Control: tag -1 pending

Hello,

Bug #965590 in icom 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/debian-hamradio-team/icom/-/commit/acfe29cc4fb71754c05225c94fb6e258a92b057f


Use debhelper-compat 13 (Closes: #965590)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/965590

Bug#1000336: Upgrading tbb (Was: numba: FTBFS with Python 3.10)

[Andreas Tille]

Hi,

Am Wed, Dec 22, 2021 at 05:09:35PM -0800 schrieb Diane Trout:
> On Wed, 2021-12-22 at 22:24 +0530, Nilesh Patra wrote:
> > 
> > Actually because of the current state of numba, several reverse
> > depends are FTBFS so it's
> > bit urgent to push. Apologies for getting on your nerves, though.
> 
> I tried. but numba needs tbb version >= 2021. I tried to update tbb but
> ran into problems trying to build it.

I've checked tbb Git and have read:


onetbb (2021.4.0-1~exp1) UNRELEASED; urgency=medium

  * Source rename following upstream. The new upstream Git URL is
https://github.com/oneapi-src/oneTBB

 -- Mo Zhou   Mon, 29 Nov 2021 21:44:57 -0500


I admit I support following upstream names in general.  However, the
lesson that we just are waiting for some package with name changes in
new for more than one month makes this name change a bit scary in the
current situation, thought.  Well, in case tbb 2021.x might bump SONAME
(which I have not checked) we can't avoid this.  However, if we might
have a chance to get a recent tbb without name changes quickly and could
do the name change later this would be helpful.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Processed: tf: diff for NMU version 1:4.0s1-21.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1000460 + patch
Bug #1000460 [src:tf] tf does not trap errors from make
Added tag(s) patch.
> tags 1000460 + pending
Bug #1000460 [src:tf] tf does not trap errors from make
Added tag(s) pending.

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

Bug#1000460: tf: diff for NMU version 1:4.0s1-21.1

[Adrian Bunk]

Control: tags 1000460 + patch
Control: tags 1000460 + pending

Dear maintainer,

I've prepared an NMU for tf (versioned as 1:4.0s1-21.1) and uploaded
it to DELAYED/14. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru tf-4.0s1/debian/changelog tf-4.0s1/debian/changelog
--- tf-4.0s1/debian/changelog	2020-07-23 12:40:24.0 +0300
+++ tf-4.0s1/debian/changelog	2021-12-23 07:50:06.0 +0200
@@ -1,3 +1,10 @@
+tf (1:4.0s1-21.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * unix/Makefile: Trap errors from make. (Closes: #1000460)
+
+ -- Adrian Bunk   Thu, 23 Dec 2021 07:50:06 +0200
+
 tf (1:4.0s1-21) unstable; urgency=medium
 
   * Fix build with gcc-10 (Closes: Bug#957871)
diff -Nru tf-4.0s1/debian/patches/Makefile-errors.patch tf-4.0s1/debian/patches/Makefile-errors.patch
--- tf-4.0s1/debian/patches/Makefile-errors.patch	1970-01-01 02:00:00.0 +0200
+++ tf-4.0s1/debian/patches/Makefile-errors.patch	2021-12-23 07:50:06.0 +0200
@@ -0,0 +1,16 @@
+Description: unix/Makefile: Trap errors from make
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/1000460
+
+--- tf-4.0s1.orig/unix/Makefile
 tf-4.0s1/unix/Makefile
+@@ -22,8 +22,7 @@ default: install
+ # to make "install", "all", AND "files", instead of just "install".
+ 
+ install all files: src/Makefile src/config.h _log
+-	cd ./src; { $(MAKE) $@ 2>&1; echo; cat exitmsg; } | \
+-	{ tee -a ../Build.log || cat; }
++	cd ./src; $(MAKE) $@ 2>&1
+ 
+ reconfigure:  unconfigure install
+ 
diff -Nru tf-4.0s1/debian/patches/series tf-4.0s1/debian/patches/series
--- tf-4.0s1/debian/patches/series	2020-07-23 12:40:24.0 +0300
+++ tf-4.0s1/debian/patches/series	2021-12-23 07:50:06.0 +0200
@@ -1 +1,2 @@
 debian-changes
+Makefile-errors.patch

Processed: closing 965654

[Debian Bug Tracking System]

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

> close 965654 0.0.17-3
Bug #965654 [src:libjorbis-java] libjorbis-java: Removal of obsolete debhelper 
compat 5 and 6 in bookworm
Ignoring request to alter fixed versions of bug #965654 to the same values 
previously set
Bug #965654 [src:libjorbis-java] libjorbis-java: Removal of obsolete debhelper 
compat 5 and 6 in bookworm
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#965654: closing 965654

[tony mancill]

close 965654 0.0.17-3
thanks

The update to debhelper-compat 13 was completed by Emmanuel's upload
of 0.0.17-3 in February of 2021.

https://tracker.debian.org/news/1226653/accepted-libjorbis-java-0017-3-source-into-unstable/

Processed: fixed 965654 in 0.0.17-3

[Debian Bug Tracking System]

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

> fixed 965654 0.0.17-3
Bug #965654 [src:libjorbis-java] libjorbis-java: Removal of obsolete debhelper 
compat 5 and 6 in bookworm
Marked as fixed in versions libjorbis-java/0.0.17-3.
> thanks
Stopping processing here.

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

Bug#997898: marked as done (src:etbemon: fails to migrate to testing for too long: FTBFS everywhere)

[Debian Bug Tracking System]

Your message dated Thu, 23 Dec 2021 04:48:37 +
with message-id 
and subject line Bug#997898: fixed in etbemon 1.3.5-8.1
has caused the Debian Bug report #997898,
regarding src:etbemon: fails to migrate to testing for too long: FTBFS 
everywhere
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.)


-- 
997898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: etbemon
Version: 1.3.5-6
Severity: serious
Control: close -1 1.3.5-7
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 992896

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:etbemon has been trying to migrate for 63
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.

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

Paul

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




OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: etbemon
Source-Version: 1.3.5-8.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
etbemon, 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.
Adrian Bunk  (supplier of updated etbemon 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, 09 Dec 2021 20:05:25 +0200
Source: etbemon
Architecture: source
Version: 1.3.5-8.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Mon Maintainers 

Changed-By: Adrian Bunk 
Closes: 992896 997898
Changes:
 etbemon (1.3.5-8.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply patch from Aurelien Jarno to fix FTBFS with glibc 2.32.
 (Closes: #992896, #997898)
Checksums-Sha1:
 3be7d6997fc77060a56969225a1d935b5d15ddc8 1951 etbemon_1.3.5-8.1.dsc
 8d89fa1458bbbf2c63d769ff99299475d43373d1 7095 etbemon_1.3.5-8.1.diff.gz
Checksums-Sha256:
 03a108fedf4882964f6d8eebe5ed9de1d8a2c85092fb55bb5f830f7e03b74a39 1951 
etbemon_1.3.5-8.1.dsc
 ba571149c6776c5dcb375d6f586f97048e6ede40eab6d5aa5fae5a3bb99ab2d9 7095 
etbemon_1.3.5-8.1.diff.gz
Files:
 e0d883137da6bb9ef0471fca408b890b 1951 admin optional etbemon_1.3.5-8.1.dsc
 bc517487889954c388411bba67e4f92f 7095 admin optional etbemon_1.3.5-8.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmGyRdEACgkQiNJCh6LY
mLEImxAAsNfgA58wy2gFLDU6PsflsDJsoQ9B2pNXrsqisaiymhMdsOA6CoTET6rL
DX9/t3htS5WJBGpflLnYzxaAYw1OLY13xAycOGE7jaWfm8omwK2Lkyy089YEmJwP
5TTyu9l0KTF2c1nAvPXuBJ7RnKxkkndZVATs5f9vlkdsZ6P4yFkXWiHOL15hqkK9
lfndxLU2sfPzuRjuYz7CE1LTpERU1jQtfZcaFXhfkZZlwJr0jvchefB0Yu6rJf/K
dcfkRepJ86C2Bw4g5+90nzsa2cMahwDGEY3m4Py/DXXH0V7lCn69NYWaSJOaF+b6
fCdAzD+AwHjwBd/ENK33+WnPOrIpy/p4VXgpKL9YaEUNSbhkH8B30+iaKfvES8NP
/q63UaoAlI6m2P8tjOkcViTD/hhapLI5j2jhGm/oqaeeAw+shEdg+bH0PpnbPUJ/
cEQUq76bUPi/9d1B3/xB7SHViWy5mdpK1L26bhxdhf41u+GoFY7fpAcGkYKlAO7A
53SatZrYdr/U41RoIeZ+u/Lfwyk1c1exoGGv0Kq+BRvKeN70p54NKZUHIEwBa8c+

Bug#995625: marked as done (httping FTBFS: error: format not a string literal and no format arguments [-Werror=format-security])

[Debian Bug Tracking System]

Your message dated Thu, 23 Dec 2021 04:48:42 +
with message-id 
and subject line Bug#995625: fixed in httping 2.5-5.2
has caused the Debian Bug report #995625,
regarding httping FTBFS: error: format not a string literal and no format 
arguments [-Werror=format-security]
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.)


-- 
995625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995625
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: httping
Version: 2.5-5.1
Severity: serious
Tags: ftbfs

httping fails to build from source in unstable on amd64. A non-parallel
build ends as follows:

| x86_64-linux-gnu-gcc -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -W -Wextra 
-pedantic -D_FORTIFY_SOURCE=2  -DVERSION=\"2.5\" 
-DLOCALEDIR=\"/usr/share/locale\" -DTCP_TFO -DNC -DFW -D_DEBUG -ggdb 
-Wdate-time -D_FORTIFY_SOURCE=2  -c -o nc.o nc.c
| nc.c: In function ‘myprint’:
| nc.c:238:3: error: format not a string literal and no format arguments 
[-Werror=format-security]
|   238 |   wprintw(w, what);
|   |   ^~~
| nc.c: In function ‘draw_graph’:
| nc.c:611:24: warning: unused parameter ‘val’ [-Wunused-parameter]
|   611 | void draw_graph(double val)
|   | ~~~^~~
| nc.c: In function ‘status_line’:
| nc.c:389:2: warning: ignoring return value of ‘vasprintf’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
|   389 |  vasprintf(, fmt, ap);
|   |  ^
| cc1: some warnings being treated as errors
| make[1]: *** [: nc.o] Error 1
| make[1]: Leaving directory '/<>'
| dh_auto_build: error: make -j1 returned exit code 2
| make: *** [debian/rules:10: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

This is likely caused by ncurses adding format string annotations.

Helmut
--- End Message ---
--- Begin Message ---
Source: httping
Source-Version: 2.5-5.2
Done: Adrian Bunk 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 11 Dec 2021 14:36:20 +0200
Source: httping
Architecture: source
Version: 2.5-5.2
Distribution: unstable
Urgency: medium
Maintainer: Abhijith PA 
Changed-By: Adrian Bunk 
Closes: 995625
Changes:
 httping (2.5-5.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add upstream fix for FTBFS with new ncurses. (Closes: #995625)
Checksums-Sha1:
 c50054816992632be6afa7ef832347e643aa55e1 1930 httping_2.5-5.2.dsc
 a3cbbfa7fbd3fb119abbd66431c2f9bad23bd95e 5012 httping_2.5-5.2.debian.tar.xz
Checksums-Sha256:
 9c2ec441f37645afc1c29b1259c96e5fbae27402c7a5b982a226b6ebd49e0029 1930 
httping_2.5-5.2.dsc
 05434385b23099378fcfd84d6f50485076e13e01a3ad74451ee96ceaf96fd518 5012 
httping_2.5-5.2.debian.tar.xz
Files:
 82c1a507552a0dcd1c1ce3be684c32c1 1930 net optional httping_2.5-5.2.dsc
 4c2d9ecf9815bbdc51774f96eaade5e5 5012 net optional 
httping_2.5-5.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmG0nKwACgkQiNJCh6LY
mLHUdA/9EUWGU2uoScKaJxFh+vk5ubLKVEjwkmf85zG0/1OiCShJsXeLzQE9mBSb
KlSpAmUWL3sOq8503crj6C5JTcf9ZZ/Cw3F91Hq2OuaWtZ1ZxPI88m7oo+jov5I6
Sh3/xEjEQEVAKus5P7nckQADR+4tEvEIQ077OtyTP0tYeHbobCSQT0GN6aVxq6KC
sPHzMoTeLftusnBNTjRUdNphs950OUUoT0YxVCpkyqgDBhtb1p8jN3wsYv6W+jCl
lWjeK+N7ho9hE9zvlvWPue42XjrNd+f+/GMHZsis+Yz5ZCArDyy7KP92MsYJ8mEa
FN5S2RFwZzTt8CccReMhjGGjb5qm5pb92MkvDKU/EcPtLemvIuEYZ9XdkQuEqryK
CesgQDzsLwoKSj/Z4cgHKIe1GQaQ0I09Su+g3SfyIVH6UYxZIFkGF6nJlDZDrVpQ
/1m0HpZBSKmfyf8itVgwVcjb7oYqPQ7CsDgwUX/v47HT3tIz3QiAMvQ8ebBz6zZa
NCwGBw6C0FSFEO4sCsqJmQgd9beoMgPhiHktNgI7oXfzJCxVfvAwTmu50t85U8Kl
WujPX9zfeUsJ88BlYjfTj2CeXnMCSVtD0ulOYno16sNNZRIA30rdIAhAqpK+mxCU
OtneJHOU3XIz27T62aTlyp2DvIKGds+BbsSiXhMvSkCWefLxT28=
=/1AZ
-END PGP SIGNATURE End Message ---

Bug#984050: marked as done (endless-sky: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Thu, 23 Dec 2021 04:48:32 +
with message-id 
and subject line Bug#984050: fixed in endless-sky 0.9.8-1.2
has caused the Debian Bug report #984050,
regarding endless-sky: 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.)


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

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

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

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

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

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

  apt-get -t=experimental install g++ 

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

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

[...]
source/AI.cpp: In member function 'void AI::Step(const PlayerInfo&)':
source/AI.cpp:571:57: warning: loop variable 'ptr' of type 'const 
std::weak_ptr&' binds to a temporary constructed from type 'const 
std::weak_ptr' [-Wrange-loop-construct]
  571 | for(const weak_ptr  : 
it->GetEscorts())
  | ^~~
source/AI.cpp:571:57: note: use non-reference type 'const std::weak_ptr' to make the copy explicit or 'const std::weak_ptr&' to prevent 
copying
source/AI.cpp: In member function 'void AI::MoveIndependent(Ship&, Command&) 
const':
source/AI.cpp:1154:57: warning: loop variable 'escort' of type 'const 
std::weak_ptr&' binds to a temporary constructed from type 'const 
std::weak_ptr' [-Wrange-loop-construct]
 1154 | for(const weak_ptr  : 
ship.GetEscorts())
  | ^~
source/AI.cpp:1154:57: note: use non-reference type 'const std::weak_ptr' to make the copy explicit or 'const std::weak_ptr&' to prevent 
copying
g++ -o build/release/Body.o -c -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -Wall -O3 
-Wdate-time -D_FORTIFY_SOURCE=2 source/Body.cpp
g++ -o build/release/CaptureOdds.o -c -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=c++11 -Wall -O3 -Wdate-time -D_FORTIFY_SOURCE=2 
source/CaptureOdds.cpp
g++ -o build/release/CargoHold.o -c -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -Wall -O3 
-Wdate-time -D_FORTIFY_SOURCE=2 source/CargoHold.cpp
g++ -o build/release/CollisionSet.o -c -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=c++11 -Wall -O3 -Wdate-time -D_FORTIFY_SOURCE=2 
source/CollisionSet.cpp
g++ -o build/release/Color.o -c -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -Wall -O3 
-Wdate-time -D_FORTIFY_SOURCE=2 source/Color.cpp
g++ -o build/release/Command.o -c -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -Wall -O3 
-Wdate-time -D_FORTIFY_SOURCE=2 source/Command.cpp
g++ -o build/release/ConditionSet.o -c -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=c++11 -Wall -O3 -Wdate-time -D_FORTIFY_SOURCE=2 
source/ConditionSet.cpp
g++ -o build/release/Conversation.o -c -g -O2 
-ffile-prefix-map=/<>=. 

Bug#992896: marked as done (etbemon: FTBFS due to RPC removal from glibc)

[Debian Bug Tracking System]

Your message dated Thu, 23 Dec 2021 04:48:37 +
with message-id 
and subject line Bug#992896: fixed in etbemon 1.3.5-8.1
has caused the Debian Bug report #992896,
regarding etbemon: FTBFS due to RPC removal from glibc
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.)


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

Dear maintainer,

The glibc SunRPC implementation has been marked obsolete for some time.
It has been removed upstream from glibc 2.32, and it got disabled in the
recent glibc uploads. The TI RPC implementation should be used instead,
which also brings new features (IPv6, Kerberos support, ...).

Your recent package upload failed to build in sid for that reason. You
will find attached a patch to switch to the TI RPC implementation,
fixing the FTBFS.

Regards,
Aurelien
diff -u etbemon-1.3.5/debian/control etbemon-1.3.5/debian/control
--- etbemon-1.3.5/debian/control
+++ etbemon-1.3.5/debian/control
@@ -4,7 +4,7 @@
 Maintainer: Debian Mon Maintainers 

 Uploaders: Dario Minnucci ,
  Russell Coker 
-Build-Depends: debhelper (>= 11), perl, libtime-period-perl
+Build-Depends: debhelper (>= 11), perl, libtime-period-perl, libtirpc-dev
 Standards-Version: 4.3.0
 Homepage: https://doc.coker.com.au/projects/etbe-mon/
 Vcs-Git: https://salsa.debian.org/etbe/etbemon.git
only in patch2:
unchanged:
--- etbemon-1.3.5.orig/mon.d/Makefile
+++ etbemon-1.3.5/mon.d/Makefile
@@ -6,7 +6,8 @@
 CC = gcc
 CFLAGS = `dpkg-buildflags --get CFLAGS`
 LDFLAGS = `dpkg-buildflags --get LDFLAGS`
-LDLIBS =
+INCFLAGS = -I/usr/include/tirpc
+LDLIBS = -ltirpc
 # uncomment next line for Solaris
 # LDLIBS = -lnsl -lsocket
 
@@ -20,7 +21,7 @@
 all: $(PROGS)
 
 rpc.monitor: rpc.monitor.c
-   $(CC) -o rpc.monitor $(CFLAGS) $(CPPFLAGS) $(LDFLAGS) rpc.monitor.c 
$(LDLIBS)
+   $(CC) -o rpc.monitor $(CFLAGS) $(CPPFLAGS) $(INCFLAGS) $(LDFLAGS) 
rpc.monitor.c $(LDLIBS)
 
 dialin.monitor.wrap: dialin.monitor.wrap.c
$(CC) -o dialin.monitor.wrap $(CFLAGS) $(CPPFLAGS) $(LDFLAGS) \
--- End Message ---
--- Begin Message ---
Source: etbemon
Source-Version: 1.3.5-8.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
etbemon, 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.
Adrian Bunk  (supplier of updated etbemon 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, 09 Dec 2021 20:05:25 +0200
Source: etbemon
Architecture: source
Version: 1.3.5-8.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Mon Maintainers 

Changed-By: Adrian Bunk 
Closes: 992896 997898
Changes:
 etbemon (1.3.5-8.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply patch from Aurelien Jarno to fix FTBFS with glibc 2.32.
 (Closes: #992896, #997898)
Checksums-Sha1:
 3be7d6997fc77060a56969225a1d935b5d15ddc8 1951 etbemon_1.3.5-8.1.dsc
 8d89fa1458bbbf2c63d769ff99299475d43373d1 7095 etbemon_1.3.5-8.1.diff.gz
Checksums-Sha256:
 03a108fedf4882964f6d8eebe5ed9de1d8a2c85092fb55bb5f830f7e03b74a39 1951 
etbemon_1.3.5-8.1.dsc
 ba571149c6776c5dcb375d6f586f97048e6ede40eab6d5aa5fae5a3bb99ab2d9 7095 
etbemon_1.3.5-8.1.diff.gz
Files:
 e0d883137da6bb9ef0471fca408b890b 1951 admin optional etbemon_1.3.5-8.1.dsc
 bc517487889954c388411bba67e4f92f 7095 admin optional etbemon_1.3.5-8.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmGyRdEACgkQiNJCh6LY
mLEImxAAsNfgA58wy2gFLDU6PsflsDJsoQ9B2pNXrsqisaiymhMdsOA6CoTET6rL
DX9/t3htS5WJBGpflLnYzxaAYw1OLY13xAycOGE7jaWfm8omwK2Lkyy089YEmJwP
5TTyu9l0KTF2c1nAvPXuBJ7RnKxkkndZVATs5f9vlkdsZ6P4yFkXWiHOL15hqkK9
lfndxLU2sfPzuRjuYz7CE1LTpERU1jQtfZcaFXhfkZZlwJr0jvchefB0Yu6rJf/K
dcfkRepJ86C2Bw4g5+90nzsa2cMahwDGEY3m4Py/DXXH0V7lCn69NYWaSJOaF+b6
fCdAzD+AwHjwBd/ENK33+WnPOrIpy/p4VXgpKL9YaEUNSbhkH8B30+iaKfvES8NP
/q63UaoAlI6m2P8tjOkcViTD/hhapLI5j2jhGm/oqaeeAw+shEdg+bH0PpnbPUJ/

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

[Debian Bug Tracking System]

Your message dated Thu, 23 Dec 2021 04:33:48 +
with message-id 
and subject line Bug#965614: fixed in kunststoff 2.0.2-6
has caused the Debian Bug report #965614,
regarding kunststoff: 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.)


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

Hi,

The package kunststoff 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: kunststoff
Source-Version: 2.0.2-6
Done: tony mancill 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 22 Dec 2021 20:02:11 -0800
Source: kunststoff
Architecture: source
Version: 2.0.2-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Closes: 965614
Changes:
 kunststoff (2.0.2-6) unstable; urgency=medium
 .
   * Team upload
   * Use debian/compat 9 (Closes: #965614)
   * Update Vcs URLs to point to Salsa
Checksums-Sha1:
 4e01c4c74dbf75329b37fb70209e8f922581e884 2033 kunststoff_2.0.2-6.dsc
 270466d571638b2bd46a8fe1d3aa6c588b750ac9 3120 kunststoff_2.0.2-6.debian.tar.xz
 dab4395f8b15b872c031680fe5c7e75957f130a3 8233 
kunststoff_2.0.2-6_amd64.buildinfo
Checksums-Sha256:
 7839722901ad1591a6023848b01016cadf3df34fbba07fd68e2fa8e14c8dd888 2033 
kunststoff_2.0.2-6.dsc
 2964ff3b39d66b3af01c1f6588a0f0580587dc5a691d6cb90f669df5eda6feba 3120 
kunststoff_2.0.2-6.debian.tar.xz
 cd1d153b57bd59f91ad58d3339d2da76b0c496de247bf5a6a4f39c93bf21d152 8233 
kunststoff_2.0.2-6_amd64.buildinfo
Files:
 6b9fb9f8455821cdf90762b7ddaa8030 2033 utils optional kunststoff_2.0.2-6.dsc
 e45e57c66004bcc7af1a582b596c1015 3120 utils optional 
kunststoff_2.0.2-6.debian.tar.xz
 9fba569cb997ad5066e266ee77876c51 8233 utils optional 
kunststoff_2.0.2-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmHD9b8UHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpb+Qg/+PZ8mN+qUxSQCnd6uJ5l7CRPS3Vdp
BZul6QnJ6r1UL6s6ZOUcDryDtpc7Mx5IH/RdnUMIs2oaIaLcBLrrtz/cIE7uGw0d
AauxZUOMQ2LvtnFEC33k02Eb9E9bYiHpkUkXucpwgx1SbQmwX59ChE3PmvxlGnIB
lqmGAzodGhpwmPqCndjcLpZGqtVjexEuy40Ddcl32sBTa64wCejxk++RUFixrlyi
+S/KSD018p5hop/gFemnNdhyvOptcbJlOeksh0gkEuDnSzMq1T0gv6AXlyZ1Tojt
uRSGlk/q1gDA5bElP6uGANedt4TL2LHJQ9HDQPFT3dO4C+w+76AD+yaeufdQHRgd
1HJX6rA5BaC9uzr0TxCUGXwcSagI6RpCG986iFbHUy+bq1dMesUtSnVyZzXbty/D
sSp+tB+/RQWDtlH1hIbKT9HKtz4KzQFSW6Ul6YQIW1hwQC0lfJi60BrRDmSXuShV
y/h24lO83WHZ7eGpoTTZnbu8Q9OkPkSZ95byp5KLg0ejl47szNepyDyTRbGI9axr
UJkaSYzgF5Cv6yDjamaf6XpTScW1XnGRu5YWrrdVvE7ItNrT2VbOqHa0zHxWz8Bj
sL+s1TFWFWE7e9EHJmVPxEPYL67jTqAmOsJhpKQt31aX//VUZC/i4b6s14BmDX4P
2uk403RV0F4yT2A=
=m4Un
-END PGP SIGNATURE End Message ---

Processed: owner 965614

[Debian Bug Tracking System]

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

> owner 965614 !
Bug #965614 [src:kunststoff] kunststoff: Removal of obsolete debhelper compat 5 
and 6 in bookworm
Owner recorded as tony mancill .
> thanks
Stopping processing here.

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

Bug#1001882: marked as done (0ad: FTBFS on armhf: error: ‘-mfloat-abi=hard’: selected architecture lacks an FPU)

[Debian Bug Tracking System]

Your message dated Thu, 23 Dec 2021 03:18:35 +
with message-id 
and subject line Bug#1001882: fixed in 0ad 0.0.25b-1.1
has caused the Debian Bug report #1001882,
regarding 0ad: FTBFS on armhf: error: ‘-mfloat-abi=hard’: selected architecture 
lacks an FPU
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.)


-- 
1001882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: 0ad
Version: 0.0.25b-1
Severity: serious
Tags: ftbfs
Justification: ftbfs
X-Debbugs-Cc: z...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=0ad=armhf=0.0.25b-1%2Bb1=1639777042=0


error: failed to run custom build command for `mozglue-static v0.1.0 
(/<>/libraries/source/spidermonkey/mozjs-78.6.0/mozglue/static/rust)`

Caused by:
  process didn't exit successfully: 
`/<>/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/debug/build/mozglue-static-db2fd9029278a596/build-script-build`
 (exit status: 1)
  --- stdout
  TARGET = Some("armv7-unknown-linux-gnueabihf")
  OPT_LEVEL = Some("1")
  HOST = Some("armv7-unknown-linux-gnueabihf")
  CXX_armv7-unknown-linux-gnueabihf = None
  CXX_armv7_unknown_linux_gnueabihf = Some(" /usr/bin/g++")
  CXXFLAGS_armv7-unknown-linux-gnueabihf = None
  CXXFLAGS_armv7_unknown_linux_gnueabihf = 
Some("-I/<>/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/dist/system_wrappers
 -include 
/<>/libraries/source/spidermonkey/mozjs-78.6.0/config/gcc_hidden.h 
-fstack-protector-strong -DDEBUG=1 -DEXPORT_JS_API -DMOZ_HAS_MOZGLUE 
-I/<>/libraries/source/spidermonkey/mozjs-78.6.0/js/src/rust 
-I/<>/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/js/src/rust
 
-I/<>/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/dist/include
 -fPIC -DMOZILLA_CLIENT -include 
/<>/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/js/src/js-confdefs.h
 -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wempty-body -Wignored-qualifiers 
-Woverloaded-virtual -Wpointer-arith -Wsign-compare -Wtype-limits 
-Wunreachable-code -Wwrite-strings -Wno-invalid-offsetof -Wc++2a-compat 
-Wduplicated-cond -Wimplicit-fallthrough -Wunused-function -Wunused-variable 
-Wno-error=maybe-uninitialized -Wno-error=deprecated-declarations 
-Wno-error=array-bounds -Wno-error=coverage-mismatch 
-Wno-error=free-nonheap-object -Wno-multistatement-macros 
-Wno-error=class-memaccess -Wno-error=deprecated-copy -Wformat 
-Wformat-overflow=2 -Wno-noexcept-type -fno-sized-deallocation -fno-aligned-new 
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fno-rtti -ffunction-sections -fdata-sections 
-fno-exceptions -fno-math-errno -pthread -pipe -g -fno-omit-frame-pointer 
-funwind-tables -DMOZILLA_CONFIG_H")
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some("true")
  CARGO_CFG_TARGET_FEATURE = None
  running: "/usr/bin/g++" "-O1" "-ffunction-sections" "-fdata-sections" "-fPIC" 
"-g" "-fno-omit-frame-pointer" "-march=armv7-a" 
"-I/<>/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/dist/system_wrappers"
 "-include" 
"/<>/libraries/source/spidermonkey/mozjs-78.6.0/config/gcc_hidden.h"
 "-fstack-protector-strong" "-DDEBUG=1" "-DEXPORT_JS_API" "-DMOZ_HAS_MOZGLUE" 
"-I/<>/libraries/source/spidermonkey/mozjs-78.6.0/js/src/rust" 
"-I/<>/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/js/src/rust"
 
"-I/<>/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/dist/include"
 "-fPIC" "-DMOZILLA_CLIENT" "-include" 
"/<>/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/js/src/js-confdefs.h"
 "-Wdate-time" "-D_FORTIFY_SOURCE=2" "-Wall" "-Wempty-body" 
"-Wignored-qualifiers" "-Woverloaded-virtual" "-Wpointer-arith" 
"-Wsign-compare" "-Wtype-limits" "-Wunreachable-code" "-Wwrite-strings" 
"-Wno-invalid-offsetof" "-Wc++2a-compat" "-Wduplicated-cond" 
"-Wimplicit-fallthrough" "-Wunused-function" "-Wunused-variable" 
"-Wno-error=maybe-uninitialized" "-Wno-error=deprecated-declarations" 
"-Wno-error=array-bounds" "-Wno-error=coverage-mismatch" 
"-Wno-error=free-nonheap-object" "-Wno-multistatement-macros" 
"-Wno-error=class-memaccess" "-Wno-error=deprecated-copy" "-Wformat" 
"-Wformat-overflow=2" "-Wno-noexcept-type" "-fno-sized-deallocation" 
"-fno-aligned-new" "-g" "-O2" "-ffile-prefix-map=/<>=." 
"-fstack-protector-strong" "-Wformat" "-Werror=format-security" "-fno-rtti" 
"-ffunction-sections" "-fdata-sections" "-fno-exceptions" "-fno-math-errno" 
"-pthread" "-pipe" "-g" "-fno-omit-frame-pointer" "-funwind-tables" 
"-DMOZILLA_CONFIG_H" "-I" 
"/<>/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/js/src"
 "-I" 

Bug#1000336: numba: FTBFS with Python 3.10

[Diane Trout]

On Wed, 2021-12-22 at 22:24 +0530, Nilesh Patra wrote:
> 
> Upstream has mentioned that it has been fixed upstream. Diane, could
> you
> please do the needful and upload?
> 
> Actually because of the current state of numba, several reverse
> depends are FTBFS so it's
> bit urgent to push. Apologies for getting on your nerves, though.


I tried. but numba needs tbb version >= 2021. I tried to update tbb but
ran into problems trying to build it.

I pushed the compatibility patch to a python-3-10-compatibility branch
on salsa for the moment.



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

Bug#999061: marked as done (libimage-metadata-jpeg-perl: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Thu, 23 Dec 2021 01:03:32 +
with message-id 
and subject line Bug#999061: fixed in libimage-metadata-jpeg-perl 0.153-1.2
has caused the Debian Bug report #999061,
regarding libimage-metadata-jpeg-perl: 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.)


-- 
999061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libimage-metadata-jpeg-perl
Version: 0.153-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: libimage-metadata-jpeg-perl
Source-Version: 0.153-1.2
Done: gregor herrmann 

We believe that the bug you reported is fixed in the latest version of
libimage-metadata-jpeg-perl, 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.
gregor herrmann  (supplier of updated 
libimage-metadata-jpeg-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 18 Dec 2021 01:29:50 CET
Source: libimage-metadata-jpeg-perl
Binary: 
Architecture: source
Version: 0.153-1.2
Distribution: unstable
Urgency: medium
Maintainer: Rene Weber 
Changed-By: gregor herrmann 
Description: 
Closes: 999061
Changes:
 libimage-metadata-jpeg-perl (0.153-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "missing required debian/rules targets build-arch and/or build-
 indep": add missing targets to debian/rules.
 (Closes: #999061)
Checksums-Sha256: 
 f8c92093bb02f3ed6e40bdac4259233cf85835b4bc9cec57ce738b00a3291d4f 1994 
libimage-metadata-jpeg-perl_0.153-1.2.dsc
 960c1bb4a49d93d57f657f80b992080ff47799c1747dbb1a96b884849d3fb109 10129 
libimage-metadata-jpeg-perl_0.153-1.2.diff.gz
 73995370d53ac5cb4f48d7c6147566412dc2f9b9c621d96f545277c3b53411b4 5986 
libimage-metadata-jpeg-perl_0.153-1.2_sourceonly.buildinfo
Checksums-Sha1: 
 ed1bb6139016aa49ccce86551b9c6abb48718709 1994 
libimage-metadata-jpeg-perl_0.153-1.2.dsc
 e381df94cc61059d39255620e5e6316757b531b1 10129 
libimage-metadata-jpeg-perl_0.153-1.2.diff.gz
 eb4fc09b4e497826f0ee21f934c6ea8f559bcee3 5986 
libimage-metadata-jpeg-perl_0.153-1.2_sourceonly.buildinfo
Files: 
 01897b2aa9f7b84f43bbf38e50817155 1994 perl optional 
libimage-metadata-jpeg-perl_0.153-1.2.dsc
 823e831dbd4654c9243d8fe8a14643e4 10129 perl optional 
libimage-metadata-jpeg-perl_0.153-1.2.diff.gz
 fabfdbef29709aa2fcfc04f3016eb050 5986 - - 
libimage-metadata-jpeg-perl_0.153-1.2_sourceonly.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmG9K39fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbKww/9FjwfE9ACIi5YGqpuNu4jzYCSJMBvzklaFVTLh9bYKLd4R1i/zKA1Ji1I
n5RMsI81nPZkiupy4jz3gVk2NMTJCuOTXPMERzwG+jG+C5qi/CPfqCnah7BTv6PD
qkh5hCwtNnvzMIdOVo7TXHFvhy+t9H/+dASMw4g52IRHJ+WHWHe2YMbj/24p8drS
JZFJECo4hJWY219Izl6p4j+J9sxwr5sqVGxA9F691T9pYwaoY8hJQZIcjOeFOn7q
phRZ1wziKLAtpcU5BnSTOj0aLoP+FF/hmBAsuAdO7nqKC0caX0VYIb6yU6ssi7dn
Roy263GSQ7E1YgA+z9hlGH7YwTIzOz5VsdmWV+ZokbxHvExOxl67D/02Kzid8aMx
lisrF1yHyydiAWrlmNPf95yfEXHd8KduG9d4F363zMUkh79L3AryevHRXq1r26G8
hwD1Hel10wfya/AmXnrMUoa8Y1ilTAI+4HDw+VjgOzmXZfdOpCMHE/VpmuuiYyBu
3R72v8J9WonKmeOfQ+xGl+UonLgHAk2KinN1kJi3BiF3aFWxsMdfBTazGpth57HB

Bug#1001292: deepdiff: needs update for python3.10: 'Mapping' from 'collections' is removed

[Louis-Philippe Véronneau]

This package is also pretty old, as upstream is at 5.6.0.

It seems upstream tests for 3.10 in their CI and it passes? I would
argue the "right" course of action here, instead of adding a
Debian-specific patch, would be to update the package to the latest
upstream version.

Cheers,

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1002344: hy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

[Tianon Gravi]

On Wed, 22 Dec 2021 at 00:04, Lucas Nussbaum  wrote:
> Source: hy
> Version: 0.19.0-2
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20211220 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> ...
> 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.

Ouch, thanks for the report.  I think the best fix for this is going
to be updating the package to the 1.0a3 upstream release (because I'm
fairly sure this is really about Hy 0.19 not actually supporting
Python 3.10 yet and the 1.0a3 release does), however that bump
includes the landmine of a complete documentation refactor that
creates a bit of a complex cycle with (the new)
https://github.com/hylang/sphinxcontrib-hydomain repository. 

I've played with building those together as a multiorig package (given
both the dependency cycle and that there aren't likely to be many/any
other consumers of "sphinxcontrib-hydomain" at this time), and ran
into a number of (hopefully minor?) problems, the first of which being
versioning (that repository has a tagged version, but it isn't
compatible with the latest Hy release nor the version of Sphinx in
Debian, but getting a commit that's good enough for the latter doesn't
fully resolve the former and requires further patching).

However, I'm definitely in a bit over my head here, so I'm adding
debian-python to CC hoping that perhaps someone there has some good
advice or ideas (maybe even a spare cycle or two). 

My (non-functional) WIP can be found at
https://salsa.debian.org/hy-team/hy/-/compare/master...1.0a3 

If I bypass the Sphinx bits, I run into "INTERNALERROR> IndexError:
list index out of range" (and the full backtrace appears to all be in
non-Hy codelike pytest and "pluggy"), which I *think* is related to
funcparserlib needing to be 1.0.0a0+
(https://github.com/hylang/hy/pull/2164), but I am not certain.

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD

Bug#1002422: marked as done (python-dcos: FTBFS: ERROR tests/test_config.py - AttributeError: module 'collections' has no attr...)

[Debian Bug Tracking System]

Your message dated Wed, 22 Dec 2021 23:33:35 +
with message-id 
and subject line Bug#1002422: fixed in python-dcos 0.2.0-5
has caused the Debian Bug report #1002422,
regarding python-dcos: FTBFS: ERROR tests/test_config.py - AttributeError: 
module 'collections' has no attr...
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_install --no-py2
> + PKGOS_USE_PY2=yes
> + PKGOS_USE_PY3=yes
> + PKGOS_IN_TMP=no
> + PKGOS_USE_PY2=no
> + shift
> + dpkg-parsechangelog -SSource
> + SRC_PKG_NAME=python-dcos
> + echo python-dcos
> + sed s/python-//
> + PY_MODULE_NAME=dcos
> + [ no = yes ]
> + [ yes = yes ]
> + py3versions -vr
> + PYTHON3S=3.10 3.9
> + [ no = yes ]
> + [ yes = yes ]
> + [ no = yes ]
> + TARGET_DIR=python3-dcos
> + pwd
> + python3.10 setup.py install --install-layout=deb --root 
> /<>/debian/python3-dcos
> /usr/lib/python3/dist-packages/setuptools/dist.py:507: UserWarning: The 
> version specified ('SNAPSHOT') is an invalid version, this may not work as 
> expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 
> for more details.
>   warnings.warn(
> running install
> /usr/lib/python3/dist-packages/setuptools/command/install.py:34: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and 
> pip and other standards-based tools.
>   warnings.warn(
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/dcos
> copying dcos/__init__.py -> build/lib/dcos
> copying dcos/package.py -> build/lib/dcos
> copying dcos/util.py -> build/lib/dcos
> copying dcos/marathon.py -> build/lib/dcos
> copying dcos/options.py -> build/lib/dcos
> copying dcos/errors.py -> build/lib/dcos
> copying dcos/subcommand.py -> build/lib/dcos
> copying dcos/http.py -> build/lib/dcos
> copying dcos/auth.py -> build/lib/dcos
> copying dcos/emitting.py -> build/lib/dcos
> copying dcos/cmds.py -> build/lib/dcos
> copying dcos/mesos.py -> build/lib/dcos
> copying dcos/config.py -> build/lib/dcos
> copying dcos/constants.py -> build/lib/dcos
> copying dcos/jsonitem.py -> build/lib/dcos
> running install_lib
> creating /<>/debian/python3-dcos
> creating /<>/debian/python3-dcos/usr
> creating /<>/debian/python3-dcos/usr/lib
> creating /<>/debian/python3-dcos/usr/lib/python3
> creating /<>/debian/python3-dcos/usr/lib/python3/dist-packages
> creating 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/__init__.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/package.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/util.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/marathon.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/options.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/errors.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/subcommand.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/http.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/auth.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/emitting.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/cmds.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/mesos.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/config.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/constants.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/jsonitem.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> byte-compiling 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos/__init__.py

Bug#1002422: marked as pending in python-dcos

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/python/python-dcos/-/commit/0f5061ca0b1f7014a7033d1abc4d42a3cb30fbff


Add fix-import-from-collections.patch (Closes: #1002422).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1002422

Processed: Bug#1002422 marked as pending in python-dcos

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1002422 [src:python-dcos] python-dcos: FTBFS: ERROR tests/test_config.py - 
AttributeError: module 'collections' has no attr...
Added tag(s) pending.

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

Bug#1001591: [Pkg-mailman-hackers] [Pkg-matrix-maintainers] Bug#1002380: drops attributes used by reverse dependencies

[Pierre-Elliott Bécue]

Jonas Smedegaard  wrote on 22/12/2021 at 23:52:11+0100:
>> Well, I was under the impression that
>> 
>> >>> Concretely I propose to revert this by a (messy) 2.0.0+really0.8.4 
>> >>> release until reverse dependencies can use the newer major version 
>> >>> of mistune.
>> 
>> meant indeed to wait until the reverse dependencies were sorted out 
>> which generally requires to wait until upstream fixes the issue 
>> (except if one likes big quilt patches and maintaining the software's 
>> code on their own).
>
> That is precisely what I did *not* imply (so it seems it was good that I 
> mentioned my non-assumption since apparently you _did_ assume stuff).  
>
> Let me try avoid false assumptions by expanding:
>
> I propose to revert this by a (messy) 2.0.0+really0.8.4 release until 
> reverse dependencies somehow (with or without upstream cooperation) can 
> use the newer major version of mistune (or, if taking unreasonably long, 
> kick any reverse dependencies from testing).

I clearly inferred the impact of what "until reverse dependencies can
use the newed major version of mistune" implied. I think it was
reasonable to do so instead of wondering where your cursor was on that
matter.

But I'm happy to see that you are more relaxed on what you expect!

>> > My proposal is to *collaborate* with your peers in Debian now - not 
>> > continue(!) to make choices without coordination with those packages 
>> > directly affected by those choices.
>> 
>> Maybe you wanted to suggest that I should *collaborate* more, but you 
>> did not write that and, as I tend to try not to assume what one says, 
>> writes or means, I did not read that.
>
> Sorry!
>
> I did indeed mean to encourage more collaboration, and apologize if that 
> failed to get across.
>
>
>> >> If I follow your opinion on this, the following issues arise:
>> >> 
>> >>  1. There is no proper way for software to be mistune 0.8.4 and 
>> >> mistune 2.0.0 compatible at the same way, so the reverse 
>> >> dependencies won't be able to update without mistune 2.0.0 
>> >> being in unstable
>> >
>> > Not sure what you imply by "proper".
>> 
>> appropriate, suitable, relevant, reasonable, …
>> 
>> > There are alternatives to abruptly abandoning support for existing 
>> > functionaling packages already in Debian testing.
>> 
>> Note that since the upload, autopkgtests for the involved 
>> reverse-dependencies were failing and therefore mistune was not 
>> planned to migrate from unstable to testing. There was therefore no 
>> chance mistune would break these packages in testing, and I was not 
>> pressing anyone to sort that out.
>>
>> Now that a serious bug against mistune is opened, even if these 
>> autopkgtests get sorted out because these very reverse-dependencies 
>> are updated, mistune will not migrate anyway (which will prevent to 
>> break other reverse-dependencies).
>
> Yes, I am aware, and that is what I describe as "abruptly": Now that 
> mistune v1 is gone, there is no way to work on any package depending on 
> that except for switching to v2.
>
> ...which is the reason I propose to revert for now.

And I did not say that I refuse this idea. In my first mail I said that
I would like to hear your opinion on how to solve the matter of
unmaintained reverse dependencies, and also that I'd like it to stay as
it is for now.

What I failed to write is that "for now" is not "for three months", but
I fixed that in my second reply to you.

>> Testing is not impacted so far.
>
> Correct.  Unstable is impacted.

-- 
PEB


signature.asc
Description: PGP signature

Bug#1002384: marked as pending in senlin

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/services/senlin/-/commit/c8f1afc4006894bb9b8b48369439374ba18a76d3


* Add install-missing-files.patch.
  * Add fix-import-from-collections.patch (Closes: #1002384).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1002384

Processed: Bug#1002384 marked as pending in senlin

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1002384 [src:senlin] senlin: FTBFS: AttributeError: module 'collections' 
has no attribute 'Mapping'
Added tag(s) pending.

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

Bug#1002377: marked as pending in python-heatclient

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/clients/python-heatclient/-/commit/6958f8e05a95f5b2e319ab2e8aeb7261df963cbd


Add fix-import-from-collections.patch (Closes: #1002377).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1002377

Processed: Bug#1002377 marked as pending in python-heatclient

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1002377 [src:python-heatclient] python-heatclient: FTBFS: AttributeError: 
module 'collections' has no attribute 'Mapping'
Added tag(s) pending.

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

Bug#1002411: marked as done (gcovr: FTBFS: /bin/sh: 1: python3.9/dist-packages: not found)

[Debian Bug Tracking System]

Your message dated Wed, 22 Dec 2021 22:33:31 +
with message-id 
and subject line Bug#1002411: fixed in gcovr 5.0-2
has caused the Debian Bug report #1002411,
regarding gcovr: FTBFS: /bin/sh: 1: python3.9/dist-packages: not found
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYTHONPATH=debian/gcovr/usr/lib/python3.10 python3.9/dist-packages \
> help2man \
>   --name "generate simple coverage reports" \
>   --no-info \
>   --version-string 5.0 \
>   --output debian/gcovr.1 \
>   debian/gcovr/usr/bin/gcovr
> /bin/sh: 1: python3.9/dist-packages: not found
> make[1]: *** [debian/rules:16: override_dh_installman] Error 127


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/gcovr_5.0-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: gcovr
Source-Version: 5.0-2
Done: Wolfgang Silbermayr 

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

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

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

Debian distribution maintenance software
pp.
Wolfgang Silbermayr  (supplier of updated gcovr package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 22 Dec 2021 18:46:13 +0100
Source: gcovr
Architecture: source
Version: 5.0-2
Distribution: unstable
Urgency: medium
Maintainer: Wolfgang Silbermayr 
Changed-By: Wolfgang Silbermayr 
Closes: 1002411
Changes:
 gcovr (5.0-2) unstable; urgency=medium
 .
   * Fix FTBFS due to false assembly of PYTHONPATH during build
 (Closes: #1002411)
Checksums-Sha1:
 86470d3468ec64a5ce8e4c4920069414a24ab48e 1905 gcovr_5.0-2.dsc
 f48c13729d12356a21850dae1f9444674e114e50 3552 gcovr_5.0-2.debian.tar.xz
 b464fc33d99c4dc72677cd4699d26980473965a5 6686 gcovr_5.0-2_amd64.buildinfo
Checksums-Sha256:
 933ec8374b05418ecdc14041a43cdef1e69f198fb21c9a89befb62ab3da6968b 1905 
gcovr_5.0-2.dsc
 03ad1691e08abd05393bf29941b05c98ce8182a668d1564988dadc71ee0a5aac 3552 
gcovr_5.0-2.debian.tar.xz
 c88f31b5ccc44f242e571bdc55bdfd24472aa4b12d95dc984b521def6df2c25a 6686 
gcovr_5.0-2_amd64.buildinfo
Files:
 e4873d33ca84add5c32394e5b32fbc48 1905 devel optional gcovr_5.0-2.dsc
 9801ef262877e5f0ba790f1be2b72e72 3552 devel optional gcovr_5.0-2.debian.tar.xz
 fb636d16c7582aa8faa5c0abc5b59483 6686 devel optional 
gcovr_5.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmHDpaIACgkQfmUo2nUv
G+E4mw/+Psg7tG8jECZ48xvXPdc6FwSN5+QY0gRJxFc3PdVS1Ae2ObALxlEG35RC
ShGHnD4jY59LRgkJPWRUBH5F8GVrP5Y90W2mJjs4qtsT7a2znE3bGL5iGFC4v3oi
Rgazsf6dayHNnPGy6B+ghFKrJkrARXU5cTo7DLRpD9ImOEurZkLxoqKZvP94e5ZH
DQhZxhFX9dOJjXnxCJpRjipFRaWiy2KMTwre5e23o7zP+RXLwpFTJkPrd64i4VQS
fLqgYtzeKJBHxzwcGMslUV1VTBa49AOiGvoRhNuViTNoX80TMpcGk197TfSvA9Ao
y6ue9+iNcMtXNVzi38zEDxwCfOkcgKdjiz9C0RtF92gJ0l/knd3UMnpnAg8CwDHb
GF2a7waJtxk+1CFkuTQQ09lC018VNixrz6JSqAmXyPfs2y8iYQI5TCmVDpaBP/nw
zXopofE/xP9Rf8s+d2rV2oOD39FfCo+zYBxloKXpF/A9BhS0zUYTEBHy405n+uHG
iFDmpgcgAUkTzRI0w/1k9A909AlsfF5s3oggN15kP8CuX0Sr5OjwM+OvEdY5uVQP
id91fGhxaENtPUYagvB+XeXNvfsbohRDQihz8GeMSkOz/+04VP9kbRQEH85YOeyx
O5j8VQmwRFcsPktpM7VGFGD1BFdb8I0BA/kKPPsJfQwpeXulwmM=
=+yVQ
-END PGP SIGNATURE End Message ---

Bug#1002368: marked as pending in python-os-win

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/libs/python-os-win/-/commit/b8ec13455485dd87a0267ccaa9f7d8d7c65cf35d


Add fix-import-from-collections.patch (Closes: #1002368).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1002368

Processed: Bug#1002368 marked as pending in python-os-win

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1002368 [src:python-os-win] python-os-win: FTBFS: AttributeError: module 
'collections' has no attribute 'Iterable'
Added tag(s) pending.

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

Bug#1001591: [Pkg-matrix-maintainers] Bug#1002380: drops attributes used by reverse dependencies

[Jonas Smedegaard]

Quoting Pierre-Elliott Bécue (2021-12-22 21:42:41)
> 
> Jonas Smedegaard  wrote on 22/12/2021 at 21:55:13+0100:
> 
> > [[PGP Signed Part:No public key for 2C7C3146C1A00121 created at 
> > 2021-12-22T21:55:09+0100 using RSA]]
> > Quoting Pierre-Elliott Bécue (2021-12-22 17:08:46)
> >> Jonas Smedegaard  wrote on 22/12/2021 at 
> >> 12:37:21+0100:
> >> > Releasing a new major release of mistune has caused several 
> >> > packages to no longer be usable at all.
> >> >
> >> > I consider this a serious issue, and have raised severity 
> >> > accordingly.
> >> >
> >> > At least python-m2r have no support for mistune v2 in sight (and 
> >> > its newer fork - python-m2r2 - does not either). Concretely I 
> >> > propose to revert this by a (messy) 2.0.0+really0.8.4 release 
> >> > until reverse dependencies can use the newer major version of 
> >> > mistune.
> >> >
> >> > It seems that a release of python3-django-hyperkitty requiring 
> >> > mistune v2 has already been uploaded to unstable as well.  That 
> >> > is very unfortunate, and will need to be rolled back as well.  
> >> > Mailman maintainers cc'ed.
> >> >
> >> > Please in future make sure to check reverse dependencies *before* 
> >> > releasing a major new upstream release to unstable, because 
> >> > reversal is messy (complicates package versioning).
> >> >
> >> >
> >> > Kind regards, and thanks for maintaining mistune,
> >> 
> >> The issue is that many reverse dependencies of mistune are not 
> >> maintained.
> >
> > I assume (in good faith) that you did not mean to say that the 
> > _Debian_ packages reverse depending on mistune are all unmaintained.
> 
> I'm not sure that there is anything to assume. I wrote "many reverse 
> dependencies of mistune are not maintained", and making it mean "the 
> _Debian_ packages reverse depending on mistune are all unmaintained" 
> would require some hard work.
> 
> > Please note that I did not propose to wait until _upstreams_ of 
> > reverse dependencies can use newer major version of mistune.
> 
> Well, I was under the impression that
> 
> >>> Concretely I propose to revert this by a (messy) 2.0.0+really0.8.4 
> >>> release until reverse dependencies can use the newer major version 
> >>> of mistune.
> 
> meant indeed to wait until the reverse dependencies were sorted out 
> which generally requires to wait until upstream fixes the issue 
> (except if one likes big quilt patches and maintaining the software's 
> code on their own).

That is precisely what I did *not* imply (so it seems it was good that I 
mentioned my non-assumption since apparently you _did_ assume stuff).  

Let me try avoid false assumptions by expanding:

I propose to revert this by a (messy) 2.0.0+really0.8.4 release until 
reverse dependencies somehow (with or without upstream cooperation) can 
use the newer major version of mistune (or, if taking unreasonably long, 
kick any reverse dependencies from testing).


> > My proposal is to *collaborate* with your peers in Debian now - not 
> > continue(!) to make choices without coordination with those packages 
> > directly affected by those choices.
> 
> Maybe you wanted to suggest that I should *collaborate* more, but you 
> did not write that and, as I tend to try not to assume what one says, 
> writes or means, I did not read that.

Sorry!

I did indeed mean to encourage more collaboration, and apologize if that 
failed to get across.


> >> If I follow your opinion on this, the following issues arise:
> >> 
> >>  1. There is no proper way for software to be mistune 0.8.4 and 
> >> mistune 2.0.0 compatible at the same way, so the reverse 
> >> dependencies won't be able to update without mistune 2.0.0 
> >> being in unstable
> >
> > Not sure what you imply by "proper".
> 
> appropriate, suitable, relevant, reasonable, …
> 
> > There are alternatives to abruptly abandoning support for existing 
> > functionaling packages already in Debian testing.
> 
> Note that since the upload, autopkgtests for the involved 
> reverse-dependencies were failing and therefore mistune was not 
> planned to migrate from unstable to testing. There was therefore no 
> chance mistune would break these packages in testing, and I was not 
> pressing anyone to sort that out.
>
> Now that a serious bug against mistune is opened, even if these 
> autopkgtests get sorted out because these very reverse-dependencies 
> are updated, mistune will not migrate anyway (which will prevent to 
> break other reverse-dependencies).

Yes, I am aware, and that is what I describe as "abruptly": Now that 
mistune v1 is gone, there is no way to work on any package depending on 
that except for switching to v2.

...which is the reason I propose to revert for now.


> Testing is not impacted so far.

Correct.  Unstable is impacted.


 - Jonas

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

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

Bug#1002365: marked as done (pynn: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.10 3.9" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Wed, 22 Dec 2021 21:35:39 +
with message-id 
and subject line Bug#1002365: fixed in pynn 0.10.0-1
has caused the Debian Bug report #1002365,
regarding pynn: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i 
python{version} -p "3.10 3.9" returned exit code 13
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cp -a test test_save
> rm -f \
> test/system/scenarios/__init__.py \
> test/unittests/test_brian.py \
> test/system/test_brian.py \
> test/system/test_brian2.py \
> test/system/test_hardware_brainscales.py \
> test/system/test_moose.py \
> test/system/scenarios/registry.py \
> test/system/test_serialization.py \
> test/system/test_nest.py \
> test/system/test_neuroml.py \
> test/system/test_neuron.py \
> test/unittests/test_random.py \
> test/unittests/test_neuron.py
> dh_auto_test
> I: pybuild base:237: cd /<>/.pybuild/cpython3_3.10_pynn/build; 
> python3.10 -m nose -v test
> /<>/.pybuild/cpython3_3.10_pynn/build/pyNN/recording/__init__.py:262:
>  SyntaxWarning: "is not" with a literal. Did you mean "!="?
>   if variables is not 'all':
> test__add__assembly (unittests.test_assembly.AssemblyTest) ... ok
> test__add__population (unittests.test_assembly.AssemblyTest) ... ok
> test__homogeneous_synapses (unittests.test_assembly.AssemblyTest) ... ok
> test__len__ (unittests.test_assembly.AssemblyTest) ... ok
> test__non_homogeneous_synapses (unittests.test_assembly.AssemblyTest) ... ok
> test_add_inplace_assembly (unittests.test_assembly.AssemblyTest) ... ok
> test_add_inplace_population (unittests.test_assembly.AssemblyTest) ... ok
> test_add_invalid_object (unittests.test_assembly.AssemblyTest) ... ok
> test_all_cells (unittests.test_assembly.AssemblyTest) ... ok
> test_all_iterator (unittests.test_assembly.AssemblyTest) ... ok
> test_conductance_based (unittests.test_assembly.AssemblyTest) ... ok
> test_create_with_non_population_should_raise_Exception 
> (unittests.test_assembly.AssemblyTest) ... ok
> test_create_with_one_population (unittests.test_assembly.AssemblyTest) ... ok
> test_create_with_two_populations (unittests.test_assembly.AssemblyTest) ... ok
> test_create_with_zero_populations (unittests.test_assembly.AssemblyTest) ... 
> ok
> test_describe (unittests.test_assembly.AssemblyTest) ... ok
> test_first_and_last_id (unittests.test_assembly.AssemblyTest) ... ok
> test_getSpikes (unittests.test_assembly.AssemblyTest) ... ok
> test_get_data_with_gather (unittests.test_assembly.AssemblyTest) ... 
> /<>/.pybuild/cpython3_3.10_pynn/build/pyNN/mock/recording.py:24: 
> FutureWarning: arrays to stack must be passed as a "sequence" type such as 
> list or tuple. Support for non-sequence iterables such as generators is 
> deprecated as of NumPy 1.16 and will raise an error in the future.
>   return numpy.vstack((numpy.random.uniform(size=n_samples) for id in ids)).T
> ok
> test_get_gsyn (unittests.test_assembly.AssemblyTest) ... ok
> test_get_multiple_homogeneous_params_with_gather 
> (unittests.test_assembly.AssemblyTest) ... ok
> test_get_multiple_inhomogeneous_params_with_gather 
> (unittests.test_assembly.AssemblyTest) ... ok
> test_get_multiple_params_no_gather (unittests.test_assembly.AssemblyTest) ... 
> ok
> test_get_population (unittests.test_assembly.AssemblyTest) ... ok
> test_get_sequence_param (unittests.test_assembly.AssemblyTest) ... ERROR
> test_get_single_param_with_gather (unittests.test_assembly.AssemblyTest) ... 
> ok
> test_get_v (unittests.test_assembly.AssemblyTest) ... ok
> test_getitem_array (unittests.test_assembly.AssemblyTest) ... ok
> test_getitem_int (unittests.test_assembly.AssemblyTest) ... ok
> test_getitem_slice (unittests.test_assembly.AssemblyTest) ... ok
> test_id_to_index (unittests.test_assembly.AssemblyTest) ... ok
> test_id_to_index_with_nonexistent_id (unittests.test_assembly.AssemblyTest) 
> ... ok
> test_ids_should_not_be_counted_twice (unittests.test_assembly.AssemblyTest) 
> ... ok
> test_initialize (unittests.test_assembly.AssemblyTest) ... ok
> test_inject (unittests.test_assembly.AssemblyTest) ... ok
> test_iter 

Bug#1001591: [Pkg-matrix-maintainers] Bug#1002380: drops attributes used by reverse dependencies

[Pierre-Elliott Bécue]

Jonas Smedegaard  wrote on 22/12/2021 at 21:55:13+0100:

> [[PGP Signed Part:No public key for 2C7C3146C1A00121 created at 
> 2021-12-22T21:55:09+0100 using RSA]]
> Quoting Pierre-Elliott Bécue (2021-12-22 17:08:46)
>> 
>> Jonas Smedegaard  wrote on 22/12/2021 at 12:37:21+0100:
>> > Releasing a new major release of mistune has caused several packages 
>> > to no longer be usable at all.
>> >
>> > I consider this a serious issue, and have raised severity 
>> > accordingly.
>> >
>> > At least python-m2r have no support for mistune v2 in sight (and its 
>> > newer fork - python-m2r2 - does not either). Concretely I propose to 
>> > revert this by a (messy) 2.0.0+really0.8.4 release until reverse 
>> > dependencies can use the newer major version of mistune.
>> >
>> > It seems that a release of python3-django-hyperkitty requiring 
>> > mistune v2 has already been uploaded to unstable as well.  That is 
>> > very unfortunate, and will need to be rolled back as well.  Mailman 
>> > maintainers cc'ed.
>> >
>> > Please in future make sure to check reverse dependencies *before* 
>> > releasing a major new upstream release to unstable, because reversal 
>> > is messy (complicates package versioning).
>> >
>> >
>> > Kind regards, and thanks for maintaining mistune,
>> 
>> The issue is that many reverse dependencies of mistune are not
>> maintained.
>
> I assume (in good faith) that you did not mean to say that the _Debian_ 
> packages reverse depending on mistune are all unmaintained.

I'm not sure that there is anything to assume. I wrote "many reverse
dependencies of mistune are not maintained", and making it mean "the
_Debian_ packages reverse depending on mistune are all unmaintained"
would require some hard work.

> Please note that I did not propose to wait until _upstreams_ of reverse 
> dependencies can use newer major version of mistune.

Well, I was under the impression that

>>> Concretely I propose to revert this by a (messy) 2.0.0+really0.8.4
>>> release until reverse dependencies can use the newer major version
>>> of mistune.

meant indeed to wait until the reverse dependencies were sorted out
which generally requires to wait until upstream fixes the issue (except
if one likes big quilt patches and maintaining the software's code on
their own).

> My proposal is to *collaborate* with your peers in Debian now - not 
> continue(!) to make choices without coordination with those packages 
> directly affected by those choices.

Maybe you wanted to suggest that I should *collaborate* more, but you
did not write that and, as I tend to try not to assume what one says,
writes or means, I did not read that.

>> If I follow your opinion on this, the following issues arise:
>> 
>>  1. There is no proper way for software to be mistune 0.8.4 and 
>> mistune 2.0.0 compatible at the same way, so the reverse 
>> dependencies won't be able to update without mistune 2.0.0 being 
>> in unstable
>
> Not sure what you imply by "proper".

appropriate, suitable, relevant, reasonable, …

> There are alternatives to abruptly abandoning support for existing
> functionaling packages already in Debian testing.

Note that since the upload, autopkgtests for the involved
reverse-dependencies were failing and therefore mistune was not planned
to migrate from unstable to testing. There was therefore no chance
mistune would break these packages in testing, and I was not pressing
anyone to sort that out.

Now that a serious bug against mistune is opened, even if these
autopkgtests get sorted out because these very reverse-dependencies are
updated, mistune will not migrate anyway (which will prevent to break
other reverse-dependencies).

>>  2. I'll need mailman3 to be able to enter testing at some point and I 
>> don't think we can expect it to wait for software that is no 
>> longer maintained upstream
>
> At some point, yes. I see no reason to rush that to the point of not
> coordinating with involved packages.

>> Apart from these two points, there are multiple cases where software 
>> are updated despite the impact on the reverse dependencies. Typically 
>> Python updates don't wait for dependencies to be ready in case of 
>> breaking changes, and that looks to me quite normal, despite it 
>> bringing more work to me as a mailman or python packages maintainer.
>
> I guess coordination within the Python team may be more relaxed.
>
> Is your point that coordination among package maintainers more generally 
> - not within the Python team - is not important?

I don't know how you fetch your assumptions on what I think or mean.

While coordination is certainly a good thing in itself, I consider it
less essential in the months that follow a stable release, because
everything is moving fast due to the delay the freeze
induced. Coordinating in this context tends to be counter productive,
and I generally accept that the packages I depend on can break mine and
so on.

>> I'd be happy to hear about how you suggest me to 

Processed: reassign 1002207 to dh-python, forcibly merging 1002182 1002207, affects 1002207

[Debian Bug Tracking System]

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

> reassign 1002207 dh-python
Bug #1002207 [src:pantalaimon] pantalaimon: FTBFS: AttributeError: 'NoneType' 
object has no attribute 'split'
Bug reassigned from package 'src:pantalaimon' to 'dh-python'.
No longer marked as found in versions pantalaimon/0.10.3-1.
Ignoring request to alter fixed versions of bug #1002207 to the same values 
previously set
> forcemerge 1002182 1002207
Bug #1002182 [dh-python] qutebrowser: FTBFS: AttributeError: 'NoneType' object 
has no attribute 'split'
Bug #1002290 [dh-python] dh_python3 needing contextvars -- not a problem with 
my package, then?
Bug #1002207 [dh-python] pantalaimon: FTBFS: AttributeError: 'NoneType' object 
has no attribute 'split'
Severity set to 'grave' from 'serious'
Added indication that 1002207 affects qutebrowser,python-anyio
Marked as found in versions dh-python/5.20211217 and dh-python/5.20211213.
Added tag(s) confirmed.
Bug #1002290 [dh-python] dh_python3 needing contextvars -- not a problem with 
my package, then?
Merged 1002182 1002207 1002290
> affects 1002207 pantalaimon
Bug #1002207 [dh-python] pantalaimon: FTBFS: AttributeError: 'NoneType' object 
has no attribute 'split'
Bug #1002182 [dh-python] qutebrowser: FTBFS: AttributeError: 'NoneType' object 
has no attribute 'split'
Bug #1002290 [dh-python] dh_python3 needing contextvars -- not a problem with 
my package, then?
Added indication that 1002207 affects pantalaimon
Added indication that 1002182 affects pantalaimon
Added indication that 1002290 affects pantalaimon
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

Your message dated Wed, 22 Dec 2021 21:04:10 +
with message-id 
and subject line Bug#999099: fixed in macutils 2.0b3-17
has caused the Debian Bug report #999099,
regarding macutils: 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.)


-- 
999099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999099
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: macutils
Version: 2.0b3-16
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: macutils
Source-Version: 2.0b3-17
Done: Eric Sharkey 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 22 Dec 2021 14:14:27 -0500
Source: macutils
Architecture: source
Version: 2.0b3-17
Distribution: unstable
Urgency: low
Maintainer: Eric Sharkey 
Changed-By: Eric Sharkey 
Closes: 965711 999099
Changes:
 macutils (2.0b3-17) unstable; urgency=low
 .
   * Upgrade standards (Closes: #965711)
   * Add standard rules targets (Closes: #999099)
   * Patch to clean up compiler warnings during build
Checksums-Sha1:
 6581ff1b7fc006011096267286f72e3aea7eff8a 1674 macutils_2.0b3-17.dsc
 13468d7f7fc14f3634450f12a158187b743ea2c0 8116 macutils_2.0b3-17.debian.tar.xz
 95ea762b0a818c981ee40d8135ba75c236ed9458 7013 macutils_2.0b3-17_amd64.buildinfo
Checksums-Sha256:
 36106a29e1ecd03e6f6bb64c93e0937bb3ea4c9527a228f3467aff758ebc924d 1674 
macutils_2.0b3-17.dsc
 f8fdb2cef1a8379cf149d980225bb0b4f2fc3a8bff9a9b90f7e6882ca359b452 8116 
macutils_2.0b3-17.debian.tar.xz
 70330daea6defa82477b8559ff514ac4b469dfda283fa2f2070f57b6f2ac0ee5 7013 
macutils_2.0b3-17_amd64.buildinfo
Files:
 a7151f96bc8929db32d0c0d09a781082 1674 otherosfs optional macutils_2.0b3-17.dsc
 2b4e21c203f74396556a59729d0500c1 8116 otherosfs optional 
macutils_2.0b3-17.debian.tar.xz
 72b64146b1ec72986e99e016a2b64228 7013 otherosfs optional 
macutils_2.0b3-17_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEELpjU0Pi3I6H/MmtbReLNpaf9kPkFAmHDe9oACgkQReLNpaf9
kPnyPBAAsf/Eoqcx2dYqeuXVApWVcL/s8BzIUTOysScJQ2tCkJ7r/NiYjg9dPJ/U
7gYrSK+38KKjDrC6o3y6GHWro0XUJwArCcDjDt+0q1YiB5oKffc3FUvyTjyOPUmj
EQ3vSZSk2tgus7MK4ljVOZAPotyXXAo0BVk0jsYPcDDWhMqSdB/QkH11fPt7GHKb
fXXx0GFo5VXgl8i9mk8Hq/hhDSe23XV3O+p38lei2ZVNEv/Y5pSsPfSIhcxXqDtK
yLyQU1emr9B0G0K+0EE0taO6j0HOfP8wDQpRr4DNLrbo8BCQaEVWdyV2SPZgp/Rs
DlNEIM+0RuXzm9y6/RsSrJPhiyug2SGauN8i77SRbF6lLM+MYrYqzzTPGVeObceJ
twfOkd+EFvL2HEMOEJhJ/0F0WZljzX8YUpZBvTcPdUdbFPBl1YrmSIARY3c7mXRy
Rb+E6ps6Do48eo+R6gUGj4WnkHSFg8uIAIqlCZBCqFsHA8kANIBVxhcafgDDMMrM
Vl0M95JUbahqC5fuqt3tMKR4IN0XusZ0TpW7u6ZfAjc7wEwtfvdgrZpKznzga76S
NoqaqU2pvCqR2Xh38cCVWhclzJdPECZyaAOpmsfQVDRJoObwV1RnOkkJfxPUh86a
J5bFTg8LH8eLaLpC/YCWI2galDFfK6jpacgJNwv1dWDg0u905Aw=
=SWX3
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Wed, 22 Dec 2021 21:04:10 +
with message-id 
and subject line Bug#965711: fixed in macutils 2.0b3-17
has caused the Debian Bug report #965711,
regarding macutils: 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.)


-- 
965711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: macutils
Version: 2.0b3-16
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package macutils 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: macutils
Source-Version: 2.0b3-17
Done: Eric Sharkey 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 22 Dec 2021 14:14:27 -0500
Source: macutils
Architecture: source
Version: 2.0b3-17
Distribution: unstable
Urgency: low
Maintainer: Eric Sharkey 
Changed-By: Eric Sharkey 
Closes: 965711 999099
Changes:
 macutils (2.0b3-17) unstable; urgency=low
 .
   * Upgrade standards (Closes: #965711)
   * Add standard rules targets (Closes: #999099)
   * Patch to clean up compiler warnings during build
Checksums-Sha1:
 6581ff1b7fc006011096267286f72e3aea7eff8a 1674 macutils_2.0b3-17.dsc
 13468d7f7fc14f3634450f12a158187b743ea2c0 8116 macutils_2.0b3-17.debian.tar.xz
 95ea762b0a818c981ee40d8135ba75c236ed9458 7013 macutils_2.0b3-17_amd64.buildinfo
Checksums-Sha256:
 36106a29e1ecd03e6f6bb64c93e0937bb3ea4c9527a228f3467aff758ebc924d 1674 
macutils_2.0b3-17.dsc
 f8fdb2cef1a8379cf149d980225bb0b4f2fc3a8bff9a9b90f7e6882ca359b452 8116 
macutils_2.0b3-17.debian.tar.xz
 70330daea6defa82477b8559ff514ac4b469dfda283fa2f2070f57b6f2ac0ee5 7013 
macutils_2.0b3-17_amd64.buildinfo
Files:
 a7151f96bc8929db32d0c0d09a781082 1674 otherosfs optional macutils_2.0b3-17.dsc
 2b4e21c203f74396556a59729d0500c1 8116 otherosfs optional 
macutils_2.0b3-17.debian.tar.xz
 72b64146b1ec72986e99e016a2b64228 7013 otherosfs optional 
macutils_2.0b3-17_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEELpjU0Pi3I6H/MmtbReLNpaf9kPkFAmHDe9oACgkQReLNpaf9
kPnyPBAAsf/Eoqcx2dYqeuXVApWVcL/s8BzIUTOysScJQ2tCkJ7r/NiYjg9dPJ/U
7gYrSK+38KKjDrC6o3y6GHWro0XUJwArCcDjDt+0q1YiB5oKffc3FUvyTjyOPUmj
EQ3vSZSk2tgus7MK4ljVOZAPotyXXAo0BVk0jsYPcDDWhMqSdB/QkH11fPt7GHKb
fXXx0GFo5VXgl8i9mk8Hq/hhDSe23XV3O+p38lei2ZVNEv/Y5pSsPfSIhcxXqDtK
yLyQU1emr9B0G0K+0EE0taO6j0HOfP8wDQpRr4DNLrbo8BCQaEVWdyV2SPZgp/Rs
DlNEIM+0RuXzm9y6/RsSrJPhiyug2SGauN8i77SRbF6lLM+MYrYqzzTPGVeObceJ
twfOkd+EFvL2HEMOEJhJ/0F0WZljzX8YUpZBvTcPdUdbFPBl1YrmSIARY3c7mXRy
Rb+E6ps6Do48eo+R6gUGj4WnkHSFg8uIAIqlCZBCqFsHA8kANIBVxhcafgDDMMrM
Vl0M95JUbahqC5fuqt3tMKR4IN0XusZ0TpW7u6ZfAjc7wEwtfvdgrZpKznzga76S
NoqaqU2pvCqR2Xh38cCVWhclzJdPECZyaAOpmsfQVDRJoObwV1RnOkkJfxPUh86a
J5bFTg8LH8eLaLpC/YCWI2galDFfK6jpacgJNwv1dWDg0u905Aw=
=SWX3
-END PGP SIGNATURE End Message ---

Bug#997845: growlight: autopkgtest regression: log repeats until it times out

[Paul Gevers]

Hi Nick,

On 21-12-2021 14:53, nick black wrote:

alright, i'm confident that this is resolved.


I triggered autopkgtest runs in testing with both growlight and 
notcurses from unstable. They are already running for a long time and I 
fear they are timing out again:


https://ci.debian.net/user/britney/jobs?package=growlight=growlight%2F1.2.38-2%5B%5D=testing

So it doesn't look resolved.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#999620: pktanon: autopkgtest regression on armhf

[Paul Gevers]

Hi Sascha,

On 20-12-2021 15:24, Sascha Steinbiss wrote:

We have porters for architecture specific support. However, I'm not
totally convinced yet it's architecture specific.


Maybe. You noted that it seems to work fine on a machine with the same
architecture but different specs.


I think you misunderstood me then. We only have one host where we run 
armhf tests (we do have other arm64 hosts, but we use those for arm64 
testing).



Is there anything I can try out for you on our armhf host to help debug
the issue? Run the command with more debug options? Grab an output file
from somewhere?

Hmmm. Since I am pretty unfamiliar with the source and/or any
assumptions that are being made in the code, a good start would be to
get an idea of where in the code the bus error is triggered. You could
try the -v option but I am not sure it would help much.


root@elbrus:/tmp/autopkgtest-lxc.9j0ja_rt/downtmp/build.ssB/real-tree# 
pktanon -vc /usr/share/doc/pktanon/examples/profiles/profile.xml 
./profiles/sample.pcap ./out.pca

---
pktanon --- profile-based traffic anonymization
---
initializing PktAnon,  configuration = 
/usr/share/doc/pktanon/examples/profiles/profile.xml

parsing configuration file...
unknown element: pktanon-config: 37
unknown element: anonymizations: 102
parsed configuration file.
configuring transformations...
configuring ethernet packet:
mac-source[0]: AnonHashHmacSha1
mac-dest[0]: AnonHashHmacSha1
ethertype[0]: AnonIdentity
configuring arp packet:
hardware-type[0]: AnonIdentity
protocol-type[0]: AnonIdentity
hardware-size[0]: AnonIdentity
protocol-size[0]: AnonIdentity
opcode[0]: AnonIdentity
sender-mac[0]: AnonHashHmacSha1
sender-ip[0]: AnonHashSha1
target-mac[0]: AnonHashHmacSha1
target-ip[0]: AnonHashSha1
configuring ip(v4) packet:
tos[0]: AnonConstOverwrite
identification[0]: AnonIdentity
flags[0]: AnonIdentity
fragment[0]: AnonIdentity
ttl[0]: AnonWhitenoise
protocol[0]: AnonIdentity
src-ip[0]: AnonHashSha1
dest-ip[0]: AnonHashSha1
options[0]: AnonShorten
newlen: 0
configuring ipv6 packet:
traffic-class[0]: AnonIdentity
flow-label[0]: AnonIdentity
next-header[0]: AnonIdentity
hop-limit[0]: AnonWhitenoise
src-ip[0]: AnonHashSha256
dest-ip[0]: AnonHashSha256
configuring tcp packet:
source-port[0]: AnonRandomize
dest-port[0]: AnonRandomize
seq[0]: AnonWhitenoise
ack[0]: AnonWhitenoise
flags[0]: AnonIdentity
window-size[0]: AnonWhitenoise
urgent-pointer[0]: AnonConstOverwrite
options[0]: AnonShorten
newlen: 0
configuring udp packet:
source-port[0]: AnonRandomize
dest-port[0]: AnonRandomize
configuring icmp(v4) packet:
type[0]: AnonIdentity
code[0]: AnonIdentity
rest[0]: AnonIdentity
configuring icmp(v6) packet:
type[0]: AnonIdentity
code[0]: AnonIdentity
rest[0]: AnonIdentity
target-address[0]: AnonHashSha256
configuring payload packet:
payload[0]: AnonShorten
newlen: 0
configured
istream: opened file ./profiles/sample.pcap
ostream: opened output file ./out.pca
initialized
Bus error

(Mind you this was pktanon/unstable build in testing and installed there).


I think a real stack trace would help, by running the tests with
valgrind or via gdb. Nothing one would do in a generic test suite :/


I very much not fluent in valgrind and gdb. Please provide the exact 
commands you'd want me to execute and I'll see if I can get them.



How much customization would be possible in the test run?


I have a shell after the failure, so I can run what I want. I just don't 
want to change packages before and build them.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1002426: marked as done (nova: FTBFS: AssertionError: expected call not found.)

[Debian Bug Tracking System]

Your message dated Wed, 22 Dec 2021 20:41:36 +
with message-id 
and subject line Bug#1002426: fixed in nova 2:24.0.0-2
has caused the Debian Bug report #1002426,
regarding nova: FTBFS: AssertionError: expected call not found.
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.)


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

Hi,

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


Relevant part (hopefully):
> ==
> FAIL: nova.tests.unit.test_utils.GenericUtilsTestCase.test_temporary_chown
> nova.tests.unit.test_utils.GenericUtilsTestCase.test_temporary_chown
> --
> testtools.testresult.real._StringException: pythonlogging:'': {{{
> 2021-12-20 18:40:19,529 WARNING [oslo_policy.policy] JSON formatted 
> policy_file support is deprecated since Victoria release. You need to use 
> YAML format which will be default in future. You can use 
> ``oslopolicy-convert-json-to-yaml`` tool to convert existing JSON-formatted 
> policy file to YAML-formatted in backward compatible way: 
> https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html.
> 2021-12-20 18:40:19,529 WARNING [oslo_policy.policy] JSON formatted 
> policy_file support is deprecated since Victoria release. You need to use 
> YAML format which will be default in future. You can use 
> ``oslopolicy-convert-json-to-yaml`` tool to convert existing JSON-formatted 
> policy file to YAML-formatted in backward compatible way: 
> https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html.
> 2021-12-20 18:40:19,531 WARNING [oslo_policy.policy] Policy Rules 
> ['os_compute_api:extensions', 'os_compute_api:os-floating-ip-pools', 
> 'os_compute_api:os-quota-sets:defaults', 
> 'os_compute_api:os-availability-zone:list', 'os_compute_api:limits', 
> 'system_admin_api', 'system_reader_api', 'project_admin_api', 
> 'project_member_api', 'project_reader_api', 'system_admin_or_owner', 
> 'system_or_project_reader', 'os_compute_api:limits:other_project', 
> 'os_compute_api:os-lock-server:unlock:unlock_override', 
> 'os_compute_api:servers:create:zero_disk_flavor', 
> 'compute:servers:resize:cross_cell'] specified in policy files are the same 
> as the defaults provided by the service. You can remove these rules from 
> policy files which will make maintenance easier. You can detect these 
> redundant rules by ``oslopolicy-list-redundant`` tool also.
> }}}
> 
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/mock/mock.py", line 1346, in patched
> return func(*newargs, **newkeywargs)
>   File "/<>/nova/tests/unit/test_utils.py", line 156, in 
> test_temporary_chown
> mock_chown.assert_called_once_with(f.name, uid=os.getuid())
>   File "/usr/lib/python3/dist-packages/mock/mock.py", line 926, in 
> assert_called_once_with
> return self.assert_called_with(*args, **kwargs)
>   File "/usr/lib/python3/dist-packages/mock/mock.py", line 913, in 
> assert_called_with
> raise AssertionError(_error_message()) from cause
> AssertionError: expected call not found.
> Expected: chown('/tmp/tmpct70vknn/tmpua12is5z', uid=0)
> Actual: chown('/tmp/tmpct70vknn/tmpua12is5z', uid=1001)
> 
> 
> --
> Ran 16076 tests in 427.851s
> 
> FAILED (failures=1, skipped=51, expected failures=1)
> + echo ==> STESTR TEST SUITE FAILED FOR python3.10: displaying pip3 
> freeze output...
> ==> STESTR TEST SUITE FAILED FOR python3.10: displaying pip3 freeze 
> output...
> + [ -x /usr/bin/pip3 ]
> + pip3 freeze
> actdiag==2.0.0
> alabaster==0.7.12
> alembic==1.7.1.dev0
> amqp==5.0.6
> anyjson==0.3.3
> appdirs==1.4.4
> attrs==20.3.0
> automaton==2.4.0
> autopage==0.4.0
> Babel==2.8.0
> bandit==1.6.2
> bcrypt==3.2.0
> blinker==1.4
> blockdiag==2.0.1
> cachetools==4.2.1
> castellan==3.9.1
> certifi==2020.6.20
> cffi==1.15.0
> chardet==4.0.0
> cliff==3.9.0
> cmd2==0.0.0
> colorama==0.4.4
> confluent-kafka==1.7.0
> coverage==5.1
> cryptography==3.4.8
> cursive==0.2.2
> ddt==1.4.2
> debtcollector==2.3.0
> decorator==4.4.2
> deprecation==2.0.7
> dnspython==2.1.0
> docutils==0.17.1
> dogpile.cache==1.1.4
> dulwich==0.20.26
> etcd3==0.12.0
> 

Bug#1002060: marked as done (liblunar-date-doc: missing Breaks+Replaces: liblunar-date-dev (<< 3))

[Debian Bug Tracking System]

Your message dated Wed, 22 Dec 2021 20:41:17 +
with message-id 
and subject line Bug#1002060: fixed in lunar-date 3.0.1-2
has caused the Debian Bug report #1002060,
regarding liblunar-date-doc: missing Breaks+Replaces: liblunar-date-dev (<< 3)
to be marked as done.

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

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


-- 
1002060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblunar-date-doc
Version: 3.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Preparing to unpack .../liblunar-date-doc_3.0.1-1_all.deb ...
  Unpacking liblunar-date-doc (3.0.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/liblunar-date-doc_3.0.1-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/liblunar-date-dev/changelog.gz', which 
is also in package liblunar-date-dev:amd64 2.4.0-8
  Errors were encountered while processing:
   /var/cache/apt/archives/liblunar-date-doc_3.0.1-1_all.deb


cheers,

Andreas


liblunar-date-dev=2.4.0-8_liblunar-date-doc=3.0.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: lunar-date
Source-Version: 3.0.1-2
Done: xiao sheng wen 

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

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

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

Debian distribution maintenance software
pp.
xiao sheng wen  (supplier of updated lunar-date package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 22 Dec 2021 10:38:50 +0800
Source: lunar-date
Architecture: source
Version: 3.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Chinese Team 
Changed-By: xiao sheng wen 
Closes: 1002060
Changes:
 lunar-date (3.0.1-2) unstable; urgency=medium
 .
   [ xiao sheng wen(肖盛文) ]
   * d/control:
   - liblunar-date-doc add Replaces+Breaks: liblunar-date-dev (<< 3)
   - liblunar-date-3.0-1 add Replaces+Breaks: liblunar-date-2.0-0 (<< 3)
 (Closes: #1002060) Thanks Andreas Beckmann
Checksums-Sha1:
 a1351b17e2a38182ded7726b34f21acd84290953 2452 lunar-date_3.0.1-2.dsc
 a8baf7d7d2be90a166debab3ec7974c41c5cff8a 103134 lunar-date_3.0.1.orig.tar.gz
 a267fc3cd4aab98a521f41937a1b9f08df7b7463 5008 lunar-date_3.0.1-2.debian.tar.xz
 cc522aad54cef2002401ebcadbf0aea04055c6bb 10424 
lunar-date_3.0.1-2_amd64.buildinfo
Checksums-Sha256:
 70761d67e677dff156160825e094432e8536e2502b5be162ccac6604bd8fce04 2452 
lunar-date_3.0.1-2.dsc
 bfdd6ea70157ea55f0632fa3c86235cf00aba43bab85b707fd7d0096cbe0ac3e 103134 
lunar-date_3.0.1.orig.tar.gz
 264b2dd017ebe5f2387130af6c3fa3c316847f372b89373e8e9fa5979ceb1613 5008 
lunar-date_3.0.1-2.debian.tar.xz
 55a98f8df26d9b592170193668bd371c765c200bc39f9af9b5a30c87e44d7404 10424 
lunar-date_3.0.1-2_amd64.buildinfo
Files:
 7522883699f7446ce61c57f871406875 2452 libs optional lunar-date_3.0.1-2.dsc
 9b33346f2a8190125bdb879dac8afbc1 103134 libs optional 
lunar-date_3.0.1.orig.tar.gz
 cd80a6ecf5baaebddb21537572fde4a6 5008 libs optional 
lunar-date_3.0.1-2.debian.tar.xz
 f4e099176fa28e48482a828bac00360a 10424 libs optional 
lunar-date_3.0.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmHDhy8ACgkQwpPntGGC
Ws5T0w/8DfmwHhQq5kAkPycIANCincRdTqJWOmW2bUtqQpCKKdtNaGoNE+guSyhW
ILdgOhLnp8WbBVgj7vSNyiONpQnrezL4vAqjHrxC6R59N9x7uLo8CGEIo8YHGfmJ
hYGwiij9xwy99cCmDbWi363M6DKm0KipDuSntWbGlAGxfPh+QOb64ik2IzDsH6wP
M6oIHiQc0OcwACx8rQ6f5qvEYLhXnYmQrLWh4D6+GzPGP7uvAVPI/mLh5P5qvCEP
8revOsErcy3vvWmMbkCVkXFTh1BAA0frfkZe3L1SP+cIeKr67l5r//ic4V5EfLhe
y0JhfeXzxikcmTvMnXZ2QVu/mA7txzMHOI3KwquOUbiq391pQNFWKjDo1y+/pmBs

Bug#965662: marked as done (libmp3-info-perl: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Wed, 22 Dec 2021 20:37:03 +
with message-id 
and subject line Bug#965662: fixed in libmp3-info-perl 1.26-1
has caused the Debian Bug report #965662,
regarding libmp3-info-perl: 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.)


-- 
965662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmp3-info-perl
Version: 1.24-1.2
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package libmp3-info-perl 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: libmp3-info-perl
Source-Version: 1.26-1
Done: Damyan Ivanov 

We believe that the bug you reported is fixed in the latest version of
libmp3-info-perl, 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.
Damyan Ivanov  (supplier of updated libmp3-info-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 22 Dec 2021 20:02:50 +
Source: libmp3-info-perl
Architecture: source
Version: 1.26-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Damyan Ivanov 
Closes: 524791 965662 1001680
Changes:
 libmp3-info-perl (1.26-1) unstable; urgency=medium
 .
   [ Damyan Ivanov ]
   * Take over for the Debian Perl Group; Closes: #1001680 -- RFA/ITA
   * debian/control: Added: Vcs-Git field (source stanza); Vcs-Browser
 field (source stanza); ${misc:Depends} to Depends: field. Changed:
 Maintainer set to Debian Perl Group  (was: Alexander Wirt
 ); Replace (build-)dependency on ancient version of
 perl with a dependency on perl without a version (as permitted by Debian
 Policy 3.8.3).
   * debian/watch: use metacpan-based URL.
   * put myself as Uploader
   * bump debhelper compatibility level to 13 (Closes: #965662)
   * drop mp3id example script
 this was never part of upstream source but added to the package in 1999,
 moved to examples/ in 2004
   * use source format 3.0 (quilt)
   * convert debian/rules to minimal dh sequencer
   * convert debian/watch to version 4
   * enable automated package testing
   * convert debian/copyright to machine-readable format, update
   * New upstream version 1.26
 + patch Makefile.PL so that system-wide Module-Install is used during
   build
 + update debian/copyright (new upstream contact)
 + README got renamed to README.md, adapt .docs
   * add deprecation notice to description, suggesting Audio::Scan
 (Closes: #524791)
 .
   [ gregor herrmann ]
   * Add a patch to handle move v2.4 tags.
   * Update short and long description.
   * Declare compliance with Debian Policy 4.6.0.
   * Set Rules-Requires-Root: no.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
   * Add Homepage to debian/control.
Checksums-Sha1: 
 892b5ea5ed447eae66c01b0b615cc6b2dbe10b29 2100 libmp3-info-perl_1.26-1.dsc
 8f4a50d5d24cfacbe53f66530b9d777fc9b31716 136554 

Bug#1001711: marked as done (libtoxcore2: Stack-based buffer overflow vulnerability in UDP packet handling in Toxcore (CVE-2021-44847))

[Debian Bug Tracking System]

Your message dated Wed, 22 Dec 2021 20:37:14 +
with message-id 
and subject line Bug#1001711: fixed in libtoxcore 0.2.13-1
has caused the Debian Bug report #1001711,
regarding libtoxcore2: Stack-based buffer overflow vulnerability in UDP packet 
handling in Toxcore (CVE-2021-44847)
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.)


-- 
1001711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtoxcore2
Version: 0.2.12-1+b1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: Debian Security Team 

Dear Maintainer,

libtoxcore has CVE-2021-44847:

https://blog.tox.chat/2021/12/stack-based-buffer-overflow-vulnerability-in-udp-packet-handling-in-toxcore-cve-2021-44847/

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44847

Workaround is to disable UDP support in settings.

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

Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8), LANGUAGE=lt
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libtoxcore2 depends on:
ii  libc62.33-1
ii  libopus0 1.3.1-0.1
ii  libsodium23  1.0.18-1
ii  libvpx7  1.11.0-2

libtoxcore2 recommends no packages.

libtoxcore2 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libtoxcore
Source-Version: 0.2.13-1
Done: Yangfl 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 21 Dec 2021 15:49:21 +0800
Source: libtoxcore
Architecture: source
Version: 0.2.13-1
Distribution: unstable
Urgency: medium
Maintainer: Yangfl 
Changed-By: Yangfl 
Closes: 1001711
Changes:
 libtoxcore (0.2.13-1) unstable; urgency=medium
 .
   * New upstream release
 * Fix CVE-2021-44847 (Closes: #1001711)
   * Bump Standards-Version to 4.6.0
Checksums-Sha1:
 3d9c18210e5f2668c840b93667a2600418501a2b 2362 libtoxcore_0.2.13-1.dsc
 70477f432352285dbcfd5dbc15289058a3c15780 511533 libtoxcore_0.2.13.orig.tar.gz
 b95d78d8aae24bc0106887e8a8a1dbc970c255a7 833 libtoxcore_0.2.13.orig.tar.gz.asc
 b794e0591ec5595d1fa1255577e24cc88df8ab43 11092 
libtoxcore_0.2.13-1.debian.tar.xz
 1cfbda60c6f9bc26a1777207aa8e8f7dbd53623b 7944 
libtoxcore_0.2.13-1_amd64.buildinfo
Checksums-Sha256:
 b3983ea40f0ba522bcd065ed672dd879f931068b4d48b6548c50419392a9a662 2362 
libtoxcore_0.2.13-1.dsc
 67114fa57504c58b695f5dce8ef85124d555f2c3c353d0d2615e6d4845114ab8 511533 
libtoxcore_0.2.13.orig.tar.gz
 15ce1867ffa4e49de80c297dce24fa99c87e125641bfdab821fb450a0cf831c4 833 
libtoxcore_0.2.13.orig.tar.gz.asc
 bffd3fb03d5094f79ab605aa79e29bc861c15cbef94184b6909435aa0c252dbe 11092 
libtoxcore_0.2.13-1.debian.tar.xz
 fccd3d3d5861202c7de3815b5b138fafe1d7bf9c53e337e88743f261fc94a2dc 7944 
libtoxcore_0.2.13-1_amd64.buildinfo
Files:
 cb1e1b3cc9c0c44fc5899fee3daeb176 2362 libs optional libtoxcore_0.2.13-1.dsc
 3fb55506a84a50cf84af7946b3706ca9 511533 libs optional 
libtoxcore_0.2.13.orig.tar.gz
 84c93b2136b39152f912d527521cabf8 833 libs optional 
libtoxcore_0.2.13.orig.tar.gz.asc
 a27e0b052a4c1ad4ce09a61f41072e4d 11092 libs optional 
libtoxcore_0.2.13-1.debian.tar.xz
 75fa9844a46e2036a79cd3ccba39700c 7944 libs optional 
libtoxcore_0.2.13-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmHDgp4ACgkQwpPntGGC
Ws6HHBAAnnAbeAPaM7Hi/bS9+GsmbQDnAYRo7P10l8jJwa+hJEjnm+FmTDUBExJV
ukOXMGQ6soiJETAN/rQ6k0z8mEx9qpFCy9VcP7kvD3L97u0Iy+Bqb7BjRwMJ4e/6

Bug#995393: fakeroot: FTBFS on ppc64el

[Christoph Biedl]

Control: tags 995393 patch

Frédéric Bonnard wrote...

>  #ifdef HAVE_OPENAT
> +#if defined(__powerpc__) && defined(__powerpc64__) && __BYTE_ORDER__ == 
> __ORDER_LITTLE_ENDIAN__
> +static int openat(int dir_fd, const char *pathname, int flags, ...)
> +#else
>  int openat(int dir_fd, const char *pathname, int flags, ...)
> +#endif

Well, that makes openat a private function - the idea however is to
provide a publicly visible function. Also, if I read the objdump output
correctly, the compiler will happily inline the function then as there
is just one usage.

> Hoping you'll get more ideas on this

After digging into this for quite a few hours, this really smells like a
bug in the optimizer but I'm not keen on spending a lot of time on a
reproducer and taking it to gcc upstream.

As a workaround I propose a tactical __attribute__ to locally disable
optimization as this issue has been blocking eatmydata for way too long,
and performance loss should be neglectable.

Status: Works on the porterbox.

Cheers,

Christoph

 #ifdef HAVE_OPENAT
-int openat(int dir_fd, const char *pathname, int flags, ...)
+int
+#if HAVE_OPENAT && defined(__powerpc__) && defined(__powerpc64__) && 
__BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__
+__attribute__((optimize("O0")))
+#endif
+openat(int dir_fd, const char *pathname, int flags, ...)


signature.asc
Description: PGP signature

Processed: Re: Bug#995393: fakeroot: FTBFS on ppc64el

[Debian Bug Tracking System]

Processing control commands:

> tags 995393 patch
Bug #995393 [src:fakeroot] fakeroot: FTBFS on ppc64el
Added tag(s) patch.

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

Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14

[Christoph Berg]

Re: Dimitri Fontaine
> Thanks again folks, I really appreciate the time and effort you're putting 
> into this, and of course the good results!

I got it working, including a workaround that will automatically
downgrade scram-sha-256 to md5 on the older distributions where
cl-postmodern doesn't understand the newer hash yet.

Thanks!

Sébastien: The cl-uax-15 autopkgtest is failing:
https://qa.debian.org/excuses.php?package=cl-uax-15

(I can reproduce the clisp error here, but not the segfault.)

Christoph

Processed: closing 995846

[Debian Bug Tracking System]

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

> close 995846 3.6.3-1
Bug #995846 [pgloader] FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14
Marked as fixed in versions pgloader/3.6.3-1.
Bug #995846 [pgloader] FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#995846: closing 995846

[Christoph Berg]

close 995846 3.6.3-1
thanks

Processed: Bug#1002426 marked as pending in nova

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1002426 [src:nova] nova: FTBFS: AssertionError: expected call not found.
Added tag(s) pending.

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

Bug#1002426: marked as pending in nova

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/services/nova/-/commit/b0f1042280b6a1b097654819c052e8a49ea49d58


* Blacklist test_temporary_chown which is expected to fail under a packaging
environement (Closes: #1002426).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1002426

Bug#1001591: [Pkg-matrix-maintainers] Bug#1002380: drops attributes used by reverse dependencies

[Jonas Smedegaard]

Quoting Pierre-Elliott Bécue (2021-12-22 17:08:46)
> 
> Jonas Smedegaard  wrote on 22/12/2021 at 12:37:21+0100:
> > Releasing a new major release of mistune has caused several packages 
> > to no longer be usable at all.
> >
> > I consider this a serious issue, and have raised severity 
> > accordingly.
> >
> > At least python-m2r have no support for mistune v2 in sight (and its 
> > newer fork - python-m2r2 - does not either). Concretely I propose to 
> > revert this by a (messy) 2.0.0+really0.8.4 release until reverse 
> > dependencies can use the newer major version of mistune.
> >
> > It seems that a release of python3-django-hyperkitty requiring 
> > mistune v2 has already been uploaded to unstable as well.  That is 
> > very unfortunate, and will need to be rolled back as well.  Mailman 
> > maintainers cc'ed.
> >
> > Please in future make sure to check reverse dependencies *before* 
> > releasing a major new upstream release to unstable, because reversal 
> > is messy (complicates package versioning).
> >
> >
> > Kind regards, and thanks for maintaining mistune,
> 
> The issue is that many reverse dependencies of mistune are not
> maintained.

I assume (in good faith) that you did not mean to say that the _Debian_ 
packages reverse depending on mistune are all unmaintained.

Please note that I did not propose to wait until _upstreams_ of reverse 
dependencies can use newer major version of mistune.

My proposal is to *collaborate* with your peers in Debian now - not 
continue(!) to make choices without coordination with those packages 
directly affected by those choices.


> If I follow your opinion on this, the following issues arise:
> 
>  1. There is no proper way for software to be mistune 0.8.4 and 
> mistune 2.0.0 compatible at the same way, so the reverse 
> dependencies won't be able to update without mistune 2.0.0 being 
> in unstable

Not sure what you imply by "proper".

There are alternatives to abruptly abandoning support for existing 
functionaling packages already in Debian testing.


>  2. I'll need mailman3 to be able to enter testing at some point and I 
> don't think we can expect it to wait for software that is no 
> longer maintained upstream

At some point, yes.  I see no reason to rush that to the point of not 
coordinating with involved packages.


> Apart from these two points, there are multiple cases where software 
> are updated despite the impact on the reverse dependencies. Typically 
> Python updates don't wait for dependencies to be ready in case of 
> breaking changes, and that looks to me quite normal, despite it 
> bringing more work to me as a mailman or python packages maintainer.

I guess coordination within the Python team may be more relaxed.

Is your point that coordination among package maintainers more generally 
- not within the Python team - is not important?


> I'd be happy to hear about how you suggest me to handle the 
> unmaintained reverse-dependencies like m2r.

Step one: File bugreports of severity important against all reverse 
dependencies (possibly except packages maintained within the Python 
team, not sure about those).

Step two: After some time, raise severity of those bugreports.


> For now I'd rather let a serious bug block the migration of mistune 
> from unstable to testing and accept that some packages are not working 
> in unstable for now.

It is a fact that a serious bug (this one) blocks the migration of 
mistune and that reverse dependencies fial to work in unstable.

Are you saying that you intend to not actively do anything about that - 
just let it be and let time pass until the mess gets resolved by release 
team or others?


 - 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#1002229: libnet-traceroute-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Hi Gregor,

On 22/12/21 at 16:30 +0100, gregor herrmann wrote:
> COntrol: tag -1 + unreproducible moreinfo
> 
> On Tue, 21 Dec 2021 17:33:43 +0100, Lucas Nussbaum wrote:
> 
> > Source: libnet-traceroute-perl
> > Version: 1.15-2
> > Severity: serious
> > Justification: FTBFS
> 
> > > /<>/blib/lib/Net/Traceroute.pm:Net::Traceroute::debug_print:230:
> > >  Running in debug mode
> > > /<>/blib/lib/Net/Traceroute.pm:Net::Traceroute::debug_print:294:
> > >  Performing traceroute
> > > /<>/blib/lib/Net/Traceroute.pm:Net::Traceroute::debug_print:487:
> > >  $VAR1 = bless( {
> > >  'debug' => 9,
> > >  'stat' => 2,
> > >  'host' => 'ip-10-84-232-242',
> > >  'trace_program' => 'traceroute',
> > >  'timeout' => 30
> > >}, 'Net::Traceroute' );
> > > No output from traceroute.  Exec failure? at 
> > > /<>/blib/lib/Net/Traceroute.pm line 360.
> > > # Looks like your test exited with 255 before it could output anything.
> > > t/95-sys-traceroute.t . 
> > > 1..2
> > > Dubious, test returned 255 (wstat 65280, 0xff00)
> > > Failed 2/2 subtests 
> 
> 
> Hi Lucas,
> 
> thanks for your bug report.
> 
> Yesterday evening, 3 of us in the Perl team could not reproduce this
> failure locally. From looking at the test and the actual code, what
> seems to happen is that `traceroute' does not produce _any_ output,
> which is a bit surprising.
> 
> Do you have any idea how this can happen in your test environment or
> any information for us, what is special about it?
> 
> 
> As a side note, the test itself is marked as TODO, i.e. expected to
> fail, with a comment that it's fragile, so we might as well skip it
> completely. - Oh, that comes from our own patch :) And the patch
> headers mention #849933 and #980475.
> 
> Still, seeing the code explode _before_ reaching this stage is
> puzzling.

I tried it again and could reproduce it.

According to execsnoop, what is executed is:
perl 24798  247690 /usr/bin/perl t/95-sys-traceroute.t
traceroute   24799  247980 /usr/sbin/traceroute -n ip-10-84-232-230
traceroute   24800  247980 /usr/sbin/traceroute -n ip-10-84-232-230

However according to exitsnoop, traceroute exits with exit code 2.

I think that what happens is:
1/ the VM hostname is set to ip-10-84-232-230 (or ip-10-84-232-242 in the
bug report)
2/ /etc/hosts is correctly configured to resolve that hostname:
127.0.1.1 ip-10-84-232-230.eu-central-1.compute.internal ip-10-84-232-230
3/ however, schroot does not copy /etc/hosts into the chroot. The
content of /etc/hosts in the chroot does not include the line for 127.0.1.1.
4/ when the test suite runs traceroute on the machine's hostname,
traceroute fails to resolve the hostname, and exits with exit code 2.
5/ for some reason, the test harness thinks the test exited with code 255.

libnet-traceroute-perl seems to be the only package failing to build due
to this condition, so it might be worth fixing in the package, even if
one could argue that it's a bug in the build environment. Maybe
tracerouting to 127.0.0.1 would be enough?

Lucas

Bug#997759: marked as done (ldc: FTBFS: /<>/runtime/druntime/src/ldc/intrinsics.di(54): Error: undefined identifier `LLVM_version`)

[Debian Bug Tracking System]

Your message dated Wed, 22 Dec 2021 19:36:08 +
with message-id 
and subject line Bug#997759: fixed in ldc 1:1.28.0-2
has caused the Debian Bug report #997759,
regarding ldc: FTBFS: 
/<>/runtime/druntime/src/ldc/intrinsics.di(54): Error: undefined 
identifier `LLVM_version`
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.)


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

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/bootstrap-stage1'
> [ 66%] Generating import/ldc/gccbuiltins_x86.di
> cd /<>/bootstrap-stage1/runtime && ../bin/gen_gccbuiltins 
> /<>/bootstrap-stage1/runtime/import/ldc/gccbuiltins_x86.di x86
> [ 66%] Generating import/ldc/gccbuiltins_aarch64.di
> cd /<>/bootstrap-stage1/runtime && ../bin/gen_gccbuiltins 
> /<>/bootstrap-stage1/runtime/import/ldc/gccbuiltins_aarch64.di 
> aarch64
> [ 66%] Generating import/ldc/gccbuiltins_aarch64.di
> cd /<>/bootstrap-stage1/runtime && ../bin/gen_gccbuiltins 
> /<>/bootstrap-stage1/runtime/import/ldc/gccbuiltins_aarch64.di 
> aarch64
> [ 66%] Generating import/ldc/gccbuiltins_aarch64.di
> cd /<>/bootstrap-stage1/runtime && ../bin/gen_gccbuiltins 
> /<>/bootstrap-stage1/runtime/import/ldc/gccbuiltins_aarch64.di 
> aarch64
> [ 66%] Generating import/ldc/gccbuiltins_aarch64.di
> cd /<>/bootstrap-stage1/runtime && ../bin/gen_gccbuiltins 
> /<>/bootstrap-stage1/runtime/import/ldc/gccbuiltins_aarch64.di 
> aarch64
> [ 66%] Generating import/ldc/gccbuiltins_amdgcn.di
> [ 66%] Generating import/ldc/gccbuiltins_amdgcn.di
> [ 66%] Generating import/ldc/gccbuiltins_amdgcn.di
> cd /<>/bootstrap-stage1/runtime && ../bin/gen_gccbuiltins 
> /<>/bootstrap-stage1/runtime/import/ldc/gccbuiltins_amdgcn.di 
> amdgcn
> cd /<>/bootstrap-stage1/runtime && ../bin/gen_gccbuiltins 
> /<>/bootstrap-stage1/runtime/import/ldc/gccbuiltins_amdgcn.di 
> amdgcn
> cd /<>/bootstrap-stage1/runtime && ../bin/gen_gccbuiltins 
> /<>/bootstrap-stage1/runtime/import/ldc/gccbuiltins_amdgcn.di 
> amdgcn
> [ 66%] Generating import/ldc/gccbuiltins_amdgcn.di
> cd /<>/bootstrap-stage1/runtime && ../bin/gen_gccbuiltins 
> /<>/bootstrap-stage1/runtime/import/ldc/gccbuiltins_amdgcn.di 
> amdgcn
> [ 66%] Generating import/ldc/gccbuiltins_arm.di
> cd /<>/bootstrap-stage1/runtime && ../bin/gen_gccbuiltins 
> /<>/bootstrap-stage1/runtime/import/ldc/gccbuiltins_arm.di arm
> [ 66%] Generating import/ldc/gccbuiltins_arm.di
> cd /<>/bootstrap-stage1/runtime && ../bin/gen_gccbuiltins 
> /<>/bootstrap-stage1/runtime/import/ldc/gccbuiltins_arm.di arm
> [ 66%] Generating import/ldc/gccbuiltins_arm.di
> cd /<>/bootstrap-stage1/runtime && ../bin/gen_gccbuiltins 
> /<>/bootstrap-stage1/runtime/import/ldc/gccbuiltins_arm.di arm
> [ 66%] Generating import/ldc/gccbuiltins_arm.di
> cd /<>/bootstrap-stage1/runtime && ../bin/gen_gccbuiltins 
> /<>/bootstrap-stage1/runtime/import/ldc/gccbuiltins_arm.di arm
> [ 66%] Generating import/ldc/gccbuiltins_mips.di
> cd /<>/bootstrap-stage1/runtime && ../bin/gen_gccbuiltins 
> /<>/bootstrap-stage1/runtime/import/ldc/gccbuiltins_mips.di mips
> [ 66%] Generating import/ldc/gccbuiltins_mips.di
> [ 66%] Generating import/ldc/gccbuiltins_mips.di
> [ 66%] Generating import/ldc/gccbuiltins_mips.di
> cd /<>/bootstrap-stage1/runtime && ../bin/gen_gccbuiltins 
> /<>/bootstrap-stage1/runtime/import/ldc/gccbuiltins_mips.di mips
> cd /<>/bootstrap-stage1/runtime && ../bin/gen_gccbuiltins 
> /<>/bootstrap-stage1/runtime/import/ldc/gccbuiltins_mips.di mips
> cd /<>/bootstrap-stage1/runtime && ../bin/gen_gccbuiltins 
> /<>/bootstrap-stage1/runtime/import/ldc/gccbuiltins_mips.di mips
> [ 66%] Generating import/ldc/gccbuiltins_nvvm.di
> cd /<>/bootstrap-stage1/runtime && ../bin/gen_gccbuiltins 
> /<>/bootstrap-stage1/runtime/import/ldc/gccbuiltins_nvvm.di nvvm
> [ 66%] Generating import/ldc/gccbuiltins_nvvm.di
> [ 73%] Generating import/ldc/gccbuiltins_nvvm.di
> [ 73%] Generating import/ldc/gccbuiltins_nvvm.di
> cd /<>/bootstrap-stage1/runtime && ../bin/gen_gccbuiltins 
> /<>/bootstrap-stage1/runtime/import/ldc/gccbuiltins_nvvm.di nvvm
> cd /<>/bootstrap-stage1/runtime && ../bin/gen_gccbuiltins 
> /<>/bootstrap-stage1/runtime/import/ldc/gccbuiltins_nvvm.di nvvm
> cd /<>/bootstrap-stage1/runtime && ../bin/gen_gccbuiltins 
> 

Bug#1002224: marked as done (network-manager-applet: FTBFS: ../meson.build:174:2: ERROR: Could not generate cargs for ayatana-appindicator3-0.1:)

[Debian Bug Tracking System]

Your message dated Wed, 22 Dec 2021 20:09:37 +0100
with message-id 
and subject line Re: [Pkg-utopia-maintainers] Bug#1002224: 
network-manager-applet: FTBFS: ../meson.build:174:2: ERROR: Could not generate 
cargs for ayatana-appindicator3-0.1:
has caused the Debian Bug report #1002224,
regarding network-manager-applet: FTBFS: ../meson.build:174:2: ERROR: Could not 
generate cargs for ayatana-appindicator3-0.1:
to be marked as done.

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

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


-- 
1002224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: network-manager-applet
Version: 1.24.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- \
>   --libexecdir=/usr/lib/NetworkManager \
>   -Dappindicator=ayatana \
>   -Dwwan=true \
>   -Dselinux=true \
>   -Dteam=true
>   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 
> --libexecdir=/usr/lib/NetworkManager -Dappindicator=ayatana -Dwwan=true 
> -Dselinux=true -Dteam=true
> The Meson build system
> Version: 0.60.2
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: network-manager-applet
> Project version: 1.24.0
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-13) 
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.37
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Checking for type "pid_t" : YES 
> Compiler for C supports arguments -fdata-sections -ffunction-sections: YES 
> Compiler for C supports link arguments -Wl,--gc-sections: YES 
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency gio-2.0 found: YES 2.70.2
> Run-time dependency gmodule-export-2.0 found: YES 2.70.2
> Run-time dependency libsecret-1 found: YES 0.20.4
> Run-time dependency libnma found: YES 1.8.32
> Library m found: YES
> Run-time dependency gtk+-3.0 found: YES 3.24.30
> Run-time dependency gudev-1.0 found: YES 237
> Run-time dependency libnotify found: YES 0.7.9
> Run-time dependency libnm found: YES 1.32.12
> Did not find CMake 'cmake'
> Found CMake: NO
> Run-time dependency ayatana-appindicator3-0.1 found: NO 
> 
> ../meson.build:174:2: ERROR: Could not generate cargs for 
> ayatana-appindicator3-0.1:
> Package ayatana-indicator3-0.4 was not found in the pkg-config search path.
> Perhaps you should add the directory containing `ayatana-indicator3-0.4.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'ayatana-indicator3-0.4', required by 'ayatana-appindicator3-0.1', 
> not found
> 
> 
> 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 2021-12-20T19:00:17.768172
> Main binary: /usr/bin/python3
> Build Options: -Dappindicator=ayatana -Dwwan=true -Dselinux=true -Dteam=true 
> -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu 
> -Dlibexecdir=/usr/lib/NetworkManager -Dlocalstatedir=/var -Dsysconfdir=/etc 
> -Dbuildtype=plain -Dwrap_mode=nodownload
> Python system: Linux
> The Meson build system
> Version: 0.60.2
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: network-manager-applet
> Project version: 1.24.0
> 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,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-13) 
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.37
> 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,defs

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

[Debian Bug Tracking System]

Your message dated Wed, 22 Dec 2021 18:49:04 +
with message-id 
and subject line Bug#965531: fixed in fxload 0.0.20081013-2
has caused the Debian Bug report #965531,
regarding fxload: 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.)


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

Hi,

The package fxload 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: fxload
Source-Version: 0.0.20081013-2
Done: Thorsten Alteholz 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 22 Dec 2021 19:03:02 +0100
Source: fxload
Architecture: source
Version: 0.0.20081013-2
Distribution: unstable
Urgency: low
Maintainer: Debian Astronomy Team 

Changed-By: Thorsten Alteholz 
Closes: 739016 745190 965531
Changes:
 fxload (0.0.20081013-2) unstable; urgency=low
 .
   * move package to debian-astro maintenance
   * thanks to Fumitoshi UKAI for the initial upload (Closes: #739016)
   * debian/control: use dh13 (Closes: #965531)
   * debian/control: bump standard to 4.6.0 (no changes)
   * debian/control: use Architectur: linux-any (Closes: #745190)
Checksums-Sha1:
 77faf006616482c813246fa49bc16210dcba8c43 2177 fxload_0.0.20081013-2.dsc
 8ed746731e24b619e5a18e6d3d9f5989967e5ec7 3036 
fxload_0.0.20081013-2.debian.tar.xz
 957849261c25d4260c541c770761a7b9f556e409 6229 
fxload_0.0.20081013-2_amd64.buildinfo
Checksums-Sha256:
 cdaa64841024c858a58f32ccffb51e7a07ab3a05bb5baf8c8c551ff8f63c8cac 2177 
fxload_0.0.20081013-2.dsc
 936e21bb21b531dc9293d0478bb344963b477b570a3ae6e3a8e22a55b9770ea0 3036 
fxload_0.0.20081013-2.debian.tar.xz
 a03433904601fac3b15d77defb2ee617d4a9d5469e6b9d99d02b79efbbbe7309 6229 
fxload_0.0.20081013-2_amd64.buildinfo
Files:
 9a4a7f0f25ba55f25b884f7e59900551 2177 admin optional fxload_0.0.20081013-2.dsc
 bf7152f0ef6386505f3c5a2c2288f4a3 3036 admin optional 
fxload_0.0.20081013-2.debian.tar.xz
 8de913fa63ca1fd97cc9682de78cc585 6229 admin optional 
fxload_0.0.20081013-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmHDbwRfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy
MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh
bHRlaG9sei5kZQAKCRCW/KwNOHtYR+kVD/9HvP6hwFTSGwliWh1K3Qvf3IlXKgOf
VPGP4sKfqkAZFfcSpylJY4j3rX/Egc3dph79mBLqIsei0npwCsEG0gkKAJ8Bivyu
DTdUbE3UKkekqZZ68rXZio0O6KsTBH0sYC6vF8b/7YaIAf89CM0fd0DhqBtNBDo4
O71JaddjjPSQSMSSrQwVtnoVltP3kZ10uf7DBKAoaTWwAo1qLHMFBLCPzAb2hj7L
WX06bBpYE3SLs2TkA2ruyr9IEgIlqW6L30rC4J8gTvuuvg7bkpy+vmA56WnHMLfr
A8+0nOFnkSDMCJ7Aq3HfNgDP3WmOrdKIfdYgxKQKSdxgpMkDslUNOqaguxnWmQUz

Bug#1002155: libgoby-java: FTBFS: [WARNING] /<>/goby-io/../goby-distribution/src/main/java/org/campagnelab/goby/modes/FastaToCompactMode.java:23: error: package edu.rit.pj does not exist

[Andreas Tille]

Hi,

Am Wed, Dec 22, 2021 at 06:17:21PM +0100 schrieb Pierre Gruet:
> 
> The warning mentioned in the bug title is issued by the Javadoc builder,
> which we do not use. It does not trigger the failure of the build.
> The real issue is in the tests: for some reason, a FileNotFoundException is
> raised by the FileOutputStream constructor when being called on files in the
> test-results/ directory.

The "can not reproduce" in combination with "file not found" rings somehow
a bell that this could be a case for a --no-parallel build.

Kind regards

  Andreas. 

-- 
http://fam-tille.de

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

[Debian Bug Tracking System]

Your message dated Wed, 22 Dec 2021 18:18:38 +
with message-id 
and subject line Bug#965442: fixed in brandy 1.20.1-2
has caused the Debian Bug report #965442,
regarding brandy: 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.)


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

Hi,

The package brandy 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: brandy
Source-Version: 1.20.1-2
Done: Stephen Kitt 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 22 Dec 2021 19:05:50 +0100
Source: brandy
Architecture: source
Version: 1.20.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Stephen Kitt 
Closes: 965442
Changes:
 brandy (1.20.1-2) unstable; urgency=medium
 .
   * QA upload.
   * Orphan the package (see #990610).
   * Upgrade to debhelper compatibility level 13. Closes: #965442.
   * Enable all hardening options.
   * Set “Rules-Requires-Root: no”.
   * Switch to a machine-readable debian/copyright.
   * Drop the obsolete dpkg-dev build-dependency.
   * Standards-Version 4.6.0, no further change required.
Checksums-Sha1:
 98d9b5e0bb9fe74d24d6d8caae01517227607b0b 1761 brandy_1.20.1-2.dsc
 0ecfbe2d3acce4a7959201e7b1416dc6a8566b67 5380 brandy_1.20.1-2.debian.tar.xz
 1ec9f62b7a6ded6c902ef47b523a3b1f2b3b7e4b 9853 brandy_1.20.1-2_source.buildinfo
Checksums-Sha256:
 92b0fec856a6352ce6c45e30226bdbbcae5b64503889b2b2320a74002022890f 1761 
brandy_1.20.1-2.dsc
 32ddb19e1a95cb5ca33aa0cd16b6f77c429860b03274e9f076e5a479ba4c7861 5380 
brandy_1.20.1-2.debian.tar.xz
 f82da6cccbe885c17e714ed81b6b9ec84e3976b0d3b9238046d7e7e4466db5ad 9853 
brandy_1.20.1-2_source.buildinfo
Files:
 514f7470e12c2877d62f0c632ce2d8df 1761 interpreters optional brandy_1.20.1-2.dsc
 fec71d2719a291be894f926805771af8 5380 interpreters optional 
brandy_1.20.1-2.debian.tar.xz
 bd645a08bd1cc61533f3ba1da3847882 9853 interpreters optional 
brandy_1.20.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAmHDaQURHHNraXR0QGRl
Ymlhbi5vcmcACgkQgNMC9Yhtg5zyBw//ZAd2suaYA3Y8EwZ9KYksheZDX/hJjmWW
M7odGlcwZOhae3JenmU24+DXMZlhwGyqX1XsHNXTe29fo5FjGwoyNLVbgzGcs7AX
pca2roxRDncDq7q7Ttlock47H7xQXQGjTck2n0YgcWWSLko66av873rKtkiNgWqv
CxF5VH815QFDwhjhkbqRg76k9oOl73MniWky3X+p4YOr8YKxtpYecT4uW08dhIRW
ubHtRJg+nwaAEPxsuuY2GmVQNCBa1ra8UjyweytJR/6/jpnIs1w2foT22oWmO0WC
AL4PWpUXyTFxfretkPKdb/i9D1zKWiNeo5x8NoetQ4FwI0FHDDl6MxPTQP8F+m1R
sDsLsQjd69+d3vKu9QSf60e/zYqEek7sVKbKa2TvlDxJ1GMpSog9lGGXR7adkB9j
ZlOGZRhl9rQKVMkZeMuKTQealrhdDXO3Ys6NTCxZL4TAgKHpi8zvT5zxijuG9t1d
yMyQ9ab5UJ4bQCr/0hRjwTR5A2r3x/st8gUBU4rZBWRvwwnyDQcQiDVk7CMvQFjY

Processed: Re: Bug#1001882: 0ad: FTBFS on armhf: error: ‘-mfloat-abi=hard’: selected architecture lacks an FPU

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1001882 [src:0ad] 0ad: FTBFS on armhf: error: ‘-mfloat-abi=hard’: selected 
architecture lacks an FPU
Added tag(s) patch.

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

Bug#1001882: 0ad: FTBFS on armhf: error: ‘-mfloat-abi=hard’: selected architecture lacks an FPU

[Shengjing Zhu]

Control: tags -1 patch

Hi,

On Sat, Dec 18, 2021 at 8:04 PM Simon McVittie  wrote:
>
> On Sat, 18 Dec 2021 at 17:22:49 +0800, Shengjing Zhu wrote:
> >   process didn't exit successfully: 
> > `/<>/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/debug/build/mozglue-static-db2fd9029278a596/build-script-build`
> >  (exit status: 1)
> ...
> >   cargo:warning=cc1plus: error: ‘-mfloat-abi=hard’: selected architecture 
> > lacks an FPU
>
> This looks like the same root cause as #1001314, which was triggered by
> configuration changes in Debian's gcc-11: 0ad seems to include a vendored
> copy of mozjs78, which includes a vendored copy of cc-rs, which needs
> 
> (originally
> ).

I take this patch for https://salsa.debian.org/games-team/0ad/-/merge_requests/2

-- 
Shengjing Zhu

Bug#1002281: marked as done (polymake: FTBFS: /<>/apps/polytope/rules/slack_ideal.rules:37: testcase 1 expected: regular return got: EXCEPTION: no more rules available to compute 'GENERAT

[Debian Bug Tracking System]

Your message dated Wed, 22 Dec 2021 17:25:01 +
with message-id 
and subject line Bug#1002281: fixed in polymake 4.4-4
has caused the Debian Bug report #1002281,
regarding polymake: FTBFS: 
/<>/apps/polytope/rules/slack_ideal.rules:37: testcase 1 expected: 
regular return got: EXCEPTION: no more rules available to compute 'GENERATORS'
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> HOME=$(mktemp -p build -d) perl perl/polymake --script run_testcases 
> --emacs-style
> polymake:  WARNING: created private directory build/tmp.8q0GzaNAXb/.polymake
> 
> *** Testing in application common ***
> 
> testing Examples:
>  [ /common/property_types/Set Types/ApproximateSet ] 1
> verifying: 1 OK
>  [ /common/property_types/Set Types/HashMap ] 1
> verifying: 1 OK
>  [ /common/property_types/Set Types/Map ] 1
> verifying: 1 OK
>  [ /common/property_types/Algebraic Types/Matrix ] 1
> verifying: 1 OK
>  [ /common/property_types/Set Types/Set ] 1
> verifying: 1 OK
>  [ /common/property_types/Algebraic Types/SparseMatrix ] 1 2
> verifying: 1 2 OK
>  [ /common/property_types/Algebraic Types/SparseVector ] 1 2
> verifying: 1 2 OK
>  [ /common/property_types/Algebraic Types/Vector ] 1
> verifying: 1 OK
>  [ /common/functions/Combinatorics/all_permutations ] 1
> verifying: 1 OK
>  [ /common/functions/Linear Algebra/anti_diag ] 1 2
> verifying: 1 2 OK
>  [ /common/property_types/Algebraic Types/Matrix/methods/anti_diagonal ] 1
> verifying: 1 OK
>  [ /core/functions/Interactive/apropos ] 1
> verifying: 1 OK
>  [ /common/functions/Combinatorics/are_permuted ] 1
> verifying: 1 OK
>  [ /common/functions/Utilities/average ] 1
> verifying: 1 OK
>  [ /common/functions/Linear Algebra/barycenter ] 1
> verifying: 1 OK
>  [ /common/functions/Linear Algebra/basis ] 1
> verifying: 1 OK
>  [ /common/functions/Linear Algebra/basis_affine ] 1
> verifying: 1 OK
>  [ /common/functions/Linear Algebra/basis_cols ] 1
> verifying: 1 OK
>  [ /common/functions/Linear Algebra/basis_rows ] 1
> verifying: 1 OK
>  [ /common/functions/Combinatorics/binomial ] 1
> verifying: 1 OK
>  [ /common/property_types/Algebraic Types/Matrix/methods/col ] 1
> verifying: 1 OK
>  [ /common/functions/Data Conversion/cols ] 1
> verifying: 1 OK
>  [ /common/property_types/Algebraic Types/Matrix/methods/cols ] 1
> verifying: 1 OK
>  [ /common/functions/Visualization/compose ] 1
> verifying: 1 OK
>  [ /common/functions/Data Conversion/concat_rows ] 1 2
> verifying: 1 2 OK
>  [ /common/functions/Data Conversion/convert_to ] 1 2
> verifying: 1 2 OK
>  [ /common/functions/Linear Algebra/cramer ] 1
> verifying: 1 OK
>  [ /core/functions/Schemas/create_permissive_schema ] 2
> verifying: 2 OK
>  [ /core/functions/Schemas/create_restrictive_schema ] 1
> verifying: 1 OK
>  [ /common/functions/Data Conversion/dense ] 1 2 3 4
> verifying: 1 2 3 4 OK
>  [ /common/functions/Linear Algebra/det ] 1 2
> verifying: 1 2 OK
>  [ /common/functions/Linear Algebra/diag ] 1 2
> verifying: 1 2 OK
>  [ /common/property_types/Algebraic Types/Matrix/methods/diagonal ] 1
> verifying: 1 OK
>  [ /common/property_types/Algebraic Types/Vector/methods/dim ] 1
> verifying: 1 OK
>  [ /common/functions/Utilities/distance_matrix ] 1
> verifying: 1 OK
>  [ /common/functions/Arithmetic/div ] 1
> verifying: 1 OK
>  [ /common/functions/Arithmetic/div_exact ] 1
> verifying: 1 OK
>  [ /common/property_types/Algebraic Types/Matrix/methods/div_exact ] 1
> verifying: 1 OK
>  [ /common/property_types/Algebraic Types/Vector/methods/div_exact ] 1
> verifying: 1 OK
>  [ /common/property_types/Graph Types/GraphAdjacency/methods/edge ] 1 2
> verifying: 1 2 OK
>  [ /common/functions/Linear Algebra/eigenvalues ] 1
> verifying: 1 OK
>  [ /common/property_types/Algebraic Types/Matrix/methods/elem ] 1
> verifying: 1 OK
>  [ /common/functions/Lattice Tools/eliminate_denominators ] 1
> verifying: 1 OK
>  [ /common/functions/Lattice Tools/eliminate_denominators_entire ] 1
> verifying: 1 OK
>  [ /common/functions/Lattice Tools/eliminate_denominators_entire_affine ] 1
> verifying: 1 OK
>  [ /common/functions/Lattice Tools/eliminate_denominators_in_rows ] 1
> verifying: 1 OK
>  [ 

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

[Debian Bug Tracking System]

Your message dated Wed, 22 Dec 2021 17:25:17 +
with message-id 
and subject line Bug#965855: fixed in unadf 0.7.11a-5
has caused the Debian Bug report #965855,
regarding unadf: 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.)


-- 
965855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unadf
Version: 0.7.11a-4
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package unadf 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: unadf
Source-Version: 0.7.11a-5
Done: Stephen Kitt 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 22 Dec 2021 18:05:25 +0100
Source: unadf
Architecture: source
Version: 0.7.11a-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Stephen Kitt 
Closes: 965855
Changes:
 unadf (0.7.11a-5) unstable; urgency=medium
 .
   * QA upload.
   * Upgrade to debhelper compatibility level 13. Closes: #965855.
   * Remove remote monitoring from the FAQ.
   * Enable all hardening options.
   * Update debian/watch to point at the current repository.
   * Set “Rules-Requires-Root: no”.
   * Standards-Version 4.6.0, no further change required.
Checksums-Sha1:
 8b55c0e6866b5ffc7e6ddfe46cf501b54de3dc4b 1741 unadf_0.7.11a-5.dsc
 31a316e4e200dcbdc947c6f626b618bdaf946789 18464 unadf_0.7.11a-5.debian.tar.xz
 b6d7f5e3f9462764f72c71a2fb84a503b418f33a 6380 unadf_0.7.11a-5_source.buildinfo
Checksums-Sha256:
 97f3ab43bd33214bd512994c7e7436a48c5588208968d723c475a8558e4c85a0 1741 
unadf_0.7.11a-5.dsc
 4c117cc82cd12d6449ecb78fe9860371b18525013040e5fd40a6e6fd58e50422 18464 
unadf_0.7.11a-5.debian.tar.xz
 c15456e7e002292ab03f12a611a7a5ed340d5cbd96c12a1b3b31ba0cd5e00540 6380 
unadf_0.7.11a-5_source.buildinfo
Files:
 289ae512e3f2794ce2f4b65d2f3f69cb 1741 utils optional unadf_0.7.11a-5.dsc
 086b30767c0bd2af51121e58fb19605c 18464 utils optional 
unadf_0.7.11a-5.debian.tar.xz
 174d564d5016b92eea4dc65a95288dc9 6380 utils optional 
unadf_0.7.11a-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAmHDWt0RHHNraXR0QGRl
Ymlhbi5vcmcACgkQgNMC9Yhtg5wSrQ/+L03C80g3Dc+NS1fJUONPHrCbPiHiEA9y
GS+dnSVlfTBOrWdF972abzzf7n2KYHBZm0tnBrov9hxC1NJA4BTs+dzOOpcUbKh+
v+s8069LmuBEubrHu6wa//zBkDhmVB6JblC1CWMe3BjmLYvUh4XaTlKHjgmiqhlU
jgj0LJjtkd3KnEsaCr3EUTxKo6FrGQmb+pIi80Ikkl4kptqVsDQRDY1SbP3onW1f
LR10n7qeakW19djbaxr5FdvZKr2UBRgN8CQH2HleNBie7t1ljSA22OULPF3cYQY/
Vqx9cgp4sLdL574qaEZvX0lQ7m5oaTGhGmzqGXpKi4s62HVMyeiQ+Ouz8Cec1H2S
5BkirBS5lw8ZZ5GMW6hOUoWaxRP8v2/XzgWIU7b0MLedHBGGDGcB7X/GQBXtZOI7
n3i9MDN9y8lJuUypIVaG+xavOAgopjxpFHoQuyl6zslyQeqK4KhpHoXETFKBC43M
RHtcaJqxZBI5+/kbPfY2hONKzZ+j6sshRJHAy1dV/bA89U4r3cCA7YfrueSKYuNk
9aEnt9K4aekINznnSzFun09nKP29qtp6+NrfB5hQtyXBIyS7vlDSraMObDwJaq2l

Bug#1002278: marked as done (node-ts-jest: FTBFS: Cannot find module 'pretty-format' or its corresponding type declarations.)

[Debian Bug Tracking System]

Your message dated Wed, 22 Dec 2021 17:24:03 +
with message-id 
and subject line Bug#1002278: fixed in node-ts-jest 27.0.7+~cs0.2.6-2
has caused the Debian Bug report #1002278,
regarding node-ts-jest: FTBFS: Cannot find module 'pretty-format' or its 
corresponding type declarations.
to be marked as done.

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

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


-- 
1002278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002278
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-ts-jest
Version: 27.0.7+~cs0.2.6-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mv node_modules/fast-json-stable-stringify 
> node_modules/.fast-json-stable-stringify
> dh_auto_build --buildsystem=nodejs
> Found debian/nodejs/bs-logger/build
>   cd ./bs-logger && sh -ex ../debian/nodejs/bs-logger/build
> + tsc -p tsconfig.build.json
> ../../../../usr/share/nodejs/jest-diff/build/types.d.ts:7:34
>  - error TS2307: Cannot find module 'pretty-format' or its 
> corresponding type declarations.
> 
> 7 import type { CompareKeys } from 'pretty-format';
>    ~~~
> 
> 
> Found 1 error.
> 
> dh_auto_build: error: cd ./bs-logger && sh -ex 
> ../debian/nodejs/bs-logger/build returned exit code 2
> make[1]: *** [debian/rules:14: override_dh_auto_build] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/node-ts-jest_27.0.7+~cs0.2.6-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: node-ts-jest
Source-Version: 27.0.7+~cs0.2.6-2
Done: Yadd 

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

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

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-ts-jest package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 22 Dec 2021 18:07:29 +0100
Source: node-ts-jest
Architecture: source
Version: 27.0.7+~cs0.2.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1002278
Changes:
 node-ts-jest (27.0.7+~cs0.2.6-2) unstable; urgency=medium
 .
   * Update tsc bug workaround (Closes: #1002278)
Checksums-Sha1: 
 794b60563a059d30f5dbd629482b6a55d98e802b 3228 
node-ts-jest_27.0.7+~cs0.2.6-2.dsc
 80dc7aa78e1c0bdc40d0cd111ad78bd783a9aa61 11084 
node-ts-jest_27.0.7+~cs0.2.6-2.debian.tar.xz
Checksums-Sha256: 
 2b01739a5009e011ec2decb80fd75635995edfe28c7b2c86f128a05ac2f4bfa3 3228 
node-ts-jest_27.0.7+~cs0.2.6-2.dsc
 a286224d5dd05f57cf33521d9bb7e69f32a57dc0594e721ce64c8e3f38dd53a5 11084 
node-ts-jest_27.0.7+~cs0.2.6-2.debian.tar.xz
Files: 
 46c813c7a43c9f9589b325bed5fed8cd 3228 javascript optional 
node-ts-jest_27.0.7+~cs0.2.6-2.dsc
 da3a4a5790456da55986d8576a446b2e 11084 javascript optional 
node-ts-jest_27.0.7+~cs0.2.6-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmHDW7MACgkQ9tdMp8mZ
7uljvA/+IMiCVFCEhHt+ChvficmqX5M3Jqahfexo4Xb9BlbPdT5fP6A0Zcl0l0h1
Ynj7p/KBlXMR7nL/c39OfHveSOkJFQVsMfUKw4kVdV8I56ckFPl8W6wFFVys6liH
hFhjYoA+GPJXXMcHVAtxmUFt4uHzUpK45k5juIwgmBjiUUu9cQT+S4SXBd/WXpxd
EGf8jLXkcIG0NddsjKNKHL52C2M5wpLLkMUS5hxMDcAGN8f9D0IHaedKQ3EsISpv
OoSujGVkj1PAabXDgefnyBUcP12aZwQ/1Yz0KS4uWSi/ZZ9vBc/zICHLUeY4NZ3C
2sMCZtR6Cano/Ow7T+kxZHabDqzoVIhs7pfc0DgpIKmOw9oFLryXu2lplXGh44qM

Bug#1002222: marked as done (victoriametrics: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 [...] returned exit code 1)

[Debian Bug Tracking System]

Your message dated Wed, 22 Dec 2021 17:25:25 +
with message-id 
and subject line Bug#100: fixed in victoriametrics 1.71.0+ds1-1
has caused the Debian Bug report #100,
regarding victoriametrics: FTBFS: dh_auto_test: error: cd _build && go test 
-vet=off -v -p 4 [...] returned exit code 1
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> --- PASS: TestTagFilterMatchSuffix/regexp-prefix-contains-suffix (0.00s)
> --- PASS: TestTagFilterMatchSuffix/negative-regexp-prefix-contains-suffix 
> (0.00s)
> --- PASS: 
> TestTagFilterMatchSuffix/negative-regexp-noprefix-contains-suffix (0.00s)
> --- PASS: TestTagFilterMatchSuffix/regexp-prefix-special-suffix (0.00s)
> --- PASS: TestTagFilterMatchSuffix/negative-regexp-prefix-special-suffix 
> (0.00s)
> --- PASS: 
> TestTagFilterMatchSuffix/negative-regexp-noprefix-special-suffix (0.00s)
> --- PASS: TestTagFilterMatchSuffix/regexp-or-suffixes (0.00s)
> --- PASS: TestTagFilterMatchSuffix/negative-regexp-or-suffixes (0.00s)
> --- PASS: TestTagFilterMatchSuffix/regexp-iflag-no-suffix (0.00s)
> --- PASS: TestTagFilterMatchSuffix/negative-regexp-iflag-no-suffix (0.00s)
> --- PASS: TestTagFilterMatchSuffix/regexp-iflag-any-suffix (0.00s)
> --- PASS: TestTagFilterMatchSuffix/negative-regexp-iflag-any-suffix 
> (0.00s)
> --- PASS: TestTagFilterMatchSuffix/non-empty-string-regexp-negative-match 
> (0.00s)
> --- PASS: TestTagFilterMatchSuffix/non-empty-string-regexp-match (0.00s)
> --- PASS: TestTagFilterMatchSuffix/match-all-regexp-negative-match (0.00s)
> --- PASS: TestTagFilterMatchSuffix/match-all-regexp-match (0.00s)
> === RUN   TestGetOrValues
> --- PASS: TestGetOrValues (0.00s)
> === RUN   TestGetRegexpPrefix
> --- PASS: TestGetRegexpPrefix (0.00s)
> === RUN   TestTagFiltersString
> --- PASS: TestTagFiltersString (0.00s)
> === RUN   TestTagFiltersAddEmpty
> --- PASS: TestTagFiltersAddEmpty (0.00s)
> === RUN   TestTimeRangeFromPartition
> --- PASS: TestTimeRangeFromPartition (0.10s)
> === RUN   TestMarshaledTSIDSize
> --- PASS: TestMarshaledTSIDSize (0.00s)
> === RUN   TestTSIDLess
> --- PASS: TestTSIDLess (0.00s)
> === RUN   TestTSIDMarshalUnmarshal
> --- PASS: TestTSIDMarshalUnmarshal (0.00s)
> PASS
> okgithub.com/VictoriaMetrics/VictoriaMetrics/lib/storage  21.616s
> ? github.com/VictoriaMetrics/VictoriaMetrics/lib/storagepacelimiter   
> [no test files]
> ? github.com/VictoriaMetrics/VictoriaMetrics/lib/syncwg   [no test files]
> === RUN   TestCreateMetricNameError
> 2021-12-20T18:55:18.404Z  panic   
> VictoriaMetrics/lib/tenantmetrics/counter_map.go:64 BUG: metric cannot be 
> empty
> --- PASS: TestCreateMetricNameError (0.00s)
> === RUN   TestCreateMetricNameSuccess
> --- PASS: TestCreateMetricNameSuccess (0.00s)
> === RUN   TestCounterMap
> --- PASS: TestCounterMap (0.00s)
> === RUN   TestCounterMapConcurrent
> --- PASS: TestCounterMapConcurrent (0.00s)
> PASS
> okgithub.com/VictoriaMetrics/VictoriaMetrics/lib/tenantmetrics0.012s
> ? github.com/VictoriaMetrics/VictoriaMetrics/lib/timerpool[no 
> test files]
> === RUN   TestSetOps
> --- PASS: TestSetOps (0.17s)
> === RUN   TestSetBasicOps
> === RUN   TestSetBasicOps/items_1
> === RUN   TestSetBasicOps/items_2
> === RUN   TestSetBasicOps/items_3
> === RUN   TestSetBasicOps/items_4
> === RUN   TestSetBasicOps/items_5
> === RUN   TestSetBasicOps/items_6
> === RUN   TestSetBasicOps/items_100
> === RUN   TestSetBasicOps/items_1000
> === RUN   TestSetBasicOps/items_1
> === RUN   TestSetBasicOps/items_10
> === RUN   TestSetBasicOps/items_100
> --- PASS: TestSetBasicOps (1.30s)
> --- PASS: TestSetBasicOps/items_1 (0.00s)
> --- PASS: TestSetBasicOps/items_2 (0.00s)
> --- PASS: TestSetBasicOps/items_3 (0.00s)
> --- PASS: TestSetBasicOps/items_4 (0.00s)
> --- PASS: TestSetBasicOps/items_5 (0.00s)
> --- PASS: TestSetBasicOps/items_6 (0.00s)
> --- PASS: TestSetBasicOps/items_100 (0.00s)
> --- PASS: TestSetBasicOps/items_1000 (0.00s)
> --- PASS: TestSetBasicOps/items_1 (0.01s)
> --- PASS: TestSetBasicOps/items_10 (0.15s)
> --- PASS: 

Bug#1002155: libgoby-java: FTBFS: [WARNING] /<>/goby-io/../goby-distribution/src/main/java/org/campagnelab/goby/modes/FastaToCompactMode.java:23: error: package edu.rit.pj does not exist

[Pierre Gruet]

Control: tags -1 unreproducible help

Hi,

Currently I am not able to reproduce the issue on my computer nor on 
several machines of the Debian project.


I shall investigate further a bit later, but so far looking at a diff 
between the provided build log and mine has not helped.


The warning mentioned in the bug title is issued by the Javadoc builder, 
which we do not use. It does not trigger the failure of the build.
The real issue is in the tests: for some reason, a FileNotFoundException 
is raised by the FileOutputStream constructor when being called on files 
in the test-results/ directory.


Cheers,

--
Pierre

Processed: Re: libgoby-java: FTBFS: [WARNING] /<>/goby-io/../goby-distribution/src/main/java/org/campagnelab/goby/modes/FastaToCompactMode.java:23: error: package edu.rit.pj does not exis

[Debian Bug Tracking System]

Processing control commands:

> tags -1 unreproducible help
Bug #1002155 [src:libgoby-java] libgoby-java: FTBFS: [WARNING] 
/<>/goby-io/../goby-distribution/src/main/java/org/campagnelab/goby/modes/FastaToCompactMode.java:23:
 error: package edu.rit.pj does not exist
Added tag(s) unreproducible and help.

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

Processed: Bug#1002278 marked as pending in node-ts-jest

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1002278 [src:node-ts-jest] node-ts-jest: FTBFS: Cannot find module 
'pretty-format' or its corresponding type declarations.
Added tag(s) pending.

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

Processed: Bug#1002278 marked as pending in node-ts-jest

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1002278 [src:node-ts-jest] node-ts-jest: FTBFS: Cannot find module 
'pretty-format' or its corresponding type declarations.
Ignoring request to alter tags of bug #1002278 to the same tags previously set

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

Bug#1002278: marked as pending in node-ts-jest

[Yadd]

Control: tag -1 pending

Hello,

Bug #1002278 in node-ts-jest 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-ts-jest/-/commit/fe880b5bacf523a86adc0f55326e80550de42d08


Update tsc bug workaround

Closes: #1002278


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1002278

Bug#1002278: marked as pending in node-ts-jest

[Yadd]

Control: tag -1 pending

Hello,

Bug #1002278 in node-ts-jest 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-ts-jest/-/commit/fe880b5bacf523a86adc0f55326e80550de42d08


Update tsc bug workaround

Closes: #1002278


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1002278

Bug#1001591: [Pkg-matrix-maintainers] Bug#1002380: drops attributes used by reverse dependencies

[Pierre-Elliott Bécue]

Jonas Smedegaard  wrote on 22/12/2021 at 12:37:21+0100:

> [[PGP Signed Part:No public key for 2C7C3146C1A00121 created at 
> 2021-12-22T12:37:23+0100 using RSA]]
> Control: severity -1 serious
>
> [ re-posting to correct bug ]
>
> Releasing a new major release of mistune has caused several packages to 
> no longer be usable at all.
>
> I consider this a serious issue, and have raised severity accordingly.
>
> At least python-m2r have no support for mistune v2 in sight (and its 
> newer fork - python-m2r2 - does not either). Concretely I propose to 
> revert this by a (messy) 2.0.0+really0.8.4 release until reverse 
> dependencies can use the newer major version of mistune.
>
> It seems that a release of python3-django-hyperkitty requiring mistune 
> v2 has already been uploaded to unstable as well.  That is very 
> unfortunate, and will need to be rolled back as well.  Mailman 
> maintainers cc'ed.
>
> Please in future make sure to check reverse dependencies *before* 
> releasing a major new upstream release to unstable, because reversal is 
> messy (complicates package versioning).
>
>
> Kind regards, and thanks for maintaining mistune,

The issue is that many reverse dependencies of mistune are not
maintained. If I follow your opinion on this, the following issues
arise:

 1. There is no proper way for software to be mistune 0.8.4 and mistune
2.0.0 compatible at the same way, so the reverse dependencies won't
be able to update without mistune 2.0.0 being in unstable
 2. I'll need mailman3 to be able to enter testing at some point and I
don't think we can expect it to wait for software that is no longer
maintained upstream

Apart from these two points, there are multiple cases where software are
updated despite the impact on the reverse dependencies. Typically Python
updates don't wait for dependencies to be ready in case of breaking
changes, and that looks to me quite normal, despite it bringing more
work to me as a mailman or python packages maintainer.

I'd be happy to hear about how you suggest me to handle the unmaintained
reverse-dependencies like m2r.

For now I'd rather let a serious bug block the migration of mistune from
unstable to testing and accept that some packages are not working in
unstable for now.

Cheers,
-- 
PEB


signature.asc
Description: PGP signature

Bug#1000336: numba: FTBFS with Python 3.10

[Nilesh Patra]

Hi all,

On Fri, 10 Dec 2021 08:56:49 +0100 Andreas Tille  wrote:
> dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:237: python3.10 setup.py clean 
> ...
>   from distutils import sysconfig
> Traceback (most recent call last):
>   File "/build/numba-0.54.1/setup.py", line 51, in 
> _guard_py_ver()
>   File "/build/numba-0.54.1/setup.py", line 48, in _guard_py_ver
> raise RuntimeError(msg.format(cur_py, min_py, max_py))
> RuntimeError: Cannot install on Python version 3.10.1; only versions 
> >=3.7,<3.10 are supported.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.10 setup.py clean 
> 
> 
> Hoping for an upstream fix of #7562 in their tracker now.

Upstream has mentioned that it has been fixed upstream. Diane, could you
please do the needful and upload?

Actually because of the current state of numba, several reverse depends are 
FTBFS so it's
bit urgent to push. Apologies for getting on your nerves, though.

Regards,
Nilesh 


signature.asc
Description: PGP signature

Bug#1002270: marked as done (kdump-tools: FTBFS: shellcheck error)

[Debian Bug Tracking System]

Your message dated Wed, 22 Dec 2021 16:19:42 +
with message-id 
and subject line Bug#1002270: fixed in kdump-tools 1:1.6.10
has caused the Debian Bug report #1002270,
regarding kdump-tools: FTBFS: shellcheck error
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> shellcheck -e SC1090,SC1091,SC3043 debian/kdump-config.in 
> debian/kernel-postrm-delete-initrd debian/kdump-tools.postinst 
> debian/kdump-tools.preinst debian/kdump-tools.postrm 
> debian/kdump-tools.config debian/kernel-postinst-generate-initrd 
> debian/initramfs.local-bottom debian/kdump-tools.init debian/initramfs.hook
> 
> In debian/kdump-config.in line 224:
>   version=${version#$symlink-}
>   ^--^ SC2295 (info): 
> Expansions inside ${..} need to be quoted separately, otherwise they match as 
> patterns.
> 
> Did you mean: 
>   version=${version#"$symlink"-}
> 
> For more information:
>   https://www.shellcheck.net/wiki/SC2295 -- Expansions inside ${..} need to 
> b...
> make[1]: *** [debian/rules:64: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/kdump-tools_1.6.9_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: kdump-tools
Source-Version: 1:1.6.10
Done: dann frazier 

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

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

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

Debian distribution maintenance software
pp.
dann frazier  (supplier of updated kdump-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 22 Dec 2021 08:38:12 -0700
Source: kdump-tools
Architecture: source
Version: 1:1.6.10
Distribution: unstable
Urgency: medium
Maintainer: Debian Kdump 
Changed-By: dann frazier 
Closes: 1002270
Changes:
 kdump-tools (1:1.6.10) unstable; urgency=medium
 .
   * kdump-config: Fix FTBFS due to new shellcheck warning (Closes: #1002270).
Checksums-Sha1:
 d66747a043252175491e952c95b0e842342b5253 1887 kdump-tools_1.6.10.dsc
 52a745b11369a85028532526ed00b95163e31e4e 38844 kdump-tools_1.6.10.tar.xz
 7bf6489634e168ffa5aa2ad4c428540d257894ba 6246 
kdump-tools_1.6.10_source.buildinfo
Checksums-Sha256:
 9c272de1d8c973d2470faa8eb51ab336fb6a1fed05f0508085bedd625842b4fd 1887 
kdump-tools_1.6.10.dsc
 bc7611c7ca0386d66d3739d5fe8055c1aa734bcf6f80bf213cbc6856202e80fb 38844 
kdump-tools_1.6.10.tar.xz
 7e50c7c0452f9cc5e9e45a3668feabfc642e09b5bf24fc8f3bdb4e354a0b4b53 6246 
kdump-tools_1.6.10_source.buildinfo
Files:
 9745547984a4f659517ed51b43429ba7 1887 devel optional kdump-tools_1.6.10.dsc
 f6572935a0e69cf98bfa40dc72e8609e 38844 devel optional kdump-tools_1.6.10.tar.xz
 239978a85b704641342f618565a204d7 6246 devel optional 
kdump-tools_1.6.10_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEECfR9vy0y7twkQ+vuG/g8XlT8hkAFAmHDSQURHGRhbm5mQGRl
Ymlhbi5vcmcACgkQG/g8XlT8hkC+Zw//fF47sPZRWNFfXVYkYkOp9pTRbkZFQMBD
99Lfiyl23UEJaZ6T13YdzHY6NcfPmM1Pwiyd3fVxekws6ei/qKoJkSQ3Df5+zy96
6aBZ8vtX/3xeuwKLEEJpknMXeefbIL0d6uGa80mEKHYppci46BgMLgs4wFU76tFy
js4JnBKmN8/AU2JCnedYyFPyJWPlr+45hJgkchZu9WGlnEbJ2nDY55wPrABrwwfW

Bug#1002447: marked as done (python-semver: FTBFS: FAILED docs/usage.rst::usage.rst)

[Debian Bug Tracking System]

Your message dated Wed, 22 Dec 2021 16:04:36 +
with message-id 
and subject line Bug#1002447: fixed in python-semver 2.10.2-3
has caused the Debian Bug report #1002447,
regarding python-semver: FTBFS: FAILED docs/usage.rst::usage.rst
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> set -e ; for pyvers in 3.10 3.9; do \
>   PYTHONPATH=/<>/debian/tmp/usr/lib/python3/dist-packages 
> python$pyvers -m pytest . ; \
> done
> = test session starts 
> ==
> platform linux -- Python 3.10.1, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
> rootdir: /<>, configfile: setup.cfg
> plugins: cov-3.0.0
> collected 308 items
> 
> README.rst . [  
> 0%]
> semver.py .  [  
> 9%]
> test_semver.py . [ 
> 28%]
>  [ 
> 51%]
>  [ 
> 75%]
>  [ 
> 98%]
> ...  [ 
> 99%]
> docs/development.rst .   [ 
> 99%]
> docs/usage.rst F 
> [100%]
> 
> === FAILURES 
> ===
> _ [doctest] usage.rst 
> __
> 431True
> 432 
> 433   The opposite does also work::
> 434 
> 435>>> dict(major=1) < v
> 436True
> 437 
> 438   If the dictionary contains unknown keys, you get a :class:`TypeError` 
> exception::
> 439 
> 440 >>> v > dict(major=1, unknown=42)
> Differences (ndiff with -expected +actual):
>   Traceback (most recent call last):
> - ...
> +   File "/usr/lib/python3.10/doctest.py", line 1346, in __run
> + exec(compile(example.source, filename, "single",
> +   File "", line 1, in 
> + v > dict(major=1, unknown=42)
> +   File "/<>/semver.py", line 152, in wrapper
> + return operator(self, other)
> +   File "/<>/semver.py", line 523, in __gt__
> + return self.compare(other) > 0
> +   File "/<>/semver.py", line 429, in compare
> + other = cls(**other)
> - TypeError: __init__() got an unexpected keyword argument 'unknown'
> + TypeError: VersionInfo.__init__() got an unexpected keyword argument 
> 'unknown'
> ?
> 
> /<>/docs/usage.rst:440: DocTestFailure
> === short test summary info 
> 
> FAILED docs/usage.rst::usage.rst
>  1 failed, 307 passed in 0.55s 
> =
> make[1]: *** [debian/rules:15: override_dh_auto_test] Error 1


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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-semver
Source-Version: 2.10.2-3
Done: Thomas Goirand 

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

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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1002...@bugs.debian.org,
and 

Bug#1002127: marked as done (python-trie: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Wed, 22 Dec 2021 16:04:44 +
with message-id 
and subject line Bug#1002127: fixed in python-trie 0.4.0+ds-1
has caused the Debian Bug report #1002127,
regarding python-trie: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p "3.10 3.9" returned exit code 13
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.)


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

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/docs'
> sphinx-build -b html -d build/doctrees   source build/html
> Running Sphinx v4.3.2
> making output directory... done
> WARNING: html_static_path entry '_static' does not exist
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 1 source files that are out of date
> updating environment: [new config] 1 added, 0 changed, 0 removed
> reading sources... [100%] index
> 
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [100%] index
> 
> generating indices... genindex py-modindex done
> writing additional pages... search done
> copying static files... done
> copying extra files... done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded, 1 warning.
> 
> The HTML pages are in build/html.
> 
> Build finished. The HTML pages are in build/html.
> make[2]: Leaving directory '/<>/docs'
> dh_auto_build
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
> I: pybuild base:237: /usr/bin/python3.10 setup.py build 
> /<>/setup.py:3: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils.core import setup
> running build
> running build_py
> copying pytrie.py -> /<>/.pybuild/cpython3_3.10_trie/build
> I: pybuild base:237: /usr/bin/python3 setup.py build 
> running build
> running build_py
> copying pytrie.py -> /<>/.pybuild/cpython3_3.9_trie/build
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 
> in use)
> I: pybuild pybuild:286: cp /<>/test/test_trie.py 
> /<>/.pybuild/cpython3_3.10_trie/build
> I: pybuild base:237: cd /<>/.pybuild/cpython3_3.10_trie/build; 
> python3.10 -m unittest discover -v 
> test_trie (unittest.loader._FailedTest) ... ERROR
> 
> ==
> ERROR: test_trie (unittest.loader._FailedTest)
> --
> ImportError: Failed to import test module: test_trie
> Traceback (most recent call last):
>   File "/usr/lib/python3.10/unittest/loader.py", line 436, in _find_test_path
> module = self._get_module_from_name(name)
>   File "/usr/lib/python3.10/unittest/loader.py", line 377, in 
> _get_module_from_name
> __import__(name)
>   File "/<>/.pybuild/cpython3_3.10_trie/build/test_trie.py", 
> line 2, in 
> from pytrie import SortedStringTrie
>   File "/<>/.pybuild/cpython3_3.10_trie/build/pytrie.py", line 
> 48, in 
> from collections import MutableMapping
> ImportError: cannot import name 'MutableMapping' from 'collections' 
> (/usr/lib/python3.10/collections/__init__.py)
> 
> 
> --
> Ran 1 test in 0.000s
> 
> FAILED (errors=1)
> E: pybuild pybuild:355: test: plugin distutils failed with: exit code=1: cd 
> /<>/.pybuild/cpython3_3.10_trie/build; python3.10 -m unittest 
> discover -v 
> I: pybuild pybuild:286: cp /<>/test/test_trie.py 
> /<>/.pybuild/cpython3_3.9_trie/build
> I: pybuild base:237: cd /<>/.pybuild/cpython3_3.9_trie/build; 
> python3.9 -m unittest discover -v 
> test_consistency_wprefix (test_trie.TestTrie) ... ok
> test_items_wprefix (test_trie.TestTrie) ... ok
> test_iter_prefix_items (test_trie.TestTrie) ... ok
> test_iter_prefix_values (test_trie.TestTrie) ... ok
> test_iter_prefixes (test_trie.TestTrie) ... ok
> test_keys_wprefix (test_trie.TestTrie) ... ok
> test_longest_prefix (test_trie.TestTrie) ... ok
> test_longest_prefix_item 

Processed: Re: mpi4py: FTBFS: testJoin socket.gaierror: Name or service not known

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 mpi4py: FTBFS: testJoin socket.gaierror: Name or service not known
Bug #1002082 [src:mpi4py] mpi4py: FTBFS: ld: cannot find -llmpe
Changed Bug title to 'mpi4py: FTBFS: testJoin socket.gaierror: Name or service 
not known' from 'mpi4py: FTBFS: ld: cannot find -llmpe'.

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

Bug#1002082: mpi4py: FTBFS: testJoin socket.gaierror: Name or service not known

[Drew Parsons]

Source: mpi4py
Version: 3.1.3-1
Followup-For: Bug #1002082
Control: retitle -1 mpi4py: FTBFS: testJoin socket.gaierror: Name or service 
not known


The actual error is

testJoin (test_dynproc.TestDPM) ... ERROR

==
ERROR: testJoin (test_dynproc.TestDPM)
--
Traceback (most recent call last):
  File "/<>/test/test_dynproc.py", line 175, in testJoin
server.bind((host, 0))
socket.gaierror: [Errno -2] Name or service not known

Processed: Bug#1002447 marked as pending in python-semver

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1002447 [src:python-semver] python-semver: FTBFS: FAILED 
docs/usage.rst::usage.rst
Added tag(s) pending.

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

Bug#1002447: marked as pending in python-semver

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/python/python-semver/-/commit/127a5928c6ce3ee1716f1c54d015b33915393da0


Correctly launch unit tests (Closes: #1002447).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1002447

Bug#1002229: libnet-traceroute-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2

[gregor herrmann]

COntrol: tag -1 + unreproducible moreinfo

On Tue, 21 Dec 2021 17:33:43 +0100, Lucas Nussbaum wrote:

> Source: libnet-traceroute-perl
> Version: 1.15-2
> Severity: serious
> Justification: FTBFS

> > /<>/blib/lib/Net/Traceroute.pm:Net::Traceroute::debug_print:230:
> >  Running in debug mode
> > /<>/blib/lib/Net/Traceroute.pm:Net::Traceroute::debug_print:294:
> >  Performing traceroute
> > /<>/blib/lib/Net/Traceroute.pm:Net::Traceroute::debug_print:487:
> >  $VAR1 = bless( {
> >  'debug' => 9,
> >  'stat' => 2,
> >  'host' => 'ip-10-84-232-242',
> >  'trace_program' => 'traceroute',
> >  'timeout' => 30
> >}, 'Net::Traceroute' );
> > No output from traceroute.  Exec failure? at 
> > /<>/blib/lib/Net/Traceroute.pm line 360.
> > # Looks like your test exited with 255 before it could output anything.
> > t/95-sys-traceroute.t . 
> > 1..2
> > Dubious, test returned 255 (wstat 65280, 0xff00)
> > Failed 2/2 subtests 


Hi Lucas,

thanks for your bug report.

Yesterday evening, 3 of us in the Perl team could not reproduce this
failure locally. From looking at the test and the actual code, what
seems to happen is that `traceroute' does not produce _any_ output,
which is a bit surprising.

Do you have any idea how this can happen in your test environment or
any information for us, what is special about it?


As a side note, the test itself is marked as TODO, i.e. expected to
fail, with a comment that it's fragile, so we might as well skip it
completely. - Oh, that comes from our own patch :) And the patch
headers mention #849933 and #980475.

Still, seeing the code explode _before_ reaching this stage is
puzzling.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Pink Floyd: Shine On You Crazy Diamond (Parts 1-5)


signature.asc
Description: Digital Signature

Processed: Re: Bug#1002229: libnet-traceroute-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + unreproducible moreinfo
Bug #1002229 [src:libnet-traceroute-perl] libnet-traceroute-perl: FTBFS: 
dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2
Added tag(s) moreinfo and unreproducible.

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

Bug#1002438: marked as pending in python-osc-lib

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/libs/python-osc-lib/-/commit/48a7c758c4d5456ef49d04229248dea2781d7535


* Blacklist failing broken tests (Closes: #1002438):
- test_add_tag_filtering_option_to_parser()
- test_add_tag_option_to_parser_for_create()
- test_add_tag_option_to_parser_for_set()
- test_add_tag_option_to_parser_for_unset()


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1002438

Processed: Bug#1002438 marked as pending in python-osc-lib

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1002438 [src:python-osc-lib] python-osc-lib: FTBFS: 
testtools.matchers._impl.MismatchError
Added tag(s) pending.

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

Processed: Bug#1002435 marked as pending in python-oslo.config

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1002435 [src:python-oslo.config] python-oslo.config: FTBFS: 
testtools.matchers._impl.MismatchError: 'optional' not in "usage
Added tag(s) pending.

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

Bug#1002435: marked as pending in python-oslo.config

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/oslo/python-oslo.config/-/commit/5be886d9db78cc8ee4ca81705cda9d466f75e7d7


* Blacklist failing tests (Closes: #1002435):
- HelpTestCase.test_print_help
- HelpTestCase.test_print_strOpt_with_choices_help


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1002435

Processed: nbconvert is mistuned

[Debian Bug Tracking System]

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

> reassign 1002375 python3-nbconvert nbconvert/6.1.0-1
Bug #1002375 [src:mdtraj] mdtraj: FTBFS: AttributeError: module 'mistune' has 
no attribute 'BlockGrammar'
Bug reassigned from package 'src:mdtraj' to 'python3-nbconvert'.
No longer marked as found in versions mdtraj/1.9.6-3.
Ignoring request to alter fixed versions of bug #1002375 to the same values 
previously set
Bug #1002375 [python3-nbconvert] mdtraj: FTBFS: AttributeError: module 
'mistune' has no attribute 'BlockGrammar'
Marked as found in versions nbconvert/6.1.0-1.
> forcemerge 1001283 1002375
Bug #1001283 [python3-nbconvert] python3-nbconvert: nbconvert Depends: 
python3-mistune (<< 2)
Bug #1002375 [python3-nbconvert] mdtraj: FTBFS: AttributeError: module 
'mistune' has no attribute 'BlockGrammar'
Set Bug forwarded-to-address to 
'https://github.com/jupyter/nbconvert/issues/1685'.
1002375 was not blocked by any bugs.
1002375 was not blocking any bugs.
Added blocking bug(s) of 1002375: 1001591
Added indication that 1002375 affects src:mistune
Bug #1001283 [python3-nbconvert] python3-nbconvert: nbconvert Depends: 
python3-mistune (<< 2)
Added tag(s) ftbfs, sid, and bookworm.
Merged 1001283 1002375
> affects 1001283 src:mdtraj
Bug #1001283 [python3-nbconvert] python3-nbconvert: nbconvert Depends: 
python3-mistune (<< 2)
Bug #1002375 [python3-nbconvert] mdtraj: FTBFS: AttributeError: module 
'mistune' has no attribute 'BlockGrammar'
Added indication that 1001283 affects src:mdtraj
Added indication that 1002375 affects src:mdtraj
> thanks
Stopping processing here.

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

Bug#996836: marked as done (node-webpack: webpack embeds binary files in es-module-lexer component)

[Debian Bug Tracking System]

Your message dated Wed, 22 Dec 2021 14:38:11 +
with message-id 
and subject line Bug#996836: fixed in node-webpack 5.65.0+dfsg+~cs9.20.9-1
has caused the Debian Bug report #996836,
regarding node-webpack: webpack embeds binary files in es-module-lexer component
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.)


-- 
996836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-webpack
Version: 5.58.2+~cs5.11.7-1
Severity: serious
Justification: DFSG

webpack 5.58 uses es-module-lexer. For now, this component is downloaded
including some binary files (WASM,...). This should be fixed before
going to unstable.
--- End Message ---
--- Begin Message ---
Source: node-webpack
Source-Version: 5.65.0+dfsg+~cs9.20.9-1
Done: Ayoyimika Ajibade 

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

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

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

Debian distribution maintenance software
pp.
Ayoyimika Ajibade  (supplier of updated 
node-webpack package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 22 Dec 2021 14:01:35 +0100
Source: node-webpack
Architecture: source
Version: 5.65.0+dfsg+~cs9.20.9-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Ayoyimika Ajibade 
Closes: 996836
Changes:
 node-webpack (5.65.0+dfsg+~cs9.20.9-1) experimental; urgency=medium
 .
   [ Yadd ]
   * Team upload
   * Exclude non DFSG files from import (Closes: #996836) and repack
   * Disable es-module-lexer and don't install it for now
   * Clean lintian overrides
   * Update nodejs dependency to nodejs:any
 .
   [ Ayoyimika Ajibade ]
   * embed webpack-cli
   * New upstream version 5.65.0+dfsg+~cs9.20.9
   * disable failing test due to error from jest-resolve
   * Fix webpack-cli path
Checksums-Sha1: 
 be38c7dedc6061ab35918291510a6dbccc8135da 3809 
node-webpack_5.65.0+dfsg+~cs9.20.9-1.dsc
 3d7351885715cf5c17b64ef3ae13ecf398d980e2 27336 
node-webpack_5.65.0+dfsg+~cs9.20.9.orig-es-module-lexer.tar.xz
 e3ed48e60772242735e872bf4b6b4c6c74b82b41 146976 
node-webpack_5.65.0+dfsg+~cs9.20.9.orig-terser-webpack-plugin.tar.xz
 1bf11c20976e75c70e89f09fccf3c6939171cccf 16832 
node-webpack_5.65.0+dfsg+~cs9.20.9.orig-webpack-cli.tar.xz
 d4ec4f5c08a6c135b722f12028acb1ceb88ff3f8 1233160 
node-webpack_5.65.0+dfsg+~cs9.20.9.orig.tar.xz
 b51cd50f63f815f2a5478eaf4fec2dc21950e1da 6544 
node-webpack_5.65.0+dfsg+~cs9.20.9-1.debian.tar.xz
Checksums-Sha256: 
 b33aa6becf96c68b2aaea2bb316dd56208674361c3770b09a87303200dbe8a8e 3809 
node-webpack_5.65.0+dfsg+~cs9.20.9-1.dsc
 d0b37bdc378490db5b7ba73d7f512c6222b32754d97b222492fad96338d75b01 27336 
node-webpack_5.65.0+dfsg+~cs9.20.9.orig-es-module-lexer.tar.xz
 59bb8639b25deb685f9da7bf34f52690218684155cb7e1608c31477a34edb5e6 146976 
node-webpack_5.65.0+dfsg+~cs9.20.9.orig-terser-webpack-plugin.tar.xz
 362d04ee5f34861d654bfee73d73ce3e45f5b3ca864d136b6d7562ee88e65e50 16832 
node-webpack_5.65.0+dfsg+~cs9.20.9.orig-webpack-cli.tar.xz
 e1381d9d6e2caca05ddd47bac59bb12648bdc4b0ce5424604818ecedd39c587e 1233160 
node-webpack_5.65.0+dfsg+~cs9.20.9.orig.tar.xz
 258cd4b96181be18945b5669a64bc0b5f47084d77242cc8b03257a9f7c256b8a 6544 
node-webpack_5.65.0+dfsg+~cs9.20.9-1.debian.tar.xz
Files: 
 fdd735ed4c1a88fecdfe48fa3de58807 3809 javascript optional 
node-webpack_5.65.0+dfsg+~cs9.20.9-1.dsc
 eed420483e370562d61cd1887f3507c5 27336 javascript optional 
node-webpack_5.65.0+dfsg+~cs9.20.9.orig-es-module-lexer.tar.xz
 6b1fdef7d0a431d825651f4480151179 146976 javascript optional 
node-webpack_5.65.0+dfsg+~cs9.20.9.orig-terser-webpack-plugin.tar.xz
 a352439a704378433c97017fb225f842 16832 javascript optional 
node-webpack_5.65.0+dfsg+~cs9.20.9.orig-webpack-cli.tar.xz
 3f798d8a07af03a97a6bb04443057367 1233160 javascript optional 
node-webpack_5.65.0+dfsg+~cs9.20.9.orig.tar.xz
 8d6c0f327eb1663da1f7f39772bec9f2 6544 javascript optional 
node-webpack_5.65.0+dfsg+~cs9.20.9-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmHDM3cACgkQ9tdMp8mZ

Bug#1001482: marked as done (restrictedpython: (autopkgtest) needs update for python3.10: deprecation warning on stderr)

[Debian Bug Tracking System]

Your message dated Wed, 22 Dec 2021 14:38:34 +
with message-id 
and subject line Bug#1001482: fixed in restrictedpython 4.0~b3-3
has caused the Debian Bug report #1001482,
regarding restrictedpython: (autopkgtest) needs update for python3.10: 
deprecation warning on stderr
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.)


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

Source: restrictedpython
Version: 4.0~b3-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of restrictedpython fails in testing when that autopkgtest is run with 
the binary packages of python3-defaults from unstable. It passes when 
run with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
restrictedpython   from testing4.0~b3-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. As mentioned 
in bug #909487 this test doesn't seem to be doing anything, and it can 
nevertheless fail. It's because there's a deprecation warning on stderr 
and autopkgtest fails on that by default. Unless a real test is added, I 
suggest to remove the autopkgtest.


Currently this regression is blocking the migration of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists 
what's new in Python3.10, it may help to identify what needs to be updated.


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

Paul

[0] https://bugs.debian.org/996584
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/r/restrictedpython/17446736/log.gz

:1: DeprecationWarning: The distutils package is deprecated and 
slated for removal in Python 3.12. Use setuptools or check PEP 632 for 
potential alternatives
:1: DeprecationWarning: The distutils.sysconfig module is 
deprecated, use sysconfig instead
Running tests for python3.10: /usr/bin/zope-testrunner3 -k --test-path 
/usr/lib/python3/dist-packages -s RestrictedPython

Total: 0 tests, 0 failures, 0 errors and 0 skipped in 0.000 seconds.
Running tests for python3.9: /usr/bin/zope-testrunner3 -k --test-path 
/usr/lib/python3/dist-packages -s RestrictedPython

Total: 0 tests, 0 failures, 0 errors and 0 skipped in 0.000 seconds.
autopkgtest [14:17:09]: test all



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: restrictedpython
Source-Version: 4.0~b3-3
Done: Christoph Berg 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 22 Dec 2021 13:59:13 +0100
Source: restrictedpython
Architecture: source
Version: 4.0~b3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Christoph Berg 
Closes: 909487 1001482
Changes:
 restrictedpython (4.0~b3-3) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Remove ancient X-Python3-Version field
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Debian Janitor ]
   * Use secure URI in Homepage field.
   * Bump debhelper from old 11 to 12.
 .
   [ Christoph Berg ]
   * d/tests: Use autodep8 test instead of the zope no-op one.
 (Closes: #909487, #1001482)
   * 

Bug#1002127: marked as pending in python-trie

[Håvard Flaget Aasen]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-trie/-/commit/92202ddc78ea795afafa877d5fe6a0c93fe33578


New upstream release supports Python 3.10. Closes: #1002127


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1002127

Processed: Bug#1002127 marked as pending in python-trie

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1002127 [src:python-trie] python-trie: FTBFS: dh_auto_test: error: pybuild 
--test -i python{version} -p "3.10 3.9" returned exit code 13
Added tag(s) pending.

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

Processed: tagging 1001528

[Debian Bug Tracking System]

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

> tags 1001528 + ftbfs
Bug #1001528 [src:purify] FTBFS with eigen3/3.4.0
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#1001482: marked as pending in restrictedpython

[Christoph Berg]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/restrictedpython/-/commit/7e76a5b22f34863ac88bdab3b0fb6f18e2694395


d/tests: Use autodep8 test instead of the zope no-op one. (Closes: #909487, 
#1001482)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1001482

Processed: Bug#1001482 marked as pending in restrictedpython

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1001482 [src:restrictedpython] restrictedpython: (autopkgtest) needs 
update for python3.10: deprecation warning on stderr
Added tag(s) pending.

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

Bug#1002418: [Pkg-privacy-maintainers] Bug#1002418: mat2: FTBFS: AssertionError: 'TransparentColor' not found in {}

[Georg Faerber]

Control: affects -1 libimage-exiftool-perl
Control: forwarded -1 https://0xacab.org/jvoisin/mat2/-/issues/162
--

Hi Lucas,

On 21-12-22 09:13:25, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

Thanks for reporting, the error is caused by libimage-exiftool-perl >=
12.37+dfsg-1.

I've forwarded this upstream.

Cheers,
Georg

Processed: Re: [Pkg-privacy-maintainers] Bug#1002418: mat2: FTBFS: AssertionError: 'TransparentColor' not found in {}

[Debian Bug Tracking System]

Processing control commands:

> affects -1 libimage-exiftool-perl
Bug #1002418 [src:mat2] mat2: FTBFS: AssertionError: 'TransparentColor' not 
found in {}
Added indication that 1002418 affects libimage-exiftool-perl
> forwarded -1 https://0xacab.org/jvoisin/mat2/-/issues/162
Bug #1002418 [src:mat2] mat2: FTBFS: AssertionError: 'TransparentColor' not 
found in {}
Set Bug forwarded-to-address to 'https://0xacab.org/jvoisin/mat2/-/issues/162'.

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

Bug#1002190: [Pkg-javascript-devel] Bug#1002190: Bug#1002190: gyp: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13

[joe]

I can take a look at this.--Joe
 Original message From: Yadd  Date: 12/22/21  
04:57  (GMT-05:00) To: 1002...@bugs.debian.org Subject: [Pkg-javascript-devel] 
Bug#1002190: Bug#1002190: gyp: FTBFS:
  dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9"
  returned exit code 13 Hi,is there someone with Python skills to fix that ?I 
think that this package should really own to Python Team, not JS 
Team.Cheers,YaddOn 21/12/2021 16:59, Lucas Nussbaum wrote:> Source: gyp> 
Version: 0.1+20210831gitd6c5dd5-1> Severity: serious> Justification: FTBFS> 
Tags: bookworm sid ftbfs> User: lu...@debian.org> Usertags: ftbfs-20211220 
ftbfs-bookworm> > Hi,> > During a rebuild of all packages in sid, your package 
failed to build> on amd64.> > > Relevant part (hopefully):>> make[1]: Entering 
directory '/<>'>> dh_auto_build>> I: pybuild base:237: 
/usr/bin/python3.10 setup.py build>> running build>> running build_py>> 
creating /<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/__init__.py -> /<>/.pybuild/cpython3_3.10/build/gyp>> 
copying pylib/gyp/xcode_ninja.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/simple_copy.py -> /<>/.pybuild/cpython3_3.10/build/gyp>> 
copying pylib/gyp/ninja_syntax.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/common_test.py -> /<>/.pybuild/cpython3_3.10/build/gyp>> 
copying pylib/gyp/win_tool.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying pylib/gyp/input.py 
-> /<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/MSVSProject.py -> /<>/.pybuild/cpython3_3.10/build/gyp>> 
copying pylib/gyp/xml_fix.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/MSVSUtil.py -> /<>/.pybuild/cpython3_3.10/build/gyp>> 
copying pylib/gyp/mac_tool.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/flock_tool.py -> /<>/.pybuild/cpython3_3.10/build/gyp>> 
copying pylib/gyp/xcodeproj_file.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/input_test.py -> /<>/.pybuild/cpython3_3.10/build/gyp>> 
copying pylib/gyp/easy_xml_test.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/msvs_emulation.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/xcode_emulation.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying pylib/gyp/common.py 
-> /<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/MSVSUserFile.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/easy_xml.py -> /<>/.pybuild/cpython3_3.10/build/gyp>> 
copying pylib/gyp/MSVSSettings.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/MSVSVersion.py -> /<>/.pybuild/cpython3_3.10/build/gyp>> 
copying pylib/gyp/MSVSToolFile.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/MSVSSettings_test.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp>> copying 
pylib/gyp/MSVSNew.py -> /<>/.pybuild/cpython3_3.10/build/gyp>> 
creating /<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/__init__.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/xcode_test.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/msvs_test.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/msvs.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/ninja_test.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/gypsh.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/analyzer.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/xcode.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/make.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/gypd.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/dump_dependency_json.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/eclipse.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/ninja.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> copying 
pylib/gyp/generator/cmake.py -> 
/<>/.pybuild/cpython3_3.10/build/gyp/generator>> I: pybuild 
base:237: /usr/bin/python3 setup.py build>> running build>> running build_py>> 
creating /<>/.pybuild/cpython3_3.9/build/gyp>> copying 
pylib/gyp/__init__.py -> /<>/.pybuild/cpython3_3.9/build/gyp>> 
copying pylib/gyp/xcode_ninja.py -> 
/<>/.pybuild/cpython3_3.9/build/gyp>> copying 
pylib/gyp/simple_copy.py -> /<>/.pybuild/cpython3_3.9/build/gyp>> 
copying pylib/gyp/ninja_syntax.py -> 
/<>/.pybuild/cpython3_3.9/build/gyp>> copying 
pylib/gyp/common_test.py -> /<>/.pybuild/cpython3_3.9/build/gyp>> 
copying pylib/gyp/win_tool.py -> 
/<>/.pybuild/cpython3_3.9/build/gyp>> copying pylib/gyp/input.py 
-> /<>/.pybuild/cpython3_3.9/build/gyp>> copying 
pylib/gyp/MSVSProject.py -> /<>/.pybuild/cpython3_3.9/build/gyp>> 
copying 

Processed: forward

[Debian Bug Tracking System]

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

> forwarded 1002398 https://github.com/arskom/spyne/issues/676
Bug #1002398 [src:spyne] spyne: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
Set Bug forwarded-to-address to 'https://github.com/arskom/spyne/issues/676'.
> tags 1002398 upstream
Bug #1002398 [src:spyne] spyne: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
Added tag(s) upstream.
>
End of message, stopping processing here.

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