From: yuriy-chumak <yuriy-chumak@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] ol: update to 2.3.
Date: Mon, 21 Feb 2022 20:25:29 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35739@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1616 bytes --]
There is a new pull request by yuriy-chumak against master on the void-packages repository
https://github.com/yuriy-chumak/void-packages ol
https://github.com/void-linux/void-packages/pull/35739
ol: update to 2.3.
#### General
* [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
* [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
* [ ] I generally don't use the affected packages but briefly tested this PR
#### Does it build and run successfully?
* [x] I built this PR locally for my native architecture:
* [x] x86_64
* [x] I built this PR locally for these architectures:
* [x] aarch64-musl
* [x] aarch64
* [x] armv5tel-musl
* [x] armv5tel
* [x] armv5te-musl
* [x] armv5te
* [x] armv6hf-musl
* [x] armv6hf
* [x] armv6l-musl
* [x] armv6l
* [x] armv7hf-musl
* [x] armv7hf
* [x] armv7l-musl
* [x] armv7l
* [x] i686-musl
* [x] i686
* [x] mipselhf-musl
* [x] mipsel-musl
* [x] mipshf-musl
* [x] mips-musl
* [x] ppc64le-musl
* [x] ppc64le
* [x] ppc64-musl
* [x] ppc64
* [x] ppcle-musl
* [x] ppcle
* [x] ppc-musl
* [x] ppc
* [x] x86_64-musl
---
Note: Yes, I really did test build for ALL of these architectures. I have a shell script that does this for me.
Will provide logs if anyone wants.
A patch file from https://github.com/void-linux/void-packages/pull/35739.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-ol-35739.patch --]
[-- Type: text/x-diff, Size: 937 bytes --]
From cdcbc29620d09e3ff61f983c071676d64ee20bcb Mon Sep 17 00:00:00 2001
From: Yuriy Chumak <yuriy.chumak@mail.com>
Date: Mon, 21 Feb 2022 21:00:12 +0200
Subject: [PATCH] ol: update to 2.3.
---
srcpkgs/ol/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/ol/template b/srcpkgs/ol/template
index 04c1b1e89874..e3c29a71f176 100644
--- a/srcpkgs/ol/template
+++ b/srcpkgs/ol/template
@@ -1,6 +1,6 @@
# Template file for 'ol'
pkgname=ol
-version=2.2.1
+version=2.3
revision=1
build_style=gnu-makefile
hostmakedepends="xxd"
@@ -9,7 +9,7 @@ maintainer="rc-05 <rc23@email.it>"
license="LGPL-3.0-or-later, MIT"
homepage="https://yuriy-chumak.github.io/ol/"
distfiles="https://github.com/yuriy-chumak/ol/archive/${version}.tar.gz"
-checksum=3afcce88ee57c861aead4a224e54504405508feb5f185b3a7819db280d5a0b5e
+checksum=99b43cb7c510b2f9345fc2ff976540689131c563a883d1bd0699124466e155a8
CFLAGS="-lm"
next reply other threads:[~2022-02-21 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 19:25 yuriy-chumak [this message]
2022-02-21 19:47 ` [PR PATCH] [Merged]: " leahneukirchen
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-35739@inbox.vuxu.org \
--to=yuriy-chumak@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).