directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <>
Subject [jira] Commented: (DIRSERVER-749) fix issues with apacheds RPM to get it working out of the box
Date Mon, 02 Oct 2006 17:22:21 GMT
    [ ] 
Emmanuel Lecharny commented on DIRSERVER-749:

Hi bastiaan,

The main problem we are having right now is that we are busy closing the 1.0, and this is
the reason your patches have been postponned.

We would be very please to allow you to commit your changes into a branch, but you have to
know that the election of a new committer is a process that is verrrrrrrryyyyyyy long (let
say at least one month). We have to propose you as a committer first, then launch a vote,
then wait for you to sign a CLA, then enter the Apache administrative loop, and finally, you
will be drying dead in the desert before being able to commit a patch...

What I could suggest is that we work in pair one of the next day to fix this issue, I have
a FC5 on a computer, and as I have done my homework lately ( newer ASN.1 codec has been committed
yesturday), I will be available to help out this problem.

I'm in France, so my TZ is UTC + 2, but I'm working during nigh (from 8 PM to 1 AM UTC)

Feel free to contact me if needed !


> fix issues with apacheds RPM to get it working out of the box
> -------------------------------------------------------------
>                 Key: DIRSERVER-749
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>          Components: installer-plugin
>    Affects Versions: 1.0-RC4
>         Environment: linux
>            Reporter: Bastiaan Bakker
>         Assigned To: Alex Karasulu
>            Priority: Minor
>             Fix For: 1.1.0, 1.0.1
>         Attachments: apacheds-branch-1.0-server-installers-rpmfix.patch, apacheds-daemon-trunk-rpmfix.patch
> The apacheds RPM has several issues that prevent it from running out of the box:
> * the init script fails to run because APACHEDS_USER is set to $USER, which is not defined
at boot time
> * the init script fails to run bevause JAVA_HOME is not defined
> * the init script it is not registered to the init subsystem with chkconfig or similar
> * the config files are not marked as such, causing them to be silently overwritten when
one upgrades the RPM
> * the RPM filename is not conform conventions: ${name}-${version}-${release}.${arch}.rpm
> * the location of the files (/usr/local/apacheds-1.0_RC4) is version dependent, making
upgrades cumbsome. The admin has to relocate the partitions and config files on every updgrade.
> * the sources and docs are included in the rpm, even though they are not necessary for
> The RPM build mechanism for apacheds also has some issues:
> * runs rpmbuild as root, which is frowned upon by RPM gurus for security and safety reasons.
> * the generated src.rpm is not self contained, ie. one cannot do a 'rpmbuild --rebuild'
with it. 
> * the sudo mechanism is totally unnecessary

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message