Qubes-Task and Github Commit

There’s a commit in github for Qubes Task Manager, but when I try to update task-manager-gui in dom0, it says it’s complete.

And when I try to use it there’s an error.

Am I doing something wrong or is this commit not final or in upstream? I don’t understand all github language yet.

1 Like

The commits might be from anyone. Sometimes from non-Qubes OS core team people such as me and you. They should be reviewed by the team members before being merged or rejected. They might be even from the team members but not be ready to be merged as they may depend on something else which is under development.

It would be very hard to provide useful help or try to provide a fix without having the details.

1 Like

Um, no. Every commit to Qubes Task Manager is signed with my Qubes Signing key - you can verify this
with git log --show-signature

There was a mistake in updating the repository on qubes.3isec.org, and
the package there was reverted. I’ve had this fixed.
@dispuser - you should be OK to update the package now. You can do it
manually, or, (if you have been so bold as to add the repository to
dom0), with sudo qubes-dom0-update

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.


sudo qubes-dom0-update
Using sys-whonix as UpdateVM to download updates for Dom0; this may take some time…
Unable to detect release version (use ‘–releasever’ to specify release version)
3isec Qubes Dom0 Repository (updates) 87 B/s | 262 B 00:03
Errors during downloading metadata for repository ‘3isec-dom0-current’:

1 Like

did i do something wrong? i get an error

i figured it out:

name = 3isec Qubes Dom0 Repository (updates)
baseurl = https://qubes.3isec.org/rpm/r$releasever/current/dom0/fc37
enabled = 1
metadata_expire = 6h
gpgcheck = 1
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-unman

i needed to edit the file to change it to fc37!

it works! i’m excited!

1 Like