Oh, because of 1.7.0.1. Right, newer versions hard-code a specific version.
Christian
On Mar 13, 2013, at 1:30, kvr wrote:
> I have just done normal upgrade but it installed django-pipeline-1.3.6 and
> django-pipeline-1.3.6 caused this error, after installing 1.2.17 or 1.7.22,
> it got fixed
I have just done normal upgrade but it installed django-pipeline-1.3.6 and
django-pipeline-1.3.6 caused this error, after installing 1.2.17 or 1.7.22,
it got fixed.
On Wednesday, March 13, 2013 12:01:32 PM UTC+5:30, Christian Hammond wrote:
>
> How did you upgrade Review Board? The proper, suppo
How did you upgrade Review Board? The proper, supported version should have
been taken care of for you (and lessc should never be invoked).
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Mar 12, 2013, at 11
Resolved this by installing django-pipeline version-1.2.17
On Wednesday, March 13, 2013 11:17:44 AM UTC+5:30, kvr wrote:
>
> Hi ,
>
> We are upgrading our Review Board 1.5.7 to 1.7.0.1.
>
> Upgrade was successful but while accessing the site, we encountered the
> following error.
>
> CompilerErr
Hi ,
We are upgrading our Review Board 1.5.7 to 1.7.0.1.
Upgrade was successful but while accessing the site, we encountered the
following error.
CompilerError at /dashboard/
/usr/bin/env: lessc: No such file or directory
This points to {% compressed_css "admin" %} in templates/admin/base.htm
