Cannot update dom0 in Qubes v3.1 rc2

87 views
Skip to first unread message

qubesuser

unread,
Jan 29, 2016, 8:25:30 PM1/29/16
to qubes...@googlegroups.com

***************************************************************
This email was sent via http://www.AnonymousSpeech.com,
the worlds leading <a href=http://www.anonymousspeech.com>anonymous email</a> provider.
Report Abuse: http://www.anonymousspeech.com/contact.aspx
Stop receiving emails from AnonymousSpeech.com: http://www.anonymousspeech.com/bannedemail.aspx?email=qubes...@googlegroups.com
***************************************************************



I can't seem to update dom0. I hope it is not a lack of reading the manual. This might be a bug, but I decided to ask as a question in the user groups instead. Since copy / paste is disabled in dom0, I am posting an abbreviated version of what happens.

On a fresh install of Qubes v3.1 rc2, I enter a command in dom0 using Konsole as follows: sudo qubes-dom0-update. After a brief delay I get a white text message about using sys-firewall, and running command on VM: sys-firewall.

Then after about a minute, I get variable red text. There used to be a complaint about using yum, and it being deprecated. Then at other times there was a note that I should ignore the complaint, then the complaint. Now I am getting a red message about checking for dom0 updates... then the message No new updates available. This would seem to be all well and good, except for the following (sometimes shortly and sometimes after some minutes)

White text: file:///var/lib/qubes/updates/repodata/repomd.xml: [Errno 14] curl#37 - "couldn't open file Trying other mirror.
Sometimes about this point I get a longish red text message about the connection being real slow (less than 1000 bytes / second.

One of the configured repositories failed (Qubes OS Repository for Dom0), and yum doesn't have enough cached data to continue.... followed by four suggested actions
1. contact upstream
2. reconfigure baseurl/etc.
3. disable the repository
4. configure the repository to be skipped if it is not available.

failure: repodata/repomod.xml from qubes-dom0-cached: [Errno 256] no more mirrors to try........[Errno 14] curl#37......... no updates available.

Previous installs of Qubes v3.1 rc1 were able to be updated. If I remember correctly, a previous download of v3.1 rc2 was able to be updated, but this one cannot be updated.

I don't know if:
1. qubes v3.1 rc2 has no updates (seems unlikely)
2. qubes v3.1 rc2 has changed over time, and what I have now has no updates
3. I did something totally wrong
4. The repository is down for days now.
5. Something else I did not think of.

Please note, that I am able to use sys-firewall for updates of templates, and I am writing and sending this in Qubes, so the basic functionality of my install is intact.


prance...@sigaint.org

unread,
Jan 30, 2016, 10:28:17 AM1/30/16
to qube...@anonymousspeech.com, qubes...@googlegroups.com
It's been mentioned on the mailing lists a couple of times. Fix by running
in dom0:

$ sudo qubes-dom0-update --enablerepo=qubes-*-testing

You don't need to download any of the packages, but rc is testing, so you
might want to. Afterwards qubes-dom0-update and gui update work fine.

Reply all
Reply to author
Forward
0 new messages