From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libbytesize: update to 2.7.
Date: Sat, 19 Nov 2022 23:46:03 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40627@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
There is a new pull request by motorto against master on the void-packages repository
https://github.com/motorto/void-packages libbytesize_2.7
https://github.com/void-linux/void-packages/pull/40627
libbytesize: update to 2.7.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **NO**, small bump news doesn't state anything that could change workflow,
`https://github.com/storaged-project/libbytesize/blob/master/NEWS.rst`
#### Local build testing
- I built this PR locally for my native architecture, x86_64-musl
A patch file from https://github.com/void-linux/void-packages/pull/40627.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libbytesize_2.7-40627.patch --]
[-- Type: text/x-diff, Size: 1633 bytes --]
From c1a4ea0c3a21e84faef378cf8d7bd7f3e777ac53 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Cerqueira?= <acerqueira021@gmail.com>
Date: Sat, 19 Nov 2022 22:44:37 +0000
Subject: [PATCH] libbytesize: update to 2.7.
---
srcpkgs/libbytesize/template | 13 +++----------
1 file changed, 3 insertions(+), 10 deletions(-)
diff --git a/srcpkgs/libbytesize/template b/srcpkgs/libbytesize/template
index 884bcb8918d8..2aabc29dcc64 100644
--- a/srcpkgs/libbytesize/template
+++ b/srcpkgs/libbytesize/template
@@ -1,7 +1,7 @@
# Template file for 'libbytesize'
pkgname=libbytesize
-version=2.6
-revision=3
+version=2.7
+revision=1
build_style=gnu-configure
hostmakedepends="gettext python3"
makedepends="mpfr-devel pcre2-devel"
@@ -12,17 +12,10 @@ license="LGPL-2.1-or-later"
homepage="https://github.com/storaged-project/libbytesize"
changelog="https://raw.githubusercontent.com/storaged-project/libbytesize/master/NEWS.rst"
distfiles="https://github.com/storaged-project/libbytesize/releases/download/${version}/libbytesize-${version}.tar.gz"
-checksum=efaa2b35b2bb3b52bf7b4ff5d0ed2c5c61360a5196053808d615dd0aa2cf0741
+checksum=8bae8287af6ef5624c320f70defdcd84ddc0c2057d3b59a5871897f27697811e
# checks fails in libbytesize_unittest.sh
make_check=no
-pre_check() {
- # Disable test that depends on unpackaged pocketlint
- sed -i 's|canary_tests.sh$||g' tests/Makefile
- # Default locale doesn't work
- sed -i 's|DEFAULT_LOCALE =.*|DEFAULT_LOCALE = "C"|g' tests/libbytesize_unittest.py
-}
-
libbytesize-devel_package() {
depends="${makedepends} ${sourcepkg}>=${version}_${revision}"
short_desc+=" - development files"
next reply other threads:[~2022-11-19 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 22:46 motorto [this message]
2022-11-24 7:01 ` [PR PATCH] [Merged]: " classabbyamp
2022-11-20 11:57 [PR PATCH] " skmpz
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-40627@inbox.vuxu.org \
--to=motorto@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).