Package Details: postman-bin 11.19.0-1

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: 289
Popularity: 2.44
First Submitted: 2016-10-21 18:18 (UTC)
Last Updated: 2024-11-12 20:35 (UTC)

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

git clone https://aur.archlinux.org/postman-bin.git
cd postman-bin

Edit the PKGBUILD file with whatever editor you like: edit line 4 to be pkgver=8.11.1 or whatever version you like, then save and exit out of the editor and run

updpkgsums
makepkg -sif

updpkgsums will download the file and update sha for file in PKGBUILD so it will install with makepkg

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

Latest Comments

« First ‹ Previous 1 .. 16 17 18 19 20 21

claudiodangelis commented on 2016-10-27 22:21 (UTC)

@jeffska, @yayo56: the problem is that the URL points to the latest available release, it does not point to a specific version, so when there is a new release, the URL destination changes and consequentially the checksum validation fails. As of this writing the latest version is 4.8.1, although it was 4.8.0 when I packaged it. I have already reached out to Postman support to see if a list of direct links is available. Thanks for your patience.

jeffska commented on 2016-10-27 22:16 (UTC)

Having the same problem as @yayo56. Downloading the file from a browser shows matching MD5 in the PKGBUILD. The download from makepkg via curl shows a different file size and MD5. Not sure what's happening here.

yayo56 commented on 2016-10-27 18:30 (UTC)

==> Building and installing package ==> Making package: postman-bin 4.8.0-2 (Thu Oct 27 20:26:01 CEST 2016) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Downloading linux?arch=64... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 50.5M 100 50.5M 0 0 366k 0 0:02:21 0:02:21 --:--:-- 279k ==> Validating source files with md5sums... linux?arch=64 ... FAILED ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build postman-bin. $> md5sum linux\?arch=64 1d2aa6932a567809245a3c0315555ba9 linux?arch=64

claudiodangelis commented on 2016-10-24 08:14 (UTC)

@chrcoe thanks for reporting, it's fixed now.

chrcoe commented on 2016-10-23 13:32 (UTC)

I receive this error: ==> Starting package()... install: cannot stat 'LICENSE': No such file or directory ==> ERROR: A failure occurred in package(). Aborting... ==> ERROR: Makepkg was unable to build postman-bin. So I commented out the two lines relating to installing the LICENSE file to get it to build and install. I am sure there is just an invalid path somewhere. I then manually copied the license files to where they should be (/usr/share/licenses/postman-bin)

« First ‹ Previous 1 .. 16 17 18 19 20 21