[opensuse-factory] Difference of openSUSE_Tumbleweed and openSUSE_Factory build targets
Hi, since I'm stumbling across a strange dependency issue right now, could some brave soul explain the difference of openSUSE_Tumbleweed and openSUSE_Factory build targets, please? E.g.: https://build.opensuse.org/project/show/graphics defines both identically: <repository name="openSUSE_Tumbleweed"> <path project="openSUSE:Factory" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="openSUSE_Factory"> <path project="openSUSE:Factory" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository> And while at it, why could some packages link to Factory, but those packages aren't available, yet. I see this issue with my blender builds. They link with liboslcomp.so.1.10()(64bit) from liboslcomp1_10 (OpenShadingLanguage), that should come from Factory: $ zyp dup [...] Problem: nothing provides liboslcomp.so.1.10()(64bit) needed by blender27-2.79b-5.2.x86_64 Problem: nothing provides liboslcomp.so.1.10()(64bit) needed by blender-git-2.82~git.20191104T103521.e45cfb574ee-9.4.x86_64 Problem: nothing provides liboslcomp.so.1.10()(64bit) needed by blender-281-2.81~git.20191107T165621.79b703bb635-8.2.x86_64 Problem: nothing provides liboslcomp.so.1.10()(64bit) needed by blender-2.80-349.1.x86_64 Problem: nothing provides liboslcomp.so.1.10()(64bit) needed by blender-281-2.81~git.20191107T165621.79b703bb635-8.2.x86_64 but obviously doesn't: $ zyp se -s liboslcomp [...] S | Name | Type | Version | Arch | Repository --+-------------------------+---------+------------+--------+-------------------------- i | liboslcomp1_9 | package | 1.9.13-2.8 | x86_64 | openSUSE-Tumbleweed-OSS v | liboslcomp1_9 | package | 1.9.13-2.8 | i586 | openSUSE-Tumbleweed-OSS | liboslcomp1_9-debuginfo | package | 1.9.13-2.8 | x86_64 | openSUSE-Tumbleweed-Debug | liboslcomp1_9-debuginfo | package | 1.9.13-2.8 | i586 | openSUSE-Tumbleweed-Debug Thanks for enlightenment, Pete -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, On Fri, 2019-11-08 at 12:55 +0100, Hans-Peter Jansen wrote:
Hi,
since I'm stumbling across a strange dependency issue right now, could some brave soul explain the difference of openSUSE_Tumbleweed and openSUSE_Factory build targets, please?
E.g.: https://build.opensuse.org/project/show/graphics defines both identically:
<repository name="openSUSE_Tumbleweed"> <path project="openSUSE:Factory" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository>
openSUSE_Tunbleweed should normally be defined as either openSUSE:Tumbleweed/standard or openSUSE:Factory/snapshot In this case, it seems somebody was 'breaking' the logic though The logic, if correctly setup, would be: openSUSE_Factory: build against the 'FUTURE' snapshot This is especially useful for devel repos, working on the future openSUSE_Tumbleweed: build against the published snapshot This is useful for user-targetted repos
<repository name="openSUSE_Factory"> <path project="openSUSE:Factory" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository>
And while at it, why could some packages link to Factory, but those packages aren't available, yet.
They are available in Factory (which is how they could be linked) but not yet available in a published Tumbleweed snapshot. In essence: Factory == Tumbleweed (with a time gap) - Factory is pre-QA-pre- Publish, Tumbleweed is post-QA-post-publish. For apparent reasons, there is a time gap in between (while Factory builds, is being tested and published) - in normal cases this delta is about 24 - 48 hours. Hope that helps Dominique
Am Freitag, 8. November 2019, 13:14:16 CET schrieb Dominique Leuenberger / DimStar:
Hi,
On Fri, 2019-11-08 at 12:55 +0100, Hans-Peter Jansen wrote:
Hi,
since I'm stumbling across a strange dependency issue right now, could some brave soul explain the difference of openSUSE_Tumbleweed and openSUSE_Factory build targets, please?
E.g.: https://build.opensuse.org/project/show/graphics defines both
identically: <repository name="openSUSE_Tumbleweed">
<path project="openSUSE:Factory" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch>
</repository>
openSUSE_Tunbleweed should normally be defined as either openSUSE:Tumbleweed/standard or openSUSE:Factory/snapshot
In this case, it seems somebody was 'breaking' the logic though
Hopefully, somebody watching with admin rights to graphics will correct this (preferably over the weekend..).
The logic, if correctly setup, would be: openSUSE_Factory: build against the 'FUTURE' snapshot This is especially useful for devel repos, working on the future openSUSE_Tumbleweed: build against the published snapshot This is useful for user-targetted repos
<repository name="openSUSE_Factory">
<path project="openSUSE:Factory" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch>
</repository>
And while at it, why could some packages link to Factory, but those packages aren't available, yet.
They are available in Factory (which is how they could be linked) but not yet available in a published Tumbleweed snapshot. In essence:
Factory == Tumbleweed (with a time gap) - Factory is pre-QA-pre- Publish, Tumbleweed is post-QA-post-publish. For apparent reasons, there is a time gap in between (while Factory builds, is being tested and published) - in normal cases this delta is about 24 - 48 hours.
Thank you very much, Dominique.
Hope that helps
Yes, "of course" ;-)
Dominique
Cheers, Pete -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Dominique Leuenberger / DimStar -
Hans-Peter Jansen