Bug#998215: closed by Debian FTP Masters (reply to Drew Parsons ) (Bug#998215: fixed in h5py 3.3.0-4)
Control: reopen -1 On Thu, Nov 04, 2021 at 01:54:07AM +, Debian Bug Tracking System wrote: >... > h5py (3.3.0-4) unstable; urgency=medium >... > - skip_ros_test_no_net.patch skips test_ros3 (catches OSError) if >network is not available. Needed since libhdf5 is now built with >ROS (S3) support, but network access is not available on buildd >servers. Closes: #998215. >... This is not sufficient, policy says [1]: For packages in the main archive, required targets must not attempt network access Packages must not even *attempt* to call home and try to inform someone that the package is being built. cu Adrian [1] https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules
Bug#999649: ckon: homepage change
Package: ckon Severity: wishlist Dear Maintainer, The current homepage seems unavailable. http://tschaume.github.com/ckon I think it can be changed to the following. https://tschaume.github.io/ckon/ -- System Information: Debian Release: 10.11 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-proposed-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-18-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE=nl_NL.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 ckon depends on: ii libboost-filesystem1.67.0 1.67.0-13+deb10u1 ii libboost-program-options1.67.0 1.67.0-13+deb10u1 ii libboost-regex1.67.01.67.0-13+deb10u1 ii libboost-system1.67.0 1.67.0-13+deb10u1 ii libc6 2.28-10 ii libcurl47.64.0-4+deb10u2 ii libgcc1 1:8.3.0-6 ii libstdc++6 8.3.0-6 ckon recommends no packages. ckon suggests no packages.
Bug#999648: solaar: Version 1.0.7 works with the G Pro X Superlight but not the Debian package
Package: solaar
Version: 1.0.7+dfsg-1
Severity: normal
X-Debbugs-Cc: s...@becker-lan.de
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Solaar 1.0.7 (git) supporting the new device, so i installed 1.0.7 from repos,
as soon it was available.
* What exactly did you do (or not do) that was effective (or
ineffective)?
if I install the 1.0.7 from the repo it doesnt find a known protocol
* What was the outcome of this action?
09:50:40,941 WARNING [ReceiverListener:hidraw7]
logitech_receiver.notifications: 1: connection notification with unknown
protocol 11: Notification(10,1,41,11,329340)
* What outcome did you expect instead?
If i manually download an run the release 1.0.7 from GitHub the "Logitech Pro X
Wireless Superlight" Mouse connects successful:
09:50:29,937 INFO [ReceiverListener:hidraw7] solaar.listener:
status_changed : paired online, {'LINK
ENCRYPTED': True, 'BATTERY LEVEL': 97, 'BATTERY STATUS': NamedInt(0,
'discharging'), 'BATTERY NEXT LEVEL': None, 'BATTERY VOLTAGE': None, 'BATTERY
CHARGING': False, 'ERROR': None} (0)
If i exchange the binaries, it still won´t find any, so i suspect it is a
missing library in the Debian package.
Thank you
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.14.0-2-amd64 (SMP w/12 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages solaar depends on:
ii adduser 3.118
ii debconf [debconf-2.0]1.5.79
ii gir1.2-ayatanaappindicator3-0.1 0.5.5-3
ii gir1.2-gtk-3.0 3.24.30-3
ii gir1.2-notify-0.70.7.9-3
ii passwd 1:4.8.1-1.1
ii python3 3.9.7-1
ii python3-gi 3.42.0-1+b1
ii python3-psutil 5.8.0-2
ii python3-pyudev 0.22.0-2
ii python3-xlib 0.29-1
ii python3-yaml 5.4.1-1
ii udev 249.5-2
Versions of packages solaar recommends:
ii python3-dbus 1.2.18-3
ii upower0.99.13-1
solaar suggests no packages.
-- debconf information:
solaar/use_plugdev_group: false
Bug#999647: squid-deb-proxy: Hompage and VCS control still actual?
Package: squid-deb-proxy Severity: wishlist I wonder whether the field homepage and VCS-* are still up to date, the github location seems equivalent, and in terms of the homepage field also more informative. If you agree with my bikesheed color, maybe update it? Otherwise just ignore me and close this bug :) Cheers, -- tobi
Bug#999544: Update golang-v2ray-core to new upstream
Hello Roger, On 14/11/2021 09:11, Roger Shimizu wrote: > Dear Aloïs, > > Thanks for your work to go packages! > Sorry I don't have time lately. So if you can update the packages and > fix the RC bugs, it'd be appreciated. > Sure thing. The only thing is: have you push the upstream branch on the repository? It looks like there's none and therefore `gbp import-orig --uscan` is failing: ``` creekorful@debuild:~/code/golang-v2ray-core$ gbp import-orig --uscan gbp:error: Repository does not have branch 'upstream' for upstream sources. If there is none see file:///usr/share/doc/git-buildpackage/manual-html/gbp.import.html#GBP.IMPORT.CONVERT on howto create it otherwise use --upstream-branch to specify it. ``` It could be really helpful if you either push upstream branch or explain me which workflow you are using. > Cheers, > Roger > Cheers, -- Aloïs Micard GPG: DA4A A436 9BFA E299 67CD E85B F733 E871 0859 FCD2
Bug#999646: squid-deb-proxy-client: uncaptured python exception breaks client
Package: squid-deb-proxy-client
Version: 0.8.15+nmu1
Severity: grave
Justification: breaks the client.
Control: tags -1 patch fixed-upstream
Dear Michael,
The client currently breaks with exmitting an error message to stdout:
error: uncaptured python exception, closing channel ('', 3142, 0, 0): 9223372036854775807 (:[Errno 111] Connection refused
[/usr/lib/python3.9/asyncore.py|read|83]
[/usr/lib/python3.9/asyncore.py|handle_read_event|417]
[/usr/lib/python3.9/asyncore.py|handle_connect_event|425])
error: uncaptured python exception, closing channel
('', 3142, 0, 0): 9223372036854775807 (:[Errno 111] Connection refused
[/usr/lib/python3.9/asyncore.py|read|83]
[/usr/lib/python3.9/asyncore.py|handle_read_event|417]
[/usr/lib/python3.9/asyncore.py|handle_connect_event|425])
error: uncaptured python exception, closing channel
(':[Errno 111] Connection refused
[/usr/lib/python3.9/asyncore.py|read|83]
[/usr/lib/python3.9/asyncore.py|handle_read_event|417]
[/usr/lib/python3.9/asyncore.py|handle_connect_event|425])
error: uncaptured python exception, closing channel
('A_IPV4_IN_THE_LAN', 3142): 9223372036854775807 (:[Errno 111] Connection refused
[/usr/lib/python3.9/asyncore.py|read|83]
[/usr/lib/python3.9/asyncore.py|handle_read_event|417]
[/usr/lib/python3.9/asyncore.py|handle_connect_event|425])
http://https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1505670;
The fix upstream is
https://github.com/mvo5/squid-deb-proxy/commit/604ba3f98beff25a8fd51783d3ffc4db5e987dab
(attaching for reference)
--
tobi
-- System Information:
Debian Release: 11.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-7-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages squid-deb-proxy-client depends on:
ii apt 2.2.3
ii avahi-utils 0.8-5
ii python3 3.9.2-3
squid-deb-proxy-client recommends no packages.
squid-deb-proxy-client suggests no packages.
-- no debconf information
>From 604ba3f98beff25a8fd51783d3ffc4db5e987dab Mon Sep 17 00:00:00 2001
From: Michael Vogt
Date: Thu, 30 Sep 2021 10:06:00 +0200
Subject: [PATCH] apt-avahi-discover: use syslog for logging in AptAvahiClient
Patch from `jasonpe...@gmail.com` - thanks!
Fixes LP: #1505670
---
apt-avahi-discover | 6 ++
1 file changed, 6 insertions(+)
diff --git a/apt-avahi-discover b/apt-avahi-discover
index dfd579b..11cc25a 100755
--- a/apt-avahi-discover
+++ b/apt-avahi-discover
@@ -10,6 +10,7 @@ import socket
import sys
import time
from subprocessimport Popen, PIPE, call
+from syslog import syslog, LOG_INFO, LOG_USER
DEFAULT_CONNECT_TIMEOUT_SEC = 2
@@ -58,6 +59,11 @@ class AptAvahiClient(asyncore.dispatcher):
def __repr__(self):
return "<{}> {}: {}".format(
self.__class__.__name__, self.addr, self.time_to_connect)
+def log(self, message):
+syslog((LOG_INFO|LOG_USER), '%s\n' % str(message))
+def log_info(self, message, type='info'):
+if type not in self.ignore_log_types:
+self.log('%s: %s' % (type, message))
def is_ipv6(a):
Bug#999645: keybase: Uninstallable in Debian 11
Package: keybase Version: 5.8.1-20210930160723.fefa22edc1 Severity: grave Tags: upstream Justification: renders package unusable Some of the dependencies are not available on Debian 11. The package is uninstallable. -- System Information: Debian Release: 11.1 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 5.10.0-9-amd64 (SMP w/8 CPU threads) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 keybase depends on: ii fuse3 [fuse] 3.10.3-2 pn libappindicator1 ii libasound21.2.4-1.1 pn libgconf-2-4 ii libgtk-3-03.24.24-4 ii libnss3 2:3.61-1 ii libxss1 1:1.2.3-1 ii libxtst6 2:1.2.3-1 ii lsof 4.93.2+dfsg-1.1 ii procps2:3.3.17-5 ii psmisc23.4-2 keybase recommends no packages. keybase suggests no packages.
Bug#999644: RM: tumgreyspf -- RoQA; RC buggy, upstream vanished
Package: ftp.debian.org Severity: normal This missed the last release and requires porting to a newer Python. Upstream has also shutdown. I don't think it serves a point to keep this in Debian anymore. Maintainer is cc'ed in case he has a different view. Scott K
Bug#999544: Update golang-v2ray-core to new upstream
Dear Aloïs, Thanks for your work to go packages! Sorry I don't have time lately. So if you can update the packages and fix the RC bugs, it'd be appreciated. Cheers, Roger On Fri, Nov 12, 2021 at 5:22 PM Aloïs Micard wrote: > > Hello there, I hope you are doing fine! > > I don't know if you recall me, but we've worked a bit together > on Go packages in the past (al...@micard.lu). :) > > I have a request regarding golang-v2ray-core: > > The package will be removed on 01-12-21 because of error with Go 1.17 > which is now the defaults in the archive. > > I wanted to update golang-v2ray-core to latest upstream (4.43.0) and backport > the commit > https://github.com/v2fly/v2ray-core/commit/77b88171d6bd837b76a5ad6e6b23689391530ed6 > in order to get the package to build with Go 1.17 and allow transition to > testing of > golang-github-lucas-clemente-quic-go which is needed to prevent Syncthing > from being > RM of testing. > > The thing is: the Salsa repository for golang-v2ray-core doesn't have > upstream branch, > therefore I'm unable to import new upstream via gbp: > > > ``` > creekorful@debuild:~/code/golang-v2ray-core$ gbp import-orig --uscan > gbp:error: > Repository does not have branch 'upstream' for upstream sources. If there is > none see > file:///usr/share/doc/git-buildpackage/manual-html/gbp.import.html#GBP.IMPORT.CONVERT > on howto create it otherwise use --upstream-branch to specify it. > ``` > > Have you forgot to push upstream branch to Salsa? Or are you using a special > workflow? > > If you can either import latest upstream or push missing upstream branch it > would > be greatly helpful. > > Many thanks. > > Cheers, > > -- > Aloïs Micard > > GPG: DA4A A436 9BFA E299 67CD E85B F733 E871 0859 FCD2
Bug#998907: closed by Håvard Flaget Aasen (Closing, CVE marked as unimportant)
Hi Håvard, On Fri, Nov 12, 2021 at 11:21:08PM +, Debian Bug Tracking System wrote: [...] > CVE-2021-40985 has now been marked as unimportant, I'm therefore > closing this bug, since the CVE was the sole purpose of the update. > > Regards, > Håvard In case this was just caused by a uncertainity what is acceptable to fix via a point release and what not: I guess SRM will accept updates in stable as well for simpler bugfixes with low severity (even more if you had already prepared the debdiff as attached to this bug and as well #998902). Regards, Salvatore
