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

Nice idea! That was pretty trivial to add in there, and will be in the next maintenance release via PG-3038: [image: 1751500114153-0862e122-a88d-49ef-ad76-204f40afaec5-image.png]

Hi @michal-roszak_0767 , That looks like it's just a "web page" with a bunch of links to files? ProGet does not support connecting to "web pages" and we have no plans to add that feature. There's simply no API to use, which users could never be able to "see" the files in ProGet until after they've been downloaded -- and the lack of metadata also creates all sorts of other complexities. However, you can create an asset directory to store "generic" files. It's basically a web-based file system: https://docs.inedo.com/docs/proget/asset-directories-file-storage/what-is-an-asset-directory Thanks, Steve

@mmaharjan_0067 we'll see how we can improve this while we work on PG-3034

Hi @mmaharjan_0067 , This is definitely some kind of UI regression; we did a lot of code-cleanup / refactoring on the front-end pages. We'll get this fixed via PG-3034 in an upcoming maintenance release (targeting next week's 2025.4). Thanks, Steve

@stevedennis The backup job in proget:25.0.3-ci.3 works as expected, thank you!

Hi Steve, thank you! I will try badssl.com out and see how ProGet reacts. Thank you again, Stefan

That's the intended/expected behavior of repackage. The use case is CI/CD workflows, so you would do something like: Create w.x.y-ci.z Repackage to w.x.y-rc.z Repackage to w.x.y Retention policies would then clear out old -ci and -rc packages. I believe that display bug has been fixed in ProGet 2025; I remember seeing it listed as a bug discovered during testing. But in any case, it's in the package history as you can see.

Hi @mmaharjan_0067, This is not a trivial request and would require database changes, new API endpoints, and of course pgutil changes. We will put it on our ProGet 2026 roadmap for future consideration -- hopefully some other users will chime in! UPDATE (2026-May-14); this did not make our ProGet 2026 release (it's a fairly complicated/involved change), and we've decided to wait for other users to let us know if they'd like this or similar API changes. Thanks, Steve

Hi @michal-roszak_0767 , You can just click "edit" on an API Key in the UI to change the date or secret value. However, if you have "Cryptographic hashing" enabled, then you will need to delete the key and recreate it to change the value. Thanks, Steve

Hi, @rhessinger! Thank you for looking into this. I will do some retesting as soon as the 2025.2 is released. Thanks, Petter

Hi @mwatt_5816, Thanks for all of the detail. I have fixed the code, BM-3982, for this template and it will be released in the next maintenance of BuildMaster 2024.0.7 on Friday. Thanks, Rich

Hi @parthu-reddy , These indicate that your network stack is being overloaded. npm can do this, as it's sending thousands of simultaneous requests to your server. Each of these requests require multiple database connections (network) and requests to remote registries (network). If you're using load balancing, you'll want to tweak the configuration to do rate limiting. For example, in npm it's this: https://blog.nginx.org/blog/rate-limiting-nginx Hope that helps, Steve