Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 224529
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: net-zope <net-zope@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Steve Arnold <nerdboy@gentoo.org>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
tinytableplus-0.9-zope2.patch patch for zope 2.8 and higher patch Steve Arnold 2008-06-01 20:58 0000 438 bytes Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 224529 depends on: Show dependency tree
Bug 224529 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2008-06-01 20:55 0000
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 From Steve Arnold 2008-06-01 20:58:25 0000 -------
Created an attachment (id=155159) [details]
patch for zope 2.8 and higher

updates persistent.mapping import statement

------- Comment #2 From Steve Arnold 2008-06-28 18:55:04 0000 -------
Action Jackson?  This is required for anyone using SquishDot...

------- Comment #3 From Steve Arnold 2008-07-12 17:57:04 0000 -------
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 From Tupone Alfredo 2008-07-21 20:40:41 0000 -------
Patch has been applied in CVS. Thanks

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug