Re: GitHub webhook to Reviewboard not working

[Ron T]

Hi Christian,
Is the approach I'm using more difficult than the norm?  I just want a
review request generated during the process of writing code, people able to
review it, etc.
What are others users doing to get a review request generated by an
in-house reviewboard server using a github repository?
Do they have to use the command line or can they use a GUI?
I followed the Review Board instructions to setup a webhook to github but I
think that is just for closing a review?

I don't understand this paragraph entirely.
If you wanted to run something when pushing to a repository, you'd have to
write a small web service/script that GitHub can HTTP POST to. They have
documentation on how to do that, but Review Board has nothing that's going
to be able to help you here, as it's a bit outside the scope and would be a
custom in-house workflow.
To clarify, are you saying, on the Review Board server I need to write a
script that will listen for an HTTP POST coming from GitHub?
Would the script still need to use the rbt post commands?
Thanks!


On Tue, Oct 1, 2019 at 11:31 AM Christian Hammond 
wrote:

> Hi Ron,
>
> I don't believe Git offers a way to force post-commit hooks to be
> installed in clones of a repository (likely for security reasons). They
> have a concept called "templates" which can auto-populate content in a
> cloned Git repository, but I don't think the repository you clone can
> control the templates. I think each person cloning would have to set it up
> individually. You may have to control all this in-house by making it part
> of the development and checkout process run by your engineers. Perhaps some
> sort of custom clone script, or a script that's run when people first set
> up a build from their cloned repository. It's outside the scope of Review
> Board, and not something we can help too much with.
>
> If you wanted to run something when pushing to a repository, you'd have to
> write a small web service/script that GitHub can HTTP POST to. They have
> documentation on how to do that, but Review Board has nothing that's going
> to be able to help you here, as it's a bit outside the scope and would be a
> custom in-house workflow.
>
> Christian
>
> On Tue, Oct 1, 2019 at 11:10 AM Ron T  wrote:
>
>> Christian,
>> When a user commits or pushes from a GUI editor to their local repository
>> which is a clone of their github repository, how do I get reviewboard to
>> send out a notification? In this case they are not running the rbt post
>> command because they are using a GUI.
>>
>> I see that each local repository has a ./git/hooks directory.  Does a
>> hook have to be written in that directory to be triggered on commit and/or
>> push?
>> If so can the .git/hooks directory be accessed on github so a post-commit
>> hook could be added for this purpose?  This way it would be accessible for
>> anyone that clones the repository. Or is there a better way of doing this
>> such as using a .reviewboardrc file?
>>
>> Thanks.
>>
>> On Tue, Sep 24, 2019 at 2:51 AM Christian Hammond <
>> christ...@beanbaginc.com> wrote:
>>
>>> Hi Ron,
>>>
>>> The built-in WebHook support for GitHub is used to automatically close
>>> review requests when a commit referencing the review request ID is pushed
>>> to the repository. It's an incoming WebHook that GitHub can send to
>>> (providing GitHub has the ability to reach your server), but it's not
>>> designed for custom uses.
>>>
>>> It sounds like what you're looking to do is to have people post code for
>>> review by committing to the repository first? If so, that's what's
>>> generally referred to as a post-commit model, where the code is already in
>>> the codebase and is then going through review. A pre-commit model, where
>>> you post to Review Board first and only push to the repository after going
>>> through a successful review cycle, is recommended to ensure nothing slips
>>> through the cracks or ends up in the repository without approval.
>>>
>>> If you're needing some sort of custom e-mails to be sent out when
>>> activity happens on your GitHub repository, then that's going to require
>>> custom work. You'd need something (whether an independent script of your
>>> own creation written in your language of choice, or an extension to Review
>>> Board written in Python) that GitHub can HTTP POST to, and then you'd need
>>> to configure a new WebHook entry in GitHub to point to that. Your script
>>> could take that commit and post it for review, or e-mail people, or
>>> whatever you'd prefer.
>>>
>>> Review Board already does send 

