From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] [WIP] updates to jupyter, jupyterlab, notebook, etc.
Date: Tue, 30 May 2023 04:15:25 +0200 [thread overview]
Message-ID: <20230530021525.bIISverhEiTaZ50-_5O5uSpNBi_D3cVCcZqQZ-L2C_0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44160@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/44160#issuecomment-1567673646
Comment:
@dkwo: maybe you want to test; still WIP.
I've been insistent on making check pass as much as possible. Yet there are some circular checkdepends (but not that many) so CI might fail... we'll see.
Cycles I know about:
- `jupyter_client`, `ipython` have `checkdepends` on `ipykernel`, but the latter build depends on the former
- `ipython` has `checkdepends` on `nbformat`, but the latter build depends on the former
- `ipykernel` has `checkdepends` on `ipyparallel`, but the latter build depends on the former
- `nbclient` has `checkdepends` on `nbconvert`, but the latter build depends on the former
- `jupyter_server_terminals` has `checkdepends` on `jupyter_server`, but the latter build depends on the former
- `pytest_jupyter` has `checkdepends` on `jupyter_server`, but the latter check depends on the former
There are no build cycles.
I guess CI cycles can be broken by setting `make_check=ci-skip` in a few packages. In principle this is only a problem if two packages are updated in the same PR (like here, everything is updated at the same time since lots of packages are quite old).
next prev parent reply other threads:[~2023-05-30 2:15 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 2:01 [PR PATCH] " tornaria
2023-05-30 2:15 ` tornaria [this message]
2023-05-30 21:51 ` dkwo
2023-05-31 0:10 ` tornaria
2023-06-28 21:30 ` dkwo
2023-07-06 1:43 ` dkwo
2023-07-06 2:08 ` [PR REVIEW] " classabbyamp
2023-08-19 8:42 ` dkwo
2023-08-19 8:42 ` dkwo
2023-08-19 19:00 ` tornaria
2023-09-26 1:47 ` [PR PATCH] [Updated] " tornaria
2023-09-26 13:54 ` tornaria
2023-09-26 19:46 ` tornaria
2023-09-26 20:27 ` tornaria
2023-09-27 13:00 ` tornaria
2023-09-28 1:40 ` tornaria
2023-09-28 23:40 ` tornaria
2023-09-29 0:48 ` tornaria
2023-09-29 12:30 ` tornaria
2023-09-30 2:53 ` tornaria
2023-09-30 15:49 ` tornaria
2023-10-02 19:06 ` dkwo
2023-10-03 0:15 ` tornaria
2023-10-03 15:19 ` dkwo
2023-10-09 21:10 ` [PR PATCH] [Updated] " tornaria
2023-10-09 21:31 ` tornaria
2023-10-09 21:31 ` tornaria
2023-10-09 21:41 ` [PR PATCH] [Updated] " tornaria
2023-10-09 22:11 ` tornaria
2023-10-09 22:31 ` dkwo
2023-10-10 13:44 ` tornaria
2023-10-10 14:21 ` [PR PATCH] [Updated] " tornaria
2023-10-10 15:19 ` tornaria
2023-10-10 16:22 ` Updates " tornaria
2023-10-10 16:24 ` tornaria
2023-10-10 16:29 ` [PR PATCH] [Merged]: " ahesford
2023-10-10 17:34 ` dkwo
2023-10-10 20:32 ` tornaria
2023-10-10 21:00 ` dkwo
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=20230530021525.bIISverhEiTaZ50-_5O5uSpNBi_D3cVCcZqQZ-L2C_0@z \
--to=tornaria@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).