Package Details: networkmanager-l2tp 1.2.10-3

Git Clone URL: (read-only)
Package Base: networkmanager-l2tp
Description: L2TP support for NetworkManager
Upstream URL:
Licenses: GPL2
Submitter: bradpitcher
Maintainer: smfsh
Last Packager: smfsh
Votes: 73
Popularity: 1.013045
First Submitted: 2013-03-13 17:16
Last Updated: 2018-06-15 02:58

Latest Comments

1 2 3 4 5 6 ... Next › Last »

pastleo commented on 2018-08-09 04:37

I deleted the following lines...


const GPtrArray *nm_device_ovs_port_get_slaves (NMDeviceOvsPort *device);


const GPtrArray *nm_device_ovs_bridge_get_slaves (NMDeviceOvsBridge *device);

and it worked...but I don't know why

ryuzy commented on 2018-07-30 14:15

@dkosovic It is NM_AVAILABLE_IN_1_12_2 in the 1.12.2 branch

dkosovic commented on 2018-07-29 09:57

Not sure why Arch Linux has NM_AVAILABLE_IN_1_12_2 that is causing the issues in libnm/nm-device-ovs-port.h , in the github repository for that file :

it has :

const GPtrArray *nm_device_ovs_port_get_slaves (NMDeviceOvsPort *device);

and don't see any previous commits where it was using NM_AVAILABLE_IN_1_12_2, so I guess someone should submit a bug report for the broken header in the Arch networkmanager-1.12.2-1 package.

For the PGP signature, I've previously sent the key to, and the keyservers for Debian and Fedora. So I'm not sure what is going on. The following confirms 49A7787EF8D3C0390 public key is on :

taylorventuresll commented on 2018-07-27 18:35

Got 3 errors: network-manager-l2tp-1.2.10.tar.gz ... FAILED (unknown public key 49A7787EF8D3C039) ==> ERROR: One or more PGP signatures could not be verified!

/usr/include/libnm/nm-device-ovs-port.h:45:1: error: macro "G_UNAVAILABLE" passed 3 arguments, but takes just 2 NM_AVAILABLE_IN_1_12_2 ^~~~~~~~~~~~~~~~~~~~~~ /usr/include/libnm/nm-device-ovs-port.h:46:1: error: expected ‘;’ before ‘const’ const GPtrArray nm_device_ovs_port_get_slaves (NMDeviceOvsPort device); ^~~~~ In file included from /usr/include/libnm/NetworkManager.h:47, from ./shared/nm-default.h:103, from shared/nm-utils/nm-vpn-plugin-utils.c:22: /usr/include/libnm/nm-device-ovs-bridge.h:45:1: error: macro "G_UNAVAILABLE" passed 3 arguments, but takes just 2 NM_AVAILABLE_IN_1_12_2 ^~~~~~~~~~~~~~~~~~~~~~ /usr/include/libnm/nm-device-ovs-bridge.h:46:1: error: expected ‘;’ before ‘const’ const GPtrArray nm_device_ovs_bridge_get_slaves (NMDeviceOvsBridge device); ^~~~~

Hspak commented on 2018-07-07 21:36

So appears down at the moment and I can't find the public key on other key servers.

As a workaround, you can always pass '--skippgpcheck', but of course, it's not recommended. ;)

Spheerys commented on 2018-06-27 11:57

I can't verify the signature :

gpg --verify network-manager-l2tp-1.2.10.tar.gz.asc                                           
gpg: les données signées sont supposées être dans « network-manager-l2tp-1.2.10.tar.gz »
gpg: Signature faite le dim. 18 mars 2018 04:04:06 CET
gpg:                avec la clef RSA 49A7787EF8D3C039
gpg: demande de la clef 49A7787EF8D3C039 sur le serveur hkp
gpg: Impossible de vérifier la signature : Pas de clef publique

So in english : no public key... is the problem comes from or elsewhere ?

dkosovic commented on 2018-06-14 11:00

I can confirm the upstream source file has been changed back to network-manager-l2tp and old/current .asc file is able to verify the tarball. I had to revert it back as it was also impacting other Linux distributions. So this AUR package will also need to be modified. Sorry for the inconvenience.

I confirmed the the .asc file is okay with the below (unfortunately this site's markdown is putting the spurious < and > in the code block below)

$ wget <> 
$ wget <>

$ gpg --verify network-manager-l2tp-1.2.10.tar.gz.asc
gpg: assuming signed data in 'network-manager-l2tp-1.2.10.tar.gz'
gpg: Signature made Sun 18 Mar 2018 13:04:06 AEST
gpg:                using RSA key 49A7787EF8D3C039
gpg: Good signature from "Douglas Kosovic <>" [ultimate]

alexanderp commented on 2018-06-14 07:39

==> Validating source files with md5sums... NetworkManager-l2tp-1.2.10.tar.gz ... FAILED ==> ERROR: One or more files did not pass the validity check!

dkosovic commented on 2018-06-12 06:34

Sorry for the inconvenience.

I've renamed it back to , unfortunately it didn't get crawled by a googlebot.

I'll rename it back to once I release the next version which I'll upload both the .asc file and tarball, thus removing dependencies on GitHub's autogenerated tarballs.

@grazzolini the .asc file is something I upload to GitHub, it's not automatically generated, so wouldn't have been valid for the period when the GitHub repository had a name change and the on the fly generated tarballs would have been different.

grazzolini commented on 2018-06-12 04:57


I get that the package source has changed, but, you can still verify the source using gpg, by explicitly setting the full source for the asc file. No need to downgrade the PKGBUILD security.