Paket keeps flapping .0 at the end of the package versions #1282

Closed
konste opened this Issue Dec 2, 2015 · 5 comments

Comments

Projects
None yet
2 participants
@konste
Contributor

konste commented Dec 2, 2015

It looks like Paket randomly (?) adds or removes ".0" at the end of the package version every time the version changes. For instance, looking at the history of the paket.lock file I can see these changes:

Costura.Fody (1.3.3) -> Costura.Fody (1.3.3.0)
Costura.Fody (1.3.3.0) -> Costura.Fody (1.3.3)
Costura.Fody (1.3.3) -> Costura.Fody (1.3.3.0)
Costura.Fody (1.3.3.0) -> Costura.Fody (1.3.3)
... ... ...

It does not happen for all packages, but for many, for instance:
Microsoft.Web.Infrastructure, PagedList, JSNLog, IKVM, MimeKit, etc.

@forki

This comment has been minimized.

Show comment
Hide comment
@forki

forki Dec 2, 2015

Member

Mhm this seems to be related to which protocol responds the fastest. I will
try to find a solution.
On Dec 2, 2015 22:01, "Konstantin Erman" notifications@github.com wrote:

It looks like Paket randomly (?) adds or removes ".0" at the end of the
package version every time the version changes. For instance, looking at
the history of the paket.lock file I can see these changes:

Costura.Fody (1.3.3) -> Costura.Fody (1.3.3.0)
Costura.Fody (1.3.3.0) -> Costura.Fody (1.3.3)
Costura.Fody (1.3.3) -> Costura.Fody (1.3.3.0)
Costura.Fody (1.3.3.0) -> Costura.Fody (1.3.3)
... ... ...

It does not happen for all packages, but for many, for instance:
Microsoft.Web.Infrastructure, PagedList, JSNLog, IKVM, MimeKit, etc.


Reply to this email directly or view it on GitHub
#1282.

Member

forki commented Dec 2, 2015

Mhm this seems to be related to which protocol responds the fastest. I will
try to find a solution.
On Dec 2, 2015 22:01, "Konstantin Erman" notifications@github.com wrote:

It looks like Paket randomly (?) adds or removes ".0" at the end of the
package version every time the version changes. For instance, looking at
the history of the paket.lock file I can see these changes:

Costura.Fody (1.3.3) -> Costura.Fody (1.3.3.0)
Costura.Fody (1.3.3.0) -> Costura.Fody (1.3.3)
Costura.Fody (1.3.3) -> Costura.Fody (1.3.3.0)
Costura.Fody (1.3.3.0) -> Costura.Fody (1.3.3)
... ... ...

It does not happen for all packages, but for many, for instance:
Microsoft.Web.Infrastructure, PagedList, JSNLog, IKVM, MimeKit, etc.


Reply to this email directly or view it on GitHub
#1282.

@forki

This comment has been minimized.

Show comment
Hide comment
@forki

forki Dec 3, 2015

Member

is this only with nuget.org?

Member

forki commented Dec 3, 2015

is this only with nuget.org?

@forki forki closed this in 763457e Dec 3, 2015

@forki

This comment has been minimized.

Show comment
Hide comment
@forki

forki Dec 3, 2015

Member

please check if this works for you. we only do this for nuget.org since other servers fail on NormalizedVersions

Member

forki commented Dec 3, 2015

please check if this works for you. we only do this for nuget.org since other servers fail on NormalizedVersions

@konste

This comment has been minimized.

Show comment
Hide comment
@konste

konste Dec 3, 2015

Contributor

It will take some time to make sure it is fixed as the problem was intermittent by nature.

Contributor

konste commented Dec 3, 2015

It will take some time to make sure it is fixed as the problem was intermittent by nature.

@forki

This comment has been minimized.

Show comment
Hide comment
@forki

forki Dec 3, 2015

Member

yes I know....

Member

forki commented Dec 3, 2015

yes I know....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment