From sara at sinodun.com  Mon Dec  2 14:49:15 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Mon, 2 Dec 2013 14:49:15 +0000
Subject: [Opendnssec-develop] Team meeting - Monday 2 Dec @ 14:00 CET
In-Reply-To: <4763D3D4-52AA-45DF-B5BF-B1B21299B20A@sinodun.com>
References: <4763D3D4-52AA-45DF-B5BF-B1B21299B20A@sinodun.com>
Message-ID: <375D0F31-FA46-4507-9B50-F446678DDF00@sinodun.com>

Hi All, 

The minutes from the meeting today are available for review:

https://wiki.opendnssec.org/display/OpenDNSSEC/2013-12-02+Minutes


The next meeting is planned for

Date:      Tuesday 14 Jan 2014
Time:      14:00-15:00 CET, 13:00-14:00 GMT, 21:00-22:00 CST, 13:00-14:00 UTC

Sara. 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenDNSSEC team meeting.ics
Type: text/calendar
Size: 715 bytes
Desc: not available
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131202/9009bc3f/attachment.bin>
-------------- next part --------------


On 29 Nov 2013, at 15:41, Sara Dickinson <sara at sinodun.com> wrote:

> Hi All, 
> 
> We have a team meeting on *Monday* next week:
> 
> Date:      Monday 2 Dec 2013
> Time:      14:00-15:00 CET, 13:00-14:00 GMT, 21:00-22:00 CST, 13:00-14:00 UTC
> Method:  Teamspeak
> Agenda:  https://wiki.opendnssec.org/display/OpenDNSSEC/2013-12-02+Agenda
> 
> 
> Sara.
> 
> _______________________________________________
> Opendnssec-develop mailing list
> Opendnssec-develop at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop


From sara at sinodun.com  Wed Dec  4 14:47:16 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Wed, 4 Dec 2013 14:47:16 +0000
Subject: [Opendnssec-develop] OpenDNSSEC 1.3.16
Message-ID: <72E3CA9D-997B-40C3-9472-A11D1F98CE8F@sinodun.com>

All, 

Version 1.3.16 of OpenDNSSEC has now been released:


Updates:

* SUPPORT-72: Improve logging when failed to increment serial in case of key rollover and serial value "keep" [OPENDNSSEC-441].
* OPENDNSSEC-436: NSEC3PARAM TTL can now be optionally configured in kasp.xml. Default value remains PT0S.
* OPENDNSSEC-458: Add 'ods-enforcerd -p <policy>' option. This prompts the enforcer to run once and only process the specified policy and associated zones. 
* OPENDNSSEC-460: ods-ksmutil: Add an option to the 'ods-ksmutil key ds-seen' command so the user can choose not to notify the enforcer.
* OPENDNSSEC-472: ods-ksmutil: Add option for 'ods-ksmutil key import' to check if there is a matching key in the repository before import.
* OPENDNSSEC-473: ods-ksmutil: Improve 'zone add' - Support default <input> and <output> values for DNS adapters.

Bugfixes:

* OPENDNSSEC-451: Signer Engine: Prevent CKA_ID and DNSKEY mixup by using a separate HSM context when loading signer configuration.
* OPENDNSSEC-462: Signer Engine: Duration PT0S is not printed correctly.
* ods-ksmutil: Fix typo in policy export with NSEC3 <Iterations>.

Documentation:

* http://wiki.opendnssec.org/display/DOCS13

Download:

* http://dist.opendnssec.org/source/opendnssec-1.3.16.tar.gz
* http://dist.opendnssec.org/source/opendnssec-1.3.16.tar.gz.sig
* Checksum sha1: 4d81517cc99f8120f773c2af772b17eb5714f793
* Checksum sha256: fa0fe18757a19d6b03e27c2c76f291d61a735f14c2661725df4e569e0be1d04c


//OpenDNSSEC team




From sara at sinodun.com  Wed Dec  4 14:47:23 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Wed, 4 Dec 2013 14:47:23 +0000
Subject: [Opendnssec-develop] OpenDNSSEC 1.4.3
Message-ID: <05C3B60A-3DE4-4C9F-9E41-9FDC6F8CE2BE@sinodun.com>

All,

Version 1.4.3 of OpenDNSSEC has now been released. This is the latest stable release.

Updates:

* SUPPORT-72: Improve logging when failed to increment serial in case of key rollover and serial value "keep" [OPENDNSSEC-461].
* OPENDNSSEC-106: Add 'ods-enforcerd -p <policy>' option. This prompts the enforcer to run once and only process the specified policy and associated zones.
* OPENDNSSEC-330: NSEC3PARAM TTL can now be optionally configured in kasp.xml. Default value remains PT0S.
* OPENDNSSEC-390: ods-ksmutil: Add an option to the 'ods-ksmutil key ds-seen' command so the user can choose not to notify the enforcer.
* OPENDNSSEC-430: ods-ksmutil: Improve 'zone add' - Zone add command could warn if a specified zone file or adapter file does not exits.
* OPENDNSSEC-431: ods-ksmutil: Improve 'zone add' - Support default <input> and <output> values for DNS adapters.
* OPENDNSSEC-454: ods-ksmutil: Add option for 'ods-ksmutil key import' to check if there is a matching key in the repository before import.

Bugfixes:

* OPENDNSSEC-435: Signer Engine: Fix a serious memory leak in signature cleanup.
* OPENDNSSEC-463: Signer Engine: Duration PT0S is now printed correctly.
* OPENDNSSEC-466: Signer Engine: Created bad TSIG signature when falling back to AXFR.
* OPENDNSSEC-467: Signer Engine: After ods-signer clear, signer should not use inbound serial.

Documentation:

* http://wiki.opendnssec.org/display/DOCS

Download:

* http://dist.opendnssec.org/source/opendnssec-1.4.3.tar.gz
* http://dist.opendnssec.org/source/opendnssec-1.4.3.tar.gz.sig
* Checksum sha1: 9e985fc42ce679c930bbdbc1a38ad5ff1ca4c61a
* Checksum sha256: 22979b53851a1ec74a242ca89bbd1fc58a170272f33c6a395f0ab14f6244e491


//OpenDNSSEC team




From jerry at opendnssec.org  Tue Dec 10 10:00:40 2013
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Tue, 10 Dec 2013 11:00:40 +0100
Subject: [Opendnssec-develop] A successful Git branching model
In-Reply-To: <5284DF16.8040001@nlnetlabs.nl>
References: <5284DF16.8040001@nlnetlabs.nl>
Message-ID: <81A858BB-8FCA-44A8-846F-7D4F16E1DF4D@opendnssec.org>

On Nov 14, 2013, at 15:32 , Matthijs Mekking wrote:

> This is the git model we are considering to use for NLnet Labs (Willem
> already uses it for getdns-api)
> 
>  http://nvie.com/posts/a-successful-git-branching-model/
> 
> It also explains Git shortly but nicely in a conceptual way.


This is Git Flow that I mentioned before, I've been using it for many projects now for over a year.

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131210/01c8a78a/attachment.bin>

From jerry at opendnssec.org  Tue Dec 10 10:06:09 2013
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Tue, 10 Dec 2013 11:06:09 +0100
Subject: [Opendnssec-develop] static analyzer
In-Reply-To: <34E1D1F9-C0E7-4F6A-BC19-FAFD4289E9E5@sinodun.com>
References: <EE93DF4E-9C33-4177-82AF-812FF5D1D6A6@sinodun.com>
	<92501CBC-BD82-45C7-9345-CCDBCE279B96@sinodun.com>
	<34E1D1F9-C0E7-4F6A-BC19-FAFD4289E9E5@sinodun.com>
Message-ID: <7493205A-876C-4A25-90EA-543F601BCC79@opendnssec.org>

On Nov 25, 2013, at 16:20 , John Dickinson wrote:

