Package Details: vpn-slice 0.15-1

Git Clone URL: (read-only, click to copy)
Package Base: vpn-slice
Description: vpnc-script replacement for easy and secure split-tunnel VPN setup
Upstream URL:
Licenses: GPL3
Submitter: akobel
Maintainer: akobel
Last Packager: akobel
Votes: 1
Popularity: 0.001340
First Submitted: 2018-09-06 14:42
Last Updated: 2020-11-25 18:34

Latest Comments

1 2 Next › Last »

akobel commented on 2020-05-31 11:38

@TecMunky Glad you got to a working state again by downgrading.

Concerning your issue with 0.14, please refrain from duplicating the information from the Github issue tracker here. There's always a risk that some crucial parts of the discussion are not propagated completely, and any functionality / feature / usability problems need to be addressed and resolved upstream. Other users that might be affected: please refer to


TecMunky commented on 2020-05-30 20:40

@akobel - thanks

reverting to 0.13 fixed my issues. I can run like this until I actually have time to troubleshoot the issue, or until it is fixed upstream.

I used pamac to ignore the vpn-slice package. This added an 'IgnorePkg' entry into pacman.conf (nice - i didn't know this would work like that).

For more information refer to

akobel commented on 2020-05-29 09:29


If version 0.11 worked for you, revert to that one unless you need a 0.13 feature. grep -C 3 vpn-slice /var/log/pacman.log should give you a hint what version you had installed before the package broke for you (look at the timestamps). Just do sudo pacman -U <path-to-0.11-pkg.tar....-in-pacaur-cache>.

makepkg only builds the package, no need no uninstall anything before doing so. It will not change anything on your system, unless you add -i. The -i (aka --install) just runs pacman after a successful build (i.e., it calls pacman -U <new-package>). This will show you what's going to happen and ask for confirmation as usual - e.g., it will ask whether you really want to downgrade vpn-slice from 0.14.1-1 to 0.11-1. Just try it.

Prohibit further updates: That's what the --ignore flag or the IgnorePkg entry in pacman.conf is about. Most pacman helpers respect it (pacaur certainly does). Not sure about pamac, but I assume it does acknowledge pacman.conf, at least. If you add the entry there, pacman will ask for explicit confirmation on any change of the ignored package, so unless you deliberately ignore the warnings, you should not get any nasty surprises.


TecMunky commented on 2020-05-29 05:42

@akobel: I do indeed know how to use git - thanks for the info.

I use pacaur. regarding the find command - it finds vpn-slice 0.11 in the pacaur cache, and vpn-slice 0.14.1 in the pacman cache.

I have not yet tried to makepkg the 0.13 build. I need to know if I should uninstall vpn-slice before I do that. Also, would I need to prohibit updates to vpn-slice until I know the upstream package has been fixed?

N.B. I use pamac to see what packages need to be updated, then switch to a TTY and use pacaur or pacman to implement updates (unless there are only a few and I know there will be no side effects).

akobel commented on 2020-05-28 07:54

Ugh. I just realise you might very well know how to use git. That makes life easier:

git clone
cd vpn-slice
git log --oneline
# shows that 11e5775 was the commit with the update to 0.13
git checkout 11e5775
makepkg -i

akobel commented on 2020-05-28 07:49

@TecMunky: Concerning downgrading, here's a summary. Indeed, that seems one of the less-lit places documentation-wise, at least I couldn't find a step-by-step walk-through within two minutes of searching. Not sure if that's bad or good given that AUR packages are really not supposed to be used without knowledge about reading and checking PKGBUILDs, and that typically comes with the necessary knowledge to dig out the previous version. No offense: we've all been there (or at least, I was, for sure).

First of all, check whether your package manager (I assume you use one?) keeps a cache. E.g., pikaur has its cache under ~/.cache/pikaur/pkg by default.

find ~/.cache /var/cache -type f -name 'vpn-slice-0.1*' 2>&-

If so, sudo pacman -U <path_to_cache_file>.

Otherwise, create some empty directory, download there and name it PKGBUILD, enter the directory and run makepkg -i. E.g., do:

cd $(mktemp -d);
curl -o PKGBUILD '';
makepkg -i;
rm -rf $(pwd -P) && cd

To got to 0.11-2, replace the URI by (and mind the quotes). To find those links, you can browse this page: "View Changes" in the top right box "Package Actions", then click on some commit and then "PKGBUILD" to see, well, the PKGBUILD instructions. Download the plain text (which I gave in the links above) to PKGBUILD or adjust manually to your needs, so that makepkg knows what to do.

Afterwards, run your next couple of upgrades with --ignore vpn-slice or add IgnorePkg = vpn-slice to /etc/pacman.conf until a fix is ready or you have more time to investigate.


TecMunky commented on 2020-05-28 00:26

@akobel - I don't really have the time to troubleshoot this right now, so I am living with having to use IPs for awhile. I don't know how to downgrade an AUR package - I googled it, but didn't find anything useful. If I had more time I could probably figure it out. I was hoping that bringing up the issue would lead to it getting corrected with another release.

If anyone out there knows how to fix this, please let me know.

If anyone can point me to a good write-up how to downgrade an AUR package, that could be useful too.

akobel commented on 2020-05-27 13:54

@TecMunky: Sorry to hear, but that'd better go upstream. Check if 0.14.1 improved the situation, or revert back to 0.13 for the time being... I solely maintain the Arch build, not the software itself; and unless it's a missing dependency or a build problem (or anything else Arch-specific that should be patched here rather than upstream), the Github issue tracker is the place to discuss any problem.

N.B.: My use case is pretty much gone, and so is my everyday "test" setup - no need or opportunity for VPN these days. I more or less react on pings here, but there's not a whole lot more I will/can do than a makepkg and sudo vpn-splice --self-test.

If there is an actual user who is interested to take over or co-maintain, let me know.

TecMunky commented on 2020-05-27 13:29

This latest update broke my ability to use computer names on the remote network. I now need to specify a computers IP address to access it.

ogasser commented on 2020-05-27 06:44

python-dnspython needs to be added as a dependency. Without python-dnspython I get the following error in the journal:

May 27 08:37:21 x network[6829]: pkg_resources.DistributionNotFound: The 'dnspython' distribution was not found and is required by vpn-slice
May 27 08:37:21 x network[6820]: Script 'vpn-slice x' returned error 1