[389-devel] Jenkins build is back to normal : 389-ds-base #1088

2016-10-05 Thread jenkins 
See 
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org

[389-devel] Build failed in Jenkins: 389-ds-base #1087

2016-10-05 Thread jenkins 
See 

Changes:

[William Brown] Ticket 48996 - update DS for ns 0.2.0

--
Started by an SCM change
Building remotely on F23 (fedora Fedora23 Fedora fedora23) in workspace 

Wiping out workspace first.
Cloning the remote Git repository
Cloning repository git://git.fedorahosted.org/git/389/ds.git
 > git init  # 
 > timeout=10
Fetching upstream changes from git://git.fedorahosted.org/git/389/ds.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > git://git.fedorahosted.org/git/389/ds.git +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url git://git.fedorahosted.org/git/389/ds.git # 
 > timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
 > git config remote.origin.url git://git.fedorahosted.org/git/389/ds.git # 
 > timeout=10
Fetching upstream changes from git://git.fedorahosted.org/git/389/ds.git
 > git -c core.askpass=true fetch --tags --progress 
 > git://git.fedorahosted.org/git/389/ds.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse origin/master^{commit} # timeout=10
Checking out Revision ff9dafa5ca40e225e240597a5d5c52f0e6c7c677 (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f ff9dafa5ca40e225e240597a5d5c52f0e6c7c677
 > git rev-list 617b64faad36e9dedf13a5bef6748e602f82c4c2 # timeout=10
[389-ds-base] $ /bin/sh -e /tmp/hudson3331412956404975727.sh

Running configure...
CFLAGS= -Wall CXXFLAGS= -Wall ./configure --with-tmpfiles-d=/etc/tmpfiles.d 
--with-openldap --enable-autobind --enable-gcc-security --with-selinux 
--with-systemdsystemunitdir=/lib/systemd/system 
--with-systemdsystemconfdir=/etc/systemd/system --enable-debug
Build log is 
http://jenkins.fedorainfracloud.org/job/389-ds-base/ws/build.1087.txt

Running make...
Build log is 
http://jenkins.fedorainfracloud.org/job/389-ds-base/ws/build.1087.txt

Checking for warnings...
Build http://jenkins.fedorainfracloud.org/job/389-ds-base/1087/ failed
There are build warnings
Warning log is 
http://jenkins.fedorainfracloud.org/job/389-ds-base/ws/build-warns.1087.txt
Last 100 lines of warning log:

ldap/servers/slapd/connection.c:171:6: warning: variable ‘enable_listeners’ set 
but not used [-Wunused-but-set-variable]


Build step 'Execute shell' marked build as failure
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org

[389-devel] Please review; 48996 rpm with ns 0.2.0

2016-10-05 Thread William Brown 
Hi,

Seems I forgot to test building the rpm. Here is the fix for it:

https://fedorahosted.org/389/ticket/48996#comment:20

https://fedorahosted.org/389/attachment/ticket/48996/0001-Ticket-48996-Fix-rpm-to-work-with-ns-0.2.0.patch



-- 
Sincerely,

William Brown
Software Engineer
Red Hat, Brisbane


signature.asc
Description: This is a digitally signed message part
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org

[389-devel] Discussion: rpm changes

2016-10-05 Thread William Brown 
Hi,

Looking in the rpm I noticed a few things:

%preun
if [ $1 -eq 0 ]; then # Final removal
# remove instance specific service files/links
rm -rf %{_sysconfdir}/systemd/system/%{groupname}.wants/*
> /dev/null 2>&1 || :
fi


I don't actually think we need this. If we un-install, the instance
configuration and data dirs will remain. So if someone un-installs and
re-installs, this will break their instances.

Because we remove the dirsrv.target unit file, leaving the
dirsrv.target.wants is probably okay, so we can remove the %preun I
think.

%postun
/sbin/ldconfig
if [ $1 = 0 ]; then # Final removal
rm -rf /var/run/%{pkgname}
fi


Similar comment here. I think we can make this:

%postun -p /sbin/ldconfig

Does that sound reasonable?


-- 
Sincerely,

William Brown
Software Engineer
Red Hat, Brisbane


signature.asc
Description: This is a digitally signed message part
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org

[389-devel] Re: Build failed in Jenkins: 389-ds-base #1087

2016-10-05 Thread William Brown 
On Thu, 2016-10-06 at 00:38 +, jenk...@fedoraproject.org wrote:
> See 
> 
> Changes:
> 
> [William Brown] Ticket 48996 - update DS for ns 0.2.0

Working on this now ... 

-- 
Sincerely,

William Brown
Software Engineer
Red Hat, Brisbane


signature.asc
Description: This is a digitally signed message part
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org

[389-devel] Re: Please review design proposal for tickets 47986 and 48976

2016-10-05 Thread Ludwig Krispenz 


On 09/30/2016 02:15 AM, Noriko Hosoi wrote:

Hi Ludwig,

On 09/29/2016 05:43 AM, Ludwig Krispenz wrote:

This is the initial proposal, thanks for your feedback

http://www.port389.org/docs/389ds/design/delay-accepting-updates-after-init.html 




Please help me understanding the design...

I'm having a bit hard time to figure out the relationship/dependency 
among these 3 config parameters.


sorry if I was not clear enough, I will update the doc, but let me try 
to explain here


nsslapd-replica-accept-updates-state: on/off
nsslapd-replica-accept-updates-delay: -1/0/n
nsslapd-replica-accept-updates-auto: on/off

Are they independent or dependent?  Do they take any combinations -- 2 
* 3 * 2 == 12.



no. the primary parameter is: nsslapd-replica-accept-updates-state
If it is off, the other determine when it should be set to on again 
(without an explicite change by an admin).

if it is on, the other two will not be used

independent of auto on/off the "delay" defines if(>=0) the state will be 
reset to on and when


the "auto" param determines if the server should in the defined "delay" 
it should try to detect if it is in sync and switch to "on" earlier.



There are 12 different behaviors?  (assuming n for -delay is one case :)

What is your recommendation to the customers?  I mean, what is the 
default setting?


that is a good question, there is the option to choose the default by 
what is "my" recommendation (auto: on, delay: n) or what is backward 
compatible (no change in default behaviour: auto off, delay: 0)


  For instance, if -auto is "on", when an online init is executed on 
the master, the scenario is automatically kicked in?


Thanks,
--noriko





||


___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org


--
Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric 
Shander

___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org

[389-devel] please review: Ticket 48926 - ds-console - fix issues with the save/reset button behavior in the password policy/account lockout panels

2016-10-05 Thread Mark Reynolds 
https://fedorahosted.org/389/ticket/48926

https://fedorahosted.org/389/attachment/ticket/48926/0001-Ticket-48926-Fixed-reset-save-button-behavior-in-the.patch
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org