On 2016-09-05 14:58, Rob Browning wrote:
> Aurelien Jarno writes:
>
> > Yes, the 0020-Always-define-gmalloc-etc.-in-src-gmalloc.c.patch actually
> > comes from upstream commit 4b1436b702d56eedd27a0777fc7232cdfb7ac4f6.
>
> Ahh, yes, quite close, so I think this may be sufficient:
>
> Author: W
Aurelien Jarno writes:
> Yes, the 0020-Always-define-gmalloc-etc.-in-src-gmalloc.c.patch actually
> comes from upstream commit 4b1436b702d56eedd27a0777fc7232cdfb7ac4f6.
Ahh, yes, quite close, so I think this may be sufficient:
Author: Wolfgang Jenkner
Date: Sat Dec 26 12:12:02 2015 -0800
On 2016-09-05 12:31, Rob Browning wrote:
> Aurelien Jarno writes:
>
> > The patch i have attached is actually a backport of the above patch. It
> > was present in various branches, so I might have backported one with a
> > different commit number, but in practice it's the same.
>
> Assuming you
Aurelien Jarno writes:
> The patch i have attached is actually a backport of the above patch. It
> was present in various branches, so I might have backported one with a
> different commit number, but in practice it's the same.
Assuming you mean the gmalloc patch, do you know if there's a very
s
Aurelien Jarno writes:
> On 2016-09-04 19:09, Rob Browning wrote:
> The patch i have attached is actually a backport of the above patch. It
> was present in various branches, so I might have backported one with a
> different commit number, but in practice it's the same.
>
> The other patch I att
Hi,
On 2016-09-04 19:09, Rob Browning wrote:
> Aurelien Jarno writes:
>
> > Ok, great if you are working on a release. I am not on a hurry
> > personally, the package in the archive still works perfectly, the
> > problem is just when trying to rebuild it. Given I am the "one" who
> > broke that,
Aurelien Jarno writes:
> Ok, great if you are working on a release. I am not on a hurry
> personally, the package in the archive still works perfectly, the
> problem is just when trying to rebuild it. Given I am the "one" who
> broke that, I felt that I have to offer help.
I've started looking a
On 2016-09-03 11:07, Rob Browning wrote:
> Aurelien Jarno writes:
>
> > glibc 2.24 is now in unstable, so I am upgrading the severity of this
> > bug to serious. If you don't have time to fix this bug, I can do a
> > non-maintainer upload with the patch which is in the bug log.
>
> I've been wor
Aurelien Jarno writes:
> glibc 2.24 is now in unstable, so I am upgrading the severity of this
> bug to serious. If you don't have time to fix this bug, I can do a
> non-maintainer upload with the patch which is in the bug log.
I've been working on a release, and I think I should have time to fi
control: severity -1 serious
On 2016-08-08 11:45, Aurelien Jarno wrote:
> Package: emacs24
> Version: 24.5+1-6+b2
> Severity: important
> Tags: patch upstream
>
> Dear Maintainer,
>
> glibc 2.24 has removed the possibility to add malloc hooks, as they have
> been deprecated for more that 5 years
Package: emacs24
Version: 24.5+1-6+b2
Severity: important
Tags: patch upstream
Dear Maintainer,
glibc 2.24 has removed the possibility to add malloc hooks, as they have
been deprecated for more that 5 years. When emacs is built against this
glibc will switch to its internal malloc implementation.
11 matches
Mail list logo