| View previous topic :: View next topic |
| Author |
Message |
richard.langly
n00b
Joined: 05 Sep 2008
Posts: 26
|
 Posted: Sun Nov 02, 2008 1:59 am Post subject: can't install pylons, access violation summary |
 |
|
Hi,
I'm trying to install pylons, and been running into a lot of problems on x86_64. I had previously installed pylons using easy_install w/ not a single problem, but with emerge, tons of masked packages and now this.
Can anyone tell me what's going on, what I should try?
| Code: |
... (lots of the following type errors)
...
paste.errordocument.StatusBasedForward:29: (ERROR/3) Unknown directive type "code-block".
.. code-block:: Python
from paste.errordocument import StatusBasedForward
from paste.recursive import RecursiveMiddleware
from urllib import urlencode
def error_mapper(code, message, environ, global_conf, kw)
if code in [404, 500]:
params = urlencode({'message':message, 'code':code})
url = '/error?'%(params)
return url
else:
return None
app = RecursiveMiddleware(
StatusBasedForward(app, mapper=error_mapper),
)
paste.response.error_response:3: (ERROR/3) Unknown directive type "code-block".
.. code-block:: Python
status, headers, body = wsgilib.error_response(
'301 Moved Permanently', 'Moved to <a href="%s">%s</a>'
% (url, url))
start_response(status, headers)
return [body]
paste.wsgiwrappers.WSGIResponse.__call__:5: (ERROR/3) Unknown directive type "code-block".
.. code-block:: Python
def wsgi_app(environ, start_response):
response = WSGIResponse()
response.write("Hello world")
response.headers['Content-Type'] = 'latin1'
return response(environ, start_response)
paste.registry:21: (ERROR/3) Unknown directive type "code-block".
.. code-block:: Python
#yourpackage/__init__.py
from paste.registry import RegistryManager, StackedObjectProxy
myglobal = StackedObjectProxy()
#wsgi app stack
app = RegistryManager(yourapp)
#inside your wsgi app
class yourapp(object):
def __call__(self, environ, start_response):
obj = someobject # The request-local object you want to access
# via yourpackage.myglobal
if environ.has_key('paste.registry'):
environ['paste.registry'].register(myglobal, obj)
paste.registry:61: (ERROR/3) Unknown directive type "code-block".
.. code-block:: Python
#sessions.py
Session = StackedObjectProxy()
# ... initialization code, etc.
# somemodule.py
import sessions
def somefunc():
session = sessions.Session._current_obj()
# ... tons of session access
colorizing: docs/html/paste/__init__.py.html
colorizing: docs/html/paste/pony.py.html
colorizing: docs/html/paste/request.py.html
colorizing: docs/html/paste/fixture.py.html
colorizing: docs/html/paste/gzipper.py.html
colorizing: docs/html/paste/session.py.html
colorizing: docs/html/paste/wsgilib.py.html
colorizing: docs/html/paste/httpserver.py.html
colorizing: docs/html/paste/recursive.py.html
colorizing: docs/html/paste/cascade.py.html
colorizing: docs/html/paste/fileapp.py.html
colorizing: docs/html/paste/cgiapp.py.html
colorizing: docs/html/paste/progress.py.html
colorizing: docs/html/paste/reloader.py.html
colorizing: docs/html/paste/modpython.py.html
colorizing: docs/html/paste/httpexceptions.py.html
colorizing: docs/html/paste/httpheaders.py.html
colorizing: docs/html/paste/errordocument.py.html
colorizing: docs/html/paste/evalexception/__init__.py.html
colorizing: docs/html/paste/cgitb_catcher.py.html
colorizing: docs/html/paste/lint.py.html
colorizing: docs/html/paste/auth/__init__.py.html
colorizing: docs/html/paste/util/__init__.py.html
colorizing: docs/html/paste/debug/__init__.py.html
colorizing: docs/html/paste/proxy.py.html
colorizing: docs/html/paste/urlmap.py.html
colorizing: docs/html/paste/response.py.html
colorizing: docs/html/paste/transaction.py.html
colorizing: docs/html/paste/url.py.html
colorizing: docs/html/paste/config.py.html
colorizing: docs/html/paste/urlparser.py.html
colorizing: docs/html/paste/translogger.py.html
colorizing: docs/html/paste/exceptions/__init__.py.html
colorizing: docs/html/paste/wsgiwrappers.py.html
colorizing: docs/html/paste/registry.py.html
>>> Source compiled.
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/var/log/sandbox/sandbox-28961.log"
open_wr: /root/.gconf/.testing.writeability
unlink: /root/.gconf/.testing.writeability
open_wr: /root/.gconfd/saved_state
open_wr: /root/.gconfd/saved_state
open_wr: /root/.gconfd/saved_state
open_wr: /root/.gconfd/saved_state.tmp
--------------------------------------------------------------------------------
* GNU info directory index is up-to-date.
* IMPORTANT: 12 config files in '/etc' need updating.
* See the CONFIGURATION FILES section of the emerge
* man page to learn how to update config files.
|
Last edited by richard.langly on Mon Nov 10, 2008 3:06 am; edited 1 time in total |
|
| Back to top |
|
 |
