How do I request a linuxbrew bottle (namely drone-cli) to be built?

It’s not a bug per se, hence cannot report a reproducible bug; reporting it not following “reproducible bug” template (which is only template) gets issue closed immediately.

What do I do?

1 Like

If brew install drone-cli works, open an issue on Homebrew/linuxbrew-core asking to add a bottle for drone-cli. We may or may not tackle the issue depending on our availability and priorities. If brew install drone-cli does not work, open a PR fixing the build for Linux.

Thank you for the swift reply.

It actually works
==> Installing drone-cli
==> Cloning
Cloning into '/home/develop7/.cache/Homebrew/drone-cli--git'...
Note: checking out 'a47e1c3f1bbd296828299e36d95155ca79a39775'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

==> Checking out tag v1.1.4
HEAD is now at a47e1c3 update yaml and runtime library
==> dep ensure -vendor-only
==> go build -ldflags -X main.version=1.1.4 -o /home/linuxbrew/.linuxbrew/Cellar/drone-cli/1.1.4/bin/drone drone/main.go
🍺  /home/linuxbrew/.linuxbrew/Cellar/drone-cli/1.1.4: 5 files, 23.5MB, built in 58 seconds

Do you mind creating a “build a bottle” PR building a bottle for Linux, while we’re at it?

Thank you in advance.

I’ve opened PR

1 Like

That PR has been merged. drone-cli should now be bottled.


Okay, so does it mean

  1. should I run into unbottled formula again I have to ask it to be bottled?
  2. bottles for linux are not built preemptively, only by request?

Once a formula is bottled for Linux, it should remain bottled for Linux. New bottles are by request.

New bottles are by request.

Is the Discourse a blessed way to post such requests, since issues not matching a “reproducible bug report template” are automatically closed (see top message for example)?

Just leave blank template in the issue. Should be fine.