As per summary, the configure-arts patch is pretty much a stupid broken hack; if you need to remove the forced arts dependency, you should now just add mirror://gentoo/kde-admindir-3.5.5.tar.bz2 to SRC_URI and make sure that kde_src_unpack is used, the rest is take care of by kde.eclass. Thanks, Diego
meh, why did I add it? ;) stable on x86
not working on amd64. It's crashing once I hit the OK button of the configuration window which pops up at startup. CHROOT / # kmyfirewall Fontconfig warning: line 32: unknown element "cachedir" Fontconfig warning: line 33: unknown element "cachedir" Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed Fontconfig warning: line 32: unknown element "cachedir" Fontconfig warning: line 33: unknown element "cachedir" Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed kbuildsycoca running... ScimInputContextPlugin() QMultiInputContext::changeInputMethod(): index=0, slave=xim QMultiInputContext::changeInputMethod(): index=0, slave=xim kio (KMimeType): WARNING: KServiceType::offers : servicetype KMyFirewall/Installer not found kio (KMimeType): WARNING: KServiceType::offers : servicetype KMyFirewall/Compiler not found kio (KMimeType): WARNING: KServiceType::offers : servicetype KMyFirewall/RuleOptionEdit not found kio (KMimeType): WARNING: KServiceType::offers : servicetype KMyFirewall/RuleTargetOptionEdit not found QMultiInputContext::changeInputMethod(): index=0, slave=xim kmyfirewall: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file kmfgenericinterfaceparetui.rc kmyfirewall: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file kmfinstallerpluginui.rc kmyfirewall: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file kmfiptablescompiler.rc QMultiInputContext::changeInputMethod(): index=0, slave=xim KCrash: Application 'kmyfirewall' crashing... Could not find 'drkonqi' executable. KCrash cannot reach kdeinit, launching directly.
Looks OK in SPARC land, so stable it is!
I just tested the latest stable (0.9.6.2-r1) and it works fine, so taking amd64 off the CC until the problem is fixed.
(In reply to comment #1) > meh, why did I add it? ;) > > stable on x86 > But not bug free :-( This version lost rules eg it reads in the config file but sometimes not all rules of them. I run into this trouble now many times.
You said you "lost" rules.. were they created with <1.0 ? upstream page says that it is kind of expected then
Tempted to go back to unstable until upstream becomes active again....
(In reply to comment #6) > You said you "lost" rules.. were they created with <1.0 ? upstream page says > that it is kind of expected then > No, if I open a newly created rule set file it might be that not all rules are loaded - the next cick onto save buttons then overwrites the file and the rules are lost. I cannot reproduce this behaviour but it happens too often fro me.
Seems debian has the same issues with it (ML archives rule), herd: do we consider masking it?
I do currently a backup both of the rule file and of the generated script after every change. Then I compare the file against backup to see whether I lost rules or not. This is awfully but I dislike to go back to the old version b/c of incompatibility of the rule file format.
Toralf: So you as poweruser, what would you recommend? add a big fat warning about this and go along with it?
Yep, a fat warning that version 0.9.x is fine for all who like the iptables interface of KMyfirewall and that the version 1.0.1 didn't have much more features for this interface to be worth to be upgraded. For all others who want to try out the new generic interface they could try it.
note added
