[maemo-developers] Community updates for diablo (specifically Application Manager if nothing else)

[From: Marius Vollmer]

ext Lucas Maneos <maemo at subs.maneos.org> writes:

> The story so far:
>  - mined a bunch of patches from bugs.maemo.org
>  - built some updated packages with the above
>  - got Nokia's blessing to modify and redistribute osso-software-version-*
>  - set up a test repository.

Great!

> The missing piece: making the updates installable via application
> manager so we can invite some brave souls for testing.
>
> The problem (as I understand it) is packages switching domains.  The
> updated versions come from a repository signed with a different key to
> the "nokia-system" one, which makes the application manager ignore them.
>
> Based on <http://hildon-app-mgr.garage.maemo.org/repos-stable.html>:
>
>> Domains have a 'trust level' associated with them. Domains with a
>> higher trust level are considered to dominate other domains and the AM
>> will allow a package to silently move from a domain to a dominating
>> one.
>
> I had assumed that setting a higher trust-level would allow domain
> switches to happen, but this doesn't seem to be the case :-(

It should work like you expect it to.

> For clarity, I'm testing on a freshly-reflashed 5.2008.43-7 N800 with
> the following added to /etc/hildon-application-manager/domains:
>
>  <domain>
>   <name>community-updates</name>
>   <trust-level>600</trust-level>
>   <key>[...]</key>
>   <default/>
>  </domain>
>
> and "<default/>" removed from nokia-system.

This looks correct.  I suspect that the Application manager just doesn't
recognize your repository as belonging to this domain.

You also need to install the matching public key.  What does 

    # apt-key list 

output?

I can try to find a Diablo device to debug this a bit.  It is a bit icky
to get all the configurations just right, but once you do, things just
start working silently.

> Every workaround I can come up with is unworkable at best, the only
> semi-viable one being to patch the application manager but this has the
> obvious chicken-and-egg problem of how to publish the patched version so
> users can install it.

You can tell people to install it in red-pill mode (or on the command
line).  In red-pill mode, the domain check can be overruled by the user.

> I may be missing something obvious, so any ideas welcome.

It might just be the missing public key.  Without it, the signature on
your repo will not be recognized as valid, and it will be associated
with the "unsigned" domain.