Package Details: heroku-cli 7.0.98-2

Git Clone URL: (read-only)
Package Base: heroku-cli
Description: a tool for creating and managing Heroku apps from the command line
Upstream URL:
Licenses: custom, ISC
Conflicts: heroku-cli, heroku-client-standalone, heroku-toolbelt, ruby-heroku
Provides: heroku-cli
Submitter: Redrield
Maintainer: Redrield
Last Packager: Redrield
Votes: 28
Popularity: 4.566804
First Submitted: 2017-08-15 23:19
Last Updated: 2018-06-27 16:11

Dependencies (2)

Required by (0)

Sources (1)

Latest Comments

mprom commented on 2018-07-18 08:48

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

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

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

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

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

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: (syntax: `source=('filename::fileuri')`)?


Throne3d commented on 2017-08-21 20:48

The upstream URL seems to be missing the protocol (`https://`), so it currently points to instead of what it should,

Other than that, thanks for this!

Redrield commented on 2017-08-17 17:07

Fixed in newest release

Alir3z4 commented on 2017-08-17 12:16

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