> I have been playing with the clang static analyzer. (http://clang-analyzer.llvm.org/)
> 
> FYI - I ran it like this (On ubuntu 13.10)


Nice, think I looked at this a year ago and you could only run it on OS X.

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131210/55658928/attachment.bin>

From jerry at opendnssec.org  Tue Dec 10 10:11:06 2013
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Tue, 10 Dec 2013 11:11:06 +0100
Subject: [Opendnssec-develop] Jenkins tests old revision
In-Reply-To: <5295E742.7060907@nlnetlabs.nl>
References: <5295E26B.2070702@nlnetlabs.nl>
	<472E48DC-C01A-47B1-BBF3-6FB61B806282@sinodun.com>
	<5295E742.7060907@nlnetlabs.nl>
Message-ID: <69A3EB75-234B-46D8-BBD6-3C2AF7CC4AAD@opendnssec.org>

On Nov 27, 2013, at 13:36 , Yuri Schaeffer wrote:

>> However the test job is running the tests against the latest build
>> (which was generated by the build job) so it is using a build of
>> 7438. Confusing I know, but I hope this helps.
> 
> Ah yes, so they are both up to date.
> Doing the svn ci from the root of the repository would cause both jobs
> have the same (latest) revision I believe.


No, since no change has been made in the testing directory the revision is not updated.

But, you can be very sure that it will run against the latest build because the jobs are chained. test-* will not run unless build-* has run successfully.

Only chance of test-* to not test the latest build is if you commit code after the build-* job has started but if that happens then the build-* job will run again after test-* is finished.

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131210/6b704786/attachment.bin>

From jerry at opendnssec.org  Tue Dec 10 10:18:20 2013
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Tue, 10 Dec 2013 11:18:20 +0100
Subject: [Opendnssec-develop] Maintenance of dist.opendnssec.org and SVN
	today Tuesday 14:30 - 15:00 CET
Message-ID: <7BAED726-1C79-4531-AB9A-8FA6650C86DF@opendnssec.org>

Hi,

I would like to do some maintenance work on the servers here at .SE so please don't use SVN during this time.

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131210/8def2df6/attachment.bin>

From sara at sinodun.com  Tue Dec 10 11:54:58 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Tue, 10 Dec 2013 11:54:58 +0000
Subject: [Opendnssec-develop] A successful Git branching model
In-Reply-To: <81A858BB-8FCA-44A8-846F-7D4F16E1DF4D@opendnssec.org>
References: <5284DF16.8040001@nlnetlabs.nl>
	<81A858BB-8FCA-44A8-846F-7D4F16E1DF4D@opendnssec.org>
Message-ID: <9D33DD20-A25B-43F7-B04F-6239F15C8D5D@sinodun.com>


On 10 Dec 2013, at 10:00, Jerry Lundstr?m <jerry at opendnssec.org> wrote:

> On Nov 14, 2013, at 15:32 , Matthijs Mekking wrote:
> 
>> This is the git model we are considering to use for NLnet Labs (Willem
>> already uses it for getdns-api)
>> 
>> http://nvie.com/posts/a-successful-git-branching-model/
>> 
>> It also explains Git shortly but nicely in a conceptual way.
> 
> 
> This is Git Flow that I mentioned before, I've been using it for many projects now for over a year.
> 

So all my reading to date indicates that this works really nicely if you have a single product version that you support. However I haven't found anything that describes how you easily use this if you have multiple production versions that you need to maintain (like we do). I can find some descriptions of how to do this e.g.

http://stackoverflow.com/questions/18220663/advice-on-multiple-release-lines-and-git-flow-for-git-non-gurus
http://stackoverflow.com/questions/16386323/following-git-flow-how-should-you-handle-a-hotfix-of-an-earlier-release

but this doesn't really look like what Git Flow was designed for. Jerry - do you have a specific workflow to present that does support maintenance of multiple production versions - is that what you will present tomorrow?

Sara. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131210/f808f365/attachment.htm>

From jerry at opendnssec.org  Tue Dec 10 11:55:05 2013
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Tue, 10 Dec 2013 12:55:05 +0100
Subject: [Opendnssec-develop] Jenkins restart stalled
Message-ID: <2D4FA4BD-A816-4274-88E7-3166C8A6BC65@opendnssec.org>

Hi John,

I updated some addons and restarted Jenkins but it hasn't come up yet (2h+), can you check on it?

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131210/5479fc90/attachment.bin>

From rick at openfortress.nl  Tue Dec 10 13:28:46 2013
From: rick at openfortress.nl (Rick van Rein)
Date: Tue, 10 Dec 2013 14:28:46 +0100
Subject: [Opendnssec-develop] A successful Git branching model
In-Reply-To: <9D33DD20-A25B-43F7-B04F-6239F15C8D5D@sinodun.com>
References: <5284DF16.8040001@nlnetlabs.nl>
	<81A858BB-8FCA-44A8-846F-7D4F16E1DF4D@opendnssec.org>
	<9D33DD20-A25B-43F7-B04F-6239F15C8D5D@sinodun.com>
Message-ID: <F5955C99-5DB8-4003-809C-CFECAC8A94BD@openfortress.nl>

Hi,

> I haven't found anything that describes how you easily use this if you have multiple production versions that you need to maintain (like we do).

Essentially, we want to push a partially-ordered set into a fully-ordered set (or list) structure.  That's like pushing square pegs into round holes.

This is *only* a problem with historic traces, which we will want to retain for future reference, but not to the patches which are pretty much treated as an unordered set in Git (although not as extremist as in Darcs).

> http://stackoverflow.com/questions/18220663/advice-on-multiple-release-lines-and-git-flow-for-git-non-gurus

They say that they split repos, but then introduce a branch naming scheme which would work in one repo as well.

One could wonder if you need to split all branches in a repo, or just the master.  I could imagine this:

1. Right after creating a new, separately supported version X.Y in master, fork a new branch as master-X.Y
2. When version X.Y is updated to X.Y.Z, patch it in the master-X.Y branch
3. Consider the patch for later master-A.B branches, perhaps until the version where they are incompatible or otherwise bad
4. When X.Y matches master, and master-X.Y changed, update master as well

Effectively, master-X.Y becomes a duplicate of master.  The advantage for naming it is that packagers can continue to track that branch throughout the supported life for X.Y, which is not possible when using master itself.  It's a bit like running "Debian Wheezy" versus "Debian Stable".  I'm not sure if the duplication could be avoided with a nifty tagging scheme.


Note that I am not this advanced with Git, these are just ideas.


Cheers,
 -Rick

From jerry at opendnssec.org  Tue Dec 10 13:39:18 2013
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Tue, 10 Dec 2013 14:39:18 +0100
Subject: [Opendnssec-develop] Re: Maintenance of dist.opendnssec.org and SVN
	today Tuesday 14:30 - 15:00 CET
In-Reply-To: <7BAED726-1C79-4531-AB9A-8FA6650C86DF@opendnssec.org>
References: <7BAED726-1C79-4531-AB9A-8FA6650C86DF@opendnssec.org>
Message-ID: <00E2F79C-B1CA-43D9-A1F1-D81F059A2F8C@opendnssec.org>

On Dec 10, 2013, at 11:18 , Jerry Lundstr?m wrote:

> I would like to do some maintenance work on the servers here at .SE so please don't use SVN during this time.


Done, feel free to use SVN.

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131210/da8982fa/attachment.bin>

From jerry at opendnssec.org  Tue Dec 10 14:04:20 2013
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Tue, 10 Dec 2013 15:04:20 +0100
Subject: [Opendnssec-develop] A successful Git branching model
In-Reply-To: <9D33DD20-A25B-43F7-B04F-6239F15C8D5D@sinodun.com>
References: <5284DF16.8040001@nlnetlabs.nl>
	<81A858BB-8FCA-44A8-846F-7D4F16E1DF4D@opendnssec.org>
	<9D33DD20-A25B-43F7-B04F-6239F15C8D5D@sinodun.com>
Message-ID: <C0766B99-8A06-47BF-842A-8207D20A4FAF@opendnssec.org>

On Dec 10, 2013, at 12:54 , Sara Dickinson wrote:

> So all my reading to date indicates that this works really nicely if you have a single product version that you support. However I haven't found anything that describes how you easily use this if you have multiple production versions that you need to maintain (like we do). I can find some descriptions of how to do this e.g.
> 
> http://stackoverflow.com/questions/18220663/advice-on-multiple-release-lines-and-git-flow-for-git-non-gurus
> http://stackoverflow.com/questions/16386323/following-git-flow-how-should-you-handle-a-hotfix-of-an-earlier-release
> 
> but this doesn't really look like what Git Flow was designed for. Jerry - do you have a specific workflow to present that does support maintenance of multiple production versions - is that what you will present tomorrow?


It may be true that Git Flow was not designed with this in mind but it can work. Git Flows basic idea is that you work in branches that is typically named after the issue. These branches does not necessary need to be forked from develop so you could have long lived release branches (ex release/1.3) that you fork from and merge to then release from.

BUT! Having said that there are different layers of work flows I want to discuss tomorrow that separates these type of issues from the development and making them a non-issue really. Unfortunately, since I just got back today from my holiday, I'm not able to share these things in details until we meet tomorrow.

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131210/1d148dac/attachment.bin>

From jad at sinodun.com  Thu Dec 12 13:49:04 2013
From: jad at sinodun.com (John Dickinson)
Date: Thu, 12 Dec 2013 13:49:04 +0000
Subject: [Opendnssec-develop] building on OS X (SUPPORT-86)
Message-ID: <895A0CA8-4899-49B1-A549-847CC1A60AB0@sinodun.com>

Hi,

This applies to trunk and the 1.4 branch. Seems like things are weird on OS X.

./configure CFLAGS=?-D_POSIX_C_SOURCE? works (well it builds at least).

However editing configure.ac and adding (to the darwin target-specific stuff)

Index: configure.ac
===================================================================
--- configure.ac	(revision 7426)
+++ configure.ac	(working copy)
@@ -133,6 +133,7 @@
 	    [Define if your platform breaks doing a seteuid before a setuid])
 	AC_DEFINE(BROKEN_SETREUID, 1, [Define if your setreuid() is broken])
 	AC_DEFINE(BROKEN_SETREGID, 1, [Define if your setregid() is broken])
+    CFLAGS="-D_DARWIN_C_SOURCE $CFLAGS"
     ;;
 esac

requires _DARWIN_C_SOURCE to work. If you use _POSIX_C_SOURCE (or nothing) you get the following build error:

gcc -DHAVE_CONFIG_H -I. -I../../../common  -I../../../common -I../../../common -I./cryptoki_compat -I/usr/local/include -I/opt/local/include/libxml2  -std=c99 -D_POSIX_C_SOURCE -g -O2 -pedantic -Wall -Wextra -D_THREAD_SAFE -pthread -MT pin.o -MD -MP -MF .deps/pin.Tpo -c -o pin.o pin.c
pin.c:111:17: error: variable has incomplete type 'union semun'
    union semun arg;
                ^
pin.c:111:11: note: forward declaration of 'union semun'
    union semun arg;
          ^
pin.c:419:17: error: variable has incomplete type 'union semun'
    union semun arg;
                ^
pin.c:419:11: note: forward declaration of 'union semun'
    union semun arg;
          ^
2 errors generated.

BTW:

        #  ifndef _POSIX_C_SOURCE
        #    define _POSIX_C_SOURCE 200112
        #  endif

is in the the AH_BOTTOM clause. Should that be 200112L to be consistent with the _XOPEN_SOURCE 600???

Any ideas?

This was tested on Mavericks.
John
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131212/22d9d9a3/attachment.bin>

From jad at sinodun.com  Thu Dec 12 16:32:49 2013
From: jad at sinodun.com (John Dickinson)
Date: Thu, 12 Dec 2013 16:32:49 +0000
Subject: [Opendnssec-develop] building on OS X (SUPPORT-86)
In-Reply-To: <895A0CA8-4899-49B1-A549-847CC1A60AB0@sinodun.com>
References: <895A0CA8-4899-49B1-A549-847CC1A60AB0@sinodun.com>
Message-ID: <76A7045C-F52C-4E58-9DA7-29023691D72C@sinodun.com>

It appears that having both

	#  ifndef _XOPEN_SOURCE
	#    define _XOPEN_SOURCE 600
	#  endif
	#  ifndef _POSIX_C_SOURCE
	#    define _POSIX_C_SOURCE 200112
	#  endif

in configure.ac is the problem. Remove this and you don?t need _POSIX_C_SOURCE or _DARWIN_C_SOURCE to build the code.

Just double checked and removing this doesn?t break the build on Ubuntu 13.10. Are these defines needed?

John


On 12 Dec 2013, at 13:49, John Dickinson <jad at sinodun.com> wrote:

> Hi,
> 
> This applies to trunk and the 1.4 branch. Seems like things are weird on OS X.
> 
> ./configure CFLAGS=?-D_POSIX_C_SOURCE? works (well it builds at least).
> 
> However editing configure.ac and adding (to the darwin target-specific stuff)
> 
> Index: configure.ac
> ===================================================================
> --- configure.ac	(revision 7426)
> +++ configure.ac	(working copy)
> @@ -133,6 +133,7 @@
> 	    [Define if your platform breaks doing a seteuid before a setuid])
> 	AC_DEFINE(BROKEN_SETREUID, 1, [Define if your setreuid() is broken])
> 	AC_DEFINE(BROKEN_SETREGID, 1, [Define if your setregid() is broken])
> +    CFLAGS="-D_DARWIN_C_SOURCE $CFLAGS"
>     ;;
> esac
> 
> requires _DARWIN_C_SOURCE to work. If you use _POSIX_C_SOURCE (or nothing) you get the following build error:
> 
> gcc -DHAVE_CONFIG_H -I. -I../../../common  -I../../../common -I../../../common -I./cryptoki_compat -I/usr/local/include -I/opt/local/include/libxml2  -std=c99 -D_POSIX_C_SOURCE -g -O2 -pedantic -Wall -Wextra -D_THREAD_SAFE -pthread -MT pin.o -MD -MP -MF .deps/pin.Tpo -c -o pin.o pin.c
> pin.c:111:17: error: variable has incomplete type 'union semun'
>    union semun arg;
>                ^
> pin.c:111:11: note: forward declaration of 'union semun'
>    union semun arg;
>          ^
> pin.c:419:17: error: variable has incomplete type 'union semun'
>    union semun arg;
>                ^
> pin.c:419:11: note: forward declaration of 'union semun'
>    union semun arg;
>          ^
> 2 errors generated.
> 
> BTW:
> 
>        #  ifndef _POSIX_C_SOURCE
>        #    define _POSIX_C_SOURCE 200112
>        #  endif
> 
> is in the the AH_BOTTOM clause. Should that be 200112L to be consistent with the _XOPEN_SOURCE 600???
> 
> Any ideas?
> 
> This was tested on Mavericks.
> John
> _______________________________________________
> Opendnssec-develop mailing list
> Opendnssec-develop at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131212/7ddc6ea1/attachment.bin>

