Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask question.(5)

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

ITtutoria

ITtutoria Logo ITtutoria Logo

ITtutoria Navigation

  • Python
  • Java
  • Reactjs
  • JavaScript
  • R
  • PySpark
  • MYSQL
  • Pandas
  • QA
  • C++
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Python
  • Science
  • Java
  • JavaScript
  • Reactjs
  • Nodejs
  • Tools
  • QA
Home/ Questions/How do I remove the shallow clone warning from homebrew?
Next
Answered
Louis Faivre
  • 21
Louis Faivre
Asked: May 17, 20222022-05-17T12:56:59+00:00 2022-05-17T12:56:59+00:00In: git

How do I remove the shallow clone warning from homebrew?

  • 21

. Advertisement .

..3..

. Advertisement .

..4..

How to remove the shallow clone warning from HomeBrew? I get the following error message:

➜ ~ brew info test 
 Error: No available formula with the name "test" 
 ==> Searching for a previously deleted formula...
 Warning: homebrew/core is shallow clone. To get complete history run:
  git -C "$(brew --repo homebrew/core)" fetch --unshallow
 
 Error: No previously deleted formula found.

When I try to change the remote git address to mirror homebrew homebrew prior to. Can someone give me some good tips?

homebrew-core is a shallow clone
  • 2 2 Answers
  • 124 Views
  • 0 Followers
  • 0
Answer
Share
  • Facebook
  • Report

2 Answers

  • Voted
  • Oldest
  • Recent
  • Random
  1. Best Answer
    dttutoria Expert
    2022-06-04T16:57:53+00:00Added an answer on June 4, 2022 at 4:57 pm

    The cause: Because Homebrew no longer makes shallow clones when installed, and from December 2020, upgrading existing shallow clones is not permitted.

    Perhaps the issue is related to changing the git remote address to the homebrew mirror location previously.

    Solution:

    In most situations, the warning can be safely ignored because the formulae being sought are unlikely to exist.

    However, if you’re seeking certain formulae that may have existed in the past, simply follow the instructions.

    Run the following commands to acquire a complete history:

    git -C "$(brew --repo homebrew/core)" fetch --unshallow
    • 9
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report
  2. Arthur Roussel
    2022-05-26T03:56:07+00:00Added an answer on May 26, 2022 at 3:56 am

    Homebrew has stopped creating shallow copies when it is installed. Additionally, updating shallow clones that are already in use is now.

    This makes it moot to ask about silencing the warning.

    A message with text such as the following will be displayed if a shallow clone has been configured

    Error:
     homebrew-core is a shallow clone.
     homebrew-cask is a shallow clone.
    To `brew update`, first run:
     git -C /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core fetch --unshallow
     git -C /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask fetch --unshallow

    It is now necessary to execute the unshallow process. To do this, run the git command(s), as shown in the error message.

    Notification: If feedback is not provided, this process can take quite a while to complete.

    You can find more information about this change in the discussion on Homebrew’s GitHub page.

    Two major drawbacks to shallow cloning are:

    1. This creates a huge computational burden for GitHub’s servers. They must dynamically calculate a new delta between what you have and the most recent commit, on each brew update. With full clones, GitHub will simply send you the commits that occurred after your last pull. Your local Git client takes care the rest.
    2. It is much more likely that GitHub will limit Homebrew operations because of [1]. This will make it sucky for everyone.

    –gromgit December 5, 2020, 12:29 PM EST

    Also, this additional text was added to error message:

    This restriction has been made on GitHub’s request because updating shallow
    clones is an extremely expensive operation due to the tree layout and traffic of
    Homebrew/homebrew-core and Homebrew/homebrew-cask.

    • 5
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

Sidebar

Ask A Question
  • How to Split String by space in C++
  • How To Convert A Pandas DataFrame Column To A List
  • How to Replace Multiple Characters in A String in Python?
  • How To Remove Special Characters From String Python

Explore

  • Home
  • Tutorial

Footer

ITtutoria

ITtutoria

This website is user friendly and will facilitate transferring knowledge. It would be useful for a self-initiated learning process.

@ ITTutoria Co Ltd.

Tutorial

  • Home
  • Python
  • Science
  • Java
  • JavaScript
  • Reactjs
  • Nodejs
  • Tools
  • QA

Legal Stuff

  • About Us
  • Terms of Use
  • Privacy Policy
  • Contact Us

DMCA.com Protection Status

Help

  • Knowledge Base
  • Support

Follow

© 2022 Ittutoria. All Rights Reserved.

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.