The AV issues are mostly time related. Once a few users have reported the exe it should be sorted.
Some key details from the log:
There is not enough information about this file to recommend it. This file has been seen by no Symantec users. Symantec has known about this file approximately 2 days.
I re-added the older berrybrew to the path and it worked again so that part is corrected.
I then ran berrybrew upgrade, and now I get this error. I had to revert the changes to the perls.json file in the git repo for it to work (this is not new). I don't imagine this is due to the installer, and is more likely something else in the development process, or how I have things set up.
berrybrew version Unhandled Exception: System.ArgumentException: Item has already been a +dded. Key in dictionary: '5.26.2_64_PDL' Key being added: '5.26.2_64 +_PDL' at System.Collections.Hashtable.Insert(Object key, Object nvalue, B +oolean add) at System.Collections.Specialized.OrderedDictionary.Add(Object key, + Object value) at BerryBrew.Berrybrew.PerlGenerateObjects(Boolean importIntoObject +) at berrybrew.Bbconsole.Main(String[] args)
UPDATE:
I ran a git pull on the repo and the issue has now gone away. The issue was perhaps something to do with berrybrew upgrade and git.
In reply to Re^3: New berrybrew installer; Looking for testers
by swl
in thread New berrybrew installer; Looking for testers
by stevieb
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |