RejectedSoftware Forums

Am 24.05.2014 20:29, schrieb Nick Sabalausky:

After about a day and several "Trigger manual update", code.dlang.org
still hasn't picked up this tag:

https://github.com/Abscissa/DAuth/releases/tag/v0.6

Does it need to be v0.6.0 or is something else wrong?

Exactly, versions must always have 3 digits (standard SemVer format). I
didn't really think about the consequences of supporting more or less
than that, so for now it's kept all according to the standard.

Am 08.06.2014 02:13, schrieb Joseph Rushton Wakeling:

On Sat, 24 May 2014 21:00:37 +0200, Sönke Ludwig wrote:

Am 24.05.2014 20:29, schrieb Nick Sabalausky:

After about a day and several "Trigger manual update", code.dlang.org
still hasn't picked up this tag:

https://github.com/Abscissa/DAuth/releases/tag/v0.6

Does it need to be v0.6.0 or is something else wrong?

Exactly, versions must always have 3 digits (standard SemVer format). I
didn't really think about the consequences of supporting more or less
than that, so for now it's kept all according to the standard.

Assuming that a version has 3 digits, is it acceptable to append -rc1, -alpha, etc.?

I tried (experimentally) setting the version of a package I'm preparing to "1.0.0-rc1". This worked fine as a dependency if the dependent package asked for ">=0.9.0" (say) but if I asked for ">=1.0.0-rc1" I got an error message with dub build:

 Error executing command build: Could not find a valid dependency tree configuration:

That should work in theory. The usual form would be to use "1.0.0-rc.1"
with a dot in the last part, so that the number part at the end is
sorted numerically instead of alphabetically, but that can't be the
reason for the error.

Does it output any detail messages after the main error message? It
sounds like either it doesn't find the 1.0.0-rc1, or that some other
dependency in the dependency graph has a dependency on the package with
<1.0.0, so that there is a conflict.

BTW, which DUB version is this? beta 2 or GIT master? There has been
quite a number of issues in beta 2 and I just want to fix one more
before releasing a third beta.

Am 08.06.2014 11:52, schrieb Joseph Rushton Wakeling:

On Sun, 08 Jun 2014 10:10:00 +0200, Sönke Ludwig wrote:

Am 08.06.2014 02:13, schrieb Joseph Rushton Wakeling:

I tried (experimentally) setting the version of a package I'm preparing to "1.0.0-rc1". This worked fine as a dependency if the dependent package asked for ">=0.9.0" (say) but if I asked for ">=1.0.0-rc1" I got an error message with dub build:

  Error executing command build: Could not find a valid dependency tree configuration:

That should work in theory. The usual form would be to use "1.0.0-rc.1"
with a dot in the last part, so that the number part at the end is
sorted numerically instead of alphabetically, but that can't be the
reason for the error.

I think that it may have been as simple and stupid that I forgot the "1" after the rc, with or without the dot -- in the dependency's dub.json "version" statement.

Does it output any detail messages after the main error message? It
sounds like either it doesn't find the 1.0.0-rc1, or that some other
dependency in the dependency graph has a dependency on the package with
<1.0.0, so that there is a conflict.

No, nothing at all. The error message was exactly as I posted.

BTW, which DUB version is this? beta 2 or GIT master? There has been
quite a number of issues in beta 2 and I just want to fix one more
before releasing a third beta.

git master, I think, but I'm not sure how up to date. Happy to pull and test, but I think in this case it was just a typo I didn't spot. :-\

Okay, I've used a non-existent version and get the same error message
without details. Going to fix that now.