Re: GitHub webhook to Reviewboard not working

[Ron T]

Christian,
When a user commits or pushes from a GUI editor to their local repository
which is a clone of their github repository, how do I get reviewboard to
send out a notification? In this case they are not running the rbt post
command because they are using a GUI.

I see that each local repository has a ./git/hooks directory.  Does a hook
have to be written in that directory to be triggered on commit and/or push?
If so can the .git/hooks directory be accessed on github so a post-commit
hook could be added for this purpose?  This way it would be accessible for
anyone that clones the repository. Or is there a better way of doing this
such as using a .reviewboardrc file?

Thanks.

On Tue, Sep 24, 2019 at 2:51 AM Christian Hammond 
wrote:

> Hi Ron,
>
> The built-in WebHook support for GitHub is used to automatically close
> review requests when a commit referencing the review request ID is pushed
> to the repository. It's an incoming WebHook that GitHub can send to
> (providing GitHub has the ability to reach your server), but it's not
> designed for custom uses.
>
> It sounds like what you're looking to do is to have people post code for
> review by committing to the repository first? If so, that's what's
> generally referred to as a post-commit model, where the code is already in
> the codebase and is then going through review. A pre-commit model, where
> you post to Review Board first and only push to the repository after going
> through a successful review cycle, is recommended to ensure nothing slips
> through the cracks or ends up in the repository without approval.
>
> If you're needing some sort of custom e-mails to be sent out when activity
> happens on your GitHub repository, then that's going to require custom
> work. You'd need something (whether an independent script of your own
> creation written in your language of choice, or an extension to Review
> Board written in Python) that GitHub can HTTP POST to, and then you'd need
> to configure a new WebHook entry in GitHub to point to that. Your script
> could take that commit and post it for review, or e-mail people, or
> whatever you'd prefer.
>
> Review Board already does send out e-mails to any reviewers (individual
> people or configured review groups) whenever there's a new review or reply
> on a review request. Is there a different type of notice you're looking
> for, like making a comment on the commit on GitHub? If so, your custom
> script/extension would do that.
>
> Christian
>
>
>
> On Thu, Sep 19, 2019 at 3:26 PM Ron A  wrote:
>
>> Hi, I have repository setup at github and it's linked to reviewboard 3.0
>> and I receive a 200 OK response.
>> The reviewboard server is on premise.
>>
>> I have followed the directions here
>> https://www.reviewboard.org/docs/manual/3.0/admin/configuration/repositories/github/
>> which seem to indicate once the webhook is inserted in the github
>> repostiory everything will work. The instructions don't seem to be complete.
>> "Then click *Add webhook*. You're done!"
>>
>> I would like to have reviewboard send out a review request with a link to
>> a diff when a person has made a commit to the github repository.
>> I would also like to have reviewboard send out a notice when someone has
>> reviewed a commit on reviewboard.
>> Is there a directory where a github webhook is located on the reviewboard
>> server?
>> Does the mydomain.com url below need to reference the webhook by name?
>>
>> The payload url is this according to the instructions.
>> https://mydomain.com/reviewboard/repos/3/github/hooks/close-submitted/
>>
>> Instructions say to include the information below when closing a commit.
>> Review Request #123
>>
>> I make a commit and push it to github but don't receive any notification.
>> Thanks, Ron
>>
>>
>>
>> --
>> 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
>> "Review Board Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to reviewboard+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/reviewboard/8c138fc3-9245-4867-8018-71862cef088e%40googlegroups.com
>> 
>> .
>>
>
>
> --
> 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 

Re: GitHub webhook to Reviewboard not working

[Ron T]

Hi Christian,
Yes the post-commit model is what I'd like to use. When I push to GitHub
from local workstation how do I have a notification sent out with a diff
from the on premise reviewboard server requesting a review of the code?

The only hooks directory is on the local working directory on the users
workstation at .gitHub/hooks

