(I mistakenly wrote "1.28 is out" instead of "7.28 is out" as the reason for flagging out of date. Clarifying here because that message cannot be edited.)
Search Criteria
Package Details: postman-bin 11.15.0-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/postman-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | postman-bin |
| Description: | Build, test, and document your APIs faster |
| Upstream URL: | https://www.getpostman.com |
| Licenses: | custom |
| Conflicts: | postman |
| Provides: | postman |
| Submitter: | claudiodangelis |
| Maintainer: | j.taala |
| Last Packager: | j.taala |
| Votes: | 287 |
| Popularity: | 2.48 |
| First Submitted: | 2016-10-21 18:18 (UTC) |
| Last Updated: | 2024-10-06 10:21 (UTC) |
Dependencies (3)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libxss
- nss (nss-hgAUR)
Required by (0)
Sources (3)
Rulatir commented on 2020-07-14 10:38 (UTC)
j.taala commented on 2020-06-09 05:38 (UTC) (edited on 2020-06-09 05:49 (UTC) by j.taala)
Hey Spixmaster - just checked sha256sum and install and passes sha256 checks fine. Most likely a CDN sync issue on their end (either hasn't synced across all their CDN nodes or they've done another stealth update and mismatches). Either way try again in a little bit. I'll keep an eye on it as well and recheck for changed binaries etc.
sha256sum for the main download should be:
$ sha256sum Postman-linux-x64-7.26.0.tar.gz
72447276645d4fcab9a6939cec6f9a996ef976776bc796913d2200b7121aba17
Spixmaster commented on 2020-06-09 05:09 (UTC)
It cannot be installed. When the "sha1sums" are check one is not correct.
j.taala commented on 2020-06-07 21:47 (UTC)
Thanks Xanarion, have updated to 7.25.3.
Xanarion commented on 2020-06-07 13:03 (UTC) (edited on 2020-06-07 13:07 (UTC) by Xanarion)
While https://dl.pstmn.io/download/version/7.25.0/linux64 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: https://dl.pstmn.io/download/version/7.25.3/linux64.
SHA256 for 7.25.3 is bc02b0b86e18df0f333e8496071d52cdb32b8a23b1febab81e040890502729a9
j.taala commented on 2020-05-28 08:23 (UTC)
@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 https://dl.pstmn.io/download/version/7.25.0/linux64 resolves.
Goomb commented on 2020-05-28 07:23 (UTC) (edited on 2020-05-28 07:23 (UTC) by Goomb)
@j.taala Error downloading sources: postman-bin. Download link was changed to https://dl.pstmn.io/download/latest/linux64
wooque commented on 2020-03-04 19:15 (UTC)
@j.taala 7.19.1 is out
j.taala commented on 2020-02-10 21:30 (UTC)
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 (UTC)
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!
Pinned Comments
j.taala commented on 2021-09-17 09:50 (UTC) (edited on 2021-12-21 22:53 (UTC) by j.taala)
@ntfc I was going to go the other way (update to 9.0.1 instead of reverting back to 8.11.1).
P.S. postman are pretty bad at updating their release notes page (even after a new version is out).
If you want to revert to any previous version you can do so by cloning the aur repo and changing the version in the PKGBUILD file and using makepkg to build it (it will download and install that version for you). E.g.:
Edit the
PKGBUILDfile with whatever editor you like: edit line 4 to bepkgver=8.11.1or whatever version you like, then save and exit out of the editor and runupdpkgsumswill download the file and update sha for file in PKGBUILD so it will install with makepkgj.taala commented on 2020-11-21 20:10 (UTC)
Have now updated to to 7.36.0, which apparently resolves the issue in the original 7.35.0 update. Thanks to @hertog and @fagianijunior for the heads up.