[cpif] Como arrancar CPIF

Mi nospa pipisspam at gmail.com
Fri Jun 26 00:28:25 CEST 2015


La 2.7 creo que la 3.0 no sirve para este codigo. Tampoco se si
pasarlo a 3.0 tendria alguna ventaja sustancial.

Este tutorial esta muy bien no se si te hace falta repasar algo.

Buenas noches.


El 26/6/15, Miguel Manzano <mmanzano at gmail.com> escribió:
> Yo sin código andaba a ciegas. Mañana miraré a ver si me aclaro. Cuanto
> menos invoquemos a Jcea mejor. Jajaja :D ¿Qué versión de Python estás
> usando?
> El 26/06/2015 00:13, "Mi nospa" <pipisspam at gmail.com> escribió:
>
>> Realmente no me queda claro donde esta la base de datos.
>>
>> Esa opcion no se si hay que pasarsela al pip o al setup.py, que es un
>> programa que cuando los busco en el /tmp, ya ha desaparecido.
>>
>> Gracias por el enlace. A ver si avanzo algo.
>>
>>
>>
>> 2015-06-25 20:29 GMT+02:00, Miguel Manzano <mmanzano at gmail.com>:
>> >
>> http://stackoverflow.com/questions/15195530/sudo-easy-install-bsddb3-error-cant-find-a-local-berkeley-db-installation
>> >
>> > ¿Has probado esto?
>> >
>> > Saludos.
>> >
>> > 2015-06-25 19:58 GMT+02:00 Miguel Manzano <mmanzano at gmail.com>:
>> >
>> >> Ahora es cuando me echáis. ¿Como te has bajado el proyecto? ;D
>> >>
>> >> svn checkout svn://svn.jcea.es/jcea/cpif/trunk cpif-trunk
>> >> svn: E670002: Unable to connect to a repository at URL 'svn://
>> >> svn.jcea.es/jcea/cpif/trunk'
>> >> svn: E670002: Nombre de máquina 'svn.jcea.es' desconocido
>> >>
>> >> :(
>> >>
>> >> Estoy con el mismo problema que tu en docker pero me parece que igual
>> hay
>> >> que bajarse primero el tar.gz, ponerlo donde dice y pasarle el
>> >> parámetro
>> >> que se recomienda (--berkeley-db=/path/to/bsddb) en el error y
>> >> entonces
>> >> instalar bsddb3 :D
>> >>
>> >> 2015-06-25 17:30 GMT+02:00 Mi nospa <pipisspam at gmail.com>:
>> >>
>> >>> El 21/6/15, Jesus Cea <jcea at jcea.es> escribió:
>> >>> > On 11/06/15 19:11, Mi nospa wrote:
>> >>> >> storage                   - Libraries to interact with Enterprise
>> >>> Storage
>> >>> >>                             Arrays, FC Switches and Servers.
>> >>> >>   INSTALLED: 0.0.4.3
>> >>> >>   LATEST:    0.0.5a2
>> >>> >
>> >>> > No sé qué es eso que has instalado pero no es nada que necesite
>> >>> > CPIF.
>> >>>
>> >>> >
>> >>> > Podría considerar retomar el proyecto si se contase con el apoyo
>> >>> > adecuado pero lo cierto es que os veo verdísimos :-).
>> >>>
>> >>>
>> >>> No hace falta que lo digas, por lo menos yo si estoy verdisimo :P
>> >>>
>> >>>
>> >>> Define apoyo adecuado. :)
>> >>>
>> >>>
>> >>> Voy a poner los errores que me da .
>> >>>
>> >>> ------
>> >>> dani at Lubuntu:~/mercurial/cpif$ cd frontend-web/
>> >>> dani at Lubuntu:~/mercurial/cpif/frontend-web$ python init.py
>> >>> /home/dani/mercurial/cpif/backend/upgrade.py 0
>> >>> Traceback (most recent call last):
>> >>>   File "init.py", line 97, in <module>
>> >>>     main()
>> >>>   File "init.py", line 31, in main
>> >>>
>> >>>
>> dummy,dummy,monitor=storage.storage_and_monitor(os.path.join(os.path.pardir,"backend","db"))
>> >>> AttributeError: 'module' object has no attribute
>> >>> 'storage_and_monitor'
>> >>> dani at Lubuntu:~/mercurial/cpif/frontend-web$ sudo pip install durus
>> >>> bsddb3
>> >>> Requirement already satisfied (use --upgrade to upgrade): durus in
>> >>> /usr/local/lib/python2.7/dist-packages
>> >>> Downloading/unpacking bsddb3
>> >>>   Downloading bsddb3-6.1.0.tar.gz (340kB): 340kB downloaded
>> >>>   Running setup.py (path:/tmp/pip_build_root/bsddb3/setup.py)
>> >>> egg_info
>> >>> for package bsddb3
>> >>>     Can't find a local Berkeley DB installation.
>> >>>     (suggestion: try the --berkeley-db=/path/to/bsddb option)
>> >>>     Complete output from command python setup.py egg_info:
>> >>>     Can't find a local Berkeley DB installation.
>> >>>
>> >>> (suggestion: try the --berkeley-db=/path/to/bsddb option)
>> >>>
>> >>> ----------------------------------------
>> >>> Cleaning up...
>> >>> Command python setup.py egg_info failed with error code 1 in
>> >>> /tmp/pip_build_root/bsddb3
>> >>> Storing debug log for failure in /home/dani/.pip/pip.log
>> >>> dani at Lubuntu:~/mercurial/cpif/frontend-web$ ls ../backend/
>> >>> database.py  durus-berkeleydbstorage                  monitor.py
>> >>> storage.py
>> >>> db           durus-berkeleydbstorage-20070503.tar.gz  smtp.py
>> >>>  upgrade.py
>> >>> dani at Lubuntu:~/mercurial/cpif/frontend-web$ ls ../backend/db
>> >>> dani at Lubuntu:~/mercurial/cpif/frontend-web$ ls
>> >>> ../backend/durus-berkeleydbstorage
>> >>> berkeleydb_storage.py   KNOW_HOW-DURUS  server.py  test3.py
>> >>> UPGRADING
>> >>> berkeleydb_storage.pyc  LICENSE         test1.py   test4.py
>> >>> CHANGES                 README          test2.py   TODO
>> >>>
>> >>> dani at Lubuntu:~/mercurial/cpif/backend$ cat
>> >>> durus-berkeleydbstorage/berkeleydb_storage.py |grep "DB_LOG"
>> >>>       self._dbenv.log_set_config(bsddb.db.DB_LOG_AUTOREMOVE,True)
>> >>> dani at Lubuntu:~/mercurial/cpif/backend$
>> >>>
>> >>> Gracias de antemano por echarle un vistazo.
>> >>> _______________________________________________
>> >>> cpif mailing list
>> >>> cpif at jcea.es -- http://www.jcea.es/wikis/cpif/
>> >>> https://mailman.jcea.es/listinfo/cpif
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Miguel Manzano Garcia
>> >>
>> >
>> >
>> >
>> > --
>> > Miguel Manzano Garcia
>> >
>> _______________________________________________
>> cpif mailing list
>> cpif at jcea.es -- http://www.jcea.es/wikis/cpif/
>> https://mailman.jcea.es/listinfo/cpif
>>
>


More information about the cpif mailing list