Package Details: heroku-cli 7.60.1-1

Git Clone URL: https://aur.archlinux.org/heroku-cli.git (read-only, click to copy)
Package Base: heroku-cli
Description: CLI to manage Heroku apps and services with forced auto-update removed
Upstream URL: https://devcenter.heroku.com/articles/heroku-cli
Licenses: custom, ISC
Conflicts: heroku-cli-bin, heroku-client-standalone, heroku-toolbelt, ruby-heroku
Provides: heroku, heroku-cli
Submitter: Redrield
Maintainer: sampsoncrowley
Last Packager: sampsoncrowley
Votes: 71
Popularity: 0.23
First Submitted: 2017-08-15 23:19 (UTC)
Last Updated: 2022-04-02 19:44 (UTC)

Pinned Comments

sampsoncrowley commented on 2019-12-06 05:22 (UTC)

Pull Requests welcome @ https://github.com/SampsonCrowley/arch_packages

Latest Comments

qark commented on 2022-04-02 22:06 (UTC)

PKGBUILD uses npx tool, should have npm as make dependency.

sampsoncrowley commented on 2022-04-02 16:46 (UTC)

Hi guys, sorry again that it's been a while since there's been a new release. I moved houses, and only just now got my arch box out unpacked. I've been only using my work laptop until recently. will get a release out today

bobpaul commented on 2022-01-07 18:45 (UTC) (edited on 2022-01-07 19:42 (UTC) by bobpaul)

Edit Nevermind. I think this is my issue to sort out. I built the package on another machine and was able to install and run that here.

I'm getting this. I tried switching from nodejs to nodejs-lts-gallium same issue.

$ heroku
/usr/lib/heroku/node_modules/@oclif/command/node_modules/semver/semver.js:1

SyntaxError: Invalid or unexpected token
    at Object.compileFunction (node:vm:352:18)
    at wrapSafe (node:internal/modules/cjs/loader:1031:15)
    at Module._compile (node:internal/modules/cjs/loader:1065:27)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/usr/lib/heroku/node_modules/@oclif/command/lib/index.js:4:16)
    at Module._compile (node:internal/modules/cjs/loader:1101:14)

sampsoncrowley commented on 2021-07-09 22:01 (UTC)

Sorry for the late release of 7.56.0; the fact that it was released got buried in my inbox under a stack of work

valandil commented on 2021-05-03 11:33 (UTC)

Not the maintainer, but I would suggest trying to build in a clean chroot. It builds fine for me that way.

ElderBladeX commented on 2021-05-02 21:43 (UTC) (edited on 2021-05-02 21:45 (UTC) by ElderBladeX)

Still having trouble with installing this package. I have yarn (1.22.10-1) and npm (7.11.2-1) installed on my system, but I get this error:

npm ERR! Invalid Version:
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/<user-name>/.npm/_logs/2021-05-02T21_12_58_012Z-debug.log
==> ERROR: A failure occurred in prepare().
    Aborting...

Looking at the npm log, it just says "Invalid Version:" I searched this error for npm and it seems to be sensitive to the format of the version number in the json package. From what I can tell, 7.53.0 is valid and is listed as such in the PKGBUILD. Yarn is also listed as a make dependency in this version so I'm at a loss as to what is causing the error.

I opted to install heroku-cli-bin instead, which installs just fine, but wanted to know what I'm missing here.

sampsoncrowley commented on 2021-04-11 12:20 (UTC)

Actually @jplatte now I remember it has both because the install crashes if each section isn't installed with each specific packager. If the outer packaging tools aren't installed with yarn, the oclif-dev tools fail to build. And now that I wen't back to remove the npm dependency I remember now that if you just drop and try to run everything with yarn, it causes npm-shrinkwrap failures and fails there. Basically, when it comes down to it, the heroku cli maintainers are assholes. They force updates on you, and they can't stick to a package manager.

If you don't want both (though, like I said, impossible to actually only have yarn without npm as far as I'm aware) use heroku-cli-bin

sampsoncrowley commented on 2021-03-23 03:40 (UTC)

