Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 224529 - net-zope/tinytableplus broken on zope-2.8 and higher
Summary: net-zope/tinytableplus broken on zope-2.8 and higher
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: net-zope (OBSOLETE)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-01 20:55 UTC by Steve Arnold
Modified: 2008-07-21 20:40 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
patch for zope 2.8 and higher (tinytableplus-0.9-zope2.patch,438 bytes, patch)
2008-06-01 20:58 UTC, Steve Arnold
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Arnold archtester gentoo-dev 2008-06-01 20:55:46 UTC
This package needs a patch for the changes in naming of the persistent.mapping module.  The patch should only be applied for zope 2.8 and higher.
Comment 1 Steve Arnold archtester gentoo-dev 2008-06-01 20:58:25 UTC
Created attachment 155159 [details, diff]
patch for zope 2.8 and higher

updates persistent.mapping import statement
Comment 2 Steve Arnold archtester gentoo-dev 2008-06-28 18:55:04 UTC
Action Jackson?  This is required for anyone using SquishDot...
Comment 3 Steve Arnold archtester gentoo-dev 2008-07-12 17:57:04 UTC
Okay, the patched tinytables and squishdot build/run correctly on my x86 server; I'll be migrating a large Zope site over to it shortly (from a much older version of zope) so I may be busy for a while...

Also, tinytables and squishdot both build fine on amd64, so it should be okay to keyword both for ~amd64.  Zope 3 runs fine on my amd64 box, once I fixed the permissions on the z3.log file, but from the looks of it, I'm not sure the legacy squishdot (or any other legacy zope products for that matter) would even work in zope 3, so I probably won't migrate my production site to zope 3 for a while.

That said, I haven't been keeping up much with current zope/plone developments, so maybe it's not that big of a migration path, but I've been buried in my own work for a while, so I really have no idea.

My recommendation would be to commit the patch for zope versions >=2.8 but <3.0 and then deal with newer versions of zope later (ie, once I find out more about migrating from 2.x to 3.0 or someone files a relevant bug).

How does that sound?
Comment 4 Tupone Alfredo gentoo-dev 2008-07-21 20:40:41 UTC
Patch has been applied in CVS. Thanks