Github messages for voidlinux
 help / color / mirror / Atom feed
From: the-maldridge <the-maldridge@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: grafana: update to 7.3.8 & fix baked-in version.
Date: Tue, 11 Jan 2022 08:20:13 +0100	[thread overview]
Message-ID: <20220111072013.pc5Fln_S-5RNyVt2LYqYSxoPmCWetqa60gI8I5eidEU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34705@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 386 bytes --]

New comment by the-maldridge on void-packages repository

https://github.com/void-linux/void-packages/pull/34705#issuecomment-1009662717

Comment:
I saw this and was quite surprised to see that the node version requirements had changed.  Originally this package was built to rebuild the JS locally, but the grafana project also provided precompiled versions.  Is that still the case?


  parent reply	other threads:[~2022-01-11  7:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-26 14:10 [PR PATCH] " lotheac
2022-01-11  7:18 ` lotheac
2022-01-11  7:20 ` the-maldridge [this message]
2022-01-11  7:22 ` lotheac
2022-01-11  7:24 ` the-maldridge
2022-01-11  7:40 ` lotheac
2022-01-11  7:41 ` the-maldridge
2022-01-11  9:35 ` [PR PATCH] [Updated] " lotheac
2022-01-11  9:37 ` grafana: update to 8.3.3 lotheac
2022-01-11 10:00 ` lotheac
2022-01-11 16:00 ` [PR PATCH] [Updated] " lotheac
2022-01-11 16:02 ` lotheac
2022-01-11 16:16 ` the-maldridge
2022-01-11 16:58 ` [PR PATCH] [Updated] " lotheac
2022-01-11 17:00 ` lotheac
2022-01-11 17:04 ` lotheac
2022-01-11 17:24 ` [PR PATCH] [Updated] " lotheac
2022-01-11 17:25 ` lotheac
2022-01-12  2:06 ` the-maldridge
2022-01-12  6:01 ` [PR PATCH] [Updated] " lotheac
2022-01-12  6:02 ` lotheac
2022-01-13  5:09 ` [PR PATCH] [Closed]: " the-maldridge

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=20220111072013.pc5Fln_S-5RNyVt2LYqYSxoPmCWetqa60gI8I5eidEU@z \
    --to=the-maldridge@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).