[qubes-users] Installing Rofi on dom0 via contributed packages?

So i tried, and think I suceeded in installing qubes-repo-contrib on dom0:

[bob@dom0 ~]$ sudo qubes-dom0-update qubes-repo-contrib
Using sys-whonix as UpdateVM to download updates for Dom0; this may take some time...
fedora/metalink | 6.4 kB 00:00
fedora | 4.3 kB 00:00
fedora/primary_db | 26 MB 01:41
qubes-contrib-dom0-r4.0-current | 3.0 kB 00:00
qubes-contrib-dom0-r4.0-current/primary_db | 16 kB 00:00
qubes-dom0-current/metalink | 2.7 kB 00:00
https://mirrors.phx.ms/qubes/repo/yum/r4.0/current/dom0/fc25/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: mirrors.phx.ms"
Trying other mirror.
qubes-dom0-current | 3.8 kB 00:00
qubes-dom0-current/primary_db | 352 kB 00:01
qubes-templates-itl/metalink | 2.7 kB 00:00
qubes-templates-itl | 3.0 kB 00:00 qubes-repo-contrib
https://mirror.hackingand.coffee/qubes/repo/yum/r4.0/templates-itl/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for qubes-templates-itl
Trying other mirror.
qubes-templates-itl | 3.0 kB 00:00
qubes-templates-itl/primary_db | 6.9 kB 00:00
updates/metalink | 5.5 kB 00:00
updates | 4.7 kB 00:00
updates/primary_db | 12 MB 00:46
--> Running transaction check
---> Package qubes-repo-contrib.noarch 0:4.0.6-1.fc25 will be reinstalled
--> Finished Dependency Resolution
qubes-repo-contrib-4.0.6-1.fc25.noarch.rpm | 11 kB 00:00
Successfully verified /var/lib/qubes/dom0-updates/packages/qubes-repo-contrib-4.0.6-1.fc25.noarch.rpm
Qubes OS Repository for Dom0 25 MB/s | 26 kB 00:00
Package qubes-repo-contrib-4.0.6-1.fc25.noarch is already installed, skipping.
Dependencies resolved.
Nothing to do.
Complete!

But when I then try to install rofi I get:
[bob@dom0 ~]$ sudo qubes-dom0-update qubes-rofi
Using sys-whonix as UpdateVM to download updates for Dom0; this may take some time...
No Match for argument qubes-rofi
Nothing to download

so, assuming I was typing the correct thing in dom0, I am not sure what to make of the error (which seems to be similar to an error i get when i try to install qubes-tunnel in a fed32 minimal template?

Thoughts?

btw, I am getting pretty much the same when i try from scratch in a dispVM

[user@disp3219 ~]$ sudo dnf install qubes-repo-contrib
Fedora Modular 32 - x86_64 - Updates 10 kB/s | 14 kB 00:01
Fedora 32 - x86_64 - Updates 17 kB/s | 13 kB 00:00
Fedora 32 - x86_64 - Updates 1.5 MB/s | 7.4 MB 00:05
Dependencies resolved.

Stumpy:

[bob@dom0 ~]$ sudo qubes-dom0-update qubes-rofi

[...]

No Match for argument qubes-rofi

The package is called just "rofi":

which seems to be similar to an error i get when i try to
install qubes-tunnel in a fed32 minimal template?

Looks like qubes-tunnel is in Fedora 32 current-testing, but hasn't
been uploaded to current yet:

Rusty

Oi. That was too simple, can't belive I didnt try just "rofi" thanks for that.

As for fed32/tunnel, thanks I will follow those git status for it.

Much appreciated!!

Fedora 32 version for qubes-tunnel is currently uploading to stable. Sorry for the delay :slight_smile:

Best,
Frédéric

Thanks for much for that!
So does this mean I should be able to install qubes-tunnel now? I just ask because when i try i get:

Last metadata expiration check: 0:08:09 ago on Thu Dec 17 06:17:34 2020.
Dependencies resolved.
Nothing to do.
Complete!
Last metadata expiration check: 0:08:31 ago on Thu Dec 17 06:17:34 2020.
Dependencies resolved.
Nothing to do.
Complete!
Last metadata expiration check: 0:08:49 ago on Thu Dec 17 06:17:34 2020.
No match for argument: qubes-tunnel
Error: Unable to find a match: qubes-tunnel

So perhaps its currently for fedora regular rather than minimal?

Stumpy:

Rusty Bird:

Stumpy:
> > Fedora 32 version for qubes-tunnel is currently uploading to stable.

> Error: Unable to find a match: qubes-tunnel
>
> So perhaps its currently for fedora regular rather than minimal?

Regular and minimal use the same repo. You're still seeing that error
because the upload didn't go through:

https://github.com/QubesOS-contrib/updates-status/issues/21#issuecomment-747355040

The Fedora 32 stable package is available now.

Rusty

Thanks for the heads up; I was (per your link earlier) following git and tried it, as well as tried for centos7 as it seemed that had also been uploaded - but it seems something is still amiss, not sure if its my side or something else?

In fed32min I am getting this:

bash-5.0# sudo dnf install qubes-repo-contrib && sudo dnf update && sudo dnf upgrade && sudo dnf install qubes-tunnel
Last metadata expiration check: 0:00:29 ago on Sat Dec 19 08:15:23 2020.
Package qubes-repo-contrib-4.0.7-1.fc32.noarch is already installed.
Dependencies resolved.
Nothing to do.
Complete!
Last metadata expiration check: 0:00:37 ago on Sat Dec 19 08:15:23 2020.
Dependencies resolved.
Nothing to do.
Complete!
Last metadata expiration check: 0:00:45 ago on Sat Dec 19 08:15:23 2020.
Dependencies resolved.
Nothing to do.
Complete!
Last metadata expiration check: 0:00:52 ago on Sat Dec 19 08:15:23 2020.
No match for argument: qubes-tunnel
Error: Unable to find a match: qubes-tunnel
bash-5.0# sudo dnf install tunnel
Last metadata expiration check: 0:01:28 ago on Sat Dec 19 08:15:23 2020.
No match for argument: tunnel
Error: Unable to find a match: tunnel

Thoughts?

PS I am also getting a different but similar error for installing rofi in dom0 (can paste it but it seems to be saying it cant find either rofi nor qubes-rofi)

Thanks!

Oi!! Sorry, centos7 installs ok but getting it to work does not seem to be working as smoothly as it did on fed31min... a separate question i guess wanted to correct myself so no needless looking over centos7 for qtunnel install was done

Stumpy:
> In fed32min I am getting this:
>
> bash-5.0# sudo dnf install qubes-repo-contrib && sudo dnf update && sudo

> No match for argument: qubes-tunnel
> Error: Unable to find a match: qubes-tunnel
> bash-5.0# sudo dnf install tunnel
> Last metadata expiration check: 0:01:28 ago on Sat Dec 19 08:15:23 2020.
> No match for argument: tunnel
> Error: Unable to find a match: tunnel

Sometimes it helps to restart the VM that is handling updates (often sys-whonix or sys-firewall) to force it to refresh the metadata if it's not finding a recently published package. Can also reboot Qubes to accomplish the same.