Latest update to heroku cli seems corrupted

[sdalezman]

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

After the latest version of the cli was updated, installing the cli started failing for us on circleci on a ubuntu 14.04.

Here's the output from the build:

curl https://cli-assets.heroku.com/install-ubuntu.sh | sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

100  1232  100  1232    0     0   1232      0  0:00:01 --:--:--  0:00:01 28651
This script requires superuser access to install apt packages.
You will be prompted for your password by sudo.
+ dpkg -s apt-transport-https
+ echo deb https://cli-assets.heroku.com/apt ./
+ dpkg -s heroku-toolbelt
+ true
+ + apt-keycurl add -
 https://cli-assets.heroku.com/apt/release.key
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

100  1737  100  1737    0     0   1737      0  0:00:01 --:--:--  0:00:01 56032
OK
+ apt-get update


Ign http://debian.neo4j.org stable/ InRelease

Ign http://repo.mongodb.org trusty/mongodb-org/3.0 InRelease

Get:1 http://debian.neo4j.org stable/ Release.gpg [819 B]

Get:2 http://debian.neo4j.org stable/ Release [1,479 B]

Ign http://archive.ubuntu.com trusty InRelease

Get:3 http://security.ubuntu.com trusty-security InRelease [65.9 kB]

Hit http://ppa.launchpad.net trusty InRelease

Hit http://repo.mongodb.org trusty/mongodb-org/3.0 Release.gpg

Get:4 http://repo.mysql.com trusty InRelease [33.5 kB]

Get:5 http://apt.postgresql.org trusty-pgdg InRelease [56.5 kB]

Hit http://repo.mongodb.org trusty/mongodb-org/3.0 Release

Get:6 http://debian.neo4j.org stable/ Packages [52.8 kB]

Get:7 http://archive.ubuntu.com trusty-updates InRelease [65.9 kB]

Ign http://ppa.launchpad.net trusty InRelease

Get:8 http://ppa.launchpad.net trusty InRelease [15.4 kB]

Hit https://apt.dockerproject.org ubuntu-trusty InRelease

Get:9 https://cli-assets.heroku.com ./ InRelease

Hit http://archive.ubuntu.com trusty Release.gpg

Get:10 http://repo.mysql.com trusty/mysql-5.7 Sources [884 B]

Get:11 http://repo.mysql.com trusty/mysql-apt-config amd64 Packages [566 B]

Get:12 http://www.apache.org 34x InRelease [3,167 B]

Get:13 http://repo.mysql.com trusty/mysql-5.7 amd64 Packages [2,841 B]

Hit http://archive.ubuntu.com trusty Release

Get:14 http://ppa.launchpad.net trusty InRelease [15.4 kB]

Get:15 http://apt.postgresql.org trusty-pgdg/main amd64 Packages [165 kB]

Hit http://repo.mongodb.org trusty/mongodb-org/3.0/multiverse amd64 Packages

Get:16 http://ppa.launchpad.net trusty InRelease [15.4 kB]

Get:17 http://security.ubuntu.com trusty-security/main amd64 Packages [924 kB]

Get:18 http://archive.ubuntu.com trusty-updates/main amd64 Packages [1,348 kB]

Hit https://apt.dockerproject.org ubuntu-trusty/main amd64 Packages

Hit http://ppa.launchpad.net trusty/main amd64 Packages

Get:19 https://cli-assets.heroku.com ./ Packages

Hit http://ppa.launchpad.net trusty Release.gpg

Get:20 http://security.ubuntu.com trusty-security/restricted amd64 Packages [18.1 kB]

Get:21 http://www.apache.org 34x/main amd64 Packages [696 B]

Get:22 http://ppa.launchpad.net trusty/main amd64 Packages [3,482 B]

Get:23 http://security.ubuntu.com trusty-security/universe amd64 Packages [292 kB]

Get:24 http://archive.ubuntu.com trusty-updates/restricted amd64 Packages [21.4 kB]

Get:25 http://archive.ubuntu.com trusty-updates/universe amd64 Packages [587 kB]

Get:26 http://security.ubuntu.com trusty-security/multiverse amd64 Packages [4,718 B]

Hit http://ppa.launchpad.net trusty Release

Get:27 http://archive.ubuntu.com trusty-updates/multiverse amd64 Packages [16.0 kB]

Get:28 http://ppa.launchpad.net trusty/main amd64 Packages [15.4 kB]

Hit http://archive.ubuntu.com trusty/main amd64 Packages

Hit http://archive.ubuntu.com trusty/restricted amd64 Packages

Get:29 http://ppa.launchpad.net trusty/main amd64 Packages [4,880 B]

Hit http://archive.ubuntu.com trusty/universe amd64 Packages

Hit http://archive.ubuntu.com trusty/multiverse amd64 Packages

Hit http://ppa.launchpad.net trusty/main amd64 Packages

Hit https://packagecloud.io trusty/main Sources

Hit https://packagecloud.io trusty/main Sources

Fetched 3,830 kB in 2s (1,553 kB/s)

Reading package lists... Done

W: Size of file /var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_trusty-security_multiverse_binary-amd64_Packages.gz is not what the server reported 4718 4728
W: Size of file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_trusty-updates_multiverse_binary-amd64_Packages.gz is not what the server reported 16015 16331
+ apt-get install -y heroku

Reading package lists... Done


Building dependency tree       


Reading state information... Done

The following package was automatically installed and is no longer required:
  os-prober
Use 'apt-get autoremove' to remove it.
The following packages will be upgraded:
  heroku
1 upgraded, 0 newly installed, 0 to remove and 305 not upgraded.
Need to get 15.3 MB of archives.
After this operation, 0 B of additional disk space will be used.


Fetched 15.3 MB in 0s (19.9 MB/s)
dpkg-deb: error: archive '/var/cache/apt/archives/heroku_7.5.0-1_amd64.deb' has premature member 'control.tar.xz' before 'control.tar.gz', giving up

dpkg: error processing archive /var/cache/apt/archives/heroku_7.5.0-1_amd64.deb (--unpack):

 subprocess dpkg-deb --control returned error exit status 2

E: Sub-process /usr/bin/dpkg returned an error code (1)

curl https://cli-assets.heroku.com/install-ubuntu.sh | sh returned exit code 100

Action failed: curl https://cli-assets.heroku.com/install-ubuntu.sh | sh

What is the expected behavior?

This is a fresh installation of the heroku cli on circleci's ubuntu 14.04 trusty version. This is an old repo that we haven't moved over to Docker based installations so our heroku version isn't frozen in that workflow.

Is it possible to install a specific version of the heroku cli without it auto-updating?

[jdx]

This is likely happening because I shifted the build to run on ubuntu 18. I'll switch it back for now.

Seems to be the same issue: sbt/sbt-native-packager#1067

[warrenrentlytics]

We are seeing this same issue as well. Is there a workaround? Thanks!

[jdx]

CI is building right now but this should be resolved when it is complete

[robertzych]

This issue appears to be resolved now.