Gary Ewan Park
Gary Ewan Park
@TheBigBear apologies on not getting back you to sooner about this! Can I ask if you are still seeing this same problem? This is a new one on me, as...
@vexx32 can you confirm whether this issue has been implemented or not? Based on a PR that you have merged, there is a commit that is tagged against this issue....
Ok, I will get the milestone updated to reflect that this was pulled in.
While it was originally believed that this issue was solved, it turns out that it wasn't. Let me try to explain... In order to push to a source, you need...
Just to follow up on this as well, we are going to remove this from the 2.0.0 milestone, as this isn't something we are going to tackle before release.
This is not a bad idea, and something that I have considered as a solution, but I wasn't convinced by it. Let me try to explain... If we add something...
@Git-North are you using, or have you used, any authenticated Chocolatey repository, where you were required to enter username/password, or certificate/password information? Or are you just using the default Chocolatey...
Okay, thank you for the information. Part of the reason that I wanted to ask that, is due to the fact that it would be good to see the contents/format...
@Git-North please accept my apologies, I misread the stacktrace for the problem that you are having here. The problem is not with the chocolatey.config file, but rather with one of...
> @Git-North said... most commands give the following error: Can you also please confirm which commands you are seeing being impacted by this?