Bug 165260 – signal.c is missing from 2.6.12-1.1398_FC4.src.rpm

Bug 165260 - signal.c is missing from 2.6.12-1.1398_FC4.src.rpm

Summary:	signal.c is missing from 2.6.12-1.1398_FC4.src.rpm

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	kernel (Show other bugs)
Sub Component:
Version:	4
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Kernel Maintainer List
QA Contact:	Brian Brock
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2005-08-05 19:15 EDT by Jasper O. Hartline
Modified:	2007-11-30 17:11 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2005-08-05 20:04:40 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 Jasper O. Hartline 2005-08-05 19:15:46 EDT

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.7.8-2

Description of problem:
signal.c is missing from 2.6.12-1.1398_FC4.src.rpm

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.updatedb
2.locate signal.c
3.no signal.c
  

Actual Results:  No kernel/signal.c file was found

Expected Results:  I thought signal.c was in kernel directory

Additional info:

Comment 1 Warren Togami 2005-08-05 20:04:40 EDT

Your understanding of source RPMS is incorrect, signal.c is contained in
archives of the .src.rpm.  They are expanded and patched during the RPM building
process.  Please ask for help on one of the mailing lists for fedoraforum.org if
you can't figure this out.  Bugzilla is not a support mechanism to teach you how
to properly use the software.

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