@aristo_4359 thanks for letting us know! You are the first person to inquire about it over very many years :) We'll see if anyone else is interested in this and then we can consider adding it!

Hi @antonio-oliveira_8481 , We have already assessed the vulnerabilities; the container image is not susceptible to any of these vulnerabilities. Only two ports are exposed on the container (for http/https) and the overwhelming majority of packages built-in to the base container image (debian) are not used. Thanks, Steve

Hi @parthu-reddy , That image is not actually hosted on Docker Hub, but in MCR (mcr.microsoft.com). Confusingly, the Docker Hub is now used to "advertise" third-party containers in other registries, in addition to its own. In this case, there are no "tags" published on the docker hub page, so you know it's just an "ad" and not a real image Thanks, Steve

Hi @ashleycanham , This is a fairly complicated issue behind the scene, and is related to how these packages have multiple casings across different versions. This is something that should be addressed with PG-3100. After upgrading, you'll want to re-index the feed. If any packages still have incorrect casing, you can re-upload them to ProGet to correct the names. -- Dean

Hi, We upgraded to 2025.9 after testing in our dev environment and ProGet is now importing PyPi packages from the drop folder Thanks!

Hi @bohdan-cech_2403, ProGet can handle most invalid Maven version numbers, but Borca-SR2 is really invalid and isn't currently supported. Our "name vs version" parsing requires that versions start with numbers, artifacts start with letters. This has been a Maven rule for 20+ years now. It's non trivial and quite risky to change our parsing logic so it's not something we're keen on doing in a maintenance release. This scenario seems to be very rare and impact ancient artifacts and a few cases where authors didn't use Maven to deploy the artifacts. Thanks, Alana

@atripp thanks everything works with inedo/proget:25.0.10-ci.9

@gdivis That was the missing information (wait 30sec AND fetch repodata) - it works as described. To summarize what lead me to incorrectly assume that it was not fixed: My initial expectation was, it would be fixed by merely updating proget After that did not show progress, I found the repodata files in the feed storage path having an old timestamp Then I deleted and re-uploaded the latest rpm and noticed no timestamps change I never tried to actually fetch repodata, because I saw the old timestamps Thanks again for your clarification -Fritz

@felfert Container started by podman run -d --name=proget -v ./proget-packages:/var/proget/packages:z -v ./proget-database:/var/proget/database:z -v ./proget-backups:/var/proget/backups:z -p 8624:80 proget But also tried: podman run -d --network=bridge:ip=<static-ip>,mac=<static-mac> --name=proget -v ./proget-packages:/var/proget/packages:z -v ./proget-database:/var/proget/database:z -v ./proget-backups:/var/proget/backups:z -p 8624:80 proget For now configured with systemd, but also if running the above on the command line I get the same results. Specifying the --hostname proget resolved the issue. podman run -d --hostname=proget --name=proget -v ./proget-packages:/var/proget/packages:z -v ./proget-database:/var/proget/database:z -v ./proget-backups:/var/proget/backups:z -p 8624:80 proget Thanks!

Yes, I do understand that is was user error. Not sure what a good solution for it would be. Showing a dry-run or a confirmation prompt before the deletion might have helped in my case, but that is just annoying when using the tool as intended Or perhaps preventing me from installing it in a "shared" folder is better, if it should always be installed in a new/empty folder anyway?

Hi @pmsensi , Thanks for the heads-up; looks like there was a replication issue with one of our edge nodes. It should be there now Thanks, Alana

Thanks! Just did more investigation to figure out it seems to a be WAF issue.

Thanks @felfert it was an easy add, so look out for PG-3106 in the next maintenance release!

@wechselberg-nisboerge_3629 said in ERROR while migrating maven repository from Jfrog Artifactory.: I am especially confused about the fact that it prints Windows paths, even though it is running as Linux Docker container. That one fooled me previously as well, but if you look carefully, those are source paths from their build-system e.g. C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\...

Hi @parthu-reddy, ProGet 2025 supports existing Maven classic feeds; you should be able to migrate just as you were in ProGet 2024. Thanks, Alana

Hey @splatteredbits , We've only had a single request for a private Chef Supermarket over all these years, and I'm almost certain that was from you My general impression of the market/demand is that Chef has become a "legacy solution" (compared to Docker, K8, etc.), and Progress has no plans to increase its relevance. They appear to be operating in "maintenance mode", and it's kind of like an SVN in a Git world. There's still some activity on recent packages, but it looks like it's just minor version bumps. I could read this wrong... but I don't think it makes sense for us to invest in a declining platform without a lot of user demand. Best, Alex

Hi @splatteredbits , I don't think this would be technically possible, at least from my initial review. Swift has neither "packages" nor "repositories" - the package index is nothing more than a packages.json file that points to other repositories on GitHub. The client clones those repositories and presumably checks-out a tag to get a specific version. Likewise, to "publish" a package to the Swift Package Index, you submit a GitHub issue. So I guess, if you wanted a private Swift repository, you'd just need to make a Git repository and follow those conventions? Cheers, Alex

Thanks for that, I'd put an alphanumeric rather than a hex key in two of my sites. Once I changed them to hex then all started working.

Hi @tyler_5201 , We'll address this via PG-3098 in an upcoming maintenance release; basically we will add a permission check before chown on Docker/Linux for PostgreSQL. If the permissions are there, then chown won't be run. Thanks, Alana

Hi @atripp , thank you for the update. I reverted to 2025.07 and I will wait for the next maintenance release. @power_pille thank you too, for your findings and suggestions.