Bug#1063076: asio: binary-any FTBFS
Ah shit, ftp-masters reject my new version to DEFERRED without notifying me but email. Thanks for the pointer, will fix it ASAP. Cheers, Stephan
Bug#1054750: reuse: FTBFS: make: *** [debian/rules:4: binary] Error 1
Caused by dh-python #1055008
Bug#1017594: cppzmq-dev: missing Replaces
As per policy: > This usage of Replaces only takes effect when both packages are at > least partially on the system at once. It is not relevant if the > packages conflict unless the conflict has been overridden. If I get this paragraph right, this will never happen since cppzmq breaks zeromq3 << 4.3.4-3 anyway and a) zeromq3 has no dependency on cppzmq at all b) cppzmq is in a different source package, so dpkg will upgrade zeromq3 and then install cppzmq At least I had no installation problems. Let me know if I got this wrong. Regards, Stephan
Bug#1017432: horizon-eda: zmq.hpp now in cppzmq-dev
Source: horizon-eda Version: 2.2.0-1 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: stephanlach...@debian.org The zmq.hpp header moved from libzmq3-dev to cppzmq-dev. To fix this just replace libzmq3-dev with cppzmq-dev in d/control. Regards, Stephan -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1012120: libwww-dict-leo-org-perl: does not connect anymore
Package: libwww-dict-leo-org-perl Version: 2.02-2 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: stephanlach...@debian.org, gre...@debian.org The package does not seem to work anymore. Calling it results in `Connection failed:` with no further information. Tested on multiple networks and machines. A debug log is given below. Probably an upstream issue. Cheers, Stephan Debug log: $ leo --debug test %DEBUG: connecting to site: dict.leo.org port 443 %DEBUG: GET /dictQuery/m-vocab/ende/query.xml?lp=ende&search=test HTTP/1.0 Connection failed: $ -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-3-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libwww-dict-leo-org-perl depends on: ii libio-socket-ssl-perl 2.074-2 ii liburi-encode-perl 1.1.1-1 ii libxml-simple-perl 2.25-1 ii perl 5.34.0-4 libwww-dict-leo-org-perl recommends no packages. libwww-dict-leo-org-perl suggests no packages. -- no debconf information
Bug#1001237: ptl: autopkgtest regression on armhf: Floating point exception
Control: forwarded -1 https://github.com/jrmadsen/PTL/issues/25 Hi Lukas, On Mon, 13 Dec 2021 15:39:18 +0100 =?utf-8?q?Lukas_M=C3=A4rdian?= wrote: > I can observe the same issue with 2.3.0-1 on Ubuntu and filed an upstream bug > at https://github.com/jrmadsen/PTL/issues/25 > > The intmax_t division seems to be the root-cause here, replacing the division > in the minimal.cc example with a constant is a (temporary) way to mitigate > this > problem. Thanks for looking into this! I didn't have the time to do it. Since I saw you fixed this upstream and 2.3.1 was released after that, I have uploaded the new version instead of adding the patch. Thanks again, Stephan
Bug#1000833: src:python-license-expression: Package licenses not properly documented in debian/copyright
On Mon, 29 Nov 2021 16:33:17 -0500 Scott Kitterman wrote: > Package: src:python-license-expression > Version: 21.6.14-1 > Severity: serious > Justification: Policy 4.5 > > As mentioned during the review in New: > > I am going to accept this and file a bug because the issue alread exists in > the archive from the current package. The package debian/copyright claims > that _pyahocorasick.py is public domain. This appears to be incorrect. If > you check the source of the code documented in _pyahocorasick.ABOUT, it says > the license in BSD 3-Clause. See: > > https://github.com/WojciechMula/pyahocorasick/blob/master/LICENSE > > Scott K > > Hi Scott, I think this is incorrect. If you look at src/license_expression/_pyahocorasick.ABOUT, you will find the link to the file they imported [1]. Those files are clearly marked as public domain in their header. The overall project license might be BSD-3-Clause, but the python files are licensed differently. Please close this if you agree with my assessment. Regards, Stephan [1] https://github.com/WojciechMula/pyahocorasick/tree/ec2fb9cb393f571fd4316ea98ed7b65992f16127/py
Bug#992277: protontricks: With any command, fails with "KeyError: 'LibraryFolders'"
Hi,
thanks for reporting. I can confirm this. I will fix it with the version
1.6.0, which has been released 3 weeks ago.
Since I don't have much time right now, it will probably stay in this
state for the next couple of weeks (sorry).
Regards
Stephan
On Mon, 16 Aug 2021 09:48:41 -0700 Brian Vaughan
wrote:
> Package: protontricks
> Version: 1.5.0-1
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: bgvaug...@gmail.com
>
> Dear Maintainer,
>
> Simply executing 'protontricks' shows the usage instructions.
Executing it with
> commands results in a Python error message.
>
> $ protontricks -s "No Man's Sky"
> Traceback (most recent call last):
> File "/usr/bin/protontricks", line 33, in
> sys.exit(load_entry_point('protontricks==1.5.0', 'console_scripts',
> 'protontricks')())
> File "/usr/lib/python3/dist-packages/protontricks/cli.py", line 167,
in main
> steam_lib_paths = get_steam_lib_paths(steam_path)
> File "/usr/lib/python3/dist-packages/protontricks/steam.py", line 613, in
> get_steam_lib_paths
> library_folders = parse_library_folders(folders_vdf_path.read_text())
> File "/usr/lib/python3/dist-packages/protontricks/steam.py", line 597, in
> parse_library_folders
> Path(value) for key, value in vdf_data["LibraryFolders"].items()
> KeyError: 'LibraryFolders'
>
> $ protontricks --gui
> Traceback (most recent call last):
> File "/usr/bin/protontricks", line 33, in
> sys.exit(load_entry_point('protontricks==1.5.0', 'console_scripts',
> 'protontricks')())
> File "/usr/lib/python3/dist-packages/protontricks/cli.py", line 167,
in main
> steam_lib_paths = get_steam_lib_paths(steam_path)
> File "/usr/lib/python3/dist-packages/protontricks/steam.py", line 613, in
> get_steam_lib_paths
> library_folders = parse_library_folders(folders_vdf_path.read_text())
> File "/usr/lib/python3/dist-packages/protontricks/steam.py", line 597, in
> parse_library_folders
> Path(value) for key, value in vdf_data["LibraryFolders"].items()
> KeyError: 'LibraryFolders'
>
> I had previously installed protontricks as a normal user, using pipx,
following
> the instructions at https://github.com/Matoking/protontricks and used it
> successfully. I uninstalled it, using pipx, prior to installing the
Debian
> package.
>
>
> -- System Information:
> Debian Release: 11.0
> APT prefers unstable
> APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.10.0-8-amd64 (SMP w/12 CPU threads)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
> TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE not
> set
> Shell: /bin/sh linked to /usr/bin/dash
Bug#988056: shim-signed: Fails to install due to missing update-secureboot-policy
I can confirm this. Regards, Stephan
Bug#981520: minigalaxy: Shows a browser login window without any proof of origin (no URL, no HTTPS indicator, no chance to review SSL certificate, etc.)
Control: severity -1 wishlist Control: forwarded -1 https://github.com/sharkwouter/minigalaxy/issues/282 Control: tags -1 upstream Hi, thanks for your bug report. I've taken a look into it and I reduced the severity for a couple of reasons. > On startup it shows a login window which looks suspiciously like a GOG > login window in a web browser, but without without any possibility to > check its origin: It has no location bar, i.e. shows no URL, it doesn't > indicate if the entered credentials are transmitted encrypted via HTTPS > or not, and it offers no chance to review the HTTPS TLS certificate if > present. Since Minigalaxy is open source, it's very easy to check if it connects actually to GOG via https. I checked the code and it is fine. This problem actually isn't solved by showing an address bar or the certificate, since that can easily be spoofed. It could just connect to GOG to show the certificate but also connect to a different, similar looking website and show it to the user. This applies to all browsers, that is why open source is important. > Possible solution: Don't use an embedded browser windows but call > sensible-browser or so to use the browser which the user is probably > already logged in to GOG anyways. In the forwarded bug report the maintainer states that an external browser is not a solution at the moment. Their argumentation sounds reasonable to me. However, I will look into adding the address, as it probably is not a bad idea. But this is more of a wishlist thing, not an actual security concern (at least to me). Regards, Stephan
Bug#980554: lutris: Crash on first when opening ~/.local/share/lutris/runtime/dxvk/dxvk_versions.json
Control: tags confirmed fixed-upstream I can confirm the behavior. It has nothing to do with an internet connection like I assumed before. I'm upload a new version with a fix from upstream [1][2]. Thanks for reporting this. Regards Stephan Lachnit [1] https://github.com/lutris/lutris/commit/1be0d6e5404068f5eeb8f6849f59b52e879f662a [2] https://github.com/lutris/lutris/commit/9328c3268164f1201f7bdb3f6c28f4b7bd314200
Bug#980554: lutris: Crash on first when opening ~/.local/share/lutris/runtime/dxvk/dxvk_versions.json
I have a suspicion, which is that this is due to the Lutris Runtime missing. Did you have an internet connection when you launched it the first time? I'll try it on a live image tomorrow as well. Regards Stephan
Bug#976245: mugshot: Muhshot fails with AttributeError: 'ElementTree' object has no attribute 'getiterator' in console
Can confirm, currently unusable. Has been fixed upstream [1], but no new release yet. The fix should be added as patch or upstream should be asked for a new release before Bullseye. Regards, Stephan [1] https://github.com/bluesabre/mugshot/commit/643b3d005a8865c961b836aeae4c1f76711646e9
Bug#977246: lutris should depend on python3-dbus
Hi, thanks for discovering this missing dependency. Since I closely follow the upstream Debian sources, I created a PR there: https://github.com/lutris/lutris/pull/3349 Depending on the schedule for a new release I will either backport this or wait for the new release. Kinda depends on how much time I have. Regards, Stephan
Bug#914587: blueman: broken package
Package: blueman Version: 2.0.6-1 Severity: grave Tags: newcomer Justification: renders package unusable Dear Maintainer, this package has wrong python dependencies. It should depend on the python3.6 package or python3 (< 3.7), because it doesn't install on latest Debian Sid (unstable). -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages blueman depends on: ii bluez 5.50-1 ii bluez-obexd 5.50-1 ii dbus 1.12.10-1 ii dbus-user-session [default-dbus-session-bus] 1.12.10-1 ii dbus-x11 [dbus-session-bus] 1.12.10-1 ii dconf-gsettings-backend [gsettings-backend] 0.30.1-1 pn gir1.2-appindicator3-0.1 ii gir1.2-gdkpixbuf-2.0 2.38.0+dfsg-6 ii gir1.2-glib-2.0 1.58.0-1 ii gir1.2-gtk-3.03.24.1-2 ii gir1.2-notify-0.7 0.7.7-3 ii gir1.2-pango-1.0 1.42.4-4 ii gnome-icon-theme 3.12.0-3 ii libbluetooth3 5.50-1 ii libc6 2.27-8 ii libglib2.0-0 2.58.1-2 ii libpulse-mainloop-glib0 12.2-2 ii libpython3.6 3.6.7-1 ii librsvg2-common 2.44.9-1 ii notification-daemon 3.20.0-3 ii python3 3.7.1-2 ii python3-cairo 1.16.2-1+b1 ii python3-dbus 1.2.8-2+b1 ii python3-gi3.30.2-1 ii python3-gi-cairo 3.30.2-1 ii xfce4-notifyd [notification-daemon] 0.4.2-1 Versions of packages blueman recommends: ii policykit-1 0.105-21 ii pulseaudio-module-bluetooth 12.2-2 blueman suggests no packages.
