Release Notes: The "conary migrate" command now functions correctly when applying critical updates as part of the migration (such as updating conary itself). Most other significant changes involve building software with Conary: shared libraries now provide filenames as well as DT_SONAME records, configuration files go in :config components by default, supplemental documentation is now stored in :supdoc by default, and the "cvc refresh" command is improved. Committing binaries to the repository now uses relative changesets and is thus faster.
Release Notes: When multiple troves with the same name are already installed, Conary now uses path information to choose the one which should be updated. This is particularly useful for multiple foo:lib components. Failure to call GPG to validate trove signatures is now printed only if a signature trust threshhold has been set. The usage message has been simplified to be more useful, and fits on one standard-size screen. Source files can now change to and from autosource files. A KDE mirror list has been added.
Release Notes: Several minor update and build issues have been resolved.
Release Notes: Local system database update performance is significantly improved. Group building has new features to help debug problems and new features to make the process easier.
Release Notes: Several unusual update cases are handled better. Updating packages is faster. A slowdown in building packages has been fixed. Macros can now be overridden by files in the /etc/conary/macros.d/ directory. Parent troves in repository changeset caches are now invalidated when a member trove is invalidated.
Release Notes: Conary updates more robustly by trying to update conary itself first and then restarting itself to finish the update. Several database queries have been significantly sped up. The cvc refresh command has been implemented to allow re-fetching autosource files that have changed content without changing name (often of the form foo.tar.gz with no version number included).
Release Notes: This release orders updates and merges configuration files based on paths, which means that files can move between arbitrary troves rather than only within a package. This makes updates more robust, particularly when moving from one branch to another. Many common operations are significantly faster, and some also use less memory. Threaded updates have been modified to avoid hiding error conditions. On the packaging site, the clone operation has been refined, and the merge and update operations are more verbose.
Release Notes: An uncommonly-encountered issue pulling sources from SRPM files, an issue which prevented sqlite-based mirrors from themselves being mirrored, and a few cosmetic issues have all been resolved.
Release Notes: Primarily bugfixes for unusual cases, plus mirror:// support for the Comprehensive R Archive Network.
Release Notes: Troves can now be marked as removed in repositories. The repository now supports querying for troves by path. Entitlements are significantly improved. Forwards and backwards compatibility is preserved between 1.0 and 1.1 clients and repository servers.