Your message dated Sun, 16 Aug 2015 09:39:44 +0000 with message-id <[email protected]> and subject line Bug#795666: fixed in vagrant 1.7.4+dfsg-1 has caused the Debian Bug report #795666, regarding vagrant: Vagrant 1.7.2 not compatible with Virtualbox 5 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 795666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795666 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: vagrant Version: 1:1.7.4 Severity: important Dear Maintainer, * What led up to the situation? The current version of Virtualbox is not compatible with Vagrant. I get this: The provider 'virtualbox' that was requested to back the machine 'default' is reporting that it isn't usable on this system. The reason is shown below: Vagrant has detected that you have a version of VirtualBox installed that is not supported. Please install one of the supported versions listed below to use Vagrant: 4.0, 4.1, 4.2, 4.3 The provider 'virtualbox' that was requested to back the machine 'default' is reporting that it isn't usable on this system. The reason is shown below: Vagrant has detected that you have a version of VirtualBox installed that is not supported. Please install one of the supported versions listed below to use Vagrant: 4.0, 4.1, 4.2, 4.3 * What exactly did you do (or not do) that was effective (or ineffective)? I tried: sudo apt-get purge virtualbox-dkms ; sudo apt-get install virtualbox-dkms as well as, sudo apt-get install linux-headers-$(uname -r) to make sure I had the kernel headers ... I did. In the end I just got the deb package from upstream (version 1.7.4). So I suppose this bug is in two parts a wishlist item and compatiblilty issue. Please can you upgrade to the latest vagrant package. Kind Regards Brent Clark -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Configuration Files: /etc/bash_completion.d/vagrant f892ce45189973fad3399f5f15d9bc8b [Errno 2] No such file or directory: u'/etc/bash_completion.d/vagrant f892ce45189973fad3399f5f15d9bc8b' -- no debconf information
--- End Message ---
--- Begin Message ---Source: vagrant Source-Version: 1.7.4+dfsg-1 We believe that the bug you reported is fixed in the latest version of vagrant, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro <[email protected]> (supplier of updated vagrant package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Sun, 16 Aug 2015 11:04:06 +0200 Source: vagrant Binary: vagrant Architecture: source all Version: 1.7.4+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Laurent Bigonville <[email protected]> Changed-By: Antonio Terceiro <[email protected]> Description: vagrant - Tool for building and distributing virtualized development enviro Closes: 795666 Changes: vagrant (1.7.4+dfsg-1) unstable; urgency=medium . * New upstream release - adds support for VirtualBox 5.0 (Closes: #795666) * Refresh patches Checksums-Sha1: 03ec00b9df9eb3efe167100ac84ce0498cc9093e 1993 vagrant_1.7.4+dfsg-1.dsc cfde96e62666ed63f5ddec1803fdb6136b8e67f0 537240 vagrant_1.7.4+dfsg.orig.tar.gz 5cb5d579461dad33d8cd89c05d84f25be1d254a1 12064 vagrant_1.7.4+dfsg-1.debian.tar.xz 13e9d7b59f334bce0734e213303cac8f4440860a 352450 vagrant_1.7.4+dfsg-1_all.deb Checksums-Sha256: 0bd635324932e1e3a6ef03440fac0f1fdb9d5f7f09fa61e8e6f1e62d56d944a2 1993 vagrant_1.7.4+dfsg-1.dsc 7c44ed6065de6af9b51067d343aec5311ad86d36976d7c69263735ff1c9e6ef3 537240 vagrant_1.7.4+dfsg.orig.tar.gz b3b79acfaecd21559ffe6e0b21ff648eb86b3312c7d036058453a2f13c11f6ea 12064 vagrant_1.7.4+dfsg-1.debian.tar.xz 9584144557b1635735dcc704083ab3dbfc2354905d561459c49fc10d33dd95fb 352450 vagrant_1.7.4+dfsg-1_all.deb Files: 87976bbf1c7b720cbbbc87eef18e3b4b 1993 admin optional vagrant_1.7.4+dfsg-1.dsc 016fdb15a49ff7a43b8f301f9dc6c141 537240 admin optional vagrant_1.7.4+dfsg.orig.tar.gz daf023158e107b2e81cd8a0b58ed5b60 12064 admin optional vagrant_1.7.4+dfsg-1.debian.tar.xz fc81b393f520e5e70b76d15deafa8709 352450 admin optional vagrant_1.7.4+dfsg-1_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJV0FYPAAoJEPwNsbvNRgvedzgP/2411RQYNxBfqPmNXt/wQIS1 Yi7VARM7wXpJ7YTZVGEjrTlEEHbQosTLYIdiKe5SuEq/DoSxb3RkCgeO+/jQ/dbN t9yLxYj4tp9ooTKDiHsJCfwCT/Rv6eJDCoxoQCGJqRX4hyA/g4s6bHfWGN3sFyRQ 0Lj6gDdKOSchGIhdOnHfgQdMR3nBTh6VoabmJINqiIZ2jV63/fHDkU1EDN7cMwgV 2G+b1br8ohR2fcGqHdghN3YQ93fucj+wkpzRRKXjXBaLLkB52KwWezjwPXwy50Vv k1VYNJLYc0EU6+37KnCDiY0X/m+tCiJ7JGC6EIH2F01zSjRdvmPwfEZPjbxk7/SA pyMPYoJxXqFq0IfOA88V9+NK/5eQskugeZ4TvcHWjVNyD0hc8WndIHgxbwk1d6/8 Gf/ZUDnOIeDBAgsfemBFw4v7zBXse45sBZcfRamZu6yMBVUY8PLJEtYU4xjfl9ZM KqMkYE3Ox90Tfxp4lrAmu8cQJGqj+YRqJoGPR4E11ytnkLfIzZd9LsN47V/NdItG 1v5VR1dXdSbWXj+O+4rCpEM+o+cijAFk9lgttQbFJp4BsbfhbJci8gglgifxKR7j xePHMjaPdjyknde30bEx4OKwILmcwsZS2ALgni/oVsmcNQ0bCI0NTQhpPLrMCKH7 dWld+yTm7y05smVqotPR =GFuJ -----END PGP SIGNATURE-----
--- End Message ---
