From: tranzystorek-io <tranzystorek-io@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] eza: update to 0.15.0
Date: Thu, 19 Oct 2023 18:37:50 +0200 [thread overview]
Message-ID: <20231019163750.WBvow3xCP3wBzfQlO-6D5H5qti6EYJvdu0oncp-defI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46775@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]
There is an updated pull request by tranzystorek-io against master on the void-packages repository
https://github.com/tranzystorek-io/void-packages eza
https://github.com/void-linux/void-packages/pull/46775
eza: update to 0.15.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/46775.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-eza-46775.patch --]
[-- Type: text/x-diff, Size: 1237 bytes --]
From 028e71b76dcc4f75dc3ded874ba371cd48793607 Mon Sep 17 00:00:00 2001
From: Marcin Puc <tranzystorek.io@protonmail.com>
Date: Thu, 19 Oct 2023 16:24:34 +0200
Subject: [PATCH] eza: update to 0.15.0
---
srcpkgs/eza/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/eza/template b/srcpkgs/eza/template
index d2a39233b270c..0cb3003dcd34e 100644
--- a/srcpkgs/eza/template
+++ b/srcpkgs/eza/template
@@ -1,6 +1,6 @@
# Template file for 'eza'
pkgname=eza
-version=0.14.2
+version=0.15.0
revision=1
build_style=cargo
hostmakedepends="pandoc pkg-config"
@@ -8,10 +8,10 @@ makedepends="libgit2-devel"
short_desc="Modern, maintained replacement for ls"
maintainer="Marcin Puc <tranzystorek.io@protonmail.com>"
license="MIT"
-homepage="https://github.com/eza-community/eza"
+homepage="https://eza.rocks"
changelog="https://raw.githubusercontent.com/eza-community/eza/main/CHANGELOG.md"
distfiles="https://github.com/eza-community/eza/archive/refs/tags/v${version}.tar.gz"
-checksum=155d6e38a37c9d2fd32d2234662dba2e0f50b553826dfff290ae8f7c16dbb389
+checksum=e4cce5a6f60e6b7405af911e3f168cf17a1e86c33c292a449c1c25c15052967a
post_patch() {
cargo update --package git2@0.18.1 --precise 0.17.2
next prev parent reply other threads:[~2023-10-19 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 14:25 [PR PATCH] " tranzystorek-io
2023-10-19 15:40 ` icp1994
2023-10-19 16:37 ` tranzystorek-io [this message]
2023-10-19 16:39 ` tranzystorek-io
2023-10-19 23:04 ` [PR PATCH] [Merged]: " classabbyamp
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=20231019163750.WBvow3xCP3wBzfQlO-6D5H5qti6EYJvdu0oncp-defI@z \
--to=tranzystorek-io@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).