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
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
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
*
On Thu, Jul 10, 2014 at 05:39:40AM +, 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
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.
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
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,
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
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
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.
10 matches
Mail list logo
