389-devel March 2017

389-devel@lists.fedoraproject.org

11 participants
64 discussions

Build failed in Jenkins: 389-ds-base #1201
by jenkins＠fedoraproject.org 09 Mar '17

09 Mar '17

See <https://jenkins.fedorainfracloud.org/job/389-ds-base/1201/> ------------------------------------------ Started by an SCM change Building remotely on F25 (Fedora25 fedora Fedora fedora25) in workspace <https://jenkins.fedorainfracloud.org/job/389-ds-base/ws/> Wiping out workspace first. Cloning the remote Git repository Cloning repository http://pagure.io/389-ds-base.git > git init <https://jenkins.fedorainfracloud.org/job/389-ds-base/ws/> # timeout=10 Fetching upstream changes from http://pagure.io/389-ds-base.git > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress http://pagure.io/389-ds-base.git +refs/heads/*:refs/remotes/origin/* ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "git -c core.askpass=true fetch --tags --progress http://pagure.io/389-ds-base.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: remote: Counting objects: 51544 remote: Counting objects: 72052, done. remote: Compressing objects: 0% (1/18162) remote: Compressing objects: 1% (182/18162) remote: Compressing objects: 2% (364/18162) remote: Compressing objects: 3% (545/18162) remote: Compressing objects: 4% (727/18162) remote: Compressing objects: 5% (909/18162) remote: Compressing objects: 6% (1090/18162) remote: Compressing objects: 7% (1272/18162) remote: Compressing objects: 8% (1453/18162) remote: Compressing objects: 9% (1635/18162) remote: Compressing objects: 10% (1817/18162) remote: Compressing objects: 11% (1998/18162) remote: Compressing objects: 12% (2180/18162) remote: Compressing objects: 13% (2362/18162) remote: Compressing objects: 14% (2543/18162) remote: Compressing objects: 15% (2725/18162) remote: Compressing objects: 16% (2906/18162) remote: Compressing objects: 17% (3088/18162) remote: Compressing objects: 18% (3270/18162) remote: Compressing objects: 19% (3451/18162) remote: Compressing objects: 20% (3633/18162) remote: Compressing objects: 21% (3815/18162) remote: Compressing objects: 22% (3996/18162) remote: Compressing objects: 23% (4178/18162) remote: Compressing objects: 24% (4359/18162) remote: Compressing objects: 25% (4541/18162) remote: Compressing objects: 26% (4723/18162) remote: Compressing objects: 27% (4904/18162) remote: Compressing objects: 28% (5086/18162) remote: Compressing objects: 29% (5267/18162) remote: Compressing objects: 30% (5449/18162) remote: Compressing objects: 31% (5631/18162) remote: Compressing objects: 32% (5812/18162) remote: Compressing objects: 33% (5994/18162) remote: Compressing objects: 34% (6176/18162) remote: Compressing objects: 35% (6357/18162) remote: Compressing objects: 36% (6539/18162) remote: Compressing objects: 37% (6720/18162) remote: Compressing objects: 38% (6902/18162) remote: Compressing objects: 39% (7084/18162) remote: Compressing objects: 40% (7265/18162) remote: Compressing objects: 41% (7447/18162) remote: Compressing objects: 42% (7629/18162) remote: Compressing objects: 43% (7810/18162) remote: Compressing objects: 44% (7992/18162) remote: Compressing objects: 45% (8173/18162) remote: Compressing objects: 46% (8355/18162) remote: Compressing objects: 47% (8537/18162) remote: Compressing objects: 48% (8718/18162) remote: Compressing objects: 49% (8900/18162) remote: Compressing objects: 50% (9081/18162) remote: Compressing objects: 51% (9263/18162) remote: Compressing objects: 52% (9445/18162) remote: Compressing objects: 53% (9626/18162) remote: Compressing objects: 54% (9808/18162) remote: Compressing objects: 55% (9990/18162) remote: Compressing objects: 56% (10171/18162) remote: Compressing objects: 57% (10353/18162) remote: Compressing objects: 58% (10534/18162) remote: Compressing objects: 59% (10716/18162) remote: Compressing objects: 60% (10898/18162) remote: Compressing objects: 61% (11079/18162) remote: Compressing objects: 62% (11261/18162) remote: Compressing objects: 63% (11443/18162) remote: Compressing objects: 64% (11624/18162) remote: Compressing objects: 65% (11806/18162) remote: Compressing objects: 66% (11987/18162) remote: Compressing objects: 67% (12169/18162) remote: Compressing objects: 68% (12351/18162) remote: Compressing objects: 69% (12532/18162) remote: Compressing objects: 70% (12714/18162) remote: Compressing objects: 71% (12896/18162) remote: Compressing objects: 72% (13077/18162) remote: Compressing objects: 73% (13259/18162) remote: Compressing objects: 74% (13440/18162) remote: Compressing objects: 75% (13622/18162) remote: Compressing objects: 76% (13804/18162) remote: Compressing objects: 77% (13985/18162) remote: Compressing objects: 78% (14167/18162) remote: Compressing objects: 79% (14348/18162) remote: Compressing objects: 80% (14530/18162) remote: Compressing objects: 81% (14712/18162) remote: Compressing objects: 82% (14893/18162) remote: Compressing objects: 83% (15075/18162) remote: Compressing objects: 84% (15257/18162) remote: Compressing objects: 85% (15438/18162) remote: Compressing objects: 86% (15620/18162) remote: Compressing objects: 87% (15801/18162) remote: Compressing objects: 88% (15983/18162) remote: Compressing objects: 89% (16165/18162) remote: Compressing objects: 90% (16346/18162) remote: Compressing objects: 91% (16528/18162) remote: Compressing objects: 92% (16710/18162) remote: Compressing objects: 93% (16891/18162) remote: Compressing objects: 94% (17073/18162) remote: Compressing objects: 95% (17254/18162) remote: Compressing objects: 96% (17436/18162) remote: Compressing objects: 97% (17618/18162) remote: Compressing objects: 97% (17758/18162) remote: Compressing objects: 98% (17799/18162) remote: Compressing objects: 99% (17981/18162) remote: Compressing objects: 100% (18162/18162) remote: Compressing objects: 100% (18162/18162), done. Receiving objects: 0% (1/72052) Receiving objects: 1% (721/72052) Receiving objects: 2% (1442/72052) Receiving objects: 3% (2162/72052) Receiving objects: 4% (2883/72052) Receiving objects: 5% (3603/72052) Receiving objects: 6% (4324/72052) Receiving objects: 7% (5044/72052) Receiving objects: 8% (5765/72052) Receiving objects: 9% (6485/72052) Receiving objects: 10% (7206/72052) Receiving objects: 11% (7926/72052) Receiving objects: 12% (8647/72052) Receiving objects: 13% (9367/72052) Receiving objects: 14% (10088/72052) Receiving objects: 15% (10808/72052) Receiving objects: 16% (11529/72052) Receiving objects: 17% (12249/72052) Receiving objects: 18% (12970/72052) Receiving objects: 19% (13690/72052) Receiving objects: 20% (14411/72052) Receiving objects: 21% (15131/72052) Receiving objects: 22% (15852/72052) Receiving objects: 23% (16572/72052) Receiving objects: 24% (17293/72052) Receiving objects: 25% (18013/72052) Receiving objects: 26% (18734/72052), 5.66 MiB | 11.31 MiB/s Receiving objects: 27% (19455/72052), 5.66 MiB | 11.31 MiB/s Receiving objects: 28% (20175/72052), 5.66 MiB | 11.31 MiB/s Receiving objects: 29% (20896/72052), 5.66 MiB | 11.31 MiB/s Receiving objects: 30% (21616/72052), 5.66 MiB | 11.31 MiB/s Receiving objects: 31% (22337/72052), 5.66 MiB | 11.31 MiB/s Receiving objects: 32% (23057/72052), 5.66 MiB | 11.31 MiB/s Receiving objects: 33% (23778/72052), 5.66 MiB | 11.31 MiB/s Receiving objects: 33% (24373/72052), 8.43 MiB | 133.00 KiB/s Receiving objects: 34% (24498/72052), 8.43 MiB | 133.00 KiB/s Receiving objects: 35% (25219/72052), 8.43 MiB | 133.00 KiB/s Receiving objects: 36% (25939/72052), 8.43 MiB | 133.00 KiB/s Receiving objects: 36% (25997/72052), 8.43 MiB | 133.00 KiB/s Receiving objects: 37% (26660/72052), 8.43 MiB | 133.00 KiB/s Receiving objects: 38% (27380/72052), 8.43 MiB | 133.00 KiB/s Receiving objects: 39% (28101/72052), 8.43 MiB | 133.00 KiB/s Receiving objects: 40% (28821/72052), 8.43 MiB | 133.00 KiB/s Receiving objects: 41% (29542/72052), 8.43 MiB | 133.00 KiB/s Receiving objects: 42% (30262/72052), 8.43 MiB | 133.00 KiB/s Receiving objects: 43% (30983/72052), 8.43 MiB | 133.00 KiB/s error: RPC failed; curl 18 transfer closed with outstanding read data remaining fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1600) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1363) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:61) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:299) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:485) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) at hudson.remoting.UserRequest.perform(UserRequest.java:153) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:332) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at ......remote call to F25(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1433) at hudson.remoting.UserResponse.retrieve(UserRequest.java:253) at hudson.remoting.Channel.call(Channel.java:797) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145) at sun.reflect.GeneratedMethodAccessor182.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131) at com.sun.proxy.$Proxy50.execute(Unknown Source) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1003) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1043) at hudson.scm.SCM.checkout(SCM.java:485) at hudson.model.AbstractProject.checkout(AbstractProject.java:1269) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) ERROR: null