From jakob at kirei.se  Fri Dec 13 08:14:06 2013
From: jakob at kirei.se (Jakob Schlyter)
Date: Fri, 13 Dec 2013 09:14:06 +0100
Subject: [Opendnssec-develop] Moving OpenDNSSEC to git
Message-ID: <8BE4AAEF-4E34-4D46-9283-A3BEB3792E23@kirei.se>

Greetings,

In the next month or so, we'll be moving OpenDNSSEC development from Subversion to git in order to facilitate better source code management, improve the way we can accept contributed code and to implement robust code review processes. We'll be using a slightly modified git-flow model - details will be posted on the wiki as soon as they are ready.

As you may know, SoftHSMv2 is already using git and we'll be moving SoftHSMv1 shortly as well. All legacy code (auditor, hsmbully, pkcs15-dnssec etc) has already been moved as well -- see https://github.com/opendnssec.


If you have any questions, feel free to contact me directly or via this mailing list.

	jakob



From jerry at opendnssec.org  Fri Dec 13 09:41:47 2013
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Fri, 13 Dec 2013 10:41:47 +0100
Subject: [Opendnssec-develop] building on OS X (SUPPORT-86)
In-Reply-To: <76A7045C-F52C-4E58-9DA7-29023691D72C@sinodun.com>
References: <895A0CA8-4899-49B1-A549-847CC1A60AB0@sinodun.com>
	<76A7045C-F52C-4E58-9DA7-29023691D72C@sinodun.com>
Message-ID: <9A83EA00-7AC0-471C-969C-676670BFB9DC@opendnssec.org>

On Dec 12, 2013, at 17:32 , John Dickinson wrote:

> Just double checked and removing this doesn?t break the build on Ubuntu 13.10. Are these defines needed?


I don't think Ubuntu is a good platform to test this on since these types of defines usually are not a problem in Linux, can you try on FreeBSD and Solaris perhaps?

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131213/2afcc46c/attachment.bin>

From jerry at opendnssec.org  Fri Dec 13 13:17:56 2013
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Fri, 13 Dec 2013 14:17:56 +0100
Subject: [Opendnssec-develop] SVN changes: branches/OpenDNSSEC-enforcer-ng
	is now trunk/OpenDNSSEC
Message-ID: <E8BB01D3-95A2-4A2E-84E8-D415CFD37FD6@opendnssec.org>

Hi all,

Our trunk/OpenDNSSEC has been in limbo for a while and branches/OpenDNSSEC-enforcer-ng had really become the real trunk.

So we decided during the developer meet, that we are having now, to replace trunk/OpenDNSSEC with branches/OpenDNSSEC-enforcer-ng and this has been done now.

Hopefully all changes make in the old trunk has been merge to enforcer-ng branch before the move but if you find anything please shout.

The old trunk can be found in tags now at http://svn.opendnssec.org/tags/OpenDNSSEC-trunk-20131213/ .

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131213/c9284af5/attachment.bin>

From jakob at kirei.se  Mon Dec 16 07:08:21 2013
From: jakob at kirei.se (Jakob Schlyter)
Date: Mon, 16 Dec 2013 08:08:21 +0100
Subject: [Opendnssec-develop] SoftHSM v1 now at git
Message-ID: <EE718640-73FB-4DF3-AA0F-7E4526B0AB66@kirei.se>

I've now moved SoftHSM v1 to git at https://github.com/opendnssec/SoftHSMv1.

SoftHSM v1 is the first module that will use the git flow process for managing code. Hence, any changes must be made in your own (cloned) repository, before requesting code review by submitting a pull request to the main repository. After review, the code will be merged into the develop branch [1]. Before release, one of our release managers (Jerry, with Jakob as backup) will release and merge changes back to master [2].

The subversion repository for SoftHSMv1 will stick around for a couple days more, please do NOT commit any code to this repository.


	jakob



[1] https://github.com/opendnssec/SoftHSMv1/tree/develop
[2] https://github.com/opendnssec/SoftHSMv1/tree/master



From sara at sinodun.com  Mon Dec 16 17:36:30 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Mon, 16 Dec 2013 17:36:30 +0000
Subject: Fwd: [Opendnssec-develop] Developer workshop
References: <4507936A-DEBA-4D9A-A643-9306CA02C514@sinodun.com>
Message-ID: <B5C5D248-80FC-4620-B672-E32091EFD2DE@sinodun.com>

Hi All, 

I have written up the minutes from the workshop last week for review:

https://wiki.opendnssec.org/display/OpenDNSSEC/Developer+Workshop+-+Stockholm+Dec+2013+-+Minutes

Please let me know of any omissions/mistakes/mis-recollections! 

The next workshop is planned for Thursday 27th & Friday 28th of February 2014 to be held in the UK (either in London or Oxfordshire). This will be a code sprint focussed on 2.0 testing and development. 

Sara. 

Begin forwarded message:

> Hi All, 
> 
> I have slightly updated the agenda for the developers workshop:
> https://wiki.opendnssec.org/display/OpenDNSSEC/Developer+Workshop+-+Stockholm+Dec+2013



From matthijs at nlnetlabs.nl  Tue Dec 17 07:53:44 2013
From: matthijs at nlnetlabs.nl (Matthijs Mekking)
Date: Tue, 17 Dec 2013 08:53:44 +0100
Subject: Fwd: [Opendnssec-develop] Developer workshop
In-Reply-To: <B5C5D248-80FC-4620-B672-E32091EFD2DE@sinodun.com>
References: <4507936A-DEBA-4D9A-A643-9306CA02C514@sinodun.com>
	<B5C5D248-80FC-4620-B672-E32091EFD2DE@sinodun.com>
Message-ID: <52B00308.8080100@nlnetlabs.nl>

Hi,

On 12/16/2013 06:36 PM, Sara Dickinson wrote:
> Hi All, 
> 
> I have written up the minutes from the workshop last week for review:
> 
> https://wiki.opendnssec.org/display/OpenDNSSEC/Developer+Workshop+-+Stockholm+Dec+2013+-+Minutes
> 
> Please let me know of any omissions/mistakes/mis-recollections! 

Well, I didn't fully agree on preferring github over gitlab ;)


Furthermore:
- "We should take a look at what SIDN have done to automate their DS
upload and capture it as a contrib at least"

Is this SIDN or do you mean Surfnet? I recall Surfnet has something like
this, but am not aware of "SIDN's upload and capture".


On the 2.0 discussions:
- 'ods-enforcer update conf' should be renamed 'ods-enforcer update
repository' as the name is misleading since all the command does is
reload the repository section of conf.xml.

Wouldn't "update repositories" or "update repositorylist" be even better?


About the 2.0.0a4 sprint:
- What is ODS-16?


Best regards,
 Matthijs

> The next workshop is planned for Thursday 27th & Friday 28th of February 2014 to be held in the UK (either in London or Oxfordshire). This will be a code sprint focussed on 2.0 testing and development. 
> 
> Sara. 
> 
> Begin forwarded message:
> 
>> Hi All, 
>>
>> I have slightly updated the agenda for the developers workshop:
>> https://wiki.opendnssec.org/display/OpenDNSSEC/Developer+Workshop+-+Stockholm+Dec+2013
> 
> _______________________________________________
> Opendnssec-develop mailing list
> Opendnssec-develop at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop
> 



From jerry at opendnssec.org  Tue Dec 17 09:55:35 2013
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Tue, 17 Dec 2013 10:55:35 +0100
Subject: [Opendnssec-develop] Jenkins Git problems (Was: SoftHSM v1 now at
	git)
In-Reply-To: <EE718640-73FB-4DF3-AA0F-7E4526B0AB66@kirei.se>
References: <EE718640-73FB-4DF3-AA0F-7E4526B0AB66@kirei.se>
Message-ID: <AFB3C5E3-42A5-494C-9FEA-CBA8630D0403@opendnssec.org>

On Dec 16, 2013, at 08:08 , Jakob Schlyter wrote:

> The subversion repository for SoftHSMv1 will stick around for a couple days more, please do NOT commit any code to this repository.


FYI,

I am trying to get the new SoftHSM v1 Git repository to work with Jenkins and there are a few problems.

- Git Plugin in Jenkins (uses cli tools) requires Git 1.7+ and we have older versions on some platforms
- JGit (Pure Java) manage to check out the repository but somehow deletes all files

Hopefully I will get this working this week, stay tuned!

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131217/2bdda828/attachment.bin>

From sara at sinodun.com  Tue Dec 17 10:07:11 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Tue, 17 Dec 2013 10:07:11 +0000
Subject: [Opendnssec-develop] Developer workshop
In-Reply-To: <52B00308.8080100@nlnetlabs.nl>
References: <4507936A-DEBA-4D9A-A643-9306CA02C514@sinodun.com>
	<B5C5D248-80FC-4620-B672-E32091EFD2DE@sinodun.com>
	<52B00308.8080100@nlnetlabs.nl>
Message-ID: <5A08B5FA-D359-44EC-8B6F-3FBEECBB6DD6@sinodun.com>


On 17 Dec 2013, at 07:53, Matthijs Mekking <matthijs at NLnetLabs.nl> wrote:

> Hi,
> 
> On 12/16/2013 06:36 PM, Sara Dickinson wrote:
>> Hi All, 
>> 
>> I have written up the minutes from the workshop last week for review:
>> 
>> https://wiki.opendnssec.org/display/OpenDNSSEC/Developer+Workshop+-+Stockholm+Dec+2013+-+Minutes
>> 
>> Please let me know of any omissions/mistakes/mis-recollections! 
> 
> Well, I didn't fully agree on preferring github over gitlab ;)
> 

Sorry - I did miss this. Can you remind me why?


> 
> Furthermore:
> - "We should take a look at what SIDN have done to automate their DS
> upload and capture it as a contrib at least"
> 
> Is this SIDN or do you mean Surfnet? I recall Surfnet has something like
> this, but am not aware of "SIDN's upload and capture".

Brain fuzz while writing up shorthand notes?. indeed this should be SurfNET (updated on wiki page)

> 
> 
> On the 2.0 discussions:
> - 'ods-enforcer update conf' should be renamed 'ods-enforcer update
> repository' as the name is misleading since all the command does is
> reload the repository section of conf.xml.
> 
> Wouldn't "update repositories" or "update repositorylist" be even better?

Good point! 'update repositorylist' does seem the most correct as this is the name of the top level xml tag. 

> 
> 
> About the 2.0.0a4 sprint:
> - What is ODS-16?

It is an id for a code review in Crucible?.

