Github messages for voidlinux
 help / color / mirror / Atom feed
From: dkosovic <dkosovic@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: NetworkManager-l2tp
Date: Sun, 05 Jul 2020 03:52:53 +0200	[thread overview]
Message-ID: <20200705015253.Wgq9fzMaOmVeLL6YEmzUkhoR68f4TVQ5CZAzgaVUilg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22610@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 2930 bytes --]

New comment by dkosovic on void-packages repository

https://github.com/void-linux/void-packages/issues/22610#issuecomment-653831687

Comment:
Here is a NetworkManager-l2tp 1.8.2 package template file, if someone wants to change the maintainer field and submit it, be my guest:

```bash
# Template file for 'NetworkManager-l2tp'
pkgname=NetworkManager-l2tp
version=1.8.2
revision=1
build_style=gnu-configure
configure_args="--runstatedir=/run"
hostmakedepends="pkg-config intltool glib-devel"
makedepends="gtk+3-devel libglib-devel libsecret-devel network-manager-applet-devel
libressl-devel nss-devel ppp-devel"
depends="strongswan xl2tpd ppp"
short_desc="NetworkManager VPN plugin for L2TP/IPsec"
maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-2.0-or-later"
homepage="https://github.com/nm-l2tp/NetworkManager-l2tp"
distfiles="https://github.com/nm-l2tp/NetworkManager-l2tp/releases/download/${version}/${pkgname}-${version}.tar.xz"
checksum=1d80986dc88951e298446833d314bab7af0a933e736960d6b3b025e6b7faca94

do_configure() {
	PPP_VERSION=`sed -n 's/^\#define\s*VERSION\s*"\([^\s]*\)"$/\1/p' /usr/include/pppd/patchlevel.h`

	./configure ${configure_args} --with-pppd-plugin-dir=/usr/lib/pppd/${PPP_VERSION}
}
```

If you want to build a NetworkManager-l2tp 1.8.2 binary package now, here is a summary of how to based on the building packages instructions from :
* https://github.com/void-linux/void-packages/blob/master/README.md

Ensure that `git`, the [requirements](Requirements) from that page as well at least one of the chroot based utilities required by `xbps-src` are installed.

Clone the void-packages git repository, install the bootstrap packages and create the NetworkManager-l2tp source package directory
```
git clone git://github.com/void-linux/void-packages.git
cd void-packages
./xbps-src binary-bootstrap
```

Use a text editor to create the `srcpkgs/NetworkManager-l2tp/template` file which has the contents from the template file at the start of this message.

Build the package with:
```
./xbps-src pkg NetworkManager-l2tp
```

Once built, install the package and run time dependencies with
```
sudo xbps-install --repository=hostdir/binpkgs NetworkManager-l2tp
sudo xbps-install -S strongswan xl2tpd ppp
```

For desktop environments to fully pickup that the NetworkManager-l2tp plugins were installed, logout and re-login to the desktop environment.

For NetworkManager-l2tp  debugging which increases the pppd logging, issue:
```
sudo killall -TERM nm-l2tp-service
sudo /usr/libexec/nm-l2tp-service --debug
```
Then bring up the VPN connection in the GUI desktop environment. Not all `nm-l2tp-service --debug` logging goes to the screen, the pppd logging uses syslog and where it goes depends on which syslog daemon you are using, if for example you are using socklog, the logging would go to `/var/log/socklog/messages/current`



       reply	other threads:[~2020-07-05  1:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22610@inbox.vuxu.org>
2020-07-05  1:52 ` dkosovic [this message]
2020-07-05  2:01 ` dkosovic
2020-07-05  2:04 ` dkosovic
2020-07-05  3:07 ` ericonr
2020-07-05  3:46 ` dkosovic
2020-07-05  4:36 ` ericonr
2020-07-09 13:58 ` benn13
2020-07-09 20:46 ` dkosovic
2020-07-09 20:49 ` dkosovic
2020-07-23 13:48 ` sgn

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200705015253.Wgq9fzMaOmVeLL6YEmzUkhoR68f4TVQ5CZAzgaVUilg@z \
    --to=dkosovic@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).