@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.

Hi @parthu-reddy , This behavior is expected; these have a status of "unlisted", which you can see on NuGet.org if you look in the API or type in the URL directly: https://www.nuget.org/packages/System.ComponentModel.Composition/2010.2.11 https://www.nuget.org/packages/System.ComponentModel.Composition/2010.2.11.1 ProGet does not hide unlisted packages by design, but shows them with an unlisted icon instead. Thanks, Alana

Hi @yaakov-smith_7984 , It looks like we forgot to ship the updated extension in 2025.8, so it's not "included" when you install ProGet. You should be able to update under Admin > Extensions, but unless you make the extensions directory (under Admin > Advacned Configuration) mapped to the docker host it will not "survive" a container reboot. We could get you a prerelease container version if you'd like to try it as included, just let us know Thanks, Alana

@misael-esperanzate_5668 thanks for the reproduction details! I was ablet to reproduce this very easily and fixed it via PG-3091 - it was an ordering problem This will be in the upcoming maintenance release this Friday

Hi @caterina, Good catch! We'll get that fix merged in. Thanks, Rich

Oh, that's a shame. We definitely try to cut down on the complexity of what we ask of folk when they deploy this, so that's more friction than is ideal. Thanks for the reply! If any of the reported users see this and have tips and tricks from their experience, I'd love to hear them!

Thank you for the clarification @dean-houston

Hi @yaakov-smith_7984 , We do not have this API, but it's on our roadmap for Q4; it's going to be a set of command like pgutil users or something to that effect. -- Dean