|| ||"Justin M. Forbes" <jmforbes-AT-rpath.com>|
|| ||rPUA-2006-0127-1 conary conary-build conary-policy
|| ||Fri, 07 Jul 2006 17:17:00 -0400|
rPath Update Advisory: 2006-0127-1
Products: rPath Linux 1
Conary 1.0.22 is a maintenance release.
o Conary now has hooks for allowing users to be prompted for both
name and password when necessary.
o Conary will no longer report a traceback when trying to perform
dependency resolution against repositories that are not available.
Instead, it will print out a warning. (CNY-578)
o It is now possible to set environment variables to use within
Conary builds from within conary configuration files, using the
new "environment" configuration item. Thanks to Pavel Volkovitskiy
for implementing this feature. (CNY-592)
o In previous versions of Conary, calls to r.PackageSpec() would
improperly override previous calls to r.ComponentSpec(); now the
ordering is preserved. Thanks to Pavel Volkovitskiy for this fix.
o A bug that could allow recursively generated changesets to have
missing redirect flags has been fixed.
o A bug in redirect handling when the branch changed but the trove
name didn't change has been fixed. Conary will do a better job of
determining what jobs to perform in this situation. (CNY-599,
o Errors relating to PGP now just display the error instead of
causing Conary to traceback. (CNY-591)
o The conary sync on a locally cooked trove will no longer traceback.
o The --from-file argument and the sync command now work together.
o An AssertionError that was occasionally reached by incorrect
repository setups is now a ConaryInternalError
o A bug has been fixed that occurred when updating to a locally cooked
trove when the user had manually removed files. (CNY-604)
o CONARY files that are not accessible will no longer cause conary to
traceback when trying to read context from them. (CNY-456)
Conary Policy: The conary-policy package has been updated, and
conary-policy 1.0.7 has been released concurrently.
Changes in 1.0.7:
o Enforce*BuildRequirements regular expression exceptions now function
with the correct sense. (CNP-14)
o A bug in NormalizePamConfig that would change pam files pointed
to by symlinks in /etc/pam.d to have permissions 0777. This would
cause Conary to fail to build the package.
o A bug in Enforce*BuildRequirements that caused it to suggest overly
aggressive and unnecessary build requirements, introduced in
conary-policy 1.0.5, has been fixed. (CNP-12)
to post comments)