Koozali.org formerly Contribs.org

[ANNOUNCE] smeserver-trac contrib

Upgrade procedure smeserver-trac version 0.2-8 and earlier
« Reply #15 on: March 28, 2007, 07:04:37 AM »
I you are trying the smeserver-trac contrib, you should be aware versions earlier than 0.2-8 have a problem in the install procedure that cause your trac environments to be deleted when you upgrade to a newer version of smeserver-trac.  

This is now fixed, but if have a version 0.2-8 or earlier installed I suggest you follow the following steps (as root):

Code: [Select]
cd /home/e-smith/files
cp -r trac/ trac-backup
yum remove smeserver-trac
yum --disablerepo=* --enablerepo=through-ip clean all
yum --enablerepo=through-ip install smeserver-trac


Then in server manager, recreate your Trac project environments exactly as you had them and then as root again:

Code: [Select]
cd /home/e-smith/files
service httpd-e-smith stop
cp -r trac-backup/ trac
service httpd-e-smith start


From then on you will be safe from loosing your trac environments upon upgrades of smeserver-trac.

Regards,

Marco
Adelaide - Australia

Re: Thankyou thf - just what I needed.
« Reply #16 on: March 28, 2007, 07:19:35 AM »
Quote from: "dlj"
I am in the UK and would prefer the dates in a UK format.


:D smeserver-trac-0.2-10 now supports setting the TracLocale in the httpd template with the value read from the configuration database.

You can check the language that your system is set to and that Trac will use from:

Code: [Select]
config show sysconfig

the Language setting that is shown there will be used for the Trac environment.

If required you can change the Language property with something like:

Code: [Select]
config setprop sysconfig Language en_GB

The only thing I am not sure of at the moment is if this database value is  the right one to use as it seems to get reset after a signal-event console-save :?

But in the mean time it works and in Trac is showing dates in that configured Locale like 28.3.07 for de_DE and 28/03/07 for en_GB and en_AU and 03/28/07 for en_US.

If you plan to upgrade, please check the previous post re. upgrading and the possibility that you loose :cry: your trac environments.

Enjoy!

Marco
Adelaide - Australia

Offline Franco

  • *
  • 1,171
    • http://contribs.org
[ANNOUNCE] smeserver-trac contrib
« Reply #17 on: March 30, 2007, 02:47:18 AM »
Very good!
Fresh install did it!

Thanks a lot and sorry for the confusion!

Fantastic Contrib!
« Reply #18 on: March 31, 2007, 03:27:26 PM »
Hi thf,

