Conary:Release Notes/1.1

From rPath Wiki

The following release notes apply to 1.1.x versions of Conary.

Conary 1.1.35

• This release is designated as a maintenance release
• Update in how unknown trove info types in the database are stored in extracted trove info
• Conary's internal diff and patch supports file without trailing newlines CNY-1979

Conary 1.1.34

• The default settings from r.add() now overrides the default settings from an r.addAll() CNY-1882
• Conary stops looking up path IDs when all files have been found instead of always walking the shadow hierarchy. CNY-1911
• Fixed: a bug that caused an error message in the rPath Appliance Platform Agent (rAPA) when using an entitlement generator CNY-1946

Conary 1.1.33

• The addArchive() source action now handles .xpi archives. (CNY-1793)
• When calling loadRecipe with a flavor, unknown flags are ignored instead of printing a traceback.
• Groups are not merged with other groups in update jobs, reducing the number of jobs that are used for updates.
• Cloning increments group version counts, mimicking the behavior of group cooking. (CNY-1724)
• When promoting, --all-flavors is now on by default. However, when specifying a flavor to promote or clone, promotes are limited by that flavor. (CNY-1535)
• Commands such as promote, update, and repquery, can take an --exact-flavors flag, indicating that the flavors for each trove must match exactly (no system flavor or heuristic is used to find the desired trove). (CNY-1829)
• If there is a problem with domain name resolution, Conary will retry five (5) times. If the connection fails after those attempts, future connection requests will then fail after the first try. (CNY-1814)
• Fixed: SQLite "ANALYZE" data causes poor database performance; the command is no longer run on local SQL databases, and any data stored by the command will be removed from those databases unless it is being accessed read-only (CNY-778)
• Fixed: relative changesets are made uninstallable when networking is down (CNY-1814)

Conary 1.1.32

• Improved efficiency for interaction between the repository and client system.
• Fixed: unused entries in the Versions table of the system Conary database not cleaned up after erasures
• Fixed: changes in the byDefault status of a trove omitted from local rollbacks (CNY-1796)

Conary 1.1.31

• Fixed: "Internal Server Error" caused when a Conary proxy attempted to convert a changeset for an older client when the upstream Conary repository was not running version 1.1.29 or later

Conary 1.1.30

• The Conary proxy no longer supports protocol version 41.
• Improved performance of the getChangeSet API call on Conary proxies running in an Apache environment.
• Fixed: version cache issue for upstream servers in the Conary proxy, which incorrectly included user information in the URL causing KeyErrors when users were switched to anonymous

Conary 1.1.29

• Repository map (repositoryMap) entries can now use wildcards for the server name in Conary configuration (conaryrc) files,
• Multiple entitlements can now be sent to each server.
• Server names in entitlements may include wildcards.
• Entitlements can be placed in Conary configuration (conaryrc) files using 'entitlement server entitlement'; "conary config" displays this entitlement information.
• Conary 1.1.29 produces metadata that is not visible to older clients, and metadata produced by older clients is not visible to Conary 1.1.29 and later clients.
• Metadata items can store strings with NUL characters.
• Client API displays insufficient permission error when the client's entitlements do not allow requested access.
• Support for the Bazaar revision control system has been added using r.addBzrSnapshot() (requires bzr >= 0.16).
• Nearly all repository operations are now performed using the permissions of the anonymous user in addition to the permission set for any user authentication information which is present.
• Path names in the entitlementsDirectory no longer have any meaning. All entitlements are read, and the serverName in the XML for the entitlement is used to determine which server to send the entitlement.
• Entitlement classes are no longer used as part of authentication; they may still be specified, but repositories now look up the class(es) for an entitlement based on the key.
• The restart information, necessary for Conary to resume execution after a critical update is applied, now includes the original command line. The way in which this information is stored is incompatible with some older versions of Conary. Downgrading from Conary version 1.1.29 (or newer) to version 1.1.11 (or older) is known to fail.
• Proxy errors are reported in the client for easier debugging.
• Changeset files are written as absolute paths in the changeset index file.
• Entitlement configuration lines continue to accept an entitlement class for backwards compatibility.
• Fixed: stack trace error for 'conary rblist' if the installLabelPath configuration option is not set
• Fixed: "Error parsing label" issue when performing 'cvc commit' on group recipes using r.setSearchPath(str(r.labelPath[0]), ...)
• Fixed: "Unknown error downloading changeset" when applying an update job containing two different versions of the same trove
• Fixed: database corruption when adding redirects pointing to otherwise-unused branches
• Conary no longer downloads redundant troves when critical updates are present in an update job with previously downloaded changesets
• Fixed: unreadable files contained in entitlement directories
• Fixed: missing documentation in Conary API (PackageRecipe classes and source-related classes)

Conary 1.1.28

• Improved performance of various file stream-related queries in a Conary repository.
• Synonym 'cvc mv' can be used in place of 'cvc rename'
• Command 'conary update' works with read-only changesets.
• Build action r.Link allows full paths to be specified for the target of the link as long as the directory matches the source of the link.
• Proxy combines all upstream changeset requests into a single job request for servers running Conary 1.1.28 and later.
• Fixed: incorrect references to createGroup
• Fixed: failed checkouts because of strange characters in the destination directory, fixed by ensuring r.addCvsSnapshot() works correctly with anonymous, pserver-based, and servers
• Fixed: directories in binary directories incorrectly provided

Conary 1.1.27

• All group cooks for one source must be done as a single large 'cvc cook' action instead of individually.
• Group flavors are shortened provided the configuration directive shortenGroupFlavors is set to True.
• Some flags are designated to be included in group flavors even if shortenGroupFlavors is set to True (including vmware, xen, and architecture flags).
• The Conary client can access the network using authenticated HTTP proxies.
• Build action r.MakeFIFO() created a named pipe at a specified location.
• When promoting two flavors of the same version of the same trove, they will always have the same version on the target branch.
• Errors in the changeset downloading code are no longer ignored by the client.
• Fixed: patch code fails when trailing context is missing at the end of the file
• Fixed: files with no permissions set (chmod 0) confused Conary because of improper checks for None
• Fixed: error in resuming a build