rPUA-2006-0190-1 conary conary-build conary-repository
[Posted October 13, 2006 by ris]
| From: |
| rPath Update Announcements <announce-noreply-AT-rpath.com> |
| To: |
| update-announce-AT-lists.rpath.com |
| Subject: |
| rPUA-2006-0190-1 conary conary-build conary-repository |
| Date: |
| Fri, 13 Oct 2006 10:50:52 -0400 |
| Cc: |
| lwn-AT-lwn.net |
rPath Update Advisory: 2006-0190-1
Published: 2006-10-13
Products: rPath Linux 1
Rating: Minor
Updated Versions:
conary=/conary.rpath.com@rpl:devel//1/1.0.34-0.1-1
conary-build=/conary.rpath.com@rpl:devel//1/1.0.34-0.1-1
conary-repository=/conary.rpath.com@rpl:devel//1/1.0.34-0.1-1
References:
http://blogs.conary.com/index.php/conarynews/2006/10/12/c...
Description:
Conary 1.0.34 is a maintenance release.
Client Changes:
o You can now delete troves, update from changeset files, and
update with a full version specified without an installLabelPath
set. (CNY-281)
o The conary rm command has been added as an alias for the conary
remove command. (CNY-952)
o Conary now produces an error message when an invalid context
is specified. (CNY-890)
o User settings in a context will override but not remove user
settings from the main conary configuration file. (CNY-972)
Build (cvc) Changes:
o The cvc cook --prep command now warns about missing dependencies
instead of raising an error. The cvc cook --download command does
not warn or error. (CNY-787)
o In a group recipe, if you use r.remove() to remove a
component from a package in a group (which marks the component
byDefault=False), and the package no longer contains any
byDefault=True components, the package itself will also be made
byDefault=False. This avoids installing packages containing no
components on the system. (CNY-774)
o Previously, Java files that have no discoverable provided
or required interfaces (for example, due to EAR dependencies)
caused a traceback. Conary now handles this case correctly and
does not traceback.
o Merging when the current version is already based on the
parent version now gives an error message instead of writing out
an incorrect CONARY file (CNY-968)
Bug Fixes:
o Erases of critical troves is no longer considered a reason to
restart Conary.
o A bug triggered when a critical update of a trove depended on
an erase has been fixed.
o A bug that caused changesets to be invalidated from the changeset
cache when signatures were not modified by setTroveSigs() has
been fixed.
o A bug that caused an Internal Server Error (ISE) when attempting
to browse the files in a shadowed component via the Conary
repository browser has been fixed. (CNY-926)
o A bug introduced 1.0.32 that affected the ability to update two
troves due to the same broken dependency when using resolveLevel
2 has been fixed. This bug affected the ability to simply run the
conary update conary command when conary-build and conary-repository
will both installed. (CNY-949)
o Conary will now display config lines that are equivalent to
the default configuration value but are set explicitly by the
user. (CNY-959)
o Specifying includeConfigFile within a context will now include
the file also within that context. (CNY-622)
o A memory leak in conary.lib.misc.depSplit() has been fixed.
o The client no longer loops forever trying to create
cross-repository relative changesets when the trove is missing
from one of the repositories. (CNY-948)
o Repositories no longer return empty troves when createChangeSet()
is called on troves which are referenced within the repository
but present on a remote repository. (CNY-948)
o Repository queries no longer return matches for troves
which are referenced by groups but are not present in the
repository. (CNY-947)
o Specifying a root (through conaryrc configuration or the --root
command line parameter) that is not a directory no longer results
in an unhandled exception. (CNY-814)
o Renaming and changing a source file no longer results in
tracebacks from the cvc update and cvc merge commands. (CNY-944,
CNY-967)
(
Log in to post comments)