Arch Linux User Repository

@pidario: No worries, fully understood - didn't get you wrong here. I just realized that also the maintainer can unflag (not that surprising, really), and that I could have done it earlier when looking at the notification. Not sure if the original reporter can even do it. Anyway, case solved. :-)

@akobel Apologies if I sounded rude. I thought it was the user who (wrongfully) flagged the package that was meant to un-flag it. Anyway, thank you very much for both this and maintaining this package.

@pidario: Sorry, my bad - should have done that before.

@infinitezero: can you please unflag it as out-of-date? It's false: as you can see on PyPI (https://pypi.org/project/vpn-slice/) its last version is 0.16.1 (same as this package), and the git tag was created in December 2021. Besides you flagged it because it was broken (according to you) but, as other user mentioned, you just probably need to do a clean reinstall of the package. Not that I care, but every time I update, yay complains that vpn-slice is out-of-date. Really annoying.

@infinitezero: for me rebuilding the package solved the issue!

Getting the following error. I had to downgrade to python-3.10.10-1-x86_64 to get it to work again.

Traceback (most recent call last): File "/usr/lib/python3.11/importlib/metadata/init.py", line 563, in from_name return next(cls.discover(name=name)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ StopIteration

During handling of the above exception, another exception occurred:

Traceback (most recent call last): File "/usr/bin/vpn-slice", line 33, in <module> sys.exit(load_entry_point('vpn-slice==0.16.1', 'console_scripts', 'vpn-slice')()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/bin/vpn-slice", line 22, in importlib_load_entry_point for entry_point in distribution(dist_name).entry_points ^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/importlib/metadata/init.py", line 981, in distribution return Distribution.from_name(distribution_name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/importlib/metadata/init.py", line 565, in from_name raise PackageNotFoundError(name) importlib.metadata.PackageNotFoundError: No package metadata was found for vpn-slice Script 'vpn-slice xxx.xx.x.x/xx' returned error 1 Traceback (most recent call last): File "/usr/lib/python3.11/importlib/metadata/init.py", line 563, in from_name return next(cls.discover(name=name)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ StopIteration

During handling of the above exception, another exception occurred:

Traceback (most recent call last): File "/usr/bin/vpn-slice", line 33, in <module> sys.exit(load_entry_point('vpn-slice==0.16.1', 'console_scripts', 'vpn-slice')()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/bin/vpn-slice", line 22, in importlib_load_entry_point for entry_point in distribution(dist_name).entry_points ^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/importlib/metadata/init.py", line 981, in distribution return Distribution.from_name(distribution_name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/importlib/metadata/init.py", line 565, in from_name raise PackageNotFoundError(name) importlib.metadata.PackageNotFoundError: No package metadata was found for vpn-slice Script 'vpn-slice xxx.xx.x.x/xx' returned error 1

@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 https://github.com/dlenski/vpn-slice/issues/53.

Thanks.

@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 https://github.com/dlenski/vpn-slice/issues/53

@TecMunky:

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.

HTH.