Hi @m-karing_2439 , The link on the "Dependencies" is provided for convenience; it's simply wrapping a <a href=... around items in the .nuspec file's Dependencies element. Without performing expensive lookups, there is no way to know if those packages are in the current feed, or if they're even valid packages or versions at all. Keep in mind that, in many cases, dependencies won't even reference a single package (e.g. MyPackage-4.8.7) - but a whole range of versions (e.g. MyPackage-4.*). This is why it's impossible for ProGet (or any tool) to "resolve" the dependencies - it requires knowing all packages in project (plus the project's environmental configuration) to know which ranges to pick. Note that, if those links yield a 404 then clients will also not be able to download them from thet feed. Thanks, Steve

Hi @inedo_1308, I have just published a new CI build that should fix your issue. If you upgrade your Docker container to ProGet 25.0.8-ci.3, that should fix the problem with your feed usage instructions. Thanks, Rich

@james-woods_8996 good to know - I've just removed that from the docs since I think that was an instruction from earlier versions (before ProGet 2022 maybe)

Hi @layfield_8963, I'm having trouble recreating this error. I just stood up a clean install of ProGet 2025.7, created an asset directory, and uploaded a file to it. I then ran the command you sent and this is what I see: pgutil.exe assets metadata set custom --path=test.txt --feed=test-import-data --key=test123 --value=12345 Setting test123 = 12345 on test.txt... Metadata set. Can you please navigate to Administration -> Software Info and copy and paste the contents of that here? If you feel more comfortable, you can email it to support@inedo.com with the subject [QA-2790] Database Information. If you email it, please let us know when you do so we can look for it in that mailbox. The only thing I can think of is that your database schema did not update properly on upgrade. Thanks, Rich

Thank you for the feedback. I will observe for a while and reserve yelling at people to close their browsers for later. ;)

Hi @koksime-yap_5909 , This is the "Feed Overview" page and the URL that you need: Thanks, Steve

@kc_2466 thanks for the suggestions, we'll also get this in a future maintenance release via PG-3067 ... should be trivial!

Hi @kc_2466 , Thanks! We'll add this via PG-3066 in an upcoming maintenance release, hopefully later this week if it's as trivial as it seems :) Thanks, Steve

@tames_0545 thanks for letting us know, we'll get this fixed right away via PG-3065 in the next maintenance release

@apxltd Lol, fair enough. I know MS is busy trying to get everyone on the cloud and destroying on prem. Not sure how well that's going for them. Well, let's watch and see what winget does. Maybe it will take off.

Thank you @stevedennis! It works!

Hi @koksime-yap_5909 , This is a known issue and will be fixed via PG-3063 in teh next maintenance release, shipping later today. Thanks, Steve

Hi @koksime-yap_5909 , That's just a "suggestion box" in the UI - you can just type in whatever you'd like. But in general you shouldn't upload files via the UI, but using maven. Thanks, Steve

Hi @koksime-yap_5909, No; when you use LDAP, then you need to manage the LDAP users' groups in your directory. Here is a recent discussion on the topic: https://forums.inedo.com/topic/5471/feature-suggestion-allow-ad-users-to-be-added-to-built-in-groups Thanks, Steve

Hi @patrick-tessier_4584 FYI, dotnet nuget and nuget.exe are effectively the same thing - they both invoke the NuGet CL.. The nuget.exe is a standalone version of the CLI and dotnet nuget is part of the .NET SDK. The issue is that your copy of nuget.exe was ancient and didn't work. Cheers, Steve

Hi @kc_2466 , Thanks for the report; we'll get this fixed in the next maintenance release (this week) via PG-3064 Thanks, Steve

Hi @misael-esperanzate_5668 , That makes perfect sense; when package caching is enabled, the package files are added to the feed and stored on disk. When it's not enabled, they are simply streamed from the server. Something is interfering with your disk storage that is deleting (quarantining) files on disk. You will need to follow the troubleshooting I identified above - it's probably a security tool. Suggest using AWS Lightsail to get a test box in an environment you can control. Thanks, Steve

@dean-houston Thanks Dean, looks like it worked. I guess I am still a new user too!

Hi @misael-esperanzate_5668 , Although ProGet can handle invalid version numbers for Maven packages, this one is a extra invalid version number (it starts with a "v") and unfortunately we can't support them at this time. ProGet requires that packages follow the ~20 year Maven standard that "packages start with a letter and versions start with a number". Sadly this team didn't like those standards and opted to do their own thing. The issue comes with identifying whether com/google/apis/google-api-services-healthcare/v1-rev20240731-2.0.0 is an artifact or a version. Because ProGet is not a basic file server, things like package names and versions matter. Anyway this will require a significant and risky change to the API so we won't consider it at least for another major release. -- Dean