Package Details: openvpn-update-resolv-conf-git r46.2485e9d-1

Git Clone URL: https://aur.archlinux.org/openvpn-update-resolv-conf-git.git (read-only, click to copy)
Package Base: openvpn-update-resolv-conf-git
Description: OpenVPN Update resolvconf
Upstream URL: https://github.com/alfredopalhares/openvpn-update-resolv-conf
Licenses: GPL
Conflicts: openvpn-update-resolv-conf
Provides: openvpn-update-resolv-conf
Submitter: mtreinish
Maintainer: buzo
Last Packager: buzo
Votes: 55
Popularity: 0.55
First Submitted: 2016-04-15 23:43 (UTC)
Last Updated: 2022-05-17 19:17 (UTC)

Pinned Comments

warmwaffles commented on 2017-11-15 15:07 (UTC)

I highly recommend you guys look at the README in the github repo which states: > However if you have systemd 229 or newer the better option is to use script from https://github.com/jonathanio/update-systemd-resolved which uses DBus calls instead of creating temporary *.network files. Which can be found here https://aur.archlinux.org/packages/openvpn-update-systemd-resolved/ Systemd is at 233 right now for me, so it is a much better option to use it instead.

Latest Comments

« First ‹ Previous 1 2 3

flamusdiu commented on 2016-04-21 16:49 (UTC)

@mtereinish: You need to add 'provides' and 'conflicts' for both this and openvpn-update-resolv-conf-git packages. It would allow people to use either package to satisfy the requirement.

mtreinish commented on 2016-04-15 23:48 (UTC)

Sorry for the delay, I was on vacation followed by some work travel and didn't get a chance to update it prior today. I've switched this package to be a fixed version per the pacaur bug and created a separate vcs package openvpn-update-resolv-conf-git which pulls it from git. I'll try to be more prompt on updating this package when someone marks it out-of-date. @Mertcan that's an issue with the script being packaged here. I suggest you file a bug or a pull request to the upstream git repo: https://github.com/masterkorp/openvpn-update-resolv-conf we can update this package once a fix has been applied.

Mertcan commented on 2016-04-11 19:05 (UTC) (edited on 2016-04-11 19:06 (UTC) by Mertcan)

###which: no resolvconf in ((null))### ################################ RESOLVCONF=$(which resolvconf) Change RESOLVCONF=$(type -p resolvconf) or find and replace resolvconf location

jugs commented on 2016-04-03 19:44 (UTC)

I've emailed the package maintainer, hopefully he replies otherwise we might have to wait for package orphan to take it over and get it working again...

Ptolom commented on 2016-01-28 22:03 (UTC)

The resolvconf issue is fixed now.

mtreinish commented on 2016-01-21 22:27 (UTC)

@weirddan455 That's a good call I'll push out a new revision of this to include it @Ptolom that sounds like a good suggestion but since this package just clones the script from github you should propose the change there. Feel free to push a pull request to: https://github.com/masterkorp/openvpn-update-resolv-conf After it's merged when you rebuild this package it will be applied @jpala hmm, I've never used pacaur before I'm gonna respin this with the missing makedepends, if it's still an issue with pacaur after that let me know and I'll investigate more deeply.

Ptolom commented on 2016-01-16 16:03 (UTC)

There is a bug in this script which causes DNS leaks. "resolvconf -a "${dev}.inet" retains the old nameservers in resolv.conf, leading to dns leaks. I suggest adding the -x flag (for exclusive) to resolvconf to only use the nameservers supplied by openvpn

weirddan455 commented on 2016-01-15 08:18 (UTC)

git should probably be added as a makedepend.

jpala commented on 2016-01-01 10:43 (UTC)

I had issues trying to install this package with pacaur. $ pacaur -Sy openvpn-update-resolv-conf This runs without error but the 'update-resolv-conf' script is not copied into /etc/openvpn and I can't see it anyware using find / -name update-resolv-conf. However, everything worked as expected when I simply downloaded the PKGBUILD and then built it with makepkg. $ makepkg $ makepkg -i Seeing as the PKGBUILD works fine with makepkg, I assume there is some error in the way pacaur is handling it but I'm not sure what it is.

« First ‹ Previous 1 2 3