sudo qubes-dom0-update downloads packages but abruptly ends with a "The downloaded packages were..."

154 views
Skip to first unread message

Sphere

unread,
Feb 7, 2019, 9:59:01 PM2/7/19
to qubes-users
I have no idea what's up with my dom0
It downloads the packages through sudo qubes-dom0-update but by Transaction Summary after showing Total Size and Installed Size it doesn't even ask me whether or not to continue the transaction but just says
"DNF will only download packages for the transaction."
Proceeds to download the packages then ends with a "Complete!"
"The downloaded packages were saved in cache until the next successful transaction."

Seems some setting about DNF got changed, how do I fix this?

Sphere

unread,
Feb 7, 2019, 10:01:20 PM2/7/19
to qubes-users
It's like this but without the errors:
https://pastebin.com/YVUFtid6

Dupéron Georges

unread,
Feb 10, 2019, 2:28:39 PM2/10/19
to qubes-users
I have the same issue. I thought there weren't any new updates, but it's been like this for a while.

There are two updates listed, but they never get installed.

Note: I am not using the regular sys-net as my updatevm (I am using a plain fedora 29 VM, that is connected to sys-firewall, which is connected to the sys-ethernet VM to which the PCI device is attached).

Log:

Using XXX as UpdateVM to download updates for Dom0; this may take some time...
REPO1  XX MB/s |  XXX MB     XX:XX
REPO2  XX MB/s |  XXX MB     XX:XX
REPO3  XX MB/s |  XXX MB     XX:XX
determining the fastest mirror (XX hosts).. done.--  B/s |   0  B     --:-- ETA
REPO3  XX MB/s |  XXX MB     XX:XX
Dependencies resolved.
====================================================
 Package       Arch    Version    Repository   Size
====================================================
Reinstalling:
 XXX           XXX     XXX        XXXX         XXX M
 XXX           XXX     XXX        XXXX         XXX M

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

Total download size: XXX M
Installed size: XXX M

DNF will only download packages for the transaction.
Downloading Packages:
(1/2): XXX    XX MB/s | XXX MB   XX:XX
(2/2): XXX    XX MB/s | XXX MB   XX:XX
----------------------------------------
Total         XX MB/s | XXX MB   XX:XX

Complete!
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
XXXX                                                      XX MB/s |  XX MB   XX:XX

Marek Marczykowski-Górecki

unread,
Feb 10, 2019, 4:13:40 PM2/10/19
to Dupéron Georges, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Sun, Feb 10, 2019 at 07:33:21PM +0100, Dupéron Georges wrote:
> I have the same issue. I thought there weren't any new updates, but it's
> been like this for a while.
>
> There are two updates listed, but they never get installed.
>
> Note: I am not using the regular sys-net as my updatevm (I am using a plain
> fedora 29 VM, that is connected to sys-firewall, which is connected to the
> sys-ethernet VM to which the PCI device is attached).
>
> Log:
(...)
> Reinstalling:

This looks like it tries to update to the same version it already have
installed. Looks to be this issue:
https://github.com/QubesOS/qubes-issues/issues/4792

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlxgk/0ACgkQ24/THMrX
1yzHkQgAkeyp0rkaSYX+ysS2sdgKk/TTt8fTJohevDpdwpJIQZ1ibMXRr+J2DEWL
LuOi7JWFebK53xGD6eQvu8AaCuvSNpWWf9lrdm8taPi267t1Q03bO6tJyqfOzFcU
H8vMuC0rdq8JH97oCUxl5lhjDNaLX2JJmjIX43td33DANxtdgkwgVg+gPThvxWZl
6CFNEtmH5rW+5n4ISyJZ9PC4k6zzjnmnyhaak4GLCeeJ5WYYU8E1xWD4JuB/ZKcT
mCH/JFgD5Bc5MS8xHYylAhBOF+gNJPOyVnb6qrxaRxmp284l1UjqtzFaiZGAeNd9
9uciJE80mKP8uh9nm8SRFtN6WfjBOQ==
=JLEm
-----END PGP SIGNATURE-----

Sphere

unread,
Feb 18, 2019, 8:15:30 PM2/18/19
to qubes-users
Thank you for this
So it seems there's a bunch of people having this problem too and now it is marked as critical

Oddly enough though it doesn't suffer from this problem when trying to install a new package. Tried installing Anti-evil maid and it gone through without problems on both Downloading and Installing
Reply all
Reply to author
Forward
0 new messages