Search Criteria
Package Details: heroku-cli 7.17.1-1
| Git Clone URL: | https://aur.archlinux.org/heroku-cli.git (read-only) |
|---|---|
| Package Base: | heroku-cli |
| Description: | a tool for creating and managing Heroku apps from the command line |
| Upstream URL: | https://devcenter.heroku.com/articles/heroku-cli |
| Licenses: | |
| Conflicts: | |
| Submitter: | Redrield |
| Maintainer: | Redrield (aimileus) |
| Last Packager: | Redrield |
| Votes: | 34 |
| Popularity: | 4.145440 |
| First Submitted: | 2017-08-15 23:19 |
| Last Updated: | 2018-10-16 22:32 |
Dependencies (3)
- nodejs (nodejs-git, nodejs-0.12, nodejs6-bin, nodejs-lts-boron, nodejs-lts-carbon)
- npm (npm53, npm4, nodejs6-bin) (make)
- git (git-git) (optional) – Deploying to Heroku
Latest Comments
1 2 Next › Last »
iboyperson commented on 2018-10-07 03:26
just fyi rev resets to 1 on version bump
soloturn commented on 2018-09-17 03:41
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
I can't reproduce this starting from a fresh start from the AUR
procrastinator commented on 2018-09-03 17:31
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
Looks like you've updated the pkgrel in the PKGBUILD, but didn't update .SRCINFO
A simple
mksrcinfoshould fix this =)saifazmi commented on 2018-08-20 08:26
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
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
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.