Package Details: cloudflare-warp-bin 2023.10.120-1

Git Clone URL: https://aur.archlinux.org/cloudflare-warp-bin.git (read-only, click to copy)
Package Base: cloudflare-warp-bin
Description: Cloudflare Warp Client
Upstream URL: https://1.1.1.1
Licenses: unknown
Conflicts: cloudflare-warp
Provides: warp-cli, warp-diag, warp-svc
Submitter: solatis
Maintainer: solatis (unlogicalcode, nomaxx117)
Last Packager: nomaxx117
Votes: 44
Popularity: 1.30
First Submitted: 2021-05-26 08:59 (UTC)
Last Updated: 2023-10-25 22:19 (UTC)

Latest Comments

1 2 3 4 5 6 .. 13 Next › Last »

nomaxx117 commented on 2023-10-25 22:24 (UTC)

I've pushed out a new release with an updated version. I don't have time right now to fix the root cause of the checksums breaking when new versions come out, but hopefully I can get to that later.

If anyone would like to submit a patch with a fix for this before I get to this, please feel free to do so.

behrad commented on 2023-10-25 10:16 (UTC) (edited on 2023-10-25 10:24 (UTC) by behrad)

Hi, I get this error:

==> Making package: cloudflare-warp-bin 2023.9.301-1 (Wed Oct 25 13:43:10 2023)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found cloudflare-warp-bin-2023.9.301-x86_64.deb
  -> Found cloudflare-warp-bin-2023.9.301-1-Release
  -> Found cloudflare-warp-bin-2023.9.301-1-x86_64-Packages
==> Validating source files with md5sums...
    cloudflare-warp-bin-2023.9.301-x86_64.deb ... Passed
    cloudflare-warp-bin-2023.9.301-1-Release ... Skipped
    cloudflare-warp-bin-2023.9.301-1-x86_64-Packages ... Skipped
==> Validating source files with sha256sums...
    cloudflare-warp-bin-2023.9.301-x86_64.deb ... Passed
    cloudflare-warp-bin-2023.9.301-1-Release ... Skipped
    cloudflare-warp-bin-2023.9.301-1-x86_64-Packages ... Skipped
==> Extracting sources...
  -> Extracting cloudflare-warp-bin-2023.9.301-x86_64.deb with bsdtar
==> Starting prepare()...
==> Removing existing $pkgdir/ directory...
==> Starting build()...
==> Starting check()...
==> Validating package checksums
==> sha256sum: /home/behrad/.cache/yay/cloudflare-warp-bin/src/cloudflare-warp-bin-2023.9.301-1-x86_64-Packages.sha256
==> sha256sum: /home/behrad/.cache/yay/cloudflare-warp-bin/src/cloudflare-warp-bin-2023.9.301-x86_64.deb.sha256
sha256sum: /home/behrad/.cache/yay/cloudflare-warp-bin/src/cloudflare-warp-bin-2023.9.301-x86_64.deb.sha256: no properly formatted checksum lines found
!!> SHA256 mismatch: /home/behrad/.cache/yay/cloudflare-warp-bin/src/cloudflare-warp-bin-2023.9.301-x86_64.deb.sha256

when I look the cloudflare-warp-bin-2023.9.301-x86_64.deb.sha256 file there is no hash in there an only the file name:

cloudflare-warp-bin-2023.9.301-x86_64.deb

but for example this is the output of cloudflare-warp-bin-2023.9.301-1-x86_64-Packages.sha256:

8c4729b1c0829eb438ae33478714fe4a45d9d8b311a4fb07d8406302304f08fc cloudflare-warp-bin-2023.9.301-1-x86_64-Packages

UPDATE: the problem should be in line 84 of PKGBUILD when grabing the sha256 of .deb file.

ojasbhagavath commented on 2023-10-02 06:45 (UTC)

Unable to install due to SHA256 mismatch error. :(

mathix commented on 2023-08-09 09:07 (UTC) (edited on 2023-08-09 09:08 (UTC) by mathix)

Another workaround is to stop (or mask) systemd-resolved after warp-svc is running.

At some point this workaround worked for me, but not since last updates.

The /etc/nsswitch.conf change did not work for me neither.

kinifwyne commented on 2023-08-06 05:05 (UTC) (edited on 2023-08-06 05:10 (UTC) by kinifwyne)

I got mine to work by editing /etc/nsswitch.conf I changed
hosts: mymachines resolve [!UNAVAIL=return] files myhostname dns
to
hosts: dns [!UNAVAIL=return] files
see https://wiki.archlinux.org/title/Domain_name_resolution.

Another workaround is to stop (or mask) systemd-resolved after warp-svc is running.

tdworz commented on 2023-08-03 10:48 (UTC)

The upstream URL would probably be better set as https://cloudflarewarp.com. Setting it to https://1.1.1.1 results in an unusable link for most people. Moreover, the idea that httpS://<ip> is a thing is technically wrong (https://stackoverflow.com/questions/33419568/accessing-https-sites-with-ip-address) regardless of their little DNS trick.

ollosh commented on 2023-07-30 16:17 (UTC)

I'm still getting Reason: Connectivity check failed due to DNS Lookup Failed Anyone experiencing the same issue?

ymz1376 commented on 2023-07-28 18:47 (UTC)

thanks for update

confirmed commented on 2023-07-28 14:00 (UTC)

Latest update works. Thanks!

1 2 3 4 5 6 .. 13 Next › Last »