Describe the bug
On Windows using a nuget binarycaching source is working out fine (now that the apikey issue was resolved), but now when trying to populate the cache for Linux I'm not able to publish any packages. The error I get is:
Data unprotection failed.
Invalid data.
I see that this is a relatively well-known problem with mono perhaps. Trouble though is that, if I run vcpkg with --debug and just replicate the commands used to cache a package, I'm able to push just fine. If we didn't need to cache like 120 packages then I'd be alright working around this manually... but oh my goodness.
Environment
Expected behavior
I expected my nuget.config to work under Linux exactly as it does on Windows.
Failure logs
-- Performing post-build validation done
[DEBUG] system(/usr/bin/mono /mnt/c/projects/kopernikus/depot/vendor/vcpkg/downloads/tools/nuget-5.5.1-linux/nuget.exe pack /mnt/c/projects/kopernikus/depot/vendor/vcpkg/buildtrees/yaml-cpp/x64-linux.nuspec -OutputDirectory /mnt/c/projects/kopernikus/depot/vendor/vcpkg/buildtrees -NoDefaultExcludes -ForceEnglishOutput -NonInteractive)
Attempting to build package from 'x64-linux.nuspec'.
Successfully created package '/mnt/c/projects/kopernikus/depot/vendor/vcpkg/buildtrees/yaml-cpp_x64-linux.0.6.3-7fe0ff83eca05b4e013193df4d4b6603feee1a0b.nupkg'.
WARNING: NU5103: The folder 'lib/pkgconfig/yaml-cpp.pc' under 'lib' is not recognized as a valid framework name or a supported culture identifier. Rename it to a valid framework name or culture identifier.
WARNING: NU5105: The package version '0.6.3-7fe0ff83eca05b4e013193df4d4b6603feee1a0b' uses SemVer 2.0.0 or components of SemVer 1.0.0 that are not supported on legacy clients. Change the package version to a SemVer 1.0.0 string. If the version contains a release label it must start with a letter. This message can be ignored if the package is not intended for older clients.
WARNING: NU5128: Some target frameworks declared in the dependencies group of the nuspec and the lib/ref folder do not have exact matches in the other location. Consult the list of actions below:
- Add a dependency group for pkgconfig0.0 to the nuspec
[DEBUG] system() returned 0 after 1846708 us
Uploading binaries for yaml-cpp:x64-linux to NuGet source https://nuget.pkg.jetbrains.space/kopernikusauto/p/avp/vcpkg/v2/package.
[DEBUG] system(/usr/bin/mono /mnt/c/projects/kopernikus/depot/vendor/vcpkg/downloads/tools/nuget-5.5.1-linux/nuget.exe push /mnt/c/projects/kopernikus/depot/vendor/vcpkg/buildtrees/yaml-cpp_x64-linux.0.6.3-7fe0ff83eca05b4e013193df4d4b6603feee1a0b.nupkg -ForceEnglishOutput -Source https://nuget.pkg.jetbrains.space/kopernikusauto/p/avp/vcpkg/v2/package -NonInteractive)
Data unprotection failed.
Invalid data.
[DEBUG] system() returned 256 after 891513 us
Pushing NuGet to https://nuget.pkg.jetbrains.space/kopernikusauto/p/avp/vcpkg/v2/package failed. Use --debug for more information.
Building package yaml-cpp[core]:x64-linux... done
Additional context
Worth noting that the default mono-complete packages in Ubuntu 18.04 were unable to even run nuget to check for data, and as a result I couldn't even install packages when specifying the binarysource flag. Only after installing .net core runtime did it start to work.
Describe the bug
On Windows using a nuget binarycaching source is working out fine (now that the apikey issue was resolved), but now when trying to populate the cache for Linux I'm not able to publish any packages. The error I get is:
I see that this is a relatively well-known problem with mono perhaps. Trouble though is that, if I run vcpkg with
--debugand just replicate the commands used to cache a package, I'm able to push just fine. If we didn't need to cache like 120 packages then I'd be alright working around this manually... but oh my goodness.Environment
Expected behavior
I expected my nuget.config to work under Linux exactly as it does on Windows.
Failure logs
Additional context
Worth noting that the default mono-complete packages in Ubuntu 18.04 were unable to even run nuget to check for data, and as a result I couldn't even install packages when specifying the binarysource flag. Only after installing .net core runtime did it start to work.