On Saturday, August 9, 2014 8:01:22 AM UTC-7, Anne Johnson wrote: > > I never signed up for this group. Please unsubscribe me or tell me how to > do so. > > Thank you, > Anne Aronson Johnson > There are clear instructions at the end of the email on how to unsubscribe.
> On Aug 9, 2014 9:33 AM, <[email protected] <javascript:>> wrote: > >> Today's topic summary >> >> Group: http://groups.google.com/group/trac-users/topics >> >> - Setuptools 5.4 performance >> >> <#CAJ5eG=cKJCpEZFhGrz=nPOdOreT55Yu=-TJP6nnosLTe5-jhxg@mail.gmail.com_147bb2feae87456d_group_thread_0> >> >> [2 Updates] >> - How to apply a patch to Trac >> >> <#CAJ5eG=cKJCpEZFhGrz=nPOdOreT55Yu=-TJP6nnosLTe5-jhxg@mail.gmail.com_147bb2feae87456d_group_thread_1> >> >> [3 Updates] >> - TracBrowser: Where is it? >> >> <#CAJ5eG=cKJCpEZFhGrz=nPOdOreT55Yu=-TJP6nnosLTe5-jhxg@mail.gmail.com_147bb2feae87456d_group_thread_2> >> >> [2 Updates] >> - CommitTicketUpdate does not seem to be checking permission (Git) >> >> <#CAJ5eG=cKJCpEZFhGrz=nPOdOreT55Yu=-TJP6nnosLTe5-jhxg@mail.gmail.com_147bb2feae87456d_group_thread_3> >> >> [1 Update] >> - 回复： [Trac] Custom fields per component >> >> <#CAJ5eG=cKJCpEZFhGrz=nPOdOreT55Yu=-TJP6nnosLTe5-jhxg@mail.gmail.com_147bb2feae87456d_group_thread_4> >> >> [1 Update] >> - TracHoursPlugin in conjunction with AnnouncerPlugin >> >> <#CAJ5eG=cKJCpEZFhGrz=nPOdOreT55Yu=-TJP6nnosLTe5-jhxg@mail.gmail.com_147bb2feae87456d_group_thread_5> >> >> [1 Update] >> >> Setuptools 5.4 performance >> <http://groups.google.com/group/trac-users/t/817e646135055cce> >> >> Peter Suter <[email protected] <javascript:>> Aug 08 09:11PM +0200 >> >> When I upgraded setuptools to 5.4.x, Trac became completely >> unresponsive >> (loading a simple page takes 30 seconds instead of less than 1). >> (On Windows, Python 2.6 or 2.7, Trac trunk tracd. The problem only >> manifested itself when Trac was installed as an egg, not in "setup.py >> develop" mode.) >> >> Downgrading setuptools (to 5.3 or below) fixed the problem. >> >> [1] points to [2] and mentionsthe PKG_RESOURCES_CACHE_ZIP_MANIFESTS >> environment variable. Setting that environment variable with 5.4 also >> enables reasonable performance. Although it sounds like this enables >> a >> new experimental feature. So why is it required to get back >> performance >> similar to 5.3? >> >> Am I missing something? (Should we report a bug? Warn users against >> this >> version?) >> >> [1] https://pypi.python.org/pypi/setuptools#id3 >> [2] https://bitbucket.org/pypa/setuptools/issue/154 >> >> >> >> >> Jun Omae <[email protected] <javascript:>> Aug 09 10:23PM +0900 >> >> > version?) >> >> > [1] https://pypi.python.org/pypi/setuptools#id3 >> > [2] https://bitbucket.org/pypa/setuptools/issue/154 >> >> I think that is a setuptools issue in 5.4. It seems the issue has been >> introduced in [10cc90d9b828] and [2d13c675f84c] of setuptools. >> >> After setuptools 5.4, the zipinfo property of ZipProvider class reads >> egg file each time. Before 5.3, __init__ method of ZipProvider class >> reads egg file and the result will be stored in its "zipinfo" instance >> variable. >> >> The following patch would fix it. >> >> --- pkg_resources.py.orig 2014-08-09 22:06:34.877375000 +0900 >> +++ pkg_resources.py 2014-08-09 22:06:37.533625000 +0900 >> @@ -1636,7 +1636,11 @@ >> >> @property >> def zipinfo(self): >> - return self._zip_manifests.load(self.loader.archive) >> + try: >> + return self._zipinfo >> + except AttributeError: >> + self._zipinfo = self._zip_manifests.load(self.loader.archive) >> + return self._zipinfo >> >> def get_resource_filename(self, manager, resource_name): >> if not self.egg_name: >> >> -- >> Jun Omae <[email protected] <javascript:>> (大前 潤) >> >> >> >> How to apply a patch to Trac >> <http://groups.google.com/group/trac-users/t/bcb23f9d5eafecd5> >> >> Jared Bownds <[email protected] <javascript:>> Aug 08 11:27AM -0700 >> >> >> URL: http://trac.edgewall.org/ticket/7339#comment:79 >> >> What are the practical steps necessary to apply a patch? Example >> patch can >> be found in the URL above. >> >> >> >> >> Jared Bownds <[email protected] <javascript:>> Aug 08 11:36AM -0700 >> >> >> For example, would these be an expected output? >> >> >> >> (jared)-(11:33:30)-(/usr/lib/python2.6/site-packages/Trac-1.0-py2.6.egg/trac) >> >> -> *patch -p1 < Trac-show_full_names-sorted-r4-0.12.2.patch* >> patching file test.py >> Hunk #1 FAILED at 283. >> 1 out of 1 hunk FAILED -- saving rejects to file test.py.rej >> patching file ticket/default_workflow.py >> Hunk #1 succeeded at 226 (offset 12 lines). >> Hunk #2 succeeded at 277 (offset 12 lines). >> patching file ticket/templates/query.html >> Hunk #1 FAILED at 83. >> 1 out of 1 hunk FAILED -- saving rejects to file >> ticket/templates/query.html.rej >> patching file ticket/templates/ticket.html >> Hunk #1 succeeded at 260 (offset -22 lines). >> patching file ticket/web_ui.py >> Hunk #1 succeeded at 18 (offset 2 lines). >> Hunk #2 FAILED at 48. >> Hunk #3 FAILED at 441. >> Hunk #4 succeeded at 1249 (offset 98 lines). >> Hunk #5 succeeded at 1567 (offset 114 lines). >> Hunk #6 FAILED at 1551. >> Hunk #7 succeeded at 1714 (offset 122 lines). >> Hunk #8 FAILED at 1617. >> Hunk #9 succeeded at 1758 with fuzz 1 (offset 121 lines). >> 4 out of 9 hunks FAILED -- saving rejects to file ticket/web_ui.py.rej >> patching file web/chrome.py >> Hunk #1 succeeded at 43 (offset 10 lines). >> Hunk #2 succeeded at 451 (offset 121 lines). >> Hunk #3 succeeded at 1045 (offset 133 lines). >> Hunk #4 succeeded at 1058 (offset 133 lines). >> Hunk #5 succeeded at 1077 (offset 133 lines). >> patching file web/session.py >> Hunk #1 succeeded at 31 (offset 3 lines). >> Hunk #2 succeeded at 143 with fuzz 1 (offset 7 lines). >> Hunk #3 FAILED at 240. >> Hunk #4 succeeded at 426 with fuzz 2. >> Hunk #5 succeeded at 443 with fuzz 1 (offset -4 lines). >> 1 out of 5 hunks FAILED -- saving rejects to file web/session.py.rej >> >> >> On Friday, August 8, 2014 11:27:34 AM UTC-7, Jared Bownds wrote: >> >> >> >> >> Steffen Hoffmann <[email protected] <javascript:>> Aug 09 03:14PM +0200 >> >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 08.08.2014 20:36, Jared Bownds wrote: >> > For example, would these be an expected output? >> >> > >> >> (jared)-(11:33:30)-(/usr/lib/python2.6/site-packages/Trac-1.0-py2.6.egg/trac) >> >> > -> *patch -p1 < Trac-show_full_names-sorted-r4-0.12.2.patch* >> >> Yes. >> >> As you see at least some changes apply. Otherwise it could be just on >> the wrong level, but obviously you adjusted it correctly with -p >> option. >> >> Offset is a hint on code changes between the version the patch has >> been >> created an the version you're trying to apply the patch. With only >> offset it might, but is not guaranteed to work. >> >> Anyway the presented case includes failing lines too, so you're >> required >> to rework the changes collected in the corresponding *.rej files to >> fit >> into the current version. >> >> Depending on the intermediately introduced changes adjusting a patch >> is >> anything between trivial and almost impossible. Recent commit messages >> could help to reveal potentially complicated changes. No one could >> tell >> without seeing the code in detail. And certainly it is no longer "just >> patching" but will require some Python knowledge to do the work. >> >> Steffen Hoffmann >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.12 (GNU/Linux) >> Comment: Using GnuPG with Icedove - http://www.enigmail.net/ >> >> iEYEARECAAYFAlPmHpgACgkQ31DJeiZFuHcB/QCeITZc6kpdzv6+SfVkhR3P8Poe >> yFoAoKP+raVrTZPdotcXzuUMkyHSyHPe >> =0vbt >> -----END PGP SIGNATURE----- >> >> >> >> TracBrowser: Where is it? >> <http://groups.google.com/group/trac-users/t/dc8aace590334c87> >> >> pgarofalo <[email protected] <javascript:>> Aug 08 09:13AM -0700 >> >> Hi there, Apologies for this super-noob question, but we're new Trac >> users, >> just installed it on the same server as our Subversion server. As >> admin I >> set Trac up to point to the SVN repository. There is now an entry for >> it in >> the "Manage Repositories" page of the Admin section. Thing is, I >> don't see >> a link to TracBrowser or the repository index anywhere. I would >> expect >> there to be a link in the main horizontal menu at the top of every >> page, >> but it's not there. The help doesn't indicate how to get to the >> repository >> index. How do you get to Trac's vaunted Subversion interface? >> >> Thanks! >> >> >> >> >> [email protected] <javascript:> Aug 08 09:20PM -0700 >> >> FYI >> >> You might need to setup user or group permissions to view the Trac >> Browser. >> Some systems may require the user to be logged-in and therefore >> authenticated. You could also allow the permissions for anonymous >> so that anyone visiting your site can view the repository. >> >> Sincerely, >> Steven J. Hathaway >> >> >> >> >> CommitTicketUpdate does not seem to be checking permission (Git) >> <http://groups.google.com/group/trac-users/t/29e25b5b6d3a0b3b> >> >> RjOllos <[email protected] <javascript:>> Aug 08 11:06AM -0700 >> >> On Friday, August 1, 2014 4:54:18 AM UTC-7, Sylvain Raybaud wrote: >> > [email protected] <javascript:> is owner of ticket >> #67 >> >> > Regards, >> >> > Sylvain Raybaud >> >> I can only make some guesses based on the source code: >> >> >> http://trac.edgewall.org/browser/trunk/tracopt/ticket/commit_updater.py?rev=12865&marks=270-274#L259 >> >> - Confirm that commit_ticket_update_check_perms is in the [ticket] >> section. The value defaults to true anyway, so it seems unlikely this >> is >> the issue. >> - Do you have any special permission policies? >> >> You could try adding some logging to line 270: >> self.log.info("check_perms = %s, checking TICKET_MODIFY user %s: %s", >> self.check_perms, authname, 'TICKET_MODIFY' in perm) >> >> >> >> 回复： [Trac] Custom fields per component >> <http://groups.google.com/group/trac-users/t/f16325652b45c7ef> >> >> RjOllos <[email protected] <javascript:>> Aug 08 10:21AM -0700 >> >> On Thursday, August 7, 2014 7:59:22 PM UTC-7, Jojo R wrote: >> > 0.11 and 0.12 both, no one can set "show_when_component". >> >> > Thanks, >> >> > - Jojo >> >> The configuration you've shown works for me on Trac 1.0.2dev, for >> both the >> 0.11 and 0.12 branches of DynamicFieldsPlugin. >> >> I suggest: >> - Try disabling all other plugins temporarily, there may be a >> conflict. If >> it works with all plugins disabled, enable them one by one to >> discover the >> plugin that DynamicFieldsPlugin conflicts with. >> - Look in the browser console for JavaScript errors. >> >> >> >> TracHoursPlugin in conjunction with AnnouncerPlugin >> <http://groups.google.com/group/trac-users/t/81627bcacc5cc504> >> >> Jared Bownds <[email protected] <javascript:>> Aug 08 08:01AM -0700 >> >> >> URL: http://trac-hacks.org/ticket/11918 >> >> When utilizing Trac with the default notification system, and >> TracHoursPlugin, email notifications are not sent when submitting >> hour >> entries (this is good behavior). >> >> However, when using the Announcer notification system, email >> notifications >> are sent for each hour entry. Is there a way to silence this behavior >> and >> disable notification for hour entries submitting using >> TracHoursPlugin? >> >> Resolving this will allow us to completely adopt the AnnouncerPlugin. >> >> Best >> >> Jared >> >> >> >> -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
