Posts made by gdivis

This is now fixed as of Inedo Hub 1.0.23.

Hi @markcodyre_7146 - we now have a prerelease version of ProGet available with support for RPM feeds. It is currently lacking support for connectors, replication, and GPG keys but otherwise is ready for testing if you'd like. It’s available now via InedoHub as ProGet 5.2.25-redline.1.

Hi,

Thanks for letting us know. Looks like the error message is wrong - actually the problem is caused by build metadata being present in a version number that is not a semver2 version.

We've filed this as PG-1655 to make parsing these versions more permissive - it will be fixed in the next ProGet release (5.2.23), currently scheduled for Jan-17.

It looks like this was caused by a change in our internal deployment process. I've logged this as PG-1615, and it will be fixed in ProGet 5.2.14, which is scheduled for release on Friday (October 18).

Thanks for the report!

We've now reproduced this, and it turns out there's a regression in 5.2.13 with how config files are read which determine whether to use SQL Server or postgres. We have implemented a fix as PG-1614, which will be included in ProGet 5.2.14 (scheduled for release on Friday, October 18).

For now, I'd recommend just reverting to 5.2.12 until the next version is available.

Thanks to all who reported this!

Just a quick update- I realized our upgrade instructions are wrong. If you're using SQL Server, you'll need to specify the database type and the connection string with the docker run command: (see the updated instructions here: https://docs.inedo.com/docs/proget/installation/installation-guide/linux-docker)

Hi,

I've tried to reproduce this in a few different ways, but it seems to work for me. What are the exact arguments you're passing to docker run?

Hi Martin,

This will be included in this Friday's (Aug 23) release (5.2.9).