[Bug 962599] New: erlang: build cycle in openSUSE:Factory
http://bugzilla.opensuse.org/show_bug.cgi?id=962599 Bug ID: 962599 Summary: erlang: build cycle in openSUSE:Factory Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: dimstar@opensuse.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- https://build.opensuse.org/project/repository_state/openSUSE:Factory/standar... currently lists a build cycle between: erlang-rebar, erlang-retest Please work on eliminating this issue - also take into account that currently erlang-rebar does not build at all in openSUSE:Factory -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=962599
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=962599
Nico Kruber
http://bugzilla.opensuse.org/show_bug.cgi?id=962599
http://bugzilla.opensuse.org/show_bug.cgi?id=962599#c1
Matwey Kornilov
http://bugzilla.opensuse.org/show_bug.cgi?id=962599
http://bugzilla.opensuse.org/show_bug.cgi?id=962599#c2
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=962599
http://bugzilla.opensuse.org/show_bug.cgi?id=962599#c3
--- Comment #3 from Matwey Kornilov
http://bugzilla.opensuse.org/show_bug.cgi?id=962599
http://bugzilla.opensuse.org/show_bug.cgi?id=962599#c4
--- Comment #4 from Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=962599
http://bugzilla.opensuse.org/show_bug.cgi?id=962599#c5
--- Comment #5 from Matwey Kornilov
http://bugzilla.opensuse.org/show_bug.cgi?id=962599
http://bugzilla.opensuse.org/show_bug.cgi?id=962599#c6
--- Comment #6 from Dominique Leuenberger
We don't lose anything except somebody will send erlang-rebar again eventually, because it is the most popular build system for erlang.
So, is "Prefer: erlang-rebar-obs" acceptable solution? If so, there are not so many thing to redo.
erlang-rebar-obs will provide erlang-rebar, and Prefer will force conflict resolution.
Prefer: is the way it's done in all other cases - and the resulting -mini (or -obs in your case) is not installable by zypper due to the missing dep 'this-is-only-for-buildsystem'. But IIRC a Provides: erlang-rebar won't work, as OBS will automatically already prefer the actual package with that name over a virtual provides. As far as I see, the difference between erlang-rebar-obs and erlang-rebar is actually no BUILD difference, but wether the test suite is executed or not? Then I'd argue the entire setup is overcomplicated. I'd suggest to think about a solution like (similar to gcc): erlang-rebar with a 2nd spec file erlang-rebar-testsuite (preferably not rebuilding the whole thing, but reusing what was there in first place) then, erlang-retest can properly depend on erlang-rebar, and erlang-rebar-testsuite can depend on erlang-rebar (for whatever built stuff it wants to test) and erlang-retest. That should give a clean dependency tree and if we're lucky, even not require to do two builds of the same source (currently, erlang-rerbar and erlang-rebar-obs both build the same sources. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=962599
http://bugzilla.opensuse.org/show_bug.cgi?id=962599#c7
--- Comment #7 from Matwey Kornilov
http://bugzilla.opensuse.org/show_bug.cgi?id=962599
http://bugzilla.opensuse.org/show_bug.cgi?id=962599#c8
--- Comment #8 from Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=962599
http://bugzilla.opensuse.org/show_bug.cgi?id=962599#c9
--- Comment #9 from Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=962599
http://bugzilla.opensuse.org/show_bug.cgi?id=962599#c10
--- Comment #10 from Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=962599
http://bugzilla.opensuse.org/show_bug.cgi?id=962599#c11
--- Comment #11 from Matwey Kornilov
http://bugzilla.opensuse.org/show_bug.cgi?id=962599
http://bugzilla.opensuse.org/show_bug.cgi?id=962599#c12
--- Comment #12 from Dominique Leuenberger
This won't help packages which are already in d:l:e. As soon as Factory will have package erlang-rebar, they will fetch it instead of local erlang-rebar-obs. Aren't they?
Yes, they would indeed (and I see the most important part you care for is the fact that rebar-obs does not rely on networking). Then I'd actually do it like this (which is a bit of work, but would be clean) in erlang-rebar-obs: Provides: erlang-rebar(nonet) = %{version} in erlang-retest: BuildRequires: erlang-rebar(nonet) in erlang-rebar: BuildRequires: erlang-retest (as is IIRC) Then all packages would have to specify that the way want an erlang-rebar with the capability to use nonet. An even cleaner solution would be similar to what ruby does: prefer if local is found and use net otherwise.. in OBS we can provide the local stuff my means of buildrequires and on the end user machines they can still go net if they want to. This would probably eliminate the need for the -obs package alltogether Or I misunderstand what the point is that is actually trying to be solved -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=962599
http://bugzilla.opensuse.org/show_bug.cgi?id=962599#c13
--- Comment #13 from Matwey Kornilov
http://bugzilla.opensuse.org/show_bug.cgi?id=962599
http://bugzilla.opensuse.org/show_bug.cgi?id=962599#c14
--- Comment #14 from Matwey Kornilov
participants (1)
-
bugzilla_noreply@novell.com