Description of problem:
LLNL which is also the upstream requests that we rebase conman to 0.2.8 to pick up some performance improvements and fixes needed for their site.
Version-Release number of selected component (if applicable):
From: Chris Dunlap <cdunlap>
Subject: Re: [Bug 1022502] Spec file URLs should point to new home page
Date: March 24, 2017 at 5:36:11 PM PDT
To: Ben Woodard <woodard>
You should be able to drop all 4 patches from conman-0.2.7-15.
In fact, conman-0.2.7-hack-around-overflow-issue.patch is wrong and
should be dropped regardless. I noted that with the patch's author
last year but didn't realized he added it to Red Hat's rpm until now.
I was finally able to see the Coverity Scan results back in Nov when
I found out their scan results are free for open-source projects.
Is this really request for rebase of conman in RHEL 7? Is there some good reason behind it? Usually we don't rebase components in released major version of RHEL unless there is some good reason for it.
As for Fedora, I see Dan Horak already built 0.2.8 in Rawhide - https://koji.fedoraproject.org/koji/buildinfo?buildID=866738 , adding him to CC of this bugzilla. Dan, can you please make sure if Chris's comments are addressed by your rebase in Rawhide? Thanks!
My initial intention on the Fedora side was cleaning up the spec file (mainly for bug #1244218), but because there was a new release available with a number of fixes mentioned in conman's release notes I've rebased it as well. The Fedora version is now clean upstream version, so except some packaging differences it's what Ben/Chris ask for. Although freeipmi is still 1.5.4 in Fedora while 1.5.5 is available, it might be what Chris means in comment #2.
The reasons for the rebase are:
1) one of the patches currently being applied introduces a bug
2) the other patches are part of the the 0.2.8 release. LLNL which is upstream made sure that our fixes were incorporated -- except when they were wrong and introduced additional bugs.
3) There are other performance issues that have shown up in the 0.2.7 release which were addressed in the 0.2.8 release.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.