From: jason1987d <jason1987d@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: python3-yfinance-0.1.87
Date: Sat, 19 Nov 2022 19:11:47 +0100 [thread overview]
Message-ID: <20221119181147.k5Afn6mGMxXNHE8iqiutR-vivRsmEbbm7LTWpGxXSsw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40620@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 269 bytes --]
New comment by jason1987d on void-packages repository
https://github.com/void-linux/void-packages/pull/40620#issuecomment-1320937987
Comment:
I'm trying to think of the best way to handle the binary /bin/sample conflict provided by python3-multitasking dependency...
next prev parent reply other threads:[~2022-11-19 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 17:34 [PR PATCH] " jason1987d
2022-11-19 17:38 ` [PR PATCH] [Updated] " jason1987d
2022-11-19 18:11 ` jason1987d [this message]
2023-02-19 2:01 ` github-actions
2023-03-05 2:09 ` [PR PATCH] [Closed]: " github-actions
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=20221119181147.k5Afn6mGMxXNHE8iqiutR-vivRsmEbbm7LTWpGxXSsw@z \
--to=jason1987d@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).