Bug#1066834: libopenmpi3t64: libs are missing after 64-bit time_t transition

[Zixing Liu]

Package: openmpi
Followup-For: Bug #1066834
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Dear Maintainer,

This patch should install the optional libraries to the transitioned binary 
packages.

  * d/rules: correctly install all the optional libraries to the t64-suffixed
binary packages. (LP: #1070321)


Thanks for considering the patch.
diff -Nru openmpi-4.1.6/debian/rules openmpi-4.1.6/debian/rules
--- openmpi-4.1.6/debian/rules  2024-03-12 20:30:35.0 -0600
+++ openmpi-4.1.6/debian/rules  2024-03-13 18:49:15.0 -0600
@@ -179,11 +179,11 @@
cp 
$(BUILDDIR_FLANG)/ompi/mpi/fortran/*/.libs/libmpi_mpifh.so.40.30.0 
$(DESTDIR)/$(LIBDIR)/openmpi/lib/libmpi_mpifh-flang.so.40.30.0 ; \
cp 
$(BUILDDIR_FLANG)/ompi/mpi/fortran/*/.libs/libmpi_usempi_ignore_tkr.so.40.30.0 
$(DESTDIR)/$(LIBDIR)/openmpi/lib/libmpi_usempi_ignore_tkr-flang.so.40.30.0 ; \
cp 
$(BUILDDIR_FLANG)/ompi/mpi/fortran/*/.libs/libmpi_usempif08.so.40.30.0 
$(DESTDIR)/$(LIBDIR)/openmpi/lib/libmpi_usempif08-flang.so.40.30.0 ; \
-   dh_link -p libopenmpi3 $(LIBDIR)/libmpi_mpifh-flang.so.40.30.0  
 $(LIBDIR)/openmpi/lib/libmpi_mpifh-flang.so.40 ; \
+   dh_link -p libopenmpi3t64 
$(LIBDIR)/libmpi_mpifh-flang.so.40.30.0   
$(LIBDIR)/openmpi/lib/libmpi_mpifh-flang.so.40 ; \
dh_link -p libopenmpi-dev 
$(LIBDIR)/libmpi_mpifh-flang.so.40.30.0   
$(FLANG_LIBDIR)/openmpi/lib/libmpi_mpifh-flang.so ; \
-   dh_link -p libopenmpi3 
$(LIBDIR)/libmpi_usempif08-flang.so.40.30.0   
$(LIBDIR)/openmpi/lib/libmpi_usempif08-flang.so.40   ; \
+   dh_link -p libopenmpi3t64 
$(LIBDIR)/libmpi_usempif08-flang.so.40.30.0   
$(LIBDIR)/openmpi/lib/libmpi_usempif08-flang.so.40   ; \
dh_link -p libopenmpi-dev 
$(LIBDIR)/libmpi_usempif08-flang.so.40.30.0   
$(FLANG_LIBDIR)/openmpi/lib/libmpi_usempif08.so ; \
-   dh_link -p libopenmpi3 
$(LIBDIR)/libmpi_usempi_ignore_tkr-flang.so.40.30.0  
$(LIBDIR)/openmpi/lib/libmpi_usempi_ignore_tkr-flang.so.40 ; \
+   dh_link -p libopenmpi3t64 
$(LIBDIR)/libmpi_usempi_ignore_tkr-flang.so.40.30.0  
$(LIBDIR)/openmpi/lib/libmpi_usempi_ignore_tkr-flang.so.40 ; \
dh_link -p libopenmpi-dev 
$(LIBDIR)/libmpi_usempi_ignore_tkr-flang.so.40.30.0   
$(FLANG_LIBDIR)/openmpi/lib/libmpi_usempi_ignore_tkr.so ; \
) || true
 #  patchelf  --set-soname libmpi_mpifh-flang.so.40 
$(DESTDIR)/$(LIBDIR)/openmpi/lib/libmpi_mpifh-flang.so.40.30.0 ; \
@@ -231,8 +231,8 @@
dh_installman -p openmpi-bin 
$(DESTDIR)/usr/share/man/man1/oshCC.1 ; \
dh_installman -p openmpi-bin 
$(DESTDIR)/usr/share/man/man1/oshc++.1 ; \
dh_installman -p openmpi-bin 
$(DESTDIR)/usr/share/man/man1/oshcxx.1 ; \
-   dh_install -p libopenmpi3 
$(LIBDIR)/openmpi/lib/liboshmem.so.40.30.3 $(LIBDIR) ; \
-dh_link -p libopenmpi3 $(LIBDIR)/liboshmem.so.40.30.3  
$(LIBDIR)/liboshmem.so.40 ; \
+   dh_install -p libopenmpi3t64 
$(LIBDIR)/openmpi/lib/liboshmem.so.40.30.3 $(LIBDIR) ; \
+   dh_link -p libopenmpi3t64 $(LIBDIR)/liboshmem.so.40.30.3  
$(LIBDIR)/liboshmem.so.40 ; \
dh_link -p libopenmpi-dev   $(LIBDIR)/liboshmem.so.40  
$(LIBDIR)/openmpi/lib/liboshmem.so ; \
dh_link -p libopenmpi-dev   $(LIBDIR)/liboshmem.so.40  
$(LIBDIR)/liboshmem.so ; \
fi
@@ -240,45 +240,45 @@
dh_install -p openmpi-bin /usr/bin/mpijavac ; \
dh_install -p openmpi-bin usr/bin/mpijavac.pl ; \
dh_installman openmpi-bin 
$(DESTDIR)/usr/share/man/man1/mpijavac.1 ; \
-   dh_install -p libopenmpi3 
$(LIBDIR)/openmpi/lib/libmpi_java.so.40.30.0 $(LIBDIR); \
-   dh_link -p libopenmpi3 $(LIBDIR)/libmpi_java.so.40.30.0  
$(LIBDIR)/libmpi_java.so.40 ; \
+   dh_install -p libopenmpi3t64 
$(LIBDIR)/openmpi/lib/libmpi_java.so.40.30.0 $(LIBDIR); \
+   dh_link -p libopenmpi3t64 $(LIBDIR)/libmpi_java.so.40.30.0  
$(LIBDIR)/libmpi_java.so.40 ; \
dh_link -p libopenmpi-dev $(LIBDIR)/libmpi_java.so.40   
$(LIBDIR)/openmpi/lib/libmpi_java.so ; \
dh_link -p libopenmpi-dev $(LIBDIR)/libmpi_java.so.40   
$(LIBDIR)/libmpi_java.so ; \
fi
if test -f 
$(DESTDIR)/$(LIBDIR)/openmpi/lib/libmca_common_ucx.so.40.30.2 ; then \
-   dh_install -p libopenmpi3 
$(LIBDIR)/openmpi/lib/libmca_common_ucx.so.40.30.2 $(LIBDIR); \
-   dh_link -p libopenmpi3 $(LIBDIR)/libmca_common_ucx.so.40.30.2  
$(LIBDIR)/libmca_common_ucx.so.40 ; \
+   dh_install -p libopenmpi3t64 
$(LIBDIR)/openmpi/lib/libmca_common_ucx.so.40.30.2 $(LIBDIR); \
+   dh_link -p libopenmpi3t64 
$(LIBDIR)/libmca_common_ucx.so.40.30.2  $(LIBDIR)/libmca_common_ucx.so.40 ; \
 

Bug#1066836: libcamera: ftbfs with 64-bit time_t

[Steve Langasek]

Package: libcamera
Version: 0.2.0-1
Severity: serious
Tags: patch
Justification: ftbfs
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch

Dear maintainers,

libcamera fails to build from source on 32-bit architectures under 64-bit
time_t, because it has a module that legitimately un-sets _FILE_OFFSET_BITS
for building but this is not allowed without also unsetting _TIME_BITS:

[...]
[267/430] c++ -Isrc/v4l2/v4l2-compat.so.p -Isrc/v4l2 -I../src/v4l2 -Iinclude 
-I../include -Iinclude/libcamera/ipa -Iinclude/libcamera 
-fdiagnostics-color=always -Wall -Winvalid-pch -Wextra -Werror -std=c++17 
-Wno-redundant-move -Wno-psabi -Wshadow -include 
/<>/obj-arm-linux-gnueabihf/config.h -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fno-stack-clash-protection 
-fdebug-prefix-map=/<>=/usr/src/libcamera-0.2.0-1ubuntu3 
-Wno-error -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 
-Wdate-time -D_FORTIFY_SOURCE=3 -fPIC -DLIBCAMERA_BASE_PRIVATE 
-U_FILE_OFFSET_BITS -D_FILE_OFFSET_BITS=32 -D_LARGEFILE64_SOURCE 
-fvisibility=hidden -MD -MQ src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -MF 
src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o.d -o 
src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -c ../src/v4l2/v4l2_camera.cpp
FAILED: src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o 
c++ -Isrc/v4l2/v4l2-compat.so.p -Isrc/v4l2 -I../src/v4l2 -Iinclude -I../include 
-Iinclude/libcamera/ipa -Iinclude/libcamera -fdiagnostics-color=always -Wall 
-Winvalid-pch -Wextra -Werror -std=c++17 -Wno-redundant-move -Wno-psabi 
-Wshadow -include /<>/obj-arm-linux-gnueabihf/config.h -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fno-stack-clash-protection 
-fdebug-prefix-map=/<>=/usr/src/libcamera-0.2.0-1ubuntu3 
-Wno-error -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 
-Wdate-time -D_FORTIFY_SOURCE=3 -fPIC -DLIBCAMERA_BASE_PRIVATE 
-U_FILE_OFFSET_BITS -D_FILE_OFFSET_BITS=32 -D_LARGEFILE64_SOURCE 
-fvisibility=hidden -MD -MQ src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -MF 
src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o.d -o 
src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -c ../src/v4l2/v4l2_camera.cpp
In file included from /usr/include/features.h:394,
 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/bits/requires_hosted.h:31,
 from /usr/include/c++/13/deque:60,
 from ../src/v4l2/v4l2_camera.h:10,
 from ../src/v4l2/v4l2_camera.cpp:8:
/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"
  | ^
[...]

  
(https://launchpad.net/ubuntu/+source/libcamera/0.2.0-1ubuntu3/+build/27902670)

Since this is a legitimate un-setting of _FILE_OFFSET_BITS in order to get
access to the necessary libc6 prototypes and macros, and since the functions
being intercepted are not sensitive to time_t, the simplest solution is to
also unset _TIME_BITS.

Please see the attached patch, which has been uploaded to Ubuntu to fix this
build failure.

Thanks for considering,
-- 
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
diff -Nru libcamera-0.2.0/debian/control libcamera-0.2.0/debian/control
--- libcamera-0.2.0/debian/control  2024-01-17 13:27:50.0 -0800
+++ libcamera-0.2.0/debian/control  2024-03-13 22:27:39.0 -0700
@@ -1,7 +1,6 @@
 Source: libcamera
 Priority: optional
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Debian Multimedia Maintainers 

+Maintainer: Debian Multimedia Maintainers 
 Uploaders: Emmanuel Arias ,
IOhannes m zmölnig (Debian/GNU) ,
Andrej Shadura ,
diff -Nru libcamera-0.2.0/debian/patches/64-bit-time-t-compat.patch 
libcamera-0.2.0/debian/patches/64-bit-time-t-compat.patch
--- libcamera-0.2.0/debian/patches/64-bit-time-t-compat.patch   1969-12-31 
16:00:00.0 -0800
+++ libcamera-0.2.0/debian/patches/64-bit-time-t-compat.patch   2024-03-13 
22:27:33.0 -0700
@@ -0,0 +1,21 @@
+Description: 64-bit time_t compatibility for v4l2 module
+ The v4l2 build unsets _FILE_OFFSET_BITS, which is not allowed when setting
+ _TIME_BITS=64.  Having verified that nothing in this module is sensitive to
+ 64-bit time_t (none of the functions it intercepts handle time), we also
+ unset _TIME_BITS to allow this to build as before.
+Author: Steve Langasek 
+Forwarded: no
+Last-Update: 2024-03-13
+
+Index: libcamera-0.2.0/src/v4l2/meson.build

Bug#1066430: namazu2: FTBFS: ld: ../nmz/.libs/libnmz.so: undefined reference to `_nmz_memcmp'

[Takatsugu Nokubi]

On Wed, 13 Mar 2024 13:03:57 +0100 Lucas Nussbaum  wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
> > /bin/bash ../libtool  --tag=CC   --mode=link gcc  -g -O2 
> > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> > -fstack-protector-strong -fstack-clash-protection -Wformat 
> > -Werror=format-security -fcf-protection -Wall -pedantic  -Wl,-z,relro 
> > -Wl,-z,now -o namazu.cgi form.o namazu.o output.o rcfile.o charset.o 
> > result.o usage.o cgi.o namazu-cgi.o ../nmz/libnmz.la ../lib/libnmzut.a  -lm
> > libtool: link: gcc -g -O2 -Werror=implicit-function-declaration 
> > -ffile-prefix-map=/<>=. -fstack-protector-strong 
> > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> > -Wall -pedantic -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/namazu.cgi form.o 
> > namazu.o output.o rcfile.o charset.o result.o usage.o cgi.o namazu-cgi.o  
> > ../nmz/.libs/libnmz.so ../lib/libnmzut.a -lm
> > libtool: link: gcc -g -O2 -Werror=implicit-function-declaration 
> > -ffile-prefix-map=/<>=. -fstack-protector-strong 
> > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> > -Wall -pedantic -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/namazu form.o 
> > namazu.o output.o rcfile.o charset.o result.o usage.o namazu-cmd.o  
> > ../nmz/.libs/libnmz.so ../lib/libnmzut.a -lm
> > /usr/bin/ld: ../nmz/.libs/libnmz.so: undefined reference to `_nmz_memcmp'
> > /usr/bin/ld: ../nmz/.libs/libnmz.so: undefined reference to `_nmz_memcmp'
> > collect2: error: ld returned 1 exit status

It was caused by configure script, checking memcmp function:

conftest.c:72:5: note: include '' or provide a declaration of 'exit'
cc1: some warnings being treated as errors
configure:15824: $? = 1
configure: program exited with status 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "namazu"
| #define PACKAGE_TARNAME "namazu"
| #define PACKAGE_VERSION "2.0.21"
| #define PACKAGE_STRING "namazu 2.0.21"
| #define PACKAGE_BUGREPORT "bug-nam...@namazu.org"
| #define PACKAGE_URL ""
| #define PACKAGE "namazu"
| #define VERSION "2.0.21"
| #define MAILING_ADDRESS "bug-nam...@namazu.org"
| #define TRAC_URI "http://www.namazu.org/trac-namazu/trac.cgi;
| #define COPYRIGHT "Copyright (C) 1997-1999 Satoru Takabayashi All
rights reserved.\nCopyright (C) 2000-2011 Namazu Project All rights
reserved."
| #define HAVE_STDIO_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_SYS_PARAM_H 1
| #define STDC_HEADERS 1
| #define HAVE_DLFCN_H 1
| #define LT_OBJDIR ".libs/"
| #define ENABLE_NLS 1
| #define HAVE_GETTEXT 1
| #define HAVE_DCGETTEXT 1
| #define HAVE_LC_MESSAGES 1
| #define HAVE_LIBM 1
| #define HAVE_FCNTL_H 1
| #define HAVE_LIMITS_H 1
| #define HAVE_MALLOC_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_STRING_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_LOCALE_H 1
| #define HAVE_ERRNO_H 1
| #define SIZEOF_INT 4
| #define SIZEOF_LONG 8
| #define SIZEOF_LONG_LONG 8
| #define HAVE_ALLOCA_H 1
| #define HAVE_ALLOCA 1
| #define HAVE_GETPAGESIZE 1
| #define HAVE_VPRINTF 1
| #define HAVE_MMAP 1
| /* end confdefs.h.  */
|
| main()
| {
|   /* Some versions of memcmp are not 8-bit clean.  */
|   char c0 = 0x40, c1 = 0x80, c2 = 0x81;
|   if (memcmp(, , 1) >= 0 || memcmp(, , 1) >= 0)
| exit (1);
|
|   /* The Next x86 OpenStep bug shows up only when comparing 16 bytes
|  or more and with at least one buffer not starting on a 4-byte boundary.
|  William Lewis provided this test program.   */
|   {
| char foo[21];
| char bar[21];
| int i;
| for (i = 0; i < 4; i++)
|   {
|  char *a = foo + i;
|  char *b = bar + i;
|  strcpy (a, "0111");
|  strcpy (b, "1000");
|  if (memcmp (a, b, 16) >= 0)
|exit (1);
|   }
| exit (0);
|   }
| }
|
configure:15835: result: no

The test program didn't include stdlib.h, so
-Werror=implicit-function-declaration caused error then the script
check failed.
I'll try to make a workaround.

Bug#1060915: golang-entgo-ent: Flaky tests due to relying on default result ordering

[Cyril Brulebois]

Hi Paul,

Paul Mars  (2024-01-16):
> Here is a patch to fix the issue.

Sorry, I didn't spot this bug report right away (its metadata got
adjusted along the way). Thanks for the bug report and the patch,
on their way to unstable!


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/


signature.asc
Description: PGP signature

Bug#986936: ITA: libcdk5 -- C-based curses widget library

[Steven Robbins]

Control: owner 986936 !

On Tue, 19 Jul 2022 13:02:08 +0200 "Jose G. López"  
wrote:
> owner 986936 !
> retitle 986936 ITA: libcdk5 -- C-based curses widget library
> thanks
> I intend to adopt it as I worked on it before but never uploaded it as
> maintainer in Debian. I have special affection for it because it was
> one of the first packages I worked with and learned.
> 

Hi again Jose,

I don't mean to take anything away from you, if you truly desire to maintain 
this package.  However, it's been over 18 months with no apparent action and 
emails to you over the last week have not been answered.  So I will 
tentatively conclude that you don't have the time for this package.  If that 
changes, do let me know and you can certainly change the maintainership.

For now, I will adopt this package and upload a new version to unblock this 
package and downstream dependencies.

Best,
-Steve


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

Bug#1064588: bookworm-pu: package glibc/2.36-9+deb12u5

[Cyril Brulebois]

Hi,

Aurelien Jarno  (2024-03-13):
> The date of the next point release is slowly approaching, could you
> please have a look at this?

Sorry, lost track of that one. Feel free to upload.


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


signature.asc
Description: PGP signature

Bug#1066832: Debian #1066832: [fsverity-utils] hard Build-Depends on unportable package pandoc

[Thorsten Glaser]

Dixi quod…

>Please split the package so that the part that requires pandoc is
>done in an arch:all build. Normally, pandoc is needed only for
>documentation, which is often easy enough to split off in a -doc
>binary package, which can then move to B-D-Indep and be built on
>amd64 or whatever hosts.

Looking at this in some detail, this is *only* ONE manual page.
Splitting into a separate package for one file will not go over
well with ftpmaster.

Dear upstream, please consider keeping the manpage in something
else, like mdoc. I would be willing to convert the manpage to
semantic, readable mdoc for you, even.

(fsverity-utils is a Build-Depends of rpm, some subpackages of
which are necessary to build other software even in Debian.)

If upstream is not willing, we could:

• do this as local patch (effort updating it every time)

• hack a script that converts man/fsverity.1.md to mdoc;
  this doesn’t need to be a full converter, it needs to
  just be good enough to convert this one page (effort
  one-time, but probably not much if at all when updating)

