Re: Google Code bug tracker

[Christian Hammond]

Hi Morgan,

Can you change the hosting account to Custom and see if any errors appear
in there?

We're going to be completely revamping the repo configuration experience
probably in the next major version. There are issues with the architecture
this form is built upon, and we're starting to bump up into more of them.

Christian

-- 
Christian Hammond
President/CEO of Beanbag 
Makers of Review Board 

On Mon, May 2, 2016 at 8:11 PM, Morgan Chang 
wrote:

> Hi, Christian
>
> Here is the screen shot when the SAVE button is pressed.
>
>
> 
>
>
> On Saturday, April 30, 2016 at 3:19:28 AM UTC+8, Christian Hammond wrote:
>>
>> Hi Morgan,
>>
>> Can you screenshot the page and show me? That'll help me get a sense of
>> what to recommend next.
>>
>> Since Google Code is no more, we'll be taking support out of a future
>> release.
>>
>> Christian
>>
>>
>> On Friday, April 29, 2016, Morgan Chang  wrote:
>>
>>> Hi,
>>>
>>> I start to try Review Board 2.5.3 on Debian stretch.
>>> After creating a subversion repository successfully, I can change
>>> settings of the repository as I wish.
>>> However, after set the bug tracker to Google Code, and save
>>> successfully, the repository cannot be
>>> changed anymore afterward.
>>> There is only a error message on the top of page "Please correct the
>>> error below.", and without
>>> any hint about what the error is.
>>>
>>> Thanks.
>>>
>>> Morgan
>>>
>>> --
>>> Supercharge your Review Board with Power Pack:
>>> https://www.reviewboard.org/powerpack/
>>> Want us to host Review Board for you? Check out RBCommons:
>>> https://rbcommons.com/
>>> Happy user? Let us know! https://www.reviewboard.org/users/
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "reviewboard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to reviewboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> --
>> Christian Hammond
>> President/CEO of Beanbag 
>> Makers of Review Board 
>>
>>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Code bug tracker

[Morgan Chang]

Hi, Christian

Here is the screen shot when the SAVE button is pressed.




On Saturday, April 30, 2016 at 3:19:28 AM UTC+8, Christian Hammond wrote:
>
> Hi Morgan,
>
> Can you screenshot the page and show me? That'll help me get a sense of 
> what to recommend next.
>
> Since Google Code is no more, we'll be taking support out of a future 
> release.
>
> Christian
>
>
> On Friday, April 29, 2016, Morgan Chang  > wrote:
>
>> Hi,
>>
>> I start to try Review Board 2.5.3 on Debian stretch.
>> After creating a subversion repository successfully, I can change 
>> settings of the repository as I wish.
>> However, after set the bug tracker to Google Code, and save successfully, 
>> the repository cannot be
>> changed anymore afterward.
>> There is only a error message on the top of page "Please correct the 
>> error below.", and without
>> any hint about what the error is.
>>
>> Thanks.
>>
>> Morgan
>>
>> -- 
>> Supercharge your Review Board with Power Pack: 
>> https://www.reviewboard.org/powerpack/
>> Want us to host Review Board for you? Check out RBCommons: 
>> https://rbcommons.com/
>> Happy user? Let us know! https://www.reviewboard.org/users/
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "reviewboard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to reviewboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> -- 
> Christian Hammond
> President/CEO of Beanbag 
> Makers of Review Board 
>
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: rb-site upgrade fails with whoosh 2.5.7 on RHEL7/OL7

[Vlad]

Thanx! I will be able to test and report on May 4.

/v
2 мая 2016 г. 16:34 пользователь "Stephen Gallagher" <
step...@gallagherhome.com> написал:

> I've just submitted a corrected version of Review Board to the
> epel-testing repository:
>
> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-2bab5ad96d
>
> Please test it and provide it with positive or negative feedback (karma).
> That will get it into the stable release faster. (note: the reason this
> happened is that I made a mistake rebasing the patch for the dependencies
> and no one ever tested the update, so it went stable after the timeout
> period. Please help test this one!)
>
>
> On Sun, May 1, 2016 at 7:14 PM Stephen Gallagher <
> step...@gallagherhome.com> wrote:
>
>> I thought I had fixed the mime parse thing already. I'll correct that
>> when I fix up the whoosh thing tomorrow.
>>
>> I'm a comaintainer of Whoosh on the other branches, so I can push the
>> updated version. I just wanted to check with the other maintainers in case
>> there was a compatibility break I need to be aware of.
>>
>> On Sun, May 1, 2016 at 7:11 PM Vlad  wrote:
>>
>>> Hi Stephen,
>>>
>>> Thank you for the reply. Also there is another issue with
>>> "mimeparse>=0.1.3" requirement. Somehow it works only once changed to
>>> "python-mimeparse>=0.1.3". RHEL has proper 0.1.4 version though another
>>> package name.
>>>
>>> I tried to contact python-whoosh rpm maintainer and got email error:
>>>
>>>  - The following addresses had permanent fatal errors -
>>> rku...@mail.corp.redhat.com
>>> (reason: 554 5.4.6 Too many hops)
>>> (expanded from: )
>>> ..
>>>
>>> It might be he left Redhat and does not maintain the rpm anymore. I
>>> tried to build newer rpm just by replacing Version to 2.7.4 in .spec file
>>> and new sources. It builds ok. Not sure how to promote the spec file change.
>>>
>>> /v
>>>
>>> On Mon, May 2, 2016 at 1:58 AM, Stephen Gallagher <
>>> step...@gallagherhome.com> wrote:
>>>
 Sorry Vlad, that's my fault. I didn't notice the upgraded requirement.
 I'm going to try to get Whoosh updates in EPEL7 on Monday (once I talk to
 the maintainer of that package to figure out if they held it to the older
 version intentionally).

 On Sat, Apr 30, 2016 at 7:01 PM Vlad  wrote:

