From: tranzystorek-io <tranzystorek-io@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] zellij: update to 0.29.0
Date: Mon, 02 May 2022 15:34:11 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36952@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]
There is a new pull request by tranzystorek-io against master on the void-packages repository
https://github.com/tranzystorek-io/void-packages zellij-0.29.0
https://github.com/void-linux/void-packages/pull/36952
zellij: update to 0.29.0
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-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/36952.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-zellij-0.29.0-36952.patch --]
[-- Type: text/x-diff, Size: 1160 bytes --]
From 51e353b26c159bae2b1c7b02eaddae725ff14ce0 Mon Sep 17 00:00:00 2001
From: Marcin Puc <tranzystorek.io@protonmail.com>
Date: Mon, 2 May 2022 15:32:43 +0200
Subject: [PATCH] zellij: update to 0.29.0
---
srcpkgs/zellij/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/zellij/template b/srcpkgs/zellij/template
index 20a338d9103e..505f83cff7f5 100644
--- a/srcpkgs/zellij/template
+++ b/srcpkgs/zellij/template
@@ -1,6 +1,6 @@
# Template file for 'zellij'
pkgname=zellij
-version=0.28.1
+version=0.29.0
revision=1
# Dependency crate `wasmer-vm` only supports the following archs: x86_64, arm64, x86
# https://docs.wasmer.io/ecosystem/wasmer/wasmer-features#compiler-support-by-chipset
@@ -15,7 +15,7 @@ license="MIT"
homepage="https://zellij.dev"
changelog="https://github.com/zellij-org/zellij/blob/main/CHANGELOG.md"
distfiles="https://github.com/zellij-org/zellij/archive/v${version}.tar.gz"
-checksum=8c9495e70b1c0179200d6137dd892776c7153b0b54115edf0f39fd732bb62efe
+checksum=376171f1e1b2ebf71f2c8c190ec4416448ea392cdb0df21f49e767b8749ae0a3
post_build() {
ZELLIJ="target/${RUST_TARGET}/release/zellij"
next reply other threads:[~2022-05-02 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 13:34 tranzystorek-io [this message]
2022-05-02 21:32 ` [PR PATCH] [Updated] " tranzystorek-io
2022-05-02 21:50 ` [PR PATCH] [Updated] zellij: update to 0.29.1 tranzystorek-io
2022-05-04 6:11 ` tranzystorek-io
2022-05-04 8:24 ` [PR PATCH] [Merged]: " 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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36952@inbox.vuxu.org \
--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).