From: zimoun <zimon.toutoune@gmail.com>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: 34613@debbugs.gnu.org
Subject: [bug#34613] [PATCH] gnu: Add prometheus.
Date: Thu, 07 Apr 2022 14:29:56 +0200 [thread overview]
Message-ID: <86mtgx2i0r.fsf@gmail.com> (raw)
In-Reply-To: <20190222114537.1431-1-boskovits@gmail.com> ("Gábor Boskovits"'s message of "Fri, 22 Feb 2019 12:45:37 +0100")
Hi,
What is the status of this old patch#34613:
<http://issues.guix.gnu.org/issue/34613>
On Fri, 22 Feb 2019 at 12:45, Gábor Boskovits <boskovits@gmail.com> wrote:
> * gnu/packages/monitoring.scm
> (go-github-com-prometheus-prometheus-cmd-prometheus): New variable.
> ---
> gnu/packages/monitoring.scm | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/gnu/packages/monitoring.scm b/gnu/packages/monitoring.scm
> index 4384406227..0fd6b9e49b 100644
> --- a/gnu/packages/monitoring.scm
> +++ b/gnu/packages/monitoring.scm
> @@ -447,3 +447,27 @@ written in Go with pluggable metric collectors.")
> (description "This package provides a file system monitor.")
> (home-page "https://github.com/emcrisostomo/fswatch")
> (license license:gpl3+)))
> +
> +(define-public go-github-com-prometheus-prometheud-cmd-prometheus
> + (package
> + (name "go-github-com-prometheus-prometheus-cmd-prometheus")
> + (version "2.7.1")
> + (source (origin
> + (method git-fetch)
> + (uri (git-reference
> + (url "https://github.com/prometheus/prometheus.git")
> + (commit (string-append "v" version))))
> + (file-name (git-file-name name version))
> + (sha256
> + (base32
> + "08nd88m162bw5612cvw5fl028l2n9jy1v4w2a8cyd0dj4lxs5d98"))))
> + (build-system go-build-system)
> + (arguments
> + '(#:import-path "github.com/prometheus/prometheus/cmd/prometheus"
> + #:unpack-path "github.com/prometheus/prometheus"))
> + (synopsis "Monitoring system & time series database")
> + (description "Prometheus is an open-source monitoring system with a
> +dimensional data model, flexible query language, efficient time series database
> +and modern alerting approach.")
> + (home-page "https://github.com/prometheus/node_exporter")
> + (license license:asl2.0)))
Because the Go ecosystem changed a bit since the submission, do we merge
this patch? Especially in the light of:
There are some problems with it however:
The tarball has a vendor directory, containing sources of third party
go stuff. How do we deal with that?
(Should we package the stuff there, and link the sources into the tree?)
<https://issues.guix.gnu.org/issue/34613#1>
Well, I propose to drop this submission since the last interaction is
from 3 years, 2 weeks, 6 days ago and then start a fresh one. WDYT?
Cheers,
simon
next prev parent reply other threads:[~2022-04-07 12:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 11:45 [bug#34613] [PATCH] gnu: Add prometheus Gábor Boskovits
[not found] ` <handler.34613.B.155083599830524.ack@debbugs.gnu.org>
2019-02-22 12:21 ` [bug#34613] Acknowledgement ([PATCH] gnu: Add prometheus.) Gábor Boskovits
2019-03-11 22:19 ` Ludovic Courtès
2019-03-12 7:03 ` Pierre Neidhardt
2019-03-12 19:31 ` Leo Famulari
2019-03-12 21:24 ` Gábor Boskovits
2019-03-12 21:29 ` Gábor Boskovits
2019-03-13 10:06 ` Ludovic Courtès
2019-03-13 12:33 ` Gábor Boskovits
2019-03-18 8:31 ` Ludovic Courtès
2022-04-07 12:29 ` zimoun [this message]
2022-10-08 14:42 ` [bug#34613] [PATCH] gnu: Add prometheus zimoun
2022-10-18 16:18 ` bug#34613: " zimoun
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86mtgx2i0r.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=34613@debbugs.gnu.org \
--cc=boskovits@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).