Bug#1057865: reproject ftbfs with Python 3.12
Control: forwarded -1 https://github.com/astropy/reproject/issues/414 Control: reassign -1 python3-astropy-healpix 1.0.0-1 Control: affects -1 src:reproject Control: tags -1 +pending This bug isn't in reproject, but in astropy-healpix and slided through the CI tests there. A solution was found upstream (https://github.com/astropy/astropy-healpix/pull/208) and will be uploaded ASAP.
Bug#1057967: Fixed - Was: Re: Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable
Le Mon, Dec 11, 2023 at 02:55:50AM +0100, Kevin Price a écrit : > When booting 6.1.0-15, my physical amd64/bookworm/gnome computer > misbehaves in many ways, rendering it largely unusable. With kernels up > to 6.1.0-13, and even briefly with the otherwise broken 6.1.0-14, all of > this seemed fine. > FWIW, I experienced the same kind of behaviour, linked to a broken wifi with rtl88x2bu DKMS driver. Fixed now with: linux-image-6.1.0-16-amd64-unsigned 6.1.67-1 $ uname -a Linux pcpapa 6.1.0-16-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.67-1 (2023-12-12) x86_64 GNU/Linux Thanks a lot. Best regards, -- Olivier BERGER (OpenPGP: 4096R/7C5BB6A5) http://www.olivierberger.com/weblog/
Bug#1058522: (no subject)
Hi, Hmmm... strange. I cannot reproduce this. I tried to (1) run tests locally with dh_elpa_test, (2) run tests locally as autopkgtest supposed to with dh_elpa_test --autopkgtest, (3) run tests during build from scratch under sbuild, (4) run tests with autopkgtest under sbuild. Tests were successful everywhere. Guess, it is a false positive, but will keep the bug report open for some time. Cheers! Lev
Bug#899245: kgb-bot: support for password-protected channels
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2023-12-12 at 17:18 -0500, Antoine Beaupré wrote: > On 2018-05-21 16:01:59, Yves-Alexis Perez wrote: > > subject mostly says it all, but it'd be nice if KGB could support > > password-protected IRC channels for notifications. > > The library backing KGB does support it, so it seems it's only a matter > of a few lines patch: > > https://salsa.debian.org/kgb-team/kgb/-/merge_requests/8 > > Also attached. > > Please test and report back here or, preferably, in the above merge request. Hi Antoine, since the bug is from 2018, I have to admit I don't really remember why I opened it and what channel was the target. I don't have a way to test the patch these days, but thanks for the work anyway. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmV5XmoACgkQ3rYcyPpX RFsWBQf+MggG6hvPz3hDO75MItVfsSVgrLQR+OfYiwSwCnuceSWOfLzxsaAUgA6r 7Ooo2YsqKt9Ga3qCTH96BRxTvimJHUKBhH16pG2gJP36u/OwUafMmAN0Mt+p1Ofg MSjYY8SN6zuOiwBhBk2WdAeQTL17ZEGP4lQJeH83AzYGjuUdUqAzc/z/UJWXBocd px6g9aBWNTB7IfZ1kuB1BxB7GAEAeTA14j8r6CqJewLShZoeUTBVEEddwwlGWExx IsBw8nH1Zxd7WOTfciPREkuKXWmtp5fI1Luz34P3+unbsWaZiYzlfJNjiT+ZgJs1 qEv7usw8sGqd0yzEz585gdQ2uzbXaA== =4cab -END PGP SIGNATURE-
Bug#1058576: linux-image-6.5.0-0.deb12.4-amd64: Kernel module for AMD Raphael ACP missing
Package: src:linux
Version: 6.5.10-1~bpo12+1
Severity: normal
X-Debbugs-Cc: peter.ganzh...@gmail.com
Dear Maintainer,
the built-in microphone of my Lenovo ThinkPad P16s Gen 2, model 21K9... laptop
is not working.
The laptop has an AMD Ryzen 7 Pro 7840U CPU ('Raphael' / RPL) with an Audio
Coprocessor:
64:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD]
ACP/ACP3X/ACP6x Audio Coprocessor (rev 63)
Subsystem: Lenovo ACP/ACP3X/ACP6x Audio Coprocessor
Flags: fast devsel, IRQ 255, IOMMU group 21
Memory at 7858 (32-bit, non-prefetchable) [disabled] [size=256K]
Memory at 1c1000 (64-bit, prefetchable) [disabled] [size=8M]
Capabilities: [48] Vendor Specific Information: Len=08
Capabilities: [50] Power Management version 3
Capabilities: [64] Express Endpoint, MSI 00
Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010
Capabilities: [2a0] Access Control Services
Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x,
snd_pci_acp6x
The default Debian 12 kernel has the KCONFIG switch
# CONFIG_SND_SOC_AMD_RPL_ACP6x is not set
disabled.
Even in the kernel available from bookworm-backports the module is not enabled.
The module is most likely required to get the built-in microphone working.
A very similar situation was reported on the Arch Linux BBS affecting Ryzen
6000 'Yellow Carp': https://bbs.archlinux.org/viewtopic.php?id=278886
In this case, the Audio Coprocessor was also the culprit for a non-working
microphone on a Lenovo laptop.
I tried building the kernel based on the config file located in /boot, but
ended up with a ~500MB initrd image and booting failed with a message like
"initrd too large".
Sadly I was unable to find any documentation about how to build a kernel based
on the default Debian configuration that enabled me to successfully build resp.
boot a kernel with the module enabled.
I would very much appreciate if you could enable CONFIG_SND_SOC_AMD_RPL_ACP6x=m
for the kernels available in bookworm-backports.
If you can hint me at why the initrd of my self-built kernel was way larger
than what is generated for the prebuilt kernel images I can confirm if loading
the module enables the laptop microphone.
I copied /boot/config-6.5.0-0.deb12.4-amd64 to .config in the extracted kernel
sources and ran
make oldconfig
make
make modules
make modules_install
cp ./arch/x86_64/boot/bzImage /boot/vmlinux-6.5.13
update-initramfs -c -k 6.5.13
update-grub
I did use vanilla sources from kernel.org for this test, there were no
compilation errors but as I already stated the generated initrd image was
almost 500MB in size and booting failed.
-- Package-specific info:
** Version:
Linux version 6.5.0-0.deb12.4-amd64 (debian-ker...@lists.debian.org) (gcc-12
(Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP
PREEMPT_DYNAMIC Debian 6.5.10-1~bpo12+1 (2023-11-23)
** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.5.0-0.deb12.4-amd64
root=UUID=a8c9220c-f0c2-45ed-ac7f-f3f540540747 ro quiet
** Not tainted
** Kernel log:
[4.708949] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC257:
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[4.708954] snd_hda_codec_realtek hdaudioC1D0:speaker_outs=0
(0x0/0x0/0x0/0x0/0x0)
[4.708955] snd_hda_codec_realtek hdaudioC1D0:hp_outs=1
(0x21/0x0/0x0/0x0/0x0)
[4.708956] snd_hda_codec_realtek hdaudioC1D0:mono: mono_out=0x0
[4.708957] snd_hda_codec_realtek hdaudioC1D0:inputs:
[4.708958] snd_hda_codec_realtek hdaudioC1D0: Mic=0x19
[4.712747] input: HD-Audio Generic HDMI/DP,pcm=7 as
/devices/pci:00/:00:08.1/:64:00.1/sound/card0/input16
[4.712811] input: HD-Audio Generic HDMI/DP,pcm=8 as
/devices/pci:00/:00:08.1/:64:00.1/sound/card0/input17
[4.722703] input: SYNA801A:00 06CB:CEC6 Mouse as
/devices/platform/AMDI0010:01/i2c-1/i2c-SYNA801A:00/0018:06CB:CEC6.0001/input/input19
[4.722830] input: SYNA801A:00 06CB:CEC6 Touchpad as
/devices/platform/AMDI0010:01/i2c-1/i2c-SYNA801A:00/0018:06CB:CEC6.0001/input/input20
[4.722942] hid-multitouch 0018:06CB:CEC6.0001: input,hidraw0: I2C HID v1.00
Mouse [SYNA801A:00 06CB:CEC6] on i2c-SYNA801A:00
[4.754892] thinkpad_acpi: ThinkPad ACPI Extras v0.26
[4.754897] thinkpad_acpi: http://ibm-acpi.sf.net/
[4.754900] thinkpad_acpi: ThinkPad BIOS R2FET33W (1.13 ), EC R2FHT27W
[4.754903] thinkpad_acpi: Lenovo ThinkPad P16s Gen 2, model 21K9CTO1WW
[4.788525] Bluetooth: Core ver 2.22
[4.788548] NET: Registered PF_BLUETOOTH protocol family
[4.788550] Bluetooth: HCI device and connection manager initialized
[4.788553] Bluetooth: HCI socket layer initialized
[4.788556] Bluetooth: L2CAP socket layer initialized
[4.788560] Bluetooth: SCO socket layer initialized
[4.789733] kvm_amd: TSC scaling supported
[4.789736] kvm_amd:
Bug#1057124: RFS: harmony/0.7.2-1 [ITA] -- program and library for creating and managing Discord accounts
Control: close -1 On Tue, 2023-12-12 at 09:52 +0100, Patrick ZAJDA wrote: > I removed the suppression of the lintian warning and sent the package again. ... > Done in the last sent package of today. Uploaded. > I plan to generate a manpage using help2man then suggest it upstream > after some eventual modifications, I think it can wait for a next > version seeing there are only --help and --debug in command line parameters. Sounds good, although I guess upstream is likely to prefer a different source format than groff. So you might want to look at what the Python community uses for generating them, or ask them before working on it. > > Looks feasible, also for a next version to have all upstream or do you > think all should be done for this version? Just some polish, so for Debian it can wait for the next upstream release. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#897277: decrease e2fsprogs' Priority: required
Hi Ted, On Wed, Aug 18, 2021 at 01:41:36AM +0300, Faidon Liambotis wrote: > I haven't received a response for this. We are now at the beginning of > the aforementioned bookworm cycle, so I thought it may be a good > opportunity to bump this :) Do you have any thoughts? It's now been 2½ years since I last followed up on this bug, and 5½ since your last response where you said you'd "batch it with some other bug fixes in the next e2fsprogs minor release" and that would happen "by early June [2018] at the latest". Has this fallen through the cracks? Have you changed your mind? Would it be possible to get an update here? Thanks, Faidon
Bug#1058575: glogic: Fails to start due AttributeError
Package: glogic
Version: 2.6-6
Severity: serious
Dear Maintainer,
qlogic isn't usable any more in unstable and testing.
It fails to start as a calling of a Python function raises a
AttributeError.
$ glogic
/usr/lib/python3/dist-packages/glogic/MainFrame.py:4: PyGIWarning: Gtk was
imported without specifying a version first. Use gi.require_version('Gtk',
'4.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk, Gdk, GdkPixbuf
Traceback (most recent call last):
File "/usr/bin/glogic", line 20, in
from glogic.MainFrame import MainFrame
File "/usr/lib/python3/dist-packages/glogic/MainFrame.py", line 18, in
themed_icons = Gtk.IconTheme.get_default()
^
AttributeError: type object 'IconTheme' has no attribute 'get_default'
Rgards
Carsten
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages glogic depends on:
ii gir1.2-gtk-3.03.24.38-6
ii python3 3.11.4-5+b1
ii python3-gi3.46.0-1+b1
ii python3-gi-cairo 3.46.0-1+b1
glogic recommends no packages.
Versions of packages glogic suggests:
ii fonts-liberation 1:2.1.5-3
-- no debconf information
Bug#1057165: libitext-java: FTBFS with bouncycastle 1.77
On Thu, Nov 30, 2023 at 10:47:18PM +0100, Markus Koschany wrote: > Source: libitext-java > Version: 2.1.7-14 > Severity: serious > Tags: ftbfs sid > User: a...@debian.org > Usertags: bouncycastle-1.77 > X-Debbugs-Cc: a...@debian.org > > Dear maintainer, > > libitext-java fails to build from source with bouncycastle 1.77. The reason > is the removal of long deprecated methods. The (hopefully) relevant > error message from the build log. I have added a patch to address the FTBFS. Unfortunately, this package doesn't run tests and getting them working is going to take some effort. The patch is straight-forward. It eliminates usage of a few long-deprecated classes in favor of their replacements, or uses some factory-like methods to instantiate objects. However, it would be nice to have at least some sort of runtime checks before uploading, which may take me a few days. I have pushed the changes to the repo if anyone is ready to move ahead with an upload. If not, I will try to upload by early next week. Thanks, tony signature.asc Description: PGP signature
Bug#1032522:
I missed this report while researching, so I ended up filing this one: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058574 It looks like it was an upstream issue where certain code in python.el was brought into emacs 28.2, but didn't make it to 29.
Bug#1057843: (no subject)
If it helps people, this is what I did on systems that automatically had rebooted into the problematic kernel. First, I uninstalled the 6.1.0-14 kernel and rebooted back into 6.1.0-13. Then I used `last` to identify the time between the problematic reboot into 6.1.0-14 and the deliberate reboot (back in to 6.1.0-13) This showed me that the 'problem time' was between 2023-12-10 06:00:00 and 2023-12-10 19:00:00 (UTC). >From there, I ran the followin gcommand to show me all files that were >modified more or less between that time. I ignore a bunch of things I don't >care about such as /var/log and other volatile parts of the filesystem. find / -type f -newermt "2023-12-10 05:59:00" \! -newermt "2023-12-10 19:00:00" | egrep -v "/proc|/run|/sys|/var/log" At least this gave me a somewhat small subset of files to manually check, which made it feel less daunting. Naturally it depends on your filesystem what files might've changed. I was fortunate that none of the client applications I use, seem to use O_DIRECT, so I found no corrupted files (so far). Note that use of O_DIRECT is not a system-wide setting (e.g not one in /etc/fstab for the ext4 filesystem), it's something that each application can choose to use when working with files. For example, I have changed MySQL's innodb_flush_method to be O_DIRECT in the past (for performance), but it's not the default. Out of the box, things like postgresql use fsync (not direct IO) by default. I used some tools like 'git fsck' in git repositories that had changed during my 'problematic' time, and there were no issues - hopefully git does not use O_DIRECT. I have not been able to find any definitive list of programs that use O_DIRECT out-of-the box. Maybe someone else will come up with such a list (if there even *are* programs that do so). As others have said here, things like fsck won't likely help you, unfortunately. The nature of the bug is not one that corrupts the journaling/filesystem structure, it is more about the *contents* of the file, which fsck can't comment on. Finally, I wanted to note: if you did `apt purge linux-image-6.1.0-14-amd64`, you might need to `apt install linux-image-amd64` (the meta package) before you can successfully pick up the new linux-image-6.1.0-15-amd64 automatically as a dependency (say, when doing apt update; apt dist-upgrade). At least, I needed to, as I think the purge automatically removed the meta package, leaving me with no *automatic* upgrade to the new kernel via those commands. Good luck!
Bug#1058574: Acknowledgement (emacs-el: emacs reliably hangs when editing python source with certain docstrings)
Of course, as soon as I file the bug, THEN I find a likely duplicate: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032522
Bug#1058535: libhinawa: FTBFS: make: *** [debian/rules:8: binary] Error 25
On Tue, 12 Dec 2023 21:51:47 +0100
Lucas Nussbaum wrote:
> Source: libhinawa
> Version: 4.0.0-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20231212 ftbfs-trixie
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
snip
[15/15] /usr/bin/gi-docgen generate --no-namespace-dir
--config=doc/hinawa.toml --output-dir=doc/hinawa
--content-dir=/<>/doc src/Hinawa-4.0.gir
> FAILED: doc/hinawa
> /usr/bin/gi-docgen generate --no-namespace-dir
> --config=doc/hinawa.toml --output-dir=doc/hinawa
> --content-dir=/<>/doc src/Hinawa-4.0.gir WARNING:
> Section domains raised Invalid version: '2.5.' INFO: Loading config
> file: doc/hinawa.toml
It need a patch somthing like:
+diff --git a/src/hinawa_enum_types.h b/src/hinawa_enum_types.h
+index 1687046..a1c1ebf 100644
+--- a/src/hinawa_enum_types.h
b/src/hinawa_enum_types.h
+@@ -98,7 +98,7 @@ typedef enum {
+ * A set of error code for [struct@GLib.Error] for operations in
[class@FwReq].
+ * The actual value is equivalent to [enum@FwRcode].
+ *
+- * Since: 2.5.
++ * Since: 2.5
+ */
+ typedef enum {
+ HINAWA_FW_REQ_ERROR_CONFLICT_ERROR =
HINAWA_FW_RCODE_CONFLICT_ERROR,
Bug#1058574: emacs-el: emacs reliably hangs when editing python source with certain docstrings
Package: emacs-el Version: 1:28.2+1-15 Severity: important Tags: upstream X-Debbugs-Cc: dalg...@gmail.com Dear Maintainer, When editing the following file, emacs will reliably hang: $ cat bug.py def foo(self): """Foo.""" """ pass def baz(self): """Ba'r.""" pass The problem seems triggered by the single-quote in the second docstring. Upon research, this is likely a problem specific to the version of progmodes/python.el shipped with emacs 28.2. Although the above specific test case did not seem to match other reports I saw. I'm not comfortable enough mixing and matching something like emacs-el from backports (which is 29.1) with stable emacs 28.2 (not enough experience with emacs). Some reference threads: https://lists.gnu.org/archive/html/bug-gnu-emacs/2023-01/msg01686.html https://www.reddit.com/r/emacs/comments/z0oye9/emacs_freezes_when_opening_a_python_file https://emacs.stackexchange.com/questions/74167/python-mode-hangs-on-class-member-comment -- System Information: Debian Release: 12.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-15-amd64 (SMP w/6 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages emacs-el depends on: ii emacs-common 1:28.2+1-15 emacs-el recommends no packages. emacs-el suggests no packages. -- no debconf information
Bug#1058573: bowtie: compilation errors on the loong64 architecture
Source: bowtie Version: 1.3.1-1 Severity: normal X-Debbugs-Cc: wuruil...@loongson.cn Dear Maintainer, bowtie has compilation errors on the loong64 architecture. Please modify the debian/control file to add support for loong64. The code is as follows: Architecture: alpha any-amd64 arm64 loong64 mips64el ppc64 ppc64el s390x sparc64 riscv64 wuruilong -- System Information: Debian Release: trixie/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: loong64 (loongarch64) Kernel: Linux 5.10.0-60.96.0.126.oe2203.loongarch64 (SMP w/32 CPU threads) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect
Bug#1058572: gnupg2.4: fail to initialize homedir and generate key due to keyboxd
Package: src:gnupg2 Version: 2.4.3-2 > gpg --quick-generate-key "A User " rsa2048 > > ~ gpg: directory '/home//.gnupg' created We need to generate a lot of random bytes. It is a good idea to perform some other action (type on the keyboard, move the mouse, utilize the disks) during the prime generation; this gives the random number generator a better chance to gain enough entropy. gpg: error writing public keyring '[keyboxd]': Attempt to write a readonly SQL database Key generation failed: Attempt to write a readonly SQL database The problem is due to when create gnupg 2.4+ will add a "common.conf" in new created ~/.gnupg directory, with "use-keyboxd", while keyboxed is not enabled on Debian yet. https://github.com/gpg/gnupg/blob/master/README -- YunQiang Su
Bug#1058571: gnupg2: please enable TPM2 support
Package: src:gnupg2 Version: 2.4.3-2 TPM2 support has been introduced into GnuPG since 2.3. https://gnupg.org/blog/20210315-using-tpm-with-gnupg-2.3.html While TPM2 support is not enabled for Debian's gnupg2 package in experimental: https://buildd.debian.org/status/fetch.php?pkg=gnupg2=i386=2.4.3-2=1695644413=0 TPM: no
Bug#1058570: bcal: compilation errors on the loong64 architecture
Source: bcal Version: 2.4-2 Severity: normal X-Debbugs-Cc: wuruil...@loongson.cn Dear Maintainer, bcal has compilation errors on the loong64 architecture. Please modify the debian/control file to add support for loong64. The code is as follows: Architecture: amd64 arm64 loong64 ppc64 ppc64el riscv64 mips64el wuruilong -- System Information: Debian Release: trixie/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: loong64 (loongarch64) Kernel: Linux 5.10.0-60.96.0.126.oe2203.loongarch64 (SMP w/32 CPU threads) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect
Bug#1058569: debian-installer: Terminal warns "setlocale: LC_ALL: cannot change locale" after non-USA install
Source: debian-installer Version: 20230607+deb12u4 Severity: normal X-Debbugs-Cc: debbugtr...@dan.heath.cc Dear Maintainer, I have installed debian via the ISO at https://gemmei.ftp.acc.umu.se/debian-cd/current/amd64/iso-cd/debian-12.4.0-amd64-netinst.iso and selecting the "Australia" locale / "Victoria" timezone / "US keyboard layout" options. Each time I open a terminal, I get the following message: -bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) Both LC_LANG and LC_ALL are set to en_US.UTF-8, which is not an installed locale. I have had a dig through /etc and $HOME but have not found anything which sets them. -- System Information: Debian Release: 12.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-15-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1058568: bglibs: crc-gentab has no manpage.
forwarded 1058568 https://github.com/bruceg/bglibs/issues/2 -- Playing the game for the games sake. Web: * Debian Wiki: https://wiki.debian.org/PhilWyett * Website: https://kathenas.org * Social Debian: https://pleroma.debian.social/kathenas/ * Social Instagram: https://www.instagram.com/kathenasorg/ signature.asc Description: This is a digitally signed message part
Bug#1054823: starlette: FTBFS: tests failed
The build failure is due to the library python3-httpx. This library uses python3-rfc3986, it's been upgraded lately [1], and it's now causing the breakage. There's a discussion about this issue upstream [2]. If we bump src:httpx to version 0.24.0, the dependency on python3-rfc3986 goes away, and the problem will be fixed. Looking at src:httpx now: Debian has 0.23.3-1, we need at least 0.24, and upstream is at 0.25.2. $ build-rdeps python3-httpx Reverse Build-depends in main: -- aioxmlrpc asgi-csrf asgi-lifespan dnspython fastapi greenbone-feed-sync nala ormar pontos python-a2wsgi python-authlib python-cobra python-duckpy python-falcon python-gvm python-tiny-proxy python-truststore python-uvicorn sqlmodel starlette Since I'm not involved in Python packaging, I don't feel comfortable doing this upgrade. Best, Arnaud [1]: https://tracker.debian.org/pkg/python-rfc3986 [2]: https://github.com/encode/starlette/discussions/1879 On Fri, 27 Oct 2023 21:48:44 +0200 Lucas Nussbaum wrote: > Source: starlette > Version: 0.31.1-1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20231027 ftbfs-trixie > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > debian/rules build > > dh build --with python3 --buildsystem=pybuild > > dh_update_autotools_config -O--buildsystem=pybuild > > dh_autoreconf -O--buildsystem=pybuild > > dh_auto_configure -O--buildsystem=pybuild > > dh_auto_build -O--buildsystem=pybuild > > I: pybuild plugin_pyproject:110: Building wheel for python3.11 with "build" module > > I: pybuild base:310: python3.11 -m build --skip-dependency-check --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.11_starlette > > * Building wheel... > > Successfully built starlette-0.31.1-py3-none-any.whl > > I: pybuild plugin_pyproject:122: Unpacking wheel built for python3.11 with "installer" module > > dh_auto_test -O--buildsystem=pybuild > > I: pybuild base:310: cd /<>/.pybuild/cpython3_3.11_starlette/build; python3.11 -m pytest tests > > = test session starts == > > platform linux -- Python 3.11.6, pytest-7.4.3, pluggy-1.3.0 > > rootdir: /<>/.pybuild/cpython3_3.11_starlette/build > > configfile: pyproject.toml > > plugins: anyio-3.7.0 > > collected 420 items > > > > tests/test__utils.py .. [ 1%] > > tests/test_applications.py .FF.FFF..F.FFF..F. [ 7%] > > tests/test_authentication.py .FF.FF [ 9%] > > tests/test_background.py [ 10%] > > tests/test_concurrency.py .F [ 10%] > > tests/test_config.py [ 11%] > > tests/test_convertors.py FFF [ 12%] > > tests/test_datastructures.py .. [ 17%] > > tests/test_endpoints.py FFF... [ 19%] > > tests/test_exceptions.py .FF.F [ 22%] > > tests/test_formparsers.py ..F [ 31%] > > tests/test_requests.py FFF...FFF.FF.F.FF. [ 41%] > > tests/test_responses.py FF. [ 48%] > > tests/test_routing.py FF..FF.FF.FF.F.F.FF..F.F.F..FFF..FFF.. [ 60%] > > .. [ 60%] > > tests/test_schemas.py .F [ 61%] > > tests/test_staticfiles.py FFF.FFF.FF.. [ 68%] > > tests/test_status.py .. [ 68%] > > tests/test_templates.py ..F.FF [ 71%] > > tests/test_testclient.py F.F..FF.FFF [ 76%] > > tests/test_websockets.py [ 84%] > > tests/middleware/test_base.py FF....FF..FF [ 89%] > > tests/middleware/test_cors.py FFF [ 93%] > > tests/middleware/test_errors.py .F [ 94%] > > tests/middleware/test_gzip.py F [ 95%] -- Arnaud Rebillout / OffSec / Kali Linux Developer
Bug#1058568: bglibs: crc-gentab has no manpage.
Package: bglibs Version:2.04+dfsg-5 bglibs: crc-gentab has no manpage. Tracking bug of maintainer. Regards Phil -- Playing the game for the games sake. Web: * Debian Wiki: https://wiki.debian.org/PhilWyett * Website: https://kathenas.org * Social Debian: https://pleroma.debian.social/kathenas/ * Social Instagram: https://www.instagram.com/kathenasorg/ signature.asc Description: This is a digitally signed message part
Bug#1038112: bglibs/sysdeps.h redeclares system functions and variables (with incomplete prototypes)
forwarded 1038112 https://github.com/bruceg/bglibs/issues/3 Actually forwarded. Regards Phil -- Playing the game for the games sake. Web: * Debian Wiki: https://wiki.debian.org/PhilWyett * Website: https://kathenas.org * Social Debian: https://pleroma.debian.social/kathenas/ * Social Instagram: https://www.instagram.com/kathenasorg/ signature.asc Description: This is a digitally signed message part
Bug#1038112: bglibs/sysdeps.h redeclares system functions and variables (with incomplete prototypes)
This looks like it was never forwarded to upstream. Will do so to get their opinions on the issue. Regards Phil -- Playing the game for the games sake. Web: * Debian Wiki: https://wiki.debian.org/PhilWyett * Website: https://kathenas.org * Social Debian: https://pleroma.debian.social/kathenas/ * Social Instagram: https://www.instagram.com/kathenasorg/ signature.asc Description: This is a digitally signed message part
Bug#1058560: libncursesw6: getch(3ncurses) returns -1 with errno unchanged, only documented to return -1 with errno=EINTR
On Wed, Dec 13, 2023 at 01:33:59AM +0100, наб wrote: > On Tue, Dec 12, 2023 at 05:55:38PM -0500, Thomas Dickey wrote: > > On Tue, Dec 12, 2023 at 11:09:13PM +0100, наб wrote: > > > urlview 1c-1 whose xterm was killed but which didn't die consumes 100% > > > CPU. > > > The event loop is for(;;) switch(getch()) ... and ignores -1 > > If it's going to ignore the error return (while at the same time > > manipulating the time delays with mousemask), then this is expected > > (mis)behavior. > Sure. > > Still, it doesn't set errno to EINTR, ...and the manual page does not say it would do that. It lists three possible causes for ERR being returned, and on the third it mentions that errno will be set: returns ERR if the window pointer is null, or if its timeout expires without having any data, or if the execution was interrupted by a signal (errno will be set to EINTR). It could be reformatted like this without changing its meaning: returns ERR * if the window pointer is null, or * if its timeout expires without having any data, or * if the execution was interrupted by a signal (errno will be set to EINTR). though doing that for every 2-3 line sentence will make the page less readable. (errno isn't set for a null window pointer either) > and instant empty reads you get from a hung-up teletype > definitely aren't exceeding the timeout. https://git.sr.ht/~nabijaczleweli/urlview-ng/tree/1c/item/urlview.c#L441 mouseinterval(0) tells it to not wait for mouse events, and results in a zero-delay in check_mouse_activity: https://github.com/ThomasDickey/ncurses-snapshots/blob/b5a2b7c720102b187e6d1099f36ed2643fea4934/ncurses/base/lib_getch.c#L152 That looks like someone's attempting to make the wheel mouse work at infinite velocity -- and might be the reason for ignoring errors -- and might be the reason for the 100% CPU. I'd have used a 5msec delay (or 1msec for "modern" computers :-) If ncurses is actually reading from a closed file descriptor, the manpage for read(2) suggests that errno may be set to EBADF -- but since you say errno is _not_ being set, then there's nothing to alert ncurses to the problem -- the timeout expired. (You may get more insight using strace). -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
Bug#1058567: python-tuspy: please remove dependency on python3-future
Source: python-tuspy Version: 1.0.0-2 Severity: normal Upstream has removed usage of python3-future in git. I proposed a supplementary PR to also remove usage of python3-six. https://github.com/tus/tus-py-client/pull/90 Greetings, -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (501, 'testing'), (450, 'unstable'), (400, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-5-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#1058566: auto-apt-proxy: "approx" should not be given https URLs
Package: auto-apt-proxy Version: 14.1 Severity: normal Dear Maintainer, according to d#756656 [1] https-URLs cannot be given to `approx`. Thus, the `approx` check should be skipped when an https URL is requested. Cheers, Lars [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756656
Bug#1001132: kdenlive: Unable to Start with Use GPU processing (Movit libary) enabled
在 2023年12月12日星期二 CST 下午11:29:00，Patrick Matthäi 写道： > Can you install the dbgsym packages and run it with gdb and send a > backtrace? > > Am 12.12.2023 um 16:21 schrieb Bob Wong: > > 在 2023年12月12日星期二 CST 下午11:05:29，您写道： > >> Hey > >> > >> Am 05.12.2021 um 02:22 schrieb Bob Wong: > >>> Package: kdenlive > >>> Version: 21.08.3-1 > >>> Severity: normal > >>> X-Debbugs-Cc:ybx...@gmail.com > >>> > >>> Dear Maintainer, > >>> > >>> The software crashes with Use GPU processing function enabled. > >> Do you still have this issue with kdenlive 23.08.4-1? > >> > > Yes. If I enable the GPU rendering, the software will still crash. > > -- System Information: > > Debian Release: trixie/sid > >APT prefers testing > >APT policy: (500, 'testing') > > Architecture: amd64 (x86_64) > > Foreign Architectures: i386 > > > > Kernel: Linux 6.5.0-5-amd64 (SMP w/12 CPU threads; PREEMPT) > > Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), > > LANGUAGE=zh_CN:zh > > Shell: /bin/sh linked to /usr/bin/dash > > Init: systemd (via /run/systemd/system) > > LSM: AppArmor: enabled > > > > Versions of packages kdenlive depends on: > > ii breeze 4:5.27.9-1 > > ii breeze-icon-theme 4:5.107.0-1 > > ii ffmpeg 7:6.1-5 > > ii gstreamer1.0-plugins-bad 1.22.7-1 > > ii kded5 5.107.0-1 > > ii kdenlive-data 23.08.3-1 > > ii kinit 5.107.0-1 > > ii kio5.107.0-1 > > ii libc6 2.37-12 > > ii libkf5archive5 5.107.0-1 > > ii libkf5bookmarks5 5.107.0-1 > > ii libkf5codecs5 5.107.0-1 > > ii libkf5completion5 5.107.0-1 > > ii libkf5configcore5 5.107.0-1 > > ii libkf5configgui5 5.107.0-1 > > ii libkf5configwidgets5 5.107.0-2 > > ii libkf5coreaddons5 5.107.0-1 > > ii libkf5crash5 5.107.0-1 > > ii libkf5dbusaddons5 5.107.0-1 > > ii libkf5filemetadata35.107.0-1+b1 > > ii libkf5guiaddons5 5.107.0-1 > > ii libkf5i18n55.107.0-1+b1 > > ii libkf5iconthemes5 5.107.0-1+b1 > > ii libkf5itemviews5 5.107.0-1 > > ii libkf5jobwidgets5 5.107.0-1 > > ii libkf5kiocore5 5.107.0-1 > > ii libkf5kiofilewidgets5 5.107.0-1 > > ii libkf5kiogui5 5.107.0-1 > > ii libkf5kiowidgets5 5.107.0-1 > > ii libkf5newstuffwidgets5 5.107.0-2 > > ii libkf5notifications5 5.107.0-1 > > ii libkf5notifyconfig55.107.0-1 > > ii libkf5purpose-bin 5.107.0-1 > > ii libkf5purpose5 5.107.0-1 > > ii libkf5solid5 5.107.0-1 > > ii libkf5textwidgets5 5.107.0-1 > > ii libkf5widgetsaddons5 5.107.0-1 > > ii libkf5xmlgui5 5.107.0-1+b1 > > ii libmlt++7 7.22.0-1 > > ii libmlt77.22.0-1 > > ii libqt5core5a 5.15.10+dfsg-5 > > ii libqt5dbus55.15.10+dfsg-5 > > ii libqt5gui5 5.15.10+dfsg-5 > > ii libqt5multimedia5 5.15.10-2 > > ii libqt5network5 5.15.10+dfsg-5 > > ii libqt5networkauth5 5.15.10-2 > > ii libqt5qml5 5.15.10+dfsg-2 > > ii libqt5quick5 5.15.10+dfsg-2 > > ii libqt5quickcontrols2-5 5.15.10+dfsg-2 > > ii libqt5quickwidgets55.15.10+dfsg-2 > > ii libqt5svg5 5.15.10-2 > > ii libqt5widgets5 5.15.10+dfsg-5 > > ii libqt5xml5 5.15.10+dfsg-5 > > ii libstdc++6 13.2.0-7 > > ii melt 7.22.0-1 > > ii qml-module-org-kde-kcm 5.107.0-1 > > ii qml-module-org-kde-newstuff5.107.0-2 > > ii qml-module-qtgraphicaleffects 5.15.10-2 > > ii qml-module-qtqml-models2 5.15.10+dfsg-2 > > ii qml-module-qtquick-controls5.15.10-2 > > ii qml-module-qtquick-controls2 5.15.10+dfsg-2 > > ii qml-module-qtquick-dialogs 5.15.10-2 > > ii qml-module-qtquick-layouts 5.15.10+dfsg-2 > > ii qml-module-qtquick-window2 5.15.10+dfsg-2 > > ii qml-module-qtquick25.15.10+dfsg-2 > > > > Versions of packages kdenlive recommends: > > ii dvdauthor 0.7.2-2 > > ii dvgrab 3.5+git20160707.1.e46042e-1+b1 > > ii frei0r-plugins 1.8.0-1+b1 > > ii genisoimage9:1.1.11-3.4 > > ii oxygen-icon-theme 5:5.107.0-1 > > ii recordmydesktop0.4.0-1+b1 > > ii swh-plugins0.4.17-3 > > > > Versions of packages kdenlive suggests: > > ii khelpcenter 4:23.08.3-1 > > ii vlc 3.0.20-1+b1 > > > > -- no debconf information > Here is the backtrace: [Thread debugging using libthread_db enabled] Using host libthread_db library
Bug#1058565: emperor: please remove extraneous dependency on python3-future
Source: emperor
Version: 1.0.3+ds-7
Severity: normal
python3-future is deprecated and being removed from the archive.
Please use attached patch to remove it from the packaging
Please check with upstream to update setup.py
Greetings,
Alexandre Detiste
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (501, 'testing'), (450, 'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-5-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff --git a/debian/control b/debian/control
index d8fe69b..2e92f8d 100644
--- a/debian/control
+++ b/debian/control
@@ -14,7 +14,6 @@ Build-Depends: debhelper-compat (= 13),
python3-numpy ,
python3-pandas ,
python3-skbio ,
- python3-future ,
python3-click ,
jsdoc-toolkit ,
python3-notebook ,
@@ -36,7 +35,6 @@ Depends: ${python3:Depends},
python3-click,
python3-pandas,
python3-jinja2,
- python3-future,
python3-skbio,
libjs-jquery-ui
Description: visualizing high-throughput microbial community data
diff --git a/debian/rules b/debian/rules
index c8aa126..dad0938 100755
--- a/debian/rules
+++ b/debian/rules
@@ -11,7 +11,7 @@ export PYBUILD_AFTER_BUILD=python{version} setup.py develop
--install-dir {build
export PYBUILD_BEFORE_INSTALL=rm -rvf {build_dir}/emperor.egg* \
{build_dir}/site.py {build_dir}/easy-install.pth \
- {build_dir}/f* {build_dir}/pasteurize {build_dir}/*.py
+ {build_dir}/f* {build_dir}/*.py
%:
dh $@ --with python3,sphinxdoc --buildsystem=pybuild
diff --git a/debian/tests/control b/debian/tests/control
index 52aca74..5268e03 100644
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -2,7 +2,6 @@ Tests: run-unit-test
Depends: @,
python3-all,
python3-click,
- python3-future,
python3-notebook,
python3-pytest,
Restrictions: allow-stderr, skip-not-installable
diff --git a/setup.py b/setup.py
index 5879203..5aa5fca 100644
--- a/setup.py
+++ b/setup.py
@@ -35,7 +35,7 @@ with open('README.md') as f:
long_description = f.read()
base = ["numpy >= 1.7", "scipy >= 0.17.0", "click", "pandas",
-"scikit-bio >= 0.4.1", "jinja2 >= 2.9", "future"]
+"scikit-bio >= 0.4.1", "jinja2 >= 2.9"]
doc = ["Sphinx", "sphinx-bootstrap-theme", "numpydoc"]
test = ["pep8", "flake8", "nose"]
all_deps = base + doc + test
Bug#1058273: gpredict: FTBFS: dh_install: error: missing files, aborting
tony mancill writes: > So this is very possibly a bug in libreoffice-writer-nogui. Sure seems like it. My guess would be that what files go in what libreoffice binary packages got refactored somehow? Not sure what the point of the nogui package is if it can't be used here any more. [shrug] I don't have any time to chase this right now. Bdale signature.asc Description: PGP signature
Bug#1057613: shed: FTBFS: error: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}
Hi. This is from Alex Sisson, the upstream author: Hi, there's a version to test from https://codeberg.org/alexs/shed , dev branch, please give that a quick test and if you're happy with that and I'll make a 1.16 release. Thanks.
Bug#1058564: biomaj3: depends on deprecated python3-future
Source: biomaj3 Version: 3.1.23-1 Severity: normal Dear Maintainers, This package depends on on Python2->3 transition helper "python3-future" which has now outlived it's usefulness. Please remove it's use. A MR has been submitted upstream to help remove it and more old Python2 constructs. https://github.com/genouest/biomaj/pull/134 Greetings, -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (501, 'testing'), (450, 'unstable'), (400, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-5-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#1058563: Lots of "peer is not from a LAN" messages in syslog
Package: minissdpd Version: 1.6.0-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Looks like bugs #890584 and #901605 are back again. I'm getting lots of "minissdpd[810]: peer xxx.xxx.xxx.xxx:y is not from a LAN" messages in my syslog. The "peer" involved is my WiFi router, if that helps, although this machine is on an Ethernet LAN. - -- System Information: Debian Release: 12.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-14-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages minissdpd depends on: ii debconf [debconf-2.0] 1.5.82 ii init-system-helpers1.65.2 ii libc6 2.36-9+deb12u3 ii libnfnetlink0 1.0.2-2 ii lsb-base 11.6 ii sysvinit-utils [lsb-base] 3.06-4 minissdpd recommends no packages. minissdpd suggests no packages. - -- debconf information: * minissdpd/start_daemon: true minissdpd/why_I_am_here: minissdpd/ip6: false * minissdpd/listen: enp4s0 lxcbr0 -BEGIN PGP SIGNATURE- iQJCBAEBCgAsFiEETZlw4yMXM0sUHntjEvfoZbXi52EFAmV47FAOHHJqbXhAcmpt eC5uZXQACgkQEvfoZbXi52ErPw/8C+olh1a8fQ+2NGyXA9hd74SJJVhB+dINj2Fx OZmwU5KFQ050ugU2UxKpLIgcZ24kn1SYHbejR+BcE+1hk+ToArByolvKAmg0T2xs 3cwcdB7r6q499WUuCUUaGtxsl80o9S9ii0IjAPjyj7a3a7EanHpj1gYykKdcxhVo lpkRBVNx9If2t7d7wjwLnEoGJRHjRxntu+Xya35o4iCbWSmgGZP9Efiqxp99QNJI w2zi3bd0m/H/oaBybI+qpC3YEvfbaUlRzHiFUy2y7c1DWo+C+fS46oFflCUTYMbN pZRh8fPdo0TMo1ERNhMwGFhyhAekGc3X9bfvB0aMM5r/0RkrBmQyHJZjqNoLQIRI YVZ6olV6pp6Dk/f2mIYk8IyLm5H6svvyYQbfOIE5iuhfarXnDmRwU09D/Fn9a3wO Mdm48F5rSv1PaQPsdEDUzvhdADkEvMwBEOqk/9+fSkD5xHAU+/ED8/z2seD/6LrV gmsnBSseOrGIrxJPwfCiypRiP/UTGkq5esxlCdjlLGJ+ab1C9fw7G/WJ7FMtxM4r BFcjeElRxEaXCPSSx5D/FoVbhxmuuxGdGtF/iiqUUcmUYyZpttJxek/JlORZudKH OISsK5jp3elgQSfs3OLAIrv+as+pgI4rXbirzYhfuwv6UJ2Kr5cr0IMlGXCZ/YND v4pT3tc= =XqIl -END PGP SIGNATURE-
Bug#1058562: bullseye-pu: package python-django-imagekit/4.0.2-3+deb11u1
Package: release.debian.org Severity: normal Tags: bullseye User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: python-django-image...@packages.debian.org, sanv...@debian.org Control: affects -1 + src:python-django-imagekit [ Reason ] This release fixes Bug #991650 FTBFS because of failing tests. [ Impact ] Anybody trying to build the package from source will get a build error. [ Tests ] I've checked that the package builds again after the fix. [ Risks ] Low risk. The patch was already tested in the unstable of the time. There are no real code changes in the program itself, only in one of the tests. [ Checklist ] [X] *all* changes are documented in the d/changelog [X] I reviewed all changes and I approve them [X] attach debdiff against the package in (old)stable [X] the issue is verified as fixed in unstable [ Changes ] Minor change to tests/test_sourcegroups.py so that it works again. [ Other info ] I've already made the upload.diff -Nru python-django-imagekit-4.0.2/debian/changelog python-django-imagekit-4.0.2/debian/changelog --- python-django-imagekit-4.0.2/debian/changelog 2020-02-23 16:33:44.0 +0100 +++ python-django-imagekit-4.0.2/debian/changelog 2023-12-12 23:00:00.0 +0100 @@ -1,3 +1,12 @@ +python-django-imagekit (4.0.2-3+deb11u1) bullseye; urgency=medium + + * Team upload. + [ Michael Fladischer ] + * Add patch to avoid triggering path traversal detection in tests. +Closes: #991650. + + -- Santiago Vila Tue, 12 Dec 2023 23:00:00 +0100 + python-django-imagekit (4.0.2-3) unstable; urgency=medium [ Ondřej Nový ] diff -Nru python-django-imagekit-4.0.2/debian/gbp.conf python-django-imagekit-4.0.2/debian/gbp.conf --- python-django-imagekit-4.0.2/debian/gbp.conf2020-02-23 16:33:44.0 +0100 +++ python-django-imagekit-4.0.2/debian/gbp.conf2023-12-12 22:53:34.0 +0100 @@ -1,2 +1,2 @@ [DEFAULT] -debian-branch=debian/master +debian-branch=debian/bullseye diff -Nru python-django-imagekit-4.0.2/debian/patches/0005-Set-filename-in-tests-to-avoid-path-traversal-detect.patch python-django-imagekit-4.0.2/debian/patches/0005-Set-filename-in-tests-to-avoid-path-traversal-detect.patch --- python-django-imagekit-4.0.2/debian/patches/0005-Set-filename-in-tests-to-avoid-path-traversal-detect.patch 1970-01-01 01:00:00.0 +0100 +++ python-django-imagekit-4.0.2/debian/patches/0005-Set-filename-in-tests-to-avoid-path-traversal-detect.patch 2023-12-12 22:55:32.0 +0100 @@ -0,0 +1,29 @@ +From: Michael Fladischer +Date: Sun, 31 Oct 2021 20:48:19 + +Subject: Set filename in tests to avoid path traversal detection (Closes: + #991650). + +--- + tests/test_sourcegroups.py | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/tests/test_sourcegroups.py b/tests/test_sourcegroups.py +index c69b11f..416b964 100644 +--- a/tests/test_sourcegroups.py b/tests/test_sourcegroups.py +@@ -23,7 +23,7 @@ def test_source_saved_signal(): + source_group = ImageFieldSourceGroup(ImageModel, 'image') + receiver = make_counting_receiver(source_group) + source_saved.connect(receiver) +-ImageModel.objects.create(image=File(get_image_file())) ++ImageModel.objects.create(image=File(get_image_file(), name='reference.png')) + eq_(receiver.count, 1) + + +@@ -51,5 +51,5 @@ def test_abstract_model_signals(): + source_group = ImageFieldSourceGroup(AbstractImageModel, 'original_image') + receiver = make_counting_receiver(source_group) + source_saved.connect(receiver) +-ConcreteImageModel.objects.create(original_image=File(get_image_file())) ++ConcreteImageModel.objects.create(original_image=File(get_image_file(), name='reference.png')) + eq_(receiver.count, 1) diff -Nru python-django-imagekit-4.0.2/debian/patches/series python-django-imagekit-4.0.2/debian/patches/series --- python-django-imagekit-4.0.2/debian/patches/series 2020-02-23 16:33:44.0 +0100 +++ python-django-imagekit-4.0.2/debian/patches/series 2023-12-12 22:55:32.0 +0100 @@ -2,3 +2,4 @@ 0002-Disable-usage-of-nose-progressive-as-it-has-not-been.patch 0003-Disable-build-status-image-to-prevent-privacy-breach.patch 0004-Do-not-check-for-existence-if-name-is-None-Closes-95.patch +0005-Set-filename-in-tests-to-avoid-path-traversal-detect.patch
Bug#1058081: nvidia-graphics-drivers: Include systemd power management services and scripts
On 12/12/2023 08.14, Jian-Hong Pan wrote: ... Also, took Fedora's gdm patch "udev: Stick with wayland on hybrid nvidia with vendor driver" [2] > [2]: https://src.fedoraproject.org/rpms/gdm/blob/rawhide/f/0001-udev-Stick-with-wayland-on-hybrid-nvidia-with-vendor.patch If you want that patch applied in Debian, please file a bug against gdm3. systemd-sleep[2781]: /usr/bin/nvidia-sleep.sh: line 33: chvt: command not found I think kbd should be the dependency of nvidia-suspend-common. Yes, will fix that in the next upload. Andreas
Bug#1058034: webkit2gtk: 2.43 fails to build on riscv64
On Tue, Dec 12, 2023 at 04:45:07PM -0500, Jeremy Bícha wrote: > > > I can do a riscv64 test build in a special Ubuntu PPA if you want to > > > turn that into a patch. > > I built with -DENABLE_JIT=OFF -DENABLE_C_LOOP=ON > -DENABLE_WEBASSEMBLY=OFF but the build fails. > https://launchpadlibrarian.net/702273866/buildlog_ubuntu-noble-riscv64.webkit2gtk_2.43.2-1ubuntu0~ppa2_BUILDING.txt.gz Oh, crap ... can you add that information to the upstream bug report? Thanks! Berto
Bug#1058560: libncursesw6: getch(3ncurses) returns -1 with errno unchanged, only documented to return -1 with errno=EINTR
On Tue, Dec 12, 2023 at 11:09:13PM +0100, наб wrote:
> Package: libncursesw6
> Version: 6.4+20231121-1
> Severity: normal
>
> Dear Maintainer,
>
> urlview 1c-1 whose xterm was killed but which didn't die consumes 100% CPU.
> The event loop is for(;;) switch(getch()) ... and ignores -1
If it's going to ignore the error return (while at the same time
manipulating the time delays with mousemask), then this is expected
(mis)behavior.
That's in the manpage -- see below.
> (https://git.sr.ht/~nabijaczleweli/urlview-ng/tree/1c/item/urlview.c#L576).
>
> strace -p:
> read(0, "", 1) = 0
> read(0, "", 1) = 0
> read(0, "", 1) = 0
> read(0, "", 1) = 0
> read(0, "", 1) = 0
> read(0, "", 1) = 0
>
>
> ltrace -p:
> wgetch(0x55e356e14860, 0, 0, 1) = 0x
> wgetch(0x55e356e14860, 0x, 0, 0x) = 0x
> wgetch(0x55e356e14860, 0, 0, 1) = 0x
> wgetch(0x55e356e14860, 0x, 0, 0x) = 0x
> wgetch(0x55e356e14860, 0, 0, 1) = 0x
> wgetch(0x55e356e14860, 0x, 0, 0x) = 0x
> wgetch(0x55e356e14860, 0, 0, 1) = 0x
> wgetch(0x55e356e14860, 0x, 0, 0x) = 0x
>
>
> gdb -p, b ./urlview.c:576:
> (gdb) cont
> Continuing.
>
> Breakpoint 1, main (argc=, argv=) at
> ./urlview.c:576
> 576 int c = getch();
> (gdb) n
> 578 switch(c) {
> (gdb) p c
> $1 = -1
> (gdb) p *__errno_location()
> $3 = 5
> this is EIO. By resetting *__errno_location() = 0 and letting it rip for
> a few more loops, I see it continue to be 0,
> so it just returns 0 but doesn't change errno
> (I'm assuming changing errno is a side-effect of read(),
> which completes successfully but emptily here),
> presumably the EIO is from an earlier refresh to a dead pty.
>
> getch(3ncurses) on bookworm and sid says
> RETURN VALUE
> All routines return the integer ERR upon failure and an integer
> value other than ERR (OK in the case of ungetch) upon successful
> completion.
>
> wgetch returns ERR if the window pointer is null, or if its
> timeout expires without having any data, or if the execution
^^^
> was interrupted by a signal (errno will be set to EINTR).
> so how precisely you're meant to handle this is unclear to me.
>
> The first sentence implies "case ERR: exit(1)",
> but the second implies "case ERR: if(errno != EINTR) exit(1); break"
> to me.
>
> I set no timeouts so I expect that bit to not apply,
> but I read this as the EINTR parenthetical applying to both the
> interruption and timeout cases.
>
> Either way, if errno isn't (re)set, then returning ERR isn't really
> reliable or meaningful i think (lest you "errno=0, getch()" always?
> which kinda sucks).
>
> I see SUSv2 XCURSES say:
> Upon successful completion getch(), mvgetch(), mvwgetch() and
> wgetch() return the single-byte character, KEY_ value, or ERR.
> When in the nodelay mode and no data is available, ERR is returned.
> which makes it silent on the issue.
>
> Reopening its pty fails with EIO, as expected, but consulting stty
> against urlview in a live xterm I see
> speed 38400 baud; rows 54; cols 172; line = 0;
> -brkint -icrnl -imaxbel iutf8
> -onlcr
> -icanon -echo
> so -icanon min=1 time=0, which is by no means a "nodelay" mode,
> and it doesn't have a "timeout" set.
>
> Naturally, setting min=0 time=1 I reproduce the empty-returning read()s,
> and the unchanging errno.
>
> So to this point, I think this just needs disambiguation to the tune of
> "having any data (with errno unchanged)".
>
> Empty read()s from a hung-up teletype aren't covered by the
> documentation. Naturally this is an adversarial reading,
> but it may not be obvious to all readers that these are homologous
> conditions:
> "or if the read from returns empty \(em be it due to a timeout
> expiring with no data or due to a hangup (with errno unchanged),"
>
> In a similar vein, I see a lot of references to a "cbreak mode"
> (sometimes in bold) and a "nocbreak mode" (never in bold).
> I suppose this is a left-over from old berkeley manuals(?),
> but that's not a feature of the Linux teletype driver,
> and according to my notes[1] the CBREAK mode features in [V7, 4.4BSD)
> exclusively, which isn't really useful to the modern reader,
> with the 4.4BSD URM being released close to 30 years ago now.
> The only remnant of this remains in stty(1), but that consistently calls
> it cbreak/-cbreak mapping it to -icanon/icanon. This makes it even more
> jarring to a modern reader.
>
> Anyway, is this behaviour expected, and is the loop best-served as
> for(;;) switch(errno=0, getch()) case ERR: if(errno != EINTR) { err = true;
>
Bug#1058561: auto-apt-proxy: for hostname `apt-proxy` resolving to both an IPv4 and IPv6 address, only the IPv6 address is attempted
Package: auto-apt-proxy
Version: 14.1
Severity: normal
Dear Maintainer,
Hello,
in my environment the name `apt-proxy` resolves to both an IPv4 and an
IPv6 address.
In `/usr/bin/auto-apt-proxy` the hostname `apt-proxy` is resolved via
the following command:
getent hosts apt-proxy
But the above command omits all IPv4 addresses, if at least one IPv6
address is found.
This seems to be the quirky - but intended - behavior of the `getent hosts`
command: https://sourceware.org/bugzilla/show_bug.cgi?id=10859
This prevents `auto-apt-proxy` from working in environments, where IPv6
is disabled for some reason (e.g. a docker instance started by
gitlab-runner configured for IPv4-only).
There, IPv6 addresses are returnd by `getent hosts`, but the IPv4-only
network setup renders these addresses unreachable.
Maybe something like the following command could be useful instead?
getent ahosts ix.de | awk '{print $1}' | sort --reverse | uniq
This should return all IPv4 and IPv6 addresses for a given hostname.
`--reverse` seems to result in IPv6 addresses being on top.
Cheers,
Lars
-- System Information:
Debian Release: trixie/sid
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
Versions of packages auto-apt-proxy depends on:
ii apt 2.7.6
Versions of packages auto-apt-proxy recommends:
ii busybox 1:1.36.1-3.1
ii iproute2 6.5.0-4
auto-apt-proxy suggests no packages.
-- no debconf information
Bug#1058273: gpredict: FTBFS: dh_install: error: missing files, aborting
On Tue, Dec 12, 2023 at 09:35:44AM +0100, Lucas Nussbaum wrote: > Source: gpredict > Version: 2.3-115-g0f3beb6-2 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20231212 ftbfs-trixie It feels slightly icky because it pulls in a much larger set of build-deps, but this FTBFS is easily fixed by relaxing the B-D-I on libreoffice-writer-nogui to libreoffice-writer. So this is very possibly a bug in libreoffice-writer-nogui. I went ahead and pushed a patch to packaging repo. If someone feels strongly about keeping the build-deps small for this arch-all package and sticking with libreoffice-writer-nogui, you can reproduce by starting with a clean chroot and running this bit of the build: soffice --writer --headless --convert-to pdf doc/um/gpredict-user-manual.odt And adding build-deps until you no longer get this error. Error: source file could not be loaded I will try to take another look at it before uploading. Cheers, tony
Bug#899245: kgb-bot: support for password-protected channels
Control: tags -1 +patch
On 2018-05-21 16:01:59, Yves-Alexis Perez wrote:
> subject mostly says it all, but it'd be nice if KGB could support
> password-protected IRC channels for notifications.
The library backing KGB does support it, so it seems it's only a matter
of a few lines patch:
https://salsa.debian.org/kgb-team/kgb/-/merge_requests/8
Also attached.
Please test and report back here or, preferably, in the above merge request.
a.
--
The secret of life is to have no fear; it's the only way to function.
- Stokely Carmichael
>From e904a049138a0cbae7ae9e72ecc0f65f9579837f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?=
Date: Tue, 12 Dec 2023 16:33:35 -0500
Subject: [PATCH] channel secret support (Closes: #899245)
---
script/kgb-bot | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/script/kgb-bot b/script/kgb-bot
index 34ffdf5..6bc422a 100755
--- a/script/kgb-bot
+++ b/script/kgb-bot
@@ -296,7 +296,7 @@ sub read_conf ($) {
die "Missing channel name at channel\n" unless ( $_->{name} );
die "Invalid network at channel " . $_->{name} . "\n"
unless ( $_->{network} and $conf->{networks}{ $_->{network} } );
-push @{ $conf->{networks}{ $_->{network} }{channels} }, $_->{name};
+$conf->{networks}{ $_->{network} }{channels}{$_->{name}} = $_->{secret};
my $chanid = KGB->get_chanid( $_->{network}, $_->{name} );
die "Invalid repos key at channel $chanid\n"
unless $_->{broadcast}
@@ -947,8 +947,8 @@ sub _irc_reconnect {
}
else {
my ( %newchan, %oldchan, %allchan );
-%newchan = map( { $_ => 1 } @{ $new->{channels} } );
-%oldchan = map( { $_ => 1 } @{ $old->{channels} } );
+%newchan = map( { $_ => 1 } %{ $new->{channels} } );
+%oldchan = map( { $_ => 1 } %{ $old->{channels} } );
%allchan = ( %newchan, %oldchan );
foreach my $chan ( keys %allchan ) {
if ( $newchan{$chan} and !$oldchan{$chan} ) {
@@ -1094,7 +1094,8 @@ sub add_channel ($$$) {
unless (exists $KGB::config->{networks}{$network});
return if (exists $KGB::config->{chanidx}{$chanid});
-push @{ $KGB::config->{networks}{$network}{channels} }, $channel;
+# secret-less
+$KGB::config->{networks}{$network}{channels}{$channel} = '';
$KGB::config->{chanidx}{$chanid} = {
name => $channel,
network => $network,
@@ -1124,11 +1125,12 @@ sub irc_001 {
my ( $kernel, $sender ) = @_[ KERNEL, SENDER ];
my $net = get_net($sender);
my $channels = $KGB::config->{networks}{$net}{channels};
+my @channel_names = keys %{$channels};
# Get the component's object at any time by accessing the heap of
# the SENDER
KGB->out( "Connected to $net (", $sender->get_heap->server_name(), ")\n" );
-KGB->out( "Joining @$channels...\n" ) if ($channels);
+KGB->out( "Joining @channel_names...\n" ) if ($channels);
undef;
}
--
GitLab
Bug#1057431: fakeupstream.cgi: add support for static.rust-lang.org
Hi Bart, > That should be suitable for a watch file. Right? Yes, while that is true, the page is updated frequently with older versions replaced with the new version. In Debian, usually, we can't package the latest version as quickly as possible due to bootstrapping requirements. Hence, a fakeupstream service is needed to retrieve a non-latest version from the upstream. Also, another use-case might be, you want a specific nightly or beta to test a certain regression. Since that page does not list the previous releases, it would be difficult to rely on it to retrieve a previous beta using uscan by specifying `--download-version`. Thanks, Zixing On Tue, Dec 12, 2023 at 2:58 PM Bart Martens wrote: > > Hi Zixing, the source code and signature are also advertised here: > https://forge.rust-lang.org/infra/other-installation-methods.html#source-code > That should be suitable for a watch file. Right? > > > On Tue, Dec 05, 2023 at 02:44:06PM -0700, Zixing Liu wrote: > > Hi Bart, > > > > > The link https://static.rust-lang.org/dist displays an error in xml > > > format. > > > > This is because this website is hosted on AWS S3 and is machine-readable > > only. > > To list the files, you need to either use an S3-compatible tool or visit > > https://static.rust-lang.org/?prefix=dist/ to see the file listing in > > XML format. > > > > > Can I view an example of a package in Debian that can be watched with > > > such extension of fakeupstream? > > > > This fakeupstream service is intended for > > https://tracker.debian.org/pkg/rustc. > > Because it needs to download the signed source tarball from > > https://static.rust-lang.org. > > > > Thanks, > > Zixing > > > > On Tue, Dec 5, 2023 at 1:46 PM Bart Martens wrote: > > > > > > Hello Zixing Liu, > > > > > > Can I view an example of a package in Debian that can be watched with such > > > extension of fakeupstream? The link https://static.rust-lang.org/dist > > > displays > > > an error in xml format. A real example would help me understand the > > > context. > > > > > > Ciao, > > > > > > Bart > > > > > > > > > On Mon, Dec 04, 2023 at 03:32:39PM -0700, Zixing Liu wrote: > > > > Package: qa.debian.org > > > > Severity: wishlist > > > > Tags: patch > > > > X-Debbugs-Cc: zixing@canonical.com > > > > > > > > Hi Debian QA Team, > > > > > > > > I would like to see a fakeupstream service implemented for > > > > https://static.rust-lang.org/dist so that > > > > > --
Bug#1058560: libncursesw6: getch(3ncurses) returns -1 with errno unchanged, only documented to return -1 with errno=EINTR
Package: libncursesw6
Version: 6.4+20231121-1
Severity: normal
Dear Maintainer,
urlview 1c-1 whose xterm was killed but which didn't die consumes 100% CPU.
The event loop is for(;;) switch(getch()) ... and ignores -1
(https://git.sr.ht/~nabijaczleweli/urlview-ng/tree/1c/item/urlview.c#L576).
strace -p:
read(0, "", 1) = 0
read(0, "", 1) = 0
read(0, "", 1) = 0
read(0, "", 1) = 0
read(0, "", 1) = 0
read(0, "", 1) = 0
ltrace -p:
wgetch(0x55e356e14860, 0, 0, 1) = 0x
wgetch(0x55e356e14860, 0x, 0, 0x) = 0x
wgetch(0x55e356e14860, 0, 0, 1) = 0x
wgetch(0x55e356e14860, 0x, 0, 0x) = 0x
wgetch(0x55e356e14860, 0, 0, 1) = 0x
wgetch(0x55e356e14860, 0x, 0, 0x) = 0x
wgetch(0x55e356e14860, 0, 0, 1) = 0x
wgetch(0x55e356e14860, 0x, 0, 0x) = 0x
gdb -p, b ./urlview.c:576:
(gdb) cont
Continuing.
Breakpoint 1, main (argc=, argv=) at
./urlview.c:576
576 int c = getch();
(gdb) n
578 switch(c) {
(gdb) p c
$1 = -1
(gdb) p *__errno_location()
$3 = 5
this is EIO. By resetting *__errno_location() = 0 and letting it rip for
a few more loops, I see it continue to be 0,
so it just returns 0 but doesn't change errno
(I'm assuming changing errno is a side-effect of read(),
which completes successfully but emptily here),
presumably the EIO is from an earlier refresh to a dead pty.
getch(3ncurses) on bookworm and sid says
RETURN VALUE
All routines return the integer ERR upon failure and an integer
value other than ERR (OK in the case of ungetch) upon successful
completion.
wgetch returns ERR if the window pointer is null, or if its
timeout expires without having any data, or if the execution
was interrupted by a signal (errno will be set to EINTR).
so how precisely you're meant to handle this is unclear to me.
The first sentence implies "case ERR: exit(1)",
but the second implies "case ERR: if(errno != EINTR) exit(1); break"
to me.
I set no timeouts so I expect that bit to not apply,
but I read this as the EINTR parenthetical applying to both the
interruption and timeout cases.
Either way, if errno isn't (re)set, then returning ERR isn't really
reliable or meaningful i think (lest you "errno=0, getch()" always?
which kinda sucks).
I see SUSv2 XCURSES say:
Upon successful completion getch(), mvgetch(), mvwgetch() and
wgetch() return the single-byte character, KEY_ value, or ERR.
When in the nodelay mode and no data is available, ERR is returned.
which makes it silent on the issue.
Reopening its pty fails with EIO, as expected, but consulting stty
against urlview in a live xterm I see
speed 38400 baud; rows 54; cols 172; line = 0;
-brkint -icrnl -imaxbel iutf8
-onlcr
-icanon -echo
so -icanon min=1 time=0, which is by no means a "nodelay" mode,
and it doesn't have a "timeout" set.
Naturally, setting min=0 time=1 I reproduce the empty-returning read()s,
and the unchanging errno.
So to this point, I think this just needs disambiguation to the tune of
"having any data (with errno unchanged)".
Empty read()s from a hung-up teletype aren't covered by the
documentation. Naturally this is an adversarial reading,
but it may not be obvious to all readers that these are homologous
conditions:
"or if the read from returns empty \(em be it due to a timeout
expiring with no data or due to a hangup (with errno unchanged),"
In a similar vein, I see a lot of references to a "cbreak mode"
(sometimes in bold) and a "nocbreak mode" (never in bold).
I suppose this is a left-over from old berkeley manuals(?),
but that's not a feature of the Linux teletype driver,
and according to my notes[1] the CBREAK mode features in [V7, 4.4BSD)
exclusively, which isn't really useful to the modern reader,
with the 4.4BSD URM being released close to 30 years ago now.
The only remnant of this remains in stty(1), but that consistently calls
it cbreak/-cbreak mapping it to -icanon/icanon. This makes it even more
jarring to a modern reader.
Anyway, is this behaviour expected, and is the loop best-served as
for(;;) switch(errno=0, getch()) case ERR: if(errno != EINTR) { err = true;
break 2; }
? Or is there a better way to drive this?
Best,
наб
[1]:
https://lfs.nabijaczleweli.xyz/0012-groff-mdoc-*q-spacing/2022-10-23-stty.1-preprint/a4.pdf
pp. 20, 67-68
-- System Information:
Debian Release: 12.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-9-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags:
Bug#1056233: Issue isn't what's described
Hi, The issue described in this bug report is invalid, however, there was another one which I just fixed (adding Fix_invalid_assert_calls.patch). I'll use the same bug report then. Cheers, Thomas Goirand (zigo)
Bug#1058034: webkit2gtk: 2.43 fails to build on riscv64
On Mon, Dec 11, 2023 at 10:41 AM Alberto Garcia wrote: >> On Mon, Dec 11, 2023 at 10:23:36AM -0500, Jeremy Bícha wrote: > > > Considering that the upstream bug (265082) has been open for > > > a month maybe we can work this around with -DENABLE_JIT=OFF > > > -DENABLE_C_LOOP=ON (I haven't tested it). > > > > I can do a riscv64 test build in a special Ubuntu PPA if you want to > > turn that into a patch. I built with -DENABLE_JIT=OFF -DENABLE_C_LOOP=ON -DENABLE_WEBASSEMBLY=OFF but the build fails. https://launchpadlibrarian.net/702273866/buildlog_ubuntu-noble-riscv64.webkit2gtk_2.43.2-1ubuntu0~ppa2_BUILDING.txt.gz Thank you, Jeremy Bícha
Bug#1057791: python-hiredis: Not built against system libhiredis library but claimed so
在 2023-12-12星期二的 12:23 +，Chris Lamb写道： > Boyuan Yang wrote: > > > Package python-hiredis claimed to be using system libhiredis library > > through > > a custom patch. However, the built binary library is not linked against > > libhiredis […] > > Oh, well spotted. How did you find this? :) > > Will look at this once #107 is address. (I suspect that patching > out the "vendor/hiredis/%s.c" glob etc. will be the place to start, > though.) Might be better to rm -rf vendor/hiredis/* in execute_before_dh_auto_configure to avoid vendored source code from being accidentally compiled. I believe a coordinated fix with libhiredis transition [2] is needed. But anyway since both packages are handled by you, that should not be a issue. Thanks, Boyuan Yang [2] https://release.debian.org/transitions/html/auto-hiredis.html signature.asc Description: This is a digitally signed message part
Bug#1058480: python-disptrans: please (temporarily) drop python3-numba dependencies
Source: python-disptrans Version: 0.0.1-2 Followup-For: Bug #1058480 X-Debbugs-Cc: kd8...@gmail.com Hi Graham, Upstream relies on the numba for its functions. In the future I will include numba in recommends as you suggested. Thank you, Yogeswaran.
Bug#1058559: bullseye-pu: package vlfeat/0.9.21+dfsg0-6+deb11u1
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: vlf...@packages.debian.org, sanv...@debian.org
Control: affects -1 + src:vlfeat
[ Reason ]
This release fixes Bug #991066: FTBFS with new imagemagick.
The bug was bullseye-ignored to avoid the package being removed,
but this upload for bullseye was still missing.
[ Impact ]
Anybody trying to build the package from source will get a build error.
[ Tests ]
I've checked that the package builds again after the fix.
[ Risks ]
Low risk. The patch was already tested in the unstable of the time.
[ Checklist ]
[X] *all* changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in (old)stable
[X] the issue is verified as fixed in unstable
[ Changes ]
Minor change to debian/rules so that the package builds again.
[ Other info ]
I've already made the upload.diff -Nru vlfeat-0.9.21+dfsg0/debian/changelog
vlfeat-0.9.21+dfsg0/debian/changelog
--- vlfeat-0.9.21+dfsg0/debian/changelog2020-02-08 06:39:32.0
+0100
+++ vlfeat-0.9.21+dfsg0/debian/changelog2023-12-12 21:30:00.0
+0100
@@ -1,3 +1,10 @@
+vlfeat (0.9.21+dfsg0-6+deb11u1) bullseye; urgency=medium
+
+ * Team upload.
+ * Apply patch by Dennis Filder to fix build error. Closes: #991066.
+
+ -- Santiago Vila Tue, 12 Dec 2023 21:30:00 +0100
+
vlfeat (0.9.21+dfsg0-6) unstable; urgency=medium
* Team upload.
diff -Nru vlfeat-0.9.21+dfsg0/debian/rules vlfeat-0.9.21+dfsg0/debian/rules
--- vlfeat-0.9.21+dfsg0/debian/rules2020-02-08 06:39:32.0 +0100
+++ vlfeat-0.9.21+dfsg0/debian/rules2023-12-12 21:26:17.0 +0100
@@ -10,12 +10,16 @@
# grab the API version from the library SONAME
API_VERSION = $(shell objdump -p bin/*/libvl.so | perl -ne
'if(/^\s+SONAME\s+libvl.so./p) {print $${^POSTMATCH}; exit;}')
+IMAGEMAGICK_POLICY := /etc/$(shell convert -version|sed -n '/^Version:
/s@Version: ImageMagick \([[:digit:]]\+\)\..*@ImageMagick-\1@p')/policy.xml
+
%:
dh $@
override_dh_auto_build:
- make PYTHON=python3 MKOCTFILE=`which mkoctfile` VERB=1 CFLAGS+=-g all
doc
-
+ mkdir -p debian/tmp/ImageMagick
+ sed -e '//s@"none"@"read|write"@' "$(IMAGEMAGICK_POLICY)" >
debian/tmp/ImageMagick/policy.xml
+ make XDG_CONFIG_HOME="$(shell pwd)/debian/tmp" PYTHON=python3
MKOCTFILE=`which mkoctfile` VERB=1 CFLAGS+=-g all doc
+ rm -Rf debian/tmp/ImageMagick
override_dh_auto_install: $(addprefix install/,data $(wildcard toolbox/*))
cp bin/*/libvl.so libvl.so.$(VERSION)
Bug#1058554: skimage: FTBFS: intersphinx inventory './_intersphinx/sklearn-objects.inv' not fetchable due to : [Errno 2] No such file or directory: '/<>/doc/sou
Source: skimage Version: 0.22.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/doc' > python3.11 tools/build_modref_templates.py > outdir: > 19 files written > Build API docs...done. > python3.11 -m sphinx -b html -d build/doctrees -D mathjax_path=MathJax.js > source build/html > Running Sphinx v7.2.6 > /usr/lib/python3/dist-packages/sphinx_gallery/sphinx_compatibility.py:71: > RemovedInSphinx80Warning: > > The alias 'sphinx.util.status_iterator' is deprecated, use > 'sphinx.util.display.status_iterator' instead. Check CHANGES for Sphinx API > modifications. > > making output directory... done > [autosummary] generating autosummary for: about/code_of_conduct.md, > about/index.rst, about/report_handling_manual.rst, about/values.md, > api/api.rst, api/skimage.color.rst, api/skimage.data.rst, > api/skimage.draw.rst, api/skimage.exposure.rst, api/skimage.feature.rst, ..., > user_guide/index.rst, user_guide/install.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/visualization.rst > loading intersphinx inventory from > /usr/share/doc/python3.9/html/objects.inv... > loading intersphinx inventory from ./_intersphinx/numpy-objects.inv... > WARNING: failed to reach any of the inventories with the following issues: > intersphinx inventory '/usr/share/doc/python3.9/html/objects.inv' not > fetchable due to : [Errno 2] No such file or > directory: '/usr/share/doc/python3.9/html/objects.inv' > loading intersphinx inventory from ./_intersphinx/scipy-objects.inv... > WARNING: failed to reach any of the inventories with the following issues: > intersphinx inventory './_intersphinx/scipy-objects.inv' not fetchable due to > : [Errno 2] No such file or directory: > '/<>/doc/source/./_intersphinx/scipy-objects.inv' > WARNING: failed to reach any of the inventories with the following issues: > intersphinx inventory './_intersphinx/numpy-objects.inv' not fetchable due to > : [Errno 2] No such file or directory: > '/<>/doc/source/./_intersphinx/numpy-objects.inv' > loading intersphinx inventory from ./_intersphinx/sklearn-objects.inv... > loading intersphinx inventory from https://matplotlib.org/objects.inv... > WARNING: failed to reach any of the inventories with the following issues: > intersphinx inventory './_intersphinx/sklearn-objects.inv' not fetchable due > to : [Errno 2] No such file or directory: > '/<>/doc/source/./_intersphinx/sklearn-objects.inv' > intersphinx inventory has moved: https://matplotlib.org/objects.inv -> > https://matplotlib.org/stable/objects.inv > generating gallery... > Using Sphinx-Gallery to convert rst text blocks to markdown for .ipynb files. > generating gallery for auto_examples... > generating gallery for auto_examples/data... > [2Kgenerating gallery for auto_examples/numpy_operations... [ 25%] > plot_camera_numpy.py > [2Kgenerating gallery for auto_examples/numpy_operations... [ 50%] > plot_structuring_elements.py > [2Kgenerating gallery for auto_examples/numpy_operations... [ 75%] > plot_view_as_blocks.py > [2Kgenerating gallery for auto_examples/numpy_operations... [100%] > plot_footprint_decompositions.py > > [2Kgenerating gallery for auto_examples/color_exposure... [ 11%] > plot_rgb_to_gray.py > [2Kgenerating gallery for auto_examples/color_exposure... [ 22%] > plot_rgb_to_hsv.py > [2Kgenerating gallery for auto_examples/color_exposure... [ 33%] > plot_histogram_matching.py > [2Kgenerating gallery for auto_examples/color_exposure... [ 44%] > plot_adapt_rgb.py > [2Kgenerating gallery for auto_examples/color_exposure... [ 56%] > plot_ihc_color_separation.py > [2Kgenerating gallery for auto_examples/color_exposure... [ 67%] > plot_regional_maxima.py > [2Kgenerating gallery for auto_examples/color_exposure... [ 78%] > plot_log_gamma.py > [2Kgenerating gallery for auto_examples/color_exposure... [ 89%] > plot_equalize.py > [2Kgenerating gallery for auto_examples/color_exposure... [100%] > plot_tinting_grayscale_images.py > > [2Kgenerating gallery for auto_examples/edges... [ 8%] plot_contours.py > [2Kgenerating gallery for auto_examples/edges... [ 15%] plot_convex_hull.py > [2Kgenerating gallery for auto_examples/edges... [ 23%] plot_canny.py > [2Kgenerating gallery for auto_examples/edges... [ 31%] > plot_marching_cubes.py > [2Kge
Bug#1058558: seqkit: FTBFS: make: *** [debian/rules:8: binary] Error 25
Source: seqkit Version: 2.3.1+ds-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --buildsystem=golang --with=golang --builddirectory=build # > --sourcedirectory=seqkit >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 install -trimpath -v -p 8 > github.com/shenwei356/seqkit/benchmark github.com/shenwei356/seqkit/seqkit > github.com/shenwei356/seqkit/seqkit/cmd > src/github.com/shenwei356/seqkit/seqkit/cmd/pair.go:32:2: cannot find package > "github.com/pkg/errors" in any of: > /usr/lib/go-1.21/src/github.com/pkg/errors (from $GOROOT) > /<>/build/src/github.com/pkg/errors (from $GOPATH) > dh_auto_build: error: cd build && go install -trimpath -v -p 8 > github.com/shenwei356/seqkit/benchmark github.com/shenwei356/seqkit/seqkit > github.com/shenwei356/seqkit/seqkit/cmd returned exit code 1 > make: *** [debian/rules:8: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/12/12/seqkit_2.3.1+ds-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1058557: msolve: FTBFS: ! LaTeX Error: Unknown option 'hyperef' for package xcolor.
Source: msolve
Version: 0.6.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd doc && pdflatex msolve-tutorial && \
> biber msolve-tutorial && \
> pdflatex msolve-tutorial && \
> pdflatex msolve-tutorial
> This is pdfTeX, Version 3.141592653-2.6-1.40.25 (TeX Live 2023/Debian)
> (preloaded format=pdflatex)
> restricted \write18 enabled.
> entering extended mode
> (./msolve-tutorial.tex
> LaTeX2e <2023-11-01>
> L3 programming layer <2023-11-09>
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrartcl.cls
> Document Class: scrartcl 2023/07/07 v3.41 KOMA-Script document class (article)
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrkbase.sty
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrbase.sty
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlfile.sty
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlfile-hook.sty
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlogo.sty)))
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)))
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/tocbasic.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrsize11pt.clo)
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/typearea.sty))
> (/usr/share/texlive/texmf-dist/tex/generic/iftex/ifpdf.sty
> (/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> (/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def)
> (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf))
> (/usr/share/texlive/texmf-dist/tex/generic/babel/locale/en/babel-english.tex)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
> For additional information on amsmath, use the `?' option.
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amscls/amsthm.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/xpatch/xpatch.sty
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty
> (/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-pdftex.def))
> (/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/etoolbox/etoolbox.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg)
>
> Package xcolor Warning: Package option `usenames' is obsolete and ignored on
> in
> put line 266.
>
>
> ! LaTeX Error: Unknown option 'hyperef' for package xcolor.
>
> For immediate help type H .
> ...
>
> l.266 \edef
>\Gin@driver{\Gin@driver}
> ?
> ! Emergency stop.
> ...
>
> l.266 \edef
>\Gin@driver{\Gin@driver}
> ! ==> Fatal error occurred, no output PDF file produced!
> Transcript written on msolve-tutorial.log.
> make[1]: *** [debian/rules:13: execute_after_dh_auto_build] Error 1
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/msolve_0.6.1-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
Bug#1058556: binutils-or1k-elf: FTBFS: make[1]: *** [debian/rules:29: src] Error 1
Source: binutils-or1k-elf Version: 1.0.9 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary -Dsrc -Bbld >debian/rules execute_before_dh_update_autotools_config > make[1]: Entering directory '/<>' > tar -xf /usr/src/binutils/binutils-*.tar.xz --transform='s|[^/]*|src|' > patch -dsrc -p1 < 0001-readelf-typos-in-user-messages.patch > patching file binutils/readelf.c > Reversed (or previously applied) patch detected! Assume -R? [n] > Apply anyway? [n] > Skipping patch. > 2 out of 2 hunks ignored -- saving rejects to file binutils/readelf.c.rej > make[1]: *** [debian/rules:29: src] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/12/12/binutils-or1k-elf_1.0.9_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1058555: parallel: FTBFS: /usr/bin/install: cannot stat './parallel_cheat_bw.pdf': No such file or directory
Source: parallel Version: 20221122+ds-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/src' > rm "/<>/debian/parallel/usr/bin"/sem || true > rm: cannot remove '/<>/debian/parallel/usr/bin/sem': No such > file or directory > ln -s parallel "/<>/debian/parallel/usr/bin"/sem > make[4]: Leaving directory '/<>/src' > Error: source file could not be loaded > /usr/bin/mkdir -p '/<>/debian/parallel/usr/share/doc/parallel' > /usr/bin/install -c -m 644 parallel.html env_parallel.html sem.html sql.html > niceload.html parallel_examples.html parallel_tutorial.html > parallel_book.html parallel_design.html parallel_alternatives.html > parcat.html parset.html parsort.html parallel.texi env_parallel.texi sem.texi > sql.texi niceload.texi parallel_examples.texi parallel_tutorial.texi > parallel_book.texi parallel_design.texi parallel_alternatives.texi > parcat.texi parset.texi parsort.texi parallel.rst env_parallel.rst sem.rst > sql.rst niceload.rst parallel_examples.rst parallel_tutorial.rst > parallel_book.rst parallel_design.rst parallel_alternatives.rst parcat.rst > parset.rst parsort.rst parallel.pdf > '/<>/debian/parallel/usr/share/doc/parallel' > /usr/bin/install -c -m 644 env_parallel.pdf sem.pdf sql.pdf niceload.pdf > parallel_examples.pdf parallel_tutorial.pdf parallel_book.pdf > parallel_design.pdf parallel_alternatives.pdf parcat.pdf parset.pdf > parsort.pdf ./parallel_cheat_bw.pdf parallel_options_map.pdf > '/<>/debian/parallel/usr/share/doc/parallel' > /usr/bin/install: cannot stat './parallel_cheat_bw.pdf': No such file or > directory > make[3]: *** [Makefile:459: install-docDATA] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/12/12/parallel_20221122+ds-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1058553: node-js-sdsl: FTBFS: TypeError: Cannot set property constructor of [object Object] which has only a getter
Source: node-js-sdsl
Version: 4.1.4-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> debian/build_modules/ttypescript/bin/tsc src/index.ts --downlevelIteration
> --declaration --module commonjs --target es5 --outDir dist/cjs
> /<>/debian/build_modules/ttypescript/lib/loadTypescript.js:13
> function __() { this.constructor = d; }
> ^
>
> TypeError: Cannot set property constructor of [object Object] which has only
> a getter
> at new __
> (/<>/debian/build_modules/ttypescript/lib/loadTypescript.js:13:42)
> at __extends
> (/<>/debian/build_modules/ttypescript/lib/loadTypescript.js:14:84)
> at
> /<>/debian/build_modules/ttypescript/lib/loadTypescript.js:65:5
> at Object.
> (/<>/debian/build_modules/ttypescript/lib/loadTypescript.js:100:2)
> at Module._compile (node:internal/modules/cjs/loader:1356:14)
> at Module._extensions..js (node:internal/modules/cjs/loader:1414:10)
> at Module.load (node:internal/modules/cjs/loader:1197:32)
> at Module._load (node:internal/modules/cjs/loader:1013:12)
> at Module.require (node:internal/modules/cjs/loader:1225:19)
> at require (node:internal/modules/helpers:177:18)
>
> Node.js v18.19.0
> make[1]: *** [debian/rules:13: override_dh_auto_build] Error 1
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/node-js-sdsl_4.1.4-2_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
Bug#1058552: science.js: FTBFS: SyntaxError: Error parsing /<>/package.json: Unexpected end of JSON input
Source: science.js
Version: 1.9.3+dfsg-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> cat src/core/core.js src/core/ascending.js src/core/constants.js
> src/core/expm1.js src/core/functor.js src/core/hypot.js src/core/quadratic.js
> src/core/zeroes.js >> science.core.js
> cat src/lin/lin.js src/lin/decompose.js src/lin/cross.js src/lin/dot.js
> src/lin/length.js src/lin/normalize.js src/lin/determinant.js
> src/lin/gaussjordan.js src/lin/inverse.js src/lin/multiply.js
> src/lin/transpose.js src/lin/tridag.js >> science.lin.js
> cat src/stats/stats.js src/stats/bandwidth.js src/stats/distance.js
> src/stats/erf.js src/stats/phi.js src/stats/kernel.js src/stats/kde.js
> src/stats/kmeans.js src/stats/hcluster.js src/stats/iqr.js src/stats/loess.js
> src/stats/mean.js src/stats/median.js src/stats/mode.js
> src/stats/quantiles.js src/stats/variance.js src/stats/distribution.js
> src/stats/distribution/gaussian.js >> science.stats.js
> cat science.core.js science.lin.js science.stats.js >> science.v1.js
> uglifyjs < science.v1.js > science.v1.min.js
> node src/package.js > package.json
> node:internal/modules/package_json_reader:92
> throw error;
> ^
>
> SyntaxError: Error parsing /<>/package.json: Unexpected end of
> JSON input
> at parse ()
> at read (node:internal/modules/package_json_reader:79:16)
> at readPackage (node:internal/modules/package_json_reader:140:10)
> at readPackageScope (node:internal/modules/package_json_reader:157:19)
> at shouldUseESMLoader (node:internal/modules/run_main:77:15)
> at Function.executeUserEntryPoint [as runMain]
> (node:internal/modules/run_main:122:24)
> at node:internal/main/run_main_module:28:49 {
> path: '/<>/package.json'
> }
>
> Node.js v18.19.0
> make[2]: *** [Makefile:80: package.json] Error 1
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/science.js_1.9.3+dfsg-3_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
Bug#1058551: git-buildpackage: FTBFS: make[2]: *** [Makefile:22: syntax-check] Error 1
Source: git-buildpackage Version: 0.9.32 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > make > make[2]: Entering directory '/<>' > flake8 > ./tests/02_test_upstream_source_tar_unpack.py:58:20: E721 do not compare > types, for exact checks use `is` / `is not`, for instance checks use > `isinstance()` > make[2]: *** [Makefile:22: syntax-check] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/12/12/git-buildpackage_0.9.32_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1058550: autopkgtest: FTBFS: make[1]: *** [debian/rules:38: override_dh_auto_test] Error 1
Source: autopkgtest Version: 5.31.1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > if type pyflakes3 >/dev/null 2>&1; then tests/pyflakes; else echo "pyflakes3 > not available, skipping"; fi > /<>/lib/autopkgtest_qemu.py:48:1: 'typing.List' imported but > unused > /<>/lib/testdesc.py:29:1: 'typing.Dict' imported but unused > /<>/lib/testdesc.py:29:1: 'typing.FrozenSet' imported but unused > /<>/lib/testdesc.py:29:1: 'typing.Union' imported but unused > /<>/tools/autopkgtest-build-qemu:41:1: 'typing.Any' imported but > unused > make[1]: *** [debian/rules:38: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/12/12/autopkgtest_5.31.1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1058549: plastex: FTBFS: make[1]: *** [debian/rules:13: execute_after_dh_auto_build] Error 2
Source: plastex Version: 3.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > export PYTHONPATH=/<>/.pybuild/cpython3_3.12_plastex/build > /<>/.pybuild/cpython3_3.11_plastex/build; \ > export > TEXINPUTS=.:/<>/Doc/commontex:/<>/Doc/texinputs; \ > cd Doc; \ > /<>/.pybuild/cpython3_3.12_plastex/build > /<>/.pybuild/cpython3_3.11_plastex/build/../scripts/plastex > --mathjax-url=mathjax/MathJax.js?config=TeX-AMS_CHTML plastex.tex > /bin/sh: 1: export: /<>/.pybuild/cpython3_3.11_plastex/build: > bad variable name > make[1]: *** [debian/rules:13: execute_after_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2023/12/12/plastex_3.0-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1058544: sahara-plugin-spark: FTBFS: AttributeError: 'ConfigHelperUtilsTest' object has no attribute 'assertDictContainsSubset'
Source: sahara-plugin-spark Version: 10.0.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > make[1]: pyversions: No such file or directory > py3versions: no X-Python3-Version in control file, using supported versions > pkgos-dh_auto_install --no-py2 --in-tmp > + PKGOS_IN_TMP=no > + echo WARNING: --no-py2 is deprecated and always on. > WARNING: --no-py2 is deprecated and always on. > + shift > + PKGOS_IN_TMP=yes > + shift > + dpkg-parsechangelog -SSource > + SRC_PKG_NAME=sahara-plugin-spark > + echo sahara-plugin-spark > + sed s/python-// > + PY_MODULE_NAME=sahara-plugin-spark > + py3versions -vr > + PYTHON3S=3.12 3.11 > + [ yes = yes ] > + TARGET_DIR=tmp > + pwd > + python3.12 setup.py install --install-layout=deb --root > /<>/debian/tmp > /usr/lib/python3/dist-packages/setuptools/dist.py:744: > SetuptoolsDeprecationWarning: Invalid dash-separated options > !! > > > > Usage of dash-separated 'description-file' will not be supported in > future > versions. Please use the underscore name 'description_file' instead. > > This deprecation is overdue, please update your project and remove > deprecated > calls to avoid build errors in the future. > > See > https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for > details. > > > > !! > opt = self.warn_dash_deprecation(opt, section) > /usr/lib/python3/dist-packages/setuptools/dist.py:744: > SetuptoolsDeprecationWarning: Invalid dash-separated options > !! > > > > Usage of dash-separated 'python-requires' will not be supported in > future > versions. Please use the underscore name 'python_requires' instead. > > This deprecation is overdue, please update your project and remove > deprecated > calls to avoid build errors in the future. > > See > https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for > details. > > > > !! > opt = self.warn_dash_deprecation(opt, section) > /usr/lib/python3/dist-packages/setuptools/dist.py:744: > SetuptoolsDeprecationWarning: Invalid dash-separated options > !! > > > > Usage of dash-separated 'author-email' will not be supported in future > versions. Please use the underscore name 'author_email' instead. > > This deprecation is overdue, please update your project and remove > deprecated > calls to avoid build errors in the future. > > See > https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for > details. > > > > !! > opt = self.warn_dash_deprecation(opt, section) > /usr/lib/python3/dist-packages/setuptools/dist.py:744: > SetuptoolsDeprecationWarning: Invalid dash-separated options > !! > > > > Usage of dash-separated 'home-page' will not be supported in future > versions. Please use the underscore name 'home_page' instead. > > This deprecation is overdue, please update your project and remove > deprecated > calls to avoid build errors in the future. > > See > https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for > details. > > > > !! > opt = self.warn_dash_deprecation(opt, section) > /usr/lib/python3/dist-packages/setuptools/__init__.py:84: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > &g
Bug#1058547: node-globby: FTBFS: make: *** [debian/rules:8: binary] Error 25
Source: node-globby
Version: 13.1.3+~cs16.25.40-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
> Link ./node_modules/@sinonjs/fake-timers ->
> /usr/share/nodejs/@sinonjs/fake-timers
> Link ./node_modules/@types/glob-parent -> /usr/share/nodejs/@types/glob-parent
> Link ./node_modules/@types/minimist -> /usr/share/nodejs/@types/minimist
> Link ./node_modules/@types/mocha -> /usr/share/nodejs/@types/mocha
> Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node
> Copy /usr/share/nodejs/@types/braces -> ./node_modules/@types
> Copy /usr/share/nodejs/@types/glob -> ./node_modules/@types
> Copy /usr/share/nodejs/@types/micromatch -> ./node_modules/@types
> Not found
> ### @types/minimatch is required by debian/nodejs/./extcopies but not
> available
> # Typescript definition detected, Fallback to main module
> ### You SHOULD update your debian/nodejs/./extcopies file!
> Copy /usr/share/nodejs/minimatch -> ./node_modules/
> Copy /usr/share/nodejs/@types/sinon -> ./node_modules/@types
> Copy /usr/share/nodejs/@types/sinonjs__fake-timers -> ./node_modules/@types
> Link node_modules/dir-glob -> ../dir-glob
> Link node_modules/fast-glob -> ../fast-glob
> Link node_modules/fastq -> ../fastq
> Link node_modules/merge2 -> ../merge2
> Link node_modules/@nodelib/fs.macchiato -> ../../nodelib-fs-macchiato
> Link node_modules/@nodelib/fs.scandir -> ../../nodelib-fsscandir
> Link node_modules/@nodelib/fs.stat -> ../../nodelib-fsstat
> Link node_modules/@nodelib/fs.walk -> ../../nodelib-fswalk
> Link node_modules/reusify -> ../reusify
> Link node_modules/run-parallel -> ../run-parallel
> Link fast-glob/node_modules/fastq -> ../../fastq
> Link fast-glob/node_modules/@nodelib/fs.scandir -> ../../../nodelib-fsscandir
> Link fast-glob/node_modules/@nodelib/fs.stat -> ../../../nodelib-fsstat
> Link fast-glob/node_modules/@nodelib/fs.walk -> ../../../nodelib-fswalk
> Link fast-glob/node_modules/run-parallel -> ../../run-parallel
> Link node_modules/@types/easy-table ->
> ../../debian/build_modules/@types/easy-table
> Link node_modules/@types/merge2 -> ../../debian/build_modules/@types/merge2
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> Found debian/nodejs/fast-glob/build
> cd ./fast-glob && sh -ex ../debian/nodejs/fast-glob/build
> + mv src/benchmark .
> + tsc
> [96msrc/utils/fs.ts[0m:[93m5[0m:[93m7[0m - [91merror[0m[90m TS2720:
> [0mClass 'DirentFromStats' incorrectly implements class 'Dirent'. Did you
> mean to extend 'Dirent' and inherit its members as a subclass?
> Property 'path' is missing in type 'DirentFromStats' but required in type
> 'Dirent'.
>
> [7m5[0m class DirentFromStats implements fs.Dirent {
> [7m [0m [91m ~~~[0m
>
>
> [96m../../../../usr/share/nodejs/@types/node/ts4.8/fs.d.ts[0m:[93m227[0m:[93m9[0m
> [7m227[0m path: string;
> [7m [0m [96m[0m
> 'path' is declared here.
>
> [96m../nodelib-fs-macchiato/out/dirent.d.ts[0m:[93m4[0m:[93m22[0m -
> [91merror[0m[90m TS2720: [0mClass
> 'import("/<>/nodelib-fs-macchiato/out/dirent").default'
> incorrectly implements class 'import("fs").Dirent'. Did you mean to extend
> 'import("fs").Dirent' and inherit its members as a subclass?
> Property 'path' is missing in type
> 'import("/<>/nodelib-fs-macchiato/out/dirent").default' but
> required in type 'import("fs").Dirent'.
>
> [7m4[0m export default class Dirent implements fs.Dirent {
> [7m [0m [91m ~~[0m
>
>
> [96m../../../../usr/share/nodejs/@types/node/ts4.8/fs.d.ts[0m:[93m227[0m:[93m9[0m
> [7m227[0m path: string;
> [7m [0m [96m[0m
> 'path' is declared here.
>
>
> Found 2 errors in 2 files.
>
> Errors Files
> 1 src/utils/fs.ts[90m:5[0m
> 1 ../nodelib-fs-macchiato/out/dirent.d.ts[90m:4[0m
> dh_auto_build: error: cd ./fast-glob && sh -ex
> ../debian/nodejs/fast-glob/build returned exit code 2
> make: *** [debian/rules:8: b
Bug#1058545: esnacc: FTBFS: make: *** [debian/rules:13: binary] Error 25
Source: esnacc Version: 1.8.1-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_install > dh_install: warning: Compatibility levels before 10 are deprecated (level 9 > in use) > rm -rf /<>/debian/esnacc/usr/share/doc/snacc-doc/ \ > /<>/debian/esnacc/usr/share/man/man1/snacced.1* > make[1]: Leaving directory '/<>' >dh_installdocs > dh_installdocs: warning: Compatibility levels before 10 are deprecated (level > 9 in use) > dh_installdocs: error: Cannot find (any matches for) "doc/Esnacc.pdf" (tried > in .) > > make: *** [debian/rules:13: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/12/12/esnacc_1.8.1-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1058542: node-ytdl-core: FTBFS: make: *** [debian/rules:8: binary] Error 25
Source: node-ytdl-core Version: 4.11.2+dfsg+~cs4.10.8-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs > Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node > Link ./node_modules/@types/sax -> /usr/share/nodejs/@types/sax > Link node_modules/m3u8stream -> ../m3u8stream > Link node_modules/miniget -> ../miniget > Link m3u8stream/node_modules/miniget -> ../../miniget >dh_auto_build --buildsystem=nodejs > Found debian/nodejs/miniget/build > cd ./miniget && sh -ex ../debian/nodejs/miniget/build > + tsc -p tsconfig.build.json > src/index.ts(310,18): error TS2769: No overload matches this call. > Overload 1 of 2, '(timeoutId: string | number | Timeout | undefined): > void', gave the following error. > Argument of type 'Timer' is not assignable to parameter of type 'string | > number | Timeout | undefined'. > Property '[Symbol.dispose]' is missing in type 'Timer' but required in > type 'Timeout'. > Overload 2 of 2, '(id: number | undefined): void', gave the following error. > Argument of type 'Timer' is not assignable to parameter of type 'number'. > dh_auto_build: error: cd ./miniget && sh -ex ../debian/nodejs/miniget/build > returned exit code 2 > make: *** [debian/rules:8: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/12/12/node-ytdl-core_4.11.2+dfsg+~cs4.10.8-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1058541: node-redis: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_build] Error 2
Source: node-redis Version: 4.5.1+~1.1.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > cd packages/client && tsc > lib/client/index.ts(359,22): error TS2345: Argument of type 'Timer | > undefined' is not assignable to parameter of type 'string | number | Timeout > | undefined'. > Type 'Timer' is not assignable to type 'string | number | Timeout | > undefined'. > Property '[Symbol.dispose]' is missing in type 'Timer' but required in > type 'Timeout'. > make[1]: *** [debian/rules:11: override_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2023/12/12/node-redis_4.5.1+~1.1.2-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1058540: ditaa: FTBFS: xargs: /usr/lib/jvm/default-java/bin/javac: No such file or directory
Source: ditaa Version: 0.10+ds1-1.3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --with javahelper >dh_update_autotools_config >dh_autoreconf >jh_linkjars >jh_build > xargs: /usr/lib/jvm/default-java/bin/javac: No such file or directory > jh_build: error: find ./src/org/ -name '*.java' -and -type f -print0 | xargs > -s 512000 -0 /usr/lib/jvm/default-java/bin/javac -g -cp > /usr/share/java/junit4.jar:/usr/lib/jvm/default-java/lib/tools.jar:/usr/share/java/commons-cli.jar:/usr/share/java/batik-bridge.jar:/usr/share/java/batik-dom.jar:/usr/share/java/batik-gvt.jar:/usr/share/java/batik-svg-dom.jar:/usr/share/java/batik-awt-util.jar:/usr/share/java/xml-apis-ext.jar:/usr/share/java/batik-libs.jar:/usr/share/java/jericho-html.jar:debian/_jh_build.ditaa > -d debian/_jh_build.ditaa -encoding ISO8859-1 -source 7 -target 7 returned > exit code 127 > make: *** [debian/rules:11: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/12/12/ditaa_0.10+ds1-1.3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1058539: node-openpgp-asmcrypto.js: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
Source: node-openpgp-asmcrypto.js
Version: 2.3.3~0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with nodejs
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
> Link ./node_modules/fs-extra -> /usr/share/nodejs/fs-extra
> Link ./node_modules/typescript -> /usr/share/nodejs/typescript
> Link ./node_modules/rollup -> /usr/share/nodejs/rollup
> Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node
> Link ./node_modules/chai -> /usr/share/nodejs/chai
>dh_auto_build --buildsystem=nodejs
> Found debian/nodejs/./build
> cd ./. && sh -ex debian/nodejs/./build
> + node build.js
> {
> file: SourceFileObject {
> pos: 0,
> end: 12659,
> flags: 18874432,
> modifierFlagsCache: 0,
> transformFlags: 1,
> parent: undefined,
> kind: 305,
> statements: [
> [NodeObject],[NodeObject], [NodeObject],
> [NodeObject],[NodeObject], [NodeObject],
> [NodeObject],[NodeObject], [NodeObject],
> [NodeObject],[NodeObject], [NodeObject],
> [NodeObject],[NodeObject], [NodeObject],
> [NodeObject],[NodeObject], [NodeObject],
> [NodeObject],[NodeObject], [NodeObject],
> [NodeObject],[NodeObject], [NodeObject],
> [NodeObject],[NodeObject], [NodeObject],
> [NodeObject],[NodeObject], [NodeObject],
> [NodeObject],[NodeObject], [NodeObject],
> [NodeObject],[NodeObject], [NodeObject],
> [NodeObject],[NodeObject], [NodeObject],
> [NodeObject],[NodeObject], [NodeObject],
> [NodeObject],[NodeObject], [NodeObject],
> [NodeObject],pos: 0,end: 12658,
> hasTrailingComma: false, transformFlags: 1
> ],
> endOfFileToken: TokenObject {
> pos: 12658,
> end: 12659,
> flags: 16777216,
> modifierFlagsCache: 0,
> transformFlags: 0,
> parent: [Circular *1],
> kind: 1
> },
> fileName: '/usr/share/nodejs/@types/node/ts4.8/globals.d.ts',
> text: '// Declare "static" methods in Error\n' +
> 'interface ErrorConstructor {\n' +
> '/** Create .stack property on a target object */\n' +
> 'captureStackTrace(targetObject: object, constructorOpt?:
> Function): void;\n' +
> '\n' +
> '/**\n' +
> ' * Optional override for formatting stack traces\n' +
> ' *\n' +
> ' * @see
> https://v8.dev/docs/stack-trace-api#customizing-stack-traces\n' +
> ' */\n' +
> 'prepareStackTrace?: ((err: Error, stackTraces: NodeJS.CallSite[])
> => any) | undefined;\n' +
> '\n' +
> 'stackTraceLimit: number;\n' +
> '}\n' +
> '\n' +
> '/*---*\n' +
> ' * *\n' +
> ' * GLOBAL *\n' +
> ' * *\n' +
> ' */\n' +
> '\n' +
> '// For backwards compability\n' +
> 'interface NodeRequire extends NodeJS.Require {}\n' +
> 'interface RequireResolve extends NodeJS.RequireResolve {}\n' +
> 'interface NodeModule extends NodeJS.Module {}\n' +
> '\n' +
> 'declare var process: NodeJS.Process;\n' +
> 'declare var console: Console;\n' +
> '\n' +
> 'declare var __filename: string;\n' +
> 'declare var __dirname: string;\n' +
> '\n' +
> 'declare var require: NodeRequire;\n' +
> 'declare var module: NodeModule;\n' +
> '\n' +
> '// Same as module.exports\n' +
> 'declare var exports: any;\n' +
> '\n' +
> '/**\n' +
> ' * Only available if `--expose-gc` is passed to the process.\n' +
> ' */\n' +
> 'declare var gc: undefined | (() => void);\n' +
> '\n' +
> '// #region borrowed\n' +
> '// from
> https://github.com/microsoft/TypeScript/blob/38da7c600c83e7b31193a62495239a0fe478cb67/lib/lib.webworker.d.ts#L633
> until moved to separate lib\n' +
> '/** A controller object that allows you to abort one or more DOM
>
Bug#1058537: node-node-pty: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_build] Error 1
Source: node-node-pty Version: 1.0.0+~6.3.0-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs > Link ./node_modules/@types/mocha -> /usr/share/nodejs/@types/mocha > Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node > Link node_modules/ps-list -> ../ps-list >debian/rules override_dh_auto_build > make[1]: Entering directory '/<>' > tsc -b ./src/tsconfig.json > src/windowsPtyAgent.ts(243,20): error TS2345: Argument of type 'Timer' is not > assignable to parameter of type 'string | number | Timeout | undefined'. > Property '[Symbol.dispose]' is missing in type 'Timer' but required in type > 'Timeout'. > make[1]: *** [debian/rules:13: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/12/12/node-node-pty_1.0.0+~6.3.0-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1058535: libhinawa: FTBFS: make: *** [debian/rules:8: binary] Error 25
Source: libhinawa Version: 4.0.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- -Ddoc=true > cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 > meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr > --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu > -Dpython.bytecompile=-1 -Ddoc=true > The Meson build system > Version: 1.3.0 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: hinawa > Project version: 4.0.0 > C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-8) 13.2.0") > C linker for the host machine: cc ld.bfd 2.41.50.20231206 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Header "include/linux/firewire-cdev.h" has symbol "FW_CDEV_EVENT_REQUEST3" : > NO > Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1 > Run-time dependency gobject-2.0 found: YES 2.78.3 > Build-time dependency glib-2.0 found: YES 2.78.3 > Program /usr/bin/glib-genmarshal found: YES (/usr/bin/glib-genmarshal) > Dependency glib-2.0 found: YES 2.78.3 (cached) > Program /usr/bin/glib-mkenums found: YES (/usr/bin/glib-mkenums) > Dependency glib-2.0 found: YES 2.78.3 (cached) > Program /usr/bin/glib-mkenums found: YES (/usr/bin/glib-mkenums) > Run-time dependency gobject-introspection-1.0 found: YES 1.78.1 > Dependency gobject-introspection-1.0 found: YES 1.78.1 (cached) > Program /usr/bin/g-ir-scanner found: YES (/usr/bin/g-ir-scanner) > Dependency gobject-introspection-1.0 found: YES 1.78.1 (cached) > Program /usr/bin/g-ir-compiler found: YES (/usr/bin/g-ir-compiler) > Program fw-node found: YES (/usr/bin/python3 /<>/tests/fw-node) > Program fw-req found: YES (/<>/tests/fw-req) > Program fw-resp found: YES (/<>/tests/fw-resp) > Program fw-fcp found: YES (/<>/tests/fw-fcp) > Program cycle-time found: YES (/usr/bin/python3 > /<>/tests/cycle-time) > Program hinawa-enum found: YES (/usr/bin/python3 > /<>/tests/hinawa-enum) > Program hinawa-functions found: YES (/usr/bin/python3 > /<>/tests/hinawa-functions) > Configuring hinawa.toml using configuration > Run-time dependency gi-docgen found: YES 2023.3 > Program gi-docgen found: YES (/usr/bin/gi-docgen) > Build targets in project: 8 > > hinawa 4.0.0 > > User defined options > buildtype : plain > libdir: lib/x86_64-linux-gnu > localstatedir : /var > prefix: /usr > sysconfdir: /etc > wrap_mode : nodownload > python.bytecompile: -1 > doc : true > > Found ninja-1.11.1 at /usr/bin/ninja > make[1]: Leaving directory '/<>' >dh_auto_build -O--buildsystem=meson > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j8 -v > [1/15] /usr/bin/glib-genmarshal --prefix hinawa_sigs_marshal --stdinc > --output src/hinawa_sigs_marshal.h --header ../src/hinawa_sigs_marshal.list > --pragma-once > INFO: Reading ../src/hinawa_sigs_marshal.list... > [2/15] /usr/bin/glib-genmarshal --prefix hinawa_sigs_marshal --stdinc > --output src/hinawa_sigs_marshal.c --body ../src/hinawa_sigs_marshal.list > --include-header hinawa_sigs_marshal.h > INFO: Reading ../src/hinawa_sigs_marshal.list... > [3/15] /usr/bin/meson --internal exe --unpickle > /<>/obj-x86_64-linux-gnu/meson-private/meson_exe_glib-mkenums_2f524c9b023ec2ae23e6f08f59994151641f9f41.dat > [4/15] /usr/bin/meson --internal exe --unpickle > /<>/obj-x86_64-linux-gnu/meson-private/meson_exe_glib-mkenums_c023153e6dc728bc4ca9c5bbd7bf1ecd9fe95298.dat > [5/15] cc -Isrc/libhinawa.so.4.0.0.p -Isrc -I../src -I../include > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MQ > src/libhinawa.so.4.0.0.p/cycle_time.c.o -MF > src/libhinawa.so.4.0.0.p/cycle_time.c.o.d -o > src/libhinawa.so.4.0.0.p/cycle_time.c.o -c ../src/cycle_time.c > [6/15] cc -Isrc/libhinawa.so.4.0.0.p -Isrc -I../src -I../include > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-stro
Bug#1058532: golang-google-api: FTBFS: tests failed
Source: golang-google-api Version: 0.61.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_test -- -short > cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 -short > google.golang.org/api google.golang.org/api/abusiveexperiencereport/v1 > google.golang.org/api/acceleratedmobilepageurl/v1 > google.golang.org/api/accessapproval/v1 > google.golang.org/api/accessapproval/v1beta1 > google.golang.org/api/accesscontextmanager/v1 > google.golang.org/api/accesscontextmanager/v1beta > google.golang.org/api/adexchangebuyer/v1.2 > google.golang.org/api/adexchangebuyer/v1.3 > google.golang.org/api/adexchangebuyer/v1.4 > google.golang.org/api/adexchangebuyer2/v2beta1 > google.golang.org/api/adexchangeseller/v1 > google.golang.org/api/adexchangeseller/v1.1 > google.golang.org/api/adexchangeseller/v2.0 > google.golang.org/api/adexperiencereport/v1 > google.golang.org/api/admin/datatransfer/v1 > google.golang.org/api/admin/directory/v1 > google.golang.org/api/admin/reports/v1 google.golang.org/api/admob/v1 > google.golang.org/api/admob/v1beta google.golang.org/api/adsense/v1.3 > google.golang.org/api/adsense/v1.4 google.golang.org/api/adsense/v2 > google.golang.org/api/adsensehost/v4.1 > google.golang.org/api/alertcenter/v1beta1 > google.golang.org/api/analytics/v2.4 google.golang.org/api/analytics/v3 > google.golang.org/api/analyticsadmin/v1alpha > google.golang.org/api/analyticsdata/v1alpha > google.golang.org/api/analyticsdata/v1beta > google.golang.org/api/analyticsreporting/v4 > google.golang.org/api/androiddeviceprovisioning/v1 > google.golang.org/api/androidenterprise/v1 > google.golang.org/api/androidmanagement/v1 > google.golang.org/api/androidpublisher/v1 > google.golang.org/api/androidpublisher/v1.1 > google.golang.org/api/androidpublisher/v2 > google.golang.org/api/androidpublisher/v3 google.golang.org/api/apigateway/v1 > google.golang.org/api/apigateway/v1alpha1 > google.golang.org/api/apigateway/v1alpha2 > google.golang.org/api/apigateway/v1beta google.golang.org/api/apigee/v1 > google.golang.org/api/apikeys/v2 google.golang.org/api/appengine/v1 > google.golang.org/api/appengine/v1alpha > google.golang.org/api/appengine/v1beta > google.golang.org/api/appengine/v1beta4 > google.golang.org/api/appengine/v1beta5 google.golang.org/api/appsactivity/v1 > google.golang.org/api/appstate/v1 > google.golang.org/api/area120tables/v1alpha1 > google.golang.org/api/artifactregistry/v1 > google.golang.org/api/artifactregistry/v1beta1 > google.golang.org/api/artifactregistry/v1beta2 > google.golang.org/api/assuredworkloads/v1 > google.golang.org/api/assuredworkloads/v1beta1 > google.golang.org/api/authorizedbuyersmarketplace/v1 > google.golang.org/api/baremetalsolution/v1 > google.golang.org/api/baremetalsolution/v1alpha1 > google.golang.org/api/baremetalsolution/v2 google.golang.org/api/bigquery/v2 > google.golang.org/api/bigqueryconnection/v1beta1 > google.golang.org/api/bigquerydatatransfer/v1 > google.golang.org/api/bigqueryreservation/v1 > google.golang.org/api/bigqueryreservation/v1alpha2 > google.golang.org/api/bigqueryreservation/v1beta1 > google.golang.org/api/bigtableadmin/v1 google.golang.org/api/bigtableadmin/v2 > google.golang.org/api/billingbudgets/v1 > google.golang.org/api/billingbudgets/v1beta1 > google.golang.org/api/binaryauthorization/v1 > google.golang.org/api/binaryauthorization/v1beta1 > google.golang.org/api/blogger/v2 google.golang.org/api/blogger/v3 > google.golang.org/api/books/v1 google.golang.org/api/calendar/v3 > google.golang.org/api/chat/v1 google.golang.org/api/chromemanagement/v1 > google.golang.org/api/chromepolicy/v1 google.golang.org/api/chromeuxreport/v1 > google.golang.org/api/civicinfo/v2 google.golang.org/api/classroom/v1 > google.golang.org/api/cloudasset/v1 google.golang.org/api/cloudasset/v1beta1 > google.golang.org/api/cloudasset/v1p1beta1 > google.golang.org/api/cloudasset/v1p4beta1 > google.golang.org/api/cloudasset/v1p5beta1 > google.golang.org/api/cloudasset/v1p7beta1 > google.golang.org/api/cloudbilling/v1 google.golang.org/api/cloudbuild/v1 > google.golang.org/api/cloudbuild/v1alpha1 > google.golang.org/api/cloudbuild/v1alpha2 > google.golang.org/api/cloudbuild/v1beta1 > google.golang.org/api/cloudchannel/v1 > google.golang.org/api/cloudcommerceprocurement/v1 > google.golang.org/api/clouddebugger/v2 google.golang.org/api/clouddeploy/v1 > google.golang.org/api/clouderrorreporting/v1beta1 > go
Bug#1058531: heat: FTBFS: AttributeError: 'FileFinder' object has no attribute 'find_module'
Source: heat Version: 1:21.0.0-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > == > FAIL: heat.tests.test_urlfetch.UrlFetchTest.test_http_scheme > heat.tests.test_urlfetch.UrlFetchTest.test_http_scheme > -- > testtools.testresult.real._StringException: Traceback (most recent call last): > File "/<>/heat/tests/common.py", line 118, in setUp > tris.append(resources.global_env().get_resource_info( > ^^ > File "/<>/heat/engine/resources/__init__.py", line 56, in > global_env > initialise() > File "/<>/heat/engine/resources/__init__.py", line 68, in > initialise > _load_global_environment(global_env) > File "/<>/heat/engine/resources/__init__.py", line 74, in > _load_global_environment > _load_global_resources(env) > File "/<>/heat/engine/resources/__init__.py", line 87, in > _load_global_resources > manager = plugin_manager.PluginManager(__name__) > ^^ > File "/<>/heat/engine/plugin_manager.py", line 54, in __init__ > self.modules = list(modules()) >^^^ > File "/<>/heat/common/plugin_loader.py", line 97, in > load_modules > module = _import_module(importer, module_name, package) > ^^ > File "/<>/heat/common/plugin_loader.py", line 69, in > _import_module > loader = importer.find_module(module_name) > > AttributeError: 'FileFinder' object has no attribute 'find_module' > > > == > FAIL: heat.tests.test_urlfetch.UrlFetchTest.test_https_scheme > heat.tests.test_urlfetch.UrlFetchTest.test_https_scheme > -- > testtools.testresult.real._StringException: Traceback (most recent call last): > File "/<>/heat/tests/common.py", line 118, in setUp > tris.append(resources.global_env().get_resource_info( > ^^ > File "/<>/heat/engine/resources/__init__.py", line 56, in > global_env > initialise() > File "/<>/heat/engine/resources/__init__.py", line 68, in > initialise > _load_global_environment(global_env) > File "/<>/heat/engine/resources/__init__.py", line 74, in > _load_global_environment > _load_global_resources(env) > File "/<>/heat/engine/resources/__init__.py", line 87, in > _load_global_resources > manager = plugin_manager.PluginManager(__name__) > ^^ > File "/<>/heat/engine/plugin_manager.py", line 54, in __init__ > self.modules = list(modules()) >^^^ > File "/<>/heat/common/plugin_loader.py", line 97, in > load_modules > module = _import_module(importer, module_name, package) > ^^ > File "/<>/heat/common/plugin_loader.py", line 69, in > _import_module > loader = importer.find_module(module_name) > > AttributeError: 'FileFinder' object has no attribute 'find_module' > > > == > FAIL: heat.tests.test_urlfetch.UrlFetchTest.test_max_fetch_size_error > heat.tests.test_urlfetch.UrlFetchTest.test_max_fetch_size_error > -- > testtools.testresult.real._StringException: Traceback (most recent call last): > File "/<>/heat/tests/common.py", line 118, in setUp > tris.append(resources.global_env().get_resource_info( > ^^ > File "/<>/heat/engine/resources/__init__.py", line 56, in > global_env > initialise() > File "/<>/heat/engine/resources/__init__.py", line 68, in > initialise > _load_global_environment(global_env) > File "/<>/heat/engine/resources/__init__.py", line 74, in > _load_global_environment > _load_global_resources(env) > File "/<>/heat/engine/re
Bug#1058534: node-rollup-plugin-node-polyfills: FTBFS: make: *** [debian/rules:8: binary] Error 25
Source: node-rollup-plugin-node-polyfills Version: 0.2.1+dfsg+~0.11.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs > Link ./node_modules/concat-stream -> /usr/share/nodejs/concat-stream > Link ./node_modules/core-util-is -> /usr/share/nodejs/core-util-is > Link ./node_modules/crypto-browserify -> /usr/share/nodejs/crypto-browserify > Link ./node_modules/errno -> /usr/share/nodejs/errno > Link ./node_modules/immediate -> /usr/share/nodejs/immediate > Link ./node_modules/inherits -> /usr/share/nodejs/inherits > Link ./node_modules/isarray -> /usr/share/nodejs/isarray > Link ./node_modules/@rollup/plugin-inject -> > /usr/share/nodejs/@rollup/plugin-inject > Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node > Link ./node_modules/xtend -> /usr/share/nodejs/xtend > Link node_modules/rollup-plugin-polyfill-node -> > ../rollup-plugin-polyfill-node > Link node_modules/abstract-leveldown -> > ../debian/build_modules/abstract-leveldown > Link node_modules/browserify-fs -> ../debian/build_modules/browserify-fs > Link node_modules/buffer-es6 -> ../debian/build_modules/buffer-es6 > Link node_modules/deferred-leveldown -> > ../debian/build_modules/deferred-leveldown > Link node_modules/fwd-stream -> ../debian/build_modules/fwd-stream > Link node_modules/level-blobs -> ../debian/build_modules/level-blobs > Link node_modules/level-errors -> ../debian/build_modules/level-errors > Link node_modules/level-filesystem -> ../debian/build_modules/level-filesystem > Link node_modules/level-iterator-stream -> > ../debian/build_modules/level-iterator-stream > Link node_modules/level-js -> ../debian/build_modules/level-js > Link node_modules/level-peek -> ../debian/build_modules/level-peek > Link node_modules/level-post -> ../debian/build_modules/level-post > Link node_modules/level-sublevel -> ../debian/build_modules/level-sublevel > Link node_modules/level-supports -> ../debian/build_modules/level-supports > Link node_modules/levelup -> ../debian/build_modules/levelup > Link node_modules/looper -> ../debian/build_modules/looper > Link node_modules/ltgt -> ../debian/build_modules/ltgt > Link node_modules/octal -> ../debian/build_modules/octal > Link node_modules/process-es6 -> ../debian/build_modules/process-es6 > Link node_modules/pull-cat -> ../debian/build_modules/pull-cat > Link node_modules/pull-level -> ../debian/build_modules/pull-level > Link node_modules/pull-live -> ../debian/build_modules/pull-live > Link node_modules/pull-pushable -> ../debian/build_modules/pull-pushable > Link node_modules/pull-stream -> ../debian/build_modules/pull-stream > Link node_modules/pull-window -> ../debian/build_modules/pull-window > Link node_modules/safer-buffer -> ../debian/build_modules/safer-buffer > Link node_modules/stream-to-pull-stream -> > ../debian/build_modules/stream-to-pull-stream >dh_auto_build --buildsystem=nodejs > Found debian/nodejs/rollup-plugin-polyfill-node/build > cd ./rollup-plugin-polyfill-node && sh -ex > ../debian/nodejs/rollup-plugin-polyfill-node/build > + node scripts/build-constants.js > + node scripts/build-polyfills.js > + node scripts/collect-polyfills.js > + tsc -p . > + rollup -c > [36m > [1mlib/index.js[22m → [1mdist/es, dist/[22m...[39m > [32mcreated [1mdist/es, dist/[22m in [1m252ms[22m[39m > + rollup lib/index.js -f cjs -o dist/index.js > [36m > [1mlib/index.js[22m → [1mdist/index.js[22m...[39m > [1m[33m(!) Unresolved dependencies[39m[22m > [90mhttps://rollupjs.org/troubleshooting/#warning-treating-module-as-external-dependency[39m > [1m@rollup/plugin-inject[22m (imported by "lib/index.js") > [1mpath[22m (imported by "lib/index.js") > [1mcrypto[22m (imported by "lib/index.js") > [32mcreated [1mdist/index.js[22m in [1m219ms[22m[39m > + rollup lib/index.js -f es -o dist/es/index.js > [36m > [1mlib/index.js[22m → [1mdist/es/index.js[22m...[39m > [1m[33m(!) Unresolved dependencies[39m[22m > [90mhttps://rollupjs.org/troubleshooting/#warning-treating-module-as-external-dependency[39m > [1m@rollup/plugin-inject[22m (imported by "lib/index.js") > [1mpath[22m (imported by "lib/index.js") > [1mcrypto[22m (imported by "lib/index.js") > [32mcreated [1mdist/es/index.js[22m in [1m211ms[22m[39m
Bug#1058533: libitext5-java: FTBFS: [ERROR] /<>/itext/src/main/java/com/itextpdf/text/pdf/security/PdfPKCS7.java:[1287,48] cannot find symbol
Source: libitext5-java Version: 5.5.13.3-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > mh_patchpoms -plibitext5-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 > OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were > deprecated in JDK 13 and will likely be removed in a future release. > [0m[0m[INFO] Scanning for projects... > [INFO] > > [INFO] Reactor Build Order: > [INFO] > [INFO] iText Core > [jar] > [INFO] iText PDF/A > [jar] > [INFO] iText XML Worker > [jar] > [INFO] iText > [pom] > [INFO] > [INFO] ---< com.itextpdf:itextpdf > > > [INFO] Building iText Core 5.5.13.3 > [1/4] > [INFO] [ jar > ]- > [WARNING] The artifact > org.apache.maven.plugins:maven-resources-plugin:jar:2.6 has been relocated to > org.apache.maven.plugins:maven-resources-plugin:jar:3.3.0 > [WARNING] The artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.1 > has been relocated to > org.apache.maven.plugins:maven-compiler-plugin:jar:3.10.1 > [INFO] > [INFO] --- maven-resources-plugin:3.3.0:resources (default-resources) @ > itextpdf --- > [INFO] Copying 23 resources > [INFO] > [INFO] --- maven-compiler-plugin:3.10.1:compile (default-compile) @ itextpdf > --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 630 source files to /<>/itext/target/classes > [INFO] > /<>/itext/src/main/java/com/itextpdf/text/pdf/PdfPublicKeySecurityHandler.java: > Some input files use or override a deprecated API. > [INFO] > /<>/itext/src/main/java/com/itextpdf/text/pdf/PdfPublicKeySecurityHandler.java: > Recompile with -Xlint:deprecation for details. > [INFO] > /<>/itext/src/main/java/com/itextpdf/text/io/ByteBufferRandomAccessSource.java: > Some input files use or override a deprecated API that is marked for removal. > [INFO] > /<>/itext/src/main/java/com/itextpdf/text/io/ByteBufferRandomAccessSource.java: > Recompile with -Xlint:removal for details. > [INFO] > /<>/itext/src/main/java/com/itextpdf/xmp/options/Options.java: > Some input files use unchecked or unsafe operations. > [INFO] > /<>/itext/src/main/java/com/itextpdf/xmp/options/Options.java: > Recompile with -Xlint:unchecked for details. > [INFO] - > [ERROR] COMPILATION ERROR : > [INFO] - > [ERROR] > /<>/itext/src/main/java/com/itextpdf/text/pdf/security/PdfPKCS7.java:[223,95] > cannot find symbol > symbol: method getObject() > location: class org.bouncycastle.asn1.ASN1TaggedObject > [ERROR] > /<>/itext/src/main/java/com/itextpdf/text/pdf/security/PdfPKCS7.java:[246,109] > cannot find symbol > symbol: method getObject() > location: class org.bouncycastle.asn1.ASN1TaggedObject > [ERROR] > /<>/itext/src/main/java/com/itextpdf/text/pdf/security/PdfPKCS7.java:[346,70] > cannot find symbol > symbol: method getObject() > location: variable tg of type org.bouncycastle.asn1.ASN1TaggedObject > [ERROR] > /<>/itext/src/main/java/com/itextpdf/text/pdf/security/PdfPKCS7.java:[350,70] > cannot find symbol > symbol: method getObject() > location: variable tg of type org.bouncycastle.asn1.ASN1TaggedObject > [ERROR] > /<>/itext/src/main/java/com/itextpdf/text/pdf/security/PdfPKCS7.java:[1286,2
Bug#1058530: yash: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
Source: yash Version: 2.55-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/tests' > ./resetsig ../yash ./run-test.sh ../yash sigcont1-p.tst > ./resetsig ../yash ./run-test.sh ../yash sigcont2-p.tst > ./resetsig ../yash ./run-test.sh ../yash sigcont5-p.tst > ./resetsig ../yash ./run-test.sh ../yash sigcont6-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigcont7-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigcont4-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigcont8-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigcont3-p.tst > ./resetsig ../yash ./run-test.sh ../yash sighup1-p.tst > ./resetsig ../yash ./run-test.sh ../yash sighup2-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sighup3-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sighup4-p.tst > ./resetsig ../yash ./run-test.sh ../yash sighup5-p.tst > ./resetsig ../yash ./run-test.sh ../yash sighup6-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sighup7-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sighup8-p.tst > ./resetsig ../yash ./run-test.sh ../yash sigint1-p.tst > ./resetsig ../yash ./run-test.sh ../yash sigint2-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigint3-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigint4-p.tst > ./resetsig ../yash ./run-test.sh ../yash sigint5-p.tst > ./resetsig ../yash ./run-test.sh ../yash sigint6-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigint7-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigint8-p.tst > ./resetsig ../yash ./run-test.sh ../yash sigquit1-p.tst > ./resetsig ../yash ./run-test.sh ../yash sigquit2-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigquit3-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigquit4-p.tst > ./resetsig ../yash ./run-test.sh ../yash sigquit5-p.tst > ./resetsig ../yash ./run-test.sh ../yash sigquit6-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigquit7-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigquit8-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigstop3-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigstop7-p.tst > ./resetsig ../yash ./run-test.sh ../yash sigterm1-p.tst > ./resetsig ../yash ./run-test.sh ../yash sigterm2-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigterm3-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigterm4-p.tst > ./resetsig ../yash ./run-test.sh ../yash sigterm5-p.tst > ./resetsig ../yash ./run-test.sh ../yash sigterm6-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigterm7-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigterm8-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigtstp3-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigtstp4-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigtstp7-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigtstp8-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigttin3-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigttin4-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigttin7-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigttin8-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigttou3-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigttou4-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigttou7-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigttou8-p.tst > ./resetsig ../yash ./run-test.sh ../yash sigurg1-p.tst > ./resetsig ../yash ./run-test.sh ../yash sigurg2-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigurg3-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigurg4-p.tst > ./resetsig ../yash ./run-test.sh ../yash sigurg5-p.tst > ./resetsig ../yash ./run-test.sh ../yash sigurg6-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigurg7-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash sigurg8-p.tst > ./resetsig ../yash ./run-test.sh ../yash alias-p.tst > ./resetsig ../yash ./run-test.sh ../yash andor-p.tst > ./resetsig ../yash ./run-test.sh ../yash arith-p.tst > ./resetsig ../yash ./run-test.sh ../yash async-p.tst > ./ptwrap ./resetsig ../yash ./run-test.sh ../yash bg-p.tst > ./resetsig ../yash ./run-test.sh ../yash break-p.tst > ./resetsig ../yash ./run-test.sh ../yash builtins-p.tst > ./resetsig ../yash ./run-test.sh ../yash case-p.tst > ./resetsig ../yash ./run-test.sh ../yash cd-p.tst > ./resetsig ../yash ./run-test.sh ../yash cmdsub
Bug#1058528: calamares-extensions: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_configure] Error 2
Source: calamares-extensions Version: 1.3.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- -DCMAKE_CXX_COMPILER_ARG1="-Wdate-time > -D_FORTIFY_SOURCE=2" > cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake > -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None > -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var > -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON > -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu > "-DCMAKE_CXX_COMPILER_ARG1=-Wdate-time -D_FORTIFY_SOURCE=2" .. > CMake Deprecation Warning at CMakeLists.txt:41 (cmake_minimum_required): > Compatibility with CMake < 3.5 will be removed from a future version of > CMake. > > Update the VERSION argument value or use a ... suffix to tell > CMake that the project does not need compatibility with older versions. > > > -- The CXX compiler identification is GNU 13.2.0 > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > -- Found YAMLCPP: /usr/include > -- Found Gettext: /usr/bin/msgmerge (found version "0.21") > CMake Error at > /usr/lib/x86_64-linux-gnu/cmake/Calamares/CalamaresAddTranslations.cmake:17 > (set_package_properties): > Unknown CMake command "set_package_properties". > Call Stack (most recent call first): > > /usr/lib/x86_64-linux-gnu/cmake/Calamares/CalamaresAddModuleSubdirectory.cmake:40 > (include) > /usr/lib/x86_64-linux-gnu/cmake/Calamares/CalamaresConfig.cmake:121 > (include) > CMakeLists.txt:64 (find_package) > > > -- Configuring incomplete, errors occurred! > cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt > ==> CMakeCache.txt <== > # This is the CMakeCache file. > # For build in directory: /<>/obj-x86_64-linux-gnu > # It was generated by CMake: /usr/bin/cmake > # You can edit this file to change values found and used by cmake. > # If you do not want to change any of the values, simply exit the editor. > # If you do want to change a value, simply edit, save, and exit the editor. > # The syntax for the file is as follows: > # KEY:TYPE=VALUE > # KEY is the name of a variable in the cache. > # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. > # VALUE is the current value for the KEY. > > > # EXTERNAL cache entries > > > //Path to a program. > CMAKE_ADDR2LINE:FILEPATH=/usr/bin/addr2line > > //Path to a program. > CMAKE_AR:FILEPATH=/usr/bin/ar > > //Choose the type of build, options are: None Debug Release RelWithDebInfo > // MinSizeRel ... > CMAKE_BUILD_TYPE:STRING=None > > //Enable/Disable color output during build. > CMAKE_COLOR_MAKEFILE:BOOL=ON > > //CXX compiler > CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++ > > //A wrapper around 'ar' adding the appropriate '--plugin' option > // for the GCC compiler > CMAKE_CXX_COMPILER_AR:FILEPATH=/usr/bin/gcc-ar-13 > > //No help, variable specified on the command line. > CMAKE_CXX_COMPILER_ARG1:UNINITIALIZED=-Wdate-time -D_FORTIFY_SOURCE=2 > > //A wrapper around 'ranlib' adding the appropriate '--plugin' option > // for the GCC compiler > CMAKE_CXX_COMPILER_RANLIB:FILEPATH=/usr/bin/gcc-ranlib-13 > > //Flags used by the CXX compiler during all build types. > CMAKE_CXX_FLAGS:STRING=-g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 > > //Flags used by the CXX compiler during DEBUG builds. > CMAKE_CXX_FLAGS_DEBUG:STRING=-g > > //Flags used by the CXX compiler during MINSIZEREL builds. > CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG > > //Flags used by the CXX compiler during NONE builds. > CMAKE_CXX_FLAGS_NONE:STRING= > > //Flags used by the CXX compiler during RELEASE builds. > CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG > > //Flags used by the CXX compiler during RELWITHDEBINFO builds. > CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG > > //Path t
Bug#1058529: node-csstype: FTBFS: make[1]: *** [debian/rules:7: override_dh_auto_build] Error 1
Source: node-csstype
Version: 3.1.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ts-node --files build.ts --start
> /usr/share/nodejs/ts-node/src/index.ts:865
> return new TSError(diagnosticText, diagnosticCodes, diagnostics);
>^
> TSError: ⨯ Unable to compile TypeScript:
> build.ts(25,22): error TS2769: No overload matches this call.
> Overload 1 of 2, '(timeoutId: string | number | Timeout | undefined):
> void', gave the following error.
> Argument of type 'Timer' is not assignable to parameter of type 'string |
> number | Timeout | undefined'.
> Property '[Symbol.dispose]' is missing in type 'Timer' but required in
> type 'Timeout'.
> Overload 2 of 2, '(id: number | undefined): void', gave the following error.
> Argument of type 'Timer' is not assignable to parameter of type 'number'.
>
> at createTSError (/usr/share/nodejs/ts-node/src/index.ts:865:12)
> at reportTSError (/usr/share/nodejs/ts-node/src/index.ts:869:19)
> at getOutput (/usr/share/nodejs/ts-node/src/index.ts:1083:36)
> at Object.compile (/usr/share/nodejs/ts-node/src/index.ts:1439:41)
> at Module.m._compile (/usr/share/nodejs/ts-node/src/index.ts:1623:30)
> at Module._extensions..js (node:internal/modules/cjs/loader:1414:10)
> at Object.require.extensions. [as .ts]
> (/usr/share/nodejs/ts-node/src/index.ts:1627:12)
> at Module.load (node:internal/modules/cjs/loader:1197:32)
> at Function.Module._load (node:internal/modules/cjs/loader:1013:12)
> at Function.executeUserEntryPoint [as runMain]
> (node:internal/modules/run_main:128:12) {
> diagnosticCodes: [ 2769 ]
> }
> make[1]: *** [debian/rules:7: override_dh_auto_build] Error 1
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/node-csstype_3.1.1-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
Bug#1058527: libqtdbustest: FTBFS: make[3]: *** No rule to make target 'tests/gmock/lib/libgtest.a', needed by 'tests/CMakeFiles/unit-tests_autogen_timestamp_deps'. Stop.
Source: libqtdbustest Version: 0.3.2-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > make[3]: Nothing to be done for > 'src/qdbus-test-runner/CMakeFiles/qdbus-simple-test-runner_autogen_timestamp_deps.dir/build'. > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' > make -f tests/CMakeFiles/unit-tests_autogen_timestamp_deps.dir/build.make > tests/CMakeFiles/unit-tests_autogen_timestamp_deps.dir/build > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > make[3]: *** No rule to make target 'tests/gmock/lib/libgtest.a', needed by > 'tests/CMakeFiles/unit-tests_autogen_timestamp_deps'. Stop. > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' > make[2]: *** [CMakeFiles/Makefile2:518: > tests/CMakeFiles/unit-tests_autogen_timestamp_deps.dir/all] Error 2 The full build log is available from: http://qa-logs.debian.net/2023/12/12/libqtdbustest_0.3.2-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1058525: node-resolve: FTBFS: make[1]: *** [debian/rules:46: test_component_packages] Error 1
Source: node-resolve Version: 1.22.1+~cs5.31.10-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > pkgjs-utils link_test_modules || true > test ! -d node_modules || mkdir -p node_modules > test ! -f node_modules/object-keys || ln -s ../object-keys > node_modules/object-keys > cd is-core-module && tap -R spec --no-cov test > > (node:1105148) [DEP0125] DeprecationWarning: The _stream_wrap module is > deprecated. > (Use `node --trace-deprecation ...` to show where the warning was created) > (node:1105148) [DEP0025] DeprecationWarning: sys is deprecated. Use util > instead. > (node:1105148) ExperimentalWarning: WASI is an experimental feature and might > change at any time > test/index.js > > ✓ should be truthy > > ✓ should be truthy > > ✓ should be truthy > > ✓ should be truthy > > ✓ should be truthy > > ✓ should be truthy > > ✓ assert supported; requiring does not throw > > ✓ node:assert supported; requiring does not throw > > ✓ assert/strict supported; requiring does not throw > > ✓ node:assert/strict supported; requiring does not throw > > ✓ async_hooks supported; requiring does not throw > > ✓ node:async_hooks supported; requiring does not throw > > ✓ buffer_ieee754 not supported; requiring throws > > ✓ buffer supported; requiring does not throw > > ✓ node:buffer supported; requiring does not throw > > ✓ child_process supported; requiring does not throw > > ✓ node:child_process supported; requiring does not throw > > ✓ cluster supported; requiring does not throw > > ✓ node:cluster supported; requiring does not throw > > ✓ console supported; requiring does not throw > > ✓ node:console supported; requiring does not throw > > ✓ constants supported; requiring does not throw > > ✓ node:constants supported; requiring does not throw > > ✓ crypto supported; requiring does not throw > > ✓ node:crypto supported; requiring does not throw > > ✓ _debug_agent not supported; requiring throws > > ✓ _debugger not supported; requiring throws > > ✓ dgram supported; requiring does not throw > > ✓ node:dgram supported; requiring does not throw > > ✓ diagnostics_channel supported; requiring does not throw > > ✓ node:diagnostics_channel supported; requiring does not throw > > ✓ dns supported; requiring does not throw > > ✓ node:dns supported; requiring does not throw > > ✓ dns/promises supported; requiring does not throw > > ✓ node:dns/promises supported; requiring does not throw > > ✓ domain supported; requiring does not throw > > ✓ node:domain supported; requiring does not throw > > ✓ events supported; requiring does not throw > > ✓ node:events supported; requiring does not throw > > ✓ freelist not supported; requiring throws > > ✓ fs supported; requiring does not throw > > ✓ node:fs supported; requiring does not throw > > ✓ fs/promises supported; requiring does not throw > > ✓ node:fs/promises supported; requiring does not throw > > ✓ _http_agent supported; requiring does not throw > > ✓ node:_http_agent supported; requiring does not throw > > ✓ _http_client supported; requiring does not throw > > ✓ node:_http_client supported; requiring does not throw > > ✓ _http_common supported; requiring does not throw > > ✓ node:_http_common supported; requiring does not throw > > ✓ _http_incoming supported; requiring does not throw > > ✓ node:_http_incoming supported; requiring does not throw > > ✓ _http_outgoing supported; requiring does not throw > > ✓ node:_http_outgoing supported; requiring does not throw > > ✓ _http_server supported; requiring does not throw > > ✓ node:_http_server supported; requiring does not throw > > ✓ http supported; requiring does not throw > > ✓ node:http supported; requiring does not throw > > ✓ http2 supported; requiring does not throw > > ✓ node:http2 supported; requiring does not throw > > ✓ https supported; requiring does not throw > > ✓ node:https supported; requiring does not throw > > ✓ inspector supported; requiring does not throw > > ✓ node:inspector supported; requiring does not throw > > ✓ _linklist not supported; requiring throws > > ✓ module supported; requiring does not throw > > ✓ node:module supported; requiring
Bug#1058523: node-babel7: FTBFS: ln: failed to create symbolic link 'node_modules/@babel/helper-string-parser/babel-helper-string-parser': Permission denied
Source: node-babel7 Version: 7.20.15+ds1+~cs214.269.168-5 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > set -e; for m in babel-check-duplicated-nodes > babel-plugin-dynamic-import-node babel-preset-modules > babel-plugin-transform-replace-object-assign pirates; do \ > (echo "Building $m"; \ > cd $m; \ > rm -rf lib; \ > /usr/bin/babeljs --out-dir lib src --ignore > '**/*.test.js'; \ > ); \ > ls $m/lib/*.js; \ > done > Building babel-check-duplicated-nodes > Successfully compiled 1 file with Babel (536ms). > babel-check-duplicated-nodes/lib/index.js > Building babel-plugin-dynamic-import-node > Successfully compiled 2 files with Babel (664ms). > babel-plugin-dynamic-import-node/lib/index.js > babel-plugin-dynamic-import-node/lib/utils.js > Building babel-preset-modules > Successfully compiled 8 files with Babel (734ms). > babel-preset-modules/lib/index.js > Building babel-plugin-transform-replace-object-assign > Successfully compiled 1 file with Babel (421ms). > babel-plugin-transform-replace-object-assign/lib/index.js > Building pirates > Successfully compiled 1 file with Babel (446ms). > pirates/lib/index.js > make[2]: Leaving directory '/<>' > mv node_modules.save node_modules > > Step 1: Link /usr/share/nodejs/@babel/* build dependencies into node_modules > LIST=`pkgjs-utils modules_list` && \ > for m in $LIST `pkgjs-utils main`; do \ > if [ -e /usr/share/nodejs/$m ]; then \ > rm -f node_modules/$m; \ > ln -vs /usr/share/nodejs/$m node_modules/$m || true; \ > fi; \ > done > 'node_modules/@babel/cli' -> '/usr/share/nodejs/@babel/cli' > 'node_modules/@babel/code-frame' -> '/usr/share/nodejs/@babel/code-frame' > 'node_modules/@babel/compat-data' -> '/usr/share/nodejs/@babel/compat-data' > 'node_modules/@babel/eslint-config-internal' -> > '/usr/share/nodejs/@babel/eslint-config-internal' > 'node_modules/@babel/eslint-parser' -> > '/usr/share/nodejs/@babel/eslint-parser' > 'node_modules/@babel/eslint-plugin' -> > '/usr/share/nodejs/@babel/eslint-plugin' > 'node_modules/@babel/eslint-plugin-development' -> > '/usr/share/nodejs/@babel/eslint-plugin-development' > 'node_modules/@babel/eslint-plugin-development-internal' -> > '/usr/share/nodejs/@babel/eslint-plugin-development-internal' > 'node_modules/@babel/eslint-shared-fixtures' -> > '/usr/share/nodejs/@babel/eslint-shared-fixtures' > 'node_modules/@babel/eslint-tests' -> '/usr/share/nodejs/@babel/eslint-tests' > 'node_modules/@babel/generator' -> '/usr/share/nodejs/@babel/generator' > 'node_modules/@babel/helper-annotate-as-pure' -> > '/usr/share/nodejs/@babel/helper-annotate-as-pure' > 'node_modules/@babel/helper-bindify-decorators' -> > '/usr/share/nodejs/@babel/helper-bindify-decorators' > 'node_modules/@babel/helper-builder-binary-assignment-operator-visitor' -> > '/usr/share/nodejs/@babel/helper-builder-binary-assignment-operator-visitor' > 'node_modules/@babel/helper-builder-react-jsx' -> > '/usr/share/nodejs/@babel/helper-builder-react-jsx' > 'node_modules/@babel/helper-call-delegate' -> > '/usr/share/nodejs/@babel/helper-call-delegate' > 'node_modules/@babel/helper-check-duplicate-nodes' -> > '/usr/share/nodejs/@babel/helper-check-duplicate-nodes' > 'node_modules/@babel/helper-compilation-targets' -> > '/usr/share/nodejs/@babel/helper-compilation-targets' > 'node_modules/@babel/helper-create-class-features-plugin' -> > '/usr/share/nodejs/@babel/helper-create-class-features-plugin' > 'node_modules/@babel/helper-create-regexp-features-plugin' -> > '/usr/share/nodejs/@babel/helper-create-regexp-features-plugin' > 'node_modules/@babel/helper-environment-visitor' -> > '/usr/share/nodejs/@babel/helper-environment-visitor' > 'node_modules/@babel/helper-explode-assignable-expression' -> > '/usr/share/nodejs/@babel/helper-explode-assignable-expression' > 'node_modules/@babel/helper-explode-class' -> > '/usr/share/nodejs/@babel/helper-explode-class' > 'node_modules/@babel/helper-fixtures' -> > '/usr/share/nodejs/@babel/helper-fixtures' > 'node_modules/@babel/helper-function-name' -> > '/usr/share/nodejs/@babel/helper-function-name' > 'node_modules/@babel/helper-hoist-variables' -> > '/usr/share/nodejs/@babel/helper-hoist-variables' > 'node_modules
Bug#1058522: dired-du: FTBFS: make[1]: *** [Makefile:8: test] Error 1
Source: dired-du Version: 0.5.2-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > emacs -batch -l dired-du.el -l dired-du-tests.el -f > ert-run-tests-batch-and-exit > Loading /etc/emacs/site-start.d/00debian.el (source)... > Loading /etc/emacs/site-start.d/50autoconf.el (source)... > Running 7 tests (2023-12-11 22:11:45+, selector ‘t’) > Initializing Dired-Du mode ... > Dired-Du collecting recursive dir sizes, please wait ... > Dired-Du collecting dir sizes ...(1/4) 25% > Dired-Du collecting dir sizes ...(3/4) 75% > Dired-Du collecting dir sizes ...(3/4) 75% > Dired-Du collecting dir sizes ...(3/4) 75% > Dired-Du collecting dir sizes ...(3/4) 75% > Dired-Du collecting dir sizes ...(3/4) 75% > Dired-Du collecting dir sizes ...(3/4) 75% > Dired-Du collecting dir sizes ...(3/4) 75% > Dired-Du collecting dir sizes ...(3/4) 75% > Dired-Du collecting dir sizes ...(3/4) 75% > Dired-Du collecting dir sizes ...(3/4) 75% > Dired-Du collecting dir sizes ...(3/4) 75% > Dired-Du collecting dir sizes ...(3/4) 75% > Dired-Du collecting dir sizes ...(3/4) 75% > Dired-Du collecting dir sizes ...(3/4) 75% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(4/4) 100% > Dired-Du collecting dir sizes ...(5/4) 125% > Dired-Du collecting dir sizes ...(5/4) 125% > Dired-Du collecting dir sizes ...(5/4) 125% > Dired-Du collecting dir sizes ...(6/4) 150% > Dired-Du collecting dir sizes ...(6/4) 150% > Dired-Du collecting dir sizes ...(6/4) 150% > Dired-Du collecting dir sizes ...(6/4) 150% > collection of recursive dir size: finished. > > Dired-Du collecting file info ... > Dired-Du replacing file info ... > Dired-Du collecting file info ... > Dired-Du collecting file info ...25% > Dired-Du collecting file info ...50% > Dired-Du collecting file info ...75% > Dired-Du replacing file info ...Done > > Dired-Du mode enabled in Dired buffers > Dired-Du catching file info ... > No marked files with mark ’*’ > Marking directory files... > 2 directory files marked > Dired-Du catching file info ... > Dired-Du catching file info ...done > Marked with ’*’ 2 files (2/0 dirs/files) with total size 0 bytes (dirs size > excluded) > Dired-Du catching file info ... > Dired-Du catching file info ...done > Marked with ’1’ 2 files (2/0 dirs/files) with total size 0 bytes (dirs size > excluded) > Marking matching files... > 3 matching files marked > Dired-Du catching file info ... > Dired-Du catching file info ...done > Marked with ’*’ 3 files (0/3 dirs/files) with total size 0 bytes (dirs size > excluded) > Dired-Du catching file info ... > Dired-Du catching file info ...done > Dired-Du catching file info ... > Dired-Du catching file info ...done > Dired-Du mode disabled in Dired buffers >passed 1/7 dired-du-count-sizes-test (0.673763 sec) > Initializing Dired-Du mode ...
Bug#1058521: libhinoko: FTBFS: make: *** [debian/rules:8: binary] Error 25
Source: libhinoko Version: 1.0.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- -Ddoc=true > cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 > meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr > --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu > -Dpython.bytecompile=-1 -Ddoc=true > The Meson build system > Version: 1.3.0 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: hinoko > Project version: 1.0.0 > C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-8) 13.2.0") > C linker for the host machine: cc ld.bfd 2.41.50.20231206 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1 > Run-time dependency hinawa found: YES 4.0.0 > Run-time dependency gobject-2.0 found: YES 2.78.3 > Build-time dependency glib-2.0 found: YES 2.78.3 > Program /usr/bin/glib-genmarshal found: YES (/usr/bin/glib-genmarshal) > Dependency glib-2.0 found: YES 2.78.3 (cached) > Program /usr/bin/glib-mkenums found: YES (/usr/bin/glib-mkenums) > Dependency glib-2.0 found: YES 2.78.3 (cached) > Program /usr/bin/glib-mkenums found: YES (/usr/bin/glib-mkenums) > Run-time dependency gobject-introspection-1.0 found: YES 1.78.1 > Dependency gobject-introspection-1.0 found: YES 1.78.1 (cached) > Program /usr/bin/g-ir-scanner found: YES (/usr/bin/g-ir-scanner) > Dependency gobject-introspection-1.0 found: YES 1.78.1 (cached) > Program /usr/bin/g-ir-compiler found: YES (/usr/bin/g-ir-compiler) > Program hinoko-enum found: YES (/usr/bin/python3 > /<>/tests/hinoko-enum) > Program fw-iso-ctx found: YES (/usr/bin/python3 > /<>/tests/fw-iso-ctx) > Program fw-iso-ir-single found: YES (/<>/tests/fw-iso-ir-single) > Program fw-iso-ir-multiple found: YES > (/<>/tests/fw-iso-ir-multiple) > Program fw-iso-it found: YES (/<>/tests/fw-iso-it) > Program fw-iso-resource found: YES (/usr/bin/python3 > /<>/tests/fw-iso-resource) > Program fw-iso-resource-auto found: YES (/usr/bin/python3 > /<>/tests/fw-iso-resource-auto) > Program fw-iso-resource-once found: YES (/usr/bin/python3 > /<>/tests/fw-iso-resource-once) > Program hinoko-functions found: YES (/usr/bin/python3 > /<>/tests/hinoko-functions) > Configuring hinoko.toml using configuration > Run-time dependency gi-docgen found: YES 2023.3 > Program gi-docgen found: YES (/usr/bin/gi-docgen) > Build targets in project: 8 > > hinoko 1.0.0 > > User defined options > buildtype : plain > libdir: lib/x86_64-linux-gnu > localstatedir : /var > prefix: /usr > sysconfdir: /etc > wrap_mode : nodownload > python.bytecompile: -1 > doc : true > > Found ninja-1.11.1 at /usr/bin/ninja > make[1]: Leaving directory '/<>' >dh_auto_build -O--buildsystem=meson > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j8 -v > [1/19] /usr/bin/glib-genmarshal --prefix hinoko_sigs_marshal --stdinc > --output src/hinoko_sigs_marshal.h --header ../src/hinoko_sigs_marshal.list > --pragma-once > INFO: Reading ../src/hinoko_sigs_marshal.list... > [2/19] /usr/bin/glib-genmarshal --prefix hinoko_sigs_marshal --stdinc > --output src/hinoko_sigs_marshal.c --body ../src/hinoko_sigs_marshal.list > --include-header hinoko_sigs_marshal.h > INFO: Reading ../src/hinoko_sigs_marshal.list... > [3/19] /usr/bin/meson --internal exe --unpickle > /<>/obj-x86_64-linux-gnu/meson-private/meson_exe_glib-mkenums_358aefc8a2d2e7e57b7937f58ed52edbb1e512ad.dat > [4/19] /usr/bin/meson --internal exe --unpickle > /<>/obj-x86_64-linux-gnu/meson-private/meson_exe_glib-mkenums_3897d4c04b1161abaabacfa321fbf0aa6805f8d0.dat > [5/19] cc -Isrc/libhinoko.so.1.0.0.p -Isrc -I../src -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/hinawa > -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MQ > src/libhinoko.so.1.0.0.p/meson-generated_.._hinoko_sigs_marshal.c.o -MF > src/libhinoko.so.1.0.0.p/meson-generated_.._hinoko_sigs_marshal.c.o.d -o > src/libhinoko.so.1.0.0.p/meson-generated_.._hinoko_sigs_
Bug#1058519: node-mdn-browser-compat-data: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1
Source: node-mdn-browser-compat-data
Version: 5.2.20+~3.33.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ts-node scripts/generate-types.ts
> TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for
> /<>/scripts/generate-types.ts
> at new NodeError (node:internal/errors:405:5)
> at Object.getFileProtocolModuleFormat [as file:]
> (node:internal/modules/esm/get_format:136:11)
> at defaultGetFormat (node:internal/modules/esm/get_format:182:36)
> at defaultLoad (node:internal/modules/esm/load:101:20)
> at nextLoad (node:internal/modules/esm/hooks:864:28)
> at load (/usr/share/nodejs/ts-node/dist/child/child-loader.js:19:122)
> at nextLoad (node:internal/modules/esm/hooks:864:28)
> at Hooks.load (node:internal/modules/esm/hooks:447:26)
> at MessagePort.handleMessage (node:internal/modules/esm/worker:196:24)
> at [nodejs.internal.kHybridDispatch] (node:internal/event_target:786:20) {
> code: 'ERR_UNKNOWN_FILE_EXTENSION'
> }
> make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/node-mdn-browser-compat-data_5.2.20+~3.33.0-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
Bug#1058520: qstopmotion: FTBFS: make: *** [debian/rules:7: build] Error 2
Source: qstopmotion Version: 2.5.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --buildsystem=cmake >dh_update_autotools_config -O--buildsystem=cmake >dh_autoreconf -O--buildsystem=cmake >dh_auto_configure -O--buildsystem=cmake > cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake > -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None > -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var > -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON > -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. > CMake Warning (dev) at CMakeLists.txt:30 (project): > cmake_minimum_required() should be called prior to this top-level project() > call. Please see the cmake-commands(7) manual for usage documentation of > both commands. > This warning is for project developers. Use -Wno-dev to suppress it. > > -- The C compiler identification is GNU 13.2.0 > -- The CXX compiler identification is GNU 13.2.0 > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working C compiler: /usr/bin/cc - skipped > -- Detecting C compile features > -- Detecting C compile features - done > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > CMake Deprecation Warning at CMakeLists.txt:32 (cmake_minimum_required): > Compatibility with CMake < 3.5 will be removed from a future version of > CMake. > > Update the VERSION argument value or use a ... suffix to tell > CMake that the project does not need compatibility with older versions. > > > CMAKE_GENERATOR: Unix Makefiles > Target platform: Unix 64bit > CMAKE_BUILD_TYPE: None > Qt5 Version: 5.15.10 > QT_INCLUDE_DIRS: > /usr/include/x86_64-linux-gnu/qt5/;/usr/include/x86_64-linux-gnu/qt5/QtWidgets;/usr/include/x86_64-linux-gnu/qt5/QtGui;/usr/include/x86_64-linux-gnu/qt5/QtCore;/usr/lib/x86_64-linux-gnu/qt5//mkspecs/linux-g++ > QT_DEFINITIONS: > -- Found Qwt: /usr/lib/libqwt-qt5.so (found version "6.1.4") > Qwt Version: 6.1.4 > QWT_INCLUDE_DIRS: /usr/include/qwt > QWT_LIBRARY: /usr/lib/libqwt-qt5.so > QWT_LIBRARIES: /usr/lib/libqwt-qt5.so > QWT_LIB_PATH: > -- Found PkgConfig: /usr/bin/pkg-config (found version "1.8.1") > -- Checking for module 'libgphoto2' > -- Found libgphoto2, version 2.5.31 > GPHOTO2_INCLUDE_DIR: > GPHOTO2_LIBRARIES: gphoto2;gphoto2_port;m > FindV4L2.cmake > CMake Error at cmake/FindV4L2.cmake:23 (MESSAGE): > Not found: Video4Linux2 ! > Call Stack (most recent call first): > CMakeLists.txt:551 (find_package) > > > V4L2_INCLUDE_DIRS: > V4L2_LIBRARIES: > CMake Warning (dev) at > /usr/lib/x86_64-linux-gnu/cmake/Qt5Core/Qt5CoreMacros.cmake:44 (message): > qt5_use_modules is not part of the official API, and might be removed in Qt > 6. > Call Stack (most recent call first): > /usr/lib/x86_64-linux-gnu/cmake/Qt5Core/Qt5CoreMacros.cmake:434 > (_qt5_warn_deprecated) > CMakeLists.txt:713 (qt5_use_modules) > This warning is for project developers. Use -Wno-dev to suppress it. > > UNAME Infos = > UNAME_ARCHITECTURE: > UNAME_LINUX_VERSION: > LSB Infos === > LSB_ID: > LSB_RELEASE: > LSB_DISTRIB: unix > Infos === > CPACK_SYSTEM_NAME: unix-x86_64 > CPACK_PACKAGE_ARCHITECTURE: x86_64 > End Infos === > -- Configuring incomplete, errors occurred! > cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt > ==> CMakeCache.txt <== > # This is the CMakeCache file. > # For build in directory: /<>/obj-x86_64-linux-gnu > # It was generated by CMake: /usr/bin/cmake > # You can edit this file to change values found and used by cmake. > # If you do not want to change any of the values, simply exit the editor. > # If you do want to change a value, simply edit, save, and exit the editor. > # The syntax for the file is as follows: > # KEY:TYPE=VALUE > # KEY is the name of a varia
Bug#1058516: fiat-ecmwf: FTBFS: make[1]: *** [debian/rules:42: override_dh_auto_configure] Error 2
Source: fiat-ecmwf Version: 1.0.0-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- -DENABLE_DOCS=On -DENABLE_OMP=On -DENABLE_FORTRAN=On > -DENABLE_MPI=On > cd debian/build && cmake -DCMAKE_MODULE_PATH=/usr/share/ecbuild/cmake > -DECBUILD_MACROS_DIR=/usr/share/ecbuild/cmake -DENABLE_BIT_REPRODUCIBLE=On > -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Release -DDISABLE_OS_CHECK=On > -DBUILD_SITE=debian -DCMAKE_INSTALL_LOCALSTATEDIR=/var > -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" > -DECBUILD_LOG_LEVEL=DEBUG -DCMAKE_VERBOSE_MAKEFILE=ON > -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DENABLE_DOCS=On -DENABLE_OMP=On > -DENABLE_FORTRAN=On -DENABLE_MPI=On ../.. > -- [34mDEBUG - ecbuild project(fiat) [m > CMake Deprecation Warning at > /usr/share/ecbuild/cmake/ecbuild_project.cmake:44 (cmake_minimum_required): > Compatibility with CMake < 3.5 will be removed from a future version of > CMake. > > Update the VERSION argument value or use a ... suffix to tell > CMake that the project does not need compatibility with older versions. > Call Stack (most recent call first): > CMakeLists.txt:12 (project) > > > -- The Fortran compiler identification is GNU 13.2.0 > -- The C compiler identification is GNU 13.2.0 > -- The CXX compiler identification is GNU 13.2.0 > -- Detecting Fortran compiler ABI info > -- Detecting Fortran compiler ABI info - done > -- Check for working Fortran compiler: /usr/bin/f95 - skipped > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working C compiler: /usr/bin/cc - skipped > -- Detecting C compile features > -- Detecting C compile features - done > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > -- [34mDEBUG - -[m > -- [34mDEBUG - Environment:[m > -- [34mDEBUG - - > SCHROOT_GID=1001 > DEB_HOST_MULTIARCH=x86_64-linux-gnu > LC_ALL=C.UTF-8 > DEB_HOST_GNU_SYSTEM=linux-gnu > DEB_BUILD_GNU_TYPE=x86_64-linux-gnu > DEB_TARGET_ARCH_LIBC=gnu > FFLAGS=-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -fcf-protection > -I/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13 > DEB_BUILD_ARCH_ENDIAN=little > DEB_BUILD_GNU_SYSTEM=linux-gnu > CFLAGS_FOR_BUILD=-g -O2 > OBJCXXFLAGS_FOR_BUILD=-g -O2 > DEB_BUILD_ARCH_BITS=64 > DEB_BUILD_OPTIONS=parallel=8 > DEB_HOST_ARCH=amd64 > LDFLAGS_FOR_BUILD= > DEB_TARGET_ARCH_ENDIAN=little > SOURCE_DATE_EPOCH=1674416047 > OBJCFLAGS_FOR_BUILD=-g -O2 > OBJCXXFLAGS=-g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection > DEB_HOST_ARCH_BITS=64 > LANG=C.UTF-8 > MAKEFLAGS= > SCHROOT_GROUP=user42 > DEB_TARGET_ARCH=amd64 > DH_INTERNAL_OPTIONS=-O--buildsystem=ecbuild -O--builddir=debian/build > DEB_HOST_GNU_CPU=x86_64 > DEB_BUILD_ARCH_LIBC=gnu > MFLAGS=-w > DH_VERBOSE=1 > DEB_TARGET_ARCH_BITS=64 > CXXFLAGS_FOR_BUILD=-g -O2 > ASFLAGS= > DEB_BUILD_ARCH_CPU=amd64 > LC_COLLATE=C.UTF-8 > SCHROOT_ALIAS_NAME=unstable > DEB_HOST_ARCH_OS=linux > SHELL=/bin/sh > FCFLAGS=-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -fcf-protection > DEB_HOST_ARCH_CPU=amd64 > SCHROOT_USER=user42 > PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games > DEB_BUILD_ARCH_ABI=base > CPPFLAGS_FOR_BUILD= > DEB_BUILD_ARCH=amd64 > FFLAGS_FOR_BUILD=-g -O2 > DEB_HOST_ARCH_LIBC=gnu > SCHROOT_SESSION_ID=sid-amd64-sbuild-f6222330-0d99-4406-afce-a3fe3d1b5abe > DEB_TARGET_ARCH_CPU=amd64 > DEB_HOST_GNU_TYPE=x86_64-linux-gnu > DEB_BUILD_ARCH_OS=linux > FCFLAGS_FOR_BUILD=-g -O2 > DFLAGS_FOR_BUILD=-frelease > LOGNAME=user42 > CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2 > DEB_TARGET_MULTIARCH=x86_64-linux-gnu > DEB_BUILD_GNU_CPU=x86_64 > DEB_TARGET_ARCH_OS=linux > USER=user42 > DEB_HOST_ARCH_ABI=base > DEB_BUILD_MULTIARCH=x86_64-linux-gnu > LDFLAGS=-Wl,-z,relro > FIAT_TEST_IGNORE_MPI_OUTPUT=1 > OMPI_MCA_rmaps_base_oversubscribe=1 > DEB_TARGET_GNU_TYPE=x86_64-linux-gnu > DEB_TARGET_ARCH_ABI=base > CFLAGS=-g -O2
Bug#1058518: node-es-module-lexer: FTBFS: make[1]: *** [debian/rules:11: src/lexer.js] Error 2
Source: node-es-module-lexer Version: 1.1.0+dfsg-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > tsc -m es2015 src/lexer.ts > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(325,84): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(326,85): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(327,85): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(328,84): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(330,22): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(336,35): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(337,35): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(338,32): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(339,39): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(340,42): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(341,35): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(342,38): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(343,34): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(344,37): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(360,21): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(367,21): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(374,21): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(381,21): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > make[1]: *** [debian/rules:11: src/lexer.js] Error 2 The full build log is available from: http://qa-logs.debian.net/2023/12/12/node-es-module-lexer_1.1.0+dfsg-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian
Bug#1058517: dvdisaster: FTBFS: make[2]: *** [GNUmakefile:219: manual] Error 2
Source: dvdisaster Version: 0.79.10-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > Producing user manual... > /usr/bin/gmake --no-print-directory -C documentation/user-manual manual.pdf > pdflatex manual > This is pdfTeX, Version 3.141592653-2.6-1.40.25 (TeX Live 2023/Debian) > (preloaded format=pdflatex) > restricted \write18 enabled. > entering extended mode > (./manual.tex > LaTeX2e <2023-11-01> > L3 programming layer <2023-11-09> > (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls > Document Class: article 2023/05/17 v1.4n Standard LaTeX document class > (/usr/share/texlive/texmf-dist/tex/latex/base/size12.clo)) > (/usr/share/texlive/texmf-dist/tex/latex/psnfss/times.sty) > (/usr/share/texlive/texmf-dist/tex/latex/ucs/ucs.sty > (/usr/share/texlive/texmf-dist/tex/latex/ucs/data/uni-global.def)) > (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty > (/usr/share/texlive/texmf-dist/tex/latex/ucs/utf8x.def)) > (/usr/share/texlive/texmf-dist/tex/latex/graphics/epsfig.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty) > (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty) > (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg) > (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def > (/usr/share/texlive/texmf-dist/tex/latex/anysize/anysize.sty > document style option `anysize' loaded > Michael Salzenberg, Thomas Esser, Dirk Hillbrecht > Version 1.0, Aug 13, 1994 > ) (/usr/share/texlive/texmf-dist/tex/latex/url/url.sty) > (/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty) > (/usr/share/texlive/texmf-dist/tex/latex/listings/listings.sty > (/usr/share/texlive/texmf-dist/tex/latex/listings/lstmisc.sty) > (/usr/share/texlive/texmf-dist/tex/latex/listings/listings.cfg)) > (/usr/share/texlive/texmf-dist/tex/latex/graphics/color.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg) > (/usr/share/texlive/texmf-dist/tex/latex/graphics/mathcolor.ltx)) > (/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg) > (/usr/share/texlive/texmf-dist/tex/latex/graphics/mathcolor.ltx)) > (/usr/share/texlive/texmf-dist/tex/latex/colortbl/colortbl.sty > (/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty > (/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty) > (/usr/share/texlive/texmf-dist/tex/generic/infwarerr/infwarerr.sty) > (/usr/share/texlive/texmf-dist/tex/latex/kvsetkeys/kvsetkeys.sty) > (/usr/share/texlive/texmf-dist/tex/generic/kvdefinekeys/kvdefinekeys.sty) > (/usr/share/texlive/texmf-dist/tex/generic/pdfescape/pdfescape.sty > (/usr/share/texlive/texmf-dist/tex/generic/ltxcmds/ltxcmds.sty) > (/usr/share/texlive/texmf-dist/tex/generic/pdftexcmds/pdftexcmds.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/hycolor/hycolor.sty) > (/usr/share/texlive/texmf-dist/tex/latex/letltxmacro/letltxmacro.sty) > (/usr/share/texlive/texmf-dist/tex/latex/auxhook/auxhook.sty) > (/usr/share/texlive/texmf-dist/tex/latex/hyperref/nameref.sty > (/usr/share/texlive/texmf-dist/tex/latex/refcount/refcount.sty) > (/usr/share/texlive/texmf-dist/tex/generic/gettitlestring/gettitlestring.sty > (/usr/share/texlive/texmf-dist/tex/latex/kvoptions/kvoptions.sty))) > (/usr/share/texlive/texmf-dist/tex/latex/etoolbox/etoolbox.sty) > (/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def) > (/usr/share/texlive/texmf-dist/tex/generic/intcalc/intcalc.sty) > (/usr/share/texlive/texmf-dist/tex/latex/hyperref/puenc.def) > (/usr/share/texlive/texmf-dist/tex/generic/bitset/bitset.sty > (/usr/share/texlive/texmf-dist/tex/generic/bigintcalc/bigintcalc.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/base/atbegshi-ltx.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hpdftex.def > (/usr/share/texlive/texmf-dist/tex/latex/base/atveryend-ltx.sty) > (/usr/share/texlive/texmf-dist/tex/latex/rerunfilecheck/rerunfilecheck.sty > (/usr/share/texlive/texmf-dist/tex/generic/uniquecounter/uniquecounter.sty))) > (/usr/share/texlive/texmf-dist/tex/latex/comment/comment.sty > Excluding comment 'comment') > ! Argument of ? has an extra }. > > \par > l.50 } > > ? > ! Emergency stop. > > \par > l.50 } > > ! ==> Fatal error occurred, no output PDF
Bug#1058515: node-rollup: FTBFS: make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1
Source: node-rollup Version: 3.29.4-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > rollup --config rollup.config.ts --configPlugin typescript > [1m[31m[!] [1m(plugin typescript) RollupError: @rollup/plugin-typescript > TS2769: No overload matches this call. > Overload 1 of 2, '(timeoutId: string | number | Timeout | undefined): > void', gave the following error. > Argument of type 'Timer' is not assignable to parameter of type 'string | > number | Timeout | undefined'. > Property '[Symbol.dispose]' is missing in type 'Timer' but required in > type 'Timeout'. > Overload 2 of 2, '(id: number | undefined): void', gave the following error. > Argument of type 'Timer' is not assignable to parameter of type > 'number'.[22m[1m[39m[22m > src/watch/watch.ts (60:39) > [2m > [7m60[0m if (this.buildTimeout) clearTimeout(this.buildTimeout); > [7m [0m [91m ~[0m > > > [96m../../../usr/share/nodejs/@types/node/ts4.8/timers.d.ts[0m:[93m76[0m:[93m17[0m > [7m76[0m [Symbol.dispose](): void; > [7m [0m [96m~[0m > '[Symbol.dispose]' is declared here. > [22m > [2mat error (/usr/share/nodejs/rollup/dist/shared/rollup.js:321:30) > at Object.error (/usr/share/nodejs/rollup/dist/shared/rollup.js:1689:20) > at emitDiagnostic > (/usr/share/nodejs/@rollup/plugin-typescript/dist/cjs/index.js:562:17) > at reportDiagnostics > (/usr/share/nodejs/@rollup/plugin-typescript/dist/cjs/index.js:570:9) > at Array.forEach () > at emitFilesAndReportErrors > (/usr/share/nodejs/typescript/lib/typescript.js:124992:21) > at Object.result.afterProgramCreate > (/usr/share/nodejs/typescript/lib/typescript.js:125181:13) > at Object.afterProgramCreate > (/usr/share/nodejs/@rollup/plugin-typescript/dist/cjs/index.js:728:29) > at synchronizeProgram > (/usr/share/nodejs/typescript/lib/typescript.js:125491:22) > at Object.createWatchProgram > (/usr/share/nodejs/typescript/lib/typescript.js:125408:9)[22m > > > make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/12/12/node-rollup_3.29.4-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1058513: node-signal-exit: FTBFS: SyntaxError: Cannot use import statement outside a module
Source: node-signal-exit
Version: 4.1.0-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> tsc -p tsconfig.json
> tsc -p tsconfig-esm.json
> sh ./scripts/fixup.sh
> #cp debian/index.cjs dist/cjs/
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
> ln -s ../. node_modules/signal-exit
> /bin/sh -ex debian/tests/pkg-js/test
> + tap -T -R spec test/all-integration-test.ts test/signal-exit-test.ts
>
> /<>/test/all-integration-test.ts:1
> import assert from 'assert'
> ^^
>
> SyntaxError: Cannot use import statement outside a module
> at internalCompileFunction (node:internal/vm:73:18)
> at wrapSafe (node:internal/modules/cjs/loader:1274:20)
> at Module._compile (node:internal/modules/cjs/loader:1320:27)
> at Module._extensions..js (node:internal/modules/cjs/loader:1414:10)
> at Module.load (node:internal/modules/cjs/loader:1197:32)
> at Module._load (node:internal/modules/cjs/loader:1013:12)
> at ModuleWrap. (node:internal/modules/esm/translators:202:29)
> at ModuleJob.run (node:internal/modules/esm/module_job:195:25)
> at async ModuleLoader.import (node:internal/modules/esm/loader:336:24)
> at async loadESM (node:internal/process/esm_loader:34:7)
>
> Node.js v18.19.0
> /<>/test/signal-exit-test.ts:1
> import { exec } from 'child_process'
> ^^
>
> SyntaxError: Cannot use import statement outside a module
> at internalCompileFunction (node:internal/vm:73:18)
> at wrapSafe (node:internal/modules/cjs/loader:1274:20)
> at Module._compile (node:internal/modules/cjs/loader:1320:27)
> at Module._extensions..js (node:internal/modules/cjs/loader:1414:10)
> at Module.load (node:internal/modules/cjs/loader:1197:32)
> at Module._load (node:internal/modules/cjs/loader:1013:12)
> at ModuleWrap. (node:internal/modules/esm/translators:202:29)
> at ModuleJob.run (node:internal/modules/esm/module_job:195:25)
> at async ModuleLoader.import (node:internal/modules/esm/loader:336:24)
> at async loadESM (node:internal/process/esm_loader:34:7)
>
> Node.js v18.19.0
> test/all-integration-test.ts
>
> 1) test/all-integration-test.ts
> test/signal-exit-test.ts
>
> 2) test/signal-exit-test.ts
>
> 0 passing (2s)
> 2 failing
>
> 1) test/all-integration-test.ts test/all-integration-test.ts:
> test/all-integration-test.ts
>
>
> 2) test/signal-exit-test.ts test/signal-exit-test.ts:
> test/signal-exit-test.ts
>
>
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/node-signal-exit_4.1.0-6_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
Bug#1058512: telegram-desktop: FTBFS: make[3]: *** No rule to make target 'Telegram/lib_ui/gen/emoji.cpp', needed by 'Telegram/lib_ui/CMakeFiles/lib_ui_autogen_timestamp_deps'. Stop.
Source: telegram-desktop Version: 4.11.8+ds-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends > "Unix Makefiles" /<> /<>/Telegram/lib_ui > /<>/obj-x86_64-linux-gnu > /<>/obj-x86_64-linux-gnu/Telegram/lib_ui > /<>/obj-x86_64-linux-gnu/Telegram/lib_ui/CMakeFiles/lib_ui_autogen_timestamp_deps.dir/DependInfo.cmake > "--color=" > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' > make -f > Telegram/lib_ui/CMakeFiles/lib_ui_autogen_timestamp_deps.dir/build.make > Telegram/lib_ui/CMakeFiles/lib_ui_autogen_timestamp_deps.dir/build > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > make[3]: *** No rule to make target 'Telegram/lib_ui/gen/emoji.cpp', needed > by 'Telegram/lib_ui/CMakeFiles/lib_ui_autogen_timestamp_deps'. Stop. > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' > make[2]: *** [CMakeFiles/Makefile2:2329: > Telegram/lib_ui/CMakeFiles/lib_ui_autogen_timestamp_deps.dir/all] Error 2 The full build log is available from: http://qa-logs.debian.net/2023/12/12/telegram-desktop_4.11.8+ds-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1058511: ntpsec: FTBFS: mv: cannot stat 'debian/tmp/lib/systemd/system/ntpd.service': No such file or directory
Source: ntpsec Version: 1.2.2+dfsg1-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > python3 waf install --destdir=/<>/debian/tmp > --- installing host --- > Waf: Entering directory `/<>/build/host' > Waf: Leaving directory `/<>/build/host' > --- installing main --- > Waf: Entering directory `/<>/build/main' > + install /<>/debian/tmp/usr/share/doc/ntpsec/html/asciidoc.js > (from build/main/docs/asciidoc.js) > + install /<>/debian/tmp/usr/share/doc/ntpsec/html/asciidoc.css > (from build/main/docs/asciidoc.css) > + install /<>/debian/tmp/usr/share/doc/ntpsec/html/404.html > (from build/main/docs/404.html) > + install > /<>/debian/tmp/usr/share/doc/ntpsec/html/NTS-QuickStart.html > (from build/main/docs/NTS-QuickStart.html) > + install /<>/debian/tmp/usr/share/doc/ntpsec/html/access.html > (from build/main/docs/access.html) > + install /<>/debian/tmp/usr/share/doc/ntpsec/html/accopt.html > (from build/main/docs/accopt.html) > + install /<>/debian/tmp/usr/share/doc/ntpsec/html/assoc.html > (from build/main/docs/assoc.html) > + install > /<>/debian/tmp/usr/share/doc/ntpsec/html/authentic.html (from > build/main/docs/authentic.html) > + install /<>/debian/tmp/usr/share/doc/ntpsec/html/authopt.html > (from build/main/docs/authopt.html) > + install /<>/debian/tmp/usr/share/doc/ntpsec/html/bugs.html > (from build/main/docs/bugs.html) > + install /<>/debian/tmp/usr/share/doc/ntpsec/html/build.html > (from build/main/docs/build.html) > + install /<>/debian/tmp/usr/share/doc/ntpsec/html/clock.html > (from build/main/docs/clock.html) > + install /<>/debian/tmp/usr/share/doc/ntpsec/html/clockopt.html > (from build/main/docs/clockopt.html) > + install /<>/debian/tmp/usr/share/doc/ntpsec/html/cluster.html > (from build/main/docs/cluster.html) > + install /<>/debian/tmp/usr/share/doc/ntpsec/html/comdex.html > (from build/main/docs/comdex.html) > + install /<>/debian/tmp/usr/share/doc/ntpsec/html/confopt.html > (from build/main/docs/confopt.html) > + install > /<>/debian/tmp/usr/share/doc/ntpsec/html/copyright.html (from > build/main/docs/copyright.html) > + install /<>/debian/tmp/usr/share/doc/ntpsec/html/debug.html > (from build/main/docs/debug.html) > + install /<>/debian/tmp/usr/share/doc/ntpsec/html/decode.html > (from build/main/docs/decode.html) > + install > /<>/debian/tmp/usr/share/doc/ntpsec/html/discipline.html (from > build/main/docs/discipline.html) > + install /<>/debian/tmp/usr/share/doc/ntpsec/html/discover.html > (from build/main/docs/discover.html) > + install > /<>/debian/tmp/usr/share/doc/ntpsec/html/driver_arbiter.html > (from build/main/docs/driver_arbiter.html) > + install > /<>/debian/tmp/usr/share/doc/ntpsec/html/driver_generic.html > (from build/main/docs/driver_generic.html) > + install > /<>/debian/tmp/usr/share/doc/ntpsec/html/driver_gpsd.html (from > build/main/docs/driver_gpsd.html) > + install > /<>/debian/tmp/usr/share/doc/ntpsec/html/driver_howto.html (from > build/main/docs/driver_howto.html) > + install > /<>/debian/tmp/usr/share/doc/ntpsec/html/driver_hpgps.html (from > build/main/docs/driver_hpgps.html) > + install > /<>/debian/tmp/usr/share/doc/ntpsec/html/driver_jjy.html (from > build/main/docs/driver_jjy.html) > + install > /<>/debian/tmp/usr/share/doc/ntpsec/html/driver_local.html (from > build/main/docs/driver_local.html) > + install > /<>/debian/tmp/usr/share/doc/ntpsec/html/driver_modem.html (from > build/main/docs/driver_modem.html) > + install > /<>/debian/tmp/usr/share/doc/ntpsec/html/driver_nmea.html (from > build/main/docs/driver_nmea.html) > + symlink /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libntpc.so.1 > (to libntpc.so.1.1.0) > + symlink /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libntpc.so (to > libntpc.so.1.1.0) > + install > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libntpc.so.1.1.0 (from > build/main/pylib/libntpc.so) > + install > /<>/debian/tmp/usr/share/doc/ntpsec/html/driver_oncore.html > (from build/main/docs/driver_oncore.html) > + install > /<>/debian/tmp/usr/share/doc/ntpsec/html/driver_pps.html (from > build/main/docs/driver_pps.html) > + install > /<>/debian/tmp/usr/share/doc/ntpsec/html/driver_shm.html (from > build/main/docs/driver_shm.html) > + install
Bug#1058510: kaidan: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2
Source: kaidan Version: 0.9.1-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>/obj-x86_64-linux-gnu' > Running tests... > /usr/bin/ctest --force-new-ctest-process --verbose -j8 > UpdateCTestConfiguration from > :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > UpdateCTestConfiguration from > :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > Test project /<>/obj-x86_64-linux-gnu > Constructing a list of tests > Done constructing a list of tests > Updating test list for fixtures > Added 0 tests to meet fixture requirements > Checking test dependency graph... > Checking test dependency graph end > test 1 > Start 1: PresenceCacheTest > > 1: Test command: /<>/obj-x86_64-linux-gnu/bin/PresenceCacheTest > 1: Working Directory: /<>/obj-x86_64-linux-gnu/tests > 1: Environment variables: > 1: QT_PLUGIN_PATH=/<>/obj-x86_64-linux-gnu/bin: > 1: Test timeout computed to be: 1000 > test 2 > Start 2: RosterItemWatcherTest > > 2: Test command: > /<>/obj-x86_64-linux-gnu/bin/RosterItemWatcherTest > 2: Working Directory: /<>/obj-x86_64-linux-gnu/tests > 2: Environment variables: > 2: QT_PLUGIN_PATH=/<>/obj-x86_64-linux-gnu/bin: > 2: Test timeout computed to be: 1000 > test 3 > Start 3: UserPresenceWatcherTest > > 3: Test command: > /<>/obj-x86_64-linux-gnu/bin/UserPresenceWatcherTest > 3: Working Directory: /<>/obj-x86_64-linux-gnu/tests > 3: Environment variables: > 3: QT_PLUGIN_PATH=/<>/obj-x86_64-linux-gnu/bin: > 3: Test timeout computed to be: 1000 > test 4 > Start 4: TrustDbTest > > 4: Test command: /<>/obj-x86_64-linux-gnu/bin/TrustDbTest > 4: Working Directory: /<>/obj-x86_64-linux-gnu/tests > 4: Environment variables: > 4: QT_PLUGIN_PATH=/<>/obj-x86_64-linux-gnu/bin: > 4: Test timeout computed to be: 1000 > test 5 > Start 5: OmemoDbTest > > 5: Test command: /<>/obj-x86_64-linux-gnu/bin/OmemoDbTest > 5: Working Directory: /<>/obj-x86_64-linux-gnu/tests > 5: Environment variables: > 5: QT_PLUGIN_PATH=/<>/obj-x86_64-linux-gnu/bin: > 5: Test timeout computed to be: 1000 > test 6 > Start 6: PublicGroupChatTest > > 6: Test command: /<>/obj-x86_64-linux-gnu/bin/PublicGroupChatTest > 6: Working Directory: /<>/obj-x86_64-linux-gnu/tests > 6: Environment variables: > 6: QT_PLUGIN_PATH=/<>/obj-x86_64-linux-gnu/bin: > 6: Test timeout computed to be: 1000 > 1: * Start testing of PresenceCacheTest * > 1: Config: Using QtTest library 5.15.10, Qt 5.15.10 > (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 13.2.0), > debian unknown > 3: * Start testing of UserPresenceWatcherTest * > 3: Config: Using QtTest library 5.15.10, Qt 5.15.10 > (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 13.2.0), > debian unknown > 1: PASS : PresenceCacheTest::initTestCase() > 1: PASS : PresenceCacheTest::presenceChangedSignal() > 1: PASS : PresenceCacheTest::presenceGetter(bob1) > 1: PASS : PresenceCacheTest::presenceGetter(bob2) > 1: PASS : PresenceCacheTest::presenceGetter(alice1) > 3: PASS : UserPresenceWatcherTest::initTestCase() > 1: PASS : PresenceCacheTest::presenceGetter(alice2) > 1: PASS : PresenceCacheTest::presenceGetter(unknwon presence) > 1: PASS : PresenceCacheTest::idealResource(DND) > 3: PASS : UserPresenceWatcherTest::testBasic() > 3: PASS : UserPresenceWatcherTest::cleanupTestCase() > 1: PASS : PresenceCacheTest::idealResource(Chat) > 1: PASS : PresenceCacheTest::idealResource(XA) > 1: PASS : PresenceCacheTest::idealResource(Away) > 1: PASS : PresenceCacheTest::idealResource(status text [DND]) > 1: PASS : PresenceCacheTest::idealResource(status text [XA]) > 1: PASS : PresenceCacheTest::cleanupTestCase() > 3: Totals: 3 passed, 0 failed, 0 skipped, 0 blacklisted, 1ms > 3: * Finished testing of UserPresenceWatcherTest * > 1: Totals: 14 passed, 0 failed, 0 skipped, 0 blacklisted, 1ms > 1: * Finished testing of PresenceCacheTest * > 6: * Start testing of GroupChatTest * > 6: Config: Using QtTest library 5.15.10, Qt 5.15.10 > (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 13.2.0), > debian unknown > 4: * Start testing of TrustDbTest * > 4: Config: Using QtTest library 5.15.10, Qt 5.15.10 > (x86_64-little_endian-lp64 shared
Bug#1058509: node-jest: FTBFS: make[1]: *** [debian/rules:22: override_dh_auto_build] Error 1
Source: node-jest Version: 29.6.2~ds1+~cs73.45.28-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build --buildsystem=nodejs > /!\ website/package.json not found > Unable to load website > ./lerna.json found > > workspaces field found in package.json > > Found debian/nodejs/additional_components > Adding component(s): packages/babel-jest, packages/babel-plugin-jest-hoist, > packages/babel-preset-jest, packages/diff-sequences, packages/expect, > packages/expect-utils, packages/jest, packages/jest-changed-files, > packages/jest-circus, packages/jest-cli, packages/jest-config, > packages/jest-console, packages/jest-core, > packages/jest-create-cache-key-function, packages/jest-diff, > packages/jest-docblock, packages/jest-each, packages/jest-environment, > packages/jest-environment-jsdom, packages/jest-environment-node, > packages/jest-expect, packages/jest-fake-timers, packages/jest-get-type, > packages/jest-globals, packages/jest-haste-map, packages/jest-jasmine2, > packages/jest-leak-detector, packages/jest-matcher-utils, > packages/jest-message-util, packages/jest-mock, packages/jest-phabricator, > packages/jest-regex-util, packages/jest-repl, packages/jest-reporters, > packages/jest-resolve, packages/jest-resolve-dependencies, > packages/jest-runner, packages/jest-runtime, packages/jest-schemas, > packages/jest-snapshot, packages/jest-source-map, packages/jest-test-result, > packages/jest-test-sequencer, packages/jest-transform, packages/jest-types, > packages/jest-util, packages/jest-validate, packages/jest-watcher, > packages/jest-worker, packages/pretty-format, packages/test-globals, > packages/test-utils > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known
Bug#1058508: libpdfbox-java: FTBFS: [ERROR] /<>/pdfbox/src/main/java/org/apache/pdfbox/pdmodel/encryption/PublicKeySecurityHandler.java:[431,63] cannot find symbol
Source: libpdfbox-java Version: 1:1.8.16-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > # work around downloading adobe file > mkdir -p pdfbox/target/classes/org/apache/pdfbox/resources/cmap > cp pdfbox/src/main/resources/org/apache/pdfbox/resources/cmap/* > pdfbox/target/classes/org/apache/pdfbox/resources/cmap/ > mkdir -p pdfbox/target/classes/org/apache/pdfbox/resources/afm > cp /usr/share/htmldoc/fonts/*.afm > pdfbox/target/classes/org/apache/pdfbox/resources/afm/ > cp /usr/share/aglfn/glyphlist.txt > pdfbox/target/classes/org/apache/pdfbox/resources > 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 > OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were > deprecated in JDK 13 and will likely be removed in a future release. > [0m[0m[INFO] Scanning for projects... > [INFO] > > [INFO] Reactor Build Order: > [INFO] > [INFO] Apache FontBox > [jar] > [INFO] Apache JempBox > [jar] > [INFO] Apache PDFBox > [jar] > [INFO] PDFBox reactor > [pom] > [INFO] > [INFO] -< org.apache.pdfbox:fontbox > >-- > [INFO] Building Apache FontBox 1.8.16 > [1/4] > [INFO] [ jar > ]- > [WARNING] The artifact > org.apache.maven.plugins:maven-resources-plugin:jar:2.6 has been relocated to > org.apache.maven.plugins:maven-resources-plugin:jar:3.3.0 > [WARNING] The artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.1 > has been relocated to > org.apache.maven.plugins:maven-compiler-plugin:jar:3.10.1 > [WARNING] The artifact > org.apache.maven.plugins:maven-surefire-plugin:jar:2.12.4 has been relocated > to org.apache.maven.plugins:maven-surefire-plugin:jar:2.22.3 > [WARNING] The artifact org.apache.maven.plugins:maven-jar-plugin:jar:2.4 has > been relocated to org.apache.maven.plugins:maven-jar-plugin:jar:3.3.0 > [INFO] > [INFO] --- maven-resources-plugin:3.3.0:resources (default-resources) @ > fontbox --- > [INFO] skip non existing resourceDirectory > /<>/fontbox/src/main/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.10.1:compile (default-compile) @ fontbox > --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 80 source files to /<>/fontbox/target/classes > [INFO] > /<>/fontbox/src/main/java/org/apache/fontbox/cmap/CMapParser.java: > > /<>/fontbox/src/main/java/org/apache/fontbox/cmap/CMapParser.java > uses or overrides a deprecated API that is marked for removal. > [INFO] > /<>/fontbox/src/main/java/org/apache/fontbox/cmap/CMapParser.java: > Recompile with -Xlint:removal for details. > [INFO] > /<>/fontbox/src/main/java/org/apache/fontbox/cmap/CMapParser.java: > > /<>/fontbox/src/main/java/org/apache/fontbox/cmap/CMapParser.java > uses unchecked or unsafe operations. > [INFO] > /<>/fontbox/src/main/java/org/apache/fontbox/cmap/CMapParser.java: > Recompile with -Xlint:unchecked for details. > [INFO] > [INFO] --- maven-resources-plugin:3.3.0:testResources (default-testResources) > @ fontbox --- > [INFO] Not copying test resources > [INFO] > [INFO] --- maven-compiler-plugin:3.10.1:testCompile (default-testCompile) @ > fontbox --- > [INFO] Not compiling test sources > [INFO] > [INFO] --- maven-surefire-plugin:2.22.3:test (default-test) @ fontbox --- > [INFO] Tests are skipped. > [INFO] > [INFO] --- maven-jar-plugin:3.3.0:jar (default-jar) @ fontbox --- > [INFO] Building jar: /<>/fontbox/target/fontbox-1.8.16.jar > [INFO] > [INFO] -< org.apache.pdfbox:jempbox > >-- > [INFO] Building Apache J
Bug#1058507: node-regexpp: FTBFS: make[1]: *** [debian/rules:30: override_dh_auto_build] Error 1
Source: node-regexpp
Version: 3.2.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cmark-gfm README.md > README.html
> cmark-gfm --to plaintext README.md > README.txt
> tsc --module es2015
> [96mnode_modules/@types/node/ts4.8/globals.d.ts[0m:[93m325[0m:[93m84[0m
> - [91merror[0m[90m TS2307: [0mCannot find module 'undici-types' or its
> corresponding type declarations.
>
> [7m325[0m type _Request = typeof globalThis extends { onmessage:
> any } ? {} : import("undici-types").Request;
> [7m [0m [91m
> ~~[0m
>
> [96mnode_modules/@types/node/ts4.8/globals.d.ts[0m:[93m326[0m:[93m85[0m
> - [91merror[0m[90m TS2307: [0mCannot find module 'undici-types' or its
> corresponding type declarations.
>
> [7m326[0m type _Response = typeof globalThis extends { onmessage:
> any } ? {} : import("undici-types").Response;
> [7m [0m [91m
>~~[0m
>
> [96mnode_modules/@types/node/ts4.8/globals.d.ts[0m:[93m327[0m:[93m85[0m
> - [91merror[0m[90m TS2307: [0mCannot find module 'undici-types' or its
> corresponding type declarations.
>
> [7m327[0m type _FormData = typeof globalThis extends { onmessage:
> any } ? {} : import("undici-types").FormData;
> [7m [0m [91m
>~~[0m
>
> [96mnode_modules/@types/node/ts4.8/globals.d.ts[0m:[93m328[0m:[93m84[0m
> - [91merror[0m[90m TS2307: [0mCannot find module 'undici-types' or its
> corresponding type declarations.
>
> [7m328[0m type _Headers = typeof globalThis extends { onmessage:
> any } ? {} : import("undici-types").Headers;
> [7m [0m [91m
> ~~[0m
>
> [96mnode_modules/@types/node/ts4.8/globals.d.ts[0m:[93m330[0m:[93m22[0m
> - [91merror[0m[90m TS2307: [0mCannot find module 'undici-types' or its
> corresponding type declarations.
>
> [7m330[0m : import("undici-types").RequestInit;
> [7m [0m [91m ~~[0m
>
> [96mnode_modules/@types/node/ts4.8/globals.d.ts[0m:[93m336[0m:[93m35[0m
> - [91merror[0m[90m TS2307: [0mCannot find module 'undici-types' or its
> corresponding type declarations.
>
> [7m336[0m type RequestInfo = import("undici-types").RequestInfo;
> [7m [0m [91m ~~[0m
>
> [96mnode_modules/@types/node/ts4.8/globals.d.ts[0m:[93m337[0m:[93m35[0m
> - [91merror[0m[90m TS2307: [0mCannot find module 'undici-types' or its
> corresponding type declarations.
>
> [7m337[0m type HeadersInit = import("undici-types").HeadersInit;
> [7m [0m [91m ~~[0m
>
> [96mnode_modules/@types/node/ts4.8/globals.d.ts[0m:[93m338[0m:[93m32[0m
> - [91merror[0m[90m TS2307: [0mCannot find module 'undici-types' or its
> corresponding type declarations.
>
> [7m338[0m type BodyInit = import("undici-types").BodyInit;
> [7m [0m [91m ~~[0m
>
> [96mnode_modules/@types/node/ts4.8/globals.d.ts[0m:[93m339[0m:[93m39[0m
> - [91merror[0m[90m TS2307: [0mCannot find module 'undici-types' or its
> corresponding type declarations.
>
> [7m339[0m type RequestRedirect =
> import("undici-types").RequestRedirect;
> [7m [0m [91m ~~[0m
>
> [96mnode_modules/@types/node/ts4.8/globals.d.ts[0m:[93m340[0m:[93m42[0m
> - [91merror[0m[90m TS2307: [0mCannot find module 'undici-types' or its
> corresponding type declarations.
>
> [7m340[0m type RequestCredentials =
> import("undici-types").RequestCredentials;
> [7m [0m [91m ~~[0m
>
> [96mnode_modules/@types/node/ts4.8/globals.d.ts[0m:[93m341[0m:[93m35[0m
> - [91merror[0m[90m TS2307: [0mCannot find module 'undici-types' or its
> corresponding type declarations.
>
> [7m341[0m type RequestMode = import("undici-types").R
Bug#1058506: golang-github-shenwei356-util: FTBFS: make: *** [debian/rules:4: binary] Error 25
Source: golang-github-shenwei356-util Version: 0.5.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --builddirectory=_build --buildsystem=golang --with=golang >dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang >dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang >dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang >dh_auto_build -O--builddirectory=_build -O--buildsystem=golang > cd _build && go install -trimpath -v -p 8 > github.com/shenwei356/util/bytesize github.com/shenwei356/util/byteutil > github.com/shenwei356/util/cliutil github.com/shenwei356/util/exec > github.com/shenwei356/util/math github.com/shenwei356/util/numbers > github.com/shenwei356/util/pathutil github.com/shenwei356/util/randutil > github.com/shenwei356/util/stats github.com/shenwei356/util/stringutil > github.com/shenwei356/util/struct/sa github.com/shenwei356/util/struct/stack > src/github.com/shenwei356/util/cliutil/others.go:9:2: cannot find package > "github.com/pkg/errors" in any of: > /usr/lib/go-1.21/src/github.com/pkg/errors (from $GOROOT) > /<>/_build/src/github.com/pkg/errors (from $GOPATH) > dh_auto_build: error: cd _build && go install -trimpath -v -p 8 > github.com/shenwei356/util/bytesize github.com/shenwei356/util/byteutil > github.com/shenwei356/util/cliutil github.com/shenwei356/util/exec > github.com/shenwei356/util/math github.com/shenwei356/util/numbers > github.com/shenwei356/util/pathutil github.com/shenwei356/util/randutil > github.com/shenwei356/util/stats github.com/shenwei356/util/stringutil > github.com/shenwei356/util/struct/sa github.com/shenwei356/util/struct/stack > returned exit code 1 > make: *** [debian/rules:4: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/12/12/golang-github-shenwei356-util_0.5.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1058503: ayatana-indicator-sound: FTBFS: make[3]: *** No rule to make target 'tests/gmock/lib/libgmock_main.a', needed by 'tests/integration/CMakeFiles/integration-tests_autogen_timestamp_deps'. S
Source: ayatana-indicator-sound Version: 22.9.2-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends > "Unix Makefiles" /<> /<>/tests/integration > /<>/obj-x86_64-linux-gnu > /<>/obj-x86_64-linux-gnu/tests/integration > /<>/obj-x86_64-linux-gnu/tests/integration/CMakeFiles/integration-tests_autogen_timestamp_deps.dir/DependInfo.cmake > "--color=" > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' > make -f > tests/integration/CMakeFiles/integration-tests_autogen_timestamp_deps.dir/build.make > > tests/integration/CMakeFiles/integration-tests_autogen_timestamp_deps.dir/build > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > make[3]: *** No rule to make target 'tests/gmock/lib/libgmock_main.a', needed > by 'tests/integration/CMakeFiles/integration-tests_autogen_timestamp_deps'. > Stop. > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' > make[2]: *** [CMakeFiles/Makefile2:4687: > tests/integration/CMakeFiles/integration-tests_autogen_timestamp_deps.dir/all] > Error 2 The full build log is available from: http://qa-logs.debian.net/2023/12/12/ayatana-indicator-sound_22.9.2-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1058504: lua-zlib: FTBFS: dh_auto_test: error: make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple test returned exit code 2
Source: lua-zlib
Version: 1.2-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> DEB_BUILD_MAINT_OPTIONS=hardening=-stackprotector dh build --buildsystem=lua
> --with lua
>dh_update_autotools_config -O--buildsystem=lua
>dh_autoreconf -O--buildsystem=lua
>dh_auto_configure -O--buildsystem=lua
> make --no-print-directory -f
> /usr/share/dh-lua/make/dh-lua.Makefile.multiple configure
>
> Making target configure for debian/lua5.1.dh-lua.conf
> # .install
> Filling in debian/lua-zlib.install using
> /usr/share/dh-lua/template/lib.install.in
> Adding new line: usr/lib/x86_64-linux-gnu/lua/5.1/zlib.so
> Adding new line: usr/lib/x86_64-linux-gnu/liblua5.1-zlib.so.*
> Filling in debian/lua-zlib-dev.install using
> /usr/share/dh-lua/template/dev.install.in
> Adding new line: usr/lib/x86_64-linux-gnu/liblua5.1-zlib.so
> Adding new line: usr/lib/x86_64-linux-gnu/liblua5.1-zlib.a
> Adding new line: usr/lib/x86_64-linux-gnu/pkgconfig/lua5.1-zlib.pc
> Adding new line: usr/include/lua5.1/lua-zlib.h
> # lua_versions
> Filling in debian/lua_versions
> Adding new line: 5.1
> Target configure made
>
>
> Making target configure for debian/lua5.2.dh-lua.conf
> # .install
> Filling in debian/lua-zlib.install using
> /usr/share/dh-lua/template/lib.install.in
> Adding new line: usr/lib/x86_64-linux-gnu/lua/5.2/zlib.so
> Adding new line: usr/lib/x86_64-linux-gnu/liblua5.2-zlib.so.*
> Filling in debian/lua-zlib-dev.install using
> /usr/share/dh-lua/template/dev.install.in
> Adding new line: usr/lib/x86_64-linux-gnu/liblua5.2-zlib.so
> Adding new line: usr/lib/x86_64-linux-gnu/liblua5.2-zlib.a
> Adding new line: usr/lib/x86_64-linux-gnu/pkgconfig/lua5.2-zlib.pc
> Adding new line: usr/include/lua5.2/lua-zlib.h
> # lua_versions
> Filling in debian/lua_versions
> Adding new line: 5.2
> Target configure made
>
>
> Making target configure for debian/lua5.3.dh-lua.conf
> # .install
> Filling in debian/lua-zlib.install using
> /usr/share/dh-lua/template/lib.install.in
> Adding new line: usr/lib/x86_64-linux-gnu/lua/5.3/zlib.so
> Adding new line: usr/lib/x86_64-linux-gnu/liblua5.3-zlib.so.*
> Filling in debian/lua-zlib-dev.install using
> /usr/share/dh-lua/template/dev.install.in
> Adding new line: usr/lib/x86_64-linux-gnu/liblua5.3-zlib.so
> Adding new line: usr/lib/x86_64-linux-gnu/liblua5.3-zlib.a
> Adding new line: usr/lib/x86_64-linux-gnu/pkgconfig/lua5.3-zlib.pc
> Adding new line: usr/include/lua5.3/lua-zlib.h
> # lua_versions
> Filling in debian/lua_versions
> Adding new line: 5.3
> Target configure made
>
>
> Making target configure for debian/lua5.4.dh-lua.conf
> # .install
> Filling in debian/lua-zlib.install using
> /usr/share/dh-lua/template/lib.install.in
> Adding new line: usr/lib/x86_64-linux-gnu/lua/5.4/zlib.so
> Adding new line: usr/lib/x86_64-linux-gnu/liblua5.4-zlib.so.*
> Filling in debian/lua-zlib-dev.install using
> /usr/share/dh-lua/template/dev.install.in
> Adding new line: usr/lib/x86_64-linux-gnu/liblua5.4-zlib.so
> Adding new line: usr/lib/x86_64-linux-gnu/liblua5.4-zlib.a
> Adding new line: usr/lib/x86_64-linux-gnu/pkgconfig/lua5.4-zlib.pc
> Adding new line: usr/include/lua5.4/lua-zlib.h
> # lua_versions
> Filling in debian/lua_versions
> Adding new line: 5.4
> Target configure made
>
>dh_auto_build -O--buildsystem=lua
> make --no-print-directory -f
> /usr/share/dh-lua/make/dh-lua.Makefile.multiple build
>
> Making target build for debian/lua5.1.dh-lua.conf
> libtoolize: putting auxiliary files in '.'.
> libtoolize: copying file './config.guess'
> libtoolize: copying file './config.sub'
> libtoolize: copying file './install-sh'
> libtoolize: copying file './ltmain.sh'
> libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
> libtoolize: and rerunning libtoolize and aclocal.
> libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> cd debian/.dh_lua-libtool && ./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 CFLAGS= LDFLAGS=
> LDFLAGS_STATIC=
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... x86_64-pc-linux-gnu
> checking how to print strings... printf
&
Bug#1058505: prometheus-blackbox-exporter: FTBFS: make[1]: *** [debian/rules:30: override_dh_auto_build] Error 25
Source: prometheus-blackbox-exporter Version: 0.24.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --buildsystem=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 >debian/rules override_dh_auto_build > make[1]: Entering directory '/<>' > dh_auto_build -- -ldflags " -X > github.com/prometheus/common/version.Version=0.24.0 -X > github.com/prometheus/common/version.Revision=0.24.0-1 -X > github.com/prometheus/common/version.Branch=debian/sid -X > github.com/prometheus/common/version.BuildUser=team+pkg...@tracker.debian.org > -X github.com/prometheus/common/version.BuildDate=20230614-12:34:02 -X > github.com/prometheus/common/version.GoVersion=go1.21.5" > cd build && go install -trimpath -v -p 8 -ldflags " -X > github.com/prometheus/common/version.Version=0.24.0 -X > github.com/prometheus/common/version.Revision=0.24.0-1 -X > github.com/prometheus/common/version.Branch=debian/sid -X > github.com/prometheus/common/version.BuildUser=team+pkg...@tracker.debian.org > -X github.com/prometheus/common/version.BuildDate=20230614-12:34:02 -X > github.com/prometheus/common/version.GoVersion=go1.21.5" > github.com/prometheus/blackbox_exporter > github.com/prometheus/blackbox_exporter/config > github.com/prometheus/blackbox_exporter/prober > src/github.com/prometheus/blackbox_exporter/main.go:31:2: cannot find package > "github.com/pkg/errors" in any of: > /usr/lib/go-1.21/src/github.com/pkg/errors (from $GOROOT) > /<>/build/src/github.com/pkg/errors (from $GOPATH) > dh_auto_build: error: cd build && go install -trimpath -v -p 8 -ldflags " -X > github.com/prometheus/common/version.Version=0.24.0 -X > github.com/prometheus/common/version.Revision=0.24.0-1 -X > github.com/prometheus/common/version.Branch=debian/sid -X > github.com/prometheus/common/version.BuildUser=team+pkg...@tracker.debian.org > -X github.com/prometheus/common/version.BuildDate=20230614-12:34:02 -X > github.com/prometheus/common/version.GoVersion=go1.21.5" > github.com/prometheus/blackbox_exporter > github.com/prometheus/blackbox_exporter/config > github.com/prometheus/blackbox_exporter/prober returned exit code 1 > make[1]: *** [debian/rules:30: override_dh_auto_build] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/12/12/prometheus-blackbox-exporter_0.24.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1058502: libqtdbusmock: FTBFS: make[3]: *** No rule to make target 'tests/gmock/lib/libgmock_main.a', needed by 'tests/CMakeFiles/unit-tests_autogen_timestamp_deps'. Stop.
Source: libqtdbusmock Version: 0.9.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends > "Unix Makefiles" /<> /<>/tests > /<>/obj-x86_64-linux-gnu > /<>/obj-x86_64-linux-gnu/tests > /<>/obj-x86_64-linux-gnu/tests/CMakeFiles/unit-tests_autogen_timestamp_deps.dir/DependInfo.cmake > "--color=" > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' > make -f tests/CMakeFiles/unit-tests_autogen_timestamp_deps.dir/build.make > tests/CMakeFiles/unit-tests_autogen_timestamp_deps.dir/build > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > make[3]: *** No rule to make target 'tests/gmock/lib/libgmock_main.a', needed > by 'tests/CMakeFiles/unit-tests_autogen_timestamp_deps'. Stop. > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' > make[2]: *** [CMakeFiles/Makefile2:337: > tests/CMakeFiles/unit-tests_autogen_timestamp_deps.dir/all] Error 2 The full build log is available from: http://qa-logs.debian.net/2023/12/12/libqtdbusmock_0.9.0-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1058462: texlive-bibtex-extra: file conflict with liblatex-tounicode-perl on ltx2unitxt(1) manpage
On 12.12.2023 14:07, Andreas Beckmann wrote: Hi Andreas, thanks for the report, I'll remove the manual page and the perl script from texlive-bibtex-extra . Hilmar during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. From the attached log (scroll to the bottom...): Preparing to unpack .../texlive-bibtex-extra_2023.20231207-1_all.deb ... Unpacking texlive-bibtex-extra (2023.20231207-1) ... dpkg: error processing archive /var/cache/apt/archives/texlive-bibtex-extra_2023.20231207-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/ltx2unitxt.1.gz', which is also in package liblatex-tounicode-perl 0.54-1 Errors were encountered while processing: /var/cache/apt/archives/texlive-bibtex-extra_2023.20231207-1_all.deb -- sigfault OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1057126: "AH03490: scoreboard is full" after nightly maintenance
Hi, Am 30.11.23 um 09:05 schrieb Peter Krefting: we are experiencing that the Apache httpd locks up, filling the error.log with errors after the nightly maintenance (not every night, though): [Wed Nov 29 00:00:01.922731 2023] [mpm_event:notice] [pid 62346:tid 139841215223680] AH00489: Apache/2.4.57 (Debian) mod_wsgi/4.9.4 Python/3.11 configured -- resuming normal operations [Wed Nov 29 00:00:01.922790 2023] [core:notice] [pid 62346:tid 139841215223680] AH00094: Command line: '/usr/sbin/apache2' [Wed Nov 29 00:00:03.924683 2023] [mpm_event:error] [pid 62346:tid 139841215223680] AH03490: scoreboard is full, not at MaxRequestWorkers.Increase ServerLimit. [Wed Nov 29 00:00:04.925780 2023] [mpm_event:error] [pid 62346:tid 139841215223680] AH03490: scoreboard is full, not at MaxRequestWorkers.Increase ServerLimit. (etc) I set up a nightly job to mail me the output of "apachectl status", and this is the contents reported at Nov 29 00:00:00, i.e. just before the nightly maintenance: Some processes are in "stopping" state but are not dying. They accumulate until the scoreboard is full. First you should verify with ps if the processes with the PIDs in the "(old gen)" lines still exist. If not, it is a bug in apache itself (probably in mpm_event). If they do, one needs to find out why they are not dying. This is likely the fault of some module. Third-party modules that do not come with apache itself are more likely to be the culprit. Since you are using mod_wsgi, that is a likely candidate. Look in the error log for the last log lines of the processes with those PIDs. Maybe that gives some hint. Or maybe mod_wsgi writes some logs itself, I am not familiar with that one. Apache Server Status for localhost (via ::1) Server Version: Apache/2.4.57 (Debian) mod_wsgi/4.9.4 Python/3.11 Server MPM: event Server Built: 2023-04-13T03:26:51 __ Current Time: Wednesday, 29-Nov-2023 00:00:01 CET Restart Time: Tuesday, 21-Nov-2023 08:51:55 CET Parent Server Config. Generation: 8 Parent Server MPM Generation: 7 Server uptime: 7 days 15 hours 8 minutes 6 seconds Server load: 0.01 0.02 0.00 Total accesses: 34860 - Total Traffic: 717.8 MB - Total Duration: 2289464 CPU Usage: u297.08 s30.61 cu.01 cs.07 - .0497% CPU load .0529 requests/sec - 1141 B/second - 21.1 kB/request - 65.676 ms/request 2 requests currently being processed, 48 idle workers Slot PID Stopping Connections Threads Async connections total accepting busy idle writing keep-alive closing 0 62348 yes (old gen) 0 no 0 0 0 0 0 1 62350 yes (old gen) 0 no 0 0 0 0 0 2 66497 yes (old gen) 0 no 0 0 0 0 0 3 66498 yes (old gen) 0 no 0 0 0 0 0 4 73089 yes (old gen) 0 no 0 0 0 0 0 5 73090 yes (old gen) 0 no 0 0 0 0 0 6 79644 yes (old gen) 0 no 0 0 0 0 0 7 79645 yes (old gen) 0 no 0 0 0 0 0 8 86126 yes (old gen) 0 no 0 0 0 0 0 9 86127 yes (old gen) 0 no 0 0 0 0 0 10 92669 yes (old gen) 0 no 0 0 0 0 0 11 92670 yes (old gen) 0 no 0 0 0 0 0 12 99203 yes (old gen) 0 no 0 0 0 0 0 13 99204 yes (old gen) 0 no 0 0 0 0 0 14 105761 no 0 yes 0 25 0 0 0 15 105762 no 0 yes 2 23 0 0 0 Sum 16 14 0 2 48 0 0 0 .._W W___ Scoreboard Key: "_" Waiting for Connection, "S" Starting up, "R" Reading Request, "W" Sending Reply, "K" Keepalive (read), "D" DNS Lookup, "C" Closing connection, "L" Logging, "G" Gracefully finishing, "I" Idle cleanup of worker, "." Open slot with no current process '/usr/bin/lynx -dump http://localhost:80/server-status' failed. Maybe you need to install a package providing www-browser or you need to adjust the APACHE_LYNX variable in /etc/apache2/envvars Cheers, Stefan
Bug#1008205: gamin: unmaintained upstream
On Fri, Nov 3, 2023 at 7:30 PM Bastian Germann wrote: > The reverse dependencies are all gone now. Please consider filing a RM bug. > If nobody reacts I am going to file one when gamin is removed from testing. Yes, we approve of the removal of gamin. Thank you for filing the RM bug. On behalf of the Debian GNOME team, Jeremy Bícha
Bug#1058195: toil: FTBFS: ModuleNotFoundError: No module named 'imp'
Control: tags -1 upstream Control: forwarded -1 https://github.com/DataBiosphere/toil/issues/4718 As boto upstream explained[1] boto does not support Python3.12 and toil upstream rather should switch to boto3. Kind regards Andreas. [1] https://github.com/boto/boto/issues/3951 Am Tue, Dec 12, 2023 at 06:17:19PM +0100 schrieb Andreas Tille: > Control: tags -1 pending > Control: block -1 by 1058237 > > A fix was pushed to Git, but the test suite fails due to > bug #1058237 in python3-boto. -- http://fam-tille.de
