[maemo-developers] Autobuilder repository priority ?

From: Ed Bartosh bartosh at gmail.com
Date: Sun Nov 1 08:46:55 EET 2009
2009/11/1 Attila Csipa <maemo at csipa.in.rs>:
>> Are you sure it works this way? I thought that packages are built with
>> dependencies from unstable in Debian, just like they're built against
>> extras-devel in Maemo.
> You're right you can't change pinning on the *builder* within the *same*
> queue, that would make no sense. The problem is that the autobuilder already
> uses a mix of repositories (as you said later, having packages from extras-*
> overriding SDK stuff is not right) and that we can't skip the promotion process
> (i.e. no security.debian.org that is handled differently). If I was unclear as
> to the goal - I don't want to cross-reference repo contents (bad, bad idea). I
> want to be able to issue updates to packages that have been already promoted
> and got to the general public (obviously not typo fixes but stuff that is REALLY
> important), and for that, we need a queue that has a different repository
> layout (i.e. no extras-devel overriding extras).
So, you propose to have one more queue, which would use only SDK? Or
only Extras? or both? Sorry, your proposal is still unclear to me and
I doubt it would be clear for other devs.

>> Actually python-dbus is not very good example. It's not only SDK
>> package. I might be wrong but I think it's included into PyMaemo
>> releases and is delivered through Extras. Nokia included it into SDK,
>> but this is a special case.
> I just ran into this problem personally with python-dbus, hence the mention,
> but I did say the problem is more generic than that :)
I agree that the problem exists. Let's find possible solutions for it.
I still think that the one I proposed is the fastest and simplest for now.

More information about the maemo-developers mailing list