Bug#980609: missing i386-cpuinfo.h

[Simon Ruderich]

Hello,

the attached patch works for me as workaround for Bullseye. It adds the
missing file and updates the #include path to it. Apply it with

cd / && patch -p1 < /path/to/patch

With the patch I can successfully build kernels which use GCC
plugins on Bullseye.

Is it possible to apply a similar patch to the official gcc
package distributed in Bullseye? Having to patch the systems
manually isn't optimal.

Regards
Simon
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9
Workaround for https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980609, based
on pr95842.diff

Apply with cd / && patch -p1 < /path/to/patch

--- a/usr/lib/gcc/x86_64-linux-gnu/10/plugin/include/config/i386/i386.h.orig	2021-01-10 12:35:39.0 +0100
+++ b/usr/lib/gcc/x86_64-linux-gnu/10/plugin/include/config/i386/i386.h	2022-01-23 10:22:59.579197064 +0100
@@ -2497,7 +2497,7 @@
 
 #include "insn-attr-common.h"
 
-#include "common/config/i386/i386-cpuinfo.h"
+#include "config/i386/i386-cpuinfo.h"
 
 class pta
 {
--- /dev/null
+++ b/usr/lib/gcc/x86_64-linux-gnu/10/plugin/include/config/i386/i386-cpuinfo.h
@@ -0,0 +1,134 @@
+/* Get CPU type and Features for x86 processors.
+   Copyright (C) 2012-2020 Free Software Foundation, Inc.
+   Contributed by Sriraman Tallam (tmsri...@google.com)
+
+This file is part of GCC.
+
+GCC is free software; you can redistribute it and/or modify it under
+the terms of the GNU General Public License as published by the Free
+Software Foundation; either version 3, or (at your option) any later
+version.
+
+GCC is distributed in the hope that it will be useful, but WITHOUT ANY
+WARRANTY; without even the implied warranty of MERCHANTABILITY or
+FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
+for more details.
+
+Under Section 7 of GPL version 3, you are granted additional
+permissions described in the GCC Runtime Library Exception, version
+3.1, as published by the Free Software Foundation.
+
+You should have received a copy of the GNU General Public License and
+a copy of the GCC Runtime Library Exception along with this program;
+see the files COPYING3 and COPYING.RUNTIME respectively.  If not, see
+.  */
+
+/* Processor Vendor and Models. */
+
+enum processor_vendor
+{
+  VENDOR_INTEL = 1,
+  VENDOR_AMD,
+  VENDOR_OTHER,
+  BUILTIN_VENDOR_MAX = VENDOR_OTHER,
+  VENDOR_MAX
+};
+
+/* Any new types or subtypes have to be inserted at the end. */
+
+enum processor_types
+{
+  INTEL_BONNELL = 1,
+  INTEL_CORE2,
+  INTEL_COREI7,
+  AMDFAM10H,
+  AMDFAM15H,
+  INTEL_SILVERMONT,
+  INTEL_KNL,
+  AMD_BTVER1,
+  AMD_BTVER2,
+  AMDFAM17H,
+  INTEL_KNM,
+  INTEL_GOLDMONT,
+  INTEL_GOLDMONT_PLUS,
+  INTEL_TREMONT,
+  CPU_TYPE_MAX,
+  BUILTIN_CPU_TYPE_MAX = CPU_TYPE_MAX
+};
+
+enum processor_subtypes
+{
+  INTEL_COREI7_NEHALEM = 1,
+  INTEL_COREI7_WESTMERE,
+  INTEL_COREI7_SANDYBRIDGE,
+  AMDFAM10H_BARCELONA,
+  AMDFAM10H_SHANGHAI,
+  AMDFAM10H_ISTANBUL,
+  AMDFAM15H_BDVER1,
+  AMDFAM15H_BDVER2,
+  AMDFAM15H_BDVER3,
+  AMDFAM15H_BDVER4,
+  AMDFAM17H_ZNVER1,
+  INTEL_COREI7_IVYBRIDGE,
+  INTEL_COREI7_HASWELL,
+  INTEL_COREI7_BROADWELL,
+  INTEL_COREI7_SKYLAKE,
+  INTEL_COREI7_SKYLAKE_AVX512,
+  INTEL_COREI7_CANNONLAKE,
+  INTEL_COREI7_ICELAKE_CLIENT,
+  INTEL_COREI7_ICELAKE_SERVER,
+  AMDFAM17H_ZNVER2,
+  INTEL_COREI7_CASCADELAKE,
+  INTEL_COREI7_TIGERLAKE,
+  INTEL_COREI7_COOPERLAKE,
+  CPU_SUBTYPE_MAX
+};
+
+/* Priority of i386 features, greater value is higher priority.   This is
+   used to decide the order in which function dispatch must happen.  For
+   instance, a version specialized for SSE4.2 should be checked for dispatch
+   before a version for SSE3, as SSE4.2 implies SSE3.  */
+enum feature_priority
+{
+  P_NONE = 0,
+  P_MMX,
+  P_SSE,
+  P_SSE2,
+  P_SSE3,
+  P_SSSE3,
+  P_PROC_SSSE3,
+  P_SSE4_A,
+  P_PROC_SSE4_A,
+  P_SSE4_1,
+  P_SSE4_2,
+  P_PROC_SSE4_2,
+  P_POPCNT,
+  P_AES,
+  P_PCLMUL,
+  P_AVX,
+  P_PROC_AVX,
+  P_BMI,
+  P_PROC_BMI,
+  P_FMA4,
+  P_XOP,
+  P_PROC_XOP,
+  P_FMA,
+  P_PROC_FMA,
+  P_BMI2,
+  P_AVX2,
+  P_PROC_AVX2,
+  P_AVX512F,
+  P_PROC_AVX512F,
+  P_PROC_DYNAMIC
+};
+
+/* These are the values for vendor types, cpu types and subtypes.  Cpu
+   types and subtypes should be subtracted by the corresponding start
+   value.  */
+
+#define M_CPU_TYPE_START (BUILTIN_VENDOR_MAX)
+#define M_CPU_SUBTYPE_START \
+  (M_CPU_TYPE_START + BUILTIN_CPU_TYPE_MAX)
+#define M_VENDOR(a) (a)
+#define M_CPU_TYPE(a) (M_CPU_TYPE_START + a)
+#define M_CPU_SUBTYPE(a) (M_CPU_SUBTYPE_START + a)



signature.asc
Description: PGP signature

Bug#1004067: closed by Debian FTP Masters (reply to Mathieu Malaterre ) (Bug#1004067: fixed in imath 3.1.3-10)

[Mathieu Malaterre]

Hi all,

On Sun, Jan 23, 2022 at 10:45 PM Matteo F. Vescovi  wrote:
>
> Version: 3.1.3-10
>
> On 2022-01-23 at 18:42 (+01), Matteo F. Vescovi wrote:
> > The build still ftbfs.
>
> Gosh, at the time of writing was still using -9 revision and it failed.
> Now, I've tested -10 revision of imath and openexr builds just fine with
> it.

My fix is rather a crude hack. I do not believe the python ecosystem
(AFAIK) is ever using cmake export files for package dependencies. So
I believe the right fix would be to "undeclare" the python module from
the list of exported cmake module. Maybe we'll need to forward the
issue upstream.

Processed: python-lupa: FTBFS on mipsel during running the test

[Debian Bug Tracking System]

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

> notfound 1001239 1.10+dfsg-1
Bug #1001239 {Done: Graham Inggs } [src:python-lupa] 
python-lupa: FTBFS on mipsel during running the test
No longer marked as found in versions python-lupa/1.10+dfsg-1.
> thanks
Stopping processing here.

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

Bug#1004223: closing 1004223

[Salvatore Bonaccorso]

close 1004223 5.4.1+repack-1
thanks

Processed: closing 1004223

[Debian Bug Tracking System]

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

> close 1004223 5.4.1+repack-1
Bug #1004223 [minetest-server] minetest-server: ItemStack meta injection 
vulnerability in Minetest 5.3
Marked as fixed in versions minetest/5.4.1+repack-1.
Bug #1004223 [minetest-server] minetest-server: ItemStack meta injection 
vulnerability in Minetest 5.3
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Re: Bug#1002657: FTBFS with OCaml 4.13.1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1002657 [src:sks] FTBFS with OCaml 4.13.1
Added tag(s) patch.

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

Bug#1002657: FTBFS with OCaml 4.13.1

[Stéphane Glondu]

Control: tags -1 + patch

Le 26/12/2021 à 21:04, Stéphane Glondu a écrit :
> Your package FTBFS with OCaml 4.13.1 with the following error:
>> File "mList.ml", line 203, characters 14-23:
>> 203 |   let slist = List.sort compare list in
>> ^
>> Error (warning 6 [labels-omitted]): label cmp was omitted in the application 
>> of this function.
>> File "mList.ml", line 211, characters 14-23:
>> 211 |   let slist = List.sort compare list in
>> ^
>> Error (warning 6 [labels-omitted]): label cmp was omitted in the application 
>> of this function.

Patch attached.


Cheers,

-- 
StéphaneFrom fd51784c6ecd09a06812fa50a6c8add72bb63ce3 Mon Sep 17 00:00:00 2001
From: Stephane Glondu 
Date: Sat, 22 Jan 2022 09:24:17 +0100
Subject: [PATCH] Do not error on warning 6 [labels-omitted]

---
 Makefile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Makefile b/Makefile
index 491190e..45514b7 100644
--- a/Makefile
+++ b/Makefile
@@ -49,7 +49,7 @@ SKSVS=$(shell grep 'version_suffix = "+"' common.ml)
 ifeq ($(strip $(SKSVS)),)
 WARNERR=
 else
-WARNERR=-warn-error A
+WARNERR=-warn-error A-6
 endif
 
 CAMLINCLUDE= -package cryptokit,unix,str,bigarray,num -I bdb
-- 
2.34.1

Bug#1003579: marked as done (wsl: destroys files/directories named 'temp')

[Debian Bug Tracking System]

Your message dated Mon, 24 Jan 2022 02:36:27 +
with message-id 
and subject line Bug#1003579: fixed in wsl 0.2.1-3
has caused the Debian Bug report #1003579,
regarding wsl: destroys files/directories named 'temp'
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.)


-- 
1003579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wsl
Version: 0.2.1-2
Severity: grave

hi,

when sourcing /usr/share/wsl/wsl-functions, files or directories named
temp are overwritten or renamed to .wslrun, depending on if it is a file
or directory. Errors are not handled at all...

 cat ${MYENV} | grep -v "^#" | sort | uniq >temp
   echo "# history ends #" >>temp
   /bin/mv temp ${MYENV}


Made my temp folder unhappy. Even if its a file named 'temp', this
should never happen, especially as the created file is sourced later.

   . ${MYENV}




Cheers,

Bernd


