Needed for totem-2.32: amd64 ia64 ppc ppc64 sparc x86 Thanks Reproducible: Always
Created attachment 262483 [details] coherence init script
(In reply to comment #1) > Created an attachment (id=262483) [details] > coherence init script > Sorry, an initscript with "--make-pidfile --pidfile /var/run/coherence.pid" added, so coherence can be started and stopped without major errors.
Comment on attachment 262483 [details] coherence init script This bug is about stabilizing coherence. Not about a init script. File a new bug and don't try to hijack unrelated bugs. Thanks!
As talked on IRC and after checking at buildtime (and it at least looks to run ok): arches, please test and mark stable
amd64 fail pulled in this dependency dev-python/epsilon-0.6.0 epsilon failed half a dozen areas. i am having trouble with my configuration and can't get a build log up yet. but will post it here if needed. epsilon.test.test_sslverify.OpenSSLOptions.testSuccessfulSymmetricSelfSignedCertificateVerification =============================================================================== [ERROR] Traceback (most recent call last): File "/var/tmp/portage/dev-python/epsilon-0.6.0/work/Epsilon-0.6.0-2.6/epsilon/test/test_sslverify.py", line 227, in testVerification clientDN = sslverify.DistinguishedName(commonName='client') exceptions.NameError: global name 'sslverify' is not defined epsilon.test.test_sslverify.OpenSSLOptions.testVerification ------------------------------------------------------------------------------- Ran 226 tests in 1.264s FAILED (skips=5, expectedFailures=1, failures=1, errors=9, successes=210) * ERROR: dev-python/epsilon-0.6.0 failed: * Testing failed with CPython 2.6 in python_test_function() function * * Call stack: * ebuild.sh, line 56: Called src_test * environment, line 5235: Called distutils_src_test * environment, line 1573: Called python_execute_trial '-P' '$(_distutils_get_PYTHONPATH)' '-s' '--' 'epsilon' * environment, line 3912: Called python_execute_function '-s' 'python_test_function' 'epsilon' * environment, line 3745: Called die * The specific snippet of code: * die "${failure_message}"; * * If you need support, post the output of 'emerge --info =dev-python/epsilon-0.6.0', * the complete build log and the output of 'emerge -pqv =dev-python/epsilon-0.6.0'. * The complete build log is located at '/var/tmp/portage/dev-python/epsilon-0.6.0/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-python/epsilon-0.6.0/temp/environment'. * S: '/var/tmp/portage/dev-python/epsilon-0.6.0/work/Epsilon-0.6.0' >>> Failed to emerge dev-python/epsilon-0.6.0, Log file: >>> '/var/tmp/portage/dev-python/epsilon-0.6.0/temp/build.log'
That *epsilon* test failures are old and known -> bug 295068 -> they don't block this
Archtested on x86: Everything fine
(In reply to comment #7) > Archtested on x86: Everything fine > In http://bugs.gentoo.org/show_bug.cgi?id=355187(In reply to comment #3) > (From update of attachment 262483 [details]) > This bug is about stabilizing coherence. Not about a init script. File a new > bug and don't try to hijack unrelated bugs. > > Thanks! > I have a submitted a new ebuild. including a working init and configuration file, see bug 355187. A user coherence is added as well, so the daemon needs not to be run as root user.
x86 done. Thanks David.
amd64 done
on ppc it needs stabilization of =media-video/coherence-0.6.6.2 =dev-python/louie-1.1 =dev-python/tagpy-0.94.8 =dev-python/axiom-0.6.0 =dev-python/epsilon-0.6.0
I think arch teams are allowed to stabilize them in cases like this, but CCing python team anyway to confirm
(In reply to comment #11) > =dev-python/louie-1.1 > =dev-python/tagpy-0.94.8 > =dev-python/axiom-0.6.0 > =dev-python/epsilon-0.6.0 I allow stabilization.
(In reply to comment #13) Test failures in these packages are not a regression.
finally, ppc/sparc stable.
ppc64 stable
not sure why i marked this ~ia64...closing
