[opensuse-packaging] cyclic repo dependencies (Gnome in first place)

older
[opensuse-packaging] Re: Fixing...

Adrian Schröter

19 Jun 2009 19 Jun '09

05:08

Hi please fix your repo dependencies, the scheduler needs to break them anyway, but we might even block the entire projects later, since this could create endless build loops. (btw these were fixed several times and come back again always it seems) From scheduler log (printed some several thousand times): cycle: GNOME:Backports/openSUSE_11.1 -> GNOME:Factory/openSUSE_11.1 breaking with GNOME:Backports/openSUSE_11.1 -> GNOME:Factory/openSUSE_11.1 cycle: home:pikerhog:gnome/standard -> home:pikerhog:utils/standard breaking with home:pikerhog:gnome/standard -> home:pikerhog:utils/standard cycle: home:pikerhog:gnome/openSUSE_11.1 -> home:pikerhog:utils/openSUSE_11.1 breaking with home:pikerhog:gnome/openSUSE_11.1 -> home:pikerhog:utils/openSUSE_11.1 event project::server:mail -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Show replies by date

Suman Manjunath

19 Jun 19 Jun

07:40

New subject: [opensuse-packaging] cyclic repo dependencies (Gnome in first place)

On Fri, Jun 19, 2009 at 10:38, Adrian Schröter wrote:

...

Hi

please fix your repo dependencies, the scheduler needs to break them anyway, but we might even block the entire projects later, since this could create endless build loops. (btw these were fixed several times and come back again always it seems)

From scheduler log (printed some several thousand times):

cycle: GNOME:Backports/openSUSE_11.1 -> GNOME:Factory/openSUSE_11.1 breaking with GNOME:Backports/openSUSE_11.1 -> GNOME:Factory/openSUSE_11.1

There should be no packages/repositories at all in GNOME:Backports. GNOME:Backports should only be a parent project for GNOME:Backports:x.yy Adrian / Magnus / Vuntz, could you please delete the packages and repositories from the GNOME:Backports main project? -Suman -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Adrian Schröter

07:47

Am Freitag, 19. Juni 2009 09:40:26 schrieb Suman Manjunath:

...

On Fri, Jun 19, 2009 at 10:38, Adrian Schröter wrote:

...
Hi

please fix your repo dependencies, the scheduler needs to break them anyway, but we might even block the entire projects later, since this could create endless build loops. (btw these were fixed several times and come back again always it seems)

From scheduler log (printed some several thousand times):

cycle: GNOME:Backports/openSUSE_11.1 -> GNOME:Factory/openSUSE_11.1 breaking with GNOME:Backports/openSUSE_11.1 -> GNOME:Factory/openSUSE_11.1

There should be no packages/repositories at all in GNOME:Backports. GNOME:Backports should only be a parent project for GNOME:Backports:x.yy

Adrian / Magnus / Vuntz, could you please delete the packages and repositories from the GNOME:Backports main project?

Okay, that is an easy one than :) Removing recursively these repositories now ... thanks adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Adrian Schröter

07:56

Am Freitag, 19. Juni 2009 09:47:32 schrieb Adrian Schröter:

...

Am Freitag, 19. Juni 2009 09:40:26 schrieb Suman Manjunath:

...
On Fri, Jun 19, 2009 at 10:38, Adrian Schröter wrote:

...
Hi

please fix your repo dependencies, the scheduler needs to break them anyway, but we might even block the entire projects later, since this could create endless build loops. (btw these were fixed several times and come back again always it seems)

From scheduler log (printed some several thousand times):

cycle: GNOME:Backports/openSUSE_11.1 -> GNOME:Factory/openSUSE_11.1 breaking with GNOME:Backports/openSUSE_11.1 -> GNOME:Factory/openSUSE_11.1

There should be no packages/repositories at all in GNOME:Backports. GNOME:Backports should only be a parent project for GNOME:Backports:x.yy

Adrian / Magnus / Vuntz, could you please delete the packages and repositories from the GNOME:Backports main project?

Okay, that is an easy one than :)

Removing recursively these repositories now ...

Ups, GNOME:Factory is building against this repo ... I suppose it should not do that ? Or should the 11.1 repo there removed as well ? bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Suman Manjunath

07:59

New subject: [opensuse-packaging] cyclic repo dependencies (Gnome in first place)

On Fri, Jun 19, 2009 at 13:26, Adrian Schröter wrote:

...

Am Freitag, 19. Juni 2009 09:47:32 schrieb Adrian Schröter:

...
Am Freitag, 19. Juni 2009 09:40:26 schrieb Suman Manjunath:

