[maemo-developers] Community updates for diablo

[From: Lucas Maneos]

On Mon, Mar 01, 2010 at 05:34:52PM +0100, Jeremiah Foster wrote:
> So what is the next step Lucas? Do we want to put something into the
> community repo to test if it works - then put in the updates on the
> Maemo.org servers running reprepro?

Hi,

we've been running tests off a private repository for the past 6 weeks
or so.  It's a relatively small sample (approximately 25 volunteer
testers), but no bricked devices so far so I think it's time to move it
to a public repository and hopefully get some more people building
packages.

You can just grab source and/or binary packages from the private
repository, but let me know if you've lost the URL or need anything
else.

There are a couple of changes needed in the community-ssu-enabler
package, namely to update it with the "official" repo keys & key
fingerprints.  It's probably a good idea to bump the trust level up a
bit so that early testers can roll over to the new repository without
hassle.  All of the above is in post-install script.

BTW, can we have a -testing repo as well?

On Mon, Mar 01, 2010 at 09:26:30AM +0200, Marius Vollmer wrote:
> If anything else comes up, don't hesitate to ask, of course.

There is one thing actually: how can I get the application manager to
forget a previously set trust-level?

I'm doing something along the lines of:

# dpkg --purge community-ssu-enabler
# apt-get install osso-software-version-rx34=1:5.2008.43-7 (+ all
  dependencies it complains about)
# /usr/bin/flash-and-reboot

The prerm script in the first step removes both the domain and key
(verified with "hildon-application-manager-config dump" & "apt-key
list"), but the application manager still offers to upgrade after that.

It would be nice to have a way of reverting back to the vanilla Diablo
state (eg for testing or as a fallback in case things go wrong), so if
I've missed something obvious any pointers welcome.

Thanks,
Lucas