I have a strange problem with my libfastjson: using “osc build” locally, it builds fine for Debian’ish systems. However, when I commit to OBS, the Debian’ish repositores are excluded. See
The message indicating “exclusion”, as far as I understand, says that the repository is either disabled (it is not) or some required files are missing (they are not, as I can build locally). For my other libs, everything works.
Hi and welcome to the Forum
Doesn’t exist anymore in the ‘Add from Distribution’ list, might have to go hunting for them via the “Add from a Project” for example old openSUSE builds need to point at the Discontinued branch… for example in your case Debian 8.0 is no longer listed…
Thx. I have now deleted the Debian 10 repo and added it again. Now waiting for the system to pick up the propagation.
As a side note: can you explain, why this works for all other subprojects, just not for this libraray? I probably have a fundamental misunderstanding here, and I would like to clear it.
Hi
Have no idea to be honest, never pointed at home projects for repos (plus only build for openSUSE). If want to use as different project for a build, just use --alternative-project (mainly use osc ).
I had given up for a couple of days. I can’t get this library to build, besides tripple-checking all definitions. I have now also applied the problem to the original home project, available at
Any suggestion to get this fixed is highly appreciated. I am short of abandoning OBS because I can’t get this going. That would be very sad and also trash a lot of investment I have made in the past couple of months
OK, I finally was able to nail this by experimenting with working projects. The issue was that the .dsc file contained:
Architecture: source
for some reason this worked until recently. It also “worked” with"osc build", which brought me to the wrong debugging path.
It would really be good if the OBS web interface and the osc command line would share same semantics. It would be even better if problems like this would be flagged with a more explicit information message other than “definition file is missing”
Anyhow, it seems to work now. Thx again for the help.
).
