Hi all,
some weeks ago I took the quassel package to fix security issues. This worked fine for Fedora and EPEL 7, but for EPEL 6 I'm unable to apply security fixes as one of them (the most important one...) requires C++11 features not available in gcc 4.4 :( What is the best strategy for such a package?
Greetings, Christian
On 23 February 2016 at 14:10, Christian Dersch lupinix@mailbox.org wrote:
Hi all,
some weeks ago I took the quassel package to fix security issues. This worked fine for Fedora and EPEL 7, but for EPEL 6 I'm unable to apply security fixes as one of them (the most important one...) requires C++11 features not available in gcc 4.4 :( What is the best strategy for such a package?
Ouch. If the patches can't be applied cleanly and it seems that the current version won't compile with the older compiler.. I would look at removing the package from EPEL-6. Now how to do that cleanly is a bit up to the maintainer. The one time I believe I have done it, I added a "README-END-OF-LIFE" file explaining why it was being removed and also made a change to the RPM info. I pushed that and then went through the process of removing the package from EPEL. That way if people updated to that version they got a reason of why it was not going to show up anymore.
Greetings, Christian _______________________________________________ epel-devel mailing list epel-devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.or...
"CD" == Christian Dersch lupinix@mailbox.org writes:
CD> [...] for EPEL 6 I'm CD> unable to apply security fixes as one of them (the most important CD> one...) requires C++11 features not available in gcc 4.4 :( What is CD> the best strategy for such a package?
Maybe ask someone who is really familiar with C++ to see if the change can be done in a way that's compatible with the older compiler?
It should be quite possible to have a newer compiler in EPEL6 that's parallel-installable, but someone would have to actually do the work to make that happen. At least I don't think that violates any EPEL rules.
- J<
On 24/02/16 10:40, Jason L Tibbitts III wrote:
It should be quite possible to have a newer compiler in EPEL6 that's parallel-installable, but someone would have to actually do the work to make that happen. At least I don't think that violates any EPEL rules.
Devtoolset 3 has gcc 4.9.2, not sure what the policy is on using devtoolset for building packages that require it in epel. It is parrallel installable, though, and I'm sure can be rebuilt for epel if need be.
Perhaps the usage of devtoolset for building epel packages should be visited (if it hasn't been already). Normally these are only required for the build phase and not needed as a binary dependency.
Peter
On 02/23/2016 04:10 PM, Christian Dersch wrote:
Hi all,
some weeks ago I took the quassel package to fix security issues. This worked fine for Fedora and EPEL 7, but for EPEL 6 I'm unable to apply security fixes as one of them (the most important one...) requires C++11 features not available in gcc 4.4 :( What is the best strategy for such a package?
The man page says -std=c++0x the (old, now deprecated) option for enabling 2011 ISO C++. (Also -std=gnu++0x).
On my RHEL6 box with gcc-4.4.7 I can run `g++ -std=c++0x foo.cxx`, although I couldn't tell you if that actually is useful for the sources/patches you need to compile.
--
Kaleb
On 02/23/2016 11:00 PM, Kaleb KEITHLEY wrote:
The man page says -std=c++0x the (old, now deprecated) option for enabling 2011 ISO C++. (Also -std=gnu++0x).
On my RHEL6 box with gcc-4.4.7 I can run `g++ -std=c++0x foo.cxx`, although I couldn't tell you if that actually is useful for the sources/patches you need to compile.
I already tried that without success, when I apply http://pkgs.fedoraproject.org/cgit/rpms/quassel.git/plain/quassel-0.11.0-CTC... to el6, build fails (patch works fine on el7). Quassel developers wrote a comment in cmake configuration, that gcc 4.7 is the minimum gcc version.
On 23 February 2016 at 15:06, Christian Dersch lupinix@mailbox.org wrote:
On 02/23/2016 11:00 PM, Kaleb KEITHLEY wrote:
The man page says -std=c++0x the (old, now deprecated) option for enabling 2011 ISO C++. (Also -std=gnu++0x).
On my RHEL6 box with gcc-4.4.7 I can run `g++ -std=c++0x foo.cxx`, although I couldn't tell you if that actually is useful for the sources/patches you need to compile.
I already tried that without success, when I apply http://pkgs.fedoraproject.org/cgit/rpms/quassel.git/plain/quassel-0.11.0-CTC... to el6, build fails (patch works fine on el7). Quassel developers wrote a comment in cmake configuration, that gcc 4.7 is the minimum gcc version.
In that case, I would start the "EOL" process.
epel-devel mailing list epel-devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.or...
epel-devel@lists.fedoraproject.org
-
Christian Dersch -
Jason L Tibbitts III -
Kaleb S. KEITHLEY -
Peter -
Stephen John Smoogen