From: bugcrazy <bugcrazy@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] oil: update to 0.14.1
Date: Wed, 15 Mar 2023 02:40:32 +0100 [thread overview]
Message-ID: <20230315014032.EAYG094V3_MCc7fUV1dr0TcOcarVtTywenxTHtSToEA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42370@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]
There is an updated pull request by bugcrazy against master on the void-packages repository
https://github.com/bugcrazy/void-packages patch-35
https://github.com/void-linux/void-packages/pull/42370
oil: update to 0.14.1
<!-- 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/42370.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-patch-35-42370.patch --]
[-- Type: text/x-diff, Size: 1062 bytes --]
From 4486d337aae652d0df2cde64094fdc248bd71c72 Mon Sep 17 00:00:00 2001
From: bugcrazy <marcoaureliopc@gmail.com>
Date: Tue, 14 Mar 2023 22:39:42 -0300
Subject: [PATCH] oil: update to 0.14.2
---
srcpkgs/oil/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/oil/template b/srcpkgs/oil/template
index 657a801d1aca..422eb51b7075 100644
--- a/srcpkgs/oil/template
+++ b/srcpkgs/oil/template
@@ -1,6 +1,6 @@
# Template file for 'oil'
pkgname=oil
-version=0.14.0
+version=0.14.2
revision=1
build_style=configure
configure_args="--prefix=/usr"
@@ -11,7 +11,7 @@ maintainer="MarcoAPC <marcoaureliopc@gmail.com>"
license="Apache-2.0"
homepage="https://www.oilshell.org"
distfiles="https://www.oilshell.org/download/oil-${version}.tar.xz"
-checksum=66b4f6bc77db7344bd43d7bd9438b2a6d7d20b7088890b3c0a8f453838a5ee86
+checksum=23faff0e110b2e928c9d9a9487ce3b17fb953e20981796f9ef87233f9f7e646d
register_shell="/usr/bin/osh /usr/bin/oil"
nocross="Build systems gets confused with host and cross toolchains/headers"
nostrip=yes
next prev parent reply other threads:[~2023-03-15 1:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 4:47 [PR PATCH] " bugcrazy
2023-03-15 1:40 ` bugcrazy [this message]
2023-03-15 20:24 ` [PR PATCH] [Merged]: oil: update to 0.14.2 paper42
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=20230315014032.EAYG094V3_MCc7fUV1dr0TcOcarVtTywenxTHtSToEA@z \
--to=bugcrazy@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).