search for: 93778a4eeb

Apologies if this email is a top post. I'm not sure how to reply to a thread if I'm not subscribed. We recently encountered the same issue that Evan reported on 6/4 and I can confirm that updated to 3.3.0-5 does address the build failure. Will 3.3.0-5 make it into EPEL? If so, do you have any idea when? The current package is breaking our build process and I'm wondering if it's

...hing would build. I was (am) getting the same build errors as another previously posted (https://stat.ethz.ch/pipermail/r-sig-fedora/2016-June/000452.html). I watched over the bodhi page for the issue and noticed 3.3.0-5 was pushed to stable (https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-93778a4eeb), so I updated this morning. Problem is, I'm still getting the exact same build errors I was the last couple of days. In fact, I can perfectly replicate the initial poster's issue: when I try to update nlme, I end up with the following: gcc: /builddir/build/BUILD/R-3.3.0/zlib-1.2.8/target...

...h the > > effort to implement a workaround or not. > > Yes, this package is going through the update process right now. You can > speed it along by logging into the Fedora Update system and giving > positive karma: > > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-93778a4eeb > > If the build gets +3 karma, it will go to stable immediately. > Otherwise, it takes two weeks to be pushed to stable according to EPEL > policies. > Thanks, Tom. I'll go try and help the karma process along. brian > > ~tom > > == > Red Hat > [[alternat...

...o implement a workaround or not. >> >> Yes, this package is going through the update process right now. You can >> speed it along by logging into the Fedora Update system and giving >> positive karma: >> >> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-93778a4eeb >> >> If the build gets +3 karma, it will go to stable immediately. >> Otherwise, it takes two weeks to be pushed to stable according to EPEL >> policies. >> > > Thanks, Tom. I'll go try and help the karma process along. > > brian > > >> &gt...