> Hi Christian,
>
> Would this hack affect only Search (Indexed search) function of
> ReviewBoard? Search is not configured by default, so this
> is not a strict dependency as I understand. Am I correct?
>
> I am not sure why RHEL7 has no whoosh update, so I did not install
> whoosh with pip.
>
> /v
>
> On Sun, May 1, 2016 at 12:48 AM, Christian Hammond <
> christ...@beanbaginc.com> wrote:
>
>> Hi Vlad,
>>
>> I can't speak for the RPMs, but Review Board itself requires Whoosh
>> 2.6+. There are bugs in prior versions that impact Review Board, so while
>> you may be able to change the dependencies, I can't guarantee it'll fully
>> work as expected.
>>
>> Christian
>>
>> --
>> Christian Hammond
>> President/CEO of Beanbag 
>> Makers of Review Board 
>>
>> On Sat, Apr 30, 2016 at 1:54 PM, Vlad S.  wrote:
>>
>>> Hi, upgrading 2.5.3 -> 2.5.4 on RHEL7 fails:
>>>
>>> # rb-site upgrade /var/www/rb.site.internal
>>>
>>> Traceback (most recent call last):
>>>
>>> File "/usr/bin/rb-site", line 5, in 
>>>
>>> from pkg_resources import load_entry_point
>>>
>>> File
>>> "/usr/lib/python2.7/site-packages/distribute-0.6.19-py2.7.egg/pkg_resources.py",
>>> line 2713, in 
>>>
>>> parse_requirements(__requires__), Environment()
>>>
>>> File
>>> "/usr/lib/python2.7/site-packages/distribute-0.6.19-py2.7.egg/pkg_resources.py",
>>> line 584, in resolve
>>>
>>> raise DistributionNotFound(req)
>>>
>>> pkg_resources.DistributionNotFound: Whoosh>=2.6
>>>
>>> # rpm -qa|grep -i whoosh
>>>
>>> python-whoosh-2.5.7-4.el7.noarch
>>>
>>> # rpm -qa|grep -i reviewboard
>>>
>>> ReviewBoard-2.5.4-1.el7.noarch
>>>
>>> RHEL7 (epel) has no whoosh 2.6+ and ReviewBoard does not requires
>>> exactly this version.. Shall I just fix ReviewBoard
>>> /usr/lib/python2.7/site-packages/ReviewBoard-2.5.4-py2.7.egg-info/requires.txt
>>>  to
>>> pass the rb-site upgrade?
>>>
>>> --
>>> Supercharge your Review Board with Power Pack:
>>> https://www.reviewboard.org/powerpack/
>>> Want us to host Review Board for you? Check out RBCommons:
>>> https://rbcommons.com/
>>> Happy user? Let us know! https://www.reviewboard.org/users/
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "reviewboard" group.
>>> To unsubscribe from 

Re: rb-site upgrade fails with whoosh 2.5.7 on RHEL7/OL7

[Stephen Gallagher]

I've just submitted a corrected version of Review Board to the epel-testing
repository:

https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-2bab5ad96d

Please test it and provide it with positive or negative feedback (karma).
That will get it into the stable release faster. (note: the reason this
happened is that I made a mistake rebasing the patch for the dependencies
and no one ever tested the update, so it went stable after the timeout
period. Please help test this one!)


On Sun, May 1, 2016 at 7:14 PM Stephen Gallagher 
wrote:

