Since RHEL7 has been released, EPEL7 won't be far behind. Before we get there, I'm planning to retire the TurboGears (v1, not Turbogears2) stack in epel7. In Fedora Infrastructure we are planning to migrate away from TurboGears1 rather than continue maintaining it throughout EPEL7's lifetime.
If someone steps up to say they'll take ownership of TurboGears1 (one of the comaintainers or someone new), then I'll reassign these packages to them. If no one does, then I'll retire them in epel7 and ask that the packages be removed from the download repos before epel7 leaves beta. Someone can revive them later if they're interested.
Let me know soon -- I'm planning to retire the packages no one says they're interested in maintaining at the end of this week so that they don't accidentally sneak into EPEL7 with no active maintainance.
== Packages to be orphaned retired == * python-cherrypy2 * python-elixir * python-peak-rules * python-turbocheetah * bodhi * python-tgcaptcha2 * python-turboflot * python-turbokid (need to remove a spurious dep on this from TurboGears2) * python-turbojson (need to remove a spurious dep on this from TurboGears2) * python-paste-script (this one has other dependents in Fedora but none in EPEL7. Please speak up or revive this later if you're interested)
Full lists of deps found (you don't need to read this unless you want to see what other packages are in the dep tree that won't be touched by this):
== Found TurboGears Deps ==
=== Requires: TG === Retire these
bodhi-server-0:0.9.8-2.el7.noarch python-tgcaptcha2-0:0.2.0-5.el7.noarch python-turboflot-0:0.7.0-4.el7.noarch
=== BR: TurboGears === Retire these (same set as Requires: TG)
bodhi-0:0.9.8-2.el7.src python-tgcaptcha2-0:0.2.0-5.el7.src python-turboflot-0:0.7.0-4.el7.src
=== TG Requires ===
==== Not needed by anything else ====
python-cherrypy2 python-elixir >= 0.6.1 python-peak-rules python-tgmochikit python-turbocheetah >= 1.0 python-turbojson >= 1.3
==== Maybe not needed by anything else ====
# TurboGears2? :: python-turbokid >= 1.0.5 Is this a spurious dep?
# ? :: python-paste-script >= 1.7 Nothing requires or BuildRequires this but maybe it's a needed thing for the paste stack?
==== Do not retire these ==== # TurboGears2 :: python-tw-forms >= 0.9.6 # RHEL :: python-configobj >= 4.3.2 # RHEL :: python-dateutil # RHEL :: python-webtest # RHEL :: python-nose >= 0.9.3 :: # RHEL :: python-setuptools >= 0.6c11 # python-sqlobject, python-tw-forms :: python-formencode >= 1.2.1 # TurboGears2 :: python-genshi >= 0.4.4 # Needed by repoview, python-turbokid :: python-kid # Probably an optional dep of SQLAlchemy python-psycopg2 # fedmsg, python-fedora, many others :: python-simplejson >= 1.9.1 # mirrorbrain-tools, python-mb :: python-sqlobject >= 0.10.1 # TurboGears2, python-tw-forms :: python-toscawidgets >= 0.9.6
=== TG BR ===
==== Not needed by anything else ==== python-cherrypy2 python-elixir python-peak-rules python-tgmochikit python-turbocheetah python-turbokid >= 1.0.5
==== Maybe not needed by anything else ==== # ? :: python-paste-script Nothing requires or BR's this but maybe it's a primary portion of hte paste stack?
# TurboGears2? :: python-turbojson Is this a spurious dep?
==== Do not retire ==== dos2unix python-configobj python-dateutil python-formencode python-genshi python-kid python-nose python-setuptools python-simplejson python-sqlalchemy python-sqlobject python-tw-forms python-webtest python2-devel python-toscawidgets
-Toshio
On Mon, Jun 16, 2014 at 12:01:26PM -0700, Toshio Kuratomi wrote:
If someone steps up to say they'll take ownership of TurboGears1 (one of the comaintainers or someone new), then I'll reassign these packages to them. If no one does, then I'll retire them in epel7 and ask that the packages be removed from the download repos before epel7 leaves beta. Someone can revive them later if they're interested.
== Packages to be orphaned retired ==
- python-cherrypy2
- python-elixir
- python-peak-rules
- python-turbocheetah
- bodhi
- python-tgcaptcha2
- python-turboflot
- python-turbokid (need to remove a spurious dep on this from TurboGears2)
- python-turbojson (need to remove a spurious dep on this from TurboGears2)
- python-paste-script (this one has other dependents in Fedora but none in EPEL7. Please speak up or revive this later if you're interested)
These have now been retired. If someone is interested in them, feel free to revive.
-Toshio
Hi Toshio,
I have just noticed this message after I failed to install TurboGears (v1) on CentOS 7.
We really need the TurboGears (v1) support via epel for el7. Migrating away from TurboGears V1 to V2 or to other framework seems impossible for us at the moment, though we know that we will have to migrate in future.
Could you help to suggest what we could do to revive these packages and have epel7 will still support TurboGears( v1 )?
------------------------------ Best Regards Jacky
-----Original Message----- From: epel-devel-bounces@lists.fedoraproject.org [mailto:epel-devel-bounces@lists.fedoraproject.org] On Behalf Of Toshio Kuratomi Sent: Saturday, 21 June 2014 3:02 AM To: epel-devel@lists.fedoraproject.org Subject: Re: EPEL Orphan or retire the TurboGears (v1) stack in 7
On Mon, Jun 16, 2014 at 12:01:26PM -0700, Toshio Kuratomi wrote:
If someone steps up to say they'll take ownership of TurboGears1 (one of the comaintainers or someone new), then I'll reassign these packages to them. If no one does, then I'll retire them in epel7 and ask that the packages be removed from the download repos before epel7 leaves beta. Someone can revive them later if they're interested.
== Packages to be orphaned retired ==
- python-cherrypy2
- python-elixir
- python-peak-rules
- python-turbocheetah
- bodhi
- python-tgcaptcha2
- python-turboflot
- python-turbokid (need to remove a spurious dep on this from
TurboGears2)
- python-turbojson (need to remove a spurious dep on this from
TurboGears2)
- python-paste-script (this one has other dependents in Fedora but none in EPEL7. Please speak up or revive this later if you're interested)
These have now been retired. If someone is interested in them, feel free to revive.
-Toshio [wargaming.net] EgzO3mXGcK This e-mail may contain CONFIDENTIAL AND PROPRIETARY INFORMATION and/or PRIVILEGED AND CONFIDENTIAL COMMUNICATION intended solely for the recipient and, therefore, may not be retransmitted to any party outside of the recipient's organization without the prior written consent of the sender. If you have received this e-mail in error please notify the sender immediately by telephone or reply e-mail and destroy the original message without making a copy. Wargaming.net accepts no liability for any losses or damages resulting from infected e-mail transmissions and viruses in e-mail attachment. kgzO3mXGcg
On Thu, Jul 10, 2014 at 05:39:40AM +0000, Zhiwei Zhu wrote:
Hi Toshio,
I have just noticed this message after I failed to install TurboGears (v1) on CentOS 7.
We really need the TurboGears (v1) support via epel for el7. Migrating away from TurboGears V1 to V2 or to other framework seems impossible for us at the moment, though we know that we will have to migrate in future.
Could you help to suggest what we could do to revive these packages and have epel7 will still support TurboGears( v1 )?
Sure! Become a package maintainer and maintain the packages that have become orphaned in EPEL7.
Note that you won't need to revive all of the packages -- some of those were retired because they depend on TurboGears1 (for instance, bodhi). You'll only need to revive the ones that TurboGears1 depends on (and those that your applications need).
-Toshio
Best Regards Jacky
-----Original Message----- From: epel-devel-bounces@lists.fedoraproject.org [mailto:epel-devel-bounces@lists.fedoraproject.org] On Behalf Of Toshio Kuratomi Sent: Saturday, 21 June 2014 3:02 AM To: epel-devel@lists.fedoraproject.org Subject: Re: EPEL Orphan or retire the TurboGears (v1) stack in 7
On Mon, Jun 16, 2014 at 12:01:26PM -0700, Toshio Kuratomi wrote:
If someone steps up to say they'll take ownership of TurboGears1 (one of the comaintainers or someone new), then I'll reassign these packages to them. If no one does, then I'll retire them in epel7 and ask that the packages be removed from the download repos before epel7 leaves beta. Someone can revive them later if they're interested.
== Packages to be orphaned retired ==
- python-cherrypy2
- python-elixir
- python-peak-rules
- python-turbocheetah
- bodhi
- python-tgcaptcha2
- python-turboflot
- python-turbokid (need to remove a spurious dep on this from
TurboGears2)
- python-turbojson (need to remove a spurious dep on this from
TurboGears2)
- python-paste-script (this one has other dependents in Fedora but none in EPEL7. Please speak up or revive this later if you're interested)
These have now been retired. If someone is interested in them, feel free to revive.
-Toshio [wargaming.net] EgzO3mXGcK This e-mail may contain CONFIDENTIAL AND PROPRIETARY INFORMATION and/or PRIVILEGED AND CONFIDENTIAL COMMUNICATION intended solely for the recipient and, therefore, may not be retransmitted to any party outside of the recipient's organization without the prior written consent of the sender. If you have received this e-mail in error please notify the sender immediately by telephone or reply e-mail and destroy the original message without making a copy. Wargaming.net accepts no liability for any losses or damages resulting from infected e-mail transmissions and viruses in e-mail attachment. kgzO3mXGcg _______________________________________________ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
On Thu, Jul 10, 2014 at 9:19 PM, Toshio Kuratomi a.badger@gmail.com wrote:
On Thu, Jul 10, 2014 at 05:39:40AM +0000, Zhiwei Zhu wrote:
Hi Toshio,
I have just noticed this message after I failed to install TurboGears (v1) on CentOS 7.
We really need the TurboGears (v1) support via epel for el7. Migrating away from TurboGears V1 to V2 or to other framework seems impossible for us at the moment, though we know that we will have to migrate in future.
Could you help to suggest what we could do to revive these packages and have epel7 will still support TurboGears( v1 )?
Sure! Become a package maintainer and maintain the packages that have become orphaned in EPEL7.
Note that you won't need to revive all of the packages -- some of those were retired because they depend on TurboGears1 (for instance, bodhi). You'll only need to revive the ones that TurboGears1 depends on (and those that your applications need).
"Best" solution.
Hi Toshio,
Thanks. Understand the situation now. Will discuss with my lead about the possibility to maintain the packages by ourselves.
BTW, as we don't have experience of maintaining packages on epel, we have no idea how much effort will be required to do that or how difficult it would be. Could you help to share something about this? I understand that there is some kind of co-maintainer path to take for new maintainers but don't how to start it.
------------------------------ Best Regards Jacky
-----Original Message----- From: epel-devel-bounces@lists.fedoraproject.org [mailto:epel-devel-bounces@lists.fedoraproject.org] On Behalf Of Toshio Kuratomi Sent: Thursday, 10 July 2014 11:20 PM To: EPEL Development List Subject: Re: EPEL Orphan or retire the TurboGears (v1) stack in 7
On Thu, Jul 10, 2014 at 05:39:40AM +0000, Zhiwei Zhu wrote:
Hi Toshio,
I have just noticed this message after I failed to install TurboGears (v1) on CentOS 7.
We really need the TurboGears (v1) support via epel for el7. Migrating away from TurboGears V1 to V2 or to other framework seems impossible for us at the moment, though we know that we will have to migrate in future.
Could you help to suggest what we could do to revive these packages and have epel7 will still support TurboGears( v1 )?
Sure! Become a package maintainer and maintain the packages that have become orphaned in EPEL7.
Note that you won't need to revive all of the packages -- some of those were retired because they depend on TurboGears1 (for instance, bodhi). You'll only need to revive the ones that TurboGears1 depends on (and those that your applications need).
-Toshio
Best Regards Jacky
-----Original Message----- From: epel-devel-bounces@lists.fedoraproject.org [mailto:epel-devel-bounces@lists.fedoraproject.org] On Behalf Of Toshio Kuratomi Sent: Saturday, 21 June 2014 3:02 AM To: epel-devel@lists.fedoraproject.org Subject: Re: EPEL Orphan or retire the TurboGears (v1) stack in 7
On Mon, Jun 16, 2014 at 12:01:26PM -0700, Toshio Kuratomi wrote:
If someone steps up to say they'll take ownership of TurboGears1 (one of the comaintainers or someone new), then I'll reassign these packages to them. If no one does, then I'll retire them in epel7 and ask that the packages be removed from the download repos before epel7 leaves beta. Someone can revive them later if they're interested.
== Packages to be orphaned retired ==
- python-cherrypy2
- python-elixir
- python-peak-rules
- python-turbocheetah
- bodhi
- python-tgcaptcha2
- python-turboflot
- python-turbokid (need to remove a spurious dep on this from
TurboGears2)
- python-turbojson (need to remove a spurious dep on this from
TurboGears2)
- python-paste-script (this one has other dependents in Fedora but none in EPEL7. Please speak up or revive this later if you're interested)
These have now been retired. If someone is interested in them, feel free to revive.
-Toshio [wargaming.net] EgzO3mXGcK This e-mail may contain CONFIDENTIAL AND PROPRIETARY INFORMATION and/or PRIVILEGED AND CONFIDENTIAL COMMUNICATION intended solely for the recipient and, therefore, may not be retransmitted to any party outside of the recipient's organization without the prior written consent of the sender. If you have received this e-mail in error please notify the sender immediately by telephone or reply e-mail and destroy the original message without making a copy. Wargaming.net accepts no liability for any losses or damages resulting from infected e-mail transmissions and viruses in e-mail attachment. kgzO3mXGcg _______________________________________________ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Excerpts from Zhiwei Zhu's message of 2014-07-11 09:31:37 +1000:
Thanks. Understand the situation now. Will discuss with my lead about the possibility to maintain the packages by ourselves.
BTW, as we don't have experience of maintaining packages on epel, we have no idea how much effort will be required to do that or how difficult it would be. Could you help to share something about this? I understand that there is some kind of co-maintainer path to take for new maintainers but don't how to start it.
I had hoped we would have Beaker ported off TG1 long before now, and I was going to use the retirement of the EPEL7 TG1 stack as extra motivation to get it done, but realistically we will be depending on it for quite a while still, just like you Zhiwei.
So I can maintain the TG1 stack in EPEL7. I will start the un-retiring process for all the packages we need and post the exact list here.
Zhiwei, if you would like to co-maintain that would be a great help. I'm not able to sponsor you into the packager group, but I think you can be a co-maintainer without a sponsor (actually I'm not sure about that...)
Hi Dan,
Thanks for sharing this. It's really a great news for us that you will help to maintain the TG1 stack in EPEL7 and will start the un-retiring process. Hope they will be available again soon.
Yes, when talking about real projects, when schedules, requirements, efforts, resources, risks, etc, are involved, the reality is always far away from the theory. We should have planned the migration from TG1 in this release. However, probably because there is no obvious benefit that we can get from it, it's never been given a high priority. I think this show-stopper will push us to really consider the migration seriously in future releases, either to TG2 or to Django.
For co-maintaining the TG1 stack, I would like to and will start to look into how to do that, but I hope it could be recovered before I can really offer any help, because our currently release is kind of blocked by this issue. A lot of tasks, plans depend on whether TG1 would be availble on EPEL7. We are going to discuss our platform support stuff early next week and hope there would be some more good news then:)
------------------------------ Best Regards Jacky
-----Original Message----- From: Dan Callaghan [mailto:dcallagh@redhat.com] Sent: Friday, 11 July 2014 10:42 AM To: Zhiwei Zhu Cc: EPEL Development List Subject: Re: EPEL Orphan or retire the TurboGears (v1) stack in 7
Excerpts from Zhiwei Zhu's message of 2014-07-11 09:31:37 +1000:
Thanks. Understand the situation now. Will discuss with my lead about the possibility to maintain the packages by ourselves.
BTW, as we don't have experience of maintaining packages on epel, we have no idea how much effort will be required to do that or how difficult it would be. Could you help to share something about this? I understand that there is some kind of co-maintainer path to take for new maintainers but don't how to start it.
I had hoped we would have Beaker ported off TG1 long before now, and I was going to use the retirement of the EPEL7 TG1 stack as extra motivation to get it done, but realistically we will be depending on it for quite a while still, just like you Zhiwei.
So I can maintain the TG1 stack in EPEL7. I will start the un-retiring process for all the packages we need and post the exact list here.
Zhiwei, if you would like to co-maintain that would be a great help. I'm not able to sponsor you into the packager group, but I think you can be a co-maintainer without a sponsor (actually I'm not sure about that...)
-- Dan Callaghan dcallagh@redhat.com Software Engineer, Hosted & Shared Services Red Hat, Inc.
On Fri, Jul 11, 2014 at 01:17:29AM +0000, Zhiwei Zhu wrote:
For co-maintaining the TG1 stack, I would like to and will start to look into how to do that, but I hope it could be recovered before I can really offer any help, because our currently release is kind of blocked by this issue. A lot of tasks, plans depend on whether TG1 would be availble on EPEL7. We are going to discuss our platform support stuff early next week and hope there would be some more good news then:)
It sounds like Dan would be willing to mentor you asw a comaintainer of the TG1 stack. If so, you can follow this policy: http://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#B...
to get sponsored quicker.
-Toshio
Excerpts from Toshio Kuratomi's message of 2014-07-13 03:56:30 +1000:
On Fri, Jul 11, 2014 at 01:17:29AM +0000, Zhiwei Zhu wrote:
For co-maintaining the TG1 stack, I would like to and will start to look into how to do that, but I hope it could be recovered before I can really offer any help, because our currently release is kind of blocked by this issue. A lot of tasks, plans depend on whether TG1 would be availble on EPEL7. We are going to discuss our platform support stuff early next week and hope there would be some more good news then:)
It sounds like Dan would be willing to mentor you asw a comaintainer of the TG1 stack. If so, you can follow this policy: http://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#B...
to get sponsored quicker.
Yes, I forgot to mention it before. Unfortunately I'm not a sponsor so I can't sponsor you myself, Jacky, but I can mentor you as co-maintainer.
Hi Dan,
Thanks for the update.
The packages you listed in previous emails should be enough for us: * python-cherrypy2 * python-elixir * python-peak-rules * python-turbokid * python-turbojson * python-turbocheetah * python-paste-script + * python-TurboMail * python-tgmochikit * TurboGears
Look forward to the recovery of them.
I went through the page mentioned by Toshio about becoming a co-maintainer. It seems the first problem for me is to get sponsored.
------------------------------ Best Regards Jacky
-----Original Message----- From: epel-devel-bounces@lists.fedoraproject.org [mailto:epel-devel-bounces@lists.fedoraproject.org] On Behalf Of Dan Callaghan Sent: Monday, 14 July 2014 9:25 AM To: EPEL Development List Subject: Re: EPEL Orphan or retire the TurboGears (v1) stack in 7
Excerpts from Toshio Kuratomi's message of 2014-07-13 03:56:30 +1000:
On Fri, Jul 11, 2014 at 01:17:29AM +0000, Zhiwei Zhu wrote:
For co-maintaining the TG1 stack, I would like to and will start to look into how to do that, but I hope it could be recovered before I can really offer any help, because our currently release is kind of blocked by this issue. A lot of tasks, plans depend on whether TG1 would be availble on EPEL7. We are going to discuss our platform support stuff early next week and hope there would be some more good news then:)
It sounds like Dan would be willing to mentor you asw a comaintainer of the TG1 stack. If so, you can follow this policy: http://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_g roup#Become_a_co-maintainer
to get sponsored quicker.
Yes, I forgot to mention it before. Unfortunately I'm not a sponsor so I can't sponsor you myself, Jacky, but I can mentor you as co-maintainer.
-- Dan Callaghan dcallagh@redhat.com Software Engineer, Hosted & Shared Services Red Hat, Inc. [wargaming.net] EgzO3mXGcK This e-mail may contain CONFIDENTIAL AND PROPRIETARY INFORMATION and/or PRIVILEGED AND CONFIDENTIAL COMMUNICATION intended solely for the recipient and, therefore, may not be retransmitted to any party outside of the recipient's organization without the prior written consent of the sender. If you have received this e-mail in error please notify the sender immediately by telephone or reply e-mail and destroy the original message without making a copy. Wargaming.net accepts no liability for any losses or damages resulting from infected e-mail transmissions and viruses in e-mail attachment. kgzO3mXGcg
I was just looking through the list of packages which Toshio retired:
Excerpts from Toshio Kuratomi's message of 2014-06-17 05:01:26 +1000:
== Packages to be orphaned retired ==
- python-cherrypy2
- python-elixir
- python-peak-rules
- python-turbocheetah
- bodhi
- python-tgcaptcha2
- python-turboflot
- python-turbokid (need to remove a spurious dep on this from TurboGears2)
- python-turbojson (need to remove a spurious dep on this from TurboGears2)
- python-paste-script (this one has other dependents in Fedora but none in EPEL7. Please speak up or revive this later if you're interested)
I think the only ones out of these which we need for Beaker (unless I have missed some transitive deps) are:
* python-cherrypy2 * python-elixir * python-peak-rules * python-turbokid * python-turbojson * python-turbocheetah * python-paste-script
Jacky, will that be enough for you?
I'm a little confused now though... I would have also expected these other TG1 pieces to be on the list:
* python-TurboMail * python-tgmochikit * TurboGears
but it looks like they are not retired... Toshio, is there some reason you left them out?
On Fri, Jul 11, 2014 at 05:41:04PM +1000, Dan Callaghan wrote:
I'm a little confused now though... I would have also expected these other TG1 pieces to be on the list:
- python-TurboMail
This doesn't have a dep on TurboGears in them so my repoquery didn't pick it up. Possibly a packaging bug. I'm pretty sure that lmacken won't want to maintain this on EPEL7 either so you'll probably want to pick it up if you need to send email from the web app.
- python-tgmochikit
This was my mistake... I remember asking lmacken about it but I just didn't retire it when I retired the others.
- TurboGears
This was also my mistake. TurboGears isn't a dep of itself nor does it require itself... so when I went down the list of deps, I forgot to orphan it either. Oops.
Dan, would you like me to reassign the epel7 branch of all three of these packages to you?
-Toshio
Excerpts from Toshio Kuratomi's message of 2014-07-13 03:53:19 +1000:
On Fri, Jul 11, 2014 at 05:41:04PM +1000, Dan Callaghan wrote:
I'm a little confused now though... I would have also expected these other TG1 pieces to be on the list:
- python-TurboMail
This doesn't have a dep on TurboGears in them so my repoquery didn't pick it up. Possibly a packaging bug. I'm pretty sure that lmacken won't want to maintain this on EPEL7 either so you'll probably want to pick it up if you need to send email from the web app.
- python-tgmochikit
This was my mistake... I remember asking lmacken about it but I just didn't retire it when I retired the others.
- TurboGears
This was also my mistake. TurboGears isn't a dep of itself nor does it require itself... so when I went down the list of deps, I forgot to orphan it either. Oops.
Dan, would you like me to reassign the epel7 branch of all three of these packages to you?
Yes we are using all three of these, in addition to the others I listed. So please assign these to me, and I will start the unretirement process on the others.
On Mon, Jul 14, 2014 at 09:26:24AM +1000, Dan Callaghan wrote:
Excerpts from Toshio Kuratomi's message of 2014-07-13 03:53:19 +1000:
Dan, would you like me to reassign the epel7 branch of all three of these packages to you?
Yes we are using all three of these, in addition to the others I listed. So please assign these to me, and I will start the unretirement process on the others.
Done!
-Toshio
Excerpts from Dan Callaghan's message of 2014-07-11 17:41 +10:00:
- python-cherrypy2
- python-elixir
- python-peak-rules
- python-turbokid
- python-turbojson
- python-turbocheetah
- python-paste-script
These have now been un-retired and unblocked, they should appear in EPEL7 soon (within 24 hours I think).
epel-devel@lists.fedoraproject.org