hello everyone,

i have to make an rpm for our software and install it on another linux
based pc.

i have created the following .spec file for it....


%define name dashboard
%define version 2.0.1
%define release 1mdk

Name: %{name}
Summary: Tools for converting websites from using GIFs to using PNGs
Version: %{version}
Release: %{release}
Source0: %{name}-%{version}.tar.gz
Group: Applications/Multimedia
License: MIT-like
Requires: python

%description
Antispam Dashboard Installation.



%prep
rm -rf /usr/mohan
mkdir -p /usr/mohan/dashboard-2.0.1

cd /usr/src/redhat/SOURCES
cp dashboard-2.0.1.tar.gz /usr/mohan/dashboard-2.0.1
cd /usr/mohan/dashboard-2.0.1
gunzip dashboard-2.0.1.tar.gz
tar -xvf dashboard-2.0.1.tar

%files
/usr/mohan/dashboard-2.0.1/dashboard-2.0.1/edituserlist.jsp
%defattr(-,root,root,0755)


Now my Problem is that when i execute the above .spec file using the
command rpmbuild -ba <filename>.spec

it sometimes works fine and in the end gives me the following messages:

Wrote: /usr/src/redhat/SRPMS/dashboard-2.0.1-1mdk.src.rpm
Wrote: /usr/src/redhat/RPMS/i586/dashboard-2.0.1-1mdk.i586.rpm

but sometimes it doesn't work fine at all and gives me a message:

Checking for unpackaged file(s): /usr/lib/rpm/check-files %{buildroot}
getOutputFrom(): Broken pipe

As, a result i am not able to get my rpm's in event of the above message.

i am confused and don't know as to why this broken pipe problem is there,
as my .spec file appears to be correct(otherwise how does it executes correctly sometimes?)

Therefore as a result of mine issuing the above rpmbuild -ba command on
this .spec file , it works some times and some times doesen't??

why this unpredictability...............???? i am confused and as a result is unable to finalize my work, even though it appears to be complete..........


plz help....me...

i am working on red hat linux and kernel version is :
2.4.20-8

thanks in anticipation
sd







"newex-gif2.spec" 44L, 937C 1,1 Top

The broken pipe error is caused when the output of a program (A) is being send to another program (B). Program B is exiting (crashing) before program A has finished producing all its data.

A problem with your .spec file shouldn't cause this problem. One possibility is a bug in your RPM tools; make sure that you have installed any available updates.

Given that the problem is intermittent, the most likely explanation here, I'm afraid, is a hardware problem. This kind of error (one program crashing intermittently) is most commonly caused by an intermittent fault in your hardware; RAM being the most common culprit, followed by an overclocked CPU. You might try running a decent RAM tester for a few hours. Another test you can do is attempt to compile a complex program like gcc from source (gcc uses lots of pointers so it tends to break if your RAM isn't working too well); it should get through the compile process in one go. If it fails intermittently, but then fails at a different point after reissuing the make command, then you know your memory isn't good.