...
On Fri, Jun 19, 2009 at 10:38, Adrian Schröter wrote:

...
Hi

please fix your repo dependencies, the scheduler needs to break them anyway, but we might even block the entire projects later, since this could create endless build loops. (btw these were fixed several times and come back again always it seems)

From scheduler log (printed some several thousand times):

cycle: GNOME:Backports/openSUSE_11.1 -> GNOME:Factory/openSUSE_11.1 breaking with GNOME:Backports/openSUSE_11.1 -> GNOME:Factory/openSUSE_11.1

There should be no packages/repositories at all in GNOME:Backports. GNOME:Backports should only be a parent project for GNOME:Backports:x.yy

Adrian / Magnus / Vuntz, could you please delete the packages and repositories from the GNOME:Backports main project?

Okay, that is an easy one than :)

Removing recursively these repositories now ...

Ups, GNOME:Factory is building against this repo ...

I suppose it should not do that ?

No, it should not.

...

Or should the 11.1 repo there removed as well ?

IIRC, we had this repo to build the latest GNOME on the last released version of openSUSE. Since GNOME:Factory has 2.27.x now, the 11.1 repository should include GNOME:Backports:2.28 in its path (and not GNOME:Backports). I had permissions to GNOME Backports and I removed the cyclic dependency on GNOME Factory. I don't have permissions to change the GNOME Factory 11.1 repo path though. -Suman -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Adrian Schröter

08:11

Am Freitag, 19. Juni 2009 09:59:38 schrieb Suman Manjunath:

...

On Fri, Jun 19, 2009 at 13:26, Adrian Schröter wrote:

...
Am Freitag, 19. Juni 2009 09:47:32 schrieb Adrian Schröter:

...
Am Freitag, 19. Juni 2009 09:40:26 schrieb Suman Manjunath:

...
On Fri, Jun 19, 2009 at 10:38, Adrian Schröter wrote:

...
Hi

please fix your repo dependencies, the scheduler needs to break them anyway, but we might even block the entire projects later, since this could create endless build loops. (btw these were fixed several times and come back again always it seems)

From scheduler log (printed some several thousand times):

cycle: GNOME:Backports/openSUSE_11.1 -> GNOME:Factory/openSUSE_11.1 breaking with GNOME:Backports/openSUSE_11.1 -> GNOME:Factory/openSUSE_11.1

There should be no packages/repositories at all in GNOME:Backports. GNOME:Backports should only be a parent project for GNOME:Backports:x.yy

Adrian / Magnus / Vuntz, could you please delete the packages and repositories from the GNOME:Backports main project?

Okay, that is an easy one than :)

Removing recursively these repositories now ...

Ups, GNOME:Factory is building against this repo ...

I suppose it should not do that ?

No, it should not.

...
Or should the 11.1 repo there removed as well ?

IIRC, we had this repo to build the latest GNOME on the last released version of openSUSE. Since GNOME:Factory has 2.27.x now, the 11.1 repository should include GNOME:Backports:2.28 in its path (and not GNOME:Backports).

I had permissions to GNOME Backports and I removed the cyclic dependency on GNOME Factory. I don't have permissions to change the GNOME Factory 11.1 repo path though.

Okay, I did so with admin rights now. thanks ! adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Vincent Untz

13:54

New subject: [opensuse-packaging] cyclic repo dependencies (Gnome in first place)

Le vendredi 19 juin 2009, à 09:47 +0200, Adrian Schröter a écrit :

...

Am Freitag, 19. Juni 2009 09:40:26 schrieb Suman Manjunath:

...
On Fri, Jun 19, 2009 at 10:38, Adrian Schröter wrote:

...
Hi

please fix your repo dependencies, the scheduler needs to break them anyway, but we might even block the entire projects later, since this could create endless build loops. (btw these were fixed several times and come back again always it seems)

From scheduler log (printed some several thousand times):

cycle: GNOME:Backports/openSUSE_11.1 -> GNOME:Factory/openSUSE_11.1 breaking with GNOME:Backports/openSUSE_11.1 -> GNOME:Factory/openSUSE_11.1

There should be no packages/repositories at all in GNOME:Backports. GNOME:Backports should only be a parent project for GNOME:Backports:x.yy

Adrian / Magnus / Vuntz, could you please delete the packages and repositories from the GNOME:Backports main project?

Okay, that is an easy one than :)

Removing recursively these repositories now ...

This was wrong, and now GNOME:Factory is broken for 11.1... Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Magnus Boman

23:38

