389-devel April 2007

389-devel@lists.fedoraproject.org

8 participants
12 discussions

[Fedora-directory-devel] [PATCH] Allow replication in 00core.ldif
by Andrew Bartlett 11 May '07

11 May '07

I've been playing with Fedora DS replication and Samba, and have been making good progress. See http://wiki.samba.org/index.php/Samba4/LDAP_Backend/Fedora_DS for the evolving set of instructions (should get better over the next week). I need this patch applied (and possibly the bitwise patch too) to get the replication working. I also had to hack up mmr.pl to take a port, and not assume 389 Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Red Hat Inc. http://redhat.com

2 3

[Fedora-directory-devel] Commit: [Bug 237356] Move DS Admin Code into Admin Server
by Noriko Hosoi 28 Apr '07

28 Apr '07

Summary: Move DS Admin Code into Admin Server https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=237356 If you are on the fedora-directory-commits mailing list, sorry about the lots of commit messages that filled your INBOX. They are all for removing or moving out the unused code from the Fedora DS base package. Thanks, --noriko ------- Additional Comments From nhosoi(a)redhat.com 2007-04-27 17:55 EST ------- Created an attachment (id=153667) --> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=153667&action=view) cvs commit message (Comment #2) ------- Additional Comments From nhosoi(a)redhat.com 2007-04-27 18:19 EST ------- Created an attachment (id=153668) --> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=153668&action=view) cvs commit message (Comment #3) ------- Additional Comments From nhosoi(a)redhat.com 2007-04-27 19:01 EST ------- Created an attachment (id=153674) --> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=153674&action=view) cvs commit message (Comment #4, #6) ------- Additional Comments From nhosoi(a)redhat.com 2007-04-27 19:19 EST ------- Created an attachment (id=153675) --> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=153675&action=view) cvs commit message (Comment #5) ------- Additional Comments From nhosoi(a)redhat.com 2007-04-27 19:41 EST ------- Created an attachment (id=153677) --> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=153677&action=view) cvs commit message (Comment #8) ------- Additional Comments From nhosoi(a)redhat.com 2007-04-27 19:49 EST ------- Created an attachment (id=153678) --> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=153678&action=view) cvs commit message (Comment #8, #9)

1 0

[Fedora-directory-devel] Admin Console
by Edward Mann 27 Apr '07

27 Apr '07

I would like to extend the console to be more friendly with Unix admins. My ideas. When you create a new user, you can also check a box that will auto create the users autofs entry, unless there is a better way to do this. Make the UID/GID optional. Maybe a checkbox to enable the field for manual editing? The reason for this is i read that the server can handle this now. When you add a new user, you can also add them to NetGroups that you have defined. A specific interface for adding NetGroups and others. I have not looked into anything else but adding NetGroups at the moment. Maybe an option during setup to enable NetGroups and autofs. So the admin can just get in and start adding objects. Those are the ideas that i have right now. I would like some feedback. Also is gcj really that urgent now that Sun has O.S Java? Thanks. -- Edward Mann ARC Technologies 1914 W. Richwoods Blvd. Peoria, IL 61604 309.645.3553 www.arctechnologies.net

2 1

[Fedora-directory-devel] mysql-client
by mesut sahin 22 Apr '07

22 Apr '07

I am using fedora core 5 when I tried to instal vpopmail it gives error that mysql.h cannot find how can I install all packages of mysqlclient.

1 0

[Fedora-directory-devel] Please review: [Bug 237040] New: Remove obsolete makefiles
by Noriko Hosoi 19 Apr '07

19 Apr '07

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=237040 Summary: Remove obsolete makefiles Product: Fedora Directory Server Version: 1.0.4 Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: medium Component: Unknown AssignedTo: nhosoi(a)redhat.com ReportedBy: nhosoi(a)redhat.com QAContact: ohegarty(a)redhat.com Estimated Hours: 0.0 Description of problem: Since we have completed migrating to autoconf/automake, we don't need the obsolete makefiles. ------- Additional Comments From nhosoi(a)redhat.com 2007-04-18 20:51 EST ------- Created an attachment (id=152974) --> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=152974&action=view) Obsolete makefile list to be removed Thanks, --noriko

1 0

[Fedora-directory-devel] Re: [Fedora-directory-commits] windowsautoenroll LICENSE.txt, NONE, 1.1 aep.nsi, 1.3, 1.4
by Andrew Bartlett 18 Apr '07

18 Apr '07

On Tue, 2007-04-17 at 10:46 -0400, Steven W Parkinson wrote: > Author: sparkins > > Update of /cvs/dirsec/windowsautoenroll > In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16941 > > Modified Files: > aep.nsi > Added Files: > LICENSE.txt > Log Message: > Add Gnu GPL license to distribution This seems to be missing the preamble, and you should be specific as to versions, when you reference the 'Gnu General Public License'. It is also traditional to put this in a file marked COPYING. (The FSF also doesn't like their document being pulled apart). > --- NEW FILE LICENSE.txt --- > Auto Enrollment Proxy License Terms > > > This software, "Auto Enrollment Proxy" is distributed > under the Gnu General Public License. The terms of the > license are reproduced below. > > > GNU GENERAL PUBLIC LICENSE > TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION > > 0. This License applies to any program or other work which contains > a notice placed by the copyright holder saying it may be distributed > under the terms of this General Public License. The "Program", below, > refers to any such program or work, and a "work based on the Program" > means either the Program or any derivative work under copyright law: > that is to say, a work containing the Program or a portion of it, > either verbatim or with modifications and/or translated into another > language. (Hereinafter, translation is included without limitation in > the term "modification".) Each licensee is addressed as "you". > > Activities other than copying, distribution and modification are not > covered by this License; they are outside its scope. The act of > running the Program is not restricted, and the output from the Program > is covered only if its contents constitute a work based on the > Program (independent of having been made by running the Program). > Whether that is true depends on what the Program does. > > 1. You may copy and distribute verbatim copies of the Program's > source code as you receive it, in any medium, provided that you > conspicuously and appropriately publish on each copy an appropriate > copyright notice and disclaimer of warranty; keep intact all the > notices that refer to this License and to the absence of any warranty; > and give any other recipients of the Program a copy of this License > along with the Program. > > You may charge a fee for the physical act of transferring a copy, and > you may at your option offer warranty protection in exchange for a fee. > > 2. You may modify your copy or copies of the Program or any portion > of it, thus forming a work based on the Program, and copy and > distribute such modifications or work under the terms of Section 1 > above, provided that you also meet all of these conditions: > > a) You must cause the modified files to carry prominent notices > stating that you changed the files and the date of any change. > > b) You must cause any work that you distribute or publish, that in > whole or in part contains or is derived from the Program or any > part thereof, to be licensed as a whole at no charge to all third > parties under the terms of this License. > > c) If the modified program normally reads commands interactively > when run, you must cause it, when started running for such > interactive use in the most ordinary way, to print or display an > announcement including an appropriate copyright notice and a > notice that there is no warranty (or else, saying that you provide > a warranty) and that users may redistribute the program under > these conditions, and telling the user how to view a copy of this > License. (Exception: if the Program itself is interactive but > does not normally print such an announcement, your work based on > the Program is not required to print an announcement.) > > These requirements apply to the modified work as a whole. If > identifiable sections of that work are not derived from the Program, > and can be reasonably considered independent and separate works in > themselves, then this License, and its terms, do not apply to those > sections when you distribute them as separate works. But when you > distribute the same sections as part of a whole which is a work based > on the Program, the distribution of the whole must be on the terms of > this License, whose permissions for other licensees extend to the > entire whole, and thus to each and every part regardless of who wrote it. > > Thus, it is not the intent of this section to claim rights or contest > your rights to work written entirely by you; rather, the intent is to > exercise the right to control the distribution of derivative or > collective works based on the Program. > > In addition, mere aggregation of another work not based on the Program > with the Program (or with a work based on the Program) on a volume of > a storage or distribution medium does not bring the other work under > the scope of this License. > > 3. You may copy and distribute the Program (or a work based on it, > under Section 2) in object code or executable form under the terms of > Sections 1 and 2 above provided that you also do one of the following: > > a) Accompany it with the complete corresponding machine-readable > source code, which must be distributed under the terms of Sections > 1 and 2 above on a medium customarily used for software interchange; or, > > b) Accompany it with a written offer, valid for at least three > years, to give any third party, for a charge no more than your > cost of physically performing source distribution, a complete > machine-readable copy of the corresponding source code, to be > distributed under the terms of Sections 1 and 2 above on a medium > customarily used for software interchange; or, > > c) Accompany it with the information you received as to the offer > to distribute corresponding source code. (This alternative is > allowed only for noncommercial distribution and only if you > received the program in object code or executable form with such > an offer, in accord with Subsection b above.) > > The source code for a work means the preferred form of the work for > making modifications to it. For an executable work, complete source > code means all the source code for all modules it contains, plus any > associated interface definition files, plus the scripts used to > control compilation and installation of the executable. However, as a > special exception, the source code distributed need not include > anything that is normally distributed (in either source or binary > form) with the major components (compiler, kernel, and so on) of the > operating system on which the executable runs, unless that component > itself accompanies the executable. > > If distribution of executable or object code is made by offering > access to copy from a designated place, then offering equivalent > access to copy the source code from the same place counts as > distribution of the source code, even though third parties are not > compelled to copy the source along with the object code. > > 4. You may not copy, modify, sublicense, or distribute the Program > except as expressly provided under this License. Any attempt > otherwise to copy, modify, sublicense or distribute the Program is > void, and will automatically terminate your rights under this License. > However, parties who have received copies, or rights, from you under > this License will not have their licenses terminated so long as such > parties remain in full compliance. > > 5. You are not required to accept this License, since you have not > signed it. However, nothing else grants you permission to modify or > distribute the Program or its derivative works. These actions are > prohibited by law if you do not accept this License. Therefore, by > modifying or distributing the Program (or any work based on the > Program), you indicate your acceptance of this License to do so, and > all its terms and conditions for copying, distributing or modifying > the Program or works based on it. > > 6. Each time you redistribute the Program (or any work based on the > Program), the recipient automatically receives a license from the > original licensor to copy, distribute or modify the Program subject to > these terms and conditions. You may not impose any further > restrictions on the recipients' exercise of the rights granted herein. > You are not responsible for enforcing compliance by third parties to > this License. > > 7. If, as a consequence of a court judgment or allegation of patent > infringement or for any other reason (not limited to patent issues), > conditions are imposed on you (whether by court order, agreement or > otherwise) that contradict the conditions of this License, they do not > excuse you from the conditions of this License. If you cannot > distribute so as to satisfy simultaneously your obligations under this > License and any other pertinent obligations, then as a consequence you > may not distribute the Program at all. For example, if a patent > license would not permit royalty-free redistribution of the Program by > all those who receive copies directly or indirectly through you, then > the only way you could satisfy both it and this License would be to > refrain entirely from distribution of the Program. > > If any portion of this section is held invalid or unenforceable under > any particular circumstance, the balance of the section is intended to > apply and the section as a whole is intended to apply in other > circumstances. > > It is not the purpose of this section to induce you to infringe any > patents or other property right claims or to contest validity of any > such claims; this section has the sole purpose of protecting the > integrity of the free software distribution system, which is > implemented by public license practices. Many people have made > generous contributions to the wide range of software distributed > through that system in reliance on consistent application of that > system; it is up to the author/donor to decide if he or she is willing > to distribute software through any other system and a licensee cannot > impose that choice. > > This section is intended to make thoroughly clear what is believed to > be a consequence of the rest of this License. > > 8. If the distribution and/or use of the Program is restricted in > certain countries either by patents or by copyrighted interfaces, the > original copyright holder who places the Program under this License > may add an explicit geographical distribution limitation excluding > those countries, so that distribution is permitted only in or among > countries not thus excluded. In such case, this License incorporates > the limitation as if written in the body of this License. > > 9. The Free Software Foundation may publish revised and/or new versions > of the General Public License from time to time. Such new versions will > be similar in spirit to the present version, but may differ in detail to > address new problems or concerns. > > Each version is given a distinguishing version number. If the Program > specifies a version number of this License which applies to it and "any > later version", you have the option of following the terms and conditions > either of that version or of any later version published by the Free > Software Foundation. If the Program does not specify a version number of > this License, you may choose any version ever published by the Free Software > Foundation. > > 10. If you wish to incorporate parts of the Program into other free > programs whose distribution conditions are different, write to the author > to ask for permission. For software which is copyrighted by the Free > Software Foundation, write to the Free Software Foundation; we sometimes > make exceptions for this. Our decision will be guided by the two goals > of preserving the free status of all derivatives of our free software and > of promoting the sharing and reuse of software generally. > > NO WARRANTY > > 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY > FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN > OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES > PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED > OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF > MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS > TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE > PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, > REPAIR OR CORRECTION. > > 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING > WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR > REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, > INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING > OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED > TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY > YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER > PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE > POSSIBILITY OF SUCH DAMAGES. > > END OF TERMS AND CONDITIONS > > > Index: aep.nsi > =================================================================== > RCS file: /cvs/dirsec/windowsautoenroll/aep.nsi,v > retrieving revision 1.3 > retrieving revision 1.4 > diff -u -r1.3 -r1.4 > --- aep.nsi 17 Apr 2007 14:33:15 -0000 1.3 > +++ aep.nsi 17 Apr 2007 14:46:14 -0000 1.4 > @@ -36,6 +36,7 @@ > dotnetpresent: > > > +file /oname=$INSTDIR\LICENSE.txt "LICENSE.txt" > file /oname=$INSTDIR\rhcsproxy.exe "proxy\${BUILDTYPE}\rhcsproxy.exe" > file /oname=$INSTDIR\messages.dll "proxy\${BUILDTYPE}\messages.dll" > file /oname=$INSTDIR\submitrequest.exe "submitrequest\${BUILDTYPE}\submitrequest.exe" > > -- > Fedora-directory-commits mailing list > Fedora-directory-commits(a)redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-commits > -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Red Hat Inc. http://redhat.com

