Bug#1065787: 64-bit time_t transition: cargo needs manual intervention

[Emanuele Rocca]

On 2024-03-16 04:21, Emanuele Rocca wrote:
> With libcurl3t64-gnutls cargo can now be rebootstrapped on armhf

And on armel too. Fixed armhf/armel packages uploaded.

> Fabian: it seems that cargo's build-depend on git can be dropped? The
> package builds fine without, tests included.

I haven't touched build-depends and git is still currently
uninstallable. For this reason cargo would not cleanly build from source
on armhf/armel in case of sourceful upload, but as I said without git it
does build fine. Leaving this one up to Fabian!

Bug#1065435: [Aptitude-devel] Bug#1065435: aptitude: FTBFS on armhf and armel (probably -Werror=implicit-function-declaration related)

[Axel Beckert]

Hi Steinar and Christoph,

Steinar H. Gunderson wrote:
> struct timeval
> {
> #ifdef __USE_TIME_BITS64
>   __time64_t tv_sec;/* Seconds.  */
>   __suseconds64_t tv_usec;  /* Microseconds.  */
> #else 
>   __time_t tv_sec;  /* Seconds.  */
>   __suseconds_t tv_usec;/* Microseconds.  */
> #endif
> };
> #endif
> 
> But the fix is straightforward, no? Just change the offending test to 
> something like
> 
>   CPPUNIT_ASSERT_EQUAL(static_cast(99), c.tv_usec);
> 
> and it should work no matter what type c.tv_usec is. Or, if you prefer
> brace-initialization (which would prevent you from ever writing in a too-big
> value, like 999 or something):
> 
>   CPPUNIT_ASSERT_EQUAL(decltype(c.tv_usec){99}, c.tv_usec);
> 
> /* Steinar */

Thanks for the patch!

Christoph Biedl wrote:
> Therefore, any progress on this?

Not before the patch (hints) from Steinar. (Although there's also a
recent merge request mentioning some FTBFS fix, but it's unclear if
this issue is meant or something else. Will have to look into it,
too.)

> Do you need help?

I'm happy about any help with aptitude as we currently don't really
have any active upstream developer. C++ is not something that I'm
particularly good at.

> I didn't get very far at a first glance, aptitude's build
> dependencies are currently uninstallable, at least in arm{el,hf}.

I got my sid armhf Raspi fixed today (it stopped booting a while ago,
seemed to have been a usrmerge related issue), so I can now test
patches locally on armhf again.

Will try to get an upload done based on Steinar's patch instructions
soon-ish. But I first need to get the Raspi uptodate with the current
state of Sid.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#1064612: rust-ahash: Failing autopkgtests

[plugwash]

tags 1064612 +patch
thanks


rust-ahash is unable to migrate to Testing because its autopkgtests are failing:

A debdiff fixing this issue is attatched.

