Bug 162077 – Makefile.cvs should run before in some KDE spec files

Bug 162077 - Makefile.cvs should run before in some KDE spec files

Summary:	Makefile.cvs should run before in some KDE spec files

Status:	CLOSED RAWHIDE

Aliases:	None

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

Priority	medium Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Ngo Than
QA Contact:	Ben Levenson
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2005-06-29 14:35 EDT by Sammy
Modified:	2007-11-30 17:11 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-06-30 06:26:16 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 Sammy 2005-06-29 14:35:04 EDT

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.4; Linux; X11; en_US) KHTML/3.4.1 (like Gecko)

Description of problem:
This is true for a number of spec files, including kdeartwork and kdenetwork. 
These packages contain patches that apply to files created by running the 
cvs makefile (if one is really building from SVN), so the running of the makefile 
needs to be relocated before these patches. 
 
PS: I guess the cvs should be renamed to svn! 

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

How reproducible:
Always

Steps to Reproduce:
1. try to rebuild kdeartwork by pulling the source from SVN 3.4 branch 
2. watch the output 
3. 
   

Additional info:

Comment 1 Ngo Than 2005-06-30 06:26:16 EDT

oh yes, it's effected in the kdeartwork-3.3.2-xscreensaver.patch
It's now fixed in kdeartwork-3.4.1-2. Thanks for your report.

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