@jplatte it has both because I forgot it was there.

It will be removed in the next release, but not worth releasing a new build just to take it out of makedepends; yarn requires nodejs anyways, and as far as I'm aware, it's not possible to have nodejs without npm since they're packaged together so it really doesn't change anything.

valandil commented on 2021-03-06 03:33 (UTC) (edited on 2021-03-06 03:33 (UTC) by valandil)

I have been having issues building 7.50.0. Interestingly, I get different errors when I try to build in a clean chroot than when building on my regular system. For the clean chroot build to work at all, I had to modify the custom function:

From cd68cdfeb007ce2d41ddf67fbf505833c086ef71 Mon Sep 17 00:00:00 2001
From: Joey Dumont <joey.dumont@gmail.com>
Date: Fri, 5 Mar 2021 22:20:51 -0500
Subject: [PATCH 1/1] Fix clean chroot build

---
 PKGBUILD | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/PKGBUILD b/PKGBUILD
index ce263b9..da471e6 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -11,7 +11,7 @@ arch=('any')
 url="https://devcenter.heroku.com/articles/heroku-cli"
 license=('custom' 'ISC')
 depends=('nodejs')
-makedepends=('npm' 'yarn' 'perl')
+makedepends=('npm' 'yarn' 'perl' 'git')
 optdepends=('git: Deploying to Heroku')
 conflicts=('heroku-cli-bin' 'heroku-client-standalone' 'heroku-toolbelt' 'ruby-heroku')
 source=("https://github.com/heroku/cli/archive/v$pkgver.tar.gz")
