Hi @atripp:
Thank you for the clarification.
The documentation on this page https://docs.inedo.com/docs/upack-tools-and-libraries-upack-cli should be updated to clarify that you need to either provide the command line arguments or the manifest file, but not both.
-marc
version: upack 3.1.1.0
When I attempt to execute the upack pack command:
upack pack folder/ --version=1.0.1 --manifest=manifest.json --tragetDirectory=packagefolder/
I receive the error:
Invalid upack.json: missing or invalid version
I would like to override the version from the command line. I have tried manifest.json files that omit the version tag or set the version tag to null.
When using a manifest file, can the version be provided on the command line or must it be in the file?
Also, I did try placing the version tag with a value in the manifest file, however, the value in the file is used, not the value on the command line.
Thanks
Hi @atripp. Yes, that worked. Thank you for all the help. -marc
@rhessinger, I have confirmed that the feed has both OData (v2) and JSON-LD (v3) enabled as Supported APIs.
Hi @atripp, unfortunately that doesn't work. When I execute the following from a command shell:
dotnet nuget push mypackage.nupkg --source http://my-internal-server/nuget/InternalLibs/index.json --api-key 1234567890
I receive an error:
error: Unable to load the service index for source http://my-internal-server/nuget/InternalLibs/index.json. error: Response status code does not indicate success: 404 (Not Found).
When I attempt to just navigate via a browser to:
http://my-internal-server/nuget/InternalLibs/index.json
I get this response:
OData method is not implemented.
I also tried running nuget.exe directly from the command line. Same response as dotnet nuget push
-marc
Yes, the feed was enabled to support the standard symbol server on the feed.
Yes, the .snupkg file exists in the same folder as the .nupkg file.
FYI, the only way I have ever gotten this to work was to use a drop folder.
From stepping through the nuget push code, when a push happens, the first step in the process is to pull the feed description document. Then is looks for the @type of SymbolPackagePublish. If that type is not found, a symbol file will not be found.
I have not tracked code back to the specific nuget version this dependency was introduced, I know I started to have issues when using nuget versions from 4.4 to current.
Hi @atripp. My apologies for taking so long to get back to you on this.
I have been doing some testing. Neither
dotnet nuget push or nuget push with the --source <url> doesn't push the symbol file.
I have checked that my feed has been configured to server symbols and is set for Standard format.
After executing the push command, I go to the package details and there is no information for under the symbol tab.
I have checked the feed's folder on the hard drive and I don't see any snupkg files.
I even tried NuGet push mypackage.nupkg -apikey ******** -source http://progetserver/nuget/InternalLibs -symbolapikey ******** -symbolsource http://progetserver/nuget/InternalLibs -verbosity detailed
That also didn't push the symbol file.
I'm currently running ProGet Free ver 2022.26 (Build 6).
Any thoughts as to why this is not working?
-marc
The blog posting on Feb 9th, 2023 about ProGet 2023: What's Coming and When discusses improved NuGet Symbol Support. It points to a preview feature that is currently available in the latest build (2022.26).
I have two questions.
It is my impression that the symbols package will need to be stored in the same feed as the library package. Is that correct?
The posting states that when this feature is enabled, you should use the --symbol option on the dotnet nuget push command.
The dotnet nuget push doesn't have a --symbol option. The only available options are --symbol-api-key and --symbol-source
What is the correct syntax for pushing symbols at the same time as the package?
I remember reading someplace that --symbol-source verifies that the feed description contains the SymbolPackagePublish @type?
Is the correct URL to add to Visual Studio http://server/symbols/feed?
Thank you.
-marc
Renaming the file works. ProGet is still able to server the symbols contained within the file to Visual Studio for debugging.
Thank you for your help.
Please consider this resolved.