Bug#872381: dpkg-dev: optimize Makefile snippets for debian/rules
Package: dpkg-dev
Followup-For: Bug #872381
Hello.
Please consider this new patch queue instead of the old or untested
ones. With this one applied on 279c6ccb, the package builds and
passes all tests.
* scripts/mk: only use ASCII characters
Cosmetic independent suggestion.
* scripts/mk: protect files against double inclusion
The variables are renamed as you have recommended.
The test is fixed (ifdef fails on a defined but empty variable).
* scripts/mk: stop hard-coding dpkg_datadir
Already discussed.
* scripts/mk/buildopts.mk: search once for parallel= in DEB_BUILD_OPTIONS
> > [...DEB_BUILD_OPTION_PARALLEL empty instead of undefined
> > when parallel= is missing...]
> [kind of an API change].
I have changed my patch and updated the comment.
However..
The policy only describes 'parallel=N' when N is a positive integer.
I think we should assume that the option is either missing or valid.
For me, 'parallel=' is as incorrect as 'parallel=foo'.
> I think it might perhaps make more sense to fallback to setting it
> to 1 if it's missing, but I need to ponder about possible
> consequences/fallout, etc.
I doubt any sensible default exist.
* 1 is safe/produces readable logs and $max_available_processors is fast.
* the policy/debhelper/... have found no one-size-fits-all solution.
* scripts/buildflags.mk: add missing GCJFLAGS
Fixes a bug.
* scripts/buildflags.mk: generate the _FOR_BUILD variant of each variable
* scripts/buildflags.mk: sort the flag list
These changes hopefully prevent new missing flags in the future (the
output of dpkg-buildflags is sorted).
* scripts/*.mk: reduce the number of subprocesses
* scripts/t: use loops instead of repetitions, check exports and overrides
* all four combinations of existing/new scripts/mk/*.mk pass the
existing/new tests in scripts/t/mk/*.mk.
* comparing the time taken by tests gives a rough idea of the speed
gain
architecture.mk 30 times faster (probably no gain under dpkg-buildpackage)
buildflags.mk 20 times faster
pkg-info.mk 4 times faster
buildtools.mk20% faster
Guillem Jover
> I've left this one out for now. I'm not entirely satisfied with the
> sed usage here. If we keep using sed, then I think it needs to be
> set via a SED variable, substituted from the value found at
In which context do you expect GNU Make but a non recent sed?
Should I rewrite the regular expressions without -r/-E?
> configure time. But then, I've been pondering whether we can have
> better export formats, that might make the sed usage not
> necessary. I started with a make-eval export mode for buildflags,
> but perhaps it would be better a more generic formatting mode where
> the caller can specify how the output should look like, akin
> «dpkg-query --showformat». Will ponder about this.
A generic format would be more maintainable in the long term.
Something like that would be convenient for the makefiles.
dpkg-architecture --print-format='${Dollar}(eval export ${key} ?= ${value})'
dpkg-buildflags --print-format='${Dollar}(eval ${key}:=${value})'
dpkg-parsechangelog --print-format='${Dollar}(eval DEB_SOURCE:=${Source})
${Dollar}(eval export SOURCE_DATE_EPOCH?=${Timestamp}) ..'
dpkg-vendor --print-format'${Dollar}(eval DEB_VENDOR:=${Vendor}) ${Dollar}(eval
DEB_PARENT_VENDOR:=${Parent})'
* scripts/buildtools.mk: style suggestions
This arguably improves the readability, and fixes a minor issue
($(findstring nostrip,...) unwantedly matches arduinostrip).
* scripts/t/mk/buildflags.mk: fix test of _MAINT_APPEND when TEST_ is empty
This fixes a minor issue. During a test with
DEB_BUILD_OPTIONS=noopt, TEST_CXXFLAGS was empty and caused the test
of DEB_CXXFLAGS_MAINT_APPEND to fail because the correct result is
not a concatenation, Make strips a space. This issue can also be
seen with 1.22.5.
>From 37f1089c450fca16d06d586cf390a05642af25f0 Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez
Date: Mon, 4 Mar 2024 13:23:56 +0100
Subject: [PATCH 01/11] scripts/mk: only use ASCII characters
The policy recommends english, so french parenthesis must be replaced.
More generally, prudence recommends ASCII in Make scripts.
---
scripts/mk/buildtools.mk | 2 +-
scripts/mk/vendor.mk | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/scripts/mk/buildtools.mk b/scripts/mk/buildtools.mk
index 933fdcfaa..7c6732210 100644
--- a/scripts/mk/buildtools.mk
+++ b/scripts/mk/buildtools.mk
@@ -20,7 +20,7 @@
# QMAKE: Qt build system generator (since dpkg 1.20.0).
#
# All the above variables have a counterpart variable for the build tool,
-# as in CC → CC_FOR_BUILD.
+# as in CC -> CC_FOR_BUILD.
#
# The variables are not exported by default. This can be changed by
# defining DPKG_EXPORT_BUILDTOOLS.
diff --git a/scripts/mk/vendor.mk b/scripts/mk/vendor.mk
index f3241a57b..8bdaa235a 100644
--- a/scripts/mk/vendor.mk
+++ b/scripts/mk/vendor.mk
@@ -1,8 +1,8 @@
# This Makefile fragment (since dpkg
Bug#1066022: RFS: keyd/2.4.3-1 [ITP] -- keyboard key remapping daemon
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "keyd": * Package name : keyd Version : 2.4.3-1 Upstream contact : Raheman Vaiya * URL : https://github.com/rvaiya/keyd * License : Expat * Vcs : https://salsa.debian.org/rhansen/keyd Section : utils The source builds the following binary packages: keyd - keyboard key remapping daemon keyd-application-mapper - keyboard key remapping daemon - application-specific remapper To access further information about this package, please visit the following URL: https://mentors.debian.net/package/keyd/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/k/keyd/keyd_2.4.3-1.dsc Changes for the initial release: keyd (2.4.3-1) unstable; urgency=medium . * Initial debianization. (Closes: #1060023) Regards, Richard OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1038882: proposal: dhcpcd-base as standard DHCP client starting with Trixie
ma 11. maalisk. 2024 klo 1.29 Bernd Zeimetz (be...@bzed.de) kirjoitti: > On Mon, 2023-06-19 at 13:54 +0300, Martin-Éric Racine wrote: > > I hereby propose bin:dhcpcd-base: > > > > 1) already supported by ifupdown. > > 2) dual stack (DHCPv4, Bonjour, RA, DHCPv6 with PD) with privilege > > separation. > > 3) writes both IPv4 and IPv6 name servers to /etc/resolv.conf > > 4) supports /etc/resolv.conf.head and /etc/resolv.conf.tail > > 5) a mere inet line in /etc/network/interfaces is sufficient to > > configure both stacks. > > > > why not switch to systemd-networkd + networkmanager for gui installs? NM already is pulled by most desktop environments. Meanwhile a bare minimal system needs a non-GUI solution and swaping which DHCP client gets pulled by ifupdown is the simplest, least disruptive way of accomplishing this. Martin-Éric
Bug#1058451: ntpsec: FTBFS [Hurd] change Build-Depends: systemd to [linux-any]
ma 11. maalisk. 2024 klo 5.44 Richard Laager (rlaa...@debian.org) kirjoitti: > > I think, but am not sure, that this is now functionally a duplicate of > #1060506. That one tells me to change it from systemd to systemd-dev > because: > > Since systemd_253-2 [1], these two pkgconfig files have been split > into a separate package named systemd-dev. This package is arch:all, > so even available on non-Linux architectures, which will simplify > the installation of upstream provided service files / udev rules. > > I have made that change. If that is NOT sufficient, please let me know > and I'll adjust again. Yes, this probably accomplished the same. We'll know for sure once the buildd's have caught up with the upload. Thanks! Martin-Éric
Bug#1063175: orc: NMU diff for 64-bit time_t transition
Dear maintainers, One more bug in the orc transition: the .symbols file declares shlibs dependencies for multiple libraries, but only the first of them was updated to point at the new library name. Please find attached a comprehensive patch for orc vis-à-vis t64. I've uploaded this hopefully final NMU to unstable. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru orc-0.4.34/debian/changelog orc-0.4.34/debian/changelog --- orc-0.4.34/debian/changelog 2024-02-28 12:51:27.0 + +++ orc-0.4.34/debian/changelog 2024-03-11 04:36:15.0 + @@ -1,3 +1,25 @@ +orc (1:0.4.34-4.3) unstable; urgency=medium + + * Non-maintainer upload. + * Fix symbols dependencies on liborc-test. + + -- Steve Langasek Mon, 11 Mar 2024 04:36:15 + + +orc (1:0.4.34-4.2) unstable; urgency=medium + + * Non-maintainer upload. + * Fix build depedency on dpkg-dev to use >= not >> (sorry). + + -- Michael Hudson-Doyle Tue, 05 Mar 2024 10:54:56 +1300 + +orc (1:0.4.34-4.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition. +(Closes: #1065272) + + -- Michael Hudson-Doyle Mon, 04 Mar 2024 23:40:36 +1300 + orc (1:0.4.34-4) unstable; urgency=medium * Team upload diff -Nru orc-0.4.34/debian/control orc-0.4.34/debian/control --- orc-0.4.34/debian/control 2024-02-28 12:51:27.0 + +++ orc-0.4.34/debian/control 2024-03-04 21:54:56.0 + @@ -4,7 +4,8 @@ Maintainer: Maintainers of GStreamer packages Uploaders: Sebastian Dröge , Sjoerd Simons -Build-Depends: debhelper-compat (= 13), +Build-Depends: dpkg-dev (>= 1.22.5), + debhelper-compat (= 13), meson, pkg-config, gtk-doc-tools diff -Nru orc-0.4.34/debian/liborc-0.4-0t64.symbols orc-0.4.34/debian/liborc-0.4-0t64.symbols --- orc-0.4.34/debian/liborc-0.4-0t64.symbols 2024-02-28 12:51:27.0 + +++ orc-0.4.34/debian/liborc-0.4-0t64.symbols 2024-03-11 04:35:56.0 + @@ -308,7 +308,7 @@ orc_x86_get_regname_sse@Base 1:0.4.34 orc_x86_get_regnum@Base 1:0.4.34 orc_x86_output_insns@Base 1:0.4.34 -liborc-test-0.4.so.0 liborc-0.4-0 #MINVER# +liborc-test-0.4.so.0 liborc-0.4-0t64 #MINVER# * Build-Depends-Package: liborc-0.4-dev orc_array_check_out_of_bounds@Base 1:0.4.34 orc_array_compare@Base 1:0.4.34 signature.asc Description: PGP signature
Bug#1064085: gts: NMU diff for 64-bit time_t transition
Package: gts Version: 0.7.6+darcs121130-5.1 Followup-For: Bug #1064085 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch Control: tags -1 patch Dear Maintainer, Please find attached a patch for fixing shlib dependency marking of libgts-0.7-5t64. This was a regression introduced by the time_t transition. * d/symbols: rename package libgts-0.7-5 to libgts-0.7-5t64. Thanks for considering the patch. -- System Information: Debian Release: bookworm/sid APT prefers jammy-updates APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'), (100, 'jammy-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-25-generic (SMP w/10 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru gts-0.7.6+darcs121130/debian/symbols gts-0.7.6+darcs121130/debian/symbols --- gts-0.7.6+darcs121130/debian/symbols2021-11-11 09:18:31.0 -0700 +++ gts-0.7.6+darcs121130/debian/symbols2024-03-10 20:46:33.0 -0600 @@ -1,4 +1,4 @@ -libgts-0.7.so.5 libgts-0.7-5 #MINVER# +libgts-0.7.so.5 libgts-0.7-5t64 #MINVER# gts_allow_floating_edges@Base 0.7.6 gts_allow_floating_faces@Base 0.7.6 gts_allow_floating_gnodes@Base 0.7.6
Bug#1058451: ntpsec: FTBFS [Hurd] change Build-Depends: systemd to [linux-any]
I think, but am not sure, that this is now functionally a duplicate of #1060506. That one tells me to change it from systemd to systemd-dev because: Since systemd_253-2 [1], these two pkgconfig files have been split into a separate package named systemd-dev. This package is arch:all, so even available on non-Linux architectures, which will simplify the installation of upstream provided service files / udev rules. I have made that change. If that is NOT sufficient, please let me know and I'll adjust again. -- Richard OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1064025: ntpsec does not sync to server if "iburst" is missing
I agree that the description, as provided, would be a bug. However, I cannot reproduce this. Can you provide your ntp.conf file, in full, please? -- Richard OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1065467: marisa: FTBFS on loongarch64 as the test case fails
Hi, Thanks for your reply. On Thu, 07 Mar 2024 09:31:20 -0500 Boyuan Yang wrote: > Hi, > > 在 2024-03-05星期二的 12:10 +0800，zhangdandan写道： > > Source: marisa > > Version: 0.2.6-15 > > Severity: wishlist > > Tags: ftbfs > > User: debian-loonga...@lists.debian.org > > Usertags: loong64 > > > > Dear maintainers, > > > > Compiling the marisa failed for loong64 in the Debian Package > > Auto-Building environment. > > Please consider the patch (my local patch) I have attached. > > If you have any questions, you can contact me at any time. > > I can take this patch, but the patch should be forwarded upstream first. > Please forward it to GitHub upstream project so that I can use the forwarded > link as a reference. After that, I can make the patched upload in Debian. I have submitted a pull request to upstream, please see https://github.com/s-yata/marisa-trie/pull/56. But this marisa-trie project hasn't been updated for a long time (about 4 years). Refer to other architectures for handling, could you add a patch for marisa-0.2.6 source package? Thanks, Dandan Zhang
Bug#1066021: pbuilder: debconf crashes while configuring pbuilder in debian:12.5 docker container
Adam Baxter dixit: >#5 3.790 Configuring pbuilder >#5 3.790 >#5 3.790 >#5 3.790 Default mirror not found […] >I believe this is due to deb822 format sources lists being used in the >container That autodetection has annoyed me multiple times in the past already anyway, *and* it had overwritten parts of my custom /etc/pbuilderrc, inserting an older mirror that it had cached in debconf (which in itself is a violation). Can we please just, in this day and age, skip that mirror detection, and let pbuilder default to deb.debian.org if no mirror variable is set in pbuilderrc? Drop all that fiddling with the configuration files and everything. Thanks, //mirabilos -- 22:20⎜ The crazy that persists in his craziness becomes a master 22:21⎜ And the distance between the craziness and geniality is only measured by the success 18:35⎜ "Psychotics are consistently inconsistent. The essence of sanity is to be inconsistently inconsistent
Bug#1066021: pbuilder: debconf crashes while configuring pbuilder in debian:12.5 docker container
Package: pbuilder Version: 0.231 Severity: normal X-Debbugs-Cc: deb...@voltagex.org Dear Maintainer, I'm not sure if this should be filed against debconf or pbuilder or both (does the Package line support multiple packages?) It was also not clear how to report bugs against the official Debian Docker image A Dockerfile with the following: FROM debian:12.5 RUN apt update && apt install --no-install-recommends -y pbuilder will loop the following: #5 3.737 Setting up pbuilder (0.231) ... #5 3.774 debconf: unable to initialize frontend: Dialog #5 3.774 debconf: (TERM is not set, so the dialog frontend is not usable.) #5 3.774 debconf: falling back to frontend: Readline #5 3.780 debconf: unable to initialize frontend: Readline #5 3.780 debconf: (This frontend requires a controlling tty.) #5 3.780 debconf: falling back to frontend: Teletype #5 3.790 Configuring pbuilder #5 3.790 #5 3.790 #5 3.790 Default mirror not found #5 3.790 #5 3.790 Mirror information detection failed and the user provided no mirror #5 3.790 information. #5 3.790 #5 3.790 Please enter valid mirror information. #5 3.790 #5 3.790 Please enter the default mirror you want to be used by pbuilder. #5 3.790 #5 3.790 If you leave this field blank, there will be one attempt to autodetect this #5 3.790 information. If this attempt fails, you will be prompted again to insert some #5 3.790 valid mirror information. #5 3.790 #5 3.790 Here is a valid mirror example: http://deb.debian.org/debian I believe this is due to deb822 format sources lists being used in the container If I change the Dockerfile to read FROM debian:12.5 RUN echo "deb http://deb.debian.org/debian/ stable main contrib" > /etc/apt/sources.list && rm /etc/apt/sources.list.d/debian.sources RUN apt update && apt install --no-install-recommends -y pbuilder Then the package installs correctly -- System Information: Debian Release: 12.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.7.7-200.fc39.x86_64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect Versions of packages pbuilder depends on: ii debconf [debconf-2.0] 1.5.82 ii debootstrap1.0.128+nmu2+deb12u1 ii dpkg-dev 1.21.22 Versions of packages pbuilder recommends: pn devscripts pn eatmydata pn fakeroot pn net-tools | iproute2 pn sudo Versions of packages pbuilder suggests: pn cowdancer pn gdebi-core -- debconf information excluded
Bug#1065713: directfb: FTBFS on arm{el,hf}: error: ‘const struct input_event’ has no member named ‘time’
On Sat, 09 Mar 2024 at 12:29:26 +0100, Sebastian Ramacher wrote: > linux_input.c: In function ‘translate_event’: > linux_input.c:761:28: error: ‘const struct input_event’ has no member named > ‘time’ > 761 | devt->timestamp = levt->time; > |^~ This seems to be essentially the same bug that was fixed in SDL by: https://github.com/libsdl-org/SDL/commit/10fc3b3db715f0e2050e49f39d7d6e932813723c so hopefully that's a useful reference. smcv
Bug#1066020: parole: Output window is a separate window only in Wayland
Package: parole Version: 4.18.1-1+b1 Severity: normal X-Debbugs-Cc: hueyche...@outlook.com Dear Maintainer, When you open Parole and play a file on Wayland, a new window will be created showing the output (frequency spectrum or video.) The expected behavior is the output to stay in the same window as the original Parole window. This bug happens only on Wayland. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.7.7-amd64 (SMP w/12 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 parole depends on: ii gstreamer1.0-libav 1.24.0-1 ii gstreamer1.0-plugins-bad [gstreamer1.0-audiosink] 1.24.0-1 ii gstreamer1.0-plugins-base 1.24.0-1 ii gstreamer1.0-plugins-good [gstreamer1.0-audiosink] 1.24.0-1 ii gstreamer1.0-x 1.24.0-1 ii libc6 2.37-15.1 ii libcairo2 1.18.0-2 ii libdbus-1-3 1.14.10-4+b1 ii libdbus-glib-1-20.112-3+b2 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-3+b2 ii libglib2.0-0t64 [libglib2.0-0] 2.78.4-4 ii libgstreamer-plugins-base1.0-0 1.24.0-1 ii libgstreamer1.0-0 1.24.0-1 ii libgtk-3-0t64 [libgtk-3-0] 3.24.41-2 ii libnotify4 0.8.3-1+b1 ii libtagc01.13.1-1+b1 ii libx11-62:1.8.7-1 ii libxfce4ui-2-0 4.18.4-1 ii libxfce4util7 4.18.1-2 ii libxfconf-0-3 4.18.1-1+b1 parole recommends no packages. Versions of packages parole suggests: ii gstreamer1.0-plugins-bad 1.24.0-1 pn gstreamer1.0-plugins-ugly -- no debconf information
Bug#1065978: Handle listxattr failures better (upstream patch 9.1.0162)
Thanks, James! I'm deeply grateful for your work on vim, thank you so much for maintaining it! paultag On Sun, Mar 10, 2024 at 8:17 PM James McCoy wrote: > > On Sun, Mar 10, 2024 at 05:44:27PM -0400, Paul R. Tagliamonte wrote: > > I sent a fix to upstream vim to handle a bug where vim would attempt > > to allocate size_t max (for me, 0x aka > > 18446744073709551615 bytes) when the filesystem responded with an > > error on listxattr other than not supported. > > > > The upstream patch can be found at > > 14759ded57447345ba11c11a99fd84344797862c[1] - I've exported that patch > > for inclusion into sid. > > Thanks! I'll likely refresh against the ~latest upstream once things in > the time_t land settle down some, so this will get pulled in then. > > Cheers, > -- > James > GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB -- :wq
Bug#1066019: mariadb: FTBFS on hurd-i386: information_schema_disks.cc:69:31: error: ‘PATH_MAX’ was not declared in this scope
Source: mariadb
Version: 1:10.11.7-2
Tags: confirmed, help, ftbfs
User: debian-h...@lists.debian.org
Usertags: hurd
X-Debbugs-CC: debian-h...@lists.debian.org
After fixing https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063739
the builds of MariaDB currently fail with:
[ 86%] Building CXX object
plugin/disks/CMakeFiles/disks.dir/information_schema_disks.cc.o
cd /<>/builddir/plugin/disks && /usr/bin/c++
-DHAVE_CONFIG_H -DMYSQL_DYNAMIC_PLUGIN -D_FILE_OFFSET_BITS=64
-Ddisks_EXPORTS -I/<>/wsrep-lib/include
-I/<>/wsrep-lib/wsrep-API/v26
-I/<>/builddir/include
-I/<>/include/providers -I/<>/sql
-I/<>/include -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -pie -fPIC
-fstack-protector --param=ssp-buffer-size=4 -O2 -g -static-libgcc
-fno-omit-frame-pointer -fno-strict-aliasing -Wno-uninitialized
-fno-omit-frame-pointer -D_FORTIFY_SOURCE=2 -DDBUG_OFF -Wall
-Wenum-compare -Wenum-conversion -Wextra -Wformat-security
-Wmissing-braces -Wno-format-truncation -Wno-init-self
-Wno-nonnull-compare -Wno-unused-parameter -Woverloaded-virtual
-Wnon-virtual-dtor -Wvla -Wwrite-strings -std=gnu++11 -fPIC
-Wdate-time -D_FORTIFY_SOURCE=2 -MD -MT
plugin/disks/CMakeFiles/disks.dir/information_schema_disks.cc.o -MF
CMakeFiles/disks.dir/information_schema_disks.cc.o.d -o
CMakeFiles/disks.dir/information_schema_disks.cc.o -c
/<>/plugin/disks/information_schema_disks.cc
/<>/plugin/disks/information_schema_disks.cc:69:31:
error: ‘PATH_MAX’ was not declared in this scope; did you mean
‘AF_MAX’?
69 | Column("Disk", Varchar(PATH_MAX), NOT_NULL),
| ^~~~
| AF_MAX
/<>/plugin/disks/information_schema_disks.cc:70:31:
error: ‘PATH_MAX’ was not declared in this scope; did you mean
‘AF_MAX’?
70 | Column("Path", Varchar(PATH_MAX), NOT_NULL),
| ^~~~
| AF_MAX
make[4]: *** [plugin/disks/CMakeFiles/disks.dir/build.make:79:
plugin/disks/CMakeFiles/disks.dir/information_schema_disks.cc.o] Error
1
make[4]: Leaving directory '/<>/builddir'
make[3]: *** [CMakeFiles/Makefile2:8478:
plugin/disks/CMakeFiles/disks.dir/all] Error 2
Full log at
https://buildd.debian.org/status/fetch.php?pkg=mariadb=hurd-i386=1%3A10.11.7-2=1709941524=0
Bug#1066017: xonsh-doc: please make the build reproducible.
Followup-For: Bug #1066017 Control: forwarded -1 https://salsa.debian.org/python-team/packages/xonsh/-/merge_requests/3
Bug#1065978: Handle listxattr failures better (upstream patch 9.1.0162)
On Sun, Mar 10, 2024 at 05:44:27PM -0400, Paul R. Tagliamonte wrote: > I sent a fix to upstream vim to handle a bug where vim would attempt > to allocate size_t max (for me, 0x aka > 18446744073709551615 bytes) when the filesystem responded with an > error on listxattr other than not supported. > > The upstream patch can be found at > 14759ded57447345ba11c11a99fd84344797862c[1] - I've exported that patch > for inclusion into sid. Thanks! I'll likely refresh against the ~latest upstream once things in the time_t land settle down some, so this will get pulled in then. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1066016: python-rdflib-doc: please make the build reproducible.
Followup-For: Bug #1066016 Control: forwarded -1 https://salsa.debian.org/python-team/packages/rdflib/-/merge_requests/2
Bug#1066018: kakoune: Installs README outside /usr/share/doc/kakoune/
Package: kakoune Version: 2022.10.31-2 Severity: minor Dear Maintainer, I was looking at where the Kakoune package installs its documentation: dpkg-query -L kakoune | sed -e 's@/[^/]*$@@' | sort -u | grep doc ...expecting to find three directories: /usr/share/doc (because it creates a package directory inside here) /usr/share/doc/kakoune/ (Debian package changelog, README, etc.) /usr/share/kak/doc/ (Kakoune's online documentation) Instead, I found an additional fourth directory, /usr/share/doc/kak Apparently the Kakoune README is installed to /usr/share/doc/kak, while all the other package documentation (package changelog, licence, etc.) is installed to /usr/share/doc/kakoune. I think the README should be installed in the directory named after the package, as it is with other Debian packages. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-5-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages kakoune depends on: ii libc6 2.37-15 ii libgcc-s1 14-20240201-3 ii libstdc++6 14-20240201-3 kakoune recommends no packages. kakoune suggests no packages. -- no debconf information
Bug#1066014: python-pathos-doc: please make the build reproducible.
Followup-For: Bug #1066014 Control: forwarded -1 https://salsa.debian.org/python-team/packages/pathos/-/merge_requests/1
Bug#1065751: pristine-tar: diff for NMU version 1.50+nmu2
Hi Sebastian, all, Will this fix be enough for addressing all cases, though? I'm thinking specifically of cases where tarball repacking is involved, for example when using git-buildpackage's "gbp import-orig --uscan" where uscan is used to download and repack the upstream tarball, because the package at hand has a Files-Excluded field in its debian/copyright header stanza. As far as I can tell, Devscripts::Compression would need to be updated to specify -T1 for xz compressions. I believe there are also some cases where git-buildpackage itself does repacking, so we'd probably want to update its gbp.pkg.compressor's Opts to pass in -T1 for xz. Thanks, -a
Bug#1065677: rust-quick-xml: please upgrade to branch v0.31
preliminary analysis upstream changelog doesn't look too scary, no obvious breakage there. rdeps: 0123456789001234567890012345678900123456789001234567890012345678900123456789001234567890 oxigraph (librust-sparesults-dev): jonas package, upstream version in Debian uses 0.30, upstream did make code changes when updating dependency to allow 0.32 but they look fairly minor https://github.com/oxigraph/oxigraph/commit/ab5f5c1c6066df8ca528811322947e045f96e925 rust-bmap-parser: new upstream uses 0.31, but new upstream is semver breaking, upstream did not appear to make any code changes when bumping dep. rust-grcov: latest upstream release uses 0.29, debian currently has 0.29 and is relaxing dependency to allow any 0.x version. Upstream git uses 0.31 and didn't make rust-gsetings-macro: upstream version in Debian already depends on 0.31, Debian is currently downpatching rust-gtk4-macros upstream version in sid depends on 0.30, upstream version in experimental depends on 0.31, debian is currently downpatching. Upstream did not make any code changes when moving from 0.30 to 0.31. rust-gvdb upstream version in sid uses 0.31, debian is currently downpatching. rust-numbat-exchange-rates: upstream version in Debian already depends on 0.32, Debian is currently relaxing rust-plist upstream version in Debian already depends on 0.31, Debian is currently downpatching downpatch includes code changes. rust-quick-junit new upstream depends on 0.31 and is not semver breaking rust-reqsign new upstream depends on 0.31 and is not semver breaking rust-rio (librust-rio-xml-dev) jonas package - debian package is currently downpatching from 0.28 to 0.27 upstream git still uses 0.28 rust-wayland-scanner new upstream uses 0.31, but is semver breaking. Upstream did not appear to make any code changes when bumping dep. rust-xcb new upstream uses 0.30 and is not semver breaking. rust-zbus upstream version in sid uses 0.27, new upstream seems to have moved the quick-xml dependency to the zbus-xml crate. Upstream did not seem to make any code changes when bumping dep. Jonas, can you look at your packages (oxigraph and rust-rio) and prepare them for the new version of quick-xml? I uploaded the new version of quick-xml to experimental yesterday (though at the time of writing it still hasn't built on amd64)
Bug#1066015: patroni-doc: please make the build reproducible.
Package: patroni-doc Followup-For: Bug #1066015 Control: tags -1 - patch (clearing unintentionally-included patch tag)
Bug#1066017: xonsh-doc: please make the build reproducible.
Package: xonsh-doc Severity: wishlist Tags: patch upstream User: reproducible-bui...@lists.alioth.debian.org Usertags: randomness Dear Maintainer, I'm an occasional volunteer contributor with the Reproducible Builds[1] project, and noticed recently that the xonsh-doc package failed[2] an automated reproducibility test on Debian. >From investigation, it seems that most (but not all) of the cause of non-reproducibility during the test was due to the Sphinx autodoc extension evaluating some of the default Python method values (like xonsh.environ.HOSTNAME[3]) at build-time and including the GeneralSetting object address, which varied, in the documentation. As a workaround, we can enable the 'autodoc_preserve_defaults'[4] configuration setting, meaning that Sphinx will render the method signature defaults using the original source code as-written, instead of evaluating the corresponding values. I'll offer a merge request on Salsa to make that change, and will link that to this bugreport. Thanks, James [1] - https://reproducible-builds.org/ [2] - https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/xonsh.html [3] - https://sources.debian.org/src/xonsh/0.14.4%2Bdfsg-1/docs/conf.py/#L317-L320 https://sources.debian.org/src/xonsh/0.14.4%2Bdfsg-1/xonsh/environ.py/#L873-L877 [4] - https://www.sphinx-doc.org/en/master/usage/extensions/autodoc.html#confval-autodoc_preserve_defaults
Bug#1066016: python-rdflib-doc: please make the build reproducible.
Package: python-rdflib-doc Severity: wishlist Tags: patch upstream User: reproducible-bui...@lists.alioth.debian.org Usertags: randomness Dear Maintainer, I'm an occasional volunteer contributor with the Reproducible Builds[1] project, and noticed recently that the python-rdflib-doc package failed[2] an automated reproducibility test on Debian. >From investigation, it seems that most if not all of the cause of non-reproducibility during the test was due to the Sphinx autodoc extension evaluating some of the default Python method values (like rdflib.extras.infixowl.Individual.factoryGraph[3]) at build-time and including theevaluated value, which varied, in the documentation. As a workaround, we can enable the 'autodoc_preserve_defaults'[4] configuration setting, meaning that Sphinx will render the method signature defaults using the original source code as-written, instead of evaluating the corresponding values. I'll offer a merge request on Salsa to make that change, and will link that to this bugreport. Thanks, James [1] - https://reproducible-builds.org/ [2] - https://tests.reproducible-builds.org/debian/rb-pkg/trixie/amd64/diffoscope-results/rdflib.html [3] - https://sources.debian.org/src/rdflib/6.1.1-3/docs/conf.py/#L41 https://sources.debian.org/src/rdflib/6.1.1-3/rdflib/extras/infixowl.py/#L371 [4] - https://www.sphinx-doc.org/en/master/usage/extensions/autodoc.html#confval-autodoc_preserve_defaults
Bug#1066015: patroni-doc: please make the build reproducible.
Package: patroni-doc Severity: wishlist Tags: patch upstream User: reproducible-bui...@lists.alioth.debian.org Usertags: randomness Dear Maintainer, I'm an occasional volunteer contributor with the Reproducible Builds[1] project, and noticed recently that the patroni-doc package failed[2] an automated reproducibility test on Debian. >From investigation, it seems that most if not all of the cause of non-reproducibility during the test was due to the Sphinx autodoc extension evaluating some of the default Python method values (like wal_log_hints[3]) at build-time and including the evaluated value, which varied, in the documentation. As a workaround, we can enable the 'autodoc_preserve_defaults'[4] configuration setting, meaning that Sphinx will render the method signature defaults using the original source code as-written, instead of evaluating the corresponding values. Thanks, James [1] - https://reproducible-builds.org/ [2] - https://tests.reproducible-builds.org/debian/rb-pkg/trixie/amd64/diffoscope-results/patroni.html [3] - https://sources.debian.org/src/patroni/3.2.2-2/patroni/postgresql/config.py/#L303 [4] - https://www.sphinx-doc.org/en/master/usage/extensions/autodoc.html#confval-autodoc_preserve_defaults
Bug#1066014: python-pathos-doc: please make the build reproducible.
Package: python-pathos-doc Severity: wishlist Tags: patch upstream User: reproducible-bui...@lists.alioth.debian.org Usertags: cpu Dear Maintainer, I'm an occasional volunteer contributor with the Reproducible Builds[1] project, and noticed recently that the python-pathos-doc package failed[2] an automated reproducibility test on Debian. >From investigation, it seems that most if not all of the cause of non-reproducibility during the test was due to the Sphinx autodoc extension evaluating some of the default Python method values (like mp.pool_size[3]) at build-time and including the evaluated value, which varied, in the documentation. As a workaround, we can enable the 'autodoc_preserve_defaults'[4] configuration setting, meaning that Sphinx will render the method signature defaults using the original source code as-written, instead of evaluating the corresponding values. I'll offer a merge request on Salsa to make that change, and will link that to this bugreport. Thanks, James [1] - https://reproducible-builds.org/ [2] - https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/pathos.html [3] - https://sources.debian.org/src/pathos/0.3.2-1/docs/source/pathos.rst/#L55 https://sources.debian.org/src/multiprocess/0.70.16-2/py3.11/multiprocess/pool.py/#L277 [4] - https://www.sphinx-doc.org/en/master/usage/extensions/autodoc.html#confval-autodoc_preserve_defaults
Bug#1065821: librsvg: reftest regression for rtl-tspan with pango1.0 1.52.1: 2655 pixels differ from reference
Control: retitle -1 librsvg: reftest regression for rtl-tspan with pango1.0 1.52.1: 2655 pixels differ from reference Control: severity -1 important On Sun, 10 Mar 2024 at 14:45:24 +, Simon McVittie wrote: > For now, I'm testing an upload that will temporarily disable this test, > after which this bug can be downgraded to non-RC. Uploaded, downgrading severity accordingly. smcv
Bug#1066013: O: elementary-icon-theme -- Original set of vector icons for elementary OS
Package: wnpp Control: affects -1 + src:elementary-icon-theme Severity: normal I intend to orphan the elementary-icon-theme package. The package description is: Elementary Icons is an original set of vector icons designed specifically for elementary OS and its desktop environment: Pantheon. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1051237: transition: move files from / to /usr to finalize /usr-merge
On Sat, Mar 09, 2024 at 09:39:50PM +0100, Helmut Grohne wrote: > Hi release team and essential maintainers, > > On Mon, Sep 04, 2023 at 10:33:54PM +0200, Helmut Grohne wrote: > > Once these issues have been resolved, we can move most files except for > > a small set of essential packages. For those, a coordinated upload > > moving their files will be needed as will be an upload of base-files > > adding the aliasing symlinks there. > > We're well into this now. Most of the essential set is moved and I've > most of the remaining pieces. I hope that within one week, we're left > with only: > - base-files > - bash > - dash > - glibc > - util-linux > > Patches for these have been prepared. The current patches are available > from https://salsa.debian.org/helmutg/bootstrap-usrmerge-demo. These > changes have been uploaded to Ubuntu noble already and feedback has been > incorporated. In particular, base-files will now divert to dot files to > avoid cluttering the / view during the transition and base-files will > remove unnecessary diversions (those where it ships symlinks). > > I'd now like to coordinate a time of upload. Given that chroots are > rebuilt in Wednesday and Sunday, I suggest we pick a Thursday morning > for the actual upload. If I unexpectedly break stuff, I still have a few > days to fix. How about March 21st? > > Once this has uploaded, we need to ensure that these packages migrate > together. Also note that dash's autopkgtest will fail unless it uses the > updated base-files, but it cannot depend on base-files. If you prefer, I > can mark the relevant test case as flaky and unmark it in a second > upload. Having a temporary migration block on these packages would also > be a good idea. > > Once agreed, I shall announce this change to d-d-a as I cannot fully > rule out it being disruptive despite the extensive testing performed. > > > We probably have to use NMUs to convert remaining packages at this > > point. Once everything is moved, we may think we're done, but we're not. > > Speaking of the rest of packages. At the time of this writing, the > numbers are: > * 224 source packages can be moved via dh-sequence-movetousr. > * 191 source packages have a dep17 usertagged bug report (most with >patches). > * 141 source packages can be moved with a no-change sourceful upload. >This is about Arch:all packages as we already binNMUed the others. > * 35 source packages cannot be analyzed, because they FTBFS (reported). > * A 1-digit number of packages (e.g. the bootstrap ones above) needs >special handling, but this is communicated and monitored. > > I hope that these numbers go down moving forward (especially the patches > one). At some point, I want to mass-NMU the remaining packages. > > > As packages are restructured throughout the release cycle, they may > > introduce file loss scenarios. Continued monitoring for problems until > > trixie is released is crucial. > > The biggest chunk of findings was due to time64. I think the reports are > timely and actionable. Generally, I hope that we'll run into less > fallout moving forward as the "big" stuff is being handled. One > exception here is that time64 has introduced a pile of "risky replaces". > These are not accounted as buggy in the above numbers but need to be > addressed before we can mass-NMU. That'll happen once the dust settles > on time64. > > Any objections so far? I know my objection is meaningless, and that I will end up dying on this hill. But, I do have an objection. It has come to my attention that the big idea behind it is due to, "compatability." Look, / is for unice universal tools that are found in every unice environment and to service boot up. That's its intention. /usr is for distrobution specific tooling. You are ALREADY doing all the work of putting everything into /usr anyways. I see no reason why the source code of unice universal tools should end up in /usr. Please provide a way for a local admin to break usr-merge. > > Helmut
Bug#1066012: zfs-dkms: Please drop dependencies on python3-distutils
Source: zfs-dkms Version: 2.2.3-1 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1066011: whipper: Please drop dependencies on python3-distutils
Source: whipper Version: 0.10.0-2 Severity: important Tags: trixie sid User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1066010: dvdisaster: FTBFS on arm{el,hf}: test compile... failed
Source: dvdisaster Version: 0.79.10-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=dvdisaster=armel=0.79.10-3%2Bb1=1710109033=0 Looking for includes and libraries: GLib 2.32.0 is required... pkg-config... works test compile... failed The tail of configure.log might contain hints about the compilation problem. make[1]: *** [debian/rules:37: override_dh_auto_configure] Error 1 Cheers -- Sebastian Ramacher
Bug#1065810: tech-ctte: Call for votes on TC membership of Craig Small
===BEGIN The Technical Committee recommends that Craig Small be appointed by the Debian Project Leader to the Technical Committee. C: Recommend to Appoint Craig Small F: Further Discussion ===END I vote C > F Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature
Bug#1066009: wfuzz: Please drop dependencies on python3-distutils
Source: wfuzz Version: 3.1.0-4 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1066008: weresync: Please drop dependencies on python3-distutils
Source: weresync Version: 1.1.5-1 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1066007: qm-dsp: FTBFS on arm{el,hf}: hmm/hmm.c:703:15: error: implicit declaration of function ‘dgetrf_’ [-Werror=implicit-function-declaration]
Source: qm-dsp Version: 1.7.1-7.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=qm-dsp=armhf=1.7.1-7.1=1709536479=0 hmm/hmm.c: In function ‘invert’: hmm/hmm.c:703:15: error: implicit declaration of function ‘dgetrf_’ [-Werror=implicit-function-declaration] 703 | ret = dgetrf_(, , a, , ipiv, ); /* ret should be zero, negative if cov is singular */ | ^~~ hmm/hmm.c:730:9: error: implicit declaration of function ‘dgetri_’ [-Werror=implicit-function-declaration] 730 | dgetri_(, a, , ipiv, , , ); | ^~~ Cheers -- Sebastian Ramacher
Bug#1066006: waypipe: Please drop dependencies on python3-distutils
Source: waypipe Version: 0.8.6-1 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1066005: epic4: FTBFS on arm{el,hf}: gailib.c:95:17: error: implicit declaration of function ‘strlcpy’; did you mean ‘strncpy’? [-Werror=implicit-function-declaration]
Source: epic4 Version: 1:2.10.10-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=epic4=armhf=1%3A2.10.10-1%2Bb5=1709806588=0 gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I./../include -I../include -c gailib.c gailib.c: In function ‘get_name’: gailib.c:95:17: error: implicit declaration of function ‘strlcpy’; did you mean ‘strncpy’? [-Werror=implicit-function-declaration] 95 | strlcpy((ai)->ai_canonname, (str), strlen(str) + 1);\ | ^~~ gailib.c:426:17: note: in expansion of macro ‘GET_CANONNAME’ 426 | GET_CANONNAME(cur, hp->h_name); | ^ cc1: some warnings being treated as errors make[2]: *** [Makefile:31: gailib.o] Error 1 Cheers -- Sebastian Ramacher
Bug#1066004: virulencefinder: Please drop dependencies on python3-distutils
Source: virulencefinder Version: 2.0.5-1 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1066003: libberkeleydb-perl: FTBFS on arm{el,hf}: Failed 1/35 test programs. 1/1861 subtests failed.
Source: libberkeleydb-perl Version: 0.64-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=libberkeleydb-perl=armhf=0.64-2%2Bb3=1709868730=0 Test Summary Report --- t/sequence.t (Wstat: 65280 (exited 255) Tests: 3 Failed: 1) Failed test: 3 Non-zero exit status: 255 Parse errors: Bad plan. You planned 13 tests but ran 3. Files=35, Tests=1861, 3 wallclock secs ( 0.24 usr 0.06 sys + 2.78 cusr 0.30 csys = 3.38 CPU) Result: FAIL Failed 1/35 test programs. 1/1861 subtests failed. make[1]: *** [Makefile:1040: test_dynamic] Error 255 Cheers -- Sebastian Ramacher
Bug#1066002: virt-manager: Please drop dependencies on python3-distutils
Source: virt-manager Version: 1:4.1.0-3 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1066001: libnet-rawip-perl: FTBFS on arm{el,hf}: RawIP.xs:660:14: error: implicit declaration of function ‘tap’; did you mean ‘tan’? [-Werror=implicit-function-declaration]
Source: libnet-rawip-perl
Version: 0.25-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=libnet-rawip-perl=armhf=0.25-3%2Bb3=1709818005=0
arm-linux-gnueabihf-gcc -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv
-fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2
-DVERSION=\"0.25\" -DXS_VERSION=\"0.25\" -fPIC
"-I/usr/lib/arm-linux-gnueabihf/perl/5.38/CORE" -D_LINUX_ -D_ETH_ -D_IFLIST_
-g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -D_GLIBC_ RawIP.c
RawIP.xs: In function ‘XS_Net__RawIP_timem’:
RawIP.xs:614:27: warning: format ‘%u’ expects argument of type ‘unsigned int’,
but argument 2 has type ‘__time64_t’ {aka ‘long long int’} [-Wformat=]
614 | RETVAL = newSVpvf("%u.%06u",tv.tv_sec,tv.tv_usec);
| ^ ~
| |
| __time64_t {aka long long int}
RawIP.xs:614:27: warning: format ‘%u’ expects argument of type ‘unsigned int’,
but argument 3 has type ‘__suseconds64_t’ {aka ‘long long int’} [-Wformat=]
614 | RETVAL = newSVpvf("%u.%06u",tv.tv_sec,tv.tv_usec);
| ^ ~~
| |
| __suseconds64_t {aka
long long int}
RawIP.xs: In function ‘XS_Net__RawIP_tap’:
RawIP.xs:660:14: error: implicit declaration of function ‘tap’; did you mean
‘tan’? [-Werror=implicit-function-declaration]
660 | RETVAL = tap(device,,m);
| ^~~
| tan
RawIP.xs: In function ‘XS_Net__RawIP_mac_disc’:
RawIP.xs:676:14: error: implicit declaration of function ‘mac_disc’
[-Werror=implicit-function-declaration]
676 | RETVAL = mac_disc(addr,m);
| ^~~~
RawIP.xs: In function ‘XS_Net__RawIP_send_eth_packet’:
RawIP.xs:691:5: error: implicit declaration of function ‘send_eth_packet’
[-Werror=implicit-function-declaration]
691 | send_eth_packet(fd, eth_device, (char*)SvPV(pkt,PL_na),
SvCUR(pkt),flag);
| ^~~
In file included from /usr/lib/arm-linux-gnueabihf/perl/5.38/CORE/perl.h:6168,
from RawIP.xs:5:
RawIP.c: In function ‘XS_Net__RawIP_open_live’:
RawIP.c:1791:15: warning: cast from pointer to integer of different size
[-Wpointer-to-int-cast]
1791 | PUSHi((IV)RETVAL);
| ^
/usr/lib/arm-linux-gnueabihf/perl/5.38/CORE/pp.h:428:23: note: in definition of
macro ‘TARGi’
428 | IV TARGi_iv = i;
\
| ^
RawIP.c:1791:9: note: in expansion of macro ‘PUSHi’
1791 | PUSHi((IV)RETVAL);
| ^
RawIP.c: In function ‘XS_Net__RawIP_open_offline’:
RawIP.c:1818:15: warning: cast from pointer to integer of different size
[-Wpointer-to-int-cast]
1818 | PUSHi((IV)RETVAL);
| ^
/usr/lib/arm-linux-gnueabihf/perl/5.38/CORE/pp.h:428:23: note: in definition of
macro ‘TARGi’
428 | IV TARGi_iv = i;
\
| ^
RawIP.c:1818:9: note: in expansion of macro ‘PUSHi’
1818 | PUSHi((IV)RETVAL);
| ^
RawIP.c: In function ‘XS_Net__RawIP_dump_open’:
RawIP.c:1831:29: warning: cast to pointer from integer of different size
[-Wint-to-pointer-cast]
1831 | pcap_t *p = (pcap_t *)SvIV(ST(0))
| ^
RawIP.xs: In function ‘XS_Net__RawIP_lookupdev’:
RawIP.xs:1370:5: warning: ‘pcap_lookupdev’ is deprecated: use
'pcap_findalldevs' and use the first device [-Wdeprecated-declarations]
1370 | RETVAL = pcap_lookupdev(ebuf);
| ^~
In file included from /usr/include/pcap.h:43,
from RawIP.xs:36:
/usr/include/pcap/pcap.h:395:18: note: declared here
395 | PCAP_API char *pcap_lookupdev(char *);
| ^~
RawIP.c: In function ‘XS_Net__RawIP_dispatch’:
RawIP.c:1937:29: warning: cast to pointer from integer of different size
[-Wint-to-pointer-cast]
1937 | pcap_t *p = (pcap_t *)SvIV(ST(0))
| ^
RawIP.c:1941:33: warning: cast to pointer from integer of different size
[-Wint-to-pointer-cast]
1941 | pcap_handlerprint = (pcap_handler)SvIV(ST(2))
| ^
RawIP.xs:1411:16: warning: cast
Bug#1066000: viagee: Please drop dependencies on python3-distutils
Source: viagee Version: 3.7.1-1 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065999: libnet-freedb-perl: FTBFS on arm{el,hf}: lib/linux.h:54:24: error: implicit declaration of function ‘read_toc’ [-Werror=implicit-function-declaration]
Source: libnet-freedb-perl Version: 0.10-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=libnet-freedb-perl=armhf=0.10-4%2Bb2=1709815611=0 arm-linux-gnueabihf-gcc -c -Ilib -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -DVERSION=\"0.10\" -DXS_VERSION=\"0.10\" -fPIC "-I/usr/lib/arm-linux-gnueabihf/perl/5.38/CORE" FreeDB.c In file included from lib/discid.h:37, from FreeDB.xs:8: lib/linux.h: In function ‘get_disc_id’: lib/linux.h:54:24: error: implicit declaration of function ‘read_toc’ [-Werror=implicit-function-declaration] 54 | data.num_of_trks = read_toc(dev); |^~~~ cc1: some warnings being treated as errors make[1]: *** [Makefile:340: FreeDB.o] Error 1 make[1]: Leaving directory '/<>' Cheers -- Sebastian Ramacher
Bug#1065998: versiontools: Please drop dependencies on python3-distutils
Source: versiontools Version: 1.9.1-4 Severity: important Tags: ftbfs trixie sid User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065997: libdata-pond-perl: FTBFS on arm{el,hf}: lib/Data/Pond.xs:159:19: error: implicit declaration of function ‘uvuni_to_utf8_flags’; did you mean ‘uvchr_to_utf8_flags’? [-Werror=implicit-funct
Source: libdata-pond-perl
Version: 0.005-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=libdata-pond-perl=armhf=0.005-2%2Bb3=1709815514=0
lib/Data/Pond.xs:9: warning: "PERL_VERSION_GE" redefined
9 | #define PERL_VERSION_GE(r,v,s) \
|
In file included from /usr/lib/arm-linux-gnueabihf/perl/5.38/CORE/perl.h:3327,
from lib/Data/Pond.xs:3:
/usr/lib/arm-linux-gnueabihf/perl/5.38/CORE/handy.h:578: note: this is the
location of the previous definition
578 | # define PERL_VERSION_GE(j,n,p) (! PERL_VERSION_LT(j,n,p))
|
lib/Data/Pond.xs: In function ‘THX_sv_cat_unichar’:
lib/Data/Pond.xs:159:19: error: implicit declaration of function
‘uvuni_to_utf8_flags’; did you mean ‘uvchr_to_utf8_flags’?
[-Werror=implicit-function-declaration]
159 | vnewend = uvuni_to_utf8_flags(voldend, val, UNICODE_ALLOW_ANY);
| ^~~
| uvchr_to_utf8_flags
lib/Data/Pond.xs:159:17: warning: assignment to ‘U8 *’ {aka ‘unsigned char *’}
from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
159 | vnewend = uvuni_to_utf8_flags(voldend, val, UNICODE_ALLOW_ANY);
| ^
lib/Data/Pond.xs: In function ‘THX_serialise_as_string’:
lib/Data/Pond.xs:580:57: warning: ‘__builtin___sprintf_chk’ may write a
terminating nul past the end of the destination [-Wformat-overflow=]
580 | sprintf(hexbuf, "\\x{%02x}",
| ^~~
In file included from /usr/include/stdio.h:906,
from /usr/lib/arm-linux-gnueabihf/perl/5.38/CORE/perlio.h:41,
from /usr/lib/arm-linux-gnueabihf/perl/5.38/CORE/iperlsys.h:50,
from /usr/lib/arm-linux-gnueabihf/perl/5.38/CORE/perl.h:4485:
In function ‘sprintf’,
inlined from ‘THX_serialise_as_string’ at lib/Data/Pond.xs:580:6:
/usr/include/arm-linux-gnueabihf/bits/stdio2.h:30:10: note:
‘__builtin___sprintf_chk’ output between 7 and 13 bytes into a destination of
size 12
30 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
| ^~
31 | __glibc_objsize (__s), __fmt,
| ~
32 | __va_arg_pack ());
| ~
cc1: some warnings being treated as errors
Cheers
--
Sebastian Ramacher
Bug#1065995: libauthen-smb-perl: FTBFS on arm{el,hf}: smblib.c:494:5: error: implicit declaration of function ‘RFCNB_Free_Pkt’; did you mean ‘RFCNB_Alloc_Pkt’? [-Werror=implicit-function-declaration]
Source: libauthen-smb-perl
Version: 0.91-7
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=libauthen-smb-perl=armhf=0.91-7%2Bb3=1709806890=0
valid.c: In function ‘Valid_User’:
valid.c:22:3: error: implicit declaration of function ‘SMB_Init’
[-Werror=implicit-function-declaration]
22 | SMB_Init();
| ^~~~
valid.c:30:7: error: implicit declaration of function ‘SMB_Negotiate’
[-Werror=implicit-function-declaration]
30 | if (SMB_Negotiate(con, SMB_Prots) < 0) { /* An error */
| ^
valid.c:31:5: error: implicit declaration of function ‘SMB_Discon’; did you
mean ‘SMBtcon’? [-Werror=implicit-function-declaration]
31 | SMB_Discon(con,0);
| ^~
| SMBtcon
Please specify prototyping behavior for Smb.xs (see perlxs manual)
session.c: In function ‘RFCNB_Get_Error_Msg’:
session.c:360:40: error: implicit declaration of function ‘abs’
[-Werror=implicit-function-declaration]
360 | strncpy(msg_buf, RFCNB_Error_Strings[abs(code)], len);
|^~~
session.c:38:1: note: include ‘’ or provide a declaration of ‘abs’
37 | #include "rfcnb-io.h"
+++ |+#include
38 |
mv Smb.xsc Smb.c
smblib-util.c: In function ‘SMB_AtrToStr’:
smblib-util.c:87:5: error: implicit declaration of function ‘strcat’
[-Werror=implicit-function-declaration]
87 | strcat(SMB_Attrib_Temp, (verbose?"Read Only ":"R"));
| ^~
smblib-util.c:30:1: note: include ‘’ or provide a declaration of
‘strcat’
29 | #include "rfcnb.h"
+++ |+#include
30 |
smblib-util.c:87:5: warning: incompatible implicit declaration of built-in
function ‘strcat’ [-Wbuiltin-declaration-mismatch]
87 | strcat(SMB_Attrib_Temp, (verbose?"Read Only ":"R"));
| ^~
smblib-util.c:87:5: note: include ‘’ or provide a declaration of
‘strcat’
smblib-util.c:90:5: warning: incompatible implicit declaration of built-in
function ‘strcat’ [-Wbuiltin-declaration-mismatch]
90 | strcat(SMB_Attrib_Temp, (verbose?"Hidden ":"H"));
| ^~
smblib-util.c:90:5: note: include ‘’ or provide a declaration of
‘strcat’
smblib-util.c:93:5: warning: incompatible implicit declaration of built-in
function ‘strcat’ [-Wbuiltin-declaration-mismatch]
93 | strcat(SMB_Attrib_Temp, (verbose?"System ":"S"));
| ^~
smblib-util.c:93:5: note: include ‘’ or provide a declaration of
‘strcat’
valid.c:42:7: error: implicit declaration of function ‘SMB_Logon_Server’; did
you mean ‘SMB_Connect_Server’? [-Werror=implicit-function-declaration]
42 | if (SMB_Logon_Server(con, USERNAME, PASSWORD) < 0) {
| ^~~~
| SMB_Connect_Server
smblib-util.c:96:5: warning: incompatible implicit declaration of built-in
function ‘strcat’ [-Wbuiltin-declaration-mismatch]
96 | strcat(SMB_Attrib_Temp, (verbose?"Volume ":"V"));
| ^~
smblib-util.c:96:5: note: include ‘’ or provide a declaration of
‘strcat’
smblib-util.c:99:5: warning: incompatible implicit declaration of built-in
function ‘strcat’ [-Wbuiltin-declaration-mismatch]
99 | strcat(SMB_Attrib_Temp, (verbose?"Directory ":"D"));
| ^~
smblib-util.c:99:5: note: include ‘’ or provide a declaration of
‘strcat’
smblib-util.c:102:5: warning: incompatible implicit declaration of built-in
function ‘strcat’ [-Wbuiltin-declaration-mismatch]
102 | strcat(SMB_Attrib_Temp, (verbose?"Archive ":"A"));
| ^~
smblib-util.c:102:5: note: include ‘’ or provide a declaration of
‘strcat’
smblib-util.c: In function ‘SMB_Figure_Protocol’:
smblib-util.c:178:11: error: implicit declaration of function ‘strcmp’
[-Werror=implicit-function-declaration]
178 | if (strcmp(dialects[prot_index], SMB_Prots[i]) == 0) { /* A match
*/
| ^~
smblib-util.c:178:11: note: include ‘’ or provide a declaration of
‘strcmp’
smblib-util.c: In function ‘SMB_Negotiate’:
smblib-util.c:214:29: error: implicit declaration of function ‘strlen’
[-Werror=implicit-function-declaration]
214 | prots_len = prots_len + strlen(Prots[i]) + 2; /* Account for null
etc */
| ^~
smblib-util.c:214:29: note: include ‘’ or provide a declaration of
‘strlen’
smblib-util.c:214:29: warning: incompatible implicit declaration of built-in
function ‘strlen’ [-Wbuiltin-declaration-mismatch]
smblib-util.c:214:29: note: include ‘’ or provide a declaration of
‘strlen’
arm-linux-gnueabihf-gcc -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv
-fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64
Bug#1065996: uwsgi: Please drop dependencies on python3-distutils
Source: uwsgi Version: 2.0.24-2 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065994: ust: Please drop dependencies on python3-distutils
Source: ust Version: 2.13.7-1 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065993: xwiimote: FTBFS on arm{el,hf}:
Source: xwiimote Version: 2-4.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=xwiimote=armhf=2-4.1=1709538546=0 libtool: compile: gcc -DHAVE_CONFIG_H -I. -include ./config.h -I ./lib "-DXWII__EXPORT=__attribute__((visibility(\"default\")))" -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -pipe -fno-common -ffast-math -fdiagnostics-show-option -fno-strict-aliasing -fvisibility=hidden -ffunction-sections -fdata-sections -fstack-protector -O2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -c lib/core.c -fPIC -DPIC -o lib/.libs/libxwiimote_la-core.o /bin/bash ./libtool --tag=CC --mode=link gcc -Wall -pipe -fno-common -ffast-math -fdiagnostics-show-option -fno-strict-aliasing -fvisibility=hidden -ffunction-sections -fdata-sections -fstack-protector -O2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -Wall -Wl,--as-needed -Wl,--gc-sections -Wl,-z,relro -Wl,-z,now -Wl,-z,relro -Wl,-z,now -Wl,--no-undefined -Wl,--as-needed -o xwiidump tools/xwiidump-xwiidump.o lib/core.c: In function ‘read_core’: lib/core.c:815:33: error: ‘struct input_event’ has no member named ‘time’ 815 | memcpy(>time, , sizeof(struct timeval)); | ^ lib/core.c: In function ‘read_accel’: lib/core.c:845:41: error: ‘struct input_event’ has no member named ‘time’ 845 | memcpy(>time, , sizeof(struct timeval)); | ^ lib/core.c: In function ‘read_ir’: lib/core.c:887:41: error: ‘struct input_event’ has no member named ‘time’ 887 | memcpy(>time, , sizeof(struct timeval)); | ^ lib/core.c: In function ‘read_mp’: lib/core.c:939:41: error: ‘struct input_event’ has no member named ‘time’ 939 | memcpy(>time, , sizeof(struct timeval)); | ^ lib/core.c: In function ‘read_bboard’: lib/core.c:991:41: error: ‘struct input_event’ has no member named ‘time’ 991 | memcpy(>time, , sizeof(struct timeval)); | ^ lib/core.c: In function ‘read_pro’: lib/core.c:1120:41: error: ‘struct input_event’ has no member named ‘time’ 1120 | memcpy(>time, , sizeof(struct timeval)); | ^ lib/core.c:1136:41: error: ‘struct input_event’ has no member named ‘time’ 1136 | memcpy(>time, , sizeof(struct timeval)); | ^ Cheers -- Sebastian Ramacher
Bug#1065992: ufw: Please drop dependencies on python3-distutils
Source: ufw Version: 0.36.2-5 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065991: udisks2: Please drop dependencies on python3-distutils
Source: udisks2 Version: 2.10.1-5 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065990: udiskie: Please drop dependencies on python3-distutils
Source: udiskie Version: 2.5.2-1 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1016991: ITP: VulkanSceneGraph -- VulkanSceneGraph (VSG), is a modern, cross platform, high performance scene graph library
Thanks Bret for your work to package this. I've been keeping an eye on upstream and this ITP for a while. One thing I noticed is that upstream integrated their own fork [1] of glslang directly into the build [2] as of 1.0.3 [3]. Their reasoning was that: > Relying upon glslang has turned out to be far more painful that it should be, > with the API evolving over the years, different packaging of glslang being > done in various ways on various platforms has meant that it's been a wake a > mole task trying to keep the VSG working on all the various build and runtime > combinations involving glslang and SPIRV-Tools. I believe this approach would violate Debian Policy on vendored dependencies, which are already available in glslang-dev. I see a few options: 1) We work with upstream to unvendor the dependency 2) We disable the shader compiler part of vsg 3) We patch the build to depend on Debian's glslang package 1) seems unlikely without a lot of work to help fix the original issues encountered by upstream. This was a deliberate choice on their side, so it would require some discussion to see if they'd be happy to try. 2) has a build flag for this, but it disables a significant portion of the library. 3) seems doable - I got it working without build or runtime issues locally, but I'm not sure if this would work in all cases, or if upstream would be happy for us to do this without further discussion. Do you have any thoughts on what is the best approach? IANADD, or involved with vsg; I'm just a user, so I may have missed something obvious. [1] https://github.com/vsg-dev/glslang [2] https://github.com/vsg-dev/VulkanSceneGraph/discussions/728 [3] https://github.com/vsg-dev/VulkanSceneGraph/releases/tag/VulkanSceneGraph-1.0.3
Bug#1065989: tulip: Please drop dependencies on python3-distutils
Source: tulip Version: 5.4.0+dfsg-3 Severity: important Tags: ftbfs trixie sid User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065988: trydiffoscope: Please drop dependencies on python3-distutils
Source: trydiffoscope Version: 67.0.6 Severity: important Tags: ftbfs trixie sid User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065987: toil: Please drop dependencies on python3-distutils
Source: toil Version: 6.1.0-2 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065985: php8.2 hardcodes dependencies on libmagic1
Package: src:php8.2 Version: 8.2.16-2 Severity: serious Tags: sid trixie patch php8.2 hardcodes dependencies on libmagic1, which became libmagic1t64 now. Please don't hard-code dependencies on shared libraries, but e.g. derive them from the dependencies of the libmagic-dev package.
Bug#1065986: php8.3 hardcodes dependencies on libmagic1
Package: src:php8.3 Version: 8.3.0-1 Severity: serious Tags: sid trixie patch php8.3 hardcodes dependencies on libmagic1, which became libmagic1t64 now. Please don't hard-code dependencies on shared libraries, but e.g. derive them from the dependencies of the libmagic-dev package.
Bug#1065984: thefuck: Please drop dependencies on python3-distutils
Source: thefuck Version: 3.29-0.3 Severity: important Tags: trixie sid User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065983: systemfixtures: Please drop dependencies on python3-distutils
Source: systemfixtures Version: 0.6.4-2 Severity: important Tags: trixie sid User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065976: python-levenshtein: FTBFS on arm{el,hf}: Levenshtein/_levenshtein.c:749:15: error: implicit declaration of function ‘PyUnicode_AS_UNICODE’; did you mean ‘PyUnicode_AsUCS4’? [-Werror=impli
Hi, Sebastian Ramacher, on 2024-03-10: > Levenshtein/_levenshtein.c:749:15: error: implicit declaration of function > ‘PyUnicode_AS_UNICODE’; did you mean ‘PyUnicode_AsUCS4’? > [-Werror=implicit-function-declaration] > 749 | string1 = PyUnicode_AS_UNICODE(arg1); This looks to be a duplicate of an initial ftbfs issue I looked up this morning. Ultimately it would be fixed by the latest upstream version of python-levenshtein, but for this to be doable, rapidfuzz-cpp needs to make it to the archive first. Julian pushed rapidfuzz-cpp some time ago to the New queue, thanks! Have a nice day, :) -- .''`. Étienne Mollier : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/4, please excuse my verbosity `- signature.asc Description: PGP signature
Bug#1065982: Would it not be possible to fix deprecated apt-key calls with a script?
Package: apt, (apt 2.4.11 (amd64) on a system using Xubuntu 22.04.3 LTS) Would it be possible to fix deprecated apt-key calls with a script? 1. download a package, 2. download its associated key, 3. open a browser to show me from where the key is downloaded, in order to find the fingerprint of the key, 4. extract the fingerprint from the downloaded key, such that I check the published fingerprint against it and decide, if it is ok. If not: exit. 5. generate a name with ending|*.gpg|for the key under which it shall be stored, which reflects the package for which it is valid, 6. use the file command and grep for "Public Key (old)" and decide whether the provided key has to be|--dearmor|ed or not when it is stored in|/etc/apt/keyrings|(the directory which was advised when I read the article), 7. creates a proper file with a name ending in|.list|to|/etc/apt/sources.list.d|. The file name should be similar to the corresponding|*.gpg|file. The script should write the proper content to this file. If I got it right, the line|deb [signed-by=<.gpg file in /etc/apt/keyrings>] https:// stable main|plays the key role in the solution. 8. Delete the old insecure key which was added by|apt-key|. Or would this be insufficient? Keys in the key ring /etc/apt/trusted.gpg show an uid [ unknown ]. Does this prevent establishing the right realtion between keys and packages?
Bug#1065981: snacc: FTBFS on arm{el,hf}: parse-asn1.c:2716:16: error: implicit declaration of function ‘yylex’ [-Werror=implicit-function-declaration]
Source: snacc
Version: 1.3.1-9.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=snacc=armhf=1.3.1-9.1=1709536993=0
cc -DHAVE_CONFIG_H -I. -I../.. -DCOMPILER -DUSE_NIBBLE_MEMORY=0 -DUSE_EXP_BUF
-I../../c-lib/inc -I../../c-lib/boot -I../../compiler/back-ends
-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 -O0 -DFLEX_IN_USE -c
-o parse-asn1.o parse-asn1.c
parse-asn1.c: In function ‘yyparse’:
parse-asn1.c:2716:16: error: implicit declaration of function ‘yylex’
[-Werror=implicit-function-declaration]
2716 | yychar = yylex ();
|^
parse-asn1.y:712:9: error: implicit declaration of function
‘LexBeginInitialContext’; did you mean ‘LexBeginIntialContext’?
[-Werror=implicit-function-declaration]
712 | LexBeginInitialContext();
| ^~
| LexBeginIntialContext
parse-asn1.y:927:13: error: implicit declaration of function ‘yyerror’; did you
mean ‘yyerrok’? [-Werror=implicit-function-declaration]
927 | yyerror("Warning: positive signed number out of range");
| ^~~
| yyerrok
parse-asn1.y:1872:34: error: implicit declaration of function ‘OidArcNameToNum’
[-Werror=implicit-function-declaration]
1872 | $$->arcNum = OidArcNameToNum ($1);
| ^
parse-asn1.y:1911:9: error: implicit declaration of function ‘AddNewValueDef’
[-Werror=implicit-function-declaration]
1911 | AddNewValueDef (oidElmtValDefsG, $1, newVal);
| ^~
parse-asn1.y: At top level:
parse-asn1.y:3065:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
3065 | yyerror (s)
| ^~~
parse-asn1.y: In function ‘yyerror’:
parse-asn1.y:3068:25: warning: format ‘%d’ expects argument of type ‘int’, but
argument 4 has type ‘long unsigned int’ [-Wformat=]
3068 | fprintf (stderr,"file \"%s\", line %d: %s at symbol
\"%s\"\n\n", modulePtrG->asn1SrcFileName, myLineNoG, s, yytext);
| ^~~
~
|
|
|
long unsigned int
parse-asn1.y: In function ‘InitAsn1Parser’:
parse-asn1.y:3092:9: error: implicit declaration of function ‘yyrestart’
[-Werror=implicit-function-declaration]
3092 | yyrestart (fPtr);
| ^
In file included from parse-asn1.y:78:
parse-asn1.y: In function ‘PushApplTag’:
snacc-util.h:25:42: warning: format ‘%d’ expects argument of type ‘int’, but
argument 4 has type ‘long unsigned int’ [-Wformat=]
25 | fprintf (stderr, "file \"%s\", line %d: ",
fileName, lineNo)
| ^~~~
parse-asn1.y:3159:13: note: in expansion of macro ‘PrintErrLoc’
3159 | PrintErrLoc (modulePtrG->asn1SrcFileName, lineNo);
| ^~~
parse-asn1.y:3160:29: warning: format ‘%d’ expects argument of type ‘int’, but
argument 3 has type ‘long unsigned int’ [-Wformat=]
3160 | fprintf (stderr,"ERROR - APPLICATION tags can be used only
once per ASN.1 module. The tag \"[APPLICATION %d]\" was previously used on
line %d.\n", tagCode, l->lineNo);
|
^~
~~~
|
|
|
long unsigned int
parse-asn1.y:3160:29: warning: format ‘%d’ expects argument of type ‘int’, but
argument 4 has type ‘long unsigned int’ [-Wformat=]
3160 | fprintf (stderr,"ERROR - APPLICATION tags can be used only
once per ASN.1 module. The tag \"[APPLICATION %d]\" was previously used on
line %d.\n", tagCode, l->lineNo);
|
^~
~
|
Bug#1065979: nsync: FTBFS on arm{el,hf}: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below
Source: nsync Version: 1.26.0-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=nsync=armel=1.26.0-1.1=1709541871=0 dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libnsync-cpp1t64/DEBIAN/symbols doesn't match completely debian/libnsync-cpp1t64.symbols --- debian/libnsync-cpp1t64.symbols (libnsync-cpp1t64_1.26.0-1.1_armel) +++ dpkg-gensymbolswG9L1v 2024-03-04 08:44:26.711800650 + @@ -24,8 +24,8 @@ _ZN5nsync15nsync_mu_unlockEPNS_11nsync_mu_s_E@Base 1.20.1 _ZN5nsync15nsync_note_freeEPNS_13nsync_note_s_E@Base 1.20.1 _ZN5nsync15nsync_note_waitEPNS_13nsync_note_s_E8timespec@Base 1.20.1 - (arch=!x32)_ZN5nsync15nsync_time_s_nsElj@Base 1.20.1 - (arch=x32)_ZN5nsync15nsync_time_s_nsExj@Base 1.20.1 +#MISSING: 1.26.0-1.1# (arch=!x32)_ZN5nsync15nsync_time_s_nsElj@Base 1.20.1 + _ZN5nsync15nsync_time_s_nsExj@Base 1.20.1 _ZN5nsync15nsync_time_zeroE@Base 1.20.1 _ZN5nsync16nsync_dll_first_EPNS_20nsync_dll_element_s_E@Base 1.20.1 _ZN5nsync16nsync_mu_runlockEPNS_11nsync_mu_s_E@Base 1.20.1 dh_makeshlibs: error: failing due to earlier errors Cheers -- Sebastian Ramacher
Bug#1065980: gfarm: FTBFS on arm{el,hf}:
Source: gfarm Version: 2.7.20+dfsg-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=gfarm=armhf=2.7.20%2Bdfsg-1.1=1709147793=0 /bin/bash ../../../libtool --mode=compile cc -D_REENTRANT -pthread -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I../../../include -I../../../include -DCOMPAT_GFARM_2_3 -I../../../lib/libgfarm/gfutil -I../../../lib/libgfarm/gfarm -I. -I/usr/include/postgresql-DGFARM_CONFIG='"/etc/gfarm2.conf"' -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -c ./gfp_xdr_server.c ./gfp_xdr.c: In function ‘gfp_xdr_vsend’: ./gfp_xdr.c:484:25: error: implicit declaration of function ‘swab’ [-Werror=implicit-function-declaration] 484 | swab(, , sizeof(nd)); | ^~~~ libtool: compile: cc -D_REENTRANT -pthread -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I../../../include -I../../../include -DCOMPAT_GFARM_2_3 -I../../../lib/libgfarm/gfutil -I../../../lib/libgfarm/gfarm -I. -I/usr/include/postgresql -DGFARM_CONFIG=\"/etc/gfarm2.conf\" -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -c ./gfp_xdr_server.c -fPIC -DPIC -o .libs/gfp_xdr_server.o /bin/bash ../../../libtool --mode=compile cc -D_REENTRANT -pthread -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I../../../include -I../../../include -DCOMPAT_GFARM_2_3 -I../../../lib/libgfarm/gfutil -I../../../lib/libgfarm/gfarm -I. -I/usr/include/postgresql-DGFARM_CONFIG='"/etc/gfarm2.conf"' -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -c ./gfs_proto.c /bin/bash ../../../libtool --mode=compile cc -D_REENTRANT -pthread -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I../../../include -I../../../include -DCOMPAT_GFARM_2_3 -I../../../lib/libgfarm/gfutil -I../../../lib/libgfarm/gfarm -I. -I/usr/include/postgresql-DGFARM_CONFIG='"/etc/gfarm2.conf"' -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -c ./io_fd.c libtool: compile: cc -D_REENTRANT -pthread -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I../../../include -I../../../include -DCOMPAT_GFARM_2_3 -I../../../lib/libgfarm/gfutil -I../../../lib/libgfarm/gfarm -I. -I/usr/include/postgresql -DGFARM_CONFIG=\"/etc/gfarm2.conf\" -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -c ./gfs_proto.c -fPIC -DPIC -o .libs/gfs_proto.o libtool: compile: cc -D_REENTRANT -pthread -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I../../../include -I../../../include -DCOMPAT_GFARM_2_3 -I../../../lib/libgfarm/gfutil -I../../../lib/libgfarm/gfarm -I. -I/usr/include/postgresql -DGFARM_CONFIG=\"/etc/gfarm2.conf\" -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -c ./io_fd.c -fPIC -DPIC -o .libs/io_fd.o /bin/bash ../../../libtool --mode=compile cc -D_REENTRANT -pthread -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I../../../include -I../../../include -DCOMPAT_GFARM_2_3 -I../../../lib/libgfarm/gfutil -I../../../lib/libgfarm/gfarm -I. -I/usr/include/postgresql-DGFARM_CONFIG='"/etc/gfarm2.conf"' -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -c ./metadb_common.c /bin/bash ../../../libtool --mode=compile cc -D_REENTRANT -pthread -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I../../../include -I../../../include -DCOMPAT_GFARM_2_3 -I../../../lib/libgfarm/gfutil -I../../../lib/libgfarm/gfarm -I. -I/usr/include/postgresql
Bug#1065978: Fixed patch
Sorry about that, the last patch had build cruft. Updated. I ought to have read through better - sorry about that. paultag -- :wq vim-listxattr.debdiff Description: Binary data
Bug#1065978: Handle listxattr failures better (upstream patch 9.1.0162)
Package: vim Severity: wishlist Tags: patch I sent a fix to upstream vim to handle a bug where vim would attempt to allocate size_t max (for me, 0x aka 18446744073709551615 bytes) when the filesystem responded with an error on listxattr other than not supported. The upstream patch can be found at 14759ded57447345ba11c11a99fd84344797862c[1] - I've exported that patch for inclusion into sid. All things considered this is a fairly minor fix; so please don't go out of your way for me, but if you're making a routine upload, I've done my best to try to help prepare this patch for inclusion. I've attached a debdiff (with a mediocre changelog entry). I'm running a patched and rebuilt vim locally, this change fixes my error (E342: Out of memory! (allocating 18446744073709551615 bytes)) Thanks for all your work on vim! paultag [1]: https://github.com/vim/vim/commit/14759ded57447345ba11c11a99fd84344797862c vim-listxattr.debdiff Description: Binary data
Bug#1065977: libsearpc: FTBFS on arm{el,hf}: searpc-demo-packet.h:40:34: error: implicit declaration of function ‘write’; did you mean ‘writen’? [-Werror=implicit-function-declaration]
Source: libsearpc
Version: 3.3.0+really3.3+git20230527.783141f-3.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=libsearpc=armhf=3.3.0%2Breally3.3%2Bgit20230527.783141f-3.1=1709152397=0
gcc -DHAVE_CONFIG_H -I. -I.. -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/glib-2.0
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I../lib -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -Wall -pedantic -c -o demo-async-client.o
demo-async-client.c
test-object.c:3:55: warning: ISO C does not allow extra ‘;’ outside of a
function [-Wpedantic]
3 | G_DEFINE_TYPE (TestObject, test_object, G_TYPE_OBJECT);
| ^
In file included from searpc-demo-client.c:13:
searpc-demo-packet.h:22:10: warning: ISO C forbids zero-size array ‘data’
[-Wpedantic]
22 | char data[0];
| ^~~~
searpc-demo-packet.h: In function ‘writen’:
searpc-demo-packet.h:40:34: error: implicit declaration of function ‘write’;
did you mean ‘writen’? [-Werror=implicit-function-declaration]
40 | if ( (nwritten = write(fd, ptr, nleft)) <= 0) {
| ^
| writen
searpc-demo-packet.h: In function ‘readn’:
searpc-demo-packet.h:65:31: error: implicit declaration of function ‘read’; did
you mean ‘readn’? [-Werror=implicit-function-declaration]
65 | if ( (nread = read(fd, buf, nleft)) < 0) {
| ^~~~
| readn
searpc-demo-client.c: In function ‘transport_callback’:
searpc-demo-client.c:34:13: warning: unused variable ‘ret’ [-Wunused-variable]
34 | int fd, ret;
| ^~~
searpc-demo-client.c: In function ‘rpc_string_test’:
searpc-demo-client.c:124:5: error: implicit declaration of function ‘close’;
did you mean ‘pclose’? [-Werror=implicit-function-declaration]
124 | close(sockfd);
| ^
| pclose
In file included from demo-async-client.c:10:
searpc-demo-packet.h:22:10: warning: ISO C forbids zero-size array ‘data’
[-Wpedantic]
22 | char data[0];
| ^~~~
searpc-demo-packet.h: In function ‘writen’:
searpc-demo-packet.h:40:34: error: implicit declaration of function ‘write’;
did you mean ‘writen’? [-Werror=implicit-function-declaration]
40 | if ( (nwritten = write(fd, ptr, nleft)) <= 0) {
| ^
| writen
In file included from searpc-demo-client.c:14:
searpc-demo-client.c: In function ‘rpc_glist_test’:
test-object.h:7:38: error: implicit declaration of function
‘test_object_get_type’; did you mean ‘g_object_get_type’?
[-Werror=implicit-function-declaration]
7 | #define TEST_OBJECT_TYPE(test_object_get_type())
| ^~~~
searpc-demo-client.c:133:44: note: in expansion of macro ‘TEST_OBJECT_TYPE’
133 |TEST_OBJECT_TYPE, , 3,
|^~~~
searpc-demo-packet.h: In function ‘readn’:
searpc-demo-packet.h:65:31: error: implicit declaration of function ‘read’; did
you mean ‘readn’? [-Werror=implicit-function-declaration]
65 | if ( (nread = read(fd, buf, nleft)) < 0) {
| ^~~~
| readn
demo-async-client.c: In function ‘transport_send’:
searpc-demo-client.c: In function ‘main’:
demo-async-client.c:39:19: warning: unused variable ‘pac_ret’
[-Wunused-variable]
39 | packet *pac, *pac_ret;
| ^~~
demo-async-client.c:37:13: warning: unused variable ‘ret’ [-Wunused-variable]
37 | int fd, ret;
| ^~~
demo-async-client.c:37:9: warning: unused variable ‘fd’ [-Wunused-variable]
37 | int fd, ret;
| ^~
searpc-demo-client.c:178:11: warning: unused variable ‘ret_str’
[-Wunused-variable]
178 | char *ret_str;
| ^~~
demo-async-client.c: In function ‘main’:
demo-async-client.c:149:5: error: implicit declaration of function ‘close’; did
you mean ‘pclose’? [-Werror=implicit-function-declaration]
149 | close(sockfd);
| ^
| pclose
demo-async-client.c:92:11: warning: unused variable ‘ret_str’
[-Wunused-variable]
92 | char *ret_str;
| ^~~
In file included from searpc-demo-server.c:13:
searpc-demo-packet.h:22:10: warning: ISO C forbids zero-size array ‘data’
[-Wpedantic]
22 | char data[0];
| ^~~~
In file included from
Bug#1065976: python-levenshtein: FTBFS on arm{el,hf}: Levenshtein/_levenshtein.c:749:15: error: implicit declaration of function ‘PyUnicode_AS_UNICODE’; did you mean ‘PyUnicode_AsUCS4’? [-Werror=impli
Source: python-levenshtein
Version: 0.12.2-3
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=python-levenshtein=armel=0.12.2-3=1709900271=0
arm-linux-gnueabi-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall
-g -Werror=implicit-function-declaration -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.12
-c Levenshtein/_levenshtein.c -o
build/temp.linux-armv8l-cpython-312/Levenshtein/_levenshtein.o
Levenshtein/_levenshtein.c: In function ‘levenshtein_common’:
Levenshtein/_levenshtein.c:731:13: warning: pointer targets in assignment from
‘char *’ to ‘lev_byte *’ {aka ‘unsigned char *’} differ in signedness
[-Wpointer-sign]
731 | string1 = PyString_AS_STRING(arg1);
| ^
Levenshtein/_levenshtein.c:732:13: warning: pointer targets in assignment from
‘char *’ to ‘lev_byte *’ {aka ‘unsigned char *’} differ in signedness
[-Wpointer-sign]
732 | string2 = PyString_AS_STRING(arg2);
| ^
Levenshtein/_levenshtein.c:746:12: error: implicit declaration of function
‘PyUnicode_GET_SIZE’; did you mean ‘PyDict_GET_SIZE’?
[-Werror=implicit-function-declaration]
746 | len1 = PyUnicode_GET_SIZE(arg1);
|^~
|PyDict_GET_SIZE
Levenshtein/_levenshtein.c:749:15: error: implicit declaration of function
‘PyUnicode_AS_UNICODE’; did you mean ‘PyUnicode_AsUCS4’?
[-Werror=implicit-function-declaration]
749 | string1 = PyUnicode_AS_UNICODE(arg1);
| ^~~~
| PyUnicode_AsUCS4
Levenshtein/_levenshtein.c:749:13: warning: assignment to ‘Py_UNICODE *’ {aka
‘unsigned int *’} from ‘int’ makes pointer from integer without a cast
[-Wint-conversion]
749 | string1 = PyUnicode_AS_UNICODE(arg1);
| ^
Levenshtein/_levenshtein.c:750:13: warning: assignment to ‘Py_UNICODE *’ {aka
‘unsigned int *’} from ‘int’ makes pointer from integer without a cast
[-Wint-conversion]
750 | string2 = PyUnicode_AS_UNICODE(arg2);
| ^
Levenshtein/_levenshtein.c: In function ‘hamming_py’:
Levenshtein/_levenshtein.c:816:13: warning: pointer targets in assignment from
‘char *’ to ‘lev_byte *’ {aka ‘unsigned char *’} differ in signedness
[-Wpointer-sign]
816 | string1 = PyString_AS_STRING(arg1);
| ^
Levenshtein/_levenshtein.c:817:13: warning: pointer targets in assignment from
‘char *’ to ‘lev_byte *’ {aka ‘unsigned char *’} differ in signedness
[-Wpointer-sign]
817 | string2 = PyString_AS_STRING(arg2);
| ^
Levenshtein/_levenshtein.c:832:13: warning: assignment to ‘Py_UNICODE *’ {aka
‘unsigned int *’} from ‘int’ makes pointer from integer without a cast
[-Wint-conversion]
832 | string1 = PyUnicode_AS_UNICODE(arg1);
| ^
Levenshtein/_levenshtein.c:833:13: warning: assignment to ‘Py_UNICODE *’ {aka
‘unsigned int *’} from ‘int’ makes pointer from integer without a cast
[-Wint-conversion]
833 | string2 = PyUnicode_AS_UNICODE(arg2);
| ^
Levenshtein/_levenshtein.c: In function ‘jaro_py’:
Levenshtein/_levenshtein.c:860:13: warning: pointer targets in assignment from
‘char *’ to ‘lev_byte *’ {aka ‘unsigned char *’} differ in signedness
[-Wpointer-sign]
860 | string1 = PyString_AS_STRING(arg1);
| ^
Levenshtein/_levenshtein.c:861:13: warning: pointer targets in assignment from
‘char *’ to ‘lev_byte *’ {aka ‘unsigned char *’} differ in signedness
[-Wpointer-sign]
861 | string2 = PyString_AS_STRING(arg2);
| ^
Levenshtein/_levenshtein.c:870:13: warning: assignment to ‘Py_UNICODE *’ {aka
‘unsigned int *’} from ‘int’ makes pointer from integer without a cast
[-Wint-conversion]
870 | string1 = PyUnicode_AS_UNICODE(arg1);
| ^
Levenshtein/_levenshtein.c:871:13: warning: assignment to ‘Py_UNICODE *’ {aka
‘unsigned int *’} from ‘int’ makes pointer from integer without a cast
[-Wint-conversion]
871 | string2 = PyUnicode_AS_UNICODE(arg2);
| ^
Levenshtein/_levenshtein.c: In function ‘jaro_winkler_py’:
Levenshtein/_levenshtein.c:910:13: warning: pointer targets in assignment from
‘char *’ to ‘lev_byte *’ {aka ‘unsigned char *’} differ in signedness
[-Wpointer-sign]
910 | string1 = PyString_AS_STRING(arg1);
| ^
Levenshtein/_levenshtein.c:911:13: warning: pointer targets in assignment from
‘char *’ to ‘lev_byte *’ {aka ‘unsigned char *’} differ in signedness
[-Wpointer-sign]
911 | string2 = PyString_AS_STRING(arg2);
| ^
Bug#1065975: libnet-nis-perl: FTBFS on arm{el,hf}: NIS.xs:499:11: error: implicit declaration of function ‘yp_maplist’; did you mean ‘xdr_pmaplist’? [-Werror=implicit-function-declaration]
Source: libnet-nis-perl Version: 0.44-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=libnet-nis-perl=armhf=0.44-2%2Bb4=1709894189=0 arm-linux-gnueabihf-gcc -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/tirpc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -DVERSION=\"0.44\" -DXS_VERSION=\"0.44\" -fPIC "-I/usr/lib/arm-linux-gnueabihf/perl/5.38/CORE" NIS.c NIS.xs: In function ‘XS_Net__NIS_yp_order’: NIS.xs:446:39: warning: passing argument 3 of ‘yp_order’ from incompatible pointer type [-Wincompatible-pointer-types] 446 | yp_status = yp_order(domain, map, ); | ^~ | | | long unsigned int * In file included from /usr/include/rpcsvc/yp_prot.h:11, from NIS.xs:10: /usr/include/rpcsvc/ypclnt.h:71:50: note: expected ‘unsigned int *’ but argument is of type ‘long unsigned int *’ 71 | extern int yp_order (const char *, const char *, unsigned int *); | ^~ NIS.c: In function ‘XS_Net__NIS_yperr_string’: NIS.c:770:16: warning: assignment discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers] 770 | RETVAL = yperr_string(code); |^ NIS.xs: In function ‘XS_Net__NIS_yp_maplist’: NIS.xs:499:11: error: implicit declaration of function ‘yp_maplist’; did you mean ‘xdr_pmaplist’? [-Werror=implicit-function-declaration] 499 | ret = yp_maplist( domain, ); | ^~ | xdr_pmaplist cc1: some warnings being treated as errors make[1]: *** [Makefile:343: NIS.o] Error 1 Cheers -- Sebastian Ramacher
Bug#1065974: ghmm: FTBFS on arm{el,hf}: mcmc.c:144:3: error: implicit declaration of function ‘init_priors’ [-Werror=implicit-function-declaration]
Source: ghmm
Version: 0.9~rc3-5.1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=ghmm=armhf=0.9%7Erc3-5.1=1709147715=0
/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 -I/usr/include/arm-linux-gnueabihf
-I/usr/include/libxml2 -Wl,-z,relro -Wl,-z,now -o libxml-test libxml-test.o
../ghmm/.libs/libghmm.a -lm -lm -lm -lm -lpthread -llapacke -lxml2
mcmc.c: In function ‘main’:
mcmc.c:144:3: error: implicit declaration of function ‘init_priors’
[-Werror=implicit-function-declaration]
144 | init_priors(mo, , , );
| ^~~
mcmc.c:146:15: error: implicit declaration of function ‘ghmm_dmodel_cfbgibbs’;
did you mean ‘ghmm_dmodel_logp’? [-Werror=implicit-function-declaration]
146 | int * Q = ghmm_dmodel_cfbgibbs(mo, my_output,
| ^~~~
| ghmm_dmodel_logp
mcmc.c:146:15: warning: initialization of ‘int *’ from ‘int’ makes pointer from
integer without a cast [-Wint-conversion]
mcmc.c:148:108: warning: passing argument 4 of ‘ghmm_dmodel_viterbi_logp’ makes
pointer from integer without a cast [-Wint-conversion]
148 | printf("viterbi prob mcmc%f \n", ghmm_dmodel_viterbi_logp(mo,
my_output->seq[0], my_output->seq_len[0], Q[0]));
|
~^~~
|
|
|
int
In file included from mcmc.c:13:
../ghmm/viterbi.h:75:76: note: expected ‘int *’ but argument is of type ‘int’
75 | double ghmm_dmodel_viterbi_logp (ghmm_dmodel * mo, int *o, int len,
int *state_seq);
|
~^
/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 -I/usr/include/arm-linux-gnueabihf
-I/usr/include/libxml2 -Wl,-z,relro -Wl,-z,now -o chmm chmm.o
../ghmm/.libs/libghmm.a -lm -lm -lm -lm -lpthread -llapacke -lxml2
/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 -I/usr/include/arm-linux-gnueabihf
-I/usr/include/libxml2 -Wl,-z,relro -Wl,-z,now -o chmm_test chmm_test.o
../ghmm/.libs/libghmm.a -lm -lm -lm -lm -lpthread -llapacke -lxml2
cc1: some warnings being treated as errors
make[5]: *** [Makefile:823: mcmc.o] Error 1
Cheers
--
Sebastian Ramacher
Bug#1065973: kmod: FTBFS on arm{el,hf}: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
Source: kmod Version: 32-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=kmod=armhf=32-1=1709960074=0 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -include ./config.h -I.. -DSYSCONFDIR=\"/etc\" -DDISTCONFDIR=\"/usr/lib\" -DMODULE_DIRECTORY=\"/lib/modules\" -DABS_TOP_BUILDDIR=\"/<>/build-deb\" -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -DANOTHER_BRICK_IN_THE -Wall -W -Wextra -Wno-inline -Wvla -Wundef -Wformat=2 -Wlogical-op -Wsign-compare -Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls -Wmissing-declarations -Wmissing-noreturn -Wshadow -Wendif-labels -Wstrict-aliasing=3 -Wwrite-strings -Wno-long-long -Wno-overlength-strings -Wno-unused-parameter -Wno-missing-field-initializers -Wno-unused-result -Wnested-externs -Wchar-subscripts -Wtype-limits -Wuninitialized -fno-common -fdiagnostics-show-option -fvisibility=hidden -ffunction-sections -fdata-sections -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -c ../testsuite/path.c -fPIC -DPIC -o testsuite/.libs/path_la-path.o In file included from /usr/include/features.h:393, from /usr/include/assert.h:35, from ../testsuite/path.c:22: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" 26 | # error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" | ^ Cheers -- Sebastian Ramacher
Bug#1065972: pngphoon: FTBFS on arm{el,hf}: tws.c:40:13: error: conflicting types for ‘time’; have ‘long int()’
Source: pngphoon
Version: 1.3-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=pngphoon=armhf=1.3-3%2Bb1=1709981075=0
tws.c:40:13: error: conflicting types for ‘time’; have ‘long int()’
40 | extern long time();
| ^~~~
In file included from /usr/include/features.h:490,
from
/usr/include/arm-linux-gnueabihf/bits/libc-header-start.h:33,
from /usr/include/stdio.h:27,
from tws.c:29:
/usr/include/time.h:86:15: note: previous declaration of ‘time’ with type
‘time_t(time_t *)’ {aka ‘long long int(long long int *)’}
86 | extern time_t __REDIRECT_NTH (time, (time_t *__timer), __time64);
| ^~
tws.c: In function ‘dlocaltime’:
tws.c:72:20: warning: passing argument 1 of ‘localtime’ from incompatible
pointer type [-Wincompatible-pointer-types]
72 |tm = localtime( clock );
|^
||
|long int *
/usr/include/time.h:141:19: note: expected ‘const time_t *’ {aka ‘const long
long int *’} but argument is of type ‘long int *’
141 | extern struct tm *__REDIRECT_NTH (localtime, (const time_t *__timer),
| ^~
make[1]: *** [Makefile:12: tws.o] Error 1
Cheers
--
Sebastian Ramacher
Bug#1065971: libgdchart-gd2: FTBFS on arm{el,hf}: ../gdc.c:284:74: error: implicit declaration of function ‘strlen’ [-Werror=implicit-function-declaration]
Source: libgdchart-gd2 Version: 0.11.5-10 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=libgdchart-gd2=armhf=0.11.5-10%2Bb1=1709991773=0 arm-linux-gnueabihf-gcc -I. -I.. -I/usr/include/freetype2 -I/usr/include/freetype2/freetype -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -D_REENTRANT -pipe -DHAVE_LIBPNG -DHAVE_LIBFREETYPE -DHAVE_LIBJPEG -fsigned-char -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o gdc.o ../gdc.c ../gdc.c: In function ‘out_err’: ../gdc.c:284:74: error: implicit declaration of function ‘strlen’ [-Werror=implicit-function-declaration] 284 |IMGWIDTH/2 - GDC_fontc[GDC_MEDBOLD].w*strlen(err_str)/2, | ^~ ../gdc.c:8:1: note: include ‘’ or provide a declaration of ‘strlen’ 7 | #include "gdc.h" +++ |+#include 8 | ../gdc.c:284:74: warning: incompatible implicit declaration of built-in function ‘strlen’ [-Wbuiltin-declaration-mismatch] 284 |IMGWIDTH/2 - GDC_fontc[GDC_MEDBOLD].w*strlen(err_str)/2, | ^~ ../gdc.c:284:74: note: include ‘’ or provide a declaration of ‘strlen’ cc1: some warnings being treated as errors make[1]: *** [: gdc.o] Error 1 Cheers -- Sebastian Ramacher
Bug#1019042: [Pkg-rust-maintainers] Bug#1019042: rust-qwertone: FTBFS - dep issue
I partially started to patch gtk3-rs to use the newer glib from experimental. However, this is not really supported and I'd rather remove it now that it's EOL. For qwertone we can employ partial vendoring; this will also need to be done for squeekboard (in progress). I'd appreciate if you agree on vendoring gtk3-rs in so I can go ahead with my removal plans. This might be the best solution going forward. Personally, if we are going to keep gtk3-rs around, particularly if two or more apps are using it, I'd much rather it be in the form of individually packaged crates than as vendored copies in application packages. How much overlap is there between the gtk3-rs and gtk4-rs stacks? how many semver-suffix packages would we have to introduce if we wanted to keep the gtk3 stack the way it is while upgrading the gtk4 stack.
Bug#1065970: system-config-printer: Please drop dependencies on python3-distutils
Source: system-config-printer Version: 1.5.18-1 Severity: important Tags: ftbfs trixie sid User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065969: ike-scan: FTBFS on arm{el,hf}: configure: error: cannot determine snprintf format string for long long int
Source: ike-scan
Version: 1.9.5-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=ike-scan=armhf=1.9.5-1%2Bb2=1709990104=0
checking snprintf format for long long int... none
configure: error: cannot determine snprintf format string for long long int
...
configure:5765: checking snprintf format for long long int
configure:5803: gcc -o conftest -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -Wall -Wshadow
-Wwrite-strings -Wextra -fstack-protector -D_FORTIFY_SOURCE=2 -Wformat
-Wformat-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64
-Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now conftest.c >&5
conftest.c: In function 'does_int64_snprintf_work':
conftest.c:58:7: error: implicit declaration of function 'strcmp'
[-Werror=implicit-function-declaration]
58 | if (strcmp(buf, "8014005") != 0)
| ^~
conftest.c:42:1: note: include '' or provide a declaration of 'strcmp'
41 | #include
+++ |+#include
42 | typedef long long int int64;
conftest.c: At top level:
conftest.c:62:1: warning: return type defaults to 'int' [-Wimplicit-int]
62 | main() {
| ^~~~
cc1: some warnings being treated as errors
Cheers
--
Sebastian Ramacher
Bug#1065968: sympy: Please drop dependencies on python3-distutils
Source: sympy Version: 1.12-7 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#968148: Would it not be possible to fix deprecated apt-key calls with a script?
Would it be possible to fix deprecated apt-key calls with a script? 1. download a package, 2. download its associated key, 3. open a browser to show me from where the key is downloaded, in order to find the fingerprint of the key, 4. extract the fingerprint from the downloaded key, such that I check the published fingerprint against it and decide, if it is ok. If not: exit. 5. generate a name with ending|*.gpg|for the key under which it shall be stored, which reflects the package for which it is valid, 6. use the file command and grep for "Public Key (old)" and decide whether the provided key has to be|--dearmor|ed or not when it is stored in|/etc/apt/keyrings|(the directory which was advised when I read the article), 7. creates a proper file with a name ending in|.list|to|/etc/apt/sources.list.d|. The file name should be similar to the corresponding|*.gpg|file. The script should write the proper content to this file. If I got it right, the line|deb [signed-by=<.gpg file in /etc/apt/keyrings>] https:// stable main|plays the key role in the solution. 8. Delete the old insecure key which was added by|apt-key|. Or would this be insufficient? Keys in the key ring /etc/apt/trusted.gpg show an uid [ unknown ]. Does this prevent establishing the right realtion between keys and packages? OpenPGP_0x07C3FA21AE77B98E.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1064147: ftbfs: test failures affecting Bio.SeqIO.SeqXmlIO
Control: severity -1 normal I reduce the severity. The version 1.83+dfsg-1 recently uploaded skips the affected tests, due to lack of better options. I leave the issue open in case someone comes up with a more appropriate way to resolve this, but the situation is not serious anymore. -- .''`. Étienne Mollier : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/1, please excuse my verbosity `-on air: Fates Warning - From The Rooftops signature.asc Description: PGP signature
Bug#1065967: sunpy: Please drop dependencies on python3-distutils
Source: sunpy Version: 5.1.1-1 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065966: gsocket: FTBFS on arm{el,hf}: /tmp/ccmyiWuJ.s:4004: Error: symbol `__lstat64_time64' is already defined
Source: gsocket Version: 1.4.41-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=gsocket=armhf=1.4.41-1%2Bb1=1709989725=0 gcc -DHAVE_CONFIG_H -I. -I.. -I./../include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -shared -fPIC -O2 -Wall -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -c -o gsocket_uchroot_dso_so_0-gsocket_uchroot_dso.o `test -f 'gsocket_uchroot_dso.c' || echo './'`gsocket_uchroot_dso.c gcc -O2 -Wall -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -o gs-netcat gs_netcat-4_gs-netcat.o gs_netcat-utils.o gs_netcat-socks.o gs_netcat-console.o gs_netcat-ids.o gs_netcat-event_mgr.o gs_netcat-pkt_mgr.o gs_netcat-console_display.o gs_netcat-filetransfer.o gs_netcat-globbing.o gs_netcat-filetransfer_mgr.o gs_netcat-gsocket_dso-lib.o ../lib/libgsocket.a -lssl -lcrypto -ldl -lutil gcc -O2 -Wall -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -o gs-helloworld gs_helloworld-1_gs-helloworld.o gs_helloworld-utils.o gs_helloworld-gsocket_dso-lib.o ../lib/libgsocket.a -lssl -lcrypto -ldl -lutil gcc -shared -fPIC -O2 -Wall -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -ldl -Wl,-soname=gsocket_dso.so.0 -Wl,-z,relro -Wl,-z,now -o gsocket_dso.so.0 gsocket_dso_so_0-gsocket_dso.o gsocket_dso_so_0-gsocket_dso-lib.o -lssl -lcrypto -ldl -lutil gcc -O2 -Wall -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -o gs-pipe gs_pipe-2_gs-pipe.o gs_pipe-utils.o gs_pipe-gsocket_dso-lib.o ../lib/libgsocket.a -lssl -lcrypto -ldl -lutil /tmp/ccmyiWuJ.s: Assembler messages: /tmp/ccmyiWuJ.s:3773: Error: symbol `__stat64_time64' is already defined /tmp/ccmyiWuJ.s:4004: Error: symbol `__lstat64_time64' is already defined make[3]: *** [Makefile:959: gsocket_uchroot_dso_so_0-gsocket_uchroot_dso.o] Error 1 make[3]: *** Waiting for unfinished jobs make[3]: Leaving directory '/<>/tools' make[2]: *** [Makefile:387: all-recursive] Error 1 Cheers -- Sebastian Ramacher
Bug#1065965: streamtuner2: Please drop dependencies on python3-distutils
Source: streamtuner2 Version: 2.2.2+dfsg-2 Severity: important Tags: trixie sid User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065964: stegcracker: Please drop dependencies on python3-distutils
Source: stegcracker Version: 2.1.0-3 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065963: foxeye: FTBFS on arm{el,hf}: configure: error: you have no encryption library but need it for password save.
Source: foxeye
Version: 0.12.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=foxeye=armhf=0.12.1-4%2Bb1=1709989052=0
yes
checking for strncasecmp... rm: cannot remove 'core': Is a directory
yes
checking for towlower... rm: cannot remove 'core': Is a directory
yes
checking whether you need libcrypt... rm: cannot remove 'core': Is a directory
rm: cannot remove 'core': Is a directory
no
configure: error: you have no encryption library but need it for password save.
rm: cannot remove 'core': Is a directory
...
configure:9575: gcc -o conftest -pthread -O2 -g -pipe -Wall -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fpic -fno-strict-aliasing -Wextra
-Wno-unused-parameter -Wno-pointer-sign -Wno-long-long -Wno-trigraphs
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time
-D_FORTIFY_SOURCE=2 -Wl,-z,defs -Wl,-O1 -rdynamic -Wl,-z,relro -Wl,-z,now
conftest.c -lcrypt >&5
conftest.c: In function 'main':
conftest.c:70:1: error: implicit declaration of function 'crypt'
[-Werror=implicit-function-declaration]
70 | crypt ("","");
| ^
cc1: some warnings being treated as errors
Cheers
--
Sebastian Ramacher
Bug#1065962: sshuttle: Please drop dependencies on python3-distutils
Source: sshuttle Version: 1.1.2-1 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1064475: lists.debian.org: missing recent posts in search indices.
Thanks for reporting this. On Sat, Mar 09, 2024 at 06:29:22PM +, James Addison wrote: > Running a search for 'python removal' on the 'testing-changes' mailing list, > ordered by most-recent-first, currently lacks any results from this year. > > > https://lists.debian.org/cgi-bin/search?P=python+removal=and=Gdebian-testing-changes=0=100=python%09removal=Gdebian-testing-changes%7E.%7E%7E0 There are currently 7 shards in the lists database, but only the first 6 were listed to be searched. It looks like indexing is working fine, except it started a new shard and failed to update the list to search. I've manually fixed this and now the search above gives me a top result of: Testing removal summary 2024-03-10 (Sunday) I really need to resolve why this didn't happen automatically or else this will go wrong again in the future. Cheers, Olly
Bug#1065961: sra-sdk: Please drop dependencies on python3-distutils
Source: sra-sdk Version: 3.0.3+dfsg-6 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065960: spopt: Please drop dependencies on python3-distutils
Source: spopt Version: 0.5.0-4 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065959: sphinx: Please drop dependencies on python3-distutils
Source: sphinx Version: 7.2.6-4 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065958: soapysdr: Please drop dependencies on python3-distutils
Source: soapysdr Version: 0.8.1-4 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065956: mtd-utils: FTBFS on arm{el,hf}: FAIL mtdlib_test (exit status: 17)
Source: mtd-utils Version: 1:2.1.6-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=mtd-utils=armel=1%3A2.1.6-1%2Bb2=1709994938=0 [ FAILED ] test_mtd_get_dev_info1 [==] tests: 17 test(s) run. [ PASSED ] 0 test(s). [ FAILED ] tests: 17 test(s), listed below: [ FAILED ] test_libmtd_open [ FAILED ] test_mtd_is_bad [ FAILED ] test_mtd_mark_bad [ FAILED ] test_mtd_lock [ FAILED ] test_mtd_unlock [ FAILED ] test_mtd_is_locked [ FAILED ] test_mtd_regioninfo [ FAILED ] test_mtd_erase_multi [ FAILED ] test_mtd_erase [ FAILED ] test_mtd_read [ FAILED ] test_mtd_write_nooob [ FAILED ] test_mtd_write_withoob [ FAILED ] test_mtd_read_oob [ FAILED ] test_mtd_write_oob [ FAILED ] test_mtd_dev_present [ FAILED ] test_mtd_get_info [ FAILED ] test_mtd_get_dev_info1 17 FAILED TEST(S) FAIL mtdlib_test (exit status: 17) Testsuite summary for mtd-utils 2.1.6 # TOTAL: 2 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 See ./test-suite.log Please report to linux-...@lists.infradead.org Cheers -- Sebastian Ramacher
Bug#1036826: Please start handling \c
severity 1036826 normal thanks please don't abuse the severity. po4a is not only for groff, and many groff pages do work without it. Instead, I'd appreciate if you could do a merge request with a test file, along with the expected output. It'd save me the time to dig into the discussion of this bug. I'm not saying that I won't fix it w/o this test case. I'm just saying that providing a test case is a better approach to speedup the fix than severity abuse. Thanks for your help, Mt Le samedi 09 mars 2024 à 12:39 +, Helge Kreutzmann a écrit : > severity 1036826 important > thanks > > Hello Martin, > you have been quite in this discussion. \c occurs in more and more man > pages, and currently the build fails for them. In turn, they are no > longer translated. > > Could you kindly check if you could add support for "\c" or is there > another workaround? > > Thanks for your support! > > Greetings > > Helge signature.asc Description: This is a digitally signed message part
Bug#1065957: sndobj: Please drop dependencies on python3-distutils
Source: sndobj Version: 2.6.7+ds1-3 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065955: slepc4py: Please drop dependencies on python3-distutils
Source: slepc4py Version: 3.19.2-3 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065954: tcltrf: FTBFS on arm{el,hf}:
Source: tcltrf Version: 2.1.4-dfsg3-2.1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=tcltrf=armhf=2.1.4-dfsg3-2.1%2Bb2=1709994458=0 gcc -DPACKAGE_NAME=\"Trf\" -DPACKAGE_TARNAME=\"trf\" -DPACKAGE_VERSION=\"2.1.4\" -DPACKAGE_STRING=\"Trf\ 2.1.4\" -DPACKAGE_BUGREPORT=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_PARAM_H=1 -DSIZEOF_INT=4 -DSIZEOF_LONG_INT=4 -DUSE_THREAD_ALLOC=1 -D_REENTRANT=1 -D_THREAD_SAFE=1 -DTCL_THREADS=1 -DMODULE_SCOPE=extern\ __attribute__\(\(__visibility__\(\"hidden\"\)\)\) -D_LARGEFILE64_SOURCE=1 -DTCL_WIDE_INT_TYPE=long\ long -DHAVE_STRUCT_STAT64=1 -DHAVE_OPEN64=1 -DHAVE_LSEEK64=1 -DHAVE_TYPE_OFF64_T=1 -DUSE_TCL_STUBS=1 -DUSE_ZLIBTCL_STUBS=1 -DHAVE_ZLIB_H=1 -DHAVE_SSL_H=1 -DHAVE_MD2_H=1 -DHAVE_MD5_H=1 -DHAVE_SHA_H=1 -DHAVE_BZ2_H=1 -DZLIB_STATIC_BUILD=1 -DBZLIB_STATIC_BUILD=1 -DMD5_STATIC_BUILD=1 -DHAVE_DLFCN_H=1 -DHAVE_STDLIB_H=1 -DHAVE_FEATURES_H=1 -DMD5_STATIC_BUILD=1 -DZLIBTCL_VERSION=\"\" -I"." -I"./generic" -I"" -I"" -I"/usr/include" -I"/usr/include/openssl" -DLIBZ_DEFAULTNAME=\"libz.so\" -I"/usr/include/tcl"-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -DSSL_STATIC_BUILD=1 -D_XOPEN_SOURCE -pipe -O2 -fomit-frame-pointer -Wall -Wno-implicit-int -fPIC -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -c `echo ./generic/crypt.c` -o crypt.o ./generic/crypt.c: In function ‘TrfCryptObjCmd’: ./generic/crypt.c:96:35: error: implicit declaration of function ‘crypt’ [-Werror=implicit-function-declaration] 96 | res = Tcl_NewStringObj ((char*) crypt (passwd, salt_b), -1); | ^ cc1: some warnings being treated as errors make[2]: *** [Makefile:260: crypt.o] Error 1 Cheers -- Sebastian Ramacher
Bug#1065953: sagemath: Please drop dependencies on python3-distutils
Source: sagemath Version: 9.5-6 Severity: important Tags: ftbfs trixie sid User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham
Bug#1065951: vde: FTBFS on arm{el,hf}: /tmp/ccwOo5J4.s:341: Error: symbol `open64' is already defined
Source: vde2 Version: 2.3.2+r586-9.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=vde2=armel=2.3.2%2Br586-9.1%2Bb1=1709997351=0 libvdetap.c:147:31: warning: ‘__builtin___snprintf_chk’ output may be truncated before the last format character [-Wformat-truncation=] 147 | snprintf(buf,16,"%s_%s",ifr->ifr_name,suffix); | ^ In file included from /usr/include/stdio.h:906, from libvdetap.c:6: In function ‘snprintf’, inlined from ‘getvdeopt’ at libvdetap.c:147:2: /usr/include/arm-linux-gnueabi/bits/stdio2.h:54:10: note: ‘__builtin___snprintf_chk’ output 2 or more bytes (assuming 17) into a destination of size 16 54 | return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1, | ^~~~ 55 |__glibc_objsize (__s), __fmt, |~ 56 |__va_arg_pack ()); |~ /tmp/ccwOo5J4.s: Assembler messages: /tmp/ccwOo5J4.s:341: Error: symbol `open64' is already defined make[3]: *** [Makefile:530: libvdetap_la-libvdetap.lo] Error 1 Cheers -- Sebastian Ramacher