The reviewboard server is accessible from GitHub.

Thanks.

On Tue, Sep 24, 2019, 02:51 Christian Hammond 
wrote:

> Hi Ron,
>
> The built-in WebHook support for GitHub is used to automatically close
> review requests when a commit referencing the review request ID is pushed
> to the repository. It's an incoming WebHook that GitHub can send to
> (providing GitHub has the ability to reach your server), but it's not
> designed for custom uses.
>
> It sounds like what you're looking to do is to have people post code for
> review by committing to the repository first? If so, that's what's
> generally referred to as a post-commit model, where the code is already in
> the codebase and is then going through review. A pre-commit model, where
> you post to Review Board first and only push to the repository after going
> through a successful review cycle, is recommended to ensure nothing slips
> through the cracks or ends up in the repository without approval.
>
> If you're needing some sort of custom e-mails to be sent out when activity
> happens on your GitHub repository, then that's going to require custom
> work. You'd need something (whether an independent script of your own
> creation written in your language of choice, or an extension to Review
> Board written in Python) that GitHub can HTTP POST to, and then you'd need
> to configure a new WebHook entry in GitHub to point to that. Your script
> could take that commit and post it for review, or e-mail people, or
> whatever you'd prefer.
>
> Review Board already does send out e-mails to any reviewers (individual
> people or configured review groups) whenever there's a new review or reply
> on a review request. Is there a different type of notice you're looking
> for, like making a comment on the commit on GitHub? If so, your custom
> script/extension would do that.
>
> Christian
>
>
>
> On Thu, Sep 19, 2019 at 3:26 PM Ron A  wrote:
>
>> Hi, I have repository setup at github and it's linked to reviewboard 3.0
>> and I receive a 200 OK response.
>> The reviewboard server is on premise.
>>
>> I have followed the directions here
>> https://www.reviewboard.org/docs/manual/3.0/admin/configuration/repositories/github/
>> which seem to indicate once the webhook is inserted in the github
>> repostiory everything will work. The instructions don't seem to be complete.
>> "Then click *Add webhook*. You're done!"
>>
>> I would like to have reviewboard send out a review request with a link to
>> a diff when a person has made a commit to the github repository.
>> I would also like to have reviewboard send out a notice when someone has
>> reviewed a commit on reviewboard.
>> Is there a directory where a github webhook is located on the reviewboard
>> server?
>> Does the mydomain.com url below need to reference the webhook by name?
>>
>> The payload url is this according to the instructions.
>> https://mydomain.com/reviewboard/repos/3/github/hooks/close-submitted/
>>
>> Instructions say to include the information below when closing a commit.
>> Review Request #123
>>
>> I make a commit and push it to github but don't receive any notification.
>> Thanks, Ron
>>
>>
>>
>> --
>> 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
>> "Review Board Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to reviewboard+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/reviewboard/8c138fc3-9245-4867-8018-71862cef088e%40googlegroups.com
>> 
>> .
>>
>
>
> --
> 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 a topic in the
> Google Groups "Review Board Community" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/reviewboard/HNAm-l2vxLQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> 

Re: Something broke! (Error 500) Trouble copying reviewboard 3.0.15 to another server

[Ron T]

Thanks Christian. I think it was a secret key problem. The default
installation was working with an empty database but when the old database
was imported it broke.

On Tue, Sep 3, 2019, 12:46 Christian Hammond 
wrote:

