Github messages for voidlinux
 help / color / mirror / Atom feed
From: wpbirney <wpbirney@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: scons: update to 4.4.0
Date: Mon, 01 Aug 2022 21:00:33 +0200	[thread overview]
Message-ID: <20220801190033.XYllV_eHfGAzyHTuPY5-3Cj5wRm9zBbT1Xd44nswq1k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38396@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 592 bytes --]

New comment by wpbirney on void-packages repository

https://github.com/void-linux/void-packages/pull/38396#issuecomment-1201590802

Comment:
i had to `make_check=no`. I talked with the developer of scons and was told the release tarballs do not contain the tests. If we want to test it, we have to build from the repo tree instead and also package some extra python3 deps that are missing from the void repos.

Whichever way you guys wanna go, if you want tests i can build from the tree and create templates for the missing python3 deps. Or we can use the release tarball without checks?

  parent reply	other threads:[~2022-08-01 19:00 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-31 17:04 [PR PATCH] " wpbirney
2022-07-31 17:06 ` [PR PATCH] [Updated] " wpbirney
2022-07-31 17:24 ` wpbirney
2022-07-31 18:08 ` [PR PATCH] [Closed]: " wpbirney
2022-07-31 18:08 ` wpbirney
2022-07-31 18:11 ` abenson
2022-07-31 18:18 ` abenson
2022-07-31 19:20 ` [PR PATCH] [Updated] WIP: " wpbirney
2022-07-31 19:35 ` wpbirney
2022-07-31 22:04 ` wpbirney
2022-07-31 22:11 ` wpbirney
2022-07-31 22:22 ` wpbirney
2022-07-31 22:26 ` wpbirney
2022-08-01 16:29 ` [PR REVIEW] " sgn
2022-08-01 16:29 ` sgn
2022-08-01 16:29 ` sgn
2022-08-01 16:29 ` sgn
2022-08-01 16:29 ` sgn
2022-08-01 16:44 ` wpbirney
2022-08-01 16:45 ` wpbirney
2022-08-01 16:47 ` wpbirney
2022-08-01 16:49 ` wpbirney
2022-08-01 16:55 ` wpbirney
2022-08-01 16:56 ` wpbirney
2022-08-01 17:01 ` [PR PATCH] [Updated] " wpbirney
2022-08-01 17:14 ` [PR REVIEW] " wpbirney
2022-08-01 17:19 ` [PR PATCH] [Updated] " wpbirney
2022-08-01 17:21 ` wpbirney
2022-08-01 18:53 ` wpbirney
2022-08-01 19:00 ` wpbirney [this message]
2022-08-01 19:01 ` wpbirney
2022-08-01 19:50 ` abenson
2022-08-01 23:38 ` abenson
2022-08-02  0:01 ` wpbirney
2022-08-02  0:09 ` abenson
2022-08-02  0:35 ` abenson
2022-08-02  0:35 ` abenson
2022-08-02  0:37 ` abenson
2022-08-02  0:37 ` abenson
2022-08-02  0:40 ` abenson
2022-08-02  0:40 ` abenson
2022-08-02  0:41 ` abenson
2022-08-02  0:43 ` abenson
2022-08-02  0:43 ` abenson
2022-08-02  0:45 ` abenson
2022-08-02  0:57 ` abenson
2022-08-02  0:59 ` abenson
2022-08-02  1:01 ` abenson
2022-08-02  1:05 ` abenson
2022-08-02  1:07 ` abenson
2022-08-02  1:08 ` abenson
2022-08-02  1:16 ` abenson
2022-08-02 18:06 ` abenson
2022-08-02 18:06 ` [PR PATCH] [Merged]: " abenson

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=20220801190033.XYllV_eHfGAzyHTuPY5-3Cj5wRm9zBbT1Xd44nswq1k@z \
    --to=wpbirney@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).