Created attachment 303321 [details] error message when starting kportagetray 1.) Currently, kportagetray-0.2.4 does not work. At startup it dies with the error log as can be seen in the attachment. This commit http://gitorious.org/~dmaggot/kportagetray/dmaggots-kportagetray/commit/2eebbc5b89f40b2ecaf4c3a9e08b8846bace5b4c fixes it. 2.) [kde] kportage-tray-9999 cannot fetch: fatal: The remote end hung up unexpectedly * ERROR: app-portage/kportagetray-9999 failed (unpack phase): * git-2_initial_clone: can't fetch from git://anongit.kde.org/kportagetray
Created attachment 303323 [details, diff] kportagetray-0.2.4_fix_class_name.patch
Created attachment 303325 [details, diff] kportagetray-0.2.4.ebuild.diff
Created attachment 303333 [details, diff] kportagetray-9999.ebuild.diff inherit needs to be before EGIT_REPO_URI
Created attachment 303335 [details, diff] kportagetray-0.2.4_update_scripts.patch ok, without that fix, scripts wouldn't work anyway
Created attachment 303337 [details, diff] kportagetray-0.2.4.ebuild.diff This is finally also running fine (on my system). kportagetray-9999: master is still lacking those packages
Fixed the in-overlay live ebuild, but somebody else will need to handle fixing it in the main portage tree.
Not that it's the most important piece of software in the tree, but this is still broken in portage. What else can I do that I haven't already here?
(In reply to comment #7) > Not that it's the most important piece of software in the tree, but this is > still broken in portage. What else can I do that I haven't already here? Applied in the main tree. Sorry, sometimes people are just busy otherwise.
Thanks! :) In such cases there's always an inner conflict between 'I want this bug be fixed' and 'I don't want to be that bugging kind of person'.
