← Back to team overview

oship-dev team mailing list archive

Re: Problem to install oship

 

In case you are not monitoring the Grok-dev list, there was a mistake
made in the last alpha where zope.container was added.   It should have
continued to use zope.app.container.  

I didn't see this issue because I have several things I'm working on and
OSHIP found the right one. :-(

There is a Grok 1.0a4 coming out within the next day or two and I will
retest in a clean environment to be sure all is well again with the
versions.cfg.

Oh the fun working on alpha software with alpha building blocks! ;-)

--Tim
  




On Mon, 2009-05-18 at 16:34 -0300, Wagner Francisco wrote:
> Hi Tim,
> 
> I added an old zope.container version in the versions.cfg and
> everything seemed working. But when I started the server and accessed
> the address I didn't can login in the system. I put the user and
> password and the system ask them again. Perhaps the problem is because
> my internet connection goes down while I was installing (maybe there
> is some corrupted file...). I will try to repeat the proccess. If it
> doesn't work, there is no problem, I install Ubuntu 8.10 in a virtual
> machine! 
> 
> Thanks for your help,
> 
> 
> Wagner.
> 
> 
> 
> 
> 2009/5/18 Tim Cook <timothywayne.cook@xxxxxxxxx>
>         Hi Wagner,
>         
>         Thanks for your persistence.
>         
>         As I am progressing through the relstorage branch...I am
>         seeing how much
>         churn there is going on in the Zope3 environment.  One reason
>         why it is
>         also good to be a member of the grok list and zope lists.
>         
>         I must be honest here and say that this is a difficult time
>         for us at
>         OSHIP.  We depend on so many underlying components.  But this
>         is
>         normally a GOOD THING(tm)
>         
>         and will be in the future. There are THOUSANDS of Zope
>         implementations
>         and many of them running very high end, high availability
>         sites.  It too
>         often goes unnoticed.
>         
>         
>         Remember that we are working on alpha software based on alpha
>         software
>         that is based on beta software.
>         
>         
>         So; can you get more bleeding edge than that? :-)
>         
>         
>         In healthcare we are looking for stability and consistency.
>         But in the
>         world of OSHIP we are seeing such a move in innovation that we
>         cannot
>         ignore it.
>         
>         [I hope this translates]
>         
>         As a bit of a "pep-rally"; OSHIP will become the only really
>         open
>         source, spec compliant, application dev environment available
>         for
>         openEHR. Simply compare it to the Java implementation and the
>         Eiffel
>         implementation.  Sadly, the C# implementation is closed
>         source.
>         
>         I just upgraded (probably a bad choice of words) to Ubuntu
>         9.10.   If I
>         was really smart I would not have done that.  It is a mess
>         going from a
>         Python 2.5 centered OS to a 2.6 centered OS while trying to
>         work in a
>         Python 2.5 dev environment.  I am still working, but my
>         solution is so
>         specific and convoluted it isn't worth repeating here.
>         
>         The reality is that MANY of our components are going to be
>         Python 2.5
>         only for quite awhile.
>         
>         I believe that I can come up with a solution for everyone
>         within the
>         next few days.
>         
>         Cheers,
>         Tim
>         
>         
>         On Mon, 2009-05-18 at 14:30 -0300, Wagner Francisco wrote:
>         > Thanks for the quick answer, Tim! But I still have some
>         problems here.
>         > I installed python 2.5.4 and then when I used the virtualenv
>         I
>         > specified the python version with the -p argument. I run the
>         python
>         > bootstrap.py with the python 2.5 but I am having a version
>         conflict
>         > problem. The problem is:
>         >
>         > Error: There is a version conflict.
>         > We already have: zope.lifecycleevent 3.4.0
>         > but zope.container 3.8.2 requires
>         'zope.lifecycleevent>=3.5.2'.
>         >
>         > I removed the directories from /tmp and I restarted
>         everything about
>         > oship (I removed the oshipenv directory and download it
>         again).  I
>         > already tried to change the versions.cfg file and change the
>         > zope.lifecycleevent version, but I saw other errors like
>         this.
>         >
>         > Does Grok use another temporary directory? Or can you send
>         me another
>         > versions.cfg file?
>         >
>         >
>         > Thank you!
>         >
>         >
>         >
>         >
>         > 2009/5/17 Tim Cook <timothywayne.cook@xxxxxxxxx>
>         >         On Sun, 2009-05-17 at 15:10 -0300, Wagner Francisco
>         wrote:
>         >         > Hello. I am trying to install OSHIP again and I am
>         having
>         >         some problems. I am using Ubuntu 9.04 and python
>         2.6.2.
>         >
>         >
>         >
>         >         My apologies.  When we moved to Launchpad a I
>         rewrote the
>         >         install
>         >         instructions I see that I left out the Python 2.5.x
>         >         requirement.
>         >
>         >         I have corrected the install FAQ.
>         >
>         >         Cheers,
>         >         Tim
>         >
>         >
>         >         --
>         >         Timothy Cook, MSc
>         >         Health Informatics Research & Development Services
>         >         LinkedIn
>         Profile:http://www.linkedin.com/in/timothywaynecook
>         >         Skype ID == timothy.cook
>         >
>         **************************************************************
>         >         *You may get my Public GPG key from  popular
>         keyservers or   *
>         >         *from this link
>         http://timothywayne.cook.googlepages.com/home*
>         >
>         **************************************************************
>         >
>         
>         > _______________________________________________
>         > Mailing list: https://launchpad.net/~oship-dev
>         > Post to     : oship-dev@xxxxxxxxxxxxxxxxxxx
>         > Unsubscribe : https://launchpad.net/~oship-dev
>         > More help   : https://help.launchpad.net/ListHelp
>         --
>         
>         Timothy Cook, MSc
>         Health Informatics Research & Development Services
>         LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook
>         Skype ID == timothy.cook
>         **************************************************************
>         *You may get my Public GPG key from  popular keyservers or   *
>         *from this link http://timothywayne.cook.googlepages.com/home*
>         **************************************************************
>         
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~oship-dev
> Post to     : oship-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~oship-dev
> More help   : https://help.launchpad.net/ListHelp
-- 
Timothy Cook, MSc
Health Informatics Research & Development Services
LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook 
Skype ID == timothy.cook 
**************************************************************
*You may get my Public GPG key from  popular keyservers or   *
*from this link http://timothywayne.cook.googlepages.com/home*
**************************************************************

Attachment: signature.asc
Description: This is a digitally signed message part


References