> I'm not sure this is a good idea to do on default and/or by the installer > package. Maybe the changes are not oncompatible, then the user looses her > settings for nothing.
I agree. > So IMO googleearth should deal with that, not googleearth-package. It's just a question how fast will they solve it? > I'd tag this upstream and leave it there, but I leave that to the maintainer. Yes, in Debian we try to not mess with users $HOME, I believe this is a upstream bug. Besides all, it's been a long time since you reported this bug and I didn't see anyone complaining with same problem. Adnan On Tue, Dec 7, 2010 at 12:29 PM, Holger Levsen <[email protected]> wrote: > Hi, > > On Dienstag, 7. Dezember 2010, Michael Below wrote: >> Today I updated googleearth-package from 0.5.7 to 0.6.1 and >> built and installed googleearth 6.0.0.1735. Before, I had a 5.x version >> installed (on AMD64, see the bug report about image artifacts). >> >> After the upgrade, googleearth wouldn't start anymore, see crash >> log below. Moving the .googleearth directory away helped, now >> googleearth starts fine. Obviously there are some >> incompatibilities between versions. If this happens on every >> upgrade, the installer should move .googleearth and inform the >> user. > > I'm not sure this is a good idea to do on default and/or by the installer > package. Maybe the changes are not oncompatible, then the user looses her > settings for nothing. > > So IMO googleearth should deal with that, not googleearth-package. > > I'd tag this upstream and leave it there, but I leave that to the maintainer. > > > cheers, > Holger > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
