-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
claw-playbook unmet dependencies #873
Comments
Commenting out the above line I was able to install islandora_core_feature and then islandora_demo_feature but my vagrant box is still a mess. Trying running ansible-playbook over the top to see if it can be recovered. |
I have made a branch without the dependency. I need to try pulling up the box using this branch and if it works I'll open a PR. |
Yeah... so if it's getting added when exporting the feature, I'm afraid I haven't separated these out as well as I had hoped :( I"ll have to dig to see what's out of place. I know @seth-shaw-unlv has already discovered a few nuggets. There's probably more. |
Yeah, commenting out that line works just fine. That'll plug the hole for now, but I'll keep on digging. Looks like some stuff for the article content type slipped in, too. |
I was incorrect, this seems to be due to |
So the issue is two fold, one we seem to have some sort of error that (I think looked like a MySQL error) on the first run through. Not sure why that has suddenly appeared. But then the geerlinguy drupal role has some weak logic and assumes that if Drupal was installed the everything after that worked too. So we fail here. We might fail because of our modules, that I am not sure of. But anyways... Then on a second run that is skipped because Drupal bootstrap IS in the output as defined way up here. So when we attempt to set the solr_search_api settings later it fails. This requires a manual intervention to enable Here is the full error that is crashing out of enabling the modules.
|
When testing originally, I used It definitely has something to do with the content translation fix I did so we can get at our datastreams in Fedora. I'm thinking I didn't fully export everything we needed for content translation in the feature. |
We're running smack dab into this: https://www.drupal.org/node/2599228. There's a bug when importing config with translations enabled and Looks like we can solve this by running We may have to shuffle some code to the post-install section and do it after running |
Having exhausted all possible options (hook install code, programatically submitting a form, This is gonna be gross, but temporary. 🙏 |
Got it. @Islandora-CLAW/committers ^^ This should fix the installer. |
Something in the last Islandora commit is failing to install cleanly.
Claw-playbook throws the error.
Logging into the vagrant and trying to load the
islandora_demo_feature
module results in.But what is interesting is...
which makes it seem like a circular dependency has been introduced.
@dannylamb
The text was updated successfully, but these errors were encountered: