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 upbug in qubes-upgrade-vm package #2250
Comments
mfc
added
the
bug
label
Aug 16, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Aug 16, 2016
Member
Did you made any manual modifications to that file? In such a case, rpm will not override it and store new content in /etc/yum.repos.d/qubes-r3.repo.rpmnew file.
|
Did you made any manual modifications to that file? In such a case, |
andrewdavidwong
added
the
C: Fedora
label
Aug 16, 2016
andrewdavidwong
added this to the Release 3.2 milestone
Aug 16, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
mfc
Aug 16, 2016
Member
nope no /etc/yum.repos.d/qubes-r3.repo.rpmnew was created. for further context in case it's helpful this was from a fresh R3.2rc2 installation with R3.1 templates that were then upgraded (i.e. I did not in-place upgrade Qubes from R3.1 to R3.2rc2).
|
nope no |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Aug 16, 2016
Member
What version of qubes-core-vm package do you have? Did you actually finished the upgrade (including the last step: dnf upgrade --refresh)?
|
What version of |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
mfc
Aug 18, 2016
Member
how do i check the version? qubes-core-vm --version doesn't work. yes i completed the upgrade including running dnf upgrade --refresh.
|
how do i check the version? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Aug 18, 2016
Member
On Thu, Aug 18, 2016 at 02:42:52AM -0700, Michael Carbone wrote:
how do i check the version?
qubes-core-vm --versiondoesn't work. yes i completed the upgrade including runningdnf upgrade --refresh.
rpm -q qubes-core-vm
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?
|
On Thu, Aug 18, 2016 at 02:42:52AM -0700, Michael Carbone wrote:
Best Regards, |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
mfc
Aug 18, 2016
Member
qubes-core-vm-3.2.9-1.fc23.x86_64
but I updated the template after changing the sources so that may not have been the version when the problem was encountered.
|
qubes-core-vm-3.2.9-1.fc23.x86_64 but I updated the template after changing the sources so that may not have been the version when the problem was encountered. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Aug 18, 2016
Member
qubes-core-vm-3.2.9-1.fc23.x86_64
Ok, this is the right version for R3.2. Maybe you have modified
/etc/yum.repo.d/qubes-r3.repo somehow? You can verify if the file
content matches what was in the package using rpm -V qubes-core-vm.
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?
Ok, this is the right version for R3.2. Maybe you have modified Best Regards, |
mfc commentedAug 16, 2016
Qubes OS version (e.g.,
R3.1):R3.2rc2
Affected TemplateVMs (e.g.,
fedora-23, if applicable):user-created R3.1 Fedora-23 template
Expected behavior:
upgraded template will have access to 3.2rc2 sources.
Actual behavior:
upgraded template does not have access to 3.2rc2 sources.
Steps to reproduce the behavior:
create R3.1 fedora template, follow R3.2 upgrade instructions, sources in template (
/etc/yum.repos.d/qubes-r3.repo) not updated to R3.2.General notes:
upgraded R3.1 user-created Debian-8 templates did not run into this issue.
The upgraded user-created Fedora-23 template still pointed to r3.1 in
/etc/yum.repos.d/qubes-r3.repowhich when edited to point to R3.2 fixed the problem. So it seems like a problem withqubes-upgrade-vm.