-
Notifications
You must be signed in to change notification settings - Fork 137
Powershell publish-module now failing in 2.1-bionic #575
Comments
@bo67192 The cmdlet is not in the repo, it is in PowerShellGet repository. Please move the issue there. |
@bo67192 thanks for reporting this issue, you mentioned
When this was working what version of dotnet were you using? Thanks! |
Looking closer we agree that it seems like the issue you linked may be the same, curious if you have tried any of the workarounds mentioned in that issue? |
@SydneyhSmith - I agree the linked NuGet issue mentions some potential workarounds, the thing I noticed was that something |
@SydneyhSmith , I had some issues come up at work that made me move away from this work for a while, the last I know it was working was for a team demo on January 14th. I'm looking at the workarounds, but I'm not sure how I would run them. I'm not directly running any msbuild commands, so how could I inject
into the middle of a Appreciate any help you can provide! |
Folks, @MichaelSimons @SydneyhSmith @bo67192 did we have progress on this problem? I spent several days hitting the same problem here - https://github.com/PowerShell/PowerShellGet/issues/584 Still, not clear on the path forward. |
Steps to reproduce the issue
Expected behavior
I would expect it to create a valid nuget package file in
/tmp/localpsrepo/
Actual behavior
I get the error
Additional information (e.g. issue happens only occasionally)
This was working about a week and a half ago, on the same base container.
Output of
docker version
Output of
docker info
I had mentioned this here and @MichaelSimons suggested moving this over here.
He thought it might be related to this Nuget issue
I'm stumped, and I'd really appreciate any help!
The text was updated successfully, but these errors were encountered: