<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Matthias Clasen wrote:
<blockquote
cite="mid:cbccc63c0711130543l458769dap4a0fa876eb43783f@mail.gmail.com"
type="cite">
<pre wrap="">On Nov 13, 2007 12:49 AM, Tim Lauridsen <a class="moz-txt-link-rfc2396E" href="mailto:tim.lauridsen@googlemail.com"><tim.lauridsen@googlemail.com></a> 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.
* Get the list of available updates.
* Foreach update check if it can be depsolved.
* if yes: submit package available if
* 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=""><!---->
Does that even give you a correct result ? I can easily imagine a situation with
2 available updates, each of which can be installed individually, but
which conflict
with each other, directly or indirectly.
_______________________________________________
PackageKit mailing list
<a class="moz-txt-link-abbreviated" href="mailto:PackageKit@lists.freedesktop.org">PackageKit@lists.freedesktop.org</a>
<a class="moz-txt-link-freetext" href="http://lists.freedesktop.org/mailman/listinfo/packagekit">http://lists.freedesktop.org/mailman/listinfo/packagekit</a>
</pre>
</blockquote>
It is not catching all the cases, but most of the cases.<br>
if two updates conflict with each other which one shall be skipped ??
The first or the second.<br>
Some case is not even catched buy the depsolver, they are first catched
in the RPM Test Transaction<br>
<br>
Tim<br>
<br>
<br>
</body>
</html>