Bug 1021851 - Upgrade to version 2.9.1
Upgrade to version 2.9.1
Status: NEW
Product: Fedora EPEL
Classification: Fedora
Component: nsca (Show other bugs)
Unspecified Linux
unspecified Severity low
: ---
: ---
Assigned To: Xavier Bachelot
Fedora Extras Quality Assurance
: 1090523 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2013-10-22 04:26 EDT by Remi Ferrand
Modified: 2014-11-04 00:34 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Remi Ferrand 2013-10-22 04:26:03 EDT
Description of problem:
Epel 6 only has version nsca version 2.7.2.
A quick Google with the maintainer name (X. Bachelot)  and nsca version 2.9.1 shows me that he already did the work to package version 2.9.1 but it was (if i understood well) released as a "test release" one year ago.

What about releasing it as production / stable version in EPEL 6 :-) ?

Comment 1 Xavier Bachelot 2013-11-15 04:30:34 EST
nsca 2.9.1 is in epel testing repo for quite a while so it's available if you want to use it but I'm not sure I'll push it to stable as there are behaviour changes between 2.7.2 and 2.9.1 and upstream doesn't seem to care much...
Comment 2 Remi Ferrand 2014-04-23 10:29:27 EDT
*** Bug 1090523 has been marked as a duplicate of this bug. ***
Comment 3 Remi Ferrand 2014-04-23 10:34:28 EDT
Hi Xavier,

I'm coming back with my request has importing and merging packages from epel-testing is quite complicated for us to maintain.

Do you think that moving 2.9.1 from testing to stable could break some things ?
As far as I known, if client and server are both in 2.9, everything works fine.
Comment 4 Xavier Bachelot 2014-04-26 12:42:31 EDT
Hi Remi,

I'd rather not push nsca 2.9.1 to EL5 and EL6 until the following bug is fixed :


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