@kc_2466 Yeah I do press the Delete Package button as well, I highlighted that other button because it's the toggle button

Hi @rhessinger, thank you for pointing out the feed features. License detection was not enabled in the feed I used for testing. After activating the feature the package is being reanalyzed correctly and the global policy is being used. Thanks Caterina

Hi @kc_2466 , We'll Add support for LC_TIME environment variable & user setting via PG-3054 in an upcoming maintenance release -- p[robably not this week's, but in the next or following. Thanks, Alana

Hey @atripp, Thanks for the update! We've got a lot of customers moving from Sonatype to Inedo. How many of those will use connectors is unknown. Thanks for linking to your internal issue for this. We can provide that to customers so they can see the status of the fix.

Hi @kc_2466 , We'll get this fixed via PG-3050 as well; the button should be shown to non-admins -- Dean

Hi @kc_2466 , Those should not be displayed to non-feed admins; we'll clear that up with PG-3050 in the next maintenance release. In the meantime, I suppose you could just click the "X" for them ;) -- Dean

@erich_1530 in the ProGet software, you will see a "License REquired" error message. if you click on the "Request License Key" you can get a Free or Trial key from within ProGet. Or you can go to my.inedo.com and request a key from there if your server does not have internet access

@stevedennis Nice one, thanks for all your help

Hi @james-woods_8996 , No problem using ProGet 2025 Docker Image with SQL Server - it works exactly as it did in ProGet 2024. We will continue to support SQL Server in the through at least ProGet 2026. Thanks, Steve

Hi @mmaharjan_0067 , We'll investigate and see about adding this via PG-3035; it's probably returning some unexpected status. Will update if we run into trouble! -- Dean

@mmaharjan_0067 we'll try to do this via PG-3034 as well

Hi @v-makkenze_6348 , We'll get this fixed via PG-3041 in the upcoming maintenance release; you can try out the prerelease container if you'd like (proget:25.0.4-ci.1), which is building now. -- Dean

I finally had a chance to try out ProGet 2024.39 and can confirm that the package metadata now contains the bin key. Thanks again! – Matthias

Thank you @stevedennis, this makes sense. One odd thing is that I noted that when I had set metadatacache=true using pgutil, the time the WebUI showed Loading Packages.... and the time it took to do sudo apt update in clients went from long to super long. It went back to long when I set metadatacache=false again. I don't know if there is a logical explanation for this or of it was just a coincidence. Br, Stefan

Unfortunately we cannot share our scripts due to intellectual property rights. The hint I can give though is to note the format of the index.json in the public dist and maintain that in your private dist.

Hi @c4buildmasters_2588 Short answer yes, and you'd probably see a bit better than 15 -> 5 TB reductions with those artifacts. We usually see 90-95% storage space reduction. Pair it with ProGet's retention rules and I wouldn't be surprised to see that drop to 500GB. Long answer, file deduplication is something you want handled by the operating system (e.g. Windows Data Deduplication, RHEL VDO, etc), not the application. It's way too complex -- you have to routinely index a fileset, centralize chunks in a compressed store, and then rebuild those files with reparse points. Maybe this wasn't the case a couple decades ago. But these days, rolling your own file deduplication would be like implementing your own hacky encryption or compression. Pointless and a bad idea. That being said, you may be using a tool by our friends at JFrog. They advertise a feature called "data deduplication", which IMHO is something between deceptive and a clever marketing flex. Because they store files by their hash instead of file names, the files are automatically "deduplicated"... so long as it's the exact same contents. Which, in most case, it will not be. Here’s an article that digs into how things are stored in Artifactory, and also should give you an idea of their “file-based” approach: https://blog.inedo.com/proget-migration/how-files-and-packages-work-in-proget-for-artifactory-users/ As for the package count, 5M is obviously a lot of packages. Obviously it's not going to be as fast as 5 packages - but probably not that much noticeably slower. There's lots of database indexes, etc. Hope that helps. -- Dean

@stevedennis By default the command operate in the local cache, but with the -r=remote argument it removes artifacts from the server. Ref: https://docs.conan.io/2/reference/commands/remove.html

Hi @stevedennis, thank you. I contemplated the idea store the fingerprint in another location (and doing so at a point in time when I'm convinced things are not compromised), and then, when a new host is to subscribe to the ProGet feed, compare the calculated fingerprint of the ProGet provided key with the one obtained from the other store. If they do not match I know one of them have been tampered with. But maybe I'm going overboard, and I still can do it by downloading the key to the second location and calculating the fingerprint there if I really want to, so things are fine. Thank you again, Stefan