On 5/8/19 8:42 AM, mark wrote: > Hi, Johnny, > > Johnny Hughes wrote: >> On 5/2/19 9:15 AM, mark wrote: >>> >>> Especially Johnny - could you possibly push this fix through as soon as >>> upstream puts it out? It's a real issue for us - we've had a number of >>> servers whether gssproxy keeps SEGVing, which hits NFS and samba. >> >> See if this fixes your issues .. if do, let me know and we can get it >> released into the fasttrack repo: >> >> https://buildlogs.centos.org/c7-fasttrack.x86_64/gssproxy/ >> >> >> Note: This packages are unsigned and if it fixes your issue, I'll sign >> and release them into fasttrack repo >> >> Note2: Here is some info on our new fasttrack repo: >> >> >> https://wiki.centos.org/AdditionalResources/Repositories >> (see CentOS-Fasttrack) >> > Thank you very much. I've d/l the x86_64 rpm, and yum upgraded to it on > one server, so it's soaking now, and we'll see what happens. > > One question: the email I got from RH bugzilla referred to the package as > gssproxy-0.7.0-25, not 21, while I see you've got it as 21.el7.0.1. Will > there be a name change, or will it be 21.whatever? Yes .. when we patch in our fasttrack repo ... we take the current release we are patching (the current version) and name it in a way where no matter the NEXT upstream release, when done .. it will replace the one we put in the fasttrack repo. Fasttrack is us (centos qa team) fixing things temporarily while waiting for them to be fixed officially and are different than base RHEL updates .. that is why it is a separate and optional repo.
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx https://lists.centos.org/mailman/listinfo/centos
