On Wed, Oct 21, 2020 at 7:45 PM Miro Hrončok <mhron...@redhat.com> wrote: > > On 10/21/20 10:10 PM, Neal Gompa wrote: > > On Wed, Oct 21, 2020 at 3:00 PM Miro Hrončok <mhron...@redhat.com> wrote: > >> 1) Why is breezy not in the ELN compose, but is in the Koji buildroot? > > > > It's defined as a buildroot only package: > > https://github.com/minimization/content-resolver-input/blob/master/configs/eln-buildroot-workload.yaml > > I wonder why. git blame suggests this is automated somehow. >
Hmm, that's a good question... > >> 2) As pip's maintainer, should I've been notified about the missing > >> dependency? > > > > Probably not, I think the idea was that ELN SIG would manage that > > exclusively. > > So I should stop caring? > I think you should still care, because in practice I don't think it's working out that way. > >> 3) When I fix breezy, should I resubmit the eln rebuilds of pip and Python? > >> > > > > No. Just submit to Rawhide and the Jenkins job for ELN will take care > > of it for you after it succeeds in Rawhide. > > Python and pip succeeded in rawhide already, this is an ELN-only fix. > I mean that their bot listens for packages built in Rawhide and triggers a rebuild automatically for ELN. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
