Bug 114704

OK, I track it down a little.

I can build it OK unless I use a slightly modified form of Mike
Harris's stuff for rpmbuild-nonroot ~/.rpmmacros

The actual error message is:

awk: cmd. line:2: fatal: cannot open file
`/home/gc/devel/rpmbuild/rhn-applet-%{version}/version' for reading
(No such file or directory)
error: line 12: Empty tag: Version:

The following is what is being used for ~/.rpmmacros

# adapt some stuff from Mike A. Harris's  custom rpmmacro
#
#
#
# %_topdir defines the top directory to be used for RPM building purposes
# By defaultROOT of the buildsystem
%_topdir 		%(echo $HOME)/devel/rpmbuild

# de not automatically create the debuginfo package
%debug_package %{nil}


# %_sourcedir is where the source code tarballs, patches, etc. will be
# placed after you do an "rpm -ivh somepackage.1.0-1.src.rpm"
%_sourcedir     %{_topdir}/%{name}-%{version}

# %_specdir is where the specfile gets placed when installing a src.rpm. I
# prefer the specfile to be in the same directory as the source
tarballs, etc.
%_specdir       %{_sourcedir}


# %_tmppath is where temporary scripts are placed during the RPM build
# process as well as the %_buildroot where %install normally dumps files
# prior to packaging up the final binary RPM's.
%_tmppath	%{_topdir}/tmp

# %_builddir is where source code tarballs are decompressed, and
patches then
# applied when building an RPM package
%_builddir	%{_topdir}/BUILD

# %_buildroot is where files get placed during the %install section of
spec
# file processing prior to final packaging into rpms.  This is oddly named
# and probably should have been called "%_installroot" back when it was
# initially added to RPM.  Alas, it was not.  ;o)
%_buildroot	%{_tmppath}/%{name}-%{version}-root

# %_rpmdir is where binary RPM packages are put after being built.
%_rpmdir	%{_topdir}/RPMS

# %_srcrpmdir is where src.rpm packages are put after being built.
%_srcrpmdir	%{_topdir}/SRPMS

# %_rpmfilename defines the naming convention of the produced RPM
packages,
# and should not be modified.  It is listed here because I am overriding
# RPM's default behaviour of dropping binary RPM's each in their own
# separate subdirectories.  I hate that.  Grrr.
%_rpmfilename	%%{NAME}-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm

Hum, I'm not an rpmbuild guru, and I really can't see
why this should be a problem ... In the worse case I
could generate the .spec statically, but %version should
be available as part of the built src.rpm ... No I can't
make much sense of this.

Daniel

OK, so was nothing "wrong" with what is in the applet.spec file and
having the separate version file ... but why.  It is not to avoid
changing applet.spec since it is changed for the %changelog ... so why
the separate file?

Solution to the problem is to plug the information into the spec file
and get rid of the awk nonsense,  Sorry but this looks like doing
something tricky to avoid doing something simple.

rhn-applet was replaced by pirut and put (package pirut) as of FC5.  Only FC5
and FC6 are currently fully supported; FC3 and FC4 are supported for security
fixes only.  If this bug occurs in FC3 or FC4 and is a security bug, please
change the product to Fedora Extras and the version to match.  If you can verify
that the bug exists in RHEL as well, please change the product and version
appropriately.

The codebase for pirut and pup is quite different, but if a similar bug exists
in pirut and pup in FC5 or FC6, please change the product to pirut and the
version appropriately and update the bug report.

We apologize that the bug was not fixed before now.  The status will be changed
to NEEDINFO, and if the bug is not updated with evidence that it is a security
bug or a bug that affects RHEL, it will be closed.

Note that rhn-applet may still be present on upgraded systems, and in general
will not function correctly on such systems.  That is not a bug; anaconda does
not generally erase removed packages upon upgrades.

Closing per previous comment.