Subject: | |
From: | |
Reply To: | |
Date: | Sat, 2 Sep 2006 13:26:40 +0300 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Michael Malik wrote:
> Connie,
>
> Thanks for the info.
>
> I just had this happen last night on yet another system; this time an
> i386 (I was playing around on a test system to see if I could reproduce
> the errors). It seems that when I updated all of my packages with all
> of the repos checked (one or two at a time) in yumex it causes this
> problem.
>
> I was watching it this time, and I observed the moment when it happened
> -- it was during the atrpms repo update, where yumex came back with the
> usual "package update complete", and then right after I clicked "ok" it
> froze with another window which gave a transaction failure notice (this
> should have happened BEFORE the update was carried out). The failure
> notice was on the screen for less than a second, so I couldn't make out
> the exact package(s) in conflict or missing.
>
> At this point the yumex application froze and never came back. Fearing
> there may be partial installs, I tried the update again (new yumex
> session). This time there were very few package updates which would
> pass the transaction test (listing python missing deps and freetype
> conflicts).
>
> Once again, this is not any attack on atrpms -- I have no idea what has
> caused this. I can only suspect there is some bug in yum which is only
> exposed under certain conditions, or some problem with one or more of
> the packages in one or more of the repos.
>
> I will certainly be more cautious when selecting repos in the future.
> However, it would have been nice to know which combinations would result
> in conflicts and overall chaos. I also did not imagine that yum/yumex
> would allow the system to break so easily (and thoroughly), especially
> on a stable distribution.
>
> In any case, I now have several backup/rebuild/restore jobs (so much for
> the long weekend! :-)).
>
> Still, I wanted to let you guys know I really appreciate the work you
> continue to do with the distribution, repo management, and this support
> list (and I'm sure that is no small task!). -Michael
The normal use of repositories is to use only the preselected SL ones, sl-base and
sl-errata. Use one of the other repositories only for installing some extra application
you need and is not included in sl-base and sl-errata.
|
|
|