>
> Looks like a lot of the battle is with SELINUX... I now have 2.0.5 running
> and it seems to be happy in its little world. Now to start tying it into
> the VisualSVN server again. At this time I have a snapshot of the unit in
> good condition however do you have an SELINUX exception that al
On Thursday, July 31, 2014 3:26:08 PM UTC-5, Christian Hammond wrote:
>
> It’s definitely valid syntax.
>
> Make sure the __ is two underscores.
>
> Can you copy/paste that to a text file and attach it, so that the
> formatting is preserved?
>
> Christian
>
>
>
>
>
> Doing it with notepad as a m
It’s definitely valid syntax.
Make sure the __ is two underscores.
Can you copy/paste that to a text file and attach it, so that the formatting is
preserved?
Christian
--
Christian Hammond - christ...@beanbaginc.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbagi
On Thursday, July 31, 2014 2:53:44 PM UTC-5, Christian Hammond wrote:
>
> During that run, is selinux still disabled?
>
> Can you run this in a shell:
>
> $ python
> >>> import whoosh
> >>> whoosh.__file__
> >>> import reviewboard
> >>> reviewboard.__file__
>
> $ python
>
During that run, is selinux still disabled?
Can you run this in a shell:
$ python
>>> import whoosh
>>> whoosh.__file__
>>> import reviewboard
>>> reviewboard.__file__
$ python
>>> import __main__
>>> __main__.__requires__ = [‘ReviewBoard’]
>>> import pkg_reso
OK wow... Went back to square one and reloaded everything to keep it clean.
I believe the bulk of my problems were actually a combination of selinux &
iptables; once I temporarily disabled them and tracked out a bunch of deps
I have the 2.0.5 system up on a clean install (no yum reviewboard re
Hi Michael,
“Whoosh” is a new dependency only in Review Board 2.0.x. The fact that it was
trying to find Whoosh says that there’s some metadata specifying that Review
Board is depending on Whoosh. Is there any chance that your first upgrade
attempt resulted in an “easy_install -U ReviewBoard” t
>
> Christian:
>
Again, just to be clear the machine is snapshot'd at the running
1.7.25 yum install, which is working. The steps above all related to
getting 1.7.25 upgraded to 1.7.27; the snapshot in question had never been
used to attempt a 2.0.x install.
I will revert, then uninsta
It doesn’t sound like anything but the metadata for Review Board 2.0.x was ever
installed. No files were ever fetched.
Your mixing and matching of yum packages and easy_install packages is likely
causing your problems. You also tried to install Review Board 2.0.x previously
(given that it’s try
>
> OK so given the yum install is topped out at RB 1.7.25, Python at 2.6 and
> others accordingly, would the best way to be rpm -e on everything and
> reinstalling from scratch? Again, I have a snapshot of the running base
> system so reverting is not an issue when I get down a dead end..
>
O
Hi Michael,
You'll likely run into problems attempting to mix yum-installed and
easy_installed packages for Review Board. You need to use one or the other,
but not both. This applies to ReviewBoard, Djblets, django-evolution,
django-pipeline, and more.
It sounds like the attempts to deal with Pyt
Trying to get up to 2.x to work on the SSL certificate errors. Environment
is:
Centos 65 updated.
Python 2.6 (yum installed)
ReviewBoard 1.7.25 (yum installed)
Setuptools are installed, so easy_install is available.
Attempting to do ANY upgrade (easy_install -U reviewboard or
reviewboard=1.7.2
12 matches
Mail list logo
