-
-
Notifications
You must be signed in to change notification settings - Fork 9.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/usr/local/Homebrew migration tracking issue #987
Comments
I am getting
Don't know if this is relevant for this issue. I was recently updating brew which went fine, afterwards I got the git error message above while running |
Thanks, that helps. Actually my tap at https://github.com/flokru/homebrew-self is empty. I don't know when and why it got in there (nor what I was trying to accomplish while foolishly adding it in the past). Not tapping it after untapping helps. Sorry for the noise. |
Edit: It's fixed with Hello, I'm not really a super literate brew user so I'm not sure how to address this but I think this is a similar error. It seems that
|
@Cynlic Run |
Posting this (new) error message here, for general awareness:
The list of installed Homebrew packages at the time of the error isn't large:
Things still seem to be working. eg The error message itself though is kind of concerning. 😉 |
Getting this problem also on the build of PR Homebrew/homebrew-core#4945, sierra passed, elcapitan and yosemite failed with same problem: [el_capitan] $ /bin/sh -xe /var/folders/03/jqjv4qms2b18_hwt2dcgsghc0000gp/T/hudson8974165171645172947.sh
+ env
+ grep JENKINS
+ grep -iv cookie
JENKINS_HOME=/Users/brew/Jenkins
JENKINS_URL=https://bot.brew.sh/
+ GIT_WORK_TREE=/usr/local
+ GIT_DIR=/usr/local/.git
+ git reset --hard origin/master
HEAD is now at 59b7f16 Merge pull request #989 from MikeMcQuaid/rubocop-final
+ brew update
Updated Homebrew from 59b7f16 to e204679.
No changes to formulae.
==> Migrating HOMEBREW_REPOSITORY (please wait)...
Error: No such file or directory - (../Homebrew/bin/brew, /usr/local/bin/brew)
Failed to migrate HOMEBREW_REPOSITORY to /usr/local/Homebrew!
Please comment with your (new) error in issue:
https://github.com/Homebrew/brew/issues/987
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:349:in `symlink'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:349:in `block in ln_s'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:1574:in `fu_each_src_dest0'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:347:in `ln_s'
/usr/local/Library/Homebrew/cmd/update-report.rb:260:in `migrate_legacy_repository_if_necessary'
/usr/local/Library/Homebrew/cmd/update-report.rb:103:in `update_report'
/usr/local/Library/Homebrew/brew.rb:99:in `<main>'
Build step 'Execute shell' marked build as failure
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
Archiving artifacts
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 7 second
[WS-CLEANUP] Deleting project workspace...[WS-CLEANUP] done
Finished: FAILURE |
@rodrigues You can ignore that, it's been addressed, thanks. |
@justinclift You need to resolve the Git conflicts/merges in your repository. |
@MikeMcQuaid You mean nuke my local branches? |
@MikeMcQuaid I'm trying to figure out what the conflicts/merges are about.
It's still complaining with the same error message. Any idea how to figure out what the problems it's complaining about are? |
@justinclift Actually, I may have a fix. Coming right up... |
Cool. 😄 |
@justinclift Try to |
Thanks @MikeMcQuaid, that worked. 😄 |
|
|
I just got the following (error on last line) after being migrated while trying to upgrade a formula:
Is this just because the formula upgrade is trying to find
Thanks Edit: Same as @viktorbenei it seems. |
Probably, rough edge I guess. Do you have any problem afterwards? EDIT: I missed the "Same command works fine now." part, sorry. |
TL;DR; for my and @MatzFan 's issue: |
This is mainly an issue in CI environment btw |
I believe this is an issue of |
correct @zmwangx |
No issues @zmwangx . As per @viktorbenei's comment, seems any arg passed during |
@MatzFan Yeah, just as you said it was trying to find |
Working on a fix to the auto-update issue. |
@MikeMcQuaid but and my packages? i lose? |
@unluisco Your packages are in |
This is my error:
Later on when I type Please help! |
@antruongnguyen |
Another error, and fix:
Fix:
|
And yet another:
Fix:
|
@hmijail If you know how to fix these issues you don't need to post them here. |
Sorry, was looking for the fixes here and then I realized the easy fix seemed to work OK. So I wrote them in case it helped someone else, or could get documented. |
When running
I removed the lock file and ran
Now when I run again it just says |
I needed to run |
|
@malopezcruz |
samair11:~ sam$ brew update |
@spullara Do that or ask a more specific question if you're unsure, thanks. |
I'm an infrequent brew user. For whatever reason today I ran a brew doctor which told me to do a brew update. I did so, with this result:
Now any brew command I try yields this message:
I decided to try re-installing, but that didn't help:
Any ideas on how to proceed would be helpful. Thanks. |
@machale Run https://github.com/homebrew/install#uninstall-homebrew and try to install again. Sorry for the inconvenience. |
Installing homebrew to a new machine with
and tried to uninstall and install it again as @MikeMcQuaid said, but got no success, any idea? |
@yeahdongcn Apologies, this was a regression that's now fixed in Homebrew/install#74. Please try again. |
@MikeMcQuaid Thanks, uninstalling cleaned things up. The uninstall process deleted everything under /usr/local/Cellar/ but luckily I saved a list of what I had in there before uninstalling, so I know what to go and reinstall. After a fresh install of brew 1.0.7, I was able to do a quick The uninstall process does not appear to have touched the one Cask I had and Thank you so much for your contribution to this amazing facility! |
Glad to be of help. |
After I run brew update, I get an error Then I run brew doctor, I get It seems that after the brew update fails, the system cannot locate homegrew |
@ofWay I'd recommend running the Homebrew installer again. |
I'm planning on following the advice above and just re-installing. But thought this info may be helpful. FWIW this is the output of the original update attempt.
|
Hey Mike - appreciate any direction you can provide. I am running sierra and uninstalled an old version of home brew beccause I was having some probs. Try to re-install it and get the following: Error: Another active Homebrew process is already in progress. I saw a similar error in another post but wasnt able to grok how to make it work. Many thanks |
@nuhuxi are there files in /usr/local/var/homebrew/locks? If so, removing them will make that message go away. You may want to make sure it's not telling the truth by rebooting first or checking |
@ilovezfs Thanks for the post. grep'd brew and saw nothing. Also no files in /usr/local/var/homebrew/locks. Tried to install again - no go. Here is the entire message: ==> Downloading and installing Homebrew... Error: Another active Homebrew process is already in progress. Please wait for it to finish or terminate it to continue. Failed during: /usr/local/bin/brew update --force |
@ilovezfs It installed. It may have been absolute brute force but it worked. I went into /usr/local/var and rm's homebrew. Installed no problem. Thanks for your help - truly appreciated. |
Hi, I didn't read through the full thread, but a simple search did not find anything relating to the error I encountered:
Basically
I just moved all stuff under
Hope it helps someone. |
If you were directed to report your errors here by
brew update
please post a comment if your error is different to a previously mentioned comment and otherwise "Subscribe" to this issue rather than posting 👍 or "me too" etc.Thanks and sorry for the inconvenience.
The text was updated successfully, but these errors were encountered: