Github messages for voidlinux
 help / color / mirror / Atom feed
From: k4leg <k4leg@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: reuse-0.13.0
Date: Mon, 30 Aug 2021 20:45:15 +0200	[thread overview]
Message-ID: <20210830184515.6Ab-6QQqwASb2qz00iYOG8KnAxBRJ3cVrfIU8mMu9jo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32746@inbox.vuxu.org>

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

New comment by k4leg on void-packages repository

https://github.com/void-linux/void-packages/pull/32746#issuecomment-908593853

Comment:
>     * `make_check=` has to be justified

I don't understand why but the tests fail in CI (see [this](https://github.com/void-linux/void-packages/actions/runs/1179827994)). With a local build everything is fine. Perhaps this will change after switching from tox to other.

>     * testing with tox undex xbps-src is useless, try good deprecated things

Btw I saw in some packages tests are missing because some dependencies are missing. Is it okay to do the same or is it better to pack them? This is why I used tox.

  parent reply	other threads:[~2021-08-30 18:45 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-29 18:12 [PR PATCH] " k4leg
2021-08-29 18:14 ` [PR PATCH] [Updated] " k4leg
2021-08-29 18:17 ` k4leg
2021-08-29 19:25 ` k4leg
2021-08-30 17:42 ` Chocimier
2021-08-30 17:46 ` Chocimier
2021-08-30 18:01 ` paper42
2021-08-30 18:01 ` paper42
2021-08-30 18:05 ` Chocimier
2021-08-30 18:16 ` paper42
2021-08-30 18:25 ` Chocimier
2021-08-30 18:36 ` paper42
2021-08-30 18:45 ` k4leg [this message]
2021-08-30 19:17 ` Chocimier
2021-09-01 19:49 ` [PR PATCH] [Updated] " k4leg
2021-09-02 17:32 ` [PR REVIEW] " paper42
2021-09-02 17:32 ` paper42
2021-09-02 17:32 ` paper42
2021-09-02 17:32 ` paper42
2021-09-02 19:21 ` k4leg
2021-09-02 19:33 ` [PR PATCH] [Updated] " k4leg
2021-09-02 19:50 ` k4leg
2021-09-04  9:38 ` k4leg
2021-09-04 20:15 ` [PR REVIEW] " Chocimier
2021-09-04 20:30 ` [PR PATCH] [Updated] " k4leg
2021-09-04 20:53 ` [PR REVIEW] " Chocimier
2021-09-04 21:27 ` [PR PATCH] [Updated] " k4leg
2021-09-04 21:30 ` [PR REVIEW] " k4leg
2021-09-04 21:34 ` [PR PATCH] [Updated] " k4leg
2021-09-04 22:49 ` [PR REVIEW] " paper42
2021-09-04 22:53 ` paper42
2021-09-04 22:53 ` paper42
2021-09-04 22:54 ` paper42
2021-09-04 22:59 ` paper42
2021-09-05 11:09 ` k4leg
2021-09-05 11:37 ` k4leg
2021-09-05 11:43 ` [PR PATCH] [Updated] " k4leg
2021-09-17 17:10 ` [PR PATCH] [Merged]: " Chocimier

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=20210830184515.6Ab-6QQqwASb2qz00iYOG8KnAxBRJ3cVrfIU8mMu9jo@z \
    --to=k4leg@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).