On Tuesday 21 July 2009 18:21:45 Adam Jimerson wrote: > >So I built a new unstable image. And updated the unstable feed. And I > > promise, that if I don't hear lots of complaints about the quality of the > > latest unstable image, I will release that one as the new shr-testing. > > First of all glad to see and update to unstable, this gives me a chance to > fully test out the newly updated opkg. Currently while upgrading I am > getting > a lot of "opkg: fork failed"'s but no segfaults yet so that is a plus, how > does opkg handle this now that it doesn't die, does it just mark the package > uninstalled and retry later, as it doesn't retry the same package > immediately, > or will I need to run the upgrade command again? I look forward to testing > out this images once it is finished updating.
I had a lot of problems during the update. First, I didn't used screen since it causes some problems with opkg. However, I lost the connection while updating dropbear. Thereafter, I got this error: can't get //usr/lib/opkg/info/etk-theme-shr.control open for read Don't know if it is related but after that the FR gave no response (not GUI, not ssh, only ping). Or I'm too inpatient? Nevertheless, I used this script http://build.shr-project.org/tests/shr-step-by-step-upgrade.sh and now I'm again at the bleeding edge :-) It isn't connecting to the GSM network. And no suspend. shr-settings tells me: Couldn't connect to FSO It seems, I have to boot my backup shr from the second partition ;-) Sven _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
