From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] calcurse: update to 4.8.0
Date: Tue, 22 Nov 2022 01:36:03 +0100 [thread overview]
Message-ID: <20221122003603.CutA9BzBhuQnYO_Ritg71Y71au2CIxL08bqlFA1iRZE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40632@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 387 bytes --]
There is an updated pull request by cinerea0 against master on the void-packages repository
https://github.com/cinerea0/void-packages cal
https://github.com/void-linux/void-packages/pull/40632
calcurse: update to 4.8.0
#### Testing the changes
- I tested the changes in this PR: **briefly**
A patch file from https://github.com/void-linux/void-packages/pull/40632.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-cal-40632.patch --]
[-- Type: text/x-diff, Size: 1221 bytes --]
From f143a27da3f1f6341256fcb02e1f748409ef5a1e Mon Sep 17 00:00:00 2001
From: cinerea0 <cinerea0@disroot.org>
Date: Mon, 21 Nov 2022 19:35:46 -0500
Subject: [PATCH] calcurse: update to 4.8.0
---
srcpkgs/calcurse/template | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/calcurse/template b/srcpkgs/calcurse/template
index aefd36d204da..f72aa4a5ea94 100644
--- a/srcpkgs/calcurse/template
+++ b/srcpkgs/calcurse/template
@@ -1,16 +1,18 @@
# Template file for 'calcurse'
pkgname=calcurse
-version=4.7.1
+version=4.8.0
revision=1
build_style=gnu-configure
makedepends="ncurses-devel"
depends="python3-httplib2"
+checkdepends="faketime"
short_desc="Text-based calendar and scheduling application"
maintainer="silvernode <mollusk@homebutter.com>"
license="BSD-2-Clause"
homepage="https://calcurse.org"
-distfiles="https://calcurse.org/files/${pkgname}-${version}.tar.gz"
-checksum=0a7c55d07674569d166c0b0e7587b2972d3da8160cdb7d60b1dbd2895803afb0
+changelog="https://calcurse.org/files/changes.html"
+distfiles="https://calcurse.org/files/calcurse-${version}.tar.gz"
+checksum=48a736666cc4b6b53012d73b3aa70152c18b41e6c7b4807fab0f168d645ae32c
post_install() {
vlicense COPYING
next prev parent reply other threads:[~2022-11-22 0:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 2:52 [PR PATCH] " cinerea0
2022-11-22 0:36 ` cinerea0 [this message]
2022-11-22 0:43 ` [PR PATCH] [Updated] " cinerea0
2022-11-22 0:50 ` cinerea0
2022-12-01 17:14 ` abenson
2023-01-28 15:56 ` dkwo
2023-04-29 1:52 ` github-actions
2023-04-29 14:48 ` dkwo
2023-04-29 14:52 ` dkwo
2023-04-30 4:39 ` [PR PATCH] [Updated] " cinerea0
2023-04-30 5:03 ` cinerea0
2023-04-30 13:41 ` dkwo
2023-05-30 0:32 ` [PR PATCH] [Closed]: " cinerea0
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=20221122003603.CutA9BzBhuQnYO_Ritg71Y71au2CIxL08bqlFA1iRZE@z \
--to=cinerea0@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).