-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F
--- End Message ---
--- Begin Message ---
Source: wsl
Source-Version: 0.2.1-3
Done: Andreas Beckmann 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 24 Jan 2022 02:40:15 +0100
Source: wsl
Architecture: source
Version: 0.2.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 1003579
Changes:
 wsl (0.2.1-3) unstable; urgency=medium
 .
   * QA upload.
   * Use a proper tempfile instead of hardcoded 'temp'.  (Closes: #1003579)
   * Switch from deprecated 'which' to 'command -v'.
Checksums-Sha1:
 2547f04f6be0a4b61a20e389a41e780b2d422df9 1696 wsl_0.2.1-3.dsc
 8f6a46794782909bc3c1bd1d8220ae18812ebd6d 4340 wsl_0.2.1-3.debian.tar.xz
 0e1d08b29e3535aca9d7a5ffd61c241d6847f8ed 5428 wsl_0.2.1-3_source.buildinfo
Checksums-Sha256:
 7ab02e9c4fab11841981cefda9a9965234b8fee3253f46c4790b4917b15ccd08 1696 
wsl_0.2.1-3.dsc
 e823b82ff46142b40786aee5ccf1870dbf1b0896795b7ba65e85c2597e3ee0f9 4340 
wsl_0.2.1-3.debian.tar.xz
 85c14db9e38313a62c6510fda63899ffa70373f88b823294b0c4648f3eaf8a0b 5428 
wsl_0.2.1-3_source.buildinfo
Files:
 bb89a9ee7e1a4d1288ee283797dff3a4 1696 admin optional wsl_0.2.1-3.dsc
 d7a9798c2e64dce289ec04ca56a702e8 4340 admin optional wsl_0.2.1-3.debian.tar.xz
 5e9bcd8f604fd1aec2b08fc33e0debef 5428 admin optional 
wsl_0.2.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmHuBMYQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCLS7D/4oWfbb9OPn0Vr77IUR+SX44C6Rj9+zGlhi
Fc8C2y+/+0zwuQK/7JIadiJXvYNS+bzTz+4YAINLmfa8TCsrSGcMFTSG4xX38YO3
N6esEObLENv4vSsv1ZQYd+vu+s4IIbIjBrL3zmpZO0QeIixo8GyDz7Fwesokl1KO
MI7VwduC57CUJp7DnFTFZHNHaI/iDokeZGVU/Mj1dXJnMqhkjt4TTbskoGOiZxbL
qOUsof0R/WTkS760jjmaEW1SfbZm2odqYnY9AshiFwp9qtPBnAyDkbKOT5m9ZKjE
LydMCHiVrdoJNKegC6Oa3xsq++081NgTW6bjQKwbMea7uKPEqS+Ppf33vJ0Fkb+O
CmxgJHigWBewrc2rEhZJb4X22E1Uk4o0JavmXI/CGIKvnr4Mc5wVXpqcqnNau9qp
cODHC5vaEjXkyIMUQAQwQ3bgivlYyh3MAqzwsqEO3hK+dlRdvUDrEiwRbimQxCW/
EOZTaJm9Tq36aoZXguZabh1wdTZMpqTfCBfQHqUEqGyrifmEz+++MbnXAAhjqtt9
NndbiumkOdxV+QpSAjtayiD0CEkFqZxf1xNeZaEZweZcEuVgaX6ECnqim8scK2po
yNfCIc9fkg0SBtQm5s0SdPftJupCWBsUjMKVpsEM00p1rqYnO6Gms0tnRvx56OsM
rerDg1jv4Q==
=8F6N
-END PGP SIGNATURE End Message ---

Bug#1002961: [Pkg-pascal-devel] Bug#1002961: Bug#1002961: src:castle-game-engine: fails to migrate to testing for too long: FTBFS on armel

[Abou Al Montacir]

Hi Paul,

On Sun, 2022-01-02 at 16:30 +0100, Paul Gevers wrote:
> > ..
> > Moreover CGE upstream think we should abandon armel (and other non 
> > widely used architectures) as a target for CGE, but I think myself it is 
> > a good test for the compiler and tend to think we should  keep it.
> 
> I agree with you. However, as a Release Team member, I also want to 
> prevent packages from being out-of-sync for too long. So, what I suggest 
> in this case is to temporarily disable the test on armel until we have 
> figured out how to fix the situation. That way the package can migrate 
> to testing, without making the situation much worse there.
Can you please review [1] before upload?

[1] 
https://salsa.debian.org/pascal-team/castle-game-engine/-/commit/d9b628c179bb53868e3d0bf9adc0b271969a613b
-- 
Cheers,
Abou Al Montacir



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

Bug#984144: fwbuilder: ftbfs with GCC-11

[Sylvestre Ledru]

Hello

Thanks for your patch

it is building for you? It is failing now with:

autoheader: warning: missing template: LIBFWBUILDER_TEMPLATE_DIR
autoheader: warning: missing template: NET_SNMP
autoheader: warning: missing template: UCD_SNMP
autoheader: warning: missing template: WORDS_LITTLEENDIAN
autoreconf: error: /usr/bin/autoheader failed with exit status: 1
dh_autoreconf: error: autoreconf -f -i returned exit code 1
make: *** [debian/rules:13: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit
status 2

Build finished at 2022-01-23T22:38:54Z

Thanks

S


Le 20/01/2022 à 16:16, Lukas Märdian a écrit :
> Package: fwbuilder
> Version: 5.3.7-4.1
> Followup-For: Bug #984144
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu jammy ubuntu-patch
> X-Debbugs-Cc: sl...@ubuntu.com
> Control: tags -1 patch
>
> Dear Sylvestre,
>
> fwbuilder fails to build from source due to using dynamic exception specs,
> which are deprecated as of C++17/GCC-11.
>
> In Ubuntu, the attached upstream patch was applied to achieve the following:
>
>   * d/p/ed4db20ec6cabfaea9c36187b7ce40d9d93c6c79.patch: Cherry-pick upstream
> commit to fix FTBFS with C++17/GCC-11
>
> https://github.com/fwbuilder/fwbuilder/commit/ed4db20ec6cabfaea9c36187b7ce40d9d93c6c79
>
> Thanks for considering the patch.
>
> Cheers,
>   Lukas
>
>
> -- System Information:
> Debian Release: 11.0
>   APT prefers impish-updates
>   APT policy: (500, 'impish-updates'), (500, 'impish-security'), (500, 
> 'impish'), (100, 'impish-backports')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.13.0-23-generic (SMP w/4 CPU threads)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
> LANGUAGE=de_DE:en_GB:en
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled

Bug#1004271: os.c:84: fatal error: RUNTIME_CHECK((size_t)s == (size_t)64) failed

[Ondřej Surý]

Control: forwarded -1 https://gitlab.isc.org/isc-projects/bind9/-/issues/3108

Yeah, there was wrong assumption on our side that the call would either not 
exist or always return valid value. There’s already MR for it which needs to be 
reviewed as I prepared it over the weekend.

Ondrej
--
Ondřej Surý  (He/Him)

> On 23. 1. 2022, at 23:18, Chris Hofstaedtler  wrote:
> 
> Package: bind9-dnsutils
> Version: 1:9.17.22-1
> Severity: serious
> X-Debbugs-Cc: p...@packages.debian.org
> 
> Dear ISC BIND Maintainers,
> Hello Ondřej,
> 
> src:pdns uses dig in its build to test pdns_server. On ppc64el this
> apparently now crashes:
> 
>  + dig -p 5301 @127.0.0.1 smoke.bind.example.org
>  + tee /tmp/tmp.RRMQ1Z4fs4
>  os.c:84: fatal error: RUNTIME_CHECK((size_t)s == (size_t)64) failed
> 
> Full pdns build log here:
>  
> https://buildd.debian.org/status/fetch.php?pkg=pdns=ppc64el=4.5.3-1=1642956562=0
> 
> It feels like, if this crashes on an arch, it would crash regardless of
> the supplied parameters, etc.
> 
> The RUNTIME_CHECK was introduced in upstream commit
>  
> https://gitlab.isc.org/isc-projects/bind9/-/commit/4f78f9d72a5dc3f6a596251e662d00cb80cd5e6d
> as I am sure you know :-)
> 
> Thanks,
> Chris

Processed: Re: Bug#1004271: os.c:84: fatal error: RUNTIME_CHECK((size_t)s == (size_t)64) failed

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://gitlab.isc.org/isc-projects/bind9/-/issues/3108
Bug #1004271 [bind9-dnsutils] os.c:84: fatal error: RUNTIME_CHECK((size_t)s == 
(size_t)64) failed
Ignoring request to change the forwarded-to-address of bug#1004271 to the same 
value

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

Processed: Re: Bug#1004271: os.c:84: fatal error: RUNTIME_CHECK((size_t)s == (size_t)64) failed

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://gitlab.isc.org/isc-projects/bind9/-/issues/3108
Bug #1004271 [bind9-dnsutils] os.c:84: fatal error: RUNTIME_CHECK((size_t)s == 
(size_t)64) failed
Set Bug forwarded-to-address to 
'https://gitlab.isc.org/isc-projects/bind9/-/issues/3108'.

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

Bug#1004271: os.c:84: fatal error: RUNTIME_CHECK((size_t)s == (size_t)64) failed

[Chris Hofstaedtler]

Control: affects -1 src:pdns

* Chris Hofstaedtler  [220123 23:18]:
> It feels like, if this crashes on an arch, it would crash regardless of
> the supplied parameters, etc.

Indeed, on the ppc64el porterbox:

...
Unpacking bind9-dnsutils (1:9.17.22-1) ...
...

(sid_ppc64-dchroot)zeha@perotto:~$ dig
os.c:84: fatal error: RUNTIME_CHECK((size_t)s == (size_t)64) failed
Aborted
(sid_ppc64-dchroot)zeha@perotto:~$

Chris

Processed: Re: Bug#1004271: os.c:84: fatal error: RUNTIME_CHECK((size_t)s == (size_t)64) failed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:pdns
Bug #1004271 [bind9-dnsutils] os.c:84: fatal error: RUNTIME_CHECK((size_t)s == 
(size_t)64) failed
Added indication that 1004271 affects src:pdns

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

Bug#1004271: os.c:84: fatal error: RUNTIME_CHECK((size_t)s == (size_t)64) failed

[Chris Hofstaedtler]

Package: bind9-dnsutils
Version: 1:9.17.22-1
Severity: serious
X-Debbugs-Cc: p...@packages.debian.org

Dear ISC BIND Maintainers,
Hello Ondřej,

src:pdns uses dig in its build to test pdns_server. On ppc64el this
apparently now crashes:

  + dig -p 5301 @127.0.0.1 smoke.bind.example.org
  + tee /tmp/tmp.RRMQ1Z4fs4
  os.c:84: fatal error: RUNTIME_CHECK((size_t)s == (size_t)64) failed

Full pdns build log here:
  
https://buildd.debian.org/status/fetch.php?pkg=pdns=ppc64el=4.5.3-1=1642956562=0

It feels like, if this crashes on an arch, it would crash regardless of
the supplied parameters, etc.

The RUNTIME_CHECK was introduced in upstream commit
  
https://gitlab.isc.org/isc-projects/bind9/-/commit/4f78f9d72a5dc3f6a596251e662d00cb80cd5e6d
as I am sure you know :-)

Thanks,
Chris

Bug#1004067: marked as done (imath: causes openexr to FTBFS)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jan 2022 22:45:01 +0100
with message-id <87a6fm9leq.fsf@localhost>
and subject line Re: Bug#1004067: closed by Debian FTP Masters 
 (reply to Mathieu Malaterre 
) (Bug#1004067: fixed in imath 3.1.3-10)
has caused the Debian Bug report #1004067,
regarding imath: causes openexr to 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.)


-- 
1004067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: imath
Version: 3.1.3-9
Severity: serious
Control: affects -1 + src:openexr

Hi,

openexr/experimental recently started to FTBFS, cmake aborts after an
imath related error:

CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Imath/ImathConfig.cmake:109 
(message):
  The imported target "Imath::PyImath_Python3_9" references the file

 "/usr/lib/x86_64-linux-gnu/libPyImath_Python3_9-3_1.so.29.2.0"

  but this file does not exist.  Possible reasons include:

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

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

 "/usr/lib/x86_64-linux-gnu/cmake/Imath/ImathConfig.cmake"

  but not all the files it references.

Call Stack (most recent call first):
  cmake/OpenEXRSetup.cmake:259 (find_package)
  CMakeLists.txt:59 (include)


-- Configuring incomplete, errors occurred!


My previous and successful build attempt of openexr/experimental was on Dec 7.
(openexr/sid is not affected)


Andreas


openexr_3.1.3-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 3.1.3-10

On 2022-01-23 at 18:42 (+01), Matteo F. Vescovi wrote:
> The build still ftbfs.

Gosh, at the time of writing was still using -9 revision and it failed.
Now, I've tested -10 revision of imath and openexr builds just fine with
it.

Thus, closing (again).

Cheers.


-- 
Matteo F. Vescovi


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

Bug#1002532: marked as done (pygments breaks ruby-pygments.rb autopkgtest: UTF-8 != ASCII-8BIT)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jan 2022 21:34:58 +
with message-id 
and subject line Bug#1002532: fixed in ruby-pygments.rb 2.3.0+ds-1
has caused the Debian Bug report #1002532,
regarding pygments breaks ruby-pygments.rb autopkgtest: UTF-8 != ASCII-8BIT
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.)


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

Source: pygments, ruby-pygments.rb
Control: found -1 pygments/2.10.0+dfsg-1
Control: found -1 ruby-pygments.rb/1.2.1-2
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
pygments   from testing2.10.0+dfsg-1
ruby-pygments.rb   from testing1.2.1-2
all others from testingfrom testing

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

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


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

