Bug 176720 - perl-HTML-Tagset: update request to 3.10
Summary: perl-HTML-Tagset: update request to 3.10
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-HTML-Tagset
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jason Vas Dias
QA Contact:
URL: http://search.cpan.org/dist/HTML-Tagset/
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-12-30 19:52 UTC by Jose Pedro Oliveira
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-01-18 16:15:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Specfile patch (1.42 KB, patch)
2006-01-10 20:32 UTC, Jose Pedro Oliveira
no flags Details | Diff

Description Jose Pedro Oliveira 2005-12-30 19:52:00 UTC
Description of problem:
New version in CPAN;

WARNING 
WARNING New module maintainer -> the source URL must be changed
WARNING 

Version-Release number of selected component (if applicable):
rawhide: perl-HTML-Tagset-3.04-2.1.src.rpm

Expected results:
Version 3.10 in rawhide.

Additional info:
Diff from HTML-Tagset-3.04 to HTML-Tagset-3.10
http://search.cpan.org/diff?from=HTML-Tagset-3.04&to=HTML-Tagset-3.10

Comment 1 Jason Vas Dias 2006-01-10 17:08:02 UTC
Thanks - perl-HTML-Tagset-3.10 now in rawhide-2006-01-10 (FC5t3) .


Comment 2 Jose Pedro Oliveira 2006-01-10 20:32:01 UTC
Created attachment 123009 [details]
Specfile patch

The current RPM may create an unowned directory.

This patch corrects this problem and a couple of other minor ones:
* package now owns the directory %{perl_vendorlib}/HTML/
* removed the ending dot from the summary (rpmlint warning)
* moved the test suite execution into the %check section
* dropped the RPM_OPT_FLAGS in the %build section (not need for noarch
packages)
* dropped the "find ... '*.bs' ..." command (also not need for noarch packages)

Comment 3 Jason Vas Dias 2006-01-17 22:29:29 UTC
OK - fixed with perl-HTML-Tagset-3.10-2 


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