From: BlueChrystal <BlueChrystal@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] alacritty: update to 0.8.0.
Date: Wed, 19 May 2021 17:26:36 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30993@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]
There is a new pull request by BlueChrystal against master on the void-packages repository
https://github.com/BlueChrystal/void-packages alacritty-0.8.0_1
https://github.com/void-linux/void-packages/pull/30993
alacritty: update to 0.8.0.
<!-- Mark items with [x] where applicable -->
#### 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
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] 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/30993.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-alacritty-0.8.0_1-30993.patch --]
[-- Type: text/x-diff, Size: 1071 bytes --]
From 98eaa45f1ef6f88be4bdd97ef39f752fa5cec773 Mon Sep 17 00:00:00 2001
From: BlueChrystal <84290062+BlueChrystal@users.noreply.github.com>
Date: Wed, 19 May 2021 18:25:40 +0300
Subject: [PATCH] alacritty: update to 0.8.0.
---
srcpkgs/alacritty/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/alacritty/template b/srcpkgs/alacritty/template
index 7a679de9696c..e0e7f9a849c5 100644
--- a/srcpkgs/alacritty/template
+++ b/srcpkgs/alacritty/template
@@ -1,6 +1,6 @@
# Template file for 'alacritty'
pkgname=alacritty
-version=0.7.2
+version=0.8.0
revision=1
build_wrksrc="${pkgname}"
build_style=cargo
@@ -13,7 +13,7 @@ license="Apache-2.0"
homepage="https://github.com/alacritty/alacritty"
changelog="https://raw.githubusercontent.com/alacritty/alacritty/master/CHANGELOG.md"
distfiles="${homepage}/archive/v${version}.tar.gz"
-checksum=750c294d384d23f1dfc30e9105380e4194507b0828ac91d8ffd94c9bbc18d6c3
+checksum=e450ff4ceafdf4894d82f2f22ca93b422ffd1283f876d44cf744e4ed3bc0eaf6
case "$XBPS_TARGET_MACHINE" in
ppc64*) ;;
next reply other threads:[~2021-05-19 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 15:26 BlueChrystal [this message]
2021-05-19 15:47 ` [PR PATCH] [Merged]: " ahesford
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-30993@inbox.vuxu.org \
--to=bluechrystal@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).