Thanks for the feedback!

Sara.



From jakob at kirei.se  Tue Dec 17 11:30:45 2013
From: jakob at kirei.se (Jakob Schlyter)
Date: Tue, 17 Dec 2013 12:30:45 +0100
Subject: [Opendnssec-develop] Developer workshop
In-Reply-To: <5A08B5FA-D359-44EC-8B6F-3FBEECBB6DD6@sinodun.com>
References: <4507936A-DEBA-4D9A-A643-9306CA02C514@sinodun.com>
	<B5C5D248-80FC-4620-B672-E32091EFD2DE@sinodun.com>
	<52B00308.8080100@nlnetlabs.nl>
	<5A08B5FA-D359-44EC-8B6F-3FBEECBB6DD6@sinodun.com>
Message-ID: <BFECAABE-D45C-48B9-9FE2-B96E1AFF04D4@kirei.se>

On 17 dec 2013, at 11:07, Sara Dickinson <sara at sinodun.com> wrote:

> Good point! 'update repository list' does seem the most correct as this is the name of the top level xml tag. 

I hope we can agree that "update repo" should work as well.

	jakob

-- 
Jakob Schlyter
Kirei AB - www.kirei.se





From matthijs at nlnetlabs.nl  Tue Dec 17 11:32:32 2013
From: matthijs at nlnetlabs.nl (Matthijs Mekking)
Date: Tue, 17 Dec 2013 12:32:32 +0100
Subject: [Opendnssec-develop] Developer workshop
In-Reply-To: <BFECAABE-D45C-48B9-9FE2-B96E1AFF04D4@kirei.se>
References: <4507936A-DEBA-4D9A-A643-9306CA02C514@sinodun.com>
	<B5C5D248-80FC-4620-B672-E32091EFD2DE@sinodun.com>
	<52B00308.8080100@nlnetlabs.nl>
	<5A08B5FA-D359-44EC-8B6F-3FBEECBB6DD6@sinodun.com>
	<BFECAABE-D45C-48B9-9FE2-B96E1AFF04D4@kirei.se>
Message-ID: <52B03650.5090500@nlnetlabs.nl>

On 12/17/2013 12:30 PM, Jakob Schlyter wrote:
> On 17 dec 2013, at 11:07, Sara Dickinson <sara at sinodun.com> wrote:
> 
>> Good point! 'update repository list' does seem the most correct as this is the name of the top level xml tag. 
> 
> I hope we can agree that "update repo" should work as well.

I am fine with something shorter, only with "update repository" I first
falsely assumed it was to update one repository. "update repos" perhaps?

Matthijs

> 
> 	jakob
> 



From jerry at opendnssec.org  Tue Dec 17 12:21:52 2013
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Tue, 17 Dec 2013 13:21:52 +0100
Subject: [Opendnssec-develop] Developer workshop
In-Reply-To: <5A08B5FA-D359-44EC-8B6F-3FBEECBB6DD6@sinodun.com>
References: <4507936A-DEBA-4D9A-A643-9306CA02C514@sinodun.com>
	<B5C5D248-80FC-4620-B672-E32091EFD2DE@sinodun.com>
	<52B00308.8080100@nlnetlabs.nl>
	<5A08B5FA-D359-44EC-8B6F-3FBEECBB6DD6@sinodun.com>
Message-ID: <0493A9C4-2C8A-4589-AC3E-66396939FCEB@opendnssec.org>

On Dec 17, 2013, at 11:07 , Sara Dickinson wrote:

> On 17 Dec 2013, at 07:53, Matthijs Mekking <matthijs at NLnetLabs.nl> wrote:
>> 
>> Well, I didn't fully agree on preferring github over gitlab ;)
> 
> Sorry - I did miss this. Can you remind me why?


I was under the impression that we did agree to use GitHub since it felt secure enough and less work then to manage our own instance. Think Patrik and Jakob brought up the argument that other companies uses GitHub private repositories to store sensitive code and as such relies on GitHub to keep it secure. Also with an own instance there is more administration with users if they are to upload pull requests. We get a lot better system for the community with GitHub and at a lot less work for us.

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131217/e4f698e8/attachment.bin>

From jakob at kirei.se  Tue Dec 17 13:21:18 2013
From: jakob at kirei.se (Jakob Schlyter)
Date: Tue, 17 Dec 2013 14:21:18 +0100
Subject: [Opendnssec-develop] Developer workshop
In-Reply-To: <0493A9C4-2C8A-4589-AC3E-66396939FCEB@opendnssec.org>
References: <4507936A-DEBA-4D9A-A643-9306CA02C514@sinodun.com>
	<B5C5D248-80FC-4620-B672-E32091EFD2DE@sinodun.com>
	<52B00308.8080100@nlnetlabs.nl>
	<5A08B5FA-D359-44EC-8B6F-3FBEECBB6DD6@sinodun.com>
	<0493A9C4-2C8A-4589-AC3E-66396939FCEB@opendnssec.org>
Message-ID: <A6A640DB-7FC3-45B3-8E3C-7CCBBF3E7F20@kirei.se>

On 17 dec 2013, at 13:21, Jerry Lundstr?m <jerry at opendnssec.org> wrote:

> I was under the impression that we did agree to use GitHub since it felt secure enough and less work then to manage our own instance. Think Patrik and Jakob brought up the argument that other companies uses GitHub private repositories to store sensitive code and as such relies on GitHub to keep it secure. Also with an own instance there is more administration with users if they are to upload pull requests. We get a lot better system for the community with GitHub and at a lot less work for us.

+1, I have seen no (good) argument for _not_ using GitHub.

	jakob

-- 
Jakob Schlyter
Kirei AB - www.kirei.se





From matthijs at nlnetlabs.nl  Tue Dec 17 13:28:22 2013
From: matthijs at nlnetlabs.nl (Matthijs Mekking)
Date: Tue, 17 Dec 2013 14:28:22 +0100
Subject: [Opendnssec-develop] Developer workshop
In-Reply-To: <A6A640DB-7FC3-45B3-8E3C-7CCBBF3E7F20@kirei.se>
References: <4507936A-DEBA-4D9A-A643-9306CA02C514@sinodun.com>	<B5C5D248-80FC-4620-B672-E32091EFD2DE@sinodun.com>	<52B00308.8080100@nlnetlabs.nl>	<5A08B5FA-D359-44EC-8B6F-3FBEECBB6DD6@sinodun.com>	<0493A9C4-2C8A-4589-AC3E-66396939FCEB@opendnssec.org>
	<A6A640DB-7FC3-45B3-8E3C-7CCBBF3E7F20@kirei.se>
Message-ID: <52B05176.8030703@nlnetlabs.nl>

My earlier comment is getting picked up more serious then expected (did
no one notices the emoticon?)

Anyway, I replied earlier to Sara off list:

 "I like to have less external dependencies as possible (for several
  kind of reasons: collateral damage risks, entity termination, ...).

  But I did agree that less maintenance overhead is a strong argument
  for using github (but personally I would still prefer gitlab)."

(You might find them no good arguments. I do)

Nevertheless, we decided to use github instead of gitlab, rough
consensus style, weighing the arguments. Perhaps it is worth mentioning
those arguments that make us come to that decision.

Best regards,
  Matthijs


On 12/17/2013 02:21 PM, Jakob Schlyter wrote:
> On 17 dec 2013, at 13:21, Jerry Lundstr?m <jerry at opendnssec.org> wrote:
> 
>> I was under the impression that we did agree to use GitHub since it felt secure enough and less work then to manage our own instance. Think Patrik and Jakob brought up the argument that other companies uses GitHub private repositories to store sensitive code and as such relies on GitHub to keep it secure. Also with an own instance there is more administration with users if they are to upload pull requests. We get a lot better system for the community with GitHub and at a lot less work for us.
> 
> +1, I have seen no (good) argument for _not_ using GitHub.
> 
> 	jakob
> 



From jakob at kirei.se  Tue Dec 17 13:32:27 2013
From: jakob at kirei.se (Jakob Schlyter)
Date: Tue, 17 Dec 2013 14:32:27 +0100
Subject: [Opendnssec-develop] Developer workshop
In-Reply-To: <52B05176.8030703@nlnetlabs.nl>
References: <4507936A-DEBA-4D9A-A643-9306CA02C514@sinodun.com>	<B5C5D248-80FC-4620-B672-E32091EFD2DE@sinodun.com>	<52B00308.8080100@nlnetlabs.nl>	<5A08B5FA-D359-44EC-8B6F-3FBEECBB6DD6@sinodun.com>	<0493A9C4-2C8A-4589-AC3E-66396939FCEB@opendnssec.org>
	<A6A640DB-7FC3-45B3-8E3C-7CCBBF3E7F20@kirei.se>
	<52B05176.8030703@nlnetlabs.nl>
Message-ID: <6ED55994-60B0-418D-86F0-3852D700FE24@kirei.se>

On 17 dec 2013, at 14:28, Matthijs Mekking <matthijs at NLnetLabs.nl> wrote:

> Nevertheless, we decided to use github instead of gitlab, rough
> consensus style, weighing the arguments. Perhaps it is worth mentioning
> those arguments that make us come to that decision.

Agreed, and nothing is set in stone - we can always revise this decision later if needed.

	jakob

-- 
Jakob Schlyter
Kirei AB - www.kirei.se





From sara at sinodun.com  Tue Dec 17 14:11:44 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Tue, 17 Dec 2013 14:11:44 +0000
Subject: [Opendnssec-develop] RE: jenkins test job on trunk
Message-ID: <AD5532E3-CF93-4BF5-B0EC-13C999A709BD@sinodun.com>

Hi All, 

fyi - I have just disabled the test-opendnssec-trunk job since it has been failing since the merge of the enforcer-ng branch last week. I haven?t had time to investigate why, I have just disabled it for now until I do?.

Sara.

From jerry at opendnssec.org  Tue Dec 17 15:32:24 2013
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Tue, 17 Dec 2013 16:32:24 +0100
Subject: [Opendnssec-develop] Re: Jenkins Git problems (Was: SoftHSM v1 now
	at git)
In-Reply-To: <AFB3C5E3-42A5-494C-9FEA-CBA8630D0403@opendnssec.org>
References: <EE718640-73FB-4DF3-AA0F-7E4526B0AB66@kirei.se>
	<AFB3C5E3-42A5-494C-9FEA-CBA8630D0403@opendnssec.org>
Message-ID: <838D669F-2C93-4BC6-9834-20021FBE5B44@opendnssec.org>

Update,

On Dec 17, 2013, at 10:55 , Jerry Lundstr?m wrote:

> - Git Plugin in Jenkins (uses cli tools) requires Git 1.7+ and we have older versions on some platforms
> - JGit (Pure Java) manage to check out the repository but somehow deletes all files


JGit is the only option since we have platforms that does not have 1.7+ but JGit is not able to fetch updates correctly.
Managed to fix that with git reset --hard (that works with older versions of git) but then its the problem that not all platforms have git installed?
AND I can't get it installed on all since I would need to reinstall some of the platforms just to get stuff installed since they have been neglected for some time.