Paul

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

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


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

└──┘

NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It 
will be removed in Rubygems 4

Gem::Specification#has_rdoc= called from pygments.rb.gemspec.gem2deb:15.
GEM_PATH= ruby2.7 -e gem\ \"pygments.rb\"

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

└──┘

mv lib ./.gem2deb.lib
RUBYLIB=. GEM_PATH= ruby2.7 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.7 -w -I"test" 
/usr/share/rubygems-integration/all/gems/rake-13.0.3/lib/rake/rake_test_loader.rb 
"test/test_pygments.rb" -v
/tmp/autopkgtest-lxc.w3sdlnr1/downtmp/build.2uD/src/test/test_pygments.rb:89: 
warning: assigned but unused variable - code
Loaded suite 
/usr/share/rubygems-integration/all/gems/rake-13.0.3/lib/rake/rake_test_loader

Started
PygmentsConfigTest:   test_filters: 
.: (0.256212)
  test_formatters:  .: (0.005894)
  test_lexers:  .: (0.002138)
  test_styles:  .: (0.000682)
PygmentsCssTest:   test_css:.: 
(0.001871)
  test_css_colorful:.: (0.001783)
  test_css_default: .: (0.001030)
  test_css_options: .: (0.001042)
  test_css_prefix:  .: (0.001095)
  test_css_prefix_and_options:  .: (0.001029)
PygmentsHighlightTest:   test_full_html_highlight:  
.: (0.115936)
  test_full_table_highlight:F
