Diablo update strategy
 

I understand that the upgrade to Diablo leaves a set of catalogue definitions in the Application Manager. Those definitions do not include all of the applications that were previously available on Chinook. Can I just examine a few strategies to consider?

Strict: Leave the catalogues untouched. They define the set of applications that are officially ported to Diablo. Over time, hopefully days and weeks, rather than months, all of most common applications (e.g. mplayer) will appear in the catalogues at which point one can be sure they are supported.

Cautious: Change the catalogues, or create new ones that include those applications previously released under Chinook. There is some risk here in that they might not work, but little risk that they would trash the device or interfere detrimentaly with Diablo applications. This could be a short term strategy until the equivalent Diablo version appears.

Expert: Make what ever changes you like and accept the consequences.

If I was to adopt the Strict strategy, how can I find out the roadmap for Diablo ports. Is there any web-page where I can see a schedule? Or do I just keep hitting refresh every day and hope they turn up?

Re: Diablo update strategy
 

My understanding is the extras recompilation should be on the order of weeks, not months ( presuming there is a package maintainer ).

Re: Diablo update strategy
 

It's all down to the packagers at this point. Feel free to go out and prod the maintainers of your favorite applications to get their stuff properly compiled through the autobuilder. ;)

Re: Diablo update strategy
 

I followed your 'Cautious' strategy. After installing the applications, I disabled the Chinook Extras repository. In the following days a lot of applications started to update to the same installed version. I think this was at the moment the application was officially ported to Diablo. If this is correct, I think in a couple of weeks most of the applications will be in Diablo.

By the way, Mplayer is one of those applications recently updated, so I think it is in Diablo Extras repository right now.

I could be totally wrong, though.

Re: Diablo update strategy
 

Extras is not an official repository, and the applications in there are not official Nokia projects.

I repeat, Extras is not an official Nokia repository, and is neither blessed nor guaranteed by Nokia in any way.

maemo.org Extras is the maemo.org community repository. The applications hosted in Extras are purely community projects (although some are packaged and maintained by Nokia employees, they are not Nokia projects).

Just so we're clear. ;)

Re: Diablo update strategy
 

Thanks for that. It's not always clear to the newcomer :o

Re: Diablo update strategy
 

Some more repos most AVERAGE users would like to have, http://www.internettablettalk.com/fo...ad.php?t=21469. Again, add repos first then install progs is a safe way to avoid dependcy problems.


bun

Re: Diablo update strategy
 

Ok. Remove the 'officially' word from my post. The remaining text is what I see happening. Am I right or not?

Re: Diablo update strategy
 

I just recently acquired an N810, and had also learned of the Diablo upgrade.

Checking the software that came with the unit (purchased off of eBay), I noticed that it is 2 versions behind Diablo. I haven't installed literally ANYTHING, nor setup email or even changed bookmarks.

Question:
Should I upgrade straight to Diablo? Or upgrade to the version just prior?

thanks,

=-= Hoot :D

Re: Diablo update strategy
 

I may not be the best one to tell you, as I'm still on OS2007.. but as I'm following things (in order to decide the right moment to upgrade) I would definitely go for the latest (Diablo) and not the previous version of OS2008. Anyway, that's what I would do.. :D

Re: Diablo update strategy
 

confusion of repos, is there any list of applications that work well on diablo somewhere? insteat of refreashing all the time to see if there is some updates available, i really wish i could go back to chinook and wait after summer before upgrading.
some of my application do not lunch even though they are safely installed.

Re: Diablo update strategy
 

Mind to share with us which application does not lunch? Maybe the forum can help.


bun

Re: Diablo update strategy
 

This is why I have been recommending to newbies that they clone their system to Deb before flashing.

Re: Diablo update strategy
 

thanks
erming is the most needed as i use g cal and gpe cal, even though i have recieved two undates since it will not lanch, unistalled reinstalled done all but it will not move when i launch it,

sorry i am not a linux expert clonning to me is like build windows xp from start, the third reason i bought this device is to learn to use linux.

Re: Diablo update strategy
 

I'd definitely go with Diablo.

Re: Diablo update strategy
 

Whom would I prod to encourage mplayer to be diabolized?;)

Re: Diablo update strategy
 

https://garage.maemo.org/projects/mplayer/

One of the people there. Though I believe Ed's on vacation.

Re: Diablo update strategy
 

after a backup and a reflash my tablet is in good working state after a restore, updates are coming step by step and making the tablet more stable no issues with the apps. thanks to those working on the devil to subdue it to good working order.

Re: Diablo update strategy
 

Ok. I've prodded him. I think it only fair that he rushes back from the beach :D

Re: Diablo update strategy
 

First, I've not found this anywhere, but you need to add the diablo tools and sdk repositories manually. Probably extras and extras-dev (for diablo). Many chinook repositories will be restored.

For the diablo tools/sdk, I just posted:

http://www.internettablettalk.com/fo...85&postcount=7

My method:

0. Backup using the normal utility which you should do anyway.

1. Use penguinbait's Clone-to-SD to copy a full (mountable) image of your current setup. I have many tweaks (like WM, startup media) that aren't backed up but I could retreive them - mainly by checking the change date. (I also use a manual rsync/gnutar to mirror to my repartitioned internal flash, but that is more effort and something I do as an extra backup)

(1a - get a chinook flash file if you want a full restore just in case)

2. Reflash to diablo. This will remove the bootability for the initfs, but you won't need it for the restore.

3. Do all the normal restores. Remove any extra media you don't want (pics, sounds, videos). This includes application manager once normally, then after you've added diablo extras and extras-devel, and the above mentioned sdk and tools.

4. If anything is missing, you can mount the SD card and look for anything that didn't get updated and manually copy it back or integrate it.

Re: Diablo update strategy
 

Woohoo! mplayer has just turned up on Diablo. Nice one :)