[maemo-developers] Autobuilder repository priority ?
From: Anderson Lizardo anderson.lizardo at openbossa.orgDate: Wed Nov 4 14:51:00 EET 2009
- Previous message: Autobuilder repository priority ?
- Next message: Promoting packages not under user/* sections, e.g. libraries (was: Re: Autobuilder repository priority ?)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Nov 3, 2009 at 4:31 PM, Attila Csipa <maemo at csipa.in.rs> wrote: > On Tuesday 03 November 2009 18:58:04 Anderson Lizardo wrote: >> 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: > [...] This path has changed due to the new python-support 1.0.2 version. They decided to change this path for some reason. Unfortunately, we can't keep compatibility in this case, as it was an upstream change. Ideally, your package should not depend on that path being the same forever. In my opinion, the best way to handle it is to have your package Build-Depend on python-support (>= 1.0.2maemo1), given that you rely on this private path (which BTW comes from "installedpath" variable in /usr/share/python-support/private/movemodules). > 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. :) I can see that it is not the main point of the discussion (I myself had problems with some broken libraries being uploaded to extras-devel that "shadowed" working ones from the SDK), but keep in mind that in case of any python* packages in the SDK, it is legitimate for the PyMaemo team to upload up-to-date versions to the extras* repositories, and you should not rely on any Python packages that come from the SDK tools repository when doing Python development on Maemo, as they are outdated and they are there just for satisfying dependencies of some SDK tools. Regards, -- Anderson Lizardo OpenBossa Labs - INdT Manaus - Brazil
- Previous message: Autobuilder repository priority ?
- Next message: Promoting packages not under user/* sections, e.g. libraries (was: Re: Autobuilder repository priority ?)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]