[4suite] Re: Amara Package Build

[Uche Ogbuji]

cc'ing the list.


Mike Freitas wrote:
> Hi Uche,
>     Thanks for the reply.  I appreciate your help.  I was able to build
> 4Suite, but the rpms weren't building.  I get this error,
> 
> # python2.4 setup.py bdist --formats=rpm
> running bdist

I'm not sure bdist_rpm has worked for ages.  Does anyone else remember?

Is building an egg [1] an option?  You're using Python 2.4, which does
support eggs.  4Suite 1.0rc4 is available as in egg form, and can create
a custom egg for you, as well.

Anyone else have any thoughts?

[1] http://peak.telecommunity.com/DevCenter/PythonEggs

--Uche

> running bdist_rpm
> Traceback (most recent call last):
>   File "setup.py", line 91, in ?
>     requires_python=['>=2.2.1'],
>   File "/usr/local/lib/python2.4/distutils/core.py", line 149, in setup
>     dist.run_commands()
>   File "/root/4Suite/Ft/Lib/DistExt/PackageManager.py", line 547, in
> run_commands
>     dist.run_command(command)
>   File "/usr/local/lib/python2.4/distutils/dist.py", line 966, in
> run_command
>     cmd_obj.run()
>   File "/usr/local/lib/python2.4/distutils/command/bdist.py", line 146,
> in run
>     self.run_command(cmd_name)
>   File "/usr/local/lib/python2.4/distutils/cmd.py", line 333, in run_command
>     self.distribution.run_command(command)
>   File "/usr/local/lib/python2.4/distutils/dist.py", line 966, in
> run_command
>     cmd_obj.run()
>   File "/root/4Suite/Ft/Lib/DistExt/BDistRpm.py", line 68, in run
>     (spec_path,
>   File "/root/4Suite/Ft/Lib/DistExt/BDistRpm.py", line 226, in
> _make_spec_file
>     for pkg in self.distribution.sub_packages:
> AttributeError: Dist instance has no attribute 'sub_packages'
> 
> 
> The tarballs were created ok, but I would prefer to have rpm's. Any
> ideas?  Thanks.
>        Mike
> 
> Uche Ogbuji wrote:
>> Mike Freitas wrote:
>>   
>>>       I'm trying to build a set of rpms so that they install all the
>>> files under /usr/bin/python2.4/site-packages/  I've tried using every
>>> setup.py config variable with no luck.  No matter how i setup
>>> config.cache, I always get these errors on install:
>>>
>>>
>>> rpm -ivh --test Amara-Amara-1.1.7-1.i386.rpm Amara-Xml-1.1.7-1.i386.rpm
>>> Preparing...                ###########################################
>>> [100%]
>>>        file /usr/bin/4xml from install of Amara-Xml-1.1.7-1 conflicts
>>> with file from package 4Suite-1.0-3
>>>        file /usr/bin/4xpath from install of Amara-Xml-1.1.7-1 conflicts
>>> with file from package 4Suite-1.0-3
>>>        file /usr/bin/4xslt from install of Amara-Xml-1.1.7-1 conflicts
>>> with file from package 4Suite-1.0-3
>>>        file /usr/bin/4xupdate from install of Amara-Xml-1.1.7-1
>>> conflicts with file from package 4Suite-1.0-3
>>>
>>> I know if I remove the 4Suite Package this will solve the problem, but
>>> we also have multiple versions of python and want to be able to easily
>>> install support for all of them.  I tried using the amaraonly setup, but
>>> I get this error:
>>>
>>> python2.4 amaraonly-setup.py config --home /usr/lib/python2.4/site-packages
>>> Traceback (most recent call last):
>>>  File "amaraonly-setup.py", line 3, in ?
>>>    from lib import __version__
>>> ImportError: No module named lib
>>>
>>>
>>> I'm not a python developer, I'm a Sysadmin with some programming skills,
>>> but i've never worked with python.  I'm sure I'm missing something easy
>>> to do this.  How do I build this rpm to install in this dir:
>>> /usr/bin/python2.4/site-packages/
>>>     
>>
>> Hi,
>>
>> Sorry you're having trouble.  For your case I do think you should use
>> the standalone packages.  Unfortunately I think you're caught in a bit
>> of a bind.  There were problems in the 1.1.7 set-up, which I fixed in a
>> version (1.1.8) that was never actually released.  I'm sitting on a
>> version, 1.1.9, which depends on some changes in the latest 4Suite
>> release candidates.  We're planning to release 4Suite 1.0 soon, and then
>> Amara 1.1.9 (and 1.2) would follow shortly.
>>
>> I guess one option is for you to build separate RPMs for the 4Suite and
>> Amara CVS snapshots:
>>
>> ftp://ftp.4suite.org/pub/cvs-snapshots/
>> http://4suite.org/docs/4SuiteCVS.xml
>>
>> Another is for you to wait a few days and build against proper releases
>> (I don't really expect much to change between today's CVS and the releases).
>>
>> As a worst case, I could also scrounge up patches to Amara 1.1.7 you
>> could incorporate into your RPM for stand-alone install, but
>> unfortunately it may be a few days before I can get to that, by which
>> time we'd likely have full releases of the new versions, anyway.
>>
>> Let me know what you think/try.


-- 
Uche Ogbuji                               Fourthought, Inc.
http://uche.ogbuji.net                    http://fourthought.com
http://copia.ogbuji.net                   http://4Suite.org
Articles: http://uche.ogbuji.net/tech/publications/