<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Richard Hughes wrote:
<blockquote cite="mid:1194900207.2527.54.camel@hughsie-laptop"
type="cite">
<pre wrap="">On Mon, 2007-11-12 at 15:28 -0500, David Zeuthen wrote:
</pre>
<blockquote type="cite">
<pre wrap="">[1] : Sorry, I haven't studied the interfaces in detail so I'm making
this up. It may be just be noise.
</pre>
</blockquote>
<pre wrap=""><!---->
Nahh, much easier would be to just return Packages() with different
types. At the moment we return stuff like:
package security foo;
package normal foo;
package low foo;
So maybe we just have:
package cant foo;
Richard.
_______________________________________________
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/package">http://lists.freedesktop.org/mailman/listinfo/package</a></pre>
</blockquote>
<br>
<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.
Tim
</pre>
<br>
<br>
</body>
</html>