From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] jrnl: update to 3.1.
Date: Fri, 26 Aug 2022 18:54:08 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38926@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 768 bytes --]
There is a new pull request by icp1994 against master on the void-packages repository
https://github.com/icp1994/void-packages jrnl
https://github.com/void-linux/void-packages/pull/38926
jrnl: update to 3.1.
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, x86_64
Changed the deps as per [upstream requirements](https://github.com/jrnl-org/jrnl/blob/v3.1/pyproject.toml#L29-L43). Tried to make the tests work using a gh tarballs with tests but there are at least 4 unpackaged deps under the fulldeptree for tests. Runtime testing seemed fine with basic operations.
A patch file from https://github.com/void-linux/void-packages/pull/38926.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-jrnl-38926.patch --]
[-- Type: text/x-diff, Size: 1595 bytes --]
From 338db89675c4653870d2aa5e2c5f33811d1bcaf8 Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Fri, 26 Aug 2022 16:25:32 +0530
Subject: [PATCH] jrnl: update to 3.1.
---
srcpkgs/jrnl/template | 15 +++++++--------
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git a/srcpkgs/jrnl/template b/srcpkgs/jrnl/template
index 5301ac052158..83c1cdb0e78a 100644
--- a/srcpkgs/jrnl/template
+++ b/srcpkgs/jrnl/template
@@ -1,19 +1,18 @@
# Template file for 'jrnl'
pkgname=jrnl
-version=3.0
+version=3.1
revision=1
-build_style=python3-module
-hostmakedepends="python3-setuptools"
-depends="python3-ansiwrap python3-asteval python3-colorama python3-cryptography
- python3-dateutil python3-keyring python3-parsedatetime python3-passlib
- python3-pytz python3-tzlocal python3-xdg python3-yaml python3-packaging
- python3-ruamel.yaml"
+build_style=python3-pep517
+hostmakedepends="python3-poetry-core"
+depends="python3-ansiwrap python3-colorama python3-cryptography
+ python3-dateutil python3-keyring python3-parsedatetime python3-rich
+ python3-tzlocal python3-xdg python3-ruamel.yaml"
short_desc="Simple journal application for your command line"
maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-3.0-only"
homepage="https://jrnl.sh"
changelog="https://raw.githubusercontent.com/jrnl-org/jrnl/develop/CHANGELOG.md"
distfiles="${PYPI_SITE}/j/jrnl/jrnl-${version}.tar.gz"
-checksum=e676780351fd92a34855b802e6ca3d95041b8b6d4d4ed621b121e66908079e73
+checksum=f1c1438b26f01f09266693870c7e81e2cb9d28b9b4d3b7c60ccda06da4189a8b
# Tarball provides no tests
make_check=no
next reply other threads:[~2022-08-26 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 16:54 icp1994 [this message]
2022-08-26 16:57 ` icp1994
2022-08-26 16:57 ` [PR PATCH] [Closed]: " icp1994
-- strict thread matches above, loose matches on Subject: below --
2022-08-26 13:24 [PR PATCH] " clyhtsuriva
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-38926@inbox.vuxu.org \
--to=icp1994@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).