> Gah I’m sorry, Ron. Can I blame autocorrect?
>
> Christian
>
>
> On Tue, Sep 3, 2019 at 12:46 Christian Hammond 
> wrote:
>
>> Hi Rob,
>>
>> Looks like your mod_wsgi setup isn’t enabled or working correctly, or you
>> have a default Apache vhost that’s conflicting with the Review Board one.
>> It shouldn’t be serving any files directly from our htdocs.
>>
>> Judging by the first error, you may also need to re-run `rb-site upgrade`
>> on the Review Board site directory in order to fix media links.
>>
>> Also, make sure you’re using the same SECRET_KEY in
>> conf/settings_local.py.
>>
>> Christian
>>
>>
>> On Mon, Sep 2, 2019 at 23:53 Ron T  wrote:
>>
>>> In addition this error is in the error log
>>> [autoindex:error] [pid 19085] [client 10.101.0.0:55445] AH01276: Cannot
>>> serve directory /www/reviewboard/htdocs/: No matching DirectoryIndex
>>> (index.html) found, and server-generated directory index forbidden by
>>> Options directive
>>>
>>> On Mon, Sep 2, 2019 at 11:42 PM Ron A  wrote:
>>>
>>>> I have a reviewboard 3.0.15 installation working on centos 7 and mysql.
>>>> I install a fresh installation of Reviewboard 3.0.15 on another server, it
>>>> works and I am able to login.  But when I import the mysql data into the
>>>> new reviewboard installation I receive all the errors below.
>>>> Any clues? Thanks!
>>>>
>>>> The website produces this error and the other errors are received from
>>>> email.
>>>> "It appears something broke when you tried to go to here. This is
>>>> either a bug in Review Board or a server configuration error. Please report
>>>> this to your administrator."
>>>>
>>>>
>>>> Traceback (most recent call last):
>>>> ..
>>>>
>>>>   File
>>>> "/usr/lib/python2.7/site-packages/django/contrib/staticfiles/storage.py",
>>>> line 96, in hashed_name
>>>> (clean_name, self))
>>>>
>>>> ValueError: The file 'djblets/js/jquery.gravy.min.j
>>>> s' could not be found with >>> object at 0x7efc06ec7390>.
>>>>
>>>>
>>>> >>> path:/reviewboard/account/login/,
>>>> GET:,
>>>> POST:,
>>>> COOKIES:{'collapsediffs': 'True',
>>>>  'csrftoken': 'Yu0qELEBn2aS0RaS93B9hPrERECnxqzg',
>>>>  'rbsessionid': '9etqxl8xc5wnyl0y8wh0051z6b30p8si'},
>>>> META:{'CONTEXT_DOCUMENT_ROOT': '/www/reviewboard/htdocs',
>>>>  'CONTEXT_PREFIX': '',
>>>>  u'CSRF_COOKIE': u'Yu0qELEBn2aS0RaS93B9hPrERECnxqzg',
>>>>  u'CSRF_COOKIE_USED': True,
>>>>  'DOCUMENT_ROOT': '/www/reviewboard/htdocs',
>>>>  'GATEWAY_INTERFACE': 'CGI/1.1',
>>>>  'HTTP_ACCEPT':
>>>> 'text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8',
>>>>  'HTTP_ACCEPT_ENCODING': 'gzip, deflate, br',
>>>>  'HTTP_ACCEPT_LANGUAGE': 'en-US,en;q=0.5',
>>>>  'HTTP_CONNECTION': 'keep-alive',
>>>>  'HTTP_COOKIE': 'rbsessionid=9etqxl8xc5wnyl0y8wh0051z6b30p8si;
>>>> csrftoken=Yu0qELEBn2aS0RaS93B9hPrERECnxqzg; collapsediffs=True',
>>>>  'HTTP_HOST': 'newhost,
>>>>  'HTTP_UPGRADE_INSECURE_REQUESTS': '1',
>>>>  'HTTP_USER_AGENT': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14;
>>>> rv:68.0) Gecko/20100101 Firefox/68.0',
>>>>  'PATH_INFO': u'/reviewboard/account/login/',
>>>>  'PATH_TRANSLATED':
>>>> '/www/reviewboard/htdocs/reviewboard.wsgi/reviewboard/account/login/',
>>>>  'QUERY_STRING': 'next=/reviewboard/',
>>>>  'REMOTE_ADDR': '192.168.16.10',
>>>>  'REMOTE_PORT': '55458',
>>>>  'REQUEST_METHOD': 'GET',
>>>>  'REQUEST_SCHEME': 'https',
>>>>  'REQUEST_URI': '/reviewboard/account/login/?next=/reviewboard/',
>>>>  'SCRIPT_FILENAME': '/www/reviewboard/htdocs/reviewboard.wsgi',
>>>>  'SCRIPT_NAME': u'',
>>>>  'SERVER_ADDR': '192.168.16.5',
>>>>  'SERVER_ADMIN': 'root@localhost',
>>>>  'SERVER_NAME': 'newhost.com <http://sa.flowplay.com>',
>>>>  'SERVER_PROTOCOL': 'HTTP/1.1',
>>>>  'SERVER_SIGNATURE': '',
>>>>  'SERVER_SOFTWARE': 'Apache/2.4.6 (

