So, this is just for the F32 or all the composes?  Also, I checked issue 989 but didnt see how you can tell what the error that caused CompNeuro ISO to fail.    How did you track down the python3-networkx-core bug.


On 2/13/20 4:04 PM, Ankur Sinha wrote:
Hello,

We're getting closer to F32 release, and we must ensure that the
CompNeuro ISO image keeps building correctly in each "compose" that the
Fedora Release Engineering (releng) runs.

Failed composes are now noted here with a new ticket:
https://pagure.io/releng/failed-composes

For example, in the latest compose, all images failed:
https://pagure.io/releng/failed-composes/issue/989

Our image also failed because of an additional error:
- nothing provides python3-networkx-core needed by
python3-scikit-image-0.16.2-2.fc32.x86_64
I've filed a bug with the python-networkx maintainer here:
https://bugzilla.redhat.com/show_bug.cgi?id=1802771

So, do we have someone who would like to be "Compose Wrangler" for us?
The main responsibility is to monitor this repository on a daily basis
to check if the ISO was created correctly. If it wasn't, to let the list
here know why so that we can see what needs fixing. The time this task
would require would be ~5/10 minutes per day (or every alternate day).

Any volunteers? :)

(If not, we can advertise for "Compose Wranger" as an open position on
the blog etc., but it'll be good for one of us to start here for the
time being.)



_______________________________________________
Neurofedora mailing list -- neurofedora@lists.fedoraproject.org
To unsubscribe send an email to neurofedora-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/neurofedora@lists.fedoraproject.org