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 upqubes-dom0-update ignores --releasever #2810
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
May 16, 2017
Member
There is no support for alternative dom0 version in given Qubes OS release. See here:
https://www.qubes-os.org/doc/supported-versions/#dom0
|
There is no support for alternative dom0 version in given Qubes OS release. See here: |
marmarek
closed this
May 16, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
GammaSQ
May 16, 2017
It may be desirable to install packages for other fedora-versions anyway. E.g.: #1648 (I am trying to emulate different architectures via stubdomains.)
In any case, it was not apparent to me that "supported version is" equals "no packages from other versions can be installed". I would be glad if that could be noted in the documentation.
GammaSQ
commented
May 16, 2017
|
It may be desirable to install packages for other fedora-versions anyway. E.g.: #1648 (I am trying to emulate different architectures via stubdomains.) In any case, it was not apparent to me that "supported version is" equals "no packages from other versions can be installed". I would be glad if that could be noted in the documentation. |
GammaSQ commentedMay 16, 2017
Qubes OS version: R3.2
Expected behavior:
--releasever=24passed down to UpdateVMActual behavior: silently ignored, since 23 is hardcoded in dom0. The only way to notice it is to read the download-progress from the UpdateVM and notice the "fc23" in the version string.
Steps to reproduce the behavior: check for any fedora package in dom0 with --releasever=24 --disablerepo=qubes* (qubes-repos don't deploy for different versions, so they would respond 404 and the command exits.)
General notes:
I fixed the issue by replacing any 23 in /etc/yum.repo.d/fedora* with
$releasever(in dom0), though that requires always passing--releaseverto the UpdateVM. This could be easily fixed by implementing that inqubes-dom0-update, but my setup works for me for now.Furthermore rpm key-import was required, which was done via a potentially insecure VM, so having a way to securely update the f24-key would be very nice!
It was very hard to figure out this one, since it's not even apparent that
--releaseveris dropped. Maybe annotate documentation to mention only fedora-23 repo is accessible in dom0 by default?