Closed Edwin-KeXu closed 7 months ago
Thanks for opening your first issue here! Be sure to follow the issue template and include your OS/Vagrant/VVV versions! Don't forget you can get support in the VVV slack at https://varyingvagrantvagrants.org/docs/en-US/slack/
Can you include the entire output? 7.4 is nearing end of life soon I hope the packages haven’t been withdrawn but I can’t tell from the output. It may even be a temporary network connectivity thing
On Sat, 19 Aug 2023 at 16:52, welcome[bot] @.***> wrote:
Thanks for opening your first issue here! Be sure to follow the issue template and include your OS/Vagrant/VVV versions! Don't forget you can get support in the VVV slack at https://varyingvagrantvagrants.org/docs/en-US/slack/
— Reply to this email directly, view it on GitHub https://github.com/Varying-Vagrant-Vagrants/VVV/issues/2686#issuecomment-1685033085, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAOLZ6JVBIRV7VS3VV2NXLXWDOKBANCNFSM6AAAAAA3WU4YZE . You are receiving this because you are subscribed to this thread.Message ID: @.***>
provisioner-main.log this
vagrant version: Vagrant 2.3.7 Apple MacOS (M1)
Hmm resource temporarily unavailable, there's nothing that can be done to fix that at the VVV end of PHP 7.4 is still to be used.
TLDR: it's saying something equivalent to the Ubuntu PHP 7.4 package shop doesn't open for another hour or two, try again later
You may also have luck switching your machine to a different network on a different ISP, universities for example are notorious for interfering to try and save bandwidth by caching things and messing it up
Closing this as the issue reported is a temporary package availability error, it isn't something VVV has control over or can influence, and will self-resolve given time.
Fixing this properly would require a re-architecture of how Apt work, I expect this will take tens of thousands of man hours across many major Linux distributions
Closing this as the issue reported is a temporary package availability error, it isn't something VVV has control over or can influence, and will self-resolve given time.
Fixing this properly would require a re-architecture of how Apt work, I expect this will take tens of thousands of man hours across many major Linux distributions
Are you using the latest stable or develop branch version of VVV?
Yes (develop)
Is it a new VVV, or an existing VVV that used to work?
Existing, worked but now broken
Did you use a CustomFile?
No (default)
Whats the problem?
When I execute the vagrant up --provision command, I get an error: Installing apt-get packages returned a failure code, cleaning up apt caches then exiting
How do we reproduce it?
No response
What is the output of
vagrant status
Which Operating System are you using?
Apple MacOS (Arm64/Apple Silicon)
Which provider are you using?
Parallels (Apple Silicon/Arm)