I even checked GitHub's SVN implementation but they are basing it on a old SVN version so (of course) some of the commands that Jenkins need does not work and it bangs.

So we are in a bit of dilemma?

Options:
1) Only build on the hosts we have git on
2) Reinstall all platforms now with the new agreed OS support (<- my vote, clean up mess now not later)
3) ..?

Platforms missing git:
ubuntu12-amd64-ods03
freebsd64-ods06
netbsd64-ods09
openbsd64-ods10
suse64-ods11
ubuntu32-ods12
opensuse32-ods14
freebsd32-ods15

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131217/ba237885/attachment.bin>

From jerry at opendnssec.org  Tue Dec 17 15:34:39 2013
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Tue, 17 Dec 2013 16:34:39 +0100
Subject: [Opendnssec-develop] Re: Jenkins Git problems (Was: SoftHSM v1 now
	at git)
In-Reply-To: <838D669F-2C93-4BC6-9834-20021FBE5B44@opendnssec.org>
References: <EE718640-73FB-4DF3-AA0F-7E4526B0AB66@kirei.se>
	<AFB3C5E3-42A5-494C-9FEA-CBA8630D0403@opendnssec.org>
	<838D669F-2C93-4BC6-9834-20021FBE5B44@opendnssec.org>
Message-ID: <262C91BF-30B4-4119-B33D-9DAF1488E78C@opendnssec.org>

On Dec 17, 2013, at 16:32 , Jerry Lundstr?m wrote:

> 2) Reinstall all platforms now with the new agreed OS support (<- my vote, clean up mess now not later)

One note, yes this will delay the move to GitHub. Only important repository that is moved is SoftHSM v1 and it only has one commit (by me for adding git to testing framework) and a pull request so we could revert that move now before more is poured into it.

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131217/3aff0503/attachment.bin>

From jerry at opendnssec.org  Tue Dec 17 15:36:43 2013
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Tue, 17 Dec 2013 16:36:43 +0100
Subject: [Opendnssec-develop] Re: Jenkins Git problems (Was: SoftHSM v1 now
	at git)
In-Reply-To: <262C91BF-30B4-4119-B33D-9DAF1488E78C@opendnssec.org>
References: <EE718640-73FB-4DF3-AA0F-7E4526B0AB66@kirei.se>
	<AFB3C5E3-42A5-494C-9FEA-CBA8630D0403@opendnssec.org>
	<838D669F-2C93-4BC6-9834-20021FBE5B44@opendnssec.org>
	<262C91BF-30B4-4119-B33D-9DAF1488E78C@opendnssec.org>
Message-ID: <CEF7A4AF-ED05-49B5-B692-C64A5ABF2F11@opendnssec.org>

On Dec 17, 2013, at 16:34 , Jerry Lundstr?m wrote:

> One note, yes this will delay the move to GitHub. Only important repository that is moved is SoftHSM v1 and it only has one commit (by me for adding git to testing framework) and a pull request so we could revert that move now before more is poured into it.


Just looked at the pull request, it a README convert to MarkDown. Nothing blocking!

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131217/362a0026/attachment.bin>

From jakob at kirei.se  Tue Dec 17 15:44:16 2013
From: jakob at kirei.se (Jakob Schlyter)
Date: Tue, 17 Dec 2013 16:44:16 +0100
Subject: [Opendnssec-develop] Re: Jenkins Git problems (Was: SoftHSM v1
	now at git)
In-Reply-To: <CEF7A4AF-ED05-49B5-B692-C64A5ABF2F11@opendnssec.org>
References: <EE718640-73FB-4DF3-AA0F-7E4526B0AB66@kirei.se>
	<AFB3C5E3-42A5-494C-9FEA-CBA8630D0403@opendnssec.org>
	<838D669F-2C93-4BC6-9834-20021FBE5B44@opendnssec.org>
	<262C91BF-30B4-4119-B33D-9DAF1488E78C@opendnssec.org>
	<CEF7A4AF-ED05-49B5-B692-C64A5ABF2F11@opendnssec.org>
Message-ID: <88536A1A-5423-4996-AB59-7EC42367295E@kirei.se>

Why not check out using HTTPS?

	jakob

-- 
Jakob Schlyter
Kirei AB - http://www.kirei.se/


> 17 dec 2013 kl. 16:36 skrev Jerry Lundstr?m <jerry at opendnssec.org>:
> 
>> On Dec 17, 2013, at 16:34 , Jerry Lundstr?m wrote:
>> 
>> One note, yes this will delay the move to GitHub. Only important repository that is moved is SoftHSM v1 and it only has one commit (by me for adding git to testing framework) and a pull request so we could revert that move now before more is poured into it.
> 
> 
> Just looked at the pull request, it a README convert to MarkDown. Nothing blocking!
> 
> --
> Jerry Lundstr?m - OpenDNSSEC Developer
> http://www.opendnssec.org/
> 
> _______________________________________________
> Opendnssec-develop mailing list
> Opendnssec-develop at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop


From jerry at opendnssec.org  Tue Dec 17 15:50:18 2013
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Tue, 17 Dec 2013 16:50:18 +0100
Subject: [Opendnssec-develop] Re: Jenkins Git problems (Was: SoftHSM v1
	now at git)
In-Reply-To: <88536A1A-5423-4996-AB59-7EC42367295E@kirei.se>
References: <EE718640-73FB-4DF3-AA0F-7E4526B0AB66@kirei.se>
	<AFB3C5E3-42A5-494C-9FEA-CBA8630D0403@opendnssec.org>
	<838D669F-2C93-4BC6-9834-20021FBE5B44@opendnssec.org>
	<262C91BF-30B4-4119-B33D-9DAF1488E78C@opendnssec.org>
	<CEF7A4AF-ED05-49B5-B692-C64A5ABF2F11@opendnssec.org>
	<88536A1A-5423-4996-AB59-7EC42367295E@kirei.se>
Message-ID: <1882175230223187270@unknownmsgid>

Already doing that, HTTP(S) URLs works with JGit.

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

On 17 dec 2013, at 16:44, Jakob Schlyter <jakob at kirei.se> wrote:

Why not check out using HTTPS?

   jakob

-- 
Jakob Schlyter
Kirei AB - http://www.kirei.se/


17 dec 2013 kl. 16:36 skrev Jerry Lundstr?m <jerry at opendnssec.org>:


On Dec 17, 2013, at 16:34 , Jerry Lundstr?m wrote:


One note, yes this will delay the move to GitHub. Only important repository
that is moved is SoftHSM v1 and it only has one commit (by me for adding
git to testing framework) and a pull request so we could revert that move
now before more is poured into it.



Just looked at the pull request, it a README convert to MarkDown. Nothing
blocking!


--

Jerry Lundstr?m - OpenDNSSEC Developer

http://www.opendnssec.org/


_______________________________________________

Opendnssec-develop mailing list

Opendnssec-develop at lists.opendnssec.org

https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131217/583768c2/attachment.htm>

From jakob at kirei.se  Tue Dec 17 16:21:54 2013
From: jakob at kirei.se (Jakob Schlyter)
Date: Tue, 17 Dec 2013 17:21:54 +0100
Subject: [Opendnssec-develop] Jenkins Git problems (Was: SoftHSM v1 now at
	git)
In-Reply-To: <1882175230223187270@unknownmsgid>
References: <EE718640-73FB-4DF3-AA0F-7E4526B0AB66@kirei.se>
	<AFB3C5E3-42A5-494C-9FEA-CBA8630D0403@opendnssec.org>
	<838D669F-2C93-4BC6-9834-20021FBE5B44@opendnssec.org>
	<262C91BF-30B4-4119-B33D-9DAF1488E78C@opendnssec.org>
	<CEF7A4AF-ED05-49B5-B692-C64A5ABF2F11@opendnssec.org>
	<88536A1A-5423-4996-AB59-7EC42367295E@kirei.se>
	<1882175230223187270@unknownmsgid>
Message-ID: <72A9F5DF-1A89-41C5-943A-4145DFBA79D6@kirei.se>

On 17 dec 2013, at 16:50, Jerry Lundstr?m <jerry at opendnssec.org> wrote:

> Already doing that, HTTP(S) URLs works with JGit.

I'm thinking we can skip JGit.

wget -o softhsm.zip https://github.com/opendnssec/SoftHSMv1/archive/develop.zip
unzip softhsm.zip


	jakob



From jerry at opendnssec.org  Tue Dec 17 18:25:27 2013
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Tue, 17 Dec 2013 19:25:27 +0100
Subject: [Opendnssec-develop] Jenkins Git problems (Was: SoftHSM v1 now at
	git)
In-Reply-To: <72A9F5DF-1A89-41C5-943A-4145DFBA79D6@kirei.se>
References: <EE718640-73FB-4DF3-AA0F-7E4526B0AB66@kirei.se>
	<AFB3C5E3-42A5-494C-9FEA-CBA8630D0403@opendnssec.org>
	<838D669F-2C93-4BC6-9834-20021FBE5B44@opendnssec.org>
	<262C91BF-30B4-4119-B33D-9DAF1488E78C@opendnssec.org>
	<CEF7A4AF-ED05-49B5-B692-C64A5ABF2F11@opendnssec.org>
	<88536A1A-5423-4996-AB59-7EC42367295E@kirei.se>
	<1882175230223187270@unknownmsgid>
	<72A9F5DF-1A89-41C5-943A-4145DFBA79D6@kirei.se>
Message-ID: <5933919606754304847@unknownmsgid>

Not really, that would cause a rebuild on each job run since it wont know
what commit its getting and NO I do not want to scrape that info. We really
want a connection to the SCM.

There might be more options, need to check more tomorrow.

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

On 17 dec 2013, at 17:22, Jakob Schlyter <jakob at kirei.se> wrote:

On 17 dec 2013, at 16:50, Jerry Lundstr?m <jerry at opendnssec.org> wrote:

Already doing that, HTTP(S) URLs works with JGit.


I'm thinking we can skip JGit.

wget -o softhsm.zip
https://github.com/opendnssec/SoftHSMv1/archive/develop.zip
unzip softhsm.zip


   jakob
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131217/9412b0c8/attachment.htm>

From jerry at opendnssec.org  Wed Dec 18 08:32:49 2013
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Wed, 18 Dec 2013 09:32:49 +0100
Subject: [Opendnssec-develop] Jenkins Git problems (Was: SoftHSM v1 now at
	git)
In-Reply-To: <5933919606754304847@unknownmsgid>
References: <EE718640-73FB-4DF3-AA0F-7E4526B0AB66@kirei.se>
	<AFB3C5E3-42A5-494C-9FEA-CBA8630D0403@opendnssec.org>
	<838D669F-2C93-4BC6-9834-20021FBE5B44@opendnssec.org>
	<262C91BF-30B4-4119-B33D-9DAF1488E78C@opendnssec.org>
	<CEF7A4AF-ED05-49B5-B692-C64A5ABF2F11@opendnssec.org>
	<88536A1A-5423-4996-AB59-7EC42367295E@kirei.se>
	<1882175230223187270@unknownmsgid>
	<72A9F5DF-1A89-41C5-943A-4145DFBA79D6@kirei.se>
	<5933919606754304847@unknownmsgid>
