From: linkert <linkert@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: On update I get: "MISSING: tbb>=2021.5.0_1"
Date: Sat, 29 Jan 2022 06:58:04 +0100 [thread overview]
Message-ID: <20220129055804.AniOhb5JyfuloapXPordpPOH6l9HEL3UV0lwdsVFIWA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35277@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 363 bytes --]
New comment by linkert on void-packages repository
https://github.com/void-linux/void-packages/issues/35277#issuecomment-1024843272
Comment:
> A broken merge of the tbb update had to be reverted which also accidentally unstaged the repository, packages are still being rebuild to resolve that. https://build.voidlinux.org/waterfall
Thanks, works fine now :)
prev parent reply other threads:[~2022-01-29 5:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 18:31 [ISSUE] " linkert
2022-01-28 19:16 ` Duncaen
2022-01-29 5:58 ` [ISSUE] [CLOSED] " linkert
2022-01-29 5:58 ` linkert [this message]
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=20220129055804.AniOhb5JyfuloapXPordpPOH6l9HEL3UV0lwdsVFIWA@z \
--to=linkert@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).