Bug#1012106: marked as done (libreflectasm-java: FTBFS with OpenJDK 17 due to test failures)

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2022 07:34:04 +
with message-id 
and subject line Bug#1012106: fixed in libreflectasm-java 1.11.9+dfsg-2
has caused the Debian Bug report #1012106,
regarding libreflectasm-java: FTBFS with OpenJDK 17 due to test failures
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.)


-- 
1012106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libreflectasm-java
Version: 1.11.6+dfsg-1
Severity: important
Tags: ftbfs sid bookworm
User: debian-j...@lists.debian.org
Usertags: default-java17

libreflectasm-java fails to build with OpenJDK 17, several tests fail (maybe 
due to illegal reflective accesses?) :


  [INFO] ---
  [INFO]  T E S T S
  [INFO] ---
  [INFO] Running com.esotericsoftware.reflectasm.MethodAccessTest
  [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.043 
s - in com.esotericsoftware.reflectasm.MethodAccessTest
  [INFO] Running com.esotericsoftware.reflectasm.ClassLoaderTest
  [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 
s - in com.esotericsoftware.reflectasm.ClassLoaderTest
  [INFO] Running com.esotericsoftware.reflectasm.ConstructorAccessTest
  Unexpected exception happened: java.lang.RuntimeException: Class cannot be 
created (the no-arg constructor is protected or package-protected, and its 
ConstructorAccess could not be defined in the same class loader): 
com.esotericsoftware.reflectasm.ConstructorAccessTest$HasProtectedConstructor
  Unexpected exception happened: java.lang.RuntimeException: Class cannot be 
created (the no-arg constructor is protected or package-protected, and its 
ConstructorAccess could not be defined in the same class loader): 
com.esotericsoftware.reflectasm.ConstructorAccessTest$HasPublicConstructor
  Expected exception happened: java.lang.RuntimeException: Class cannot be 
created (missing no-arg constructor): 
com.esotericsoftware.reflectasm.ConstructorAccessTest$HasArgumentConstructor
  Unexpected exception happened: java.lang.RuntimeException: Class cannot be 
created (the no-arg constructor is protected or package-protected, and its 
ConstructorAccess could not be defined in the same class loader): 
com.esotericsoftware.reflectasm.ConstructorAccessTest$HasPackageProtectedConstructor
  Expected exception happened: java.lang.RuntimeException: Class cannot be 
created (the no-arg constructor is private): 
com.esotericsoftware.reflectasm.ConstructorAccessTest$HasPrivateConstructor
  [ERROR] Tests run: 7, Failures: 3, Errors: 1, Skipped: 0, Time elapsed: 0.01 
s <<< FAILURE! - in com.esotericsoftware.reflectasm.ConstructorAccessTest
  [ERROR] 
testHasProtectedConstructor(com.esotericsoftware.reflectasm.ConstructorAccessTest)
  Time elapsed: 0.004 s  <<< FAILURE!
  junit.framework.AssertionFailedError
  at 
com.esotericsoftware.reflectasm.ConstructorAccessTest.testHasProtectedConstructor(ConstructorAccessTest.java:74)
  
  [ERROR] 
testHasPublicConstructor(com.esotericsoftware.reflectasm.ConstructorAccessTest) 
 Time elapsed: 0.001 s  <<< FAILURE!
  junit.framework.AssertionFailedError
  at 
com.esotericsoftware.reflectasm.ConstructorAccessTest.testHasPublicConstructor(ConstructorAccessTest.java:98)
  
  [ERROR] 
testPackagePrivateNewInstance(com.esotericsoftware.reflectasm.ConstructorAccessTest)
  Time elapsed: 0.001 s  <<< ERROR!
  java.lang.RuntimeException: Class cannot be created (the no-arg constructor 
is protected or package-protected, and its ConstructorAccess could not be 
defined in the same class loader): 
com.esotericsoftware.reflectasm.ConstructorAccessTest$PackagePrivateClass
  at 
com.esotericsoftware.reflectasm.ConstructorAccessTest.testPackagePrivateNewInstance(ConstructorAccessTest.java:31)
  
  [ERROR] 
testHasPackageProtectedConstructor(com.esotericsoftware.reflectasm.ConstructorAccessTest)
  Time elapsed: 0.001 s  <<< FAILURE!
  junit.framework.AssertionFailedError
  at 
com.esotericsoftware.reflectasm.ConstructorAccessTest.testHasPackageProtectedConstructor(ConstructorAccessTest.java:86)
  
  [INFO] Running com.esotericsoftware.reflectasm.FieldAccessTest
  [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - 
in com.esotericsoftware.reflectasm.FieldAccessTest
  [INFO]
  [INFO] Results:
  [INFO]
  [ERROR] Failures:
  [ERROR]   ConstructorAccessTest.testHasPackageProtectedConstructor:86
  [ERROR]   ConstructorAccessTest.testHasPro

Bug#1023839: ardour: Ardour won't start

[raffaele morelli]

Package: ardour
Version: 1:7.0.0+ds0-3
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: raffaele.more...@gmail.com

Ardour doesn't start

/usr/lib/ardour7/ardour-7.0.0~ds0: symbol lookup error: 
/usr/lib/ardour7/libardour.so.3: undefined symbol: 
_ZNK10RubberBand19RubberBandStretcher20getPreferredStartPadEv




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

Kernel: Linux 6.0.0-2-rt-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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

Versions of packages ardour depends on:
ii  ardour-data  1:7.0.0+ds0-3
ii  ardour-lv2-plugins   1:7.0.0+ds0-3
ii  libarchive13 3.6.0-1
ii  libasound2   1.2.7.2-1
ii  libatkmm-1.6-1v5 2.28.3-1
ii  libaubio50.4.9-4.2+b1
ii  libc62.36-4
ii  libcairo21.16.0-6
ii  libcairomm-1.0-1v5   1.14.4-1
ii  libcurl3-gnutls  7.86.0-1
ii  libcwiid10.6.91-4
ii  libdbus-1-3  1.14.4-1
ii  libfftw3-single3 3.3.8-2
ii  libfluidsynth3   2.3.0-1+b1
ii  libfontconfig1   2.13.1-4.5
ii  libgcc-s112.2.0-9
ii  libgdk-pixbuf-2.0-0  2.42.9+dfsg-1
ii  libglib2.0-0 2.74.1-1
ii  libglibmm-2.4-1v52.66.5-1
ii  libgtk2.0-0  2.24.33-2
ii  libgtkmm-2.4-1v5 1:2.24.5-4+b1
ii  liblilv-0-0  0.24.14-1
ii  liblo7   0.31-1
ii  liblrdf0 0.6.1-3
ii  libltc11 1.3.2-1
ii  libpango-1.0-0   1.50.10+ds-1
ii  libpangocairo-1.0-0  1.50.10+ds-1
ii  libpangoft2-1.0-01.50.10+ds-1
ii  libpangomm-1.4-1v5   2.46.3-1
ii  libpulse016.1+dfsg1-2+b1
ii  libqm-dsp0   1.7.1-5
ii  libreadline8 8.2-1.1
ii  librubberband2   1:2.0.2-dmo1
ii  libsamplerate0   0.2.2-2
ii  libsigc++-2.0-0v52.10.8-1
ii  libsndfile1  1.1.0-3+b1
ii  libstdc++6   12.2.0-9
ii  libsuil-0-0  1:0.10.10-dmo1
ii  libtag1v51.13-1
ii  libusb-1.0-0 2:1.0.26-1
ii  libvamp-hostsdk3v5   1:2.10.0-dmo1
ii  libvamp-sdk2v5   1:2.10.0-dmo1
ii  libwebsockets17  4.1.6-3
ii  libx11-6 2:1.8.1-2
ii  libxml2  2.9.14+dfsg-1+b1

Versions of packages ardour recommends:
ii  ardour-video-timeline  1:7.0.0+ds0-3

ardour suggests no packages.

-- no debconf information

Bug#1020135: numpy: FTBFS: AttributeError: 'UnixCCompiler' object has no attribute 'cxx_compiler'

[Sandro Tosi]

On Fri, Nov 4, 2022 at 4:30 PM Nilesh Patra  wrote:
>
> Control: tags -1 patch
>
> This was as simple as a reorder (again same as many py packages)

i decided to go with this solution:
https://salsa.debian.org/python-team/packages/numpy/-/commit/0f4a34b1992b421d803b2ce90eb84b52bc986511


-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Bug#1018818: bpfcc: FTBFS with libbpf 1.0.0

[Vasudev Kamath]

Control: fixed -1 0.25.0+ds-1

Hi Sudip,

Thanks for the report new upstream release is fixing this issue and I've
already uploaded new version and is building fine against all release
architecture. So closing this bug.

Thanks and Regards,
Vasudev

Bug#1018818: marked as done (bpfcc: FTBFS with libbpf 1.0.0)

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2022 09:25:11 +0530
with message-id <87cz9uqh5s@debian.org>
and subject line Re: bpfcc: FTBFS with libbpf 1.0.0
has caused the Debian Bug report #1018818,
regarding bpfcc: FTBFS with libbpf 1.0.0
to be marked as done.

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

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


-- 
1018818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bpfcc
Version: 0.24.0+ds-1
Severity: important
X-Debbugs-Cc: sudipm.mukher...@gmail.com
Tags: ftbfs
Usertags: libbpf1

Dear Maintainer,

bpfcc FTBFS with libbpf 1.0.0 (available in experimental).
These are some of the errors from the build log:

In file included from /<>/src/cc/bcc_libbpf_inc.h:5,
 from /<>/src/cc/libbpf.c:57:
/usr/include/bpf/btf.h: In function ‘btf_enum64_value’:
/usr/include/bpf/btf.h:496:25: error: invalid use of undefined type ‘const 
struct btf_enum64’
  496 | return ((__u64)e->val_hi32 << 32) | e->val_lo32;
  | ^~


/<>/src/cc/libbpf.c: In function ‘libbpf_bpf_map_create’:
/<>/src/cc/libbpf.c:304:28: error: invalid use of undefined type 
‘struct bpf_create_map_attr’
  304 |   p.map_flags = create_attr->map_flags;
  |^~


/<>/src/cc/libbpf.c: In function ‘bcc_create_map’:
/<>/src/cc/libbpf.c:376:10: error: variable ‘attr’ has initializer 
but incomplete type
  376 |   struct bpf_create_map_attr attr = {};
  |  ^~~
/<>/src/cc/libbpf.c:376:30: error: storage size of ‘attr’ isn’t 
known
  376 |   struct bpf_create_map_attr attr = {};
  |  ^~~~


/<>/src/cc/libbpf.c: In function ‘libbpf_bpf_prog_load’:
/<>/src/cc/libbpf.c:640:37: error: invalid use of undefined type 
‘const struct bpf_load_program_attr’
  640 |   p.expected_attach_type = load_attr->expected_attach_type;
  | ^~


In file included from /<>/src/cc/bcc_libbpf_inc.h:5,
 from /<>/src/cc/libbpf.c:57:
/usr/include/bpf/btf.h: In function ‘btf_enum64_value’:
removing 'bcc-0.24.0' (and everything under it)
/usr/include/bpf/btf.h:496:25: error: invalid use of undefined type ‘const 
struct btf_enum64’
  496 | return ((__u64)e->val_hi32 << 32) | e->val_lo32;
  | ^~


/<>/src/cc/libbpf.c: In function ‘bpf_attach_xdp’:
/<>/src/cc/libbpf.c:1549:9: warning: implicit declaration of 
function ‘bpf_set_link_xdp_fd’; did you mean ‘bpf_link__fd’? 
[-Wimplicit-function-declaration]
 1549 |   ret = bpf_set_link_xdp_fd(ifindex, progfd, flags);
  | ^~~
  | bpf_link__fd


-- 
Regards
Sudip
--- End Message ---
--- Begin Message ---

Control: fixed -1 0.25.0+ds-1

Hi Sudip,

Thanks for the report new upstream release is fixing this issue and I've
already uploaded new version and is building fine against all release
architecture. So closing this bug.

Thanks and Regards,
Vasudev--- End Message ---

Processed: Re: bpfcc: FTBFS with libbpf 1.0.0

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.25.0+ds-1
Bug #1018818 [src:bpfcc] bpfcc: FTBFS with libbpf 1.0.0
Marked as fixed in versions bpfcc/0.25.0+ds-1.

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

Bug#1000955: libkf5globalaccel-bin: /usr/bin/kglobalaccel5 eats up huge amount of CPU after suspend

[Patrick Franz]

Hi Filippo,

I have noticed a similar behaviour. However, the behaviour has improved 
significantly (at least for me) and in recent versions of 
libkf5globalaccel-bin the CPU bursts after connecting e.g. a mouse with 
a USB connector are only relatively short (a couple of seconds maybe 
depending on your machine).

Could you try to run a recent KDE stack with testing or unstable and see 
if the issue is still as bad ?

For some people, the issue was apparently caused by ~/.Xmodmap. Can you 
check whether you have such a file ? Thank you.


-- 
Med vänliga hälsningar

Patrick Franz

Bug#1023835: wolfssl: FTBFS because of amd64-only symbols in symbols file

[Felix Lechner]

Hi,

On Thu, Nov 10, 2022 at 4:06 PM Bastian Germann  wrote:
>
> Please keep the three symbols out of the symbols file or make them optional.

Thanks. We are aware of the issue.

Unfortunately, your suggestion will likely cause a build failure on
amd64. How do you make the symbols "optional" please? Thanks!

Kind regards,
Felix Lechner

Bug#1023835: wolfssl: FTBFS because of amd64-only symbols in symbols file

[Bastian Germann]

Source: wolfssl
Version: 5.5.3-1
Severity: serious
Tags: ftbfs

The build fails because of

--- debian/libwolfssl35.symbols (libwolfssl35_5.5.3-2_armhf)
+++ dpkg-gensymbolsjJzBRh   2022-11-10 20:32:48.418173057 +
@@ -48,9 +48,9 @@
  WOLFSSL_ERROR_LINE@Base 5.2.0
  WOLFSSL_ERROR_MSG@Base 5.2.0
  WOLFSSL_EVP_CIPHER_mode@Base 5.2.0
- cpuid_clear_flag@Base 5.5.3
- cpuid_select_flags@Base 5.5.3
- cpuid_set_flag@Base 5.5.3
+#MISSING: 5.5.3-2# cpuid_clear_flag@Base 5.5.3
+#MISSING: 5.5.3-2# cpuid_select_flags@Base 5.5.3
+#MISSING: 5.5.3-2# cpuid_set_flag@Base 5.5.3
  get_digit@Base 5.2.0
  get_digit_count@Base 5.2.0
  get_rand_digit@Base 5.2.0

Please keep the three symbols out of the symbols file or make them optional.

Bug#1020560: diffutils: Missing LGPL-2.1+, GPL-2+ in d/copyright

[Bastian Germann]

Am 10.11.22 um 21:38 schrieb Santiago Vila:

For example, your proposed copyright file has this:

Files: *Makefile.in

I guess this means "anything including the 'Makefile.in' string, which includes a file called Makefile.in at any 
directory depth but also something called this-is-not-really-a-Makefile.in-file".


The documentation about this I'm reading:

https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/

suggests */Makefile.in. Am I right to think that this includes the Makefile.in 
file in the root directory of the package?


Yes, you could have a this-is-not-really-a-Makefile.in that also matches, but 
there is none.
Sure you can match */... to get around that.


Also: What would be the easiest way to put debian/* files in public-domain?

Docs say that when I use "public-domain" string I have to explain exactly "what exemption the corresponding files for 
that paragraph have from default copyright restrictions". What would be an example of this?


If you are the only copyright holder for debian/* you can easily do that. There is not really a standard way to put a 
file in the public domain and there seems to be no such thing in some jurisdictions. A plain English sentence expressing 
that should be enough. A good way to do it in my opinion is to use a public domain statement with some fallback license 
like Unlicense or CC0. CC0 is available in Debian's common-licenses, so you just need to reference that file instead of 
carrying the whole text in your copyright file.


The reason that the standard has this explanation requirement is that many people mistake being freely licensed or "has 
no copyright statement" for "public domain" and will put "public domain" on things that were never released into the 
public domain.

Bug#1023833: FTBFS with OpenJDK 17

[Olek Wojnar]

Source: bazel-bootstrap
Version: 4.2.2+ds-1
Severity: serious
Tags: ftbfs upstream
Forwarded: https://github.com/bazelbuild/bazel/issues/15831

The default use of OpenJDK 17 causes bazel-bootstrap to FTBFS. This is an
upstream issue and upstream's fix[1] should be cherry-picked as soon as
possible.

[1] https://github.com/bazelbuild/bazel/pull/16706

Bug#1018922: kbibtex crashes on startup

[Arnout Boelens]

Hi Adrian,

I rebuilt kbibtex using Qt 5.15.6 in unstable, but this did not resolve the
issue. I was not able to install Qt 5.15.7 from experimental due to
dependency issues.

Thanks,

Arnout

On Thu, Nov 10, 2022 at 7:55 AM Adrian Bunk  wrote:

> On Sat, Sep 03, 2022 at 07:05:46PM -0700, Arnout Boelens wrote:
> > Looks like it might be a QT bug:
> >
> > https://bugs.kde.org/show_bug.cgi?id=433084
>
> Is this fixed in Qt 5.15.6 in unstable or in Qt 5.15.7 in experimental?
>
> Thanks
> Adrian
>

Bug#1023826: marked as done (libnvme: Fails to build on big endian systems (e.g. s390x))

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2022 22:26:57 +
with message-id 
and subject line Bug#1023826: fixed in libnvme 1.2-2
has caused the Debian Bug report #1023826,
regarding libnvme: Fails to build on big endian systems (e.g. s390x)
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.)


-- 
1023826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023826
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnvme
Version: 1.2-1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar ubuntu-patch
X-Debbugs-Cc: bdr...@debian.org

Dear Maintainer,

libnvme fails to build on big endian systems (e.g. s390x). I forwarded
the bug upstream and they fixed. Please apply the fix (see attachement).

Thanks for considering the patch.

-- 
Benjamin Drung
Debian & Ubuntu Developer
diff -Nru libnvme-1.2/debian/patches/mi-endian-fixes.patch 
libnvme-1.2/debian/patches/mi-endian-fixes.patch
--- libnvme-1.2/debian/patches/mi-endian-fixes.patch1970-01-01 
01:00:00.0 +0100
+++ libnvme-1.2/debian/patches/mi-endian-fixes.patch2022-11-10 
16:24:08.0 +0100
@@ -0,0 +1,61 @@
+From ac657355bc86b71e1d2d8dd6079d5d69332dedaa Mon Sep 17 00:00:00 2001
+From: Jeremy Kerr 
+Date: Thu, 10 Nov 2022 12:20:37 +0800
+Subject: [PATCH] mi: endian fixes
+
+We have a couple of endian issues in the mi code: one where we're not
+converting cdw0 for MI commands, and one where we're using the wrong
+byte length for an existing conversion. There is also an error in the
+test suite, where we should be converting the nsze field of a
+nvme_id_ns.
+
+This change fixes those, so that the test suite passes on a BE platform
+(ppc64 in my case).
+
+Fixes: https://github.com/linux-nvme/libnvme/issues/524
+Signed-off-by: Jeremy Kerr 
+Bug-Ubuntu: https://launchpad.net/bugs/1995935
+Origin: https://github.com/linux-nvme/libnvme/pull/529
+---
+ src/nvme/mi.c | 4 ++--
+ test/mi.c | 2 +-
+ 2 files changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/src/nvme/mi.c b/src/nvme/mi.c
+index cd86e41..1a34208 100644
+--- a/src/nvme/mi.c
 b/src/nvme/mi.c
+@@ -139,7 +139,7 @@ int nvme_mi_scan_ep(nvme_mi_ep_t ep, bool force_rescan)
+   struct nvme_mi_ctrl *ctrl;
+   __u16 id;
+ 
+-  id = le32_to_cpu(list.identifier[i]);
++  id = le16_to_cpu(list.identifier[i]);
+   if (!id)
+   continue;
+ 
+@@ -985,7 +985,7 @@ static int nvme_mi_read_data(nvme_mi_ep_t ep, __u32 cdw0,
+   req_hdr.hdr.nmp = (NVME_MI_ROR_REQ << 7) |
+   (NVME_MI_MT_MI << 3); /* we always use command slot 0 */
+   req_hdr.opcode = nvme_mi_mi_opcode_mi_data_read;
+-  req_hdr.cdw0 = cdw0;
++  req_hdr.cdw0 = cpu_to_le32(cdw0);
+ 
+   memset(&req, 0, sizeof(req));
+   req.hdr = &req_hdr.hdr;
+diff --git a/test/mi.c b/test/mi.c
+index 102cea9..4c7f1f2 100644
+--- a/test/mi.c
 b/test/mi.c
+@@ -1287,7 +1287,7 @@ static void test_admin_ns_mgmt_create(struct nvme_mi_ep 
*ep)
+   assert(!rc);
+   assert(ns == 0x01020304);
+ 
+-  nsid.nsze = 42;
++  nsid.nsze = cpu_to_le64(42);
+   rc = nvme_mi_admin_ns_mgmt_create(ctrl, &nsid, 0, &ns);
+   assert(rc);
+ }
+-- 
+2.37.2
+
diff -Nru libnvme-1.2/debian/patches/series libnvme-1.2/debian/patches/series
--- libnvme-1.2/debian/patches/series   1970-01-01 01:00:00.0 +0100
+++ libnvme-1.2/debian/patches/series   2022-11-10 16:20:16.0 +0100
@@ -0,0 +1 @@
+mi-endian-fixes.patch
--- End Message ---
--- Begin Message ---
Source: libnvme
Source-Version: 1.2-2
Done: Daniel Baumann 

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

Debian distribution maintenance software
pp.
Daniel Baumann  (supplier of updated libnvme 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 10 Nov 2022 23:06:24 +0100
Source: libnvme
Architecture: source
Version: 1.2-2
Distribution: sid
Urgency: 

Bug#998180: marked as done (basix: no longer builds any binaries)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2022 23:57:32 +0200
with message-id 
and subject line Re: Bug#998180: basix: no longer builds any binaries
has caused the Debian Bug report #998180,
regarding basix: no longer builds any binaries
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.)


-- 
998180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: basix
Version: 0.0.1~git20210122.4f10ef2-2
Severity: serious

The binaries have been taken over by fenics-basix and basix should be
removed.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
On Sun, Oct 31, 2021 at 03:56:57PM +0100, Sebastian Ramacher wrote:
> Source: basix
> Version: 0.0.1~git20210122.4f10ef2-2
> Severity: serious
> 
> The binaries have been taken over by fenics-basix and basix should be
> removed.

This has happened in the meantime.

> Cheers

cu
Adrian--- End Message ---

Processed: tagging 1004441

[Debian Bug Tracking System]

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

> tags 1004441 + bookworm sid
Bug #1004441 [release.debian.org] Chromium: decide before the freeze if it can 
be part of bookworm
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

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

Bug#1023830: widelands: FTBFS on s390x

[Sebastian Ramacher]

Source: widelands
Version: 2:1.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=widelands&arch=s390x&ver=2%3A1.1-1&stamp=1668005308&raw=0

Running testcase ./src/base/test/test_string.cc:174
[00:00:00.000 real] ERROR: format error: A string contains invalid printf 
placeholders
[00:00:00.000 real] ERROR: Error: [./src/base/format/tree.cc:244] unrecognized 
format type character 'q'
[00:00:00.000 real] ERROR: String: %q
Running testcase ./src/base/test/test_string.cc:175
[00:00:00.000 real] ERROR: format error: A string contains invalid printf 
placeholders
[00:00:00.000 real] ERROR: Error: [./src/base/format/tree.cc:222] invalid 
format type character 'f' after '%l'
[00:00:00.000 real] ERROR: String: %lf
Running testcase ./src/base/test/test_string.cc:176
[00:00:00.000 real] ERROR: format error: A string contains invalid printf 
placeholders
[00:00:00.000 real] ERROR: Error: [./src/base/format/tree.cc:244] unrecognized 
format type character '|'
[00:00:00.000 real] ERROR: String: %|1$d|
Running testcase ./src/base/test/test_string.cc:177
[00:00:00.000 real] ERROR: format error: A string contains invalid printf 
placeholders
[00:00:00.000 real] ERROR: Error: [./src/base/format/tree.cc:244] unrecognized 
format type character '
[00:00:00.000 real] ERROR: String: %02.7
Running testcase ./src/base/test/test_string.cc:178
[00:00:00.000 real] ERROR: format error: A string contains invalid printf 
placeholders
[00:00:00.000 real] ERROR: Error: [./src/base/format/tree.cc:314] index 1 is 
unused
[00:00:00.000 real] ERROR: String: %2% %3$i
Running testcase ./src/base/test/test_string.cc:179
[00:00:00.000 real] ERROR: format error: A string contains invalid printf 
placeholders
[00:00:00.000 real] ERROR: Error: [./src/base/format/tree.cc:94] duplicate use 
of index 1
[00:00:00.000 real] ERROR: String: %1% %1$d
Running testcase ./src/base/test/test_string.cc:180
[00:00:00.000 real] ERROR: format error: A string contains invalid printf 
placeholders
[00:00:00.000 real] ERROR: Error: [./src/base/format/tree.cc:102] Cannot mix 
positional and unpositional placeholders
[00:00:00.000 real] ERROR: String: %4d %2%
Running testcase ./src/base/test/test_string.cc:181
[00:00:00.000 real] ERROR: format error: A string contains invalid printf 
placeholders
[00:00:00.000 real] ERROR: Error: [./src/base/format/tree.h:134] Too many 
arguments provided (expected only 3)
[00:00:00.000 real] ERROR: String: %u %li %lld
Running testcase ./src/base/test/test_string.cc:182
[00:00:00.000 real] ERROR: format error: A string contains invalid printf 
placeholders
[00:00:00.000 real] ERROR: Error: [./src/base/format/tree.h:269] Too few 
arguments provided: 3 required but only 2 passed
[00:00:00.000 real] ERROR: String: %lu %llu %lli
Running testcase ./src/base/test/test_string.cc:183
[00:00:00.000 real] ERROR: format error: A string contains invalid printf 
placeholders
[00:00:00.000 real] ERROR: Error: [./src/base/format/string_node.h:40] Wrong 
argument type: expected string, found int
[00:00:00.000 real] ERROR: String: %s
Running testcase ./src/base/test/test_string.cc:184
[00:00:00.000 real] ERROR: format error: A string contains invalid printf 
placeholders
[00:00:00.000 real] ERROR: Error: [./src/base/format/number_node.h:64] Wrong 
argument type: expected int, found string
[00:00:00.000 real] ERROR: String: %i
Running testcase ./src/base/test/test_string.cc:185
[00:00:00.000 real] ERROR: format error: A string contains invalid printf 
placeholders
[00:00:00.000 real] ERROR: Error: [./src/base/format/float_node.h:82] Floating 
point value too large: 12345679395506094080.00
[00:00:00.000 real] ERROR: String: %f
Running testcase ./src/base/test/test_string.cc:186
[00:00:00.000 real] ERROR: format error: A string contains invalid printf 
placeholders
[00:00:00.000 real] ERROR: Error: [./src/base/format/number_node.h:51] Unsigned 
integral value too large: 9756277977048271785
[00:00:00.000 real] ERROR: String: %ld
Running testcase ./src/base/test/test_string.cc:187
[00:00:00.000 real] ERROR: format error: A string contains invalid printf 
placeholders
[00:00:00.000 real] ERROR: Error: [./src/base/format/number_node.h:35] '-' and 
'0' can not be combined
[00:00:00.000 real] ERROR: String: %-05d
Running testcase ./src/base/test/test_string.cc:188
[00:00:00.000 real] ERROR: format error: A string contains invalid printf 
placeholders
[00:00:00.000 real] ERROR: Error: [./src/base/format/tree.cc:75] Repeated flag 
'+'
[00:00:00.000 real] ERROR: String: %+0+5d
Running strings::trim_split_replace
Running testcase ./src/base/test/test_string.cc:86
Running testcase ./src/base/test/test_string.cc:88
Running testcase ./src/base/test/test_string.cc:90
Running testcase ./src/base/test/test_string.cc:92
Running testcase ./src/base/test/test_string.cc:96
Running testcase ./src/base/test/test_string.cc:97
Runn

Bug#1023697: Keep out of testing

[Bastian Germann]

As a new maintainer has stepped up, this cannot be the reason anymore to dump 
the package.
Actually, with the next version of swupdate (one of those handful) I wanted to 
switch from OpenSSL
to SWUpdate.

It would also be interesting for Debian's downstreams who take a different 
approach to combining
OpenSSL with GPL-2-only packages (licenses are incompatible, which Debian heals 
with the application
of the GPL-built-in system library exception). Ubuntu and probably others do 
not take the same stand
and wolfSSL is really the only TLS library that has a usable OpenSSL 
compatibility layer.

If it helps, I can support the new maintainer.

Bug#1023031: marked as done (rust-async-std: autopkgtest failure.)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2022 21:40:18 +0100
with message-id <166811281816.1867533.15176773445554230...@auryn.jones.dk>
and subject line Re: Bug#1023031: marked as done (rust-async-std: autopkgtest 
failure.)
has caused the Debian Bug report #1023031,
regarding rust-async-std: autopkgtest failure.
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.)


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

