Bug#1026781: pkgconf: breaks adequate missing-pkgconfig-dependency check due to behaviour change in: pkg-config --exists --print-errors
Package: pkgconf
Severity: serious
When a pkg doesn't have its dependencies satisfied, pkgconf --cflags
etc all print an error message and return a failure exit code.
With pkg-config, --exists does this check too, exits with an error and
with --print-errors present, prints the same error as --cflags etc do.
With pkgconf, --exists exits with an error only when the .pc file
doesn't actually exist, so I think it doesn't check if dependencies
are satisfied either, since with --print-errors no errors are printed.
This breaks the adequate test missing-pkgconfig-dependency, which runs
pkg-config and parses the output for errors about missing dependencies,
see below for the code that does this parsing.
pkg-config --exists --print-errors foo
An example of the behaviour under pkg-config:
$ pkg-config --exists --print-errors mpv ; echo $?
Package wayland-protocols was not found in the pkg-config search path.
Perhaps you should add the directory containing `wayland-protocols.pc'
to the PKG_CONFIG_PATH environment variable
Package 'wayland-protocols', required by 'mpv', not found
1
An example of the behaviour under pkgconf:
$ pkgconf --exists --print-errors mpv ; echo $?
0
$ pkgconf --cflags mpv ; echo $?
Package wayland-protocols was not found in the pkg-config search path.
Perhaps you should add the directory containing `wayland-protocols.pc'
to the PKG_CONFIG_PATH environment variable
Package 'wayland-protocols', required by 'mpv', not found
1
This is the bug that lead me to this pkgconf bug:
https://bugs.debian.org/1026624
Here is the code from adequate that performs this check,
please ensure that the error message matches the regex below.
$ dgrep -EC4 pkg-?conf adequate
/usr/bin/adequate- check_elfs(%file_map);
/usr/bin/adequate- check_paths(%file_map);
/usr/bin/adequate- check_alternatives(\%package_map, \%file_map);
/usr/bin/adequate- check_binfmts(@packages);
/usr/bin/adequate: check_pkgconfig(%file_map);
/usr/bin/adequate- flush_debconf();
/usr/bin/adequate- return;
/usr/bin/adequate-}
/usr/bin/adequate-
--
/usr/bin/adequate- }
/usr/bin/adequate- return;
/usr/bin/adequate-}
/usr/bin/adequate-
/usr/bin/adequate:sub check_pkgconfig
/usr/bin/adequate:: Tags(qw(missing-pkgconfig-dependency))
/usr/bin/adequate-{
/usr/bin/adequate- my %file_map = @_;
/usr/bin/adequate- my %pkg_map = ();
/usr/bin/adequate: -x '/usr/bin/pkg-config' or return;
/usr/bin/adequate- while (my ($debpkg, $files) = each %file_map) {
/usr/bin/adequate- for my $file (@{$files}) {
/usr/bin/adequate: $file =~
m{^/usr/(?:share|lib(?:/[^/]+)?)/pkgconfig/([^/]+)[.]pc$} or next;
/usr/bin/adequate- my $pkg = $1;
/usr/bin/adequate- $pkg_map{$pkg} = $debpkg;
/usr/bin/adequate- }
/usr/bin/adequate- }
/usr/bin/adequate- while (my ($pkg, $debpkg) = each %pkg_map) {
/usr/bin/adequate- local $ENV{LC_ALL} = 'C';
/usr/bin/adequate- flush_std_fh();
/usr/bin/adequate: my $pkgconfig_pid = open(my $pkgconfig, '-|') //
die "can't fork: $ERRNO";
/usr/bin/adequate: if ($pkgconfig_pid) { # parent
/usr/bin/adequate: while (<$pkgconfig>) {
/usr/bin/adequate- if (m/^Package '(.+)', required by
'\Q$pkg\E', not found$/) {
/usr/bin/adequate- my $deppkg = $1;
/usr/bin/adequate: tag $debpkg,
'missing-pkgconfig-dependency', $pkg, '=>', $deppkg;
/usr/bin/adequate- }
/usr/bin/adequate- }
/usr/bin/adequate: wait or die "pkg-config --exists: $ERRNO";
/usr/bin/adequate: close $pkgconfig; ## no critic
(CheckedSyscalls)
/usr/bin/adequate- } else { # child
/usr/bin/adequate- open(STDERR, '>') or die "can't
redirect stderr: $ERRNO";
/usr/bin/adequate: exec('pkg-config', '--exists',
'--print-errors', $pkg);
/usr/bin/adequate: die "can't exec pkg-config: $ERRNO";
/usr/bin/adequate- }
/usr/bin/adequate- }
/usr/bin/adequate- return;
/usr/bin/adequate-}
-- System Information:
Debian Release: bookworm/sid
APT prefers testing-debug
APT policy: (900, 'testing-debug'), (900, 'testing'), (800,
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700,
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages pkgconf depends on:
ii pkgconf-bin 1.8.0-11
pkgconf recommends no packages.
pkgconf suggests
Bug#1026676: marked as done (mapsforge: FTBFS: make: *** [debian/rules:9: build] Error 25)
Your message dated Wed, 21 Dec 2022 06:04:17 + with message-id and subject line Bug#1026676: fixed in mapsforge 0.17.0+dfsg.1-2 has caused the Debian Bug report #1026676, regarding mapsforge: FTBFS: make: *** [debian/rules:9: build] Error 25 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026676 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mapsforge Version: 0.17.0+dfsg.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > # Set version string correctly > if [ ! -f build.gradle.debsave ]; then \ > sed -i.debsave 's/master-SNAPSHOT/0.17.0/' build.gradle ;\ > fi > dh_auto_configure > make[1]: Leaving directory '/<>' >dh_auto_build -O--buildsystem=gradle > mkdir -p .gradle/init.d > cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/ > gradle --info --console plain --offline --stacktrace --no-daemon > --refresh-dependencies --gradle-user-home .gradle -Duser.home=. > -Duser.name=debian -Ddebian.package=mapsforge -Dfile.encoding=UTF-8 > --parallel --max-workers=8 jar > OpenJDK 64-Bit Server VM warning: Ignoring option --illegal-access=permit; > support was removed in 17.0 > Initialized native services in: /<>/.gradle/native > To honour the JVM settings for this build a new JVM will be forked. Please > consider using the daemon: > https://docs.gradle.org/4.4.1/userguide/gradle_daemon.html. > Starting process 'Gradle build daemon'. Working directory: > /<>/.gradle/daemon/4.4.1 Command: > /usr/lib/jvm/java-17-openjdk-amd64/bin/java > -Xbootclasspath/a:/usr/share/java/gradle-helper-hook.jar:/usr/share/java/maven-repo-helper.jar > --add-opens java.base/java.lang=ALL-UNNAMED -Dfile.encoding=UTF-8 > -Duser.country -Duser.language=en -Duser.variant -cp > /usr/share/gradle/lib/gradle-launcher-4.4.1.jar > org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.4.1 > Successfully started process 'Gradle build daemon' > An attempt to start the daemon took 1.085 secs. > The client will now receive all logging from the daemon (pid: 1056301). The > daemon log file: /<>/.gradle/daemon/4.4.1/daemon-1056301.out.log > Daemon will be stopped at the end of the build stopping after processing > Closing daemon's stdin at end of input. > The daemon will no longer process any standard input. > Using 8 worker leases. > Creating new cache for fileHashes, path > /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@6fe3a4b9 > Creating new cache for resourceHashesCache, path > /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, > access org.gradle.cache.internal.DefaultCacheAccess@6fe3a4b9 > Creating new cache for fileHashes, path > /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@5b5ae1da > Starting Build > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using SubsetScriptTransformer. > Creating new cache for metadata-1.1/results, path > /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access > org.gradle.cache.internal.DefaultCacheAccess@3a3235bf > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using BuildScriptTransformer. > Compiling settings file '/<>/settings.gradle' using > SubsetScriptTransformer. > Compiling settings file '/<>/settings.gradle' using > BuildScriptTransformer. > Settings evaluated using settings file '/<>/settings.gradle'. > Settings file found (/<>/settings.gradle), but > rootProject.name isn't defined > Root project name not defined in settings.gradle, defaulting to > 'mapsforge' instead of the name of the root directory > 'mapsforge-0.17.0+dfsg.1' > Projects loaded. Root project using build file > '/<>/build.gradle'. > Included projects: [root project 'mapsforge', project ':mapsforge-core', > project ':mapsforge-map', project ':mapsforge-map-awt', project > ':mapsforge-map-reader', project ':mapsforge-map-writer', project > ':mapsforge-poi', project ':mapsfo
Bug#1026561: mailscripts: FTBFS: AttributeError: module 'cryptography.utils' has no attribute 'register_interface'. Did you mean: 'verify_interface'?
Hello, dkg, could you take a look? Thank you. On Tue 20 Dec 2022 at 06:22PM +01, Lucas Nussbaum wrote: > Source: mailscripts > Version: 27-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20221220 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): >> make[1]: Entering directory '/<>' >> ./tests/email-print-mime-structure.sh >> Testing alternative.eml >> Traceback (most recent call last): >> File "/<>/./email-print-mime-structure", line 46, in >> import pgpy #type: ignore >> File "/usr/lib/python3/dist-packages/pgpy/__init__.py", line 4, in >> from .pgp import PGPKey >> File "/usr/lib/python3/dist-packages/pgpy/pgp.py", line 27, in >> from .constants import CompressionAlgorithm >> File "/usr/lib/python3/dist-packages/pgpy/constants.py", line 23, in >> >> from ._curves import BrainpoolP256R1, BrainpoolP384R1, BrainpoolP512R1, >> X25519, Ed25519 >> File "/usr/lib/python3/dist-packages/pgpy/_curves.py", line 37, in >> @utils.register_interface(ec.EllipticCurve) >> AttributeError: module 'cryptography.utils' has no attribute >> 'register_interface'. Did you mean: 'verify_interface'? >> --- tests/email-print-mime-structure/alternative.out 2022-06-24 >> 21:52:21.0 + >> +++ /dev/fd/63 2022-12-20 09:49:43.674063951 + >> @@ -1,3 +0,0 @@ >> -└┬╴multipart/alternative 414 bytes >> - ├─╴text/plain 26 bytes >> - └─╴text/html 72 bytes >> make[1]: *** [Makefile:14: check] Error 1 >> make[1]: Leaving directory '/<>' >> dh_auto_test: error: make -j8 check returned exit code 2 > > > The full build log is available from: > http://qa-logs.debian.net/2022/12/20/mailscripts_27-1_unstable.log > > All bugs filed during this archive rebuild are listed at: > https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org > or: > https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=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. -- Sean Whitton
Bug#1011567: android-framework-23: FTBFS with OpenJDK 17 due to com.sun.javadoc removal
[Emmanuel Bourg] > android-framework-23 fails to build with OpenJDK 17, Doclava no longer > works due to the removal of the com.sun.javadoc API: Is there any hope to have this fixed for bookworm? This bug block the Android SDK to entering testing. -- Happy hacking Petter Reinholdtsen
Bug#1026624: mpv-mpris: FTBFS: mpris.c:1:10: fatal error: gio/gio.h: No such file or directory
Control: reassign -1 libmpv-dev Control: affects -1 src:mpv-mpris Control: retitle -1 libmpv-dev: missing dependency on wayland-protocols On Tue, 2022-12-20 at 18:16 +0100, Lucas Nussbaum wrote: > [mpv-mpris] failed to build on amd64. > > Relevant part (hopefully): ... > > Package wayland-protocols was not found in the pkg-config search path. > > Perhaps you should add the directory containing `wayland-protocols.pc' > > to the PKG_CONFIG_PATH environment variable > > Package 'wayland-protocols', required by 'mpv', not found This is a bug in libmpv-dev, it should dep on wayland-protocols: # pkg-config --cflags mpv Package wayland-protocols was not found in the pkg-config search path. Perhaps you should add the directory containing `wayland-protocols.pc' to the PKG_CONFIG_PATH environment variable Package 'wayland-protocols', required by 'mpv', not found # apt install wayland-protocols Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: wayland-protocols 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 71.8 kB of archives. After this operation, 549 kB of additional disk space will be used. Get:1 https://deb.debian.org/debian sid/main amd64 wayland-protocols all 1.27-1 [71.8 kB] Fetched 71.8 kB in 0s (243 kB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package wayland-protocols. (Reading database ... 24263 files and directories currently installed.) Preparing to unpack .../wayland-protocols_1.27-1_all.deb ... Unpacking wayland-protocols (1.27-1) ... Setting up wayland-protocols (1.27-1) ... # pkg-config --cflags mpv -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/uuid -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/fribidi -I/usr/include/x86_64-linux-gnu -I/usr/include/libxml2 -I/usr/include/lua5.2 -I/usr/include/SDL2 -I/usr/include/uchardet -I/usr/include/pipewire-0.3 -I/usr/include/spa-0.2 -D_REENTRANT -I/usr/include/libdrm -I/usr/include/sixel -I/usr/include/spirv_cross # grep wayland-protocols /usr/lib/x86_64-linux-gnu/pkgconfig/mpv.pc Requires.private: wayland-client >= 1.15.0, libass >= 0.12.2, libavcodec >= 58.12.100, libavfilter >= 7.14.100, libavformat >= 58.9.100, libavutil >= 56.12.100, libswresample >= 3.0.100, libswscale >= 5.0.101, libcdio_paranoia, dvdnav >= 4.2.0, dvdread >= 4.1.0, mujs >= 1.0.0, lcms2 >= 2.6, libarchive >= 3.4.0, libavdevice >= 57.0.0, libbluray >= 0.3.0, lua52 >= 5.2.0, rubberband >= 1.8.0, sdl2, uchardet, zimg >= 2.9, zlib, alsa >= 1.0.18, jack, libpipewire-0.3 >= 0.3.19, libpulse >= 1.0, caca >= 0.99.beta18, libdrm >= 2.4.75, gbm >= 17.1.0, libjpeg, libplacebo >= 4.157.0, libsixel >= 1.5, spirv-cross-c-shared, wayland-cursor >= 1.15.0, wayland-protocols >= 1.15, xkbcommon >= 0.3.0, x11 >= 1.0.0, xscrnsaver >= 1.0.0, xext >= 1.0.0, xinerama >= 1.0.0, xpresent >= 1.0.0, xrandr >= 1.2.0, xv, egl > 1.4.0, wayland-egl >= 9.0.0, vulkan, ffnvcodec >= 8.2.15.7, libva >= 1.1.0, libva-drm >= 1.1.0, libva-wayland >= 1.1.0, libva-x11 >= 1.1.0, vdpau >= 0.2 -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#1026624: mpv-mpris: FTBFS: mpris.c:1:10: fatal error: gio/gio.h: No such file or directory
Processing control commands: > reassign -1 libmpv-dev Bug #1026624 [src:mpv-mpris] mpv-mpris: FTBFS: mpris.c:1:10: fatal error: gio/gio.h: No such file or directory Bug reassigned from package 'src:mpv-mpris' to 'libmpv-dev'. No longer marked as found in versions mpv-mpris/0.7.1-1. Ignoring request to alter fixed versions of bug #1026624 to the same values previously set > affects -1 src:mpv-mpris Bug #1026624 [libmpv-dev] mpv-mpris: FTBFS: mpris.c:1:10: fatal error: gio/gio.h: No such file or directory Added indication that 1026624 affects src:mpv-mpris > retitle -1 libmpv-dev: missing dependency on wayland-protocols Bug #1026624 [libmpv-dev] mpv-mpris: FTBFS: mpris.c:1:10: fatal error: gio/gio.h: No such file or directory Changed Bug title to 'libmpv-dev: missing dependency on wayland-protocols' from 'mpv-mpris: FTBFS: mpris.c:1:10: fatal error: gio/gio.h: No such file or directory'. -- 1026624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026624 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1023365: prusa-slicer: Wrong wxWidgets Version linked during debian Build resulting in instant SIGSEGV on launch (due to lacking wxWidgets 3.2 support)
On Wed, Dec 21, 2022 at 11:21:03AM +0800, Chow Loong Jin wrote: > I've fixed the segfault by applying the patch from [1], but there's one > issue remaining -- PrusaSlicer fails to initialize GLEW due to [2], > resulting in the plater screen not showing up, same as this SuperSlicer > issue[3]. > > I've also attempted to roll PrusaSlicer back to wxwidgets3.0 Please don't do that. We're really close to eliminating wxwidgets3.0 now, and we're not planning to include it in the bookworm release. We're going to switch to --disable-glcanvasegl in wxwidgets3.2 which should solve the incompatibilities with GLEW which seem to be the problem here. However that's an ABI breaking change affecting any packages using wxwidgets3.2's OpenGL APIs so it needs coordinating with the release team - Scott is currently working on that. Cheers, Olly
Bug#1026635: rust-packed-simd: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101
During a rebuild of all packages in sid, your package failed to build on amd64. I make the following observations about this package. * It relies on perma-unstable rustc features and this is the third time it has broken in the last two years due to changes in rustc. * It has no long-term future, the future of "portable simd" is as a feature in the standard library "std::simd". This is also an unstable feature at present but at least has a path to stabilization. * The current development team does not have access to the packed-simd crate on crates.io, so new releases are being released under the alternate crate name "packed-simd2". * No applications in Debian currently use it, the only remaining reverse dependencies are optional features in the encoding-rs, grep-searcher and grep crates. * The upstream author of those crates said in a recent commit message "I'm *very* close to just removing the 'simd-accel' feature altogether." Personally I think it's time for this package to go. Unless someone expresses an intent to fix this package, I intend to patch the encoding-rs grep-searcher and grep crates to remove the "simd-accel" feature allowing this package to be autoremoved from testing without taking any applications with it.
Bug#1026696: golang-github-prometheus-client-model: FTBFS: make: *** [debian/rules:6: binary] Error 25
After a fair amount of head scratching, I tracked this down to a change
in behaviour of the protobuf compiler. Version 3.14.0+ generates
slightly different pb.go files with respect to the timestamp type (and
possibly others):
--- metrics.pb.go.old 2022-11-08 23:31:00.0 +1300
+++ metrics.pb.go.new 2022-11-08 23:31:00.0 +1300
@@ -6,7 +6,7 @@
import (
fmt "fmt"
proto "github.com/golang/protobuf/proto"
- timestamp "github.com/golang/protobuf/ptypes/timestamp"
+ timestamppb "google.golang.org/protobuf/types/known/timestamppb"
math "math"
)
@@ -629,12 +629,12 @@
}
type Exemplar struct {
- Label []*LabelPair
`protobuf:"bytes,1,rep,name=label" json:"label,omitempty"`
- Value *float64
`protobuf:"fixed64,2,opt,name=value" json:"value,omitempty"`
- Timestamp *timestamp.Timestamp
`protobuf:"bytes,3,opt,name=timestamp" json:"timestamp,omitempty"`
- XXX_NoUnkeyedLiteral struct{} `json:"-"`
- XXX_unrecognized []byte `json:"-"`
- XXX_sizecache int32 `json:"-"`
+ Label []*LabelPair
`protobuf:"bytes,1,rep,name=label" json:"label,omitempty"`
+ Value *float64
`protobuf:"fixed64,2,opt,name=value" json:"value,omitempty"`
+ Timestamp *timestamppb.Timestamp
`protobuf:"bytes,3,opt,name=timestamp" json:"timestamp,omitempty"`
+ XXX_NoUnkeyedLiteral struct{} `json:"-"`
+ XXX_unrecognized []byte `json:"-"`
+ XXX_sizecache int32 `json:"-"`
}
func (m *Exemplar) Reset() { *m = Exemplar{} }
@@ -676,7 +676,7 @@
return 0
}
-func (m *Exemplar) GetTimestamp() *timestamp.Timestamp {
+func (m *Exemplar) GetTimestamp() *timestamppb.Timestamp {
if m != nil {
return m.Timestamp
}
I was surprised that the protobuf _compiler_ was responsible for this
change, but verified with an older snapshot of the package (3.12.4-1+b5)
that the previous behaviour was restored. Snapshot versions 3.14.0-1 and
later produce the newer style generated pb.go file, referencing
timestamppb.Timestamp.
The upstream changelogs for the protobuf compiler do not list any
Go-related changes in version 3.13.x, however for version 3.14.0 the
following is mentioned:
Go:
* Update go_package options to reference google.golang.org/protobuf
module.
I strongly suspect that this resulted in the change in the generated
pb.go file. The Makefile in prometheus/client_model also pins the
protobuf compiler version to 3.13.0:
# Need to be on a previous version that doesn't cause the updated WKT
go_package values to be added.
PROTOC_VERSION := 3.13.0
OpenPGP_signature
Description: OpenPGP digital signature
Processed: Re: Bug#1023365: prusa-slicer: Wrong wxWidgets Version linked during debian Build resulting in instant SIGSEGV on launch (due to lacking wxWidgets 3.2 support)
Processing commands for cont...@bugs.debian.org: > block 1023365 by 1024147 Bug #1023365 [prusa-slicer] prusa-slicer: Wrong wxWidgets Version linked during debian Build resulting in instant SIGSEGV on launch (due to lacking wxWidgets 3.2 support) 1023365 was not blocked by any bugs. 1023365 was blocking: 1019416 Added blocking bug(s) of 1023365: 1024147 > retitle 1023365 Compatibility problems with wxwidgets3.2 Bug #1023365 [prusa-slicer] prusa-slicer: Wrong wxWidgets Version linked during debian Build resulting in instant SIGSEGV on launch (due to lacking wxWidgets 3.2 support) Changed Bug title to 'Compatibility problems with wxwidgets3.2' from 'prusa-slicer: Wrong wxWidgets Version linked during debian Build resulting in instant SIGSEGV on launch (due to lacking wxWidgets 3.2 support)'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1023365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1023365: prusa-slicer: Wrong wxWidgets Version linked during debian Build resulting in instant SIGSEGV on launch (due to lacking wxWidgets 3.2 support)
block 1023365 by 1024147 retitle 1023365 Compatibility problems with wxwidgets3.2 thanks I've fixed the segfault by applying the patch from [1], but there's one issue remaining -- PrusaSlicer fails to initialize GLEW due to [2], resulting in the plater screen not showing up, same as this SuperSlicer issue[3]. I've also attempted to roll PrusaSlicer back to wxwidgets3.0, including dropping all the wx3.2-related distro patches but it segfaults for an entirely different reason now, and I haven't had the time to figure it out (it's starting to look like a gcc bug to do with std::vector, but that doesn't make any sense). [1] https://bugs.debian.org/1022234 [2] https://bugs.debian.org/1024147 [3] https://github.com/supermerill/SuperSlicer/issues/1093 -- Kind regards, Loong Jin signature.asc Description: PGP signature
Processed: tagging 1023633
Processing commands for cont...@bugs.debian.org: > tags 1023633 + pending Bug #1023633 [python3-scalene] python3-scalene: can't import (or execute) scalene Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1023633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1025237
Processing commands for cont...@bugs.debian.org: > tags 1025237 + pending Bug #1025237 [src:scalene] scalene: FTBFS with python3.11 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1025237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025237 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026593: marked as done (volk: FTBFS: collect2: error: ld returned 1 exit status)
Your message dated Wed, 21 Dec 2022 01:52:48 + with message-id and subject line Bug#1026593: fixed in volk 2.5.2-3 has caused the Debian Bug report #1026593, regarding volk: FTBFS: collect2: error: ld returned 1 exit status to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026593 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: volk Version: 2.5.2-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -fcx-limited-range -Wall -Wl,-z,relro > CMakeFiles/cmTC_16f14.dir/src.cxx.o -o cmTC_16f14 > /usr/bin/ld: i386 architecture of input file > `CMakeFiles/cmTC_16f14.dir/src.cxx.o' is incompatible with i386:x86-64 output > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2022/12/20/volk_2.5.2-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=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. --- End Message --- --- Begin Message --- Source: volk Source-Version: 2.5.2-3 Done: A. Maitland Bottoms We believe that the bug you reported is fixed in the latest version of volk, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. A. Maitland Bottoms (supplier of updated volk package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 20 Dec 2022 20:03:23 -0500 Source: volk Architecture: source Version: 2.5.2-3 Distribution: unstable Urgency: medium Maintainer: A. Maitland Bottoms Changed-By: A. Maitland Bottoms Closes: 1026593 Changes: volk (2.5.2-3) unstable; urgency=medium . * orc 1:0.4.33-1 dropped building static library, so now volk will drop building its static library too. (Closes: #1026593) Checksums-Sha1: 8037f7538e8ff5623d1740bcf75983d0a0af1b01 2160 volk_2.5.2-3.dsc f7e5e651ad988af5cdc70ad64f4bff3c8b91ce46 16296 volk_2.5.2-3.debian.tar.xz fa9217b1ff0ac584fa50f447089e9619c49decee 11281 volk_2.5.2-3_amd64.buildinfo Checksums-Sha256: c6b2c216d6c2f51f32672913a4329305034d755f353c04d06d6ca325196afce6 2160 volk_2.5.2-3.dsc 84b1bf04f80f681c8e372c0544408dd8e09126e124e917af115d79f0056324d2 16296 volk_2.5.2-3.debian.tar.xz d213c0302a85ace3ce0514f591c08f49b0b93e1993bd850ebc6d670bb1d80bda 11281 volk_2.5.2-3_amd64.buildinfo Files: 7e43342d0e96a810f3d3f73ff432136a 2160 libdevel optional volk_2.5.2-3.dsc 5ef879ac77a29129d9c2d29063c654c5 16296 libdevel optional volk_2.5.2-3.debian.tar.xz e5bbefa5a1a71db377bbf6c6fab6a2f4 11281 libdevel optional volk_2.5.2-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAmOiXfMACgkQUEHxiR9E 4JC+RBAAuD/aB3W4scR0nh3Fpb7+uou9SW2fe5uzTf7ciCCHAZvhdyK9r/vdWv0n V7OGuiELR44MFqGnNcdyEYsKuUzyC483PT9GOme22SJoJnU7r1W0UnIoWBR0Tm3t ICURayjrXV9lN1iJF9r8ACagWpdbHzvwhKP7qKlrKxi8tNwYHin136f6qK6Mn40n 5HUqGVy2/+rOgxg6PISktUIz4tZ8ruNoODFj14S1woo/Ah8yYE3WTC3T7s8RPQx4 HJFBFlNzyk4GqwxrmjA+UbMtRRBIMcThlsyxRConYU45qE06jBnd/VK1AtrKTfOC i4kxW8oe0eEs/lgjv6TghlbU1ReydRtKSrAXT0KRwyoJsvsYGvC+pDCWNXDcC2gm mZpjy+zLli/Y+qFylOPgEfJiR+JZclZdoDExRb3YvtrhTQReKM552h9YFclDE20q kUMnZcivvuPyta7EiFxKLsT11NyZmPSqeEQmZ
Bug#1026442: marked as done (binutils-or1k-elf: FTBFS due to failed patch)
Your message dated Wed, 21 Dec 2022 01:49:51 + with message-id and subject line Bug#1026442: fixed in binutils-or1k-elf 1.0.7 has caused the Debian Bug report #1026442, regarding binutils-or1k-elf: FTBFS due to failed patch to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026442 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: binutils-or1k-elf Version: 1.0.6 Severity: serious Tags: ftbfs patch Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: i...@hack3r.moe Dear maintainer(s), binutils-or1k-elf recently failed to build due to failure applying patch: ``` make[1]: Entering directory '/<>' tar -xf /usr/src/binutils/binutils-*.tar.xz mv binutils* src patch -p0 < mbstowcs-null-size.diff patching file src/gas/read.c Hunk #1 FAILED at 1667. 1 out of 1 hunk FAILED -- saving rejects to file src/gas/read.c.rej make[1]: *** [debian/rules:31: src] Error 1 ``` The patch is being applied upstream (see PR 29447 [1]), so simply commenting out that patch command works just fine. I've included a patch to do so. If more help is needed, please let me know. Cheers, Eric [1]: https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=5858ac626e548772407c038b09b7837550b127dd --- a/debian/rules +++ b/debian/rules @@ -28,7 +28,8 @@ src: tar -xf $(tar_dir)/binutils-*.tar.xz mv binutils* src - patch -p0 < mbstowcs-null-size.diff +# Already fixed in source +# patch -p0 < mbstowcs-null-size.diff # _GCC_AUTOCONF_VERSION_CHECK in config/override.m4 requires 2.69. override_dh_autoreconf: --- End Message --- --- Begin Message --- Source: binutils-or1k-elf Source-Version: 1.0.7 Done: Nicolas Boulenguez We believe that the bug you reported is fixed in the latest version of binutils-or1k-elf, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Boulenguez (supplier of updated binutils-or1k-elf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 21 Dec 2022 00:17:44 + Source: binutils-or1k-elf Architecture: source Version: 1.0.7 Distribution: unstable Urgency: medium Maintainer: Nicolas Boulenguez Changed-By: Nicolas Boulenguez Closes: 1026442 Changes: binutils-or1k-elf (1.0.7) unstable; urgency=medium . * Autoreconf libiberty again (fixed in 2.39.50). * Standards-Version: 4.6.2 (no changes). * Update format of lintian overrides. * Update copyright years. . [ Eric Long ] * Remove mbstowcs patch (applied in 2.39.50). Closes: #1026442. Checksums-Sha1: c83a24b51846fe17358b0dec5ba22dca22d3f82e 1866 binutils-or1k-elf_1.0.7.dsc 2841af7b2662317c23bdaf1ea494a9c1d6ecf251 4780 binutils-or1k-elf_1.0.7.tar.xz Checksums-Sha256: 43a8743c3902f7bfa841c1f2d673ce0b26c8c333172a0b98ddf84b7a29fb1797 1866 binutils-or1k-elf_1.0.7.dsc f37ce741e7ccea44b8e654177d5778ab2aef1460b4353a2994812c55811fecfe 4780 binutils-or1k-elf_1.0.7.tar.xz Files: e5261609136b18ce6f088d1ea58875ae 1866 devel optional binutils-or1k-elf_1.0.7.dsc 470904b1e197a7c873886bae5d00a5e5 4780 devel optional binutils-or1k-elf_1.0.7.tar.xz -BEGIN PGP SIGNATURE- iQJHBAEBCAAxFiEEawm/6zYhqkfTAKHtFHKayZgPCdIFAmOiXr0THG5pY29sYXNA ZGViaWFuLm9yZwAKCRAUcprJmA8J0lT5EACm8F6ioAUuG68MqFmxD0EMTqmHoi9e hNv1e/cq268QIGxdsrC6RJnXh/2yGiEko3cJSNrPfEbS6sJJSHf3UDbWVGpnHxNY dHxGrhUgdRqtUtG7MRQ0yDnmhrKVbBDQB5TszufTHzjnGO0DZDi9TlwMw6XMUfoy HWtuyhsqg/tIqprh+i7JyPy9MpWJvg+1459InT6XHOUNgqO5jQr/VxnJ1cbBvuTL Ymta38gRDCqTBprs1SMpmPiUUJ8ad9/rmZzRFrD4Bph/n5wRMtRZOqSKAL93+o2d MyU05oNPit3+GXQlZdtKClUm2OOUoewuOv2iRIf1iCy9nDrmGV3lQFYcSwMbBAXZ ZgKqbEZE+qHwxzt0Fl9Kpatvx2Kc+0w/yiNsWjorhsXI97AJ57aiO+u7nSXYk28X IcjxU/kWfZZ4pR24JYOETkwDM5hcYGA4+slGXIm1/TN43j16RMr2Ou+ajIAXKeue pQhMATL+9rI5Svn1WXkIyyQo0O6+i5xluZRnnMxvHCoYVRITZ4bn+JbFq/F8F4Lw JXVcrK1Rohz1qd4ArYndw2BzxexGuuoyCH5HPThmwvK3DaKC+zOmI04CeQ9Lic8R 52OhtzxSAMN+OgKhTLP7t4oElU/K28kRXMAAAXRauTwsMI0DKf5v0rcGJRBQyvj9 mZTm89ihb0l/QQ== =ghgd -END PGP SIGNATURE End Message ---
Bug#1026779: binutils: cross binutils and foreign libbinutils not coinstallable, breaking upgrades
Source: binutils
Version: 2.39.50.20221208-5
Severity: serious
Dear Maintainer,
Up to src:binutils 2.39-8, binutils-${DEB_HOST_MULTIARCH} and
libbinutils:${DEB_HOST_ARCH} were coinstallable. Upgrading a system
where both are installed (e.g. binutils-aarch64-linux-gnu and
libbinutils:arm64) fails like this:
8<8<8<-
Unpacking libbinutils:arm64 (2.39.50.20221208-5) over (2.39-8) ...
Preparing to unpack
.../3-binutils-aarch64-linux-gnu_2.39.50.20221208-5_amd64.deb ...
Unpacking binutils-aarch64-linux-gnu (2.39.50.20221208-5) over (2.39-8) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-maU0ym/3-binutils-aarch64-linux-gnu_2.39.50.20221208-5_amd64.deb
(--unpack):
trying to overwrite '/usr/lib/aarch64-linux-gnu/libsframe.so.0.0.0', which is
also in package libbinutils:arm64 2.39.50.20221208-5
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Preparing to unpack .../4-binutils-common_2.39.50.20221208-5_amd64.deb ...
De-configuring binutils-common:arm64 (2.39-8), to allow configuration of
binutils-common:amd64 (2.39.50.20221208-5) ...
Unpacking binutils-common:amd64 (2.39.50.20221208-5) over (2.39-8) ...
Preparing to unpack .../5-binutils-common_2.39.50.20221208-5_arm64.deb ...
Unpacking binutils-common:arm64 (2.39.50.20221208-5) over (2.39-8) ...
Selecting previously unselected package libbinutils:amd64.
Preparing to unpack .../6-libbinutils_2.39.50.20221208-5_amd64.deb ...
Unpacking libbinutils:amd64 (2.39.50.20221208-5) ...
Selecting previously unselected package libjansson4:amd64.
Preparing to unpack .../7-libjansson4_2.14-2_amd64.deb ...
Unpacking libjansson4:amd64 (2.14-2) ...
Errors were encountered while processing:
/tmp/apt-dpkg-install-maU0ym/3-binutils-aarch64-linux-gnu_2.39.50.20221208-5_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
8<8<8<-
-- System Information:
Debian Release: bookworm/sid
APT prefers testing-debug
APT policy: (900, 'testing-debug'), (900, 'testing'), (500,
'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.0.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
LANGUAGE=pt_BR:pt:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-- no debconf information
signature.asc
Description: PGP signature
Bug#1026034: marked as done (diffoscope: failing autopkg tests)
Your message dated Tue, 20 Dec 2022 23:36:14 + with message-id and subject line Bug#1026034: fixed in diffoscope 229 has caused the Debian Bug report #1026034, regarding diffoscope: failing autopkg tests to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:diffoscope Version: 228 Severity: serious Tags: sid bookworm diffoscope's autopkg tests fail in unstable with: === FAILURES === __ test_diff ___ differences = /tmp/autopkgtest-lxc.vxtjt4v9/downtmp/autopkgtest_tmp/tests/data/test1.html -- /tmp/autopkgtest-lxc.vxtjt4v9/downtmp/autopkgtest_tmp/tests/data/test2.html []> def test_diff(differences): assert_diff(differences, "html_expected_diff") > assert_diff(differences.details[0], "html_text_expected_diff") E IndexError: list index out of range differences = /tmp/autopkgtest-lxc.vxtjt4v9/downtmp/autopkgtest_tmp/tests/data/test1.html -- /tmp/autopkgtest-lxc.vxtjt4v9/downtmp/autopkgtest_tmp/tests/data/test2.html []> tests/comparators/test_html.py:46: IndexError --- End Message --- --- Begin Message --- Source: diffoscope Source-Version: 229 Done: Chris Lamb We believe that the bug you reported is fixed in the latest version of diffoscope, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lamb (supplier of updated diffoscope package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 20 Dec 2022 23:12:16 + Source: diffoscope Built-For-Profiles: nocheck Architecture: source Version: 229 Distribution: unstable Urgency: medium Maintainer: Reproducible builds folks Changed-By: Chris Lamb Closes: 1026034 Changes: diffoscope (229) unstable; urgency=medium . [ Chris Lamb ] * Skip test_html.py::test_diff if html2text is not installed. (Closes: #1026034) . [ Holger Levsen ] * Bump standards version to 4.6.2, no changes needed. Checksums-Sha1: 1084605f41607e3b31257d652610e4ae03844f72 5130 diffoscope_229.dsc 3c352fd537ca34bc73a3d0f81db55a9e4f5338a5 2443272 diffoscope_229.tar.xz e44e56f2d2e8cce9944c20b9652fb327344c610e 7529 diffoscope_229_amd64.buildinfo Checksums-Sha256: 249d699de82fa3b4b15232c94275591c95eae230b449d6d4badb98dd9e76dbdd 5130 diffoscope_229.dsc 77c5275716d8b931d1ec0ca2b4f0c449dd96da018028bb8b2dfc1c7014e116d9 2443272 diffoscope_229.tar.xz 95288ccd95df6c802c8b925561b093f163e97d166c60062c41b5d50af7b1f68d 7529 diffoscope_229_amd64.buildinfo Files: ff58bef1d69225081f38593851e362df 5130 devel optional diffoscope_229.dsc a0a7a56ac31938c8c15fee23ac71f768 2443272 devel optional diffoscope_229.tar.xz 8220b03f15a0af6b43b14f14d8f910a7 7529 devel optional diffoscope_229_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAmOiQbAACgkQHpU+J9Qx Hljr/w/6Avj69Cuy/wbQmaIP6bu7nopHEJWEPHfnUcW/6Q9X51W8sQ5AM04xmpeM KoCdEkeUs3UVLv+hP2kpmbtxvOyuFLB5AJcXPk7Q6RwjojXO8wHwVn7Smfuie5r7 rFSYun8TTgtwUWzfUzZ6Ui0EwuxbHwIQNfBipwHPY9cPfdw5Rqc2JyEJki7TPX5X 45Wyrw5TvjjoFOkdPwxf+QIopSuplMs+GtReGWcR0RU0FxqkwpYZKa+DlM7jBalB Y5sqQzT8AlmTUVs8fNFIwb42R6ftlDxsCEeMewBIsC4kqkW7CK66UegsyOwpasNT 6ak/OpJ8onAqjUNOaVzPbEPZV7qR48z00Vj6csfOyj1+1viPgFA0420HNCx/XNLi KQjADw9bAkspHsrwKAiV/2i5x9lQYNaUTil7VIL6CU5wuUmzF/XJ+tYant3GEks6 DVDZe36lWpie6lT3CzeerNjJeBbdRn4sVxmk8lD7de9Lfwv6wY4CCb+w7qDjBZrQ IPzTVkVKplTFQVoxsLj598ytfAEsizBjn2H8hQH1w4o0ZGhgSEsjPwzKdvq4YgyT 41Xq1VFCxWReRYgJoNUuAnonJfcwP4qIVls3VnhmeRiUZABaihhnOedrndOm5yBu vp1+LzxY4jclHQ86lFygiG+WNbYrsfVnFjKTYLTMblfBAHnqueE= =Kpk/ -END PGP SIGNATURE End Message ---
Processed: severity of 981637 is serious
Processing commands for cont...@bugs.debian.org: > severity 981637 serious Bug #981637 [ifscheme] ifscheme: ifup no longer recognises interface names with ifscheme suffixes Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 981637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1026485: debian-installer: FTBFS: Failed to stat - stat (2: No such file or directory)
Processing control commands: > tag -1 patch pending Bug #1026485 [src:debian-installer] debian-installer: FTBFS: Failed to stat - stat (2: No such file or directory) Added tag(s) patch and pending. -- 1026485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026485 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026485: debian-installer: FTBFS: Failed to stat - stat (2: No such file or directory)
Control: tag -1 patch pending Lucas Nussbaum (2022-12-20): > Source: debian-installer > Version: 20220917 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20221220 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. We know, there's no need to open a bug report against debian-installer every time the Linux ABI is bumped. Cheers, -- Cyril Brulebois (k...@debian.org)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Bug#1026700: marked as done (snek: FTBFS: make[4]: *** [Makefile:73: lesson-4-washing-machine.pdf] Error 1)
Your message dated Tue, 20 Dec 2022 23:08:29 +
with message-id
and subject line Bug#1026700: fixed in ruby-asciidoctor-pdf 2.3.4-3
has caused the Debian Bug report #1026700,
regarding snek: FTBFS: make[4]: *** [Makefile:73: lesson-4-washing-machine.pdf]
Error 1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1026700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: snek
Version: 1.8-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering directory '/<>/doc/lessons/lesson-1'
> cp ../../../doc/snek.css snek.css
> cp ../../../doc/snek-theme.yml snek-theme.yml
> cp ../../../snek.svg snek.svg
> asciidoctor -v --attribute="revdate=2022-03-26" --attribute="version=1.8" -b
> html5 lesson-1-snekboard.adoc
> asciidoctor-pdf --attribute="revdate=2022-03-26" --attribute="version=1.8"
> --attribute='pdf-style=snek' lesson-1-snekboard.adoc
> asciidoctor: ERROR: failed to parse formatted text: = (reason:
> Expected one of [^<&], '<', '&', '= at byte 10)
> asciidoctor: ERROR: failed to parse formatted text: *= (reason:
> Expected one of 'br', 'img', 'a', 'strong', 'em', 'code', 'font', 'span',
> 'button', 'kbd', 'sup', 'sub', 'mark', 'menu', 'del' after < at byte 2)
> undefined method `imported_page?' for # @document=# return unless (content_start_page_number =
> state.pages[skip_pages..-1].index {|it| !it.imported_page? })
>
> ^^^
> Did you mean? imported_page
> Use --trace to show backtrace
> make[4]: *** [Makefile:73: lesson-4-washing-machine.pdf] Error 1
The full build log is available from:
http://qa-logs.debian.net/2022/12/20/snek_1.8-4_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=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.
--- End Message ---
--- Begin Message ---
Source: ruby-asciidoctor-pdf
Source-Version: 2.3.4-3
Done: Keith Packard
We believe that the bug you reported is fixed in the latest version of
ruby-asciidoctor-pdf, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1026...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Keith Packard (supplier of updated ruby-asciidoctor-pdf
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 20 Dec 2022 11:25:34 -0800
Source: ruby-asciidoctor-pdf
Architecture: source
Version: 2.3.4-3
Distribution: unstable
Urgency: medium
Maintainer: Keith Packard
Changed-By: Keith Packard
Closes: 1026652 1026700
Changes:
ruby-asciidoctor-pdf (2.3.4-3) unstable; urgency=medium
.
* Re-enable ruby-prawn-templates. (Closes: #1026652, #1026700).
Checksums-Sha1:
27b71fe1c9cf72faf2953d51dad97164295d07e6 2309 ruby-asciidoctor-pdf_2.3.4-3.dsc
4cbd16f8282d1f3a68be4ffc4d0ea932e39474f8 8000
ruby-asciidoctor-pdf_2.3.4-3.debian.tar.xz
b4f0665cd83751bbaf770e8de98742fc90a9ffc5 10492
ruby-asciidoctor-pdf_2.3.4-3_amd64.buildinfo
Checksums-Sha256:
14625cb94d3e6793762eb4b84c6e6c17f4e098f670e4a89cecc5cd06c44cb5a7 2309
ruby-asciidoctor-pdf_2.3.4-3.dsc
3dc828c79dcfc1a929040ead9ed74fd3bf59fd2692527306972c03302be3dd7b 8000
ruby-asciidoctor-pd
Bug#1026652: marked as done (nickle: FTBFS: make[4]: *** [Makefile:490: nickle-tutorial.pdf] Error 1)
Your message dated Tue, 20 Dec 2022 23:08:29 +
with message-id
and subject line Bug#1026652: fixed in ruby-asciidoctor-pdf 2.3.4-3
has caused the Debian Bug report #1026652,
regarding nickle: FTBFS: make[4]: *** [Makefile:490: nickle-tutorial.pdf] Error
1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1026652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nickle
Version: 2.91
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering directory '/<>/doc/tutorial'
> asciidoctor-pdf -o nickle-tutorial.pdf nickle-tutorial.adoc
> undefined method `imported_page?' for # @document=# @backend_traits={:basebackend=>"html", :filetype=>"pdf", :htmlsyntax=>"html",
> :outfilesuffix=>".pdf"}, @label=:primary,
> @initial_instance_variables=[:@initial_instance_variables, :@backend,
> :@backend_traits,
> [...]
> return unless (content_start_page_number =
> state.pages[skip_pages..-1].index {|it| !it.imported_page? })
>
> ^^^
> Did you mean? imported_page
> Use --trace to show backtrace
> make[4]: *** [Makefile:490: nickle-tutorial.pdf] Error 1
The full build log is available from:
http://qa-logs.debian.net/2022/12/20/nickle_2.91_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=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.
--- End Message ---
--- Begin Message ---
Source: ruby-asciidoctor-pdf
Source-Version: 2.3.4-3
Done: Keith Packard
We believe that the bug you reported is fixed in the latest version of
ruby-asciidoctor-pdf, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1026...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Keith Packard (supplier of updated ruby-asciidoctor-pdf
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 20 Dec 2022 11:25:34 -0800
Source: ruby-asciidoctor-pdf
Architecture: source
Version: 2.3.4-3
Distribution: unstable
Urgency: medium
Maintainer: Keith Packard
Changed-By: Keith Packard
Closes: 1026652 1026700
Changes:
ruby-asciidoctor-pdf (2.3.4-3) unstable; urgency=medium
.
* Re-enable ruby-prawn-templates. (Closes: #1026652, #1026700).
Checksums-Sha1:
27b71fe1c9cf72faf2953d51dad97164295d07e6 2309 ruby-asciidoctor-pdf_2.3.4-3.dsc
4cbd16f8282d1f3a68be4ffc4d0ea932e39474f8 8000
ruby-asciidoctor-pdf_2.3.4-3.debian.tar.xz
b4f0665cd83751bbaf770e8de98742fc90a9ffc5 10492
ruby-asciidoctor-pdf_2.3.4-3_amd64.buildinfo
Checksums-Sha256:
14625cb94d3e6793762eb4b84c6e6c17f4e098f670e4a89cecc5cd06c44cb5a7 2309
ruby-asciidoctor-pdf_2.3.4-3.dsc
3dc828c79dcfc1a929040ead9ed74fd3bf59fd2692527306972c03302be3dd7b 8000
ruby-asciidoctor-pdf_2.3.4-3.debian.tar.xz
71d18636bf631e9a388745d46748e48f4ca94e3ec3e1725c7c198d7b576d163b 10492
ruby-asciidoctor-pdf_2.3.4-3_amd64.buildinfo
Files:
1ad2592b539f29fbffd337c6a72635ad 2309 ruby optional
ruby-asciidoctor-pdf_2.3.4-3.dsc
cb740c208cc40d19771c37b032353f3e 8000 ruby optional
ruby-asciidoctor-pdf_2.3.4-3.debian.tar.xz
3feb35f8d297b7316082ff826443ec5c 10492 ruby optional
ruby-asciidoctor-pdf_2.3.4-3_amd64.buildi
Processed: Please make liblog4j2-java depend on junit5
Processing control commands: > retitle -1 Please make liblog4j2-java depend on junit5 Bug #102 [apache-log4j2] barclay: FTBFS: make[1]: *** [debian/rules:23: override_dh_auto_build] Error 25 Bug #1026668 [apache-log4j2] picard-tools: FTBFS: make[1]: *** [debian/rules:15: override_dh_auto_build] Error 25 Changed Bug title to 'Please make liblog4j2-java depend on junit5' from 'barclay: FTBFS: make[1]: *** [debian/rules:23: override_dh_auto_build] Error 25'. Changed Bug title to 'Please make liblog4j2-java depend on junit5' from 'picard-tools: FTBFS: make[1]: *** [debian/rules:15: override_dh_auto_build] Error 25'. -- 102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=102 1026668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026668 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026666: Please make liblog4j2-java depend on junit5
Control: retitle -1 Please make liblog4j2-java depend on junit5 Hello, In version 2.19.0-1 of liblog4j2-java, the file /usr/share/maven-repo/org/apache/logging/log4j/log4j/debian/log4j-debian.pom declares the junit-bom artifact as a dependency. It is shipped in junit5. If this dependency is not added, reverse dependencies of liglog4j2-java fail to build (see logs above) as the junit-bom artifact is not found. Cheers, -- Pierre OpenPGP_signature Description: OpenPGP digital signature
Processed: affects 1026666
Processing commands for cont...@bugs.debian.org: > affects 102 picard-tools Bug #102 [apache-log4j2] barclay: FTBFS: make[1]: *** [debian/rules:23: override_dh_auto_build] Error 25 Bug #1026668 [apache-log4j2] picard-tools: FTBFS: make[1]: *** [debian/rules:15: override_dh_auto_build] Error 25 Added indication that 102 affects picard-tools Added indication that 1026668 affects picard-tools > thanks Stopping processing here. Please contact me if you need assistance. -- 102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=102 1026668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026668 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 1026666 1026668
Processing commands for cont...@bugs.debian.org: > forcemerge 102 1026668 Bug #102 [apache-log4j2] barclay: FTBFS: make[1]: *** [debian/rules:23: override_dh_auto_build] Error 25 Bug #1026668 [apache-log4j2] picard-tools: FTBFS: make[1]: *** [debian/rules:15: override_dh_auto_build] Error 25 Removed indication that 1026668 affects picard-tools Added indication that 1026668 affects barclay Merged 102 1026668 > thanks Stopping processing here. Please contact me if you need assistance. -- 102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=102 1026668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026668 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): your mail
Processing commands for cont...@bugs.debian.org: > reassign 102 apache-log4j2 2.19.0-1 Bug #102 [src:barclay] barclay: FTBFS: make[1]: *** [debian/rules:23: override_dh_auto_build] Error 25 Bug reassigned from package 'src:barclay' to 'apache-log4j2'. No longer marked as found in versions barclay/4.1.0+dfsg-1. Ignoring request to alter fixed versions of bug #102 to the same values previously set Bug #102 [apache-log4j2] barclay: FTBFS: make[1]: *** [debian/rules:23: override_dh_auto_build] Error 25 There is no source info for the package 'apache-log4j2' at version '2.19.0-1' with architecture '' Unable to make a source version for version '2.19.0-1' Marked as found in versions 2.19.0-1. > reassign 1026668 apache-log4j2 2.19.0-1 Bug #1026668 [src:picard-tools] picard-tools: FTBFS: make[1]: *** [debian/rules:15: override_dh_auto_build] Error 25 Bug reassigned from package 'src:picard-tools' to 'apache-log4j2'. No longer marked as found in versions picard-tools/2.27.5+dfsg-2. Ignoring request to alter fixed versions of bug #1026668 to the same values previously set Bug #1026668 [apache-log4j2] picard-tools: FTBFS: make[1]: *** [debian/rules:15: override_dh_auto_build] Error 25 There is no source info for the package 'apache-log4j2' at version '2.19.0-1' with architecture '' Unable to make a source version for version '2.19.0-1' Marked as found in versions 2.19.0-1. > affects 102 barclay Bug #102 [apache-log4j2] barclay: FTBFS: make[1]: *** [debian/rules:23: override_dh_auto_build] Error 25 Added indication that 102 affects barclay > affects 1026668 picard-tools Bug #1026668 [apache-log4j2] picard-tools: FTBFS: make[1]: *** [debian/rules:15: override_dh_auto_build] Error 25 Added indication that 1026668 affects picard-tools > merge 102 1026668 Bug #102 [apache-log4j2] barclay: FTBFS: make[1]: *** [debian/rules:23: override_dh_auto_build] Error 25 Unable to merge bugs because: affects of #1026668 is 'picard-tools' not 'barclay' Failed to merge 102: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=102 1026668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026668 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Set spectral_cube bug forwarded
Processing commands for cont...@bugs.debian.org:
> forwarded 1026720
> https://github.com/radio-astro-tools/spectral-cube/issues/853
Bug #1026720 [src:spectral-cube] spectral-cube: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit
code 13
Set Bug forwarded-to-address to
'https://github.com/radio-astro-tools/spectral-cube/issues/853'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1026720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#670739: marked as done ([PATCH] lifelines: Helping to update to packaging format 3.0)
Your message dated Tue, 20 Dec 2022 22:21:13 +
with message-id
and subject line Bug#670739: fixed in lifelines 3.0.61-2.2
has caused the Debian Bug report #670739,
regarding [PATCH] lifelines: Helping to update to packaging format 3.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
670739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lifelines
Severity: wishlist
Tags: patch
Hi,
The dpatch patch management system has been deprecated for some time. The
Lintian currently flags use of dpatch packages as an error. The new 3.0
packaging format is an improved version which, among other things, contains
patch management built-in. For more information, see:
http://wiki.debian.org/Projects/DebSrc3.0
I had some free time; see attached patch to migrate to new package
format. Note that all files in debian/patches/* are canocalized to
*.patch.
Let me know if there is anything that needs adjusting or if it is ok
to upload this version in a NMU in case you are working on other
issues needing attention.
Thanks,
Jari
>From e73c9230e3f193c51bb8c1de0c2ab4b081cabe12 Mon Sep 17 00:00:00 2001
From: Jari Aalto
Date: Sat, 28 Apr 2012 18:45:46 +0300
Subject: [PATCH] format-3.0
Organization: Private
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Signed-off-by: Jari Aalto
---
debian/changelog | 10
debian/compat |2 +-
debian/control |4 +-
debian/copyright |2 +-
debian/patches/00list |4 --
...akefile.in.dpatch => 01-docs-Makefile.in.patch} | 26 +--
debian/patches/02-Makefile.am.patch| 15 ++
debian/patches/02_Makefile.am.dpatch | 37 ---
...{03_Makefile.in.dpatch => 03-Makefile.in.patch} | 26 +--
debian/patches/04-docs-ll-userguide.xml.patch | 15 ++
debian/patches/04_docs-ll-userguide.xml.dpatch | 37 ---
debian/patches/series |4 ++
debian/rules | 48 ++--
debian/source/format |1 +
14 files changed, 68 insertions(+), 163 deletions(-)
delete mode 100644 debian/patches/00list
rename debian/patches/{01_docs-Makefile.in.dpatch => 01-docs-Makefile.in.patch} (57%)
create mode 100644 debian/patches/02-Makefile.am.patch
delete mode 100644 debian/patches/02_Makefile.am.dpatch
rename debian/patches/{03_Makefile.in.dpatch => 03-Makefile.in.patch} (60%)
create mode 100644 debian/patches/04-docs-ll-userguide.xml.patch
delete mode 100644 debian/patches/04_docs-ll-userguide.xml.dpatch
create mode 100644 debian/patches/series
create mode 100644 debian/source/format
diff --git a/debian/changelog b/debian/changelog
index e74f469..fbd0c85 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+lifelines (3.0.61-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Remove deprecated dpatch and upgrade to packaging format "3.0 quilt".
+ * Update to Standards-Version to 3.9.3 and debhelper to 9.
+ * Add required build-arch and build-indep targets to rules file.
+ * Add note to copyright file about unreachable upstream URL.
+
+ -- Jari Aalto Sat, 28 Apr 2012 18:45:23 +0300
+
lifelines (3.0.61-2) unstable; urgency=low
* The "let's modernize this package a bit" release
diff --git a/debian/compat b/debian/compat
index 45a4fb7..ec63514 100644
--- a/debian/compat
+++ b/debian/compat
@@ -1 +1 @@
-8
+9
diff --git a/debian/control b/debian/control
index 7311b52..117a41d 100644
--- a/debian/control
+++ b/debian/control
@@ -3,8 +3,8 @@ Section: misc
Priority: optional
Maintainer: Felipe Augusto van de Wiel (faw)
Uploaders: Christian Perrier
-Build-Depends: libncursesw5-dev, bison, debhelper (>= 8), sgmltools-lite, docbook-utils, ghostscript, autoconf (>= 2.5), autotools-dev, devscripts, dh-buildinfo, dpatch, lynx
-Standards-Version: 3.9.2
+Build-Depends: libncursesw5-dev, bison, debhelper (>= 9), sgmltools-lite, docbook-utils, ghostscript, autoconf (>= 2.5), autotools-dev, devscripts, dh-buildinfo, lynx
+Standards-Version: 3.9.3
Package: lifelines
Architecture: any
diff --git a/debian/copyright b/debian/copyright
index 93b1e4a..b70d0a2 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -2,7 +2,7 @@ This is Debian GNU/Linux's prepackaged version of the
Bug#670739: [PATCH] lifelines: Helping to update to packaging format 3.0
I am uploading a NMU to fix this. debdiff is attached.diff -Nru lifelines-3.0.61/build/autotools/config.guess
lifelines-3.0.61/build/autotools/config.guess
--- lifelines-3.0.61/build/autotools/config.guess 2022-12-20
23:13:58.0 +0100
+++ lifelines-3.0.61/build/autotools/config.guess 2002-06-25
04:13:27.0 +0200
@@ -1,10 +1,9 @@
#! /bin/sh
# Attempt to guess a canonical system name.
# Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
-# 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
-# 2011 Free Software Foundation, Inc.
+# 2000, 2001, 2002 Free Software Foundation, Inc.
-timestamp='2011-05-11'
+timestamp='2002-03-04'
# This file is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by
@@ -18,25 +17,23 @@
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
-# Foundation, Inc., 51 Franklin Street - Fifth Floor, Boston, MA
-# 02110-1301, USA.
+# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
#
# As a special exception to the GNU General Public License, if you
# distribute this file as part of a program that contains a
# configuration script generated by Autoconf, you may include it under
# the same distribution terms that you use for the rest of that program.
-
-# Originally written by Per Bothner. Please send patches (context
-# diff format) to and include a ChangeLog
-# entry.
+# Originally written by Per Bothner .
+# Please send patches to . Submit a context
+# diff and a properly formatted ChangeLog entry.
#
# This script attempts to guess a canonical system name similar to
# config.sub. If it succeeds, it prints the system name on stdout, and
# exits with 0. Otherwise, it exits with 1.
#
-# You can get the latest version of this script from:
-#
http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD
+# The plan is that this can be called by configure scripts if you
+# don't specify an explicit build system type.
me=`echo "$0" | sed -e 's,.*/,,'`
@@ -56,9 +53,8 @@
GNU config.guess ($timestamp)
Originally written by Per Bothner.
-Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000,
-2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011 Free
-Software Foundation, Inc.
+Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001
+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."
@@ -70,11 +66,11 @@
while test $# -gt 0 ; do
case $1 in
--time-stamp | --time* | -t )
- echo "$timestamp" ; exit ;;
+ echo "$timestamp" ; exit 0 ;;
--version | -v )
- echo "$version" ; exit ;;
+ echo "$version" ; exit 0 ;;
--help | --h* | -h )
- echo "$usage"; exit ;;
+ echo "$usage"; exit 0 ;;
-- ) # Stop option processing
shift; break ;;
- )# Use stdin as input.
@@ -92,42 +88,30 @@
exit 1
fi
-trap 'exit 1' 1 2 15
-# CC_FOR_BUILD -- compiler used by this script. Note that the use of a
-# compiler to aid in system detection is discouraged as it requires
-# temporary files to be created and, as you can see below, it is a
-# headache to deal with in a portable fashion.
+dummy=dummy-$$
+trap 'rm -f $dummy.c $dummy.o $dummy.rel $dummy; exit 1' 1 2 15
+# CC_FOR_BUILD -- compiler used by this script.
# Historically, `CC_FOR_BUILD' used to be named `HOST_CC'. We still
# use `HOST_CC' if defined, but it is deprecated.
-# Portable tmp directory creation inspired by the Autoconf team.
-
-set_cc_for_build='
-trap "exitcode=\$?; (rm -f \$tmpfiles 2>/dev/null; rmdir \$tmp 2>/dev/null) &&
exit \$exitcode" 0 ;
-trap "rm -f \$tmpfiles 2>/dev/null; rmdir \$tmp 2>/dev/null; exit 1" 1 2 13 15
;
-: ${TMPDIR=/tmp} ;
- { tmp=`(umask 077 && mktemp -d "$TMPDIR/cgXX") 2>/dev/null` && test -n
"$tmp" && test -d "$tmp" ; } ||
- { test -n "$RANDOM" && tmp=$TMPDIR/cg$$-$RANDOM && (umask 077 && mkdir $tmp)
; } ||
- { tmp=$TMPDIR/cg-$$ && (umask 077 && mkdir $tmp) && echo "Warning: creating
insecure temp directory" >&2 ; } ||
- { echo "$me: cannot create a temporary directory in $TMPDIR" >&2 ; exit 1 ; }
;
-dummy=$tmp/dummy ;
-tmpfiles="$dummy.c $dummy.o $dummy.rel $dummy" ;
-case $CC_FOR_BUILD,$HOST_CC,$CC in
- ,,)echo "int x;" > $dummy.c ;
- for c in cc gcc c89 c99 ; do
- if ($c -c -o $dummy.o $dummy.c) >/dev/null 2>&1 ; then
+set_cc_for_build='case $CC_FOR_BUILD,$HOST_CC,$CC in
+ ,,)echo "int dummy(){}" > $dummy.c ;
+ for c in cc gcc c89 ; do
+ ($c $dummy.c -c -o $dummy.o) >/dev/null 2>&1 ;
+ if test $? = 0 ; then
CC_FOR_BUILD="$c"; break ;
fi ;
done ;
+ rm -f $dummy.c $dummy.o $dummy.rel ;
Processed: Set specutils bug forwarded
Processing commands for cont...@bugs.debian.org:
> forwarded 1026504 https://github.com/astropy/specutils/issues/993
Bug #1026504 [src:specutils] specutils: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13
Set Bug forwarded-to-address to
'https://github.com/astropy/specutils/issues/993'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1026504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reassign 1026462 to src:linux, tagging 1026383, tagging 1026696, tagging 1026539, tagging 1013021 ...
Processing commands for cont...@bugs.debian.org:
> reassign 1026462 src:linux 6.1.0-2
Bug #1026462 [linux-image-6.1.0] linux-image-6.1.0: cannot control the keyboard
leds
Warning: Unknown package 'linux-image-6.1.0'
Bug reassigned from package 'linux-image-6.1.0' to 'src:linux'.
No longer marked as found in versions 6.1.0-2.
Ignoring request to alter fixed versions of bug #1026462 to the same values
previously set
Bug #1026462 [src:linux] linux-image-6.1.0: cannot control the keyboard leds
The source 'linux' and version '6.1.0-2' do not appear to match any binary
packages
Marked as found in versions linux/6.1.0-2.
> tags 1026383 + sid bookworm
Bug #1026383 [src:haskell-simple-templates] Removal notice: obsolete
Added tag(s) bookworm and sid.
> tags 1026696 - sid bookworm
Bug #1026696 [src:golang-github-prometheus-client-model]
golang-github-prometheus-client-model: FTBFS: make: *** [debian/rules:6:
binary] Error 25
Removed tag(s) bookworm and sid.
> tags 1026539 - sid bookworm
Bug #1026539 [src:theano] theano: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.10 returned exit code 13
Removed tag(s) bookworm and sid.
> tags 1013021 - sid bookworm
Bug #1013021 {Done: Gudjon I. Gudjonsson } [src:qscintilla2]
qscintilla2: ftbfs with GCC-12
Removed tag(s) sid and bookworm.
> tags 1026198 + sid
Bug #1026198 [src:ruby-webpack-rails] ruby-webpack-rails: FTBFS in bookworm
(missing build-depends on tzdata)
Added tag(s) sid.
> tags 1026197 - bookworm
Bug #1026197 [src:ruby-webpacker] ruby-webpacker: FTBFS in bookworm (missing
build-depends on tzdata)
Removed tag(s) bookworm.
> tags 1026196 + sid
Bug #1026196 [src:ruby-voight-kampff] ruby-voight-kampff: FTBFS in bookworm
(missing build-depends on tzdata)
Added tag(s) sid.
> tags 1026195 - bookworm
Bug #1026195 [src:ruby-sprockets-rails] ruby-sprockets-rails: FTBFS in bookworm
(missing build-depends on tzdata)
Removed tag(s) bookworm.
> tags 1026194 - bookworm
Bug #1026194 [src:ruby-sassc-rails] ruby-sassc-rails: FTBFS in bookworm
(missing build-depends on tzdata)
Removed tag(s) bookworm.
> tags 1026193 - bookworm
Bug #1026193 [src:ruby-rails-controller-testing] ruby-rails-controller-testing:
FTBFS in bookworm (missing build-depends on tzdata)
Removed tag(s) bookworm.
> tags 1026192 + sid
Bug #1026192 [src:ruby-pry-rails] ruby-pry-rails: FTBFS in bookworm (missing
build-depends on tzdata)
Added tag(s) sid.
> tags 1026191 - bookworm
Bug #1026191 [src:ruby-omniauth-rails-csrf-protection]
ruby-omniauth-rails-csrf-protection: FTBFS in bookworm (missing build-depends
on tzdata)
Removed tag(s) bookworm.
> tags 1026190 - bookworm
Bug #1026190 [src:ruby-joiner] ruby-joiner: FTBFS in bookworm (missing
build-depends on tzdata)
Removed tag(s) bookworm.
> tags 1026189 - bookworm
Bug #1026189 [src:ruby-invisible-captcha] ruby-invisible-captcha: FTBFS in
bookworm (missing build-depends on tzdata)
Removed tag(s) bookworm.
> tags 1026188 - bookworm
Bug #1026188 [src:ruby-haml] ruby-haml: FTBFS in bookworm (missing
build-depends on tzdata)
Removed tag(s) bookworm.
> tags 1026187 - bookworm
Bug #1026187 [src:ruby-globalid] ruby-globalid: FTBFS in bookworm (missing
build-depends on tzdata)
Removed tag(s) bookworm.
> tags 1026186 - bookworm
Bug #1026186 [src:ruby-factory-bot-rails] ruby-factory-bot-rails: FTBFS in
bookworm (missing build-depends on tzdata)
Removed tag(s) bookworm.
> tags 1026185 - bookworm
Bug #1026185 [src:ruby-enumerize] ruby-enumerize: FTBFS in bookworm (missing
build-depends on tzdata)
Removed tag(s) bookworm.
> tags 1026184 - bookworm
Bug #1026184 [src:ruby-combustion] ruby-combustion: FTBFS in bookworm (missing
build-depends on tzdata)
Removed tag(s) bookworm.
> tags 1026183 + sid
Bug #1026183 [src:ruby-coffee-rails] ruby-coffee-rails: FTBFS in bookworm
(missing build-depends on tzdata)
Added tag(s) sid.
> tags 1026182 + sid
Bug #1026182 [src:ruby-browser] ruby-browser: FTBFS in bookworm (missing
build-depends on tzdata)
Added tag(s) sid.
> tags 1026181 - bookworm
Bug #1026181 [src:ruby-arbre] ruby-arbre: FTBFS in bookworm (missing
build-depends on tzdata)
Removed tag(s) bookworm.
> tags 1026180 - bookworm
Bug #1026180 [src:ruby-ahoy-email] ruby-ahoy-email: FTBFS in bookworm (missing
build-depends on tzdata)
Removed tag(s) bookworm.
> tags 1026179 - bookworm
Bug #1026179 [src:ruby-active-model-serializers] ruby-active-model-serializers:
FTBFS in bookworm (missing build-depends on tzdata)
Removed tag(s) bookworm.
> tags 1026178 - bookworm
Bug #1026178 [src:redmine] redmine: FTBFS in bookworm (missing build-depends on
tzdata)
Removed tag(s) bookworm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1013021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013021
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
1026179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026179
1026180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026180
1026181:
Bug#1026754: marked as done (mtree-netbsd: FTBFS: make[1]: *** [debian/rules:41: override_dh_auto_test] Error 2)
Your message dated Tue, 20 Dec 2022 22:07:44 + with message-id and subject line Bug#1026754: fixed in mtree-netbsd 20180822-7 has caused the Debian Bug report #1026754, regarding mtree-netbsd: FTBFS: make[1]: *** [debian/rules:41: override_dh_auto_test] Error 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026754 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mtree-netbsd Version: 20180822-6.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > # Removing the next two to avoid dependency on freebsd-buildutils, > # which is currently blocking transition of this package into testing, > # per #957230. > #fmtree -c -K > cksum,md5digest,sha1digest,sha256digest,rmd160,nlink,gname,uname | ./mtree > #./mtree -c -K > cksum,md5digest,sha1digest,sha256digest,rmd160,nlink,gname,uname | sed -e > 's/\(md5\|sha1\|sha256\|sha384\|sha512\)=/\1digest=/' -e > 's/rmd160=/ripemd160digest=/' | fmtree > bsdtar -cf - --options > 'mtree:uname,gname,md5,sha1,sha256,sha384,sha512,device,flags,gid,link,mode,nlink,size,time,uid,type,uname' > --format mtree . | ./mtree > spec.o: sha256 > (0x7a4a7834b37d7d71319897cb9d249e2843edb772740f99f66fabccf25bee2a58, > 0x99dae58808228095c2ba38b0e530f67402ca16ba0255762b91a4b3e3dd573abd) > excludes.c: > sha256 > (0x77c7bb085755e3e7395b5285a7778194b325cc212f8c14fdf5af3f32471e96a4, > 0x6a689a5fa3e6f150bdfac6e706dac38cc83bb86753776460fafe9552cc3b38a6) > getid.c: > sha256 > (0xc98dfe3032f6817feb0c310e52a77b2bb59269727d598f6fc72cd82924e65b91, > 0x4f8be49a24273ded845507929457f482423f904759b783f52fdde21aee034e16) > pack_dev.o: > sha256 > (0x4690bdb2490698407f0a4ef0a14ac1a473aaf57f91596dcd45c8c2d7f42b6125, > 0xe5d0eb943ba3ead8bc5e10bad238ecfda8db65140ce1432ca6874bbd99615133) > config.sub: > sha256 > (0xdeb02c26f43b2ea64276c9ede77ec0f53d08e6256710f3c0a12275712085c348, > 0x02bb01deb64a5ebcebdd47069a54f18be83e56816f118b097ef814cf85117b66) > .pc/.version: > sha256 > (0x53c234e5e8472b6ac51c1ae1cab3fe06fad053beb8ebfd8977b010655bfdd3c3, > 0x5c93dc903b17c3903e27b6dd712047f8264dcdd45a133a36e9e6c1f7e694e2a2) > .pc/debian.patch/spec.c: > sha256 > (0x31dfe13fcd485b15c30ca2e195de22de1a901d21e3ca96b9c3b597588d86e30b, > 0xbbb528a9715e4d9c9cb752edd84386f499bc70a6bf664a016f887fa24cf6d360) > .pc/debian.patch/pack_dev.c: > sha256 > (0x12896cf68b7d6267789c9e2eef64038344d527ee7854ce9f2677ded9ab1552cd, > 0x356a4a5df146b2b3062c62fe6a41a07c5d56b8ef5e7f0c34a0fd87c8d09a3bde) > .pc/applied-patches: > sha256 > (0x2a46e98fa8cbc033d2916091452280f2553ffa85efa62579c0db7158e4e850af, > 0x4a34d8e9dff4b004c46c01d07159dd8e68308065acfce92deea898c74ad7a462) > .pc/.quilt_patches: > sha256 > (0x0623de532bc23399e87e6c1914e8e90e999efbfd26b6b95a493893739f0d, > 0x14e41fe34acb1d5ce4b8afc66e6730c454dfb8599c25ed7f9c743927ec28df0d) > .pc/.quilt_series: > sha256 > (0x9afbb183d1b683d2770aecb9b379093804ccc56027f07ecf7fc252d5b93a8df2, > 0x76f69701bcc9cd67410afbadf393e11d3ef412f356763a524a3af2dd5a45bee8) > stat_flags.c: > sha256 > (0x8a4f1c0719834892e811a584e359ce58bf642d39109c2463dfb39f4df2a9cbb7, > 0x9d08b68ebc324300a86ecb82159d9c14fd0bbf2174cd379d6b871005dfdc77c8) > verify.c: > sha256 > (0x4e3a378a8f62ce904bbc12c5d38abf90c5f19de98828d502d1ca3def6d65038c, > 0x025e509ee786c978754e4405dbdb77b2fffb8a2662c1344f92d70376ff474055) > compare.o: > sha256 > (0x69617c3faf5df5a6355abd02c19027443d0c27d8651f351f3aa138b65b0b, > 0xe38bc5113f4b6df153e975369aa7c19f79fb9c9822117d716de452afe22d8227) > verify.o: > sha256 > (0xea8d0c4386b15bbd12d56ff26bf1967d8a62a9305a7ed114934b8f0c8ca15b8d, > 0xb20d16d6007358490abeb99ea620ec178a4bd08099a6cbce936f962f4cd00f96) > config.guess.dh-orig: > sha256 > (0xcf610daf8afdedbf2110abd79bdd4121d59080cab5ec46deaf67f97273bb6bda, > 0xe33921a591c6e2409ebfe6eb3f763d16c87c8a317a2b2c4db9e1f9907762b0fb) > Makefile: > sha256 > (0x1c6d768cd2f8688655329f061939e79a01364d78cc528a7f99c519b3ffd54db2, > 0xd7b403c32b6a90de7af
Bug#1023697: Keep out of testing
Am Wed, Nov 16, 2022 at 03:27:53PM +0100 schrieb Jan Altenberg: > On Thu, 10 Nov 2022 22:45:57 +0100 Bastian Germann wrote: > > As a new maintainer has stepped up, this cannot be the reason anymore > > to dump the package. Actually, with the next version of swupdate (one > > of those handful) I wanted to switch from OpenSSL to SWUpdate. > > We're glad to hear, there's a new maintainer. > > > It would also be interesting for Debian's downstreams who take a > > different approach to combining OpenSSL with GPL-2-only packages > > (licenses are incompatible, which Debian heals with the application of > > the GPL-built-in system library exception). Ubuntu and probably others > > do not take the same stand and wolfSSL is really the only TLS > > library that has a usable OpenSSL compatibility layer. > > > > If it helps, I can support the new maintainer > > OSADL is supporting Bastian with his work on SWUpdate. Quite a few of our > members are concerned about the license incompatibility issue mentioned > above. OSADL can relicense swupdate to GPL-2.0+ or GPL3.0 to address this, has that been considered/is it being worked on? Cheers, Moritz
Bug#1026712: marked as done (wtforms-components: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13)
Your message dated Tue, 20 Dec 2022 21:55:14 +
with message-id
and subject line Bug#1026712: fixed in wtforms-components 0.10.5-4
has caused the Debian Bug report #1026712,
regarding wtforms-components: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.11 3.10" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1026712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wtforms-components
Version: 0.10.5-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> pybuild --build -i python{version} -p "3.11 3.10"
> I: pybuild base:240: /usr/bin/python3.11 setup.py build
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508:
> SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use
> license_files instead.
> warnings.warn(msg, warning_class)
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.11_wtforms-components/build/wtforms_components
> copying wtforms_components/__init__.py ->
> /<>/.pybuild/cpython3_3.11_wtforms-components/build/wtforms_components
> copying wtforms_components/validators.py ->
> /<>/.pybuild/cpython3_3.11_wtforms-components/build/wtforms_components
> copying wtforms_components/_compat.py ->
> /<>/.pybuild/cpython3_3.11_wtforms-components/build/wtforms_components
> copying wtforms_components/widgets.py ->
> /<>/.pybuild/cpython3_3.11_wtforms-components/build/wtforms_components
> copying wtforms_components/utils.py ->
> /<>/.pybuild/cpython3_3.11_wtforms-components/build/wtforms_components
> creating
> /<>/.pybuild/cpython3_3.11_wtforms-components/build/wtforms_components/fields
> copying wtforms_components/fields/__init__.py ->
> /<>/.pybuild/cpython3_3.11_wtforms-components/build/wtforms_components/fields
> copying wtforms_components/fields/html5.py ->
> /<>/.pybuild/cpython3_3.11_wtforms-components/build/wtforms_components/fields
> copying wtforms_components/fields/ajax.py ->
> /<>/.pybuild/cpython3_3.11_wtforms-components/build/wtforms_components/fields
> copying wtforms_components/fields/time.py ->
> /<>/.pybuild/cpython3_3.11_wtforms-components/build/wtforms_components/fields
> copying wtforms_components/fields/color.py ->
> /<>/.pybuild/cpython3_3.11_wtforms-components/build/wtforms_components/fields
> copying wtforms_components/fields/split_date_time.py ->
> /<>/.pybuild/cpython3_3.11_wtforms-components/build/wtforms_components/fields
> copying wtforms_components/fields/passive_hidden.py ->
> /<>/.pybuild/cpython3_3.11_wtforms-components/build/wtforms_components/fields
> copying wtforms_components/fields/select.py ->
> /<>/.pybuild/cpython3_3.11_wtforms-components/build/wtforms_components/fields
> copying wtforms_components/fields/select_multiple.py ->
> /<>/.pybuild/cpython3_3.11_wtforms-components/build/wtforms_components/fields
> copying wtforms_components/fields/json_field.py ->
> /<>/.pybuild/cpython3_3.11_wtforms-components/build/wtforms_components/fields
> copying wtforms_components/fields/interval.py ->
> /<>/.pybuild/cpython3_3.11_wtforms-components/build/wtforms_components/fields
> running egg_info
> creating WTForms_Components.egg-info
> writing WTForms_Components.egg-info/PKG-INFO
> writing dependency_links to WTForms_Components.egg-info/dependency_links.txt
> writing requirements to WTForms_Components.egg-info/requires.txt
> writing top-level names to WTForms_Components.egg-info/top_level.txt
> writing manifest file 'WTForms_Components.egg-info/SOURCES.txt'
> reading manifest file 'WTForms_Components.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '*.pyc' found under directory
> 'tests'
> warning: no previously-included files matching '*.pyc' found under directory
> 'docs'
> no previously-included directories found matching 'docs/_build'
> warning: no previously-included files found matching
Processed: streamlink: FTBFS: dh_install: error: missing files, aborting: pending
Processing commands for cont...@bugs.debian.org: > tags 1026714 + pending Bug #1026714 [src:streamlink] streamlink: FTBFS: dh_install: error: missing files, aborting Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026714 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026703: marked as done (pd-iemguts: FTBFS: make: *** [debian/rules:10: binary] Error 25)
Your message dated Tue, 20 Dec 2022 21:51:30 + with message-id and subject line Bug#1026703: fixed in pd-iemguts 0.3.1-3 has caused the Debian Bug report #1026703, regarding pd-iemguts: FTBFS: make: *** [debian/rules:10: binary] Error 25 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pd-iemguts Version: 0.3.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > rm -f -- /<>/debian/*//usr/lib/pd/extra/*/LICENSE.txt > make[1]: Leaving directory '/<>' >dh_installdocs >dh_installchangelogs >dh_perl >dh_usrlocal > dh_usrlocal: error: > debian/pd-iemguts/usr/local/lib/pd-externals/iemguts/LICENSE.txt is not a > directory > make: *** [debian/rules:10: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2022/12/20/pd-iemguts_0.3.1-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=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. --- End Message --- --- Begin Message --- Source: pd-iemguts Source-Version: 0.3.1-3 Done: IOhannes m zmölnig (Debian/GNU) We believe that the bug you reported is fixed in the latest version of pd-iemguts, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. IOhannes m zmölnig (Debian/GNU) (supplier of updated pd-iemguts package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 20 Dec 2022 22:10:29 +0100 Source: pd-iemguts Architecture: source Version: 0.3.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Closes: 1026703 Changes: pd-iemguts (0.3.1-3) unstable; urgency=medium . * Explicitly set buildsystem to 'pd_lib_builder' (Closes: #1026703) * Remove superfluous deletion of LICENSE.txt prior to symlinking it. * Update 'licensecheck' target + Ensure that 'licensecheck' is run with the C.UTF-8 locale + Exclude debian/ from 'licensecheck' + Re-generate d/copyright_hints * Bump standards version to 4.6.2 Checksums-Sha1: b26ff4bd1020b62fbc12fb9185fda39ddff713fc 2149 pd-iemguts_0.3.1-3.dsc 23d6b6a4f5762c861cf162f15979648a10f5f42d 3872 pd-iemguts_0.3.1-3.debian.tar.xz Checksums-Sha256: 0f69856bd46217f257b8e4ade38bf28336bdace2c63c2a260ffa6940b8cb9d91 2149 pd-iemguts_0.3.1-3.dsc ed41a777db87bbad681889008a0001a29fd7300eaf008f7fb3d3f53ff3ba573f 3872 pd-iemguts_0.3.1-3.debian.tar.xz Files: 08bc29dd866cba38470e372a17a1e919 2149 sound optional pd-iemguts_0.3.1-3.dsc 527840c7e5458f8aa518fc63b5c9738d 3872 sound optional pd-iemguts_0.3.1-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAmOiJRcWHGZvcnVtQHVt bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+KjiD/wJPjQ/k0uAGHJXUBZcDfqdjsJg 58ljUblnaa4O5m1tzcB3WUl1yoOiSuBPyhnPaRP2I2cgvcZuJL751B2iQNhL7f0z kcOo+ImCDnCQZimH2DuLrBIKUdDur+ngmLPcFJn802hDG/1sG1RRNtBinSmL8KAb lZC3G7NM+dtKrFXOlMcJRN/zTuRYXOzQDQ7bOCNBWED4htzXAxvMm8kfhhdTmtTl UEClR9NcRov/sfLLqdu52hhdecw4saiorhkhJkuoOAxJAMVETnwu7+8IafFGaAIl A4+gfxBCc+JPBlymSc8cs8mkiNzLh7xTlg3fhVV7LjCbNRUUBRIpMBZQ7K+y75D6 VzYQ4KE+ndg+94tGoqQzUpBeRLO7b4gpE2WZ
Bug#1026673: marked as done (libpf4j-java: FTBFS: make: *** [debian/rules:4: binary] Error 25)
Your message dated Tue, 20 Dec 2022 21:51:05 + with message-id and subject line Bug#1026673: fixed in libpf4j-java 3.8.0+dfsg-2 has caused the Debian Bug report #1026673, regarding libpf4j-java: FTBFS: make: *** [debian/rules:4: binary] Error 25 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libpf4j-java Version: 3.8.0+dfsg-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm 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 javahelper >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > mh_patchpoms -plibpf4j-java --debian-build --keep-pom-version > --maven-repo=/<>/libpf4j-java-3.8.0\+dfsg/debian/maven-repo >jh_linkjars >dh_auto_build > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<>/libpf4j-java-3.8.0\+dfsg > -Dclassworlds.conf=/etc/maven/m2-debian.conf > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml > -Ddebian.dir=/<>/libpf4j-java-3.8.0\+dfsg/debian > -Dmaven.repo.local=/<>/libpf4j-java-3.8.0\+dfsg/debian/maven-repo > --batch-mode package -DskipTests -Dnotimestamp=true -Dlocale=en_US > OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were > deprecated in JDK 13 and will likely be removed in a future release. > [0m[0m[INFO] Scanning for projects... > [INFO] > > [INFO] Reactor Build Order: > [INFO] > [INFO] PF4J Parent > [pom] > [INFO] PF4J > [jar] > [INFO] > [INFO] < org.pf4j:pf4j-parent > > > [INFO] Building PF4J Parent 3.8.0 > [1/2] > [INFO] [ pom > ]- > [INFO] > [INFO] --- maven-javadoc-plugin:3.0.1:jar (default) @ pf4j-parent --- > [INFO] Not executing Javadoc as the project is not a Java classpath-capable > package > [INFO] > [INFO] >>> maven-source-plugin:3.2.1:jar (default) > generate-sources @ > pf4j-parent >>> > [INFO] > [INFO] <<< maven-source-plugin:3.2.1:jar (default) < generate-sources @ > pf4j-parent <<< > [INFO] > [INFO] > [INFO] --- maven-source-plugin:3.2.1:jar (default) @ pf4j-parent --- > [INFO] > [INFO] ---< org.pf4j:pf4j > > > [INFO] Building PF4J 3.8.0 > [2/2] > [INFO] [ jar > ]- > [WARNING] The artifact org.hamcrest:hamcrest-all:jar:debian has been > relocated to org.hamcrest:hamcrest:jar:debian > [INFO] > [INFO] --- templating-maven-plugin:1.0.0:filter-sources (filter-src) @ pf4j > --- > [INFO] Coping files with filtering to temporary directory. > [INFO] Copying 1 resource > [INFO] Copied 1 files to output directory: > /<>/pf4j/target/generated-sources/java-templates > [INFO] Source directory: > /<>/pf4j/target/generated-sources/java-templates added. > [INFO] > [INFO] --- maven-resources-plugin:3.3.0:resources (default-resources) @ pf4j > --- > [INFO] Copying 1 resource > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ pf4j --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 79 source files to /<>/pf4j/target/classes > [INFO] > /<>/pf4j/src/main/java/org/pf4j/AbstractPluginManager.java: Some > input files use or override a deprecated API. > [INFO] > /<>/pf4j/src/main/java/org/pf4j/AbstractPluginManager.java: > Recompile with -Xlint:deprecation for details. > [INFO] > /<>/pf4j/src/main/java/org/pf4j/AbstractExtensionFinder.java: > /<>/pf4j/src/main/java/org/pf4j/A
Bug#1026644: marked as done (pd-iemlib: FTBFS: make: *** [debian/rules:11: binary] Error 25)
Your message dated Tue, 20 Dec 2022 21:51:40 + with message-id and subject line Bug#1026644: fixed in pd-iemlib 1.22.2-3 has caused the Debian Bug report #1026644, regarding pd-iemlib: FTBFS: make: *** [debian/rules:11: binary] Error 25 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pd-iemlib Version: 1.22.2-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > rm -f -- /<>/debian/*//usr/lib/pd/extra/*/LICENSE.txt > make[1]: Leaving directory '/<>' >dh_installdocs >dh_installchangelogs >dh_installexamples >dh_perl >dh_usrlocal > dh_usrlocal: error: > debian/pd-iemlib/usr/local/lib/pd-externals/iemlib/$n-help.pd is not a > directory > make: *** [debian/rules:11: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2022/12/20/pd-iemlib_1.22.2-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=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. --- End Message --- --- Begin Message --- Source: pd-iemlib Source-Version: 1.22.2-3 Done: IOhannes m zmölnig (Debian/GNU) We believe that the bug you reported is fixed in the latest version of pd-iemlib, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. IOhannes m zmölnig (Debian/GNU) (supplier of updated pd-iemlib package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 20 Dec 2022 22:09:03 +0100 Source: pd-iemlib Architecture: source Version: 1.22.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Closes: 1026644 Changes: pd-iemlib (1.22.2-3) unstable; urgency=medium . * Explicitly set buildsystem to 'pd_lib_builder' (Closes: #1026644) * Remove superfluous deletion of LICENSE.txt prior to symlinking it. * Update 'licensecheck' target + Ensure that 'licensecheck' is run with the C.UTF-8 locale + Exclude debian/ from 'licensecheck' + Re-generate d/copyright_hints * Bump standards version to 4.6.2 Checksums-Sha1: 29aaa62f2da81fcbec955db7e96387e8c4dfd5c9 2176 pd-iemlib_1.22.2-3.dsc 681f3e87af295eb237a0a179053b2fd0d9f5add5 6152 pd-iemlib_1.22.2-3.debian.tar.xz Checksums-Sha256: 3bbcf221bd4bee7452bf9d7cbc7964874ec4f59290aee7b31d01d8527776d796 2176 pd-iemlib_1.22.2-3.dsc 9e0050de4651d6cb7bd1911c6993d5f696333dc18ade880c06e9d066b838e723 6152 pd-iemlib_1.22.2-3.debian.tar.xz Files: 68734b8d8398d67ac00a036f910c49ec 2176 sound optional pd-iemlib_1.22.2-3.dsc 10d256380d99f7187de293706a326737 6152 sound optional pd-iemlib_1.22.2-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAmOiJOEWHGZvcnVtQHVt bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+GGPEACB/2295+Vr0jiU5irwd1rgEsfD AskrBL2V3yEX8h9MZc90222W15eKDiMLvfDcGB18p0tJH7Leb3fjNFWBgqOLgFQT +ss4Z1o29fSculVWjua8MxYDRWOM0zo33/hkNzLY+uBfiiiIO2hk8dv0m7cvbmzC yDWC2eIds5862KmMdoSCka7OT/I8M9wxmgbdvhIBzYuKxqD1+KJWnLzM2eVbyRbJ 4+TMu/6zBwvE8xhHgyRPOIp9PPGP/ptUyVUTjGzpjcK1FVxFWJ9PmgwkM61TAXAD 3i0kMEn+OI5cDgSupkNdpkAvsZrglnXD2OXoKSu0i+8aD/KuUYU9QMVfhhneWtpd 1srJrVzLuo
Bug#1026724: marked as done (git-secrets: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2)
Your message dated Tue, 20 Dec 2022 21:50:05 + with message-id and subject line Bug#1026724: fixed in git-secrets 1.3.0-5 has caused the Debian Bug report #1026724, regarding git-secrets: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026724 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: git-secrets Version: 1.3.0-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > LANG=C test/bats/bin/bats test/ > 1..50 > ok 1 Rejects commit messages with prohibited patterns > ok 2 Allows commit messages that do not match a prohibited pattern > ok 3 no arguments prints usage instructions > ok 4 -h prints help > ok 5 Invalid scan filename fails > ok 6 Does not require secrets > ok 7 No prohibited matches exits 0 > ok 8 Scans all files when no file provided > ok 9 Scans all files including history > ok 10 Scans all files when no file provided with secret in history > ok 11 Scans all files including history with secret in history > ok 12 Scans history with secrets distributed among branches in history > ok 13 Scans recursively > ok 14 Scans recursively only if -r is given > ok 15 Excludes allowed patterns from failures > ok 16 Prohibited matches exits 1 > ok 17 Only matches on word boundaries > ok 18 Can scan from stdin using - > ok 19 installs hooks for repo > ok 20 fails if hook exists and no -f > not ok 21 Overwrites hooks if -f is given > # (in test file test/git-secrets.bats, line 147) > # `[ $status -eq 0 ]' failed > # hint: Using 'master' as the name for the initial branch. This default > branch name > # hint: is subject to change. To configure the initial branch name to use in > all > # hint: of your new repositories, which will suppress this warning, call: > # hint: > # hint: git config --global init.defaultBranch > # hint: > # hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and > # hint: 'development'. The just-created branch can be renamed via this > command: > # hint: > # hint: git branch -m > # Initialized empty Git repository in > /<>/debian/testtmp/test-repo/.git/ > # /<> > # /<>/debian/testtmp/test-repo > # /<>/debian/testtmp/test-repo > ok 22 installs hooks for repo with Debian style directories > not ok 23 installs hooks to template directory > # (in test file test/git-secrets.bats, line 164) > # `[ $status -eq 0 ]' failed > # hint: Using 'master' as the name for the initial branch. This default > branch name > # hint: is subject to change. To configure the initial branch name to use in > all > # hint: of your new repositories, which will suppress this warning, call: > # hint: > # hint: git config --global init.defaultBranch > # hint: > # hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and > # hint: 'development'. The just-created branch can be renamed via this > command: > # hint: > # hint: git branch -m > # Initialized empty Git repository in > /<>/debian/testtmp/test-repo/.git/ > # /<> > # /<>/debian/testtmp/test-repo > ok 24 Scans using keys from credentials file > ok 25 Lists secrets for a repo > ok 26 Adds secrets to a repo and de-dedupes > ok 27 Adds allowed patterns to a repo and de-dedupes > ok 28 Empty lines must be ignored in .gitallowed files > ok 29 Comment lines must be ignored in .gitallowed files > ok 30 Scans all files and allowing none of the bad patterns in .gitallowed > ok 31 Scans all files and allowing all bad patterns in .gitallowed > ok 32 Adds common AWS patterns > ok 33 Adds providers > ok 34 Strips providers that return nothing > ok 35 --recursive cannot be used with SCAN_* > ok 36 --recursive can be used with --scan > ok 37 --recursive can't be used with --list > ok 38 -f can only be used with --install > ok 39 -a can only be used with --add > ok 40 -l can only be used with --add > ok 41 --cached can only be used with --scan > ok 42 --no-index can only be used with --scan > ok 43 --untracked can only be used with -
Bug#1026772: marked as done (libsane: The size of the libsane_1.0.31-4.1_amd64.deb package is only about 46 kB whereas the libsane_1.0.27-3.2_amd64.deb package has a size of 2,1 MB.)
Your message dated Tue, 20 Dec 2022 22:49:00 +0100 with message-id and subject line Re: Bug#1026772: libsane: The size of the libsane_1.0.31-4.1_amd64.deb package is only about 46 kB whereas the libsane_1.0.27-3.2_amd64.deb package has a size of 2,1 MB. has caused the Debian Bug report #1026772, regarding libsane: The size of the libsane_1.0.31-4.1_amd64.deb package is only about 46 kB whereas the libsane_1.0.27-3.2_amd64.deb package has a size of 2,1 MB. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026772 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libsane Version: 1.0.31-4.1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: 15151...@mail.ru Dear Maintainer, The size of the libsane_1.0.31-4.1_amd64.deb package is only about 46 kB whereas the libsane_1.0.27-3.2_amd64.deb package has a size of 2,1 MB. It looks like some files were lost during packaging. It looks like the /lib/udev and /usr/lib branches were completely lost. Only the /usr/share/doc/libsane branch remains. -- System Information: Debian Release: 11.5 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-18-amd64 (SMP w/12 CPU threads) --- End Message --- --- Begin Message --- Hi Aleksey On 2022-12-20 23:59:24 +0300, Aleksey wrote: > Package: libsane > Version: 1.0.31-4.1 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: 15151...@mail.ru > > Dear Maintainer, > > The size of the libsane_1.0.31-4.1_amd64.deb package is only about 46 kB > whereas the libsane_1.0.27-3.2_amd64.deb package has a size of 2,1 MB. It > looks like some files were lost during packaging. > It looks like the /lib/udev and /usr/lib branches were completely lost. Only > the /usr/share/doc/libsane branch remains. libsane is a transitional package in bullseye, so that's expected. Take a look at libsane1. Cheers -- Sebastian Ramacher--- End Message ---
Bug#1026503: Processed: retitle 1026503 to ibembperl-perl: FTBFS: Expected 6 more error(s) in logfile, tagging 1026503
On Tue, 20 Dec 2022 22:44:57 +0100, Axel Beckert wrote: > Debian Bug Tracking System wrote: > > > tags 1026503 + confirmed > > Bug #1026503 [src:libembperl-perl] ibembperl-perl: FTBFS: Expected 6 more > > error(s) in logfile (Thanks for fixing this copypaste mistake!) > Can confirm as well. Are you already working on it? I've put it on my > TODO list at least, too. :-) No, I had a brief look and didn't find a handle to even start; and secretly I hoped that you would see the bug report as well :) Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1026503: Processed: retitle 1026503 to ibembperl-perl: FTBFS: Expected 6 more error(s) in logfile, tagging 1026503
Hi gregor, Debian Bug Tracking System wrote: > > tags 1026503 + confirmed > Bug #1026503 [src:libembperl-perl] ibembperl-perl: FTBFS: Expected 6 more > error(s) in logfile Can confirm as well. Are you already working on it? I've put it on my TODO list at least, too. :-) Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Processed: retitle 1026503 to libembperl-perl: FTBFS: Expected 6 more error(s) in logfile
Processing commands for cont...@bugs.debian.org: > # fix typo in package name > retitle 1026503 libembperl-perl: FTBFS: Expected 6 more error(s) in logfile Bug #1026503 [src:libembperl-perl] ibembperl-perl: FTBFS: Expected 6 more error(s) in logfile Changed Bug title to 'libembperl-perl: FTBFS: Expected 6 more error(s) in logfile' from 'ibembperl-perl: FTBFS: Expected 6 more error(s) in logfile'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026503 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026626: marked as done (qttranslations-opensource-src: FTBFS: build-dependency not installable: qttools5-dev-tools (>= 5.15.7~))
Your message dated Wed, 21 Dec 2022 00:29:27 +0300 with message-id and subject line Re: Bug#1026553: qttranslations-opensource-src: FTBFS: build-dependency not installable: qttools5-dev-tools (>= 5.15.7~) has caused the Debian Bug report #1026553, regarding qttranslations-opensource-src: FTBFS: build-dependency not installable: qttools5-dev-tools (>= 5.15.7~) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026553 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qttranslations-opensource-src Version: 5.15.7-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm 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), qt5-qmake (>= 5.15.7+dfsg~), > qttools5-dev-tools (>= 5.15.7~), build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), qt5-qmake (>= 5.15.7+dfsg~), > qttools5-dev-tools (>= 5.15.7~), 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 [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [404 B] > Get:5 copy:/<>/apt_archive ./ Packages [487 B] > Fetched 1848 B in 0s (104 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > 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: qttools5-dev-tools (>= 5.15.7~) > but it is not going to be installed > 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/2022/12/20/qttranslations-opensource-src_5.15.7-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=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. --- End Message --- --- Begin Message --- Hi Lucas! On Tue, Dec 20, 2022 at 06:10:27PM +0100, Lucas Nussbaum wrote: > Source: qttranslations-opensource-src > Version: 5.15.7-2 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20221220 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > The following packages have unmet dependencies: > > sbuild-build-depends-main-dummy : Depends: qttools5-dev-tools > > (>= 5.15.7~) but it is not going to be installed We are in process of Qt 5.15.7 transition, see #1025863. And today it built fine on a buildd: https://buildd.debian.org/status/fetch.php?pkg=qttranslations-opensource-src=all=5.15.7-2=1671546195=0 -- Dmitry Shachnev signature.asc Description: PGP signature --- End Message ---
Bug#1026553: marked as done (qttranslations-opensource-src: FTBFS: build-dependency not installable: qttools5-dev-tools (>= 5.15.7~))
Your message dated Wed, 21 Dec 2022 00:29:27 +0300 with message-id and subject line Re: Bug#1026553: qttranslations-opensource-src: FTBFS: build-dependency not installable: qttools5-dev-tools (>= 5.15.7~) has caused the Debian Bug report #1026553, regarding qttranslations-opensource-src: FTBFS: build-dependency not installable: qttools5-dev-tools (>= 5.15.7~) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026553 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qttranslations-opensource-src Version: 5.15.7-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm 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), qt5-qmake (>= 5.15.7+dfsg~), > qttools5-dev-tools (>= 5.15.7~), build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), qt5-qmake (>= 5.15.7+dfsg~), > qttools5-dev-tools (>= 5.15.7~), 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 [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [404 B] > Get:5 copy:/<>/apt_archive ./ Packages [487 B] > Fetched 1848 B in 0s (104 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > 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: qttools5-dev-tools (>= 5.15.7~) > but it is not going to be installed > 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/2022/12/20/qttranslations-opensource-src_5.15.7-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=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. --- End Message --- --- Begin Message --- Hi Lucas! On Tue, Dec 20, 2022 at 06:10:27PM +0100, Lucas Nussbaum wrote: > Source: qttranslations-opensource-src > Version: 5.15.7-2 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20221220 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > The following packages have unmet dependencies: > > sbuild-build-depends-main-dummy : Depends: qttools5-dev-tools > > (>= 5.15.7~) but it is not going to be installed We are in process of Qt 5.15.7 transition, see #1025863. And today it built fine on a buildd: https://buildd.debian.org/status/fetch.php?pkg=qttranslations-opensource-src=all=5.15.7-2=1671546195=0 -- Dmitry Shachnev signature.asc Description: PGP signature --- End Message ---
Bug#1026580: marked as done (svim: FTBFS: ModuleNotFoundError: No module named 'pysam.libchtslib')
Your message dated Tue, 20 Dec 2022 21:27:12 +
with message-id
and subject line Bug#1026580: fixed in svim 2.0.0-3
has caused the Debian Bug report #1026580,
regarding svim: FTBFS: ModuleNotFoundError: No module named 'pysam.libchtslib'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1026580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: svim
Version: 2.0.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --system=custom --test-args="PYTHONPATH={build_dir}
> {interpreter} -m unittest discover -v src/tests"
> I: pybuild base:240: PYTHONPATH=/<>/.pybuild/cpython3_3.11/build
> python3.11 -m unittest discover -v src/tests
> test_Collect (unittest.loader._FailedTest.test_Collect) ... ERROR
> test_downstream_distance_to
> (test_SVCandidate.DeletionCandidateTestCase.test_downstream_distance_to) ...
> ok
> test_get_key (test_SVCandidate.DeletionCandidateTestCase.test_get_key) ... ok
> test_get_source (test_SVCandidate.DeletionCandidateTestCase.test_get_source)
> ... ok
> test_get_std_pos
> (test_SVCandidate.DeletionCandidateTestCase.test_get_std_pos) ... ok
> test_get_std_span
> (test_SVCandidate.DeletionCandidateTestCase.test_get_std_span) ... ok
> test_get_vcf_entry
> (test_SVCandidate.DeletionCandidateTestCase.test_get_vcf_entry) ... ok
> test_accessors (test_Signature.TestSVSignature.test_accessors) ... ok
> test_as_string (test_Signature.TestSVSignature.test_as_string) ... ok
> test_downstream_distance_to
> (test_Signature.TestSVSignature.test_downstream_distance_to) ... ok
> test_clustering (unittest.loader._FailedTest.test_clustering) ... ERROR
> test_consensus (unittest.loader._FailedTest.test_consensus) ... ERROR
> test_guess_file_type
> (test_input_parsing.TestInputParsing.test_guess_file_type) ... ok
> test_inter (unittest.loader._FailedTest.test_inter) ... ERROR
> test_analyze_cigar_indel (test_intra.TestSVIMIntra.test_analyze_cigar_indel)
> ... ok
> test_satag (unittest.loader._FailedTest.test_satag) ... ERROR
>
> ==
> ERROR: test_Collect (unittest.loader._FailedTest.test_Collect)
> --
> ImportError: Failed to import test module: test_Collect
> Traceback (most recent call last):
> File "/usr/lib/python3.11/unittest/loader.py", line 407, in _find_test_path
> module = self._get_module_from_name(name)
>
> File "/usr/lib/python3.11/unittest/loader.py", line 350, in
> _get_module_from_name
> __import__(name)
> File "/<>/src/tests/test_Collect.py", line 2, in
> import pysam
> File "/usr/lib/python3/dist-packages/pysam/__init__.py", line 4, in
> from pysam.libchtslib import *
> ModuleNotFoundError: No module named 'pysam.libchtslib'
>
>
> ==
> ERROR: test_clustering (unittest.loader._FailedTest.test_clustering)
> --
> ImportError: Failed to import test module: test_clustering
> Traceback (most recent call last):
> File "/usr/lib/python3.11/unittest/loader.py", line 407, in _find_test_path
> module = self._get_module_from_name(name)
>
> File "/usr/lib/python3.11/unittest/loader.py", line 350, in
> _get_module_from_name
> __import__(name)
> File "/<>/src/tests/test_clustering.py", line 6, in
> from svim.SVIM_clustering import form_partitions, partition_and_cluster
> File
> "/<>/.pybuild/cpython3_3.11/build/svim/SVIM_clustering.py", line
> 11, in
> from pysam import FastaFile
> File "/usr/lib/python3/dist-packages/pysam/__init__.py", line 4, in
> from pysam.libchtslib import *
> ModuleNotFoundError: No module named 'pysam.libchtslib'
>
>
>
Bug#1026684: marked as done (pd-purest-json: FTBFS: make[1]: *** No rule to make target 'pd-lib-builder/Makefile.pdlibbuilder'. Stop.)
Your message dated Tue, 20 Dec 2022 21:25:41 + with message-id and subject line Bug#1026684: fixed in pd-purest-json 2.0.1-2 has caused the Debian Bug report #1026684, regarding pd-purest-json: FTBFS: make[1]: *** No rule to make target 'pd-lib-builder/Makefile.pdlibbuilder'. Stop. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026684 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pd-purest-json Version: 2.0.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules clean > dh clean >dh_auto_clean > make -j8 distclean > make[1]: Entering directory '/<>' > Makefile:53: pd-lib-builder/Makefile.pdlibbuilder: No such file or directory > make[1]: *** No rule to make target 'pd-lib-builder/Makefile.pdlibbuilder'. > Stop. > make[1]: Leaving directory '/<>' > dh_auto_clean: error: make -j8 distclean returned exit code 2 > make: *** [debian/rules:11: clean] Error 25 The full build log is available from: http://qa-logs.debian.net/2022/12/20/pd-purest-json_2.0.1-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=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. --- End Message --- --- Begin Message --- Source: pd-purest-json Source-Version: 2.0.1-2 Done: IOhannes m zmölnig (Debian/GNU) We believe that the bug you reported is fixed in the latest version of pd-purest-json, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. IOhannes m zmölnig (Debian/GNU) (supplier of updated pd-purest-json package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 20 Dec 2022 22:05:19 +0100 Source: pd-purest-json Architecture: source Version: 2.0.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Closes: 1026684 Changes: pd-purest-json (2.0.1-2) unstable; urgency=medium . * Explicitly set buildsystem to 'pd_lib_builder' (Closes: #1026684) * Remove superfluous deletion of LICENSE.txt prior to symlinking it. * Ensure that 'licensecheck' is run with the C.UTF-8 locale * Bump standards version to 4.6.2 Checksums-Sha1: 59ae66dee6bf0415dc9c36dd9fa600a946d3dad3 2299 pd-purest-json_2.0.1-2.dsc f4c9131c00f843bd474ceb36c1c9223bfa2c544d 5108 pd-purest-json_2.0.1-2.debian.tar.xz Checksums-Sha256: e9d06ba8edc95e956da12d8ca35d23bd317c548fce89481cbdc0a4f452036719 2299 pd-purest-json_2.0.1-2.dsc 36c6f4f8077a9dae22b62bf5b1dea12fd8f2b5fa818901e40b37300c8ae9fdf0 5108 pd-purest-json_2.0.1-2.debian.tar.xz Files: 0bc308ecd20b2f59f30ede6e5109445c 2299 sound optional pd-purest-json_2.0.1-2.dsc 16e34c3eb442b59860053b6d59c22f82 5108 sound optional pd-purest-json_2.0.1-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAmOiI8sWHGZvcnVtQHVt bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+LYkD/9Uri8ucc9DKtMl7EUfxiB1WWVW mvGM8UY3qMh2CjgLd7TPO5YxMtXcbteqRwbH+ko9z+RRJknqrBWRo6nB5JL40WZ3 HRrdP/ccfXWbrxGKDaVZ6OuUhP6eKfV3Ef+Xh80pFLhUUJOK+pvKExV7ytemLNQe UYu1T67L66EMQCxnbAavwc25GuDIuHVzpZtPpalB/vESrSov0jfTFFHgbVs9ZYJc MMXfZlR+pbCO6Yh0vt0C7VJ8QZ1Wf0RQVS7x3EQOlFtL2REL/vBStRtLPaUbAwiv iIYYY8Ti0mslMAbUkOFCa7msIpjl2M7nBsQ8/1cFVANoVX4gZxhg1y
Bug#1026651: marked as done (pd-comport: FTBFS: make: *** [debian/rules:10: binary] Error 25)
Your message dated Tue, 20 Dec 2022 21:25:23 + with message-id and subject line Bug#1026651: fixed in pd-comport 1.2-2 has caused the Debian Bug report #1026651, regarding pd-comport: FTBFS: make: *** [debian/rules:10: binary] Error 25 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pd-comport Version: 1.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > rm -f -- /<>/debian/*//usr/lib/pd/extra/*/LICENSE.txt > make[1]: Leaving directory '/<>' >dh_installdocs >dh_installchangelogs >dh_perl >dh_usrlocal > dh_usrlocal: error: > debian/pd-comport/usr/local/lib/pd-externals/comport/CHANGES.txt is not a > directory > make: *** [debian/rules:10: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2022/12/20/pd-comport_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-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=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. --- End Message --- --- Begin Message --- Source: pd-comport Source-Version: 1.2-2 Done: IOhannes m zmölnig (Debian/GNU) We believe that the bug you reported is fixed in the latest version of pd-comport, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. IOhannes m zmölnig (Debian/GNU) (supplier of updated pd-comport package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 20 Dec 2022 22:06:06 +0100 Source: pd-comport Architecture: source Version: 1.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Closes: 1026651 Changes: pd-comport (1.2-2) unstable; urgency=medium . * Explicitly set buildsystem to 'pd_lib_builder' (Closes: #1026651) * Remove superfluous deletion of LICENSE.txt prior to symlinking it. * Update 'licensecheck' target + Ensure that 'licensecheck' is run with the C.UTF-8 locale + Exclude debian/ from 'licensecheck' + Re-generate d/copyright_hints * Bump standards version to 4.6.2 Checksums-Sha1: 06d5536d439507865d90ee5af77c1aacf4fa16e8 2116 pd-comport_1.2-2.dsc 2c3334ac309eea3b9dda94520e634a706b11daf4 3588 pd-comport_1.2-2.debian.tar.xz Checksums-Sha256: 50dd47d8ee33d27a2227b40965bb5cb722b14143dc20b83d332d455e1c67276e 2116 pd-comport_1.2-2.dsc fee338676bf8c2a61827fea8baf2495572d9e2e37b49353be77c6d9180b4948d 3588 pd-comport_1.2-2.debian.tar.xz Files: 5a6699286f4f3d6f6f6c08f84de10e73 2116 sound optional pd-comport_1.2-2.dsc 7c9d072791af1c6a000d63fdbb7b0ec5 3588 sound optional pd-comport_1.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAmOiJCcWHGZvcnVtQHVt bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+PNLD/4yG/1lGpFg1FVbJVFcGIShTaon QMg3rNU6BqlRrc8F8bPRdksk6R+uFtiu59F1apqtvWOmbTAt5ZBn+qA+henBw7EI biBOiSkavnHym7ZMDefh04pbwJcDHBiTJlcqnHBHy7mcpOTuwtiqWQQJbxqR6Wuw IVZqdky5s6ITM1fKAxt6+8TWhbyT8y0ee6FYBI7HFH3IdkG+cH8kItwnVA7D9gcG 91+KN9BBCi4hlX1HJo2g0JqyV52sipuFoyQ3pxYGTw3yslwa9r+geioR7aSPKPVq i9mkQ10VCza7GwpNZ37vTf+tCpTlJUkR0HZzhCBlkBRELxgofYMK6jsqUgLFboSD aaTh77tciCTBCwurVy+GLRZR/SoI9pbJ/jbCvXYljz483BD7wqhk99
Bug#1026677: marked as done (pd-hcs: FTBFS: make: *** [debian/rules:9: binary] Error 25)
Your message dated Tue, 20 Dec 2022 21:25:33 + with message-id and subject line Bug#1026677: fixed in pd-hcs 0.2.1-2 has caused the Debian Bug report #1026677, regarding pd-hcs: FTBFS: make: *** [debian/rules:9: binary] Error 25 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026677 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pd-hcs Version: 0.2.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > rm -f -- /<>/debian/*//usr/lib/pd/extra/*/LICENSE.txt > make[1]: Leaving directory '/<>' >dh_installdocs >dh_installchangelogs >dh_lintian >dh_perl >dh_usrlocal > dh_usrlocal: error: > debian/pd-hcs/usr/local/lib/pd-externals/hcs/ISOdate-help.pd is not a > directory > make: *** [debian/rules:9: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2022/12/20/pd-hcs_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-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=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. --- End Message --- --- Begin Message --- Source: pd-hcs Source-Version: 0.2.1-2 Done: IOhannes m zmölnig (Debian/GNU) We believe that the bug you reported is fixed in the latest version of pd-hcs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. IOhannes m zmölnig (Debian/GNU) (supplier of updated pd-hcs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 20 Dec 2022 22:08:28 +0100 Source: pd-hcs Architecture: source Version: 0.2.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Closes: 1026677 Changes: pd-hcs (0.2.1-2) unstable; urgency=medium . * Explicitly set buildsystem to 'pd_lib_builder' (Closes: #1026677) * Remove superfluous deletion of LICENSE.txt prior to symlinking it. * Bump standards version to 4.6.2 Checksums-Sha1: 059583387775aaca24c952e7df2463e563676e18 2084 pd-hcs_0.2.1-2.dsc 5209e2b982e4aff8a269b48d0b2e0fe1ba4f05cb 5096 pd-hcs_0.2.1-2.debian.tar.xz Checksums-Sha256: b0c4e778d08cc96ffdcde64d1b1d2554742b74ddf1c2a2a8667aafcdc83562b1 2084 pd-hcs_0.2.1-2.dsc 93441f98b2247dcaab7c6dc969a579270d4bb44d83c53c71948bb5a1814e908e 5096 pd-hcs_0.2.1-2.debian.tar.xz Files: 53085574673ffa86556024d4930537e2 2084 sound optional pd-hcs_0.2.1-2.dsc 14ef709d990d3aa70079d2c8d47cb004 5096 sound optional pd-hcs_0.2.1-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAmOiJIYWHGZvcnVtQHVt bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+DDhD/9CMcsti/RnPoKrWW/RQJZi9JI6 J3Ewy44YATm1fdnsFvUWhegRTee1BD29bek5Bu69kMEJW9veJFLCyZmB9X1anA+f Sq1mDQsOPzRsLB1Hp3d9jNakJf9zuywmbCXTnhOzvrnmv+rrXd9/WksJpPn4XB2f LDmtI9I+Fvtk3c/yXPhaaMrHQ7FEVqgRbFZoMx7i3KhRtDqfnxDVbxpibACBsFjj g2ZCqjKr3z0IPu4SIuKSt9ztGsB6ugWiPOM25rAqeEhWf52SWjKtC/spreTB7nKA G/mScK8aq8YAgMLwEyxvqSTYQd6DeAYYp/RMx1l1ERTaX7Umht4LtUEpw0pWWSwE 1/BH8Iq8hotZVj4vOol3r88Ipar9TKzalpLTqtg9hzfD77zNPA8ESZnxy2BrcUeG WRb4Oj/lh/ijBMa64XQmvoJVR+GtKx2DoJjgnHXvLO4/pbDDgXYHe0J68/OTtU6I B7O+WrekrhtfsTJhkSJCIXckUr7n2VOabqTK2Iwqfs8t+RB3ueFF6TKsXTBpJ4WV T24o+JYs6fYI9VDOivIid7odj6Ro3fnu/UK+dqAQTFRo9Xx
Bug#1026616: marked as done (mkdocstrings-python-legacy: FTBFS: make: *** [debian/rules:15: binary] Error 25)
Your message dated Tue, 20 Dec 2022 21:25:52 +
with message-id
and subject line Bug#1026616: fixed in python-promise 2.3.0-3
has caused the Debian Bug report #1026616,
regarding mkdocstrings-python-legacy: FTBFS: make: *** [debian/rules:15:
binary] Error 25
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1026616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mkdocstrings-python-legacy
Version: 0.2.3-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
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
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:107: Building wheel for python3.11 with "build"
> module
> I: pybuild base:240: python3.11 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.11_mkdocstrings
> * Building wheel...
> Traceback (most recent call last):
> File "/usr/lib/python3/dist-packages/pep517/in_process/_in_process.py",
> line 351, in
> main()
> File "/usr/lib/python3/dist-packages/pep517/in_process/_in_process.py",
> line 333, in main
> json_out['return_val'] = hook(**hook_input['kwargs'])
>
> File "/usr/lib/python3/dist-packages/pep517/in_process/_in_process.py",
> line 249, in build_wheel
> return _build_backend().build_wheel(wheel_directory, config_settings,
>^^
> File "/usr/lib/python3/dist-packages/pdm/pep517/api.py", line 75, in
> build_wheel
> builder.build(wheel_directory, metadata_directory=metadata_directory)
> File "/usr/lib/python3/dist-packages/pdm/pep517/wheel.py", line 151, in
> build
> self._copy_module()
> File "/usr/lib/python3/dist-packages/pdm/pep517/wheel.py", line 321, in
> _copy_module
> root = self.meta.config.package_dir or self.location
>^
> File "/usr/lib/python3/dist-packages/pdm/pep517/base.py", line 154, in meta
> self._meta.validate(True)
> File "/usr/lib/python3/dist-packages/pdm/pep517/metadata.py", line 58, in
> validate
> return validate_pep621(self.data, raising)
>^^^
> File "/usr/lib/python3/dist-packages/pdm/pep517/validator.py", line 85, in
> validate_pep621
> raise PEP621ValidationError(validator.errors)
> pdm.pep517.exceptions.PEP621ValidationError: {'license-expression': ['unknown
> field']}
>
> ERROR Backend subproccess exited when trying to invoke build_wheel
> E: pybuild pybuild:386: build: plugin pyproject failed with: exit code=1:
> python3.11 -m build --skip-dependency-check --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.11_mkdocstrings
> I: pybuild plugin_pyproject:107: Building wheel for python3.10 with "build"
> module
> I: pybuild base:240: python3.10 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.10_mkdocstrings
> * Building wheel...
> Traceback (most recent call last):
> File "/usr/lib/python3/dist-packages/pep517/in_process/_in_process.py",
> line 351, in
> main()
> File "/usr/lib/python3/dist-packages/pep517/in_process/_in_process.py",
> line 333, in main
> json_out['return_val'] = hook(**hook_input['kwargs'])
> File "/usr/lib/python3/dist-packages/pep517/in_process/_in_process.py",
> line 249, in build_wheel
> return _build_backend().build_wheel(wheel_directory, config_settings,
> File "/usr/lib/python3/dist-packages/pdm/pep517/api.py", line 75, in
> build_wheel
> builder.build(wheel_directory, metadata_directory=metadata_directory)
> File "/usr/lib/python3/dist-packages/pdm/pep517/wheel.py", line 151, in
> build
> self._copy_module()
> File "/usr/lib/python3/dist-packages
Processed: Re: Bug#1026445: mutter: test failure on armhf and sometimes armel: ../../src/xcb_io.c:626: _XAllocID: Assertion `ret != inval_id' failed
Processing control commands: > severity -1 important Bug #1026445 [src:mutter] mutter: test failure on armhf and sometimes armel: ../../src/xcb_io.c:626: _XAllocID: Assertion `ret != inval_id' failed Severity set to 'important' from 'serious' -- 1026445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026445 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026445: mutter: test failure on armhf and sometimes armel: ../../src/xcb_io.c:626: _XAllocID: Assertion `ret != inval_id' failed
Control: severity -1 important On Tue, 20 Dec 2022 at 11:47:10 +, Simon McVittie wrote: > Recent uploads of mutter have had a FTBFS on armhf and sometimes armel, > with this test failure in "mutter:core+mutter/wayland / xwayland" In 43.2-4 I've downgraded failures in this test to be non-fatal, reducing the severity of this issue. > The same test failure has not been seen on arm64 or on non-ARM > architectures, for whatever reason (in particular, other slower > architectures like riscv64 and mips*el don't seem to have this > problem). This is probably because d/rules in mutter explicitly skips the tests on riscv64 and mips*el. I'd prefer to re-enable the tests on all architectures (even if all failures are ignored on some of them) now that it's using Meson, in which all tests have a finite timeout, but that will probably need to happen via experimental in order to avoid disrupting migration. One important and possibly relevant difference between 32-bit ARM and arm64 is that on 32-bit ARM, we explicitly set the default driver in mutter's fork of cogl to be OpenGL|ES 2 instead of OpenGL 3, using non-upstreamed patches. I'd like to be able to stop applying those patches, but that will need input from users of proprietary GPU drivers on ARM. smcv
Bug#1026534: marked as done (criu: FTBFS: unistd.h:1091:17: error: conflicting types for ‘syscall’; have ‘long int(long int, ...)’)
Your message dated Tue, 20 Dec 2022 21:21:27 + with message-id and subject line Bug#1026534: fixed in criu 3.17.1-2 has caused the Debian Bug report #1026534, regarding criu: FTBFS: unistd.h:1091:17: error: conflicting types for ‘syscall’; have ‘long int(long int, ...)’ to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: criu Version: 3.17.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > Note: Building criu without amdgpu_plugin. > Note: libdrm and libdrm_amdgpu are required to build amdgpu_plugin. > make[1]: git: No such file or directory > GEN .gitid > GEN include/common/asm > GEN compel/include/asm > touch .config > GEN compel/include/version.h > GEN criu/include/version.h > GEN include/common/config.h > GEN compel/plugins/include/uapi/std/syscall-codes-64.h > GEN compel/plugins/include/uapi/std/syscall-64.h > DEP compel/arch/x86/plugins/std/memcpy.d > DEP compel/arch/x86/plugins/std/parasite-head.d > GEN compel/plugins/include/uapi/std/syscall-codes.h > GEN compel/plugins/include/uapi/std/asm/syscall-types.h > DEP soccr/soccr.d > GEN compel/plugins/include/uapi/std/syscall.h > GEN compel/arch/x86/plugins/std/syscalls-64.S > DEP compel/arch/x86/plugins/std/syscalls-64.d > GEN compel/arch/x86/plugins/std/sys-exec-tbl-64.c > DEP compel/plugins/std/infect.d > DEP compel/plugins/std/string.d > DEP compel/plugins/std/log.d > DEP compel/plugins/std/fds.d > DEP compel/plugins/std/std.d > DEP compel/plugins/shmem/shmem.d > CC soccr/soccr.o > DEP compel/plugins/fds/fds.d > CC compel/plugins/std/std.o > CC compel/plugins/std/fds.o > CC compel/plugins/std/log.o > CC compel/plugins/std/string.o > CC compel/plugins/std/infect.o > CC compel/arch/x86/plugins/std/parasite-head.o > CC compel/arch/x86/plugins/std/memcpy.o > CC compel/arch/x86/plugins/std/syscalls-64.o > PBCC images/rseq.pb-c.c > PBCC images/apparmor.pb-c.c > PBCC images/bpfmap-data.pb-c.c > PBCC images/fown.pb-c.c > PBCC images/google/protobuf/descriptor.pb-c.c > PBCC images/img-streamer.pb-c.c > PBCC images/timens.pb-c.c > PBCC images/macvlan.pb-c.c > PBCC images/autofs.pb-c.c > PBCC images/sysctl.pb-c.c > PBCC images/time.pb-c.c > PBCC images/binfmt-misc.pb-c.c > PBCC images/seccomp.pb-c.c > PBCC images/pidns.pb-c.c > PBCC images/userns.pb-c.c > PBCC images/cgroup.pb-c.c > PBCC images/ext-file.pb-c.c > PBCC images/siginfo.pb-c.c > PBCC images/rpc.pb-c.c > PBCC images/rlimit.pb-c.c > PBCC images/file-lock.pb-c.c > PBCC images/creds.pb-c.c > PBCC images/utsns.pb-c.c > PBCC images/ipc-desc.pb-c.c > PBCC images/ipc-var.pb-c.c > PBCC images/sk-opts.pb-c.c > PBCC images/timer.pb-c.c > PBCC images/pipe-data.pb-c.c > PBCC images/sk-packet.pb-c.c > PBCC images/pstree.pb-c.c > PBCC images/fs.pb-c.c > PBCC images/eventpoll.pb-c.c > PBCC images/eventfd.pb-c.c > PBCC images/remap-file-path.pb-c.c > PBCC images/fifo.pb-c.c > PBCC images/ns.pb-c.c > PBCC images/cpuinfo.pb-c.c > PBCC images/stats.pb-c.c > DEP images/rseq.pb-c.d > DEP images/apparmor.pb-c.d > PBCC images/opts.pb-c.c > DEP images/bpfmap-data.pb-c.d > DEP images/fown.pb-c.d > DEP images/google/protobuf/descriptor.pb-c.d > DEP images/img-streamer.pb-c.d > DEP images/timens.pb-c.d > PBCC images/memfd.pb-c.c > PBCC images/sit.pb-c.c > DEP images/macvlan.pb-c.d > DEP images/autofs.pb-c.d > DEP images/sysctl.pb-c.d > DEP images/time.pb-c.d > DEP images/binfmt-misc.pb-c.d > DEP images/seccomp.
Processed: Merging 1026553 1026626
Processing commands for cont...@bugs.debian.org: > merge 1026553 1026626 Bug #1026553 [src:qttranslations-opensource-src] qttranslations-opensource-src: FTBFS: build-dependency not installable: qttools5-dev-tools (>= 5.15.7~) Bug #1026626 [src:qttranslations-opensource-src] qttranslations-opensource-src: FTBFS: build-dependency not installable: qttools5-dev-tools (>= 5.15.7~) Merged 1026553 1026626 > thanks Stopping processing here. Please contact me if you need assistance. -- 1026553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026553 1026626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026626 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026773: libcap2: autopkgtest failures block other packages from migrating
Source: libcap2 Version: 1:2.66-2 Severity: serious Jutsification: stops other packages from migrating to testing Hi, The autopkgtest run for the latest version of libcap2 in unstable fails on all architectures: autopkgtest [18:14:20]: test upstream-nonroot: - - - - - - - - - - results - - - - - - - - - - upstream-nonroot FAIL stderr: dpkg-architecture: warning: cannot determine CC system type, falling back to default (native compilation) https://ci.debian.net/packages/libc/libcap2/testing/amd64/ This stops unrelated packages from migrating to testing. Please consider either fixing the tests or removing them to unblock other packages. Thanks! Kind regards, Luca Boccassi
Bug#1017104: src:git: fails to migrate to testing for too long: piuparts reports issue
Version: 1:2.39.0-1 On Mon, 13 Jun 2022 21:22:09 +0200 Paul Gevers wrote: The excuses pages tells us that piuparts is reporting an issue with bin:git-daemon-run during removal: rmdir: failed to remove '/var/log/git-daemon': No such file or directory Unknown option: f deluser USER The excuses page is now clean, piuparts is happy. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1024653: marked as done (git: FTBFS on s390x due to test failure, incorrect /proc/cpuinfo parsing)
Your message dated Tue, 20 Dec 2022 22:03:25 +0100
with message-id <1abf52ff-1697-619f-1714-04b00b9f5...@debian.org>
and subject line Re: git: FTBFS on s390x due to test failure, incorrect
/proc/cpuinfo parsing
has caused the Debian Bug report #1024653,
regarding git: FTBFS on s390x due to test failure, incorrect /proc/cpuinfo
parsing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1024653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: git
Version: 1:2.38.1-1
Severity: normal
Dear Maintainer,
git commit 29fb2ec384a867ca577335a12f4b45c184e7b642, present in 2.38.0
and later, introduced a function that gets the number of cores from
/proc/cpuinfo. It essentially does this:
do { local @ARGV='/proc/cpuinfo'; return
scalar(grep(/^processor\s*:/, <>)); } if -r '/proc/cpuinfo';
On s390x, the ^processor lines are like this:
processor 0: version = FF, identification = 148F67, machine = 2964
In other arches (I checked amd64, armhf and arm64), they are like this instead:
processor : 0
As a result, that function is returning 0 on s390x, and that value is
used for the number of jobs the script should execute. Since it's
zero, it exits without doing anything, and that breaks the test and
the build[3] on s390x.
The failure can also be seen in debian's s390x build[4].
I suggest this simple regexp change in t/chainlint.pl:
- do { local @ARGV='/proc/cpuinfo'; return
scalar(grep(/^processor\s*:/, <>)); } if -r '/proc/cpuinfo';
+ do { local @ARGV='/proc/cpuinfo'; return
scalar(grep(/^processor[\s\d]*:/, <>)); } if -r '/proc/cpuinfo';
1. https://github.com/git/git/commit/29fb2ec384a867ca577335a12f4b45c184e7b642
2.
https://github.com/git/git/commit/29fb2ec384a867ca577335a12f4b45c184e7b642#diff-e7042d714d4be11a06d153e6f2daeb3c3a9766b972522baab8ba113b962086cfR574
3.
https://launchpadlibrarian.net/635348769/buildlog_ubuntu-lunar-s390x.git_1%3A2.38.1-1ubuntu1_BUILDING.txt.gz
4.
https://buildd.debian.org/status/fetch.php?pkg=git=s390x=1%3A2.38.1-1=1668068969=0
--- End Message ---
--- Begin Message ---
Version: 1:2.39.0-1
Hi,
The last version uploaded built on s390x.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
Processed: block 1026761 with 1026312
Processing commands for cont...@bugs.debian.org: > block 1026761 with 1026312 Bug #1026761 [src:wreport] wreport: FTBFS: dh_install: error: missing files, aborting 1026761 was not blocked by any bugs. 1026761 was not blocking any bugs. Added blocking bug(s) of 1026761: 1026312 > thanks Stopping processing here. Please contact me if you need assistance. -- 1026761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026761 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1026761
Processing commands for cont...@bugs.debian.org: > affects 1026761 + wreport Bug #1026761 [src:wreport] wreport: FTBFS: dh_install: error: missing files, aborting Added indication that 1026761 affects wreport > thanks Stopping processing here. Please contact me if you need assistance. -- 1026761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026761 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1026761
Processing commands for cont...@bugs.debian.org: > affects 1026761 + dballe Bug #1026761 [src:wreport] wreport: FTBFS: dh_install: error: missing files, aborting Added indication that 1026761 affects dballe > thanks Stopping processing here. Please contact me if you need assistance. -- 1026761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026761 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026772: libsane: The size of the libsane_1.0.31-4.1_amd64.deb package is only about 46 kB whereas the libsane_1.0.27-3.2_amd64.deb package has a size of 2,1 MB.
Package: libsane Version: 1.0.31-4.1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: 15151...@mail.ru Dear Maintainer, The size of the libsane_1.0.31-4.1_amd64.deb package is only about 46 kB whereas the libsane_1.0.27-3.2_amd64.deb package has a size of 2,1 MB. It looks like some files were lost during packaging. It looks like the /lib/udev and /usr/lib branches were completely lost. Only the /usr/share/doc/libsane branch remains. -- System Information: Debian Release: 11.5 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-18-amd64 (SMP w/12 CPU threads)
Bug#1026771: misspell-fixer: flaky autopkgtest
Source: misspell-fixer Version: 0.4-1 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of your package. I noticed that it regularly fails on nearly all architectures. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Don't hesitate to reach out if you need help and some more information from our infrastructure. Paul https://ci.debian.net/data/autopkgtest/testing/i386/m/misspell-fixer/29450943/log.gz diff -ruwb /tmp/misspell-fixer-test/1187/expected/1.txt /tmp/misspell-fixer-test/1187/work/1.txt --- /tmp/misspell-fixer-test/1187/expected/1.txt 2022-12-16 17:16:38.379207670 + +++ /tmp/misspell-fixer-test/1187/work/1.txt 2022-12-16 17:16:38.379207670 + @@ -1,3 +1,3 @@ -successful -successfully -lower than \ No newline at end of file +succesful +succesfully +lower then \ No newline at end of file ASSERT:Expected output differs. https://ci.debian.net/data/autopkgtest/testing/amd64/m/misspell-fixer/29495252/log.gz grep: .misspell-fixer.1192.prepared.grep.patterns: No such file or directory ASSERT: /tmp/autopkgtest-lxc.m76gii84/downtmp/build.pyf/src --- test/expecteds/0.txt2021-01-13 19:01:21.0 + +++ /tmp/misspell-fixer-test/1192/work/0.txt 2022-12-20 09:41:00.880559995 + @@ -1,3 +1,3 @@ -successful -successfully -lower than \ No newline at end of file +succesful +succesfully +lower then \ No newline at end of file ASSERT:Gitignore respected. https://ci.debian.net/data/autopkgtest/testing/armhf/m/misspell-fixer/29128270/log.gz https://ci.debian.net/data/autopkgtest/testing/ppc64el/m/misspell-fixer/29329154/log.gz https://ci.debian.net/data/autopkgtest/testing/s390x/m/misspell-fixer/28654360/log.gz OpenPGP_signature Description: OpenPGP digital signature
Bug#1026734: marked as done (mricron: FTBFS: /usr/bin/ld.bfd: cannot find -lX11: No such file or directory)
Your message dated Tue, 20 Dec 2022 20:49:13 + with message-id and subject line Bug#1026734: fixed in mricron 1.2.20211006+dfsg-3 has caused the Debian Bug report #1026734, regarding mricron: FTBFS: /usr/bin/ld.bfd: cannot find -lX11: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mricron Version: 1.2.20211006+dfsg-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > # first the non-gui parts > cp common/notgui.inc common/isgui.inc > # and now the gui parts > cp common/gui.inc common/isgui.inc > lazbuild --build-all --ws=qt5 --pcp=/etc/lazarus mricron.lpi > SetPrimaryConfigPath NewValue="/etc/lazarus" -> "/etc/lazarus" > InitializeFppkg failed: Unable to create file > "/sbuild-nonexistent/.config/fppkg.cfg": No such file or directory > Hint: (lazarus) [RunTool] "/usr/bin/fpc" "-iWTOTP" > Hint: (lazarus) [RunTool] "/usr/bin/fpc" "-va" "compilertest.pas" > Hint: (lazarus) [RunTool] "/usr/bin/fpc" "-iWTOTP" "-Px86_64" "-Tlinux" > Hint: (lazarus) [RunTool] "/usr/bin/fpc" "-va" "compilertest.pas" "-Px86_64" > "-Tlinux" > TProject.DoLoadStateFile Statefile not found: > /<>/lib/x86_64-linux/mricron.compiled > Hint: (11030) Start of reading config file /etc/fpc.cfg > Hint: (11031) End of reading config file /etc/fpc.cfg > Free Pascal Compiler version 3.2.2+dfsg-17 [2022/11/27] for x86_64 > Copyright (c) 1993-2021 by Florian Klaempfl and others > (1002) Target OS: Linux for x86-64 > (3104) Compiling mricron.lpr > (3104) Compiling uscaledpi.pas > (3104) Compiling nifti_img_view.pas > (3104) Compiling yokesharemem.pas > /<>/yokesharemem.pas(40,1) Warning: (5059) Function result > variable does not seem to be initialized > /<>/yokesharemem.pas(16,28) Hint: (5024) Parameter "lApp" not > used > (3104) Compiling dcm_load.pas > /<>/dcm_load.pas(162,48) Hint: (5057) Local variable "Buffer" > does not seem to be initialized > /<>/dcm_load.pas(265,27) Hint: (5057) Local variable "h" does > not seem to be initialized > /<>/dcm_load.pas(265,24) Hint: (5057) Local variable "w" does > not seem to be initialized > (3104) Compiling fx8.pas > (3104) Compiling ./common/define_types.pas > (3104) Compiling ./common/userdir.pas > (3104) Compiling ./common/define_types.pas > /<>/./common/define_types.pas(330,34) Hint: (5092) Variable > "$result" of a managed type does not seem to be initialized > /<>/./common/define_types.pas(330,45) Hint: (5091) Local > variable "lExt" of a managed type does not seem to be initialized > /<>/./common/define_types.pas(330,40) Hint: (5091) Local > variable "lName" of a managed type does not seem to be initialized > /<>/./common/define_types.pas(392,42) Hint: (5091) Local > variable "lPath" of a managed type does not seem to be initialized > /<>/./common/define_types.pas(392,48) Hint: (5091) Local > variable "lName" of a managed type does not seem to be initialized > /<>/./common/define_types.pas(392,53) Hint: (5091) Local > variable "lExt" of a managed type does not seem to be initialized > /<>/./common/define_types.pas(470,15) Hint: (5028) Local type > "swaptypep" is not used > /<>/./common/define_types.pas(489,15) Hint: (5028) Local type > "swaptypep" is not used > /<>/./common/define_types.pas(773,35) Hint: (5091) Local > variable "lPath" of a managed type does not seem to be initialized > /<>/./common/define_types.pas(773,41) Hint: (5091) Local > variable "lName" of a managed type does not seem to be initialized > /<>/./common/define_types.pas(773,48) Hint: (5091) Local > variable "lExtIn" of a managed type does not seem to be initialized > /<>/./common/def
Bug#1026534: criu: FTBFS: unistd.h:1091:17: error: conflicting types for ‘syscall’; have ‘long int(long int, ...)’
Control: tags -1 + confirmed upstream Control: forwarded -1 https://github.com/checkpoint-restore/criu/issues/1949 Hi Lucas, On Tue, Dec 20, 2022 at 05:14:55PM +0100, Lucas Nussbaum wrote: > Source: criu > Version: 3.17.1-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20221220 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > make[1]: Entering directory '/<>' > > Note: Building criu without amdgpu_plugin. > > Note: libdrm and libdrm_amdgpu are required to build amdgpu_plugin. > > make[1]: git: No such file or directory > > GEN .gitid > > GEN include/common/asm > > GEN compel/include/asm > > touch .config > > GEN compel/include/version.h > > GEN criu/include/version.h > > GEN include/common/config.h > > GEN compel/plugins/include/uapi/std/syscall-codes-64.h > > GEN compel/plugins/include/uapi/std/syscall-64.h > > DEP compel/arch/x86/plugins/std/memcpy.d > > DEP compel/arch/x86/plugins/std/parasite-head.d > > GEN compel/plugins/include/uapi/std/syscall-codes.h > > GEN compel/plugins/include/uapi/std/asm/syscall-types.h > > DEP soccr/soccr.d > > GEN compel/plugins/include/uapi/std/syscall.h > > GEN compel/arch/x86/plugins/std/syscalls-64.S > > DEP compel/arch/x86/plugins/std/syscalls-64.d > > GEN compel/arch/x86/plugins/std/sys-exec-tbl-64.c > > DEP compel/plugins/std/infect.d > > DEP compel/plugins/std/string.d > > DEP compel/plugins/std/log.d > > DEP compel/plugins/std/fds.d > > DEP compel/plugins/std/std.d > > DEP compel/plugins/shmem/shmem.d > > CC soccr/soccr.o > > DEP compel/plugins/fds/fds.d > > CC compel/plugins/std/std.o > > CC compel/plugins/std/fds.o > > CC compel/plugins/std/log.o > > CC compel/plugins/std/string.o > > CC compel/plugins/std/infect.o > > CC compel/arch/x86/plugins/std/parasite-head.o > > CC compel/arch/x86/plugins/std/memcpy.o > > CC compel/arch/x86/plugins/std/syscalls-64.o > > PBCC images/rseq.pb-c.c > > PBCC images/apparmor.pb-c.c > > PBCC images/bpfmap-data.pb-c.c > > PBCC images/fown.pb-c.c > > PBCC images/google/protobuf/descriptor.pb-c.c > > PBCC images/img-streamer.pb-c.c > > PBCC images/timens.pb-c.c > > PBCC images/macvlan.pb-c.c > > PBCC images/autofs.pb-c.c > > PBCC images/sysctl.pb-c.c > > PBCC images/time.pb-c.c > > PBCC images/binfmt-misc.pb-c.c > > PBCC images/seccomp.pb-c.c > > PBCC images/pidns.pb-c.c > > PBCC images/userns.pb-c.c > > PBCC images/cgroup.pb-c.c > > PBCC images/ext-file.pb-c.c > > PBCC images/siginfo.pb-c.c > > PBCC images/rpc.pb-c.c > > PBCC images/rlimit.pb-c.c > > PBCC images/file-lock.pb-c.c > > PBCC images/creds.pb-c.c > > PBCC images/utsns.pb-c.c > > PBCC images/ipc-desc.pb-c.c > > PBCC images/ipc-var.pb-c.c > > PBCC images/sk-opts.pb-c.c > > PBCC images/timer.pb-c.c > > PBCC images/pipe-data.pb-c.c > > PBCC images/sk-packet.pb-c.c > > PBCC images/pstree.pb-c.c > > PBCC images/fs.pb-c.c > > PBCC images/eventpoll.pb-c.c > > PBCC images/eventfd.pb-c.c > > PBCC images/remap-file-path.pb-c.c > > PBCC images/fifo.pb-c.c > > PBCC images/ns.pb-c.c > > PBCC images/cpuinfo.pb-c.c > > PBCC images/stats.pb-c.c > > DEP images/rseq.pb-c.d > > DEP images/apparmor.pb-c.d > > PBCC images/opts.pb-c.c > > DEP images/bpfmap-data.pb-c.d > > DEP images/fown.pb-c.d > > DEP images/google/protobuf/descriptor.pb-c.d > > DEP images/img-streamer.pb-c.d > > DEP images/timens.pb-c.d > > PBCC images/memfd.pb-c.c > > PBCC images/sit.pb-c.c > > DEP images/macvlan.pb-c.d > > DEP images/autofs.pb-c.d > > DEP images/sysctl.pb-c.d > > DEP images/time.pb-c.d > > DEP images/binfmt-misc.pb-c.d > > DEP images/seccomp.pb-c.d > > DEP images/pidns.pb-c.d > > DEP images/userns.pb-c.d > > DEP images/cgroup.pb-c.d >
Processed: Re: Bug#1026534: criu: FTBFS: unistd.h:1091:17: error: conflicting types for ‘syscall’; have ‘long int(long int, ...)’
Processing control commands: > tags -1 + confirmed upstream Bug #1026534 [src:criu] criu: FTBFS: unistd.h:1091:17: error: conflicting types for ‘syscall’; have ‘long int(long int, ...)’ Added tag(s) upstream and confirmed. > forwarded -1 https://github.com/checkpoint-restore/criu/issues/1949 Bug #1026534 [src:criu] criu: FTBFS: unistd.h:1091:17: error: conflicting types for ‘syscall’; have ‘long int(long int, ...)’ Set Bug forwarded-to-address to 'https://github.com/checkpoint-restore/criu/issues/1949'. -- 1026534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026518: marked as done (check-manifest: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13)
Your message dated Tue, 20 Dec 2022 20:39:52 +
with message-id
and subject line Bug#1026518: fixed in check-manifest 0.49-1
has caused the Debian Bug report #1026518,
regarding check-manifest: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.11 3.10" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1026518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: check-manifest
Version: 0.46-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
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:240: python3.11 setup.py config
> running config
> I: pybuild base:240: python3.10 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3.11 setup.py build
> running build
> running build_py
> copying check_manifest.py ->
> /<>/.pybuild/cpython3_3.11_check-manifest/build
> I: pybuild base:240: /usr/bin/python3 setup.py build
> running build
> running build_py
> copying check_manifest.py ->
> /<>/.pybuild/cpython3_3.10_check-manifest/build
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild pybuild:307: cp /<>/tests.py
> /<>/.pybuild/cpython3_3.11_check-manifest/build
> I: pybuild base:240: cd
> /<>/.pybuild/cpython3_3.11_check-manifest/build; python3.11 -m
> pytest -k "not test_build_sdist"
> = test session starts
> ==
> platform linux -- Python 3.11.1, pytest-7.2.0, pluggy-1.0.0+repack
> rootdir: /<>, configfile: setup.cfg
> collected 149 items / 2 deselected / 147 selected
>
> check_manifest.py . [
> 0%]
> tests.py ... [
> 43%]
> FF..s...s... [
> 92%]
> ...
> [100%]
>
> === FAILURES
> ===
> _ TestGit.test_get_versioned_files_with_git_submodules
> _
>
> self =
>
> def test_get_versioned_files_with_git_submodules(self):
> from check_manifest import get_vcs_files
> self._init_repo_with_files('repo1', ['file1', 'file2'])
> self._init_repo_with_files('repo2', ['file3'])
> self._init_repo_with_files('repo3', ['file4'])
> > self._add_submodule('repo2', 'sub3', '../repo3')
>
> tests.py:1094:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> tests.py:1074: in _add_submodule
> self.vcs._run('git', 'submodule', 'add', subrepo, subdir)
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
>
> self =
> command = ('git', 'submodule', 'add', '../repo3', 'sub3')
> p = 'sub3')>
> stdout = b"Cloning into
> '/tmp/test-dztzapgy-check-manifest/repo2/sub3'...\nfatal: transport 'file'
> not allowed\nfatal: clone of '/tmp/test-dztzapgy-check-manifest/repo3' into
> submodule path '/tmp/test-dztzapgy-check-manifest/repo2/sub3' failed\n"
> stderr = None
>
> def _run(self, *command):
> # Windows doesn't like Unicode arguments to subprocess.Popen(), on
> Py2:
> #
> https://github.com/mgedmin/check-manifest/issues/23#issuecomment-33933031
> if str is bytes:
> command = [s.encode(locale.getpreferredencoding()) for s in
> command]
> print('$', ' '.join(command))
> p = subprocess.Popen(command, stdout=subprocess.PIPE,
> stderr=subprocess.STDOUT)
> stdout, stderr = p.communicate()
> rc = p.wait()
> if stdout:
> print(
> stdout if isinstance(stdout, str) else
>
Bug#1023801: marked as done (check-manifest: autopkgtest needs update for new version of git: transport 'file' not allowed)
Your message dated Tue, 20 Dec 2022 20:39:52 +
with message-id
and subject line Bug#1023801: fixed in check-manifest 0.49-1
has caused the Debian Bug report #1023801,
regarding check-manifest: autopkgtest needs update for new version of git:
transport 'file' not allowed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1023801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: check-manifest
Version: 0.46-2
Severity: serious
X-Debbugs-CC: g...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:git
Dear maintainer(s),
With a recent upload of git the autopkgtest of check-manifest fails in
testing when that autopkgtest is run with the binary packages of git
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
gitfrom testing1:2.38.1-1
check-manifest from testing0.46-2
all others from testingfrom testing
I copied some of the output at the bottom of this report. This is due to """
* Addresses the security issue CVE-2022-39253: cloning an
attacker-controlled local repository could store arbitrary files
in the ".git" directory of the destination repository.
"""
This has a nice write up:
https://vielmetti.typepad.com/logbook/2022/10/git-security-fixes-lead-to-fatal-transport-file-not-allowed-error-in-ci-systems-cve-2022-39253.html
Currently this regression is blocking the migration of git to testing
[1]. Of course, git shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in git was
intended and your package needs to update to the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from git should really add a
versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=git
https://ci.debian.net/data/autopkgtest/testing/amd64/c/check-manifest/28079226/log.gz
=== FAILURES
===
_ TestGit.test_get_versioned_files_with_git_submodules
_
self = testMethod=test_get_versioned_files_with_git_submodules>
def test_get_versioned_files_with_git_submodules(self):
from check_manifest import get_vcs_files
self._init_repo_with_files('repo1', ['file1', 'file2'])
self._init_repo_with_files('repo2', ['file3'])
self._init_repo_with_files('repo3', ['file4'])
self._add_submodule('repo2', 'sub3', '../repo3')
tests.py:1094: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ tests.py:1074: in _add_submodule
self.vcs._run('git', 'submodule', 'add', subrepo, subdir)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
self =
command = ('git', 'submodule', 'add', '../repo3', 'sub3')
p = '../repo3', 'sub3')>
stdout = b"Cloning into
'/tmp/test-62xpxof5-check-manifest/repo2/sub3'...\nfatal: transport
'file' not allowed\nfatal: clone of
'/tmp/test-62xpxof5-check-manifest/repo3' into submodule path
'/tmp/test-62xpxof5-check-manifest/repo2/sub3' failed\n"
stderr = None
def _run(self, *command):
# Windows doesn't like Unicode arguments to subprocess.Popen(),
on Py2:
#
https://github.com/mgedmin/check-manifest/issues/23#issuecomment-33933031
if str is bytes:
command = [s.encode(locale.getpreferredencoding()) for s in
command]
print('$', ' '.join(command))
p = subprocess.Popen(command, stdout=subprocess.PIPE,
stderr=subprocess.STDOUT)
stdout, stderr = p.communicate()
rc = p.wait()
if stdout:
print(
stdout if isinstance(stdout, str) else
stdout.decode('ascii', 'backslashreplace')
)
if rc:
raise subprocess.CalledProcessError(rc, command[0], output=stdout)
E subprocess.CalledProcessError: Command 'git' returned
non-zero exit status 128.
Bug#1026769: rust-trust-dns-proto - uninstallable on architectures other than arm* and x86*
Package: rust-trust-dns-proto Version: 0.22.0-1 Severity: serious 01234567890123456789012345678901234567890123456789012345678901234567890123456789 rust-trust-dns-proto has an "optional" (in the cargo sense) dependency on rustls, since collapse_features is used*, this results in it depending but not build-depending on rust-rustls. rustls itself is written in portable rust. However it depends on ring which is written in a mixture of rust, C and asm and current releases only support x86-* and arm-*. There is upstream work to improve portability but I wouldn't feel comfortable packaging a pre-release version of a crypto library and it looks like s390x is still out of luck even with current upstream main So the current situation is that rust-trust-dns-proto is uninstable on three release architectures and is unable to migrate to testing, the question then becomes what to do about it, I see three options. 1. Add architecture restrictions to the packaging so the features are only made available on the relevant architectures. 2. Add build-dependencies so the package is not built on architectures where rustls/ring is available. The request removal of the uninstable package by ftpmaster. 3. Disable rustls support in the trust-dns stack completely. Option 1 is the best from the point of view of offering the widest range of features on each architecture. Unfortunately debcargo is currently unable to do this declaratively, it can only be done by overriding debian/control which makes maintaining the package more annoying. I attempted to implement option 1 with the 0.21.2-4 upload, but I screwed up slightly and as I was about to fix my screwups, my changes were reverted by siretart and he implemented option 2 in the 0.21.2-5 upload. However the upload of 0.22.0-1 seemed to drop the implementation of option 2, leading to the package becoming uninstallable again. Meanwhile over in trust-dns-client, Reinhard seemed to go with the option of disabling rustls support. I don't really mind which option we implement, but it would be good to have a consensus and then do it consistently. * If collapse_features was not used, the affect would be that the main binary package was installable, but the relavent feature packages were not. This would still prevent the package from migrating to testing.
Bug#1023833: marked as done (FTBFS with OpenJDK 17)
Your message dated Tue, 20 Dec 2022 20:36:30 + with message-id and subject line Bug#1023833: fixed in bazel-bootstrap 4.2.3+ds-1 has caused the Debian Bug report #1023833, regarding FTBFS with OpenJDK 17 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1023833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bazel-bootstrap Version: 4.2.2+ds-1 Severity: serious Tags: ftbfs upstream Forwarded: https://github.com/bazelbuild/bazel/issues/15831 The default use of OpenJDK 17 causes bazel-bootstrap to FTBFS. This is an upstream issue and upstream's fix[1] should be cherry-picked as soon as possible. [1] https://github.com/bazelbuild/bazel/pull/16706 --- End Message --- --- Begin Message --- Source: bazel-bootstrap Source-Version: 4.2.3+ds-1 Done: Olek Wojnar We believe that the bug you reported is fixed in the latest version of bazel-bootstrap, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1023...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Olek Wojnar (supplier of updated bazel-bootstrap package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 14 Nov 2022 17:43:02 -0500 Source: bazel-bootstrap Architecture: source Version: 4.2.3+ds-1 Distribution: unstable Urgency: high Maintainer: Debian Bazel Team Changed-By: Olek Wojnar Closes: 1023833 Changes: bazel-bootstrap (4.2.3+ds-1) unstable; urgency=high . * New upstream release * Ease building packages that use Bazel source code - Use default-jdk - Add patch to use "@io_bazel" Bazel package names * Modify d/watch to ignore pre-release tags * Remove unnecessary dependency versioning * Fix FTBFS with OpenJDK 17 (Closes: #1023833) - Add patch for `--add-opens` - Update Bazel package build process in d/rules * Add patch to fix FTBFS with OpenJDK 13+ * Refactor autopkgtests * Add patch to fix test failures with OpenJDK 16+ * Sync add_include_for_limits.patch with upstream * Update build-bash_completion.patch to prevent duplicate file * Set LC_ALL=C for reproducible builds * Add Dockerfile for easy upstream troubleshooting of autopkgtests Checksums-Sha1: a669141e07fdb9e2bdf30718d2ef57cee6901430 3686 bazel-bootstrap_4.2.3+ds-1.dsc 1e8c59e0ad975e506784f2adf0436523453a9da7 10778740 bazel-bootstrap_4.2.3+ds.orig.tar.xz bb04535b1fabb9fe42db0c391d9039f3e319c41a 38744 bazel-bootstrap_4.2.3+ds-1.debian.tar.xz 06a996f67bac8e15df6f9d0bb88c58b61970679b 11830 bazel-bootstrap_4.2.3+ds-1_amd64.buildinfo Checksums-Sha256: 2f61254abed16a9710ec3c6c186edafee4da7f0ef745ba53e83d47a27373e87c 3686 bazel-bootstrap_4.2.3+ds-1.dsc 12da647c178ca4d5925a33c496cc3579db336be3aa6421a4319dc9238d40a1ff 10778740 bazel-bootstrap_4.2.3+ds.orig.tar.xz 21a44aa6dfdc3da39713cd4ce917b11f04a8787a2145173706e363f31329c7a5 38744 bazel-bootstrap_4.2.3+ds-1.debian.tar.xz 930a9d68efd5bcca8b2ef54677867a23c87db942967bbe3032995901b9ca6648 11830 bazel-bootstrap_4.2.3+ds-1_amd64.buildinfo Files: f5cdd7250936e990fb582133c8cbede8 3686 devel optional bazel-bootstrap_4.2.3+ds-1.dsc 1e92233e62df9c3ff048149e75371bee 10778740 devel optional bazel-bootstrap_4.2.3+ds.orig.tar.xz a3d9af7a5b90722021ff1fbf3e0cb593 38744 devel optional bazel-bootstrap_4.2.3+ds-1.debian.tar.xz 3912ada2527547f854629e9a0e11adf5 11830 devel optional bazel-bootstrap_4.2.3+ds-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEELejiDiSiH9jtG0ynfYPUBqCdweQFAmOiDlIACgkQfYPUBqCd weQkXQ/8Dmga+/uCJIFGHA9If60VXvITVeosNv4ShStkTes2KPEhQvc6gCMgglxT kbnhv4AmwGQYKknTBK+s9PivV9oOe5SLJhCaGsvGWxGyqmIN38Wodaf0O82/RobM Chd40dzY8iUNZwri31jildz5TGFN/fi0EC93hitB4gLkst+KK/nbkvhbZv0vvoHQ CM/cGPJD0NLO+1SCL2+9/la704+rrvvAc8cGplsDJU0lAFruqQfCThP4jNQbozxo 6eFXlH6PMgMWSuXqRhhwljy7ATkAxnZ3p0mI7PAZX3yYccACGQwgazQyfRso4IuH IEDm3IwKPh9ZXxVSGhPAcEdo0yN1VPoI3dnPSRT4JBaS+8batmd2AfGQAtlk6L2/ EzR3Tv+lC8nW5QIHpEAAW7s0fZZqKOQdi/L3iq0NJVBk/kQYKMxSwfV3xcLoKuqf 1CZz+f8DJRom8olLabF0WNmK9jX8mCvS2+ptGNvaj7q+5BccGXGzfCgiWeITeHl2 T6/f4fbPQYMB/I/74/nNLeLLJMLCN3tRvr+kdsDOuB+qpwkX3ExHUfAn2aRohe/H
Bug#1024002: marked as done (ruby-nokogiri: FTBFS on s390x)
Your message dated Tue, 20 Dec 2022 21:33:17 +0100 with message-id and subject line Re: ruby-nokogiri: FTBFS on s390x has caused the Debian Bug report #1024002, regarding ruby-nokogiri: FTBFS on s390x to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1024002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-nokogiri Version: 1.13.8+dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=ruby-nokogiri=s390x=1.13.8%2Bdfsg-1=1665929973=0 Nokogiri::HTML4::Document#test_parse_works_with_an_object_that_responds_to_read :239: [BUG] Couldn't unprotect page 0x03ff905b4000, errno: Cannot allocate memory ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [s390x-linux-gnu] -- Control frame information --- c:0027 p:0003 s:0143 e:000142 METHOD :239 c:0026 p:0134 s:0139 e:000138 METHOD /<>/test/helper.rb:124 c:0025 p:0005 s:0135 e:000134 BLOCK /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:103 c:0024 p:0002 s:0132 e:000131 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:195 c:0023 p:0004 s:0127 e:000126 BLOCK /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:102 [FINISH] c:0022 p: s:0123 e:000122 CFUNC :each c:0021 p:0017 s:0119 e:000118 BLOCK /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:101 c:0020 p:0015 s:0116 e:000115 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:281 c:0019 p:0004 s:0111 e:000110 BLOCK /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:94 c:0018 p:0029 s:0108 e:000107 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:376 c:0017 p:0044 s:0100 E:001108 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:221 c:0016 p:0004 s:0093 E:000eb0 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:93 c:0015 p:0058 s:0089 e:88 METHOD /usr/lib/ruby/vendor_ruby/minitest/reporters.rb:44 c:0014 p:0008 s:0082 e:81 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:1042 c:0013 p:0026 s:0075 e:73 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:350 :239: [BUG] Segmentation fault at 0x03ff905ba000 ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [s390x-linux-gnu] -- Control frame information --- c:0027 p:0003 s:0143 e:000142 METHOD :239 c:0026 p:0134 s:0139 e:000138 METHOD /<>/test/helper.rb:124 c:0025 p:0005 s:0135 e:000134 BLOCK /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:103 c:0024 p:0002 s:0132 e:000131 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:195 c:0023 p:0004 s:0127 e:000126 BLOCK /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:102 [FINISH] c:0022 p: s:0123 e:000122 CFUNC :each c:0021 p:0017 s:0119 e:000118 BLOCK /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:101 c:0020 p:0015 s:0116 e:000115 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:281 c:0019 p:0004 s:0111 e:000110 BLOCK /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:94 c:0018 p:0029 s:0108 e:000107 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:376 c:0017 p:0044 s:0100 E:001108 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:221 c:0016 p:0004 s:0093 E:000eb0 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:93 c:0015 p:0058 s:0089 e:88 METHOD /usr/lib/ruby/vendor_ruby/minitest/reporters.rb:44 c:0014 p:0008 s:0082 e:81 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:1042 c:0013 p:0026 s:0075 e:73 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:350 Segmentation fault rake aborted! Command failed with status (139): [ruby -w -I"test" /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb "test/css/test_css.rb" "test/css/test_css_integration.rb" "test/css/test_parser.rb" "test/css/test_tokenizer.rb" "test/css/test_xpath_visitor.rb" "test/decorators/test_slop.rb" "test/html4/sax/test_parser.rb" "test/html4/sax/test_parser_context.rb" "test/html4/sax/test_parser_text.rb" "test/html4/sax/test_push_parser.rb" "test/html4/test_attributes.rb" "test/html4/test_attributes_properly_escaped.rb"
Bug#1020045: marked as done (versiontools: FTBFS: AssertionError: False is not true)
Your message dated Tue, 20 Dec 2022 21:11:41 +0100
with message-id
and subject line Re: Bug#1020045: versiontools: FTBFS: AssertionError: False is
not true
has caused the Debian Bug report #1020045,
regarding versiontools: FTBFS: AssertionError: False is not true
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1020045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020045
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: versiontools
Version: 1.9.1-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm
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=pybuild --with python3
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py config
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning:
> Distutils was imported before Setuptools, but importing Setuptools also
> replaces the `distutils` module in `sys.modules`. This may lead to
> undesirable behaviors or errors. To avoid these issues, avoid using distutils
> directly, ensure that setuptools is installed in the traditional way (e.g.
> not an editable install), and/or make sure that setuptools is always imported
> before distutils.
> warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning:
> Setuptools is replacing distutils.
> warnings.warn("Setuptools is replacing distutils.")
> /usr/lib/python3/dist-packages/setuptools/dist.py:771: UserWarning: Usage of
> dash-separated 'upload-dir' will not be supported in future versions. Please
> use the underscore name 'upload_dir' instead
> warnings.warn(
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning:
> Distutils was imported before Setuptools, but importing Setuptools also
> replaces the `distutils` module in `sys.modules`. This may lead to
> undesirable behaviors or errors. To avoid these issues, avoid using distutils
> directly, ensure that setuptools is installed in the traditional way (e.g.
> not an editable install), and/or make sure that setuptools is always imported
> before distutils.
> warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning:
> Setuptools is replacing distutils.
> warnings.warn("Setuptools is replacing distutils.")
> /usr/lib/python3/dist-packages/setuptools/dist.py:771: UserWarning: Usage of
> dash-separated 'upload-dir' will not be supported in future versions. Please
> use the underscore name 'upload_dir' instead
> warnings.warn(
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.10_versiontools/build/versiontools
> copying versiontools/__init__.py ->
> /<>/.pybuild/cpython3_3.10_versiontools/build/versiontools
> copying versiontools/tests.py ->
> /<>/.pybuild/cpython3_3.10_versiontools/build/versiontools
> copying versiontools/versiontools_support.py ->
> /<>/.pybuild/cpython3_3.10_versiontools/build/versiontools
> copying versiontools/git_support.py ->
> /<>/.pybuild/cpython3_3.10_versiontools/build/versiontools
> copying versiontools/bzr_support.py ->
> /<>/.pybuild/cpython3_3.10_versiontools/build/versiontools
> copying versiontools/setuptools_hooks.py ->
> /<>/.pybuild/cpython3_3.10_versiontools/build/versiontools
> copying versiontools/hg_support.py ->
> /<>/.pybuild/cpython3_3.10_versiontools/build/versiontools
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py test
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning:
> Distutils was imported before Setuptools, but importing Setuptools also
> replaces the `distutils` module in `sys.modules`. This may lead to
> undesirable behaviors or errors. To avoid these issues, avoid using distutils
> directly, ensure that setuptools is installed in the traditional way (e.g.
> not an editable install), and/or make sure that setuptools is always imported
> before distutils.
> warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning:
> Setuptools is replacing distutils.
> warnings.warn("Setuptools is replacing distutils.")
> /usr/lib/python3/dist-packages/setuptools/dist.py:771: UserWarning: Usage
Bug#1016328: marked as done (mandelbulber2: FTBFS: Last OS error: No such file or directory)
Your message dated Tue, 20 Dec 2022 21:05:23 +0100 with message-id and subject line Re: Bug#1016328: mandelbulber2: FTBFS: Last OS error: No such file or directory has caused the Debian Bug report #1016328, regarding mandelbulber2: FTBFS: Last OS error: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1016328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mandelbulber2 Version: 2.20-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220728 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > xsltproc -''-nonet -''-param man.charmap.use.subset "0" > /usr/share/xml/docbook/stylesheet/docbook-xsl/manpages/docbook.xsl > debian/mandelbulber2.man.xml > I/O error : Attempt to load network entity > http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd > debian/mandelbulber2.man.xml:55: warning: failed to load external entity > "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd; > ]> > ^ > Note: Writing mandelbulber2.1 > cd docs ; ./build.sh > This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Debian) > (preloaded format=pdflatex) > restricted \write18 enabled. > entering extended mode > (./handbook.tex > LaTeX2e <2022-06-01> patch level 5 > L3 programming layer <2022-07-15> (./mandelbulber2/preamble.tex > (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls > Document Class: article 2021/10/04 v1.4n Standard LaTeX document class > (/usr/share/texlive/texmf-dist/tex/latex/base/size12.clo)) > (/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty) > (/usr/share/texlive/texmf-dist/tex/generic/iftex/ifvtex.sty > (/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty))) > (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty > (/usr/share/texlive/texmf-dist/tex/latex/ucs/utf8x.def)) > (/usr/share/texlive/texmf-dist/tex/latex/ucs/ucs.sty > (/usr/share/texlive/texmf-dist/tex/latex/ucs/data/uni-global.def)) > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty > For additional information on amsmath, use the `?' option. > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty) > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty) > (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty) > (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty) > (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg) > (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def))) > (/usr/share/texlive/texmf-dist/tex/latex/tools/longtable.sty) > (/usr/share/texlive/texmf-dist/tex/latex/booktabs/booktabs.sty) > (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty > (/usr/share/texlive/texmf-dist/tex/generic/ltxcmds/ltxcmds.sty) > (/usr/share/texlive/texmf-dist/tex/generic/pdftexcmds/pdftexcmds.sty > (/usr/share/texlive/texmf-dist/tex/generic/infwarerr/infwarerr.sty)) > (/usr/share/texlive/texmf-dist/tex/generic/kvsetkeys/kvsetkeys.sty) > (/usr/share/texlive/texmf-dist/tex/generic/kvdefinekeys/kvdefinekeys.sty) > (/usr/share/texlive/texmf-dist/tex/generic/pdfescape/pdfescape.sty) > (/usr/share/texlive/texmf-dist/tex/latex/hycolor/hycolor.sty) > (/usr/share/texlive/texmf-dist/tex/latex/letltxmacro/letltxmacro.sty) > (/usr/share/texlive/texmf-dist/tex/latex/auxhook/auxhook.sty) > (/usr/share/texlive/texmf-dist/tex/latex/hyperref/nameref.sty > (/usr/share/texlive/texmf-dist/tex/latex/refcount/refcount.sty) > (/usr/share/texlive/texmf-dist/tex/generic/gettitlestring/gettitlestring.sty > (/usr/share/texlive/texmf-dist/tex/latex/kvoptions/kvoptions.sty))) > (/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def) > (/usr/share/texlive/texmf-dist/tex/generic/intcalc/intcalc.sty) > (/usr/share/texlive/texmf-dist/tex/generic/etexcmds/etexcmds.sty) > (/usr/share/texlive/texmf-dist/tex/latex/hyperref/puenc.def) > (/usr/share/texlive/texmf-dist/tex/latex/url/url.sty) > (/usr/share/texlive/texmf-dist/tex/generic/bitset/bitset.sty >
Bug#1022315: marked as done (ruby-puma-worker-killer: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:311:in `to_specs': Could not find 'puma' (>= 2.7) among 106
Your message dated Tue, 20 Dec 2022 21:09:16 +0100 with message-id and subject line Re: Bug#1022315: ruby-puma-worker-killer: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:311:in `to_specs': Could not find 'puma' (>= 2.7) among 106 total gem(s) (Gem::MissingSpecError) has caused the Debian Bug report #1022315, regarding ruby-puma-worker-killer: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:311:in `to_specs': Could not find 'puma' (>= 2.7) among 106 total gem(s) (Gem::MissingSpecError) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022315 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-puma-worker-killer Version: 0.3.1-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:311:in `to_specs': Could not > find 'puma' (>= 2.7) among 106 total gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-puma-worker-killer/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1411:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > abbrev (default: 0.1.0) > ast (2.4.1) > base64 (default: 0.1.0) > benchmark (default: 0.1.1) > bigdecimal (default: 3.0.0) > bundler (2.3.15, default: 2.2.33) > cgi (default: 0.2.1) > csv (default: 3.1.9) > date (default: 3.1.3) > dbm (default: 1.1.0) > debug (default: 0.2.1) > delegate (default: 0.2.0) > did_you_mean (default: 1.5.0) > digest (default: 3.0.0) > drb (default: 2.0.5) > english (default: 0.7.1) > erb (default: 2.2.0) > etc (default: 1.3.0) > fcntl (default: 1.0.1) > ffi (1.15.4) > fiddle (default: 1.0.8) > fileutils (default: 1.5.0) > find (default: 0.1.0) > forwardable (default: 1.3.2) > gdbm (default: 2.1.0) > get_process_mem (0.2.5) > getoptlong (default: 0.1.1) > io-console (default: 0.5.7) > io-nonblock (default: 0.1.0) > io-wait (default: 0.2.0) > ipaddr (default: 1.2.2) > irb (default: 1.3.5) > json (default: 2.5.1) > logger (default: 1.4.3) > matrix (default: 0.3.1) > minitest (5.14.2) > mutex_m (default: 0.1.1) > net-ftp (default: 0.1.2) > net-http (default: 0.1.1) > net-imap (default: 0.1.1) > net-pop (default: 0.1.1) > net-protocol (default: 0.1.1) > net-smtp (default: 0.2.1) > net-telnet (0.1.1) > nio4r (2.5.8) > nkf (default: 0.1.0) > observer (default: 0.1.1) > open-uri (default: 0.1.0) > open3 (default: 0.1.1) > openssl (default: 3.0.0) > optparse (default: 0.1.1) > ostruct (default: 0.3.1) > parallel (1.22.1) > parser (3.0.2.0) > pathname (default: 0.1.0) > power_assert (1.2.0) > pp (default: 0.2.1) > prettyprint (default: 0.1.1) > prime (default: 0.1.2) > pstore (default: 0.1.1) > psych (default: 3.3.2) > puma (5.6.4) > racc (default: 1.5.2) > rack (2.2.4) > rainbow (3.1.1) > rake (13.0.6, 13.0.3) > rbs (1.4.0) > rdoc (default: 6.3.3) > readline (default: 0.0.2) > readline-ext (default: 0.1.1) > regexp_parser (2.1.1) > reline (default: 0.2.5) > resolv (default: 0.2.1) > resolv-replace (default: 0.1.0) > rexml (3.2.5) > rinda (default: 0.1.1) > rss (0.2.9) > rubocop (0.89.1) > rubocop-ast (0.6.0) > ruby-progressbar (1.11.0) > rubygems-update (3.3.15) > sdbm (1.0.0) > securerandom (default: 0.1.0) > set (default: 1.0.1) > shellwords (default: 0.1.0) > singleton (default: 0.1.1) > stringio (default: 3.0.1) > strscan (default: 3.0.1) > syslog (default: 0.1.0) > tempfile (default:
Bug#1011674: marked as done (ruby-rack-oauth2: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: private_key: OpenSSL::PKey::EC.new('prime256v1').generate_key,)
Your message dated Tue, 20 Dec 2022 21:10:02 +0100
with message-id
and subject line Re: Bug#1011674: ruby-rack-oauth2: FTBFS: ERROR: Test
"ruby3.0" failed: Failure/Error: private_key:
OpenSSL::PKey::EC.new('prime256v1').generate_key,
has caused the Debian Bug report #1011674,
regarding ruby-rack-oauth2: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error:
private_key: OpenSSL::PKey::EC.new('prime256v1').generate_key,
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1011674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rack-oauth2
Version: 1.19.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> Failure/Error: private_key:
> OpenSSL::PKey::EC.new('prime256v1').generate_key,
>
> OpenSSL::PKey::PKeyError:
>pkeys are immutable on OpenSSL 3.0
> # ./spec/rack/oauth2/client_spec.rb:189:in `generate_key!'
> # ./spec/rack/oauth2/client_spec.rb:189:in `block (8 levels) in (required)>'
> # ./spec/rack/oauth2/client_spec.rb:87:in `block (5 levels) in (required)>'
>
> Finished in 0.69138 seconds (files took 0.77443 seconds to load)
> 396 examples, 1 failure
>
> Failed examples:
>
> rspec ./spec/rack/oauth2/client_spec.rb:195 #
> Rack::OAuth2::Client#access_token! *args handling client authentication
> method when jwt_bearer auth method specified when private_key is given when
> EC key should be JWT bearer client assertion w/ auto-generated ES256-signed
> JWT assertion
>
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.0" failed:
The full build log is available from:
http://qa-logs.debian.net/2022/05/25/ruby-rack-oauth2_1.19.0-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=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 marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
I cannot reproduce this anymore => closing--- End Message ---
Bug#1015069: marked as done (pagure: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)
Your message dated Tue, 20 Dec 2022 21:06:08 +0100 with message-id and subject line Re: Bug#1015069: pagure: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity has caused the Debian Bug report #1015069, regarding pagure: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1015069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015069 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pagure Version: 5.11.3+dfsg-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): >dh_builddeb -O--buildsystem=pybuild > dpkg-deb: building package 'pagure-ci' in > '../pagure-ci_5.11.3+dfsg-1_all.deb'. > dpkg-deb: building package 'pagure-logcom' in > '../pagure-logcom_5.11.3+dfsg-1_all.deb'. > dpkg-deb: building package 'pagure-doc' in > '../pagure-doc_5.11.3+dfsg-1_all.deb'. > dpkg-deb: building package 'pagure-milters' in > '../pagure-milters_5.11.3+dfsg-1_all.deb'. > dpkg-deb: building package 'pagure' in '../pagure_5.11.3+dfsg-1_all.deb'. > dpkg-deb: building package 'pagure-mirror' in > '../pagure-mirror_5.11.3+dfsg-1_all.deb'. > dpkg-deb: building package 'pagure-loadjson' in > '../pagure-loadjson_5.11.3+dfsg-1_all.deb'. > dpkg-deb: building package 'pagure-webhook' in > '../pagure-webhook_5.11.3+dfsg-1_all.deb'. > dpkg-deb: building package 'pagure-ev-server' in > '../pagure-ev-server_5.11.3+dfsg-1_all.deb'. > dpkg-genbuildinfo -O../pagure_5.11.3+dfsg-1_amd64.buildinfo > dpkg-genchanges -sa -O../pagure_5.11.3+dfsg-1_amd64.changes > dpkg-genchanges: info: including full source code in upload > dpkg-source --after-build . > dpkg-buildpackage: info: full upload (original source is included) > E: Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://qa-logs.debian.net/2022/07/16/pagure_5.11.3+dfsg-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=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 marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- I cannot reproduce this anymore => closing--- End Message ---
Bug#1015040: marked as done (php-ps: FTBFS: cc: error: unrecognized command-line option '-V')
Your message dated Tue, 20 Dec 2022 21:06:50 +0100 with message-id and subject line Re: Bug#1015040: php-ps: FTBFS: cc: error: unrecognized command-line option '-V' has caused the Debian Bug report #1015040, regarding php-ps: FTBFS: cc: error: unrecognized command-line option '-V' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1015040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-ps Version: 1.4.4+1.3.7-6 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc version 11.3.0 (Debian 11.3.0-4) > ... rest of stderr output deleted ... > configure:3103: $? = 0 > configure:3092: cc -V >&5 > cc: error: unrecognized command-line option '-V' > cc: fatal error: no input files > compilation terminated. > configure:3103: $? = 1 > configure:3092: cc -qversion >&5 > cc: error: unrecognized command-line option '-qversion'; did you mean > '--version'? > cc: fatal error: no input files > compilation terminated. > configure:3103: $? = 1 > configure:3092: cc -version >&5 > cc: error: unrecognized command-line option '-version' > cc: fatal error: no input files > compilation terminated. > configure:3103: $? = 1 > configure:3123: checking whether the C compiler works > configure:3145: cc -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic > -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -Wl,--as-needed > conftest.c >&5 > configure:3149: $? = 0 > configure:3199: result: yes > configure:3202: checking for C compiler default output file name > configure:3204: result: a.out > configure:3210: checking for suffix of executables > configure:3217: cc -o conftest -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic > -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -Wl,--as-needed > conftest.c >&5 > configure:3221: $? = 0 > configure:3244: result: > configure:3266: checking whether we are cross compiling > configure:3274: cc -o conftest -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic > -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -Wl,--as-needed > conftest.c >&5 > configure:3278: $? = 0 > configure:3285: ./conftest > configure:3289: $? = 0 > configure:3304: result: no > configure:3309: checking for suffix of object files > configure:3332: cc -c -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic > -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5 > configure:3336: $? = 0 > configure:3358: result: o > configure:3362: checking whether the compiler supports GNU C > configure:3382: cc -c -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic > -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5 > configure:3382: $? = 0 > configure:3392: result: yes > configure:3403: checking whether cc accepts -g > configure:3424: cc -c -g -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5 > configure:3424: $? = 0 > configure:3468: result: yes > configure:3488: checking for cc option to enable C11 features > configure:3503: cc -c -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic > -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5 > configure:3503: $? = 0 > configure:3521: result: none needed > configure:3637: checking how to run the C preprocessor > configure:3663: cc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c > configure:3663: $? = 0 > configure:3678: cc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c > conftest.c:9:10: fatal error: ac_nonexistent.h: No such file or directory > 9 | #include > | ^~ > compilation terminated. > configure:3678: $? = 1 > configure: failed program was: > | /* confdefs.h */ > | #define PACKAGE_NAME "" > | #define PACKAGE_TARNAME "" > | #define PACKAGE_VERSION "" > | #define PACKAGE_STRING "" > | #define PACKAGE_BUGREPORT "" > | #define PACKAGE_URL "" > | /* end confdefs.h. */ > | #include > configure:3705: result: cc -E > configure:3719: cc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c > configure:3719: $? = 0 > configure:3734: cc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c > conftest.c:9:10: fatal error: ac_nonexistent.h: No such file or
Bug#1013506: marked as done (python-ara: FTBFS: ImportError: cannot import name 'url' from 'django.conf.urls' (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py))
Your message dated Tue, 20 Dec 2022 21:07:40 +0100
with message-id
and subject line Re: Bug#1013506: python-ara: FTBFS: ImportError: cannot import
name 'url' from 'django.conf.urls'
(/usr/lib/python3/dist-packages/django/conf/urls/__init__.py)
has caused the Debian Bug report #1013506,
regarding python-ara: FTBFS: ImportError: cannot import name 'url' from
'django.conf.urls' (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1013506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-ara
Version: 1.5.8-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom \
> PYBUILD_TEST_ARGS="{interpreter} manage.py test -v 2 ara" \
> dh_auto_test
> I: pybuild base:239: python3.9 manage.py test -v 2 ara
> [ara] No setting found for SECRET_KEY. Generating a random key...
> /<>/ara/server/settings.py:216: PytzUsageWarning: The zone
> attribute is specific to pytz's interface; please migrate to a new time zone
> provider. For more details on how to do so, see
> https://pytz-deprecation-shim.readthedocs.io/en/latest/migration.html
> LOCAL_TIME_ZONE = tzlocal.get_localzone().zone
> [ara] Writing default settings to /tmp/settings.yaml
> [ara] Using settings file: /tmp/settings.yaml
> Found 169 test(s).
> Creating test database for alias 'default'
> ('file:memorydb_default?mode=memory=shared')...
> Operations to perform:
> Synchronize unmigrated apps: corsheaders, django_filters, health_check,
> messages, rest_framework, staticfiles, ui
> Apply all migrations: admin, api, auth, contenttypes, db, sessions
> Synchronizing apps without migrations:
> Creating tables...
> Running deferred SQL...
> Running migrations:
> Applying contenttypes.0001_initial... OK
> Applying auth.0001_initial... OK
> Applying admin.0001_initial... OK
> Applying admin.0002_logentry_remove_auto_add... OK
> Applying admin.0003_logentry_add_action_flag_choices... OK
> Applying api.0001_initial... OK
> Applying api.0002_remove_host_alias... OK
> Applying api.0003_add_missing_result_properties... OK
> Applying api.0004_duration_in_database... OK
> Applying api.0005_unique_label_names... OK
> Applying api.0006_remove_result_statuses... OK
> Applying api.0007_add_expired_status... OK
> Applying api.0008_playbook_controller... OK
> Applying api.0009_latesthost... OK
> Applying api.0010_result_delegated_to... OK
> Applying contenttypes.0002_remove_content_type_name... OK
> Applying auth.0002_alter_permission_name_max_length... OK
> Applying auth.0003_alter_user_email_max_length... OK
> Applying auth.0004_alter_user_username_opts... OK
> Applying auth.0005_alter_user_last_login_null... OK
> Applying auth.0006_require_contenttypes_0002... OK
> Applying auth.0007_alter_validators_add_error_messages... OK
> Applying auth.0008_alter_user_username_max_length... OK
> Applying auth.0009_alter_user_last_name_max_length... OK
> Applying auth.0010_alter_group_name_max_length... OK
> Applying auth.0011_update_proxy_permissions... OK
> Applying auth.0012_alter_user_first_name_max_length... OK
> Applying db.0001_initial... OK
> Applying sessions.0001_initial... OK
> Destroying test database for alias 'default'
> ('file:memorydb_default?mode=memory=shared')...
> Traceback (most recent call last):
> File "/<>/manage.py", line 22, in
> main()
> File "/<>/ara/server/__main__.py", line 66, in main
> execute_from_command_line(sys.argv)
> File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
> line 446, in execute_from_command_line
> utility.execute()
> File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
> line 440, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
> File
> "/usr/lib/python3/dist-packages/django/core/management/commands/test.py",
> line 24, in run_from_argv
> super().run_from_argv(argv)
> File "/usr/lib/python3/dist-packages/django/core/management/base.py", line
> 414, in run_from_argv
> self.execute(*args, **cmd_options)
> File "/usr/lib/python3/dist-packages/django/core/management/base.py", line
> 460, in execute
> output = self.handle(*args, **options)
> File
>
Bug#1011685: marked as done (ruby-openid-connect: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error:)
Your message dated Tue, 20 Dec 2022 21:08:35 +0100 with message-id and subject line Re: Bug#1011685: ruby-openid-connect: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: has caused the Debian Bug report #1011685, regarding ruby-openid-connect: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1011685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011685 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-openid-connect Version: 1.2.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220525 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Failure/Error: >expect do > klass.decode self_issued, :self_issued >end.not_to raise_error > >expected no Exception, got # incompatible with OpenSSL 3.0> with backtrace: > # > /usr/share/rubygems-integration/all/gems/json-jwt-1.13.0/lib/json/jwk.rb:106:in > `set_key' > # > /usr/share/rubygems-integration/all/gems/json-jwt-1.13.0/lib/json/jwk.rb:106:in > `to_rsa_key' > # > /usr/share/rubygems-integration/all/gems/json-jwt-1.13.0/lib/json/jwk.rb:43:in > `to_key' > # > /usr/share/rubygems-integration/all/gems/json-jwt-1.13.0/lib/json/jose.rb:27:in > `with_jwk_support' > # > /usr/share/rubygems-integration/all/gems/json-jwt-1.13.0/lib/json/jws.rb:124:in > `valid?' > # > /usr/share/rubygems-integration/all/gems/json-jwt-1.13.0/lib/json/jws.rb:26:in > `verify!' > # ./lib/openid_connect/response_object/id_token.rb:79:in > `decode_self_issued' > # ./lib/openid_connect/response_object/id_token.rb:68:in `decode' > # ./spec/openid_connect/response_object/id_token_spec.rb:263:in > `block (7 levels) in ' > # ./spec/openid_connect/response_object/id_token_spec.rb:262:in > `block (6 levels) in ' > # ./spec/openid_connect/response_object/id_token_spec.rb:262:in `block > (6 levels) in ' > > Finished in 13.15 seconds (files took 1.19 seconds to load) > 234 examples, 2 failures, 2 pending > > Failed examples: > > rspec ./spec/openid_connect/discovery/provider/config/response_spec.rb:98 # > OpenIDConnect::Discovery::Provider::Config::Response#public_keys > rspec ./spec/openid_connect/response_object/id_token_spec.rb:261 # > OpenIDConnect::ResponseObject::IdToken.decode when self-issued when valid > when key == :self_issued is expected not to raise Exception > > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.0" failed: The full build log is available from: http://qa-logs.debian.net/2022/05/25/ruby-openid-connect_1.2.0-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=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 marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- I cannot reproduce this anymore => closing--- End Message ---
Bug#1022499: marked as done (fades: FTBFS: TypeError: dist must be a Distribution instance)
Your message dated Tue, 20 Dec 2022 21:02:09 +0100
with message-id
and subject line Re: Bug#1022499: fades: FTBFS: TypeError: dist must be a
Distribution instance
has caused the Debian Bug report #1022499,
regarding fades: FTBFS: TypeError: dist must be a Distribution instance
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1022499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fades
Version: 9.0.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py clean
> /<>/setup.py:35: DeprecationWarning: The distutils package is
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP
> 632 for potential alternatives
> from distutils.core import setup
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning:
> Distutils was imported before Setuptools, but importing Setuptools also
> replaces the `distutils` module in `sys.modules`. This may lead to
> undesirable behaviors or errors. To avoid these issues, avoid using distutils
> directly, ensure that setuptools is installed in the traditional way (e.g.
> not an editable install), and/or make sure that setuptools is always imported
> before distutils.
> warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning:
> Setuptools is replacing distutils.
> warnings.warn("Setuptools is replacing distutils.")
> /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution
> option: 'install_requires'
> warnings.warn(msg)
> /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution
> option: 'tests_require'
> warnings.warn(msg)
> /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution
> option: 'python_requires'
> warnings.warn(msg)
> /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution
> option: 'extras_require'
> warnings.warn(msg)
> running clean
> Traceback (most recent call last):
> File "/<>/setup.py", line 104, in
> setup(
> File "/usr/lib/python3.10/distutils/core.py", line 148, in setup
> dist.run_commands()
> File "/usr/lib/python3.10/distutils/dist.py", line 966, in run_commands
> self.run_command(cmd)
> File "/usr/lib/python3.10/distutils/dist.py", line 983, in run_command
> cmd_obj = self.get_command_obj(command)
> File "/usr/lib/python3.10/distutils/dist.py", line 858, in get_command_obj
> cmd_obj = self.command_obj[command] = klass(self)
> File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 158, in
> __init__
> super().__init__(dist)
> File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line
> 59, in __init__
> raise TypeError("dist must be a Distribution instance")
> TypeError: dist must be a Distribution instance
> E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1:
> python3.10 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned
> exit code 13
> make: *** [debian/rules:10: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2022/10/23/fades_9.0.1-3_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=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 marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
I cannot reproduce this anymore => closing--- End Message ---
Bug#1016334: marked as done (dvdisaster: FTBFS: ! Argument of ? has an extra }.)
Your message dated Tue, 20 Dec 2022 21:00:02 +0100 with message-id and subject line Re: Bug#1016334: dvdisaster: FTBFS: make[2]: *** [GNUmakefile:209: manual] Error 2 has caused the Debian Bug report #1016334, regarding dvdisaster: FTBFS: ! Argument of ? has an extra }. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1016334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dvdisaster Version: 0.79.5-10 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220728 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > Producing user manual... > /usr/bin/gmake --no-print-directory -C documentation/user-manual manual.pdf > pdflatex manual > This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Debian) > (preloaded format=pdflatex) > restricted \write18 enabled. > entering extended mode > (./manual.tex > LaTeX2e <2022-06-01> patch level 5 > L3 programming layer <2022-07-15> > (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls > Document Class: article 2021/10/04 v1.4n Standard LaTeX document class > (/usr/share/texlive/texmf-dist/tex/latex/base/size12.clo)) > (/usr/share/texlive/texmf-dist/tex/latex/psnfss/times.sty) > (/usr/share/texlive/texmf-dist/tex/latex/ucs/ucs.sty > (/usr/share/texlive/texmf-dist/tex/latex/ucs/data/uni-global.def)) > (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty > (/usr/share/texlive/texmf-dist/tex/latex/ucs/utf8x.def)) > (/usr/share/texlive/texmf-dist/tex/latex/graphics/epsfig.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty) > (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty) > (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg) > (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def > (/usr/share/texlive/texmf-dist/tex/latex/anysize/anysize.sty > document style option `anysize' loaded > Michael Salzenberg, Thomas Esser, Dirk Hillbrecht > Version 1.0, Aug 13, 1994 > ) (/usr/share/texlive/texmf-dist/tex/latex/url/url.sty) > (/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty) > (/usr/share/texlive/texmf-dist/tex/latex/listings/listings.sty > (/usr/share/texlive/texmf-dist/tex/latex/listings/lstmisc.sty) > (/usr/share/texlive/texmf-dist/tex/latex/listings/listings.cfg)) > (/usr/share/texlive/texmf-dist/tex/latex/graphics/color.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg) > (/usr/share/texlive/texmf-dist/tex/latex/graphics/mathcolor.ltx)) > (/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg) > (/usr/share/texlive/texmf-dist/tex/latex/colortbl/colortbl.sty > (/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/graphics/mathcolor.ltx)) > (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty > (/usr/share/texlive/texmf-dist/tex/generic/ltxcmds/ltxcmds.sty) > (/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty) > (/usr/share/texlive/texmf-dist/tex/generic/pdftexcmds/pdftexcmds.sty > (/usr/share/texlive/texmf-dist/tex/generic/infwarerr/infwarerr.sty)) > (/usr/share/texlive/texmf-dist/tex/generic/kvsetkeys/kvsetkeys.sty) > (/usr/share/texlive/texmf-dist/tex/generic/kvdefinekeys/kvdefinekeys.sty) > (/usr/share/texlive/texmf-dist/tex/generic/pdfescape/pdfescape.sty) > (/usr/share/texlive/texmf-dist/tex/latex/hycolor/hycolor.sty) > (/usr/share/texlive/texmf-dist/tex/latex/letltxmacro/letltxmacro.sty) > (/usr/share/texlive/texmf-dist/tex/latex/auxhook/auxhook.sty) > (/usr/share/texlive/texmf-dist/tex/latex/hyperref/nameref.sty > (/usr/share/texlive/texmf-dist/tex/latex/refcount/refcount.sty) > (/usr/share/texlive/texmf-dist/tex/generic/gettitlestring/gettitlestring.sty > (/usr/share/texlive/texmf-dist/tex/latex/kvoptions/kvoptions.sty))) > (/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def) > (/usr/share/texlive/texmf-dist/tex/generic/intcalc/intcalc.sty) > (/usr/share/texlive/texmf-dist/tex/generic/etexcmds/etexcmds.sty) > (/usr/share/texlive/texmf-dist/tex/latex/hyperref/puenc.def) > (/usr/share/texlive/texmf-dist/tex/generic/bitset/bitset.sty > (/usr/share/texlive/texmf-dist/tex/generic/bigintcalc/bigintcalc.sty)) >
Bug#1013468: marked as done (autoradio: FTBFS: ImportError: cannot import name 'ugettext_lazy' from 'django.utils.translation' (/usr/lib/python3/dist-packages/django/utils/translation/__init__.py))
Your message dated Tue, 20 Dec 2022 20:58:31 +0100
with message-id
and subject line Re: Bug#1013468: autoradio: FTBFS: ImportError: cannot import
name 'ugettext_lazy' from 'django.utils.translation'
(/usr/lib/python3/dist-packages/django/utils/translation/__init__.py)
has caused the Debian Bug report #1013468,
regarding autoradio: FTBFS: ImportError: cannot import name 'ugettext_lazy'
from 'django.utils.translation'
(/usr/lib/python3/dist-packages/django/utils/translation/__init__.py)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1013468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: autoradio
Version: 3.4-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_clean
> I: pybuild base:239: python3.10 setup.py clean
> /<>/setup.py:2: DeprecationWarning: The distutils package is
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP
> 632 for potential alternatives
> from distutils.core import setup
> django_extensions is not installed; I do not use it
> Traceback (most recent call last):
> File "/<>/setup.py", line 17, in
> django.setup()
> File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, in setup
> apps.populate(settings.INSTALLED_APPS)
> File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 116, in
> populate
> app_config.import_models()
> File "/usr/lib/python3/dist-packages/django/apps/config.py", line 304, in
> import_models
> self.models_module = import_module(models_module_name)
> File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> File "", line 1050, in _gcd_import
> File "", line 1027, in _find_and_load
> File "", line 1006, in _find_and_load_unlocked
> File "", line 688, in _load_unlocked
> File "", line 883, in exec_module
> File "", line 241, in _call_with_frames_removed
> File "/<>/autoradio/programs/models.py", line 7, in
> from django.utils.translation import ugettext_lazy
> ImportError: cannot import name 'ugettext_lazy' from
> 'django.utils.translation'
> (/usr/lib/python3/dist-packages/django/utils/translation/__init__.py)
> E: pybuild pybuild:369: clean: plugin distutils failed with: exit code=1:
> python3.10 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned
> exit code 13
> make[1]: *** [debian/rules:10: override_dh_auto_clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2022/06/24/autoradio_3.4-4_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220624=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 marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
I cannot reproduce this anymore => closing--- End Message ---
Bug#1002334: marked as done (aiohttp-wsgi: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13)
Your message dated Tue, 20 Dec 2022 20:57:20 +0100
with message-id
and subject line Re: Bug#1002334: aiohttp-wsgi: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13
has caused the Debian Bug report #1002334,
regarding aiohttp-wsgi: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p "3.10 3.9" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1002334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002334
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aiohttp-wsgi
Version: 0.8.2-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
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,sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:237: python3.10 setup.py config
> running config
> I: pybuild base:237: python3.9 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:237: /usr/bin/python3.10 setup.py build
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.10_aiohttp-wsgi/build/aiohttp_wsgi
> copying aiohttp_wsgi/__init__.py ->
> /<>/.pybuild/cpython3_3.10_aiohttp-wsgi/build/aiohttp_wsgi
> copying aiohttp_wsgi/__main__.py ->
> /<>/.pybuild/cpython3_3.10_aiohttp-wsgi/build/aiohttp_wsgi
> copying aiohttp_wsgi/wsgi.py ->
> /<>/.pybuild/cpython3_3.10_aiohttp-wsgi/build/aiohttp_wsgi
> copying aiohttp_wsgi/utils.py ->
> /<>/.pybuild/cpython3_3.10_aiohttp-wsgi/build/aiohttp_wsgi
> I: pybuild base:237: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.9_aiohttp-wsgi/build/aiohttp_wsgi
> copying aiohttp_wsgi/__init__.py ->
> /<>/.pybuild/cpython3_3.9_aiohttp-wsgi/build/aiohttp_wsgi
> copying aiohttp_wsgi/__main__.py ->
> /<>/.pybuild/cpython3_3.9_aiohttp-wsgi/build/aiohttp_wsgi
> copying aiohttp_wsgi/wsgi.py ->
> /<>/.pybuild/cpython3_3.9_aiohttp-wsgi/build/aiohttp_wsgi
> copying aiohttp_wsgi/utils.py ->
> /<>/.pybuild/cpython3_3.9_aiohttp-wsgi/build/aiohttp_wsgi
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:237: cd
> /<>/.pybuild/cpython3_3.10_aiohttp-wsgi/build; python3.10 -m
> unittest discover -v
> testEnviron (tests.test_environ.EnvironTest) ...
> /usr/lib/python3/dist-packages/aiohttp/connector.py:771: DeprecationWarning:
> The object should be created within an async function
> super().__init__(
> /usr/lib/python3/dist-packages/aiohttp/connector.py:782: DeprecationWarning:
> The object should be created within an async function
> resolver = DefaultResolver(loop=self._loop)
> /<>/.pybuild/cpython3_3.10_aiohttp-wsgi/build/tests/base.py:67:
> DeprecationWarning: The object should be created within an async function
> session = aiohttp.ClientSession(connector=connector, loop=loop)
> /usr/lib/python3/dist-packages/aiohttp/cookiejar.py:67: DeprecationWarning:
> The object should be created within an async function
> super().__init__(loop=loop)
> Error handling request
> Traceback (most recent call last):
> File "/usr/lib/python3/dist-packages/aiohttp/web_protocol.py", line 435, in
> _handle_request
> resp = await request_handler(request)
> File "/usr/lib/python3/dist-packages/aiohttp/web_app.py", line 504, in
> _handle
> resp = await handler(request)
> File
> "/<>/.pybuild/cpython3_3.10_aiohttp-wsgi/build/aiohttp_wsgi/wsgi.py",
> line 262, in handle_request
> status, reason, headers, body = await self._loop.run_in_executor(
> File "/usr/lib/python3.10/concurrent/futures/thread.py", line 58, in run
> result = self.fn(*self.args, **self.kwargs)
> File
> "/<>/.pybuild/cpython3_3.10_aiohttp-wsgi/build/aiohttp_wsgi/wsgi.py",
> line 127, in _run_application
> body_iterable = application(environ, start_response)
> File
> "/<>/.pybuild/cpython3_3.10_aiohttp-wsgi/build/tests/test_environ.py",
> line 11, in do_environ_application
> func(environ)
> File
> "/<>/.pybuild/cpython3_3.10_aiohttp-wsgi/build/tests/test_environ.py",
> line 21, in assert_environ
> assert environ["CONTENT_TYPE"] == ""
> AssertionError
> /usr/lib/python3/dist-packages/aiohttp/connector.py:91: DeprecationWarning:
> Connector.close() is a coroutine, please use await connector.close()
> warnings.warn(
>
Bug#1022472: closed by Debian FTP Masters (reply to Stefano Rivera ) (Bug#1022472: fixed in python-av 9.2.0-3.1)
Dear maintainer, The NMU that fixed that bug was not acknowledged in the next upload to unstable, so this bug still affects unstable (but not testing). Lucas
Bug#1026528: marked as done (roundcube: FTBFS: make[1]: *** [debian/rules:105: override_dh_auto_test] Error 1)
Your message dated Tue, 20 Dec 2022 19:52:59 + with message-id and subject line Bug#1026528: fixed in roundcube 1.6.0+dfsg-2 has caused the Debian Bug report #1026528, regarding roundcube: FTBFS: make[1]: *** [debian/rules:105: override_dh_auto_test] Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026528 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: roundcube Version: 1.6.0+dfsg-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > debian/rules:76: target 'skins/elastic/styles/styles.min.css.map' given more > than once in the same rule > debian/rules:76: target 'skins/elastic/styles/print.min.css.map' given more > than once in the same rule > debian/rules:76: target 'skins/elastic/styles/embed.min.css.map' given more > than once in the same rule > debian/rules:84: target 'program/js/publickey.min.js.gz' given more than once > in the same rule > debian/rules:84: target 'skins/elastic/styles/styles.min.css.gz' given more > than once in the same rule > debian/rules:84: target 'skins/elastic/styles/print.min.css.gz' given more > than once in the same rule > debian/rules:84: target 'skins/elastic/styles/embed.min.css.gz' given more > than once in the same rule > [ -d tests/.locale ] || mkdir tests/.locale > localedef -c -i en_US -f UTF-8 tests/.locale/en_US.utf8 > ln -sfT ../.github/config-test.inc.php config/config-test.inc.php > env RCUBE_INSTALL_PATH=/<> > LOCPATH=/<>/tests/.locale \ > phpunit -c tests/phpunit.xml --fail-on-skipped \ > --exclude-group flaky > PHPUnit 9.5.27 by Sebastian Bergmann and contributors. > > . 61 / 1025 ( > 5%) > . 122 / 1025 ( > 11%) > . 183 / 1025 ( > 17%) > ..II. 244 / 1025 ( > 23%) > . 305 / 1025 ( > 29%) > ...I. 366 / 1025 ( > 35%) > . 427 / 1025 ( > 41%) > . 488 / 1025 ( > 47%) > . 549 / 1025 ( > 53%) > .I..I..III... 610 / 1025 ( > 59%) > ...III..I...III..I...F..I 671 / 1025 ( > 65%) > .I.I.II..I..I..I.I.I...II...I..II 732 / 1025 ( > 71%) > I.I.I.I.II...II..II.II...I... 793 / 1025 ( > 77%) > ..I...I.. 854 / 1025 ( > 83%) > ...I..II......II. 915 / 1025 ( > 89%) > . 976 / 1025 ( > 95%) > . 1025 / 1025 > (100%) > > Time: 00:01.779, Memory: 36.00 MB > > There was 1 failure: > > 1) Rcmail_Rcmail::test_format_date > Failed asserting that two strings are identical. > --- Expected > +++ Actual > @@ @@ > -'6/1/20, 12:20 PM' > +'6/1/20, 12:20 PM' > > /<>/tests/Rcmail/Rcmail.php:270 > /usr/bin/phpunit:73 > > FAILURES! > Tests: 1025, Assertions: 2705, Failures: 1, Incomplete: 87. > make[1]: *** [debian/rules:105: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/12/20/roundcube_1.6.0+dfsg-1.1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=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 r
Processed: retitle 1026503 to ibembperl-perl: FTBFS: Expected 6 more error(s) in logfile, tagging 1026503
Processing commands for cont...@bugs.debian.org: > retitle 1026503 ibembperl-perl: FTBFS: Expected 6 more error(s) in logfile Bug #1026503 [src:libembperl-perl] libembperl-perl: FTBFS: cat: test/tmp/httpd.pid: No such file or directory Changed Bug title to 'ibembperl-perl: FTBFS: Expected 6 more error(s) in logfile' from 'libembperl-perl: FTBFS: cat: test/tmp/httpd.pid: No such file or directory'. > tags 1026503 + confirmed Bug #1026503 [src:libembperl-perl] ibembperl-perl: FTBFS: Expected 6 more error(s) in logfile Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026503 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026759: marked as done (spyder-kernels: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13)
Your message dated Tue, 20 Dec 2022 19:14:44 +
with message-id
and subject line Re: Bug#1026759: spyder-kernels: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit
code 13
has caused the Debian Bug report #1026759,
regarding spyder-kernels: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.11 3.10" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1026759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spyder-kernels
Version: 2.3.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
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:240: python3.11 setup.py config
> running config
> I: pybuild base:240: python3.10 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3.11 setup.py build
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels
> copying spyder_kernels/__init__.py ->
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels
> copying spyder_kernels/py3compat.py ->
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels
> copying spyder_kernels/_version.py ->
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels
> creating
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/__init__.py ->
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/spyderpdb.py ->
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/spydercustomize.py ->
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/umr.py ->
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/namespace_manager.py ->
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/utils.py ->
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/customize
> creating
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/__init__.py ->
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/lazymodules.py ->
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/mpl.py ->
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/nsview.py ->
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/dochelpers.py ->
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/iofuncs.py ->
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/test_utils.py ->
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/misc.py ->
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/utils
> creating
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/console
> copying spyder_kernels/console/__init__.py ->
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/console
> copying spyder_kernels/console/__main__.py ->
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/console
> copying spyder_kernels/console/shell.py ->
> /<>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/console
> copying spyder_kernels/console/kernel.py ->
> /<>/.pybuild/cpython3_3.11_spyder-k
Bug#1026753: libio-compress-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2
COntrol: tag -1 + confirmed On Tue, 20 Dec 2022 18:28:54 +0100, Lucas Nussbaum wrote: > Source: libio-compress-perl > Version: 2.201-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20221220 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > > # Failed test (t/cz-03zlib-v1.t at line 713) > > # got: 1 > > # expected: -3 > > # Looks like you failed 1 test of 471. > > t/cz-03zlib-v1.t > > 1..471 > > not ok 196 > > Test Summary Report > > --- > > t/cz-03zlib-v1.t (Wstat: 256 (exited 1) Tests: 471 Failed: 1) > > Failed test: 196 > > Non-zero exit status: 1 > > Files=93, Tests=25495, 39 wallclock secs ( 2.20 usr 0.22 sys + 17.58 cusr > > 2.44 csys = 22.44 CPU) > > Result: FAIL > > Failed 1/93 test programs. 1/25495 subtests failed. > > make[2]: *** [Makefile:957: test_dynamic] Error 255 > > make[2]: Leaving directory '/<>' > > dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2 I think this has to do with zlib1g-dev 1:1.2.13.dfsg-1 and libcompress-raw-zlib-perl and (a bit) https://github.com/pmqs/Compress-Raw-Zlib/issues/20 If I rebuild libcompress-raw-zlib-perl (against zlib 1.2.13) and then rebuild libio-compress-perl, its tests pass. PS: This also reminds me that #1024179 in libcompress-raw-zlib-perl is still not closed. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Processed: Re: Bug#1026753: libio-compress-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2
Processing control commands: > tag -1 + confirmed Bug #1026753 [src:libio-compress-perl] libio-compress-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2 Added tag(s) confirmed. -- 1026753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026753 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016332: librsb: FTBFS: gmake[3]: *** [Makefile:920: qtests] Error 1
Hi, On 07/12/22 at 08:19 +0100, Rafael Laboissière wrote: > @Lucas: if the rebuild goes fine, will this bug report be automatically > closed? Otherwise, is there a web page where the results can be tracked? Not automatically no. Rebuilds are mostly a manual process, with a bunch of helpers mainly to file bugs. Regarding old unreproducible failures, I do some clean up from time to time, so I will close the bug eventually. However the best strategy is for the maintainers to close the bug when they think it is fixed, and then I'll reopen or open another bug if I can still reproduce. Lucas
Bug#1026342: marked as done (scipy: autopkgtest needs update for new version of numpy: DeprecationWarning)
Your message dated Tue, 20 Dec 2022 19:10:18 +
with message-id
and subject line Bug#1026342: fixed in scipy 1.8.1-15
has caused the Debian Bug report #1026342,
regarding scipy: autopkgtest needs update for new version of numpy:
DeprecationWarning
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1026342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scipy
Version: 1.8.1-14
Severity: serious
X-Debbugs-CC: nu...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:numpy
Dear maintainer(s),
With a recent upload of numpy the autopkgtest of scipy fails in testing
when that autopkgtest is run with the binary packages of numpy from
unstable. It passes when run with only packages from testing. In tabular
form:
passfail
numpy from testing1:1.23.5-2
scipy from testing1.8.1-14
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of numpy to testing
[1]. Of course, numpy shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in numpy was
intended and your package needs to update to the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from numpy should really add a
versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=numpy
https://ci.debian.net/data/autopkgtest/testing/armel/s/scipy/29447608/log.gz
skipping tests with SKIP_TEST_LIST=
=== Testing: python3.10 ===
= test session starts
==
platform linux -- Python 3.10.9, pytest-7.1.2, pluggy-1.0.0+repack --
/usr/bin/python3.10
cachedir: .pytest_cache
rootdir: /tmp/autopkgtest-lxc.81kfm6nh/downtmp/build.dRh/src,
configfile: pytest.ini
collecting ... collected 49779 items / 1 error / 12514 deselected / 1
skipped / 37265 selected
ERRORS
__ ERROR collecting _build_utils/tests/test_scipy_version.py
___
/usr/lib/python3.10/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
level = 0
name = 'scipy._build_utils.tests.test_scipy_version'
package= None
:1050: in _gcd_import
???
level = 0
name = 'scipy._build_utils.tests.test_scipy_version'
package= None
:1027: in _find_and_load
???
import_=
module =
name = 'scipy._build_utils.tests.test_scipy_version'
:992: in _find_and_load_unlocked
???
import_=
name = 'scipy._build_utils.tests.test_scipy_version'
parent = 'scipy._build_utils.tests'
path = None
:241: in _call_with_frames_removed
???
args = ('scipy._build_utils.tests',)
f =
kwds = {}
:1050: in _gcd_import
???
level = 0
name = 'scipy._build_utils.tests'
package= None
:1027: in _find_and_load
???
import_=
module =
name = 'scipy._build_utils.tests'
:992: in _find_and_load_unlocked
???
import_=
name = 'scipy._build_utils.tests'
parent = 'scipy._build_utils'
path = None
:241: in _call_with_frames_removed
???
args = ('scipy._build_utils',)
f =
kwds = {}
:1050: in _gcd_import
???
level = 0
name = 'scipy._build_utils'
package= None
:1027: in _find_and_load
???
import_=
module =
name = 'scipy._build_utils'
:1006: in _find_and_load_unlocked
???
import_=
name = 'scipy._build_utils'
parent = 'scipy'
parent_module = '/usr/lib/python3/dist-packages/scipy/__init__.py'>
Bug#1026210: marked as done (scipy: autopkgtest regression due to invalid test function returns)
Your message dated Tue, 20 Dec 2022 19:10:18 + with message-id and subject line Bug#1026210: fixed in scipy 1.8.1-15 has caused the Debian Bug report #1026210, regarding scipy: autopkgtest regression due to invalid test function returns to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: scipy Version: 1.8.1-14 Severity: serious Control: affects -1 src:pytest -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainers, the autopkgtest of your package started failing because some of the tests return values. This has always been incorrect (tests are expected to assert, not return anything), but recently, pytest 7.2 started issuing warnings [1], which are turned into hard errors by your pytest.ini filterwarnings directive. Cheers Timo [1] https://docs.pytest.org/en/7.2.x/deprecations.html#returning-non-none-value-in-test-functions -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmOcTDIACgkQ+C8H+466 LVl98AwAk1Wnpwkl+NU8uNXM8gtiP4YLQ7ncEZFaCOrbrjQEHY/JMgHy6s3mEFvg EndEr2mXNk5BsID1kLmXX+nz9hqhAoA1R7admtzFJNd8wNZC2yZNSegQffT6yRM5 WoCxaoK89quDomxhVRAHzIHUxmXJXHHhkjymNKOL9iULkexWMTOyrXSIiTrdqskL 7skF/Ak+GtdT4oswn675fEvWeAAgxexcjRyxO9UQ6Jt7vq7D+GP0PIC+tKsXv5Iw FK0RUuNLpOPTAqlECkFlE6/ekupD5MNWFIYrqhn0iCl656Dclgxa8UeXfO0kt0ot o/m7+aMkDvMCq+N702jKCIHKjBNxcZA/YMMUtQ1hGr7sO+O7G3rKvozdhoq1HjnI 88uqk5fJf5TYsRS7to5Atv+nMLWNMN5AE/QlOLGzVNJoBKaSds0yQ+P4H41gR8hZ QfqaPExVr0V1o/3kOqwrFLDUuU8kVzDvY41d9vWoMr6W1m29fYf4J+aO/SpaOlbV yWH373Hn =A9xu -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: scipy Source-Version: 1.8.1-15 Done: Jochen Sprickerhof We believe that the bug you reported is fixed in the latest version of scipy, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jochen Sprickerhof (supplier of updated scipy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 20 Dec 2022 19:47:35 +0100 Source: scipy Architecture: source Version: 1.8.1-15 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Jochen Sprickerhof Closes: 1025699 1026210 1026342 1026516 Changes: scipy (1.8.1-15) unstable; urgency=medium . * Team upload. * Fix FTBFS with new numpy (deprecated numpy.distutils) (Closes: #1026210, #1026342, #1026516) * Add workaround for FTBFS with new sphinx * Ignore test failure on armel (Closes: #1025699) Checksums-Sha1: 5e52400fe2575ef7dd75b74c99618f054d8ea6dd 2789 scipy_1.8.1-15.dsc 255b3f6bc3ea9723ec60a50eb3ae9f855d032a5b 30020 scipy_1.8.1-15.debian.tar.xz dd9b2f4aaf73cd9bf66ed6ddb801264a0dd3cc1f 10257 scipy_1.8.1-15_source.buildinfo Checksums-Sha256: 9e8df054e70d02279c88317cf1d0d4761d9fa80669f34723cf7033f32a5b0849 2789 scipy_1.8.1-15.dsc cac4694005e75cdb014cf53ab95369a8b6f9a0de64e2e5bbb55974edb5efefcf 30020 scipy_1.8.1-15.debian.tar.xz ce69e98f9d42dedde2905193747557b49f7d170bc04a67737fc22a2677dc57e1 10257 scipy_1.8.1-15_source.buildinfo Files: 59552a29d910949028bf280838d7884e 2789 python optional scipy_1.8.1-15.dsc 591043c85d9a856592103d6d8b0bbf7f 30020 python optional scipy_1.8.1-15.debian.tar.xz 9cbe1806200f5ea099b7d5c59e904319 10257 python optional scipy_1.8.1-15_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmOiBDkACgkQW//cwljm lDM/iw//bWD/zDOOGqDUy8kHf724kYk2EqEuUZNW3AWsPMpCmLNqDNoGDLiesuz6 ThiDBu+DJ8dOOafCUlnGB8FLxScbSo5oxHdRHrLkntHVghEl8D8qf4MWKphGeD4B CKcLGa3Wtb7/CikmgxB5zFGjFr0O6G15UeJkweIeRZeTqquZBWqfs9zF1krdiPqD wzhVK5y4xeirwauT4BdTVlNYm1DYGEbKiyf6sjzfGz8KDCZR/IPavd9d9U0IdlMW 2qgFSNJU3FnPlcIhgGuNWnxXd8ajNmUflYVwF9E9rzSTfVjfWxvRVgMnwxJ5bBx2 rvYdvJ2AMB1JZ2LRUBk4Cs9KtA8Ue/tlsy2uGQCJQ2yrFs4eTVkwiDKQ/dayw8zB TQvs7P1s+rZ62dRKqnn928vCQunsrzajfLQ6UCIRdy05e9MepbofV+FVPWoWrR4j 5AFM3lXm4ZZdNlBuHciudNzvZSlDwNjGT8eaeuBHbVWANC0JVq1Q91LFxHpLH8KJ oyAErPqt6eqcP5XVcG01WW2SgGgl+kePDY8xouHx8lEyaDeNlN+jsvkxR/ZxADnQ
Bug#1025699: marked as done (autopkgtest fails on armel against atlas 3.10.3-13)
Your message dated Tue, 20 Dec 2022 19:10:18 + with message-id and subject line Bug#1025699: fixed in scipy 1.8.1-15 has caused the Debian Bug report #1025699, regarding autopkgtest fails on armel against atlas 3.10.3-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1025699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025699 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: scipy Version: 1.8.1-14 Severity: serious Control: affects -1 atlas Dear Maintainer, Since the upload of atlas 3.10.3-13 to unstable, the autopkgtest of scipy fails on armel. See: https://ci.debian.net/data/autopkgtest/testing/armel/s/scipy/29064436/log.gz More precisely, a test in sparse/linalg/_eigen/tests/test_svds.py fails because the error is now slightly above tolerance. Simply increasing the tolerance should fix the problem. Note that the only numerically significant change in 3.10.3-13 was the rebuild against lapack 3.11, hence the latter is probably the real cause of the problem (though it may also be a change in the toolchain). In particular, note that this issue transitively prevents lapack 3.11 from migrating to testing/bookworm. Incidentally, you should be aware that atlas has not seen a stable major upstream since 2016; it has also been superseded by better alternatives like OpenBLAS and BLIS; I’m therefore considering its possible removal during the trixie development cycle. Thanks for your work, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org --- End Message --- --- Begin Message --- Source: scipy Source-Version: 1.8.1-15 Done: Jochen Sprickerhof We believe that the bug you reported is fixed in the latest version of scipy, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jochen Sprickerhof (supplier of updated scipy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 20 Dec 2022 19:47:35 +0100 Source: scipy Architecture: source Version: 1.8.1-15 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Jochen Sprickerhof Closes: 1025699 1026210 1026342 1026516 Changes: scipy (1.8.1-15) unstable; urgency=medium . * Team upload. * Fix FTBFS with new numpy (deprecated numpy.distutils) (Closes: #1026210, #1026342, #1026516) * Add workaround for FTBFS with new sphinx * Ignore test failure on armel (Closes: #1025699) Checksums-Sha1: 5e52400fe2575ef7dd75b74c99618f054d8ea6dd 2789 scipy_1.8.1-15.dsc 255b3f6bc3ea9723ec60a50eb3ae9f855d032a5b 30020 scipy_1.8.1-15.debian.tar.xz dd9b2f4aaf73cd9bf66ed6ddb801264a0dd3cc1f 10257 scipy_1.8.1-15_source.buildinfo Checksums-Sha256: 9e8df054e70d02279c88317cf1d0d4761d9fa80669f34723cf7033f32a5b0849 2789 scipy_1.8.1-15.dsc cac4694005e75cdb014cf53ab95369a8b6f9a0de64e2e5bbb55974edb5efefcf 30020 scipy_1.8.1-15.debian.tar.xz ce69e98f9d42dedde2905193747557b49f7d170bc04a67737fc22a2677dc57e1 10257 scipy_1.8.1-15_source.buildinfo Files: 59552a29d910949028bf280838d7884e 2789 python optional scipy_1.8.1-15.dsc 591043c85d9a856592103d6d8b0bbf7f 30020 python optional scipy_1.8.1-15.debian.tar.xz 9cbe1806200f5ea099b7d5c59e904319 10257 python optional scipy_1.8.1-15_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmOiBDkACgkQW//cwljm lDM/iw//bWD/zDOOGqDUy8kHf724kYk2EqEuUZNW3AWsPMpCmLNqDNoGDLiesuz6 ThiDBu+DJ8dOOafCUlnGB8FLxScbSo5oxHdRHrLkntHVghEl8D8qf4MWKphGeD4B CKcLGa3Wtb7/CikmgxB5zFGjFr0O6G15UeJkweIeRZeTqquZBWqfs9zF1krdiPqD wzhVK5y4xeirwauT4BdTVlNYm1DYGEbKiyf6sjzfGz8KDCZR/IPavd9d9U0IdlMW 2qgFSNJU3FnPlcIhgGuNWnxXd8ajNmUflYVwF9E9rzSTfVjfWxvRVgMnwxJ5bBx2 rvYdvJ2AMB1JZ2LRUBk4Cs9KtA8Ue/tlsy2uGQCJQ2yrFs4eTVkwiDKQ/dayw8zB TQvs7P1s+rZ62dRKqnn928vCQunsrzajfLQ6UCIRdy05e9MepbofV+FVPWoWrR4j 5AFM3lXm4ZZdNlBuHciudNzvZSlDwNjGT8eaeuBHbVWANC0JVq1Q91LFxHpLH8KJ oyAErPqt6eqcP5XVcG01WW2SgGgl+kePDY8xouHx8lEyaDeNlN+jsvkxR/ZxADnQ Qdda7NaIro5T7Xspt3RKJwj4ann+PSag6GJYAYLrAeogPEPP7sEr9fTelCECq4JW AJ26Ua/In65FXBbmbXfuEcesMpMs3NloC0PJGv0fmfgsA4I/QWg= =+k5c
Bug#1026312: Setuptools 65.5.0-1.1 breaks installing Python modules/extensions via meson
Hi Simon (2022.12.20_18:59:12_+) > This appears to be a behaviour change in the build system, and I think it's > triggered by the new setuptools. It is. The Debian detection in meson doesn't support the newer distutils that dynamically sources available schema from the sysconfig module. I'm working on a patch for meson. The latest setuptools upload made setuptools-bundled distutils override the system distutils, when installed. Triggering this bug report. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#1026744: marked as done (libcgi-application-plugin-captcha-perl: FTBFS: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit code 255)
Your message dated Tue, 20 Dec 2022 19:04:48 + with message-id and subject line Bug#1026744: fixed in libcgi-application-plugin-captcha-perl 0.04-4 has caused the Debian Bug report #1026744, regarding libcgi-application-plugin-captcha-perl: FTBFS: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit code 255 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libcgi-application-plugin-captcha-perl Version: 0.04-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build >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 -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config > "ld=x86_64-linux-gnu-gcc -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro" > Created MYMETA.yml and MYMETA.json > Creating new 'Build' script for 'CGI-Application-Plugin-CAPTCHA' version > '0.04' >dh_auto_build > /usr/bin/perl Build > Building CGI-Application-Plugin-CAPTCHA >dh_auto_test > /usr/bin/perl Build test --verbose 1 > # Testing CGI::Application::Plugin::CAPTCHA 0.04, Perl 5.036000, /usr/bin/perl > t/00-load.t ... > 1..1 > ok 1 - use CGI::Application::Plugin::CAPTCHA; > ok > t/01-config.t . > 1..7 > ok 1 - IMAGE_OPTIONS defined > ok 2 - CREATE_OPTIONS defined > ok 3 - PARTICLE_OPTIONS defined > ok 4 - IMAGE_OPTIONS should be a hashref > ok 5 - CREATE_OPTIONS should be an arrayref > ok 6 - PARTICLE_OPTIONS should be an arrayref > ok 7 - CAP::CAPTCHA died when given invalid options > ok > Base class package "HTTP::Server::Simple::CGI" is empty. > (Perhaps you need to 'use' the module which defines that package first, > or make that module available in @INC (@INC contains: ./t > /<>/blib/lib /<>/blib/arch /etc/perl > /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 > /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 > /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 > /usr/share/perl/5.36 /usr/local/lib/site_perl). > at t/CAPCServer.pm line 6. > BEGIN failed--compilation aborted at t/CAPCServer.pm line 6. > Compilation failed in require at t/02-create.t line 22. > BEGIN failed--compilation aborted at t/02-create.t line 22. > t/02-create.t . > Dubious, test returned 2 (wstat 512, 0x200) > No subtests run > Base class package "HTTP::Server::Simple::CGI" is empty. > (Perhaps you need to 'use' the module which defines that package first, > or make that module available in @INC (@INC contains: ./t > /<>/blib/lib /<>/blib/arch /etc/perl > /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 > /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 > /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 > /usr/share/perl/5.36 /usr/local/lib/site_perl). > at t/CAPCServer.pm line 6. > BEGIN failed--compilation aborted at t/CAPCServer.pm line 6. > Compilation failed in require at t/03-verify.t line 22. > BEGIN failed--compilation aborted at t/03-verify.t line 22. > t/03-verify.t . > Dubious, test returned 2 (wstat 512, 0x200) > No subtests run > t/pod-coverage.t .. > 1..1 > ok 1 - Pod coverage on CGI::Application::Plugin::CAPTCHA > ok > t/pod.t ... > 1..1 > ok 1 - POD test for blib/lib/CGI/Application/Plugin/CAPTCHA.pm > ok > > Test Summary Report > --- > t/02-create.t (Wstat: 512 (exited 2) Tests: 0 Failed: 0) > Non-zero exit status: 2 > Parse errors: No plan found in TAP output > t/03-verify.t (Wstat: 512 (exited 2) Tests: 0 Failed: 0) > Non-zero exit status: 2 > Parse errors: No plan found in TAP output > Files=6, Tests=10, 1 wallclock secs ( 0.03 usr 0.00 sys + 0.66 cusr 0.11 > csys = 0.80 CPU) > Result: FAIL &
Bug#1026760: libhttp-daemon-ssl-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2
Control: tag -1 + confirmed upstream On Tue, 20 Dec 2022 18:28:48 +0100, Lucas Nussbaum wrote: > Source: libhttp-daemon-ssl-perl > Version: 1.05-01-3 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20221220 ftbfs-bookworm > > > t/testmodule.t .. > > 1..14 > > ok #authority certificate generated 1 > > ok #server certificate generated 2 > > ok #authority certificate saved 3 > > ok #server certificate saved 4 > > ok #server key saved 5 > > ok #server init port=37009 6 > > ok #server fileno 7 > > ok #server url test 8 > > ok #bad request handled 9 > > ok #client bad connection test 7 > > not ok #client failure > > not ok 9 # valid request did not return a socket > > Dubious, test returned 255 (wstat 65280, 0xff00) > > Failed 4/14 subtests I believe this is fallout from the upgrade of libio-socket-ssl-perl from 2.077-1 to 2.078-1 (the tests pass in testing). libio-socket-ssl-perl's upstream changelog says 2.078 2022/12/11 - revert decision from 2014 to not verify hostname by default if hostname is IP address but no explicit verification scheme given https://github.com/noxxi/p5-io-socket-ssl/issues/121 So I guess we need to do something about the created certs for this test … Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Processed: Re: Bug#1026312: Setuptools 65.5.0-1.1 breaks installing Python modules/extensions via meson
Processing control commands: > severity -1 serious Bug #1026312 [src:setuptools] Setuptools 65.5.0-1.1 breaks installing Python modules/extensions via meson Severity set to 'serious' from 'important' > block 1026526 by -1 Bug #1026526 [src:dbus-python] dbus-python: FTBFS: mv: cannot move 'debian/tmp/usr/libexec/installed-tests/dbus-python/python3.11/test/dbus_py_test.cpython-311-x86_64-linux-gnu.so' to 'debian/tmp/usr/lib/python3/dist-packages/': No such file or directory 1026526 was not blocked by any bugs. 1026526 was not blocking any bugs. Added blocking bug(s) of 1026526: 1026312 > block 1026751 by -1 Bug #1026751 [src:gi-docgen] gi-docgen: FTBFS: dh_install: error: missing files, aborting 1026751 was not blocked by any bugs. 1026751 was not blocking any bugs. Added blocking bug(s) of 1026751: 1026312 > block 1026732 by -1 Bug #1026732 [src:libgit2-glib] libgit2-glib: FTBFS: dh_install: error: missing files, aborting 1026732 was not blocked by any bugs. 1026732 was not blocking any bugs. Added blocking bug(s) of 1026732: 1026312 > affects -1 + meson python3-distutils src:dbus-python src:libgit2-glib > src:gi-docgen Bug #1026312 [src:setuptools] Setuptools 65.5.0-1.1 breaks installing Python modules/extensions via meson Added indication that 1026312 affects meson, python3-distutils, src:dbus-python, src:libgit2-glib, and src:gi-docgen -- 1026312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026312 1026526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026526 1026732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026732 1026751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1026760: libhttp-daemon-ssl-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2
Processing control commands: > tag -1 + confirmed upstream Bug #1026760 [src:libhttp-daemon-ssl-perl] libhttp-daemon-ssl-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2 Added tag(s) confirmed and upstream. -- 1026760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026760 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026581: marked as done (natbraille: FTBFS: nat/convertisseur/Convertisseur2ODT.java:46: error: end tag missing: )
Your message dated Tue, 20 Dec 2022 18:50:21 +
with message-id
and subject line Bug#1026581: fixed in natbraille 2.0rc3-14
has caused the Debian Bug report #1026581,
regarding natbraille: FTBFS: nat/convertisseur/Convertisseur2ODT.java:46:
error: end tag missing:
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1026581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: natbraille
Version: 2.0rc3-13
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> javac -source 1.7 -target 1.7 -encoding utf8 -classpath
> /usr/share/java/commons-io.jar:/usr/share/java/fop.jar:/usr/share/java/xalan2.jar:/usr/share/java/jaxe.jar:/usr/share/java/jazzy.jar:/usr/share/java/jhall.jar:/usr/share/java/jing.jar:/usr/share/java/jodconverter.jar:/usr/share/java/joptsimple.jar:/usr/share/java/juh.jar:/usr/share/java/jurt.jar:/usr/share/java/log4j-1.2.jar:/usr/share/java/ridl.jar:/usr/share/java/saxonb.jar:/usr/share/java/saxon-dom.jar/usr/share/java/slf4j-api.jar:/usr/share/java/slf4j-jdk14.jar:/usr/lib/libreoffice/program/classes/unoil.jar:/usr/share/java/xstream.jar:/usr/share/java/writer2latex.jar:/usr/share/java/jeuclid-core.jar
> `find gestionnaires nat outils ui org -name \*.java`
> warning: [options] bootstrap class path not set in conjunction with -source 7
> warning: [options] source value 7 is obsolete and will be removed in a future
> release
> warning: [options] target value 7 is obsolete and will be removed in a future
> release
> warning: [options] To suppress warnings about obsolete options, use
> -Xlint:-options.
> ui/FenetrePrinc.java:38: warning: [removal] Applet in java.applet has been
> deprecated and marked for removal
> import java.applet.Applet;
> ^
> ui/FenetrePrinc.java:39: warning: [removal] AudioClip in java.applet has been
> deprecated and marked for removal
> import java.applet.AudioClip;
> ^
> ui/FenetrePrinc.java:284: warning: [removal] Integer(int) in Integer has been
> deprecated and marked for removal
> UIManager.put("FileChooser.lookInLabelMnemonic", new
> Integer(KeyEvent.VK_R));
>^
> ui/FenetrePrinc.java:1338: warning: [removal] AudioClip in java.applet has
> been deprecated and marked for removal
> AudioClip ac;
> ^
> ui/FenetrePrinc.java:1343: warning: [removal] Applet in java.applet has been
> deprecated and marked for removal
> ac = Applet.newAudioClip(new URL("file:"+
> curDir.getAbsolutePath()+"/ui/sounds/tic.au"));
>^
> ui/FenetrePrinc.java:1358: warning: [removal] Applet in java.applet has been
> deprecated and marked for removal
> ac = Applet.newAudioClip(new
> URL("file:"+ curDir.getAbsolutePath()+"/ui/sounds/fin.au"));
>^
> ui/FenetrePrinc.java:1362: warning: [removal] Applet in java.applet has been
> deprecated and marked for removal
> ac = Applet.newAudioClip(new
> URL("file:"+ curDir.getAbsolutePath()+"/ui/sounds/erreur.au"));
>^
> nat/ConfigNat.java:201: warning: [removal] Boolean(String) in Boolean has
> been deprecated and marked for removal
> public boolean getUpdateCheck(){ return new
> Boolean(fiConf.getProperty(OptNames.ge_check_update,"true")).booleanValue();}
> ^
> nat/ConfigNat.java:239: warning: [removal] Integer(int) in Integer has been
> deprecated and marked for removal
> public void setNiveauLog(int
> lg){fiConf.setProperty(OptNames.ge_log_verbosity, (new
> Integer(lg)).toString());}
>
> ^
> nat/ConfigNat.java:247: warning: [removal] Integer(int) in Integer has been
> deprecated and marked for removal
> fiConf.setProperty(OptNames.ge_log_verbosity, (new
> Integer(lg))
Bug#1026744: marked as pending in libcgi-application-plugin-captcha-perl
Control: tag -1 pending Hello, Bug #1026744 in libcgi-application-plugin-captcha-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libcgi-application-plugin-captcha-perl/-/commit/42c9aa346e4be4448a3fc62e2e895ba1b2f0e6c2 Add test dependency on libhttp-server-simple-perl. Thanks: Lucas Nussbaum for the bug report. Closes: #1026744 (this message was generated automatically) -- Greetings https://bugs.debian.org/1026744