1 0

[Fedora-directory-devel] Please Review: (236612) Default filesystem layout should follow FHS optional package standards
by Nathan Kinder 18 Apr '07

18 Apr '07

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=236612 Resolves: bug 236612 Bug Description: The current default filesystem layout of a Fedora Directory Server build is to lump everything FHS style underneath a prefix of /opt/fedora-ds. We should change this to follow the FHS standards for an optional software package, namely using /etc/opt and /var/opt. We will leave the "--with-fhs" configure option for using the /usr, /etc/, and /var layout that are used when packaging Fedora Directory Server for inclusion in Fedora Extras. Reviewed by: ??? Files: see diff Branch: HEAD Fix Description: The attached diffs implement this new default layout. In addition to using /var/opt and /etc/opt, I merged all of the component and server libraries into a single /opt/fedora-ds/lib directory. I also made the instance directories live in /opt/fedora-ds/slapd-<instance> instead of using the lib directory. Platforms tested: HP-UX 11.23 Flag Day: no Doc impact: no https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=152711

3 4

[Fedora-directory-devel] Please review: Bug 235743: small memory leaks in task code
by Rich Megginson 10 Apr '07

10 Apr '07

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=235743 Resolves: bug 235743 Bug Description: small memory leaks in task code Reviewed by: ??? Files: see diff Branch: HEAD Fix Description: There were a few places that were using slapi_get_first/next_backend without freeing the iterator cookie. Platforms tested: RHEL4 Flag Day: no Doc impact: no https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=152068&action=diff

1 0

[Fedora-directory-devel] Admin Console
by Edward Mann 09 Apr '07

09 Apr '07

I was in IRC asking about the Admin console, and was directed to post a message here. My questions are, 1. is anyone working on it? 2. is there a wish/ToDo list for the application. I would like to offer some time to developing the application. Thanks. -- Edward Mann ARC Technologies 1914 W. Richwoods Blvd. Peoria, IL 61604 309.645.3553 www.arctechnologies.net

2 1

[Fedora-directory-devel] new uid/gid autogeneration feature
by Giulio Fidente 05 Apr '07

05 Apr '07

Hi all, someone knows how to get more informations about the new feature mentioned in the subject and how use it? there are nightly builts ready or something else for use the feature? thank you so much ! -- Giulio Fidente Babel S.r.l. - http://www.babel.it Tel. +39.06.97849121 - fax +39.06.91612446 P.zza S.Benedetto da Norcia, 33 - 00040 Pomezia (Roma)

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-devel April 2007