On Fri, 2009-06-19 at 09:47 +0200, Adrian Schröter wrote:

...

Am Freitag, 19. Juni 2009 09:40:26 schrieb Suman Manjunath:

...
On Fri, Jun 19, 2009 at 10:38, Adrian Schröter wrote:

...
Hi

please fix your repo dependencies, the scheduler needs to break them anyway, but we might even block the entire projects later, since this could create endless build loops. (btw these were fixed several times and come back again always it seems)

From scheduler log (printed some several thousand times):

cycle: GNOME:Backports/openSUSE_11.1 -> GNOME:Factory/openSUSE_11.1 breaking with GNOME:Backports/openSUSE_11.1 -> GNOME:Factory/openSUSE_11.1

There should be no packages/repositories at all in GNOME:Backports. GNOME:Backports should only be a parent project for GNOME:Backports:x.yy

Adrian / Magnus / Vuntz, could you please delete the packages and repositories from the GNOME:Backports main project?

Okay, that is an easy one than :)

Removing recursively these repositories now ...

In the future, I think it'd be a good idea to wait for the repo maintainers to speak up before starting to delete packages. Even better would be to never delete packages but just disable the repo and let us know why. Cheers, Magnus -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Vincent Untz

13:56

New subject: [opensuse-packaging] cyclic repo dependencies (Gnome in first place)

Le vendredi 19 juin 2009, à 07:08 +0200, Adrian Schröter a écrit :

...

Hi

please fix your repo dependencies, the scheduler needs to break them anyway, but we might even block the entire projects later, since this could create endless build loops. (btw these were fixed several times and come back again always it seems)

From scheduler log (printed some several thousand times):

cycle: GNOME:Backports/openSUSE_11.1 -> GNOME:Factory/openSUSE_11.1 breaking with GNOME:Backports/openSUSE_11.1 -> GNOME:Factory/openSUSE_11.1

Here's the issue: GNOME:Factory/openSUSE_11.1 needs some stuff to be backported (since openSUSE:11.1 doesn't have everything it needs) to build. However, some of the stuff in GNOME:Backports/openSUSE_11.1 also needs packages that exist in GNOME:Factory/openSUSE_11.1 to build. Sure, we could let it build against openSUSE:11.1 and assume it will work fine, but we want to go the safe way. So what would be a good way to organize this? Vncent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Dirk Müller

17:14

On Friday 19 June 2009, Vincent Untz wrote:

...

Here's the issue: GNOME:Factory/openSUSE_11.1 needs some stuff to be backported (since openSUSE:11.1 doesn't have everything it needs) to build. However, some of the stuff in GNOME:Backports/openSUSE_11.1 also needs packages that exist in GNOME:Factory/openSUSE_11.1 to build.

Sure, we could let it build against openSUSE:11.1 and assume it will work fine, but we want to go the safe way.

So what would be a good way to organize this?

how about splitting the stuff in GNOME:Backports that needs stuff in GNOME:Factory to build into something else, like GNOME:Platform or something like that? alternatively _aggregate those packages that you need to break the build cycle. thats not as nice, but fixes it as well. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Vincent Untz

17:19

New subject: [opensuse-packaging] cyclic repo dependencies (Gnome in first place)

Le vendredi 19 juin 2009, à 19:14 +0200, Dirk Müller a écrit :

...

On Friday 19 June 2009, Vincent Untz wrote:

...
Here's the issue: GNOME:Factory/openSUSE_11.1 needs some stuff to be backported (since openSUSE:11.1 doesn't have everything it needs) to build. However, some of the stuff in GNOME:Backports/openSUSE_11.1 also needs packages that exist in GNOME:Factory/openSUSE_11.1 to build.

Sure, we could let it build against openSUSE:11.1 and assume it will work fine, but we want to go the safe way.

So what would be a good way to organize this?

how about splitting the stuff in GNOME:Backports that needs stuff in GNOME:Factory to build into something else, like GNOME:Platform or something like that?

Sorry, I wasn't clear and this wouldn't help. Here's an example: ConsoleKit (G:B) needs glib2 (G:F). gnome-session (G:F) needs ConsoleKit (G:B). Whatever we do, there'll be a package that needs G:F and is needed by G:F. Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Dirk Müller

17:54

On Friday 19 June 2009, Vincent Untz wrote:

...

Sorry, I wasn't clear and this wouldn't help. Here's an example:

ConsoleKit (G:B) needs glib2 (G:F). gnome-session (G:F) needs ConsoleKit (G:B).

Whatever we do, there'll be a package that needs G:F and is needed by G:F.

