That makes sense. That said, do you know of a way to configure sqv to
accept SHA-1 for keys?
Package: apt
Version: 2.9.23
Followup-For: Bug #1088288
Dear Maintainer,
The addition of default-sequoia.config has helped, but seems to be
incomplete. Slack still cannot be updated. It gives this error message:
Get:2 https://packagecloud.io/slacktechnologies/slack/debian jessie
InRele
Package: cups-browsed
Version: 1.28.15-1
Severity: normal
Dear Maintainer,
We include an apparmor profile for cups_browsed that implicitly denies the
SYS_NICE capability. This capability isn't actually needed by cups-browsed,
but is tested as part of startup.
I suggest we add a rule to debian
I think this is fixed upstream in 2.1.2; see
https://github.com/adrianlopezroche/fdupes/commit/c0dd064bb02b5496e1ef51fcc9eed11dd08b6268
I figured that would be the case; it’s a known upstream issue. Thanks for
confirming that I didn’t miss something obvious.
Should we mark the control file as breaks kernel < 590? Maybe just for
libcuda1 (not quite accurate, but has a result closer to the observed issue)?
Or just wait until i
Package: nvidia-kernel-dkms
Version: 455.38-1
Severity: normal
Thanks for the recent 450.80.02 update! I now can run the Nvidia driver with
the 5.9 kernel.
However, I cannot load the nvidia-uvm kernel module. When I try, the error
messages logged in dmesg are:
nvidia_uvm: Unknown symbol
Thanks for the new version! But it seems to introduce a regression.
After installing it on my bullseye box, I couldn't run CUDA programs
anymore. Normally, CUDA requires the nvidia-uvm module to be loaded.
However, loading the uvm module reports the following errors in dmesg:
nvidia_uvm: m
0.1.3+dfsg-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix HID extractBits for big-endian systems (Closes: #963201)
+
+ -- Joel Ray Holveck Mon, 28 Sep 2020 14:32:08 -0700
+
flightgear (1:2020.1.3+dfsg-1) unstable; urgency=medium
* New upstream version 2020.1.3+dfsg
8 matches
Mail list logo
