I just found the following email from you earlier in the
day. I still
think, if you're going to build at all, it's worth trying
the rpm src,
and editing its directives to use python 2.4. I don't think
it will
work, but worth a try. If it does, it gives you an rpm,
which would be
useful.
I'm sorry I didn't see all your email about your attempts
via Fedora
development before I saw your email that said you tried
building from
the tar ball. That certainly sheds a different light on your
steps, and
my comments to you were unnecessarily stringent in this
light. My
apologies for that.
PS: Still think your best bet is a vm.
Janina
Donald Raikes writes:
> Hi,
>
> Since the yum upgrade didn't work, I decided to try
building orca from a tarball.
>
> Steps I took:
>
> downloaded atk-1.21.92.tar.gz
> extracted configured compiled and installed it.
>
> downloaded at-spi-1.21.92.tar.gz
> tried to configure it, but it needed libbonobo 2.0 or
later
>
> downloaded libbonobo-2.19.6.tar.gz
> extracted configured compiled and installed it.
> configured compiled and installed at-spi now.
>
> downloaded orca-2.21.92.tar.gz
> extracted configured compiled and installed it.
>
> everything looked good so far.
>
> Now I tried running orca from the console to configure
it.
> I got the following error:
>
> Traceback (most recent call last):
> File "<string>", line 1, in ?
> File
"/usr/local/lib/python2.4/site-packages/orca/orca.py&qu
ot;, line 54, in ?
> import pyatspi
> File
"/usr/local/lib/python2.4/site-packages/pyatspi/__init_
_.py", line 44, in ?
> reg =
bonobo.activation.activate_from_id(REGISTRY_IID, 0, 0)
> Bonobo.GeneralError
>
> I ran updatedb and then did a locate pyatspi, and this
is what I found:
> /usr/local/lib/python2.4/site-packages/pyatspi
>
/usr/local/lib/python2.4/site-packages/pyatspi/__init__.py
>
/usr/local/lib/python2.4/site-packages/pyatspi/__init__.pyc
>
/usr/local/lib/python2.4/site-packages/pyatspi/__init__.pyo
>
/usr/local/lib/python2.4/site-packages/pyatspi/accessible.py
>
/usr/local/lib/python2.4/site-packages/pyatspi/accessible.py
c
>
/usr/local/lib/python2.4/site-packages/pyatspi/accessible.py
o
>
/usr/local/lib/python2.4/site-packages/pyatspi/constants.py
>
/usr/local/lib/python2.4/site-packages/pyatspi/constants.pyc
>
/usr/local/lib/python2.4/site-packages/pyatspi/constants.pyo
>
/usr/local/lib/python2.4/site-packages/pyatspi/event.py
>
/usr/local/lib/python2.4/site-packages/pyatspi/event.pyc
>
/usr/local/lib/python2.4/site-packages/pyatspi/event.pyo
>
/usr/local/lib/python2.4/site-packages/pyatspi/registry.py
>
/usr/local/lib/python2.4/site-packages/pyatspi/registry.pyc
>
/usr/local/lib/python2.4/site-packages/pyatspi/registry.pyo
>
/usr/local/lib/python2.4/site-packages/pyatspi/utils.py
>
/usr/local/lib/python2.4/site-packages/pyatspi/utils.pyc
>
/usr/local/lib/python2.4/site-packages/pyatspi/utils.pyo
>
> How do I tell orca that pyatspi is there?
>
> -----Original Message-----
> From: Janina Sajka [mailto:janina a11y.org]
> Sent: Thursday, March 06, 2008 9:15 AM
> To: Willem van der Walt
> Cc: Janina Sajka; Donald Raikes; orca-listgnome.org
> Subject: Re: [orca-list] upgrading orca in oracle
enterprise linux
>
>
> Agree with "should." But for various reasons,
including human error
> specifying things like "requires" statements,
we've certainly seen
> highly inappropriate dependencies being pulled in. Most
recently we've
> seen this with development builds of xulrunner and
firefox 3 from
> development.
>
> Janina
>
> Willem van der Walt writes:
> >
> > I think it would mostly upgrade stuff and should
at the end of the day not
> > install a lot of extra stuff.
> > The oracle servers these days normally have X on
them anyway.
> > As stated before, my Redhat and Oracle knowledge
is a bit dated, but I
> > don't think it has changed that mutch in the
meanwhile.
> > Regards, Willem
> >
> > On Thu, 6 Mar 2008, Janina Sajka wrote:
> >
> > > This is certainly woprth looking into. It may
be that yum will want to
> > > install far too many packages. But, you
should try enabling the
> > > development repository for Fedora and see. Do
that and issue:
> > >
> > > yum --disablerepo='*'
--enablerepo=development upgrade orca
> > >
> > > and see how much yum needs to pull in. If
you're looking at a handful of
> > > packages, you're good to go.
> > >
> > > Janina
> > >
> > > Willem van der Walt writes:
> > > > Hi,
> > > > I would suggest that you get the stuff
from Fedora, likely the latest
> > > > version.
> > > > There should be a rpm for atspi and all
the needed dependancies. There
> > > > should also be an rpm for orca itsellf.
> > > > I am a bit out-dated with the Redhat
stuff, but the Rel versions is fed by
> > > > the tested Fedora stuff.
> > > > Regards, Willem
> > > >
> > > >
> > > > On Wed, 5 Mar 2008, Donald Raikes
wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > Sorry if this is a duplicate of
earlier questions, but I haven't been able to locate any
info on this.
> > > > >
> > > > > I have been trying to find any
notes on how to upgrade orca for oracle enterprise linux.
> > > > >
> > > > > OEL5 is based on rhel5, but with
some oracle specific tweaks.
> > > > > The version of orca installed by
default is orca-1.0.0-el5.
> > > > >
> > > > > A couple of weeks ago I tried to
compile orca 2.21 and had issues with pyatspi which I could
never get resolved.
> > > > >
> > > > > Is there a specific list of
packages I absolutely need to compile and which order they
should be compiled in?
> > > > >
> > > > >
> > > > >
_______________________________________________
> > > > > Orca-list mailing list
> > > > > Orca-listgnome.org
> > > > > http
://mail.gnome.org/mailman/listinfo/orca-list
> > > > > Visit http://live.gnome.org/Orca
for more information on Orca
> > > > >
> > > >
> > > > --
> > > > This message is subject to the CSIR's
copyright terms and conditions, e-mail legal notice, and
implemented Open Document Format (ODF) standard.
> > > > The full disclaimer details can be found
at http://www.csi
r.co.za/disclaimer.html.
> > > >
> > > > This message has been scanned for
viruses and dangerous content by MailScanner,
> > > > and is believed to be clean.
MailScanner thanks Transtec Computers for their support.
> > > >
> > > >
_______________________________________________
> > > > Orca-list mailing list
> > > > Orca-listgnome.org
> > > > http
://mail.gnome.org/mailman/listinfo/orca-list
> > > > Visit http://live.gnome.org/Orca
for more information on Orca
> > >
> > > --
> > >
> > > Janina
Sajka, Phone: +1.202.595.7777; sip:janinaa11y.org
> > > Partner, Capital Accessibility LLC http://CapitalAccessi
bility.Com
> > >
> > > Marketing the Owasys 22C talking screenless
cell phone in the U.S. and Canada
> > > Learn more at http://ScreenlessPhone.Com
> > >
> > > Chair, Open Accessibility janinaa11y.org
> > > Linux Foundation http://a11y.org
> > >
> >
> > --
> > This message is subject to the CSIR's copyright
terms and conditions, e-mail legal notice, and implemented
Open Document Format (ODF) standard.
> > The full disclaimer details can be found at http://www.csi
r.co.za/disclaimer.html.
> >
> > This message has been scanned for viruses and
dangerous content by MailScanner,
> > and is believed to be clean. MailScanner thanks
Transtec Computers for their support.
>
> --
>
> Janina Sajka, Phone: +1.202.595.7777; sip:janinaa11y.org
> Partner, Capital Accessibility LLC http://CapitalAccessi
bility.Com
>
> Marketing the Owasys 22C talking screenless cell phone
in the U.S. and Canada
> Learn more at http://ScreenlessPhone.Com
>
> Chair, Open Accessibility janinaa11y.org
> Linux Foundation http://a11y.org
--
Janina Sajka, Phone: +1.202.595.7777; sip:janinaa11y.org
Partner, Capital Accessibility LLC http://CapitalAccessi
bility.Com
Marketing the Owasys 22C talking screenless cell phone in
the U.S. and Canada
Learn more at http://ScreenlessPhone.Com
Chair, Open Accessibility janinaa11y.org
Linux Foundation http://a11y.org
_______________________________________________
Orca-list mailing list
Orca-listgnome.org
http
://mail.gnome.org/mailman/listinfo/orca-list
Visit http://live.gnome.org/Orca
for more information on Orca
|