===
Failure: test_full_table_highlight(PygmentsHighlightTest)
/tmp/autopkgtest-lxc.w3sdlnr1/downtmp/build.2uD/src/test/test_pygments.rb:32:in 
`test_full_table_highlight'

 29:   def test_full_table_highlight
 30: code = P.highlight(RUBY_CODE, :options => {:linenos => true})
 31: assert_match '#!/usr/bin/ruby', code
  => 32: assert_equal "class=\"linenos\">1\n2class=\"code\">class=\"ch\">#!/usr/bin/ruby\nputs 
class=\"s1\">foo\n\n", code

 33:   end
 34:  35:   def test_highlight_works_with_larger_files
<"class=\"linenodiv\">1\n" +
"2class=\"highlight\">class=\"ch\">#!/usr/bin/ruby\n" +

"puts foo\n" +
"\n" +
""> expected but was
<"class=\"linenodiv\">1\n" +

Bug#1002366: marked as done (python-django-celery-results: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" --system=custom "--test-args={interpreter} -m pytes

[Debian Bug Tracking System]

Your message dated Sun, 23 Jan 2022 21:34:23 +
with message-id 
and subject line Bug#1002366: fixed in python-django-celery-results 2.2.0-1
has caused the Debian Bug report #1002366,
regarding python-django-celery-results: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p "3.10 3.9" --system=custom 
"--test-args={interpreter} -m pytest" returned exit code 13
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --system=custom --test-args="{interpreter} -m pytest"
> I: pybuild base:237: python3.10 -m pytest
> = test session starts 
> ==
> platform linux -- Python 3.10.1, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
> Django settings: t.proj.settings (from ini file)
> rootdir: /<>, configfile: setup.cfg, testpaths: t/
> plugins: django-3.5.1, case-1.5.3
> collected 23 items
> 
> t/unit/backends/test_database.py FFF.FFF.[ 
> 34%]
> t/integration/benchmark_models.py s  [ 
> 39%]
> t/unit/test_migrations.py .. [ 
> 47%]
> t/unit/test_models.py s. [ 
> 56%]
> t/unit/test_views.py ..  [ 
> 65%]
> t/unit/backends/test_cache.py    
> [100%]
> 
> === FAILURES 
> ===
> _ test_DatabaseBackend.test_backend__pickle_serialization__dict_result 
> _
> 
> self =  0x7f4a30fc9ba0>
> 
> def test_backend__pickle_serialization__dict_result(self):
> self.app.conf.result_serializer = 'pickle'
> self.app.conf.accept_content = {'pickle', 'json'}
> self.b = DatabaseBackend(app=self.app)
> 
> tid2 = uuid()
> result = {'foo': 'baz', 'bar': SomeClass(12345)}
> request = mock.MagicMock()
> request.task = 'my_task'
> request.args = ['a', 1, SomeClass(67)]
> request.kwargs = {'c': 6, 'd': 'e', 'f': SomeClass(89)}
> request.hostname = 'celery@ip-0-0-0-0'
> request.chord = None
> del request.argsrepr, request.kwargsrepr
> 
> self.b.mark_as_done(tid2, result, request=request)
> mindb = self.b.get_task_meta(tid2)
> 
> >   assert mindb.get('result').get('foo') == 'baz'
> E   AttributeError: 'NoneType' object has no attribute 'get'
> 
> t/unit/backends/test_database.py:50: AttributeError
> _ test_DatabaseBackend.test_backend__pickle_serialization__str_result 
> __
> 
> self =  0x7f4a30f1b3d0>
> 
> def test_backend__pickle_serialization__str_result(self):
> self.app.conf.result_serializer = 'pickle'
> self.app.conf.accept_content = {'pickle', 'json'}
> self.b = DatabaseBackend(app=self.app)
> 
> tid2 = uuid()
> result = 'foo'
> request = mock.MagicMock()
> request.task = 'my_task'
> request.args = ['a', 1, SomeClass(67)]
> request.kwargs = {'c': 6, 'd': 'e', 'f': SomeClass(89)}
> request.hostname = 'celery@ip-0-0-0-0'
> request.chord = None
> del request.argsrepr, request.kwargsrepr
> 
> self.b.mark_as_done(tid2, result, request=request)
> mindb = self.b.get_task_meta(tid2)
> 
> >   assert mindb.get('result') == 'foo'
> E   AssertionError: assert None == 'foo'
> E+  where None =  0x7f4a30f84f80>('result')
> E+where  = 
> {'date_done': None, 'result': None, 'status': 'PENDING', 'task_args': None, 
> ...}.get
> 
> t/unit/backends/test_database.py:91: AssertionError
>  test_DatabaseBackend.test_backend__pickle_serialization__bytes_result 
> _
> 
> self =  0x7f4a30da2cb0>
> 
> def test_backend__pickle_serialization__bytes_result(self):
> self.app.conf.result_serializer = 'pickle'
> self.app.conf.accept_content = {'pickle', 'json'}
> self.b = DatabaseBackend(app=self.app)
> 
> tid2 = uuid()
> result = b'foo'
> request = 

Processed: closing 997310

[Debian Bug Tracking System]

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

> close 997310 2.3.0+ds-1
Bug #997310 [src:ruby-pygments.rb] ruby-pygments.rb: FTBFS: ERROR: Test 
"ruby2.7" failed.
The source 'ruby-pygments.rb' and version '2.3.0+ds-1' do not appear to match 
any binary packages
Marked as fixed in versions ruby-pygments.rb/2.3.0+ds-1.
Bug #997310 [src:ruby-pygments.rb] ruby-pygments.rb: FTBFS: ERROR: Test 
"ruby2.7" failed.
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1002532: pygments breaks ruby-pygments.rb autopkgtest: UTF-8 != ASCII-8BIT

[Mattia Rizzolo]

On Fri, Jan 21, 2022 at 03:51:02PM +0100, Alexandre Ghiti wrote:
> I can't find how to create a MR in salsa, can you pull directly from here:
> 
> https://salsa.debian.org/alexghiti/ruby-pygments.rb/-/tree/int/alex/2.3.0
> 
> It successfully built in my PPA, if you need any more modification, do
> not hesitate.

Ah, another thing.  Please be careful with the version you pick.

You used 2.3.0+ds-1ubuntu1, which is *higher* than what I'll be
uploading, namely 2.3.0+ds-1.
Furthermore, in your PPA you used 2.3.0+ds-1ubuntu2, which would also
conflict with an eventual -1ubuntu done in the offical ubuntu archive.

I'd recommend you used something like -0ppa1 or -0ubuntu1~ppa1 or
somesuch.

(in this case this is of no consequence, but just something to note).



Lastly, I noticed that you haven't even touched the changelog.  In this
case there was even a new copyright holder, so it really should have
been updated.
I didn't add you to the paragraph of d/copyright, as I assume you are
doing this under your paid time, and I don't know what's Canonical's
rules regarding copyright here.  If needed/wanted, just send me a note
and I'll update the copy in git.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Processed: tagging 1001760, found 1001760 in 6.9.5-3, tagging 1003345, tagging 1004143 ...

[Debian Bug Tracking System]

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

> tags 1001760 + experimental
Bug #1001760 {Done: Jose Luis Rivero } [dart] FTBFS: 
'placeholders' is ambiguous
Added tag(s) experimental.
> found 1001760 6.9.5-3
Bug #1001760 {Done: Jose Luis Rivero } [dart] FTBFS: 
'placeholders' is ambiguous
There is no source info for the package 'dart' at version '6.9.5-3' with 
architecture ''
Unable to make a source version for version '6.9.5-3'
Marked as found in versions 6.9.5-3.
> tags 1003345 + sid bookworm
Bug #1003345 {Done: Cédric Boutillier } [src:ruby-sqlite3] 
ruby-sqlite3: FTBFS with SQLite3 3.37.0+
Added tag(s) sid and bookworm.
> tags 1004143 + sid bookworm
Bug #1004143 [src:libminion-backend-sqlite-perl] libminion-backend-sqlite-perl: 
test failures with SQLite 3.37
Added tag(s) bookworm and sid.
> reassign 1004188 src:openems 0.0.35+git20190103.6a75e98+dfsg.1-3.1
Bug #1004188 [0.0.35+git20190103.6a75e98+dfsg.1-3.1] 
[0.0.35+git20190103.6a75e98+dfsg.1-3.1] 
Warning: Unknown package '0.0.35+git20190103.6a75e98+dfsg.1-3.1'
Bug reassigned from package '0.0.35+git20190103.6a75e98+dfsg.1-3.1' to 
'src:openems'.
Ignoring request to alter found versions of bug #1004188 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1004188 to the same values 
previously set
Bug #1004188 [src:openems] [0.0.35+git20190103.6a75e98+dfsg.1-3.1] 
The source 'openems' and version '0.0.35+git20190103.6a75e98+dfsg.1-3.1' do not 
appear to match any binary packages
Marked as found in versions openems/0.0.35+git20190103.6a75e98+dfsg.1-3.1.
> thanks
Stopping processing here.

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

Bug#1002532: pygments breaks ruby-pygments.rb autopkgtest: UTF-8 != ASCII-8BIT

[Mattia Rizzolo]

Hi Alex!

Please take note that the Debian BTS doesn't subscribe automatically
posters to a bug report, so you need to explicitly CC people that you
want to message!
(Grahm pointed me to your reply ^^)

Also, I'm happy to have pointed out to tools and things you weren't
aware of!  :)

On Fri, Jan 21, 2022 at 03:51:02PM +0100, Alexandre Ghiti wrote:
> On Fri, 21 Jan 2022 12:08:27 +0100 Alexandre Ghiti
>  wrote:
> > On Thu, 20 Jan 2022 18:50:33 +0100 Mattia Rizzolo  wrote:
> > > * You did a ton of patch wrangling, including deletion, renaming,
> > > rebasing, etc. which is all fine, except that the way you did it
> > > obscures quite a bit what you did. Why did you drop the numbers from
> > > the patches? Do you have --no-patch-numbers as you gbp-pq default or
> > > something?
> >
> > I changed the patches names since they were different: I fixed that in
> > my coming MR. Thanks for gbp that I did not know neither.

Indeed, those patches from before were handled by gbp-pq, which
basically uses `git format-patch` instead of plain dep-3 headers.

I must admit that I prefer the original DEP-3, however that makes the
gbp-pq import/export more noisy.  But well, that's fine.

> > > * why requiring gem2deb >=1 ? that's already in bullseye as well in
> > > focal, so why did you feel the need to add the version? (that's also
> > > not in the changelog)
> >
> > I simply copied the debian/ directory from the previous version that I
> > got from pull-lp-source, I did not use git...I'll use git in the
> > future, thanks.

Ah, I see indeed that the current package has that thing.  mh.  Sorry I
didn't notice that.


Normally it's fine to base some work in the released package, however
especially for team-maintained packages, it might be more useful and
helpful to do the work in git nowadays, even if that exposes the
submitter to the mess that is git maintenance in debian (where different
teams have different workflows and different tools).

> > > Could I ask you to submit a MR on top of it, with at least commits
> > > separating the deletion, refresh and rebasing of patches (and eventual
> > > new ones, I can't tell at a glance if any new patch appeared…) also
> > > separated.
> > > https://salsa.debian.org/ruby-team/ruby-pygments.rb
> >
> 
> > It's on its way :)
> 
> I can't find how to create a MR in salsa,

That's because you create a new repo instead of clicking the "fork"
button on the original project.  GitLab allows for MR to be created only
in forks.

> can you pull directly from here:
> 
> https://salsa.debian.org/alexghiti/ruby-pygments.rb/-/tree/int/alex/2.3.0
> 
> It successfully built in my PPA, if you need any more modification, do
> not hesitate.

That looks fine!

I'm going to massage the changelog a bit, but besides that it looks
cool!


Thank you!

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#984063: [Debian-med-packaging] Bug#984063: Closing bug (Was: Bug#984063: itk libtiff test issues (Was: Bug#984063))

[Steven Robbins]

On Saturday, January 22, 2022 12:15:25 P.M. CST Étienne Mollier wrote:
> Hi Andreas,
> 
> Andreas Tille, on 2022-01-16:
> > I think the roadmap that ITK4 will be deleted as soon as possible
> > is clear.  However, if it might serve as an intermediate means
> > to support some remaining dependencies temporarily I think it
> > is OK to do some tricks that would not be acceptable as long
> > term means.
> 
> I have been working on a rewrap of insighttoolkit4 to include
> the embedded tiff library, and with all the previous patching to
> address the initial issue described in this bug, the build went
> through.  The package should be in shape for upload tomorrow.

Neat!   I'm  sure that those using ITK 4 will appreciate your work.

As far as the existing Salsa repository is concerned: I would encourage you to 
consider using a v4 branch to maintain it.  If you prefer to do something 
else, that is also fine with me.  Just want to be clear that I haven't any 
objection to keeping v4 and v5 in a single repository.

-Steve


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

Bug#999575: elan: error: failed to select a version for the requirement `itertools = "^0.9.0"`

[Christopher Hoskin]

Source: elan
Version: 1.0.6-1
Followup-For: Bug #999575

Dear Peter,

Thank you very much for the debdiff patch. I'm embarrassed to say, I'm not sure 
what to do with a debdiff patch. Can I import it into the salsa repo in some 
way?

Thank you for your help,

Christopher

Bug#1001239: marked as done (python-lupa: FTBFS on mipsel during running the test)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jan 2022 21:53:20 +0200
with message-id 

and subject line python-lupa: FTBFS on mipsel during running the test
has caused the Debian Bug report #1001239,
regarding python-lupa: FTBFS on mipsel during running the test
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.)


-- 
1001239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-lupa
Version: 1.10+dfsg-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
Control: affects -1 python-fakeredis

Dear maintainer,

Your latest upload FTBFS on mipsel. This is delaying the Python3.10
transition.

==
FAIL: test_coroutine_while_status (lupa.tests.test.TestLuaCoroutines)
--
Traceback (most recent call last):
  File "/<>/lupa/tests/test.py", line 1510, in 
test_coroutine_while_status
self.assertEqual([0,1,0,1,0,1], result)
AssertionError: Lists differ: [0, 1, 0, 1, 0, 1] != [0, 1, 0, 1, 0, 0]

First differing element 5:
1
0

- [0, 1, 0, 1, 0, 1]
? ^

+ [0, 1, 0, 1, 0, 0]
? ^


--
Ran 264 tests in 7.487s

FAILED (failures=1)
Test failed: 
error: Test failed: 
E: pybuild pybuild:354: test: plugin distutils failed with: exit code=1: 
python3.9 setup.py test 
dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned 
exit code 13
make: *** [debian/rules:14: binary-arch] Error 25
--- End Message ---
--- Begin Message ---
Version: 1.10+dfsg-1

given back on mipsel and built successfully--- End Message ---

Bug#1004167: marked as done (debianutils: tries to overwrite /usr/share/man/fr/man1/readlink.1.gz, also in manpages-fr)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jan 2022 18:48:59 +
with message-id 
and subject line Bug#1004167: fixed in debianutils 5.7-0.1
has caused the Debian Bug report #1004167,
regarding debianutils: tries to overwrite /usr/share/man/fr/man1/readlink.1.gz, 
also in manpages-fr
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.)


-- 
1004167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debianutils
Version: 5.5-1
Severity: grave
Justification: renders package unusable

I get the following error when I want to upgrade:

Unpacking debianutils (5.6-0.1) over (5.5-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/debianutils_5.6-0.1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/man/fr/man1/readlink.1.gz', which is also in 
package manpages-fr 4.12.1-3
Errors were encountered while processing:
 /var/cache/apt/archives/debianutils_5.6-0.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

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

Versions of packages debianutils depends on:
ii  libc6  2.33-3

debianutils recommends no packages.

debianutils suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: debianutils
Source-Version: 5.7-0.1
Done: Bastian Blank 

We believe that the bug you reported is fixed in the latest version of
debianutils, 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.
Bastian Blank  (supplier of updated debianutils 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: Sun, 23 Jan 2022 19:05:32 +0100
Source: debianutils
Architecture: source
Version: 5.7-0.1
Distribution: unstable
Urgency: medium
Maintainer: Clint Adams 
Changed-By: Bastian Blank 
Closes: 1004167
Changes:
 debianutils (5.7-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove old and now conflicting manpage.  closes: #1004167
Checksums-Sha1:
 4566dc567c2a2ec3e9f09fd53d603c829a645925 1542 debianutils_5.7-0.1.dsc
 de1860b7874d5e2f0635a08b8ab2d31e7ca50be4 257231 debianutils_5.7.orig.tar.gz
 88b645dd0f7c73a1101e87d996bc3b17661a38ce 21564 
debianutils_5.7-0.1.debian.tar.xz
 789e4b1d9ed308fda792a4b626f27098ac67a586 4199 
debianutils_5.7-0.1_source.buildinfo
Checksums-Sha256:
 437dd4a5bae8a592ca1b844f98975605497009cd45fdca9325178c382d49bca1 1542 
debianutils_5.7-0.1.dsc
 27ec9e0e7e44dc8ab611aa576330471bacb07e4491ffecf0d3aa6909c92f9022 257231 
debianutils_5.7.orig.tar.gz
 43e959668d0731072613ff910e4c9354164ee7c8df7d805505ca0e2604bea8c4 21564 
debianutils_5.7-0.1.debian.tar.xz
 8eed0aada8d2e9b37316c3a556d35a88f7e2c3e030c642dce691c411620bc492 4199 
debianutils_5.7-0.1_source.buildinfo
Files:
 eed27ed53bcfe309aea2dfacbf6d3356 1542 utils required debianutils_5.7-0.1.dsc
 8bbe5fd5524e1960a792d8a4420b2539 257231 utils required 
debianutils_5.7.orig.tar.gz
 a3b730e5c382c136afee2aaa95176f69 21564 utils required 
debianutils_5.7-0.1.debian.tar.xz
 1b28ee91679ef25de0dfaee7c05ce876 4199 utils required 
debianutils_5.7-0.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEER3HMN63jdS1rqjxLbZOIhYpp/lEFAmHtmWgACgkQbZOIhYpp
/lH3pgf+Np3hCgQM7zNE8J8xu25pkhPZwnpof7twWj8lPxCFxDTZNMF5MNFJxu8L
l/7IB7NqTM9XYr8ggaGHKkSZaptexB79SobGunm4GGtgYZhfQEfcbr89lvkGowKu

Bug#1004260: marked as done (pybuild-plugin-pyproject: Uninstallable)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jan 2022 12:47:58 -0500
with message-id <1719988.nozkWluFcG@localhost>
and subject line Re: Bug#1004260: pybuild-plugin-pyproject: Uninstallable
has caused the Debian Bug report #1004260,
regarding pybuild-plugin-pyproject: Uninstallable
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.)


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

Package: pybuild-plugin-pyproject
Version: 5.20220119
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: ste...@debian.org


Dear Maintainer,

The dh-python-pep517 meta package, required for poetry builds, and 
satisfied solely by this package, fails to install.


$ sudo apt-get install dh-python dh-python-pep517
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
dh-python is already the newest version (5.20220119).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 dh-python-pep517 : Depends: dh-python (= 5.20211225) but 5.20220119 is 
to be installed

E: Unable to correct problems, you have held broken packages.

Corroborated by the current debcheck report - 
https://qa.debian.org/debcheck.php?dist=unstable=dh-python


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

Kernel: Linux 5.14.0-2-amd64 (SMP w/6 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: 
LC_ALL set to en_US.UTF-8), LANGUAGE not set

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pybuild-plugin-pyproject depends on:
ii  dh-python  5.20220119
ii  python3-build  0.7.0-2
ii  python3-installer  0.4.0+dfsg1-2
ii  python3-tomli  1.2.2-2

pybuild-plugin-pyproject recommends no packages.

pybuild-plugin-pyproject suggests no packages.

-- no debconf information



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
On Sunday, January 23, 2022 12:44:22 PM EST David Steele wrote:
> Package: pybuild-plugin-pyproject
> Version: 5.20220119
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: ste...@debian.org
> 
> 
> Dear Maintainer,
> 
> The dh-python-pep517 meta package, required for poetry builds, and
> satisfied solely by this package, fails to install.
> 
> $ sudo apt-get install dh-python dh-python-pep517
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> dh-python is already the newest version (5.20220119).
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>   dh-python-pep517 : Depends: dh-python (= 5.20211225) but 5.20220119 is
> to be installed
> E: Unable to correct problems, you have held broken packages.
> 
> Corroborated by the current debcheck report -
> https://qa.debian.org/debcheck.php?dist=unstable=dh-python

The package was renamed to pybuild-plugin-pyproject.  Use that in build-
depends instead.  This is intentional, not a bug.

Scott K


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

Processed: Re: Bug#1004067 closed by Debian FTP Masters (reply to Mathieu Malaterre ) (Bug#1004067: fixed in imath 3.1.3-10)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1004067 {Done: Mathieu Malaterre } [src:imath] imath: 
causes openexr to FTBFS
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions imath/3.1.3-10.

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

Bug#1004260: pybuild-plugin-pyproject: Uninstallable

[David Steele]

Package: pybuild-plugin-pyproject
Version: 5.20220119
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: ste...@debian.org


Dear Maintainer,

The dh-python-pep517 meta package, required for poetry builds, and 
satisfied solely by this package, fails to install.


$ sudo apt-get install dh-python dh-python-pep517
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
dh-python is already the newest version (5.20220119).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 dh-python-pep517 : Depends: dh-python (= 5.20211225) but 5.20220119 is 
to be installed

E: Unable to correct problems, you have held broken packages.

Corroborated by the current debcheck report - 
https://qa.debian.org/debcheck.php?dist=unstable=dh-python


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

Kernel: Linux 5.14.0-2-amd64 (SMP w/6 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: 
LC_ALL set to en_US.UTF-8), LANGUAGE not set

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pybuild-plugin-pyproject depends on:
ii  dh-python  5.20220119
ii  python3-build  0.7.0-2
ii  python3-installer  0.4.0+dfsg1-2
ii  python3-tomli  1.2.2-2

pybuild-plugin-pyproject recommends no packages.

pybuild-plugin-pyproject suggests no packages.

-- no debconf information



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1004067: closed by Debian FTP Masters (reply to Mathieu Malaterre ) (Bug#1004067: fixed in imath 3.1.3-10)

[Matteo F. Vescovi]

Control: reopen -1

On 2022-01-23 at 16:51 (GMT), Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:imath package:
>
> #1004067: imath: causes openexr to FTBFS

The build still ftbfs.

Cheers.


-- 
Matteo F. Vescovi || Debian Developer
GnuPG KeyID: 4096R/0x8062398983B2CF7A


signature.asc
Description: PGP signature

Bug#1003663: marked as done (golang-github-containers-image: FTBFS: tests fail with 'key has been revoked')

[Reinhard Tartler]

>
>
> Hi Andreas, thank you for your report,
>
> I've tried rebuilding the package on my laptop in a clean sid chroot,
> and for some reason, it works just fine.
>
> Can you please have a look at my build log and help me understand why
> the build is failing for you but not for me?
>
>
I looked a bit more at the code, and it appears to me that the code that is
failing is accessing the kernel "session" keyring using the kernel API here:

https://man7.org/linux/man-pages/man3/keyctl_get_keyring_ID.3.html

It seems to me that on your system, someone or something has revoked the
keys using "keyctl revoke" or some equivalent system call. As said, this
does not appear to be happening on my system, and it also doesn't appear to
be happening on the debian buildd machines.

Have a great weekend,
-rt


-- 
regards,
Reinhard

Bug#1004067: marked as done (imath: causes openexr to FTBFS)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jan 2022 16:49:10 +
with message-id 
and subject line Bug#1004067: fixed in imath 3.1.3-10
has caused the Debian Bug report #1004067,
regarding imath: causes openexr to 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.)


-- 
1004067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: imath
Version: 3.1.3-9
Severity: serious
Control: affects -1 + src:openexr

Hi,

openexr/experimental recently started to FTBFS, cmake aborts after an
imath related error:

CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Imath/ImathConfig.cmake:109 
(message):
  The imported target "Imath::PyImath_Python3_9" references the file

 "/usr/lib/x86_64-linux-gnu/libPyImath_Python3_9-3_1.so.29.2.0"

  but this file does not exist.  Possible reasons include:

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

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

 "/usr/lib/x86_64-linux-gnu/cmake/Imath/ImathConfig.cmake"

  but not all the files it references.

Call Stack (most recent call first):
  cmake/OpenEXRSetup.cmake:259 (find_package)
  CMakeLists.txt:59 (include)


-- Configuring incomplete, errors occurred!


My previous and successful build attempt of openexr/experimental was on Dec 7.
(openexr/sid is not affected)


Andreas


openexr_3.1.3-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: imath
Source-Version: 3.1.3-10
Done: Mathieu Malaterre 

We believe that the bug you reported is fixed in the latest version of
imath, 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.
Mathieu Malaterre  (supplier of updated imath 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: Sun, 23 Jan 2022 17:29:48 +0100
Source: imath
Architecture: source
Version: 3.1.3-10
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 

Changed-By: Mathieu Malaterre 
Closes: 1004067
Changes:
 imath (3.1.3-10) unstable; urgency=medium
 .
   * Team upload.
   * d/rules: Downgrade an error to simply a status message. Closes: #1004067
Checksums-Sha1:
 ef935d7d54054e70041ef05e9821feeb88503c78 2486 imath_3.1.3-10.dsc
 d87df0e43f5616f48f4dfee92f6cee160b22d8c0 9960 imath_3.1.3-10.debian.tar.xz
 fb590aa9b62710ba91ed5f8086868ae3da01bad5 8908 imath_3.1.3-10_source.buildinfo
Checksums-Sha256:
 9ecd305123b26382598afb4fe859f385664393ef8efe6083ee9ec99fd37c7153 2486 
imath_3.1.3-10.dsc
 d3aeb0430193a35057bb8c95f34a87bf317468aed0df4bbc9b5fb8396b1abfad 9960 
imath_3.1.3-10.debian.tar.xz
 83234fdde16837a64c11c89497f80a3e6a3d66b8821d3d4cc4ffcde88a72 8908 
imath_3.1.3-10_source.buildinfo
Files:
 89abceb63d53935b71256e04f6393b76 2486 libs optional imath_3.1.3-10.dsc
 7b3a6cf66e6a8e9ddd2a53473c7acae9 9960 libs optional 
imath_3.1.3-10.debian.tar.xz
 2313a1610c76314572e3098be2d03af7 8908 libs optional 
imath_3.1.3-10_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAmHthA8RHG1hbGF0QGRl
Ymlhbi5vcmcACgkQAXHhgorgk0WtPQ//WUap6sFkeQToZP4RVSxfBO4lkXh2dYse
Z9w62sZwGjyLbgrwooviDzKxYFmaDSNQTRB+g9MG3MNyzDuTTuUwHyA07MoYllhj
+dqVYYh5qDSx/SO+zsEvwluDaUw7hXkBz7TgB2e77gabED8WXl1coevBqkGqsX+s
NFWBaUDpSYIRwloviponj1rUYtjO6D2wjejcvZfvEbuXn4d4BtwmT3DWt5hkD5hH
vEFwQq5ujDrvZTbS/WcjMIE9TLi5AEh8j2kOmJjl+spRjt4jP5+N5x/305ZeD5MJ
Gj5vQRFs0pPV0esX2Pune6C9oxgniXgZXOwuIpceluKuU5oCdfllwPqr2ZAAQ8pC
9DtfT7J78ElybF2yNqt3TFo2eTKCYqCB6YmKypqLhV96PUY/HLwVKjrhNOOQRLef
GNDItZxM2b2XWG9PhICT3BicHxt7XfkNZ++nOr1CrI/lQRCYcL43uB8ufClat/Ru
21ZGJ7JPePwcqFKmHOTlk+Jo7PdGjefkMvQK/nn//w3hdOzaamdO/+5tDBR5E/zO
KzGZp8xQERxIVpxkvACqveZFpmPRLUifgdMaqZJWNLbASXmkPhKczJh4Ryl5/sIm
4nYG8/2z1bI5MYnVmjiwtN+bH3qCXl8VYVTkBJwJWeWL98HQHlVVZdNozt0vlOIW
TXOcfAgr00c=
=pFt4
-END PGP SIGNATURE End Message ---

Bug#1004253: broken for BIND in stable

[Marco d'Itri]

Package: prometheus-bind-exporter
Version: 0.4.0+ds-1+b5
Severity: grave

It just does not work due to 
https://github.com/prometheus-community/bind_exporter/issues/96:

Jan 23 16:31:43 dns2 prometheus-bind-exporter[14800]: level=error 
ts=2022-01-23T15:31:43.292Z caller=bind_exporter.go:427 msg="Couldn't retrieve 
BIND stats" err="failed to unmarshal XML response: strconv.ParseUint: parsing 
\"-\": invalid syntax"

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#964654:

[Akbar Emamy]

On Tue, 21 Sep 2021 04:56:47 +1200 Kaily Salmon <74pacervail...@gmail.com>
wrote:
>

Bug#1002773: marked as done (nbdkit: FTBFS: build-dependency not installable: guestfs-tools)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jan 2022 16:59:36 +0100
with message-id <87v8yatpcn@msgid.hilluzination.de>
and subject line PAckage is available
has caused the Debian Bug report #1002773,
regarding nbdkit: FTBFS: build-dependency not installable: guestfs-tools
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.)


-- 
1002773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002773
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nbdkit
Version: 1.28.3-2
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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 12), perl, pkg-config, 
> bash-completion, xorriso, comerr-dev, libcurl4-gnutls-dev | libcurl-dev, 
> libext2fs-dev, libgnutls28-dev (>= 3.3), gnutls-bin, libguestfs-dev (>= 
> 1:1.36.11-3), liblzma-dev, liblua5.3-dev, libperl-dev, python3-dev, ruby, 
> ruby-dev, tcl-dev, libselinux1-dev, libssh-dev, libtorrent-rasterbar-dev, 
> libvirt-dev, zlib1g-dev, libzstd-dev, linux-image-amd64, busybox, iproute2, 
> jq, socat, libguestfs-tools, libnbd-dev, libnbd-bin, python3-libnbd, expect, 
> bsdmainutils, openssh-server, qemu-utils, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 12), perl, pkg-config, 
> bash-completion, xorriso, comerr-dev, libcurl4-gnutls-dev, libext2fs-dev, 
> libgnutls28-dev (>= 3.3), gnutls-bin, libguestfs-dev (>= 1:1.36.11-3), 
> liblzma-dev, liblua5.3-dev, libperl-dev, python3-dev, ruby, ruby-dev, 
> tcl-dev, libselinux1-dev, libssh-dev, libtorrent-rasterbar-dev, libvirt-dev, 
> zlib1g-dev, libzstd-dev, linux-image-amd64, busybox, iproute2, jq, socat, 
> libguestfs-tools, libnbd-dev, libnbd-bin, python3-libnbd, expect, 
> bsdmainutils, openssh-server, qemu-utils, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [672 B]
> Get:5 copy:/<>/apt_archive ./ Packages [688 B]
> Fetched 2323 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libguestfs-tools : Depends: guestfs-tools but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2021/12/28/nbdkit_1.28.3-2_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
guestfs-tools is now available, I am therefore closing this bug.

Cheers,
-Hilko--- End Message ---

Bug#1002609: marked as done (Build-Conflicts with ocaml)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jan 2022 15:06:19 +
with message-id 
and subject line Bug#1002609: fixed in llvm-toolchain-13 1:13.0.1~+rc3-1~exp1
has caused the Debian Bug report #1002609,
regarding Build-Conflicts with ocaml
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.)


-- 
1002609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-11
Version: 1:11.1.0-4
Severity: important
X-Debbugs-Cc: debian-ocaml-ma...@lists.debian.org

Dear Maintainer,

I don't understand with llvm-toolchain-11 build-conflicts with ocaml.

With ocaml 4.13.1 (in experimental), the *-nox binary packages are
becoming transitional, and their contents moved to
ocaml{,-base}. Hence, llvm-toolchain-11 cannot be built in the
universe rebuit with the new ocaml.

The build-conflicts should be dropped.


Cheers,

-- 
Stéphane


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

Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-13
Source-Version: 1:13.0.1~+rc3-1~exp1
Done: Sylvestre Ledru 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 13 Jan 2022 21:17:23 +0100
Source: llvm-toolchain-13
Architecture: source
Version: 1:13.0.1~+rc3-1~exp1
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Closes: 1002609 1003081
Changes:
 llvm-toolchain-13 (1:13.0.1~+rc3-1~exp1) experimental; urgency=medium
 .
   [ Samuel Thibault ]
   * Explicitly link against -latomic on all ports, not only the Linux ones.
   * Stop hardcoding -DCMAKE_SYSTEM_NAME=Linux as cmake parameter, as it breaks
 stage2 builds on non-Linux architectures
 .
   [ Pino Toscano ]
   * debian/rules: Disable 64bit runtime build on hurd-i386 (Closes: #1003081).
 .
   [ Sylvestre Ledru ]
   * New rc
   * Lower the debhelper dep to 10 for debian stretch
   * Rename ocaml-nox => ocaml-base (Closes: #1002609)
   * Remove Build-Conflicts: ocaml
Checksums-Sha1:
 4b8b5118ea0b24bc38f223648be82044e4547293 6887 
llvm-toolchain-13_13.0.1~+rc3-1~exp1.dsc
 3f774ad64230b6a8f71a56392cd19ef4cee7caed 121117204 
llvm-toolchain-13_13.0.1~+rc3.orig.tar.xz
 90571d6976885c38b13d71fb5c6cb9c75e4d10ea 148008 
llvm-toolchain-13_13.0.1~+rc3-1~exp1.debian.tar.xz
 a584093bc8595e56324c26fa9c144087c9a4d3fd 32549 
llvm-toolchain-13_13.0.1~+rc3-1~exp1_amd64.buildinfo
Checksums-Sha256:
 22370f6baec52776e93c8558b43c71ec018cdb55830dff2e77f928e8d13b97d3 6887 
llvm-toolchain-13_13.0.1~+rc3-1~exp1.dsc
 9a13c3f34f6c574f428efd863ab5de91f3826e4359342f5adcb12b8bf2e8110b 121117204 
llvm-toolchain-13_13.0.1~+rc3.orig.tar.xz
 ff61f3aa7fc4d4876b023207fb194172e4b80e0fcc4d8a6ed2aaefc148afb460 148008 
llvm-toolchain-13_13.0.1~+rc3-1~exp1.debian.tar.xz
 bf51244a44dbe1bc25d5184fd15405e3d5962c7e734f8d2393a03e21a4c2 32549 
llvm-toolchain-13_13.0.1~+rc3-1~exp1_amd64.buildinfo
Files:
 218b9740ab0a482c7069c8ae8b64417a 6887 devel optional 
llvm-toolchain-13_13.0.1~+rc3-1~exp1.dsc
 a0804eb928a0a7a731722aec3ef34d7f 121117204 devel optional 
llvm-toolchain-13_13.0.1~+rc3.orig.tar.xz
 49909baacd3554901529257582d7988a 148008 devel optional 
llvm-toolchain-13_13.0.1~+rc3-1~exp1.debian.tar.xz
 846b40530c6ea1f2322737df1a3290f6 32549 devel optional 
llvm-toolchain-13_13.0.1~+rc3-1~exp1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmHtaYkACgkQfmUo2nUv
G+EHJA/+MX6x/cemnEQ8NxdYF0LafWW1swHWvgRdFtnyDRdDr8rz3qURRDLYf3ZT

Bug#995360: marked as done (pytorch: autopkgtest regression: fft: ATen not compiled with MKL support)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jan 2022 14:37:46 +
with message-id 
and subject line Bug#995360: fixed in pytorch 1.8.1-3
has caused the Debian Bug report #995360,
regarding pytorch: autopkgtest regression: fft: ATen not compiled with MKL 
support
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.)


-- 
995360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytorch
Version: 1.8.1-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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

   passfail
pytorchfrom testing1.8.1-2
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

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

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

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

Paul

[0] You can see what packages were added from the second line of the log file
quoted below. The migration software adds source package from unstable to the
list if they are needed to install packages from pytorch/1.8.1-2. I.e. due to
versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=pytorch

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pytorch/15624807/log.gz

=== FAILURES ===
__ TestFFTCPU.test_stft_requires_complex_cpu ___

self = 
device = 'cpu'

def test_stft_requires_complex(self, device):
x = torch.rand(100)
>   y = x.stft(10, pad_mode='constant')

test_spectral_ops.py:939:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/torch/tensor.py:453: in stft
return torch.stft(self, n_fft, hop_length, win_length, window, center,
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

input = tensor([0., 0., 0., 0., 0., 0.0290, 0.4019, 0.2598, 
0.3666,
0.0583, 0.7006, 0.0518, 0.46810910, 0.2323,
0.7269, 0.1187, 0.3951, 0.7199, 0.7595, 0.5311, 0., 0., 0.,
0., 0.])
n_fft = 10, hop_length = None, win_length = None, window = None, center = True
pad_mode = 'constant', normalized = False, onesided = None
return_complex = None

def stft(input: Tensor, n_fft: int, hop_length: Optional[int] = None,
 win_length: Optional[int] = None, window: Optional[Tensor] = None,
 center: bool = True, pad_mode: str = 'reflect', normalized: bool = 
False,
 onesided: Optional[bool] = None,
 return_complex: Optional[bool] = None) -> Tensor:
r"""Short-time Fourier transform (STFT).

.. warning::
From version 1.8.0, :attr:`return_complex` must always be given
explicitly for real inputs and `return_complex=False` has been
deprecated. Strongly prefer `return_complex=True` as in a future
pytorch release, this function will only return complex tensors.

Note that :func:`torch.view_as_real` can be used to recover a real
tensor with an extra last dimension for real and imaginary 
components.

The STFT computes the Fourier transform of short overlapping windows of 
the
input. This giving frequency components of the signal as they change 
over
time. The interface of this function is modeled after the librosa_ stft 
function.

.. _librosa: https://librosa.org/doc/latest/generated/librosa.stft.html

Ignoring the optional batch dimension, this method computes the 
following
expression:

.. math::
X[m, \omega] = \sum_{k = 0}^{\text{win\_length-1}}%
\text{window}[k]\ \text{input}[m \times 
\text{hop\_length} + k]\ %
\exp\left(- j \frac{2 \pi \cdot \omega 
k}{\text{win\_length}}\right),

where :math:`m` is the index of the sliding window, and :math:`\omega` 
is
the frequency that :math:`0 \leq \omega < \text{n\_fft}`. 

Bug#994423: marked as done (pytorch: Baseline violation on armhf)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jan 2022 14:37:46 +
with message-id 
and subject line Bug#994423: fixed in pytorch 1.8.1-3
has caused the Debian Bug report #994423,
regarding pytorch: Baseline violation on 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.)


-- 
994423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994423
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytorch-vision
Version: 0.8.2-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

| I: pybuild base:232: python3.9 setup.py clean 
| Illegal instruction
| E: pybuild pybuild:353: clean: plugin distutils failed with: exit code=132: 
python3.9 setup.py clean 
| dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
code 13
| make: *** [debian/rules:6: clean] Error 25

https://buildd.debian.org/status/fetch.php?pkg=pytorch-vision=armhf=0.8.2-1%2Bb1=1631302732=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: pytorch
Source-Version: 1.8.1-3
Done: Mo Zhou 

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

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

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

Debian distribution maintenance software
pp.
Mo Zhou  (supplier of updated pytorch 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: Sun, 23 Jan 2022 09:14:58 -0500
Source: pytorch
Architecture: source
Version: 1.8.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Deep Learning Team 
Changed-By: Mo Zhou 
Closes: 994423 995360
Changes:
 pytorch (1.8.1-3) unstable; urgency=medium
 .
   * Add comments in d/rules on package maintainence.
   * Mask python spectral_ops test which requires MKL. (Closes: #995360)
   * Mask python binary_ufuncs autopkgtest.
   * Only build on modern 64-bit architectures. (Closes: #994423)
   * Add missing Dep libprotobuf-dev for libtorch-dev.
   * d/watch: Track releases instead of tags.
Checksums-Sha1:
 07136a31d06c00ec0cec92cc6881a22aa1c6d554 3338 pytorch_1.8.1-3.dsc
 0537963336f822286a1751a5ca5691bac1fbdc89 56724 pytorch_1.8.1-3.debian.tar.xz
 a3c651357d4a3f247efa16740fc6c4c6d5bbf2af 7513 pytorch_1.8.1-3_source.buildinfo
Checksums-Sha256:
 b90c09456b78cac04e045ad3e80303823d1a28dddc4f47014c059d63232431b4 3338 
pytorch_1.8.1-3.dsc
 8f7e4214dcbfdc0239131650d602dadc63488825e3e901f490ef85f9ad0fa4f7 56724 
pytorch_1.8.1-3.debian.tar.xz
 cfcdf978dd4a66f095e79e1708d5a16424efeee0b47c0d4a44001342977b8c3c 7513 
pytorch_1.8.1-3_source.buildinfo
Files:
 6e463e6053862150392eecd32bbb8d4d 3338 science optional pytorch_1.8.1-3.dsc
 9fbb319dac9469a9dba80955b637ffc3 56724 science optional 
pytorch_1.8.1-3.debian.tar.xz
 8d27ed3b196dccab6ebfde361071240c 7513 science optional 
pytorch_1.8.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAvFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAmHtY8MRHGx1bWluQGRl
Ymlhbi5vcmcACgkQYmRes19oaoojSg/2Kh5EwF9aRYNXaueOXB4sDcKThG0zd4vr
bD2Bzuw/HJ1oJCJcRZw4c/PYiMpTcKmHRUY7ekN7O/nu++YmxOen+8Objr/XSKs3
TQzDx8tiZRkeQNTiaYoAQ1HSZOccmthKBq1qUnrsX315BIKAHYXVH+6FOUBCt3yY
9j4nUUHtrJH1QLqXdzg238JGl++mzSL3mLcq+dZ9uRNXyYuvI0PMR6NlNrsZPiXI
D9jJD5IpbTEfvmQwFnvk948gLHNYBbfHDy+5xyZ7ar+DzwEMSjsYduIklf9/kafu
Vff1hHFtwhOdQCKrnb1uklJOJk7e3nDCgAP87Botf9IvdK1ojvtipF+W/h+B0hY2
PIVTh8YSp/0MGoxmN95q1y24vXNG4hQMvyNqShhYEuOZizspGkaV4CXcBc3O7ojk
2TmDu6QHjF5Cg68eXHce2THPGnIPjm5rI7tfWUU5uOSjiI6BaieZ3SE4zrH7bIvP
YUqk9OeStzuMyQAPlBNND70Q+p6jNZacClapNq2uGivWsYHAOlrFotTZIhZq5z6g
JcQKlihJDB/zD7LQX9AYmD5zdOK0VsRPZGBDeyMLGlH0yHRmT2CmV3S72cvGxFo9
B9dwbVQuWbhKd/fCfcc07uRxzdRJGddZl43li8SsofMRD0fGoE+f90uwfDiishBC
Q47MJuWI9Q==
=RAOI
-END PGP SIGNATURE End Message ---

Bug#995356: python-parameterized: autopkgtest regression: AssertionError in tearDownModule

[Paul Gevers]

Source: python-parameterized
Followup-For: Bug #995356

Hi,

As announced yesterday, I have uploaded an NMU to DELAYED/5 dropping
the autopkgtest. Please let me know if I should cancel that, but then
I expect a solution reasonably soon.

Paul
diff --git a/debian/changelog b/debian/changelog
index fdfb630..dbc842f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+python-parameterized (0.8.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop autopkgtest for now as it fails and this is blocking migration
+(See: #995356)
+
+ -- Paul Gevers   Sun, 23 Jan 2022 15:08:44 +0100
+
 python-parameterized (0.8.1-1) unstable; urgency=medium
 
   [ Debian Janitor ]
diff --git a/debian/tests/control b/debian/tests/control
deleted file mode 100644
index 0c55f37..000
--- a/debian/tests/control
+++ /dev/null
@@ -1,19 +0,0 @@
-Test-Command: set -e
- ; for py in $(py3versions -r 2>/dev/null)
- ; do cd "$AUTOPKGTEST_TMP"
- ; echo "Testing with $py (unittest):"
- ; $py -m unittest -v parameterized.test
- ; echo "Testing with $py (nose):"
- ; $py -m nose -v parameterized.test
- ; echo "Testing with $py (nose2):"
- ; $py -m nose2 -v parameterized.test
- ; echo "Testing with $py (pytest):"
- ; $py -m pytest -v --pyargs parameterized.test
- ; done
-Depends: python3-all,
- python3-mock,
- python3-nose,
- python3-nose2,
- python3-parameterized,
- python3-pytest
-Restrictions: allow-stderr

Bug#1000637: generating debian/control is *NOT* policy compliant

[Ondřej Surý]

That’s exactly how it’s done in the PHP packages. If you see a different 
content in the debian/control, it means the packages were not generated in the 
clean build environment.

Ondřej
--
Ondřej Surý  (He/Him)

> On 23. 1. 2022, at 15:09, Thomas Goirand  wrote:
> 
> Hi,
> 
> Looks like the php-* PECL packages are getting their debian/control generated 
> at build time from a debian/control.in.
> 
> If you didn't know, this is *NOT* policy compliant. The policy clearly says 
> source packages must have a not-generated debian/control in good shape 
> (though I haven't taken the time to find where this is written in the policy, 
> I just know it's forbidden...). Please stop doing this.
> 
> If you still need to generate it, then you can have a look how the Linux 
> kernel package does it. They generate the debian/control from control.in 
> thanks to some internal tooling, but save the debian/control in the generated 
> form in their source package. That may be a nice workaround, and the better 
> way to go for you.
> 
> Cheers,
> 
> Thomas Goirand (zigo)
> 

Bug#1000637: generating debian/control is *NOT* policy compliant

[Thomas Goirand]

Hi,

Looks like the php-* PECL packages are getting their debian/control 
generated at build time from a debian/control.in.


If you didn't know, this is *NOT* policy compliant. The policy clearly 
says source packages must have a not-generated debian/control in good 
shape (though I haven't taken the time to find where this is written in 
the policy, I just know it's forbidden...). Please stop doing this.


If you still need to generate it, then you can have a look how the Linux 
kernel package does it. They generate the debian/control from control.in 
thanks to some internal tooling, but save the debian/control in the 
generated form in their source package. That may be a nice workaround, 
and the better way to go for you.


Cheers,

Thomas Goirand (zigo)

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

[Debian Bug Tracking System]

Your message dated Sun, 23 Jan 2022 13:48:54 +
with message-id 
and subject line Bug#1002212: fixed in python-pyorick 1.4-4
has caused the Debian Bug report #1002212,
regarding python-pyorick: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p "3.10 3.9" returned exit code 13
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
> I: pybuild base:237: python3.10 setup.py config 
> running config
> I: pybuild base:237: python3.9 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
> I: pybuild base:237: /usr/bin/python3.10 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_pyorick/build/pyorick
> copying pyorick/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_pyorick/build/pyorick
> copying pyorick/test_pyorick.py -> 
> /<>/.pybuild/cpython3_3.10_pyorick/build/pyorick
> copying pyorick/pyorick.py -> 
> /<>/.pybuild/cpython3_3.10_pyorick/build/pyorick
> copying pyorick/pyorick.i0 -> 
> /<>/.pybuild/cpython3_3.10_pyorick/build/pyorick
> I: pybuild base:237: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_pyorick/build/pyorick
> copying pyorick/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_pyorick/build/pyorick
> copying pyorick/test_pyorick.py -> 
> /<>/.pybuild/cpython3_3.9_pyorick/build/pyorick
> copying pyorick/pyorick.py -> 
> /<>/.pybuild/cpython3_3.9_pyorick/build/pyorick
> copying pyorick/pyorick.i0 -> 
> /<>/.pybuild/cpython3_3.9_pyorick/build/pyorick
>dh_auto_test -O--buildsystem=pybuild
> dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 
> in use)
> I: pybuild base:237: cd 
> /<>/.pybuild/cpython3_3.10_pyorick/build; python3.10 -m unittest 
> discover -v 
> pyorick (unittest.loader._FailedTest) ... ERROR
> 
> ==
> ERROR: pyorick (unittest.loader._FailedTest)
> --
> ImportError: Failed to import test module: pyorick
> Traceback (most recent call last):
>   File "/usr/lib/python3.10/unittest/loader.py", line 470, in _find_test_path
> package = self._get_module_from_name(name)
>   File "/usr/lib/python3.10/unittest/loader.py", line 377, in 
> _get_module_from_name
> __import__(name)
>   File 
> "/<>/.pybuild/cpython3_3.10_pyorick/build/pyorick/__init__.py", 
> line 190, in 
> from .pyorick import *
>   File 
> "/<>/.pybuild/cpython3_3.10_pyorick/build/pyorick/pyorick.py", 
> line 29, in 
> from collections import Sequence, Mapping
> ImportError: cannot import name 'Sequence' from 'collections' 
> (/usr/lib/python3.10/collections/__init__.py)
> 
> 
> --
> Ran 1 test in 0.000s
> 
> FAILED (errors=1)
> E: pybuild pybuild:355: test: plugin distutils failed with: exit code=1: cd 
> /<>/.pybuild/cpython3_3.10_pyorick/build; python3.10 -m unittest 
> discover -v 
> I: pybuild base:237: cd /<>/.pybuild/cpython3_3.9_pyorick/build; 
> python3.9 -m unittest discover -v 
> test_active (pyorick.test_pyorick.TestCodec)
> Check codec for active messages. ... 
> /<>/.pybuild/cpython3_3.9_pyorick/build/pyorick/pyorick.py:1304: 
> DeprecationWarning: tostring() is deprecated. Use tobytes() instead.
>   s = a.tostring().decode('iso_8859_1')
> ok
> test_arrays (pyorick.test_pyorick.TestCodec)
> Check that array types can be encoded and decoded. ... ok
> test_bad (pyorick.test_pyorick.TestCodec)
> Check that unencodable types cannot be encoded. ... 
> /<>/.pybuild/cpython3_3.9_pyorick/build/pyorick/pyorick.py:1497: 
> DeprecationWarning: tostring() is deprecated. Use tobytes() instead.
>   return 

Bug#967010:

[Mubariz Qaribov]

Processed: Re: elan: error: failed to select a version for the requirement `itertools = "^0.9.0"`

[Debian Bug Tracking System]

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

> tags 999575 +patch
Bug #999575 [src:elan] elan: error: failed to select a version for the 
requirement `itertools = "^0.9.0"`
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#999575: elan: error: failed to select a version for the requirement `itertools = "^0.9.0"`

[Peter Green]

tags 999575 +patch
thanks

The attatched patch fixes up the dependencies so that elan will build 
successfully both in current sid and in sid after the upcoming rand

transition enters sid.


diff -Nru elan-1.0.6/debian/changelog elan-1.0.6/debian/changelog
--- elan-1.0.6/debian/changelog 2021-05-10 20:15:09.0 +
+++ elan-1.0.6/debian/changelog 2022-01-22 14:24:59.0 +
@@ -1,3 +1,15 @@
+elan (1.0.6-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Relax cargo dependencies on itertools and rand ( Closes: 999575 ).
+  * Remove cargo dependency on the "vendored" feature of the openssl crate,
+it has been removed in current Debian packaging of that crate (and was a
+no-op before that)
+  * Change Debian dependency to depend on librust-semver-0.9-dev
+instead of librust-semver-dev.
+
+ -- Peter Michael Green   Sat, 22 Jan 2022 14:24:59 +
+
 elan (1.0.6-1) unstable; urgency=medium
 
   * Initial release (Closes: #991801)
diff -Nru elan-1.0.6/debian/control elan-1.0.6/debian/control
--- elan-1.0.6/debian/control   2021-05-10 20:15:09.0 +
+++ elan-1.0.6/debian/control   2022-01-22 14:24:59.0 +
@@ -32,7 +32,7 @@
  librust-curl-dev,
  librust-walkdir-dev,
  librust-openssl-dev,
- librust-semver-dev,
+ librust-semver-0.9-dev,
  librust-backtrace-dev,
  librust-aho-corasick-dev,
  librust-thread-local-dev,
diff -Nru elan-1.0.6/debian/patches/dependencies.patch 
elan-1.0.6/debian/patches/dependencies.patch
--- elan-1.0.6/debian/patches/dependencies.patch2021-05-10 
20:15:09.0 +
+++ elan-1.0.6/debian/patches/dependencies.patch2022-01-22 
14:24:59.0 +
@@ -2,21 +2,23 @@
 Forwarded: not-needed
 Author: Christopher Hoskin 
 Last-Update: 2021-08-02
 a/Cargo.toml
-+++ b/Cargo.toml
-@@ -29,34 +29,28 @@
+Index: elan-1.0.6/Cargo.toml
+===
+--- elan-1.0.6.orig/Cargo.toml
 elan-1.0.6/Cargo.toml
+@@ -29,34 +29,28 @@ elan-utils = { path = "src/elan-utils" }
  download = { path = "src/download" }
  clap = "2.33.3"
  error-chain = "0.12.4"
 -itertools = "0.10.0"
 -libc = "0.2.82"
-+itertools = "0.9.0"
++itertools = ">= 0.9.0"
  markdown = "0.3.0"
 -rand = "0.8.2"
 -regex = "1.4.3"
 -remove_dir_all = "0.6.1"
 +libc = "0.2.80"
-+rand = "0.7.3"
++rand = ">= 0.7.3"
 +regex = "1.3.7"
 +remove_dir_all = "0.5.1"
  same-file = "1.0.6"
@@ -57,9 +59,11 @@
  
  [lib]
  name = "elan"
 a/src/download/Cargo.toml
-+++ b/src/download/Cargo.toml
-@@ -15,8 +15,8 @@
+Index: elan-1.0.6/src/download/Cargo.toml
+===
+--- elan-1.0.6.orig/src/download/Cargo.toml
 elan-1.0.6/src/download/Cargo.toml
+@@ -15,8 +15,8 @@ reqwest-backend = ["reqwest", "env_proxy
  
  [dependencies]
  error-chain = "0.12.4"
@@ -70,9 +74,11 @@
  openssl = { version = "0.10", features = ["vendored"], optional = true }
  env_proxy = { version = "0.4.1", optional = true }
  lazy_static = { version = "1.4.0", optional = true }
 a/src/elan-dist/Cargo.toml
-+++ b/src/elan-dist/Cargo.toml
-@@ -9,28 +9,23 @@
+Index: elan-1.0.6/src/elan-dist/Cargo.toml
+===
+--- elan-1.0.6.orig/src/elan-dist/Cargo.toml
 elan-1.0.6/src/elan-dist/Cargo.toml
+@@ -9,28 +9,23 @@ build = "build.rs"
  license = "MIT OR Apache-2.0"
  
  [dependencies]
@@ -83,7 +89,7 @@
 -tar = "0.4.33"
 -flate2 = "1.0.14"
 +regex = "1.3.7"
-+itertools = "0.9.0"
++itertools = ">= 0.9.0"
 +url = "2.1.1"
 +tar = "0.4.26"
 +flate2 = "1.0.13"
@@ -113,9 +119,11 @@
  
  [lib]
  name = "elan_dist"
 a/src/elan-utils/Cargo.toml
-+++ b/src/elan-utils/Cargo.toml
-@@ -10,20 +10,15 @@
+Index: elan-1.0.6/src/elan-utils/Cargo.toml
+===
+--- elan-1.0.6.orig/src/elan-utils/Cargo.toml
 elan-1.0.6/src/elan-utils/Cargo.toml
+@@ -10,20 +10,15 @@ license = "MIT OR Apache-2.0"
  [dependencies]
  download = { path = "../download" }
  error-chain = "0.12.4"
@@ -123,7 +131,7 @@
 -rand = "0.8.3"
 -remove_dir_all = "0.7.0"
 +libc = "0.2.80"
-+rand = "0.7.3"
++rand = ">= 0.7.3"
 +remove_dir_all = "0.5.1"
  scopeguard = "1.1.0"
 -semver = "0.11.0"
@@ -131,13 +139,14 @@
 -toml = "0.5.8"
 -url = "2.2.1"
 -curl = "0.4.34"
+-openssl = { version = "0.10", features = ["vendored"] }
+-regex = "1.4.3"
 +semver = "0.9.0"
 +sha2 = "0.9.2"
 +toml = "0.5.5"
 +url = "2.1.1"
 +curl = "0.4.33"
- openssl = { version = "0.10", features = ["vendored"] }
--regex = "1.4.3"
++openssl = { version = "0.10" }
 +regex = "1.3.7"
  dirs = "3.0.1"
 -

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

[Debian Bug Tracking System]

Your message dated Sun, 23 Jan 2022 13:15:52 +0100
with message-id <87czkive9z@msgid.hilluzination.de>
and subject line This has been closed in libguestfs 1.46.x
has caused the Debian Bug report #1002634,
regarding 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.)


-- 
1002634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libguestfs
Version: 1:1.44.2-1.1
Severity: important
Tags: ftbfs

Dear Maintainer,

Your package FTBFS with OCaml 4.13.1 with the following error:
> File "../../../customize/perl_edit.ml", line 30, characters 2-13:
> 30 |   c_edit_file (verbose ()) g (Guestfs.c_pointer g) file expr
>^^^
> Error (warning 6 [labels-omitted]): label verbose was omitted in the 
> application of this function.
> make[5]: *** [Makefile:3266: perl_edit.cmx] Error 2

Packages rebuilt with OCaml 4.13.1 are available at:

  https://ocaml.debian.net/transitions/ocaml-4.13.1/


Cheers,

-- 
Stéphane

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

Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
control: fixed -1 1:1.46.2-1

Apparently, OCaml-related FTBFS is no longer a problem; closing this bug.--- End Message ---

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

[Debian Bug Tracking System]

Your message dated Sun, 23 Jan 2022 12:43:40 +0100
with message-id 
and subject line Re: Bug#1002357: flask-login: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit 
code 13
has caused the Debian Bug report #1002357,
regarding flask-login: FTBFS: dh_auto_test: error: pybuild --test --test-pytest 
-i python{version} -p "3.10 3.9" returned exit code 13
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3,sphinxdoc --buildsystem pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:237: python3.10 setup.py config 
> running config
> I: pybuild base:237: python3.9 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:237: /usr/bin/python3.10 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_flask-login/build/flask_login
> copying flask_login/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_flask-login/build/flask_login
> copying flask_login/__about__.py -> 
> /<>/.pybuild/cpython3_3.10_flask-login/build/flask_login
> copying flask_login/login_manager.py -> 
> /<>/.pybuild/cpython3_3.10_flask-login/build/flask_login
> copying flask_login/mixins.py -> 
> /<>/.pybuild/cpython3_3.10_flask-login/build/flask_login
> copying flask_login/_compat.py -> 
> /<>/.pybuild/cpython3_3.10_flask-login/build/flask_login
> copying flask_login/signals.py -> 
> /<>/.pybuild/cpython3_3.10_flask-login/build/flask_login
> copying flask_login/config.py -> 
> /<>/.pybuild/cpython3_3.10_flask-login/build/flask_login
> copying flask_login/test_client.py -> 
> /<>/.pybuild/cpython3_3.10_flask-login/build/flask_login
> copying flask_login/utils.py -> 
> /<>/.pybuild/cpython3_3.10_flask-login/build/flask_login
> I: pybuild base:237: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_flask-login/build/flask_login
> copying flask_login/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_flask-login/build/flask_login
> copying flask_login/__about__.py -> 
> /<>/.pybuild/cpython3_3.9_flask-login/build/flask_login
> copying flask_login/login_manager.py -> 
> /<>/.pybuild/cpython3_3.9_flask-login/build/flask_login
> copying flask_login/mixins.py -> 
> /<>/.pybuild/cpython3_3.9_flask-login/build/flask_login
> copying flask_login/_compat.py -> 
> /<>/.pybuild/cpython3_3.9_flask-login/build/flask_login
> copying flask_login/signals.py -> 
> /<>/.pybuild/cpython3_3.9_flask-login/build/flask_login
> copying flask_login/config.py -> 
> /<>/.pybuild/cpython3_3.9_flask-login/build/flask_login
> copying flask_login/test_client.py -> 
> /<>/.pybuild/cpython3_3.9_flask-login/build/flask_login
> copying flask_login/utils.py -> 
> /<>/.pybuild/cpython3_3.9_flask-login/build/flask_login
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild pybuild:286: cp -r /<>/test_login.py 
> /<>/.pybuild/cpython3_3.10_flask-login/build
> I: pybuild base:237: cd 
> /<>/.pybuild/cpython3_3.10_flask-login/build; python3.10 -m 
> pytest -v
> = test session starts 
> ==
> platform linux -- Python 3.10.1, pytest-6.2.5, py-1.10.0, pluggy-0.13.0 -- 
> /usr/bin/python3.10
> cachedir: .pytest_cache
> rootdir: /<>
> collecting ... collected 117 items
> 
> test_login.py::AboutTestCase::test_have_about_data PASSED[  
> 0%]
> test_login.py::StaticTestCase::test_static_loads_anonymous PASSED[  
> 1%]
> test_login.py::StaticTestCase::test_static_loads_without_accessing_session 
> PASSED [  2%]
> test_login.py::InitializationTestCase::test_class_init PASSED[  
> 3%]
> test_login.py::InitializationTestCase::test_init_app PASSED  [  
> 4%]
> test_login.py::InitializationTestCase::test_login_disabled_is_set PASSED [  
> 5%]
> test_login.py::InitializationTestCase::test_no_user_loader_raises PASSED [  
> 5%]
> test_login.py::MethodViewLoginTestCase::test_options_call_exempt PASSED  [  
> 6%]
> 

Bug#993620: marked as done (vip-manager: test failure with some network configurations)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jan 2022 11:03:45 +
with message-id 
and subject line Bug#993620: fixed in vip-manager 1.0.1-5
has caused the Debian Bug report #993620,
regarding vip-manager: test failure with some network configurations
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.)


-- 
993620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vip-manager
Version: 1.0.1-4
Severity: normal
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu impish

Dear Maintainer,

vip-manager behavior_test can fail, depending on the device network
configuration.  If the test device has a network device of type ether
and a zero hardware address, and it selects this network device as the
one to use, the tests will fail.

Example failure:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/v/vip-manager/20210901_213607_5779b@/log.gz
2021/09/01 21:35:37 Problems with generating the virtual ip manager: Cannot run 
vip-manager on the loopback device
as its hardware address is the local address (00:00:00:00:00:00),
which prohibits sending of gratuitous ARP messages

Here is abbreviated output of 'ip link show' for one such test device:
3: gretap0@NONE:  mtu 1476 qdisc noop state DOWN mode 
DEFAULT group default qlen 1000
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
44262: eth0@if44263:  mtu 1458 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
link/ether 00:16:3e:0f:a3:f7 brd ff:ff:ff:ff:ff:ff link-netnsid 0

In this example, gretap0 will be the chosen network device, but will
fail at runtime of vip-manager due to the all-zeros mac address.
Instead, eth0 should be chosen.

Please see the attached patch, which I will be looking to get integrated
to Ubuntu, which seems to address the above problem for Ubuntu armhf
autopkgtest.

This bug report was also filed in Ubuntu and can be found at
https://launchpad.net/bugs/1942375

-Dan
Description: Improved test device selection
Author:  Dan Bungert 
Bug-Ubuntu:  https://bugs.launchpad.net/bugs/1942375
Last-Update: 2021-09-03
--- a/test/behaviour_test.sh
+++ b/test/behaviour_test.sh
@@ -7,9 +7,29 @@
 NC='\033[0m' # No Color
 
 # testing parameters
-dev=`ip link show | grep -B1 ether | cut -d ":" -f2 | head -n1 | cut -d " " -f2 | sed s/@.*//`
 vip=10.0.2.123
 