diff -Nru rust-ahash-0.8.9/debian/changelog rust-ahash-0.8.9/debian/changelog
--- rust-ahash-0.8.9/debian/changelog   2024-02-23 07:28:35.0 +
+++ rust-ahash-0.8.9/debian/changelog   2024-03-16 17:46:03.0 +
@@ -1,3 +1,10 @@
+rust-ahash (0.8.9-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix feature gaurds for test_key_ref (Closes: #1064612)
+
+ -- Peter Michael Green   Sat, 16 Mar 2024 17:46:03 +
+
 rust-ahash (0.8.9-2) unstable; urgency=medium
 
   * drop patch 2001, obsoleted by Debian package changes;
diff -Nru rust-ahash-0.8.9/debian/patches/1002_test_feature_requirements.patch 
rust-ahash-0.8.9/debian/patches/1002_test_feature_requirements.patch
--- rust-ahash-0.8.9/debian/patches/1002_test_feature_requirements.patch
2024-02-18 09:46:30.0 +
+++ rust-ahash-0.8.9/debian/patches/1002_test_feature_requirements.patch
2024-03-16 17:46:03.0 +
@@ -1,12 +1,15 @@
 Description: fix feature requirements for tests
 Author: Peter Michael Green 
 Bug-Debian: https://bugs.debian.org/1057451
-Last-Update: 2023-12-27
+Bug-Debian: https://bugs.debian.org/1064612
+Last-Update: 2024-03-16
 ---
 This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
 a/src/lib.rs
-+++ b/src/lib.rs
-@@ -322,12 +322,14 @@
+Index: rust-ahash-0.8.9/src/lib.rs
+===
+--- rust-ahash-0.8.9.orig/src/lib.rs
 rust-ahash-0.8.9/src/lib.rs
+@@ -322,12 +322,14 @@ mod test {
  use std::hash::Hash;
  
  #[test]
@@ -21,7 +24,7 @@
  fn test_ahash_alias_set_construction() {
  let mut set = super::HashSet::with_capacity(1234);
  set.insert(1);
-@@ -342,6 +344,7 @@
+@@ -342,6 +344,7 @@ mod test {
  }
  
  #[test]
@@ -29,9 +32,11 @@
  fn test_builder() {
  let mut map = HashMapdefault();
  map.insert(1, 3);
 a/tests/bench.rs
-+++ b/tests/bench.rs
-@@ -116,6 +116,7 @@
+Index: rust-ahash-0.8.9/tests/bench.rs
+===
+--- rust-ahash-0.8.9.orig/tests/bench.rs
 rust-ahash-0.8.9/tests/bench.rs
+@@ -116,6 +116,7 @@ fn bench_map(c:  Criterion) {
  #[cfg(feature = "std")]
  {
  let mut group = c.benchmark_group("map");
@@ -39,7 +44,7 @@
  group.bench_function("aHash-alias", |b| {
  b.iter(|| {
  let hm: ahash::HashMap = (0..1_000_000).map(|i| (i, 
i)).collect();
-@@ -138,6 +139,7 @@
+@@ -138,6 +139,7 @@ fn bench_map(c:  Criterion) {
  }
  })
  });
@@ -47,7 +52,7 @@
  group.bench_function("aHash-hashBrown-explicit", |b| {
  b.iter(|| {
  let hm: hashbrown::HashMap = 
(0..1_000_000).map(|i| (i, i)).collect();
-@@ -160,6 +162,7 @@
+@@ -160,6 +162,7 @@ fn bench_map(c:  Criterion) {
  }
  })
  });
@@ -55,9 +60,11 @@
  group.bench_function("aHash-rand", |b| {
  b.iter(|| {
  let hm: std::collections::HashMap = 
(0..1_000_000).map(|i| (i, i)).collect();
 a/tests/map_tests.rs
-+++ b/tests/map_tests.rs
-@@ -179,7 +179,7 @@
+Index: rust-ahash-0.8.9/tests/map_tests.rs
+===
+--- rust-ahash-0.8.9.orig/tests/map_tests.rs
 rust-ahash-0.8.9/tests/map_tests.rs
+@@ -179,7 +179,7 @@ fn test_bucket_distribution() {
  check_for_collisions(_hasher, , 256);
  }
  
@@ -66,7 +73,7 @@
  #[test]
  fn test_ahash_alias_map_construction() {
  let mut map = ahash::HashMap::default();
-@@ -189,7 +189,7 @@
+@@ -189,7 +189,7 @@ fn test_ahash_alias_map_construction() {
  map.insert(1, "test");
  }
  
@@ -75,3 +82,12 @@
  #[test]
  fn test_ahash_alias_set_construction() {
  let mut set = ahash::HashSet::default();
+@@ -201,7 +201,7 @@ fn test_ahash_alias_set_construction() {
+ }
+ 
+ 
+-#[cfg(feature = "std")]
++#[cfg(all(feature = "std", any(feature = "runtime-rng", feature = 
"compile-time-rng", feature = "no-rng")))]
+ #[test]
+ fn test_key_ref() {
+ let mut map = ahash::HashMap::default();

Bug#1064158: jxrlib: NMU diff for 64-bit time_t transition

[Steve Langasek]

Hello,

Unfortunately, the mass NMU scripting missed that debian/symbols needed
updated as well, resulting in a libjxr0t64 package that depends on libjxr0
which doesn't exist on 32-bit archs.

Attached is a comprehensive NMU patch that fixes this issue as well.  I am
uploading this change to unstable.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org

On Sat, Feb 17, 2024 at 08:36:44PM +, Steve Langasek wrote:
> Source: jxrlib
> Version: 1.2~git20170615.f752187-5
> Severity: important
> Tags: patch pending sid trixie
> User: debian-...@lists.debian.org
> Usertags: time-t
> 
> NOTICE: these changes must not be uploaded to unstable yet!
> 
> Dear maintainer,
> 
> As part of the 64-bit time_t transition required to support 32-bit
> architectures in 2038 and beyond
> (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
> jxrlib as a source package shipping runtime libraries whose ABI
> either is affected by the change in size of time_t, or could not be
> analyzed via abi-compliance-checker (and therefore to be on the safe
> side we assume is affected).
> 
> To ensure that inconsistent combinations of libraries with their
> reverse-dependencies are never installed together, it is necessary to
> have a library transition, which is most easily done by renaming the
> runtime library package.
> 
> Since turning on 64-bit time_t is being handled centrally through a change
> to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
> important that libraries affected by this ABI change all be uploaded close
> together in time.  Therefore I have prepared a 0-day NMU for jxrlib
> which will initially be uploaded to experimental if possible, then to
> unstable after packages have cleared binary NEW.
> 
> Please find the patch for this NMU attached.
> 
> If you have any concerns about this patch, please reach out ASAP.  Although
> this package will be uploaded to experimental immediately, there will be a
> period of several days before we begin uploads to unstable; so if information
> becomes available that your package should not be included in the transition,
> there is time for us to amend the planned uploads.
> 
> 
> 
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
> 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
> Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)

> diff -Nru jxrlib-1.2~git20170615.f752187/debian/changelog 
> jxrlib-1.2~git20170615.f752187/debian/changelog
> --- jxrlib-1.2~git20170615.f752187/debian/changelog   2022-01-28 
> 12:55:06.0 +
> +++ jxrlib-1.2~git20170615.f752187/debian/changelog   2024-02-17 
> 20:20:40.0 +
> @@ -1,3 +1,10 @@
> +jxrlib (1.2~git20170615.f752187-5.1) experimental; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Rename libraries for 64-bit time_t transition.
> +
> + -- Steve Langasek   Sat, 17 Feb 2024 20:20:40 +
> +
>  jxrlib (1.2~git20170615.f752187-5) unstable; urgency=medium
>  
>[ Mathieu Malaterre ]
> diff -Nru jxrlib-1.2~git20170615.f752187/debian/control 
> jxrlib-1.2~git20170615.f752187/debian/control
> --- jxrlib-1.2~git20170615.f752187/debian/control 2022-01-28 
> 10:19:14.0 +
> +++ jxrlib-1.2~git20170615.f752187/debian/control 2024-02-17 
> 20:20:40.0 +
> @@ -14,7 +14,10 @@
>  Standards-Version: 4.6.0
>  Rules-Requires-Root: no
>  
> -Package: libjxr0
> +Package: libjxr0t64
> +Provides: ${t64:Provides}
> +Replaces: libjxr0
> +Breaks: libjxr0 (<< ${source:Version})
>  Section: libs
>  Architecture: any
>  Depends: ${misc:Depends}, ${shlibs:Depends}
> @@ -42,7 +45,7 @@
>  Architecture: any
>  Section: libdevel
>  Multi-Arch: same
> -Depends: libjxr0 (= ${binary:Version}), ${misc:Depends}
> +Depends: libjxr0t64 (= ${binary:Version}), ${misc:Depends}
>  Description: JPEG-XR lib - dev files
>   JPEG XR is an approved ISO/IEC International standard (its official
>   designation is ISO/IEC 29199-2).
> diff -Nru jxrlib-1.2~git20170615.f752187/debian/libjxr0t64.lintian-overrides 
> jxrlib-1.2~git20170615.f752187/debian/libjxr0t64.lintian-overrides
> --- jxrlib-1.2~git20170615.f752187/debian/libjxr0t64.lintian-overrides
> 1970-01-01 00:00:00.0 +
> +++ jxrlib-1.2~git20170615.f752187/debian/libjxr0t64.lintian-overrides
> 2024-02-17 20:20:40.0 +
> @@ -0,0 +1 @@
> +libjxr0t64: package-name-doesnt-match-sonames libjxr0
> diff -Nru 

Bug#1067027: python-cryptography build-dependencies unsatisfiable.

[Peter Michael Green]

Package: python-cryptography
Version: 41.0.7-5
Severity: serious
x-debbugs-cc: eam...@debian.org, kapo...@melix.org


python-cryptography build-depends on python3-cryptography-vectors (<< 
41.0.8~)

but unstable has version 42.0.5-1

If you need rust package updates to fix this issue, please tell me what 
they are and

I will see what I can do.

This is blocking the time64 transition for python-cryptography.

Bug#1066237: nas: FTBFS: main.c:125:9: error: implicit declaration of function ‘yyparse’ [-Werror=implicit-function-declaration]

[Steve McIntyre]

On Wed, Mar 13, 2024 at 12:42:56PM +0100, Lucas Nussbaum wrote:
>Source: nas
>Version: 1.9.4-7
>Severity: serious
>Justification: FTBFS
>Tags: trixie sid ftbfs
>User: lu...@debian.org
>Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Thanks for the report!

Nas contains some really awful old C code, and it's taking a bit of
fixing. But I'm getting there...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
You lock the door
And throw away the key
There's someone in my head but it's not me 

Bug#980768: gnupg2: fails to build gpgkeys_ldap, probably due to -Werror=implicit-function-declaration

[Thorsten Glaser]

Hello again,

>Afaict ghostscript/fig2dev have stopped being blockers so I do not plan
>on doing another upload (with more work for the other autobuilders) just
>to temporarily disable these b-ds.

unfortunately, imagemagick/graphicsmagick is still a problem,
and bin:gnupg and bin:gnupg-l10n are arch:all packages, making
it impossible for architectures where the arch:any parts have
not (yet) built to install bin:gnupg which is a frequent B-D.

bye,
//mirabilos
-- 
 you introduced a merge commit│ % g rebase -i HEAD^^
 sorry, no idea and rebasing just fscked │ Segmentation
 should have cloned into a clean repo  │  fault (core dumped)
 if I rebase that now, it's really ugh │ wuahh

Bug#1066113: guix: CVE-2024-27297

[Vagrant Cascadian]

On 2024-03-15, Salvatore Bonaccorso wrote:
> On Fri, Mar 15, 2024 at 11:22:52AM -0700, Vagrant Cascadian wrote:
>> On 2024-03-13, Vagrant Cascadian wrote:
>> > On 2024-03-12, Vagrant Cascadian wrote:
>> >> On 2024-03-12, Salvatore Bonaccorso wrote:
>> > I have now tested an updated 1.4.x package on bookworm and a 1.2.x
>> > package on bullseye, and the reproducer (with a small change for 1.2.x)
>> > was able to reproduce the problem before upgrading to the patched
>> > versions, but not after upgrading to a patched version.
>> >
>> > I've pushed fixes to various branches; debian/latest (for unstable),
>> > debian/bookworm and debian/bullseye:
>> >
>> >   https://salsa.debian.org/debian/guix/
>> 
>> Attached should be debdiffs for updates for bookworm and bullseye. Let
>> me know if I should upload them or if someone from the security team
>> will!
...
> We had a look, and as per
> https://salsa.debian.org/security-tracker-team/security-tracker/-/commit/b11b98d89550ce201b0de31401e822c55f4fa2a1
> we think that it does not require a DSA, but a fix in the upcoming
> point releases would be good.

Oh my! I am a bit shocked by this honestly ... why is it treated as a
minor security issue?

I realize Guix is pretty niche in Debian... Nix is perhaps a little more
widely used...

For anyone with Guix or Nix installed, if I understand correctly, it
basically allows arbitrarily replacing the source code for anything that
you might build using Guix or Nix.


> So can you submit it for the point releases? (make sure to adjust the
> target distribution to bullseye respetively bookworm instead of
> *-security).

I can... although, I would like to make a kind and freindly nudge to
reconsider a DSA if at all possible. :)


> Thanks a lot for your work!

Likewise!


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1065139: morph's abandoned packages (list)

[Torrance, Douglas]

Control: retitle 1065139 ITA: dot2tex -- Graphviz to LaTeX converter
Control: owner 1065139 !
Control: retitle 1065220 ITA: mpmath -- library for arbitrary-precision 
floating-point arithmetic
Control: owner 1065220 !

I'll work on the following:

On Thu 14 Mar 2024 06:20:11 AM GMT, Julian Gilbey  wrote:

#1065139 O: dot2tex -- Graphviz to LaTeX converter
#1065220 O: mpmath -- library for arbitrary-precision floating-point 
arithmetic


Doug


signature.asc
Description: PGP signature

Bug#1067026: graphviz: please build without librsvg except on rust platforms

[Thorsten Glaser]

Source: graphviz
Version: 2.42.2-9
X-Debbugs-Cc: t...@mirbsd.de, debian-po...@lists.debian.org

librsvg has become extremely unportable, and so only a subset of
architectures have it:

amd64 arm64 armel armhf i386 mips64el ppc64el riscv64 s390x
loong64 powerpc ppc64 sparc64

Please whitelist the librsvg usage restricting it to these
architectures. This is a ports-only change, release architectures
are not affected, but it’ll help tremendously.

Bug#1066261: lintian: FTBFS: hello.c:9:5: error: implicit declaration of function 'strcpy' [-Werror=implicit-function-declaration]

[James McCoy]

Control: tag -1 patch

On Wed, Mar 13, 2024 at 12:42:03PM +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> This is most likely caused by a change in dpkg 1.22.6, that enabled
> -Werror=implicit-function-declaration. For more information, see
> https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
> 
> Relevant part (hopefully):
> > cc -o strong \
> > -Wdate-time -D_FORTIFY_SOURCE=2 \
> > -g -O2 -Werror=implicit-function-declaration 
> > -ffile-prefix-map=/<>/debian/test-out/packages/checks/binaries/hardening/binaries-hardening/binaries-hardening-1.0=.
> >  -fstack-protector-strong -fstack-clash-protection -Wformat 
> > -Werror=format-security -fcf-protection \
> > -Wl,-z,relro -Wl,-z,now \
> > hello.c
> > hello.c: In function 'report':
> > hello.c:9:5: error: implicit declaration of function 'strcpy' 
> > [-Werror=implicit-function-declaration]
> > 9 | strcpy(buf, string);
> >   | ^~
> > hello.c:2:1: note: include '' or provide a declaration of 'strcpy'
> > 1 | #include 
> >   +++ |+#include 
> > 2 | 
> > hello.c:9:5: warning: incompatible implicit declaration of built-in 
> > function 'strcpy' [-Wbuiltin-declaration-mismatch]
> > 9 | strcpy(buf, string);
> >   | ^~
> > hello.c:9:5: note: include '' or provide a declaration of 'strcpy'
> > cc1: some warnings being treated as errors
> > make[2]: *** [Makefile:11: all] Error 1

Attached patch fixes these issues.  This is also available as MR!496 on
Salsa.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB
>From 53dc310d4d5af6b0701d55577b30fb9a7e493bd1 Mon Sep 17 00:00:00 2001
From: James McCoy 
Date: Fri, 15 Mar 2024 12:31:42 -0400
Subject: [PATCH] t: Fix compilation failures with dpkg 1.22.6

Dpkg 1.22.6 enables -Werror=implicit-function-declaration by default.
This causes various compilation failures in the tests, mainly due to
missing includes.

The remaining failures are due to newer GCC versions defaulting to the
C11 standard, which doesn't expose the gets() function anymore.  For
these tests, explicitly compile with -std=c99 to re-expose the function.

Closes: #1066261
Signed-off-by: James McCoy 
---
 .../hardening/binaries-hardening/build-spec/orig/hello.c   | 1 +
 .../binaries/static/binaries-golang/build-spec/orig/Makefile   | 2 +-
 .../build-spec/orig/Makefile   | 2 +-
 .../control-file-golang-built-using/build-spec/orig/Makefile   | 2 +-
 .../built-using/binaries-golang/build-spec/orig/Makefile   | 2 +-
 .../import-path/binaries-golang/build-spec/orig/Makefile   | 2 +-
 .../control-file-golang-built-using/build-spec/orig/Makefile   | 2 +-
 .../build-spec/orig/Makefile   | 2 +-
 .../binaries-embedded-libs/build-spec/orig/hardening-trigger.h | 3 +++
 9 files changed, 11 insertions(+), 7 deletions(-)

diff --git a/t/recipes/checks/binaries/hardening/binaries-hardening/build-spec/orig/hello.c b/t/recipes/checks/binaries/hardening/binaries-hardening/build-spec/orig/hello.c
index 7b87bd737..0ee9099e1 100644
--- a/t/recipes/checks/binaries/hardening/binaries-hardening/build-spec/orig/hello.c
+++ b/t/recipes/checks/binaries/hardening/binaries-hardening/build-spec/orig/hello.c
@@ -1,4 +1,5 @@
 #include 
+#include 
 
 void
 report(char *string)
diff --git a/t/recipes/checks/binaries/static/binaries-golang/build-spec/orig/Makefile b/t/recipes/checks/binaries/static/binaries-golang/build-spec/orig/Makefile
index f04b342de..66c9d6f3a 100644
--- a/t/recipes/checks/binaries/static/binaries-golang/build-spec/orig/Makefile
+++ b/t/recipes/checks/binaries/static/binaries-golang/build-spec/orig/Makefile
@@ -4,7 +4,7 @@ COMPILE:= $(CC) $(NOPIE_CFLAGS) $(CPPFLAGS) $(NOPIE_LDFLAGS)
 
 all:
 	# static version
-	$(COMPILE) -static -o basic.static basic.c
+	$(COMPILE) -std=c99 -static -o basic.static basic.c
 
 install:
 	install -d $(DESTDIR)/usr/lib/foo/
diff --git a/t/recipes/checks/debian/control/field/adopted/control-file-golang-xs-go-import-path/build-spec/orig/Makefile b/t/recipes/checks/debian/control/field/adopted/control-file-golang-xs-go-import-path/build-spec/orig/Makefile
index 6047afb59..900ebadbe 100644
--- a/t/recipes/checks/debian/control/field/adopted/control-file-golang-xs-go-import-path/build-spec/orig/Makefile
+++ b/t/recipes/checks/debian/control/field/adopted/control-file-golang-xs-go-import-path/build-spec/orig/Makefile
@@ -4,7 +4,7 @@ COMPILE:= $(CC) $(NOPIE_CFLAGS) $(CPPFLAGS) $(NOPIE_LDFLAGS)
 
 all:
 	# static version
-	$(COMPILE) -static -o static basic.c
+	$(COMPILE) -std=c99 -static -o static basic.c
 
 clean distclean:
 	rm -f basic
diff --git a/t/recipes/checks/debian/control/field/built-using/control-file-golang-built-using/build-spec/orig/Makefile b/t/recipes/checks/debian/control/field/built-using/control-file-golang-built-using/build-spec/orig/Makefile

Bug#1067025: dokuwiki: Please package the new upstream version 2024-02-06a "Kaos"

[Kamaraju Kusumanchi]

Package: dokuwiki
Version: 0.0.20220731.a-2
Severity: wishlist
X-Debbugs-Cc: kamar...@gmail.com

A new upstream version 2024-02-06a “Kaos” is available at
https://download.dokuwiki.org/ . Could you please package it?

Thanks
raju


-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-17-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
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 dokuwiki depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  javascript-common  11+nmu1
ii  libjs-jquery   3.6.1+dfsg+~3.5.14-1
ii  libjs-jquery-cookie12-4
ii  libjs-jquery-ui1.13.2+dfsg-1
ii  libphp-simplepie   1.3.1+dfsg-5
ii  perl   5.36.0-7+deb12u1
ii  php2:8.2+93
ii  php-geshi  1.0.9.1-1
ii  php-phpseclib  2.0.42-1+deb12u1
ii  php-random-compat  2.0.21-1
ii  php-xml2:8.2+93
ii  php8.2 [php]   8.2.7-1~deb12u1
ii  php8.2-xml [php-xml]   8.2.7-1~deb12u1
ii  ucf3.0043+nmu1

Versions of packages dokuwiki recommends:
ii  imagemagick  8:6.9.11.60+dfsg-1.6
ii  imagemagick-6.q16 [imagemagick]  8:6.9.11.60+dfsg-1.6
ii  php-mysql2:8.2+93
ii  php8.2-cli [php-cli] 8.2.7-1~deb12u1
ii  wget 1.21.3-1+b2

Versions of packages dokuwiki suggests:
pn  libapache2-mod-xsendfile  

-- debconf information:
* dokuwiki/wiki/license: cc-by-sa
  dokuwiki/wiki/policy: public
* dokuwiki/wiki/acl: true
  dokuwiki/system/localnet: 10.0.0.0/24
* dokuwiki/system/writeplugins: true
* dokuwiki/system/writeconf: true
  dokuwiki/wiki/fullname: DokuWiki Administrator
* dokuwiki/wiki/title: Debian DokuWiki
* dokuwiki/system/configure-webserver: apache2
* dokuwiki/system/purgepages: false
* dokuwiki/system/documentroot: /dokuwiki
  dokuwiki/wiki/email: webmaster@localhost
* dokuwiki/system/restart-webserver: true
* dokuwiki/system/accessible: global
  dokuwiki/wiki/failpass:
  dokuwiki/wiki/superuser: admin

Bug#1067024: wap-wml-tools: FTBFS with -Werror=implicit-function-declaration

[Andreas Beckmann]

Source: wap-wml-tools
Version: 0.0.4-7
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)

Hi,

wap-wml-tools FTBFS with -Werror=implicit-function-declaration which was
recently enabled by default in dpkg 1.22.6 to support the 64-bit time_t
transition. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

   dh_auto_build
dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 9 
in use)
make -j1
make[1]: Entering directory '/build/wap-wml-tools-0.0.4'
make[2]: Entering directory '/build/wap-wml-tools-0.0.4/rdfwml'
gcc -I../ -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/build/wap-wml-tools-0.0.4=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -O2  -I/usr/
include/libxml2 -o rdfwml rdfwml.c  -lxml2
gcc -I../ -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/build/wap-wml-tools-0.0.4=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -O2  -I/usr/
include/libxml2 -DCGI_BIN -o rdfwml.cgi rdfwml.c  -lxml2
make[2]: Leaving directory '/build/wap-wml-tools-0.0.4/rdfwml'
make[2]: Entering directory '/build/wap-wml-tools-0.0.4/wbmp'
gcc -I../ -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/build/wap-wml-tools-0.0.4=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -O2  -o wbmp2xpm wbmp2xpm.c
wbmp2xpm.c: In function 'main':
wbmp2xpm.c:21:17: error: implicit declaration of function 'exit' 
[-Werror=implicit-function-declaration]
   21 | exit(1);
  | ^~~~
wbmp2xpm.c:12:1: note: include '' or provide a declaration of 'exit'
   11 | #include 
  +++ |+#include 
   12 |
wbmp2xpm.c:21:17: warning: incompatible implicit declaration of built-in 
function 'exit' [-Wbuiltin-declaration-mismatch]
   21 | exit(1);
  | ^~~~
wbmp2xpm.c:21:17: note: include '' or provide a declaration of 'exit'
wbmp2xpm.c:26:17: warning: incompatible implicit declaration of built-in 
function 'exit' [-Wbuiltin-declaration-mismatch]
   26 | exit(1);
  | ^~~~
wbmp2xpm.c:26:17: note: include '' or provide a declaration of 'exit'
wbmp2xpm.c:41:17: warning: incompatible implicit declaration of built-in 
function 'exit' [-Wbuiltin-declaration-mismatch]
   41 | exit(1);
  | ^~~~
wbmp2xpm.c:41:17: note: include '' or provide a declaration of 'exit'
cc1: some warnings being treated as errors
make[2]: *** [Makefile:8: wbmp2xpm] Error 1
make[2]: Leaving directory '/build/wap-wml-tools-0.0.4/wbmp'
make[1]: *** [Makefile:9: all] Error 1
make[1]: Leaving directory '/build/wap-wml-tools-0.0.4'
dh_auto_build: error: make -j1 returned exit code 2
make: *** [debian/rules:10: build] Error 255


Andreas

Bug#1055771: sysvinit script corrections

[Jonas Smedegaard]

Hi Frank,

Quoting Frank Lienhard (2024-03-13 19:06:31)
> Package: radicale
> Version: 3.1.8-2
> [..]
> Filename: pool/DEBIAN/main/r/radicale/radicale_3.1.8-2_all.deb
> 
> My System
> Devuan Daedalus (radicale package the debian bookworm packge)
> 6.1.0-18-amd64
> 
> So applied changes from #1038930 and #1055771
> 
> I'm not a 100% sure that I had the unmodified original, so it would be 
> nice if someone could re-check my attached patch

Thanks for the proposed patch.
Unfortunately it does not apply to the Debian package.
Please provide a patch against the Debian package (not Devuan).

Also, nothing else in the Debian packaging messes with the path
"$dir/collection-root" - that is left for Radicale itself to handle.
Can you please test if adequate to replace the 3 instances of
"$dir/collections" with "$dir" instead?


Kind regards,

 - 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

Bug#1067023: ITP: vaultwarden -- Bitwarden compatible server written in Rust

[Bernhard Dick]

Package: wnpp
Severity: wishlist
Owner: Bernhard Dick 
X-Debbugs-Cc: debian-de...@lists.debian.org, bernh...@bdick.de

* Package name: vaultwarden
  Version : 1.30.5
  Upstream Contact: Daniel García 
* URL : https://github.com/dani-garcia/vaultwarden
* License : AGPL
  Programming Lang: Rust
  Description : Bitwarden compatible server written in Rust

Alternative implementation of the Bitwarden server API written in Rust
and compatible with upstream Bitwarden clients*, perfect for self-hosted
deployment where running the official resource-heavy service might not
be ideal.


OpenPGP_0xD61E22D000471E9B.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065180: argus-clients: diff for NMU version 1:3.0.8.2-6.3

[Sebastian Ramacher]

Control: tags 1065180 + patch

Dear maintainer,

I've prepared an NMU for argus-clients (versioned as 1:3.0.8.2-6.3). The diff
is attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru argus-clients-3.0.8.2/debian/changelog argus-clients-3.0.8.2/debian/changelog
--- argus-clients-3.0.8.2/debian/changelog	2023-07-01 20:20:39.0 +0200
+++ argus-clients-3.0.8.2/debian/changelog	2024-03-17 00:25:35.0 +0100
@@ -1,3 +1,10 @@
+argus-clients (1:3.0.8.2-6.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add libtirpc-dev and libnsl-dev to Build-Depends (Closes: #1065180)
+
+ -- Sebastian Ramacher   Sun, 17 Mar 2024 00:25:35 +0100
+
 argus-clients (1:3.0.8.2-6.2) unstable; urgency=medium
 
   * Non-maintainer upload
diff -Nru argus-clients-3.0.8.2/debian/control argus-clients-3.0.8.2/debian/control
--- argus-clients-3.0.8.2/debian/control	2023-07-01 20:20:30.0 +0200
+++ argus-clients-3.0.8.2/debian/control	2024-03-17 00:25:33.0 +0100
@@ -2,7 +2,7 @@
 Section: utils
 Priority: optional
 Maintainer: Michael Stone 
-Build-Depends: debhelper (>= 12), libreadline-dev, zlib1g-dev, bison, flex, libncurses5-dev, libwrap0-dev, libsasl2-dev, libgeoip-dev, default-libmysqlclient-dev
+Build-Depends: debhelper (>= 12), libreadline-dev, zlib1g-dev, bison, flex, libncurses5-dev, libwrap0-dev, libsasl2-dev, libgeoip-dev, default-libmysqlclient-dev, libtirpc-dev, libnsl-dev
 Standards-Version: 4.5.0
 Homepage: http://qosient.com/argus
 

Bug#1065179: argus: diff for NMU version 2:3.0.8.2-2.3

[Sebastian Ramacher]

Control: tags 1065179 + patch

Dear maintainer,

I've prepared an NMU for argus (versioned as 2:3.0.8.2-2.3). The diff
is attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru argus-3.0.8.2/debian/changelog argus-3.0.8.2/debian/changelog
--- argus-3.0.8.2/debian/changelog	2023-02-12 17:15:42.0 +0100
+++ argus-3.0.8.2/debian/changelog	2024-03-17 00:23:29.0 +0100
@@ -1,3 +1,10 @@
+argus (2:3.0.8.2-2.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add libtirpc-dev and libnsl-dev to Build-Depends (Closes: #1065179)
+
+ -- Sebastian Ramacher   Sun, 17 Mar 2024 00:23:29 +0100
+
 argus (2:3.0.8.2-2.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru argus-3.0.8.2/debian/control argus-3.0.8.2/debian/control
--- argus-3.0.8.2/debian/control	2021-11-07 17:45:39.0 +0100
+++ argus-3.0.8.2/debian/control	2024-03-17 00:23:27.0 +0100
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Michael Stone 
 Standards-Version: 4.5.0
-Build-Depends: libpcap-dev, libwrap0-dev, libsasl2-dev, zlib1g-dev, bison, flex, debhelper (>= 10)
+Build-Depends: libpcap-dev, libwrap0-dev, libsasl2-dev, zlib1g-dev, bison, flex, debhelper (>= 10), libtirpc-dev, libnsl-dev
 Homepage: https://openargus.org
 
 Package: argus-server

Bug#1065109: perdition: diff for NMU version 2.2-3.3

[Sebastian Ramacher]

Control: tags 1065109 + patch
Control: tags 1066417 + patch

Dear maintainer,

I've prepared an NMU for perdition (versioned as 2.2-3.3). The diff
is attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru perdition-2.2/debian/changelog perdition-2.2/debian/changelog
--- perdition-2.2/debian/changelog	2022-04-01 03:39:14.0 +0200
+++ perdition-2.2/debian/changelog	2024-03-17 00:15:52.0 +0100
@@ -1,3 +1,10 @@
+perdition (2.2-3.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add libnsl-dev to Build-Depends (Closes: #1065109, #1066417)
+
+ -- Sebastian Ramacher   Sun, 17 Mar 2024 00:15:52 +0100
+
 perdition (2.2-3.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru perdition-2.2/debian/control perdition-2.2/debian/control
--- perdition-2.2/debian/control	2016-11-28 10:58:07.0 +0100
+++ perdition-2.2/debian/control	2024-03-17 00:15:14.0 +0100
@@ -1,5 +1,5 @@
 Source: perdition
-Build-Depends: libvanessa-logger-dev (>= 0.0.10), libvanessa-adt-dev (>= 0.0.6), libvanessa-socket-dev (>= 0.0.12), libpopt-dev, libpam0g-dev, default-libmysqlclient-dev, libpq-dev, libgdbm-dev, libldap2-dev, debhelper (>= 9.0.0), zlib1g-dev, libssl-dev, unixodbc-dev, libdb-dev, libcdb-dev, libidn11-dev, dpkg-dev (>=1.16.1), dh-autoreconf
+Build-Depends: libvanessa-logger-dev (>= 0.0.10), libvanessa-adt-dev (>= 0.0.6), libvanessa-socket-dev (>= 0.0.12), libpopt-dev, libpam0g-dev, default-libmysqlclient-dev, libpq-dev, libgdbm-dev, libldap2-dev, debhelper (>= 9.0.0), zlib1g-dev, libssl-dev, unixodbc-dev, libdb-dev, libcdb-dev, libidn11-dev, dpkg-dev (>=1.16.1), dh-autoreconf, libnsl-dev
 Section: mail
 Priority: optional
 Maintainer: Simon Horman 

Bug#1065109: perdition: diff for NMU version 2.2-3.3

[Sebastian Ramacher]

Control: tags 1065109 + patch
Control: tags 1066417 + patch

Dear maintainer,

I've prepared an NMU for perdition (versioned as 2.2-3.3). The diff
is attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru perdition-2.2/debian/changelog perdition-2.2/debian/changelog
--- perdition-2.2/debian/changelog	2022-04-01 03:39:14.0 +0200
+++ perdition-2.2/debian/changelog	2024-03-17 00:15:52.0 +0100
@@ -1,3 +1,10 @@
+perdition (2.2-3.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add libnsl-dev to Build-Depends (Closes: #1065109, #1066417)
+
+ -- Sebastian Ramacher   Sun, 17 Mar 2024 00:15:52 +0100
+
 perdition (2.2-3.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru perdition-2.2/debian/control perdition-2.2/debian/control
--- perdition-2.2/debian/control	2016-11-28 10:58:07.0 +0100
+++ perdition-2.2/debian/control	2024-03-17 00:15:14.0 +0100
@@ -1,5 +1,5 @@
 Source: perdition
-Build-Depends: libvanessa-logger-dev (>= 0.0.10), libvanessa-adt-dev (>= 0.0.6), libvanessa-socket-dev (>= 0.0.12), libpopt-dev, libpam0g-dev, default-libmysqlclient-dev, libpq-dev, libgdbm-dev, libldap2-dev, debhelper (>= 9.0.0), zlib1g-dev, libssl-dev, unixodbc-dev, libdb-dev, libcdb-dev, libidn11-dev, dpkg-dev (>=1.16.1), dh-autoreconf
+Build-Depends: libvanessa-logger-dev (>= 0.0.10), libvanessa-adt-dev (>= 0.0.6), libvanessa-socket-dev (>= 0.0.12), libpopt-dev, libpam0g-dev, default-libmysqlclient-dev, libpq-dev, libgdbm-dev, libldap2-dev, debhelper (>= 9.0.0), zlib1g-dev, libssl-dev, unixodbc-dev, libdb-dev, libcdb-dev, libidn11-dev, dpkg-dev (>=1.16.1), dh-autoreconf, libnsl-dev
 Section: mail
 Priority: optional
 Maintainer: Simon Horman 

Bug#1067022: man2html: Segmentation fault with tzfile(5)

[Alejandro Colomar]

Package: man2html
Version: 1.6g-16
Severity: normal
Tags: upstream
X-Debbugs-Cc: Alejandro Colomar , Paul Eggert 
, "G. Branden Robinson" , 
linux-...@vger.kernel.org, gr...@gnu.org, t...@iana.org

Dear Maintainer,

The page tzfile(5) from tzdb-2024a manages to consistently produce a
Segmentation fault with man2html(1).  Below is a reproducer:

alx@debian:~/tmp$ wget 
https://data.iana.org/time-zones/releases/tzdb-2024a.tar.lz 2>/dev/null
alx@debian:~/tmp$ tar xf tzdb-2024a.tar.lz 
alx@debian:~/tmp$ man2html tzdb-2024a/tzfile.5
Content-type: text/html; charset=UTF-8


Man page of tzfile

tzfile
Section: File Formats (5)Updated: Index
Return to Main Contents


NAME

tzfile - timezone information

DESCRIPTION









The timezone information files used by
tzset(3)

are typically found under a directory with a name like
/usr/share/zoneinfo.

These files use the format described in Internet RFC 8536.
Each file is a sequence of 8-bit bytes.
In a file, a binary integer is represented by a sequence of one or
more bytes in network order (bigendian, or high-order byte first),
with all bits significant,
a signed binary integer is represented using two's complement,
and a boolean is represented by a one-byte binary integer that is
either 0 (false) or 1 (true).
The format begins with a 44-byte header containing the following fields:
Segmentation fault
alx@debian:~/tmp$ dpkg -l | grep man2html
ii  man2html   1.6g-16  
 amd64browse man pages in your web browser
ii  man2html-base  1.6g-16  
 amd64convert man pages into HTML format

I've refreshed this page today, and the previous version I used didn't
have this crash.  Below is the part of the diff that I think is
responsible for the crash:

diff --git a/man5/tzfile.5 b/man5/tzfile.5
index 45afecc10..867348d67 100644
--- a/man5/tzfile.5
+++ b/man5/tzfile.5
@@ -26,23 +26,24 @@ .SH DESCRIPTION
 and a boolean is represented by a one-byte binary integer that is
 either 0 (false) or 1 (true).
 The format begins with a 44-byte header containing the following 
fields:
-.IP * 2
+.RS "\w'  'u"
+.IP \(bu "\w'\(bu  'u"
 The magic four-byte ASCII sequence
 .q "TZif"
 identifies the file as a timezone information file.

BTW, I noticed that the upstream homepage is dead:
.
Is this project defunct?

Have a lovely day!
Alex


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

Kernel: Linux 6.8.0-rc7-alx-dirty (SMP w/24 CPU threads; PREEMPT)
Locale: LANG=C.utf8, LC_CTYPE=C.utf8 (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 man2html depends on:
ii  debconf [debconf-2.0]  1.5.86
ii  gawk   1:5.2.1-2
ii  libc6  2.37-15.1
ii  lynx   2.9.0rel.0-2+b1
ii  man-db 2.12.0-3
ii  man2html-base  1.6g-16
ii  sensible-utils 0.0.22

man2html recommends no packages.

Versions of packages man2html suggests:
ii  firefox-esr [www-browser]  115.8.0esr-1+b1
ii  lynx [www-browser] 2.9.0rel.0-2+b1
pn  swish++
ii  w3m [www-browser]  0.5.3+git20230121-2+b3

-- debconf information:
  man2html/index_manpages: true

Bug#1067021: mrpt ftbfs on armhf (32bit time_t64 architecture)

[Matthias Klose]

Package: src:mrpt
Version: 1:2.11.10+ds-2
Severity: serious
Tags: sid trixie ftbfs

the package ftbfs on armhf (32bit time_t64 architecture):

full build log at
https://launchpad.net/ubuntu/+source/mrpt/1:2.11.10+ds-2/+build/27932950

[...]
[100%] Building CXX object 
python/CMakeFiles/pymrpt.dir/all_mrpt_system.cpp.o
cd /<>/.pybuild/cpython3_3.12/build/python && /usr/bin/c++ 
-DMRPT_BUILDING_PYTHON_WRAPPER -Doverride_caster_t=overload_caster_t 
-Dpymrpt_EXPORTS -I/<>/python/. 
-I/<>/libs/apps/include 
-I/<>/libs/hwdrivers/include 
-I/<>/libs/comms/include -I/<>/libs/io/include 
-I/<>/libs/system/include 
-I/<>/libs/typemeta/include 
-I/<>/libs/containers/include 
-I/<>/.pybuild/cpython3_3.12/build/include/mrpt-configuration 
-I/<>/libs/core/include 
-I/<>/libs/maps/include -I/<>/libs/obs/include 
-I/<>/libs/opengl/include 
-I/<>/libs/poses/include 
-I/<>/libs/bayes/include 
-I/<>/libs/math/include -I/usr/include/suitesparse 
-I/<>/libs/serialization/include 
-I/<>/libs/rtti/include 
-I/<>/libs/random/include 
-I/<>/libs/config/include 
-I/<>/libs/expr/include -I/<>/libs/img/include 
-I/<>/libs/tfest/include 
-I/<>/libs/graphs/include 
-I/<>/libs/gui/include 
-I/<>/3rdparty/nanogui/ext/nanovg/src 
-I/<>/3rdparty/nanogui/include 
-I/<>/.pybuild/cpython3_3.12/build/3rdparty/nanogui 
-I/<>/libs/vision/include 
-I/<>/libs/slam/include 
-I/<>/libs/tclap/include 
-I/<>/libs/topography/include 
-I/<>/libs/nav/include 
-I/<>/libs/kinematics/include -isystem 
/usr/include/python3.12 -isystem /usr/include/eigen3 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fno-stack-clash-protection 
-fdebug-prefix-map=/<>=/usr/src/mrpt-1:2.11.10+ds-2 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
-D_FORTIFY_SOURCE=3 -D_FILE_OFFSET_BITS=64 -fPIC -fvisibility=hidden 
-flto -fno-fat-lto-objects -MD -MT 
python/CMakeFiles/pymrpt.dir/all_mrpt_system.cpp.o -MF 
CMakeFiles/pymrpt.dir/all_mrpt_system.cpp.o.d -o 
CMakeFiles/pymrpt.dir/all_mrpt_system.cpp.o -c 
/<>/python/all_mrpt_system.cpp

In file included from /<>/python/all_mrpt_system.cpp:7:
/<>/python/src/mrpt/system/datetime.cpp: In function ‘void 
bind_mrpt_system_datetime(std::functionstd::__cxx11::basic_string&)>&)’:
/<>/python/src/mrpt/system/datetime.cpp:60:96: error: 
address of overloaded function with no contextual type information
   60 | M("mrpt::system").def("time_tToTimestamp", 
(mrpt::Clock::time_point (*)(const long &)) 
::system::time_tToTimestamp, "Transform from standard \"time_t\" to 
TTimeStamp.\n \n\n timestampTotime_t\n\nC++: 
mrpt::system::time_tToTimestamp(const long &) --> 
mrpt::Clock::time_point", pybind11::arg("t"));
  | 
   ^~~~

Bug#1067020: jupyterlab: please use node-get-intrinsic

[Bastien Roucariès]

Source: jupyterlab
Version: 4.0.11+ds1-1
Severity: important

Dear Maintainer,

Your package include files included elsewhere:
python3-jupyterlab: /usr/share/jupyter/lab/staging/node_modules/get-
intrinsic/.eslintrc
python3-jupyterlab: /usr/share/jupyter/lab/staging/node_modules/get-
intrinsic/.github/FUNDING.yml
python3-jupyterlab: /usr/share/jupyter/lab/staging/node_modules/get-
intrinsic/.nycrc
python3-jupyterlab: /usr/share/jupyter/lab/staging/node_modules/get-
intrinsic/CHANGELOG.md
python3-jupyterlab: /usr/share/jupyter/lab/staging/node_modules/get-
intrinsic/LICENSE
python3-jupyterlab: /usr/share/jupyter/lab/staging/node_modules/get-
intrinsic/README.md
python3-jupyterlab: /usr/share/jupyter/lab/staging/node_modules/get-
intrinsic/index.js
python3-jupyterlab: /usr/share/jupyter/lab/staging/node_modules/get-
intrinsic/package.json
python3-jupyterlab: /usr/share/jupyter/lab/staging/node_modules/get-
intrinsic/test/GetIntrinsic.js


-- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armel

Kernel: Linux 6.6.15-rt-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1067019: jupyterlab: use pacckaged node-call-bind (provided package)

[Bastien Roucariès]

Source: jupyterlab
Version: 4.0.11+ds1-1
Severity: important

Dear Maintainer,

node-call-bind provided virtual package provides these files
python3-jupyterlab: /usr/share/jupyter/lab/staging/node_modules/call-
bind/.eslintignore
python3-jupyterlab: /usr/share/jupyter/lab/staging/node_modules/call-
bind/.eslintrc
python3-jupyterlab: /usr/share/jupyter/lab/staging/node_modules/call-
bind/.github/FUNDING.yml
python3-jupyterlab: /usr/share/jupyter/lab/staging/node_modules/call-
bind/.nycrc
python3-jupyterlab: /usr/share/jupyter/lab/staging/node_modules/call-
bind/CHANGELOG.md
python3-jupyterlab: /usr/share/jupyter/lab/staging/node_modules/call-
bind/LICENSE
python3-jupyterlab: /usr/share/jupyter/lab/staging/node_modules/call-
bind/README.md
python3-jupyterlab: /usr/share/jupyter/lab/staging/node_modules/call-
bind/callBound.js
python3-jupyterlab: /usr/share/jupyter/lab/staging/node_modules/call-
bind/index.js
python3-jupyterlab: /usr/share/jupyter/lab/staging/node_modules/call-
bind/package.json
python3-jupyterlab: /usr/share/jupyter/lab/staging/node_modules/call-
bind/test/callBound.js
python3-jupyterlab: /usr/share/jupyter/lab/staging/node_modules/call-
bind/test/index.js


-- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armel

Kernel: Linux 6.6.15-rt-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1067018: lnav: FTBFS on arm{el,hf}: test failures

[Sebastian Ramacher]

Source: lnav
Version: 0.11.2-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=lnav=armhf=0.11.2-1%2Bb1=1710618595=0


2024-03-16T19:49:36+00:00 
␛[0;35m=␛[0m
␛[0;35mCommand␛[0m: test: env TEST_COMMENT=parse_url1 ./drive_sql
␛[0;32mBEGIN␛[0m 
test_sql_str_func.sh_b088735cf46f23ca3d5fb3da41f07a6a3b1cba35.out
␛[0;32mEND␛[0m   
test_sql_str_func.sh_b088735cf46f23ca3d5fb3da41f07a6a3b1cba35.out
OUT: test: env TEST_COMMENT=parse_url1 ./drive_sql
--- 
/<>/test/expected/test_sql_str_func.sh_b088735cf46f23ca3d5fb3da41f07a6a3b1cba35.out
2023-07-03 04:16:02.0 +
+++ test_sql_str_func.sh_b088735cf46f23ca3d5fb3da41f07a6a3b1cba35.out   
2024-03-16 19:49:36.550940820 +
@@ -1,2 +0,0 @@
-Row 0:
-  Column parse_url('https://example.com'): 
{"scheme":"https","user":null,"password":null,"host":"example.com","port":null,"path":"/","query":null,"parameters":null,"fragment":null}
FAIL! EXPECTED OUT DIFF
␛[0;31mBEGIN␛[0m 
test_sql_str_func.sh_b088735cf46f23ca3d5fb3da41f07a6a3b1cba35.err
error: sqlite3_exec failed -- misuse of sqlite3_result_subtype() by parse_url()
␛[0;31mEND␛[0m   
test_sql_str_func.sh_b088735cf46f23ca3d5fb3da41f07a6a3b1cba35.err
ERR: test: env TEST_COMMENT=parse_url1 ./drive_sql
--- 
/<>/test/expected/test_sql_str_func.sh_b088735cf46f23ca3d5fb3da41f07a6a3b1cba35.err
2023-07-03 04:16:02.0 +
+++ test_sql_str_func.sh_b088735cf46f23ca3d5fb3da41f07a6a3b1cba35.err   
2024-03-16 19:49:36.558940841 +
@@ -0,0 +1 @@
+error: sqlite3_exec failed -- misuse of sqlite3_result_subtype() by parse_url()
FAIL! EXPECTED ERR DIFF

2024-03-16T19:49:36+00:00 
␛[0;35m=␛[0m
␛[0;35mCommand␛[0m: test: env TEST_COMMENT=parse_url2 ./drive_sql
␛[0;32mBEGIN␛[0m 
test_sql_str_func.sh_0947bfe7ec626eaa0409a45b10fcbb634fb12eb7.out
␛[0;32mEND␛[0m   
test_sql_str_func.sh_0947bfe7ec626eaa0409a45b10fcbb634fb12eb7.out
OUT: test: env TEST_COMMENT=parse_url2 ./drive_sql
--- 
/<>/test/expected/test_sql_str_func.sh_0947bfe7ec626eaa0409a45b10fcbb634fb12eb7.out
2023-07-03 04:16:02.0 +
+++ test_sql_str_func.sh_0947bfe7ec626eaa0409a45b10fcbb634fb12eb7.out   
2024-03-16 19:49:36.662941118 +
@@ -1,2 +0,0 @@
-Row 0:
-  Column parse_url('https://example.com/'): 
{"scheme":"https","user":null,"password":null,"host":"example.com","port":null,"path":"/","query":null,"parameters":null,"fragment":null}
FAIL! EXPECTED OUT DIFF
␛[0;31mBEGIN␛[0m 
test_sql_str_func.sh_0947bfe7ec626eaa0409a45b10fcbb634fb12eb7.err
error: sqlite3_exec failed -- misuse of sqlite3_result_subtype() by parse_url()
␛[0;31mEND␛[0m   
test_sql_str_func.sh_0947bfe7ec626eaa0409a45b10fcbb634fb12eb7.err
ERR: test: env TEST_COMMENT=parse_url2 ./drive_sql
--- 
/<>/test/expected/test_sql_str_func.sh_0947bfe7ec626eaa0409a45b10fcbb634fb12eb7.err
2023-07-03 04:16:02.0 +
+++ test_sql_str_func.sh_0947bfe7ec626eaa0409a45b10fcbb634fb12eb7.err   
2024-03-16 19:49:36.674941150 +
@@ -0,0 +1 @@
+error: sqlite3_exec failed -- misuse of sqlite3_result_subtype() by parse_url()
FAIL! EXPECTED ERR DIFF

2024-03-16T19:49:36+00:00 
␛[0;35m=␛[0m
␛[0;35mCommand␛[0m: test: env TEST_COMMENT=parse_url3 ./drive_sql
␛[0;32mBEGIN␛[0m 
test_sql_str_func.sh_bac7f6531a2adf70cd1871fb13eab26dff133b7c.out
␛[0;32mEND␛[0m   
test_sql_str_func.sh_bac7f6531a2adf70cd1871fb13eab26dff133b7c.out
OUT: test: env TEST_COMMENT=parse_url3 ./drive_sql
--- 
/<>/test/expected/test_sql_str_func.sh_bac7f6531a2adf70cd1871fb13eab26dff133b7c.out
2023-07-03 04:16:02.0 +
+++ test_sql_str_func.sh_bac7f6531a2adf70cd1871fb13eab26dff133b7c.out   
2024-03-16 19:49:36.778941428 +
@@ -1,2 +0,0 @@
-Row 0:
-  Column parse_url('https://example.com/search?flag'): 
{"scheme":"https","user":null,"password":null,"host":"example.com","port":null,"path":"/search","query":"flag","parameters":{"flag":null},"fragment":null}
FAIL! EXPECTED OUT DIFF
␛[0;31mBEGIN␛[0m 
test_sql_str_func.sh_bac7f6531a2adf70cd1871fb13eab26dff133b7c.err
error: sqlite3_exec failed -- misuse of sqlite3_result_subtype() by parse_url()
␛[0;31mEND␛[0m   
test_sql_str_func.sh_bac7f6531a2adf70cd1871fb13eab26dff133b7c.err
ERR: test: env TEST_COMMENT=parse_url3 ./drive_sql
--- 
/<>/test/expected/test_sql_str_func.sh_bac7f6531a2adf70cd1871fb13eab26dff133b7c.err
2023-07-03 04:16:02.0 +
+++ test_sql_str_func.sh_bac7f6531a2adf70cd1871fb13eab26dff133b7c.err   
2024-03-16 19:49:36.790941460 +
@@ -0,0 +1 @@
+error: sqlite3_exec failed -- misuse of sqlite3_result_subtype() by parse_url()
FAIL! EXPECTED ERR DIFF

2024-03-16T19:49:36+00:00 
␛[0;35m=␛[0m
␛[0;35mCommand␛[0m: test: env TEST_COMMENT=parse_url4 ./drive_sql

Bug#1067016: osslsigncode: FTBFS on arm{el,hf}: test failures

[Sebastian Ramacher]

Source: osslsigncode
Version: 2.8-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=osslsigncode=armhf=2.8-1=1710618749=0


The following tests FAILED:
 64 - attached_pem_exe (Not Run)
 65 - attached_der_exe (Not Run)
 66 - attached_pem_ex_ (Not Run)
 67 - attached_der_ex_ (Not Run)
 68 - attached_pem_msi (Not Run)
 69 - attached_der_msi (Not Run)
 70 - attached_pem_256appx (Not Run)
 71 - attached_der_256appx (Not Run)
 72 - attached_pem_512appx (Not Run)
 73 - attached_der_512appx (Not Run)
 74 - attached_pem_ps1 (Not Run)
 75 - attached_der_ps1 (Not Run)
 76 - attached_pem_psc1 (Not Run)
 77 - attached_der_psc1 (Not Run)
 78 - attached_pem_mof (Not Run)
 79 - attached_der_mof (Not Run)
 98 - verify_catalog_exe (Failed)
 99 - verify_catalog_ex_ (Failed)
100 - verify_catalog_msi (Failed)
101 - verify_catalog_ps1 (Failed)
102 - verify_catalog_psc1 (Failed)
103 - verify_catalog_mof (Failed)
104 - verify_legacy_exe (Not Run)
105 - verify_legacy_ex_ (Not Run)
106 - verify_legacy_msi (Not Run)
107 - verify_legacy_256appx (Not Run)
108 - verify_legacy_512appx (Not Run)
109 - verify_legacy_cat (Not Run)
110 - verify_legacy_ps1 (Not Run)
111 - verify_legacy_psc1 (Not Run)
112 - verify_legacy_mof (Not Run)
113 - verify_signed_exe (Not Run)
114 - verify_signed_ex_ (Not Run)
115 - verify_signed_msi (Not Run)
116 - verify_signed_256appx (Not Run)
117 - verify_signed_512appx (Not Run)
118 - verify_signed_cat (Not Run)
119 - verify_signed_ps1 (Not Run)
120 - verify_signed_psc1 (Not Run)
121 - verify_signed_mof (Not Run)
122 - verify_nested_exe (Not Run)
123 - verify_nested_ex_ (Not Run)
124 - verify_nested_msi (Not Run)
125 - verify_nested_256appx (Not Run)
126 - verify_nested_512appx (Not Run)
127 - verify_nested_cat (Not Run)
128 - verify_nested_ps1 (Not Run)
129 - verify_nested_psc1 (Not Run)
130 - verify_nested_mof (Not Run)
131 - verify_added_exe (Not Run)
132 - verify_added_ex_ (Not Run)
133 - verify_added_msi (Not Run)
134 - verify_added_256appx (Not Run)
135 - verify_added_512appx (Not Run)
136 - verify_added_cat (Not Run)
137 - verify_added_ps1 (Not Run)
138 - verify_added_psc1 (Not Run)
139 - verify_added_mof (Not Run)
157 - verify_attached_pem_exe (Not Run)
158 - verify_attached_pem_ex_ (Not Run)
159 - verify_attached_pem_msi (Not Run)
160 - verify_attached_pem_256appx (Not Run)
161 - verify_attached_pem_512appx (Not Run)
162 - verify_attached_pem_ps1 (Not Run)
163 - verify_attached_pem_psc1 (Not Run)
164 - verify_attached_pem_mof (Not Run)
165 - verify_attached_der_exe (Not Run)
166 - verify_attached_der_ex_ (Not Run)
167 - verify_attached_der_msi (Not Run)
168 - verify_attached_der_256appx (Not Run)
169 - verify_attached_der_512appx (Not Run)
170 - verify_attached_der_ps1 (Not Run)
171 - verify_attached_der_psc1 (Not Run)
172 - verify_attached_der_mof (Not Run)
287 - attached_data_exe_pem_pem (SEGFAULT)
288 - attached_data_exe_pem_der (SEGFAULT)
289 - attached_data_exe_der_pem (SEGFAULT)
290 - attached_data_exe_der_der (SEGFAULT)
297 - attached_data_ex__pem_pem (SEGFAULT)
298 - attached_data_ex__pem_der (SEGFAULT)
299 - attached_data_ex__der_pem (SEGFAULT)
300 - attached_data_ex__der_der (SEGFAULT)
307 - attached_data_msi_pem_pem (Failed)
308 - attached_data_msi_pem_der (Failed)
309 - attached_data_msi_der_pem (Failed)
310 - attached_data_msi_der_der (Failed)
317 - attached_data_256appx_pem_pem (Failed)
318 - attached_data_256appx_pem_der (Failed)
319 - attached_data_256appx_der_pem (Failed)
320 - attached_data_256appx_der_der (Failed)
327 - attached_data_512appx_pem_pem (Failed)
328 - attached_data_512appx_pem_der (Failed)
329 - attached_data_512appx_der_pem (Failed)
330 - attached_data_512appx_der_der (Failed)
337 - attached_data_ps1_pem_pem (Failed)
338 - attached_data_ps1_pem_der (Failed)
339 - attached_data_ps1_der_pem (Failed)
340 - attached_data_ps1_der_der (Failed)
347 - attached_data_psc1_pem_pem (Failed)
348 - attached_data_psc1_pem_der (Failed)
349 - attached_data_psc1_der_pem (Failed)
350 - attached_data_psc1_der_der (Failed)
357 - 

Bug#1067017: jupyterlab: Use node-long package

[Bastien Roucariès]

Source: jupyterlab
Version: 4.0.11+ds1-1
Severity: serious
Justification: duplicate code source not build from source

Dear Maintainer,

Your package include the following file packaged elsewhere
python3-jupyterlab:
/usr/share/jupyter/lab/staging/node_modules/@xtuc/long/LICENSE
python3-jupyterlab:
/usr/share/jupyter/lab/staging/node_modules/@xtuc/long/README.md
python3-jupyterlab:
/usr/share/jupyter/lab/staging/node_modules/@xtuc/long/dist/long.js
python3-jupyterlab:
/usr/share/jupyter/lab/staging/node_modules/@xtuc/long/dist/long.js.map
python3-jupyterlab:
/usr/share/jupyter/lab/staging/node_modules/@xtuc/long/index.d.ts
python3-jupyterlab:
/usr/share/jupyter/lab/staging/node_modules/@xtuc/long/index.js
python3-jupyterlab:
/usr/share/jupyter/lab/staging/node_modules/@xtuc/long/package.json
python3-jupyterlab:
/usr/share/jupyter/lab/staging/node_modules/@xtuc/long/src/long.js


Moreover, it was hard for debian to get this files builded and @xtuc ones does
not build from source

Bastien


-- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armel

Kernel: Linux 6.6.15-rt-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1067015: xrootd: FTBFS on arm{el,hf}: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"

[Sebastian Ramacher]

Source: xrootd
Version: 5.6.7-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=xrootd=armhf=5.6.7-1.1=1710627143=0

make[4]: Leaving directory '/<>/obj-arm-linux-gnueabihf'
/<>/src/XrdApps/Xrdadler32.cc: In function ‘int 
fGetXattrAdler32(int, const char*, char*)’:
/<>/src/XrdApps/Xrdadler32.cc:91:23: warning: format ‘%ld’ expects 
argument of type ‘long int’, but argument 3 has type ‘__time64_t’ {aka ‘long 
long int’} [-Wformat=]
   91 | sprintf(mtime, "%ld", st.st_mtime);
  | ~~^
  |   |
  |   long int
  | %lld
[ 91%] Built target xrdcl-tls
make  -f src/CMakeFiles/XrdPosixPreload.dir/build.make 
src/CMakeFiles/XrdPosixPreload.dir/depend
make[4]: Entering directory '/<>/obj-arm-linux-gnueabihf'
cd /<>/obj-arm-linux-gnueabihf && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<>/src 
/<>/obj-arm-linux-gnueabihf 
/<>/obj-arm-linux-gnueabihf/src 
/<>/obj-arm-linux-gnueabihf/src/CMakeFiles/XrdPosixPreload.dir/DependInfo.cmake
 "--color="
make[4]: Leaving directory '/<>/obj-arm-linux-gnueabihf'
make  -f src/CMakeFiles/XrdPosixPreload.dir/build.make 
src/CMakeFiles/XrdPosixPreload.dir/build
make[4]: Entering directory '/<>/obj-arm-linux-gnueabihf'
[ 91%] Building CXX object 
src/CMakeFiles/XrdPosixPreload.dir/XrdPosix/XrdPosixPreload32.cc.o
cd /<>/obj-arm-linux-gnueabihf/src && /usr/bin/c++ -DHAVE_ATOMICS 
-DHAVE_CRYPT -DHAVE_CURL_MULTI_WAIT -DHAVE_DH_PADDED -DHAVE_ET_COM_ERR_H 
-DHAVE_FSTATAT -DHAVE_FUSE -DHAVE_GETHBYXR -DHAVE_GETIFADDRS -DHAVE_LIBZ 
-DHAVE_NAMEINFO -DHAVE_PROTOR -DHAVE_READLINE -DHAVE_SENDFILE -DHAVE_SETRESUID 
-DHAVE_SHADOWPW -DHAVE_SIGWTI -DHAVE_SSL -DHAVE_SYSTEMD -DHAVE_XML2 
-DHAVE_XRDCRYPTO -DXRDPLUGIN_SOVERSION=\"5\" -DXrdPosixPreload_EXPORTS 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE 
-I/<>/obj-arm-linux-gnueabihf/src -I/<>/src -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
-Wextra -Wno-unused-parameter -std=gnu++14 -fPIC -fno-lto -MD -MT 
src/CMakeFiles/XrdPosixPreload.dir/XrdPosix/XrdPosixPreload32.cc.o -MF 
CMakeFiles/XrdPosixPreload.dir/XrdPosix/XrdPosixPreload32.cc.o.d -o 
CMakeFiles/XrdPosixPreload.dir/XrdPosix/XrdPosixPreload32.cc.o -c 
/<>/src/XrdPosix/XrdPosixPreload32.cc
In file included from /usr/include/features.h:393,
 from 
/usr/include/arm-linux-gnueabihf/c++/13/bits/os_defines.h:39,
 from 
/usr/include/arm-linux-gnueabihf/c++/13/bits/c++config.h:679,
 from /usr/include/c++/13/cerrno:41,
 from /<>/src/XrdPosix/XrdPosixPreload32.cc:51:
/usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed 
only with _FILE_OFFSET_BITS=64"
   26 | #   error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
  | ^

Cheers
-- 
Sebastian Ramacher

Bug#1061087: RFS: bash-unit/2.3.1-1 [ITP] -- bash_unit - bash unit testing

[Martin Dosch]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "bash-unit":

 * Package name : bash-unit
   Version  : 2.3.1-1
   Upstream contact : Pascal Grange 
 * URL  : https://github.com/pgrange/bash_unit
 * License  : GPL-3
 * Vcs  : https://salsa.debian.org/mdosch/bash-unit
   Section  : devel

The source builds the following binary packages:

  bash-unit - bash_unit - bash unit testing

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/bash-unit/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/b/bash-unit/bash-unit_2.3.1-1.dsc

Changes for the initial release:

 bash-unit (2.3.1-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #839210)

Regards,
--
  Martin Dosch


signature.asc
Description: PGP signature

Bug#1067014: accesses internet during build

[Thomas Goirand]

Source: mapclassify
Version: 2.6.1-3
Severity: important

Hi,

During the build, mapclassify is using intersphinx, which is collecting
information from the internet during build. Please remove the intersphinx
module from docs/conf.py.

Cheers,

Thomas Goirand (zigo)

Bug#1067013: trn4: FTBFS with -Werror=implicit-function-declaration

[Andreas Beckmann]

Source: trn4
Version: 4.0-test77-16
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)

Hi,

trn4 FTBFS with -Werror=implicit-function-declaration which was
recently enabled by default in dpkg 1.22.6 to support the 64-bit time_t
transition. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

   debian/rules override_dh_auto_configure
make[1]: Entering directory '/build/trn4-4.0-test77'
cp debian/Policy.sh .
# Configure adds -DDEBUG for us when we use -g.
./Configure -OdErs
First let's make sure your kit is complete.  Checking...
Locating common programs...
Checking compatibility between /usr/bin/echo and builtin echo (if any)...
Symbolic links are supported.
Good, your tr supports [:lower:] and [:upper:] to convert case.
Using [:upper:] and [:lower:] to convert case.
aix_rs   domainos   i386  linux  sco_3_2_4 svr4
altos486 dynix  irix  mc6000 sco_xenix
convexos freebsdisc_2_2_1 mips   sgi
dec_osf1 hp9000_800 isc_3_2_2 next   solaris_2
dgux hpux   isc_3_2_3 sco_3  sunos
Which of these apply, if any? [Policy linux]
Operating system name? [linux]
Select the news spool support ("local", "nntp", or "both"): [both]
Do you want to use generic user-authentication? [y]
Enter "local", a server name, or a file name (~name ok): [/etc/news/server]
Do you expect to run these scripts and binaries on multiple machines? [n]
Installation prefix to use? (~name ok) [/usr]
Where is the news library directory for local news? (~name ok)
[/var/lib/news]
Directory /var/lib/news doesn't exist.  Use that name anyway? [y]
Where is the newsgroups file? ("none" ok) (~name ok) [none]
Pathname where trn's inews will reside? ("none" ok) (~name ok)
[/usr/lib/trn4]
Directory /usr/lib/trn4 doesn't exist.  Use that name anyway? [y]
Which inews should be used for posting local articles? (~name ok)
[/usr/bin/inews]
File /usr/bin/inews doesn't exist.  Use that name anyway? [y]
Enter a local directory for overview files, "remote", or "none":  (~name ok)
[remote]
Enter a local directory for thread files, "remote", or "none":  (~name ok)
[remote]
Do you want trn to default to -x, regardless of name? [n]
Should the -X option be on by default for trn (not rn)? [y]
Pathname where the public executables will reside? (~name ok)
[/usr/lib/trn4]
Directory /usr/lib/trn4 doesn't exist.  Use that name anyway? [y]
What directory name should be used for the install? (~name ok)
[/usr/lib/trn4]
Directory /usr/lib/trn4 doesn't exist.  Use that name anyway? [y]
What is the distribution code for your local organization? [none]
What is the distribution code for your organization? [none]
What is the distribution code for your city? [none]
What is the distribution code for your state/province? [none]
What is the distribution code for your multi-state region? [none]
What is the distribution code for your country? [none]
What is the distribution code for your continent? [none]
System manual is in /usr/share/man/man1.
Use which C compiler? [gcc]
Checking for GNU cc in disguise and/or its version number...
What hostname goes on the From line of this machine's postings?
[/etc/mailname]
Compare how many dot-separated words from the end of the hostname? [2]
Where do the manual pages (source) go? (~name ok) [/usr/share/man/man1]
What directory name should be used for the install? (~name ok)
[/usr/share/man/man1]
Pathname where the private library files will reside? (~name ok)
[/usr/share/trn4]
What directory name should be used for the install? (~name ok)
[/usr/share/trn4]
Directory /usr/share/trn4 doesn't exist.  Use that name anyway? [y]
Which interactive speller should we use? ("none" ok) [/usr/bin/ispell]
What options should be used? ("none" ok) [none]
What global mimecap file should trn use? ("none" ok) (~name ok)
[/etc/mailcap]
File /etc/mailcap doesn't exist.  Use that name anyway? [y]
Organization: [/etc/news/organization]
Do you want to include strn's scan and score features? [y]
Now, how can we feed standard input to your C preprocessor...
Directories to use for library searches?
[/lib /lib/x86_64-linux-gnu /usr/lib /usr/lib/x86_64-linux-gnu]
What is the file extension used for shared libraries? [so]
Checking for optional libraries...
Any additional libraries? [-lresolv -lnsl]
What optimizer/debugger flag should be used? [-O]
Any additional cc flags?
[-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/build/trn4-4.0-test77=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall 
-DINET6 -D_FILE_OFFSET_BITS=64 -fpcc-struct-return]
Let me guess what the preprocessor flags are...
Any additional ld flags (NOT including libraries)? [-Wl,-z,relro]
Checking your choice of C compiler and flags for coherency...
I've tried to compile 

Bug#1066092: koko: please enable blhc-recommended build hardening

[Marco Mattiolo]

Hi,
thank you for the report.

I believe this is not a bug in koko: can you please check the build log against 
blhc 0.14 (not yet in Debian)? Background is [1].

Kind regards
Marco

[1]https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043522

Bug#1067012: renderdoc: FTBFS with glslang 14: fatal error: glslang/Include/Types.h: No such file or directory

[Andreas Beckmann]

Source: renderdoc
Version: 1.27+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

renderdoc FTBFS with glslang 14 in sid due to a missing header:

[184/311] /usr/bin/c++ -DAMD_EXTENSIONS 
-DDISTRIBUTION_CONTACT=\"https://salsa.debian.org/xorg-team/app/renderdoc\; 
-DDISTRIBUTION_NAME=\"Debian\" -DDISTRIBUTION_VERSION=\"1.27+dfsg-1\" 
-DNV_EXTENSIONS -DRELEASE -DRENDERDOC_EXPORTS -DRENDERDOC_PLATFORM_LINUX
 -DRENDERDOC_STABLE_BUILD=1 -DRENDERDOC_SUPPORT_EGL -DRENDERDOC_SUPPORT_GL 
-DRENDERDOC_SUPPORT_GLES -DRENDERDOC_SUPPORT_VULKAN 
-DRENDERDOC_VULKAN_JSON_SUFFIX="" -DRENDERDOC_WINDOWING_XCB 
-DRENDERDOC_WINDOWING_XLIB -DRENDERDOC_X86_PROC_FAMILY=1 -I/build/rende
rdoc-1.27+dfsg/renderdoc -I/build/renderdoc-1.27+dfsg/renderdoc/3rdparty -g -O2 
-ffile-prefix-map=/build/renderdoc-1.27+dfsg=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wdate-time -D_FORTIFY_SOURCE=2 
-std=c++11 -fno-strict-aliasing -fvisibility=hidden -fvisibility-inlines-hidden 
-Wall -Wextra -Wno-unused-variable -Wno-unused-parameter -Wno-unused-result 
-Wno-type-limits -Wno-missing-field-initializers -Wno-unknown-pragmas 
-Wno-reorder -Wno-unused-but-set
-variable -Wno-maybe-uninitialized -Wno-class-memaccess 
-Wimplicit-fallthrough=2 -Wno-unused-value -O3 -DNDEBUG -fPIC -MD -MT 
renderdoc/driver/shaders/spirv/CMakeFiles/rdoc_spirv.dir/glslang_compile.cpp.o 
-MF renderdoc/driver/shaders/spirv/CMakeFiles/rdoc_sp
irv.dir/glslang_compile.cpp.o.d -o 
renderdoc/driver/shaders/spirv/CMakeFiles/rdoc_spirv.dir/glslang_compile.cpp.o 
-c /build/renderdoc-1.27+dfsg/renderdoc/driver/shaders/spirv/glslang_compile.cpp
FAILED: 
renderdoc/driver/shaders/spirv/CMakeFiles/rdoc_spirv.dir/glslang_compile.cpp.o 
/usr/bin/c++ -DAMD_EXTENSIONS 
-DDISTRIBUTION_CONTACT=\"https://salsa.debian.org/xorg-team/app/renderdoc\; 
-DDISTRIBUTION_NAME=\"Debian\" -DDISTRIBUTION_VERSION=\"1.27+dfsg-1\" 
-DNV_EXTENSIONS -DRELEASE -DRENDERDOC_EXPORTS -DRENDERDOC_PLATFORM_LINUX 
-DRENDERD
OC_STABLE_BUILD=1 -DRENDERDOC_SUPPORT_EGL -DRENDERDOC_SUPPORT_GL 
-DRENDERDOC_SUPPORT_GLES -DRENDERDOC_SUPPORT_VULKAN 
-DRENDERDOC_VULKAN_JSON_SUFFIX="" -DRENDERDOC_WINDOWING_XCB 
-DRENDERDOC_WINDOWING_XLIB -DRENDERDOC_X86_PROC_FAMILY=1 
-I/build/renderdoc-1.27+
dfsg/renderdoc -I/build/renderdoc-1.27+dfsg/renderdoc/3rdparty -g -O2 
-ffile-prefix-map=/build/renderdoc-1.27+dfsg=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11
 -fno-strict-aliasing -fvisibility=hidden -fvisibility-inlines-hidden -Wall 
-Wextra -Wno-unused-variable -Wno-unused-parameter -Wno-unused-result 
-Wno-type-limits -Wno-missing-field-initializers -Wno-unknown-pragmas 
-Wno-reorder -Wno-unused-but-set-variable 
-Wno-maybe-uninitialized -Wno-class-memaccess -Wimplicit-fallthrough=2 
-Wno-unused-value -O3 -DNDEBUG -fPIC -MD -MT 
renderdoc/driver/shaders/spirv/CMakeFiles/rdoc_spirv.dir/glslang_compile.cpp.o 
-MF renderdoc/driver/shaders/spirv/CMakeFiles/rdoc_spirv.dir/gl
slang_compile.cpp.o.d -o 
renderdoc/driver/shaders/spirv/CMakeFiles/rdoc_spirv.dir/glslang_compile.cpp.o 
-c /build/renderdoc-1.27+dfsg/renderdoc/driver/shaders/spirv/glslang_compile.cpp
/build/renderdoc-1.27+dfsg/renderdoc/driver/shaders/spirv/glslang_compile.cpp:32:10:
 fatal error: glslang/Include/Types.h: No such file or directory
   32 | #include "glslang/Include/Types.h"
  |  ^
compilation terminated.

Andreas

Bug#1066095: llvm-18 is available in unstable, please also build spirv-llvm-translator-18 in unstable

[Andreas Beckmann]

Control: tag -1 pending

On 15/03/2024 15.33, Andreas Beckmann wrote:

On 15/03/2024 15.19, Matthias Klose wrote:
A quick build of the spirv-llvm-translator 18.1.0 release in sid (using 
llvm packages versioned 1:18.1.1-1) mostly succeeded, seems like I only 
need to update the symbols file ...


Package has been uploaded to unstable, but needs a detour via binary-NEW 
since there was a last-minute soversion bump (18 to 18.1) before 
upstream tagged v18.1.0 and I had to rename the library package again.



Andreas

Bug#932090: firebird3.0: Please include patch to ensure correct sizes of on-disk structures

[Thorsten Glaser]

John Paul Adrian Glaubitz dixit:

>However, it turns out that my approach is wrong and upstream has already used
>a different approach for firebird4.0 [2], although I haven't tested that on
>m68k yet.

>> [2] https://github.com/FirebirdSQL/firebird/pull/234/commits

(use https://github.com/FirebirdSQL/firebird/pull/234.patch in lynx)

Very much not; firebird3.0 also has that now AFAICT, and now the static
asserts fail.

The alignment assumptions must be made explicit: change something like…

struct foo {
char a;
int b;
};

… to:

struct foo {
char a;
char padding1[3];
int b;
};

bye,
//mirabilos
-- 
When he found out that the m68k port was in a pretty bad shape, he did
not, like many before him, shrug and move on; instead, he took it upon
himself to start compiling things, just so he could compile his shell.
How's that for dedication. -- Wouter, about my Debian/m68k revival

Bug#1067011: ITP: python-observabilityclient -- OpenStack Observability Client

[Thomas Goirand]

Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: python-observabilityclient
  Version : 0.1.1
  Upstream Contact: OpenStack Foundation 
* URL : https://infrawatch.github.io/documentation/
* License : Apache-2.0
  Programming Lang: Python
  Description : OpenStack Observability Client

 observabilityclient is an OpenStackClient (OSC) plugin implementation that
 implements commands for management of Prometheus.

This is a new dependency of OpenStack.

Bug#1062636: close

[Sudip Mukherjee]

Control: close -1
--

Closing this as the ABI is unaffected in time_t transition.

Adding irc chat for reference:

Mar 16 18:01:25 sudip: libsrm> it appears a later analysis 
showed the ABI was unaffected but we missed closing the bug so far, sorry. You 
can close it with this explanation (referencing 
https://adrien.dcln.fr/misc/armhf-time_t/2024-02-26T12%3A07%3A00/summary/results_none.txt
 if you wish)

-- 
Regards
Sudip

Bug#1067010: libsquashfuse-dev: Incompatible pointer types on 32-bit architectures

[Peter Wienemann]

Package: libsquashfuse-dev
Version: 0.5.0-2
Severity: serious
Tags: ftbfs fixed-upstream
Affects: src:charliecloud

Dear Maintainer,

squashfuse suffers from an incompatible pointer type issue on 32-bit
architectures. Checking the latest build logs for armel, armhf and
i386 ([0], [1], [2]) one finds the following warning:

ll_main.c: In function ‘main’:
ll_main.c:164:41: warning: assignment to ‘void (*)(struct fuse_req *, 
fuse_ino_t,  uint64_t)’ {aka ‘void (*)(struct fuse_req *, long long unsigned 
int,  long long unsigned int)’} from incompatible pointer type ‘void (*)(struct 
fuse_req *, fuse_ino_t,  long unsigned int)’ {aka ‘void (*)(struct fuse_req *, 
long long unsigned int,  long unsigned int)’} [-Wincompatible-pointer-types]
  164 | sqfs_ll_ops.forget  = sqfs_ll_op_forget;
  | ^

This incompatibility leads to an FTBFS issue for the charliecloud
package on 32-bit architectures (see e. g. [3]) since it is built
using the -Werror option.

It seems that this issue was fixed in upstream release 0.5.1 [4].

More background information on this issue can be obtained from the
corresponding Charliecloud upstream issue and PR ([5], [6]).

Best regards,

Peter

[0] 
https://buildd.debian.org/status/fetch.php?pkg=squashfuse=armel=0.5.0-2%2Bb1=1707534165=0
[1] 
https://buildd.debian.org/status/fetch.php?pkg=squashfuse=armhf=0.5.0-2%2Bb1=1707538322=0
[2] 
https://buildd.debian.org/status/fetch.php?pkg=squashfuse=i386=0.5.0-2%2Bb1=1707537260=0
[3] 
https://buildd.debian.org/status/fetch.php?pkg=charliecloud=armel=0.37-2=1710594551=log
[4] 
https://github.com/vasi/squashfuse/commit/cb148fc1477ed676049b7891ebb6efc90b2c00ec
[5] https://github.com/hpc/charliecloud/issues/1858
[6] https://github.com/hpc/charliecloud/pull/1859

Bug#1067009: lomiri-ui-toolkit: FTBFS: 63 failures which MUST be fixed

[Dmitry Shachnev]

Source: lomiri-ui-toolkit
Version: 1.3.5012+dfsg-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Control: block 1061179 by -1

Dear Maintainer,

As can be seen in [1], the package failed to build on buildds in unstable.

The relevant part is:

  /<>/tests/checkresults.sh /<>/tests/*.xml || exit 1;
  63 failures which MUST be fixed:
tst_scrollbar.13.qml
tst_scrollbar_header.13.qml
tst_scrollview.13.qml

The reasons why the tests failed can be found by searching for FAIL!.
E.g., the first test failed with this error:

  FAIL!  : components::Scrollbar::test_defaultStylingValues(vertical scrollbar) 
Uncaught exception: Cannot read property 'interactive' of null
 Loc: [/<>/tests/unit/visual/tst_scrollbar.13.qml(1187)]

[1]: https://buildd.debian.org/status/package.php?p=lomiri-ui-toolkit

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#1066887: Patch not sufficient

[M. Buecher]

Sorry, that was nonsense (assuming I was too tired), of course my local 
patch is overwritten by a package update.


On Fri, 15 Mar 2024 18:54:42 +0100 "M. Buecher" 
 wrote:


> Unfortunately enhancing `locale-gen` doesn't work during an package
> update via apt:
>
> ...
> Setting up locales (2.36-9+deb12u4) ...
> Generating locales (this might take a while)...
>   en_US.UTF-8... done
>   en_DE.UTF-8@INTL...[error] cannot open locale definition file
> `en_US@INTL': No such file or directory
>  done
>   en_US.UTF-8@INTL... done
> Generation complete.
> ...
>

Bug#1066195: a56: FTBFS: keybld.c:29:15: error: implicit declaration of function ‘gets’; did you mean ‘fgets’? [-Werror=implicit-function-declaration]

[Bastian Germann]

Control: tags -1 patch

Please find a patch attached.diff -Nru a56-1.3+dfsg/debian/changelog a56-1.3+dfsg/debian/changelog
--- a56-1.3+dfsg/debian/changelog   2024-01-13 22:00:00.0 +
+++ a56-1.3+dfsg/debian/changelog   2024-03-16 20:29:00.0 +
@@ -1,3 +1,11 @@
+a56 (1.3+dfsg-10.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use standard strtol.
+  * Fix a lot of implicit-function-declarations. (Closes: #1066195)
+
+ -- Bastian Germann   Sat, 16 Mar 2024 20:29:00 +
+
 a56 (1.3+dfsg-10) unstable; urgency=medium
 
   [ debian janitor ]
diff -Nru a56-1.3+dfsg/debian/patches/ansi-c.patch 
a56-1.3+dfsg/debian/patches/ansi-c.patch
--- a56-1.3+dfsg/debian/patches/ansi-c.patch1970-01-01 00:00:00.0 
+
+++ a56-1.3+dfsg/debian/patches/ansi-c.patch2024-01-13 22:00:00.0 
+
@@ -0,0 +1,170 @@
+Origin: 
https://github.com/rkujawa/a56/commit/68dacec16838a482264e67976b23310841bb539c
+From: =?UTF-8?q?Rados=C5=82aw=20Kujawa?= 
+Date: Fri, 17 May 2013 10:46:34 +0200
+Subject: More code cleanup and converstion to ANSI C.
+---
+diff --git a/frac2int.c b/frac2int.c
+index 8f01796..a045a70 100644
+--- a/frac2int.c
 b/frac2int.c
+@@ -98,21 +98,26 @@
+ * signed, fractional quantities.   *
+ \**/
+ 
+-main()
+-{
+-   double fractnum;  /* double precision floating pt */
+-   long   hexval;/* long integer */
+-
+-for(;;) {
+-/* Read 1 Decimal Floating Point Number from the Keyboard */
+-   printf("Enter the decimal fraction: ");
+-   scanf("%lf", );
++#include 
++#include 
+ 
+-/* Convert to a Hex Integer which can be used by the DSP56200 */
+-   hexval =  (long) (8388608.0 * fractnum);
+-   hexval =  0x00ffL & hexval;
+-
+-/* Write the Hex number out to the Terminal */
+-   printf("DSP56200 Coefficient = %06lx\n", hexval);
+-}
++int
++main(void)
++{
++  double fractnum;  /* double precision floating pt */
++  long   hexval;/* long integer */
++
++  for(;;) {
++  /* Read 1 Decimal Floating Point Number from the Keyboard */
++  printf("Enter the decimal fraction: ");
++  scanf("%lf", );
++
++  /* Convert to a Hex Integer which can be used by the DSP56200 */
++  hexval =  (long) (8388608.0 * fractnum);
++  hexval =  0x00ffL & hexval;
++
++  /* Write the Hex number out to the Terminal */
++  printf("DSP56200 Coefficient = %06lx\n", hexval);
++  }
++  return(EXIT_SUCCESS);
+ }
+diff --git a/main.c b/main.c
+index 06f6dc4..9d2aacf 100644
+--- a/main.c
 b/main.c
+@@ -21,6 +21,7 @@
+  */
+ #include 
+ #include 
++#include 
+ 
+ static char *Copyright = "Copyright (C) 1990-1994 Quinn C. Jensen";
+ 
+@@ -45,11 +46,12 @@ BOOL list_on_next = TRUE;
+ 
+ 
++void dump_symtab();
+ void summarize(struct psect *);
+ 
+ 
+ void psect_summary();
+ void reset_psects();
+ 
+ int
+ main(int argc, char *argv[])
+ {
+@@ -107,8 +111,8 @@ struct inc inc[MAX_NEST];
+ int inc_p = 0;
+ FILE *yyin;
+ 
+-include(file)
+-char *file;
++void
++include(char *file)
+ {
+   FILE *fp = open_read(file);
+ 
+@@ -205,7 +209,7 @@ sym_def(char *sym, int type, int seg, int i, double f)
+   sp->n.val.f = f;
+   } else {
+   sp = find_sym(sym);
+-  if(NOT sp)
++  if(!sp)
+   fatal("internal error 304\n");
+   if(sp->n.type != type ||
+   type == INT && sp->n.val.i != (i & 0xFF) ||
+@@ -214,8 +218,8 @@ sym_def(char *sym, int type, int seg, int i, double f)
+   }   
+ }
+ 
+-struct sym *find_sym(sym)
+-char *sym;
++struct sym *
++find_sym(char *sym)
+ {
+   struct sym *sp, **stop;
+ 
+@@ -228,6 +232,8 @@ char *sym;
+ }
+ 
+ extern char segs[];
++
++void
+ dump_symtab()
+ {
+   struct sym *sp, **stop;
+@@ -339,6 +345,7 @@ char *s;
+ 
+ #define ONE 0x400
+ 
++int
+ makefrac(char *s)
+ {
+   int frac = 0, div = 1;
+diff --git a/torom.c b/torom.c
+index afb79c2..cf19d5b 100644
+--- a/torom.c
 b/torom.c
+@@ -5,7 +5,7 @@
+  *  Written by Quinn C. Jensen
+  *  July 1990
+  *
+- ***\
++ ***/
+ 
+ /*
+  * Copyright (C) 1990-1994 Quinn C. Jensen
+@@ -27,12 +27,14 @@ static char *Copyright = "Copyright (C) 1990-1994 Quinn C. 
Jensen";
+  *
+  */
+ 
++#include 
++#include 
++
+ 
+ #define MAX 256
+ 
+-main(argc,argv)
+-int argc;
+-char *argv[];
++int
++main(int argc, char *argv[])
+ {
+   char buf[MAX];
+   int curaddr = 0;
+@@ -59,10 +61,11 @@ char *argv[];
+   }
+   }
+   }
++  return EXIT_SUCCESS;
+ }
+ 
+-putword(data)
+-int data;
++void 

Bug#1067008: qt6-base: please do not use firebird3.0 on m68k

[Thorsten Glaser]

Source: qt6-base
Version: 6.4.2+dfsg-21.1
X-Debbugs-Cc: t...@mirbsd.de, debian-...@lists.debian.org

firebird3.0 is not available on m68k because it invalidly assumes…

struct foo {
char a;
int b;
};

… that b is 32-bit aligned in this struct from implicit padding,
which neither C nor POSIX guarantee (on m68k, it is aligned 16 bit
due to the ABI spec) and this situation is the same as a decade ago.

It would be very helpful if qt6 (and qt5) could just not use this
database on m68k, as it’s hard to keep on top with manually fixing
these:

struct foo {
char a;
char dummy[3];
int b;
};

Thanks in advance!

Bug#1067006: rpc-statd.service: State 'stop-sigterm' timed out. Killing.

[Salvatore Bonaccorso]

Hi,

On Sat, Mar 16, 2024 at 08:13:44PM +0100, Harald Dunkel wrote:
> Package: nfs-common
> Version: 1:2.6.4-3
> 
> Restarting rpc-statd.service (e.g via needrestart at upgrade time)
> runs into a timeout:
> 
> Mar 16 20:06:58 lola.afaics.de systemd[1]: rpc-statd.service: State 
> 'stop-sigterm' timed out. Killing.
> Mar 16 20:06:58 lola.afaics.de systemd[1]: rpc-statd.service: Killing process 
> 2342 (rpc.statd) with signal SIGKILL.
> Mar 16 20:06:58 lola.afaics.de systemd[1]: rpc-statd.service: Main process 
> exited, code=killed, status=9/KILL
> Mar 16 20:06:58 lola.afaics.de systemd[1]: rpc-statd.service: Failed with 
> result 'timeout'.
> Mar 16 20:06:58 lola.afaics.de systemd[1]: Stopped rpc-statd.service - NFS 
> status monitor for NFSv2/3 locking..
> Mar 16 20:06:58 lola.afaics.de systemd[1]: Starting rpcbind.service - RPC 
> bind portmap service...
> Mar 16 20:06:58 lola.afaics.de systemd[1]: Started rpcbind.service - RPC bind 
> portmap service.
> Mar 16 20:06:58 lola.afaics.de systemd[1]: Starting rpc-statd.service - NFS 
> status monitor for NFSv2/3 locking
> Mar 16 20:06:58 lola.afaics.de rpc.statd[49886]: Version 2.6.4 starting
> Mar 16 20:06:58 lola.afaics.de rpc.statd[49886]: Flags: TI-RPC
> Mar 16 20:06:58 lola.afaics.de systemd[1]: Started rpc-statd.service - NFS 
> status monitor for NFSv2/3 locking..
> 
> Please reassign if necessary

I cannot reproduce this. If this was not a one-time off issue on your
system, do you have a way to reproduce the behaviour to further
investigate it?

Regards,
Salvatore

Bug#1067007: spamassassin: Insufficient test condition in /etc/cron.daily/spamassassin

[Bob Proulx]

Package: spamassassin
Version: 4.0.1~pre1-1
Severity: normal
Tags: patch

In this following commit systemd timers were introduced.


https://salsa.debian.org/debian/spamassassin/-/commit/f2753c72e8052f03e60c5a5532ccb4e1080b6406#b323bf39a23be9c27fd25690d333c4e9dbcddec7

In this following commit the test condition on line 24 was corrected.
Because multiple other programs now make use of that directory too and
the original test became insufficient.  This change implements the
corrected test condition.


https://salsa.debian.org/debian/spamassassin/-/commit/211e60e8bfec56f31e4fe54100438a6a899953fa

That was a good change.  But that fix and improvement was not applied
to line 34 a few lines further down which continued to have only the
previous condition test.

It would be most appreciated if the same change were applied to the
test on line 34 as well so that it would have the same behavior.  I am
certain that not applying the same fix there was simply an accidental
oversight.  To be explicit here is the proposed patch.

-if [ -d /run/systemd ] && [ ! -e /etc/spamassassin/skip-timer-conversion 
]; then
+if [ -d /run/systemd/system ] && [ ! -e 
/etc/spamassassin/skip-timer-conversion ]; then

I also wanted to say thank you and that I appreciate having the
skip-timer-conversion option available.  That's what I have been using
on my main system and that is why I have not been seeing this problem
on those systems.  But recently when setting up an additional system I
experienced the problem there with a fresh installation of the
spamassassin package.

Thank you for maintaining spamassassin!

Bob



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

Kernel: Linux 6.4.0-4-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Bug#1066112: weston: Enable support to libseat launcher in weston 10

[Carlos Henrique Lima Melara]

Hi, sorry for taking so long.

On Wed, Mar 13, 2024 at 05:42:29PM +0100, Dylan Aïssi wrote:
> Hi,
> 
> Le mer. 13 mars 2024 à 16:05, Carlos Henrique Lima Melara
>  a écrit :
> >
> > > I can try this week to prepare an updated package in a dedicated branch
> > > in salsa, so you can test it. Then, if everything is okay, we could fill
> > > the request to the release team.
> >
> > Sure, just let me know if you need help with anything and/or when the
> > packaging is ready for testing.
> 
> Ready for testing at:
> https://salsa.debian.org/xorg-team/wayland/weston/-/tree/debian-10.0
> I just realized the branch name is confusing...

So, I have good and bad news, but I guess they are mostly good.

THe bad news first, when I was checking the upstream commits, I saw some
changes in libweston.h which raised some flags about ABI incompatibilty
because they introduced some members in a publicly exposed struct. So I
set my feet on testing abi changes with abi-dumper +
abi-compliance-checker (it was my first time, that's why it took so
long).

The actually bad new is 08979a1 (from 10.0.4) [1] makes some problematic
changes in libweston.h:

--- a/include/libweston/libweston.h
+++ b/include/libweston/libweston.h
@@ -1289,6 +1289,7 @@ struct weston_view {
struct weston_surface *surface;
struct wl_list surface_link;
struct wl_signal destroy_signal;
+   struct wl_signal unmap_signal;

/* struct weston_paint_node::view_link */
struct wl_list paint_node_list;
@@ -1441,6 +1442,7 @@ struct weston_pointer_constraint {
bool hint_is_pending;

struct wl_listener pointer_destroy_listener;
+   struct wl_listener view_unmap_listener;
struct wl_listener surface_commit_listener;
struct wl_listener surface_activate_listener;
 };

This introduces an ABI incompatibility in libweston as caught by
abi-compliance-checker (report attached):

Comparing ABIs ...¬
Comparing APIs ...¬
Creating compatibility report ...¬
Binary compatibility: 77.8%¬
Source compatibility: 100%¬
Total binary compatibility problems: 1, warnings: 1¬
Total source compatibility problems: 0, warnings: 1¬
Report: compat_reports/libweston-10.so.dump/0_to_1/compat_report.html¬

I think this would get a solid NO from the release team (although I'm
not sure). Since the whole 10.0.4 release (the 4 commits) are related to
each other, I think we won't be able to pick it.

That said, I started testing with the 10.0.3 release (because if we
can't get the latest, let's try to get something at least). And the
results are good, we have 100% abi and api compatibility for all DSOs,
even internal ones.

Also, building the 10.0.3 (always with libseat launcher support
enabled), the build time tests give the same results (with 10.0.5 I was
getting slightly different results).

I also tested the libseat launcher and normal launcher and they both
work.

Finally, since the 10.0.5 patch release is only 1 commit, we can grab it
as a patch in the packaging side, so we would just miss the 10.0.4 patch
release.

Well, it was a long email, but the main takeway is 10.0.4 introduces an
ABI incompatibility and would be unsuitable for a proposed-update to
bookworm. But we can use the 10.0.3 release plus the only commit in
10.0.5 with libseat launcher support with 100% abi and api
compatibility.

What do you think?

> Best,
> Dylan

Cheers,
Charles
Title: libweston-10.so.dump: 0 to 1 compatibility report





API compatibility report for the libweston-10.so object between 0 and 1 versions on x86_64



BinaryCompatibility
SourceCompatibility

Test Info

Module Namelibweston-10.so.dump
Version #10
Version #21
Archx86_64
GCC Version12.2.0
SubjectBinary Compatibility

Test Results
Total Header Files26
Total Source Files27
Total Objects1
Total Symbols / Types352 / 259
Compatibility
77.8%


Problem Summary
SeverityCountAdded Symbols-0
Removed SymbolsHigh0
Problems withData TypesHigh0
Medium1
Low1
Problems withSymbolsHigh0
Medium0
Low0
Problems withConstantsLow0



Problems with Data Types, Medium Severity  1 
libweston.h

[+] struct weston_view  1 




Change
Effect
1
Field unmap_signal has been added at the middle position of this structural type.
1) Size of the inclusive type has been changed.2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications.



[+] affected symbols: 156 (44.3%)

linux_dmabuf_buffer_get ( struct wl_resource* resource )
Field 'retval.compositor.touch_calibrator.view' in the return value (pointer) has base type 'struct weston_view'.
linux_dmabuf_buffer_get_user_data ( struct linux_dmabuf_buffer* buffer )
Field 'buffer.compositor.touch_calibrator.view' in 1st parameter 'buffer' (pointer) has base type 'struct weston_view'.
linux_dmabuf_buffer_send_server_error ( struct linux_dmabuf_buffer* buffer, char const* msg )
Field 

Bug#1067005: libLLVM.so symbols are no longer versioned?

[Sylvestre Ledru]

Hello

I am aware and it is an upstream change; I need to adjust our package.

Cheers

Sylvestre


Le 16/03/2024 à 19:49, Roman Lebedev a écrit :
Package: libllvm18 > Version: 1:18.1.1-1 > Severity: serious > File: 
/usr/lib/llvm-18/lib/libLLVM.so.18.1, 
/usr/lib/x86_64-linux-gnu/libLLVM-17.so.1 > X-Debbugs-Cc: Sylvestre 
Ledru , Gianfranco Costamagna 
 >

I'm having a bit of a deja-vu here, because this exact kind of bug was
happening a while ago and was fixed, but looks like it's back?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846410
(same bugs happened in other distros too)

(TLDR: when two different libLLVM versions happen to [transitively] exist
within one running process, you may get weird segfaults.)

Could you please double-check that the symbols for the `libLLVM.so.18.1`
and `libLLVM-17.so.1` are versioned? If they are not, this bugs' severity
is actually Grave (and affecting at least LLVM17 too?)

Concretely, i'm hitting it when building halide package and then trying to
run it's tests with mesa's RustiCL implementation, llvmpipe driver.
To reproduce, `gbp buildpackage` on
https://salsa.debian.org/LebedevRI-guest/halide/-/commits/debian-opencl-FOR-BUGREPORT

Weirdly-enough, it happens when building the package,
but does not happen with manually hand-built halide.
```
$ export Halide_TARGET=host-opencl
$ export OCL_ICD_VENDORS=rusticl.icd
$ export RUSTICL_ENABLE=llvmpipe
$ gdb 
/build/halide-17.0.1-build/build/stage-2/halide/test/correctness/correctness_boundary_conditions 
-ex 'run' -ex 'thread apply all bt full'

GNU gdb (Debian 13.2-1+b1) 13.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 


This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from 
/build/halide-17.0.1-build/build/stage-2/halide/test/correctness/correctness_boundary_conditions...
Starting program: 
/build/halide-17.0.1-build/build/stage-2/halide/test/correctness/correctness_boundary_conditions 


[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffdce006c0 (LWP 172580)]
[New Thread 0x7fffdc4006c0 (LWP 172581)]
[New Thread 0x7fffdba006c0 (LWP 172582)]
[New Thread 0x7fffdb0006c0 (LWP 172583)]
[New Thread 0x7fffda6006c0 (LWP 172584)]
[New Thread 0x7fffd9c006c0 (LWP 172585)]
[New Thread 0x7fffd92006c0 (LWP 172586)]
[New Thread 0x7fffd3e006c0 (LWP 172587)]
[New Thread 0x7fffd34006c0 (LWP 172588)]
[New Thread 0x7fffd2a006c0 (LWP 172589)]
[New Thread 0x7fffd20006c0 (LWP 172590)]
[New Thread 0x7fffd16006c0 (LWP 172591)]
[New Thread 0x7fffd0c006c0 (LWP 172592)]
[New Thread 0x7fffc7e006c0 (LWP 172593)]
[New Thread 0x7fffc74006c0 (LWP 172594)]
[New Thread 0x7fffc6a006c0 (LWP 172595)]
[New Thread 0x7fffc60006c0 (LWP 172596)]
[New Thread 0x7fffc56006c0 (LWP 172597)]
[New Thread 0x7fffc4c006c0 (LWP 172598)]
[New Thread 0x7fffbbe006c0 (LWP 172599)]
[New Thread 0x7fffbb4006c0 (LWP 172600)]
[New Thread 0x7fffbaa006c0 (LWP 172601)]
[New Thread 0x7fffba0006c0 (LWP 172602)]
[New Thread 0x7fffb96006c0 (LWP 172603)]
[New Thread 0x7fffb8c006c0 (LWP 172604)]
[New Thread 0x7fffafe006c0 (LWP 172605)]
[New Thread 0x7fffaf4006c0 (LWP 172606)]
[New Thread 0x7fffaea006c0 (LWP 172607)]
[New Thread 0x7fffae0006c0 (LWP 172608)]
[New Thread 0x7fffad6006c0 (LWP 172609)]
[New Thread 0x7fffacc006c0 (LWP 172610)]
[New Thread 0x7fffa3e006c0 (LWP 172611)]
[New Thread 0x7fffa34006c0 (LWP 172612)]
[New Thread 0x7fffa2a006c0 (LWP 172613)]
[New Thread 0x7fffa20006c0 (LWP 172614)]
[New Thread 0x7fffa16006c0 (LWP 172615)]
[New Thread 0x7fffa0c006c0 (LWP 172616)]
[New Thread 0x7fff97e006c0 (LWP 172617)]
[New Thread 0x7fff974006c0 (LWP 172618)]
[New Thread 0x7fff96a006c0 (LWP 172619)]
[New Thread 0x7fff960006c0 (LWP 172620)]
[New Thread 0x7fff956006c0 (LWP 172621)]
[New Thread 0x7fff94c006c0 (LWP 172622)]
[New Thread 0x7fff8be006c0 (LWP 172623)]
[New Thread 0x7fff8b4006c0 (LWP 172624)]
[New Thread 0x7fff8aa006c0 (LWP 172625)]
[New Thread 0x7fff8a0006c0 (LWP 172626)]
[New Thread 0x7fff896006c0 (LWP 172627)]
[New Thread 0x7fff88c006c0 (LWP 172628)]
[New Thread 0x7fff7fe006c0 (LWP 172629)]
[New Thread 0x7fff7f4006c0 (LWP 172630)]
[New Thread 0x7fff7ea006c0 (LWP 172631)]
[New Thread 0x7fff7e0006c0 (LWP 172632)]
[New Thread 0x7fff7d6006c0 (LWP 172633)]
[New Thread 0x7fff7cc006c0 (LWP 172634)]
[New Thread 0x7fff73e006c0 (LWP 172635)]
[New Thread 0x7fff734006c0 (LWP 172636)]
[New Thread 

Bug#1067005: libLLVM.so symbols are no longer versioned?

[Roman Lebedev]

Package: libllvm18
Version: 1:18.1.1-1
Followup-For: Bug #1067005

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I've just tried building the halide package against LLVM17 (instead of LLVM18),
and the bug no longer happens, so it's, almost assuredly,
symbol versioning, in my opinion.

Roman.

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

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

Versions of packages libllvm18 depends on:
ii  libc6   2.37-15.1
ii  libedit23.1-20230828-1
ii  libffi8 3.4.6-1
ii  libgcc-s1   14-20240303-1
ii  libstdc++6  14-20240303-1
ii  libtinfo6   6.4+20240113-1
ii  libxml2 2.9.14+dfsg-1.3+b2
ii  libz3-4 4.8.12-3.1+b2
ii  libzstd11.5.5+dfsg2-2
ii  zlib1g  1:1.3.dfsg-3.1

libllvm18 recommends no packages.

libllvm18 suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE+UikBxeiu50LOdFYgbqkFMWfZdAFAmX17r8ACgkQgbqkFMWf
ZdAOfRAAhrbBZmyRc2L50yem1byb+cEwsv6aIPvc3zzAANGHjS7fH4s7fiiGX0zO
nRtJoGUS5eelfoRGSpRvVqxmj5djGZGTX9oz2m1sy1xEl350xnE2X4lX2KL835FE
GlLIefJFkmYhfrWACFRwNsxwOzv6g26xI0OZ+QickTgDtEPDH7O/nPEQR6vJkE2N
oIaP4+EZ3xGEFsf/RW/nw3g6faJQftB2Hf0Wqfn15Lnx1hyLM0ClFYd24fF9/dFl
hBcXqB2WMAfrSpstooHr5Oa6WOm2BZ/NTzt5SNl0nkVdmVJeF+T9d2mhMX/g+NmM
U8/87tOH6eS+ZARt8vZzhiW+C7935RDax6We9gg2CHGc9qemIBfBUagkkcHtoGoN
odbLLM91YcYK7xSd1yRS5Hacr8zAmKJEpgUE50RJpx62PcUaEqiGvAlgMs6mkDGZ
BgiiN+WUw+0ji+2B9RaWbh1asMDKJSsdicO8pSbnG3QsWReP7GAtYZcxrnmJGfUC
GfmCAVZ78fOb9TUNVA2Kb2qeD2CEeDZOsUlSmIkEJMszOo3dzibupHhfSm4KZ+QO
/nGiGmbcgGOMlslWXrY8dkYBNRs6UfpptEqLbxw702ePlB3knHKeCTrK9ugXDnr0
m+Ci6yu11O+39O4fz5Lah+317zUqdszJoDbEpJFmT9G/BGQUbgM=
=cI8R
-END PGP SIGNATURE-

Bug#1067006: rpc-statd.service: State 'stop-sigterm' timed out. Killing.

[Harald Dunkel]

Package: nfs-common
Version: 1:2.6.4-3

Restarting rpc-statd.service (e.g via needrestart at upgrade time)
runs into a timeout:

Mar 16 20:06:58 lola.afaics.de systemd[1]: rpc-statd.service: State 
'stop-sigterm' timed out. Killing.
Mar 16 20:06:58 lola.afaics.de systemd[1]: rpc-statd.service: Killing process 
2342 (rpc.statd) with signal SIGKILL.
Mar 16 20:06:58 lola.afaics.de systemd[1]: rpc-statd.service: Main process 
exited, code=killed, status=9/KILL
Mar 16 20:06:58 lola.afaics.de systemd[1]: rpc-statd.service: Failed with 
result 'timeout'.
Mar 16 20:06:58 lola.afaics.de systemd[1]: Stopped rpc-statd.service - NFS 
status monitor for NFSv2/3 locking..
Mar 16 20:06:58 lola.afaics.de systemd[1]: Starting rpcbind.service - RPC bind 
portmap service...
Mar 16 20:06:58 lola.afaics.de systemd[1]: Started rpcbind.service - RPC bind 
portmap service.
Mar 16 20:06:58 lola.afaics.de systemd[1]: Starting rpc-statd.service - NFS 
status monitor for NFSv2/3 locking
Mar 16 20:06:58 lola.afaics.de rpc.statd[49886]: Version 2.6.4 starting
Mar 16 20:06:58 lola.afaics.de rpc.statd[49886]: Flags: TI-RPC
Mar 16 20:06:58 lola.afaics.de systemd[1]: Started rpc-statd.service - NFS 
status monitor for NFSv2/3 locking..

Please reassign if necessary


Regards

Harri

Bug#1066137: gnupg1: fails to build gpgkeys_ldap, probably due to -Werror=implicit-function-declaration

[Thorsten Glaser]

Hi Andreas,

>Afaict ghostscript/fig2dev have stopped being blockers so I do not plan
>on doing another upload (with more work for the other autobuilders) just
>to temporarily disable these b-ds.

Indeed, that’s fine. But including that in the n̲e̲x̲t̲ upload
you do anyway would be nice.

Thanks,
//mirabilos
-- 
When he found out that the m68k port was in a pretty bad shape, he did
not, like many before him, shrug and move on; instead, he took it upon
himself to start compiling things, just so he could compile his shell.
How's that for dedication. -- Wouter, about my Debian/m68k revival

Bug#1065787: 64-bit time_t transition: cargo needs manual intervention

[Samuel Henrique]

On Sat, 16 Mar 2024 at 14:29, Simon McVittie  wrote:
> On Thu, 14 Mar 2024 at 22:03:57 -0700, Otto Kekäläinen wrote:
> > For example curl isn't building on armel/armhf now and numerous packages 
> > that
> > depend of curl are not building on armel/armhf.
>
> I believe a maintainer upload or NMU of #1066981 and #1066982 would
> now be enough to unblock curl, which would hopefully unblock a lot of
> the C/C++ ecosystem (in particular fixing the unsatisfiable dependency
> libdebuginfod1t64 -> libcurl3t64-gnutls on armel/armhf, which would allow
> gdb to be installed), while also making life easier for the people trying
> to re-bootstrap cargo.

I've uploaded curl 8.6.0-4 with the patches from #1066981 and #1066982, thank
you for those, Simon!

Cheers,

--
Samuel Henrique 

Bug#1067005: libLLVM.so symbols are no longer versioned?

[Roman Lebedev]

Package: libllvm18
Version: 1:18.1.1-1
Severity: serious
File: /usr/lib/llvm-18/lib/libLLVM.so.18.1, 
/usr/lib/x86_64-linux-gnu/libLLVM-17.so.1
X-Debbugs-Cc: Sylvestre Ledru , Gianfranco Costamagna 


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I'm having a bit of a deja-vu here, because this exact kind of bug was
happening a while ago and was fixed, but looks like it's back?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846410
(same bugs happened in other distros too)

(TLDR: when two different libLLVM versions happen to [transitively] exist
within one running process, you may get weird segfaults.)

Could you please double-check that the symbols for the `libLLVM.so.18.1`
and `libLLVM-17.so.1` are versioned? If they are not, this bugs' severity
is actually Grave (and affecting at least LLVM17 too?)

Concretely, i'm hitting it when building halide package and then trying to
run it's tests with mesa's RustiCL implementation, llvmpipe driver.
To reproduce, `gbp buildpackage` on
https://salsa.debian.org/LebedevRI-guest/halide/-/commits/debian-opencl-FOR-BUGREPORT

Weirdly-enough, it happens when building the package,
but does not happen with manually hand-built halide.
```
$ export Halide_TARGET=host-opencl
$ export OCL_ICD_VENDORS=rusticl.icd
$ export RUSTICL_ENABLE=llvmpipe
$ gdb 
/build/halide-17.0.1-build/build/stage-2/halide/test/correctness/correctness_boundary_conditions
 -ex 'run' -ex 'thread apply all bt full'
GNU gdb (Debian 13.2-1+b1) 13.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from 
/build/halide-17.0.1-build/build/stage-2/halide/test/correctness/correctness_boundary_conditions...
Starting program: 
/build/halide-17.0.1-build/build/stage-2/halide/test/correctness/correctness_boundary_conditions
 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffdce006c0 (LWP 172580)]
[New Thread 0x7fffdc4006c0 (LWP 172581)]
[New Thread 0x7fffdba006c0 (LWP 172582)]
[New Thread 0x7fffdb0006c0 (LWP 172583)]
[New Thread 0x7fffda6006c0 (LWP 172584)]
[New Thread 0x7fffd9c006c0 (LWP 172585)]
[New Thread 0x7fffd92006c0 (LWP 172586)]
[New Thread 0x7fffd3e006c0 (LWP 172587)]
[New Thread 0x7fffd34006c0 (LWP 172588)]
[New Thread 0x7fffd2a006c0 (LWP 172589)]
[New Thread 0x7fffd20006c0 (LWP 172590)]
[New Thread 0x7fffd16006c0 (LWP 172591)]
[New Thread 0x7fffd0c006c0 (LWP 172592)]
[New Thread 0x7fffc7e006c0 (LWP 172593)]
[New Thread 0x7fffc74006c0 (LWP 172594)]
[New Thread 0x7fffc6a006c0 (LWP 172595)]
[New Thread 0x7fffc60006c0 (LWP 172596)]
[New Thread 0x7fffc56006c0 (LWP 172597)]
[New Thread 0x7fffc4c006c0 (LWP 172598)]
[New Thread 0x7fffbbe006c0 (LWP 172599)]
[New Thread 0x7fffbb4006c0 (LWP 172600)]
[New Thread 0x7fffbaa006c0 (LWP 172601)]
[New Thread 0x7fffba0006c0 (LWP 172602)]
[New Thread 0x7fffb96006c0 (LWP 172603)]
[New Thread 0x7fffb8c006c0 (LWP 172604)]
[New Thread 0x7fffafe006c0 (LWP 172605)]
[New Thread 0x7fffaf4006c0 (LWP 172606)]
[New Thread 0x7fffaea006c0 (LWP 172607)]
[New Thread 0x7fffae0006c0 (LWP 172608)]
[New Thread 0x7fffad6006c0 (LWP 172609)]
[New Thread 0x7fffacc006c0 (LWP 172610)]
[New Thread 0x7fffa3e006c0 (LWP 172611)]
[New Thread 0x7fffa34006c0 (LWP 172612)]
[New Thread 0x7fffa2a006c0 (LWP 172613)]
[New Thread 0x7fffa20006c0 (LWP 172614)]
[New Thread 0x7fffa16006c0 (LWP 172615)]
[New Thread 0x7fffa0c006c0 (LWP 172616)]
[New Thread 0x7fff97e006c0 (LWP 172617)]
[New Thread 0x7fff974006c0 (LWP 172618)]
[New Thread 0x7fff96a006c0 (LWP 172619)]
[New Thread 0x7fff960006c0 (LWP 172620)]
[New Thread 0x7fff956006c0 (LWP 172621)]
[New Thread 0x7fff94c006c0 (LWP 172622)]
[New Thread 0x7fff8be006c0 (LWP 172623)]
[New Thread 0x7fff8b4006c0 (LWP 172624)]
[New Thread 0x7fff8aa006c0 (LWP 172625)]
[New Thread 0x7fff8a0006c0 (LWP 172626)]
[New Thread 0x7fff896006c0 (LWP 172627)]
[New Thread 0x7fff88c006c0 (LWP 172628)]
[New Thread 0x7fff7fe006c0 (LWP 172629)]
[New Thread 0x7fff7f4006c0 (LWP 172630)]
[New Thread 0x7fff7ea006c0 (LWP 172631)]
[New Thread 0x7fff7e0006c0 (LWP 172632)]
[New Thread 0x7fff7d6006c0 (LWP 172633)]
[New Thread 0x7fff7cc006c0 (LWP 172634)]
[New Thread 0x7fff73e006c0 (LWP 172635)]
[New Thread 0x7fff734006c0 (LWP 172636)]
[New Thread 0x7fff72a006c0 (LWP 172637)]
[New Thread 0x7fff720006c0 (LWP 172638)]
[New Thread 0x7fff716006c0 (LWP 172639)]

Bug#1067004: gmpc: no upstream maintainer

[Simon McVittie]

Source: gmpc
Severity: important
Tags: upstream wontfix
X-Debbugs-Cc: gmpc-plug...@packages.debian.org

It appears that gmpc no longer has any sort of upstream developer.
https://github.com/DaveDavenport/gmpc is specifically labelled as
unmaintained, https://repo.or.cz/w/gmpc.git hasn't been touched since 2015,
and the former maintainer's domains sarine.nl and gmpclient.org are
domain-parking placeholders.

I am already a single point of failure for too many things, so I am not
able to become the new upstream maintainer for this. Is there anyone else
in the mpd team who could?

Next time there is a problem that is not trivial to solve, we are
probably going to have to deprecate and remove this package, for example
in favour of sonata (which is also looking for a new maintainer, but at
least it still has somewhere for that announcement to appear).

smcv

Bug#1067003: howdoi: Please consider updating to recent upstream version v2.0.20

[Carl Johnson]

Package: howdoi
Version: 1.1.9-1.1
Severity: wishlist
X-Debbugs-Cc: kni9p...@anonaddy.me

Dear Maintainer,

howdoi is currently unusable as it is REALLY outdated (pls also see #1051370). 
A new upstream release would fix this as well as making new functionalities 
available.

Best Regards
Carl Johnson

-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.6.13+bpo-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.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 howdoi depends on:
ii  python3 3.11.2-1+b1
ii  python3-cssselect   1.2.0-2
ii  python3-lxml4.9.2-1+b1
ii  python3-pygments2.14.0+dfsg-1
ii  python3-pyquery 1.4.3-1
ii  python3-requests2.28.1+dfsg-1
ii  python3-requests-cache  0.9.8-1

howdoi recommends no packages.

howdoi suggests no packages.

-- no debconf information

Bug#1067002: plymouth: Theme broken if config file is a symlink

[Markus Koller]

Package: plymouth
Version: 24.004.60-1+b2
Severity: minor

Dear Maintainer,

I used to have a symlink from /etc/plymouth/plymouthd.conf to my
dotfiles repository, which resulted in a broken theme (a gray screen
with three white dots).

At some point I realized that the initramfs hook is copying the symlink
itself, so I switched to a hardlink which resolved that issue.

The problem is in /usr/share/initramfs-tools/hooks/plymouth which uses
`cp -dRp` to copy certain files. Could that be changed to `cp -p`
perhaps? I noticed that `cp -R` will still create symlinks when used
with a single file, but recursion isn't necessary in these cases anyway.

I also saw some other hooks explicitly use `cp -L`.

Thanks,
Markus


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

Kernel: Linux 6.7.9-1-liquorix-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages plymouth depends on:
ii  init-system-helpers  1.66
ii  initramfs-tools  0.142
ii  libc62.37-15.1
ii  libdrm2  2.4.120-2
ii  libplymouth5 24.004.60-1+b2
ii  systemd  255.4-1+b1
ii  udev 255.4-1+b1

plymouth recommends no packages.

Versions of packages plymouth suggests:
ii  desktop-base 12.0.6+nmu1
pn  plymouth-themes  

-- Configuration Files:
/etc/plymouth/plymouthd.conf changed:
[Daemon]
Theme=moonlight
ShowDelay=0


-- no debconf information

Bug#1067001: gdm3: Unable to log in after upgrade to 46~rc-1, works after reboot

[Paul Menzel]

Package: gdm3
Version: 46~rc-1
Severity: normal


Dear Debian folks,


Using Debian sid/unstable, I had a GNOME Shell Wayland session running, 
and *gdm3* was upgraded:


2024-03-16 16:30:46 upgrade gdm3:amd64 45.0.1-3+b1 46~rc-1

Then logging out, and wanting to log in again it hung indefinitely. 
First with GNOME Shell with X.Org and then another user with Wayland. 
Restarting the system, it worked again. I couldn’t spot anything in the 
logs. It looks like, the session was created successfully, but not 
switched to it or so.



Kind regards,

Paul


```
Mar 16 19:07:51 abreu (sd-pam)[1501]: pam_unix(systemd-user:session): 
session closed for user pmenzel
Mar 16 19:07:51 abreu systemd[1]: user@5272.service: Deactivated 
successfully.
Mar 16 19:07:51 abreu systemd[1]: Stopped user@5272.service - User 
Manager for UID 5272.
Mar 16 19:07:51 abreu systemd[1]: user@5272.service: Consumed 1h 7min 
2.208s CPU time, 8.6G memory peak, 0B memory swap peak.
Mar 16 19:07:51 abreu systemd[1]: Stopping user-runtime-dir@5272.service 
- User Runtime Directory /run/user/5272...
Mar 16 19:07:51 abreu systemd[1]: run-user-5272.mount: Deactivated 
successfully.
Mar 16 19:07:52 abreu systemd[1]: user-runtime-dir@5272.service: 
Deactivated successfully.
Mar 16 19:07:52 abreu systemd[1]: Stopped user-runtime-dir@5272.service 
- User Runtime Directory /run/user/5272.
Mar 16 19:07:52 abreu systemd[1]: Removed slice user-5272.slice - User 
Slice of UID 5272.
Mar 16 19:07:52 abreu systemd[1]: user-5272.slice: Consumed 1h 7min 
2.720s CPU time, 8.6G memory peak, 0B memory swap peak.
Mar 16 19:08:01 abreu gdm-password][20894]: gkr-pam: unable to locate 
daemon control file
Mar 16 19:08:01 abreu gdm-password][20894]: gkr-pam: stashed password to 
try later in open session
Mar 16 19:08:01 abreu gdm-password][20894]: 
pam_unix(gdm-password:session): session opened for user 
pmenzel(uid=5272) by pmenzel(uid=0)
Mar 16 19:08:01 abreu systemd[1]: Created slice user-5272.slice - User 
Slice of UID 5272.
Mar 16 19:08:01 abreu systemd[1]: Starting user-runtime-dir@5272.service 
- User Runtime Directory /run/user/5272...

Mar 16 19:08:01 abreu systemd-logind[780]: New session 22 of user pmenzel.
Mar 16 19:08:01 abreu systemd[1]: Finished user-runtime-dir@5272.service 
- User Runtime Directory /run/user/5272.
Mar 16 19:08:01 abreu systemd[1]: Starting user@5272.service - User 
Manager for UID 5272...
Mar 16 19:08:01 abreu (systemd)[20910]: pam_unix(systemd-user:session): 
session opened for user pmenzel(uid=5272) by pmenzel(uid=0)
Mar 16 19:08:02 abreu systemd[20910]: Queued start job for default 
target default.target.
Mar 16 19:08:02 abreu systemd[20910]: Created slice app.slice - User 
Application Slice.
Mar 16 19:08:02 abreu systemd[20910]: Created slice session.slice - User 
Core Session Slice.

Mar 16 19:08:02 abreu systemd[20910]: Reached target paths.target - Paths.
Mar 16 19:08:02 abreu systemd[20910]: Reached target timers.target - Timers.
Mar 16 19:08:02 abreu systemd[20910]: Starting dbus.socket - D-Bus User 
Message Bus Socket...
Mar 16 19:08:02 abreu systemd[20910]: Listening on dirmngr.socket - 
GnuPG network certificate management daemon.
Mar 16 19:08:02 abreu systemd[20910]: Listening on gcr-ssh-agent.socket 
- GCR ssh-agent wrapper.
Mar 16 19:08:02 abreu systemd[20910]: Listening on 
gnome-keyring-daemon.socket - GNOME Keyring daemon.
Mar 16 19:08:02 abreu systemd[20910]: Listening on 
gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase 
cache (access for web browsers).
Mar 16 19:08:02 abreu systemd[20910]: Listening on 
gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache 
(restricted).
Mar 16 19:08:02 abreu systemd[20910]: Listening on gpg-agent-ssh.socket 
- GnuPG cryptographic agent (ssh-agent emulation).
Mar 16 19:08:02 abreu systemd[20910]: Listening on gpg-agent.socket - 
GnuPG cryptographic agent and passphrase cache.
Mar 16 19:08:02 abreu systemd[20910]: Listening on pipewire-pulse.socket 
- PipeWire PulseAudio.
Mar 16 19:08:02 abreu systemd[20910]: Listening on pipewire.socket - 
PipeWire Multimedia System Sockets.
Mar 16 19:08:02 abreu systemd[20910]: Listening on 
pk-debconf-helper.socket - debconf communication socket.
Mar 16 19:08:02 abreu systemd[20910]: Listening on dbus.socket - D-Bus 
User Message Bus Socket.
Mar 16 19:08:02 abreu systemd[20910]: Reached target sockets.target - 
Sockets.
Mar 16 19:08:02 abreu systemd[20910]: Reached target basic.target - 
Basic System.
Mar 16 19:08:02 abreu systemd[1]: Started user@5272.service - User 
Manager for UID 5272.
Mar 16 19:08:02 abreu systemd[1]: Started session-22.scope - Session 22 
of User pmenzel.
Mar 16 19:08:02 abreu systemd[20910]: Started pipewire.service - 
PipeWire Multimedia Service.
Mar 16 19:08:02 abreu systemd[20910]: Started filter-chain.service - 
PipeWire filter chain daemon.
Mar 16 19:08:02 abreu systemd[20910]: Started wireplumber.service - 
Multimedia Service Session Manager.
Mar 16 19:08:02 abreu 

Bug#1063957: python-pytest-lazy-fixture: autopkgtest regression with pytest 8

[Sebastiaan Couwenberg]

The upstream repo shows no progress for two years,
affected packages should switch to alternatives.

Bug#1067000: ros-diagnostics ftbfs with Python 3.12

[Matthias Klose]

Package: src:ros-diagnostics
Version: 1.11.0+ds-4
Severity: important
Tags: sid trixie patch
User: debian-pyt...@lists.debian.org
Usertags: python3.12

tests fail with Python 3.12, patch at
http://launchpadlibrarian.net/719734251/ros-diagnostics_1.11.0+ds-4build4_1.11.0+ds-4ubuntu1.diff.gz

Bug#1066999: ros-vision-opencv ftbfs with Python 3.12

[Matthias Klose]

Package: src:ros-vision-opencv
Version: 1.16.2+ds-1
Severity: important
Tags: sid trixie patch
User: debian-pyt...@lists.debian.org
Usertags: python3.12

tests fail with Python 3.12, patch at
http://launchpadlibrarian.net/719733685/ros-vision-opencv_1.16.2+ds-1build4_1.16.2+ds-1ubuntu1.diff.gz

Bug#1066998: sift: FTBFS with -Werror=implicit-function-declaration

[Andreas Beckmann]

Source: sift
Version: 4.0.3b-6
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source

Hi,

sift TBFS with -Werror=implicit-function-declaration which was
recently enabled by default in dpkg 1.22.6 to support the 64-bit time_t
transition. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

make[2]: Entering directory '/build/sift-4.0.3b/src'
gcc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/build/sift-4.0.3b/src=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wno-unused-result -I/usr/include/blimps -O2 -D__MAKE_PREFIX__=\"/u
sr\" -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
choose_seqs_via_psiblastseedmedian.o choose_seqs_via_psiblastseedmedian.c
gcc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/build/sift-4.0.3b/src=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wno-unused-result -I/usr/include/blimps -O2 -D__MAKE_PREFIX__=\"/usr\" 
-Wdate-time -D_FORTIFY_SOURCE=2  -c -o clump_output_alignedseq.o 
clump_output_alignedseq.c
gcc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/build/sift-4.0.3b/src=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wno-unused-result -I/usr/include/blimps -O2 -D__MAKE_PREFIX__=\"/usr\" 
-Wdate-time -D_FORTIFY_SOURCE=2  -c -o consensus_to_seq.o consensus_to_seq.c
In file included from choose_seqs_via_psiblastseedmedian.c:20:
Matrix_Info.c: In function 'allow_min_and_above':
Matrix_Info.c:916:26: error: implicit declaration of function 
'min_aa_in_column' [-Werror=implicit-function-declaration]
  916 | min_aa = min_aa_in_column (matrix, pos);
  |  ^~~~
In file included from clump_output_alignedseq.c:23:
Matrix_Info.c: In function 'allow_min_and_above':
Matrix_Info.c:916:26: error: implicit declaration of function 
'min_aa_in_column' [-Werror=implicit-function-declaration]
  916 | min_aa = min_aa_in_column (matrix, pos);
  |  ^~~~
gcc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/build/sift-4.0.3b/src=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wno-unused-result -I/usr/include/blimps -O2 -D__MAKE_PREFIX__=\"/usr\" 
-Wdate-time -D_FORTIFY_SOURCE=2  -c -o info_on_seqs.o info_on_seqs.c
In file included from info_on_seqs.c:10:
Matrix_Info.c: In function 'allow_min_and_above':
Matrix_Info.c:916:26: error: implicit declaration of function 
'min_aa_in_column' [-Werror=implicit-function-declaration]
  916 | min_aa = min_aa_in_column (matrix, pos);
  |  ^~~~
cc1: some warnings being treated as errors
make[2]: *** [: choose_seqs_via_psiblastseedmedian.o] Error 1


Andreas

Bug#1066025: dh_installsystemd doesn't process user services in /usr/lib/systemd/user/

[Niels Thykier]

Control: tags -1 moreinfo

Niels Thykier:

Sergey Ponomarev:

debhelper package version: 13.11.6ubuntu1
Ubuntu 23.10 Mantic

Is there any plan for support of user services?
The user service is complicated by itself because it differs by commands
from system services.
That's why I also asked to make a review of mine scripts to have at least
one right example of this.


[...]


User services are handled by `dh_installsystemduser` (not 
`dh_installsystemd`) and that command used `/usr/lib` since the 
beginning as far as I can tell. That command was added in 10.9.1 and 
should be in the default sequence.


Best regards,
Niels




Hi Sergey,

I hope the above solved your issues.  If so, I will close this bug as 
resolved. :)


Best regards,
Niels

Bug#1064749: pymatgen: FTBFS: make[1]: *** [debian/rules:104: override_dh_auto_test] Error 1

[Drew Parsons]

Source: pymatgen
Followup-For: Bug #1064749
Control: tags -1 ftbfs

I can't reproduce this error.

See also

https://buildd.debian.org/status/fetch.php?pkg=pymatgen=amd64=2024.1.27%2Bdfsg1-7=1708967242=0
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/pymatgen_2024.1.27+dfsg1-7.rbuild.log.gz

https://ci.debian.net/data/autopkgtest/unstable/amd64/p/pymatgen/43357166/log.gz
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pymatgen/43355416/log.gz


test_quasiharmonic_debye_approx is passing on all systems.

I think we can close this bug.

Bug#1066997: mlterm cannot launch mlconfig because it doesn’t support --geometry

[Andrew Chadwick]

Package: mlterm
Version: 3.9.3-1+b1
Severity: important
Tags: a11y
X-Debbugs-Cc: a.t.chadw...@gmail.com

Dear Maintainer,

The mlconfig helper does not support --geometry, so it can’t be invoked by 
the user using its Ctrl+MouseButton3 binding, which tries to use this 
option. If mlterm is run from a different terminal, it instead prints the 
message “Unknown option --geometry” when this combination is pressed, 
without giving any other indication of what it’s trying to do. See the 
trace below for that detail.

I think that mlterm should invoke this command without --geometry, or the 
mlconfig helper should be patched to support the --geometry option. I can 
confirm that this functionality was working correctly under Debian 12’s 
version of mlterm and its supporting binaries.


   thanks for looking at this,
   Andrew

-- Trace for message:
$ rm -fr ~/.mlterm
$ strace -ff mlterm 2>&1 | grep geometry
[pid 136423] execve("mlconfig", ["mlconfig", "--geometry", "+1371+345", 
"--display", ":0.0"], 0x7fffd47338b8 /* 59 vars */) = -1 ENOENT (No such file 
or directory)
[pid 136423] execve("/usr/lib/x86_64-linux-gnu/mlterm/mlconfig", 
["/usr/lib/x86_64-linux-gnu/mlterm"..., "--geometry", "+1371+345", "--display", 
":0.0"], 0x7fffd47338b8 /* 59 vars */) = 0
[pid 136423] write(2, "Unknown option --geometry\n", 26Unknown option --geometry

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (5, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.15-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mlterm depends on:
ii  libc62.37-15
ii  libfreetype6 2.13.2+dfsg-1+b1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-3+b1
ii  libglib2.0-0 2.78.4-1
ii  libx11-6 2:1.8.7-1
ii  mlterm-common3.9.3-1+b1

Versions of packages mlterm recommends:
ii  mlterm-tools  3.9.3-1+b1

Versions of packages mlterm suggests:
pn  fonts-arphic-bsmi00lp 
pn  fonts-arphic-gbsn00lp 
ii  fonts-freefont-ttf20211204+svn4273-2
ii  fonts-ipafont-gothic [fonts-japanese-gothic]  00303-23
ii  fonts-nanum   20200506-1
pn  mlterm-im-m17nlib 
pn  mlterm-im-scim
pn  mlterm-im-uim 
pn  t1-cyrillic   
ii  unifont   1:15.1.01-1
pn  xfonts-efont-unicode  

-- no debconf information

Bug#1066146: morph's abandoned packages (list)

[Alexandre Detiste]

Hi,

The arguments to remove  flask-basicauth looks sensible, can someone confirm ?

CCing Daniele who uploads bespoken flask-login and Carsten who manage
whole flaks ecosystem.

Greetings

Le jeu. 14 mars 2024 à 07:20, Julian Gilbey  a écrit :
>
> Dear all (and Bcc-ing the RM bugs),
>
> For information, here is a list of packages that morph has either
> requested removal of or orphaned.  If you are interested in taking one
> or more of them on, that would be great!
>
> Removal requested:
>
> #1066146 RM: flask-basicauth -- ROM; RC buggy, dead upstream, leaf package

Bug#1066996: python-greenlet: Please add patch to support sh4

[John Paul Adrian Glaubitz]

Source: python-greenlet
Version: 3.0.1-3
Severity: normal
Tags: patch
User: debian-sup...@lists.debian.org
Usertags: sh4
X-Debbugs-Cc: debian-sup...@lists.debian.org

Hi,

the attached patch adds support for building python-greenlet on sh4, it's
a modified (fixed) version that is currently open for review upstream [1].

The fixed version can be found here [2].

Thanks,
Adrian

> [1] https://github.com/python-greenlet/greenlet/pull/398
> [2] 
> https://github.com/glaubitz/greenlet/commit/e73592dec7950ad9fcdb5c0287ef3758df010f11

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
>From e73592dec7950ad9fcdb5c0287ef3758df010f11 Mon Sep 17 00:00:00 2001
From: Pietro Monteiro 
Date: Wed, 6 Mar 2024 21:59:14 -0500
Subject: [PATCH] Add support for SuperH

---
 src/greenlet/platform/switch_sh_gcc.h | 36 +++
 src/greenlet/slp_platformselect.h |  2 ++
 2 files changed, 38 insertions(+)
 create mode 100644 src/greenlet/platform/switch_sh_gcc.h

diff --git a/src/greenlet/platform/switch_sh_gcc.h 
b/src/greenlet/platform/switch_sh_gcc.h
new file mode 100644
index 000..5ecc3b3
--- /dev/null
+++ b/src/greenlet/platform/switch_sh_gcc.h
@@ -0,0 +1,36 @@
+#define STACK_REFPLUS 1
+
+#ifdef SLP_EVAL
+#define STACK_MAGIC 0
+#define REGS_TO_SAVE "r8", "r9", "r10", "r11", "r13", \
+ "fr12", "fr13", "fr14", "fr15"
+
+// r12 Global context pointer, GP
+// r14 Frame pointer, FP
+// r15 Stack pointer, SP
+
+static int
+slp_switch(void)
+{
+int err;
+void* fp;
+int *stackref, stsizediff;
+__asm__ volatile("" : : : REGS_TO_SAVE);
+__asm__ volatile("mov.l r14, %0" : "=m"(fp) : :);
+__asm__("mov r15, %0" : "=r"(stackref));
+{
+SLP_SAVE_STATE(stackref, stsizediff);
+__asm__ volatile(
+"add %0, r15\n"
+"add %0, r14\n"
+: /* no outputs */
+: "r"(stsizediff));
+SLP_RESTORE_STATE();
+__asm__ volatile("mov r0, %0" : "=r"(err) : :);
+}
+__asm__ volatile("mov.l %0, r14" : : "m"(fp) :);
+__asm__ volatile("" : : : REGS_TO_SAVE);
+return err;
+}
+
+#endif
diff --git a/src/greenlet/slp_platformselect.h 
b/src/greenlet/slp_platformselect.h
index c959f0f..8a77328 100644
--- a/src/greenlet/slp_platformselect.h
+++ b/src/greenlet/slp_platformselect.h
@@ -64,6 +64,8 @@ extern "C" {
 # include "platform/switch_aarch64_gcc.h" /* LLVM Aarch64 ABI for Windows */
 #elif defined(__GNUC__) && defined(__loongarch64) && defined(__linux__)
 # include "platform/switch_loongarch64_linux.h" /* LoongArch64 */
+#elif defined(__GNUC__) && defined(__sh__)
+# include "platform/switch_sh_gcc.h" /* SuperH */
 #endif
 
 #ifdef __cplusplus
-- 
2.44.0

Bug#1066995: pulseaudio: FTBFS with _TIME_BITS=64 on 32-bit systems

[John Paul Adrian Glaubitz]

Source: pulseaudio
Version: 16.1+dfsg1-3
Severity: serious
Tags: upstream
Justification: ftbfs
User: debian-powe...@lists.debian.org
Usertags: powerpc
X-Debbugs-Cc: debian-powe...@lists.debian.org

Hi,

pulseaudio fails to built from source with _TIME_BITS=64 [1]:

[632/648] cc -Isrc/utils/libpulsedsp.so.p -Isrc/utils -I../src/utils -I. -I.. 
-Isrc -I../src -fdiagnostics-color=always -Wall -Winvalid-pch -std=gnu11 -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-pthread -DHAVE_CONFIG_H -D_GNU_SOURCE -Wno-nonnull-compare -MD -MQ 
src/utils/libpulsedsp.so.p/padsp.c.o -MF src/utils/libpulsedsp.so.p/padsp.c.o.d 
-o src/utils/libpulsedsp.so.p/padsp.c.o -c ../src/utils/padsp.c
FAILED: src/utils/libpulsedsp.so.p/padsp.c.o 
cc -Isrc/utils/libpulsedsp.so.p -Isrc/utils -I../src/utils -I. -I.. -Isrc 
-I../src -fdiagnostics-color=always -Wall -Winvalid-pch -std=gnu11 -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-pthread -DHAVE_CONFIG_H -D_GNU_SOURCE -Wno-nonnull-compare -MD -MQ 
src/utils/libpulsedsp.so.p/padsp.c.o -MF src/utils/libpulsedsp.so.p/padsp.c.o.d 
-o src/utils/libpulsedsp.so.p/padsp.c.o -c ../src/utils/padsp.c
In file included from /usr/include/features.h:393,
 from /usr/include/endian.h:21,
 from /usr/include/linux/soundcard.h:43,
 from /usr/include/powerpc-linux-gnu/sys/soundcard.h:1,
 from ../src/utils/padsp.c:33:
/usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed 
only with _FILE_OFFSET_BITS=64"
   26 | #   error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
  | ^

This needs to be fixed for the time_t transition [2].

Thanks,
Adrian

> [1] 
> https://buildd.debian.org/status/fetch.php?pkg=pulseaudio=powerpc=16.1%2Bdfsg1-3%2Bb1=1710500596=0
> [2] https://wiki.debian.org/ReleaseGoals/64bit-time

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; nice-level = -11

; realtime-scheduling = yes
; realtime-priority = 5

; exit-idle-time = 20
; scache-idle-time = 20

; dl-search-path = (depends on architecture)

; load-default-script-file = yes
; default-script-file = /etc/pulse/default.pa

; log-target = auto
; 

Bug#1066994: RM: libjconv -- RoQA; orphaned; dead upstream; RC-buggy; leaf library

[Andrey Rahmatullin]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: libjc...@packages.debian.org
Control: affects -1 + src:libjconv
User: ftp.debian@packages.debian.org
Usertags: remove

Last (the only) upstream upload 2001, last maintainer upload 2001, orphaned
since 2007. The upstream doesn't seem to exist anymore. While the description
says "it is used as helper in sylpheed mailer", sylpheed actually dropped it in
2003.
Currently FTBFS with -Werror=implicit-function-declaration.

wrar@coccia:~$ dak rm -Rn libjconv
Will remove the following packages from unstable:

  libjconv |  2.8-7 | source
libjconv-bin |  2.8-7 | riscv64
libjconv-bin |   2.8-7+b1 | amd64, arm64, armel, armhf, i386, mips64el,
ppc64el, s390x
libjconv-dev |  2.8-7 | riscv64
libjconv-dev |   2.8-7+b1 | amd64, arm64, armel, armhf, i386, mips64el,
ppc64el, s390x
 libjconv2 |  2.8-7 | riscv64
 libjconv2 |   2.8-7+b1 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el,
s390x

Maintainer: Debian QA Group 

--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.

Bug#1066993: RM: libpcl1 -- RoQA; orphaned; dead upstream; RC-buggy; leaf library

[Andrey Rahmatullin]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: libp...@packages.debian.org
Control: affects -1 + src:libpcl1
User: ftp.debian@packages.debian.org
Usertags: remove

Last upstream release 2010, orphaned since 2016 (but last maintainer upload
2006), FTBFS with -Werror=implicit-function-declaration.

wrar@coccia:~$ dak rm -Rn libpcl1
Will remove the following packages from unstable:

   libpcl1 | 1.12-2 | source, amd64, arm64, armel, armhf, i386, mips64el,
ppc64el, riscv64, s390x
libpcl1-dev | 1.12-2 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el,
riscv64, s390x

Maintainer: Debian QA Group 

--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.

Bug#1066992: search crashes since python3-urwid 2.3.4-0.1

[Ryan Kavanagh]

Package: urlscan
Version: 0.9.9-1
Severity: normal
X-Debbugs-Cc: r...@debian.org

urlscan has a keybinding '/' for search. However, attempting to search
by pressing / causes urlscan to crash with the traceback below.
Downgrading python3-urwid to 2.1.2-4.2 fixes this bug. I can reproduce
the crash with every python3-urwid version since 2.3.4-0.1.

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/urwid/event_loop/main_loop.py", line 
435, in _run
self.start()
  File "/usr/lib/python3/dist-packages/urwid/event_loop/main_loop.py", line 
400, in start
raise CantUseExternalLoop(f"Screen {self.screen!r} doesn't support external 
event loops")
urwid.event_loop.main_loop.CantUseExternalLoop: Screen 
 doesn't support external 
event loops

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/urlscan", line 33, in 
sys.exit(load_entry_point('urlscan==0.9.9', 'console_scripts', 'urlscan')())
 ^^
  File "/usr/lib/python3/dist-packages/urlscan/__main__.py", line 185, in main
tui.main()
  File "/usr/lib/python3/dist-packages/urlscan/urlchoose.py", line 262, in main
self.loop.run()
  File "/usr/lib/python3/dist-packages/urwid/event_loop/main_loop.py", line 
342, in run
self._run()
  File "/usr/lib/python3/dist-packages/urwid/event_loop/main_loop.py", line 
438, in _run
self._run_screen_event_loop()
  File "/usr/lib/python3/dist-packages/urwid/event_loop/main_loop.py", line 
509, in _run_screen_event_loop
self.process_input(keys)
  File "/usr/lib/python3/dist-packages/urwid/event_loop/main_loop.py", line 
594, in process_input
something_handled |= bool(self.unhandled_input(k))
  ^^^
  File "/usr/lib/python3/dist-packages/urwid/event_loop/main_loop.py", line 
640, in unhandled_input
return self._unhandled_input(data)
   ^^^
  File "/usr/lib/python3/dist-packages/urlscan/urlchoose.py", line 338, in 
unhandled
self.keys[key]()
  File "/usr/lib/python3/dist-packages/urlscan/urlchoose.py", line 473, in 
_search_key
self._search()
  File "/usr/lib/python3/dist-packages/urlscan/urlchoose.py", line 696, in 
_search
if isinstance(col[0], urwid.decoration.AttrMap):
  
  File "/usr/lib/python3/dist-packages/urwid/__init__.py", line 333, in 
__getattr__
raise AttributeError(f"{name} not found in {__package__}")
AttributeError: decoration not found in urwid
Press any key to continue...


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

Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8), LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages urlscan depends on:
ii  python33.11.6-1
ii  python3-urwid  2.6.4-1

urlscan recommends no packages.

Versions of packages urlscan suggests:
ii  chromium [www-browser] 122.0.6261.57-1
ii  firefox [www-browser]  123.0-1
ii  links2 [www-browser]   2.29-1+b1
ii  lynx [www-browser] 2.9.0rel.0-2
ii  neomutt20231103+dfsg1-1
ii  qutebrowser [www-browser]  2.5.4-2
ii  w3m [www-browser]  0.5.3+git20230121-2+b2

-- no debconf information

-- 
|)|/  Ryan Kavanagh  | 4E46 9519 ED67 7734 268F
|\|\  https://rak.ac | BD95 8F7B F8FC 4A11 C97A


signature.asc
Description: PGP signature

Bug#1066991: easy way to crash diffoscope

[Holger Levsen]

package: diffoscope
version: 240

hi,

crashing diffoscope in under 2min (the package build takes 42sec here).

$ apt source golang-github-stvp-tempredis 
$ sudo pbuilder build golang-github-stvp-tempredis_0.0~git20231107.8a695b6-1.dsc
$ mkdir p1 ; mv /var/cache/pbuilder/unstable/result/* p1/
$ sudo pbuilder build golang-github-stvp-tempredis_0.0~git20231107.8a695b6-1.dsc
$ mkdir p2 ; mv /var/cache/pbuilder/unstable/result/* p2/
$ diffoscope 
p1/golang-github-stvp-tempredis_0.0~git20231107.8a695b6-1_amd64.changes 
p2/golang-github-stvp-tempredis_0.0~git20231107.8a695b6-1_amd64.changes 
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/diffoscope/main.py", line 767, in main
sys.exit(run_diffoscope(parsed_args))
 ^^^
  File "/usr/lib/python3/dist-packages/diffoscope/main.py", line 718, in 
run_diffoscope
difference = compare_root_paths(path1, path2)
 
  File 
"/usr/lib/python3/dist-packages/diffoscope/comparators/utils/compare.py", line 
69, in compare_root_paths
difference = compare_files(file1, file2)
 ^^^
  File 
"/usr/lib/python3/dist-packages/diffoscope/comparators/utils/compare.py", line 
149, in compare_files
return file1.compare(file2, source)
   
  File "/usr/lib/python3/dist-packages/diffoscope/comparators/debian.py", line 
275, in compare
differences = super().compare(other, *args, **kwargs)
  ^^^
  File "/usr/lib/python3/dist-packages/diffoscope/comparators/utils/file.py", 
line 532, in compare
difference = self._compare_using_details(other, source)
 ^^
  File "/usr/lib/python3/dist-packages/diffoscope/comparators/utils/file.py", 
line 467, in _compare_using_details
details.extend(
  File 
"/usr/lib/python3/dist-packages/diffoscope/comparators/utils/container.py", 
line 197, in compare_pair
difference = compare_files(
 ^^
  File 
"/usr/lib/python3/dist-packages/diffoscope/comparators/utils/compare.py", line 
149, in compare_files
return file1.compare(file2, source)
   
  File "/usr/lib/python3/dist-packages/diffoscope/comparators/utils/file.py", 
line 532, in compare
difference = self._compare_using_details(other, source)
 ^^
  File "/usr/lib/python3/dist-packages/diffoscope/comparators/utils/file.py", 
line 467, in _compare_using_details
details.extend(
  File 
"/usr/lib/python3/dist-packages/diffoscope/comparators/utils/container.py", 
line 197, in compare_pair
difference = compare_files(
 ^^
  File 
"/usr/lib/python3/dist-packages/diffoscope/comparators/utils/compare.py", line 
149, in compare_files
return file1.compare(file2, source)
   
  File "/usr/lib/python3/dist-packages/diffoscope/comparators/utils/file.py", 
line 532, in compare
difference = self._compare_using_details(other, source)
 ^^
  File "/usr/lib/python3/dist-packages/diffoscope/comparators/utils/file.py", 
line 467, in _compare_using_details
details.extend(
  File 
"/usr/lib/python3/dist-packages/diffoscope/comparators/utils/container.py", 
line 197, in compare_pair
difference = compare_files(
 ^^
  File 
"/usr/lib/python3/dist-packages/diffoscope/comparators/utils/compare.py", line 
149, in compare_files
return file1.compare(file2, source)
   
  File "/usr/lib/python3/dist-packages/diffoscope/comparators/utils/file.py", 
line 532, in compare
difference = self._compare_using_details(other, source)
 ^^
  File "/usr/lib/python3/dist-packages/diffoscope/comparators/utils/file.py", 
line 467, in _compare_using_details
details.extend(
  File 
"/usr/lib/python3/dist-packages/diffoscope/comparators/utils/container.py", 
line 197, in compare_pair
difference = compare_files(
 ^^
  File 
"/usr/lib/python3/dist-packages/diffoscope/comparators/utils/compare.py", line 
149, in compare_files
return file1.compare(file2, source)
   
  File "/usr/lib/python3/dist-packages/diffoscope/comparators/utils/file.py", 
line 532, in compare
difference = self._compare_using_details(other, source)
 ^^
  File "/usr/lib/python3/dist-packages/diffoscope/comparators/utils/file.py", 
line 433, in _compare_using_details
details.extend(self.compare_details(other, source))
   ^^^
  File "/usr/lib/python3/dist-packages/diffoscope/comparators/rdata.py", line 
166, in 

Bug#1066487: libgpiv: FTBFS: ../../lib/img.c:939:16: error: implicit declaration of function ‘gets’; did you mean ‘fgets’? [-Werror=implicit-function-declaration]

[Andrey Rakhmatullin]

On Wed, Mar 13, 2024 at 12:52:19PM +0100, Lucas Nussbaum wrote:
> > ../../lib/img.c: In function ‘gpiv_img_read_header’:
> > ../../lib/img.c:939:16: error: implicit declaration of function ‘gets’; did 
> > you mean ‘fgets’? [-Werror=implicit-function-declaration]
> >   939 | while (gets (line) != NULL) {
The proper fix would be to rewrite all related code to stop using gets(),
but this is a dead library with no revdeps so I requested an RM instead.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#1066990: RM: libgpiv -- RoQA; orphaned; dead upstream; RC-buggy; leaf library

[Andrey Rahmatullin]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: libg...@packages.debian.org
Control: affects -1 + src:libgpiv
User: ftp.debian@packages.debian.org
Usertags: remove

It now FTBFS with -Werror=implicit-function-declaration because it uses
gets(3).

Last upstream release 2008, orphaned since 2016.


wrar@coccia:~$ dak rm -Rn libgpiv
Will remove the following packages from unstable:

   libgpiv |  0.6.1-7.1 | source
   libgpiv |  0.6.1-7.2 | source
libgpiv-mpi3 | 0.6.1-7.1+b2 | armel, armhf
libgpiv-mpi3t64 |  0.6.1-7.2 | amd64, arm64, i386, mips64el, ppc64el, riscv64,
s390x
  libgpiv3 | 0.6.1-7.1+b2 | armel, armhf
libgpiv3-common | 0.6.1-7.1+b2 | armel, armhf
libgpiv3-common |  0.6.1-7.2 | amd64, arm64, i386, mips64el, ppc64el, riscv64,
s390x
libgpiv3-dev | 0.6.1-7.1+b2 | armel, armhf
libgpiv3-dev |  0.6.1-7.2 | amd64, arm64, i386, mips64el, ppc64el, riscv64,
s390x
libgpiv3-doc |  0.6.1-7.1 | all
libgpiv3-doc |  0.6.1-7.2 | all
libgpiv3t64 |  0.6.1-7.2 | amd64, arm64, i386, mips64el, ppc64el, riscv64,
s390x

Maintainer: Debian QA Group 

--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.

Bug#1066210: libfreefare: diff for NMU version 0.4.0-2.3

[Andrey Rakhmatullin]

Control: tags 1066210 + patch
Control: tags 1066210 + pending

Dear maintainer,

I've prepared an NMU for libfreefare (versioned as 0.4.0-2.3) and
uploaded it to unstable.

Regards.


-- 
WBR, wRAR
diff -Nru libfreefare-0.4.0/debian/changelog libfreefare-0.4.0/debian/changelog
--- libfreefare-0.4.0/debian/changelog	2024-03-01 17:21:18.0 +0500
+++ libfreefare-0.4.0/debian/changelog	2024-03-16 20:28:25.0 +0500
@@ -1,3 +1,10 @@
+libfreefare (0.4.0-2.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066210).
+
+ -- Andrey Rakhmatullin   Sat, 16 Mar 2024 20:28:25 +0500
+
 libfreefare (0.4.0-2.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libfreefare-0.4.0/debian/patches/fix-implicit-function-declaration.patch libfreefare-0.4.0/debian/patches/fix-implicit-function-declaration.patch
--- libfreefare-0.4.0/debian/patches/fix-implicit-function-declaration.patch	1970-01-01 05:00:00.0 +0500
+++ libfreefare-0.4.0/debian/patches/fix-implicit-function-declaration.patch	2024-03-16 20:28:25.0 +0500
@@ -0,0 +1,15 @@
+Description: Add missing header includes.
+Author: Andrey Rakhmatullin 
+Bug-Debian: https://bugs.debian.org/1066210
+Last-Update: 2024-03-16
+
+--- libfreefare-0.4.0.orig/libfreefare/mifare_desfire_crypto.c
 libfreefare-0.4.0/libfreefare/mifare_desfire_crypto.c
+@@ -59,6 +59,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ #ifdef WITH_DEBUG
+ #  include 
diff -Nru libfreefare-0.4.0/debian/patches/series libfreefare-0.4.0/debian/patches/series
--- libfreefare-0.4.0/debian/patches/series	1970-01-01 05:00:00.0 +0500
+++ libfreefare-0.4.0/debian/patches/series	2024-03-16 20:28:25.0 +0500
@@ -0,0 +1 @@
+fix-implicit-function-declaration.patch


signature.asc
Description: PGP signature

Bug#1065787: 64-bit time_t transition: cargo needs manual intervention

[Emanuele Rocca]

Hi!

On 2024-03-16 02:29, Simon McVittie wrote:
> On Thu, 14 Mar 2024 at 22:03:57 -0700, Otto Kekäläinen wrote:
> > For example curl isn't building on armel/armhf now and numerous packages 
> > that
> > depend of curl are not building on armel/armhf.
> 
> I believe a maintainer upload or NMU of #1066981 and #1066982 would
> now be enough to unblock curl, which would hopefully unblock a lot of
> the C/C++ ecosystem (in particular fixing the unsatisfiable dependency
> libdebuginfod1t64 -> libcurl3t64-gnutls on armel/armhf, which would allow
> gdb to be installed), while also making life easier for the people trying
> to re-bootstrap cargo.

Thanks Simon. I can confirm that curl does indeed build properly on
armhf with DEB_BUILD_PROFILES='pkg.curl.noldap nocheck'.

With libcurl3t64-gnutls cargo can now be rebootstrapped on armhf
(haven't tried armel yet). See https://people.debian.org/~ema/cargo/ for
the debs. I've included installable curl packages there too in case
someone else wants to give it a go.

Fabian: it seems that cargo's build-depend on git can be dropped? The
package builds fine without, tests included.

Bug#1066556: libdrpm: diff for NMU version 0.5.1-1.1

[Andrey Rakhmatullin]

Control: tags 1066556 + patch
Control: tags 1066556 + pending

Dear maintainer,

I've prepared an NMU for libdrpm (versioned as 0.5.1-1.1) and
uploaded it to DELAYED/4. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
WBR, wRAR
diff -Nru libdrpm-0.5.1/debian/changelog libdrpm-0.5.1/debian/changelog
--- libdrpm-0.5.1/debian/changelog	2022-09-09 11:08:12.0 +0500
+++ libdrpm-0.5.1/debian/changelog	2024-03-16 20:17:44.0 +0500
@@ -1,3 +1,10 @@
+libdrpm (0.5.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066556).
+
+ -- Andrey Rakhmatullin   Sat, 16 Mar 2024 20:17:44 +0500
+
 libdrpm (0.5.1-1) unstable; urgency=medium
 
   * Declare compliance with Policy 4.6.1 with no changes.
diff -Nru libdrpm-0.5.1/debian/patches/fix-implicit-function-declaration.patch libdrpm-0.5.1/debian/patches/fix-implicit-function-declaration.patch
--- libdrpm-0.5.1/debian/patches/fix-implicit-function-declaration.patch	1970-01-01 05:00:00.0 +0500
+++ libdrpm-0.5.1/debian/patches/fix-implicit-function-declaration.patch	2024-03-16 20:17:44.0 +0500
@@ -0,0 +1,15 @@
+Description: Add missing header includes.
+Author: Andrey Rakhmatullin 
+Bug-Debian: https://bugs.debian.org/1066556
+Last-Update: 2024-03-16
+
+--- libdrpm-0.5.1.orig/src/drpm_write.c
 libdrpm-0.5.1/src/drpm_write.c
+@@ -24,6 +24,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include 
+ #include 
+ #include 
diff -Nru libdrpm-0.5.1/debian/patches/series libdrpm-0.5.1/debian/patches/series
--- libdrpm-0.5.1/debian/patches/series	2022-09-09 11:08:12.0 +0500
+++ libdrpm-0.5.1/debian/patches/series	2024-03-16 20:17:44.0 +0500
@@ -1 +1,2 @@
 openssl-evp.patch
+fix-implicit-function-declaration.patch


signature.asc
Description: PGP signature

Bug#1066531: policykit-1: FTBFS: ../subprojects/mocklibc-1.0/src/netgroup-debug.c:25:3: error: implicit declaration of function ‘print_indent’ [-Werror=implicit-function-declaration]

[Michael Biebl]

Am 15.03.24 um 19:55 schrieb Michael Biebl:

Control: tags -1 - patch

On Wed, 13 Mar 2024 13:01:49 + Mark Hindley  
wrote:

Control: tags -1 patch

I also bumped into this whilst rebuilding src:policykit-1 yesterday.

There is an upstream patch[1], but it doesn't fix the build for me; I 
think it

is patching the wrong files.The problem appears to be multiple copies of
mocklibc. AFAICS ./test/mocklibc is not used in favour of a meson 
subproject.


The pkla-compat tarball also has mocklibc, but that is also patched 
already.


We should drop pkla-compat in trixie. But that is a separate issue.


Getting the multiple layers of quilt and meson patches to work was
unpleasant. So the attached patch may save you some time.

HTH

Mark

[1]  
https://github.com/polkit-org/polkit/commit/0d78d1e4bf5ab3ce11678005b220aac0cfc5bee5




Thanks for the patch
Unfortunately it fails to apply to the src:policykit-1 package as 
shipped in Debian sid. Thus marking the bug report accordingly.




Thanks for hint regarding diff_files for wrapped Meson projects.

I've submitted this upstream as 
https://github.com/polkit-org/polkit/pull/436


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1063266: polylib: NMU diff for 64-bit time_t transition

[Andrey Rakhmatullin]

Hello. I see this wasn't uploaded to sid yet, in the mean time I'm
uploading a different NMU to sid that fixes the FTBFS #1066303 so please
make sure this one doesn't override that one (and if that FTBFS was
blocking something it should be unblocked after the fix is uploaded and
built).


-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#1066303: polylib: diff for NMU version 5.22.5-4.1+dfsg

[Andrey Rakhmatullin]

Control: tags 1066303 + patch
Control: tags 1066303 + pending

Dear maintainer,

I've prepared an NMU for polylib (versioned as 5.22.5-4.1+dfsg) and
uploaded it to unstable.

Regards.


-- 
WBR, wRAR
diff -Nru polylib-5.22.5/debian/changelog polylib-5.22.5/debian/changelog
--- polylib-5.22.5/debian/changelog	2018-01-26 20:47:38.0 +0500
+++ polylib-5.22.5/debian/changelog	2024-03-16 20:05:30.0 +0500
@@ -1,3 +1,10 @@
+polylib (5.22.5-4.1+dfsg) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066303).
+
+ -- Andrey Rakhmatullin   Sat, 16 Mar 2024 20:05:30 +0500
+
 polylib (5.22.5-4+dfsg) unstable; urgency=medium
 
   * Team upload.
diff -Nru polylib-5.22.5/debian/patches/fix-implicit-function-declaration.patch polylib-5.22.5/debian/patches/fix-implicit-function-declaration.patch
--- polylib-5.22.5/debian/patches/fix-implicit-function-declaration.patch	1970-01-01 05:00:00.0 +0500
+++ polylib-5.22.5/debian/patches/fix-implicit-function-declaration.patch	2024-03-16 20:05:30.0 +0500
@@ -0,0 +1,19 @@
+Description: Add missing forward declarations.
+Author: Andrey Rakhmatullin 
+Bug-Debian: https://bugs.debian.org/1066303
+Last-Update: 2024-03-16
+
+--- polylib-5.22.5.orig/applications/testCompressParms.c
 polylib-5.22.5/applications/testCompressParms.c
+@@ -42,6 +42,11 @@
+ 
+ #define maxRays 200
+ 
++int test_Constraints_Remove_parm_eqs(Matrix * A, Matrix * B);
++int test_Polyhedron_Remove_parm_eqs(Matrix * A, Matrix * B);
++int test_Constraints_fullDimensionize(Matrix * A, Matrix * B,
++  unsigned int nbSamples);
++
+ const char *origNames[] =
+ 	{"n", "o", "p", "q", "r", "s", "t", "u", "v", "w", "x", "y", "z"};
+ 
diff -Nru polylib-5.22.5/debian/patches/series polylib-5.22.5/debian/patches/series
--- polylib-5.22.5/debian/patches/series	1970-01-01 05:00:00.0 +0500
+++ polylib-5.22.5/debian/patches/series	2024-03-16 20:05:30.0 +0500
@@ -0,0 +1 @@
+fix-implicit-function-declaration.patch


signature.asc
Description: PGP signature

Bug#1066974: freecad: package got copletely removed from Debian testing

[Kurt Kremitzki]

The current status of this:

- the Path workbench has a test which checks string equality on generated vs 
expected G-code for an operation. On the i386 arch only, the produced G-code is 
not what is expected, although it is consistent. In a G-code viewer, what is 
produced is visually identical, just with an increased number of arcs of 
shorter length. I've patched this test with a special-case check to use a 
different "expected" string id the arch is i386, and this works, even if not 
elegant; the further yak-shaving needed has been discussed with upstream.

- on armel, it seems FEM workbench tests are failing, but it isn't enough to 
e.g. disable that workbench, because then the failures just pop up elsewhere. 
I've repeated this "disable test, different test segfaults elsewhere" pattern 
about 5 times. It seems like, for some reason, the armel builds are no longer 
viable. It isn't ideal, but FreeCAD is probably not getting much use on the 
arch, so it may be that it ought to be removed from the architecture.

I would appreciate some feedback on these 2 items. I could do an upload with a 
patch for the Path test and request armel removal if nobody has any better 
suggestions or reservations about this approach.

Thanks,
Kurt

Bug#1066989: atf: descriptions swapped on library packages

[Ingo Saitz]

Source: atf
Version: 0.21-6
Severity: minor

Dear Maintainer,

$ apt-cache search libatf-c
libatf-c++-2 - Automated Test Framework (shared C library)
libatf-c-1 - Automated Test Framework (shared C++ library)

This looks like the descriptions are swapped on these two packages. I
checked the contents of the included shared libraries and indeed only
libatf-c++-2 contains C++ symbols.

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

Kernel: Linux 6.7.6-spatz20240223 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_USER, TAINT_WARN, TAINT_FIRMWARE_WORKAROUND, 
TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Bug#1066988: numpy: FTBFS: RuntimeError: Running cythonize failed!

[Sebastian Ramacher]

Source: numpy
Version: 1:1.24.2-3
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=numpy=amd64=1%3A1.24.2-3=1709907264=0

Running from numpy source directory.
/<>/setup.py:67: DeprecationWarning: 

  `numpy.distutils` is deprecated since NumPy 1.23.0, as a result
  of the deprecation of `distutils` itself. It will be removed for
  Python >= 3.12. For older Python versions it will remain present.
  It is recommended to use `setuptools < 60.0` for those Python versions.
  For more details, see:
https://numpy.org/devdocs/reference/distutils_status_migration.html 


  import numpy.distutils.command.sdist

Error compiling Cython file:

...
cdef sfc64_state rng_state

def __init__(self, seed=None):
BitGenerator.__init__(self, seed)
self._bitgen.state = _state
self._bitgen.next_uint64 = _uint64
   ^


_sfc64.pyx:90:35: Cannot assign type 'uint64_t (*)(void *) except? -1 nogil' to 
'uint64_t (*)(void *) noexcept nogil'. Exception values are incompatible. 
Suggest adding 'noexcept' to type 'uint64_t (void *) except? -1 nogil'.
Processing numpy/random/_bounded_integers.pxd.in
Processing numpy/random/mtrand.pyx
Processing numpy/random/bit_generator.pyx
Processing numpy/random/_sfc64.pyx
Traceback (most recent call last):
  File "/<>/tools/cythonize.py", line 205, in 
main()
  File "/<>/tools/cythonize.py", line 201, in main
find_process_files(root_dir)
  File "/<>/tools/cythonize.py", line 192, in find_process_files
process(root_dir, fromfile, tofile, function, hash_db)
  File "/<>/tools/cythonize.py", line 158, in process
processor_function(fromfile, tofile)
  File "/<>/tools/cythonize.py", line 47, in process_pyx
subprocess.check_call(
  File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/python3.12', '-m', 'cython', 
'-3', '--fast-fail', '-o', '_sfc64.c', '_sfc64.pyx']' returned non-zero exit 
status 1.
Cythonizing sources
Traceback (most recent call last):
  File "/<>/setup.py", line 479, in 
setup_package()
  File "/<>/setup.py", line 458, in setup_package
generate_cython()
  File "/<>/setup.py", line 261, in generate_cython
raise RuntimeError("Running cythonize failed!")
RuntimeError: Running cythonize failed!
E: pybuild pybuild:391: configure: plugin distutils failed with: exit code=1: 
python3.12 setup.py config 
dh_auto_configure: error: pybuild --configure -i python{version} -p "3.12 3.11" 
returned exit code 13

Cheers
-- 
Sebastian Ramacher

Bug#1066986: ghemical: FTBFS: /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libghemical.so: undefined reference to `sc::RenderedBallMolecule::RenderedBallMolecule(sc::Ref

[Sebastian Ramacher]

Source: ghemical
Version: 3.0.0-5
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=ghemical=amd64=3.0.0-5%2Bb3=1710520317=0

/bin/bash ../libtool  --tag=CXX   --mode=link g++  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection  
-Wl,-z,relro -Wl,--as-needed -o ghemical fileio.o filetrans.o custom_app.o 
custom_camera.o custom_lights.o project.o spline.o pangofont_wcl.o 
oglview_wcl.o ac_stor_wcl.o p1dview_wcl.o p2dview_wcl.o eldview_wcl.o 
rcpview_wcl.o gpcview_wcl.o ogl_plane.o ogl_surface.o ogl_ribbon.o 
gtk_simple_dialogs.o gtk_glade_dialog.o gtk_file_export_dialog.o 
gtk_file_import_dialog.o gtk_geomopt_dialog.o gtk_moldyn_dialog.o 
gtk_progress_dialog.o gtk_setup_dialog.o gtk_stereo_dialog.o 
gtk_trajview_dialog.o gtk_wnd.o gtk_oglview_wnd.o gtk_p1dview_wnd.o 
gtk_p2dview_wnd.o gtk_eldview_wnd.o gtk_rcpview_wnd.o gtk_gpcview_wnd.o 
gtk_app.o gtk_project.o gtk_main.o  -lm  -L/usr/X11R6/lib -lgthread-2.0 
-pthread -lglib-2.0  -lgtkglext-x11-1.0 -lgdkglext-x11-1.0 -lGLU -lGL -lXmu 
-lXt -lSM -lICE -Wl,--export-dynamic -lgmodule-2.0 -pthread -lglib-2.0 
-lglade-2.0 -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo 
-lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 
-lharfbuzz -lfontconfig -lfreetype -lxml2  -lopenbabel  -lghemical -lmopac7 
-lGL -lGLU -loglappth 
libtool: link: g++ -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wl,-z -Wl,relro -Wl,--as-needed -o 
ghemical fileio.o filetrans.o custom_app.o custom_camera.o custom_lights.o 
project.o spline.o pangofont_wcl.o oglview_wcl.o ac_stor_wcl.o p1dview_wcl.o 
p2dview_wcl.o eldview_wcl.o rcpview_wcl.o gpcview_wcl.o ogl_plane.o 
ogl_surface.o ogl_ribbon.o gtk_simple_dialogs.o gtk_glade_dialog.o 
gtk_file_export_dialog.o gtk_file_import_dialog.o gtk_geomopt_dialog.o 
gtk_moldyn_dialog.o gtk_progress_dialog.o gtk_setup_dialog.o 
gtk_stereo_dialog.o gtk_trajview_dialog.o gtk_wnd.o gtk_oglview_wnd.o 
gtk_p1dview_wnd.o gtk_p2dview_wnd.o gtk_eldview_wnd.o gtk_rcpview_wnd.o 
gtk_gpcview_wnd.o gtk_app.o gtk_project.o gtk_main.o -Wl,--export-dynamic  -lm 
-L/usr/X11R6/lib -lgthread-2.0 /usr/lib/x86_64-linux-gnu/libgtkglext-x11-1.0.so 
/usr/lib/x86_64-linux-gnu/libgdkglext-x11-1.0.so -lXmu -lXt -lSM -lICE 
-lgmodule-2.0 -lglade-2.0 -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 
-latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 
-lgobject-2.0 -lglib-2.0 -lharfbuzz -lfontconfig -lfreetype -lxml2 -lopenbabel 
-lghemical -lmopac7 -lGL -lGLU -loglappth -pthread
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libghemical.so: 
undefined reference to 
`sc::PthreadThreadGrp::PthreadThreadGrp(sc::Ref const&)'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libghemical.so: 
undefined reference to `sc::RefSCDimension::~RefSCDimension()'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libghemical.so: 
undefined reference to 
`sc::ReplSCMatrixKit::ReplSCMatrixKit(sc::Ref const&)'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libghemical.so: 
undefined reference to 
`sc::SymmMolecularCoor::SymmMolecularCoor(sc::Ref const&)'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libghemical.so: 
undefined reference to 
`sc::KeyValValueRefDescribedClass::~KeyValValueRefDescribedClass()'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libghemical.so: 
undefined reference to 
`sc::ThreadGrp::set_default_threadgrp(sc::Ref const&)'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libghemical.so: 
undefined reference to `sc::SCVectordouble::operator double()'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libghemical.so: 
undefined reference to `vtable for sc::KeyValValueRefDescribedClass'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libghemical.so: 
undefined reference to `sc::RefSCVector::operator[](int) const'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libghemical.so: 
undefined reference to 
`sc::SteepestDescentOpt::SteepestDescentOpt(sc::Ref const&)'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libghemical.so: 
undefined reference to `sc::RefSCVector::~RefSCVector()'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libghemical.so: 
undefined reference to `sc::MTMPIMemoryGrp::MTMPIMemoryGrp(sc::Ref 
const&)'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libghemical.so: 
undefined reference to 
`sc::RegionTimer::set_default_regiontimer(sc::Ref const&)'
/usr/bin/ld: 

Bug#1065310: I've been hit by this bug also

[Eric Valette]

Using different package name, all with t64 in their names and yes it 
seams that Provides: is not taken into account for reverse depends.


-- eric

Bug#1066987: clickhouse: FTBFS: flaky tests

[Sebastian Ramacher]

Source: clickhouse
Version: 18.16.1+ds-7.4
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=clickhouse=amd64=18.16.1%2Bds-7.4%2Bb5=1710317462=0

10/10 Test #10: with_server ***Failed  357.43 sec

The following tests passed:
test_longjmp
test_siglongjmp
test_local_date_time_comparison
test_unit_tests_libcommon
test_hashing_read_buffer
test_multi_version
test_expression_analyzer
test_in_join_subqueries_preprocessor
test_hashing_write_buffer

90% tests passed, 1 tests failed out of 10

Total Test time (real) = 357.54 sec

The following tests FAILED:
 10 - with_server (Failed)
Errors while running CTest
Output from these tests are in: 
/<>/obj-x86_64-linux-gnu/Testing/Temporary/LastTest.log

https://buildd.debian.org/status/fetch.php?pkg=clickhouse=mips64el=18.16.1%2Bds-7.4=1694786851=0

5/7 Test #4: test_hashing_write_buffer ..   Passed0.46 sec
7: [OK] SELECT number AS n FROM system.numbers LIMIT 0
7: [OK] SELECT number AS n FROM system.numbers LIMIT 0
6/7 Test #6: test_in_join_subqueries_preprocessor ...***Exception: SegFault  
1.64 sec
7/7 Test #7: test_expression_analyzer ...   Passed1.64 sec

The following tests passed:
test_local_date_time_comparison
test_multi_version
test_hashing_read_buffer
test_hashing_write_buffer
test_expression_analyzer

71% tests passed, 2 tests failed out of 7

Total Test time (real) =   1.92 sec

The following tests FAILED:
  3 - test_unit_tests_libcommon (SEGFAULT)
  6 - test_in_join_subqueries_preprocessor (SEGFAULT)
Errors while running CTest
Output from these tests are in: 
/<>/obj-mips64el-linux-gnuabi64/Testing/Temporary/LastTest.log

Cheers
-- 
Sebastian Ramacher

Bug#1066985: gdis: FTBFS: crystal_graph.c:180:3: error: implicit declaration of function ‘type_dreiding_gasteiger’ [-Werror=implicit-function-declaration]

[Sebastian Ramacher]

Source: gdis
Version: 0.90-6
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=gdis=amd64=0.90-6%2Bb2=1710520208=0

cc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-fcommon `pkg-config --cflags gtk+-2.0 gthread-2.0 gtkglext-1.0 gmodule-2.0` 
-DWITH_GUI -UWITH_GRISU -Wdate-time -D_FORTIFY_SOURCE=2  -c -o defect.o defect.c
In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
 from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
 from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
 from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
 from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
 from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
 from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:33,
 from gdis.h:270,
 from error.c:27:
/usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: ‘GTypeDebugFlags’ is 
deprecated [-Wdeprecated-declarations]
  236 | voidgtk_type_init   (GTypeDebugFlagsdebug_flags);
  | ^~~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:26,
 from /usr/include/glib-2.0/gobject/gbinding.h:31,
 from /usr/include/glib-2.0/glib-object.h:24,
 from /usr/include/glib-2.0/gio/gioenums.h:30,
 from /usr/include/glib-2.0/gio/giotypes.h:30,
 from /usr/include/glib-2.0/gio/gio.h:28,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:32:
/usr/include/glib-2.0/gobject/gtype.h:723:1: note: declared here
  723 | {
  | ^
In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
 from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtk.h:126:
/usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTimeVal’ is deprecated: 
Use 'GDateTime' instead [-Wdeprecated-declarations]
   73 |   GTimeVal last_popdown;
  |   ^~~~
In file included from /usr/include/glib-2.0/glib/galloca.h:34,
 from /usr/include/glib-2.0/glib.h:32,
 from gdis.h:269:
/usr/include/glib-2.0/glib/gtypes.h:580:8: note: declared here
  580 | struct _GTimeVal
  |^
In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
 from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
 from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
 from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
 from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
 from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
 from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:33,
 from gdis.h:270,
 from scan.c:28:
/usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: ‘GTypeDebugFlags’ is 
deprecated [-Wdeprecated-declarations]
  236 | voidgtk_type_init   (GTypeDebugFlagsdebug_flags);
  | ^~~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:26,
 from /usr/include/glib-2.0/gobject/gbinding.h:31,
 from /usr/include/glib-2.0/glib-object.h:24,
 from /usr/include/glib-2.0/gio/gioenums.h:30,
 from /usr/include/glib-2.0/gio/giotypes.h:30,
 from /usr/include/glib-2.0/gio/gio.h:28,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:32:
/usr/include/glib-2.0/gobject/gtype.h:723:1: note: declared here
  723 | {
  | ^
In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
 from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtk.h:126:
/usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTimeVal’ is deprecated: 
Use 'GDateTime' instead [-Wdeprecated-declarations]
   73 |   GTimeVal last_popdown;
  |   ^~~~
In file included from /usr/include/glib-2.0/glib/galloca.h:34,
 from /usr/include/glib-2.0/glib.h:32,
 from gdis.h:269:
/usr/include/glib-2.0/glib/gtypes.h:580:8: note: declared here
  580 | struct _GTimeVal
  |^
cc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat 

Bug#1066984: gabedit: FTBFS: Preferences.c:2254:23: error: implicit declaration of function ‘selectionOfDir’; did you mean ‘selctionOfDir’? [-Werror=implicit-function-declaration]

[Sebastian Ramacher]

Source: gabedit
Version: 2.5.1+ds-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=gabedit=amd64=2.5.1%2Bds-1%2Bb3=1710520087=0

gcc -fno-common -c -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wdate-time -D_FORTIFY_SOURCE=2 -DENABLE_DEPRECATED -fcommon -DENABLE_OMP 
-fopenmp -DDRAWGEOMGL -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi 
-I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/x86_64-linux-gnu -I/usr/include/webp -I/usr/include/atk-1.0 
-I/usr/include/gtkglext-1.0 -I/usr/lib/x86_64-linux-gnu/gtkglext-1.0/include 
-pthread  GInterfaceMethodeBase.c -o GInterfaceMethodeBase.o
In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
 from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtk.h:126:
/usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTimeVal’ is deprecated: 
Use 'GDateTime' instead [-Wdeprecated-declarations]
   73 |   GTimeVal last_popdown;
  |   ^~~~
In file included from /usr/include/glib-2.0/glib/galloca.h:34,
 from /usr/include/glib-2.0/glib.h:32,
 from /usr/include/glib-2.0/gobject/gbinding.h:30:
/usr/include/glib-2.0/glib/gtypes.h:580:8: note: declared here
  580 | struct _GTimeVal
  |^
In file included from Preferences.c:27:
../Utils/UtilsInterface.h:124:13: warning: Deprecated pre-processor symbol: 
replace with "const"
  124 | GtkWidget *add_label_table(GtkWidget *Table, G_CONST_RETURN gchar 
*label,gushort line,gushort colonne);
  | ^
../Utils/UtilsInterface.h:129:13: warning: Deprecated pre-processor symbol: 
replace with "const"
  129 | void set_last_directory(G_CONST_RETURN gchar* FileName);
  | ^~~~ 
In file included from Preferences.c:29:
../Utils/Utils.h:63:13: warning: Deprecated pre-processor symbol: replace with 
"const"
   63 | G_CONST_RETURN gchar *get_local_user();
  | ^~~  
../Utils/Utils.h:75:13: warning: Deprecated pre-processor symbol: replace with 
"const"
   75 | gchar *get_dir_file_name(G_CONST_RETURN gchar* dirname, G_CONST_RETURN 
gchar* filename);
  | ^
../Utils/Utils.h:75:13: warning: Deprecated pre-processor symbol: replace with 
"const"
../Utils/Utils.h:150:13: warning: Deprecated pre-processor symbol: replace with 
"const"
  150 | void gabedit_string_get_pixel_size(GtkWidget* parent, 
PangoFontDescription *font_desc, G_CONST_RETURN gchar* t, int *width, int* 
height);
  | ^
../Utils/Utils.h:151:13: warning: Deprecated pre-processor symbol: replace with 
"const"
  151 | void gabedit_draw_string(GtkWidget* parent, GdkPixmap* pixmap, 
PangoFontDescription *font_desc, GdkGC* gc , gint x, gint y, G_CONST_RETURN 
gchar* t, gboolean centerX, gboolean centerY);
  | ^
../Utils/Utils.h:153:13: warning: Deprecated pre-processor symbol: replace with 
"const"
  153 | G_CONST_RETURN gchar* get_open_babel_command();
  | ^~~  
../Utils/Utils.h:162:13: warning: Deprecated pre-processor symbol: replace with 
"const"
  162 | gchar * mystrcasestr(G_CONST_RETURN gchar *haystack, G_CONST_RETURN 
gchar *needle);
  | ^
../Utils/Utils.h:162:13: warning: Deprecated pre-processor symbol: replace with 
"const"
Preferences.c: In function ‘remove_gamess_command’:
Preferences.c:140:13: warning: Deprecated pre-processor symbol: replace with 
"const"
  140 |   G_CONST_RETURN gchar *strcom;
  | ^~~  
Preferences.c: In function ‘modify_gamess_command’:
Preferences.c:187:13: warning: Deprecated pre-processor symbol: replace with 
"const"
  187 |   G_CONST_RETURN gchar *strcom;
  | ^~~  
Preferences.c: In function ‘remove_gaussian_command’:
Preferences.c:222:13: warning: Deprecated pre-processor symbol: replace with 
"const"
  222 |   

Bug#1066951: RM: a56 -- ROM; rc buggy and dead upstream

[Bastian Germann]

On Fri, 15 Mar 2024 23:18:30 + (UTC) Thorsten Alteholz  
wrote:

When trying to fix #1066195, the corresponding patch grew more and more.

I no longer wonder why C got such a bad reputation when this was valid 
code 30 years ago. From my point of view this code needs an entire rework.


As I long time ago stopped working with DSPs, I don't want to do this 
rework by myself. If nobody takes up the baton, I think it is better to 
remove this package from Debian. As the software fails to compile now, 
orphaning the package does not seem to be appropriate.


Please do not remove the package as it is needed to fix #890601.
Fixing #890601 by removing the firmware blobs that are currently
not built from source would be fine for me as well.

I will take a look at #1066195 when time allows.

Thanks!

Bug#1065787: 64-bit time_t transition: cargo needs manual intervention

[Matthias Klose]

On 16.03.24 15:29, Simon McVittie wrote:

On Thu, 14 Mar 2024 at 22:03:57 -0700, Otto Kekäläinen wrote:

For example curl isn't building on armel/armhf now and numerous packages that
depend of curl are not building on armel/armhf.


I believe a maintainer upload or NMU of #1066981 and #1066982 would
now be enough to unblock curl, which would hopefully unblock a lot of
the C/C++ ecosystem (in particular fixing the unsatisfiable dependency
libdebuginfod1t64 -> libcurl3t64-gnutls on armel/armhf, which would allow
gdb to be installed), while also making life easier for the people trying
to re-bootstrap cargo.


build gdb without libdebuginfo on the bootstrap archs for a while.

Bug#1066983: monopd: Fails to start monopd.service

[Shriram Ravindranathan]

Package: monopd
Version: 0.10.2-6+b2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: s...@ters.dev

Dear Maintainer,

monopd.service fails to start (could not bind port 1234), rendering the package 
unusable.

Here is the lsof output after the package is installed:
systemd  1root   47u  IPv6 198704  0t0  TCP *:1234 (LISTEN)
exim4 1116 Debian-exim4u  IPv4  20710  0t0  TCP 127.0.0.1:25 
(LISTEN)
exim4 1116 Debian-exim5u  IPv6  20711  0t0  TCP [::1]:25 (LISTEN)

This was on a fresh install of bookworm. Here are the journalctl logs:

Mar 16 19:25:02 think182 sudo[4410]:  shriram : TTY=pts/0 ; PWD=/home/shriram ; 
USER=root ; COMMAND=/usr/bin/apt install monopd
Mar 16 19:25:02 think182 sudo[4410]: pam_unix(sudo:session): session opened for 
user root(uid=0) by (uid=1000)
Mar 16 19:25:03 think182 systemd[1]: Reloading.
Mar 16 19:25:04 think182 systemd[1]: Reloading.
Mar 16 19:25:04 think182 systemd[1]: Starting monopd.service - game server for 
board games like GtkAtlantic...
Mar 16 19:25:04 think182 systemd[1]: Listening on monopd.socket - monopd 
listening socket.
Mar 16 19:25:04 think182 monopd[4512]: monopd 0.10.2 started
Mar 16 19:25:04 think182 monopd[4512]: loaded game configuration: 
game=[Atlantic]
Mar 16 19:25:04 think182 monopd[4512]: loaded game configuration: 
game=[Monopoly]
Mar 16 19:25:04 think182 systemd[1]: monopd.service: Failed to parse ERRNO= 
field value '-2' in notification message: Numerical result out of range
Mar 16 19:25:04 think182 monopd[4512]: could not bind port 1234, exiting
Mar 16 19:25:04 think182 systemd[1]: monopd.service: Main process exited, 
code=exited, status=254/n/a
Mar 16 19:25:04 think182 systemd[1]: monopd.service: Failed with result 
'exit-code'.
Mar 16 19:25:04 think182 systemd[1]: Failed to start monopd.service - game 
server for board games like GtkAtlantic.
Mar 16 19:25:05 think182 sudo[4410]: pam_unix(sudo:session): session closed for 
user root


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

Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages monopd depends on:
ii  libc6  2.36-9+deb12u4
ii  libgcc-s1  12.2.0-14
ii  libmuparser2v5 2.3.3-0.1
ii  libstdc++6 12.2.0-14
ii  libsystemd0252.22-1~deb12u1
ii  sysvinit-utils [lsb-base]  3.06-4

monopd recommends no packages.

Versions of packages monopd suggests:
ii  gtkatlantic  0.6.3-2

-- no debconf information

Bug#1065787: 64-bit time_t transition: cargo needs manual intervention

[Simon McVittie]

On Thu, 14 Mar 2024 at 22:03:57 -0700, Otto Kekäläinen wrote:
> For example curl isn't building on armel/armhf now and numerous packages that
> depend of curl are not building on armel/armhf.

I believe a maintainer upload or NMU of #1066981 and #1066982 would
now be enough to unblock curl, which would hopefully unblock a lot of
the C/C++ ecosystem (in particular fixing the unsatisfiable dependency
libdebuginfod1t64 -> libcurl3t64-gnutls on armel/armhf, which would allow
gdb to be installed), while also making life easier for the people trying
to re-bootstrap cargo.

As a non-user of the affected architectures, I'm not comfortable with
being responsible for NMU'ing those changes (certainly not without giving
the curl maintainers a chance to comment!), but I've provided patches so
that either a curl maintainer or a porter could do so.

Thanks,
smcv

Bug#1066506: mcpp: diff for NMU version 2.7.2-5.1

[Andrey Rakhmatullin]

Control: tags 1066506 + patch
Control: tags 1066506 + pending

Dear maintainer,

I've prepared an NMU for mcpp (versioned as 2.7.2-5.1) and
uploaded it to DELAYED/4. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
WBR, wRAR
diff -Nru mcpp-2.7.2/debian/changelog mcpp-2.7.2/debian/changelog
--- mcpp-2.7.2/debian/changelog	2019-08-15 11:50:38.0 +0500
+++ mcpp-2.7.2/debian/changelog	2024-03-16 18:23:16.0 +0500
@@ -1,3 +1,10 @@
+mcpp (2.7.2-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066506).
+
+ -- Andrey Rakhmatullin   Sat, 16 Mar 2024 18:23:16 +0500
+
 mcpp (2.7.2-5) unstable; urgency=medium
 
   * debian/compat: Require 10.
diff -Nru mcpp-2.7.2/debian/patches/fix-implicit-function-declaration.patch mcpp-2.7.2/debian/patches/fix-implicit-function-declaration.patch
--- mcpp-2.7.2/debian/patches/fix-implicit-function-declaration.patch	1970-01-01 05:00:00.0 +0500
+++ mcpp-2.7.2/debian/patches/fix-implicit-function-declaration.patch	2024-03-16 18:23:16.0 +0500
@@ -0,0 +1,18 @@
+Description: Define a feature test macro
+Author: Andrey Rakhmatullin 
+Bug-Debian: https://bugs.debian.org/1066506
+Last-Update: 2024-03-16
+
+Index: mcpp-2.7.2/src/system.c
+===
+--- mcpp-2.7.2.orig/src/system.c
 mcpp-2.7.2/src/system.c
+@@ -36,6 +36,8 @@
+  *  1. specify the constants in "configed.H" or "noconfig.H",
+  *  2. append the system-dependent routines in this file.
+  */
++#define _POSIX_C_SOURCE 200809L
++
+ #if PREPROCESSED
+ #include"mcpp.H"
+ #else
diff -Nru mcpp-2.7.2/debian/patches/series mcpp-2.7.2/debian/patches/series
--- mcpp-2.7.2/debian/patches/series	2019-08-15 11:46:26.0 +0500
+++ mcpp-2.7.2/debian/patches/series	2024-03-16 18:23:16.0 +0500
@@ -4,3 +4,4 @@
 04-gniibe-fix-12.patch
 05-gniibe-fix-13.patch
 06-gniibe-fix-autotools.patch
+fix-implicit-function-declaration.patch


signature.asc
Description: PGP signature

Bug#1066982: curl: please consider temporarily disabling LDAP and build-time tests on 32-bit non-x86

[Simon McVittie]

Source: curl
Version: 8.6.0-3.2
Severity: wishlist
X-Debbugs-Cc: debian-...@lists.debian.org, e...@debian.org
Tags: trixie sid patch
Control: block -1 by 1066981

On the architectures affected by the 64-bit time_t transition, there
are at least two cyclic build-dependencies involving this package:
curl, openldap, cyrus-sasl2, postgresql-16, gdb, elfutils, curl and
curl, impacket, pyopenssl, python-cryptography, cargo, curl.

I think it could be pragmatic to disable build-time tests and LDAP on
the affected architectures for a short time in order to unblock this
transition: quite a lot of packages are queued for rebuilding behind
curl and/or cargo.

The attached patches (which are also available from
https://salsa.debian.org/debian/curl/-/merge_requests/24, and depend
on the build profile added in #1066981) implement what I'm
suggesting. I've confirmed that the package builds successfully with
this change in armel and armhf porterbox chroots, and that it still runs
build-time tests on amd64 and i386 (at the time of writing, my amd64
build has passed its tests and my i386 build is still running them).

Unlike #1066981, the patches attached to this bug are intended to be
temporary and should be reverted when the transition has finished.

Thanks,
smcv
>From bc8cd5d7a40c8acaf2c164c538b6c0b07f2d3dab Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Sat, 16 Mar 2024 11:36:05 +
Subject: [PATCH 2/3] Temporarily disable LDAP support on 32-bit non-x86

This makes official buildd builds of curl (with no special build
profiles) temporarily equivalent to pkg.curl.noldap on the
architectures affected by the ongoing 64-bit time_t transition.

This helps to break cyclic dependencies like this one:
curl, openldap, cyrus-sasl2, postgresql-16, gdb, elfutils, curl.
It can be reverted after the transition has progressed past curl.

Helps: #1036884
---
 debian/control | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index ee188861b..fe6cf6881 100644
--- a/debian/control
+++ b/debian/control
@@ -16,7 +16,7 @@ Build-Depends: dpkg-dev (>= 1.22.5),
  libgnutls28-dev,
  libidn2-dev,
  libkrb5-dev,
- libldap2-dev ,
+ libldap2-dev [!armel !armhf !hppa !m68k !powerpc !sh4] ,
  libnghttp2-dev,
  libpsl-dev,
  librtmp-dev,
-- 
2.43.0

>From c105fbbae946bae3c755d8f87d247a36d8d59d47 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Sat, 16 Mar 2024 11:34:46 +
Subject: [PATCH 3/3] Temporarily disable build-time tests on 32-bit non-x86

This makes official buildd builds of curl (with no special build profiles)
temporarily equivalent to nocheck on the architectures affected by the
ongoing 64-bit time_t transition.

This helps to break cyclic dependencies like this one:
curl, impacket, pyopenssl, python-cryptography, cargo, curl.
It can be reverted after the transition has progressed past curl.

Helps: #1036884
---
 debian/control | 12 ++--
 debian/rules   |  4 
 2 files changed, 10 insertions(+), 6 deletions(-)

diff --git a/debian/control b/debian/control
index fe6cf6881..35945dfcf 100644
--- a/debian/control
+++ b/debian/control
@@ -25,13 +25,13 @@ Build-Depends: dpkg-dev (>= 1.22.5),
  libssl-dev,
  libtool,
  libzstd-dev,
- locales-all ,
- openssh-server ,
- python3:native ,
- python3-impacket ,
- gnutls-bin [!ppc64el] ,
+ locales-all [!armel !armhf !hppa !m68k !powerpc !sh4] ,
+ openssh-server [!armel !armhf !hppa !m68k !powerpc !sh4] ,
+ python3:native [!armel !armhf !hppa !m68k !powerpc !sh4] ,
+ python3-impacket [!armel !armhf !hppa !m68k !powerpc !sh4] ,
+ gnutls-bin [!armel !armhf !hppa !m68k !powerpc !sh4 !ppc64el] ,
  quilt,
- stunnel4 ,
+ stunnel4 [!armel !armhf !hppa !m68k !powerpc !sh4] ,
  zlib1g-dev,
 Build-Conflicts: autoconf2.13, automake1.4
 Standards-Version: 4.6.2
diff --git a/debian/rules b/debian/rules
index 3049d659d..f0ceec938 100755
--- a/debian/rules
+++ b/debian/rules
@@ -100,6 +100,9 @@ TESTS_GENERAL_PARAMETERS += $(TESTS_FAILS_ON_IPV6_ONLY_MACHINES)
 
 override_dh_auto_test:
 ifeq ($(filter nocheck,$(DEB_BUILD_PROFILES)),)
+ifeq ($(DEB_HOST_ARCH_BITS)$(filter i386,$(DEB_HOST_ARCH_CPU)),32)
+	: # TODO: Tests temporarily skipped for 64-bit time_t transition
+else
 ifeq ($(filter pkg.curl.no-openssl,$(DEB_BUILD_PROFILES)),)
 # OpenSSL tests.
 	cd debian/build && VERBOSE=1 \
@@ -113,6 +116,7 @@ ifeq ($(filter pkg.curl.no-gnutls,$(DEB_BUILD_PROFILES)),)
 		$(MAKE) test-nonflaky
 endif
 endif
+endif
 
 override_dh_install:
 ifeq ($(filter pkg.curl.no-openssl,$(DEB_BUILD_PROFILES)),)
-- 
2.43.0

Bug#1061212: Please upgrade to llvm-toolchain-17

[Bastian Germann]

v3.1.44 should be the best upstream version for this.

Bug#1066981: curl: please provide a build-profile that disables LDAP

[Simon McVittie]

Source: curl
Version: 8.6.0-3.2
Severity: wishlist
Tags: trixie sid patch
User: debian-cr...@lists.debian.org
Usertags: staged-build

curl is involved in the critical path for re-bootstrapping 32-bit
architectures for the time_t transition, and in general it's likely
to be tied up in bootstrapping of every other new architecture, because
important toolchain components like elfutils and cmake depend on it.
One thing that can easily be done to break some of the cycles is to
disable its optional support for openldap, which is involved in cycles like:
curl, openldap, cyrus-sasl2, postgresql-16, gdb, elfutils, curl.

The attached patch (also available from
https://salsa.debian.org/debian/curl/-/merge_requests/23)
adds a build-profile that disables this optional feature.

I've confirmed that in the current state of unstable, curl can be built
successfully in armel and armhf porterbox chroots with the combination of
this build profile and nocheck.

(An ulterior motive for me contributing this change is that in my
day job, I'm involved in maintaining the Debian-based Steam Runtime,
which contains a copy of curl with its packaging patched to disable
LDAP, RTSP, RTMP and possibly other features that are unlikely to be
used by game engines. When I'm back at work I'd be happy to look at
contributing similar build-profiles to disable other optional bits if
there is interest.)

smcv
>From ae094c1e4b2b0ec943f39f2b6a6176091af20d33 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Sat, 16 Mar 2024 11:26:58 +
Subject: [PATCH 1/3] d/control: Add a build-profile that disables LDAP support

openldap is involved in a cyclic build dependency
(curl, openldap, cyrus-sasl2, postgresql-16, gdb, elfutils, curl).
The ability to load LDAP resources is probably a relatively infrequently
used feature of curl, and is straightforward to disable.

Helps: #1036884
---
 debian/control | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index de9ac8f69..ee188861b 100644
--- a/debian/control
+++ b/debian/control
@@ -16,7 +16,7 @@ Build-Depends: dpkg-dev (>= 1.22.5),
  libgnutls28-dev,
  libidn2-dev,
  libkrb5-dev,
- libldap2-dev,
+ libldap2-dev ,
  libnghttp2-dev,
  libpsl-dev,
  librtmp-dev,
-- 
2.43.0

Bug#1065793: charliecloud: FTBFS on arm{el,hf}: ch_fuse.c:68:19: error: initialization of ‘void (*)(struct fuse_req *, fuse_ino_t, uint64_t)’ {aka ‘void (*)(struct fuse_req *, long long unsigned int,

[Peter Wienemann]

Control: reopen -1

It seems that the patch uploaded with 0.37-2 does not fix this issue.

See

https://buildd.debian.org/status/fetch.php?pkg=charliecloud=armel=0.37-2=1710594551=log

and

https://buildd.debian.org/status/fetch.php?pkg=charliecloud=armhf=0.37-2=1710594414=log

Therefore I reopen this bug.

Best regards,

Peter

Bug#1066328: scalapack: FTBFS: igsum2d_.c:154:7: error: implicit declaration of function ‘BI_imvcopy’; did you mean ‘BI_zmvcopy’? [-Werror=implicit-function-declaration]

[Andrey Rakhmatullin]

Control: forwarded -1 https://github.com/Reference-ScaLAPACK/scalapack/issues/31

On Wed, Mar 13, 2024 at 12:44:37PM +0100, Lucas Nussbaum wrote:
> > /<>/BLACS/SRC/igsum2d_.c: In function ‘igsum2d_’:
> > /<>/BLACS/SRC/igsum2d_.c:154:7: error: implicit declaration of 
> > function ‘BI_imvcopy’; did you mean ‘BI_zmvcopy’? 
> > [-Werror=implicit-function-declaration]
BLACS/SRC is a smelly mess of one-function files calling each other
without (in most cases at least) bothering to declare prototypes.
I started with adding the following prototypes to Bdef.h (before the last
#endif) because adding them to individual files is too much work:

void BI_dmvcopy(Int m, Int n, double *A, Int lda, double *buff);
void BI_dvmcopy(Int m, Int n, double *A, Int lda, double *buff);
void BI_imvcopy(Int m, Int n, Int *A, Int lda, Int *buff);
void BI_ivmcopy(Int m, Int n, Int *A, Int lda, Int *buff);
void BI_smvcopy(Int m, Int n, float *A, Int lda, float *buff);
void BI_svmcopy(Int m, Int n, float *A, Int lda, float *buff);
void BI_TransDist(BLACSCONTEXT *ctxt, char scope, Int m, Int n, Int *rA,
  Int *cA, Int ldrc, BI_DistType *dist, Int rdest, Int cdest);

But the next errors are things like "BLACS/SRC/blacs_init_.c:35:4: error:
implicit declaration of function ‘blacs_gridmap_’" and blacs_init_.c calls
either Cblacs_gridmap or blacs_gridmap_ but only declares a prototype for
the former and at this point I think let's the authors of this code sort
this mess.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#1064344: RFS: vzlogger/0.8.3 ITP #864255

[Joachim Zobel]

Hi Tobias.

Am Donnerstag, dem 14.03.2024 um 17:20 +0100 schrieb Tobias Frost:
> - $2 might be empty, you need to quote it: use "$2" otherwise dpkg will fail

That was a stupid one, thanks. Fixed and uploaded.

Sincerely,
Joachim

Bug#1066980: Please include "notify-send" in package description

[Christoph Berg]

Package: libnotify-bin
Version: 0.8.3-1
Severity: wishlist

This package solely ships "notify-send", but doesn't mention it in the
package description, so "apt-cache search notify send" doesn't find
it.

Please consider mentioning it, perhaps like this:

Description-en: sends desktop notifications to a notification daemon (Utilities)
 A library that sends desktop notifications to a notification daemon, as
 defined in the Desktop Notifications spec. These notifications can be
 used to inform the user about an event or display some form of
 information without getting in the user's way.
 .
 This package contains the notify-send command line utility.

Thanks,
Christoph

Bug#1066979: common-auth: sudo should not have incorrect password delay

[Tim Hutt]

Package: libpam-runtime
Version: 1.5.2-6+rpt2+deb12u1
Severity: normal
File: common-auth
X-Debbugs-Cc: tdh...@gmail.com

Dear Maintainer,

By default, on Debian and derivatives, `sudo` has a ~2 second delay for 
incorrect password attempts. This serves no security purpose whatsoever and 
merely annoys the user.

I think it would be great if it could be removed. Unfortunately it's not super 
simple because you do want a delay from other authentication clients (sshd, 
etc.), and they all use /etc/pam.d/auth-common, so you can't just add `nodelay` 
to `pam_unix.so` in that file.

I can think of a few solutions, but I'm not super familiar with Debian's PAM 
system (especially `pam-auth-update`). Anyway:

1. Add `auth-common-nodelay` that's exactly the same as `auth-common` but with 
`nodelay`, and use that from `/etc/pam.d/sudo[-i]`.
2. Add `nodelay` in `auth-common` and then add `auth-delay` that uses 
`pam_faildelay.so` to add a delay. The `@include auth-delay` from all files 
*except* `sudo[-i]`.
3. Improve `pam_faillock.so` to support exponential delays. The use of 
exponential delays is a very obvious feature and surprising omission. I assume 
the delay was originally fixed because of PAM's weird architecture that makes 
stateless authentication easier. However `pam_faillock.so` is stateful and 
records failed authentication attempts so the hard work has already been done. 
Modifying it to have an exponential delay (0, 0, 0, 0, 0, 1, 2, 2, 5, 10s, ...) 
would be quite easy.

I think 3 would be the best solution but is probably a fair bit of work. I'm 
not sure 2 is a great option because it isn't fail-safe. 1 is probably a 
reasonable option.

Also, a 2 second delay may sound insignificant but think how many people in the 
world use sudo. It's a minor annoyance multiplied by millions.

Cheers,

Tim

-- System Information:
Debian Release: 12.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 6.1.0-rpi7-rpi-v8 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libpam-runtime depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  libpam-modules 1.5.2-6+rpt2+deb12u1

libpam-runtime recommends no packages.

libpam-runtime suggests no packages.

-- debconf information:
  libpam-runtime/profiles: unix, systemd, chksshpwd
  libpam-runtime/override: false
  libpam-runtime/conflicts:
  libpam-runtime/no_profiles_chosen:
  libpam-runtime/title:

Bug#1062014: closing 1062014

[Gregor Riepl]

> The upstream bug has been closed because Prusa Slicer no longer has USB 
control
> capabilities.

Are you sure this is related?
Your upstream bug[1] is still open last I checked.

Also, prusa-slicer 2.7.1+dfsg-1 still depends on libbgcode[2], so it 
will still FTBFS on all big endian archs and block migration due to the 
missing s390x build.


Incidentally, I tried to build it with the dependency on libbgcode-dev 
removed, and it resulted in this error:



CMake Error at src/libslic3r/CMakeLists.txt:24 (find_package):
  By not providing "FindLibBGCode.cmake" in CMAKE_MODULE_PATH this project
  has asked CMake to find a package configuration file provided by
  "LibBGCode", but CMake did not find one.

  Could not find a package configuration file provided by "LibBGCode" with
  any of the following names:

LibBGCodeConfig.cmake
libbgcode-config.cmake

  Add the installation prefix of "LibBGCode" to CMAKE_PREFIX_PATH or set
  "LibBGCode_DIR" to a directory containing one of the above files.  If
  "LibBGCode" provides a separate development package or SDK, be sure it has
  been installed.


Looks like slicer 2.7.1 very much still depends on libbgcode.

Bug#1064170: mediastreamer2: NMU diff for 64-bit time_t transition

[Dennis Filder]

X-Debbugs-CC: Steve Langasek 

On Sat, Feb 17, 2024 at 04:27:04PM -0800, Steve Langasek wrote:
> Unfortunately, this has not been uploaded because mediastreamer2 appears to
> have a preexisting FTBFS in unstable due to missing cmake commands.

The NMU patch missed the library package name mentioned in
debian/rules.  Attached is a fixed revision of the patch (last hunk).

Regards.
diff -Nru mediastreamer2-5.2.0+dfsg/debian/changelog 
mediastreamer2-5.2.0+dfsg/debian/changelog
--- mediastreamer2-5.2.0+dfsg/debian/changelog  2024-01-30 14:30:19.0 
+
+++ mediastreamer2-5.2.0+dfsg/debian/changelog  2024-02-18 00:13:01.0 
+
@@ -1,3 +1,10 @@
+mediastreamer2 (1:5.2.0+dfsg-3.2) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Sun, 18 Feb 2024 00:13:01 +
+
 mediastreamer2 (1:5.2.0+dfsg-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru mediastreamer2-5.2.0+dfsg/debian/control 
mediastreamer2-5.2.0+dfsg/debian/control
--- mediastreamer2-5.2.0+dfsg/debian/control2024-01-30 14:30:14.0 
+
+++ mediastreamer2-5.2.0+dfsg/debian/control2024-02-18 00:13:01.0 
+
@@ -58,7 +58,10 @@
 Vcs-Browser: 
https://salsa.debian.org/pkg-voip-team/linphone-stack/mediastreamer2
 Description: Multimedia streaming engine for telephony
 
-Package: libmediastreamer13
+Package: libmediastreamer13t64
+Provides: ${t64:Provides}
+Replaces: libmediastreamer13
+Breaks: libmediastreamer13 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends},
@@ -86,7 +89,7 @@
 Section: libdevel
 Architecture: any
 Multi-Arch: same
-Depends: libmediastreamer13 (= ${binary:Version}),
+Depends: libmediastreamer13t64 (= ${binary:Version}),
  ${misc:Depends},
 # the .pc file mentions these 2, so a Depends: is needed
 # also the headers reference files from these 2
diff -Nru mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13.install 
mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13.install
--- mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13.install 2024-01-30 
14:20:36.0 +
+++ mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13.install 1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/libmediastreamer.so.*
diff -Nru mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13.shlibs 
mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13.shlibs
--- mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13.shlibs  2024-01-30 
14:20:36.0 +
+++ mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13.shlibs  1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-libmediastreamer 13 libmediastreamer13 (>= 1:5.2.0-1), libmediastreamer13 (<< 
1:5.3.0-1)
diff -Nru mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13t64.install 
mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13t64.install
--- mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13t64.install  
1970-01-01 00:00:00.0 +
+++ mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13t64.install  
2024-01-30 14:20:36.0 +
@@ -0,0 +1 @@
+usr/lib/*/libmediastreamer.so.*
diff -Nru 
mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13t64.lintian-overrides 
mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13t64.lintian-overrides
--- mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13t64.lintian-overrides
1970-01-01 00:00:00.0 +
+++ mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13t64.lintian-overrides
2024-02-18 00:13:01.0 +
@@ -0,0 +1 @@
+libmediastreamer13t64: package-name-doesnt-match-sonames libmediastreamer13
diff -Nru mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13t64.shlibs 
mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13t64.shlibs
--- mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13t64.shlibs   
1970-01-01 00:00:00.0 +
+++ mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13t64.shlibs   
2024-02-18 00:13:01.0 +
@@ -0,0 +1 @@
+libmediastreamer 13 libmediastreamer13t64 (>= 1:5.2.0-1), 
libmediastreamer13t64 (<< 1:5.3.0-1)
diff -Nru mediastreamer2-5.2.0+dfsg/debian/rules 
mediastreamer2-5.2.0+dfsg/debian/rules
--- mediastreamer2-5.2.0+dfsg/debian/rules  2024-01-30 14:30:19.0 
+
+++ mediastreamer2-5.2.0+dfsg/debian/rules  2024-02-18 00:13:01.0 
+
@@ -24,7 +24,7 @@ indeptargets := $(filter ms2-html-doc,$(cmaketargets))
 archtargets := $(filter-out ms2-html-doc,$(cmaketargets))
 endif
 
-libpkgname := libmediastreamer13
+libpkgname := libmediastreamer13t64
 
 features += -DENABLE_TOOLS=$(call 
when-building-package,libmediastreamer-tools,YES,NO)
 features += -DENABLE_UNIT_TESTS=no

Bug#1066361: atlas: FTBFS: probe_comp.c:653:13: error: implicit declaration of function ‘CompIsClang’ [-Werror=implicit-function-declaration]

[Sébastien Villemot]

Le samedi 16 mars 2024 à 17:32 +0500, Andrey Rakhmatullin a écrit :
> On Wed, Mar 13, 2024 at 12:35:48PM +0100, Lucas Nussbaum wrote:
> > > /<>/build/..//CONFIG/src/probe_comp.c:653:13: error: 
> > > implicit declaration of function ‘CompIsClang’ 
> > > [-Werror=implicit-function-declaration]
> > > /<>/build/..//CONFIG/src/probe_comp.c:1140:24: error: 
> > > implicit declaration of function ‘CompIsMinGW’ 
> > > [-Werror=implicit-function-declaration]
> The fix for these is adding
> 
> int CompIsClang(char *comp);
> int CompIsMinGW(char *comp);
> 
> to CONFIG/include/atlconf_misc.h (after CompIsGcc).
> 
> I have no idea how to fix the next errors though:
> 
> /<>/build/..//src/testing/ATL_f77gelqf.c: In function 
> ‘ATL_df77gelqf’:
> /<>/build/..//include/atlas_misc.h:127:16: error: implicit 
> declaration of function ‘dgelqf_’ [-Werror=implicit-function-declaration]
>   127 |#define PRE d
>   |^
> /<>/build/..//include/atlas_misc.h:74:27: note: in definition of 
> macro ‘my_join’
>74 | #define my_join(pre, nam) pre ## nam
>   |   ^~~
> /<>/build/..//src/testing/ATL_f77gelqf.c:40:21: note: in 
> expansion of macro ‘Mjoin’
>40 |#define F77GELQF Mjoin(PRE,gelqf_)
>   | ^
> /<>/build/..//src/testing/ATL_f77gelqf.c:40:27: note: in 
> expansion of macro ‘PRE’
>40 |#define F77GELQF Mjoin(PRE,gelqf_)
>   |   ^~~
> /<>/build/..//src/testing/ATL_f77gelqf.c:58:4: note: in 
> expansion of macro ‘F77GELQF’
>58 |F77GELQF(, , A, , tau, work, , );
>   |^~~~
> 
> In file included from /<>/build/..//src/testing/ATL_f77gels.c:30:
> /<>/build/..//src/testing/ATL_f77gels.c: In function 
> ‘ATL_df77gels’:
> /<>/build/..//include/atlas_misc.h:127:16: error: implicit 
> declaration of function ‘dgels_’ [-Werror=implicit-function-declaration]
>   127 |#define PRE d
>   |^
> /<>/build/..//include/atlas_misc.h:74:27: note: in definition of 
> macro ‘my_join’
>74 | #define my_join(pre, nam) pre ## nam
>   |   ^~~
> /<>/build/..//src/testing/ATL_f77gels.c:39:20: note: in 
> expansion of macro ‘Mjoin’
>39 |#define F77GELS Mjoin(PRE,gels_)
>   |^
> /<>/build/..//src/testing/ATL_f77gels.c:39:26: note: in 
> expansion of macro ‘PRE’
>39 |#define F77GELS Mjoin(PRE,gels_)
>   |  ^~~
> /<>/build/..//src/testing/ATL_f77gels.c:99:4: note: in expansion 
> of macro ‘F77GELS’
>99 |F77GELS(args);
>   |^~~
> 
> 
> This seems like some autogenerated code with heavy C macro usage.

Thanks for the suggested fix.

Note that atlas is obsolete scheduled for removal before trixie, see
the thread at:
https://lists.debian.org/msgid-search/4311acc16afb473599c79bd5b17a8b734c2f8d2b.ca...@debian.org

So I may fix this issue, but I’d rather have atlas removed sooner. The
remaining blockers are there:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=atlas-rm;users=debian-scie...@lists.debian.org

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org



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