notHerbert
Advocate
Joined: 11 Mar 2008
Posts: 2228
Location: 45N 73W
|
| Posted: Sun Nov 02, 2008 9:08 pm Post subject: |
|
|
Have you tried re-emerging sandbox? | Code: | | emerge --oneshot sandbox |
As a last resort you can disable sandbox for pylons only | Code: | | FEATURES="-sandbox" emerge pylons |
|
|
| Back to top |
|
|
richard.langly
n00b
Joined: 05 Sep 2008
Posts: 26
|
| Posted: Tue Nov 04, 2008 1:12 am Post subject: |
|
|
So I could only do 'FEATURES="-sandbox" emerge pylons' to get past it, only to run into the following. And I do have pudge installed.
| Code: |
...
creating build/lib/pylons/templates/minimal_project/+package+/tests
copying pylons/templates/minimal_project/+package+/tests/__init__.py_tmpl -> build/lib/pylons/templates/minimal_project/+package+/tests
* Generating docs as requested...
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help
error: invalid command 'pudge'
*
* ERROR: dev-python/pylons-0.9.4.1-r1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 2439: Called die
* The specific snippet of code:
* "${python}" setup.py pudge || die "generating docs failed";
* The die message:
* generating docs failed
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/dev-python/pylons-0.9.4.1-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-python/pylons-0.9.4.1-r1/temp/environment'.
*
* Messages for package dev-python/pylons-0.9.4.1-r1:
*
* ERROR: dev-python/pylons-0.9.4.1-r1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 2439: Called die
* The specific snippet of code:
* "${python}" setup.py pudge || die "generating docs failed";
* The die message:
* generating docs failed
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/dev-python/pylons-0.9.4.1-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-python/pylons-0.9.4.1-r1/temp/environment'.
*
|
|
|
| Back to top |
|
|
notHerbert
Advocate
Joined: 11 Mar 2008
Posts: 2228
Location: 45N 73W
|
| Posted: Tue Nov 04, 2008 6:55 pm Post subject: |
|
|
| You could always try un-merging pudge, emerging pylons, then re-emerging pudge. |
|
| Back to top |
|
|
richard.langly
n00b
Joined: 05 Sep 2008
Posts: 26
|
| Posted: Tue Nov 04, 2008 8:58 pm Post subject: |
|
|
I did an 'emerge -C pudge', then tried 'FEATURES="-sandbox" emerge pylons' ... and still get ..
| Code: |
...
ld/lib/pylons/templates/minimal_project/+package+/tests
* Generating docs as requested...
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help
error: invalid command 'pudge'
*
* ERROR: dev-python/pylons-0.9.4.1-r1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 2439: Called die
* The specific snippet of code:
* "${python}" setup.py pudge || die "generating docs failed";
* The die message:
* generating docs failed
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/dev-python/pylons-0.9.4.1-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-python/pylons-0.9.4.1-r1/temp/environment'.
*
* Messages for package dev-python/pylons-0.9.4.1-r1:
*
* ERROR: dev-python/pylons-0.9.4.1-r1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 2439: Called die
* The specific snippet of code:
* "${python}" setup.py pudge || die "generating docs failed";
* The die message:
* generating docs failed
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/dev-python/pylons-0.9.4.1-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-python/pylons-0.9.4.1-r1/temp/environment'.
*
* GNU info directory index is up-to-date.
* IMPORTANT: 12 config files in '/etc' need updating.
* See the CONFIGURATION FILES section of the emerge
* man page to learn how to update config files.
|
|
|
| Back to top |
|
|
notHerbert
Advocate
Joined: 11 Mar 2008
Posts: 2228
Location: 45N 73W
|
| Posted: Tue Nov 04, 2008 9:15 pm Post subject: |
|
|
What if you try without the doc use flag? Because pudge is a dependency of pylons with the doc use flag.
If you need the doc flag enabled, then I suggest you file a bug report |
|
| Back to top |
|
|
richard.langly
n00b
Joined: 05 Sep 2008
Posts: 26
|
| Posted: Tue Nov 04, 2008 9:23 pm Post subject: |
|
|
| Tried that. Not working, seeing the same thing. No matter what I do, it's one error after another. |
|
| Back to top |
|
|
notHerbert
Advocate
Joined: 11 Mar 2008
Posts: 2228
Location: 45N 73W
|
| Posted: Tue Nov 04, 2008 10:14 pm Post subject: |
|
|
Strange, I emerge pylons with no problems today | Code: | genlop --list --date 1 day ago
Tue Nov 4 13:42:02 2008 >>> dev-python/paste-1.6
Tue Nov 4 13:43:01 2008 >>> dev-python/routes-1.8
Tue Nov 4 13:43:45 2008 >>> dev-python/simplejson-1.9.1
Tue Nov 4 13:44:29 2008 >>> dev-python/nose-0.10.4
Tue Nov 4 13:45:05 2008 >>> dev-python/formencode-1.0.1
Tue Nov 4 13:45:40 2008 >>> dev-python/beaker-0.9.4
Tue Nov 4 13:46:31 2008 >>> dev-python/cheetah-2.0.1
Tue Nov 4 13:47:02 2008 >>> dev-python/pastedeploy-1.3.1
Tue Nov 4 13:47:34 2008 >>> dev-python/webhelpers-0.3.4
Tue Nov 4 13:48:06 2008 >>> dev-python/pastescript-1.6.2
Tue Nov 4 13:49:00 2008 >>> dev-python/myghty-1.1
Tue Nov 4 13:49:50 2008 >>> dev-python/pylons-0.9.4.1-r1
|
What about the rest of your system? Can you run | Code: | emerge --sync
emerge-uDN @system @world (emerge -uDN world for <portage-2.2)
emerge --depclean
revdep-rebuild |
Do you get errors from that? |
|
| Back to top |
|
|
richard.langly
n00b
Joined: 05 Sep 2008
Posts: 26
|
| Posted: Tue Nov 04, 2008 10:22 pm Post subject: |
|
|
Well, I guess I might as well update the entire system. I usually do this once every 3 months and something is always broken, I know I have blocks right now.
I'm on an amd64 where pylons and all those dependencies you listed are masked. I wonder if that is a difference.
Here's some problems I'm seeing, and portage pylons only goes to 0.9.4 and that doc problem is listed. So thought I'd try a later.
https://bugs.gentoo.org/show_bug.cgi?id=176640 |
|
| Back to top |
|
|
notHerbert
Advocate
Joined: 11 Mar 2008
Posts: 2228
Location: 45N 73W
|
| Posted: Wed Nov 05, 2008 6:58 am Post subject: |
|
|
Yep, update your system, fix it all real nice, then you could play around with unmasking all the pylons dependencies. Try different versions is one fails. Try them one-by-one, it might even be fun.  |
|
| Back to top |
|
|
richard.langly
n00b
Joined: 05 Sep 2008
Posts: 26
|
| Posted: Sun Nov 09, 2008 5:14 am Post subject: help emerging pylons |
|
|
Still trying to get pylons installed, I just updated my entire system (world), over 300 packages, and I'm still getting the exact same errors before when trying to install pylons.
I've tried ...
| Code: |
FEATURES="-sandbox" emerge pylons
|
Only to get past this error ...
| Code: |
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/var/log/sandbox/sandbox-29991.log"
open_wr: /root/.gconf/.testing.writeability
unlink: /root/.gconf/.testing.writeability
open_wr: /root/.gconfd/saved_state
open_wr: /root/.gconfd/saved_state
open_wr: /root/.gconfd/saved_state.tmp
--------------------------------------------------------------------------------
|
Which then does continue to build pylons, and when it gets to pylons leads to this error ...
| Code: |
* Generating docs as requested...
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help
error: invalid command 'pudge'
*
* ERROR: dev-python/pylons-0.9.5 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 2438: Called die
* The specific snippet of code:
* "${python}" setup.py pudge || die "generating docs failed";
* The die message:
* generating docs failed
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/dev-python/pylons-0.9.5/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-python/pylons-0.9.5/temp/environment'.
* This ebuild is from an overlay: '/usr/local/portage/'
*
* Messages for package dev-python/pylons-0.9.5:
*
* ERROR: dev-python/pylons-0.9.5 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 2438: Called die
* The specific snippet of code:
* "${python}" setup.py pudge || die "generating docs failed";
* The die message:
* generating docs failed
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/dev-python/pylons-0.9.5/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-python/pylons-0.9.5/temp/environment'.
* This ebuild is from an overlay: '/usr/local/portage/'
*
* GNU info directory index is up-to-date.
|
I then re-emerge pudge, but still get the same error msg.
Anyone have ideas ? |
|
| Back to top |
|
|
desultory
Bodhisattva
Joined: 04 Nov 2005
Posts: 9410
|
| Posted: Sun Nov 09, 2008 6:48 am Post subject: |
|
|
| Merged the above post. |
|
| Back to top |
|
|
yngwin
Retired Dev
Joined: 19 Dec 2002
Posts: 4572
Location: Suzhou, China
|
| Posted: Sun Nov 09, 2008 11:17 pm Post subject: |
|
|
| richard.langly wrote: | | Well, I guess I might as well update the entire system. I usually do this once every 3 months |
You really should do this at least once a month. Little problems like blocks should be easier to deal with when not letting them stack up.
_________________
"Those who deny freedom to others deserve it not for themselves." - Abraham Lincoln
Free Culture | Defective by Design | EFF |
|
| Back to top |
|
|
richard.langly
n00b
Joined: 05 Sep 2008
Posts: 26
|
| Posted: Tue Nov 11, 2008 5:49 pm Post subject: |
|
|
| bump ... anyone have ideas on my last message in this thread? |
|
| Back to top |
|
|
notHerbert
Advocate
Joined: 11 Mar 2008
Posts: 2228
Location: 45N 73W
|
| Posted: Tue Nov 11, 2008 9:56 pm Post subject: Re: help emerging pylons |
|
|
| richard.langly wrote: |
* The specific snippet of code:
* "${python}" setup.py pudge || die "generating docs failed";
* The die message:
* generating docs failed |
Try without the doc use flag. I know you tried that before upgrading your system, but it should work now. |
|
| Back to top |
|
|
|
Portage & Programming
