On Tue, 2015-12-15 at 00:29 +0000, Jim Henderson wrote:
I've gone in and tried to configure my home: project to build for Leap 42.1, but it stays stuck in a disabled state, even though the builds for the one project (pan-git) have the repos enabled.
It's been a while since I set this up for 13.2, but that build works - can someone jog my memory as to what I'm missing to get the build to work for 42.1?
Looking at the project meta definition, there is a global disable flag: <disable/> and there is no <enable> defined for the Leap_42.1 repositories to override the global setting - neither in the project or package level meta. It looks like the repository definitions in your project meta need to be cleaned up. There are build disables and enables defined for targets that don't exist as repository definitions. This might be confusing the web frontend which doesn't seem to match reality. For example: <disable arch="x86_64" repository="SLES_9"/> <disable repository="SLE_11_SP1"/> But <repository> with name="SLES_9" or "SLE_11_SP1" don't exist. -Scott