Message-ID: <CAGTFMNZiefKq1L2kHRoVOFyU00J3DknGbqQpF6w0640L5YqwFA@mail.gmail.com>

On Tue, Dec 17, 2013 at 7:25 PM, Jerry Lundstr?m <jerry at opendnssec.org>wrote:

> There might be more options, need to check more tomorrow.
>

Progress, there was an option I didn't see yesterday.

"Wipe out repository & force clone", ugly but it worked to get changes at
least.

But sadly, now Polling SCM does not work correctly so it rebuilds every
check.

I'll keep working on it.
/Jerry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131218/047fa113/attachment.htm>

From jakob at kirei.se  Wed Dec 18 08:33:35 2013
From: jakob at kirei.se (Jakob Schlyter)
Date: Wed, 18 Dec 2013 09:33:35 +0100
Subject: [Opendnssec-develop] Jenkins Git problems (Was: SoftHSM v1 now at
	git)
In-Reply-To: <CAGTFMNZiefKq1L2kHRoVOFyU00J3DknGbqQpF6w0640L5YqwFA@mail.gmail.com>
References: <EE718640-73FB-4DF3-AA0F-7E4526B0AB66@kirei.se>
	<AFB3C5E3-42A5-494C-9FEA-CBA8630D0403@opendnssec.org>
	<838D669F-2C93-4BC6-9834-20021FBE5B44@opendnssec.org>
	<262C91BF-30B4-4119-B33D-9DAF1488E78C@opendnssec.org>
	<CEF7A4AF-ED05-49B5-B692-C64A5ABF2F11@opendnssec.org>
	<88536A1A-5423-4996-AB59-7EC42367295E@kirei.se>
	<1882175230223187270@unknownmsgid>
	<72A9F5DF-1A89-41C5-943A-4145DFBA79D6@kirei.se>
	<5933919606754304847@unknownmsgid>
	<CAGTFMNZiefKq1L2kHRoVOFyU00J3DknGbqQpF6w0640L5YqwFA@mail.gmail.com>
Message-ID: <7C034E07-0E36-4F03-965F-D0C1DDA2590C@kirei.se>

We could also try using the github subversion interface for checking out code;
https://github.com/blog/626-announcing-svn-support

	jakob



From jerry at opendnssec.org  Wed Dec 18 08:39:45 2013
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Wed, 18 Dec 2013 09:39:45 +0100
Subject: [Opendnssec-develop] Jenkins Git problems (Was: SoftHSM v1 now at
	git)
In-Reply-To: <7C034E07-0E36-4F03-965F-D0C1DDA2590C@kirei.se>
References: <EE718640-73FB-4DF3-AA0F-7E4526B0AB66@kirei.se>
	<AFB3C5E3-42A5-494C-9FEA-CBA8630D0403@opendnssec.org>
	<838D669F-2C93-4BC6-9834-20021FBE5B44@opendnssec.org>
	<262C91BF-30B4-4119-B33D-9DAF1488E78C@opendnssec.org>
	<CEF7A4AF-ED05-49B5-B692-C64A5ABF2F11@opendnssec.org>
	<88536A1A-5423-4996-AB59-7EC42367295E@kirei.se>
	<1882175230223187270@unknownmsgid>
	<72A9F5DF-1A89-41C5-943A-4145DFBA79D6@kirei.se>
	<5933919606754304847@unknownmsgid>
	<CAGTFMNZiefKq1L2kHRoVOFyU00J3DknGbqQpF6w0640L5YqwFA@mail.gmail.com>
	<7C034E07-0E36-4F03-965F-D0C1DDA2590C@kirei.se>
Message-ID: <CAGTFMNb-LjapNC99r5XOGvsnjqH6+WZy1rdVup0bh3RY9jopRg@mail.gmail.com>

On Wed, Dec 18, 2013 at 9:33 AM, Jakob Schlyter <jakob at kirei.se> wrote:

> We could also try using the github subversion interface for checking out
> code;
> https://github.com/blog/626-announcing-svn-support
>

Already tested, does not work. Mentioned it in a mail yesterday.

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131218/f978cedb/attachment.htm>

From jerry at opendnssec.org  Wed Dec 18 08:57:31 2013
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Wed, 18 Dec 2013 09:57:31 +0100
Subject: [Opendnssec-develop] Jenkins+Git working! (Was: Jenkins Git
	problems)
Message-ID: <CAGTFMNZLcBcRFHri56G_p3hD3gEM8AwVOq=26vR8FXrYt4xtGQ@mail.gmail.com>

Finally,

Git checkout with changes works and SCM is polled correctly and triggers
new builds on new commits.

There will be a small change in the testing framework.

Today the framework keeps a couple control files in the workspace directory
to keep track of what revision has been built and does not rebuild it if
its the same, this is to not waste resources when jobs are triggered in the
dependencies chains we have (softhsm -> ldns -> opendnssec -> test etc) if
no changes has been made.

These files where kept in workspace so if you want to force a rebuild of
the same commit you could wipe the workspace before triggering the build.

