On Wed, 11 Dec 2013, Michael Cronenworth wrote:
On 12/08/2013 08:37 AM, Mateusz Marzantowicz wrote:
Curious, why it blew up right now, just before F20 is released. It
should have happened in alpha and not now.
Workaround is to yum group mark remove <group name here> for every group
on the list. What a waste of time.
Whatever you do - do not run "yum group mark convert". Now one of my systems
wants to install every Fedora package with "yum update".
This affects all Fedoras with yum -120. Here's the parent bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1014202
There is much more problems with groups in bugzilla, it affects F19 too.
You can "fix" this by using "yum mark remove <group>" on all groups you
get a warning they are missing (you have to have the latest yum - so yum
update yum).
If you do a mark convert it takes old group info and converts it to new
objects. So whenever you do this again, you'll end in the same "broken"
state again.
In my opinion, this is somewhat badly broken.
Adam Pribyl
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test