[HOME] [DOWNLOAD] [DOCS] [NEWS] [SUPPORT] [TIPS] [ISSUES] [CONTRIBUTE] [DONATE]

Debian bullseye port

1. Note from Qubes R4.1 testers:

Package qubes-template-whonix-gw-15 available, but not installed.
No match for argument: qubes-template-whonix-gw-15
Error: No packages marked for reinstall
Fetching updates failed with code1; press Enter to exit

&

Yes I was able to install the template by enabling the templates-community-testing repo and then issuing this command: sudo qubes-dom0-update --enablerepo=qubes-templates-community qubes-template-whonix-gw-15 & sudo qubes-dom0-update --enablerepo=qubes-templates-community-testing qubes-template-whonix-ws-15

Note that the whonix wiki states to use the --action=upgrade or --action=reinstall argument which clearly failed to work in my case.

A bit confusing that R4.1 testers can’t install the template from the community repo which the whonix wiki insists on using.

I don’t know if we want to change anything i.e. since Qubes R4.1 will be stable soon enough?

Also, that reporter’s action to resolve it looks confusing i.e. enabling whonix-gw-15 from qubes-template-community, while whonix-ws-15 installed from qubes-templates-community-testing?

Why would ws and gw be available from different repos in that case? Weird.

2. Also, with Debian 11 released in two weeks (August 14), should there be some News announcement about upcoming Whonix 16? I know that you previously released Whonix 15 slightly before Debian 10 stable was released (from memory).

I don’t know anything other than the general public. No inside information. No news on that as far as I know.

Qubes-Whonix R4.1 plans generally:

That’s a Qubes issue. I don’t manage Qubes dom0 repositories.

Fedora upgrades (which Qubes dom0 is based on) and then on top of that the qubes-dom0-update is confusing. It might show “not available” while it actually means “installed and no other version found but let’s say not available”.

User didn’t follow instructions.
Instructions HowTo: Install the Stable Version of Qubes-Whonix ™ 15 do not mention sudo qubes-dom0-update --enablerepo [...].

Many Qubes specific quirks related to template installation. Related:

This time, no. I planned to wait until Debian 11 is released to avoid issues such as last time: apt-get error - E: Repository 'tor+https://cdn-aws.deb.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'testing' to 'stable'

Repository

deb tor+https://deb.debian.org/debian-security bullseye/updates main contrib non-free

does not exist yet.

Err:5 tor+https://deb.debian.org/debian-security bullseye/updates Release
404 Not Found [IP: 127.0.0.1 9050]
Reading package lists… Done
E: The repository ‘tor+https://deb.debian.org/debian-security bullseye/updates Release’ does not have a Release file.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

@patrick replace “bullseye/updates” with “bullseye-security”. the debian team changed the name.

https://www.debian.org/releases/bullseye/amd64/release-notes/ch-information.en.html#security-archive

1 Like

Release upgrades support:


Whonix 16 KVM status:

  • Whonix 15 KVM to Whonix 16 KVM release upgrades will likely be unsupported as per KVM maintainer decision. Similar to KVM Upgrade Instructions.
  • Wait for Whonix KVM release based on version 16.0.2.7.

Downloadable Whonix 16 for VirtualBox images:


Downloadable Qubes-Whonix 16 images status:

Also interesting:

Linux user namespaces - Chapter 5. Issues to be aware of for bullseye

Linux unprivileged bpf - Chapter 5. Issues to be aware of for bullseye

1 Like

Above post updated.


Discussion:


And locales-all package not installed by default in all Debian templates · Issue #4889 · QubesOS/qubes-issues · GitHub (maybe should be re-titled) - fixed (workaround) already in Whonix repository.

I successfully installed the kicksecure-cli on debian 11 from the bullseye-repo together with sdwdate, bootclockrandomization, security-misc etc.
However when I try to install kloak or tirdad, I get:

Note, selecting 'dummy-dependency' instead of 'kloak'
Note, selecting 'dummy-dependency' instead of 'tirdad'
The following NEW packages will be installed:
  dummy-dependency
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 54.2 kB of archives.
After this operation, 61.4 kB of additional disk space will be used.

I’m not in a hurry, so if these are not ready to be rolled out yet, I have every bit of patience, though when you said all packages are ported to Debian 11 and uploaded to the whonix-repo, it could also mean that there is some issue.

1 Like

Which hardware architecture? In other words, what’s the output of:

dpkg --print-architecture

?

Expected:

amd64

(means Intel64 and AMD64)

Otherwise, see:

dpkg --print-architecture

amd64

and

cat /etc/apt/sources.list.d/derivative.list

deb tor+https://deb.whonix.org bullseye main contrib non-free

1 Like

Fixed.

Thank you for fixing it.

build process issue:

[Imprint] [Privacy Policy] [Cookie Policy] [Terms of Use] [E-Sign Consent] [DMCA] [Contributors] [Investors] [Priority Support] [Professional Support]