From: Luciogi <Luciogi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] New package: Cockatrice-2.9.0
Date: Sat, 09 Dec 2023 20:10:52 +0100 [thread overview]
Message-ID: <20231209191052.Lhgsgb_K6nuWujvIXrqu2S8t1Fbf817G8VG1izC5-qA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47313@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 306 bytes --]
New comment by Luciogi on void-packages repository
https://github.com/void-linux/void-packages/pull/47313#issuecomment-1848617962
Comment:
as protobuf25 old package (which is deprecated) works, my guess is that current package `protobuf` has different build option which is causing abnormal linking here
next prev parent reply other threads:[~2023-12-09 19:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-19 18:33 [PR PATCH] [WIP] New pacakge: Cockatrice-2.9.0 jason1987d
2023-11-19 18:41 ` [PR PATCH] [Updated] " jason1987d
2023-11-24 2:10 ` jason1987d
2023-11-30 9:49 ` robertek
2023-11-30 21:20 ` jason1987d
2023-12-06 8:41 ` [WIP] New package: Cockatrice-2.9.0 robertek
2023-12-08 15:37 ` jason1987d
2023-12-08 15:39 ` jason1987d
2023-12-08 15:40 ` jason1987d
2023-12-08 15:45 ` jason1987d
2023-12-08 15:47 ` jason1987d
2023-12-08 15:53 ` jason1987d
2023-12-08 16:03 ` [PR PATCH] [Updated] " jason1987d
2023-12-08 16:05 ` jason1987d
2023-12-08 16:06 ` jason1987d
2023-12-08 16:33 ` jason1987d
2023-12-08 19:08 ` [PR PATCH] [Updated] " jason1987d
2023-12-08 19:08 ` jason1987d
2023-12-08 20:14 ` jason1987d
2023-12-08 20:15 ` jason1987d
2023-12-08 20:15 ` jason1987d
2023-12-08 20:23 ` [PR REVIEW] " Luciogi
2023-12-09 3:14 ` jason1987d
2023-12-09 3:16 ` jason1987d
2023-12-09 5:50 ` Luciogi
2023-12-09 19:10 ` Luciogi [this message]
2024-01-18 16:01 ` [PR PATCH] [Closed]: " jason1987d
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=20231209191052.Lhgsgb_K6nuWujvIXrqu2S8t1Fbf817G8VG1izC5-qA@z \
--to=luciogi@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).