Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionToshio Ernie Kuratomi
2011-01-17 18:16:07 UTC
Description of problem:
The version of python-turbokid in RHEL6.0 has a bug where templates are not reloaded when modified. This causes development of applications to be slowed somewhat as the web application being tested needs to be manually restarted instead of automatically detecting the change and restarting itself.
Version-Release number of selected component (if applicable):
python-turbokid-1.0.5-3.el6.noarch
How reproducible:
100%
Steps to Reproduce:
1. rpm -q python-turbokid
2.
3.
Actual results:
python-turbokid-1.0.5-3.el6.noarch
Expected results:
turbokid-1.0.5
Additional info:
Upstream TurboGears has a hard requirement on the updated version of turbokid which the TurboGears package in EPEL6 has to patch out for now so that it can run (the justification being that the older version of turbokid does not prevent deploying apps, it just makes developing apps a pain). When this is updated EPEL6 can drop that patch.
Comment 1Toshio Ernie Kuratomi
2011-01-17 18:20:45 UTC
Cut and paste error in my report; Expected and Actual results should be:
Actual Results:
python-turbokid-1.0.4-4.1.el6.noarch
Expected Results:
python-turbokid-1.0.5-3.el6.noarch
Comment 3RHEL Program Management
2011-01-17 18:38:14 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 4Toshio Ernie Kuratomi
2011-01-17 18:52:38 UTC
I'm more than happy to have this evaluated for 6.1, 6.2 or a later RHEL-6.x release. If this is a no for any 6.x release, please specify that, thanks.
(In reply to Matt Domsch from comment #5)
> please re-evaluate including this is a future RHEL6 update.
Red Hat, can you share plans to include this in RHEL 6.x?
I have stopped maintaining anything that uses TurboGears with the advent of MirrorManager v2. I have no personal or work interest in this request any longer. Thanks. -Matt
Comment 13Petr Viktorin (pviktori)
2016-07-14 14:35:13 UTC
Red Hat Enterprise Linux version 6 is entering the Production 2 phase of its lifetime and this bug doesn't meet the criteria for it, i.e. only high severity issues will be fixed. Please see https://access.redhat.com/support/policy/updates/errata/ for further information.