Bug#1030096: dask.distributed intermittent autopkgtest fail
On 09/02/2023 06:36, Diane Trout wrote: Also there's still some flaky tests as the rebuild triggered by my just committing the changelog release had a failure in "test_release_retry" I don't think I've seen that particular one before, though like several others it's a warning being treated as an error because dask.distributed now does that (in setup.cfg). debci doesn't appear to have run yet. (If it does and fails, note that there's a retry button next to failure reports. Given how tight we are on time (we need to be in testing by the 12th), I'd rather not re-upload (restarting the migration clock) if we don't have to.) Also, we need to close this bug (by email _not_ by uploading).
Bug#1030918: RM: googleearth-package -- RoM; uninstallable, no upload since 2014
Package: ftp.debian.org Severity: normal Usertags: rm-request User: ftp.debian@packages.debian.org Usertags: remove Hi, Please proceed to deleting the package: googleearth-package This one is RoM because I emailed the author and the reply is: > [...] Yes, please feel free to remove googleearth-package and feel free to remove me from lxcfs. > As I don't have time to maintain these packages anymore and consider myself "ex-maintainer" for some time now. Informations: - Last activity of the maintainer on Debian: 2016-04-03 - Last upload: 2014-10-04, 9 years ago. -- William Desportes
Bug#1030785: -ffile-prefix-map option and reproducibility
Hi! I'm end up with following thing: https://github.com/rockdrilla/debian-container/blob/808dfa15d130f833602a1486362cc551593a0d8a/image/python/template/rules#L543 Hovewer, "execute_before_dh_builddeb" recipe is for information only (to be viewed by human) and "execute_before_dh_install" recipe is for actual adjustments. ср, 8 февр. 2023 г. в 13:39, Guillem Jover : > > On Tue, 2023-02-07 at 20:00:06 +0100, Sven Joachim wrote: > > On 2023-02-07 17:50 +0100, Guillem Jover wrote: > > > On Tue, 2023-02-07 at 16:41:47 +0100, Stéphane Glondu wrote: > > >> I suspect this was added to improve reproducibility. Ironically, it makes > > >> packages that capture this variable non reproducible, since the build > > >> path > > >> seems to be randomized (has it always been the case? since when?). It is > > >> the > > >> case of OCaml (see #1030785), and seemingly of R as well (found by > > >> grepping > > >> in my /etc). I wouldn't be surprised other packages are affected as well. > > > > > > AFAIR this was considered at the time, yes. If the flag is effectively > > > not fixing anything for the set of packages involved, and is in fact > > > actually making them unreproducible when they would not then, you can > > > disable the fixfilepath feature in the reproducible build flags area, > > > via DEB_BUILD_MAINT_OPTIONS. > > > > This does not help for packages which capture all build flags and store > > them in some file in the package (as is the case here). With > > DEB_BUILD_MAINT_OPTIONS=reproducible=-fixfilepath, dpkg-buildflags falls > > back to "-fdebug-prefix-map==.", and you have the same > > problem. If you disable that as well via > > DEB_BUILD_MAINT_OPTIONS=reproducible=-fixfilepath,-fixdebugpath, the > > -dbgsym packages will most likely end up unreproducible. > > Ah, you are absolutely right. I don't think the case of these flags > making the build unreproducible and the package not generating any > debug objects are going to be common at all. I considered mentioning > fixing the build to stop capturing, but felt it might be more effort > than requested. :) Should probably have mentioned anyway, as was done > elsewhere in the thread. > > In any case I'm thinking to add something like the attached to the man > page to try to clarify this. > > Thanks, > Guillem -- SY, Konstantin Demin
Bug#1030096: dask.distributed intermittent autopkgtest fail
On Wed, 2023-02-08 at 23:11 +, Rebecca N. Palmer wrote: > > Mostly, please upload *something* today, because we won't know for > sure > whether it passes on a real buildd/debci until we try that, and if it > doesn't then the sooner we find out the better. > It's uploaded it earlier today dask.distributed is past buildd, but I haven't seen dask.distributed on ci.debian.org yet. Also there's still some flaky tests as the rebuild triggered by my just committing the changelog release had a failure in "test_release_retry" Diane
Bug#1030917: systemsettings: kcm_users creates new users with shell set to /usr/sbin/nologin
Package: systemsettings Version: 4:5.26.90-1 Severity: normal X-Debbugs-Cc: fores...@sonic.net Dear Maintainer, When creating a new user in the KDE Plasma System Settings: Users panel, the new user's shell is set to /usr/sbin/nologin in /etc/passwd. I believe it should be /bin/bash or some other usable default. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-3-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemsettings depends on: ii kio 5.102.0-1 ii kpackagetool5 5.102.0-1 ii libc6 2.36-8 ii libkf5activities5 5.102.0-1 ii libkf5auth5 5.102.0-1 ii libkf5authcore5 5.102.0-1 ii libkf5completion5 5.102.0-1 ii libkf5configcore5 5.102.0-1 ii libkf5configgui55.102.0-1 ii libkf5configwidgets55.102.0-1 ii libkf5coreaddons5 5.102.0-1 ii libkf5crash55.102.0-1 ii libkf5dbusaddons5 5.102.0-1 ii libkf5i18n5 5.102.0-1 ii libkf5iconthemes5 5.102.0-1 ii libkf5itemmodels5 5.102.0-1 ii libkf5itemviews55.102.0-1 ii libkf5kcmutils5 5.102.0-1 ii libkf5kiocore5 5.102.0-1 ii libkf5kiogui5 5.102.0-1 ii libkf5kiowidgets5 5.102.0-1 ii libkf5kirigami2-5 5.102.0-1 ii libkf5notifications55.102.0-1 ii libkf5package5 5.102.0-1 ii libkf5runner5 5.102.0-1 ii libkf5service-bin 5.102.0-1 ii libkf5service5 5.102.0-1 ii libkf5widgetsaddons55.102.0-1 ii libkf5windowsystem5 5.102.0-1 ii libkf5xmlgui5 5.102.0-1 ii libkworkspace5-54:5.26.90-1 ii libqt5core5a5.15.8+dfsg-2 ii libqt5gui5 5.15.8+dfsg-2 ii libqt5qml5 5.15.8+dfsg-2 ii libqt5quick55.15.8+dfsg-2 ii libqt5quickwidgets5 5.15.8+dfsg-2 ii libqt5widgets5 5.15.8+dfsg-2 ii libstdc++6 12.2.0-14 ii qml-module-org-kde-kcm 5.102.0-1 ii qml-module-org-kde-kcmutils 5.102.0-1 ii qml-module-org-kde-kirigami25.102.0-1 ii qml-module-org-kde-kitemmodels 5.102.0-1 ii qml-module-org-kde-newstuff 5.102.0-1 ii qml-module-qtquick-controls 5.15.8-2 ii qml-module-qtquick-layouts 5.15.8+dfsg-2 ii qml-module-qtquick-shapes 5.15.8+dfsg-2 ii qml-module-qtquick2 5.15.8+dfsg-2 systemsettings recommends no packages. systemsettings suggests no packages. -- no debconf information
Bug#1030096: dask.distributed intermittent autopkgtest fail
Am Wed, Feb 08, 2023 at 11:11:49PM + schrieb Rebecca N. Palmer: > Mostly, please upload *something* today, because we won't know for sure > whether it passes on a real buildd/debci until we try that, and if it > doesn't then the sooner we find out the better. +1 Thanks to you both for all your work Andreas. -- http://fam-tille.de
Bug#1030915: rust-sequoia-keyring-linter: FTBFS with new rust-rpassword.
Package: rust-sequoia-keyring-linter Version: 1.0.0-1 Severity: serious rust-rpassword was recently updated to version 6.x, but sequoia-keyring-linter still depends on version 5.x. I have checked crates.io and upstream git, and there does not appear to be an upstream patch available. on bumping the dependency it fails to build with. error[E0425]: cannot find function `read_password_from_tty` in crate `rpassword` --> src/keyring-linter.rs:57:38 | 57 | match rpassword::read_password_from_tty( | ^^ help: a function with a similar name exists: `read_password_from_bufread` sequoia-sq fixed a similar issue by replacing read_password_from_tty with prompt_password, as can be seen at https://gitlab.com/sequoia-pgp/sequoia/-/commit/7936e3513ee339650a7ac2eff11edd2fac3f037d but I am not in a position to determine if this is also appropriate for sequoia-keyring-linter.
Bug#1030524: iwd segfaults in 2.2-1 no armhf on Rasperry Pi
Hello Jonas, > A new release 2.3-1 has just been released. It would be helpful if you > could test whether the problem has been fixed. I can confirm that the Debian package 2.3-1 works without segfault (have it running for > 10 hours without a problem). Thanks for the quick packaging! > Upstream changes do not mention any RPi or ARM-related issues > specifically, but mentions an off-by-one error which perhaps could lead > to segfaults on your system. If I had to guess, I would think that it was an ABI mismatch resulting from a missing versioned dependency/conflict in one of the related packages and somehow related to being a 32-bit ARM system, which is probably not that common in combination with iwd (and amd64 got a binary-only update, which armhf did not get). If that should be true, the issue could reappear in the future. Nevertheless, I suggest to close this bug and do a more detailed analysis only if the issue really reappears in the future. Kind regards Patrick signature.asc Description: This is a digitally signed message part.
Bug#1030914: firmware-brcm80211 causes system to freeze and reboot
Package: firmware-brcm80211 Version: 20221214-5 Severity: important X-Debbugs-Cc: mathi...@hotmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? My system has the following network card 02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43225 802.11b/g/n [14e4:4357] (rev 01) If i install the firmware for this card (firmware-brcm80211), the system freezes and reboots by itself. * What exactly did you do (or not do) that was effective (or ineffective)? install the firmware with the command "sudo nala install firmware-brcm80211" This causes the system to freeze and reboot. I could not even collect any logs. When the system boots up, "dmesg" is clean. There are no errors. Please let me know if there is somewhere else i should be looking for logs, errors and useful info to troubleshoot this issue. * What was the outcome of this action? Installing the firmware gets the network card to work. But in a short while (1 min approx) the system freezes and reboots. * What outcome did you expect instead? I expect the system to funtion normally and not freeze/reboot *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-3-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_CRAP 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 firmware-brcm80211 depends on no packages. firmware-brcm80211 recommends no packages. Versions of packages firmware-brcm80211 suggests: ii initramfs-tools 0.142
Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))
Some crashes in the signal handler are the just created "MDEV-30613 output_core_info crashes in my_read()" with a probable cause. Doesn't help the original crash reason however. A single thread backtrace isn't sufficient on errors like: " InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch" With MTR_PRINT_CORE=detailed in the environment will do multiple threads and be more likely to identify deadlocks between processes (or if the builder is just very slow at this point). Disabling performance schema -DPLUGIN_PERFSCHEMA=NO on s390x might be a way to get some breathing space on this optional feature to resolve later as the unmap crashes seem firmly in this feature's shutdown.
Bug#1030846: e2fsprogs: generates filesystems that grub-install doesn't recognize
On Wed, Feb 08, 2023 at 09:12:05PM +, Steve McIntyre wrote: > > I've just queued these up in our repo for the next grub upload, due in > a few days. Many thanks, Steve! - Ted
Bug#1030913: verilator: FTBFS on hppa - #error "Missing VL_CPU_RELAX() definition."
Source: verilator
Version: 5.006-2
Severity: normal
Tags: ftbfs patch
Dear Maintainer,
Build fails with following error:
g++ -g -O2 -ffile-prefix-map=/<>=. -Wformat
-Werror=format-security -g -O2 -ffile-prefix-map=/<>=. -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time
-D_FORTIFY_SOURCE=2 -Og -ggdb -gz -DVL_DEBUG -D_GLIBCXX_DEBUG -MMD -I. -I..
-I.. -I../../include -I../../include -MP -faligned-new -Wno-unused-parameter
-Wno-shadow -DDEFENV_SYSTEMC=\"\" -DDEFENV_SYSTEMC_ARCH=\"\"
-DDEFENV_SYSTEMC_INCLUDE=\"\" -DDEFENV_SYSTEMC_LIBDIR=\"\"
-DDEFENV_VERILATOR_ROOT=\"/usr/share/verilator\" -c ../VlcMain.cpp -o VlcMain.o
In file included from ../config_build.h:91,
from ../VlcMain.cpp:18:
../../include/verilatedos.h:537:3: error: #error "Missing VL_CPU_RELAX()
definition."
537 | # error "Missing VL_CPU_RELAX() definition."
| ^
Full log is here:
https://buildd.debian.org/status/fetch.php?pkg=verilator=hppa=5.006-2=1675879005=0
Attached patch fixes build on hppa:
https://buildd.debian.org/status/fetch.php?pkg=verilator=hppa=5.006-2=1675904676=0
Regards,
Dave Anglin
-- System Information:
Debian Release: bookworm/sid
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)
Kernel: Linux 6.1.10+ (SMP w/4 CPU threads)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Index: verilator-5.006/include/verilatedos.h
===
--- verilator-5.006.orig/include/verilatedos.h
+++ verilator-5.006/include/verilatedos.h
@@ -519,6 +519,8 @@ using ssize_t = uint32_t; ///< signed s
# define VL_CPU_RELAX() asm volatile("nop" ::: "memory");
#elif defined(__aarch64__) || defined(__arm__)
# define VL_CPU_RELAX() asm volatile("yield" ::: "memory")
+#elif defined(__hppa__) // HPPA does not currently have yield/pause
+# define VL_CPU_RELAX() asm volatile("nop" ::: "memory")
#elif defined(__loongarch__) // LoongArch does not currently have yield/pause
# define VL_CPU_RELAX() asm volatile("nop" ::: "memory")
#elif defined(__mips64el__) || defined(__mips__) || defined(__mips64__) ||
defined(__mips64)
Bug#1030912: kaffeine: Attempting to call Channel Menu by 'C' command, segfaulted
Package: kaffeine Version: 2.0.18-1+b1 Severity: normal X-Debbugs-Cc: marathon.duran...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? After installing Debian KDE. It was working fine previously in Gnome (Bookworm too) * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? Kaffeine crashed. * What outcome did you expect instead? To see my channel list *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.10-1-liquorix-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages kaffeine depends on: ii iso-codes4.12.0-1 ii kinit5.102.0-1 ii kio 5.102.0-1 ii libc62.36-8 ii libdvbv5-0 1.22.1-5+b1 ii libkf5configcore55.102.0-1 ii libkf5configwidgets5 5.102.0-1 ii libkf5coreaddons55.102.0-1 ii libkf5dbusaddons55.102.0-1 ii libkf5i18n5 5.102.0-1 ii libkf5kiocore5 5.102.0-1 ii libkf5kiofilewidgets55.102.0-1 ii libkf5solid5 5.102.0-1 ii libkf5widgetsaddons5 5.102.0-1 ii libkf5windowsystem5 5.102.0-1 ii libkf5xmlgui55.102.0-1 ii libqt5core5a 5.15.8+dfsg-2 ii libqt5dbus5 5.15.8+dfsg-2 ii libqt5gui5 5.15.8+dfsg-2 ii libqt5sql5 5.15.8+dfsg-2 ii libqt5sql5-sqlite5.15.8+dfsg-2 ii libqt5widgets5 5.15.8+dfsg-2 ii libqt5x11extras5 5.15.8-2 ii libqt5xml5 5.15.8+dfsg-2 ii libstdc++6 12.2.0-14 ii libvlc5 3.0.18-2 ii libxss1 1:1.2.3-1 ii vlc-plugin-base 3.0.18-2 ii vlc-plugin-video-output 3.0.18-2 kaffeine recommends no packages. Versions of packages kaffeine suggests: pn libdvdcss2 -- no debconf information -- debsums errors found: debsums: missing file /usr/share/locale/ar/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/be/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/bg/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/bs/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/ca/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/ca@valencia/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/cs/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/da/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/de/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/el/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/en_GB/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/eo/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/es/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/et/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/eu/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/fi/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/fr/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/ga/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/gl/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/hr/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/hu/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/ia/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/id/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/it/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/ja/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/km/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/ko/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/ku/LC_MESSAGES/kaffeine.mo (from kaffeine package) debsums: missing file /usr/share/locale/lt/LC_MESSAGES/kaffeine.mo (from kaffeine
Bug#1030911: Repeated Unicode circles
Package: ibus-chewing Version: 1.6.1-2 Severity: minor I found that ○● ○● are actually the same unicodes repeated at 1, 2 and 5, 6: One pair is all that is needed. This is the second page of 8:特殊圖形.
Bug#1030910: ITP: libfile-findlib-perl -- find and use a file/dir from a directory above your script file
Package: wnpp Owner: Mason James Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org * Package name: libfile-findlib-perl Version : 0.001004 Upstream Author : Tye McQueen * URL : https://metacpan.org/release/File-FindLib * License : Unlicense Programming Lang: Perl Description : find and use a file/dir from a directory above your script file File::FindLib starts in the directory where your script (or library) is located and looks for the file or directory whose name you pass in. If it isn't found, then FindLib looks in the parent directory and continues moving up parent directories until it finds it or until there is not another parent directory. If it finds the named path and it is a directory, then it prepends it to @INC. That is, use File::FindLib 'lib'; is roughly equivalent to: use File::Basename qw< dirname >; use lib dirname(__FILE__) . '/../../../lib'; The package will be maintained under the umbrella of the Debian Perl Group. -- Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.
Bug#1030909: Unable to run xscreensaver-demo or xscreensaver-settings
Package: xscreensaver Version: 6.06+dfsg1-2 Severity: important Since upgrading to 6.06+dfsg1-2, I have been unable to run xscreensaver-settings or xscreensaver-demo. The main xscreensaver binary still runs and works correctly; however, I can no longer configure which screensavers show up except by editing .xscreensaver by hand. So marking this as important. Here's the typical output from xscreensaver-settings: xscreensaver-settings: 15:24:45: X error: xscreensaver-settings: Failed request: BadMatch (invalid parameter attributes) xscreensaver-settings: Major opcode: 42 (X_SetInputFocus) xscreensaver-settings: Resource id:0x187 xscreensaver-settings: Serial number: 440 / 441 Here's the output from xscreensaver-settings --debug: xscreensaver-settings: 15:25:11: DISPLAY=:0 xscreensaver-settings: 15:25:11: added "/usr/libexec/xscreensaver" to $PATH xscreensaver-settings: 15:25:11: pref changed: GtkSpinButton xscreensaver-settings: 15:25:11: pref changed: GtkSpinButton xscreensaver-settings: 15:25:11: pref changed: GtkSpinButton xscreensaver-settings: 15:25:11: pref changed: GtkSpinButton xscreensaver-settings: 15:25:11: pref changed: GtkSpinButton xscreensaver-settings: 15:25:11: pref changed: GtkSpinButton xscreensaver-settings: 15:25:11: pref changed: GtkSpinButton xscreensaver-settings: 15:25:11: pref changed: GtkCheckButton xscreensaver-settings: 15:25:11: pref changed: GtkCheckButton xscreensaver-settings: 15:25:11: pref changed: GtkCheckButton xscreensaver-settings: 15:25:11: pref changed: GtkRadioButton xscreensaver-settings: 15:25:11: pref changed: GtkRadioButton xscreensaver-settings: 15:25:11: list selection changed xscreensaver-settings: 15:25:11: scheduling preview "hextrail --root" xscreensaver-settings: 15:25:11: reading /usr/share/xscreensaver/config/hextrail.xml... xscreensaver-settings: 15:25:11: scheduling preview "hextrail --root" xscreensaver-settings: 15:25:11: reading /usr/share/xscreensaver/config/hextrail.xml... xscreensaver-settings: 15:25:11: scheduling preview "hextrail --root" xscreensaver-settings: 15:25:11: select list elt 114 xscreensaver-settings: 15:25:11: scheduling preview "hextrail --root" xscreensaver-settings: 15:25:11: reading /usr/share/xscreensaver/config/hextrail.xml... xscreensaver-settings: 15:25:11: scheduling preview "hextrail --root" xscreensaver-settings: 15:25:12: xscreensaver-gl-visual says the GL visual is 0x21. xscreensaver-settings: 15:25:12: using non-default visual 0x21 xscreensaver-settings: 15:25:12: saved screenshot 0x1800010 1920x1080 for window 0x18f 425x238+437+116 xscreensaver-settings: 15:25:12: X error: xscreensaver-settings: Failed request: BadMatch (invalid parameter attributes) xscreensaver-settings: Major opcode: 42 (X_SetInputFocus) xscreensaver-settings: Resource id:0x187 xscreensaver-settings: Serial number: 440 / 441 I found bug #1030659, which seems to be related to this issue (it also has the X_SetInputFocus error), but in my case there is no segfault so I decided to file a separate bug. Some other information that may be pertinent: - CPU: AMD Ryzen 7 5700G with Radeon Graphics - GPU: Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8) - glxinfo output: please see attached. - Desktop environment: none, using minimal XDM + ratpoison as WM. Possibly relevant packages: hi ratpoison 1.4.8-2+b1amd64keyboard-only window manager ii xdm1:1.1.11-3+b2 amd64X display manager ii xserver-common 2:21.1.6-1all common files used by various X servers ii xserver-xorg-core 2:21.1.6-1amd64Xorg X server - core server ii xserver-xorg-input-evdev 1:2.10.6-2+b1 amd64X.Org X server -- evdev input driver ii xserver-xorg-input-kbd 1:1.9.0-1+b3 amd64X.Org X server -- keyboard input driver ii xserver-xorg-input-libinput1.2.1-1+b1amd64X.Org X server -- libinput input driver ii xserver-xorg-input-mouse 1:1.9.3-1+b1 amd64X.Org X server -- mouse input driver ii xserver-xorg-video-amdgpu 22.0.0-3 amd64X.Org X server -- AMDGPU display driver T -- Recently, our IT department hired a bug-fix engineer. He used to work for Volkswagen.
Bug#1030908: mariadb: [INTL:pt_BR] Brazilian Portuguese debconf templates translation
Package: mariadb Tags: l10n patch Severity: wishlist Hello, Could you please update the Brazilian Portuguese translation? Attached you will find the file pt_BR.po. It is UTF-8 encoded and tested with msgfmt and podebconf-display-po. Kind regards. pt_BR.po.gz Description: application/gzip signature.asc Description: PGP signature
Bug#1030906: taurus-pyqtgraph: FTBFS (failing tests)
Package: src:taurus-pyqtgraph Version: 0.5.9-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in bookworm, your package failed to build: [...] debian/rules binary-indep dh binary-indep --with python3 --buildsystem=pybuild dh_update_autotools_config -i -O--buildsystem=pybuild dh_autoreconf -i -O--buildsystem=pybuild dh_auto_configure -i -O--buildsystem=pybuild I: pybuild base:240: python3.11 setup.py config running config dh_auto_build -i -O--buildsystem=pybuild I: pybuild base:240: /usr/bin/python3 setup.py build running build running build_py creating /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/datainspectortool.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/autopantool.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/buffersizetool.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/dateaxisitem.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/taurustrendset.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/plot.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/forcedreadtool.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/y2axis.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/curvesmodel.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/curveproperties.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/taurusimageitem.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/__init__.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/trend.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/curvespropertiestool.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/taurusmodelchoosertool.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/util.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/taurusplotdataitem.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/cli.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/legendtool.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph creating /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples copying taurus_pyqtgraph/examples/legendExample.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples copying taurus_pyqtgraph/examples/taurustrendset.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples copying taurus_pyqtgraph/examples/axislabels.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples copying taurus_pyqtgraph/examples/y2axis.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples copying taurus_pyqtgraph/examples/__init__.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples copying taurus_pyqtgraph/examples/taurusplotdataitem.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples running egg_info creating taurus_pyqtgraph.egg-info writing taurus_pyqtgraph.egg-info/PKG-INFO writing dependency_links to taurus_pyqtgraph.egg-info/dependency_links.txt writing entry points to taurus_pyqtgraph.egg-info/entry_points.txt writing requirements to taurus_pyqtgraph.egg-info/requires.txt writing top-level names to taurus_pyqtgraph.egg-info/top_level.txt writing manifest file 'taurus_pyqtgraph.egg-info/SOURCES.txt' reading manifest file 'taurus_pyqtgraph.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files matching '__pycache__' found under directory '*' warning: no previously-included files matching '*.py[co]' found under directory '*' warning: no files found matching '*.jpg' under directory 'docs' warning: no files found matching '*.png' under directory 'docs' warning: no files found matching '*.gif' under directory 'docs' adding license file 'LICENSE.txt' writing manifest file 'taurus_pyqtgraph.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:202: SetuptoolsDeprecationWarning: Installing 'taurus_pyqtgraph.ui' as data is deprecated, please list it in `packages`. !! # Package would be ignored
Bug#1030907: umap-learn: FTBFS (failing tests)
Package: src:umap-learn
Version: 0.4.5+dfsg-3
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules binary-indep
dh binary-indep --with python3 --buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_autoreconf -i -O--buildsystem=pybuild
dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:240: python3.11 setup.py config
running config
dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:240: /usr/bin/python3 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.11/build/umap
copying umap/spectral.py -> /<>/.pybuild/cpython3_3.11/build/umap
copying umap/sparse_nndescent.py ->
/<>/.pybuild/cpython3_3.11/build/umap
[... snipped ...]
FAILED umap/tests/test_umap_nn.py::test_sparse_nn_search - numba.core.errors
FAILED
umap/tests/test_umap_on_iris.py::test_initialized_umap_trustworthiness_on_iris
FAILED umap/tests/test_umap_on_iris.py::test_umap_trustworthiness_on_sphere_iris
FAILED umap/tests/test_umap_on_iris.py::test_umap_transform_on_iris - numba.c...
FAILED
umap/tests/test_umap_on_iris.py::test_umap_transform_on_iris_modified_dtype
FAILED umap/tests/test_umap_on_iris.py::test_umap_sparse_transform_on_iris - ...
FAILED umap/tests/test_umap_ops.py::test_blobs_cluster - numba.core.errors.Lo...
FAILED umap/tests/test_umap_ops.py::test_multi_component_layout - numba.core
FAILED umap/tests/test_umap_ops.py::test_umap_transform_embedding_stability
FAILED
umap/tests/test_umap_repeated_data.py::test_repeated_points_large_sparse_spatial
FAILED
umap/tests/test_umap_repeated_data.py::test_repeated_points_small_sparse_spatial
FAILED
umap/tests/test_umap_repeated_data.py::test_repeated_points_large_dense_spatial
FAILED
umap/tests/test_umap_repeated_data.py::test_repeated_points_small_dense_spatial
FAILED
umap/tests/test_umap_repeated_data.py::test_repeated_points_large_sparse_binary
FAILED
umap/tests/test_umap_repeated_data.py::test_repeated_points_small_sparse_binary
FAILED
umap/tests/test_umap_repeated_data.py::test_repeated_points_large_dense_binary
FAILED
umap/tests/test_umap_repeated_data.py::test_repeated_points_small_dense_binary
FAILED umap/tests/test_umap_repeated_data.py::test_repeated_points_large_n - ...
FAILED umap/tests/test_umap_trustworthiness.py::test_umap_sparse_trustworthiness
FAILED
umap/tests/test_umap_trustworthiness.py::test_umap_trustworthiness_fast_approx
FAILED
umap/tests/test_umap_trustworthiness.py::test_umap_trustworthiness_random_init
FAILED
umap/tests/test_umap_trustworthiness.py::test_supervised_umap_trustworthiness
FAILED
umap/tests/test_umap_trustworthiness.py::test_semisupervised_umap_trustworthiness
FAILED
umap/tests/test_umap_trustworthiness.py::test_metric_supervised_umap_trustworthiness
FAILED
umap/tests/test_umap_trustworthiness.py::test_string_metric_supervised_umap_trustworthiness
FAILED
umap/tests/test_umap_trustworthiness.py::test_discrete_metric_supervised_umap_trustworthiness
FAILED
umap/tests/test_umap_trustworthiness.py::test_count_metric_supervised_umap_trustworthiness
FAILED umap/tests/test_umap_validation_params.py::test_haversine_on_highd - n...
FAILED
umap/tests/test_umap_validation_params.py::test_umap_haversine_embed_to_highd
FAILED
umap/tests/test_umap_validation_params.py::test_umap_too_many_neighbors_warns
FAILED
umap/tests/test_umap_validation_params.py::test_umap_fit_data_and_targets_compliant
FAILED
umap/tests/test_umap_validation_params.py::test_umap_fit_instance_returned
ERROR umap/tests/test_umap_on_iris.py::test_umap_trustworthiness_on_iris - nu...
ERROR
umap/tests/test_umap_on_iris.py::test_umap_clusterability_on_supervised_iris
ERROR umap/tests/test_umap_on_iris.py::test_umap_inverse_transform_on_iris - ...
=== 56 failed, 66 passed, 2 xfailed, 20 warnings, 3 errors in 48.47s ===
E: pybuild pybuild:388: test: plugin custom failed with: exit code=1:
PYTHONPATH=/<>/.pybuild/cpython3_3.11/build python3.11 -m pytest
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11
--system=custom "--test-args=PYTHONPATH={build_dir} {interpreter} -m pytest"
returned exit code 13
make[1]: *** [debian/rules:16: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:12: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).
If you could not reproduce the bug please contact me privately, as I
am
Bug#1030904: libgovirt: FTBFS randomly (Could not connect to localhost: Connection refused)
Package: src:libgovirt Version: 0.3.9-2 Severity: important Tags: ftbfs Dear maintainer: During a rebuild of all packages in bookworm, your package failed to build: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_autoreconf -i dh_auto_configure -i cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu The Meson build system Version: 1.0.0 Source dir: /<> Build dir: /<>/obj-x86_64-linux-gnu Build type: native build Project name: libgovirt Project version: 0.3.9 C compiler for the host machine: cc (gcc 12.2.0 "cc (Debian 12.2.0-14) 12.2.0") C linker for the host machine: cc ld.bfd 2.40 Host machine cpu family: x86_64 Host machine cpu: x86_64 Found pkg-config: /usr/bin/pkg-config (1.8.1) Run-time dependency gobject-2.0 found: YES 2.74.5 Run-time dependency gio-2.0 found: YES 2.74.5 Run-time dependency gthread-2.0 found: YES 2.74.5 Run-time dependency rest-1.0 found: YES 0.9.1 ../meson.build:90: WARNING: Consider using the built-in option for language standard version instead of using "-std=c99". ../meson.build:90: WARNING: Consider using the built-in warning_level option instead of using "-Wall". ../meson.build:90: WARNING: Consider using the built-in warning_level option instead of using "-Wextra". ../meson.build:90: WARNING: Consider using the built-in werror option instead of using "-Werror". Program glib-mkenums found: YES (/usr/bin/glib-mkenums) Program glib-mkenums found: YES (/usr/bin/glib-mkenums) Program glib-mkenums found: YES (/usr/bin/glib-mkenums) Program glib-mkenums found: YES (/usr/bin/glib-mkenums) Compiler for C supports link arguments -Wl,--version-script=/<>/govirt/govirt.sym: YES Run-time dependency gobject-introspection-1.0 found: YES 1.74.0 Dependency gobject-introspection-1.0 found: YES 1.74.0 (cached) Program g-ir-scanner found: YES (/usr/bin/g-ir-scanner) Dependency gobject-introspection-1.0 found: YES 1.74.0 (cached) Program g-ir-compiler found: YES (/usr/bin/g-ir-compiler) Program msgfmt found: YES (/usr/bin/msgfmt) Program msginit found: YES (/usr/bin/msginit) Program msgmerge found: YES (/usr/bin/msgmerge) Program xgettext found: YES (/usr/bin/xgettext) Configuring config.h using configuration Build targets in project: 46 libgovirt 0.3.9 User defined options buildtype: plain libdir : lib/x86_64-linux-gnu localstatedir: /var prefix : /usr sysconfdir : /etc wrap_mode: nodownload Found ninja-1.11.1 at /usr/bin/ninja dh_auto_build -i cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j2 -v [1/72] /usr/bin/meson --internal exe --unpickle /<>/obj-x86_64-linux-gnu/meson-private/meson_exe_glib-mkenums_2344c7feda859570856677f7ac1347dc00086022.dat [2/72] /usr/bin/meson --internal exe --unpickle /<>/obj-x86_64-linux-gnu/meson-private/meson_exe_glib-mkenums_b52fe2ab2b8e36447c4a2ffd17a6bc2a9aadd0fe.dat [3/72] /usr/bin/meson --internal exe --unpickle /<>/obj-x86_64-linux-gnu/meson-private/meson_exe_glib-mkenums_ae41e37139c2dc4daa5377c7fbc122349a834d89.dat [4/72] /usr/bin/msgfmt ../po/bs.po -o po/bs/LC_MESSAGES/govirt-1.0.mo [5/72] /usr/bin/msgfmt ../po/ca.po -o po/ca/LC_MESSAGES/govirt-1.0.mo [6/72] /usr/bin/msgfmt ../po/cs.po -o po/cs/LC_MESSAGES/govirt-1.0.mo [7/72] /usr/bin/msgfmt ../po/da.po -o po/da/LC_MESSAGES/govirt-1.0.mo [8/72] /usr/bin/msgfmt ../po/de.po -o po/de/LC_MESSAGES/govirt-1.0.mo [9/72] /usr/bin/meson --internal exe --unpickle /<>/obj-x86_64-linux-gnu/meson-private/meson_exe_glib-mkenums_06e0afc1956c128753656e39d07b97d4749d7733.dat [10/72] /usr/bin/msgfmt ../po/el.po -o po/el/LC_MESSAGES/govirt-1.0.mo [11/72] cc -Igovirt/libgovirt.so.2.3.1.p -Igovirt -I../govirt -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/rest-1.0 -I/usr/include/libsoup-3.0 -I/usr/include/sysprof-4 -I/usr/include/libxml2 -I/usr/include/json-glib-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=c99 '-DG_LOG_DOMAIN="libgovirt"' -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_66 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_66 -Wall -Wextra -Werror -Wcast-align -Wno-error=cast-align -Wmissing-declarations -Wpointer-arith -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -Wno-unused-parameter -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ
Bug#1030905: sardana: FTBFS (cannot import name 'getargspec' from 'sphinx.util.inspect')
Package: src:sardana
Version: 3.0.3-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules build-indep
dh build-indep --with python3,sphinxdoc --buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_autoreconf -i -O--buildsystem=pybuild
dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:240: python3.11 setup.py config
/<>/setup.py:27: 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
running config
dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:240: /usr/bin/python3 setup.py build
/<>/setup.py:27: 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
running build
[... snipped ...]
byte-compiling
/<>/debian/python3-sardana/usr/lib/python3.11/dist-packages/sardana/pool/test/helper.py
to helper.cpython-311.pyc
byte-compiling
/<>/debian/python3-sardana/usr/lib/python3.11/dist-packages/sardana/pool/test/res/controllers/ROI.py
to ROI.cpython-311.pyc
byte-compiling
/<>/debian/python3-sardana/usr/lib/python3.11/dist-packages/sardana/pool/test/test_synchronization.py
to test_synchronization.cpython-311.pyc
byte-compiling
/<>/debian/python3-sardana/usr/lib/python3.11/dist-packages/sardana/pool/test/test_poolmotor.py
to test_poolmotor.cpython-311.pyc
byte-compiling
/<>/debian/python3-sardana/usr/lib/python3.11/dist-packages/sardana/pool/test/test_poolpseudocounter.py
to test_poolpseudocounter.cpython-311.pyc
byte-compiling
/<>/debian/python3-sardana/usr/lib/python3.11/dist-packages/sardana/pool/test/util.py
to util.cpython-311.pyc
byte-compiling
/<>/debian/python3-sardana/usr/lib/python3.11/dist-packages/sardana/test/testsuite.py
to testsuite.cpython-311.pyc
byte-compiling
/<>/debian/python3-sardana/usr/lib/python3.11/dist-packages/sardana/test/test_sardanabuffer.py
to test_sardanabuffer.cpython-311.pyc
byte-compiling
/<>/debian/python3-sardana/usr/lib/python3.11/dist-packages/sardana/test/__init__.py
to __init__.cpython-311.pyc
byte-compiling
/<>/debian/python3-sardana/usr/lib/python3.11/dist-packages/sardana/test/test_sardanavalue.py
to test_sardanavalue.cpython-311.pyc
running install_egg_info
Copying src/sardana.egg-info to
/<>/debian/python3-sardana/usr/lib/python3.11/dist-packages/sardana-3.0.3.egg-info
Skipping SOURCES.txt
running install_scripts
Installing MacroServer script to /<>/debian/python3-sardana/usr/bin
Installing Pool script to /<>/debian/python3-sardana/usr/bin
Installing Sardana script to /<>/debian/python3-sardana/usr/bin
Installing sardanatestsuite script to
/<>/debian/python3-sardana/usr/bin
Installing spock script to /<>/debian/python3-sardana/usr/bin
Installing diffractometeralignment script to
/<>/debian/python3-sardana/usr/bin
Installing hklscan script to /<>/debian/python3-sardana/usr/bin
Installing macroexecutor script to
/<>/debian/python3-sardana/usr/bin
Installing sequencer script to /<>/debian/python3-sardana/usr/bin
Installing showscan script to /<>/debian/python3-sardana/usr/bin
Installing ubmatrix script to /<>/debian/python3-sardana/usr/bin
I: pybuild pybuild:333: dh_numpy3
dh_installdocs -i -O--buildsystem=pybuild
debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/<>'
PYBUILD_SYSTEM=custom \
PYBUILD_BUILD_ARGS="cd doc && PYTHONPATH={build_dir} http_proxy='127.0.0.1:9'
{interpreter} -m sphinx -N -bhtml source build/html" dh_auto_build # HTML generator
I: pybuild base:240: cd doc &&
PYTHONPATH=/<>/.pybuild/cpython3_3.11_sardana/build
http_proxy='127.0.0.1:9' python3.11 -m sphinx -N -bhtml source build/html
Running Sphinx v5.3.0
Extension error:
Could not import extension sardanaextension (exception: cannot import name
'getargspec' from 'sphinx.util.inspect'
(/usr/lib/python3/dist-packages/sphinx/util/inspect.py))
E: pybuild pybuild:388: build: plugin custom failed with: exit code=2: cd doc &&
PYTHONPATH=/<>/.pybuild/cpython3_3.11_sardana/build
http_proxy='127.0.0.1:9' python3.11 -m sphinx -N -bhtml source build/html
dh_auto_build: error: pybuild --build -i python{version} -p 3.11 returned exit
code 13
make[1]: *** [debian/rules:15: override_dh_sphinxdoc] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess
returned exit status 2
(The above is just how the build ends and not necessarily the most relevant
part)
About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a
Bug#1030903: RFS: tapecalc/20230205-1 -- full-screen tape editor that lets the user edit a calculation
Package: sponsorship-requests Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear mentors, I am looking for a sponsor for my package "tapecalc": * Package name : tapecalc Version : 20230205-1 Upstream contact : Thomas E. Dickey * URL : https://invisible-island.net/add/add.html * License : X11, MIT-old * Vcs : https://salsa.debian.org/debian/tapecalc Section : math The source builds the following binary packages: tapecalc - full-screen tape editor that lets the user edit a calculation To access further information about this package, please visit the following URL: https://mentors.debian.net/package/tapecalc/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/t/tapecalc/tapecalc_20230205-1.dsc Changes since the last upload: tapecalc (20230205-1) unstable; urgency=medium . * New upstream version 20230205. * Update copyright years. * Update standards version to 4.6.2, no changes needed. * Enable Large File Support. * Add autopkgtest. - -- Groet, Regards, Victor Westerhuis -BEGIN PGP SIGNATURE- iQJHBAEBCAAxFiEE6OxII3T+o0Ujs6ECQz2Rq5dHQPsFAmPkLmATHHZpY3RvckB3 ZXN0ZXJodS5pcwAKCRBDPZGrl0dA+5kYEACRb5qYpb3e5KcSxmusLGzjP7NTMlKV C0OI7HbccKn0bBDAs5vBzM+chYSBRh3KIdmj7vuzawQ89VxbXMm2M9K6UmrJNT+k 1/VhwvhGRGesx2moGh5inJ/73zuLH0cViZxFoIPbOVKAJZbjKrN34KXbXJbl9v5j jJedCPTZoml12MSIkzScWf1h2wh3p03mku5KC3NDLFwy//b4Z9Ps0zfFSb6xQ9uQ caG+YxJRS7zLwZPV9hc696XCEU8tNl7E7cSD+911yXqG69uz6GbKFUZw0yC+v9Gc 3oEQkgn3BD38N5YrF8yWbqkUKxVfYbZwJLCclQO5OYj/iPTQx+UTrYQxN8xjlrpX QemIeqatd3RTaExzFSsoh08lZX6zATgxewGRWfb2jBdgNLsUo27w1JQUL5kAWJBv YT4VOWunN/qcg2XKAJodKGyb2xTB9aK6J8PjkjI3NfkCh8SPBoIBZcrMLrVIKm+9 akEpG9bV6/K8Z4QpiQ4NjOFRy0msumLKBAqhqp7J5MFJM52gle6bo5fHdJuQg7sy EoOqpIkRWmLtRkMSQsOVg0E9N6j5KSrPWOOJX+AcFAH1oJc8d5vTxj6wJIA5lcBk 3esGZi+AaPl5VMf8yvH8YqUyy0lZr5QysuLH0TUXHmR9NFpLROzSuSxu5uB4VZVf iYR2bsk1Xdqs1g== =0wge -END PGP SIGNATURE-
Bug#987124: console-setup not work properly with plymouth
Check if systemd is present to avoid errors if it is not. --- /lib/console-setup/console-setup.sh 2023-02-09 01:33:51.198998809 +0300 +++ /lib/console-setup/console-setup.sh 2023-02-09 01:59:48.786418782 +0300 @@ -16,6 +16,13 @@ -nt /etc/default/keyboard ] || do_configure=yes [ /etc/console-setup/cached_setup_terminal.sh \ -nt /etc/default/console-setup ] || do_configure=yes + +# if plymouth-exit.service was launched, this means +# plymouth released tty1 for us to fix +command -v systemctl >/dev/null && \ + [ $(ps -p 1 -o comm=) == "systemd" ] && \ + systemctl is-active -q plymouth-quit.service && \ + do_configure=yes ;; esac Other than that I do not know how to quickly detect exited plymouth and properly order console-setup launch in a SysV boot. Maybe modify /etc/init.d/console-setup.sh to hold while plymouthd is running (with a timeout).
Bug#1030856: debian-i18n: The installer doesn't allow to select freely language and locale
Package: debian-i18n Followup-For: Bug #1030856 Control: tags -1 moreinfo Hi Nicola - please can you provide additional information for this bug report? (for example: what language and locale options are available in the installer, and what is not possible currently in the selection process?)
Bug#1030879: ognibuild: FTBFS randomly (failing tests)
On Wed, Feb 08, 2023 at 07:06:16PM +0100, Santiago Vila wrote:
> ==
> ERROR: test_tee (tests.test_logs.TestCopyOutput.test_tee)
> --
> Traceback (most recent call last):
> File "/<>/.pybuild/cpython3_3.11/build/tests/test_logs.py",
> line 48, in test_tee
> with open(p) as f:
> ^^^
> FileNotFoundError: [Errno 2] No such file or directory:
> '/tmp/tmp7kt8qvlo/foo.log'
>
> --
> Ran 29 tests in 1.676s
>
> FAILED (errors=1)
> E: pybuild pybuild:388: test: plugin distutils failed with: exit code=1: cd
> /<>/.pybuild/cpython3_3.11/build; python3.11 -m unittest
> discover -v
> dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit
> code 13
> make: *** [debian/rules:4: binary-indep] Error 25
> dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit
> status 2
>
>
> The above is really for version 0.0.18-1 where I tested one more time before
> sending this report (I usually don't do archive-wide rebuilds for unstable),
> but this kind of error also happens in the buildds:
>
> https://buildd.debian.org/status/fetch.php?pkg=ognibuild=all=0.0.16-2=1672869872=0
>
> and also in reproducible-builds:
>
> https://tests.reproducible-builds.org/debian/logs/unstable/armhf/ognibuild_0.0.18-1.build2.log.gz
>
> This seems to be "random", but on the machines I've tested it, the failure
> rate is 100%.
Thanks! I've managed to reproduce this locally; will upload an upstream fix &
updated package in
the next couple of days.
Cheers,
Jelmer
Bug#1030096: dask.distributed intermittent autopkgtest fail
On 08/02/2023 22:09, Diane Trout wrote: I just got back a passed from salsa. So does anyone want to make any more changes? Or should we release this version? The *maybe* remaining issue is that test_balance_expensive_tasks[enough work to steal] seems to fail repeatedly when it fails, so if we want to ignore that (I don't claim to know whether that's a good idea), it needs an xfail/skip not just a flaky. I haven't seen that failure in your runs, but I don't know whether that means you've fixed it or just that you were lucky. Mostly, please upload *something* today, because we won't know for sure whether it passes on a real buildd/debci until we try that, and if it doesn't then the sooner we find out the better.
Bug#1030902: RFP: carbonyl -- a Chromium based browser built to run in a terminal
Package: wnpp Severity: wishlist * Package name: carbonyl Version : git Upstream Contact: Fathy Boundjadj * URL : https://github.com/fathyb/carbonyl * License : BSD Programming Lang: Rust, C++ Description : a Chromium based browser built to run in a terminal Carbonyl is a Chromium based browser built to run in a terminal. It supports pretty much all Web APIs including WebGL, WebGPU, audio and video playback, animations, etc.. It's snappy, starts in less than a second, runs at 60 FPS, and idles at 0% CPU usage. It does not require a window server (i.e. works in a safe-mode console), and even runs through SSH. Carbonyl originally started as html2svg and is now the runtime behind it.
Bug#987124: console-setup not work properly with plymouth
Still reproducible on testing. Here is the deal: Console setup is supposed to rely on cached scripts in /etc/console-setup (copied to initramfs). But plymouth starts in initramfs, occupies tty1, which causes setupcon to detect graphical mode and skip tty1. When scripts exist in /etc/console-setup, conditions in /lib/console-setup/console-setup.sh basically skip running setupcon if console-setup.service is launched first time during boot. To fix this: 1. add plymouth-exit.service to After= in console-setup.service 2. add plymouth exit detection to console-setup.sh --- /lib/console-setup/console-setup.sh 2023-02-09 01:33:51.198998809 +0300 +++ /lib/console-setup/console-setup.sh 2023-02-09 01:34:10.826464995 +0300 @@ -16,6 +16,10 @@ -nt /etc/default/keyboard ] || do_configure=yes [ /etc/console-setup/cached_setup_terminal.sh \ -nt /etc/default/console-setup ] || do_configure=yes + +# if plymouth-exit.service was launched and registered as active, +# plymouth has released tty1 for us to fix +systemctl is-active -q plymouth-quit.service && do_configure=yes ;; esac
Bug#1030840: fonts-femkeklaver: relicensing of Debian packaging to 0BSD?
Hi Gioele, --- Original Message --- On Wednesday, February 8th, 2023 at 09:06, Gioele Barabucci wrote: > Given the trivial amount of packaging now left (a handful of boilerplate > code), would you be OK with relicensing it under 0BSD (ISC without > attribution, pretty much public domain)? > > https://opensource.org/licenses/0BSD > > A yes/no answer is enough. I'll take care of the change if you both agree. Sure, go ahead. Cheers Leo Antunes
Bug#1030892: maxima: tab causes "fatal error" and "Segmentation violation"
tags 1030892 unreproducible thanks Greetings, and thanks for your report! I cannot reproduce this. Are you running in a terminal or in an emacs shell? If you precede the tabs with :lisp (si::readline-off) does the problem go away? Take care, Jakub Wilk writes: > Package: maxima > Version: 5.46.0-8 > > Maxima crashes when I press tab twice: > >$ maxima -q > >(%i1) >Maxima encountered a Lisp error: > > Condition in MACSYMA-TOP-LEVEL [or a callee]: INTERNAL-SIMPLE-ERROR: > Caught fatal error [memory may be damaged] > >Automatically continuing. >To enable the Lisp debugger set *debugger-hook* to nil. >(%i1) >Unrecoverable error: Segmentation violation.. >Aborted > > > -- System Information: > Architecture: i386 > > Versions of packages maxima depends on: > ii libc6 2.36-8 > ii libedit2 3.1-20221030-2 > ii libgmp10 2:6.2.1+dfsg1-1.1 > ii libtirpc3 1.3.3+ds-1 > ii libx11-6 2:1.8.3-3 -- Camm Maguirec...@maguirefamily.org == "The earth is but one country, and mankind its citizens." -- Baha'u'llah
Bug#1013933: Keep xsane out of Debian releases
Hello Adrian, I was hoping that the upstream will manage to fix the problems until the new release sane-backends. So far it doesn't look like that unfortunately. I therefore close this bug so that in xsane can be published in bookworm. I am happy to continue to maintain xsane. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser git: https://jff.email/cgit/ Threema: SYR8SJXB Wire: @joergfringsfuerst Skype: joergpenguin Ring: jff Telegram: @joergfringsfuerst My wish list: - Please send me a picture from the nature at your home. Am Montag, dem 06.02.2023 um 22:20 +0200 schrieb Adrian Bunk: > On Mon, Jun 27, 2022 at 07:25:13PM +0200, Jörg Frings-Fürst wrote: > > Package: xsane > > Version: 0.999-12 > > Severity: serious > > > > > > This is a placeholder RC bug to prevent xsane from entering testing > > and making it to a Debian release. Xsane has not been maintained by > > the Upstream author since 2014. Even the current fork does not show > > much further development. > > > > Because of the bugs in the GUI I don't think the current version > > is suitable for a Debian release. > > > > Should the fork develop positively, I will close this bug. > > I am still a user of xsane, and would like to continue using it. > > If the current fork does not well-maintained enough for you, > would you agree to me adopting xsane? > > > CU > > Jörg > > Thanks > Adrian signature.asc Description: This is a digitally signed message part
Bug#1030901: zoph: [INTL:it] Italian po-debconf translation
Sorry, I forgot to actually attach the translation. Here it is. -- Ceppo # zoph po-debconf Italian translation. # Copyright (C) 2023 zoph's copyright holder # This file is distributed under the same license as the zoph package. # Ceppo , 2023. # msgid "" msgstr "" "Project-Id-Version: zoph\n" "Report-Msgid-Bugs-To: z...@packages.debian.org\n" "POT-Creation-Date: 2016-12-15 12:45+\n" "PO-Revision-Date: 2023-02-08 00:00+\n" "Last-Translator: Ceppo \n" "Language-Team: Italian \n" "Language: it\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: select #. Description #: ../zoph.templates:1001 msgid "Remove image files (photos) you uploaded ?" msgstr "Rimuovere i file immagine (fotografie) caricati?" #. Type: select #. Description #: ../zoph.templates:1001 msgid "" "Zoph imports files into, by default, /var/lib/zoph If you decide to remove " "the zoph package, but wish to keep the photos you uploaded answer yes. To " "have the files removed, answer no. To be asked at package removal time " "answer ask." msgstr "" "Zoph importa i file in, per impostazione predefinita, /var/lib/zoph. Se si " "decide di rimuovere il pacchetto zoph, ma si desidera mantenere le " "fotografie caricate rispondere sì. Perché i file vengano rimossi, rispondere " "no. Perché venga chiesto al momento della rimozione del pacchetto rispondere " "chiedi." #. Type: boolean #. Description #: ../zoph.templates:2001 msgid "Keep uploaded image files after removal ?" msgstr "Mantenere dopo la rimozione i file immagine caricati?" #. Type: boolean #. Description #: ../zoph.templates:2001 msgid "" "You have imported some photos into /var/lib/zoph, and are removing the zoph " "package." msgstr "" "Alcune fotografie sono state importate in /var/lib/zoph, e si sta rimuovendo " "il pacchetto zoph."
Bug#1030096: dask.distributed intermittent autopkgtest fail
Hello, So I discovered I'd forgotten to do git cherry-pick --continue so missed the last patch from Rebecca. (b82894aa) Thank you so much for working out a better strategy for the flaky tests. I also found a computer I could log into that has has no working ipv6 support, and so could more quickly debug the ipv6 detection code, and finally got a version of it that works correctly. This version just uses ping but turns off set -e for the test. I just got back a passed from salsa. So does anyone want to make any more changes? Or should we release this version? Diane
Bug#1030901: zoph: [INTL:it] Italian po-debconf translation
Package: zoph Severity: wishlist Tags: l10n patch X-Debbugs-Cc: ce...@oziosi.org Hello, you can find the Italian debconf translation in the attachment. Cheers, -- Ceppo
Bug#1030883: release.debian.org: CI for rust-ureq mysteriously "in progress" for 5 days even on most powerful arches
Quoting Paul Gevers (2023-02-08 21:20:04) > On 08-02-2023 19:31, Jonas Smedegaard wrote: > > omething seems wrong in autopkgtests for rust-ureq: status is listed as > > "Test in progress" on all arches, except ppc64el and s390x that had > > failed, seemingly due to choking on the src:rust-rustls package recently > > switching from arch-any to arch-all - I have requested rechecking of > > those. The others that are "in progress" for suspiciously long do not > > offer me a request to recheck, so I am asking you to please try > > investigate what is going on there... > > I think this is more something for debian-ci (in cc). Very interesting. > On all architectures, there's 1 package pending longer than 5 days, and > on all but one that's rust-ureq. What worries me however, is that > https://ci.debian.net/packages/r/rust-ureq/ mentions also 2 days old > triggered tests in unstable that haven't run. The queue on most > architectures is empty at the moment. > > I've just started a manual run on one of our workers (ci-worker01, > amd64) to see if I see something odd. [some time later] ... and it > passes without issues. (You probably have an unintended test name with > gzip, but otherwise, manual running is OK) > > So it's either the timing was extremely unfortunate and your package hit > something unknown on our infrastructure, or it's actually the package > that's causing issues on our infrastructure. @terceiro; do you have > ideas where to look? I suspect somehow the results of this package cause > the rabbitmq to choke, so the test gets removed from the queue, but its > results not added to the database (that's the opposite of our s390x (and > old riscv64) issue). In case it is helpful: That same day I released between 20 and 40 package updates, all Rust libraries and all involving a switch from arch-any to arch-all, and received some feedback that it had triggered temporary FTBFS for other Rust library packages. My vague impression is that some infrastructure caches package names for virtually provided packages, and then fails to resolve a dependency on "rust-foo-2+bar-dev" which it internally assumes should resolve to "rust-foo-dev:same-arch" but has changed to resolve to "rust-foo-dev:all". - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1030900: gcc-11-cross-ports: FTBFS in Testing due to gcc-9 build-depends
Package: gcc-11-cross-ports Version: 13 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) - broken Build-Depends: gcc-11-cross-ports: lib32gcc1-ppc64-cross lib32gcc1-sparc64-cross lib32gcc1-x32-cross lib64gcc1-powerpc-cross lib64gcc1-x32-cross These packages are NBS by gcc-9-cross-ports and have been removed from Testing. Scott K
Bug#1030899: gcc-10-cross-ports: FTBFS in Testing due to gcc-9 build-depends
Source: gcc-10-cross-ports Version: 21 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) - broken Build-Depends: gcc-10-cross-ports: lib32gcc1-ppc64-cross lib32gcc1-sparc64-cross lib32gcc1-x32-cross lib64gcc1-powerpc-cross lib64gcc1-x32-cross These packages are NBS by gcc-9-cross-ports and have been removed from Testing. Scott K
Bug#1030898: please enable rdma support
Source: libpcap Version: 1.10.3-1 Severity: wishlist Tags: patch This would enable the RDMA sniffer in tcpdump. --- libpcap-1.10.3/debian/controlorig 2023-02-08 14:31:21.136166108 -0700 +++ libpcap-1.10.3/debian/control 2023-02-08 14:22:13.560898916 -0700 @@ -7,6 +7,7 @@ Build-Depends: bison, flex, libbluetooth-dev [linux-any], libdbus-1-dev, + libibverbs-dev, linux-libc-dev [i386] Rules-Requires-Root: no Standards-Version: 4.6.2 -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-3-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND 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#1030897: gcc-11-cross: FTBFS in Testing due to gcc-9 build-depends
Package: gcc-11-cross Version: 17 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) - broken Build-Depends: gcc-11-cross: lib32gcc1-amd64-cross lib32gcc1-s390x-cross lib64gcc1-i386-cross libx32gcc1-amd64-cross libx32gcc1-i386-cross These packages are NBS by gcc-9-cross and have been removed from Testing. Scott K
Bug#1030896: gcc-10-cross-base: FTBFS in Testing due to gcc-9 build-depends
Package: gcc-10-cross-base Version: 20 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) - broken Build-Depends: gcc-10-cross: lib32gcc1-amd64-cross lib32gcc1-s390x-cross lib64gcc1-i386-cross libx32gcc1-amd64-cross libx32gcc1-i386-cross These packages are NBS by gcc-9-cross and have been removed from Testing. Scott K -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-21-amd64 (SMP w/4 CPU threads) 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#1030846: e2fsprogs: generates filesystems that grub-install doesn't recognize
Control: reassign -1 grub2 On Wed, Feb 08, 2023 at 02:02:44PM -0500, Theodore Ts'o wrote: > >The fix for this issue landed in the grub2 repository on June 11, >2021: > >commit 7fd5feff97c4b1f446f8fcf6d37aca0c64e7c763 >Author: Javier Martinez Canillas >Date: Fri Jun 11 21:36:16 2021 +0200 ... >If we *are* going to backport some grub2 patches, may also make a plug >for this one, which is also in the upstream grub2 git repo: > >commit 2e9fa73a040462b81bfbfe56c0bc7ad2d30b446b >Author: Theodore Ts'o >Date: Tue Aug 30 22:41:59 2022 -0400 I've just queued these up in our repo for the next grub upload, due in a few days. -- Steve McIntyre, Cambridge, UK.st...@einval.com "... the premise [is] that privacy is about hiding a wrong. It's not. Privacy is an inherent human right, and a requirement for maintaining the human condition with dignity and respect." -- Bruce Schneier
Bug#1029944: neon27 FTBFS on IPV6-only buildds
On Sun, Jan 29, 2023 at 02:29:23PM +0100, László Böszörményi (GCS) wrote: > Control: tags -1 +confirmed > > On Sun, Jan 29, 2023 at 12:33 PM Adrian Bunk wrote: > > https://buildd.debian.org/status/logs.php?pkg=neon27=amd64 > > > > ... > > auth.. 3/20 FAIL - retries (line 311: HTTP error: > > Could not resolve hostname `127.0.0.1': Address family for hostname not > > supported) > Is there a way to detect such buildds as a maintainer? What can I do > except notifying upstream and / or disable such tests? I don't know any better solution than fixing or disabling such tests (but I am not an expert on that). > Cheers, > Laszlo/GCS cu Adrian
Bug#1007000: closed by Debian FTP Masters (reply to Lucas Kanashiro ) (Bug#1007000: fixed in thin 1.8.1-1)
Control: reopen -1 On Wed, Feb 08, 2023 at 05:57:05PM +, Debian Bug Tracking System wrote: >... > thin (1.8.1-1) unstable; urgency=medium >... >* d/ruby-tests.rake: do not run tests failing on IPv6 builders > (Closes: #1007000). >... This did not work: https://buildd.debian.org/status/fetch.php?pkg=thin=arm64=1.8.1-1=1675888515=0 cu Adrian
Bug#1022061: Where is development happening?
Hi Debian Kernel Team, Where is develop happening? Groeten Geert Stappers P.S. At https://salsa.debian.org/kernel-team/kernel-handbook/-/tags is tag 1.20 missing. -- Silence is hard to parse
Bug#1030894: mirror submission for debianmirror.una.ac.cr
Package: mirrors Severity: wishlist User: mirr...@packages.debian.org Usertags: mirror-submission Submission-Type: new Site: debianmirror.una.ac.cr Type: leaf Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x Archive-http: /debian/ Maintainer: Maykol Phillips Country: CR Costa Rica Trace Url: http://debianmirror.una.ac.cr/debian/project/trace/ Trace Url: http://debianmirror.una.ac.cr/debian/project/trace/ftp-master.debian.org Trace Url: http://debianmirror.una.ac.cr/debian/project/trace/debianmirror.una.ac.cr
Bug#1030883: release.debian.org: CI for rust-ureq mysteriously "in progress" for 5 days even on most powerful arches
Hi Jonas, On 08-02-2023 19:31, Jonas Smedegaard wrote: omething seems wrong in autopkgtests for rust-ureq: status is listed as "Test in progress" on all arches, except ppc64el and s390x that had failed, seemingly due to choking on the src:rust-rustls package recently switching from arch-any to arch-all - I have requested rechecking of those. The others that are "in progress" for suspiciously long do not offer me a request to recheck, so I am asking you to please try investigate what is going on there... I think this is more something for debian-ci (in cc). Very interesting. On all architectures, there's 1 package pending longer than 5 days, and on all but one that's rust-ureq. What worries me however, is that https://ci.debian.net/packages/r/rust-ureq/ mentions also 2 days old triggered tests in unstable that haven't run. The queue on most architectures is empty at the moment. I've just started a manual run on one of our workers (ci-worker01, amd64) to see if I see something odd. [some time later] ... and it passes without issues. (You probably have an unintended test name with gzip, but otherwise, manual running is OK) So it's either the timing was extremely unfortunate and your package hit something unknown on our infrastructure, or it's actually the package that's causing issues on our infrastructure. @terceiro; do you have ideas where to look? I suspect somehow the results of this package cause the rabbitmq to choke, so the test gets removed from the queue, but its results not added to the database (that's the opposite of our s390x (and old riscv64) issue). Paul rust-ureq-2:@PASS rust-ureq-2: PASS rust-ureq-2:brotli PASS rust-ureq-2:cookies PASS rust-ureq-2:default PASS rust-ureq-2:charset PASS -ureq-2:gzip PASS rust-ureq-2:json PASS rust-ureq-2:native-certs PASS rust-ureq-2:native-tls PASS rust-ureq-2:socks-proxy PASS rust-ureq-2:tls PASS OpenPGP_signature Description: OpenPGP digital signature
Bug#1030893: gdb FTBFS
Source: gdb Version: 13.0.91-0.1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=gdb=13.0.91-0.1 ... make[5]: Entering directory '/<>/build/default/gdb/doc' (test "ln -s" = "ln -s" && \ ln -s /<>/gdb/doc/all-cfg.texi gdb-cfg.texi) || \ ln /<>/gdb/doc/all-cfg.texi gdb-cfg.texi || \ cp /<>/gdb/doc/all-cfg.texi gdb-cfg.texi makeinfo --split-size=500 --split-size=500 -DHAVE_MAKEINFO_CLICK -I /<>/gdb/doc/../mi -I /<>/gdb/doc \ -o gdb.info /<>/gdb/doc/gdb.texinfo makeinfo --split-size=500 --split-size=500 -DHAVE_MAKEINFO_CLICK -I /<>/gdb/doc -o stabs.info /<>/gdb/doc/stabs.texinfo makeinfo --split-size=500 --split-size=500 -DHAVE_MAKEINFO_CLICK -I /<>/gdb/doc -o annotate.info /<>/gdb/doc/annotate.texinfo gdb.texinfo:39177: @include: could not find rluser.texi gdb.texinfo:39178: @include: could not find hsuser.texi gdb.texinfo:26429: @xref reference to nonexistent node `Command Line Editing' gdb.texinfo:26461: @xref reference to nonexistent node `Using History Interactively' gdb.texinfo:26557: @xref reference to nonexistent node `Event Designators' gdb.texinfo:29361: @pxref reference to nonexistent node `Command Line Editing' gdb.texinfo:172: @menu reference to nonexistent node `Command Line Editing' gdb.texinfo:173: @menu reference to nonexistent node `Using History Interactively' make[5]: *** [Makefile:491: gdb.info] Error 1
Bug#1030887: Debian 10 To 11 SyntaxError python3-mock 4.0.3-1
Manual Debian 10 python3-certbot-apache install pulled in python3-mock After proceeding with sudo apt-get dist-upgrade: The following packages were automatically installed and are no longer required: bind9utils bsdmainutils dh-python geoip-database libbind9-140 libcurl3-gnutls libdns162 libdumbnet1 libgeoip1 libicu57 libio-stringy-perl libirs141 libisc160 libisccc140 libisccfg140 liblua5.2-0 liblwres141 libmpdec2 libpython3.5-minimal libpython3.5-stdlib libruby2.3 libwebpmux2 libxerces-c3.1 libxml-security-c17v5 linux-image-4.9.0-18-amd64 python3-mock python3-pbr python3.5 python3.5-minimal rename ruby-did-you-mean ruby2.3 tcpd No errors or warnings with sudo apt-get --purge autoremove
Bug#1030886: No Package Available
Vincas, Thank you for the information in your bug report and for your followup fix. I do not personally own any hardware wallets, so I have not been able to test out hardware wallet support. Based on what you have written, it would appear that the dependency you needed to have installed is not packaged in Debian. https://pypi.org/project/ledger-bitcoin/[1] https://packages.debian.org/search?keywords=ledger[2] Also, it appears it might be specific to hardware manufactured by Ledger, although I admit that I do now know enough about the subject to be sure. https://www.ledger.com/[3] In the future it would be ideal to package everything in Debian necessary to fully support hardware ledgers. However, as that is not likely to happen in the short term, I think it would be valuable to at least document what a user needs to add to get hardware wallets working in a README file installed with Electrum. Would you be willing to send me a list of what you have done to get hardware wallets working for you and which hardware wallets are supported by these steps? Thanks, Soren -- Soren Stoutner so...@stoutner.com [1] https://pypi.org/project/ledger-bitcoin/ [2] https://packages.debian.org/search?keywords=ledger [3] https://www.ledger.com/ signature.asc Description: This is a digitally signed message part.
Bug#1030892: maxima: tab causes "fatal error" and "Segmentation violation"
Package: maxima Version: 5.46.0-8 Maxima crashes when I press tab twice: $ maxima -q (%i1) Maxima encountered a Lisp error: Condition in MACSYMA-TOP-LEVEL [or a callee]: INTERNAL-SIMPLE-ERROR: Caught fatal error [memory may be damaged] Automatically continuing. To enable the Lisp debugger set *debugger-hook* to nil. (%i1) Unrecoverable error: Segmentation violation.. Aborted -- System Information: Architecture: i386 Versions of packages maxima depends on: ii libc6 2.36-8 ii libedit2 3.1-20221030-2 ii libgmp10 2:6.2.1+dfsg1-1.1 ii libtirpc3 1.3.3+ds-1 ii libx11-6 2:1.8.3-3 -- Jakub Wilk
Bug#1030891: aom: Use system libwebm instead of the bundled one
Package: aom Version: aom Severity: wishlist Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu lunar ubuntu-patch X-Debbugs-Cc: vladimir.pe...@canonical.com Dear Maintainer, Package aom currently builds with the bundled libwebm located in the `third_party` directory. This bug depends on #1030890, as the current version of libwebm lacks necessary headers. In Ubuntu, the attached patch was applied to achieve the following: - remove bundled libwebm sources - replace references to the bundled libwebm sources in CMakeLists.txt to the system library * debian/patches/0003-use-system-libwebm.patch, debian/rules: Use system libwebm instead of the bundled one. Thanks for considering the patch. aom_3.5.0-1ubuntu1.debdiff Description: Binary data
Bug#1030890: libwebm: Provide additional headers to alllow building aom with the system libwebm
Package: libwebm Severity: wishlist Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu lunar ubuntu-patch X-Debbugs-Cc: vladimir.pe...@canonical.com Dear Maintainer, In order to build aom using the system libwebm, aom needs access to /mkvparser/* and /mkvmuxer/* headers. In Ubuntu, the attached patch was applied to achieve the following: Update CMakeLists.txst so that /mkvparser/* and /mkvmuxer/* headers are provided in /usr/include/webm/mkvparser and /usr/include/webm/mkvparser respectively * debian/patches/0004-add-public-headers.patch: Add additional public headers for aom build Thanks for considering the patch. libwebm_1.0.0.29-1ubuntu1.debdiff Description: Binary data
Bug#1030889: aspic new versions
Package: aspic Version: 1.05-5 Hello, there's a new version of aspic published on: https://github.com/PhilipHazel/aspic This was brought to the Ubuntu security team's attention via some possible security issues discovered by a fuzzing enthusiast: https://github.com/PhilipHazel/aspic/issues/1 https://bugs.launchpad.net/ubuntu/+source/aspic/+bug/2003344 https://bugs.launchpad.net/ubuntu/+source/aspic/+bug/2003354 (I'd be happy to subscribe anyone who wants to take a look at these.) As far as I know, no CVEs have been assigned for any issues. Thanks signature.asc Description: PGP signature
Bug#1030888: bullseye-pu: package ncurses/6.2+20201114-2+deb11u1
Package: release.debian.org Severity: normal Tags: bullseye d-i User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: ncur...@packages.debian.org, debian-b...@lists.debian.org Control: affects -1 + src:ncurses I would like to fix two crash bugs in tic(1) & friends for Bullseye. There have been various similar issues in the previous years which we usually fixed in point releases. [ Reason ] 1. Bug #10098701[1] aka CVE-2022-29458[2] 2. Bug #1029399[3] [ Impact ] 1. Out-of-bounds read in the tinfo library could lead to crashes and potential code execution on crafted input. This usually requires the victim's assistance. 2. Stack buffer overflow can lead to a crash in tic on crafted input. This usually requires the victim's assistance. [ Tests ] 1. The upstream bug report contains a reproducer[4]. It requires building ncurses with -fsanitize=address which I did. This confirmed that the original code has the bug, and the patch seems to fix it. 2. The upstream bug report contains a reproducer[5]. It crashes Bullseye's tic version, but not the patched one. Additionally, I verified that the terminfo database in the ncurses-base and ncurses-term packages is identical to the one in version 6.2+20201114-2. [ Risks ] 1. The upstream fixes in the 20220416 patchlevel do not apply cleanly and needed to be backported, which Thorsten Alteholz did in DLA-3167-1[6] for Bullseye LTS. This obviously increases the risk of something going wrong, however the same change has been in Buster LTS for over three months, and I have not heard of any complaints. While this fix touches the tinfo library, the code in question is, to the best of my knowledge, only used by tic and its aliases as it deals with terminfo source files. 2. The upstream fix from the 20230121 applies cleanly and is fairly small, so I think the risk is low. This issue only affects the tic program, not the library. [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in stable [x] the issues are verified as fixed in unstable [ Changes ] 1. Backport fixes from the 20220416 patchlevel. This has been done by Thorsten Alteholz in 6.1+20181013-2+deb10u3 for Buster LTS, and his patch applys cleanly to the Bullseye version. I have reviewed and fixed up mior issues with the patch such as trailing leading spaces followed by tabs. 2. Cherry-pick bug fix from the 20230121 upstream patchlevel. This is identical to the patch that went into ncurses 6.4-2. 3. Two small changes that help with CI and do not affect the binary packages: Set the release to bullseye in the Salsa CI, and add a lintian override for false-positive errors triggered by lintian 2.115 and newer. [ Other info ] Since ncurses builds a udeb, I have put debian-boot in X-Debbugs-Cc. The changes should not affect the installer. Cheers, Sven 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009870 2. https://security-tracker.debian.org/tracker/CVE-2022-29458 3. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029399 4. https://lists.gnu.org/archive/html/bug-ncurses/2022-04/msg00014.html 5. https://lists.gnu.org/archive/html/bug-ncurses/2023-01/msg00035.html 6. https://security-tracker.debian.org/tracker/DLA-3167-1 diff -Nru ncurses-6.2+20201114/debian/changelog ncurses-6.2+20201114/debian/changelog --- ncurses-6.2+20201114/debian/changelog 2021-01-01 16:02:10.0 +0100 +++ ncurses-6.2+20201114/debian/changelog 2023-02-08 20:16:03.0 +0100 @@ -1,3 +1,18 @@ +ncurses (6.2+20201114-2+deb11u1) bullseye; urgency=medium + + * New patch CVE-2022-29458.diff: add a limit-check to guard against +corrupt terminfo data (report/testcase by NCNIPC of China, +CVE-2022-29458), fix backported from the 20220416 upstream patchlevel +(Closes: #1009870). Thanks to Thorsten Alteholz for the patch. + * New patch fix_crash_on_very_long_tc-use_clause.diff, cherry-picked +from the 20230121 patchlevel: correct limit-check when dumping tc/use +clause via tic -I (report by Gabriel Ravier, Closes: #1029399). + * Use bullseye as the release in the Salsa CI pipeline. + * Add a lintian override for source-is-missing in the Ada documentation +(see #1019980). + + -- Sven Joachim Wed, 08 Feb 2023 20:16:03 +0100 + ncurses (6.2+20201114-2) unstable; urgency=medium * New patch 02-fix-mlterm.diff, cherry-picked from the 20201205 upstream diff -Nru ncurses-6.2+20201114/debian/gitlab-ci.yml ncurses-6.2+20201114/debian/gitlab-ci.yml --- ncurses-6.2+20201114/debian/gitlab-ci.yml 2021-01-01 10:31:15.0 +0100 +++ ncurses-6.2+20201114/debian/gitlab-ci.yml 2023-01-28 12:24:41.0 +0100 @@ -1,3 +1,6 @@ include: - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml +
Bug#1012103: upstream still uses java8
Doclava, which does not work with Java newer than 11. Upstream still builds it with java8. As in Android 13 still uses java8 in the build. Is there any hope?
Bug#1014369: Regression: incorrect icon used in 0.8.0
Hello, Thank you for this bug and the upstream forward. I'll prepare the Debian version for 0.8.1. Cheers, Sebastien signature.asc Description: PGP signature
Bug#1030846: e2fsprogs: generates filesystems that grub-install doesn't recognize
On Wed, Feb 08, 2023 at 11:39:48AM +0100, Cyril Brulebois wrote:
>
> Spotted via debian-installer tests: grub-install fails with “unknown
> filesystem” when trying to run a simple `grub-install /dev/sda` with
> an all-default installation.
The fix for this issue landed in the grub2 repository on June 11,
2021:
commit 7fd5feff97c4b1f446f8fcf6d37aca0c64e7c763
Author: Javier Martinez Canillas
Date: Fri Jun 11 21:36:16 2021 +0200
fs/ext2: Ignore checksum seed incompat feature
This incompat feature is used to denote that the filesystem stored its
metadata checksum seed in the superblock. This is used to allow tune2fs
changing the UUID on a mounted metdata_csum filesystem without having
to rewrite all the disk metadata. However, the GRUB doesn't use the
metadata checksum at all. So, it can just ignore this feature if it
is enabled. This is consistent with the GRUB filesystem code in general
which just does a best effort to access the filesystem's data.
The checksum seed incompat feature has to be removed from the ignore
list if the support for metadata checksum verification is added to the
GRUB ext2 driver later.
Suggested-by: Eric Sandeen
Suggested-by: Lukas Czerner
Signed-off-by: Javier Martinez Canillas
Reviewed-by: Lukas Czerner
Reviewed-by: Daniel Kiper
Unfortunately, this just missed the last grub release, since grub 2.06
was tagged on June 8, 2021.
There are two ways we can fix this. One is we can disable the
checksum seed feature in the Debian release of mke2fs.conf. Or we can
land this above-mentioned commit into the grub2 package. Since the
hard freeze is almost upon us, I'm happy to handle this either way.
If we *are* going to backport some grub2 patches, may also make a plug
for this one, which is also in the upstream grub2 git repo:
commit 2e9fa73a040462b81bfbfe56c0bc7ad2d30b446b
Author: Theodore Ts'o
Date: Tue Aug 30 22:41:59 2022 -0400
fs/ext2: Ignore the large_dir incompat feature
Recently, ext4 added the large_dir feature, which adds support for
a 3 level htree directory support.
The GRUB supports existing file systems with htree directories by
ignoring their existence, and since the index nodes for the hash tree
look like deleted directory entries (by design), the GRUB can simply do
a brute force O(n) linear search of directories. The same is true for
3 level deep htrees indicated by large_dir feature flag.
Hence, it is safe for the GRUB to ignore the large_dir incompat feature.
Fixes: https://savannah.gnu.org/bugs/?61606
Signed-off-by: Theodore Ts'o
Reviewed-by: Daniel Kiper
Otherwise, what can happen is that users may choose to enable the
large_dir feature, and if they do it on the root file system, they can
end up making their system unbootable. I've had some Arch and Gentoo
users get bitten by this
> The “e2fsprogs gets a new upstream release and new flags” hypothesis was
> confirmed by building d-i with e2fsprogs-udeb_1.46.6-1_amd64.udeb
> rebranded as 1.48, which made the problem disappear.
Alternatively, I can apply this patch to e2fsprogs:
diff --git a/misc/mke2fs.conf.in b/misc/mke2fs.conf.in
index b7fc95df7..ff47bdb39 100644
--- a/misc/mke2fs.conf.in
+++ b/misc/mke2fs.conf.in
@@ -11,7 +11,7 @@
features = has_journal
}
ext4 = {
- features =
has_journal,extent,huge_file,flex_bg,metadata_csum,metadata_csum_seed,64bit,dir_nlink,extra_isize,orphan_file
+ features =
has_journal,extent,huge_file,flex_bg,metadata_csum,64bit,dir_nlink,extra_isize,orphan_file
}
small = {
blocksize = 1024
Which will kind of suck, since the reason for enabling
metadata_csum_seed is to be able to reliably change the label and file
system uuid on a mounted file system, which matters for certain cloud
workloads. Specifically, for Google's Cloud Optimized OS, which
attempts to update the file system UUID and resize the root file
system to fit the size of the cloud-emulated block device on two
separate, racing systemd unit files. This which works 99.9% of the
time, but when you launch a huge number of cloud images, that last
0.1% of the time is really noticeable.
But that's for COS; if we have to disable the metadata_csum_seed
feature on Debian file systems, I can live with that.
Cheers,
- Ted
Bug#1030887: Debian 10 To 11 SyntaxError python3-mock 4.0.3-1
Package: python3-mock
Version: 4.0.3-1
user@host:~/ops/all$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
apache2 apache2-bin apache2-data apache2-utils apt apt-utils awscli bash
bind9 bind9-host bind9utils binutils bsd-mailx bsdmainutils bsdutils busybox
ca-certificates certbot coreutils cron curl dash dbus dmsetup dnsutils dpkg
e2fsprogs findutils fuse gdisk gnupg gnupg-agent gpgv groff-base grub-common
grub-pc grub-pc-bin grub2-common iamerican ibritish ienglish-common
initramfs-tools initramfs-tools-core iproute2 iptables iputils-ping irqbalance
isc-dhcp-client ispell less libapache2-mod-svn libapr1 libaprutil1
libaprutil1-dbd-sqlite3 libaprutil1-ldap libaugeas0 libblkid1 libbsd0 libc-bin
libc6
libcurl3-gnutls libdbus-1-3 libdevmapper1.02.1 libedit2 libexpat1 libfdisk1
libfreetype6 libfuse2 libglib2.0-0 libgnutls30 libgpg-error0 libgssapi-krb5-2
libidn2-0 libiptc0 libk5crypto3 libkrb5-3 libkrb5support0 liblcms2-2
libldap-2.4-2 liblocale-gettext-perl libmount1 libncurses5 libncursesw5
libp11-kit0
libpam-modules libpam-modules-bin libpam-systemd libpci3 libpng16-16 libpopt0
libpsl5 libpython3-stdlib librtmp1 libselinux1 libsemanage-common libsemanage1
libserf-1-1 libslang2 libsmartcols1 libsqlite3-0 libss2 libssl1.1 libstdc++6
libsvn1 libsystemd0 libtext-charwidth-perl libtext-iconv-perl libtiff5 libtinfo5
libudev1 libuuid1 libwebp6 libwrap0 libx11-6 libxapian30 libxml2 libxtables12
linux-image-amd64 locales login logrotate lsof man-db mawk mime-support mount
nano ncurses-base ncurses-bin ncurses-term net-tools ntp open-vm-tools
openssh-client openssh-server openssh-sftp-server openssl passwd pciutils perl
perl-base
pinentry-curses postfix postfix-sqlite procps python3 python3-acme
python3-botocore python3-certbot python3-certbot-apache python3-cffi-backend
python3-colorama python3-cryptography python3-minimal python3-openssl
python3-pil python3-pkg-resources python3-requests python3-setuptools
python3-urllib3
python3-zope.hookable python3-zope.interface rename rsyslog ruby screen
subversion sudo systemd systemd-sysv tar tcpd udev util-linux util-linux-locales
vim-common vim-tiny wget whois zerofree
0 upgraded, 0 newly installed, 0 to remove and 180 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up python3-mock (4.0.3-1) ...
File "/usr/lib/python3/dist-packages/mock/mock.py", line 765
mock_name = f'{self._extract_mock_name()}.{name}'
^
SyntaxError: invalid syntax
dpkg: error processing package python3-mock (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
python3-mock
E: Sub-process /usr/bin/dpkg returned an error code (1)
user@host:~/ops/all$
Bug#1030882: RFS: dbus-c++/0.9.0-11 [QA] -- C++ API for D-Bus
Dear mentors, I have forgotten to mention that AFAICS libdbus-c++-dev is the only binary package in Debian that depends on the libraries libdbus-c++-ecore-1.so.0 and/or libdbus-c++-glib-1.so.0. So the introduction of the separate packages libdbus-c++-ecore-1-0 and libdbus-c++-glib-1-0 does not have any impact on any other package in Debian (i.e., no transition needed), and the package libdbus-c++-dev is automatically updated by this new version. For further information, please see Debian bug #1018772: https://bugs.debian.org/1018772 Best regards, Thomas Uhle
Bug#1030885: python-cogent: FTBFS (some tests require more than one CPU)
Package: src:python-cogent
Version: 2020.12.21a+dfsg-4
Severity: important
Tags: ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules binary-indep
dh binary-indep --with python3 --buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_autoreconf -i -O--buildsystem=pybuild
dh_auto_configure -i -O--buildsystem=pybuild
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
I: pybuild plugin_flit:75: Installing package /<>/src/cogent3 ->
/<>/.pybuild/cpython3_3.10_cogent3/build/cogent3
I: pybuild plugin_flit:88: Writing dist-info
/<>/.pybuild/cpython3_3.10_cogent3/build/
set -x; cd doc; PYTHONPATH=/<> http_proxy='127.0.0.1:9'
/usr/bin/make html
+ cd doc
+ PYTHONPATH=/<> http_proxy=127.0.0.1:9 /usr/bin/make html
make[2]: Entering directory '/<>/doc'
[...]
=== FAILURES ===
__ TestBootstrap.test_bstrap_parallel __
self =
def test_bstrap_parallel(self):
"""exercising bootstrap with parallel"""
aln = load_aligned_seqs(join(data_dir, "brca1.fasta"), moltype="dna")
aln = aln.take_seqs(aln.names[:3])
aln = aln.omit_gap_pos(allowed_gap_frac=0)
opt_args = dict(max_evaluations=20, limit_action="ignore")
m1 = evo_app.model("F81", opt_args=opt_args)
m2 = evo_app.model("HKY85", opt_args=opt_args)
hyp = evo_app.hypothesis(m1, m2)
strapper = evo_app.bootstrap(hyp, num_reps=2, parallel=True)
result = strapper(aln)
self.assertIsInstance(result, evo_app.bootstrap_result)
E AssertionError: NotCompleted(type=ERROR, origin=bootstrap,
source="/<>/.pybuild/cpython3_3.10_cogent3/build/tests/data/brca1.fasta",
message="Traceback (most recent call last):
E File
"/<>/.pybuild/cpython3_3.10_cogent3/build/cogent3/app/composable.py",
line 312, in _trapped_call
E val = func(val, *args, **kwargs)
E File
"/<>/.pybuild/cpython3_3.10_cogent3/build/cogent3/app/evo.py",
line 461, in run
E sym_results = [r for r in map_fun(self._fit_sim,
range(self._num_reps)) if r]
E File
"/<>/.pybuild/cpython3_3.10_cogent3/build/cogent3/app/evo.py", line 461,
in
E sym_results = [r for r in map_fun(self._fit_sim,
range(self._num_reps)) if r]
E File
"/<>/.pybuild/cpython3_3.10_cogent3/build/cogent3/util/parallel.py",
line 169, in imap
E chunksize = get_default_chunksize(s, max_workers)
E File
"/<>/.pybuild/cpython3_3.10_cogent3/build/cogent3/util/parallel.py",
line 90, in get_default_chunksize
E chunksize, remainder = divmod(len(s), max_workers * 4)
E ZeroDivisionError: integer division or modulo by zero
E ") is not an instance of
/<>/.pybuild/cpython3_3.10_cogent3/build/tests/test_app/test_evo.py:858:
AssertionError
TestIo.test_write_db_parallel _
self =
def test_write_db_parallel(self):
"""writing with overwrite in parallel should reset db"""
with TemporaryDirectory(dir=".") as dirname:
outdir = join(dirname, "delme.tinydb")
dstore = io_app.get_data_store(self.basedir, suffix="fasta")
members = dstore.filtered(
callback=lambda x: "brca1.fasta" not in x.split("/")
)
reader = io_app.load_unaligned()
aligner = align_app.align_to_ref()
writer = write_db(outdir, create=True, if_exists="overwrite")
process = reader + aligner + writer
r = process.apply_to(
members, show_progress=False, parallel=True, cleanup=True
)
/<>/.pybuild/cpython3_3.10_cogent3/build/tests/test_app/test_io.py:523:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/<>/.pybuild/cpython3_3.10_cogent3/build/cogent3/util/progress_display.py:197:
in f
result = slow_function(*args, **kw)
/<>/.pybuild/cpython3_3.10_cogent3/build/cogent3/app/composable.py:487:
in apply_to
for result in ui.series(to_do, count=len(inputs)):
/<>/.pybuild/cpython3_3.10_cogent3/build/cogent3/util/progress_display.py:123:
in series
for (i, item) in enumerate(items):
/<>/.pybuild/cpython3_3.10_cogent3/build/cogent3/util/parallel.py:240:
in as_completed
yield from _as_completed_mproc(f, s, max_workers)
/<>/.pybuild/cpython3_3.10_cogent3/build/cogent3/util/parallel.py:225:
in _as_completed_mproc
with concurrentfutures.ProcessPoolExecutor(max_workers=max_workers) as
executor:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self =
max_workers = 0, mp_context = None, initializer = None, initargs = ()
def __init__(self, max_workers=None, mp_context=None,
Bug#1030884: python-cogent: FTBFS (ImportError: cannot import name 'float' from 'numpy')
Package: src:python-cogent
Version: 2022.8.24a1+dfsg-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules binary-indep
dh binary-indep --with python3 --buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_autoreconf -i -O--buildsystem=pybuild
[...]
Traceback:
/usr/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
test_evolve/test_coevolution.py:27: in
from cogent3.evolve.coevolution import (
../cogent3/evolve/coevolution.py:50: in
from numpy import (
E ImportError: cannot import name 'float' from 'numpy'
(/usr/lib/python3/dist-packages/numpy/__init__.py)
=== warnings summary ===
../../../../../../usr/lib/python3/dist-packages/llvmlite/binding/ffi.py:159
/usr/lib/python3/dist-packages/llvmlite/binding/ffi.py:159:
DeprecationWarning: path is deprecated. Use files() instead. Refer to
https://importlib-resources.readthedocs.io/en/latest/using.html#migrating-from-legacy
for migration advice.
_lib_handle = importlib.resources.path(pkgname, _lib_name)
-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=== short test summary info
ERROR tests/test_evolve/test_coevolution.py
Interrupted: 1 error during collection
== 5 deselected, 1 warning, 1 error in 11.16s ==
E: pybuild pybuild:388: test: plugin flit failed with: exit code=2: cd
/<>/.pybuild/cpython3_3.11_cogent3/build; python3.11 -m pytest -k
'not test_pickleable_member_roundtrip and not test_pickleable_roundtrip'
dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit
code 13
make: *** [debian/rules:22: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit
status 2
The above is just how the build ends but I believe it's also the most relevant
part.
A very similar error happens here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-cogent.html
-
About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).
If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks.
Bug#1018061: pads: segfault at 3a ip
Opppss I thought I had, here it is. bt full #0 0x5641638af954 in print_arp_asset_screen (rec=0x2a) at ./src/output/output-screen.c:115 No locals. #1 0x5641638af6f0 in print_arp_asset (ip_addr=..., mac_addr=0x7fa6db692384 "") at ./src/output/output.c:210 head = 0x5641654a33f0 list = rec = 0x2a #2 0x7fa6dbe004f6 in ?? () from /lib/x86_64-linux- gnu/libpcap.so.0.8 No symbol table info available. #3 0x7fa6dbe008ec in ?? () from /lib/x86_64-linux- gnu/libpcap.so.0.8 No symbol table info available. #4 0x7fa6dbe07d1d in pcap_loop () from /lib/x86_64-linux-gnu/libpcap.so.0.8 No symbol table info available. #5 0x5641638a8e5b in main_pads () at ./src/pads.c:278 No locals. #6 0x5641638a847b in main (argc=, argv=) at ./src/pads.c:491 No locals. (gdb) Quit (gdb) bt full #0 0x5641638af954 in print_arp_asset_screen (rec=0x2a) at ./src/output/output-screen.c:115 No locals. #1 0x5641638af6f0 in print_arp_asset (ip_addr=..., mac_addr=0x7fa6db692384 "") at ./src/output/output.c:210 head = 0x5641654a33f0 list = rec = 0x2a #2 0x7fa6dbe004f6 in ?? () from /lib/x86_64-linux- gnu/libpcap.so.0.8 No symbol table info available. #3 0x7fa6dbe008ec in ?? () from /lib/x86_64-linux- gnu/libpcap.so.0.8 No symbol table info available. #4 0x7fa6dbe07d1d in pcap_loop () from /lib/x86_64-linux-gnu/libpcap.so.0.8 No symbol table info available. #5 0x5641638a8e5b in main_pads () at ./src/pads.c:278 No locals. #6 0x5641638a847b in main (argc=, argv=) at ./src/pads.c:491 No locals. (gdb) #0 0x5641638af954 in print_arp_asset_screen (rec=0x2a) at ./src/output/output-screen.c:115 No locals. #1 0x5641638af6f0 in print_arp_asset (ip_addr=..., mac_addr=0x7fa6db692384 "") at ./src/output/output.c:210 head = 0x5641654a33f0 list = rec = 0x2a #2 0x7fa6dbe004f6 in ?? () from /lib/x86_64-linux- gnu/libpcap.so.0.8 No symbol table info available. #3 0x7fa6dbe008ec in ?? () from /lib/x86_64-linux- gnu/libpcap.so.0.8 No symbol table info available. #4 0x7fa6dbe07d1d in pcap_loop () from /lib/x86_64-linux-gnu/libpcap.so.0.8 No symbol table info available. #5 0x5641638a8e5b in main_pads () at ./src/pads.c:278 No locals. #6 0x5641638a847b in main (argc=, argv=) at ./src/pads.c:491 No locals. (gdb) -- Tim McConnell On Wed, 2023-02-08 at 19:26 +0100, Bernhard Übelacker wrote: > Am 08.02.23 um 18:42 schrieb Tim McConnell: > > Hi Bernhard, > > Okay I did that. Let me know if that was of any use. > > Hello Tim, > could you send the actual output below the `bt full`? > > Kind regards, > Bernhard
Bug#1030883: release.debian.org: CI for rust-ureq mysteriously "in progress" for 5 days even on most powerful arches
Package: release.debian.org Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 omething seems wrong in autopkgtests for rust-ureq: status is listed as "Test in progress" on all arches, except ppc64el and s390x that had failed, seemingly due to choking on the src:rust-rustls package recently switching from arch-any to arch-all - I have requested rechecking of those. The others that are "in progress" for suspiciously long do not offer me a request to recheck, so I am asking you to please try investigate what is going on there... Kind regards, - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmPj6mkACgkQLHwxRsGg ASFRDhAAj8TkU5voEEtYUYqRTKO6em1sDezRY3o2VBY2yXZ/bw09nrR2BxpvGyri jOFpdOEVVitL6MTpjU2zALT6Gk1jWJfOT6FIrRbCo43J1fFyDuse+p+TI5nr2iWq jRyL81TF+F6UssK2qw5oKVijbc7pEEXvReHSF4MHAkQm0vaIH4mX9bFvTBByfa8l v2FqLo3EeYvuR8mLDig7h9uv2XmR2zbZq1A/wCP02O+YRaGFEsjWeVDo8LzH93ef aQ883hzWYYEXNFwqHd+M5pj4+jeuD3iEVCjFmlF4a4NAWMKLFO5FYhaAgzrOGGO4 kck51HCq/4p1tfp+UtDqpItsYImyfNR9FiI//Sb/drA40d73yY01CB9yj1fFlaS4 iHc2kgzEIMSbUxNCJMf8BRIj+MZUuHjkvYklGxFzwciG/flFDPq1QMXudOI2+R43 jGNblioXBsh32W367J1YPgaGm6zubudaWauoMqtGnLP+ajWQ7tErAAl8Jy8E/Xt0 ksHsx3dV9eKN7iX875Cvglhko1hPPpQe57qgekm3p2wkBp9TSZeRv1dybnUNnflT 1TLuGxaHwothyoNJZetdR61NZVM4S7dey6hX5LyBkuDmnyMRt1PG95VBfSVImleo rHdvIsk4lVVLyY+d8yepPfxnbwzwZj4yIX05aLC82/0zrAr225o= =rupV -END PGP SIGNATURE-
Bug#1030882: RFS: dbus-c++/0.9.0-11 [QA] -- C++ API for D-Bus
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the dbus-c++ package: * Package name : dbus-c++ Version : 0.9.0-11 Upstream contact : * URL or Web page : http://sourceforge.net/projects/dbus-cplusplus/ * License : LGPL-2.1, GPL-3+ * Vcs : https://salsa.debian.org/debian/dbus-cplusplus Section : libs The source builds the following binary packages: libdbus-c++-1-0v5 - C++ API for D-Bus (runtime library with independent main loop) libdbus-c++-bin - C++ API for D-Bus (utilities) libdbus-c++-dev - C++ API for D-Bus (development package) libdbus-c++-doc - C++ API for D-Bus (documentation) libdbus-c++-ecore-1-0 - C++ API for D-Bus (runtime library with Ecore main loop) libdbus-c++-glib-1-0 - C++ API for D-Bus (runtime library with GLib main loop) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/dbus-c++/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/d/dbus-c++/dbus-c++_0.9.0-11.dsc Changes since the last upload: dbus-c++ (0.9.0-11) UNRELEASED; urgency=medium * QA upload. * Add 09_fix_build_order_and_linking.patch to change the order in which the libraries are built and to fix the underlinking issue. (Closes: #889114) * Add 10_prevent_deadlock_on_timeout_expiration.patch to prevent a possible deadlock. (Closes: #956114) * Add 11_fix_MessageIter__copy_data.patch to fix copying nested types in dicts and structs. (LP: #1098723) * Add 12_autoconf_update.patch to avoid hard-to-read deprecation warnings that clutter the build logs. * Update 01_host_name_max.patch because stdio.h is needed by perror(). * debian/control: + Add libdbus-1-dev to libdbus-c++-dev's dependencies. (Closes: #1018771) + Fix spelling and capitalization of the package descriptions. + Put libdbus-c++-ecore-1.so.* and libdbus-c++-glib-1.so.* in their own binary packages libdbus-c++-ecore-1-0 and libdbus-c++-glib-1-0 resp. to avoid pulling in e.g. Ecore libraries (and their dependencies) on systems where these libraries are not needed. (Closes: 1018772) + Mark libdbus-c++-bin as Multi-Arch: allowed. It fixes a regression since version 0.9.0-9. + Add Rules-Requires-Root: no. + Bump Standards-Version to 4.6.2, no changes needed. Mainly, this new version closes all the remaining bugs in Debian and from Launchpad, and it fixes a regression that was introduced by version 0.9.0-9. Therefore, I think it would be good to have it in Debian 12. I already have uploaded all individual commits to Salsa for an easier review. You can find them at: https://salsa.debian.org/uhle/dbus-cplusplus (forked repo) As this is my very first attempt to upload a package to Debian, I certainly need some kind of guidance. I don't know if I should do a merge request on Salsa for instance. But who would respond then? This package has been orphaned. Best regards, Thomas Uhle
Bug#1018061: pads: segfault at 3a ip
Am 08.02.23 um 18:42 schrieb Tim McConnell: Hi Bernhard, Okay I did that. Let me know if that was of any use. Hello Tim, could you send the actual output below the `bt full`? Kind regards, Bernhard
Bug#1030881: release.debian.org: please have rust-rustls-native-certs ignore CI tests for s390x and ppc64el
Package: release.debian.org Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 rust-rustls-native-certs currently fails to migrate to testing due to dependency rust-ring missing on archs ppc64el and s390x. rust-rustls-native-certs is arch-all, and ideally rust-ring would be arch-all as well and this issue would not occur. (for completeness sake I should mention that Rust team would likely argue that the ideal was that I joined the Rust team, obeyed their team policy, and released rust-rustls-native-certs as arch-any in which case the World would burn slightly more fossil fuel and this issue also would disappear). Please marg ppc64el and s390x as irrelevant archs for rust-rustls-native-certs to let the package migrate to testing. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmPj6JMACgkQLHwxRsGg ASHZlg//S5x+A0F985fyq/hns5h/cm9i4mwjPerar+slBGktHdvvmqyG2ltRHkoS th4Ir3e/HhBkBkv56Lm0d7JIk5/6vqANNeH5yIqXi6TLM/BrzghJD52F6khebgR6 VIyqWjWMj67LhAQrXtifKLBlYed9we4g/kjMRWqEXxW20AQqwNlLB80o7Z15z/x8 MIQ6KHrjDCEP0RHmnZk/VymCYUsdgsmNqVZRjHmLyMKluJ9KTdVVRa4GXT4SR+iZ J+QzZo65/dly1roWQk1vuHsosgPPQYWdmxoaWVHe3N1vYlyyYJhAFh8myIc1ZJFa VG7jlHBKGnOiJhk0wSL468LDi4w1Dtq51R5deYxo4QtQkQHGCnmSCw6D11zoewCU ik8g6s9yboUGGBi2mJ6SPPTE8SwUIMrjKe+Dlm6SLjQnzyh12FcRzy8NREb8QOC3 9Vu6IDl39SM1+tOC4BtIveUAvyEMVHr2J6iMAVpRzYjAdXOWeR1/AKB+iWjAfcLW oI7IcFuxUo2QxH5Im35XoXiMRLC9z0jE2plaeGhKWvmYqEdnx/PSPyVDqBhxHwB7 mP+uuNwzUnGpSZnj8vGOoh0Jq0KRQErefILbrXUN3noq2YhBnyOpaZcGpdvzo4I6 nsGLJ/vMLDMcia42FvRtN5uYMBxPVTUZjd7xc1Q9MdyLmnfgMjM= =LzC6 -END PGP SIGNATURE-
Bug#1030880: RM: sa-learn-cyrus -- RoQA; outdated, uninstallable, no upload since 2013
Package: ftp.debian.org Severity: normal Usertags: rm-request User: ftp.debian@packages.debian.org Usertags: remove Hi, Please proceed to deleting the package: sa-learn-cyrus It's only in unstable now and is uninstallable. Last upload: 2013-03-06, 10 years ago. Informations: - Last activity of the maintainer on Debian: 2013-05-26 Package bugs: - #[730335][1] (ipurge command path has changed in the latest cyrus-common package) - #[730729][2] (fail for mailboxes with spaces) - #[830596][3] (depends on cyrus-imapd-2.4 which is gone) [edos-uninstallable,piuparts] Found on my QA dashboard. [1]: https://bugs.debian.org/730335 [2]: https://bugs.debian.org/730729 [3]: https://bugs.debian.org/830596 -- William Desportes
Bug#1030879: ognibuild: FTBFS randomly (failing tests)
Package: src:ognibuild Version: 0.0.18-1 Severity: important Tags: ftbfs Dear maintainer: During a rebuild of all packages in bookworm, your package failed to build: [...] debian/rules binary-indep dh binary-indep --buildsystem=pybuild dh_update_autotools_config -i -O--buildsystem=pybuild dh_autoreconf -i -O--buildsystem=pybuild dh_auto_configure -i -O--buildsystem=pybuild I: pybuild base:240: python3.11 setup.py config running config dh_auto_build -i -O--buildsystem=pybuild I: pybuild base:240: /usr/bin/python3 setup.py build running build running build_py creating /<>/.pybuild/cpython3_3.11/build/ognibuild copying ognibuild/clean.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild copying ognibuild/requirements.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild copying ognibuild/__main__.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild copying ognibuild/dep_server.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild copying ognibuild/buildlog_converters.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild copying ognibuild/info.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild copying ognibuild/fix_build.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild copying ognibuild/buildsystem.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild copying ognibuild/build.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild copying ognibuild/upstream.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild copying ognibuild/dist.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild copying ognibuild/outputs.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild copying ognibuild/logs.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild copying ognibuild/buildlog.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild copying ognibuild/vcs.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild copying ognibuild/install.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild copying ognibuild/__init__.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild copying ognibuild/test.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild copying ognibuild/dist_catcher.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild copying ognibuild/fixers.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild creating /<>/.pybuild/cpython3_3.11/build/ognibuild/debian copying ognibuild/debian/udd.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild/debian copying ognibuild/debian/fix_build.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild/debian copying ognibuild/debian/build.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild/debian copying ognibuild/debian/build_deps.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild/debian copying ognibuild/debian/__init__.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild/debian copying ognibuild/debian/file_search.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild/debian copying ognibuild/debian/apt.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild/debian copying ognibuild/debian/upstream_deps.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild/debian creating /<>/.pybuild/cpython3_3.11/build/ognibuild/resolver copying ognibuild/resolver/dep_server.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild/resolver copying ognibuild/resolver/__init__.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild/resolver copying ognibuild/resolver/apt.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild/resolver creating /<>/.pybuild/cpython3_3.11/build/ognibuild/session copying ognibuild/session/plain.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild/session copying ognibuild/session/schroot.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild/session copying ognibuild/session/__init__.py -> /<>/.pybuild/cpython3_3.11/build/ognibuild/session copying ognibuild/py.typed -> /<>/.pybuild/cpython3_3.11/build/ognibuild running build_scripts creating build creating build/scripts-3.11 copying and adjusting scripts/report-apt-deps-status -> build/scripts-3.11 changing mode of build/scripts-3.11/report-apt-deps-status from 644 to 755 dh_auto_test -i -O--buildsystem=pybuild I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build; python3.11 -m unittest discover -v test_exist (tests.test_buildlog.TestProblemsExists.test_exist) ... ok test_exists (tests.test_debian_build.AddDummyChangelogEntryTests.test_exists) tests.test_debian_build.AddDummyChangelogEntryTests.test_exists ... failed to open trace file: [Errno 13] Permission denied: '/you-should-use-TestCaseInTempDir-if-you-need-a-log-file' ok test_native (tests.test_debian_build.AddDummyChangelogEntryTests.test_native) tests.test_debian_build.AddDummyChangelogEntryTests.test_native ... ok test_simple (tests.test_debian_build.AddDummyChangelogEntryTests.test_simple) tests.test_debian_build.AddDummyChangelogEntryTests.test_simple ... ok test_is_str (tests.test_debian_build.BuildArchitectureTests.test_is_str) tests.test_debian_build.BuildArchitectureTests.test_is_str ... ok test_simple (tests.test_debian_build.BuilddebCommandTests.test_simple)
Bug#1030878: RM: gcap -- RoQA; outdated, broken, no upload since 2018, no upstream updates
Package: ftp.debian.org Severity: normal Usertags: rm-request User: ftp.debian@packages.debian.org Usertags: remove Hi, Please proceed to deleting the package: gcap I tested it and reported in #1030877 that the package is not usable. Informations: - Last upload: 2018-10-04, 5 years ago. - Maintainer is the QA group. Found on my QA dashboard. -- William Desportes
Bug#299927: debtags future unclear
On Wed, Feb 08, 2023 at 01:24:52PM +, Holger Levsen wrote: > control: tags -1 +moreinfo > control: affects -1 debtags > thanks > > hi, > > https://lists.debian.org/msgid-search/20221019132043.d4c4liyt6s6qe...@enricozini.org > and > https://lists.debian.org/msgid-search/bb7064071ebd838a9e045a1916bba49a9b960d80.ca...@debian.org > indicate that debtags.debian.org might be shutdown after the release > of bookworm, thus tagging this bug moreinfo for now, as there's not > much point documenting something which is going away. It seems this concerns only the debtags.debian.org website, not the whole debgtags system, right ? Cheers, -- Bill. Imagine a large red swirl here.
Bug#1030877: gcap: perl error, package unusable
Package: gcap Version: 0.1.1-2 Severity: grave This package does not work (with an existing or non existing YT video), using manpage examples: On my workstation: $ gcap 0QRO3gKj3qw Checking ...Couldn't parsefile [http://video.google.com/timedtext?hl=en=list=0QRO3gKj3qw] with LWP: no element found at line 1, column 0, byte -1 at /usr/lib/x86_64-linux-gnu/perl5/5.34/XML/Parser.pm line 187. On Debian sid: $ gcap 0QRO3gKj3qw Checking ...Couldn't parsefile [http://video.google.com/timedtext?hl=en=list=0QRO3gKj3qw] with LWP: no element found at line 1, column 0, byte -1 at /usr/lib/x86_64-linux-gnu/perl5/5.36/XML/Parser.pm line 187. $ gcap "http://www.youtube.com/watch?v=0QRO3gKj3qw; Checking ...Couldn't parsefile [http://video.google.com/timedtext?hl=en=list=0QRO3gKj3qw] with LWP: no element found at line 1, column 0, byte -1 at /usr/lib/x86_64-linux-gnu/perl5/5.36/XML/Parser.pm line 187. $ gcap -ti 0QRO3gKj3qw WARNING Umph::Prompt not found, ignoring --interactive option Checking ...Couldn't parsefile [http://video.google.com/timedtext?hl=en=list=0QRO3gKj3qw] with LWP: no element found at line 1, column 0, byte -1 at /usr/lib/x86_64-linux-gnu/perl5/5.36/XML/Parser.pm line 187. $ gcap https://www.youtube.com/watch?v=kkui_qBYvmY Checking ...Couldn't parsefile [http://video.google.com/timedtext?hl=en=list=kkui_qBYvmY] with LWP: no element found at line 1, column 0, byte -1 at /usr/lib/x86_64-linux-gnu/perl5/5.36/XML/Parser.pm line 187. $ gcap kkui_qBYvmY Checking ...Couldn't parsefile [http://video.google.com/timedtext?hl=en=list=kkui_qBYvmY] with LWP: no element found at line 1, column 0, byte -1 at /usr/lib/x86_64-linux-gnu/perl5/5.36/XML/Parser.pm line 187.
Bug#801065: Documenting how to not fail postinst on service fails to starto
On Wed, Feb 08, 2023 at 06:39:08PM +0100, Bill Allombert wrote: > Note that the TC declining to rule on an issue does not override the policy > group right to make > a determination on that issue. So we are back to the situation before the > referral to the TC. do you think #801065 should be assigned from developers-reference to debian-policy? -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ It's climate crime, not climate change. signature.asc Description: PGP signature
Bug#1030785: -ffile-prefix-map option and reproducibility
On 2023-02-08, Stéphane Glondu wrote: > Thank you all for your answers! > > Using: > >DEB_BUILD_MAINT_OPTIONS=reproducible=-fixfilepath,-fixdebugpath > > makes the package unreproducible in another way that seems difficult to fix. Most likely reintroducing the things that the -ffile-prefix-map and -fdebug-prefix-map was effectively removing... We track these kinds of issues with the "records build flags" issue, which has a description of the problem and links to more information: https://tests.reproducible-builds.org/debian/issues/unstable/records_build_flags_issue.html There are some potential fixes to the issue more fundamentally, but they are currently stalled out... one of which I should probably spend some time on after bookworm release... You had earlier asked when this was enabled, this can mostly be found in the dpkg changelog: fixfilepath (a.k.a. -ffile-prefix-map) Enabled by default: dpkg (1.20.6) unstable; urgency=medium ... * dpkg-buildflags: Enable reproducible=fixfilepath by default. Thanks to Vagrant Cascadian . See https://lists.debian.org/debian-devel/2020/10/msg00222.html. Closes: #974087 ... -- Guillem Jover Fri, 08 Jan 2021 04:39:40 +0100 fixfilepath (a.k.a. -ffile-prefix-map) feature added, and enabled in reproducible builds infrastructure soon after: dpkg (1.19.1) unstable; urgency=medium ... - Dpkg::Vendor::Debian: Add fixfilepath support to reproducible feature. ... -- Guillem Jover Wed, 26 Sep 2018 15:13:22 +0200 fixdebugpath (a.k.a. -fdebug-prefix-map) enabled by default: dpkg (1.18.10) unstable; urgency=medium ... - Enable fixdebugpath build flag feature by default. Thanks to Mattia Rizzolo . Closes: #832179 ... -- Guillem Jover Sun, 31 Jul 2016 12:57:02 +0200 fixdebugpath (a.k.a. -fdebug-prefix-map) feature added, and presumably enabled in reproducible builds infrastructure soon after: dpkg (1.18.5) unstable; urgency=medium ... - Add fixdebugpath to reproducible feature in Dpkg::Vendor::Debian. Thanks to Daniel Kahn Gillmor . Closes: #819194 ... -- Guillem Jover Mon, 02 May 2016 04:14:57 +0200 Of course, this is only for packages respecting dpkg-buildflags. > Le 07/02/2023 à 19:12, Mattia Rizzolo a écrit : >> I actually propose to you to filter out the whole option from being >> saved. [...] > > I've gone this way, and managed to make the package reproducible, at > least with the build path variation. Glad that works! > I will upload the fixed ocaml package when the current batch of related > packages waiting in unstable migrates to testing, hopefully in 4 days. Thanks! live well, vagrant signature.asc Description: PGP signature
Bug#1018061: pads: segfault at 3a ip
Hi Bernhard, Okay I did that. Let me know if that was of any use. -- Tim McConnell On Wed, 2023-02-08 at 16:16 +0100, Bernhard Übelacker wrote: > bt full
Bug#801065: consent unclear
On Wed, Feb 08, 2023 at 06:13:32PM +0100, Bill Allombert wrote: > > not only based on that, but way more importantly that this would change > > *years* of existing practice. > Could you clarify which 'existing practices' ? how Debian packages behaved in the last decades. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ The wrong Amazon is burning. signature.asc Description: PGP signature
Bug#801065: Documenting how to not fail postinst on service fails to starto
O#n Wed, Feb 08, 2023 at 04:47:37PM +, Holger Levsen wrote: > retitle -1 turn #904558 into advice - how postinst should deal with failures > thanks > > On Wed, Feb 08, 2023 at 09:26:58AM -0700, Sam Hartman wrote: > > The TC bug is 904558. > > thank you very much for this pointer, that's a pretty good discussion, > which resulted in > > - > > So, the TC declines to rule on what should maintscripts do when failing > to > (re)start a service (or otherwise encountering a similarly serious > problem). > > - > (read the full result at > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904558#137 ) Note that the TC declining to rule on an issue does not override the policy group right to make a determination on that issue. So we are back to the situation before the referral to the TC. Cheers, -- Bill. Imagine a large red swirl here.
Bug#1030876: rocm-smi-lib:FTBFS on hppa - out of range call
Source: rocm-smi-lib Version: 5.2.3-2 Severity: normal Tags: ftbfs Dear Maintainer, The build fails with the following error: [ 48%] Linking CXX shared library liboam.so cd /<>/obj-hppa-linux-gnu/oam && /usr/bin/cmake -E cmake_link_script CMakeFiles/oam.dir/link.txt --verbose=1 /usr/bin/c++ -fPIC -g -O2 -ffile-prefix-map=/<>=. -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -fno-rtti -std=c++11 -Wconversion -Wcast-align -Wformat=2 -fno-common -Wstrict-overflow -Woverloaded-virtual -Wreorder -DFORTIFY_SOURCE=2 -fstack-protector-all -Wcast-align -Wl,-z,noexecstack -Wl,-znoexecheap -Wl,-z,relro -Wtrampolines -Wl,-z,now -fPIE -ggdb -O0 -DDEBUG -shared -Wl,-soname,liboam.so.1 -o liboam.so.1.0 CMakeFiles/oam.dir/__/src/rocm_smi_device.cc.o CMakeFiles/oam.dir/__/src/rocm_smi_main.cc.o CMakeFiles/oam.dir/__/src/rocm_smi_monitor.cc.o CMakeFiles/oam.dir/__/src/rocm_smi_power_mon.cc.o CMakeFiles/oam.dir/__/src/rocm_smi_utils.cc.o CMakeFiles/oam.dir/__/src/rocm_smi_counters.cc.o CMakeFiles/oam.dir/__/src/rocm_smi_kfd.cc.o CMakeFiles/oam.dir/__/src/rocm_smi_io_link.cc.o CMakeFiles/oam.dir/__/src/rocm_smi_gpu_metrics.cc.o CMakeFiles/oam.dir/__/src/rocm_smi.cc.o CMakeFiles/oam.dir/__/third_party/shared_mutex/shared_mutex.cc.o CMakeFiles/oam.dir/src/amd_oam.cc.o -lpthread -lrt /usr/bin/ld: warning: -z noexecheap ignored /usr/bin/ld: CMakeFiles/oam.dir/__/src/rocm_smi_device.cc.o(.text._ZNSt12_Vector_baseIN3amd3smi12DevInfoTypesESaIS2_EE12_Vector_implC2ERKS3_[_ZNSt12_Vector_baseIN3amd3smi12DevInfoTypesESaIS2_EE12_Vector_implC5ERKS3_]+0x3c): cannot reach 1bea__ZNSaIN3amd3smi12DevInfoTypesEEC2ERKS2_+0, recompile with -ffunction-sections /usr/bin/ld: CMakeFiles/oam.dir/__/src/rocm_smi_device.cc.o(.text._ZNSt12_Vector_baseIN3amd3smi12DevInfoTypesESaIS2_EE12_Vector_implC2ERKS3_[_ZNSt12_Vector_baseIN3amd3smi12DevInfoTypesESaIS2_EE12_Vector_implC5ERKS3_]+0x3c): cannot handle R_PARISC_PCREL17F for _ZNSaIN3amd3smi12DevInfoTypesEEC2ERKS2_ /usr/bin/ld: final link failed: bad value collect2: error: ld returned 1 exit status make[3]: *** [oam/CMakeFiles/oam.dir/build.make:276: oam/liboam.so.1.0] Error 1 make[3]: Leaving directory '/<>/obj-hppa-linux-gnu' This can be worked around by adding "-mlong-calls" to CXXFLAGS. See for example: https://buildd.debian.org/status/fetch.php?pkg=rocm-smi-lib=hppa=5.2.3-2=1675874950=0 Regards, Dave Anglin -- System Information: Debian Release: bookworm/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: hppa (parisc64) Kernel: Linux 6.1.10+ (SMP w/4 CPU threads) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#1030846: e2fsprogs: generates filesystems that grub-install doesn't recognize
On 2023-02-08 11:39 +0100, Cyril Brulebois wrote: > Package: e2fsprogs > Version: 1.47.0-1 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: debian-b...@lists.debian.org, gr...@packages.debian.org > > (Please keep debian-b...@lists.debian.org and gr...@packages.debian.org > in the loop.) > > Hi, > > Spotted via debian-installer tests: grub-install fails with “unknown > filesystem” when trying to run a simple `grub-install /dev/sda` with > an all-default installation. > > While there might be something wrong about e2fsprogs-udeb specifically, > possibly only affecting the installer context, I'm not sure what that > means for existing systems, hence the severity. > > The “e2fsprogs gets a new upstream release and new flags” hypothesis was > confirmed by building d-i with e2fsprogs-udeb_1.46.6-1_amd64.udeb > rebranded as 1.48, which made the problem disappear. It is the metadata_csum_seed feature that is now enabled by default which grub-install does not grok. This has been reported "recently"[1]. Cheers, Sven 1. https://bugs.debian.org/866603
Bug#1030875: ITP: golang-github-go-enry-go-oniguruma -- Super Fast Regex in Go
Package: wnpp Severity: wishlist Owner: Vinay Keshava * Package name : golang-github-go-enry-go-oniguruma Version : 1.2.1-1 Upstream Author : go-enry * URL : https://github.com/go-enry/go-oniguruma * License : Expat Programming Lang: Go Description: Super Fast Regex in Go (library) simple regular expression library (based on oniguruma (https://github.com/kkos/oniguruma)) that supports Ruby's regex syntax. Regards, Vinay
Bug#801065: consent unclear
On Wed, Feb 08, 2023 at 03:54:22PM +, Holger Levsen wrote: > hi, > > btw, as pointed out on irc: I ment consensus, not consent. :) > > On Wed, Feb 08, 2023 at 10:36:02AM -0500, Marvin Renich wrote: > > > I don't think there has been consent on the issue, thus I'm tagging it > > > moreinfo. > > > > > > I'm also wondering whether to mark this bug as wontfix (until there is > > > consent) or to reassign to debian-policy or simply to close it. > > > > I disagree. Re-reading the messages to the bug report, We have > > "strongly support" from Sam Hartman, and "also in favor" from Russ > > Allbery and Bill Allombert. > > > > The only objection was from Henrique de Moraes Holschuh based on lack of > > risk assessment from the mistaken impression > > not only based on that, but way more importantly that this would change > *years* of existing practice. Could you clarify which 'existing practices' ? Cheers, -- Bill. Imagine a large red swirl here.
Bug#1030874: linux-headers-6.1.0-3-amd64: Dependency problems prevent configuration of linux-headers-amd64
Package: linux-headers-6.1.0-3-amd64
Version: 6.1.8-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in
the past)
X-Debbugs-Cc: smit...@hush.com
Dear Maintainer,
*** Reporter, please consider answering these questions, where
appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE not
set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages linux-headers-6.1.0-3-amd64 depends on:
ii linux-compiler-gcc-12-x86 6.1.8-1
ii linux-headers-6.1.0-3-common 6.1.8-1
ii linux-kbuild-6.1 6.1.8-1
linux-headers-6.1.0-3-amd64 recommends no packages.
linux-headers-6.1.0-3-amd64 suggests no packages.
-- no debconf information
p, li { white-space: pre-wrap; }
Bug#1030873: ruby-coffee-script is deprecated, please remove the dependency
Package: ruby-jekyll-coffeescript Version: 1.2.2-3 severity: serious Control: block 1019927 by -1 ruby-coffee-script is deprecated #1019927 and we are trying to remove it from bookworm. coffee command line provided by coffeescript package still works (and using node version via webpack is recommended by rails), so using that could be an option, or alternatively if ruby-coffee-script is still useful, someone will need to take over the upstream maintenance.
Bug#1030872: ITP: ruby-google-apis-compute-v1 -- Simple REST client for Compute Engine API V1
package: wnpp Severity: wishlist Owner: Vinay Keshava *Package Name : ruby-google-apis-compute-v1 Version : 0.14.0 Upstream Author : 2021 Google LLC *URL :https://github.com/googleapis/google-api-ruby-client *License : Apache-2.0 Programming Lang : Ruby *Description: Simple REST client for Compute Engine API V1 This is the simple REST client for Compute Engine API V1. Simple REST clients are Ruby client libraries that provide access to Google services via their HTTP REST API endpoints. These libraries are generated and updated automatically based on the discovery documents published by the service, and they handle most concerns such as authentication, pagination, retry, timeouts, and logging. You can use this client to access the Compute Engine API, but note that some services may provide a separate modern client that is easier to use.. This gem is required for gitlab. - Vinay Keshava
Bug#801065: Documenting how to not fail postinst on service fails to start
retitle -1 turn #904558 into advice - how postinst should deal with failures thanks On Wed, Feb 08, 2023 at 09:26:58AM -0700, Sam Hartman wrote: > The TC bug is 904558. thank you very much for this pointer, that's a pretty good discussion, which resulted in - So, the TC declines to rule on what should maintscripts do when failing to (re)start a service (or otherwise encountering a similarly serious problem). - (read the full result at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904558#137 ) so I still think "#801065 discourage failing install or upgrade when service fails to start" is the wrong recommendation for dev-ref. That said, I'd still appreciate a patch that conveys the gist of #904558. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ The apocalypse is here now, it’s just not equally distributed. signature.asc Description: PGP signature
Bug#1030871: libtcnative-1: Current version of tcnative is not compatible with version of tomcat 10 packaged
Package: libtcnative-1 Version: 1.2.32-1+b1 Severity: important X-Debbugs-Cc: jorge.moral...@gmail.com Dear Maintainer, The version of tomcat10 currently packaged (10.1.5) cannot work with the version of libtcnative-1 currently packaged (1.2.32). The exact log error in Catalina.out is An incompatible version [1.2.32] of the Apache Tomcat Native library is installed, while Tomcat requires version [1.2.34] I think that tomcat9 "may" still be able to use 1.2.32 version (I have not tested it) hence I have marked the severity "important" and not "grave". Thank you -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (800, 'testing'), (50, 'experimental'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-3-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE 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 libtcnative-1 depends on: ii libapr1 1.7.0-8 ii libc62.36-8 ii libssl3 3.0.7-2 libtcnative-1 recommends no packages. libtcnative-1 suggests no packages. -- no debconf information
Bug#1030870: Drop unneeded dependency on ruby-coffee-script
Package: tdiary-core Version: 5.2.3-1 Severity: serious Justification: ruby-coffee-script is deprecated and we want to remove it in bookworm Control: block 1019927 by -1 ruby-coffee-script is deprecated (#1019927) and we'd like to remove it from bookworm (this and ruby-jekyll-coffeescript are the lats two packages still depending on ruby-coffee-script). It looks https://salsa.debian.org/ruby-team/tdiary/-/blob/master/tdiary.gemspec does not list ruby-coffee-script, so it should be easy to drop it from Depends. If you really want to use coffeescript in this package, you can still use the coffee command line (which also supports -t option to generate ES5 output, which is no longer the default in coffeescript 2).
Bug#1030869: tomcat10: Catalina won't deploy applications missing class jakarta.websocket.DeploymentException
Package: tomcat10 Version: 10.1.5-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: jorge.moral...@gmail.com Dear Maintainer, Catalina is unable to deploy any applications (including samplp ROOT) complaining of java.lang.ClassNotFoundException: jakarta.websocket.DeploymentException Please see full log of Catalina.out [2023-02-08 11:21:24] [info] Listening for transport dt_socket at address: 8000 [2023-02-08 11:21:24] [info] Server version name: Apache Tomcat/10.1.5 (Debian) [2023-02-08 11:21:24] [info] Server built: Jan 2 1970 23:05:43 UTC [2023-02-08 11:21:24] [info] Server version number: 10.1.5.0 [2023-02-08 11:21:24] [info] OS Name: Linux [2023-02-08 11:21:24] [info] OS Version:6.1.0-3-amd64 [2023-02-08 11:21:24] [info] Architecture: amd64 [2023-02-08 11:21:24] [info] Java Home: /usr/lib/jvm/java-17-openjdk-amd64 [2023-02-08 11:21:24] [info] JVM Version: 17.0.6+10-Debian-1 [2023-02-08 11:21:24] [info] JVM Vendor:Debian [2023-02-08 11:21:24] [info] CATALINA_BASE: /var/lib/tomcat10 [2023-02-08 11:21:24] [info] CATALINA_HOME: /usr/share/tomcat10 [2023-02-08 11:21:24] [info] Command line argument: -Djava.util.logging.config.file=/var/lib/tomcat10/conf/logging.properties [2023-02-08 11:21:24] [info] Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager [2023-02-08 11:21:24] [info] Command line argument: -Djava.awt.headless=true [2023-02-08 11:21:24] [info] Command line argument: -agentlib:jdwp=transport=dt_socket,address=nile:8000,server=y,suspend=n [2023-02-08 11:21:24] [info] Command line argument: -Djdk.tls.ephemeralDHKeySize=2048 [2023-02-08 11:21:24] [info] Command line argument: -Djava.protocol.handler.pkgs=org.apache.catalina.webresources [2023-02-08 11:21:24] [info] Command line argument: -Dorg.apache.catalina.security.SecurityListener.UMASK=0027 [2023-02-08 11:21:24] [info] Command line argument: --add- opens=java.base/java.lang=ALL-UNNAMED [2023-02-08 11:21:24] [info] Command line argument: --add- opens=java.base/java.io=ALL-UNNAMED [2023-02-08 11:21:24] [info] Command line argument: --add- opens=java.base/java.util=ALL-UNNAMED [2023-02-08 11:21:24] [info] Command line argument: --add- opens=java.base/java.util.concurrent=ALL-UNNAMED [2023-02-08 11:21:24] [info] Command line argument: --add- opens=java.rmi/sun.rmi.transport=ALL-UNNAMED [2023-02-08 11:21:24] [info] Command line argument: -Dcatalina.base=/var/lib/tomcat10 [2023-02-08 11:21:24] [info] Command line argument: -Dcatalina.home=/usr/share/tomcat10 [2023-02-08 11:21:24] [info] Command line argument: -Djava.io.tmpdir=/tmp [2023-02-08 11:21:24] [info] The Apache Tomcat Native library which allows using OpenSSL was not found on the java.library.path: [/usr/java/packages/lib:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux- gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib] [2023-02-08 11:21:25] [info] The ["https-jsse-nio-8443"] connector has been configured to support negotiation to [h2] via ALPN [2023-02-08 11:21:25] [info] Initializing ProtocolHandler ["https-jsse- nio-8443"] [2023-02-08 11:21:25] [info] Server initialization in [1098] milliseconds [2023-02-08 11:21:25] [info] Starting service [Catalina] [2023-02-08 11:21:25] [info] Starting Servlet engine: [Apache Tomcat/10.1.5 (Debian)] [2023-02-08 11:21:26] [info] Deploying web application directory [/var/lib/tomcat10/webapps/ROOT] [2023-02-08 11:21:26] [crit] Error deploying web application directory [/var/lib/tomcat10/webapps/ROOT] [2023-02-08 11:21:26] [crit] java.lang.IllegalStateException: Error starting child [2023-02-08 11:21:26] [crit] at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:729) [2023-02-08 11:21:26] [crit] at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:698) [2023-02-08 11:21:26] [crit] at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:747) [2023-02-08 11:21:26] [crit] at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1136) [2023-02-08 11:21:26] [crit] at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1971) [2023-02-08 11:21:26] [crit] at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [2023-02-08 11:21:26] [crit] at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) [2023-02-08 11:21:26] [crit] at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) [2023-02-08 11:21:26] [crit] at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:123) [2023-02-08 11:21:26] [crit] at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:1046) [2023-02-08 11:21:26] [crit] at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:428) [2023-02-08 11:21:26] [crit] at
Bug#1030868: ITP: ruby-google-apis-monitoring-v3 -- Simple REST client for Cloud Monitoring API V3
package: wnpp Severity: wishlist Owner: Vinay Keshava *Package Name : ruby-google-apis-monitoring-v3 Version : 0.12.0 Upstream Author : 2021 Google LLC *URL :https://github.com/googleapis/google-api-ruby-client *License : Apache-2.0 Programming Lang : Ruby *Description: Simple REST client for Cloud Monitoring API V3 This is the simple REST client for Cloud Monitoring API V3. Simple REST clients are Ruby client libraries that provide access to Google services via their HTTP REST API endpoints. These libraries are generated and updated automatically based on the discovery documents published by the service, and they handle most concerns such as authentication, pagination, retry, timeouts, and logging. You can use this client to access the Cloud Monitoring API, but note that some services may provide a separate modern client that is easier to use. This gem is required for gitlab. - Vinay Keshava
Bug#1030867: aseba: Missing builds on s390x and ppc64el
Package: aseba
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar ubuntu-patch
Dear Maintainer,
In Ubuntu, aseba previously built on s390x and ppc64el. I see build
architectures were restricted[1] in a recent version. I have tested
s390x and ppc64el builds in Ubuntu, and would like to re-enable those
arches.
Thanks for considering the patch.
-Nick
[1]
https://salsa.debian.org/science-team/aseba/-/commit/d5ad0ce97c814ccac777cf5ee86eeaaf4b5a9bac
[2]
https://launchpad.net/~enr0n/+archive/ubuntu/proposed-migration/+packages?field.name_filter=aseba_filter=published_filter=lunar
diff -Nru aseba-1.6.99+dfsg/debian/control aseba-1.6.99+dfsg/debian/control
--- aseba-1.6.99+dfsg/debian/control2022-07-15 12:25:36.0 -0400
+++ aseba-1.6.99+dfsg/debian/control2023-02-07 09:58:53.0 -0500
@@ -18,7 +18,7 @@
Homepage: https://github.com/aseba-community/aseba
Package: aseba
-Architecture: any-amd64 any-i386 arm64 mips64el mipsel riscv64
+Architecture: any-amd64 any-i386 arm64 mips64el mipsel riscv64 s390x ppc64el
Depends: ${shlibs:Depends}, ${misc:Depends}
Suggests: aseba-plugin-blockly
Description: Event-based framework for distributed mobile robots control
Bug#1030866: ITP: ruby-google-apis-monitoring-v3 -- Simple REST client for Cloud Monitoring API V3
package: wnpp Severity: wishlist Owner: Vinay Keshava *Package Name : ruby-google-apis-monitoring-v3 Version : 0.12.0 Upstream Author : 2021 Google LLC *URL :https://github.com/googleapis/google-api-ruby-client *License : Apache-2.0 Programming Lang : Ruby *Description: Simple REST client for Cloud Monitoring API V3 This is the simple REST client for Cloud Monitoring API V3. Simple REST clients are Ruby client libraries that provide access to Google services via their HTTP REST API endpoints. These libraries are generated and updated automatically based on the discovery documents published by the service, and they handle most concerns such as authentication, pagination, retry, timeouts, and logging. You can use this client to access the Cloud Monitoring API, but note that some services may provide a separate modern client that is easier to use. This gem is required for gitlab. - Vinay Keshava
Bug#1030865: RFS: ncdu/1.18-0.2 [NMU] -- ncurses disk usage viewer
Package: sponsorship-requests Severity: normal X-Debbugs-CC: jac...@debian.org Dear mentors, I am looking for a sponsor for my package "ncdu": * Package name : ncdu Version : 1.18-0.2 Upstream contact : Yoran Heling * URL : https://dev.yorhel.nl/ncdu/ * License : Zlib, Expat Section : admin The source builds the following binary packages: ncdu - ncurses disk usage viewer To access further information about this package, please visit the following URL: https://mentors.debian.net/package/ncdu/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/n/ncdu/ncdu_1.18-0.2.dsc Changes since the last upload: ncdu (1.18-0.2) unstable; urgency=medium . * Non-maintainer upload. * d/patches: cherry-pick commits to fix FTBFS on GNU/Hurd Regards, -- Christian Göttsche
Bug#801065: Documenting how to not fail postinst on service fails to start
The TC bug is 904558. Busy with day job now.
Bug#1030864: RFS: selint/1.4.0-2 -- Static code analysis of refpolicy style SELinux policies
Package: sponsorship-requests Severity: normal X-Debbugs-CC: selinux-de...@lists.alioth.debian.org Dear mentors, I am looking for a sponsor for my package "selint": * Package name : selint Version : 1.4.0-2 Upstream contact : Daniel Burgener * URL : https://github.com/SELinuxProject/selint * License : Apache-2.0 * Vcs : https://salsa.debian.org/selinux-team/selint Section : devel The source builds the following binary packages: selint - Static code analysis of refpolicy style SELinux policies To access further information about this package, please visit the following URL: https://mentors.debian.net/package/selint/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/s/selint/selint_1.4.0-2.dsc Changes since the last upload: selint (1.4.0-2) unstable; urgency=medium . * d/patches: add: skip valgrind tests if valgrind is not available Regards, -- Christian Göttsche
Bug#1030852: unable to run "aideinit" successfully
Control: tags -1 moreinfo unreproducible
thanks
On Wed, Feb 08, 2023 at 02:01:13PM +0100, David S wrote:
> When I invoke `aideinit' without arguments from an ordinary shell
> prompt it prints:
>
> `ERROR: /etc/aide/aide.conf.d/31_aide_munin-nodes (stdout):1:
> unexpected character: '/' (line:
> '/var/cache/munin/www/uaegeas1/(index\.html|uaegeas1\n/[-_[:alnum:]]+\.(png|html))$
> f VarFile/var/lib/munin/uaegeas1/uaegeas1\n-.*\.rrd$ f
> VarFile/@@{RUN}/munin/munin-(update|datafile|uaegeas1-uaegeas1|limits)\.lock$
> f VarFile')
This does not happen on current sid. Can you show bash -x
/etc/aide/aide.conf.d/31_aide_munin-nodes output and probably your
munin.conf file? This looks like the parsing of your munin.conf
incorrectly includes line feeds into the parsed HOSTS variable.
> I am using Debian GNU/Linux 2.2, kernel 2.2.17-pre-patch-13
> and libc6 2.1.3-10.
Are you joking?
Grüße
Marc
Bug#801065: Documenting how to not fail postinst on service fails to start
> "Holger" == Holger Levsen writes: Holger> I do agree with that. I'm more against a general Holger> recommendation, depending on the circumstances, it's the Holger> right thing to do. My recollection is this came before the TC, but I'm blanking on the bug number. But it seems like the sticking point is the general recommendation. I'd love to figure out how to do this though and document for other people (I have a Ubuntu bug open against krb5 that basically boils down to this issue). >> Holger, would you support adding a comment to 6.4 explaining how >> to do it? Holger> surely. >> I'd write text but I'm honestly baffled how to accomplish this >> for systemd units with dh. Holger> :) Marvin, do you have any clue how to accomplish?
Bug#1030863: Following Redirecs breaks authentication on subsequent requests
Package: libcurl3-gnutls
Version: 7.74.0-1.3+deb11u5
When a curl handle is used to follow a cross-protocol (e.g. https to
http) redirect, subsequent requests done with the same handle lack the
"Authorization" header even though basicauth credentials are provided.
The following pycurl-based Python script demonstrates the problem (I'm
sorry I cannot provide a reproducer in C):
### START OF SCRIPT ###
#!/usr/bin/env python3
import pycurl
curl = pycurl.Curl()
# Perform request with https-to-http redirect
curl.setopt(pycurl.VERBOSE, True)
curl.setopt(pycurl.URL,
"https://httpbin.org/redirect-to?url=http://httpbin.org;
)
curl.setopt(pycurl.FOLLOWLOCATION, True)
curl.setopt(pycurl.WRITEFUNCTION, lambda buff: None)
curl.perform()
assert curl.getinfo(pycurl.REDIRECT_COUNT) == 1
assert curl.getinfo(pycurl.RESPONSE_CODE) == 200
curl.reset()
# Perform request with basicauth. This fails.
curl.setopt(pycurl.VERBOSE, True)
curl.setopt(
pycurl.HTTPAUTH,
pycurl.HTTPAUTH_ANY & ~pycurl.HTTPAUTH_NEGOTIATE,
)
curl.setopt(
pycurl.URL,
"https://httpbin.org:443/basic-auth/user/password;,
)
curl.setopt(pycurl.USERPWD, "user:password")
curl.perform()
print("Status:", curl.getinfo(pycurl.RESPONSE_CODE))
### END OF SCRIPT ###
The debug output of libcurl contains the message
* Clear auth, redirects to port from 443 to 80
when following the redirect. The requests during the second transfer
all lack the "Authorization" header (full log is attached). When the
first request is omitted, the second one works.
The bug must have been introduced after 7.74.0-1.3+deb11u3 because that
version does not have this problem. I suspect that the patch "CVE-2022-
27774_2_of_4.patch" introduced in version 7.74.0-1.3+deb11u5 is
incomplete because it sets the "this_is_a_follow_without_auth" bit but
never seems to clear it.
Regards
Marc Schmitzer
--
Marc Schmitzer
Software Developer
Phone: +49 721 98993239
Fax:+49 721 98993-66
E-mail: m...@solute.de
solute GmbH
Zeppelinstraße 15
76185 Karlsruhe
Germany
Marken der solute GmbH | brands of solute GmbH
billiger.de | Shopping.de
Geschäftsführer | Managing Director: Dr. Thilo Gans, Bernd Vermaaten
Webseite | www.solute.de
Sitz | Registered Office: Karlsruhe
Registergericht | Register Court: Amtsgericht Mannheim
Registernummer | Register No.: HRB 110579
USt-ID | VAT ID: DE234663798
Informationen zum Datenschutz | Information about privacy policy
http://solute.de/ger/datenschutz/grundsaetze-der-datenverarbeitung.php
* Trying 52.200.117.68:443...
* Connected to httpbin.org (52.200.117.68) port 443 (#0)
* found 389 certificates in /etc/ssl/certs
* ALPN, offering h2
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256
* server certificate verification OK
* server certificate status verification SKIPPED
* common name: httpbin.org (matched)
* server certificate expiration date OK
* server certificate activation date OK
* certificate public key: RSA
* certificate version: #3
* subject: CN=httpbin.org
* start date: Fri, 21 Oct 2022 00:00:00 GMT
* expire date: Sun, 19 Nov 2023 23:59:59 GMT
* issuer: C=US,O=Amazon,OU=Server CA 1B,CN=Amazon
* ALPN, server accepted to use h2
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x1cd1570)
> GET /redirect-to?url=http://httpbin.org HTTP/2
Host: httpbin.org
user-agent: PycURL/7.43.0.6 libcurl/7.74.0 GnuTLS/3.7.1 zlib/1.2.11 brotli/1.0.9 libidn2/2.3.0 libpsl/0.21.0 (+libidn2/2.3.0) libssh2/1.9.0 nghttp2/1.43.0 librtmp/2.3
accept: */*
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 302
< date: Wed, 08 Feb 2023 15:56:22 GMT
< content-type: text/html; charset=utf-8
< content-length: 0
< location: http://httpbin.org
< server: gunicorn/19.9.0
< access-control-allow-origin: *
< access-control-allow-credentials: true
<
* Connection #0 to host httpbin.org left intact
* Clear auth, redirects to port from 443 to 80* Issue another request to this URL: 'http://httpbin.org/'
* Trying 52.1.93.201:80...
* Connected to httpbin.org (52.1.93.201) port 80 (#1)
> GET / HTTP/1.1
Host: httpbin.org
User-Agent: PycURL/7.43.0.6 libcurl/7.74.0 GnuTLS/3.7.1 zlib/1.2.11 brotli/1.0.9 libidn2/2.3.0 libpsl/0.21.0 (+libidn2/2.3.0) libssh2/1.9.0 nghttp2/1.43.0 librtmp/2.3
Accept: */*
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Date: Wed, 08 Feb 2023 15:56:23 GMT
< Content-Type: text/html; charset=utf-8
< Content-Length: 9593
< Connection: keep-alive
< Server: gunicorn/19.9.0
< Access-Control-Allow-Origin: *
< Access-Control-Allow-Credentials: true
<
* Connection #1 to host httpbin.org left intact
* Found bundle for host httpbin.org: 0x1cc56a0 [can multiplex]
* Re-using existing connection! (#0) with host httpbin.org
* Connected to httpbin.org (52.200.117.68) port 443
Bug#1005824: QtWebEngine: build with pipewire support
Control: affects -1 + qutebrowser
Control: tags -1 + patch
On Tue, 15 Feb 2022 22:31:33 +0530 Pirate Praveen
wrote:
> Hi! I have seen
> https://mail.kde.org/pipermail/falkon/2022-February/000869.html – FYI,
> whether screensharing works under Wayland or not depends on how QtWebEngine
> is built, see: https://github.com/qutebrowser/qutebrowser/issues/5421
>
> Looking at the Fedora package, it is not currently built with Pipewire, so no
> way it will work on Fedora. But that is not Falkon's fault. We need to fix
> our QtWebEngine package.
>
> It is the same for other affected distros.
>
> That said, whether it will work then or hit other bugs, I cannot tell, since
> we have not enabled it yet.
Patch (thanks to ArchLinux [1]) in attachment works under pipewire + wayland +
qutebrowser.
[1]
https://github.com/archlinux/svntogit-packages/commit/5d4742100b9ddbcf4f374276335bb42dfcc5423d
--
Cédric Hannotier
>From f238e94bc767d0aedaf750ab1ab509ad70d7c673 Mon Sep 17 00:00:00 2001
Subject: [PATCH] Enable PipeWire screencasting
---
debian/control|1 +
.../patches/qt5-webengine-pipewire-0.3.patch | 1824 +
debian/patches/series |1 +
debian/rules |1 +
4 files changed, 1827 insertions(+)
create mode 100644 debian/patches/qt5-webengine-pipewire-0.3.patch
diff --git a/debian/control b/debian/control
index 827e12c..6f4086f 100644
--- a/debian/control
+++ b/debian/control
@@ -39,6 +39,7 @@ Build-Depends: binutils (>= 2.32-8~),
libopenjp2-7-dev,
libopus-dev (>= 1.3.1),
libpci-dev,
+ libpipewire-0.3-dev,
libpng-dev,
libprotobuf-dev,
libpulse-dev,
diff --git a/debian/patches/qt5-webengine-pipewire-0.3.patch b/debian/patches/qt5-webengine-pipewire-0.3.patch
new file mode 100644
index 000..67b5a33
--- /dev/null
+++ b/debian/patches/qt5-webengine-pipewire-0.3.patch
@@ -0,0 +1,1824 @@
+Description: Enable WebRTC screen sharing through PipeWire
+Origin: https://github.com/archlinux/svntogit-packages/blob/packages/qt5-webengine/trunk/qt5-webengine-pipewire-0.3.patch
+Bug: 1005824
+Last-Update: 2023-02-06
+
+diff --git a/src/3rdparty/chromium/third_party/webrtc/modules/desktop_capture/BUILD.gn b/src/3rdparty/chromium/third_party/webrtc/modules/desktop_capture/BUILD.gn
+index 5235512735d..8259442f811 100644
+--- a/src/3rdparty/chromium/third_party/webrtc/modules/desktop_capture/BUILD.gn
b/src/3rdparty/chromium/third_party/webrtc/modules/desktop_capture/BUILD.gn
+@@ -11,6 +11,11 @@ import("//build/config/ui.gni")
+ import("//tools/generate_stubs/rules.gni")
+ import("../../webrtc.gni")
+
++if (rtc_use_pipewire) {
++ assert(rtc_pipewire_version == "0.2" || rtc_pipewire_version == "0.3",
++ "Unsupported PipeWire version")
++}
++
+ use_desktop_capture_differ_sse2 = current_cpu == "x86" || current_cpu == "x64"
+
+ config("x11_config") {
+@@ -200,22 +205,41 @@ if (is_linux || is_chromeos) {
+ ]
+ }
+
+-if (rtc_link_pipewire) {
++if (rtc_pipewire_version == "0.3") {
+ pkg_config("pipewire") {
+-packages = [ "libpipewire-0.2" ]
++packages = [ "libpipewire-0.3" ]
++if (!rtc_link_pipewire) {
++ ignore_libs = true
++}
+ }
+ } else {
++ pkg_config("pipewire") {
++packages = [ "libpipewire-0.2" ]
++if (!rtc_link_pipewire) {
++ ignore_libs = true
++}
++ }
++}
++
++if (!rtc_link_pipewire) {
+ # When libpipewire is not directly linked, use stubs to allow for dlopening of
+ # the binary.
+ generate_stubs("pipewire_stubs") {
+-configs = [ "../../:common_config" ]
++configs = [
++ "../../:common_config",
++ ":pipewire",
++]
+ deps = [ "../../rtc_base" ]
+ extra_header = "linux/pipewire_stub_header.fragment"
+ logging_function = "RTC_LOG(LS_VERBOSE)"
+ logging_include = "rtc_base/logging.h"
+ output_name = "linux/pipewire_stubs"
+ path_from_source = "modules/desktop_capture/linux"
+-sigs = [ "linux/pipewire.sigs" ]
++if (rtc_pipewire_version == "0.3") {
++ sigs = [ "linux/pipewire03.sigs" ]
++} else {
++ sigs = [ "linux/pipewire02.sigs" ]
++}
+ }
+ }
+
+@@ -506,6 +530,7 @@ rtc_library("desktop_capture_generic") {
+ absl_deps = [
+ "//third_party/abseil-cpp/absl/memory",
+ "//third_party/abseil-cpp/absl/strings",
++"//third_party/abseil-cpp/absl/types:optional",
+ ]
+
+ if (rtc_use_x11_extensions) {
+@@ -526,20 +551,15 @@ rtc_library("desktop_capture_generic") {
+ sources += [
+ "linux/base_capturer_pipewire.cc",
+ "linux/base_capturer_pipewire.h",
+- "linux/screen_capturer_pipewire.cc",
+- "linux/screen_capturer_pipewire.h",
+-
Bug#1019927: Remove ruby-coffee-script - deprecated upstream
On Fri, 16 Sep 2022 16:38:52 +0530 Pirate Praveen wrote: > As per upstream [1], this project is deprecated and last release was on > Apr 7, 2015 (7 years ago), so I think we should try to remove it from > bookworm, but if we can't get there close to freeze, we can ask for > bookworm-ignore or lower severity. Current list of dependencies (with dependencies removed from ruby-blade and ruby-hamlit): Reverse-Depends === * ruby-jekyll-coffeescript * tdiary-core Reverse-Build-Depends = * ruby-sprockets
Bug#801065: consent unclear
hi, btw, as pointed out on irc: I ment consensus, not consent. :) On Wed, Feb 08, 2023 at 10:36:02AM -0500, Marvin Renich wrote: > > I don't think there has been consent on the issue, thus I'm tagging it > > moreinfo. > > > > I'm also wondering whether to mark this bug as wontfix (until there is > > consent) or to reassign to debian-policy or simply to close it. > > I disagree. Re-reading the messages to the bug report, We have > "strongly support" from Sam Hartman, and "also in favor" from Russ > Allbery and Bill Allombert. > > The only objection was from Henrique de Moraes Holschuh based on lack of > risk assessment from the mistaken impression not only based on that, but way more importantly that this would change *years* of existing practice. > What is being proposed in this bug is simply a change to the Developers > Reference to encourage package maintainers to allow dpkg installation to > succeed even if the service fails to start, unless the package > maintainer has a specific reason to do otherwise. "patches welcome", especially for something which some perceive as simple change! -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ Stop saying that we are all in the same boat. We’re all in the same storm. But we’re not all in the same boat. signature.asc Description: PGP signature
Bug#1022023: xrdp timeout
Seems upstream is discuing to increase the time: https://github.com/neutrinolabs/xrdp/pull/2214 and: https://github.com/neutrinolabs/xrdp/issues/2213
