dub.json contains package in "dependencies" with ~>1.2.3 version. And it is available 1.2.4 version of this package.
Why dub isn't downloads version 1.2.4 and uses 1.2.3 before build? "dub upgrade" isn't solves this problem.
dub.json contains package in "dependencies" with ~>1.2.3 version. And it is available 1.2.4 version of this package.
Why dub isn't downloads version 1.2.4 and uses 1.2.3 before build? "dub upgrade" isn't solves this problem.
Am 04.05.2015 um 08:41 schrieb pdbr:
dub.json contains package in "dependencies" with ~>1.2.3 version. And it is available 1.2.4 version of this package.
Why dub isn't downloads version 1.2.4 and uses 1.2.3 before build? "dub upgrade" isn't solves this problem.
Try to run dub clean-caches
. dub upgrade
currently uses cached
information and in turn it can take a while before it picks up new
versions. We intend to change that behavior, though.
On Mon, 04 May 2015 10:18:10 +0200, Sönke Ludwig wrote:
Am 04.05.2015 um 08:41 schrieb pdbr:
dub.json contains package in "dependencies" with ~>1.2.3 version. And it is available 1.2.4 version of this package.
Why dub isn't downloads version 1.2.4 and uses 1.2.3 before build? "dub upgrade" isn't solves this problem.
Try to run
dub clean-caches
.dub upgrade
currently uses cached
information and in turn it can take a while before it picks up new
versions. We intend to change that behavior, though.
Thanks!
On Mon, 04 May 2015 10:18:10 +0200, Sönke Ludwig wrote:
Am 04.05.2015 um 08:41 schrieb pdbr:
dub.json contains package in "dependencies" with ~>1.2.3 version. And it is available 1.2.4 version of this package.
Why dub isn't downloads version 1.2.4 and uses 1.2.3 before build? "dub upgrade" isn't solves this problem.
Try to run
dub clean-caches
.dub upgrade
currently uses cached
information and in turn it can take a while before it picks up new
versions. We intend to change that behavior, though.
I am checked this on clean cloned package and it is reproduced: dub used v1.2.3 package for build, but 1.2.4 was available at github (but not listed at code.dlang.org)
Am 05.05.2015 um 23:42 schrieb pdbr:
On Mon, 04 May 2015 10:18:10 +0200, Sönke Ludwig wrote:
Am 04.05.2015 um 08:41 schrieb pdbr:
dub.json contains package in "dependencies" with ~>1.2.3 version. And it is available 1.2.4 version of this package.
Why dub isn't downloads version 1.2.4 and uses 1.2.3 before build? "dub upgrade" isn't solves this problem.
Try to run
dub clean-caches
.dub upgrade
currently uses cached
information and in turn it can take a while before it picks up new
versions. We intend to change that behavior, though.I am checked this on clean cloned package and it is reproduced: dub used v1.2.3 package for build, but 1.2.4 was available at github (but not listed at code.dlang.org)
Ah OK, that's a different issue. This usually means that there is some
kind of error with the package for the v1.2.4 tag, such as syntax errors
in dub.json or similar. The package owner has a list of errors when
logged in on code.dlang.org.
In this case, it looks like the issue is already gone now? The only
package with version 1.2.3 seems to be "dproto", which is now at 1.2.4.
On Wed, 06 May 2015 17:41:08 +0200, Sönke Ludwig wrote:
Am 05.05.2015 um 23:42 schrieb pdbr:
On Mon, 04 May 2015 10:18:10 +0200, Sönke Ludwig wrote:
Am 04.05.2015 um 08:41 schrieb pdbr:
dub.json contains package in "dependencies" with ~>1.2.3 version. And it is available 1.2.4 version of this package.
Why dub isn't downloads version 1.2.4 and uses 1.2.3 before build? "dub upgrade" isn't solves this problem.
Try to run
dub clean-caches
.dub upgrade
currently uses cached
information and in turn it can take a while before it picks up new
versions. We intend to change that behavior, though.I am checked this on clean cloned package and it is reproduced: dub used v1.2.3 package for build, but 1.2.4 was available at github (but not listed at code.dlang.org)
Ah OK, that's a different issue. This usually means that there is some
kind of error with the package for the v1.2.4 tag, such as syntax errors
in dub.json or similar. The package owner has a list of errors when
logged in on code.dlang.org.In this case, it looks like the issue is already gone now?
Yes!
The only
package with version 1.2.3 seems to be "dproto", which is now at 1.2.4.
Yeh! yes, surely.
Thanks for explanation!