Bug 77915 - NoSource tag doesn't accept more than one number
NoSource tag doesn't accept more than one number
Status: CLOSED UPSTREAM
Product: Red Hat Linux
Classification: Retired
Component: rpm-build (Show other bugs)
8.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-11-15 05:17 EST by Jos Vos
Modified: 2007-04-18 12:48 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-09-29 17:41:13 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)
Spec file reproducing the problem. (694 bytes, text/plain)
2002-11-15 05:18 EST, Jos Vos
no flags Details

  None (edit)
Description Jos Vos 2002-11-15 05:17:01 EST
Description of Problem:
The NoSource tag doesn't accept more than one number ("NoSource: 0,1" or
"NoSource: 0 1" both say "Bad number: 0, 1" resp. "Bad number: 0 1"). The
workaround is to use multiple NoSource tags, but in case you have 10 source
elements, this is a bit inconvenient...

Version-Release number of selected component (if applicable):
4.1-1.06 (problem also occurs in older versions, RH 7.2 and 7.3).

How Reproducible:
See the attached spec file.  Touch two files testing.txt and testing.init in the
SOURCES directory and use the spec file, then the problem occurs.
Comment 1 Jos Vos 2002-11-15 05:18:20 EST
Created attachment 85165 [details]
Spec file reproducing the problem.
Comment 2 Jos Vos 2002-11-15 05:27:56 EST
Oops, this spec file has two NoSource tags, change them to one line with
"NoSource: 0, 1" and the problem will occur.
Comment 3 Bill Nottingham 2005-09-29 17:41:13 EDT
Closing bugs on older, no longer supported, releases. Apologies for any lack of
response.

For RPM issues, please try a current release such as Fedora Core 4; if bugs
persist, please open a new issue.

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