Re: Something broke! (Error 500) Trouble copying reviewboard 3.0.15 to another server

[Ron T]

In addition this error is in the error log
[autoindex:error] [pid 19085] [client 10.101.0.0:55445] AH01276: Cannot
serve directory /www/reviewboard/htdocs/: No matching DirectoryIndex
(index.html) found, and server-generated directory index forbidden by
Options directive

On Mon, Sep 2, 2019 at 11:42 PM Ron A  wrote:

> I have a reviewboard 3.0.15 installation working on centos 7 and mysql. I
> install a fresh installation of Reviewboard 3.0.15 on another server, it
> works and I am able to login.  But when I import the mysql data into the
> new reviewboard installation I receive all the errors below.
> Any clues? Thanks!
>
> The website produces this error and the other errors are received from
> email.
> "It appears something broke when you tried to go to here. This is either a
> bug in Review Board or a server configuration error. Please report this to
> your administrator."
>
>
> Traceback (most recent call last):
> ..
>
>   File
> "/usr/lib/python2.7/site-packages/django/contrib/staticfiles/storage.py",
> line 96, in hashed_name
> (clean_name, self))
>
> ValueError: The file 'djblets/js/jquery.gravy.min.j
> s' could not be found with  at 0x7efc06ec7390>.
>
>
>  path:/reviewboard/account/login/,
> GET:,
> POST:,
> COOKIES:{'collapsediffs': 'True',
>  'csrftoken': 'Yu0qELEBn2aS0RaS93B9hPrERECnxqzg',
>  'rbsessionid': '9etqxl8xc5wnyl0y8wh0051z6b30p8si'},
> META:{'CONTEXT_DOCUMENT_ROOT': '/www/reviewboard/htdocs',
>  'CONTEXT_PREFIX': '',
>  u'CSRF_COOKIE': u'Yu0qELEBn2aS0RaS93B9hPrERECnxqzg',
>  u'CSRF_COOKIE_USED': True,
>  'DOCUMENT_ROOT': '/www/reviewboard/htdocs',
>  'GATEWAY_INTERFACE': 'CGI/1.1',
>  'HTTP_ACCEPT':
> 'text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8',
>  'HTTP_ACCEPT_ENCODING': 'gzip, deflate, br',
>  'HTTP_ACCEPT_LANGUAGE': 'en-US,en;q=0.5',
>  'HTTP_CONNECTION': 'keep-alive',
>  'HTTP_COOKIE': 'rbsessionid=9etqxl8xc5wnyl0y8wh0051z6b30p8si;
> csrftoken=Yu0qELEBn2aS0RaS93B9hPrERECnxqzg; collapsediffs=True',
>  'HTTP_HOST': 'newhost,
>  'HTTP_UPGRADE_INSECURE_REQUESTS': '1',
>  'HTTP_USER_AGENT': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14;
> rv:68.0) Gecko/20100101 Firefox/68.0',
>  'PATH_INFO': u'/reviewboard/account/login/',
>  'PATH_TRANSLATED':
> '/www/reviewboard/htdocs/reviewboard.wsgi/reviewboard/account/login/',
>  'QUERY_STRING': 'next=/reviewboard/',
>  'REMOTE_ADDR': '192.168.16.10',
>  'REMOTE_PORT': '55458',
>  'REQUEST_METHOD': 'GET',
>  'REQUEST_SCHEME': 'https',
>  'REQUEST_URI': '/reviewboard/account/login/?next=/reviewboard/',
>  'SCRIPT_FILENAME': '/www/reviewboard/htdocs/reviewboard.wsgi',
>  'SCRIPT_NAME': u'',
>  'SERVER_ADDR': '192.168.16.5',
>  'SERVER_ADMIN': 'root@localhost',
>  'SERVER_NAME': 'newhost.com ',
>  'SERVER_PROTOCOL': 'HTTP/1.1',
>  'SERVER_SIGNATURE': '',
>  'SERVER_SOFTWARE': 'Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips
> mod_wsgi/3.4 Python/2.7.5 SVN/1.11.0',
>  'SSL_TLS_SNI': 'newhost.com ',
>  'UNIQUE_ID': 'XW3-w1j3wDZ4c9vjfZWO7AE',
>  'mod_wsgi.application_group': newhost.com|',
>  'mod_wsgi.callable_object': 'application',
>  'mod_wsgi.enable_sendfile': '0',
>  'mod_wsgi.handler_script': '',
>  'mod_wsgi.input_chunked': '0',
>  'mod_wsgi.listener_host': '0.0.0.0',
>  'mod_wsgi.process_group': '',
>  'mod_wsgi.queue_start': '1567489987154458',
>  'mod_wsgi.request_handler': 'wsgi-script',
>  'mod_wsgi.script_reloading': '1',
>  'mod_wsgi.version': (3, 4),
>  'wsgi.errors': ,
>  'wsgi.file_wrapper':  object at 0x7efc06eab7b0>,
>  'wsgi.input': ,
>
>  'wsgi.multiprocess': True,
>  'wsgi.multithread': False,
>  'wsgi.run_once': False,
>  'wsgi.url_scheme': u'https',
>  'wsgi.version': (1, 0)}>
>
> --
> 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 a topic in the
> Google Groups "Review Board Community" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/reviewboard/gaBZsnb24e8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> reviewboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/reviewboard/1ecbeb5d-f8b4-4392-9670-633a9ee82801%40googlegroups.com
> 
> .
>

