Toshio Kuratomi schrieb:

• Note: Felix, Luke, and I haven't banged out a definite opinion on what

we ideally want to do in this situation yet... since this seems to touch on some rather basic EPEL policy, I thought it needed to be brought here for comment.

A short addition: I asked on the TurboGears mailing list for opinions (nearly every TurboGears users will use formencode too) and got some responses - mainly "update to 1.0.1 was ok, some minor problems": http://groups.google.com/group/turbogears/browse_thread/thread/bb4411abfc563...

fs

On Wed, Aug 06, 2008 at 01:05:11PM -0700, Toshio Kuratomi wrote:

Currently I've got a package python-toscawidgets-0.9 in epel. It is a python library that can have modules that add functionality. python-tw-forms is one of the major modules. This has just been reviewed and built for Fedora. Unfortunately, it needs a newer version of python-formencode than is in EPEL-5. Moreover, this is a newer version that can cause bugs if your code uses certain features of formencode.

How do we want to deal with this? Upgrade formencode? Upgrade formencode at a certain point in time? Remove toscawidgets since it's pretty useless? Create a parallel installable version of formencode for the new version?

Each of these has drawbacks. What's the initial leaning?

I'm initially leaning towards bringing FormEncode up to 1.0.1. We're going to have to make the leap anyway if we expect to get TG2 working in EPEL.

I haven't hit any regressions with 1.0.1 in any of my projects, so I'm not entirely sure what issues may arise.

luke