On Mon, 2019-04-08 at 04:26 -0400, Robert P. J. Day wrote:

i have no idea if package groups are supposed to be installable at this point, but:

$ sudo dnf groupinstall "Electronic Lab" Last metadata expiration check: 0:03:55 ago on Mon 08 Apr 2019 04:20:34 AM EDT. No match for group package "eqntott" No match for group package "gds2pov" No match for group package "piklab" No match for group package "pharosc" No match for group package "covered" No match for group package "archimedes" No match for group package "fped" No match for group package "dinotrace" No match for group package "qtoctave" No match for group package "geda-gaf" No match for group package "eclipse-eclox" No match for group package "pharosc-synopsys" No match for group package "tetex-IEEEtran" No match for group package "sk2py" No match for group package "pikloops" No match for group package "emacs-verilog-mode" No match for group package "pharosc-alliance" No match for group package "emacs-dinotrace" No match for group package "gplcver" No match for group package "picprog" No match for group package "pikdev" No match for group package "eclipse-veditor" No match for group package "eclipse-texlipse" No match for group package "pharosc-xcircuit" No match for group package "pharosc-magic" No match for group package "perl-SystemPerl" Error: Problem 1: conflicting requests

• nothing provides geda-gnetlist needed by

gspiceui-1.1.00-2.fc30.x86_64

• nothing provides geda-gschem needed by

gspiceui-1.1.00-2.fc30.x86_64

... much more here ...

or am i being premature in that package groups won't be finalized until closer to release?

No, not at all, anything like this is a real bug. Can you please file bugs for the issues you found? The "No match for group package" errors aren't critical (though it would be best to fix them), but the conflicts are. File the bugs against the packages that won't install (so for the above conflict you'd file a bug against gspiceui).

Thanks!