Jelmer, > > How come a problem in Seahorse causes stupid behaviour of viz with dbus? > > This seems obscure to say the least! > > > viz contacts seahorse over dbus to verify GPG signatures on revisions.
Sorry to hammer on this one, but I guess there is some issue I am
missing.
Knowing nothing of the details, my reaction would be:
OK so Bazaar tries to contact Seahorse over DBus, there is an exception.
This exception is internal and should not be exposed to the user. The
exception should be caught by Bazaar. Bazaar knows this is a sequencing
issue and that a second try should work so try it. It works. User
probably doesn't notice the slight delay.
The fact that the DBus problem appears to be cured by a later Seahorse
is not a reason for Bazaar to abdicate its responsibility to the user,
i.e. not exposing them to unnecessary bizarrenesses. My feeling is that
Bazaar should be handling this exception not passing the buck.
--
Russel.
=============================================================================
Dr Russel Winder Partner
xmpp: [email protected]
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084 voip: sip:[email protected]
London SW11 1EN, UK m: +44 7770 465 077 skype: russel_winder
signature.asc
Description: This is a digitally signed message part
-- bzr-gtk mailing list [email protected] Modify settings or unsubscribe at: https://lists.canonical.com/mailman/listinfo/bzr-gtk
