Re: Quick runup: plugin installation?
Thanks Ryan! For future reference, the following procedure worked: 1) grabbed the source zip 2) decompressed 3) accessed the directory with the setup.py (that I wished to install) 4) ran the following: python setup.py bdist_egg 5) located the `.egg` file in the ./dist/ directory 6) copied the `.egg` into the plugins directory located ./installer/bloodhound/environments/main/plugins 7) stopped the server that's handling trac/bloodhound 8) the plugin is now listed in admin> General/plugins where I checked off the options I'd like to enable. 9) In my case (being the trac.ini Editor https://trac-hacks.org/wiki/TracIniAdminPanelPlugin ), there appeared a menu entry on the admin> General menu. Could I have also just used the Bloodhound web UI to install the .egg file? What else would this have done other than copying the .egg file into the plugins directory? Thanks! Matt On Wed, Mar 18, 2015 at 4:03 PM, Ryan J Ollos wrote: > On Wed, Mar 18, 2015 at 12:22 PM, Matt Brown > wrote: > >> Hello all, >> >> I'm new to both trac and bloodhound. >> >> I'm in process of attempting to host Bloodhound on IIS7.5 through >> http://trac.edgewall.org/wiki/TracOnWindowsIisIsapi without luck (I just >> stalked Seb on twitter, so maybe that will help). But I'll get to this >> later. >> >> >> Regardless, I'd like to go ahead with some plugin installations and >> wanted a better understanding of how to install plugins. >> >> I'm specifically interested in LDAP authentication straight away (I'm >> hoping to leverage NTLM/kerberos for transparent logon from a user's >> browser... is this possible?). In my search, I came across two add-ins >> that would likely help me quickly administer some options: >> https://trac-hacks.org/wiki/IniAdminPlugin >> https://trac-hacks.org/wiki/TracIniAdminPanelPlugin >> >> TracIniAdminPanelPlugin seems to be preferred. Given that plugin, how >> can I go ahead with the installation? Should I pop it into the plugins dir >> (,,/installer/bloodhound/environments/main/plugins)? Or should I use the >> handy web UI? If so, which file should I place there? There doesn't >> appear to be a .egg available. >> >> >> Any assistance is appreciated. >> >> >> Thanks, >> >> Matt >> > > > Best to start by reading the TracPlugins page, and let us know if you have > any questions: > http://trac.edgewall.org/wiki/TracPlugins >
Re: Quick runup: plugin installation?
Also for reference, _a_ list of plugins is available: http://trac-hacks.org/browser On Thu, Mar 19, 2015 at 8:34 AM, Matt Brown wrote: > Thanks Ryan! > > For future reference, the following procedure worked: > > 1) grabbed the source zip > 2) decompressed > 3) accessed the directory with the setup.py (that I wished to install) > 4) ran the following: > > python setup.py bdist_egg > > 5) located the `.egg` file in the ./dist/ directory > 6) copied the `.egg` into the plugins directory located > ./installer/bloodhound/environments/main/plugins > 7) stopped the server that's handling trac/bloodhound > 8) the plugin is now listed in admin> General/plugins where I checked off > the options I'd like to enable. > 9) In my case (being the trac.ini Editor > https://trac-hacks.org/wiki/TracIniAdminPanelPlugin ), there appeared a > menu entry on the admin> General menu. > > > Could I have also just used the Bloodhound web UI to install the .egg > file? What else would this have done other than copying the .egg file into > the plugins directory? > > > Thanks! > > Matt > > > > On Wed, Mar 18, 2015 at 4:03 PM, Ryan J Ollos wrote: > >> On Wed, Mar 18, 2015 at 12:22 PM, Matt Brown >> wrote: >> >>> Hello all, >>> >>> I'm new to both trac and bloodhound. >>> >>> I'm in process of attempting to host Bloodhound on IIS7.5 through >>> http://trac.edgewall.org/wiki/TracOnWindowsIisIsapi without luck (I >>> just stalked Seb on twitter, so maybe that will help). But I'll get to >>> this later. >>> >>> >>> Regardless, I'd like to go ahead with some plugin installations and >>> wanted a better understanding of how to install plugins. >>> >>> I'm specifically interested in LDAP authentication straight away (I'm >>> hoping to leverage NTLM/kerberos for transparent logon from a user's >>> browser... is this possible?). In my search, I came across two add-ins >>> that would likely help me quickly administer some options: >>> https://trac-hacks.org/wiki/IniAdminPlugin >>> https://trac-hacks.org/wiki/TracIniAdminPanelPlugin >>> >>> TracIniAdminPanelPlugin seems to be preferred. Given that plugin, how >>> can I go ahead with the installation? Should I pop it into the plugins dir >>> (,,/installer/bloodhound/environments/main/plugins)? Or should I use the >>> handy web UI? If so, which file should I place there? There doesn't >>> appear to be a .egg available. >>> >>> >>> Any assistance is appreciated. >>> >>> >>> Thanks, >>> >>> Matt >>> >> >> >> Best to start by reading the TracPlugins page, and let us know if you >> have any questions: >> http://trac.edgewall.org/wiki/TracPlugins >> > >
PostgreSQL IntegrityError upgrading BH from v0.5 to v0.8
Hello, I've been trying to upgrade Bloodhound from v0.5 to v0.8. I also tried upgrading from v0.5 to v0.7 and get the same error below. I followed the instructions at https://issues.apache.org/bloodhound/wiki/BloodhoundUpgrade. The version of PostgreSQL I'm using is 9.1.5 and I'm running on Ubuntu 12.04 with Python 2.7.3. Error I get: (bloodhound)root@vcs01:/srv/webapps/bloodhound# trac-admin apache-bloodhound/installer/bloodhound/environments/knack upgrade The upgrade failed. Please fix the issue and try again. IntegrityError: duplicate key value violates unique constraint "permission_pk" DETAIL: Key (username, action, product)=(authenticated, PRODUCT_VIEW, art) already exists. I've checked trac mailing list archives and BH mailing list archives as well as tickets in BH, but I wasn't able to find any solution. Does anyone know how to get past this? Thanks, Vijay p.s. I tried to find BH v0.6 to try and upgrade to, but it's not available anywhere.
Re: upgrading to 0.8
Well, I tried a fresh install and compared the .ini files. I tried to match my old .ini files to the new ones as much as possible and that seems to have corrected the problem. I guess the main issue is there's no method of upgrading the .ini files when upgrading to a newer version. In previous upgrades I had just made sure that paths were changed. I guess I must have accumulated some setting from a previous version (I think my starting version was 0.5.3) that caused the issues in 0.8.
Re: Quick runup: plugin installation?
On Thu, Mar 19, 2015 at 5:34 AM, Matt Brown wrote: > Thanks Ryan! > > For future reference, the following procedure worked: > > 1) grabbed the source zip > 2) decompressed > 3) accessed the directory with the setup.py (that I wished to install) > 4) ran the following: > > python setup.py bdist_egg > > 5) located the `.egg` file in the ./dist/ directory > 6) copied the `.egg` into the plugins directory located > ./installer/bloodhound/environments/main/plugins > 7) stopped the server that's handling trac/bloodhound > 8) the plugin is now listed in admin> General/plugins where I checked off > the options I'd like to enable. > 9) In my case (being the trac.ini Editor > https://trac-hacks.org/wiki/TracIniAdminPanelPlugin ), there appeared a > menu entry on the admin> General menu. > > > Could I have also just used the Bloodhound web UI to install the .egg > file? What else would this have done other than copying the .egg file into > the plugins directory? > You could upload the egg through the Plugin admin page, but it I don't think that feature will help you much. The easiest way to install a plugin is to use easy_install, or just run "python setup.py install" from the plugin source directory. If you have followed the written installation procedure for Bloodhound, then Bloodhound will be installed in a virtualenv. The virtualenv isolates your installation from Python's global site packages directory, which should alleviate concerns about where the plugin gets installed. It will simply be installed in the "lib/python2.7/site-packages" directory of your virtualenv. http://trac.edgewall.org/wiki/TracPlugins#Forallprojects The TracPlugin page should be improved; it doesn't do a very good job of describing the ways a plugin can be installed. The InstallingTrac page does a better job of describing how to install eggs: http://trac.edgewall.org/wiki/TracInstall#InstallingTrac
Re: Quick runup: plugin installation?
On Thu, Mar 19, 2015 at 6:08 AM, Matt Brown wrote: > Also for reference, _a_ list of plugins is available: > http://trac-hacks.org/browser > There is also an index of plugins: http://trac-hacks.org/wiki/HackIndex You may need to adjust the //Show hacks for release// filter to display plugins for Trac 1.0. Of all the plugins on trac-hacks, only one or two have themes for Bloodhound. If a plugin doesn't add new pages this may not be an issue, but plugins that add pages may not look very pleasing to the eye because they lack the appropriate styling.
Re: upgrading to 0.8
On Thu, Mar 19, 2015 at 9:04 AM, Tim Tisdall wrote: > Well, I tried a fresh install and compared the .ini files. I tried to > match my old .ini files to the new ones as much as possible and that > seems to have corrected the problem. I guess the main issue is > there's no method of upgrading the .ini files when upgrading to a > newer version. In previous upgrades I had just made sure that paths > were changed. I guess I must have accumulated some setting from a > previous version (I think my starting version was 0.5.3) that caused > the issues in 0.8. > The plugins are responsible for upgrading the INI file configuration when necessary. That is not to say that the Bloodhound plugins do this correctly for all cases. A backup of your original INI file would help us investigate the issue further. - Ryan
Re: upgrading to 0.8
On Thu, Mar 19, 2015 at 1:44 PM, Ryan J Ollos wrote: > The plugins are responsible for upgrading the INI file configuration when > necessary. That is not to say that the Bloodhound plugins do this correctly > for all cases. > > A backup of your original INI file would help us investigate the issue > further. I noticed I had issues with the request_factory setting being in there, but not the same issue I originally reported. Also, I removed the environment_factory option which pointed to the same value as request_factory, but didn't test to see if that was causing the issue. I don't have a copy of the INI files after I did the migration, but here's a copy of the files before I did the migration (hopefully that's sufficient): (I stripped some private info out) base.ini - [account-manager] account_changes_notify_addresses = authentication_url = db_htdigest_realm = force_passwd_change = true hash_method = HtDigestHashMethod htdigest_file = /sites/apache-bloodhound-0.7/installer/bloodhound/environments/bloodhound.htdigest htdigest_realm = bloodhound htpasswd_file = htpasswd_hash_type = crypt password_file = /sites/apache-bloodhound-0.7/installer/bloodhound/environments/bloodhound.htdigest password_store = HtDigestStore persistent_sessions = False refresh_passwd = False user_lock_max_time = 0 verify_email = True [components] acct_mgr.admin.*= enabled acct_mgr.api.accountmanager = enabled acct_mgr.guard.accountguard = enabled acct_mgr.htfile.htdigeststore = enabled acct_mgr.web_ui.accountmodule = enabled acct_mgr.web_ui.loginmodule = enabled bhtheme.* = enabled bhdashboard.* = enabled multiproduct.* = enabled themeengine.* = enabled trac.ticket.report.reportmodule = disabled trac.ticket.web_ui.ticketmodule = disabled trac.web.auth.loginmodule = disabled tracopt.versioncontrol.git.* = enabled [header_logo] src = [mainnav] browser.label = Source roadmap = disabled timeline = disabled tickets.label = Tickets [theme] theme = bloodhound [trac] #mainnav = dashboard,wiki,browser,tickets,newticket,timeline,roadmap,search,admin mainnav = wiki, timeline, roadmap, browser, tickets, newticket, search trac.ini --- # -*- coding: utf-8 -*- [account-manager] user_lock_max_time = 86400 [attachment] max_size = 262144 max_zip_size = 2097152 render_unsafe_content = false [browser] color_scale = True downloadable_paths = /trunk, /branches/*, /tags/* hide_properties = svk:merge intermediate_color = intermediate_point = newest_color = (255, 136, 136) oldest_color = (136, 136, 255) oneliner_properties = trac:summary render_unsafe_content = false wiki_properties = trac:description [changeset] max_diff_bytes = 1000 max_diff_files = 0 wiki_format_messages = true [inherit] file = /sites/apache-bloodhound-0.7/installer/bloodhound/environments/base.ini htdocs_dir = plugins_dir = templates_dir = [logging] log_file = /sites/apache-bloodhound-0.7/installer/bloodhound/bin/main/log/trac.log log_level = WARNING log_type = file [milestone] stats_provider = DefaultTicketGroupStatsProvider [mimeviewer] max_preview_size = 262144 mime_map = text/x-dylan:dylan, text/x-idl:ice, text/x-ada:ads:adb mime_map_patterns = text/plain:README|INSTALL|COPYING.* pygments_default_style = trac pygments_modes = tab_width = 8 treat_as_binary = application/octet-stream, application/pdf, application/postscript, application/msword,application/rtf, [notification] admit_domains = always_notify_owner = false always_notify_reporter = false always_notify_updater = true ambiguous_char_width = single batch_subject_template = $prefix Batch modify: $tickets_descr email_sender = SmtpEmailSender ignore_domains = mime_encoding = none sendmail_path = sendmail smtp_always_bcc = smtp_always_cc = smtp_default_domain = smtp_enabled = true smtp_from = and...@example.com smtp_from_author = true smtp_from_name = smtp_subject_prefix = __default__ smtp_user = ticket_subject_template = $prefix #$ticket.id: $summary use_public_cc = false use_short_addr = false use_tls = false [project] admin_trac_url = . descr = footer = name = My Site url = [query] default_anonymous_query = status!=closed&cc~=$USER default_query = status!=closed&owner=$USER items_per_page = 100 ticketlink_query = ?status=!closed [report] items_per_page = 100 items_per_page_rss = 0 [revisionlog] default_log_limit = 100 graph_colors = ['#cc0', '#0c0', '#0cc', '#00c', '#c0c', '#c00'] [roadmap] stats_provider = DefaultTicketGroupStatsProvider [search] min_query_length = 3 [ticket] default_cc = default_component = default_description = default_keywords = default_milestone = default_owner = < default > default_priority = major default_product = mainserver default_resolution = fixed default_severity = default_summary = default_type = defect default_version = max_comment_size = 262144 max_description_size = 262144 preserve_newlines = default restrict_owner = false workflow = ConfigurableTicketWorkflow [ticket-workflow] accept = new,assigned,accepted,reopened ->
Re: upgrading to 0.8
On Thu, Mar 19, 2015 at 10:55 AM, Tim Tisdall wrote: > On Thu, Mar 19, 2015 at 1:44 PM, Ryan J Ollos wrote: > > The plugins are responsible for upgrading the INI file configuration when > > necessary. That is not to say that the Bloodhound plugins do this > correctly > > for all cases. > > > > A backup of your original INI file would help us investigate the issue > > further. > > I noticed I had issues with the request_factory setting being in > there, but not the same issue I originally reported. Also, I removed > the environment_factory option which pointed to the same value as > request_factory, but didn't test to see if that was causing the issue. > There were changes to environment_factory and request_factory in Release 8 (1), so it's likely that was the issue. It should be sufficient to remove both options from trac.ini and/or base.ini, which will result in the defaults being used. I added a brief statement to BloodhoundUpgrade (2) and will expand on that when I have time to do more thorough testing. Thanks for working through this and sorry for the trouble. (1) https://issues.apache.org/bloodhound/ticket/795#comment:10 (2) https://issues.apache.org/bloodhound/wiki/BloodhoundUpgrade
