Re: Proposed F19 Feature: GLIBC 2.17

2013-02-13 Thread Orion Poplawski
On 01/28/2013 03:02 AM, Florian Weimer wrote: GLIBC 2.17 was released at the end of 2012; we have been closely tracking the GLIBC 2.17 development code in Fedora Rawhide and addressing any issues as they arise. The __secure_getenv to secure_getenv renaming need to be reflected in a few packages

Re: Proposed F19 Feature: GLIBC 2.17

2013-01-29 Thread Tomas Mraz
On Mon, 2013-01-28 at 11:02 +0100, Florian Weimer wrote: > > GLIBC 2.17 was released at the end of 2012; we have been closely tracking > > the > > GLIBC 2.17 development code in Fedora Rawhide and addressing any issues as > > they arise. > > The __secure_getenv to secure_getenv renaming need to

Re: Proposed F19 Feature: GLIBC 2.17

2013-01-29 Thread Jakub Jelinek
On Tue, Jan 29, 2013 at 12:09:51PM +0100, Florian Weimer wrote: > nss_hesiod needs secure_getenv, so a non-private symbol is needed. > In any case, I can link against __libc_secure_getenv in Fedora > rawhide: > > [root@oldenburg tmp]# rpm -q glibc > glibc-2.17-1.fc19.x86_64 > [root@oldenburg tmp]#

Re: Proposed F19 Feature: GLIBC 2.17

2013-01-29 Thread Florian Weimer
On 01/29/2013 10:47 AM, Jakub Jelinek wrote: Precisely because it's in the private namespace, glibc could just have documented the existing __secure_getenv symbol. It's not that there aren't any public functions starting with __. But this was rejected by upstream, and now we have the __secure_

Re: Proposed F19 Feature: GLIBC 2.17

2013-01-29 Thread Jakub Jelinek
On Tue, Jan 29, 2013 at 10:39:21AM +0100, Florian Weimer wrote: > On 01/28/2013 06:31 PM, Bill Nottingham wrote: > >Florian Weimer (fwei...@redhat.com) said: > >>See > >>for code snippets to implement in the change in a > >>backwards-

Re: Proposed F19 Feature: GLIBC 2.17

2013-01-29 Thread Florian Weimer
On 01/28/2013 06:31 PM, Bill Nottingham wrote: Florian Weimer (fwei...@redhat.com) said: See for code snippets to implement in the change in a backwards-compatible fashion. Unfortunately, glibc upstream insistent on renaming befor

Re: Proposed F19 Feature: GLIBC 2.17

2013-01-28 Thread Bill Nottingham
Florian Weimer (fwei...@redhat.com) said: > See > for code snippets to implement in the change in a > backwards-compatible fashion. Unfortunately, glibc upstream > insistent on renaming before making the symbol official. I'm a litt

Re: Proposed F19 Feature: GLIBC 2.17

2013-01-28 Thread Kevin Fenzi
On Mon, 28 Jan 2013 11:02:31 +0100 Florian Weimer wrote: > > GLIBC 2.17 was released at the end of 2012; we have been closely > > tracking the GLIBC 2.17 development code in Fedora Rawhide and > > addressing any issues as they arise. > > The __secure_getenv to secure_getenv renaming need to be r

Re: Proposed F19 Feature: GLIBC 2.17

2013-01-28 Thread Florian Weimer
GLIBC 2.17 was released at the end of 2012; we have been closely tracking the GLIBC 2.17 development code in Fedora Rawhide and addressing any issues as they arise. The __secure_getenv to secure_getenv renaming need to be reflected in a few packages (as of Fedora 18): sourc

Proposed F19 Feature: GLIBC 2.17

2013-01-27 Thread Jaroslav Reznik
= Features/GLIBC217 = https://fedoraproject.org/wiki/Features/GLIBC217 Feature owner(s): Jeff Law Switch GLIBC in Fedora 19 to GLIBC version 2.17. == Detailed description == GLIBC 2.17 was released at the end of 2012; we have been closely tracking the GLIBC 2.17 development code in Fedora R

Proposed F19 Feature: GLIBC 2.17

2013-01-24 Thread Jaroslav Reznik
= Features/GLIBC217 = https://fedoraproject.org/wiki/Features/GLIBC217 Feature owner(s): Jeff Law Switch GLIBC in Fedora 19 to GLIBC version 2.17. == Detailed description == GLIBC 2.17 was released at the end of 2012; we have been closely tracking the GLIBC 2.17 development code in Fedora Ra