From: Mike Frysinger <vapier@gentoo.org>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8296] nodejs 0.12.7 - npm crashes (seg core dump)
Date: Wed, 2 Dec 2015 16:50:50 -0500 [thread overview]
Message-ID: <20151202215050.GF23754@vapier.lan> (raw)
In-Reply-To: <CAFGQKxdWRz-KepYPOEamNSKfV50X5iDN8jCcVgBzQZZeE47UyQ@mail.gmail.com>
On 01 Dec 2015 23:02, Martin Bark wrote:
> https://bugs.busybox.net just died :( I was in the middle of posting
> a back trace form the core dump and bugzilla stopped working. It
> gives a perl error about DateTime.pm missing.
it's fine now. i was in the middle of updating a lot of software and
forgot about the immediate impact on bugzilla.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20151202/ec4e0e6e/attachment.asc>
next prev parent reply other threads:[~2015-12-02 21:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 17:13 [Buildroot] [Bug 8296] New: nodejs 0.12.7 - npm crashes (seg core dump) bugzilla at busybox.net
2015-12-01 21:41 ` [Buildroot] [Bug 8296] " bugzilla at busybox.net
2015-12-01 21:42 ` bugzilla at busybox.net
2015-12-01 21:49 ` bugzilla at busybox.net
2015-12-01 22:04 ` bugzilla at busybox.net
2015-12-01 23:02 ` Martin Bark
2015-12-02 8:12 ` Thomas Petazzoni
2015-12-02 21:50 ` Mike Frysinger [this message]
2015-12-02 20:00 ` bugzilla at busybox.net
2015-12-02 20:58 ` bugzilla at busybox.net
2015-12-02 21:51 ` bugzilla at busybox.net
2015-12-02 22:01 ` bugzilla at busybox.net
2015-12-14 15:40 ` bugzilla at busybox.net
2015-12-23 17:48 ` bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151202215050.GF23754@vapier.lan \
--to=vapier@gentoo.org \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.