Homebrew-core is a shallow clone error

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account. Today I git pull ed my brew repo, which was a shallow clone of depth around 50, and suddenly it's a full clone. This has been happening in recent weeks, though the clone doesn't always become entirely a full one. I think it might have to do with something I've recently observed. The commits page for brew is now regularly full of a bunch of merge commits by maintainers. This was formerly not the case. The page used to just show the commits, not the commits capped off with a commit declaring a merge.

I don't know why it is now. FWIW, from a user perspective, it makes the formerly enjoyable enterprise of browsing and examining the latest commits into a difficult one.

But then, I don't know much about git, so perhaps these two things are unrelated. The suddenly unshallowed shallow clones thing is irritating, though. If my connection is slow, I don't want to wait for commits from to be pulled in! The text was updated successfully, but these errors were encountered:. Those things are likely unrelated. Is it literally a completely full clone now or just has more commits than you'd expect? I used to, until it began triggering full clones a few months ago. Other times it doesn't become full, but I get way more commits than what has actually been committed since the last update.

Before I went to bed last night I shallowly cloned. Since then, the only things committed to the brew repo are the mergings of PRs 51bdd85 and b2cbe I cd'd to my local clone, did git pulland the entire history got pulled in. And again, between 51bdd85 and d39eeac :. What does git show 29dea6c0eaebda4db46f1acf say? Do you get shown a commit or an error message? That shrunk the size of the.

And yet, the very first HB commit is still lurking in there.Have a question about this project?

Rock groups of the 90s

Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. I have also made sure to get the latest homebrew from github using: from here.

The text was updated successfully, but these errors were encountered:. I noticed that it recurses into the git submodule I have set up for testing, which is a separate issue, but other than that it seems to work. Here's my brew --config - nothing stands out as potentially problem-causing to me, except maybe the different ruby setups we have.

HomeBrew - Error: homebrew-core is a shallow clone.

Doesn't seem like the ruby differences should matter since homebrew always? It does? I just tried uninstalling, killing the cache, manually cloning, and reinstalling here, and it attempts to update the existing clone:. I noticed I'm running git 1. I'll let you know. Everything also "Works for me tm " using fresh clone and manual pre-clone on git 1.

Sorry about the troubles Mine didn't even get that far. But I figured it out. Even though homebrew said: System Ruby: 1. The fix was to search and find the original ruby executable stored in Ruby. Fixed it for me. No worries - glad you figured it out! Feel free to swing back around if you run into any other issues or have feedback or even better!

Thanks man! Still recouping from my last one but the fix is perfect. Keithbsmiley Could you open a separate issue for that last error? I'd be interested in a closer look at it. Done On Tue, Jan 8, at PM, muescha notifications github. For me the issue was the system installed ruby path.Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account. If you have e. Running this command an expensive, one-time operation but if it's run once, manually by humans spread out over a time period it will be a small increase in load which will then drop. If those CI configurations all run this e. Similarly, this motivates configurations that repeatedly setup a shallow clone of homebrew-core to be fixed rather than us automatically "fix" them in a way that's even more expensive.

Can we add an extra comment about brew update potentially running in someone else's CI?

homebrew-core is a shallow clone error

This part clarifies that if we run git fetch --unshallow automatically and someone sets up a shallow clone in their CI, it would lead to a greatly increased load on GitHub's servers, which we don't want. If that can't be done, why not split the difference by wrapping the git As it stands the handling of this is bad on two counts: it makes it sound like the user has done something wring "you made a nasty shallow clone", whatever that is ; and it asks them to drop unto the implementation of Homebrew to fix it.

I've opened to clarify the reasoning in the output message. Skip to content. New issue. Jump to bottom. Copy link Quote reply. GitHub has requested this as these are extremely expensive operations. Copy link. Review period will end on at UTC. BrewTestBot added the waiting for feedback label Dec 2, View changes. Sign in to view.

Price of suzuki jimny 2020 in pakistan

I don't understand this, sorry? I'd rather the more explicit comment for when partial diffs are shown. I was referring to the first sentence in your response: If you have e. MikeMcQuaid Dec 3, Author Member This part clarifies that if we run git fetch --unshallow automatically and someone sets up a shallow clone in their CI, it would lead to a greatly increased load on GitHub's servers, which we don't want.

I think this being documented in the PR is fine for now.

homebrew-core is a shallow clone error

This commit was signed with a verified signature. Review period ended. BrewTestBot removed the waiting for feedback label Dec 3, BrewTestBot approved these changes Dec 3, EricFromCanada mentioned this pull request Dec 4, Cannot brew update or upgrade: Error: homebrew-cask is a shallow clone.

EricFromCanada mentioned this pull request Dec 5, Can't update or upgrade Homebrew This comment was marked as off-topic. Homebrew locked as too heated and limited conversation to collaborators Dec 7, Sign up for free to subscribe to this conversation on GitHub.Ask Different is a question and answer site for power users of Apple hardware and software.

It only takes a minute to sign up. I inadvertently installed it as root and now when attempting to uninstall and reinstall it as the "crmpicco" user is proving fruitless. As you can see from the output below it is always installed as root. Sign up to join this community. The best answers are voted up and rise to the top.

PostgreSQL 9. Asked 1 month ago. Active 1 month ago. Viewed 26 times. How can I install as the current user as it's clear I can't run it as root? We don't do this for you automatically to avoid repeatedly performing an expensive unshallow operation in CI systems which should instead be fixed to not use shallow clones. Sorry for the inconvenience! If you need to have postgresql 9.