First, thanks alot for this fantastic contrib!
I tried to built a contrib for TRAC for a while but ultimitely failed because of lack of time and understanding (mainly understanding, i'm still new to linux  :?  ).

I do have one issue which may just be a matter of taste but I thought I'd share it in case its easy to implement:

Usually, I like to setup the svn repo & trac database so they have the same project name to minimise confusion.
eg: the "myproject" project would look like:
/path_to_repo/myproject   (repo folder)
/path_to_trac/myproject    (trac DB)
and similarly the URL's to each carry the same project name:
  http://myserver/svn/myproject
  http://myserver/trac/myproject
or even better:
  http://svn.myserver/myproject
  http://trac.myserver/myproject

I've found that this removed any confusion there might have been about which trac project was for which svn repository.

I have figured how to change the URL by using custom "VirtualHosts" fragments but the TRAC contrib wont allow me to create a TRAC system with the same name as the svn repository.
It gives the following error when I try:
"The Trac project environment "myproject" is an existing account."

Do you have any suggestions as to how I might be able to have the same name for both TRAC & svn projects?

Thanks for any help.

Black

PS: One thought that came to mind was to append "_trac" to all trac account names and remove the "_trac" appendage when referring to the file location or URL.

[ANNOUNCE] smeserver-trac contrib
« Reply #19 on: April 02, 2007, 10:40:33 AM »
Quote from: "blacknz"
Hi thf,
Usually, I like to setup the svn repo & trac database so they have the same project name to minimise confusion.
eg: the "myproject" project would look like:
/path_to_repo/myproject   (repo folder)
/path_to_trac/myproject    (trac DB)
and similarly the URL's to each carry the same project name:
  http://myserver/svn/myproject
  http://myserver/trac/myproject
or even better:
  http://svn.myserver/myproject
  http://trac.myserver/myproject


Hi blacknz,
My very first attempt in setting up Trac on my SME server used the account name from the subversion repository with a /trac prefix). However when I was delving deeper into it,  there were a couple of reasons against that approach:
  • I discovered that Trac allows for creating any number of trac projects for different parts of the same SVN repository. I really liked this and decided to support this in the contrib and hence there is no longer a true one-on-one mapping of names anyway. On my own projects I have only one or two main repositories which each hold multiple 'projects' or 'modules'. I have Trac environments for almost all of those projects.
  • For simplicity, the contrib relies on and makes use of the SME account naming system. This avoid avoids clashes  between different things (e.g. users versus ibays versus pseudonyms, etc.).  As a consequence each account item on SME needs to have a unique name. Also, a prefix like /trac/project could clash with an ibay called trac so I still would have to have build checks for that :-(!. Then finally, I was not sure what the other implications would have been of creating a completely new name space just for Trac.
  • For me, the main reason for implementing the Trac contrib (other than that is was a nice first contrib project) is that I really like the Trac repository browser with its colourised way of showing the differences and syntax colouring. As such I did not consider the subversion web browsing of the repository and instead I use the Trac browser exclusively. If you are a user of subversion, this could be your main reason for installing Trac, only use the repository browser and forget about the Wiki and Ticket system!
  • The only time I need the repository URL is when I setup a new module in my repository. After that the svn access is virtually transparent as it remembers the svn path on subsequent accesses, so it seemed not so much of a deal that I needed to have the same name for the project. I guess that you should be able to setup a local intranet page that describes your setup with URL links for SVN and Trac bits of the various projects that you have.


So that were some of my considerations. Things are not always that straightforward if you delve under the surface and need to consider other implications.

Having said that, the src of the contrib is available in http://through-ip.com/packages/smeserver/SRPMS/ so you can have a look and have a go at modifying or extending it. If you have a patch available, I am happy to take a look at it.

I am working with the SME development team to have this contrib in the SME contribs repository so that it becomes available through the normal SME channels and it then should also have a bug tracker category assigned where you can make bug reports and feature requests.

In the mean time, thanks for trying out my smeserver-trac contrib.

Regards,

Marco Hess
Adelaide - Australia

[ANNOUNCE] smeserver-trac contrib
« Reply #20 on: April 03, 2007, 08:19:03 AM »
Hi thf,

Thank you for your very candid response.

I can now fully understand why you implemented the contrib the way you did.

The possible conflict between the /trac & /svn prefixes and ibay names hadn't occurred to me and I can now see that your method of implementation is very good.

I think I will now setup my svn projects so the project names carry the svn prefix and I will use the proper name for the trac projects.
eg. 'myproject' would be 'svn_myproject' for the repository & just 'myproject' for trac.
As you say, the repo path is rarely used and I can provide a how-to wiki on the projects trac website.

I still haven't quite figured how to get the system working so trac access is limited to only http://trac.myserver/myproject instead of http://myserver/myproject.
I'm sure it should be quite simple but being a noob I'm struggling a little.

On a similar note, is it possible to choose which domains the trac projects are available on?
Currently all trac projects are available on all domains and I think allowing the user to select from available domains would be an excellent feature.

Thanks again for your help.

Best regards,

Black

[ANNOUNCE] smeserver-trac contrib
« Reply #21 on: April 04, 2007, 02:36:47 AM »
Quote from: "blacknz"

I still haven't quite figured how to get the system working so trac access is limited to only http://trac.myserver/myproject instead of http://myserver/myproject.
I'm sure it should be quite simple but being a noob I'm struggling a little.


That is an area where currently the SME support is somewhat limited. All host names are basically aliases of the same thing and all services reside in the same virtual host environment. I looked into some of that, but could not see an immediate solution without having to dig a whole lot deeper.

Regards,

Marco
Adelaide - Australia

[ANNOUNCE] smeserver-trac contrib
« Reply #22 on: April 04, 2007, 07:47:34 AM »
Quote from: "thf"

That is an area where currently the SME support is somewhat limited.
[snip]
could not see an immediate solution without having to dig a whole lot deeper.


Yeah, I'm not really very good with apache configuration files so I think I'll just forget about it for now.

Quote from: "blacknz"
is it possible to choose which domains the trac projects are available on?


I did a little research on this one, it appears that all templates in the VirtualHosts template folder are passed a variable $virtualHost.
This variable contains the name of the domain that is being processed (eg mysite.local, mysite.com etc)
So, by testing this you could restrict which virtual domains the trac site is available on:
Code: [Select]
 if ( $virtualHost eq $allowedDomains )
  {
    # process the trac template
  }
(I know the code is incorrect as I don't know perl & I'm not sure how you check to see if a string is in a list).

I couldn't figure out how you could build a list of domains to select from for the server-manager panel (like you have to select the groups & users) but I havent figured that out ... yet.

What do you think about having an option for selecting which domain the trac project should be available on?

If you think its a good addition to your contrib then perhaps I could try to dig a little deeper.

Black

[ANNOUNCE] smeserver-trac contrib
« Reply #23 on: April 06, 2007, 02:05:41 PM »
Quote from: "blacknz"

Code: [Select]
 if ( $virtualHost eq $allowedDomains )
{
    # process the trac template
}


That approach sounds quite doable. I have made a start with implementing that.

In hindsight the comment that I made previously referred to the host names that SME provides on domains (e.g. the www, mail, etc.). What I wanted to do was to make the trac environments available under a specified host name only like in trac.domain.com and not www.domain.com. That sort of support is quite limited. e.g. you can go into the hostname panel and remove the various host names that are local to the machine and in the http config they still show up.


Marco
Adelaide - Australia

pabbec

Problem at install smeserver-trac
« Reply #24 on: April 06, 2007, 10:21:54 PM »
Hi. I have a problem when I want to install smeserver-trac in my SME Server. When I execute the command:

Code: [Select]

# yum --enablerepo=through-ip install smeserver-trac


I obtain the following answer:

Code: [Select]

==============================================================
WARNING: Additional commands may be required after running yum
==============================================================
Loading "smeserver" plugin
Loading "fastestmirror" plugin
Setting up Install Process
Setting up repositories
through-ip                100% |=========================|  951 B    00:00
Cannot find a valid baseurl for repo: snetram
Error: Cannot find a valid baseurl for repo: snetram
================================================================
No new rpms were installed. No additional commands are required.
================================================================


I'm using SME Server 7.1.3. I have installed subversion from a contrib of snetram. Thanks in advance and sorry for my bad english :(

Re: Problem at install smeserver-trac
« Reply #25 on: April 07, 2007, 02:22:38 AM »
Quote from: "pabbec"
Hi. I have a problem when I want to install smeserver-trac in my SME Server


Hi pabbec,
I was asked to remove some packages from my repository as it duplicated packages from more authoritative repositories :-) so the updated install should now be:
Code: [Select]
yum --enablerepo=smedev --enablerepo=through-ip install smeserver-trac


