Re: migration of 1.5.5

[Roman Klaiber]

Hi Christian,

I just installed it via yum and that is the version I got.
Is the version 3 of RB not yet in the official repositories?

Roman

Am Freitag, 23. März 2018 22:07:33 UTC+1 schrieb Christian Hammond:
>
> Hi Roman,
>
> We have a bug in the migration code. I have a (tentative) fix, but it will 
> require a patch on top of Review Board 3.0.5. Is there a reason you want to 
> upgrade to 2.5 specifically?
>
> Christian
>
> On Thu, Mar 22, 2018 at 8:47 AM, Roman Klaiber  > wrote:
>
>> Hi Christian,
>>
>> thanks for your help but now I am stuck at the next point.
>> I did import the mysql dump and copied the complete site
>> But when I try to run the upgrade it gives me the error that the database 
>> is not defined
>>
>> Thanks and best regards,
>> Roman
>>
>>
>> [root@sas-srv-reviewboard conf]# rb-site upgrade /var/www/review_board/
>> Traceback (most recent call last):
>>   File "/bin/rb-site", line 9, in 
>> load_entry_point('ReviewBoard==2.5.17', 'console_scripts', 
>> 'rb-site')()
>>   File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py", 
>> line 1964, in main
>> command.run()
>>   File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py", 
>> line 1740, in run
>> diff_dedup_needed = site.get_diff_dedup_needed()
>>   File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py", 
>> line 512, in get_diff_dedup_needed
>> from reviewboard.diffviewer.models import FileDiff
>>   File 
>> "/usr/lib/python2.7/site-packages/reviewboard/diffviewer/models.py", line 
>> 6, in 
>> from django.db import models
>>   File "/usr/lib/python2.7/site-packages/django/db/models/__init__.py", 
>> line 5, in 
>> from django.db.models.query import Q
>>   File "/usr/lib/python2.7/site-packages/django/db/models/query.py", line 
>> 17, in 
>> from django.db.models.deletion import Collector
>>   File "/usr/lib/python2.7/site-packages/django/db/models/deletion.py", 
>> line 4, in 
>> from django.db.models import signals, sql
>>   File 
>> "/usr/lib/python2.7/site-packages/django/db/models/sql/__init__.py", line 
>> 4, in 
>> from django.db.models.sql.subqueries import *
>>   File 
>> "/usr/lib/python2.7/site-packages/django/db/models/sql/subqueries.py", line 
>> 12, in 
>> from django.db.models.sql.query import Query
>>   File "/usr/lib/python2.7/site-packages/django/db/models/sql/query.py", 
>> line 22, in 
>> from django.db.models.sql import aggregates as base_aggregates_module
>>   File 
>> "/usr/lib/python2.7/site-packages/django/db/models/sql/aggregates.py", line 
>> 9, in 
>> ordinal_aggregate_field = IntegerField()
>>   File 
>> "/usr/lib/python2.7/site-packages/django/db/models/fields/__init__.py", 
>> line 116, in __init__
>> self.db_tablespace = db_tablespace or 
>> settings.DEFAULT_INDEX_TABLESPACE
>>   File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 
>> 54, in __getattr__
>> self._setup(name)
>>   File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 
>> 49, in _setup
>> self._wrapped = Settings(settings_module)
>>   File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 
>> 128, in __init__
>> mod = importlib.import_module(self.SETTINGS_MODULE)
>>   File "/usr/lib/python2.7/site-packages/django/utils/importlib.py", line 
>> 40, in import_module
>> __import__(name)
>>   File "/usr/lib/python2.7/site-packages/reviewboard/settings.py", line 
>> 308, in 
>> for db_info in DATABASES.values():
>> NameError: name 'DATABASES' is not defined
>>
>>
>>
>> Am Montag, 19. März 2018 21:58:53 UTC+1 schrieb Christian Hammond:
>>>
>>> Hi Roman,
>>>
>>> You should be able to load the MySQL dump into a new server, copy over 
>>> the site directory, install the new version of Review Board, and do a 
>>> 'rb-site upgrade' on the site directory. Provided there are no custom 
>>> modifications to the old database schema, it should do the upgrade 
>>> correctly. (Keep that database dump around though in case things fail.)
>>>
>>> A common issue on MySQL is that newer versions use a different table 
>>> format, which will break upgrades. Your database dump is likely using 
>>> MyISAM tables, while newer versions are likely going to use InnoDB. To get 
>>> the upgrade to work, you'll probably need to edit the database dump file 
>>> and replace any MyISAM references with InnoDB.
>>>
>>> If things do go wrong, or you want some one-on-one assistance while 
>>> doing this, we offer Premium Support contracts that covers (amongst other 
>>> things) custom modifications to databases and evolution history for older 
>>> deployments that have trouble upgrading. Having trouble is *not* the norm, 
>>> but it sometimes happens when using older versions for a variety of reasons 
>>> (particularly if there are any modifications), and we can help with that 
>>> and any other issues that come up. Completely optional, but if you're 
>>> interested, I can reach out 