Villa carita b&b la morra

HINT: You might need to initdb. The server must be started under an unprivileged user ID to prevent possible system security compromise. See the documentation for more information on how to properly start the server. Improve this question. Active Oldest Votes. The Overflow Blog. A deeper dive into our May security incident. Episode Gaming PCs to heat your home, oceans to cool your data centers. Related 2.Have a question about this project?

Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account.

Needed me lyrics by rihanna

But cleanup are all or none. As an alternative since it's already version 2. As an example. Find the formula from github that represented the version you want and apply it from there Or. I can only speak on behave of my teams OSS and work and this would definitely help. Especially if installing previous version was easier.

The text was updated successfully, but these errors were encountered:.

Subscribe to RSS

Sorry, we won't be implementing this. We've gotten a ton of feedback over the years about how brew cleanup should run automatically in order to save multiple gigabytes of disk space. Back then, most users were completely unaware that they had to run cleanup occasionally to clear out old bottles.

Changing the behavior to opt-in is a clear step back for most users.

homebrew-core is a shallow clone error

If your team is dependent on old versions of Homebrew bottles they should be willing to do a bit more work to accommodate your uncommon use case. There are two things that might help:.

4. DevOps-Containers - Docker Installation on AWS - thanksswf.site4

You can then host this formula in your own tap. The third-party brew installv external commandbut Homebrew does not support this and things could break at any given moment. Great thanks jonchang! That should be added to brew help.

It's listed in man brew though. I was wrong. Skip to content. New issue. Jump to bottom.Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. I find it confusing that the first time you fail because of an shallow clone issue it only tells you about one of the shallow clones.

Ligovsky Avenue, 1j1, Saint Petersburg

Since the second one is very similarly named, for example This is a terrible way to do it, but since I am completely unfamiliar with how brew is constructed it is a straightforward example of the way I think it should work. I don't like empty lines in the output. The following produces a better result suppresses empty lines but I can't say that I'm a big fan of how this code looks so let's see what other maintainers think about it.

I would imagine that So making it look nice when there is only one feels like polishing an edge case.

Subscribe to RSS

But if you want to do it then I've added my way of doing that. Thank you, rgant! Looks great! Thanks so much for your first contribution! Without people like you submitting PRs we couldn't run this project. You rock, rgant! Skip to content. New issue. Jump to bottom.

MikeMcQuaid merged 6 commits into Homebrew : master from unknown repository Dec 14, Check for both shallow clones at the same time. Copy link Quote reply. Have you followed the guidelines in our Contributing document? Have you checked to ensure there aren't other open Pull Requests for the same change? Have you added an explanation of what your changes do and why you'd like us to include them?

Have you written new tests for your changes? Here's an example.

Enterprise resource planning example

Have you successfully run brew style with your changes locally? Have you successfully run brew tests with your changes locally? Have you successfully run brew man locally and committed any changes?

This commit was signed with a verified signature. View changes. If the eariler code produced multiple messages I wouldn't have compla… …. Copy link.Join Stack Overflow to learn, share knowledge, and build your career. Stack Overflow for Teams is a private, secure spot for you and your coworkers to find and share information.

I have modified the git remote address to mirror address of homebrew before. Maybe it's relevant to this but I don't know. As of Oct Homebrew no longer creates shallow clones when being installed, and as of Dec updating existing shallow clones is not allowed either. It is now required to perform the unshallow process by running the git commands above even without a desire for having access to the expanded history that this process provides.

For some details about the motivation for this change, see this discussion on Homebrew's GitHub page, specifically:. Actually, in most cases the warning can be safely ignored, as the formulae being searched for probably isn't available. But if you're really looking for some formulae which might existed in the past, Just do what it suggests:.

This way Homebrew could search for formula that existed only in the past but removed at some point. I would advise against unshallowing the clone because it cramps disk space, makes the lookups slower and enables you only to install obsolete or unmaintaned applications.

There is currently no way to silence this warning. It was proposed in this Github issue but then ignored. Learn more. How to remove the shallow clone warning from HomeBrew Ask Question. Asked 3 years, 5 months ago. Active 4 days ago. Viewed 32k times. Improve this question. Note that as of Dec Homebrew no longer allows shallow clones anyway. GrishaLevit this should probably be the new accepted answer! Active Oldest Votes. This makes the original question about silencing the warning moot.

If a shallow clone is configured, a message containing text like the below will be shown: Error: homebrew-core is a shallow clone. Note: This process may take a long time to complete without providing feedback.

With full clones, GitHub can simply send you all the commits that happened after your last pull, and your local Git client takes care of the rest. Because of [1], it makes it far more likely that GitHub will rate-limit Homebrew operations, which will make it suck for everyone. Improve this answer. Grisha Levit Grisha Levit 6, 1 1 gold badge 32 32 silver badges 47 47 bronze badges.

homebrew-core is a shallow clone error

Thanks for all the details. Can you clarify what exactly is the problem with shallow clones? Shouldn't they be preferred since only the latest version is downloaded? Does this mean that if we don't manually unshallow our homebrew install, that we won't receive updates even when running "brew update"? OliverDixon, wait longer, it's a gigantic repo, it took me minutes to execute this.


thoughts on “Homebrew-core is a shallow clone error

Leave a Reply

Your email address will not be published. Required fields are marked *