Re: Wheezy update of ruby-eventmachine?
- To: Balint Reczey <balint@balintreczey.hu>
- Cc: Debian LTS <debian-lts@lists.debian.org>, debian-ruby <debian-ruby@lists.debian.org>
- Subject: Re: Wheezy update of ruby-eventmachine?
- From: Christian Hofstaedtler <zeha@debian.org>
- Date: Fri, 1 Jul 2016 10:03:20 +0200
- Message-id: <[🔎] 20160701080319.GA9812@sx>
- In-reply-to: <b1286d49-c23a-6c7d-23a0-9568afb5951a@balintreczey.hu>
- References: <CAK0OdpxhSS0JVv-Q1SaMRXKkgC=XORBAWu2MqrGMH01Qak5tRQ@mail.gmail.com> <20160628052734.GA91898@tn> <CAK0OdpxNKC-6_+L82h11EmH3hqFPTyxm=HOuUfq=g_1d_WK1wg@mail.gmail.com> <b1286d49-c23a-6c7d-23a0-9568afb5951a@balintreczey.hu>
* Balint Reczey <balint@balintreczey.hu> [160630 00:20]:
[..]
> >>> I plan updating Jessie's version through jessie-proposed-updates, since
> >>> the issue is marked as no-DSA.
> >>
> >> This can probably still go through debian-security?
> >
> > I'll ask them, showing the proposed diff.
>
> I asked, but here is no clear new decision regarding handling the issue
> in Jessie.
Jessie has the exact same issue, right?
> While reading all the bug reports related to the crash I noticed that
> the fix introduced a memory leak which is fixed in successive commits.
Right, I knew about that but already had forgotten again.
> I have added them to the update growing it significantly, but at least
> we don't introduce a regression with the fix.
> Please see the diff attached and also in the git repository as separate
> commits.
Wow that's a ton of patches on top. Look at least logically
consistent to me.
--
,''`. Christian Hofstaedtler <zeha@debian.org>
: :' : Debian Developer
`. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03
`-
Reply to: