Hi.

I finally got the bravery to try this out and generally it went OK but after 
doing some testing I found that the Create Ticket function throws an exception 
in the upgraded system.  I've upgraded 0.5.3 to 0.6 using the following steps, 
so please let me know if I did something wrong and perhaps it would be good to 
have some instructions on the bloodhound upgrade site on how to actually do 
this step by step:

deleted  the following folders in 0.5.3 root:

bloodhound_dashboard
bloodhound_multiproduct
bloodhound_search
bloodhound_them
doc
trac
.rat-ignore
DISCLAIMER
LICENSE
NOTICE
README
RELEASE_NOTES

\installer\createdigest.pyc

Then replaced with the version from 0.6

\installer\bloodhound_setup.py
\installer\createdigest.py
\installer\pgrequirements.txt
\installer\README.rst
\installer\requirements.txt
\installer\requirements-dev.txt
\installer\tests

And then copied the following from 0.6 zip into my bloodhound home directory
bloodhound_dasbhbaord
bloodhound_multiproduct
bloodhound_relations
bloodhound_search
bloodhound_theme
doc
trac
.rat-ignore
DISCLAIMER
LICENSE
NOTICE
README
RELEASE_NO

Then ran the following commands:

>bloodhound\Scripts\activate.bat

>trac-admin bloodhound\environments\MyEnvName upgrade

>trac-admin bloodhound\environments\MyEnvName wiki upgrade

This did not lead to any changes to tired to the following:

>pip install -r requirements.txt

Then noticed some info message saying that "run upgrade" and did the following:


>pip install --upgrade -r requirements.txt

After everythign completed, the home page showed an error and told me to run 
the upgrade:

>trac-admin 
>c:\opt\apache-bloodhound-0.5.3\installer\bloodhound\environments\MyEnvName 
>upgrade

>trac-admin 
>c:\opt\apache-bloodhound-0.5.3\installer\bloodhound\environments\MyEnvName 
>wiki upgrade

All ok, restarted Apache and site is up. Besides few missing wiki pages the 
main issue was failure to create the ticket in both short and full dialogs.  
The error in the log is:|

2013-09-30 13:19:21,674 Trac[loader] ERROR: Skipping 
"bhrelations.widgets.ticketrelations = bhrelations.widgets.relations": 
Traceback (most recent call last):
  File 
"C:\opt\apache-bloodhound-0.5.3\installer\bloodhound\Lib\site-packages\trac\loader.py",
 line 68, in _load_eggs
    entry.load(require=True)
  File 
"C:\opt\apache-bloodhound-0.5.3\installer\bloodhound\Lib\site-packages\pkg_resources.py",
 line 2108, in load
    entry = __import__(self.module_name, globals(),globals(), ['__name__'])
ImportError: No module named widgets.relations
2013-09-30 13:19:21,838 Trac[env] WARNING: Inheriting parent logger for product 
'@'
2013-09-30 13:19:21,848 Trac[env] WARNING: Inheriting parent logger for product 
'TestProduct1'
2013-09-30 13:19:21,855 Trac[env] WARNING: Inheriting parent logger for product 
'MyInternalFramework'
2013-09-30 13:19:21,871 Trac[env] WARNING: Inheriting parent logger for product 
'MyMODULES'
2013-09-30 13:19:21,881 Trac[env] WARNING: Inheriting parent logger for product 
'MyUtilityApp'
2013-09-30 13:19:21,934 Trac[env] WARNING: base_url option not set in 
configuration, generated links may be incorrect
2013-09-30 13:19:21,951 Trac[api] WARNING: Unable to find repository 
'(default)' for synchronization
2013-09-30 13:19:40,098 Trac[env] WARNING: product_base_url option not set in 
configuration, generated links may be incorrect
2013-09-30 13:19:40,121 Trac[api] WARNING: Unable to find repository 
'(default)' for synchronization
2013-09-30 13:19:40,160 Trac[theme] ERROR: BH: Quick create ticket failed 
column "product" specified more than once
LINE 1: ...atus,priority,product,resolution,time,changetime, product) V...
                                                             ^
Traceback (most recent call last):
  File 
"C:\opt\apache-bloodhound-0.5.3\installer\bloodhound\Lib\site-packages\bhtheme\theme.py",
 line 519, in process_request
    product, tid = self.create(req, summary, desc, attrs, True)
  File 
"C:\opt\apache-bloodhound-0.5.3\installer\bloodhound\Lib\site-packages\bhtheme\theme.py",
 line 552, in create
    t.insert()
  File 
"C:\opt\apache-bloodhound-0.5.3\installer\bloodhound\Lib\site-packages\trac\ticket\model.py",
 line 241, in insert
    [values[name] for name in std_fields])
  File 
"C:\opt\apache-bloodhound-0.5.3\installer\bloodhound\Lib\site-packages\multiproduct\dbcursor.py",
 line 143, in execute
    return self.cursor.execute(sql, args=args)
  File 
"C:\opt\apache-bloodhound-0.5.3\installer\bloodhound\Lib\site-packages\multiproduct\dbcursor.py",
 line 83, in execute
    return super(BloodhoundIterableCursor, 
self).execute(translate_sql(self.env, sql), args=args)
  File 
"C:\opt\apache-bloodhound-0.5.3\installer\bloodhound\Lib\site-packages\trac\db\util.py",
 line 65, in execute
    return self.cursor.execute(sql_escape_percent(sql), args)
ProgrammingError: column "product" specified more than once
LINE 1: ...atus,priority,product,resolution,time,changetime, product) V...
                                                             ^

Any thoughts on what may be wrong?

Thanks a lot!
Serge


________________________________
 From: Matevž Bradač <[email protected]>
To: [email protected] 
Sent: Thursday, August 1, 2013 8:00 AM
Subject: Re: Upgrade procedure 0.5.8-->0.6
 


On 31. Jul, 2013, at 18:30, <[email protected]> <[email protected]> 
wrote:

> What is the procedure for updating an existing installation from 0.5.8 to 0.6?

The procedure is similar to trac upgrades:
1. upgrade the code (extract/replace the old code with the new version)
2. upgrade the environment:
  trac-admin <path_to_environment> upgrade
3. upgrade the wiki:
  trac-admin <path_to_environment> wiki upgrade
4. restart the server

Note that existing tickets that were not bound to any product in 0.5.3
will be moved to a default product in 0.6.

--
matevz

> 
> Christopher Murphy, Vice President
> Jervis B. Webb Company, 34375 W. Twelve Mile Road, Farmington Hills, MI  48331
> 248.521.8704
> 
> DAIFUKU WEBB
> Always an Edge Ahead
> 
> PRIVACY NOTICE: The information contained in this e-mail, including any 
> attachments, is confidential and intended only for the named recipient(s). 
> Unauthorized use, disclosure, forwarding, or copying is strictly prohibited 
> and may be unlawful. If you are not the intended recipient, please delete the 
> e-mail and any attachments and notify us immediately by return e-mail.

Reply via email to