From: klarasm <klarasm@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: routinator: integrate better into Void Linux
Date: Mon, 22 Aug 2022 02:19:36 +0200 [thread overview]
Message-ID: <20220822001936.QsQGxsSsbjkN2MtjdsDKQfh8rqCttLakP0zKdFoIA-Q@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37848@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 347 bytes --]
New comment by klarasm on void-packages repository
https://github.com/void-linux/void-packages/pull/37848#issuecomment-1221654847
Comment:
I've added the missing python packages, basically no testing done for them but the manual for routinator builds without pip now.
Is it ok for them to be in the same PR or should I create a separate one?
next prev parent reply other threads:[~2022-08-22 0:19 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 21:08 [PR PATCH] " klarasm
2022-08-21 17:50 ` [PR PATCH] [Updated] " klarasm
2022-08-21 17:55 ` klarasm
2022-08-21 17:58 ` Duncaen
2022-08-21 18:18 ` [PR PATCH] [Updated] " klarasm
2022-08-21 22:21 ` klarasm
2022-08-21 22:44 ` klarasm
2022-08-21 22:58 ` klarasm
2022-08-21 23:06 ` Duncaen
2022-08-21 23:06 ` Duncaen
2022-08-21 23:10 ` [PR REVIEW] " paper42
2022-08-21 23:12 ` klarasm
2022-08-21 23:14 ` [PR REVIEW] " klarasm
2022-08-21 23:19 ` [PR PATCH] [Updated] " klarasm
2022-08-22 0:19 ` klarasm
2022-08-22 0:19 ` klarasm [this message]
2022-08-22 0:53 ` klarasm
2022-09-28 21:32 ` klarasm
2022-09-30 19:50 ` klarasm
2022-10-22 12:04 ` klarasm
2022-11-09 12:11 ` klarasm
2022-11-13 15:47 ` [PR PATCH] [Updated] " klarasm
2022-11-13 15:50 ` klarasm
2022-11-13 16:14 ` klarasm
2022-11-15 18:31 ` [PR PATCH] [Updated] " klarasm
2022-11-15 18:45 ` klarasm
2022-11-15 18:49 ` klarasm
2023-01-11 16:36 ` [PR PATCH] [Updated] routinator: update to 0.12.0 and add runit service klarasm
2023-01-11 16:57 ` routinator: update to 0.12.1 " klarasm
2023-01-11 23:13 ` [PR REVIEW] " paper42
2023-01-11 23:35 ` [PR PATCH] [Updated] " klarasm
2023-01-11 23:36 ` [PR REVIEW] " klarasm
2023-01-12 16:07 ` paper42
2023-01-12 16:07 ` [PR PATCH] [Merged]: " paper42
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=20220822001936.QsQGxsSsbjkN2MtjdsDKQfh8rqCttLakP0zKdFoIA-Q@z \
--to=klarasm@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).