Hi, Thanks for letting us know. Looks like the error message is wrong - actually the problem is caused by build metadata being present in a version number that is not a semver2 version. We've filed this as PG-1655 to make parsing these versions more permissive - it will be fixed in the next ProGet release (5.2.23), currently scheduled for Jan-17.

Hello @luminiscence_6236, It looks like ProGet is misinterpreting the auth token request helm sends during the second command as being anonymous. I've filed PG-1651 to address this.

Hello; this will probably be the fastest route to fix things -- https://docs.inedo.com/docs/desktophub/troubleshooting

@atripp Thanks for the clarification, you have me pointed to the tooling and steps I will need to perform the bulk import. I will have to try, but I think I have enough information to script this task.

You should have access now! Let me know if not :)

Great news, Alana! Thanks.

Thanks a lot, I confirm it's working now with v5.2.9

Hello, Sorry for the confusion. For your solution you would need two separate feeds. One for normal package, one for symbols. Thanks, Jason

Hi Chris, You'll need to run the NuGetPackagesV2_SetListed method instead. In order to this, you'll need to mark it as non-internal; this can be done with a simple database query... UPDATE [__StoredProcInfo] SET [Internal_Indicator] = 'N' WHERE [StoredProc_Name] = 'NuGetPackagesV2_SetListed' This will be also be updated in 5.2.10 as PG-1549.

Hello, I think what you are trying to do can be accomplished by adding a restriction for "View & Download Packages" to "any" feed for "Authenticated" users. Then add whatever permission to the API user. Use the Test Privileges button to verify. Thanks Jason

Hi Gordon, Looking at the code, it should work if the ReleaseNotes element is within PackageManifest under Metadata. This would be the schema we use: https://docs.microsoft.com/en-us/visualstudio/extensibility/vsix-extension-schema-2-0-reference?view=vs-2019 Thanks, Jason

Thanks very much for the clarification

Hi Jared, According to the docs - It’s currently not possible to mirror another private registry. Only the central Hub can be mirrored. However, we do support connectors to another repository and are nearing completion on a project for docker replication between ProGet instances. Thanks, Jason

Hi Bohdan, For the feed migration please refer to this: https://inedo.com/support/kb/1168/migrating-a-proget-feed As far as Users/Api Keys.. are you using a Built-In user directory only? Thanks, Jason

ProGet does not have the concept of "public" or "private" feeds, you can instead grant the "Anonymous" user certain permissions, including viewing and publishing packages. ProGet Free Edition does not allow feed-level permissions, only system-level permissions. So you can grant "Anonymous" whatever rights you want, just not at a feed-level.

Hi Jared, I am glad it is fixed. I will make a note of how you were able to get it resolved! If you notice anything else, let us know. Thanks, Jason

Hi Larry, Please refer to this documentation for a list of the ProGet license restrictions.

Hello, This documentation may help you determine the best approach for your solution: https://inedo.com/support/documentation/proget/feeds/nuget#nuget Please let me know if you have additional questions. Thanks, Jason

Hi Eyal, What version of ProGet are you using? This was a known issue that should have been fixed in version 5.1 Let me know if this is not that case. Thanks! Jason

Brent, This our public Q&A forum, which is used for software technical support; as such, I've edited your message to remove your company and contact information. That said, we help organizations with compliance-related questionnaires on our products all the time, both sales and post-sales. Please reach out to your Inedo account manager or use our contact form, and send whatever security compliance forms/documentation you are trying to fill out, and we will do our best to advise and help.