On Tue, Dec 1, 2009 at 9:18 AM, Mikko Vartiainen <[email protected]> wrote: >> 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.
So what should we do here to have newer version of dependencies promoted ? Obviously, we will not recommend depending on python2.5 directly (that was the whole idea of the "python" meta package). Also depending on a specific version just to force promotion seems odd IMHO. Should I proceed and promote the missing PyMaemo packages to extras-testing ? IMHO ideally, the auto promotion should be aware of newer versions of dependencies, otherwise how are we (the maintainers) supposed to provide bugfixes ? (.e.g the new optified packages). Thanks in advance, -- Anderson Lizardo OpenBossa Labs - INdT Manaus - Brazil _______________________________________________ maemo-developers mailing list [email protected] https://lists.maemo.org/mailman/listinfo/maemo-developers
