From: TinfoilSubmarine <TinfoilSubmarine@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] prometheus: update to 2.43.0.
Date: Tue, 28 Mar 2023 18:22:10 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43071@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
There is a new pull request by TinfoilSubmarine against master on the void-packages repository
https://github.com/TinfoilSubmarine/void-packages update/prometheus
https://github.com/void-linux/void-packages/pull/43071
prometheus: update to 2.43.0.
update run script to properly increase max open files limit
<!-- 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/43071.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update/prometheus-43071.patch --]
[-- Type: text/x-diff, Size: 1779 bytes --]
From a7d09954b8175e27ae457b9e305e299bb80280f4 Mon Sep 17 00:00:00 2001
From: Joel Beckmeyer <joel@beckmeyer.us>
Date: Tue, 28 Mar 2023 12:17:16 -0400
Subject: [PATCH] prometheus: update to 2.43.0.
update run script to properly increase max open files limit
---
srcpkgs/prometheus/files/prometheus/run | 4 +++-
srcpkgs/prometheus/template | 4 ++--
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/prometheus/files/prometheus/run b/srcpkgs/prometheus/files/prometheus/run
index 1d72db840ff3..7e3a02c65e1d 100755
--- a/srcpkgs/prometheus/files/prometheus/run
+++ b/srcpkgs/prometheus/files/prometheus/run
@@ -3,8 +3,10 @@ exec 2>&1
[ -f ./conf ] && . ./conf
+ulimit -n ${MAX_OPEN_FILES:-8192}
+
: ${WRKDIR:=/var/lib/prometheus}
cd "${WRKDIR}"
-exec chpst -o 8192 -u _prometheus prometheus --config.file=/etc/prometheus/prometheus.yml $ARGS 2>&1
+exec chpst -u _prometheus prometheus --config.file=/etc/prometheus/prometheus.yml $ARGS 2>&1
diff --git a/srcpkgs/prometheus/template b/srcpkgs/prometheus/template
index 10ca3c2fcdb9..19640168bae2 100644
--- a/srcpkgs/prometheus/template
+++ b/srcpkgs/prometheus/template
@@ -1,6 +1,6 @@
# Template file for 'prometheus'
pkgname=prometheus
-version=2.40.7
+version=2.43.0
revision=1
build_style=go
go_import_path="github.com/prometheus/prometheus"
@@ -18,7 +18,7 @@ license="Apache-2.0, MIT"
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=83b4e891204500fc798b5a9e86d0189cbef7f8274c3303c215da5e2c75df6cde
+checksum=0cd8860e5f10d0ecb35d20d23252ddc459e8319882dc163bf71b723e3bcafd71
system_accounts="_prometheus"
next reply other threads:[~2023-03-28 16:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 16:22 TinfoilSubmarine [this message]
2023-03-29 0:45 ` [PR PATCH] [Merged]: " abenson
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-43071@inbox.vuxu.org \
--to=tinfoilsubmarine@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).