From: SpidFightFR <SpidFightFR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] lolcat-c: update to 1.4.
Date: Wed, 01 Mar 2023 20:11:21 +0100 [thread overview]
Message-ID: <20230301191121.y564xKYTAV6TFPMnyC6VUCCzEzEq0a721WH0CnTgEJE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42482@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 671 bytes --]
There is an updated pull request by SpidFightFR against master on the void-packages repository
https://github.com/SpidFightFR/void-packages patch-1
https://github.com/void-linux/void-packages/pull/42482
lolcat-c: update to 1.4.
This version fix an issue with neofetch (see: https://github.com/jaseg/lolcat/issues/48 )
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64 Glibc)
A patch file from https://github.com/void-linux/void-packages/pull/42482.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-patch-1-42482.patch --]
[-- Type: text/x-diff, Size: 996 bytes --]
From f97e8dc6166382a848b090100c08bc2cc7f5c5d0 Mon Sep 17 00:00:00 2001
From: SpidFightFR <vincent.bardot@outlook.fr>
Date: Wed, 1 Mar 2023 18:29:27 +0000
Subject: [PATCH] lolcat-c: update to 1.4.
---
srcpkgs/lolcat-c/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/lolcat-c/template b/srcpkgs/lolcat-c/template
index 3db29baec216..8b01acf704d1 100644
--- a/srcpkgs/lolcat-c/template
+++ b/srcpkgs/lolcat-c/template
@@ -1,6 +1,6 @@
# Template file for 'lolcat-c'
pkgname=lolcat-c
-version=1.3
+version=1.4
revision=1
build_style=gnu-makefile
make_build_target="lolcat"
@@ -9,7 +9,7 @@ maintainer="John <me@johnnynator.dev>"
license="WTFPL"
homepage="https://github.com/jaseg/lolcat"
distfiles="https://github.com/jaseg/lolcat/archive/refs/tags/v${version}.tar.gz"
-checksum=5596c9ad40f78cc40483ada3fed25f9fa743b4d281b00c2b78de02f49a415d10
+checksum=6ea43ee2b2bb2f15fc91812b72ebcdaa883052853ed8f055b6f8b38637bda909
do_install() {
vbin lolcat
next prev parent reply other threads:[~2023-03-01 19:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 11:50 [PR PATCH] Update lolcat-c to 1.4 version SpidFightFR
2023-02-27 18:56 ` icp1994
2023-02-28 5:12 ` lolcat-c: update " SpidFightFR
2023-02-28 5:16 ` icp1994
2023-02-28 5:53 ` SpidFightFR
2023-02-28 21:58 ` paper42
2023-03-01 10:22 ` SpidFightFR
2023-03-01 10:42 ` paper42
2023-03-01 12:04 ` SpidFightFR
2023-03-01 12:45 ` paper42
2023-03-01 12:45 ` paper42
2023-03-01 12:45 ` paper42
2023-03-01 12:59 ` SpidFightFR
2023-03-01 13:22 ` [PR PATCH] [Updated] " SpidFightFR
2023-03-01 13:25 ` SpidFightFR
2023-03-01 13:43 ` paper42
2023-03-01 14:35 ` SpidFightFR
2023-03-01 14:36 ` SpidFightFR
2023-03-01 16:15 ` paper42
2023-03-01 18:35 ` [PR PATCH] [Updated] " SpidFightFR
2023-03-01 18:36 ` SpidFightFR
2023-03-01 18:55 ` paper42
2023-03-01 18:58 ` lolcat-c: update to 1.4 SpidFightFR
2023-03-01 19:06 ` paper42
2023-03-01 19:07 ` SpidFightFR
2023-03-01 19:11 ` SpidFightFR [this message]
2023-03-01 19:12 ` SpidFightFR
2023-03-02 21:14 ` paper42
2023-03-02 21:14 ` [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=20230301191121.y564xKYTAV6TFPMnyC6VUCCzEzEq0a721WH0CnTgEJE@z \
--to=spidfightfr@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).