Re: [Trac] Re: Trac.ini

2017-07-10 Thread Steffen Hoffmann
Am 9. Juli 2017 22:13:00 MESZ schrieb toto200891 :
>Yes. is it possible?
>
>Regards,
>SF
>
>On Friday, July 7, 2017 at 8:26:30 PM UTC+2, RjOllos wrote:
>>
>>
>>
>> On Friday, July 7, 2017 at 10:57:15 AM UTC-4, toto200891 wrote:
>>>
>>> Hi
>>>
>>> Could you somebody please tell me like how to have a whole trac.ini
>file 
>>> within the trac environment?
>>>
>>> Regards,
>>> SF
>>>
>>
>> I'm unsure what you mean by "whole trac.ini file".
>>
>> - Ryan
>>  
>>
>
>-- 
>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 trac-users+unsubscr...@googlegroups.com.
>To post to this group, send email to trac-users@googlegroups.com.
>Visit this group at https://groups.google.com/group/trac-users.
>For more options, visit https://groups.google.com/d/optout.


We'll try to help you, if you need more than what our documentaton already 
covers. So please start by reading https://trac.edgewall.org/wiki/TracIni
Hope, the global config section will already tell you much.

Greetings,

Steffen Hoffmann

-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.


Re: [Trac] Re: Trac.ini

2017-07-10 Thread Steffen Hoffmann
Am 7. Juli 2017 20:26:30 MESZ schrieb RjOllos :
>
>
>On Friday, July 7, 2017 at 10:57:15 AM UTC-4, toto200891 wrote:
>>
>> Hi
>>
>> Could you somebody please tell me like how to have a whole trac.ini
>file 
>> within the trac environment?
>>
>> Regards,
>> SF
>>
>
>I'm unsure what you mean by "whole trac.ini file".
>
I think, he's aiming at one central INI file with settings inherited by 
multiple Trac environments.

Steffen Hoffmann

-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.


Re: [Trac] Trying to install Trac on CentOS 5

2017-07-10 Thread Greg Earle

On 10 Jul 2017, at 14:09, James Lampert wrote:


On Monday, July 10, 2017 at 12:56:59 PM UTC-7, Greg Earle wrote:


If James installs the following: 


