On 1/14/21 4:21 PM, Sven Semmler wrote:
Not sure where to go from here.
Can't seem to make it work on the plain debian templates. So my choices are:
a) debian-minimal based kicksecure
b) fedora-minimal
The reason I wanted to have "plain" debian-minimal was to get more
minimal (less space /
Hi,
My 'Qubes Updates' notifier told me there were updates available for the
dom0.
I tried running my usual command:
qubes-dom0-update --enablerepo=qubes-dom0-security-testing --clean
but I am getting the error below. Any ideas? This is Qubes 4.0, and the
Debian repository for my
On 1/13/21 9:11 PM, Sven Semmler wrote:
So my strategy is to see which additional packages kicksecure installs
in the system.
Didn't work out. None of the packages that are not specific to
kicksecure and are part of the normal debian repo fix the issue. Neither
does debian-10 full.
Not
On 1/14/21 11:06 AM, Sven Semmler wrote:
Actually I am unsure about debian-10 ... but definitely kicksecure
(debian based) and fedora.
Yup, debian-10 full also doesn't work.
Found this: https://github.com/QubesOS/qubes-issues/issues/4276
Ignore, this is unrelated.
--
public key:
OK, reported, some optimization attempts included:
https://groups.google.com/g/qubes-users/c/uTi3QHuhdy8
Also, I have some temptation to reimplement qubes-i3status as a Python
wrapper around the original i3status. We would probably also resolve some
other problems. For example, I had to fix
On 1/13/21 9:11 PM, Sven Semmler wrote:
That was with kicksecure (installed on top of debian-10-minimal by
following https://www.whonix.org/wiki/Kicksecure/Debian) as well as
a full debian-10 and fedora-?? (long ago) template.
Actually I am unsure about debian-10 ... but definitely kicksecure
