The problem turned out to be the RPM spec file for reviewboard listed
Djblets 0.6.20, while we upgraded to 0.6.21.
There were auth module errors in the reviewboard log.
This has been fixed by re-rolling the reviewboard RPM.
Thanks for your help.
Phil
On Wednesday, July 25, 2012 2:00:36 PM UTC
We make use of setuptools-provided Python Entrypoints, which register some
scannable bits of data for things like authentication modules. It sounds
like those registrations got lost somehow in your packaging.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewbo
We grabed the gzips from the releases directory and created RPMs for
DJblets 0.6.21 and reviewboard 1.6.10,
then installed the RPMs, then ran rb-site upgrade.
We used RPMs before for 1.6.3, so continued doing it this way just in case
we need to back out.
On Wednesday, July 25, 2012 1:05:27 PM
Did you upgrade using pip or easy_install?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Jul 25, 2012 at 12:40 PM, Phil Hom wrote:
> We upgraded from 1.6.3 to 1.6.10, everything looks good.
> Except
We upgraded from 1.6.3 to 1.6.10, everything looks good.
Except the Authentication Settings page only shows Standard Reg and Legacy,
no LDAP, AD, or others.
Is there something I'm misssing.
THanks.
Phil
On Sunday, July 22, 2012 1:20:30 AM UTC-7, Christian Hammond wrote:
>
> Hey everyone,
>
> We
Thanks. I'll try the update when I'm back at work.
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send
I'm having the same problem.
On the outgoing requests page, the new review is tagged with [Draft].
There we no javascript errors during page load (using Chrome).
I did do an rb-site upgrade and it completed with no errors.
On Monday, 23 July 2012 15:38:06 UTC+1, Darryl McCutcheon wrote:
>
>
> I
Alright guys, I've found the problem.
This was a bug in Djblets. It was doing a check if an ID was an integer,
but not all databases represent it as an integer. The check has been fixed.
I have upgraded Review Board (still 1.6.10) to fetch the proper version.
You can re-upgrade to 1.6.10, or if y
Also, can you e-mail me a screenshot? In private is fine.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Tue, Jul 24, 2012 at 10:44 AM, Christian Hammond wrote:
> Are you able to edit existing non-drafts?
Are you able to edit existing non-drafts?
Christian
On Jul 24, 2012, at 3:44, Alex Postlethwaite
wrote:
> I'm having the same problem.
>
> On the outgoing requests page, the new review is tagged with [Draft].
>
> There we no javascript errors during page load (using Chrome).
> I did do an
I'll update when I get another chance to try later this week. I'm sure
it's something simple.
On Monday, July 23, 2012 4:10:18 PM UTC-4, Christian Hammond wrote:
>
> This doesn't sound like something in the code, but rather a setup issue on
> your server. If that import fails, my guess is that
By the way, if there are people who upgraded to this release and aren't
experiencing errors, that'd be a great datapoint to have.
Christian
On Jul 23, 2012, at 11:48, Christian Hammond wrote:
> I'd be interested in knowing if there were any JavaScript errors.
>
> Did you do rb-site upgrade?
This doesn't sound like something in the code, but rather a setup issue on your
server. If that import fails, my guess is that 1.6.10 isn't anywhere in the
python path.
Christian
On Jul 23, 2012, at 5:47, whatever wrote:
> So I upgraded from 1.6.9 yesterday, but rbssh.py was having issues.
I'd be interested in knowing if there were any JavaScript errors.
Did you do rb-site upgrade?
Christian
On Jul 23, 2012, at 7:38, Darryl McCutcheon wrote:
>
> I had an issue when I upgraded this morning that none of the users could edit
> their review, or mark their reviews as closed (submi
I had an issue when I upgraded this morning that none of the users could
edit their review, or mark their reviews as closed (submitted or discarded).
I ended up creating a perm group with enough rights, then added all the
users to the group. Seems to have temporarily solved the problem.
On Su
So I upgraded from 1.6.9 yesterday, but rbssh.py was having issues.
It couldn't get past the following import:
from reviewboard.scmtools import sshutils
I didn't have time to figure out the problem as I needed to get it back up
last night, so I went back to 1.6.9. I should be able to try agai
16 matches
Mail list logo