On Thu, Sep 10, 2009 at 11:01 AM, drew einhorn <drew.einhorn@xxxxxxxxx> wrote:
>> Rather than trying to figure out what you have and how to fix it,
>> it may be easier to start over an build a new system from scratch.
So? Yum is simply hanging for him, not failing with python errors or
incompatible package messages. Rather than immediately jump straight
to the 'format C:' logic, why not simply turn up the debugging level
for yum to see specifically what it's doing. From there, identifying
the problem repositories (per the earlier advice given of disablerepo)
and narrowing down the issue are the appropriate steps.
Your doctor does not simply rip your heart out because you have high
blood pressure. They find out possible causes and then treat them
appropriately.
> True. But figuring out which packages came from which repo, can
> be difficult.
While yum and rpm both lack a method to tag which repository a given
package came from, the packages themselves can tell you. A repo tag,
while easier, is but one method for doing so. The CentOS wiki even has
a section on this in the
http://wiki.centos.org/TipsAndTricks/YumAndRPM page.
rpm -qa --qf '%{NAME} %{VENDOR}\n' | grep -v CentOS
This command will show all packages installed on the system that are
NOT from CentOS. Add an additional pipe and you can sort the output by
3rd party vendor.
If you're going to take the time to answer someone on the mailing
list, please make it helpful advice that attempts to solve the
problem. Advising heart surgery (or in this case a lobotomy) for the
common cold isn't really good practice.
--
During times of universal deceit, telling the truth becomes a revolutionary act.
George Orwell
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
