That's what I expected, due to how things have been setup, going from singnet to opencog is more troublesome than going from opencog to singnet. Eventhough it seems it's only a matter of fixing the circleci config.
Options I see
Subsequently fix circleci config on the opencog side, but then going from opencog to singnet will create a similar breakage.
Find a way to make that circleci repo-generic.
Drop circleci altogether it sucks anyway :-D
There's of course the options of always going from opencog to singnet (which I have done so far, for that very reason), or the option of never going from singnet to opencog (which seems a bit extreme, especially if we want to avoid at least artificial divergence between opencog and singnet).
That's what I expected, due to how things have been setup, going from singnet to opencog is more troublesome than going from opencog to singnet. Eventhough it seems it's only a matter of fixing the circleci config.
Options I see
There's of course the options of always going from opencog to singnet (which I have done so far, for that very reason), or the option of never going from singnet to opencog (which seems a bit extreme, especially if we want to avoid at least artificial divergence between opencog and singnet).