From: ashpooljh <ashpooljh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: jrnl: update to 2.5.
Date: Fri, 20 Nov 2020 01:45:23 +0100 [thread overview]
Message-ID: <20201120004523.rCxrHvVn5jzOZ76bUjIjMkeX-FDG9nFwLMJYChI8RE4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26398@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 693 bytes --]
New comment by ashpooljh on void-packages repository
https://github.com/void-linux/void-packages/pull/26398#issuecomment-730727935
Comment:
Sorry, I haven't yet found a way to make this work. There's no `Makefile` bundled with the Python module on PyPI.
Things we can try:
- change the upstream to GitHub and build it using the `gnu-makefile` style, not `python3-module`, and use `make test` for checking, or
- figure out why `python3-module`-style `do_check()` fails and patch the package to pass it.
For now, I added the `checkdepends` to fix the warnings, but the check phase remains broken. For anyone who'd like to try to fix it, I'll paste the full output of this phase below.
next prev parent reply other threads:[~2020-11-20 0:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 11:01 [PR PATCH] " ashpooljh
2020-11-19 4:17 ` ericonr
2020-11-19 14:08 ` ashpooljh
2020-11-19 14:09 ` ashpooljh
2020-11-19 15:03 ` ericonr
2020-11-19 15:05 ` ericonr
2020-11-20 0:37 ` [PR PATCH] [Updated] " ashpooljh
2020-11-20 0:44 ` ashpooljh
2020-11-20 0:44 ` ashpooljh
2020-11-20 0:45 ` ashpooljh [this message]
2020-11-20 0:47 ` jrnl: update to 2.5, add checkdepends ashpooljh
2020-11-23 5:09 ` ericonr
2020-12-22 12:39 ` [PR PATCH] [Closed]: " sgn
2020-12-21 17:02 [PR PATCH] jrnl: update to 2.6 ndowens
2020-12-22 3:58 ` jrnl: update to 2.5 ericonr
2020-12-22 9:59 [PR PATCH] " Eluminae
2020-12-22 12:38 ` sgn
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=20201120004523.rCxrHvVn5jzOZ76bUjIjMkeX-FDG9nFwLMJYChI8RE4@z \
--to=ashpooljh@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).