Bug 506757 – Whitespace is required around '=' sign in Requires directives

Bug 506757 - Whitespace is required around '=' sign in Requires directives

Summary:	Whitespace is required around '=' sign in Requires directives

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	rpm (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Panu Matilainen
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2009-06-18 11:26 EDT by Peter Lemenkov
Modified:	2009-06-18 12:58 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2009-06-18 12:58:27 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 Peter Lemenkov 2009-06-18 11:26:24 EDT

These syntactically correct Requires directives producing missing dependencies (see subpackage demo):

http://cvs.fedoraproject.org/viewvc/rpms/openscada/devel/openscada.spec?revision=1.4&view=markup

Requires:%{name}-ARH-DBArch=%{version}-%{release}
Requires:%{name}-ARH-FSArch=%{version}-%{release}
Requires:%{name}-ARH-SQLite=%{version}-%{release}

After adding whitespace around '=' sign, the issue was gone. This should be either reported upstream and fixed, or described in docs. Unfortunately, I cannot find the description of this issue in docs.

Comment 1 Panu Matilainen 2009-06-18 12:58:27 EDT

See /usr/share/doc/rpm-*/dependencies, or in a bit nicer format: http://rpm.org/wiki/PackagerDocs/Dependencies: "Spaces are required around the numeric operator to separate the operator from the package name."

This has always been the case, and changing it would only introduce a spec-file incompatibility for something that makes the spec less readable.

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