Can you tell us more. Perhaps share an example that packages web2py
On Tuesday, 28 August 2012 23:05:16 UTC-5, LightDot wrote:
>
> I'm distributing and supporting a project made with web2py as a set of
> RPMs (RHEL/CentOS/SL) for a while now. No big problems... I use Mock on SL6
> to generate the RPMs.
>
> This project is fairly complex and involves much more than just web2py
> app, so my spec files wouldn't be applicaple straight away. But the parts
> that concern web2py itself are straightforward. I just wrote the spec files
> from blank, according to Fedora / RHEL standards. Their rpm/spec
> documentation is pretty good.
>
> As to your error - it seems that the string "of secure database-driven
> web-based applications, written and" gets misinterpreted as a tag. I assume
> it's a part of the textual description that should be under a %*
> description* tag..? Can't say what causes this without looking at the
> spec file, though.
>
> Regards,
> Ales
>
>
> On Wednesday, August 29, 2012 5:26:12 AM UTC+2, thinkwell wrote:
>>
>> Hello everyone,
>>
>> The report feature I've been toiling over is now finished - YEA! and
>> ready to be to deployed to the /opt/www/web2py directory of the various
>> machines. This is a task for puppet, which we use for config & package
>> management as it handles RPMs and custom repos extremely well, so that was
>> my plan for deploying this project.
>>
>> My thought was to make an RPM by running setup.py bdist_rpm, but even a
>> fresh copy of web2py throws errors like:
>>
>> error: line 7: Unknown tag: of secure database-driven web-based
>> applications, written and
>> error: query of specfile build/bdist.linux-i686/rpm/SPECS/web2py.spec
>> failed, can't parse
>> error: Failed to execute: "rpm -q --qf
>> '%{name}-%{version}-%{release}.src.rpm
>> %{arch}/%{name}-%{version}-%{release}.%{arch}.rpm\\n' --specfile
>> 'build/bdist.linux-i686/rpm/SPECS/web2py.spec'"
>>
>> Any suggestions? I'm green when it comes to making noarch RPMs with
>> rpmbuild. This is a nonstandard use-case I suppose because it's getting
>> deployed somewhat as an application on many servers. I'm open to advice.
>>
>
--