1 1

Please review: Issue 49156 - Add more IDs and fix docstrings
by Simon Pichugin 09 Mar '17

09 Mar '17

Hi team, please, review my small patch that should fix the points I've missed. https://pagure.io/389-ds-base/issue/49156 https://pagure.io/389-ds-base/issue/raw/files/f8e868bd9c2af26e54a63e56cefdf… Thanks, Simon

1 1

please review: Issue 49162 - Can not build 1.3.6 on non x86_64 architectures
by Mark Reynolds 09 Mar '17

09 Mar '17

https://pagure.io/389-ds-base/issue/49162 https://pagure.io/389-ds-base/issue/raw/files/856636484a24383bee533dd7ceeed…

1 0

Re: Interested to contribute to admistrative tools development for 389 directory server task in GSOC'17
by sane sai charan 08 Mar '17

08 Mar '17

OMG !! I forgot to attach the log file. 😕 Here it is. On Thu, Mar 9, 2017 at 1:15 AM, sane sai charan <sanesaicharan23(a)gmail.com> wrote: > Hi, > I sent you invitation link so that you can edit proposal. I have a > small doubt. I wonder why Perl tools are being replaced by Python. > > > > On Thu, Mar 9, 2017 at 1:12 AM, sane sai charan <sanesaicharan23(a)gmail.com > > wrote: > >> >> >> On Fri, Mar 3, 2017 at 5:30 AM, William Brown < >> firstyear(a)fedoraproject.org> wrote: >> >>> Hi, >>> >>> I'm really excited that you find this project interesting! I'm putting >>> my answers inline, and I hope that this helps you, >>> >>> On Fri, 2017-03-03 at 02:35 +0530, sane sai charan wrote: >>> > Hi, >>> > I am a senior undergraduate student from >>> > Indian Institute of Technology-BHU, Varanasi, India. I am a GSoC 2017 >>> > aspirant and am interested in developing administrative tools for 389 >>> > directory server task. I have a good understanding of Python classes, >>> > inheritance, MRO, the working of modules, etc. Though I haven't >>> produced >>> > any good quality code, I started this <https://github.com/sacha23/bo >>> oker>noobie >>> > script just for fun. I just worked on it for two days as I was busy >>> last >>> > semester due to placements. >>> >>> That's no problem - life and study do take time so I can understand you >>> making this choice. >>> >> >> Thanks for understanding. >> >> >>> As a note, python uses soft tabs, not hard ones, so maybe use 4 spaces >>> not tabs in your python. Most text editors like vim and emacs can be set >>> to do this automatically. More generally, you'll find many projects have >>> a style guide like this that helps you write your code in certain ways. >>> For example, here is ours: >>> >>> http://www.port389.org/docs/389ds/development/coding-style.html >>> >>> You'll find that review like this is an important part of work in open >>> source, and I find it really enjoyable - Some of the people in the DS >>> team are truly experts, and their reviews help improve your code. >>> >>> >> Excellent. I always look forward to learn new principles and I enjoy >> that. >> >> >>> > >>> > I am *interested in this project because* >>> > >>> > ** *I find this as a *great opportunity to learn *how >>> to >>> > produce high-quality and highly reliable code as William said >>> > <https://www.youtube.com/watch?v=1mIttrUcS5w&t=28s> 😀 >>> > >>> > * ** I *get to know how open source world work*. >>> > >>> > *** I *want to apply my python knowledge* to some real >>> > world application. I read books on Python (David Beazley's book, Dive >>> into >>> > Python, etc.) few times but I never used that knowledge to full >>> potential, >>> > although I code in python usually. >>> > >>> > * ** Fedora and Redhat's stickers and T-Shirt's.😎 >>> > >>> > Programming languages: Good - Python, C >>> > Intermediate - Bash >>> > Noob - C++,perl >>> >>> Excellent: We are really happy you are interested. In this you'll mainly >>> be focused on python only, so don't worry about the C. >>> >>> >> Great !! >> >> >>> >>> >>> > >>> > Although I was selected for GSOC last >>> time >>> > for RTEMS to do "Integrating RTEMS file descriptors with LwIP" task, I >>> > withdrew from the program just before >>> > Mid-Term evaluation. The reason was. First, It was the first time for >>> me to >>> > look into the kernel and chasing the function calls and see what is >>> > happening and I actually started late in preparing to GSOC. I never >>> thought >>> > I would apply for GSOC, and it happened suddenly as the qualification >>> task >>> > was quite easy. There was a lot to know about RTEMS for me. I was >>> > frustrated by seeing large pieces of code daily trying to understand >>> how it >>> > is working. Second reason was my mentor is a very active contributor in >>> > many projects and Prof. at Czech Technical University, and he was quite >>> > busy and many people in RTEMS community did not have enough experience >>> with >>> > LwIP. My mentor helped me a lot by answering all silly questions very >>> > patiently, but the problem for me was his answers contain dense >>> > information. Even after reading his message for 4-5 times I was >>> unclear. So >>> > I decided to withdraw and learn necessary things before reattempting >>> that >>> > task. I contacted my mentor recently about the task, and he said he was >>> > busy and may not help me out regularly. >>> > >>> > >>> > I want to ask you that >>> > 1. *How to approach* and where should I start >>> > studying to get enough knowledge? >>> >>> I think this is a good document to read: >>> >>> http://www.port389.org/docs/389ds/development.html >>> >>> As well, for the project itself we don't expect a lot of code, we mainly >>> want you to go through the process of being in the project. My rough >>> timeline and idea of how the project will progress is: >>> >>> May 4 - May 30: This is your time to setup a DS server, install the >>> lib389 source code, and test it out. Try running dsconf, get it to work. >>> This is your time to ask me about how to make it work (ask as many >>> questions as you like in this time!). In this time we'll cover what >>> module we think you can write, joining you to mailing lists and irc, >>> getting you a fas account, and making sure you have access to pagure >>> (our code and ticket system). >>> >>> May 30 - June 26: Write first module. This means that you should have >>> code in lib389/plugins.py for enabling/disabling the module, maybe >>> changing some simple settings. There should be tests for this behaviour. >>> You should have the ability to see the plugin in the dsconf tool also >>> and configure it. This too would have tests. >>> >>> We don't want this to be one "big patch", we would rather you do it in >>> smaller submissions, so we can review and work with you as you go. We'll >>> teach you how to write the patch, how to submit for review, and how to >>> go through the review process with us. >>> >>> June 26 is the end of "Phase 1" so that's our chance to review and see >>> how we are going, and if we have asked to much. >>> >>> June 30 - July 28: Start on a second plugin or module. Again, same >>> requirements as the first. Iterative commits, where we can review and >>> work with you through the whole process. During this phase, if you felt >>> comfortable, you could start to look at and review the python work of >>> others in the team to understand their work. Asking questions is a great >>> way to learn. >>> >>> July 28 - August 29: Google calls this the "submit final work" - But as >>> I've made it clear here, I think we want you to submit "as you go". >>> Perhaps this "final work" is the final addition of the hooks to dsconf >>> so you really can use it, perhaps you can write a report on the >>> experience. This would be the "end of work", so this is a chance for you >>> to hand in anything you haven't finished 100% if you wanted. >>> >>> These times are taken from: >>> >>> https://developers.google.com/open-source/gsoc/timeline >>> >>> >>> > 2. Any *qualification task*s? >>> >>> None besides what you have listed here. >>> >> >> Great !! >> >> >>> >>> > 3. Did anyone want to do this task already? >>> >>> There have been a number of other expressions of interest, but >>> applications don't open for a few weeks so the selection hasn't been >>> made yet. I'm also not sure about how many students I can have in the >>> project either, so I need to confirm this with Fedora Project. >>> >>> > Best regards, >>> > Sai Charan Sane. >>> >>> >>> Thanks for your valuable suggestions. >> I tried to build 389 DS on kali linux ( >> Debian ) but had no luck. I got some errors. I looked into configure script >> with some hope but could not make it out. I am attaching the config.log >> here. I installed all required libraries ( libdb-dev libkrb5-dev >> libicu-dev libsnmp-dev libsasl2-2 libsasl2-dev libsasl2-modules-gssapi-mit >> libpam0g-dev libpcre2-dev libldap-dev libsvrcore-dev libnss3-dev >> libnspr4-dev autoconf automake libtool ant libapache2-mod-nss >> libds-admin-serv0 libidm-console-framework-java libjss-java libldap-java >> libmozilla-ldap-perl libnetaddr-ip-perl libnss3-tools >> libperl4-corelibs-perl libsocket-getaddrinfo-perl ). Please help me >> solving these errors. I am now trying to install in fedora. >> I made draft proposal here >> <https://docs.google.com/document/d/17dDMUoHuoOYuVnTSkVbhgKeIE1Go4s0ZEoov4ki…>. >> Please look into this and don't hesitate to comment on any additions or >> deletions. I created FAS account with handle sacha23 and yet to get access >> to create a wiki page. >> >> Best regards, >> Sai Charan Sane. >> > >

