Bug#1023865: docker.io: docker build breaks breaks host network
On Mon, Nov 14, 2022 at 03:35:26PM +0800, Shengjing Zhu wrote: > Control: retitle -1 connman should ignore veth interface > > On Mon, Nov 14, 2022 at 03:16:46AM +0800, ChangZhuo Chen (陳昌倬) wrote: > > Control: reassign -1 connman > > Control: tags - moreinfo unreproducible > > > > The problem is fixed by removing connman. connman seem to wrongly assign > > IP address to bridge port interface (e.g. veth??), and this causes > > problem in host network. > > > > This issue is similar to [0]. > > > > [0] https://unix.stackexchange.com/q/648084/11640 > > > > So connman should have something like: > https://salsa.debian.org/utopia-team/network-manager/-/blob/debian/master/data/85-nm-unmanaged.rules Archwiki does mention this issue with docker. https://wiki.archlinux.org/title/ConnMan#Blacklist_interfaces
Bug#1023007: tex-common: configuration fails due to "Illegal instruction" on i386
Control: retitle -1 luatex has no support for CPU's w/o SSE2 Control: tags -1 + wontfix Am 29.10.2022 um 04:51 teilte G.raud mit: Hi, When trying to reconfigure the package tex-common (whose configuration had already failed previously): I just found the upstream bug: http://tracker.luatex.org/view.php?id=1008 Tag it wontfix. Sorry! H. -- sigfault
Bug#1023865: docker.io: docker build breaks breaks host network
Control: retitle -1 connman should ignore veth interface On Mon, Nov 14, 2022 at 03:16:46AM +0800, ChangZhuo Chen (陳昌倬) wrote: > Control: reassign -1 connman > Control: tags - moreinfo unreproducible > > The problem is fixed by removing connman. connman seem to wrongly assign > IP address to bridge port interface (e.g. veth??), and this causes > problem in host network. > > This issue is similar to [0]. > > [0] https://unix.stackexchange.com/q/648084/11640 > So connman should have something like: https://salsa.debian.org/utopia-team/network-manager/-/blob/debian/master/data/85-nm-unmanaged.rules
Bug#844741: [ristretto] Segafault when run as root
Control: tags -1 unreproducible Control: retitle -1 'ristretto: SEGV when run as root' With ristretto 0.12.3, I can run it as root. The errors are similar but it doesn't segfault. Can you reproduce it in the latest version? Thanks.
Bug#1024056: new upstream
Package: firmware-sof-signed Version: 2.2.2-1 No mic on Lenovo X1 Carbon Gen 10. There are several BRs about missing microphone on various laptops. Since there is a new upstream version I wonder if it could be included? Regards Harri
Bug#609905: adjust info
Control: tag -1 + moreinfo unreproducible Adding some info to an old bug report. This request is questionable. In my opinion, this should be configurable if anything. The problem is that it might be necessary to do it one way or another. One scenario is to create a temporary share to copy some stuff, connect to it, start the copy process and remove it before the copy is complete - so that there's nothing to clean up afrerwards, there's no need to babysit the long copy process. In this case, obviously, it's not a good idea to kill the running connection, which leads to data corruption too. And another scenario is maybe to kill some misbehaving session, - in this case maybe deleting the share is a wrong thing to do. But the original bug report was about something else really: when you delete a share, samba keeps the port busy. Which is true indeed, because samba should be running as a daemon, regardless of the shares configured in Nautilus. And this does *not*, despite what initial report says, prevents one from creating other (user)shares, even usershares with the same name as has just been deleted. So I'm adding a "moreinfo" here again. What exact behavour we're discussing here, what exactly is wrong? Adding "moreinfo" for now, but I'm just this >< close to closing this bug. Thanks, /mjt
Bug#886241: config file directories hidden in /usr/share/lightdm
Control: tags -1 wontfix Just to expand on what Yves-Alexis said. On Wed, 3 Jan 2018 13:42:38 +0100 Harald Dunkel wrote: > lightdm and lightdm-gtk-greeter hide some config file directories > in /usr/share/lightdm. According to the debian policy manual 4.1.3.0 > they must reside in /etc. They do not hide their configuration files. Note that the parts of the policy that touches on the filesystem layout are only a subset of the FHS—Filesystem Hierarchy Standard, which reserves the /usr/share hierarchy for "for all read-only architecture independent data files." What constitutes data files is entirely up to individual packages. Having two distinct hierarchies for configuration files eases package maintenance and allows distributions to ship their defauts in /usr/share that are usually overridden by those in /etc (maintained by the end-user and the system administrator). This is exactly what LightDM does and even mentions in its README file, shipped with the package and available at /usr/share/doc/lightdm. Debian defaults are stored in /usr/share/lightdm/lightdm.conf.d/01_debian.conf. > The man pages don't mention these config files in /usr, i.e. you get > weird effects due to some undocumented config files. They shouldn't. From the README file: > System provided configuration should be stored in > `/usr/share/lightdm/lightdm.conf.d/`. > System administrators can override this configuration by adding files to > `/etc/lightdm/lightdm.conf.d/` and `/etc/lightdm/lightdm.conf` The fact that it's not mentioned in the man page hints that a user is not supposed to even know the existence of /usr/share/lightdm, let alone touch the files in it. Consider configuration files under /usr/share as read-only (even though most of them are writable) and a mechanism to provide sane defaults and fallback. You're rarely supposed to edit them. Of course, there are some exceptions.
Bug#1024055: buster-pu: package mariadb-10.3 10.3.37-0+deb10u1
Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu I propose that the latest version of MariaDB 10.3.37 would be included in the upcoming (old)stable release update of Debian. Package almost ready at https://salsa.debian.org/mariadb-team/mariadb-10.3/-/commits/buster Before I submit the final debdiff and changelog I will wait for the release date to show up at https://release.debian.org/ or other indication of the final date. Current changelog: mariadb-10.3 (1:10.3.37-0+deb10u1) UNRELEASED; urgency=medium * New upstream version 10.3.37. -- Otto Kekäläinen Fri, 11 Nov 2022 20:54:48 -0800 This release does not (at least not yet) have any CVE tracked vulnerabilities. I realize you might not be interested to include this in a LTS release if there are no critical fixes to point out, but I decided to file this anyway, as the bug email will act as a communication channel about the next pending MariaDB upload to Buster. - Otto
Bug#1024054: bullseye-pu: package mariadb-10.5 10.5.18-0+deb11u1
Package: release.debian.org Severity: normal Tags: bullseye User: release.debian@packages.debian.org Usertags: pu I propose that the latest version of MariaDB 10.5.18 would be included in the upcoming stable release update of Debian. Package almost ready at https://salsa.debian.org/mariadb-team/mariadb-10.5/-/commits/bullseye Before I submit the final debdiff and changelog I will wait for the release date to show up at https://release.debian.org/ Current changelog: mariadb-10.5 (1:10.5.18-0+deb11u1) UNRELEASED; urgency=medium * New upstream version 10.5.18. * New upstream version 10.5.17. Includes security fixes for - CVE-2018-25032 - CVE-2022-32081 - CVE-2022-32082 - CVE-2022-32084 - CVE-2022-32089 - CVE-2022-32091 * New upstream version 10.5.16. Includes security fixes for - CVE-2021-46669 - CVE-2022-27376 - CVE-2022-27377 - CVE-2022-27378 - CVE-2022-27379 - CVE-2022-27380 - CVE-2022-27381 - CVE-2022-27382 - CVE-2022-27383 - CVE-2022-27384 - CVE-2022-27386 - CVE-2022-27387 - CVE-2022-27444 - CVE-2022-27445 - CVE-2022-27446 - CVE-2022-27447 - CVE-2022-27448 - CVE-2022-27449 - CVE-2022-27451 - CVE-2022-27452 - CVE-2022-27455 - CVE-2022-27456 - CVE-2022-27457 - CVE-2022-27458 - CVE-2022-32083 - CVE-2022-32085 - CVE-2022-32086 - CVE-2022-32087 - CVE-2022-32088 -- Otto Kekäläinen Fri, 11 Nov 2022 18:33:01 -0800
Bug#1024053: yggdrasil: document how to ensure starting before sshd & other services
Package: yggdrasil Version: 0.4.6-1~bpo11+1 Severity: wishlist Hi, I have a machine with sshd disabled on the public interfaces, and instead set to bind to yggdrasil's ipv6 address in sshd_config: ListenAddress [201:dd5a: ... ]:22 This works great when the machine's already running, and I restart sshd. However, when the machine first boots up, sshd fails to bind to the yggdrasil ipv6 interface; likely because sshd comes up before yggdrasil is finished initializing the interface. I tried running "systemctl edit yggdrasil.service" and inserting the following: [Unit] Before=ssh.service Similarly, I also edited editing ssh.service and adding an "After=yggdrasil.service". Neither seemed to fix the issue after rebooting. Instead, sshd continues refusing to listen on the ipv6 interface until I manually restart ssh. I'd suggest documenting the proper way to handle this in README.Debian. For now, I'm simply creating an /etc/cron.d/yggdrasil that contains "@reboot root sleep 60 && systemctl restart ssh", which is pretty hackish. Thanks, Andres
Bug#834724: curl: (35) gnutls_handshake() failed: Public key signature verification has failed.
On Sat, 12 Nov 2016 20:22:21 -0500 Kamaraju Kusumanchi wrote: > Confirm that Tim Small solution worked for me as well. I am running > Debian Stretch and removing libgnutls-deb0-28 fixed the error. > > -- System Information: > Debian Release: stretch/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: sysvinit (via /sbin/init) > > Versions of packages curl depends on: > ii libc62.24-3 > ii libcurl3-gnutls 7.50.1-1 > ii zlib1g 1:1.2.8.dfsg-2+b1 > > curl recommends no packages. > > curl suggests no packages. > > -- no debconf information > > -- > Kamaraju S. Kusumanchi > http://raju.shoutwiki.com/wiki/Blog > >
Bug#981713: graftcp: Change Architecture from "any" to "amd64"
Source: graftcp Version: 0.1.3+ds1-1 Followup-For: Bug #981713 Dear Maintainer, This package is only compatitable with amd64 (i386/amd64/aarch64 for upstream), on amd64 it need header file, which is only available on amd64 (for aarch64 it use some arm assembly code). maybe we should change debian/control from "any" to "amd64". Debian salsa: v0.3 (amd64 only) <-- current package upstream stable: v0.4 (amd64 only) upstream latest: v0.5.0-beta.1 (i386/amd64/aarch64) Thanks, Yifan Xu
Bug#1024052: export MAXJIGDOS=ALL has error in Debian 11 bullseye
Package: simple-cdd Version: 0.6.8 Severity: normal X-Debbugs-Cc: atzli...@sina.com Hi, I use "export MAXJIGDOS=ALL" in my build.conf to get jigdo files. It has no problem in Debian 10, but the same build.conf has error in Debian 11. 2022-11-14 11:32:41,691 DEBUG build/debian-cd stdout: xorriso -as mkisofs -r -checksum_algorithm_iso sha256,sha512 -V 'atzlinux 11.5.1 amd64 1' -o /home/atzlinux/isodvd/images/atzlinux-11.5.1-amd64-DVD-1.iso -checksum-list /home/atzlinux/isodvd/tmp/cd-build/bullseye/checksum-check -jigdo-checksum-algorithm -jigdo-force-checksum /pool/ -jigdo-jigdo /home/atzlinux/isodvd/images/atzlinux-11.5.1-amd64-DVD-1.jigdo -jigdo-template /home/atzlinux/isodvd/images/atzlinux-11.5.1-amd64-DVD-1.template -jigdo-map Debian=/home/atzlinux/isodvd/tmp/mirror/ -jigdo-exclude boot1 -J -joliet-long -cache-inodes -isohybrid-mbr syslinux/usr/lib/ISOLINUX/isohdpfx.bin -b isolinux/isolinux.bin -c isolinux/boot.cat -boot-load-size 4 -boot-info-table -no-emul-boot -eltorito-alt-boot -e boot/grub/efi.img -no-emul-boot -isohybrid-gpt-basdat -isohybrid-apm-hfsplus boot1 CD1 2022-11-14 11:32:41,694 DEBUG build/debian-cd stderr: xorriso 1.5.2 : RockRidge filesystem manipulator, libburnia project. 2022-11-14 11:32:41,694 DEBUG build/debian-cd stderr: 2022-11-14 11:32:41,695 DEBUG build/debian-cd stderr: Drive current: -outdev 'stdio:/home/atzlinux/isodvd/images/atzlinux-11.5.1-amd64-DVD-1.iso' 2022-11-14 11:32:41,695 DEBUG build/debian-cd stderr: Media current: stdio file, overwriteable 2022-11-14 11:32:41,695 DEBUG build/debian-cd stderr: Media status : is blank 2022-11-14 11:32:41,695 DEBUG build/debian-cd stderr: Media summary: 0 sessions, 0 data blocks, 0 data, 11.4g free 2022-11-14 11:32:41,695 DEBUG build/debian-cd stderr: xorriso : WARNING : -volid text problematic as automatic mount point name 2022-11-14 11:32:41,696 DEBUG build/debian-cd stderr: xorriso : WARNING : -volid text does not comply to ISO 9660 / ECMA 119 rules 2022-11-14 11:32:41,696 DEBUG build/debian-cd stderr: xorriso : FAILURE : libjte: Unknown checksum algorithm -jigdo-force-checksum 2022-11-14 11:32:41,696 DEBUG build/debian-cd stderr: xorriso : FAILURE : Experienced libjte failure with: -jigdo -jigdo-checksum-algorithm -jigdo-force-checksum 2022-11-14 11:32:41,696 DEBUG build/debian-cd stderr: xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE' 2022-11-14 11:32:41,698 DEBUG build/debian-cd stderr: make: *** [Makefile:498：images] error 5 2022-11-14 11:32:41,698 DEBUG build/debian-cd retval: 2 2022-11-14 11:32:41,699 ERROR build/debian-cd exited with code 2 2022-11-14 11:32:41,699 ERROR Last 5 lines of standard error: 2022-11-14 11:32:41,699 ERROR build/debian-cd: xorriso : WARNING : -volid text does not comply to ISO 9660 / ECMA 119 rules 2022-11-14 11:32:41,699 ERROR build/debian-cd: xorriso : FAILURE : libjte: Unknown checksum algorithm -jigdo-force-checksum 2022-11-14 11:32:41,699 ERROR build/debian-cd: xorriso : FAILURE : Experienced libjte failure with: -jigdo -jigdo-checksum-algorithm -jigdo-force-checksum 2022-11-14 11:32:41,699 ERROR build/debian-cd: xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE' 2022-11-14 11:32:41,699 ERROR build/debian-cd: make: *** [Makefile:498：images] error 5 2022-11-14 11:32:41,700 ERROR build/debian-cd exited with code 2, full log can be found in /home/atzlinux/isodvd/tmp/log/build-debian-c In Debian 11, xorriso --version is 1.5.2. In debian-cd package(version is 3.1.35 in Debian 11), there is one xorriso verison compare in: https://salsa.debian.org/images-team/debian-cd/-/blob/master/tools/make_image#L97 When simple-cdd run on Debian 10(xorriso 1.5.0), JIGDO_CHECKSUM_OPTS will use -jigdo-force-md5, it's no problem; But when simple-cdd run on Debian 11(xorriso 1.5.2), JIGDO_CHECKSUM_OPTS will be -jigdo-checksum-algorithm $JIGDO_CHECKSUM, unfortunately, the $JIGDO_CHECKSUM is not exist in Debian 11 when running simple-cdd. After I add "export JIGDO_CHECKSUM="md5"" in my build.conf, the build will success. In debian-cd package, the $JIGDO_CHECKSUM had set in: https://salsa.debian.org/images-team/debian-cd/-/blob/master/CONF.sh#L191 but simple-cdd has not use this variable in the building default. Is this a bug of simple-cdd? or debian-cd? I suggest use(pass) JIGDO_CHECKSUM="md5" default in simple-cdd. Thanks! xiao sheng wen https://www.atzlinux.com 《铜豌豆 Linux》基于 Debian 的 Linux 中文 桌面 操作系统 Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com Debian salsa: https://salsa.debian.org/atzlinux-guest GnuPG Public Key: 0x00186602339240CB -- System Information: Release:11.5 Codename: bullseye Architecture: x86_64 Kernel: Linux 5.10.0-19-rt-amd64 (SMP w/4 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 simple-cdd depends
Bug#1024041: mariadb-10.6: FTBFS on riscv64: rocksdb/db/memtable.cc:129: undefined reference to `__atomic_compare_exchange_1'
Hi, On Sun, Nov 13, 2022 at 02:49:13PM -0800, Otto Kekäläinen wrote: Source: mariadb-10.6 Version: 1:10.6.9-1 Tags: upstream, confirmed, ftbfs User: debian-ri...@lists.debian.org Usertags: riscv64, riscv X-Debbugs-CC: debian-ri...@lists.debian.org After upload of mariadb-10.6 1:10.6.9-1 I noticed that riscv64 builds at https://buildd.debian.org/status/package.php?p=mariadb-10.6 were failing: ... /usr/bin/ld: /usr/include/c++/12/bits/atomic_base.h:523: undefined reference to `__atomic_compare_exchange_1' /usr/bin/ld: librocksdblib.a(memtable.cc.o):/usr/include/c++/12/bits/atomic_base.h:523: more undefined references to `__atomic_compare_exchange_1' follow ... storage/sphinx/CMakeFiles/sphinx.dir/snippets_udf.cc.o -MF CMakeFiles/sphinx.dir/snippets_udf.cc.o.d -o CMakeFiles/sphinx.dir/snippets_udf.cc.o -c /<>/storage/sphinx/snippets_udf.cc collect2: error: ld returned 1 exit status make[4]: *** [storage/rocksdb/CMakeFiles/sst_dump.dir/build.make:105: storage/rocksdb/sst_dump] Error 1 make[4]: Leaving directory '/<>/builddir' make[3]: *** [CMakeFiles/Makefile2:7827: storage/rocksdb/CMakeFiles/sst_dump.dir/all] Error 2 This is a regression as riscv64 builds used to work on MariaD 10.6.8-1: https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.6=riscv64=1%3A10.6.8-1=1653304190=0 This build failure due to atomic issue on riscv64. Now we have a lot of packages has the issue. While waiting for the gcc patch(can be backported is ok also), we are also thinking of a better solution to sove the issue from a broader perspective. For mariadb-10.6-1:10.6.10-1, I will test the patch and it will be sent if everything is ok. PS: I remerber try to build it with fixed the issue, but still fail due to another issue. -- Regards, -- Bo YU signature.asc Description: PGP signature
Bug#1007556: uqm-content: please consider upgrading to 3.0 source format
Package: uqm-content Followup-For: Bug #1007556 X-Debbugs-Cc: mnalis-debian...@voyager.hr Dear Maintainer, it has been fixed in uqm-content 0.8.0+deb-1 in Bookworm.
Bug#1024051: RFS: wiki2beamer/0.10.0-5 -- Tool to create LaTeX beamer presentations in wiki syntax
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "wiki2beamer": * Package name : wiki2beamer Version : 0.10.0-5 Upstream contact : Valentin Haenel * URL : https://wiki2beamer.github.io/ * License : GPL-2+, GFDL-1.3+ * Vcs : https://salsa.debian.org/debian/wiki2beamer Section : text The source builds the following binary packages: wiki2beamer - Tool to create LaTeX beamer presentations in wiki syntax To access further information about this package, please visit the following URL: https://mentors.debian.net/package/wiki2beamer/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/w/wiki2beamer/wiki2beamer_0.10.0-5.dsc Changes since the last upload: wiki2beamer (0.10.0-5) unstable; urgency=medium . * debian/control: - Bumped Standards-Version to 4.6.1 - Adjusted dependencies * debian/watch: - Properly find tarballs. - Removed filenamemangle. * Adjusted year in debian/copyright. * Fixed debian/upstream/metadata (Bug-Tracking -> Bug-Database). * Adjusted debian/patches/010_fix-doc-makefile.patch to point to related issue on upstream repository. Regards, Francisco M Neto
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
On Sat, Nov 12, 2022 at 03:17:01PM +0100, Andreas Tille wrote: > Am Sun, Nov 06, 2022 at 07:55:33PM -0500 schrieb Thomas Dickey: > > On Tue, Nov 01, 2022 at 09:23:55AM +0100, Andreas Tille wrote: > > > Am Sun, Oct 30, 2022 at 04:53:24PM -0400 schrieb Thomas Dickey: > > > > > > $ grep font /etc/X11/Xresources/xterm | grep -v ^! > > > > > > *VT100.utf8Fonts.font: fixed > > > > what locale settings are you using? > > > > (that might be relevant - or the choice of desktop/window-manager) > > $ locale > LANG=de_DE.UTF-8 > LANGUAGE= > LC_CTYPE="de_DE.UTF-8" > LC_NUMERIC="de_DE.UTF-8" > LC_TIME="de_DE.UTF-8" > LC_COLLATE="de_DE.UTF-8" > LC_MONETARY="de_DE.UTF-8" > LC_MESSAGES="de_DE.UTF-8" > LC_PAPER="de_DE.UTF-8" > LC_NAME="de_DE.UTF-8" > LC_ADDRESS="de_DE.UTF-8" > LC_TELEPHONE="de_DE.UTF-8" > LC_MEASUREMENT="de_DE.UTF-8" > LC_IDENTIFICATION="de_DE.UTF-8" > LC_ALL= I tried that - no change > Desktop environment is xfce4. > > > > Sorry its "comment". > > > > > > > > (the grep seems to indicate that the latter is meant) > > > > > > > > > > > crash with segmentation fault when not finding some specified font. > > > > I suppose the problem is something along the lines of the X server > > returning some error in using the fonts. If it were TrueType fonts, > > I'd use strace to verify that they're opened -- but for bitmap > > fonts, that's done on the server side. > > I admit I'm fine with any nicely readable font. I once considered the > terminus fonts to fit this requirement and never found any reason > to change this. > > > > The crash happens for > > > > > > $ xrdb -query > > > *VT100.utf8Fonts.font: fixed > > > XTermVT100.faceSize:22 > > > XTerm*geometry: 111x36 > > > > hmm - I'm still not seeing _this_ problem. > > (by the way, the geometry resource is over-broad, making the font-menu > > less than useful). > > I've made the Geometry that size to fit exactly a quarter of my screen > fitting 4 xterms at one time. Xfce4 places these intelligently in a > 2x2 matrix. Something like this will work, but fixing the problem with the menus: XTerm*VT100.geometry: 111x36 It's in the FAQ: https://invisible-island.net/xterm/xterm.faq.html#tiny_menus > > I used xcfe4 for testing, on a virtual machine. > > > > My most recent snapshot (from 2022/11/01) didn't work - some problem > > with X and the window manaager), so I upgraded from 2022/10/29, > > to get a workable machine. > > > > Given that (I also have the terminus font installed), > > I used "xrdb -load" with these resources, and ran xterm > > from the Debian package. It looks okay to me - no crash. > > I'm using Debian packages exclusively - I have no time to spent > extra fancy things. BTW. I'm observing the very same bug on my > second laptop I'm using for traveling (but my desktop with the > same setup works without any problem) > > Could you send me the full command line >"xrdb -load ??" I pasted the text from earlier mail as "bad.ad" (attached), and loaded it with xrdb -load bad.ad > I could check here. What strace call should I send to track > down the issue. Please note that while I'm an experienced I'd just strace -o trace.log -s 1024 xterm to capture a long trace (~200kb), and look to see if there's something interesting where xterm dies. I also ran xterm using -report-fonts, which shows the fonts opened. > Debian user and long year developer I would not consider myself > an X expert. > > Kind regards > >Andreas. > > -- > http://fam-tille.de -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net Loaded VTFonts(font6) fNorm: -*-terminus-*-*-*-32-*-*-*-*-*-*-* all chars: no default char: 63 direction: 0 ascent:26 descent: 6 first char:0 last char: 255 maximum-chars: 256 missing-chars: 37 present-chars: 219 min_byte1: 0 max_byte1: 0 properties:22 min_bounds: lbearing: 0 rbearing: 0 width:16 ascent: -1 descent: -22 max_bounds: lbearing: 6 rbearing: 16 width:16 ascent: 26 descent: 6 fBold: -xos4-Terminus-bold-R-*-*-32-320-72-72-C-160-ISO8859-1 all chars: no default char: 63 direction: 0 ascent:26 descent: 6 first char:0 last char: 255 maximum-chars: 256 missing-chars: 37 present-chars: 219 min_byte1: 0
Bug#1024050: python-cytoolz FTBFS with Python 3.11 as supported version
Source: python-cytoolz
Version: 0.11.0-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=python-cytoolz=0.11.0-2%2Bb2
...
=== FAILURES ===
__ test_random_sample __
def test_random_sample():
alist = list(range(100))
assert list(random_sample(prob=1, seq=alist, random_state=2016)) ==
alist
mk_rsample = lambda rs=1: list(random_sample(prob=0.1,
seq=alist,
random_state=rs))
rsample1 = mk_rsample()
assert rsample1 == mk_rsample()
rsample2 = mk_rsample(1984)
randobj = Random(1984)
assert rsample2 == mk_rsample(randobj)
assert rsample1 != rsample2
> assert mk_rsample(object) == mk_rsample(object)
cytoolz/tests/test_itertoolz.py:545:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
cytoolz/tests/test_itertoolz.py:533: in
mk_rsample = lambda rs=1: list(random_sample(prob=0.1,
cytoolz/itertoolz.pyx:1794: in cytoolz.itertoolz.random_sample.__cinit__
random_state = Random(random_state)
/usr/lib/python3.11/random.py:125: in __init__
self.seed(x)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = , a = , version = 2
def seed(self, a=None, version=2):
"""Initialize internal state from a seed.
The only supported seed types are None, int, float,
str, bytes, and bytearray.
None or no argument seeds from current time or from an operating
system specific randomness source if available.
If *a* is an int, all bits are used.
For version 2 (the default), all of the bits are used if *a* is a str,
bytes, or bytearray. For version 1 (provided for reproducing random
sequences from older versions of Python), the algorithm for str and
bytes generates a narrower range of seeds.
"""
if version == 1 and isinstance(a, (str, bytes)):
a = a.decode('latin-1') if isinstance(a, bytes) else a
x = ord(a[0]) << 7 if a else 0
for c in map(ord, a):
x = ((103 * x) ^ c) & 0x
x ^= len(a)
a = -2 if x == -1 else x
elif version == 2 and isinstance(a, (str, bytes, bytearray)):
if isinstance(a, str):
a = a.encode()
a = int.from_bytes(a + _sha512(a).digest())
elif not isinstance(a, (type(None), int, float, str, bytes, bytearray)):
> raise TypeError('The only supported seed types are: None,\n'
'int, float, str, bytes, and bytearray.')
E TypeError: The only supported seed types are: None,
E int, float, str, bytes, and bytearray.
/usr/lib/python3.11/random.py:160: TypeError
=== warnings summary ===
cytoolz/compatibility.py:2
/<>/.pybuild/cpython3_3.11_cytoolz/build/cytoolz/compatibility.py:2:
DeprecationWarning: The toolz.compatibility module is no longer needed in
Python 3 and has been deprecated. Please import these utilities directly from
the standard library. This module will be removed in a future release.
warnings.warn("The toolz.compatibility module is no longer "
.pybuild/cpython3_3.11_cytoolz/build/cytoolz/tests/test_tlz.py::test_tlz
/usr/lib/python3.11/importlib/__init__.py:126: DeprecationWarning: The
toolz.compatibility module is no longer needed in Python 3 and has been
deprecated. Please import these utilities directly from the standard library.
This module will be removed in a future release.
return _bootstrap._gcd_import(name[level:], package, level)
-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=== short test summary info
FAILED cytoolz/tests/test_itertoolz.py::test_random_sample - TypeError: The o...
== 1 failed, 186 passed, 2 warnings in 1.79s ===
E: pybuild pybuild:379: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.11_cytoolz/build; python3.11 -m pytest
...
Bug#1021541: lomiri-terminal-app: ships a copy of qml-module-qmltermwidget
Followup-For: Bug #1021541 There is now a separate source package src:qmltermwidget building qml-module-termwidget. Please use that. Andreas
Bug#1024049: python-clevercsv FTBFS with Python 3.11 as supported version
Source: python-clevercsv Version: 0.7.4+ds-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=python-clevercsv=0.7.4%2Bds-2%2Bb1 ... I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build; python3.11 -m unittest discover -v -f -s tests/test_unit test_get_best_set_1 (test_consistency.ConsistencyTestCase.test_get_best_set_1) ... ok test_get_best_set_2 (test_consistency.ConsistencyTestCase.test_get_best_set_2) ... ok test_code_1 (test_console.ConsoleTestCase.test_code_1) ... ERROR /usr/lib/python3.11/unittest/case.py:622: ResourceWarning: unclosed file <_io.TextIOWrapper name=3 mode='w' encoding='UTF-8'> with outcome.testPartExecutor(self): ResourceWarning: Enable tracemalloc to get the object allocation traceback == ERROR: test_code_1 (test_console.ConsoleTestCase.test_code_1) -- Traceback (most recent call last): File "/<>/.pybuild/cpython3_3.11/build/tests/test_unit/test_console.py", line 126, in test_code_1 tmpfname = self._build_file(table, dialect) File "/<>/.pybuild/cpython3_3.11/build/tests/test_unit/test_console.py", line 28, in _build_file w = writer(tmpid, dialect=dialect) ^^ File "/<>/.pybuild/cpython3_3.11/build/clevercsv/write.py", line 32, in __init__ self._writer = csv.writer(csvfile, dialect=self.dialect) ^ TypeError: "quotechar" must be a 1-character string -- Ran 3 tests in 0.004s FAILED (errors=1) E: pybuild pybuild:379: test: plugin distutils failed with: exit code=1: cd /<>/.pybuild/cpython3_3.11/build; python3.11 -m unittest discover -v -f -s tests/test_unit ...
Bug#1024048: pyliblo FTBFS with Python 3.11 as supported version
Source: pyliblo Version: 0.10.0-5 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=pyliblo=0.10.0-5%2Bb2 ... testSendReceive (test.test_liblo.DecoratorTestCase.testSendReceive) ... AttributeError: module 'inspect' has no attribute 'getargspec' Exception ignored in: 'liblo._msg_callback' Traceback (most recent call last): File "/<>/test/test_liblo.py", line 270, in testSendReceive self.assertTrue(self.server.recv()) ^^ AttributeError: module 'inspect' has no attribute 'getargspec' ERROR testNoPermission (test.test_liblo.ServerCreationTestCase.testNoPermission) ... ok testPort (test.test_liblo.ServerCreationTestCase.testPort) ... ok testPortProto (test.test_liblo.ServerCreationTestCase.testPortProto) ... ok testRandomPort (test.test_liblo.ServerCreationTestCase.testRandomPort) ... ok testSendReceive (test.test_liblo.ServerTCPTestCase.testSendReceive) ... AttributeError: module 'inspect' has no attribute 'getargspec' Exception ignored in: 'liblo._msg_callback' Traceback (most recent call last): File "/<>/test/test_liblo.py", line 226, in testSendReceive self.assertTrue(self.server.recv()) ^^ AttributeError: module 'inspect' has no attribute 'getargspec' ERROR testBundleCallbacksFire (test.test_liblo.ServerTestCase.testBundleCallbacksFire) ... AttributeError: module 'inspect' has no attribute 'getargspec' Exception ignored in: 'liblo._msg_callback' Traceback (most recent call last): File "/<>/test/test_liblo.py", line 144, in testSendBundle self.assertTrue(self.server.recv(100)) ^ AttributeError: module 'inspect' has no attribute 'getargspec' AttributeError: module 'inspect' has no attribute 'getargspec' Exception ignored in: 'liblo._msg_callback' Traceback (most recent call last): File "/<>/test/test_liblo.py", line 144, in testSendBundle self.assertTrue(self.server.recv(100)) ^ AttributeError: module 'inspect' has no attribute 'getargspec' ERROR testMethodAfterFree (test.test_liblo.ServerTestCase.testMethodAfterFree) ... ok testPort (test.test_liblo.ServerTestCase.testPort) ... ok testRecvImmediate (test.test_liblo.ServerTestCase.testRecvImmediate) ... ok testRecvTimeout (test.test_liblo.ServerTestCase.testRecvTimeout) ... ok testSendBlob (test.test_liblo.ServerTestCase.testSendBlob) ... AttributeError: module 'inspect' has no attribute 'getargspec' Exception ignored in: 'liblo._msg_callback' Traceback (most recent call last): File "/<>/test/test_liblo.py", line 75, in testSendBlob self.assertTrue(self.server.recv()) ^^ AttributeError: module 'inspect' has no attribute 'getargspec' ERROR testSendBundle (test.test_liblo.ServerTestCase.testSendBundle) ... AttributeError: module 'inspect' has no attribute 'getargspec' Exception ignored in: 'liblo._msg_callback' Traceback (most recent call last): File "/<>/test/test_liblo.py", line 144, in testSendBundle self.assertTrue(self.server.recv(100)) ^ AttributeError: module 'inspect' has no attribute 'getargspec' AttributeError: module 'inspect' has no attribute 'getargspec' Exception ignored in: 'liblo._msg_callback' Traceback (most recent call last): File "/<>/test/test_liblo.py", line 144, in testSendBundle self.assertTrue(self.server.recv(100)) ^ AttributeError: module 'inspect' has no attribute 'getargspec' ERROR testSendInt (test.test_liblo.ServerTestCase.testSendInt) ... AttributeError: module 'inspect' has no attribute 'getargspec' Exception ignored in: 'liblo._msg_callback' Traceback (most recent call last): File "/<>/test/test_liblo.py", line 65, in testSendInt self.assertTrue(self.server.recv()) ^^ AttributeError: module 'inspect' has no attribute 'getargspec' ERROR testSendInvalid (test.test_liblo.ServerTestCase.testSendInvalid) ... ok testSendLong (test.test_liblo.ServerTestCase.testSendLong) ... AttributeError: module 'inspect' has no attribute 'getargspec' Exception ignored in: 'liblo._msg_callback' Traceback (most recent call last): File "/<>/test/test_liblo.py", line 128, in testSendLong self.assertTrue(self.server.recv()) ^^ AttributeError: module 'inspect' has no attribute 'getargspec' ERROR testSendMessage (test.test_liblo.ServerTestCase.testSendMessage) ... AttributeError: module 'inspect' has no attribute 'getargspec' Exception ignored in: 'liblo._msg_callback' Traceback (most recent call last): File "/<>/test/test_liblo.py", line 118, in testSendMessage self.assertTrue(self.server.recv()) ^^ AttributeError: module 'inspect' has no attribute 'getargspec' ERROR testSendOthers (test.test_liblo.ServerTestCase.testSendOthers) ... AttributeError: module 'inspect' has no attribute
Bug#1024047: python-line-profiler FTBFS with Python 3.11 as supported version
Source: python-line-profiler
Version: 2.1-3
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=python-line-profiler=2.1-3%2Bb4
...
_line_profiler.c: In function ‘__pyx_f_14_line_profiler_python_trace_callback’:
_line_profiler.c:5627:46: error: invalid use of incomplete typedef
‘PyFrameObject’ {aka ‘struct _frame’}
5627 | __pyx_t_1 = ((PyObject *)__pyx_v_py_frame->f_code);
| ^~
_line_profiler.c:5835:58: error: invalid use of incomplete typedef
‘PyFrameObject’ {aka ‘struct _frame’}
5835 | __pyx_t_1 = __Pyx_PyInt_From_int(__pyx_v_py_frame->f_lineno);
if (unlikely(!__pyx_t_1)) __PYX_ERR(0, 218, __pyx_L1_error)
| ^~
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1:
/usr/bin/python3.11 setup.py build
Bug#1024046: pyopencl FTBFS with Python 3.11 as supported version
Source: pyopencl
Version: 2022.1.6-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=pyopencl=amd64=2022.1.6-2%2Bb1=1668366441=0
...
=== FAILURES ===
_ test_elwise_kernel[>] _
ctx_factory =
def test_elwise_kernel(ctx_factory):
context = ctx_factory()
queue = cl.CommandQueue(context)
from pyopencl.clrandom import rand as clrand
> a_gpu = clrand(queue, (50,), np.float32)
test_algorithm.py:52:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
../pyopencl/clrandom.py:767: in rand
gen.fill_uniform(result, a=a, b=b)
../pyopencl/clrandom.py:681: in fill_uniform
return self._fill("uniform", ary,
../pyopencl/clrandom.py:658: in _fill
self.get_gen_kernel(ary.dtype, distribution)
/usr/lib/python3/dist-packages/pytools/__init__.py:696: in wrapper
result = function(obj, *args, **kwargs)
../pyopencl/clrandom.py:641: in get_gen_kernel
knl.set_scalar_arg_dtypes(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self =
arg_types = (, , , , , None, ...)
def kernel_set_arg_types(self, arg_types):
arg_types = tuple(arg_types)
# {{{ arg counting bug handling
# For example:
# https://github.com/pocl/pocl/issues/197
# (but Apple CPU has a similar bug)
work_around_arg_count_bug = False
warn_about_arg_count_bug = False
from pyopencl.characterize import has_struct_arg_count_bug
count_bug_per_dev = [
has_struct_arg_count_bug(dev, self.context)
for dev in self.context.devices]
from pytools import single_valued
if any(count_bug_per_dev):
if all(count_bug_per_dev):
work_around_arg_count_bug = single_valued(count_bug_per_dev)
else:
warn_about_arg_count_bug = True
# }}}
from pyopencl.invoker import generate_enqueue_and_set_args
enqueue, my_set_args = \
generate_enqueue_and_set_args(
self.function_name,
len(arg_types), self.num_args,
arg_types,
warn_about_arg_count_bug=warn_about_arg_count_bug,
work_around_arg_count_bug=work_around_arg_count_bug,
devs=self.context.devices)
# Make ourselves a kernel-specific class, so that we're able to override
# __call__. Inspired by https://stackoverflow.com/a/38541437
class KernelWithCustomEnqueue(type(self)):
__call__ = enqueue
set_args = my_set_args
> self.__class__ = KernelWithCustomEnqueue
E TypeError: __class__ assignment: 'KernelWithCustomEnqueue' object
layout differs from 'pyopencl._cl.Kernel'
../pyopencl/__init__.py:878: TypeError
_ test_elwise_kernel_with_options[>] _
ctx_factory =
def test_elwise_kernel_with_options(ctx_factory):
from pyopencl.clrandom import rand as clrand
from pyopencl.elementwise import ElementwiseKernel
context = ctx_factory()
queue = cl.CommandQueue(context)
> in_gpu = clrand(queue, (50,), np.float32)
...
= 203 failed, 57 passed, 6 skipped, 1 deselected, 2 xfailed, 19 warnings in
115.65s (0:01:55) =
E: pybuild pybuild:379: test: plugin custom failed with: exit code=1:
PYTHONPATH=/<>/.pybuild/cpython3_3.11/build cp -r
/<>/test /<>/.pybuild/cpython3_3.11/build && cd
/<>/.pybuild/cpython3_3.11/build/test && python3.11 -m pytest
--verbosity=2 -k 'not test_event_set_callback' && rm -rf
/<>/.pybuild/cpython3_3.11/build/test
...
Bug#1024045: python-pomegranate FTBFS with Python 3.11 as supported version
Source: python-pomegranate Version: 0.14.8-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=python-pomegranate=0.14.8-1%2Bb1 ... == ERROR: test suite for >/.pybuild/cpython3_3.11_pomegranate/build/tests/test_profile_hmm.py'> -- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/suite.py", line 209, in run self.setUp() File "/usr/lib/python3/dist-packages/nose/suite.py", line 292, in setUp self.setupContext(ancestor) File "/usr/lib/python3/dist-packages/nose/suite.py", line 315, in setupContext try_run(context, names) File "/usr/lib/python3/dist-packages/nose/util.py", line 453, in try_run inspect.getargspec(func) ^^ AttributeError: module 'inspect' has no attribute 'getargspec' -- Ran 362 tests in 13.186s FAILED (errors=10) E: pybuild pybuild:379: test: plugin distutils failed with: exit code=1: cd /<>/.pybuild/cpython3_3.11_pomegranate/build; python3.11 -m nose -v tests ...
Bug#1024044: python-ltfatpy FTBFS with Python 3.11 as supported version
Source: python-ltfatpy
Version: 1.0.16-7
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=python-ltfatpy=sid
...
=== FAILURES ===
TestGabWin.test_composed_dictionnaries_entries
self =
def test_composed_dictionnaries_entries(self):
a = random.randint(10, 40)
M = random.randint(10, 40)
L = lcm(a, M)
# default
self.assertRaises(TypeError, gabwin, {'name': 1}, a, M, L)
# dual psech
tfr = 10
gd = {'name': ('dual', 'sech'), 'tfr': tfr}
mess = "a = {0:d}, M = {1:d}, L = {2:d}".format(a, M, L)
mess += str(gd)
(g, info) = gabwin(gd, a, M, L)
mess += "\ng = " + str(g)
mess += "\ninfo = " + str(info)
self.assertFalse(info['gauss'], mess)
self.assertTrue(info['wasreal'], mess)
self.assertFalse(info['istight'], mess)
self.assertTrue(info['isdual'], mess)
self.assertFalse(info['wasrow'], mess)
self.assertFalse(info['isfir'], mess)
self.assertEqual(info['auxinfo']["tfr"], tfr, mess)
self.assertEqual(info["gl"], len(g), mess)
gt = gabdual(psech(L, tfr)[0], a, M, L)
mess += "\ngt = " + str(gt)
np.testing.assert_array_almost_equal(g, gt, 10, mess)
self.assertRaises(ValueError, gabwin, gd, a, M)
# dual pgauss
tfr = 10
gd = {'name': ('dual',), 'tfr': tfr}
mess = "a = {0:d}, M = {1:d}, L = {2:d}".format(a, M, L)
mess += str(gd)
(g, info) = gabwin(gd, a, M, L)
mess += "\ng = " + str(g)
mess += "\ninfo = " + str(info)
self.assertTrue(info['auxinfo']['gauss'], mess)
self.assertTrue(info['wasreal'], mess)
self.assertFalse(info['istight'], mess)
self.assertTrue(info['isdual'], mess)
self.assertFalse(info['wasrow'], mess)
self.assertFalse(info['isfir'], mess)
self.assertEqual(info['auxinfo']["tfr"], tfr, mess)
self.assertEqual(info["gl"], len(g), mess)
gt = gabdual(pgauss(L, tfr)[0], a, M, L)
mess += "\ngt = " + str(gt)
np.testing.assert_array_almost_equal(g, gt, 10, mess)
self.assertRaises(ValueError, gabwin, gd, a, M)
# dual fir
> name = random.sample(arg_firwin(), 1)[0]
ltfatpy/tests/gabor/test_gabwin.py:356:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self =
population = {'bartlett', 'blackman', 'blackman2', 'cosine', 'hamming', 'hann',
...}
k = 1
def sample(self, population, k, *, counts=None):
"""Chooses k unique random elements from a population sequence.
Returns a new list containing elements from the population while
leaving the original population unchanged. The resulting list is
in selection order so that all sub-slices will also be valid random
samples. This allows raffle winners (the sample) to be partitioned
into grand prize and second place winners (the subslices).
Members of the population need not be hashable or unique. If the
population contains repeats, then each occurrence is a possible
selection in the sample.
Repeated elements can be specified one at a time or with the optional
counts parameter. For example:
sample(['red', 'blue'], counts=[4, 2], k=5)
is equivalent to:
sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5)
To choose a sample from a range of integers, use range() for the
population argument. This is especially fast and space efficient
for sampling from a large population:
sample(range(1000), 60)
"""
# Sampling without replacement entails tracking either potential
# selections (the pool) in a list or previous selections in a set.
# When the number of selections is small compared to the
# population, then tracking selections is efficient, requiring
# only a small set and an occasional reselection. For
# a larger number of selections, the pool tracking method is
# preferred since the list takes less space than the
# set and it doesn't suffer from frequent reselections.
# The number of calls to _randbelow() is kept at or near k, the
# theoretical minimum. This is important because running time
# is dominated by _randbelow() and because it extracts the
# least entropy from the underlying random number generators.
# Memory requirements are kept to the smaller of a k-length
# set or an n-length list.
# There are other sampling algorithms that do not require
# auxiliary memory, but they were rejected because they made
# too many calls to _randbelow(), making
Bug#1024043: python-cassandra-driver FTBFS with Python 3.11 as supported version
Source: python-cassandra-driver Version: 3.25.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=python-cassandra-driver=3.25.0-1%2Bb2 ... == ERROR: Failure: AttributeError (module 'asyncio' has no attribute 'coroutine') -- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest raise self.exc_val.with_traceback(self.tb) File "/usr/lib/python3/dist-packages/nose/loader.py", line 416, in loadTestsFromName module = self.importer.importFromPath( ^ File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in importFromPath return self.importFromDir(dir_path, fqname) File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in importFromDir mod = load_module(part_fqname, fh, filename, desc) File "/usr/lib/python3.11/imp.py", line 235, in load_module return load_source(name, filename, file) ^ File "/usr/lib/python3.11/imp.py", line 172, in load_source module = _load(spec) ^^^ File "", line 721, in _load File "", line 690, in _load_unlocked File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "/<>/.pybuild/cpython3_3.11_cassandra/build/tests/unit/io/test_asyncioreactor.py", line 3, in from cassandra.io.asyncioreactor import AsyncioConnection File "/<>/.pybuild/cpython3_3.11_cassandra/build/cassandra/io/asyncioreactor.py", line 29, in class AsyncioTimer(object): File "/<>/.pybuild/cpython3_3.11_cassandra/build/cassandra/io/asyncioreactor.py", line 49, in AsyncioTimer @asyncio.coroutine ^ AttributeError: module 'asyncio' has no attribute 'coroutine' == FAIL: test_immutable_predicate (tests.unit.test_policies.HostFilterPolicyInitTest.test_immutable_predicate) -- AttributeError: property 'predicate' of 'HostFilterPolicy' object has no setter During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/<>/.pybuild/cpython3_3.11_cassandra/build/tests/unit/test_policies.py", line 1304, in test_immutable_predicate with self.assertRaisesRegexp(AttributeError, expected_message_regex): AssertionError: "can't set attribute" does not match "property 'predicate' of 'HostFilterPolicy' object has no setter" -- Ran 611 tests in 20.442s FAILED (SKIP=28, errors=1, failures=1) E: pybuild pybuild:379: test: plugin distutils failed with: exit code=1: cd /<>/.pybuild/cpython3_3.11_cassandra/build; python3.11 -m nose -v tests
Bug#1024042: python-jpype FTBFS with Python 3.11 as supported version
Source: python-jpype
Version: 1.4.0-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=python-jpype=1.4.0-2%2Bb1
...
native/common/jp_exception.cpp: In function ‘PyTracebackObject*
tb_create(PyTracebackObject*, PyObject*, const char*, const char*, int)’:
native/common/jp_exception.cpp:524:23: error: ‘PyThreadState’ {aka ‘struct
_ts’} has no member named ‘frame’; did you mean ‘cframe’?
524 | state.frame = last_traceback->tb_frame;
| ^
| cframe
native/common/jp_exception.cpp:526:23: error: ‘PyThreadState’ {aka ‘struct
_ts’} has no member named ‘frame’; did you mean ‘cframe’?
526 | state.frame = NULL;
| ^
| cframe
native/common/jp_exception.cpp:552:36: error: invalid use of incomplete type
‘PyFrameObject’ {aka ‘struct _frame’}
552 | traceback->tb_lasti = frame->f_lasti;
|^~
In file included from /usr/include/python3.11/Python.h:42,
from native/common/jp_exception.cpp:16:
/usr/include/python3.11/pytypedefs.h:22:16: note: forward declaration of
‘PyFrameObject’ {aka ‘struct _frame’}
22 | typedef struct _frame PyFrameObject;
|^~
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1:
/usr/bin/python3.11 setup.py build
Bug#1024041: mariadb-10.6: FTBFS on riscv64: rocksdb/db/memtable.cc:129: undefined reference to `__atomic_compare_exchange_1'
Source: mariadb-10.6 Version: 1:10.6.9-1 Tags: upstream, confirmed, ftbfs User: debian-ri...@lists.debian.org Usertags: riscv64, riscv X-Debbugs-CC: debian-ri...@lists.debian.org After upload of mariadb-10.6 1:10.6.9-1 I noticed that riscv64 builds at https://buildd.debian.org/status/package.php?p=mariadb-10.6 were failing: cd /<>/builddir/storage/innobase && /usr/bin/c++ -DBTR_CUR_ADAPT -DBTR_CUR_HASH_ADAPT -DCOMPILER_HINTS -DDBUG_TRACE -DEMBEDDED_LIBRARY -DHAVE_CONFIG_H -DHAVE_FALLOC_PUNCH_HOLE_AND_KEEP_SIZE=1 -DHAVE_LIBNUMA=1 -DHAVE_LZ4=1 -DHAVE_LZ4_COMPRESS_DEFAULT=1 -DHAVE_SCHED_GETCPU=1 -DHAVE_SNAPPY=1 -DHAVE_URING -D_FILE_OFFSET_BITS=64 -I/<>/wsrep-lib/include -I/<>/wsrep-lib/wsrep-API/v26 -I/<>/builddir/include -I/<>/storage/innobase/include -I/<>/storage/innobase/handler -I/<>/libbinlogevents/include -I/<>/tpool -I/<>/include -I/<>/sql -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -pie -fPIC -fstack-protector --param=ssp-buffer-size=4 -Wconversion -Wno-sign-conversion -O2 -g -static-libgcc -fno-omit-frame-pointer -fno-strict-aliasing -Wno-uninitialized -fno-omit-frame-pointer -D_FORTIFY_SOURCE=2 -DDBUG_OFF -Wall -Wenum-compare -Wenum-conversion -Wextra -Wformat-security -Wno-format-truncation -Wno-init-self -Wno-nonnull-compare -Wno-unused-parameter -Woverloaded-virtual -Wnon-virtual-dtor -Wvla -Wwrite-strings -Wdate-time -D_FORTIFY_SOURCE=2 -DUNIV_LINUX -D_GNU_SOURCE=1 -DHAVE_OPENSSL -DOPENSSL_API_COMPAT=0x1010L -fPIC -fvisibility=hidden -std=gnu++11 -MD -MT storage/innobase/CMakeFiles/innobase_embedded.dir/row/row0quiesce.cc.o -MF CMakeFiles/innobase_embedded.dir/row/row0quiesce.cc.o.d -o CMakeFiles/innobase_embedded.dir/row/row0quiesce.cc.o -c /<>/storage/innobase/row/row0quiesce.cc librocksdblib.a(memtable.cc.o): in function `rocksdb::MemTable::ApproximateMemoryUsage()': ./builddir/storage/rocksdb/./storage/rocksdb/rocksdb/db/memtable.cc:129: undefined reference to `__atomic_compare_exchange_1' /usr/bin/ld: librocksdblib.a(memtable.cc.o): in function `std::__atomic_base::compare_exchange_weak(bool&, bool, std::memory_order, std::memory_order)': /usr/include/c++/12/bits/atomic_base.h:523: undefined reference to `__atomic_compare_exchange_1' /usr/bin/ld: /usr/include/c++/12/bits/atomic_base.h:523: undefined reference to `__atomic_compare_exchange_1' /usr/bin/ld: /usr/include/c++/12/bits/atomic_base.h:523: undefined reference to `__atomic_compare_exchange_1' /usr/bin/ld: /usr/include/c++/12/bits/atomic_base.h:523: undefined reference to `__atomic_compare_exchange_1' /usr/bin/ld: librocksdblib.a(memtable.cc.o):/usr/include/c++/12/bits/atomic_base.h:523: more undefined references to `__atomic_compare_exchange_1' follow [ 53%] Building CXX object storage/sphinx/CMakeFiles/sphinx.dir/snippets_udf.cc.o cd /<>/builddir/storage/sphinx && /usr/bin/c++ -DDBUG_TRACE -DHAVE_CONFIG_H -DMYSQL_DYNAMIC_PLUGIN -DMYSQL_SERVER -D_FILE_OFFSET_BITS=64 -Dsphinx_EXPORTS -I/<>/wsrep-lib/include -I/<>/wsrep-lib/wsrep-API/v26 -I/<>/builddir/include -I/<>/include -I/<>/sql -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -pie -fPIC -fstack-protector --param=ssp-buffer-size=4 -Wno-write-strings -O2 -g -static-libgcc -fno-omit-frame-pointer -fno-strict-aliasing -Wno-uninitialized -fno-omit-frame-pointer -D_FORTIFY_SOURCE=2 -DDBUG_OFF -Wall -Wenum-compare -Wenum-conversion -Wextra -Wformat-security -Wno-format-truncation -Wno-init-self -Wno-nonnull-compare -Wno-unused-parameter -Woverloaded-virtual -Wnon-virtual-dtor -Wvla -Wwrite-strings -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++11 -MD -MT storage/sphinx/CMakeFiles/sphinx.dir/snippets_udf.cc.o -MF CMakeFiles/sphinx.dir/snippets_udf.cc.o.d -o CMakeFiles/sphinx.dir/snippets_udf.cc.o -c /<>/storage/sphinx/snippets_udf.cc collect2: error: ld returned 1 exit status make[4]: *** [storage/rocksdb/CMakeFiles/sst_dump.dir/build.make:105: storage/rocksdb/sst_dump] Error 1 make[4]: Leaving directory '/<>/builddir' make[3]: *** [CMakeFiles/Makefile2:7827: storage/rocksdb/CMakeFiles/sst_dump.dir/all] Error 2 This is a regression as riscv64 builds used to work on MariaD 10.6.8-1: https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.6=riscv64=1%3A10.6.8-1=1653304190=0 Neither me nor upstream has any Alpha expertise. Please help by providing info on this bug report or - preferably - submit a MR to fix this: https://salsa.debian.org/mariadb-team/mariadb-server/-/wikis/Contributing-to-MariaDB-packaging-in-Debian
Bug#1024040: mariadb-10.6: FTBFS on alpha: relocation truncated to fit: GPREL16 against symbol `wsrep_debug'
Source: mariadb-10.6 Version: 1:10.6.7-1 Tags: upstream, confirmed, ftbfs User: debian-al...@lists.debian.org Usertags: alpha X-Debbugs-CC: debian-al...@lists.debian.org After upload of mariadb-10.6 1:10.6.7-1 I noticed that alpha builds at https://buildd.debian.org/status/package.php?p=mariadb-10.6 were failing: cd /<>/builddir/extra/mariabackup && /usr/bin/cmake -E cmake_link_script CMakeFiles/mariadb-backup.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -specs=/usr/share/dpkg/pie-compile.specs -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -pie -fPIC -fstack-protector --param=ssp-buffer-size=4 -Wconversion -Wno-sign-conversion -O2 -g -static-libgcc -fno-omit-frame-pointer -fno-strict-aliasing -Wno-uninitialized -fno-omit-frame-pointer -D_FORTIFY_SOURCE=2 -DDBUG_OFF -Wall -Wenum-compare -Wenum-conversion -Wextra -Wformat-security -Wno-format-truncation -Wno-init-self -Wno-nonnull-compare -Wno-unused-parameter -Woverloaded-virtual -Wnon-virtual-dtor -Wvla -Wwrite-strings -specs=/usr/share/dpkg/pie-link.specs -Wl,-z,relro -Wl,-z,now -Wl,-z,relro,-z,now -Wl,--export-dynamic "CMakeFiles/mariadb-backup.dir/xtrabackup.cc.o" "CMakeFiles/mariadb-backup.dir/innobackupex.cc.o" "CMakeFiles/mariadb-backup.dir/changed_page_bitmap.cc.o" "CMakeFiles/mariadb-backup.dir/datasink.cc.o" "CMakeFiles/mariadb-backup.dir/ds_buffer.cc.o" "CMakeFiles/mariadb-backup.dir/ds_compress.cc.o" "CMakeFiles/mariadb-backup.dir/ds_local.cc.o" "CMakeFiles/mariadb-backup.dir/ds_stdout.cc.o" "CMakeFiles/mariadb-backup.dir/ds_tmpfile.cc.o" "CMakeFiles/mariadb-backup.dir/ds_xbstream.cc.o" "CMakeFiles/mariadb-backup.dir/fil_cur.cc.o" "CMakeFiles/mariadb-backup.dir/quicklz/quicklz.c.o" "CMakeFiles/mariadb-backup.dir/read_filt.cc.o" "CMakeFiles/mariadb-backup.dir/write_filt.cc.o" "CMakeFiles/mariadb-backup.dir/wsrep.cc.o" "CMakeFiles/mariadb-backup.dir/xbstream_write.cc.o" "CMakeFiles/mariadb-backup.dir/backup_mysql.cc.o" "CMakeFiles/mariadb-backup.dir/backup_copy.cc.o" "CMakeFiles/mariadb-backup.dir/encryption_plugin.cc.o" "CMakeFiles/mariadb-backup.dir/__/__/sql/sql_builtin.cc.o" "CMakeFiles/mariadb-backup.dir/__/__/sql/net_serv.cc.o" "CMakeFiles/mariadb-backup.dir/__/__/libmysqld/libmysql.c.o" -o mariadb-backup -pthread -llz4 -lsnappy -lnuma ../../sql/libsql.a ../../sql/libsql_builtins.a ../../vio/libvio.a -lpcre2-8 -lcrypt ../../storage/maria/libaria.a ../../mysys_ssl/libmysys_ssl.a ../../sql/libpartition.a ../../storage/perfschema/libperfschema.a ../../sql/libsql_sequence.a ../../sql/libwsrep.a ../../storage/csv/libcsv.a ../../storage/heap/libheap.a ../../storage/innobase/libinnobase.a -llz4 -lsnappy -lnuma ../../tpool/libtpool.a -luring -lsystemd ../../storage/myisam/libmyisam.a ../../mysys/libmysys.a ../../dbug/libdbug.a ../../strings/libstrings.a ../../mysys/libmysys.a ../../dbug/libdbug.a ../../strings/libstrings.a -lz -lm ../../storage/myisammrg/libmyisammrg.a ../../storage/sequence/libsequence.a ../../plugin/auth_socket/libauth_socket.a ../../plugin/feedback/libfeedback.a -lssl -lcrypto ../../plugin/type_geom/libtype_geom.a ../../plugin/type_inet/libtype_inet.a ../../plugin/user_variables/libuser_variables.a ../../plugin/userstat/libuserstat.a ../../wsrep-lib/src/libwsrep-lib.a -lpthread -ldl ../../wsrep-lib/wsrep-API/libwsrep_api_v26.a ../../sql/libthread_pool_info.a -pthread ../../sql/libwsrep.a(wsrep_client_service.cc.o): in function `Wsrep_client_service::interrupted(std::unique_lock&) const': ./builddir/sql/./sql/wsrep_client_service.cc:77:(.text+0x140): relocation truncated to fit: GPREL16 against symbol `wsrep_debug' defined in .sbss section in ../../sql/libwsrep.a(wsrep_mysqld.cc.o) ../../sql/libwsrep.a(wsrep_client_service.cc.o): in function `Wsrep_client_service::cleanup_transaction()': ./builddir/sql/./sql/wsrep_client_service.cc:149:(.text+0x1d8): relocation truncated to fit: GPREL16 against symbol `WSREP_PROVIDER_EXISTS_' defined in .sbss section in ../../sql/libwsrep.a(wsrep_mysqld.cc.o) ./builddir/sql/./sql/wsrep_client_service.cc:149:(.text+0x1f4): relocation truncated to fit: GPREL16 against symbol `wsrep_emulate_bin_log' defined in .sbss section in ../../sql/libwsrep.a(wsrep_mysqld.cc.o) ../../sql/libwsrep.a(wsrep_client_service.cc.o): in function `wsrep::server_state::id() const': ./builddir/sql/./wsrep-lib/include/wsrep/server_state.hpp:210:(.text+0x39c): relocation truncated to fit: GPREL16 against symbol `Wsrep_server_state::m_instance' defined in .sbss section in ../../sql/libwsrep.a(wsrep_mysqld.cc.o) ../../sql/libwsrep.a(wsrep_client_service.cc.o): in function `Wsrep_client_service::remove_fragments()': ./builddir/sql/./sql/wsrep_client_service.cc:217:(.text+0x3bc): relocation truncated to fit: GPREL16 against symbol `wsrep_schema' defined in .sbss section in ../../sql/libwsrep.a(wsrep_mysqld.cc.o)
Bug#1024039: Current default JDK should be updated in Lintian
Package: lintian Version: 2.115.3 Severity: normal Dear Maintainer, Recently, java-common was updated in unstable and then in testing, it changes the default JDK in Debian from OpenJDK11 to OpenJDK17. Thus I think the line 21 in data/java/constants should be changed from default-bytecode-version = 56 to default-bytecode-version = 61 in order to avoid warnings like --8<-- W: beast2-mcmc: incompatible-java-bytecode-format Java17 version (Class format: 61) N: N: The package contains Java class files with a minimum requirement on the N: listed Java version. This Java version is not supported by the default JVM N: in Debian and is therefore likely to be a mistake. N: N: Please refer to Bug#673276 for details. N: N: Visibility: warning N: Show-Always: no N: Check: languages/java N: --8<-- which I got with beast2-mcmc 2.7.1+dfsg-1. The package was successfully built using OpenJDK17 and is now in unstable. I also just got a similar warning with libjgraph-java, which should hit unstable within a couple of hours. Thanks for all the work on Lintian! Cheers, -- Pierre
Bug#1024038: consensuscore FTBFS: command class must subclass Command
Source: consensuscore
Version: 1.1.1+dfsg-3
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=consensuscore=amd64=1.1.1%2Bdfsg-3%2Bb3=1668361931=0
...
dh_auto_build -a -O--buildsystem=pybuild
I: pybuild base:240: /usr/bin/python3.11 setup.py build
/<>/setup.py:4: DeprecationWarning: The distutils package is
deprecated and slated for removal in Python 3.12. Use setuptools or check PEP
632 for potential alternatives
from distutils.command.build import build as _build
/<>/setup.py:6: DeprecationWarning: The distutils.sysconfig module
is deprecated, use sysconfig instead
from distutils import sysconfig
/usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning:
Distutils was imported before Setuptools, but importing Setuptools also
replaces the `distutils` module in `sys.modules`. This may lead to undesirable
behaviors or errors. To avoid these issues, avoid using distutils directly,
ensure that setuptools is installed in the traditional way (e.g. not an
editable install), and/or make sure that setuptools is always imported before
distutils.
warnings.warn(
/usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning:
Setuptools is replacing distutils.
warnings.warn("Setuptools is replacing distutils.")
WARNING: '' not a valid package name; please use only .-separated package names
in setup.py
Traceback (most recent call last):
File "/<>/setup.py", line 96, in
setup(name="ConsensusCore",
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in
setup
return distutils.core.setup(**attrs)
^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
172, in setup
ok = dist.parse_command_line()
^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
474, in parse_command_line
args = self._parse_command_opts(parser, args)
^^
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1107, in
_parse_command_opts
nargs = _Distribution._parse_command_opts(self, parser, args)
^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
540, in _parse_command_opts
raise DistutilsClassError(
distutils.errors.DistutilsClassError: command class
must subclass Command
E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1:
/usr/bin/python3.11 setup.py build
I: pybuild base:240: /usr/bin/python3 setup.py build
/<>/setup.py:4: DeprecationWarning: The distutils package is
deprecated and slated for removal in Python 3.12. Use setuptools or check PEP
632 for potential alternatives
from distutils.command.build import build as _build
/<>/setup.py:6: DeprecationWarning: The distutils.sysconfig module
is deprecated, use sysconfig instead
from distutils import sysconfig
/usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning:
Distutils was imported before Setuptools, but importing Setuptools also
replaces the `distutils` module in `sys.modules`. This may lead to undesirable
behaviors or errors. To avoid these issues, avoid using distutils directly,
ensure that setuptools is installed in the traditional way (e.g. not an
editable install), and/or make sure that setuptools is always imported before
distutils.
warnings.warn(
/usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning:
Setuptools is replacing distutils.
warnings.warn("Setuptools is replacing distutils.")
WARNING: '' not a valid package name; please use only .-separated package names
in setup.py
Traceback (most recent call last):
File "/<>/setup.py", line 96, in
setup(name="ConsensusCore",
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in
setup
return distutils.core.setup(**attrs)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
172, in setup
ok = dist.parse_command_line()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
474, in parse_command_line
args = self._parse_command_opts(parser, args)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1107, in
_parse_command_opts
nargs = _Distribution._parse_command_opts(self, parser, args)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
540, in _parse_command_opts
raise DistutilsClassError(
distutils.errors.DistutilsClassError: command class
must subclass Command
E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1:
/usr/bin/python3 setup.py build
dh_auto_build: error: pybuild --build -i python{version} -p "3.11 3.10"
returned exit code 13
make: *** [debian/rules:12: binary-arch] Error 25
Bug#1024037: pytaglib FTBFS with Python 3.11 as supported version
Source: pytaglib
Version: 1.5.0-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=pytaglib=1.5.0-2%2Bb1
...
src/taglib.cpp: In function ‘void __Pyx_AddTraceback(const char*, int, int,
const char*)’:
src/taglib.cpp:463:62: error: invalid use of incomplete type ‘PyFrameObject’
{aka ‘struct _frame’}
463 | #define __Pyx_PyFrame_SetLineNumber(frame, lineno) (frame)->f_lineno
= (lineno)
| ^~
src/taglib.cpp:6507:5: note: in expansion of macro ‘__Pyx_PyFrame_SetLineNumber’
6507 | __Pyx_PyFrame_SetLineNumber(py_frame, py_line);
| ^~~
In file included from /usr/include/python3.11/Python.h:42,
from src/taglib.cpp:23:
/usr/include/python3.11/pytypedefs.h:22:16: note: forward declaration of
‘PyFrameObject’ {aka ‘struct _frame’}
22 | typedef struct _frame PyFrameObject;
|^~
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1:
/usr/bin/python3.11 setup.py build
Bug#1020387: dictionaries-common: Consensus regarding the packaging of the Qt WebEngine hunspell binary dictionaries
El jue, 3 nov 2022 a las 23:33, Soren Stoutner () escribió: > > On Friday, October 28, 2022 4:09:45 AM MST Agustin Martin wrote: > > I am not particularly happy about this (see details below), but seems > > we will have to package all these .bdic files because qtwebengine and > > chromium use them. Since some .bdic may fail to build I would rather > > prefer them to be generated during package creation, where it is > > easier not to create them if required. If done during package install > > I think everything should be handled from qtwebengine package. In this > > case some fine tuning can be done to improve efficiency (handling > > symlinks better, regenerate only when a new version of dict package is > > installed or incompatibilities in qtwebengine hunspell appear, ...) > > I agree with you. I am also unhappy that Chromium and QtWebEngine want to use > a specialized file format instead of just using the standard Hunspell files. > However, as much as I don’t like it, I also agree with you that the best thing > Debian can do in the short term is to move forward with the packaging of these > .bdic files while we wait to see if we can make any changes upstream. > > Given that nobody else responded to this question, I think there is a > consensus that it is best to create the .bdic files during package creation. > > The next question that needs to be answered is if we should create new binary > packages for the .bdic files or if we should ship them as part of the existing > Hunspell language binary packages. The opinions that have been expressed so > far have run the gamut on both sides, but my sense is they lean a little > towards shipping them in the existing Hunspell packages so as to not add 80+ > new packages to Debian that only contain a few files each. > > Is there anyone who feels strongly that they should not be shipped in the > existing files? Hi, I am for the approach that causes as little annoyance as possible to the Debian archive, and I think that is using current packages. This way we do not bother ftpmasters with all these new packages that might be temporary. I would personally expect this to be temporary until someone with the appropiate skills provides a patch to make qtwebengine use system hunspell in Debian (as has already been done for other libs in Debian qtwebengine). I looked at the embedded hunspell code, but I am far from having those skills, so got no result. Also note that https://github.com/sheremetyev/hunspell seems to be based in a 10 years old fork of hunspell. I hope hunspell code in chromium and qtwebengine is not 10 years old and hunspell upstream has been tracked for updates (at least for security updates). I have done a quick comparison and they are not exactly the same, and not only cosmetically, but did not go further. It is to note that even that 10 years code apparently has support for the IGNORE flag, unsupported by the .bdic dicts. Fortunately, seems that there are not many dicts using that flag in libreoffice-dictionaries. libreoffice-dictionaries-7.4.2$ grep -r IGNORE * dictionaries/bo/bo.aff:IGNORE ༵༷ dictionaries/ar/ar.aff:IGNORE ًٌٍَُِّْـٰ dictionaries/uk_UA/uk_UA.aff:IGNORE ́ dictionaries/ckb/dictionaries/ckb.aff:IGNORE ًٌٍَُِّْـٰ١٢٣٤۴٥۵٦۶٧٨٩٠ dictionaries/hu_HU/hu_HU.aff:IGNORE ()]
Bug#1024036: nipy FTBFS with Python 3.11 as supported version
Source: nipy Version: 0.5.0-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=nipy=amd64=0.5.0-2%2Bb3=1668370732=0 ... Could not find datasource "nipy/templates" in data path "/usr/share/nipy:/usr/local/share/nipy:/<>/.pybuild/cpython3_3.10_nipy/.nipy"; Is it possible you have not installed a data package? You may need the package "nipy-templates" You can download and install the package from: http://nipy.org/data-packages/nipy-templates-0.2.tar.gz Check the instructions in the ``doc/users/install_data.rst`` file in the nipy source tree, or online at http://nipy.org/nipy/users/install_data.html If you have the package, have you set the path to the package correctly? Could not find datasource "nipy/data" in data path "/usr/share/nipy:/usr/local/share/nipy:/<>/.pybuild/cpython3_3.10_nipy/.nipy"; Is it possible you have not installed a data package? You may need the package "nipy-data" You can download and install the package from: http://nipy.org/data-packages/nipy-data-0.2.tar.gz Check the instructions in the ``doc/users/install_data.rst`` file in the nipy source tree, or online at http://nipy.org/nipy/users/install_data.html If you have the package, have you set the path to the package correctly? ...
Bug#1023558: dictionaries-common: installation fails with emacs23
On 2022-11-13 at 22:35 +0100, Agustin Martin wrote: > > Installing dictionaries-common with "emacs23" fails > > No problem to change that., but I am curious What errors are you > getting? emacs23 segfaults as follows. ``` # sh -x /usr/lib/emacsen-common/packages/install/dictionaries-common emacs23 ... + emacs23 --no-site-file -q -batch -l path.el -f batch-byte-compile debian-ispell.el ispell.el flyspell.el Fatal error (11)Segmentation fault ``` emacs24 and later are fine. So skipping emacs23 is enough for me. Thanks, -- Tatsuya Kinoshita pgpSWwmeW3Eyc.pgp Description: PGP signature
Bug#1023778: TMPDIR behaviour in maintainer scripts [was: Re: Bug#1023778: mysql-server-8.0: fails to restart on upgrade with libpam-tmpdir]
> "Otto" == Otto Kekäläinen writes: Otto> Instead of manually trying to manage TMPDIR env variable in Otto> various places, we should have a standardized way to run Otto> maintainer scripts in clean shell sessions that have all env Otto> variables set automatically correctly. I think trusting TMPDIR when running a maintainer script as root is fine.\ The sanitization should happen by sudo (or su or sshd) which is what gates you into root privilege. The issue with the mysql/mariadb scripts is that they are taking root's environment and applying it to the mysql user. So, those scripts need to do additional sanitization/trimming of the environment. But that comes up because those scripts are introducing a uid transition.
Bug#1024035: pycifrw FTBFS with Python 3.11 as supported version
Source: pycifrw
Version: 4.4.4-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=pycifrw=4.4.4-1%2Bb2
...
ERROR:
/<>/.pybuild/cpython3_3.11_pycifrw/build/CifFile/drel/drel_lex.py:163:
Invalid regular expression for rule 't_ELSEIF'. global flags not at the start
of the expression at position 13
...
==
ERROR: testMandatory (TestPyCIFRW.DDLmDicTestCase.testMandatory)
Test that missing mandatory items are found
--
Traceback (most recent call last):
File "/<>/TestPyCIFRW.py", line 1729, in setUp
self.refdic = CifFile.CifDic('dictionaries/ddl.dic',grammar='auto')
^
File
"/<>/.pybuild/cpython3_3.11_pycifrw/build/CifFile/CifFile_module.py",
line 363, in __init__
self.initialise_drel()
File
"/<>/.pybuild/cpython3_3.11_pycifrw/build/CifFile/CifFile_module.py",
line 1392, in initialise_drel
self.transform_drel() #parse the drel functions
^
File
"/<>/.pybuild/cpython3_3.11_pycifrw/build/CifFile/CifFile_module.py",
line 1396, in transform_drel
from .drel import drel_ast_yacc
File
"/<>/.pybuild/cpython3_3.11_pycifrw/build/CifFile/drel/drel_ast_yacc.py",
line 16, in
from .drel_lex import lexer,tokens
File
"/<>/.pybuild/cpython3_3.11_pycifrw/build/CifFile/drel/drel_lex.py",
line 226, in
lexer = lex.lex(reflags=re.MULTILINE)
^
File "/usr/lib/python3/dist-packages/ply/lex.py", line 916, in lex
raise SyntaxError("Can't build lexer")
SyntaxError: Can't build lexer
==
...
Ran 182 tests in 72.458s
FAILED (errors=34, skipped=1)
Bug#1023995: starpu-contrib: requires rebuild for freeglut transition
Hello, Sebastian Ramacher, le dim. 13 nov. 2022 18:14:54 +0100, a ecrit: > starpu-contrib requires a rebuild for the freeglut transition, but is > not auto-buildable. Please upload a rebuild. I have uploaded the rebuild. Samuel
Bug#1022311: python-stdnum: FTBFS: AssertionError: Failed doctest test for test_no_fodselsnummer.doctest
On Sun, 2022-10-23 at 14:50 +0200, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. A fix has just been uploaded and is part of version 1.18-1. If this ever needs to be backported for some reason the fix is trivial: https://arthurdejong.org/git/python-stdnum/commit/?id=1003033fa0e97726d92f47231f96cf02fb35869a -- -- arthur - art...@arthurdejong.org - https://arthurdejong.org/ -- signature.asc Description: This is a digitally signed message part
Bug#1024034: pynfft FTBFS: command class must subclass Command
Source: pynfft
Version: 1.3.2-6
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=pynfft=1.3.2-6%2Bb1
...
dh clean --with python3 --buildsystem=pybuild
dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:240: python3.11 setup.py clean
/<>/setup.py:99: DeprecationWarning: The distutils package is
deprecated and slated for removal in Python 3.12. Use setuptools or check PEP
632 for potential alternatives
from distutils.core import Command
/usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning:
Distutils was imported before Setuptools, but importing Setuptools also
replaces the `distutils` module in `sys.modules`. This may lead to undesirable
behaviors or errors. To avoid these issues, avoid using distutils directly,
ensure that setuptools is installed in the traditional way (e.g. not an
editable install), and/or make sure that setuptools is always imported before
distutils.
warnings.warn(
/usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning:
Setuptools is replacing distutils.
warnings.warn("Setuptools is replacing distutils.")
/<>/setup.py:219: DeprecationWarning: the imp module is deprecated
in favour of importlib and slated for removal in Python 3.12; see the module's
documentation for alternative uses
import imp
Traceback (most recent call last):
File "/<>/setup.py", line 314, in
setup_package()
File "/<>/setup.py", line 310, in setup_package
setup(**setup_args)
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in
setup
return distutils.core.setup(**attrs)
^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
172, in setup
ok = dist.parse_command_line()
^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
474, in parse_command_line
args = self._parse_command_opts(parser, args)
^^
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1107, in
_parse_command_opts
nargs = _Distribution._parse_command_opts(self, parser, args)
^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
540, in _parse_command_opts
raise DistutilsClassError(
distutils.errors.DistutilsClassError: command class must subclass Command
E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1:
python3.11 setup.py clean
dh_auto_clean: error: pybuild --clean -i python{version} -p "3.11 3.10"
returned exit code 13
make: *** [debian/rules:9: clean] Error 25
Bug#1023973: apt-listbugs: [INTL:nl] Dutch translation for the apt-listbugs package
On Sun, 13 Nov 2022 12:18:45 +0100 Frans Spiesschaert wrote: > Package: apt-listbugs > Severity: wishlist > Tags: l10n patch > > Dear Maintainer, Hello Frans! :-) > > > Please find attached the updated Dutch po file for the apt-listbugs > package. > A draft was posted a few weeks ago to the debian-l10n-dutch mailing list > asking for review. > Please add it to your next package revision. > It should be put as "po/nl.po" in your package build tree. Great! Thanks a lot for your contribution, which will be part of the next upload of the package. This is really appreciated. Bye. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpsDGRHDmQZX.pgp Description: PGP signature
Bug#1024033: debian-edu-config: broken thin client chroot installation in case type is (mini-)desktop and language is English
Package: debian-edu-config Version: 2.11.56+deb11u4 Severity: normal Dashamir Hoxha reported on debian-edu@lists.d.o some time ago: > When I try to create the image for a mini-desktop thin client, with the > command: > > debian-edu-ltsp-install --thin_type desktop > > I get this error message: > "E: Unable to locate package firefox-esr-l10n-en" The script tries to install firefox-esr-l10n-"$LANGCODE", with $LANGCODE grabbed from the /etc/debian-edu/config file. Since Firefox supports 'en' (and 'en-us') natively, the firefox-esr-l10n-en package doesn't exist. The issue has been fixed in Git (master branch): https://salsa.debian.org/debian-edu/debian-edu-config/-/commit/6202ef11fe4159c521b9be1cc503552543cdfc91 Since the firefox-esr-l10n-en-gb package does exist, a simple workaround for bullseye would be: Set LANGCODE="en-gb" in /etc/debian-edu/config (temporarily). Run 'debian-edu-ltsp-install --thin_type desktop' Wolfgang signature.asc Description: PGP signature
Bug#1024032: rust-criterion: FTBFS: needs to be compiled against librust-cast (>> 0.3)
Package: librust-criterion+async-futures-dev Severity: serious X-Debbugs-Cc: none, Reinhard Tartler The rust-cast crate has been updated from version 0.2 to 0.3 on 2022/11/11. Can you please build against that new version of rust-cast? -rt -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN 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
Bug#1023558: dictionaries-common: installation fails with emacs23
El dom, 6 nov 2022 a las 18:12, Tatsuya Kinoshita () escribió: > > Package: dictionaries-common > Version: 1.28.18 > Severity: wishlist > Tags: patch > > Please skip byte-compilation when emacs23. > > This bug is "wishlist", because current official GNU Emacs flavor > is only "emacs". However, I personally use unofficial flavors, > "emacs-snapshot", "emacs28", "emacs24", "emacs23", and so on. > > Installing dictionaries-common with "emacs23" fails with this bug > because of Emacs incompatibility. Hi, No problem to change that., but I am curious What errors are you getting? Depending on the underlying problem I may even skip byte-compilation for all emacs2* flavors. Regards, -- Agustin
Bug#1024029: minitube: FTBFS with mpv 0.35
Thanks for the report! The upstream bugtracker already contains a proposed fix. I will try it against mpv from experimental.
Bug#1021846: grub-install is broken since 2.06-3: error: unknown filesystem
On Sat, Nov 12, 2022 at 03:11:49PM +0300, программист некто wrote: >Hello. I rebuilt and tested grub only with patch >0087-fs-f2fs-Do-not-read-past-the-end-of-nat-journal-entr.patch >Result: error: unknown filesystem. Yay! Thanks very much for following up on this. I'll raise this with upstream. Are you happy for me to CC you on that discussion too? -- Steve McIntyre, Cambridge, UK.st...@einval.com "C++ ate my sanity" -- Jon Rabone
Bug#1024031: numba FTBFS with Python 3.11 as supported version
Source: numba Version: 0.56.2+dfsg-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=numba=0.56.2%2Bdfsg-2%2Bb1 ... dh_auto_clean -O--buildsystem=pybuild I: pybuild base:240: python3.11 setup.py clean Traceback (most recent call last): File "/<>/setup.py", line 52, in _guard_py_ver() File "/<>/setup.py", line 49, in _guard_py_ver raise RuntimeError(msg.format(cur_py, min_py, max_py)) RuntimeError: Cannot install on Python version 3.11.0; only versions >=3.7,<3.11 are supported.
Bug#944757: endless-sky: please package Endless Sky 0.9.10
Hello Zitchas, -=| Zitchas Z, 11.11.2022 14:24:57 -0700 |=- > Good day everyone, > > To start off, I have a few questions for you in regards to this. Sorry for the > quantity, I haven't been part of the process of getting a game into Debian > before, so I'm not sure on done of the terminology or what it entails. In short: I am volunteering to maintain the Debian package (plus endless-sky-high-dpi) and this doesn't require that you do anything but produce the great game you already do :) Maybe answer a copyright/license question or respond to a bug report/patch from time to time, but that should be business as usual. > 1. What do we need to do to facilitate updates to Endless Sky being > packaged and made available here? Technically, somebody with a key in the keyring needs to upload a "source package" to the Debian infrastructure. This gets built automatically on the various architectures supported by Debian and the results are made (automatically) available for download through the Debian package repositories, mirrored worldwide. Such Debian "source package" usually requires only an additional "debian/" directory along with the upstream sources. debian/ contains various metadata and instructions for building the binary packages. So far the source package was taken care of by Michael and uploaded by a couple of Debian developers. > 2. There had been mention of having someone as co-maintainer, sponsor/mentor, > and the option of having this under the group maintenance of the Debian Games > group. What would be involved in each of these options? Are these mutually > exclusive options, or complimentary? "Maintainer" would be the primary contact about the package. The person doing most of the work. Co-maintainers are other people who help and are also considered "authority" about what is done and how with regard to the packaging. "Sponsor" would be somebody with a key in the keyring who can upload the package, after a review. "Mentor" would be someone who guides the maintainer and helps them learn. Usually the mentor is also a sponsor. With the Games team option, the team would be "maintainer" with individual members who have interest in the package listed as co-maintainers. This is the option that seems natural to me, with Michael stepping down[0] from maintainer position. I am interested in the package so I'll be listed as co-maintainer. Having the team as maintainer allows other team members to help when needed. [0] https://lists.debian.org/debian-devel-games/2022/11/msg8.html > 3. What sort of long term commitment do we need of someone takes on > responsibility for handling this? Is this someone who just needs to do a > build, > test, and upload the game each update? Is there likely to be additional > editing > and adjustment required? You can see the history of the Git repository[1] in which I worked on the upgrade to 0.9.16 for the details but in short, the one big thing I had to do to was to make sure that all copyright/licensing changes are properly reflected in the debian/copyright file. By the way, I am impressed of how good this is presented upstream. Really made the job easier :) [1] https://salsa.debian.org/dmn/endless-sky > have our > GitHub repository setup to automatically build releases for MacOS, Windows, > and > an appimage. Can the Debian build feasibly be done alongside these? I guess you can make a CI produce .deb packages, but these can't be made part of the official Debian repositories, not without a real person with a key in the Debian keyring uploading the source package (after a review). > 5. Does whoever does this require any permissions beyond the publicly > available > source code and data? (There is no secret data/code, it is all > publicly > visible). Preparing the source package needs someone doing the work. Uploading to Debian requires a GPG key in the keyring. This is much more involved and requires completing the New maintainer process[2] [2] https://www.debian.org/devel/join/ Not sure if my answers settle down your questions. I am happy to try to clarify any dim points. -- Damyan signature.asc Description: PGP signature
Bug#1024027: transition: ros-class-loader
Control: tags -1 moreinfo Hi Jochen On 2022-11-13 21:51:03 +0100, Jochen Sprickerhof wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Hi release team, > > I would like to transition the new ros-class-loader. The auto generated > ben file seems fine and I've rebuild all listed packages successfully. ros2-rcpputils with a SONAME bump also prepared in experimental. Can we do those two at the same time? Cheers -- Sebastian Ramacher
Bug#1023005: A recent Bookworm upgrade broke video playback in the VLC player
Hello, I can confirm this. Same problem here. video-output is set to automatic, but changing the setting make no difference. mpv works fine, Version: 3.0.18~rc2-1+b1 -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.8 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de:nds:en_GB:en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages vlc depends on: ii vlc-bin 3.0.18~rc2-1+b1 ii vlc-plugin-base 3.0.18~rc2-1+b1 ii vlc-plugin-qt3.0.18~rc2-1+b1 ii vlc-plugin-video-output 3.0.18~rc2-1+b1 Versions of packages vlc recommends: ii vlc-l10n 3.0.18~rc2-1 ii vlc-plugin-access-extra3.0.18~rc2-1+b1 ii vlc-plugin-notify 3.0.18~rc2-1+b1 ii vlc-plugin-samba 3.0.18~rc2-1+b1 ii vlc-plugin-skins2 3.0.18~rc2-1+b1 ii vlc-plugin-video-splitter 3.0.18~rc2-1+b1 ii vlc-plugin-visualization 3.0.18~rc2-1+b1 Versions of packages vlc suggests: ii vlc-plugin-fluidsynth 3.0.18~rc2-1+b1 ii vlc-plugin-jack3.0.18~rc2-1+b1 ii vlc-plugin-pipewire3-2 ii vlc-plugin-svg 3.0.18~rc2-1+b1 Versions of packages libvlc-bin depends on: ii libc62.36-4 ii libvlc5 3.0.18~rc2-1+b1 Versions of packages libvlc5 depends on: ii libc62.36-4 ii libvlccore9 3.0.18~rc2-1+b1 Versions of packages libvlc5 recommends: ii libvlc-bin 3.0.18~rc2-1+b1 Versions of packages vlc-bin depends on: ii libc6 2.36-4 ii libvlc-bin 3.0.18~rc2-1+b1 ii libvlc5 3.0.18~rc2-1+b1 Versions of packages vlc-plugin-access-extra depends on: ii libc62.36-4 ii libsrt1.5-gnutls 1.5.1-1 ii libvlccore9 [vlc-plugin-abi-3-0-0f] 3.0.18~rc2-1+b1 ii libvncclient10.9.13+dfsg-4 ii libxcb-composite01.15-1 ii libxcb-shm0 1.15-1 ii libxcb1 1.15-1 Versions of packages vlc-plugin-base depends on: ii liba52-0.7.4 0.7.4-20 ii libarchive13 3.6.0-1 ii libaribb24-0 1.0.3-2 ii libasound2 1.2.7.2-1 ii libass9 1:0.16.0-1 ii libavahi-client3 0.8-6+b1 ii libavahi-common3 0.8-6+b1 ii libavc1394-0 0.5.4-5 ii libavcodec-extra59 [libavcodec59]7:5.1.2-1 ii libavformat597:5.1.2-1 ii libavutil57 7:5.1.2-1 ii libbluray2 1:1.3.3-1 ii libc62.36-4 ii libcairo21.16.0-6 ii libcddb2 1.3.2-7 ii libchromaprint1 1.5.1-2+b1 ii libdav1d61.0.0-2 ii libdbus-1-3 1.14.4-1 ii libdc1394-25 2.2.6-4 ii libdca0 0.0.7-2 ii libdvbpsi10 1.3.3-1 ii libdvdnav4 6.1.1-1 ii libdvdread8 6.1.3-1 ii libebml5 1.4.4-1 ii libfaad2 2.10.1-1 ii libflac121.4.2+ds-1 ii libfontconfig1 2.13.1-4.5 ii libfreetype6 2.12.1+dfsg-3 ii libfribidi0 1.0.8-2.1 ii libgcc-s112.2.0-9 ii libgcrypt20 1.10.1-2 ii libglib2.0-0 2.74.1-2 ii libgnutls30 3.7.8-4 ii libgpg-error01.45-2 ii libharfbuzz0b5.2.0-2+b1 ii libixml101:1.8.4-2 ii libjpeg62-turbo 1:2.1.2-1+b1 ii libkate1 0.4.1-11 ii liblirc-client0 0.10.1-7.1 ii liblua5.2-0 5.2.4-2 ii libmad0 0.15.1b-10.1+b1 ii libmatroska7 1.7.1-1 ii libmpcdec6 2:0.1~r495-2 ii libmpeg2-4 0.5.1-9 ii libmpg123-0 1.31.1-1 ii libmtp9 1.1.20-1 ii libncursesw6 6.3+20220423-2 ii libnfs13 4.0.0-1 ii libogg0 1.3.5-1 ii libopenmpt-modplug1 0.8.9.0-openmpt1-2+b1 ii libopus0 1.3.1-2 ii libpng16-16 1.6.38-2 ii libpostproc567:5.1.2-1 ii libprotobuf-lite23 3.12.4-1+b5 ii libpulse016.1+dfsg1-2+b1 ii
Bug#1024030: kylin-video: FTBFS with mpv 0.35
Source: kylin-video Version: 3.1.3-3 Severity: important Tags: ftbfs sid bookworm X-Debbugs-Cc: sramac...@debian.org kylin-video FTBFS with mpv 0.35.0: g++ -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++11 -Wall -Wextra -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -D_UNICODE -DQT_NO_DEBUG -DQT_X11EXTRAS_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_SQL_LIB -DQT_DBUS_LIB -DQT_CORE_LIB -I. -I/usr/include/KF5/KWindowSystem -Ilog -Isliderbar -I/usr/include/x86_64-linux-gnu/qt5/QGSettings -I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtX11Extras -I/usr/include/x86_64-linux-gnu/qt5/QtGui/5.15.6 -I/usr/include/x86_64-linux-gnu/qt5/QtGui/5.15.6/QtGui -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets -I/usr/include/x86_64-linux-gnu/qt5/QtGui -I/usr/include/x86_64-linux-gnu/qt5/QtSql -I/usr/include/x86_64-linux-gnu/qt5/QtDBus -I/usr/include/KF5/KWayland -I/usr/include/x86_64-linux-gnu/qt5/QtCore/5.15.6 -I/usr/include/x86_64-linux-gnu/qt5/QtCore/5.15.6/QtCore -I/usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc -I. -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o dbusadapter.o dbusadapter.cpp In file included from core/mpvcore.cpp:23: core/mpvcore.h:28:10: fatal error: mpv/opengl_cb.h: No such file or directory 28 | #include | ^ compilation terminated. make[3]: *** [Makefile:1325: mpvcore.o] Error 1 make[3]: *** Waiting for unfinished jobs Cheers -- Sebastian Ramacher
Bug#1023921: pykafka: diff for NMU version 2.7.0-2.1
Hi submit (2022.11.12_14:51:22_+0200) > It's delayed, because we need Python 3.11 support in snappy before it'll > build. That got rescheduled and uploaded today, so I'll reschedule this to 2-day, now. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#1024029: minitube: FTBFS with mpv 0.35
Source: minitube
Version: 3.9.3-1
Severity: important
Tags: sid bookworm ftbfs
X-Debbugs-Cc: sramac...@debian.org
minitube FTBFS with mpv 0.35.0:
g++ -c -pipe -g -ffile-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3
-std=gnu++1z -fno-rtti -fno-exceptions -Wall -Wextra -D_REENTRANT -fPIC
-DAPP_VERSION=3.9.3 -DAPP_NAME=Minitube -DAPP_UNIX_NAME=minitube -DAPP_SNAPSHOT
-DQT_NO_DEBUG_OUTPUT -DQT_USE_QSTRINGBUILDER -DQT_STRICT_ITERATORS
-DQT_DEPRECATED_WARNINGS -DHTTP -DMEDIA_MPV -DAPP_LINUX
-DDATADIR=\"/usr/share\" -DPKGDATADIR=\"/usr/share/minitube\"
-DQT_NO_DYNAMIC_CAST -DQT_NO_EXCEPTIONS -DQT_NO_DEBUG -DQT_WIDGETS_LIB
-DQT_X11EXTRAS_LIB -DQT_GUI_LIB -DQT_QML_LIB -DQT_NETWORK_LIB -DQT_SQL_LIB
-DQT_DBUS_LIB -DQT_CORE_LIB -I. -Ilib/http/src -Ilib/idle/src -Ilib/js
-Ilib/promises -Ilib/media/src -Ilib/media/src/mpv -Isrc/qtsingleapplication
-Isrc/yt -Isrc/yt/invidious -Isrc/yt/ytjs -Isrc -Ilocale
-I/usr/include/x86_64-linux-gnu/qt5
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets
-I/usr/include/x86_64-linux-gnu/qt5/QtX11Extras
-I/usr/include/x86_64-linux-gnu/qt5/QtGui
-I/usr/include/x86_64-linux-gnu/qt5/QtQml
-I/usr/include/x86_64-linux-gnu/qt5/QtNetwork
-I/usr/include/x86_64-linux-gnu/qt5/QtSql
-I/usr/include/x86_64-linux-gnu/qt5/QtDBus
-I/usr/include/x86_64-linux-gnu/qt5/QtCore -Ibuild/moc
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o
build/obj/src/yt/invidious/ivlistparser.o src/yt/invidious/ivlistparser.cpp
In file included from lib/media/src/mpv/mpvwidget.cpp:1:
lib/media/src/mpv/mpvwidget.h:12:79: warning: ‘constexpr
QFlags::QFlags(Zero) [with Enum = Qt::WindowType; Zero = int
QFlags::Private::*]’ is deprecated: Use default constructor
instead [-Wdeprecated-declarations]
12 | MpvWidget(mpv_handle *mpv, QWidget *parent = nullptr,
Qt::WindowFlags f = nullptr);
|
^~~
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:1299,
from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtCore:4,
from
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/QtWidgetsDepends:3,
from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QtWidgets:3,
from lib/media/src/mpv/mpvwidget.h:4:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qflags.h:123:80: note: declared here
123 | QT_DEPRECATED_X("Use default constructor instead") Q_DECL_CONSTEXPR
inline QFlags(Zero) noexcept : i(0) {}
|
^~
lib/media/src/mpv/mpvwidget.cpp: In member function ‘virtual void
MpvWidget::initializeGL()’:
lib/media/src/mpv/mpvwidget.cpp:33:74: error: too many initializers for
‘mpv_opengl_init_params’
33 | mpv_opengl_init_params gl_init_params{get_proc_address, this,
nullptr};
|
^
lib/media/src/mpv/mpvwidget.cpp: At global scope:
lib/media/src/mpv/mpvwidget.cpp:8:14: warning: ‘void* get_proc_address(void*,
const char*)’ defined but not used [-Wunused-function]
8 | static void *get_proc_address(void *ctx, const char *name) {
| ^~~~
make[1]: *** [Makefile:2514: build/obj/lib/media/src/mpv/mpvwidget.o] Error 1
make[1]: *** Waiting for unfinished jobs
In file included from lib/media/src/mpv/mediampv.cpp:7:
lib/media/src/mpv/mpvwidget.h:12:79: warning: ‘constexpr
QFlags::QFlags(Zero) [with Enum = Qt::WindowType; Zero = int
QFlags::Private::*]’ is deprecated: Use default constructor
instead [-Wdeprecated-declarations]
12 | MpvWidget(mpv_handle *mpv, QWidget *parent = nullptr,
Qt::WindowFlags f = nullptr);
|
^~~
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:1299,
from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtCore:4,
from lib/media/src/mpv/mediampv.h:4,
from lib/media/src/mpv/mediampv.cpp:1:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qflags.h:123:80: note: declared here
123 | QT_DEPRECATED_X("Use default constructor instead") Q_DECL_CONSTEXPR
inline QFlags(Zero) noexcept : i(0) {}
|
^~
lib/media/src/mpv/mediampv.cpp: In member function ‘virtual QWidget*
MediaMPV::videoWidget()’:
lib/media/src/mpv/mediampv.cpp:267:35: warning: ‘constexpr
QFlags::QFlags(Zero) [with Enum = Qt::WindowType; Zero = int
QFlags::Private::*]’ is deprecated: Use default constructor
instead [-Wdeprecated-declarations]
267 | widget = new MpvWidget(mpv);
| ^
/usr/include/x86_64-linux-gnu/qt5/QtCore/qflags.h:123:80: note: declared here
123 | QT_DEPRECATED_X("Use default constructor instead")
Bug#1024028: qimgv: FTBFS with mpv 0.35.0
Source: qimgv
Version: 1.0.2-1
Severity: important
Tag: ftbfs sid bookworm
X-Debbugs-Cc: sramac...@debian.org
qimgv fails to build with mpv 0.35.0:
/<>/plugins/player_mpv/src/mpvwidget.cpp: In member function
‘virtual void MpvWidget::initializeGL()’:
/<>/plugins/player_mpv/src/mpvwidget.cpp:72:77: error: too many
initializers for ‘mpv_opengl_init_params’
72 | mpv_opengl_init_params gl_init_params{get_proc_address, nullptr,
nullptr};
|
^
make[3]: *** [plugins/player_mpv/CMakeFiles/player_mpv.dir/build.make:107:
plugins/player_mpv/CMakeFiles/player_mpv.dir/src/mpvwidget.cpp.o] Error 1
Cheers
--
Sebastian Ramacher
Bug#1017711: bug#58956: mark_object, mark_objects(?) crash
Hello, On Sat 12 Nov 2022 at 02:55AM +01, Vincent Lefevre wrote: > Hi, > > On 2022-11-11 11:32:33 -0700, Sean Whitton wrote: >> On Thu 10 Nov 2022 at 11:23AM +01, Vincent Lefevre wrote: >> > On 2022-11-08 12:44:08 -0700, Sean Whitton wrote: >> >> Are you able to test the patch? Let me know if you need help getting an >> >> installable .deb. Thanks. >> > >> > Sorry, I couldn't test it yet, first because of an uninstallable >> > package needed for the build because I couldn't upgrade libc6 yet >> > and I couldn't get the previous version from snapshot.debian.org >> > (bug 1023540). Now that I could upgrade libc6, I'll be able to >> > test when I have some time, but perhaps not before the week-end. >> >> Okay, do let me know if I can help -- this is blocking Emacs from migrating. > > I've rebuilt the packages with the patch and couldn't reproduce > the bug yet. So it may be the correct fix. Many thanks for testing, and Eli and Paul for the patch. -- Sean Whitton signature.asc Description: PGP signature
Bug#1024027: transition: ros-class-loader
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hi release team, I would like to transition the new ros-class-loader. The auto generated ben file seems fine and I've rebuild all listed packages successfully. Cheers Jochen
Bug#1023887: Acknowledgement (systemd:amd64 (252-2 -> 252.1-1) brakes suspend/resume)
Bug title should be renamed to * "suspend / resume"
Bug#1024003: src:elpi: fails to migrate to testing for too long: make reverse (test) dependencies uninstallable
Le dimanche 13 novembre 2022 à 19:08 +0100, Paul Gevers a écrit : > Source: elpi > Version: 1.16.5-1 > Severity: serious > Control: close -1 1.16.7-2 > Tags: sid bookworm > User: release.debian@packages.debian.org > Usertags: out-of-sync > > Dear maintainer(s), > > The Release Team considers packages that are out-of-sync between > testing and unstable for more than 60 days as having a Release > Critical bug in testing [1]. Your package src:elpi has been trying to > migrate for 62 days [2]. Hence, I am filing this bug. I think > something went wrong with the rebuilds (or the order of them or > something), because elpi can't migrate because it would make libcoq- > elpi on armhf not installable and libcoq-elpi in unstable can't > migrate because two reverse test dependencies fail to install during > autopkgtesting on armhf. I have filed bugs to get those armhf binary packages removed last tuesday ; I expect they'll go away soon enough. I waited too long for elpi's upstream to fix the arch-issues before disabling them... sorry. Hopefully things will go smooth afterwards. Thanks, J.Puydt
Bug#1024026: libgetdata FTBFS with Python 3.11 as supported version
Source: libgetdata
Version: 0.11.0-4
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=libgetdata=amd64=0.11.0-4%2Bb2=1668369340=0
...
dh_missing -a
dh_missing: warning:
usr/local/lib/python3.11/dist-packages/pygetdata.cpython-311-x86_64-linux-gnu.so
exists in debian/tmp but is not installed to anywhere
dh_missing: error: missing files, aborting
The following debhelper tools have reported what they installed (with
files per package)
* dh_fortran_mod: libgetdata-dev (1)
* dh_install: libf95getdata7 (2), libfgetdata6 (2), libgetdata++7 (2),
libgetdata-dev (27), libgetdata-doc (191), libgetdata-perl (1),
libgetdata-tools (4), libgetdata8 (2), python3-pygetdata (1)
* dh_installdocs: libf95getdata7 (0), libfgetdata6 (0), libgetdata++7
(0), libgetdata-dev (0), libgetdata-doc (3), libgetdata-perl (0),
libgetdata-tools (0), libgetdata8 (0), python3-pygetdata (0)
* dh_installman: libf95getdata7 (0), libfgetdata6 (0), libgetdata++7
(0), libgetdata-dev (0), libgetdata-doc (0), libgetdata-perl (0),
libgetdata-tools (0), libgetdata8 (0), python3-pygetdata (0)
If the missing files are installed by another tool, please file a bug
against it.
When filing the report, if the tool is not part of debhelper itself,
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide
for debhelper (10.6.3+).
(in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary
when only a subset is built
If the omission is intentional or no other helper can take care of this
consider adding the
paths to debian/not-installed.
Remember to be careful with paths containing "x86_64-linux-gnu", where
you might need to
use a wildcard or (assuming compat 13+) e.g. ${DEB_HOST_MULTIARCH} in
debian/not-installed
to ensure it works on all architectures (see #961104).
make: *** [debian/rules:28: binary-arch] Error 25
Bug#1022527: ddupdate: diff for NMU version 0.6.6-1.2
Hi again, On Sun, 13 Nov 2022 09:47:03 +0100 Alec Leamas wrote: Thanks for taking care of this! That said, could you please delay this a little longer so I can make a regular release instead, avoiding an in my eyes somewhat painful NMU? I have committed your patch upstream in your name [1], I hope it's ok. New release is pending on mentors [2] --alec [1] https://github.com/leamas/ddupdate/commit/a480bd9e5cdae [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024025
Bug#1024025: RFS: ddupdate/0.6.6-2 [RC] -- Tool updating DNS data for dynamic IP addresses
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "ddupdate": * Package name : ddupdate Version : 0.6.6-2 Upstream contact : https://github.com/leamas/ddupdate/issues * URL : https://github.com/leamas/ddupdate * License : Expat * Vcs : https://gitlab.com/leamas/ddupdate Section : net The source builds the following binary package: ddupdate - Tool updating DNS data for dynamic IP addresses More info at https://mentors.debian.net/package/ddupdate/ or using 'dget' with this command: dget -x https://mentors.debian.net/debian/pool/main/d/ddupdate/ddupdate_0.6.6-2.dsc Changes since the last upload: ddupdate (0.6.6-2) unstable; urgency=medium . [Stefano Rivera] * New patch for bundled distutils in setuptools. Closes: #1022527 [Alec Leamas] * Move packaging to separate repo at gitlab This is a RC bugfix release on a straight-forward python package, nothing strange. On a sidenote, I would appreciate if someone who reviews and eventually uploads this package also perhaps could sponsor me so I could get package upload rights (have for some others). -- Alec Leamas
Bug#1023944: kxmlgui FTCBFS: disables designer plugin
Control: retitle -1 kxmlgui FTCBFS: disables designer plugin On Sat, Nov 12, 2022 at 09:09:36PM +0100, Helmut Grohne wrote: > kxmlgui fails to cross build from source, because building tests fails. > However, cross builds are performed with the nocheck option, so they > should not be building tests. I'm attaching a patch to disable building > tests for nocheck builds for your convenience. With this patch, it cross > builds successfully. Sorry, Wrong bug template. This is one the FTCBFS bugs where the designer plugin is not being built. The patch is correct, but the bug text is wrong. Helmut
Bug#1024024: kpty FTCBFS: does not locate utempter
Source: kpty Version: 5.98.0-1 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs kpty fails to cross build from source, because it requires specifying the location of utempter for cross builds, but the packaging doesn't do that yet. I'm attaching a patch for your convenience. I am slightly wondering though whether utempter could provide a pkg-config file containing its location. Do you think that would be useful? Helmut diff --minimal -Nru kpty-5.98.0/debian/changelog kpty-5.98.0/debian/changelog --- kpty-5.98.0/debian/changelog2022-09-18 23:11:43.0 +0200 +++ kpty-5.98.0/debian/changelog2022-11-13 04:58:07.0 +0100 @@ -1,3 +1,10 @@ +kpty (5.98.0-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Specify location of utempter. (Closes: #-1) + + -- Helmut Grohne Sun, 13 Nov 2022 04:58:07 +0100 + kpty (5.98.0-1) unstable; urgency=medium [ Aurélien COUDERC ] diff --minimal -Nru kpty-5.98.0/debian/rules kpty-5.98.0/debian/rules --- kpty-5.98.0/debian/rules2022-07-28 00:29:51.0 +0200 +++ kpty-5.98.0/debian/rules2022-11-13 04:58:06.0 +0100 @@ -2,12 +2,18 @@ # -*- makefile -*- export DEB_BUILD_MAINT_OPTIONS = hardening=+all +include /usr/share/dpkg/architecture.mk + +cmake_extra_args := +ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH)) +cmake_extra_args += -DUTEMPTER_EXECUTABLE=/usr/lib/$(DEB_HOST_MULTIARCH)/utempter/utempter +endif %: dh $@ --with kf5,pkgkde_symbolshelper --buildsystem kf5 --without build_stamp override_dh_auto_configure: - dh_auto_configure -- -DBUILD_QCH=ON + dh_auto_configure -- -DBUILD_QCH=ON $(cmake_extra_args) override_dh_auto_test: # Disable dh_auto_test at build time
Bug#1024023: mark libkf5codecs-dev Multi-Arch: same
Package: libkf5codecs-dev
Version: 5.98.0-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
Control: affects -1 + src:kcmutils
kcmutils currently fails to cross build from source. In order to fix
that, it'll have to gain native build dependencies that cause
libkf5codecs-dev to be required for both build architecture and host
architecture simultaneously. Thus, this package needs to become
Multi-Arch: same. This is also reported by the multiarch hinter, which
makes it a relatively safe thing to do. I'm attaching a patch for your
convenience.
Helmut
diff --minimal -Nru kcodecs-5.98.0/debian/changelog
kcodecs-5.98.0/debian/changelog
--- kcodecs-5.98.0/debian/changelog 2022-09-18 23:11:34.0 +0200
+++ kcodecs-5.98.0/debian/changelog 2022-11-13 04:23:36.0 +0100
@@ -1,3 +1,10 @@
+kcodecs (5.98.0-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Mark libkf5codecs-dev Multi-Arch: same. (Closes: #-1)
+
+ -- Helmut Grohne Sun, 13 Nov 2022 04:23:36 +0100
+
kcodecs (5.98.0-1) unstable; urgency=medium
[ Aurélien COUDERC ]
diff --minimal -Nru kcodecs-5.98.0/debian/control kcodecs-5.98.0/debian/control
--- kcodecs-5.98.0/debian/control 2022-09-18 23:11:34.0 +0200
+++ kcodecs-5.98.0/debian/control 2022-11-13 04:23:34.0 +0100
@@ -32,6 +32,7 @@
Package: libkf5codecs-dev
Architecture: any
+Multi-Arch: same
Section: libdevel
Depends: libkf5codecs5 (= ${binary:Version}),
qtbase5-dev (>= 5.15.2~),
Bug#1012226: unattended-upgrades: flaky autopkgtest: kernel-patterns seems to regularly get confused
Control: tag -1 patch
On Wed, 01 Jun 2022 21:50:33 +0200 Paul Gevers wrote:
unattended-upgrades showed up in the stable-proposed queue viewer [1]
because it appears to regress with the new xz-utils. However,
inspecing other failures in other suites, I think the test doesn't
behave well in archives where there are more than one version of
src:linux available. This happens regularly in pure unstable, in
unstable-to-testing and in stable-proposed-to-stable testing.
Can you please have a look? Because the unstable-to-testing migration
software now blocks on regressions in testing, flaky tests, i.e. tests
that flip between passing and failing without changes to the list of
installed packages, are causing people unrelated to your package to
spend time on these tests.
Don't hesitate to reach out if you need help and some more information
from our infrastructure.
Looking at the error messages I think this is due to bug 983363 which
isn't related to qemu, but the fact that the regexp for the running
kernel in the test isn't closed, so it also matches the -dbg and
-unsigned package with the same name.
Attached is a patch that fixes that part of the issue. I must confess
that I don't fully grasp why this isn't always a problem (e.g. now on
arm64/stable), but on my current bookworm amd64 system the test fails
without this patch and passes with the patch.
Paul
From 6301dc299b6167db00881f9d1cb3b80adf28ad13 Mon Sep 17 00:00:00 2001
From: Paul Gevers
Date: Sun, 13 Nov 2022 20:19:12 +0100
Subject: [PATCH] test: don't confuse -dbg and -unsigned with current running
kernel
Closes: #983363, #1012226
---
test/autopkgtest_kernel_patterns.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/test/autopkgtest_kernel_patterns.py b/test/autopkgtest_kernel_patterns.py
index 111c72d..f0ce3c5 100755
--- a/test/autopkgtest_kernel_patterns.py
+++ b/test/autopkgtest_kernel_patterns.py
@@ -18,7 +18,7 @@ class TestKernelPatterns(unittest.TestCase):
running_regexp = running_kernel_pkgs_regexp()
running_kernel_version = subprocess.check_output(
["uname", "-r"], universal_newlines=True).rstrip()
-running_escaped_regexp = ".*" + re.escape(running_kernel_version)
+running_escaped_regexp = ".*" + re.escape(running_kernel_version) + '$'
try:
running_noflavor_regexp = "linux.*-" + re.escape(
re.match("[1-9][0-9]*\\.[0-9]+\\.[0-9]+-[0-9]+",
--
2.35.1
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1024016: mysql-8.0: CVE-2022-39400 CVE-2022-39402 CVE-2022-39403 CVE-2022-39408 CVE-2022-39410 CVE-2022-21594 CVE-2022-21599 CVE-2022-21604 CVE-2022-21608 CVE-2022-21611 CVE-2022-21617 CVE-2022-21
On Sun, Nov 13, 2022 at 08:31:24PM +0100, Moritz Mühlenhoff wrote: > The following vulnerabilities were published for mysql-8.0. FTR, an update to 8.0.31 to fix these is already prepared and being tested at https://salsa.debian.org/mariadb-team/mysql/-/merge_requests/65 signature.asc Description: PGP signature
Bug#1024021: netatalk: CVE-2022-45188
Source: netatalk X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for netatalk. CVE-2022-45188[0]: | Netatalk through 3.1.13 has an afp_getappl heap-based buffer overflow | resulting in code execution via a crafted .appl file. This provides | remote root access on some platforms such as FreeBSD (used for | TrueNAS). https://rushbnt.github.io/bug%20analysis/netatalk-0day/ If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-45188 https://www.cve.org/CVERecord?id=CVE-2022-45188 Please adjust the affected versions in the BTS as needed.
Bug#1024022: qemu: CVE-2022-3872
Source: qemu X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for qemu. CVE-2022-3872[0]: | An off-by-one read/write issue was found in the SDHCI device of QEMU. | It occurs when reading/writing the Buffer Data Port Register in | sdhci_read_dataport and sdhci_write_dataport, respectively, if | data_count == block_size. A malicious guest could use this flaw to | crash the QEMU process on the host, resulting in a denial of service | condition. https://bugzilla.redhat.com/show_bug.cgi?id=2140567 https://lists.nongnu.org/archive/html/qemu-devel/2022-11/msg01068.html https://lists.nongnu.org/archive/html/qemu-devel/2022-11/msg01161.html If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-3872 https://www.cve.org/CVERecord?id=CVE-2022-3872 Please adjust the affected versions in the BTS as needed.
Bug#1024020: net-snmp: CVE-2022-44792 CVE-2022-44793
Source: net-snmp X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerabilities were published for net-snmp. CVE-2022-44792[0]: | handle_ipDefaultTTL in agent/mibgroup/ip-mib/ip_scalars.c in Net-SNMP | 5.8 through 5.9.3 has a NULL Pointer Exception bug that can be used by | a remote attacker (who has write access) to cause the instance to | crash via a crafted UDP packet, resulting in Denial of Service. https://github.com/net-snmp/net-snmp/issues/474 https://gist.github.com/menglong2234/b7bc13ae1a144f47cc3c95a7ea062428 CVE-2022-44793[1]: | handle_ipv6IpForwarding in agent/mibgroup/ip-mib/ip_scalars.c in Net- | SNMP 5.4.3 through 5.9.3 has a NULL Pointer Exception bug that can be | used by a remote attacker to cause the instance to crash via a crafted | UDP packet, resulting in Denial of Service. https://github.com/net-snmp/net-snmp/issues/475 https://gist.github.com/menglong2234/d07a65b5028145c9f4e1d1db8c4c202f If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-44792 https://www.cve.org/CVERecord?id=CVE-2022-44792 [1] https://security-tracker.debian.org/tracker/CVE-2022-44793 https://www.cve.org/CVERecord?id=CVE-2022-44793 Please adjust the affected versions in the BTS as needed.
Bug#1024019: iminuit FTBFS with Python 3.11 as supported version
Source: iminuit
Version: 2.11.2-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=iminuit=2.11.2-2%2Bb2
...
In file included from
/<>/extern/pybind11/include/pybind11/cast.h:16,
from
/<>/extern/pybind11/include/pybind11/attr.h:13,
from
/<>/extern/pybind11/include/pybind11/pybind11.h:13,
from /<>/src/application.cpp:3:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h: In
function ‘std::string pybind11::detail::error_string()’:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h:482:26:
error: invalid use of incomplete type ‘PyFrameObject’ {aka ‘struct _frame’}
482 | frame = frame->f_back;
| ^~
In file included from /usr/include/python3.11/Python.h:42,
from
/<>/extern/pybind11/include/pybind11/detail/common.h:209,
from
/<>/extern/pybind11/include/pybind11/pytypes.h:12,
from
/<>/extern/pybind11/include/pybind11/cast.h:13:
/usr/include/python3.11/pytypedefs.h:22:16: note: forward declaration of
‘PyFrameObject’ {aka ‘struct _frame’}
22 | typedef struct _frame PyFrameObject;
|^~
In file included from
/<>/extern/pybind11/include/pybind11/cast.h:16,
from
/<>/extern/pybind11/include/pybind11/attr.h:13,
from
/<>/extern/pybind11/include/pybind11/pybind11.h:13,
from
/<>/extern/pybind11/include/pybind11/numpy.h:12,
from /<>/src/type_caster.hpp:2,
from /<>/src/fcn.cpp:2:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h: In
function ‘std::string pybind11::detail::error_string()’:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h:482:26:
error: invalid use of incomplete type ‘PyFrameObject’ {aka ‘struct _frame’}
482 | frame = frame->f_back;
| ^~
In file included from /usr/include/python3.11/Python.h:42,
from
/<>/extern/pybind11/include/pybind11/detail/common.h:209,
from
/<>/extern/pybind11/include/pybind11/pytypes.h:12,
from /<>/src/fcn.hpp:2,
from /<>/src/fcn.cpp:1:
/usr/include/python3.11/pytypedefs.h:22:16: note: forward declaration of
‘PyFrameObject’ {aka ‘struct _frame’}
22 | typedef struct _frame PyFrameObject;
|^~
In file included from
/<>/extern/pybind11/include/pybind11/cast.h:16,
from
/<>/extern/pybind11/include/pybind11/attr.h:13,
from
/<>/extern/pybind11/include/pybind11/pybind11.h:13,
from /<>/src/contours.cpp:5:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h: In
function ‘std::string pybind11::detail::error_string()’:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h:482:26:
error: invalid use of incomplete type ‘PyFrameObject’ {aka ‘struct _frame’}
482 | frame = frame->f_back;
| ^~
In file included from /usr/include/python3.11/Python.h:42,
from
/<>/extern/pybind11/include/pybind11/detail/common.h:209,
from
/<>/extern/pybind11/include/pybind11/pytypes.h:12,
from
/<>/extern/pybind11/include/pybind11/cast.h:13:
/usr/include/python3.11/pytypedefs.h:22:16: note: forward declaration of
‘PyFrameObject’ {aka ‘struct _frame’}
22 | typedef struct _frame PyFrameObject;
|^~
In file included from
/<>/extern/pybind11/include/pybind11/cast.h:16,
from
/<>/extern/pybind11/include/pybind11/attr.h:13,
from
/<>/extern/pybind11/include/pybind11/pybind11.h:13,
from
/<>/extern/pybind11/include/pybind11/operators.h:12,
from /<>/src/functionminimum.cpp:9:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h: In
function ‘std::string pybind11::detail::error_string()’:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h:482:26:
error: invalid use of incomplete type ‘PyFrameObject’ {aka ‘struct _frame’}
482 | frame = frame->f_back;
| ^~
In file included from /usr/include/python3.11/Python.h:42,
from
/<>/extern/pybind11/include/pybind11/detail/common.h:209,
from
/<>/extern/pybind11/include/pybind11/pytypes.h:12,
from /<>/src/fcn.hpp:2,
from /<>/src/functionminimum.cpp:2:
/usr/include/python3.11/pytypedefs.h:22:16: note: forward declaration of
‘PyFrameObject’ {aka ‘struct _frame’}
22 | typedef struct _frame PyFrameObject;
|^~
gmake[4]: *** [CMakeFiles/_core.dir/build.make:79:
CMakeFiles/_core.dir/src/application.cpp.o] Error 1
gmake[4]: *** Waiting for unfinished jobs
gmake[4]: *** [CMakeFiles/_core.dir/build.make:93:
CMakeFiles/_core.dir/src/contours.cpp.o] Error 1
gmake[4]: ***
Bug#1024018: python-cleo: CVE-2022-42966
Source: python-cleo X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for python-cleo. CVE-2022-42966[0]: | An exponential ReDoS (Regular Expression Denial of Service) can be | triggered in the cleo PyPI package, when an attacker is able to supply | arbitrary input to the Table.set_rows method https://research.jfrog.com/vulnerabilities/cleo-redos-xray-257186/ This doesn't seem to have been reported upstream yet, can you please take care of that?` If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-42966 https://www.cve.org/CVERecord?id=CVE-2022-42966 Please adjust the affected versions in the BTS as needed.
Bug#1024017: pymatgen: CVE-2022-42964
Source: pymatgen X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for pymatgen. CVE-2022-42964[0]: | An exponential ReDoS (Regular Expression Denial of Service) can be | triggered in the pymatgen PyPI package, when an attacker is able to | supply arbitrary input to the GaussianInput.from_string method https://research.jfrog.com/vulnerabilities/pymatgen-redos-xray-257184/ This doesn't seem to have been reported upstream yet, can you please take care of that? If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-42964 https://www.cve.org/CVERecord?id=CVE-2022-42964 Please adjust the affected versions in the BTS as needed.
Bug#988776: Bug#983357: Netinst crashes xen domU when loading kernel
On Tue, 24 Aug 2021 15:27:19 -0400 Phillip Susi wrote: > This seems to be the heart of the problem: libinput was designed > assuming that all keyboards can and must report what keys are actually > present, and then libinput tries to cram that information into the > modalias rather than some other sysfs attribute as it should ( or not at > all... I still don't see how this information is actually supposed to be > useful to userspace ). > Firefox in guest will crash trying to handle the “joystick“ with this enormous number of keys, that does not actually respond as a joystick.
Bug#1024016: mysql-8.0: CVE-2022-39400 CVE-2022-39402 CVE-2022-39403 CVE-2022-39408 CVE-2022-39410 CVE-2022-21594 CVE-2022-21599 CVE-2022-21604 CVE-2022-21608 CVE-2022-21611 CVE-2022-21617 CVE-2022-21
Source: mysql-8.0 X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for mysql-8.0. CVE-2022-39400[0]: | Vulnerability in the MySQL Server product of Oracle MySQL (component: | Server: Optimizer). Supported versions that are affected are 8.0.30 | and prior. Easily exploitable vulnerability allows high privileged | attacker with network access via multiple protocols to compromise | MySQL Server. Successful attacks of this vulnerability can result in | unauthorized ability to cause a hang or frequently repeatable crash | (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability | impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2022-39402[1]: | Vulnerability in the MySQL Shell product of Oracle MySQL (component: | Shell: Core Client). Supported versions that are affected are 8.0.30 | and prior. Easily exploitable vulnerability allows unauthenticated | attacker with logon to the infrastructure where MySQL Shell executes | to compromise MySQL Shell. While the vulnerability is in MySQL Shell, | attacks may significantly impact additional products (scope change). | Successful attacks of this vulnerability can result in unauthorized | read access to a subset of MySQL Shell accessible data. CVSS 3.1 Base | Score 4.3 (Confidentiality impacts). CVSS Vector: | (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N). CVE-2022-39403[2]: | Vulnerability in the MySQL Shell product of Oracle MySQL (component: | Shell: Core Client). Supported versions that are affected are 8.0.30 | and prior. Easily exploitable vulnerability allows low privileged | attacker with logon to the infrastructure where MySQL Shell executes | to compromise MySQL Shell. Successful attacks require human | interaction from a person other than the attacker. Successful attacks | of this vulnerability can result in unauthorized update, insert or | delete access to some of MySQL Shell accessible data as well as | unauthorized read access to a subset of MySQL Shell accessible data. | CVSS 3.1 Base Score 3.9 (Confidentiality and Integrity impacts). CVSS | Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N). CVE-2022-39408[3]: | Vulnerability in the MySQL Server product of Oracle MySQL (component: | Server: Optimizer). Supported versions that are affected are 8.0.30 | and prior. Easily exploitable vulnerability allows low privileged | attacker with network access via multiple protocols to compromise | MySQL Server. Successful attacks of this vulnerability can result in | unauthorized ability to cause a hang or frequently repeatable crash | (complete DOS) of MySQL Server. CVSS 3.1 Base Score 6.5 (Availability | impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). CVE-2022-39410[4]: | Vulnerability in the MySQL Server product of Oracle MySQL (component: | Server: Optimizer). Supported versions that are affected are 8.0.30 | and prior. Easily exploitable vulnerability allows low privileged | attacker with network access via multiple protocols to compromise | MySQL Server. Successful attacks of this vulnerability can result in | unauthorized ability to cause a hang or frequently repeatable crash | (complete DOS) of MySQL Server. CVSS 3.1 Base Score 6.5 (Availability | impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). CVE-2022-21594[5]: | Vulnerability in the MySQL Server product of Oracle MySQL (component: | Server: Optimizer). Supported versions that are affected are 8.0.30 | and prior. Easily exploitable vulnerability allows high privileged | attacker with network access via multiple protocols to compromise | MySQL Server. Successful attacks of this vulnerability can result in | unauthorized ability to cause a hang or frequently repeatable crash | (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability | impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2022-21599[6]: | Vulnerability in the MySQL Server product of Oracle MySQL (component: | Server: Stored Procedure). Supported versions that are affected are | 8.0.30 and prior. Easily exploitable vulnerability allows high | privileged attacker with network access via multiple protocols to | compromise MySQL Server. Successful attacks of this vulnerability can | result in unauthorized ability to cause a hang or frequently | repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score | 4.9 (Availability impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2022-21604[7]: | Vulnerability in the MySQL Server product of Oracle MySQL (component: | InnoDB). Supported versions that are affected are 8.0.30 and prior. | Easily exploitable vulnerability allows high privileged attacker with | network access via multiple protocols to compromise MySQL Server. | Successful attacks of this vulnerability can result in unauthorized | ability to cause a hang or frequently repeatable crash (complete DOS) |
Bug#1024015: python-gevent FTBFS with Python 3.11 as supported version
Source: python-gevent Version: 21.12.0-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=python-gevent=21.12.0-3%2Bb1 ... In file included from src/gevent/_greenlet_primitives.c:764: /<>/deps/greenlet/greenlet.h:42:5: error: unknown type name ‘CFrame’ 42 | CFrame* cframe; | ^~ error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1 E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1: /usr/bin/python3.11 setup.py build
Bug#1024014: RM: gatling -- RoQA; Obsolete, unmaintained, unused
Package: ftp.debian.org Severity: normal Please remove gatling, the last maintainer upload was in 2016, the version currently in the archive is way behind current upstream releases, popcon is virtually non-existent and there's plenty of other httpds in the archive. Cheers, Moritz
Bug#1023865: docker.io: docker build breaks breaks host network
Control: reassign -1 connman
Control: tags - moreinfo unreproducible
The problem is fixed by removing connman. connman seem to wrongly assign
IP address to bridge port interface (e.g. veth??), and this causes
problem in host network.
This issue is similar to [0].
[0] https://unix.stackexchange.com/q/648084/11640
--
ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790 8793 CC65 B0CD EC27 5D5B
signature.asc
Description: PGP signature
Bug#1022994: Bug#1023778: TMPDIR behaviour in maintainer scripts [was: Re: Bug#1023778: mysql-server-8.0: fails to restart on upgrade with libpam-tmpdir]
On Sun, Nov 13, 2022 at 05:46:00PM +0100, Marco d'Itri wrote: > On Nov 13, Robie Basak wrote: > > > This seems inconsistent to me. Where is the expectation that TMPDIR must > > be unset if dropping privileges coming from? Obviously for users of > Where is the expectation that $TMPDIR is writable by any user but the > current one? > I do not believe that it is expected that if a user creates a directory > and points $TMPDIR to it then they also have to make it sticky, so this > has nothing to do with libpam-tmpdir. I understand the traditional semantics of TMPDIR to be exactly the same as /tmp. So that includes the sticky bit, or at least behaviour that is equivalent under all circumstances. Or, alternatively, that someone who sets TMPDIR without setting the sticky bit is certain that it will be used in a way that does not rely on that. libpam-tmpdir breaks those semantics in a way that breaks in edge cases like the situation raised in this (and other) bug reports. So on the contrary, I think it has everything to do with libpam-tmpdir, and anything else that sets TMPDIR to something that doesn't match the traditional semantics. To be clear, if it's better that we change the semantics to improve the system as a whole, then I don't have a particular objection to that. But I'd prefer that it be done deliberately, with consensus across all developers, and be well-defined and documented. Rather than have a change of semantics exist in a multitude of individual fixes for individual bug reports that potentially end up solving the issue differently, inconsistently or incompletely, and without regard for the bigger picture (eg. if the conclusion is that it should be done somewhere other than maintainer scripts or in common tooling). There's also the risk that we swap one problem for another - for example if there are use cases which rely on maintainer scripts honouring TMPDIR, including when they drop privileges. signature.asc Description: PGP signature
Bug#1021045: gdm3: gdm-fingerprint fails if fprintd is installed but libpam-fprint is not
Control: reassign -1 fprintd Hello, On Sun, Nov 13, 2022 at 03:00:26PM +, Simon McVittie wrote: > On Fri, 30 Sep 2022 at 21:37:20 -0700, Ross Vandegrift wrote: > > If fprintd and gdm3 are installed, but libpam-fprintd is not installed, then > > users with enrolled fingerprints cannot login. > ... > > Installing libpam-fprintd fixes the issue. Perhaps it should be in > > Recommends > > instead of Suggests? > > I'm not sure about this as a solution. I don't think it would be true > to say that installations of gdm3 that don't need (libpam-)fprintd > are unusual, which is the level of dependency where Recommends are > necessary. Most gdm3 users log in with a password and don't use a > fingerprint reader. Yea, fair enough. I've posted an issue to gdm upstream gitlab with a request for better UX in this case. FingerForce team - Would you consider adding libpam-fprintd to fprintd's Recommends? After installing fprintd and enrolling a fingerprint, I couldn't login with gdm even though the option was presented. Strictly, it might be excessive (enlightenment could use fprintd without libpam-fprintd for unlock). But there's an awkward usability issue now since nothing pulls it in automatically. If not, I can add it to enlightenment (along with fprintd). But it seems non-optimal to require this on every WM/desktop env package. Thanks, Ross
Bug#1024013: frozenlist FTBFS with Python 3.11 as supported version
Source: frozenlist Version: 1.2.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=frozenlist=amd64=1.2.0-1%2Bb3=1668362318=0 ... x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.11 -c frozenlist/_frozenlist.c -o build/temp.linux-x86_64-cpython-311/frozenlist/_frozenlist.o frozenlist/_frozenlist.c:198:12: fatal error: longintrepr.h: No such file or directory 198 | #include "longintrepr.h" |^~~ compilation terminated. error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1 E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1: /usr/bin/python3.11 setup.py build
Bug#1024012: r-cran-xts: autopkgtest regression on i386
Source: r-cran-xts
Version: 0.12.2-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
https://ci.debian.net/data/autopkgtest/testing/i386/r/r-cran-xts/28179801/log.gz
The following objects are masked from 'package:base':
as.Date, as.Date.numeric
Error in make.index.unique.xts(x, eps = eps) :
(converted from warning) index value is unique but will be replaced; it is
less than the cumulative epsilon for the preceding duplicate index values
In addition: Warning messages:
1: In make.index.unique.xts(x, eps = 1e-06) :
index value is unique but will be replaced; it is less than the cumulative
epsilon for the preceding duplicate index values
2: In make.index.unique.xts(x, eps = eps) :
index value is unique but will be replaced; it is less than the cumulative
epsilon for the preceding duplicate index values
Error in try.xts(sample.data.frame[, 1]) :
Error in as.xts.double(x, ..., .RECLASS = TRUE) : order.by must be either
'names()' or otherwise specified
Error in diff.xts(x, 1L, -1L) :
'diff.xts' defined only for positive lag and differences arguments
Error in diff.xts(x, 1L, "a") : 'differences' must be integer
In addition: Warning message:
In diff.xts(x, 1L, "a") : NAs introduced by coercion
Error in diff.xts(x, -1L, 1L) :
'diff.xts' defined only for positive lag and differences arguments
Error in diff.xts(x, "a", 1L) : 'lag' must be integer
In addition: Warning message:
In diff.xts(x, "a", 1L) : NAs introduced by coercion
Error in endpoints(x, on = "years", k = 0) : 'k' must be > 0
Error in endpoints(x, on = "years", k = -1) : 'k' must be > 0
Error in endpoints(x, on = "quarters", k = 0) : 'k' must be > 0
Error in endpoints(x, on = "quarters", k = -1) : 'k' must be > 0
Error in endpoints(x, on = "months", k = 0) : 'k' must be > 0
Error in endpoints(x, on = "months", k = -1) : 'k' must be > 0
Error in endpoints(x, on = "weeks", k = 0) : 'k' must be > 0
Error in endpoints(x, on = "weeks", k = -1) : 'k' must be > 0
Error in endpoints(x, on = "days", k = 0) : 'k' must be > 0
Error in endpoints(x, on = "days", k = -1) : 'k' must be > 0
Error in endpoints(x, on = "hours", k = 0) : 'k' must be > 0
Error in endpoints(x, on = "hours", k = -1) : 'k' must be > 0
Error in endpoints(x, on = "minutes", k = 0) : 'k' must be > 0
Error in endpoints(x, on = "minutes", k = -1) : 'k' must be > 0
Error in endpoints(x, on = "seconds", k = 0) : 'k' must be > 0
Error in endpoints(x, on = "seconds", k = -1) : 'k' must be > 0
Error in endpoints(x, on = "ms", k = 0) : 'k' must be > 0
Error in endpoints(x, on = "ms", k = -1) : 'k' must be > 0
Error in endpoints(x, on = "us", k = 0) : 'k' must be > 0
Error in endpoints(x, on = "us", k = -1) : 'k' must be > 0
Error in `tclass<-.xts`(x, value) : improperly specified value for tclass
In addition: There were 50 or more warnings (use warnings() to see the first 50)
Error in `tclass<-.xts`(x, value) : unsupported 'tclass' indexing type:
In addition: Warning message:
'indexClass<-' is deprecated.
Use 'tclass<-' instead.
See help("Deprecated") and help("xts-deprecated").
Error in `tclass<-.xts`(x, value) : improperly specified value for tclass
In addition: Warning message:
'indexClass<-' is deprecated.
Use 'tclass<-' instead.
See help("Deprecated") and help("xts-deprecated").
Error in eval(expr, envir = parent.frame()) : object 'Date' not found
In addition: Warning message:
In rm(Date) : object 'Date' not found
Error in h(simpleError(msg, call)) :
error in evaluating the argument 'i' in selecting a method for function '[':
'match' requires vector arguments
In addition: Warning message:
'indexClass<-' is deprecated.
Use 'tclass<-' instead.
See help("Deprecated") and help("xts-deprecated").
Registered S3 method overwritten by 'quantmod':
methodfrom
as.zoo.data.frame zoo
Error in periodicity(x) :
(converted from warning) can not calculate periodicity of 1 observation
In addition: There were 14 warnings (use warnings() to see them)
Error in periodicity(x) :
(converted from warning) can not calculate periodicity of empty object
In addition: Warning message:
In periodicity(x) : can not calculate periodicity of empty object
Timing stopped at: 0.013 0 0.014
Error in checkIdentical(nm_target, nm_ms, msg) : FALSE
microsecond data split by milliseconds
Error : Supply time-of-day subsetting in the format of T%H:%M:%OS/T%H:%M:%OS
Error : Supply time-of-day subsetting in the format of T%H:%M:%OS/T%H:%M:%OS
Error : (converted from warning) 'indexClass' is deprecated.
Use 'tclass' instead.
See help("Deprecated") and help("xts-deprecated").
In addition: Warning message:
In .parseISO8601(ii, .index(x)[1], .index(x)[nr], tz = tz) :
cannot determine first and last time from 2012-02-30/2012-02-30
Error : (converted from warning) 'indexClass<-' is deprecated.
Use 'tclass<-' instead.
See help("Deprecated") and help("xts-deprecated").
Error : (converted from warning) 'indexFormat' is deprecated.
Use 'tformat' instead.
See help("Deprecated") and
Bug#1024011: gtksourceview4: autopkgtest regression
Source: gtksourceview4 Version: 4.8.4-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org https://ci.debian.net/data/autopkgtest/testing/amd64/g/gtksourceview4/27967119/log.gz # Start of file-loader tests # GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? (/usr/libexec/installed-tests/gtksourceview-4/test-file-loader:6343): GLib-GIO-DEBUG: 15:17:49.746: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? ok 1 /file-loader/end-line-stripping ok 2 /file-loader/end-new-line-detection ok 3 /file-loader/begin-new-line-detection # End of file-loader tests PASS: gtksourceview-4/test-file-loader.test Running test: gtksourceview-4/test-language-specs.test ** GtkSourceView:ERROR:../testsuite/test-language-specs.c:47:main: 'srcdir' should not be NULL Bail out! GtkSourceView:ERROR:../testsuite/test-language-specs.c:47:main: 'srcdir' should not be NULL FAIL: gtksourceview-4/test-language-specs.test (Child process killed by signal 6) SUMMARY: total=23; passed=3; skipped=0; failed=20; user=0.9s; system=0.4s; maxrss=70476 FAIL: gtksourceview-4/test-completion-words.test (Child process killed by signal 5) FAIL: gtksourceview-4/test-mark.test (Child process killed by signal 5) FAIL: gtksourceview-4/test-printcompositor.test (Child process killed by signal 5) FAIL: gtksourceview-4/test-regex.test (Child process killed by signal 5) FAIL: gtksourceview-4/test-languagemanager.test (Child process killed by signal 5) FAIL: gtksourceview-4/test-iter.test (Child process killed by signal 5) FAIL: gtksourceview-4/test-completion-model.test (Child process killed by signal 5) FAIL: gtksourceview-4/test-buffer.test (Child process killed by signal 5) FAIL: gtksourceview-4/test-file-saver.test (Child process killed by signal 5) FAIL: gtksourceview-4/test-stylescheme.test (Child process killed by signal 5) FAIL: gtksourceview-4/test-region.test (Child process killed by signal 5) FAIL: gtksourceview-4/test-styleschememanager.test (Child process killed by signal 5) FAIL: gtksourceview-4/test-space-drawer.test (Child process killed by signal 5) FAIL: gtksourceview-4/test-encoding.test (Child process killed by signal 5) FAIL: gtksourceview-4/test-search-context.test (Child process killed by signal 5) FAIL: gtksourceview-4/test-view.test (Child process killed by signal 5) FAIL: gtksourceview-4/test-undo-manager.test (Child process killed by signal 5) FAIL: gtksourceview-4/test-utils.test (Child process killed by signal 5) FAIL: gtksourceview-4/test-language.test (Child process killed by signal 5) FAIL: gtksourceview-4/test-language-specs.test (Child process killed by signal 6) autopkgtest [15:17:50]: test installed-tests: ---] autopkgtest [15:17:50]: test installed-tests: - - - - - - - - - - results - - - - - - - - - - installed-tests FAIL non-zero exit status 2 autopkgtest [15:17:50]: summary installed-tests FAIL non-zero exit status 2 Cheers -- Sebastian Ramacher
Bug#1024010: compreffor FTBFS with Python 3.11 as supported version
Source: compreffor Version: 0.5.1-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=compreffor=0.5.1-2%2Bb2 ... src/cython/_compreffor.cpp:196:12: fatal error: longintrepr.h: No such file or directory 196 | #include "longintrepr.h" |^~~ compilation terminated. error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1 E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1: /usr/bin/python3.11 setup.py build
Bug#1024009: rust-wasmer-enumset - should this package be removed
Package: rust-wasmer-enumset rust-wasmer-enumset and it's support crate rust-wasmer-enumset-derive are a fork of the enumset/enumset-derive crates to fix a specific issue. The issue has now been fixed in the enumset crates and the wasmer-enumset crates are unmaintained The only reverse-dependency in Debian was cursive-core which was patched to use wasmer-enumset, I have now (after discussion with it's maintainer on IRC) switched that over to using enumset. So there doesn't seem any reason to keep wasmer-enumset around.
Bug#1024008: python3-spyder is not installable
Package: python3-spyder Version: 5.3.3+dfsg-3 Severity: serious The following packages have unmet dependencies: python3-spyder : Depends: python3-pylsp (< 1.6~) but 1.6.0-1 is to be installed Depends: python3-qtconsole (< 5.4~) but 5.4.0-1 is to be installed
Bug#1024007: haskell98-report: reproducible builds: timestamp embedded in .ps files
Source: haskell98-report Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The build time was embedded in several .ps files: https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope-results/haskell98-report.html /usr/share/doc/haskell98-report/ffi.ps.gz %DVIPSSource:··TeX·output·2023.12.08:1504 vs. %DVIPSSource:··TeX·output·2022.11.06:1057 The attached patch to debian/rules fixes this by setting the FORCE_SOURCE_DATE environment variable, which ensures that texlive respects SOURCE_DATE_EPOCH to set the timestamp. According to my local tests, with this patch applied, haskell98-report should build reproducibly on tests.reproducible-builds.org! Thanks for maintaining haskell98-report! live well, vagrant From c5f0a7284e26e38663fb9862d976fb10a9949fd1 Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Sun, 13 Nov 2022 18:18:44 + Subject: [PATCH] debian/rules: Set FORCE_SOURCE_DATE for reproducible builds. https://tests.reproducible-builds.org/debian/issues/unstable/timestamps_in_ps_generated_by_dvips_issue.html --- debian/rules | 4 1 file changed, 4 insertions(+) diff --git a/debian/rules b/debian/rules index a1c1a5c..0744c4e 100755 --- a/debian/rules +++ b/debian/rules @@ -1,4 +1,8 @@ #!/usr/bin/make -f + +# Ensure texlive respects SOURCE_DATE_EPOCH for reproducible builds +export FORCE_SOURCE_DATE=1 + %: dh $@ -- 2.38.1 signature.asc Description: PGP signature
Bug#1024006: bugs.debian.org: Waking up from sleep causes laptop to irrecoverably freeze
Package: bugs.debian.org Severity: normal X-Debbugs-Cc: yellradi...@hotmail.com Dear Maintainer, Basically the title. Whenever I put my laptop to sleep and then try to wake it up by pressing a key or the power off button, the laptop freezes beyond any recourse but to force-shut it down by holding the power button down. As the following thread suggests (https://forum.manjaro.org/t/suspend-problems-with-lpss-on-alder-lake-cpu/98107), adding the "noapic" kernel parameter does indeed enable the laptop to resume from sleep successfully, alas, it renders all input devices, including the keyboard, non-functional, and is thus a non-solution. Appreciate your help in solving this extremely frustrating problem.
Bug#1024005: RM: llvm-toolchain-snapshot -- ROM; uploaded incorrectly to unstable
Package: ftp.debian.org Severity: normal Hello Sorry, I uploaded by mistake to unstable. it is supposed to stay in experimental https://apt.llvm.org/ also provides backports. Sylvestre
Bug#1024004: src:vectorscan: fails to migrate to testing for too long: autopkgtest regression on ppc64el
Source: vectorscan Version: 5.4.7-1 Severity: serious Control: close -1 5.4.8-2 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1021079 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:vectorscan has been trying to migrate for 61 days [2]. Hence, I am filing this bug. The package in unstable regressed its autopkgtest on ppc64el which I reported in bug 1021079. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=vectorscan OpenPGP_signature Description: OpenPGP digital signature
Bug#1024003: src:elpi: fails to migrate to testing for too long: make reverse (test) dependencies uninstallable
Source: elpi Version: 1.16.5-1 Severity: serious Control: close -1 1.16.7-2 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:elpi has been trying to migrate for 62 days [2]. Hence, I am filing this bug. I think something went wrong with the rebuilds (or the order of them or something), because elpi can't migrate because it would make libcoq-elpi on armhf not installable and libcoq-elpi in unstable can't migrate because two reverse test dependencies fail to install during autopkgtesting on armhf. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=elpi OpenPGP_signature Description: OpenPGP digital signature
Bug#1024002: ruby-nokogiri: FTBFS on s390x
Source: ruby-nokogiri Version: 1.13.8+dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=ruby-nokogiri=s390x=1.13.8%2Bdfsg-1=1665929973=0 Nokogiri::HTML4::Document#test_parse_works_with_an_object_that_responds_to_read :239: [BUG] Couldn't unprotect page 0x03ff905b4000, errno: Cannot allocate memory ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [s390x-linux-gnu] -- Control frame information --- c:0027 p:0003 s:0143 e:000142 METHOD :239 c:0026 p:0134 s:0139 e:000138 METHOD /<>/test/helper.rb:124 c:0025 p:0005 s:0135 e:000134 BLOCK /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:103 c:0024 p:0002 s:0132 e:000131 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:195 c:0023 p:0004 s:0127 e:000126 BLOCK /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:102 [FINISH] c:0022 p: s:0123 e:000122 CFUNC :each c:0021 p:0017 s:0119 e:000118 BLOCK /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:101 c:0020 p:0015 s:0116 e:000115 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:281 c:0019 p:0004 s:0111 e:000110 BLOCK /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:94 c:0018 p:0029 s:0108 e:000107 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:376 c:0017 p:0044 s:0100 E:001108 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:221 c:0016 p:0004 s:0093 E:000eb0 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:93 c:0015 p:0058 s:0089 e:88 METHOD /usr/lib/ruby/vendor_ruby/minitest/reporters.rb:44 c:0014 p:0008 s:0082 e:81 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:1042 c:0013 p:0026 s:0075 e:73 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:350 :239: [BUG] Segmentation fault at 0x03ff905ba000 ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [s390x-linux-gnu] -- Control frame information --- c:0027 p:0003 s:0143 e:000142 METHOD :239 c:0026 p:0134 s:0139 e:000138 METHOD /<>/test/helper.rb:124 c:0025 p:0005 s:0135 e:000134 BLOCK /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:103 c:0024 p:0002 s:0132 e:000131 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:195 c:0023 p:0004 s:0127 e:000126 BLOCK /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:102 [FINISH] c:0022 p: s:0123 e:000122 CFUNC :each c:0021 p:0017 s:0119 e:000118 BLOCK /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:101 c:0020 p:0015 s:0116 e:000115 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:281 c:0019 p:0004 s:0111 e:000110 BLOCK /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:94 c:0018 p:0029 s:0108 e:000107 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:376 c:0017 p:0044 s:0100 E:001108 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:221 c:0016 p:0004 s:0093 E:000eb0 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:93 c:0015 p:0058 s:0089 e:88 METHOD /usr/lib/ruby/vendor_ruby/minitest/reporters.rb:44 c:0014 p:0008 s:0082 e:81 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:1042 c:0013 p:0026 s:0075 e:73 METHOD /usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:350 Segmentation fault rake aborted! Command failed with status (139): [ruby -w -I"test" /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb "test/css/test_css.rb" "test/css/test_css_integration.rb" "test/css/test_parser.rb" "test/css/test_tokenizer.rb" "test/css/test_xpath_visitor.rb" "test/decorators/test_slop.rb" "test/html4/sax/test_parser.rb" "test/html4/sax/test_parser_context.rb" "test/html4/sax/test_parser_text.rb" "test/html4/sax/test_push_parser.rb" "test/html4/test_attributes.rb" "test/html4/test_attributes_properly_escaped.rb" "test/html4/test_builder.rb" "test/html4/test_comments.rb" "test/html4/test_document.rb" "test/html4/test_document_encoding.rb" "test/html4/test_document_fragment.rb" "test/html4/test_element_description.rb" "test/html4/test_html_module.rb" "test/html4/test_named_characters.rb" "test/html4/test_node.rb" "test/html4/test_node_encoding.rb" "test/html5/test_api.rb" "test/html5/test_encoding.rb" "test/html5/test_monkey_patch.rb" "test/html5/test_nokogumbo.rb" "test/html5/test_null.rb" "test/html5/test_serialize.rb" "test/html5/test_tree-construction.rb" "test/namespaces/test_additional_namespaces_in_builder_doc.rb" "test/namespaces/test_namespaces_aliased_default.rb" "test/namespaces/test_namespaces_in_builder_doc.rb" "test/namespaces/test_namespaces_in_cloned_doc.rb"
Bug#1016716: regression in Xfce
Let's tackle this mess bit by bit because I feel like there's at least a dozen problems mixed and minced together. > Distro: MX-21.1_x64 Wildflower You submitted this bug report to the Debian BTS (bug tracking system) while running MX Linux. Even though it claims to be using the Debian archive (thus, Debian-based), it may come with completely different configs on top of the base system. They have their own bug tracker: https://bugs.mxlinux.org/ > I had installed zoom and it was working fine then in June I found out when I > go to share screen I lose audio and sometimes got message driver not > available. Zoom is not available in the Debian archive (and will never be since it's a proprietary software). You should contact their support: https://support.zoom.us/hc/en-us/search#q=linux=All=relevancy > I followed the direction on Linux mint website to localize problem. What direction? Which website? Again, Linux Mint is a completely different distribution with its own community. > I was able to repeat problem on different machine. What machine? Windows? Mac? Vague. > When changed desktop problem went away. >From what to what? Where did the problem go? > I tried Budgie, Mate and a friend tried Cinnamon they all work. None of these names start with 'X', end in 'e' and have 'fc' in the middle. What constitutes work here? > I think it was a security update. Security updates seldom introduce new features or touch the existing ones. Even if one did so, we still have point 2: Zoom is not available in the Debian repos. > It also showed up in the MX usb witer if opened from file manager it loses > the iso you want to write. What is it that also showed up? MX usb witer or whatever that is doesn't exist in Debian. Which file manager? > These both showed up at the the same time. Who or what are both? Where did they show up? > This one is a small problem that is nothing more than annoyance but it might > point to the cause of the bigger problem. Sounds ominous. I wouldn't call it small, though. > the technical details are below Mostly irrelevant. Here's your prize for reaching this far: https://forum.mxlinux.org/
Bug#1024001: flatpak should Recommend: xdg-desktop-portal-gtk (without alternative)
Package: flatpak Version: 1.14.0-2 Severity: normal Dear Maintainer, GTK3 and/or GTK4 applications running inside flatpak on a Wayland host need the xdg-desktop-portal-gtk package to be installed or else font rendering will look terrible (see https://github.com/flatpak/flatpak/issues/2861). So the flatpak package should Recommend: xdg-desktop-portal-gtk. Right now it recommends 'xdg-desktop-portal-gtk | xdg-desktop-portal-packend', which in my case is satisfied by xdk-desktop-portal-kde, but that is not enough to get proper font rendering. Kind regards, Ralf -- Package-specific info: Permissions of /usr/bin/bwrap: -rwxr-xr-x 1 root root 72080 Nov 7 18:57 /usr/bin/bwrap /etc/sysctl.d/*-bubblewrap.conf: cat: '/etc/sysctl.d/*-bubblewrap.conf': No such file or directory /usr/lib/sysctl.d/50-bubblewrap.conf: # Enable unprivileged creation of new user namespaces in older Debian # kernels. # # If this is not desired, copy this file to # /etc/sysctl.d/50-bubblewrap.conf and change the value of this parameter # to 0, then use dpkg-statoverride to make /usr/bin/bwrap setuid root. # # For more details see https://deb.li/bubblewrap or # /usr/share/doc/bubblewrap/README.Debian kernel.unprivileged_userns_clone=1 /proc/sys/kernel/unprivileged_userns_clone: 1 /proc/sys/user/max_cgroup_namespaces: 127534 /proc/sys/user/max_ipc_namespaces: 127534 /proc/sys/user/max_mnt_namespaces: 127534 /proc/sys/user/max_net_namespaces: 127534 /proc/sys/user/max_pid_namespaces: 127534 /proc/sys/user/max_time_namespaces: 127534 /proc/sys/user/max_user_namespaces: 127534 /proc/sys/user/max_uts_namespaces: 127534 -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-3-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER 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 flatpak depends on: ii adduser 3.129 ii bubblewrap 0.7.0-1 ii dbus [default-dbus-system-bus] 1.14.4-1 ii fuse3 3.12.0-1 ii libappstream4 0.15.5-1 ii libarchive133.6.0-1 ii libc6 2.36-4 ii libcurl3-gnutls 7.86.0-1 ii libdconf1 0.40.0-3 ii libfuse3-3 3.12.0-1 ii libgdk-pixbuf-2.0-0 2.42.9+dfsg-1 ii libglib2.0-02.74.1-2 ii libgpgme11 1.18.0-1 ii libjson-glib-1.0-0 1.6.6-1 ii libmalcontent-0-0 0.11.0-3 ii libostree-1-1 2022.6-1+b1 ii libpolkit-agent-1-0 122-1 ii libpolkit-gobject-1-0 122-1 ii libseccomp2 2.5.4-1+b2 ii libsystemd0 252.1-1 ii libxau6 1:1.0.9-1 ii libxml2 2.9.14+dfsg-1+b1 ii libzstd11.5.2+dfsg-1 ii xdg-dbus-proxy 0.1.4-1 Versions of packages flatpak recommends: ii ca-certificates 20211016 ii desktop-file-utils 0.26-1 ii gtk-update-icon-cache3.24.34-3 ii hicolor-icon-theme 0.17-2 ii libpam-systemd 252.1-1 ii p11-kit 0.24.1-1 ii policykit-1 122-1 ii polkitd 122-1 ii shared-mime-info 2.2-1 ii xdg-desktop-portal 1.15.0-2+b1 ii xdg-desktop-portal-gtk [xdg-desktop-portal-backend] 1.14.0-1 ii xdg-desktop-portal-kde [xdg-desktop-portal-backend] 5.26.0-1 ii xdg-user-dirs0.18-1 Versions of packages flatpak suggests: ii avahi-daemon0.8-6+b1 pn malcontent-gui Versions of packages bubblewrap depends on: ii libc62.36-4 ii libcap2 1:2.44-1 ii libselinux1 3.4-1+b3 Versions of packages bubblewrap recommends: ii procps 2:3.3.17-7.1 -- no debconf information
Bug#998223: Contributors for Mailman 3 in Debian / your RFH
> Mailman3 has been part of buster and bullseye, but the release of sqlalchemy > 1.4 is not compatible with it and therefore there is a chance that it will > not make it in bookworm. There is nothing that any contributor can do except > taking the time to help mailman upstream to be fixed and work with sqlalchemy > 1.4. Upstream released a version which is compatible with sqlalchemy 1.4 and which should also fix all other blocking problems in the mailman3 problems. See bug #1023976 for things I am assuming are fixed by it.
Bug#1024000: pink-pony: FTBFS: OSError: 'pkg-config IlmBase --cflags --libs' exited 1
Source: pink-pony
Version: 1.4.1-3
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
scons: Reading SConscript files ...
Package IlmBase was not found in the pkg-config search path.
Perhaps you should add the directory containing `IlmBase.pc'
to the PKG_CONFIG_PATH environment variable
Package 'IlmBase', required by 'virtual:world', not found
OSError: 'pkg-config IlmBase --cflags --libs' exited 1:
File "/<>/SConstruct.Debian", line 10:
env.ParseConfig("pkg-config IlmBase --cflags --libs")
File "/usr/lib/python3/dist-packages/SCons/Environment.py", line 1674:
return function(self, self.backtick(command), unique)
File "/usr/lib/python3/dist-packages/SCons/Environment.py", line 597:
raise OSError("'%s' exited %d" % (command, status))
make: *** [debian/rules:37: build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Cheers
--
Sebastian Ramacher
Bug#1023877: apt-listbugs: [INTL:ru] Russian translation update
On Sat, 12 Nov 2022 01:17:21 +0300 Алексей Шилин wrote: > Package: apt-listbugs > Version: 0.1.37 > Severity: wishlist > Tags: l10n patch > > Hi, Hello Алексей! :-) > > Updated apt-listbugs translation into Russian is attached. Thank you so much for your contribution! The updated file will be included in the next upload of the package. This is greatly appreciated. Bye! -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpq1ASHT3YCz.pgp Description: PGP signature
Bug#1021262: failing test disabled in 0.2.21-2
Hi, I disabled the failing test on all arches except amd64 on 0.2.21-2, until the issue is fixed upstream. Since the package now builds, and other tests are passing, I am changing the severity of the bug to 'normal'. Thanks, Cédric signature.asc Description: signature
Bug#1022994: Bug#1023778: TMPDIR behaviour in maintainer scripts [was: Re: Bug#1023778: mysql-server-8.0: fails to restart on upgrade with libpam-tmpdir]
On Nov 13, Robie Basak wrote: > This seems inconsistent to me. Where is the expectation that TMPDIR must > be unset if dropping privileges coming from? Obviously for users of Where is the expectation that $TMPDIR is writable by any user but the current one? I do not believe that it is expected that if a user creates a directory and points $TMPDIR to it then they also have to make it sticky, so this has nothing to do with libpam-tmpdir. -- ciao, Marco signature.asc Description: PGP signature
Bug#1023999: stormbaancoureur: build-depends on missing: plib1.8.4-dev
Source: stormbaancoureur Version: 2.1.6-3 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/package.php?p=stormbaancoureur stormbaancoureur build-depends on missing: - plib1.8.4-dev:amd64 Cheers -- Sebastian Ramacher
Bug#1023998: openuniverse: build-depends on missing: plib1.8.4-dev
Source: openuniverse Version: 1.0beta3.1+dfsg-7 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/package.php?p=openuniverse openuniverse build-depends on missing: - plib1.8.4-dev:armel Cheers -- Sebastian Ramacher
