From: non-Jedi <non-Jedi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-jupyter_console: tarball from github instead of pypi
Date: Tue, 07 Jul 2020 15:54:39 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23446@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 544 bytes --]
There is a new pull request by non-Jedi against master on the void-packages repository
https://github.com/non-Jedi/void-packages python3-jupyter_console/add-script
https://github.com/void-linux/void-packages/pull/23446
python3-jupyter_console: tarball from github instead of pypi
The tarball on pypi does not include the scripts dir which is where
/usr/bin/jupyter-console is installed from. Earlier versions included
the scripts directory on pypi.
A patch file from https://github.com/void-linux/void-packages/pull/23446.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-jupyter_console/add-script-23446.patch --]
[-- Type: text/x-diff, Size: 1581 bytes --]
From 83058bc34da0e5079579bcca372bd7d8f6f692e9 Mon Sep 17 00:00:00 2001
From: Adam Beckmeyer <adam_gpg@thebeckmeyers.xyz>
Date: Tue, 7 Jul 2020 09:49:55 -0400
Subject: [PATCH] python3-jupyter_console: tarball from github instead of pypi
The tarball on pypi does not include the scripts dir which is where
/usr/bin/jupyter-console is installed from. Earlier versions included
the scripts directory on pypi.
---
srcpkgs/python3-jupyter_console/template | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/python3-jupyter_console/template b/srcpkgs/python3-jupyter_console/template
index 85cdf4df567..3a56c47392b 100644
--- a/srcpkgs/python3-jupyter_console/template
+++ b/srcpkgs/python3-jupyter_console/template
@@ -1,7 +1,7 @@
# Template file for 'python3-jupyter_console'
pkgname=python3-jupyter_console
version=6.1.0
-revision=1
+revision=2
archs=noarch
wrksrc="jupyter_console-${version}"
build_style=python3-module
@@ -13,8 +13,9 @@ short_desc="Jupyter terminal console (Python3)"
maintainer="Alessio Sergi <al3hex@gmail.com>"
license="BSD-3-Clause"
homepage="https://github.com/jupyter/jupyter_console"
-distfiles="${PYPI_SITE}/j/jupyter_console/jupyter_console-${version}.tar.gz"
-checksum=6f6ead433b0534909df789ea64f0a14cdf9b6b2360757756f08182be4b9e431b
+# pypi release of jupyter_console v6.1.0 does not include scripts dir
+distfiles="${homepage}/archive/${version}.tar.gz"
+checksum=838c95c99ce52978e1660e7a30dd933dede158e2f4da1bc5fad1a8fad44570b7
# alternatives will be a conflict
conflicts="python-jupyter_console<=6.0.0_2"
next reply other threads:[~2020-07-07 13:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 13:54 non-Jedi [this message]
2020-07-07 15:45 ` sgn
2020-07-07 15:52 ` non-Jedi
2020-07-07 19:40 ` non-Jedi
2020-07-07 23:52 ` [PR PATCH] [Merged]: " sgn
2020-07-08 13:25 ` non-Jedi
2020-07-08 16:04 ` sgn
2020-07-08 16:12 ` non-Jedi
2020-07-08 16:32 ` non-Jedi
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-23446@inbox.vuxu.org \
--to=non-jedi@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).