In the near future, some more cleanup will occur to get rid of duplicate packages in my repository and eventually everything will move to smedev  

At the moment the yum command above should give you something like this:

Code: [Select]

Dependencies Resolved

=============================================================================
 Package                 Arch       Version          Repository        Size
=============================================================================
Installing:
 smeserver-trac          noarch     0.3-1.el4.sme    through-ip        113 k
Installing for dependencies:
 clearsilver             i386       0.10.1-1.2.el4.rf  through-ip        192 k
 fontconfig              i386       2.2.3-7.centos4  smeos             117 k
 guile                   i386       5:1.6.4-14       base              746 k
 mod_dav_svn             i386       1.1.4-2.ent      base               50 k
 mod_python              i386       3.1.3-5.1        base              568 k
 neon                    i386       0.24.7-4         base               86 k
 python-clearsilver      i386       0.10.1-1.2.el4.rf  through-ip        181 k
 python-docutils         noarch     0.4-1.el4.kb     through-ip        1.3 M
 python-imaging          i386       1.1.4-7          through-ip        358 k
 python-setuptools       noarch     0.6a10-1         through-ip        447 k
 python-silvercity       i386       0.9.5-3.el4.pyv  through-ip         13 k
 python23-silvercity     i386       0.9.5-3.el4.pyv  through-ip        175 k
 smeserver-mod_dav       noarch     0.1-2.el4.sme    smedev            4.3 k
 smeserver-mod_python    noarch     0.1-0.el4.sme    smedev            4.2 k
 smeserver-subversion    noarch     1.2-5.el4.sme    smedev             45 k
 subversion              i386       1.1.4-2.ent      base              1.6 M
 swig                    i386       1.3.21-6         base              1.0 M
 tcl                     i386       8.4.7-2          base              897 k
 tk                      i386       8.4.7-2          base              838 k
 trac                    noarch     0.10.3.1-2.rf.sme01  smedev            665 k
 umb-scheme              i386       3.2-36.EL4       base              967 k
 xorg-x11-Mesa-libGL     i386       6.8.2-1.EL.13.37.7  updates           379 k
 xorg-x11-libs           i386       6.8.2-1.EL.13.37.7  updates           2.7 M

