From: atweiden <atweiden@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: boost: update to 1.79.0.
Date: Wed, 06 Jul 2022 13:26:28 +0200 [thread overview]
Message-ID: <20220706112628.H2r_elyOzozAs3eq2JzZg_PhQ_O8UVHd-DIo95pLTtU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36204@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 279 bytes --]
New comment by atweiden on void-packages repository
https://github.com/void-linux/void-packages/pull/36204#issuecomment-1176106195
Comment:
> cryfs (fails on `do_build()`)
cryfs builds succeed with [boost-1.79.0](https://github.com/atweiden/voidpkgs/tree/cryfs-boost1.79.0)
next prev parent reply other threads:[~2022-07-06 11:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 14:28 [PR PATCH] boost: update to 1.79.0.b1 JamiKettunen
2022-03-18 14:32 ` [PR REVIEW] " ahesford
2022-03-18 14:32 ` ahesford
2022-03-18 14:37 ` Johnnynator
2022-03-18 14:38 ` [PR PATCH] [Updated] " JamiKettunen
2022-03-18 16:32 ` JamiKettunen
2022-03-18 16:33 ` [PR REVIEW] " JamiKettunen
2022-03-18 16:42 ` [PR PATCH] [Updated] " JamiKettunen
2022-03-18 17:58 ` JamiKettunen
2022-03-18 23:32 ` JamiKettunen
2022-03-18 23:33 ` JamiKettunen
2022-03-19 12:39 ` JamiKettunen
2022-04-08 3:00 ` q66
2022-05-04 15:22 ` loreb
2022-05-26 15:22 ` [PR PATCH] [Updated] " JamiKettunen
2022-05-26 15:29 ` [PR PATCH] [Updated] boost: update to 1.79.0 JamiKettunen
2022-05-26 16:21 ` JamiKettunen
2022-05-26 18:41 ` JamiKettunen
2022-05-26 20:27 ` JamiKettunen
2022-05-26 20:29 ` JamiKettunen
2022-05-27 16:20 ` JamiKettunen
2022-05-27 16:21 ` JamiKettunen
2022-06-08 22:18 ` JamiKettunen
2022-06-08 23:46 ` JamiKettunen
2022-06-08 23:47 ` JamiKettunen
2022-06-09 0:26 ` JamiKettunen
2022-07-06 11:26 ` atweiden [this message]
2022-08-27 3:35 ` classabbyamp
2022-08-27 19:21 ` JamiKettunen
2022-08-27 19:21 ` [PR PATCH] [Closed]: " JamiKettunen
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=20220706112628.H2r_elyOzozAs3eq2JzZg_PhQ_O8UVHd-DIo95pLTtU@z \
--to=atweiden@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).