From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] prometheus: update to 2.38.0.
Date: Thu, 18 Aug 2022 23:49:05 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38767@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
There is a new pull request by paper42 against master on the void-packages repository
https://github.com/paper42/void-packages prometheus-2.38
https://github.com/void-linux/void-packages/pull/38767
prometheus: update to 2.38.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/38767.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-prometheus-2.38-38767.patch --]
[-- Type: text/x-diff, Size: 1272 bytes --]
From be8b61ef713c188e07ae30fb5a31272b6a1dd8c7 Mon Sep 17 00:00:00 2001
From: Michal Vasilek <michal@vasilek.cz>
Date: Thu, 18 Aug 2022 23:48:02 +0200
Subject: [PATCH] prometheus: update to 2.38.0.
---
srcpkgs/prometheus/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/prometheus/template b/srcpkgs/prometheus/template
index e56d5cd4e936..1574ea90d6ce 100644
--- a/srcpkgs/prometheus/template
+++ b/srcpkgs/prometheus/template
@@ -1,6 +1,6 @@
# Template file for 'prometheus'
pkgname=prometheus
-version=2.33.1
+version=2.38.0
revision=1
build_style=go
go_import_path="github.com/prometheus/prometheus"
@@ -18,14 +18,14 @@ license="Apache-2.0"
homepage="https://prometheus.io/"
changelog="https://raw.githubusercontent.com/prometheus/prometheus/master/CHANGELOG.md"
distfiles="https://github.com/prometheus/prometheus/archive/v${version}.tar.gz"
-checksum=a3ec7bde701b0663e706c718ea58722544c4a3bbb902d89cf64d3b7f34523ad5
+checksum=311f9f2f867ee0f2bef5c8227bbf672edf4037b6fd5e036c45ed7e947d61c375
system_accounts="_prometheus"
make_dirs="/var/lib/prometheus 700 _prometheus _prometheus"
pre_build() {
- CGO_ENABLED=0 GOARCH= make assets
+ CGO_ENABLED=0 GOARCH= make assets assets-compress
}
post_install() {
next reply other threads:[~2022-08-18 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 21:49 paper42 [this message]
2022-08-18 21:50 ` paper42
2022-08-19 19:15 ` [PR PATCH] [Merged]: " Vaelatern
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38767@inbox.vuxu.org \
--to=paper42@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).