With the required "Wipe out repository & force clone" this is done every
run so these files need to be moved to the INSTALL_ROOT and we can replace
the "force a rebuild" functionality with a stand alone job that removes
those files if we need it (don't actually know if anyone has use it).

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131218/c0b12edf/attachment.htm>

From jerry at opendnssec.org  Wed Dec 18 10:50:45 2013
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Wed, 18 Dec 2013 11:50:45 +0100
Subject: [Opendnssec-develop] Changes to commit messages when moved to GitHub
Message-ID: <CAGTFMNY-bm8c7Jq0a8X=NtAG1Hdxj9TgG9yq2pdHF3vrT7HTJQ@mail.gmail.com>

Hi,

There will be a change to the commit messages as we move the projects to
GitHub.

GitHub has only implemented an email notification of the push and it is
without the change to the code (diff). You will easily see what repository,
commit tag, commit message it is for and a link to the commit on GitHub. So
there is only an extra step if you want to see the full diff.

This on the other hand won't be something important since we will be
working in user forked repositories and doing pull requests.

If people want notifications on pull requests (not made by themselves) or
anything else related to a repository you need to watch the repository on
GitHub.

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131218/57a33d23/attachment.htm>

From jerry at opendnssec.org  Wed Dec 18 11:16:32 2013
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Wed, 18 Dec 2013 12:16:32 +0100
Subject: [Opendnssec-develop] Repaired SoftHSMv1 Git master branch
Message-ID: <CAGTFMNbvF9Hd2hwpRi5JFPduJV0dgNZHoE5yVWN9LC0RQfo=tA@mail.gmail.com>

Hi,

Just FYI, I have forced pushed changes to the index for SoftHSMv1 to
rearrange the commit order for master and develop. This adds my testing
fixes before a commit that was made to trunk before the convert.

If you have clone SoftHSMv1 you WILL get errors! Best to do is to remove
the repository locally and clone it again. If you have made changes contact
me and I'll help you export them and the apply them again.

Also, since we convert tagging trunk as the master we did an error after
the convert was done. Trunk that becomes master needs to be renamed develop
and then you create a master based on the latest release.

Very good that this got noticed before we convert OpenDNSSEC since there
has been a lot more commit in that then in SoftHSM.

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131218/ddc8b5b2/attachment.htm>

From jerry at opendnssec.org  Wed Dec 18 11:21:47 2013
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Wed, 18 Dec 2013 12:21:47 +0100
Subject: [Opendnssec-develop] Re: Repaired SoftHSMv1 Git master branch
In-Reply-To: <CAGTFMNbvF9Hd2hwpRi5JFPduJV0dgNZHoE5yVWN9LC0RQfo=tA@mail.gmail.com>
References: <CAGTFMNbvF9Hd2hwpRi5JFPduJV0dgNZHoE5yVWN9LC0RQfo=tA@mail.gmail.com>
Message-ID: <CAGTFMNbKb1v7FM3mSMcpu7fDRqNH5wa7ZnnSgMVf6PCnWj3MuA@mail.gmail.com>

On Wed, Dec 18, 2013 at 12:16 PM, Jerry Lundstr?m <jerry at opendnssec.org>wrote:

>
> If you have clone SoftHSMv1 you WILL get errors! Best to do is to remove
> the repository locally and clone it again. If you have made changes contact
> me and I'll help you export them and the apply them again.
>

Small note, this only applies if you try and fetch updates from the
upstream. Since the index in the upstream has been rewritten then you will
get errors.

Does not apply on your user fork since they are not kept in sync with the
upstream.

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131218/a02ff30b/attachment.htm>

From jerry at opendnssec.org  Wed Dec 18 14:08:36 2013
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Wed, 18 Dec 2013 15:08:36 +0100
Subject: [Opendnssec-develop] How about removing [Opendnssec-commits] from
	commits emails?
Message-ID: <CAGTFMNYgmeeCX0Nh0jbM_ardqz9Vdri9B9g73E6fPg7L7m-Hqw@mail.gmail.com>

Hi all,

I'm proposing removing the tag from the mailing list, with GitHub we get
double tagged now.

I know people might be filtering on subject but there are other things to
filter on also, like List-Id: and From: .

We could also add [jenkins] for all the Jenkins stuff.

Whats your 2c?

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131218/57845884/attachment.htm>

From jakob at kirei.se  Wed Dec 18 14:09:47 2013
From: jakob at kirei.se (Jakob Schlyter)
Date: Wed, 18 Dec 2013 15:09:47 +0100
Subject: [Opendnssec-develop] How about removing [Opendnssec-commits] from
	commits emails?
In-Reply-To: <CAGTFMNYgmeeCX0Nh0jbM_ardqz9Vdri9B9g73E6fPg7L7m-Hqw@mail.gmail.com>
References: <CAGTFMNYgmeeCX0Nh0jbM_ardqz9Vdri9B9g73E6fPg7L7m-Hqw@mail.gmail.com>
Message-ID: <9FE41FB3-B021-40C0-AA1E-CF718DEFAE14@kirei.se>

On 18 dec 2013, at 15:08, Jerry Lundstr?m <jerry at opendnssec.org> wrote:

> Whats your 2c?

go for it.

	jakob



From matthijs at nlnetlabs.nl  Wed Dec 18 14:59:05 2013
From: matthijs at nlnetlabs.nl (Matthijs Mekking)
Date: Wed, 18 Dec 2013 15:59:05 +0100
Subject: [Opendnssec-develop] How about removing [Opendnssec-commits]
	from commits emails?
In-Reply-To: <CAGTFMNYgmeeCX0Nh0jbM_ardqz9Vdri9B9g73E6fPg7L7m-Hqw@mail.gmail.com>
References: <CAGTFMNYgmeeCX0Nh0jbM_ardqz9Vdri9B9g73E6fPg7L7m-Hqw@mail.gmail.com>
Message-ID: <52B1B839.3060402@nlnetlabs.nl>

On 12/18/2013 03:08 PM, Jerry Lundstr?m wrote:
> Hi all,
> 
> I'm proposing removing the tag from the mailing list, with GitHub we get
> double tagged now.
> 
> I know people might be filtering on subject but there are other things
> to filter on also, like List-Id: and From: .
> 
> We could also add [jenkins] for all the Jenkins stuff.
> 
> Whats your 2c?

Currently I filter commits and jenkins test outputs to different
directories. As long as I can differentiate between the two I am fine
with everything.

Best regards,
  Matthijs

> 
> -- 
> Jerry Lundstr?m - OpenDNSSEC Developer
> http://www.opendnssec.org/
> 
> 
> _______________________________________________
> Opendnssec-develop mailing list
> Opendnssec-develop at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop
> 



From sion at nominet.org.uk  Wed Dec 18 15:08:55 2013
From: sion at nominet.org.uk (=?ISO-8859-1?Q?Si=F4n_Lloyd?=)
Date: Wed, 18 Dec 2013 15:08:55 +0000
Subject: [Opendnssec-develop] How about removing [Opendnssec-commits]
	from commits emails?
In-Reply-To: <52B1B839.3060402@nlnetlabs.nl>
References: <CAGTFMNYgmeeCX0Nh0jbM_ardqz9Vdri9B9g73E6fPg7L7m-Hqw@mail.gmail.com>
	<52B1B839.3060402@nlnetlabs.nl>
Message-ID: <52B1BA87.9090401@nominet.org.uk>

On 18/12/13 14:59, Matthijs Mekking wrote:
> On 12/18/2013 03:08 PM, Jerry Lundstr?m wrote:
>> Hi all,
>>
>> I'm proposing removing the tag from the mailing list, with GitHub we get
>> double tagged now.
>>
>> I know people might be filtering on subject but there are other things
>> to filter on also, like List-Id: and From: .
>>
>> We could also add [jenkins] for all the Jenkins stuff.
>>
>> Whats your 2c?
> Currently I filter commits and jenkins test outputs to different
> directories. As long as I can differentiate between the two I am fine
> with everything.
>
>

I think a few of us will have to change our filters; but it should still
be possible. Unless anyone objects I'll make the change tomorrow.

Sion


From jerry at opendnssec.org  Wed Dec 18 16:22:18 2013
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Wed, 18 Dec 2013 17:22:18 +0100
Subject: [Opendnssec-develop] SoftHSM v1 now at git
In-Reply-To: <EE718640-73FB-4DF3-AA0F-7E4526B0AB66@kirei.se>
References: <EE718640-73FB-4DF3-AA0F-7E4526B0AB66@kirei.se>
Message-ID: <CAGTFMNZqfvnuLkXSrGcjJyVqvXQ0V5T6Ps5HsPV4CRgjsPpmEA@mail.gmail.com>

On Mon, Dec 16, 2013 at 8:08 AM, Jakob Schlyter <jakob at kirei.se> wrote:

> I've now moved SoftHSM v1 to git at
> https://github.com/opendnssec/SoftHSMv1.
>
> The subversion repository for SoftHSMv1 will stick around for a couple
> days more, please do NOT commit any code to this repository.
>

Jenkins is now successfully building build-softhsm-trunk from GitHub
SoftHSMv1 origin/develop on all platforms.

Tomorrow I will change the 1.3 and 1.4 branches to build from GitHub
SoftHSMv1 origin/master (which will contain the latest release version) and
me and Jakob is working on a pull request, testing the process and seeing
that everything works and is trigged when we accept a pull request.

When all of that has been done successfully the SVN repository for SoftHSM
v1 will be removed and replaced with a README like the others.

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131218/2d081075/attachment.htm>

From sion at nominet.org.uk  Thu Dec 19 10:45:45 2013
From: sion at nominet.org.uk (=?ISO-8859-1?Q?Si=F4n_Lloyd?=)
Date: Thu, 19 Dec 2013 10:45:45 +0000
Subject: [Opendnssec-develop] How about removing [Opendnssec-commits]
	from commits emails?
In-Reply-To: <52B1BA87.9090401@nominet.org.uk>
References: <CAGTFMNYgmeeCX0Nh0jbM_ardqz9Vdri9B9g73E6fPg7L7m-Hqw@mail.gmail.com>	<52B1B839.3060402@nlnetlabs.nl>
	<52B1BA87.9090401@nominet.org.uk>
Message-ID: <52B2CE59.2010808@nominet.org.uk>

On 18/12/13 15:08, Si?n Lloyd wrote:
> On 18/12/13 14:59, Matthijs Mekking wrote:
>> On 12/18/2013 03:08 PM, Jerry Lundstr?m wrote:
>>> Hi all,
>>>
>>> I'm proposing removing the tag from the mailing list, with GitHub we get
>>> double tagged now.
>>>
>>> I know people might be filtering on subject but there are other things
>>> to filter on also, like List-Id: and From: .
>>>
>>> We could also add [jenkins] for all the Jenkins stuff.
>>>
>>> Whats your 2c?
>> Currently I filter commits and jenkins test outputs to different
>> directories. As long as I can differentiate between the two I am fine
>> with everything.
>>
>>
> I think a few of us will have to change our filters; but it should still
> be possible. Unless anyone objects I'll make the change tomorrow.
>
> Sion

I've made that change now; we can always put it back if need be.


From jerry at opendnssec.org  Thu Dec 19 11:02:03 2013
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Thu, 19 Dec 2013 12:02:03 +0100
Subject: [Opendnssec-develop] SoftHSM v1 now at git
In-Reply-To: <CAGTFMNZqfvnuLkXSrGcjJyVqvXQ0V5T6Ps5HsPV4CRgjsPpmEA@mail.gmail.com>
References: <EE718640-73FB-4DF3-AA0F-7E4526B0AB66@kirei.se>
	<CAGTFMNZqfvnuLkXSrGcjJyVqvXQ0V5T6Ps5HsPV4CRgjsPpmEA@mail.gmail.com>
Message-ID: <080C8F1A-B16F-40C5-8D9B-B518ADCF39AB@opendnssec.org>

On Dec 18, 2013, at 17:22 , Jerry Lundstr?m wrote:

> Tomorrow I will change the 1.3 and 1.4 branches to build from GitHub
> SoftHSMv1 origin/master (which will contain the latest release version) and
> me and Jakob is working on a pull request, testing the process and seeing
> that everything works and is trigged when we accept a pull request.


All branches is building successfully on Jenkins from GitHub now.

We (me and Jakob) have been testing pull requests and the process is working and merging request are very easy when they are done and reviewed.

Therefor I have now removed trunk/softHSM from SVN.

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131219/a3a46c7b/attachment.bin>

From jerry at opendnssec.org  Thu Dec 19 14:12:28 2013
From: jerry at opendnssec.org (=?iso-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Thu, 19 Dec 2013 15:12:28 +0100
Subject: [Opendnssec-develop] Can we keep repositories on GitHub in
	lowercase?
Message-ID: <EB9DB4BB-DC10-4C41-A170-BFA0717346C0@opendnssec.org>

Hi,

I would like to suggest that we keep all repositories on GitHub in lowercase because that is the standard.

That would also mean a rename of SoftHSMv1 (to perhaps softhsm) and SoftHSMv2 (to perhaps softhsm2).

2c's?

--
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131219/0b991352/attachment.bin>

From sion at nominet.org.uk  Thu Dec 19 16:09:54 2013
From: sion at nominet.org.uk (=?ISO-8859-1?Q?Si=F4n_Lloyd?=)
Date: Thu, 19 Dec 2013 16:09:54 +0000
Subject: [Opendnssec-develop] Can we keep repositories on GitHub in
	lowercase?
In-Reply-To: <EB9DB4BB-DC10-4C41-A170-BFA0717346C0@opendnssec.org>
References: <EB9DB4BB-DC10-4C41-A170-BFA0717346C0@opendnssec.org>
Message-ID: <52B31A52.90702@nominet.org.uk>

On 19/12/13 14:12, Jerry Lundstr?m wrote:
> Hi,
>
> I would like to suggest that we keep all repositories on GitHub in lowercase because that is the standard.
>
> That would also mean a rename of SoftHSMv1 (to perhaps softhsm) and SoftHSMv2 (to perhaps softhsm2).
>
> 2c's?
>
>

I'd rather not change; I think that the mixed case versions are more
readable.

Also, if GitHub itself has a mixed case name I don't see why we shouldn't.

Sion


From jakob at kirei.se  Thu Dec 19 19:20:56 2013
From: jakob at kirei.se (Jakob Schlyter)
Date: Thu, 19 Dec 2013 20:20:56 +0100
Subject: [Opendnssec-develop] Can we keep repositories on GitHub in
	lowercase?
In-Reply-To: <52B31A52.90702@nominet.org.uk>
References: <EB9DB4BB-DC10-4C41-A170-BFA0717346C0@opendnssec.org>
	<52B31A52.90702@nominet.org.uk>
Message-ID: <4C79A7CE-A1A7-4475-92F2-56AE959E47D9@kirei.se>

On 19 dec 2013, at 17:09, Si?n Lloyd <sion at nominet.org.uk> wrote:

> I'd rather not change; I think that the mixed case versions are more
> readable.

+1

	jakob



From jerry at opendnssec.org  Fri Dec 20 08:24:52 2013
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Fri, 20 Dec 2013 09:24:52 +0100
Subject: [Opendnssec-develop] Git work process
Message-ID: <CAGTFMNZa6MySohyu-WYGbGkaRTSuunOb7NC++5Yacs4gQst8ew@mail.gmail.com>

Hi all,

Been documenting the work process in git, can you all review this please:

https://wiki.opendnssec.org/display/OpenDNSSEC/Git#Git-Dosomework

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131220/75f17d7a/attachment.htm>

From jerry at opendnssec.org  Fri Dec 20 10:30:02 2013
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Fri, 20 Dec 2013 11:30:02 +0100
Subject: [Opendnssec-develop] Re: Git work process
In-Reply-To: <CAGTFMNZa6MySohyu-WYGbGkaRTSuunOb7NC++5Yacs4gQst8ew@mail.gmail.com>
References: <CAGTFMNZa6MySohyu-WYGbGkaRTSuunOb7NC++5Yacs4gQst8ew@mail.gmail.com>
Message-ID: <CAGTFMNYMveo1aWhJZ2fD2Q1oWtzdK-YvjEUGeRFpF=b_ZAf9yg@mail.gmail.com>

Hi,

A few basic steps are now documented:
- Setup
- Do some work
- Update from upstream

Can people start testing this setup with the opendnssec-workflow-test
repository now and make pull requests that we can reject and merge etc?

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131220/0a0d3652/attachment.htm>

From sara at sinodun.com  Fri Dec 20 14:20:05 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Fri, 20 Dec 2013 14:20:05 +0000
Subject: [Opendnssec-develop] SoftHSM v1 now at git
In-Reply-To: <080C8F1A-B16F-40C5-8D9B-B518ADCF39AB@opendnssec.org>
References: <EE718640-73FB-4DF3-AA0F-7E4526B0AB66@kirei.se>
	<CAGTFMNZqfvnuLkXSrGcjJyVqvXQ0V5T6Ps5HsPV4CRgjsPpmEA@mail.gmail.com>
	<080C8F1A-B16F-40C5-8D9B-B518ADCF39AB@opendnssec.org>
Message-ID: <FC43BD27-F545-4390-B397-8E50BCAC3A28@sinodun.com>

> 
> All branches is building successfully on Jenkins from GitHub now.

This is great news - really well done!

Sara.


From sara at sinodun.com  Fri Dec 20 14:21:09 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Fri, 20 Dec 2013 14:21:09 +0000
Subject: [Opendnssec-develop] Git work process
In-Reply-To: <CAGTFMNZa6MySohyu-WYGbGkaRTSuunOb7NC++5Yacs4gQst8ew@mail.gmail.com>
References: <CAGTFMNZa6MySohyu-WYGbGkaRTSuunOb7NC++5Yacs4gQst8ew@mail.gmail.com>
Message-ID: <979C7624-A63D-403E-8BC1-4E977B064B34@sinodun.com>


On 20 Dec 2013, at 08:24, Jerry Lundstr?m <jerry at opendnssec.org> wrote:

> Hi all,
> 
> Been documenting the work process in git, can you all review this please:
> 
> https://wiki.opendnssec.org/display/OpenDNSSEC/Git#Git-Dosomework

This also looks great - thanks for all your effort in documenting this!

Some comments and questions:

- GitHub accounts. Am I right in thinking that the OpenDNSSEC account is an organisation (with just 3 members today)? So we should all request that our github accounts be added to the OpenDNSSEC organisation (i.e. send our usernames to Jerry)?

- (minor) in the setup section there is a note under the instructions for forking "You might the a option where the fork should be done, select yourself." I suppose this should be "You might get the option of where the fork should be done, select yourself"???

- (minor) need to add a step cd into your cloned dir after cloning and before checkout

- using git clone git at github.com:<your git username>/<repository name>.git assumes you have a SSH key set up on your account. I presume that we are recommending this but if I understand correctly it is possible to work without this (e.g. using http instead)?

- Jerry - could you please update the JIRA Fisheye config for SoftHSM?

- I have updated the wiki pages:

http://www.opendnssec.org/download/
https://wiki.opendnssec.org/display/SoftHSMDOCS/SoftHSM+Documentation+v1.3

To reflect that the code has moved for SoftHSMv1. A second pair of eyes to make sure I got this right would be appreciated! 

Sara. 

From jakob at kirei.se  Fri Dec 20 14:47:06 2013
From: jakob at kirei.se (Jakob Schlyter)
Date: Fri, 20 Dec 2013 15:47:06 +0100
Subject: [Opendnssec-develop] Git work process
In-Reply-To: <979C7624-A63D-403E-8BC1-4E977B064B34@sinodun.com>
References: <CAGTFMNZa6MySohyu-WYGbGkaRTSuunOb7NC++5Yacs4gQst8ew@mail.gmail.com>
	<979C7624-A63D-403E-8BC1-4E977B064B34@sinodun.com>
Message-ID: <E759E205-B371-414F-981F-D2EB501CB3E7@kirei.se>


> 20 dec 2013 kl. 15:21 skrev Sara Dickinson <sara at sinodun.com>:
> 
> - GitHub accounts. Am I right in thinking that the OpenDNSSEC account is an organisation (with just 3 members today)? So we should all request that our github accounts be added to the OpenDNSSEC organisation (i.e. send our usernames to Jerry)?

No, developers are not handled differently than any other persons - only release managers has push access to the main repos. 

> - using git clone git at github.com:<your git username>/<repository name>.git assumes you have a SSH key set up on your account. I presume that we are recommending this but if I understand correctly it is possible to work without this (e.g. using http instead)?

You can use HTTPS with password authentication. 

  Jakob

From sara at sinodun.com  Fri Dec 20 14:48:01 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Fri, 20 Dec 2013 14:48:01 +0000
Subject: [Opendnssec-develop] RE: Move to git
Message-ID: <4822620B-D990-41AD-A079-CDF908165361@sinodun.com>

Hi All, 

The email below is a draft of an announcement to the users list about the move to git? Comments? Anything I missed?

Sara.


---------------------------------------------------------------
Hi All, 

The OpenDNSSEC project is in the process of moving code development from subversion to git.  This is to facilitate better source code management, improve the way we can accept contributed code and to implement robust code review processes.  (Please note that we will not be using the GitHub issue tracker, we will continue to use JIRA: http://bugs.opendnssec.org/)

This email is to announce that both SoftHSMv1 and SoftHSMv2 have been migrated from subversion to git and are now hosted on GitHub:

https://github.com/opendnssec/SoftHSMv1
https://github.com/opendnssec/SoftHSMv2

Several other minor components have also been migrated - the full list is available here:

http://fisheye.opendnssec.org/browse/opendnssec/trunk/README.git?hb=true

We will be using a branching model based on the one described here:

http://nvie.com/posts/a-successful-git-branching-model/

And the workflow process is being documented here: 

https://wiki.opendnssec.org/display/OpenDNSSEC/Git

The OpenDNSSEC code will move to git sometime next year, we are in the process of agreeing the migration plan and exact timing. We will announce more details of this nearer the time. 

Please feel free to ask any questions related to this move on this list. 

Sara. 

From jakob at kirei.se  Fri Dec 20 15:04:29 2013
From: jakob at kirei.se (Jakob Schlyter)
Date: Fri, 20 Dec 2013 16:04:29 +0100
Subject: [Opendnssec-develop] Git work process
In-Reply-To: <979C7624-A63D-403E-8BC1-4E977B064B34@sinodun.com>
References: <CAGTFMNZa6MySohyu-WYGbGkaRTSuunOb7NC++5Yacs4gQst8ew@mail.gmail.com>
	<979C7624-A63D-403E-8BC1-4E977B064B34@sinodun.com>
Message-ID: <DB3239E6-AFCF-4F7E-86A5-2B3EA9BE931C@kirei.se>

On 20 dec 2013, at 15:21, Sara Dickinson <sara at sinodun.com> wrote:

> - Jerry - could you please update the JIRA Fisheye config for SoftHSM?

Fixed now.

	jakob



From sara at sinodun.com  Fri Dec 20 17:41:53 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Fri, 20 Dec 2013 17:41:53 +0000
Subject: [Opendnssec-develop] jenkins test job on trunk
In-Reply-To: <AD5532E3-CF93-4BF5-B0EC-13C999A709BD@sinodun.com>
References: <AD5532E3-CF93-4BF5-B0EC-13C999A709BD@sinodun.com>
Message-ID: <0B68C0CE-AD62-42B1-BEFE-4A3B4E2A3972@sinodun.com>

fyi - this job is running again now...

On 17 Dec 2013, at 14:11, Sara Dickinson <sara at sinodun.com> wrote:

> Hi All, 
> 
> fyi - I have just disabled the test-opendnssec-trunk job since it has been failing since the merge of the enforcer-ng branch last week. I haven?t had time to investigate why, I have just disabled it for now until I do?.
> 
> Sara._______________________________________________
> Opendnssec-develop mailing list
> Opendnssec-develop at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop



From sara at sinodun.com  Fri Dec 20 17:50:16 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Fri, 20 Dec 2013 17:50:16 +0000
Subject: [Opendnssec-develop] RE: Christmas leave
Message-ID: <265858A4-1345-404C-9C73-ACFE9D1D8CC5@sinodun.com>

Hi All, 

I am on holiday all next week but will be back on the office on Monday 30th December.

Happy Holidays everyone!

Sara. 

From jerry at opendnssec.org  Fri Dec 20 19:13:14 2013
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Fri, 20 Dec 2013 20:13:14 +0100
Subject: [Opendnssec-develop] RE: Christmas leave
In-Reply-To: <265858A4-1345-404C-9C73-ACFE9D1D8CC5@sinodun.com>
References: <265858A4-1345-404C-9C73-ACFE9D1D8CC5@sinodun.com>
Message-ID: <-2903080679104309864@unknownmsgid>

And I'm back 2/1 next year!

So happy everything to all dudes and dudettes!

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

On 20 dec 2013, at 18:49, Sara Dickinson <sara at sinodun.com> wrote:

Hi All,

I am on holiday all next week but will be back on the office on Monday 30th
December.

Happy Holidays everyone!

Sara. _______________________________________________
Opendnssec-develop mailing list
Opendnssec-develop at lists.opendnssec.org
https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131220/e12f2206/attachment.htm>

From matthijs at nlnetlabs.nl  Mon Dec 23 08:44:59 2013
From: matthijs at nlnetlabs.nl (Matthijs Mekking)
Date: Mon, 23 Dec 2013 09:44:59 +0100
Subject: [Opendnssec-develop] Git work process
In-Reply-To: <E759E205-B371-414F-981F-D2EB501CB3E7@kirei.se>
References: <CAGTFMNZa6MySohyu-WYGbGkaRTSuunOb7NC++5Yacs4gQst8ew@mail.gmail.com>	<979C7624-A63D-403E-8BC1-4E977B064B34@sinodun.com>
	<E759E205-B371-414F-981F-D2EB501CB3E7@kirei.se>
Message-ID: <52B7F80B.9000003@nlnetlabs.nl>

On 12/20/2013 03:47 PM, Jakob Schlyter wrote:
> 
>> 20 dec 2013 kl. 15:21 skrev Sara Dickinson <sara at sinodun.com>:
>>
>> - GitHub accounts. Am I right in thinking that the OpenDNSSEC account is an organisation (with just 3 members today)? So we should all request that our github accounts be added to the OpenDNSSEC organisation (i.e. send our usernames to Jerry)?
> 
> No, developers are not handled differently than any other persons - only release managers has push access to the main repos. 

During the workshop we agreed that core developers should be included in
the organisation, aka they can bypass the code review part and accept
their own changes in special scenarios.

Matthijs

> 
>> - using git clone git at github.com:<your git username>/<repository name>.git assumes you have a SSH key set up on your account. I presume that we are recommending this but if I understand correctly it is possible to work without this (e.g. using http instead)?
> 
> You can use HTTPS with password authentication. 
> 
>   Jakob_______________________________________________
> Opendnssec-develop mailing list
> Opendnssec-develop at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop
> 



From jakob at kirei.se  Mon Dec 23 09:20:46 2013
From: jakob at kirei.se (Jakob Schlyter)
Date: Mon, 23 Dec 2013 10:20:46 +0100
Subject: [Opendnssec-develop] Git work process
In-Reply-To: <52B7F80B.9000003@nlnetlabs.nl>
References: <CAGTFMNZa6MySohyu-WYGbGkaRTSuunOb7NC++5Yacs4gQst8ew@mail.gmail.com>	<979C7624-A63D-403E-8BC1-4E977B064B34@sinodun.com>
	<E759E205-B371-414F-981F-D2EB501CB3E7@kirei.se>
	<52B7F80B.9000003@nlnetlabs.nl>
Message-ID: <1D845C73-700C-4882-ADC9-8D8C66716690@kirei.se>

On 23 dec 2013, at 09:44, Matthijs Mekking <matthijs at nlnetlabs.nl> wrote:

> During the workshop we agreed that core developers should be included in
> the organisation, aka they can bypass the code review part and accept
> their own changes in special scenarios.

Ack, send all usernames to me and I'll start collecting them.

-- 
Jakob Schlyter
Kirei AB - www.kirei.se