@@ -20,7 +20,7 @@ sha512sums=('d5d80ba4439407b75efa7dffff031a4112336de4bab953141ee399e1861275d8b8b
 options=('!strip')
 provides=('heroku' 'heroku-cli')

-append_path() {
+_append_path() {
   case ":$PATH:" in
       *:"$1":*)
           ;;
@@ -33,9 +33,9 @@ prepare() {
   # Set path to perl scriptdirs if they exist
   # https://wiki.archlinux.org/index.php/Perl_Policy#Binaries_and_scripts
   # Added /usr/bin/*_perl dirs for scripts
-  [ -d /usr/bin/site_perl ] && append_path '/usr/bin/site_perl'
-  [ -d /usr/bin/vendor_perl ] && append_path '/usr/bin/vendor_perl'
-  [ -d /usr/bin/core_perl ] && append_path '/usr/bin/core_perl'
+  [ -d /usr/bin/site_perl ] && _append_path '/usr/bin/site_perl'
+  [ -d /usr/bin/vendor_perl ] && _append_path '/usr/bin/vendor_perl'
+  [ -d /usr/bin/core_perl ] && _append_path '/usr/bin/core_perl'

   export PATH

-- 
2.30.1

A regular makepkg -Cfs yields:

$ makepkg -Cfs
==> Making package: heroku-cli 7.50.0-1 (Fri 05 Mar 2021 10:28:30 PM)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found v7.50.0.tar.gz
==> Validating source files with sha256sums...
    v7.50.0.tar.gz ... Passed
==> Validating source files with sha512sums...
    v7.50.0.tar.gz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting v7.50.0.tar.gz with bsdtar
==> Starting prepare()...
~/build/heroku-cli/src ~/build/heroku-cli/src
~/build/heroku-cli/src/cli-7.50.0 ~/build/heroku-cli/src ~/build/heroku-cli/src
yarn install v1.22.10
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
warning "workspace-aggregator-038f5b6b-fe5e-49e0-bad1-bb8c9a27a8fa > @heroku-cli/plugin-addons-v5 > @oclif/plugin-legacy > @oclif/command@1.8.0" has unmet peer dependency "@oclif/config@^1".
[5/5] Building fresh packages...
Done in 43.88s.
~/build/heroku-cli/src/cli-7.50.0/packages/cli ~/build/heroku-cli/src/cli-7.50.0 ~/build/heroku-cli/src ~/build/heroku-cli/src
npm WARN deprecated @types/write-json-file@3.2.1: This is a stub types definition. write-json-file provides its own type definitions, so you do not need this installed.
npm WARN deprecated strip-eof@2.0.0: Renamed to `strip-final-newline` to better represent its functionality.
npm ERR! semver.simplifyRange is not a function

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/valandil/.npm/_logs/2021-03-06T03_29_39_399Z-debug.log
==> ERROR: A failure occurred in prepare().
    Aborting...

Not sure if the error comes from semver. Maybe the version is too recent? (I'm kind of a n00b at npm packaging.)

However, when trying to build in a clean chroot:

==> Starting prepare()...
~/heroku-cli/src ~/heroku-cli/src
~/heroku-cli/src/cli-7.50.0 ~/heroku-cli/src ~/heroku-cli/src
yarn install v1.22.10
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
warning "workspace-aggregator-653c8e20-0ece-412a-9081-7b661e8d6fe4 > @heroku-cli/plugin-addons-v5 > @oclif/plugin-legacy > @oclif/command@1.8.0" has unmet peer dependency "@oclif/config@^1".
[5/5] Building fresh packages...
Done in 60.71s.
~/heroku-cli/src/cli-7.50.0/packages/cli ~/heroku-cli/src/cli-7.50.0 ~/heroku-cli/src ~/heroku-cli/src
npm WARN deprecated strip-eof@2.0.0: Renamed to `strip-final-newline` to better represent its functionality.
npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated @types/write-json-file@3.2.1: This is a stub types definition. write-json-file provides its own type definitions, so you do not need this installed.
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)

added 859 packages, removed 3 packages, changed 4 packages, and audited 939 packages in 37s

38 packages are looking for funding
  run `npm fund` for details

8 vulnerabilities (3 low, 2 moderate, 3 high)

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
fatal: not a git repository (or any of the parent directories): .git
    Error: Command failed: git rev-parse --short HEAD
    null

    Code: 128
==> ERROR: A failure occurred in prepare().
    Aborting...
==> ERROR: Build failed, check /var/lib/archbuild/extra-x86_64/valandil/build

Any ideas on how to fix either of these issues? Am I the only one with these issues?

jplatte commented on 2021-01-28 11:42 (UTC) (edited on 2021-01-28 11:42 (UTC) by jplatte)

Is there a reason this uses both yarn install and npm install? If only yarn works / is supported for building this, why not use that consistently (and drop the make dep on npm)?

sampsoncrowley commented on 2021-01-27 21:00 (UTC)

@patchcard2 nope, you're right, after fixing the exit problem by trapping it in a subcommand, yarn isnt added to the PATH for prepare to use when installed through npm. makedepends is the only option

sampsoncrowley commented on 2021-01-27 20:32 (UTC)

@patchcard2 not everyone wants yarn, an npm package, installed through arch packages, instead of through npm, the actual package manager for yarn. This seemed like the cleaner way of checking that it was installed through either method

somepaulo commented on 2021-01-23 13:22 (UTC)

@zeteref Thank you! Adding yarn to make depends in PKGBUILD solves the problem.

patchcard2 commented on 2021-01-23 12:50 (UTC) (edited on 2021-01-23 12:51 (UTC) by patchcard2)

# install packaging tools; install fails now unless installed with yarn >:(
hasYarn="$(which yarn 2> /dev/null)"

if [ -z "$hasYarn" ]; then
   npm install -g yarn
fi

I'm curious, wouldn't the "cleaner" way be to just add yarn as a make dependency?

zeteref commented on 2021-01-23 08:57 (UTC)

@somepaulo there seems to be a small bug in prepare where makepkg exists when which returns exit code 1 on this check:

hasYarn="$(which yarn 2> /dev/null)

after i installed yarn heroku-cli installation worked

somepaulo commented on 2021-01-22 22:01 (UTC) (edited on 2021-01-22 22:02 (UTC) by somepaulo)

Cannot update package. Getting an uninformative error when trying to build package:

==> Starting prepare()...
~/.cache/yay/heroku-cli/src ~/.cache/yay/heroku-cli/src
~/.cache/yay/heroku-cli/src/cli-7.47.11 ~/.cache/yay/heroku-cli/src ~/.cache/yay/heroku-cli/src
==> ERROR: A failure occurred in prepare().
    Aborting...
error making: heroku-cli

Any suggestions? Thanks!

sampsoncrowley commented on 2021-01-05 23:21 (UTC)

The yarn requirement was because of a nodenv dependency I forgot to turn off when running build tests. yarn has been removed as a dependency again

ruestique commented on 2020-11-13 15:01 (UTC) (edited on 2020-11-13 15:14 (UTC) by ruestique)

49 packages are looking for funding
  run `npm fund` for details

found 2 vulnerabilities (1 low, 1 high)
  run `npm audit fix` to fix them, or `npm audit` for details
fatal: not a git repository (or any of the parent directories): .git
Error: Command failed: git rev-parse --short HEAD
null
    at makeError (~/.cache/pikaur/build/heroku-cli/src/cli-7.47.2/packages/cli/node_modules/qqjs/node_modules/execa/index.js:172:9)
    at ~/.cache/pikaur/build/heroku-cli/src/cli-7.47.2/packages/cli/node_modules/qqjs/node_modules/execa/index.js:277:16
    at processTicksAndRejections (node:internal/process/task_queues:93:5)
    at async Promise.all (index 1)
==> ERROR: A failure occurred in prepare().
    Aborting...


pikaur - garbage, yay did things just fine.

HarryHenryGebel commented on 2020-11-05 20:05 (UTC) (edited on 2020-11-05 20:06 (UTC) by HarryHenryGebel)

To add to ruy16109's comment, I also got append_path not found despite seeing it in your code. I had updated the package repo using git, when I deleted it and cloned it from scratch it worked fine. I don't know enough about how the package system works to know why that make a difference, but I thought it might help you. I am using makepkg to build the package if that makes a difference.

ruy16109 commented on 2020-10-17 00:42 (UTC)

Not sure if this is an issue with your scripting or with PKGBUILD syntax itself, but despite I can clearly see you have defined append_path function in the code, makechrootpkg refuses to call it, saying that the command is not found. Any ideas?

sampsoncrowley commented on 2020-10-16 19:04 (UTC)

@Gordin Thank you for finding that. I completely forgot that perl isn't added to PATH by default; I've just gotten too used to having it around I guess...

I pushed a new release of 7.46.0 that includes perl as a makedepend and also adds all three perl directories to $PATH on prepare

Gordin commented on 2020-10-16 12:48 (UTC)

Building this currently doesn't work, because a dependency uses "shasum" in the build process, which is available by default on iOS, but not on arch. On arch this comes with the "perl" package at "/usr/bin/core_perl/shasum", which is not added to $PATH by default though, so the PKGBUILD needs "perl" in makedepends and needs to add that folder to $PATH before the "npm install" step.

benslv commented on 2020-10-11 10:43 (UTC)

Getting the same error as laurensk; unable to update the package because of it.

laurensk commented on 2020-10-10 09:49 (UTC)

Hi there, I am getting the following:

/tmp/makepkg/heroku-cli/src/cli-7.45.0/packages/cli /tmp/makepkg/heroku-cli/src/cli-7.45.0 /tmp/makepkg/heroku-cli/src /tmp/makepkg/heroku-cli/src
npm WARN deprecated @types/write-json-file@3.2.1: This is a stub types definition. write-json-file provides its own type definitions, so you do not need this installed.
npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated

> yarn@1.22.10 preinstall /tmp/makepkg/heroku-cli/src/cli-7.45.0/packages/cli/node_modules/yarn
> :; (node ./preinstall.js > /dev/null 2>&1 || true)

npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN eslint-config-xo-space@0.20.0 requires a peer of eslint@^5.3.0 but none is installed. You must install peer dependencies yourself.

added 1170 packages from 1335 contributors and audited 1133 packages in 27.729s

44 packages are looking for funding
  run `npm fund` for details

found 2 vulnerabilities (1 low, 1 high)
  run `npm audit fix` to fix them, or `npm audit` for details
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Error: Command failed: git rev-parse --short HEAD
null
    at makeError (/tmp/makepkg/heroku-cli/src/cli-7.45.0/packages/cli/node_modules/qqjs/node_modules/execa/index.js:172:9)
    at /tmp/makepkg/heroku-cli/src/cli-7.45.0/packages/cli/node_modules/qqjs/node_modules/execa/index.js:277:16
    at async Promise.all (index 1)
==> ERROR: A failure occurred in prepare().
    Aborting...

Any suggestions? Thanks.

sampsoncrowley commented on 2020-09-10 20:55 (UTC)

v7.42.13-4 should fix any lingering checksum errors from differences in system caches; please let me know if you still have issues

giswqs commented on 2020-09-10 14:18 (UTC)

I got the same validity check error. Please fix this. Thanks.

sahina commented on 2020-09-09 12:33 (UTC)

Upgrade fails...

Building heroku-cli... ==> Making package: heroku-cli 7.42.13-3 (Wed 09 Sep 2020 08:31:10 AM EDT) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found heroku-v7.42.13-linux-x64.tar.xz ==> Validating source files with sha256sums... heroku-v7.42.13-linux-x64.tar.xz ... FAILED ==> ERROR: One or more files did not pass the validity check! Failed to build heroku-cli

maverick1 commented on 2020-09-08 16:01 (UTC)

Build failed for 7.42.13-3 due to invalid sha256sum for heroku-v7.42.13-linux-x64.tar.xz

sampsoncrowley commented on 2020-09-06 05:07 (UTC) (edited on 2020-09-06 05:09 (UTC) by sampsoncrowley)

For anyone wondering, the reason the package source now comes from my Google storage buckets, is so that I can precompile them specifically for Pacman/AUR compatibility.

RELEVANT THREADS:

sampsoncrowley commented on 2020-09-06 04:54 (UTC)

Sorry about the current checksums everyone. I was working with another project to debug ARM support and forgot to update them.

For the short term, version 7.42.13-1 is technically the same version just with a few different build steps from the newest version

ArchNewbie commented on 2020-09-05 05:37 (UTC) (edited on 2020-09-05 05:39 (UTC) by ArchNewbie)

I made a PR for fixing incorrect SHA256 & SHA521 sums for version 7.42.13-2

https://github.com/SampsonCrowley/arch_packages/pull/7

sampsoncrowley commented on 2020-06-15 17:19 (UTC)

Sorry for the delayed release of v7.42.1; heroku has stopped warning me when there's a new version out

sampsoncrowley commented on 2019-12-06 05:22 (UTC)

Pull Requests welcome @ https://github.com/SampsonCrowley/arch_packages

Redrield commented on 2018-10-20 22:08 (UTC)

I didn't run into that when I was testing the latest release, delete ~/.cache/yay/heroku-cli and have yay pull it fresh to see if it still occurs

heppu commented on 2018-10-20 05:52 (UTC) (edited on 2018-10-20 05:52 (UTC) by heppu)

It's seem that I cannot update this anymore:

error: missing package metadata in /home/heppu/.cache/yay/heroku-cli/heroku-cli-7.17.1-1-x86_64.pkg.tar.xz

error: '/home/heppu/.cache/yay/heroku-cli/heroku-cli-7.17.1-1-x86_64.pkg.tar.xz': invalid or corrupted package

tjquillan commented on 2018-10-07 03:26 (UTC)

just fyi rev resets to 1 on version bump

soloturn commented on 2018-09-17 03:41 (UTC)

heroku has fixed versions via yarn, and "yarn add" should be possible. also new npm recommends "npm ci" instead of "npm install" to use fixed versions. would be great if the heroku package would do this instead of a "npm install".

Redrield commented on 2018-09-03 19:32 (UTC)

I can't reproduce this starting from a fresh start from the AUR

procrastinator commented on 2018-09-03 17:31 (UTC)

Getting the following error from npm

npm ERR! code E404 npm ERR! 404 Not Found: heroku-client@^3.0.6

Psykar commented on 2018-08-21 02:32 (UTC)

Looks like you've updated the pkgrel in the PKGBUILD, but didn't update .SRCINFO

A simple mksrcinfo should fix this =)

saifazmi commented on 2018-08-20 08:26 (UTC) (edited on 2018-08-20 08:28 (UTC) by saifazmi)

Getting the following error in npm logs when trying to upgrade to the latest version.

194 verbose Linux 4.18.1-arch1-1-ARCH
195 verbose argv "/usr/bin/node" "/usr/bin/npm" "install" "-g" "--user" "root" "--prefix" "/home/saif/.cache/pacaur/heroku-cli/pkg/heroku-cli/usr" "heroku-7.9.3.tgz"
196 verbose node v10.9.0
197 verbose npm v6.4.0
198 error code ETARGET
199 error notarget No matching version found for @heroku-cli/plugin-addons-v5@^7.9.3
200 error notarget In most cases you or one of your dependencies are requesting
200 error notarget a package version that doesn't exist.
200 error notarget
200 error notarget It was specified as a dependency of 'heroku'
201 verbose exit [ 1, true ]

golinski commented on 2018-07-26 11:13 (UTC)

The newest version has permissions 777 for /usr/bin. This is not a big deal (permission on the directory are not changed), but still gives a warning during installation.

mprom commented on 2018-07-18 08:48 (UTC)

Running heroku now gives the warning: "Warning: heroku update available from 7.0.98 to 7.4.1".

pizzapill commented on 2018-06-27 09:45 (UTC)

I think "npm" is now a dependency for this package since it does not build without it.

Redrield commented on 2018-04-24 14:31 (UTC)

The way that Heroku is storing tarballs on their server has changed again, and the directory names in the unzipped tarballs give me no clues as to where static releases are found, or even an idea of what version it is (I had to hunt down their github to update pkgver). I'll see if I can find a way to revert to what I had before but for the mean time, in the next update this package is going to be skipping hashsum checks.

ad1217 commented on 2017-09-07 07:00 (UTC) (edited on 2017-09-07 07:01 (UTC) by ad1217)

So the problem here seems to be that heroku keeps updating their tar.gz without changing the name, at a somewhat faster rate than it is reasonable to update this package. They do seem to provide static versions which match the folder name in the tar.gz that is currently used (ex https://cli-assets.heroku.com/heroku-cli/channels/stable/heroku-cli-v6.14.20-737bba7-linux-x64.tar.gz for the current version), so please consider switching this package to use those (it should also remove the need for your prepare function as well). Additionally, I've created heroku-cli-nightly, which should always pull the latest.

Throne3d commented on 2017-08-23 21:11 (UTC)

Hi there! I think (as a new version of the package was released), pkgrel should be reset to 1 instead of incremented – at least, it looks that way here: https://wiki.archlinux.org/index.php/PKGBUILD#pkgrel ? Also I'm getting an issue when I try to update the package, as it's finding the old .tar.gz file and assuming it's up-to-date, then failing the new integrity check as it hasn't actually downloaded an updated version. I'm not *totally* sure what the correct way is to handle this, but it seems like you could set the script to download the file but save it with the version in the downloaded filename: https://wiki.archlinux.org/index.php/PKGBUILD#source (syntax: `source=('filename::fileuri')`)? Thanks!

Throne3d commented on 2017-08-21 20:48 (UTC)

The upstream URL seems to be missing the protocol (`https://`), so it currently points to https://aur.archlinux.org/packages/heroku-cli/devcenter.heroku.com/articles/devcenter.heroku.com/articles/heroku-cli instead of what it should, https://devcenter.heroku.com/articles/heroku-cli Other than that, thanks for this!

Redrield commented on 2017-08-17 17:07 (UTC)

Fixed in newest release

Alir3z4 commented on 2017-08-17 12:16 (UTC)

==> Validating source_x86_64 files with md5sums... heroku-cli-linux-x64.tar.gz ... FAILED ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build heroku-cli.