It would be great if there was an ebuild for feodra directory server. I am currently using open-ldap which is difficult to configure, especially acls and seems flaky. My database gets corrupt every now and then and then needs to be restored. thanks Reproducible: Always Steps to Reproduce: 1. 2. 3. See http://directory.fedora.redhat.com/wiki/Main_Page
1.0 version bump.
Here's another request for Fedora DS ebuilds.
Make mine #3 pleez! I'm going to pick through the rpm this coming week and see what i can do about helping with an ebuild. Hopefully some others drum up some interest
(In reply to comment #3) > I'm going to pick through the rpm this coming week and see what you need is http://directory.fedora.redhat.com/wiki/Building#Example confirmed it compiled successfully and it was not so difficult. possible problems are: * it doesn't use installed libraries or software(uses its own db-4.*, net-snmp) * many components to handle * dependencies are unclear(you need zip to build)
I'd like to see to an ebuild too! :)
I'd like to see an ebuild too!
Created attachment 74427 [details] fedora ds 1.0 ebuild and patches incomplete (!) ebuild ccache breaks it, distcc is unsupported
man -- i really need this ebuild. Wish I could do it myself. Just got screwed by openldap 2.3.19 upgrade. Will someone please deliver us from this openldap hell? thanks
*** Bug 128019 has been marked as a duplicate of this bug. ***
HI all, I installed binaries of Fedora DS, on Gentoo AMD64 and i686, by using the by using rpm. It simply works. This is my init script (which is not good if you use certificates): #!/sbin/runscript # Copyright 1999-2006 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 # $Header: $ #Modify this parameter depending on your setup # This is usually the hostname. MYSLAPD=gentoo DSPATH=/opt/fedora-ds export MYSLAPD DSPATH depend() { need net use dns } start() { ebegin "Starting Fedora DS" start-stop-daemon --start --quiet \ --make-pidfile --pidfile /var/run/fedora-ds.pid \ --exec ${DSPATH}/slapd-${MYSLAPD}/start-slapd eend $? ebegin "Starting Fedora Admin Server" start-stop-daemon --start --quiet \ --make-pidfile --pidfile /var/run/fedora-admsrv.pid \ --exec ${DSPATH}/start-admin eend $? } stop() { ebegin "Stopping Fedora Admin Server" start-stop-daemon --start --quiet \ --pidfile /var/run/fedora-admsrv.pid \ --exec ${DSPATH}/stop-admin eend $? ebegin "Stopping Fedora DS" start-stop-daemon --start --quiet \ --pidfile /var/run/fedora-ds.pid \ --exec ${DSPATH}/slapd-${MYSLAPD}/stop-slapd eend $? } restart() { svc_stop svc_start }
bump
The krb5 inside this won't build.. any change to get the package to use external mit-krb5 package? The latest version of fedora-ds is 1.0.4.
any news regarding a net-nds/fedora-ds-1.0.4 ebuild?
Seems to have java stuff so should be checked with use before adding to the tree.
What's the status on this one? Anybody working on the ebuild? Sunrise maybe?
I was just able to build this using the dsbuild tarball provided by the fedora folks. I did have to change a few make files and create one symlink but other then this it built fine. I haven't tried to run it yet though. I removed -ltermcap from four or five make files and the symlink I made was for /usr/sbin/apxs2 to /usr/sbin/apxs. That was done to satisfy mod_nss.
Ok, so I rebuilt this and took some notes to help out. First, i did try emerging the termcap from portage, but this didn't seem to make any difference. So, here are the list of files I edited -ltermcap out of: $PATH/dsbuild-fds104/ds/setuputil/work/fedora-setuputil-1.0.3/installer/unix/Makefile $PATH/dsbuild-fds104/ds/adminserver/work/fedora-adminserver-1.0.3/admservi/newinst/src/Makefile $PATH/dsbuild-fds104/ds/ldapserver/work/fedora-ds-1.0.4/ldap/cm/newinst/Makefile $PATH of crouse is up to you, mine happened to be /usr/local/src/ldap. The APXS business was easy too. I just changed into the mod_nss dir and did a configure like this: ./confiure --with-apxs=/usr/sbin/apxs2 and then I did a make and changed back to the $PATH/dsbuild-fds104/meta/ds dir to continue the build process. The server seems to fire up but I also built it with the NOJAVA=1 option since it's just going to be a server. It starts up all fine and I will be testing with it shortly. I don't know how to make an ebuild file. I may investigate this but I have more pressing issues right now.
Created attachment 110645 [details] net-nds/fedora-ds-adminutil/fedora-ds-adminutil-1.0.4.ebuild I continued to work on from the giant ebuild. This is the first one I got working, it uses external libs. I managed to get this one compiled, I've no idea if it really works. I'll try to modularize the rest as well. Please test to see if it works and look for updates in the following days.
Created attachment 110657 [details] net-nds/fedora-ds-adminutil/fedora-ds-adminutil-1.0.4.ebuild Updated. Use this.
Created attachment 110675 [details] net-nds/fedora-ds-mozilla/fedora-ds-mozilla-1.0.3.ebuild I figured this one is the first to install. It builds several files to which the later packages link. I'm not sure if I got everything right the first time, probably not. :D Emerge tells me this after a successful install, I don't know if the problem is in the ebuild or in the code itself (it seems it's from gcc 2> stream): * QA Notice: Package has poor programming practices which may compile * fine but exhibit random runtime failures. * ../../../../pr/src/io/prfdcach.c:165: warning: dereferencing type-punned pointer will break strict-aliasing rules ../../../../pr/src/io/prfdcach.c:224: warning: dereferencing type-punned pointer will break strict-aliasing rules ../../../../pr/src/misc/prthinfo.c:109: warning: dereferencing type-punned pointer will break strict-aliasing rules ../../../../pr/src/misc/prthinfo.c:235: warning: dereferencing type-punned pointer will break strict-aliasing rules ../../../../pr/src/pthreads/ptio.c:899: warning: dereferencing type-punned pointer will break strict-aliasing rules ../../../dbm/src/ndbm.c:100: warning: dereferencing type-punned pointer will break strict-aliasing rules ../../../dbm/src/ndbm.c:100: warning: dereferencing type-punned pointer will break strict-aliasing rules ../../../dbm/src/ndbm.c:119: warning: dereferencing type-punned pointer will break strict-aliasing rules ../../../dbm/src/ndbm.c:119: warning: dereferencing type-punned pointer will break strict-aliasing rules ../../../dbm/src/ndbm.c:136: warning: dereferencing type-punned pointer will break strict-aliasing rules ../../../dbm/src/ndbm.c:136: warning: dereferencing type-punned pointer will break strict-aliasing rules ../../../dbm/src/ndbm.c:151: warning: dereferencing type-punned pointer will break strict-aliasing rules ../../../dbm/src/ndbm.c:167: warning: dereferencing type-punned pointer will break strict-aliasing rules ../../../dbm/src/ndbm.c:167: warning: dereferencing type-punned pointer will break strict-aliasing rules pkistore.c:318: warning: dereferencing type-punned pointer will break strict-aliasing rules pkistore.c:452: warning: dereferencing type-punned pointer will break strict-aliasing rules pkistore.c:500: warning: dereferencing type-punned pointer will break strict-aliasing rules pk11load.c:306: warning: dereferencing type-punned pointer will break strict-aliasing rules sslsnce.c:1085: warning: dereferencing type-punned pointer will break strict-aliasing rules sslsnce.c:1086: warning: dereferencing type-punned pointer will break strict-aliasing rules sslsnce.c:1087: warning: dereferencing type-punned pointer will break strict-aliasing rules sslsnce.c:1088: warning: dereferencing type-punned pointer will break strict-aliasing rules sslsnce.c:1089: warning: dereferencing type-punned pointer will break strict-aliasing rules sslsnce.c:1090: warning: dereferencing type-punned pointer will break strict-aliasing rules sslsnce.c:1091: warning: dereferencing type-punned pointer will break strict-aliasing rules sslsnce.c:1364: warning: dereferencing type-punned pointer will break strict-aliasing rules sslsnce.c:1365: warning: dereferencing type-punned pointer will break strict-aliasing rules sslsnce.c:1366: warning: dereferencing type-punned pointer will break strict-aliasing rules sslsnce.c:1367: warning: dereferencing type-punned pointer will break strict-aliasing rules sslsnce.c:1368: warning: dereferencing type-punned pointer will break strict-aliasing rules sslsnce.c:1369: warning: dereferencing type-punned pointer will break strict-aliasing rules sslsnce.c:1370: warning: dereferencing type-punned pointer will break strict-aliasing rules cmsattr.c:95: warning: dereferencing type-punned pointer will break strict-aliasing rules cmsattr.c:132: warning: dereferencing type-punned pointer will break strict-aliasing rules cmsenvdata.c:139: warning: dereferencing type-punned pointer will break strict-aliasing rules cmsrecinfo.c:231: warning: dereferencing type-punned pointer will break strict-aliasing rules cmssigdata.c:766: warning: dereferencing type-punned pointer will break strict-aliasing rules cmssigdata.c:810: warning: dereferencing type-punned pointer will break strict-aliasing rules cmssigdata.c:826: warning: dereferencing type-punned pointer will break strict-aliasing rules cmssigdata.c:864: warning: dereferencing type-punned pointer will break strict-aliasing rules cmssigdata.c:1037: warning: dereferencing type-punned pointer will break strict-aliasing rules cmssigdata.c:1039: warning: dereferencing type-punned pointer will break strict-aliasing rules blapitest.c:3383: warning: dereferencing type-punned pointer will break strict-aliasing rules install.c:443: warning: dereferencing type-punned pointer will break strict-aliasing rules ldappr-io.c:138: warning: dereferencing type-punned pointer will break strict-aliasing rules clientinit.c:253: warning: dereferencing type-punned pointer will break strict-aliasing rules clientinit.c:254: warning: dereferencing type-punned pointer will break strict-aliasing rules clientinit.c:255: warning: dereferencing type-punned pointer will break strict-aliasing rules clientinit.c:256: warning: dereferencing type-punned pointer will break strict-aliasing rules clientinit.c:257: warning: dereferencing type-punned pointer will break strict-aliasing rules clientinit.c:277: warning: dereferencing type-punned pointer will break strict-aliasing rules clientinit.c:278: warning: dereferencing type-punned pointer will break strict-aliasing rules clientinit.c:279: warning: dereferencing type-punned pointer will break strict-aliasing rules ldapsinit.c:233: warning: dereferencing type-punned pointer will break strict-aliasing rules
Created attachment 110714 [details] net-nds/fedora-ds-adminutil/fedora-ds-adminutil-1.0.4.ebuild Work in progress.
Created attachment 110956 [details] net-nds/fedora-ds-mozilla/fedora-ds-mozilla-1.0.3.ebuild
Created attachment 110957 [details] net-nds/fedora-ds-adminutil/fedora-ds-adminutil-1.0.4.ebuild
Created attachment 110959 [details] net-nds/fedora-ds-setuputil/fedora-ds-setuputil-1.0.3.ebuild
These packages build fine. I don't have time to develop these right now, I hope someone else would continue from here. I'm not very good at writing such complicated ebuilds. The next step would be to install the Apache modules. However, these link to adminutil, and as I separated the libs and headers, the configure script won't accept this, it wants them both to be on the same path. Symlinks perhaps? I'm going to login to a root account on a Fedora box and try to install the rpms for now. :/
(In reply to comment #25) > These packages build fine. I don't have time to develop these right now, I hope > someone else would continue from here. I'm not very good at writing such > complicated ebuilds. Hallo I am working at the moment on some new ebuilds: I only have the required libs in the tree to get the ds compile (ebuild for ds will be added this week) dev-libs/svrcore dev-libs/mozldap dev-perl/perl-mozldap the overlay is located at svn co http://mars.arge.at/svn/linamh/trunk/linamh/ so my plan is to finisch the ebuild for the ds this week and start working on the rest next week. wfg Mario
(In reply to comment #26) > > dev-libs/svrcore > dev-libs/mozldap > dev-perl/perl-mozldap > Adding perl to CC so that they can comment.
> so my plan is to finisch the ebuild for the ds this week and start working on > the rest next week. The ebuild for fedora-ds-base is in the tree. net-nds/fedora-ds-base (is the suggested name from the fedora project) net-nds/fedora-ds-adminutil (the suggested name is adminutils ? ) the server also includes a nice initscript with instance support only setup the server with setup-ds.pl and add the instance name to /etc/conf.d/fedora-ds the fedora-ds-setuputil is deprecated so lets start adding the complicated ebuilds (java + apache + cgi + perl + ....) all packages are using the todays snapshot for all packages with autotools support (waiting for the fedora-ds 1.1 release) wfg Mario
Created attachment 127259 [details] dev-libs/svrcore/svrcore-4.0.4.ebuild My ebuilds, based on Fedora spec.
Created attachment 127260 [details] dev-libs/mozldap/mozldap-6.0.4.ebuild
Created attachment 127262 [details] net-nds/fedora-ds-adminutil/fedora-ds-adminutil-1.1.2_pre20070808.ebuild
Created attachment 127263 [details] net-nds/fedora-ds/fedora-ds-1.1.0_pre20070808.ebuild
Created attachment 127265 [details] net-nds/fedora-ds/files/fedora-ds.initd
Created attachment 127266 [details] net-nds/fedora-ds/files/fedora-ds.confd
Created attachment 127269 [details] net-nds/fedora-ds-setuputil/fedora-ds-setuputil-1.1.0_pre20070808.ebuild
(In reply to comment #35) > Created an attachment (id=127269) [edit] > net-nds/fedora-ds-setuputil/fedora-ds-setuputil-1.1.0_pre20070808.ebuild > the setup utils are offical deprecated by the fedora-ds 1.1 so the setuputils are not required.
(In reply to comment #28) > net-nds/fedora-ds-adminutil (the suggested name is adminutils ? ) had to move the fedora-ds-adminutil to dev-libs/adminutil (yes fedora was right with ther suggestion ) > so lets start adding the complicated ebuilds (java + apache + cgi + perl + > ....) > the new additions to the tree are www-apache/mod_nss www-apache/mod_admserv can someone plz test this mod_*'s mainly the default configfiles if there are some false asumptions. wfg Mario
akira fedora # emerge -pv www-apache/mod_admserv www-apache/mod_nss These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] net-www/apache-2.0.58-r2 USE="apache2 mpm-worker ssl -debug -doc -ldap -mpm-itk -mpm-leader -mpm-peruser -mpm-prefork -mpm-threadpool (-selinux) -static-modules -threads" 0 kB [ebuild N ] dev-libs/adminutil-1.1.4.20070807 USE="ipv6 sasl -debug" 302 kB [1] [ebuild N ] www-apache/mod_admserv-1.0.20070807 USE="ssl" 230 kB [1] [ebuild N ] www-apache/mod_nss-1.0.20070807 USE="ssl" 293 kB [1] Total: 4 packages (4 new), Size of downloads: 824 kB The first two build just fine but i'm having trouble downloading the packages for the last two. Both distfiles.gentoo.org and distro.ibiblio.org give me a 404 and I am not allowing FTP here at work.
(In reply to comment #38) > The first two build just fine but i'm having trouble downloading the packages > for the last two. Both distfiles.gentoo.org and distro.ibiblio.org give me a > 404 and I am not allowing FTP here at work. > i have added an http mirror to the list. at the moment i am on working out what would be the best way for handling fds-admin the requirement for admin is that the apache that is running the admin soft should use the mozldap ..stop.. the fedora way: they are using the system apache with LD_PRELOAD=/usr/lib/mozldap/libldap60.so to overrride all openldap functions. so they have an initscript that is mainly an apache start script with the override. the gentoo way: (the way it should be; i think) as gentoo has this nice USE flags add a new one "mozldap" this use flag should be used by apr-utils & apache this way these packages would be compiled aginst mozldap and no need for this odd override then have a init script (fedora-ds-admin only start admin server) with befor apache2 & after fedora-ds apr-utils must be patched to detect mozldap60 or mozldap must be downgradet to 50 so what way we are going? wfg Mario
My vote would be the gentoo way. That is indeed why we do have USE flags.
I downloaded the files you had sent me but they don't pass the checks for building. It looks like the file size has changed and not been updated, or I got the wrong one. akira fedora # emerge -v net-nds/fedora-ds-base These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] net-nds/fedora-ds-base-1.1.0.20070807 USE="ipv6 sasl -debug -snmp" 0 kB [1] Total: 1 package (1 new), Size of downloads: 0 kB Portage overlays: >>> Emerging (1 of 1) net-nds/fedora-ds-base-1.1.0.20070807 to / * fedora-ds-1.1.0-20070807.tar.bz2 MD5 ;-) ... [ ok ] * fedora-ds-1.1.0-20070807.tar.bz2 RMD160 ;-) ... [ ok ] * fedora-ds-1.1.0-20070807.tar.bz2 SHA1 ;-) ... [ ok ] * fedora-ds-1.1.0-20070807.tar.bz2 SHA256 ;-) ... [ ok ] * fedora-ds-1.1.0-20070807.tar.bz2 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ !! ] !!! Digest verification failed: !!! /usr/local/portage/fedora/net-nds/fedora-ds-base/files/fedora-ds-cvs.sh !!! Reason: Filesize does not match recorded size !!! Got: 346 !!! Expected: 334
why not creating a binary package: net-nds/fedora-ds-bin and closing this ticket after 2 years ?? There is already binary package either for x86 and amd64. This ticket is 2 years old and I don't understand where you want to get on. cheeers
(In reply to comment #42) > why not creating a binary package: net-nds/fedora-ds-bin and closing this > ticket after 2 years ?? > There is already binary package either for x86 and amd64. > This ticket is 2 years old and I don't understand where you want to get on. > > cheeers > the fedora-ds already works ok. i am working on the management system that will become a new framework for managing the next versions of RHEL.
(In reply to comment #43) > (In reply to comment #42) > > why not creating a binary package: net-nds/fedora-ds-bin and closing this > > ticket after 2 years ?? > > There is already binary package either for x86 and amd64. > > This ticket is 2 years old and I don't understand where you want to get on. > > > > cheeers > > > the fedora-ds already works ok. > i am working on the management system that will become a new framework for > managing the next versions of RHEL. > Cool!... but I hope, once you finish, you'll not have to work again to create an ebuild for opends :) http://www.opends.org/ http://blogs.sun.com/DirectoryManager/entry/opends_0_9_0_is This software derives from the Netscape DS (like Fedora-ds), it's licensed with CDDL license and it will replace SunDS. cheers
(In reply to comment #44) > Cool!... but I hope, once you finish, you'll not have to work again to create > an ebuild for opends :) > http://www.opends.org/ > http://blogs.sun.com/DirectoryManager/entry/opends_0_9_0_is > This software derives from the Netscape DS (like Fedora-ds), it's licensed with > CDDL license and it will replace SunDS. > cheers > i dont think this server derives from Netscape ! the whole server is written in java i have not found any c Code like in fedora-ds
The OpenDS isn't related to the fedora-ds as far as I can tell. If there are people who want the OpenDS to run LDAP, they are most welcome to use it, create ebuilds etc. There are others interested in the fedora-ds because of it's maturity level and because there is already an investment in understanding it.
(In reply to comment #40) > My vote would be the gentoo way. That is indeed why we do have USE flags. > the apr-util & apache are now mozldap aware and the modified ebuilds are already in my tree the apr-util patch is already send upstream (not included yet) only add mozldap to your useflags the next step is to create the ebuild for the admin server and module so not that far away from the final ebuilds my plan is to have testing ebuilds for the final fds release
i have added a basic fedora-ds-admin ebuild to my tree have removed the start/stop/restart -ds-admin scripts as the apache server is build against mozldap the apache confs are in /etc/dirsrv/admin-serv/ could someone with apache config knowhow create some basic working gentoo style configs that i can use as a save default install my idee is to have 47_mod_nss -> www-apache/mod_nss 48_mod_restartd -> www-apache/mod_restartd 49_mod_admserv -> net-nds/fedora-ds-admin console.conf ?
the fedora management framework is now in my tree dev-java/idm-console-framework -> the management framwork only merge app-admin/fedora-admin-console -> the adminserver plugin for idm app-admin/fedora-ds-console -> the directory server plugin for idm app-admin/fedora-idm-console -> the artwork amd startscript for idm the name of of the brad changed from fedora-ds to dirsrv migrate-ds.pl
Any progress here? Mario Fetka, is your overlay accessible?
(In reply to comment #50) > Any progress here? > > Mario Fetka, is your overlay accessible? > yes my overlay is accesssibel. but i am stuck at the admin server with the apache eclass patch it would be great if someone with more knowlege at eclass design can have a look at the eclass and arp-util patch yes its working apache build against mozldap. the overlay only holds the management console and the server but not the admin server my overlay file for layman: http://ftp.mars.arge.at/pub/overlay/linamh-overlay.xml be warnde this overlay also holds some other ebuilds
mark layman # layman -a linamh * Running command "/usr/bin/svn co "http://mars.arge.at/svn/linamh/trunk/linamh/" "/usr/portage/local/layman/linamh""... svn: PROPFIND request failed on '/svn/linamh/trunk/linamh' svn: PROPFIND of '/svn/linamh/trunk/linamh': 405 Method Not Allowed (http://mars.arge.at) * Failed to add overlay "linamh". * Error was: Adding the overlay failed!
(In reply to comment #52) > mark layman # layman -a linamh > * Running command "/usr/bin/svn co > "http://mars.arge.at/svn/linamh/trunk/linamh/" > "/usr/portage/local/layman/linamh""... > svn: PROPFIND request failed on '/svn/linamh/trunk/linamh' > svn: PROPFIND of '/svn/linamh/trunk/linamh': 405 Method Not Allowed > (http://mars.arge.at) > * Failed to add overlay "linamh". > * Error was: Adding the overlay failed! > i am having some server problems i will correct in a view minutes
dirsrv-admin slowly starts working: the admin server (apache2 build against mozldap) starts working. i was able to connect with the idm-console to the admin-server but then complains about not finding some jars so there is some progress the progress can be folled in the overlay.
fedora-ds-base-1.1.1 does not build without sasl: # USE="-sasl" emerge <....> <...> checking for --with-sasl... no checking for --with-sasl-inc... no checking for --with-sasl-lib... no checking for sasl.h... no configure: error: sasl not found, specify with --with-sasl. amd64
(In reply to comment #55) > fedora-ds-base-1.1.1 does not build without sasl: > > > # USE="-sasl" emerge <....> > <...> > checking for --with-sasl... no > checking for --with-sasl-inc... no > checking for --with-sasl-lib... no > checking for sasl.h... no > configure: error: sasl not found, specify with --with-sasl. > > amd64 > thx updated ebuild to depend on sals
Created attachment 163221 [details] fixed fedora-ds-base ebuild from svn Tried to fix compilation without sasl (not tested, ebuild could be broken). Added missing dependency: dev-perl/perl-mozldap
Created attachment 163230 [details] added missing dependencies
Hi Mario. I'm getting following error after using setup-ds-admin.pl: [08/08/19:06:27:10] - [Setup] Info Are you ready to set up your servers? [08/08/19:06:27:13] - [Setup] Info yes [08/08/19:06:27:13] - [Setup] Info Creating directory server . . . [08/08/19:06:27:16] - [Setup] Info Your new DS instance 'edir01' was successfully created. [08/08/19:06:27:16] - [Setup] Info Creating the configuration directory server . . . [08/08/19:06:27:16] - [Setup] Info Beginning Admin Server creation . . . [08/08/19:06:27:16] - [Setup] Info Creating Admin Server files and directories . . . [08/08/19:06:27:16] - [Setup] Info Updating adm.conf . . . [08/08/19:06:27:16] - [Setup] Info Updating admpw . . . [08/08/19:06:27:16] - [Setup] Info Registering admin server with the configuration directory server . . . [08/08/19:06:27:17] - [Setup] Info Updating adm.conf with information from configuration directory server . . . [08/08/19:06:27:17] - [Setup] Info Updating the configuration for the httpd engine . . . [08/08/19:06:27:17] - [Setup] Info Starting admin server . . . [08/08/19:06:27:17] - [Setup] Info output: sh: /usr/sbin/start-ds-admin: No such file or directory [08/08/19:06:27:17] - [Setup] Fatal Failed to create and configure the admin server [08/08/19:06:27:17] - [Setup] Fatal Exiting . . . As I can see, all configuration files on /etc/dirserv/admin-serv/ were updated seccesfully, but I can't find start-ds-admin anywhere. dirserv seems to work well, at least I can `telnet localhost ldap`
> As I can see, all configuration files on /etc/dirserv/admin-serv/ were updated > seccesfully, but I can't find start-ds-admin anywhere. > > dirserv seems to work well, at least I can `telnet localhost ldap` > plz update svn: the fedora-ds-admin now works the missing script were removed on the old ebuilds (hard coded paths; this changed with 1.1.1 1.1.5) the use flags are removed now as the m4 macros aren't working on gentoo there is no switch like --without-sasl if its on the system its used even with USE=-sasl Mario
Hello, There seems to be a checksum issue with the ds-console tarball: >>> Downloading 'http://directory.fedoraproject.org/sources/fedora-ds-console-1.1.1.tar.bz2' --14:29:56-- http://directory.fedoraproject.org/sources/fedora-ds-console-1.1.1.tar.bz2 => `/usr/portage/distfiles/fedora-ds-console-1.1.1.tar.bz2' Resolving directory.fedoraproject.org... 209.132.176.189 Connecting to directory.fedoraproject.org|209.132.176.189|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 803,125 (784K) [application/x-bzip2] 100%[===========================================================================================>] 803,125 221.28K/s ETA 00:00 14:30:00 (203.10 KB/s) - `/usr/portage/distfiles/fedora-ds-console-1.1.1.tar.bz2' saved [803125/803125] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking fedora-ds-console-1.1.1.tar.bz2 ;-) ... [ !! ] !!! Digest verification failed: !!! /usr/portage/distfiles/fedora-ds-console-1.1.1.tar.bz2 !!! Reason: Filesize does not match recorded size !!! Got: 803125 !!! Expected: 802587
(In reply to comment #61) > Hello, > > There seems to be a checksum issue with the ds-console tarball: > is corrected thx for report.
Hi Mario, I'm still getting the same error: >>> Downloading 'http://directory.fedoraproject.org/sources/fedora-ds-console-1.1.1.tar.bz2' --09:37:01-- http://directory.fedoraproject.org/sources/fedora-ds-console-1.1.1.tar.bz2 => `/usr/portage/distfiles/fedora-ds-console-1.1.1.tar.bz2' Resolving directory.fedoraproject.org... 209.132.176.189 Connecting to directory.fedoraproject.org|209.132.176.189|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 803,125 (784K) [application/x-bzip2] 100%[===========================================================================================>] 803,125 350.77K/s 09:37:04 (349.91 KB/s) - `/usr/portage/distfiles/fedora-ds-console-1.1.1.tar.bz2' saved [803125/803125] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking fedora-ds-console-1.1.1.tar.bz2 ;-) ... [ !! ] !!! Digest verification failed: !!! /usr/portage/distfiles/fedora-ds-console-1.1.1.tar.bz2 !!! Reason: Filesize does not match recorded size !!! Got: 803125 !!! Expected: 802587 * GNU info directory index is up-to-date. Thank you, Erric
Never mind, It was me. I didn't do a layman -S :D However: checking for --with-httpd... using /usr/sbin/apache2 grep: /usr//etc/apache2/httpd.conf: No such file or directory configure: error: mime.types file not found !!! Please attach the following file when seeking support: !!! /var/tmp/portage/net-nds/fedora-ds-admin-1.1.5-r1/work/fedora-ds-admin-1.1.5/config.log * * ERROR: net-nds/fedora-ds-admin-1.1.5-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2502: Called econf 'src_compile' 'src_compile' '--disable-debug' * ebuild.sh, line 513: Called die * The specific snippet of code: * die "econf failed" * The die message: * econf failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/net-nds/fedora-ds-admin-1.1.5-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/net-nds/fedora-ds-admin-1.1.5-r1/temp/environment'. * This ebuild is from an overlay: '/usr/portage/local/layman/linamh/' Looks like a simple path issue. --Erric
(In reply to comment #64) > checking for --with-httpd... using /usr/sbin/apache2 > grep: /usr//etc/apache2/httpd.conf: No such file or directory > configure: error: mime.types file not found added missing depend on app-misc/mime-types thx for report
Mario, Thank you for updating this. It all builds correctly now on my system. Now to see if it runs ok :D Erric hostname # equery list fedora [ Searching for package 'fedora' in all categories among: ] * installed packages [I--] [ ~] app-admin/fedora-admin-console-1.1.1 (1.1) [I--] [ ~] app-admin/fedora-ds-console-1.1.1 (1.1) [I--] [ ~] app-admin/fedora-idm-console-1.1.1 (1.1) [I--] [ ~] net-nds/fedora-ds-admin-1.1.5-r1 (0) [I--] [ ~] net-nds/fedora-ds-base-1.1.1-r1 (0)
(In reply to comment #66) > Mario, > > Thank you for updating this. It all builds correctly now on my system. Now to > see if it runs ok :D > > Erric > > hostname # equery list fedora > [ Searching for package 'fedora' in all categories among: ] > * installed packages > [I--] [ ~] app-admin/fedora-admin-console-1.1.1 (1.1) > [I--] [ ~] app-admin/fedora-ds-console-1.1.1 (1.1) > [I--] [ ~] app-admin/fedora-idm-console-1.1.1 (1.1) > [I--] [ ~] net-nds/fedora-ds-admin-1.1.5-r1 (0) > [I--] [ ~] net-nds/fedora-ds-base-1.1.1-r1 (0) > at the moment i am stuck at the webinterface it only errors out hey maby you can find the reason for the error mod_admserv access permissons ? Mario
I'm not completely sure if its the same problem I have when building on my own from source, but it sounds like it. Basically I would get everything installed and running, then try and use the fancy java client to log in but would always get denied there even when using a simple password. Strange thing is that I was able to log into the Web based manager as DC=Administrator, but it's not very robust. I will certainly report back what I find later on today.
(In reply to comment #57) > Created an attachment (id=163221) [edit] > fixed fedora-ds-base ebuild from svn > > Tried to fix compilation without sasl (not tested, ebuild could be broken). I'm having problems with this. I do have cyrus-sasl installed. But I can't compile with or without it: >USE="-sasl" emerge --deep fedora-ds-base .... ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-debug --without-sasl --with-fhs --build=i686-pc-linux-gnu .... configure: checking for sasl... checking for --with-sasl... yes configure: error: sasl not found in no (that's the exact message). Graham(In reply to comment #57)
(In reply to comment #69) > I'm having problems with this. I do have cyrus-sasl installed. But I can't > compile with or without it: plz update svn
I have moved the all fds related ebuilds to its own overlay. the new layman file is located at http://ftp.mars.arge.at/pub/overlay/geos_one-overlay.xml the overlay is called "fds" so everyone using this ebuilds should move to this overlay
updated ebuilds in my overlay fds 1.2
mark ~ # layman -s fds * Running command "/usr/bin/svn up "/usr/portage/local/layman/fds""... svn: OPTIONS of 'http://mars.arge.at/svn/linamh/trunk/fds': could not connect to server (http://mars.arge.at) * * Errors: * ------ * * Failed to sync overlay "fds". * Error was: Syncing overlay "fds" returned status 256! *
(In reply to comment #73) > mark ~ # layman -s fds > * Running command "/usr/bin/svn up "/usr/portage/local/layman/fds""... > svn: OPTIONS of 'http://mars.arge.at/svn/linamh/trunk/fds': could not connect > to server (http://mars.arge.at) > * > * Errors: > * ------ > * > * Failed to sync overlay "fds". > * Error was: Syncing overlay "fds" returned status 256! > * > the server is up but there are some important corporate updates taking the compleat internet quota so lets hope they are finished tomorrow
the update to 389 is on the way can someone plz correct the Summery to: EBuild for 389 Directory Ldap Server
most of the tree has been renamed including the tree there are still packages that dont have new renamed versions the overlay is now called 389-ds happy testing
update for the 1.2.1 release now in tree also added my mirror of the used packages packages upstream is doing package update without version bump still working on the admin server bug all packages are now renamed to 389-* also renamed the fedora-idm-console package (its the fedora theme package) a gentoo theme pack would be greate ;-) one thing that is low priority is a patch for setup-ds.pl the problem: when you run setup-ds.pl a ldif file for the inital start is created in the privat tempdir for the root user when the server makes its initial start as unprivileged dirsrv user it has no access to the prior as root generated ldif file for now when you want to setup the server unset TMP and unset TMPDIR this way the generated file will be placed into /tmp and everything is going as it should the second thing with high priority that needs work are patches for the m4 macros for 389-ds-base 389-admin to specify --without-sasl and alike at the moment when the sasl is found it is build even if the system is build with USE=-sasl patches appriciated
What is the status of the overlay? Where can I currently check out from? I cannot find it on any of the above-mentioned URL (be it layman xml, or a SVN address) nor in the official Gentoo overlays list.
(In reply to comment #78) > What is the status of the overlay? Where can I currently check out from? > > I cannot find it on any of the above-mentioned URL (be it layman xml, or a SVN > address) nor in the official Gentoo overlays list. > here the updated infos the layman file http://ftp.mars.arge.at/pub/overlay/geos_one-overlay.xml the overlay is named 389-ds if you had the fedora directory server installed the plz unmerge all fedora packages first so happy testing
Created attachment 209028 [details] version bump more fix, it is compatible witch FreeIPA ( FreeIPA ebuils in process)
Created attachment 209030 [details] 389 Directory Server - Admin serwer
Created attachment 209032 [details] wersion bump, fix install binary and headers files Based om Mario Fetka ebuild
Created attachment 209033 [details] apr-util ebuild as mozldap USE/Support - reqired for user web interface 389 serwer
Created attachment 209035 [details] 389-adminutil ebuild
Created attachment 209037 [details] 389-admin-console Java based remote GUI for 389-admin server
Created attachment 209039 [details] 389-ds-console ebuild A Java based remote management console used for Managing 389 Administration and Directory Server
Created attachment 209041 [details] idm-console for 389 ladp server
Created attachment 209043 [details] 389 Directory Server Gateway web apps
All ebuild/programm stack developed by me in rion overlay. I also write for ebuilds for RedHat pki server, based on 389 serwer - is a separate bug
Optional kerberos support in 389 server depend on #177522
Created attachment 212617 [details] 389-ds-base-1.2.5_rc2.ebuild
Created attachment 213604 [details] 389-admin-1.1.10_alpha2.ebuild
Created attachment 213605 [details] 389-ds-base-1.2.5_rc3.ebuild
added 389-dsgw to my overlay (ebuilds is based on Andreis_Vinogradovs ) also corrected some old errors typos all ebuilds are now eapi2
initial freeipa ebuilds are now also in the tree (i did do not move them into its own overlay because they depend on 389 dirsrv) this ebuilds are not for production freeipa heavily depends on redhat style system so if someone is that adventurous take a look at the blocking bug #297665
Created attachment 217432 [details] 1.2.5.ebuild - snmp agent script added Upstream relized 1.2.5 version
Created attachment 217433 [details] 389-admin-1.1.10.ebuild upstream relised 1.1.10 version on this package. This ebuild install mod_restartd and mod_admserv due build system for this module deleted
Comment on attachment 209032 [details] wersion bump, fix install binary and headers files See #309539
Comment on attachment 217433 [details] 389-admin-1.1.10.ebuild See #309575 bug
Created attachment 224381 [details] net-nds/389-ds-base-1.2.6_alpha2.ebuild this ebuild adds selinux (thx to Andries) and adds the openldap (for the adventourous ones) and adds the with without patch (no use workarounds) again thx to the great work on squashing the last bugs to Andries
Created attachment 224383 [details, diff] 389-ds-base/files/0001-Bug-480787-Autoconf-parameter-with-and-without.patch the upstream patch for with and without
Created attachment 224389 [details] net-nds/389-ds-base/files/389-ds-base-1.2.6.a2-gentoo_selinux-1.patch the combined selinux patch from Andreis as usual this updated ebuilds are in my overlay http://ftp.disconnected-by-peer.at/pub/overlay/geos_one-overlay.xml happy testing
I wonder if you guys are interested in merging this stuff into the Portage tree, or if there's already somebody willing do to that.
Thanks, I took the maintainership of net-nds/389-ds-base and I merged it into tree. --- ChangeLog 1970-01-01 01:00:00.000000000 +0100 +++ ChangeLog.new 2010-07-07 16:36:03.331952701 +0200 @@ -0,0 +1,15 @@ +# ChangeLog for net-nds/389-ds-base +# Copyright 1999-2010 Gentoo Foundation; Distributed under the GPL v2 +# $Header: $ + +*389-ds-base-1.2.6_rc3 (07 Jul 2010) + + 07 Jul 2010; Fabio Erculiani <lxnay@gentoo.org> + +files/1.2.6/selinux_gentoo.patch, +files/1.2.6/selinux_makefile.patch, + +files/389-ds.initd, +files/389-ds-snmp.initd, + +389-ds-base-1.2.6_rc3.ebuild, +files/restart-dirsrv, +files/start-dirsrv, + +metadata.xml: + new ebuild, 389 Directory Server server package, thanks to + Andreis_Vinogradovs ( slepnoga ) <spamslepnoga@inbox.ru> for the base + ebuild, closing #309553 + I am going to close this bug once all its bug dependencies are closed.
(In reply to comment #104) > Thanks, I took the maintainership of net-nds/389-ds-base and I merged it into > tree. > great news now after more then 3 years maintaining this ebuilds they went into portage year. so all my hard work leads to success OT: thx to all the testers that mailed me bugreports to get some errors fixed and also to upstream for help fixing some gentoo related bugs.
Thanks to you again. I've been able to squash every bug, including the admin interface one, caused by improper usage of apache by upstream.
Thank you guys, we can now (yay!) close this bug. Enjoy 389 Directory Server in Gentoo and feel free to file bugs if you find something broken.
