dom0 updates not visible?

42 views
Skip to first unread message

qubes...@riseup.net

unread,
Jul 7, 2019, 9:40:16 AM7/7/19
to qubes-users
Hi,

I fear I have an issue with dom0 updates.

I noticed that there is a newer release
for
qubes-mgmt-salt-dom0-virtual-machines (4.0.16)

but I still have:

qubes-mgmt-salt-dom0-virtual-machines-4.0.15-1.fc25.noarch

An update in dom0 doesn't install the update:

sudo qubes-dom0-update

Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time...
Last metadata expiration check: 0:35:59 ago on Sun Jul 7 14:57:27 2019.
Dependencies resolved.
================================================================================
Package Arch Version Repository Size
================================================================================
Reinstalling:
anaconda-core x86_64 1000:25.20.9-14.fc25 qubes-dom0-current 1.5 M
anaconda-gui x86_64 1000:25.20.9-14.fc25 qubes-dom0-current 386 k
anaconda-tui x86_64 1000:25.20.9-14.fc25 qubes-dom0-current 186 k
anaconda-widgets x86_64 1000:25.20.9-14.fc25 qubes-dom0-current 119 k
garcon x86_64 1000:0.5.0-1.fc25 qubes-dom0-current 179 k
python3-blivet noarch 2:2.1.6-5.fc25 qubes-dom0-current 1.0 M
python3-kickstart noarch 1000:2.32-4.fc25 qubes-dom0-current 370 k
qubes-anaconda-addon noarch 4.0.9-1.fc25 qubes-dom0-current 34 k
xfwm4 x86_64 1000:4.12.4-1.fc25 qubes-dom0-current 636 k
xorg-x11-drv-ati x86_64 18.0.1-1.fc25 qubes-dom0-current 168 k
xorg-x11-drv-intel x86_64 2.99.917-32.20171025.fc25 qubes-dom0-current 696 k

Transaction Summary
================================================================================

Total size: 5.1 M
Installed size: 19 M
DNF will only download packages for the transaction.
Downloading Packages:
[SKIPPED] anaconda-core-25.20.9-14.fc25.x86_64.rpm: Already downloaded
[SKIPPED] anaconda-gui-25.20.9-14.fc25.x86_64.rpm: Already downloaded
[SKIPPED] anaconda-tui-25.20.9-14.fc25.x86_64.rpm: Already downloaded
[SKIPPED] anaconda-widgets-25.20.9-14.fc25.x86_64.rpm: Already downloaded
[SKIPPED] garcon-0.5.0-1.fc25.x86_64.rpm: Already downloaded
[SKIPPED] python3-blivet-2.1.6-5.fc25.noarch.rpm: Already downloaded
[SKIPPED] python3-kickstart-2.32-4.fc25.noarch.rpm: Already downloaded
[SKIPPED] qubes-anaconda-addon-4.0.9-1.fc25.noarch.rpm: Already downloaded
[SKIPPED] xfwm4-4.12.4-1.fc25.x86_64.rpm: Already downloaded
[SKIPPED] xorg-x11-drv-ati-18.0.1-1.fc25.x86_64.rpm: Already downloaded
[SKIPPED] xorg-x11-drv-intel-2.99.917-32.20171025.fc25.x86_64.rpm: Already downloaded
Complete!
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Qubes OS Repository for Dom0


I don't use the testing/unstable dom0 repos, just current.


I'm using sys-firewall (fedora-30) as update VM.

I also tried
sudo dnf clean all

using Qubes R4.0

Do you have recommendations on how to debug this?
thanks!

unman

unread,
Jul 7, 2019, 12:07:32 PM7/7/19
to qubes-users
This is, unfortunately, a known issue.
You can manually install the "SKIPPED" packages by using dnf install.
Your "dnf clean all" has scuppered that.
Just try the update again, and if the same packages are downloaded, just
install them yourself.

qubes...@riseup.net

unread,
Jul 7, 2019, 12:32:54 PM7/7/19
to qubes...@googlegroups.com


unman:
> On Sun, Jul 07, 2019 at 01:40:00PM +0000, qubes...@riseup.net wrote:
>> Hi,
>>
>> I fear I have an issue with dom0 updates.
>>
>> I noticed that there is a newer release
>> for
>> qubes-mgmt-salt-dom0-virtual-machines (4.0.16)
>>
>> but I still have:
>>
>> qubes-mgmt-salt-dom0-virtual-machines-4.0.15-1.fc25.noarch


>
> This is, unfortunately, a known issue.
> You can manually install the "SKIPPED" packages by using dnf install.
> Your "dnf clean all" has scuppered that.
> Just try the update again, and if the same packages are downloaded, just
> install them yourself.


but the relevant package qubes-mgmt-salt-dom0-virtual-machines
is not even listed as skipped.

lik...@gmx.de

unread,
Jul 7, 2019, 1:07:04 PM7/7/19
to qubes...@googlegroups.com
On 7/7/19 5:32 PM, qubes-lists-sGOZH...@public.gmane.org wrote:
>
>
> unman:
>> On Sun, Jul 07, 2019 at 01:40:00PM +0000, qubes-lists-sGOZH...@public.gmane.org wrote:
>>> Hi,
>>>
>>> I fear I have an issue with dom0 updates.
>>>
>>> I noticed that there is a newer release
>>> for
>>> qubes-mgmt-salt-dom0-virtual-machines (4.0.16)
>>>
>>> but I still have:
>>>
>>> qubes-mgmt-salt-dom0-virtual-machines-4.0.15-1.fc25.noarch
>
>
>>
>> This is, unfortunately, a known issue.
>> You can manually install the "SKIPPED" packages by using dnf install.
>> Your "dnf clean all" has scuppered that.
>> Just try the update again, and if the same packages are downloaded, just
>> install them yourself.
>
>
> but the relevant package qubes-mgmt-salt-dom0-virtual-machines
> is not even listed as skipped.
>

I'm also interested in that. Last week I discovered that I'm using the kernel 4.14.119 whereas 4.19 is already used by others according to this mailing list.
How to find the skipped packages and how to update qubes to the _real_ latest version?

qubes...@riseup.net

unread,
Jul 7, 2019, 1:40:17 PM7/7/19
to qubes...@googlegroups.com


qubes...@riseup.net:
> Hi,
>
> I fear I have an issue with dom0 updates.
>
> I noticed that there is a newer release
> for
> qubes-mgmt-salt-dom0-virtual-machines (4.0.16)
>
> but I still have:
>
> qubes-mgmt-salt-dom0-virtual-machines-4.0.15-1.fc25.noarch


Just to verify:

Do others have v4.0.16 installed for the package
qubes-mgmt-salt-dom0-virtual-machines
on your R4.0 systems without testing repos enabled?

awokd

unread,
Jul 7, 2019, 2:57:37 PM7/7/19
to qubes...@googlegroups.com
qubes...@riseup.net:

> Do others have v4.0.16 installed for the package
> qubes-mgmt-salt-dom0-virtual-machines
> on your R4.0 systems without testing repos enabled?
>
No, doesn't look like it is in stable/current yet.

unman

unread,
Jul 7, 2019, 7:26:14 PM7/7/19
to qubes...@googlegroups.com
The *latest* version is in testing - you can check by using
--action=search to see what's available, and the --enable-repo option to
check what's in testing.
But, of course, that's testing - if you're concerned about stability,
stick to current. Not so good for QA, but may be better for you.
Reply all
Reply to author
Forward
0 new messages