Arch Linux User Repository

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

I get this during build. Any ideas as to why and how to fixit?

. . .
Parsing documentation for pleaserun-0.0.32
Installing ri documentation for pleaserun-0.0.32
Parsing documentation for rchardet-1.8.0
Installing ri documentation for rchardet-1.8.0
Parsing documentation for git-1.11.0
Installing ri documentation for git-1.11.0
Parsing documentation for backports-3.23.0
Installing ri documentation for backports-3.23.0
Parsing documentation for arr-pm-0.0.11
Installing ri documentation for arr-pm-0.0.11
Parsing documentation for fpm-1.14.2
Installing ri documentation for fpm-1.14.2
Done installing documentation for stud, mustache, insist, dotenv, clamp, cabin, pleaserun, rchardet, git, backports, arr-pm, fpm after 3 seconds
12 gems installed
patching file /home/sv-cheats-1/.cache/yay/windscribe-git/src/desktop-v2/tools/deps/install_qt.py
patching file /home/sv-cheats-1/.cache/yay/windscribe-git/src/desktop-v2/tools/build_all.py
Hunk #1 FAILED at 669.
1 out of 1 hunk FAILED -- saving rejects to file /home/sv-cheats-1/.cache/yay/windscribe-git/src/desktop-v2/tools/build_all.py.rej
==> ERROR: A failure occurred in prepare().
    Aborting...
 -> error making: windscribe-git

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 get-pip.py if you want pip2 in your system path (which you do, otherwise this package still won't install unless you heavily edit the PKGBUILD).

[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.

BUILDDIR=/tmp/makepkg

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.

@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.

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

@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.

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.

https://pastebin.com/LdJsudju

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

@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 https://aur.archlinux.org/packags/windscribe-git && 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
usr/local/windscribe/windscribewireguard
usr/local/windscribe/windscribestunnel
usr/local/windscribe/windscribeopenvpn
usr/local/windscribe/lib/libcrypto.so.1.1
usr/local/windscribe/lib/libQt5Core.so.5
usr/local/windscribe/helper
==> 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)

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

@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.