https://bugzilla.redhat.com/show_bug.cgi?id=1169966 --- Comment #20 from Tom "spot" Callaway <tcallawa@xxxxxxxxxx> --- I don't think that mkrootfs.sh is going to work. A) There is no networking in the koji runtime instances, so it can't download anything, even from koji. B) Including that binary image into the SRPM is ... troublesome. I'm not confident that distributing the binary RPM along with the SRPM guarantees that we remain in compliance with all of the licenses in that binary docker image. Is there no way we can distribute this tool without a binary distribution image? If the answer is "the tool doesn't do anything without one", the options are: 1) Add a README.fedora that points to the latest Fedora image and let the user figure it out AND/OR Include a script to download the latest Fedora image (but don't run it in a %post scriptlet please). 2) Somehow get the latest Fedora image into an RPM where the corresponding SRPM has the BuildRequires to properly build it from the RPMs in the Fedora tree, then Requires on that image RPM here. (This sounds convoluted, and it is, but it ensures that we are in license compliance). 3) Figure out a way to document and track the source revisions of EVERY component inside the binary Fedora image, then work with rel-eng to ensure that as long as we distribute the binary Fedora image inside of this package, the other SRPMs remain available (and accurate). This is going to be painful, so I strongly advise against it. I'm open to other suggestions, but this is all that comes to mind at the moment. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review