New Post: Removing the version parameter from the packages.config file does not work

Hi,

When installing a package or bunch of packages into a project, a packages.config file is being created and a new line for each package is being created in it. One of the parameters in this line is the "version" parameter.
Now let's say there's a certain initial version number for this parameter and whenever a newer package is being installed, the value of this parameter will be changed to the new version number. If one developer has updated this package two days ago, and another developer is updating this package today to a newer version than the other developer, commiting will cause a conflict. It is a never ending story.
Not commiting the packages.config will cause NuGet to fail when the initial version of the package will not exist anymore in the NuGet server (Is it a bug? Works as designed?)
Whan we have tried to do is to commit only one version of packages.config when the version parameter's value is empty but it does not work.

Am I missing something? What is the preferred way to work with the packages.config files?

Thanks
Gil