Package Details: windscribe-git 2.3.15_beta-1

Git Clone URL: https://aur.archlinux.org/windscribe-git.git (read-only, click to copy)
Package Base: windscribe-git
Description: Windscribe's GUI desktop client
Upstream URL: https://github.com/Windscribe/desktop-v2
Licenses: GPL2
Provides: windscribe
Submitter: Topik
Maintainer: None
Last Packager: syntheit
Votes: 4
Popularity: 0.000018
First Submitted: 2021-11-22 17:50 (UTC)
Last Updated: 2022-08-17 22:00 (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

« First ‹ Previous 1 2 3 Next › Last »

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

This is the contents, https://pastebin.com/Dabc2UkK

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. https://pastebin.com/VRcHrVW5

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:

https://i.imgur.com/Z61RFwd.png

@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/utils.py", 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

« First ‹ Previous 1 2 3 Next › Last »