[https://dl.iuscommunity.org/pub/ius/archive/Redhat/5/$basearch/ius-release-1.0-15.ius.el5.noarch.rpm]()
 

(Substitute "i386" or "x86_64" for $basearch first, obvs.) 

then you can go into "/etc/yum.repos.d" and massage the 
"ius-archive.repo" file it installs - enable "baseurl" and comment 
out 

"mirrorlist".  It should end up looking like this: 

. . .

I had to do something like what you describe with "basurl" and 
"mirrorlist" lines (and then some), just to get the already-recognized 
repositories to work, when installing SVN.


Forgive the newbie question, but how do I install the URL you gave me? 
Is it a yum subcommand? Something else?


If you have your own local yum repo (recommended), download the file(s) 
to that,   update your repo and install it from there.


If not, use "rpm" directly:

rpm -ivh 
https://dl.iuscommunity.org/pub/ius/archive/Redhat/5/i386/ius-release-1.0-15.ius.el5.noarch.rpm


or

rpm -ivh 
https://dl.iuscommunity.org/pub/ius/archive/Redhat/5/x86_64/ius-release-1.0-15.ius.el5.noarch.rpm


whichever is appropriate for your architecture (or both).

If you have further issues we should probably take this off-line.

- Greg

--
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.


Re: [Trac] Trying to install Trac on CentOS 5

2017-07-10 Thread James Lampert


On Monday, July 10, 2017 at 12:56:59 PM UTC-7, Greg Earle wrote:
>
> If James installs the following: 
>
>
> https://dl.iuscommunity.org/pub/ius/archive/Redhat/5/$basearch/ius-release-1.0-15.ius.el5.noarch.rpm
>  
>
> (Substitute "i386" or "x86_64" for $basearch first, obvs.) 
>
> then you can go into "/etc/yum.repos.d" and massage the 
> "ius-archive.repo" file it installs - enable "baseurl" and comment out 
> "mirrorlist".  It should end up looking like this: 
>
. . .

I had to do something like what you describe with "basurl" and "mirrorlist" 
lines (and then some), just to get the already-recognized repositories to 
work, when installing  SVN.

Forgive the newbie question, but how do I install the URL you gave me? Is 
it a yum subcommand? Something else?

--
JHHL
 
 

-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.


Re: [Trac] CommitTicketUpdater issue or something else?

2017-07-10 Thread RjOllos


On Monday, July 3, 2017 at 2:26:33 PM UTC-4, JST wrote:
>
> I am using "trac-svn-hook" and I am able to view some logs.
>
> I am receiving the following error "post-commit hook failed (exit code 2) 
> with no output."
>
> So I am still able to commit and update to the repository I am just not 
> able to "link/ref" ticket #'s and have it linked to the corresponding 
> ticket.
>
> From my research it seems as if the common failure is with "exit code 2 
> with output" not without.  Any suggestions?
>

You could try running the script manually after changing to the users under 
which your webserver runs. If the webserver user is www-data, that would be 
something like:

su - www-data -c '/path/to/svn/hook/script "$REPOS" "$REV"', where $REPOS 
and $REV have been replaced with a valid repository and revision.

>From the [repositories] configuration you showed, it looks like you are 
using the default repository and have added an alias "my-project". I'd try 
using both "(default)" and "my-project" as the repository name in your 
testing.

- Ryan

-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.


Re: [Trac] Trying to install Trac on CentOS 5

2017-07-10 Thread Greg Earle

On 10 Jul 2017, at 12:23, Ryan Ollos wrote:

If you must install on CentOS 5, I'd install Python but don't make it 
the default installation.  Install to a path such a /opt/python27.  
Then, use a virtual environment that points to the 2.7 install for 
your Trac installation.


On our RHEL 5.x boxes we used the IUS repo to install their python27 
RPMS, they didn't interfere/overlap with the system Python.  They worked 
fine for us.


Unfortunately IUS migrated their RHEL 5 repo to their Archives so the 
setup isn't so straightforward now.  They have an "ius-release" RPM for 
RHEL 5 in the Archives but the mirror list doesn't work, so you have to 
hand-hack it after installing it.


If James installs the following:

https://dl.iuscommunity.org/pub/ius/archive/Redhat/5/$basearch/ius-release-1.0-15.ius.el5.noarch.rpm

(Substitute "i386" or "x86_64" for $basearch first, obvs.)

then you can go into "/etc/yum.repos.d" and massage the 
"ius-archive.repo" file it installs - enable "baseurl" and comment out 
"mirrorlist".  It should end up looking like this:


--
[ius-archive]
name=IUS Community Packages for Enterprise Linux 5 - $basearch - Archive
baseurl=http://dl.iuscommunity.org/pub/ius/archive/Redhat/5/$basearch
#mirrorlist=http://dmirr.iuscommunity.org/mirrorlist/?repo=ius-el5-archive&arch=$basearch
failovermethod=priority
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/IUS-COMMUNITY-GPG-KEY

[ius-archive-debuginfo]
name=IUS Community Packages for Enterprise Linux 5 - $basearch - Archive 
Debug

baseurl=http://dl.iuscommunity.org/pub/ius/archive/Redhat/5/$basearch/debuginfo
#mirrorlist=http://dmirr.iuscommunity.org/mirrorlist/?repo=ius-el5-archive-debuginfo&arch=$basearch
failovermethod=priority
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/IUS-COMMUNITY-GPG-KEY

[ius-archive-source]
name=IUS Community Packages for Enterprise Linux 5 - $basearch - Archive 
Source

baseurl=http://dl.iuscommunity.org/pub/ius/archive/Redhat/5/SRPMS
#mirrorlist=http://dmirr.iuscommunity.org/mirrorlist/?repo=ius-el5-archive-source&arch=source
failovermethod=priority
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/IUS-COMMUNITY-GPG-KEY
--

At that point you should be able to do a "yum list python27" and install 
it from there.  (They also have python31 RPMs for 3.1 as well.)


--
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.


Re: [Trac] Trying to install Trac on CentOS 5

2017-07-10 Thread Ryan Ollos
On Mon, Jul 10, 2017 at 12:20 PM, James Lampert 
wrote:

> On Monday, July 10, 2017 at 12:18:27 PM UTC-7, RjOllos wrote:
>>
>> CentOS 5 is rather old. Can you use CentOS 7?
>>
>
> For the scratch-install of the current WinDoze box, probably.
>
> For this box, no.
> --
> JHHL
>


In that case, consider creating a new virtual machine to run the Trac
instance.

If you must install on CentOS 5, I'd install Python but don't make it the
default installation. Install to a path such a /opt/python27. Then, use a
virtual environment that points to the 2.7 install for your Trac
installation.

- Ryan

-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.


Re: [Trac] Trying to install Trac on CentOS 5

2017-07-10 Thread James Lampert
On Monday, July 10, 2017 at 12:18:27 PM UTC-7, RjOllos wrote:
>
> CentOS 5 is rather old. Can you use CentOS 7?
>

For the scratch-install of the current WinDoze box, probably.

For this box, no.
--
JHHL 

-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.


Re: [Trac] Trying to install Trac on CentOS 5

2017-07-10 Thread Ryan Ollos
On Mon, Jul 10, 2017 at 12:08 PM, James Lampert 
wrote:

> On Monday, July 10, 2017 at 11:34:44 AM UTC-7, RjOllos wrote:
>>
>> On Monday, July 10, 2017 at 2:32:59 PM UTC-4, netjunki wrote:
>>>
>>> Centos5's default python is very old. If you can do this on something
>>> newer you'll have a much easier time of it. Pretty sure Trac past 1.0
>>> requires at least python 2.7.
>>>
>>
>> That's right. Looks like he's trying to install in Python 2.4. You'll
>> have to use Trac 0.12.x for Python 2.4.
>>
>> Trac 1.2.x supports Python 2.6 and 2.7. I highly suggest using Python 2.7
>> and Trac 1.2.x for new installs.
>>
>
> That's a roger on the current Python being 2.4. Specifically 2.4.3.
>
> As soon as I read that, I started looking up how to install Python 2.7 on
> CentOS 5.11, and found two things:
>
>1. Simply replacing the system Python breaks Yum, and probably breaks
>a few other things.
>2. There's a whole bunch of subtly different procedures for getting
>Python 2.7 onto CentOS 2.7 side-by-side with the existing 2.4.3.
>
> http://blog.technotesdesk.com/how-to-install-python-2-7-on-rhel-5
>
> http://russell.ballestrini.net/a-system-administrators-
> guide-to-installing-and-maintaining-multiple-python-environments/
>
> https://www.centos.org/forums/viewtopic.php?t=22179  (a rather heated
> discussion)
>
>
>
> Any recommendations on how to proceed?
>

CentOS 5 is rather old. Can you use CentOS 7?

- Ryan

-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.


Re: [Trac] Trying to install Trac on CentOS 5

