From: Adam Van Ymeren <adam@vany.ca>
To: ludo@gnu.org
Cc: 28973@debbugs.gnu.org
Subject: [bug#28973] [PATCH 1/1] gnu: Add strongswan.
Date: Sun, 19 Nov 2017 18:20:13 -0500 [thread overview]
Message-ID: <DC27A8B2-DCDC-461B-96C5-8C60F23B9460@vany.ca> (raw)
In-Reply-To: <87k1ylzy6y.fsf@gnu.org>
On November 19, 2017 5:43:49 PM EST, ludo@gnu.org wrote:
>Hello!
>
>Adam Van Ymeren <adam@vany.ca> skribis:
>
>> Updated patch below.
>
>Tobias, should we go ahead and applied this updated patch? Feel free
>to
>do so if it looks good to you. :-)
>
>Thanks,
>Ludo’.
Hey Ludo,
I'm still not sure we've gotten all the licensing info correct. I particular if I recall correctly there is some 4 clause BSD code in the source package that the debian package apparently avoids compiling.
I've been hoping to make a detailed pass of this package so I can say with confidence that the code licenses are correct, but I've been short on time.
next prev parent reply other threads:[~2017-11-19 23:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 18:58 [bug#28973] [PATCH 1/1] gnu: Add strongswan Adam Van Ymeren
2017-10-24 20:05 ` [bug#28973] [PATCH] Add the patches necessary to build strongswan Adam Van Ymeren
2017-10-24 20:11 ` [bug#28973] [PATCH 1/1] gnu: Add strongswan Tobias Geerinckx-Rice
2017-10-24 23:08 ` Adam Van Ymeren
2017-11-19 22:43 ` Ludovic Courtès
2017-11-19 23:20 ` Adam Van Ymeren [this message]
2018-01-11 21:48 ` Ludovic Courtès
2018-01-12 17:15 ` Adam Van Ymeren
2018-01-13 13:52 ` Ludovic Courtès
2018-01-13 14:00 ` Tobias Geerinckx-Rice
2018-01-15 20:36 ` Adam Van Ymeren
2018-01-15 21:50 ` Tobias Geerinckx-Rice
2018-01-15 22:32 ` Adam Van Ymeren
2018-01-30 21:22 ` Ludovic Courtès
2018-01-31 19:46 ` Adam Van Ymeren
2018-01-31 22:33 ` bug#28973: " Ludovic Courtès
2017-10-24 20:13 ` [bug#28973] " Tobias Geerinckx-Rice
2018-01-23 20:43 ` [bug#28973] Updated: " Adam Van Ymeren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DC27A8B2-DCDC-461B-96C5-8C60F23B9460@vany.ca \
--to=adam@vany.ca \
--cc=28973@debbugs.gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).