[rhelv6-list] RHEL 6.3 Released

[Paul Preston]

Hi Chris,

>From my experience it's better to run "yum clean all" if number of packages are waiting to be updated or if a minor distribution version update is available.

Kind Regards,
--
Paul Preston
Proxar IT Ltd. Registered in England and Wales: 6744401- VAT: 942985479
Tubs Hill House, London Road, Sevenoaks, Kent, TN13 1BL
Tel:  (+44) 0844 809 4335
Fax: (+44) 01732 459 423
Mob: (+44) 077 9509 3450
Web: www.proxar.co.uk
Email: paul.preston at proxar.co.uk


-----Original Message-----
From: rhelv6-list-bounces at redhat.com [mailto:rhelv6-list-bounces at redhat.com] On Behalf Of Chris Adams
Sent: 20 June 2012 14:14
To: Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list
Subject: Re: [rhelv6-list] RHEL 6.3 Released

Once upon a time, "Weiergräber, Oliver H." <o.h.weiergraeber at fz-juelich.de> said:
> Yesterday evening, "yum update" revealed dozens of updated packages, but dependency resolution failed.

So that's what it was.  I was trying to update a server last night and got all kinds of errors with an odd set of packages.  I did a "yum clean expire-cache" to redownload metadata, and a bunch of the updates disappeared.  I still had a problem because there was a new "rpm-cron"
package but none of the other rpm-* packages (and rpm-cron requires the exact same version of rpm).

--
Chris Adams <cmadams at hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble.

_______________________________________________
rhelv6-list mailing list
rhelv6-list at redhat.com
https://www.redhat.com/mailman/listinfo/rhelv6-list
Please note that we may monitor or record telephone calls, email traffic data and also the content of email for the purposes of security and staff training. This message (and any associated file or documentation) is intended only for the use of the individual or entity to whom it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notifiedthat any dissemination, copying or distribution of this message, or files and documentation associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from oyur computer. Any views or opinions presented are solely those of the authorand do not necessarily represent those of the company.