We've started publishing our current development version of conary twice a day into conary-unstable.conary.com@rpl:devel. I'll be manually pushing versions that I think are more or less appropriate for public consumption to conary-unstable.conary.com@rpl:1. We'd love for enterprising testers to start using this label to give us an early heads up for bugs in conary.

And, currently there's a special reason to download conary from the unstable branch - I've just added code that makes our dependency resolution algorithm more powerful. Let's imagine this "hypothetical" situation:

1. conary:python v.1 provides "trove: conary:python(1)"
2. conary-build:python v.1 requires "trove: conary:python(1)"
3. conary:runtime v.1 requires "trove: conary:python(1)"

A new version of conary, version 2.0 comes out, which looks exactly like version 1.0 except for it requires version 2 of everything.

So let's say you want to update conary from version 1 to version 2, and so run 'conary update conary'.

Currently, conary will fail to perform the update, even with --resolve, because conary-build v.1 requires conary:python v.1, and conary doesn't want to make conary-build v.1 unusable! The new conary will see this dependency problem and try to update conary-build. If you have conary and conary-build installed, you will have seen that you cannot update one without specifying the other as well. The new conary will allow you to use dep resolution to solve this problem.

Because the algorithm almost certainly still needs tweaks, we have turned it off by default. To enable it, add "resolveLevel 2" to your conary configuration.

So update to conary using 'conary update {conary,conary-build}=conary-unstable.rpath.org@rpl:1', set your conaryrc 'resolveLevel 2'.