• as package maintainer, run the pandoc conversion script
  and put the result into debian/fsverity.1 and install
  from there and stop B-D’ing on pandoc (needs some, but
  not much, manual effort on each update, and the package
  maintainer to have a clean sid system on which to do that)

• install a dummy manpage (that maybe summarises the options
  and points the reader to
  https://manpages.debian.org/unstable/fsverity/fsverity.1.en.html
  for the full page) on architectures without pandoc (needs
  a bit of initial hacking, and to keep a whitelist of arches
  with pandoc up-to-date)

bye,
//mirabilos
-- 
21:12⎜ sogar bei opensolaris haben die von der community so
ziemlich jeden mist eingebaut │ man sollte unices nich so machen das
desktopuser zuviel intresse kriegen │ das macht die code base kaputt
21:13⎜ linux war früher auch mal besser :D

Bug#1050393: Unneeded dependency on "dconf-gsettings-backend | gsettings-backend"?

[Xiyue Deng]

Xiyue Deng  writes:

> Control: tags -1 patch
>
> Hi,
>
> It looks like the gsettings-backend dependency was introduced since
> Emacs 29.1.  Tried to debug this a little, and it looks like the
> dependencies was pulled in through ${misc:Depends} due to the GSettings
> schema file[1].  With helps from folks on IRC, we found that this file
> was installed only in PGTK mode[2], so technically this is not required
> by other modes and should be safe to be moved from emacs-common to
> emacs-pgtk.
>
> I have prepared a MR[3] (patch also attached) as an attempt and verified
> that it moved the "dconf-gsettings-backend | gsettings-backend" from
> emacs-common to emacs-pgtk.  I'll try to use this locally with emacs-nox
> to further verify that it doesn't cause any issues.
>
> Meanwhile, would be great to have people review the patch.  TIA!
>
> [1] Search for
> "/usr/share/glib-2.0/schemas/org.gnu.emacs.defaults.gschema.xml" on
> https://packages.debian.org/sid/all/emacs-common/filelist
>
> [2] 
> https://salsa.debian.org/rlb/deb-emacs/-/blob/deb/emacs/d/sid/master/Makefile.in?ref_type=heads#L1334-1337
>
> [3] https://salsa.debian.org/rlb/deb-emacs/-/merge_requests/12

I have made a few updates to the merge request, and please see the
updated patch attached.  Do refer to the merge request[1] for the latest
updates.

