Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upThe 3.2 qubes-dom0-current repo is not reachable #3827
Comments
andrewdavidwong
added
bug
C: other
P: major
labels
Apr 15, 2018
andrewdavidwong
added this to the Release 3.2 updates milestone
Apr 15, 2018
andrewdavidwong
assigned
marmarek
Apr 15, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
marmarek
Apr 16, 2018
Member
Looks like repo metadata synchronization was interrupted leaving it in inconsistent state. Fixed.
|
Looks like repo metadata synchronization was interrupted leaving it in inconsistent state. Fixed. |
marmarek
closed this
Apr 16, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
This is happening again. |
andrewdavidwong
reopened this
Jun 14, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Fixed. |
marmarek
closed this
Jun 14, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
andrewdavidwong commentedApr 15, 2018
•
edited
Edited 1 time
-
andrewdavidwong
edited Apr 15, 2018 (most recent)
Qubes OS version:
R3.2Affected component(s):
The
qubes-dom0-currentrepo (and probably others)Steps to reproduce the behavior:
Attempt to update dom0 from Qubes 3.2 within the past 24 hours of this report.
Tried:
Expected behavior:
Download updates or receive report that no updates are available without an error.
Actual behavior:
General notes:
It's normal for
Failed to synchronize cacheto happen occasionally (i.e., for a few bad Tor exit nodes or temporary network or server problems), but not consistently across many different Tor circuits and clearnet over the course of a whole day. This suggests some problem with the server hosting the repo.