rPUA-2006-0104-1 conary conary-build conary-policy conary-repository

rPath Update Advisory: 2006-0104-1
Published: 2006-06-13
Products: rPath Linux 1
Rating: Minor
Updated Versions:
    conary=/conary.rpath.com@rpl:devel/1.0.19-1-1
    conary-build=/conary.rpath.com@rpl:devel/1.0.19-1-1
    conary-repository=/conary.rpath.com@rpl:devel/1.0.19-1-1
    conary-policy=/conary.rpath.com@rpl:devel/1.0.5-1-1

References:
    http://issues.rpath.com/browse/CNY-22
    http://issues.rpath.com/browse/CNY-391
    http://issues.rpath.com/browse/CNY-405
    http://issues.rpath.com/browse/CNY-424
    http://issues.rpath.com/browse/CNY-450
    http://issues.rpath.com/browse/CNY-460
    http://issues.rpath.com/browse/CNY-471
    http://issues.rpath.com/browse/CNY-476
    http://issues.rpath.com/browse/CNY-497
    http://issues.rpath.com/browse/CNY-520
    http://issues.rpath.com/browse/CNY-530
    http://issues.rpath.com/browse/CNP-11

Description:
    Conary 1.0.19 is a maintenance release.
    
    API Change:
     o  In order to fully represent empty flavors in Conary, a new Flavor
        object class has been added. Previously, DependencySet objects
        were used to store flavor information. Unfortunately, it was not
        possible to distinguish "empty flavor" from "flavor not specified".
        When dealing with thawing frozen flavors, use ThawFlavor() instead
        of ThawDependencySet(). When testing to see if a flavor is empty,
        use the isEmpty() method of the flavor object.
    
    Client Changes:
     o  The default resolveLevel setting is now 2, instead of its previous
        value of 1. This means that Conary will try to update troves that
        would otherwise cause an update to fail. See the conary man page
        for more details.
     o  Multiple issues have been addressed related to interactive
        prompting for user passwords (CNY-466):
        - Password prompts are based on the server name portion of the
          label being accessed, not the actual hostname of the server
          (these are often different when repositoryMaps are used).
        - When no password callback is available, the operation will fail
          with an open error (which is identical to what would happen if no
          user name was present) instead of giving a traceback.
        - The download thread uses the passwords that the original thread
          obtained from the user.
        - The download thread is able to prompt for passwords from the user
          if distributed changesets require access to additional repositories.
    
    Build Changes:
     o  The r.Ant(), r.JavaCompile(), and r.ClassPath() build actions have
        been added to support building Java packages with Conary.
     o  The r.addPatch() source action will now determine the patchlevel
        without users needing to add level=... in the r.addPatch()
        invocation. The level parameter is still honored, but should not
        be needed.
     o  The cvc cook --show-buildreqs command now displays build
        requirements inherited from parent recipe classes. (CNY-520)
     o  The output of the cvc diff and cvc rdiff commands can now be used
        as an input to patch when files are added between two versions.
        (CNY-424)
     o  The dom0 and domU Use flags have been added. They default to sense
        prefernot. The domU flag should be used to build binaries specific
        to Xen domU environments where special provisions are made for
        paravirtualization. The dom0 flag should be used to build binaries
        specific to Xen dom0 environments where special provisions are made
        for the hypervisor. The existing xen flag should be used to build
        binaries specific to Xen which apply equally to Xen dom0 and domU
        environments. (dom0 and domU without reference to the xen flavor
        would apply to any paravirtualization technology, and so if there
        were dom0 or domU changes that were really specific to a particular
        paravirtualization technology, then they would be flavored both for
        that particular paravirtualization technology and the domain of use.)
     o  The warning message for modes specified without an initial "0" have
        been improved to include the path that is affected. (CNY-530)
    
    Server Changes:
     o  Conary now uses the term "Entitlement Class" in all Conary repository
        web interfaces, replacing "Entitlement Group".
    
    Bugs Fixed:
     o  The Conary repository now returns an error to a client when
        committing duplicate troves that have an empty flavor. (CNY-476)
     o  When checking out a source trove from a repository using the cvc
        checkout command, the user is no longer warned about not being able
        to change the ownership of the files checked out.
     o  A bug has been fixed in Conary's determination of what troves had
        been updated locally. This bug caused the conary updateall command
        to consider many x86 troves as needing to be updated separately
        instead of as a part of group-dist. This could cause the conary
        updateall command to fail. (CNY-497)
     o  Issuing the command conary q tmpwatch:runtime --recurse no longer
        causes a traceback. (CNY-460)
     o  Interactive mode now handles EOF by assuming it means 'no'; thanks
        go to David Coulthart for the patch. (CNY-391)
     o  Configuration settings in contexts can now be overridden from the
        command line. (CNY-22)
     o  Redirect changesets now have primary troves, improving the way
        conary showchangeset displays them. (CNY-450)
     o  Users' passwords are now masked when using the cvc context command
        (unless the --show-passwords option is specified). (CNY-471)
     o  Excess output from commitaction, which was caused by a change in
        option parsing code, has been removed. (CNY-405)
    
    Conary Policy: The conary-policy package has been updated, and
    conary-policy 1.0.5 has been released concurrently.
     o  The Enforce*BuildRequirements policies now enforce that interpreters
        for scripts are listed as build requirements. (CNP-11)
     o  Previously, when the buildPath was too short to modify path
        references in binary files, the Strip policy silently disabled using
        the debugedit program to move debugging information from those
        binary files into separate files in the :debuginfo component, and
        instead removed the debugging information entirely. Now, the Strip
        policy raises an exception, preventing accidental destruction of
        debugging information in this (rare) circumstance.
     o  The Strip policy is no longer run for bootstrap builds, making the
        debugging of bootstrap builds more straightforward.