2017-07-10 Thread James Lampert
On Monday, July 10, 2017 at 11:34:44 AM UTC-7, RjOllos wrote:
>
> On Monday, July 10, 2017 at 2:32:59 PM UTC-4, netjunki wrote:
>>
>> Centos5's default python is very old. If you can do this on something 
>> newer you'll have a much easier time of it. Pretty sure Trac past 1.0 
>> requires at least python 2.7.
>>
>
> That's right. Looks like he's trying to install in Python 2.4. You'll have 
> to use Trac 0.12.x for Python 2.4.
>
> Trac 1.2.x supports Python 2.6 and 2.7. I highly suggest using Python 2.7 
> and Trac 1.2.x for new installs.
>

That's a roger on the current Python being 2.4. Specifically 2.4.3.

As soon as I read that, I started looking up how to install Python 2.7 on 
CentOS 5.11, and found two things:

   1. Simply replacing the system Python breaks Yum, and probably breaks a 
   few other things.
   2. There's a whole bunch of subtly different procedures for getting 
   Python 2.7 onto CentOS 2.7 side-by-side with the existing 2.4.3.

http://blog.technotesdesk.com/how-to-install-python-2-7-on-rhel-5

http://russell.ballestrini.net/a-system-administrators-guide-to-installing-and-maintaining-multiple-python-environments/

https://www.centos.org/forums/viewtopic.php?t=22179  (a rather heated 
discussion) 

 

Any recommendations on how to proceed?

-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.


Re: [Trac] Trying to install Trac on CentOS 5

2017-07-10 Thread RjOllos


On Monday, July 10, 2017 at 2:34:44 PM UTC-4, RjOllos wrote:
>
>
>
> On Monday, July 10, 2017 at 2:32:59 PM UTC-4, netjunki wrote:
>>
>> Centos5's default python is very old. If you can do this on something 
>> newer you'll have a much easier time of it. Pretty sure Trac past 1.0 
>> requires at least python 2.7.
>>
>
> That's right. Looks like he's trying to install in Python 2.4. You'll have 
> to use Trac 0.12.x for Python 2.4.
>
> Trac 1.2.x supports Python 2.6 and 2.7. I highly suggest using Python 2.7 
> and Trac 1.2.x for new installs.
>
> - Ryan
>

Also the error message should be better, but looks like a recent change is 
giving unexpected behavior when installing into an unsupported Python 
version:

https://trac.edgewall.org/ticket/12578#comment:21

- Ryan 

-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.


Re: [Trac] Trying to install Trac on CentOS 5

2017-07-10 Thread RjOllos


On Monday, July 10, 2017 at 2:32:59 PM UTC-4, netjunki wrote:
>
> Centos5's default python is very old. If you can do this on something 
> newer you'll have a much easier time of it. Pretty sure Trac past 1.0 
> requires at least python 2.7.
>

That's right. Looks like he's trying to install in Python 2.4. You'll have 
to use Trac 0.12.x for Python 2.4.

Trac 1.2.x supports Python 2.6 and 2.7. I highly suggest using Python 2.7 
and Trac 1.2.x for new installs.

- Ryan

-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.


Re: [Trac] Trying to install Trac on CentOS 5

2017-07-10 Thread Benjamin Lau
Centos5's default python is very old. If you can do this on something newer
you'll have a much easier time of it. Pretty sure Trac past 1.0 requires at
least python 2.7.

On Mon, Jul 10, 2017 at 11:25 AM, James Lampert 
wrote:

