Bug 160630 – Missing BuildReq in cvs

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 160630 - Missing BuildReq in cvs

Summary:	Missing BuildReq in cvs

Status:	CLOSED NEXTRELEASE

Aliases:	None

Product:	Red Hat Enterprise Linux 4
Classification:	Red Hat
Component:	cvs (Show other bugs)
Sub Component:
Version:	4.0
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Martin Stransky
QA Contact:	Ben Levenson
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2005-06-16 04:07 EDT by Andreas Thienemann
Modified:	2007-11-30 17:07 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2005-07-21 07:06:52 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Andreas Thienemann 2005-06-16 04:07:05 EDT

During a testbuild of cvs-1.11.17-5 in mock, the following problem in the
buildprocess manifests itself:

checking for vim... no
checking for vi... no
checking for emacs... no
checking for nano... no
checking for pico... no
checking for edit... no
configure: error:
    Failed to find a text file editor.  CVS cannot be compiled
    without a default log message editor.  Searched for
    `vim vi emacs nano pico edit'.  Try `configure --with-editor'.
error: Bad exit status from /var/tmp/rpm-tmp.148 (%build)

It seems cvs won't build without an installed editor.
Thus it would be good if the specfile either contains a BuildRequire for an
editor or the --with-editor command is used during the %configure phase.
As the current cvs builds from redhat use vim as the standard editor, the latter
option would probably be the easiest choice.

Note You need to log in before you can comment on or make changes to this bug.