That should have been fixed, but you can move CHANGES to doc directory
as a work around.
On 03/21/2016 11:57 AM, Bill Durant wrote:
Hello Martin:
I am unable to build the rpm from source for Monit 5.17.1:
$ rpmbuild -tb monit-5.17.1.tar.gz
...
...
+ rm -rf
/home/admin/rpmbuild/BUILDROOT/monit-5.17.1-1.x86_64/usr/share/doc/monit-5.17.1
+ /bin/mkdir -p
/home/admin/rpmbuild/BUILDROOT/monit-5.17.1-1.x86_64/usr/share/doc/monit-5.17.1
+ cp -pr COPYING README doc/CHANGES
/home/admin/rpmbuild/BUILDROOT/monit-5.17.1-1.x86_64/usr/share/doc/monit-5.17.1
cp: cannot stat `doc/CHANGES': No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.C0Cd8h (%doc)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.C0Cd8h (%doc)
==============================================
It looks like the tar ball doesn't include doc/CHANGES:
$ tar htvf monit-5.17.1.tar.gz | grep doc/
drwxr-xr-x 1001/1001 0 2016-03-06 03:01 monit-5.17.1/doc/
-rw-r--r-- 1001/1001 117078 2016-03-06 03:00 monit-5.17.1/doc/monit.pod
The CHANGES file is actually under monit-5.17.1:
$ tar htvf monit-5.17.1.tar.gz | grep CHANGES
-rw-r--r-- 1001/1001 38 2016-03-06 03:00 monit-5.17.1/CHANGES
Is there a workaround besides manually reconstructing the tar ball and
copying the CHANGES file to doc/CHANGES?
Thanks,
Bill
On 01/26/2016 11:55 AM, Martin Pala wrote:
Hi,
you can build rpm from the source code release directly:
rpmbuild -tb monit-5.15.tar.gz
Regards,
Martin
On 26 Jan 2016, at 20:48, Bill Durant <[email protected]> wrote:
Greetings:
Is there a Redhat RPM available for the latest version of Monit (5.15)?
Thanks,
Bill
--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general
--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general
--
Alex Litvak
System Architect
XCast Labs Inc.
(847) 716-5102 Phone
(847) 716-5112 Fax
(800) 254-3109 Customer Support
191 Waukegan Rd * Suite 310 * Northfield, IL 60093
[email protected]
--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general
