http://bugzilla.novell.com/show_bug.cgi?id=516845 Summary: unnecessary blocking on packages that are not 'usedforbuild' Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: SLES 11 Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: michael_e_brown@dell.com QAContact: adrian@novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b4) Gecko/20090427 Fedora/3.5-0.20.beta4.fc11 Firefox/3.5b4 OBS blocks packages that BuildRequire building packages even if those packages have <usedforbuild></disable></useforbuild>. I have a case in my private OBS instance where it looks like there is unnecessary blocking between two packages (with a BuildRequires dependency) in a project when publish and useforbuild is disabled. My project setup: Integration (BuildRepositories BR-a BR-b BR-c) pkgA pkgB (BuildRequires: pkgA) ... pkg-n home:testbuild (BuildRepositories Integration/BR-a Integration/BR-b Integration/BR-c) pkgA pkgB (BuildRequires: pkgA, which should be coming from Integration/pkgA) The testbuild project is set to build off the integration project so that we can do a test build of any individual package. The 'pkgA', 'pkgB' packages in home:testbuild are set to: <publish><disable/></publish> <useforbuild><disable/></useforbuild> This is so that all BuildRequires are always set to pull from the integration project. What I have observed is that when I rebuild pkgA in home:testbuild, pkgB goes into a "blocking" state unnecessarily. I say unnecessarily because pkgB should be pulling pkgA from the Integration project, not home:testbuild, so there should not actually be a dependency relationship between these two packages. Despite this, obs will block build of pkgA until pkgB has completed its build. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.