[maemo-developers] Autobuilder repository priority ?

[From: Attila Csipa]

Foreword: My particular problem is not that big of an issue, in the end I went 
for extras-devel compatibility, no big deal, it's not yet for end users 
anyway. It's the generic approach that is at question here - tomorrow someone 
else will fall through the same manhole and it might become a recurring issue.

On Tuesday 03 November 2009 18:58:04 Anderson Lizardo wrote:
> Did you mean "-1maemo1" instead of "-1maemo0"? (there is no maemo0 IIRC)

Yes, indeed, -1maemo1. To add to the confusion there *IS* a python2.5-0maemo0 
in *extras-testing* (see http://maemo.org/packages/view/python2.5-dbus/ )

> Can you be more specific? Which paths are those? How does this affect
> your package?

Okay, I backtracked my steps as far as I could, and it *seems* the actual 
source of the problem is python-support (which I pull in through python-dbus). 
1maemo1 (from the SDK) pulls in python-support 0.6.4 (from the SDK). 1maemo3, 
on the other hand, pulls in python-support 1.0.2maemo1 (from extras-devel). 
Depending on which python-support module got pulled in, the paths for the dbus 
module change:

The sdk version's
/var/lib/python-support/python2.5/dbus

in extras-devel becomes
/usr/lib/pymodules/python2.5/dbus

This affects my package as I have a .install  file that looks like this 
(inherited from upstream):

debian/python2.5-qt4-dbus.install:
var/lib/python-support/python2.5/dbus

And since the paths change, the .so will go (or rather won't go, as the 
autobuilder bombs) to the wrong path. Yes, I know, I can introduce a 
downstream patchset and start depending on python-support myself, but that is 
not the point here. :)

> Why can't you promote the package using -1maemo3?

See the path problem above.