Re: migration of 1.5.5

[Christian Hammond]

Hi Roman,

We have a bug in the migration code. I have a (tentative) fix, but it will
require a patch on top of Review Board 3.0.5. Is there a reason you want to
upgrade to 2.5 specifically?

Christian

On Thu, Mar 22, 2018 at 8:47 AM, Roman Klaiber 
wrote:

> Hi Christian,
>
> thanks for your help but now I am stuck at the next point.
> I did import the mysql dump and copied the complete site
> But when I try to run the upgrade it gives me the error that the database
> is not defined
>
> Thanks and best regards,
> Roman
>
>
> [root@sas-srv-reviewboard conf]# rb-site upgrade /var/www/review_board/
> Traceback (most recent call last):
>   File "/bin/rb-site", line 9, in 
> load_entry_point('ReviewBoard==2.5.17', 'console_scripts',
> 'rb-site')()
>   File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py",
> line 1964, in main
> command.run()
>   File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py",
> line 1740, in run
> diff_dedup_needed = site.get_diff_dedup_needed()
>   File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py",
> line 512, in get_diff_dedup_needed
> from reviewboard.diffviewer.models import FileDiff
>   File "/usr/lib/python2.7/site-packages/reviewboard/diffviewer/models.py",
> line 6, in 
> from django.db import models
>   File "/usr/lib/python2.7/site-packages/django/db/models/__init__.py",
> line 5, in 
> from django.db.models.query import Q
>   File "/usr/lib/python2.7/site-packages/django/db/models/query.py", line
> 17, in 
> from django.db.models.deletion import Collector
>   File "/usr/lib/python2.7/site-packages/django/db/models/deletion.py",
> line 4, in 
> from django.db.models import signals, sql
>   File "/usr/lib/python2.7/site-packages/django/db/models/sql/__init__.py",
> line 4, in 
> from django.db.models.sql.subqueries import *
>   File "/usr/lib/python2.7/site-packages/django/db/models/sql/subqueries.py",
> line 12, in 
> from django.db.models.sql.query import Query
>   File "/usr/lib/python2.7/site-packages/django/db/models/sql/query.py",
> line 22, in 
> from django.db.models.sql import aggregates as base_aggregates_module
>   File "/usr/lib/python2.7/site-packages/django/db/models/sql/aggregates.py",
> line 9, in 
> ordinal_aggregate_field = IntegerField()
>   File "/usr/lib/python2.7/site-packages/django/db/models/fields/__init__.py",
> line 116, in __init__
> self.db_tablespace = db_tablespace or settings.DEFAULT_INDEX_
> TABLESPACE
>   File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line
> 54, in __getattr__
> self._setup(name)
>   File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line
> 49, in _setup
> self._wrapped = Settings(settings_module)
>   File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line
> 128, in __init__
> mod = importlib.import_module(self.SETTINGS_MODULE)
>   File "/usr/lib/python2.7/site-packages/django/utils/importlib.py", line
> 40, in import_module
> __import__(name)
>   File "/usr/lib/python2.7/site-packages/reviewboard/settings.py", line
> 308, in 
> for db_info in DATABASES.values():
> NameError: name 'DATABASES' is not defined
>
>
>
> Am Montag, 19. März 2018 21:58:53 UTC+1 schrieb Christian Hammond:
>>
>> Hi Roman,
>>
>> You should be able to load the MySQL dump into a new server, copy over
>> the site directory, install the new version of Review Board, and do a
>> 'rb-site upgrade' on the site directory. Provided there are no custom
>> modifications to the old database schema, it should do the upgrade
>> correctly. (Keep that database dump around though in case things fail.)
>>
>> A common issue on MySQL is that newer versions use a different table
>> format, which will break upgrades. Your database dump is likely using
>> MyISAM tables, while newer versions are likely going to use InnoDB. To get
>> the upgrade to work, you'll probably need to edit the database dump file
>> and replace any MyISAM references with InnoDB.
>>
>> If things do go wrong, or you want some one-on-one assistance while doing
>> this, we offer Premium Support contracts that covers (amongst other things)
>> custom modifications to databases and evolution history for older
>> deployments that have trouble upgrading. Having trouble is *not* the norm,
>> but it sometimes happens when using older versions for a variety of reasons
>> (particularly if there are any modifications), and we can help with that
>> and any other issues that come up. Completely optional, but if you're
>> interested, I can reach out privately with more information.
>>
>> Christian
>>
>>
>> On Fri, Mar 16, 2018 at 4:36 AM, Roman Klaiber 
>> wrote:
>>
>>> Hi,
>>>
>>> we have a RB 1.5.5 on an Ubuntu 10.04 running. This should be migrated
>>> to a new server.
>>> The goal is to have the RB running on a VM with the newest version.
>>> As this is used daily by our development department, I can 