+function get_dev {
+# select a suitable device for testing purposes
+# * a device that is an "ether"
+# * and isn't a nil hardware address
+
+# https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
+ARPHRD_ETHER=1
+
+for dev in /sys/class/net/* ; do
+test ! -e "$dev/address" && continue
+test "$(cat $dev/address)" = "00:00:00:00:00:00" && continue
+test "$(cat $dev/type)" != "$ARPHRD_ETHER" && continue
+basename "$dev"
+break
+done
+}
+
+dev="$(get_dev)"
+# prerequisite test - do we have a suitable device?
+test -n "$dev"
+
 #cleanup
 function cleanup {
 if test -f .ncatPid
@@ -35,7 +55,7 @@
 }
 trap cleanup EXIT
 
-# prerequisite test 0: vip should not yet be registered
+# prerequisite test: vip should not yet be registered
 ! ip address show dev $dev | grep $vip
 
 # run etcd with podman/docker maybe?
--- End Message ---
--- Begin Message ---
Source: vip-manager
Source-Version: 1.0.1-5
Done: Michael Banck 

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

Debian distribution maintenance software
pp.
Michael Banck  (supplier of updated vip-manager 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 23 Jan 2022 11:35:21 +0100
Source: vip-manager
Architecture: source
Version: 1.0.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 
Changed-By: Michael Banck 
Closes: 993620
Changes:
 vip-manager (1.0.1-5) unstable; urgency=medium
 .
   * debian/patches/select_valid_net_device.patch: New patch, makes the
 behaviour test try harder to select a valid network device, taken from
 upstream 

Bug#993620: marked as pending in vip-manager

[Michael Banck]

Control: tag -1 pending

Hello,

Bug #993620 in vip-manager 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/postgresql/vip-manager/-/commit/cb1f5580ae7623d129f1d9c53df85d4e190300bd


* debian/patches/select_valid_net_device.patch: New patch, makes the
behaviour test try harder to select a valid network device, taken from
upstream commit cd9ab29 (Closes: #993620).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/993620

Processed: Bug#993620 marked as pending in vip-manager

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #993620 [vip-manager] vip-manager: test failure with some network 
configurations
Ignoring request to alter tags of bug #993620 to the same tags previously set

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

Processed: #1002336: forwarded upstream

[Debian Bug Tracking System]

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

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

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

Processed: tagging 993620

[Debian Bug Tracking System]

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

> tags 993620 + pending
Bug #993620 [vip-manager] vip-manager: test failure with some network 
configurations
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#999334: marked as done (android-platform-tools: FTBFS: error: no member named 'unique_lock' in namespace 'std')

[Debian Bug Tracking System]

Your message dated Sun, 23 Jan 2022 10:03:41 +
with message-id 
and subject line Bug#999334: fixed in android-platform-tools 29.0.6-2
has caused the Debian Bug report #999334,
regarding android-platform-tools: FTBFS: error: no member named 'unique_lock' 
in namespace 'std'
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.)


-- 
999334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999334
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: android-platform-tools
Version: 29.0.6-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sramac...@debian.org

| clang++ -c -o system/core/liblog/event_tag_map.o 
system/core/liblog/event_tag_map.cpp -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fPIC -std=gnu++17 -Wdate-time -D_FORTIFY_SOURCE=2 
-DNDEBUG -UDEBUG -Isystem/core/liblog/include -Isystem/core/include 
-Isystem/core/base/include -I/usr/include/android -DLIBLOG_LOG_TAG=1006 
-DFAKE_LOG_DEVICE=1 -DSNET_EVENT_LOG_TAG=1397638484 
| system/core/liblog/logger_write.cpp:147:20: error: no member named 
'unique_lock' in namespace 'std'
|   auto lock = std::unique_lock{default_tag_lock};
|   ~^
| system/core/liblog/logger_write.cpp:147:31: error: expected ';' at end of 
declaration
|   auto lock = std::unique_lock{default_tag_lock};
|   ^
|   ;
| system/core/liblog/logger_write.cpp:170:20: error: no member named 
'unique_lock' in namespace 'std'
|   auto lock = std::unique_lock{logger_function_lock};
|   ~^
| system/core/liblog/logger_write.cpp:170:31: error: expected ';' at end of 
declaration
|   auto lock = std::unique_lock{logger_function_lock};
|   ^
|   ;
| system/core/liblog/logger_write.cpp:187:20: error: no member named 
'unique_lock' in namespace 'std'
|   auto lock = std::unique_lock{aborter_function_lock};
|   ~^
| system/core/liblog/logger_write.cpp:187:31: error: expected ';' at end of 
declaration
|   auto lock = std::unique_lock{aborter_function_lock};
|   ^
|   ;
| 6 errors generated.

See
https://buildd.debian.org/status/fetch.php?pkg=android-platform-tools=amd64=29.0.6-1%2Bb1=1636368880=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: android-platform-tools
Source-Version: 29.0.6-2
Done: Roger Shimizu 

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

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

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

Debian distribution maintenance software
pp.
Roger Shimizu  (supplier of updated android-platform-tools 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 23 Jan 2022 18:03:24 +0900
Source: android-platform-tools
Binary: adb fastboot etc1tool dmtracedump hprof-conv
Architecture: source
Version: 29.0.6-2
Distribution: unstable
Urgency: medium
Maintainer: Android Tools Maintainers 

Changed-By: Roger Shimizu 
Description:
 adb- Android Debug Bridge
 dmtracedump - Generates graphical call-stack diagrams from Android trace logs
 etc1tool   - ETC1 conversion tool
 fastboot   - Android fastboot tool
 hprof-conv - HPROF Converter
Closes: 999334
Changes:
 android-platform-tools (29.0.6-2) unstable; urgency=medium
 .
   * Team upload.
   * debian/control:
 - Remove unused B-D: debhelper (>= 11).
 - Use clang for all ARCHs.
   * debian/patches:
 - Update to adapt patch requirement for gbp pq command:
   + debian/patches/system/core/stub-out-fastdeploy.patch
 - To fix ftbfs issues (Closes: #999334):
   + Update: debian/patches/art/fix-standard-namespace-errors.patch
   + Update: debian/patches/system/core/add-missing-headers.patch
   + Add: debian/patches/system/core/fix-standard-namespace-errors.patch
 - Cherry-pick patch from upstream:
   + Switch to an assembler macro for CFI_RESTORE_STATE_AND_DEF_CFA.
Checksums-Sha1:
 

Processed: bug 993620 is forwarded to https://github.com/cybertec-postgresql/vip-manager/pull/76

[Debian Bug Tracking System]

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

> forwarded 993620 https://github.com/cybertec-postgresql/vip-manager/pull/76
Bug #993620 [vip-manager] vip-manager: test failure with some network 
configurations
Set Bug forwarded-to-address to 
'https://github.com/cybertec-postgresql/vip-manager/pull/76'.
> thanks
Stopping processing here.

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