Bug 425827 - perl-libwhisker2: broken deps
Summary: perl-libwhisker2: broken deps
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: perl-libwhisker2
Version: el5
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Sindre Pedersen Bjørdal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
: 429478 (view as bug list)
Depends On: 481457
Blocks: EPEL5-BrokenDeps
TreeView+ depends on / blocked
 
Reported: 2007-12-16 10:32 UTC by Thorsten Leemhuis
Modified: 2009-03-28 19:15 UTC (History)
3 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2009-03-28 19:15:02 UTC


Attachments (Terms of Use)

Description Thorsten Leemhuis 2007-12-16 10:32:15 UTC
Description of problem:
package: perl-libwhisker2 - 2.4-3.el5.noarch from epel5-testing
  unresolved deps: 
     perl(MD5)

Additional info:
I'd like to see the above problems solved.

ixs, would you be willing to take care of perl(Text::Aspell) in EPEL5?

Comment 1 Thorsten Leemhuis 2007-12-16 10:35:21 UTC
s/perl(Text::Aspell)/perl(MD5)/ of course ;)

Comment 2 Thorsten Leemhuis 2008-01-14 15:57:15 UTC
ping ixs

Comment 3 Kevin Fenzi 2008-01-20 21:50:21 UTC
*** Bug 429478 has been marked as a duplicate of this bug. ***

Comment 4 Kevin Fenzi 2008-09-20 22:17:48 UTC
This has been broken a long long time. 

If it's not fixed soon, these package(s) may be removed.

Comment 5 Kevin Fenzi 2009-01-25 04:10:13 UTC
This is a pretty ancient bug now. ;( 

ixs: Shall we just remove this package or can you branch/maintain perl-MD5 in EPEL?

Comment 6 Andreas Thienemann 2009-01-25 04:23:23 UTC
Uhrg. I must have completely missed this bug.
Yeah, certainly I can maintain perl-MD5 for EPEL.

Setting the branching request now.

Comment 7 Andreas Thienemann 2009-01-26 22:23:06 UTC
Okay, perl-MD5 has been branched, tagged and built.

Enjoy.

Comment 8 Michael Stahnke 2009-03-28 17:40:07 UTC
It appears this is no longer an issue.  Can this be closed?

Comment 9 Thorsten Leemhuis 2009-03-28 19:04:36 UTC
(In reply to comment #8)
> It appears this is no longer an issue.  Can this be closed?  

Then why did you close as it seems you verified it ;-)


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