1 0

Re: Interested to contribute to admistrative tools development for 389 directory server task in GSOC'17
by sane sai charan 08 Mar '17

08 Mar '17

On Fri, Mar 3, 2017 at 5:30 AM, William Brown <firstyear(a)fedoraproject.org> wrote: > Hi, > > I'm really excited that you find this project interesting! I'm putting > my answers inline, and I hope that this helps you, > > On Fri, 2017-03-03 at 02:35 +0530, sane sai charan wrote: > > Hi, > > I am a senior undergraduate student from > > Indian Institute of Technology-BHU, Varanasi, India. I am a GSoC 2017 > > aspirant and am interested in developing administrative tools for 389 > > directory server task. I have a good understanding of Python classes, > > inheritance, MRO, the working of modules, etc. Though I haven't produced > > any good quality code, I started this <https://github.com/sacha23/booker > >noobie > > script just for fun. I just worked on it for two days as I was busy last > > semester due to placements. > > That's no problem - life and study do take time so I can understand you > making this choice. > Thanks for understanding. > As a note, python uses soft tabs, not hard ones, so maybe use 4 spaces > not tabs in your python. Most text editors like vim and emacs can be set > to do this automatically. More generally, you'll find many projects have > a style guide like this that helps you write your code in certain ways. > For example, here is ours: > > http://www.port389.org/docs/389ds/development/coding-style.html > > You'll find that review like this is an important part of work in open > source, and I find it really enjoyable - Some of the people in the DS > team are truly experts, and their reviews help improve your code. > > Excellent. I always look forward to learn new principles and I enjoy that. > > > > I am *interested in this project because* > > > > ** *I find this as a *great opportunity to learn *how to > > produce high-quality and highly reliable code as William said > > <https://www.youtube.com/watch?v=1mIttrUcS5w&t=28s> 😀 > > > > * ** I *get to know how open source world work*. > > > > *** I *want to apply my python knowledge* to some real > > world application. I read books on Python (David Beazley's book, Dive > into > > Python, etc.) few times but I never used that knowledge to full > potential, > > although I code in python usually. > > > > * ** Fedora and Redhat's stickers and T-Shirt's.😎 > > > > Programming languages: Good - Python, C > > Intermediate - Bash > > Noob - C++,perl > > Excellent: We are really happy you are interested. In this you'll mainly > be focused on python only, so don't worry about the C. > > Great !! > > > > > > Although I was selected for GSOC last time > > for RTEMS to do "Integrating RTEMS file descriptors with LwIP" task, I > > withdrew from the program just before > > Mid-Term evaluation. The reason was. First, It was the first time for me > to > > look into the kernel and chasing the function calls and see what is > > happening and I actually started late in preparing to GSOC. I never > thought > > I would apply for GSOC, and it happened suddenly as the qualification > task > > was quite easy. There was a lot to know about RTEMS for me. I was > > frustrated by seeing large pieces of code daily trying to understand how > it > > is working. Second reason was my mentor is a very active contributor in > > many projects and Prof. at Czech Technical University, and he was quite > > busy and many people in RTEMS community did not have enough experience > with > > LwIP. My mentor helped me a lot by answering all silly questions very > > patiently, but the problem for me was his answers contain dense > > information. Even after reading his message for 4-5 times I was unclear. > So > > I decided to withdraw and learn necessary things before reattempting that > > task. I contacted my mentor recently about the task, and he said he was > > busy and may not help me out regularly. > > > > > > I want to ask you that > > 1. *How to approach* and where should I start > > studying to get enough knowledge? > > I think this is a good document to read: > > http://www.port389.org/docs/389ds/development.html > > As well, for the project itself we don't expect a lot of code, we mainly > want you to go through the process of being in the project. My rough > timeline and idea of how the project will progress is: > > May 4 - May 30: This is your time to setup a DS server, install the > lib389 source code, and test it out. Try running dsconf, get it to work. > This is your time to ask me about how to make it work (ask as many > questions as you like in this time!). In this time we'll cover what > module we think you can write, joining you to mailing lists and irc, > getting you a fas account, and making sure you have access to pagure > (our code and ticket system). > > May 30 - June 26: Write first module. This means that you should have > code in lib389/plugins.py for enabling/disabling the module, maybe > changing some simple settings. There should be tests for this behaviour. > You should have the ability to see the plugin in the dsconf tool also > and configure it. This too would have tests. > > We don't want this to be one "big patch", we would rather you do it in > smaller submissions, so we can review and work with you as you go. We'll > teach you how to write the patch, how to submit for review, and how to > go through the review process with us. > > June 26 is the end of "Phase 1" so that's our chance to review and see > how we are going, and if we have asked to much. > > June 30 - July 28: Start on a second plugin or module. Again, same > requirements as the first. Iterative commits, where we can review and > work with you through the whole process. During this phase, if you felt > comfortable, you could start to look at and review the python work of > others in the team to understand their work. Asking questions is a great > way to learn. > > July 28 - August 29: Google calls this the "submit final work" - But as > I've made it clear here, I think we want you to submit "as you go". > Perhaps this "final work" is the final addition of the hooks to dsconf > so you really can use it, perhaps you can write a report on the > experience. This would be the "end of work", so this is a chance for you > to hand in anything you haven't finished 100% if you wanted. > > These times are taken from: > > https://developers.google.com/open-source/gsoc/timeline > > > > 2. Any *qualification task*s? > > None besides what you have listed here. > Great !! > > > 3. Did anyone want to do this task already? > > There have been a number of other expressions of interest, but > applications don't open for a few weeks so the selection hasn't been > made yet. I'm also not sure about how many students I can have in the > project either, so I need to confirm this with Fedora Project. > > > Best regards, > > Sai Charan Sane. > > > Thanks for your valuable suggestions. I tried to build 389 DS on kali linux ( Debian ) but had no luck. I got some errors. I looked into configure script with some hope but could not make it out. I am attaching the config.log here. I installed all required libraries ( libdb-dev libkrb5-dev libicu-dev libsnmp-dev libsasl2-2 libsasl2-dev libsasl2-modules-gssapi-mit libpam0g-dev libpcre2-dev libldap-dev libsvrcore-dev libnss3-dev libnspr4-dev autoconf automake libtool ant libapache2-mod-nss libds-admin-serv0 libidm-console-framework-java libjss-java libldap-java libmozilla-ldap-perl libnetaddr-ip-perl libnss3-tools libperl4-corelibs-perl libsocket-getaddrinfo-perl ). Please help me solving these errors. I am now trying to install in fedora. I made draft proposal here <https://docs.google.com/document/d/17dDMUoHuoOYuVnTSkVbhgKeIE1Go4s0ZEoov4ki…>. Please look into this and don't hesitate to comment on any additions or deletions. I created FAS account with handle sacha23 and yet to get access to create a wiki page. Best regards, Sai Charan Sane.

