Github messages for voidlinux
 help / color / mirror / Atom feed
From: mvf <mvf@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [help needed] New package: muse-3.1.1
Date: Fri, 29 Jan 2021 13:05:46 +0100	[thread overview]
Message-ID: <20210129120546.rbUZmkFbBmcTs2b18Hvdbes6h0IGFad-mZGJliiJX6A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25526@inbox.vuxu.org>

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

New comment by mvf on void-packages repository

https://github.com/void-linux/void-packages/pull/25526#issuecomment-769766192

Comment:
The `ui_` headers are generated, but the code that includes them doesn't depend on them, so sometimes they're not generated in time. That's also why retrying incrementally works. Unless we can fix the deps in `CMakeLists.txt`, the usual workaround is `disable_parallel_build=yes`.

  parent reply	other threads:[~2021-01-29 12:05 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-11 16:57 [PR PATCH] [WIP] " ev-ermakov
2020-10-11 16:59 ` ev-ermakov
2020-10-11 19:10 ` [PR PATCH] [Updated] " ev-ermakov
2020-10-12  0:38 ` [PR REVIEW] " fosslinux
2020-10-12 18:09 ` ev-ermakov
2020-10-12 18:15 ` [PR PATCH] [Updated] " ev-ermakov
2020-10-12 23:39 ` ev-ermakov
2020-10-12 23:44 ` ev-ermakov
2020-10-12 23:46 ` [PR PATCH] [Updated] " ev-ermakov
2020-10-12 23:47 ` ev-ermakov
2020-10-13 21:11 ` userabc123xyz
2020-11-19  1:02 ` uzr123x
2020-11-19  1:20 ` fosslinux
2020-11-19  1:20 ` [PR REVIEW] " ericonr
2020-11-19  1:20 ` ericonr
2020-11-19  1:52 ` sgn
2020-12-12 20:36 ` [PR REVIEW] " Piraty
2020-12-12 20:37 ` Piraty
2020-12-14  6:17 ` [PR PATCH] [Updated] " ev-ermakov
2020-12-14  6:17 ` [PR REVIEW] " ev-ermakov
2020-12-14  6:18 ` ev-ermakov
2020-12-14  6:20 ` ev-ermakov
2020-12-14  6:24 ` [PR PATCH] [Updated] " ev-ermakov
2020-12-20 12:38 ` unspecd
2020-12-20 12:39 ` unspecd
2020-12-20 12:40 ` unspecd
2020-12-20 15:07 ` [PR PATCH] [Updated] " unspecd
2020-12-20 15:19 ` unspecd
2020-12-20 15:24 ` unspecd
2020-12-21 14:17 ` [PR REVIEW] " Piraty
2020-12-26 11:18 ` unspecd
2020-12-26 11:28 ` [PR PATCH] [Updated] " unspecd
2020-12-26 13:09 ` unspecd
2020-12-26 15:02 ` [PR PATCH] [Updated] " unspecd
2020-12-26 15:32 ` [PR REVIEW] " unspecd
2021-01-14 19:39 ` [PR PATCH] [Updated] " unspecd
2021-01-18 12:24 ` [PR REVIEW] " Piraty
2021-01-18 12:24 ` Piraty
2021-01-18 12:25 ` Piraty
2021-01-18 12:25 ` Piraty
2021-01-18 14:41 ` unspecd
2021-01-18 14:43 ` unspecd
2021-01-18 14:53 ` [PR PATCH] [Updated] " unspecd
2021-01-18 14:54 ` unspecd
2021-01-18 14:55 ` unspecd
2021-01-18 14:56 ` [PR REVIEW] " unspecd
2021-01-27 14:18 ` Piraty
2021-01-27 17:48 ` [PR PATCH] [Updated] " unspecd
2021-01-27 17:50 ` unspecd
2021-01-27 17:53 ` [PR REVIEW] " unspecd
2021-01-27 18:07 ` unspecd
2021-01-27 19:02 ` unspecd
2021-01-29  8:40 ` [PR PATCH] [Updated] " unspecd
2021-01-29  8:57 ` unspecd
2021-01-29  9:14 ` unspecd
2021-01-29  9:36 ` [help needed] " unspecd
2021-01-29 12:05 ` mvf [this message]
2021-01-29 12:09 ` [PR PATCH] [Updated] " unspecd
2021-01-29 12:15 ` unspecd
2021-01-29 12:42 ` [PR REVIEW] " unspecd
2021-02-24 16:43 ` [PR PATCH] [Updated] " unspecd
2021-03-18 21:00 ` [PR PATCH] [Updated] New package: muse-4.0.0pre3 unspecd
2021-03-19 15:38 ` Piraty
2021-04-22 23:49 ` Usr666x
2021-04-22 23:54 ` Usr666x
2021-04-22 23:57 ` uzr123x
2021-04-24 17:57 ` [PR PATCH] [Updated] " unspecd
2021-04-24 18:00 ` New package: muse-4.0.0 unspecd
2021-04-24 18:03 ` [PR PATCH] [Updated] " unspecd
2021-04-24 18:07 ` [PR REVIEW] " ericonr
2021-04-24 18:07 ` ericonr
2021-04-24 18:07 ` ericonr
2021-04-24 18:24 ` [PR PATCH] [Updated] " unspecd
2021-04-24 18:25 ` [PR REVIEW] " unspecd
2021-04-24 18:29 ` unspecd
2021-04-25  1:01 ` ericonr
2021-04-25  1:01 ` [PR PATCH] [Merged]: " ericonr
2021-04-25  1:10 ` unspecd
2021-05-04  0:55 ` uzr123x

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=20210129120546.rbUZmkFbBmcTs2b18Hvdbes6h0IGFad-mZGJliiJX6A@z \
    --to=mvf@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).