https://bugs.meego.com/show_bug.cgi?id=14985 Summary: nightly testing: Evolution 2.32 + Debian Testing Classification: MeeGo Projects Product: SyncEvolution Version: unspecified Platform: All Architecture: --- Status: NEW Severity: major Priority: High Component: SyncEvolution AssignedTo: syncevolution-bugs(a)meego.bugs ReportedBy: patrick.ohly(a)intel.com QAContact: jingke.zhang(a)intel.com CC: syncevolution-bugs(a)meego.bugs, syncevolution-default-bugs(a)meego.bugs Estimated Hours: 0.0 Our current "testing" chroot is actually Debian Squeeze, with Evolution 2.30. It should be archived (just in case), then updated to Debian testing. This will lead to several problems: 1. Evolution 2.32 uses a different layout of files (.evolution -> .config/.local) which is no longer compatible with previous releases. The "nightly" account is mounted the same way in all chroots, so once Evolution 2.32 rewrites the files, older Evolution releases in other chroots will no longer find them. Solution a) create an archive of the relevant files in each chroot, wipe out files and recreate from the right archive in setup-syncevolution.sh. There should be a schroot env variable which describes the chroot, that might be usable to determine the right archive. Relevant are: .evolution .gconf* .*/evolution .*/*/evolution Solution b) mount different "nightly" home directories in each chroot. I prefer solution a) because the rest of the files (like ~nightly/results) can still be shared. Note that some chroots currently fail the "open default database" test, probably because these databases already do not exist anymore. Need to run Evolution UI to create them. 2. Evolution 2.32 no longer supports file:// URIs. The nightly testing uses those to create test databases in /tmp. We have to switch to a CLIENT_TEST_EVOLUTION_PREFIX which names existing local databases, which have to be created in the UI first in each chroot. -- Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. You are watching someone on the CC list of the bug.