vagrant provision failed when Repository changed its 'Label' value . The SSH command responded with a non-zero exit status.

[jordivela007]

Command

vagrant provision

failed when Repository changed its 'Label' value . The SSH command responded with a non-zero exit status.

Solution:

In the file homestead\scripts\homestead.rb search the line with

config.vm.provision "apt_update", type: "shell", inline: "apt-get update"

and change to

config.vm.provision "apt_update", type: "shell", inline: "apt-get update --allow-releaseinfo-change"

to avoid this error in vagrant provision

[nicolasverlhiac]

I confirm that this issue also occurs during a vagrant up of a new VM, not just with vagrant provision.

I encountered exactly the same error:

E: Repository 'https://ppa.launchpadcontent.net/ondrej/php/ubuntu jammy InRelease' changed its 'Label' value from '***** The main PPA for supported PHP versions with many PECL extensions *****' to 'PPA for PHP'
The SSH command responded with a non-zero exit status.

The proposed solution by @jordivela007 works perfectly. I suggest implementing this change in the next version to avoid this problem for all users, whether during a vagrant provision or a vagrant up.

[kieranmetcalfe]

I've been experiencing this too and thank you for the fix @jordivela007

A temporary workaround, to save having local code out step with the repo can be found at https://stackoverflow.com/questions/79615328/laravel-homestead-wont-load-label-value-changed

In short - after the error, the VM is running, so you can:

vagrant ssh to enter VM console
sudo apt update
y to accept all
exit to leave console
vagrant up --provision to re-provision the VM