[1] https://salsa.debian.org/rlb/deb-emacs/-/merge_requests/12
-- 
Xiyue Deng
>From 5fbec288a2c0c3fa54e100362155268ed40373e3 Mon Sep 17 00:00:00 2001
From: Xiyue Deng 
Date: Wed, 13 Mar 2024 10:22:46 -0700
Subject: [PATCH] Install GSettings schema in pgtk build only (Closes:
 #1050393)

* In PGTK build it generates the GSettings schema file
"/usr/share/glib-2.0/schemas/org.gnu.emacs.defaults.gschema.xml" which
is not needed in other variant.
* Move the file from emacs-common to emacs-pgtk, and adds proper
breaks/replaces/conflicts to ensure a smooth upgrade.
---
 debian/changelog |  7 +++
 debian/control   | 12 ++--
 debian/rules |  9 -
 3 files changed, 25 insertions(+), 3 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index c53984fc648..960672b6297 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+emacs (1:29.2+1-3) UNRELEASED; urgency=medium
+
+  * Team upload.
+  * Install GSettings schema in pgtk build only (Closes: #1050393)
+
+ -- Xiyue Deng   Wed, 13 Mar 2024 10:22:10 -0700
+
 emacs (1:29.2+1-2) unstable; urgency=medium
 
   * Fix Breaks/Replaces by prepending missing epoch (Closes: #1064851)
diff --git a/debian/control b/debian/control
index e168717089f..0c6fab0bfeb 100644
--- a/debian/control
+++ b/debian/control
@@ -138,8 +138,15 @@ Provides: editor, emacs, emacsen, info-browser, mail-reader, news-reader
 Recommends: fonts-noto-color-emoji
 Suggests: emacs-common-non-dfsg
 Conflicts: emacs-gtk, emacs-lucid, emacs-nox
-Replaces: emacs-gtk, emacs-lucid, emacs-nox, emacs-bin-common (<< 1:29.2)
-Breaks: emacs-bin-common (<< 1:29.2)
+Replaces:
+ emacs-gtk,
+ emacs-lucid,
+ emacs-nox,
+ emacs-bin-common (<< 1:29.2),
+ emacs-common (<< 1:29.2+1-3~),
+Breaks:
+ emacs-bin-common (<< 1:29.2),
+ emacs-common (<< 1:29.2+1-3~),
 Description: GNU Emacs editor (with GTK+ Wayland GUI support)
  GNU Emacs is the extensible self-documenting text editor.  This
  package contains a version of Emacs with a graphical user interface
@@ -184,6 +191,7 @@ Breaks:
  emacs-gtk (<< 1:25),
  emacs-lucid (<< 1:25),
  emacs-nox (<< 1:25),
+ emacs-pgtk (<< 1:29.2+1-3~),
 Replaces:
  emacs-bin-common (<< 1:28)
 Description: GNU Emacs editor's shared, architecture independent infrastructure
diff --git a/debian/rules b/debian/rules
index 38965316f3d..8448d7c9be3 100755
--- a/debian/rules
+++ b/debian/rules
@@ -425,6 +425,9 @@ override_dh_auto_install: $(autogen_install_files)
 	  cp -a $(install_dir_pgtk)/* $(pkgdir_common)
 
 	  rm -r $(pkgdir_common)/usr/bin
+	  # PGTK builds a GSettings schema that is PGTK specific and
+	  # should not be shipped in emacs-common
+	  rm -r $(pkgdir_common)/usr/share/glib-2.0
 	  rm \
 	$(pkgdir_common)/$(libexec_dir_emacs)/hexl \
 	$(pkgdir_common)/$(libexec_dir_emacs)/emacs-*.pdmp \
@@ -548,7 +551,7 @@ override_dh_auto_install: $(autogen_install_files)
 
 ##
 # emacs-pgtk
-ifneq (,$(findstring emacs, $(shell dh_listpackages)))
+ifneq (,$(findstring emacs-pgtk, $(shell dh_listpackages)))
 	  $(call install_common_binpkg_bits,$(install_dir_pgtk),$(pkgdir_pgtk),emacs-pgtk,pgtk)
 
   # install desktop entries
@@ -557,6 +560,10 @@ override_dh_auto_install: $(autogen_install_files)
 	debian/emacs.desktop \
 	debian/emacs-term.desktop \
 	$(pkgdir_pgtk)/usr/share/applications/
+	  # install GSettings schema
+	  install -d $(pkgdir_pgtk)/usr/share/glib-2.0
+	  cp -a $(install_dir_pgtk)/usr/share/glib-2.0/* \
+	$(pkgdir_pgtk)/usr/share/glib-2.0
 endif
 
 ##
-- 

Bug#1066835: universal-ctags: please add support for loong64

[wuruilong]

Package: universal-ctags
Version: 5.9.20210829.0-1
Severity: normal
X-Debbugs-Cc: wuruil...@loongson.cn
User: debian-de...@lists.debian.org
Usertags: loong64

Dear Maintainer,

Universal-ctags has a compilation error in the loong64 architecture. 
The attached patch solves the problem. Please refer to it supports loong64 
architecture.

wuruilong

-- System Information:
Debian Release: trixie/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: loong64 (loongarch64)

Kernel: Linux 5.10.0-60.96.0.126.oe2203.loongarch64 (SMP w/32 CPU threads)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages universal-ctags depends on:
ii  libc62.37-15.1
ii  libjansson4  2.14-2+b1
ii  libseccomp2  2.5.4-1+loong64
ii  libxml2  2.9.14+dfsg-1.3+b1
ii  libyaml-0-2  0.2.5-1+b1

universal-ctags recommends no packages.

Versions of packages universal-ctags suggests:
ii  vim  2:9.1.0016-1+b1

-- no debconf information
Description: 
 TODO: Put a short summary on the line above and replace this paragraph
 with a longer explanation of this change. Complete the meta-information
 with other relevant fields (see below for details). To make it easier, the
 information below has been extracted from the changelog. Adjust it or drop
 it.
 .
 universal-ctags (5.9.20210829.0-1) unstable; urgency=medium
 .
   * New upstream release
 + Fix FTBFS with glibc 2.33 (Closes: #990784)
 + Fix etags segfault (Closes: #993509)
   * Add debian/watch file
   * Bump Standards-Version to 4.6.0 (no changes needed)
   * Add patch to avoid running git during tests
   * Update d/copyright
Author: Alessandro Ghedini 
Bug-Debian: https://bugs.debian.org/990784
Bug-Debian: https://bugs.debian.org/993509

---
The information above should follow the Patch Tagging Guidelines, please
checkout https://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: (upstream|backport|vendor|other), (|commit:)
Bug: 
Bug-Debian: https://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded: (no|not-needed|)
Applied-Upstream: , (|commit:)
Reviewed-By: 
Last-Update: 2024-03-14

--- universal-ctags-5.9.20210829.0.orig/main/seccomp.c
+++ universal-ctags-5.9.20210829.0/main/seccomp.c
@@ -41,7 +41,9 @@ int installSyscallFilter (void)
seccomp_rule_add (ctx, SCMP_ACT_ALLOW, SCMP_SYS (exit_group), 0);
 
// The bowels of stdio want to know the size of a file, even for stdout.
+#if(defined(__SNR_fstat) && __SNR_fstat)
seccomp_rule_add (ctx, SCMP_ACT_ALLOW, SCMP_SYS (fstat), 0);
+#endif
seccomp_rule_add (ctx, SCMP_ACT_ALLOW, SCMP_SYS (fstat64), 0);
 #ifdef __SNR_newfstatat
seccomp_rule_add (ctx, SCMP_ACT_ALLOW, SCMP_SYS (newfstatat), 0);

Bug#1065463: debootstrap can deal with native dpkg file replacement feature

[Steven Shiau]

On 3/5/2024 7:25 PM, Holger Levsen wrote:

On Tue, Mar 05, 2024 at 08:36:59AM +0800, Steven Shiau wrote:

debootstrap should be able to solve the libuuid1t64 dependency by installing
libuuid1 only.

just in case you are not aware, bootstrapping using either mmdebstrap or
cdebootstrap works atm. mmdebstrap is faster and mostly a drop-in replacement.
(same applies to cdebootstrap but its less faster :)

daily tests are available at:

https://jenkins.debian.net/job/reproducible_debootstrap_unstable/
https://jenkins.debian.net/job/reproducible_cdebootstrap_unstable/
https://jenkins.debian.net/job/reproducible_mmdebstrap_unstable/

Hi Holger,
Great. Thanks for this useful info.
We have patched Debian live-build and created a merger request to 
support mmdebostrap:

https://salsa.debian.org/live-team/live-build/-/merge_requests/343

Steven

--
Steven Shiau 
Public Key Server PGP Key ID: 4096R/163E3FB0
Fingerprint: EB1D D5BF 6F88 820B BCF5  356C 8E94 C9CD 163E 3FB0

Bug#1065961: sra-sdk: Please drop dependencies on python3-distutils

[Aaron M. Ucko]

Graham Inggs  writes:

> In fact, there is no module for Python 3.12 in python3-distutils, so
> these dependencies may already be unnecessary.

I hear you, but can't readily determine whether any additional changes
would be in order until dh-python drops or downgrades its distutils
dependency, which I called out just now:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066833

Thanks for the report, though!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#1066834: libopenmpi3t64: libs are missing after 64-bit time_t transition

[Damir R. Islamov]

Package: libopenmpi3t64
Version: 4.1.6-5.1
Severity: important

Dear Maintainer,

After libopenmpi3 package renaming due to 64-bit time_t transition
some .so libs are lost because they are installed/soft linked manually by
debian/rules script.
The list of lost files are:
$(LIBDIR)/libmca_common_libfabric.so.40*
$(LIBDIR)/libmca_common_monitoring.so.50*
$(LIBDIR)/libmca_common_ofi.so.10*
$(LIBDIR)/libmca_common_ompio.so.41*
$(LIBDIR)/libmca_common_ucx.so.40*
$(LIBDIR)/libmca_common_verbs.so.40*
$(LIBDIR)/libmpi_java.so.40*
$(LIBDIR)/libmpi_mpifh-flang.so.40.30.0 
$(LIBDIR)/libmpi_usempif08-flang.so.40.30.0 
$(LIBDIR)/libmpi_usempi_ignore_tkr-flang.so.40.30.0 
$(LIBDIR)/liboshmem.so.40*
$(LIBDIR)/openmpi/lib/libmca_common_libfabric.so.40.30.0 
$(LIBDIR)/openmpi/lib/libmca_common_monitoring.so.50.20.0 
$(LIBDIR)/openmpi/lib/libmca_common_ofi.so.10.0.2 
$(LIBDIR)/openmpi/lib/libmca_common_ompio.so.41.29.4 
$(LIBDIR)/openmpi/lib/libmca_common_ucx.so.40.30.2 
$(LIBDIR)/openmpi/lib/libmca_common_verbs.so.40.30.0 
$(LIBDIR)/openmpi/lib/libmpi_java.so.40.30.0 
$(LIBDIR)/openmpi/lib/libmpi_mpifh-flang.so.40
$(LIBDIR)/openmpi/lib/libmpi_usempif08-flang.so.40
$(LIBDIR)/openmpi/lib/libmpi_usempi_ignore_tkr-flang.so.40
$(LIBDIR)/openmpi/lib/liboshmem.so.40.30.3

A possible solution is correcting the package name in d/rules.

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

Kernel: Linux 6.6.15-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 libopenmpi3t64 depends on:
ii  libc6   2.37-15.1
ii  libevent-core-2.1-7t64  2.1.12-stable-8.1+b1
ii  libevent-pthreads-2.1-7t64  2.1.12-stable-8.1+b1
ii  libfabric1  1.17.0-3
ii  libgcc-s1   14-20240303-1
ii  libhwloc-plugins2.10.0-1+b1
ii  libhwloc15  2.10.0-1+b1
ii  libibverbs1 50.0-2
ii  libnl-3-200 3.7.0-0.3
ii  libpmix25.0.1-4+b1
ii  libpsm-infinipath1  3.3+20.604758e7-6.3
ii  libpsm2-2   11.2.185-2
ii  libstdc++6  14-20240303-1
ii  libucx0 1.16.0+ds-4
ii  zlib1g  1:1.3.dfsg-3.1

libopenmpi3t64 recommends no packages.

libopenmpi3t64 suggests no packages.

-- no debconf information

Bug#1066833: dh-python: depends on legacy python3-distutils

[Aaron M. Ucko]

Package: dh-python
Version: 6.20240310
Severity: important

I'm sure I'm not alone in having a request [1] to ensure a package
builds without legacy python3-distutils.  However, sra-sdk, for one,
uses dh-python, which still depends on python3-distutils.  As such,
removing the explicit build dependency wouldn't yet break anything,
but I can't readily tell what would happen with python3-distutils
actually out of the picture.  Consequently, I'd appreciate it if
dh-python could please go ahead and either downgrade or outright
remove its dependency on python3-distutils to facilitate determining
what actually still needs it.

Thanks!

[1] https://bugs.debian/org/1065961

-- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'proposed-updates-debug'), (500, 'oldstable-security'), 
(500, 'testing'), (300, 'unstable-debug'), (300, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, x32

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

Versions of packages dh-python depends on:
ii  python3 3.11.6-1
ii  python3-distutils   3.11.5-1
ii  python3-setuptools  68.1.2-2

dh-python recommends no packages.

Versions of packages dh-python suggests:
ii  dpkg-dev   1.22.4
ii  flit   3.9.0-2
ii  libdpkg-perl   1.22.4
ii  python3-build  1.0.3-2
ii  python3-installer  0.7.0+dfsg1-2
ii  python3-wheel  0.42.0-1

-- debconf-show failed

Bug#1066832: fsverity-utils: hard Build-Depends on unportable package pandoc

[Thorsten Glaser]

Source: fsverity-utils
Version: 1.5-1.1
Severity: important
Justification: RC for Debian-Ports
X-Debbugs-Cc: t...@mirbsd.de, debian-po...@lists.debian.org

Recent versions of fsverity-utils (larger than 1.4-1~exp1 anyway)
have a Build-Depends-Arch on pandoc; however, pandoc is an extremely
unportable package written in a hard to port language.

Please split the package so that the part that requires pandoc is
done in an arch:all build. Normally, pandoc is needed only for
documentation, which is often easy enough to split off in a -doc
binary package, which can then move to B-D-Indep and be built on
amd64 or whatever hosts.

Thanks,
//mirabilos

Bug#1066279: [Debian-zh-dev] Bug#1066279: unicon: FTBFS: cin2tab.c:238:13: error: implicit declaration of function ‘tolower’ [-Werror=implicit-function-declaration]

[肖盛文]

Hi,

Thanks for your report.

I'd uploaded the new version in mentors to fix this bug.

https://mentors.debian.net/package/unicon/

Welcome to review and upload.

Thanks!

在 2024/3/13 19:46, Lucas Nussbaum 写道:

Source: unicon
Version: 3.0.4+dfsg1-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User:lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

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):

gcc -fPIC -g -Wall -I../../include -I. -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 -c -g -I../../include -I. cin2tab.c -o cin2tab.o
cin2tab.c: In function ‘get_line’:
cin2tab.c:80:16: warning: pointer targets in passing argument 1 of ‘fgets’ 
differ in signedness [-Wpointer-sign]
80 | fgets (tt, 128, fr);
   |^~
   ||
   |u_char * {aka unsigned char *}
In file included from /usr/include/stdio.h:906,
  from cin2tab.c:27:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:209:25: note: expected ‘char * 
restrict’ but argument is of type ‘u_char *’ {aka ‘unsigned char *’}
   209 | fgets (char *__restrict __s, int __n, FILE *__restrict __stream)
   |~^~~
cin2tab.c: In function ‘cmd_arg’:
cin2tab.c:96:18: warning: pointer targets in passing argument 1 of ‘skip_space’ 
differ in signedness [-Wpointer-sign]
96 | s=skip_space(s);
   |  ^
   |  |
   |  u_char * {aka unsigned char *}
cin2tab.c:50:24: note: expected ‘char *’ but argument is of type ‘u_char *’ 
{aka ‘unsigned char *’}
50 | char *skip_space(char *s)
   |  ~~^
cin2tab.c:96:6: warning: pointer targets in assignment from ‘char *’ to ‘u_char 
*’ {aka ‘unsigned char *’} differ in signedness [-Wpointer-sign]
96 | s=skip_space(s);
   |  ^
cin2tab.c:97:16: warning: pointer targets in passing argument 1 of ‘to_space’ 
differ in signedness [-Wpointer-sign]
97 | t=to_space(s);
   |^
   ||
   |u_char * {aka unsigned char *}
cin2tab.c:56:22: note: expected ‘char *’ but argument is of type ‘u_char *’ 
{aka ‘unsigned char *’}
56 | char *to_space(char *s)
   |~~^
cin2tab.c:100:13: warning: pointer targets in assignment from ‘char *’ to 
‘u_char *’ {aka ‘unsigned char *’} differ in signedness [-Wpointer-sign]
   100 | *arg=t;
   | ^
cin2tab.c:107:9: warning: pointer targets in assignment from ‘char *’ to 
‘u_char *’ {aka ‘unsigned char *’} differ in signedness [-Wpointer-sign]
   107 | *arg=t;
   | ^
cin2tab.c: In function ‘main’:
cin2tab.c:194:13: warning: pointer targets in passing argument 1 of ‘cmd_arg’ 
differ in signedness [-Wpointer-sign]
   194 | cmd_arg(tt, , );
   | ^~
   | |
   | char *
cin2tab.c:89:22: note: expected ‘u_char *’ {aka ‘unsigned char *’} but argument 
is of type ‘char *’
89 | void cmd_arg(u_char *s, u_char **cmd, u_char **arg)
   |  ^
cin2tab.c:195:16: warning: pointer targets in passing argument 1 of ‘strcmp’ 
differ in signedness [-Wpointer-sign]
   195 | if (strcmp(cmd,"%ename") || !(*arg) )
   |^~~
   ||
   |u_char * {aka unsigned char *}
In file included from cin2tab.c:30:
/usr/include/string.h:156:32: note: expected ‘const char *’ but argument is of 
type ‘u_char *’ {aka ‘unsigned char *’}
   156 | extern int strcmp (const char *__s1, const char *__s2)
   |^~~~
cin2tab.c:198:27: warning: pointer targets in passing argument 2 of ‘strcpy’ 
differ in signedness [-Wpointer-sign]
   198 | strcpy(InpTable.ename,arg);
   |   ^~~
   |   |
   |   u_char * {aka unsigned char *}
In file included from /usr/include/features.h:490,
  from 
/usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
  from /usr/include/stdio.h:27:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:77:1: note: expected 
‘const char * restrict’ but argument is of type ‘u_char *’ {aka ‘unsigned char 
*’}
77 | __NTH (strcpy (char *__restrict __dest, const char *__restrict __src))
   | ^
cin2tab.c:200:13: warning: pointer targets in passing argument 1 of ‘cmd_arg’ 
differ in signedness [-Wpointer-sign]
   200 

Bug#1066831: nbd-server: Crash on -C /dev/null or -C /missing/file

[Hilko Bengen]

Package: nbd-client
Version: 1:3.26.1-1
Severity: serious
Tags: patch
X-Debbugs-Cc: none, Hilko Bengen 

Dear Maintainer,

While investigating libnbd build failures (see ##1066766), I stumbled
across a bug that makes nbd-server crash without an error message when
trying to read its configuration from /dev/null or any non-existing
file:

$ ./nbd-server -C /dev/null 
Segmentation fault

It turns out that one g_key_file_free() call was left in the code when
auto-freeing was introduced in upstream commit
ab41c4f5a91857d9466d83ea062ec60435f7eaa0. The attached patch fixes this.

Cheers,
-Hilko
Index: nbd-3.26.1/nbd-server.c
===
--- nbd-3.26.1.orig/nbd-server.c
+++ nbd-3.26.1/nbd-server.c
@@ -881,7 +881,6 @@ GArray* parse_cfile(gchar* f, struct gen
 			G_KEY_FILE_KEEP_TRANSLATIONS, )) {
 		g_set_error(e, NBDS_ERR, NBDS_ERR_CFILE_NOTFOUND, "Could not open config file %s: %s",
 f, err->message);
-		g_key_file_free(cfile);
 		return retval;
 	}
 	startgroup = g_key_file_get_start_group(cfile);

Bug#1066830: xfig: Ignores "print only active" checkbox in print dialog

[Dennis Boone]

Package: xfig
Version: 1:3.2.9-2+b1
Severity: normal
X-Debbugs-Cc: d...@msu.edu

Dear Maintainer,

Disabling a layer by unchecking it in the right column, then entering
the print dialog and checking "print only active", produces a print
that includes the disabled layer.  If I instead export to postscript
with the same settings, the resulting file is correct.


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

Kernel: Linux 6.6.11-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=es_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 xfig depends on:
ii  fig2dev  1:3.2.9-3+b1
ii  libc62.37-15.1
ii  libfontconfig1   2.15.0-1.1
ii  libgs10  10.02.1~dfsg-3+b1
ii  libjpeg62-turbo  1:2.1.5-2+b2
ii  libpng16-16t64   1.6.43-3
ii  libtiff6 4.5.1+git230720-4
ii  libx11-6 2:1.8.7-1
ii  libxft2  2.3.6-1+b1
ii  libxi6   2:1.8.1-1
ii  libxpm4  1:3.5.17-1
ii  libxt6t641:1.2.1-1.2
ii  sensible-utils   0.0.22
ii  xaw3dg   1.5+F-1.1+b1
ii  xdg-utils1.1.3-4.1

Versions of packages xfig recommends:
ii  xfig-libs  1:3.2.9-2

Versions of packages xfig suggests:
ii  cups-bsd [lpr]2.4.7-1.2+b1
ii  cups-client   2.4.7-1.2+b1
ii  fonts-urw-base35  20200910-8
ii  ghostscript   10.02.1~dfsg-3+b1
ii  netpbm2:11.05.02-1.1
pn  spell 
pn  xfig-doc  

-- no debconf information

Bug#1066829: ITP: assetfinder -- Find domains and subdomains related to a given domain

[aquilamacedo]

Package: wnpp
X-Debbugs-Cc: debian-de...@lists.debian.org
Owner: Aquila Macedo Costa 
Severity: wishlist

* Package name: assetfinder
  Version : 0.1.1
  Upstream Contact: Tom Hudson 
* URL : https://github.com/tomnomnom/assetfinder
* License : MIT 
  Programming Lang: Golang
  Description : Find domains and subdomains related to a given
domain

assetfinder is a command-line tool to find domains and subdomains
potentially
related to a specified domain. Enhances domain discovery for
comprehensive analysis.

I'm writing to submit an Intention to Package (ITP) for assetfinder
under
the pkg-security team's umbrella.

Bug#1059909: Enable shell completion for wormhole-william

[Taavi Väänänen]

tags 1059909 patch
thanks

Hi, I've attached a patch to implement this.

Taavi
From 7f4476171c2dbc3c5be9050972618d58a4ef0e86 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Taavi=20V=C3=A4=C3=A4n=C3=A4nen?= 
Date: Thu, 14 Mar 2024 01:57:47 +0200
Subject: [PATCH] Install shell completion files

---
 debian/changelog| 7 +++
 debian/control  | 1 +
 debian/rules| 9 +
 debian/wormhole-william.bash-completion | 1 +
 debian/wormhole-william.install | 4 
 5 files changed, 22 insertions(+)
 create mode 100644 debian/wormhole-william.bash-completion

diff --git a/debian/changelog b/debian/changelog
index f0186ed..140154d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+wormhole-william (1.0.6-4) UNRELEASED; urgency=medium
+
+  * Team upload
+  * Install shell completion files
+
+ -- Taavi Väänänen   Thu, 14 Mar 2024 01:56:57 +0200
+
 wormhole-william (1.0.6-3) unstable; urgency=medium
 
   * Disable flaky tests (Closes: #1031063)
diff --git a/debian/control b/debian/control
index fe9d1a4..8483572 100644
--- a/debian/control
+++ b/debian/control
@@ -6,6 +6,7 @@ Testsuite: autopkgtest-pkg-go
 Priority: optional
 Build-Depends: debhelper-compat (= 13),
dh-golang,
+   dh-sequence-bash-completion,
golang-any,
golang-debian-vasudev-gospake2-dev,
golang-github-cheggaaa-pb.v3-dev,
diff --git a/debian/rules b/debian/rules
index 45a362d..515665c 100755
--- a/debian/rules
+++ b/debian/rules
@@ -6,3 +6,12 @@ BINDIR=$(CURDIR)/debian/wormhole-william/usr/bin
 
 %:
 	dh $@ --builddirectory=_build --buildsystem=golang --with=golang
+
+override_dh_auto_build:
+	dh_auto_build
+
+	# Build shell completions
+	mkdir _build/completion _build/completion/bash _build/completion/fish _build/completion/zsh
+	_build/bin/wormhole-william completion bash > _build/completion/bash/wormhole-william
+	_build/bin/wormhole-william completion fish > _build/completion/fish/wormhole-william.fish
+	_build/bin/wormhole-william completion zsh > _build/completion/zsh/_wormhole-william
diff --git a/debian/wormhole-william.bash-completion b/debian/wormhole-william.bash-completion
new file mode 100644
index 000..3f72d51
--- /dev/null
+++ b/debian/wormhole-william.bash-completion
@@ -0,0 +1 @@
+_build/completion/bash/wormhole-william wormhole-william
diff --git a/debian/wormhole-william.install b/debian/wormhole-william.install
index e772481..95bd017 100644
--- a/debian/wormhole-william.install
+++ b/debian/wormhole-william.install
@@ -1 +1,5 @@
 usr/bin
+# There is currently no fish or zsh equivalent of dh_bash-completion.
+# For zsh, see https://bugs.debian.org/921236
+_build/completion/fish/wormhole-william.fish /usr/share/fish/vendor_completions.d/
+_build/completion/zsh/_wormhole-william /usr/share/zsh/vendor-completions/
-- 
2.43.0



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1049711: Unable to reproduce

[Taavi Väänänen]

I'm not able to reproduce this, either. As far as I can tell from the 
code, this error would happen if there were two fully instances of this 
test running at the exact same time on the same host, but I don't think 
that was the case here?


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1066459: yiyantang: FTBFS: xmalloc.c:136:16: error: implicit declaration of function ‘strlen’ [-Werror=implicit-function-declaration]

[肖盛文]

Hi,

Thanks for your report.

I'd uploaded the new version in mentors to fix this bug.

https://mentors.debian.net/package/yiyantang/


Welcome to review and upload.

Thanks!

在 2024/3/13 19:59, Lucas Nussbaum 写道:

Source: yiyantang
Version: 0.7.0-8
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

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):

x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include 
-DG_LOG_DOMAIN=\"yyt\" -I../intl -I../intl  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
yiyantang_init.c
xmalloc.c: In function ‘xstrdup’:
xmalloc.c:136:16: error: implicit declaration of function ‘strlen’ 
[-Werror=implicit-function-declaration]
   136 |   p = xmalloc (strlen (str) + 1);
   |^~
xmalloc.c:48:1: note: include ‘’ or provide a declaration of ‘strlen’
47 | #include "error.h"
   +++ |+#include 
48 |
xmalloc.c:136:16: warning: incompatible implicit declaration of built-in 
function ‘strlen’ [-Wbuiltin-declaration-mismatch]
   136 |   p = xmalloc (strlen (str) + 1);
   |^~
xmalloc.c:136:16: note: include ‘’ or provide a declaration of 
‘strlen’
xmalloc.c:137:3: error: implicit declaration of function ‘strcpy’ 
[-Werror=implicit-function-declaration]
   137 |   strcpy (p, str);
   |   ^~
xmalloc.c:137:3: note: include ‘’ or provide a declaration of ‘strcpy’
xmalloc.c:137:3: warning: incompatible implicit declaration of built-in 
function ‘strcpy’ [-Wbuiltin-declaration-mismatch]
xmalloc.c:137:3: note: include ‘’ or provide a declaration of ‘strcpy’
loop.c: In function ‘loop’:
loop.c:91:25: error: implicit declaration of function ‘exit’ 
[-Werror=implicit-function-declaration]
91 | exit (ret);
   | ^~~~
loop.c:42:1: note: include ‘’ or provide a declaration of ‘exit’
41 | #include "zhconv.h"
   +++ |+#include 
42 |
loop.c:91:25: warning: incompatible implicit declaration of built-in function 
‘exit’ [-Wbuiltin-declaration-mismatch]
91 | exit (ret);
   | ^~~~
loop.c:91:25: note: include ‘’ or provide a declaration of ‘exit’
loop.c:117:33: warning: ignoring return value of ‘write’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
   117 | write (ptym, ibuf, ret);
   | ^~~
loop.c:162:41: warning: ignoring return value of ‘write’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
   162 | write (STDOUT_FILENO, tbuf2, 
ret);
   | 
^
cc1: some warnings being treated as errors
make[3]: *** [Makefile:201: xmalloc.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/yiyantang_0.7.0-8_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results

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

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

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


--
肖盛文 xiao sheng wen
https://www.atzlinux.com 《铜豌豆 Linux》基于 Debian 的 Linux 中文 桌面 操作系统
Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com
Debian salsa: https://salsa.debian.org/atzlinux-guest
GnuPG Public Key: 0x00186602339240CB



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1066814: plotly: Please upgrade to latest upstream version

[Josue Ortega]

On Wed, Mar 13, 2024 at 09:29:55PM +0100, Andreas Tille wrote:
> Source: plotly
> Version: 5.15.0+dfsg1-1
> Severity: normal
> 
> Hi,
> 
> I want to upgrade multiqc but this package requires a higher version of
> plotly as you can see in Salsa CI[1].  It would be great if you could
> upgrade the package.
> 
> BTW, I would consider it a good idea if plotly would be maintained in
> the Debian Python Team.
> 
> Kind regards
> Andreas.
> 
> [1] https://salsa.debian.org/med-team/multiqc/-/jobs/5442252
> 
> 
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (50, 'buildd-unstable'), 
> (1, 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 6.3.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_WARN
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=sh: 0: getcwd() 
> failed: No such file or directory
> UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled


Hey Andreas,

Hopefully, I'll be uploading the latest version next weekend. I've been quite
busy with $DAILY_JOB.

Cheers,

---
Josue Ortega
«Happy Hacking»


signature.asc
Description: PGP signature

Bug#1066113: guix: CVE-2024-27297

[Vagrant Cascadian]

On 2024-03-12, Vagrant Cascadian wrote:
> On 2024-03-12, Salvatore Bonaccorso wrote:
>> The following vulnerability was published for guix.
>>
>> CVE-2024-27297[0]:
>> | Nix is a package manager for Linux and other Unix systems. A fixed-
>> | output derivations on Linux can send file descriptors to files in
>> | the Nix store to another program running on the host (or another
>> | fixed-output derivation) via Unix domain sockets in the abstract
>> | namespace. This allows to modify the output of the derivation, after
>> | Nix has registered the path as "valid" and immutable in the Nix
>> | database. In particular, this allows the output of fixed-output
>> | derivations to be modified from their expected content. This issue
>> | has been addressed in versions 2.3.18 2.18.2 2.19.4 and 2.20.5.
>> | Users are advised to upgrade. There are no known workarounds for
>> | this vulnerability.
...
> A summary from the guix perspective, including code to verify the issue
> was posted:
>
>   
> https://guix.gnu.org/en/blog/2024/fixed-output-derivation-sandbox-bypass-cve-2024-27297/
>
> I have not yet had a chance to actually verify the fix on locally built
> Debian packages, but all three releases do successfully build with the
> patches applied.

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 is the reproducer used on 1.2.x from bullseye, which should
also work on 1.4.x in bookworm/trixie/sid.

live well,
  vagrant


guix-cve-2024-27297-patched
Description: Binary data


signature.asc
Description: PGP signature

Bug#1066828: xz-utils: worse compression ratio should be announced in NEWS.Debian

[Vincent Lefevre]

Package: xz-utils
Version: 5.6.0-0.2
Severity: wishlist

After upgrading xz-utils from 5.4.5-0.3 to 5.6.0-0.2, the compression
ratio with "xz -9" has decreased. For instance, on 3 files:

Old   118822308   146463040   157197172
New   121120576   148930624   161255000

It took me some time to figure out. This is the reason:

/usr/share/doc/xz-utils/NEWS.gz

5.6.0 (2024-02-24)

[...]
* xz:

- Multithreaded mode is now the default. This improves
  compression speed and creates .xz files that can be
  decompressed in multithreaded mode. The downsides are
  increased memory usage and slightly worse compression ratio.
[...]

Using -T1 restores the old behavior.

Since this affects what the user gets and is some kind of regression,
this should be announced in NEWS.Debian, IMHO.

Note also that this change might affect diffs between .xz files (e.g.
after something is appended to the uncompressed file), though I have
not checked.

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

Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, 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)
LSM: AppArmor: enabled

Versions of packages xz-utils depends on:
ii  libc6 2.37-15.1
ii  liblzma5  5.6.0-0.2

xz-utils recommends no packages.

xz-utils suggests no packages.

-- no debconf information

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

Bug#1041477: php-net-ftp: PHP Fatal error with Bookworm PHP 8.2

[Benjamin Renard]

Hi David,

Le 09/03/2024 à 11:49, David Prévot a écrit :

Also, this package has no reverse dependencies. Given the amount of care
it brought in the last few years, I believe it should be removed from
the archive. Bumping the severity to see it removed from testing ASAP,
maybe it should also be removed from (at least) Bookworm.

I intend to follow up with RM requests in a few months if nobody objects
(but feel free to beat me to it).


Thanks for return. I removed my dependencies on this package since I 
discovered this problem. So, for me, feel free to remove this package, I 
don't use it anymore :)


Freely,

--
Benjamin Renard

Bug#1066827: foot: mouse-click results in sequence 0;45;9M0;45;9m, displayed at the prompt

[Johann Hoermann]

Package: foot
Version: 1.16.2-2
Severity: important

Dear Maintainer,

   when i do a mouse-click in a just opened foot terminal, it highlights the 
text under the mouse-pointer which is the expected behaviour.

   After a while, instead of highlighting, a new mouse-click results in a 
sequence 0;45;9M0;45;9m being displayed at the shell prompt.

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

Kernel: Linux 6.7.9-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 foot depends on:
ii  init-system-helpers  1.66
ii  libc62.37-15.1
ii  libfcft4 3.1.8-1
ii  libfontconfig1   2.15.0-1.1
ii  libpixman-1-00.42.2-1+b1
ii  libutf8proc3 2.9.0-1+b1
ii  libwayland-client0   1.22.0-2.1+b1
ii  libwayland-cursor0   1.22.0-2.1+b1
ii  libxkbcommon01.6.0-1
ii  ncurses-term 6.4+20240113-1

foot recommends no packages.

Versions of packages foot suggests:
pn  foot-themes  

-- no debconf information

Bug#1050393: Unneeded dependency on "dconf-gsettings-backend | gsettings-backend"?

[Xiyue Deng]

Control: tags -1 patch

Hi,

It looks like the gsettings-backend dependency was introduced since
Emacs 29.1.  Tried to debug this a little, and it looks like the
dependencies was pulled in through ${misc:Depends} due to the GSettings
schema file[1].  With helps from folks on IRC, we found that this file
was installed only in PGTK mode[2], so technically this is not required
by other modes and should be safe to be moved from emacs-common to
emacs-pgtk.

I have prepared a MR[3] (patch also attached) as an attempt and verified
that it moved the "dconf-gsettings-backend | gsettings-backend" from
emacs-common to emacs-pgtk.  I'll try to use this locally with emacs-nox
to further verify that it doesn't cause any issues.

Meanwhile, would be great to have people review the patch.  TIA!

[1] Search for
"/usr/share/glib-2.0/schemas/org.gnu.emacs.defaults.gschema.xml" on
https://packages.debian.org/sid/all/emacs-common/filelist

[2] 
https://salsa.debian.org/rlb/deb-emacs/-/blob/deb/emacs/d/sid/master/Makefile.in?ref_type=heads#L1334-1337

[3] https://salsa.debian.org/rlb/deb-emacs/-/merge_requests/12

-- 
Xiyue Deng
>From f52a28d269f9e9698347c3a7a4c7d3cc531c166c Mon Sep 17 00:00:00 2001
From: Xiyue Deng 
Date: Wed, 13 Mar 2024 10:22:46 -0700
Subject: [PATCH] Install GSettings schema in pgtk build only (Closes:
 #1050393)

* In PGTK build it generates the GSettings schema file
"/usr/share/glib-2.0/schemas/org.gnu.emacs.defaults.gschema.xml" which
is not needed in other variant.
* Move the file from emacs-common to emacs-pgtk, and adds proper
breaks/replaces/conflicts to ensure a smooth upgrade.
---
 debian/changelog |  7 +++
 debian/control   | 10 --
 debian/rules |  9 -
 3 files changed, 23 insertions(+), 3 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index c53984fc648..960672b6297 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+emacs (1:29.2+1-3) UNRELEASED; urgency=medium
+
+  * Team upload.
+  * Install GSettings schema in pgtk build only (Closes: #1050393)
+
+ -- Xiyue Deng   Wed, 13 Mar 2024 10:22:10 -0700
+
 emacs (1:29.2+1-2) unstable; urgency=medium
 
   * Fix Breaks/Replaces by prepending missing epoch (Closes: #1064851)
diff --git a/debian/control b/debian/control
index e168717089f..a2b65b26329 100644
--- a/debian/control
+++ b/debian/control
@@ -138,8 +138,13 @@ Provides: editor, emacs, emacsen, info-browser, mail-reader, news-reader
 Recommends: fonts-noto-color-emoji
 Suggests: emacs-common-non-dfsg
 Conflicts: emacs-gtk, emacs-lucid, emacs-nox
-Replaces: emacs-gtk, emacs-lucid, emacs-nox, emacs-bin-common (<< 1:29.2)
-Breaks: emacs-bin-common (<< 1:29.2)
+Replaces:
+ emacs-gtk,
+ emacs-lucid,
+ emacs-nox,
+ emacs-bin-common (<< 1:29.2),
+ emacs-common (<< 1:29.2+1-3),
+Breaks: emacs-bin-common (<< 1:29.2), emacs-common (<< 1:29.2+1-3)
 Description: GNU Emacs editor (with GTK+ Wayland GUI support)
  GNU Emacs is the extensible self-documenting text editor.  This
  package contains a version of Emacs with a graphical user interface
@@ -184,6 +189,7 @@ Breaks:
  emacs-gtk (<< 1:25),
  emacs-lucid (<< 1:25),
  emacs-nox (<< 1:25),
+ emacs-pgtk (<< 1:29.2+1-3),
 Replaces:
  emacs-bin-common (<< 1:28)
 Description: GNU Emacs editor's shared, architecture independent infrastructure
diff --git a/debian/rules b/debian/rules
index 38965316f3d..8448d7c9be3 100755
--- a/debian/rules
+++ b/debian/rules
@@ -425,6 +425,9 @@ override_dh_auto_install: $(autogen_install_files)
 	  cp -a $(install_dir_pgtk)/* $(pkgdir_common)
 
 	  rm -r $(pkgdir_common)/usr/bin
+	  # PGTK builds a GSettings schema that is PGTK specific and
+	  # should not be shipped in emacs-common
+	  rm -r $(pkgdir_common)/usr/share/glib-2.0
 	  rm \
 	$(pkgdir_common)/$(libexec_dir_emacs)/hexl \
 	$(pkgdir_common)/$(libexec_dir_emacs)/emacs-*.pdmp \
@@ -548,7 +551,7 @@ override_dh_auto_install: $(autogen_install_files)
 
 ##
 # emacs-pgtk
-ifneq (,$(findstring emacs, $(shell dh_listpackages)))
+ifneq (,$(findstring emacs-pgtk, $(shell dh_listpackages)))
 	  $(call install_common_binpkg_bits,$(install_dir_pgtk),$(pkgdir_pgtk),emacs-pgtk,pgtk)
 
   # install desktop entries
@@ -557,6 +560,10 @@ override_dh_auto_install: $(autogen_install_files)
 	debian/emacs.desktop \
 	debian/emacs-term.desktop \
 	$(pkgdir_pgtk)/usr/share/applications/
+	  # install GSettings schema
+	  install -d $(pkgdir_pgtk)/usr/share/glib-2.0
+	  cp -a $(install_dir_pgtk)/usr/share/glib-2.0/* \
+	$(pkgdir_pgtk)/usr/share/glib-2.0
 endif
 
 ##
-- 
2.39.2

Bug#1066826: RFP: cotp -- command line totp/hotp authenticator

[commoncargo]

Package: cotp
Version: 1.5.0
Upstream Author: replydev mailto:someb...@some.org>com>
 URL: https://github.com/replydev/cotp
License: GPL3
 Description: Trustworthy, encrypted, command-line TOTP/HOTP authenticator app 
with import functionality.

If needed I can provide packaged .deb files.

Thanks for reading my request, best regards,
replydev

Bug#1045917: monado: Fails to build source after successful build

[Rylie Pavlik]

On Sun, 13 Aug 2023 21:20:59 +0200 Lucas Nussbaum  wrote:

Source: monado
Version: 21.0.0+git2905.e26a272c1~dfsg1-2
Severity: minor
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian...@lists.debian.org
Usertags: qa-doublebuild

Hi,

This package fails to build a source package after a successful build
(dpkg-buildpackage ; dpkg-buildpackage -S).

This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.

More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild

Relevant part of the build log:
> cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env 
-us -uc -rfakeroot -S
> 

> 
> dpkg-buildpackage: info: source package monado

> dpkg-buildpackage: info: source version 21.0.0+git2905.e26a272c1~dfsg1-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Ryan Pavlik 
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<>'
> rm -f imgui.ini
> dh_auto_clean
> make[1]: Leaving directory '/<>'
>dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building monado using existing 
./monado_21.0.0+git2905.e26a272c1~dfsg1.orig.tar.xz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: error: cannot represent change to 
src/xrt/ipc/shared/ipcproto/__pycache__/__init__.cpython-311.pyc: binary file 
contents changed
> dpkg-source: error: add 
src/xrt/ipc/shared/ipcproto/__pycache__/__init__.cpython-311.pyc in 
debian/source/include-binaries if you want to store the modified binary in the 
debian tarball
> dpkg-source: error: cannot represent change to 
src/xrt/ipc/shared/ipcproto/__pycache__/common.cpython-311.pyc: binary file 
contents changed
> dpkg-source: error: add 
src/xrt/ipc/shared/ipcproto/__pycache__/common.cpython-311.pyc in 
debian/source/include-binaries if you want to store the modified binary in the 
debian tarball
> dpkg-source: error: unrepresentable changes to source
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 1
> 
> E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -S' failed to run.



The full build log is available from:
http://qa-logs.debian.net/2023/08/13/monado_21.0.0+git2905.e26a272c1~dfsg1-2_unstable.log

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



For some reason I thought that the whole "python binary cache" thing was 
sorted automatically by dh. But it turns out I was able to fix this by 
just adding that directory to debian/clean, which seems simple enough. 
It is in git on salsa and will be in the next upload of the package: 
this did not seem substantial enough to merit a release.


Rylie Pavlik


OpenPGP_0x9045010AE5C2B9ED.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1066214: cyrus-sasl2: FTBFS: gssapi.c:1600:9: error: implicit declaration of function ‘gsskrb5_register_acceptor_identity’ [-Werror=implicit-function-declaration]

[Thorsten Glaser]

Dixi quod…

>Suggested fix:
>
>+ AC_CHECK_HEADERS(gssapi/gssapi_krb5.h)
>  AC_CHECK_FUNCS(gsskrb5_register_acceptor_identity)
>  if test "$ac_cv_func_gsskrb5_register_acceptor_identity" = no ; then
>-   AC_CHECK_HEADERS(gssapi/gssapi_krb5.h)
>
>If it’s really that, anyway.

At least it allows the build to proceed further. It’s still
building, though, so I cannot say if this fixes the build.
(Thanks to #1066811 the result will not work right anyway.)

bye,
//mirabilos
-- 
[...] if maybe ext3fs wasn't a better pick, or jfs, or maybe reiserfs, oh but
what about xfs, and if only i had waited until reiser4 was ready... in the be-
ginning, there was ffs, and in the middle, there was ffs, and at the end, there
was still ffs, and the sys admins knew it was good. :)  -- Ted Unangst über *fs

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

[Thorsten Glaser]

Dixi quod…

>I just tested the 2.2 patch on gnupg1, and it applies cleanly,
>[…]
>For gnupg1, the B-D are also already installable, so there’s no
>current need to modify them there, just apply the same patch as
>was applied in gnupg2 2.2 and upload.

It finished building with the patch, so please do ☻

Thanks,
//mirabilos
-- 
Solange man keine schmutzigen Tricks macht, und ich meine *wirklich*
schmutzige Tricks, wie bei einer doppelt verketteten Liste beide
Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz
hervorragend.   -- Andreas Bogk über boehm-gc in d.a.s.r

Bug#1066809: e2fsprogs: dependency loop libss2t64 versus libss2

[Sven Joachim]

On 2024-03-13 21:11 +0200, Martin-Éric Racine wrote:

> Package: e2fsprogs
> Version: 1.47.0-2.4
> Severity: important
>
> The latest upload introduces a dependency loop between libss2t64
> versus libss2 which also results in the removal of e2fsprogs-l10n.

No, there is no dependency loop because libss2 provides libss2t64.
Upgrading e2fsprogs resulted in removal of e2fsprogs-l10n because the
latter has a rather strict versioned dependency on the former and had
not been built yet.  Run "apt update", and you should be able to
reinstall e2fsprogs-l10n.

Cheers,
   Sven

Bug#1066825: alsa-oss: FTBFS on arm{el,hf}: error: ‘__open’ aliased to undefined symbol ‘open’

[Sebastian Ramacher]

Source: alsa-oss
Version: 1.1.8-2
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=alsa-oss=armhf=1.1.8-2%2Bb1=1710256499=0

libtool: compile:  gcc -DPACKAGE_NAME=\"alsa-oss\" 
-DPACKAGE_TARNAME=\"alsa-oss\" -DPACKAGE_VERSION=\"1.1.8\" 
"-DPACKAGE_STRING=\"alsa-oss 1.1.8\"" -DPACKAGE_BUGREPORT=\"\" 
-DPACKAGE_URL=\"\" -DPACKAGE=\"alsa-oss\" -DVERSION=\"1.1.8\" -DHAVE_STDIO_H=1 
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 
-DSTDC_HEADERS=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_LIBASOUND=1 -I. 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -c mixer.c  -fPIC 
-DPIC -o .libs/libalsatoss_la-mixer.o
alsa-oss.c:794:20: error: ‘__open’ aliased to undefined symbol ‘open’
  794 | strong_alias(open, __open);
  |^~
alsa-oss.c:792:26: note: in definition of macro ‘strong_alias’
  792 |   extern __typeof (name) aliasname __attribute__ ((alias (#name)));
  |  ^
alsa-oss.c:805:21: error: ‘__fopen’ aliased to undefined symbol ‘fopen’
  805 | strong_alias(fopen, __fopen);
  | ^~~
alsa-oss.c:792:26: note: in definition of macro ‘strong_alias’
  792 |   extern __typeof (name) aliasname __attribute__ ((alias (#name)));
  |  ^
alsa-oss.c:804:22: error: ‘__select’ aliased to undefined symbol ‘select’
  804 | strong_alias(select, __select);
  |  ^~~~
alsa-oss.c:792:26: note: in definition of macro ‘strong_alias’
  792 |   extern __typeof (name) aliasname __attribute__ ((alias (#name)));
  |  ^
alsa-oss.c:801:20: error: ‘__mmap’ aliased to undefined symbol ‘mmap’
  801 | strong_alias(mmap, __mmap);
  |^~
alsa-oss.c:792:26: note: in definition of macro ‘strong_alias’
  792 |   extern __typeof (name) aliasname __attribute__ ((alias (#name)));
  |  ^
alsa-oss.c:800:21: error: ‘__fcntl’ aliased to undefined symbol ‘fcntl’
  800 | strong_alias(fcntl, __fcntl);
  | ^~~
alsa-oss.c:792:26: note: in definition of macro ‘strong_alias’
  792 |   extern __typeof (name) aliasname __attribute__ ((alias (#name)));
  |  ^
make[2]: *** [Makefile:519: alsa-oss.lo] Error 1

Cheers
-- 
Sebastian Ramacher

Bug#1066824: lirc: socket missing

[Oswald Buddenhagen]

Package: lirc
Version: 0.10.2-0.7
Severity: important

# systemctl status lircd
● lircd.service - Flexible IR remote input/output application support
 Loaded: loaded (/usr/lib/systemd/system/lircd.service; enabled; preset: 
enabled)
 Active: active (running) since Wed 2024-03-13 23:05:48 CET; 3s ago
TriggeredBy: ● lircd.socket
   Docs: man:lircd(8)
 http://lirc.org/html/configure.html
   Main PID: 247266 (lircd)
  Tasks: 2 (limit: 19009)
 Memory: 624.0K (peak: 1.8M)
CPU: 26ms
 CGroup: /system.slice/lircd.service
 └─247266 /usr/sbin/lircd --nodaemon

Mar 13 23:05:48 ugly lircd-0.10.2[247266]: Notice: Current driver: default
Mar 13 23:05:48 ugly lircd-0.10.2[247266]: Notice: Driver API version: 3
Mar 13 23:05:48 ugly lircd-0.10.2[247266]: Notice: Driver  version: 0.10.2
Mar 13 23:05:48 ugly lircd-0.10.2[247266]: Notice: Driver  info: See 
file:///usr/share/doc/lirc/plugindocs/default.html
Mar 13 23:05:48 ugly lircd-0.10.2[247266]: Info: lircd:  Opening log, level: 
Info
Mar 13 23:05:48 ugly lircd-0.10.2[247266]: Notice: Using systemd fd
Mar 13 23:05:48 ugly lircd-0.10.2[247266]: Warning: Running as root
Mar 13 23:05:48 ugly lircd-0.10.2[247266]: Info: Using remote: maxdome.
Mar 13 23:05:48 ugly lircd-0.10.2[247266]: Info: Using remote: RH6820.
Mar 13 23:05:48 ugly lircd-0.10.2[247266]: Notice: lircd(default) ready, using 
/var/run/lirc/lircd
# irw
Cannot connect to socket /run/lirc/lircd: No such file or directory
# ls -l /var/run/lirc
total 4
-rw-r--r-- 1 root root 7 Mar 13 23:05 lircd.pid

so the notice about he used socket clearly does not reflect reality.
this started after the latest upgrade, the first within a month or so.
i haven't investigated this further yet.

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

Kernel: Linux 6.7.7-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C, 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 lirc depends on:
ii  libasound2t64   1.2.11-1
ii  libc6   2.37-15.1
ii  libftdi1-2  1.5-6+b3
ii  libgcc-s1   14-20240303-1
ii  liblirc-client0t64  0.10.2-0.7
ii  liblirc0t64 0.10.2-0.7
ii  libportaudio2   19.6.0-1.2+b1
ii  libstdc++6  14-20240303-1
ii  libsystemd0 255.4-1+b1
ii  libusb-0.1-42:0.1.12-35
ii  libusb-1.0-02:1.0.27-1
ii  python3 3.11.6-1

Versions of packages lirc recommends:
ii  gir1.2-vte-2.91  0.74.2-1
ii  python3-gi   3.46.0-3
ii  python3-yaml 6.0.1-2
ii  systemd  255.4-1+b1

Versions of packages lirc suggests:
ii  ir-keytable  1.26.1-3
pn  lirc-compat-remotes  
pn  lirc-doc 
pn  lirc-drv-irman   
ii  lirc-x   0.10.2-0.7
ii  setserial2.17-53+b1

-- Configuration Files:
/etc/lirc/lirc_options.conf changed:
[lircd]
nodaemon= False
driver  = default
device  = /dev/lirc0
output  = /var/run/lirc/lircd
pidfile = /var/run/lirc/lircd.pid
plugindir   = /usr/lib/x86_64-linux-gnu/lirc/plugins
permission  = 666
allow-simulate  = Yes
repeat-max  = 600
[lircmd]
uinput  = False
nodaemon= False

/etc/lirc/lircd.conf.d/devinput.lircd.conf [Errno 2] No such file or directory: 
'/etc/lirc/lircd.conf.d/devinput.lircd.conf'

-- no debconf information

Bug#1066823: plptools: FTBFS on arm{el,hf}: plpdirent.cc:44:35: error: call of overloaded ‘PsiTime(long int)’ is ambiguous

[Sebastian Ramacher]

Source: plptools
Version: 1.0.13-2
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=plptools=armhf=1.0.13-2%2Bb1=1710265542=0

libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -I../intl -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -c plpdirent.cc  
-fPIC -DPIC -o .libs/plpdirent.o
plpdirent.cc: In constructor ‘PlpDirent::PlpDirent()’:
plpdirent.cc:44:35: error: call of overloaded ‘PsiTime(long int)’ is ambiguous
   44 | : size(0), attr(0), name(""), time(0L), attrstr("") {
  |   ^~~~
In file included from plpdirent.h:30,
 from plpdirent.cc:23:
./psitime.h:179:5: note: candidate: ‘PsiTime::PsiTime(const PsiTime&)’
  179 | PsiTime(const PsiTime );
  | ^~~
./psitime.h:161:5: note: candidate: ‘PsiTime::PsiTime(psi_timeval*, 
psi_timezone*)’
  161 | PsiTime(psi_timeval *_ptv, psi_timezone *_ptz = 0L);
  | ^~~
./psitime.h:153:5: note: candidate: ‘PsiTime::PsiTime(time_t)’
  153 | PsiTime(time_t time);
  | ^~~
./psitime.h:146:5: note: candidate: ‘PsiTime::PsiTime(timeval*, timezone*)’
  146 | PsiTime(struct timeval *_utv, struct timezone *_utz = 0L);
  | ^~~
make[3]: *** [Makefile:579: plpdirent.lo] Error 1

Cheers
-- 
Sebastian Ramacher

Bug#1066822: linuxtv-dvb-apps: FTBFS on arm{el,hf}: evtest.c:244:38: error: ‘struct input_event’ has no member named ‘time’

[Sebastian Ramacher]

Source: linuxtv-dvb-apps
Version: 1.1.1+rev1500-1.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=linuxtv-dvb-apps=armhf=1.1.1%2Brev1500-1.4%2Bb1=1710350526=0

test_video.c: In function ‘play_file_video’:
test_video.c:245:9: warning: ignoring return value of ‘write’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  245 | write(fd,buf,count);
  | ^~~
CC evtest
evtest.c: In function ‘main’:
evtest.c:244:38: error: ‘struct input_event’ has no member named ‘time’
  244 | ev[i].time.tv_sec, ev[i].time.tv_usec, 
ev[i].type,
  |  ^
evtest.c:244:57: error: ‘struct input_event’ has no member named ‘time’
  244 | ev[i].time.tv_sec, ev[i].time.tv_usec, 
ev[i].type,
  | ^
make[2]: *** [../Make.rules:82: evtest] Error 1

Cheers
-- 
Sebastian Ramacher

Bug#1061493: consolekit: install PAM module and udev files into /usr

[Andreas Beckmann]

Followup-For: Bug #1061493
Control: found -1 1.2.6-3.1~exp1
Control: severity -1 serious
Control: tag -1 ftbfs

This change causes consolekit2 to to FTBFS in experimental:

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

dh_install
dh_install: warning: Cannot find (any matches for) "usr/lib/udev/" (tried in ., 
debian/tmp)

dh_install: warning: consolekit missing files: usr/lib/udev/
dh_install: error: missing files, aborting
make[1]: *** [debian/rules:43: override_dh_install] Error 255


Andreas

Bug#1040070: ITP texlab

[Matthias Geiger]

Am 13.03.24 um 21:55 schrieb Matthias Geiger:


>
>
> I got isocountry accepted. this equals only the logos-* stack missing;
> currently it's not packageable because a dependency had an api change.

Just packaged the logos stack, will look into getting it uploaded to 
the archive.


Haven't looked into whether anything else is missing for the new 
upstream.



Additionally missing:

human_name v2.0.2

unicode-case-mapping v0.4.0

 unidecode v0.3.0

--
Matthias Geiger 
Debian Maintainer
"Freiheit ist immer Freiheit des anders Denkenden" -- Rosa Luxemburg



OpenPGP_0x18BD106B3B6C5475.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1066821: apr-util: FTBFS on arm{el,hf}: /bin/bash: line 3: 3132384 Segmentation fault LD_LIBRARY_PATH="`echo "../crypto/.libs:../dbm/.libs:../dbd/.libs:../ldap/.libs:$LD_LIBRARY_PATH" | sed -

[Sebastian Ramacher]

Source: apr-util
Version: 1.6.3-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=apr-util=armhf=1.6.3-1.1=1709086833=0

testldap:  SUCCESS
testdbd :  SUCCESS
testdate:  SUCCESS
testmemcache:  Error 111 occurred attempting to reach memcached on 
localhost:11211.  Skipping apr_memcache tests...
SUCCESS
testredis   :  Error 111 occurred attempting to reach Redis on 
localhost:6379.  Skipping apr_redis tests...
SUCCESS
testxml :  SUCCESS
testxlate   :  SUCCESS
testrmm :  SUCCESS
testdbm :  BDB1565 DB->put: method not permitted before handle's 
open method
/bin/bash: line 3: 3132384 Segmentation fault  LD_LIBRARY_PATH="`echo 
"../crypto/.libs:../dbm/.libs:../dbd/.libs:../ldap/.libs:$LD_LIBRARY_PATH" | 
sed -e 's/::*$//'`" ./$prog -v
Programs failed: testall
make[2]: *** [Makefile:60: check] Error 139

Cheers
-- 
Sebastian Ramacher

Bug#1066820: python-aiosmtpd: CVE-2024-27305

[Salvatore Bonaccorso]

Source: python-aiosmtpd
Version: 1.4.4.post2-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for python-aiosmtpd.

CVE-2024-27305[0]:
| aiosmtpd is a reimplementation of the Python stdlib smtpd.py based
| on asyncio. aiosmtpd is vulnerable to inbound SMTP smuggling. SMTP
| smuggling is a novel vulnerability based on not so novel
| interpretation differences of the SMTP protocol. By exploiting SMTP
| smuggling, an attacker may send smuggle/spoof e-mails with fake
| sender addresses, allowing advanced phishing attacks. This issue is
| also existed in other SMTP software like Postfix. With the right
| SMTP server constellation, an attacker can send spoofed e-mails to
| inbound/receiving aiosmtpd instances. This issue has been addressed
| in version 1.4.5. Users are advised to upgrade. There are no known
| workarounds for this vulnerability.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-27305
https://www.cve.org/CVERecord?id=CVE-2024-27305
[1] https://github.com/aio-libs/aiosmtpd/security/advisories/GHSA-pr2m-px7j-xg65
[2] 
https://github.com/aio-libs/aiosmtpd/commit/24b6c79c8921cf1800e27ca144f4f37023982bbb

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1066819: dput manpage: missing space between "-S," and "--unset"

[Jakub Wilk]

Source: dput-ng
Version: 1.39
Severity: minor
Tags: patch

--
Jakub Wilk
From ac7204149aa6538ff02413222e0f438374a24d41 Mon Sep 17 00:00:00 2001
From: Jakub Wilk 
Date: Mon, 11 Mar 2024 10:36:50 +0100
Subject: [PATCH] dput manpage: add missing space

---
 docs/man/dput.1.man | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/man/dput.1.man b/docs/man/dput.1.man
index a627a9c..c7bf898 100644
--- a/docs/man/dput.1.man
+++ b/docs/man/dput.1.man
@@ -113,7 +113,7 @@ OPTIONS
 	connection is set-up (for example logging in through the FTP or SFTP
 	protocol) and tested for its functionality. 
 
-*-S,--unset*=OVERRIDE::
+*-S, --unset*=OVERRIDE::
 	Override the configured profile key by unsetting its value. See *-O* for a
 	full explanation of the behavior.
 
-- 
2.39.2

Bug#1066498: dh-make-perl: autopkgtest regression due to time_t transition

[Niko Tyni]

On Wed, Mar 13, 2024 at 05:39:49PM +0100, gregor herrmann via 
pkg-perl-maintainers wrote:
> On Wed, 13 Mar 2024 13:34:57 +0100, gregor herrmann wrote:
> 
> > > 80s not ok 5 - Errno is in libperl5.38 or perl-base (or only perl-base
> > > for perl < 5.22)
> > libperl5.38 or as it's called nowadays: libperl5.38t64, that's the
> > point probably …
> 
> Fix committed in git.
> 
> Reviews welcome; I'm not sure it's the most elegant and safe solution,
> and also if this libperl5.38t64 naming has other effects.

Thanks for fixing this.

Didn't dig deeply into what the test is actually doing, but I think it'd
be fine to just hardcode libperl5.38t64 FWIW.

We can get rid of the suffix with 5.40, and I doubt any other distro
will go through this than Ubuntu who we're syncing with anyway (for
better or worse).

But whatever works is good of course.
-- 
Niko

Bug#1066818: ITP: python-msgspec -- Fast serialization and validation library

[Stein Magnus Jodal]

Package: wnpp
Severity: wishlist
Owner: Stein Magnus Jodal 
X-Debbugs-Cc: debian-de...@lists.debian.org, jo...@debian.org

* Package name: python-msgspec
  Version : 0.18.6
  Upstream Contact: Jim Crist-Harif 
* URL : https://jcristharif.com/msgspec/
* License : BSD-3-Clause
  Programming Lang: Python
  Description : Fast serialization and validation library

A fast serialization and validation library, with builtin support for JSON,
MessagePack, YAML, and TOML.
.
 * High performance encoders/decoders for common protocols. The JSON and
   MessagePack implementations regularly benchmark as the fastest options for
   Python.
 * Support for a wide variety of Python types. Additional types may be
   supported through extensions.
 * Zero-cost schema validation using familiar Python type annotations. In
   benchmarks msgspec decodes and validates JSON faster than orjson can decode
   it alone.
 * A speedy Struct type for representing structured data. If you already use
   dataclasses or attrs, structs should feel familiar. However, they're 5-60x
   faster for common operations.
.
All of this is included in a lightweight library with no required
dependencies.

I will maintain this package as part of the Python team.

Bug#1065831: document package specifiers for `upgrade`

[Miguel Angel Rojas]

Hi all,

>>  No. Without a package as an argument it won't.

Thanks! You're right. Let me write it down here again:

   - "apt upgrade" (no argument) will never remove a package, only upgrade
   or install
   - "apt upgrade pkg_name" will remove, upgrade or install the required
   package to satisfy its dependencies.
   - "apt upgrade foo- bar+": advanced option that can be used to
   specifically removed or install packages.

>> Julian provided an explanation in #74,
20240312113620.ga1944...@debian.org

I can't access this link..

>> I'm not a Debian developer, never have been. Just someone who submitted
a patch or two.

And your comments have been really valuable in figuring out what's going
on! Again, my confusion was because this was the first time I reported a
bug AND several people jumped in the conversation! It is not usually the
case ;)

Regards

Bug#1040070: ITP texlab

[Matthias Geiger]

On Sun, 31 Dec 2023 00:50:23 +0100 Matthias Geiger 
 wrote:

> On Wed, 26 Jul 2023 22:45:19 +0100 Sebastian Crane
>  wrote:
> > Dear Matthias,
> >
> > > This seems like a nice thing to have in debian. Do you need any
> help with
> > > rust packaging ? From a first glance it doesn't look like there's
> that much
> > > missing. itertools and logos look like a good starting point.
> >
> > I would receive such help gratefully! I'll join the IRC channel as per
> > your suggestion.
> >
>
>
> I got isocountry accepted. this equals only the logos-* stack missing;
> currently it's not packageable because a dependency had an api change.

Just packaged the logos stack, will look into getting it uploaded to the 
archive.


Haven't looked into whether anything else is missing for the new upstream.

best,

--
Matthias Geiger 
Debian Maintainer
"Freiheit ist immer Freiheit des anders Denkenden" -- Rosa Luxemburg



OpenPGP_0x18BD106B3B6C5475.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1066817: input-remapper-gtk: Syntax errors at installation

[Richard]

Package: input-remapper-gtk
Version: 2.0.1-1
Severity: minor

Dear Maintainer,
this is a really minor issue, but upon finishing installation (from
terminal),
I'm greeted by this error message:

Notices:
  /usr/lib/python3/dist-packages/inputremapper/gui/controller.py:304:
SyntaxWarning: invalid escape sequence '\d'
  match = re.search(" copy *\d*$", name)

/usr/lib/python3/dist-packages/inputremapper/gui/messages/message_data.py:45:
SyntaxWarning: invalid escape sequence '\d'
  all_matches = list(re.finditer("(\d+, )+", string))

It doesn't seem to be affecting anything, but maybe issues would only be
appearing in special circumstances.


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

Kernel: Linux 6.6.15-amd64 (SMP w/8 CPU threads; PREEMPT)
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 input-remapper-gtk depends on:
ii  gir1.2-glib-2.01.78.1-15
ii  gir1.2-gtk-3.0 3.24.41-1
ii  gir1.2-gtksource-4 4.8.4-5+b1
ii  input-remapper-daemon  2.0.1-1
ii  python33.11.6-1
ii  python3-inputremapper  2.0.1-1

input-remapper-gtk recommends no packages.

input-remapper-gtk suggests no packages.

-- no debconf information

Bug#1065309: transition: gnat (12 -> 13 + time_t64)

[nicolas . boulenguez]

Hello.

A bug affects the Ada tests during the build of the gcc-12 source 
package.


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

Such error messages happen on each (uncoordinated) change in the sources 
of an Ada library.  Some sources for the standard library built by GCC 
are generated from C headers, so, as Matthias wrote in the bug report, 
this is without doubt caused by the t64 transition (especially taking 
into account that Ada.Calendar defines types for time representation).


All/most Ada packages will probably soon FTBFS with a similar message.

All/most Ada libraries need small manual changes and a passage through 
NEW in order to fix this (Ada -dev packages built with gcc-12 and 
earlier carry a version, in addition to the SO version carried by 
library packages).


I agree with Matthias that we should instead start the gcc-13 transition 
in unstable. All packages are ready in experimental, with all library 
packages already renamed through NEW. But unfortunately also with 
intrusive unrelated changes, for example new upstream versions and a new 
Ada workflow removing the version from -dev package names.


This will fix the issue quickly (only a new changelog entry for each 
package), but I would like a formal approval by the release managers 
before starting the gnat-13 transition.


As described above in #1065309, all precautions have been taken in 
experimental, and all is needed is a rebuild in unstable with a new 
changelog entry. The FTBFSs in experimental reported by the salsa CI 
pipeline can be ignored, they are caused by the difficulty to resolve 
build dependencies in a context mixing unstable and experimental.


For the record, some unrelated changes in the gnat-12 sources were 
already causing similar bugs (#1061631,  [1]#1061633,  [2]#1064745 [3]), 
that will also be fixed by the gnat-13 transition.  These bugs are less 
important because they affect a few Ada packages, not GCC.




Links:
--
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061631
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061633
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064745

Bug#1066816: RM: libcuneiform0t64/experimental -- RoQA; NBS; t64 transition not needed

[Andreas Beckmann]

Package: ftp.debian.org
Severity: normal

Please remove libcuneiform0t64 from experimental, according to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061914#19 after
improved analysis the t64 transition is not needed for src:cuneiform.

Andreas

Bug#1065908: multiqc: Please drop dependencies on python3-distutils

[Andreas Tille]

Control: tags -1 pending

Hi,

this bug is fixed in Git.  Since I used the chance to upgrade to
latest upstream which is blocked by a needed upgrade of plotly
the upload will be delayed.

Kind regards
   Andreas.

-- 
http://fam-tille.de

Bug#1066815: ITP: golang-github-woblerr-pgbackrest-exporter -- Prometheus exporter for pgBackRest

[Lena Voytek]

Package: wnpp
Severity: wishlist
Owner: Lena Voytek 
X-Debbugs-Cc: debian-de...@lists.debian.org, l...@voytek.dev

* Package name: golang-github-woblerr-pgbackrest-exporter
  Version : 0.16.2
  Upstream Author : Anton Kurochkin 
* URL : https://github.com/woblerr/pgbackrest_exporter
* License : MIT
  Programming Lang: Go
  Description : Prometheus exporter for pgBackRest

pgBackRest Exporter is a Prometheus exporter tool designed to collect and
expose metrics from pgBackRest, a PostgreSQL backup and restore system. For
more information on pgBackRest see https://pgbackrest.org/ and for exporters
in general see https://prometheus.io/docs/instrumenting/exporters/

I intend to actively maintain this package within the Debian Go
Packaging team.

Bug#1066814: plotly: Please upgrade to latest upstream version

[Andreas Tille]

Source: plotly
Version: 5.15.0+dfsg1-1
Severity: normal

Hi,

I want to upgrade multiqc but this package requires a higher version of
plotly as you can see in Salsa CI[1].  It would be great if you could
upgrade the package.

BTW, I would consider it a good idea if plotly would be maintained in
the Debian Python Team.

Kind regards
Andreas.

[1] https://salsa.debian.org/med-team/multiqc/-/jobs/5442252


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

Kernel: Linux 6.3.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=sh: 0: getcwd() failed: 
No such file or directory
UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1066813: RFS: sane-frontends/1.0.14-18 [RC] -- scanner graphical frontends

[Jörg Frings-Fürst]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "sane-frontends":

 * Package name : sane-frontends
   Version  : 1.0.14-18
   Upstream contact : [fill in name and email of upstream]
 * URL  : http://www.sane-project.org
 * License  : public-domain, GPL-2+ with sane exception, LGPL-2+, 
  Artistic-1.0, GPL-2+
 * Vcs  : https://git.jff.email/cgit/sane-frontends.git
   Section  : graphics

The source builds the following binary packages:

  sane - scanner graphical frontends

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

  https://mentors.debian.net/package/sane-frontends/

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

 dget -x 
https://mentors.debian.net/debian/pool/main/s/sane-frontends/sane-frontends_1.0.14-18.dsc


or from

 git 
https://git.jff.email/cgit/sane-frontends.git/?h=release%2Fdebian%2F1.0.14-18


Changes since the last upload:

 sane-frontends (1.0.14-18) unstable; urgency=medium
 .
   * New debian/patches/0145-ftbfs-impfuncdef.patch.
  Fix FTBFS -Werror=implicit-function-declaration (Closes: #1066571).
   * debian/copyright
 - Add year 2024 to myself.
   * debian/control:
 - Change to new repository.

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56


Jörg Frings-Fürst
D-54470 Lieser


git:  https://git.jff.email/cgit/

Skype:jff-skype@jff.email
Jami: joergfringsfuerst
Telegram: @joergfringsfuerst
Matrix:   @joergff:matrix.snct-gmbh.de

My wish list: 
 - Please send me a picture from the nature at your home.






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

Bug#1066049: stunnel4: please consider temporarily disabling tests on arm to unblock the t64 transition

[Emanuele Rocca]

Hi!

On 2024-03-12 10:46, Simon McVittie wrote:
> I think this change might be a pragmatic way to shorten the critical
> path for the time64 transition.

The patch works fine indeed, and stunnel4 can be built successfully on
armhf with it. I agree that it should be applied.

It seems however that stunnel4 alone is unfortunately not sufficient to
build curl as hoped:

 sbuild --arch armhf --dist unstable curl --extra-package 
stunnel4_5.72-1.1_armhf.deb

 [...]

 libssh-4 : Depends: libssl3 (>= 3.0.0) but it is not installable
 openssh-client : Depends: libssl3 (>= 3.0.0) but it is not installable
 openssh-server : Depends: libcom-err2 (>= 1.43.9) but it is not installable
  Depends: libssl3 (>= 3.0.0) but it is not installable
 python3-cryptography : Depends: libssl3 (>= 3.0.0) but it is not installable
 sbuild-build-depends-main-dummy : Depends: libldap2-dev

Bug#1066214: cyrus-sasl2: FTBFS: gssapi.c:1600:9: error: implicit declaration of function ‘gsskrb5_register_acceptor_identity’ [-Werror=implicit-function-declaration]

[Thorsten Glaser]

Andrey Rakhmatullin dixit:

>On Wed, Mar 13, 2024 at 12:36:37PM +0100, Lucas Nussbaum wrote:
>> > gssapi.c:1600:9: error: implicit declaration of function 
>> > ‘gsskrb5_register_acceptor_identity’ 
>> > [-Werror=implicit-function-declaration]
>> >  1600 | gsskrb5_register_acceptor_identity(keytab_path);
>> >   | ^~
>The function should be declared in , in this case it's
>/usr/include/heimdal/gssapi/gssapi_krb5.h from heimdal-multidev, but
>build-heimdal/config.h defines HAVE_GSSKRB5_REGISTER_ACCEPTOR_IDENTITY but
>doesn't define HAVE_GSSAPI_GSSAPI_KRB5_H, so  is not
>included but the code is compiled.

That’s because m4/sasl2.m4…

  AC_CHECK_FUNCS(gsskrb5_register_acceptor_identity)
  if test "$ac_cv_func_gsskrb5_register_acceptor_identity" = no ; then
AC_CHECK_HEADERS(gssapi/gssapi_krb5.h)
if test "$ac_cv_header_gssapi_gssapi_krb5_h" = "yes"; then
  AC_CHECK_DECL(gsskrb5_register_acceptor_identity,
[AC_DEFINE(HAVE_GSSKRB5_REGISTER_ACCEPTOR_IDENTITY,1,
   [Define if your GSSAPI implementation defines 
gsskrb5_register_acceptor_identity])],,
[
AC_INCLUDES_DEFAULT
#include 
])
fi
  fi

… only checks for the header file if gsskrb5_register_acceptor_identity
is not found without it included.

Suggested fix:

+ AC_CHECK_HEADERS(gssapi/gssapi_krb5.h)
  AC_CHECK_FUNCS(gsskrb5_register_acceptor_identity)
  if test "$ac_cv_func_gsskrb5_register_acceptor_identity" = no ; then
-   AC_CHECK_HEADERS(gssapi/gssapi_krb5.h)

If it’s really that, anyway.

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#1064967: fontforge DSA (was: Re: Bug#1064967: fontforge: diff for NMU version 1:20230101~dfsg-1.1)

[Salvatore Bonaccorso]

Hi Adrian,

On Fri, Mar 08, 2024 at 02:03:55AM +0200, Adrian Bunk wrote:
> Control: tags 1064967 + patch
> Control: tags 1064967 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for fontforge (versioned as 1:20230101~dfsg-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it.
> 
> @Security team:
> If wanted, I could afterwards also prepare (pu or DSA) updates for 
> bookworm and bullseye.

We came to the conclusion that it warrants a DSA. Could you prepare
debdiffs for bookworm-security and bulseye-security?

Regards,
Salvatore

Bug#1066811: cyrus-sasl2: assumes time_t fits into long for printf and scanf(!), will break on big endian

[Thorsten Glaser]

Source: cyrus-sasl2
Version: 2.1.28+dfsg1-4
Severity: serious
Justification: breaks
X-Debbugs-Cc: t...@mirbsd.de

cyrus-sasl2, before aborting the build due to #1066214, spews
several warnings like the following:

[…]
otp.c:648:43: warning: format '%ld' expects argument of type 'long int', but 
argument 7 has type 'time_t' {aka 'long long int'} [-Wformat=]
  648 | sprintf(data, "%s\t%04d\t%s\t%s\t%020ld",
  |  ~^
  |   |
  |   long int
  |  %020lld
  649 | alg, seq, seed, buf, timeout);
  |  ~~~
  |  |
  |  time_t {aka long long int}
otp.c:709:48: warning: format '%ld' expects argument of type 'long int *', but 
argument 7 has type 'time_t *' {aka 'long long int *'} [-Wformat=]
  709 | sscanf(secret, "%s\t%04d\t%s\t%s\t%020ld",
  |   ~^
  ||
  |long int *
  |   %020lld
  710 |alg, seq, seed, buf, timeout);
  | ~~~
  | |
  | time_t * {aka long long int *}
[…]

These are actual problems that not only result in bad data
being printed or read but, if the time_t argument is not
(like here) the last one, also wrong arguments being used
for subsequent positional parameters.

Please fix *all* -Wformat mismatches involving time_t, for
example:

-   sprintf(data, "%s\t%04d\t%s\t%s\t%020ld",
+   sprintf(data, "%s\t%04d\t%s\t%s\t%020lld",
-   alg, seq, seed, buf, timeout);
+   alg, seq, seed, buf, (long long)timeout);

+   long long tmptimeout;
-   sscanf(secret, "%s\t%04d\t%s\t%s\t%020ld",
+   sscanf(secret, "%s\t%04d\t%s\t%s\t%020lld",
-   alg, seq, seed, buf, timeout);
+   alg, seq, seed, buf, tmptimeout);
+   timeout = tmptimeout;

Justification: I’ve been fixing bugs like these on MirBSD
since its i386 port switched to 64-bit time_t in 2004…

Thanks,
//mirabilos
-- 
16:47⎜«mika:#grml» .oO(mira ist einfach gut)  23:22⎜«mikap:#grml»
mirabilos: und dein bootloader ist geil :)23:29⎜«mikap:#grml» und ich
finds saugeil dass ich ein bsd zum booten mit grml hab, das muss ich dann
gleich mal auf usb-stick installieren   -- Michael Prokop über MirOS bsd4grml

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

[Thorsten Glaser]

Hi again,

>on 1.x or 2.4 before the weekend.

I just tested the 2.2 patch on gnupg1, and it applies cleanly,
and configure also seems happy:

[…]
checking whether the resolver is usable... yes
checking whether LDAP via "-lldap" is present and sane... yes
checking for ldap_get_option... yes
checking for ldap_set_option... yes
checking for ldap_start_tls_s... yes
checking for ldap_start_tls_sA... no
checking for gawk... (cached) mawk
[…]

For gnupg1, the B-D are also already installable, so there’s no
current need to modify them there, just apply the same patch as
was applied in gnupg2 2.2 and upload.

Thanks,
//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#1066810: libdmtx: NMU diff for removing remaining reference to libdmtx0b

[Amin Bandali]

Control: tags -1 patch

Please find the debdiff attached.
diff -Nru libdmtx-0.7.7/debian/changelog libdmtx-0.7.7/debian/changelog
--- libdmtx-0.7.7/debian/changelog  2024-02-28 05:45:56.0 -0500
+++ libdmtx-0.7.7/debian/changelog  2024-03-13 15:28:28.0 -0400
@@ -1,3 +1,11 @@
+libdmtx (0.7.7-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Change the leftover reference to libdmtx0b to libdmtx0t64 in
+debian/rules. (Closes: #1066810)
+
+ -- Amin Bandali   Wed, 13 Mar 2024 15:28:28 -0400
+
 libdmtx (0.7.7-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libdmtx-0.7.7/debian/rules libdmtx-0.7.7/debian/rules
--- libdmtx-0.7.7/debian/rules  2019-04-12 15:26:32.0 -0400
+++ libdmtx-0.7.7/debian/rules  2024-03-13 15:09:57.0 -0400
@@ -3,6 +3,6 @@
 export DH_OPTIONS
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 override_dh_installdocs:
-   dh_installdocs --link-doc=libdmtx0b
+   dh_installdocs --link-doc=libdmtx0t64
 %:
dh $@

Bug#1066113: guix: CVE-2024-27297

[Salvatore Bonaccorso]

Control: clone -1 -2
Control: reassign -2 src:nix 2.18.1+dfsg-1
Control: retitle -2 nix: CVE-2024-27297

Hi,

On Tue, Mar 12, 2024 at 04:01:26PM -0700, Vagrant Cascadian wrote:
> Control: found 1066113 1.4.0-3
> Control: tags  1066113 pending
> 
> On 2024-03-12, Salvatore Bonaccorso wrote:
> > The following vulnerability was published for guix.
> >
> > CVE-2024-27297[0]:
> > | Nix is a package manager for Linux and other Unix systems. A fixed-
> > | output derivations on Linux can send file descriptors to files in
> > | the Nix store to another program running on the host (or another
> > | fixed-output derivation) via Unix domain sockets in the abstract
> > | namespace. This allows to modify the output of the derivation, after
> > | Nix has registered the path as "valid" and immutable in the Nix
> > | database. In particular, this allows the output of fixed-output
> > | derivations to be modified from their expected content. This issue
> > | has been addressed in versions 2.3.18 2.18.2 2.19.4 and 2.20.5.
> > | Users are advised to upgrade. There are no known workarounds for
> > | this vulnerability.
> 
> Technically, it was published for Nix (CCed the listed maintainer)! Guix
> just happens to share some of the same code history. :)
> 
> Should the bug be cloned for nix, or a separate bug filed?

you are absolutely right, I should have done that from the start.
Done now with this message and kept some some sort of context.

> > If you fix the vulnerability please also make sure to include the
> > CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> >
> > For further information see:
> >
> > [0] https://security-tracker.debian.org/tracker/CVE-2024-27297
> > https://www.cve.org/CVERecord?id=CVE-2024-27297
> > [1] 
> > https://git.savannah.gnu.org/cgit/guix.git/commit/?id=8f4ffb3fae133bb21d7991e97c2f19a7108b1143
> 
> > Please adjust the affected versions in the BTS as needed.
> 
> There was another followup fix committed in upstream guix, which I
> already merged into the Debian packaging:
> 
>   
> https://salsa.debian.org/debian/guix/-/commit/03eeedaddbdded880743461cbca0261b96737319
> 
> This commit can be trivially cherry-picked for bookworm (1.4.0-3) and
> for bullseye (with some easily resolved conflicts in
> debian/patches/series).
> 
> A summary from the guix perspective, including code to verify the issue
> was posted:
> 
>   
> https://guix.gnu.org/en/blog/2024/fixed-output-derivation-sandbox-bypass-cve-2024-27297/
> 
> I have not yet had a chance to actually verify the fix on locally built
> Debian packages, but all three releases do successfully build with the
> patches applied.

Regards,
Salvatore

Bug#1066810: libdmtx: NMU diff for removing remaining reference to libdmtx0b

[Amin Bandali]

Source: libdmtx
Version: 0.7.7-1.1
Severity: important

Dear maintainer,

I'll be uploading an NMU to unstable to change the remaining
reference to libdmtx0b in debian/rules to libdmtx0t64, relating to
the time_t transition.  The diff will be like so:

--- libdmtx-0.7.7/debian/rules  2019-04-12 15:26:32.0 -0400
+++ libdmtx-0.7.7/debian/rules  2024-03-13 15:08:05.0 -0400
@@ -3,6 +3,6 @@
 export DH_OPTIONS
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 override_dh_installdocs:
-   dh_installdocs --link-doc=libdmtx0b
+   dh_installdocs --link-doc=libdmtx0t64
 %:
dh $@

Best
-a

Bug#1066809: e2fsprogs: dependency loop libss2t64 versus libss2

[Martin-Éric Racine]

Package: e2fsprogs
Version: 1.47.0-2.4
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The latest upload introduces a dependency loop between libss2t64 versus libss2 
which also results in the removal of e2fsprogs-l10n.

Martin-Éric

- -- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages e2fsprogs depends on:
ii  libblkid1 2.39.3-10
ii  libc6 2.37-15.1
ii  libcom-err2t64 [libcom-err2]  1.47.0-2.3+b1
ii  libext2fs2t64 1.47.0-2.4
ii  libss21.47.0-2.4
ii  libuuid1  2.39.3-10
ii  logsave   1.47.0-2.4

Versions of packages e2fsprogs recommends:
pn  e2fsprogs-l10n  

Versions of packages e2fsprogs suggests:
pn  e2fsck-static  
pn  fuse2fs
pn  gpart  
pn  parted 

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmXx+lwACgkQrh+Cd8S0
17aasA//e73csg+hxm7SWDyHbEzkxrLP7WSrul3cUJitfJg/TgMBV4f7s2fLMzQo
4793rIOa7mS7eWuzUo9KmzC9o24koe6pG99cPv+C/MJwArrGEhDD9UeHVxs7J15I
5tjGkv1wELAu9nxEHTxXAU5ItNtkOjJiYyjb5JbYJq44yXySIkYTaixAvfYH/v1S
QHg7W1c39/nWv+PBgxXMKfGOSB9zWbi8mSlq/tvAYKv+r1hsACfE4P/BPQ05r6YB
8w9i/MFq092AI6S3+sCJrVo+1ru1YhGwr+Fg4UcXV6hLlFLogA8AtNLCIQNmwLcs
H8xZgbxEa3aybjY18sQGVgxEdbX7y+dGqFdE5mUCP7hykI6da2JiLZnN3dyJ/k8Y
H5Ubbh8euA0awC351OyCGC+QUIrgMojOJ5qFoWxnx3iuqQeSC5lULKDbjN6K2bpR
Ks7I2mUaw9UvonXaWJGMQtnAlXa0oISGrDYQMqavUy2us6mgrbfgC5IhBuL9fIu7
2ysaBK6ljK5i58oVRcjeJaJ1iAWZBEa3SIfbyakLYW8pIi8H7Y1D0Mp3mXfuZFAX
XKoCenJZmJaKIqGjDNR/+Nr62B/dCEqpuB/F6V1ptqd+vuYyMWveG2BC9rsL5Is9
3xGYDucM0+KogEsyA6vDuWeSCLoBMnvPR8Qd1nGwQowN3QhRLuY=
=1zKm
-END PGP SIGNATURE-

Bug#1066808: ITP: gtk-gnutella -- The Most Efficient Gnutella Client

[Lucio Marinelli]

Package: wnpp
Severity: whishlist

* Package name: gtk-gnutella
  Version : 1.2.3
  Upstream Author : Raphael Manfredi
* URL : https://gtk-gnutella.sourceforge.io
* License : GPL
  Programming Lang: C++
  Description : P2P Gnutella server/client

This is the follow-up of bug 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065479


gtk-gnutella is a server/client for the Gnutella peer-to-peer network. 
It was previously included in Debian repository.
The source code is hosted in Github: 
https://github.com/gtk-gnutella/gtk-gnutella
I already prepared the .deb package here: 
https://sourceforge.net/projects/gtk-gnutella/files/gtk-gnutella/1.2.3/


--
Lucio Marinelli

Bug#1066403: R packages failing to build with missing -ltirpc are actually an issue in r-base

[Dirk Eddelbuettel]

On 13 March 2024 at 19:06, Aurelien Jarno wrote:
| control: reassign 1066403 r-base-dev
| control: reassign 1066452 r-base-dev
| control: reassign 1066455 r-base-dev
| control: reassign 1066456 r-base-dev
| control: forcemerge 1066403 1066452 1066455 1066456
| control: affects 1066403 rjava
| control: affects 1066403 rapache
| control: affects 1066403 littler
| control: affects 1066403 rpy2
| control: retitle 1066403 r-base-dev: missing dependency on libtirpc-dev 
| 
| Hi Dirk,
| 
| There are 4 r-base packages failing to build in the latest archive
| rebuild:
| 
| #1066403 rjava: FTBFS: ld: cannot find -ltirpc: No such file or directory
| #1066452 rapache: FTBFS: ld: cannot find -ltirpc: No such file or directory
| #1066455 littler: FTBFS: ld: cannot find -ltirpc: No such file or directory
| #1066456 rpy2: FTBFS: ld: cannot find -ltirpc: No such file or directory
| 
| Investigating, it appears that the issue is actually at the r-base
| level. They try to link with -ltirpc because R tell them to do so:
| 
| $ R CMD config --ldflags
| -Wl,--export-dynamic -fopenmp -Wl,-z,relro -L/usr/lib/R/lib -lR -lpcre2-8 
-llzma -lbz2 -lz -ltirpc -lrt -ldl -lm -licuuc -licui18n
| 
| Therefore it seems that r-base-dev is missing a dependency on
| libtirpc-dev. Sorry for not having noticed that when filling #1065216.

I should have noticed that too when I prepared 4.3.3-2 from your #1065216:

  r-base (4.3.3-2) unstable; urgency=medium

* debian/control: Add libtirpc-dev to Build-Depends to fix build issue
  from side effects of t64 transition   (Closes: 
#1065216)

   -- Dirk Eddelbuettel   Mon, 04 Mar 2024 08:54:45 -0600

I will take care of it in -3.

Dirk 

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1066469: tack: FTBFS: configure: error: No curses header-files found

[Thomas Dickey]

On Wed, Mar 13, 2024 at 07:03:29PM +0100, Sven Joachim wrote:
> On 2024-03-13 13:08 +0100, Lucas Nussbaum wrote:
> 
> > Source: tack
> > Version: 1.08-1
> > Severity: serious
> > Justification: FTBFS
> > Tags: trixie sid ftbfs
> > User: lu...@debian.org
> > Usertags: ftbfs-20240313 ftbfs-trixie
> >
> > Hi,
> >
> > During a rebuild of all packages in sid, your package failed to build
> > on amd64.
> >
> >
> > Relevant part (hopefully):
> >> configure: WARNING: pkg-config is not installed
> >> checking for specific curses-directory... no
> >> checking for specified curses library type... curses
> >> checking for extra include directories... no
> >> checking if we have identified curses headers... none
> >> configure: error: No curses header-files found
> >>tail -v -n \+0 config.log
> 
> This reminds me that I really should update the tack package to a newer
> version.  The error is still present in tack 1.09 (the latest stable
> release), but fixed as of tack 1.09-20230201 (the latest development
> snapshot).
> 
> @Thomas: since tack 1.09 is more than four years old and there has been
> no new snapshot for over a year, how about releasing tack 1.10?  This
> bug will likely hit other distros as they upgrade to GCC 14.

I suppose so - though others seem okay with the snapshots
(I'll take a look "soon" - am working on Lynx at the moment)

-- 
Thomas E. Dickey 
https://invisible-island.net


signature.asc
Description: PGP signature

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

[Thorsten Glaser]

Hi Andreas

>I have upload a fix for 2.2

OK, that should help.

>probably will not be able to spend any time on 1.x or 2.4 before the weekend.

They can probably wait until then, no worries.

>It is fixed in 2.4 and I am very reluctant to backport major packaging
>updates to 2.2

For some values of major; Helmut already verified that the resulting
binary packages are identical, and…

>since I think we will need to ship some kind of 2.4 in trixie.

… this massively helps with the current transition in unstable,
which has to come before thinking of trixie.

Even gdb-13 has temporarily lost its gdb B-D, and pam temporarily
broke ABI by not including one module, to help the transition.
For gnupg2 this is a no-change-in-binary source change, so of much
less impact.

Thanks,
//mirabilos
-- 
Gast: „Ein Bier, bitte!“
Wirt: „Geht auch alkoholfrei?“
Gast: „Geht auch Spielgeld?“

Bug#1036559: (no subject)

[Hans-Christoph Steiner]

control: fixed 1036559 3.4.0~a1-7

Bug#1066473: multitail: FTBFS: mt.c:707:25: error: implicit declaration of function ‘waddnwstr’; did you mean ‘waddnstr’? [-Werror=implicit-function-declaration]

[Rene Engelhard]

tag 1066473: + pending

thanks

Hi,

Am 13.03.24 um 12:53 schrieb Lucas Nussbaum:

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


Interesting. I almost wanted to tag it unreproducible since it didn't 
happen in my already-existing chroot... But it definitely does fail in 
cowbuilder build <.dsc> :/



Nope. Just works here. Yes, with dpkg-dev 1.22.6. In a manual chroot I 
have here and upgraded and in a cowbuilder build multitail_6.5.0-1.dsc




Relevant part (hopefully):

cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -Wno-unused-parameter -funsigned-char -O3 
-DLinux -DVERSION=\"6.5.0\" -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -DCONFIG_FILE=\"/etc/multitail.conf\" -MMD -MP -DUTF8_SUPPORT  -c -o mt.o 
mt.c
mt.c: In function ‘do_color_print’:
mt.c:707:25: error: implicit declaration of function ‘waddnwstr’; did you mean 
‘waddnstr’? [-Werror=implicit-function-declaration]
   707 | waddnwstr(win -> win, , 1);
   | ^
   | waddnstr
mt.c: In function ‘update_statusline’:
mt.c:1467:126: warning: format ‘%lld’ expects argument of type ‘long long int’, 
but argument 5 has type ‘off64_t’ {aka ‘long int’} [-Wformat=]
  1467 | mvwprintw(status -> win, 0, 
win_width - (strlen(timestamp) + cur_len), "%10lld - %s", fsize, timestamp);
   |
 ~^~
   |
  ||
   |
  |off64_t {aka 
long int}
   |
  long long int
   |
 %10ld
cc1: some warnings being treated as errors
make[2]: *** [: mt.o] Error 1


Actually upstream has

#if defined(UTF8_SUPPORT) && defined(NCURSES_WIDECHAR)
// FIXME warning: implicit declaration of function �~@~Xwaddnwstr�~@~Y 
is invalid in C99 [-Wimplicit-function-declaration]

// see /usr/include/ncurses.h
    waddnwstr(win -> win, , 1);
#else
    wprintw(win -> win, "%c", wcur);
#endif

so is aware...


Actually (thanks to discussion on IRC) it seems that

CPPFLAGS:=$(shell pkg-config --cflags ncurses)
NCURSES_LIB:=$(shell pkg-config --libs ncurses)

is empty even though it shouldn't be. So fix is to add that missing 
build-dep.



Regards,


Rene

Bug#1064588: bookworm-pu: package glibc/2.36-9+deb12u5

[Aurelien Jarno]

Hi Cyril,

On 2024-02-25 13:45, Jonathan Wiltshire wrote:
> Control: tag -1 d-i
> 
> Hi,
> 
> On Sat, Feb 24, 2024 at 04:59:10PM +0100, Aurelien Jarno wrote:
> > [ Reason ]
> > The upstream stable branch got a few fixes in the last months, and this
> > update pulls them into the debian package.
> > 
> > [ Impact ]
> > In case the update isn't approved, systems will be left with a few
> > issues, and the differences with upstream will increase, which might
> > make next fixes more difficult to review.
> 
> I'm happy with it from SRM point of view, but as you say d-i ack needed.

The date of the next point release is slowly approaching, could you
please have a look at this?

Thanks
Aurelien

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

Bug#1064588: bookworm-pu: package glibc/2.36-9+deb12u5

[Aurelien Jarno]

Hi Cyril,

On 2024-02-25 13:45, Jonathan Wiltshire wrote:
> Control: tag -1 d-i
> 
> Hi,
> 
> On Sat, Feb 24, 2024 at 04:59:10PM +0100, Aurelien Jarno wrote:
> > [ Reason ]
> > The upstream stable branch got a few fixes in the last months, and this
> > update pulls them into the debian package.
> > 
> > [ Impact ]
> > In case the update isn't approved, systems will be left with a few
> > issues, and the differences with upstream will increase, which might
> > make next fixes more difficult to review.
> 
> I'm happy with it from SRM point of view, but as you say d-i ack needed.

The date of the next point release is slowly approaching, could you
please have a look at this?

Thanks
Aurelien

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

Bug#1055771: sysvinit script corrections

[Frank Lienhard]

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--- radicale_orig	2024-03-09 10:46:34.564111521 +0100
+++ radicale	2024-03-12 17:29:29.364390914 +0100
@@ -34,7 +34,7 @@
 . /lib/lsb/init-functions
 
 # Declare default options
-RADICALE_OPTS="--daemon"
+RADICALE_OPTS=""
 
 # Read configuration variable file if it is present
 [ -r /etc/default/$NAME ] && . /etc/default/$NAME
@@ -55,9 +55,9 @@
 			chown $DAEMON_UID:$DAEMON_GID $dir
 			chmod g-w,o-rwx $dir
 			if [ "$CALDIR" = $dir ]; then
-[ -e $dir/collections ] || mkdir -p $dir/collections
-chown $DAEMON_UID:$DAEMON_GID $dir/collections
-chmod g-w,o-rwx $dir/collections
+[ -e $dir/collection-root ] || mkdir -p $dir/collection-root
+chown $DAEMON_UID:$DAEMON_GID $dir/collection-root
+chmod g-w,o-rwx $dir/collection-root
 			fi
 		fi
 	done
@@ -68,10 +68,10 @@
 	fi
 
 	start-stop-daemon --start --quiet --startas $DAEMON \
-		--name $NAME --test > /dev/null \
+		--exec $DAEMON --test > /dev/null \
 		|| return 1
-	start-stop-daemon --start --quiet --startas $DAEMON \
-		--name $NAME --umask 0027 --chuid $DAEMON_UID:$DAEMON_GID -- \
+	start-stop-daemon --start --quiet --startas $DAEMON --background --output $LOGDIR/$NAME.log \
+		--exec $DAEMON --umask 0027 --chuid $DAEMON_UID:$DAEMON_GID -- \
 		$RADICALE_OPTS \
 		|| return 2
 }
@@ -86,7 +86,7 @@
 	#   1 if daemon was already stopped
 	#   2 if daemon could not be stopped
 	#   other if a failure occurred
-	start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --name $NAME
+	start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --user $DAEMON_UID
 }
 
 case "$1" in

Bug#1041552: HFS/HFS+ are insecure

[Michael Biebl]

Hi Marco

On Sun, 27 Aug 2023 02:34:04 +0200 Marco d'Itri  wrote:

Control: reassign -1 udisks2
Control: retitle -1 do not mount automatically unmaintained file systems

On Jul 20, md wrote:

> You are totally correct.
> Kernel team, please blacklist HFS/HFS+ for automounting.
As discussed on debian-devel@, this policy should not be handled by the 
kernel because modules autoloading of file systems drivers should not be

disabled.

So I propose this content for a file like
/usr/lib/udev/rules.d/75-insecure-fs.rules:


Just curious: Why did you pick priority 75?


OpenPGP_signature.asc
Description: OpenPGP digital signature

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

[Andreas Metzler]

On 2024-03-13 Thorsten Glaser  wrote:
> clone 1066137 -1
> reassign -1 gnupg1 1.4.23-1.1
> retitle -1 gnupg1: fails to build gpgkeys_ldap, probably due to 
> -Werror=implicit-function-declaration
> thanks

> Dixi quod…

> >This matches the following failure mode at the end of the build:

> Same for gnupg1 according to the buildd page:
> https://buildd.debian.org/status/package.php?p=gnupg1

Hello Thorsten,
I have upload a fix for 2.2, probably will not be able to spend any time
on 1.x or 2.4 before the weekend.

> >Trying to binNMU gnupg2 to make it installable during t64 transition,

> Please do also reduce the B-D as Helmut noted in #980768; specifically,
> dropping ghostscript, imagemagick, libcurl4-gnutls-dev and transfig
> from src:gnupg2 produces identical binary packages according to his
> analysis. Perhaps some of that applies to gnupg1 as well. This will
> help tremendously.

It is fixed in 2.4 and I am very reluctant to backport major packaging
updates to 2.2 since I think we will need to ship some kind of 2.4 in
trixie.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1066403: R packages failing to build with missing -ltirpc are actually an issue in r-base

[Aurelien Jarno]

control: reassign 1066403 r-base-dev
control: reassign 1066452 r-base-dev
control: reassign 1066455 r-base-dev
control: reassign 1066456 r-base-dev
control: forcemerge 1066403 1066452 1066455 1066456
control: affects 1066403 rjava
control: affects 1066403 rapache
control: affects 1066403 littler
control: affects 1066403 rpy2
control: retitle 1066403 r-base-dev: missing dependency on libtirpc-dev 

Hi Dirk,

There are 4 r-base packages failing to build in the latest archive
rebuild:

#1066403 rjava: FTBFS: ld: cannot find -ltirpc: No such file or directory
#1066452 rapache: FTBFS: ld: cannot find -ltirpc: No such file or directory
#1066455 littler: FTBFS: ld: cannot find -ltirpc: No such file or directory
#1066456 rpy2: FTBFS: ld: cannot find -ltirpc: No such file or directory

Investigating, it appears that the issue is actually at the r-base
level. They try to link with -ltirpc because R tell them to do so:

$ R CMD config --ldflags
-Wl,--export-dynamic -fopenmp -Wl,-z,relro -L/usr/lib/R/lib -lR -lpcre2-8 
-llzma -lbz2 -lz -ltirpc -lrt -ldl -lm -licuuc -licui18n

Therefore it seems that r-base-dev is missing a dependency on
libtirpc-dev. Sorry for not having noticed that when filling #1065216.

Regards
Aurelien

Bug#1066469: tack: FTBFS: configure: error: No curses header-files found

[Sven Joachim]

On 2024-03-13 13:08 +0100, Lucas Nussbaum wrote:

> Source: tack
> Version: 1.08-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240313 ftbfs-trixie
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
>> configure: WARNING: pkg-config is not installed
>> checking for specific curses-directory... no
>> checking for specified curses library type... curses
>> checking for extra include directories... no
>> checking if we have identified curses headers... none
>> configure: error: No curses header-files found
>>  tail -v -n \+0 config.log

This reminds me that I really should update the tack package to a newer
version.  The error is still present in tack 1.09 (the latest stable
release), but fixed as of tack 1.09-20230201 (the latest development
snapshot).

@Thomas: since tack 1.09 is more than four years old and there has been
no new snapshot for over a year, how about releasing tack 1.10?  This
bug will likely hit other distros as they upgrade to GCC 14.

Cheers,
   Sven

Bug#1066422: packages using dcmtk failing to build with missing -lnsl are actually an issue in dcmtk

[Aurelien Jarno]

control: reassign 1066422 libdcmtk-dev
control: reassign 1066423 libdcmtk-dev
control: forcemerge 1066422 1066423
control: retitle 1066422 libdcmtk-dev: missing dependency on libnsl-dev
control: affects 1066422 plastimatch
control: affects 1066423 sight

Hi,

There are 2 packages using dcmtk failing to build in the latest archive
rebuild:

#1066422 plastimatch: FTBFS: ld: cannot find -lnsl: No such file or directory
#1066423 sight: FTBFS: ld.gold: error: cannot find -lnsl

Investigating, it appears that the issue is actually at the dcmtk
package level. They try to link with -lnsl because dcmtk says so:

$ grep nsl /usr/lib/x86_64-linux-gnu/cmake/dcmtk/DCMTKTargets.cmake   
  INTERFACE_LINK_LIBRARIES "DCMTK::config;nsl;pthread;rt"

dcmtk actually does not depends on libnsl-dev, but gets this dependency
through the libwrap0-dev package. Therefore it seems that libdcmtk-dev
is missing a dependency on libnsl-dev. In addition it might be good to
add it as a build-dependency of the dcmtk package, to ensure it
continues building even if libwrap0-dev drops it at some point.

Regards
Aurelien

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

Bug#1066807: nvtop now eligible to be in main?

[Ken Harris]

Package: nvtop
Severity: wishlist

Dear Maintainer,

The program nvtop (currently version 3.0.1-1 in bookworm=stable) is in
"contrib" rather than "main", despite being licensed under the GNU GPL.

The copyright file explains that this is because "it is only useful in
combination with the proprietary NVIDIA drivers in non-free".

This was true in version 1.  Since then, nvtop version 2 added support for AMD
GPUs (and retconned the "nv" to mean "Neat Videocard"), and version 3 added
support for Intel GPUs, so I believe it's now perfectly usable with only free
software.

The Policy Manual says packages in main "must not require or recommend a
package outside of main for compilation or execution".  nvtop depends on only 4
packages (libc6, libncursesw6, libsystemd0, libtinfo6), all of which are in
"main", and it lists no "recommends/suggests/enhances" packages.  All of the
Build-Depends packages appear to be in main, as well.

Also, the Debian package description is still "Interactive NVIDIA GPU process
monitor", while the upstream description is now "GPU & Accelerator process
monitoring for AMD, Apple, Huawei, Intel, NVIDIA and Qualcomm".

thanks,


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

Kernel: Linux 6.1.0-15-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
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

Bug#1065751: pristine-tar: diff for NMU version 1.50+nmu2

[Jeremy Bícha]

On Tue, Mar 12, 2024 at 5:16 PM Jeremy Bícha  wrote:
>
> On Tue, Mar 12, 2024 at 4:13 PM Sebastian Andrzej Siewior
>  wrote:
> >
> > On 2024-03-12 09:26:32 [-0400], Jeremy Bícha wrote:
> > > > Could someone check this, please?
> > >
> > > Did you try running autopkgtests on this version? The autopkgtests fail 
> > > for me.
> >
> > autopkgtests were the first thing that pointed me here and they passed.
> > If you say they fail for you then I may have used the wrong xz version…
>
> I tried running the autopkgtests locally using a version of 1.50+nmu2
> that I built using your patch and the autopkgtests failed.
>
> None of the 3 test cases passed for me with that version or with 1.50+nmu1.

The 3 test cases pass for me now with the uploaded 1.50+nmu2. Maybe my
earlier test build used the old version of xz-utils. Thank you for
your upload!

Jeremy Bícha

Bug#1066263: xfonts-utils: FTBFS: ../fonttosfnt/util.c:89:10: error: implicit declaration of function ‘vasprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declaration]

[Andrey Rakhmatullin]

On Wed, Mar 13, 2024 at 12:46:49PM +0100, Lucas Nussbaum wrote:
> > ../fonttosfnt/util.c: In function ‘vsprintf_alloc’:
> > ../fonttosfnt/util.c:89:10: error: implicit declaration of function 
> > ‘vasprintf’; did you mean ‘vsprintf’? 
> > [-Werror=implicit-function-declaration]
Looks like it's caused by the lack of -D_GNU_SOURCE, not sure who should
set it. There is a very old debian/changelog entry about temporarily
setting it from d/rules and fonttosfnt/write.c sets it but
fonttosfnt/util.c doesn't and there is nothing related in the autotools
stuff.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#1065742: dh_install: cannot use empty lines or comments in substitution

[Andreas Metzler]

On 2024-03-13 Niels Thykier  wrote:
> Andreas Metzler:
>> On 2024-03-10 Niels Thykier  wrote:
>>> Andreas Metzler:
>> [...]
 supporting build-profiles like nodoc with dh_install seems to cumbersome.

>>> Any reason for not using dh_installdocs, which does `nodoc` out of the box?

>> Because for this specific case I need to handle files outside of
>> /usr/share/doc/$package.

> Ok, thanks for clarifying.

> The use of substitution is not intended as a filtering mechanism. The go-to
> solution for having filtering beyond debhelper's built-in is `dh-exec` which
> has architecture and build-profile filtering.

Hello,

would you mind documenting that? I accept that is your choice to make
that design but I ended up spending quite some time on debugging things
that afaict (from reading debhelper(7) should have worked. Could you please
untag this wontfix and document it?

> I understand that this might not be what you want. However, this is the
> feature set provided. If you really want to do all this logic in
> debian/rules, then you can simply do a `install foo bar` directly in the
> d/rules (or a `dh_install foo bar`).

"dh_install foo bar" was my "second try" in the bugreport (more details there)
but that broke dh_missing in the --build=any case.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


signature.asc
Description: PGP signature

Bug#1064123: libgl1-mesa-dri: latest version crashes X, can't use mouse/keyboard

[Sven Joachim]

Control: forwarded -1 https://gitlab.freedesktop.org/mesa/mesa/-/issues/10613

On 2024-02-17 18:53 +0100, Sven Joachim wrote:

> Control: severity -1 grave
>
> On 2024-02-17 13:35 +0100, Lorenzo Beretta wrote:
>
>> Package: libgl1-mesa-dri
>> Version: 24.0.1-1
>> Severity: important
>>
>> Dear Maintainer,
>>
>> after the latest upgrade it's impossible for me to run a display manager
>> or startx any window manager; after at most a few seconds / keypresses /
>> mouse movements the screen freezes, completely unresponsive to anything
>> other than the power button; the log below suggests a null pointer.
>>
>> Running "sleep 30; killall -u lorenzo" as root before startx returns me
>> to a tty.
>>
>> Reverting to the previous version everything works.
>>
>> I'm running this on a debian derivative, devuan; afaik it shouldn't make
>> a difference, as the package is unmodified from debian - I don't know
>> how to verify that other than by installing debian in some partition,
>> can one start some window manager from a debian chroot/whatever?
>>
>> If it's ok in debian or you need any more info please do let me know.
>
> I can reproduce that on my laptop which runs pure Debian, and at least
> one other user seems to have the same problem.
>
>> VGA-compatible devices on PCI bus:
>> --
>> 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
>> [AMD/ATI] Oland [Radeon HD 8570 / R5 430 OEM / R7 240/340 / Radeon 520
>> OEM] [1002:6611]
>
> I have the following graphics hardware:
>
> ,
> | 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices,
> | Inc. [AMD/ATI] Mullins [Radeon R3 Graphics] [1002:985\ 0] (rev 40)
> `
>
> This is also using the radeonsi driver, and the symptoms and the
> backtrace are the same as yours.
>
> Bumping severity to keep this mesa version out of testing, but I will
> not be able to investigate the problem because I need the machine and
> have already downgraded all packages from src:mesa.  There does not seem
> to be an upstream report yet.

Looks like there is one now and it even has a patch which seems to have
been applied in Archlinux and Ubuntu, but not committed upstream. :-(

Cheers,
   Sven

Bug#1066272: bc: FTBFS: stack.c:40:5: error: implicit declaration of function ‘checkferror_output’ [-Werror=implicit-function-declaration]

[Andrey Rakhmatullin]

On Wed, Mar 13, 2024 at 12:35:55PM +0100, Lucas Nussbaum wrote:
> > stack.c: In function ‘dc_binop’:
> > stack.c:40:5: error: implicit declaration of function ‘checkferror_output’ 
> > [-Werror=implicit-function-declaration]
> >40 | checkferror_output(stderr); \
> >   | ^~
[etc.]
This is most likely because
debian/patches/05_notice_read_write_errors.diff adds calls of
checkferror_output() to various files but doesn't add the relevant header
(which seems to be "h/number.h").

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#1066296: xli: FTBFS: dither.c:77:36: error: implicit declaration of function ‘strlen’ [-Werror=implicit-function-declaration]

[Nilson Silva]

Hello Lucas!
Thanks!
I will correct


Nilson F. Silva



De: Lucas Nussbaum 
Enviado: quarta-feira, 13 de março de 2024 08:46
Para: sub...@bugs.debian.org 
Assunto: Bug#1066296: xli: FTBFS: dither.c:77:36: error: implicit declaration 
of function ‘strlen’ [-Werror=implicit-function-declaration]

Source: xli
Version: 1.17.0+20061110-8
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

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 -c -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O 
> -DSYSPATHFILE=\"/usr/lib/X11/Xli\"   -Wdate-time -D_FORTIFY_SOURCE=2 fill.c
> dither.c: In function ‘dither’:
> dither.c:77:36: error: implicit declaration of function ‘strlen’ 
> [-Werror=implicit-function-declaration]
>77 | image->title = (char *)lmalloc(strlen(cimage->title) + 12);
>   |^~
> dither.c:28:1: note: include ‘’ or provide a declaration of ‘strlen’
>27 | #include "xli.h"
>   +++ |+#include 
>28 |
> dither.c:77:36: warning: incompatible implicit declaration of built-in 
> function ‘strlen’ [-Wbuiltin-declaration-mismatch]
>77 | image->title = (char *)lmalloc(strlen(cimage->title) + 12);
>   |^~
> dither.c:77:36: note: include ‘’ or provide a declaration of 
> ‘strlen’
> cc -c -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O 
> -DSYSPATHFILE=\"/usr/lib/X11/Xli\"   -Wdate-time -D_FORTIFY_SOURCE=2 g3.c
> cc -c -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O 
> -DSYSPATHFILE=\"/usr/lib/X11/Xli\"   -Wdate-time -D_FORTIFY_SOURCE=2 gif.c
> cc -c -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O 
> -DSYSPATHFILE=\"/usr/lib/X11/Xli\"   -Wdate-time -D_FORTIFY_SOURCE=2 
> halftone.c
> cc -c -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O 
> -DSYSPATHFILE=\"/usr/lib/X11/Xli\"   -Wdate-time -D_FORTIFY_SOURCE=2 
> imagetypes.c
> cc -c -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O 
> -DSYSPATHFILE=\"/usr/lib/X11/Xli\"   -Wdate-time -D_FORTIFY_SOURCE=2 img.c
> gif.c: In function ‘gifin_open_file’:
> gif.c:193:7: error: implicit declaration of function ‘strcmp’ 
> [-Werror=implicit-function-declaration]
>   193 |   if (strcmp((char *) buf, GIF_SIG) == 0)
>   |   ^~
> gif.c:21:1: note: include ‘’ or provide a declaration of ‘strcmp’
>20 | #include "imagetypes.h"
>   +++ |+#include 
>21 |
> cc -c -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O 
> -DSYSPATHFILE=\"/usr/lib/X11/Xli\"   -Wdate-time -D_FORTIFY_SOURCE=2 mac.c
> cc1: some warnings being treated as errors
> imagetypes.c: In function ‘loadImage’:
> imagetypes.c:66:39: error: implicit declaration of function ‘strlen’ 
> [-Werror=implicit-function-declaration]
>66 | image_ops->fullname = lmalloc(strlen(fullname) + 1);
>   |   ^~
> imagetypes.c:15:1: note: include ‘’ or provide a declaration of 
> ‘strlen’
>14 | #include 
>   +++ |+#include 
>15 |
> imagetypes.c:66:39: warning: incompatible implicit declaration of built-in 
> function ‘strlen’ [-Wbuiltin-declaration-mismatch]
>66 | image_ops->fullname = lmalloc(strlen(fullname) + 1);
>   |   ^~
> imagetypes.c:66:39: note: include ‘’ or provide a declaration of 
> ‘strlen’
> imagetypes.c:67:9: error: implicit declaration of

Bug#1063771: Also needed for aioquic

[Scott Kitterman]

This is starting to affect a lot of things.

Scott K

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

Bug#1066806: mirror submission for debian.linux.n0c.ca

[PlanetHoster]

Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: debian.linux.n0c.ca
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 hurd-amd64 i386 
mips mips64el mipsel powerpc ppc64el riscv64 s390x
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: PlanetHoster 
Country: CA Canada
Location: Montreal
Comment: We are currently mirroring from DST.ca, but we would prefer to mirror 
from more upstream servers.




Trace Url: http://debian.linux.n0c.ca/debian/project/trace/
Trace Url: http://debian.linux.n0c.ca/debian/project/trace/ftp-master.debian.org
Trace Url: http://debian.linux.n0c.ca/debian/project/trace/debian.linux.n0c.ca

Bug#1066351: aalib: diff for NMU version 1.4p5-51.1

[Andrey Rakhmatullin]

Control: tags 1066351 + patch
Control: tags 1066351 + pending

Dear maintainer,

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

Regards.


-- 
WBR, wRAR
diff -Nru aalib-1.4p5/debian/changelog aalib-1.4p5/debian/changelog
--- aalib-1.4p5/debian/changelog	2024-01-25 20:07:26.0 +0500
+++ aalib-1.4p5/debian/changelog	2024-03-13 22:25:58.0 +0500
@@ -1,3 +1,10 @@
+aalib (1.4p5-51.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066351).
+
+ -- Andrey Rakhmatullin   Wed, 13 Mar 2024 22:25:58 +0500
+
 aalib (1.4p5-51) unstable; urgency=medium
 
   * Accept MR: Fix Netscape typo
diff -Nru aalib-1.4p5/debian/patches/fix-implicit-function-declaration.patch aalib-1.4p5/debian/patches/fix-implicit-function-declaration.patch
--- aalib-1.4p5/debian/patches/fix-implicit-function-declaration.patch	1970-01-01 05:00:00.0 +0500
+++ aalib-1.4p5/debian/patches/fix-implicit-function-declaration.patch	2024-03-13 22:23:43.0 +0500
@@ -0,0 +1,109 @@
+Description: Add missing header includes.
+Author: Andrey Rakhmatullin 
+Bug-Debian: https://bugs.debian.org/1066351
+Last-Update: 2024-03-13
+
+Index: aalib-1.4p5/src/aainfo.c
+===
+--- aalib-1.4p5.orig/src/aainfo.c
 aalib-1.4p5/src/aainfo.c
+@@ -1,3 +1,4 @@
++#include 
+ 
+ #include "aalib.h"
+ #include "aaint.h"
+Index: aalib-1.4p5/src/aalinuxkbd.c
+===
+--- aalib-1.4p5.orig/src/aalinuxkbd.c
 aalib-1.4p5/src/aalinuxkbd.c
+@@ -22,6 +22,7 @@
+ #include 		/* for VT stuff - nah, really? :) */
+ #include 
+ #include 
++#include 
+ #ifdef GPM_MOUSEDRIVER
+ #include 
+ #endif
+Index: aalib-1.4p5/src/aaxkbd.c
+===
+--- aalib-1.4p5.orig/src/aaxkbd.c
 aalib-1.4p5/src/aaxkbd.c
+@@ -7,6 +7,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include "aalib.h"
+ #include "aaint.h"
+ #include "aaxint.h"
+Index: aalib-1.4p5/src/aalib.c
+===
+--- aalib-1.4p5.orig/src/aalib.c
 aalib-1.4p5/src/aalib.c
+@@ -1,6 +1,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include "aalib.h"
+ #include "aaint.h"
+ 
+Index: aalib-1.4p5/src/aaregist.c
+===
+--- aalib-1.4p5.orig/src/aaregist.c
 aalib-1.4p5/src/aaregist.c
+@@ -1,4 +1,5 @@
+ #include 
++#include 
+ #include "config.h"
+ #include "aalib.h"
+ #include "aaint.h"
+Index: aalib-1.4p5/src/aakbdreg.c
+===
+--- aalib-1.4p5.orig/src/aakbdreg.c
 aalib-1.4p5/src/aakbdreg.c
+@@ -1,4 +1,5 @@
+ #include 
++#include 
+ #include "config.h"
+ #include "aalib.h"
+ #include "aaint.h"
+Index: aalib-1.4p5/src/aamoureg.c
+===
+--- aalib-1.4p5.orig/src/aamoureg.c
 aalib-1.4p5/src/aamoureg.c
+@@ -1,4 +1,5 @@
+ #include 
++#include 
+ #include "config.h"
+ #include "aalib.h"
+ #include "aaint.h"
+Index: aalib-1.4p5/src/aatest.c
+===
+--- aalib-1.4p5.orig/src/aatest.c
 aalib-1.4p5/src/aatest.c
+@@ -1,3 +1,5 @@
++#include 
++#include 
+ #include "aalib.h"
+ int main(int argc, char **argv)
+ {
+Index: aalib-1.4p5/src/aafire.c
+===
+--- aalib-1.4p5.orig/src/aafire.c
 aalib-1.4p5/src/aafire.c
+@@ -1,4 +1,5 @@
+ #include 
++#include 
+ #include "aalib.h"
+ 
+ #define XSIZ aa_imgwidth(context)
+Index: aalib-1.4p5/src/aasavefont.c
+===
+--- aalib-1.4p5.orig/src/aasavefont.c
 aalib-1.4p5/src/aasavefont.c
+@@ -1,3 +1,4 @@
++#include 
+ #include "aalib.h"
+ int main(int argc, char **argv)
+ {
diff -Nru aalib-1.4p5/debian/patches/series aalib-1.4p5/debian/patches/series
--- aalib-1.4p5/debian/patches/series	2024-01-25 20:07:26.0 +0500
+++ aalib-1.4p5/debian/patches/series	2024-03-13 22:10:58.0 +0500
@@ -14,3 +14,4 @@
 fix-wording
 fix-netscape-typo
 fix-ftbfs-incomplete-typedef
+fix-implicit-function-declaration.patch


signature.asc
Description: PGP signature

Bug#1066137: gnupg2: -Werror=implicit-function-declaration failure testing for ldap_open

[Andreas Metzler]

Control: forcemerge 1066137 1066744
Control: found 1066137 2.4.3-2

On 2024-03-12 Thorsten Glaser  wrote:
> Source: gnupg2
> Version: 2.2.40-1.1
> Severity: serious
> Justification: ftbfs
> X-Debbugs-Cc: t...@mirbsd.de

> Trying to binNMU gnupg2 to make it installable during t64 transition,
> I notice the following configury output:

> […]
> checking for library containing dn_skipname... none required
> checking whether the resolver is usable... yes
> checking whether LDAP via "-lldap" is present and sane... no
[...]

I am going to take a look at this.

I am also marking this as applying to experimental, too. I have not
done a test-build yet but ldap.m4 looks similar.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1066805: Package request: `lua-latest`

[Pierre Tomon]

Source: lua5.4
Version: 5.4.6-3+b1
Severity: wishlist

Dear Maintainer,

It would be handy, if a metapackage can be created, that always depends on the 
latest version of the Lua package.
e.g. `lua-latest` package will depend on the latest version, currently the 
`lua5.4` package.
This would make easier to install and upgrade automatically to the latest 
version.

Bug#1066382: xserver-xorg-video-nouveau: FTBFS: ../../src/nv_driver.c:1451:23: error: implicit declaration of function ‘wfbScreenInit’; did you mean ‘fbScreenInit’? [-Werror=implicit-function-declarat

[Sven Joachim]

Control: forwarded -1 
https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/569

On 2024-03-13 12:47 +0100, Lucas Nussbaum wrote:

> Source: xserver-xorg-video-nouveau
> Version: 1:1.0.17-2
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
>
> Hi,
>
> 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):
>> /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H
>> -I. -I../../src -I..  -Wdate-time -D_FORTIFY_SOURCE=2
>> -I/usr/include/xorg -fvisibility=hidden -I/usr/include/pixman-1
>> -I/usr/include/X11/dri -I/usr/include/libdrm -I/usr/include/libdrm
>> -I/usr/include/libdrm/nouveau -I/usr/include/libdrm -g -O2
>> -Werror=implicit-function-declaration
>> -ffile-prefix-map=/<>=. -fstack-protector-strong
>> -fstack-clash-protection -Wformat -Werror=format-security
>> -fcf-protection -Wall -minline-all-stringops -I/usr/include/xorg
>> -fvisibility=hidden -I/usr/include/pixman-1 -I/usr/include/X11/dri
>> -I/usr/include/libdrm -c -o nv04_xv_ovl.lo ../../src/nv04_xv_ovl.c
>> ../../src/nv_driver.c: In function ‘NVScreenInit’:
>> ../../src/nv_driver.c:1451:23: error: implicit declaration of
>> function ‘wfbScreenInit’; did you mean ‘fbScreenInit’?
>> [-Werror=implicit-function-declaration]
>>  1451 | ret = wfbScreenInit(pScreen, FBStart, 
>> pScrn->virtualX,
>>   |   ^
>>   |   fbScreenInit

This has already been reported upstream, unfortunately without a
followup so far.  Adding -DFB_ACCESS_WRAPPER to CPPFLAGS lets the build
succeed, but I have not tested the resulting binary package yet.  See
commit d7ba24fb6e4f ("wfb: Fix missing init function decls behind
FB_ACCESS_WRAPPER") which noticed and fixed the missing function
declaration, but got reverted in commit ca13913aaf7e.

Cheers,
   Sven

Bug#1066214: cyrus-sasl2: FTBFS: gssapi.c:1600:9: error: implicit declaration of function ‘gsskrb5_register_acceptor_identity’ [-Werror=implicit-function-declaration]

[Andrey Rakhmatullin]

On Wed, Mar 13, 2024 at 12:36:37PM +0100, Lucas Nussbaum wrote:
> > gssapi.c:1600:9: error: implicit declaration of function 
> > ‘gsskrb5_register_acceptor_identity’ [-Werror=implicit-function-declaration]
> >  1600 | gsskrb5_register_acceptor_identity(keytab_path);
> >   | ^~
The function should be declared in , in this case it's
/usr/include/heimdal/gssapi/gssapi_krb5.h from heimdal-multidev, but
build-heimdal/config.h defines HAVE_GSSKRB5_REGISTER_ACCEPTOR_IDENTITY but
doesn't define HAVE_GSSAPI_GSSAPI_KRB5_H, so  is not
included but the code is compiled.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

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

[Carlos Henrique Lima Melara]

Hi,

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:

That was fast :-)

> https://salsa.debian.org/xorg-team/wayland/weston/-/tree/debian-10.0
> I just realized the branch name is confusing...

Might be a bit confusing with Debian buster (a.k.a. Debian 10), yes
hahahhaah.

I can start testing today, but I think we should wait until the weekend
to be sure enough for filling the bug against the release team. Would
that be okay?

> Best,
> Dylan

Cheers,
Charles


signature.asc
Description: PGP signature

Bug#1066233: libmpeg3: FTBFS: audio/synthesizers.c:36:9: error: implicit declaration of function ‘mpeg3audio_dct64’; did you mean ‘mpeg3audio_dopcm’? [-Werror=implicit-function-declaration]

[Andrey Rakhmatullin]

On Wed, Mar 13, 2024 at 12:41:13PM +0100, Lucas Nussbaum wrote:
> > audio/synthesizers.c: In function ‘mpeg3audio_synth_stereo’:
> > audio/synthesizers.c:36:9: error: implicit declaration of function 
> > ‘mpeg3audio_dct64’; did you mean ‘mpeg3audio_dopcm’? 
> > [-Werror=implicit-function-declaration]
> >36 | mpeg3audio_dct64(buf[1] + ((audio->bo + 1) & 0xf), buf[0] + 
> > audio->bo, bandPtr);
> >   | ^~~~
> >   | mpeg3audio_dopcm
mpeg3audio_dct64() is defined in audio/dct.c and there is no header with
its prototype.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#1066498: dh-make-perl: autopkgtest regression due to time_t transition

[gregor herrmann]

On Wed, 13 Mar 2024 13:34:57 +0100, gregor herrmann wrote:

> > 80s not ok 5 - Errno is in libperl5.38 or perl-base (or only perl-base
> > for perl < 5.22)
> libperl5.38 or as it's called nowadays: libperl5.38t64, that's the
> point probably …

Fix committed in git.

Reviews welcome; I'm not sure it's the most elegant and safe solution,
and also if this libperl5.38t64 naming has other effects.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

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

[Dylan Aïssi]

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...

Best,
Dylan

Bug#1066804: extrepo: Suites path for r-project repo is wrong.

[Bruno Gravato]

Package: extrepo
Version: 0.11
Severity: minor
X-Debbugs-Cc: bgravato+debianb...@gmail.com

Dear Maintainer,

"Suites" path for r-project repo is wrong.

Editing /etc/apt/sources.list.d/extrepo_r-project.sources and changing "Suites: 
../bookworm-cran40/" to "Suites: bookworm-cran40/" solves de problem.


-- 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/2 CPU threads; PREEMPT)
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)

Versions of packages extrepo depends on:
ii  gpgv  2.2.40-1.1
ii  libcryptx-perl0.077-1+b1
ii  libdpkg-perl  1.21.22
ii  libwww-perl   6.68-1
ii  libyaml-libyaml-perl  0.86+ds-1
ii  perl  5.36.0-7+deb12u1

Versions of packages extrepo recommends:
ii  apt [apt-transport-https]  2.6.1
pn  extrepo-offline-data   

extrepo suggests no packages.

-- no debconf information

Bug#1065831: document package specifiers for `upgrade`

[Wesley Schwengle]

On Wed, Mar 13, 2024 at 09:44:02AM +0100, Miguel Angel Rojas wrote:
> Hi there,
> 
> > If "apt upgrade" is saying that it removes packages, that is a bug, yes.
> 
> @david: it is not a bug, apparently.
> 
> To put everything in a nutshell:
> 
>- "apt upgrade" can remove packages

No. Without a package as an argument it won't.

>- "apt upgrade" accepts specific packages to be upgraded

To be installed if not installed yet, removed, downgraded or upgraded if
already installed depending on your arguments. For example `apt upgrade foo-
bar+ baz=version toto/archive' will remove foo, add bar, install, up- or
downgrade baz and the same for toto and it will upgrade packages where it can.

> Therefore, this behaviour is expected and documentation needs to be
> modified.
> 
> In the meantime, while the documentation is modified, can some developer
> provide some explanation to the current "apt upgrade" behaviour? (*)

Julian provided an explanation in #74, 20240312113620.ga1944...@debian.org

> whereas `apt upgrade foo` first does the normal install argument handling and
> then runs an upgrade, so `foo` could also be a new package that is not
> currently installed to hint the solver if it is unable to find a solution.



> (*) I'm a bit confused because I don't know which of the people involved in
> this bug are actually a developer of the apt package ;)

I'm not a Debian developer, never been. Just someone who submitted a patch or
two.

Cheers,
Wesley

Bug#1066803: linux-image-6.1.0-18-amd64: keyboard is not detected after most recent security patch

[Daniel Blaschke]

Package: src:linux
Version: 6.1.76-1
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: blasc...@hep.itp.tuwien.ac.at

Dear Maintainer,

after the latest security patch in debian stable (kernel version 6.1.0-18) the
keyboard on my dell xps 13 (2015 model) no longer works (therefore I'm writing
this bug report after booting into previous kernel 6.1.0-17 which works fine).
Right after installing and rebooting the newer kernel, the keyboard did work
briefly but then stopped after a standby cycle (together with the touchpad but
the latter came back after another standby cycle allowing me to gracefully
reboot); I've been using the older kernel since. When I tried to write this bug
report from the newer kernel just now, I could not get the keyboard to work at
all (only in the previous kernel).

Thanks,
Daniel



-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: Dell Inc.
product_name: XPS 13 9343
product_version: 
chassis_vendor: Dell Inc.
chassis_version: 
bios_vendor: Dell Inc.
bios_version: A18
board_vendor: Dell Inc.
board_name: 0TM99H
board_version: A00

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Broadwell-U Host Bridge -OPI 
[8086:1604] (rev 09)
Subsystem: Dell Broadwell-U Host Bridge -OPI [1028:0665]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: bdw_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 5500 
[8086:1616] (rev 09) (prog-if 00 [VGA controller])
DeviceName:  Onboard IGD
Subsystem: Dell HD Graphics 5500 [1028:0665]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller 
[8086:160c] (rev 09)
Subsystem: Dell Broadwell-U Audio Controller [1028:0665]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:04.0 Signal processing controller [1180]: Intel Corporation Broadwell-U 
Processor Thermal Subsystem [8086:1603] (rev 09)
Subsystem: Dell Broadwell-U Processor Thermal Subsystem [1028:0665]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device_pci_legacy

00:14.0 USB controller [0c03]: Intel Corporation Wildcat Point-LP USB xHCI 
Controller [8086:9cb1] (rev 03) (prog-if 30 [XHCI])
Subsystem: Dell Wildcat Point-LP USB xHCI Controller [1028:0665]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:16.0 Communication controller [0780]: Intel Corporation Wildcat Point-LP MEI 
Controller #1 [8086:9cba] (rev 03)
Subsystem: Dell Wildcat Point-LP MEI Controller [1028:0665]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:1b.0 Audio device [0403]: Intel Corporation Wildcat Point-LP High Definition 
Audio Controller [8086:9ca0] (rev 03)
Subsystem: Dell Wildcat Point-LP High Definition Audio Controller 
[1028:0665]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root 
Port #1 [8086:9c90] (rev e3) (prog-if 00 [Normal decode])
Subsystem: Dell Wildcat Point-LP PCI Express Root Port [1028:0665]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1c.3 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root 
Port #4 [8086:9c96] 

Bug#1066096: bookworm-pu: package libpod/4.3.1+ds1-8+deb12u1

[Jérôme Charaoui]

Just noting that I'm aware in the provided debdiff, the d/changelog 
entry is missing the Closes: tag.


This is already fixed in the upload I'm preparing, but if requested I 
can upload a new .debdiff without issue.


Also, as this is an NMU in its current form, I've also been in touch 
with the package maintainers in order to get additonal review and approval.


Thanks.

Bug#1059496: podman: network ls: might fail to handle removed container

[Jérôme Charaoui]

Just for the record, I've submitted a debdiff that includes the upstream 
patch for to fix this as a proposed-update for bookworm:


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

-- Jérôme

Bug#1066724: chibicc: change upstream

[Gürkan Myczko]

Hi UrsI think I found that and did some tests back a while:Index of /debian/chibicc/sid.ethz.chWill recheck…AlexOn Mar 13, 2024, at 15:18, Urs Janßen  wrote:Package: chibiccSeverity: wishlistDear Maintainer, seems no longer to be maintained,but the fork  looks like it isunder active development.It might be a good idea to switch the upstream source.

Bug#1066707: ifupdown-ng: FTBFS: libifupdown/interface.c:28:9: error: implicit declaration of function ‘strlcpy’; did you mean ‘strncpy’? [-Werror=implicit-function-declaration]

[Daniel Gröber]

On Wed, Mar 13, 2024 at 12:51:44PM +0100, Lucas Nussbaum wrote:
> Source: ifupdown-ng
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

Thanks Lucas, I'm uploading a fix right now.

> 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

It was due to a hardcoded path to libbsd's include directory which seems to
have moved to to a multiarch location.

Thanks,
--Daniel


signature.asc
Description: PGP signature