Daniel James wrote: > Hi Ralf, > >> I guess there is a script that always tries to do this: >> >> File "/usr/lib/python2.5/site-packages/augeas.py", line 266, in save >> raise IOError, "Unable to save to file!" >> IOError: Unable to save to file! > > Yes, the script is /usr/sbin/64studio-config and it's a post-install > script for the 64studio package. Some package change has broken this > script between 3.0 beta 3 and now, and so I need to find a solution. > > If anyone who knows Python wants to delve into this in the meantime, > here is the traceback I got from a test install of the current master > image: > > in-target: Traceback (most recent call last): > in-target: File "/usr/sbin/64studio-config", line 24, in <module> > in-target: > in-target: main () > in-target: File "/usr/sbin/64studio-config", line 21, in main > in-target: > in-target: studio.save() > in-target: File "/var/lib/python-support/python2.5/remix.py", line 88, > in save > > in-target: > in-target: self._augeas.save() > in-target: File "/usr/lib/python2.5/site-packages/augeas.py", line > 266, in save > > in-target: > in-target: raise IOError, "Unable to save to file!" > in-target: IOError > in-target: : > in-target: Unable to save to file! > in-target: > in-target: dpkg: error processing 64studio (--configure) > > Cheers! > > Daniel
Hi Daniel :) maybe this is the only bug for 3.0 and I unerring but unwanted touched this package :D, hm, this is the risk when using a beta. Résumé: My install was clean ;) and maybe I can make it clean again, after restoring /usr/sbin/64studio-config from one of my backups :). What files will be changed by this script? If I restore the script and all files it would change, my 64 Studio 3.0-beta3 should be fine again. Cheers, Ralf _______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
