Error while updating kali-core template

User Support
1

I installed kali-core template from Qubes Template Manager, then update for it showed up, i updated it and encountered this error(Full log here - Updating kali-core-cloneRefreshing package infoRefreshing packages.Refresh - Pastebin.com). How do you fix this and install qubes-core-agent?

Failed to disable unit: Unit file qubes-sysinit.service does not exist.
dpkg: error processing package qubes-core-agent (–remove):
installed qubes-core-agent package post-removal script subprocess returned error exit status 1
dpkg: too many errors, stopping
Error during installation qubes-core-agent:installed qubes-core-agent package post-removal script subprocess returned error exit status 1
Errors were encountered while processing:
qubes-core-agent
Processing was halted because there were too many errors.
sh: 1: /usr/lib/qubes/upgrades-status-notify: not found
E:Sub-process /usr/bin/dpkg returned an error code (1)

2
3

How can i replace it? Do i need to just change word bookworm with trixie to make it look like this?

# Qubes experimental/unstable repository
#deb [arch=amd64 signed-by=/usr/share/keyrings/qubes-archive-keyring-4.2.gpg] https://deb.qubes-os.org/r4.2/vm trixie-unstable main
#deb-src  [arch=amd64 signed-by=/usr/share/keyrings/qubes-archive-keyring-4.2.gpg ] https://deb.qubes-os.org/r4.2/vm trixie-unstable main
4

Yes, just replace bookworm with trixie.

I think it should be just trixie.

1 Like
5

This is for unstable qubes os repository, isn’t kali-core still an unstable community template?

6

There is no Qubes OS debian repository for unstable (sid), but there is one for testing (trixie). And trixie-unstable is just incorrect distribution name.
The packages in testing are newer than the ones from stable (bookworm) repository so the chance of the package conflicts are lower.

7

Will this do the same effect as enabling all testing updates in Qubes OS global config?

8

No, update settings in the Qubes Os Global Config are only for dom0 and they don’t affect your repositories defined inside templates.