Bug#1061059: javaws.sh fails to determine java version if extra java options exist
Package: icedtea-netx Version: 1.8.8-2 I pass some extra scaling option on my system to JAVA so i can actually read something on a 4K laptop display so the -version call in javaws.sh receives a string like 'Picked up JAVA_TOOL_OPTIONS: -Dsun.java2d.uiScale=2.0 openjdk version "11.0.20"...' on my system resulting in the cut sequence to fail which is supposed to determine the java version number to set MODULAR_JDK=(YES|NO). I can imagine that it's a challenge to get an easy solution working with any java to extract the java version number. I might be the only one doing something like that, but I can imagine any extra options exported to java will do the trick failing this test.
Bug#1060056:
merged - https://github.com/MariaDB/server/pull/2995
Bug#1061058: RM: python3-compyle [ppc64el s390x] -- RoM ANAIS
Package: python3-compyle Version: 0.8.1-8 Severity: normal X-Debbugs-Cc: antonio.valent...@tiscali.it Dear Maintainer, apparently one of the build dependencies of compyle (pocl-opencl-icd) is no longer available on the ppc64el and s390x. This prevents the migration of compyle to testing. Removing python3-compyle for the ppc64el and s390x is expected to allow the migration of compyle to testing. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-14-generic (SMP w/8 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 python3-compyle depends on: ii python3 3.11.6-1 pn python3-mako ii python3-numpy 1:1.24.2-2 pn python3-pytools ii python3-setuptools 68.1.2-2 python3-compyle recommends no packages. Versions of packages python3-compyle suggests: pn cython3 pn python3-pycuda pn python3-pyopencl
Bug#1061049: libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in libcholmod5 without bumping to "libcholmod6"
Hi Dima,
Le mardi 16 janvier 2024 à 15:06 -0800, Dima Kogan a écrit :
> Hi. I'm chasing down
>
> http://bugs.debian.org/1060986
>
> The problem is that mrcal uses libdogleg, which contains
>
> typedef struct
> {
> cholmod_common common;
>
> } dogleg_solverContext_t;
>
> The existing "libdogleg2" package was built against libsuitesparse-dev
> 7.3, so it must be linked with packages that use that ABI. But in
> suitesparse 7.4 the cholmod_common structure has a new member at the
> end:
>
> FILE *blas_dump ; // only used if CHOLMOD is compiled with -DBLAS_DUMP
>
> This is in CHOLMOD/Include/cholmod.h
>
> This extra member changes sizeof(cholmod_common), which changes the ABI,
> causing the crash. One way to fix this is to bump the SONAME of
> libcholmod.
I was indeed suspecting an ABI break in suitesparse, after having
noticed unexpected autopkgtest failures.
Thanks for investigating and finding the cause of the problem, you
saved me a lot of time!
I’ll report this upstream and fix it properly in Debian.
Best wishes,
--
⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁ Debian Developer
⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name
⠈⠳⣄ https://www.debian.org
signature.asc
Description: This is a digitally signed message part
Bug#1061057: clang-16 fails to install as build-dep during cross-build
Package: clang-16 Severity: normal Dear Maintainer, the problem initially was described in # 1060887 but postgres maintainer told me, it's a clang problem. So, here I am. The minimal reproducible example of debian/control follows: Source: cross-deps-problem Build-Depends: debhelper (>= 13.3.4), postgresql-server-dev-16 Section: libs Priority: optional Standards-Version: 4.3.0 So I start with official debian:trixie docker image on amd64 host with the following commands: # dpkg --add-architecture armhf # apt-get update # apt-get dist-upgrade # apt-get -o APT::Get::Build-Dep-Automatic=yes -o Debug::pkgProblemResolver=yes build-dep --host-architecture=armhf -y . which yields: Note, using directory '.' to get the build dependencies Reading package lists... Done Building dependency tree... Done Reading state information... Done Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) clang-16:armhf < none -> 1:16.0.6-19 @un puN Ib > Broken clang-16:armhf Depends on binutils:armhf < none @un pH > Considering binutils:armhf 0 as a solution to clang-16:armhf 0 Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: clang-16:armhf : Depends: binutils:armhf but it is not installable E: Unable to correct problems, you have held broken packages. Manual installation (i.e. apt-get install clang-16:armhf binutils:armhf) succeeds, but it does not help to resolve build-dep issue... Worth to mention, it also happens in bookworm with clang-14 and bullseye with clang-11 (you can find apt diagnostics in #1060887 for that cases too) Please help me diagnose and resolve this issue at least in bookworm Best, Andrey
Bug#964900: I want to own kytos-sphinx-theme
I want to own kytos-sphinx-theme
Bug#1061056: giara: please add support for loong64
Source: giara Version: 1.0.1 Severity: normal X-Debbugs-Cc: wuruil...@loongson.cn Dear Maintainer, Please modify the control file to support loong64 arch. wuruilong -- System Information: Debian Release: trixie/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: loong64 (loongarch64) Kernel: Linux 5.10.0-60.96.0.126.oe2203.loongarch64 (SMP w/32 CPU threads) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect
Bug#1061055: obs-build: init_buildsystem: improper debootstrap implementation violates assumption in Debian policy
Package: obs-build Tags: upstream X-Debbugs-Cc: unit...@debian.org Hi, obs-build has its own implementation of debootstrap in init_buildsystem. Unlike other implementations, it does not ensure that packages from the essential set have been configured before unpacking non-essential packages. The Debian policy requires that essential packages have to work at all times after having been configured at least once. Since non-essential packages may assume presence of essential in their Pre-Depends, essential packages must be configured before unpacking non-essential packages. obs-build's implementation does not ensure this property. We can see this in e.g. https://build.opensuse.org/package/live_build_log/home:unit193/certbot-dns-porkbun/Debian_Testing/x86_64 where essential package bash is installed after non-essential package python3-cffi-backend. The current work on /usr-merge heavily relies on this property. One of the next steps is adding the aliasing symlinks to base-files. If any non-essential package with aliased files is installed before base-files, the aliasing links will be lost and the created chroot will not work at all. I think the property expected here is reasonable and the bug resides with obs-build. In particular, it is a bug that also affects upstream and the upstream deployment at build.opensuse.org. Helmut
Bug#1059546: pylint generates false positive 'import-error' with local editable modules.
control: tags -1 +moreinfo
> To reproduce, I used the following toy module:
> $ find -type f -exec printf '\n%s\n' {} \; -exec cat {} \;
next time, please setup a throw-away repo somewhere like
github.com/gitlab.com, cause it takes too long to setup a reproduce
environment like this.
> With the module not installed, nothing works, as expected:
not really
> $ python t.py
> Traceback (most recent call last):
> File "/home/nexus/t.py", line 3, in
> from ttt import pylintbug
> ModuleNotFoundError: No module named 'ttt'
python has . in its module search path, so this should work (and in
fact it does in my docker container testing env). please check your
installation environment.
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi
Bug#1056989: libaacs: build aacs_info
Control: tags -1 + patch Hey Dylan and people from the multimedia team. I'd have made a PR at: https://salsa.debian.org/multimedia-team/libaacs/-/merge_requests/2 which packages the already built aacs_info in a new libaacs-bin package. Would be nice if this could be reviewed, merged and a new version uploaded anytime soon :-) Thanks, Chris.
Bug#1060896: openafs-modules-dkms: module build fails for Linux 6.7: osi_file.c:178:42: error: 'struct inode' has no member named 'i_mtime'
tags -1 + fixed-upstream patch thanks On Tue, Jan 16, 2024 at 10:30:40AM +0100, Andreas Beckmann wrote: > Package: openafs-modules-dkms > Version: 1.8.10-2 > Severity: important > > Hi, > > openafs-modules-dkms fails to build a module for Linux 6.7 that was just > uploaded to experimental: Thanks for the heads-up; upstream already has the needed patch queued up for the next stable release. -Ben
Bug#1057499: exec-maven-plugin: FTBFS with default Java 21
Dear Maintainers, Would it be possible to consider a merge request[1] that addresses this issue? Alternatively, we can update the package to the upstream version 3.1.1. Best Regards, Vladimir. [1]https://salsa.debian.org/java-team/exec-maven-plugin/-/merge_requests/2
Bug#1061044: [Pkg-nagios-devel] Bug#1061044: nagvis: Website only response with a PHP-Deprecation Error.
On 1/16/24 20:39, Jens Ritter wrote: Upstream provides an update for PHP8.2-Errors (https://www.nagvis.org/downloads/changelog/1.9.36) That's already in testing & unstable, see: https://tracker.debian.org/pkg/nagvis Is there any way possible to include this changes ? I doubt the viability of cherry-picking the php8.2 changes. Backporting nagvis for bookworm should be easier. Someone who actually uses nagvis should do that. Perhaps you? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1060388: sponsor for endless-sky
On 2024-01-17 at 10:22, Bo YU wrote: > Hi, > > First sorry without contacting here before NMU. Welcome! > I am looking for a sponsor for my package "endless-sky": I'm not a DD, but I gave this a look and have a couple comments. > * Vcs : https://salsa.debian.org/games-team/endless-sky Do you have an account on Salsa? You could fork the repository and submit an MR so that the changes are ready to merge and upload. If not, that's OK; I think the changes are small enough for one of us to just commit in one shot. > endless-sky (0.10.4-0.1) UNRELEASED; urgency=medium > . >* Non-maintainer upload. >* New upstream version 0.10.4. (Closes: #1059987) >* rebase debian/patches I see out/troff.patch and out/spelling.patch were applied upstream and removed from debian/patches/series, but the patch files are still under debian/patches/. They should be removed. >* Change Build-Depends on 'cmake' to'cmake (>= 3.21)'. > (Closes: #1054624). (Coincidentally, seeing this bug on Friday reminded me to do a similar cmake B-D version bump in another package.) Other than the suggestions of Git and removing patch files, this looks OK to me for an NMU. But of course it needs a DD's review (ideally Damyan). Since the changes are apparently not in Git, here's the diff I reviewed: changelog | 10 ++ control |2 +- patches/atomics.patch | 29 ++--- patches/series|2 -- 4 files changed, 29 insertions(+), 14 deletions(-) --- diff -Naur endless-sky-0.10.2/debian/changelog endless-sky-0.10.4/debian/changelog --- endless-sky-0.10.2/debian/changelog 2023-10-10 10:57:15.0 -0400 +++ endless-sky-0.10.4/debian/changelog 2024-01-07 20:42:17.0 -0500 @@ -1,3 +1,13 @@ +endless-sky (0.10.4-0.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * New upstream version 0.10.4. (Closes: #1059987) + * rebase debian/patches + * Change Build-Depends on 'cmake' to'cmake (>= 3.21)'. +(Closes: #1054624). + + -- Bo YU Mon, 08 Jan 2024 09:42:17 +0800 + endless-sky (0.10.2-6) unstable; urgency=medium [ Adrian Bunk ] diff -Naur endless-sky-0.10.2/debian/control endless-sky-0.10.4/debian/control --- endless-sky-0.10.2/debian/control 2023-10-06 09:23:26.0 -0400 +++ endless-sky-0.10.4/debian/control 2024-01-07 20:42:17.0 -0500 @@ -8,7 +8,7 @@ Vcs-Git: https://salsa.debian.org/games-team/endless-sky.git Homepage: https://endless-sky.github.io Build-Depends: - cmake, + cmake (>= 3.21), debhelper-compat (= 13), g++ (>=4.6), libgl-dev, diff -Naur endless-sky-0.10.2/debian/patches/atomics.patch endless-sky-0.10.4/debian/patches/atomics.patch --- endless-sky-0.10.2/debian/patches/atomics.patch 2023-10-05 06:08:09.0 -0400 +++ endless-sky-0.10.4/debian/patches/atomics.patch 2024-01-07 20:42:17.0 -0500 @@ -1,17 +1,24 @@ -Description: link with libatomic - On armel and mipsel, there are a bunch of missing __atomic_load_8 symbols - during linking - . - These are provided by libatomic and that is even in the build-dependencies, - but is missing on the linker command line. - . - The right spot to add it is a bit tricky, appending it to SConstrict near - 'pthread' doesn't seem to have any effect, but adding to CMakeLists.txt works. -Author: Damyan Ivanov +From: Damyan Ivanov +Date: Mon, 8 Jan 2024 07:21:47 +0800 +Subject: link with libatomic +On armel and mipsel, there are a bunch of missing __atomic_load_8 symbols +during linking + +These are provided by libatomic and that is even in the build-dependencies, +but is missing on the linker command line. + +The right spot to add it is a bit tricky, appending it to SConstrict near +'pthread' doesn't seem to have any effect, but adding to CMakeLists.txt works. +--- + CMakeLists.txt | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/CMakeLists.txt b/CMakeLists.txt +index fa0903a..d7807e9 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt -@@ -123,7 +123,7 @@ target_link_libraries(ExternalLibraries +@@ -125,7 +125,7 @@ target_link_libraries(ExternalLibraries INTERFACE SDL2::SDL2 PNG::PNG JPEG::JPEG if(WIN32) target_link_libraries(ExternalLibraries INTERFACE rpcrt4 Winmm) else() diff -Naur endless-sky-0.10.2/debian/patches/series endless-sky-0.10.4/debian/patches/series --- endless-sky-0.10.2/debian/patches/series2023-10-05 02:53:48.0 -0400 +++ endless-sky-0.10.4/debian/patches/series2024-01-07 20:42:17.0 -0500 @@ -1,3 +1 @@ -out/troff.patch -out/spelling.patch atomics.patch -- Patrick "P. J." McDermott: http://www.pehjota.net/ Lead Developer, ProteanOS: http://www.proteanos.com/ Founder and CEO, Libiquity: http://www.libiquity.com/
Bug#1061054: srst2: please add support for loong64
Source: srst2 Version: 0.2.0 Severity: normal X-Debbugs-Cc: wuruil...@loongson.cn Dear Maintainer, Please modify the file to support the loong64 architecture, the content is as follows: debian/tests/control:5:Architecture: amd64 arm64 loong64 mips64el ppc64el riscv64 sh4 wuruilong -- System Information: Debian Release: trixie/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: loong64 (loongarch64) Kernel: Linux 5.10.0-60.96.0.126.oe2203.loongarch64 (SMP w/32 CPU threads) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect
Bug#1061053: httrack: Formatting error on man page
Source: httrack Version: 3.49.4 Severity: minor Tags: patch The text "IMPORTANT NOTE: DANGEROUS OPTION, ONLY SUITABLE FOR EXPERTS USE IT WITH EXTREME CARE" which appears after the '%!' option is formatted as if both lines were further options The attached small patch fixes this. I'm no groff expert so it could possibly be done better, but this certainly fixes the issue so the formatting comes out more or less correct. Wookey -- http://wookware.org/ --- httrack.1.orig 2023-01-14 16:32:49.0 + +++ httrack.1 2024-01-17 03:08:36.724857714 + @@ -456,10 +456,8 @@ .SS Dangerous options: (do NOT use unless you exactly know what you are doing) .IP \-%! bypass built\-in security limits aimed to avoid bandwidth abuses (bandwidth, simultaneous connections) (\-\-disable\-security\-limits) -.IP \-IMPORTANT -NOTE: DANGEROUS OPTION, ONLY SUITABLE FOR EXPERTS -.IP \-USE -IT WITH EXTREME CARE + IMPORTANT NOTE: DANGEROUS OPTION, ONLY SUITABLE FOR EXPERTS + USE IT WITH EXTREME CARE .SS Command\-line specific options: .IP \-V
Bug#1059829: Thank you
On 1/16/24 20:36, Georges Khaznadar wrote: Hello, Javascript/Npm are not my cup of tea; so, please receive many thanks about the help you provided to my poor packaging efforts. If node-html5-qrcode happens to be dfsg-free, which should be the right umbrella to host it on salsa.d.o? https://salsa.debian.org/js-team or https://salsa.debian.org/georgesk ? Hi, yes I already push it on js-team/node-html5-qrcode. It is fixed now in it and ready to be pushed. Do you want I push it ? I saw that you managed to let salsa's automaton pass 53 of the upstream tests, and I would like to learn such magics. Please have you some useful links about them? Most of JS Team packages uses dh-sequence-nodejs. To start with it: https://wiki.debian.org/Javascript/Tutorial and then pkg-js-tools(7) However, the changes I did here need a minimum knowledge of npm because the package doesn't follow exactly the common way (see dh_auto_install hook) Best regards, Georges. Cheers, Yadd
Bug#237925: ITP: cdemu -- CD drive emulator for Linux
Hi, apologies, but I've transitioned to another task, and the estimated time for CDEmu is approximately 6 months. So whoever completes their task first can take care of the CDEmu maintenance. On Tue, Jan 16, 2024 at 12:49 AM Matteo Bini wrote: > > Control: owner 237925 Matteo Bini > > Hi Christoph, hi Robert. > > I'm still going to package CDEmu, but I don't know exactly when. There > are a few things I need to better understand before I can do it, for > instance if it's fine to make as many DEB packages as the source > tarballs CDEmu is divided in. Moreover right now I'm a bit busy. > > CDEmu is on my to do list. However if Robert has time to spare and would > like to take care of it, he's most welcome. > > My current ETA is about four months from now. > > Thank you for your interest. > > -- > Matteo Bini
Bug#995670: ITP: zig -- General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software
Hi Nick, Are you still working on the zig package? I'd be happy to help you fix any problems that remain. Kind regards, Maytham signature.asc Description: This is a digitally signed message part
Bug#1001643: Bug#1060913: Re: Bug#1060913: RFS: sdaps/1.9.11-0.1 [NMU] [RC] -- scripts for data acquisition with paper-based surveys
Hi! On Tue, Jan 16, 2024 at 10:39 PM Dominik George wrote: > > Hi, > > > Here I am not a member of DebianEdu team and told if am not a member > > of one team there is no reason to do team upload. > > Ideally, I should contact the team to join in or tell team I am going > > to fix ftbfs issue. > > Whether the maintainer is a team doesn't matter here (it just means I am > not responsible alone for the lack of updates on the package, haha ;)). Ah, I just realized you are the maintainer of the package(as uploader), many thanks for your work. > > In general, you always contact the maintainer for every upload before > doing an NMU, through the address from the package meta-data or by > sending your changes to the BTS into the bug you are fixing. Thanks for reminding me about this. Before submitting an NMU I basically will give it at a glance from debian tracker to look at the care/upload frequency of this package is used to determine if the NMU. Because for some packages that lack care, there are bugs filed in time, but they may not be resolved for a long time. But this is only from my experience. I should obey Debian NMU guidance here. > > > But I got no response from there(not DebianEdu > > team) in the past. > > Can you point me to message IDs where you requested changes to be > uploaded? Sorry, here I mean I asked for some help on IRC. The package is here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060388 I will ping the maintainer of the package again and will fix some issue like `UNRELEASE` here. > > Ideally, you should just send the changes to the BTS bug you are fixing, > and tag it "patch". OKay, no problem. Sometimes the debdiff for new upstream release is very huge and BTS will drop this.:( Many Thanks again, TIL. BR, Bo > > -nik
Bug#1061052: libjogl2-java: please add support for loong64
Source: libjogl2-java Version: please add support for loong64 Severity: normal X-Debbugs-Cc: wuruil...@loongson.cn Dear Maintainer, Please refer to the attached patch to support the loong64 arch. wuruilong -- System Information: Debian Release: trixie/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: loong64 (loongarch64) Kernel: Linux 5.10.0-60.96.0.126.oe2203.loongarch64 (SMP w/32 CPU threads) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect Description: TODO: Put a short summary on the line above and replace this paragraph with a longer explanation of this change. Complete the meta-information with other relevant fields (see below for details). To make it easier, the information below has been extracted from the changelog. Adjust it or drop it. . libjogl2-java (2.5.0+dfsg-1) unstable; urgency=medium . * New upstream version 2.5.0+dfsg * Refreshing patches * Fixing the clean target (Closes: #1046349) * Refreshing d/copyright * Raising minimal gluegen2 version in the (Build-)Depends Author: Pierre Gruet Bug-Debian: https://bugs.debian.org/1046349 --- The information above should follow the Patch Tagging Guidelines, please checkout https://dep.debian.net/deps/dep3/ to learn about the format. Here are templates for supplementary fields that you might want to add: Origin: (upstream|backport|vendor|other), (|commit:) Bug: Bug-Debian: https://bugs.debian.org/ Bug-Ubuntu: https://launchpad.net/bugs/ Forwarded: (no|not-needed|) Applied-Upstream: , (|commit:) Reviewed-By: Last-Update: 2024-01-17 --- libjogl2-java-2.5.0+dfsg.orig/make/build-jogl.xml +++ libjogl2-java-2.5.0+dfsg/make/build-jogl.xml @@ -1451,6 +1451,12 @@ + + + + + + @@ -1506,7 +1512,7 @@ - + --- libjogl2-java-2.5.0+dfsg.orig/make/build-nativewindow.xml +++ libjogl2-java-2.5.0+dfsg/make/build-nativewindow.xml @@ -730,6 +730,13 @@ + + + + + + + @@ -791,7 +798,7 @@ - + --- libjogl2-java-2.5.0+dfsg.orig/make/build-newt.xml +++ libjogl2-java-2.5.0+dfsg/make/build-newt.xml @@ -777,6 +777,16 @@ + + + + + + + + + @@ -874,7 +884,7 @@ - +
Bug#1061051: RFS: notes-tree/1.2-1 -- a note taking app, which organizes notes in a hierarchical structure
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "notes-tree": * Package name : notes-tree Version : 1.2-1 Upstream contact : Dmitry Sviridov <1000hz.radiow...@gmail.com> * URL : https://gitlab.com/44100Hz/NotesTree/-/tree/dev * License : Zlib * Vcs : g...@gitlab.com:44100Hz/NotesTree.git Section : editors The source builds the following binary packages: notes-tree - a note taking app, which organizes notes in a hierarchical (tree like) structure. To access further information about this package, please visit the following URL: https://gitlab.com/44100Hz/NotesTree/-/tree/dev Alternatively, you can download the package with 'dget' using this command: dget -x https://gitlab.com/44100Hz/NotesTree/-/raw/deb-package/deb-pkg/notes-tree_1.2-1.dsc Regards,
Bug#1060840: ITP: golang-k8s-sigs-release-utils -- utilities for kubernetes Go release engineering (library)
I managed to get this package to build, and I belive it actually is required. Rekor is using it for "rekor-cli version": root@vello:~# rekor-cli version _ _ __ ___ _ ___ | _ \ | | | |/ / / _ \ | _ \ / ___| | | |_ _| | |_) | | _| | ' / | | | | | |_) | _ | | | | | | | _ < | |___ | . \ | |_| | | _ < |_| | |___ | |___ | | |_| \_\ |_| |_|\_\ \___/ |_| \_\ \| |_| |___| rekor-cli: Rekor CLI GitVersion:v1.1.0 GitCommit: 4a6592612dc015f24d0700b6d274b3663d128ad8 GitTreeState: clean BuildDate: 2023-03-28T22:13:50Z GoVersion: go1.20.1 Compiler: gc Platform: linux/ppc64le root@vello:~# This comes via sigs.k8s.io/release-utils/version that uses github.com/common-nighthawk/go-figure for the ASCII art output. Of course, we would have to be careful about setting the proper version fields to not cause reproducible build problems, but I believe that is possible using -ldflags=-X=sigs.k8s.io... parameters, compare: https://git.alpinelinux.org/aports/tree/community/rekor/APKBUILD https://github.com/sigstore/rekor/blob/9df89979ba08e76a3f86c0b7406a1ba90710ade6/Makefile#L58 /Simon signature.asc Description: PGP signature
Bug#1061050: ITP: golang-github-common-nighthawk-go-figure -- Prints ASCII art from text
Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-github-common-nighthawk-go-figure Version : 0.0~git20210622.734e95f-1 Upstream Author : Daniel Deutsch * URL : https://github.com/common-nighthawk/go-figure * License : Expat Programming Lang: Go Description : Prints ASCII art from text Go Figure prints beautiful ASCII art from text. It supports FIGlet (http://www.figlet.org/) files, and most of its features. . This package was inspired by the Ruby gem artii (https://github.com/miketierney/artii), but built from scratch and with a different feature set. I hope to maintain this package as part of Debian Go Packaging Team: https://salsa.debian.org/go-team/packages/golang-github-common-nighthawk-go-figure /Simon signature.asc Description: PGP signature
Bug#1061004: guestfs-tools: FTBFS: make[6]: *** [Makefile:1723: test-suite.log] Error 1
control: fixed -1 1.52.0-2
Bug#1059411: nano: install files into /usr/bin
Hi Jordi, please find the same patch here on salsa: https://salsa.debian.org/debian/nano/-/merge_requests/2 Note that nano is part of the bootstrap set, so it has to be converted sooner than later (before base-files can be changed). Chris
Bug#1060708: python3-wxgtk4.0: Package doesn't import
On Sat, 13 Jan 2024, Matthias Urlichs wrote: Package: python3-wxgtk4.0 Version: 4.2.0+dfsg-3 Severity: important X-Debbugs-Cc: sm...@smurf.noris.de /usr/lib/python3/dist-packages/wx/__init__.py contains: from wx.core import * del core del wx This doesn't work on my system. "wx.core" does *not* export a symbol named "core", thus the "del core" fails. Deleting the "del core" part fixes the problem. -- System Information: Debian Release: 12.4 APT prefers stable APT policy: (750, 'stable'), (700, 'testing'), (650, 'oldstable'), (600, 'oldoldstable'), (500, 'stable-security'), (500, 'oldstable-security'), (500, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 6.1.0-10-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-wxgtk4.0 depends on: ii libc62.36-9+deb12u3 ii libgcc-s112.2.0-14 ii libstdc++6 13.2.0-9 ii libwxbase3.2-1 3.2.4+dfsg-1 ii libwxgtk-gl3.2-1 3.2.4+dfsg-1 ii libwxgtk3.2-13.2.2+dfsg-2 ii python3 [python3-supported-min] 3.11.2-1+b1 ii python3-numpy1:1.24.2-1 ii python3-pil 9.4.0-1.1+b1 ii python3-six 1.16.0-4 Can you provide any additional details that may be relevant to reproducing this problem? I'm going to assume this is probably related to your other bug where you seem to be mixing and matching packages from testing and bookworm? Scott
Bug#1061049: libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in libcholmod5 without bumping to "libcholmod6"
Package: libsuitesparse-dev
Version: 1:7.3.1+dfsg-2
Severity: serious
X-Debbugs-Cc: none, Dima Kogan
Hi. I'm chasing down
http://bugs.debian.org/1060986
The problem is that mrcal uses libdogleg, which contains
typedef struct
{
cholmod_common common;
} dogleg_solverContext_t;
The existing "libdogleg2" package was built against libsuitesparse-dev
7.3, so it must be linked with packages that use that ABI. But in
suitesparse 7.4 the cholmod_common structure has a new member at the
end:
FILE *blas_dump ; // only used if CHOLMOD is compiled with -DBLAS_DUMP
This is in CHOLMOD/Include/cholmod.h
This extra member changes sizeof(cholmod_common), which changes the ABI,
causing the crash. One way to fix this is to bump the SONAME of
libcholmod.
Thanks.
Bug#1060711: python3-wxgtk4.0: Library dependency too lenient
On Sat, 13 Jan 2024, Matthias Urlichs wrote: Package: python3-wxgtk4.0 Version: 4.2.1+dfsg-3 Severity: normal X-Debbugs-Cc: sm...@smurf.noris.de Installing the version from Testing says import wx.core Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/wx/__init__.py", line 17, in from wx.core import * File "/usr/lib/python3/dist-packages/wx/core.py", line 12, in from ._core import * ImportError: /usr/lib/python3/dist-packages/wx/_core.cpython-311-x86_64-linux-gnu.so: undefined symbol: _ZN13wxRadioButtonD2Ev, version WXU_3.2 due to its dependency on libwxgtk3.2-1, which apparently needs to be >= 3.2.4 instead of 3.2.2. Semantic versioning appears to be overrated. :-( Hello Matthias, Do I understand correctly that you installed the python3-wxgtk4.0 4.2.1+dfsg-3 binary package from Debian Testing into a Debian 12 system and that's how you encountered this error? Scott
Bug#1056764: grub-efi-amd64: can't boot with GRUB 2.12~rc1-12
Hello Mate, Thanks for letting us know. I just tried with 2.12~rc1-13 and no luck. I'll wait for 2.12 and let you know if it fixes my issue. Thanks, -- Nicolas Haller On Mon, 15 Jan 2024 07:51:22 + Mate Kukri wrote: Hello, Just letting you know that the 2.12 merge is in progress, and GRUB 2.12 (non-rc1) will be available in Debian the (hopefully) not too distant future. Mate On Fri, Jan 12, 2024 at 9:18 PM wrote: > > Good day, > > does grub 2.12 (without rc1) help? There are a good pile of fixups > between rc1 and release. E.g. > https://git.savannah.gnu.org/cgit/grub.git/commit/?h=grub-2.12=1f5b180742ff2706bc3a696d115ddbc677ec75b9 > or > https://git.savannah.gnu.org/cgit/grub.git/commit/?h=grub-2.12=67ae3981dc5113e5af3a0539174bcd7eab8f7722 > could help. > > Additionally, the ZFS fixes are needed to boot from volumes touched by > ZFS 2.2 ( https://github.com/openzfs/zfs/issues/13873 ), so migrating to > 2.12 is helpful in either case. > > Best regards, > Michael Fritscher > > On Sat, 25 Nov 2023 17:36:41 -0500 Nicolas Haller > wrote: > > Package: grub-efi-amd64 > > Version: 2.06-13 > > Severity: critical > > Justification: breaks the whole system > > > > Dear Maintainer, > > > > My old laptop (Lenovo 11e) runs Sid and all was right before I updated > > it the other day (I don't do that very often). After that upgrade, GRUB > > wasn't able to load any kernel with the pretty much generic error > > "Error: can't load image". The version of GRUB was 2.12~rc1-12. > > If I try to boot again, GRUB tells me that I need to load the image > > first (I guess it somehow ignores the linux command and sends that when > > trying to load the initrd). > > > > I tried to reinstall grub, grub-install /dev/sda, update-grub, reinstall > > the kernel, update-initramfs from the rescue mode but nothing worked. > > The "file" command was able to read the vmlinuz file and none seemed > > truncated. The system has one partition with both / and /boot and isn't > > running out of space. > > I did not see any error message during those operation besides GRUB > > saying it wasn't able to update EFI parameters. > > > > I don't know if there is a way to get more logs or error message during > > the boot explaining why it wasn't able to load the image. > > > > I tried to get the last version of GRUB from Bookworm, that is > > 2.06-13, and now I'm able to boot. The kernel version did not change, > > the only change I did is to downgrade GRUB (and dependencies apt was > > asking for). > > > > I'm not sure which GRUB package I should use for reporting so I took the
Bug#1057843:
moutaz
Bug#1061048: RFS: RPGMod/1.3 ITP -- heyo!
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "RPGMod": * Package name : RPGMod Version : 1.3.0 Upstream contact : admi...@peq42.com * URL : http://peq42.com * License : MIT * Vcs : https://peq42.com/downloads/RPGmod%20-%20Linux.deb To access further information about this package, please visit the following URL: https://peq42.com/projects/rpgmod/ Alternatively, you can download the package with 'dget' using this command: dget -x https://peq42.com/downloads/RPGmod%20-%20Linux.deb Changes since the last upload: -Released .DEB additional comments: I'm sorry if this e-mail is not exactly perfect or if anything is missing, this is my first time packaging and submiting a package to the debian store. I setup the package using my personal e-mail(gabrielpm2...@gmail.com) and real name(Gabriel), but for the sake of lowering spam I get there, if possible, utilize this one(admi...@peq42.com) in the store Regards, Gabriel
Bug#1060994: libshumate: FTBFS: Couldn't find include 'GObject-2.0.gir'
Control: retitle -1 libshumate: FTBFS: Couldn't find include 'GObject-2.0.gir' On Tue, 16 Jan 2024 at 20:43:20 +0100, Lucas Nussbaum wrote: > > Couldn't find include 'GObject-2.0.gir' (search path: > > '['/usr/share/gir-1.0', '/usr/lib/x86_64-linux-gnu/gir-1.0', > > '/<>/debian/.debhelper/generated/_source/home/.local/share/gir-1.0', > > 'gir-1.0', '/usr/local/share/gir-1.0', '/usr/share/gir-1.0', > > '/usr/lib/x86_64-linux-gnu/gir-1.0', '/usr/share/gir-1.0', > > '/usr/share/gir-1.0']') This is collateral damage from me removing an unnecessary dependency in src:graphene, which previously pulled in an unwanted dependency chain that included libgirepository1.0-dev. Historically, packages that processed GIR XML needed to build-depend on libgirepository1.0-dev. As of this week, it's better to build-depend on gobject-introspection and the individual GIR XML packages that are needed, which opens the way for being cross-compilable in future. smcv
Bug#1060950: cage: FTBFS: ../idle_inhibit_v1.c:11:10: fatal error: wlr/types/wlr_idle.h: No such file or directory
Control: reassign 1058495 src:cage Control: forcemerge -1 1058495 signature.asc Description: This is a digitally signed message part.
Bug#1061046: gnutls28: CVE-2024-0553
Source: gnutls28 Version: 3.8.2-1 Severity: important Tags: security upstream Forwarded: https://gitlab.com/gnutls/gnutls/-/issues/1522 X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 3.7.9-2+deb12u1 Control: found -1 3.7.1-5+deb11u4 Hi, The following vulnerability was published for gnutls28. CVE-2024-0553[0]: | A vulnerability was found in GnuTLS. The response times to malformed | ciphertexts in RSA-PSK ClientKeyExchange differ from response times | of ciphertexts with correct PKCS#1 v1.5 padding. This issue may | allow a remote attacker to perform a timing side-channel attack in | the RSA-PSK key exchange, potentially leading to the leakage of | sensitive data. CVE-2024-0553 is designated as an incomplete | resolution for CVE-2023-5981. Note, that the CVE exists because of an incomplete fix for CVE-2023-5981. So strictly speaking the bullseye version is not yet released in stable, and so if we do a complete fix with a followup, then strictly speaking gnutls28 in bullseye won't be affected. OTOH the gnutls28 version with the incomplete fix is already in bullseye-proposed-updates, so guess it's safe to track it as it's done now. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-0553 https://www.cve.org/CVERecord?id=CVE-2024-0553 [1] https://gitlab.com/gnutls/gnutls/-/issues/1522 [2] https://lists.gnupg.org/pipermail/gnutls-help/2024-January/004841.html Regards, Salvatore
Bug#1061045: gnutls28: CVE-2024-0567
Source: gnutls28 Version: 3.8.2-1 Severity: important Tags: security upstream Forwarded: https://gitlab.com/gnutls/gnutls/-/issues/1521 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for gnutls28. CVE-2024-0567[0]: | A vulnerability was found in GnuTLS, where a cockpit (which uses | gnuTLS) rejects a certificate chain with distributed trust. This | issue occurs when validating a certificate chain with cockpit- | certificate-ensure. This flaw allows an unauthenticated, remote | client or attacker to initiate a denial of service attack. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-0567 https://www.cve.org/CVERecord?id=CVE-2024-0567 [1] https://gitlab.com/gnutls/gnutls/-/issues/1521 [2] https://lists.gnupg.org/pipermail/gnutls-help/2024-January/004841.html Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1060990: wacomtablet: FTBFS: make: *** [debian/rules:8: binary] Error 2
This might be https://bugs.debian.org/1060687 Thank you, Jeremy Bícha
Bug#1060950: cage: FTBFS: ../idle_inhibit_v1.c:11:10: fatal error: wlr/types/wlr_idle.h: No such file or directory
Control: forcemerge -1 1058495 On dinsdag 16 januari 2024 20:29:22 CET you wrote: > Source: cage > Version: 0.1.5-1 > Severity: serious > Justification: FTBFS > > During a rebuild of all packages in sid, your package failed to build > on amd64. It's a known problem, see https://bugs.debian.org/1058495 signature.asc Description: This is a digitally signed message part.
Bug#1014616: extrepo update fails with "uninitialized value" error
Version: 0.11
Hi Adam,
Thanks for your report.
The run function in Update.pm has been removed and merged into Enable.pm
since extrepo 0.10, which means that this bug should be resolved now.
However, I forgot to close the bug report at the time.
Doing so now.
Thanks,
--
w@uter.{be,co.za}
wouter@{grep.be,fosdem.org,debian.org}
I will have a Tin-Actinium-Potassium mixture, thanks.
Bug#1058661: [Debian-med-packaging] Bug#1058661: dipy: slow (sometimes timing out) autopkgtest
Étienne Mollier, on 2024-01-12: > Rebecca N. Palmer, on 2023-12-14: > > This autopkgtest, and particularly test_reconstruct_rumba, is slow enough > > that it sometimes times out and fails. I think this is varying hardware > > speed and not a random hang because failure seems to correlate with the > > earlier tests taking longer. > > dipy 1.8.0-1 took more than thirteen hours to build on riscv64 > machine rv-manda-01[1]. Bumping the severity because this looks > a tad bit excessive. In the end, the build time of dipy 1.8.0-2 on rv-manda-03 was still 13h. On the other hand the autopkgtest on amd64 looks to have dropped from timeout at 1s to 3770s run time. This should be enough to even avoid dropping whent two python3 versions will be tested in sequence. Have a nice day, :) -- .''`. Étienne Mollier : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/2, please excuse my verbosity `-on air: One Shot - Off The Grid signature.asc Description: PGP signature
Bug#1057179: mariadb 10.11.6-0+deb12u1 flagged for acceptance
package release.debian.org tags 1057179 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: mariadb Version: 10.11.6-0+deb12u1 Explanation: new upstream stable release; fix denial of service issue [CVE-2023-22084]
Bug#1061021: cinnamon-control-center: FTBFS: Package 'libevdev', required by 'libwacom', not found
Il 16/01/2024 20:29, Lucas Nussbaum ha scritto: CMake binary for host machine is not cached CMake binary missing from cross or native file, or env var undefined. Trying a default CMake fallback at cmake Did not find CMake 'cmake' Found CMake: NO Dependency lookup for libwacom with method 'cmake' failed: CMake binary for machine host machine not found. Giving up. Run-time dependency libwacom found: NO ../meson.build:86:14: ERROR: Dependency lookup for libwacom with method 'pkgconfig' failed: Could not generate cflags for libwacom: Package libevdev was not found in the pkg-config search path. Perhaps you should add the directory containing `libevdev.pc' to the PKG_CONFIG_PATH environment variable Package 'libevdev', required by 'libwacom', not found dh_auto_configure: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dpython.bytecompile=-1 returned exit code 1 make: *** [debian/rules:10: binary] Error 25 Thanks for your work about FTBFS reports. libevdev seems don't required by cinnamon-control-center but by wacom, from a fast look I saw require it but don't have libevdev-dev dep. anyway is already reported by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060687 I don't think is a good thing add libevdev-dev build-dep. in cinnamon-control-center as temporary workaround and should wait fix in libwacom instead, or I'm wrong? OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1060803: gnome-software: Please don't depend on `software-properties-gtk`
Am Di., 16. Jan. 2024 um 20:03 Uhr schrieb Julian : > > > > Fair point. We could maybe make it so g-s-p is only a recommended > > dependency > > That is what this request is requesting. Just a change from depend to > recommend > > > and modify the code so when g-s-p is not available, it > > falls back to the GS dialog. > > I'm not sure what code you're referring to, but when running GNOME > Software on Debian without s-p-gtk installed, the GS dialog is instead > used. Neat, looks like I wrote it properly back then :-) Also appears like the change was reverted upstream a few months ago, I wonder why... (we patch it back in at Debian/Ubuntu anyway) In any case, I have no objections to moving g-s-p to recommends under these circumstances :-) Thanks for reporting this issue! Best, Matthias -- I welcome VSRE emails. See http://vsre.info/
Bug#1060346: live-boot-initramfs-tools: Debian Live ISO not bootable on exfat partition (loopback)
Hi,
I am sending the proposed patch to add the exfat module to initrd:
diff --git a/backend/initramfs-tools/live.hook
b/backend/initramfs-tools/live.hook
index
ff8f4210690e21961dd5e8c3f1d7b3a5b14d4167..7c476ea6159c0664e47497f82145b6da8391
100755
--- a/backend/initramfs-tools/live.hook
+++ b/backend/initramfs-tools/live.hook
@@ -133,6 +133,12 @@ then
manual_add_modules vfat
fi
+# Filesystem: exfat
+if [ "${DISABLE_EXFAT:-}" != "true" ] && [ "${DISABLE_EXFAT:-}" != "yes" ]
+then
+ manual_add_modules exfat
+fi
+
# Filesystem: ntfs
if [ "${DISABLE_NTFS:-}" != "true" ] && [ "${DISABLE_NTFS:-}" != "yes" ]
then
diff --git a/manpages/en/live-boot.7 b/manpages/en/live-boot.7
index
02b355da2f124208a951ffa428874b9148665f55..a0f7292e53c535ac63afee3b78d48cd4b359748d
100644
--- a/manpages/en/live-boot.7
+++ b/manpages/en/live-boot.7
@@ -38,6 +38,10 @@ Disable support for dm-verity. If set to true
\fItrue\fR' mkinitramfs will build
\fBDISABLE_FAT\fR=[\fItrue\fR|\fIfalse\fR]
Disable support for booting from FAT file systems. If set to
'\fItrue\fR' mkinitramfs will build an initramfs without the kernel
module vfat and some nls_* modules.
+.TP
+\fBDISABLE_FAT\fR=[\fItrue\fR|\fIfalse\fR]
+Disable support for booting from FAT file systems. If set to
'\fItrue\fR' mkinitramfs will build an initramfs without the kernel
module exfat.
+
.TP
\fBDISABLE_FUSE\fR=[\fItrue\fR|\fIfalse\fR]
Disable support for booting from FUSE-based file systems. If set to
'\fItrue\fR' mkinitramfs will build an initramfs without the kernel
module fuse and file systems that depend on it (like curlftpfs and
httpfs2).
diff --git a/manpages/po/es/live-boot.7.po b/manpages/po/es/live-boot.7.po
index
28f916cedbe59b89a986f5f1eb72878383bc4219..6838418f2a4990a668679d461197b6f488c590dc
100644
--- a/manpages/po/es/live-boot.7.po
+++ b/manpages/po/es/live-boot.7.po
@@ -194,6 +194,19 @@ msgid ""
"nls_* modules."
msgstr ""
+#. type: TP
+#: en/live-boot.7:41
+#, no-wrap
+msgid "B=[I|I]"
+msgstr ""
+
+#. type: Plain text
+#: en/live-boot.7:44
+msgid ""
+"Disable support for booting from exFAT file systems. If set to 'I' "
+"mkinitramfs will build an initramfs without the kernel module exfat."
+msgstr ""
+
#. type: TP
#: en/live-boot.7:37
#, no-wrap
diff --git a/manpages/po/fr/live-boot.7.po b/manpages/po/fr/live-boot.7.po
index
2f51f42e7ff3c61d434c2038dbd3a9a5c6453dcf..163b437e60240296bcb58dde3e33d78debc9827f
100644
--- a/manpages/po/fr/live-boot.7.po
+++ b/manpages/po/fr/live-boot.7.po
@@ -192,6 +192,19 @@ msgid ""
"nls_* modules."
msgstr ""
+#. type: TP
+#: en/live-boot.7:41
+#, no-wrap
+msgid "B=[I|I]"
+msgstr ""
+
+#. type: Plain text
+#: en/live-boot.7:44
+msgid ""
+"Disable support for booting from exFAT file systems. If set to 'I' "
+"mkinitramfs will build an initramfs without the kernel module exfat."
+msgstr ""
+
#. type: TP
#: en/live-boot.7:37
#, no-wrap
diff --git a/manpages/po/ja/live-boot.7.po b/manpages/po/ja/live-boot.7.po
index
8a3224748f80845c5c45731d15c0b52e6749f59d..9ccf31216a5ad14a648b66a3bcab42abb48bb371
100644
--- a/manpages/po/ja/live-boot.7.po
+++ b/manpages/po/ja/live-boot.7.po
@@ -189,6 +189,19 @@ msgid ""
"nls_* modules."
msgstr ""
+#. type: TP
+#: en/live-boot.7:41
+#, no-wrap
+msgid "B=[I|I]"
+msgstr ""
+
+#. type: Plain text
+#: en/live-boot.7:44
+msgid ""
+"Disable support for booting from exFAT file systems. If set to 'I' "
+"mkinitramfs will build an initramfs without the kernel module exfat."
+msgstr ""
+
#. type: TP
#: en/live-boot.7:37
#, no-wrap
diff --git a/manpages/pot/live-boot.7.pot b/manpages/pot/live-boot.7.pot
index
dee33bb55cf9ad13f53c04edc8d2dc1ed08a2030..5d798b579f89747275a6343123cdda55397e4767
100644
--- a/manpages/pot/live-boot.7.pot
+++ b/manpages/pot/live-boot.7.pot
@@ -165,6 +165,19 @@ msgid ""
"nls_* modules."
msgstr ""
+#. type: TP
+#: en/live-boot.7:41
+#, no-wrap
+msgid "B=[I|I]"
+msgstr ""
+
+#. type: Plain text
+#: en/live-boot.7:44
+msgid ""
+"Disable support for booting from exFAT file systems. If set to 'I' "
+"mkinitramfs will build an initramfs without the kernel module exfat."
+msgstr ""
+
#. type: TP
#: en/live-boot.7:37
#, no-wrap
Bug#1061042: flask-mongoengine: FTBFS: tests failed
Source: flask-mongoengine Version: 1.0.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:305: python3.12 setup.py config > running config > I: pybuild base:305: python3.11 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:305: /usr/bin/python3.12 setup.py build > running build > running build_py > creating > /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine > copying flask_mongoengine/operation_tracker.py -> > /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine > copying flask_mongoengine/__init__.py -> > /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine > copying flask_mongoengine/json.py -> > /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine > copying flask_mongoengine/pagination.py -> > /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine > copying flask_mongoengine/panels.py -> > /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine > copying flask_mongoengine/sessions.py -> > /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine > copying flask_mongoengine/connection.py -> > /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine > creating > /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine/wtf > copying flask_mongoengine/wtf/__init__.py -> > /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine/wtf > copying flask_mongoengine/wtf/models.py -> > /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine/wtf > copying flask_mongoengine/wtf/fields.py -> > /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine/wtf > copying flask_mongoengine/wtf/base.py -> > /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine/wtf > copying flask_mongoengine/wtf/orm.py -> > /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine/wtf > running egg_info > creating flask_mongoengine.egg-info > writing flask_mongoengine.egg-info/PKG-INFO > writing dependency_links to flask_mongoengine.egg-info/dependency_links.txt > writing requirements to flask_mongoengine.egg-info/requires.txt > writing top-level names to flask_mongoengine.egg-info/top_level.txt > writing manifest file 'flask_mongoengine.egg-info/SOURCES.txt' > reading manifest file 'flask_mongoengine.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no previously-included files matching '*.pyc' found under directory > 'docs' > warning: no previously-included files matching '*.pyo' found under directory > 'docs' > no previously-included directories found matching 'docs/_build' > no previously-included directories found matching 'docs/_themes/.git' > adding license file 'LICENSE' > adding license file 'AUTHORS' > writing manifest file 'flask_mongoengine.egg-info/SOURCES.txt' > /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: > Package 'flask_mongoengine.templates.panels' is absent from the `packages` > configuration. > !! > > > > > # Package would be ignored # > > Python recognizes 'flask_mongoengine.templates.panels' as an > importable package[^1], > but it is absent from setuptools' `packages` configuration. > > This leads to an ambiguous overall configuration. If you want to > distribute this > package, please make sure that 'flask_mongoengine.templates.panels' > is explicitly added > to the `packages` configuration field. > > Alternatively, you can also rely on setuptools' discovery methods > (for example by using `find_namespace_packages(...)`/`find_namespace:` > instead of `find_packages(...)`/`find:`). > > You can read more about "package discovery" on setuptools > documentation page: > > - > https://setuptools.pypa.io/en/latest/userguide/package_discovery.html > > If you don't want 'flask_mongoengine.templates.panels' to be > distributed and are > already explicitly excluding 'flask_mongoengine.templates.panels' via > `find_namespace_packages(...)/find_namespace` or > `find_packages(...)/find`, > you can try to use `exclude_package_data`, or > `include-package-data=False` in > combination with a more fine grained `package-data` configuration. > > You can read more about "package data files" on setuptools
Bug#1061044: nagvis: Website only response with a PHP-Deprecation Error.
Package: nagvis
Version: 1:1.9.34-1
Severity: normal
Dear Maintainer,
the provided nagvis-package does not work out-of-the-box. It only
provides this Error-Message in the Browser:
Error: (0) Creation of dynamic property GlobalMainCfg::$PUCACHE is deprecated
URL: /nagvis/frontend/nagvis-js/index.php?mod=Map=view=demo-muc-srv1
File: /usr/share/nagvis/share/server/core/classes/GlobalMainCfg.php
Line: 1547
#0 /usr/share/nagvis/share/server/core/classes/GlobalMainCfg.php(1547):
nagvisExceptionErrorHandler()
#1 /usr/share/nagvis/share/server/core/functions/core.php(36):
GlobalMainCfg->init()
#2 /usr/share/nagvis/share/frontend/nagvis-js/index.php(41): require('...')
#3 {main}
Upstream provides an update for PHP8.2-Errors
(https://www.nagvis.org/downloads/changelog/1.9.36)
Is there any way possible to include this changes ?
-- System Information:
Debian Release: 12.4
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-15-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages nagvis depends on:
ii debconf [debconf-2.0] 1.5.82
ii graphviz 2.42.2-7+b3
ii php 2:8.2+93
ii php-common2:93
ii php-gd2:8.2+93
ii php-net-socket1.2.2-2
ii php-sqlite3 2:8.2+93
ii php8.2 [php] 8.2.7-1~deb12u1
ii php8.2-gd [php-gd]8.2.7-1~deb12u1
ii php8.2-sqlite3 [php-sqlite3] 8.2.7-1~deb12u1
ii ucf 3.0043+nmu1
nagvis recommends no packages.
Versions of packages nagvis suggests:
pn check-mk-livestatus
pn nagvis-demos
-- debconf information:
nagvis/monitoring_system: icinga
nagvis/delete_on_purge: false
Bug#1061041: syncthingtray: FTBFS: make[5]: *** [connector/CMakeFiles/check.dir/build.make:73: connector/CMakeFiles/check] Error 8
Source: syncthingtray Version: 1.3.2-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[5]: Entering directory '/<>/debian/build' > /usr/bin/ctest -V > UpdateCTestConfiguration from > :/<>/debian/build/DartConfiguration.tcl > UpdateCTestConfiguration from > :/<>/debian/build/DartConfiguration.tcl > Test project /<>/debian/build > Constructing a list of tests > Done constructing a list of tests > Updating test list for fixtures > Added 0 tests to meet fixture requirements > Checking test dependency graph... > Checking test dependency graph end > test 1 > Start 1: syncthingconnector_run_tests > > 1: Test command: > /<>/debian/build/connector/syncthingconnector_tests "-p" > "/<>/connector/testfiles" "-w" > "/<>/debian/build/connector/testworkingdir" > 1: Working Directory: /<>/debian/build/connector > 1: Test timeout computed to be: 1000 > 1: /<>/connector/testfiles/ > 1: /<>/connector/testfiles/ > 1: ./testfiles/ > 1: Directory used to store working copies: > 1: /<>/debian/build/connector/testworkingdir/ > 1: [1mExecuting test cases ...[0m > 1: . > 1: - Setup configuration for Syncthing tests ... > 1: - No timeout factor set, defaulting to 1 > 1:(set environment variable SYNCTHING_TEST_TIMEOUT_FACTOR to specify a > factor to run tests on a slow machine) > 1: > 1: - Launching Syncthing: syncthing -gui-address=http://127.0.0.1:4001 > -gui-apikey=syncthingtestinstance > -home=/<>/debian/build/connector/testworkingdir/testconfig > -no-browser -verbose > 1: [1;34mInfo: [0m[1mLaunched process, PID: 1655520[0m > 1: > 1: - Preparing connection ... > 1: > 1: - Error handling in case of insufficient configuration ... > 1: - Connection error: Connection configuration is insufficient. > 1: - Connection status changed to: disconnected > 1: > 1: - Error handling in case of inavailability ... > 1: - Connection error: Unable to request Syncthing config: Connection refused > 1: - Connection error: Unable to request Syncthing status: Connection refused > 1: [start] 2024/01/15 20:12:46 INFO: syncthing v1.27.2-ds4 "Gold Grasshopper" > (go1.21.5 linux-amd64) debian@debian 2024-01-06 14:38:16 UTC > 1: [start] 2024/01/15 20:12:46 INFO: Generating ECDSA key and certificate for > syncthing... > 1: [start] 2024/01/15 20:12:46 INFO: Archiving a copy of old config file > format at: > /<>/debian/build/connector/testworkingdir/testconfig/config.xml.v28 > 1: [GUZKE] 2024/01/15 20:12:46 INFO: My ID: > GUZKEQZ-NUIVT6O-EAK4SLK-PICXPBH-NRMSN67-NO2HK4C-KKZSBJF-DRNQKAX > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection error: Unable to request Syncthing config: Connection refused > 1: - Connection error: Unable to request Syncthing status: Connection refused > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection error: Unable to request Syncthing config: Connection refused > 1: - Connection error: Unable to request Syncthing status: Connection refused > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection error: Unable to request Syncthing config: Connection refused > 1: - Connection error: Unable to request Syncthing status: Connection refused > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection error: Unable to request Syncthing config: Connection refused > 1: - Connection error: Unable to request Syncthing status: Connection refused > 1: [GUZKE] 2024/01/15 20:12:47 INFO: Single thread SHA256 performance is 347 > MB/s using minio/sha256-simd (344 MB/s using crypto/sha256). > 1: [GUZKE] 2024/01/15 20:12:47 VERBOSE: Starting up > (/<>/debian/build/connector/testworkingdir/testconfig) > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection error: Unable to request Syncthing config: Connection refused > 1: - Connection error: Unable to request Syncthing status: Connection refused > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection status changed to: disconnected > 1: - Connection status changed to:
Bug#1060886: swupdate: Additional dependency support may need to be added
Control: block -1 by 1060884 Am 16.01.24 um 05:04 schrieb zhangdandan: The swupdate source package (pull from sid) was compiled successfully on my local loong64 rootfs environment. But refer to other architectures, maybe we need to add additional dependency support in d/control and d/rules. I would like to remind you there is no package for loong64 yet about the additional dependency. I reported this phenomenon (whether additional dependency support is needed?) in advance and hope to get suggestions from the maintainers. The efibootguard support is optional. As long as that is not available on loong64, it is not a good idea to apply your patch. For now, we are waiting for the experimental nodejs to become available in unstable.
Bug#1061037: gnome-settings-daemon: FTBFS: Package 'libevdev', required by 'libwacom', not found
Source: gnome-settings-daemon Version: 45.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- \ > --libdir=/usr/lib \ > -Dgcr3=true \ > > cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 > meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr > --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu > -Dpython.bytecompile=-1 --libdir=/usr/lib -Dgcr3=true > The Meson build system > Version: 1.3.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: gnome-settings-daemon > Project version: 45.1 > C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-9) 13.2.0") > C linker for the host machine: cc ld.bfd 2.41.50.20231227 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1 > Run-time dependency glib-2.0 found: YES 2.78.3 > Run-time dependency geocode-glib-2.0 found: YES 3.26.3 > Run-time dependency gio-2.0 found: YES 2.78.3 > Run-time dependency gio-unix-2.0 found: YES 2.78.3 > Run-time dependency gnome-desktop-3.0 found: YES 44.0 > Run-time dependency gsettings-desktop-schemas found: YES 45.0 > Run-time dependency gtk+-3.0 found: YES 3.24.39 > Run-time dependency gtk+-x11-3.0 found: YES 3.24.39 > Run-time dependency gweather4 found: YES 4.4.0 > Run-time dependency libcanberra-gtk3 found: YES 0.30 > Run-time dependency libgeoclue-2.0 found: YES 2.7.1 > Run-time dependency libnotify found: YES 0.8.3 > Run-time dependency libpulse-mainloop-glib found: YES 16.1 > Run-time dependency pango found: YES 1.51.0 > Run-time dependency polkit-gobject-1 found: YES 123 > Run-time dependency upower-glib found: YES 1.90.2 > Run-time dependency x11 found: YES 1.8.7 > Run-time dependency xfixes found: YES 6.0.0 > Run-time dependency systemd found: YES 255 > ../meson.build:118: WARNING: Project targets '>= 0.57.0' but uses feature > deprecated since '0.56.0': dependency.get_pkgconfig_variable. use > dependency.get_variable(pkgconfig : ...) instead > Library m found: YES > > Executing subproject gvc > > gvc| Project name: gvc > gvc| Project version: undefined > gvc| C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-9) > 13.2.0") > gvc| C linker for the host machine: cc ld.bfd 2.41.50.20231227 > gvc| Dependency glib-2.0 found: YES 2.78.3 (cached) > gvc| Program /usr/bin/glib-mkenums found: YES (/usr/bin/glib-mkenums) > gvc| Dependency glib-2.0 found: YES 2.78.3 (cached) > gvc| Program /usr/bin/glib-mkenums found: YES (/usr/bin/glib-mkenums) > gvc| Dependency gio-2.0 found: YES 2.78.3 (cached) > gvc| Run-time dependency gobject-2.0 found: YES 2.78.3 > gvc| Run-time dependency libpulse found: YES 16.1 > gvc| Dependency libpulse-mainloop-glib found: YES 16.1 (cached) > gvc| Run-time dependency alsa found: YES 1.2.10 > gvc| Configuring config.h using configuration > gvc| Build targets in project: 4 > gvc| Subproject gvc finished. > > Run-time dependency gudev-1.0 found: YES 238 > Checking for function "timerfd_create" : YES > Run-time dependency wayland-client found: YES 1.22.0 > Run-time dependency gdk-wayland-3.0 found: YES 3.24.39 > Did not find CMake 'cmake' > Found CMake: NO > Run-time dependency libwacom found: NO > > ../meson.build:163:17: ERROR: Dependency lookup for libwacom with method > 'pkgconfig' failed: Could not generate cflags for libwacom: > Package libevdev was not found in the pkg-config search path. > Perhaps you should add the directory containing `libevdev.pc' > to the PKG_CONFIG_PATH environment variable > Package 'libevdev', required by 'libwacom', not found > > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2024-01-15T20:21:32.69 > Main binary: /usr/bin/python3 > Build Options: -Dpython.bytecompile=-1 -Dgcr3=true -Dprefix=/usr > -Dlibdir=/usr/lib -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain > -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 1.3.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: gnome-settings-daemon > Project version: 45.1 > --- > Detecting compiler via: `cc --version` -> 0 > stdout: > cc (Debian 13.2.0-9) 13.2.0 > Copyright (C) 2023 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > --- > Running command: cc -E -dM - > - > --- > Detecting linker via: `cc -Wl,--version -Wl,-z,relro -Wl,-z,now
Bug#1061040: apertium-eu-en: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
Source: apertium-eu-en Version: 0.3.3-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > apertium-regtest test > Corpus 1 of 1: eu-en-pending > 1/59 (1.69%) tests pass (0/1 (0.0%) match gold) > > There were changes! Rerun in interactive mode to update tests. > Changed corpora: eu-en-pending > make[1]: *** [Makefile:788: test] Error 1 > make[1]: Leaving directory '/<>' > dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 > returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2024/01/15/apertium-eu-en_0.3.3-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1061038: apertium-en-gl: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
Source: apertium-en-gl Version: 0.5.4-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > apertium-regtest test > Corpus 1 of 1: en-gl-regression > 0/1 (0.0%) tests pass > > There were changes! Rerun in interactive mode to update tests. > Changed corpora: en-gl-regression > make[1]: *** [Makefile:806: test] Error 1 > make[1]: Leaving directory '/<>' > dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 > returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2024/01/15/apertium-en-gl_0.5.4-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1061035: libconfig-model-dpkg-perl: FTBFS: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit code 255
Source: libconfig-model-dpkg-perl Version: 3.002 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > /usr/bin/perl Build.PL --installdirs vendor --config "optimize=-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2" --config "ld=x86_64-linux-gnu-gcc -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wl,-z,relro" > Can't find dist packages without a MANIFEST file > Run 'Build manifest' to generate one > > WARNING: Possible missing or corrupt 'MANIFEST' file. > Nothing to enter for 'provides' field in metafile. > Created MYMETA.yml and MYMETA.json > Creating new 'Build' script for 'Config-Model-Dpkg' version '0' >dh_auto_build > /usr/bin/perl Build > Checking doc for model Dpkg::Patch > Wrote documentation in lib/Config/Model/models/Dpkg/Patch.pod > Checking doc for model Dpkg > Wrote documentation in lib/Config/Model/models/Dpkg.pod > Wrote documentation in lib/Config/Model/models/Dpkg/BugFiles.pod > Wrote documentation in lib/Config/Model/models/Dpkg/BugFiles/Control.pod > Wrote documentation in lib/Config/Model/models/Dpkg/Control.pod > Wrote documentation in lib/Config/Model/models/Dpkg/Control/Binary.pod > Wrote documentation in lib/Config/Model/models/Dpkg/Control/Source.pod > Wrote documentation in lib/Config/Model/models/Dpkg/Copyright.pod > Wrote documentation in lib/Config/Model/models/Dpkg/Copyright/Content.pod > Wrote documentation in lib/Config/Model/models/Dpkg/Copyright/FileLicense.pod > Wrote documentation in lib/Config/Model/models/Dpkg/Copyright/FillBlanks.pod > Wrote documentation in > lib/Config/Model/models/Dpkg/Copyright/FillBlanks/Pattern.pod > Wrote documentation in > lib/Config/Model/models/Dpkg/Copyright/GlobalLicense.pod > Wrote documentation in lib/Config/Model/models/Dpkg/Copyright/LicenseSpec.pod > Wrote documentation in lib/Config/Model/models/Dpkg/Copyright/ScanPatterns.pod > Wrote documentation in > lib/Config/Model/models/Dpkg/Copyright/ScanPatterns/Lists.pod > Wrote documentation in lib/Config/Model/models/Dpkg/Install.pod > Wrote documentation in lib/Config/Model/models/Dpkg/Meta.pod > Wrote documentation in lib/Config/Model/models/Dpkg/PackageScripts.pod > Wrote documentation in lib/Config/Model/models/Dpkg/Source.pod > Wrote documentation in lib/Config/Model/models/Dpkg/Source/Options.pod > Wrote documentation in lib/Config/Model/models/Dpkg/Tests.pod > Wrote documentation in lib/Config/Model/models/Dpkg/Tests/Control.pod > Checking doc for model Dpkg::Copyright > Checking doc for model Dpkg::Patches > Wrote documentation in lib/Config/Model/models/Dpkg/Patches.pod > Checking doc for model Dpkg::Control > Building Config-Model-Dpkg >dh_auto_test > /usr/bin/perl Build test --verbose 1 > when is deprecated at /usr/share/perl5/App/Cme/Command/run.pm line 185. > when is deprecated at /usr/share/perl5/App/Cme/Command/run.pm line 188. > when is deprecated at /usr/share/perl5/App/Cme/Command/run.pm line 191. > when is deprecated at /usr/share/perl5/App/Cme/Command/run.pm line 196. > when is deprecated at /usr/share/perl5/App/Cme/Command/run.pm line 200. > when is deprecated at /usr/share/perl5/App/Cme/Command/run.pm line 203. > when is deprecated at /usr/share/perl5/App/Cme/Command/run.pm line 207. > t/cme-scripts.t .. > > Reading package lists... 0% > > Reading package lists... 100% > > Reading package lists... Done > > > Building dependency tree... 0% > > Building dependency tree... 0% > > Building dependency tree... 50% > > Building dependency tree... 50% > > Building dependency tree... Done > > > Reading state information... 0% > > Reading state information... 0% > > Reading state information... Done > > # Subtest: bump_dependency > ok 1 - all went well > ok 2 - check changes on stderr > ok 3 - check: no message on stdout > ok 4 - updated dependency in file > 1..4 > ok 1 - bump_dependency > # Subtest: update_my_copyright_year > ok 1 - all went well > ok 2 - check: no message on stdout > ok 3 - updated copyright in file > 1..3 > ok 2 - update_my_copyright_year > 1..2 > ok > t/copyright-from-scratch.t ... > ok 1 - compiled > # Running tests in wr_root/copyright-from-scratch > # Subtest: Creation of debian/copyright > ok 1 - initial load is done > ok 2 - check license text brought by Software::License > ok 3 - check lic text > ok 4 - check lic text > ok 5 - check lic text > 1..5 > ok 2 - Creation of debian/copyright > # Subtest: Check "and/or"
Bug#1061036: trash-cli: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Source: trash-cli Version: 0.23.2.13.2-1.1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild >dh_auto_build -O--buildsystem=pybuild > I: pybuild plugin_pyproject:129: Building wheel for python3.11 with "build" > module > I: pybuild base:305: python3.11 -m build --skip-dependency-check > --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.11 > * Building wheel... > running bdist_wheel > running build > running build_py > creating build > creating build/lib > creating build/lib/trashcli > copying trashcli/__init__.py -> build/lib/trashcli > copying trashcli/rm.py -> build/lib/trashcli > copying trashcli/trash_dirs_scanner.py -> build/lib/trashcli > copying trashcli/list.py -> build/lib/trashcli > copying trashcli/py2compat.py -> build/lib/trashcli > copying trashcli/trash.py -> build/lib/trashcli > copying trashcli/list_mount_points.py -> build/lib/trashcli > copying trashcli/super_enum.py -> build/lib/trashcli > copying trashcli/fstab.py -> build/lib/trashcli > copying trashcli/shell_completion.py -> build/lib/trashcli > copying trashcli/fs.py -> build/lib/trashcli > creating build/lib/trashcli/empty > copying trashcli/empty/__init__.py -> build/lib/trashcli/empty > copying trashcli/empty/print_version_action.py -> build/lib/trashcli/empty > copying trashcli/empty/parser.py -> build/lib/trashcli/empty > copying trashcli/empty/older_than.py -> build/lib/trashcli/empty > copying trashcli/empty/empty_action.py -> build/lib/trashcli/empty > copying trashcli/empty/delete_according_date.py -> build/lib/trashcli/empty > copying trashcli/empty/main.py -> build/lib/trashcli/empty > copying trashcli/empty/print_time_action.py -> build/lib/trashcli/empty > copying trashcli/empty/description.py -> build/lib/trashcli/empty > copying trashcli/empty/prepare_output_message.py -> build/lib/trashcli/empty > copying trashcli/empty/emptier.py -> build/lib/trashcli/empty > copying trashcli/empty/errors.py -> build/lib/trashcli/empty > copying trashcli/empty/console.py -> build/lib/trashcli/empty > copying trashcli/empty/empty_cmd.py -> build/lib/trashcli/empty > copying trashcli/empty/user.py -> build/lib/trashcli/empty > copying trashcli/empty/is_input_interactive.py -> build/lib/trashcli/empty > copying trashcli/empty/actions.py -> build/lib/trashcli/empty > copying trashcli/empty/guard.py -> build/lib/trashcli/empty > copying trashcli/empty/parse_reply.py -> build/lib/trashcli/empty > copying trashcli/empty/existing_file_remover.py -> build/lib/trashcli/empty > creating build/lib/trashcli/lib > copying trashcli/lib/__init__.py -> build/lib/trashcli/lib > copying trashcli/lib/my_permission_error.py -> build/lib/trashcli/lib > copying trashcli/lib/my_input.py -> build/lib/trashcli/lib > creating build/lib/trashcli/put > copying trashcli/put/class_name_meta.py -> build/lib/trashcli/put > copying trashcli/put/trasher.py -> build/lib/trashcli/put > copying trashcli/put/trash_directories_finder.py -> build/lib/trashcli/put > copying trashcli/put/__init__.py -> build/lib/trashcli/put > copying trashcli/put/trash_put_cmd.py -> build/lib/trashcli/put > copying trashcli/put/trash_dir_volume_reader.py -> build/lib/trashcli/put > copying trashcli/put/volume_message_formatter.py -> build/lib/trashcli/put > copying trashcli/put/trash_all.py -> build/lib/trashcli/put > copying trashcli/put/parser.py -> build/lib/trashcli/put > copying trashcli/put/info_dir.py -> build/lib/trashcli/put > copying trashcli/put/trash_result.py -> build/lib/trashcli/put > copying trashcli/put/main.py -> build/lib/trashcli/put > copying trashcli/put/candidate.py -> build/lib/trashcli/put > copying trashcli/put/trashing_checker.py -> build/lib/trashcli/put > copying trashcli/put/security_check.py -> build/lib/trashcli/put > copying trashcli/put/reporter.py -> build/lib/trashcli/put > copying trashcli/put/trashee.py -> build/lib/trashcli/put > copying trashcli/put/suffix.py -> build/lib/trashcli/put > copying trashcli/put/describer.py -> build/lib/trashcli/put > copying trashcli/put/my_logger.py -> build/lib/trashcli/put > copying trashcli/put/trash_directory_for_put.py -> build/lib/trashcli/put > copying trashcli/put/file_trasher.py -> build/lib/trashcli/put > copying trashcli/put/same_volume_gate.py -> build/lib/trashcli/put > copying trashcli/put/gate.py -> build/lib/trashcli/put > copying trashcli/put/original_location.py -> build/lib/trashcli/put > copying trashcli/put/user.py -> build/lib/trashcli/put > copying trashcli/put/format_trash_info.py -> build/lib/trashcli/put > copying trashcli/put/clock.py -> build/lib/trashcli/put > copying
Bug#1061032: golang-github-go-kit-kit: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/go-kit/kit/auth/basic github.com/go-kit/kit/auth/casbin [...] returned
Source: golang-github-go-kit-kit Version: 0.10.0-5 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --buildsystem=golang >dh_update_autotools_config -O--buildsystem=golang >dh_autoreconf -O--buildsystem=golang >dh_auto_configure -O--buildsystem=golang > Copy go.mod -> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/go.mod > Copy go.sum -> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/go.sum > Copy transport/doc.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/doc.go > Copy transport/error_handler.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/error_handler.go > Copy transport/error_handler_test.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/error_handler_test.go > Copy transport/httprp/server.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/httprp/server.go > Copy transport/httprp/server_test.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/httprp/server_test.go > Copy transport/httprp/doc.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/httprp/doc.go > Copy transport/http/example_test.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/example_test.go > Copy transport/http/server.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/server.go > Copy transport/http/request_response_funcs_test.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/request_response_funcs_test.go > Copy transport/http/server_test.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/server_test.go > Copy transport/http/doc.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/doc.go > Copy transport/http/request_response_funcs.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/request_response_funcs.go > Copy transport/http/client_test.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/client_test.go > Copy transport/http/encode_decode.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/encode_decode.go > Copy transport/http/client.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/client.go > Copy transport/http/jsonrpc/request_response_types_test.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/jsonrpc/request_response_types_test.go > Copy transport/http/jsonrpc/server.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/jsonrpc/server.go > Copy transport/http/jsonrpc/error_test.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/jsonrpc/error_test.go > Copy transport/http/jsonrpc/server_test.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/jsonrpc/server_test.go > Copy transport/http/jsonrpc/doc.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/jsonrpc/doc.go > Copy transport/http/jsonrpc/client_test.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/jsonrpc/client_test.go > Copy transport/http/jsonrpc/request_response_types.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/jsonrpc/request_response_types.go > Copy transport/http/jsonrpc/encode_decode.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/jsonrpc/encode_decode.go > Copy transport/http/jsonrpc/error.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/jsonrpc/error.go > Copy transport/http/jsonrpc/client.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/jsonrpc/client.go > Copy transport/http/proto/server.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/proto/server.go > Copy transport/http/proto/proto_test.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/proto/proto_test.go > Copy transport/http/proto/proto_pb_test.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/proto/proto_pb_test.go > Copy transport/http/proto/proto_test.proto -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/proto/proto_test.proto > Copy transport/http/proto/client.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/proto/client.go > Copy transport/grpc/server.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/grpc/server.go > Copy transport/grpc/doc.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/grpc/doc.go > Copy transport/grpc/request_response_funcs.go -> > obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/grpc/request_response_funcs.go >
Bug#1061034: c-evo-dh: FTBFS: make[1]: *** [debian/rules:39: override_dh_auto_build] Error 2
Source: c-evo-dh Version: 1.10-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > # Show versions > lazbuild -v > 3.0 > echo 1.10-1 > 1.10-1 > # Show location of gcc support files > grep gcc /etc/fpc.cfg > # path to the gcclib > -Fl/usr/lib/gcc/x86_64-linux-gnu/13 > -Fl/usr/lib/gcc/x86_64-linux-gnu/13 > dirname `gcc -print-libgcc-file-name` > /usr/lib/gcc/x86_64-linux-gnu/13 > # Use custom fpc.cfg > cp Pascal/Release.cfg fpc.cfg > cp Pascal/Release.cfg AI/StdAI/fpc.cfg > cp Pascal/Release.cfg Packages/CevoComponents/fpc.cfg > cp Pascal/Release.cfg Packages/Common/fpc.cfg > # > # Build AI module (Peephole broken in fpc < 3.2.4) > cd AI/StdAI && fpc -dRelease -Xc -B -O3 -OoNOPEEPHOLE -k-znoexecstack > -k-zseparate-code -olibstdai.so StdAI.lpr > Compiling Release Version > Compile Release Version > Free Pascal Compiler version 3.2.2+dfsg-32 [2024/01/05] for x86_64 > Copyright (c) 1993-2021 by Florian Klaempfl and others > (1002) Target OS: Linux for x86-64 > (3104) Compiling StdAI.lpr > (3104) Compiling Protocol.pas > (3104) Compiling CustomAI.pas > (3104) Compiling ToolAI.pas > (3104) Compiling Pile.pas > (3104) Compiling AI.pas > (3104) Compiling Barbarina.pas > (9015) Linking libstdai.so > (1008) 10306 lines compiled, 0.6 sec > # > # Build GTK2 program > rm -fr tmphome > rm -fr lib > rm -fr Packages/CevoComponents/lib > lazbuild --bm=Release -B --ws=gtk2 --no-write-project Integrated.lpi > CopySecondaryConfigFile /etc/lazarus/environmentoptions.xml -> > /<>/tmphome/.lazarus/environmentoptions.xml > Note: (lazarus) Invalid Package Link: file > "/usr/lib/lazarus/3.0/ide/packages/ideconfig/ideconfig.lpk" does not exist. > > $563872B27B7A > $563872B22B65 > $563872A7EF2E > $5638730D0713 > $563872C32C83 > $563872C1D1DE > $563872C1D0D8 > $563872A8313D > $563872A80D64 > $563872A7F3EB > $563872A84C93 > $563872A87979 > $563872AA975C > Error: (lazbuild) Package file not found > The package "IdeConfig" is installed but no valid package file (.lpk) was > found. > A broken dummy package was created. > lazbuild is non interactive, aborting now. > make[1]: *** [debian/rules:39: override_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2024/01/15/c-evo-dh_1.10-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1061031: bdebstrap: FTBFS: AttributeError: module 'astroid.nodes' has no attribute 'TryExcept'
Source: bdebstrap Version: 0.6.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --buildsystem pybuild --with python3 >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:305: python3.11 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:305: /usr/bin/python3 setup.py build > running build > running doc > running command: pandoc -s -t man bdebstrap.1.md -o bdebstrap.1 > running build_scripts > creating build > creating build/scripts-3.11 > copying and adjusting bdebstrap -> build/scripts-3.11 > changing mode of build/scripts-3.11/bdebstrap from 644 to 755 >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:305: cd /<>/.pybuild/cpython3_3.11/build; > python3.11 -m unittest discover -v -s /<> > test_get_path_exists (tests.TestGetPath.test_get_path_exists) > Test get_path(__file__). ... ok > test_get_path_missing (tests.TestGetPath.test_get_path_missing) > Test non-existing file for get_path(). ... ok > test_get_path_pybuild (tests.TestGetPath.test_get_path_pybuild) > Test changing current directory before calling get_path(). ... ok > test_black (tests.test_black.BlackTestCase.test_black) > Test: Run black code formatter on Python source code. ... Running following > command: > black --check --diff -l 99 /<>/bdebstrap tests > /<>/setup.py > ok > test_debug (tests.test_config.TestArguments.test_debug) > Test --debug argument parsing. ... ok > test_empty_args (tests.test_config.TestArguments.test_empty_args) > Test setting arguments to empty strings. ... ok > test_malformed_env (tests.test_config.TestArguments.test_malformed_env) > Test malformed --env parameter (missing equal sign). ... ok > test_mirrors_with_spaces > (tests.test_config.TestArguments.test_mirrors_with_spaces) > Test --mirrors with leading/trailing spaces. ... ok > test_no_args (tests.test_config.TestArguments.test_no_args) > Test calling bdebstrap without arguments. ... ok > test_optional_args (tests.test_config.TestArguments.test_optional_args) > Test optional arguments (which also have positional ones). ... ok > test_parse_env (tests.test_config.TestArguments.test_parse_env) > Test parsing --env parameters. ... ok > test_positional_args (tests.test_config.TestArguments.test_positional_args) > Test positional arguments (overwriting optional ones). ... ok > test_split (tests.test_config.TestArguments.test_split) > Test splitting comma and space separated values. ... ok > test_add_command_line_arguments > (tests.test_config.TestConfig.test_add_command_line_arguments) > Test Config.add_command_line_arguments(). ... ok > test_add_command_line_arguments_no_config > (tests.test_config.TestConfig.test_add_command_line_arguments_no_config) > Test Config.add_command_line_arguments() with no config file. ... ok > test_check_example (tests.test_config.TestConfig.test_check_example) > Test example unstable.yaml file. ... ok > test_commented_packages (tests.test_config.TestConfig.test_commented_packages) > Test commented-packages.yaml file. ... ok > test_config_and_arguments > (tests.test_config.TestConfig.test_config_and_arguments) > Test Config.add_command_line_arguments() with config file and arguments. ... > ok > test_env_items (tests.test_config.TestConfig.test_env_items) > Test environment variables for example unstable.yaml. ... ok > test_loading (tests.test_config.TestConfig.test_loading) > Test loading a YAML configuration file. ... ok > test_sanitize_packages_debs > (tests.test_config.TestConfig.test_sanitize_packages_debs) > Test sanitize_packages method: multiple local .debs ... ok > test_sanitize_packages_duplicate_debs > (tests.test_config.TestConfig.test_sanitize_packages_duplicate_debs) > Test sanitize_packages method: remove duplicate local .debs. ... ok > test_sanitize_packages_duplicates > (tests.test_config.TestConfig.test_sanitize_packages_duplicates) > Test sanitize_packages method: remove duplicates. ... ok > test_sanitize_packages_pattern > (tests.test_config.TestConfig.test_sanitize_packages_pattern) > Test sanitize_packages method: APT pattern ... ok > test_source_date_epoch (tests.test_config.TestConfig.test_source_date_epoch) > Test getting and setting SOURCE_DATE_EPOCH. ... ok > test_wrong_element_type (tests.test_config.TestConfig.test_wrong_element_type) > Test error message for wrong list element type. ... ok > test_yaml_rendering (tests.test_config.TestConfig.test_yaml_rendering) > Test that config.yaml is formatted correctly. ... ok > test_merge_lists (tests.test_config.TestDictMerge.test_merge_lists) > Test merging nested dicts. ... ok > test_merge_nested_dicts > (tests.test_config.TestDictMerge.test_merge_nested_dicts) >
Bug#1061028: flask-restful: FTBFS: intersphinx inventory 'six/objects.inv' not fetchable due to : [Errno 2] No such file or directory: '/<>/docs/six/objects.inv
Source: flask-restful
Version: 0.3.9-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/docs'
> sphinx-build -b html -d _build/doctrees . _build/html
> Running Sphinx v7.2.6
> making output directory... done
> WARNING: The pre-Sphinx 1.0 'intersphinx_mapping' format is deprecated and
> will be removed in Sphinx 8. Update to the current format as described in the
> documentation. Hint: "intersphinx_mapping = {'': ('six',
> None)}".https://www.sphinx-doc.org/en/master/usage/extensions/intersphinx.html#confval-intersphinx_mapping
> loading intersphinx inventory from
> /usr/share/doc/python-flask-doc/html/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory '/usr/share/doc/python-flask-doc/html/objects.inv' not
> fetchable due to : [Errno 2] No such file or
> directory: '/usr/share/doc/python-flask-doc/html/objects.inv'
> loading intersphinx inventory from
> /usr/share/doc/python-werkzeug-doc/html/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory '/usr/share/doc/python-werkzeug-doc/html/objects.inv'
> not fetchable due to : [Errno 2] No such file or
> directory: '/usr/share/doc/python-werkzeug-doc/html/objects.inv'
> loading intersphinx inventory from
> /usr/share/doc/python3-doc/html/objects.inv...
> loading intersphinx inventory from
> /usr/share/doc/python3-doc/html/objects.inv...
> loading intersphinx inventory from six/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'six/objects.inv' not fetchable due to 'FileNotFoundError'>: [Errno 2] No such file or directory:
> '/<>/docs/six/objects.inv'
> building [mo]: targets for 0 po files that are out of date
> writing output...
> building [html]: targets for 9 source files that are out of date
> updating environment: [new config] 9 added, 0 changed, 0 removed
> [2Kreading sources... [ 11%] api
> [2Kreading sources... [ 22%] extending
> [2Kreading sources... [ 33%] fields
> [2Kreading sources... [ 44%] index
> [2Kreading sources... [ 56%] installation
> [2Kreading sources... [ 67%] intermediate-usage
> [2Kreading sources... [ 78%] quickstart
> [2Kreading sources... [ 89%] reqparse
> [2Kreading sources... [100%] testing
>
> /<>/flask_restful/__init__.py:docstring of
> flask_restful.Api.unauthorized:1: WARNING: duplicate object description of
> flask_restful.Api.unauthorized, other instance in api, use :no-index: for one
> of them
> /<>/docs/index.rst:6: WARNING: duplicate object description of
> flask_restful, other instance in api, use :no-index: for one of them
> /<>/docs/reqparse.rst:217: WARNING: Explicit markup ends without
> a blank line; unexpected unindent.
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> copying assets... copying static files... done
> copying extra files... done
> done
> [2Kwriting output... [ 11%] api
> [2Kwriting output... [ 22%] extending
> [2Kwriting output... [ 33%] fields
> [2Kwriting output... [ 44%] index
> [2Kwriting output... [ 56%] installation
> [2Kwriting output... [ 67%] intermediate-usage
> [2Kwriting output... [ 78%] quickstart
> [2Kwriting output... [ 89%] reqparse
> [2Kwriting output... [100%] testing
>
> /<>/docs/intermediate-usage.rst:80: WARNING: undefined label:
> 'blueprints'
> generating indices... genindex py-modindex done
> writing additional pages... search done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded, 8 warnings.
>
> The HTML pages are in _build/html.
>
> Build finished. The HTML pages are in _build/html.
> make[2]: Leaving directory '/<>/docs'
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:305: cd
> /<>/.pybuild/cpython3_3.12_flask-restful/build; python3.12 -m
> pytest tests
> = test session starts
> ==
> platform linux -- Python 3.12.1, pytest-7.4.4, pluggy-1.3.0
> rootdir: /<>
> collected 318 items
>
> tests/test_accept.py [
> 3%]
> tests/test_api.py x.F... [
> 20%]
> ...FF... [
> 29%]
> tests/test_api_with_blueprint.py . [
> 33%]
> tests/test_cors.py [
> 34%]
> tests/test_fields.py ... [
> 50%]
> [
> 57%]
>
Bug#1061029: lookatme: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Source: lookatme Version: 2.5.4-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/docs' > Running Sphinx v7.2.6 > making output directory... done > Creating file /<>/docs/source/autodoc/lookatme.rst. > Creating file /<>/docs/source/autodoc/lookatme.ascii_art.rst. > Creating file /<>/docs/source/autodoc/lookatme.config.rst. > Creating file /<>/docs/source/autodoc/lookatme.exceptions.rst. > Creating file /<>/docs/source/autodoc/lookatme.log.rst. > Creating file /<>/docs/source/autodoc/lookatme.parser.rst. > Creating file /<>/docs/source/autodoc/lookatme.pres.rst. > Creating file /<>/docs/source/autodoc/lookatme.prompt.rst. > Creating file /<>/docs/source/autodoc/lookatme.schemas.rst. > Creating file /<>/docs/source/autodoc/lookatme.slide.rst. > Creating file /<>/docs/source/autodoc/lookatme.tui.rst. > Creating file /<>/docs/source/autodoc/lookatme.tutorial.rst. > Creating file /<>/docs/source/autodoc/lookatme.utils.rst. > Creating file /<>/docs/source/autodoc/lookatme.contrib.rst. > Creating file > /<>/docs/source/autodoc/lookatme.contrib.file_loader.rst. > Creating file > /<>/docs/source/autodoc/lookatme.contrib.terminal.rst. > Creating file /<>/docs/source/autodoc/lookatme.render.rst. > Creating file > /<>/docs/source/autodoc/lookatme.render.asciinema.rst. > Creating file > /<>/docs/source/autodoc/lookatme.render.markdown_block.rst. > Creating file > /<>/docs/source/autodoc/lookatme.render.markdown_inline.rst. > Creating file > /<>/docs/source/autodoc/lookatme.render.pygments.rst. > Creating file /<>/docs/source/autodoc/lookatme.themes.rst. > Creating file /<>/docs/source/autodoc/lookatme.themes.dark.rst. > Creating file /<>/docs/source/autodoc/lookatme.themes.light.rst. > Creating file /<>/docs/source/autodoc/lookatme.widgets.rst. > Creating file > /<>/docs/source/autodoc/lookatme.widgets.clickable_text.rst. > Creating file /<>/docs/source/autodoc/lookatme.widgets.table.rst. > Creating file /<>/docs/source/autodoc/modules.rst. > building [mo]: targets for 0 po files that are out of date > writing output... > building [html]: targets for 12 source files that are out of date > updating environment: [new config] 40 added, 0 changed, 0 removed > [2Kreading sources... [ 2%] autodoc/lookatme > [2Kreading sources... [ 5%] autodoc/lookatme.ascii_art > [2Kreading sources... [ 8%] autodoc/lookatme.config > [2Kreading sources... [ 10%] autodoc/lookatme.contrib > [2Kreading sources... [ 12%] autodoc/lookatme.contrib.file_loader > [2Kreading sources... [ 15%] autodoc/lookatme.contrib.terminal > [2Kreading sources... [ 18%] autodoc/lookatme.exceptions > [2Kreading sources... [ 20%] autodoc/lookatme.log > [2Kreading sources... [ 22%] autodoc/lookatme.parser > [2Kreading sources... [ 25%] autodoc/lookatme.pres > [2Kreading sources... [ 28%] autodoc/lookatme.prompt > [2Kreading sources... [ 30%] autodoc/lookatme.render > [2Kreading sources... [ 32%] autodoc/lookatme.render.asciinema > [2Kreading sources... [ 35%] autodoc/lookatme.render.markdown_block > [2Kreading sources... [ 38%] autodoc/lookatme.render.markdown_inline > [2Kreading sources... [ 40%] autodoc/lookatme.render.pygments > [2Kreading sources... [ 42%] autodoc/lookatme.schemas > [2Kreading sources... [ 45%] autodoc/lookatme.slide > [2Kreading sources... [ 48%] autodoc/lookatme.themes > [2Kreading sources... [ 50%] autodoc/lookatme.themes.dark > [2Kreading sources... [ 52%] autodoc/lookatme.themes.light > [2Kreading sources... [ 55%] autodoc/lookatme.tui > [2Kreading sources... [ 57%] autodoc/lookatme.tutorial > [2Kreading sources... [ 60%] autodoc/lookatme.utils > [2Kreading sources... [ 62%] autodoc/lookatme.widgets > [2Kreading sources... [ 65%] autodoc/lookatme.widgets.clickable_text > [2Kreading sources... [ 68%] autodoc/lookatme.widgets.table > [2Kreading sources... [ 70%] autodoc/modules > [2Kreading sources... [ 72%] builtin_extensions/file_loader > [2Kreading sources... [ 75%] builtin_extensions/index > [2Kreading sources... [ 78%] builtin_extensions/terminal > [2Kreading sources... [ 80%] contrib_extensions > [2Kreading sources... [ 82%] contrib_extensions_auto > [2Kreading sources... [ 85%] dark_theme > [2Kreading sources... [ 88%] getting_started > [2Kreading sources... [ 90%] index > [2Kreading sources... [ 92%] light_theme > [2Kreading sources... [ 95%] slides > [2Kreading sources... [ 98%] smart_splitting > [2Kreading sources... [100%] style_precedence > > /<>/docs/source/../../lookatme/contrib/__init__.py:docstring of > lookatme.contrib:7: WARNING: Inline emphasis start-string without end-string. > /<>/docs/source/../../lookatme/contrib/__init__.py:docstring of > lookatme.contrib:7: WARNING: Inline strong start-string without end-string. >
Bug#1061030: wavbreaker: FTBFS: dpkg-checkbuilddeps: error: Unmet build dependencies: scour:native
Source: wavbreaker Version: 0.16-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -sa > dpkg-buildpackage: info: source package wavbreaker > dpkg-buildpackage: info: source version 0.16-2 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Dennis Braun > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > dpkg-checkbuilddeps: error: Unmet build dependencies: scour:native > dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting > dpkg-buildpackage: warning: (Use -d flag to override.) > > Build finished at 2024-01-15T20:25:04Z The full build log is available from: http://qa-logs.debian.net/2024/01/15/wavbreaker_0.16-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1061026: python-watchgod: FTBFS: FAILED tests/test_watch.py::test_watch_log[trio] - RuntimeError: Already runn...
Source: python-watchgod
Version: 0.8.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:305: python3.12 setup.py config
> running config
> I: pybuild base:305: python3.11 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3.12 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> copying watchgod/__init__.py ->
> /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> copying watchgod/version.py ->
> /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> copying watchgod/main.py ->
> /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> copying watchgod/watcher.py ->
> /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> copying watchgod/__main__.py ->
> /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> copying watchgod/cli.py ->
> /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> copying watchgod/py.typed ->
> /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> I: pybuild base:305: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
> copying watchgod/__init__.py ->
> /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
> copying watchgod/version.py ->
> /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
> copying watchgod/main.py ->
> /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
> copying watchgod/watcher.py ->
> /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
> copying watchgod/__main__.py ->
> /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
> copying watchgod/cli.py ->
> /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
> copying watchgod/py.typed ->
> /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:305: cd
> /<>/.pybuild/cpython3_3.12_watchgod/build; python3.12 -m pytest
> -W ignore::trio.TrioDeprecationWarning
> = test session starts
> ==
> platform linux -- Python 3.12.1, pytest-7.4.4, pluggy-1.3.0
> rootdir: /<>
> configfile: setup.cfg
> plugins: anyio-4.1.0, asyncio-0.20.3, toolbox-0.4, sugar-0.9.7, mock-3.12.0
> asyncio: mode=Mode.STRICT
> collected 162 items
>
> tests/test_cli.py .. [
> 33%]
> ... [
> 42%]
> tests/test_run_process.py F..[
> 51%]
> tests/test_watch.py [
> 83%]
> ....F..F..
> [100%]
>
> === FAILURES
> ===
> _ test_async_alive_terminates[asyncio+uvloop]
> __
>
> pyfuncitem =
>
> @pytest.hookimpl(tryfirst=True)
> def pytest_pyfunc_call(pyfuncitem: Any) -> bool | None:
> def run_with_hypothesis(**kwargs: Any) -> None:
> with get_runner(backend_name, backend_options) as runner:
> runner.run_test(original_func, kwargs)
>
> backend = pyfuncitem.funcargs.get("anyio_backend")
> if backend:
> backend_name, backend_options =
> extract_backend_and_options(backend)
>
> if hasattr(pyfuncitem.obj, "hypothesis"):
> # Wrap the inner test function unless it's already wrapped
> original_func = pyfuncitem.obj.hypothesis.inner_test
> if original_func.__qualname__ !=
> run_with_hypothesis.__qualname__:
> if iscoroutinefunction(original_func):
> pyfuncitem.obj.hypothesis.inner_test =
> run_with_hypothesis
>
> return None
>
> if iscoroutinefunction(pyfuncitem.obj):
> funcargs = pyfuncitem.funcargs
> testargs = {arg: funcargs[arg] for arg in
> pyfuncitem._fixtureinfo.argnames}
> > with get_runner(backend_name, backend_options) as runner:
>
> /usr/lib/python3/dist-packages/anyio/pytest_plugin.py:123:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> /usr/lib/python3.12/contextlib.py:137: in __enter__
> return next(self.gen)
> /usr/lib/python3/dist-packages/anyio/pytest_plugin.py:45: in get_runner
> asynclib.create_test_runner(backend_options)
> /usr/lib/python3/dist-packages/anyio/_backends/_asyncio.py:2431: in
> create_test_runner
>
Bug#1061027: moment-timezone.js: FTBFS: make[1]: *** [debian/rules:28: execute_before_dh_auto_configure] Error 1
Source: moment-timezone.js Version: 0.5.43+dfsg-1+2023c Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >debian/rules execute_before_dh_auto_configure > make[1]: Entering directory '/<>' > # Fail the build if the tzdata package does not match TZVER. > grep -q '^# version 2023c$' /usr/share/zoneinfo/tzdata.zi > make[1]: *** [debian/rules:28: execute_before_dh_auto_configure] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/01/15/moment-timezone.js_0.5.43+dfsg-1+2023c_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1061024: transgui: FTBFS: InitializeFppkg failed: Unable to create file "/sbuild-nonexistent/.config/fppkg.cfg": No such file or directory
Source: transgui Version: 5.18.0+dfsg-3.1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lazbuild -B transgui.lpi --lazarusdir=/usr/lib/lazarus/default/ > CopySecondaryConfigFile /etc/lazarus/environmentoptions.xml -> > /sbuild-nonexistent/.lazarus/environmentoptions.xml > WARNING: unable to create primary config directory > "/sbuild-nonexistent/.lazarus" > SetupCompilerFilename: Searching compiler ... > SearchCompilerCandidates Value=/usr/bin/fpc File=/usr/bin/fpc > SetupCompilerFilename: using /usr/bin/fpc > Hint: (lazarus) storing Lazarus directory "/usr/lib/lazarus/default/" > Compiler path "/usr/bin/fpc" in > "/sbuild-nonexistent/.lazarus/environmentoptions.xml" > Error: (lazarus) unable to edit file > /sbuild-nonexistent/.lazarus/environmentoptions.xml > InitializeFppkg failed: Unable to create file > "/sbuild-nonexistent/.config/fppkg.cfg": No such file or directory > Note: (lazarus) Invalid Package Link: file > "/usr/lib/lazarus/default/ide/packages/ideconfig/ideconfig.lpk" does not > exist. > > $55596A94CB7A > $55596A947B65 > $55596A8A3F2E > $55596AEF5713 > $55596AA57C83 > $55596AA421DE > $55596AA420D8 > $55596A8A813D > $55596A8A5D64 > $55596A8A43EB > $55596A8A9C93 > $55596A8AC979 > $55596A8CE75C > Error: (lazbuild) Package file not found > The package "IdeConfig" is installed but no valid package file (.lpk) was > found. > A broken dummy package was created. > lazbuild is non interactive, aborting now. > make[1]: *** [debian/rules:13: override_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2024/01/15/transgui_5.18.0+dfsg-3.1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1061023: svtplay-dl: FTBFS: ModuleNotFoundError: No module named 'distutils.core'
Source: svtplay-dl Version: 3.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > argparse-manpage \ > --project-name svtplay-dl \ > --author 'Johan Andersson' \ > --author-email 'j...@i19.se' \ > --pyfile lib/svtplay_dl/utils/parser.py \ > --function gen_parser \ > --url https://svtplay-dl.se/ \ > --output svtplay-dl.1 > Traceback (most recent call last): > File "/usr/bin/argparse-manpage", line 5, in > from build_manpages.cli import main > File "/usr/lib/python3/dist-packages/build_manpages/cli/__init__.py", line > 5, in > from build_manpages.build_manpage import ManPageWriter, get_parser > File "/usr/lib/python3/dist-packages/build_manpages/build_manpage.py", line > 10, in > from distutils.core import Command > ModuleNotFoundError: No module named 'distutils.core' > make[1]: *** [debian/rules:25: svtplay-dl.1] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/01/15/svtplay-dl_3.0-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1061021: cinnamon-control-center: FTBFS: Package 'libevdev', required by 'libwacom', not found
Source: cinnamon-control-center Version: 5.8.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --with=gnome >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 > meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr > --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu > -Dpython.bytecompile=-1 > The Meson build system > Version: 1.3.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: cinnamon-control-center > Project version: 5.8.2 > C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-9) 13.2.0") > C linker for the host machine: cc ld.bfd 2.41.50.20231227 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Library m found: YES > Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1 > Run-time dependency cinnamon-desktop found: YES 5.8.0 > Run-time dependency libcinnamon-menu-3.0 found: YES 6.0.0 > Run-time dependency gtk+-3.0 found: YES 3.24.39 > Run-time dependency glib-2.0 found: YES 2.78.3 > Run-time dependency gio-unix-2.0 found: YES 2.78.3 > Run-time dependency gudev-1.0 found: YES 238 > Run-time dependency libgnomekbd found: YES 3.28.1 > Run-time dependency libgnomekbdui found: YES 3.28.1 > Run-time dependency libnotify found: YES 0.8.3 > Run-time dependency x11 found: YES 1.8.7 > Run-time dependency polkit-gobject-1 found: YES 123 > Run-time dependency libxklavier found: YES 5.4 > Run-time dependency upower-glib found: YES 1.90.2 > Has header "X11/extensions/XKB.h" : YES > Run-time dependency iso-codes found: YES 4.16.0 > Run-time dependency libnm found: YES 1.44.2 > Run-time dependency libnma found: YES 1.10.6 > Run-time dependency mm-glib found: YES 1.22.0 > Run-time dependency colord found: YES 1.4.6 > Did not find CMake 'cmake' > Found CMake: NO > Run-time dependency libwacom found: NO > > ../meson.build:86:14: ERROR: Dependency lookup for libwacom with method > 'pkgconfig' failed: Could not generate cflags for libwacom: > Package libevdev was not found in the pkg-config search path. > Perhaps you should add the directory containing `libevdev.pc' > to the PKG_CONFIG_PATH environment variable > Package 'libevdev', required by 'libwacom', not found > > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2024-01-15T20:22:22.141671 > Main binary: /usr/bin/python3 > Build Options: -Dpython.bytecompile=-1 -Dprefix=/usr > -Dlibdir=lib/x86_64-linux-gnu -Dlocalstatedir=/var -Dsysconfdir=/etc > -Dbuildtype=plain -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 1.3.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: cinnamon-control-center > Project version: 5.8.2 > --- > Detecting compiler via: `cc --version` -> 0 > stdout: > cc (Debian 13.2.0-9) 13.2.0 > Copyright (C) 2023 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > --- > Running command: cc -E -dM - > - > --- > Detecting linker via: `cc -Wl,--version -Wl,-z,relro -Wl,-z,now -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2` -> 0 > stdout: > GNU ld (GNU Binutils for Debian) 2.41.50.20231227 > Copyright (C) 2023 Free Software Foundation, Inc. > This program is free software; you may redistribute it under the terms of > the GNU General Public License version 3 or (at your option) a later version. > This program has absolutely no warranty. > --- > stderr: > collect2 version 13.2.0 > /usr/bin/ld -plugin /usr/libexec/gcc/x86_64-linux-gnu/13/liblto_plugin.so > -plugin-opt=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper > -plugin-opt=-fresolution=/tmp/ccwNlt0l.res -plugin-opt=-pass-through=-lgcc > -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lc > -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s --build-id > --eh-frame-hdr -m elf_x86_64 --hash-style=gnu --as-needed -dynamic-linker > /lib64/ld-linux-x86-64.so.2 -pie > /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/Scrt1.o > /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/crti.o > /usr/lib/gcc/x86_64-linux-gnu/13/crtbeginS.o > -L/usr/lib/gcc/x86_64-linux-gnu/13 > -L/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu >
Bug#1061016: sccache: FTBFS: unsatisfiable build-dependencies
Source: sccache Version: 0.7.4-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), dh-cargo, help2man, > librust-anyhow-1+backtrace-dev, librust-anyhow-1+default-dev, > librust-ar-0.9+default-dev, librust-assert-cmd-2+default-dev, > librust-async-trait-0.1+default-dev (>= 0.1.52), > librust-atty-0.2+default-dev, librust-base64-0.21+default-dev, > librust-bincode-1+default-dev, librust-blake3-1+default-dev, > librust-byteorder-1+default-dev, librust-bytes-1+default-dev, > librust-chrono-0.4+default-dev, librust-clap-4+default-dev, > librust-counted-array-0.1+default-dev, librust-daemonize-0.5+default-dev, > librust-directories-5+default-dev, librust-encoding-0.2+default-dev, > librust-env-logger-0.10+default-dev, librust-filetime-0.2+default-dev, > librust-flate2-1+rust-backend-dev, librust-fs-err-2+default-dev, > librust-futures-0.3+default-dev, librust-futures-locks-0.7+default-dev, > librust-http-0.2+default-dev, librust-hyper-0.14+default-dev (>= 0.14.19), > librust-hyper-0.14+server-dev, librust-is-terminal-0.4+default-dev, > librust-itertools-0.10+default-dev, librust-jobserver-0.1+default-dev, > librust-libc-0.2+default-dev, librust-linked-hash-map-0.5+default-dev, > librust-log-0.4+default-dev, librust-memchr-2+default-dev, > librust-memmap2-0.9+default-dev, librust-mime-0.3+default-dev, > librust-num-cpus-1+default-dev, librust-number-prefix-0.4+default-dev, > librust-object-dev (<< 0.32), librust-once-cell-1+default-dev (>= 1.17), > librust-predicates-3+default-dev, librust-rand-0.8+default-dev, > librust-regex-1+default-dev, librust-reqwest-0.11+blocking-dev, > librust-reqwest-0.11+default-dev, librust-reqwest-0.11+json-dev, > librust-reqwest-0.11+rustls-tls-dev, librust-reqwest-0.11+stream-dev, > librust-reqwest-0.11+trust-dns-dev, librust-retry-2+default-dev, > librust-semver-1+default-dev, librust-serde-1+default-dev, > librust-serde-1+derive-dev, librust-serde-json-1+default-dev, > librust-serial-test-2+default-dev, librust-sha2-0.10+default-dev, > librust-strip-ansi-escapes-0.1+default-dev, librust-tar-0.4+default-dev, > librust-tempfile-3+default-dev, librust-test-case-3+default-dev, > librust-tokio-1+default-dev, librust-tokio-1+io-util-dev, > librust-tokio-1+macros-dev, librust-tokio-1+net-dev, > librust-tokio-1+process-dev, librust-tokio-1+rt-multi-thread-dev, > librust-tokio-1+time-dev, librust-tokio-serde-0.8+default-dev, > librust-tokio-util-0.7+codec-dev, librust-tokio-util-0.7+default-dev, > librust-tokio-util-0.7+io-dev, librust-toml-dev (<< 0.9), > librust-tower-0.4+default-dev, librust-trust-dns-resolver-0.22+default-dev, > librust-trust-dns-resolver-0.22+dns-over-https-rustls-dev, > librust-trust-dns-resolver-0.22+dns-over-rustls-dev, > librust-trust-dns-resolver-0.22+dnssec-ring-dev, librust-url-2+default-dev, > librust-uuid-1+default-dev, librust-uuid-1+v4-dev, > librust-walkdir-2+default-dev, librust-which-4-dev, librust-zip-0.6-dev, > librust-zstd-dev (<< 0.14), libstring-shellquote-perl, rustc (>= 1.65), > build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), dh-cargo, help2man, > librust-anyhow-1+backtrace-dev, librust-anyhow-1+default-dev, > librust-ar-0.9+default-dev, librust-assert-cmd-2+default-dev, > librust-async-trait-0.1+default-dev (>= 0.1.52), > librust-atty-0.2+default-dev, librust-base64-0.21+default-dev, > librust-bincode-1+default-dev, librust-blake3-1+default-dev, > librust-byteorder-1+default-dev, librust-bytes-1+default-dev, > librust-chrono-0.4+default-dev, librust-clap-4+default-dev, > librust-counted-array-0.1+default-dev, librust-daemonize-0.5+default-dev, > librust-directories-5+default-dev, librust-encoding-0.2+default-dev, > librust-env-logger-0.10+default-dev, librust-filetime-0.2+default-dev, > librust-flate2-1+rust-backend-dev, librust-fs-err-2+default-dev, > librust-futures-0.3+default-dev, librust-futures-locks-0.7+default-dev, > librust-http-0.2+default-dev, librust-hyper-0.14+default-dev (>= 0.14.19), > librust-hyper-0.14+server-dev, librust-is-terminal-0.4+default-dev, > librust-itertools-0.10+default-dev, librust-jobserver-0.1+default-dev, > librust-libc-0.2+default-dev, librust-linked-hash-map-0.5+default-dev, > librust-log-0.4+default-dev, librust-memchr-2+default-dev, > librust-memmap2-0.9+default-dev, librust-mime-0.3+default-dev, > librust-num-cpus-1+default-dev, librust-number-prefix-0.4+default-dev, > librust-object-dev
Bug#1061020: libervia-pubsub: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_install] Error 25
Source: libervia-pubsub
Version: 0.4.0+hg488-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_install --destdir=debian/tmp
> I: pybuild base:305: /usr/bin/python3.12 setup.py install --root
> /<>/debian/tmp --install-lib=/usr/share/libervia
> --install-scripts=/usr/share/libervia --verbose
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84:
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are
> deprecated.
> !!
>
>
>
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
>
>
>
> !!
> dist.fetch_build_eggs(dist.setup_requires)
> WARNING: The wheel package is not available.
> /usr/lib/python3/dist-packages/setuptools_scm/_integration/setuptools.py:90:
> UserWarning: version of sat_pubsub already set
> warnings.warn(f"version of {dist_name} already set")
> /usr/lib/python3/dist-packages/setuptools/dist.py:509:
> SetuptoolsDeprecationWarning: Invalid version: '0.5.0D'.
> !!
>
>
>
> The version specified is not a valid version according to PEP 440.
> This may not work as expected with newer versions of
> setuptools, pip, and PyPI.
>
> This deprecation is overdue, please update your project and remove
> deprecated
> calls to avoid build errors in the future.
>
> See https://peps.python.org/pep-0440/ for details.
>
>
>
> !!
> self._validate_version(self.metadata.version)
> running install
> /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66:
> SetuptoolsDeprecationWarning: setup.py install is deprecated.
> !!
>
>
>
> Please avoid running ``setup.py`` directly.
> Instead, use pypa/build, pypa/installer or other
> standards-based tools.
>
> See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html
> for details.
>
>
>
> !!
> self.initialize_options()
> running build
> running build_py
> running install_lib
> creating /<>/debian/tmp/usr
> creating /<>/debian/tmp/usr/share
> creating /<>/debian/tmp/usr/share/libervia
> creating /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying /<>/.pybuild/cpython3_3.12/build/sat_pubsub/__init__.py
> -> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying /<>/.pybuild/cpython3_3.12/build/sat_pubsub/error.py ->
> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying /<>/.pybuild/cpython3_3.12/build/sat_pubsub/container.py
> -> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying
> /<>/.pybuild/cpython3_3.12/build/sat_pubsub/exceptions.py ->
> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying /<>/.pybuild/cpython3_3.12/build/sat_pubsub/const.py ->
> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying /<>/.pybuild/cpython3_3.12/build/sat_pubsub/iidavoll.py
> -> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying /<>/.pybuild/cpython3_3.12/build/sat_pubsub/privilege.py
> -> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying /<>/.pybuild/cpython3_3.12/build/sat_pubsub/mam.py ->
> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying /<>/.pybuild/cpython3_3.12/build/sat_pubsub/pam.py ->
> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying
> /<>/.pybuild/cpython3_3.12/build/sat_pubsub/pubsub_admin.py ->
> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying
> /<>/.pybuild/cpython3_3.12/build/sat_pubsub/pgsql_storage.py ->
> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> creating /<>/debian/tmp/usr/share/libervia/sat_pubsub/test
> copying
> /<>/.pybuild/cpython3_3.12/build/sat_pubsub/test/test_storage.py
> -> /<>/debian/tmp/usr/share/libervia/sat_pubsub/test
> copying
> /<>/.pybuild/cpython3_3.12/build/sat_pubsub/test/__init__.py ->
> /<>/debian/tmp/usr/share/libervia/sat_pubsub/test
> copying
> /<>/.pybuild/cpython3_3.12/build/sat_pubsub/test/test_backend.py
> -> /<>/debian/tmp/usr/share/libervia/sat_pubsub/test
> copying /<>/.pybuild/cpython3_3.12/build/sat_pubsub/backend.py
> -> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying /<>/.pybuild/cpython3_3.12/build/sat_pubsub/VERSION ->
> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying
> /<>/.pybuild/cpython3_3.12/build/sat_pubsub/delegation.py ->
>
Bug#1061017: octave-divand: FTBFS: make: *** [debian/rules:5: binary] Error 134
Source: octave-divand Version: 1.1.2+dfsg-6 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --buildsystem=octave >dh_update_autotools_config -O--buildsystem=octave >dh_autoreconf -O--buildsystem=octave >dh_octave_version -O--buildsystem=octave > Checking the Octave version... ok >dh_auto_configure -O--buildsystem=octave >dh_auto_build -O--buildsystem=octave >dh_auto_test -O--buildsystem=octave >create-stamp debian/debhelper-build-stamp >dh_testroot -O--buildsystem=octave >dh_prep -O--buildsystem=octave >dh_auto_install --destdir=debian/octave-divand/ -O--buildsystem=octave > octave --no-gui --no-history --silent --no-init-file --no-window-system > /usr/share/dh-octave/install-pkg.m > /<>/octave-divand-1.1.2\+dfsg/debian/octave-divand/usr/share/octave/packages > > /<>/octave-divand-1.1.2\+dfsg/debian/octave-divand/usr/lib/x86_64-linux-gnu/octave/packages > For information about changes from previous versions of the divand package, > run 'news divand'. >dh_octave_check -O--buildsystem=octave > Checking package... > Run the unit tests... > Checking m files ... > [inst/statevector_init.m] > > /<>/inst/statevector_init.m > * test > mask = rand(10,10) > .5; > mask_u = rand(9,10) > .5; > mask_v = rand(10,9) > .5; > sv = statevector_init(mask,mask_u,mask_v); > var = rand(10,10); > var(mask==0) = 0; > var_u = rand(9,10); > var_u(mask_u==0) = 0; > var(mask==0) = 0; > var_v = rand(10,9); > var_v(mask_v==0) = 0; > [E] = statevector_pack(sv,var,var_u,var_v); > [Ezeta2,Eu2,Ev2] = statevector_unpack(sv,E); > assert(Ezeta2,var) > assert(Eu2,var_u) > assert(Ev2,var_v) > 1 test, 1 passed, 0 known failure, 0 skipped > Checking C++ files ... > Run tests in debian/check.m > [test_divand] > run test_interp_1d: (max difference=2.77556e-16) [42m OK [0m > run test_interp_2d: (max difference=2.22045e-16) [42m OK [0m > run test_interp_regular: (max difference=2.22045e-16) [42m OK [0m > run test_sparse_diff: (max difference=0) [42m OK [0m > run test_1dvar: malloc(): invalid size (unsorted) > fatal: caught signal Aborted -- stopping myself... > Aborted > make: *** [debian/rules:5: binary] Error 134 The full build log is available from: http://qa-logs.debian.net/2024/01/15/octave-divand_1.1.2+dfsg-6_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1061018: octave-splines: FTBFS: make: *** [debian/rules:5: binary] Error 134
Source: octave-splines Version: 1.3.5-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --buildsystem=octave >dh_update_autotools_config -O--buildsystem=octave >dh_autoreconf -O--buildsystem=octave >dh_octave_version -O--buildsystem=octave > Checking the Octave version... ok >dh_auto_configure -O--buildsystem=octave >dh_auto_build -O--buildsystem=octave >dh_auto_test -O--buildsystem=octave >create-stamp debian/debhelper-build-stamp >dh_testroot -O--buildsystem=octave >dh_prep -O--buildsystem=octave >dh_auto_install --destdir=debian/octave-splines/ -O--buildsystem=octave > octave --no-gui --no-history --silent --no-init-file --no-window-system > /usr/share/dh-octave/install-pkg.m > /<>/debian/octave-splines/usr/share/octave/packages > /<>/debian/octave-splines/usr/lib/x86_64-linux-gnu/octave/packages > For information about changes from previous versions of the splines package, > run 'news splines'. >dh_octave_check -O--buildsystem=octave > Checking package... > Run the unit tests... > Checking m files ... > [inst/tps_val_der.m] > > /<>/inst/tps_val_der.m > * shared a,b,x,y,x1,x2,y1,c,dy,dy0 > a = 2; b = -3; x = ([1:2:10 10.5 11.3])'; y = a*x; > c = tpaps(x,y,1); > * assert (a*ones(size(x)), tps_val_der(x,c,x), 1E3*eps); > [x1 x2] = meshgrid(x, x); > y1 = a*x1+b*x2; > c = tpaps([x1(:) x2(:)],y1(:),0.5); > dy = tps_val_der([x1(:) x2(:)],c,[x1(:) x2(:)]); > dy0 = tps_val_der([x1(:) x2(:)],c,[x1(:) x2(:)],false); > * assert (a*ones(size(x1(:))), dy(:, 1), 1E3*eps); > * assert (b*ones(size(x2(:))), dy(:, 2), 1E3*eps); > * assert (dy0, dy, 1E3*eps); > 4 tests, 4 passed, 0 known failure, 0 skipped > [inst/bin_values.m] > > /<>/inst/bin_values.m > * shared x, y, x_bin, y_bin, w_bin, n_bin > x = [1; 2; 2; 3; 4]; > y = [0 0; 1 1; 2 1; 3 4; 5 NaN]; > [x_bin y_bin w_bin n_bin] = bin_values(x, y); > * assert (x_bin, [1; 7/3]); > * assert (y_bin, [0 0; 2 2]); > * assert (!any(isfinite(w_bin(1, :; > * assert (w_bin(2, :), [3 1]); > * assert (n_bin, [1; 3]); > 5 tests, 5 passed, 0 known failure, 0 skipped > [inst/csaps_sel.m] > > /<>/inst/csaps_sel.m > * shared x,y,ret,p,sigma2,unc_y > x = [0:0.01:1]'; y = sin(x); > [ret,p,sigma2,unc_y] = csaps_sel(x,y,x); > malloc(): invalid size (unsorted) > fatal: caught signal Aborted -- stopping myself... > Aborted > make: *** [debian/rules:5: binary] Error 134 The full build log is available from: http://qa-logs.debian.net/2024/01/15/octave-splines_1.3.5-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1061015: pygame-sdl2: FTBFS: make: *** [debian/rules:6: binary] Error 25
Source: pygame-sdl2
Version: 8.1.3-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:305: python3.12 setup.py config
> /<>/setuplib.py:269: SyntaxWarning: invalid escape sequence '\('
> ccode = re.sub('Py_InitModule4\("([^"]+)"', 'Py_InitModule4("' +
> parent_module + '.\\1"', ccode) # Py2
>
> Error compiling Cython file:
>
> ...
> sf.base = base
> sf.length = length
> sf.tell = 0
>
> rv = SDL_AllocRW()
> rv.size = subfile_size
> ^
>
>
> src/pygame_sdl2/rwobject.pyx:336:22: Cannot assign type 'Sint64 (SDL_RWops *)
> except? -1 nogil' to 'Sint64 (*)(SDL_RWops *) noexcept'. Exception values are
> incompatible. Suggest adding 'noexcept' to type 'Sint64 (SDL_RWops *) except?
> -1 nogil'.
>
> Error compiling Cython file:
>
> ...
> sf.length = length
> sf.tell = 0
>
> rv = SDL_AllocRW()
> rv.size = subfile_size
> rv.seek = subfile_seek
> ^
>
>
> src/pygame_sdl2/rwobject.pyx:337:22: Cannot assign type 'Sint64 (SDL_RWops *,
> Sint64, int) except? -1 nogil' to 'Sint64 (*)(SDL_RWops *, Sint64, int)
> noexcept'. Exception values are incompatible. Suggest adding 'noexcept' to
> type 'Sint64 (SDL_RWops *, Sint64, int) except? -1 nogil'.
>
> Error compiling Cython file:
>
> ...
> sf.tell = 0
>
> rv = SDL_AllocRW()
> rv.size = subfile_size
> rv.seek = subfile_seek
> rv.read = subfile_read
> ^
>
>
> src/pygame_sdl2/rwobject.pyx:338:22: Cannot assign type 'size_t (SDL_RWops *,
> void *, size_t, size_t) except? -1 nogil' to 'size_t (*)(SDL_RWops *, void *,
> size_t, size_t) noexcept'. Exception values are incompatible. Suggest adding
> 'noexcept' to type 'size_t (SDL_RWops *, void *, size_t, size_t) except? -1
> nogil'.
>
> Error compiling Cython file:
>
> ...
> rv = SDL_AllocRW()
> rv.size = subfile_size
> rv.seek = subfile_seek
> rv.read = subfile_read
> rv.write = NULL
> rv.close = subfile_close
>^
>
>
> src/pygame_sdl2/rwobject.pyx:340:23: Cannot assign type 'int (SDL_RWops *)
> except? -1 nogil' to 'int (*)(SDL_RWops *) noexcept'. Exception values are
> incompatible. Suggest adding 'noexcept' to type 'int (SDL_RWops *) except? -1
> nogil'.
>
> Error compiling Cython file:
>
> ...
> raise IOError("{!r} is not a filename or file-like
> object.".format(filelike))
>
> Py_INCREF(filelike)
>
> rv = SDL_AllocRW()
> rv.size = python_size
> ^
>
>
> src/pygame_sdl2/rwobject.pyx:367:14: Cannot assign type 'Sint64 (SDL_RWops *)
> except? -1 nogil' to 'Sint64 (*)(SDL_RWops *) noexcept'. Exception values are
> incompatible. Suggest adding 'noexcept' to type 'Sint64 (SDL_RWops *) except?
> -1 nogil'.
>
> Error compiling Cython file:
>
> ...
>
> Py_INCREF(filelike)
>
> rv = SDL_AllocRW()
> rv.size = python_size
> rv.seek = python_seek
> ^
>
>
> src/pygame_sdl2/rwobject.pyx:368:14: Cannot assign type 'Sint64 (SDL_RWops *,
> Sint64, int) except? -1 nogil' to 'Sint64 (*)(SDL_RWops *, Sint64, int)
> noexcept'. Exception values are incompatible. Suggest adding 'noexcept' to
> type 'Sint64 (SDL_RWops *, Sint64, int) except? -1 nogil'.
>
> Error compiling Cython file:
>
> ...
> Py_INCREF(filelike)
>
> rv = SDL_AllocRW()
> rv.size = python_size
> rv.seek = python_seek
> rv.read = python_read
> ^
>
>
> src/pygame_sdl2/rwobject.pyx:369:14: Cannot assign type 'size_t (SDL_RWops *,
> void *, size_t, size_t) except? -1 nogil' to
Bug#1061014: apertium-isl-eng: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
Source: apertium-isl-eng Version: 0.1.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > apertium-regtest test > Corpus 1 of 2: isl-eng-pending > 0/219 (0.0%) tests pass > > Corpus 2 of 2: isl-eng-regression > 0/201 (0.0%) tests pass > > There were changes! Rerun in interactive mode to update tests. > Changed corpora: isl-eng-pending, isl-eng-regression > make[1]: *** [Makefile:788: test] Error 1 > make[1]: Leaving directory '/<>' > dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 > returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2024/01/15/apertium-isl-eng_0.1.2-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1061010: click: FTBFS: tests failed
Source: click Version: 0.5.0-9 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>' > set -e; for python in python3.12 python3; do \ > $python setup.py test; \ > done > /usr/lib/python3/dist-packages/setuptools/dist.py:508: InformationOnly: > Normalizing '0.5.0-9' to '0.5.0.post9' > self.metadata.version = self._normalize_version( > running test > WARNING: Testing via this command is deprecated and will be removed in a > future version. Users looking for a generic test entry point independent of > test runner are encouraged to use tox. > /usr/lib/python3/dist-packages/setuptools/command/test.py:193: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > ir_d = dist.fetch_build_eggs(dist.install_requires) > /usr/lib/python3/dist-packages/setuptools/command/test.py:194: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > tr_d = dist.fetch_build_eggs(dist.tests_require or []) > /usr/lib/python3/dist-packages/setuptools/command/test.py:195: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > er_d = dist.fetch_build_eggs( > running egg_info > creating click.egg-info > writing click.egg-info/PKG-INFO > writing dependency_links to click.egg-info/dependency_links.txt > writing top-level names to click.egg-info/top_level.txt > writing manifest file 'click.egg-info/SOURCES.txt' > reading manifest file 'click.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > adding license file 'LICENSE' > writing manifest file 'click.egg-info/SOURCES.txt' > running build_ext > /usr/lib/python3/dist-packages/setuptools/dist.py:508: InformationOnly: > Normalizing '0.5.0-9' to '0.5.0.post9' > self.metadata.version = self._normalize_version( > running test > WARNING: Testing via this command is deprecated and will be removed in a > future version. Users looking for a generic test entry point independent of > test runner are encouraged to use tox. > /usr/lib/python3/dist-packages/setuptools/command/test.py:193: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > ir_d = dist.fetch_build_eggs(dist.install_requires) > /usr/lib/python3/dist-packages/setuptools/command/test.py:194: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > tr_d = dist.fetch_build_eggs(dist.tests_require or []) > /usr/lib/python3/dist-packages/setuptools/command/test.py:195: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > er_d = dist.fetch_build_eggs( > running egg_info > writing click.egg-info/PKG-INFO > writing dependency_links to click.egg-info/dependency_links.txt >
Bug#1061008: aiohttp-jinja2: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Source: aiohttp-jinja2
Version: 1.5.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:305: python3.12 setup.py config
> running config
> I: pybuild base:305: python3.11 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3.12 setup.py build
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.12_aiohttp-jinja2/build/aiohttp_jinja2
> copying aiohttp_jinja2/__init__.py ->
> /<>/.pybuild/cpython3_3.12_aiohttp-jinja2/build/aiohttp_jinja2
> copying aiohttp_jinja2/typedefs.py ->
> /<>/.pybuild/cpython3_3.12_aiohttp-jinja2/build/aiohttp_jinja2
> copying aiohttp_jinja2/helpers.py ->
> /<>/.pybuild/cpython3_3.12_aiohttp-jinja2/build/aiohttp_jinja2
> running egg_info
> creating aiohttp_jinja2.egg-info
> writing aiohttp_jinja2.egg-info/PKG-INFO
> writing dependency_links to aiohttp_jinja2.egg-info/dependency_links.txt
> writing requirements to aiohttp_jinja2.egg-info/requires.txt
> writing top-level names to aiohttp_jinja2.egg-info/top_level.txt
> writing manifest file 'aiohttp_jinja2.egg-info/SOURCES.txt'
> reading manifest file 'aiohttp_jinja2.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'pytest.ini'
> warning: no directories found matching 'examples'
> warning: no previously-included files matching '*.pyc' found anywhere in
> distribution
> adding license file 'LICENSE'
> writing manifest file 'aiohttp_jinja2.egg-info/SOURCES.txt'
> copying aiohttp_jinja2/py.typed ->
> /<>/.pybuild/cpython3_3.12_aiohttp-jinja2/build/aiohttp_jinja2
> I: pybuild base:305: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.11_aiohttp-jinja2/build/aiohttp_jinja2
> copying aiohttp_jinja2/__init__.py ->
> /<>/.pybuild/cpython3_3.11_aiohttp-jinja2/build/aiohttp_jinja2
> copying aiohttp_jinja2/typedefs.py ->
> /<>/.pybuild/cpython3_3.11_aiohttp-jinja2/build/aiohttp_jinja2
> copying aiohttp_jinja2/helpers.py ->
> /<>/.pybuild/cpython3_3.11_aiohttp-jinja2/build/aiohttp_jinja2
> running egg_info
> writing aiohttp_jinja2.egg-info/PKG-INFO
> writing dependency_links to aiohttp_jinja2.egg-info/dependency_links.txt
> writing requirements to aiohttp_jinja2.egg-info/requires.txt
> writing top-level names to aiohttp_jinja2.egg-info/top_level.txt
> reading manifest file 'aiohttp_jinja2.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'pytest.ini'
> warning: no directories found matching 'examples'
> warning: no previously-included files matching '*.pyc' found anywhere in
> distribution
> adding license file 'LICENSE'
> writing manifest file 'aiohttp_jinja2.egg-info/SOURCES.txt'
> copying aiohttp_jinja2/py.typed ->
> /<>/.pybuild/cpython3_3.11_aiohttp-jinja2/build/aiohttp_jinja2
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:305: cd
> /<>/.pybuild/cpython3_3.12_aiohttp-jinja2/build; python3.12 -m
> pytest tests
> = test session starts
> ==
> platform linux -- Python 3.12.1, pytest-7.4.4, pluggy-1.3.0
> rootdir: /<>
> configfile: setup.cfg
> plugins: cov-4.1.0, anyio-4.1.0, asyncio-0.20.3, aiohttp-1.0.5
> asyncio: mode=Mode.AUTO
> collected 30 items
>
> tests/test_context_processors.py F [
> 16%]
> tests/test_jinja_filters.py F[
> 20%]
> tests/test_jinja_globals.py [
> 46%]
> tests/test_simple_renderer.py F.FF
> [100%]
>
> === FAILURES
> ===
> ___ test_context_processors
>
>
> aiohttp_client = .go at 0x7fe063cbfa60>
>
> async def test_context_processors(aiohttp_client):
> @aiohttp_jinja2.template("tmpl.jinja2")
> async def func(request):
> return {"bar": 2}
>
> app =
> web.Application(middlewares=[aiohttp_jinja2.context_processors_middleware])
> > aiohttp_jinja2.setup(
> app,
> loader=jinja2.DictLoader(
> {"tmpl.jinja2": "foo: {{ foo }}, bar: {{ bar }}, path: {{
> request.path }}"}
> ),
> )
>
> tests/test_context_processors.py:15:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> aiohttp_jinja2/__init__.py:82: in setup
> app[app_key] = env
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Bug#1061011: octave-zeromq: FTBFS: make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1
Source: octave-zeromq Version: 1.5.6-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > ( cd doc ;\ > texi2pdf -q zeromq.texi ; \ > makeinfo zeromq.texi ) > /usr/bin/texi2dvi: pdfetex exited with bad status, quitting. > zeromq.texi:17: @include: could not find version.texi > zeromq.texi:22: warning: undefined flag: VERSION > zeromq.texi:119: warning: undefined flag: VERSION > zeromq.texi:240: @include: could not find functions.texi > make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/01/15/octave-zeromq_1.5.6-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1061009: winff: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_build-arch] Error 2
Source: winff Version: 1.6.2+dfsg-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lazbuild --widgetset=qt5 -B winff/winff.lpr > CopySecondaryConfigFile /etc/lazarus/environmentoptions.xml -> > /<>/tmphome/.lazarus/environmentoptions.xml > Note: (lazarus) Invalid Package Link: file > "/usr/lib/lazarus/3.0/ide/packages/ideconfig/ideconfig.lpk" does not exist. > > $55A851D53B7A > $55A851D4EB65 > $55A851CAAF2E > $55A8522FC713 > $55A851E5EC83 > $55A851E491DE > $55A851E490D8 > $55A851CAF13D > $55A851CACD64 > $55A851CAB454 > $55A851CB0C93 > $55A851CB3979 > $55A851CD575C > Error: (lazbuild) Package file not found > The package "IdeConfig" is installed but no valid package file (.lpk) was > found. > A broken dummy package was created. > lazbuild is non interactive, aborting now. > make[1]: *** [debian/rules:16: override_dh_auto_build-arch] Error 2 The full build log is available from: http://qa-logs.debian.net/2024/01/15/winff_1.6.2+dfsg-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1061007: xeus-python: FTBFS: ./obj-x86_64-linux-gnu/./src/main.cpp:147:(.text.startup+0x5bd): undefined reference to `xeus::make_xserver_shell_main(xeus::xcontext&, xeus::xconfiguration const&, nl
Source: xeus-python Version: 0.15.10+~0.6.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: CMakeFiles/xpython.dir/src/main.cpp.o: in function `main': > ./obj-x86_64-linux-gnu/./src/main.cpp:147:(.text.startup+0x5bd): undefined > reference to `xeus::make_xserver_shell_main(xeus::xcontext&, > xeus::xconfiguration const&, > nlohmann::json_abi_v3_11_3::detail::error_handler_t)' > /usr/bin/ld: ./obj-x86_64-linux-gnu/./src/main.cpp:147:(.text.startup+0x5d7): > undefined reference to `xeus::xkernel::xkernel(xeus::xconfiguration const&, > std::__cxx11::basic_string, std::allocator > > const&, std::unique_ptr > >, std::unique_ptr std::default_delete >, std::unique_ptr std::default_delete > (*)(xeus::xcontext&, > xeus::xconfiguration const&, > nlohmann::json_abi_v3_11_3::detail::error_handler_t), > std::unique_ptr std::default_delete >, std::unique_ptr std::default_delete >, std::unique_ptr std::default_delete > (*)(xeus::xcontext&, > xeus::xconfiguration const&, std::__cxx11::basic_string std::char_traits, std::allocator > const&, > std::__cxx11::basic_string, std::allocator > > const&, nlohmann::json_abi_v3_11_3::basic_json std::__cxx11::basic_string, std::allocator > >, bool, long, unsigned long, double, std::allocator, > nlohmann::json_abi_v3_11_3::adl_serializer, std::vector std::allocator >, void> const&), > nlohmann::json_abi_v3_11_3::basic_json std::__cxx11::basic_string, std::allocator > >, bool, long, unsigned long, double, std::allocator, > nlohmann::json_abi_v3_11_3::adl_serializer, std::vector std::allocator >, void>, > nlohmann::json_abi_v3_11_3::detail::error_handler_t)' > /usr/bin/ld: ./obj-x86_64-linux-gnu/./src/main.cpp:166:(.text.startup+0x89b): > undefined reference to `xeus::make_xserver_shell_main(xeus::xcontext&, > xeus::xconfiguration const&, > nlohmann::json_abi_v3_11_3::detail::error_handler_t)' > /usr/bin/ld: ./obj-x86_64-linux-gnu/./src/main.cpp:166:(.text.startup+0x8d8): > undefined reference to > `xeus::xkernel::xkernel(std::__cxx11::basic_string std::char_traits, std::allocator > const&, > std::unique_ptr >, > std::unique_ptr > >, std::unique_ptr > > (*)(xeus::xcontext&, xeus::xconfiguration const&, > nlohmann::json_abi_v3_11_3::detail::error_handler_t), > std::unique_ptr std::default_delete >, std::unique_ptr std::default_delete >, std::unique_ptr std::default_delete > (*)(xeus::xcontext&, > xeus::xconfiguration const&, std::__cxx11::basic_string std::char_traits, std::allocator > const&, > std::__cxx11::basic_string, std::allocator > > const&, nlohmann::json_abi_v3_11_3::basic_json std::__cxx11::basic_string, std::allocator > >, bool, long, unsigned long, double, std::allocator, > nlohmann::json_abi_v3_11_3::adl_serializer, std::vector std::allocator >, void> const&), > nlohmann::json_abi_v3_11_3::basic_json std::__cxx11::basic_string, std::allocator > >, bool, long, unsigned long, double, std::allocator, > nlohmann::json_abi_v3_11_3::adl_serializer, std::vector std::allocator >, void>, > nlohmann::json_abi_v3_11_3::detail::error_handler_t)' > /usr/bin/ld: libxeus-python.so.0.15.10: undefined reference to > `xeus::xtarget::publish_message(std::__cxx11::basic_string std::char_traits, std::allocator > const&, > nlohmann::json_abi_v3_11_3::basic_json std::__cxx11::basic_string, std::allocator > >, bool, long, unsigned long, double, std::allocator, > nlohmann::json_abi_v3_11_3::adl_serializer, std::vector std::allocator >, void>, > nlohmann::json_abi_v3_11_3::basic_json std::__cxx11::basic_string, std::allocator > >, bool, long, unsigned long, double, std::allocator, > nlohmann::json_abi_v3_11_3::adl_serializer, std::vector std::allocator >, void>, std::vector std::allocator >, std::allocator > > > >) const' > /usr/bin/ld: libxeus-python.so.0.15.10: undefined reference to > `xeus::xinterpreter::update_display_data(nlohmann::json_abi_v3_11_3::basic_json std::vector, std::__cxx11::basic_string, > std::allocator >, bool, long, unsigned long, double, std::allocator, > nlohmann::json_abi_v3_11_3::adl_serializer, std::vector std::allocator >, void>, > nlohmann::json_abi_v3_11_3::basic_json std::__cxx11::basic_string, std::allocator > >, bool, long, unsigned long, double, std::allocator, > nlohmann::json_abi_v3_11_3::adl_serializer, std::vector std::allocator >, void>, > nlohmann::json_abi_v3_11_3::basic_json std::__cxx11::basic_string, std::allocator > >, bool, long, unsigned long, double, std::allocator, > nlohmann::json_abi_v3_11_3::adl_serializer, std::vector std::allocator >, void>)' > /usr/bin/ld: libxeus-python.so.0.15.10: undefined reference to > `xeus::xdap_tcp_client::forward_event(nlohmann::json_abi_v3_11_3::basic_json std::vector, std::__cxx11::basic_string, > std::allocator >, bool, long, unsigned long, double,
Bug#1061006: sphinxcontrib-bibtex: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Source: sphinxcontrib-bibtex Version: 2.6.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/doc' > sphinx-build -b html -d _build/doctrees . _build/html > Running Sphinx v7.2.6 > making output directory... done > loading intersphinx inventory from > /usr/share/doc/python3-doc/html/objects.inv... > loading intersphinx inventory from > /usr/share/doc/sphinx-doc/html/objects.inv... > building [mo]: targets for 0 po files that are out of date > writing output... > building [html]: targets for 17 source files that are out of date > updating environment: [new config] 17 added, 0 changed, 0 removed > [2Kreading sources... [ 6%] api > [2Kreading sources... [ 12%] api/bibfile > [2Kreading sources... [ 18%] api/directives > [2Kreading sources... [ 24%] api/domains > [2Kreading sources... [ 29%] api/interface > [2Kreading sources... [ 35%] api/nodes > [2Kreading sources... [ 41%] api/plugin > [2Kreading sources... [ 47%] api/pybtex > [2Kreading sources... [ 53%] api/referencing > [2Kreading sources... [ 59%] api/roles > [2Kreading sources... [ 65%] api/transforms > [2Kreading sources... [ 71%] changes > [2Kreading sources... [ 76%] index > [2Kreading sources... [ 82%] license > [2Kreading sources... [ 88%] quickstart > [2Kreading sources... [ 94%] related > [2Kreading sources... [100%] usage > > looking for now-outdated files... none found > pickling environment... done > checking consistency... done > preparing documents... done > copying assets... copying static files... done > copying extra files... done > done > [2Kwriting output... [ 6%] api > [2Kwriting output... [ 12%] api/bibfile > [2Kwriting output... [ 18%] api/directives > [2Kwriting output... [ 24%] api/domains > [2Kwriting output... [ 29%] api/interface > [2Kwriting output... [ 35%] api/nodes > [2Kwriting output... [ 41%] api/plugin > [2Kwriting output... [ 47%] api/pybtex > [2Kwriting output... [ 53%] api/referencing > [2Kwriting output... [ 59%] api/roles > [2Kwriting output... [ 65%] api/transforms > [2Kwriting output... [ 71%] changes > [2Kwriting output... [ 76%] index > [2Kwriting output... [ 82%] license > [2Kwriting output... [ 88%] quickstart > [2Kwriting output... [ 94%] related > [2Kwriting output... [100%] usage > > generating indices... genindex py-modindex done > [2Khighlighting module code... [ 4%] pybtex.style.template > [2Khighlighting module code... [ 9%] sphinxcontrib.bibtex > [2Khighlighting module code... [ 13%] sphinxcontrib.bibtex.bibfile > [2Khighlighting module code... [ 17%] sphinxcontrib.bibtex.directives > [2Khighlighting module code... [ 22%] sphinxcontrib.bibtex.domain > [2Khighlighting module code... [ 26%] sphinxcontrib.bibtex.foot_directives > [2Khighlighting module code... [ 30%] sphinxcontrib.bibtex.foot_domain > [2Khighlighting module code... [ 35%] sphinxcontrib.bibtex.foot_roles > [2Khighlighting module code... [ 39%] sphinxcontrib.bibtex.nodes > [2Khighlighting module code... [ 43%] sphinxcontrib.bibtex.plugin > [2Khighlighting module code... [ 48%] sphinxcontrib.bibtex.richtext > [2Khighlighting module code... [ 52%] sphinxcontrib.bibtex.roles > [2Khighlighting module code... [ 57%] sphinxcontrib.bibtex.style.names.last > [2Khighlighting module code... [ 61%] sphinxcontrib.bibtex.style.referencing > [2Khighlighting module code... [ 65%] > sphinxcontrib.bibtex.style.referencing.author_year > [2Khighlighting module code... [ 70%] > sphinxcontrib.bibtex.style.referencing.basic_author_year > [2Khighlighting module code... [ 74%] > sphinxcontrib.bibtex.style.referencing.basic_label > [2Khighlighting module code... [ 78%] > sphinxcontrib.bibtex.style.referencing.extra_author > [2Khighlighting module code... [ 83%] > sphinxcontrib.bibtex.style.referencing.extra_label > [2Khighlighting module code... [ 87%] > sphinxcontrib.bibtex.style.referencing.extra_year > [2Khighlighting module code... [ 91%] > sphinxcontrib.bibtex.style.referencing.label > [2Khighlighting module code... [ 96%] sphinxcontrib.bibtex.style.template > [2Khighlighting module code... [100%] sphinxcontrib.bibtex.transforms > > writing additional pages... search done > dumping search index in English (code: en)... done > dumping object inventory... done > build succeeded. > > The HTML pages are in _build/html. > > Build finished. The HTML pages are in _build/html. > make[2]: Leaving directory '/<>/doc' > make[1]: Leaving directory '/<>' >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:305: cd > /<>/.pybuild/cpython3_3.12_sphinxcontrib.bibtex/build; > python3.12 -m pytest "-k not test_citation_rinoh" > = test session starts > == > platform linux -- Python 3.12.1, pytest-7.4.4, pluggy-1.3.0
Bug#1061001: scikit-fmm: FTBFS: avx512pfintrin.h:180:3: error: ‘base’ may be used uninitialized [-Werror=maybe-uninitialized]
Source: scikit-fmm Version: 2022.08.15-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > cython3 --cplus -3 /<>/skfmm/pheap.pyx > dh_auto_configure > I: pybuild base:305: python3.12 setup.py config > /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:265: > UserWarning: Unknown distribution option: 'configuration' > warnings.warn(msg) > /usr/lib/python3/dist-packages/setuptools/dist.py:508: InformationOnly: > Normalizing '2022.08.15' to '2022.8.15' > self.metadata.version = self._normalize_version( > running config > I: pybuild base:305: python3.11 setup.py config > /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:265: > UserWarning: Unknown distribution option: 'configuration' > warnings.warn(msg) > /usr/lib/python3/dist-packages/setuptools/dist.py:508: InformationOnly: > Normalizing '2022.08.15' to '2022.8.15' > self.metadata.version = self._normalize_version( > running config > make[1]: Leaving directory '/<>' >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:305: /usr/bin/python3.12 setup.py build > /<>/setup.py:116: DeprecationWarning: > > `numpy.distutils` is deprecated since NumPy 1.23.0, as a result > of the deprecation of `distutils` itself. It will be removed for > Python >= 3.12. For older Python versions it will remain present. > It is recommended to use `setuptools < 60.0` for those Python versions. > For more details, see: > https://numpy.org/devdocs/reference/distutils_status_migration.html > > > from numpy.distutils.core import setup > /usr/lib/python3/dist-packages/setuptools/dist.py:508: InformationOnly: > Normalizing '2022.08.15' to '2022.8.15' > self.metadata.version = self._normalize_version( > running build > running config_cc > INFO: unifing config_cc, config, build_clib, build_ext, build commands > --compiler options > running config_fc > INFO: unifing config_fc, config, build_clib, build_ext, build commands > --fcompiler options > running build_src > INFO: build_src > INFO: building extension "skfmm.cfmm" sources > INFO: building extension "skfmm.pheap" sources > INFO: build_src: building npy-pkg config files > /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: > SetuptoolsDeprecationWarning: setup.py install is deprecated. > !! > > > > Please avoid running ``setup.py`` directly. > Instead, use pypa/build, pypa/installer or other > standards-based tools. > > See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html > for details. > > > > !! > self.initialize_options() > running build_py > creating /<>/.pybuild/cpython3_3.12_scikit-fmm/build/skfmm > copying skfmm/__init__.py -> > /<>/.pybuild/cpython3_3.12_scikit-fmm/build/skfmm > copying skfmm/setup.py -> > /<>/.pybuild/cpython3_3.12_scikit-fmm/build/skfmm > copying skfmm/heap.py -> > /<>/.pybuild/cpython3_3.12_scikit-fmm/build/skfmm > copying skfmm/pfmm.py -> > /<>/.pybuild/cpython3_3.12_scikit-fmm/build/skfmm > running build_ext > INFO: customize UnixCCompiler > INFO: customize UnixCCompiler using build_ext > INFO: CCompilerOpt.cc_test_flags[1077] : testing flags (-march=native) > INFO: C compiler: x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare > -DNDEBUG -g -O2 -Wall -g -fstack-protector-strong -fstack-clash-protection > -Wformat -Werror=format-security -fcf-protection -g -fwrapv -O2 > -I/usr/include/python3.11 -I/usr/include/python3.11 -Wsign-compare -g > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -DNDEBUG -g -fwrapv -O2 -Wall > -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC > > creating /tmp/tmp4j7s8560/usr > creating /tmp/tmp4j7s8560/usr/lib > creating /tmp/tmp4j7s8560/usr/lib/python3 > creating /tmp/tmp4j7s8560/usr/lib/python3/dist-packages > creating /tmp/tmp4j7s8560/usr/lib/python3/dist-packages/numpy > creating /tmp/tmp4j7s8560/usr/lib/python3/dist-packages/numpy/distutils > creating /tmp/tmp4j7s8560/usr/lib/python3/dist-packages/numpy/distutils/checks > INFO: compile options: '-I/usr/include/python3.12 -c' > extra options: '-march=native' > INFO: CCompilerOpt.cc_test_flags[1077] : testing flags (-O3) > INFO: C compiler: x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare > -DNDEBUG -g -O2 -Wall -g -fstack-protector-strong -fstack-clash-protection > -Wformat -Werror=format-security -fcf-protection -g -fwrapv -O2 > -I/usr/include/python3.11 -I/usr/include/python3.11 -Wsign-compare -g > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -DNDEBUG -g -fwrapv -O2
Bug#1061004: guestfs-tools: FTBFS: make[6]: *** [Makefile:1723: test-suite.log] Error 1
Source: guestfs-tools Version: 1.52.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[6]: Entering directory '/<>/builder' > PASS: test-docs.sh > FAIL: test-virt-builder-cacheall.sh > FAIL: test-virt-builder-list.sh > PASS: test-virt-index-validate.sh > rm -f test-console-centos-7.2.sh test-console-centos-7.2.sh-t > f=`echo "test-console-centos-7.2.sh" | /usr/bin/sed > 's/test-console-\(.*\).sh/\1/'`; \ > echo 'script=test-console-centos-7.2.sh exec $srcdir/test-console.sh' "$f" > > test-console-centos-7.2.sh-t > chmod 0755 test-console-centos-7.2.sh-t > mv test-console-centos-7.2.sh-t test-console-centos-7.2.sh > SKIP: test-console-centos-7.2.sh > rm -f test-console-rhel-6.8.sh test-console-rhel-6.8.sh-t > f=`echo "test-console-rhel-6.8.sh" | /usr/bin/sed > 's/test-console-\(.*\).sh/\1/'`; \ > echo 'script=test-console-rhel-6.8.sh exec $srcdir/test-console.sh' "$f" > > test-console-rhel-6.8.sh-t > chmod 0755 test-console-rhel-6.8.sh-t > mv test-console-rhel-6.8.sh-t test-console-rhel-6.8.sh > SKIP: test-console-rhel-6.8.sh > rm -f test-console-rhel-7.2.sh test-console-rhel-7.2.sh-t > f=`echo "test-console-rhel-7.2.sh" | /usr/bin/sed > 's/test-console-\(.*\).sh/\1/'`; \ > echo 'script=test-console-rhel-7.2.sh exec $srcdir/test-console.sh' "$f" > > test-console-rhel-7.2.sh-t > chmod 0755 test-console-rhel-7.2.sh-t > mv test-console-rhel-7.2.sh-t test-console-rhel-7.2.sh > SKIP: test-console-rhel-7.2.sh > rm -f test-console-debian-7.sh test-console-debian-7.sh-t > f=`echo "test-console-debian-7.sh" | /usr/bin/sed > 's/test-console-\(.*\).sh/\1/'`; \ > echo 'script=test-console-debian-7.sh exec $srcdir/test-console.sh' "$f" > > test-console-debian-7.sh-t > chmod 0755 test-console-debian-7.sh-t > mv test-console-debian-7.sh-t test-console-debian-7.sh > SKIP: test-console-debian-7.sh > rm -f test-console-debian-8.sh test-console-debian-8.sh-t > f=`echo "test-console-debian-8.sh" | /usr/bin/sed > 's/test-console-\(.*\).sh/\1/'`; \ > echo 'script=test-console-debian-8.sh exec $srcdir/test-console.sh' "$f" > > test-console-debian-8.sh-t > chmod 0755 test-console-debian-8.sh-t > mv test-console-debian-8.sh-t test-console-debian-8.sh > SKIP: test-console-debian-8.sh > rm -f test-console-fedora-24.sh test-console-fedora-24.sh-t > f=`echo "test-console-fedora-24.sh" | /usr/bin/sed > 's/test-console-\(.*\).sh/\1/'`; \ > echo 'script=test-console-fedora-24.sh exec $srcdir/test-console.sh' "$f" > > test-console-fedora-24.sh-t > chmod 0755 test-console-fedora-24.sh-t > mv test-console-fedora-24.sh-t test-console-fedora-24.sh > SKIP: test-console-fedora-24.sh > rm -f test-console-ubuntu-12.04.sh test-console-ubuntu-12.04.sh-t > f=`echo "test-console-ubuntu-12.04.sh" | /usr/bin/sed > 's/test-console-\(.*\).sh/\1/'`; \ > echo 'script=test-console-ubuntu-12.04.sh exec $srcdir/test-console.sh' "$f" > > test-console-ubuntu-12.04.sh-t > chmod 0755 test-console-ubuntu-12.04.sh-t > mv test-console-ubuntu-12.04.sh-t test-console-ubuntu-12.04.sh > SKIP: test-console-ubuntu-12.04.sh > rm -f test-console-ubuntu-14.04.sh test-console-ubuntu-14.04.sh-t > f=`echo "test-console-ubuntu-14.04.sh" | /usr/bin/sed > 's/test-console-\(.*\).sh/\1/'`; \ > echo 'script=test-console-ubuntu-14.04.sh exec $srcdir/test-console.sh' "$f" > > test-console-ubuntu-14.04.sh-t > chmod 0755 test-console-ubuntu-14.04.sh-t > mv test-console-ubuntu-14.04.sh-t test-console-ubuntu-14.04.sh > SKIP: test-console-ubuntu-14.04.sh > rm -f test-console-ubuntu-16.04.sh test-console-ubuntu-16.04.sh-t > f=`echo "test-console-ubuntu-16.04.sh" | /usr/bin/sed > 's/test-console-\(.*\).sh/\1/'`; \ > echo 'script=test-console-ubuntu-16.04.sh exec $srcdir/test-console.sh' "$f" > > test-console-ubuntu-16.04.sh-t > chmod 0755 test-console-ubuntu-16.04.sh-t > mv test-console-ubuntu-16.04.sh-t test-console-ubuntu-16.04.sh > SKIP: test-console-ubuntu-16.04.sh > rm -f test-console-ubuntu-18.04.sh test-console-ubuntu-18.04.sh-t > f=`echo "test-console-ubuntu-18.04.sh" | /usr/bin/sed > 's/test-console-\(.*\).sh/\1/'`; \ > echo 'script=test-console-ubuntu-18.04.sh exec $srcdir/test-console.sh' "$f" > > test-console-ubuntu-18.04.sh-t > chmod 0755 test-console-ubuntu-18.04.sh-t > mv test-console-ubuntu-18.04.sh-t test-console-ubuntu-18.04.sh > SKIP: test-console-ubuntu-18.04.sh > rm -f test-console-ubuntu-20.04.sh test-console-ubuntu-20.04.sh-t > f=`echo "test-console-ubuntu-20.04.sh" | /usr/bin/sed > 's/test-console-\(.*\).sh/\1/'`; \ > echo 'script=test-console-ubuntu-20.04.sh exec $srcdir/test-console.sh' "$f" > > test-console-ubuntu-20.04.sh-t > chmod 0755 test-console-ubuntu-20.04.sh-t > mv test-console-ubuntu-20.04.sh-t test-console-ubuntu-20.04.sh > SKIP: test-console-ubuntu-20.04.sh > SKIP: test-virt-builder-planner.sh > SKIP: test-virt-builder-repository.sh >
Bug#1061002: python-flask-httpauth: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Source: python-flask-httpauth
Version: 4.5.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:305: /usr/bin/python3.12 setup.py build
> running build
> running build_py
> copying src/flask_httpauth.py ->
> /<>/.pybuild/cpython3_3.12_flask-httpauth/build
> running egg_info
> creating src/Flask_HTTPAuth.egg-info
> writing src/Flask_HTTPAuth.egg-info/PKG-INFO
> writing dependency_links to src/Flask_HTTPAuth.egg-info/dependency_links.txt
> writing requirements to src/Flask_HTTPAuth.egg-info/requires.txt
> writing top-level names to src/Flask_HTTPAuth.egg-info/top_level.txt
> writing manifest file 'src/Flask_HTTPAuth.egg-info/SOURCES.txt'
> reading manifest file 'src/Flask_HTTPAuth.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> adding license file 'AUTHORS'
> writing manifest file 'src/Flask_HTTPAuth.egg-info/SOURCES.txt'
> I: pybuild base:305: /usr/bin/python3 setup.py build
> running build
> running build_py
> copying src/flask_httpauth.py ->
> /<>/.pybuild/cpython3_3.11_flask-httpauth/build
> running egg_info
> writing src/Flask_HTTPAuth.egg-info/PKG-INFO
> writing dependency_links to src/Flask_HTTPAuth.egg-info/dependency_links.txt
> writing requirements to src/Flask_HTTPAuth.egg-info/requires.txt
> writing top-level names to src/Flask_HTTPAuth.egg-info/top_level.txt
> reading manifest file 'src/Flask_HTTPAuth.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> adding license file 'AUTHORS'
> writing manifest file 'src/Flask_HTTPAuth.egg-info/SOURCES.txt'
> PYTHONPATH=. python3 -m sphinx -N -bhtml docs/ build/html # HTML generator
> Running Sphinx v7.2.6
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> writing output...
> building [html]: targets for 1 source files that are out of date
> updating environment: [new config] 1 added, 0 changed, 0 removed
> [2Kreading sources... [100%] index
>
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> copying assets... copying static files... done
> copying extra files... done
> done
> [2Kwriting output... [100%] index
>
> generating indices... genindex py-modindex done
> writing additional pages... search done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded.
>
> The HTML pages are in build/html.
> PYTHONPATH=. python3 -m sphinx -N -bman docs/ build/man # Manpage generator
> Running Sphinx v7.2.6
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> writing output...
> building [man]: all manpages
> updating environment: [new config] 1 added, 0 changed, 0 removed
> [2Kreading sources... [100%] index
>
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> writing... flask-httpauth.3 { } done
> build succeeded.
>
> The manual pages are in build/man.
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:305: cd
> /<>/.pybuild/cpython3_3.12_flask-httpauth/build; python3.12 -m
> pytest tests
> = test session starts
> ==
> platform linux -- Python 3.12.1, pytest-7.4.4, pluggy-1.3.0
> rootdir: /<>
> collected 108 items
>
> tests/test_basic_custom_realm.py ... [
> 2%]
> tests/test_basic_get_password.py . [
> 7%]
> tests/test_basic_hashed_password.py ... [
> 10%]
> tests/test_basic_verify_password.py [
> 17%]
> tests/test_basic_verify_password_async.py [
> 25%]
> tests/test_digest_custom_realm.py .. [
> 26%]
> tests/test_digest_get_password.py ...[
> 33%]
> tests/test_digest_ha1_password.py . [
> 34%]
> tests/test_error_responses.py . [
> 35%]
> tests/test_multi.py FF.. [
> 46%]
> tests/test_multi_async.py FF.. [
> 57%]
> tests/test_roles.py .. [
> 66%]
> tests/test_roles_async.py .. [
> 75%]
> tests/test_token.py ..FF.[
> 87%]
> tests/test_token_async.py ..FF.
> [100%]
>
> === FAILURES
Bug#1060994: libshumate: FTBFS: make: *** [debian/rules:9: binary] Error 25
Source: libshumate
Version: 1.1.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- -Dauto_features=enabled
> cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8
> meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr
> --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu
> -Dpython.bytecompile=-1 -Dauto_features=enabled
> The Meson build system
> Version: 1.3.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: libshumate
> Project version: 1.1.2
> C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-9) 13.2.0")
> C linker for the host machine: cc ld.bfd 2.41.50.20231227
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Library m found: YES
> Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1
> Run-time dependency glib-2.0 found: YES 2.78.3
> Run-time dependency gobject-2.0 found: YES 2.78.3
> Run-time dependency gio-2.0 found: YES 2.78.3
> Run-time dependency cairo found: YES 1.18.0
> Run-time dependency sqlite3 found: YES 3.44.2
> Run-time dependency gtk4 found: YES 4.12.4
> Run-time dependency libsoup-3.0 found: YES 3.4.4
> Run-time dependency gobject-introspection-1.0 found: YES 1.78.1
> Run-time dependency vapigen found: YES 0.56.14
> Run-time dependency sysprof-capture-4 found: YES 45.1
> Build-time dependency gi-docgen found: YES 2023.3
> Program gi-docgen found: YES (/usr/bin/gi-docgen)
> Dependency gio-2.0 found: YES 2.78.3 (cached)
> Program /usr/bin/glib-compile-resources found: YES
> (/usr/bin/glib-compile-resources)
> Configuring shumate-version.h using configuration
> Dependency glib-2.0 found: YES 2.78.3 (cached)
> Program /usr/bin/glib-genmarshal found: YES (/usr/bin/glib-genmarshal)
> Dependency glib-2.0 found: YES 2.78.3 (cached)
> Program /usr/bin/glib-mkenums found: YES (/usr/bin/glib-mkenums)
> Dependency glib-2.0 found: YES 2.78.3 (cached)
> Program /usr/bin/glib-mkenums found: YES (/usr/bin/glib-mkenums)
> ../shumate/meson.build:213: WARNING: Project targets '>= 0.53.0' but uses
> feature introduced in '0.55.0': fatal_warnings arg in gnome.generate_gir.
> Dependency gobject-introspection-1.0 found: YES 1.78.1 (cached)
> Dependency gobject-introspection-1.0 found: YES 1.78.1 (cached)
> Program /usr/bin/x86_64-linux-gnu-g-ir-scanner found: YES
> (/usr/bin/x86_64-linux-gnu-g-ir-scanner)
> Dependency gobject-introspection-1.0 found: YES 1.78.1 (cached)
> Program /usr/bin/x86_64-linux-gnu-g-ir-compiler found: YES
> (/usr/bin/x86_64-linux-gnu-g-ir-compiler)
> Program vapigen found: YES (/usr/bin/vapigen)
> Program msgfmt found: YES (/usr/bin/msgfmt)
> Program msginit found: YES (/usr/bin/msginit)
> Program msgmerge found: YES (/usr/bin/msgmerge)
> Program xgettext found: YES (/usr/bin/xgettext)
> Configuring libshumate.toml using configuration
> Dependency gio-2.0 found: YES 2.78.3 (cached)
> Program /usr/bin/glib-compile-resources found: YES
> (/usr/bin/glib-compile-resources)
> Program valgrind found: NO
> Message:
> --
> libshumate 1.1.2 (1.0)
>
> Demos: false
> Documentation: true
> Introspection: true
> Vala API: true
>
> Directories:
>prefix: /usr
>includedir: /usr/include
>libdir: /usr/lib/x86_64-linux-gnu
> datadir: /usr/share
> --
> Build targets in project: 69
> WARNING: Project specifies a minimum meson_version '>= 0.53.0' but uses
> features which were added in newer versions:
> * 0.55.0: {'fatal_warnings arg in gnome.generate_gir'}
>
> libshumate 1.1.2
>
> User defined options
> auto_features : enabled
> buildtype : plain
> libdir: lib/x86_64-linux-gnu
> localstatedir : /var
> prefix: /usr
> sysconfdir: /etc
> wrap_mode : nodownload
> python.bytecompile: -1
>
> Found ninja-1.11.1 at /usr/bin/ninja
> make[1]: Leaving directory '/<>'
>dh_auto_build
> cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j8 -v
> [1/124] /usr/bin/glib-compile-resources ../data/libshumate.gresource.xml
> --sourcedir ../data --c-name shumate --internal --generate --target
> data/shumate-resources.h
> xml-stripblanks preprocessing requested, but XMLLINT is not set, and xmllint
> is not in PATH
> [2/124] /usr/bin/glib-compile-resources ../data/libshumate.gresource.xml
> --sourcedir ../data --c-name shumate --internal --generate --target
> data/shumate-resources.c --dependency-file data/shumate-resources.c.d
> xml-stripblanks preprocessing requested, but XMLLINT is not set, and xmllint
> is not in PATH
> [3/124] /usr/bin/msgfmt -o po/ab/LC_MESSAGES/shumate1.mo ../po/ab.po
> [4/124] /usr/bin/msgfmt -o po/ca/LC_MESSAGES/shumate1.mo
Bug#1061000: dqlite: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
Source: dqlite Version: 1.16.0-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>' > PASS: unit-test > FAIL: integration-test > >libdqlite 1.16.0: ./test-suite.log > > > # TOTAL: 2 > # PASS: 1 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > .. contents:: :depth: 2 > > FAIL: integration-test > == > > Running test suite with seed 0x48146ffc... > client/exec > disk_mode=0 [ OK] [ > 0.00848620 / 0.00474892 CPU ] > disk_mode=1 [ OK] [ > 0.00903412 / 0.00310910 CPU ] > client/execWithOneParam > disk_mode=0 [ OK] [ > 0.01107855 / 0.00322604 CPU ] > disk_mode=1 [ OK] [ > 0.01084037 / 0.00271260 CPU ] > client/execSql > disk_mode=0 [ OK] [ > 0.00588297 / 0.00149010 CPU ] > disk_mode=1 [ OK] [ > 0.00743165 / 0.00155657 CPU ] > client/query > disk_mode=0 [ OK] [ > 0.04957668 / 0.02712912 CPU ] > disk_mode=1 [ OK] [ > 0.02748792 / 0.01775024 CPU ] > client/querySql > disk_mode=0 [ OK] [ > 0.03543575 / 0.02319791 CPU ] > disk_mode=1 [ OK] [ > 0.03526996 / 0.01552904 CPU ] > cluster/restart > num_records=0, disk_mode=0[ OK] [ > 0.09370341 / 0.02169809 CPU ] > num_records=0, disk_mode=1[ OK] [ > 0.12578984 / 0.02156978 CPU ] > num_records=1, disk_mode=0[ OK] [ > 0.08911703 / 0.02158624 CPU ] > num_records=1, disk_mode=1[ OK] [ > 0.10179450 / 0.02262160 CPU ] > num_records=256, disk_mode=0 [ OK] [ > 1.33302500 / 0.36639435 CPU ] > num_records=256, disk_mode=1 [ OK] [ > 1.09571285 / 0.30773684 CPU ] > num_records=993, disk_mode=0 [ OK] [ > 4.43455608 / 1.49089326 CPU ] > num_records=993, disk_mode=1 [ OK] [ > 4.07793608 / 1.49977670 CPU ] > num_records=2200, disk_mode=0 [ OK] [ > 9.31523289 / 2.74274570 CPU ] > num_records=2200, disk_mode=1 [ OK] [ > 8.22212519 / 2.03489432 CPU ] > cluster/dataOnNewNode > num_records=0, disk_mode=0[ OK] [ > 1.02777129 / 0.01749712 CPU ] > num_records=0, disk_mode=1[ OK] [ > 1.02522202 / 0.01251844 CPU ] > num_records=1, disk_mode=0[ OK] [ > 1.04220156 / 0.01379738 CPU ] > num_records=1, disk_mode=1[ OK] [ > 1.02847857 / 0.01512479 CPU ] > num_records=256, disk_mode=0 [ OK] [ > 1.93572853 / 0.23575930 CPU ] > num_records=256, disk_mode=1 [ OK] [ > 2.27937617 / 0.42763899 CPU ] > num_records=993, disk_mode=0 [ ERROR ] > Error: test/integration/test_cluster.c:165: assertion failed: rv_ == 0 (1 == > 0) > Error: child killed by signal 6 (Aborted) > num_records=993, disk_mode=1 [ OK] [ > 5.01102442 / 1.52215910 CPU ] > num_records=2200, disk_mode=0 [ OK] [ > 9.22951190 / 2.42304560 CPU ] > num_records=2200, disk_mode=1 [ OK] [ > 9.26020030 / 2.42893808 CPU ] > cluster/hugeRow [ OK] [ > 0.82882703 / 0.50905253 CPU ] > cluster/modifyingQuery > num_records=0, disk_mode=0[ OK] [ > 1.02560865 / 0.01266010 CPU ] > num_records=0, disk_mode=1[ OK] [ > 1.02765664 / 0.01314657 CPU ] > num_records=1, disk_mode=0[ OK] [ > 1.02474720 / 0.01152366 CPU ] > num_records=1, disk_mode=1
Bug#1060996: h5z-zfp: FTBFS: H5Dcreate failed at line 489, errno=2 (No such file or directory)
Source: h5z-zfp Version: 1.1.0+git20221021-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/src' > make[3]: Nothing to be done for 'plugin'. > make[3]: Leaving directory '/<>/src' > x86_64-linux-gnu-gcc -c test_write.c -o test_write_plugin.o > -DH5Z_ZFP_USE_PLUGIN -DZFP_LIB_VERSION=0x1010 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I../src -I/usr/include > -I/usr/include/hdf5/serial > x86_64-linux-gnu-gcc test_write_plugin.o -o test_write_plugin -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC > -Wl,-rpath,/usr/lib/x86_64-linux-gnu/hdf5/serial -Wl,-rpath,/usr/lib > -L/usr/lib/x86_64-linux-gnu/hdf5/serial -L/usr/lib -lhdf5 -lzfp -lm > -Wl,-z,relro > > ./test_write_plugin zfpmode=1 rate=32 ...HDF5-DIAG: Error > detected in HDF5 (1.10.10) thread 1: > #000: ../../../src/H5D.c line 140 in H5Dcreate2(): unable to create dataset > major: Dataset > minor: Unable to initialize object > #001: ../../../src/H5Dint.c line 328 in H5D__create_named(): unable to > create and link to dataset > major: Dataset > minor: Unable to initialize object > #002: ../../../src/H5L.c line 1542 in H5L_link_object(): unable to create > new link to object > major: Links > minor: Unable to initialize object > #003: ../../../src/H5L.c line 1785 in H5L__create_real(): can't insert link > major: Links > minor: Unable to insert object > #004: ../../../src/H5Gtraverse.c line 830 in H5G_traverse(): internal path > traversal failed > major: Symbol table > minor: Object not found > #005: ../../../src/H5Gtraverse.c line 607 in H5G__traverse_real(): > traversal operator failed > major: Symbol table > minor: Callback failed > #006: ../../../src/H5L.c line 1590 in H5L__link_cb(): unable to create > object > major: Links > minor: Unable to initialize object > #007: ../../../src/H5Oint.c line 2459 in H5O_obj_create(): unable to open > object > major: Object header > minor: Can't open object > #008: ../../../src/H5Doh.c line 287 in H5O__dset_create(): unable to create > dataset > major: Dataset > minor: Unable to initialize object > #009: ../../../src/H5Dint.c line 1196 in H5D__create(): I/O filters can't > operate on this dataset > major: Invalid arguments to routine > minor: Unable to initialize object > #010: ../../../src/H5Z.c line 891 in H5Z_can_apply(): unable to apply filter > major: Data filters > minor: Error from filter 'can apply' callback > #011: ../../../src/H5Z.c line 852 in H5Z__prepare_prelude_callback_dcpl(): > unable to apply filter > major: Data filters > minor: Error from filter 'can apply' callback > #012: ../../../src/H5Z.c line 753 in H5Z__prelude_callback(): error during > user callback > major: Data filters > minor: Error from filter 'can apply' callback > #013: H5Zzfp.c line 158 in H5Z_zfp_can_apply(): ZFP lib not compiled with > -DBIT_STREAM_WORD_TYPE=uint8 > major: Data filters > minor: Unable to initialize object > H5Dcreate failed at line 489, errno=2 (No such file or directory) > [[31;01mFAILED[0m] > ./test_write_plugin zfpmode=1 rate=16 ...HDF5-DIAG: Error > detected in HDF5 (1.10.10) thread 1: > #000: ../../../src/H5D.c line 140 in H5Dcreate2(): unable to create dataset > major: Dataset > minor: Unable to initialize object > #001: ../../../src/H5Dint.c line 328 in H5D__create_named(): unable to > create and link to dataset > major: Dataset > minor: Unable to initialize object > #002: ../../../src/H5L.c line 1542 in H5L_link_object(): unable to create > new link to object > major: Links > minor: Unable to initialize object > #003: ../../../src/H5L.c line 1785 in H5L__create_real(): can't insert link > major: Links > minor: Unable to insert object > #004: ../../../src/H5Gtraverse.c line 830 in H5G_traverse(): internal path > traversal failed > major: Symbol table > minor: Object not found > #005: ../../../src/H5Gtraverse.c line 607 in H5G__traverse_real(): > traversal operator failed > major: Symbol table > minor: Callback failed > #006: ../../../src/H5L.c line 1590 in H5L__link_cb(): unable to create > object > major: Links > minor: Unable to initialize object > #007: ../../../src/H5Oint.c line 2459 in H5O_obj_create(): unable to open > object > major: Object header > minor: Can't open object > #008: ../../../src/H5Doh.c line 287 in H5O__dset_create():
Bug#1060999: octave-sockets: FTBFS: make: *** [debian/rules:5: binary] Error 25
Source: octave-sockets
Version: 1.4.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>/src'
> /usr/bin/mkoctfile --verbose socket.cc
> g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -I/usr/include/octave-8.4.0/octave/.. -I/usr/include/octave-8.4.0/octave
> -pthread -fopenmp -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protectionsocket.cc -o /tmp/oct-DW4tFF.o
> Extracting tests from socket.cc ...
> g++ -I/usr/include/octave-8.4.0/octave/.. -I/usr/include/octave-8.4.0/octave
> -pthread -fopenmp -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -o socket.oct /tmp/oct-DW4tFF.o
> -shared -Wl,-Bsymbolic -Wl,-z,relro -L/usr/lib/x86_64-linux-gnu -shared
> -Wl,-Bsymbolic -flto=auto -ffat-lto-objects -Wl,-z,relro
> make[1]: Leaving directory '/<>/src'
> copyfile /<>/./src/socket.oct
> /<>/./src/socket.cc-tst
> /<>/./inst/x86_64-pc-linux-gnu-api-v58
> For information about changes from previous versions of the sockets package,
> run 'news sockets'.
>dh_octave_check -O--buildsystem=octave
> Checking package...
> Run the unit tests...
> Checking m files ...
> Checking C++ files ...
> [src/socket.cc]
> > /<>/src/socket.cc
> * test
> ## Server socket
> server = socket (AF_INET, SOCK_STREAM, 0);
> assert (server >= 0);
>
> rc = bind (server, 9001);
> assert (rc, 0);
>
> rc = listen (server, 1);
> assert (rc, 0);
>
> ## Client socket
> client = socket (AF_INET, SOCK_STREAM, 0);
> assert (client >= 0);
>
> ## Create the connection and accept the connection
> server_info = struct ("addr", "127.0.0.1", "port", 9001);
> rc = connect (client, server_info);
> assert (rc, 0);
>
> server_data = accept (server);
> assert (server_data >= 0);
>
> ## Send and receive data
>
> ## Send as string from client
> msg = "Hello socket-land!";
> rc = send (client, msg);
> assert (rc,length (msg));
>
> ## Receive at server
> [msg_s, len_s] = recv (server_data, 100);
> assert (msg_s != -1);
> assert (len_s, length (msg));
>
> ## Send back out from server
> rc = send (server_data, msg_s);
> assert (rc, length (msg_s));
>
> ## Receive at client
> [msg_c, len_c] = recv (client, 100);
> assert (msg_c != -1);
> assert (len_c, length (msg));
>
> ## Compare original string with recv string
> assert (msg, num2str (msg_c, "%c"));
>
> assert (shutdown (client, SHUT_WR), 0);
> assert (shutdown (client, SHUT_RD), 0);
> assert (shutdown (client, SHUT_RDWR), 0);
>
> assert (disconnect (client), 0);
> assert (disconnect (server_data), 0);
> assert (disconnect (server), 0);
> * test
> ## UDP
> sock = socket (AF_INET, SOCK_DGRAM, 0);
> assert (sock >= 0);
>
> rc = bind (sock, 9001);
> assert (rc, 0);
>
> msg = "Hello socket-land!";
> addrinfo = struct ("addr", "127.0.0.1", "port", 9001);
> rc = sendto (sock, msg, 0, addrinfo);
> assert (rc,length (msg));
>
> [msg_c, len_c, addr_c] = recvfrom (sock, 100);
> assert (msg_c != -1);
> assert (len_c, length (msg));
> assert (addr_c.port, 9001);
>
> assert (msg, num2str (msg_c, "%c"));
>
> assert (disconnect (sock), 0);
> * test
> assert (SOL_SOCKET != 0)
> assert (MSG_WAITALL != 0)
> assert (MSG_PEEK != 0)
> assert (SO_REUSEADDR != 0)
> assert (SO_KEEPALIVE != 0)
> assert (SO_TYPE != 0)
> assert (SHUT_RD, 0)
> assert (SHUT_WR, 1)
> assert (SHUT_RDWR, 2)
> * test
> ## select
> sock = socket (AF_INET, SOCK_DGRAM, 0);
> assert (sock >= 0);
>
> rc = bind (sock, 9001);
> assert (rc, 0);
>
> [ret, rdfs, wdfs, edfs] = select(sock+1, [sock], [sock], [sock], 1);
> assert(ret, 1);
> assert(rdfs, []);
> # initial open
> assert(wdfs, [sock]);
> assert(edfs, []);
>
> msg = "Hello socket-land!";
> addrinfo = struct ("addr", "127.0.0.1", "port", 9001);
> rc = sendto (sock, msg, 0, addrinfo);
> assert (rc,length (msg));
> pause(1);
>
> [ret, rdfs, wdfs, edfs] = select(sock+1, [sock], [], [], .2);
> assert(ret, 1);
> assert(rdfs, [sock]);
> assert(wdfs, []);
> assert(edfs, []);
>
> [msg_c, len_c, addr_c] = recvfrom (sock, 100);
> assert (msg_c != -1);
> assert (len_c, length (msg));
> assert (addr_c.port, 9001);
>
> [ret, rdfs, wdfs, edfs] = select(sock+1, [sock], [], [], .1);
> assert(ret, 0);
> assert(rdfs, []);
> assert(wdfs, []);
> assert(edfs, []);
>
> assert (disconnect (sock), 0);
>
> * xtest
> sock = socket (AF_INET, SOCK_DGRAM, 0);
> assert (sock >= 0);
>
> start = tic;
> [ret, rdfs, wdfs, edfs] = select(sock+1, [sock], [], [], 1);
> timeout = toc(start);
> assert(ret, 0);
> assert(rdfs, []);
> assert(wdfs, []);
> assert(edfs, []);
> assert(timeout, 1, 0.01);
>
Bug#1060998: cthreadpool: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
Source: cthreadpool Version: 0.0+git20201207.b259a6e-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > 1/10 > 2/10 > 3/10 > 4/10 > 5/10 > 6/10 > 7/10 > 8/10 > 9/10 > 10/10 > > Testing multiple threads creation and destruction in pool(threads=3 times=20) > 1/20 > 2/20 > 3/20 > E: Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://qa-logs.debian.net/2024/01/15/cthreadpool_0.0+git20201207.b259a6e-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1060997: khard: FTBFS: make[2]: *** [Makefile:20: html] Error 2
Source: khard Version: 0.19.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/doc' > Running Sphinx v7.2.6 > making output directory... done > /usr/lib/python3/dist-packages/autoapi/mappers/python/mapper.py:300: > RemovedInSphinx80Warning: The alias 'sphinx.util.status_iterator' is > deprecated, use 'sphinx.util.display.status_iterator' instead. Check CHANGES > for Sphinx API modifications. > for dir_root, path in sphinx.util.status_iterator( > [2K[AutoAPI] Reading files... [ 7%] /<>/khard/__init__.py > > Extension error (autoapi.extension): > Handler for event 'builder-inited' > threw an exception (exception: 'Module' object has no attribute 'doc') > make[2]: *** [Makefile:20: html] Error 2 The full build log is available from: http://qa-logs.debian.net/2024/01/15/khard_0.19.1-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1060995: ddrescueview: FTBFS: make[1]: *** [debian/rules:10: override_dh_auto_build] Error 2
Source: ddrescueview Version: 0.4.5-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lazbuild source/ddrescueview.lpi --bm="GNU/Linux Release" --no-write-project > --ws=qt5 > CopySecondaryConfigFile /etc/lazarus/environmentoptions.xml -> > /<>/tmphome/.lazarus/environmentoptions.xml > Note: (lazarus) Invalid Package Link: file > "/usr/lib/lazarus/3.0/ide/packages/ideconfig/ideconfig.lpk" does not exist. > > $55D5C4FD9B7A > $55D5C4FD4B65 > $55D5C4F30F2E > $55D5C5582713 > $55D5C50E4C83 > $55D5C50CF1DE > $55D5C50CF0D8 > $55D5C4F3513D > $55D5C4F32D64 > $55D5C4F313EB > $55D5C4F36C93 > $55D5C4F39979 > $55D5C4F5B75C > Error: (lazbuild) Package file not found > The package "IdeConfig" is installed but no valid package file (.lpk) was > found. > A broken dummy package was created. > lazbuild is non interactive, aborting now. > make[1]: *** [debian/rules:10: override_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2024/01/15/ddrescueview_0.4.5-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1060992: lomiri-system-settings: FTBFS: 12: QWARN : tst_notifications::ClickAppsVibrationsNotify::test_should_update_when_added() file:///<>/plugins/notifications/ClickAppsVibrations
Source: lomiri-system-settings Version: 1.0.1-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' > Running tests... > /usr/bin/ctest --force-new-ctest-process --verbose -j1 > UpdateCTestConfiguration from > :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > UpdateCTestConfiguration from > :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > Test project /<>/obj-x86_64-linux-gnu > Constructing a list of tests > Done constructing a list of tests > Updating test list for fixtures > Added 0 tests to meet fixture requirements > Checking test dependency graph... > Checking test dependency graph end > test 1 > Start 1: tst-plugins > > 1: Test command: /<>/obj-x86_64-linux-gnu/tests/tst-plugins > 1: Working Directory: /<>/obj-x86_64-linux-gnu/tests > 1: Environment variables: > 1: QT_QPA_PLATFORM=minimal > 1: XDG_DATA_DIRS=/<>/tests > 1: Test timeout computed to be: 1000 > 1: * Start testing of PluginsTest * > 1: Config: Using QtTest library 5.15.10, Qt 5.15.10 > (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 13.2.0), > debian unknown > 1: PASS : PluginsTest::initTestCase() > 1: PASS : PluginsTest::testCategory() > 1: PASS : PluginsTest::testName() > 1: PASS : PluginsTest::testKeywords() > 1: PASS : PluginsTest::testSorting() > 1: PASS : PluginsTest::testReset() > 1: PASS : PluginsTest::testResetInPlugin() > 1: PASS : PluginsTest::cleanupTestCase() > 1: Totals: 8 passed, 0 failed, 0 skipped, 0 blacklisted, 15ms > 1: * Finished testing of PluginsTest * > 1/12 Test #1: tst-plugins .. Passed0.03 sec > test 2 > Start 2: tst-arguments > > 2: Test command: /<>/obj-x86_64-linux-gnu/tests/tst-arguments > 2: Working Directory: /<>/obj-x86_64-linux-gnu/tests > 2: Test timeout computed to be: 1000 > 2: * Start testing of ArgumentsTest * > 2: Config: Using QtTest library 5.15.10, Qt 5.15.10 > (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 13.2.0), > debian unknown > 2: PASS : ArgumentsTest::initTestCase() > 2: PASS : ArgumentsTest::testNull() > 2: QWARN : ArgumentsTest::testDefaultPlugin() could not locate map file > 2: QWARN : ArgumentsTest::testDefaultPlugin() could not locate map file > 2: PASS : ArgumentsTest::testDefaultPlugin() > 2: QWARN : ArgumentsTest::testPluginOptions() could not locate map file > 2: PASS : ArgumentsTest::testPluginOptions() > 2: PASS : ArgumentsTest::testObsoleted() > 2: PASS : ArgumentsTest::cleanupTestCase() > 2: Totals: 6 passed, 0 failed, 0 skipped, 0 blacklisted, 1ms > 2: * Finished testing of ArgumentsTest * > 2/12 Test #2: tst-arguments Passed0.01 sec > test 3 > Start 3: tst-systemimage > > 3: Test command: /<>/obj-x86_64-linux-gnu/tests/tst-systemimage > 3: Working Directory: /<>/obj-x86_64-linux-gnu/tests > 3: Test timeout computed to be: 1000 > 3: * Start testing of TstSystemImage * > 3: Config: Using QtTest library 5.15.10, Qt 5.15.10 > (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 13.2.0), > debian unknown > 3: PASS : TstSystemImage::initTestCase() > 3: 1705349587.298 Information > 3: 1705349587.299 GetSetting "auto_download" > 3: 1705349587.300 GetSetting "failures_before_warning" > 3: QWARN : TstSystemImage::testDetailedVersionDetails() Unable to locate > signal on s-i interface. Will not connect to s-i events. > 3: PASS : TstSystemImage::testDetailedVersionDetails() > 3: 1705349587.422 Information > 3: 1705349587.422 GetSetting "auto_download" > 3: 1705349587.423 GetSetting "failures_before_warning" > 3: QWARN : TstSystemImage::testVersionTag() Unable to locate signal on s-i > interface. Will not connect to s-i events. > 3: PASS : TstSystemImage::testVersionTag() > 3: 1705349587.546 Information > 3: 1705349587.546 GetSetting "auto_download" > 3: 1705349587.547 GetSetting "failures_before_warning" > 3: QWARN : TstSystemImage::testAvailableStatus(available, downloading) > Unable to locate signal on s-i interface. Will not connect to s-i events. > 3: PASS : TstSystemImage::testAvailableStatus(available, downloading) > 3: 1705349587.682 Information > 3: 1705349587.682 GetSetting "auto_download" > 3: 1705349587.683 GetSetting "failures_before_warning" > 3: QWARN : TstSystemImage::testAvailableStatus(available, paused) Unable to > locate signal on s-i interface. Will not connect to s-i events. > 3: PASS : TstSystemImage::testAvailableStatus(available, paused) > 3: 1705349587.811 Information > 3: 1705349587.812 GetSetting "auto_download" > 3: 1705349587.812 GetSetting "failures_before_warning" > 3: QWARN : TstSystemImage::testAvailableStatus(not available) Unable
Bug#1060993: distro-info: FTBFS: AttributeError: module 'astroid.nodes' has no attribute 'TryExcept'
Source: distro-info Version: 1.7 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > ./test-debian-distro-info > cd perl && ./test.pl > testAlias > py3versions: no X-Python3-Version in control file, using supported versions > cd python && python3.12 setup.py test > 1..35 > testAll > ok 1 - unique: Matching lists > ok 2 - symmetric_difference: Matching lists > ok 3 - unique: 1 Unique Item > ok 4 - unique: 1 Unique Item in the haystack > ok 5 - symmetric_difference: 1 Unique Item > ok 6 - Debian all > ok 7 - Debian devel > ok 8 - Debian oldstable > ok 9 - Debian stable > ok 10 - Debian testing > ok 11 - Debian valid > ok 12 - Debian valid > ok 13 - Debian invalid > ok 14 - Debian supported > ok 15 - Debian LTS > ok 16 - Debian ELTS > ok 17 - Debian unsupported > ok 18 - Debian codename, invalid > ok 19 - Debian codename > ok 20 - Debian version, invalid > ok 21 - Debian version > ok 22 - Ubuntu all > ok 23 - Ubuntu version > ok 24 - Ubuntu LTS version > ok 25 - Ubuntu devel > ok 26 - Ubuntu LTS > ok 27 - Ubuntu stable > ok 28 - Ubuntu valid > ok 29 - Ubuntu invalid > ok 30 - Ubuntu is_lts > ok 31 - Ubuntu !is_lts > ok 32 - Ubuntu !is_lts > ok 33 - Ubuntu supported > ok 34 - Ubuntu ESM > ok 35 - Ubuntu unsupported > testDevel > testOldstable > testStable > testSupported > testLTS > testELTS > testUnsupported > testTesting > testFullname > running test > WARNING: Testing via this command is deprecated and will be removed in a > future version. Users looking for a generic test entry point independent of > test runner are encouraged to use tox. > /usr/lib/python3/dist-packages/setuptools/command/test.py:193: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > ir_d = dist.fetch_build_eggs(dist.install_requires) > WARNING: The wheel package is not available. > /usr/lib/python3/dist-packages/setuptools/command/test.py:194: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > tr_d = dist.fetch_build_eggs(dist.tests_require or []) > WARNING: The wheel package is not available. > /usr/lib/python3/dist-packages/setuptools/command/test.py:195: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > er_d = dist.fetch_build_eggs( > WARNING: The wheel package is not available. > running egg_info > creating distro_info.egg-info > writing distro_info.egg-info/PKG-INFO > writing dependency_links to distro_info.egg-info/dependency_links.txt > writing top-level names to distro_info.egg-info/top_level.txt > writing manifest file 'distro_info.egg-info/SOURCES.txt' > reading manifest file 'distro_info.egg-info/SOURCES.txt' > writing manifest file 'distro_info.egg-info/SOURCES.txt' > running build_ext > test_all (distro_info_test.test_distro_info.DebianDistroInfoTestCase.test_all) > Test: List all known Debian distributions. ... ok > test_codename > (distro_info_test.test_distro_info.DebianDistroInfoTestCase.test_codename) > Test: Codename decoding ... ok > test_codename_result > (distro_info_test.test_distro_info.DebianDistroInfoTestCase.test_codename_result) > Test: Check result set to codename. ... ok > test_devel > (distro_info_test.test_distro_info.DebianDistroInfoTestCase.test_devel) > Test: Get latest development Debian distribution. ... ok > test_elts_supported > (distro_info_test.test_distro_info.DebianDistroInfoTestCase.test_elts_supported) > Test: List all ELTS supported Debian distribution. ... ok > test_fullname > (distro_info_test.test_distro_info.DebianDistroInfoTestCase.test_fullname) > Test: Check result set to fullname. ... ok > test_lts_supported > (distro_info_test.test_distro_info.DebianDistroInfoTestCase.test_lts_supported) > Test: List all LTS supported Debian
Bug#1060990: wacomtablet: FTBFS: make: *** [debian/rules:8: binary] Error 2
Source: wacomtablet Version: 3.2.0-5 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake > -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None > -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var > -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON > -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. > CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required): > Compatibility with CMake < 3.5 will be removed from a future version of > CMake. > > Update the VERSION argument value or use a ... suffix to tell > CMake that the project does not need compatibility with older versions. > > > -- The C compiler identification is GNU 13.2.0 > -- The CXX compiler identification is GNU 13.2.0 > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working C compiler: /usr/bin/cc - skipped > -- Detecting C compile features > -- Detecting C compile features - done > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > -- Installing in the same prefix as Qt, adopting their path scheme. > -- Could not set up the appstream test. appstreamcli is missing. > -- Looking for __GLIBC__ > -- Looking for __GLIBC__ - found > -- Performing Test _OFFT_IS_64BIT > -- Performing Test _OFFT_IS_64BIT - Success > -- Performing Test HAVE_DATE_TIME > -- Performing Test HAVE_DATE_TIME - Success > CMake Warning (dev) at /usr/share/ECM/modules/ECMFindModuleHelpers.cmake:113 > (message): > Your project should require at least CMake 3.16.0 to use FindKF5.cmake > Call Stack (most recent call first): > /usr/share/ECM/find-modules/FindKF5.cmake:30 > (ecm_find_package_version_check) > CMakeLists.txt:25 (find_package) > This warning is for project developers. Use -Wno-dev to suppress it. > > -- Found KF5CoreAddons: > /usr/lib/x86_64-linux-gnu/cmake/KF5CoreAddons/KF5CoreAddonsConfig.cmake > (found version "5.107.0") > -- Found Gettext: /usr/bin/msgmerge (found version "0.21") > -- Found KF5I18n: /usr/lib/x86_64-linux-gnu/cmake/KF5I18n/KF5I18nConfig.cmake > (found version "5.107.0") > -- Found KF5GlobalAccel: > /usr/lib/x86_64-linux-gnu/cmake/KF5GlobalAccel/KF5GlobalAccelConfig.cmake > (found version "5.107.0") > -- Found KF5Config: > /usr/lib/x86_64-linux-gnu/cmake/KF5Config/KF5ConfigConfig.cmake (found > version "5.107.0") > -- Found KF5XmlGui: > /usr/lib/x86_64-linux-gnu/cmake/KF5XmlGui/KF5XmlGuiConfig.cmake (found > version "5.107.0") > -- Found KF5WidgetsAddons: > /usr/lib/x86_64-linux-gnu/cmake/KF5WidgetsAddons/KF5WidgetsAddonsConfig.cmake > (found version "5.107.0") > -- Found X11: /usr/include > -- Looking for XOpenDisplay in > /usr/lib/x86_64-linux-gnu/libX11.so;/usr/lib/x86_64-linux-gnu/libXext.so > -- Looking for XOpenDisplay in > /usr/lib/x86_64-linux-gnu/libX11.so;/usr/lib/x86_64-linux-gnu/libXext.so - > found > -- Looking for gethostbyname > -- Looking for gethostbyname - found > -- Looking for connect > -- Looking for connect - found > -- Looking for remove > -- Looking for remove - found > -- Looking for shmat > -- Looking for shmat - found > -- Found KF5WindowSystem: > /usr/lib/x86_64-linux-gnu/cmake/KF5WindowSystem/KF5WindowSystemConfig.cmake > (found version "5.107.0") > -- Found KF5Notifications: > /usr/lib/x86_64-linux-gnu/cmake/KF5Notifications/KF5NotificationsConfig.cmake > (found version "5.107.0") > -- Found KF5DBusAddons: > /usr/lib/x86_64-linux-gnu/cmake/KF5DBusAddons/KF5DBusAddonsConfig.cmake > (found version "5.107.0") > -- Found KF5Plasma: > /usr/lib/x86_64-linux-gnu/cmake/KF5Plasma/KF5PlasmaConfig.cmake (found > version "5.107.0") > -- Found KF5DocTools: > /usr/lib/x86_64-linux-gnu/cmake/KF5DocTools/KF5DocToolsConfig.cmake (found > version "5.107.0") > -- Found KF5: success (found version "5.107.0") found components: CoreAddons > I18n GlobalAccel Config XmlGui WidgetsAddons WindowSystem Notifications > DBusAddons Plasma DocTools > CMake Warning (dev) at /usr/share/ECM/modules/ECMFindModuleHelpers.cmake:113 > (message): > Your project should require at least CMake 3.16.0 to use FindXCB.cmake > Call Stack (most recent call first): > /usr/share/ECM/find-modules/FindXCB.cmake:67 > (ecm_find_package_version_check) > CMakeLists.txt:26
Bug#1060991: tuba: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_test] Error 1
Source: tuba
Version: 0.6.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd debian/build && ninja test
> [0/1] Running all tests.
> 1/9 BlurhashOK 0.03s
> 2/9 Celebrate OK 0.03s
> 3/9 TrackingOK 0.02s
> 4/9 Units OK 0.01s
> 5/9 WebApHandlerOK 0.01s
> 6/9 DateTimeFAIL0.03s killed by signal 6 SIGABRT
> >>> MALLOC_PERTURB_=151
> >>> UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
> >>> ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1
> >>> /<>/debian/build/tests/DateTime
> ― ✀ ―
> stdout:
> TAP version 13
> # random seed: R02S83fee4da4199330390e8ca34545512f3
> 1..5
> not ok /test_left -
> Tuba:ERROR:tests/DateTime.p/DateTime.test.c:758:test_left: assertion failed
> (_tmp7_ == _tmp9_): ("Aug 8, 2023" == "Aug 8")
> Bail out!
> stderr:
> **
> Tuba:ERROR:tests/DateTime.p/DateTime.test.c:758:test_left: assertion failed
> (_tmp7_ == _tmp9_): ("Aug 8, 2023" == "Aug 8")
> ――
>
> 7/9 HtmlOK 0.03s
> 8/9 Validate desktop file OK 0.01s
> 9/9 Validate appstream file OK 0.04s
>
> Summary of Failures:
>
> 6/9 DateTimeFAIL0.03s killed by signal 6 SIGABRT
>
> Ok: 8
> Expected Fail: 0
> Fail: 1
> Unexpected Pass:0
> Skipped:0
> Timeout:0
>
> Full log written to /<>/debian/build/meson-logs/testlog.txt
> FAILED: meson-internal__test
> /usr/bin/meson test --no-rebuild --print-errorlogs
> ninja: build stopped: subcommand failed.
> make[1]: *** [debian/rules:16: override_dh_auto_test] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/01/15/tuba_0.6.1-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
Bug#1060989: astap: FTBFS: make[1]: *** [debian/rules:14: override_dh_auto_build] Error 2
Source: astap Version: 2022.12.09-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lazbuild --widgetset=qt5 astap_linux.lpi > CopySecondaryConfigFile /etc/lazarus/environmentoptions.xml -> > /<>/tmphome/.lazarus/environmentoptions.xml > Note: (lazarus) Invalid Package Link: file > "/usr/lib/lazarus/3.0/ide/packages/ideconfig/ideconfig.lpk" does not exist. > > $55E0224A2B7A > $55E02249DB65 > $55E0223F9F2E > $55E022A4B713 > $55E0225ADC83 > $55E0225981DE > $55E0225980D8 > $55E0223FE13D > $55E0223FBD64 > $55E0223FA3EB > $55E0223FFC93 > $55E022402979 > $55E02242475C > Error: (lazbuild) Package file not found > The package "IdeConfig" is installed but no valid package file (.lpk) was > found. > A broken dummy package was created. > lazbuild is non interactive, aborting now. > make[1]: *** [debian/rules:14: override_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2024/01/15/astap_2022.12.09-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1060988: mathcomp-analysis: FTBFS: make[3]: *** [Makefile.coq:838: classical/mathcomp_extra.vo] Error 1
Source: mathcomp-analysis Version: 0.6.4-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > COQDEP VFILES > COQC classical/boolp.v > COQC classical/mathcomp_extra.v > COQC theories/forms.v > COQC theories/altreals/xfinmap.v > File "./classical/mathcomp_extra.v", line 7, characters 9-28: > Error: The reference choice.Choice.mixin was not found in the current > environment. > > make[3]: *** [Makefile.coq:838: classical/mathcomp_extra.vo] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/01/15/mathcomp-analysis_0.6.4-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1060987: q2cli: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Source: q2cli
Version: 2022.11.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:305: python3.11 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11/build/q2cli
> copying q2cli/__init__.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli
> copying q2cli/_version.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli
> copying q2cli/__main__.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli
> copying q2cli/commands.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli
> copying q2cli/util.py -> /<>/.pybuild/cpython3_3.11/build/q2cli
> creating /<>/.pybuild/cpython3_3.11/build/q2cli/tests
> copying q2cli/tests/test_mystery_stew.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli/tests
> copying q2cli/tests/__init__.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli/tests
> copying q2cli/tests/test_cache_cli.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli/tests
> copying q2cli/tests/test_dev.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli/tests
> copying q2cli/tests/test_cli.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli/tests
> copying q2cli/tests/test_core.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli/tests
> copying q2cli/tests/test_usage.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli/tests
> copying q2cli/tests/test_tools.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli/tests
> creating /<>/.pybuild/cpython3_3.11/build/q2cli/core
> copying q2cli/core/__init__.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli/core
> copying q2cli/core/completion.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli/core
> copying q2cli/core/state.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli/core
> copying q2cli/core/usage.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli/core
> copying q2cli/core/config.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli/core
> copying q2cli/core/cache.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli/core
> creating /<>/.pybuild/cpython3_3.11/build/q2cli/builtin
> copying q2cli/builtin/__init__.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli/builtin
> copying q2cli/builtin/tools.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli/builtin
> copying q2cli/builtin/dev.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli/builtin
> copying q2cli/builtin/info.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli/builtin
> creating /<>/.pybuild/cpython3_3.11/build/q2cli/click
> copying q2cli/click/type.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli/click
> copying q2cli/click/__init__.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli/click
> copying q2cli/click/parser.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli/click
> copying q2cli/click/command.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli/click
> copying q2cli/click/option.py ->
> /<>/.pybuild/cpython3_3.11/build/q2cli/click
> running egg_info
> creating q2cli.egg-info
> writing q2cli.egg-info/PKG-INFO
> writing dependency_links to q2cli.egg-info/dependency_links.txt
> writing entry points to q2cli.egg-info/entry_points.txt
> writing top-level names to q2cli.egg-info/top_level.txt
> writing manifest file 'q2cli.egg-info/SOURCES.txt'
> reading manifest file 'q2cli.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> writing manifest file 'q2cli.egg-info/SOURCES.txt'
> UPDATING /<>/.pybuild/cpython3_3.11/build/q2cli/_version.py
> set /<>/.pybuild/cpython3_3.11/build/q2cli/_version.py to
> '2022.11.1'
> running build_scripts
> creating build
> creating build/scripts-3.11
> copying bin/tab-qiime -> build/scripts-3.11
> changing mode of build/scripts-3.11/tab-qiime from 644 to 755
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:305: cd /<>/.pybuild/cpython3_3.11/build;
> python3.11 -m pytest --ignore=q2cli/tests/test_usage.py
> = test session starts
> ==
> platform linux -- Python 3.11.7, pytest-7.4.4, pluggy-1.3.0
> rootdir: /<>
> collected 0 items / 6 errors
>
> ERRORS
>
> _ ERROR collecting .pybuild/cpython3_3.11/build/q2cli/tests/test_cache_cli.py
> __
> q2cli/tests/test_cache_cli.py:15: in
> from qiime2 import Artifact
> /usr/lib/python3/dist-packages/qiime2/__init__.py:23: in
> __citations__ = tuple(Citations.load('citations.bib', package='qiime2'))
> /usr/lib/python3/dist-packages/qiime2/core/cite.py:26: in load
> parser = bp.bparser.BibTexParser()
> E AttributeError: module 'bibtexparser' has no attribute
Bug#1060985: prewikka: FTBFS: ModuleNotFoundError: No module named 'six'
Source: prewikka
Version: 5.2.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with=python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:305: python3.12 setup.py config
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84:
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are
> deprecated.
> !!
>
>
>
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
>
>
>
> !!
> dist.fetch_build_eggs(dist.setup_requires)
> WARNING: The wheel package is not available.
> running config
> I: pybuild base:305: python3.11 setup.py config
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84:
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are
> deprecated.
> !!
>
>
>
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
>
>
>
> !!
> dist.fetch_build_eggs(dist.setup_requires)
> WARNING: The wheel package is not available.
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3.12 setup.py build
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84:
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are
> deprecated.
> !!
>
>
>
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
>
>
>
> !!
> dist.fetch_build_eggs(dist.setup_requires)
> WARNING: The wheel package is not available.
> running build
> running compile_catalog
> compiling catalog prewikka/locale/en/LC_MESSAGES/prewikka.po to
> prewikka/locale/en/LC_MESSAGES/prewikka.mo
> error: prewikka/locale/ru/LC_MESSAGES/prewikka.po:168: unknown named
> placeholder 'version'
> error: prewikka/locale/ru/LC_MESSAGES/prewikka.po:2793: placeholders are
> incompatible
> compiling catalog prewikka/locale/ru/LC_MESSAGES/prewikka.po to
> prewikka/locale/ru/LC_MESSAGES/prewikka.mo
> error: prewikka/locale/pl/LC_MESSAGES/prewikka.po:2162: placeholders are
> incompatible
> error: prewikka/locale/pl/LC_MESSAGES/prewikka.po:2854: placeholders are
> incompatible
> compiling catalog prewikka/locale/pl/LC_MESSAGES/prewikka.po to
> prewikka/locale/pl/LC_MESSAGES/prewikka.mo
> error: prewikka/locale/de/LC_MESSAGES/prewikka.po:2804: placeholders are
> incompatible
> compiling catalog prewikka/locale/de/LC_MESSAGES/prewikka.po to
> prewikka/locale/de/LC_MESSAGES/prewikka.mo
> error: prewikka/locale/pt_BR/LC_MESSAGES/prewikka.po:2397: placeholders are
> incompatible
> error: prewikka/locale/pt_BR/LC_MESSAGES/prewikka.po:2810: placeholders are
> incompatible
> compiling catalog prewikka/locale/pt_BR/LC_MESSAGES/prewikka.po to
> prewikka/locale/pt_BR/LC_MESSAGES/prewikka.mo
> compiling catalog prewikka/locale/fr/LC_MESSAGES/prewikka.po to
> prewikka/locale/fr/LC_MESSAGES/prewikka.mo
> error: prewikka/locale/es/LC_MESSAGES/prewikka.po:2393: placeholders are
> incompatible
> error: prewikka/locale/es/LC_MESSAGES/prewikka.po:2807: placeholders are
> incompatible
> compiling catalog prewikka/locale/es/LC_MESSAGES/prewikka.po to
> prewikka/locale/es/LC_MESSAGES/prewikka.mo
> compiling catalog prewikka/locale/it/LC_MESSAGES/prewikka.po to
> prewikka/locale/it/LC_MESSAGES/prewikka.mo
> 9 errors encountered.
> running build_custom
> Traceback (most recent call last):
> File "/usr/bin/lesscpy", line 33, in
> sys.exit(load_entry_point('lesscpy==0.15.1', 'console_scripts',
> 'lesscpy')())
> ^
> File "/usr/bin/lesscpy", line 25, in importlib_load_entry_point
> return next(matches).load()
>
> File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 202, in load
> module = import_module(match.group('module'))
>
> File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
> return _bootstrap._gcd_import(name[level:],
Bug#1060984: apertium-eo-en: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
Source: apertium-eo-en Version: 1.0.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > apertium-regtest test > Corpus 1 of 5: en-eo-outstanding > Failed command: apertium-postchunk -z apertium-eo-en.en-eo.t3x en-eo.t3x.bin > Writing stderr to test/error.log > Exiting > make[1]: *** [Makefile:898: test] Error 1 > make[1]: Leaving directory '/<>' > dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 > returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2024/01/15/apertium-eo-en_1.0.2-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1060982: image-factory: FTBFS: AttributeError: module 'astroid.nodes' has no attribute 'TryExcept'
Source: image-factory
Version: 1.0.2-1.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> python3 -m unittest discover -v
> test_black (tests.test_black.BlackTestCase.test_black)
> Test: Run black code formatter on Python source code. ... Running following
> command:
> black --check --diff -l 99 image-factory tests
> ok
> test_empty_config (tests.test_cli.TestCLI.test_empty_config)
> Test empty configuration file. ... ok
> test_example_config (tests.test_cli.TestCLI.test_example_config)
> Test exapmle image-factory.conf file. ... ok
> test_override_cache_dir (tests.test_cli.TestCLI.test_override_cache_dir)
> Test overriding the cache directory. ... ok
> test_flake8 (tests.test_flake8.Flake8TestCase.test_flake8)
> Test: Run flake8 on Python source code. ... Running following command:
> /usr/bin/python3 -m flake8 --max-line-length=99 image-factory tests
> ok
> test_invalid (tests.test_helper.TestParseBytes.test_invalid)
> Test parse_bytes("invalid") ... ok
> test_parse_1_g (tests.test_helper.TestParseBytes.test_parse_1_g)
> Test parse_bytes("1G") ... ok
> test_parse_2_tb (tests.test_helper.TestParseBytes.test_parse_2_tb)
> Test parse_bytes("2 TB") ... ok
> test_parse_512_mib (tests.test_helper.TestParseBytes.test_parse_512_mib)
> Test parse_bytes("512 MiB") ... ok
> test_isort (tests.test_isort.IsortTestCase.test_isort)
> Test: Run isort on Python source code. ... Running following command:
> isort --check-only --diff -l 99 image-factory tests
> ok
> test_pylint (tests.test_pylint.PylintTestCase.test_pylint)
> Test: Run pylint on Python source code. ... Running following command:
> /usr/bin/python3 -m pylint --rcfile=/<>/tests/pylint.conf --
> image-factory tests
> FAIL
> test_chmod_dnf_log (tests.test_sudo_helper.TestSudoHelper.test_chmod_dnf_log)
> Test read access for dnf log file. ... ok
> test_chmod_log_file
> (tests.test_sudo_helper.TestSudoHelper.test_chmod_log_file)
> Test read access for mounted /var/log/... ... ok
> test_chmod_recursive
> (tests.test_sudo_helper.TestSudoHelper.test_chmod_recursive)
> Test chmod recursively ... ok
> test_chmod_remove_root
> (tests.test_sudo_helper.TestSudoHelper.test_chmod_remove_root)
> Test chmod remove mounted /root permission ... ok
> test_chmod_root (tests.test_sudo_helper.TestSudoHelper.test_chmod_root)
> Test chmod mounted /root ... ok
> test_chmod_var_log (tests.test_sudo_helper.TestSudoHelper.test_chmod_var_log)
> Test write access for mounted /var/log/... ... ok
> test_mount (tests.test_sudo_helper.TestSudoHelper.test_mount)
> Test mounting. ... ok
> test_reject_escaping
> (tests.test_sudo_helper.TestSudoHelper.test_reject_escaping)
> Test rejecting ../../etc/shadow. ... ok
> test_umount (tests.test_sudo_helper.TestSudoHelper.test_umount)
> Test unmounting. ... ok
>
> ==
> FAIL: test_pylint (tests.test_pylint.PylintTestCase.test_pylint)
> Test: Run pylint on Python source code.
> --
> Traceback (most recent call last):
> File "/<>/tests/test_pylint.py", line 74, in test_pylint
> self.fail("\n".join(msgs))
> AssertionError: pylint exited with code 1 and has unexpected output on stderr:
> Traceback (most recent call last):
> File "", line 198, in _run_module_as_main
> File "", line 88, in _run_code
> File "/usr/lib/python3/dist-packages/pylint/__main__.py", line 10, in
>
> pylint.run_pylint()
> File "/usr/lib/python3/dist-packages/pylint/__init__.py", line 36, in
> run_pylint
> PylintRun(argv or sys.argv[1:])
> File "/usr/lib/python3/dist-packages/pylint/lint/run.py", line 157, in
> __init__
> linter.load_default_plugins()
> File "/usr/lib/python3/dist-packages/pylint/lint/pylinter.py", line 369, in
> load_default_plugins
> checkers.initialize(self)
> File "/usr/lib/python3/dist-packages/pylint/checkers/__init__.py", line
> 136, in initialize
> register_plugins(linter, __path__[0])
> File "/usr/lib/python3/dist-packages/pylint/utils/utils.py", line 204, in
> register_plugins
> module = modutils.load_module_from_file(
> ^^^
> File "/usr/lib/python3/dist-packages/astroid/modutils.py", line 235, in
> load_module_from_file
> return load_module_from_modpath(modpath)
>^
> File "/usr/lib/python3/dist-packages/astroid/modutils.py", line 220, in
> load_module_from_modpath
> return load_module_from_name(".".join(parts))
>^^
> File "/usr/lib/python3/dist-packages/astroid/modutils.py", line 194, in
> load_module_from_name
> module = importlib.import_module(dotted_name)
>
Bug#1060981: libreswan: FTBFS: plutomain.c:1724:9: error: ignoring return value of ‘capng_apply’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result]
Source: libreswan Version: 4.12-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cc -pthread -std=gnu99 -g -Werror -Wall -Wextra -Wformat -Wformat-nonliteral > -Wformat-security -Wundef -Wmissing-declarations -Wredundant-decls > -Wnested-externs -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 > -fstack-protector-all -fno-strict-aliasing -fPIE -DPIE -DNSS_IPSEC_PROFILE > -DUSE_IKEv1 -DKERNEL_XFRM -DUSE_XFRM_INTERFACE -DXFRM_LIFETIME_DEFAULT=30 > -DUSE_DNSSEC -DDEFAULT_DNSSEC_ROOTKEY_FILE=\"/usr/share/dns/root.key\" > -DHAVE_LABELED_IPSEC -DLIBCURL -DUSE_LINUX_AUDIT -DUSE_SYSTEMD_WATCHDOG > -DLIBLDAP -DHAVE_NM -DUSE_PAM_AUTH -DUSE_3DES -DUSE_AES -DUSE_CAMELLIA > -DUSE_CHACHA -DUSE_DH31 -DUSE_MD5 -DUSE_SHA1 -DUSE_SHA2 -DUSE_PRF_AES_XCBC > -DUSE_NSS_KDF -DDEFAULT_RUNDIR=\"/run/pluto\" > -DIPSEC_CONF=\"/etc/ipsec.conf\" -DIPSEC_CONFDDIR=\"/etc/ipsec.d\" > -DIPSEC_NSSDIR=\"/var/lib/ipsec/nss\" -DIPSEC_CONFDIR=\"/etc\" > -DIPSEC_EXECDIR=\"/usr/libexec/ipsec\" -DIPSEC_SBINDIR=\"/usr/sbin\" > -DIPSEC_VARDIR=\"/var\" -DPOLICYGROUPSDIR=\"/etc/ipsec.d/policies\" > -DIPSEC_SECRETS_FILE=\"/etc/ipsec.secrets\" -DFORCE_PR_ASSERT -DHAVE_IPTABLES > -DUSE_FORK=1 -DUSE_VFORK=0 -DUSE_DAEMON=0 -DUSE_PTHREAD_SETSCHEDPRIO=1 > -DGCC_LINT -DHAVE_LIBCAP_NG \ > -I../../OBJ.linux.amd64/programs/pluto -I../../include > -I/usr/include/nss -I/usr/include/nspr > -I/<>/programs/pluto/linux-copy \ > -DHERE_FILENAME=\"/programs/pluto/orient.c\" \ > -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection \ > -MF ../../OBJ.linux.amd64/programs/pluto/orient.d \ > -MP -MMD -MT orient.o \ > -o ../../OBJ.linux.amd64/programs/pluto/orient.o \ > -c /<>/programs/pluto/orient.c > /<>/programs/pluto/plutomain.c: In function ‘main’: > /<>/programs/pluto/plutomain.c:1724:9: error: ignoring return > value of ‘capng_apply’ declared with attribute ‘warn_unused_result’ > [-Werror=unused-result] > 1724 | capng_apply(CAPNG_SELECT_BOTH); > | ^~ > cc -pthread -std=gnu99 -g -Werror -Wall -Wextra -Wformat -Wformat-nonliteral > -Wformat-security -Wundef -Wmissing-declarations -Wredundant-decls > -Wnested-externs -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 > -fstack-protector-all -fno-strict-aliasing -fPIE -DPIE -DNSS_IPSEC_PROFILE > -DUSE_IKEv1 -DKERNEL_XFRM -DUSE_XFRM_INTERFACE -DXFRM_LIFETIME_DEFAULT=30 > -DUSE_DNSSEC -DDEFAULT_DNSSEC_ROOTKEY_FILE=\"/usr/share/dns/root.key\" > -DHAVE_LABELED_IPSEC -DLIBCURL -DUSE_LINUX_AUDIT -DUSE_SYSTEMD_WATCHDOG > -DLIBLDAP -DHAVE_NM -DUSE_PAM_AUTH -DUSE_3DES -DUSE_AES -DUSE_CAMELLIA > -DUSE_CHACHA -DUSE_DH31 -DUSE_MD5 -DUSE_SHA1 -DUSE_SHA2 -DUSE_PRF_AES_XCBC > -DUSE_NSS_KDF -DDEFAULT_RUNDIR=\"/run/pluto\" > -DIPSEC_CONF=\"/etc/ipsec.conf\" -DIPSEC_CONFDDIR=\"/etc/ipsec.d\" > -DIPSEC_NSSDIR=\"/var/lib/ipsec/nss\" -DIPSEC_CONFDIR=\"/etc\" > -DIPSEC_EXECDIR=\"/usr/libexec/ipsec\" -DIPSEC_SBINDIR=\"/usr/sbin\" > -DIPSEC_VARDIR=\"/var\" -DPOLICYGROUPSDIR=\"/etc/ipsec.d/policies\" > -DIPSEC_SECRETS_FILE=\"/etc/ipsec.secrets\" -DFORCE_PR_ASSERT -DHAVE_IPTABLES > -DUSE_FORK=1 -DUSE_VFORK=0 -DUSE_DAEMON=0 -DUSE_PTHREAD_SETSCHEDPRIO=1 > -DGCC_LINT -DHAVE_LIBCAP_NG \ > -I../../OBJ.linux.amd64/programs/pluto -I../../include > -I/usr/include/nss -I/usr/include/nspr > -I/<>/programs/pluto/linux-copy \ > -DHERE_FILENAME=\"/programs/pluto/server.c\" \ > -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection \ > -MF ../../OBJ.linux.amd64/programs/pluto/server.d \ > -MP -MMD -MT server.o \ > -o ../../OBJ.linux.amd64/programs/pluto/server.o \ > -c /<>/programs/pluto/server.c > cc -pthread -std=gnu99 -g -Werror -Wall -Wextra -Wformat -Wformat-nonliteral > -Wformat-security -Wundef -Wmissing-declarations -Wredundant-decls > -Wnested-externs -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 > -fstack-protector-all -fno-strict-aliasing -fPIE -DPIE -DNSS_IPSEC_PROFILE > -DUSE_IKEv1 -DKERNEL_XFRM -DUSE_XFRM_INTERFACE -DXFRM_LIFETIME_DEFAULT=30 > -DUSE_DNSSEC -DDEFAULT_DNSSEC_ROOTKEY_FILE=\"/usr/share/dns/root.key\" > -DHAVE_LABELED_IPSEC -DLIBCURL -DUSE_LINUX_AUDIT -DUSE_SYSTEMD_WATCHDOG > -DLIBLDAP -DHAVE_NM -DUSE_PAM_AUTH -DUSE_3DES -DUSE_AES -DUSE_CAMELLIA > -DUSE_CHACHA -DUSE_DH31 -DUSE_MD5 -DUSE_SHA1 -DUSE_SHA2 -DUSE_PRF_AES_XCBC > -DUSE_NSS_KDF -DDEFAULT_RUNDIR=\"/run/pluto\" > -DIPSEC_CONF=\"/etc/ipsec.conf\" -DIPSEC_CONFDDIR=\"/etc/ipsec.d\" > -DIPSEC_NSSDIR=\"/var/lib/ipsec/nss\" -DIPSEC_CONFDIR=\"/etc\" > -DIPSEC_EXECDIR=\"/usr/libexec/ipsec\" -DIPSEC_SBINDIR=\"/usr/sbin\" > -DIPSEC_VARDIR=\"/var\"
Bug#1060983: dwarf2sources: FTBFS: build-dependency not installable: librust-gimli-0+indexmap-dev (>= 0.26)
Source: dwarf2sources Version: 0.2.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 12), dh-cargo, > librust-anyhow-1-dev, librust-fallible-iterator-0-dev, > librust-gimli-0+indexmap-dev (>= 0.26), librust-memmap-0-dev (>= 0.7), > librust-object-0+default-dev (>= 0.29), librust-serde-1+derive-dev, > librust-serde-json-1-dev, librust-structopt-0+default-dev (>= 0.3), > librust-typed-arena-2-dev, build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 12), dh-cargo, > librust-anyhow-1-dev, librust-fallible-iterator-0-dev, > librust-gimli-0+indexmap-dev (>= 0.26), librust-memmap-0-dev (>= 0.7), > librust-object-0+default-dev (>= 0.29), librust-serde-1+derive-dev, > librust-serde-json-1-dev, librust-structopt-0+default-dev (>= 0.3), > librust-typed-arena-2-dev, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [609 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [916 B] > Get:5 copy:/<>/apt_archive ./ Packages [949 B] > Fetched 2474 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: librust-gimli-0+indexmap-dev (>= > 0.26) but it is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2024/01/15/dwarf2sources_0.2.1-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1060980: apertium-es-ro: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
Source: apertium-es-ro Version: 0.7.5-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > apertium-regtest test > Corpus 1 of 2: es-ro > 1/2 (50.0%) tests pass (0/1 (0.0%) match gold) > > Corpus 2 of 2: ro-es > 2/10 (20.0%) tests pass (0/2 (0.0%) match gold) > > There were changes! Rerun in interactive mode to update tests. > Changed corpora: es-ro, ro-es > make[1]: *** [Makefile:774: test] Error 1 > make[1]: Leaving directory '/<>' > dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 > returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2024/01/15/apertium-es-ro_0.7.5-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1060978: python-procrunner: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Source: python-procrunner Version: 1.1.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:305: python3.12 setup.py config > running config > I: pybuild base:305: python3.11 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:305: /usr/bin/python3.12 setup.py build > running build > running build_py > creating > /<>/.pybuild/cpython3_3.12_python-procrunner/build/procrunner > copying procrunner/__init__.py -> > /<>/.pybuild/cpython3_3.12_python-procrunner/build/procrunner > running egg_info > creating procrunner.egg-info > writing procrunner.egg-info/PKG-INFO > writing dependency_links to procrunner.egg-info/dependency_links.txt > writing requirements to procrunner.egg-info/requires.txt > writing top-level names to procrunner.egg-info/top_level.txt > writing manifest file 'procrunner.egg-info/SOURCES.txt' > reading manifest file 'procrunner.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no previously-included files matching '__pycache__' found under > directory '*' > warning: no previously-included files matching '*.py[co]' found under > directory '*' > warning: no files found matching '*.jpg' under directory 'docs' > warning: no files found matching '*.png' under directory 'docs' > warning: no files found matching '*.gif' under directory 'docs' > adding license file 'LICENSE' > adding license file 'AUTHORS.rst' > writing manifest file 'procrunner.egg-info/SOURCES.txt' > I: pybuild base:305: /usr/bin/python3 setup.py build > running build > running build_py > creating > /<>/.pybuild/cpython3_3.11_python-procrunner/build/procrunner > copying procrunner/__init__.py -> > /<>/.pybuild/cpython3_3.11_python-procrunner/build/procrunner > running egg_info > writing procrunner.egg-info/PKG-INFO > writing dependency_links to procrunner.egg-info/dependency_links.txt > writing requirements to procrunner.egg-info/requires.txt > writing top-level names to procrunner.egg-info/top_level.txt > reading manifest file 'procrunner.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no previously-included files matching '__pycache__' found under > directory '*' > warning: no previously-included files matching '*.py[co]' found under > directory '*' > warning: no files found matching '*.jpg' under directory 'docs' > warning: no files found matching '*.png' under directory 'docs' > warning: no files found matching '*.gif' under directory 'docs' > adding license file 'LICENSE' > adding license file 'AUTHORS.rst' > writing manifest file 'procrunner.egg-info/SOURCES.txt' >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:305: cd > /<>/.pybuild/cpython3_3.12_python-procrunner/build; python3.12 > -m pytest tests > = test session starts > == > platform linux -- Python 3.12.1, pytest-7.4.4, pluggy-1.3.0 > rootdir: /<> > configfile: setup.cfg > collected 0 items / 3 errors > > ERRORS > > _ ERROR collecting > .pybuild/cpython3_3.12_python-procrunner/build/tests/test_procrunner.py _ > ImportError while importing test module > '/<>/.pybuild/cpython3_3.12_python-procrunner/build/tests/test_procrunner.py'. > Hint: make sure your test modules/packages have valid Python names. > Traceback: > /usr/lib/python3.12/importlib/__init__.py:90: in import_module > return _bootstrap._gcd_import(name[level:], package, level) > tests/test_procrunner.py:6: in > import procrunner > procrunner/__init__.py:9: in > import six > E ModuleNotFoundError: No module named 'six' > _ ERROR collecting > .pybuild/cpython3_3.12_python-procrunner/build/tests/test_procrunner_resolution.py > _ > ImportError while importing test module > '/<>/.pybuild/cpython3_3.12_python-procrunner/build/tests/test_procrunner_resolution.py'. > Hint: make sure your test modules/packages have valid Python names. > Traceback: > /usr/lib/python3.12/importlib/__init__.py:90: in import_module > return _bootstrap._gcd_import(name[level:], package, level) > tests/test_procrunner_resolution.py:7: in > import procrunner > procrunner/__init__.py:9: in > import six > E ModuleNotFoundError: No module named 'six' > _ ERROR collecting > .pybuild/cpython3_3.12_python-procrunner/build/tests/test_procrunner_system.py > _ > ImportError while importing test module > '/<>/.pybuild/cpython3_3.12_python-procrunner/build/tests/test_procrunner_system.py'. > Hint: make sure your test modules/packages have valid Python
