[maemo-developers] QA Process for non user/* packages and how Application Manager handles upgrades (was: Re: extras-devel -> extras-testing auto-promotion not working?)

[From: Tim Teulings]

Hello!

> That's what is happening at the moment with python-osso.

[...] 
> So unless someone promotes a user/* package to extras-testing that has
> "Depends: python-osso (>= 0.4.0-0maemo2)" , python-osso will remain
> broken on extras & extras-testing.

That also happend for me recently with libIllumination even in
extras-devel! A bugfix does not get installed by the device.

Is this the same effect? If yes, thrilling is that I have a n:1
constellation where multiple application depend on the same library, where
the applications do not have any dependencies on each other. So I must
increase the version and force a rebuild with a higher dependency for *all*
application packages? If I miss one, funny things will likely happend, with
some people having the new version and some the old. The effect occured
recently. I assume because before libIllumination had a user/* category
(which was identified as bug).

That all sound very broken... Imaging this happening for the community
based hildon add-on controls library, which is likely widly spread in
future.

-- 
Gruß...
    Tim