Package Details: heroku-toolbelt 3.43.9-1

Git Clone URL: (read-only)
Package Base: heroku-toolbelt
Description: Everything you need to get started using Heroku
Upstream URL:
Licenses: MIT
Conflicts: heroku-client-standalone, heroku-toolbelt, ruby-heroku
Provides: heroku-client-standalone, heroku-toolbelt, ruby-heroku
Submitter: WhyNotHugo
Maintainer: WhyNotHugo
Last Packager: WhyNotHugo
Votes: 165
Popularity: 0.000163
First Submitted: 2016-02-03 15:44
Last Updated: 2016-08-30 21:18

Latest Comments

« First ‹ Previous 1 2 3 4 5

roylines commented on 2013-02-10 22:24

Current version is failing with an invalid md5 checksum for foreman.

yaourt errors with:
Validating source files with md5sums...
heroku-client-2.34.0.tgz ... Passed
foreman-0.61.0.tgz ... FAILED

Anonymous comment on 2013-02-09 06:10

I definitely would like to see this in [community]. The duplication of heroku-toolbelt and heroku-client is confusing (I agree -client should be merged into this package, even if not moved to [community]), and foreman is sourced strangely. Is there a reason not to just depend on ruby-foreman, and move that as well?

petelewis commented on 2013-02-06 19:03

Having said all that, there are actually easily enough votes for this to move to [community], so following any feedback, I might do that.

petelewis commented on 2013-02-06 19:02


I've taken over and reworked the PKGBUILD for the heroku toolbelt, over here:

That package now conforms to the Arch ruby packaging guidelines (and hence avoids /opt) and also uses version numbered downloads, to avoid breakage when there's an update from heroku. Thanks alanbriolat for the link.

Testing / comments welcome :-)

I'd also like to merge these two packages, since they seem to be duplicates anyway. This package has the better (more accurate) name though, I think, and both have votes.

Please let me know if there's a reason not to do this.

petelewis commented on 2013-01-25 15:55

Hi, there appears to be some duplication between this package and

Can someone clarify why there need to be two packages? Thanks.

alanbriolat commented on 2012-10-23 12:08

This package will break every time a new heroku is released, rendering it useless until it's fixed. How about using${pkgver}.tgz as the source, like this:

Mic92 commented on 2012-10-20 10:31

New checksum: