Conary 0.80.2 automatically generates Perl and Python dependencies, both provides and requires, when building packages. (It does not yet enforce the new dependencies, in order to give time to rebuild packages to deploy them.) The repository server now falls back to anonymous access when user/password access fails. There are several improvments to update and display code.

One note to help you prepare for the near future: Conary 0.80.3 will be split into three packages: conary, conary-repository, and conary-build. When Python dependency generation is enabled, the conary-repository package will depend on kid and elementtree, but the base conary package will not.

System management:

• The cvc co foo=label command will now work even if you don't have a buildLabel set.
• The conary showcs command will now work more nicely with group changesets.
• The conary showcs --all command no longer shows ids and sha1s.
• The conary verify and conary q --diff commands work again.
• The conary q package --components command will display the components installed for a package.
• Conary now will not erase pinned items until they are explicitly unpinned.
• The pinTroves config item behavior has been fixed. It now consistently pins all troves that match a pinTrove line.
• When a trove is left on the system because of dependency resolution during an update, a warning message is printed.
• Command line configuration, such as --config 'buildLabel conary.rpath.com@rpl:devel', now overrides context configuration.
• Bugs in the conary update foo=old--new behavior have been fixed.

Building packages:

• Automated Perl dependencies have been added, for both provides and requires. They are not yet enforced, in order to give time to adapt while perl packages are being re-built.
• Automated Python dependencies have been added, for both provides and requires. Like Perl dependencies, they are not yet enforced.
• It is now possible for a recipe to request that specific individual requirements be removed from files using the exceptDeps keyword argument to r.Requires(). Previously, your only choices were to accept all or none of the dependencies generated by r.Requires().
• The EnforceJavaBuildRequirements policy has been added. When you are packaging precompiled Java software where you have .class/.jar files but no .java files, you can use del EnforceJavaBuildRequirements to prevent this from policy from generating false positives.
• The EnforceCILBuildRequirements policy has been added to ensure that C# applications have a complete build requirement set.
• The EnforcePerlBuildRequirements and EnforcePythonBuildRequirements policies have been added. Failures found by this policy may be caused by packages on the system not having been rebuilt yet with Perl and Python dependencies, but could also show bugs in the Perl or Python dependency code.
• Enforce*BuildRequirements now warn when a package has requirements which they don't fulfill themselves and which are not fulfilled by the system database (for example, soname dependencies from linking against libraries that are not managed by Conary on the system).
• Java dependencies now properly ignore array elements in all cases, removing false Java dependencies like [[I and [[B.
• The r.Replace() action now takes a lines=regexp argument, to match a line based on a regexp.
• A bug that caused r.Requires('file:runtime') to create a file dependency on runtime instead of trove dependency on file:runtime has been fixed.
• Conary now writes more information about the build environment to the build log when cooking.

Repository server:

• The repository server now retries a request as an anonymous user if the provided user authentication information does not allow a client request to succeed.
• When using server.py --add-user to add a user to a repository server, the user will only be given admin privileges if --admin is added to the command line. Previously, all users added with server.py had admin privileges.