From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: qt5-core missing causing xbps to fail
Date: Tue, 18 Jan 2022 17:18:11 +0100 [thread overview]
Message-ID: <20220118161811.i9ND48te_HIDSX1lCoIGyaxDMgOM9NQ8ga1WwFPPNKg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35112@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 357 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/35112#issuecomment-1015572102
Comment:
There is a big rebuild going on, including `qt5` of which `qt5-core` is a subpackage of.
Even if it might already be build, the repository is still incomplete and staged until all dependencies of icu are rebuild.
next prev parent reply other threads:[~2022-01-18 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 16:05 [ISSUE] " Vistaus
2022-01-18 16:17 ` [ISSUE] [CLOSED] " Duncaen
2022-01-18 16:17 ` Duncaen
2022-01-18 16:18 ` Duncaen [this message]
2022-01-18 16:27 ` Vistaus
2022-01-18 16:27 ` Vistaus
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=20220118161811.i9ND48te_HIDSX1lCoIGyaxDMgOM9NQ8ga1WwFPPNKg@z \
--to=duncaen@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).