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 upFedora 26 and fedora 26 minimal templates "update sign" stuck in Qubes R 3.2 #3743
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Duplicate of #2009 |
andrewdavidwong
marked this as
a duplicate of
#2009
Mar 25, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
andrewdavidwong
Mar 25, 2018
Member
This appears to be a duplicate of an existing issue. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.
|
This appears to be a duplicate of an existing issue. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you. |
andrewdavidwong
closed this
Mar 25, 2018
andrewdavidwong
added
the
duplicate
label
Mar 25, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
tonsimple commentedMar 25, 2018
Qubes OS version:
R 3.2
Affected component(s):
Fedora-26 based templates
Fedora 26-minimal based templates
Steps to reproduce the behavior:
Carefully observe the Qubes VM manager after updating a bunch of F25 templates to F26
Expected behavior:
No update sign, since they are definitely, totally, very certainly updated to F26 and all updates are installed
Actual behavior:
Update sign (the downwards facing green arrow) is present.
If update process is initiated it runs without issue, but reports that there is nothing to do (no fresh updates available)
General notes:
Related issues: