Re: glibc fix to allow instlangs to really work -- too late for f22?
On Wed, Mar 18, 2015 at 11:50 AM, Matthew Miller mat...@fedoraproject.org wrote: The glibc team has a fix for a longstanding issue, which is that instlangs hasn't worked in the installer. This means that in a minimal image of about 400MB, 100MB is translation information. (Of course we want Fedora to be international, but there are many cases like Docker containers where no human is really even looking inside, so it's just overhead.) In the cloud and docker images, we've been carrying horribly hacks (really, horrible) to strip this out ofter the fact. The new fix would let us get the same effect the right way. I'm told that this is a low-risk change and does not affect the rest of glibc. So, the question -- I guess mostly for FESCo, but in general -- is: should we get this in before the beta, or should it wait for F23? How long has it been in F-23? ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
glibc fix to allow instlangs to really work -- too late for f22?
The glibc team has a fix for a longstanding issue, which is that instlangs hasn't worked in the installer. This means that in a minimal image of about 400MB, 100MB is translation information. (Of course we want Fedora to be international, but there are many cases like Docker containers where no human is really even looking inside, so it's just overhead.) In the cloud and docker images, we've been carrying horribly hacks (really, horrible) to strip this out ofter the fact. The new fix would let us get the same effect the right way. I'm told that this is a low-risk change and does not affect the rest of glibc. So, the question -- I guess mostly for FESCo, but in general -- is: should we get this in before the beta, or should it wait for F23? -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: glibc fix to allow instlangs to really work -- too late for f22?
My 2cts as Cloud SIG member is that we shouldn't wait for F23 as long as it's ready for beta or even shortly before. This is not just an annoyance, this is an huge impediment toward successful cloud product. I kindly ask fesco to take this into consideration Regards, H. ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: glibc fix to allow instlangs to really work -- too late for f22?
On Wed, Mar 18, 2015 at 7:50 AM, Matthew Miller mat...@fedoraproject.org wrote: The glibc team has a fix for a longstanding issue, which is that instlangs hasn't worked in the installer. This means that in a minimal image of about 400MB, 100MB is translation information. (Of course we want Fedora to be international, but there are many cases like Docker containers where no human is really even looking inside, so it's just overhead.) In the cloud and docker images, we've been carrying horribly hacks (really, horrible) to strip this out ofter the fact. The new fix would let us get the same effect the right way. I'm told that this is a low-risk change and does not affect the rest of glibc. So, the question -- I guess mostly for FESCo, but in general -- is: should we get this in before the beta, or should it wait for F23? Isn't this causing RPM dependency issues when trying to create rawhide chroots on RHEL6 hosts via mock? I am fairly sure it's the reason COPR rawhide chroots are failing. If so, then I don't think we want it in f22 until that is fixed. josh ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
