Josef Reidinger schrieb:
Stefan Schubert write:
ref: refs/heads/master
commit d50ad4b891552d7f205325e408fca63ad53d5a89
Author: Stefan Schubert <[email protected]>
Date: Fri Dec 18 13:10:02 2009 +0100
handle PackageKit errors (bnc #559233)
---
plugins/patches/app/models/resolvable.rb | 30 +++++++++++++++++++-
.../package/yast2-webservice-patches.changes | 5 +++
2 files changed, 34 insertions(+), 1 deletions(-)
diff --git a/plugins/patches/app/models/resolvable.rb
b/plugins/patches/app/models/resolvable.rb
index 09b1795..7b9acc3 100644
--- a/plugins/patches/app/models/resolvable.rb
+++ b/plugins/patches/app/models/resolvable.rb
@@ -7,6 +7,23 @@ require 'thread'
require 'exceptions'
+class PackageKitError < BackendException
+ def initialize(description)
+ @description = description
+ super("PackageKit error")
+ end
+
+ def to_xml
+ xml = Builder::XmlMarkup.new({})
+ xml.instruct!
+
+ xml.error do
+ xml.type "PACKAGEKIT_ERROR"
+ xml.description @description
^^^
Hi,
duncan add to frontend ability to identify bugs. By default if exception
doesn't have bug key it is considered as bug (duncan - it is good default?).
So in this case it is not our bug, but it is problem of package kit, maybe we
should not report it as bug - Duncan what is idea behind bug key and how it is
used?
Hm, in that case I am not sure concerning Bug ID, cause there will also
problems reported which depends on our environment like "not signed GPG
key". So
in this case the user would not expect an error key...I assume
thanks
Josef
<snip/>
--
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
