-
-
Notifications
You must be signed in to change notification settings - Fork 649
'postgresql_packages' is undefined #957
Comments
@mgifford - This would be inside the VM itself... but there shouldn't be a condition when using Drupal VM where that variable isn't defined—you're using Vagrant and building a VM using one of the Here's the task in the Ansible role that defines the packages: https://github.com/geerlingguy/ansible-role-postgresql/blob/3cb4aaaa53b32a0a0df113db19777d4a72afcd83/tasks/variables.yml#L11-L14 Do you have something like |
|
Same issue. Upgraded from 3.2 or older version of DrupalVM. Had to figure out how to upgrade Ansible, no mention of that in "breaking changes". But can't find workaround for this issue. |
I have the same issue, running the 14.04 vm |
Fixed upstream, going to fix by updating role deps here. |
Progress. I'm getting different errors now. I ran I made that ansible is at 2.2.0.0 I've updated the git repo for drupalvm
GitHub doesn't seem to like the long lines. Full report here - http://pastebin.com/ezBwqzfS Seems the problem boils down to "The requested package drupal/devel could not be found in any version". |
For anyone looking for a fix to the original problem here... basically the solution is to update DrupalVM to 3.5.1. It doesn't look like there was ever an upstream "fix" to Ansible. |
I think the long lines are fine, but maybe it is hard to tell because your browser does not show a scrollbar unless you are actively scrolling. Is this a "feature" of recent versions of macOS? |
…e 2.2 compatibility.
…e 2.2 compatibility.
I'm not sure why I am getting this error when I run
$ vagrant provision
:I can't find a solid reference to 'postgresql_packages', but have made sure that postgresql is installed:
$ brew install postgresql
It seems to be running:
$ brew services start postgresql
Service
postgresql
already started, usebrew services restart postgresql
to restart.Where should this be defined?
This is on a Mac (obviously), but not sure where to go from here. It was running find the last time I used DrupalVM. Just did an update and now am rather stuck.
The text was updated successfully, but these errors were encountered: