When you attempt to emerge the unmasked version of meld, it fails. Reproducible: Always Steps to Reproduce: 1. emerge meld Actual Results: Calculating dependencies ...done! >>> emerge (1 of 1) dev-util/meld-0.9.0-r1 to / >>> md5 src_uri ;-) meld-0.9.0.tgz >>> Unpacking source... >>> Unpacking meld-0.9.0.tgz to /var/tmp/portage/meld-0.9.0-r1/work * Applying meld-0.9.0-gentoo.diff ... [ ok ] * Applying meld-0.9.0-gtktoolbar.patch ... [ ok ] >>> Source unpacked. #./meld . make: check_release: Command not found ./meld foo? make: *** [check] Error 127 make: *** Waiting for unfinished jobs.... (meld:15634): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", (meld:15634): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", (meld:15634): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", (meld:15634): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", ACCESS DENIED chmod: /root/.gnome2_private Could not set mode 0700 on private per-user gnome configuration directory `/root/.gnome2_private/': Permission denied make: *** [rundiff] Error 1 !!! ERROR: dev-util/meld-0.9.0-r1 failed. !!! Function src_compile, Line 510, Exitcode 2 !!! emake failed !!! If you need support, post the topmost build error, NOT this status message. --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-dev-util_-_meld-0.9.0-r1-15609.log" chmod: /root/.gnome2_private -------------------------------------------------------------------------------- Expected Results: emerge
there are a great deal of gnome packages that fail maketest in this way. (nautilus, libbonobo, etc) apparently the gentoo gnome herd finds fixing lowly maketest bugs beneath them. see bug 69347 and bug 69343.
@Ryan : Quite the biased misinterpretation you got going there. You really think your comment will encourage us to drop all more urgent devving & start like mad fixing broken tests ? I haven't seen you fixing any of these tests, so I'd suggest you start doing your 'community duty' instead of wasting your time here blackmouthing us. *** This bug has been marked as a duplicate of 69343 ***
One day, a man visited his doctor in great pain. The doctor asked him what was wrong. "When I awoke this morning, I found I experience a terrible stabbing pain in my chest whenever I move my left arm." "Then don't move your left arm", the doctor said, and pronounced him cured. i couldn't care less if you fix the tests or not. they're upstream's problem and your team is obviously extremely busy. but if someone reports the test is broken, "then don't use maketest" is not a constructive answer. perhaps disabling the src_test portion of the the offending ebuild would be a better solution - saving user frustration, duplicate bug reports, and your time to work on more important matters. sorry for the bugspam.
