> Well, it *used* to work like that some time ago, but in the last weeks
> I've noticed that no newer versions of PyMaemo packages (which are all
> dependencies from various user/* application) got promoted as before.

Packages don't get updated in promotion process if earlier version satisfies 
dependency. Many packages have direct dependency only for "python" package, 
which hasn't been updated lately, not for "python2.5" which is the actual 
optified version. "python2.5" isn't probably promoted because no package hasn't 
had dependency "python2.5 (>=2.5.2-3maemo3). If packagers like to keep their 
"Depends" line clean they are unlikely to put python2.5 directly there.

-- 
Mikko Vartiainen
_______________________________________________
maemo-developers mailing list
[email protected]
https://lists.maemo.org/mailman/listinfo/maemo-developers

Reply via email to