[opensuse-packaging] status 'broken' ?
From "osc results" - what does this mean?
openSUSE_Tumbleweed i586 broken openSUSE_Tumbleweed x86_64 broken openSUSE_Leap_42.1 x86_64 broken openSUSE_Factory_images i586 broken openSUSE_Factory_images ppc64p7 * openSUSE_Factory_images aarch64 broken openSUSE_Factory_images armv7l broken openSUSE_Factory_images armv6l broken openSUSE_Factory_images local * openSUSE_Factory_images s390x broken openSUSE_Factory_images ppc64 broken openSUSE_Factory_images ppc broken openSUSE_Factory_images x86_64 broken openSUSE_Factory_images ppc64le broken openSUSE_Factory_PowerPC ppc broken openSUSE_Factory_PowerPC ppc64 broken openSUSE_Factory_PowerPC ppc64le broken openSUSE_Factory_ARM aarch64 broken openSUSE_Factory_ARM armv7l broken openSUSE_Factory x86_64 broken openSUSE_Factory i586 broken openSUSE_13.2 i586 broken openSUSE_13.2 x86_64 broken SLE_12 x86_64 broken SLE_11_SP4 i586 broken SLE_11_SP4 x86_64 broken thanks Per -- Per Jessen, Zürich (13.4°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Thu, 2016-05-19 at 17:00 +0200, Per Jessen wrote:
From "osc results" - what does this mean?
openSUSE_Tumbleweed i586 broken openSUSE_Tumbleweed x86_64 broken openSUSE_Leap_42.1 x86_64 broken openSUSE_Factory_images i586 broken openSUSE_Factory_images ppc64p7 * openSUSE_Factory_images aarch64 broken openSUSE_Factory_images armv7l broken openSUSE_Factory_images armv6l broken openSUSE_Factory_images local * openSUSE_Factory_images s390x broken openSUSE_Factory_images ppc64 broken openSUSE_Factory_images ppc broken openSUSE_Factory_images x86_64 broken openSUSE_Factory_images ppc64le broken openSUSE_Factory_PowerPC ppc broken openSUSE_Factory_PowerPC ppc64 broken openSUSE_Factory_PowerPC ppc64le broken openSUSE_Factory_ARM aarch64 broken openSUSE_Factory_ARM armv7l broken openSUSE_Factory x86_64 broken openSUSE_Factory i586 broken openSUSE_13.2 i586 broken openSUSE_13.2 x86_64 broken SLE_12 x86_64 broken SLE_11_SP4 i586 broken SLE_11_SP4 x86_64 broken
usually a merge conflict or no source available...
try "osc results -v" Cheers, Dominique -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Adam Spiers wrote:
Per Jessen <per@computer.org> wrote:
From "osc results" - what does this mean?
The -v option might help.
Yes, it did, thanks - openSUSE_13.2 i586 broken: conflict in file lilo.spec openSUSE_13.2 x86_64 broken: conflict in file lilo.spec SLE_12 x86_64 broken: conflict in file lilo.spec SLE_11_SP4 i586 broken: conflict in file lilo.spec SLE_11_SP4 x86_64 broken: conflict in file lilo.spec Okay, not totally sure I understand what this means, but I think I've fixed it, it's building again. I notice a couple of status 'blocked': openSUSE_Tumbleweed i586 blocked openSUSE_Tumbleweed x86_64 blocked openSUSE_Factory x86_64 blocked openSUSE_Factory i586 blocked I think I saw that (for TW) yesterday too at some point, is this a process/scheduler status? -- Per Jessen, Zürich (12.6°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On čtvrtek 19. května 2016 18:21 Per Jessen wrote:
Adam Spiers wrote:
Per Jessen <per@computer.org> wrote:
From "osc results" - what does this mean?
The -v option might help.
Yes, it did, thanks -
openSUSE_13.2 i586 broken: conflict in file lilo.spec openSUSE_13.2 x86_64 broken: conflict in file lilo.spec SLE_12 x86_64 broken: conflict in file lilo.spec SLE_11_SP4 i586 broken: conflict in file lilo.spec SLE_11_SP4 x86_64 broken: conflict in file lilo.spec
Okay, not totally sure I understand what this means, but I think I've fixed it, it's building again. I notice a couple of status 'blocked':
Usual way of handling the conflict is osc update osc pull At this moment, "osc status" should show "C" at lilo.spec and you should have also files lilo.spec.mine, lilo.spec.old and lilo.spec.new. File lilo.spec should contain markers similar to those used in git conflict resolution. Once you edit lilo.spec to look the way you want it, do osc resolved lilo.spec osc commit and you should be done (I hope I didn't miss anything).
openSUSE_Tumbleweed i586 blocked openSUSE_Tumbleweed x86_64 blocked openSUSE_Factory x86_64 blocked openSUSE_Factory i586 blocked
I think I saw that (for TW) yesterday too at some point, is this a process/scheduler status?
This should mean the build of your package waits for another package which is being built now or is also blocked by something else. With "-v" option, the command should tell you what is it waiting for (and so does the web interface). Michal Kubeček -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Adam Spiers wrote:
Per Jessen <per@computer.org> wrote:
From "osc results" - what does this mean?
The -v option might help.
Yes, it did, thanks everyone - openSUSE_13.2 i586 broken: conflict in file lilo.spec openSUSE_13.2 x86_64 broken: conflict in file lilo.spec SLE_12 x86_64 broken: conflict in file lilo.spec SLE_11_SP4 i586 broken: conflict in file lilo.spec SLE_11_SP4 x86_64 broken: conflict in file lilo.spec Okay, not totally sure I understand what this means, but I think I've fixed it, it's building again. I notice a couple of status 'blocked': openSUSE_Tumbleweed i586 blocked openSUSE_Tumbleweed x86_64 blocked openSUSE_Factory x86_64 blocked openSUSE_Factory i586 blocked I think I saw that (for TW) yesterday too at some point, is this a process/scheduler status? -- Per Jessen, Zürich (12.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Thu, 2016-05-19 at 18:25 +0200, Per Jessen wrote:
Adam Spiers wrote:
Per Jessen <per@computer.org> wrote:
From "osc results" - what does this mean?
The -v option might help.
Yes, it did, thanks everyone -
openSUSE_13.2 i586 broken: conflict in file lilo.spec openSUSE_13.2 x86_64 broken: conflict in file lilo.spec SLE_12 x86_64 broken: conflict in file lilo.spec SLE_11_SP4 i586 broken: conflict in file lilo.spec SLE_11_SP4 x86_64 broken: conflict in file lilo.spec
The package you branched from had meen modified in the meantime... 'osc pull' to merge.. make sure to carefully review that your changes still make sense (don't just put your files into place)
Okay, not totally sure I understand what this means, but I think I've fixed it, it's building again. I notice a couple of status 'blocked':
openSUSE_Tumbleweed i586 blocked openSUSE_Tumbleweed x86_64 blocked openSUSE_Factory x86_64 blocked openSUSE_Factory i586 blocked I think I saw that (for TW) yesterday too at some point, is this a process/scheduler status?
Some packages which are needed to build your package are currently scheduled for building or are building - your build is 'blocked' until all your build dependencies are ready. Cheers, Dominique -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Thu, May 19, 2016 at 12:46 PM, Dominique Leuenberger / DimStar <dimstar@opensuse.org> wrote:
Okay, not totally sure I understand what this means, but I think I've fixed it, it's building again. I notice a couple of status 'blocked':
openSUSE_Tumbleweed i586 blocked openSUSE_Tumbleweed x86_64 blocked openSUSE_Factory x86_64 blocked openSUSE_Factory i586 blocked I think I saw that (for TW) yesterday too at some point, is this a process/scheduler status?
Some packages which are needed to build your package are currently scheduled for building or are building - your build is 'blocked' until all your build dependencies are ready.
For clarity, an example. I new gcc c compiler gets checked in. All packages with c code get automatically marked for re-building. But only those that don't build against any other c libraries get actually scheduled to build. The rest are blocked. As each c library is built, the list of blocked packages is scanned to see if all their dependencies are current. (ie. Not marked for re-build). Those blocked packages that now have all dependencies in "built" status are queued for building (ie. scheduled). Greg -- Greg Freemyer www.IntelligentAvatar.net -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Donnerstag, 19. Mai 2016, 17:00:36 wrote Per Jessen:
From "osc results" - what does this mean?
The source or project setup is broken. A build can not even be calculated. => osc r -v for details. -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (7)
-
Adam Spiers -
Adrian Schröter -
Dominique Leuenberger / DimStar -
Greg Freemyer -
Michal Kubecek -
Per Jessen -
Per Jessen