Your message dated Fri, 5 Jun 2020 09:46:18 +0200
with message-id
<cakjshr26f5u9tcuvmgvsft_3-xs6quxtxnxvf0uiywr7szq...@mail.gmail.com>
and subject line Re: Bug#956402: plans for uploading a newer icu to unstable
has caused the Debian Bug report #956402,
regarding plans for uploading a newer icu to unstable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
956402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956402
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libicu-dev
Version: 63.2-3
Severity: important
Control: block 956211 by -1
nodejs 12 transition is blocked by libicu-dev >= 64.0~ and gitlab no
longer works with nodejs 10 (when memory usage in webpack goes above
2GB it crashes, see #956211).
It'd be really helpful if you can upload a newer version to unstable to
allow nodejs 12 in unstable.
NB: gitlab is in experimental currently as it needs rails 6, but I hope
to be able to upload it to unstable when rails 6 transition starts
right after ruby 2.7 transition completes.
--- End Message ---
--- Begin Message ---
Version: 67.1-2
On Fri, Apr 10, 2020 at 10:07 PM Xavier <y...@debian.org> wrote:
> Le 10/04/2020 à 20:48, Pirate Praveen a écrit :
> > On Fri, Apr 10, 2020 at 8:38 pm, László Böszörményi (GCS)
> > <g...@debian.org> wrote:
> >> Is ICU update the last step to have NodeJS 12 in unstable?
> yes it seems to be the last step
It's in unstable for some days.
Cheers,
Laszlo/GCS
--- End Message ---
