redmine in subdirectories

Links you need to read to have redmine working your way.

• The basic stuff for debian ( with lighttp ) is here
• but if you don't want to use vhost you will need these lines to show you how to set several RoR applications in subdirectories
• even other snips can help you to understand the problems and solutions behind

egroupware dependencies

if you run into

CreateObject('emailadmin.bo'): Cant instanciate class!!!
mail_server(Array)

while trying a selected/uncomplete egroupware setup, that seems to be due to a missing dependency. Just install egroupware-emailadmin and you are done.

apt-get install egroupware-emailadmin

reset mysql root password

this is for debian... and it is so straight forward... Here a copy and paste...

# dpkg -l mysql-server* | grep ii
ii  mysql-server                        5.0.51a-3                     MySQL database server (meta package depending on the latest version)
ii  mysql-server-5.0                    5.0.51a-3                     MySQL database server binaries


# dpkg-reconfigure mysql-server-5.0
Stopping MySQL database server: mysqld.
[debconf screen appears]

 While not mandatory, it is highly       
 recommended that you set a password     
 for the MySQL administrative "root"     
 user.                                   
                                         
 If that field is left blank, the        
 password will not be changed.           
                                         
 New password for the MySQL "root"       
 user:                                   
 _______________________________________ 
                                         
                                     


Stopping MySQL database server: mysqld.
Stopping MySQL database server: mysqld.
Starting MySQL database server: mysqld.
Checking for corrupt, not cleanly closed and upgrade needing tables..

...one click closer from the original post. In the same page you will find other procedures including a windows solution. Credits to anonymous, the original poster.

roundup issue tracker

Roundup is a said to be a simple issue tracker. Some documentation exist about integrating subversion and roundup that being my target. However i had some self imposed limitations:

• Use debian packages
• No smtp server, and i dont want to have any running

After some hours of work, i came out with this step by step solution.

Install roundup:

prompt# apt-get install roundup

Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
...
Selecting previously deselected package roundup.
(Reading database ... 19361 files and directories currently installed.)
Unpacking roundup (from .../roundup_1.4.4-2_all.deb) ...
Processing triggers for man-db ...
Setting up roundup (1.4.4-2) ...
Starting Roundup HTTP-Server: roundup-server.

OK, so that!. Now i have a roundup-server running. But no Tracker. You see, the Tracker is where the info will be stored, the issue repository, the database. So i need to create a tracker. My setup only requires one tracker, and i want to have it under /var/rounup/trackername. This is what i did.

root@server:/var/roundup# roundup-admin install
Enter tracker home: /var/roundup/trackername
Templates: minimal, classic
Select template [classic]: classic
Back ends: anydbm, sqlite
Select backend [anydbm]: sqlite

---------------------------------------------------------------------------
 You should now edit the tracker configuration file:
   /var/roundup/trackername/config.ini
 ... at a minimum, you must set following options:
   [mail]: domain, host
   [tracker]: web

 If you wish to modify the database schema,
 you should also edit the schema file:
   /var/roundup/trackername/schema.py
 You may also change the database initialisation file:
   /var/roundup/trackername/initial_data.py
 ... see the documentation on customizing for more information.

 You MUST run the "roundup-admin initialise" command once you've performed
 the above steps.
---------------------------------------------------------------------------

There it is. My first Tracker. Still some edit has to be done. The most important value to set, since i do not have/want SMTP around is in the [mail]::debug...

[mail]
# Setting this option makes Roundup to write all outgoing email
# messages to this file *instead* of sending them.
# This option has the same effect as environment variable SENDMAILDEBUG.
# Environment variable takes precedence.
# The path may be either absolute or relative
# to the directory containig this config file.
# Default:
debug = reponame.mail.log

With this configuration, all the mails sent to the admin (with setup errors / warnings, etc) will end it that file.

root@server:/var/roundup# roundup-admin initialise
Enter tracker home: /var/roundup/trackername
Admin Password:*****
       Confirm:*****

Next step is to make the Tracker available throught the roundup server. We have to add these lines on /etc/roundup/roundup-server.ini

[trackers]
trackername = /var/roundup/trackername

and restart the roundup server

/etc/init.d/roundup restart

watch /var/log/roundup/roundup.log and /var/log/roundup/reponame.mails.log for errors. finally one of the problems i left was permision related...

    chmod roundup.roundup -R /var/roundup/trackname

AptPinning - Debian Wiki

Some times you need some packages from a more diferent Debian flavor. Ok. maybe you don't, but right now i do, and pinning seems to be the answer.

I'll give it a try (want to test subversion 1.5 for a while), and then i will update this entry.

UPDATE: I did not have to guts to do it. Replacing libc right now does not seem like a good option just now.

tools and tools

deborphan and orphaner