On 2015-08-17 13:17, Carlos O'Donell wrote: > On Sat, Aug 15, 2015 at 4:31 AM, Aurelien Jarno <[email protected]> wrote: > > control: fixed -1 glibc/2.21-0experimental0 > > > > On 2015-08-14 18:28, Tulio Magno Quites Machado Filho wrote: > >> I believe Debian is missing the following patch for ppc64el: > >> https://sourceware.org/git/?p=glibc.git;a=commit;h=a53fbd8e6cd2f69bdfa3431d616a5f332aea6664 > > > > I have just committed a fix to our SVN in the stable branch. If accepted > > by the Debian stable release manager, we plan to have it in the next > > stable point release. > > > > Given this bug is fixed in the experimental branch, I am marking it as > > fixed for this version. > > So this is IMO, the wrong thing to do. You should push the patch into > upstream 2.19 stable and rebase instead of keeping the patch in debian > svn. Given the patch is already in upstream master it is OK to commit > to 2.19 stable, and post to libc-stable stating you checked in this > fix. That way debian gets broader testing of the patches we are using > instead of the narrower "just debian" users.
If it is fine to push this kind of patch in this branch, I would certainly do that. I also backported for debian patch b0a3c164. Would it be possible to also push it to the branch? Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B [email protected] http://www.aurel32.net
