Bug 759021

Summary: perl-EV-4.03-6 does not build because libev-source changed version
Product: [Fedora] Fedora Reporter: Petr Pisar <ppisar>
Component: perl-EVAssignee: Petr Pisar <ppisar>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: bochecha, perl-devel
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: perl-EV-4.03-7.fc17 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-17 07:33:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Proposed fix none

Description Petr Pisar 2011-12-01 09:22:14 UTC
perl-EV build-requires exact version of libev-sources. However spot has rebased libev in F16--17:

* Tue Aug 09 2011 Tom Callaway <spot>
- 4.04-1 - move man page
- cleanup spec
- update to 4.04

thus versions do not match anymore.

The problem is perl-EV upstream has not yet released 4.04 version. Fortunately, the libev-4.04 seems compatible with libev-4.03 (all tests pass), thus I propose to weak build-time dependency in perl-EV as following:

-BuildRequires:  libev-source == %{version}
+BuildRequires:  libev-source >= %{version}

Other option is to add Provide: libev-source = 4.03 into libev-source.

This issue must be fixed in F17--16.

Comment 1 Petr Pisar 2011-12-01 09:28:28 UTC
Created attachment 539036 [details]
Proposed fix

Comment 2 Mathieu Bridon 2011-12-01 10:09:50 UTC
I had thought about that when I made the package, but I was a bit worried about potential incompatible changes in libev.

But I guess if that happened then the package would not build anymore, which is what happens with the strict versioned BR anyway, so the strict "==" doesn't seem to bring any value over a ">="

Thanks for the patch, I'll try to apply/push/build/update tomorrow or next week (bit swamped), but feel free to use your provenpackager super powers and beat me to it. :)

Comment 3 Petr Pisar 2011-12-01 14:55:06 UTC
Thank you for acknowledge. I will push it into F17--16.

Comment 4 Fedora Update System 2011-12-01 15:15:47 UTC
perl-EV-4.03-7.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/perl-EV-4.03-7.fc16

Comment 5 Fedora Update System 2011-12-04 02:30:18 UTC
Package perl-EV-4.03-7.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing perl-EV-4.03-7.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2011-16691/perl-EV-4.03-7.fc16
then log in and leave karma (feedback).

Comment 6 Fedora End Of Life 2013-01-17 02:13:26 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Mathieu Bridon 2013-01-17 07:33:03 UTC
The update has been pushed to the stable repo more than a year ago, not sure why Bodhi never closed this bug report...