[EPEL-devel] Python 3 discussion

Kevin Fenzi kevin at scrye.com
Mon Mar 2 12:38:16 UTC 2015


On Mon, 2 Mar 2015 06:59:29 -0500 (EST)
Bohuslav Kabrda <bkabrda at redhat.com> wrote:

> ----- Original Message -----
> > Excerpts from Orion Poplawski's message of 2015-02-28 04:36 +10:00:
> > >             all python34 packages are retired
> > 
> > Except there is no way to retire an individual subpackage, is there?
> > Instead we are saying, the python34-* subpackage will just go away.
> 
> Yeah, I'm still not sure how this should be handled. Does anyone know
> whether the python34- subpackage will disappear from the repo if only
> python35- is built in a newer build? I'd tend to think so, since I
> think Koji builds repos from the newest builds, so if the package is
> rebuilt without python34- subpackage, it won't be there when the repo
> regenerates... But maybe I'm completely wrong here.

It would. mash pulls the 'latest tagged' build from the tag. So, if the
newer one has different subpackages that will get used and the old one
is completely gone. 

kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/epel-devel/attachments/20150302/1e246103/attachment.sig>


More information about the epel-devel mailing list