On 11/28/2017 08:30 AM, Kaleb S. KEITHLEY wrote:
I've been contacted by Fedora QE about this, and have bz
https://bugzilla.redhat.com/show_bug.cgi?id=1518150
I haven't followed (can't follow) Fedora closely enough to know what's
needed here. Apparently none of my co-maintainers have either. ;-)
glusterfs packages are built for f27.
Reading through -devel it kinda looks like there was a branch created. A
branch that I should be doing builds on. But I have no branch in the
glusterfs dist-git other than the usual f26, f27, master that I could do
a build on.
Would someone hit me with a cluebat please? Was I supposed to request a
-module branch in dist-git?
It's more complicated than just creating a new branch. modules are their
own whole new namespace (fedpkg co modules/$name) with their own
packaging data (modulemd yaml). To modularize a package/set of packages
requires doing the equivalent of a new package review.
https://fedoraproject.org/wiki/Module:Review_Process
https://fedoraproject.org/wiki/Fedora_Packaging_Guidelines_for_Modules
In the f27 modular server release, a whole bunch of things aren't going
to be installable by default: gluster, virt stack, basic things like
screen last I heard, and a whole lot more. Currently everything needs to
be modularized before it's available to install out of the box
WRT gluster, actually just yesterday I was working on creating a
glusterfs module as step towards modularizing qemu and libvirt. It
doesn't involve any gluster code/spec changes, it's all higher level
packaging type stuff. I plan to submit a review request this week, I'll
CC you
- Cole