New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dom0 update errors ("Couldn't open file /var/lib/qubes/updates/repodata/repomd.xml") #1703

Closed
mig5 opened this Issue Jan 29, 2016 · 1 comment

Comments

Projects
None yet
1 participant
@mig5

mig5 commented Jan 29, 2016

Since maybe a week ago, I get this error when I run 'sudo qubes-dom0-update' (with or without --clean)

[miguel@dom0 ~]$ sudo qubes-dom0-update --clean
Using untrusted as UpdateVM to download updates for Dom0; this may take some time...
Running command on VM: 'untrusted'...
Cleaning repos: fedora qubes-dom0-current qubes-dom0-security-testing
              : qubes-templates-itl updates
Cleaning up Everything
Checking for dom0 updates...
No new updates available
file:///var/lib/qubes/updates/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /var/lib/qubes/updates/repodata/repomd.xml"
Trying other mirror.


 One of the configured repositories failed (Qubes OS Repository for Dom0),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Disable the repository, so yum won't use it by default. Yum will then
        just ignore the repository until you permanently enable it again or use
        --enablerepo for temporary usage:

            yum-config-manager --disable qubes-dom0-cached

     4. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=qubes-dom0-cached.skip_if_unavailable=true

failure: repodata/repomd.xml from qubes-dom0-cached: [Errno 256] No more mirrors to try.
file:///var/lib/qubes/updates/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /var/lib/qubes/updates/repodata/repomd.xml"
No updates avaliable

I don't recall changing anything on dom0 to have caused this. This is Qubes 3.1

What could cause this issue? And any idea how to fix it?

@mig5

This comment has been minimized.

Show comment
Hide comment
@mig5

mig5 Jan 29, 2016

Closing, as this is a duplicate of #1685

mig5 commented Jan 29, 2016

Closing, as this is a duplicate of #1685

@mig5 mig5 closed this Jan 29, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment