@rhessinger Thank you Rich - will install it once released and confirm it is fixed.

Hi Bohdan, For the feed migration please refer to this: https://inedo.com/support/kb/1168/migrating-a-proget-feed As far as Users/Api Keys.. are you using a Built-In user directory only? Thanks, Jason

Thank you very much for your precision. I realy appreciate it. I personaly work with non conterize Postgres database in order to avoid data corruption issue; but I understand your make this decision. Hava a good day, Mathieu HOFERT

We believe we have fixed this as PG-1377, which will be included in ProGet 5.1.11. Thank you!

Hello Javier, There is an error in the PostgreSQL version of NuGetPackagesV2_GetLatestStable, which was introduced in the 5.0 beta. I've filed this as PG-1164 and submitted a fix for my co-workers to review.

Hi Ben Lubar, The error messages are listed as follows: Add new ADUserDirectory.sql failed: 42601: syntax error at or near "IF" Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object at System.Web.Caching.Cache.ExpireItems (System.Object data) [0x00008] in <d777bf5120224d38839a5bae355ed440>:0 at System.Threading.Timer+Scheduler.TimerCB (System.Object o) [0x00007] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00008] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00074] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <77c9551943624fd18301ba6f78a841e5>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.NullReferenceException: Object reference not set to an instance of an object at System.Web.Caching.Cache.ExpireItems (System.Object data) [0x00008] in <d777bf5120224d38839a5bae355ed440>:0 at System.Threading.Timer+Scheduler.TimerCB (System.Object o) [0x00007] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00008] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00074] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <77c9551943624fd18301ba6f78a841e5>:0 Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object at System.Web.Caching.Cache.ExpireItems (System.Object data) [0x00008] in <d777bf5120224d38839a5bae355ed440>:0 at System.Threading.Timer+Scheduler.TimerCB (System.Object o) [0x00007] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00008] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00074] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <77c9551943624fd18301ba6f78a841e5>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.NullReferenceException: Object reference not set to an instance of an object at System.Web.Caching.Cache.ExpireItems (System.Object data) [0x00008] in <d777bf5120224d38839a5bae355ed440>:0 at System.Threading.Timer+Scheduler.TimerCB (System.Object o) [0x00007] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00008] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00074] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <77c9551943624fd18301ba6f78a841e5>:0 I hope this help.

Regarding the database migration, we don't have an export/import function.. but you can just recreate the feed and use the bulk import path for your exisitng packages.

Hello Matt, It looks like the PostgreSQL version of Feeds_SetLastSyncDate was not updated when the MSSQL version was. I've logged this as PG-1006 and it will be fixed in the next version of ProGet.

Hi Alana, Thank you for the update. I was quite surprised too when realised we can't use case insensitive collation in Postgres. But what if we have 2 columns, one contains data as is, and one contains normalised data, e.g. Login and LoginNormalized. The first one is indexed, the last one is used in queries. But I understand this leads to different schemas in SQL Server and Postgres. I completely agree we can bet on SQL Server, but I don't know its licensing options yet. Posgres is working well from my point of view, except this detail. Since a lot of web applications use Postgres and I haven't heard about case sensitive logins yet, I believe that solution exists. Thank you for all of your hard work on this awesome project!

Thanks for the bug report. This will be fixed in v4.7.2, which should be released today. To upgrade, see the "Upgrading to a new version" section of this KB article: http://inedo.com/support/kb/1100/getting-started-with-proget-for-linux Basically though, when the container starts up it makes sure the database schema version is current, so all you really need to do is run the new container and point to the same data.

Hi Alana, Thanks for the comprehensive answer. Looks like things are still quite away off then. It's a pity mono is not more stable right now, hopefully Microsoft will put in some investment, but it looks like SQL Server is not going to be available until for at least another year.