Re: 'Fixed in Fremantle' and Diablo community SSU
 

What version number would we use? My perspective was: Nokia created Diablo, Nokia maintained Diablo, and now Nokia has turned Diablo maintenance over to the community (with some closed-source handcuffs). So I personally would be comfortable with talking about a new Diablo version. For everyone who has it hardwired into their heads that Maemo = Nokia, this could be confusing. But the confusion could be greatly helped by just appending to the version number something like CE for community edition (I like that better than HE). So I like incrementing the Diablo version number and adding something like CE.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I'm game. :)

Sent you a PM Ima.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Certainly, I fully agree. I guess I wasn't very clear... What I was trying to say was that taking over the "Maemo Official" Products in BugZilla necessarily means using a bumped version at that time, and that confusion could ensue if uninformed speculation came out of that before the Community SSU was more officially announced. Think of what would be happening right now if Nokia had officially ditched Fremantle, and then a new version number was mentioned somewhere with no prior clarification. That was all I was saying - a matter of timing, not saying it was a bad idea.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

The confusion with the word "Official" could perhaps be avoided by renaming the classifications, but another problem is the QA contacts (which are shared with Fremantle so we can't change them and we don't want to spam Nokia with "our" bugs either).

So, after some consideration I'm leaning towards the separate product option. I propose we create a "community-something" product under Extras, with some pre-defined components based on what patches are currently available, plus a "general" or "other" in case something fresh comes along.

Workflow-wise, should we re-assign the existing bugs to Extras/Community/whatever or clone them?

To be honest, I don't see this as a very long term activity. There are only a finite number of contributed patches we can package after all, and I remain hopeful that Mer^2 and/or Meego will provide a more viable distribution for the OMAP2 devices in the long run.

You mean something other than bugs.maemo.org? I'd like to avoid that if possible for various reasons (the bugs, discussions and patches are already on bmo, users shouldn't have to create yet another account to file bugs etc).

At the moment I'm using the pre-existing versionsing scheme, simply because I didn't want to think too much about it (the testing SSU is '5.2010-09-2" for example, or perhaps it should start with 6?) but it's not cast in stone, ideas welcome. Keep in mind that for all intents and purposes it is a slightly patched Diablo so a radical departure like calling it Elephanta or something would seem misleading/inappropriate.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

So I installed the Community SSU Enabler (from the link lma sent me), and it installed cleanly with no fuss into my highly modded multi-boot SD partition.

What do I do now? It isn't clear.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

The application manager should offer the update after a manual refresh (needed so that it will see the packages with the new priority defined by the enabler package). If it doesn't please clear the log, refresh again and post the contents of the log here (or PM me if you prefer).

I had one report where an SD-booted N800 didn't see the update, but the problem turned out to be that the catalogue.tableteer.nokia.com repositories were configured twice and removing the duplicate repositories fixed it. Not sure why that would happen (both copies had the default 500 priority) or if there's anything that can be done about it.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Your reasoning makes sense.
Okay, I guess I had some misconceptions, then. In that case, you can disregard most of what I said. :P

See my previous bit... I was under the assumption that this was longer-term, and that there would be further testing before it was "released" in a larger sense. I thus was just thinking that practically anything would be a better medium for it than a forum. Disregard that too.

Sorry for the confusion.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

OK, I figured out my problem. My hacked rotation-enabled (+ fast SD I/O) kernel and xserver-omap are blocking any version of osso-software-version-rx34 from being installed.

Don't suppose you could include those hacks in your version? I do like my rotation...

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Yep. I have the same rotation kernel thingie as qole.

Just go ahead and flash a clean Diablo for this?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

You could uninstall (sob! :( ) the beautiful hacked kernel and xserver-omap packages, then install this SSU that will fix the PDF reader. :(

You could then turn around and re-install the hacked kernel, of course.