Bug#965491: dictconv: diff for NMU version 0.2-7.1

2022-01-19 Thread Francesco Namuri

Hello Adrian,
thank you so much.

Francesco

---
.''`. Francesco Namuri
: :' : https://hal.hierax.net/
`. `' «Dave, my mind is going. I can feel it. I'm a ...fraid.»
  `- 4096R/260F0067 - 320D D86E 1E25 6275 B28F  89D7 29CE ADC9 260F 0067

Il 19/01/2022 15:26 Adrian Bunk ha scritto:

Control: tags 581630 + patch
Control: tags 581630 + pending
Control: tags 965491 + patch
Control: tags 965491 + pending

Dear maintainer,

I've prepared an NMU for dictconv (versioned as 0.2-7.1) and uploaded
it to DELAYED/7. Please feel free to tell me if I should cancel it.

cu
Adrian




Bug#1004041: marked as done (gwcs FTBFS)

2022-01-19 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jan 2022 07:18:43 +
with message-id 
and subject line Bug#1004041: fixed in gwcs 0.18.0-2
has caused the Debian Bug report #1004041,
regarding gwcs FTBFS
to be marked as done.

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

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


-- 
1004041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gwcs
Version: 0.18.0-1
Severity: serious
Tags: ftbfs
Control: block 1001238 by -1

https://buildd.debian.org/status/fetch.php?pkg=gwcs=all=0.18.0-1=1642613373=0

...
 ERRORS 
