[maemo-developers] QA Process for non user/* packages and how Application Manager handles upgrades

[From: Anderson Lizardo]

On Tue, Dec 1, 2009 at 11:55 AM, Mikko Vartiainen <mvartiainen at gmail.com> wrote:
> On Tue, Dec 1, 2009 at 5:39 PM, Anderson Lizardo
> <anderson.lizardo at openbossa.org> wrote:
>> The other solution is to fix Application Manager :o)
>
> IMO Application Manager is broken from community (Extras) perspective.
> From Nokia's perspective it's probably not broken because they can
> control that single meta package for SSU. How could we get that fixed?

I'm trying to get attention from community to problem by changing the
subject... Unfortunately they seem busy with other topics :/

IMHO, I can't understand why the HAM can't be used to upgrade single
packages (i.e. do a simple "apt-get upgrade"), and still support the
meta-packages for SSU. Is it possible to write some plugin to handle
upgrades of packages from extras repository in HAM?

Regarding the promotion of non user/* packages to extras-testing, I
really don't have other ideas besides creating a user/* metapackage
and push it to extras-testing (hoping the current QA process accepts a
meta-package that does nothing besides pulling new versions of
important packages to extras-testing together with it, and are not
supposed to be installed on the device). What developers and people
involved with the QA process feel about that?

Can some of the guys working on the QA process please shed some light
on that? The problem is becoming more critical, and people on #maemo
are saying some Python packages are broken or that Python is not
optified, while the fixes have already been put on extras-devel a long
time ago.

Thanks,
-- 
Anderson Lizardo
OpenBossa Labs - INdT
Manaus - Brazil