Comment # 13 on bug 1163592 from Martin Pluskal

(In reply to Miroslav Bene�� from comment #12)
> This got stuck for quite a while, I suppose. The problem itself is almost
> all Greek to me, but I'll try anyway. So Richard said that there was a
> decision made to stop using Group and then he removed the tag from some of
> our KMPs. Is that correct? It obviously led to a not nice issue that
> Stanislav reported.
> 
> So how do you propose to proceed? Since there was the decision, someone
> needs to fix the kernel package. Or we could, of course, revert Richard's
> incomplete change in KMPs and live with the tag. No one has responded to
> Michal's comment 9.
> 
> Well?

The issue occured after following change was made:
-------------------------------------------------------------------
Thu Oct 17 17:48:47 UTC 2019 - Richard Brown <rbrown@suse.com>

- Remove obsolete Groups tag (fate#326485)

However package sans rpm group is considered valid. I wonder why fixing kernel
rpm macros would however be responsibility of someone who made change to one of
many kmp's, as bluntly requested in comment#9 . Furthermore mentioned kmp, as
well as others are building as expected, well at least for Factory, they only
have invalid group defined, as consequence of deficiencies of kernel rpm macros
which were not adapted to recent advances in packaging.