List Info

Thread: 2.0.4->2.1.3 PloneCollector Breaks Dry Run




2.0.4->2.1.3 PloneCollector Breaks Dry Run
user name
2006-08-17 20:22:18
I think PloneCollectorNG is what's causing the error based
on the 
traceback below. Here's the deal though, I've got ver
1.2.7 installed 
since that's the last version that works with 2.0.x
(confirmed by trial 
and error) but I think 2.1.x requires 1.2.8+, So a little
classic 
chicken and egg problem.
If this is the problem hopefully Andreas will have a
solution.


Thanks, Alex

Can someone confirm my that it is PloneCollector based on
this log:
Plone Migration Tool Plone Migration Tool at 
/www/portal_migration


Result of the attempt...

     * Dry run selected.
     * Starting the migration from version: 2.0.4
     * Attempting to upgrade from: 2.0.4
     * Upgrade to: 2.0.5-rc1, completed
     * Attempting to upgrade from: 2.0.5-rc1
     * Upgrade to: 2.0.5-rc2, completed
     * Attempting to upgrade from: 2.0.5-rc2
     * Renamed Folder 'properties' tab to 'edit'.
     * Added 'folderlisting' action to Topics.
     * Interchanged 'edit' and 'sharing' tabs.
     * Upgrade to: 2.0.5, completed
     * Attempting to upgrade from: 2.0.5
     * Upgrade aborted
     * Error type:
Products.ATContentTypes.migration.walker.MigrationError
     * Error value: MigrationError for obj at
/www/applications (CMF 
Folder -> Folder): Traceback (most recent call last):
File 
"/home/amandel/zopesite/213/Products/ATContentTypes/mi
gration/walker.py", 
line 174, in migrate migrator.migrate() File 
"/home/amandel/zopesite/213/Products/ATContentTypes/mi
gration/migrator.py", 
line 196, in migrate method() File 
"/home/amandel/zopesite/213/Products/ATContentTypes/mi
gration/migrator.py", 
line 517, in migrate_children self.new._setObject(id, obj,
set_owner=0) 
File
"/home/amandel/zope/lib/python/OFS/ObjectManager.py&q
uot;, line 276, in 
_setObject object.manage_afterAdd(object, self) File 
"/home/amandel/zopesite/213/Products/PloneCollectorNG/
Collector.py", 
line 109, in manage_afterAdd
BaseBTreeFolder.manage_afterAdd(self, item, 
container) File 
"/home/amandel/zopesite/213/Products/Archetypes/BaseBT
reeFolder.py", 
line 37, in manage_afterAdd BaseFolder.manage_afterAdd(self,
item, 
container) File 
"/home/amandel/zopesite/213/Products/Archetypes/BaseFo
lder.py", line 
107, in manage_afterAdd
CatalogMultiplex.manage_afterAdd(self, item, 
container) File 
"/home/amandel/zopesite/213/Products/CMFCore/CMFCatalo
gAware.py", line 
199, in manage_afterAdd self.__recurse('manage_afterAdd',
item, 
container) File 
"/home/amandel/zopesite/213/Products/CMFCore/CMFCatalo
gAware.py", line 
235, in __recurse getattr(ob, name)(*args) File 
"/home/amandel/zopesite/213/Products/PloneCollectorNG/
Collector.py", 
line 952, in manage_afterAdd self._initIndexes() File 
"/home/amandel/zopesite/213/Products/CMFCore/CatalogTo
ol.py", line 188, 
in _initIndexes for index_name, index_type, extra in 
self.enumerateIndexes(): ValueError: unpack list of wrong
size
     * File 
"/home/amandel/zopesite/213/Products/CMFPlone/Migratio
nTool.py", line 
274, in upgrade newv, msgs = self._upgrade(newv)
     * File 
"/home/amandel/zopesite/213/Products/CMFPlone/Migratio
nTool.py", line 
371, in _upgrade res = function(self.aq_parent)
     * File 
"/home/amandel/zopesite/213/Products/CMFPlone/migratio
ns/v2_1/alphas.py", 
line 69, in two05_alpha1 migrateToATCT10(portal, out)
     * File 
"/home/amandel/zopesite/213/Products/CMFPlone/migratio
ns/v2_1/alphas.py", 
line 298, in migrateToATCT10 tool.migrateToATCT()
     * File 
"/home/amandel/zopesite/213/Products/ATContentTypes/to
ol/migration.py", 
line 240, in migrateToATCT out, elapse, c_elapse = 
self.migrateContentTypesToATCT(portal_types=None)
     * File 
"/home/amandel/zopesite/213/Products/ATContentTypes/to
ol/migration.py", 
line 260, in migrateContentTypesToATCT out =
migrateAll(portal)
     * File 
"/home/amandel/zopesite/213/Products/ATContentTypes/mi
gration/atctmigrator.py", 
line 239, in migrateAll migrator=migrator, **kwargs)
     * File 
"/home/amandel/zopesite/213/Products/ATContentTypes/mi
gration/common.py", 
line 224, in migratePortalType walk.go()
     * File 
"/home/amandel/zopesite/213/Products/ATContentTypes/mi
gration/walker.py", 
line 126, in go self.migrate(self.walk(), **kwargs)
     * File 
"/home/amandel/zopesite/213/Products/ATContentTypes/mi
gration/walker.py", 
line 205, in migrate raise MigrationError(objpath, migrator,
tb)
     * End of upgrade path, migration has finished
     * The upgrade path did NOT reach current version
     * Migration has failed
     * Dry run selected, transaction aborted

Return


_______________________________________________
Setup mailing list
Setuplists.plone.org
http://
lists.plone.org/mailman/listinfo/setup
2.0.4->2.1.3 PloneCollector Breaks Dry Run
user name
2006-08-18 08:27:36
Alex Mandel wrote:
> I think PloneCollectorNG is what's causing the error
based on the 
> traceback below. Here's the deal though, I've got ver
1.2.7 installed 
> since that's the last version that works with 2.0.x
(confirmed by trial 
> and error) but I think 2.1.x requires 1.2.8+, So a
little classic 
> chicken and egg problem.
Alex,
    Why is that chicken & egg?

In theory, shouldn't you be able to put PloneCollectorNG
1.2.8 in your 
new Plone 2.1 products directory, then when you try to
migrate to Plone 
2.1 it will have PloneCollectorNG 1.2.8?

If you're trying to migrate to Plone 2.1, with
PloneCollectorNG 1.2.7 in 
the Products dir, then I wouldn't expect that to work..

Or maybe I misunderstood you here..........


> Can someone confirm my that it is PloneCollector based
on this log:
> Plone Migration Tool Plone Migration Tool at 
/www/portal_migration

If it proves hard to confirm that just from your log, had
you thought of 
  simply on a test copy of your data, deleting
PloneCollectorNG from 
products (+ probably need to delete any related content
first, although 
with some luck migration should just ignore content from a 
no-longer-installed product), and try to migrate? If it then
works (or 
breaks somewhere else    ) at least
you know PloneCollectorNG was the 
problem.

In such sticky migration situations, using a debugger really
helps. You 
can patch stuff to make it work here because it only has to
work once...

Regards
Nick


-- 
Nick Davis
Web Application Developer
University of Leicester
http://www2.le.ac.uk
http://ebulletin.le.ac.uk


_______________________________________________
Setup mailing list
Setuplists.plone.org
http://
lists.plone.org/mailman/listinfo/setup
[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )