You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by CM...@jerviswebb.com on 2013/07/31 18:30:58 UTC
Upgrade procedure 0.5.8-->0.6
What is the procedure for updating an existing installation from 0.5.8 to 0.6?
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.
Re: Upgrade procedure 0.5.3-->0.6
Posted by Olemis Lang <ol...@gmail.com>.
On Mon, Sep 30, 2013 at 3:25 PM, Serge Bykov <dd...@yahoo.com> wrote:
> Yes, I deciphered that as being the intent, but maybe the default copying
> over of the page would help with making this more new-user friendly. I
> felt that I had to at least create default page before sharing the upgraded
> system with the team. Especially since when selecting a different product
> from the Dashboard / <products> drop down I am being redirected to the
> WikiStart page again, instead of staying in the tickets dashboard and
> refreshing it for the tickets of the selected product.
Product home page may be configured , if that's what you want ...
> I then have to click on the Tickets to get back to the tickets view. Not
> sure what is the logic for being sent to the wiki page when I'm clearly in
> the tickets view
The link points at product home page
> and just want to switch the product and see the tickets for the selected
> product?
>
>
...
--
Regards,
Olemis - @olemislc
Re: Upgrade procedure 0.5.3-->0.6
Posted by Gary Martin <ga...@wandisco.com>.
On 30/09/13 21:51, Joe Dreimann wrote:
>
>> On 30 Sep 2013, at 16:25, Serge Bykov <dd...@yahoo.com> wrote:
>>
>> Yes, I deciphered that as being the intent, but maybe the default copying over of the page would help with making this more new-user friendly. I felt that I had to at least create default page before sharing the upgraded system with the team. Especially since when selecting a different product from the Dashboard / <products> drop down I am being redirected to the WikiStart page again, instead of staying in the tickets dashboard and refreshing it for the tickets of the selected product. I then have to click on the Tickets to get back to the tickets view. Not sure what is the logic for being sent to the wiki page when I'm clearly in the tickets view and just want to switch the product and see the tickets for the selected product?
>>
>> Cheers,
>> Serge
> I wouldn't expect you to land on the Wiki Start page when you navigate to a product, but on the dashboard-style Product page. That would seem more helpful to me.
Yes, I think this would be better behaviour when navigating from a
ticket related view to a new product.
I think I have mentioned in another thread that I would like to see the
breadcrumb available throughout the system. Under that kind of setup I
would suggest that product switching should attempt to stay in the same
kind of page as was just left. At a minimum we could have:
* products/<src>/wik/path -> products/<dst>/wiki
* products/<src>/ticket_related_path -> products/<dst>/dashboard
It may be nice to take this further and allow any general
* products/<src>/<section>/path -> products/<dst>/<section>
There will be some values for <section> that will not have a matching
handler and so we may need to specify mappings and fall back to the
products/<dst> option for any that are not defined.
Cheers,
Gary
Re: Upgrade procedure 0.5.3-->0.6
Posted by Joe Dreimann <jo...@wandisco.com>.
> On 30 Sep 2013, at 16:25, Serge Bykov <dd...@yahoo.com> wrote:
>
> Yes, I deciphered that as being the intent, but maybe the default copying over of the page would help with making this more new-user friendly. I felt that I had to at least create default page before sharing the upgraded system with the team. Especially since when selecting a different product from the Dashboard / <products> drop down I am being redirected to the WikiStart page again, instead of staying in the tickets dashboard and refreshing it for the tickets of the selected product. I then have to click on the Tickets to get back to the tickets view. Not sure what is the logic for being sent to the wiki page when I'm clearly in the tickets view and just want to switch the product and see the tickets for the selected product?
>
> Cheers,
> Serge
I wouldn't expect you to land on the Wiki Start page when you navigate to a product, but on the dashboard-style Product page. That would seem more helpful to me.
- Joe
________________________
@jdreimann - Twitter
Sent from Harvard University campus
>
>
> ________________________________
> From: Olemis Lang <ol...@gmail.com>
> To: dev <de...@bloodhound.apache.org>; Serge Bykov <dd...@yahoo.com>
> Sent: Monday, September 30, 2013 4:15 PM
> Subject: Re: Upgrade procedure 0.5.3-->0.6
>
>
>> On Mon, Sep 30, 2013 at 3:07 PM, Serge Bykov <dd...@yahoo.com> wrote:
>>
>> Thanks Ryan.
>>
>> I've upgraded to 0.7 (from upgrade to 0.6) using the same method and all
>> seems to work now. The only nuisance which I quickly fixed, was that the
>> WikiStart pages were missing for each product, so I had to copy the default
>> one to each product
>
>
> We should be adding a product-specific WikiStart page for new products ...
> maybe including basic instructions on using products ?
>
> [...]
>
> --
> Regards,
>
> Olemis - @olemislc
Re: Upgrade procedure 0.5.3-->0.6
Posted by Serge Bykov <dd...@yahoo.com>.
Yes, I deciphered that as being the intent, but maybe the default copying over of the page would help with making this more new-user friendly. I felt that I had to at least create default page before sharing the upgraded system with the team. Especially since when selecting a different product from the Dashboard / <products> drop down I am being redirected to the WikiStart page again, instead of staying in the tickets dashboard and refreshing it for the tickets of the selected product. I then have to click on the Tickets to get back to the tickets view. Not sure what is the logic for being sent to the wiki page when I'm clearly in the tickets view and just want to switch the product and see the tickets for the selected product?
Cheers,
Serge
________________________________
From: Olemis Lang <ol...@gmail.com>
To: dev <de...@bloodhound.apache.org>; Serge Bykov <dd...@yahoo.com>
Sent: Monday, September 30, 2013 4:15 PM
Subject: Re: Upgrade procedure 0.5.3-->0.6
On Mon, Sep 30, 2013 at 3:07 PM, Serge Bykov <dd...@yahoo.com> wrote:
> Thanks Ryan.
>
> I've upgraded to 0.7 (from upgrade to 0.6) using the same method and all
> seems to work now. The only nuisance which I quickly fixed, was that the
> WikiStart pages were missing for each product, so I had to copy the default
> one to each product
We should be adding a product-specific WikiStart page for new products ...
maybe including basic instructions on using products ?
[...]
--
Regards,
Olemis - @olemislc
Re: Upgrade procedure 0.5.3-->0.6
Posted by Olemis Lang <ol...@gmail.com>.
On Mon, Sep 30, 2013 at 3:07 PM, Serge Bykov <dd...@yahoo.com> wrote:
> Thanks Ryan.
>
> I've upgraded to 0.7 (from upgrade to 0.6) using the same method and all
> seems to work now. The only nuisance which I quickly fixed, was that the
> WikiStart pages were missing for each product, so I had to copy the default
> one to each product
We should be adding a product-specific WikiStart page for new products ...
maybe including basic instructions on using products ?
[...]
--
Regards,
Olemis - @olemislc
Re: Upgrade procedure 0.5.3-->0.6
Posted by Serge Bykov <dd...@yahoo.com>.
Thanks Ryan.
I've upgraded to 0.7 (from upgrade to 0.6) using the same method and all seems to work now. The only nuisance which I quickly fixed, was that the WikiStart pages were missing for each product, so I had to copy the default one to each product and also fix the link to Product Admin as the link structure now just ends with /admin. The links to versions/components on the wikistart page were working as before.
Cheers,
Serge
________________________________
From: Ryan Ollos <ry...@wandisco.com>
To: "dev@bloodhound.apache.org" <de...@bloodhound.apache.org>; Serge Bykov <dd...@yahoo.com>
Sent: Monday, September 30, 2013 2:13 PM
Subject: Re: Upgrade procedure 0.5.3-->0.6
On Mon, Sep 30, 2013 at 10:59 AM, Serge Bykov <dd...@yahoo.com> wrote:
> Thanks Ryan.
>
> So should I repeat all the steps using the 0.7 code base or are some of my
> "upgrade" steps incorrect?
> Also, was there a need to go to 0.5.3 -> 0.6 ->0.7 or is it safe to
> upgrade to 0.7 directly?
>
> Cheers,
> Serge
I think your upgrade steps are okay. You are right, we need to document the
upgrade process. We also need to make it more obvious and straightforward
to upgrade, and I think that will involve changing the directory layout, as
discussed here:
http://markmail.org/message/j3sk7w2ye7ock4nm
Both of those items are on my near-term todo list.
We have no reason to think that you'll have a problem upgrading to 0.7
directly from 0.53. Make sure you have a backup of your environment and
database though.
Re: Upgrade procedure 0.5.3-->0.6
Posted by Ryan Ollos <ry...@wandisco.com>.
On Mon, Sep 30, 2013 at 10:59 AM, Serge Bykov <dd...@yahoo.com> wrote:
> Thanks Ryan.
>
> So should I repeat all the steps using the 0.7 code base or are some of my
> "upgrade" steps incorrect?
> Also, was there a need to go to 0.5.3 -> 0.6 ->0.7 or is it safe to
> upgrade to 0.7 directly?
>
> Cheers,
> Serge
I think your upgrade steps are okay. You are right, we need to document the
upgrade process. We also need to make it more obvious and straightforward
to upgrade, and I think that will involve changing the directory layout, as
discussed here:
http://markmail.org/message/j3sk7w2ye7ock4nm
Both of those items are on my near-term todo list.
We have no reason to think that you'll have a problem upgrading to 0.7
directly from 0.53. Make sure you have a backup of your environment and
database though.
Re: Upgrade procedure 0.5.3-->0.6
Posted by Serge Bykov <dd...@yahoo.com>.
Thanks Ryan.
So should I repeat all the steps using the 0.7 code base or are some of my "upgrade" steps incorrect?
Also, was there a need to go to 0.5.3 -> 0.6 ->0.7 or is it safe to upgrade to 0.7 directly?
Cheers,
Serge
________________________________
From: Ryan Ollos <ry...@wandisco.com>
To: "dev@bloodhound.apache.org" <de...@bloodhound.apache.org>; Serge Bykov <dd...@yahoo.com>
Sent: Monday, September 30, 2013 1:36 PM
Subject: Re: Upgrade procedure 0.5.3-->0.6
On Mon, Sep 30, 2013 at 10:30 AM, Serge Bykov <dd...@yahoo.com> wrote:
> 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?
>
There's a 0.7 version now, and I believe this issue is fixed in that
version.
Re: Upgrade procedure 0.5.3-->0.6
Posted by Ryan Ollos <ry...@wandisco.com>.
On Mon, Sep 30, 2013 at 10:30 AM, Serge Bykov <dd...@yahoo.com> wrote:
> 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?
>
There's a 0.7 version now, and I believe this issue is fixed in that
version.
Re: Upgrade procedure 0.5.3-->0.6
Posted by Serge Bykov <dd...@yahoo.com>.
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č <ma...@digiverse.si>
To: dev@bloodhound.apache.org
Sent: Thursday, August 1, 2013 8:00 AM
Subject: Re: Upgrade procedure 0.5.8-->0.6
On 31. Jul, 2013, at 18:30, <CM...@jerviswebb.com> <CM...@jerviswebb.com> 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.
Re: Upgrade procedure 0.5.8-->0.6
Posted by Matevž Bradač <ma...@digiverse.si>.
On 31. Jul, 2013, at 18:30, <CM...@jerviswebb.com> <CM...@jerviswebb.com> 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.