RHBA-2009:1419: bug fix update
271
package already on the system as being installed and not available. This warning was nonsensical
and misleading because it implied that every package already on the system was available in a
repository that yum could access. The code that produced this warning has been removed from
yum
. Now when yum install '*' is used under circumstances where no packages are available
in any repository,
yum
does not produce this warning, but simply reports
Nothing to do
.
(
BZ#482812
1912
)
• Previously, one of the tests that
yum
performed during a transaction produced erroneous results
when rolling back a package on a managed system to an earlier version. The result of this test
was that
yum
would remove the package altogether rather than roll it back. Since the test was
redundant, it has been removed from
yum
, with the result that
yum
now rolls back packages on
managed systems correctly. (
BZ#489256
1913
)
• Current versions of yum include code for old
yum
utilities. The continued availability of the old
utilities allows developers to ensure backward compatibility of
yum
features with the versions of
yum
shipped with earlier versions of Red Hat Enterprise Linux. A number of errors in this code have
been corrected, ensuring that tests against these old utilities remain valid. (
BZ#491077
1914
)
• Because every rpm package should have a
%description
field,
yum info
did not allow for
packages where this field might be empty. When
yum info
encountered such a package, it would
crash.
Yum info
now allows for empty
%description
fields in packages and will not crash when
it encounters an empty field. (
BZ#491406
1915
)
• Previously, when an old version of a package accidentally provided a capability,
yum
might still
have picked newer versions of that package to provide that capability, even if the newer vesions did
not provide the capability. As a result,
yum
could assume that a dependency was met, even when it
was not.
Yum
now tests dependencies more carefully, preventing this situation from occurring and
ensuring that dependencies are properly met. (
BZ#498635
1916
)
• When
yum
installed local packages, it defaulted to expecting SHA-256 checksums. Because
packages for Red Hat Enterprise Linux 5 use MD5 checksums, the installation would fail with a
bad
checksum type
error. Now, when
yum
encounters a bad SHA-256 checksum, it attempts to verify
the package with a SHA-1 checksum instead, which will sucessfully verify the MD5 checksums used
for Red Hat Enterprise Linux 5 packages. (
BZ#500697
1917
)
• Previously, when a user attempted a
yum update
for a package that was not installed,
yum
would
exit with the message
No Packages marked for Update
, whether the package were available
or not. Although true, this message did not alert the user that such a package was available for
installation. Now, if the package is available but not installed,
yum
notifies the user of this fact.
(
BZ#507326
1918
)
• The Linux environment variable
LC_CTYPE
specifies a character set and the variable
LC_MESSAGES
specifies a language for messages. Previously, yum selected a language for messages based
on
LC_CTYPE
instead of
LC_MESSAGES
. Although on many configurations,
LC_CTYPE
and
LC_MESSAGES
will be set to the same language and character encoding, this is not necessarily the
case, and by using the wrong environment variable, yum would not provide the expected output
under configurations where
LC_CTYPE
and
LC_MESSAGES
were set differently. Yum now uses
LC_MESSAGES
to determine the language to provide messages in, resulting in consistent and
expected behavior. (
BZ#507357
1919
)
• Due to a logic error in the code,
yum
ignored the
--color=never
option on the command
line and
color=never option
in
yum.conf
.
Yum
output was therefore always in color,
Summary of Contents for ENTERPRISE 5.4 RELEASE NOTES
Page 1: ...Red Hat Enterprise Linux 5 4 Technical Notes Every Change to Every Package ...
Page 18: ...xviii ...
Page 306: ...288 ...
Page 464: ...446 ...
Page 466: ...448 ...
