Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#45862 - [vagrant] 1.7.4-1 fails with error

Attached to Project: Community Packages
Opened by Dmitry Moskowski (corpix) - Saturday, 01 August 2015, 17:13 GMT
Last edited by Jonathan Steel (jsteel) - Thursday, 20 August 2015, 09:56 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jonathan Steel (jsteel)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Vagrant 1.7.4-1 fails with error.
1.7.3-2 also fails, but 1.7.3-1 works fine.

Console log attached.

Steps to reproduce:
Install latest vagrant version and try to run vagrant status, it will fail.
   vagrant.std.log (7.2 KiB)
This task depends upon

Closed by  Jonathan Steel (jsteel)
Thursday, 20 August 2015, 09:56 GMT
Reason for closing:  Works for me
Comment by Jonathan Steel (jsteel) - Sunday, 02 August 2015, 16:14 GMT
Works fine for me. Can you try under a new user account? After 1.7.3-1 the substrate was updated, which might be the reason for seeing some differences, but both should work just fine.
Comment by Dmitry Moskowski (corpix) - Wednesday, 05 August 2015, 22:03 GMT
Have tried 1.7.4-1 under new user, works fine. Thanks for your reply!
Comment by Jonathan Steel (jsteel) - Wednesday, 05 August 2015, 22:14 GMT
I wondered if it could be some environment variable or similar. Hopefully you can narrow down the cause (comparing the differences between your normal user and the new one). I'll leave this open for a week or two in case you can report your solution.

Loading...