Re: Policy or best practice on mentioning dependency issues

["cornel panceac" <cpanceac@xxxxxxxxx>]

and sometimes, yumex is just not working like when it's behind the m$ proxy i have at office, even if i set the proxy in yumex config. wich reminds me of another issue: sometimes the mirrors work slow or not at all, unfortunately there's no easy way to tell wich mirror is used until yum gives-up. also there's no indication of speed. and, if using multiple mirrors, download is still serialized, that is yum is not downloadingfrom many repos in the same time and some other issues.  BUT:
that does not mean yum is not improving constantly (wich it does) AND we are really grateful to the yum developers for their work.so, one last question is: what else (except testing and reporting) can we do to help yum become better? :)

thank you.

2007/10/19, Arch Willingham <arch@xxxxxxxxxxx>:

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.

-----Original Message-----
From: fedora-test-list-bounces@xxxxxxxxxx [mailto:fedora-test-list-bounces@xxxxxxxxxx]On Behalf Of Dan Carruthers
Sent: Thursday, October 18, 2007 8:12 PM
To: For testers of Fedora Core development releases
Subject: Re: Policy or best practice on mentioning dependency issues

Arch Willingham wrote:

In my case, I guess I am "crying" (?) for two reasons:

 

1. 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.
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.

Arch

like it happened yesterday for me: there were deps issues, (livna enabled) and after unselecting kernel, it was added as a  dependency and everything was ok, _all_ updates were installed (f8t3).

-----Original Message-----
From: fedora-test-list-bounces@xxxxxxxxxx [mailto:fedora-test-list-bounces@xxxxxxxxxx]On Behalf Of Dan Carruthers
Sent: Thursday, October 18, 2007 7:11 PM
To: For testers of Fedora Core development releases
Subject: Re: Policy or best practice on mentioning dependency issues

seth vidal wrote:

On Thu, 2007-10-18 at 17:29 +0300, cornel panceac wrote:
  

hmm, what if instead of exiting, yum would ask: "do you wanna continue
with the broken deps packages excluded?" or similar?
    

what would you want yum to do if you ran it with -y?


-sv





  

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.

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.

--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list

-- 
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe: 
https://www.redhat.com/mailman/listinfo/fedora-test-list