I’m trying to set up a local pressbooks-dev instance using the instructions found here. All is well until I run vagrant up to provision the environment.
The first error I’m getting is:
...
- downloading role from https://github.com/pressbooks/ansible-role-princexml/archive/11.3.tar.gz
[ERROR]: failed to download the file: HTTP Error 404: Not Found
[WARNING]: - princexml was NOT installed successfully.
To side-step this, I tried just removing all mentions of princexml in the server.yml, dev.yml, and requirements.yml, and that worked fine.
The issue that I’m stuck on now is this error:
TASK [common : Verify dict format for apt package component variables] *********
[WARNING]: Failure using method (v2_runner_on_failed) in callback plugin
(<ansible.plugins.callback.output.CallbackModule object at 0x105321208>): name
'unicode' is not defined
to retry, use: --limit @/Users/bryan/code/pressbooks-dev/trellis/dev.retry
PLAY RECAP *********************************************************************
default : ok=1 changed=0 unreachable=0 failed=1
Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
A cursory Google search makes it kind of look like a Python version issue? I’m not entirely sure. Will continue poking at this, but wanted to drop a line here in case someone’s run into this before and knows offhand how to solve.
Hey @bryan, as it so happens I was just working on the PrinceXML role yesterday. If you restore it to the requirements.yml and use version 11.4.0 it will work as expected.
Still didn’t get this working, but it’s not a crisis. From what I can tell, I’m still running into a python/ansible compatibility issue. I’ll keep tinkering about, and if I can get it working I’ll post here again.
vault_mysql_root_password: devpw
# Variables to accompany `group_vars/development/wordpress_sites.yml`
# Note: the site name (`example.com`) must match up with the site name in the above file.
vault_wordpress_sites:
pressbooks.test:
admin_password: admin
env:
db_password: example_dbpassword
Interesting. If you are running this in the same location as you were before pulling the latest version, can you try deleting the the trellis/vendor directory, then running vagrant halt && vagrant up --provision?