qvm-template install -y --enablerepo=qubes-templates-community-testing kali-core should work!
for more infos at this stage of install, please go: Kali Linux Metapackages | Kali Linux Documentation
I’ve tried to install with this command
sudo apt install kali-linux-default
but I get an error that says
E: Unable to locate package kali-linux-default
Is there some thing I’m missing?
edit: I’ve also tried a full upgrade and get 0 updates
Have you tried before `sudo apt update (just confirming). I ask this because since it’s a new template, it must have new updates.
Something got wrong in the derivation of Debian, it has not Kali stuff into. I need to see what went wrong.
2 Likes
Ok I’ve identified the problem, it’s a problem due to branch name…going to fix that and run a new build. Sorry.
3 Likes
When I run sudo apt update in the kali template I get the following error:
Hit:1 https://deb.debian.org/debian bullseye InRelease
Hit:2 https://deb.qubes-os.org/r4.1/vm bullseye InRelease
Hit:4 https://deb.debian.org/debian-security bullseye-security InRelease
Get:3 http://ftp.halifax.rwth-aachen.de/kali kali-rolling InRelease [41.5 kB]
Err:3 http://ftp.halifax.rwth-aachen.de/kali kali-rolling InRelease
The following signatures were invalid: EXPKEYSIG ED444FF07D8D0BF6 Kali Linux Repository <devel@kali.org>
Fetched 41.5 kB in 2s (18.6 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
32 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ftp.halifax.rwth-aachen.de/kali kali-rolling InRelease: The following signatures were invalid: EXPKEYSIG ED444FF07D8D0BF6 Kali Linux Repository <devel@kali.org>
W: Failed to fetch http://http.kali.org/kali/dists/kali-rolling/InRelease The following signatures were invalid: EXPKEYSIG ED444FF07D8D0BF6 Kali Linux Repository <devel@kali.org>
W: Some index files failed to download. They have been ignored, or old ones used instead.
I’m guessing I need to update the gpg keys, but I’m not sure how.
Attempted using the Qubes Updater tool & received this error:
Updating kali
Error on updating kali: Command '['sudo', 'qubesctl', '--skip-dom0', '--targets=kali', '--show-output', 'state.sls', 'update.qubes-vm']' returned non-zero exit status 20.
kali:
----------
ID: update
Function: pkg.uptodate
Result: False
Comment: Problem encountered upgrading packages. Additional info follows:
result:
----------
pid:
3799
retcode:
100
stderr:
Running scope as unit: run-reb32658240f24ec78a65bec149785f7b.scope
E: Packages were downgraded and -y was used without --allow-downgrades.
stdout:
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following package was automatically installed and is no longer required:
qubes-thunderbird
Use 'apt autoremove' to remove it.
The following packages have been kept back:
qubes-core-agent-dom0-updates qubes-pdf-converter qubes-thunderbird
The following packages will be upgraded:
libqrexec-utils2 libqubes-rpc-filecopy2 libqubesdb libvchan-xen
pulseaudio-qubes python3-qubesdb python3-qubesimgconverter qubes-core-agent
qubes-core-agent-nautilus qubes-core-agent-network-manager
qubes-core-agent-networking qubes-core-agent-passwordless-root
qubes-core-qrexec qubes-gpg-split qubes-gui-agent qubes-img-converter
qubes-input-proxy-sender qubes-kernel-vm-support
qubes-mgmt-salt-vm-connector qubes-usb-proxy qubes-utils
qubes-vm-dependencies qubes-vm-recommended qubesdb qubesdb-vm
xen-utils-guest xserver-xorg-input-qubes xserver-xorg-qubes-common
xserver-xorg-video-dummyqbs
The following packages will be DOWNGRADED:
gir1.2-polkit-1.0 libpolkit-agent-1-0 libpolkit-gobject-1-0 policykit-1
python3-xcffib
29 upgraded, 0 newly installed, 5 downgraded, 0 to remove and 3 not upgraded.
Started: 02:56:24.849635
Duration: 18635.671 ms
Changes:
----------
ID: notify-updates
Function: cmd.run
Name: /usr/lib/qubes/upgrades-status-notify
Result: True
Comment: Command "/usr/lib/qubes/upgrades-status-notify" run
Started: 02:56:43.489043
Duration: 5494.793 ms
Changes:
----------
pid:
3804
retcode:
0
stderr:
stdout:
Summary for kali
------------
Succeeded: 1 (changed=1)
Failed: 1
------------
Total states run: 2
Total run time: 24.130 s
Just installed the kali-core template, but it looks like there aren’t no kali repos inside the sources.list file. I don’t know if it’s a new bug or still the one due to the Debian derivation problem
1 Like
Read three posts before…
Thanks Frederic, just let us know, when the new build is ready.
Updated: qubes-template-kali-core 4.2.0-202402081323 (r4.2) · Issue #4415 · QubesOS/updates-status · GitHub
I’ve started it, we should have everything needed now 
3 Likes
working now for me… kali-linux-default package is currently installing…
Do you mean kali-core?
Does not work for me. Using sys-firewall download stays at 0%.
Using sys-whonix I don’t get any response at all.
Download via sys-whonix takes some minutes until you recognize, download is moving on.
But you should download the new kali-core template with qvm-template install --enablerepo=qubes-templates-community-testing kali-core command
Download works now with sys-firewall for me too.
Installation not:
$ qvm-template install ./qubes-template-kali-core-0\:4.2.0-202402081323.rpm
ERROR: Signature verification failed -: digests SIGNATURES NOT OK
$ md5sum qubes-template-kali-core-0\:4.2.0-202402081323.rpm
b1f2d5d280e36168f5b080082477a118 qubes-template-kali-core-0:4.2.0-202402081323.rpm
$ sha256sum qubes-template-kali-core-0\:4.2.0-202402081323.rpm
c51be99e8a3c2afebe4d44340746501f4523a7cf140486f44d2eadad0e42e22a qubes-template-kali-core-0:4.2.0-202402081323.rpm
@TheGardner you had no problems, right?
edit:
Just used qvm-template install instead of qvm-template download and installation works.
For future endeavors: what would be the proper command to install a local .rpm?
Your way should be the best for installing a local .rpm. In 90% of the cases it should work. But as long, as a install/ile/.rpm is available via the qubes repositories, I ALWAYS would suggest to install via the qubes QVM routines (i.e. qvm-template install --enablerepo=qubes-templates-<reponame> <templatename>)
The latter was working for me last Saturday!
Facing now the first problems. After download and install of the kali-core template, it now shows the first ‘update available’ messages in Qubes Updater, but whenever I try to run an update (just a single update for my virgin kali-core-original template only), I getting the following errors:
Updating kali-core-original
Fail to fetch Packages: Index of /kali/ kali-rolling/main amd64 Packages from http://mirror.pyratelan.org/kali/dists/kali-rolling/main/binary-amd64/Packages.gz
Fail to fetch Contents-amd64: Index of /kali/ kali-rolling/main amd64 Contents (deb) from http://mirror.pyratelan.org/kali/dists/kali-rolling/main/Contents-amd64.gz
Fail to fetch Packages: Index of /kali/ kali-rolling/main amd64 Packages from http://mirror.pyratelan.org/kali/dists/kali-rolling/main/binary-amd64/Packages.gz
Fail to fetch Contents-amd64: Index of /kali/ kali-rolling/main amd64 Contents (deb) from http://mirror.pyratelan.org/kali/dists/kali-rolling/main/Contents-amd64.gz
Fail to fetch Packages: Index of /kali/ kali-rolling/main amd64 Packages from http://mirror.pyratelan.org/kali/dists/kali-rolling/main/binary-amd64/Packages.gz
Fail to fetch Contents-amd64: Index of /kali/ kali-rolling/main amd64 Contents (deb) from http://mirror.pyratelan.org/kali/dists/kali-rolling/main/Contents-amd64.gz
Fail to fetch Packages: Index of /kali/ kali-rolling/main amd64 Packages from http://mirror.pyratelan.org/kali/dists/kali-rolling/main/binary-amd64/Packages.gz
Fail to fetch Contents-amd64: Index of /kali/ kali-rolling/main amd64 Contents (deb) from http://mirror.pyratelan.org/kali/dists/kali-rolling/main/Contents-amd64.gz
Fail to fetch Packages: mirrors.dotsrc.org kali-rolling/main amd64 Packages from http://mirrors.dotsrc.org/kali/dists/kali-rolling/main/binary-amd64/Packages.gz
Fail to fetch Contents-amd64: Index of / kali-rolling/main amd64 Contents (deb) from http://http.kali.org/kali/dists/kali-rolling/main/Contents-amd64.gz
Fail to fetch Packages: Index of /kali/ kali-rolling/main amd64 Packages from http://mirror.pyratelan.org/kali/dists/kali-rolling/main/binary-amd64/Packages
Fail to fetch Contents-amd64: Index of /kali/ kali-rolling/main amd64 Contents (deb) from http://mirror.pyratelan.org/kali/dists/kali-rolling/main/Contents-amd64
Fail to fetch Packages: Index of / kali-rolling/main amd64 Packages from http://http.kali.org/kali/dists/kali-rolling/main/binary-amd64/Packages
Fail to fetch Contents-amd64: Index of / kali-rolling/main amd64 Contents (deb) from http://http.kali.org/kali/dists/kali-rolling/main/Contents-amd64
E:Failed to fetch http://http.kali.org/kali/dists/kali-rolling/main/binary-amd64/Packages Error reading from server. Remote end closed connection [IP: 127.0.0.1 8082], E:Some index files failed to download. They have been ignored, or old ones used instead.
I have two kali-core templates. One virgin kali-core-original and one kali-core, which already has the kali-linux-default packages installed. The latter also has updates in qubes updater, but I just ignore it, until the kali-core-original updates will work…
Solution for me now was: to run the update manually in terminal sessions. The thing is, the download/update/upgrade process always seems to fall into sleep and so I had to STRG+C all the time and trying new. Thank god the entire function uses cache and starts from last point again… and so I finally quit both kali updat/grades.