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: 72
Popularity: 1.729021
First Submitted: 2013-03-13 17:16
Last Updated: 2018-06-15 02:58

Latest Comments

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.

smfsh commented on 2018-06-12 02:38

Thanks for the insight, dkosovic. I was gonna reach out to you on GitHub about the change but you beat me to it here. It makes sense to me about what you had to do. When you change the package back, I'll just push another build up, no worries.

Thanks for all you do for this package!

dkosovic commented on 2018-06-12 02:16 is preventing search engines from crawling because of the 'Disallow: /*/network' lines. So last night I reverted the repository name back to NetworkManager-l2tp after lots of complaints about not being able to find it with Google.

I submitted the new URL to search engines and was waiting for a googlebot to crawl and was thinking of reverting back after that to try and defeat the robots.txt file. GitHub has been doing the redirection between network-manager-l2tp and NetworkManager-l2tp since the inception of this repository (as mentioned it was originally called NetworkManager-l2tp), but unfortunately the top level directory in the generated tarballs is based on the current repository name. In hindsight I should probably create and upload tarballs rather than depend on generated ones.

Two days ago I submitted and because robot.txt file has 'Allow: /*/*/blob/master', the file now appears in google searches, but it wasn't an ideal solution.

Anyway, when I revert back to, it's going to break the latest changes to this AUR package.

smfsh commented on 2018-06-11 18:16

Fixed, but I'm not super happy with the solution as it was generically what squalou had said is what needed to happen. We can't change $pkgname directly because it would also change the name of the AUR package, and that's not easily done.

We can change $_pkgname, which we've used for a while to get around the fact that this package and upstream were named different, so we'll continue to do that.

Unfortunately, because of the upstream name change and the fact that they haven't actually published a new build, we can no longer use the asc file to automatically validate signatures. Hopefully all of this mess will go away on the next official package update upstream.

squalou commented on 2018-06-11 17:22

Additionally : package does not build anymore.

Error comes from what is inside the tarball : instead of containing sources in $pkgname-$version, they are in 'NetworkManager-l2tp'-$version

I suspect this change is also the reason why tarball checksum changed.

failed Rename attempt ? without a new version/revision ... sounds like bad practice.

You can manually edit the PKGBUILD and change $pkgname by NetworkManager-l2tp to fix the build .. but it's ugly.

bunder commented on 2018-06-11 17:02

Package fails with:

==> Validating source files with md5sums...
    network-manager-l2tp-1.2.10.tar.gz ... FAILED

Why has tarball checksum changed?

dkosovic commented on 2018-04-23 10:10 as previously mentioned in the comments below.

Execute the following command before trying to rebuild the package:

$ gpg --recv-keys 49A7787EF8D3C039

Or alternatevely read makepkg man page, specifically the --skippgpcheck section.

All comments