tobi / tobi/try

'brew tap tobi/try' fails

Open
#73 3 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
4k
Forks
159
PR merge metrics
No merged PRs in 30d

Description

This has already been reported and a workaround provided in https://github.com/tobi/try/issues/59 but the actual problem has not been fixed.

A couple solutions:

  1. Rename the repo to homebrew-try in order to be compliant with Homebrew conventions.

  2. Update the README.md to document the correct Homebrew installation,

    brew tap tobi/try https://github.com/tobi/try
    brew install try
    
❯ brew tap tobi/try

==> Auto-updating Homebrew...
Adjust how often this is run with `$HOMEBREW_AUTO_UPDATE_SECS` or disable with
`$HOMEBREW_NO_AUTO_UPDATE=1`. Hide these hints with `$HOMEBREW_NO_ENV_HINTS=1` (see `man brew`).
==> Auto-updated Homebrew!
==> Updated Homebrew from 3b5b4903b0 to c3790fc6e4.
Updated 4 taps (sst/tap, charmbracelet/tap, homebrew/core and homebrew/cask).
==> New Formulae
ctre: Compile-time PCRE-compatible regular expression matcher for C++
==> New Casks
elgato-studio: Capture and manage Elgato devices for content creation
opencode-desktop: AI coding agent desktop client

You have 3 outdated formulae installed.

==> Tapping tobi/try
Cloning into '/opt/homebrew/Library/Taps/tobi/homebrew-try'...
remote: Repository not found.
fatal: repository 'https://github.com/tobi/homebrew-try/' not found
Error: Failure while executing; `git clone https://github.com/tobi/homebrew-try /opt/homebrew/Library/Taps/tobi/homebrew-try --origin=origin --template= --config core.fsmonitor=false` exited with 128.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with README.md and the Homebrew tap command shown in the issue. Check the repository naming and installation instructions against Homebrew’s expected tap layout, then verify that the documented command no longer reports the repository as missing and that the installation steps are complete.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
cli
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.