_ ERROR collecting .pybuild/cpython3_3.9_gwcs/build/gwcs/extension.py __
gwcs/extension.py:8: in 
from .converters.selector import (
gwcs/converters/selector.py:11: in 
from asdf_astropy.converters.transform.core import TransformConverterBase
E   ModuleNotFoundError: No module named 'asdf_astropy'
_ ERROR collecting .pybuild/cpython3_3.9_gwcs/build/gwcs/converters/geometry.py 
_
gwcs/converters/geometry.py:5: in 
from asdf_astropy.converters.transform.core import TransformConverterBase
E   ModuleNotFoundError: No module named 'asdf_astropy'
_ ERROR collecting .pybuild/cpython3_3.9_gwcs/build/gwcs/converters/selector.py 
_
gwcs/converters/selector.py:11: in 
from asdf_astropy.converters.transform.core import TransformConverterBase
E   ModuleNotFoundError: No module named 'asdf_astropy'
_ ERROR collecting 
.pybuild/cpython3_3.9_gwcs/build/gwcs/converters/spectroscopy.py _
gwcs/converters/spectroscopy.py:6: in 
from asdf_astropy.converters.transform.core import (
E   ModuleNotFoundError: No module named 'asdf_astropy'
_ ERROR collecting 
.pybuild/cpython3_3.9_gwcs/build/gwcs/converters/tests/test_transforms.py _
gwcs/converters/tests/test_transforms.py:7: in 
from asdf_astropy.converters.transform.tests.test_transform import (
E   ModuleNotFoundError: No module named 'asdf_astropy'
_ ERROR collecting 
.pybuild/cpython3_3.9_gwcs/build/gwcs/converters/tests/test_transforms.py _
ImportError while importing test module 
'/<>/.pybuild/cpython3_3.9_gwcs/build/gwcs/converters/tests/test_transforms.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.9/importlib/__init__.py:127: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
gwcs/converters/tests/test_transforms.py:7: in 
from asdf_astropy.converters.transform.tests.test_transform import (
E   ModuleNotFoundError: No module named 'asdf_astropy'
_ ERROR collecting 
.pybuild/cpython3_3.9_gwcs/build/gwcs/converters/tests/test_wcs.py _
gwcs/converters/tests/test_wcs.py:15: in 
from asdf_astropy.converters.transform.tests.test_transform import (  # 
noqa: E402
E   ModuleNotFoundError: No module named 'asdf_astropy'
_ ERROR collecting 
.pybuild/cpython3_3.9_gwcs/build/gwcs/converters/tests/test_wcs.py _
ImportError while importing test module 
'/<>/.pybuild/cpython3_3.9_gwcs/build/gwcs/converters/tests/test_wcs.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.9/importlib/__init__.py:127: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
gwcs/converters/tests/test_wcs.py:15: in 
from asdf_astropy.converters.transform.tests.test_transform import (  # 
noqa: E402
E   ModuleNotFoundError: No module named 'asdf_astropy'
_ ERROR collecting .pybuild/cpython3_3.9_gwcs/build/gwcs/tests/test_geometry.py 
_
gwcs/tests/test_geometry.py:10: in 
from asdf_astropy.converters.transform.tests.test_transform import (
E   ModuleNotFoundError: No module named 'asdf_astropy'
_ ERROR collecting .pybuild/cpython3_3.9_gwcs/build/gwcs/tests/test_geometry.py 
_
ImportError while importing test module 
'/<>/.pybuild/cpython3_3.9_gwcs/build/gwcs/tests/test_geometry.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.9/importlib/__init__.py:127: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
gwcs/tests/test_geometry.py:10: in 
from asdf_astropy.converters.transform.tests.test_transform import (
E   ModuleNotFoundError: No module named 'asdf_astropy'
=== warnings summary ===
../../../../../../usr/lib/python3/dist-packages/astropy/wcs/wcsapi/sliced_low_level_wcs.py:6
  /usr/lib/python3/dist-packages/astropy/wcs/wcsapi/sliced_low_level_wcs.py:6: 
AstropyDeprecationWarning: SlicedLowLevelWCS has been moved to 

Processed: Fix forwarded address

2022-01-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> notforwarded 1002369
Bug #1002369 [src:piglit] piglit: FTBFS: AttributeError: module 'collections' 
has no attribute 'MutableMapping'
Unset Bug forwarded-to-address
> forwarded 1002369 
> https://gitlab.freedesktop.org/mesa/piglit/-/commit/a37fd8bcf7b1673c93
Bug #1002369 [src:piglit] piglit: FTBFS: AttributeError: module 'collections' 
has no attribute 'MutableMapping'
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/mesa/piglit/-/commit/a37fd8bcf7b1673c93'.
> --
Stopping processing here.

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



Processed: #1002369: forward to upstream fix

2022-01-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 1002369 https://gitlab.freedesktop.org/mesa/piglit/-/commit/a37fd8
Bug #1002369 [src:piglit] piglit: FTBFS: AttributeError: module 'collections' 
has no attribute 'MutableMapping'
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/mesa/piglit/-/commit/a37fd8'.
> --
Stopping processing here.

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



Bug#1004052: marked as done (ledit FTBFS with OCaml 4.13.1)

2022-01-19 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jan 2022 05:34:11 +
with message-id 
and subject line Bug#1004052: fixed in ledit 2.04-6
has caused the Debian Bug report #1004052,
regarding ledit FTBFS with OCaml 4.13.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.)


-- 
1004052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004052
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ledit
Version: 2.04-5
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/logs.php?pkg=ledit=2.04-5%2Bb2

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
/usr/bin/make CUSTOM=
make[2]: Entering directory '/<>'
camlp5r -I ext -loc loc ext/pa_def.ml -o ext/pa_def.ppo
ocamlc -I `camlp5 -where` -c -impl ext/pa_def.ppo
File "ext/pa_def.ml", line 36, characters 55-58:
36 | let pel = List.map (fun (p, e) -> (p, loop e)) pel in
^^^
Error: This expression has type
 (MLast.patt * MLast.expr * MLast.attributes) list
   but an expression was expected of type ('a * MLast.expr) list
   Type MLast.patt * MLast.expr * MLast.attributes
   is not compatible with type 'a * MLast.expr 
make[2]: *** [Makefile:69: ext/pa_def.cmo] Error 2
--- End Message ---
--- Begin Message ---
Source: ledit
Source-Version: 2.04-6
Done: Stéphane Glondu 

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

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

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

Debian distribution maintenance software
pp.
Stéphane Glondu  (supplier of updated ledit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 20 Jan 2022 06:07:28 +0100
Source: ledit
Architecture: source
Version: 2.04-6
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Closes: 1004052
Changes:
 ledit (2.04-6) unstable; urgency=medium
 .
   * Fix compilation with camlp5 8.00.02 (Closes: #1004052)
   * Bump Standards-Version to 4.6.0
Checksums-Sha1:
 7210b098bdfa99a89579a332841e959966c9df2a 1845 ledit_2.04-6.dsc
 4e437b17f235ff3afd20fe1ac8c52e0ecbf40858 7064 ledit_2.04-6.debian.tar.xz
Checksums-Sha256:
 5ba1d10cfd64944fbe0889981d702e84002ee0b1b3dd1e10d444c6620b722233 1845 
ledit_2.04-6.dsc
 ac3e62acb195a0911bd4a89dc73e8be8f60236306b4707f5e4a10425204dedbc 7064 
ledit_2.04-6.debian.tar.xz
Files:
 abb46291e5c7f4e4438180447eb35ec8 1845 editors optional ledit_2.04-6.dsc
 9515a10bcc0a099904582a95035cfe7c 7064 editors optional 
ledit_2.04-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmHo7zASHGdsb25kdUBk
ZWJpYW4ub3JnAAoJECG47vGxiTCBwPcH/i3WI7TaXHGwVD0U1E1j0dXZ8eeuYIeM
D0Fs6C1b5MeKItm33/HGvUWsF2d7CT9hUo7HzPHTMrGrVlcKd8LurB0fhLWTjBbe
raP3gHKKYL59rS3ywcnuMsKGYagQsd/LEMS1nPQ2OqZDotxBc33S5amz3XVIpqj0
XpnNLjU8JbSgu7zGpm8u3TmyhMQdlkkJ2jcKYvH2Yr4vUUoH4ZYfCiuqNAMhqqPp
d07VwcfYnoUQzbiHfYx+s0XnkgrM6ujBr9amWTfd1Q0mDBJLEjAMEX4E1QyxKEsw
HhyodPFUwvo6WzgvS94BKVawGYTB6emdgqKd20s+Xoo80Wc8Gw3zmt4=
=OUV9
-END PGP SIGNATURE End Message ---


Bug#1004060: systemd: breaks lightdm / lightdm-gtk-greeter

2022-01-19 Thread Vincent Lefevre
On 2022-01-20 05:08:53 +0100, Vincent Lefevre wrote:
> I've attached the logs from lightdm, but they may not really be useful.

There seem to be no additional messages compared to when it is working.

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



Bug#1004019: marked as done (Should forensics-extra drop the dependendency on smb-nat?)

2022-01-19 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jan 2022 04:18:43 +
with message-id 
and subject line Bug#1004019: fixed in forensics-extra 2.35
has caused the Debian Bug report #1004019,
regarding Should forensics-extra drop the dependendency on smb-nat?
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.)


-- 
1004019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: forensics-extra
Version: 2.34
Severity: serious
Control: block 1004018 by -1

Does the 25 year old smb-nat provide any functionality that is
not also provided by Samba tools (that were originally written
by the same author)?
--- End Message ---
--- Begin Message ---
Source: forensics-extra
Source-Version: 2.35
Done: Joao Eriberto Mota Filho 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 20 Jan 2022 00:26:18 -0300
Source: forensics-extra
Architecture: source
Version: 2.35
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Joao Eriberto Mota Filho 
Closes: 1004019
Changes:
 forensics-extra (2.35) unstable; urgency=medium
 .
   * excluded-packages: added smb-nat. (See #1004019)
   * list-of-packages-extra: removed smb-nat. Thanks to Adrian
 Bunk . (Closes: #1004019)
   * debian/control: updated.
   * debian/forensics-extra.README.Debian: updated.
Checksums-Sha1:
 fb7d6757dda03a1d7e1086d659cfd0e07b311b9e 1888 forensics-extra_2.35.dsc
 52cfdd4dba7ccaacefd0f7e1760440d9823b1a50 23152 forensics-extra_2.35.tar.xz
 9be85fe4586c4680b4e2ebe49facc67fb1b0f100 5531 
forensics-extra_2.35_source.buildinfo
Checksums-Sha256:
 84e754a038c40f55a51d341cc10997bdb9ebc3b58599d783ff575653e9f73d11 1888 
forensics-extra_2.35.dsc
 a2649c5c959681842bb7a6aa1e25d9dd6b437bd46b8094daec5f99ce2bc75a57 23152 
forensics-extra_2.35.tar.xz
 a2e27b0210eb08bbb008627f7beab2751adf2cc3eb42c24e22bc4ebe68152634 5531 
forensics-extra_2.35_source.buildinfo
Files:
 f743482b24247f85ef4b44ae87e674b8 1888 metapackages optional 
forensics-extra_2.35.dsc
 bbcb7ca4ae1f6e5f3ab357d8121daca9 23152 metapackages optional 
forensics-extra_2.35.tar.xz
 7b810cd38b53d7d51b8c95a18a8ee2c4 5531 metapackages optional 
forensics-extra_2.35_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmHo33kACgkQ3mO5xwTr
6e8opxAAl7kpwNQy7pbOdWogrC4NwTXK17weuWkPYCqDT2tkFm8CTLfyMEE4XVio
f5jpOt1vR/6fBn9WPLt40maAt7efFtk24x89n37dETsYIBY4+WQKjpaNUwwhOKQp
EMJ69haYXc3zkK2PiFgvuzv1kc22hOStAiyHSL2nushkSsArI+mi0ifPlWadR60N
KYNrKQTGgmVERzLHX41U+OXq6XV/tLRUxVad+X9bprc3aGjh/WPr+1H3Gp1RRRZm
1IHsVaUzdEDGXxV8wTwvJAdR02hSVekeruHeH+GyLP71FCgmkiPTuUgDN7CvgiU1
DgJe+9GMEOoVRpctCNq+4Xl8NZPvOriFEZHXYEtuwkaZW3HTomwX0w6qh+GV+TxX
6rW5IVwR1Lm+64flx9w80aN5KPBOhSXUge4kV4JTIV4EESX1P5tnKRZdoouS2ejr
0Vx8B3bpcMQqrFkCjY4VQQyqH8fhQ4+PCQF03F7DA3FUvF/Dh8AcffyO1EFzcjyn
u0FGM8ogBumyxKq0L4nr9FMKhbNoqIVuruPPeL84d8MqTfahXPm9cnPFtdZ5B1pe
zfs0X1w5AbCge9aA0sT3EC1kaWNknVTLsiF+oXjopqA8kIKEpkwQflHMQPlihmQp
MDYDcsPaY7W/uTm78aBtXAc6jwL0/S8vl+XIoNRS/JPaBjSq3cc=
=Up67
-END PGP SIGNATURE End Message ---


Bug#1004019: Should forensics-extra drop the dependendency on smb-nat?

2022-01-19 Thread Eriberto
Em qua., 19 de jan. de 2022 às 09:48, Adrian Bunk  escreveu:
>
> Package: forensics-extra
> Version: 2.34
> Severity: serious
> Control: block 1004018 by -1
>
> Does the 25 year old smb-nat provide any functionality that is
> not also provided by Samba tools (that were originally written
> by the same author)?
>

Hi Adrian,

Thanks for your tip. I will remove this package from forensics-extra.

Cheers,

Eriberto



Bug#670860: marked as done ([PATCH] spell: Helping to update to packaging format 3.0)

2022-01-19 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jan 2022 02:35:38 +
with message-id 
and subject line Bug#670860: fixed in spell 1.0-24.2
has caused the Debian Bug report #670860,
regarding [PATCH] spell: Helping to update to packaging format 3.0
to be marked as done.

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

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


-- 
670860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: spell
Severity: wishlist
Tags: patch

Hi,

The dpatch patch management system has been deprecated for some time. The
Lintian currently flags use of dpatch packages as an error. The new 3.0
packaging format is an improved version which, among other things, contains
patch management built-in. For more information, see:

http://wiki.debian.org/Projects/DebSrc3.0

I had some free time; see attached patch to migrate to new package
format. Note that all files in debian/patches/* are canocalized to
*.patch.

Let me know if there is anything that needs adjusting or if it is ok
to upload this version in a NMU in case you are working on other
issues needing attention.

Thanks,
Jari

>From bd882b2a77ab8f86ef7d6c58b74befd46a0cfdb3 Mon Sep 17 00:00:00 2001
From: Jari Aalto 
Date: Sun, 29 Apr 2012 21:35:20 +0300
Subject: [PATCH] format-3.0
Organization: Private
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Signed-off-by: Jari Aalto 
---
 debian/changelog |   10 ++
 debian/compat|2 +-
 debian/control   |6 +++---
 debian/patches/00list|1 -
 ...conglomeration.dpatch => 20-conglomeration.patch} |7 ++-
 debian/patches/series|1 +
 debian/rules |9 ++---
 debian/source/format |1 +
 spell.c  |   18 ++
 9 files changed, 26 insertions(+), 29 deletions(-)
 delete mode 100644 debian/patches/00list
 rename debian/patches/{01-conglomeration.dpatch => 20-conglomeration.patch} (99%)
 create mode 100644 debian/patches/series
 create mode 100644 debian/source/format

diff --git a/debian/changelog b/debian/changelog
index 406af1e..b6cc1c0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+spell (1.0-24.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Remove deprecated dpatch and upgrade to packaging format "3.0 quilt".
+  * Update to Standards-Version to 3.9.3 and debhelper to 9.
+  * Add required build-arch and build-indep targets to rules file.
+  * Fix missing-dependency-on-install-info (Lintian).
+
+ -- Jari Aalto   Sun, 29 Apr 2012 21:04:58 +0300
+
 spell (1.0-24) unstable; urgency=low
 
   * Support also aspell (Closes: #381511)
diff --git a/debian/compat b/debian/compat
index 7f8f011..ec63514 100644
--- a/debian/compat
+++ b/debian/compat
@@ -1 +1 @@
-7
+9
diff --git a/debian/control b/debian/control
index 55d5542..0530d5a 100644
--- a/debian/control
+++ b/debian/control
@@ -2,14 +2,14 @@ Source: spell
 Section: text
 Priority: optional
 Maintainer: Giacomo Catenazzi 
-Build-Depends: debhelper (>= 7), dpatch, texinfo
-Standards-Version: 3.8.2
+Build-Depends: debhelper (>= 9), texinfo
+Standards-Version: 3.9.3
 Homepage: http://directory.fsf.org/project/spell/
 
 Package: spell
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, ispell | aspell,
- iamerican | ibritish | ispell-dictionary
+ iamerican | ibritish | ispell-dictionary, install-info
 Description: GNU Spell, a clone of Unix `spell'
  GNU Spell is a spell checking program which prints each misspelled word on a
  line of its own. It is designed as a clone of the standard Unix `spell'
diff --git a/debian/patches/00list b/debian/patches/00list
deleted file mode 100644
index 4926043..000
--- a/debian/patches/00list
+++ /dev/null
@@ -1 +0,0 @@
-01-conglomeration.dpatch
diff --git a/debian/patches/01-conglomeration.dpatch b/debian/patches/20-conglomeration.patch
similarity index 99%
rename from debian/patches/01-conglomeration.dpatch
rename to debian/patches/20-conglomeration.patch
index 3461269..aa482b0 100644
--- a/debian/patches/01-conglomeration.dpatch
+++ b/debian/patches/20-conglomeration.patch
@@ -1,9 +1,6 @@
-#!/bin/sh /usr/share/dpatch/dpatch-run
-## 01-conglomeration.dpatch
-##
-## DP: Needs to be broken out (FIXME).
+From: Unknown
+Subject: Needs to be broken out (FIXME).
 
-@DPATCH@
 
 diff -Naur spell-1.0.orig/spell.c 

Bug#1003962: marked as done (Fails with --buildsystem=cmake if builddirectory contains package version with ~ tilde)

2022-01-19 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jan 2022 01:48:48 +
with message-id 
and subject line Bug#1003962: fixed in dh-python 5.20220119
has caused the Debian Bug report #1003962,
regarding Fails with --buildsystem=cmake if builddirectory contains package 
version with ~ tilde
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.)


-- 
1003962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003962
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dh-python
Version: 5.20220101
Severity: serious
Affects: pynest2s

pynest2s 4.13~beta-1 ftbfses on all architectures:
https://buildd.debian.org/status/package.php?p=pynest2d

The reason is that pybuild "'double quotes'" the --builddirectory
argument, making it a relative path since it doesn't start with /.
Note how PKGBUILDDIR is duplicated:

dh build-arch --buildsystem=pybuild --with python3 --with sip3
   dh_update_autotools_config -a -O--buildsystem=pybuild
   dh_autoreconf -a -O--buildsystem=pybuild
   dh_auto_configure -a -O--buildsystem=pybuild
I: pybuild base:237: dh_auto_configure --buildsystem=cmake 
--builddirectory="'/<>/.pybuild/cpython3_3.10/build'" -- [...]
...
   dh_auto_build -a -O--buildsystem=pybuild
I: pybuild base:237: dh_auto_build --buildsystem=cmake 
--builddirectory="'/<>/.pybuild/cpython3_3.10/build'" --
cd '/<>/pynest2d-4.13\~beta/.pybuild/cpython3_3.10/build' && 
make -j4 "INSTALL=install --strip-program=true" VERBOSE=1
make[1]: Entering directory 
'/<>/'/<>/.pybuild/cpython3_3.10/build''
(For whatever reason make is still happy with the borked path at that point...)
...
/usr/bin/cmake -E touch 
/<>/'/<>/.pybuild/cpython3_3.10/build'/src/sippynest2dpart0.cpp
 [...]
cmake -E touch: failed to update 
"/<>//<>/.pybuild/cpython3_3.10/build/src/sippynest2dpart0.cpp".


I suspect the error is in /usr/share/dh-python/dhpython/build/plugin_cmake.py:

return ('dh_auto_build --buildsystem=cmake'
' --builddirectory="{build_dir}"'

If I replace "{build_dir}" by {build_dir} in that file, the build
succeeds.

Christoph
--- End Message ---
--- Begin Message ---
Source: dh-python
Source-Version: 5.20220119
Done: Stefano Rivera 

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated dh-python package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Jan 2022 21:06:38 -0400
Source: dh-python
Architecture: source
Version: 5.20220119
Distribution: unstable
Urgency: medium
Maintainer: Piotr Ożarowski 
Changed-By: Stefano Rivera 
Closes: 1003962
Changes:
 dh-python (5.20220119) unstable; urgency=medium
 .
   * Allow passing arguments to tox tests.
   * cmake plugin: Don't quote arguments that will be substituted (and quoted)
 by shell_command. (closes: 1003962)
Checksums-Sha1:
 a1079038e4e4fec23c855a8bf8ada189603c5a01 1552 dh-python_5.20220119.dsc
 157a0e212d3d406051f43697915e42611584feca 112016 dh-python_5.20220119.tar.xz
 148aa889ba9b87b222762b05d5540785e7e84591 6434 
dh-python_5.20220119_source.buildinfo
Checksums-Sha256:
 2591978a708c4d6a0ed82eab93e368b9de4ea9d92fa6b682a652f131ed52868e 1552 
dh-python_5.20220119.dsc
 ddd5549e705b0f39f4fad8a7816a24033a8b336896bc25b5be5c41cc2aca9391 112016 
dh-python_5.20220119.tar.xz
 5a77aa16e2743988747ad6ae021b4fb5c3497d83c989d4b277a3789cd60839a4 6434 
dh-python_5.20220119_source.buildinfo
Files:
 8e2408de2451dcc92574611e88d3519d 1552 python optional dh-python_5.20220119.dsc
 f952ce322a3e0edb8d507a18e1ffa571 112016 python optional 
dh-python_5.20220119.tar.xz
 52bf55275a716fd67b6a9ab13ab35b5d 6434 python optional 
dh-python_5.20220119_source.buildinfo

-BEGIN PGP SIGNATURE-

iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCYei7/hQcc3RlZmFub3JA
ZGViaWFuLm9yZwAKCRBHew2wJjpU2BzFAP4//e2G+esQO6O5Mqk68R77sOhxnWhY
H+kmBymjAtuW6gD/XYzKW0VgGQgXImZc4zWRfwhAJ8lMV7uxbYLogTduqQQ=
=y4wC
-END PGP SIGNATURE End Message ---


Processed: your mail

2022-01-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 983966 patch
Bug #983966 [src:android-platform-system-core] android-platform-system-core: 
ftbfs with GCC-11
Added tag(s) patch.
> thanks
Stopping processing here.

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



Processed: tagging 1003896, found 965439 in 2.24~ti+exp0, tagging 1004026

2022-01-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 1003896 + sid bookworm
Bug #1003896 {Done: gregor herrmann } 
[src:libclass-dbi-plugin-type-perl] FTBFS: t/1.t: Failed 2/6 subtests
Added tag(s) sid and bookworm.
> found 965439 2.24~ti+exp0
Bug #965439 [src:binutils-msp430] binutils-msp430: Removal of obsolete 
debhelper compat 5 and 6 in bookworm
Marked as found in versions binutils-msp430/2.24~ti+exp0.
> tags 1004026 + sid bookworm
Bug #1004026 [covered] covered: gplcver support should be dropped or gplcver 
adopted by the Electronics Team
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

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



Bug#1004052: ledit FTBFS with OCaml 4.13.1

2022-01-19 Thread Adrian Bunk
Source: ledit
Version: 2.04-5
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/logs.php?pkg=ledit=2.04-5%2Bb2

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
/usr/bin/make CUSTOM=
make[2]: Entering directory '/<>'
camlp5r -I ext -loc loc ext/pa_def.ml -o ext/pa_def.ppo
ocamlc -I `camlp5 -where` -c -impl ext/pa_def.ppo
File "ext/pa_def.ml", line 36, characters 55-58:
36 | let pel = List.map (fun (p, e) -> (p, loop e)) pel in
^^^
Error: This expression has type
 (MLast.patt * MLast.expr * MLast.attributes) list
   but an expression was expected of type ('a * MLast.expr) list
   Type MLast.patt * MLast.expr * MLast.attributes
   is not compatible with type 'a * MLast.expr 
make[2]: *** [Makefile:69: ext/pa_def.cmo] Error 2



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

2022-01-19 Thread Aurelien Jarno
Hi,

On 2022-01-19 22:08, John Paul Adrian Glaubitz wrote:
> Hi Aurelien!
> 
> Unfortunately, glibc no longer builds with this change on powerpc and ppc64
> and kernel builds still fails on both targets:
> 
> > https://buildd.debian.org/status/fetch.php?pkg=glibc=powerpc=2.33-3=1642542048=0
> > https://buildd.debian.org/status/fetch.php?pkg=glibc=ppc64=2.33-3=1642542055=0

The ppc64el fix is not the cause for those failures. Previous glibc
versions also do not build on powerpc and ppc64 following the binutils
snapshot upload to sid. It's just that more code got broken on powerpc
and ppc64 than on ppc64el. I have queued the backported fixes from
upstream for the next upload.

> > https://buildd.debian.org/status/fetch.php?pkg=linux=powerpc=5.15.15-1=1642579068=0
> > https://buildd.debian.org/status/fetch.php?pkg=linux=ppc64=5.15.15-1=1642578946=0

Those failures are completely unrelated to do with glibc. A porter need
to fix the kernel code to make it compatible with the new binutils.

Cheers
Aurelien

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



Bug#1002063: marked as done (libvtk9.1: missing Breaks+Replaces: libvtk9 (<< 9.1.0+really9.1.0))

2022-01-19 Thread Debian Bug Tracking System
Your message dated Wed, 19 Jan 2022 22:13:22 +
with message-id 
and subject line Bug#1002063: fixed in vtk9 9.1.0+really9.1.0+dfsg2-3~exp2
has caused the Debian Bug report #1002063,
regarding libvtk9.1: missing Breaks+Replaces: libvtk9 (<< 9.1.0+really9.1.0)
to be marked as done.

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

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


-- 
1002063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvtk9.1
Version: 9.1.0+really9.1.0+dfsg2-3~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../libvtk9.1_9.1.0+really9.1.0+dfsg2-3~exp1_amd64.deb ...
  Unpacking libvtk9.1:amd64 (9.1.0+really9.1.0+dfsg2-3~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libvtk9.1_9.1.0+really9.1.0+dfsg2-3~exp1_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/vtk/hierarchy/VTK/vtkChartsCore-hierarchy.txt', 
which is also in package libvtk9:amd64 9.1.0+really9.0.3+dfsg1-4+b1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libvtk9.1_9.1.0+really9.1.0+dfsg2-3~exp1_amd64.deb

There are a lot of conflicting files:
/usr/lib//vtk/hierarchy/VTK/vtk*.txt

cheers,

Andreas


libvtk9=9.1.0+really9.0.3+dfsg1-4+b1_libvtk9.1=9.1.0+really9.1.0+dfsg2-3~exp1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: vtk9
Source-Version: 9.1.0+really9.1.0+dfsg2-3~exp2
Done: Anton Gladky 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Jan 2022 22:40:05 +0100
Source: vtk9
Architecture: source
Version: 9.1.0+really9.1.0+dfsg2-3~exp2
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Anton Gladky 
Closes: 1002063
Changes:
 vtk9 (9.1.0+really9.1.0+dfsg2-3~exp2) experimental; urgency=medium
 .
   [ Adrian Bunk ]
   * [33b75d5] Restore the 83_allow_gles_platforms.patch hack for Qt with 
OpenGL ES
   * [b243b24] HACK: vtkQWidgetTexture.cxx: Don't use vtkOpenGLCheckErrorMacro
 .
   [ Anton Gladky ]
   * [4449d7a] Add missing Breaks+Replaces to libvtk9. (Closes: #1002063)
Checksums-Sha1:
 098a3317fd9c2665d86273d0e83a5fd73ea8affa 3853 
vtk9_9.1.0+really9.1.0+dfsg2-3~exp2.dsc
 62953793d0c0e06803289aa4e8279c7f07b23000 19932 
vtk9_9.1.0+really9.1.0+dfsg2-3~exp2.debian.tar.xz
 980b29c6a65d75473e23f1b2c802e3b3eab53303 27989 
vtk9_9.1.0+really9.1.0+dfsg2-3~exp2_source.buildinfo
Checksums-Sha256:
 5a60c97c1e90abbe8bed5e68cafdfb423b591b8eb819ebe478ad072f5fc1e168 3853 
vtk9_9.1.0+really9.1.0+dfsg2-3~exp2.dsc
 716703624fa7295226b8c2c9813adc2a4d443e4b94bc71d73df0bae6ca4a 19932 
vtk9_9.1.0+really9.1.0+dfsg2-3~exp2.debian.tar.xz
 9a4450f6217d69a0ccf666d57a729b73c088189721f0f7fb7610aeaf3f407a85 27989 
vtk9_9.1.0+really9.1.0+dfsg2-3~exp2_source.buildinfo
Files:
 aa47fb93167c76b4c0821fa02934184d 3853 graphics optional 
vtk9_9.1.0+really9.1.0+dfsg2-3~exp2.dsc
 3c6550857d57824094855abf4e3d76ac 19932 graphics optional 
vtk9_9.1.0+really9.1.0+dfsg2-3~exp2.debian.tar.xz
 3b57e2c09e6995c4dccd2904ea16f9e8 27989 graphics optional 
vtk9_9.1.0+really9.1.0+dfsg2-3~exp2_source.buildinfo

-BEGIN PGP SIGNATURE-


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

2022-01-19 Thread John Paul Adrian Glaubitz
Hello!

On 1/19/22 22:38, Jeffrey Walton wrote:
> On Wed, Jan 19, 2022 at 4:08 PM John Paul Adrian Glaubitz
>  wrote:
>>
>> Unfortunately, glibc no longer builds with this change on powerpc and ppc64
>> and kernel builds still fails on both targets:
>>
>>> https://buildd.debian.org/status/fetch.php?pkg=glibc=powerpc=2.33-3=1642542048=0
>>> https://buildd.debian.org/status/fetch.php?pkg=glibc=ppc64=2.33-3=1642542055=0
>>
>>> https://buildd.debian.org/status/fetch.php?pkg=linux=powerpc=5.15.15-1=1642579068=0
>>> https://buildd.debian.org/status/fetch.php?pkg=linux=ppc64=5.15.15-1=1642578946=0
> 
> This seems to be related to the ones stamped 1642542048 and 1642542055
> (the first two):
> https://patchwork.sourceware.org/project/glibc/patch/20210925202746.819385-1...@us.ibm.com/

It will be fixed in glibc_2.33-4 [1] which has not been released yet.

Adrian

> [1] 
> https://salsa.debian.org/glibc-team/glibc/-/commit/20e02061f900515ebac6ee3872c5cd22ea5801d2

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



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

2022-01-19 Thread Jeffrey Walton
On Wed, Jan 19, 2022 at 4:08 PM John Paul Adrian Glaubitz
 wrote:
>
> Unfortunately, glibc no longer builds with this change on powerpc and ppc64
> and kernel builds still fails on both targets:
>
> > https://buildd.debian.org/status/fetch.php?pkg=glibc=powerpc=2.33-3=1642542048=0
> > https://buildd.debian.org/status/fetch.php?pkg=glibc=ppc64=2.33-3=1642542055=0
>
> > https://buildd.debian.org/status/fetch.php?pkg=linux=powerpc=5.15.15-1=1642579068=0
> > https://buildd.debian.org/status/fetch.php?pkg=linux=ppc64=5.15.15-1=1642578946=0

This seems to be related to the ones stamped 1642542048 and 1642542055
(the first two):
https://patchwork.sourceware.org/project/glibc/patch/20210925202746.819385-1...@us.ibm.com/



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

2022-01-19 Thread Paul Gevers

Source: golang-github-komkom-toml
Version: 0.0~git20211215.3c8ee9d-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of golang-github-komkom-toml the autopkgtest of 
golang-github-komkom-toml fails in testing when that autopkgtest is run 
with the binary packages of golang-github-komkom-toml from unstable on 
armhf and i386. It passes when run with only packages from testing. In 
tabular form:


  passfail
golang-github-komkom-toml from testing0.0~git20211215.3c8ee9d-1
all othersfrom testingfrom testing

I copied some of the output at the bottom of this report. Seems like a 
32 bit issue where some value overflows.


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


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

Paul

[1] https://qa.debian.org/excuses.php?package=golang-github-komkom-toml

https://ci.debian.net/data/autopkgtest/testing/armhf/g/golang-github-komkom-toml/18432554/log.gz

[info] Testing github.com/komkom/toml...
[info] Source code installed by binary package, overriding 
dh_auto_configure...

dh build --builddirectory=_build --buildsystem=golang --with=golang
   dh_update_autotools_config -O--builddirectory=_build 
-O--buildsystem=golang

   dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang
   debian/rules override_dh_auto_configure
make[1]: Entering directory 
'/tmp/autopkgtest-lxc.qwkbqa0f/downtmp/autopkgtest_tmp'

mkdir -p "_build"
cp -a /usr/share/gocode/src "_build"
make[1]: Leaving directory 
'/tmp/autopkgtest-lxc.qwkbqa0f/downtmp/autopkgtest_tmp'

   dh_auto_build -O--builddirectory=_build -O--buildsystem=golang
	cd _build && go install -trimpath -v -p 160 github.com/komkom/toml 
github.com/komkom/toml/internal

unicode/utf8
internal/unsafeheader
internal/goexperiment
math/bits
runtime/internal/sys
internal/itoa
internal/race
internal/abi
internal/cpu
sync/atomic
unicode
runtime/internal/math
math
runtime/internal/atomic
internal/bytealg
runtime
internal/reflectlite
sync
internal/testlog
errors
sort
internal/oserror
path
io
strconv
syscall
bytes
strings
reflect
internal/syscall/execenv
internal/syscall/unix
time
io/fs
internal/poll
internal/fmtsort
os
fmt
github.com/pkg/errors
github.com/komkom/toml/internal
github.com/komkom/toml
   dh_auto_test -O--builddirectory=_build -O--buildsystem=golang
	cd _build && go test -vet=off -v -p 160 github.com/komkom/toml 
github.com/komkom/toml/internal

=== RUN   TestReader
reader_test.go:169: doc a."b".d=2
reader_test.go:169: doc a.'b.c.d'.d=2

a.b.c.d=2
reader_test.go:169: doc a."\u".c=1
reader_test.go:169: doc a."\UD7FF16".c=1
reader_test.go:169: doc key = """\u"""
reader_test.go:169: doc key = """\UD7FF16"""
reader_test.go:169: doc key = [0,1,2,3,4]
reader_test.go:169: doc key = [1,2,3,4,0]
reader_test.go:169: doc key={a=0}
reader_test.go:169: doc key-test=1
reader_test.go:169: doc k.e .y=1
reader_test.go:169: dock  .  e .y=1
reader_test.go:169: doc"k"  .  'e'  .y=1
reader_test.go:169: doc animal = { type.name = "pug"}
reader_test.go:169: doc key = {v.y=1}
reader_test.go:169: doc a = "\r"
reader_test.go:169: doc another = "# test"
reader_test.go:169: doc 'quoted "value"' = "value"
reader_test.go:169: doc hex3 = 0x123_123
reader_test.go:169: doc hex3 = 0xdead_beef
reader_test.go:184: Error Trace:reader_test.go:184
	Error:  	Not equal: 		expected: 
"{\"hex3\":3735928559}"

actual  : "{\"hex3\":-559038737}"

Diff:
--- Expected
+++ Actual
@@ -1 +1 @@
-{"hex3":3735928559}
+{"hex3":-559038737}
Test:   TestReader
reader_test.go:169: doc flt9 = -0e0
reader_test.go:169: doc sf6 = -nan
reader_test.go:169: doc sf6 = +nan
reader_test.go:169: doc k = 0e0
reader_test.go:169: doc sf6 = +inf
reader_test.go:169: doc sf6 = -inf
reader_test.go:169: doc sf6 = inf
reader_test.go:169: doc key = """a b c \

ooo"""
reader_test.go:169: doc key = """value  \
"""
reader_test.go:169: doc [x.y.z.w] # for this to work

Processed: closing 1002320

2022-01-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 1002320
Bug #1002320 [src:segyio] segyio: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.10 3.9" "--test-args=-o 
python_files=test/*" returned exit code 13
Marked Bug as done
> thanks
Stopping processing here.

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



Bug#1004047: python-django-dbconn-retry: autopkgtest failure: Authentication failure

2022-01-19 Thread Paul Gevers

Source: python-django-dbconn-retry
Version: 0.1.6-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

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


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

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

Paul

[1] https://qa.debian.org/excuses.php?package=python-django-dbconn-retry

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-django-dbconn-retry/18488294/log.gz

Password: su: Authentication failure
autopkgtest [16:49:14]: test upstream



OpenPGP_signature
Description: OpenPGP digital signature


Bug#1004046: python-aioamqp: autopkgtest regression: No module named 'pamqp.commands'

2022-01-19 Thread Paul Gevers

Source: python-aioamqp
Version: 0.14.0-4
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
python-aioamqp from testing0.14.0-4
all others from testingfrom testing

I copied some of the output at the bottom of this report. Seems like you 
are missing a *versioned* (test) dependency somewhere. It seems the test 
passes in pure unstable.


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


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

Paul

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

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

Testing with python3.9:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/aioamqp/__init__.py", line 6, in 


from .protocol import AmqpProtocol
  File "/usr/lib/python3/dist-packages/aioamqp/protocol.py", line 8, in 


import pamqp.commands
ModuleNotFoundError: No module named 'pamqp.commands'
autopkgtest [20:11:40]: test autodep8-python3



OpenPGP_signature
Description: OpenPGP digital signature


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

2022-01-19 Thread John Paul Adrian Glaubitz
Hi Aurelien!

Unfortunately, glibc no longer builds with this change on powerpc and ppc64
and kernel builds still fails on both targets:

> https://buildd.debian.org/status/fetch.php?pkg=glibc=powerpc=2.33-3=1642542048=0
> https://buildd.debian.org/status/fetch.php?pkg=glibc=ppc64=2.33-3=1642542055=0

> https://buildd.debian.org/status/fetch.php?pkg=linux=powerpc=5.15.15-1=1642579068=0
> https://buildd.debian.org/status/fetch.php?pkg=linux=ppc64=5.15.15-1=1642578946=0

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Bug#1003865: GPG error: http://deb.debian.org/debian sid InRelease: The following signatures were invalid: BADSIG 648ACFD622F3D138 Debian Archive Automatic Signing Key (10/buster)

2022-01-19 Thread Andreas Beckmann
On Wed, 19 Jan 2022 02:47:56 +0530 Pirate Praveen 
 wrote:
I have seen at least one forum posting on the same error when searching for it so its likely more common 
 https://www.nixcraft.com/t/signatures-were-invalid-badsig-648acfd622f3d138-debian-archive-automatic-signing-key-10-buster/4025


May be related to apt-cacher-ng (though I tried with apt-cacher-ng disabled 
without fixing this issue).


When I encounter similar errors from time to time (once a year or so) I 
consider them as "caching artefacts" and fix them by having apt 
"reinitialize" the corresponding package source: first comment the line 
in sources.list (or rename the snippet in sources.list.d to *.list.off), 
run apt-get update (or whatever you like instead) to "forget" the 
source, enable it again, apt-get update again and the error is gone.


Actually I cannot remember having ever seen that as a piuparts failure 
(and that does a lot of apt-get update), only once in a while on my main 
machine which has everything from oldoldstable to experimental with 4 
foreign architectures available ...


Andreas



Bug#1001591: marked as done (drops attributes used by reverse dependencies)

2022-01-19 Thread Debian Bug Tracking System
Your message dated Wed, 19 Jan 2022 21:42:15 +0100
with message-id <20220119204215.voiax7ttnq74u...@pimeys.fr>
and subject line Re: Bug#1001591: [Pkg-matrix-maintainers] Bug#1002380: drops 
attributes used by reverse dependencies
has caused the Debian Bug report #1001591,
regarding drops attributes used by reverse dependencies
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.)


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

Package: python3-mistune
Version: 2.0.0-1
Severity: normal

Hey,

since this package was upgraded about a week ago, matrix-mirage package 
(matrix client), doesn't work anymore (= blank window trying to load 
something indefinetely).
running matrix-mirage with python3-mistune version 2.0.0-1, produces 
following errors on console :


$ matrix-mirage
~ 21:05:35 | Got library name: 
"/usr/lib/x86_64-linux-gnu/qt5/qml/io/thp/pyotherside/libpyothersideplugin.so"

! 21:05:36 | QSystemTrayIcon::setVisible: No Icon set
/usr/lib/python3/dist-packages/baron/grammator.py:830: 
ParserGeneratorWarning: Token 'EXEC' is unused

  parser = pg.build()
~ 21:05:44 | "PyOtherSide error: Traceback (most recent call last):\n\n 
File \"qrc:/src/backend/qml_bridge.py\", line 181, in \n 
BRIDGE = QMLBridge()\n\n  File \"qrc:/src/backend/qml_bridge.py\", line 
52, in __init__\nfrom .backend import Backend\n\n  File 
\"qrc:/src/backend/backend.py\", line 24, in \nfrom 
.matrix_client import MatrixClient\n\n  File 
\"qrc:/src/backend/matrix_client.py\", line 42, in \nfrom 
.html_markdown import HTML_PROCESSOR as HTML\n\n  File 
\"qrc:/src/backend/html_markdown.py\", line 21, in \nclass 
MarkdownInlineGrammar(mistune.InlineGrammar):\n\nAttributeError: module 
'mistune' has no attribute 'InlineGrammar'\n"
! 21:05:44 | Unhandled PyOtherSide error: Cannot import module: 
backend.qml_bridge (Traceback (most recent call last):


  File "qrc:/src/backend/qml_bridge.py", line 181, in 
BRIDGE = QMLBridge()

  File "qrc:/src/backend/qml_bridge.py", line 52, in __init__
from .backend import Backend

  File "qrc:/src/backend/backend.py", line 24, in 
from .matrix_client import MatrixClient

  File "qrc:/src/backend/matrix_client.py", line 42, in 
from .html_markdown import HTML_PROCESSOR as HTML

  File "qrc:/src/backend/html_markdown.py", line 21, in 
class MarkdownInlineGrammar(mistune.InlineGrammar):

AttributeError: module 'mistune' has no attribute 'InlineGrammar'
)
~ 21:05:44 | "PyOtherSide error: Traceback (most recent call last):\n\n 
File \"\", line 1, in \n\nNameError: name 'BRIDGE' is 
not defined\n"
! 21:05:44 | Unhandled PyOtherSide error: Function not found: 
'BRIDGE.call_backend_coro' (Traceback (most recent call last):


  File "", line 1, in 

NameError: name 'BRIDGE' is not defined
)


downgrading to python3-mistune version 0.8.4-5 in testing, and 
matrix-mirage works as expected.
found relative tip in arch AUR : 
https://aur.archlinux.org/packages/matrix-mirage/#comment-833416, and it 
works for debian too, so that's why i'm submitting this bug here.
if you think this is really a matrix-mirage bug, just reassign as you 
think best.


thanks in advance,
d.


-- System Information:
Distributor ID: Devuan
Description:Devuan GNU/Linux 5 (daedalus/ceres)
Release:5
Codename:   daedalus ceres
Architecture: x86_64

Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)
LSM: AppArmor: enabled

Versions of packages python3-mistune depends on:
ii  python3  3.9.8-1

python3-mistune recommends no packages.

python3-mistune suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Le mardi 11 janvier 2022 à 16:12:43-0500, Sandro Tosi a écrit :
> [snip]

Anyway, I think this bug can be closed right now.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for principles than to live up to them.


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


Bug#965612: marked as done (kmfl-keyboards-mywin: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-01-19 Thread Debian Bug Tracking System
Your message dated Wed, 19 Jan 2022 20:35:36 +
with message-id 
and subject line Bug#965612: fixed in kmfl-keyboards-mywin 2.1.1-4
has caused the Debian Bug report #965612,
regarding kmfl-keyboards-mywin: 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.)


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

Hi,

The package kmfl-keyboards-mywin 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: kmfl-keyboards-mywin
Source-Version: 2.1.1-4
Done: Adrian Bunk 

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated kmfl-keyboards-mywin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Jan 2022 22:00:32 +0200
Source: kmfl-keyboards-mywin
Architecture: source
Version: 2.1.1-4
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 965612
Changes:
 kmfl-keyboards-mywin (2.1.1-4) unstable; urgency=low
 .
   * QA upload.
   * Set Maintainer to Debian QA Group. (see #726361)
   * debian/compat: 5 -> 7. (Closes: #965612)
Checksums-Sha1:
 d520a90f49fb0918ee10dda708cfcf1402c0fbe7 1999 kmfl-keyboards-mywin_2.1.1-4.dsc
 bb64863d1236a91a995bddb43e6d64a7fc028426 2228 
kmfl-keyboards-mywin_2.1.1-4.debian.tar.xz
Checksums-Sha256:
 1483c7ebc28c92651cd9e241bcb9dd5259bce9213ba4073b10fdd499f312b17c 1999 
kmfl-keyboards-mywin_2.1.1-4.dsc
 bc30645c3ceec05591be682cb07b6651894312d5be1359fcd53ca950939495bb 2228 
kmfl-keyboards-mywin_2.1.1-4.debian.tar.xz
Files:
 7bc1872e0697ddfb26b6d9c745e50454 1999 utils extra 
kmfl-keyboards-mywin_2.1.1-4.dsc
 1bc6fa10441e22242b712dceb3a2750e 2228 utils extra 
kmfl-keyboards-mywin_2.1.1-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHobqIACgkQiNJCh6LY
mLFBbhAAxM4pb12ONxlkIiVz+vVLOleJJcPXuQC01vpFKkKWD9px1O02eriyycUh
1QNJuGTGwmRBPWuy2EJWZMluYueb0yEU+z5wL70tgLQmEb0+vPpcqlJm7ZbTwExB
WSSoo9PAoVFFm8aOb+HgqvHaCoYWG2LY6mOD7nPfca9DsQs1Bnvo9yKCcPseuDJX
dsdbMXdJVtNwjRl3aLjbucjxyj7U5r7f7GQtQDPXwK6kf5CEsAtPpaLyalwrAWdx
6onlMQr6Kc01qYMtEEEUG1LQ2T4bNi7UB2jj0tFL1rXqUN/V1lS6IdudKk89KqoO
YBJiEJ5oOwZzxswREPdBQyxw0kJBrdIQ0gsLOtWtvGXn6GMgiVLNFWs69KUXbNjP
upGrQJjaPq0tVHJJpjNGUMD9I0mnqkU/ccd1kYmJKN5qYiD9MlS+GGuATGUq32ZJ
kN6mb19QasHcfQYQ6yPjOOH/XsWT7hWC3cjgqfipZbfSs1uRmdOFyXKeJfAm/kPO
Hkuljw4Cmzd5fGQ/KP0bf32YdvdlfmhKc2oLBM6gQd8ntBkS4ttvVWg7TashGCu/
qOposJRtOY5dEUVisB8JMdnDOBwg4eITGjYuWfaxeoHEX9OitRAA4VY0x2unHDGW
6uV182Ss4KbgfvEYcwltQM9OCULSxS6slLd8rNmLU0vhvNVwjTc=
=YXKv
-END PGP SIGNATURE End Message ---


Processed: severity of 1002163 is normal, severity of 1002376 is normal

2022-01-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 1002163 normal
Bug #1002163 [src:python-m2r] python-m2r: FTBFS: AttributeError: module 
'mistune' has no attribute 'BlockGrammar'
Severity set to 'normal' from 'serious'
> severity 1002376 normal
Bug #1002376 [src:python-aiosqlite] python-aiosqlite: FTBFS: AttributeError: 
module 'mistune' has no attribute 'BlockGrammar'
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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



Processed: tagging 1002312

2022-01-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 1002312 + bookworm sid
Bug #1002312 [gnu-smalltalk-browser] gnu-smalltalk-browser: Smalltalk browser 
fails to start
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

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



Processed: gwcs FTBFS

2022-01-19 Thread Debian Bug Tracking System
Processing control commands:

> block -1 by 1003331
Bug #1004041 [src:gwcs] gwcs FTBFS
1004041 was not blocked by any bugs.
1004041 was blocking: 1001238
Added blocking bug(s) of 1004041: 1003331

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



Bug#1004041: gwcs FTBFS

2022-01-19 Thread Ole Streicher

Control: block -1 by 1003331

This is because the new gwcs needs asdf-wcs-schemas, which is in the NEW 
queue, but not accepted yet.




Processed: gwcs FTBFS

2022-01-19 Thread Debian Bug Tracking System
Processing control commands:

> block 1001238 by -1
Bug #1001238 {Done: Ole Streicher } [src:gwcs] astropy 
breaks gwcs autopkgtest: module 'astropy.modeling.utils' has no attribute 
'_BoundingBox'
1001238 was not blocked by any bugs.
1001238 was not blocking any bugs.
Added blocking bug(s) of 1001238: 1004041

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



Bug#1004041: gwcs FTBFS

2022-01-19 Thread Adrian Bunk
Source: gwcs
Version: 0.18.0-1
Severity: serious
Tags: ftbfs
Control: block 1001238 by -1

https://buildd.debian.org/status/fetch.php?pkg=gwcs=all=0.18.0-1=1642613373=0

...
 ERRORS 
_ ERROR collecting .pybuild/cpython3_3.9_gwcs/build/gwcs/extension.py __
gwcs/extension.py:8: in 
from .converters.selector import (
gwcs/converters/selector.py:11: in 
from asdf_astropy.converters.transform.core import TransformConverterBase
E   ModuleNotFoundError: No module named 'asdf_astropy'
_ ERROR collecting .pybuild/cpython3_3.9_gwcs/build/gwcs/converters/geometry.py 
_
gwcs/converters/geometry.py:5: in 
from asdf_astropy.converters.transform.core import TransformConverterBase
E   ModuleNotFoundError: No module named 'asdf_astropy'
_ ERROR collecting .pybuild/cpython3_3.9_gwcs/build/gwcs/converters/selector.py 
_
gwcs/converters/selector.py:11: in 
from asdf_astropy.converters.transform.core import TransformConverterBase
E   ModuleNotFoundError: No module named 'asdf_astropy'
_ ERROR collecting 
.pybuild/cpython3_3.9_gwcs/build/gwcs/converters/spectroscopy.py _
gwcs/converters/spectroscopy.py:6: in 
from asdf_astropy.converters.transform.core import (
E   ModuleNotFoundError: No module named 'asdf_astropy'
_ ERROR collecting 
.pybuild/cpython3_3.9_gwcs/build/gwcs/converters/tests/test_transforms.py _
gwcs/converters/tests/test_transforms.py:7: in 
from asdf_astropy.converters.transform.tests.test_transform import (
E   ModuleNotFoundError: No module named 'asdf_astropy'
_ ERROR collecting 
.pybuild/cpython3_3.9_gwcs/build/gwcs/converters/tests/test_transforms.py _
ImportError while importing test module 
'/<>/.pybuild/cpython3_3.9_gwcs/build/gwcs/converters/tests/test_transforms.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.9/importlib/__init__.py:127: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
gwcs/converters/tests/test_transforms.py:7: in 
from asdf_astropy.converters.transform.tests.test_transform import (
E   ModuleNotFoundError: No module named 'asdf_astropy'
_ ERROR collecting 
.pybuild/cpython3_3.9_gwcs/build/gwcs/converters/tests/test_wcs.py _
gwcs/converters/tests/test_wcs.py:15: in 
from asdf_astropy.converters.transform.tests.test_transform import (  # 
noqa: E402
E   ModuleNotFoundError: No module named 'asdf_astropy'
_ ERROR collecting 
.pybuild/cpython3_3.9_gwcs/build/gwcs/converters/tests/test_wcs.py _
ImportError while importing test module 
'/<>/.pybuild/cpython3_3.9_gwcs/build/gwcs/converters/tests/test_wcs.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.9/importlib/__init__.py:127: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
gwcs/converters/tests/test_wcs.py:15: in 
from asdf_astropy.converters.transform.tests.test_transform import (  # 
noqa: E402
E   ModuleNotFoundError: No module named 'asdf_astropy'
_ ERROR collecting .pybuild/cpython3_3.9_gwcs/build/gwcs/tests/test_geometry.py 
_
gwcs/tests/test_geometry.py:10: in 
from asdf_astropy.converters.transform.tests.test_transform import (
E   ModuleNotFoundError: No module named 'asdf_astropy'
_ ERROR collecting .pybuild/cpython3_3.9_gwcs/build/gwcs/tests/test_geometry.py 
_
ImportError while importing test module 
'/<>/.pybuild/cpython3_3.9_gwcs/build/gwcs/tests/test_geometry.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.9/importlib/__init__.py:127: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
gwcs/tests/test_geometry.py:10: in 
from asdf_astropy.converters.transform.tests.test_transform import (
E   ModuleNotFoundError: No module named 'asdf_astropy'
=== warnings summary ===
../../../../../../usr/lib/python3/dist-packages/astropy/wcs/wcsapi/sliced_low_level_wcs.py:6
  /usr/lib/python3/dist-packages/astropy/wcs/wcsapi/sliced_low_level_wcs.py:6: 
AstropyDeprecationWarning: SlicedLowLevelWCS has been moved to 
astropy.wcs.wcsapi.wrappers.sliced_wcs.SlicedLowLevelWCS, or can be imported 
from astropy.wcs.wcsapi.
warnings.warn(

-- Docs: https://docs.pytest.org/en/stable/warnings.html
=== short test summary info 
ERROR gwcs/extension.py - ModuleNotFoundError: No module named 'asdf_astropy'
ERROR gwcs/converters/geometry.py - ModuleNotFoundError: No module named 'asd...
ERROR gwcs/converters/selector.py - ModuleNotFoundError: No module named 'asd...
ERROR gwcs/converters/spectroscopy.py - ModuleNotFoundError: No module named ...
ERROR gwcs/converters/tests/test_transforms.py - ModuleNotFoundError: No modu...
ERROR gwcs/converters/tests/test_transforms.py
ERROR gwcs/converters/tests/test_wcs.py - ModuleNotFoundError: No module name...
ERROR 

Bug#1003453: marked as done (Old bug is back, needs a rebuild.)

2022-01-19 Thread Debian Bug Tracking System
Your message dated Wed, 19 Jan 2022 19:34:56 +
with message-id 
and subject line Bug#1003453: fixed in qtcreator 6.0.2-1
has caused the Debian Bug report #1003453,
regarding Old bug is back, needs a rebuild.
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.)


-- 
1003453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qtcreator
Version: 6.0.1-1
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Looks like qtcreator (and iwyu/etc) need to be rebuilt again.
After some recent updates, qtcreator again shows errors
about certain C++ types not being known.

Roman


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

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

Versions of packages qtcreator depends on:
ii  clang-13   1:13.0.1~+rc1-1~exp4
ii  libc6  2.33-2
ii  libclang1-13   1:13.0.1~+rc1-1~exp4
ii  libdw1 0.186-1
ii  libelf10.186-1
ii  libgcc-s1  11.2.0-13
ii  libkf5syntaxhighlighting5  5.88.0-2
ii  libqt5concurrent5  5.15.2+dfsg-14
ii  libqt5core5a [qtbase-abi-5-15-2]   5.15.2+dfsg-14
ii  libqt5designer55.15.2-5+b1
ii  libqt5designercomponents5  5.15.2-5+b1
ii  libqt5gui5 5.15.2+dfsg-14
ii  libqt5help55.15.2-5+b1
ii  libqt5network5 5.15.2+dfsg-14
ii  libqt5printsupport55.15.2+dfsg-14
ii  libqt5qml5 [qtdeclarative-abi-5-15-2]  5.15.2+dfsg-9
ii  libqt5quick5   5.15.2+dfsg-9
ii  libqt5quickwidgets55.15.2+dfsg-9
ii  libqt5serialport5  5.15.2-2
ii  libqt5sql5 5.15.2+dfsg-14
ii  libqt5sql5-sqlite  5.15.2+dfsg-14
ii  libqt5svg5 5.15.2-4
ii  libqt5test55.15.2+dfsg-14
ii  libqt5widgets5 5.15.2+dfsg-14
ii  libqt5xml5 5.15.2+dfsg-14
ii  libstdc++6 11.2.0-13
ii  libyaml-cpp0.7 0.7.0+dfsg-8
ii  libzstd1   1.4.8+dfsg-3
ii  qml-module-qtqml-models2   5.15.2+dfsg-9
ii  qml-module-qtquick-controls5.15.2-2
ii  qml-module-qtquick25.15.2+dfsg-9
ii  qtchooser  66-2
ii  qtcreator-data 6.0.1-1

Versions of packages qtcreator recommends:
pn  clang-tidy 
ii  gdb10.1-2
ii  konsole [x-terminal-emulator]  4:21.08.2-1
ii  make   4.3-4.1
ii  qmlscene   5.15.2+dfsg-9
pn  qt5-doc
ii  qt5-qmltooling-plugins 5.15.2+dfsg-9
ii  qtbase5-dev-tools  5.15.2+dfsg-14
pn  qtcreator-doc  
ii  qtdeclarative5-dev-tools   5.15.2+dfsg-9
ii  qttools5-dev-tools 5.15.2-5+b1
ii  qttranslations5-l10n   5.15.2-2
ii  qtxmlpatterns5-dev-tools   5.15.2-3
ii  xterm [x-terminal-emulator]370-1

Versions of packages qtcreator suggests:
pn  clazy  
ii  cmake  3.22.1-1+b1
ii  g++4:11.2.0-2
ii  git1:2.34.1-1
ii  meson  0.60.3-1
pn  python3-pylsp  
ii  subversion 1.14.1-3+b2
ii  valgrind   1:3.18.1-1

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEjkF6151RK40WXe2HCDw+u0oWieAFAmHcJ2QACgkQCDw+u0oW
ieCsyhAAlol3UkpwhpKZf0vvdmoMCEc3sBzQYm2FfEQ3/3cwvTh5f+JIDSNTxYgV
3lIPFlMv7IKcc55p0e/MXFlBOHOG2q/bYVdTuf5h/cuAafX6Y2zr5m2TjFUNqffX
646hQS4rkoipR1r3l4ou5gomBpW+WoqEExnpc02/GfwxvVOTrQuZe8C1nXj2OlzZ
YFYOgCQBv6hdzxVcMTx7v4RQetLmJ/c+GegATqjLOEHdtr5D4KHRxkS/tbr/itQE
8wkaD0G4PRTRtGtDPJf53UTBD7rBLcz44HIWp5bn62dMO4epwY5EXnjNRt1aO9HO
7LxfcmAnC8w42tOB7T3wIEbw+qyPTCCaw8H4jYmVlQfptpGk7lG5CInqwfBGQLNb
JPzq7AVAmksssbeOyzxZbh6TzGqOrhJeCxdOqyRtn6/FR1uubIBco8U2Bzz7Tk12
dPse/gzvtrBky3fWeY1VQ83dhihsb5Jcg2lsaHW7eVA4n9EIdJTgMRdxgdOOW6XE

Processed: src:plink2: fails to migrate to testing for too long: autopkgtest regression

2022-01-19 Thread Debian Bug Tracking System
Processing control commands:

> close -1 2.00~a3-211011+dfsg-1
Bug #1004037 [src:plink2] src:plink2: fails to migrate to testing for too long: 
autopkgtest regression
Marked as fixed in versions plink2/2.00~a3-211011+dfsg-1.
Bug #1004037 [src:plink2] src:plink2: fails to migrate to testing for too long: 
autopkgtest regression
Marked Bug as done
> block -1 by 1000782
Bug #1004037 {Done: Paul Gevers } [src:plink2] src:plink2: 
fails to migrate to testing for too long: autopkgtest regression
1004037 was not blocked by any bugs.
1004037 was not blocking any bugs.
Added blocking bug(s) of 1004037: 1000782

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



Bug#1004037: src:plink2: fails to migrate to testing for too long: autopkgtest regression

2022-01-19 Thread Paul Gevers

Source: plink2
Version: 2.00~a3-210816+dfsg-1
Severity: serious
Control: close -1 2.00~a3-211011+dfsg-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1000782

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:plink2 has been trying to migrate for 61 
days [2]. Hence, I am filing this bug.


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


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


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


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



OpenPGP_signature
Description: OpenPGP digital signature


Bug#990428: Add fixed package to stable?

2022-01-19 Thread Jörn Heissler
Hello,

could the fixed version 2.13 please be added to stable/bullseye?
So far it appears to work for me; 2.12 doesn't.

Cheers


signature.asc
Description: PGP signature


Processed: forcibly merging 999524 1002351

2022-01-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forcemerge 999524 1002351
Bug #999524 [src:python-language-server] python-language-server: FTBFS with 
numpy 1.21 (in experimental): dh_auto_test: error: pybuild --test --test-pytest 
-i python{version} -p 3.9 returned exit code 13
Bug #1002351 [src:python-language-server] python-language-server: FTBFS: 
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 
3.9" returned exit code 13
Merged 999524 1002351
> thanks
Stopping processing here.

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



Processed: pyls-black: diff for NMU version 0.4.6-3.1

2022-01-19 Thread Debian Bug Tracking System
Processing control commands:

> tags 997478 + patch
Bug #997478 [src:pyls-black] pyls-black: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p 3.9 returned exit code 13
Added tag(s) patch.
> tags 997478 + pending
Bug #997478 [src:pyls-black] pyls-black: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p 3.9 returned exit code 13
Added tag(s) pending.

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



Bug#997478: pyls-black: diff for NMU version 0.4.6-3.1

2022-01-19 Thread Adrian Bunk
Control: tags 997478 + patch
Control: tags 997478 + pending

Dear maintainer,

I've prepared an NMU for pyls-black (versioned as 0.4.6-3.1) and 
uploaded it to DELAYED/15. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru pyls-black-0.4.6/debian/changelog pyls-black-0.4.6/debian/changelog
--- pyls-black-0.4.6/debian/changelog	2021-02-05 11:19:34.0 +0200
+++ pyls-black-0.4.6/debian/changelog	2022-01-19 19:12:45.0 +0200
@@ -1,3 +1,11 @@
+pyls-black (0.4.6-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add upstream fix for test failure with new Black.
+(Closes: #997478)
+
+ -- Adrian Bunk   Wed, 19 Jan 2022 19:12:45 +0200
+
 pyls-black (0.4.6-3) unstable; urgency=medium
 
   * Fix Build-Depends
diff -Nru pyls-black-0.4.6/debian/patches/0001-Fix-test-failure-with-black-21.4b0-39.patch pyls-black-0.4.6/debian/patches/0001-Fix-test-failure-with-black-21.4b0-39.patch
--- pyls-black-0.4.6/debian/patches/0001-Fix-test-failure-with-black-21.4b0-39.patch	1970-01-01 02:00:00.0 +0200
+++ pyls-black-0.4.6/debian/patches/0001-Fix-test-failure-with-black-21.4b0-39.patch	2022-01-19 19:11:25.0 +0200
@@ -0,0 +1,65 @@
+From 4a2780358c2827b2b1598e9e60365f0d5c9a27a4 Mon Sep 17 00:00:00 2001
+From: Mathis 
+Date: Sat, 5 Jun 2021 06:40:55 +0800
+Subject: Fix test failure with black 21.4b0+ (#39)
+
+Inline PY36_VERSIONS because black no longer exposes it.
+
+Closes #36.
+---
+ pyls_black/plugin.py | 4 +++-
+ tests/test_plugin.py | 9 +++--
+ 2 files changed, 10 insertions(+), 3 deletions(-)
+
+diff --git a/pyls_black/plugin.py b/pyls_black/plugin.py
+index 407802f..dc5d482 100644
+--- a/pyls_black/plugin.py
 b/pyls_black/plugin.py
+@@ -4,6 +4,8 @@ import black
+ import toml
+ from pyls import hookimpl
+ 
++_PY36_VERSIONS = {black.TargetVersion[v] for v in ["PY36", "PY37", "PY38", "PY39"]}
++
+ 
+ @hookimpl(tryfirst=True)
+ def pyls_format_document(document):
+@@ -97,7 +99,7 @@ def load_config(filename: str) -> Dict:
+ black.TargetVersion[x.upper()] for x in file_config["target_version"]
+ )
+ elif file_config.get("py36"):
+-target_version = black.PY36_VERSIONS
++target_version = _PY36_VERSIONS
+ else:
+ target_version = set()
+ 
+diff --git a/tests/test_plugin.py b/tests/test_plugin.py
+index f943b16..e722dba 100644
+--- a/tests/test_plugin.py
 b/tests/test_plugin.py
+@@ -8,7 +8,12 @@ import pytest
+ from pyls import uris
+ from pyls.workspace import Document, Workspace
+ 
+-from pyls_black.plugin import load_config, pyls_format_document, pyls_format_range
++from pyls_black.plugin import (
++_PY36_VERSIONS,
++load_config,
++pyls_format_document,
++pyls_format_range,
++)
+ 
+ here = Path(__file__).parent
+ fixtures_dir = here / "fixtures"
+@@ -191,7 +196,7 @@ def test_load_config_target_version():
+ def test_load_config_py36():
+ config = load_config(str(fixtures_dir / "py36" / "example.py"))
+ 
+-assert config["target_version"] == black.PY36_VERSIONS
++assert config["target_version"] == _PY36_VERSIONS
+ 
+ 
+ def test_load_config_defaults():
+-- 
+2.20.1
+
diff -Nru pyls-black-0.4.6/debian/patches/series pyls-black-0.4.6/debian/patches/series
--- pyls-black-0.4.6/debian/patches/series	2021-02-05 11:19:34.0 +0200
+++ pyls-black-0.4.6/debian/patches/series	2022-01-19 19:12:45.0 +0200
@@ -1 +1,2 @@
 suppress-post-install-tests.patch
+0001-Fix-test-failure-with-black-21.4b0-39.patch


Processed (with 2 errors): Merge duplicates

2022-01-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 1002679 src:gst-plugins-good1.0;
Unknown command or malformed arguments to command.
> forcemerge 998383 1002679
Bug #998383 {Done: Sebastian Dröge } 
[src:gst-plugins-good1.0] gstreamer1.0-qt5 should again be built on armel/armhf
Unable to merge bugs because:
package of #1002679 is 'nheko' not 'src:gst-plugins-good1.0'
Failed to forcibly merge 998383: Did not alter merged bugs.

> thanks
Stopping processing here.

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



Processed: closing 1002379

2022-01-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 1002379
Bug #1002379 [src:taurus] taurus: FTBFS: AttributeError: module 'collections' 
has no attribute 'Callable'
Marked Bug as done
> thanks
Stopping processing here.

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



Bug#1004035: rumur FTBFS on 32bit: Bad system call

2022-01-19 Thread Adrian Bunk
Source: rumur
Version: 2021.12.27-1
Severity: serious
Tags: ftbfs
Control: block 1002186 by -1

https://buildd.debian.org/status/package.php?p=rumur

...
--- SIGSYS {si_signo=SIGSYS, si_code=SYS_SECCOMP, si_call_addr=0x5c20ec, 
si_syscall=__NR_statx, si_arch=AUDIT_ARCH_PPC} ---
+++ killed by SIGSYS +++
/<>/tests/strace-sandbox.sh: line 69: 3494941 Bad system call  
   strace ./model.exe
+ RET=159
+ '[' 159 -eq 0 ']'
+ popd
+ rm -rf /tmp/tmp.MFJZxsf2dZ
+ exit 159


==
FAIL: test_basic_sandbox_m (__main__.rumurDebugMultithreaded)
--
Traceback (most recent call last):
  File "/<>/tests/run-tests.py", line 576, in 
setattr(c, name, lambda self, p=p: self._run(p))
  File "/<>/tests/run-tests.py", line 490, in _run
self._run_param(testcase, True, False, True, False)
  File "/<>/tests/run-tests.py", line 441, in _run_param
self.fail('Unexpected checker exit status {}:\n{}{}'
AssertionError: Unexpected checker exit status -31:
...
Ran 5344 tests in 1239.289s

FAILED (failures=13, skipped=2211)
make[4]: *** [CMakeFiles/check.dir/build.make:73: CMakeFiles/check] Error 1



Processed: rumur FTBFS on 32bit: Bad system call

2022-01-19 Thread Debian Bug Tracking System
Processing control commands:

> block 1002186 by -1
Bug #1002186 {Done: Matthew Fernandez } 
[src:rumur] rumur: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make 
-j4 check ARGS\+=--verbose ARGS\+=-j4 returned exit code 2
1002186 was not blocked by any bugs.
1002186 was not blocking any bugs.
Added blocking bug(s) of 1002186: 1004035

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



Processed: clamfs: diff for NMU version 1.2.0-2.1

2022-01-19 Thread Debian Bug Tracking System
Processing control commands:

> tags 1002180 + patch
Bug #1002180 [src:clamfs] clamfs: FTBFS: stats.cxx:73:34: error: ‘mallinfo 
mallinfo()’ is deprecated [-Werror=deprecated-declarations]
Added tag(s) patch.
> tags 1002180 + pending
Bug #1002180 [src:clamfs] clamfs: FTBFS: stats.cxx:73:34: error: ‘mallinfo 
mallinfo()’ is deprecated [-Werror=deprecated-declarations]
Added tag(s) pending.

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



Bug#1002180: clamfs: diff for NMU version 1.2.0-2.1

2022-01-19 Thread Adrian Bunk
Control: tags 1002180 + patch
Control: tags 1002180 + pending

Dear maintainer,

I've prepared an NMU for clamfs (versioned as 1.2.0-2.1) and uploaded
it to DELAYED/14. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru clamfs-1.2.0/debian/changelog clamfs-1.2.0/debian/changelog
--- clamfs-1.2.0/debian/changelog	2020-01-10 02:46:18.0 +0200
+++ clamfs-1.2.0/debian/changelog	2022-01-19 18:35:36.0 +0200
@@ -1,3 +1,10 @@
+clamfs (1.2.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't build with -Werror. (Closes: #1002180)
+
+ -- Adrian Bunk   Wed, 19 Jan 2022 18:35:36 +0200
+
 clamfs (1.2.0-2) unstable; urgency=medium
 
   * Add patches/Remove-_start-symbol-check-for-CXX-libraries.patch to fix
diff -Nru clamfs-1.2.0/debian/patches/no-Werror.patch clamfs-1.2.0/debian/patches/no-Werror.patch
--- clamfs-1.2.0/debian/patches/no-Werror.patch	1970-01-01 02:00:00.0 +0200
+++ clamfs-1.2.0/debian/patches/no-Werror.patch	2022-01-19 18:35:36.0 +0200
@@ -0,0 +1,15 @@
+Description: Don't build with -Werror.
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/1002180
+
+--- clamfs-1.2.0.orig/configure.ac
 clamfs-1.2.0/configure.ac
+@@ -37,7 +37,7 @@ AC_CHECK_FUNCS([fchdir fdatasync fork ft
+ AC_C_FDPASSING
+ 
+ # Set initial CPPFLAGS
+-CPPFLAGS="$CPPFLAGS -Wall -Werror -Wextra"
++CPPFLAGS="$CPPFLAGS -Wall -Wextra"
+ 
+ # Checks for boost
+ AX_BOOST_BASE(1.33)
diff -Nru clamfs-1.2.0/debian/patches/series clamfs-1.2.0/debian/patches/series
--- clamfs-1.2.0/debian/patches/series	2020-01-10 01:59:11.0 +0200
+++ clamfs-1.2.0/debian/patches/series	2022-01-19 18:35:36.0 +0200
@@ -1 +1,2 @@
 Remove-_start-symbol-check-for-CXX-libraries.patch
+no-Werror.patch


Processed: bug 1002173 is forwarded to https://github.com/pympler/pympler/commit/dcb851f26fca8f8e5a4d8e2662cb84d43f98d6e3

2022-01-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 1002173 
> https://github.com/pympler/pympler/commit/dcb851f26fca8f8e5a4d8e2662cb84d43f98d6e3
Bug #1002173 [src:pympler] pympler: FTBFS: ImportError: cannot import name 
'MutableMapping' from 'collections' 
(/usr/lib/python3.10/collections/__init__.py)
Set Bug forwarded-to-address to 
'https://github.com/pympler/pympler/commit/dcb851f26fca8f8e5a4d8e2662cb84d43f98d6e3'.
> thanks
Stopping processing here.

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



Processed: closing 1002168

2022-01-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 1002168
Bug #1002168 [src:gamehub] gamehub: FTBFS: 
src/com.github.tkashkin.gamehub.p/data/Runnable.c:1977:57: error: lvalue 
required as unary ‘&’ operand
Marked Bug as done
> thanks
Stopping processing here.

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



Bug#1002167: hmat-oss: diff for NMU version 1.2.0-2.2

2022-01-19 Thread Adrian Bunk
Control: tags 1002167 + patch
Control: tags 1002167 + pending

Dear maintainer,

I've prepared an NMU for hmat-oss (versioned as 1.2.0-2.2) and uploaded 
it to DELAYED/14. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru hmat-oss-1.2.0/debian/changelog hmat-oss-1.2.0/debian/changelog
--- hmat-oss-1.2.0/debian/changelog	2020-05-02 02:18:14.0 +0300
+++ hmat-oss-1.2.0/debian/changelog	2022-01-19 18:14:34.0 +0200
@@ -1,3 +1,10 @@
+hmat-oss (1.2.0-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Backport upstream fix for FTBFS with glibc 2.33. (Closes: #1002167)
+
+ -- Adrian Bunk   Wed, 19 Jan 2022 18:14:34 +0200
+
 hmat-oss (1.2.0-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru hmat-oss-1.2.0/debian/patches/0001-instrumentation-Use-mallinfo2-from-glibc-2.33.patch hmat-oss-1.2.0/debian/patches/0001-instrumentation-Use-mallinfo2-from-glibc-2.33.patch
--- hmat-oss-1.2.0/debian/patches/0001-instrumentation-Use-mallinfo2-from-glibc-2.33.patch	1970-01-01 02:00:00.0 +0200
+++ hmat-oss-1.2.0/debian/patches/0001-instrumentation-Use-mallinfo2-from-glibc-2.33.patch	2022-01-19 18:14:34.0 +0200
@@ -0,0 +1,41 @@
+From 40b12c8c90ab5d67847fec6bda6111c396fa3b0d Mon Sep 17 00:00:00 2001
+From: Julien Schueller 
+Date: Fri, 19 Feb 2021 10:22:35 +0100
+Subject: instrumentation: Use mallinfo2 from glibc 2.33
+
+mallinfo being deprecated
+---
+ src/common/memory_instrumentation.cpp | 8 
+ 1 file changed, 8 insertions(+)
+
+diff --git a/src/common/memory_instrumentation.cpp b/src/common/memory_instrumentation.cpp
+index 22acd3d..a98870e 100644
+--- a/src/common/memory_instrumentation.cpp
 b/src/common/memory_instrumentation.cpp
+@@ -31,7 +31,11 @@
+ #ifdef __GLIBC__
+ #include 
+ // Do not care about thread safety. This is an acceptable approximation.
++#if __GLIBC_PREREQ(2,33)
++static struct mallinfo2 global_mallinfo;
++#else
+ static struct mallinfo global_mallinfo;
++#endif
+ static int mallinfo_counter;
+ #endif
+ static int write_counter;
+@@ -142,7 +146,11 @@ void MemoryInstrumenter::allocImpl(mem_t size, char type) {
+ #ifdef __GLIBC__
+ mallinfo_counter ++;
+ if(mallinfo_counter >= mallinfo_sampling) {
++#if __GLIBC_PREREQ(2,33)
++global_mallinfo = mallinfo2();
++#else
+ global_mallinfo = mallinfo();
++#endif
+ mallinfo_counter = 0;
+ }
+ int k = 3;
+-- 
+2.20.1
+
diff -Nru hmat-oss-1.2.0/debian/patches/series hmat-oss-1.2.0/debian/patches/series
--- hmat-oss-1.2.0/debian/patches/series	2020-05-02 01:27:04.0 +0300
+++ hmat-oss-1.2.0/debian/patches/series	2022-01-19 18:14:05.0 +0200
@@ -1,3 +1,4 @@
 0001-make-build-reproducible.patch
 0002-Fix-compilation-on-Linux-32-bits-systems.patch
 fix_gcc.patch
+0001-instrumentation-Use-mallinfo2-from-glibc-2.33.patch


Processed: hmat-oss: diff for NMU version 1.2.0-2.2

2022-01-19 Thread Debian Bug Tracking System
Processing control commands:

> tags 1002167 + patch
Bug #1002167 [src:hmat-oss] hmat-oss: FTBFS: memory_instrumentation.cpp:145:39: 
error: ‘mallinfo mallinfo()’ is deprecated [-Werror=deprecated-declarations]
Added tag(s) patch.
> tags 1002167 + pending
Bug #1002167 [src:hmat-oss] hmat-oss: FTBFS: memory_instrumentation.cpp:145:39: 
error: ‘mallinfo mallinfo()’ is deprecated [-Werror=deprecated-declarations]
Added tag(s) pending.

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



Bug#999821: marked as done (fftw: FBTFS: dh_install: error: missing files, aborting)

2022-01-19 Thread Debian Bug Tracking System
Your message dated Wed, 19 Jan 2022 16:03:58 +
with message-id 
and subject line Bug#999821: fixed in fftw 2.1.5-6
has caused the Debian Bug report #999821,
regarding fftw: FBTFS: dh_install: error: missing files, aborting
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.)


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

fftw fails to build from source:
|debian/rules override_dh_install-arch
| make[1]: Entering directory '/<>'
| mkdir -p /<>/debian/tmp-single/usr/share/doc/sfftw-dev/fortran
| mkdir -p /<>/debian/tmp-double/usr/share/doc/fftw-dev/fortran
| cp -a fortran/fftw_f77.i 
/<>/debian/tmp-single/usr/share/doc/sfftw-dev/fortran/
| cp -a fortran/fftw_f77.i 
/<>/debian/tmp-double/usr/share/doc/fftw-dev/fortran/
| dh_install --sourcedir=/<>/debian/tmp-single -p sfftw2
| dh_install: warning: Cannot find (any matches for) "usr/lib/lib*.so.*" (tried 
in /<>/debian/tmp-single, debian/tmp)
| 
| dh_install: warning: sfftw2 missing files: usr/lib/lib*.so.*
| dh_install: error: missing files, aborting
| make[1]: *** [debian/rules:78: override_dh_install-arch] Error 25
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:14: binary-arch] Error 2
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

The full build log can be found there:
https://buildd.debian.org/fetch.php?pkg=fftw=amd64=2.1.5-5=1636562013=0
--- End Message ---
--- Begin Message ---
Source: fftw
Source-Version: 2.1.5-6
Done: Andreas Tille 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Jan 2022 16:38:42 +0100
Source: fftw
Architecture: source
Version: 2.1.5-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Andreas Tille 
Closes: 999821
Changes:
 fftw (2.1.5-6) unstable; urgency=medium
 .
   * Team upload.
   * DEP3
   * Enable architecture all builds
   * Enhance clean target
   * Do not run configure twice (in arch and indep build) to ensure
 libsfftw will be properly build
 Closes: #999821
Checksums-Sha1:
 d9fdacbe6c2393a9b90de295970cf363b722 2203 fftw_2.1.5-6.dsc
 67d1c2d38ccbc7d7e5813fab9f6b9f27b12bfedc 58760 fftw_2.1.5-6.debian.tar.xz
 55097b98ebf456d534b47690fda1c1bbcfe584b0 9768 fftw_2.1.5-6_amd64.buildinfo
Checksums-Sha256:
 d4b11ff493d958dda6f741b0d10b62c2391cb8b37d4f63715b6a14720d8006e3 2203 
fftw_2.1.5-6.dsc
 a2317d16510ddb82f91d9cdcf136df0609894a1416dbcdf8b761969f54c00442 58760 
fftw_2.1.5-6.debian.tar.xz
 691652af7b4af93ce42769eafad54f72f9c5a253af9660464f85db3bed56ee23 9768 
fftw_2.1.5-6_amd64.buildinfo
Files:
 e53666c56794bc7addd428aa76e0a8c4 2203 oldlibs optional fftw_2.1.5-6.dsc
 e28ed64927e0367f902e96e30609fef9 58760 oldlibs optional 
fftw_2.1.5-6.debian.tar.xz
 e5a7ed8c4886985ae6dd29ade3c6454a 9768 oldlibs optional 
fftw_2.1.5-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmHoMlgRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHqFw/+PLVMmWhbjXSJ0S8IurjNM3GDsJ4tC88a
c3yyl/tfoa9xxq7LKqAPYbQO/5Pfc4JB95L0ecBgD3pl5n8GOyV2cUtrRYgg2CYy
RyJAzl/ySOBKPc6ZYkV1NyGBHNe67r3/J1cryA7qVqMh/kzmXpfQEk1NF9ckuWsr
1tTUTv+Jyb2QonuX0Xiw6BjzpwlJzclcN/ekTN3yMrsohbbCHL+flqxaLleF2Xla
8mkIWxqY7k0M+fp3+kXh7IB0J1AYlQSL2TM8RVkVc5SGhD98lgOUCwuHc06jRGiK
IMIhLHdzye4Q/tTx5xHYsmvsnInFreeq2xrFBAUd/XjttsfiJQmiQMw4RlppWqsU
Q3KwyzDcs3arAYG+heL5Lo+DUfO0pXlxtxmJkxwwuSIioeo39bDJPLUi8OyPgwla
8swveR7fBAEe8NyXFcpECtwuNgRQROZ/AOx0KTqHZjCi5dOwsCGmNzQEAWG7f0I8
t91V+wdvA2BRfoITfW9IOCBwYJkwt9BmiV+hbkr1GgckH5dOpiQujKvlZMUxh9MB
6nLzgS2GzbKmnIK5bSXcTKL0OstDsDeFUKd8KnGiRzPPiWc4oCGLmIVDVOwO/caz
T02Eb6ww+eCUk5wZrMDx08HFgs74Fq0qfX1nTggjXaW2THb4mVehPc32S/EIxIJP
baHzS5SZdOQ=
=fUFO
-END PGP SIGNATURE 

Processed: closing 1002160

2022-01-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 1002160
Bug #1002160 [src:ignition-transport] ignition-transport: FTBFS: 
build-dependency not installable: libignition-msgs5-5 (= 5.1.0+dfsg-7+b1)
Marked Bug as done
> thanks
Stopping processing here.

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



Processed: bug 1002118 is forwarded to https://github.com/romanbsd/heroku-deflater/issues/54

2022-01-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 1002118 https://github.com/romanbsd/heroku-deflater/issues/54
Bug #1002118 [src:ruby-heroku-deflater] ruby-heroku-deflater: FTBFS: ERROR: 
Test "ruby2.7" failed: NoMethodError: undefined method `match?' for 
#
Set Bug forwarded-to-address to 
'https://github.com/romanbsd/heroku-deflater/issues/54'.
> thanks
Stopping processing here.

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



Processed: bug 1002106 is forwarded to https://github.com/andrmuel/gr-dab/issues/28

2022-01-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 1002106 https://github.com/andrmuel/gr-dab/issues/28
Bug #1002106 [src:gr-dab] gr-dab: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to 
`pthread_create'
Set Bug forwarded-to-address to 'https://github.com/andrmuel/gr-dab/issues/28'.
> thanks
Stopping processing here.

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



Processed: Merge duplicates

2022-01-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 1002099 dh-python
Bug #1002099 [src:pagure] pagure: FTBFS: E: Build killed with signal TERM after 
150 minutes of inactivity
Bug reassigned from package 'src:pagure' to 'dh-python'.
No longer marked as found in versions pagure/5.11.3+dfsg-1.
Ignoring request to alter fixed versions of bug #1002099 to the same values 
previously set
> reassign 1002189 dh-python
Bug #1002189 [src:aiohttp-cors] aiohttp-cors: FTBFS: AttributeError: 'NoneType' 
object has no attribute 'split'
Bug reassigned from package 'src:aiohttp-cors' to 'dh-python'.
No longer marked as found in versions aiohttp-cors/0.7.0-2.
Ignoring request to alter fixed versions of bug #1002189 to the same values 
previously set
> forcemerge 1002182 1002099 1002189
Bug #1002182 {Done: Stefano Rivera } [dh-python] 
qutebrowser: FTBFS: AttributeError: 'NoneType' object has no attribute 'split'
Bug #1002096 {Done: Stefano Rivera } [dh-python] grpc: 
FTBFS: AttributeError: 'NoneType' object has no attribute 'split'
Bug #1002200 {Done: Stefano Rivera } [dh-python] wfuzz: 
FTBFS: AttributeError: 'NoneType' object has no attribute 'split'
Bug #1002207 {Done: Stefano Rivera } [dh-python] 
pantalaimon: FTBFS: AttributeError: 'NoneType' object has no attribute 'split'
Bug #1002290 {Done: Stefano Rivera } [dh-python] 
dh_python3 needing contextvars -- not a problem with my package, then?
Bug #1002189 [dh-python] aiohttp-cors: FTBFS: AttributeError: 'NoneType' object 
has no attribute 'split'
Severity set to 'grave' from 'serious'
Marked Bug as done
Added indication that 1002189 affects qutebrowser,python-anyio,grpc,pantalaimon
Marked as fixed in versions dh-python/5.20211225.
Marked as found in versions dh-python/5.20211213 and dh-python/5.20211217.
Added tag(s) confirmed.
Bug #1002099 [dh-python] pagure: FTBFS: E: Build killed with signal TERM after 
150 minutes of inactivity
Severity set to 'grave' from 'serious'
Marked Bug as done
Added indication that 1002099 affects qutebrowser,python-anyio,grpc,pantalaimon
Marked as fixed in versions dh-python/5.20211225.
Marked as found in versions dh-python/5.20211213 and dh-python/5.20211217.
Added tag(s) confirmed.
Bug #1002096 {Done: Stefano Rivera } [dh-python] grpc: 
FTBFS: AttributeError: 'NoneType' object has no attribute 'split'
Bug #1002200 {Done: Stefano Rivera } [dh-python] wfuzz: 
FTBFS: AttributeError: 'NoneType' object has no attribute 'split'
Bug #1002207 {Done: Stefano Rivera } [dh-python] 
pantalaimon: FTBFS: AttributeError: 'NoneType' object has no attribute 'split'
Bug #1002290 {Done: Stefano Rivera } [dh-python] 
dh_python3 needing contextvars -- not a problem with my package, then?
Merged 1002096 1002099 1002182 1002189 1002200 1002207 1002290
> affects 1002182 src:pagure src:aiohttp-cors
Bug #1002182 {Done: Stefano Rivera } [dh-python] 
qutebrowser: FTBFS: AttributeError: 'NoneType' object has no attribute 'split'
Bug #1002096 {Done: Stefano Rivera } [dh-python] grpc: 
FTBFS: AttributeError: 'NoneType' object has no attribute 'split'
Bug #1002099 {Done: Stefano Rivera } [dh-python] pagure: 
FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
Bug #1002189 {Done: Stefano Rivera } [dh-python] 
aiohttp-cors: FTBFS: AttributeError: 'NoneType' object has no attribute 'split'
Bug #1002200 {Done: Stefano Rivera } [dh-python] wfuzz: 
FTBFS: AttributeError: 'NoneType' object has no attribute 'split'
Bug #1002207 {Done: Stefano Rivera } [dh-python] 
pantalaimon: FTBFS: AttributeError: 'NoneType' object has no attribute 'split'
Bug #1002290 {Done: Stefano Rivera } [dh-python] 
dh_python3 needing contextvars -- not a problem with my package, then?
Added indication that 1002182 affects src:pagure and src:aiohttp-cors
Added indication that 1002096 affects src:pagure and src:aiohttp-cors
Added indication that 1002099 affects src:pagure and src:aiohttp-cors
Added indication that 1002189 affects src:pagure and src:aiohttp-cors
Added indication that 1002200 affects src:pagure and src:aiohttp-cors
Added indication that 1002207 affects src:pagure and src:aiohttp-cors
Added indication that 1002290 affects src:pagure and src:aiohttp-cors
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1002096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002096
1002099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002099
1002182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002182
1002189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002189
1002200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002200
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#1003447: marked as done (pgplot5: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-01-19 Thread Debian Bug Tracking System
Your message dated Wed, 19 Jan 2022 14:48:47 +
with message-id 
and subject line Bug#1003447: fixed in pgplot5 5.2.2-19.5
has caused the Debian Bug report #1003447,
regarding pgplot5: 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.)


-- 
1003447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pgplot5
Version: 5.2.2-19.4
Severity: serious
Tags: ftbfs sid bookworm
User: nthyk...@master.debian.org
Usertags: compat-5-6-removal

Hi,

The package pgplot5 uses debhelper with a compat level of 5 or 6,
which is no longer supported [1].

Please bump the debhelper compat at your earliest convenience

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

  * Compat 7 is the bare minimum


Thanks,
Andreas

[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html
--- End Message ---
--- Begin Message ---
Source: pgplot5
Source-Version: 5.2.2-19.5
Done: Picca Frédéric-Emmanuel 

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

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated pgplot5 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Jan 2022 15:27:56 +0100
Source: pgplot5
Architecture: source
Version: 5.2.2-19.5
Distribution: unstable
Urgency: medium
Maintainer: Carlo Segre 
Changed-By: Picca Frédéric-Emmanuel 
Closes: 1003447
Changes:
 pgplot5 (5.2.2-19.5) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Use secure URI in Homepage field.
   * Bump debhelper from deprecated 5 to 13.
   * Set debhelper-compat version in Build-Depends.
   * d/rules: Modernize to use dh
   * Bug fix: "Removal of obsolete debhelper compat 5 and 6 in bookworm",
 thanks to Andreas Beckmann (Closes: #1003447).
Checksums-Sha1:
 59e205cf6c3e5553b4fadc094ef41901c4e45633 1999 pgplot5_5.2.2-19.5.dsc
 4beb9ed7a6cf1c36cf150e7e92562cefe99bbffc 22628 pgplot5_5.2.2-19.5.debian.tar.xz
Checksums-Sha256:
 6799dade7a4f79ccc359d641686c44a90b9dc6c6e2bb44c31b9efdc2856e7f4b 1999 
pgplot5_5.2.2-19.5.dsc
 26cacbc2a0a34c58647048ed0bc90c6e69b9625ab2c22c1158a7d96bd4d089b5 22628 
pgplot5_5.2.2-19.5.debian.tar.xz
Files:
 7f730eb50bc73edc894ee8444ae5951d 1999 non-free/math optional 
pgplot5_5.2.2-19.5.dsc
 b8fee64fb9c3e082a3ced2994249f87b 22628 non-free/math optional 
pgplot5_5.2.2-19.5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE2bRTt5m4gw2UXmoKW/VOXhK5ALsFAmHoIGgRHHBpY2NhQGRl
Ymlhbi5vcmcACgkQW/VOXhK5ALvUMw/+In1p+cmaHLdK+q8rGKOnfGQCODOYtLnt
4vh7FpNY9wYQz2Xzl0UK3Jg+e3H74hrYBY4V3hG8tKBa06L6eRSJ2yfkQj7or8lV
wDplIkoJ/1SaYcvHzwT4RU3Zrzr+/ZTVRnjiApX6/MPrIStl0RVAxZHyBvsX6Zo+
tYTkmmfhZAFU9zBLBIM+Nza+7cibeOMRLk1R+tCy9SosczfadbyT+vg0GkQ7iqeg
iuY6ol3lS7zsCpfxGw+2BuQfO0lwyI14bT31+/VfnBBSCz5f7VoIoP/ii30G2bYJ
4hWNsWVG4BuaXIXqtgJJzVU3sOezWQ8Q1hxhrh7HZMnlkPO8eSvA1coUBlbxuSfJ
dMLM0l4wUcK7bcWw+t+bS8go9JKzgojiWehX4DG4bTJBvXLQH+REso5k1M9HdSDY
/8uJ7NxytSZzMdwr1vLH2nRHXUjSQ5yhEAC6qurJRpJOR2d9VcGLR9VBqbJ0gz6P
NFMRjM4aJMhj7SkCjpvdjoa/myWh5XtDm0WrW8EFElNAJ6A3DrbCC2FToRc2f9tH
N9SHdYOLqpX/jqPMrqYS2lG2Qq07v1WYLRh9UCpo8wgLawWhBCYUbUCYkPjVyzWs
EEvhnX9hVf/OQMdmefzNkdQQXybL66pwOZ2zioPUei+aJd8m/whxZlD8HFKT1Sut
TLhVI93Vrz4=
=ZdGT
-END PGP SIGNATURE End Message ---


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

2022-01-19 Thread Debian Bug Tracking System
Your message dated Wed, 19 Jan 2022 14:48:34 +
with message-id 
and subject line Bug#965487: fixed in delimmatch 1.06a-5
has caused the Debian Bug report #965487,
regarding delimmatch: 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.)


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

Hi,

The package delimmatch 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: delimmatch
Source-Version: 1.06a-5
Done: Adrian Bunk 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Jan 2022 16:30:24 +0200
Source: delimmatch
Architecture: source
Version: 1.06a-5
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 965487
Changes:
 delimmatch (1.06a-5) unstable; urgency=low
 .
   * QA upload.
   * Set Maintainer to Debian QA Group. (see #945394)
   * debian/compat: 5 -> 7. (Closes: #965487)
Checksums-Sha1:
 545c7f4578f3f2d327f4e8777ba7b20129402e9f 1773 delimmatch_1.06a-5.dsc
 455dc24d7d3ef59dab8d262f15dc84e46ec30551 1944 delimmatch_1.06a-5.diff.gz
Checksums-Sha256:
 feb84309f734cb60b36cc723670c0bf09c65d4e888d40f8efacc1dc77ba06e2e 1773 
delimmatch_1.06a-5.dsc
 c856ce34903aa7674c697ecf0425f183c0360911eb828dbf8cef908c67fa14f5 1944 
delimmatch_1.06a-5.diff.gz
Files:
 3dc6face5f0bd25e3b135983f217cb74 1773 perl optional delimmatch_1.06a-5.dsc
 e311f71eb3fb333b7c6b37269ab5c718 1944 perl optional delimmatch_1.06a-5.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHoITkACgkQiNJCh6LY
mLHFLBAAyuBULj1hWshw0us+aYjfnUHdqRbfsoiN9/sXC0rbbWWricO1yDUdWmd9
OVBLy81b1arxT4X1gyBlUsqSSOJiQujyazWfQRCUwjkJD92Q/bBtFH2Pl9Y5PjsX
znkIOs2swOLKgiX2E1RslUK48vuqM8mN5U+ygwW3QuaZPCoEuftDw3AVYDsmto7J
8U6Xtqlxd3Srl+oOCv5H8m+cHDXpXWm+l/Djd0b4yiMFbPwgMY7sA6GUX0OA3nF2
ieSM/BuSNRac783MwS/o0TqpxslPYham7xPSFN8IrAOefGwMQuCC65v/7sn5uxQR
8YWn/fsbXyYsO/PsYCdALFqpcMRy3nC5SR2anV1TmG6Qu01J3de/+mcVxdz7PdET
+EtWKLfZBAAU8ZI2HNU3CbkdJLvD0Ol9d/tLVMQNOqNI3wMe7cJZr0aNLulb7gu1
e8RBMimedzibyQ9hVVSoFJ43G47uUzlqdh25GThzusaA3S8oMousO/M6kvyrchvj
XWeULB9j2QS+4wIbErlboqnaK8k/Xx47C12278GN/7tbu3rqIf0kJJLMuHASLsUB
+tbOt5YZjlhCd/InVcsBJgPLe6hx+Z1nBnYC0ywWvXR7mcwJn0ItQNGtGt5ZZYnS
+eEDTqPK7X2u3sCivIpWdICmv9WSuHyKV6Pr2ayUuD8A7JfNX/o=
=EYJt
-END PGP SIGNATURE End Message ---


Processed: covered: gplcver support should be dropped or gplcver adopted by the Electronics Team

2022-01-19 Thread Debian Bug Tracking System
Processing control commands:

> block 965565 by -1
Bug #965565 [src:gplcver] gplcver: Removal of obsolete debhelper compat 5 and 6 
in bookworm
965565 was not blocked by any bugs.
965565 was not blocking any bugs.
Added blocking bug(s) of 965565: 1004026

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



Bug#1004026: covered: gplcver support should be dropped or gplcver adopted by the Electronics Team

2022-01-19 Thread Adrian Bunk
Package: covered
Version: 0.7.10-3.1
Severity: serious
Control: block 965565 by -1

If gplcver provides any functionality not available in iverilog,
it would be useful if this orphaned package could be adopted by
the Electronics Team.

Otherwise, please drop gplcver support from covered.



Processed: tagging 1001760

2022-01-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 1001760 + bookworm sid
Bug #1001760 {Done: Jose Luis Rivero } [dart] FTBFS: 
'placeholders' is ambiguous
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

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



Bug#965491: dictconv: diff for NMU version 0.2-7.1

2022-01-19 Thread Adrian Bunk
Control: tags 581630 + patch
Control: tags 581630 + pending
Control: tags 965491 + patch
Control: tags 965491 + pending

Dear maintainer,

I've prepared an NMU for dictconv (versioned as 0.2-7.1) and uploaded
it to DELAYED/7. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -u dictconv-0.2/debian/control dictconv-0.2/debian/control
--- dictconv-0.2/debian/control
+++ dictconv-0.2/debian/control
@@ -11,7 +11,7 @@
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Recommends: dictzip
 Description: convert a dictionary file type in another dictionary file type
- Dictconv is a small program to convert a dictionay file type in another
+ Dictconv is a small program to convert a dictionary file type in another
  dictionary file type. Currently, it supports converting from Babylon
  glossaries, Freedict dictionaries, Sdictionary dictionaries and Stardict
  dictionaries to DICT dictionaries, plain text dictionaries and StarDict
diff -u dictconv-0.2/debian/changelog dictconv-0.2/debian/changelog
--- dictconv-0.2/debian/changelog
+++ dictconv-0.2/debian/changelog
@@ -1,3 +1,11 @@
+dictconv (0.2-7.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/compat: 5 -> 7. (Closes: #965491)
+  * Spelling fix in the package description. (Closes: #581630)
+
+ -- Adrian Bunk   Wed, 19 Jan 2022 16:23:08 +0200
+
 dictconv (0.2-7) unstable; urgency=low
 
   * debian/rules: added simple-patchsys include.
diff -u dictconv-0.2/debian/compat dictconv-0.2/debian/compat
--- dictconv-0.2/debian/compat
+++ dictconv-0.2/debian/compat
@@ -1 +1 @@
-5
+7


Processed: dictconv: diff for NMU version 0.2-7.1

2022-01-19 Thread Debian Bug Tracking System
Processing control commands:

> tags 581630 + patch
Bug #581630 [dictconv] dictconv: Minor spelling mistake in package description
Ignoring request to alter tags of bug #581630 to the same tags previously set
> tags 581630 + pending
Bug #581630 [dictconv] dictconv: Minor spelling mistake in package description
Ignoring request to alter tags of bug #581630 to the same tags previously set
> tags 965491 + patch
Bug #965491 [src:dictconv] dictconv: Removal of obsolete debhelper compat 5 and 
6 in bookworm
Ignoring request to alter tags of bug #965491 to the same tags previously set
> tags 965491 + pending
Bug #965491 [src:dictconv] dictconv: Removal of obsolete debhelper compat 5 and 
6 in bookworm
Ignoring request to alter tags of bug #965491 to the same tags previously set

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



Processed: dictconv: diff for NMU version 0.2-7.1

2022-01-19 Thread Debian Bug Tracking System
Processing control commands:

> tags 581630 + patch
Bug #581630 [dictconv] dictconv: Minor spelling mistake in package description
Added tag(s) patch.
> tags 581630 + pending
Bug #581630 [dictconv] dictconv: Minor spelling mistake in package description
Added tag(s) pending.
> tags 965491 + patch
Bug #965491 [src:dictconv] dictconv: Removal of obsolete debhelper compat 5 and 
6 in bookworm
Added tag(s) patch.
> tags 965491 + pending
Bug #965491 [src:dictconv] dictconv: Removal of obsolete debhelper compat 5 and 
6 in bookworm
Added tag(s) pending.

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



Bug#965458: chntpw: Removal of obsolete debhelper compat 5 and 6 in bookworm

2022-01-19 Thread Fabio Fantoni
Hi, in recent days I had prepared a git for chntpw, contacted the 
maintainer, then prepared the patches to convert to dh and compat 13 and 
also solve other few issues.


the maintainer is still active and he told me he would revise my 
changes, anyway thanks to Adrian Bunk for your pending patch/build that 
delayed remove from testing (in case the maintainer does not have time 
to review and do the new build)




OpenPGP_signature
Description: OpenPGP digital signature


Processed: opus-tools: diff for NMU version 0.1.10-1.1

2022-01-19 Thread Debian Bug Tracking System
Processing control commands:

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

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



Bug#965759: opus-tools: diff for NMU version 0.1.10-1.1

2022-01-19 Thread Adrian Bunk
Control: tags 965759 + patch
Control: tags 965759 + pending

Dear maintainer,

I've prepared an NMU for opus-tools (versioned as 0.1.10-1.1) and 
uploaded it to DELAYED/7. Please feel free to tell me if I should
cancel it.

cu
Adrian
diff -u opus-tools-0.1.10/debian/changelog opus-tools-0.1.10/debian/changelog
--- opus-tools-0.1.10/debian/changelog
+++ opus-tools-0.1.10/debian/changelog
@@ -1,3 +1,10 @@
+opus-tools (0.1.10-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/compat: 5 -> 7. (Closes: #965759)
+
+ -- Adrian Bunk   Wed, 19 Jan 2022 16:18:25 +0200
+
 opus-tools (0.1.10-1) unstable; urgency=medium
 
   * Improved handling of malformed input files to avoid crashes and other
diff -u opus-tools-0.1.10/debian/compat opus-tools-0.1.10/debian/compat
--- opus-tools-0.1.10/debian/compat
+++ opus-tools-0.1.10/debian/compat
@@ -1 +1 @@
-5
+7


Processed: gcc-h8300-hms: diff for NMU version 1:3.4.6+dfsg2-4.2

2022-01-19 Thread Debian Bug Tracking System
Processing control commands:

> tags 965538 + patch
Bug #965538 [src:gcc-h8300-hms] gcc-h8300-hms: Removal of obsolete debhelper 
compat 5 and 6 in bookworm
Added tag(s) patch.
> tags 965538 + pending
Bug #965538 [src:gcc-h8300-hms] gcc-h8300-hms: Removal of obsolete debhelper 
compat 5 and 6 in bookworm
Added tag(s) pending.

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



Bug#965538: gcc-h8300-hms: diff for NMU version 1:3.4.6+dfsg2-4.2

2022-01-19 Thread Adrian Bunk
Control: tags 965538 + patch
Control: tags 965538 + pending

Dear maintainer,

I've prepared an NMU for gcc-h8300-hms (versioned as 1:3.4.6+dfsg2-4.2) 
and uploaded it to DELAYED/7. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru gcc-h8300-hms-3.4.6+dfsg2/debian/changelog gcc-h8300-hms-3.4.6+dfsg2/debian/changelog
--- gcc-h8300-hms-3.4.6+dfsg2/debian/changelog	2019-12-17 01:36:24.0 +0200
+++ gcc-h8300-hms-3.4.6+dfsg2/debian/changelog	2022-01-19 16:12:47.0 +0200
@@ -1,3 +1,10 @@
+gcc-h8300-hms (1:3.4.6+dfsg2-4.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/compat: 5 -> 7. (Closes: #965538)
+
+ -- Adrian Bunk   Wed, 19 Jan 2022 16:12:47 +0200
+
 gcc-h8300-hms (1:3.4.6+dfsg2-4.1) unstable; urgency=medium
 
   [ Balint Reczey ]
diff -Nru gcc-h8300-hms-3.4.6+dfsg2/debian/compat gcc-h8300-hms-3.4.6+dfsg2/debian/compat
--- gcc-h8300-hms-3.4.6+dfsg2/debian/compat	2014-12-20 10:29:34.0 +0200
+++ gcc-h8300-hms-3.4.6+dfsg2/debian/compat	2022-01-19 16:12:37.0 +0200
@@ -1 +1 @@
-5
+7


Processed: tagging 1002657, tagging 1002658, tagging 1002940, tagging 1002941, tagging 1002942, tagging 1002983 ...

2022-01-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 1002657 + sid bookworm
Bug #1002657 [src:sks] FTBFS with OCaml 4.13.1
Added tag(s) bookworm and sid.
> tags 1002658 + sid bookworm
Bug #1002658 [src:xen] FTBFS with OCaml 4.13.1
Added tag(s) sid and bookworm.
> tags 1002940 + sid bookworm
Bug #1002940 [src:otags] FTBFS with ocaml-migrate-parsetree 2.3.0
Added tag(s) bookworm and sid.
> tags 1002941 + sid bookworm
Bug #1002941 [src:ppx-tools-versioned] FTBFS with ocaml-migrate-parsetree 2.3.0
Added tag(s) sid and bookworm.
> tags 1002942 + sid bookworm
Bug #1002942 [src:ppxfind] FTBFS with ocaml-migrate-parsetree 2.3.0
Added tag(s) bookworm and sid.
> tags 1002983 + sid bookworm
Bug #1002983 [src:hol-light] FTBFS with camlp5 8.00.02
Added tag(s) sid and bookworm.
> tags 1002979 + sid bookworm
Bug #1002979 [src:geneweb] FTBFS with camlp5 8.00.02
Added tag(s) sid and bookworm.
> notfixed 908054 1.9.5-1
Bug #908054 {Done: Ludovic Rousseau } [pcscd] pcscd 
fails to communicate with smartcard after resuming from suspend-to-RAM
No longer marked as fixed in versions pcscd/1.9.5-1.
> fixed 908054 1.9.5-1
Bug #908054 {Done: Ludovic Rousseau } [pcscd] pcscd 
fails to communicate with smartcard after resuming from suspend-to-RAM
Marked as fixed in versions pcsc-lite/1.9.5-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1002657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002657
1002658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002658
1002940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002940
1002941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002941
1002942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002942
1002979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002979
1002983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002983
908054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#965917: yorick-z: diff for NMU version 1.2.0+cvs20080115-5.1

2022-01-19 Thread Thibaut Paumard

Dear Adrian,

Thanks a lot.

I completely forgot to process these yorick-* updates after the release 
and missed the mail in December. I did the two most urgent a couple of 
days ago (reverse dependencies of Gyoto) and plan on processing the rest 
within the next week.


NMUs are very welcome! Most or all should be trivial.

Best regards, Thibaut.

Le 19/01/2022 à 12:02, Adrian Bunk a écrit :

Control: tags 965917 + patch
Control: tags 965917 + pending

Dear maintainer,

I've prepared an NMU for yorick-z (versioned as 1.2.0+cvs20080115-5.1)
and uploaded it to DELAYED/7. Please feel free to tell me if I should
cancel it.

cu
Adrian



--
* Dr Thibaut Paumard   | LESIA/CNRS - Table équatoriale (bât. 5)   *
* Tel: +33 1 45 07 78 35   | Observatoire de Paris - Section de Meudon *
* Fax: +33 1 45 07 79 17   | 5, Place Jules Janssen*
* thibaut.paum...@obspm.fr | 92195 MEUDON CEDEX (France)   *


smime.p7s
Description: Signature cryptographique S/MIME


Bug#1002988: Too early to fix

2022-01-19 Thread Julien Puydt
Hi,

upstream didn't release a new version with support for camlp5 8.* ; but
they have a patch here:
https://github.com/LPCIC/elpi/pull/110/commits/f58341831b56ccfe5f2f49158c600e4e36bcb9b5

so I should be able to fix the problem as soon as it actually occurs.

Cheers,

J.Puydt



Bug#1003962: Fails with --buildsystem=cmake if builddirectory contains package version with ~ tilde

2022-01-19 Thread Gregor Riepl
> I suspect the error is in /usr/share/dh-python/dhpython/build/plugin_cmake.py:
> 
> return ('dh_auto_build --buildsystem=cmake'
> ' --builddirectory="{build_dir}"'
> 
> If I replace "{build_dir}" by {build_dir} in that file, the build
> succeeds.

Is that safe?
What if the build_dir contains spaces or shell characters?

Perhaps the command should be single quoted instead, or the resulting
strings should be escaped.



Processed: Should forensics-extra drop the dependendency on smb-nat?

2022-01-19 Thread Debian Bug Tracking System
Processing control commands:

> block 1004018 by -1
Bug #1004018 [smb-nat] Is smb-nat still useful?
1004018 was not blocked by any bugs.
1004018 was not blocking any bugs.
Added blocking bug(s) of 1004018: 1004019

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



Bug#1004019: Should forensics-extra drop the dependendency on smb-nat?

2022-01-19 Thread Adrian Bunk
Package: forensics-extra
Version: 2.34
Severity: serious
Control: block 1004018 by -1

Does the 25 year old smb-nat provide any functionality that is
not also provided by Samba tools (that were originally written
by the same author)?



Bug#1004018: Is smb-nat still useful?

2022-01-19 Thread Adrian Bunk
Package: smb-nat
Version: 1:1.0-6
Severity: serious
Tags: bookworm sid

Does smb-nat provide any functionality that is not also provided
by Samba tools (that were originally written by the same author)?



Processed: severity of 1002634 is serious, severity of 1002607 is serious, severity of 1002608 is serious ...

2022-01-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 1002634 serious
Bug #1002634 [src:libguestfs] FTBFS with OCaml 4.13.1
Severity set to 'serious' from 'important'
> severity 1002607 serious
Bug #1002607 [src:llvm-toolchain-11] Build-Conflicts with ocaml
Severity set to 'serious' from 'important'
> severity 1002608 serious
Bug #1002608 [src:llvm-toolchain-12] Build-Conflicts with ocaml
Severity set to 'serious' from 'important'
> severity 1002609 serious
Bug #1002609 [src:llvm-toolchain-13] Build-Conflicts with ocaml
Severity set to 'serious' from 'important'
> severity 1002657 serious
Bug #1002657 [src:sks] FTBFS with OCaml 4.13.1
Severity set to 'serious' from 'important'
> severity 1002658 serious
Bug #1002658 [src:xen] FTBFS with OCaml 4.13.1
Severity set to 'serious' from 'important'
> severity 1002940 serious
Bug #1002940 [src:otags] FTBFS with ocaml-migrate-parsetree 2.3.0
Severity set to 'serious' from 'important'
> severity 1002941 serious
Bug #1002941 [src:ppx-tools-versioned] FTBFS with ocaml-migrate-parsetree 2.3.0
Severity set to 'serious' from 'important'
> severity 1002942 serious
Bug #1002942 [src:ppxfind] FTBFS with ocaml-migrate-parsetree 2.3.0
Severity set to 'serious' from 'important'
> severity 1002979 serious
Bug #1002979 [src:geneweb] FTBFS with camlp5 8.00.02
Severity set to 'serious' from 'important'
> severity 1002983 serious
Bug #1002983 [src:hol-light] FTBFS with camlp5 8.00.02
Severity set to 'serious' from 'important'
> severity 1002984 serious
Bug #1002984 [src:mlpost] FTBFS with ocaml-migrate-parsetree 2.3.0
Severity set to 'serious' from 'important'
> severity 1002988 serious
Bug #1002988 [src:elpi] FTBFS with camlp5 8.00.02
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1002607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002607
1002608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002608
1002609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002609
1002634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002634
1002657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002657
1002658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002658
1002940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002940
1002941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002941
1002942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002942
1002979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002979
1002983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002983
1002984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002984
1002988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#885140: [pkg-wicd-maint] Bug#885140: wicd: Depends on unmaintained pygtk

2022-01-19 Thread Vincent Lefevre
On 2022-01-19 05:43:15 +0100, Sebastian Rasmussen wrote:
> Sadly it appears no one has stepped up to do the porting in the four years
> since 2017. As a user of wicd-curses, can I humbly suggest that Debian
> disables wicd-gtk for the time being so that Debian/testing mapped to
> bookworm can continue using wicd?
> 
> I'm slightly worried by this comment though:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885140#77

There are also other issues.

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

is rather annoying for networks with several access points.

> If wicd-curses is kicked out of Debian entirely, what is the suggested
> alternative for scanning, connecting to and disconnecting from Wi-Fi
> in a terminal?

Due to the various wicd issues, I've switched to nmcli, e.g.

  nmcli device wifi rescan
  nmcli device wifi list
  nmcli device wifi connect ...
  nmcli device disconnect ...

There are completions for bash and zsh.

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



Bug#1004013: python3-typedload-doc: missing Breaks+Replaces: python3-typedload (<< 2.15)

2022-01-19 Thread Andreas Beckmann
Package: python3-typedload-doc
Version: 2.15-2
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 .../python3-typedload-doc_2.15-2_all.deb ...
  Unpacking python3-typedload-doc (2.15-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-typedload-doc_2.15-2_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/python3-typedload/docs/CHANGELOG.md.gz', 
which is also in package python3-typedload 2.14-2
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-typedload-doc_2.15-2_all.deb

The exisiting
  Breaks+Replaces: python3-typedload (<< 2.5)
are insufficiently versioned.


cheers,

Andreas


python3-typedload=2.14-2_python3-typedload-doc=2.15-2.log.gz
Description: application/gzip


Bug#965916: yorick-cubeview: diff for NMU version 2.2-2.2

2022-01-19 Thread Adrian Bunk
Control: tags 965916 + patch
Control: tags 965916 + pending

Dear maintainer,

I've prepared an NMU for yorick-cubeview (versioned as 2.2-2.2) and 
uploaded it to DELAYED/7. Please feel free to tell me if I should
cancel it.

cu
Adrian
diff -Nru yorick-cubeview-2.2/debian/changelog yorick-cubeview-2.2/debian/changelog
--- yorick-cubeview-2.2/debian/changelog	2021-01-03 13:25:53.0 +0200
+++ yorick-cubeview-2.2/debian/changelog	2022-01-19 13:03:55.0 +0200
@@ -1,3 +1,10 @@
+yorick-cubeview (2.2-2.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/compat: 5 -> 7. (Closes: #965916)
+
+ -- Adrian Bunk   Wed, 19 Jan 2022 13:03:55 +0200
+
 yorick-cubeview (2.2-2.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -Nru yorick-cubeview-2.2/debian/compat yorick-cubeview-2.2/debian/compat
--- yorick-cubeview-2.2/debian/compat	2013-07-28 15:48:29.0 +0300
+++ yorick-cubeview-2.2/debian/compat	2022-01-19 13:03:55.0 +0200
@@ -1 +1 @@
-5
+7


Processed: yorick-cubeview: diff for NMU version 2.2-2.2

2022-01-19 Thread Debian Bug Tracking System
Processing control commands:

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

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



Processed: yorick-z: diff for NMU version 1.2.0+cvs20080115-5.1

2022-01-19 Thread Debian Bug Tracking System
Processing control commands:

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

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



Bug#965917: yorick-z: diff for NMU version 1.2.0+cvs20080115-5.1

2022-01-19 Thread Adrian Bunk
Control: tags 965917 + patch
Control: tags 965917 + pending

Dear maintainer,

I've prepared an NMU for yorick-z (versioned as 1.2.0+cvs20080115-5.1) 
and uploaded it to DELAYED/7. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru yorick-z-1.2.0+cvs20080115/debian/changelog yorick-z-1.2.0+cvs20080115/debian/changelog
--- yorick-z-1.2.0+cvs20080115/debian/changelog	2012-06-28 14:30:43.0 +0300
+++ yorick-z-1.2.0+cvs20080115/debian/changelog	2022-01-19 12:59:55.0 +0200
@@ -1,3 +1,10 @@
+yorick-z (1.2.0+cvs20080115-5.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/compat: 5 -> 7. (Closes: #965917)
+
+ -- Adrian Bunk   Wed, 19 Jan 2022 12:59:55 +0200
+
 yorick-z (1.2.0+cvs20080115-5) unstable; urgency=low
 
   * Comply with Debian Science Policy
diff -Nru yorick-z-1.2.0+cvs20080115/debian/compat yorick-z-1.2.0+cvs20080115/debian/compat
--- yorick-z-1.2.0+cvs20080115/debian/compat	2012-06-28 12:51:22.0 +0300
+++ yorick-z-1.2.0+cvs20080115/debian/compat	2022-01-19 12:59:55.0 +0200
@@ -1 +1 @@
-5
+7


Bug#965458: chntpw: diff for NMU version 1.0-1.2

2022-01-19 Thread Adrian Bunk
Control: tags 965458 + patch
Control: tags 965458 + pending

Dear maintainer,

I've prepared an NMU for chntpw (versioned as 1.0-1.2) and uploaded
it to DELAYED/7. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -u chntpw-1.0/debian/changelog chntpw-1.0/debian/changelog
--- chntpw-1.0/debian/changelog
+++ chntpw-1.0/debian/changelog
@@ -1,3 +1,10 @@
+chntpw (1.0-1.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/compat: 5 -> 7. (Closes: #965458)
+
+ -- Adrian Bunk   Wed, 19 Jan 2022 12:46:45 +0200
+
 chntpw (1.0-1.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -u chntpw-1.0/debian/compat chntpw-1.0/debian/compat
--- chntpw-1.0/debian/compat
+++ chntpw-1.0/debian/compat
@@ -1 +1 @@
-5
+7


Processed: chntpw: diff for NMU version 1.0-1.2

2022-01-19 Thread Debian Bug Tracking System
Processing control commands:

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

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



Bug#965900: xfsdump: diff for NMU version 3.1.9+0+nmu2

2022-01-19 Thread Adrian Bunk
Control: tags 965900 + patch
Control: tags 965900 + pending

Dear maintainer,

I've prepared an NMU for xfsdump (versioned as 3.1.9+0+nmu2) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should cancel it.

cu
Adrian
diff -Nru xfsdump-3.1.9+0+nmu1/debian/changelog xfsdump-3.1.9+0+nmu2/debian/changelog
--- xfsdump-3.1.9+0+nmu1/debian/changelog	2021-12-16 10:44:12.0 +0200
+++ xfsdump-3.1.9+0+nmu2/debian/changelog	2022-01-19 12:22:32.0 +0200
@@ -1,3 +1,10 @@
+xfsdump (3.1.9+0+nmu2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/compat: 5 -> 7. (Closes: #965900)
+
+ -- Adrian Bunk   Wed, 19 Jan 2022 12:22:32 +0200
+
 xfsdump (3.1.9+0+nmu1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru xfsdump-3.1.9+0+nmu1/debian/compat xfsdump-3.1.9+0+nmu2/debian/compat
--- xfsdump-3.1.9+0+nmu1/debian/compat	2020-01-31 19:30:58.0 +0200
+++ xfsdump-3.1.9+0+nmu2/debian/compat	2022-01-19 12:22:27.0 +0200
@@ -1 +1 @@
-5
+7


Processed: xfsdump: diff for NMU version 3.1.9+0+nmu2

2022-01-19 Thread Debian Bug Tracking System
Processing control commands:

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

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



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

2022-01-19 Thread Georg Faerber
Hi Utkarsh,

Thanks for your upload.

Could you please push the changes you did to the git repo?

Thanks,
cheers,
Georg



Processed: bug 1001225 is forwarded to https://github.com/tmate-io/tmate-ssh-server/issues/95

2022-01-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 1001225 https://github.com/tmate-io/tmate-ssh-server/issues/95
Bug #1001225 [src:tmate-ssh-server] tmate-ssh-server: CVE-2021-44512 
CVE-2021-44513
Set Bug forwarded-to-address to 
'https://github.com/tmate-io/tmate-ssh-server/issues/95'.
> thanks
Stopping processing here.

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



Bug#998583: marked as done (orc: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "disable_gtkdoc, disable_tests")

2022-01-19 Thread Debian Bug Tracking System
Your message dated Wed, 19 Jan 2022 10:19:48 +
with message-id 
and subject line Bug#998583: fixed in orc 1:0.4.32-2
has caused the Debian Bug report #998583,
regarding orc: FTBFS: ../meson.build:1:0: ERROR: Unknown options: 
"disable_gtkdoc, disable_tests"
to be marked as done.

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

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


-- 
998583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: orc
Version: 1:0.4.32-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 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 '/<>'
> if test -r /proc/cpuinfo; then \
>   cat /proc/cpuinfo; \
> fi
> processor : 0
> vendor_id : GenuineIntel
> cpu family: 6
> model : 85
> model name: Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz
> stepping  : 7
> microcode : 0x5003005
> cpu MHz   : 3102.019
> cache size: 36608 KB
> physical id   : 0
> siblings  : 4
> core id   : 0
> cpu cores : 2
> apicid: 0
> initial apicid: 0
> fpu   : yes
> fpu_exception : yes
> cpuid level   : 13
> wp: yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
> pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm 
> constant_tsc rep_good nopl xtopology nonstop_tsc cpuid aperfmperf 
> tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe 
> popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 
> 3dnowprefetch invpcid_single pti fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms 
> invpcid mpx avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd 
> avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves ida arat pku ospke
> bugs  : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
> swapgs itlb_multihit
> bogomips  : 4999.98
> clflush size  : 64
> cache_alignment   : 64
> address sizes : 46 bits physical, 48 bits virtual
> power management:
> 
> processor : 1
> vendor_id : GenuineIntel
> cpu family: 6
> model : 85
> model name: Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz
> stepping  : 7
> microcode : 0x5003005
> cpu MHz   : 3106.629
> cache size: 36608 KB
> physical id   : 0
> siblings  : 4
> core id   : 1
> cpu cores : 2
> apicid: 2
> initial apicid: 2
> fpu   : yes
> fpu_exception : yes
> cpuid level   : 13
> wp: yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
> pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm 
> constant_tsc rep_good nopl xtopology nonstop_tsc cpuid aperfmperf 
> tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe 
> popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 
> 3dnowprefetch invpcid_single pti fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms 
> invpcid mpx avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd 
> avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves ida arat pku ospke
> bugs  : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
> swapgs itlb_multihit
> bogomips  : 4999.98
> clflush size  : 64
> cache_alignment   : 64
> address sizes : 46 bits physical, 48 bits virtual
> power management:
> 
> processor : 2
> vendor_id : GenuineIntel
> cpu family: 6
> model : 85
> model name: Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz
> stepping  : 7
> microcode : 0x5003005
> cpu MHz   : 3102.941
> cache size: 36608 KB
> physical id   : 0
> siblings  : 4
> core id   : 0
> cpu cores : 2
> apicid: 1
> initial apicid: 1
> fpu   : yes
> fpu_exception : yes
> cpuid level   : 13
> wp: yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
> pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm 
> constant_tsc rep_good nopl xtopology nonstop_tsc cpuid aperfmperf 
> tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe 
> popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 
> 3dnowprefetch invpcid_single pti fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms 
> invpcid mpx avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd 
> avx512bw 

Bug#998383: marked as done (gstreamer1.0-qt5 should again be built on armel/armhf)

2022-01-19 Thread Debian Bug Tracking System
Your message dated Wed, 19 Jan 2022 10:19:02 +
with message-id 
and subject line Bug#998383: fixed in gst-plugins-good1.0 1.18.5-2
has caused the Debian Bug report #998383,
regarding gstreamer1.0-qt5 should again be built on armel/armhf
to be marked as done.

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

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


-- 
998383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998383
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nheko
Version: 0.8.2-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

nheko fails to migrate to testing since it depends on gstreamer1.0-qt5.
This package is not available on armel and armhf.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: gst-plugins-good1.0
Source-Version: 1.18.5-2
Done: Sebastian Dröge 

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

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

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

Debian distribution maintenance software
pp.
Sebastian Dröge  (supplier of updated gst-plugins-good1.0 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Jan 2022 11:55:09 +0200
Source: gst-plugins-good1.0
Architecture: source
Version: 1.18.5-2
Distribution: unstable
Urgency: medium
Maintainer: Maintainers of GStreamer packages 

Changed-By: Sebastian Dröge 
Closes: 998210 998383
Changes:
 gst-plugins-good1.0 (1.18.5-2) unstable; urgency=medium
 .
   [ Adrian Bunk ]
   * debian/rules,
 debian/control:
 + With #894076 fixed, gstreamer1.0-qt5 builds again on armel/armhf 
(Closes: #998383).
 .
   [ Samuel Thibault ]
   * debian/control:
 + Build Qt5/Wayland support only on Linux (Closes: #998210).
 .
   [ Sebastian Dröge ]
   * Upload to unstable.
Checksums-Sha1:
 b7c75a037f81b5738bf349d18e0429c7341cbd87 3572 gst-plugins-good1.0_1.18.5-2.dsc
 9db4d1d1cc9f6b631a0d22b380fce3fcaf189eaa 34408 
gst-plugins-good1.0_1.18.5-2.debian.tar.xz
 c35e921f2f7f76c7edaa36844a1eb70e2556984c 21266 
gst-plugins-good1.0_1.18.5-2_amd64.buildinfo
Checksums-Sha256:
 c25635a9110210c8ca74f2a72f831be7ce03b64395b6cdb3d77f0a2489a2bbbe 3572 
gst-plugins-good1.0_1.18.5-2.dsc
 fa7062b9aca2ef55f57deed1a996783dc3e12d1f42bd631c06e3c4b8c5db60a1 34408 
gst-plugins-good1.0_1.18.5-2.debian.tar.xz
 f48046b4eca7f0fafdd9935b4b367626a99aaec70049656148fff56a8e3a3695 21266 
gst-plugins-good1.0_1.18.5-2_amd64.buildinfo
Files:
 a75e407eec5feb545f513aba09ce33f9 3572 libs optional 
gst-plugins-good1.0_1.18.5-2.dsc
 c1e5e46d7fec2632e44393741c9e50c1 34408 libs optional 
gst-plugins-good1.0_1.18.5-2.debian.tar.xz
 64585fa1f72dac54a2d66208c1719ca3 21266 libs optional 
gst-plugins-good1.0_1.18.5-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEEf0vHzDygb5cza7/rBmjMFIbC17UFAmHn4wZfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDdG
NEJDN0NDM0NBMDZGOTczMzZCQkZFQjA2NjhDQzE0ODZDMkQ3QjUSHHNsb21vQGNv
YXhpb24ubmV0AAoJEAZozBSGwte1vh0QAKC5CTxdfF2gS05Ddk5g+APn4wafhIcG
+QMGaPuRt39o+yAnSjDzBo8Tje+tDeHKtWlvUPScCiDh6enG4QQ5DSYoKvbA5OWk
bpa7X2iEyK9X9TEuB3zqafkwKiFBNy1x7Oy41RtKXnH+tN5zyMhuJ3XqwAUc1vNE
hmsWbqHTL93eDhORWZUaq5PGbtyYgBdiYgRKCQV6LffdZAAF1823LjYoVJ4KBrNZ
FgkADC+omw7Zm9Er4HeIyRwY5TnByk0senPFrDvEnHFZzcYxB3KvzN88Kh3t0Q2P
f35NBW3rgp4xEMHJNCPDHNcIPTjoM725Fxtb1IpadgBuCRoAVtQEVKY3M7yUE69S
3VIC4rb7FJmzaeiyaiRBr9RBqoTpTdViy2nkBzIUMvxgmvqjb+qmRUKF5j9ZNTfd
eN837Gm6aKprUi1npsOX2JriYCxD82qtOz8+xTuCP6p7j5HBN6d5LhdhXW8jAqbF
y75JdTHpOeN2X/6BssaE3dN56cFcHmEOlRg/HHZRcEOmUX5m6uB0bpzsRlptaVrM
6tX1jVUj07GADImEi4T1YRGHIc8cdWqmRQ5TCvJu0/6T647N7HC9Cw8rGUP6Sn+N
X0hUu9ZbPkVyKtvTFOLVBMaHzrt5BBIh15/EiQkcykq4XfF/ZBv8NJL0274LEbku
DlOFu5K2kIqH
=Q8wF
-END PGP SIGNATURE End Message ---


Processed: block 999291 with 965900

2022-01-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> block 999291 with 965900
Bug #999291 {Done: Damyan Ivanov } [src:xfsdump] xfsdump: 
missing required debian/rules targets build-arch and/or build-indep
999291 was not blocked by any bugs.
999291 was not blocking any bugs.
Added blocking bug(s) of 999291: 965900
> thanks
Stopping processing here.

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



Bug#1003907: fails to successfully associate

2022-01-19 Thread Michael Biebl

Am 18.01.22 um 21:56 schrieb Andrej Shadura:

Hi Michael,

On Tue, 18 Jan 2022, at 21:52, Michael Biebl wrote:

Am 18.01.22 um 21:47 schrieb Masashi Honma:

The log indicates that the Wi-Fi access point rejected the association
request from the Wi-Fi station with status
code=WLAN_STATUS_INVALID_IE.

We can't read from this log why the Wi-Fi access point rejected the
assocication request.
If I have that Wi-Fi access point on hand, I can bisect this issue.
What is the Wi-Fi access point you are using?



It's a FRITZ!Box 7490 (a very common Wi-Fi Router in Germany) running
Firmware version 07.39.
WPA-Mode is set to WPA2+WPA3


Just a random thought: could you please try those two versions formerly from 
experimental:
  * 2:2.9.0+git20200517+dd2daf0-1
  * 2:2.9.0+git20210909+a75fdcd-1

I have re-enabled some options (WNM, MBO, FILS and mesh networking) in the 
latter, I wonder if that could have some effect.




I tried the various versions from snapshots.d.o

2:2.9.0-23 - works
2:2.9.0+git20200221+f65da0c-1 - works
2:2.9.0+git20200517+dd2daf0-1 - doesn't work
2:2.9.0+git20210909+a75fdcd-1 - doesn't work
2:2.9.0+git20211018+2e122945fa53-1 - doesn't work
2:2.9.0+git2026+0b853303ae31-1 - doesn't work
2:2.10-1 - doesn't work


I then went on and disabled WPA2+WPA3 mode on the Wi-Fi router and set 
it to WPA2 (CCMP).


After that, the connection was established successfully with 2.10.

If I remember correctly, my hardware doesn't support WPA3, but since I 
enabled support for both WPA2+WPA3, it should fall back to WPA2.


Obviously I'd like to keep WPA3 enabled for newer clients.

Regards,
Michael





OpenPGP_signature
Description: OpenPGP digital signature


Bug#1003964: pandoc doesn't start: error while loading shared libraries: libcmark-gfm.so.0.29.0.gfm.0

2022-01-19 Thread Sebastian Ramacher
On 2022-01-18 19:30:39 +0100, Jonas Smedegaard wrote:
> Control: clone -1 -2
> Control: reassign -1 src:cmark-gfm 0.29.0.gfm.2-1
> Control: retitle -1 cmark-gfm: shlibs too relaxed for unstable ABI
> Control: affects -1 pandoc blogliterately gitit pandoc-citeproc patat
> Control: reassign -2 src:cmark 0.30.2-3
> Control: severity -2 important
> Control: retitle -2 cmark: shlibs too relaxed for unstable ABI
> 
> Quoting Jonas Smedegaard (2022-01-18 18:40:33)
> > Quoting gregor herrmann (2022-01-18 18:08:02)
> > > While looking at some test issues in libpod-pandoc-perl, I noticed
> > > that pandoc looks quite broken in current amd64/sid:
> > > 
> > > % pandoc --version
> > > pandoc: error while loading shared libraries: 
> > > libcmark-gfm.so.0.29.0.gfm.0: cannot open shared object file: No such 
> > > file or directory
> > [...]
> > > So it looks like pandoc wants libcmark-gfm.so.0.29.0.gfm.0 but 
> > > libcmark-gfm0 ships libcmark-gfm.so.0.29.0.gfm.2. Maybe this is an 
> > > issue in libcmark-gfm0 … Not sure where to fix this.
> > 
> > libcmark-gfm offers an unstable API, so I guess pandoc packaging is to 
> > blame for having too loose dependency on that inherently untameable 
> > library package.
> > 
> > Thanks for reporting, Gregor - might be enough to request a binNMU but 
> > I'd better tighten that dependency, so will do a regular upload.
> 
> Hmm - thinking on it, it seems to me that the change really should be in 
> the libcmark-gfm package - something like this (untested):
> 
> override_dh_makeshlibs:
>   dh_makeshlibs --version-info="libcmark-gfm0 (>= ${DEB_VERSION}), 
> libcmark-gfm0 (<< ${DEB_VERSION}+)"

No, please review Section 8 of the policy.

The SONAME is:

$ objdump -x libcmark-gfm.so.0.29.0.gfm.2 | grep SONAME
  SONAME   libcmark-gfm.so.0.29.0.gfm.2

So the package needs to be named libcmark-gfm0.29.0.gfm.2.

Cheers

> 
> Similar is required for the package cmark.
> 
> 
>  - Jonas
> 
> -- 
>  * Jonas Smedegaard - idealist & Internet-arkitekt
>  * Tlf.: +45 40843136  Website: http://dr.jones.dk/
> 
>  [x] quote me freely  [ ] ask before reusing  [ ] keep private



-- 
Sebastian Ramacher


signature.asc
Description: PGP signature


Bug#1002785: marked as done (pd-mediasettings: FTBFS: audiosettings.c:210:16: error: redefinition of ‘struct _audiosettings’)

2022-01-19 Thread Debian Bug Tracking System
Your message dated Wed, 19 Jan 2022 08:36:38 +
with message-id 
and subject line Bug#1002785: fixed in pd-mediasettings 0.1.2-1
has caused the Debian Bug report #1002785,
regarding pd-mediasettings: FTBFS: audiosettings.c:210:16: error: redefinition 
of ‘struct _audiosettings’
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.)


-- 
1002785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-mediasettings
Version: 0.1.1-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211228 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -DVERSION='"0.1.1"' -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -o midisettings.o -c midisettings.c
> In file included from midisettings.c:17:
> mediasettings.h: In function ‘mediasettings_boilerplate’:
> In file included from audiosettings.c:17:
> mediasettings.h: In function ‘mediasettings_boilerplate’:
> mediasettings.h:110:34: warning: macro "__DATE__" might prevent reproducible 
> builds [-Wdate-time]
>   110 |   verbose(0,"  compiled "BUILD_DATE"");
>   |  ^~
> mediasettings.h:110:34: warning: macro "__DATE__" might prevent reproducible 
> builds [-Wdate-time]
>   110 |   verbose(0,"  compiled "BUILD_DATE"");
>   |  ^~
> mediasettings.h:27:27: warning: macro "__TIME__" might prevent reproducible 
> builds [-Wdate-time]
>27 | # define BUILD_DATE "on " __DATE__ " at " __TIME__
>   |   ^~~~
> mediasettings.h:110:34: note: in expansion of macro ‘BUILD_DATE’
>   110 |   verbose(0,"  compiled "BUILD_DATE"");
>   |  ^~
> mediasettings.h:27:27: warning: macro "__TIME__" might prevent reproducible 
> builds [-Wdate-time]
>27 | # define BUILD_DATE "on " __DATE__ " at " __TIME__
>   |   ^~~~
> mediasettings.h:110:34: note: in expansion of macro ‘BUILD_DATE’
>   110 |   verbose(0,"  compiled "BUILD_DATE"");
>   |  ^~
> midisettings.c: In function ‘ms_symkeys_add’:
> audiosettings.c: In function ‘as_get_audio_params’:
> midisettings.c:97:2: warning: #warning LATER check how to deal with multiple 
> devices of the same name! [-Wcpp]
>97 | #warning LATER check how to deal with multiple devices of the same 
> name!
>   |  ^~~
> audiosettings.c:31:3: warning: implicit declaration of function 
> ‘sys_get_audio_params’; did you mean ‘as_get_audio_params’? 
> [-Wimplicit-function-declaration]
>31 |   sys_get_audio_params(pnaudioindev , paudioindev , pchindev,
>   |   ^~~~
>   |   as_get_audio_params
> audiosettings.c: At top level:
> audiosettings.c:210:16: error: redefinition of ‘struct _audiosettings’
>   210 | typedef struct _audiosettings
>   |^~
> In file included from mediasettings.h:18,
>  from audiosettings.c:17:
> /usr/include/pd/s_stuff.h:61:16: note: originally defined here
>61 | typedef struct _audiosettings
>   |^~
> audiosettings.c:217:3: error: conflicting types for ‘t_audiosettings’; have 
> ‘struct _audiosettings’
>   217 | } t_audiosettings;
>   |   ^~~
> In file included from mediasettings.h:18,
>  from audiosettings.c:17:
> /usr/include/pd/s_stuff.h:76:3: note: previous declaration of 
> ‘t_audiosettings’ with type ‘t_audiosettings’ {aka ‘struct _audiosettings’}
>76 | } t_audiosettings;
>   |   ^~~
> audiosettings.c: In function ‘audiosettings_listdevices’:
> audiosettings.c:230:3: error: too few arguments to function 
> ‘sys_get_audio_devs’
>   230 |   sys_get_audio_devs((char*)indevlist, ,
>   |   ^~
> In file included from mediasettings.h:18,
>  from audiosettings.c:17:
> /usr/include/pd/s_stuff.h:163:13: note: declared here
>   163 | EXTERN void sys_get_audio_devs(char *indevlist, int *nindevs,
>   | ^~
> midisettings.c: In function ‘midisettings_listdevices_devices’:
> midisettings.c:325:18: warning: assignment discards ‘const’ qualifier from 
> pointer target type 

Bug#1002188: re: resvg: FTBFS: unsatisfiable build-dependencies

2022-01-19 Thread Andrej Shadura

Hi,

On Wed, 29 Dec 2021 05:24:03 + peter green  wrote:

The parts of the rust gtk stack used by resvg are now installable again after 
having been broken for some time,
so I decided to take a look and see if I could get

The first thing I did was change the dependency on pico-args to 0.4 so that I 
could attempt a build.

I then discovered that the dependenices in Cargo.toml were often more 
restrictive than those in the
Debian package, I relaxed these.

Unfortunately I then discovered that the API of the cairo crate seems to have 
changed quite substantially,
I started trying to port it but quickly reached the point where I was not 
confident either that
my changes would work correctly or that patching was the right approach.

When I look at resvg upstream, the cairo code seems to have disappeared from 
the repository.

Work in progress debdiff attatched, do with it as you see fit.


Thanks Peter. I have some work in progress packaging of a newer upstream 
version, but it’s been stuck for some time for lack of time and build 
dependencies.


--
Cheers,
  Andrej



Processed: Bug#1002785 marked as pending in pd-mediasettings

2022-01-19 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1002785 [src:pd-mediasettings] pd-mediasettings: FTBFS: 
audiosettings.c:210:16: error: redefinition of ‘struct _audiosettings’
Added tag(s) pending.

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



Bug#1002785: marked as pending in pd-mediasettings

2022-01-19 Thread IOhannes zmölnig
Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/pd/pd-mediasettings/-/commit/33d1c1131548e30fa7ac29155fe28f3383965065


Versioned (Build-)Depends on Pd>=0.52

Closes: #1002785


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1002785