1 0

please review: Issue 47536 - Fix CI test for certificate PEM files
by Mark Reynolds 08 Mar '17

08 Mar '17

https://pagure.io/389-ds-base/issue/47536 https://pagure.io/389-ds-base/issue/raw/files/69163233d259e14e639f219b591bf…

1 0

please review 49160 sds copyright and benchmark
by William Brown 07 Mar '17

07 Mar '17

https://pagure.io/389-ds-base/issue/49160 https://pagure.io/389-ds-base/issue/raw/files/5dcf794618dbecb08e5541d6bd976… -- Sincerely, William Brown Software Engineer Red Hat, Australia/Brisbane

1 0

please review: Issue 49158 - fix coverity issues
by Mark Reynolds 07 Mar '17

07 Mar '17

https://pagure.io/389-ds-base/issue/49158 https://pagure.io/389-ds-base/issue/raw/files/4ca8250c45b2278f3d53aeb991f5c…

1 0

Please review: Issue 49159 - test_schema_comparewithfiles fails with python-ldap>=2.4.26
by Viktor Ashirov 07 Mar '17

07 Mar '17

https://pagure.io/389-ds-base/issue/49159 https://pagure.io/389-ds-base/issue/raw/files/6ee1eb7319ffb0c4aba546a23f452…

1 0

Please review: Issue 49156 - Clean up test suites dir structure and docstrings
by Simon Pichugin 05 Mar '17

05 Mar '17

Hi team, please, review my test suites clean up. Also, Amita, please, review the Polarion test plans part, if the fields fit the importer. https://pagure.io/389-ds-base/issue/49156 https://pagure.io/389-ds-base/issue/raw/files/0a0f06b64b6657be75436832cdd41… Thanks! Simon

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-devel March 2017