Conary 1.0.32 and 1.1.5 are maintenance releases. Except as noted, changes listed here apply equally to both versions.

Optimizations:

• Some duplicate trove instantiations have been removed. Build requires are no longer thawed out of abstract change sets, and methods were added to get dependency and path hash information directly from trove change set objects. These changes combined for a 50% speedup of the update --info command when updating a large group into an empty root, and saved a few megabytes of memory as well. (CNY-892)
• The changes in the previous version of Conary in how XML-RPC responses are decompressed actually made Conary slower. These changes have been reverted.

Build (cvc) Changes:

• The Requires() policy now reads pkg-config files and converts the "Requires:" lines in them into trove dependencies, removing the need to specify those dependencies manually. (CNY-896)
• Files in /etc/conary/macros.d/ are now loaded in sorted order after initial macros are read from /etc/conary/macros. (CNY-878)

Bug Fixes:

• Conary now runs tagscripts correctly when passed a relative --root parameter (CNY-416).
• The cvc log command now works when there are multiple branches matching for the same trove on the same label.
• Fixed resolveLevel 2 so that it does not try to update packages that are already a part of the update. (CNY-886, CNY-780)
• Fixed resolveLevel 2 so that it does not repeatedly try to perform the same update. (CNY-887)
• The cvc cook | less command now leaves less in control of the terminal. (CNY-802)
• The download thread terminating during an update is now a fatal error.
• The web interface to a conary repository will now print an error message instead of a traceback when adding an entitlement class with access to a group that does not exist.
• The cvc cook command, when cooking a group, now limits the number of path conflicts displayed for one trove to 10. (CNY-910)
• Conary update now respects local changes when a group update occurs along with the update of the switched trove. For example, switch foo to be installed from another branch instead of the default, and then update foo and its containing group at the same time would cause conary to try to reinstall the original foo (resulting in path conflicts). (CNY-915)
• The loadRecipe() function now selects the most recent of two recipes available in the case where there are multiple choices due to label multiplicity. (CNY-918)
• Parent troves in repository changeset caches are now invalidated when a member trove is invalidated (1.1.5 only, as repositories cannot invalidate troves in 1.0.x) (CNY-746)