Package Details: postman-bin 7.34.0-1

Git Clone URL: (read-only, click to copy)
Package Base: postman-bin
Description: Build, test, and document your APIs faster
Upstream URL:
Licenses: custom
Submitter: claudiodangelis
Maintainer: j.taala
Last Packager: j.taala
Votes: 185
Popularity: 4.12
First Submitted: 2016-10-21 18:18
Last Updated: 2020-10-08 20:57

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 ... Next › Last »

Xanarion commented on 2020-06-07 13:03

While works as expected, the 7.25.2 is not working. Seems they remove patched versions as 7.25.3 is out and the download URL for newest version is working:

SHA256 for 7.25.3 is bc02b0b86e18df0f333e8496071d52cdb32b8a23b1febab81e040890502729a9

j.taala commented on 2020-05-28 08:23

@Goomb, just checked it and it's working fine on this end. Mostly likely a CDN sync issue on their end. Might need to try again later. Can also check that resolves.

Goomb commented on 2020-05-28 07:23

@j.taala Error downloading sources: postman-bin. Download link was changed to

wooque commented on 2020-03-04 19:15

@j.taala 7.19.1 is out

j.taala commented on 2020-02-10 21:30

No probs pythoneer. Btw, I've just updated to 7.18.0 and also changed the checksums to sha256 (preferred for AUR). Let me know if see any issues here.

pythoneer commented on 2020-02-10 18:00

Just to give an update on this – the problem is gone for my case. I think the CDN is progressively updating their caches. Maybe they deployed a wrong version and immediately fixed it in the primary source and that update needs to ripple through the CDN nodes. Thanks for your quick responses btw!

j.taala commented on 2020-02-09 11:03

Well crap, must be an issue on their mirroring or CDN nodes end.

wget gets me the correct file (note the download address resolves differently - looks like they're using cloudfront, not synced up properly?):

--2020-02-09 21:59:33--
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving (,,, ...
Connecting to (||:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 80973216 (77M) [application/gzip]
Saving to: ‘linux64’

linux64                                                     100%[==========================================================================================================================================>]  77.22M  2.76MB/s    in 26s     

2020-02-09 22:00:01 (2.97 MB/s) - ‘linux64’ saved [80973216/80973216]

$md5sum linux64                                                                                                                                                                                     
b5dcca9c97c0dbc06e0ae1e0507d772f  linux64

P.S. don't laugh at my download speeds (blimmin` Australia...)

pythoneer commented on 2020-02-09 10:57

Downloading the file from with Mozilla Firefox gets me the correct file.

Doing the same with wget gets me the wrong canary file

$ wget <>
--2020-02-09 11:53:00--  <>
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving (,,, ...
Connecting to (||:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 81058216 (77M) [application/gzip]
Saving to: ‘linux64’

linux64                       100%[=================================================>]  77,30M  11,7MB/s    in 6,6s

2020-02-09 11:53:07 (11,7 MB/s) - ‘linux64’ saved [81058216/81058216]

$ tar -zxf linux64 && ls
linux64  PostmanCanary

j.taala commented on 2020-02-09 10:55

Thanks pythoneer. That's definitely a different file that the same makepkg downloads for me (even though download link is the same). Any thoughts here?

Only thing I can think of is some CDN / mirror issue (e.g. CDN node closest to where you are has an issue where it's pointing to the canary builds?). I'm in Australia btw and can confirm installing via yay downloads and checkums the correct file...

Haven't seen this issue before.

pythoneer commented on 2020-02-09 10:47

ls ~/.cache/yay/
completion.cache  postman-bin  vcs.json

rm -rf ~/.cache/yay/postman-bin

ls ~/.cache/yay/
completion.cache  vcs.json

yay -S postman-bin
:: Checking for conflicts...
:: Checking for inner conflicts...
[Aur: 1]  postman-bin-7.17.0-1

:: Downloaded PKGBUILD (1/1): postman-bin
  1 postman-bin                              (Installed) (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
:: Parsing SRCINFO (1/1): postman-bin
==> Making package: postman-bin 7.17.0-1 (So 09 Feb 2020 11:41:38 CET)
==> Retrieving sources...
  -> Downloading Postman-linux-x64-7.17.0.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 77.3M  100 77.3M    0     0  11.3M      0  0:00:06  0:00:06 --:--:-- 11.5M
  -> Found postman.desktop
==> Validating source files with md5sums...
    Postman-linux-x64-7.17.0.tar.gz ... FAILED
    postman.desktop ... Passed
==> ERROR: One or more files did not pass the validity check!
Error downloading sources: postman-bin

md5sum ~/.cache/yay/postman-bin/Postman-linux-x64-7.17.0.tar.gz 
bfebe8d41369d074cbef60ce04ee8ddc  /home/naikon/.cache/yay/postman-bin/Postman-linux-x64-7.17.0.tar.gz

tar -zxvf ~/.cache/yay/postman-bin/Postman-linux-x64-7.17.0.tar.gz

cd ~/PostmanCanary/ && ls
app  PostmanCanary