Bug#1070652: [DRE-maint] Bug#1070652: ruby-json: breaks how-can-i-help
Hi! I am reassigning this bug to the `how-can-i-help` package. Indeed, the script `/usr/bin/how-can-i-help` uses implicitly the OpenStruct class, without requiring explicitly 'ostruct'. The class was loaded transitively from the json gem it seems. Adding below line 35 the following line: require 'ostruct' fixes the bug. Cheers, Cédric Quoting Vincent Lefevre (2024-05-06 17:41:49) > Package: ruby-json > Version: 2.7.2+dfsg-1 > Severity: grave > Justification: renders package unusable > This new ruby-json version breaks how-can-i-help: > [...] > Unpacking ruby-json:amd64 (2.7.2+dfsg-1) over (2.6.3+dfsg-1+b2) ... > Setting up ruby-json:amd64 (2.7.2+dfsg-1) ... > /usr/bin/how-can-i-help:155:in `': uninitialized constant OpenStruct > (NameError) > proxy_uri = $proxy_url.nil? ? OpenStruct.new : URI.parse($proxy_url) > ^^ > -- System Information: > Debian Release: trixie/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, > 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), > (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > Kernel: Linux 6.6.15-amd64 (SMP w/12 CPU threads; PREEMPT) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, > TAINT_UNSIGNED_MODULE > Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > Versions of packages ruby-json depends on: > ii libc6 2.38-7 > ii libruby1:3.1+nmu1 > ii libruby3.1t64 3.1.2-8.3 > ruby-json recommends no packages. > ruby-json suggests no packages. > -- no debconf information--- /tmp/how-can-i-help 2024-05-07 01:08:00.390399139 +0200 +++ /usr/bin/how-can-i-help 2024-05-07 00:59:24.082457226 +0200 @@ -33,6 +33,7 @@ require 'fileutils' require 'time' require 'etc' +require 'ostruct' include Debian
Bug#1069994: systemd-resolved: resolvectl dnssec failed for unsigned domains
Dear Luca Boccassi, Dear Maintainers, On Sun, 28 Apr 2024 11:42:11 +0100 Luca Boccassi wrote: > On Sun, 28 Apr 2024 11:53:17 +0200 Adrien CLERC > wrote: > > Package: systemd-resolved > > Version: 255.5-1 > > Severity: important > > > > Dear Maintainer, > > > > Since 255.5-1, resolvectl produces the following: > > > > ❯ resolvectl query --validate=yes www.youtube.com > > www.youtube.com: resolve call failed: DNSSEC validation failed: no- > signature > > > > The domain is unsigned. It worked in 255.4-1+b1, but I'm unable to > rollback, > > since it depends on libsystemd which makes a lot of package unhappy > with > > dependencies. > > > > Did I miss something? > > In the meantime, I'll use "DNSSEC=no", but that's not a definitive > answer. > > > > Have a nice day, > > Adrien > > > > There are no resolved patches downstream, report this upstream It has been resolved upstream [1] but need backporting for now. I think commits to backports from upstream are: d840783db5208219c78d73b9b46ef5daae9fea0a 5237ffdf2b63a5afea77c3470d9981a2c29643cc 414a9b8e5e1e772261b0ffaedc853f5c0aba5719 which have already been backported in ArchLinux [2]. [1] https://github.com/systemd/systemd/issues/32531 [2] https://gitlab.archlinux.org/archlinux/packaging/packages/systemd/-/blob/main/PKGBUILD?ref_type=heads#L95 -- Cédric Hannotier
Bug#1064843: odoo-16: minor upgrades available
Package: odoo-16 Version: 16.0.0+dfsg.2-2~bpo12+1 Severity: important X-Debbugs-Cc: ced...@villemain.org Dear Maintainer, * What led up to the situation? Evaluating debian native package. * What exactly did you do (or not do) that was effective (or ineffective)? Getting an up to date odoo with open source patches applied. And adding community addons * What was the outcome of this action? Odoo version number is not very clear. 16.0 is current but they have others, see odoo saas: https://www.odoo.com/documentation/16.0/administration/maintain/supported_versions.html Also it's not very clear if OCA/OCB should be used instead. * What outcome did you expect instead? Getting more information about version packaged in debian and policy about upgrade, where to add addons... Maybe outline if it's the relevant package to install for users of odoo community applications. -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-0.deb12.4-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 odoo-16 depends on: ii adduser 3.134 ii fonts-dejavu-core 2.37-6 ii fonts-font-awesome5.0.10+really4.7.0~dfsg-4.1 ii fonts-freefont-ttf20120503-10 ii fonts-glyphicons-halflings1.009~3.4.1+dfsg-3 ii fonts-inconsolata 001.010-6 ii fonts-noto-core 20201225-1 ii fonts-ocr-b 0.3~dfsg1-1 ii fonts-roboto-unhinted 2:0~20170802-3 ii gsfonts 2:20200910-7 ii init-system-helpers 1.65.2 ii libjs-jquery 3.6.1+dfsg+~3.5.14-1 ii libjs-jquery-form 12-4 ii libjs-underscore 1.13.4~dfsg+~1.11.4-3 ii postgresql-client-10 [postgresql-client] 10.23-3.pgdg120+1 ii postgresql-client-11 [postgresql-client] 11.22-2.pgdg120+1 ii postgresql-client-12 [postgresql-client] 12.18-1.pgdg120+1 ii postgresql-client-13 [postgresql-client] 13.14-1.pgdg120+1 ii postgresql-client-14 [postgresql-client] 14.11-1.pgdg120+1 ii postgresql-client-15 [postgresql-client] 15.6-1.pgdg120+1 ii postgresql-client-16 [postgresql-client] 16.2-1.pgdg120+1 ii python3 3.11.2-1+b1 ii python3-babel 2.10.3-1 ii python3-chardet 5.1.0+dfsg-2 ii python3-cryptography 38.0.4-3 ii python3-dateutil 2.8.2-2 ii python3-decorator 5.1.1-3 ii python3-docutils 0.19+dfsg-6 ii python3-freezegun 1.2.1+actually1.2.1-1 ii python3-gevent22.10.2-3 ii python3-greenlet 2.0.2-1 ii python3-idna 3.3-1 ii python3-jinja23.1.2-1 ii python3-libsass 0.22.0-1 ii python3-lxml 4.9.2-1+b1 ii python3-markupsafe2.1.2-1+b1 ii python3-num2words 0.5.10-2 ii python3-ofxparse 0.21-2 ii python3-openssl 23.0.0-1 ii python3-passlib 1.7.4-3 ii python3-pil 9.4.0-1.1+b1 ii python3-polib 1.1.1-1 ii python3-psutil5.9.4-1+b1 ii python3-psycopg2 2.9.9-1.pgdg120+1 ii python3-pydot 1.4.2-1 ii python3-pypdf22.12.1-3+deb12u1 ii python3-qrcode7.4.2-2 ii python3-renderpm 3.6.12-1+b1 ii python3-reportlab 3.6.12-1 ii python3-requests 2.28.1+dfsg-1 ii python3-serial3.5-1.1 ii python3-stdnum1.18-1 ii python3-tz2022.7.1-4 ii python3-urllib3 1.26.12-1 ii python3-usb 1.2.1-2 ii python3-vobject 0.9.6.1-2 ii python3-werkzeug 2.2.2-3 ii python3-xlrd 1.2.0-3 ii python3-xlsxwriter3.0.2-2 ii python3-xlwt 1.3.0-4 ii python3-zeep 4.2.1-1 ii wkhtmltopdf
Bug#1054749: ruby-android-key-attestation: bug in ruby-pry-byebug 3.9.0, fixed in 3.10.1
Package: ruby-android-key-attestation Followup-For: Bug #1054749 Hi, This bug is in fact in ruby-pry-byebug, version v3.9.0-1. It was fixed by the upload of 3.10.1-1. This is a duplicate of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054737 signature.asc Description: PGP signature
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",
Bug#1027867: Bug#1028439: Unable to run X server since 22.3.1-1 upgrade
Same result with 23.0.0~rc1-1 Le ven. 20 janv. 2023 à 15:18, Fabio Pedretti a écrit : > Can you also check with 23.0.0~rc1-1 in experimental? > > Il giorno mer 18 gen 2023 alle ore 16:48 Cédric Nisio > ha scritto: > > > > As I answered on gitlab I tried 22.3.3-1 with the same backtrace & error > logs. > > I rolled back to 22.2.4-1. > > > > Happy to help if I can. >
Bug#1027867: Unable to run X server since 22.3.1-1 upgrade
As I answered on gitlab I tried 22.3.3-1 with the same backtrace & error logs. I rolled back to 22.2.4-1. Happy to help if I can. Le mer. 18 janv. 2023 à 15:28, < deb-bug.oluj0xj403ou050siy9dp...@qmail.sunbirdgrove.com> a écrit : > 22.3.3-1 works here! > > But the upstream bug is unanswered still: > https://gitlab.freedesktop.org/mesa/mesa/-/issues/8007. > And there's another guy who did the same to no avail. It's not fixed for > everyone. If we want to fix it for all, why not just revert it globally > now, until the cause has been found? Who knows how long that'll take. > > The laptop I can personally test on is rather average. (intel UHD630, some > unused nv card, nouveau is blacklisted for energy savings, and the busses > removed via udev) If someone has an idea how to debug this that does not > eat all day, I'd help possibly diff to find out why it works here, and not > for him. > > > Side note: I received 2 mails, one triggered directly by you, another from > being subscribed to the bug. The latter fails DKIM. If this is unintended, > we might want to tell the postmaster. > > January 18, 2023 10:25 AM, "Fabio Pedretti" > wrote: > > > Can you check with 22.3.3-1 (now in testing) or 23.0.0~rc1-1 (in > > experimental) if the issue is fixed or still not? >
Bug#1028403: wtype: descriptions refers to the 'wdotool' name instead of wtype
Package: wtype Version: 0.4-2 Severity: minor Dear Maintainer, Looking at the description of the package, I see that it mentions 'wdotool', whereas the package and the tool under /usr/bin are called wtype, and there is no indication of wdotool. Thanks for maintaing that tool! Best wishes, Cédric signature.asc Description: PGP signature
Bug#1027791: Unable to run X server since 22.3.1-1 upgrade
Package: libgl1-mesa-dri Version: 22.3.1-1 After upgrading libgl1-mesa-dri from 22.2.4-1 to 22.3.1-1 X server won’t start (both X.org & Wayland). On startup I just get a black screen with a blinking caret. Still I can access ttys Here are the gdm-x-session logs from journalctl (II) modeset(0): Output eDP-1 connected (II) modeset(0): Output DP-1 disconnected (II) modeset(0): Output DP-2 disconnected (II) modeset(0): Output DP-3 connected (II) modeset(0): Using spanning desktop for initial modes (II) modeset(0): Output eDP-1 using initial mode 1920x1080 +0+0 (II) modeset(0): Output DP-3 using initial mode 2560x1440 +1920+0 (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0) (==) modeset(0): DPI set to (96, 96) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Module "fb" already built-in (==) modeset(G0): Depth 24, (==) framebuffer bpp 32 (==) modeset(G0): RGB weight 888 (==) modeset(G0): Default visual is TrueColor (II) Loading sub module "glamoregl" (II) LoadModule: "glamoregl" (II) Loading /usr/lib/xorg/modules/libglamoregl.so (II) Module glamoregl: vendor="X.Org Foundation" compiled for 1.21.1.5, module version = 1.0.1 ABI class: X.Org ANSI C Emulation, version 0.4 nvc0_screen_create:1072 - Base screen init failed: -19 (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55c156406cc9] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x40) [0x7f2b6165af90] (EE) 2: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x4406c) [0x7f2b5f95935c] (EE) 3: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x1e4c9) [0x7f2b5f9337b9] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x266) [0x7f2b5f915556] (EE) unw_get_proc_name failed: no unwind info found [-10] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7f2b5f0aaf56] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_d3d12+0x60aec4) [0x7f2b5f6b63e4] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_d3d12+0x1a93) [0x7f2b5f0acfb3] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_d3d12+0xa175) [0x7f2b5f0b5695] (EE) 9: /lib/x86_64-linux-gnu/libgbm.so.1 (gbm_format_get_name+0xf2e) [0x7f2b60d29eae] (EE) 10: /lib/x86_64-linux-gnu/libgbm.so.1 (gbm_format_get_name+0x16f8) [0x7f2b60d2a678] (EE) unw_get_proc_name failed: no unwind info found [-10] (EE) 11: /lib/x86_64-linux-gnu/libgbm.so.1 (?+0x0) [0x7f2b60d2874c] (EE) 12: /lib/x86_64-linux-gnu/libgbm.so.1 (gbm_create_device+0x44) [0x7f2b60d28884] (EE) 13: /usr/lib/xorg/modules/libglamoregl.so (glamor_egl_init+0x61) [0x7f2b60d533c1] (EE) unw_get_proc_name failed: no unwind info found [-10] (EE) 14: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f2b60d8c733] (EE) 15: /usr/lib/xorg/Xorg (InitOutput+0xa2a) [0x55c1562d657a] (EE) 16: /usr/lib/xorg/Xorg (InitFonts+0x1ce) [0x55c1562974de] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x8a) [0x7f2b6164618a] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x85) [0x7f2b61646245] (EE) 19: /usr/lib/xorg/Xorg (_start+0x21) [0x55c156280b71] (EE) (EE) Segmentation fault at address 0x20 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation fault). Server aborting (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/lib/gdm3/.local/share/xorg/Xorg.0.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. Unable to run X server I was able to workaround the issue by reverting to libgl1-mesa-dri=22.2.4-1 I had to find an outdated repository as it is already gone from official repository which is not very handy. $ uname -a Linux debian 6.0.0-6-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.12-1 (2022-12-09) x86_64 GNU/Linux as it is related to drivers I guess some hw info could be useful: $ lspci 00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 07) 00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 07) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10) 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10) 00:15.0 Serial bus controller: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #0 (rev 10) 00:15.1 Serial bus controller: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #1 (rev 10) 00:16.0
Bug#1026821: python-matplotlib-doc: Broken search functionality
Package: python-matplotlib-doc Version: 3.5.2-4 Severity: normal Dear Maintainer, Search does not work anymore. It fails with the following message: ``` Uncaught ReferenceError: SPHINX_HIGHLIGHT_ENABLED is not defined at Object.query (searchtools.js:279) at Object.performSearch (searchtools.js:238) at HTMLDocument.init (searchtools.js:179) ``` Rebuilding the package solves the issue. IMO, its due to the major version bump of libjs-sphinxdoc. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-5-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python-matplotlib-doc depends on: ii libjs-jquery 3.6.1+dfsg+~3.5.14-1 ii libjs-sphinxdoc 5.3.0-2 python-matplotlib-doc recommends no packages. python-matplotlib-doc suggests no packages. -- no debconf information -- Cédric Hannotier
Bug#1017524: [DRE-maint] Bug#1017524: status?
Hi, I recently looked at failures in jekyll. Jekyll is broken in several ways in unstable due to version constraints on the dependencies. One can easily relax the version dependency on mercenary in the gemdeps (no changes needed). One would need a newer version of jekyll to fix most of them. But the blocking point seems that even the latest jekyll release requires ruby-liquid < 5, whereas we have 5.4. There is some issue opened upstream to try to use liquid 5.x, https://github.com/jekyll/jekyll/issues/9094 but there are some missing pieces... Not being a user of jekyll myself, I could not test yet if the code in jekyll indicated in this issue is enough to make it work with liquid 5.x, if we simply relax the version dependency in gemdeps. Cheers, Cédric
Bug#1024204: imv: typo in description
Package: imv Version: 4.3.0-1.1+b2 Severity: minor Dear Maintainer, The package indicates two executables in the second paragraph: `imv-x11` and `x11-wayland`. The second one should be `imv-wayland`. Thanks! Best, Cédric signature.asc Description: PGP signature
Bug#1021262: failing test disabled in 0.2.21-2
Hi, I disabled the failing test on all arches except amd64 on 0.2.21-2, until the issue is fixed upstream. Since the package now builds, and other tests are passing, I am changing the severity of the bug to 'normal'. Thanks, Cédric signature.asc Description: signature
Bug#1016272: transient bug in latex
This bug seems caused by a transient bug due to a non-UTF8 character in
one of the included files by latex(?). This problem was present with
texlive-latex-base 2022.20220722-1, but after the recent upgrade to
2022.20220923-1, the problem has disappeared, and all tests pass.
For the record, please find attached one of the latex files produced
with kramdown which was causing the problematic character, together with
the output of the failing compilation log with latex from
texlive-latex-base/2022.20220722-1, and the succeeding compilation with
texlive-latex-base/2022.20220923-1.
Best wishes,
Cédric
\documentclass{scrartcl}
\usepackage[utf8x]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{listings}
\usepackage{hyperref}
\setcounter{footnote}{0}
\hypersetup{colorlinks=true,urlcolor=blue}
\begin{document}
This is a % simple
paragraph.
This is a % simple
paragraph.
This is a % simple {:/other} paragraph
.
This is a paragraph.
This is a \{:/comment\} simple \{:/\} paragraph.
This is a \{::comment\} paragraph.
\end{document}
This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Debian)
(preloaded format=latex)
restricted \write18 enabled.
entering extended mode
(./latex.tex
LaTeX2e <2022-06-01> patch level 5
L3 programming layer <2022-07-15>
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrartcl.cls
Document Class: scrartcl 2022/07/04 v3.37 KOMA-Script document class (article)
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrkbase.sty
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrbase.sty
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlfile.sty
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlfile-hook.sty
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlogo.sty)))
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)))
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/tocbasic.sty)
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrsize11pt.clo)
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/typearea.sty))
(/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
(/usr/share/texlive/texmf-dist/tex/latex/ucs/utf8x.def))
(/usr/share/texlive/texmf-dist/tex/latex/ucs/ucs.sty
(/usr/share/texlive/texmf-dist/tex/latex/ucs/data/uni-global.def))
(/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty)
(/usr/share/texlive/texmf-dist/tex/latex/listings/listings.sty
(/usr/share/texlive/texmf-dist/tex/latex/listings/lstmisc.sty)
(/usr/share/texlive/texmf-dist/tex/latex/listings/listings.cfg))
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
(/usr/share/texlive/texmf-dist/tex/generic/ltxcmds/ltxcmds.sty)
(/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty)
(/usr/share/texlive/texmf-dist/tex/generic/pdftexcmds/pdftexcmds.sty
(/usr/share/texlive/texmf-dist/tex/generic/infwarerr/infwarerr.sty))
(/usr/share/texlive/texmf-dist/tex/generic/kvsetkeys/kvsetkeys.sty)
(/usr/share/texlive/texmf-dist/tex/generic/kvdefinekeys/kvdefinekeys.sty)
(/usr/share/texlive/texmf-dist/tex/generic/pdfescape/pdfescape.sty)
(/usr/share/texlive/texmf-dist/tex/latex/hycolor/hycolor.sty)
(/usr/share/texlive/texmf-dist/tex/latex/letltxmacro/letltxmacro.sty)
(/usr/share/texlive/texmf-dist/tex/latex/auxhook/auxhook.sty)
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/nameref.sty
(/usr/share/texlive/texmf-dist/tex/latex/refcount/refcount.sty)
(/usr/share/texlive/texmf-dist/tex/generic/gettitlestring/gettitlestring.sty
(/usr/share/texlive/texmf-dist/tex/latex/kvoptions/kvoptions.sty)))
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def)
(/usr/share/texlive/texmf-dist/tex/generic/intcalc/intcalc.sty)
(/usr/share/texlive/texmf-dist/tex/generic/etexcmds/etexcmds.sty)
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/puenc.def)
(/usr/share/texlive/texmf-dist/tex/latex/url/url.sty)
(/usr/share/texlive/texmf-dist/tex/generic/bitset/bitset.sty
(/usr/share/texlive/texmf-dist/tex/generic/bigintcalc/bigintcalc.sty))
(/usr/share/texlive/texmf-dist/tex/latex/base/atbegshi-ltx.sty))
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/hdvips.def
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/pdfmark.def
(/usr/share/texlive/texmf-dist/tex/latex/rerunfilecheck/rerunfilecheck.sty
(/usr/share/texlive/texmf-dist/tex/latex/base/atveryend-ltx.sty)
(/usr/share/texlive/texmf-dist/tex/generic/uniquecounter/uniquecounter.sty
(/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-dvips.def)
No file latex.aux.
(/usr/share/texlive/texmf-dist/tex/latex/ucs/ucsencs.def)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/color.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg)
(/usr/share/texlive/texmf-dist/tex/latex/graphics-def/dvips.def)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/dvipsnam.def)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/mathcolor.ltx))
Package hyperref Warning: Rerun to get /PageLabels entry.
(/usr/share/texlive/texmf-dist/tex/latex/bookmark/bookmark.sty
(/usr/share/texlive/texmf-di
Bug#1021257: imagemagick-6.q16: import renders X unresponsive
Package: imagemagick-6.q16 Version: 8:6.9.11.60+dfsg-1.3+b3 Severity: important Dear Maintainer, Using import (symlink to import-im6.q16) freezes the whole X session. Only exit door is to go to another tty and kill the process. Steps: $ import my_file_name -- Package-specific info: ImageMagick program version --- animate: ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org compare: ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org convert: ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org composite: ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org conjure: ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org display: ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org identify: ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org import: ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org mogrify: ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org montage: ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org stream: ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.19.0-1-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages imagemagick-6.q16 depends on: ii hicolor-icon-theme 0.17-2 ii libc6 2.35-1 ii libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.3+b3 ii libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.3+b3 Versions of packages imagemagick-6.q16 recommends: ii ghostscript 9.56.1~dfsg-1 pn libmagickcore-6.q16-6-extra ii netpbm 2:10.97.00-2 Versions of packages imagemagick-6.q16 suggests: pn autotrace ii cups-bsd [lpr] 2.4.2-1+b1 ii curl 7.85.0-1 pn enscript ii ffmpeg 7:5.1.2-1 ii fig2dev [transfig] 1:3.2.8b-3 ii gimp 2.10.32-1+b1 pn gnuplot pn grads ii graphviz 2.42.2-7 ii groff-base 1.22.4-8 pn hp2xx pn html2ps pn imagemagick-doc ii libwmf-bin 0.2.12-5 pn mplayer pn povray pn radiance ii sane-utils 1.1.1-5 ii texlive-binaries [texlive-base-bin] 2022.20220321.62855-4 pn ufraw-batch ii xdg-utils1.1.3-4.1 -- no debconf information -- Cédric Hannotier
Bug#1019238: fixed in redmine 5.0.2-1
I do agree with Paolo the ticket should stay open. Because the only way fix the issue right now is to disable security updates: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019238#10
Bug#1005833: [DRE-maint] Bug#1005833: src:ruby-redis: fails to migrate to testing for too long: autopkgtest regression
Quoting Paul Gevers (2022-03-21 21:13:29) > Is there any progress on this issue? Is no progress is there another way > to move the problem forward? E.g. revert ruby-redis to the previous > version if redis and fakeredis can agree on the change in behavior? I am preparing an upload of ruby-fakeredis with an upstream PR accomodating the fact that 'exists' returns now an integer, plus some modifications of the test suite. This should fix the issue. Best wishes, Cédric
Bug#1006042: Processed: fixed 1006042 in 0.2.0-1
Dear Sandro Quoting Sandro Tosi (2022-02-23 18:14:41) > are you sure this is correct? rich never had a 0.2.0-1 upload Sorry, I messed up when copying with my big fingers another bug number. Thank you for noticing, and apologies for the noise. Best wishes, Cédric signature.asc Description: signature
Bug#1002115: bug in texlive?
I suspect this is caused by a change in texlive.
Here is the diff for the list of packages used in tests in ci.debian.net
between the last green and the (almost) first red:
--- kramdown-ok 2022-01-26 14:35:12.162946913 +0100
+++ kramdown-nok2022-01-26 14:35:21.802998157 +0100
@@ -1,7 +1,7 @@
fontconfig-config 2.13.1-4.2
fonts-dejavu-core 2.37-2
fonts-lmodern 2.004.5-6.1
-gem2deb-test-runner1.7
+gem2deb-test-runner1.8
kramdown 2.3.1-3
libapache-pom-java 18-1
libbrotli1 1.0.9-2+b3
@@ -11,7 +11,7 @@
libfontbox-java1:1.8.16-2
libfontconfig1 2.13.1-4.2
libfreetype6 2.11.0+dfsg-1
-libglib2.0-0 2.70.1-1
+libglib2.0-0 2.70.2-1
libgraphite2-3 1.3.14-1
libharfbuzz0b 2.7.4-1
libice62:1.0.10-1
@@ -70,13 +70,13 @@
rubygems-integration 1.18
t1utils1.41-4
tex-common 6.17
-texlive-base 2021.20210921-1
+texlive-base 2021.20211127-1
texlive-binaries 2021.20210626.59705-1
-texlive-fonts-recommended 2021.20210921-1
-texlive-latex-base 2021.20210921-1
-texlive-latex-extra2021.20210921-1
-texlive-latex-recommended 2021.20210921-1
-texlive-pictures 2021.20210921-1
+texlive-fonts-recommended 2021.20211127-1
+texlive-latex-base 2021.20211127-1
+texlive-latex-extra2021.20211127-1
+texlive-latex-recommended 2021.20211127-1
+texlive-pictures 2021.20211127-1
tidy 2:5.6.0-11
x11-common 1:7.7+23
xdg-utils 1.1.3-4.1
The test failure comes from the filtering of the latex output. Removing
the 'scan and join' part works around the issue.
diff --git a/test/test_files.rb b/test/test_files.rb
index 7e2ccad..bc5523a 100644
--- a/test/test_files.rb
+++ b/test/test_files.rb
@@ -150,7 +150,7 @@ class TestFiles < Minitest::Test
io.close_write
io.read
end
- assert($?.exitstatus == 0, result.scan(/^!(.*\n.*)/).join("\n"))
+ assert($?.exitstatus == 0, result)
end
end
end
signature.asc
Description: PGP signature
Bug#1004299: ruby-net-ssh: FTBFS in sid
Package: ruby-net-ssh Version: 1:6.1.0-2 Hi, When trying to rebuild ruby-net-ssh in sid, I get test failures related to DSA cryptography. They all have the message: OpenSSL:PKey::DSAError: bad sig size Hopefully, this is the relevant part. Full log attached Finished in 4.013999s, 372.1974 runs/s, 1244.6442 assertions/s. 1) Error: Authentication::TestAgent#test_add_dsa_cert_identity: OpenSSL::PKey::DSAError: bad sig size /<>/lib/net/ssh/transport/openssl.rb:115:in `ssh_do_sign' /<>/lib/net/ssh/authentication/certificate.rb:91:in `sign!' /<>/test/authentication/test_agent.rb:414:in `make_cert' /<>/test/authentication/test_agent.rb:273:in `test_add_dsa_cert_identity' 2) Error: Authentication::TestKeyManager#test_each_identity_should_load_from_implicit_cert_file: OpenSSL::PKey::DSAError: bad sig size /<>/lib/net/ssh/transport/openssl.rb:115:in `ssh_do_sign' /<>/lib/net/ssh/authentication/certificate.rb:91:in `sign!' /<>/test/authentication/test_key_manager.rb:320:in `rsa_cert' /<>/test/authentication/test_key_manager.rb:76:in `test_each_identity_should_load_from_implicit_cert_file' 3) Error: Authentication::TestKeyManager#test_each_identity_should_ignore_explicit_cert_file_unless_matching_key_is_avaiable: OpenSSL::PKey::DSAError: bad sig size /<>/lib/net/ssh/transport/openssl.rb:115:in `ssh_do_sign' /<>/lib/net/ssh/authentication/certificate.rb:91:in `sign!' /<>/test/authentication/test_key_manager.rb:320:in `rsa_cert' /<>/test/authentication/test_key_manager.rb:104:in `test_each_identity_should_ignore_explicit_cert_file_unless_matching_key_is_avaiable' 4) Error: Authentication::TestKeyManager#test_each_identity_should_load_from_explicit_cert_file_given_matching_key_is_loaded: OpenSSL::PKey::DSAError: bad sig size /<>/lib/net/ssh/transport/openssl.rb:115:in `ssh_do_sign' /<>/lib/net/ssh/authentication/certificate.rb:91:in `sign!' /<>/test/authentication/test_key_manager.rb:320:in `rsa_cert' /<>/test/authentication/test_key_manager.rb:88:in `test_each_identity_should_load_from_explicit_cert_file_given_matching_key_is_loaded' 5) Error: Authentication::TestKeyManager#test_each_identity_should_match_explicit_keycert_with_agent_provided_identity: OpenSSL::PKey::DSAError: bad sig size /<>/lib/net/ssh/transport/openssl.rb:115:in `ssh_do_sign' /<>/lib/net/ssh/authentication/certificate.rb:91:in `sign!' /<>/test/authentication/test_key_manager.rb:320:in `rsa_cert' /<>/test/authentication/test_key_manager.rb:141:in `test_each_identity_should_match_explicit_keycert_with_agent_provided_identity' 6) Error: Authentication::TestKeyManager#test_sign_with_agent_originated_key_should_be_signable_through_explicitly_loaded_cert: OpenSSL::PKey::DSAError: bad sig size /<>/lib/net/ssh/transport/openssl.rb:115:in `ssh_do_sign' /<>/lib/net/ssh/authentication/certificate.rb:91:in `sign!' /<>/test/authentication/test_key_manager.rb:320:in `rsa_cert' /<>/test/authentication/test_key_manager.rb:218:in `test_sign_with_agent_originated_key_should_be_signable_through_explicitly_loaded_cert' 1494 runs, 4996 assertions, 0 failures, 6 errors, 0 skips rake aborted! Command failed with status (1): [ruby -w /usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb "test/test_all.rb" "test/test_buffer.rb" "test/test_buffered_io.rb" "test/test_config.rb" "test/test_key_factory.rb" "test/test_known_hosts.rb" "test/test_proxy_jump.rb" -v] /usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `' Tasks: TOP => default (See full trace by running task with --trace) ERROR: Test "ruby3.0" failed. Exiting. dh_auto_install: error: dh_ruby --install /<>/debian/ruby-net-ssh returned exit code 1 make: *** [debian/rules:7: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Source: ruby-net-ssh Version: 1:6.1.0-2 Severity: serious Tags: ftbfs Justification: fails to build from source 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 unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-3-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr:en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled ruby-net-ssh_6.1.0-2_amd64-2022-01-24T13:24:15Z.build.gz Description: application/gzip signature.asc Description: signature
Bug#946683: nokogumbo has been merged into nokogiri
Hi, It seems that since nokogiri 1.12, the functionalities of nokogumbo have been merged into nokogiri. html-proofer does not depend on nokogumbo anymore, and uses nokogiri >=1.12. It seems reasonable to upgrade nokogiri (I am trying to do it), make all packages depending on ruby-nokogumbo to switch to nokogiri if it is not already the case, and then remove nokogumbo. Best wishes, Cédric signature.asc Description: signature
Bug#892058: thanks for the reminder
> This is a courtesy reminder that your Debian key is expiring on 2022-01-20. > [...] > If you like this service, please leave a favorable comment here [2]. Thanks Felix Lechner for the reminder about the expiration of my GPG key approaching. I found it very useful! Best wishes, Cédric signature.asc Description: signature
Bug#1000683: RFP: wxMathPlot -- library to add 2D scientific plot functionality to wxWidgets
Package: wnpp Severity: wishlist URL: https://wxmathplot.sourceforge.io/ License: wxWindows license Description: wxMathPlot is a library to add 2D scientific plot functionality to wxWidgets. It allows to embed inside your program a window for plotting scientific, statistical or mathematical data, with additions like legend or coordinate display in overlay.
Bug#996386: other error with mechanize 2.7.7-3
The error in the log comes from ruby-mechanize < 2.7.7-3 not depending
on ruby-webrick.
Now, there are 7 test failures of the following kind:
> 1) ShamRack mounted Rack application can be accessed using open-uri
> Failure/Error: response = open("http://www.greetings.com;)
>
> Errno::ENOENT:
>No such file or directory @ rb_sysopen - http://www.greetings.com
> # ./spec/sham_rack_spec.rb:42:in `initialize'
> # ./spec/sham_rack_spec.rb:42:in `open'
> # ./spec/sham_rack_spec.rb:42:in `block (3 levels) in '
>
> 2) ShamRack.at with a block mounts associated block as an app
> Failure/Error: expect(open("http://simple.xyz;).read).to eq("Easy, huh?")
>
> Errno::ENOENT:
>No such file or directory @ rb_sysopen - http://simple.xyz
> # ./spec/sham_rack_spec.rb:76:in `initialize'
> # ./spec/sham_rack_spec.rb:76:in `open'
> # ./spec/sham_rack_spec.rb:76:in `block (4 levels) in '
log attached.
Cheers,
Cédricsbuild (Debian sbuild) 0.81.2 (31 January 2021) on kashan
+==+
| ruby-sham-rack 1.4.1-2 (amd64) Thu, 18 Nov 2021 00:00:33 + |
+==+
Package: ruby-sham-rack
Version: 1.4.1-2
Source Version: 1.4.1-2
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: full
I: NOTICE: Log filtering will replace
'var/run/schroot/mount/unstable-amd64-sbuild-7945e2af-3685-497b-8e1b-182c61bf38b0'
with '<>'
I: NOTICE: Log filtering will replace
'build/ruby-sham-rack-hdLhOr/resolver-A62XUh' with '<>'
+--+
| Update chroot|
+--+
Get:1 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./ InRelease
Ign:1 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./ InRelease
Get:2 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./ Release
[951 B]
Get:2 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./ Release
[951 B]
Get:3 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./
Release.gpg
Ign:3 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./
Release.gpg
Get:4 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./ Packages
[659 B]
Get:5 http://deb.debian.org/debian unstable InRelease [165 kB]
Err:4 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./ Packages
Could not open file
/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive/./Packages - open (13:
Permission denied)
Get:4 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./ Packages
[1084 B]
Get:6 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB]
Ign:6 http://deb.debian.org/debian unstable/main Sources.diff/Index
Get:7 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index
[63.6 kB]
Ign:7 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index
Get:8 http://deb.debian.org/debian unstable/main Sources [9378 kB]
Get:9 http://deb.debian.org/debian unstable/main amd64 Packages [8838 kB]
Fetched 18.5 MB in 2s (8057 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages were automatically installed and are no longer required:
fontconfig-config fonts-dejavu-core libbrotli1 libbsd0 libc-devtools
libdeflate0 libexpat1 libfontconfig1 libfreetype6 libgd3 libjbig0
libjpeg62-turbo libmd0 libpng16-16 libtiff5 libwebp6 libx11-6 libx11-data
libxau6 libxcb1 libxdmcp6 libxpm4 manpages manpages-dev sensible-utils ucf
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
libsemanage2 libsepol2
The following packages will be upgraded:
apt bash binutils binutils-common binutils-x86-64-linux-gnu coreutils cpp-10
dash debconf g++-10 gcc-10 gcc-10-base libapt-pkg6.0 libbinutils
libcrypt-dev libcrypt1 libctf-nobfd0 libctf0 libdebconfclient0 libexpat1
libgcc-10-dev libgmp10 libjpeg62-turbo libpcre2-8-0 libselinux1
libsemanage-common libsemanage1 libstdc++-10-dev libsystemd0 libtasn1-6
libtinfo6 libudev1 linux-libc-dev login ncurses-base ncurses-bin passwd
tzdata
38 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 35.1 MB/58.4 MB of archives.
After this operation, 980 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian unstable/main amd64 g++-10 amd64 10.3.0-12
[9433 kB]
Get:2 http://deb.debian.org/debian unstable/main amd64 gcc-10 amd64 10.3.0-12
[17.1 MB]
Get:3 http://deb.debian.org/debian unstable/main amd64 cpp-10 amd64 10.3.0-12
[8571 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 35.1 MB
Bug#996125: reassign to ruby-rspec-rails or rails?
The actual part reporting the error seems to be: > An error occurred while loading ./spec/rails/integration/forms_spec.rb. > Failure/Error: require 'rspec/rails' > > ArgumentError: > wrong number of arguments (given 4, expected 3) > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # ./spec/rails/rails_spec_helper.rb:7:in `' > # ./spec/rails/integration/forms_spec.rb:1:in `require' > # ./spec/rails/integration/forms_spec.rb:1:in `' which seems to be a duplicate of #996377. So it probably has to be merged with that one. signature.asc Description: signature
Bug#996477: E1208: -complete used without allowing arguments
Package: vim-tlib Version: 1.27-5 Severity: normal Tags: upstream Dear maintainer, Since a recent upgrade of vim, the tlib plugin is issuing an error when launching vim: Error detected while processing /var/lib/vim/addons/plugin/02tlib.vim: line 77: E1208: -complete used without allowing arguments This error has been reported upstream, and is not present anymore in more recent version of the plugin. Could you please update the package to a more recent version? Thank you in advance! -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 vim-tlib depends on: ii vim2:8.2.3455-2 ii vim-addon-manager 0.5.10 ii vim-gtk3 [vim] 2:8.2.3455-2 vim-tlib recommends no packages. vim-tlib suggests no packages. -- no debconf information
Bug#984858: python-numpy-doc: numpy doc search results broken by appending "undefined"
On Tue, 09 Mar 2021 10:15:52 +0100 Drew Parsons wrote: > The local numpy docs at /usr/share/doc/python-numpy-doc/html/index.html > provide a search window. Search does work, but the result links are > borken. > > For instance, search for norm, finds 76 pages of results, the first > being "numpy.linalg.norm (Python function, in numpy.linalg.norm)" > The url link for this result is > file:///usr/share/doc/python-numpy-doc/html/reference/generated/numpy.linalg.normundefined?highlight=norm#numpy.linalg.norm > > The "undefined" suffix at the end of the filepath of course means the > link does not work. The actual file is > file:///usr/share/doc/python-numpy-doc/html/reference/generated/numpy.linalg.norm.html > > The tags on the search url do work if applied to the correct filepath, as in > file:///usr/share/doc/python-numpy-doc/html/reference/generated/numpy.linalg.norm.html?highlight=norm > > Something in the search engine is replacing '.html' with 'undefined'. It is because the sphinx builder seems to do something wrong when building the search.html file... DIR=/usr/share/doc/python-numpy-doc/html in $DIR/_static/searchtools.js line 268, the script generates links using this: ``` linkUrl = item[0] + DOCUMENTATION_OPTIONS.LINK_SUFFIX; ``` The issue is that, somehow, the `DOCUMENTATION_OPTIONS` is defined in $DIR/search.html, and does not contain a `LINK_SUFFIX` parameter (-> undefined). >From numpy doc website, they use this instead: ``` ``` Dirty workaround is to comment the definition of `DOCUMENTATION_OPTIONS` in search.html and add this line, or add `LINK_SUFFIX: '.html'` to its definition. Sadly, I do not have any knowledge on Sphinx build to properly fix it. Regards -- Cédric Hannotier
Bug#993829: Please ship nokogiri.h header file
Hi Daniel, Le Sun, Sep 19, 2021 at 10:13:59PM +0200, Daniel Leidert a écrit : > Am Sonntag, dem 19.09.2021 um 17:31 +0200 schrieb Cédric Boutillier: > > I have been looking at the bugs on ruby-nokogiri before trying to update > > it to the new upstream version. > > > > Using the gem install layout is not enough to have the > > ext/nokogiri/nokogiri.h installed. As I understand it, gem_installer.rb > > in gem2deb is removing all sources from the ext/ directory. Actually, I pushed a couple of commits today to fix that: I changed the 'gemspec' target of debian/rules slightly to call a Ruby script filtering non-needed dependencies and the ports/* and patches/* parts of the files metadata. Removing the ports/* from the list of files fixed the gem install layout part. Remains the question about where to put the header file (in the gem install layout context). > RUBYHDRDIR (/usr/include/ruby-) > SITEHDRDIR (/usr/include/ruby-/site_ruby) > VENDORHDRDIR (/usr/include/ruby-/vendor_ruby) In the context of an installation under vendor_ruby, I would go for VENDORHDRDIR, although I would have hoped for a path which does not depend on the ruby version. Best wishes, Cédric signature.asc Description: PGP signature
Bug#993829: Please ship nokogiri.h header file
Hi, I have been looking at the bugs on ruby-nokogiri before trying to update it to the new upstream version. Using the gem install layout is not enough to have the ext/nokogiri/nokogiri.h installed. As I understand it, gem_installer.rb in gem2deb is removing all sources from the ext/ directory. So my questions are: - should we modify gem2deb to allow for installation of headers file? (at least maybe the ones added to the WHITELIST) - if so, should we install them, as the gem command does, in the /usr/lib/ruby/gems/x.y.z/gems/package-a.b.c/ext subdirectory? OR - would it make sense for nokogumbo to use instead Built-Using: to use the nokogiri.h present in the source package? what would be the best strategy for this situation? Best wishes, Cédric signature.asc Description: PGP signature
Bug#993739: blends-common: tempfile has to be replaced by mktemp
Hi Andreas,
I have submitted a merge request on salsa
https://salsa.debian.org/blends-team/blends/-/merge_requests/8
applying the patch attached.
Best wishes,
Cédric
>From e555f8405ea4e2cf90a8d50261545665ab49605c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?C=C3=A9dric=20Boutillier?=
Date: Wed, 8 Sep 2021 12:14:02 +0200
Subject: [PATCH] Replace deprecated temfile by mktemp
debianutils 5.x removed the script `tempfile`, which has to be replaced
by `mktemp` from the coreutils package.
---
debian/changelog | 5 +
share/blends/unixgroups/blend-actions | 2 +-
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/debian/changelog b/debian/changelog
index 88c3aa1..d0f823d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,7 +1,12 @@
blends (0.7.4) UNRELEASED; urgency=medium
+ [ Gianfranco Costamagna ]
* Add Ubuntu disco and eoan sources.list files
+ [ Cédric Boutillier ]
+ * Replace deprecated `tempfile` by `mktemp` in blend-actions script (Closes:
+#993739)
+
-- Gianfranco Costamagna Fri, 14 Jun 2019 00:58:11 +0200
blends (0.7.3) experimental; urgency=medium
diff --git a/share/blends/unixgroups/blend-actions b/share/blends/unixgroups/blend-actions
index 2b12a50..9452d54 100644
--- a/share/blends/unixgroups/blend-actions
+++ b/share/blends/unixgroups/blend-actions
@@ -126,7 +126,7 @@ getAllUsers() {
RET=64 # EX_USAGE
else
SIMPLE=$1
- TMPFILE=`tempfile`
+ TMPFILE=`mktemp`
(IFS=":"
while read user pass uid gid name rest ; do
if [ "$uid" != "" ] ; then
--
2.33.0
Bug#993739: blends-common: tempfile has to be replaced by mktemp
Package: blends-common Version: 0.7.2 Followup-For: Bug #993739 Hi I have just experienced this bug today too. According to the NEWS.Debian file in debianutils package, the `tempfile` script was removed from debianutils in the version 5.0. Therefore, its usage in /usr/share/blends/unixgroups/blend-actions should indeed be replaced by mktemp from coreutils. Best wishes, Cédric
Bug#991155: fixed in neovim 0.5.0-1
Hi James, On Tue, 10 Aug 2021 03:48:30 + Debian FTP Masters wrote: > We believe that the bug you reported is fixed in the latest version of > neovim, which is due to be installed in the Debian FTP archive. Release 0.5.0-1 did not successfully build on a significant number of arch, and especially amd64. Could you reconsider ? Regards -- Cédric Hannotier
Bug#991461: linux-image-5.10.0-8-armmp: [armhf] PHC not available with driver fec on i.MX6 SoC
Package: src:linux Version: 5.10.46-2 Severity: normal Tags: patch Dear maintainer, With the current Bullseye armhf Linux kernel, the PTP Hardware Clock is not available on the network interface of an i.MX6 SoC managed by the driver 'fec' (CONFIG_FEC). This driver is currently built-in and the Ethernet interface works properly. $ ethtool -i eth0 driver: fec version: 5.10.0-8-armmp firmware-version: expansion-rom-version: bus-info: eth0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: yes supports-priv-flags: no $ ethtool -T eth0 Time stamping parameters for eth0: Capabilities: hardware-transmit software-transmit hardware-receive software-receive software-system-clock hardware-raw-clock PTP Hardware Clock: none Hardware Transmit Timestamp Modes: off on Hardware Receive Filter Modes: none all $ dmesg | fgrep eth0 [ 23.580932] fec 2188000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 23.581001] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready The problem is that the driver 'ptp' (CONFIG_PTP_1588_CLOCK) is built as a module. As a result, the call to function ptp_clock_register() (in file drivers/net/ethernet/freescale/fec_ptp.c, line 631) effectively uses the stub version defined at include/linux/ptp_clock_kernel.h:277. One way to solve this problem should be to also build the driver 'fec' as a module. Expected result (obtained after applying the attached patch): $ ethtool -T eth0 Time stamping parameters for eth0: Capabilities: hardware-transmit software-transmit hardware-receive software-receive software-system-clock hardware-raw-clock PTP Hardware Clock: 0 Hardware Transmit Timestamp Modes: off on Hardware Receive Filter Modes: none all $ dmesg | fgrep eth0 [6.570275] fec 2188000.ethernet eth0: registered PHC device 0 [ 24.988653] fec 2188000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 24.988720] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready If you do not see a possible regression, could it be possible to have this change integrated in the official package? Thank you in advance. Best regards. Cédric Delmas -- Package-specific info: ** Version: Linux version 5.10.0-8-armmp (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.46-2 (2021-07-20) ** Command line: console=ttymxc0,115200 quiet ** Tainted: WCE (9728) * kernel issued warning * staging driver was loaded * unsigned module was loaded ** Kernel log: [ 12.684805] systemd[1]: Finished Load Kernel Module configfs. [ 12.687424] systemd[1]:modprobe@drm.service: Succeeded. [ 12.691377] systemd[1]: Finished Load Kernel Module drm. [ 12.703809] systemd[1]:modprobe@fuse.service: Succeeded. [ 12.706144] systemd[1]: Finished Load Kernel Module fuse. [ 12.709347] systemd[1]: Finished Load Kernel Modules. [ 12.716102] systemd[1]: Finished Remount Root and Kernel File Systems. [ 12.726265] systemd[1]: Mounting FUSE Control File System... [ 12.737173] systemd[1]: Mounting Kernel Configuration File System... [ 12.747882] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. [ 12.748797] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. [ 12.763249] systemd[1]: Starting Load/Save Random Seed... [ 12.781066] systemd[1]: Starting Apply Kernel Variables... [ 12.807354] systemd[1]: Starting Create System Users... [ 12.832250] systemd[1]: Mounted FUSE Control File System. [ 12.833534] systemd[1]: Mounted Kernel Configuration File System. [ 13.265966] systemd[1]: Started Journal Service. [ 13.435605] systemd-journald[195]: Received client request to flush runtime journal. [ 13.479320] random: crng init done [ 13.479337] random: 7 urandom warning(s) missed due to ratelimiting [ 15.386473] Registered IR keymap rc-empty [ 15.386638] rc rc0: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0 [ 15.389515] rc rc0: lirc_dev: driver gpio_ir_recv registered at minor = 0, raw IR receiver, no transmitter [ 15.389783] input: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0/input0 [ 15.442505] imx-ipuv3 240.ipu: IPUv3H probed [ 15.587588] imx_media_common: module is from the staging directory, the quality is unknown, you have been warned. [ 15.609741] imx6_media: module is from the staging directory, the quality is unknown, you have been warned. [ 15.748158] etnaviv etnaviv: bound 13.gpu (ops gpu_ops [etnaviv]) [ 15.752573] etnaviv etnaviv: bound 134000.gpu (ops gpu_ops [etnaviv]) [ 15.752600] etnaviv-gpu 13.gpu: model: GC880, revision: 5106 [ 15.760781] etnaviv-gpu 134000.gpu: model: GC320, revision: 5007 [ 15.764480] [drm] Initialized etnaviv
Bug#989151: aerc: please package newer upstream version (0.5.2 as of today)
Package: aerc Severity: wishlist Dear Maintainer, Thank you for introducing this software in Debian. Could you please update the package of aerc to a newer upstream version? The current one, 0.5.2 according to the website, has been out for more than 6 months. Thanks a lot! Cédric signature.asc Description: PGP signature
Bug#988084: unblock: ruby-rugged/1.1.0+ds-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package ruby-rugged
Version 1.1.0+ds-3 in testing was trying to access internet during tests
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987650
As indicated in the bug report, Ubuntu had a patch for that issue
https://git.launchpad.net/~usd-import-team/ubuntu/+source/ruby-rugged/tree/debian/patches/ubuntu-skip-network-tests.patch?id=2f18d60418e71d96ef34c5627370752f94933da6
(I just removed the part where they modified test/remote_test.rb which
is run in Debian only for autopkgtest)
[ Reason ]
Migrating this new version would fix an FTBFS bug caused by those test
failures when the building environment has no access to the internet.
(*and* the internet must not be accessed during build!)
[ Impact ]
[ Tests ]
Five tests from the testsuite are thus now skipped during the build.
[ Risks ]
The code of the library itself has not changed. So risks are (close to)
zero.
[ 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 testing
unblock ruby-rugged/1.1.0+ds-4
diff -Nru ruby-rugged-1.1.0+ds/debian/changelog
ruby-rugged-1.1.0+ds/debian/changelog
--- ruby-rugged-1.1.0+ds/debian/changelog 2021-02-03 10:09:43.0
+0100
+++ ruby-rugged-1.1.0+ds/debian/changelog 2021-05-04 15:27:51.0
+0200
@@ -1,3 +1,12 @@
+ruby-rugged (1.1.0+ds-4) unstable; urgency=high
+
+ * Add patch to really prevent network access in tests (Closes: #987650)
+Thanks Olivier Tilloy for the initial
+patch, adapted here.
+ * Remove duplicate build-dependency on gem2deb
+
+ -- Cédric Boutillier Tue, 04 May 2021 15:27:51 +0200
+
ruby-rugged (1.1.0+ds-3) unstable; urgency=medium
* Enable remote tests only for autopkgtest (Closes: #980258)
diff -Nru ruby-rugged-1.1.0+ds/debian/control
ruby-rugged-1.1.0+ds/debian/control
--- ruby-rugged-1.1.0+ds/debian/control 2021-02-03 10:09:43.0 +0100
+++ ruby-rugged-1.1.0+ds/debian/control 2021-05-04 15:27:51.0 +0200
@@ -8,7 +8,6 @@
Build-Depends: debhelper-compat (= 13),
gem2deb (>= 1),
cmake,
- gem2deb (>= 1.0~),
git,
libgit2-dev (>= 1.1~),
libgit2-fixtures,
diff -Nru ruby-rugged-1.1.0+ds/debian/patches/series
ruby-rugged-1.1.0+ds/debian/patches/series
--- ruby-rugged-1.1.0+ds/debian/patches/series 2021-02-03 10:09:43.0
+0100
+++ ruby-rugged-1.1.0+ds/debian/patches/series 2021-05-04 15:27:51.0
+0200
@@ -3,3 +3,4 @@
dont-try-to-build-libgit2.patch
libgit2-fixtures-path.patch
disable-test-global-config.patch
+skip-network-tests.patch
diff -Nru ruby-rugged-1.1.0+ds/debian/patches/skip-network-tests.patch
ruby-rugged-1.1.0+ds/debian/patches/skip-network-tests.patch
--- ruby-rugged-1.1.0+ds/debian/patches/skip-network-tests.patch
1970-01-01 01:00:00.0 +0100
+++ ruby-rugged-1.1.0+ds/debian/patches/skip-network-tests.patch
2021-05-04 15:27:51.0 +0200
@@ -0,0 +1,53 @@
+Description: skip unit tests that require network access,
+ because Launchpad builders and autopkgtests run in a restricted environment.
+ (This is a trimmed version of Ubuntu patch, letting autopkgtests access the
+ Internet)
+Author: Olivier Tilloy
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987650
+Origin:
https://git.launchpad.net/~usd-import-team/ubuntu/+source/ruby-rugged/tree/debian/patches/ubuntu-skip-network-tests.patch?id=2f18d60418e71d96ef34c5627370752f94933da6
+Reviewed-By: Cédric Boutillier
+
+--- a/test/online/ls_test.rb
b/test/online/ls_test.rb
+@@ -7,6 +7,7 @@ class OnlineLsTest < Rugged::OnlineTestC
+
+ if Rugged.features.include?(:https)
+ def test_ls_over_https
++ skip "this test requires network access"
+ remote = @repo.remotes.create("origin",
"https://github.com/libgit2/TestGitRepository.git;)
+
+ assert_equal [
+--- a/test/online/fetch_test.rb
b/test/online/fetch_test.rb
+@@ -15,6 +15,7 @@ class OnlineFetchTest < Rugged::OnlineTe
+
+ if Rugged.features.include?(:https)
+ def test_fetch_over_https
++ skip "this test requires network access"
+ @repo.remotes.create("origin",
"https://github.com/libgit2/TestGitRepository.git;)
+
+ @repo.fetch("origin")
+@@ -30,6 +31,7 @@ class OnlineFetchTest < Rugged::OnlineTe
+ end
+
+ def test_fetch_over_https_with_certificate_callback
++ skip "this test requires network access"
+ @repo.remotes.create("origin",
"https://github.com/libgit2/TestGitRepository.git;)
+
+ args = {}
+@@ -46,6 +48,7 @@ class OnlineFetchTest < Rugged::OnlineTe
+ end
+
+ def test_fetch_over_https_with_certificate_callback_fail
++ skip "this test req
Bug#986829: uhd-host: Update sysctl configuration filename and path
Package: uhd-host
Version: 3.15.0.0-4+b1
Severity: normal
Dear Maintainer,
For some UHD applications, we need to change {r,w}mem_max values [1].
>From 'sysctl.d (5)' manual,
files under '/.../sysctl.d/' are read in lexicographic order.
It also recommends to:
- "prefix all filenames with a two-digit number
and a dash, to simplify the ordering of the files."
- install package's configuration files under '/usr/lib/'
Current filename ('uhd-usrp2.conf') prevent me to overwrite those values
with another file using the first recommendation (since digits are
lexicographically before letters).
Could you prepend a two-digit number + dash (for easy overwriting)
and move that file to '/usr/lib/sysctl.d/' (for consistency)?
[1]
https://files.ettus.com/manual/page_usrp_x3x0_config.html#x3x0cfg_hostpc_netcfg_sockbuff
Regards,
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-security'), (500, 'testing-debug'), (500, 'unstable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-5-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages uhd-host depends on:
ii adduser 3.118
ii libboost-filesystem1.74.0 1.74.0-9
ii libboost-program-options1.74.0 1.74.0-9
ii libboost-test1.74.0 1.74.0-9
ii libboost-thread1.74.0 1.74.0-9
ii libc6 2.31-11
ii libgcc-s1 10.2.1-6
ii libncurses6 6.2+20201114-2
ii libstdc++6 10.2.1-6
ii libtinfo6 6.2+20201114-2
ii libuhd3.15.03.15.0.0-4+b1
pn libuhd4.0.0
pn libuhd4.0.0-dpdk
ii python3 3.9.2-2
ii python3-requests2.25.1+dfsg-2
Versions of packages uhd-host recommends:
ii curl7.74.0-1.1
ii procps 2:3.3.17-4
Versions of packages uhd-host suggests:
ii fdisk 2.36.1-7
ii gnuradio3.8.2.0-14
ii util-linux 2.36.1-7
--
Cédric Hannotier
Bug#985891: dicompyler doesn't start
Package: dicompyler
Version: 0.4.2.0+git20200106.2643e0e-1
Severity: important
X-Debbugs-Cc: desmont...@netcourrier.com
Dear Maintainer,
The dicompyler installation ends successfully but the application does not
start. It seems that matplotlib dependency is not satisfied.
In a terminal:
desmonts@debian:~$ dicompyler
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 568, in
_build_master
ws.require(__requires__)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 886, in
require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 777, in
resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (matplotlib 3.3.4
(/usr/lib/python3/dist-packages), Requirement.parse('matplotlib<2.2,>=1.3.0'),
{'dicompyler'})
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/dicompyler", line 6, in
from pkg_resources import load_entry_point
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3243,
in
def _initialize_master_working_set():
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3226,
in _call_aside
f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3255,
in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 570, in
_build_master
return cls._build_from_requirements(__requires__)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 583, in
_build_from_requirements
dists = ws.resolve(reqs, Environment())
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 772, in
resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'matplotlib<2.2,>=1.3.0' distribution
was not found and is required by dicompyler
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-4-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 dicompyler depends on:
ii python3 3.9.2-2
ii python3-dicompylercore 0.5.5-2
ii python3-matplotlib 3.3.4-1
ii python3-numpy 1:1.19.5-1
ii python3-pil 8.1.2-1
ii python3-pydicom 2.0.0-1
ii python3-tornado 6.1.0-1+b1
ii python3-wxgtk4.04.0.7+dfsg-10
dicompyler recommends no packages.
dicompyler suggests no packages.
Bug#981625: coreutils: ln -svf fails on nfs share if symbolic link already exists
pushing the investigation, it seems to only be an error on my side. I used to do this on file, but when doing it on a directory, it creates a link inside the linked directory instead of updating the current link. Sorry about that, the main issue can be closed for me. however, the behavior is a bit confusing, without the f option, ln fail saying that the destination file exists, and with it, it doesn't overwrite ii but instead create a new link inside it. Either the destination is the link that should be updated, and it is ok to fail without -f but it should be updated with -f either the destination is a new link inside the directory and it can be created without -f Le mar. 2 févr. 2021 à 14:27, Michael Stone a écrit : > On Tue, Feb 02, 2021 at 10:46:29AM +0100, cedric borgese wrote: > >Package: coreutils > >Version: 8.32-4+b1 > >Severity: normal > >X-Debbugs-Cc: cedric.borg...@gmail.com > > > >Dear Maintainer, > >trying to update a symbolic link from a nfs share silently fails. > >if the symbolic link /some/nfs/share/tmp already exists, the command > >ln -sv /tmp /some/nfs/share/tmp > >fails as expected with an error message, but the command > >ln -svf /tmp /some/nfs/share/tmp > >fails and print an output as if the link was succesfully updated > > I can't duplicate on nfs. I'd guess there's something on the NFS server > preventing the command from succeeding but I can't be more specific > without more information. What should actually be happening is that ln > makes an attempt to create the symlink, that fails, then it makes the > link with a random name and renames it into place. If you run your > command with strace you can see the exact system calls. >
Bug#972574: libgit2: merge request with a proposition
Source: libgit2 Followup-For: Bug #972574 Dear Maintainer, I've just created a merge request on salsa https://salsa.debian.org/debian/libgit2/-/merge_requests/3 with a proposition. This adds an extra libgit2-fixtures binary package, shipping the examples under tests/resources in /usr/share/doc/libgit2-fixtures/examples. Feel free to suggest another path if you think it is more appropriate. This allows me to run correctly the testsuite of ruby-rugged, once indicating the correct location of libgit2 fixtures directory. Best wishes, Cédric signature.asc Description: PGP signature
Bug#977382: qutebrowser-qtwebengine: Most devtools tabs stay blank
On 18/12/20 22:27, Fritz Reichwald wrote: > Hi Cédric, Hi Fritz, > To check if the issue is qutebrowser or webengine related usually we > suggest to try if the bug is reprodudcible with falkon (another browser > using webengine) > If the bug also happens in falkon its with webengine. > Else it might be a qb bug. There were both affected. It took time because I needed to downgrade qtwebengine-opensource-src and qtbase-opensource-src (5.15.2 → 5.15.1). So it was a qt bug. But it is fixed in current version of qtwebengine-opensource-src and qtbase-opensource-src in testing. Since it is fixed, this can be closed. Feel free to reassign it to qt. Regards -- Cédric Hannotier
Bug#977382: qutebrowser-qtwebengine: Most devtools tabs stay blank
It seems to be solved with qtwebengine-opensource-src (5.15.2+dfsg-3) landing on testing. -- Cédric Hannotier
Bug#977382: qutebrowser-qtwebengine: Most devtools tabs stay blank
Package: qutebrowser-qtwebengine
Version: 1.14.1-1
Severity: normal
Dear Maintainer,
Most tabs in qutebrowser devtools stay blank,
making most of devtools unusable.
Affected tabs are:
- Sources
- Network
- Performance
- Memory
- Application
- Security
- Audits
Log using `qutebrowser --debug --temp-basedir`:
ERRORqt-js shell:none:0 Uncaught (in promise) TypeError: Failed to
fetch dynamically imported module: devtools://devtools/bundled/diff/diff.js
File "/usr/bin/qutebrowser", line 33, in
sys.exit(load_entry_point('qutebrowser==1.14.1', 'gui_scripts',
'qutebrowser')())
File "/usr/lib/python3/dist-packages/qutebrowser/qutebrowser.py", line 204,
in main
return app.run(args)
File "/usr/lib/python3/dist-packages/qutebrowser/app.py", line 128, in run
ret = qt_mainloop()
File "/usr/lib/python3/dist-packages/qutebrowser/app.py", line 138, in
qt_mainloop
return q_app.exec_()
File "/usr/lib/python3/dist-packages/qutebrowser/utils/log.py", line 507, in
qt_message_handler
stack = ''.join(traceback.format_stack()) # type: typing.Optional[str]
[369178:369178:1214/160458.123841:ERROR:CONSOLE(0)] "Uncaught (in promise)
TypeError: Failed to fetch dynamically imported module:
devtools://devtools/bundled/diff/diff.js", source:
devtools://devtools/bundled/devtools_app.html (0)
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.9.0-4-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages qutebrowser-qtwebengine depends on:
ii libqt5webenginecore5 5.15.1+dfsg-5+b1
ii python3-pyqt5.qtwebengine 5.15.2-1
ii qutebrowser1.14.1-1
qutebrowser-qtwebengine recommends no packages.
qutebrowser-qtwebengine suggests no packages.
-- no debconf information
Regards
--
Cédric Hannotier
Bug#975553: suckless-tools: Windows lose focus when they are interrupted by dmenu
Package: suckless-tools Version: 45-1 Severity: important Dear Maintainer, Focused window looses input focus when interrupted by dmenu. It affects some WM. This was already reported on i3 side [1] and on suckless side [2]. It was fixed by commit db6093f6ec1bb884f7540f2512935b5254750b30 [3]. Could you backport that commit or, (better IMO) update dmenu to version 5.0 (released on 2020/09/02) [4] ? [1] https://github.com/i3/i3/issues/3528 [2] https://lists.suckless.org/dev/1902/33272.html [3] https://git.suckless.org/dmenu/commit/db6093f6ec1bb884f7540f2512935b5254750b30.html [4] https://git.suckless.org/dmenu/commit/1a13d0465d1a6f4f74bc5b07b04c9bd542f20ba6.html -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-1-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages suckless-tools depends on: ii libc6 2.31-4 ii libcap2-bin 1:2.44-1 ii libfontconfig1 2.13.1-4.2 ii libpam0g1.3.1-5 ii libx11-62:1.6.12-1 ii libxft2 2.3.2-2 ii libxinerama12:1.1.4-2 ii libxrandr2 2:1.5.1-1 ii libxss1 1:1.2.3-1 suckless-tools recommends no packages. Versions of packages suckless-tools suggests: pn dwm ii stterm 0.8.4-1 pn surf -- no debconf information Best regards -- Cédric Hannotier
Bug#972335: i3lock: Cannot read image from pipe
Dear sur5r, On Sun, 18 Oct 2020 18:53:50 + Jakob Haufe wrote: > Seems I completely missed this. Will take care of it in the next few > days. Do you have any update regarding this issue? -- Cédric Hannotier
Bug#927076: any progress?
Hi, I was wondering if there was any progress in the process of getting xournalpp into Debian. I would be really happy to have it in the official archive. Oh, I see that your work, Barak, has been imported recently into the Debian group on salsa: https://salsa.debian.org/debian/xournalpp although the last commit is 4 months old. Are there any plans to upload it soon? Thanks in advance signature.asc Description: PGP signature
Bug#972574: libgit2: consider providing a binary package with libgit2 fixtures for test purposes
Source: libgit2 Version: 1.0.0+dfsg.1-2 Severity: wishlist Dear Maintainer, I am in the process of preparing ruby-rugged to work with the new libgit2 1.0 in experimental. The new upstream version of this package has new tests relying on the availability of the fixtures provided in the sourcetree of libgit2. I was wondering if you would consider providing a binary package with these fixtures in case other software relying on libgit2 would use them as part of their testsuite. Best regards, Cédric -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled signature.asc Description: PGP signature
Bug#972335: i3lock: Cannot read image from pipe
Package: i3lock Version: 2.11.1-1 Severity: normal Dear Maintainer, Reading image from stdin throws OOM. It has been reported in [1]. It is solved using option --raw introduced in [2]. It is included in last release [3]. Could you please upgrade i3lock to v2.12? It was release more than 1 year ago. [1] https://github.com/i3/i3lock/issues/227 [2] https://github.com/i3/i3lock/pull/226/files [3] https://github.com/i3/i3lock/releases/tag/2.12 -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-2-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages i3lock depends on: ii libc6 2.31-3 ii libcairo2 1.16.0-4 ii libev4 1:4.33-1 ii libpam0g1.3.1-5 ii libxcb-image0 0.4.0-1+b2 ii libxcb-randr0 1.14-2 ii libxcb-shm0 1.14-2 ii libxcb-util00.3.8-3+b2 ii libxcb-xinerama01.14-2 ii libxcb-xkb1 1.14-2 ii libxcb-xrm0 1.0-3 ii libxcb1 1.14-2 ii libxkbcommon-x11-0 0.10.0-1 ii libxkbcommon0 0.10.0-1 i3lock recommends no packages. i3lock suggests no packages. -- no debconf information -- Cédric Hannotier
Bug#967999: version 6.x has support for rails 6
The last upstream version 6.3.0 has support for Rails 6. I have imported the package in the Ruby team salsa group (it was missing for some reason), at the place expected from the Vcs fields. I upgraded roughly the package, and noticed (only?) two test failures (and no error), that I could not fix yet. Cheers Cédric
Bug#943617: help welcome
Dear Klaus-Michael, apologies for my late answer. If you are still interested in helping maintaining ruby-cmdparse, you are most welcome to join the ruby team. We are never lacking manpower to update the many packages maintained by the team. Write an email to debian-r...@lists.debian.org and create an account on the salsa.debian.org platform if you don't have one yet. You'll be included in the ruby group and can update the package from there, and have your package sponsored for an upload in the archive. Best wishes, Cédric signature.asc Description: PGP signature
Bug#970496: gnuradio: Crash on missing gsettings
19.0.2-2 Versions of packages gnuradio recommends: pn gnuradio-dev ii python3-matplotlib 3.3.0-3 ii python3-networkx2.4-4 ii python3-pyqt5.qwt 1.02.00-2 ii python3-scipy 1.5.2-2 ii rtl-sdr 0.6.0-3 ii uhd-host 3.15.0.0-3 Versions of packages gnuradio suggests: pn gr-fosphor pn gr-osmosdr -- no debconf information -- Cédric Hannotier
Bug#969738: ruby-asciidoctor-pdf: relax version constraint on ruby-prawn (2.3.0 in experimental)
Source: ruby-asciidoctor-pdf Version: 1.5.3-1 Severity: important Dear Keith, I have just uploaded ruby-prawn 2.3.0-1~exp1 to experimental. The package ruby-asciidoctor-pdf does not accept versions of ruby-prawn higher than 2.2.x in debian control file and in the gemspec. Please relax this constraint and test against the package in experimental. I also saw that there is a comment in the gemspec about the fact that ttfunk 1.6 may cause problems with asciidoctor-pdf. Note that I already uploaded ttfunk 1.6 to unstable. Possible issues were unnoticed because of the lack of explicit dependency. I hope this is fixable, as prawn 2.3 require ttfunk 1.6. Best regards, Cédric
Bug#969736: ruby-asciidoctor-pdf: misleading Maintainer: field
Package: ruby-asciidoctor-pdf Severity: normal Dear Keith, The package ruby-asciidoctor-pdf indicates that the maintainer for this package is the Ruby team. However this package is not maintained in the Ruby group on salsa, but under your personal name space. This can create some confusion, e.g. in case of bug reports. Would you mind changing the maintainer field of the package to reflect that? You are also most welcome to move the repo to the ruby group, and maintain it from there, if you wish. Best regards, Cédric
Bug#968596: zathura: Cannot find user-level thread for LWP 101764: generic error
Package: gdb Version: 9.2-1 Severity: normal Dear Maintainer, I was trying to debug zathura-0.4.6-1, but gdb fails: $ gdb zathura GNU gdb (Debian 9.2-1) 9.2 [...] Type "apropos word" to search for commands related to "word"... Reading symbols from zathura... (No debugging symbols found in zathura) (gdb) r Starting program: /usr/bin/zathura [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x74e9b700 (LWP 104676)] Cannot find user-level thread for LWP 104672: generic error (gdb) info thread Id Target IdFrame * 1Thread 0x7550b100 (LWP 104672) "zathura" (running) 2Thread 0x74e9b700 (LWP 104676) "gmain" (running) -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-2-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gdb depends on: ii libbabeltrace1 1.5.8-1+b1 ii libc6 2.31-3 ii libexpat1 2.2.9-1 ii libgcc-s1 10.2.0-5 ii libipt2 2.0.2-1 ii liblzma55.2.4-1+b1 ii libmpfr64.0.2-1 ii libncursesw66.2-1 ii libpython3.83.8.5-2 ii libreadline88.0-4 ii libsource-highlight4v5 3.1.9-3 ii libstdc++6 10.2.0-5 ii libtinfo6 6.2-1 ii libxxhash0 0.8.0-1 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages gdb recommends: ii libc6-dbg [libc-dbg] 2.31-3 Versions of packages gdb suggests: pn gdb-doc pn gdbserver -- no debconf information
Bug#966846: Kernel panic (4.19.0-10): RIP __cgroup_bpf_run_filter_skb
Package: linux-source-4.19 Version: 4.19.132-1 Severity: important Hello, Since linux-image-4.19.0-10-amd64, I'm facing regular Kernel panics - "RIP: 0010:__cgroup_bpf_run_filter_skb+0x26d/0x3d0" - resulting in full (file) *server freeze*. The issue is pretty well described and summarized in https://forum.proxmox.com/threads/kernel-5-4-44-causes-system-freeze-on-hp-microserver-gen8.72050/page-2#post-323498 The "culprit" commit - "netprio_cgroup: Fix unlimited memory leak of v2 cgroups" - is indeed included in Debian kernel (4.19) since changelog entry 4.19.131-1 It *seems* there is already a patch proposed upstream (although here for kernel 4.9): https://lkml.org/lkml/2020/7/20/883 Best regards, Cédric -- Cédric Dufour
Bug#966436: files
Here are the promised files Image: spec/fixtures/clipping_path.jpg Format: JPEG (Joint Photographic Experts Group JFIF format) Mime type: image/jpeg Class: DirectClass Geometry: 200x120+0+0 Resolution: 72x72 Print size: 2.8x1.7 Units: PixelsPerInch Colorspace: sRGB Type: Palette Base type: Undefined Endianess: Undefined Depth: 8-bit Channel depth: red: 8-bit green: 8-bit blue: 8-bit Channel statistics: Pixels: 24000 Red: min: 208 (0.815686) max: 208 (0.815686) mean: 208 (0.815686) standard deviation: 0 (0) kurtosis: 4.19021e+54 skewness: 0 entropy: 0 Green: min: 176 (0.690196) max: 176 (0.690196) mean: 176 (0.690196) standard deviation: 0 (0) kurtosis: -1.73261e+54 skewness: 0 entropy: 0 Blue: min: 177 (0.694118) max: 177 (0.694118) mean: 177 (0.694118) standard deviation: 0 (0) kurtosis: 1.47046e+54 skewness: -1.39375e+37 entropy: 0 Image statistics: Overall: min: 176 (0.690196) max: 208 (0.815686) mean: 187 (0.73) standard deviation: 0 (0) kurtosis: -1.50004 skewness: 0.70469 entropy: 0 Colors: 1 Histogram: 24000: (208,176,177) #D0B0B1 srgb(208,176,177) Rendering intent: Perceptual Gamma: 0.454545 Chromaticity: red primary: (0.64,0.33) green primary: (0.3,0.6) blue primary: (0.15,0.06) white point: (0.3127,0.329) Background color: white Border color: srgb(223,223,223) Matte color: grey74 Transparent color: black Interlace: None Intensity: Undefined Compose: Over Page geometry: 200x120+0+0 Dispose: Undefined Iterations: 0 Compression: JPEG Quality: 99 Orientation: TopLeft Properties: date:create: 2018-03-18T06:54:04+01:00 date:modify: 2018-03-18T06:54:04+01:00 exif:ColorSpace: 1 exif:DateTime: 2016:01:20 19:28:30 exif:ExifOffset: 172 exif:Orientation: 1 exif:PixelXDimension: 200 exif:PixelYDimension: 120 exif:ResolutionUnit: 2 exif:Software: Adobe Photoshop CC 2014 (Macintosh) exif:thumbnail:Compression: 6 exif:thumbnail:JPEGInterchangeFormat: 310 exif:thumbnail:JPEGInterchangeFormatLength: 814 exif:thumbnail:ResolutionUnit: 2 exif:thumbnail:XResolution: 72/1 exif:thumbnail:YResolution: 72/1 exif:XResolution: 72/1 exif:YResolution: 72/1 icc:copyright: Copyright (c) 1998 Hewlett-Packard Company icc:description: sRGB IEC61966-2.1 icc:manufacturer: IEC http://www.iec.ch icc:model: IEC 61966-2.1 Default RGB colour space - sRGB jpeg:colorspace: 2 jpeg:sampling-factor: 1x1,1x1,1x1 signature: 44f62c0b59893193d132f211e53e1d4fc8d92b27d5699d1ccdb340c97f9e6d12 Clipping path: http://www.w3.org/2000/svg; width="200" height="120"> Profiles: Profile-8bim: 3720 bytes Profile-exif: 1130 bytes Profile-icc: 3144 bytes Profile-xmp: 4273 bytes Artifacts: filename: spec/fixtures/clipping_path.jpg verbose: true Tainted: False Filesize: 14616B Number pixels: 24000 Pixels per second: 2.4MB User time: 0.010u Elapsed time: 0:01.009 Version: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org Image: Filename: spec/fixtures/clipping_path.jpg Format: JPEG (Joint Photographic Experts Group JFIF format) Mime type: image/jpeg Class: DirectClass Geometry: 200x120+0+0 Resolution: 72x72 Print size: 2.8x1.7 Units: PixelsPerInch Colorspace: sRGB Type: Palette Base type: Undefined Endianness: Undefined Depth: 8-bit Channel depth: red: 8-bit green: 8-bit blue: 8-bit Channel statistics: Pixels: 24000 Red: min: 208 (0.815686) max: 208 (0.815686) mean: 208 (0.815686) standard deviation: 0 (0) kurtosis: 4.19021e+54 skewness: 0 entropy: 0 Green: min: 176 (0.690196) max: 176 (0.690196) mean: 176 (0.690196) standard deviation: 0 (0) kurtosis: -1.73261e+54 skewness: 0 entropy: 0 Blue: min: 177 (0.694118) max: 177 (0.694118) mean: 177 (0.694118) standard deviation: 0 (0) kurtosis: 1.47046e+54 skewness: -1.39375e+37 entropy: 0 Image statistics: Overall: min: 176 (0.690196) max: 208 (0.815686) mean: 187 (0.73) standard deviation: 0 (0) kurtosis: -1.50004 skewness: 0.70469 entropy: 0 Colors: 1 Histogram: 24000: (208,176,177) #D0B0B1 srgb(208,176,177) Rendering intent: Perceptual Gamma: 0.454545 Chromaticity: red primary: (0.64,0.33) green primary: (0.3,0.6) blue primary: (0.15,0.06) white point: (0.3127,0.329) Background color: white Border color: srgb(223,223,223) Matte color: grey74 Transparent color: black Interlace: None Intensity: Undefined Compose: Over Page geometry: 200x120+0+0
Bug#966436: reassign to imagemagick 8:6.9.11.24+dfsg-1
reassign 966436 src:imagemagick found 966436 8:6.9.11.24+dfsg-1n retitle scrambled property in identify -verbose output affects 966436 ruby-mini-magick thanks ruby-mini-magick relies (too) heavily on a parsing of output of imagemagick tools like identify. The issue discussed here is caused by a change in the output of the `identify -verbose` command from the version in testing (8:6.9.10.23+dfsg-2.1+b2) and unstable (8:6.9.11.24+dfsg-1). Attached are the corresponding outputs of the above command on the file from ruby-mini-magick specs (spec/fixtures/clipping_path.jpg). In the "unstable" version, the field Properties: has first subfield (on line 96) with a strange name, which makes regexp filtering from ruby-mini-magick choke. The content seems to be the same as the "Clipping path:" field. This subfield does not appear in the version of testing. It is mentionned as a warning on newer versions of ruby-mini-magick that the `details` method reading the output of `identify -verbose` in a specific way, has become unreliable for newer versions of ImageMagick. I am therefore disabling the corresping test in that code. However, I believe that the output of identify -verbose should not contain such cryptic field names, therefore, I am reassigning the but to imagemagick package. Thanks, Cédric signature.asc Description: PGP signature
Bug#963691: resource-agents : /lib/ocf/resource.d/heartbeat/IPsrcaddr needs to be patched
Package: resource-agents Version: 1:4.2.0-2+deb10u1 Severity: normal Hello, IPsrcaddr fails to stop when ipaddress is on interface not managed by NetworkManager Bug as already been reported to redhat : https://bugzilla.redhat.com/show_bug.cgi?id=1504055 Error message example output of crm_mon : Online: [ cluster2 ] OFFLINE: [ cluster1 ] Full list of resources: email_alert (ocf::heartbeat:MailTo): Started cluster2 Resource Group: freepbx shared_ip_data (ocf::heartbeat:IPaddr2): Started cluster2 srcaddr_ip_data (ocf::heartbeat:IPsrcaddr): FAILED cluster2 (blocked) Failed Resource Actions: * srcaddr_ip_data_stop_0 on cluster2 'unknown error' (1): call=20, status=complete, exitreason='command 'ip route replace dev ens18' failed', last-rc-change='Thu Jun 25 12:09:35 2020', queued=0ms, exec=28ms Fix : see https://github.com/ClusterLabs/resource-agents/pull/1311 Patch which fixes the problem : https://github.com/ClusterLabs/resource-agents/pull/1311/commits/6052e8fd37d23f46db217f915b445c7e67dccb34.patch -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-9-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages resource-agents depends on: ii cluster-glue 1.0.12-12 ii gawk 1:4.2.1+dfsg-1 ii libc6 2.28-10 ii libglib2.0-0 2.58.3-2+deb10u2 ii libnet1 1.1.6+dfsg-3.1 ii libplumb2 1.0.12-12 ii libplumbgpl2 1.0.12-12 ii python3 3.7.3-1 Versions of packages resource-agents recommends: ii libxml2-utils 2.9.9+dfsg-1+0~20200226.5+debian10~1.gbp3b6674 ii net-tools 1.60+git20180626.aebd88e-1 ii python3-googleapi 1.5.5-1 resource-agents suggests no packages. -- no debconf information
Bug#955429: possiblity of using a different download agent like wget in bad internet connections
Hi, Here is a log attached. The client has private IP 192.168.0.106 behind an ADSL "box" with public IP 82.65.29.121 The package with a missed download was actually this time apt-cacher-ng: E: Impossible de récupérer http://deb.debian.org/debian/pool/main/a/apt-cacher-ng/apt-cacher-ng_3.5-1_amd64.deb Somme de contrôle de hachage incohérente Hashes of expected file: - SHA256:5bf309906ebfb202e2d91abd6bb952f42e38326c6a12fdc9326936dbf0b974b9 - MD5Sum:7407fe84c3f123b76a5daebd9bb71925 [weak] - Filesize:562512 [weak] Hashes of received file: - SHA256:f7284dd1761a74cd592496c8c3451721b14894c03fed22b9fd499924a1ea7dfb - MD5Sum:d1df236d3c207c51d32c26da401a10e5 [weak] - Filesize:562512 [weak] Last modification reported: Mon, 20 Apr 2020 22:42:49 + Thanks for investigating. Cheers, Cédric apt-cacher.err.gz Description: application/gzip signature.asc Description: PGP signature
Bug#959130: i3status: Drop CAP_NET_ADMIN and libcap2-bin rec
Package: i3status Version: 2.13-2 Severity: normal Dear Maintainer, Since [1], capability CAP_NET_ADMIN is no more required to request Ethernet speed (related to EOL of a specific kernel version). However, it seems that there is an old postinstall file [2] that still tries to add it. Could you update the packaging process? Regards, Cédric [1] https://github.com/i3/i3status/commit/03c8908ec6429a67c3a8f480f1002788ff155bfb [2] https://salsa.debian.org/i3-team/i3status/-/blob/02705f8792c5fded19e180f5733f86ca23f707e7/debian/i3status.postinst
Bug#959095: imv: Update to 4.1.0
Package: imv Version: 4.0.1-1 Severity: wishlist Dear Maintainer, Could you package v4.1.0 and push it to unstable/testing? It was released on 2019-12-21. It fixes reading images from stdin. Regards, Cédric
Bug#956280: shapelib: change in ronn 0.9.0 breaks generation of manpages
On Sat, Apr 11, 2020 at 06:20:13AM +0200, Sebastiaan Couwenberg wrote: > > pycsw required the same changes. Those are also ready in git. Ah... I was wondering why it was not listed by build-rdepends script (without parameters), but it is probably because it is in non-free. > You don't have to wait for me, just bump the severity of this issue to > serious when you move it to unstable. Ok. I went ahead, and uploaded to unstable. Raising bug severity. Cheers, Cédric signature.asc Description: PGP signature
Bug#956280: shapelib: change in ronn 0.9.0 breaks generation of manpages
Dear Sebastiaan, On Thu, Apr 09, 2020 at 12:20:52PM +0200, Sebastiaan Couwenberg wrote: > > Hopefully that (new) behavior will stay, this is not the first time an > update of ruby-ronn required changes. I think (or at least hope too) that it is here to stay. > When do you plan to move it to unstable? Given that shapelib is the only reverse build-dependency failing because of this change, we can move to unstable when shapelib is ready to. What about in 7 days from now? Tell me what suits best for you. Cheers, Cédric signature.asc Description: PGP signature
Bug#955429: possiblity of using a different download agent like wget in bad internet connections
Hi, On Thu, Apr 09, 2020 at 09:43:02PM +0530, Pirate Praveen wrote: > boutil and terceiro also reported same problem yesterday in #debian-ruby irc > (copying them). So I think the issue is not specific to me. > > boutil: hi! do you experience many "Hash Sum mismatch" when doing upgrades > with apt-cache-ng? I indeed experience this often on my laptop (uptodate sid). On wifi, about every second `apt update` fails with such a mismatch, either when updating my system, or building a package with sbuild. Ethernet connection is a bit better, but still it happens. I have a not so fast ADSL line. I just got 5 times in a row this: [...] Err:19 http://ftp.fr.debian.org/debian testing/main DEP-11 64x64 Icons Hash Sum mismatch Hashes of expected file: - Filesize:7050569 [weak] - SHA256:802728a6bcbe5201c8cafa40286b9b10c8942beefe2922725056bfc706f86753 - MD5Sum:570e3cdb335fed69c669af1610093c7b [weak] Hashes of received file: - SHA256:43b59d8c2ef9ac42b56f38108557a5e9b35a793a96a4268d6004a0d5e10865f9 - MD5Sum:46fcee066fb69d7934cbbdf8d941273a [weak] - Filesize:7050569 [weak] Last modification reported: Fri, 10 Apr 2020 08:17:35 + Release file created at: Fri, 10 Apr 2020 15:23:29 + [...] My desktop station at work doesn't seem to show this behavior. It is connected to a fast ethernet cable and fast internet connection. Cheers, Cédric signature.asc Description: PGP signature
Bug#956112: RFS: eggdrop/1.8.4-3 -- Advanced IRC Robot
Hi Adam, Thank you very much for your feedback! I have fixed all the issues you listed and uploaded an updated package to mentors: - https://mentors.debian.net/package/eggdrop - https://mentors.debian.net/debian/pool/main/e/eggdrop/eggdrop_1.8.4-1.dsc > The package is marked as UNRELEASED, and uploading that would cause an > autoreject. Distribution changed to "unstable". > The changelog entry from 11 Aug 2014 is overwritten with a bunch of > UNRELEASED entries. This shows some confusion. Past changelog entries are > supposed to be immutable other than for corrections. These were all the not uploaded releases (lived only in mentors), there has been quite a few. I have reimported the published changelog and added a single 1.8.4-1 entry with all changes since 2014. > dh-missing complains about a lot of files installed into staging dirs but > not put anywhere into actual packages. dh_missing warnings fixed, they were due to documentation files taken from source directory instead of installed package. Regards -- Cédric
Bug#956280: shapelib: change in ronn 0.9.0 breaks generation of manpages
Source: shapelib Version: 1.5.0-1 Severity: important Dear Maintainer, I uploaded ruby-ronn 0.9.0 in experimental. This version contains a change that strips all extensions (not just .ronn) from processed files to produce the name of the man page. It seems that the loop present in debian/rules to rename the man pages from .md.1 to .1 extension fails if there is no debian/man/*.md.1 file. When ruby-ronn 0.9.0 will go in unstable, removing this loop will be enough, but as is, the loop does not behave well if debian/man/*.md.1 is empty. Best regards, Cédric -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled signature.asc Description: PGP signature
Bug#953198: ronn 0.9.0 uploaded to experimental
Hi! Thank you for your work. I am uploading right now your version with some additional commits to experimental, as some reverse build-dependencies (in particular shapelib) are failing to build with this new version. Looking forward to your next contribution to the Ruby team Best wishes, Cédric signature.asc Description: PGP signature
Bug#928786: eggdrop FTCBFS: multiple minor issues
tags 928786 + pending stop Hi Helmut, First of all sorry it took me so long to answer. Both issues have been fixed upstream and are packaged for a long time, but I don't have upload rights and could not find a sponsor since the release of eggdrop 1.8.0 (packaged in Feb 2017), despite a few contacts with debian developers and one RFS (closed without notification because the package had been removed from mentors). The up-to-date package is available on mentors.debian.net : https://mentors.debian.net/package/eggdrop https://mentors.debian.net/debian/pool/main/e/eggdrop/eggdrop_1.8.4-3.dsc Regards -- Cédric May 11, 2019 7:42 AM, "Helmut Grohne" wrote: > Source: eggdrop > Version: 1.6.21-4 > Tags: patch upstream > User: helm...@debian.org > Usertags: rebootstrap > > eggdrop fails to cross build from source for two reasons: > > * It uses AC_RUN_IFELSE with a wrong cross guess to check whether > socklen_t exists. > > A better solution is using AC_CHECK_TYPE here. > > * It insists on running eggdrop -v during build. > > It simply should not do that as it does not contribute to the build > in any way. > > The attached patch fixes both. Please consider applying it. > > Helmut
Bug#956112: RFS: eggdrop/1.8.4-3 -- Advanced IRC Robot
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "eggdrop" * Package name : eggdrop Version : 1.8.4-3 Upstream Author : EggHeads Development Team * URL : http://www.eggheads.org * License : GPL-2+ * Vcs : https://github.com/yastupin/eggdrop-debian Section : net It builds those binary packages: eggdrop - Advanced IRC Robot eggdrop-data - Architecture independent files for eggdrop To access further information about this package, please visit the following URL: https://mentors.debian.net/package/eggdrop Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/e/eggdrop/eggdrop_1.8.4-3.dsc Changes since the last upload: * New upstream version 1.8.4 * patches - remove 03openssl_checks (fixed upstream) - refresh patches * fix some lintian warnings - use debhelper 12 - enable hardening flags (+all) - remove autotools-dev and dh-autoreconf dependencies - update to standards version 4.3.0 - add override for compress.so hardening * debian/watch - use https - ignore rc releases in debian/watch * rename NEWS and UPGRADING files * add Vcs-Git and Vcs-Browser to control * use dh_autoreconf Regards -- Cédric
Bug#943191: nanoc: Python2 removal in sid/bullseye
Hi Sandro, Thanks for the heads-up, and sorry for the delay. I am uploading your fix now, in 4.11.0-5. Cheers, Cédric signature.asc Description: PGP signature
Bug#950901: ruby-fakefs: missing ruby2.7 support
Package: ruby-fakefs Version: 0.20.1-1 Severity: important Tags: upstream Control: forwarded -1 https://github.com/fakefs/fakefs/issues/437 Dear Maintainer, This library still does not support ruby2.7. More investigation is needed.
Bug#949392: RM: ruby-notifier -- ROM; dead upstream, RC buggy, no reverse dependencies
Package: ftp.debian.org Severity: normal Hi, We would like to request the removal of ruby-notifier package, which is has had no activity upstream activity for four years, has a RC bug #896175, low popcon, no reverse (build-) dependencies. THanks in advance. Cédric, for the ruby team
Bug#934160: nfs-common: Umask ignored, all files created world-writable on NFS
+1 QUIRK: In order to reliably disable NFS 4.2 on *server* side; in /etc/systemd/system/nfs-server.service.d/nfs-version.conf # Disable NFS 4.2 # FIX: umask ignored (files created world-writable) when using NFS 4.2 (on top of ZFS) # BUG: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934160 # REF: https://tools.ietf.org/id/draft-ietf-nfsv4-umask-03.html # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=47057abde515155a4fee53038e7772d6b387e0aa # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=880a3a5325489a143269a8e172e7563ebf9897bc # BUG: https://zfsonlinux.topicbox.com/groups/zfs-discuss/T36a651c77dc95fec-Ma755882676a054fe9a903c7f/zfs-discuss-umask-not-respected-when-a-shared-dataset-is-mountedvia-nfs-4-2 # BUG: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738063 # BUG: https://linuxlists.cc/l/17/linux-nfs/t/3236382/nfs-config.service_fails_to_apply_no-nfs-version_after_a_reboot#post3236382 [Service] ExecStartPre=/bin/sh -c '/usr/sbin/rpc.nfsd 0; echo -2 +3 +4 +4.1 -4.2 > /proc/fs/nfsd/versions'
Bug#941618: torus-trooper: fails to start with "undefined symbol" error
Package: torus-trooper Version: 0.22.dfsg1-12 Severity: important Dear Maintainer, I've just installed the game and tried to launch it from the terminal: I got the following error message: torus-trooper: symbol lookup error: torus-trooper: undefined symbol: _D4core4stdc5errno5errnoFNbNdNiNeZ Rebuilding in sbuild fixed the issue for me. Does it mean that the package needs a binNMU? Cheers -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages torus-trooper depends on: ii libbulletml0v5 0.0.6-7 ii libc6 2.29-2 ii libgcc1 1:9.2.1-8 ii libgl1 1.1.0-1+b1 ii libglu1-mesa [libglu1] 9.0.0-2.1+b3 ii libgphobos769.2.1-8 ii libsdl-mixer1.2 1.2.12-16 ii libsdl1.2debian 1.2.15+dfsg2-5 ii torus-trooper-data 0.22.dfsg1-12 torus-trooper recommends no packages. torus-trooper suggests no packages. -- no debconf information
Bug#919877: fixed by 1.7.1-3 upload
Control: fixed -1 ruby-sprite-factory/1.7.1-3 Hi, This failing test is skipped by a patch since 1.7.1-3. The package now builds fine. I am therefore closing this bug. Cheers, Cédric
Bug#939437: ruby-glib2: missing dependency on ruby-pkg-config >=1.3.5
Package: ruby-glib2 Version: 3.3.7-1 Severity: important Dear Maintainer, the glib2 gemspec indicates that it should depend on ruby-pkg-config. However this package does not appear in the dependency list. gem dependency check will thus fail for every package depending on ruby-glib2. Please add the dependency or remove it from gemspec depending on what is the best approach. Best wishes, Cédric -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ruby-glib2 depends on: ii libc6 2.28-10 ii libglib2.0-0 2.60.6-2 ii libruby2.52.5.5-4 ii ruby 1:2.5.1 ruby-glib2 recommends no packages. ruby-glib2 suggests no packages. -- no debconf information
Bug#914511: Please enable the "virtio-rng" driver in "cloud" kernels
Workaround: have the hypervisor expose the 'rdrand' CPU feature to the VM (but this is in the hands of the hypervisor's provider, not the VM user)
Bug#914511: Please enable the "virtio-rng" driver in "cloud" kernels
Now that *u*random is blocking until considered properly initialized, the entropy starvation [1] issue becomes a real problem during the boot process; e.g. it takes several minutes until one gets SSH access to the box. [1] https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#entropy-starvation -- Cédric Dufour - Exoscale (Lausanne, Switzerland)
Bug#930358: qmodbus: Qt-based ModBus master application
Package: wnpp Severity: wishlist Package name: qmodbus Version : 0.3.0 Upstream Author : Karl-Heinz Reichel URL : https://github.com/ed-chemnitz/qmodbus License : GPL2+ Programming Lang: C++ Description : ModBus master GUI QModBus is a free Qt-based implementation of a ModBus master application. A graphical user interface allows easy communication with ModBus slaves over serial line interface. QModBus also includes a bus monitor for sniffing all traffic on the bus.
Bug#847937: 5 years and nothing :-/
Hello, Lollypop dev here... Lollypop started 5 years ago and Debian (and Ubuntu) is the last distro not packaging it, it's really sad for me because I'm missing Debian users ;) regards, -- Cédric Bellegarde
Bug#925397: unblock: nanoc/4.11.0-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package nanoc Version 4.11.0-3 currently in unstable fixes RC bug #924845: the package now does not build-depend on ruby-fog (which has been removed from the archive), but only on ruby-fog-local (and suggests ruby-fog-core). Please find in attachment the debdiff between the source package 4.11.0-2 currently in testing. unblock nanoc/4.11.0-3 -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru nanoc-4.11.0/debian/changelog nanoc-4.11.0/debian/changelog --- nanoc-4.11.0/debian/changelog 2019-01-06 22:10:41.0 +0100 +++ nanoc-4.11.0/debian/changelog 2019-03-23 00:18:11.0 +0100 @@ -1,3 +1,10 @@ +nanoc (4.11.0-3) unstable; urgency=medium + + * Change (build-)dependencies from ruby-fog (removed from the archive) to +ruby-fog-local (Closes: #924845) + + -- Cédric Boutillier Sat, 23 Mar 2019 00:18:11 +0100 + nanoc (4.11.0-2) unstable; urgency=medium * Tighten ruby-hamster and ruby-ref dependency relation from Recommends to diff -Nru nanoc-4.11.0/debian/control nanoc-4.11.0/debian/control --- nanoc-4.11.0/debian/control 2019-01-06 22:10:41.0 +0100 +++ nanoc-4.11.0/debian/control 2019-03-23 00:18:11.0 +0100 @@ -26,7 +26,7 @@ ruby-ddplugin, ruby-erubi, ruby-erubis, - ruby-fog (>= 0.13.0~), + ruby-fog-local, ruby-fuubar, ruby-haml, ruby-hamster, @@ -110,7 +110,7 @@ Suggests: coderay | ruby-pygments.rb | python3-pygments | highlight, git, rsync, - ruby-fog (>= 0.13.0~), + ruby-fog-core (>= 0.13.0~), ruby-rack Description: static site generator written in Ruby Nanoc is a static site generator, fit for building anything from a small signature.asc Description: PGP signature
Bug#919048: fixed in unstable : should postpone autoremoval from testing
Hi, This bug has been fixed with 1.0.0-1. ruby-haml-rails is flagged for autoremoval in 19 hours. Hoping that writing to this bug will postpone the autoremoval to let the package from unstable migrate to testing in time. Cédric
Bug#907438: fixed in 1.0.0-2
Control: fixed -1 ruby-toml-rb/1.0.0-2 Hi, thanks for your report. this bug has been fixed with the 1.0.0-2, when the file init.rb from source was installed in the binary package. I am therefore closing this bug. Cheers, Cédric
Bug#888130: set severity to normal as 2.9.4-2 skips this test
Control: tag -1 -ftbfs Control: severity -1 normal Control: tag -1 experimental Hi, This bug does not affect experimental, as the 3.x branch removed this test (and the corresponding code). The reuse functionality has been reported upstream to cause problems in some situations in the 2.x branch. I am therefore skipping the corresponding test in 2.9.4-2, and decrease the severity to normal for now, since the possible problem does not affect the building process. Cheers, Cédric signature.asc Description: PGP signature
Bug#912249: not ftbfs anymore since 1.2.0-1 (test disable)
Control: tag -1 -ftbfs Control: retitle -1 test_tail_change2(FileTailTest) fails Control: severity -1 normal Hi, This test is now disabled in the test suite (build and autopkgtest). I am therefore downgrading the severity of the bug and removing the ftbfs tag, but leave the bug open, waiting for a true fix. Cheers, Cédric signature.asc Description: PGP signature
Bug#919916: RFS: eggdrop/1.8.4-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "eggdrop" * Package name : eggdrop Version : 1.8.4-1 Upstream Author : Eggheads Development Team * URL : https://www.eggheads.org/ * License : GPL-2+ Section : net It builds those binary packages: eggdrop - Advanced IRC Robot eggdrop-data - Architecture independent files for eggdrop To access further information about this package, please visit the following URL: https://mentors.debian.net/package/eggdrop Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/e/eggdrop/eggdrop_1.8.4-1.dsc More information about eggdrop can be obtained from https://www.eggheads.org/ Changes since the last upload: * New upstream version 1.8.4 * patches - remove 03openssl_checks (fixed upstream) - refresh patches * fix some lintian warnings - use debhelper 10 - enable hardening flags - remove autotools-dev and dh-autoreconf dependencies * debian/watch - use https - ignore rc releases in debian/watch * rename NEWS and UPGRADING files * add Vcs-Git and Vcs-Browser to control Build log on travis : https://travis-ci.org/yastupin/eggdrop-debian/builds/482084985 Regards, -- Cédric Barboiron
Bug#919720: RM: ruby-albino -- ROM; dead upstream, obsolete
Package: ftp.debian.org Severity: normal Dear FTP masters, please remove ruby-albino from the archive. It has problems due to transition of pygmentize to python3, dead upstream for many years and obsolete. No reverse (build)dependencies. Thanks in advance! Cheers, Cédric
Bug#919653: python-pygments: pygmentize and its manpage in different binary packages
Package: python-pygments Version: 2.3.1+dfsg-1 Severity: normal Tags: a11y Dear Maintainer, I've noticed that even though the script pygmentize has been moved to python3-pygments, its manpage is still shipped within the python-pygments binary package (no man page in the python3-pygments). Cheers, Cédric -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python-pygments depends on: ii python 2.7.15-3 Versions of packages python-pygments recommends: ii python-chardet3.0.4-2 ii python-pkg-resources 40.6.2-1 Versions of packages python-pygments suggests: pn python-pygments-doc ii ttf-bitstream-vera 1.10-8 -- no debconf information
Bug#918236: transient bug in ruby-prawn
Control: tag -1 notfound ruby-prawn-svg/0.28.0-2 This was caused during the transition to ruby-prawn 2.2.0 during which a mismatch for version of ruby-ttfunk occurred. This is now solved, and has no root in this package. Closing. Cheers, Cédric signature.asc Description: PGP signature
Bug#918235: transient bug in ruby-prawn
Control: tag -1 notfound ruby-prawn-icon/2.3.0-2 This was caused during the transition to ruby-prawn 2.2.0 during which a mismatch for version of ruby-ttfunk occurred. This is now solved, and has no root in this package. Closing. Cheers, Cédric signature.asc Description: PGP signature
Bug#918605: fixed with 3.8.1-2 upload
Control: tag -1 fixed ryby-rspec-rails/3.8.1-2 Hi, This has been fixed with the upload of ruby-rspec-rails/3.8.1-2 in unstable. Cheers, Cédric signature.asc Description: PGP signature
Bug#918234: ruby-asciidoctor-pdf: FTBFS in sid
Package: ruby-asciidoctor-pdf Followup-For: Bug #918234 The log in the report corresponds to a transient bug during the update of ruby- prawn (earlier version depended on earlier version of ruby-ttfunk). So this part is gone. But the dependency check still fails now because of version mismatch of ruby-treetop: the gemspec file wants version 1.5.3 whereas the archive has 1.6.8 The solution is to patch further the gemspec file to relax strict dependency on this version of treetop. diff --git a/debian/patches/0001-Fix-dependencies-for-debian-build.patch b/debian/patches/0001-Fix-dependencies-for-debian-build.patch index 05748d1..589b7f4 100644 --- a/debian/patches/0001-Fix-dependencies-for-debian-build.patch +++ b/debian/patches/0001-Fix-dependencies-for-debian-build.patch @@ -14,11 +14,9 @@ Signed-off-by: Keith Packard lib/asciidoctor-pdf/prawn-templates_ext.rb | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) -diff --git a/asciidoctor-pdf.gemspec b/asciidoctor-pdf.gemspec -index 940bc9f..59b23c9 100644 --- a/asciidoctor-pdf.gemspec +++ b/asciidoctor-pdf.gemspec -@@ -43,10 +43,10 @@ An extension for Asciidoctor that converts AsciiDoc documents to PDF using the P +@@ -43,13 +43,13 @@ s.add_runtime_dependency 'prawn', '>= 1.3.0', '< 2.3.0' s.add_runtime_dependency 'prawn-table', '0.2.2' # prawn-templates >= 0.0.5 requires prawn >= 2.2.0, so we must cast a wider net to support Ruby 1.9.3 @@ -32,11 +30,13 @@ index 940bc9f..59b23c9 100644 s.add_runtime_dependency 'safe_yaml', '~> 1.0.4' s.add_runtime_dependency 'thread_safe', '~> 0.3.6' s.add_runtime_dependency 'concurrent-ruby', '~> 1.0.5' -diff --git a/lib/asciidoctor-pdf/prawn-templates_ext.rb b/lib/asciidoctor- pdf/prawn-templates_ext.rb -index fca8178..92fe260 100644 + # For our usage, treetop 1.6.2 is slower than 1.5.3 +- s.add_runtime_dependency 'treetop', '1.5.3' ++ s.add_runtime_dependency 'treetop', '>= 1.5.3' + end --- a/lib/asciidoctor-pdf/prawn-templates_ext.rb +++ b/lib/asciidoctor-pdf/prawn-templates_ext.rb -@@ -2,4 +2,4 @@ class Prawn::Document +@@ -2,4 +2,4 @@ # NOTE allows prawn-templates 0.0.4 to be used with prawn >= 2.2.0 const_set :VALID_OPTIONS, (send :remove_const, :VALID_OPTIONS).dup if VALID_OPTIONS.frozen? end -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ruby-asciidoctor-pdf depends on: ii ruby 1:2.5.1 ii ruby-asciidoctor 1.5.8-1 ii ruby-concurrent 1.0.5-2 ii ruby-prawn2.2.0+dfsg-1 ii ruby-prawn-icon 2.3.0-2 ii ruby-prawn-svg0.28.0-2 ii ruby-prawn-table 0.2.2-1 ii ruby-safe-yaml1.0.4-2 ii ruby-thread-safe 0.3.6-1 ii ruby-treetop 1.6.8-1 ruby-asciidoctor-pdf recommends no packages. ruby-asciidoctor-pdf suggests no packages. diff --git a/debian/patches/0001-Fix-dependencies-for-debian-build.patch b/debian/patches/0001-Fix-dependencies-for-debian-build.patch index 05748d1..589b7f4 100644 --- a/debian/patches/0001-Fix-dependencies-for-debian-build.patch +++ b/debian/patches/0001-Fix-dependencies-for-debian-build.patch @@ -14,11 +14,9 @@ Signed-off-by: Keith Packard lib/asciidoctor-pdf/prawn-templates_ext.rb | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) -diff --git a/asciidoctor-pdf.gemspec b/asciidoctor-pdf.gemspec -index 940bc9f..59b23c9 100644 --- a/asciidoctor-pdf.gemspec +++ b/asciidoctor-pdf.gemspec -@@ -43,10 +43,10 @@ An extension for Asciidoctor that converts AsciiDoc documents to PDF using the P +@@ -43,13 +43,13 @@ s.add_runtime_dependency 'prawn', '>= 1.3.0', '< 2.3.0' s.add_runtime_dependency 'prawn-table', '0.2.2' # prawn-templates >= 0.0.5 requires prawn >= 2.2.0, so we must cast a wider net to support Ruby 1.9.3 @@ -32,11 +30,13 @@ index 940bc9f..59b23c9 100644 s.add_runtime_dependency 'safe_yaml', '~> 1.0.4' s.add_runtime_dependency 'thread_safe', '~> 0.3.6' s.add_runtime_dependency 'concurrent-ruby', '~> 1.0.5' -diff --git a/lib/asciidoctor-pdf/prawn-templates_ext.rb b/lib/asciidoctor-pdf/prawn-templates_ext.rb -index fca8178..92fe260 100644 + # For our usage, treetop 1.6.2 is slower than 1.5.3 +- s.add_runtime_dependency 'treetop', '1.5.3' ++ s.add_runtime_dependency 'treetop', '>= 1.5.3' + end --- a/lib/asciidoctor-pdf/prawn-templates_ext.rb +++ b/lib/asciidoctor-pdf/prawn-templates_ext.rb -@@ -2,4 +2,4 @@ class Prawn::Document +@@ -2,4 +2,4 @@ # NOTE allows prawn-templates 0.0.4 to be used with prawn >= 2.2.0 const_set :VALID_OPTIONS, (send :remove_const, :VALID_OPTIONS).dup if VALID_OPTIONS.frozen? end
Bug#662960: ssmtp doesn't validate server TLS certificates
On 09/01/2019 16:44, Simon Deziel wrote: > On 2019-01-09 10:23 a.m., Cédric Dufour - Idiap Research Institute wrote: > ssmtp seems like abandonware. Have you tried msmtp(-mta)? It works in a > similar way, is well supported and does the right thing when you want TLS. Indeed. mstmp-mta works like a charm (just tested in Buster). Thanks for the tip. (I liked the extreme lightweight of ssmtp but so be it) PS: one might also look at esmtp(-run)
Bug#662960: ssmtp doesn't validate server TLS certificates
Any chance seeing this issue addressed or its severity lowered, so we can have the package in Buster ? Given its purpose - "extremely simple MTA [...]" - should this issue really be considered "serious" (and Release Critical) ? PS: ssmtp is extremely handy to forward machine-generated messages in large deployments, internally, iow. where TLS is not required
Bug#914546: failing test skipped in 3.7.1-2; decreasing bug severity
Control: severity -1 normal Control: tag -1 - ftbfs Hi, The bug has been reported upstream, and while waiting for a fix, the failing test is skipped in 3.7.1-2, so that this won't cause a ftbs. The bug is kept open, but severity is lowered to normal. Thanks, Cédric signature.asc Description: PGP signature
Bug#905648: skipping all tests, non-critical
Control: severity -1 normal As per upstream's advice, https://github.com/grosser/parallel/issues/227 tests are now skipped entirely (except naive library loading) since 1.12.1-2. The test failures are still present, but are not critical anymore because they don't lead to build failure. I am therefore lowering the severity Cedric signature.asc Description: PGP signature
Bug#915381: Shouldn't nvidia-persistenced be daemonized (using Debian standard way to do so) ?
On 03/12/2018 11:58, Andreas Beckmann wrote:
> Patches welcome! (Or a pull request against the repo on salsa.)
Well, maybe even simpler than a patch:
sed 's/__USER__/nvpd/g' \
init/systemd/nvidia-persistenced.service.template \
> debian/nvidia-persistenced.service
sed 's/__USER__/nvpd/g' \
init/sysv/nvidia-persistenced.template \
> debian/nvidia-persistenced.init
cat << EOF > debian/nvidia-persistenced.postinst
#!/bin/sh
set -e
case "$1" in
'configure')
if ! getent passwd nvpd >/dev/null; then
# Create ad-hoc system user/group
adduser --system --group \
--home /var/run/nvpd/ \
--gecos 'nVidia Persistence daemon' \
--no-create-home \
nvpd
fi
;;
esac
#DEBHELPER#
EOF
PS: you picked my curiosity; I'll have a look at what "salsa" might be ;-)
> We will probably not "fix" this for stretch (but stretch-backports),
> unless someone gets this approved by the release team (but let's have
> this in sid first.)
Totally understand.
It'd be nice to have it in Buster though.
> And it should work with both systemd and legacy sysv.
Applied to latest (Unstable) 390.25 source package, this passes compilation
using pbuilder and produces a package with the ad-hoc /etc/init.d script
and /lib/systemd/system service file (debhelper >= 10 takes care of the
SysV/SystemD configuration; no need for dh-systemd build dependency).
And it installs and works OK on Stretch (SystemD).
I can't tell about SysV, though the nVidia init script looks simple
enough. Maybe an additional debian/nvidia-persistenced.default with a
"START={yes,no}" stanza might be needed (vs Debian Policy ?)
> Andreas
Thanks for your addressing this issue on such short notice.
Cédric
PS: In my effort to backport the latest upstream (410.78) drivers to Stretch
(we need CUDA 10 and serie 20** support), I personally used the (pre-compiled)
nvidia-persistenced available in the nVidia "*.run" package and included it
in my custom nvidia-graphics-driver source package
Bug#915381: Shouldn't nvidia-persistenced be daemonized (using Debian standard way to do so) ?
Package: nvidia-persistenced Version: 390.25-1 Hello, nVidia made it clear to us that nvidia-persistenced *really* should be running on (headless/no X server) CUDA nodes, because it does *more* than just keep the driver "up" (in particular, it fixes erroneous outputs from nvidia-smi; e.g. wrong GPU perf-state/load/memory accross multi-GPU setups). I see the current (Stretch) and latest (Unstable) Debian packaging of nvidia-persistenced does not enable the binary as a daemon (but merely provides example sysv/systemd/upstart scripts, in /usr/share/doc). Is there a reason the Debian package does not enable this binary as a (sysv+systemd) daemon, along creating the ad-hoc system user (e.g. "nvpd") for it ? If not, could this be looked into (I can provide input based on my own re-packaging of the daemon) ? Thanks for your work and best regards, Cédric -- Cédric Dufour @ Idiap Research Institute
Bug#913404: builds but tests fail
Control: forwarded -1 https://github.com/taf2/curb/issues/369 The library builds with the following commit from upstream https://github.com/taf2/curb/commit/aa23bf67b0290882514385ad25659d4511c882d2 however, several test failures appear: https://github.com/taf2/curb/issues/369 signature.asc Description: PGP signature
Bug#911110: gradio: automatic codec installation isn't supported by your distribution
The gradio application says: automatic codec installation isn't supported by your distribution. Please install "gstreamer|1.0|gradio|MPEG-2 AAC decoder-audio/mpeg, mpegversion=(int)2, level=(string)1, profile=(string)lc" manually. From the point of view of a Flatpak app, "your distribution" is the Flatpak runtime (container) that it's running in, not Debian. gradio uses GStreamer plugins from the Flatpak runtime, not from Debian. That is really misleading. The Flatpak runtime that gradio uses is chosen by the maintainers of the gradio Flatpak app, so only they can solve this. I'd suggest reporting this at https://github.com/flathub/de.haeckerfelix.gradio/issues For the record, I've open a issue on github: https://github.com/haecker-felix/Gradio/issues/355 So it seems that somehow, flatpak could be able to automatically install the right package Flatpak automatically installs the runtime that the gradio app asks for (currently org.gnome.Platform version 3.28, although until a few days ago it was version 3.30). If that runtime isn't suitable, then that's a bug in the gradio app or a bug in the runtime. That makes things clearer in my mind. Thanks for your prompt answer. Let's then close this bug. smcv cED
Bug#911110: gradio: automatic codec installation isn't supported by your distribution
Package: flatpak Version: 1.0.4-1 Severity: normal Dear Maintainer, Hi, on a fresh debian install, after installing flatpak as follow: apt install flatpak apt install gnome-software-plugin-flatpak flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo reboot I tried to install gradio from here: https://flathub.org/apps/details/de.haeckerfelix.gradio The process did well. But after looking for the radio named: couleur3 with the thumbnail: https://upload.wikimedia.org/wikipedia/commons/thumb/3/3a/Couleur_3_logo.svg/360px- Couleur_3_logo.svg.png The gradio application says: automatic codec installation isn't supported by your distribution. Please install "gstreamer|1.0|gradio|MPEG-2 AAC decoder-audio/mpeg, mpegversion=(int)2, level=(string)1, profile=(string)lc" manually. So it seems that somehow, flatpak could be able to automatically install the right package, or at least provide a "apt install " to ease the installation -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CH:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages flatpak depends on: ii bubblewrap 0.3.1-2 ii libappstream-glib8 0.7.12-1 ii libarchive13 3.2.2-5 ii libc6 2.27-6 ii libglib2.0-0 2.58.1-2 ii libgpgme11 1.11.1-2 ii libjson-glib-1.0-0 1.4.4-1 ii libostree-1-1 2018.8-2 ii libpolkit-gobject-1-0 0.105-21 ii libseccomp22.3.3-3 ii libsoup2.4-1 2.64.1-3 ii libxau61:1.0.8-1+b2 ii libxml22.9.4+dfsg1-7+b1 ii xdg-desktop-portal 1.0.3-1 Versions of packages flatpak recommends: ii desktop-file-utils 0.23-4 ii gtk-update-icon-cache3.24.1-2 ii hicolor-icon-theme 0.17-2 ii libpam-systemd 239-10 ii p11-kit 0.23.14-2 ii policykit-1 0.105-21 ii shared-mime-info 1.10-1 ii xdg-desktop-portal-gtk [xdg-desktop-portal-backend] 1.0.2-2 Versions of packages flatpak suggests: ii avahi-daemon 0.7-4+b1 -- no debconf information
