Talk:Olpc-update

Where the _bleep_ did my stuff go???

I just updated to 656, using the internet incremental update. Everything I installed on 653 is gone -- Java, Flash, XFCE, OpenOffice, a Java application, preference folders. You get the idea. However, all the space that they took up still seems used. I'm not back down to anything resembling a 300mb clean image.

So where's it hiding? Can it be recovered? If it can't be recovered, how do I reclaim the space?

IMO, there should be a big red warning on the update page about losing non-standard installs when updating. Better yet, why doesn't it respect what I've got on the machine, given that this is an incremental update that looks to be repeated fairly regularly as the base software evolves. After all, when I update from MacOS 10.4.10 to 10.4.11, all my non-Apple apps and data don't go away.

Rmyers 12:28, 1 February 2008 (EST)

Feature Requests

A request from a non-programmer for olpc-update and olpc-update-rsync commands:

Provide a --list (-l?) option that shows all available builds (easier to remember)
Provide a --changelog (-c?) option that shows a builds changelog (olpc-update -c build-609)
Provide --help (-h) to explain its usage, and the above options

HoboPrimate 00:04, 5 October 2007 (EDT)

 Done. You'll need very recent pyvserver and rainbow RPMs to try 
 these out. Also, you'll need to convince cscott to put ChangeLogs 
 in the rsync modules. (Or volunteer to do so yourself). 
   -- Michael Stone 01:54, 5 October 2007 (EDT)

When I click latest release, I see no file named osXYZ.usb, I see one called osXYZ.img, osXYZ.toc, etc. but no .usb. What gives?

Simplification needed

Gosh, this page is meaty and full of great stuff. However, if we are going to send users to it, it needs to be much simpler. Pictures are not out of the question. Alternatively, if there's another page to send users to for this, this we need to link it prominently in eg Support_FAQ. (And the Stable_Upgrade page is not even as clear as this page is).

On a related note, (why) do you need to specify the branch to get ship.2-653 ? This is counter to the documentation on this page. Edit: 653 is in a stable tree, but may not be officially stable in some sense (650 is still on front page of Wiki). I'm seeing conflicting reports of upgrades (usb and olpc-update) to 653, some not booting without a dev key. Thanks, --Adricnet 02:23, 25 December 2007 (EST)

How to get current Build Number? Unsuccessful olpc-update

(I'm a retired developer, but almost no Linux or Unix expertise.) First, there must be some some command to retrieve what build is in the machine. olpc-update --version does not give a build. Second, I did run through the olpc-update -rv 653 apparently successfully, but it refused to reboot because I have no developer key. Do I have to have one to update manually? If so, how do I get one. Thanks, --Javerell 20:20, 28 January 2008 (EST)

You shouldn't need an developer key, however you can request one easily. To tell what version you have, type "cat /etc/issue" on the terminal. ffm 17:33, 29 January 2008 (EST)

Keep getting error: "could not download update contents"

I've been trying

#olpc-update 653

for days now. All I get is

"Could not download update contents file from: rsync://updates.laptop.org/build-653/contents. I don't think you're connected to the internet."

I'm logged in as root (su -), I have a dev key, I can ping myself, my router, google, everybody as far as I can tell, *except* olpc-update!

Has a login step been left out? If the server is down pending changes to the build, please put a box to that effect somewhere, so we poor schmoes don't knock ourselves out trying to fix the unfixable.

Merge, re-organization, and page split

I 2nd, the proposal of a page merge with Stable Update (most of the information is already here).

Then, I also reccommend looking at this current page and split it out into three pages with completely seperate content focus.

1. Sugar update (General Public: How to go from current stable build to next stable build)
2. olpc-update (General Public: Command Reference: The command and various options, examples)
3. Sugar joyride (For Developers: Living on the edge differencs between Stable,Ship,Update, and joyride builds)

I think the page currently mixes these concepts together 1) General public will have difficulty understanding what is needed, 2) Developers don't need to know about stable 'simple' upgrades, 3) there's more details and background missing which developers might want to know about the 'joyride build' stream.

This re-organization might even blend into several other pages, which duplicate this page information (presented in different incomplete forms). And a simple link back to one of the 3 pages above would suffice.

If this sounds like a good plan, who would be willing to assist me with the re-org? :-)

Thoughts? --IainD 02:37, 9 January 2008 (EST)

---