RejectedSoftware Forums

Sign up

biggest common denominator for dependancy version

I have a problem: My closed source server yet again depends on changes in vibe-d ~master HEAD. My other open source libs like sockjs-d or gcm-d do not require this. so I would like to keep the version set to >=0.7.18 there since this is the current stable release. But, even though ~master of vibe.d would be the common denominator here dub rejects this:

There are conflicts in the dependency graph.
The dependency graph could not be filled, there are conflicts.
The following changes will be performed:
Conflict vibe-d >=~master, userWide
Issued by:
 s4server: ~master
 sockjs-d: >=0.7.18
 gcm-d: >=0.7.18
 s4db: >=0.7.18
Error executing command run: Unknown dependency: sockjs-d

what can i do ?

Re: biggest common denominator for dependancy version

Am 09.02.2014 19:46, schrieb Stephan Dilly:

I have a problem: My closed source server yet again depends on changes in vibe-d ~master HEAD. My other open source libs like sockjs-d or gcm-d do not require this. so I would like to keep the version set to >=0.7.18 there since this is the current stable release. But, even though ~master of vibe.d would be the common denominator here dub rejects this:

There are conflicts in the dependency graph.
The dependency graph could not be filled, there are conflicts.
The following changes will be performed:
Conflict vibe-d >=~master, userWide
Issued by:
  s4server: ~master
  sockjs-d: >=0.7.18
  gcm-d: >=0.7.18
  s4db: >=0.7.18
Error executing command run: Unknown dependency: sockjs-d

what can i do ?

I'll make a new beta tag for vibe.d after finalizing the SSL cert.
verification API (still tonight or tomorrow morning). DUB will be able
to manage this in 0.9.22.

Re: biggest common denominator for dependancy version

On Mon, 10 Feb 2014 21:45:02 +0100, Sönke Ludwig wrote:

Am 09.02.2014 19:46, schrieb Stephan Dilly:

I have a problem: My closed source server yet again depends on changes in vibe-d ~master HEAD. My other open source libs like sockjs-d or gcm-d do not require this. so I would like to keep the version set to >=0.7.18 there since this is the current stable release. But, even though ~master of vibe.d would be the common denominator here dub rejects this:

There are conflicts in the dependency graph.
The dependency graph could not be filled, there are conflicts.
The following changes will be performed:
Conflict vibe-d >=~master, userWide
Issued by:
  s4server: ~master
  sockjs-d: >=0.7.18
  gcm-d: >=0.7.18
  s4db: >=0.7.18
Error executing command run: Unknown dependency: sockjs-d

what can i do ?

I'll make a new beta tag for vibe.d after finalizing the SSL cert.
verification API (still tonight or tomorrow morning). DUB will be able
to manage this in 0.9.22.

So with a specific version tag like >=foobar1.2.3-beta this problem should be gone too? did not know that! Thank you!

Re: biggest common denominator for dependancy version

Am 10.02.2014 21:51, schrieb Stephan Dilly:

On Mon, 10 Feb 2014 21:45:02 +0100, Sönke Ludwig wrote:

Am 09.02.2014 19:46, schrieb Stephan Dilly:

I have a problem: My closed source server yet again depends on changes in vibe-d ~master HEAD. My other open source libs like sockjs-d or gcm-d do not require this. so I would like to keep the version set to >=0.7.18 there since this is the current stable release. But, even though ~master of vibe.d would be the common denominator here dub rejects this:

There are conflicts in the dependency graph.
The dependency graph could not be filled, there are conflicts.
The following changes will be performed:
Conflict vibe-d >=~master, userWide
Issued by:
   s4server: ~master
   sockjs-d: >=0.7.18
   gcm-d: >=0.7.18
   s4db: >=0.7.18
Error executing command run: Unknown dependency: sockjs-d

what can i do ?

I'll make a new beta tag for vibe.d after finalizing the SSL cert.
verification API (still tonight or tomorrow morning). DUB will be able
to manage this in 0.9.22.

So with a specific version tag like >=foobar1.2.3-beta this problem should be gone too? did not know that! Thank you!

Yes, that should do the trick. New v0.7.19-beta.3 is tagged now, too.

Re: biggest common denominator for dependancy version

On Tue, 11 Feb 2014 10:55:46 +0100, Sönke Ludwig wrote:

Am 10.02.2014 21:51, schrieb Stephan Dilly:

On Mon, 10 Feb 2014 21:45:02 +0100, Sönke Ludwig wrote:

Am 09.02.2014 19:46, schrieb Stephan Dilly:

I have a problem: My closed source server yet again depends on changes in vibe-d ~master HEAD. My other open source libs like sockjs-d or gcm-d do not require this. so I would like to keep the version set to >=0.7.18 there since this is the current stable release. But, even though ~master of vibe.d would be the common denominator here dub rejects this:

There are conflicts in the dependency graph.
The dependency graph could not be filled, there are conflicts.
The following changes will be performed:
Conflict vibe-d >=~master, userWide
Issued by:
   s4server: ~master
   sockjs-d: >=0.7.18
   gcm-d: >=0.7.18
   s4db: >=0.7.18
Error executing command run: Unknown dependency: sockjs-d

what can i do ?

I'll make a new beta tag for vibe.d after finalizing the SSL cert.
verification API (still tonight or tomorrow morning). DUB will be able
to manage this in 0.9.22.

So with a specific version tag like >=foobar1.2.3-beta this problem should be gone too? did not know that! Thank you!

Yes, that should do the trick. New v0.7.19-beta.3 is tagged now, too.

Will try and come back at you (heut nachmittag ^^)

Re: biggest common denominator for dependancy version

On Tue, 11 Feb 2014 10:55:46 +0100, Sönke Ludwig wrote:

Am 10.02.2014 21:51, schrieb Stephan Dilly:

On Mon, 10 Feb 2014 21:45:02 +0100, Sönke Ludwig wrote:

Am 09.02.2014 19:46, schrieb Stephan Dilly:

I have a problem: My closed source server yet again depends on changes in vibe-d ~master HEAD. My other open source libs like sockjs-d or gcm-d do not require this. so I would like to keep the version set to >=0.7.18 there since this is the current stable release. But, even though ~master of vibe.d would be the common denominator here dub rejects this:

There are conflicts in the dependency graph.
The dependency graph could not be filled, there are conflicts.
The following changes will be performed:
Conflict vibe-d >=~master, userWide
Issued by:
   s4server: ~master
   sockjs-d: >=0.7.18
   gcm-d: >=0.7.18
   s4db: >=0.7.18
Error executing command run: Unknown dependency: sockjs-d

what can i do ?

I'll make a new beta tag for vibe.d after finalizing the SSL cert.
verification API (still tonight or tomorrow morning). DUB will be able
to manage this in 0.9.22.

So with a specific version tag like >=foobar1.2.3-beta this problem should be gone too? did not know that! Thank you!

Yes, that should do the trick. New v0.7.19-beta.3 is tagged now, too.

Well it seems like it would work, but the Assert described here: http://forum.rejectedsoftware.com/groups/rejectedsoftware.dub/thread/965/?page=3 keeps me from knowing for sure... right now it won't compile at all ;(