<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=UTF-8" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Richard Hughes wrote: <blockquote cite="mid:1194941853.2987.3.camel@hughsie-laptop" type="cite"> <pre wrap="">On Tue, 2007-11-13 at 06:49 +0100, Tim Lauridsen wrote: </pre> <blockquote type="cite"> <pre wrap="">It is a difficult case the 'skip-broken' plugin i has written is working by depsolve each of the available updates, to see if it can depsolve without errors, this functionality can be build into the YumBackend. But ït increase to time to get the updates. So it should be something there can be turned on/off. </pre> </blockquote> <pre wrap=""> Why not just get the update list (complete) and: 1. if it can be depsolved, return the list 2. if not, then start processing each package and depsolving each one. so we only use the "go slow" case when the repos are broken. </pre> </blockquote> Depsolving all available updates will also take time, so it would be nice to have the possibility to turn it off. Depsolve each package one at a time, will not take much longer than depsolve the whole transaction. So i see no need to at an extra step to depsolve the whole transaction. <blockquote cite="mid:1194941853.2987.3.camel@hughsie-laptop" type="cite"> <pre wrap=""> </pre> <blockquote type="cite"> <pre wrap="">* Get the list of available updates. * Foreach update check if it can be depsolved. * if yes: submit package available if </pre> </blockquote> <pre wrap=""> not "available" - that's for searching. you want low, high, normal, security etc. </pre> </blockquote> Yes, just of cause. <blockquote cite="mid:1194941853.2987.3.camel@hughsie-laptop" type="cite"> <pre wrap=""> </pre> <blockquote type="cite"> <pre wrap="">* if no: submit package cant foo It i not easy to find the cause of why the package not can be updated is hard to get, because the error messages is not always clear. </pre> </blockquote> <pre wrap=""> Sure, we just need to find a sane English version of "cannot depsolve" - I appreciate this isn't an easy problem to fix. </pre> </blockquote> What i meant is the error messages there comes from the yum depsolver, describe the problem, not the cause of the problem. Example: 'Missing Denpendency: foolib = 1.2.3 if needed by package bar' This can be caused by a lot of causes. Tim </body> </html>