From: klardotsh <klardotsh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: chamber-2.8.1
Date: Tue, 05 May 2020 22:32:09 +0200 [thread overview]
Message-ID: <20200505203209.mqvmQFpAkIrYr5Gy1Vf2pK0sIirI9O6C33Ou7Mgrle0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21582@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]
New comment by klardotsh on void-packages repository
https://github.com/void-linux/void-packages/pull/21582#issuecomment-624290388
Comment:
Closing this again until I can sort out what on earth the difference is between the packages getting generated with `build_style=go` vs. what I can build with `go get` - the former is *consistently* broken (I had one good build around the time I submitted the package, but it doesn't seem to be reproducible), but the latter works every time.
The way I end up discovering this package is broken is by attempting `chamber exec --pristine` and then finding out that the `--pristine` flag wasn't built in. This seems to be because https://github.com/segmentio/chamber/blob/efa34c951185b60996ac983c838d3304bb7a38e2/cmd/exec.go is being built incorrectly, but I can't for the life of me figure out how or why (I've even tried forcing some `export CGO_ENABLED=0; unset GOOS GOARCH` magic in a local revision of this template, no dice)
If someone else wants to give this a go before I get back around to it, awesome, until then, I've resorted to using the `go get` version for work.
next prev parent reply other threads:[~2020-05-05 20:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 9:25 [PR PATCH] " klardotsh
2020-05-03 9:48 ` [PR PATCH] [Updated] " klardotsh
2020-05-03 9:51 ` klardotsh
2020-05-03 22:00 ` klardotsh
2020-05-04 1:00 ` klardotsh
2020-05-04 1:03 ` klardotsh
2020-05-05 20:32 ` klardotsh [this message]
2020-05-05 20:32 ` [PR PATCH] [Closed]: " klardotsh
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=20200505203209.mqvmQFpAkIrYr5Gy1Vf2pK0sIirI9O6C33Ou7Mgrle0@z \
--to=klardotsh@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).