> I have a CentOS 5 development box, that I'm attempting to install SVN and
> Trac on, in preparation for eventually migrating our existing SVN/Trac
> server from WinDoze to Linux (probably CentOS, possibly a more recent
> CentOS).
>
>
> Last week, I was able to figure out how to get SVN up and running, first
> through Apache, and eventually through svnserve.
>
>
> But now that I've turned my attention to Trac, I'm a bit stymied. Yum
> couldn't find it, and I couldn't make head or tail of the instructions for
> registering RPMforge (which appears to be deprecated anyway). I then found
> instructions for doing it with "easy_install," and got as far as installing
> easy_install itself, but it blew up when I tried to install TRAC (and
> unfortunately, what I know about Python wouldn't buy you a cup of coffee):
>
> [root@localhost ~]# easy_install Trac
>
> Searching for Trac
>
> Reading http://pypi.python.org/simple/Trac/
>
> Best match: Trac 1.2.2
>
> Downloading https://pypi.python.org/packages/57/b5/
> fe5784c5f9aeccec0790c3c7c90082838c886e27747f0e12bb424dc33140
> /Trac-1.2.2.tar.gz#md5=38cb5480c35616d8ecb3f0968e454536
>
> Processing Trac-1.2.2.tar.gz
>
> Running Trac-1.2.2/setup.py -q bdist_egg --dist-dir
> /tmp/easy_install-W5NDRI/Trac-1.2.2/egg-dist-tmp-ysJdMQ
>
> Traceback (most recent call last):
>
>  File "/usr/bin/easy_install", line 7, in ?
>
>sys.exit(
>
>  File "/usr/lib/python2.4/site-packages/setuptools-0.6c11-
> py2.4.egg/setuptools/command/easy_install.py", line 1712, in main
>
>with_ei_usage(lambda:
>
>  File "/usr/lib/python2.4/site-packages/setuptools-0.6c11-
> py2.4.egg/setuptools/command/easy_install.py", line 1700, in with_ei_usage
>
>return f()
>
>  File "/usr/lib/python2.4/site-packages/setuptools-0.6c11-
> py2.4.egg/setuptools/command/easy_install.py", line 1716, in 
>
>distclass=DistributionWithoutHelpCommands, **kw
>
>  File "/usr/lib/python2.4/distutils/core.py", line 149, in setup
>
>dist.run_commands()
>
>  File "/usr/lib/python2.4/distutils/dist.py", line 946, in run_commands
>
>self.run_command(cmd)
>
>  File "/usr/lib/python2.4/distutils/dist.py", line 966, in run_command
>
>cmd_obj.run()
>
>  File "/usr/lib/python2.4/site-packages/setuptools-0.6c11-
> py2.4.egg/setuptools/command/easy_install.py", line 211, in run
>
>self.easy_install(spec, not self.no_deps)
>
>  File "/usr/lib/python2.4/site-packages/setuptools-0.6c11-
> py2.4.egg/setuptools/command/easy_install.py", line 446, in easy_install
>
>return self.install_item(spec, dist.location, tmpdir, deps)
>
>  File "/usr/lib/python2.4/site-packages/setuptools-0.6c11-
> py2.4.egg/setuptools/command/easy_install.py", line 476, in install_item
>
>dists = self.install_eggs(spec, download, tmpdir)
>
>  File "/usr/lib/python2.4/site-packages/setuptools-0.6c11-
> py2.4.egg/setuptools/command/easy_install.py", line 655, in install_eggs
>
>return self.build_and_install(setup_script, setup_base)
>
>  File "/usr/lib/python2.4/site-packages/setuptools-0.6c11-
> py2.4.egg/setuptools/command/easy_install.py", line 930, in
> build_and_install
>
>self.run_setup(setup_script, setup_base, args)
>
>  File "/usr/lib/python2.4/site-packages/setuptools-0.6c11-
> py2.4.egg/setuptools/command/easy_install.py", line 919, in run_setup
>
>run_setup(setup_script, args)
>
>  File "/usr/lib/python2.4/site-packages/setuptools-0.6c11-
> py2.4.egg/setuptools/sandbox.py", line 61, in run_setup
>
>DirectorySandbox(setup_dir).run(
>
>  File "/usr/lib/python2.4/site-packages/setuptools-0.6c11-
> py2.4.egg/setuptools/sandbox.py", line 105, in run
>
>return func()
>
>  File "/usr/lib/python2.4/site-packages/setuptools-0.6c11-
> py2.4.egg/setuptools/sandbox.py", line 64, in 
>
>{'__file__':setup_script, '__name__':'__main__'}
>
>  File "setup.py", line 44
>
>with open('README.rst') as f:
>
>^
>
> SyntaxError: invalid syntax
>
> As I said, what I know about Python (or easy_install, for that matter)
> wouldn't buy you a cup of coffee. To quote a line from a certain David
> Hedison movie, "Helpp m"
>
> --
> James H. H. Lampert
>
> --
> 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 trac-users+unsubscr...@googlegroups.com.
> To post to this group, send email to trac-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/trac-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 trac-users+unsub

[Trac] Trying to install Trac on CentOS 5

2017-07-10 Thread James Lampert
I have a CentOS 5 development box, that I'm attempting to install SVN and 
Trac on, in preparation for eventually migrating our existing SVN/Trac 
server from WinDoze to Linux (probably CentOS, possibly a more recent 
CentOS).


Last week, I was able to figure out how to get SVN up and running, first 
through Apache, and eventually through svnserve.


But now that I've turned my attention to Trac, I'm a bit stymied. Yum 
couldn't find it, and I couldn't make head or tail of the instructions for 
registering RPMforge (which appears to be deprecated anyway). I then found 
instructions for doing it with "easy_install," and got as far as installing 
easy_install itself, but it blew up when I tried to install TRAC (and 
unfortunately, what I know about Python wouldn't buy you a cup of coffee):

[root@localhost ~]# easy_install Trac

Searching for Trac

Reading http://pypi.python.org/simple/Trac/

Best match: Trac 1.2.2

Downloading 
https://pypi.python.org/packages/57/b5/fe5784c5f9aeccec0790c3c7c90082838c886e27747f0e12bb424dc33140/Trac-1.2.2.tar.gz#md5=38cb5480c35616d8ecb3f0968e454536

Processing Trac-1.2.2.tar.gz

Running Trac-1.2.2/setup.py -q bdist_egg --dist-dir 
/tmp/easy_install-W5NDRI/Trac-1.2.2/egg-dist-tmp-ysJdMQ

Traceback (most recent call last):

 File "/usr/bin/easy_install", line 7, in ?

   sys.exit(

 File 
"/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/command/easy_install.py",
 
line 1712, in main

   with_ei_usage(lambda:

 File 
"/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/command/easy_install.py",
 
line 1700, in with_ei_usage

   return f()

 File 
"/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/command/easy_install.py",
 
line 1716, in 

   distclass=DistributionWithoutHelpCommands, **kw

 File "/usr/lib/python2.4/distutils/core.py", line 149, in setup

   dist.run_commands()

 File "/usr/lib/python2.4/distutils/dist.py", line 946, in run_commands

   self.run_command(cmd)

 File "/usr/lib/python2.4/distutils/dist.py", line 966, in run_command

   cmd_obj.run()

 File 
"/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/command/easy_install.py",
 
line 211, in run

   self.easy_install(spec, not self.no_deps)

 File 
"/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/command/easy_install.py",
 
line 446, in easy_install

   return self.install_item(spec, dist.location, tmpdir, deps)

 File 
"/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/command/easy_install.py",
 
line 476, in install_item

   dists = self.install_eggs(spec, download, tmpdir)

 File 
"/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/command/easy_install.py",
 
line 655, in install_eggs

   return self.build_and_install(setup_script, setup_base)

 File 
"/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/command/easy_install.py",
 
line 930, in build_and_install

   self.run_setup(setup_script, setup_base, args)

 File 
"/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/command/easy_install.py",
 
line 919, in run_setup

   run_setup(setup_script, args)

 File 
"/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/sandbox.py",
 
line 61, in run_setup

   DirectorySandbox(setup_dir).run(

 File 
"/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/sandbox.py",
 
line 105, in run

   return func()

 File 
"/usr/lib/python2.4/site-packages/setuptools-0.6c11-py2.4.egg/setuptools/sandbox.py",
 
line 64, in 

   {'__file__':setup_script, '__name__':'__main__'}

 File "setup.py", line 44

   with open('README.rst') as f:

   ^

SyntaxError: invalid syntax

As I said, what I know about Python (or easy_install, for that matter) 
wouldn't buy you a cup of coffee. To quote a line from a certain David 
Hedison movie, "Helpp m"

--
James H. H. Lampert

-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.


[Trac] Re: STATUS VIEW POLICY

2017-07-10 Thread RjOllos


On Wednesday, July 5, 2017 at 4:16:44 AM UTC-4, toto200891 wrote:
>
> Hi,
>
> I have been using STATUS VIEW POLICY for having a permission which could 
> allow the user to view the tickets only based "ticket-status". For the 
> same, I have been using the following plugin:
>
> # -*- coding: utf-8 -*-
> #
> # Copyright (C) 2017 Edgewall Software
> # All rights reserved.
> #
> # This software is licensed as described in the file COPYING, which
> # you should have received as part of this distribution. The terms
> # are also available at http://trac.edgewall.org/wiki/TracLicense.
> #
> # This software consists of voluntary contributions made by many
> # individuals. For the exact contribution history, see the revision
> # history and logs, available at http://trac.edgewall.org/log/.
>
> from trac.core import *
> from trac.perm import IPermissionPolicy, IPermissionRequestor
> from trac.resource import ResourceNotFound
> from trac.ticket.model import Ticket
>
>
> class StatusDeskPolicy(Component):
> """Provides a permission for restricting ticket actions to the
> ticket owner.
> """
>
> implements(IPermissionPolicy, IPermissionRequestor)
>
> # IPermissionRequestor methods
>
> def get_permission_actions(self):
> return ['TICKET_VIEW_STATUS']
>
> # IPermissionPolicy methods
>
> def check_permission(self, action, username, resource, perm):
> if username != 'anonymous' and \
> action == 'TICKET_VIEW' and \
> 'TICKET_ADMIN' not in perm:
> if 'TICKET_VIEW_STATUS' in perm:
> if resource is None or \
> resource.realm == 'ticket' and \
> resource.id is None:
> return True
> elif resource.realm == 'ticket' and \
> resource.id is not None:
> try:
> ticket = Ticket(self.env, resource.id)
> except ResourceNotFound:
> pass
> else:
>  return ticket['status'] in ['new', 'test', 
> 'accepted_for_test'] or username in [ticket['reporter'], ticket['owner']]
>
> Initially it was working great, by I dont know what happend recently, it 
> is not functioning properly. As the user with the permission 
> TICKET_VIEW_STATUS, could view all tickets, instead the user with the 
> permission TICKET_VIEW_STATUS , should be able to see only tickets with 
> status, new, test, accepted_for_test, reporter, owner.
>
> Please help me if am missing something?
>
> Regards,
> SF 
>


Please execute the TracAdmin "permission list" command for a users that 
incorrectly sees all tickets rather than the subset with the specified 
status.
https://trac.edgewall.org/wiki/TracAdmin#FullCommandReference

Please post here the output of "permission list" for the specified user.

- Ryan 

-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.


[Trac] Re: TicketCharts

2017-07-10 Thread RjOllos


On Sunday, July 9, 2017 at 4:18:21 PM UTC-4, toto200891 wrote:
>
> Hi,
>
> I just installed a plugin TicketChartsMacro by following this link 
> https://trac-hacks.org/wiki/TicketChartsMacro. I added all the components 
> as described in the link.
>
> And I used one of the examples like 
>
> [[TicketChart(type = stacked_bars, key = type, x_axis = owner)]]
>
> But I don't see any charts on my wiki page. Could somebody guide me with this 
> please?
>
> Regards,
>
> SF
>
>
I've added a notice to the plugin page to indicate that it's deprecated 
since it uses Flash.
https://trac-hacks.org/wiki/TicketChartsMacro

- Ryan 

-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.


[Trac] Re: "Version Control" option is missing from Administration menu

2017-07-10 Thread RjOllos


On Friday, July 7, 2017 at 9:04:57 AM UTC-4, david.johnstone wrote:
>
> Good Evening,
>
>  
>
> The "Version Control" option is missing from Administration menu when I 
> run Trac with Apache.  If I use Tracd, the “Version Control” option is 
> available the Administration menu.  Apache and Tracd are using the same 
> trac.conf file, and I have both Apache (on port 80) and tracd (on port 
> 8080) running at the same time.  This is a test system and not in 
> production.
>
>  
>
> Turning on debug messages in the log file I get the following
>
>  
>
> Traceback (most recent call last):
>
>   File 
> "C:\Python27\lib\site-packages\tracopt\versioncontrol\svn\svn_fs.py", line 
> 298, in __init__
>
> _import_svn()
>
>   File 
> "C:\Python27\lib\site-packages\tracopt\versioncontrol\svn\svn_fs.py", line 
> 77, in _import_svn
>
> from svn import fs, repos, core, delta
>
>   File "C:\Python27\lib\site-packages\svn\fs.py", line 26, in 
>
> from libsvn.fs import *
>
>   File "C:\Python27\lib\site-packages\libsvn\fs.py", line 86, in 
>
> import core
>
>   File "C:\Python27\lib\site-packages\libsvn\core.py", line 25, in 
>
> _core = swig_import_helper()
>
>   File "C:\Python27\lib\site-packages\libsvn\core.py", line 21, in 
> swig_import_helper
>
> _mod = imp.load_module('_core', fp, pathname, description)
>
> ImportError: DLL load failed: The specified procedure could not be found.
>
>  
>
> I assume I have DLL mis-match, but not sure where to look.
>
>  
>
> The system is a Windows 2012R2 server, with Trac 1.2.2, Python 2.7.13, 
> Apache 2.4.26 (VC9) from Apache Haus, and Subversion 1.8.18 from 
> http://alagazam.net/
>
>  
>
> Cheers,
>
> David J.
>

If you can figure out the name of the DLL that is being loaded, you could 
drop that into DependencyWalker and see if there are any missing 
dependencies:
http://dependencywalker.com/

It might be that the DLLs are not on your python patch and your Apache 
configuration needs some modifications. Are you using mod_wsgi?

You could try using different SVN installers:
https://www.wandisco.com/subversion/download
https://www.visualsvn.com/server/download/
https://bitnami.com/stack/trac

I don't have much experience installing on Windows, unfortunately.

- Ryan
 

-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.


[Trac] Re: TracTicketStats

2017-07-10 Thread RjOllos


On Monday, July 10, 2017 at 6:11:58 AM UTC-4, toto200891 wrote:
>
> Hi,
>
> I tried installing the plugin TracTicketStats plugin, but I am gettin the 
> following error:
>
> splugin\trunk>python setup.py install
> running install
> running bdist_egg
> running egg_info
> creating Tracticketstats.egg-info
> writing requirements to Tracticketstats.egg-info\requires.txt
> writing Tracticketstats.egg-info\PKG-INFO
> writing top-level names to Tracticketstats.egg-info\top_level.txt
> writing dependency_links to Tracticketstats.egg-info\dependency_links.txt
> writing entry points to Tracticketstats.egg-info\entry_points.txt
> writing manifest file 'Tracticketstats.egg-info\SOURCES.txt'
> reading manifest file 'Tracticketstats.egg-info\SOURCES.txt'
> writing manifest file 'Tracticketstats.egg-info\SOURCES.txt'
> installing library code to build\bdist.win32\egg
> running install_lib
> running build_py
> creating build
> creating build\lib
> creating build\lib\ticketstats
> copying ticketstats\macro.py -> build\lib\ticketstats
> copying ticketstats\ticketstats.py -> build\lib\ticketstats
> copying ticketstats\__init__.py -> build\lib\ticketstats
> creating build\lib\ticketstats\templates
> copying ticketstats\templates\jsondata.html -> 
> build\lib\ticketstats\templates
> copying ticketstats\templates\ticketstats.html -> 
> build\lib\ticketstats\template
> s
> copying ticketstats\templates\ticketstats_macro.html -> 
> build\lib\ticketstats\te
> mplates
> creating build\bdist.win32
> creating build\bdist.win32\egg
> creating build\bdist.win32\egg\ticketstats
> copying build\lib\ticketstats\macro.py -> build\bdist.win32\egg\ticketstats
> creating build\bdist.win32\egg\ticketstats\templates
> copying build\lib\ticketstats\templates\jsondata.html -> 
> build\bdist.win32\egg\t
> icketstats\templates
> copying build\lib\ticketstats\templates\ticketstats.html -> 
> build\bdist.win32\eg
> g\ticketstats\templates
> copying build\lib\ticketstats\templates\ticketstats_macro.html -> 
> build\bdist.wi
> n32\egg\ticketstats\templates
> copying build\lib\ticketstats\ticketstats.py -> 
> build\bdist.win32\egg\ticketstat
> s
> copying build\lib\ticketstats\__init__.py -> 
> build\bdist.win32\egg\ticketstats
> byte-compiling build\bdist.win32\egg\ticketstats\macro.py to macro.pyc
> byte-compiling build\bdist.win32\egg\ticketstats\ticketstats.py to 
> ticketstats.p
> yc
> byte-compiling build\bdist.win32\egg\ticketstats\__init__.py to 
> __init__.pyc
> creating build\bdist.win32\egg\EGG-INFO
> copying Tracticketstats.egg-info\PKG-INFO -> build\bdist.win32\egg\EGG-INFO
> copying Tracticketstats.egg-info\SOURCES.txt -> 
> build\bdist.win32\egg\EGG-INFO
> copying Tracticketstats.egg-info\dependency_links.txt -> 
> build\bdist.win32\egg\E
> GG-INFO
> copying Tracticketstats.egg-info\entry_points.txt -> 
> build\bdist.win32\egg\EGG-I
> NFO
> copying Tracticketstats.egg-info\requires.txt -> 
> build\bdist.win32\egg\EGG-INFO
> copying Tracticketstats.egg-info\top_level.txt -> 
> build\bdist.win32\egg\EGG-INFO
>
> zip_safe flag not set; analyzing archive contents...
> creating dist
> creating 'dist\Tracticketstats-3.0.0.dev0-py2.7.egg' and adding 
> 'build\bdist.win
> 32\egg' to it
> removing 'build\bdist.win32\egg' (and everything under it)
> Processing Tracticketstats-3.0.0.dev0-py2.7.egg
> Removing c:\python27\lib\site-packages\Tracticketstats-3.0.0.dev0-py2.7.egg
> Copying Tracticketstats-3.0.0.dev0-py2.7.egg to 
> c:\python27\lib\site-packages
> Tracticketstats 3.0.0.dev0 is already the active version in 
> easy-install.pth
>
> Installed 
> c:\python27\lib\site-packages\tracticketstats-3.0.0.dev0-py2.7.egg
> Processing dependencies for Tracticketstats==3.0.0.dev0
> Searching for TracAdvParseArgsPlugin
> Reading https://pypi.python.org/simple/TracAdvParseArgsPlugin/
> Download error on https://pypi.python.org/simple/TracAdvParseArgsPlugin/: 
> timed
> out -- Some packages may not be found!
> Couldn't find index page for 'TracAdvParseArgsPlugin' (maybe misspelled?)
> Scanning index of all packages (this may take a while)
> Reading https://pypi.python.org/simple/
> Download error on https://pypi.python.org/simple/: timed out -- Some 
> packages ma
> y not be found!
> No local packages or download links found for TracAdvParseArgsPlugin
> error: Could not find suitable distribution for 
> Requirement.parse('TracAdvParseA
> rgsPlugin')
>
>
> I downloaded the zip file on the following link: 
> https://trac-hacks.org/wiki/TracTicketStatsPlugin and by using comman 
> "python setup.py install" I tried installing the plugin, But I found the 
> following error.
>
> Please help me in this regard.
>
> Regards,
> SF
>

I modified the plugin to locate the dependency in:
https://trac-hacks.org/changeset/16699

However, the plugin is currently not compatible with Trac >= 1.2. I'll fix 
it later today, and you can follow progress in this ticket:
https://trac-hacks.org/ticket/13231 

- Ryan

-- 
You received this message because you are subscribed to the 

[Trac] Re: Trac.ini

2017-07-10 Thread RjOllos


On Sunday, July 9, 2017 at 4:13:00 PM UTC-4, toto200891 wrote:
>
> Yes. is it possible?
>
> Regards,
> SF
>

I don't know, because I still don't understand what question you are asking.

- Ryan 

-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.


[Trac] Re: TRAC reports

2017-07-10 Thread RjOllos


On Monday, July 10, 2017 at 5:51:48 AM UTC-4, toto200891 wrote:
>
> Hi,
>
> Could somebody please tell me like how to sort the report ordering? I 
> would like to reverse the order of "Active tickets by version" report. For 
> now it is showing from oldest to newest version. I would like to have from 
> newest to oldest? How do I do that?
>
> SELECT p.value AS __color__,
>version AS __group__,
>id AS ticket, summary, component, version, t.type AS type, 
>owner, status,
>time AS created,
>changetime AS _changetime, description AS _description,
>reporter AS _reporter
>   FROM ticket t
>   LEFT JOIN enum p ON p.name = t.priority AND p.type = 'priority'
>   WHERE status <> 'closed'
>   ORDER BY (version IS NULL),version, CAST(p.value AS integer), t.type, 
> time
>
>
> Any help is appreciated.
>
> Regards,
>
> SF
>


To dynamically change the sort ordering, see:
https://trac.edgewall.org/wiki/TracReports#ChangingSortOrder

To change the default ordering you can use the ASC and DESC keywords:
https://sqlite.org/lang_select.html#orderby

You can try:
ORDER BY (version IS NULL),version DESC, CAST(p.value AS integer), t.type, 
time

If you want to sort by Version release date, you'll need to join the 
Version table and sort by version.time:
https://trac.edgewall.org/wiki/TracDev/DatabaseSchema/TicketSystem#Tableversion

- Ryan

-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.


Re: [Trac] Re: tracd and suggested number of users

2017-07-10 Thread Logan Anderson
The way I would make such a decision is asking myself, 

How important is this? 
Do I consider this a "production" environment? 
Do I expect this to grow and be a significant part of my daily work, as well as 
the daily work of others? 
When I am in the middle of "the work" Trac is being setup to manage, am I going 
to WANT to have to consider this question? 
Or am I going to be thankful that it works and I don't have to think about it? 




From: "RjOllos"  
To: "Trac Users"  
Sent: Saturday, July 8, 2017 2:26:33 AM 
Subject: [Trac] Re: tracd and suggested number of users 



On Friday, July 7, 2017 at 8:36:23 AM UTC-4, david.johnstone wrote: 




Good Evening, 



In the Trac documentation it suggestes that tracd is suitable for small 
installations and that for larger installation a “real” web server, like 
Apache, should be used. 



In terms of number of users, what is a small installation? 10 users or 20 users 
or 50 users. 



The question is when should we switching from tracd to Apache? 



Thank you, 

David J. 



When reviewing the documentation I've considered that statement you refer to 
might be a bit too vague because "small" and "large" depend on a number of 
factors, particularly how frequently your web users are making requests. 

If you receive complaints from users or find that the latency or time to 
process a request is too great then it's possible that a web server such as 
Apache would improve performance when properly configured. Moving from SQLite 
to PostgreSQL or MySQL can also give performance improvements. 

Because site performance depends on a number of factors including how your 
users are interacting with the site, you would really only be able to determine 
which changes to make by running site performance monitoring and profiling the 
request requests. Since that's a lot of work, requires expertise and is 
difficult to describe in a general way, we are left with suggesting that if 
performance isn't good enough, then you might consider switching to Apache or 
changing the database backend. I suggest setting up a mirror of your site and 
making incremental changes while profiling the requests using browser tools 
until you get the performance improvements you are looking for. 

More information here: 
https://trac.edgewall.org/wiki/TracPerformance 

Are you running into any performance issues? 

- Ryan 


-- 
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 trac-users+unsubscr...@googlegroups.com . 
To post to this group, send email to trac-users@googlegroups.com . 
Visit this group at https://groups.google.com/group/trac-users . 
For more options, visit https://groups.google.com/d/optout . 

-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.


[Trac] TracTicketStats

2017-07-10 Thread toto200891
Hi,

I tried installing the plugin TracTicketStats plugin, but I am gettin the 
following error:

splugin\trunk>python setup.py install
running install
running bdist_egg
running egg_info
creating Tracticketstats.egg-info
writing requirements to Tracticketstats.egg-info\requires.txt
writing Tracticketstats.egg-info\PKG-INFO
writing top-level names to Tracticketstats.egg-info\top_level.txt
writing dependency_links to Tracticketstats.egg-info\dependency_links.txt
writing entry points to Tracticketstats.egg-info\entry_points.txt
writing manifest file 'Tracticketstats.egg-info\SOURCES.txt'
reading manifest file 'Tracticketstats.egg-info\SOURCES.txt'
writing manifest file 'Tracticketstats.egg-info\SOURCES.txt'
installing library code to build\bdist.win32\egg
running install_lib
running build_py
creating build
creating build\lib
creating build\lib\ticketstats
copying ticketstats\macro.py -> build\lib\ticketstats
copying ticketstats\ticketstats.py -> build\lib\ticketstats
copying ticketstats\__init__.py -> build\lib\ticketstats
creating build\lib\ticketstats\templates
copying ticketstats\templates\jsondata.html -> 
build\lib\ticketstats\templates
copying ticketstats\templates\ticketstats.html -> 
build\lib\ticketstats\template
s
copying ticketstats\templates\ticketstats_macro.html -> 
build\lib\ticketstats\te
mplates
creating build\bdist.win32
creating build\bdist.win32\egg
creating build\bdist.win32\egg\ticketstats
copying build\lib\ticketstats\macro.py -> build\bdist.win32\egg\ticketstats
creating build\bdist.win32\egg\ticketstats\templates
copying build\lib\ticketstats\templates\jsondata.html -> 
build\bdist.win32\egg\t
icketstats\templates
copying build\lib\ticketstats\templates\ticketstats.html -> 
build\bdist.win32\eg
g\ticketstats\templates
copying build\lib\ticketstats\templates\ticketstats_macro.html -> 
build\bdist.wi
n32\egg\ticketstats\templates
copying build\lib\ticketstats\ticketstats.py -> 
build\bdist.win32\egg\ticketstat
s
copying build\lib\ticketstats\__init__.py -> 
build\bdist.win32\egg\ticketstats
byte-compiling build\bdist.win32\egg\ticketstats\macro.py to macro.pyc
byte-compiling build\bdist.win32\egg\ticketstats\ticketstats.py to 
ticketstats.p
yc
byte-compiling build\bdist.win32\egg\ticketstats\__init__.py to __init__.pyc
creating build\bdist.win32\egg\EGG-INFO
copying Tracticketstats.egg-info\PKG-INFO -> build\bdist.win32\egg\EGG-INFO
copying Tracticketstats.egg-info\SOURCES.txt -> 
build\bdist.win32\egg\EGG-INFO
copying Tracticketstats.egg-info\dependency_links.txt -> 
build\bdist.win32\egg\E
GG-INFO
copying Tracticketstats.egg-info\entry_points.txt -> 
build\bdist.win32\egg\EGG-I
NFO
copying Tracticketstats.egg-info\requires.txt -> 
build\bdist.win32\egg\EGG-INFO
copying Tracticketstats.egg-info\top_level.txt -> 
build\bdist.win32\egg\EGG-INFO

zip_safe flag not set; analyzing archive contents...
creating dist
creating 'dist\Tracticketstats-3.0.0.dev0-py2.7.egg' and adding 
'build\bdist.win
32\egg' to it
removing 'build\bdist.win32\egg' (and everything under it)
Processing Tracticketstats-3.0.0.dev0-py2.7.egg
Removing c:\python27\lib\site-packages\Tracticketstats-3.0.0.dev0-py2.7.egg
Copying Tracticketstats-3.0.0.dev0-py2.7.egg to 
c:\python27\lib\site-packages
Tracticketstats 3.0.0.dev0 is already the active version in easy-install.pth

Installed c:\python27\lib\site-packages\tracticketstats-3.0.0.dev0-py2.7.egg
Processing dependencies for Tracticketstats==3.0.0.dev0
Searching for TracAdvParseArgsPlugin
Reading https://pypi.python.org/simple/TracAdvParseArgsPlugin/
Download error on https://pypi.python.org/simple/TracAdvParseArgsPlugin/: 
timed
out -- Some packages may not be found!
Couldn't find index page for 'TracAdvParseArgsPlugin' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Reading https://pypi.python.org/simple/
Download error on https://pypi.python.org/simple/: timed out -- Some 
packages ma
y not be found!
No local packages or download links found for TracAdvParseArgsPlugin
error: Could not find suitable distribution for 
Requirement.parse('TracAdvParseA
rgsPlugin')


I downloaded the zip file on the following 
link: https://trac-hacks.org/wiki/TracTicketStatsPlugin and by using comman 
"python setup.py install" I tried installing the plugin, But I found the 
following error.

Please help me in this regard.

Regards,
SF

-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.


[Trac] TRAC reports

2017-07-10 Thread toto200891
Hi,

Could somebody please tell me like how to sort the report ordering? I would 
like to reverse the order of "Active tickets by version" report. For now it 
is showing from oldest to newest version. I would like to have from newest 
to oldest? How do I do that?

SELECT p.value AS __color__,
   version AS __group__,
   id AS ticket, summary, component, version, t.type AS type, 
   owner, status,
   time AS created,
   changetime AS _changetime, description AS _description,
   reporter AS _reporter
  FROM ticket t
  LEFT JOIN enum p ON p.name = t.priority AND p.type = 'priority'
  WHERE status <> 'closed'
  ORDER BY (version IS NULL),version, CAST(p.value AS integer), t.type, time


Any help is appreciated.

Regards,

SF

-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.