| 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: | 297 |
| Popularity: | 3.24 |
| First Submitted: | 2016-10-21 18:18 (UTC) |
| Last Updated: | 2025-04-30 22:45 (UTC) |
After the latest update I am having an issue with the Postman GUI. When I click into another window (after postman is running and I send a request), the entire Postman window goes black (except for the header with the minimize/maximize/close buttons). Any ideas on this would be much appreciated as I use Postman daily for development testing. For the time being, I have resigned myself to several terminal windows running curl commands...
Thank you
@claudiodangelis, you can execute some commands on a predefined phases (one of which is pre_upgrade). have a look at https://wiki.archlinux.org/index.php/PKGBUILD. look for the "install" variable
Hi gitterrost4, I don't think this is possible to do in PKGBUILD though. PKGBUILD contains information used by makepkg to build and install the package into a fakeroot environment, which is subsequently compressed into a package file and eventually installed into the system by pacman.
I need to do more research on this, many thanks for pointing it out.
According to this thread, upgrading should involve clearing the installation directory first. Otherwise it leads to unexpected behavior. Is that possible to do in the PKGBUILD?
https://github.com/postmanlabs/postman-app-support/issues/5039#issuecomment-416453456
Just change pkgver for 6.2.2 and first md5sums for 657568caeb0bdaef8e0aff8dbfc99fbb
6.2.1 released
Hi @bashM0nk3y, you are passing the wrong argument, the correct command is:
sudo pacman -U postman-bin-6.1.3-2-x86_64.pkg.tar.xz
For completeness, the argument you're using, Postman-linux-x64-6.1.3.tar.gz, is not the package built for the installation but the source package as it is relased by Postman.
[user@host:postman-bin]$ sudo pacman -U Postman-linux-x64-6.1.3.tar.gz
[sudo] password for user:
loading packages...
error: missing package metadata in Postman-linux-x64-6.1.3.tar.gz
error: 'Postman-linux-x64-6.1.3.tar.gz': invalid or corrupted packageEDIT: Sorry guys, it might help if I try to install the actual pkg huh? lol Thanks claudiodangelis!
Many thanks @libertylocked and @wshuman3, I just fixed the icon link.
The icon link is broken. It should be /opt/postman/app/resources/app/assets/icon.png instead of /opt/postman/resources/app/assets/icon.png
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 makepkg