Re: What is the criterion for Python 3.7 side tag merge?

2018-07-04 Thread Zbigniew Jędrzejewski-Szmek
On Tue, Jul 03, 2018 at 04:33:37PM -0600, William Moreno wrote: > > > > > > OK. I'll ask releng to merge on Monday. > > > > > Was it merged? Yep. Zbyszek ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to

Re: What is the criterion for Python 3.7 side tag merge?

2018-07-03 Thread William Moreno
> > > OK. I'll ask releng to merge on Monday. > > Was it merged? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct:

Re: What is the criterion for Python 3.7 side tag merge?

2018-06-28 Thread Miro Hrončok
On 28.6.2018 15:42, Miro Hrončok wrote: The Python 3.7 rebuild in the f29-python side tag is currently:  - 2168 built  - ~170 FTBFS  - ~120 blocked by dependencies that FTBFS Ideally, this would all get fixed before the merge, but that's unrealistic, there are packages that are FTBFS for

Re: What is the criterion for Python 3.7 side tag merge?

2018-06-28 Thread Miro Hrončok
On 28.6.2018 15:42, Miro Hrončok wrote: The Python 3.7 rebuild in the f29-python side tag is currently:  - 2168 built  - ~170 FTBFS  - ~120 blocked by dependencies that FTBFS Ideally, this would all get fixed before the merge, but that's unrealistic, there are packages that are FTBFS for

Re: What is the criterion for Python 3.7 side tag merge?

2018-06-28 Thread Kalev Lember
On 06/28/2018 03:42 PM, Miro Hrončok wrote: The Python 3.7 rebuild in the f29-python side tag is currently:  - 2168 built  - ~170 FTBFS  - ~120 blocked by dependencies that FTBFS Ideally, this would all get fixed before the merge, but that's unrealistic, there are packages that are FTBFS

Re: What is the criterion for Python 3.7 side tag merge?

2018-06-28 Thread Jason L Tibbitts III
> "MH" == Miro Hrončok writes: MH> What is the criterion to merge the side tag? I think ultimately that's up to you, but certainly the idea is to balance disruption (breaking builds or rawhide usability) against holding back progress (the approved python 3.7 feature). It would certainly be

Re: What is the criterion for Python 3.7 side tag merge?

2018-06-28 Thread Jason L Tibbitts III
> "MH" == Miro Hrončok writes: MH> What is the criterion to merge the side tag? I think ultimately that's up to you, but certainly the idea is to balance disruption (breaking builds or rawhide usability) against holding back progress (the approved python 3.7 feature). It would certainly be

Re: What is the criterion for Python 3.7 side tag merge?

2018-06-28 Thread Laura Abbott
On 06/28/2018 06:42 AM, Miro Hrončok wrote: Stuff that doesn't build and sounds important:  - ceph (also FTBFS in regular rawhide)  - libreoffice (also FTBFS in regular rawhide)  - orca (blocked by pyatspi, looking at it ATM)  - kernel-tools For kernel-tools, it depends on your definition

What is the criterion for Python 3.7 side tag merge?

2018-06-28 Thread Miro Hrončok
The Python 3.7 rebuild in the f29-python side tag is currently: - 2168 built - ~170 FTBFS - ~120 blocked by dependencies that FTBFS Ideally, this would all get fixed before the merge, but that's unrealistic, there are packages that are FTBFS for unrelated reasons, etc. What is the

What is the criterion for Python 3.7 side tag merge?

2018-06-28 Thread Miro Hrončok
The Python 3.7 rebuild in the f29-python side tag is currently: - 2168 built - ~170 FTBFS - ~120 blocked by dependencies that FTBFS Ideally, this would all get fixed before the merge, but that's unrealistic, there are packages that are FTBFS for unrelated reasons, etc. What is the