> I thought I had fixed the mime parse thing already. I'll correct that when
> I fix up the whoosh thing tomorrow.
>
> I'm a comaintainer of Whoosh on the other branches, so I can push the
> updated version. I just wanted to check with the other maintainers in case
> there was a compatibility break I need to be aware of.
>
> On Sun, May 1, 2016 at 7:11 PM Vlad  wrote:
>
>> Hi Stephen,
>>
>> Thank you for the reply. Also there is another issue with
>> "mimeparse>=0.1.3" requirement. Somehow it works only once changed to
>> "python-mimeparse>=0.1.3". RHEL has proper 0.1.4 version though another
>> package name.
>>
>> I tried to contact python-whoosh rpm maintainer and got email error:
>>
>>  - The following addresses had permanent fatal errors -
>> rku...@mail.corp.redhat.com
>> (reason: 554 5.4.6 Too many hops)
>> (expanded from: )
>> ..
>>
>> It might be he left Redhat and does not maintain the rpm anymore. I tried
>> to build newer rpm just by replacing Version to 2.7.4 in .spec file and new
>> sources. It builds ok. Not sure how to promote the spec file change.
>>
>> /v
>>
>> On Mon, May 2, 2016 at 1:58 AM, Stephen Gallagher <
>> step...@gallagherhome.com> wrote:
>>
>>> Sorry Vlad, that's my fault. I didn't notice the upgraded requirement.
>>> I'm going to try to get Whoosh updates in EPEL7 on Monday (once I talk to
>>> the maintainer of that package to figure out if they held it to the older
>>> version intentionally).
>>>
>>> On Sat, Apr 30, 2016 at 7:01 PM Vlad  wrote:
>>>
 Hi Christian,

 Would this hack affect only Search (Indexed search) function of
 ReviewBoard? Search is not configured by default, so this
 is not a strict dependency as I understand. Am I correct?

 I am not sure why RHEL7 has no whoosh update, so I did not install
 whoosh with pip.

 /v

 On Sun, May 1, 2016 at 12:48 AM, Christian Hammond <
 christ...@beanbaginc.com> wrote:

> Hi Vlad,
>
> I can't speak for the RPMs, but Review Board itself requires Whoosh
> 2.6+. There are bugs in prior versions that impact Review Board, so while
> you may be able to change the dependencies, I can't guarantee it'll fully
> work as expected.
>
> Christian
>
> --
> Christian Hammond
> President/CEO of Beanbag 
> Makers of Review Board 
>
> On Sat, Apr 30, 2016 at 1:54 PM, Vlad S.  wrote:
>
>> Hi, upgrading 2.5.3 -> 2.5.4 on RHEL7 fails:
>>
>> # rb-site upgrade /var/www/rb.site.internal
>>
>> Traceback (most recent call last):
>>
>> File "/usr/bin/rb-site", line 5, in 
>>
>> from pkg_resources import load_entry_point
>>
>> File
>> "/usr/lib/python2.7/site-packages/distribute-0.6.19-py2.7.egg/pkg_resources.py",
>> line 2713, in 
>>
>> parse_requirements(__requires__), Environment()
>>
>> File
>> "/usr/lib/python2.7/site-packages/distribute-0.6.19-py2.7.egg/pkg_resources.py",
>> line 584, in resolve
>>
>> raise DistributionNotFound(req)
>>
>> pkg_resources.DistributionNotFound: Whoosh>=2.6
>>
>> # rpm -qa|grep -i whoosh
>>
>> python-whoosh-2.5.7-4.el7.noarch
>>
>> # rpm -qa|grep -i reviewboard
>>
>> ReviewBoard-2.5.4-1.el7.noarch
>>
>> RHEL7 (epel) has no whoosh 2.6+ and ReviewBoard does not requires
>> exactly this version.. Shall I just fix ReviewBoard
>> /usr/lib/python2.7/site-packages/ReviewBoard-2.5.4-py2.7.egg-info/requires.txt
>>  to
>> pass the rb-site upgrade?
>>
>> --
>> Supercharge your Review Board with Power Pack:
>> https://www.reviewboard.org/powerpack/
>> Want us to host Review Board for you? Check out RBCommons:
>> https://rbcommons.com/
>> Happy user? Let us know! https://www.reviewboard.org/users/
>> ---
>> You received this message because you are subscribed to the Google
>> Groups "reviewboard" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to reviewboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> Supercharge your Review Board with Power Pack:
> 

Re: Exyending Characters in Username Field

[john levin]

Ok. I have altered the field first_name in the DB directly. Now i could 
able to login with more than 30 characters. 

Now, the GUI i could see it is not including the characters more than 30 in 
the Username field. But that couldn't be a trouble at all for us (since 
users are able to login). 

However, i'm going to try to extend that too. Seems like i have to work on 
Django stuffs.. Any Idea about this ?

Thanks !

/BR
John

On Thursday, April 28, 2016 at 5:07:07 PM UTC+5:30, john levin wrote:
>
> Hi,
>
> It was allowing 30 characters in username field. We have some ids which 
> goes beyond 30 characters (We use LDAP authentication).
> Can you please let me know how to increase the length of username field ?
>
> Thanks.
>
> Regards
> John
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.