Package: rust-async-std
Version: 1.12.0-5
Severity: serious

The autopkgtest for rust-async-std is failing and preventing it's migration to 
testing.


error[E0425]: cannot find function `block_on` in module `task`
   --> src/io/read/take.rs:231:15
|
231 | task::block_on(async move {
|    not found in `task`
|
help: consider importing one of these items
|
223 | use async_io::block_on;
|
223 | use futures::executor::block_on;
|

error[E0425]: cannot find function `block_on` in module `crate::task`
   --> src/io/read/mod.rs:394:22
|
394 | crate::task::block_on(async {
|   not found in `crate::task`
|
help: consider importing one of these items
|
389 | use async_io::block_on;
|
389 | use futures::executor::block_on;
|

For more information about this error, try `rustc --explain E0425`.
error: could not compile `async-std` due to 2 previous errors
--- End Message ---
--- Begin Message ---
Version: 1.12.0-10

Quoting Jonas Smedegaard (2022-11-01 07:50:59)
> Control: reopen -1
> 
> Quoting Debian Bug Tracking System (2022-10-31 16:42:05)
> > Your message dated Mon, 31 Oct 2022 15:39:12 +
> > with message-id 
> > and subject line Bug#1023031: fixed in rust-async-std 1.12.0-6
> > has caused the Debian Bug report #1023031,
> > regarding rust-async-std: autopkgtest failure.
> > to be marked as done.
> > 
> > This means that you claim that the problem has been dealt with.
> 
> Whoops - wasn't fixed after all :-/

This really should be fixed since 1.12.0-5.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

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

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

Bug#1020560: diffutils: Missing LGPL-2.1+, GPL-2+ in d/copyright

[Santiago Vila]

El 23/9/22 a las 11:34, Bastian Germann escribió:

Source: diffutils
Severity: important
Version: 1:3.8-1

Hi,

diffutils has an incomplete copyright file. At least LGPL-2.1+ and 
GPL-2+ licenses are missing even though they are applicable to some 
files. While they can be distributed as GPL-3+, it is not the correct 
license for those files to record in d/copyright.


I have attached a d/copyright file in the machine-readable format for v3.8.


Thanks for the report and the revised file.

I have a lot of copyright files to convert in other packages, so there 
are a few things I still don't understand in full. Hope you don't mind 
if I ask you about them.


For example, your proposed copyright file has this:

Files: *Makefile.in

I guess this means "anything including the 'Makefile.in' string, which 
includes a file called Makefile.in at any directory depth but also 
something called this-is-not-really-a-Makefile.in-file".


The documentation about this I'm reading:

https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/

suggests */Makefile.in. Am I right to think that this includes the 
Makefile.in file in the root directory of the package?


Also: What would be the easiest way to put debian/* files in public-domain?

Docs say that when I use "public-domain" string I have to explain 
exactly "what exemption the corresponding files for that paragraph have 
from default copyright restrictions". What would be an example of this?


Thanks.

Processed: rust-zoxide is a source package

[Debian Bug Tracking System]

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

> reassign 1021754 src:rust-zoxide 0.4.3-4
Bug #1021754 [rust-zoxide] rust-zoxide: build-dependencies unsatisfiable.
Bug reassigned from package 'rust-zoxide' to 'src:rust-zoxide'.
No longer marked as found in versions 0.4.3-4.
Ignoring request to alter fixed versions of bug #1021754 to the same values 
previously set
Bug #1021754 [src:rust-zoxide] rust-zoxide: build-dependencies unsatisfiable.
Marked as found in versions rust-zoxide/0.4.3-4.
> thanks
Stopping processing here.

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

Bug#998950: mailsync: diff for NMU version 5.2.7-3.1

[Tomas Pospisek]

On Thu, 3 Nov 2022, Marcos Talau wrote:


Control: tags 998950 + patch
Control: tags 998950 + pending


Dear maintainer,

I've prepared an NMU for mailsync (versioned as 5.2.7-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.


Many, many thanks Marcos!
*t

Bug#1013613: marked as done (ontospy: FTBFS: make[1]: *** [debian/rules:28: execute_after_dh_auto_install] Error 1)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2022 20:12:48 +0100
with message-id <166810756849.1867533.8708839472229040...@auryn.jones.dk>
and subject line Re: Bug#1013613: ontospy: FTBFS: make[1]: *** 
[debian/rules:28: execute_after_dh_auto_install] Error 1
has caused the Debian Bug report #1013613,
regarding ontospy: FTBFS: make[1]: *** [debian/rules:28: 
execute_after_dh_auto_install] Error 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.)


-- 
1013613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ontospy
Version: 1.9.9.4~dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 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 '/<>'
> PATH="/<>/debian/tmp/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
>  PYTHONPATH="/<>/debian/tmp/usr/lib/python3.10/dist-packages" 
> prove debian/tests/*.t
> 
> #   Failed test 'Check return from 'ontospy gendocs --type 3 
> file:///<>/ontospy/tests/rdf/foaf.rdf' is 0'
> #   at debian/tests/ontospy-gendocs.t line 33.
> #  got: '1'
> # expected: '0'
> # Looks like you failed 1 test of 22.
> debian/tests/ontospy-gendocs.t .. 
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/22 subtests 
> debian/tests/ontospy-lib.t .. ok
> debian/tests/ontospy-scan.t . ok
> debian/tests/ontospy-ser.t .. ok
> debian/tests/ontospy-shell.t  ok
> debian/tests/ontospy-utils.t  ok
> debian/tests/ontospy.t .. ok
> 
> Test Summary Report
> ---
> debian/tests/ontospy-gendocs.t (Wstat: 256 Tests: 22 Failed: 1)
>   Failed test:  20
>   Non-zero exit status: 1
> Files=7, Tests=88,  6 wallclock secs ( 0.04 usr  0.00 sys +  5.72 cusr  0.51 
> csys =  6.27 CPU)
> Result: FAIL
> make[1]: *** [debian/rules:28: execute_after_dh_auto_install] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/ontospy_1.9.9.4~dfsg-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220624&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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 ---
Version: 2.0.0~dfsg-2

Quoting Lucas Nussbaum (2022-06-24 13:27:45)
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

Build succesfully again since packaging release 2.0.0~dfsg-2.

Thanks for reporting!

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

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

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

Bug#1021021: marked as done (wolfssl: CVE-2022-38152 CVE-2022-38153 CVE-2022-39173)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2022 19:00:14 +
with message-id 
and subject line Bug#1021021: fixed in wolfssl 5.5.3-1
has caused the Debian Bug report #1021021,
regarding wolfssl: CVE-2022-38152 CVE-2022-38153 CVE-2022-39173
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.)


-- 
1021021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wolfssl
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for wolfssl.

CVE-2022-38152[0]:
| An issue was discovered in wolfSSL before 5.5.0. When a TLS 1.3 client
| connects to a wolfSSL server and SSL_clear is called on its session,
| the server crashes with a segmentation fault. This occurs in the
| second session, which is created through TLS session resumption and
| reuses the initial struct WOLFSSL. If the server reuses the previous
| session structure (struct WOLFSSL) by calling wolfSSL_clear(WOLFSSL*
| ssl) on it, the next received Client Hello (that resumes the previous
| session) crashes the server. Note that this bug is only triggered when
| resuming sessions using TLS session resumption. Only servers that use
| wolfSSL_clear instead of the recommended SSL_free; SSL_new sequence
| are affected. Furthermore, wolfSSL_clear is part of wolfSSL's
| compatibility layer and is not enabled by default. It is not part of
| wolfSSL's native API.

https://github.com/wolfSSL/wolfssl/pull/5468

CVE-2022-38153[1]:
| An issue was discovered in wolfSSL before 5.5.0 (when --enable-
| session-ticket is used); however, only version 5.3.0 is exploitable.
| Man-in-the-middle attackers or a malicious server can crash TLS 1.2
| clients during a handshake. If an attacker injects a large ticket
| (more than 256 bytes) into a NewSessionTicket message in a TLS 1.2
| handshake, and the client has a non-empty session cache, the session
| cache frees a pointer that points to unallocated memory, causing the
| client to crash with a "free(): invalid pointer" message. NOTE: It is
| likely that this is also exploitable during TLS 1.3 handshakes between
| a client and a malicious server. With TLS 1.3, it is not possible to
| exploit this as a man-in-the-middle.

https://github.com/wolfSSL/wolfssl/pull/5476

CVE-2022-39173[2]:
| In wolfSSL before 5.5.1, malicious clients can cause a buffer overflow
| during a TLS 1.3 handshake. This occurs when an attacker supposedly
| resumes a previous TLS session. During the resumption Client Hello a
| Hello Retry Request must be triggered. Both Client Hellos are required
| to contain a list of duplicate cipher suites to trigger the buffer
| overflow. In total, two Client Hellos have to be sent: one in the
| resumed session, and a second one as a response to a Hello Retry
| Request message.

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-38152
https://www.cve.org/CVERecord?id=CVE-2022-38152
[1] https://security-tracker.debian.org/tracker/CVE-2022-38153
https://www.cve.org/CVERecord?id=CVE-2022-38153
[2] https://security-tracker.debian.org/tracker/CVE-2022-39173
https://www.cve.org/CVERecord?id=CVE-2022-39173

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: wolfssl
Source-Version: 5.5.3-1
Done: Jacob Barthelmeh 

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

Debian distribution maintenance software
pp.
Jacob Barthelmeh  (supplier of updated wolfssl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 9 Nov 2022 16:10:39 -0800
Source: wolfssl
Binary: libwolfssl-dev libwolfssl35 libwolfssl35-dbgsym
Architecture: source amd64
Version: 5.5.3-1
Distribution: unstable
Urgency: medium
Maintainer: Jacob Barthelmeh 
Changed-By: Jacob Barthelmeh 
Description:
 libwolfssl-dev - Development fil

Bug#1023574: marked as done (wolfssl: CVE-2022-42961)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2022 19:00:14 +
with message-id 
and subject line Bug#1023574: fixed in wolfssl 5.5.3-1
has caused the Debian Bug report #1023574,
regarding wolfssl: CVE-2022-42961
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.)


-- 
1023574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wolfssl
Version: 5.2.0-2
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for wolfssl.

CVE-2022-42961[0]:
| An issue was discovered in wolfSSL before 5.5.0. A fault injection
| attack on RAM via Rowhammer leads to ECDSA key disclosure. Users
| performing signing operations with private ECC keys, such as in
| server-side TLS connections, might leak faulty ECC signatures. These
| signatures can be processed via an advanced technique for ECDSA key
| recovery. (In 5.5.0 and later, WOLFSSL_CHECK_SIG_FAULTS can be used to
| address the vulnerability.)


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-42961
https://www.cve.org/CVERecord?id=CVE-2022-42961

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: wolfssl
Source-Version: 5.5.3-1
Done: Jacob Barthelmeh 

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

Debian distribution maintenance software
pp.
Jacob Barthelmeh  (supplier of updated wolfssl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 9 Nov 2022 16:10:39 -0800
Source: wolfssl
Binary: libwolfssl-dev libwolfssl35 libwolfssl35-dbgsym
Architecture: source amd64
Version: 5.5.3-1
Distribution: unstable
Urgency: medium
Maintainer: Jacob Barthelmeh 
Changed-By: Jacob Barthelmeh 
Description:
 libwolfssl-dev - Development files for the wolfSSL encryption library
 libwolfssl35 - wolfSSL encryption library
Closes: 1014867 1016981 1021021 1023574
Changes:
 wolfssl (5.5.3-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #1014867, #1016981, #1021021, #1023574)
   * Fixes CVE-2022-34293, CVE-2022-38152, CVE-2022-38153, CVE-2022-39173,
 CVE-2022-42961
   * Bump SONAME version to 35.
   * Update symbols file.
   * Drop patch turn-off-fastmath-for-amd64.patch; now using sp-math
 everywhere.
   * Ship docs/QUIC.md with the development files.
   * Bump Standards-Version to 4.6.1.
   * Drop Vcs-Git and Vcs-Browser; upstream releases often do not share a
 common history, especially for security releases fixing vulnerabilities.
   * Fix watch file to look at tags instead of releases.
   * Add Jacob Barthelmeh as Maintainer and move self into Uploaders.
Checksums-Sha1:
 ae77e0818ae1538f1d9aa510f73f25e152ef4adc 2343 wolfssl_5.5.3-1.dsc
 9f50833f798f8f3b5451ad8d56acb8d597d7a2d6 19153825 wolfssl_5.5.3.orig.tar.gz
 b5b468c1bb45d9a27f66b776e4f6a3e153df09a3 488 wolfssl_5.5.3.orig.tar.gz.asc
 e5214188ab5f828fd0074e3e988003c2dda93e4a 31436 wolfssl_5.5.3-1.debian.tar.xz
 4ebb5b29091423ad7a2914d9ba2e7e9b7ad132e0 1307764 
libwolfssl-dev_5.5.3-1_amd64.deb
 bf91702b272bac131645ecbb6323b13a056775c8 2460352 
libwolfssl35-dbgsym_5.5.3-1_amd64.deb
 fdd27d82ef11bea5917439464fba34d8b26717f5 884496 libwolfssl35_5.5.3-1_amd64.deb
 1326a8cec117e498cbea79686247898296258f5e 6715 wolfssl_5.5.3-1_amd64.buildinfo
Checksums-Sha256:
 272f96cc8a188c84d313ad4354728aa5eb47fad5b8b9e7b4b2359a10e7481c2d 2343 
wolfssl_5.5.3-1.dsc
 fd3135b8657d09fb96a8aad16585da850b96ea420ae8ce5ac4d5fdfc614c2683 19153825 
wolfssl_5.5.3.orig.tar.gz
 9037df9ea6e19de743ec30c73d9e90440a63733fb2d50ef20f3253f46c60576d 488 
wolfssl_5.5.3.orig.tar.gz.asc
 e6ead09a6aac5d947c796291f191398f81a9385eee509a0f87384f666d3d304e 31436 
wolfssl_5.5.3-1.debian.tar.xz
 227249371b5d14fae34b2cf0015ef0c185faf7d934ebb9efb12456814712da89 1307764 
libwolfssl-dev_5.5.3-1_amd64.deb
 da6

Bug#1000560: marked as done (Compatibility with Symfony 5)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2022 19:00:13 +
with message-id 
and subject line Bug#1000560: fixed in php-laravel-framework 8.83.26+dfsg-1
has caused the Debian Bug report #1000560,
regarding Compatibility with Symfony 5
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.)


-- 
1000560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-cboden-ratchet
Version: 0.4.2-1
Severity: serious
X-Debbugs-Cc: Debian PHP PEAR Maintainers 
User: pkg-php-p...@lists.alioth.debian.org
Usertags: Symfony5
Control: clone -1 -2 -3
Control: reassign -2 php-robmorgan-phinx 0.9.2-3
Control: reassign -3 php-laravel-framework 6.20.14+dfsg-2

Hi,

Since symfony 5 has finally been uploaded to unstable, packages now
can’t depend on php-symfony-* (<< 5) anymore. Upgrading to a new
upstream version should do the trick (Symfony 5 has been released two
years ago).

Symfony 5 (5.4, the upcoming LTS) will a priori be the version in
Bookworm, the next LTS (6.4) is expected in two years from now, so
probably well after the freeze starts (and hopefully the Bookworm
release).

Thanks in advance for fixing this issue, do not hesitate to ask for help
on pkg-php-p...@lists.alioth.debian.org if needed.

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: php-laravel-framework
Source-Version: 8.83.26+dfsg-1
Done: Robin Gustafsson 

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

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

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

Debian distribution maintenance software
pp.
Robin Gustafsson  (supplier of updated php-laravel-framework 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 09 Nov 2022 21:51:45 +0100
Source: php-laravel-framework
Binary: php-illuminate-auth php-illuminate-broadcasting php-illuminate-bus 
php-illuminate-cache php-illuminate-collections php-illuminate-config 
php-illuminate-console php-illuminate-container php-illuminate-contracts 
php-illuminate-cookie php-illuminate-database php-illuminate-encryption 
php-illuminate-events php-illuminate-filesystem php-illuminate-hashing 
php-illuminate-http php-illuminate-log php-illuminate-macroable 
php-illuminate-mail php-illuminate-notifications php-illuminate-pagination 
php-illuminate-pipeline php-illuminate-queue php-illuminate-redis 
php-illuminate-routing php-illuminate-session php-illuminate-support 
php-illuminate-testing php-illuminate-translation php-illuminate-validation 
php-illuminate-view php-laravel-framework
Architecture: source all
Version: 8.83.26+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: Robin Gustafsson 
Description:
 php-illuminate-auth - Illuminate Auth library component for PHP
 php-illuminate-broadcasting - Illuminate Broadcasting library component for PHP
 php-illuminate-bus - Illuminate Bus library component for PHP
 php-illuminate-cache - Illuminate Cache library component for PHP
 php-illuminate-collections - illuminate Collections library component for PHP
 php-illuminate-config - Illuminate Config library component for PHP
 php-illuminate-console - Illuminate Console library component for PHP
 php-illuminate-container - Illuminate Container library component for PHP
 php-illuminate-contracts - Illuminate Contracts library component for PHP
 php-illuminate-cookie - Illuminate Cookie library component for PHP
 php-illuminate-database - Illuminate Database library component for PHP
 php-illuminate-encryption - Illuminate Encryption library component for PHP
 php-illuminate-events - Illuminate Events library component for PHP
 php-illuminate-filesystem - Illuminate Filesystem library component for PHP
 php-illuminate-hashing - Illuminate Hashing library component for PHP
 php-illuminate-http - Illuminate HTTP library component for PHP
 php-illuminate-log - Illuminate Log library component for PHP
 php-illuminate-macroable - Illuminate Macroable component for PHP
 php-illuminate-mail - Illuminate Mail library componen

Processed: bug 1023803 is forwarded to https://github.com/cgwalters/git-evtag/pull/39, tagging 1023803

[Debian Bug Tracking System]

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

> forwarded 1023803 https://github.com/cgwalters/git-evtag/pull/39
Bug #1023803 [src:git-evtag] git-evtag: autopkgtest needs update for new 
version of git: transport 'file' not allowed
Set Bug forwarded-to-address to 
'https://github.com/cgwalters/git-evtag/pull/39'.
> tags 1023803 + pending
Bug #1023803 [src:git-evtag] git-evtag: autopkgtest needs update for new 
version of git: transport 'file' not allowed
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1023811: golang-github-grpc-ecosystem-go-grpc-middleware_1.3.0-1 sources changed in the archive?

[Cyril Brulebois]

Adrian Bunk  (2022-11-10):
> Package: ftp.debian.org
> Severity: grave
> X-Debbugs-Cc: debian-wb-t...@lists.debian.org, Thomas Goirand 
> 

Yeah, the dsc seems to have changed, deb.debian.org returns the old version
(due to corporate-grade caching or whatever), while my local mirror (standard
apache2 serving files synced by ftpsync via syncproxy2.eu.debian.org and
debian.ethz.ch) shows the new version (which matches the Sources file and
downloads fine accordingly).

> Get:1 https://deb.debian.org/debian experimental/main 
> golang-github-grpc-ecosystem-go-grpc-middleware 1.3.0-1 (dsc) [2857 B]
> Err:1 https://deb.debian.org/debian experimental/main 
> golang-github-grpc-ecosystem-go-grpc-middleware 1.3.0-1 (dsc)
>   Hash Sum mismatch
>   Hashes of expected file:
>- SHA256:8e86e0a9cc31461c0f564e8feefb2e1e9ec05c265ab06e96fd32b7de787bc504
>- Filesize:2857 [weak]
>- MD5Sum:c4d33ab09e4f4a95c819dd1de88d0876 [weak]
>   Hashes of received file:
>- SHA256:8bbee530bbdb11a58a275c34878c372558223c294384897822eba1338b84db82
>- MD5Sum:8d6eee1b2b773c9be12536396ba949a6 [weak]
>- Filesize:2857 [weak]
>   Last modification reported: Wed, 26 Oct 2022 14:32:16 +

An extra check can be done by querying snapshot.debian.org, and `debsnap
golang-github-grpc-ecosystem-go-grpc-middleware 1.3.0-1` downloads
the old version as well.

An extra hint is obtained by clicking the 1.3.0-1 link on

and getting an error page, I suppose because of a different lookup
implementation.

Adding `-v` to the debsnap line above, I'm getting this URL:
  
https://snapshot.debian.org/mr/package/golang-github-grpc-ecosystem-go-grpc-middleware/1.3.0-1/srcfiles?fileinfo=1

which indeed has two `fileinfo` entries for the .dsc:

"0feb631739624059c1db234338e87a57d33f4d5f": [
  {
"archive_name": "debian",
"first_seen": "20221027T213940Z",
"name": "golang-github-grpc-ecosystem-go-grpc-middleware_1.3.0-1.dsc",
"path": "/pool/main/g/golang-github-grpc-ecosystem-go-grpc-middleware",
"size": 2857
  }
],
"48d5553979d3de93b05587668ce30305d3ad9141": [
  {
"archive_name": "debian",
"first_seen": "20221103T151306Z",
"name": "golang-github-grpc-ecosystem-go-grpc-middleware_1.3.0-1.dsc",
"path": "/pool/main/g/golang-github-grpc-ecosystem-go-grpc-middleware",
"size": 2857
  }
],

Maybe that'll help pinpoint what happened and/or when.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1023811: golang-github-grpc-ecosystem-go-grpc-middleware_1.3.0-1 sources changed in the archive?

[Adam D. Barratt]

On Thu, 2022-11-10 at 15:53 +0200, Adrian Bunk wrote:
> 
Get:1 https://deb.debian.org/debian experimental/main golang-github-
> grpc-ecosystem-go-grpc-middleware 1.3.0-1 (dsc) [2857 B]
> Err:1 https://deb.debian.org/debian experimental/main golang-github-
> grpc-ecosystem-go-grpc-middleware 1.3.0-1 (dsc)
>   Hash Sum mismatch
>   Hashes of expected file:
>-
> SHA256:8e86e0a9cc31461c0f564e8feefb2e1e9ec05c265ab06e96fd32b7de787bc5
> 04
>- Filesize:2857 [weak]
>- MD5Sum:c4d33ab09e4f4a95c819dd1de88d0876 [weak]
>   Hashes of received file:
>-
> SHA256:8bbee530bbdb11a58a275c34878c372558223c294384897822eba1338b84db
> 82
>- MD5Sum:8d6eee1b2b773c9be12536396ba949a6 [weak]
>- Filesize:2857 [weak]
>   Last modification reported: Wed, 26 Oct 2022 14:32:16 +
> Get:2 https://deb.debian.org/debian experimental/main golang-github-
> grpc-ecosystem-go-grpc-middleware 1.3.0-1 (tar) [104 kB]
> Get:3 https://deb.debian.org/debian experimental/main golang-github-
> grpc-ecosystem-go-grpc-middleware 1.3.0-1 (diff) [2652 B]
> E: Failed to fetch 
> https://deb.debian.org/debian/pool/main/g/golang-github-grpc-ecosystem-go-grpc-middleware/golang-github-grpc-ecosystem-go-grpc-middleware_1.3.0-1.dsc
>   Hash Sum mismatch
>Hashes of expected file:
> -
> SHA256:8e86e0a9cc31461c0f564e8feefb2e1e9ec05c265ab06e96fd32b7de787bc5
> 04
> - Filesize:2857 [weak]
>Fetched 109 kB in 0s (416 kB/s)
>  - MD5Sum:c4d33ab09e4f4a95c819dd1de88d0876 [weak]
>Hashes of received file:
> -
> SHA256:8bbee530bbdb11a58a275c34878c372558223c294384897822eba1338b84db
> 82
> - MD5Sum:8d6eee1b2b773c9be12536396ba949a6 [weak]
> - Filesize:2857 [weak]
>Last modification reported: Wed, 26 Oct 2022 14:32:16 +
> E: Failed to fetch some archives.
> E: apt-get for sources failed
> ...
> 
> 
> I can reproduce the problem locally with
> $ apt-get source golang-github-grpc-ecosystem-go-grpc-
> middleware/experimental
> 
> This is not supposed to happen, and I haven't seen this before.

So far as I can tell, the timeline is:

- 2022-10-26 package is uploaded
- 2022-10-31 package is removed as obsolete
- 2022-11-03 the same package is re-uploaded, with a different GPG
signature

The file in the archive matches the "expected" hashes, whereas deb.d.o
is returning the original file.

Regards,

Adam

Processed: forcibly merging 1021675 1022508

[Debian Bug Tracking System]

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

> forcemerge 1021675 1022508
Bug #1021675 [src:ariba] ariba: autopkgtest regression and ftbfs with samtools 
1.16
Bug #1021675 [src:ariba] ariba: autopkgtest regression and ftbfs with samtools 
1.16
Added tag(s) patch, bookworm, and sid.
Bug #1022508 [src:ariba] ariba: ftbfs with samtools 1.16
Set Bug forwarded-to-address to 
'https://github.com/sanger-pathogens/ariba/issues/327'.
Added indication that 1022508 affects src:python-pysam
Added tag(s) help and upstream.
Merged 1021675 1022508
> thanks
Stopping processing here.

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

Bug#979101: marked as done (Legally problematic GPL-3+ readline dependency)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2022 17:49:02 +
with message-id 
and subject line Bug#979101: fixed in devtodo 0.1.20+git20200830.0ad52b0-2
has caused the Debian Bug report #979101,
regarding Legally problematic GPL-3+ readline dependency
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.)


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

Package: devtodo
Severity: important

This package depends on libreadline8 which is GPL-3+ licensed. According 
to debian/copyright parts of your package are GPL-2-only licensed. If 
that is also (transitively) the case for the binaries that link with 
libreadline.so.8 it might be legally problematic (see 
https://www.gnu.org/licenses/gpl-faq.html#AllCompatibility).


There is an easy solution to the problem: Replacing the build dependency 
libreadline-dev with libreadline-gplv2-dev links with the GPL-2+ 
licensed older version. However, that is orphaned in Debian, so 
libeditreadline-dev should be preferred, which does not compile with 
your package without any patch. It links with the BSD-licensed libedit 
library which is a readline replacement.
--- End Message ---
--- Begin Message ---
Source: devtodo
Source-Version: 0.1.20+git20200830.0ad52b0-2
Done: Carlos Henrique Lima Melara 

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

Debian distribution maintenance software
pp.
Carlos Henrique Lima Melara  (supplier of updated 
devtodo package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 10 Nov 2022 11:27:55 -0300
Source: devtodo
Architecture: source
Version: 0.1.20+git20200830.0ad52b0-2
Distribution: unstable
Urgency: medium
Maintainer: Carlos Henrique Lima Melara 
Changed-By: Carlos Henrique Lima Melara 
Closes: 979101
Changes:
 devtodo (0.1.20+git20200830.0ad52b0-2) unstable; urgency=medium
 .
   * debian/control:
   - Bumped Standards-Version to 4.6.1 - no changes needed.
   - Changed Build-Depends from libreadline-dev to libeditreadline-dev.
 (Closes: #979101)
   * debian/copyright: updated packaging copyright years.
   * debian/gbp.conf: added gbp.conf file.
   * debian/patches/:
   - 020_use-libedit-readline-compat-layer.patch: added.
   - 030_fix-compiler-error.patch: added.
Checksums-Sha1:
 749346af03058fc2aa0efa570571b101ea34fcff 1917 
devtodo_0.1.20+git20200830.0ad52b0-2.dsc
 6b1e2b9fef72acb7e1fc7bc1dea682baa771b33b 12852 
devtodo_0.1.20+git20200830.0ad52b0-2.debian.tar.xz
 3e53dc05659bda6255b644e62d8046d41217daac 6022 
devtodo_0.1.20+git20200830.0ad52b0-2_source.buildinfo
Checksums-Sha256:
 09c828a1bcc33f5e15787f95f528ed05b098fc09d3b559bfeeef468fd31eeefa 1917 
devtodo_0.1.20+git20200830.0ad52b0-2.dsc
 aab2d658032fbfa5bacd14ee3bd432abb37707ec7027b8d9968cba61e3d187a2 12852 
devtodo_0.1.20+git20200830.0ad52b0-2.debian.tar.xz
 804ab0b6a0e947f013da4b5e6e8357f45004b8335256d7bd262abd16cb7419d6 6022 
devtodo_0.1.20+git20200830.0ad52b0-2_source.buildinfo
Files:
 921e08f31a148a78c4febc3c32650e31 1917 utils optional 
devtodo_0.1.20+git20200830.0ad52b0-2.dsc
 bf23710db5c3fb9c0d85b55190e5bd9f 12852 utils optional 
devtodo_0.1.20+git20200830.0ad52b0-2.debian.tar.xz
 35537c7510d3d2adb0003f30a324877c 6022 utils optional 
devtodo_0.1.20+git20200830.0ad52b0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmNtNMsQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFK8gDADHStVI4HhMIo2mJ+F+CJmDF41Fis6MCS3C
gU+sr7f7KnlKOnuERnp6AdynH3GP8HbHRjE3Vn1F2GxrvPvQ9ZCVEKJgHe/NZNMi
vLSpm3xO2vdtWSOnYUC7Pb4GEL77wicDhlgTIgzl1Lz+AVyU2QV3Zo/JKRbvZ7vk
sqy0hAmwoS9oSAA/GkUuQB+8/8vpGKOtoLKZVKWZDYY6C2f1LpMT3eAWySWqSWU2
F7e/6FXW+TRFdYzOMoq3BUXeQ/Cx3RNvaYnRt5iu2NE/mcpDvPfbYC1BzAuvhGD9
fon1dQApTZ53TZRP3voly1ipL05OQH3vE8CU4QEiKZ5nH6PRAh24Txnita+/H6Ox
We2fVMSGpw/B8+d/lSqNU48WhCI+tMG6iEHuWlfkZ2lxUXJbGYP9tn4LmrInEiCl
PY948ElwKfi0kjLtQChI93DUeYx80xG31P/NJXvR9JALWm1tsdZkwsmHaGviw2hT
ocwfVPYFw/MPQlCRWNcognXw7WON3TM=
=yIub
-END PGP SIGNATURE End Message ---

Processed: [bts-link] source package emacs

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package emacs
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1017711 (http://bugs.debian.org/1017711)
> # Bug title: emacs-gtk: terminated with signal SIGABRT, 137 MB coredump
> #  * https://debbugs.gnu.org/58956
> #  * remote status changed: pending -> done
> #  * closed upstream
> tags 1017711 + fixed-upstream
Bug #1017711 [emacs-gtk] emacs-gtk: terminated with signal SIGABRT, 137 MB 
coredump
Added tag(s) fixed-upstream.
> usertags 1017711 - status-pending
Usertags were: status-pending.
There are now no usertags set.
> usertags 1017711 + status-done
There were no usertags set.
Usertags are now: status-done.
> # remote status report for #1023414 (http://bugs.debian.org/1023414)
> # Bug title: emacs-gtk: "lax space matching" no longer works
> #  * https://debbugs.gnu.org/58992
> #  * remote status changed: (?) -> done
> #  * closed upstream
> tags 1023414 + fixed-upstream
Bug #1023414 [emacs-gtk] emacs-gtk: "lax space matching" no longer works
Added tag(s) fixed-upstream.
> usertags 1023414 + status-done
There were no usertags set.
Usertags are now: status-done.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package mutt

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package mutt
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1023599 (http://bugs.debian.org/1023599)
> # Bug title: mutt: FTBFS due to lack of gpgme-config since gpgme1.0 1.18.0-2
> #  * https://gitlab.com/muttmua/mutt/-/issues/430
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1023599 + fixed-upstream
Bug #1023599 [mutt] mutt: FTBFS due to lack of gpgme-config since gpgme1.0 
1.18.0-2
Added tag(s) fixed-upstream.
> usertags 1023599 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#1023826: libnvme: Fails to build on big endian systems (e.g. s390x)

[Benjamin Drung]

Package: libnvme
Version: 1.2-1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar ubuntu-patch
X-Debbugs-Cc: bdr...@debian.org

Dear Maintainer,

libnvme fails to build on big endian systems (e.g. s390x). I forwarded
the bug upstream and they fixed. Please apply the fix (see attachement).

Thanks for considering the patch.

-- 
Benjamin Drung
Debian & Ubuntu Developer
diff -Nru libnvme-1.2/debian/patches/mi-endian-fixes.patch 
libnvme-1.2/debian/patches/mi-endian-fixes.patch
--- libnvme-1.2/debian/patches/mi-endian-fixes.patch1970-01-01 
01:00:00.0 +0100
+++ libnvme-1.2/debian/patches/mi-endian-fixes.patch2022-11-10 
16:24:08.0 +0100
@@ -0,0 +1,61 @@
+From ac657355bc86b71e1d2d8dd6079d5d69332dedaa Mon Sep 17 00:00:00 2001
+From: Jeremy Kerr 
+Date: Thu, 10 Nov 2022 12:20:37 +0800
+Subject: [PATCH] mi: endian fixes
+
+We have a couple of endian issues in the mi code: one where we're not
+converting cdw0 for MI commands, and one where we're using the wrong
+byte length for an existing conversion. There is also an error in the
+test suite, where we should be converting the nsze field of a
+nvme_id_ns.
+
+This change fixes those, so that the test suite passes on a BE platform
+(ppc64 in my case).
+
+Fixes: https://github.com/linux-nvme/libnvme/issues/524
+Signed-off-by: Jeremy Kerr 
+Bug-Ubuntu: https://launchpad.net/bugs/1995935
+Origin: https://github.com/linux-nvme/libnvme/pull/529
+---
+ src/nvme/mi.c | 4 ++--
+ test/mi.c | 2 +-
+ 2 files changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/src/nvme/mi.c b/src/nvme/mi.c
+index cd86e41..1a34208 100644
+--- a/src/nvme/mi.c
 b/src/nvme/mi.c
+@@ -139,7 +139,7 @@ int nvme_mi_scan_ep(nvme_mi_ep_t ep, bool force_rescan)
+   struct nvme_mi_ctrl *ctrl;
+   __u16 id;
+ 
+-  id = le32_to_cpu(list.identifier[i]);
++  id = le16_to_cpu(list.identifier[i]);
+   if (!id)
+   continue;
+ 
+@@ -985,7 +985,7 @@ static int nvme_mi_read_data(nvme_mi_ep_t ep, __u32 cdw0,
+   req_hdr.hdr.nmp = (NVME_MI_ROR_REQ << 7) |
+   (NVME_MI_MT_MI << 3); /* we always use command slot 0 */
+   req_hdr.opcode = nvme_mi_mi_opcode_mi_data_read;
+-  req_hdr.cdw0 = cdw0;
++  req_hdr.cdw0 = cpu_to_le32(cdw0);
+ 
+   memset(&req, 0, sizeof(req));
+   req.hdr = &req_hdr.hdr;
+diff --git a/test/mi.c b/test/mi.c
+index 102cea9..4c7f1f2 100644
+--- a/test/mi.c
 b/test/mi.c
+@@ -1287,7 +1287,7 @@ static void test_admin_ns_mgmt_create(struct nvme_mi_ep 
*ep)
+   assert(!rc);
+   assert(ns == 0x01020304);
+ 
+-  nsid.nsze = 42;
++  nsid.nsze = cpu_to_le64(42);
+   rc = nvme_mi_admin_ns_mgmt_create(ctrl, &nsid, 0, &ns);
+   assert(rc);
+ }
+-- 
+2.37.2
+
diff -Nru libnvme-1.2/debian/patches/series libnvme-1.2/debian/patches/series
--- libnvme-1.2/debian/patches/series   1970-01-01 01:00:00.0 +0100
+++ libnvme-1.2/debian/patches/series   2022-11-10 16:20:16.0 +0100
@@ -0,0 +1 @@
+mi-endian-fixes.patch

Bug#979101: Legally problematic GPL-3+ readline dependency

[Carlos Henrique Lima Melara]

Hi, Bastian.

On Wed, 27 Apr 2022 11:53:20 +0200 Bastian Germann  wrote:
> On Mon, 18 Oct 2021 14:17:22 -0300 Carlos Henrique Lima Melara 
>  wrote:
> > On Tue, Oct 12, 2021 at 12:44:18PM +0200, Bastian Germann wrote:
> > > I see that upstream included your patch to deal with this. Can you please
> > > include that in the package and change the build dependency? I am happy to
> > > sponsor the new revision.
> > 
> > Thanks for the offer and I'll take it, but I'd like to wait a bit
> > because my patch solved the dependency and also broke the autocompletion
> > of the package. Turns out the libedit compatibility layer has some
> > bugs, I've already reported one and it was fixed by the developers, but I
> > need some time to test the behaviour of devtodo after the fix.
> > 
> > Maybe I'll be able to do that next weekend, but I don't think we'll
> > have time to upload a new version before the 27th of October deadline.
>
> Any news on this?


Actually, yes. Turns out that I'm stupid. The first patch did fix
everything without breaking the program, but I inserted an
rl_redisplay() in a wrong place and it introduced a bug in my
devolopment/testing tree. So I thought there was a bug breaking the
program behaviour, but there wasn't actually.

I prepared a new upload including the patch [1] I sent to upstream.
Would you be able to review it and upload if everything is okay?
Thanks again for helping me with this issue.

This patch produced a compilation error so I sent another patch to
upstream (and included it in the upload) [2], but he hasn't responded
yet.

Cheers,
Charles

[1] https://salsa.debian.org/debian/devtodo
[2] https://github.com/alecthomas/devtodo/pull/6


signature.asc
Description: PGP signature

Bug#1014120: marked as done (libowfat FTBFS: ln: failed to create hard link 'libowfat/buffer.h')

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2022 17:06:44 +0100
with message-id <4c6223e5-d901-ca88-1e8b-a922fbd38...@debian.org>
and subject line Re: Bug#1014120: libowfat FTBFS: ln: failed to create hard 
link 'libowfat/buffer.h'
has caused the Debian Bug report #1014120,
regarding libowfat FTBFS: ln: failed to create hard link 'libowfat/buffer.h'
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.)


-- 
1014120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libowfat
Version: 0.32-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=libowfat&ver=0.32-1

...
/usr/bin/make -f /<>/GNUmakefile -C build-glibc 
SRC=/<>/ CFLAGS="-g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -I. -I.." DIET=''
make[2]: Entering directory '/<>/build-glibc'
ln -f /<>/buffer.h libowfat/buffer.h
ln: failed to create hard link 'libowfat/buffer.h' => 
'/<>/buffer.h': No such file or directory
make[2]: *** [/<>/GNUmakefile:217: libowfat/buffer.h] Error 1
--- End Message ---
--- Begin Message ---

Version: 0.32-4--- End Message ---

Bug#1018922: kbibtex crashes on startup

[Adrian Bunk]

On Sat, Sep 03, 2022 at 07:05:46PM -0700, Arnout Boelens wrote:
> Looks like it might be a QT bug:
> 
> https://bugs.kde.org/show_bug.cgi?id=433084

Is this fixed in Qt 5.15.6 in unstable or in Qt 5.15.7 in experimental?

Thanks
Adrian

Bug#1017316: marked as done (libowfat byte.h incompatible with glibc 2.34)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2022 15:49:15 +
with message-id 
and subject line Bug#1017157: fixed in libowfat 0.32-4
has caused the Debian Bug report #1017157,
regarding libowfat byte.h incompatible with glibc 2.34
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.)


-- 
1017157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gatling
Version: 0.13-6.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> gcc -c connstat.c -o connstat.o -I. -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -Wall -DUSE_ZLIB
> In file included from /usr/include/features.h:489,
>  from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/stdlib.h:25,
>  from connstat.c:2:
> /usr/include/x86_64-linux-gnu/sys/cdefs.h:297:60: error: macro 
> "__has_attribute" requires an identifier
>   297 | #if __GNUC_PREREQ (2,96) || __glibc_has_attribute (__pure__)
>   |^
> make[2]: *** [GNUmakefile:110: connstat.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/08/13/gatling_0.13-6.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220813&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

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

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

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated libowfat package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 10 Nov 2022 16:32:49 +0100
Source: libowfat
Architecture: source
Version: 0.32-4
Distribution: unstable
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Bastian Germann 
Closes: 1017157
Changes:
 libowfat (0.32-4) unstable; urgency=high
 .
   * QA upload
   * Prevent identifiers from conflicting with glibc (Closes: #1017157)
   * Drop unused package libowfat-dietlibc-dev (simplifies build)
Checksums-Sha1:
 f9f81d1df635d3e850b9ba3c7685d4dcde751449 1730 libowfat_0.32-4.dsc
 8ace39be88baabccf506107b864f5a7adda5cabd 14588 libowfat_0.32-4.debian.tar.xz
 cfabe9b1e26f7111cffe0278fad95921db6e2dfb 5570 libowfat_0.32-4_source.buildinfo
Checksums-Sha256:
 5e4bd17b96dcf8f9a15213d77c55561977c0f311800ad869888729ee74cd950d 1730 
libowfat_0.32-4.dsc
 0c80ef8c2c8bc9b25886647bb5bf48b3ffdc3e81277d0b7249f14ce3ad862a9c 14588 
libowfat_0.32-4.debian.tar.xz
 ed0cbf09c1d3033f6026d90481591598830c75f7f829c833e52db6c4d4067c4f 5570 
libowfat_0.32-4_source.buildinfo
Files:
 ca77045e514580c828de976a6292b7e1 1730 libs optional libowfat_0.32-4.dsc
 5054e138ab1afd36df33e030eb204dd4 14588 libs optional 
libowfat_0.32-4.debian.tar.xz
 229e5faa390ba1e3f1b50ab5f328557a 5570 libs optional 
libowfat_0.32-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmNtG10QHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFNQPC/4xOXAiVxUu4MO7eOhFp9BQW3hCiXMboVtg
jzArnQVGoRk7UoDiGN

Bug#1023763: marked as done (mathcomp-algebra-tactics: autopkgtest regression: interface mismatch on Elpi__BuiltinFindlib)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2022 15:49:24 +
with message-id 
and subject line Bug#1023763: fixed in mathcomp-algebra-tactics 1.0.0-8
has caused the Debian Bug report #1023763,
regarding mathcomp-algebra-tactics: autopkgtest regression: interface mismatch 
on Elpi__BuiltinFindlib
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.)


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

Source: mathcomp-algebra-tactics
Version: 1.0.0-7
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
mathcomp-algebra-tactics from testing1.0.0-7
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 
mathcomp-algebra-tactics/1.0.0-7. I.e. due to versioned dependencies or 
breaks/conflicts.

[1] https://qa.debian.org/excuses.php?package=mathcomp-algebra-tactics

https://ci.debian.net/data/autopkgtest/testing/amd64/m/mathcomp-algebra-tactics/28060854/log.gz

Error:
Dynlink error: interface mismatch on Elpi__BuiltinFindlib paths:
/usr/lib/ocaml/coq/../coq-core/plugins/ltac
/usr/lib/ocaml/coq/../coq-core/plugins/ssreflect
/usr/lib/ocaml/coq/../coq-core/plugins/ring
/usr/lib/ocaml/coq/../coq-core/plugins/ssrmatching
/usr/lib/ocaml/coq/../coq-core/plugins/nsatz
/usr/lib/ocaml/coq/../coq-core/plugins/ltac2
/usr/lib/ocaml/coq/../coq-core/plugins/number_string_notation
/usr/lib/ocaml/coq/../coq-core/plugins/cc
/usr/lib/ocaml/coq/../coq-core/plugins/firstorder
/usr/lib/ocaml/coq/../coq-core/plugins/tauto
/usr/lib/ocaml/coq/../coq-core/plugins/rtauto
/usr/lib/ocaml/coq/../coq-core/plugins/extraction
/usr/lib/ocaml/coq/../coq-core/plugins/zify
/usr/lib/ocaml/coq/../coq-core/plugins/funind
/usr/lib/ocaml/coq/../coq-core/plugins/micromega
/usr/lib/ocaml/coq/../coq-core/plugins/derive
/usr/lib/ocaml/coq/../coq-core/plugins/btauto
/usr/lib/ocaml/coq/../coq-core/..
/usr/lib/ocaml/coq/user-contrib/Ltac2
/usr/lib/ocaml/coq/user-contrib/elpi
/usr/lib/ocaml/coq/user-contrib/elpi/apps
/usr/lib/ocaml/coq/user-contrib/elpi/apps/eltac
/usr/lib/ocaml/coq/user-contrib/elpi/apps/derive
/usr/lib/ocaml/coq/user-contrib/mathcomp
/usr/lib/ocaml/coq/user-contrib/mathcomp/algebra
/usr/lib/ocaml/coq/user-contrib/mathcomp/ssreflect
/usr/lib/ocaml/coq/user-contrib/mathcomp/algebra_tactics
/usr/lib/ocaml/coq/user-contrib/mathcomp/zify
/usr/lib/ocaml/coq/user-contrib/mathcomp/fingroup
/usr/local/lib/ocaml/4.13.1
/usr/lib/ocaml
/usr/lib/ocaml/METAS


autopkgtest [19:17:45]: test command1



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: mathcomp-algebra-tactics
Source-Version: 1.0.0-8
Done: Julien Puydt 

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

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated mathcomp-algebra-tactics 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 10 Nov 2022 16:22:08 +0100
Source: mathcomp-algebra-tactics
Architecture: source
Version: 1.0.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Mai

Bug#1017157: marked as done (libowfat byte.h incompatible with glibc 2.34)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2022 15:49:15 +
with message-id 
and subject line Bug#1017157: fixed in libowfat 0.32-4
has caused the Debian Bug report #1017157,
regarding libowfat byte.h incompatible with glibc 2.34
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.)


-- 
1017157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gatling
Version: 0.13-6.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> gcc -c connstat.c -o connstat.o -I. -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -Wall -DUSE_ZLIB
> In file included from /usr/include/features.h:489,
>  from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/stdlib.h:25,
>  from connstat.c:2:
> /usr/include/x86_64-linux-gnu/sys/cdefs.h:297:60: error: macro 
> "__has_attribute" requires an identifier
>   297 | #if __GNUC_PREREQ (2,96) || __glibc_has_attribute (__pure__)
>   |^
> make[2]: *** [GNUmakefile:110: connstat.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/08/13/gatling_0.13-6.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220813&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.


--- End Message ---
--- Begin Message ---
Source: libowfat
Source-Version: 0.32-4
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated libowfat package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 10 Nov 2022 16:32:49 +0100
Source: libowfat
Architecture: source
Version: 0.32-4
Distribution: unstable
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Bastian Germann 
Closes: 1017157
Changes:
 libowfat (0.32-4) unstable; urgency=high
 .
   * QA upload
   * Prevent identifiers from conflicting with glibc (Closes: #1017157)
   * Drop unused package libowfat-dietlibc-dev (simplifies build)
Checksums-Sha1:
 f9f81d1df635d3e850b9ba3c7685d4dcde751449 1730 libowfat_0.32-4.dsc
 8ace39be88baabccf506107b864f5a7adda5cabd 14588 libowfat_0.32-4.debian.tar.xz
 cfabe9b1e26f7111cffe0278fad95921db6e2dfb 5570 libowfat_0.32-4_source.buildinfo
Checksums-Sha256:
 5e4bd17b96dcf8f9a15213d77c55561977c0f311800ad869888729ee74cd950d 1730 
libowfat_0.32-4.dsc
 0c80ef8c2c8bc9b25886647bb5bf48b3ffdc3e81277d0b7249f14ce3ad862a9c 14588 
libowfat_0.32-4.debian.tar.xz
 ed0cbf09c1d3033f6026d90481591598830c75f7f829c833e52db6c4d4067c4f 5570 
libowfat_0.32-4_source.buildinfo
Files:
 ca77045e514580c828de976a6292b7e1 1730 libs optional libowfat_0.32-4.dsc
 5054e138ab1afd36df33e030eb204dd4 14588 libs optional 
libowfat_0.32-4.debian.tar.xz
 229e5faa390ba1e3f1b50ab5f328557a 5570 libs optional 
libowfat_0.32-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmNtG10QHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFNQPC/4xOXAiVxUu4MO7eOhFp9BQW3hCiXMboVtg
jzArnQVGoRk7UoDi

Bug#1023762: marked as done (mathcomp-analysis: autopkgtest regression: interface mismatch on Elpi__BuiltinFindlib)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2022 15:49:33 +
with message-id 
and subject line Bug#1023762: fixed in mathcomp-analysis 0.5.4-3
has caused the Debian Bug report #1023762,
regarding mathcomp-analysis: autopkgtest regression: interface mismatch on 
Elpi__BuiltinFindlib
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.)


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

Source: mathcomp-analysis
Version: 0.5.4-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
mathcomp-analysis  from testing0.5.4-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 
mathcomp-analysis/0.5.4-2. I.e. due to versioned dependencies or 
breaks/conflicts.

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

https://ci.debian.net/data/autopkgtest/testing/arm64/m/mathcomp-analysis/28071927/log.gz

Error:
Dynlink error: interface mismatch on Elpi__BuiltinFindlib paths:
/usr/lib/ocaml/coq/../coq-core/plugins/zify
/usr/lib/ocaml/coq/../coq-core/plugins/derive
/usr/lib/ocaml/coq/../coq-core/plugins/funind
/usr/lib/ocaml/coq/../coq-core/plugins/micromega
/usr/lib/ocaml/coq/../coq-core/plugins/rtauto
/usr/lib/ocaml/coq/../coq-core/plugins/ssreflect
/usr/lib/ocaml/coq/../coq-core/plugins/number_string_notation
/usr/lib/ocaml/coq/../coq-core/plugins/extraction
/usr/lib/ocaml/coq/../coq-core/plugins/firstorder
/usr/lib/ocaml/coq/../coq-core/plugins/ssrmatching
/usr/lib/ocaml/coq/../coq-core/plugins/ltac
/usr/lib/ocaml/coq/../coq-core/plugins/ltac2
/usr/lib/ocaml/coq/../coq-core/plugins/nsatz
/usr/lib/ocaml/coq/../coq-core/plugins/tauto
/usr/lib/ocaml/coq/../coq-core/plugins/btauto
/usr/lib/ocaml/coq/../coq-core/plugins/ring
/usr/lib/ocaml/coq/../coq-core/plugins/cc
/usr/lib/ocaml/coq/../coq-core/..
/usr/lib/ocaml/coq/user-contrib/HB
/usr/lib/ocaml/coq/user-contrib/elpi
/usr/lib/ocaml/coq/user-contrib/elpi/apps
/usr/lib/ocaml/coq/user-contrib/elpi/apps/derive
/usr/lib/ocaml/coq/user-contrib/elpi/apps/eltac
/usr/lib/ocaml/coq/user-contrib/mathcomp
/usr/lib/ocaml/coq/user-contrib/mathcomp/field
/usr/lib/ocaml/coq/user-contrib/mathcomp/ssreflect
/usr/lib/ocaml/coq/user-contrib/mathcomp/bigenough
/usr/lib/ocaml/coq/user-contrib/mathcomp/solvable
/usr/lib/ocaml/coq/user-contrib/mathcomp/finmap
/usr/lib/ocaml/coq/user-contrib/mathcomp/algebra
/usr/lib/ocaml/coq/user-contrib/mathcomp/analysis
/usr/lib/ocaml/coq/user-contrib/mathcomp/analysis/altreals
/usr/lib/ocaml/coq/user-contrib/mathcomp/fingroup
/usr/lib/ocaml/coq/user-contrib/Ltac2
/usr/local/lib/ocaml/4.13.1
/usr/lib/ocaml
/usr/lib/ocaml/METAS


autopkgtest [16:17:00]: test command1



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: mathcomp-analysis
Source-Version: 0.5.4-3
Done: Julien Puydt 

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

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated mathcomp-analysis package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 10 Nov 2022 16:2

Bug#1022281: marked as done (iem-plugin-suite: FTBFS: ld: AllRADecoder_artefacts/None/libAllRADecoder_SharedCode.a(juce_core.cpp.o): undefined reference to symbol 'inflateEnd')

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2022 14:42:13 +
with message-id 
and subject line Bug#1022281: fixed in juce 7.0.2~ds0-3
has caused the Debian Bug report #1022281,
regarding iem-plugin-suite: FTBFS: ld: 
AllRADecoder_artefacts/None/libAllRADecoder_SharedCode.a(juce_core.cpp.o): 
undefined reference to symbol 'inflateEnd'
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.)


-- 
1022281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: iem-plugin-suite
Version: 1.13.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -DJUCE_JACK=1 -DJUCE_MODAL_LOOPS_PERMITTED=1 -Wl,-z,relro 
> -Wl,-z,now -Wl,--no-undefined 
> CMakeFiles/AllRADecoder_Standalone.dir/usr/share/juce/modules/juce_audio_plugin_client/juce_audio_plugin_client_AAX.cpp.o
>  
> CMakeFiles/AllRADecoder_Standalone.dir/usr/share/juce/modules/juce_audio_plugin_client/juce_audio_plugin_client_ARA.cpp.o
>  
> CMakeFiles/AllRADecoder_Standalone.dir/usr/share/juce/modules/juce_audio_plugin_client/juce_audio_plugin_client_LV2.cpp.o
>  
> CMakeFiles/AllRADecoder_Standalone.dir/usr/share/juce/modules/juce_audio_plugin_client/juce_audio_plugin_client_Standalone.cpp.o
>  
> CMakeFiles/AllRADecoder_Standalone.dir/usr/share/juce/modules/juce_audio_plugin_client/juce_audio_plugin_client_Unity.cpp.o
>  
> CMakeFiles/AllRADecoder_Standalone.dir/usr/share/juce/modules/juce_audio_plugin_client/juce_audio_plugin_client_VST2.cpp.o
>  
> CMakeFiles/AllRADecoder_Standalone.dir/usr/share/juce/modules/juce_audio_plugin_client/juce_audio_plugin_client_VST3.cpp.o
>  -o AllRADecoder_artefacts/None/Standalone/AllRADecoder  
> AllRADecoder_artefacts/None/libAllRADecoder_SharedCode.a 
> /usr/lib/x86_64-linux-gnu/libpng16.so /usr/lib/x86_64-linux-gnu/libjpeg.so 
> ../libLAF_fonts.a /usr/lib/x86_64-linux-gnu/libasound.so -lGL 
> /usr/lib/x86_64-linux-gnu/libfreetype.so -lrt -ldl -lpthread 
> /usr/bin/ld: 
> AllRADecoder_artefacts/None/libAllRADecoder_SharedCode.a(juce_core.cpp.o): 
> undefined reference to symbol 'inflateEnd'
> /usr/bin/ld: /lib/x86_64-linux-gnu/libz.so.1: error adding symbols: DSO 
> missing from command line
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/iem-plugin-suite_1.13.0-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221023&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: juce
Source-Version: 7.0.2~ds0-3
Done: IOhannes m zmölnig (Debian/GNU) 

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated juce 
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, 10 Nov 2022 13:55:28 +0100
Source: juce
Architecture: source
Version: 7.0.2~ds0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 

Processed: forward

[Debian Bug Tracking System]

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

> forwarded 1019835 https://forum.filezilla-project.org/viewtopic.php?t=55191
Bug #1019835 [src:filezilla] filezilla: Please transition to wxwidgets3.2
Set Bug forwarded-to-address to 
'https://forum.filezilla-project.org/viewtopic.php?t=55191'.
>
End of message, stopping processing here.

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

Processed: vim: buffer overflow in block_insert

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 vim/2:8.2.3455-1
Bug #1023818 [vim] vim: buffer overflow in block_insert
Marked as fixed in versions vim/2:8.2.3455-1.
> close -1
Bug #1023818 [vim] vim: buffer overflow in block_insert
Marked Bug as done

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

Bug#1023818: vim: buffer overflow in block_insert

[Helmut Grohne]

Package: vim
Version: 2:8.1.0875-5
Severity: serious
Tags: security upstream fixed-upstream
X-Debbugs-Cc: Debian Security Team 
Control: fixed -1 vim/2:8.2.3455-1
Control: close -1

Hi,

while looking into vim source, I stumbled into
https://github.com/vim/vim/commit/4067bd3604215b48e4b4201e28f9e401b08418e4

Among other things, this change adds "if (spaces < 0) spaces = 0" to
block_insert. While this has been fixed in bookworm and later, it is
missing from bullseye and earlier. If spaces happens to be < 0, bad
things happen when we later vim_memset(..., ' ', (size_t)spaces).

A prospective stable update should probably fix this.

Helmut

Bug#1023812: git: Source package misses dependency to libssl-dev package

[doak]

Package: git
Version: 1:2.30.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: doak+...@posteo.net

Dear Maintainer,

The source package of `git` seems not to specify the dependency to
`libssl-dev`.

Steps to reproduce:
Compiling Git on a Debian live CD fails. These are the steps to
reproduce:
# apt build-dep git
git$ make

Make complains about missing OpenSSL header. Installing `libssl-dev`
fixes this.

Expected:
I would that after installing build dependencies for Git, it is built
successfully.


Best regards,
doak



-- System Information:
Debian Release: 11.5
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages git depends on:
ii  git-man  1:2.30.2-1
ii  libc62.31-13+deb11u4
ii  libcurl3-gnutls  7.74.0-1.3+deb11u3
ii  liberror-perl0.17029-1
ii  libexpat12.2.10-2+deb11u3
ii  libpcre2-8-0 10.36-2+deb11u1
ii  perl 5.32.1-4+deb11u2
ii  zlib1g   1:1.2.11.dfsg-2+deb11u2

Versions of packages git recommends:
ii  ca-certificates  20210119
ii  less 551-2
ii  openssh-client [ssh-client]  1:8.4p1-5+deb11u1
ii  patch2.7.6-7

Versions of packages git suggests:
ii  gettext-base  0.21-4
pn  git-cvs   
pn  git-daemon-run | git-daemon-sysvinit  
pn  git-doc   
pn  git-el
pn  git-email 
pn  git-gui   
pn  git-mediawiki 
pn  git-svn   
pn  gitk  
pn  gitweb

-- no debconf information

Bug#1023811: golang-github-grpc-ecosystem-go-grpc-middleware_1.3.0-1 sources changed in the archive?

[Adrian Bunk]

Package: ftp.debian.org
Severity: grave
X-Debbugs-Cc: debian-wb-t...@lists.debian.org, Thomas Goirand 

https://buildd.debian.org/status/logs.php?pkg=golang-github-grpc-ecosystem-go-grpc-middleware&ver=1.3.0-1&arch=all&suite=experimental

The three Maybe-Failed until November 3rd at the bottom are normal FTBFS.

But the Maybe-Given-back since yesterday are:

...
Get:1 https://deb.debian.org/debian experimental/main 
golang-github-grpc-ecosystem-go-grpc-middleware 1.3.0-1 (dsc) [2857 B]
Err:1 https://deb.debian.org/debian experimental/main 
golang-github-grpc-ecosystem-go-grpc-middleware 1.3.0-1 (dsc)
  Hash Sum mismatch
  Hashes of expected file:
   - SHA256:8e86e0a9cc31461c0f564e8feefb2e1e9ec05c265ab06e96fd32b7de787bc504
   - Filesize:2857 [weak]
   - MD5Sum:c4d33ab09e4f4a95c819dd1de88d0876 [weak]
  Hashes of received file:
   - SHA256:8bbee530bbdb11a58a275c34878c372558223c294384897822eba1338b84db82
   - MD5Sum:8d6eee1b2b773c9be12536396ba949a6 [weak]
   - Filesize:2857 [weak]
  Last modification reported: Wed, 26 Oct 2022 14:32:16 +
Get:2 https://deb.debian.org/debian experimental/main 
golang-github-grpc-ecosystem-go-grpc-middleware 1.3.0-1 (tar) [104 kB]
Get:3 https://deb.debian.org/debian experimental/main 
golang-github-grpc-ecosystem-go-grpc-middleware 1.3.0-1 (diff) [2652 B]
E: Failed to fetch 
https://deb.debian.org/debian/pool/main/g/golang-github-grpc-ecosystem-go-grpc-middleware/golang-github-grpc-ecosystem-go-grpc-middleware_1.3.0-1.dsc
  Hash Sum mismatch
   Hashes of expected file:
- SHA256:8e86e0a9cc31461c0f564e8feefb2e1e9ec05c265ab06e96fd32b7de787bc504
- Filesize:2857 [weak]
   Fetched 109 kB in 0s (416 kB/s)
 - MD5Sum:c4d33ab09e4f4a95c819dd1de88d0876 [weak]
   Hashes of received file:
- SHA256:8bbee530bbdb11a58a275c34878c372558223c294384897822eba1338b84db82
- MD5Sum:8d6eee1b2b773c9be12536396ba949a6 [weak]
- Filesize:2857 [weak]
   Last modification reported: Wed, 26 Oct 2022 14:32:16 +
E: Failed to fetch some archives.
E: apt-get for sources failed
...


I can reproduce the problem locally with
$ apt-get source golang-github-grpc-ecosystem-go-grpc-middleware/experimental

This is not supposed to happen, and I haven't seen this before.

Bug#1023758: marked as pending in pipewire

[Dylan Aïssi]

Control: tag -1 pending

Hello,

Bug #1023758 in pipewire 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/utopia-team/pipewire/-/commit/c08408bdac3f4a8fa79fbd61ed6aee2297da118b


pipewire: depend on adduser (Closes: #1023758)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1023758

Processed: Bug#1023758 marked as pending in pipewire

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1023758 [pipewire] pipewire: calls addgroup without an adduser dependency
Added tag(s) pending.

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

Bug#999033: marked as done (asterisk-prompt-fr-armelle: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2022 13:04:28 +
with message-id 
and subject line Bug#999033: fixed in asterisk-prompt-fr-armelle 20070613-2.2
has caused the Debian Bug report #999033,
regarding asterisk-prompt-fr-armelle: missing required debian/rules targets 
build-arch and/or build-indep
to be marked as done.

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

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


-- 
999033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: asterisk-prompt-fr-armelle
Version: 20070613-2.1
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: asterisk-prompt-fr-armelle
Source-Version: 20070613-2.2
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
asterisk-prompt-fr-armelle, 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.
Adrian Bunk  (supplier of updated asterisk-prompt-fr-armelle 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Nov 2022 14:06:48 +0200
Source: asterisk-prompt-fr-armelle
Architecture: source
Version: 20070613-2.2
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP team 
Changed-By: Adrian Bunk 
Closes: 965429 999033
Changes:
 asterisk-prompt-fr-armelle (20070613-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/compat: 5 -> 7. (Closes: #965429)
   * debian/rules: Add build-arch. (Closes: #999033)
Checksums-Sha1:
 b7a356e4505d99202ca9940a2c61d03c4d42c77a 1907 
asterisk-prompt-fr-armelle_20070613-2.2.dsc
 3dc634e3caf1b8f39721e363c6719aae5c09194c 2658 
asterisk-prompt-fr-armelle_20070613-2.2.diff.gz
Checksums-Sha256:
 93c0a6a05cb89622482d9c17e4d47c95eb6c2ee268b9aa7522690e46278b4675 1907 
asterisk-prompt-fr-armelle_20070613-2.2.dsc
 1e9ca644d6af4c0ebbfc6109961ea479fd4e2ebb0e783716c767007cac006587 2658 
asterisk-prompt-fr-armelle_20070613-2.2.diff.gz
Files:
 105fa81245664de45bf210516c3b662e 1907 comm extra 
asterisk-prompt-fr-armelle_20070613-2.2.dsc
 4642939d9686ed7415d18f58b7d7072b 2658 comm extra 
asterisk-prompt-fr-armelle_20070613-2.2.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmNqSVsACgkQiNJCh6LY
mLHfdg//SwH1yhjLu7ptJ0WUBuP8uSLZz35kjNPc1MMgFKVjSNqzK3fiDcJOcTpy
PgBi3Gk24E4sMJRRfK7AixsvuoDosF7KYUOARs+mFxQtdeCA5JvGjUAAZqpJw9yK
tQ/rugitypLcHST1is8qX9G4RcXldjJHGbjDWubmCUphidcYqmItFbHIG/dN3/5u
q4J1UofeUNgBC92x20Ikshe3gixPna6qKOxZYzJAsqDNXwFkYxLC09GJXC9eHpO8
xSS32Og2zoFBHm2jGJ07KIt6OrRlP6EzI0wZLnQPFPBxgvu5iFKqjs4y7bwbDcLG
Vu1XdJyP84xIjhl7F4G00i6U5VAPdWm6ZghkE3iEM2oZpuvADDBkD0C4NHIfWeuf
+ywc/39K55ntr4+ft2k9kK8ptMwF84AtQriROuMEblWGZsnI9L7BxWlb70ENgIL9
0uz8IcY/8dUdSpukCrF0HvAMAcWPDQaHanqm0rU+dGD5gm9rQj159PG+Yqitpj3H
J3toxU483fXVdIeQJxBxPdNka4j04fgO3EZ46O7Ox8JW356ZxwbNvGPAQ2RJB5mL
DUSxCOyz5yfXHuW5vzGb/eO2VYVNmn38lvrqrWyVLDp0Okc27fPe8gLG6FILHGlZ
2+hBDgQIXXqBqpHuGABvUViH7PlvdLszCSkkcOgPVenHO+g6sZQ=
=tyPP
-END PGP SIGNATURE End Message ---

Bug#965429: marked as done (asterisk-prompt-fr-armelle: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2022 13:04:28 +
with message-id 
and subject line Bug#965429: fixed in asterisk-prompt-fr-armelle 20070613-2.2
has caused the Debian Bug report #965429,
regarding asterisk-prompt-fr-armelle: Removal of obsolete debhelper compat 5 
and 6 in bookworm
to be marked as done.

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

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


-- 
965429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965429
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: asterisk-prompt-fr-armelle
Version: 20070613-2
Severity: normal
Usertags: compat-5-6-removal

Hi,

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

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

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

  * Compat 7 is the bare minimum


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

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


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


Thanks,
~Niels


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

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

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

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: asterisk-prompt-fr-armelle
Source-Version: 20070613-2.2
Done: Adrian Bunk 

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated asterisk-prompt-fr-armelle 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Nov 2022 14:06:48 +0200
Source: asterisk-prompt-fr-armelle
Architecture: source
Version: 20070613-2.2
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP team 
Changed-By: Adrian Bunk 
Closes: 965429 999033
Changes:
 asterisk-prompt-fr-armelle (20070613-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/compat: 5 -> 7. (Closes: #965429)
   * debian/rules: Add build-arch. (Closes: #999033)
Checksums-Sha1:
 b7a356e4505d99202ca9940a2c61d03c4d42c77a 1907 
asterisk-prompt-fr-armelle_20070613-2.2.dsc
 3dc634e3caf1b8f39721e363c6719aae5c09194c 2658 
asterisk-prompt-fr-armelle_20070613-2.2.diff.gz
Checksums-Sha256:
 93c0a6a05cb89622482d9c17e4d47c95eb6c2ee268b9aa7522690e46278b4675 1907 
asterisk-prompt-fr-armelle_20070613-2.2.dsc
 1e9ca644d6af4c0ebbfc6109961ea479fd4e2ebb0e783716c767007cac006587 2658 
asterisk-prompt-fr-armelle_20070613-2.2.diff.gz
Files:
 105fa81245664de45bf210516c3b662e 1907 comm extra 
asterisk-prompt-fr-armelle_20070613-2.2.dsc
 4642939d9686ed7415d18f58b7d7072b 2658 comm extra 
asterisk-prompt-fr-armelle_20070613-2.2.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmNqSVsACgkQiNJCh6LY
mLHfdg//SwH1yhjLu7ptJ0WUBuP8uSLZz35kjNPc1MMgFKVjSNqzK3fiDcJOcTpy
PgBi3Gk24E4sMJRRfK7AixsvuoDosF7KYUOARs+mFxQtdeCA5JvGjUAAZqpJw9yK
tQ/rugitypLcHST1is8qX9G4RcXldjJHGbjDWubmCUphidcYqmItFbHIG/dN3/5u
q4J1UofeUNgBC92x20Ikshe3gixPna6qKOxZYzJAsqDNXwFkYxLC09GJXC9eHpO8
xSS32Og2zoFBHm2jGJ07KIt6OrRlP6EzI0wZLnQPFPBxgvu5iFKqjs4y7bwbDcLG
Vu1XdJyP84xIjhl7F4G00i6U5VAPdWm6ZghkE3iEM2oZpuvADDBkD0C4NHIfWeuf
+ywc/39K55ntr4+ft2k9kK8ptMwF84AtQriROuMEblWGZsnI9L7BxWlb70ENgIL9
0uz8IcY/8dUdSpukCrF0HvAMAcWPDQaHanqm0rU+dGD5gm9rQj159PG+Yqitpj3H
J3toxU483fXVdIeQJxBxPdNka4j04fgO3EZ46O7Ox8JW356ZxwbNvGPAQ2RJB5mL
DUSxCOyz5yfXHuW5vzGb/eO2VYVNmn38lvrqrWyVLDp0Okc27fPe8gLG6FILHGlZ
2+hBDgQIXXqBqpHuGABvUViH7PlvdLszCSkkcOgPVenHO+g6sZQ=
=tyPP
-END PGP SIGNATURE End Message ---

Bug#1004107: marked as done (meson: flaky autopkgtest on armhf: dictionary changed size during iteration -> timeout)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2022 13:52:56 +0100
with message-id 
and subject line Re: Bug#1004107: meson: flaky autopkgtest on armhf: dictionary 
changed size during iteration -> timeout
has caused the Debian Bug report #1004107,
regarding meson: flaky autopkgtest on armhf: dictionary changed size during 
iteration -> timeout
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.)


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

Source: meson
Version: 0.56.2-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky timeout

Dear maintainer(s),

I looked at the results of the autopkgtest of you package on armhf 
because it was showing up as a regression for the upload of 
python-defaults and setuptools. I noticed that the test regularly fails, 
what's worse, it also seems to hang as the test is killed because it 
hits an autopkgtest timeout.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests. In this case, Release Team members had to investigate if curl was 
OK to go into the next Stable point release.


Don't hesitate to reach out if you need help and some more information
from our infrastructure. Please note that the host we run our armhf 
tests on is very powerful. It has 160 cores and 255 GB RAM. This is 
sometimes the root cause of test that fail. It seems that before we 
switch to this host, the test was more reliable.


Paul

https://ci.debian.net/packages/m/meson/testing/amd64/

E.g. 
https://ci.debian.net/data/autopkgtest/testing/armhf/m/meson/18519155/log.gz


Ran 462 tests in 569.524s

OK (skipped=66)
Meson build system 0.61.0 Unit Tests
pytest-xdist not found, using unittest instead
Total time: 569.540 seconds
Meson build system 0.61.0 Project Tests
Using python 3.9.9 (main, Jan 12 2022, 16:10:51)

host machine compilers

c  : [gcc]  cc (gcc 11.2.0 "cc (Debian 11.2.0-13) 11.2.0")
cpp: [gcc]  c++ (gcc 11.2.0 "c++ (Debian 11.2.0-13) 11.2.0")
cs : [mono] mcs (mono 6.8.0.105)
cuda   : [not found]
cython : [not found]
d  : [llvm] ldc2 (llvm 1.28.0 "LDC - the LLVM D compiler (1.28.0):")
fortran: [gcc]  gfortran (gcc 11.2.0 "GNU Fortran (Debian 11.2.0-13) 
11.2.0")

java   : [unknown]  javac (unknown 11.0.13)
objc   : [gcc]  cc (gcc 11.2.0)
objcpp : [gcc]  c++ (gcc 11.2.0)
rust   : [rustc]rustc -C linker=cc (rustc 1.56.0)
swift  : [not found]
vala   : [valac]valac (valac 0.54.6)

tools

ninja  : /usr/bin/ninja (1.10.1)
cmake  : /usr/bin/cmake (3.22.1)
hotdoc : not found

Checking that configuring works...
Checking that introspect works...
Checking that building works...
Checking that testing works...
Checking that installing works...

Running tests with 160 workers
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python3.9/threading.py", line 973, in _bootstrap_inner
self.run()
  File "/usr/lib/python3.9/concurrent/futures/process.py", line 317, in run
result_item, is_broken, cause = self.wait_result_broken_or_wakeup()
  File "/usr/lib/python3.9/concurrent/futures/process.py", line 376, in 
wait_result_broken_or_wakeup

worker_sentinels = [p.sentinel for p in self.processes.values()]
  File "/usr/lib/python3.9/concurrent/futures/process.py", line 376, in 


worker_sentinels = [p.sentinel for p in self.processes.values()]
RuntimeError: dictionary changed size during iteration

Running cmake tests.

autopkgtest [16:04:29]: ERROR: timed out on command "su -s /bin/bash 
debci -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || 
true;  . ~/.profile >/dev/null 2>&1 || true; 
buildtree="/tmp/autopkgtest-lxc.f3gr65px/downtmp/build.IRe/src"; mkdir 
-p -m 1777 -- 
"/tmp/autopkgtest-lxc.f3gr65px/downtmp/exhaustive-artifacts"; export 
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.f3gr65px/downtmp/exhaustive-artifacts"; 
export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 
"/tmp/autopkgtest-lxc.f3gr65px/downtmp/autopkgtest_tmp"; export 
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.f3gr65px/downtmp/autopkgtest_tmp"; 
export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; 
export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=160; unset 
LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY 
LC_MESSAGES LC_PAPER LC_NAME

Bug#1013302: ntopng FTBFS /build/1st/ntopng-5.2.1+dfsg1/debian/missing-sources/gauge.coffee:179:3: error: Can't reference 'this' before calling super in derived class constructors

[Blair Noctis]

On Tue, 21 Jun 2022 09:08:56 +0100 Peter Green  wrote:> >
/build/1st/ntopng-5.2.1+dfsg1/debian/missing-sources/gauge.coffee:179:3: error:
Can't reference 'this' before calling super in derived class constructors
> > @value = 1 * @elem.innerHTML
> > ^
> > make[1]: *** [debian/rules:24: override_dh_auto_build] Error 1

Simply adding two lines of `super()` solves this, but I'm curious if we could
get rid of the coffee script. It's there supposedly because there were only
minimized JavaScript and we need a way to reproduce them. Now upstream has the
"original" JS file present. Original in quotes because it's still generated from
a coffee script, but *its upstream* distributes the coffee script together with
generated JS.

-- 
Sdrager,
Blair Noctis


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: slurm-wlm: flaky autopkgtest: sbatch fails without

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch pending
Bug #1014506 [src:slurm-wlm] slurm-wlm: flaky autopkgtest: sbatch fails without
Added tag(s) patch and pending.

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

Bug#1014506: slurm-wlm: flaky autopkgtest: sbatch fails without

[Paul Gevers]

Control: tag -1 patch pending

Hi,

On Thu, 7 Jul 2022 11:22:44 +0200 Paul Gevers  wrote:
I looked at the results of the autopkgtest of you package on armhf 
because it was showing up as a regression for the upload of perl. I 
noticed that the test regularly fails and I saw failures on other 
architectures too.


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


I took a look how long the test needs if I let it run a bit longer, and 
on armhf it took 17 seconds in several attempts. Apparently 5 seconds is 
just a bit tight.


I am going to upload an NMU to DELAYED/10 with the changes in MR5 [1]. 
Please let me know if I should delay further or should cancel the upload.


Paul

[1] https://salsa.debian.org/hpc-team/slurm-wlm/-/merge_requests/5


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023807: seqan-needle: /usr/bin/needle is already shipped by emboss

[Andreas Beckmann]

Package: seqan-needle
Version: 1.0.1.0.0.git.3011926+ds-1
Severity: serious

There is already a (unrelated?) /usr/bin/needle binary in the Debian
archive, provided by the emboss package.


Andreas

Processed: closing 1023467, reopening 1023444

[Debian Bug Tracking System]

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

> close 1023467 1:15.0.4-1
Bug #1023467 [llvm-toolchain-15] llvm-toolchain-15: FTBFS with swig 4.1: 
interfaces.swig:5: Error: Macro '__STDC_LIMIT_MACROS' redefined
There is no source info for the package 'llvm-toolchain-15' at version 
'1:15.0.4-1' with architecture ''
Unable to make a source version for version '1:15.0.4-1'
Marked as fixed in versions 1:15.0.4-1.
Bug #1023467 [llvm-toolchain-15] llvm-toolchain-15: FTBFS with swig 4.1: 
interfaces.swig:5: Error: Macro '__STDC_LIMIT_MACROS' redefined
Marked Bug as done
> reopen 1023444
Bug #1023444 {Done: Sylvestre Ledru } 
[src:llvm-toolchain-14] llvm-toolchain-14: FTBFS with swig 4.1: 
interfaces.swig:5: Error: Macro '__STDC_LIMIT_MACROS' redefined
'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 llvm-toolchain-15/1:15.0.4-1.
> thanks
Stopping processing here.

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

Processed: Re: field3d FTBFS: OpenEXR/ImathBox.h: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> tag -1 sid bookworm
Bug #1023719 [src:field3d] field3d FTBFS: OpenEXR/ImathBox.h: No such file or 
directory
Added tag(s) sid and bookworm.

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

Bug#1023719: field3d FTBFS: OpenEXR/ImathBox.h: No such file or directory

[Andreas Beckmann]

Followup-For: Bug #1023719
Control: tag -1 sid bookworm

libilmbase-dev has been superseded by libimath-dev with a different file
layout.

Andreas

Processed: Bug#1022281 marked as pending in juce

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1022281 [juce-modules-source] iem-plugin-suite: FTBFS: ld: 
AllRADecoder_artefacts/None/libAllRADecoder_SharedCode.a(juce_core.cpp.o): 
undefined reference to symbol 'inflateEnd'
Added tag(s) pending.

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

Bug#1022281: marked as pending in juce

[IOhannes zmölnig]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/juce/-/commit/8173fa3b279203b94f382e9172a650a5109bcf7d


Patch to ensure that juce_core links against zlib

Closes: #1022281


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1022281

Processed: affects 1022281, summary 1022281 Fails to link juce_core against zlib

[Debian Bug Tracking System]

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

> affects 1022281 src:iem-plugin-suite
Bug #1022281 [juce-modules-source] iem-plugin-suite: FTBFS: ld: 
AllRADecoder_artefacts/None/libAllRADecoder_SharedCode.a(juce_core.cpp.o): 
undefined reference to symbol 'inflateEnd'
Added indication that 1022281 affects src:iem-plugin-suite
> summary 1022281 Fails to link juce_core against zlib
Summary recorded from message bug 1022281 message 
> thanks
Stopping processing here.

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

Bug#1023806: hg-git: autopkgtest needs update for new version of git: transport 'file' not allowed

[Paul Gevers]

Source: hg-git
Version: 0.10.4-3
Severity: serious
X-Debbugs-CC: g...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:git

Dear maintainer(s),

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


   passfail
gitfrom testing1:2.38.1-1
hg-git from testing0.10.4-3
all others from testingfrom testing

I copied some of the output at the bottom of this report. This is due to """
* Addresses the security issue CVE-2022-39253: cloning an
  attacker-controlled local repository could store arbitrary files
  in the ".git" directory of the destination repository.
"""

This has a nice write up:
https://vielmetti.typepad.com/logbook/2022/10/git-security-fixes-lead-to-fatal-transport-file-not-allowed-error-in-ci-systems-cve-2022-39253.html

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


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/h/hg-git/28079230/log.gz

no username found, using 'debci@ci-313-1f6a2f66' instead
cd tests && /usr/bin/python3 run-tests.py --with-hg=/usr/bin/hg 
--blacklist=/tmp/autopkgtest-lxc.dy2eo59z/downtmp/build.WMG/src/debian/hg-git.test_blacklist
/tmp/autopkgtest-lxc.dy2eo59z/downtmp/build.WMG/src/tests/run-tests.py:51: 
DeprecationWarning: The distutils package is deprecated and slated for 
removal in Python 3.12. Use setuptools or check PEP 632 for potential 
alternatives

  import distutils.version as version
running 51 tests using 51 parallel processes s
--- 
/tmp/autopkgtest-lxc.dy2eo59z/downtmp/build.WMG/src/tests/test-git-submodules.t
+++ 
/tmp/autopkgtest-lxc.dy2eo59z/downtmp/build.WMG/src/tests/test-git-submodules.t.err

@@ -32,385 +32,14 @@
  $ git submodule add ../gitsubrepo subrepo 2>&1 | python -c 
"$rmpwd" | sed "$clonefilt" | egrep -v '^done\.$'

   Initialized empty Git repository in ...
+  fatal: transport 'file' not allowed
+  fatal: clone of 'gitrepo2/../gitsubrepo' into submodule path 
'gitrepo2/subrepo' failed

  $ git commit -m 'add subrepo' | sed 's/, 0 deletions(-)//'
-  [master e42b08b] add subrepo
-   2 files changed, 4 insertions(+)
-   create mode 100644 .gitmodules
-   create mode 16 subrepo
+  On branch master
+  Your branch is up to date with 'origin/master'.
+  +  nothing to commit, working tree clean
   $ cd subrepo
+  $TESTTMP.sh: 42: cd: can't cd to subrepo
   $ echo gamma > gamma
-  $ git add gamma
-  $ fn_git_commit -m 'add gamma'
-  $ cd ..
-  $ git add subrepo
-  $ git commit -m 'change subrepo commit'
-  [master a000567] change subrepo commit
-   1 file changed, 1 insertion(+), 1 deletion(-)
-
-  $ git submodule add ../gitsubrepo subrepo2 2>&1 | python -c "$rmpwd" 
| sed "$clonefilt" | egrep -v '^done\.$'

-  Initialized empty Git repository in ...
-  -  $ git commit -m 'add another subrepo' | sed 's/, 0 deletions(-)//'
-  [master 6e21952] add another subrepo
-   2 files changed, 4 insertions(+)
-   create mode 16 subrepo2
-
-remove one subrepo, replace with file
-
-  $ git rm --cached subrepo
-  rm 'subrepo'
-we'd ordinarily use sed here, but BSD sed doesn't support two-address 
formats

-like +2 -- so use grep with the stuff we want to keep
-  $ grep 'submodule "subrepo2"' -A2 .gitmodules > .gitmodules-new
-  $ mv .gitmodules-new .gitmodules
-  $ git add .gitmodules
-  $ git config --unset submodule.subrepo.url
-  $ rm -rf subrepo
-  $ echo subrepo > subrepo
-  $ git add subrepo
-  $ git commit -m 'replace subrepo with file' | sed 's/, 0 
deletions(-)//' | sed 's/, 0 insertions(+)//'

-  [master f6436a4] replace subrepo with file
-   2 files changed, 1 insertion(+), 4 deletions(-)
-   mode change 16 => 100644 subrepo
-
-replace file with subrepo -- apparently, git complains about the 
subrepo if the
-same name has existed at any point historically, so use alpha instead 
of subrepo

-
-  $ git rm alpha
-  rm 'alpha'
-  $ git submodule add ../gitsubrepo alpha 2>&1 | python -c "$rmpwd" | 
sed "$clon

Processed: hg-git: autopkgtest needs update for new version of git: transport 'file' not allowed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:git
Bug #1023806 [src:hg-git] hg-git: autopkgtest needs update for new version of 
git: transport 'file' not allowed
Added indication that 1023806 affects src:git

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

Bug#1023805: guilt: autopkgtest needs update for new version of git: git log --decorate slightly different output

[Paul Gevers]

Source: guilt
Version: 0.36-2
Severity: serious
X-Debbugs-CC: g...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:git

Dear maintainer(s),

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


   passfail
gitfrom testing1:2.38.1-1
guilt  from testing0.36-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 git to testing 
[1]. Of course, git shouldn't just break your autopkgtest (or even 
worse, your package), but it seems to me that the change in git was 
intended and your package needs to update to the new situation.


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/g/guilt/28079229/log.gz

034: --- t-034.out  2022-11-09 20:14:59.570042679 +
+++ /tmp/guilt.log.218772022-11-09 20:15:20.238478229 +
@@ -307,133 +307,133 @@
 Applying patch..can-have-embedded-single-slashes.patch
 Patch applied.
 % git log --decorate
-commit 434e07cacdd8e7eb4723e67cb2d100b3a4121a3a (HEAD -> guilt/master, 
refs/patches/master/can-have-embedded-single-slashes.patch)

+commit 434e07cacdd8e7eb4723e67cb2d100b3a4121a3a (HEAD -> guilt/master)
 Author: Author Name 
 Date:   Mon Jan 1 00:00:00 2007 +
  Can/have/embedded/single/slashes
 -commit 7c3ffa4f940c862e9f11f5d4a5ae421f7a8d3141 
(refs/patches/master/backslash-is-forbidden.patch)

+commit 7c3ffa4f940c862e9f11f5d4a5ae421f7a8d3141
 Author: Author Name 
 Date:   Mon Jan 1 00:00:00 2007 +
  Backslash\is\forbidden.
 -commit ea46f435d4d8f3c5349dce1aabc1a39fbf7ef803 
(refs/patches/master/x.patch)

+commit ea46f435d4d8f3c5349dce1aabc1a39fbf7ef803
 Author: Author Name 
 Date:   Mon Jan 1 00:00:00 2007 +
  @
 -commit a275ed5d7f10ea88c986852ee95a7d5a61663b5f 
(refs/patches/master/cannot@have@the@sequence@at-brace.patch)

+commit a275ed5d7f10ea88c986852ee95a7d5a61663b5f
 Author: Author Name 
 Date:   Mon Jan 1 00:00:00 2007 +
  Cannot@{have@{the@{sequence@{at-brace.
 -commit f091fee39457e64ebd35410c1cf95e6613816a54 
(refs/patches/master/cannot_end_in_.patch)

+commit f091fee39457e64ebd35410c1cf95e6613816a54
 Author: Author Name 
 Date:   Mon Jan 1 00:00:00 2007 +
  Cannot end in ..
 -commit 025672497aff5c910c8ff86aaedc662f14c2f4ad 
(refs/patches/master/cannot-end-in-slash-.patch)

+commit 025672497aff5c910c8ff86aaedc662f14c2f4ad
 Author: Author Name 
 Date:   Mon Jan 1 00:00:00 2007 +
  Cannot/end/in/slash/
 -commit f13e243c7c56f39422567a431bccceec8b789596 
(refs/patches/master/multiple-slashes--are--forbidden.patch)

+commit f13e243c7c56f39422567a431bccceec8b789596
 Author: Author Name 
 Date:   Mon Jan 1 00:00:00 2007 +
  Multiple/slashes//are//forbidden.
 -commit edef5e925083d445f71c170d3293fac9619bc7a2 
(refs/patches/master/openbracketisforbidden.patch)

+commit edef5e925083d445f71c170d3293fac9619bc7a2
 Author: Author Name 
 Date:   Mon Jan 1 00:00:00 2007 +
  Open[bracket[is[forbidden.
 -commit 1626a11d979a1e9e775c766484172212277153df 
(refs/patches/master/asterisk-is-forbidden.patch)

+commit 1626a11d979a1e9e775c766484172212277153df
 Author: Author Name 
 Date:   Mon Jan 1 00:00:00 2007 +
  Asterisk*is*forbidden.
 -commit 74df14ab3a0ec9a0382998fbf167ebb1b0a36c6a 
(refs/patches/master/question-mark-is-forbidden.patch)

+commit 74df14ab3a0ec9a0382998fbf167ebb1b0a36c6a
 Author: Author Name 
 Date:   Mon Jan 1 00:00:00 2007 +
  Question-mark?is?forbidden.
 -commit ec46429125abdb0c5ac2b46cc399bdcd7cfc73fd 
(refs/patches/master/crisalsoforbidden.patch)

+commit ec46429125abdb0c5ac2b46cc399bdcd7cfc73fd
 Author: Author Name 
 Date:   Mon Jan 1 00:00:00 2007 +
  CR
is
also
forbidden.
 -commit 01524f9921af2a041cc88c068f76baa39e436cb2 
(refs/patches/master/ctrlisforbidden.patch)

+commit 01524f9921af2a041cc88c068f76baa39e436cb2
 Author: Author Name 
 Date:   Mon Jan 1 00:00:00 2007 +
  Ctrl
isforbidden.
 -commit 9fc9677b61880f9159838e89f714893e0a2fcafb 
(refs/patches/master/delisforbidden.patch)

+commit 9fc9677b61880f9159838e89f714893e0a2fcafb
 Author: Author Name 
 Date:   Mon Jan

Processed: guilt: autopkgtest needs update for new version of git: git log --decorate slightly different output

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:git
Bug #1023805 [src:guilt] guilt: autopkgtest needs update for new version of 
git: git log --decorate slightly different output
Added indication that 1023805 affects src:git

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

Bug#997587: marked as done (node-request: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2022 11:37:43 +
with message-id 
and subject line Bug#997587: fixed in node-request 2.88.1-6
has caused the Debian Bug report #997587,
regarding node-request: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/tests/pkg-js/test returned exit code 1
to be marked as done.

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

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


-- 
997587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997587
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-request
Version: 2.88.1-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package node-request
> dpkg-buildpackage: info: source version 2.88.1-5
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Pirate Praveen 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with nodejs
>dh_auto_clean --buildsystem=nodejs
>   rm -rf ./node_modules/.cache
>dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building node-request using existing 
> ./node-request_2.88.1.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building node-request in 
> node-request_2.88.1-5.debian.tar.xz
> dpkg-source: info: building node-request in node-request_2.88.1-5.dsc
>  debian/rules binary
> dh binary --with nodejs
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../debian/tests/test_modules/server-destroy 
> node_modules/server-destroy
>   ln -s ../. node_modules/request
>   /bin/sh -ex debian/tests/pkg-js/test
> + + grep -v -f debian/tests/excluded
> ls tests/test-agent.js tests/test-agentOptions.js tests/test-api.js 
> tests/test-aws.js tests/test-baseUrl.js tests/test-basic-auth.js 
> tests/test-bearer-auth.js tests/test-body.js tests/test-cookies.js 
> tests/test-defaults.js tests/test-digest-auth.js tests/test-emptyBody.js 
> tests/test-errors.js tests/test-event-forwarding.js 
> tests/test-follow-all-303.js tests/test-follow-all.js 
> tests/test-form-data-error.js tests/test-form-data.js 
> tests/test-form-urlencoded.js tests/test-form.js tests/test-gzip.js 
> tests/test-har.js tests/test-hawk.js tests/test-headers.js 
> tests/test-http-signature.js tests/test-httpModule.js tests/test-https.js 
> tests/test-isUrl.js tests/test-json-request.js tests/test-localAddress.js 
> tests/test-multipart-encoding.js tests/test-multipart.js 
> tests/test-node-debug.js tests/test-oauth.js tests/test-onelineproxy.js 
> tests/test-option-reuse.js tests/test-options-convenience-method.js 
> tests/test-params.js tests/test-piped-redirect.js tests/test-pipes.js 
> tests/test-pool.js tests/test-promise.js tests/test-proxy-connect.js 
> tests/test-proxy.js tests/test-qs.js tests/test-redirect-auth.js 
> tests/test-redirect-complex.js tests/test-redirect.js tests/test-rfc3986.js 
> tests/test-stream.js tests/test-timeout.js tests/test-timing.js 
> tests/test-toJSON.js tests/test-tunnel.js tests/test-unix.js
> + NODE_PATH=debian/tests/test_modules tape tests/test-agent.js 
> tests/test-api.js tests/test-aws.js tests/test-baseUrl.js 
> tests/test-basic-auth.js tests/test-bearer-auth.js tests/test-body.js 
> tests/test-cookies.js tests/test-defaults.js tests/test-digest-auth.js 
> tests/test-emptyBody.js tests/test-errors.js tests/test-event-forwarding.js 
> tests/test-follow-all-303.js tests/test-follow-all.js 
> tests/test-form-data-error.js tests/test-form-data.js 
> tests/test-form-urlencoded.js tests/test-form.js tests/test-gzip.js 
> tests/test-har.js tests/test-hawk.js tests/test-headers.js 
> tests/test-http-signature.js tests/test-isUrl.js tests/test-json-request.js 
> tests/test-multipart-encoding.js tests/test-multipart.js 
> tests/test-node-debug.js tests/test-oauth.js tests/test-onelineproxy.js 
> tests/test-option-reuse.js tests/test-options-convenience-method.js 
> tests/test-params.js tests/test-piped-redirect.js tests/test-pipes.js 
> tests/test-pool.js tests/test-promise.js tests/test-proxy-connect.js 
> t

Processed: reassign 1022281 to juce-modules-source

[Debian Bug Tracking System]

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

> reassign 1022281 juce-modules-source
Bug #1022281 [src:iem-plugin-suite] iem-plugin-suite: FTBFS: ld: 
AllRADecoder_artefacts/None/libAllRADecoder_SharedCode.a(juce_core.cpp.o): 
undefined reference to symbol 'inflateEnd'
Bug reassigned from package 'src:iem-plugin-suite' to 'juce-modules-source'.
No longer marked as found in versions iem-plugin-suite/1.13.0-3.
Ignoring request to alter fixed versions of bug #1022281 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1023804: git-remote-hg: autopkgtest needs update for new version of git: transport 'file' not allowed

[Paul Gevers]

Source: git-remote-hg
Version: 1.0.3.2~ds-2
Severity: serious
X-Debbugs-CC: g...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:git

Dear maintainer(s),

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


   passfail
gitfrom testing1:2.38.1-1
git-remote-hg  from testing1.0.3.2~ds-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. This is due to """
* Addresses the security issue CVE-2022-39253: cloning an
  attacker-controlled local repository could store arbitrary files
  in the ".git" directory of the destination repository.
"""

This has a nice write up:
https://vielmetti.typepad.com/logbook/2022/10/git-security-fixes-lead-to-fatal-transport-file-not-allowed-error-in-ci-systems-cve-2022-39253.html

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


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/g/git-remote-hg/28079228/log.gz

Initialized empty Git repository in 
/tmp/autopkgtest-lxc.4ir0bv3l/downtmp/build.jzc/src/test/trash 
directory.main-push/tmp/sub/.git/

[master (root-commit) be983cd] init
 Author: A U Thor 
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 empty
Initialized empty Git repository in 
/tmp/autopkgtest-lxc.4ir0bv3l/downtmp/build.jzc/src/test/trash 
directory.main-push/tmp/gitrepo/.git/
Cloning into 
'/tmp/autopkgtest-lxc.4ir0bv3l/downtmp/build.jzc/src/test/trash 
directory.main-push/tmp/gitrepo/sub'...

fatal: transport 'file' not allowed
fatal: clone of 
'/tmp/autopkgtest-lxc.4ir0bv3l/downtmp/build.jzc/src/test/trash 
directory.main-push/tmp/sub' into submodule path 
'/tmp/autopkgtest-lxc.4ir0bv3l/downtmp/build.jzc/src/test/trash 
directory.main-push/tmp/gitrepo/sub' failed

not ok 52 - push with submodule


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023803: git-evtag: autopkgtest needs update for new version of git: transport 'file' not allowed

[Paul Gevers]

Source: git-evtag
Version: 2016.1-2
Severity: serious
X-Debbugs-CC: g...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:git

Dear maintainer(s),

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


   passfail
gitfrom testing1:2.38.1-1
git-evtag  from testing2016.1-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. This is due to """
* Addresses the security issue CVE-2022-39253: cloning an
  attacker-controlled local repository could store arbitrary files
  in the ".git" directory of the destination repository.
"""

This has a nice write up:
https://vielmetti.typepad.com/logbook/2022/10/git-security-fixes-lead-to-fatal-transport-file-not-allowed-error-in-ci-systems-cve-2022-39253.html

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


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/g/git-evtag/28079227/log.gz

Running test: git-evtag/test-basic.test
+ set -o pipefail
+ echo 1..6
1..6
++ dirname /usr/libexec/git-evtag/installed-tests/test-basic.sh
+ . /usr/libexec/git-evtag/installed-tests/libtest.sh
+++ dirname /usr/libexec/git-evtag/installed-tests/test-basic.sh
++ SRCDIR=/usr/libexec/git-evtag/installed-tests
+++ pwd
++ test_tmpdir=/tmp/test-tmp-git-evtag_test-basic.test-2FD4U1
++ export G_DEBUG=fatal-warnings
++ G_DEBUG=fatal-warnings
++ export TEST_GPG_KEYID_1=472CDAFA
++ TEST_GPG_KEYID_1=472CDAFA
++ export TEST_GPG_KEYID_2=CA950D41
++ TEST_GPG_KEYID_2=CA950D41
++ export TEST_GPG_KEYID_3=DF444D67
++ TEST_GPG_KEYID_3=DF444D67
++ export 'GIT_AUTHOR_NAME=Colin Walters'
++ GIT_AUTHOR_NAME='Colin Walters'
++ export GIT_AUTHOR_EMAIL=walt...@verbum.org
++ GIT_AUTHOR_EMAIL=walt...@verbum.org
++ export 'GIT_COMMITTER_NAME=Colin Walters'
++ GIT_COMMITTER_NAME='Colin Walters'
++ export GIT_COMMITTER_EMAIL=walt...@verbum.org
++ GIT_COMMITTER_EMAIL=walt...@verbum.org
++ cp -a /usr/libexec/git-evtag/installed-tests/gpghome 
/tmp/test-tmp-git-evtag_test-basic.test-2FD4U1

++ chmod 0700 /tmp/test-tmp-git-evtag_test-basic.test-2FD4U1/gpghome
++ export GNUPGHOME=/tmp/test-tmp-git-evtag_test-basic.test-2FD4U1/gpghome
++ GNUPGHOME=/tmp/test-tmp-git-evtag_test-basic.test-2FD4U1/gpghome
++ test -n ''
+ setup_test_repository
++ pwd
+ oldpwd=/tmp/test-tmp-git-evtag_test-basic.test-2FD4U1
+ cd /tmp/test-tmp-git-evtag_test-basic.test-2FD4U1
+ mkdir coolproject
+ cd coolproject
+ git init
hint: Using 'master' as the name for the initial branch. This default 
branch name
hint: is subject to change. To configure the initial branch name to use 
in all

hint: of your new repositories, which will suppress this warning, call:
hint: hint: git config --global init.defaultBranch 
hint: hint: Names commonly chosen instead of 'master' are 'main', 
'trunk' and
hint: 'development'. The just-created branch can be renamed via this 
command:

hint: hint: git branch -m 
Initialized empty Git repository in 
/tmp/test-tmp-git-evtag_test-basic.test-2FD4U1/coolproject/.git/

+ gitcommit_reset_time
+ TSCOUNTER=1436222301
+ echo 'So cool!'
+ git add .
+ gitcommit_inctime -a -m 'Initial commit'
+ TSCOUNTER=1436222302
+ TSV='1436222302 +'
+ env 'GIT_AUTHOR_DATE=1436222302 +' 'GIT_COMMITTER_DATE=1436222302 
+' git commit -a -m 'Initial commit'

[master (root-commit) a83a4b8] Initial commit
 1 file changed, 1 insertion(+)
 create mode 100644 README.md
+ mkdir src
+ echo 'printf("hello world")'
+ git add .
+ gitcommit_inctime -a -m 'Add C source'
+ TSCOUNTER=1436222303
+ TSV='1436222303 +'
+ env 'GIT_AUTHOR_DATE=1436222303 +' 'GIT_COMMITTER_DATE=1436222303 
+' git commit -a -m 'Add C source'

[master 91df757] Add C source
 1 file changed, 1 insertion(+)
 create mode 100644 src/cool.c
+ cd /tmp/test-tmp-git-evtag_test-basic.test-2FD4U1
+ mkdir -p repos/coolproject
+ cd repos/coolproject
+ git init --bare
hint: Using 'master' as the name for the i

Processed: git-remote-hg: autopkgtest needs update for new version of git: transport 'file' not allowed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:git
Bug #1023804 [src:git-remote-hg] git-remote-hg: autopkgtest needs update for 
new version of git: transport 'file' not allowed
Added indication that 1023804 affects src:git

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

Processed: git-evtag: autopkgtest needs update for new version of git: transport 'file' not allowed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:git
Bug #1023803 [src:git-evtag] git-evtag: autopkgtest needs update for new 
version of git: transport 'file' not allowed
Added indication that 1023803 affects src:git

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

Bug#1023801: check-manifest: autopkgtest needs update for new version of git: transport 'file' not allowed

[Paul Gevers]

Source: check-manifest
Version: 0.46-2
Severity: serious
X-Debbugs-CC: g...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:git

Dear maintainer(s),

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


   passfail
gitfrom testing1:2.38.1-1
check-manifest from testing0.46-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. This is due to """
* Addresses the security issue CVE-2022-39253: cloning an
  attacker-controlled local repository could store arbitrary files
  in the ".git" directory of the destination repository.
"""

This has a nice write up:
https://vielmetti.typepad.com/logbook/2022/10/git-security-fixes-lead-to-fatal-transport-file-not-allowed-error-in-ci-systems-cve-2022-39253.html

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


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/c/check-manifest/28079226/log.gz

=== FAILURES 
===
_ TestGit.test_get_versioned_files_with_git_submodules 
_


self = testMethod=test_get_versioned_files_with_git_submodules>


def test_get_versioned_files_with_git_submodules(self):
from check_manifest import get_vcs_files
self._init_repo_with_files('repo1', ['file1', 'file2'])
self._init_repo_with_files('repo2', ['file3'])
self._init_repo_with_files('repo3', ['file4'])

  self._add_submodule('repo2', 'sub3', '../repo3')


tests.py:1094: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ tests.py:1074: in _add_submodule

self.vcs._run('git', 'submodule', 'add', subrepo, subdir)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

self = 
command = ('git', 'submodule', 'add', '../repo3', 'sub3')
p = '../repo3', 'sub3')>
stdout = b"Cloning into 
'/tmp/test-62xpxof5-check-manifest/repo2/sub3'...\nfatal: transport 
'file' not allowed\nfatal: clone of 
'/tmp/test-62xpxof5-check-manifest/repo3' into submodule path 
'/tmp/test-62xpxof5-check-manifest/repo2/sub3' failed\n"

stderr = None

def _run(self, *command):
# Windows doesn't like Unicode arguments to subprocess.Popen(), 
on Py2:
# 
https://github.com/mgedmin/check-manifest/issues/23#issuecomment-33933031

if str is bytes:
command = [s.encode(locale.getpreferredencoding()) for s in 
command]

print('$', ' '.join(command))
p = subprocess.Popen(command, stdout=subprocess.PIPE,
 stderr=subprocess.STDOUT)
stdout, stderr = p.communicate()
rc = p.wait()
if stdout:
print(
stdout if isinstance(stdout, str) else
stdout.decode('ascii', 'backslashreplace')
)
if rc:

  raise subprocess.CalledProcessError(rc, command[0], output=stdout)
E   subprocess.CalledProcessError: Command 'git' returned 
non-zero exit status 128.


tests.py:949: CalledProcessError
- Captured stdout call 
-

$ git init
hint: Using 'master' as the name for the initial branch. This default 
branch name
hint: is subject to change. To configure the initial branch name to use 
in all

hint: of your new repositories, which will suppress this warning, call:
hint: hint: git config --global init.defaultBranch 
hint: hint: Names commonly chosen instead of 'master' are 'main', 
'trunk' and
hint: 'development'. The just-created branch can be renamed via this 
command:

hint: hint: git branch -m 
Initialized empty Git repository in 
/tmp/test-62xpxof5-check-manifest/repo1/.git/


$ git config user.name Unit Test
$ git config user.email t...@example.com
$ git add --force -- file1 file2
$ git commit -m Initial
[master (root-commit) bbd8b65] Initial
 2 files changed,

Processed: check-manifest: autopkgtest needs update for new version of git: transport 'file' not allowed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:git
Bug #1023801 [src:check-manifest] check-manifest: autopkgtest needs update for 
new version of git: transport 'file' not allowed
Added indication that 1023801 affects src:git

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

Bug#1023800: fdroidserver: autopkgtest needs update for new version of git: transport 'file' not allowed

[Paul Gevers]

Source: fdroidserver
Version: 2.1.1-2
Severity: serious
X-Debbugs-CC: g...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:git

Dear maintainer(s),

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


   passfail
gitfrom testing1:2.38.1-1
fdroidserver   from testing2.1.1-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. This is due to """
* Addresses the security issue CVE-2022-39253: cloning an
  attacker-controlled local repository could store arbitrary files
  in the ".git" directory of the destination repository.
"""

This has a nice write up:
https://vielmetti.typepad.com/logbook/2022/10/git-security-fixes-lead-to-fatal-transport-file-not-allowed-error-in-ci-systems-cve-2022-39253.html

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


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


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

Paul

[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 
git/1:2.38.1-1. I.e. due to versioned dependencies or breaks/conflicts.

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

https://ci.debian.net/data/autopkgtest/testing/amd64/f/fdroidserver/28075853/log.gz

==
Test recovering from from broken git submodules
++ create_test_dir
++ test -e /tmp/autopkgtest-lxc.7wnh4imd/downtmp/build.qNQ/src/.testfiles
++ mktemp -d 
/tmp/autopkgtest-lxc.7wnh4imd/downtmp/build.qNQ/src/.testfiles/run-tests.
+ 
ROOT=/tmp/autopkgtest-lxc.7wnh4imd/downtmp/build.qNQ/src/.testfiles/run-tests.FZCB
+ cd 
/tmp/autopkgtest-lxc.7wnh4imd/downtmp/build.qNQ/src/.testfiles/run-tests.FZCB

+ mkdir foo bar
+ cd foo
+ env HOME= 'GIT_AUTHOR_NAME='\''Test'\''' 
'GIT_AUTHOR_EMAIL='\''no@mail'\''' 'GIT_COMMITTER_NAME='\''Test'\''' 
'GIT_COMMITTER_EMAIL='\''no@mail'\''' git init
hint: Using 'master' as the name for the initial branch. This default 
branch name
hint: is subject to change. To configure the initial branch name to use 
in all

hint: of your new repositories, which will suppress this warning, call:
hint: hint: git config --global init.defaultBranch 
hint: hint: Names commonly chosen instead of 'master' are 'main', 
'trunk' and
hint: 'development'. The just-created branch can be renamed via this 
command:

hint: hint: git branch -m 
Initialized empty Git repository in 
/tmp/autopkgtest-lxc.7wnh4imd/downtmp/build.qNQ/src/.testfiles/run-tests.FZCB/foo/.git/

+ echo a
+ env HOME= 'GIT_AUTHOR_NAME='\''Test'\''' 
'GIT_AUTHOR_EMAIL='\''no@mail'\''' 'GIT_COMMITTER_NAME='\''Test'\''' 
'GIT_COMMITTER_EMAIL='\''no@mail'\''' git add a
+ env HOME= 'GIT_AUTHOR_NAME='\''Test'\''' 
'GIT_AUTHOR_EMAIL='\''no@mail'\''' 'GIT_COMMITTER_NAME='\''Test'\''' 
'GIT_COMMITTER_EMAIL='\''no@mail'\''' git commit -m a

[master (root-commit) a0c70da] a
 1 file changed, 1 insertion(+)
 create mode 100644 a
+ cd ../bar
+ env HOME= 'GIT_AUTHOR_NAME='\''Test'\''' 
'GIT_AUTHOR_EMAIL='\''no@mail'\''' 'GIT_COMMITTER_NAME='\''Test'\''' 
'GIT_COMMITTER_EMAIL='\''no@mail'\''' git init
hint: Using 'master' as the name for the initial branch. This default 
branch name
hint: is subject to change. To configure the initial branch name to use 
in all

hint: of your new repositories, which will suppress this warning, call:
hint: hint: git config --global init.defaultBranch 
hint: hint: Names commonly chosen instead of 'master' are 'main', 
'trunk' and
hint: 'development'. The just-created branch can be renamed via this 
command:

hint: hint: git branch -m 
Initialized empty Git repository in 
/tmp/autopkgtest-lxc.7wnh4imd/downtmp/build.qNQ/src/.testfiles/run-tests.FZCB/bar/.git/

++ pwd
+ env HOME= 'GIT_AUTHOR_NAME='\''Test'\''' 
'GIT_AUTHOR_EMAIL='\''no@mail'\''' 'GIT_COMMITTER_NAME='\''Test'\''' 
'GIT_COMMITTER_EMAIL='\''no@mail'\''' git submodule add 
file:///tmp/autopkgtest

Processed: fdroidserver: autopkgtest needs update for new version of git: transport 'file' not allowed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:git
Bug #1023800 [src:fdroidserver] fdroidserver: autopkgtest needs update for new 
version of git: transport 'file' not allowed
Added indication that 1023800 affects src:git

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

Processed: Bug#997587 marked as pending in node-request

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997587 [src:node-request] node-request: FTBFS: dh_auto_test: error: 
/bin/sh -ex debian/tests/pkg-js/test returned exit code 1
Added tag(s) pending.

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

Bug#997587: marked as pending in node-request

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-request/-/commit/2cdfc03f79bffd4573e5d2b63ed9e82a2470f968


Fix test for recent tape & deep-equal

Closes: #997587


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997587

Bug#1023797: lintian-brush: autopkgtest regression: No module named 'upstream_ontologist.tests' (and more)

[Paul Gevers]

Source: lintian-brush
Version: 0.134
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
lintian-brush  from testing0.134
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 
lintian-brush/0.134. I.e. due to versioned dependencies or breaks/conflicts.

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

https://ci.debian.net/data/autopkgtest/testing/amd64/l/lintian-brush/28079251/log.gz

failed to open trace file: [Errno 13] Permission denied: 
'/you-should-use-TestCaseInTempDir-if-you-need-a-log-file'
...Unexpected line while looking for first heading: THIS IS NOT A 
PARSEABLE LINE
...F..xINFO:brz:Committing 
to: 
/tmp/testbzr-8ohdek32.tmp/lintian_brush.tests.test_run.RunLintianFixerTests.test_upstream_change_stacked/work/

INFO:brz:added debian
INFO:brz:added debian/changelog
INFO:brz:added debian/control
INFO:brz:Committed revision 1.
INFO:brz:Committing to: 
/tmp/testbzr-8ohdek32.tmp/lintian_brush.tests.test_run.RunLintianFixerTests.test_upstream_change_stacked/work/

INFO:brz:added debian/patches
INFO:brz:added debian/patches/foo
INFO:brz:added debian/patches/series
INFO:brz:Committed revision 2.
.INFO:brz:Committing to: 
/tmp/testbzr-8ohdek32.tmp/lintian_brush.tests.test_run.RunLintianFixersTests.test_fails/work/

INFO:brz:added debian
INFO:brz:added debian/changelog
INFO:brz:added debian/control
INFO:brz:Committed revision 1.
/usr/lib/python3/dist-packages/pyinotify.py:71: DeprecationWarning: The 
asyncore module is deprecated and will be removed in Python 3.12. The 
recommended replacement is asyncio

  import asyncore
.INFO:brz:Committing to: 
/tmp/testbzr-8ohdek32.tmp/lintian_brush.tests.test_run.RunLintianFixersTests.test_not_debian_tree/work/

INFO:brz:added debian
INFO:brz:added debian/changelog
INFO:brz:added debian/control
INFO:brz:Committed revision 1.
INFO:brz:removed debian/changelog
INFO:brz:Committing to: 
/tmp/testbzr-8ohdek32.tmp/lintian_brush.tests.test_run.RunLintianFixersTests.test_not_debian_tree/work/

INFO:brz:deleted debian/changelog
INFO:brz:Committed revision 2.
.INFO:brz:Committing to: 
/tmp/testbzr-8ohdek32.tmp/lintian_brush.tests.test_run.RunLintianFixersTests.test_simple_modify/work/

INFO:brz:added debian
INFO:brz:added debian/changelog
INFO:brz:added debian/control
INFO:brz:Committed revision 1.
...F...F.F..EETraceback 
(most recent call last):
  File 
"/tmp/autopkgtest-lxc.7zevms7k/downtmp/build.go5/src/fixers/old-override-info-format.py", 
line 37, in 

update_overrides(fix_info)
  File 
"/tmp/autopkgtest-lxc.7zevms7k/downtmp/build.go5/src/lintian_brush/lintian_overrides.py", 
line 55, in update_overrides

update_overrides_file(
  File 
"/tmp/autopkgtest-lxc.7zevms7k/downtmp/build.go5/src/lintian_brush/lintian_overrides.py", 
line 77, in update_overrides_file

entry = cb(lineno, entry)
  File 
"/tmp/autopkgtest-lxc.7zevms7k/downtmp/build.go5/src/lintian_brush/lintian_overrides.py", 
line 56, in 

lambda lineno, override: cb(path, lineno, override),
  File 
"/tmp/autopkgtest-lxc.7zevms7k/downtmp/build.go5/src/fixers/old-override-info-format.py", 
line 22, in fix_info

info = fix_override_info(override)
  File 
"/tmp/autopkgtest-lxc.7zevms7k/downtmp/build.go5/src/lintian_brush/lintian_overrides.py", 
line 343, in fix_override_info

info = re.sub(fixer[0], fixer[1], override.info)
NameError: name 're' is not defined
FTraceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.7zevms7k/downtmp/build.go5/src/fixers/old-override-info-format.py", 
line 37, in 

update_overrides(fix_info)
  File 
"/tmp/autopkgtest-lxc.7zevms7k/downtmp/build.go5/src/lintian_brush/lintian_overrides.py", 
line 55, in update_overrides

update_overrides_file(
  File 
"/tmp/autopkgtest-lxc.7zevms7k/downtmp/build.go5/src/lintian_brush/lintian_overrides.py", 
line 77, in update_overrides_file

entry = cb(lineno, entry)
  File 
"/tmp/autopkgtest-lxc.7zevms7k

Bug#1019610: ruby-ahoy-email: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp (LoadError)

[s3v]

On Sun, 6 Nov 2022 20:31:39 +0200 Adrian Bunk  wrote:
> Is there a bug in rails?

https://github.com/rails/rails/pull/44083
seems relevant.

Kind Regards

Bug#1023597: FTBFS: t/21-submodule.t: fatal: transport 'file' not allowed

[Paul Gevers]

Hi,

On Mon, 07 Nov 2022 12:31:05 +0100 gregor herrmann 
wrote:

libgit-repository-perl's test suite started to fail recently:

Cloning into '/tmp/M19xNBDPV8/sub'...
fatal: transport 'file' not allowed
fatal: clone of '/tmp/tC7mgf7E52' into submodule path '/tmp/M19xNBDPV8/sub' 
failed at t/21-submodule.t line 46.
# Looks like your test exited with 128 before it could output anything.
t/21-submodule.t ...
1..1
Dubious, test returned 128 (wstat 32768, 0x8000)
Failed 1/1 subtests


AUR is "fixing" this with "protocol.file.allow=always":
https://wiki.archlinux.org/title/VCS_package_guidelines#Git_submodules

This has a nice write up: 
https://vielmetti.typepad.com/logbook/2022/10/git-security-fixes-lead-to-fatal-transport-file-not-allowed-error-in-ci-systems-cve-2022-39253.html


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1017711: bug#58956: mark_object, mark_objects(?) crash

[Vincent Lefevre]

On 2022-11-08 12:44:08 -0700, Sean Whitton wrote:
> Are you able to test the patch?  Let me know if you need help getting an
> installable .deb.  Thanks.

Sorry, I couldn't test it yet, first because of an uninstallable
package needed for the build because I couldn't upgrade libc6 yet
and I couldn't get the previous version from snapshot.debian.org
(bug 1023540). Now that I could upgrade libc6, I'll be able to
test when I have some time, but perhaps not before the week-end.

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

Bug#1017711: bug#58956: mark_object, mark_objects(?) crash

[Eli Zaretskii]

> Date: Sat, 5 Nov 2022 13:54:54 -0700
> Cc: vinc...@vinc17.net, spwhit...@spwhitton.name, 58...@debbugs.gnu.org,
>  1017...@bugs.debian.org
> From: Paul Eggert 
> 
> On 2022-11-04 00:00, Eli Zaretskii wrote:
> > We need to establish what is the
> > source of SIGHUP in these cases.  "These cases" mean, AFAIU, the
> > situations where Emacs launched an async subprocess to do native
> > compilation (which is another Emacs process in a --batch session), and
> > the parent Emacs session is terminated by the user before the async
> > compilation runs to completion.  Would the child Emacs process get
> > SIGHUP in this scenario?
> 
> Hard for me to say. It's a messy area, with kernels (and Emacs itself) 
> sending SIGHUP on various whims.
> 
> Does the attached patch fix things? It builds on your commit 
> 190a6853708ab22072437f6ebd93beb3ec1a9ce6 dated 2020-12-04; I don't know 
> why that earlier patch was installed, but it would seem to apply to 
> SIGHUP and SIGTERM as well as it applies to SIGINT.

No further comments, so I've now installed this on the master branch,
and I'm marking this bug done.

Thanks.

Processed: Re: Bug#1023650: vlc: Trying to view video files via Vlc 3.0.18~rc2-1+b1 tightly hangs Debian

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1023650 [vlc] vlc: Trying to view video files via Vlc 3.0.18~rc2-1+b1 
tightly hangs Debian
Severity set to 'normal' from 'critical'

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

Bug#1023650: vlc: Trying to view video files via Vlc 3.0.18~rc2-1+b1 tightly hangs Debian

[Sebastian Ramacher]

Control: severity -1 normal

On 2022-11-08 14:52:21 +0100, Sebastian Ramacher wrote:
> Control: tags -1 moreinfo
> 
> On 2022-11-08 12:09:28 +0300, Сергей Фёдоров wrote:
> > Package: vlc
> > Version: 3.0.18~rc2-1+b1
> > Severity: critical
> > Justification: breaks the whole system
> > X-Debbugs-Cc: serfyod...@yandex.ru
> > 
> > Dear Maintainer,
> > 
> > Trying to view video files via Vlc 3.0.18~rc2-1+b1 tightly hangs Debian
> 
> Please provide a verbose log of vlc when this issue happens.

Downgrading until this info is provided.

Cheers
-- 
Sebastian Ramacher

Bug#1012093: ciftools-java: FTBFS with OpenJDK 17 due to test failures

[Andrius Merkys]

Hi Pierre,

On 2022-11-10 11:04, Pierre Gruet wrote:
But whoops, sorry, this morning I tried to upload 4.0.3-2 with a manual 
fix as I hadn't seen upstream released 4.0.4 fixing the issue. I 
launched a dcut cancel command, we will see if it worked...

Else my upload will get accepted and I will update the VCS!


Wow, what a coincidence :) Anyway, I think this should not be a problem. 
I have fetched your commits, merged and resolved the conflicts to 
reflect the state after my upload of 4.0.4-1.


Sorry for the mess.

Best,
Andrius

Bug#1012093: ciftools-java: FTBFS with OpenJDK 17 due to test failures

[Pierre Gruet]

In the end, two simultaneous uploads... yours will override mine, perfect!

There only remains to merge your changes with mine in the VCS...

Cheers,

--
Pierre


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1012093: ciftools-java: FTBFS with OpenJDK 17 due to test failures

[Pierre Gruet]

Hi again,

Le 10/11/2022 à 10:04, Pierre Gruet a écrit :

Hi Andrius,

Le 10/11/2022 à 09:18, Andrius Merkys a écrit :

Control: owner -1 !
Control: tags -1 + pending fixed-upstream

Hi Pierre,

On 2022-11-10 00:05, Pierre Gruet wrote:

I investigated the test failure a bit and saw tiny differences between a
generated gzip file and a reference one. This reminded me of one 
similar and

innocuous issue [0] so that I filled an issue upstream [1]. Let's see.


Thanks a lot for investigating and contacting the upstream! The new 
release builds and passes its tests successfully. I will upload it in 
short.


You're welcome!

But whoops, sorry, this morning I tried to upload 4.0.3-2 with a manual 
fix as I hadn't seen upstream released 4.0.4 fixing the issue. I 
launched a dcut cancel command, we will see if it worked...

Else my upload will get accepted and I will update the VCS!



Sorry, my upload reached unstable. I updated the VCS accordingly. You 
should still make your upload but it won't close the bug...



Thanks,

--
Pierre


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1012093: ciftools-java: FTBFS with OpenJDK 17 due to test failures

[Pierre Gruet]

Hi Andrius,

Le 10/11/2022 à 09:18, Andrius Merkys a écrit :

Control: owner -1 !
Control: tags -1 + pending fixed-upstream

Hi Pierre,

On 2022-11-10 00:05, Pierre Gruet wrote:

I investigated the test failure a bit and saw tiny differences between a
generated gzip file and a reference one. This reminded me of one 
similar and

innocuous issue [0] so that I filled an issue upstream [1]. Let's see.


Thanks a lot for investigating and contacting the upstream! The new 
release builds and passes its tests successfully. I will upload it in 
short.


You're welcome!

But whoops, sorry, this morning I tried to upload 4.0.3-2 with a manual 
fix as I hadn't seen upstream released 4.0.4 fixing the issue. I 
launched a dcut cancel command, we will see if it worked...

Else my upload will get accepted and I will update the VCS!



Best,
Andrius


Best,

--
Pierre


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#1012093: ciftools-java: FTBFS with OpenJDK 17 due to test failures

[Debian Bug Tracking System]

Processing control commands:

> owner -1 !
Bug #1012093 [src:ciftools-java] ciftools-java: FTBFS with OpenJDK 17 due to 
test failures
Owner recorded as Andrius Merkys .
> tags -1 + pending fixed-upstream
Bug #1012093 [src:ciftools-java] ciftools-java: FTBFS with OpenJDK 17 due to 
test failures
Added tag(s) fixed-upstream.

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

Bug#1012093: ciftools-java: FTBFS with OpenJDK 17 due to test failures

[Andrius Merkys]

Control: owner -1 !
Control: tags -1 + pending fixed-upstream

Hi Pierre,

On 2022-11-10 00:05, Pierre Gruet wrote:

I investigated the test failure a bit and saw tiny differences between a
generated gzip file and a reference one. This reminded me of one similar and
innocuous issue [0] so that I filled an issue upstream [1]. Let's see.


Thanks a lot for investigating and contacting the upstream! The new 
release builds and passes its tests successfully. I will upload it in short.


Best,
Andrius

Bug#1023789: thunderbird: FTBFS: error: no matching function for call to 'arc4random_buf'

[Sebastian Ramacher]

Source: thunderbird
Version: 1:102.4.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=thunderbird&arch=amd64&ver=1%3A102.4.1-1%2Bb1&stamp=1668054836&raw=0

/usr/bin/clang++ -std=gnu++17 -o exploitability_win.o -c  
-I/<>/obj-thunderbird/dist/system_wrappers -include 
/<>/config/gcc_hidden.h -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 
-fstack-protector-strong -fstack-clash-protection -DNDEBUG=1 -DTRIMMED=1 
-DBPLOG_MINIMUM_SEVERITY=SEVERITY_CRITICAL -DNO_STABS_SUPPORT 
-I/<>/toolkit/crashreporter/google-breakpad/src/processor 
-I/<>/obj-thunderbird/toolkit/crashreporter/google-breakpad/src/processor
 -I/<>/toolkit/crashreporter/breakpad-client 
-I/<>/toolkit/crashreporter/google-breakpad/src 
-I/<>/obj-thunderbird/dist/include -I/usr/include/nspr 
-I/usr/include/nss -I/usr/include/nspr 
-I/<>/obj-thunderbird/dist/include/nss -DMOZILLA_CLIENT -include 
/<>/obj-thunderbird/mozilla-config.h -Qunused-arguments 
-Wdate-time -D_FORTIFY_SOURCE=2 -Qunused-arguments -Wall 
-Wbitfield-enum-conversion -Wdeprecated-this-capture -Wempty-body 
-Wformat-type-confusion -Wignored-qualifiers -Wpointer-arith 
-Wshadow-field-in-constructor-modified -Wsign-compare -Wtype-limits 
-Wno-error=tautological-type-limit-compare -Wunreachable-code 
-Wunreachable-code-return -Wunused-but-set-parameter -Wno-invalid-offsetof 
-Wclass-varargs -Wempty-init-stmt -Wfloat-overflow-conversion 
-Wfloat-zero-conversion -Wloop-analysis -Wno-range-loop-analysis -Wc++2a-compat 
-Wcomma -Wenum-compare-conditional -Wimplicit-fallthrough -Wstring-conversion 
-Wno-inline-new-delete -Wno-error=deprecated-declarations 
-Wno-error=array-bounds -Wno-error=backend-plugin 
-Wno-error=free-nonheap-object -Wno-error=return-std-move 
-Wno-error=atomic-alignment -Wno-error=deprecated-copy -Wformat 
-Wformat-security -Wno-gnu-zero-variadic-macro-arguments -Wno-psabi 
-Wthread-safety -Wno-unknown-warning-option -fno-sized-deallocation 
-fno-aligned-new -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fno-exceptions -fPIC 
-fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -fno-math-errno 
-pthread -pipe -gdwarf-4 -O2 -fomit-frame-pointer -funwind-tables 
-Wno-unused-local-typedefs -Wno-deprecated-declarations -Wno-bool-compare 
-Wno-unused-but-set-variable -Wno-c++11-narrowing -Wno-implicit-fallthrough 
-fno-strict-aliasing -ffp-contract=off  -MD -MP -MF 
.deps/exploitability_win.o.pp   
/<>/toolkit/crashreporter/google-breakpad/src/processor/exploitability_win.cc
toolkit/crashreporter/google-breakpad/src/processor/Unified_cpp_src_processor0.o
In file included from Unified_cpp_client0.cpp:47:
/<>/toolkit/crashreporter/client/ping.cpp:56:3: error: no matching 
function for call to 'arc4random_buf'
  arc4random_buf(id, sizeof(UUID));
  ^~
/usr/include/stdlib.h:542:13: note: candidate function not viable: no known 
conversion from 'CrashReporter::UUID' to 'void *' for 1st argument; take the 
address of the argument with &
extern void arc4random_buf (void *__buf, size_t __size)
^
1 error generated.
make[5]: *** [/<>/config/rules.mk:669: Unified_cpp_client0.o] 
Error 1
make[5]: Leaving directory 
'/<>/obj-thunderbird/toolkit/crashreporter/client'
make[4]: *** [/<>/config/recurse.mk:72: 
toolkit/crashreporter/client/target-objects] Error 2
make[4]: *** Waiting for unfinished jobs

Cheers
-- 
Sebastian Ramacher

Bug#1023788: getfem: fails to build from source on s390x

[Paul Gevers]

Source: getfem
Version: 5.4.2+dfsg1-1
Severity: serious
Tags: ftbfs

Dear maintainer,

Version 5.4.1+dfsg1-1 built successfully on s390x, but 5.4.2+dfsg1-1
fails to build from source there. This is blocking migration.

Can you look into the situation and solve it?

Paul