this is only a problem for openSUSE 11.x (with other words non-Factory users),correct? depending on gnome-session in G:F needs the latest ConsoleKit to work /compile at all: needs latest ConsoleKit: G:F: ConsoleKit gnome-session G:B glib2 does not need latest ConsoleKit: not forcing the latest (possibly unstable or completely nonworking version for older distros) ConsoleKit onto users is preferred, so: X11:common:Factory ConsoleKit G:B glib2 G:F gnome-session (build against G:B for old dists and X11:common:Factory for factory). if you would use X11:common:Factory more for such packages that are shared by GNOME+KDE would definitely help the KDE team. we frequently get complains from users that try to use GNOME:Factory and KDE:KDE4:Factory:Desktop that we rely on two different versions of common packages, which breaks one or the other desktop in horrible ways. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Vincent Untz

23:16

New subject: [opensuse-packaging] cyclic repo dependencies (Gnome in first place)

Hi, Le vendredi 19 juin 2009, à 19:54 +0200, Dirk Müller a écrit :

...

On Friday 19 June 2009, Vincent Untz wrote:

...
Sorry, I wasn't clear and this wouldn't help. Here's an example:

ConsoleKit (G:B) needs glib2 (G:F). gnome-session (G:F) needs ConsoleKit (G:B).

Whatever we do, there'll be a package that needs G:F and is needed by G:F.

this is only a problem for openSUSE 11.x (with other words non-Factory users),correct?

depending on gnome-session in G:F needs the latest ConsoleKit to work /compile at all:

needs latest ConsoleKit:

G:F: ConsoleKit gnome-session

G:B glib2

does not need latest ConsoleKit:

not forcing the latest (possibly unstable or completely nonworking version for older distros) ConsoleKit onto users is preferred, so:

X11:common:Factory ConsoleKit

G:B glib2

G:F gnome-session (build against G:B for old dists and X11:common:Factory for factory).

I'm sorry, I don't understand your approach: + for 11.1 users of G:F, we don't need the latest ConsoleKit. We need the ConsoleKit of 11.1 with a small additional patch. We don't want the latest one. + glib2 is in G:F, so why would it be in G:B?

...

if you would use X11:common:Factory more for such packages that are shared by GNOME+KDE would definitely help the KDE team. we frequently get complains from users that try to use GNOME:Factory and KDE:KDE4:Factory:Desktop that we rely on two different versions of common packages, which breaks one or the other desktop in horrible ways.

Sure, it makes sense to move ConsoleKit and other fd.o packages to X11:common:Factory. I was considering the option today; just didn't have time to investigate things completely. But it's on my list of things to do for making G:F a bit smaller. (fwiw, the only reason ConsoleKit ended up in G:F is because it was marked as maintained by gnome-maintainers in PDB, and when we start using the build service, we moved all such packages to G:F) Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Suman Manjunath

17:17

New subject: [opensuse-packaging] cyclic repo dependencies (Gnome in first place)

On Fri, Jun 19, 2009 at 19:26, Vincent Untz wrote:

...

Le vendredi 19 juin 2009, à 07:08 +0200, Adrian Schröter a écrit :

...
Hi

please fix your repo dependencies, the scheduler needs to break them anyway, but we might even block the entire projects later, since this could create endless build loops. (btw these were fixed several times and come back again always it seems)

From scheduler log (printed some several thousand times):

cycle: GNOME:Backports/openSUSE_11.1 -> GNOME:Factory/openSUSE_11.1 breaking with GNOME:Backports/openSUSE_11.1 -> GNOME:Factory/openSUSE_11.1

Here's the issue: GNOME:Factory/openSUSE_11.1 needs some stuff to be backported (since openSUSE:11.1 doesn't have everything it needs) to build.

Right. Like I mentioned earlier, since G:F is now building 2.27.x, it may have GNOME:Backports:2.28 in its path.

...

However, some of the stuff in GNOME:Backports/openSUSE_11.1 also needs packages that exist in GNOME:Factory/openSUSE_11.1 to build.

There are about 6 packages in GNOME:Backports:2.26. They have 11.1 + updates only in their path. So how does the dependency on G:F come in? (all this will apply to GNOME:Backports:2.28 as well) So, could you please explain what can't be fixed without having packages in the GNOME:Backports main project? -Suman -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

5424

Age (days ago)

5424

Last active (days ago)

List overview

Download

13 comments

5 participants

participants (5)

Adrian Schröter
Dirk Müller
Magnus Boman
Suman Manjunath
Vincent Untz

[opensuse-packaging] cyclic repo dependencies (Gnome in first place)

tags

participants (5)