| 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) |
Just to confirm the results that @quangdinh and @muffehazard get. So I guess it's not an environmental failure, but -perhaps- and environmental success. :)
Is there any information that I can provide from my environment that might be useful for you, @j.taala?
@j.taala I'm using Arch
> which chmod
/bin/chmod
> chmod --version
chmod (GNU coreutils) 9.0
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by David MacKenzie and Jim Meyering.
But why do we need to chmod to 755? Not all files are executable. Why just not leave the file permission as is?
same here:
~/.c/y/postman-bin# makepkg -sC
==> Making package: postman-bin 9.0.3-1 (Do 30 Sep 2021 10:44:50 CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found Postman-linux-x64-9.0.3.tar.gz
-> Found postman.desktop
==> Validating source files with sha256sums...
Postman-linux-x64-9.0.3.tar.gz ... Passed
postman.desktop ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
-> Extracting Postman-linux-x64-9.0.3.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Entering fakeroot environment...
==> Starting package()...
==> ERROR: A failure occurred in package().
Aborting...
Thanks @muffehazard - hadn't seen this before you and @quangdinh raised it. Could @quangdinh and @muffehazard let me know your distro (e.g. arch, manjaro, arco, etc.) and let me know the output of
which chmod
and
chmod --version
Thanks!
Having the same problem with the build as @quangdinh, commenting the mentioned 22 and 24 chmod-lines makes the build succeed. Tested with both yay and without, both result the same.
Did a clean chroot build and it built without issue. Not sure what went wrong with your previous build @quangdinh.
@j.taala No helpers. Here is a screenshot of what I did: https://ibb.co/hHgZDrC
Thanks @quangdinh - anyone else seeing the chmod error?
@quangdinh did you use an aur-helpers? (e.g. yay etc.). A chmod at that point would generally mean you don't have perms to change those files in the build dir.
It builds fine for me - I'll try a clean chroot build to see if it shows any issues there.
Got an error while trying to install this package:
==> Making package: postman-bin 9.0.2-1 (Thu 30 Sep 2021 02:08:06 PM +07)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading Postman-linux-x64-9.0.2.tar.gz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 127M 100 127M 0 0 14.3M 0 0:00:08 0:00:08 --:--:-- 17.4M
-> Found postman.desktop
==> Validating source files with sha256sums...
Postman-linux-x64-9.0.2.tar.gz ... Passed
postman.desktop ... Passed
==> Extracting sources...
-> Extracting Postman-linux-x64-9.0.2.tar.gz with bsdtar
==> Entering fakeroot environment...
==> Starting package()...
==> ERROR: A failure occurred in package().
Aborting...
Seems it's caused by line 22 and line 24, specifically the "chmod" command failed. I fixed it by removing those lines with "chmod". While doing so, I also update to version 9.0.3: https://gist.github.com/quangdinh/4191ae2c625ac36b398139c386e35937
@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
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.