Re: migration of 1.5.5

[Roman Klaiber]

Hi Christian,

thanks for your help but now I am stuck at the next point.
I did import the mysql dump and copied the complete site
But when I try to run the upgrade it gives me the error that the database 
is not defined

Thanks and best regards,
Roman


[root@sas-srv-reviewboard conf]# rb-site upgrade /var/www/review_board/
Traceback (most recent call last):
  File "/bin/rb-site", line 9, in 
load_entry_point('ReviewBoard==2.5.17', 'console_scripts', 'rb-site')()
  File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py", 
line 1964, in main
command.run()
  File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py", 
line 1740, in run
diff_dedup_needed = site.get_diff_dedup_needed()
  File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py", 
line 512, in get_diff_dedup_needed
from reviewboard.diffviewer.models import FileDiff
  File "/usr/lib/python2.7/site-packages/reviewboard/diffviewer/models.py", 
line 6, in 
from django.db import models
  File "/usr/lib/python2.7/site-packages/django/db/models/__init__.py", 
line 5, in 
from django.db.models.query import Q
  File "/usr/lib/python2.7/site-packages/django/db/models/query.py", line 
17, in 
from django.db.models.deletion import Collector
  File "/usr/lib/python2.7/site-packages/django/db/models/deletion.py", 
line 4, in 
from django.db.models import signals, sql
  File "/usr/lib/python2.7/site-packages/django/db/models/sql/__init__.py", 
line 4, in 
from django.db.models.sql.subqueries import *
  File 
"/usr/lib/python2.7/site-packages/django/db/models/sql/subqueries.py", line 
12, in 
from django.db.models.sql.query import Query
  File "/usr/lib/python2.7/site-packages/django/db/models/sql/query.py", 
line 22, in 
from django.db.models.sql import aggregates as base_aggregates_module
  File 
"/usr/lib/python2.7/site-packages/django/db/models/sql/aggregates.py", line 
9, in 
ordinal_aggregate_field = IntegerField()
  File 
"/usr/lib/python2.7/site-packages/django/db/models/fields/__init__.py", 
line 116, in __init__
self.db_tablespace = db_tablespace or settings.DEFAULT_INDEX_TABLESPACE
  File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 54, 
in __getattr__
self._setup(name)
  File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 49, 
in _setup
self._wrapped = Settings(settings_module)
  File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 
128, in __init__
mod = importlib.import_module(self.SETTINGS_MODULE)
  File "/usr/lib/python2.7/site-packages/django/utils/importlib.py", line 
40, in import_module
__import__(name)
  File "/usr/lib/python2.7/site-packages/reviewboard/settings.py", line 
