[opensuse-factory] How to control builds in OBS?
I am the relatively new maintainer for VirtualBox with limited knowledge of the RPM build process. My predecessors had made the decision to keep the version of VB in openSUSE 13.2 to VB 4.3.x and that 13.1 be kept to VB 4.2.x. I support that decision, thus the builds for 5.0.x are never submitted to the openSUSE:13.y:Update branches. Despite that, I just received a build failure notice from OBS with the subject "Build failure of Virtualization/virtualbox in openSUSE_13.1/x86_64". The detailed log shows that a build of VB 5.0.10 that ran out of disk space. As far as I am concerned, attempting that build was a waste of OBS resources. What changes should I make in the .spec file to prevent these useless builds for 13.1 and 13.2? In case a build that is important runs out of space, what is the default disk space assigned to builds. Thanks, Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
you can disable build for speccific repo.
+ you can add _constrains file with needed minimal amount disk space:)
On 18 December 2015 at 18:15, Larry Finger
I am the relatively new maintainer for VirtualBox with limited knowledge of the RPM build process. My predecessors had made the decision to keep the version of VB in openSUSE 13.2 to VB 4.3.x and that 13.1 be kept to VB 4.2.x. I support that decision, thus the builds for 5.0.x are never submitted to the openSUSE:13.y:Update branches. Despite that, I just received a build failure notice from OBS with the subject "Build failure of Virtualization/virtualbox in openSUSE_13.1/x86_64". The detailed log shows that a build of VB 5.0.10 that ran out of disk space. As far as I am concerned, attempting that build was a waste of OBS resources.
What changes should I make in the .spec file to prevent these useless builds for 13.1 and 13.2?
In case a build that is important runs out of space, what is the default disk space assigned to builds.
Thanks,
Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op vrijdag 18 december 2015 11:15:57 schreef Larry Finger:
I am the relatively new maintainer for VirtualBox with limited knowledge of the RPM build process. My predecessors had made the decision to keep the version of VB in openSUSE 13.2 to VB 4.3.x and that 13.1 be kept to VB 4.2.x. I support that decision, thus the builds for 5.0.x are never submitted to the openSUSE:13.y:Update branches. Despite that, I just received a build failure notice from OBS with the subject "Build failure of Virtualization/virtualbox in openSUSE_13.1/x86_64". The detailed log shows that a build of VB 5.0.10 that ran out of disk space. As far as I am concerned, attempting that build was a waste of OBS resources.
What changes should I make in the .spec file to prevent these useless builds for 13.1 and 13.2?
In case a build that is important runs out of space, what is the default disk space assigned to builds.
Thanks,
Larry When you have the OBS webinterface open at package level, the repository tab allows you to disable specific builds for only that package. -- Gertjan Lettink, a.k.a. Knurpht
Official openSUSE Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 12/18/2015 11:28 AM, Knurpht - Gertjan Lettink wrote:
Op vrijdag 18 december 2015 11:15:57 schreef Larry Finger:
I am the relatively new maintainer for VirtualBox with limited knowledge of the RPM build process. My predecessors had made the decision to keep the version of VB in openSUSE 13.2 to VB 4.3.x and that 13.1 be kept to VB 4.2.x. I support that decision, thus the builds for 5.0.x are never submitted to the openSUSE:13.y:Update branches. Despite that, I just received a build failure notice from OBS with the subject "Build failure of Virtualization/virtualbox in openSUSE_13.1/x86_64". The detailed log shows that a build of VB 5.0.10 that ran out of disk space. As far as I am concerned, attempting that build was a waste of OBS resources.
What changes should I make in the .spec file to prevent these useless builds for 13.1 and 13.2?
In case a build that is important runs out of space, what is the default disk space assigned to builds.
Thanks,
Larry When you have the OBS webinterface open at package level, the repository tab allows you to disable specific builds for only that package.
Thanks. That was easy. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, Dec 18, 2015 at 12:39 PM, Larry Finger
On 12/18/2015 11:28 AM, Knurpht - Gertjan Lettink wrote:
Op vrijdag 18 december 2015 11:15:57 schreef Larry Finger:
I am the relatively new maintainer for VirtualBox with limited knowledge of the RPM build process. My predecessors had made the decision to keep the version of VB in openSUSE 13.2 to VB 4.3.x and that 13.1 be kept to VB 4.2.x. I support that decision, thus the builds for 5.0.x are never submitted to the openSUSE:13.y:Update branches. Despite that, I just received a build failure notice from OBS with the subject "Build failure of Virtualization/virtualbox in openSUSE_13.1/x86_64". The detailed log shows that a build of VB 5.0.10 that ran out of disk space. As far as I am concerned, attempting that build was a waste of OBS resources.
What changes should I make in the .spec file to prevent these useless builds for 13.1 and 13.2?
In case a build that is important runs out of space, what is the default disk space assigned to builds.
Thanks,
Larry
When you have the OBS webinterface open at package level, the repository tab allows you to disable specific builds for only that package.
Thanks. That was easy.
Larry
Larry, Just a comment that a lot of "devel" packages build newer RPMs for older releases of openSUSE. That gives the users the ability to upgrade to newer versions by directly installing from the devel project. If, as maintainer, you don't want to support that feature, fine, but it is definitely a feature many opensuse users leverage. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Greg Freemyer -
Knurpht - Gertjan Lettink -
Larry Finger -
Ondřej Súkup