Transaction Summary
=============================================================================
Install     24 Package(s)
Update       0 Package(s)
Remove       0 Package(s)
Total download size: 13 M
Is this ok [y/N]:



Regards,

Marco
Adelaide - Australia

Offline cactus

  • *
  • 4,880
    • http://www.snetram.nl
Re: Problem at install smeserver-trac
« Reply #26 on: April 07, 2007, 09:41:20 AM »
Quote from: "thf"
I was asked to remove some packages from my repository as it duplicated packages from more authoritative repositories :-)
Thanks very much, nice to know you followed my request!
Be careful whose advice you buy, but be patient with those who supply it. Advice is a form of nostalgia, dispensing it is a way of fishing the past from the disposal, wiping it off, painting over the ugly parts and recycling it for more than its worth ~ Baz Luhrmann - Everybody's Free (To Wear Sunscreen)

pabbec

Problem solved.
« Reply #27 on: April 07, 2007, 05:36:56 PM »
Thanks for your answer. I tired again with the command:

Code: [Select]

yum --enablerepo=smedev --enablerepo=through-ip install smeserver-trac


but the problem persisted:

Code: [Select]

Error: Cannot find a valid baseurl for repo: snetram


In order to solve it, I edited /etc/yum.conf and cleared the # on the line baseurl of section [snetram] of this file.

After that, I tried again with the command, TRAC was installed on my server. :).

Re: Problem solved.
« Reply #28 on: April 08, 2007, 02:49:37 AM »
Quote from: "pabbec"

Error: Cannot find a valid baseurl for repo: snetram


This seems more an issue with that you have setup access to the snetram repository rather than a problem with the smeserver-trac contrib.

I don't think you need the snetram repository, because as far as I know, the smeserver-subversion contrib comes from the smedev repository.

Marco
Adelaide - Australia

Offline cactus

  • *
  • 4,880
    • http://www.snetram.nl
Re: Problem solved.
« Reply #29 on: April 08, 2007, 06:16:26 PM »
Quote from: "thf"
Quote from: "pabbec"

Error: Cannot find a valid baseurl for repo: snetram


This seems more an issue with that you have setup access to the snetram repository rather than a problem with the smeserver-trac contrib.

This is caused by two things:[list=1]
  • You have enabled the snetram repository by default which you should not do, if you need software from this repository you should explicitly enable this by adding the repository on the server shell line using the --enablerepo=snetram parameter or temporarily enable it in the server-manager
  • Probably the url to the mirrorlist is incorrect as the devteam corrected a webserver configuration error which changed the address where my contrib directory lives. The command to configure my repository can be found in the wiki: http://wiki.contribs.org/Snetram[/list:o]
    Quote from: "thf"
    I don't think you need the snetram repository, because as far as I know, the smeserver-subversion contrib comes from the smedev repository.
    Yes I moved smeserver-subversion to the smedev repository a while ago so technically speeking you don't really need it anymore.
Be careful whose advice you buy, but be patient with those who supply it. Advice is a form of nostalgia, dispensing it is a way of fishing the past from the disposal, wiping it off, painting over the ugly parts and recycling it for more than its worth ~ Baz Luhrmann - Everybody's Free (To Wear Sunscreen)