Package Details: windscribe-git 2.3.15_beta-1

Git Clone URL: (read-only, click to copy)
Package Base: windscribe-git
Description: Windscribe's GUI desktop client
Upstream URL:
Licenses: GPL2
Provides: windscribe
Submitter: Topik
Maintainer: Topik
Last Packager: Topik
Votes: 2
Popularity: 0.068674
First Submitted: 2021-11-22 17:50 (UTC)
Last Updated: 2021-12-23 23:04 (UTC)

Pinned Comments

Topik commented on 2021-12-24 04:54 (UTC)

PSA: An official and supported binary version will be released with version 2.4 in January 2022.

Latest Comments

gardotd426 commented on 2021-12-24 15:04 (UTC)

When something is commented out like that it's because its usually the default. You have a BUILDDIR somewhere, but anyway just uncomment it out because you need to know where it is.

Then all you have to do is go to your builddir/makepkg/windscribe-git/src/desktop-v2/tools/bin/ and run sudo python2 if you want pip2 in your system path (which you do, otherwise this package still won't install unless you heavily edit the PKGBUILD).

redkurn commented on 2021-12-24 05:53 (UTC) (edited on 2021-12-24 05:54 (UTC) by redkurn)

[x@Overlord ~]$ sudo pip2 install glob2 && sudo pip3 install glob2 [sudo] password for x: sudo: pip2: command not found

In the config it is commented out

-- Specify a directory for package building.

Also folder isn't there.

Can't install python2-pip even from aur.

@Topik I'm not exactly sure where I should be making this symlink.

I'll just wait until next month, terminal works fine.

gardotd426 commented on 2021-12-24 05:04 (UTC)

@Topik they shouldn't have to move anything.

It builds fine as-is.

But what I would suggest, @redkurn, is pasting the output of both pip2 list and pip list

you don't have the glob2 module installed, I do agree with Topik that it seems like the build process moves between Python 2 and Python 3, which is insane, but all you need to do is make sure glob2 is installed in both.

Just run sudo pip2 install glob2 && sudo pip3 install glob2

Then delete your builddir and try again.

When I say builddir, I don't mean your yay cache, I mean your makepkg builddir. If you haven't edited /etc/makepkg.conf then it's /tmp/makepkg. So remove /tmp/makepkg/windscribe-git, then try again after making sure glob2 is in both your pip2 and pip3 lists.

Topik commented on 2021-12-24 04:54 (UTC)

PSA: An official and supported binary version will be released with version 2.4 in January 2022.

Topik commented on 2021-12-24 04:53 (UTC)

@redkurn Seems like it may be switching back to Python 3. Try adding the python 2 symlink bit (lines 34-39) to the beginning of build() to see if that helps. Try running python --version in build() as well to make sure that Python 2.7 is running.

redkurn commented on 2021-12-24 03:24 (UTC) (edited on 2021-12-24 03:26 (UTC) by redkurn)

I'm using the defaults, never got into changing where things happen in the 16 years I've dabbled with linux. Getting the idea back in my head to convert again fully (as much as I can) again.

Output of the failed install, deleted the windscribe-git folder in .cache/yay with su, rm -rf.

This is the only package having an issue, I've installed a few others in the mean time.

gardotd426 commented on 2021-12-24 01:29 (UTC)

@redkurn you probably need to clear your yay cache. I'm rebuilding (for the 3rd time today) windscribe in a fresh builddir and all patches applied cleanly. My system is up-to-date).

The patches not applying cleanly isn't an issue with the package, it's something to do with your yay cache (which can cause issues).

And 5 minutes after starting, the build is finished successfully yet again.

Just to give a rundown of my setup, I have a tmpfs mounted at ~/tmp (alongside the default /tmp), and that's my BUILDDIR set in /etc/makepkg.conf. So all AUR packages get built in ~/tmp/makepkg/<pkgname>. And yay clones the repos in ~/tmp/pkgname.

So I run yay -S windscribe-git, it clones the AUR package repo in ~/tmp/windscribe-git, then starts building in ~/tmp/makepkg/windscribe-git.

So obviously every reboot, that all gets deleted. Which is how I want it. But anyway, on a fresh boot, I just ran cd ~/tmp && git clone && cd windscribe-git, followed by makepkg -s

And here we go:

All done: 1 minutes 14 seconds elapsed
==> Entering fakeroot environment...
==> Starting package()...
x - debian-binary
x - control.tar.xz
x - data.tar.xz
==> Tidying install...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Stripping unneeded symbols from binaries and libraries...
  -> Compressing man and info pages...
==> Checking for packaging issues...
==> WARNING: Package contains reference to $srcdir
==> Creating package "windscribe-git"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Adding install file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: windscribe-git 2.3.15_beta-1 (Thu 23 Dec 2021 08:25:00 PM EST)

redkurn commented on 2021-12-23 23:09 (UTC)

Awesome, it would be nice moving from shortcuts and CLI to a nice GUI that I am used to from windows.

Topik commented on 2021-12-23 22:49 (UTC)

@redkurn It seems like there has been an update to the git, which likely caused an issue with the patch. I'm compiling an updated version right now and will update the package soon. Plus, it seems like there are finally official binaries, so I'm also working on a package for that right now.

redkurn commented on 2021-12-23 22:35 (UTC) (edited on 2021-12-23 22:41 (UTC) by redkurn)

This is the contents,

Topik commented on 2021-12-23 21:30 (UTC)

@redkurn Seems like the sourcechanges patch is failing. Can you send /home/x/.cache/yay/windscribe-git/src/desktop-v2/tools/deps/custom_qt/source_changes.json.rej ? Check out line 197 of what you sent.

redkurn commented on 2021-12-23 20:26 (UTC)

gone in a week.

Topik commented on 2021-12-23 07:15 (UTC)

@redkurn Could you please upload the full output?

redkurn commented on 2021-12-23 07:12 (UTC)

I get as far as this...

(27/27) removing python-msgpack [----------------------] 100% :: Running post-transaction hooks... (1/4) Arming ConditionNeedsUpdate... (2/4) Updating the MIME type database... (3/4) Updating icon theme caches... (4/4) Updating the desktop file MIME type cache... -> error making: windscribe-git

Then it fails.

Topik commented on 2021-12-23 06:16 (UTC)

@gardotd426 Thank you for your suggestions. I updated the package as per your fixes and it seems to work fine now.

gardotd426 commented on 2021-12-23 03:24 (UTC) (edited on 2021-12-23 03:31 (UTC) by gardotd426)

@encrypt3d @Topik

If it's irreparably broken, then how is this a thing:

@encrypt3d you have to install the correct message package, I can't recall if its python3 or python2's version, but when I figure it out I'll post here. But it 100% works, as shown in the screenshot. And yes, it connects and works as intended.

Also you now have to patch the vars/stunnel.yml file to change the version to 5.61 from 5.60 because 5.60 has been replaced.

But I built it back when I commented earlier, successfully, and it ran perfectly fine, then after seeing these comments, I went at it again, it was a bit more of a PITA this time, but I still did it. Proof in screenshot.

Also one of the problems I initially exposed in the PKGBUILD a few weeks ago has been fixed, but the other hasn't. You have to export your path. Not just PATH=. You have to export it.

So I have message installed with pip2, and messages (with an s) installed with pip3. I couldn't get it to build without both. But you have to patch the stunnel.yml either before building with a traditional patch, or during building before the build process makes it to stunnel. You just edit vars/stunnel.yml and change it to 5.61 from 5.60. That's it.

If the build fails, you have to remove BUILDDIR/makepkg/windscribe-git and try again. I found that out the hard way. But I have now successfully built and installed (and ran, and used) this package, weeks apart.

Topik commented on 2021-12-22 20:20 (UTC)

The build process is broken for now and I am unable to find a solution. According to a comment by a Windscribe dev on a Github issue, the Python 2 dependency is set to be replaced with Python 3, so hopefully that will resolve the issue. This package will be updated as soon as that fix is released.

encrypt3d commented on 2021-12-15 00:49 (UTC)

Package is indeed broken. gardotd426's patches get it a bit further along, but it's missing messages. Adding python -m pip install messages after it installs from requirements.txt just results in a big error in pip.

internetuser commented on 2021-12-01 03:12 (UTC)

File "/home/user/tmp/windscribe-git/src/desktop-v2/tools/base/", line 15, in <module> import messages as msg ModuleNotFoundError: No module named 'messages' ==> ERROR: A failure occurred in build(). Aborting...

Seems I don't have the messages package installed, although it isn't in requirements.txt. Not sure whats going on here. Conflict with python2/3? Can anyone help

gardotd426 commented on 2021-11-23 00:36 (UTC)

I've gone ahead and taken the liberty of fixing this PKGBUILD, as it's not really functional right now.

First of all, you're not exporting your PATH stuff, so it tries to use the user's /usr/bin/python when you run python within the PKGBUILD. It basically makes your symlinking useless.


    if [ ! -d "${srcdir}"/py2 ]; then
        mkdir "${srcdir}"/py2
        ln -s /usr/bin/python2 "${srcdir}"/py2/python

needs to be:

    if [ ! -d "${srcdir}"/py2 ]; then
        mkdir "${srcdir}"/py2
        export PATH="${srcdir}"/py2:$PATH
        ln -s /usr/bin/python2 "${srcdir}"/py2/python

Second, you get "install_openssl": file not found errors, since you don't cd into the proper directory in the build() function.


build() {
    # Need to figure out how to detect if certain modules were already made so that a re-compilation isn't needed

Needs to be this:

build() {
    # Need to figure out how to detect if certain modules were already made so that a re-compilation isn't needed
    cd $srcdir/desktop-v2/tools/deps

With those changes I've successfully built, installed, and ran the Windscribe GUI.

FabioLolix commented on 2021-11-22 19:47 (UTC)

Hello, this need conflicts=('windscribe') instead of windscribe-bin and a pkgver function

Writing (git release) in pkgdesc not needed