Hello Tom, or anyone else affected, Accepted vagrant into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/vagrant/1.8.1+dfsg- 1ubuntu0.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: vagrant (Ubuntu) Status: New => Fix Released ** Changed in: vagrant (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1747426 Title: Vagrant <2.x can no longer fetch box metadata from Hashicorp Status in cloud-images: New Status in vagrant package in Ubuntu: Fix Released Status in vagrant source package in Xenial: Fix Committed Status in vagrant source package in Artful: Fix Committed Bug description: [Impact] As of February 2nd, the legacy Vagrant Cloud URLs were disabled by Hashicorp[0], meaning that the versions of vagrant in xenial and artful can no longer fetch Vagrant boxes from the global index (which is a fundamental part of Vagrant use). [0] https://groups.google.com/forum/#!topic/vagrant-up/H8C68UTkosU [Test Case] Before fix: $ vagrant box add 'ubuntu/trusty64' [...] URL: ["https://atlas.hashicorp.com/ubuntu/trusty64";] Error: The requested URL returned error: 404 Not Found After fix: $ vagrant box add 'ubuntu/trusty64' ==> box: Loading metadata for box 'ubuntu/trusty64' box: URL: https://vagrantcloud.com/ubuntu/trusty64 [...] [Regression Potential] These changes were cherry-picked directly from upstream (where they have been for several upstream releases), and they only affect the parts of the code concerned with the fetching of boxes (which doesn't work at all currently). I believe the potential for regression outside this functionality is low. [Original Report] When trying to update my ubuntu/trusty64 vagrant box, I get the following failure: $ vagrant box update --box 'ubuntu/trusty64' Checking for updates to 'ubuntu/trusty64' Latest installed version: 20180124.0.0 Version constraints: > 20180124.0.0 Provider: virtualbox There was an error while downloading the metadata for this box. The error message is shown below: The requested URL returned error: 404 Not Found I have the following Vagrant version: $ vagrant --version Vagrant 2.0.2 and am able to access the resources where I assume they are hosted: $ curl -O http://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 4 425M 4 17.1M 0 0 1062k 0 0:06:50 0:00:16 0:06:34 972k To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1747426/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : [email protected] Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
