Mailinglist Archive: opensuse-buildservice (124 mails)

< Previous Next >
Re: [opensuse-buildservice] OBS build dependency issue
  • From: Adrian Schröter <adrian@xxxxxxx>
  • Date: Wed, 20 Mar 2013 09:14:50 +0100
  • Message-id: <2798065.fQlU4BdNOR@scherben>
On Dienstag, 19. März 2013, 19:25:14 wrote Malcolm Fernandes:

-----Original Message-----
From: Malcolm Fernandes [mailto:mfernand@xxxxxxxxxxxx]
Sent: Sunday, March 17, 2013 8:40 PM
To: Marcus Meissner
Cc: opensuse-buildservice@xxxxxxxxxxxx
Subject: RE: [opensuse-buildservice] OBS build dependency issue

Hi Markus,

Comments embedded below.

-----Original Message-----
From: Marcus Meissner [mailto:meissner@xxxxxxx]
Sent: Saturday, March 16, 2013 1:42 AM
To: Malcolm Fernandes
Cc: opensuse-buildservice@xxxxxxxxxxxx
Subject: Re: [opensuse-buildservice] OBS build dependency issue

On Fri, Mar 15, 2013 at 10:47:33PM +0000, Malcolm Fernandes wrote:
We have a project in our local OBS instance where we are encountering some
build dependency issues.

Our OBS is running on an appliance: obs-server-2.3.1-6.7.x86_64

To illustrate the problem:

Let's assume we have 5 packages in a project (pkg1, pkg2, pkg3, pkg4, pkg5)

The pkg2 spec file contains a "BuildRequires:" for one of the rpms
generated by pkg1.
Similarly the pkg3 spec file contains a "BuildRequires:" for one of the
rpms generated by pkg2 and so forth.

When a commit was made to pkg1, it got rebuilt and this triggered pkg2 to
start building. While pkg2 was rebuilding, pkg3, pkg4 and pkg5 went into
a blocked state (which is what we expected).

However, after pkg2 finished building, pkg-3/4/5 get unblocked and do NOT
get rebuilt.

Did you check the buildlog? Perhaps "build compare" triggered and found the
builds identical?

[MF] Yes, the buildlog does detect changes in the generated rpms as per the
build compare. Note, that I tried the exact same scenario in a
home:mfernand:debug project and the dependent packages all build fine there.
It's just this one project which is exhibiting these issues.

[MF-03/19/2013] Some more observations. The OBS project having issues had
rebuild="direct" in the project meta, while my home project (which does not
have problems) does not have that attribute. I believe rebuild="transitive"
is the default. When I added the rebuild="direct" in the project meta of my
home project, it also exhibited the build dependency issues.
I'm guessing I should remove the rebuild="direct" in the project meta and let
it default to 'transitive'. Any thoughts on this?

yes. It is the default for a good reason :)

..
What is the project meta and the repository rebuild strategy?
[MF] This is an extract of the project meta:
<repository rebuild="direct" name="standard">
<arch>armv8el</arch>

Uh, you really use that one? You are aware that this architecture never existed
and actually got called "aarch64" meanwhile?

bye
adrian

--
Adrian Schroeter
SUSE Linux Products GmbH
email: adrian@xxxxxxx

--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups