Upgrading from Mailman 3.0 installed with mailman-bundler: sassc error
Hit an issue while upgrading mailman bundler that I'm just going to note here in case it affects anyone else.
After upgrading, I go to the web interface and try to log in only to get the following error: “/bin/sh: sassc: command not found”
Which as a security person is the type of error message I least like seeing, but that's another story. ;)
This thankfully made me think of the last commit message in mailman-bundler, and the commits helped me figure out the rest:
https://gitlab.com/mailman/mailman-bundler/commit/3d6555acd640d77f510b786e5e...
the solution is
- install rubygem-sass
- update mailman_web/development.py so that COMPRESS_PRECOMPILERS asks for sass instead of sassc
I'm sure I'm going to find a few more bugs as I go, but I wanted to note that one before I forgot.
Terri
Terri Oda writes:
the solution is
- install rubygem-sass
- update mailman_web/development.py so that COMPRESS_PRECOMPILERS asks for sass instead of sassc
I suppose the idea was to depend on sassc and libsass rather than Ruby. Do we really need to introduce a dependency on Ruby? Won't that pull in a whole ecosystem?
On 2015-12-05 3:48 PM, Terri Oda wrote:
- update mailman_web/development.py so that COMPRESS_PRECOMPILERS asks for sass instead of sassc
Follow-up on this. I tried this on a fresh mailman-bundler install and you do indeed see the same problem. I changed the config in development.py and pushed my change, so hopefully people won't get hit by it going forwards.
... and I just realized I probably need to fix this in production.py as well. phooey. I'll go do that.
Terri
participants (3)
-
Barry Warsaw -
Stephen J. Turnbull -
Terri Oda