<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE></TITLE>
<META content="MSHTML 6.00.6000.16544" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV><SPAN class=049425700-19102007><FONT face=Arial color=#0000ff
size=2>Normally that works but every once in a while, the text of the dependency
error message does not point out what you are supposed to exclude. There was one
the other day but I can't think of its name.</FONT></SPAN></DIV>
<BLOCKQUOTE>
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B>
fedora-test-list-bounces@redhat.com
[mailto:fedora-test-list-bounces@redhat.com]<B>On Behalf Of </B>Dan
Carruthers<BR><B>Sent:</B> Thursday, October 18, 2007 8:12 PM<BR><B>To:</B>
For testers of Fedora Core development releases<BR><B>Subject:</B> Re: Policy
or best practice on mentioning dependency issues<BR><BR></FONT></DIV>Arch
Willingham wrote:
<BLOCKQUOTE cite=mid:6B74CFE2B2A0B748BB3DC16E047697864B87BA@hall.tup.com
type="cite">
<META content="MSHTML 6.00.6000.16544" name=GENERATOR>
<DIV><SPAN class=061104423-18102007><FONT face=Arial color=#0000ff size=2>In
my case, I guess I am "crying" (?) for two reasons:</FONT></SPAN></DIV>
<DIV><SPAN class=061104423-18102007></SPAN> </DIV>
<OL>
<LI><SPAN class=061104423-18102007><FONT face=Arial color=#0000ff
size=2>With yumex you have to start it, wait for it to come up, pick
select, tell it it ok, wait for it to finish, tell it to close.....lost of
hand holding. On the other hand, with a yum command line (shell script),
you click one command and walk away.</FONT></SPAN>
<LI><SPAN class=061104423-18102007><FONT face=Arial color=#0000ff
size=2>Sometimes, you can't tell which one is the problem with yumex. It
bombs out and says there is a problem with x dependency in y package. When
you review he list, none of the updatable packages contain anything
obvious to clue you in to which package to exclude. I had one happen that
way the other night. I had to end up opening yumex, selecting five
packages, telling it to apply them. If they ran...great...if not figure
out which of those five were causing the problem.</FONT></SPAN> </LI></OL>
<DIV><SPAN class=061104423-18102007><FONT face=Arial color=#0000ff
size=2>Arch</FONT></SPAN></DIV>
<DIV><SPAN class=061104423-18102007></SPAN> </DIV>
<BLOCKQUOTE>
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> <A
class=moz-txt-link-abbreviated
href="mailto:fedora-test-list-bounces@redhat.com">fedora-test-list-bounces@redhat.com</A>
[<A class=moz-txt-link-freetext
href="mailto:fedora-test-list-bounces@redhat.com">mailto:fedora-test-list-bounces@redhat.com</A>]<B>On
Behalf Of </B>Dan Carruthers<BR><B>Sent:</B> Thursday, October 18, 2007
7:11 PM<BR><B>To:</B> For testers of Fedora Core development
releases<BR><B>Subject:</B> Re: Policy or best practice on mentioning
dependency issues<BR><BR></FONT></DIV>seth vidal wrote:
<BLOCKQUOTE cite=mid:1192718023.8542.111.camel@cutter type="cite"><PRE wrap="">On Thu, 2007-10-18 at 17:29 +0300, cornel panceac wrote:
</PRE>
<BLOCKQUOTE type="cite"><PRE wrap="">hmm, what if instead of exiting, yum would ask: "do you wanna continue
with the broken deps packages excluded?" or similar?
</PRE></BLOCKQUOTE><PRE wrap=""><!---->
what would you want yum to do if you ran it with -y?
-sv
</PRE></BLOCKQUOTE>I see all these people crying about broken deps
packages in yum, so why not run yumex than when you have a broken dep just
uncheck that package and go ahead with the
install.<BR></BLOCKQUOTE></BLOCKQUOTE>Seems that when I have a dependency
error a message box pops up and I take the time to read it to determine the
error than just correct it and rerun.<BR></BLOCKQUOTE></BODY></HTML>