-- 
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 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, 

Re: Reviewboard upgrade problem 1.7 to 3.0.14

[Ron T]

Hi Christian,
Yes I first attempted to upgrade to 3.x but it failed with:
The database error was: (1050, "Table
'reviews_reviewrequest_file_attachment_histories' already exists")
So I dropped the table and ran the upgrade again.
Then it  failed with the column issue below.
I dropped the database to start fresh.
Then I installed reviewboard 2.x, thinking it was a problem with the
versions being so far apart.
I ran the rb-site install sitename and things looked normal.
I then did a mysql import of the .sql data and got prompted to run the
upgrade command.  That ended up failing in the same way.

This last time after receiving your email I first dropped the database and
did a mysql import.
Then I installed reviewboard 3.0 again using pip install ReviewBoard==3.0.15
I did not run rb-site install sitename this time.
Then I got a prompt to upgrade the site so I upgraded the whole directory
and there were no errors! yay!
But the site looked odd with not all images resolving correctly. Looking at
the web source many links were pointing to an incorrect path.

The site information in reviewboard-home2/conf/apache-wsgi.conf didn't
match the information in the database that was imported so I had to do a
manual string replace in mysql siteconfig_siteconfiguration.settings to
update the database to the new reviewboard-home2 and reviewboard2 data.

UPDATE siteconfig_siteconfiguration set settings = replace(settings,
'reviewboard-home','reviewboard-home2');
UPDATE siteconfig_siteconfiguration set settings = replace(settings,
'reviewboard/static','reviewboard2/static');
UPDATE siteconfig_siteconfiguration set settings = replace(settings,
'reviewboard/media','reviewboard2/media');

Now it comes up fine.
Thanks for your help!

On Tue, Jun 11, 2019 at 9:26 PM Christian Hammond 
wrote:

> Hi Ron,
>
> This looks to me like there's state recorded that says some parts of the
> upgrade (perhaps to an earlier release, like a 2.0.x/2.5.x) was attempted,
> but that it never completed successfully, and it's now trying to resume
> from that bad state. Do you know anything about any attempted upgrades from
> the past?
>
> You might want to try completely dropping the new database and then
> importing the mysql one without letting Review Board create or populate the
> database at all, to make absolutely sure that you're not introducing some
> bad state there. Once you've imported, please run:
>
> rb-site manage /path/to/sitedir list-evolutions
>
> And show me the results. I can get a sense of whether my hunch is correct.
>
> We do offer database repair services as part of a support contract, or as
> a one-off job (billed per-hour). If the state's all wrong (and particularly
> if the database schema itself is in some half-upgraded state), then it
> requires a bit of work to undo. We're good at this, though, and can
> untangle this pretty fast. We can talk more about this in private, if
> you're interested.
>
> Christian
>
> On Tue, Jun 11, 2019 at 2:07 PM Ron A  wrote:
>
>> Hi, Posted this in the wrong group so am reposting to the Review Board
>> Community, thanks!
>>
>> On linux I have reviewboard 1.7 and an upgrading to 3.0.14 on a second
>> server.  3.0.14 was working fine on the second server but just with a base
>> install and an empty database created by the inital reviewboard
>> installation. I did a mysqldump of the data from 1.7 and then imported the
>> data to reviewboard 3.0.14. Upon accessing the 3.0.14 url I am prompted to
>> run the  rb-site upgrade  tool.
>>
>> During the upgrade I get this error below.  What steps should I take next
>> to resolve the error? Thanks!
>> Applying database evolutions for auth...
>> Applying database evolutions for contenttypes...
>> Applying database evolutions for accounts...
>> Database evolutions for accounts failed!
>> The SQL statement was: ALTER TABLE `accounts_profile` CHANGE COLUMN
>> `show_submitted` `show_closed` bool NOT NULL;
>> The database error was: (1054, "Unknown column 'show_submitted' in
>> 'accounts_profile'")
>> CommandError: Error applying evolution for accounts: (1054, "Unknown
>> column 'show_submitted' in 'accounts_profile'")
>>
>> --
>> 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
>> "Review Board Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to reviewboard+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/reviewboard/b6d41dc9-915b-4c4d-895a-9090c62c1383%40googlegroups.com
>> 
>> .
>> For more options, visit 

Reviewboard upgrade problem 1.7 to 3.0.14

[Ron T]

Hi, On linux I have reviewboard 1.7 and an upgrading to 3.0.14 on a second 
server.  3.0.14 is working fine on the second server but just with a base 
install and an empty database created by the inital reviewboard 
installation. I did a mysqldump of the data from 1.7 and then imported the 
data to reviewboard 3.0.14. Upon accessing the 3.0.14 url I am prompted to 
run the  rb-site upgrade  tool.

During the upgrade I get this error below.  What steps should I take next 
to resolve the error? Thanks!
Applying database evolutions for auth...
Applying database evolutions for contenttypes...
Applying database evolutions for accounts...
Database evolutions for accounts failed!
The SQL statement was: ALTER TABLE `accounts_profile` CHANGE COLUMN 
`show_submitted` `show_closed` bool NOT NULL;
The database error was: (1054, "Unknown column 'show_submitted' in 
'accounts_profile'")
CommandError: Error applying evolution for accounts: (1054, "Unknown column 
'show_submitted' in 'accounts_profile'")

-- 
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at https://groups.google.com/group/reviewboard-issues.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard-issues/60b524b1-ee12-4e33-8b92-4ab461472d38%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.