On Thu, Mar 31, 2011 at 11:03:30PM +0100, Neil Jerram wrote: > Hi there... > > When I recently switched from SHR-T to SHR-U, I just copied across my > pim.db, and I discovered that Messages would then crash sometimes (on > startup). Investigation showed that this was because the code was > expecting some fields to be of a certain type, and the older messages > in the pim.db didn't conform to that. > > Now of course that makes perfect sense - because of course SHR-U needs > to be free to change fields from time to time - and I assume that > simply copying an old pim.db isn't intended to be a supported > workflow. > > In this case, however, it turns out to be easy to enhance the code to > allow both the old and new types, and the following patch does that. > Given that it is quite easy, what do you think about taking this > patch? > > Alternatively, what methods are there for upgrading an old pim.db?
this is what was shown during last year after every frameworkd opkg upgrade
pkg_postinst_${PN} () {
echo "*IMPORTANT NOTICE*: There has been a change in internal opimd
database structure as well as in the backend mechanism."
echo " This change is not backwards compatible so a conversion is
needed, furthermore, since new opimd does not (and will not) support working
with SIM, importing your SIM data is also required."
echo " In order to import SIM contacts, please use PISI."
echo " If you still have old contacts with 'tel:' prefix instead of
field types (i.e you haven't upgraded since 26.1.2010) please run the
'remove-tel' script first."
echo " For the database conversion:"
echo " 1) stop frameworkd '/etc/init.d/frameworkd stop'"
echo " 2) use the conversion script, called: 'opimd_convert_db'
which is already installed in your system"
echo " 3) restart your device"
}
http://git.openembedded.org/cgit.cgi/openembedded/commit/?id=509dbd7d97ca5544ce6fe287f0465b9d86aad2f3
I've removed this postinst about 2 months ago
http://git.openembedded.org/cgit.cgi/openembedded/commit/?id=1f4d72bf332d3e843c42767d3e34f5b953c22c33
1) 1/3 doesn't read that
2) 1/3 reads that everytime and isn't sure if it's still that old conversion or
something new
3) 1/3 just reflashes with newer image and copy old pim.db before first
framework upgrade
(so they don't have a chance to notice this warning)
--
Martin 'JaMa' Jansa jabber: [email protected]
pgpHmf1xIDxhG.pgp
Description: PGP signature
_______________________________________________ Shr-devel mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-devel
