Bug 428085 – broken spec

Bug 428085 - broken spec

Summary:	broken spec

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	perl-CGI-Session (Show other bugs)
Sub Component:
Version:	8
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Andreas Thienemann
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	419631
	Show dependency tree / graph

Reported:	2008-01-08 23:40 EST by Ralf Corsepius
Modified:	2008-02-02 03:59 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:	4.20-3.fc8
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-02-02 03:59:58 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
patch to fix this issue (2.69 KB, patch) 2008-01-08 23:40 EST, Ralf Corsepius	no flags	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Ralf Corsepius 2008-01-08 23:40:33 EST

Description of problem:
Package doesn't build on FC-8 and FC-9, because the perl-package split has not
been reflected to it.

Version-Release number of selected component (if applicable):
perl-CGI-Session-4.20-2%{?dist}

How to reproduce:
check out from CVS
make mockbuild

Additional info:
I would have fixed this bug in CVS, but you have restrictive ACLs 
set on this package, preventing me from helping you.

Comment 1 Ralf Corsepius 2008-01-08 23:40:33 EST

Created attachment 291112 [details]
patch to fix this issue

Comment 2 Fedora Update System 2008-01-27 17:01:48 EST

perl-CGI-Session-4.20-3.fc8 has been submitted as an update for Fedora 8

Comment 3 Fedora Update System 2008-02-02 03:59:56 EST

perl-CGI-Session-4.20-3.fc8 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.

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