[EPEL-devel] Python 3 discussion

Orion Poplawski orion at cora.nwra.com
Tue Mar 3 18:01:23 UTC 2015


On 03/03/2015 08:35 AM, Kevin Fenzi wrote:
> On Tue, 3 Mar 2015 07:46:00 -0500 (EST)
> Bohuslav Kabrda <bkabrda at redhat.com> wrote:
> 
>>> ^ Is this step part of a coordinated mass-rebuild, or is this just a
>>> period of time after we make the announcement: "Hey Packagers: be
>>> sure to rebuild for python35"?
>>
>> That's a good question. I guess we should standardize how this will
>> be done. Something like:
>> - there's an announcement on epel-devel that python35 is the "main
>> python3" and packagers should rebuild their packagers (and users
>> their apps/scripts/...)
>> - wait for a week (two?)
>> - open bugs for packages that haven't been rebuilt during the
>> previous week and get them fixed ASAP
> 
> I'd say just doing the mass rebuild by a provenpackager or the like
> would be easier than filing bugs and waiting. 

Yeah, just do the builds and be done with it.  Will need to get built in dep
order.

> Also, we need to coordinate the update with them in it... ideally they
> would all be in the same update?

That's seem sure to crash bodhi :)

As long as deps are pushed out in the right order things would be okay.

-- 
Orion Poplawski
Technical Manager                     303-415-9701 x222
NWRA, Boulder/CoRA Office             FAX: 303-415-9702
3380 Mitchell Lane                       orion at nwra.com
Boulder, CO 80301                   http://www.nwra.com


More information about the epel-devel mailing list