libtatsu 1.0.4 (new formula)

[tux-mind]

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

[github-actions]

Thanks for contributing to Homebrew! 🎉 It looks like you're having trouble with a CI failure. See our contribution guide for help. You may be most interested in the section on dealing with CI failures. You can find the CI logs in the Checks tab of your pull request.

[tux-mind]

Is it possible to remove the notable repository requirement from the Formulae audit?

* GitHub repository not notable enough (<30 forks, <30 watchers and <75 stars)

The libtatsu repo is from libimobiledevice organization, whose main repo has 1.3k forks, 251 watchers and 6.7k stars ⭐

Thank you in advance for your precious help!

[jpstotz]

The libtatsu repo is from libimobiledevice organization, whose main repo has 1.3k forks, 251 watchers and 6.7k stars ⭐

IMHO this is a bug of homebrew as it does not consider dependencies. libtatsu is a mandatory requirement of libimobiledevice which has 6.7k stars and 1.3k forks. Thus if a popular project requires a dependency the popularity of the dependency should be the cumulated popularity of all projects that depend on it, not just the project itself.

[nikias]

I agree with @jpstotz, also being the maintainer of libimobiledevice (et al.) I feel like this should not prevent the merge of this PR (it is used for personalized developer disk image mounting starting with iOS 17+).
Besides, it is a dependency of idevicerestore too.

[tux-mind]

Thanks @daeho-ro for adding the CI label, all the checks pass!

@chenrui333 can you please review and approve this PR?

Thank you for your help 😊