Vagrant 2.3.5 deb fails to install on Ubuntu 20

iainelder commented 1 year ago

Debug output

Failed CI run of Vagrant 2.3.5.

Expected behavior

Vagrant 2.3.5 should be installed via apt.

See last CI execution of Vagrant 2.3.4 for a successful example.

Actual behavior

The CI run shows the following error when installing Vagrant 2.3.5 via apt.

+ sudo apt-get install ./vagrant_2.3.5-1_amd64.deb
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  vagrant:none
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/139 MB of archives.
After this operation, 357 MB of additional disk space will be used.
Get:1 /tmp/tmp.DESY5s8fZA/vagrant_2.3.5-1_amd64.deb vagrant none 0:2.3.5-1 [139 MB]
debconf: delaying package configuration, since apt-utils is not installed
dpkg: warning: parsing file '/var/lib/dpkg/tmp.ci/control' near line 12 package 'vagrant':
 empty value for 'Architecture' field
dpkg: error processing archive /tmp/tmp.DESY5s8fZA/vagrant_2.3.5-1_amd64.deb (--unpack):
 package architecture () does not match system (amd64)
Errors were encountered while processing:
 /tmp/tmp.DESY5s8fZA/vagrant_2.3.5-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Error: Process completed with exit code 100.

Reproduction information

Vagrant version

Vagrant 2.3.5

Host operating system

Ubuntu 20

Guest operating system

Not applicable.

Steps to reproduce

Execute this script as root on Ubuntu 20 to exactly reproduce the CI installation process.

For humans:

Download Vagrant 2.3.5 deb
Install deb: sudo apt install ./vagrant.2.3.5.deb
Note error message

Vagrantfile

None.

rgl commented 1 year ago

Maybe that's because of that that vagrant 2.3.5 is not available at the repository at:

Maybe the vagrant CI pipeline should check whether is can actually install vagrant from the repository?

iainelder commented 1 year ago

Thanks, @rgl , I didn't know about the Hashicorp Apt repostiory. Maybe it was still missing from the Vagrant documentation when I wrote my installation script back in 2021.

My own CI process runs my custom installation scripts. Feel free to adapt my Vagrant installation script for any installability testing.

Now I see that the Apt repository is already supported by deb-get, so one day I'll replace that custom script with a deb-get install command.

chrisroberts commented 1 year ago

Fixed deb package is available in the dev build here. Will likely be pushing a point release that includes this update tomorrow.

iainelder commented 1 year ago

Today's CI run picked up package version 2.3.6 and installed it correctly. This is fixed now. Thanks, everyone!

hashicorp / vagrant