[maemo-developers] Autobuilder repository priority ?

From: Ed Bartosh bartosh at gmail.com
Date: Sat Oct 31 15:49:24 EET 2009
2009/10/31 Attila Csipa <maemo at csipa.in.rs>:
> I have a small issue with the autobuilder. The whole thing started out by
> having a package that compiled nice in the SDK but not in the autobuilder due
> to a versioning mismatch (in my case python-dbus, but it's a generic problem
> as you'll see). After some snooping around, I realized the problem was that
> the SDK had 0.83.0-1maemo1 in fremantle/tools/free (and that's what got used
> when compiling in the SDK), however, the autobuilder insists on using
> 0.83.0-1maemo3 from fremantle/free (-devel). The problem is IMHO that
> the repository priorities seem to be wrong. The autobuilder should be using
> the highest version in the TOP PRIORITY repository that satisfies a dependency
> to avoid breakage because of unstable stuff in -devel and because otherwise a
> package can't be promoted without dragging other folks' packages with them.
> Thoughts ?
The reason of this is that apt designed so that it will always install
higher possible version of package. It's actually rather good than
bad. Imagine what would happen if it would work another way. No new
python-dbus ever :)

The solution for this is to go to bugs.maemo.org and report your
problem to Pymaemo project and wait for a fix. Or, better, to provide
patch. You can also discuss this with pymaemo developers on their irc
channel or mailing list:

More information about the maemo-developers mailing list