can't install kernel-qubes-vm from qubes-dom0-unstable repo

244 views
Skip to first unread message

Holger Levsen

unread,
Apr 7, 2017, 6:24:26 PM4/7/17
to qubes...@googlegroups.com
Hi,

"long ago" I successfully installed kernel-4.8.12-12 from the
qubes-dom0-unstable repo and today I realized that maybe Qubes
would be more stable for me, if I'd also install kernel-qubes-vm
4.8.12-12 instead of still using 4.4.38 in the VMs…

But…

[user@dom0 ~]$ sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable kernel-qubes-vm
Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time...
Running command on VM: 'sys-firewall'...
fedora/metalink | 22 kB 00:00
qubes-dom0-current | 3.6 kB 00:00
qubes-dom0-unstable | 2.9 kB 00:00
qubes-templates-itl | 2.9 kB 00:00
updates/metalink | 20 kB 00:00
--> Running transaction check
---> Package kernel-qubes-vm.x86_64 1000:4.8.12-12.pvops.qubes will be installed
--> Finished Dependency Resolution
/var/lib/qubes/dom0-updates/packages/kernel-qubes-vm-4.8.12-12.pvops.qubes.x86_64.rpm already exists and appears to be complete
find: `/var/lib/qubes/dom0-updates/var/cache/yum': No such file or directory
Redirecting to '/usr/bin/dnf --exclude=qubes-template-whonix-gw,qubes-template-fedora-24,qubes-template-fedora-23,qubes-template-debian-8,qubes-template-whonix-ws, install kernel-qubes-vm' (see 'man yum2dnf')

Qubes OS Repository for Dom0 23 MB/s | 44 kB 00:00
Package kernel-qubes-vm-1000:4.4.14-11.pvops.qubes.x86_64 is already installed, skipping.
Package kernel-qubes-vm-1000:4.4.38-11.pvops.qubes.x86_64 is already installed, skipping.
Dependencies resolved.
==================================================================================================================
Package Arch Version Repository Size
==================================================================================================================
Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
kernel-qubes-vm x86_64 1000:4.8.12-12.pvops.qubes qubes-dom0-cached 45 M

Transaction Summary
==================================================================================================================
Skip 1 Package

Nothing to do.
Complete!
[user@dom0 ~]$ rpm -qa |grep kernel
qubes-core-dom0-linux-kernel-install-3.2.12-1.fc23.x86_64
kernel-4.4.14-11.pvops.qubes.x86_64
kernel-4.4.38-11.pvops.qubes.x86_64
kernel-4.8.12-12.pvops.qubes.x86_64
kernel-qubes-vm-4.4.14-11.pvops.qubes.x86_64
kernel-qubes-vm-4.4.38-11.pvops.qubes.x86_64
[user@dom0 ~]$ sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable --best --allowerasing kernel-qubes-vm
Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time...
Running command on VM: 'sys-firewall'...
Usage: "yumdownloader [options] package1 [package2] [package..]

Command line error: no such option: --best
[user@dom0 ~]$

So, two questions:

a.) How can I actually force installation of kernel-qubes-vm-4.8.12-12.pvops.qubes?
The package has already been downloaded, where is it stored?
b.) How can I check what conflicts there are?

I'll try to provide patches for qubes-doc.git/common-tasks/software-update-dom0.md
once I know more!


--
cheers,
Holger
signature.asc

Chris Laprise

unread,
Apr 8, 2017, 12:04:02 AM4/8/17
to qubes...@googlegroups.com
I think 'rpm -qa' is essentially saying the package is installed. You
can check this with 'sudo dnf info kernel-qubes-vm'. If its listed it
should be installed. You can check this in the kernel dropdown box under
VM Settings / Advanced.

If the rpm is still cached in dom0, you can try 'sudo dnf reinstall
kernel-qubes-vm-4.8.12-12'.

If not, try 'sudo qubes-dom0-update kernel-qubes-vm-4.8.12-12
--enablerepo=qubes-dom0-unstable --action=reinstall'

--

Chris Laprise, tas...@openmailbox.org
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886

Holger Levsen

unread,
Apr 8, 2017, 5:35:27 AM4/8/17
to qubes...@googlegroups.com
On Sat, Apr 08, 2017 at 12:03:55AM -0400, Chris Laprise wrote:
> I think 'rpm -qa' is essentially saying the package is installed.

I think you misread the output I posted, it was:

[user@dom0 ~]$ rpm -qa |grep kernel
qubes-core-dom0-linux-kernel-install-3.2.12-1.fc23.x86_64
kernel-4.4.14-11.pvops.qubes.x86_64
kernel-4.4.38-11.pvops.qubes.x86_64
kernel-4.8.12-12.pvops.qubes.x86_64
kernel-qubes-vm-4.4.14-11.pvops.qubes.x86_64
kernel-qubes-vm-4.4.38-11.pvops.qubes.x86_64

and clearly lacks kernel-qubes-vm 4.8.12 :)

> If the rpm is still cached in dom0, you can try 'sudo dnf reinstall
> kernel-qubes-vm-4.8.12-12'.

this didnt do the trick, but it made me look again on the filesystem as
qubes-dom0-update also said it was cached… so this time I went for
"sudo find / |grep kernel-qubes-vm" which found it in
/var/lib/qubes/updates/rpm/ so I just installed it with "rpm -i $file"
which worked nicely.

However, it didnt show me the conflict dnf showed me while using
qubes-dom0-update and I still would like to know what conflict that was…!

> If not, try 'sudo qubes-dom0-update kernel-qubes-vm-4.8.12-12
> --enablerepo=qubes-dom0-unstable --action=reinstall'

this doesnt work anymore:

ERROR: yum version installed in VM sys-firewall does not support --downloadonly option
ERROR: only 'install' and 'upgrade' actions support (reinstall not)

So thanks, your reply made me dig deeper and find a manual workaround,
but I still would be more happy if qubes-dom0-update would work to install
kernel-qubes-vm 4.8.12-12 in a way that one can document in qubes-doc…

Now hoping that this will indeed make my system more stable too. I'll see.


--
cheers,
Holger
signature.asc

Chris Laprise

unread,
Apr 8, 2017, 10:28:55 AM4/8/17
to qubes...@googlegroups.com
On 04/08/2017 05:35 AM, Holger Levsen wrote:
>> If not, try 'sudo qubes-dom0-update kernel-qubes-vm-4.8.12-12
>> --enablerepo=qubes-dom0-unstable --action=reinstall'
>
> this doesnt work anymore:
>
> ERROR: yum version installed in VM sys-firewall does not support --downloadonly option
> ERROR: only 'install' and 'upgrade' actions support (reinstall not)

This sounds like you're using Debian as your updatevm. This is one of
the few reasons I keep Fedora around.

Hope your upgrade works!
Reply all
Reply to author
Forward
0 new messages