[maemo-developers] Fremantle Community SSU

From: Timo Härkönen timop.harkonen at gmail.com
Date: Tue Nov 2 08:10:06 EET 2010
Hi

2010/11/1 Mohammad Abu-Garbeyyeh <mohammad7410 at gmail.com>

> Hello everyone :)
>
> Some of you may have heard back in summer when I announced that I was
> working on an SSU, however, I decided to postpone it till PR1.3's out.
> Now that it's out, I decided to work on it again. Niels Breet (X-Fade) has
> kindly set up the repository on
> http://repository.maemo.org/community-testing/.
>
> Me and X-Fade have come to a conclusion that instead of faking the Nokia
> meta-package, it would be better to make a new community one
> (mp-fremantle-community-pr).
> Unfortunately, while this might be the right way, it caused me some
> problems with the enabler package, so to work around it, a terminal window
> is started from HAM (postinst) and then the postinst exits, the user then
> has to exit HAM and go back to the terminal window to continue installation.
>
> I've yet to make a complete changelog for this repository, however, I can
> confirm that https://bugs.maemo.org/show_bug.cgi?id=10613 is no longer
> reproducible with the new hildon-desktop in the repository, so that's a
> start ;)
> New system packages, all of them are based on the latest gitorious sources.
> hildon-desktop (with Matan's patches) | hildon-home |
> hildon-application-manager | hildon-status-menu | modest (with patches for
> bmo bugs #3700 and #2563)
>
> As per above, community patches are welcome for any of the system packages.
>
>
Thanks for the effort.

To enable the repository, open
> http://repository.maemo.org/community-testing/community-testing-fremantle.installon the N900.
>
> This is not a proper announcement for the SSU, but more of a prerelease
> before it's posted on talk.maemo.org, so please, do not post about this on
> talk.
>
>
>
I'd appreciate any testing, suggestions and bug reports about this SSU,
> before I make a proper announcement about it.
>

Are you also packaging the corresponding -tests packages [1] for the
libraries? I could give them a spin to see if they pass, etc. For the
community updates to be credible I think we should have some testing going
on for the provided updates.

After MeeGo's open test system [2] is stable enough it could be used to
automate testing (if the -tests packages and needed hardware [3] are
available). At least I don't see any reason why it wouldn't work with Maemo.

The tests can be also executed on device without the automation stuff.
Basically you need to install testrunner-lite (available from extras-devel)
and some test packages. then you do for example: 'testrunner-lite -f
/usr/share/testrunnner-lite-tests/tests.xml -v -o /home/user/results.xml'

[1] http://wiki.meego.com/Quality/QA-tools/Test_packaging
[2] http://wiki.meego.com/Quality/QA-tools/OTS
[3] n900, a PC to control testing, some software controlled device to toggle
usb and power



> I'd also like to thanks Niels and Lucas Maneos (the Diablo community SSU
> maintainer) for their help in setting this up.
>
> P.S. #maemo-ssu is the SSU's channel on Freenode.
>
>
Joined. I'm known as timoph there


--Timo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.maemo.org/pipermail/maemo-developers/attachments/20101102/f57086f1/attachment.htm>
More information about the maemo-developers mailing list