308, in 
for db_info in DATABASES.values():
NameError: name 'DATABASES' is not defined



Am Montag, 19. März 2018 21:58:53 UTC+1 schrieb Christian Hammond:
>
> Hi Roman,
>
> You should be able to load the MySQL dump into a new server, copy over the 
> site directory, install the new version of Review Board, and do a 'rb-site 
> upgrade' on the site directory. Provided there are no custom modifications 
> to the old database schema, it should do the upgrade correctly. (Keep that 
> database dump around though in case things fail.)
>
> A common issue on MySQL is that newer versions use a different table 
> format, which will break upgrades. Your database dump is likely using 
> MyISAM tables, while newer versions are likely going to use InnoDB. To get 
> the upgrade to work, you'll probably need to edit the database dump file 
> and replace any MyISAM references with InnoDB.
>
> If things do go wrong, or you want some one-on-one assistance while doing 
> this, we offer Premium Support contracts that covers (amongst other things) 
> custom modifications to databases and evolution history for older 
> deployments that have trouble upgrading. Having trouble is *not* the norm, 
> but it sometimes happens when using older versions for a variety of reasons 
> (particularly if there are any modifications), and we can help with that 
> and any other issues that come up. Completely optional, but if you're 
> interested, I can reach out privately with more information.
>
> Christian
>
>
> On Fri, Mar 16, 2018 at 4:36 AM, Roman Klaiber  > wrote:
>
>> Hi,
>>
>> we have a RB 1.5.5 on an Ubuntu 10.04 running. This should be migrated to 
>> a new server.
>> The goal is to have the RB running on a VM with the newest version.
>> As this is used daily by our development department, I can not shutdown 
>> the server for a longer time.
>>
>> I tried to setup the 1.5.5 on a fresh installed CentOS 7 as well on an 
>> old Centos 6.4 but failed to install the RB
>> I tried to convert the machine completely with VMware Converter but 
>> unfortunately this failed (I think the LVM version is too old and therefor 
>> I can not start the VM)
>>
>> What would happen if I load the mysql dump from the 1.5.5 into a 

Re: migration of 1.5.5

[Christian Hammond]

Hi Roman,

You should be able to load the MySQL dump into a new server, copy over the
site directory, install the new version of Review Board, and do a 'rb-site
upgrade' on the site directory. Provided there are no custom modifications
to the old database schema, it should do the upgrade correctly. (Keep that
database dump around though in case things fail.)

A common issue on MySQL is that newer versions use a different table
format, which will break upgrades. Your database dump is likely using
MyISAM tables, while newer versions are likely going to use InnoDB. To get
the upgrade to work, you'll probably need to edit the database dump file
and replace any MyISAM references with InnoDB.

If things do go wrong, or you want some one-on-one assistance while doing
this, we offer Premium Support contracts that covers (amongst other things)
custom modifications to databases and evolution history for older
deployments that have trouble upgrading. Having trouble is *not* the norm,
but it sometimes happens when using older versions for a variety of reasons
(particularly if there are any modifications), and we can help with that
and any other issues that come up. Completely optional, but if you're
interested, I can reach out privately with more information.

Christian


On Fri, Mar 16, 2018 at 4:36 AM, Roman Klaiber 
wrote:

> Hi,
>
> we have a RB 1.5.5 on an Ubuntu 10.04 running. This should be migrated to
> a new server.
> The goal is to have the RB running on a VM with the newest version.
> As this is used daily by our development department, I can not shutdown
> the server for a longer time.
>
> I tried to setup the 1.5.5 on a fresh installed CentOS 7 as well on an old
> Centos 6.4 but failed to install the RB
> I tried to convert the machine completely with VMware Converter but
> unfortunately this failed (I think the LVM version is too old and therefor
> I can not start the VM)
>
> What would happen if I load the mysql dump from the 1.5.5 into a newer
> version?
>
> What would be the best way to migrate the RB or do a fresh installation
> but migrating the data from the existing one?
>
> As I am stuck at this point I highly appreciate any help
>
>
> Thanks
> Roman
>
> --
> 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.
> 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 
"Review Board Community" 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.