Package Details: heroku-cli-bin 8.10.0-1

Git Clone URL: https://aur.archlinux.org/heroku-cli-bin.git (read-only, click to copy)
Package Base: heroku-cli-bin
Description: CLI to Manage Heroku apps with forced auto-update removed. Packaged before release to save time and bandwidth.
Upstream URL: https://devcenter.heroku.com/articles/heroku-cli
Keywords: bin cli heroku
Licenses: custom, ISC
Conflicts: heroku-cli, heroku-client-standalone, heroku-toolbelt, ruby-heroku
Provides: heroku, heroku-cli
Submitter: sampsoncrowley
Maintainer: ChloeColman
Last Packager: ChloeColman
Votes: 13
Popularity: 0.006831
First Submitted: 2020-10-08 19:18 (UTC)
Last Updated: 2024-02-20 17:30 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

GLutz commented on 2021-05-19 22:06 (UTC) (edited on 2021-05-19 22:07 (UTC) by GLutz)

I'm sorry @sampsoncrowley, I got confused when interpreting the use of checksum. I deleted my comment so as not to induce others to the same error. Thanks for quickly fixing it.

sampsoncrowley commented on 2021-05-19 19:34 (UTC)

@Typology I'll be submitting a new release in a few minutes.

Don't bypass checksums; it means there was a mistake when creating the previous release

Typology commented on 2021-05-19 13:11 (UTC) 

==> Making package: heroku-cli-bin 7.54.0-1 (Wed 19 May 2021 04:10:45 PM +03)
==> Retrieving sources...
  -> Found heroku-cli-bin-v7.54.0-1.tar.xz
==> Validating source files with sha256sums...
    heroku-cli-bin-v7.54.0-1.tar.xz ... FAILED
==> ERROR: One or more files did not pass the validity check!
:: Packages failed to build: heroku-cli-bin-7.54.0-1

sampsoncrowley commented on 2021-01-06 06:09 (UTC)

@ngoonee sorry, I must've accidentally hit save on the PKGBUILD that hadn't had the sums updated for the release version yet when I was publishing. releasing v3 now

ngoonee commented on 2021-01-06 06:00 (UTC)

The checksums fail (upstream seems to have changed their binary).

sampsoncrowley commented on 2020-11-17 18:45 (UTC) (edited on 2020-11-17 18:47 (UTC) by sampsoncrowley)

@Taxules, @ruestique The issue should be fixed now. I seems using nodenv locally while the package was being built had effected the package process. it shouldn't happen again

sampsoncrowley commented on 2020-11-17 17:48 (UTC)

@TaXules thank you, that was what I needed to know

TaXules commented on 2020-11-17 17:38 (UTC)

@sampsoncrowley Same error than @ruestique, I fall back to 7.47.0-1 which works perfectly.

sampsoncrowley commented on 2020-11-13 22:30 (UTC)

@rustique I'm asking you to try an older version, not if you've used one previously.

« First ‹ Previous 1 2 3 Next › Last »