Bug#947063: ITP: pass-import -- Pass extension for importing ata from existing password managers
Control: retitle -1 ITP: pass-import -- Pass extension for importing ata from existing password managers Dear Hans-Christoph, Hans-Christoph Steiner wrote in December 2019: > * Package name: pass-import > Version : 2.6 > Upstream Author : Alexandre Pujol > * URL : https://github.com/roddhjav/pass-import > * License : GPLv3 > Programming Lang: Python > Package source : > https://salsa.debian.org/alexander.tolios-guest/pass-import > Description: > Pass extension for importing data from existing password managers Any news on this? The Salsa repository seems to be a bit behind upstream with regards to upstream releases: The packaging is still at 2.6 (released June 2019) while upstream is at 3.2, released half a year ago in May 2021. I think seeing this tool in Debian would be a real benefit as the pass eco-system seems to really gain in importance and popularity. P.S.: I allowed myself to fix the ITP title as Kunal Mehta already suggested. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#997530:
Hi Lucas, Thanks for reporting! I've investigated this and found that the error comes from building against a version of the package "cv_bridge" (libcv-bridge-dev) which wasn't yet rebuilt against the latest opencv 4.5.4, but for the older 4.5.3. Does this still qualify as a FTBFS error in mrpt? "libcv-bridge-dev" is already listed in d/control... (?). Best, JL
Bug#997673: Audio: brasero.cue:5: String too long
Package: brasero Version: 3.12.2-6 Severity: important Dear Maintainer, I cannot use brasero easily to burn an AUDIO cd. When converting mp3 to cue and then burning cue project, brasero get stuck in an infinite loop and eventually task get killed for inactivity. Upon inspection it seems the CUE file generated by brasero cannot be consumed by brasero in my setup. Using command line tool reveal the following error: % cdrdao simulate --device ATA:0,0,0 --driver generic-mmc --speed 16 brasero.cue Cdrdao version 1.2.4 - (C) Andreas Mueller brasero.cue:1: Warning, big endian binary file brasero.cue:5: String too long After editing the CUE text file and simplify the 'PERFORMER' line, I can finally burn the CUE project to blank CDROM. --- It would be nice: 1. Brasero should not write too long line for 'PERFORMER' since it seems to be a portability issue. 2. Brasero should report an issue (eg. message box) saying that the CUE file cannot be consumed, instead of stopping in an infinite loop. -- System Information: Debian Release: 11.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages brasero depends on: ii brasero-common 3.12.2-6 ii gstreamer1.0-plugins-base 1.18.4-2 ii gvfs1.46.2-1 ii libbrasero-media3-1 3.12.2-6 ii libc6 2.31-13+deb11u2 ii libcairo2 1.16.0-5 ii libgdk-pixbuf2.0-0 2.40.2-2 ii libglib2.0-02.66.8-1 ii libgstreamer-plugins-base1.0-0 1.18.4-2 ii libgstreamer1.0-0 1.18.4-2.1 ii libgtk-3-0 3.24.24-4 ii libpango-1.0-0 1.46.2-3 ii libtotem-plparser18 3.26.5-5 ii libtracker-sparql-2.0-0 2.3.6-2 ii libxml2 2.9.10+dfsg-6.7 Versions of packages brasero recommends: ii brasero-cdrkit 3.12.2-6 ii nautilus-extension-brasero 3.12.2-6 ii yelp3.38.3-1 Versions of packages brasero suggests: ii libdvd-pkg [libdvdcss2] 1.4.2-1-1 ii libdvdcss2 1.4.2-1~local ii tracker 2.3.6-2 ii vcdimager2.0.1+dfsg-5 -- no debconf information
Bug#997270: ovn: FTBFS: | ./conftest.c:48: undefined reference to `pow'
Hi, On 24/10/21 at 00:23 +0200, Thomas Goirand wrote: > Hi Lucas, > > I wasn't able to reproduce the FTBFS. If you look a bit more closely, > the error is *NOT* "./conftest.c:48: undefined reference to `pow'" which > is in fact just a warning of the configure script. The error is an test > failure (which can be seen at the top of what's above). > > Both OVN and openvswitch are running timing sensitive tests, which may > fail in some environment (for example, if you build on an already busy > machine). So I wouldn't be surprised if this was due to your build > environment. > > I'm closing this bug, but of course, let me know if you think this is > wrong (in which case we can try to find out together what's going on). When a package fails, I re-build it on an otherwise idle machine. So it might be time-sensitive by itself (without external load). I'd prefer if you downgrade/retitle the bug so that this is tracked. If it fails randomly and you close it, I'll open another bug during a subsequent rebuild. Lucas
Bug#996960: scipy: FTBFS in unstable
Hi Sandro On Sat, 23 Oct 2021 at 17:35, Sandro Tosi wrote: > pydata-sphinx-theme 0.7.1 (which contains that fix) has just been > uploaded to unstable Great, thanks! I see you temporarily disabled building the docs. Would it be possible to temporarily drop the Build-Depends on python3-jupyter-sphinx as well? I think that may unblock things. Regards Graham
Bug#995053: dh_assistant command for listing installed files
On Sat, 25 Sep 2021 22:09:53 +0200 Niels Thykier wrote: > Control: tags -1 moreinfo > > Jelmer Vernooij: > > Package: debhelper > > Version: 13.5.2 > > Severity: wishlist > > > > Dear debhelper maintainers, > > > > For lintian-brush, it would be really useful if it was possible to discover > > which patterns it would be installing, why and where. > > > > I have no idea how hard this would be to implement, and whether this > > information is readily available in debhelper - but figured it's at least > > worth > > starting the discussion and seeing where it goes. I suspect there are some > > corner cases where it's impossible to discover like where dh-exec is in use > > (but even some information would be great). > > > > I imagine something like a "dh_assistant installed-files" that then reports: > > > > [...] > > I can definitely see how that would be interesting to you. > Unfortunately, debhelper is a bunch of "black box" tools that knows > nothing about each other. Even figuring out which dh_tools will be run > is non-trivial (but I might be able to do that). > > The best I can offer is a "post build" list of which tools installed > what where. But I am pretty sure that would not be helpful to your case > (because that would be "did install" and not "would install"). > > Even if I did find a solution, it would rely on each tool "helping out" > somehow. In other words, the solution would be incomplete or "unsafe" > with third party tools involved (or both). > > > Can you describe the use cases where you see the use for this? Maybe we > can meet somewhere in the middle for them. > > ~Niels > > Hi Jelmer, I am still waiting/hoping for your feedback on this. :) I would like to know what problem you want to solve using this data. :) If we are going forward with this that information would be necessary to understand what to do with: 1) debhelper supported substitutions (should the be expanded or not) - If they are to be expanded, then when do we do when we cannot expand them? 2) globs - currently debhelper is strict on expanding globs. The provided example output implies it should *not* be expanded. 3) search path - debhelper cannot know where in the search path a file is found unless the file is present (e.g., d/tmp is only available after dh_auto_install). 4) executable config files. This involves third-party tooling and is completely out of control for debhelper for how they will behave. 5) do you want tools like dh_link to provide data? It does not "install" any upstream provided file but it can generate links. I am still not sure to what extend debhelper can help with/provide this data in its current form. However, I would still like to know the problem better so I can look into supporting it in the future. Thanks, ~Niels
Bug#997674: allure: don't start with erorr Allure: SDLCallFailed (seem the problem is freetype 2.11)
Package: allure
Version: 0.9.5.0-2+b1
Severity: normal
X-Debbugs-Cc: davide.pr...@gmail.com
Dear Maintainer,
$ Allure
Allure: SDLCallFailed {sdlExceptionCaller = "SDL.Font.shadedGlyph", sdlFunction
= "TTF_RenderGlyph_Solid", sdlExceptionError = "Couldn't find glyph"}
it seem that the problem is freetype 2.11, see:
https://github.com/libsdl-org/SDL_ttf/issues/119
I found a workaround to start the game with:
$ Allure --sdlFontFile "Fix15Mono-Bold.woff"
Ciao
Davide
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-proposed-updates-debug'), (500,
'testing-debug'), (500, 'stable-security')
Architecture: amd64 (x86_64)
Kernel: Linux 5.14.9-dp-20211009 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages allure depends on:
ii libc6 2.32-4
ii libffi83.4.2-3
ii libgmp10 2:6.2.1+dfsg-2
ii libsdl2-2.0-0 2.0.16+dfsg1-5
ii libsdl2-ttf-2.0-0 2.0.15+dfsg1-1
ii zlib1g 1:1.2.11.dfsg-2
allure recommends no packages.
allure suggests no packages.
-- no debconf information
Bug#997675: gnome-software: wrong license for allure game
Package: gnome-software Version: 41.0-1 Severity: normal X-Debbugs-Cc: davide.pr...@gmail.com Dear Maintainer, in gnome-software the allure license is Proprietary code and marked as unsafe, but this software is AGPL 3.0 and present in Debian main Ciao Davide -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-proposed-updates-debug'), (500, 'testing-debug'), (500, 'stable-security') Architecture: amd64 (x86_64) Kernel: Linux 5.14.9-dp-20211009 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-software depends on: ii appstream0.14.6-1 ii apt-config-icons 0.14.6-1 ii dconf-gsettings-backend [gsettings-backend] 0.40.0-2 ii gnome-software-common41.0-1 ii gsettings-desktop-schemas41.0-1 ii libappstream40.14.6-1 ii libatk1.0-0 2.36.0-2 ii libc62.32-4 ii libcairo21.16.0-5 ii libfwupd21.5.7-5 ii libgdk-pixbuf-2.0-0 2.42.6+dfsg-2 ii libglib2.0-0 2.70.0-1+b1 ii libgspell-1-21.9.1-2 ii libgtk-3-0 3.24.30-3 ii libgtk3-perl 0.038-1 ii libgudev-1.0-0 237-2 ii libhandy-1-0 1.4.0-1 ii libjson-glib-1.0-0 1.6.6-1 ii libmalcontent-0-00.10.1-1 ii libpackagekit-glib2-18 1.2.2-2 ii libpango-1.0-0 1.48.10+ds1-1 ii libpolkit-gobject-1-00.105-31 ii libsoup2.4-1 2.74.0-2 ii libxmlb2 0.3.2-1 ii packagekit 1.2.2-2 ii software-properties-gtk 0.96.20.2-2.1 Versions of packages gnome-software recommends: pn fwupd Versions of packages gnome-software suggests: pn apt-config-icons-hidpi pn gnome-software-plugin-flatpak pn gnome-software-plugin-snap -- no debconf information
Bug#997676: rust-rusty-tags: FTBFS because of a recent upload
Source: rust-rusty-tags Severity: important Dear Maintainer, This package currently FTBFS with: (I)Dose_applications: --checkonly specified, consider all packages as background packages (I)Dose_applications: Solving... output-version: 1.2 native-architecture: amd64 report: - package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 status: broken reasons: - missing: pkg: package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 unsat-dependency: librust-semver-0.9+default-dev:amd64 Cheers, Sylvestre
Bug#997138: ffdiaporama: FTBFS: engine/_EncodeVideo.cpp:134:46: error: ‘AVStream’ {aka ‘struct AVStream’} has no member named ‘probe_data’; did you mean ‘priv_data’?
On 2021-10-23 20:34:40 +0200, Lucas Nussbaum wrote: > Source: ffdiaporama > Version: 2.1+dfsg-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > In file included from > > /usr/include/x86_64-linux-gnu/libavformat/avformat.h:312, > > from > > /usr/include/x86_64-linux-gnu/libavdevice/avdevice.h:51, > > from engine/cDeviceModelDef.h:47, > > from engine/cApplicationConfig.h:42, > > from engine/_Transition.h:80, > > from engine/_Diaporama.h:26, > > from engine/_EncodeVideo.h:28, > > from engine/_EncodeVideo.cpp:21: > > /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:1764:35: note: declared > > here > > 1764 | attribute_deprecated AVFrame *coded_frame; > > | ^~~ > > make[2]: *** [Makefile:4376: _EncodeVideo.o] Error 1 Unless somebody wants to take care of ffdiaporama, I think it's time to remove it from unstable. Upstream development has ceased 7 years ago. Cheers > > > The full build log is available from: > http://qa-logs.debian.net/2021/10/23/ffdiaporama_2.1+dfsg-1_unstable.log > > 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. > -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#997677: v4l-utils: FTBFS on riscv64 due to missing build-depends on clang:native
Package: v4l-utils Version: 1.22.1-1 Severity: important Tags: ftbfs patch User: debian-ri...@lists.debian.org Usertags: riscv64 Dear maintainer, Since version 1.22.1-1, v4l-utils fails to build on riscv64: | v4l2-compliance uses libv4l: yes | v4l2-compliance-32 : no | BPF IR Decoders: : no | make[1]: Leaving directory '/<>' |debian/rules override_dh_auto_build ... | dh_install | dh_install: warning: Cannot find (any matches for) "lib/systemd/system/systemd-udevd.service.d/50-rc_keymap.conf" (tried in ., debian/tmp) | | dh_install: warning: ir-keytable missing files: lib/systemd/system/systemd-udevd.service.d/50-rc_keymap.conf | dh_install: error: missing files, aborting | make[1]: *** [debian/rules:27: override_dh_install] Error 25 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:12: binary-arch] Error 2 | dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 The full build log is available there: https://buildd.debian.org/status/fetch.php?pkg=v4l-utils&arch=riscv64&ver=1.22.1-1&stamp=1635009273&raw=0 The missing file reported by dh_install is lacking as the "BPF IR Decoders" are not enabled, because clang is not available in the build-depends on riscv64, contrary to many other architectures. Therefore the fix is as simple as adding riscv64 to the clang:native build-depends: --- v4l-utils-1.22.1/debian/control +++ v4l-utils-1.22.1/debian/control @@ -4,7 +4,7 @@ Maintainer: Gregor Jasny Uploaders: Loic Minier Build-Depends: debhelper-compat (= 13), - clang:native [amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el s390x powerpc powerpcspe ppc64 sparc64 x32], + clang:native [amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el s390x powerpc powerpcspe riscv64 ppc64 sparc64 x32], doxygen, gettext, graphviz, Could you please consider applying this patch for the future uploads? Regards, Aurelien
Bug#997678: rust-kmon: FTBFS because of a recent upload of a dep
Source: rust-kmon Severity: important Dear Maintainer, This package currently FTBFS with: report: - package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 status: broken reasons: - missing: pkg: package: librust-tui-dev version: 0.9.0-1 architecture: amd64 unsat-dependency: librust-itertools-0.9+default-dev:amd64 depchains: - depchain: - package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 depends: librust-tui-0.9+default-dev:amd64 | librust-tui-0.9+default-dev:amd64 - package: librust-tui+default-dev version: 0.9.0-1 architecture: amd64 depends: librust-tui-dev:amd64 (= 0.9.0-1) Cheers, Sylvestre
Bug#997679: rust-sequoia-sqv: FTBFS because of a recent upload
Source: rust-sequoia-sqv Severity: important Dear Maintainer, This package currently FTBFS with: report: - package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 status: broken reasons: - missing: pkg: package: librust-lalrpop-dev version: 0.17.2-7+b1 architecture: amd64 unsat-dependency: librust-itertools-0.9+default-dev:amd64 | librust-itertools-0.8+default-dev:amd64 depchains: - depchain: - package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 depends: librust-sequoia-openpgp-1-dev:amd64 | librust-sequoia-openpgp-1-dev:amd64 - package: librust-sequoia-openpgp-dev version: 1.3.0-4 architecture: amd64 depends: librust-lalrpop+default-dev:amd64 (>= 0.17-~~) | librust-lalrpop+default-dev:amd64 (>= 0.17-~~) Cheers, Sylvestre
Bug#997680: rust-grcov: FTBFS because of a recent upload
Source: rust-grcov Severity: important Dear Maintainer, This package currently FTBFS with: report: - package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 status: broken reasons: - missing: pkg: package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 unsat-dependency: librust-semver-0.9+default-dev:amd64 Cheers, Sylvestre
Bug#997681: rust-process-viewer: FTBFS because of a recent upload
Source: rust-process-viewer Severity: important Dear Maintainer, This package currently FTBFS with: native-architecture: amd64 report: - package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 status: broken reasons: - missing: pkg: package: librust-rustc-version-dev version: 0.2.3-1+b1 architecture: amd64 unsat-dependency: librust-semver-0.9+default-dev:amd64 depchains: - depchain: - package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 depends: librust-sysinfo-0.13+default-dev:amd64 | librust-sysinfo-0.13+default-dev:amd64 - package: librust-sysinfo-dev version: 0.13.2-3 architecture: amd64 depends: librust-rayon-1+default-dev:amd64 | librust-rayon-1+default-dev:amd64 - package: librust-rayon-dev version: 1.1.0-2 architecture: amd64 depends: librust-crossbeam-deque-0.7+default-dev:amd64 | librust-crossbeam-deque-0.7+default-dev:amd64 - package: librust-crossbeam-deque-dev version: 0.7.4-2 architecture: amd64 depends: librust-crossbeam-epoch-0.8+default-dev:amd64 | librust-crossbeam-epoch-0.8+default-dev:amd64 - package: librust-crossbeam-epoch+std-dev version: 0.8.2-1 architecture: amd64 depends: librust-crossbeam-epoch-dev:amd64 (= 0.8.2-1) - package: librust-crossbeam-epoch-dev version: 0.8.2-1 architecture: amd64 depends: librust-memoffset-0.5+default-dev:amd64 | librust-memoffset-0.5+default-dev:amd64 - package: librust-memoffset-dev version: 0.5.3-1 architecture: amd64 depends: librust-rustc-version-0.2+default-dev:amd64 (>= 0.2.3-~~) | librust-rustc-version-0.2+default-dev:amd64 (>= 0.2.3-~~) Cheers, Sylvestre
Bug#997682: rust-debcargo: FTBFS because of a recent upload
Source: rust-debcargo Severity: important Dear Maintainer, This package currently FTBFS with: report: - package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 status: broken reasons: - missing: pkg: package: librust-cargo-dev version: 0.43.1-4 architecture: amd64 unsat-dependency: librust-env-logger-0.7+default-dev:amd64 depchains: - depchain: - package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 depends: librust-cargo-0.43+default-dev:amd64 | librust-cargo-0.43+default-dev:amd64 Cheers, Sylvestre
Bug#997683: rust-dfrs: FTBFS because of a recent upload
Source: rust-dfrs Severity: important Dear Maintainer, This package currently FTBFS with: report: - package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 status: broken reasons: - missing: pkg: package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 unsat-dependency: librust-env-logger-0.7+default-dev:amd64 Cheers, Sylvesre
Bug#997684: rust-sequoia-sop: FTBFS because of a recent upload
Source: rust-sequoia-sop Severity: important Dear Maintainer, This package currently FTBFS with: package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 status: broken reasons: - missing: pkg: package: librust-lalrpop-dev version: 0.17.2-7+b1 architecture: amd64 unsat-dependency: librust-itertools-0.9+default-dev:amd64 | librust-itertools-0.8+default-dev:amd64 depchains: - depchain: - package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 depends: librust-sequoia-openpgp-1-dev:amd64 | librust-sequoia-openpgp-1-dev:amd64 - package: librust-sequoia-openpgp-dev version: 1.3.0-4 architecture: amd64 depends: librust-lalrpop+default-dev:amd64 (>= 0.17-~~) | librust-lalrpop+default-dev:amd64 (>= 0.17-~~) Cheers, Sylvestre
Bug#997685: rust-spotify-tui: FTBFS because of a recent upload
Source: rust-spotify-tui Severity: important Dear Maintainer, This package currently FTBFS with: report: - package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 status: broken reasons: - missing: pkg: package: librust-rspotify-dev version: 0.7.0-3 architecture: amd64 unsat-dependency: librust-base64-0.12+default-dev:amd64 depchains: - depchain: - package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 depends: librust-rspotify-0.7+default-dev:amd64 | librust-rspotify-0.7+default-dev:amd64 Cheers, Sylvestre
Bug#997686: rust-rusty-tags: FTBFS because of a recent upload
Source: rust-rusty-tags Severity: important Dear Maintainer, This package currently FTBFS with: (I)Dose_applications: --checkonly specified, consider all packages as background packages (I)Dose_applications: Solving... output-version: 1.2 native-architecture: amd64 report: - package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 status: broken reasons: - missing: pkg: package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 unsat-dependency: librust-semver-0.9+default-dev:amd64 Cheers, Sylvestre
Bug#997687: rust-sniffglue: FTBFS because of a recent upload
Source: rust-sniffglue Severity: important Dear Maintainer, This package currently FTBFS with: report: - package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 status: broken reasons: - missing: pkg: package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 unsat-dependency: librust-env-logger-0.7+default-dev:amd64 Cheers, Sylvestre
Bug#997688: rust-bat: FTBFS because of a recent upload
Source: rust-bat Severity: important Dear Maintainer, This package currently FTBFS with: package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 status: broken reasons: - missing: pkg: package: librust-bindgen+logging-dev version: 0.59.1-1 architecture: amd64 unsat-dependency: librust-env-logger-0.7+default-dev:amd64 depchains: - depchain: - package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 depends: librust-syntect-3+parsing-dev:amd64 (>= 3.2.1-~~) | librust-syntect-3+parsing-dev:amd64 (>= 3.2.1-~~) - package: librust-syntect+parsing-dev version: 3.3.0-4 architecture: amd64 depends: librust-onig-6+default-dev:amd64 | librust-onig-6+default-dev:amd64 - package: librust-onig-dev version: 6.1.0-1 architecture: amd64 depends: librust-onig-sys-69-dev:amd64 (>= 69.5-~~) | librust-onig-sys-69-dev:amd64 (>= 69.5-~~) - package: librust-onig-sys-dev version: 69.5.1-4 architecture: amd64 depends: librust-bindgen-0.59+default-dev:amd64 | librust-bindgen-0.59+default-dev:amd64 | librust-bindgen-0.58+default-dev:amd64 | librust-bindgen-0.57+default-dev:amd64 | librust-bindgen-0.56+default-dev:amd64 | librust-bindgen-0.55+default-dev:amd64 - package: librust-bindgen+default-dev version: 0.59.1-1 architecture: amd64 depends: librust-bindgen+logging-dev:amd64 (= 0.59.1-1) Cheers, Sylvestre
Bug#997689: smplayer: please make the build reproducible
Source: smplayer
Version: 21.8.0-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi,
Whilst working on the Reproducible Builds effort [0] we noticed that
smplayer could not be built reproducibly.
This is because it embedded a timestamp in the smplayer.appdata.xml
file. Strangely, this line was commented out (from an XML parser's
perspective, that is), but it still renders the build unreproducible:
-
+
Patch attached that uses SOURCE_DATE_EPOCH.
[0] https://reproducible-builds.org/
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
--- a/debian/patches/11-reproducible-build.patch1970-01-01
01:00:00.0 +0100
--- b/debian/patches/11-reproducible-build.patch2021-10-24
10:04:51.886520349 +0100
@@ -0,0 +1,13 @@
+Description: Make the build reproducible
+Author: Chris Lamb
+Last-Update: 2021-10-24
+
+--- smplayer-21.8.0.orig/install_appdata.sh
smplayer-21.8.0/install_appdata.sh
+@@ -3,5 +3,5 @@ install -m 644 smplayer.appdata.xml $1
+
+ ./get_version.sh
+ sed -e "s/{version}/`cat version`/" -i $1
+-sed -e "s/{date}/`date +%Y-%m-%d`/" -i $1
++sed -e "s/{date}/`date --utc --date="@${SOURCE_DATE_EPOCH:-$(date +%s)}"
+%Y-%m-%d`/" -i $1
+
--- a/debian/patches/series 2021-10-24 09:57:42.166572210 +0100
--- b/debian/patches/series 2021-10-24 10:05:10.302518129 +0100
@@ -8,3 +8,4 @@
#08-disable-yt-js.patch - if the 'only' problem is https - fixed in 09-
10_drop_DONATE_REMINDER.patch
+11-reproducible-build.patch
Bug#997690: ITP: libobject-pad-slotattr-lazyinit-perl -- lazily initialise Object::Pad slots at first read
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Perl Group -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: libobject-pad-slotattr-lazyinit-perl Version : 0.03 Upstream Author : Paul Evans * URL : https://metacpan.org/release/Object-Pad-SlotAttr-LazyInit * License : Artistic or GPL-1+ Programming Lang: Perl, C Description : lazily initialise Object::Pad slots at first read Object::Pad::SlotAttr::LazyInit provides a third-party slot attribute for Object::Pad-based classes, which declares that the slot it is attached to has a lazy initialisation method, which will be called the first time the slot's value is read from. . Object::Pad provides a simple syntax for creating object classes, which uses private variables that look like lexicals as object member fields. This package will be team-maintained at https://salsa.debian.org/perl-team/modules/packages/libobject-pad-slotattr-lazyinit-perl - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmF1RCQACgkQLHwxRsGg ASEeEg//btPlGKHFwia04ZCIGIY/cSG986gebXbGinH7ntOykYrY86d0eiFfYqxA qvjQT+EmrzxknZQ+Z+9qcOPY6oErhSa34a6XyulYMJEwPQbDGrLUJESNBrQ/Ls9M czeMCe4n+rml6ynKKVXQZ7yyiGGYq5Qm58UUZuldTa2APCeEv3gFic2rhSU7vE13 G2cN7OkKfvdbj42eH+2ITf5ZzSB0nLwY1F9eV4LVTFQZyVLvM6fubkUVOFUpi82Y gOiyM//3Cp8muHgyHs6/zmjRWflDIjo4b3Cu88oV+9PqSIDzBnqWW5yekVm01DkA 0mv0Bkbh5Nj28b5PFzu9k/E2R8Hk369ns0cGmesaoGPdkyKSJwzkevCpJeJss0mg av27oVin1OqTadf2G7xvICpCtso9MlZVJChx5GO9B92cxBZuyKiBdrBtrB42B47y UmcQicPGI0vXIcyx+Qn3YSs0PVeBpoHJyy5bXvRB34cWcx25dUw7ixaYJP+mjbiB iVtFf475QyGVoFfN0y0L9LhrUrYBalm37p3Dob3HlWl4lz52skZrt9gQY4+0MNHp B6kwVjlknFKrMvG1i9s6I1HqDTbE007SuNVtZTWu/BopuOAeOhgGrDMuIOkD0omn bUWLhxutq74ldbXh26WSApAE2k4ayMEyOAhyEvYs/TJM3Les6b8= =jYAY -END PGP SIGNATURE-
Bug#931812: Driver does not work in Debian buster
Quack, Interestingly we used 8.046.00-1, with 4.19.0-17 until 2021-10-21 and it worked fine. Then we upgraded to bullseye and the package was upgraded to 8.048.03-3. After rebooting the host never came back until we were able to reach the sever and debug today. It turns out modprobe was not able to locate the module and as you can see here: https://paste.debian.net/1216568/ It says: Status: This module version was INACTIVE for this kernel. I had no idea a DKMS module could be installed, compiled properly but not enabled, that's really confusing. Anyway, we're now using the realtek driver included in the kernel along with firmware-realtek and it works fine. Hope that helps. \_o< -- Marc Dequènes
Bug#997051: fakechroot: deadlock with jemalloc on arm64 and riscv64
On 2021-10-23 08:12, Johannes Schauer Marin Rodrigues wrote:
> Package: fakechroot
> Version: 2.20.1-1
> Severity: normal
> Control: affects -1 + jemalloc
>
> Hi,
>
> libjemalloc and fakechroot do not play well together on arm64 and
> riscv64. Faidon managed to analyze the situation. It follows what they
> found out:
>
> I got a backtrace (see below) by:
> 1) attempting a normal build; killing it when it reaches t/jemalloc.t
> 2) cd test; ./t/jemalloc.t
> 3) gdb -p ($pidof cat)
>
> This is a deadlock, by malloc() being invoked in the code path for malloc().
> Something tries to malloc(), jemalloc tries to initialize itself, which in
> turn
> means trying to open() /sys/kernel/mm/transparent_hugepage/enabled, but open()
> is LD_PRELOADed to fakechroot, which tries to initialize itself, which in turn
> tries to malloc memory.
>
> I'm not entirely sure why that happens yet, or why it only happens on arm64.
> I
> believe it is unrelated to the previous bug, #918742.
The common point of arm64 and riscv64 (and a few new architectures) is
that they lack the older syscalls that can be replaced by newer one. In
that case they lack the open syscall, which can be replaced by openat.
jemalloc tries to query /sys/kernel/mm/transparent_hugepage/enabled
directly through a syscall if available, without going through glibc as
can be seen in src/pages.c:562:
| #if defined(JEMALLOC_USE_SYSCALL) && defined(SYS_open)
| int fd = (int)syscall(SYS_open,
| "/sys/kernel/mm/transparent_hugepage/enabled", O_RDONLY);
| #else
| int fd = open("/sys/kernel/mm/transparent_hugepage/enabled",
O_RDONLY);
| #endif
I guess one fix or workaround would be to add support for the SYS_openat
syscall as a fallback. Luckily this has already been done upstream:
https://github.com/jemalloc/jemalloc/commit/6924f83cb21f75e1c892d8f469500e12f1a3f5a7#diff-e2003bd99a76acf15d071c2fd49cfaeefae69debe6fc304a86f104b662da986c
Regards,
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
Bug#997691: micro-httpd: fix for Lintian warning about missing Depends on update-inetd
Source: micro-httpd
Version: 20140814-2.1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
As per (https://lintian.debian.org/sources/micro-httpd), the correct package to
Depends on for inetd-based systems is update-inetd.
The attached patch prepends it to the package dependencies.
Best Regards,
Martin-Éric
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmF1KM4ACgkQrh+Cd8S0
17ZVexAAlAgNquZEgucZdRFqyc+1y0UqxcN+HYroxUPkkN35Bh4ziva9fkli5eOY
7X6xPBzNBUhW0WQ9TYtUT5rxJKbO7/9YrpM2uWUtV6ypSuAwdJR4YDdsXOpYKasz
uCmBDOXYCdYynCvh3wYGtRU/sFl/QEkjlMb7YUyCn3lREIw2pKh3kqpKFiZOX5w1
nECaPDMMughsfgttp1XKtxotq9ZXbct1//ubM/ICbxJ8KqihOEd/wnnZ81XZD1lj
bpxay5ds82M9wK60LLtK29cNlDikaH/n+Gmb1+lN9j7ADi7vW1SBlpmsx2wMWe2E
zeZvNaftGLVtlrD7IlkrIdglDT18Y53ZxrWL/ufrU/HvrxGw5P9LfilXdmytKdIs
9JOOwIXF9wC/rMWPflN/y029UGJmoG9sSpE1+f7IllP53krIl3Z5ELlwi8CLUrql
BMmPU/Nw9RSTOatn5JQ2CGuETlNTrbqKY0ENWg9Le+9R1q+C+fvczB5D2JcAsXqp
er259rpw2lDFhHRWdJbbzyRdb5klPiHOmBTJbn9/fzQGqF8STmYUPI07pZwoGamC
QQkCE22V9fzwkIM67JPrJiC3BYtpiobhrHtBNbyb5GiSD48dQomNIVoJRSeFMiil
NVRZ5+oDic62C5heZKZ4maakxYZRdx+GmQ0QmOjjKObULm9QCk8=
=68ll
-END PGP SIGNATURE-
diff -Nru micro-httpd-20140814/debian/control
micro-httpd-20140814/debian/control
--- micro-httpd-20140814/debian/control 2020-02-06 01:14:09.0 +0200
+++ micro-httpd-20140814/debian/control 2021-10-24 12:29:38.0 +0300
@@ -11,7 +11,7 @@
Package: micro-httpd
Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}, openbsd-inetd | inet-superserver
| micro-inetd | netcat-traditional | systemd-sysv
+Depends: ${misc:Depends}, ${shlibs:Depends}, update-inetd | inetutils-inetd |
inet-superserver | micro-inetd | openbsd-inetd| rlinetd | xinetd |
netcat-traditional | systemd-sysv
Suggests: micro-proxy
Provides: httpd
Description: really small HTTP server
Bug#997692: RM: crystalhd -- ROM; unusable without usable firmware
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: sramac...@debian.org firmware-crystalhd was removed since it was unusuable (#865978), but crystalhd itself is unusable without the firmware. So let's also remove it. See also #934242 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#997693: ITP: protege -- ontology editor
Package: wnpp Owner: Andrius Merkys Severity: wishlist Control: block -1 by 996898 996779 996810 997050 996996 * Package name: protege Version : 5.5.0 Upstream Author : M. Horridge, C. Nyulas, T. Redmond, T. Tudorache, J. Vendetti * URL : https://protege.stanford.edu * License : BSD-2-Clause Programming Lang: Java Description : ontology editor Protégé Desktop is a feature rich ontology editing environment with full support for the OWL 2 Web Ontology Language, and direct in-memory connections to description logic reasoners like HermiT and Pellet. Protégé Desktop supports creation and editing of one or more ontologies in a single workspace via a completely customizable user interface. Visualization tools allow for interactive navigation of ontology relationships. Advanced explanation support aids in tracking down inconsistencies. Refactor operations available including ontology merging, moving axioms between ontologies, rename of multiple entities, and more. Protégé is a popular (Web version has >300k users) ontology editor, dating back to 1999. Remark: This package is to be maintained with Debian Java Maintainers at https://salsa.debian.org/java-team/protege
Bug#993324: libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp
On 2021-10-23 19:44:49 -0500, Dirk Eddelbuettel wrote: > > I have now 'patched' the upstream setting of GSL_AGE, this results (as kindly > analysed by Sebastian) in new sonames '26' so I prepared a new version which > just went out to unstable. > > Unless I am mistaken, I need to get the release team on board for a proper > transition. Correct? Yes, the workflow is documented at https://wiki.debian.org/Teams/ReleaseTeam/Transitions Cheers > > Dirk > > -- > https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#997694: unbound: FTBFS on hurd-i386
Source: unbound
Version: 1.13.1-1
Severity: important
Tags: patch
User: debian-h...@lists.debian.org
Usertags: hurd
Hi,
Currently unbound FTBFS on GNU/Hurd due to usage of protocol level
IPV6_TCLASS, which is not defined on GNU/Hurd. The attached patch,
services_listen_dnsport.c.diff, make this usage conditional.
This patch has been used to successfully build unbound on GNU/Hurd
and GNU/Linux.
Thanks!
Index: unbound-1.13.1/services/listen_dnsport.c
===
--- unbound-1.13.1.orig/services/listen_dnsport.c
+++ unbound-1.13.1/services/listen_dnsport.c
@@ -821,10 +821,12 @@ set_ip_dscp(int socket, int addrfamily,
return NULL;
ds = dscp << 2;
switch(addrfamily) {
+#ifdef IPV6_TCLASS
case AF_INET6:
if(setsockopt(socket, IPPROTO_IPV6, IPV6_TCLASS, (void*)&ds, sizeof(ds)) < 0)
return sock_strerror(errno);
break;
+#endif
default:
if(setsockopt(socket, IPPROTO_IP, IP_TOS, (void*)&ds, sizeof(ds)) < 0)
return sock_strerror(errno);
Bug#997694: unbound: #997694 Correction of argument name of setsockopt()
s/protocol level/option name/
Bug#973313: The locales package not installed in salsa lintian Docker image
Hi, 在 2021/10/24 下午12:13, Felix Lechner 写道: Hi 肖盛文 Possibly. I thought I had looked into the locales question with Iñaki Malerba from the Salsa CI Team about a year ago. If you found it, I am going to have a party! I hope. :-) The messages have never been reported in any other setting. Just this morning, I was again unable to reproduce the messages on my local system with docker run --rm -it --privileged registry.salsa.debian.org/salsa-ci-team/pipeline/lintian:unstable bash and concluded that Salsa's host system was probably to blame. The shared runner operates in 'privileged' mode. [1] The Salsa's host system, Can ssh to it? SSH to it, login into the lintian docker, then run debug tools like strace -p ,etc. on the lintian's groff-message process. If we has lucky, we perhaps find some thing. We also can check the /var/log dir to find error infos. The Salsa's host system's /var/log dir, check it too. I also contemplated other methods making the C.UTF-8 locale available via the Docker file. [2] Install locales package is preferably in Docker image, /etc/default/locale and /etc/locale.gen will exist in the docker after install it. At present, these two files don't exist in the docker of registry.salsa.debian.org/salsa-ci-team/pipeline/lintian:unstable I'll look into the Salsa runner package list again, unless you beat me to it. Thanks! Kind regards 吴大菲 (Felix Lechner) [1] https://www.educba.com/docker-privileged/ [2] https://leimao.github.io/blog/Docker-Locale/ -- 肖盛文 xiao sheng wen Faris Xiao 微信(wechat)：atzlinux 《铜豌豆 Linux》https://www.atzlinux.com 基于 Debian 的 Linux 中文 桌面 操作系统 Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com GnuPG Public Key: 0x00186602339240CB OpenPGP_0x00186602339240CB.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#997695: transition: draco
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: roehl...@debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear release team, the draco library needs a transition after an ABI break due to a refactored class in a public header. I notified upstream that they forgot to bump the SOVERSION, but they did not react yet. Fortunately, none of the reverse dependencies (PDAL and the filament library waiting in NEW) uses that refactored class, so the transition should run smoothly, and my local rebuild on amd64 was successful at least. The auto-generated ben file is good. Cheers Timo -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmF1LFoACgkQ+C8H+466 LVmFkgwAqAfVlDMCoa6XBfCBPnzUqv1oHnrPHMTKx09keKTWsxAAYaQULy1ieLhm e3lSm+yJHx8UJW0O1poWQiYGslWceQ8iF83SCF8PWpudvoX1T3j8giuRIO1aY+a9 XhP92QSW7iNt/QqHrg2tImsECTsqfnYSJ/BJNUI2wm+oUm5zdy4wByqk5AWRBFot tgONw2hyVKjGSPmd+KnmQsm8zixKdYa6uY+1tKLSvMUnQeP7sD4ViqAVcLlPMAae QYcD2dk+O6ZlwgsAhW1INrlmcjcOjXmMGFEJNnTKRG7fV6xF9qwwnGOf+/aoU8DK 9fp8y7iFtnnnlC0ZWXoE2wEhuhLl3VVFRvJjgENE3aNEdjJwMk3+nMgA0R1HpToa RiJOLWjxUvoZmrdJnbOlYkp6pn9WscLenLiETPjpdXzkd+flBRfrh34SL93KCS7y kLdABmI6jwjwYbcnMCbH8fQZNP0Hes/mUXD/gUo6gQyzQIpM8AaN7Ar18vSQEBhm JGnN4K7X =//07 -END PGP SIGNATURE-
Bug#973313: The locales package not installed in salsa lintian Docker image
Hi, On Sun, Oct 24, 2021 at 2:46 AM xiao sheng wen(肖盛文) wrote: > > The Salsa's host system, Can ssh to it? I do not think either one of us can. > Install locales package is preferably in Docker image, > /etc/default/locale and /etc/locale.gen will exist in the docker after > install it. For now, I requested locales-all. [1] Kind regards Felix Lechner [1] https://salsa.debian.org/salsa-ci-team/pipeline/-/merge_requests/312
Bug#997663: general: bullseye, system freezes completely when firefox freezes
Hello Stephan, > Possibly relevant: > - Are you using X11 or Wayland? Wayland > - Do you have proprietary graphics drivers installed? $ lspci -v | grep -A 10 VGA 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 620 [...] Kernel driver in use: i915 Kernel modules: i915 It seems to be the open source driver 'i915' in the package: 'xserver-xorg-video-intel'. > - Does the freeze occur without those? Does not apply. No proprietary graphics drivers installed. > - Can you SSH into the machine after the screen/input freezes Interesting idea. I will install 'openssh-server' and try this the next time. > - Do you have other indications that the machine is still working? I'm not sure. Maybe I can try the keyboard backlight function? Or the Fn+Special-Function-Keys like: Volume or Display-Brightness ? Thank you very much for your time. Regards, Jacob
Bug#997404: theme-d-gnome: FTBFS: dh_auto_configure: Error: Guile version 2.2 not found.
Hello
Package theme-d-gnome is going to be removed from Debian. See bug #996874.
- Tommi
Lucas Nussbaum kirjoitti 23.10.2021 klo 23.21:
Source: theme-d-gnome
Version: 0.9.6-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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_configure -- --with-guile=2.2 \
--with-guile-gnome=2.16.5
install -d /<>/debian/.debhelper/generated/_source/home
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --with-guile=2.2
--with-guile-gnome=2.16.5
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
Error: Guile version 2.2 not found.
tail -v -n \+0 config.log
==> config.log <==
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by Theme-D-Gnome configure 0.9.6, which was
generated by GNU Autoconf 2.71. Invocation command line was
$ ./configure --build=x86_64-linux-gnu --prefix=/usr
'--includedir=${prefix}/include' '--mandir=${prefix}/share/man'
'--infodir=${prefix}/share/info' --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
'--libdir=${prefix}/lib/x86_64-linux-gnu' --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --with-guile=2.2
--with-guile-gnome=2.16.5
## - ##
## Platform. ##
## - ##
hostname = ip-172-31-6-140
uname -m = x86_64
uname -r = 4.19.0-6-cloud-amd64
uname -s = Linux
uname -v = #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11)
/usr/bin/uname -p = unknown
/bin/uname -X = unknown
/bin/arch = unknown
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /usr/local/sbin/
PATH: /usr/local/bin/
PATH: /usr/sbin/
PATH: /usr/bin/
PATH: /sbin/
PATH: /bin/
PATH: /usr/games/
## --- ##
## Core tests. ##
## --- ##
configure:1744: looking for aux files: missing install-sh
configure:1757: trying ./
configure:1786: ./missing found
configure:1768: ./install-sh found
configure:1916: checking for a BSD-compatible install
configure:1989: result: /usr/bin/install -c
configure:2000: checking whether build environment is sane
configure:2055: result: yes
configure:2214: checking for a race-free mkdir -p
configure:2258: result: /bin/mkdir -p
configure:2265: checking for gawk
configure:2300: result: no
configure:2265: checking for mawk
configure:2286: found /usr/bin/mawk
configure:2297: result: mawk
configure:2308: checking whether make sets $(MAKE)
configure:2331: result: yes
configure:2361: checking whether make supports nested variables
configure:2379: result: yes
configure:2589: checking for pkg-config
configure:2612: found /usr/bin/pkg-config
configure:2624: result: /usr/bin/pkg-config
configure:2649: checking pkg-config is at least version 0.9.0
configure:2652: result: yes
configure:2662: $PKG_CONFIG --exists --print-errors "guile-3.0"
configure:2665: $? = 0
configure:2672: $PKG_CONFIG --exists --print-errors "guile-2.2"
Package guile-2.2 was not found in the pkg-config search path.
Perhaps you should add the directory containing `guile-2.2.pc'
to the PKG_CONFIG_PATH environment variable
No package 'guile-2.2' found
configure:2675: $? = 1
configure:2682: $PKG_CONFIG --exists --print-errors "guile-2.0"
Package guile-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `guile-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'guile-2.0' found
configure:2685: $? = 1
## ##
## Cache variables. ##
## ##
ac_cv_env_PKG_CONFIG_LIBDIR_set=
ac_cv_env_PKG_CONFIG_LIBDIR_value=
ac_cv_env_PKG_CONFIG_PATH_set=
ac_cv_env_PKG_CONFIG_PATH_value=
ac_cv_env_PKG_CONFIG_set=
ac_cv_env_PKG_CONFIG_value=
ac_cv_env_build_alias_set=set
ac_cv_env_build_alias_value=x86_64-linux-gnu
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_path_ac_pt_PKG_CONFIG=/usr/bin/pkg-config
ac_cv_path_install='/usr/bin/install -c'
ac_cv_pa
Bug#994061: [Pkg-libvirt-maintainers] Bug#994061: libvirt: new upstream version available
On Fri, Oct 22, 2021 at 09:10:26AM +0200, Guido Günther wrote: > On Fri, Sep 10, 2021 at 09:25:06PM +0200, Salvatore Bonaccorso wrote: > > Source: libvirt > > Version: 7.6.0-1 > > Severity: wishlist > > X-Debbugs-Cc: car...@debian.org > > > > Hi > > > > When feasible, there is a new upstream version 7.7.0 available. Would > > it be possible to push it to unstable? > > Would be great. I keeps slipping here. Maybe Andrea has it on the list > already? Right. I've been trying to stay on top of upstream releases and import them into Debian quickly, but unfortunately real life keeps getting in the way :( 7.9.0 is set to be released in about a week, so spending time on older releases at this point feels like a waste of time. I'll try to package 7.9.0 shorty after it's out. -- Andrea Bolognani Resistance is futile, you will be garbage collected. signature.asc Description: PGP signature
Bug#997208: firmware-microbit-micropython: FTBFS: platform.h:25:10: fatal error: cstddef: No such file or directory
On Sat, Oct 23, 2021 at 09:11:58PM +0200, Lucas Nussbaum wrote: > Source: firmware-microbit-micropython > Version: 1.0.1-2 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): >> In file included from >> /<>/yotta_modules/mbed-classic/api/Ethernet.h:19, >> from >> /<>/yotta_modules/mbed-classic/common/Ethernet.cpp:16: >> /<>/yotta_modules/mbed-classic/api/platform.h:25:10: fatal >> error: cstddef: No such file or directory >>25 | #include >> | ^ >> compilation terminated. On my bookworm system this is caused by the ARM toolchain being out of sync in the archive, sid/testing have: - gcc-arm-none-eabi 10.3 (15:10.3-2021.07-1) - libstdc++-arm-none-eabi from gcc 8 (15:8-2019-q3-1+13) Where bullseye has both at 15:8-2019-q3-1+13 (and 15:8-2019-q3-1+b1). In essence this is #953420 with different version combinations. I think the first step would be to mark gcc builds with Breaks for the older libstdc++ and vice versa. Or, if possible, submit them in lockstep. Regards, Ondrej
Bug#997663: general: bullseye, system freezes completely when firefox freezes
On Sun, 2021-10-24 at 00:50 +0200, Jacob Kochems wrote: > That is why I consider this *not* to be a bug of FF, although a bug > in FF seems to trigger it. No user space program should be able to tank the > system by hogging up resources. I fully share this idea that Linux should be robust to any kind of these freezes. In past most of these bugs were closed without any real fix. I hope this will not be the case here. -- Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part
Bug#984047: elastix: ftbfs with GCC-11
Control: tags -1 patch fixed-upstream Control: forwarded -1 https://github.com/SuperElastix/elastix/commit/2962fb17f18273e533355ed625e43364e1c537a7 On Wed, Mar 03, 2021 at 04:11:52PM +, Matthias Klose wrote: >... > /<>/Common/Transforms/itkAdvancedCombinationTransform.h:350:52: > error: ISO C++17 does not allow dynamic exception specifications > 350 | virtual void NoCurrentTransformSet( void ) const throw ( > ExceptionObject ); > |^ >... This is fixed with the upstream commit linked above, attached is a rebase to 4.9.0. git already contains a new upstream version, which does not build due to requiring ITK 5 (see #909280). cu Adrian >From a0e4c488d37a5afe267626a0b369ef245f911238 Mon Sep 17 00:00:00 2001 From: Kasper Marstal Date: Thu, 17 Jan 2019 07:35:46 +0100 Subject: ENH: Remove dynamic exception specifications which are deprecated in C++11 --- Common/CostFunctions/itkAdvancedImageToImageMetric.h| 4 ++-- Common/CostFunctions/itkAdvancedImageToImageMetric.hxx | 4 ++-- Common/CostFunctions/itkExponentialLimiterFunction.h| 2 +- Common/CostFunctions/itkExponentialLimiterFunction.hxx | 2 +- Common/CostFunctions/itkImageToImageMetricWithFeatures.h| 2 +- Common/CostFunctions/itkImageToImageMetricWithFeatures.hxx | 2 +- Common/CostFunctions/itkLimiterFunctionBase.h | 2 +- Common/CostFunctions/itkMultiInputImageToImageMetricBase.h | 4 ++-- .../CostFunctions/itkMultiInputImageToImageMetricBase.hxx | 4 ++-- .../itkParzenWindowHistogramImageToImageMetric.h| 2 +- .../itkParzenWindowHistogramImageToImageMetric.hxx | 2 +- .../CostFunctions/itkSingleValuedPointSetToPointSetMetric.h | 2 +- .../itkSingleValuedPointSetToPointSetMetric.hxx | 2 +- Common/Transforms/itkAdvancedCombinationTransform.h | 2 +- Common/Transforms/itkAdvancedCombinationTransform.hxx | 2 +- Common/itkMultiResolutionImageRegistrationMethod2.h | 2 +- Common/itkMultiResolutionImageRegistrationMethod2.hxx | 2 +- .../elxAdvancedKappaStatisticMetric.h | 2 +- .../elxAdvancedKappaStatisticMetric.hxx | 2 +- .../elxAdvancedMattesMutualInformationMetric.h | 2 +- .../elxAdvancedMattesMutualInformationMetric.hxx| 2 +- .../AdvancedMeanSquares/elxAdvancedMeanSquaresMetric.h | 2 +- .../AdvancedMeanSquares/elxAdvancedMeanSquaresMetric.hxx| 2 +- .../itkAdvancedMeanSquaresImageToImageMetric.h | 2 +- .../itkAdvancedMeanSquaresImageToImageMetric.hxx| 2 +- .../elxAdvancedNormalizedCorrelationMetric.h| 2 +- .../elxAdvancedNormalizedCorrelationMetric.hxx | 2 +- .../elxTransformBendingEnergyPenaltyTerm.h | 2 +- .../elxTransformBendingEnergyPenaltyTerm.hxx| 2 +- .../elxCorrespondingPointsEuclideanDistanceMetric.h | 2 +- .../elxCorrespondingPointsEuclideanDistanceMetric.hxx | 2 +- .../elxDisplacementMagnitudePenalty.h | 2 +- .../elxDisplacementMagnitudePenalty.hxx | 2 +- .../elxDistancePreservingRigidityPenaltyTerm.h | 2 +- .../elxDistancePreservingRigidityPenaltyTerm.hxx| 2 +- .../itkDistancePreservingRigidityPenaltyTerm.h | 2 +- .../itkDistancePreservingRigidityPenaltyTerm.hxx| 2 +- .../GradientDifference/elxGradientDifferenceMetric.h| 2 +- .../GradientDifference/elxGradientDifferenceMetric.hxx | 2 +- .../itkGradientDifferenceImageToImageMetric2.h | 2 +- .../itkGradientDifferenceImageToImageMetric2.hxx| 2 +- .../elxKNNGraphAlphaMutualInformationMetric.h | 2 +- .../elxKNNGraphAlphaMutualInformationMetric.hxx | 2 +- .../itkKNNGraphAlphaMutualInformationImageToImageMetric.h | 2 +- .../itkKNNGraphAlphaMutualInformationImageToImageMetric.hxx | 2 +- .../MissingStructurePenalty/elxMissingStructurePenalty.h| 2 +- .../MissingStructurePenalty/elxMissingStructurePenalty.hxx | 2 +- .../MissingStructurePenalty/itkMissingStructurePenalty.h| 2 +- .../MissingStructurePenalty/itkMissingStructurePenalty.hxx | 2 +- .../elxMutualInformationHistogramMetric.h | 2 +- .../elxMutualInformationHistogramMetric.hxx | 2 +- .../elxNormalizedGradientCorrelationMetric.h| 2 +- .../elxNormalizedGradientCorrelationMetric.hxx | 2 +- .../itkNormalizedGradientCorrelationImageToImageMetric.h| 2 +- .../itkNormalizedGradientCorrelationImageToImageMetric.hxx | 2 +- .../elxNormalizedMutualInformationMetric.h | 2 +- .../elxNormalizedMutualInformationMetric.hxx| 2 +- Components/Metrics/PCAMetric/elxPCAMetric.h | 2 +- Components/Metrics/PCAMetric/elxPCAMetric.hxx | 2 +- Components/Metrics/PCAMetric/itkPCAMet
Bug#997194: mtr: FTBFS: ../ui/curses.c:435:17: error: format not a string literal and no format arguments [-Werror=format-security]
On Sat, Oct 23, 2021 at 09:07:10PM +0200, Lucas Nussbaum wrote:
> Source: mtr
> Version: 0.94-2
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
That's an error in your compiler.
A printf-like function often has a string litteral specifying the
format
printf ("a = %d\n", a);
But it is still just a string. So when I want to print something
either in hex or in dec depending on a user-setting.
I could do something like:
printf ("a = ");
printf (theformat, a);
printf ("\n");
Now this has become three statements. To compact this a bit more, we
might do:
sprintf (format, "a = %s\n", theformat); // format is %d or %x or... set by
user
printf (format, a);
I think this is perfectly legal C code and your compiler doesn't like
it. It doesn't just warn, but gives an error.
Roger.
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
> > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread
> > -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include
> > -I/usr/include/pango-1.0 -I/usr/include/atk-1.0
> > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16
> > -I/usr/include/x86_64-linux-gnu -I/usr/include/pango-1.0
> > -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/libmount
> > -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo
> > -I/usr/include/pixman-1 -I/usr/include/harfbuzz -I/usr/include/glib-2.0
> > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid
> > -I/usr/include/freetype2 -I/usr/include/libpng16-g -O2
> > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> > -Werror=format-security -Wall -Wno-pointer-sign -c -o ui/mtr-curses.o `test
> > -f 'ui/curses.c' || echo '../'`ui/curses.c
> > ../ui/curses.c: In function ‘mtr_curses_hosts’:
> > ../ui/curses.c:435:17: error: format not a string literal and no format
> > arguments [-Werror=format-security]
> > 435 | printw(fmt_ipinfo(ctl, addr));
> > | ^~
> > ../ui/curses.c:488:21: error: format not a string literal and no format
> > arguments [-Werror=format-security]
> > 488 | printw(fmt_ipinfo(ctl, addrs));
> > | ^~
> > ../ui/curses.c: In function ‘mtr_curses_graph’:
> > ../ui/curses.c:653:17: error: format not a string literal and no format
> > arguments [-Werror=format-security]
> > 653 | printw(fmt_ipinfo(ctl, addr));
> > | ^~
> > ../ui/curses.c: In function ‘mtr_curses_redraw’:
> > ../ui/curses.c:703:5: error: format not a string literal and no format
> > arguments [-Werror=format-security]
> > 703 | mvprintw(1, maxx - 25, iso_time(&t));
> > | ^~~~
> > ../ui/curses.c:763:42: error: format not a string literal and no format
> > arguments [-Werror=format-security]
> > 763 | mvprintw(rowstat - 1, startstat, msg);
> > | ^~~
> > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread
> > -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include
> > -I/usr/include/pango-1.0 -I/usr/include/atk-1.0
> > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16
> > -I/usr/include/x86_64-linux-gnu -I/usr/include/pango-1.0
> > -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/libmount
> > -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo
> > -I/usr/include/pixman-1 -I/usr/include/harfbuzz -I/usr/include/glib-2.0
> > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid
> > -I/usr/include/freetype2 -I/usr/include/libpng16-g -O2
> > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> > -Werror=format-security -Wall -Wno-pointer-sign -c -o ui/mtr-gtk.o `test -f
> > 'ui/gtk.c' || echo '../'`ui/gtk.c
> > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> > -Werror=format-security -Wall -Wno-pointer-sign -c -o packet/packet.o
> > ../packet/packet.c
> > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> > -Werror=format-security -Wall -Wno-pointer-sign -c -o packet/cmdparse.o
> > ../packet/cmdparse.c
> > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> > -Werror=format-security -Wall -Wno-pointer-sign -c -o packet/command.o
> > ../packet/command.c
> > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> > -Werror=format-security -Wall -Wno-pointer-sign -c -o packet/probe.o
> > ../packet/probe.c
> > In file included from /usr/include/string.h:519,
> > from ../packet/probe.c:31:
> > In function ‘
Bug#996028: InnoDB: corrupted TRX_NO after upgrading to 10.3.31
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, 2021-10-24 at 00:51 +0800, Marc Gallet wrote: > Am I to understand that the expected path forward with what is supposed to be > a minor update offered on oldstable is that everyone shall dump their > databases, > delete the data folder, restore, then upgrade??? > > Sure I can do that, not happy to, but I can. > > However, that's an awful upgrade path and user experience for what would have > normally been a mere and uneventful "apt-get upgrade". I do hope not everyone > still on buster will have to do that after learning about it from a bug > report. To be fair, I think we might actually have an issue with our databases and the way they are stored: it's likely they do have some corruption in it that doesn't show before 10.3.31 but doesn't mean they're ok. So all in all even if the bug is fixed, it might be a good idea to do that backup/restore dance. > > Seems to me it would be better to not have pushed this update to oldstable in > the first place. (I'm not familiar with process, but could it be possibly > undone, > such that users stay on 10.3.29 and are not proposed the broken upgrade?). Well, 10.3.31 actually fixes security issues so you don't really want to stay behind in any case. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmF1SFUACgkQ3rYcyPpX RFtQjgf/ckSNysleNW7oW6QWOrlJrG5DKxw9LhhJYD/0zIMlDUKL3YSJM7VqCUS+ EFrUB2N/r7/p1d7/aispWKWuk3O6LvYmkoqv3V/GddverxZwfsaCCOnBkJXeEWgv dNKw2rv4Vt1xbhFtcISWnxNA3ES48cM1Vfdt7tUL7Qn21RreLYMNvtzez6d9f8mC p1Oan7JHQyPj9Ad50DR0IrnIAc+YAz1RaqQ9Dc98wfW5CkUXqLMk6kXWNImUYNiW zxEtuzDN8jAD1gOAwKLrfKNAIFLwdS0dO0aM6q/ILwSWwgHBdlTn8wkOXgZ8NsEI 2Jlw4arlq2dpPJGjfu912CuLtmmGRw== =PtQ4 -END PGP SIGNATURE-
Bug#983425: add support for DPKG_ROOT
On Sat, Oct 23, 2021 at 11:18:32AM +0200, Johannes Schauer Marin Rodrigues wrote: > Quoting Johannes Schauer Marin Rodrigues (2021-08-24 14:58:55) > > for your convenience, I created a merge request on salsa, fixing #989567 as > > well as #983425. > > > > https://salsa.debian.org/pkg-debconf/debconf/-/merge_requests/8 > > > > Both changes are necessary to support DPKG_ROOT. We verify that chroots > > created > > with DPKG_ROOT and these changes are bit-by-bit identical to chroots created > > the normal way in this salsaci job: > > > > https://salsa.debian.org/helmutg/dpkg-root-demo/-/jobs > > > > Please consider applying these changes to debconf. > > there have been no maintainer replies to this bug and it has been two months > since Colin's last reply to > https://salsa.debian.org/pkg-debconf/debconf/-/merge_requests/8 -- if you > don't > have time, I would like to offer to NMU debconf with the change proposed in > that merge request. What do you think? No, thanks. I had to fix a number of things on top of your MR; I'm doing some more testing and expect to upload today. -- Colin Watson (he/him) [cjwat...@debian.org]
Bug#997641: knews: FTBFS: ar: libdeps specified more than once
Control: reassign -1 xutils-dev Control: affects -1 knews Control: merge 994276 -1 On Sat, Oct 23, 2021 at 11:18:35PM +0200, Lucas Nussbaum wrote: > > ar clq libWidgets.a ArtText.o ArtTree.o CloseSh.o Dialogue.o FileSel.o > > Login.o Manager.o Menu.o MenuG.o MenuKnapp.o MenuShell.o > > Notice.o Knapp.o Message.o PullRight.o Sash.o Scrollable.o ScrBar.o > > ScrList.o SeparatorG.o Shadow.o StringG.o TextField.o Toggle.o > > ToggleG.o Util.o Layout.o laylex.o laygram.o > > ar: libdeps specified more than once > > make[3]: *** [Makefile:1057: libWidgets.a] Error 1 knews uses imake, so this is #994276. -- Colin Watson (he/him) [cjwat...@debian.org]
Bug#997697: libesmtp-dev: Missing dependency on libssl-dev
Package: libesmtp-dev Version: 1.1.0-2 Severity: serious Justification: Missing dependency X-Debbugs-Cc: car...@debian.org Hi libesmtp-1.0.pc contains Requires.private: openssl >= 1.1.0 but the libesmtp-dev binary package misses a Depends on libssl-dev accordingly. Accordingly: $ pkg-config --print-errors --exists libesmtp-1.0 Package openssl was not found in the pkg-config search path. Perhaps you should add the directory containing `openssl.pc' to the PKG_CONFIG_PATH environment variable Package 'openssl', required by 'libesmtp-1.0', not found Regards, Salvatore
Bug#997615: troffcvt: FTBFS: ar: libdeps specified more than once
Control: reassign -1 xutils-dev Control: affects -1 troffcvt Control: merge 994276 -1 On Sat, Oct 23, 2021 at 11:18:52PM +0200, Lucas Nussbaum wrote: > > ar clq libport.a ato.o dir.o fd.o lock.o mem.o > > ar: libdeps specified more than once > > make[3]: *** [Makefile:325: libport.a] Error 1 troffcvt uses imake, so this is #994276. -- Colin Watson (he/him) [cjwat...@debian.org]
Bug#997663: general: bullseye, system freezes completely when firefox freezes
On Sun, Oct 24, 2021 at 12:25:23PM +0200, jacobkoch...@gmail.com wrote: > Hello Stephan, > > > Possibly relevant: > > - Are you using X11 or Wayland? > Wayland > > > - Do you have proprietary graphics drivers installed? > $ lspci -v | grep -A 10 VGA > 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 > (rev 02) (prog-if 00 [VGA controller]) > Subsystem: CLEVO/KAPOK Computer HD Graphics 620 > [...] > Kernel driver in use: i915 > Kernel modules: i915 > It seems to be the open source driver 'i915' in the package: > 'xserver-xorg-video-intel'. > > > - Does the freeze occur without those? > Does not apply. No proprietary graphics drivers installed. > > > - Can you SSH into the machine after the screen/input freezes > Interesting idea. I will install 'openssh-server' and try this the next > time. > > > - Do you have other indications that the machine is still working? > I'm not sure. Maybe I can try the keyboard backlight function? > Or the Fn+Special-Function-Keys like: Volume or Display-Brightness ? Does this only happen when on battery power? There is https://gitlab.freedesktop.org/drm/intel/-/issues/3510 which looks similar, and happens to me. signature.asc Description: PGP signature
Bug#997700: node-proxyquire: FTBFS: tests fail
Source: node-proxyquire Version: 2.1.3+~1.0.1+~1.0.2-11 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > eslint --format tap --no-eslintrc --env es6,node --no-inline-config '**/*.js' > TAP version 13 > 1..59 > ok 1 - /<>/examples/api/api-test.js > ok 2 - /<>/examples/api/samples/bar.js > ok 3 - /<>/examples/api/samples/foo.js > ok 4 - /<>/examples/api/samples/stats.js > ok 5 - /<>/examples/async/foo-tests.js > ok 6 - /<>/examples/async/foo.js > ok 7 - /<>/examples/example-utils.js > ok 8 - /<>/examples/simple/foo.inlineoverride.test.js > ok 9 - /<>/examples/simple/foo.js > ok 10 - /<>/examples/simple/foo.test.js > ok 11 - /<>/examples/sinon/foo-tests.js > ok 12 - /<>/examples/sinon/foo.js > ok 13 - /<>/index.js > ok 14 - /<>/lib/is.js > ok 15 - /<>/lib/proxyquire-error.js > ok 16 - /<>/lib/proxyquire.js > ok 17 - /<>/test/proxyquire-api.js > ok 18 - /<>/test/proxyquire-argumentvalidation.js > ok 19 - /<>/test/proxyquire-cache.js > ok 20 - /<>/test/proxyquire-compat.js > ok 21 - /<>/test/proxyquire-extensions.js > ok 22 - /<>/test/proxyquire-global.js > ok 23 - /<>/test/proxyquire-independence.js > ok 24 - /<>/test/proxyquire-non-object.js > ok 25 - /<>/test/proxyquire-notexisting.js > ok 26 - /<>/test/proxyquire-relative-paths.js > ok 27 - /<>/test/proxyquire-remove.js > ok 28 - /<>/test/proxyquire-sub-dependencies.js > ok 29 - /<>/test/proxyquire.js > ok 30 - /<>/test/samples/bar.js > ok 31 - /<>/test/samples/boof.js > ok 32 - /<>/test/samples/cache/bar.js > ok 33 - /<>/test/samples/cache/foo.js > ok 34 - /<>/test/samples/extensions.js > ok 35 - /<>/test/samples/foo-singleton.js > ok 36 - /<>/test/samples/foo.js > ok 37 - /<>/test/samples/fooarray.js > ok 38 - /<>/test/samples/foobool.js > ok 39 - /<>/test/samples/foonum.js > ok 40 - /<>/test/samples/global/bar.js > ok 41 - /<>/test/samples/global/baz.js > ok 42 - /<>/test/samples/global/foo-deferred.js > ok 43 - /<>/test/samples/global/foo.js > ok 44 - /<>/test/samples/no-call-thru-test/index.js > ok 45 - /<>/test/samples/no-call-thru-test/required.js > ok 46 - /<>/test/samples/notexisting/foo-relative.js > ok 47 - /<>/test/samples/notexisting/foo.js > ok 48 - /<>/test/samples/relative-paths/a/index.js > ok 49 - /<>/test/samples/relative-paths/a/util.js > ok 50 - /<>/test/samples/relative-paths/b/index.js > ok 51 - /<>/test/samples/relative-paths/b/util.js > ok 52 - /<>/test/samples/stats.js > ok 53 - /<>/test/samples/sub-dependencies/bar.js > ok 54 - /<>/test/samples/sub-dependencies/baz.js > ok 55 - /<>/test/samples/sub-dependencies/foo.js > ok 56 - /<>/Xerror/index.js > ok 57 - /<>/Xerror/test.js > ok 58 - /<>/Xkeys/index.js > ok 59 - /<>/Xkeys/test.js > > tape Xerror/test.js Xkeys/test.js | debian/tap-todo \ > 'should be equal' > TAP version 13 > # (anonymous) > not ok 1 should be strictly equal > # skipped 0 > # skip-patterns 1 > make[1]: *** [debian/rules:22: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/node-proxyquire_2.1.3+~1.0.1+~1.0.2-11_unstable.log 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.
Bug#997701: golang-github-mattn-go-runewidth: FTBFS: open /usr/share/unicode/emoji/emoji-data.txt: no such file or directory
Source: golang-github-mattn-go-runewidth Version: 0.0.13-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package golang-github-mattn-go-runewidth > dpkg-buildpackage: info: source version 0.0.13-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Anthony Fok > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean --buildsystem=golang --with=golang --builddirectory=_build >dh_auto_clean -O--buildsystem=golang -O--builddirectory=_build >dh_autoreconf_clean -O--buildsystem=golang -O--builddirectory=_build >dh_clean -O--buildsystem=golang -O--builddirectory=_build > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building golang-github-mattn-go-runewidth using existing > ./golang-github-mattn-go-runewidth_0.0.13.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: warning: ignoring deletion of file runewidth_table.go, use > --include-removal to override > dpkg-source: info: building golang-github-mattn-go-runewidth in > golang-github-mattn-go-runewidth_0.0.13-1.debian.tar.xz > dpkg-source: info: building golang-github-mattn-go-runewidth in > golang-github-mattn-go-runewidth_0.0.13-1.dsc > debian/rules binary > dh binary --buildsystem=golang --with=golang --builddirectory=_build >dh_update_autotools_config -O--buildsystem=golang -O--builddirectory=_build >dh_autoreconf -O--buildsystem=golang -O--builddirectory=_build >dh_auto_configure -O--buildsystem=golang -O--builddirectory=_build >dh_auto_build -O--buildsystem=golang -O--builddirectory=_build > cd _build && go generate -v github.com/mattn/go-runewidth > src/github.com/mattn/go-runewidth/benchmark_test.go > src/github.com/mattn/go-runewidth/runewidth.go > 2021/10/23 07:42:24 open /usr/share/unicode/emoji/emoji-data.txt: no such > file or directory > exit status 1 > src/github.com/mattn/go-runewidth/runewidth.go:9: running "go": exit status 1 > dh_auto_build: error: cd _build && go generate -v > github.com/mattn/go-runewidth returned exit code 1 > make: *** [debian/rules:6: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/10/23/golang-github-mattn-go-runewidth_0.0.13-1_unstable.log 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.
Bug#997699: r-cran-git2r: FTBFS: configure.ac: error: required file 'config.rpath' not found
Source: r-cran-git2r Version: 0.28.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package r-cran-git2r > dpkg-buildpackage: info: source version 0.28.0-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Andreas Tille > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean --buildsystem R >dh_auto_clean -O--buildsystem=R >dh_autoreconf_clean -O--buildsystem=R >dh_clean -O--buildsystem=R > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building r-cran-git2r using existing > ./r-cran-git2r_0.28.0.orig.tar.gz > dpkg-source: info: building r-cran-git2r in > r-cran-git2r_0.28.0-1.debian.tar.xz > dpkg-source: info: building r-cran-git2r in r-cran-git2r_0.28.0-1.dsc > debian/rules binary > dh binary --buildsystem R >dh_update_autotools_config -O--buildsystem=R >dh_autoreconf -O--buildsystem=R > configure.ac: error: required file 'config.rpath' not found > dh_autoreconf: error: autoreconf -f -i returned exit code 1 > make: *** [debian/rules:4: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/10/23/r-cran-git2r_0.28.0-1_unstable.log 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.
Bug#997702: trinityrnaseq: FTBFS: /bin/sh: 1: cd: can't cd to htslib
Source: trinityrnaseq Version: 2.11.0+dfsg-6 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>/trinity-plugins/slclust/src' > rm -f slcluster.o graph.o graphnode.o cmd_line_opts.o core a.out *~ \#* > slclust Makefile.bak \ > ../bin/slclust > make[4]: Leaving directory '/<>/trinity-plugins/slclust/src' > make[3]: Leaving directory '/<>/trinity-plugins/slclust' > cd COLLECTL && rm -rf "collectl-4.1.0" && rm -f collectl > cd htslib && /usr/bin/make clean > /bin/sh: 1: cd: can't cd to htslib > make[2]: *** [Makefile:55: clean] Error 2 The full build log is available from: http://qa-logs.debian.net/2021/10/23/trinityrnaseq_2.11.0+dfsg-6_unstable.log 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.
Bug#997698: pg-dirtyread: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.
Source: pg-dirtyread
Version: 2.3-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 pg_dirtyread.so libpg_dirtyread.a libpg_dirtyread.pc
> rm -f pg_dirtyread.o dirtyread_tupconvert.o pg_dirtyread.bc
> dirtyread_tupconvert.bc
> rm -rf results/ regression.diffs regression.out tmp_check/ tmp_check_iso/
> log/ output_iso/
> make[1]: Leaving directory '/<>'
>dh_clean
>pg_buildext checkcontrol
> --- debian/control2020-10-19 09:11:52.0 +
> +++ debian/control.1cKEsI 2021-10-23 06:29:14.799095718 +
> @@ -9,9 +9,9 @@
> Vcs-Browser: https://github.com/ChristophBerg/pg_dirtyread
> Vcs-Git: https://github.com/ChristophBerg/pg_dirtyread.git
>
> -Package: postgresql-13-dirtyread
> +Package: postgresql-14-dirtyread
> Architecture: any
> -Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-13
> +Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-14
> Description: Read dead but unvacuumed tuples from a PostgreSQL relation
> The pg_dirtyread extension provides the ability to read dead but unvacuumed
> rows from a PostgreSQL relation.
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is
> required.
> make: *** [debian/rules:7: clean] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pg-dirtyread_2.3-2_unstable.log
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.
Bug#997703: wal2json: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.
Source: wal2json
Version: 2.4-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 wal2json.so wal2json.o \
> wal2json.bc
> rm -rf results/ regression.diffs regression.out tmp_check/ tmp_check_iso/
> log/ output_iso/
> make[1]: Leaving directory '/<>'
>dh_clean
>pg_buildext checkcontrol
> --- debian/control2021-09-09 15:19:52.0 +
> +++ debian/control.odxLl0 2021-10-23 07:38:30.876840629 +
> @@ -10,9 +10,9 @@
> Vcs-Git: https://salsa.debian.org/postgresql/wal2json.git
> Vcs-Browser: https://salsa.debian.org/postgresql/wal2json
>
> -Package: postgresql-13-wal2json
> +Package: postgresql-14-wal2json
> Architecture: any
> -Depends: postgresql-13, ${misc:Depends}, ${shlibs:Depends}
> +Depends: postgresql-14, ${misc:Depends}, ${shlibs:Depends}
> Description: PostgreSQL logical decoding JSON output plugin
> wal2json is an output plugin for PostgreSQL's logical decoding. The plugin
> has
> access to tuples produced by INSERT and UPDATE. Also, UPDATE/DELETE old row
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is
> required.
> make: *** [debian/rules:12: clean] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/wal2json_2.4-1_unstable.log
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.
Bug#997704: pgfincore: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.
Source: pgfincore
Version: 1.2.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 pgfincore.so pgfincore.o \
> pgfincore.bc
> rm -rf results/ regression.diffs regression.out tmp_check/ tmp_check_iso/
> log/ output_iso/
> make[1]: Leaving directory '/<>'
>dh_clean
>pg_buildext checkcontrol
> --- debian/control2020-10-19 10:39:15.0 +
> +++ debian/control.7wnJbI 2021-10-23 07:39:31.290006942 +
> @@ -10,9 +10,9 @@
> Vcs-Browser: http://git.postgresql.org/gitweb/?p=pgfincore.git
> Homepage: http://villemain.org/projects/pgfincore
>
> -Package: postgresql-13-pgfincore
> +Package: postgresql-14-pgfincore
> Architecture: any
> -Depends: ${shlibs:Depends}, ${misc:Depends}, postgresql-13
> +Depends: ${shlibs:Depends}, ${misc:Depends}, postgresql-14
> Description: set of PostgreSQL functions to manage blocks in memory
> Those functions let you know which and how many disk block from a relation
> are in the page cache of the operating system, and eventually write the
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is
> required.
> make: *** [debian/rules:7: clean] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pgfincore_1.2.2-2_unstable.log
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.
Bug#997705: trapperkeeper-metrics-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.junit:junit-bom:pom:debian has not been downloaded from i
Source: trapperkeeper-metrics-clojure Version: 1.3.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > lein test > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:28: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/trapperkeeper-metrics-clojure_1.3.1-2_unstable.log 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.
Bug#997706: skimage: FTBFS: Unknown key(s) in sphinx_gallery_conf: 'binder-disabled'
Source: skimage
Version: 0.18.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>/doc'
> python3.9 tools/build_modref_templates.py
> Matplotlib created a temporary config/cache directory at
> /tmp/matplotlib-82kakoz8 because the default path
> (/sbuild-nonexistent/.config/matplotlib) is not a writable directory; it is
> highly recommended to set the MPLCONFIGDIR environment variable to a writable
> directory, in particular to speed up the import of Matplotlib and to better
> support multiprocessing.
> /<>/doc/tools/apigen.py:205: UserWarning: Viewer requires Qt
> mod = __import__(uri, fromlist=[uri.split('.')[-1]])
> WARNING: Empty - skimage.scripts
> outdir:
> 26 files written
> Build API docs...done.
> Copying release notes
> python3.9 -m sphinx -b html -d build/doctrees -D mathjax_path=MathJax.js
> source build/html
> Running Sphinx v4.2.0
> Matplotlib created a temporary config/cache directory at
> /tmp/matplotlib-gggxkkq5 because the default path
> (/sbuild-nonexistent/.config/matplotlib) is not a writable directory; it is
> highly recommended to set the MPLCONFIGDIR environment variable to a writable
> directory, in particular to speed up the import of Matplotlib and to better
> support multiprocessing.
> making output directory... done
> [autosummary] generating autosummary for: api/api.rst, api/skimage.color.rst,
> api/skimage.data.rst, api/skimage.draw.rst, api/skimage.exposure.rst,
> api/skimage.feature.rst, api/skimage.filters.rank.rst,
> api/skimage.filters.rst, api/skimage.future.graph.rst,
> api/skimage.future.rst, ..., user_guide/numpy_images.rst,
> user_guide/plugins.rst, user_guide/transforming_image_data.rst,
> user_guide/tutorial_parallelization.rst,
> user_guide/tutorial_segmentation.rst, user_guide/tutorials.rst,
> user_guide/video.rst, user_guide/viewer.rst, user_guide/visualization.rst,
> values.md
> /usr/lib/python3.9/importlib/__init__.py:127: UserWarning:
>
> Viewer requires Qt
>
> loading intersphinx inventory from
> /usr/share/doc/python3.9/html/objects.inv...
> loading intersphinx inventory from ./_intersphinx/numpy-objects.inv...
> loading intersphinx inventory from ./_intersphinx/scipy-objects.inv...
> loading intersphinx inventory from ./_intersphinx/sklearn-objects.inv...
> loading intersphinx inventory from
> /usr/share/doc/python-matplotlib-doc/html/objects.inv...
> generating gallery...
>
> Configuration error:
> Unknown key(s) in sphinx_gallery_conf:
> 'binder-disabled'
> make[2]: *** [Makefile:58: html] Error 2
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/skimage_0.18.3-1_unstable.log
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.
Bug#997707: fava: FTBFS: help2man: can't get `--help' info from PYTHONPATH="/<>/src" python3 -m fava.cli
Source: fava Version: 1.18-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 > I: pybuild base:232: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.9_fava/build/fava > copying src/fava/application.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava > copying src/fava/cli.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava > copying src/fava/__init__.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava > copying src/fava/helpers.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava > copying src/fava/template_filters.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava > copying src/fava/context.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava > copying src/fava/serialisation.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava > copying src/fava/json_api.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava > creating /<>/.pybuild/cpython3_3.9_fava/build/fava/util > copying src/fava/util/__init__.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/util > copying src/fava/util/date.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/util > copying src/fava/util/ranking.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/util > copying src/fava/util/excel.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/util > creating /<>/.pybuild/cpython3_3.9_fava/build/fava/core > copying src/fava/core/extensions.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/core > copying src/fava/core/conversion.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/core > copying src/fava/core/documents.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/core > copying src/fava/core/ingest.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/core > copying src/fava/core/watcher.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/core > copying src/fava/core/__init__.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/core > copying src/fava/core/_compat.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/core > copying src/fava/core/tree.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/core > copying src/fava/core/fava_options.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/core > copying src/fava/core/misc.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/core > copying src/fava/core/budgets.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/core > copying src/fava/core/query_shell.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/core > copying src/fava/core/attributes.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/core > copying src/fava/core/file.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/core > copying src/fava/core/number.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/core > copying src/fava/core/accounts.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/core > copying src/fava/core/charts.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/core > copying src/fava/core/module_base.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/core > copying src/fava/core/filters.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/core > copying src/fava/core/inventory.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/core > creating /<>/.pybuild/cpython3_3.9_fava/build/fava/plugins > copying src/fava/plugins/__init__.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/plugins > copying src/fava/plugins/link_documents.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/plugins > copying src/fava/plugins/tag_discovered_documents.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/plugins > creating /<>/.pybuild/cpython3_3.9_fava/build/fava/ext > copying src/fava/ext/__init__.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/ext > copying src/fava/ext/auto_commit.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/ext > creating /<>/.pybuild/cpython3_3.9_fava/build/fava/help > copying src/fava/help/__init__.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/help > creating > /<>/.pybuild/cpython3_3.9_fava/build/fava/ext/portfolio_list > copying src/fava/ext/portfolio_list/__init__.py -> > /<>/.pybuild/cpython3_3.9_fava/build/fava/ext/portfolio_list > running egg_info > writing src/fava.egg-info/PKG-INFO > writing dependency_links to src/fava.egg-info/dependency_links.txt > writing entry points to src/fava.egg-info/entry_points.txt > writing requirements to src/fava.egg-info/requires.txt > writing top-level names to src/fava.egg-info/top_level.txt > reading manifest file 'src/fava.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no previously-included files found matching '.editorconfig' > warning: no previously-included files found matching '.gitignore' > warning: no previously-included files found matching '.travis.yml' > warning: no previously-included files found matching 'appveyor.yml' > warning: no previously-inclu
Bug#997708: slony1-2: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.
Source: slony1-2
Version: 2.2.10-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package slony1-2
> dpkg-buildpackage: info: source version 2.2.10-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Christoph Berg
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> pg_buildext checkcontrol
> --- debian/control2021-01-18 16:09:47.0 +
> +++ debian/control.d5gD6h 2021-10-23 07:29:06.033674019 +
> @@ -75,26 +75,26 @@
> This package contains the documentation for the Slony-I system. It is
> not required for normal operation.
>
> -Package: postgresql-13-slony1-2
> +Package: postgresql-14-slony1-2
> Architecture: any
> Depends:
> - postgresql-13,
> + postgresql-14,
> ${misc:Depends},
> ${shlibs:Depends},
> Suggests:
> slony1-2-bin,
> Provides:
> - postgresql-13-slony1,
> + postgresql-14-slony1,
> Conflicts:
> - postgresql-13-slony1,
> -Description: replication system for PostgreSQL: PostgreSQL 13 server plug-in
> + postgresql-14-slony1,
> +Description: replication system for PostgreSQL: PostgreSQL 14 server plug-in
> Slony-I is an asynchronous master-to-multiple-slaves replication system
> for PostgreSQL with cascading and slave promotion.
> .
> This package contains the support functions that are loaded into the
> PostgreSQL database server. It needs to be installed on the hosts where
> the database server nodes are running. This package works with version
> - 13 of the PostgreSQL server; you need the package that corresponds to
> + 14 of the PostgreSQL server; you need the package that corresponds to
> the version of your database server.
> .
> The actual replication daemon and the administration tools are in the
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is
> required.
> make: *** [/usr/share/postgresql-common/pgxs_debian_control.mk:9:
> debian/control] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/slony1-2_2.2.10-1_unstable.log
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.
Bug#997709: initramfs-tools: FTBFS: shellcheck errors
Source: initramfs-tools
Version: 0.140
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> shellcheck -e SC1090,SC1091 -s dash hook-functions $(find hooks scripts -type
> f) $({ find . -maxdepth 1 -type f -executable; find debian -maxdepth 1 -type
> f; find docs kernel -type f; } | xargs grep -l '^#!/bin/sh')
>
> In scripts/nfs line 42:
> if [ "x${NFSROOT}" = "xauto" ]; then
> ^---^ SC2268: Avoid x-prefix in comparisons as it no
> longer serves a purpose.
>
> Did you mean:
> if [ "${NFSROOT}" = "auto" ]; then
>
>
> In ./init line 170:
> [ "x$debug" = "xy" ] && log_output=/dev/kmsg
> ^---^ SC2268: Avoid x-prefix in comparisons as it no
> longer serves a purpose.
>
> Did you mean:
> [ "$debug" = "y" ] && log_output=/dev/kmsg
>
>
> In ./update-initramfs line 14:
> if [ -n "$DPKG_MAINTSCRIPT_PACKAGE" ] && [ $# = 1 ] && [ x"$1" = x-u ]; then
> ^---^ SC2268: Avoid
> x-prefix in comparisons as it no longer serves a purpose.
>
> Did you mean:
> if [ -n "$DPKG_MAINTSCRIPT_PACKAGE" ] && [ $# = 1 ] && [ "$1" = -u ]; then
>
>
> In ./unmkinitramfs line 115:
> if [ -n "$dir" ]; then
> ^--^ SC2030: Modification of dir is local
> (to subshell caused by (..) group).
>
>
> In ./unmkinitramfs line 130:
> xcpio "$subarchive" "${dir:+$dir/main}" -i "$@"
> ^---^ SC2031: dir was
> modified in a subshell. That change might be lost.
> ^--^ SC2031: dir was modified in
> a subshell. That change might be lost.
>
>
> In ./unmkinitramfs line 133:
> xcpio "$initramfs" "$dir" -i "$@"
> ^--^ SC2031: dir was modified in a
> subshell. That change might be lost.
>
>
> In debian/initramfs-tools-core.postrm line 5:
> if [ "x${1}" = "xpurge" ]; then
> ^-^ SC2268: Avoid x-prefix in comparisons as it no longer serves a
> purpose.
>
> Did you mean:
> if [ "${1}" = "purge" ]; then
>
> For more information:
> https://www.shellcheck.net/wiki/SC2030 -- Modification of dir is local (to
> ...
> https://www.shellcheck.net/wiki/SC2031 -- dir was modified in a subshell.
> T...
> https://www.shellcheck.net/wiki/SC2268 -- Avoid x-prefix in comparisons as
> ...
> make[1]: *** [debian/rules:28: override_dh_auto_test] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/initramfs-tools_0.140_unstable.log
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.
Bug#997710: erlang-erlware-commons: FTBFS: src/ec_cmd_log.erl:160:5: ambiguous call of overridden auto-imported BIF error/3
Source: erlang-erlware-commons
Version: 1.3.1+dfsg-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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=rebar --with rebar
>dh_update_autotools_config -O--buildsystem=rebar
>dh_autoreconf -O--buildsystem=rebar
>dh_auto_configure -O--buildsystem=rebar
> make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile
> configure
> make[1]: Nothing to be done for 'configure'.
>dh_auto_build -O--buildsystem=rebar
> make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile
> build
> rebar_compile
> rebar compile skip_deps=true -vv
> DEBUG: Evaluating config script "/<>/rebar.config.script"
> DEBUG: Consult config file "/<>/rebar.config"
> DEBUG: Rebar location: "/usr/bin/rebar"
> DEBUG: Consult config file "/<>/src/erlware_commons.app.src"
> DEBUG: Available deps: []
> DEBUG: Missing deps : []
> DEBUG: Plugins requested while processing /<>: []
> DEBUG: Predirs: []
> ==> erlang-erlware-commons-1.3.1+dfsg (compile)
> DEBUG: Matched required ERTS version: 12.1.1 -> .*
> DEBUG: Matched required OTP release: 24 -> .*
> DEBUG: Min OTP version unconfigured
> DEBUG: erl_opts [debug_info,
> {d,namespaced_types},
> {d,have_callback_support},
> {d,rand_module},
> {d,unicode_str},
> debug_info,warnings_as_errors]
> DEBUG: Files to compile first: ["src/ec_vsn.erl","src/ec_dictionary.erl"]
> Compiled src/ec_vsn.erl
> Compiled src/ec_dictionary.erl
> DEBUG: Starting 3 compile worker(s)
> Compiled src/ec_dict.erl
> Compiled src/ec_orddict.erl
> Compiled src/ec_git_vsn.erl
> src/ec_cmd_log.erl:160:5: ambiguous call of overridden auto-imported BIF
> error/3
> - use erlang:error/3 or "-compile({no_auto_import,[error/3]})." to resolve
> name clash
> Compiling src/ec_cmd_log.erl failed:
> DEBUG: Worker compilation failed: {{error,
> {error,[],
> [["src/ec_cmd_log.erl:160:5: ambiguous
> call of overridden auto-imported BIF error/3\n - use erlang:error/3 or
> \"-compile({no_auto_import,[error/3]}).\" to resolve name clash\n"]]}},
>{source,"src/ec_cmd_log.erl"}}
> ERROR: compile failed while processing /<>: rebar_abort
> make[1]: *** [/usr/share/dh-rebar/make/dh-rebar.Makefile:126: rebar_compile]
> Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/erlang-erlware-commons_1.3.1+dfsg-2_unstable.log
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.
Bug#997711: puppetlabs-http-client-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.junit:junit-bom:pom:debian has not been downloaded from
Source: puppetlabs-http-client-clojure Version: 1.2.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > lein test > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:24: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/puppetlabs-http-client-clojure_1.2.0-2_unstable.log 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.
Bug#997712: repmgr: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.
Source: repmgr
Version: 5.2.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package repmgr
> dpkg-buildpackage: info: source version 5.2.1-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Marco Nenciarini
>
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> pg_buildext checkcontrol
> --- debian/control2021-08-23 16:33:21.0 +
> +++ debian/control.BKCvyy 2021-10-23 06:29:04.153028096 +
> @@ -50,14 +50,14 @@
> .
> This is a metapackage that depends on the version specific packages.
>
> -Package: postgresql-13-repmgr
> +Package: postgresql-14-repmgr
> Architecture: any
> -Depends: postgresql-13, repmgr-common (>= ${source:Version}),
> ${misc:Depends}, ${shlibs:Depends}
> +Depends: postgresql-14, repmgr-common (>= ${source:Version}),
> ${misc:Depends}, ${shlibs:Depends}
> Suggests: rsync
> -Description: replication manager for PostgreSQL 13
> +Description: replication manager for PostgreSQL 14
> repmgr is an open-source tool suite for managing replication and failover
> in a
> cluster of PostgreSQL servers. It enhances PostgreSQL's built-in hot-standby
> capabilities with tools to set up standby servers, monitor replication, and
> perform administrative tasks such as failover or manual switchover
> operations.
> .
> - This package contains repmgr for PostgreSQL 13.
> + This package contains repmgr for PostgreSQL 14.
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is
> required.
> make: *** [/usr/share/postgresql-common/pgxs_debian_control.mk:9:
> debian/control] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/repmgr_5.2.1-1_unstable.log
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.
Bug#997713: pushpin: FTBFS: error: failed to select a version for the requirement `base64 = "^0.12"`
Source: pushpin Version: 1.32.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > ./configure --prefix=/usr --qtselect=5 --configdir=/etc > --extraconf="$QMAKE_BUILDFLAGS" --verbose > /usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > Configuring Pushpin ... > > PREFIX=/usr > BINDIR=/usr/bin > EX_QTDIR= > QC_EXTRACONF=QMAKE_CPPFLAGS *= -Wdate-time -D_FORTIFY_SOURCE=2 QMAKE_CFLAGS > *= -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 > QMAKE_CXXFLAGS *= -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 QMAKE_LFLAGS *= -Wl,-z,relro -Wl,-z,now -Wl,--as-needed > QC_LIBDIR= > QC_CONFIGDIR=/etc > QC_RUNDIR= > QC_LOGDIR= > QC_DISABLE_cargo= > QC_DEFAULT_ENABLE_cargo= > > Verifying Qt build environment ... > running: /usr/bin/qtchooser -run-tool=qmake -qt=5 -query QT_INSTALL_BINS > running: "/usr/lib/qt5/bin/qmake" -query QT_VERSION > qmake found in /usr/lib/qt5/bin/qmake > /usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > makespec is > -> ok > conf command: [./configure] > conf path:[./configure] > srcdir: [/<>] > builddir: [/<>] > profile: [/<>/pushpin.pro] > qmake path: [/usr/lib/qt5/bin/qmake] > qmakespec:[] > make tool:[/usr/bin/gmake] > > Checking for Qt >= 5.2.0 ... yes > > * extra += APP_VERSION = 1.32.2 > * extra += LIBDIR = /usr/lib/pushpin > * extra += CONFIGDIR = /etc/pushpin > * extra += RUNDIR = /var/run/pushpin > * extra += LOGDIR = /var/log/pushpin > * INCLUDEPATH += $$PWD/src > * DEFINES += HAVE_CONFIG > Checking for libzmq >= 2.0 ... > * [pkg-config libzmq --exists] > * returned: 0 > * [pkg-config libzmq --atleast-version=2.0] > * returned: 0 > * [pkg-config libzmq --modversion] > 4.3.4 > * returned: 0 > * [pkg-config libzmq --libs] > -lzmq > * returned: 0 > * [pkg-config libzmq --cflags] > -isystem /usr/include/mit-krb5 -I/usr/include/pgm-5.3 -I/usr/include/libxml2 > * returned: 0 > * INCLUDEPATH += /usr/include/pgm-5.3 > * INCLUDEPATH += /usr/include/libxml2 > * LIBS += -lzmq > -> yes > Checking for cargo >= 1.34.0 ... > * [cargo version] > cargo 1.46.0 > * returned: 0 > * extra += CONFIG += use_cargo > -> yes > Info: creating stash file /<>/.qmake.stash > > Good, your configure finished. Now run /usr/bin/gmake. > > echo "CONFIG += debug" >>conf.pri > # Upstream Cargo.lock contains versions not valid for debian > rm Cargo.lock > # Upstream config.toml references vendored dependencies not part of the > debian package > rm .cargo/config.toml > cargo update > error: failed to select a version for the requirement `base64 = "^0.12"` > candidate versions found which didn't match: 0.13.0 > location searched: directory source `/usr/share/cargo/registry` (which is > replacing registry `https://github.com/rust-lang/crates.io-index`) > required by package `pushpin v1.32.2 (/<>)` > perhaps a crate was updated and forgotten to be re-vendored? > make[1]: *** [debian/rules:37: override_dh_auto_configure] Error 101 The full build log is available from: http://qa-logs.debian.net/2021/10/23/pushpin_1.32.2-1_unstable.log 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.
Bug#997714: trapperkeeper-status-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.junit:junit-bom:pom:debian has not been downloaded from it
Source: trapperkeeper-status-clojure Version: 1.1.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > lein test > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:24: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/trapperkeeper-status-clojure_1.1.1-2_unstable.log 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.
Bug#997716: preprepare: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.
Source: preprepare
Version: 0.9-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 pre_prepare.so pre_prepare.o \
> pre_prepare.bc
> rm -f pre_prepare--0.4.sql
> rm -rf results/ regression.diffs regression.out tmp_check/ tmp_check_iso/
> log/ output_iso/
> make[1]: Leaving directory '/<>'
>dh_clean
>pg_buildext checkcontrol
> --- debian/control2020-10-09 18:07:00.0 +
> +++ debian/control.AtZw8u 2021-10-23 07:39:37.051706134 +
> @@ -10,9 +10,9 @@
> Vcs-Git: https://github.com/dimitri/preprepare.git -b debian
> XS-Testsuite: autopkgtest
>
> -Package: postgresql-13-preprepare
> +Package: postgresql-14-preprepare
> Architecture: any
> -Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-13
> +Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-14
> Description: pre prepare your PostgreSQL statements server side
> The pre_prepare module for PostgreSQL aims to prepare all your statements as
> soon as possible and in a way that allows client queries not to bother at
> all
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is
> required.
> make: *** [debian/rules:10: clean] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/preprepare_0.9-5_unstable.log
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.
Bug#997715: libapache-poi-java: FTBFS: tests failed
Source: libapache-poi-java Version: 4.0.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 -- -Dversion.id=4.0.1 -DDSTAMP=20190121 jar maven-poms javadocs > ant -propertyfile ./debian/ant.properties -Duser.name debian > -Dversion.id=4.0.1 -DDSTAMP=20190121 jar maven-poms javadocs > Buildfile: /<>/build.xml > [propertyreset] Warning: Nashorn engine is planned to be removed from a > future JDK release > [propertyreset] Warning: Nashorn engine is planned to be removed from a > future JDK release >[tstamp] Honouring environment variable SOURCE_DATE_EPOCH which has been > set to 1548110052 > > check-jars: > [mkdir] Created dir: /<>/ooxml-testlib > > fetch-jars: > > check-ooxml-jars: > > fetch-ooxml-jars: > > init: > [mkdir] Created dir: /<>/build > [mkdir] Created dir: /<>/build/classes > [mkdir] Created dir: /<>/build/test-classes > [mkdir] Created dir: /<>/build/test-results > [mkdir] Created dir: /<>/build/scratchpad-classes > [mkdir] Created dir: /<>/build/scratchpad-test-classes > [mkdir] Created dir: /<>/build/scratchpad-test-results > [mkdir] Created dir: /<>/build/geometry-java > [mkdir] Created dir: /<>/build/ooxml-classes > [mkdir] Created dir: /<>/build/ooxml-test-classes > [mkdir] Created dir: /<>/build/ooxml-test-results > [mkdir] Created dir: /<>/build/excelant-classes > [mkdir] Created dir: /<>/build/excelant-test-classes > [mkdir] Created dir: /<>/build/excelant-test-results > [mkdir] Created dir: /<>/build/examples-classes > [mkdir] Created dir: /<>/build/integration-test-classes > [mkdir] Created dir: /<>/build/integration-test-results > [mkdir] Created dir: /<>/build/dist > [mkdir] Created dir: /<>/build/site > [echo] Using Ant: Apache Ant(TM) version 1.10.11 compiled on December 29 > 1969 from /usr/share/ant, Ant detected Java 11 (may be different than actual > Java sometimes...) > [echo] Using Java: > 11.0.13/11.0.13+8-post-Debian-1/11.0.13+8-post-Debian-1/OpenJDK 64-Bit Server > VM from Debian on Linux: 4.19.0-6-cloud-amd64 > [release_tag] Warning: Nashorn engine is planned to be removed from a future > JDK release > > compile-main: > [javac] Compiling 1211 source files to /<>/build/classes > [javac] warning: [options] bootstrap class path not set in conjunction > with -source 8 > [javac] Note: Some input files use or override a deprecated API. > [javac] Note: Recompile with -Xlint:deprecation for details. > [javac] Note: Some input files use unchecked or unsafe operations. > [javac] Note: Recompile with -Xlint:unchecked for details. > [javac] 1 warning > [javac] Creating empty > /<>/build/classes/org/apache/poi/poifs/dev/package-info.class > [javac] Creating empty > /<>/build/classes/org/apache/poi/poifs/common/package-info.class > [javac] Creating empty > /<>/build/classes/org/apache/poi/poifs/filesystem/package-info.class > [javac] Creating empty > /<>/build/classes/org/apache/poi/poifs/storage/package-info.class > [javac] Creating empty > /<>/build/classes/org/apache/poi/poifs/package-info.class > [javac] Creating empty > /<>/build/classes/org/apache/poi/poifs/crypt/package-info.class > [javac] Creating empty > /<>/build/classes/org/apache/poi/poifs/eventfilesystem/package-info.class > [javac] Creating empty > /<>/build/classes/org/apache/poi/poifs/property/package-info.class > [javac] Compiling 538 source files to /<>/build/test-classes > [javac] warning: [options] bootstrap class path not set in conjunction > with -source 8 > [javac] Note: Some input files use or override a deprecated API. > [javac] Note: Recompile with -Xlint:deprecation for details. > [javac] Note: > /<>/src/testcases/org/apache/poi/sl/usermodel/BaseTestSlideShow.java > uses unchecked or unsafe operations. > [javac] Note: Recompile with -Xlint:unchecked for details. > [javac] 1 warning > [copy] Copying 4 files to /<>/build/classes > > check-ooxml-xsds: > > fetch-ooxml-xsds: > > generate-geometry: > > compile-scratchpad: > [javac] Compiling 488 source files to > /<>/build/scratchpad-classes > [javac] warning: [options] bootstrap class path not set in conjunction > with -source 8 > [javac] Note: Some input files use or override a deprecated API. > [javac] Note: Recompile with -Xlint:deprecation for details. > [javac] Note: > /<>/src/scratchpad/src/org/apache/poi/extractor/ole2/OLE2ScratchpadExtractorFactory.java > uses unchecked or unsafe operations. > [javac] Note: Recompile with -Xlint:unchecked for details. > [javac] 1 warning > [javac] Compiling 191 source files to > /<>/build/scratchpad-test-classes > [javac]
Bug#997718: glewlwyd: FTBFS: Module not found: Error: Can't resolve 'cross-fetch' in '/<>/webapp-src/node_modules/i18next-http-backend/cjs'
Source: glewlwyd
Version: 2.5.2-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> # Build webapp
> cp -RL /usr/share/nodejs webapp-src/node_modules || true
> cp -RL /usr/lib/nodejs/* webapp-src/node_modules/ || true
> (cd webapp-src && webpack --config webpack.config.js)
> Hash: a8dcd07a19fb3af83c81
> Version: webpack 4.43.0
> Time: 29020ms
> Built at: 10/23/2021 7:31:30 AM
> 6 assets
> Entrypoint admin = vendors~admin~callback~login~profile.js admin.js
> Entrypoint login = vendors~admin~callback~login~profile.js login.js
> Entrypoint profile = vendors~admin~callback~login~profile.js
> vendors~profile.js profile.js
> Entrypoint callback = vendors~admin~callback~login~profile.js callback.js
> [1] ./node_modules/i18next/dist/esm/i18next.js + 13 modules 98.8 KiB {0}
> [built]
> |14 modules
> [2] ./src/lib/MessageDispatcher.js 1.67 KiB {1} {2} {3} {4} [built]
> [3] ./src/lib/APIManager.js 3.08 KiB {1} {2} {3} {4} [built]
> [4] ./src/lib/Notification.js 7.63 KiB {1} {3} {4} [built]
> [8] ./src/lib/ErrorConfig.js 3.51 KiB {1} {2} {3} {4} [built]
> [9] ./src/Modal/Message.js 5.76 KiB {1} {3} {4} [built]
> [12] (webpack)/buildin/global.js 472 bytes {1} {2} {3} {4} [built]
> [13] ./src/Modal/Confirm.js 5.57 KiB {1} {4} [built]
> [23] ./src/admin.js + 30 modules 1010 KiB {1} [built]
> | ./src/admin.js 2.11 KiB [built]
> | ./src/Admin/App.js 87.2 KiB [built]
> | ./src/Modal/EditRecord.js 48.6 KiB [built]
> | ./src/Admin/Navbar.js 19.6 KiB [built]
> | ./src/Admin/Users.js 18.1 KiB [built]
> | ./src/Admin/Clients.js 15.4 KiB [built]
> | ./src/Admin/Scopes.js 14.6 KiB [built]
> | ./src/Admin/UserMod.js 14.3 KiB [built]
> | ./src/Admin/ClientMod.js 14.4 KiB [built]
> | ./src/Admin/SchemeMod.js 12.5 KiB [built]
> | ./src/Admin/Plugin.js 12.5 KiB [built]
> | ./src/Admin/ScopeEdit.js 22.1 KiB [built]
> | ./src/Admin/ModEdit.js 21.8 KiB [built]
> | ./src/Admin/PluginEdit.js 14.8 KiB [built]
> | ./src/Admin/APIKey.js 14.7 KiB [built]
> | + 16 hidden modules
> [24] ./src/login.js + 20 modules 205 KiB {3} [built]
> | ./src/login.js 2.6 KiB [built]
> | ./src/Login/App.js 30.1 KiB [built]
> | ./src/Login/Buttons.js 19 KiB [built]
> | ./src/Login/Body.js 7.62 KiB [built]
> | ./src/Login/PasswordForm.js 8.47 KiB [built]
> | ./src/Login/NoPasswordForm.js 10.9 KiB [built]
> | ./src/Login/SelectAccount.js 10.8 KiB [built]
> | ./src/Login/EndSession.js 6.32 KiB [built]
> | ./src/Login/SessionClosed.js 4.63 KiB [built]
> | ./src/Login/DeviceAuth.js 8.84 KiB [built]
> | ./src/Login/ResetCredentials.js 10.6 KiB [built]
> | ./src/Login/GrantScope.js 16.7 KiB [built]
> | ./src/Login/scheme/MockSchemeForm.js 9.97 KiB [built]
> | ./src/Login/scheme/EmailSchemeForm.js 8.28 KiB [built]
> | ./src/Login/scheme/WebauthnForm.js 10.1 KiB [built]
> | + 6 hidden modules
> [25] ./src/profile.js + 15 modules 290 KiB {4} [built]
> | ./src/profile.js 2.77 KiB [built]
> | ./src/Profile/App.js 34.4 KiB [built]
> | ./src/Profile/Navbar.js 20.9 KiB [built]
> | ./src/Profile/User.js 31.3 KiB [built]
> | ./src/Profile/UserDelegate.js 4.03 KiB [built]
> | ./src/Profile/UserResetCredentials.js 11.6 KiB [built]
> | ./src/Profile/Register.js 40.5 KiB [built]
> | ./src/Profile/Session.js 18.2 KiB [built]
> | ./src/Profile/Password.js 25.8 KiB [built]
> | ./src/Profile/SchemePage.js 5.86 KiB [built]
> | ./src/Modal/Edit.js 6.42 KiB [built]
> | ./src/Profile/SchemeMock.js 7.72 KiB [built]
> | ./src/Profile/SchemeWebauthn.js 28.6 KiB [built]
> | ./src/Profile/SchemeOTP.js 18.7 KiB [built]
> | ./src/Profile/SchemeCertificate.js 22.2 KiB [built]
> | + 1 hidden module
> [26] ./src/callback.js + 1 modules 14.6 KiB {2} [built]
> | ./src/callback.js 4.07 KiB [built]
> | ./src/Callback/App.js 10.5 KiB [built]
> + 15 hidden modules
>
> ERROR in ./node_modules/i18next-http-backend/cjs/getFetch.js
> Module not found: Error: Can't resolve 'cross-fetch' in
> '/<>/webapp-src/node_modules/i18next-http-backend/cjs'
> @ ./node_modules/i18next-http-backend/cjs/getFetch.js 11:22-44
> @ ./node_modules/i18next-http-backend/cjs/request.js
> @ ./node_modules/i18next-http-backend/cjs/index.js
> @ ./src/admin.js
> make[1]: *** [debian/rules:32: override_dh_auto_build-indep] Error 2
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/glewlwyd_2.5.2-3_unstable.log
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, pl
Bug#997720: wims: FTBFS: configure.ac: error: required file 'config.sub' not found
Source: wims Version: 2:4.22~dfsg1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > cd wims/src; autoreconf && ./configure --without-units --without-chemeq > --without-wimsd CFLAGS="-g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security" > CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" CXXFLAGS="-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security" DFLAGS="-frelease" FCFLAGS="-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong" FFLAGS="-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong" GCJFLAGS="-g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong" > LDFLAGS="-Wl,-z,relro" OBJCFLAGS="-g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security" OBJCXXFLAGS="-g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security" > configure.ac:5: warning: The macro `AC_CONFIG_HEADER' is obsolete. > configure.ac:5: You should run autoupdate. > ./lib/autoconf/status.m4:719: AC_CONFIG_HEADER is expanded from... > configure.ac:5: the top level > configure.ac:39: warning: AC_PROG_LEX without either yywrap or noyywrap is > obsolete > ./lib/autoconf/programs.m4:716: _AC_PROG_LEX is expanded from... > ./lib/autoconf/programs.m4:709: AC_PROG_LEX is expanded from... > configure.ac:39: the top level > configure.ac:74: warning: AC_CHECK_FUNCS($fun): you should use literals > ./lib/autoconf/functions.m4:117: AC_CHECK_FUNCS is expanded from... > configure.ac:74: the top level > configure.ac:83: warning: AC_CHECK_FUNCS($fun): you should use literals > ./lib/autoconf/functions.m4:117: AC_CHECK_FUNCS is expanded from... > configure.ac:83: the top level > configure.ac:93: warning: AC_CHECK_FUNCS($fun): you should use literals > ./lib/autoconf/functions.m4:117: AC_CHECK_FUNCS is expanded from... > configure.ac:93: the top level > configure.ac:98: warning: AC_CHECK_FUNCS($fun): you should use literals > ./lib/autoconf/functions.m4:117: AC_CHECK_FUNCS is expanded from... > configure.ac:98: the top level > configure.ac:109: warning: The macro `AC_HEADER_STDC' is obsolete. > configure.ac:109: You should run autoupdate. > ./lib/autoconf/headers.m4:704: AC_HEADER_STDC is expanded from... > configure.ac:109: the top level > configure.ac:111: warning: The macro `AC_MEMORY_H' is obsolete. > configure.ac:111: You should run autoupdate. > ./lib/autoconf/headers.m4:853: AC_MEMORY_H is expanded from... > configure.ac:111: the top level > configure.ac:122: warning: The macro `AC_HEADER_TIME' is obsolete. > configure.ac:122: You should run autoupdate. > ./lib/autoconf/headers.m4:743: AC_HEADER_TIME is expanded from... > configure.ac:122: the top level > configure.ac:145: warning: The macro `AC_TYPE_SIGNAL' is obsolete. > configure.ac:145: You should run autoupdate. > ./lib/autoconf/types.m4:776: AC_TYPE_SIGNAL is expanded from... > configure.ac:145: the top level > configure.ac: error: required file 'config.sub' not found > configure.ac: error: required file 'config.guess' not found > configure.ac: try running autoreconf --install > make[1]: *** [debian/rules:37: override_dh_auto_configure] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/wims_4.22~dfsg1-2_unstable.log 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.
Bug#997719: libvirt-python: FTBFS: ERROR: failed virDomainGetMessages
Source: libvirt-python
Version: 7.0.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:232: /usr/bin/python3 setup.py build
> running build
> /usr/bin/pkg-config --print-errors --atleast-version=0.9.11 libvirt
> /usr/bin/python3 generator.py libvirt /usr/share/libvirt/api/libvirt-api.xml
> Found 485 functions in /usr/share/libvirt/api/libvirt-api.xml
> Found 0 functions in libvirt-override-api.xml
> Generated 395 wrapper functions
> Missing type converters:
> char ** *:1
> ERROR: failed virDomainGetMessages
> error: command '/usr/bin/python3' failed with exit code 1
> E: pybuild pybuild:354: build: plugin distutils failed with: exit code=1:
> /usr/bin/python3 setup.py build
> dh_auto_build: error: pybuild --build -i python{version} -p 3.9 returned exit
> code 13
> make: *** [debian/rules:12: build] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/libvirt-python_7.0.0-2_unstable.log
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.
Bug#997717: golang-github-twstrike-gotk3adapter: FTBFS: src/github.com/gotk3/gotk3/gtk/accel.go:247:5: val.accel_flags undefined (type _Ctype_struct__GtkAccelKey has no field or method accel_flags)
Source: golang-github-twstrike-gotk3adapter Version: 0.0~git20170505.0.901a95d+ds-3.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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=golang --with=golang >dh_update_autotools_config -O--buildsystem=golang >dh_autoreconf -O--buildsystem=golang >dh_auto_configure -O--buildsystem=golang >dh_auto_build -O--buildsystem=golang > cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 > github.com/twstrike/gotk3adapter/gdk_mock > github.com/twstrike/gotk3adapter/gdka github.com/twstrike/gotk3adapter/gdki > github.com/twstrike/gotk3adapter/glib_mock > github.com/twstrike/gotk3adapter/gliba github.com/twstrike/gotk3adapter/glibi > github.com/twstrike/gotk3adapter/gtk_mock > github.com/twstrike/gotk3adapter/gtka github.com/twstrike/gotk3adapter/gtki > github.com/twstrike/gotk3adapter/pango_mock > github.com/twstrike/gotk3adapter/pangoa > github.com/twstrike/gotk3adapter/pangoi > internal/unsafeheader > github.com/twstrike/gotk3adapter/glibi > internal/abi > internal/cpu > internal/goexperiment > runtime/internal/atomic > github.com/twstrike/gotk3adapter/gdki > github.com/twstrike/gotk3adapter/glib_mock > internal/bytealg > runtime/internal/sys > internal/itoa > github.com/twstrike/gotk3adapter/gdk_mock > runtime/internal/math > math/bits > unicode/utf8 > internal/race > sync/atomic > math > unicode > runtime > github.com/twstrike/gotk3adapter/gtki > github.com/twstrike/gotk3adapter/pangoi > github.com/twstrike/gotk3adapter/pango_mock > github.com/twstrike/gotk3adapter/gtk_mock > internal/reflectlite > sync > internal/testlog > runtime/cgo > errors > sort > io > strconv > internal/oserror > syscall > path > reflect > time > internal/syscall/unix > internal/syscall/execenv > io/fs > internal/poll > internal/fmtsort > os > fmt > github.com/gotk3/gotk3/glib > # github.com/gotk3/gotk3/glib > cgo-gcc-prolog: In function ‘_cgo_734360ee47f5_Cfunc_g_binding_get_source’: > cgo-gcc-prolog:71:2: warning: ‘g_binding_get_source’ is deprecated: Use > 'g_binding_dup_source' instead [-Wdeprecated-declarations] > In file included from /usr/include/glib-2.0/glib-object.h:22, > from /usr/include/glib-2.0/gio/gioenums.h:28, > from /usr/include/glib-2.0/gio/giotypes.h:28, > from /usr/include/glib-2.0/gio/gio.h:26, > from src/github.com/gotk3/gotk3/glib/gbinding.go:4: > /usr/include/glib-2.0/gobject/gbinding.h:113:23: note: declared here > 113 | GObject * g_binding_get_source (GBinding > *binding); > | ^~~~ > cgo-gcc-prolog: In function ‘_cgo_734360ee47f5_Cfunc_g_binding_get_target’: > cgo-gcc-prolog:107:2: warning: ‘g_binding_get_target’ is deprecated: Use > 'g_binding_dup_target' instead [-Wdeprecated-declarations] > In file included from /usr/include/glib-2.0/glib-object.h:22, > from /usr/include/glib-2.0/gio/gioenums.h:28, > from /usr/include/glib-2.0/gio/giotypes.h:28, > from /usr/include/glib-2.0/gio/gio.h:26, > from src/github.com/gotk3/gotk3/glib/gbinding.go:4: > /usr/include/glib-2.0/gobject/gbinding.h:117:23: note: declared here > 117 | GObject * g_binding_get_target (GBinding > *binding); > | ^~~~ > github.com/twstrike/gotk3adapter/gliba > github.com/gotk3/gotk3/cairo > github.com/gotk3/gotk3/gdk > github.com/gotk3/gotk3/pango > github.com/twstrike/gotk3adapter/pangoa > # github.com/gotk3/gotk3/gdk > cgo-gcc-prolog: In function ‘_cgo_f31c63d07257_Cfunc_gdk_device_grab’: > cgo-gcc-prolog:285:2: warning: ‘gdk_device_grab’ is deprecated: Use > 'gdk_seat_grab' instead [-Wdeprecated-declarations] > In file included from /usr/include/gtk-3.0/gdk/gdkdnd.h:33, > from /usr/include/gtk-3.0/gdk/gdkevents.h:34, > from /usr/include/gtk-3.0/gdk/gdkdisplay.h:31, > from /usr/include/gtk-3.0/gdk/gdkscreen.h:32, > from /usr/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31, > from /usr/include/gtk-3.0/gdk/gdk.h:32, > from src/github.com/gotk3/gotk3/gdk/gdk.go:21: > /usr/include/gtk-3.0/gdk/gdkdevice.h:230:15: note: declared here > 230 | GdkGrabStatus gdk_device_grab(GdkDevice*device, > | ^~~ > cgo-gcc-prolog: In function > ‘_cgo_f31c63d07257_Cfunc_gdk_device_manager_get_client_pointer’: > cgo-gcc-prolog:303:2: warning: ‘gdk_device_manager_get_client_pointer’ is > deprecated [-Wdeprecated-declarations] > In file included from /usr/include/gtk-3.0/gdk/gdkdisplay.h:32, > from /usr/include/gtk-3.0/gdk/gdkscreen.h:32, > from /usr/inc
Bug#997721: postgresql-semver: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.
Source: postgresql-semver
Version: 0.31.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package postgresql-semver
> dpkg-buildpackage: info: source version 0.31.1-3
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Felix Lechner
>
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> pg_buildext checkcontrol
> --- debian/control2021-09-27 20:01:37.0 +
> +++ debian/control.ZO45zn 2021-10-23 06:29:04.950729454 +
> @@ -11,9 +11,9 @@
> Vcs-Git: https://salsa.debian.org/lechner/postgresql-semver.git
> Homepage: https://pgxn.org/dist/semver/doc/semver.html
>
> -Package: postgresql-13-semver
> +Package: postgresql-14-semver
> Architecture: any
> -Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-13
> +Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-14
> Description: Semantic version number type for PostgreSQL
> This library contains a single PostgreSQL extension for a data type
> called 'semver'. It implements the version number format described
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is
> required.
> make: *** [/usr/share/postgresql-common/pgxs_debian_control.mk:9:
> debian/control] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/postgresql-semver_0.31.1-3_unstable.log
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.
Bug#997724: leaflet: FTBFS: Error: Cannot find module 'js-yaml'
Source: leaflet
Version: 1.7.1~dfsg-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> eslint --format tap --no-eslintrc --global L --env commonjs,amd,node
> --parser-options '{ "ecmaVersion": 6, "sourceType": "module" }' --rule '{
> "linebreak-style": [ 0, "unix" ], "no-mixed-spaces-and-tabs": [ 2,
> "smart-tabs" ], "indent": [ 2, "tab", { "VariableDeclarator": 0,
> "flatTernaryExpressions": true } ], "curly": 2, "spaced-comment": 2,
> "strict": 0, "wrap-iife": 0, "key-spacing": 0, "consistent-return": 0,
> "no-unused-expressions": [ "error", { "allowShortCircuit": true } ] }' src
> spec/suites docs/docs/js
> There was a problem loading formatter: ./formatters/tap
> Error: Cannot find module 'js-yaml'
> Require stack:
> - /usr/share/nodejs/eslint/lib/formatters/tap.js
> - /usr/share/nodejs/eslint/lib/cli-engine.js
> - /usr/share/nodejs/eslint/lib/cli.js
> - /usr/share/nodejs/eslint/bin/eslint.js
> make[1]: *** [debian/rules:33: override_dh_auto_test] Error 2
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/leaflet_1.7.1~dfsg-2_unstable.log
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.
Bug#997722: pg-partman: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.
Source: pg-partman
Version: 4.5.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 src/pg_partman_bgw.so src/pg_partman_bgw.o \
> src/pg_partman_bgw.bc
> rm -rf sql/pg_partman--4.5.1.sql
> make[1]: Leaving directory '/<>'
>dh_clean
>pg_buildext checkcontrol
> --- debian/control2021-02-04 15:59:40.0 +
> +++ debian/control.ffLqBs 2021-10-23 07:39:15.041961159 +
> @@ -14,10 +14,10 @@
> Vcs-Git: https://salsa.debian.org/postgresql/pg-partman.git
> Homepage: https://github.com/pgpartman/pg_partman
>
> -Package: postgresql-13-partman
> +Package: postgresql-14-partman
> Architecture: any
> Depends:
> - postgresql-13,
> + postgresql-14,
> python3,
> python3-psycopg2,
> ${misc:Depends},
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is
> required.
> make: *** [debian/rules:11: clean] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pg-partman_4.5.1-1_unstable.log
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.
Bug#997725: node-agent-base: FTBFS: test/test.ts(253,18): error TS2571: Object is of type 'unknown'.
Source: node-agent-base Version: 6.0.2+~cs5.4.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > tsc > test/test.ts(253,18): error TS2571: Object is of type 'unknown'. > test/test.ts(280,18): error TS2571: Object is of type 'unknown'. > make[1]: *** [debian/rules:7: override_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2021/10/23/node-agent-base_6.0.2+~cs5.4.1-2_unstable.log 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.
Bug#997723: node-cosmiconfig: FTBFS: Object is of type 'unknown'.
Source: node-cosmiconfig
Version: 7.0.0+ds1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> babeljs-7 src -d dist --verbose --extensions .js,.ts --ignore
> '**/**/*.test.js,**/**/*.test.ts' --source-maps
> src/Explorer.ts -> dist/Explorer.js
> src/ExplorerBase.ts -> dist/ExplorerBase.js
> src/ExplorerSync.ts -> dist/ExplorerSync.js
> src/cacheWrapper.ts -> dist/cacheWrapper.js
> src/getDirectory.ts -> dist/getDirectory.js
> src/getPropertyByPath.ts -> dist/getPropertyByPath.js
> src/index.ts -> dist/index.js
> src/loaders.ts -> dist/loaders.js
> src/readFile.ts -> dist/readFile.js
> src/types.ts -> dist/types.js
> Successfully compiled 10 files with Babel (676ms).
> tsc --project tsconfig.types.json
> [96msrc/loaders.ts[0m:[93m29[0m:[93m5[0m - [91merror[0m[90m TS2571:
> [0mObject is of type 'unknown'.
>
> [7m29[0m error.message = `JSON Error in ${filepath}:\n${error.message}`;
> [7m [0m [91m~[0m
>
> [96msrc/loaders.ts[0m:[93m29[0m:[93m52[0m - [91merror[0m[90m TS2571:
> [0mObject is of type 'unknown'.
>
> [7m29[0m error.message = `JSON Error in ${filepath}:\n${error.message}`;
> [7m [0m [91m ~[0m
>
> [96msrc/loaders.ts[0m:[93m44[0m:[93m5[0m - [91merror[0m[90m TS2571:
> [0mObject is of type 'unknown'.
>
> [7m44[0m error.message = `YAML Error in ${filepath}:\n${error.message}`;
> [7m [0m [91m~[0m
>
> [96msrc/loaders.ts[0m:[93m44[0m:[93m52[0m - [91merror[0m[90m TS2571:
> [0mObject is of type 'unknown'.
>
> [7m44[0m error.message = `YAML Error in ${filepath}:\n${error.message}`;
> [7m [0m [91m ~[0m
>
> [96msrc/readFile.ts[0m:[93m34[0m:[93m36[0m - [91merror[0m[90m
> TS2571: [0mObject is of type 'unknown'.
>
> [7m34[0m if (throwNotFound === false && error.code === 'ENOENT') {
> [7m [0m [91m ~[0m
>
> [96msrc/readFile.ts[0m:[93m50[0m:[93m36[0m - [91merror[0m[90m
> TS2571: [0mObject is of type 'unknown'.
>
> [7m50[0m if (throwNotFound === false && error.code === 'ENOENT') {
> [7m [0m [91m ~[0m
>
>
> Found 6 errors.
>
> make[1]: *** [debian/rules:14: override_dh_auto_build] Error 2
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/node-cosmiconfig_7.0.0+ds1-1_unstable.log
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.
Bug#997726: rainloop: FTBFS: Error: File not found with singular glob: /usr/lib/nodejs/pikaday/css/pikaday.css (if this was purposeful, use `allowEmpty` option)
Source: rainloop Version: 1.14.0-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > gulp rainloop > [07:30:51] Local modules not found in /<> > [07:30:51] Try running: npm install > [07:30:51] Using globally installed gulp > [07:30:52] Using gulpfile /<>/gulpfile.js > [07:30:52] Starting 'rainloop'... > [07:30:52] Starting ''... > [07:30:52] Finished '' after 3.11 ms > [07:30:52] Starting 'assetsCopy'... > [07:30:52] Finished 'assetsCopy' after 63 ms > [07:30:52] Starting 'jsClean'... > [07:30:52] Starting 'cssClean'... > [07:30:52] Starting 'momentLocalesClear'... > [07:30:52] Starting 'ckeditorClear'... > [07:30:52] Starting 'fontasticFontsClear'... > [07:30:52] Starting 'lightgalleryFontsClear'... > [07:30:52] Finished 'ckeditorClear' after 2.56 ms > [07:30:52] Starting 'ckeditorCopyPlugins'... > [07:30:52] Finished 'jsClean' after 7.02 ms > [07:30:52] Starting ''... > [07:30:52] Finished 'cssClean' after 108 ms > [07:30:52] Starting 'cssMainBuild'... > [07:30:52] Starting 'cssSocialBuild'... > [07:30:52] Finished 'momentLocalesClear' after 116 ms > [07:30:52] Starting 'momentLocales'... > [07:30:52] Finished 'fontasticFontsClear' after 118 ms > [07:30:52] Starting 'fontasticFontsCopy'... > [07:30:52] Finished 'lightgalleryFontsClear' after 118 ms > [07:30:52] Starting 'lightgalleryFontsCopy'... > [07:30:52] 'cssMainBuild' errored after 19 ms > [07:30:52] Error: File not found with singular glob: > /usr/lib/nodejs/pikaday/css/pikaday.css (if this was purposeful, use > `allowEmpty` option) > at Glob. (/usr/share/nodejs/glob-stream/readable.js:84:17) > at Object.onceWrapper (events.js:421:26) > at Glob.emit (events.js:314:20) > at Glob.EventEmitter.emit (domain.js:483:12) > at Glob._finish (/usr/share/nodejs/glob/glob.js:195:8) > at done (/usr/share/nodejs/glob/glob.js:180:14) > at Glob._processSimple2 (/usr/share/nodejs/glob/glob.js:686:12) > at /usr/share/nodejs/glob/glob.js:674:10 > at Glob._stat2 (/usr/share/nodejs/glob/glob.js:770:12) > at lstatcb_ (/usr/share/nodejs/glob/glob.js:762:12) > [07:30:52] 'rainloop' errored after 197 ms > [07:30:52] The following tasks did not complete: , , > , , , , ckeditorCopyPlugins, , > cssSocialBuild, momentLocales, fontasticFontsCopy, lightgalleryFontsCopy > [07:30:52] Did you forget to signal async completion? > make[1]: *** [debian/rules:10: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/rainloop_1.14.0-3_unstable.log 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.
Bug#997727: rdma-core: FTBFS: dh_installsystemd: error: Package 'ibacm' does not install unit 'ibacm.service'.
Source: rdma-core Version: 36.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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_installinit -prdma-core --onlyscripts --name=iwpmd > dh_installinit --remaining-packages > make[1]: Leaving directory '/<>' >debian/rules override_dh_installsystemd > make[1]: Entering directory '/<>' > dh_installsystemd -pibacm --no-start ibacm.service > dh_installsystemd: error: Package 'ibacm' does not install unit > 'ibacm.service'. > make[1]: *** [debian/rules:92: override_dh_installsystemd] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/10/23/rdma-core_36.0-1_unstable.log 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.
Bug#997728: libgnatcoll-db: FTBFS: raised CONSTRAINT_ERROR : uintp.adb:2002 overflow check failed
Source: libgnatcoll-db Version: 21.0.0-6 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 xref/generated/* > ADA_PROJECT_PATH=sql:sqlite:postgres:xref gprbuild -p -j4 -R -v -eS > -Xgnatcoll_sql_version="3" -Xgnatcoll_sqlite_version="20" > -Xgnatcoll_postgres_version="1" -Xgnatcoll_xref_version="20" > -XGNATCOLL_SQLITE="external" gnatcoll_db2ada/gnatcoll_all2ada.gpr > -XLIBRARY_TYPE=relocatable > object directory "/<>/sql/obj/relocatable" created for project > GnatColl_SQL > library directory "/<>/sql/lib/relocatable" created for project > GnatColl_SQL > object directory "/<>/sqlite/obj/relocatable" created for > project GnatColl_Sqlite > library directory "/<>/sqlite/lib/relocatable" created for > project GnatColl_Sqlite > object directory "/<>/postgres/obj/relocatable" created for > project GnatColl_Postgres > library directory "/<>/postgres/lib/relocatable" created for > project GnatColl_Postgres > object directory "/<>/gnatcoll_db2ada/obj" created for project > Gnatcoll_All2ada > Changing to object directory of "Gnatcoll_All2ada": > "/<>/gnatcoll_db2ada/obj/" > /usr/bin/gnatgcc -c -x ada -gnatA -O2 -gnatn -gnatwaCJ -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -gnatec=/tmp/GNAT-TEMP-03.TMP -gnatem=/tmp/GNAT-TEMP-04.TMP > /<>/gnatcoll_db2ada/gnatcoll_all2ada.adb > Changing to object directory of "GnatColl_Postgres": > "/<>/postgres/obj/relocatable/" > /usr/bin/gcc -c -x c -DHAS_PQPREPARE -O2 -Wunreachable-code -Wdate-time > -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -fPIC -MMD -MF > postgres_support.d -specs=/tmp/GNAT-TEMP-06.TMP > /<>/postgres/postgres_support.c > /usr/bin/gnatgcc -c -x ada -gnatA -O2 -gnatn -gnatwaCJ -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -fPIC > -gnatec=/tmp/GNAT-TEMP-07.TMP -gnatem=/tmp/GNAT-TEMP-08.TMP > /<>/postgres/gnatcoll-sql-ranges.adb > /usr/bin/gnatgcc -c -x ada -gnatA -O2 -gnatn -gnatwaCJ -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -fPIC > -gnatec=/tmp/GNAT-TEMP-07.TMP -gnatem=/tmp/GNAT-TEMP-09.TMP > /<>/postgres/gnatcoll-sql-postgres.adb > Changing to object directory of "GnatColl_Sqlite": > "/<>/sqlite/obj/relocatable/" > /usr/bin/gnatgcc -c -x ada -gnatA -O2 -gnatn -gnatwaCJ -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -fPIC > -gnatec=/tmp/GNAT-TEMP-10.TMP -gnatem=/tmp/GNAT-TEMP-11.TMP > /<>/sqlite/gnatcoll-sql-sqlite-builder.adb > /usr/bin/gnatgcc -c -x ada -gnatA -O2 -gnatn -gnatwaCJ -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -fPIC > -gnatec=/tmp/GNAT-TEMP-10.TMP -gnatem=/tmp/GNAT-TEMP-12.TMP > /<>/sqlite/gnatcoll-sql-sqlite.adb > /usr/bin/gnatgcc -c -x ada -gnatA -O2 -gnatn -gnatwaCJ -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -fPIC > -gnatec=/tmp/GNAT-TEMP-10.TMP -gnatem=/tmp/GNAT-TEMP-13.TMP > /<>/sqlite/gnatcoll-sql-sqlite-gnade.adb > Changing to object directory of "GnatColl_SQL": > "/<>/sql/obj/relocatable/" > /usr/bin/gnatgcc -c -x ada -gnatA -O2 -gnatn -gnatwaCJ -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -fPIC > -gnatec=/tmp/GNAT-TEMP-14.TMP -gnatem=/tmp/GNAT-TEMP-15.TMP > /<>/sql/gnatcoll-sql-exec.adb > /usr/bin/gnatgcc -c -x ada -gnatA -O2 -gnatn -gnatwaCJ -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -fPIC > -gnatec=/tmp/GNAT-TEMP-14.TMP -gnatem=/tmp/GNAT-TEMP-16.TMP > /<>/sql/gnatcoll-sql-inspect.adb > /usr/bin/gnatgcc -c -x ada -gnatA -O2 -gnatn -gnatwaCJ -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -fPIC > -gnatec=/tmp/GNAT-TEMP-14.TMP -gnatem=/tmp/GNAT-TEMP-17.TMP > /<>/sql/gnatcoll-sql-exec_private.adb > /usr/bin/gnatgcc -c -x ada -gnatA -O2 -gnatn -gnatwaCJ -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -fPIC > -gnatec=/tmp/GNAT-TEMP-14.TMP -gnatem=/tmp/GNAT-TEMP-17.TMP > /<>/sql/gnatcoll-sql-exec-tasking.adb > /usr/bin/gnatgcc -c -x ada -gnatA -O2 -gnatn -gnatwaCJ -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -fPIC > -gnatec=/tmp/GNAT-TEMP-14.TMP -gnatem=/tmp/GNAT-TEMP-17.TMP > /<>/sql/gnatcoll-sql-sessions.adb > /usr/bin/gnatgcc -c -x ada -gnatA -O2 -gnatn -gnatwaCJ -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -fPIC > -gnatec=/tmp/GNAT-TEMP-14.TMP -gnatem=/tmp/GNAT-TEMP-18.TMP > /<>/sql/gnatcoll-sql_impl.adb > /usr/bin/gnatgcc -c -x ada -gnatA -O2 -gnatn -gnatwaCJ -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -fPIC > -gnatec=/tmp/GNAT-TEMP-14.TMP -gnatem=/tmp/GNAT-TEMP-15.TMP > /<>/sql/gnatcoll-sql.adb > /usr/bin/gnatgcc -c -x ada -gnatA -O2 -gnatn -gnatwaCJ -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong
Bug#997730: plr: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.
Source: plr
Version: 1:8.4.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 plr.so libplr.a libplr.pc
> rm -f plr.o pg_conversion.o pg_backend_support.o pg_userfuncs.o pg_rsupport.o
> plr.bc pg_conversion.bc pg_backend_support.bc pg_userfuncs.bc pg_rsupport.bc
> rm -rf results/ regression.diffs regression.out tmp_check/ tmp_check_iso/
> log/ output_iso/
> make[1]: Leaving directory '/<>'
>dh_clean
>pg_buildext checkcontrol
> --- debian/control2021-06-30 12:32:40.0 +
> +++ debian/control.o8DjmV 2021-10-23 07:38:02.658684327 +
> @@ -11,9 +11,9 @@
> Vcs-Browser: https://salsa.debian.org/postgresql/plr
> Vcs-Git: https://salsa.debian.org/postgresql/plr.git
>
> -Package: postgresql-13-plr
> +Package: postgresql-14-plr
> Architecture: any
> -Depends: r-base-core (>= 2.10), postgresql-13, ${shlibs:Depends},
> ${misc:Depends}
> +Depends: r-base-core (>= 2.10), postgresql-14, ${shlibs:Depends},
> ${misc:Depends}
> Suggests: r-recommended
> Provides: postgresql-plr
> Description: Procedural language interface between PostgreSQL and R
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is
> required.
> make: *** [debian/rules:10: clean] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/plr_8.4.3-1_unstable.log
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.
Bug#997729: ghdl: FTBFS: Unhandled version llvm 11.1.0
Source: ghdl Version: 1.0.0+dfsg-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>/builddir/mcode' > for d in ieee/v87 ieee/v93 ieee/v08 std/v87 std/v93 std/v08 src/ieee > src/ieee/v87 src/ieee/v93 src/ieee2008 src/std src/std/v87 src/std/v93 > src/std/v08 src/synopsys src/synopsys/v08 src/upf; do \ > mkdir -p lib/ghdl/mcode/$d; \ > done > make[2]: Leaving directory '/<>/builddir/mcode' > Generate ortho_code-x86-flags.ads > Generate elf_arch.ads > Generate ghdlsynth_maybe.ads > Generate default_paths.ads > > > Configuring with llvm backend > > if [ -n "1" ]; then \ > cd /<>/builddir/llvm; \ > ../../configure --srcdir=../.. --prefix=/usr \ > --libdir=lib/ghdl/llvm --incdir=lib/ghdl/include \ > --disable-libghdl --enable-gplcompat \ > --with-llvm-config; \ > fi > Build machine is: x86_64-linux-gnu > Unhandled version llvm 11.1.0 > make[1]: *** [debian/rules:77: override_dh_auto_configure] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/ghdl_1.0.0+dfsg-4_unstable.log 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.
Bug#997731: trapperkeeper-webserver-jetty9-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.junit:junit-bom:pom:debian has not been download
Source: trapperkeeper-webserver-jetty9-clojure Version: 4.1.0-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > lein pom debian/pom.xml > Wrote /<>/debian/pom.xml > lein i18n make > Running 'make i18n' > lein jar > Warning: specified :main without including it in :aot. > Implicit AOT of :main will be removed in Leiningen 3.0.0. > If you only need AOT for your uberjar, consider adding :aot :all into your > :uberjar profile instead. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/trapperkeeper-webserver-jetty9-clojure_4.1.0-4_unstable.log 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.
Bug#997732: libcxx-serial: FTBFS: dh_missing: error: missing files, aborting
Source: libcxx-serial
Version: 1.2.1-4.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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_missing --fail-missing
> dh_missing: warning:
> usr/lib/x86_64-linux-gnu/cmake/cxx-serial/cxx-serialConfig-version.cmake
> exists in debian/tmp but is not installed to anywhere
> dh_missing: warning:
> usr/lib/x86_64-linux-gnu/cmake/cxx-serial/cxx-serialConfig.cmake exists in
> debian/tmp but is not installed to anywhere
> dh_missing: warning: usr/lib/x86_64-linux-gnu/pkgconfig/cxx-serial.pc exists
> in debian/tmp but is not installed to anywhere
> dh_missing: error: missing files, aborting
> The following debhelper tools have reported what they installed (with
> files per package)
>* dh_install: libcxx-serial-dev (3), libcxx-serial1 (2)
>* dh_installdocs: libcxx-serial-dev (3), libcxx-serial1 (0)
> If the missing files are installed by another tool, please file a bug
> against it.
> When filing the report, if the tool is not part of debhelper itself,
> please reference the
> "Logging helpers and dh_missing" section from the "PROGRAMMING" guide
> for debhelper (10.6.3+).
> (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
> Be sure to test with dpkg-buildpackage -A/-B as the results may vary
> when only a subset is built
> If the omission is intentional or no other helper can take care of this
> consider adding the
> paths to debian/not-installed.
>
> Remember to be careful with paths containing "x86_64-linux-gnu", where
> you might need to
> use a wildcard or (assuming compat 13+) e.g. ${DEB_HOST_MULTIARCH} in
> debian/not-installed
> to ensure it works on all architectures (see #961104).
> make[1]: *** [debian/rules:20: override_dh_missing] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/libcxx-serial_1.2.1-4.1_unstable.log
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.
Bug#997733: pycryptodome: FTBFS: There is a syntax error in your configuration file: Missing parentheses in call to 'print'. Did you mean print(sys.path)? (conf.py, line 18)
Source: pycryptodome Version: 3.9.7+dfsg1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > PYTHONPATH=. python3 -m sphinx -N -bhtml Doc/ build/html # HTML generator > Running Sphinx v4.2.0 > > Configuration error: > There is a syntax error in your configuration file: Missing parentheses in > call to 'print'. Did you mean print(sys.path)? (conf.py, line 18) > > make[1]: *** [debian/rules:26: execute_after_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2021/10/23/pycryptodome_3.9.7+dfsg1-1_unstable.log 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.
Bug#997735: pg-fact-loader: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.
Source: pg-fact-loader
Version: 1.6.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 pg_fact_loader.so pg_fact_loader.o \
> pg_fact_loader.bc
> rm -rf results/ regression.diffs regression.out tmp_check/ tmp_check_iso/
> log/ output_iso/
> make[1]: Leaving directory '/<>'
>dh_clean
>pg_buildext checkcontrol
> --- debian/control2020-12-10 16:37:58.0 +
> +++ debian/control.hekcaQ 2021-10-23 06:28:09.225523068 +
> @@ -8,8 +8,8 @@
> Homepage: https://github.com/enova/pg_fact_loader
> Vcs-Git: https://github.com/enova/pg_fact_loader.git
>
> -Package: postgresql-13-pg-fact-loader
> +Package: postgresql-14-pg-fact-loader
> Architecture: any
> -Depends: postgresql-13, ${shlibs:Depends}, ${misc:Depends}
> +Depends: postgresql-14, ${shlibs:Depends}, ${misc:Depends}
> Description: Build fact tables asynchronously with Postgres
> - Use queue tables to build fact tables asynchronously for PostgreSQL 13.
> + Use queue tables to build fact tables asynchronously for PostgreSQL 14.
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is
> required.
> make: *** [debian/rules:10: clean] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pg-fact-loader_1.6.0-4_unstable.log
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.
Bug#997736: moment-timezone.js: FTBFS: grep -q '^# version 2021a$' /usr/share/zoneinfo/tzdata.zi => fails
Source: moment-timezone.js Version: 0.5.32+dfsg1-2+2021a Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 data/packed/2021a.json data/unpacked/2021a.json data/meta/2021a.json > rm -rf temp/ > make[1]: Leaving directory '/<>' >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building moment-timezone.js using existing > ./moment-timezone.js_0.5.32+dfsg1.orig.tar.xz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building moment-timezone.js in > moment-timezone.js_0.5.32+dfsg1-2+2021a.debian.tar.xz > dpkg-source: info: building moment-timezone.js in > moment-timezone.js_0.5.32+dfsg1-2+2021a.dsc > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs >debian/rules override_dh_auto_build > make[1]: Entering directory '/<>' > # Fail the build if the tzdata package does not match TZVER. > grep -q '^# version 2021a$' /usr/share/zoneinfo/tzdata.zi > make[1]: *** [debian/rules:12: data/meta/2021a.json] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/moment-timezone.js_0.5.32+dfsg1-2+2021a_unstable.log 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.
Bug#997734: trapperkeeper-authorization-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.junit:junit-bom:pom:debian has not been downloaded
Source: trapperkeeper-authorization-clojure Version: 1.0.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > lein test > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:25: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/trapperkeeper-authorization-clojure_1.0.0-2_unstable.log 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.
Bug#997737: Volume changes sometimes have wrong icon
Package: gnome-shell Version: 41.0-2 Severity: normal X-Debbugs-Cc: j...@joshtriplett.org [I don't know which component is responsible for the UI for changing volume/brightness/etc; I guessed gnome-shell, but I don't know if it's that, gnome-settings-daemon, or something else.] Several times lately I've changed audio volume with the volume hotkeys, and the UI popped up with the wrong icon: instead of volume, it shows the brightness icon, or the microphone icon, or similar. The hotkeys still change the audio volume; it's just an issue with the UI icon. Whenever this happens, it continues to happen as long as I hit the volume hotkeys. Even if I wait and let the UI disappear, and then hit the volume hotkeys again, the UI will come back up with the wrong icon. But as soon as I hit a different hotkey that uses a different icon (e.g. mic mute or brightness), the next time I use the volume keys they'll have the right icon again. I managed to capture a screenshot (attached) from using the volume hotkeys and seeing the brightness icon. - Josh Triplett -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: arm64 Kernel: Linux 5.14.0-3-amd64 (SMP w/8 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-2 ii evolution-data-server3.42.0-2 ii gir1.2-accountsservice-1.0 0.6.55-3 ii gir1.2-atk-1.0 2.36.0-2 ii gir1.2-atspi-2.0 2.42.0-1 ii gir1.2-gcr-3 3.40.0-3+b1 ii gir1.2-gdesktopenums-3.0 41.0-1 ii gir1.2-gdkpixbuf-2.0 2.42.6+dfsg-2 ii gir1.2-gdm-1.0 41.0-2 ii gir1.2-geoclue-2.0 2.5.7-3 ii gir1.2-glib-2.0 1.70.0-2 ii gir1.2-gnomebluetooth-1.03.34.5-4 ii gir1.2-gnomedesktop-3.0 41.0-1 ii gir1.2-graphene-1.0 1.10.6+dfsg1-2 ii gir1.2-gstreamer-1.0 1.18.5-1 ii gir1.2-gtk-3.0 3.24.30-3 ii gir1.2-gtk-4.0 4.4.0+ds1-5 ii gir1.2-gweather-3.0 40.0-4 ii gir1.2-ibus-1.0 1.5.25-2 ii gir1.2-mutter-9 41.0-5 ii gir1.2-nm-1.01.32.12-1 ii gir1.2-nma-1.0 1.8.32-1 ii gir1.2-pango-1.0 1.48.10+ds1-1 ii gir1.2-polkit-1.00.105-31 ii gir1.2-rsvg-2.0 2.50.7+dfsg-2 ii gir1.2-soup-2.4 2.74.0-2 ii gir1.2-upowerglib-1.00.99.13-1 ii gir1.2-webkit2-4.0 2.34.1-1 ii gjs 1.70.0-3 ii gnome-backgrounds41.0-1 ii gnome-settings-daemon41.0-2 ii gnome-shell-common 41.0-2 ii gsettings-desktop-schemas41.0-1 ii gstreamer1.0-pipewire0.3.39-1 ii libatk-bridge2.0-0 2.38.0-2 ii libatk1.0-0 2.36.0-2 ii libc62.32-4 ii libcairo21.16.0-5 ii libecal-2.0-13.42.0-2 ii libedataserver-1.2-263.42.0-2 ii libgcr-base-3-1 3.40.0-3+b1 ii libgdk-pixbuf-2.0-0 2.42.6+dfsg-2 ii libgirepository-1.0-11.70.0-2 ii libgjs0g 1.70.0-3 ii libgles2 1.3.4-2+b1 ii libglib2.0-0 2.70.0-1+b1 ii libglib2.0-bin 2.70.0-1+b1 ii libgnome-autoar-0-0 0.4.0-1 ii libgnome-desktop-3-1941.0-1 ii libgraphene-1.0-01.10.6+dfsg1-2 ii libgtk-3-0 3.24.30-3 ii libgtk-4-1 4.4.0+ds1-5 ii libical3 3.0.11-2 ii libjson-glib-1.0-0 1.6.6-1 ii libmutter-9-041.0-5 ii libnm0 1.32.12-1 ii libpango-1.0-0 1.48.10+ds1-1 ii libpangocairo-1.0-0 1.48.10+ds1-1 ii libpolkit-age
Bug#997739: plplot: FTBFS: make[3]: *** [bindings/qt_gui/pyqt5/CMakeFiles/generate_pyqt5_source.dir/build.make:76: bindings/qt_gui/pyqt5/sipAPIplplot_pyqt5.h] Error 1
Source: plplot Version: 5.15.0+dfsg-22 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > cd /<>/obj-x86_64-linux-gnu/examples/python && /usr/bin/cmake -E > copy /<>/examples/python/x00 > /<>/obj-x86_64-linux-gnu/examples/python > cd /<>/obj-x86_64-linux-gnu/examples/lua && /usr/bin/cmake -E > copy /<>/examples/lua/x04.lua > /<>/obj-x86_64-linux-gnu/examples/lua > cd /<>/obj-x86_64-linux-gnu/examples/python && /usr/bin/cmake -E > copy /<>/examples/python/x01 > /<>/obj-x86_64-linux-gnu/examples/python > cd /<>/obj-x86_64-linux-gnu/examples/python && /usr/bin/cmake -E > copy /<>/examples/python/x02 > /<>/obj-x86_64-linux-gnu/examples/python > cd /<>/obj-x86_64-linux-gnu/examples/lua && /usr/bin/cmake -E > copy /<>/examples/lua/x05.lua > /<>/obj-x86_64-linux-gnu/examples/lua > cd /<>/obj-x86_64-linux-gnu/examples/python && /usr/bin/cmake -E > copy /<>/examples/python/x03 > /<>/obj-x86_64-linux-gnu/examples/python > cd /<>/obj-x86_64-linux-gnu/examples/lua && /usr/bin/cmake -E > copy /<>/examples/lua/x06.lua > /<>/obj-x86_64-linux-gnu/examples/lua > cd /<>/obj-x86_64-linux-gnu/examples/python && /usr/bin/cmake -E > copy /<>/examples/python/x04 > /<>/obj-x86_64-linux-gnu/examples/python > Querying qmake about your Qt installation... > cd /<>/obj-x86_64-linux-gnu/examples/lua && /usr/bin/cmake -E > copy /<>/examples/lua/x07.lua > /<>/obj-x86_64-linux-gnu/examples/lua > cd /<>/obj-x86_64-linux-gnu/examples/python && /usr/bin/cmake -E > copy /<>/examples/python/x05 > /<>/obj-x86_64-linux-gnu/examples/python > These bindings will be built: plplot. > Generating the plplot bindings... > sip-build: Unable to find file "QtCore/QtCoremod.sip" > > cd /<>/obj-x86_64-linux-gnu/examples/lua && /usr/bin/cmake -E > copy /<>/examples/lua/x08.lua > /<>/obj-x86_64-linux-gnu/examples/lua > cd /<>/obj-x86_64-linux-gnu/examples/python && /usr/bin/cmake -E > copy /<>/examples/python/x06 > /<>/obj-x86_64-linux-gnu/examples/python > cd /<>/obj-x86_64-linux-gnu/examples/lua && /usr/bin/cmake -E > copy /<>/examples/lua/x09.lua > /<>/obj-x86_64-linux-gnu/examples/lua > cd /<>/obj-x86_64-linux-gnu/examples/python && /usr/bin/cmake -E > copy /<>/examples/python/x07 > /<>/obj-x86_64-linux-gnu/examples/python > cd /<>/obj-x86_64-linux-gnu/examples/lua && /usr/bin/cmake -E > copy /<>/examples/lua/x10.lua > /<>/obj-x86_64-linux-gnu/examples/lua > cd /<>/obj-x86_64-linux-gnu/examples/python && /usr/bin/cmake -E > copy /<>/examples/python/x08 > /<>/obj-x86_64-linux-gnu/examples/python > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' > make[3]: *** > [bindings/qt_gui/pyqt5/CMakeFiles/generate_pyqt5_source.dir/build.make:76: > bindings/qt_gui/pyqt5/sipAPIplplot_pyqt5.h] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/plplot_5.15.0+dfsg-22_unstable.log 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.
Bug#997738: ipywidgets: FTBFS: src/ui/vdom.ts(92,23): error TS2304: Cannot find name 'MouseWheelEvent'.
Source: ipywidgets
Version: 6.0.0-8
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 --test-pytest -i python{version} -p 3.9
> I: pybuild base:232: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9/build/ipywidgets
> copying ipywidgets/__init__.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets
> copying ipywidgets/_version.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets
> creating /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_color.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_controller.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/domwidget.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_link.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_selectioncontainer.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_image.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/__init__.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/valuewidget.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_bool.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_layout.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_string.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_core.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_float.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_style.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_button.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_output.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_date.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/interaction.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_selection.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/trait_types.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_int.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_box.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> creating /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets/tests
> copying ipywidgets/widgets/tests/test_link.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets/tests
> copying ipywidgets/widgets/tests/__init__.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets/tests
> copying ipywidgets/widgets/tests/test_interaction.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets/tests
> copying ipywidgets/widgets/tests/test_traits.py ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets/tests
> copying ipywidgets/state.schema.json ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets
> copying ipywidgets/view.schema.json ->
> /<>/.pybuild/cpython3_3.9/build/ipywidgets
> dh_auto_build --buildsystem nodejs
> Found debian/nodejs/additional_components
> Adding component(s): jupyter-js-widgets
> Adding component(s): jupyter-widgets-schema
> Adding component(s): phosphor
> Adding component(s): scriptjs
> Adding component(s): widgetsnbextension
> No build command found, searching known files
> Found debian/nodejs/phosphor/build
> cd ./phosphor && sh -ex ../debian/nodejs/phosphor/build
> + tsc --project src
> src/ui/vdom.ts(92,23): error TS2304: Cannot find name 'MouseWheelEvent'.
> dh_auto_build: error: cd ./phosphor && sh -ex ../debian/nodejs/phosphor/build
> returned exit code 1
> make[1]: *** [debian/rules:24: override_dh_auto_build] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/ipywidgets_6.0.0-8_unstable.log
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
Bug#997740: python-pkginfo: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 176)
Source: python-pkginfo Version: 1.4.2-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 --buildsystem=pybuild > I: pybuild base:232: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > copying pkginfo/develop.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > copying pkginfo/__init__.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > copying pkginfo/_compat.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > copying pkginfo/index.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > copying pkginfo/commandline.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > copying pkginfo/sdist.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > copying pkginfo/bdist.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > copying pkginfo/distribution.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > copying pkginfo/installed.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > copying pkginfo/utils.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > copying pkginfo/wheel.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > creating /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > copying pkginfo/tests/__init__.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_index.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_utils.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_wheel.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_develop.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_commandline.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_installed.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_sdist.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_bdist.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_distribution.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > python3 setup.py build_sphinx > running build_sphinx > Running Sphinx v4.2.0 > > Configuration error: > There is a syntax error in your configuration file: invalid syntax (conf.py, > line 176) > > make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/python-pkginfo_1.4.2-3_unstable.log 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.
Bug#997741: listparser: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 171)
Source: listparser Version: 0.18-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > PYTHONPATH=. python3 -m sphinx -N -bhtml docs/ build/html > Running Sphinx v4.2.0 > > Configuration error: > There is a syntax error in your configuration file: invalid syntax (conf.py, > line 171) > > make[1]: *** [debian/rules:7: execute_after_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2021/10/23/listparser_0.18-2_unstable.log 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.
Bug#997742: pyrlp: FTBFS: There is a syntax error in your configuration file: Missing parentheses in call to 'print'. Did you mean print(sys.path)? (conf.py, line 22)
Source: pyrlp Version: 0.5.1-1.2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 > I: pybuild base:232: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.9_rlp/build/rlp > copying rlp/__init__.py -> > /<>/.pybuild/cpython3_3.9_rlp/build/rlp > copying rlp/utils_py2.py -> > /<>/.pybuild/cpython3_3.9_rlp/build/rlp > copying rlp/lazy.py -> /<>/.pybuild/cpython3_3.9_rlp/build/rlp > copying rlp/codec.py -> /<>/.pybuild/cpython3_3.9_rlp/build/rlp > copying rlp/exceptions.py -> > /<>/.pybuild/cpython3_3.9_rlp/build/rlp > copying rlp/utils.py -> /<>/.pybuild/cpython3_3.9_rlp/build/rlp > copying rlp/utils_py3.py -> > /<>/.pybuild/cpython3_3.9_rlp/build/rlp > creating /<>/.pybuild/cpython3_3.9_rlp/build/rlp/sedes > copying rlp/sedes/__init__.py -> > /<>/.pybuild/cpython3_3.9_rlp/build/rlp/sedes > copying rlp/sedes/raw.py -> > /<>/.pybuild/cpython3_3.9_rlp/build/rlp/sedes > copying rlp/sedes/lists.py -> > /<>/.pybuild/cpython3_3.9_rlp/build/rlp/sedes > copying rlp/sedes/binary.py -> > /<>/.pybuild/cpython3_3.9_rlp/build/rlp/sedes > copying rlp/sedes/big_endian_int.py -> > /<>/.pybuild/cpython3_3.9_rlp/build/rlp/sedes > running egg_info > creating rlp.egg-info > writing rlp.egg-info/PKG-INFO > writing dependency_links to rlp.egg-info/dependency_links.txt > writing top-level names to rlp.egg-info/top_level.txt > writing manifest file 'rlp.egg-info/SOURCES.txt' > reading manifest file 'rlp.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no previously-included files matching '__pycache__' found under > directory '*' > warning: no previously-included files matching '*.py[co]' found under > directory '*' > adding license file 'LICENSE' > writing manifest file 'rlp.egg-info/SOURCES.txt' > sphinx-build -N -bhtml docs/ \ > docs/_build/html/ > Running Sphinx v4.2.0 > > Configuration error: > There is a syntax error in your configuration file: Missing parentheses in > call to 'print'. Did you mean print(sys.path)? (conf.py, line 22) > > make[1]: *** [debian/rules:65: override_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2021/10/23/pyrlp_0.5.1-1.2_unstable.log 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.
Bug#997743: spatial4j: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project spatial4j: Compilation failure: Compilation failu
Source: spatial4j Version: 0.7-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package spatial4j > dpkg-buildpackage: info: source version 0.7-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by tony mancill > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean >dh_auto_clean > bash -c "for dir in \$(find . -name target -type d); do if [ -f \$(echo > \$dir | sed -e s/target\$/pom.xml/) ]; then rm -Rf \$dir; fi done" > mh_unpatchpoms -plibspatial4j-java >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building spatial4j using existing > ./spatial4j_0.7.orig.tar.gz > dpkg-source: info: building spatial4j in spatial4j_0.7-1.debian.tar.xz > dpkg-source: info: building spatial4j in spatial4j_0.7-1.dsc > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > mh_patchpoms -plibspatial4j-java --debian-build --keep-pom-version > --maven-repo=/<>/debian/maven-repo >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=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > -DskipTests -Dnotimestamp=true -Dlocale=en_US > [INFO] Scanning for projects... > [WARNING] The project org.locationtech.spatial4j:spatial4j:bundle:0.7 uses > prerequisites which is only intended for maven-plugin projects but not for > non maven-plugin projects. For such purposes you should use the > maven-enforcer-plugin. See > https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html > [INFO] > [INFO] < org.locationtech.spatial4j:spatial4j > > > [INFO] Building Spatial4J 0.7 > [INFO] ---[ bundle > ]--- > [INFO] > [INFO] --- replacer:1.5.3:replace (process-packageVersion) @ spatial4j --- > [INFO] Replacement run on 1 file. > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ > spatial4j --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory /<>/src/main/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ spatial4j > --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 72 source files to /<>/target/classes > [INFO] > /<>/src/main/java/org/locationtech/spatial4j/context/SpatialContextFactory.java: > Some input files use unchecked or unsafe operations. > [INFO] > /<>/src/main/java/org/locationtech/spatial4j/context/SpatialContextFactory.java: > Recompile with -Xlint:unchecked for details. > [INFO] - > [WARNING] COMPILATION WARNING : > [INFO] - > [WARNING] bootstrap class path not set in conjunction with -source 7 > [WARNING] > /<>/src/main/java/org/locationtech/spatial4j/shape/jts/JtsShapeFactory.java:[23,38] > org.locationtech.jts.algorithm.CGAlgorithms in > org.locationtech.jts.algorithm has been deprecated > [WARNING] > /<>/src/main/java/org/locationtech/spatial4j/io/jts/JtsGeoJSONWriter.java:[17,37] > org.locationtech.spatial4j.io.LegacyShapeWriter in > org.locationtech.spatial4j.io has been deprecated > [WARNING] > /<>/src/main/java/org/locationtech/spatial4j/io/BinaryCodec.java:[117,15] > makePoint(double,double) in > org.locationtech.spatial4j.context.SpatialContext has been deprecated > [WARNING] > /<>/src/main/java/org/locationtech/spatial4j/io/BinaryCodec.java:[126,15] > makeRectangle(double,double,double,double) in > org.locationtech.spatial4j.context.SpatialContext has been deprecated > [WARNING] > /<>/src/main/java/org/locationtech/spatial4j/io/BinaryCodec.java:[137,15] > makeCircle(org.locationtech.spatial4j.shape.Point,double) in > org.locationtech.spatial4j.context.SpatialContext has been deprecated > [WARNING] > /<>/src/main/java/org/locationtech/spatial4j/io/BinaryCodec.java:[159,15] > makeCollection(java.util.List) in > org.locationtech.spatial4j.context.SpatialContext has been deprecated > [WARNING] > /<>/src/main/java/org/locationtech/spatial4j/context/SpatialContextFactory.java:[103,45] > newIn
Bug#997744: pt-websocket: FTBFS: go install: version is required when current directory is not in a module
Source: pt-websocket Version: 0.2-9 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > cd obj-x86_64-linux-gnu && GOPATH=$PWD go install -v > git.torproject.org/pluggable-transports/websocket/websocket > git.torproject.org/pluggable-transports/websocket/pt-websocket-server > go install: version is required when current directory is not in a module > Try 'go install > git.torproject.org/pluggable-transports/websocket/websocket@latest > git.torproject.org/pluggable-transports/websocket/pt-websocket-server@latest' > to install the latest version > make[1]: *** [debian/rules:13: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/pt-websocket_0.2-9_unstable.log 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.
Bug#997745: rdkit: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.
Source: rdkit
Version: 202009.5-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> pg_buildext checkcontrol
> --- debian/control2021-09-28 12:56:39.0 +
> +++ debian/control.DuaHuU 2021-10-23 06:32:01.031892836 +
> @@ -164,10 +164,10 @@
> .
> This package contains the header files.
>
> -Package: postgresql-13-rdkit
> +Package: postgresql-14-rdkit
> Architecture: any
> Section: database
> -Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-13
> +Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-14
> Suggests:
> Description: Cheminformatics and machine-learning software (PostgreSQL
> Cartridge)
> RDKit is a Python/C++ based cheminformatics and machine-learning software
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is
> required.
> make: *** [/usr/share/postgresql-common/pgxs_debian_control.mk:9:
> debian/control] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/rdkit_202009.5-2_unstable.log
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.
Bug#997746: node-gulp-tsb: FTBFS: Error: Cannot find module './lib-prebuild'
Source: node-gulp-tsb Version: 4.0.5+~cs7.0.2-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > gulp build > [06:32:22] Local gulp not found in /<> > [06:32:22] Try running: npm install gulp > [06:32:22] Using globally installed gulp > "No inputs were found in config file 'tsconfig.json'. Specified 'include' > paths were '[\"src\"]' and 'exclude' paths were '[\"lib/\"]'." > [06:32:22] Using gulpfile /<>/gulpfile.js > [06:32:22] Starting 'build'... > [06:32:22] Starting 'pre-build'... > [06:32:22] Finished 'pre-build' after 8.19 ms > [06:32:22] Starting 'buildWithPreBuild'... > [06:32:22] 'buildWithPreBuild' errored after 967 μs > [06:32:22] Error: Cannot find module './lib-prebuild' > Require stack: > - /<>/gulpfile.js > - /usr/share/nodejs/gulp-cli/lib/versioned/^4.0.0/index.js > - /usr/share/nodejs/gulp-cli/index.js > - /usr/share/nodejs/gulp/bin/gulp.js > at Function.Module._resolveFilename > (internal/modules/cjs/loader.js:815:15) > at Function.resolve (internal/modules/cjs/helpers.js:80:19) > at reload (/<>/gulpfile.js:62:22) > at buildWithPreBuild (/<>/gulpfile.js:28:15) > at bound (domain.js:427:14) > at runBound (domain.js:440:12) > at asyncRunner > (/usr/share/nodejs/gulp/node_modules/async-done/index.js:55:18) > at processTicksAndRejections (internal/process/task_queues.js:79:11) > [06:32:22] 'build' errored after 11 ms > make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/node-gulp-tsb_4.0.5+~cs7.0.2-2_unstable.log 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.
Bug#997747: fiat: FTBFS: sed: no input files
Source: fiat Version: 2019.2.0~git20210116.0439689-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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_sphinxdoc -i > grep "https://cdnjs.cloudflare.com/ajax/libs/mathjax/.*/latest.js"; > debian/python-fiat-doc/usr/share/doc/python-fiat-doc/* -r > --files-with-matches | xargs sed > "s|src=\"https://cdnjs.cloudflare.com/ajax/libs/mathjax/.*/latest.js|src=\"file://usr/share/javascript/mathjax/unpacked/latest.js|g" > -i > sed: no input files > make[1]: *** [debian/rules:32: override_dh_sphinxdoc-indep] Error 123 The full build log is available from: http://qa-logs.debian.net/2021/10/23/fiat_2019.2.0~git20210116.0439689-2_unstable.log 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.
Bug#997749: mdtraj: FTBFS: sed: no input files
Source: mdtraj Version: 1.9.6-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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_sphinxdoc -i > dh_sphinxdoc: warning: ignoring unknown JavaScript code: > debian/python-mdtraj-doc/usr/share/doc/python-mdtraj-doc/html/_static/js/versions.js > grep "https://cdnjs.cloudflare.com/ajax/libs/mathjax/.*/latest.js"; > debian/python-mdtraj-doc/usr/share/doc/python-mdtraj-doc/* -r > --files-with-matches | xargs sed > "s|src=\"https://cdnjs.cloudflare.com/ajax/libs/mathjax/.*/latest.js|src=\"file:///usr/share/javascript/mathjax/unpacked/latest.js|g" > -i > sed: no input files > make[1]: *** [debian/rules:51: override_dh_sphinxdoc-indep] Error 123 The full build log is available from: http://qa-logs.debian.net/2021/10/23/mdtraj_1.9.6-1_unstable.log 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.
Bug#997748: libcomps: FTBFS: There is a syntax error in your configuration file: Missing parentheses in call to 'print'. Did you mean print(os.environ['LD_LIBRARY_PATH'])? (conf.py, line 23)
Source: libcomps Version: 0.1.15-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[5]: Entering directory '/<>/build' > cd /<>/build/src/python/docs && set -E > /<>/build/src: > cd /<>/build/src/python/docs && /usr/bin/cmake -E make_directory > /<>/build/src/python/src//libcomps/comps/ > copy /<>/libcomps/src/python/tests//__test.py to > /<>/build/src/python/src//libcomps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests/__test.py > /<>/build/src/python/src//libcomps/ > copy /<>/libcomps/src/python/tests//test_libcomps.py to > /<>/build/src/python/src//libcomps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests/test_libcomps.py > /<>/build/src/python/src//libcomps/ > copy /<>/libcomps/src/python/tests//test_merge_comps.py to > /<>/build/src/python/src//libcomps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests/test_merge_comps.py > /<>/build/src/python/src//libcomps/ > copy /<>/libcomps/src/python/tests//utest.py to > /<>/build/src/python/src//libcomps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests/utest.py > /<>/build/src/python/src//libcomps/ > /<>/libcomps/src/python/tests//comps/biarchonly.xml to > /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests//comps/biarchonly.xml > /<>/build/src/python/src//libcomps/comps/ > /<>/libcomps/src/python/tests//comps/comps-f21.xml to > /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests//comps/comps-f21.xml > /<>/build/src/python/src//libcomps/comps/ > /<>/libcomps/src/python/tests//comps/comps-f21.xml.in to > /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests//comps/comps-f21.xml.in > /<>/build/src/python/src//libcomps/comps/ > /<>/libcomps/src/python/tests//comps/comps-rawhide.xml to > /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests//comps/comps-rawhide.xml > /<>/build/src/python/src//libcomps/comps/ > /<>/libcomps/src/python/tests//comps/comps_empty_by_lang_tags.xml > to /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests//comps/comps_empty_by_lang_tags.xml > /<>/build/src/python/src//libcomps/comps/ > /<>/libcomps/src/python/tests//comps/comps_part1.xml to > /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests//comps/comps_part1.xml > /<>/build/src/python/src//libcomps/comps/ > /<>/libcomps/src/python/tests//comps/comps_part2.xml to > /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests//comps/comps_part2.xml > /<>/build/src/python/src//libcomps/comps/ > /<>/libcomps/src/python/tests//comps/f21-rawhide-comps.xml to > /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests//comps/f21-rawhide-comps.xml > /<>/build/src/python/src//libcomps/comps/ > /<>/libcomps/src/python/tests//comps/fedora_comps.xml to > /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests//comps/fedora_comps.xml > /<>/build/src/python/src//libcomps/comps/ > /<>/libcomps/src/python/tests//comps/main_arches.xml to > /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests//comps/main_arches.xml > /<>/build/src/python/src//libcomps/comps/ > /<>/libcomps/src/python/tests//comps/main_comps.xml to > /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests//comps/main_comps.xml > /<>/build/src/python/src//libcomps/comps/ > /<>/libcomps/src/python/tests//comps/main_comps2.xml to > /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests//comps/main_comps2.xml > /<>/build/src/python/src//libcomps/comps/ > /<>/libcomps/src/python/tests//comps/main_def.xml to > /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests//comps/main_def.xml > /<>/build/src/python/src//libcomps/comps/ > /<>/libcomps/src/python/tests//comps/merged_comps_1_2.xml to > /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/do
