$ sudo dnf group install --with-optional virtualization
Last metadata expiration check: 0:41:26 ago on Wed 04 Apr 2018 03:53:26 PM EDT.
Group 'Virtualization' is already installed.
No match for group package "python-libguestfs"
Nothing to do.
Not sure how you want to resolve that.
Yes it'd be nice if comps.xml had some kind of automatic check
for this. Maybe it could even automatically fix them.
Unfortunately I tried to fix this using the procedure outlined
in the wiki page, but it fails.
$ git clone ssh://email@example.com/forks/rjones/fedora-comps.git
Cloning into 'fedora-comps'...
FATAL: R any forks/rjones/fedora-comps rjones DENIED by fallthru
(or you mis-spelled the reponame)
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Richard: it's like github, you have to actually *create* the fork first (I just do it via the web UI, there may be a more CLI-ish way too, I dunno). Go to https://pagure.io/fedora-comps , make sure you're logged in, and hit the 'Fork' or 'Create Fork' or whatever it's called button at top-right.
Oh good, they copied the worst workflow in history.
I did all the other stuff, but couldn't work out how to create the
Such a complex system to make a 2 character change to a file!
If you just go to the Pagure page for the original repo or your fork, and make sure you're logged in, a 'create pull request' button should appear. Sometimes as a notification of a 'recently changed branch' or so, otherwise on the page for your fork, next to the branch name on the right hand side.
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '27'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 27 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
So this was fixed a while back.