Post install fails for shared-mime-info on mojave #38213
Labels
outdated
PR was locked due to age
Comments
|
I've got the same issue. |
|
poke @tschoonj |
|
Also occurs on High Sierra. In my case, it's a dependency for Imagemagick. #38219 says this might be temporary, but I don't really know. |
|
@chrisfinazzo The bintray issue would only cause a 404, not a symlink error. I doubt that is the issue. |
|
This was the issue for me: Looks like it's libheif issue. I guess b3ea3ae should've fixed it, but it didn't work for me. (FYI this problem has occurred when I've ran brew upgrade) |
|
Oh and ofc: |
|
@stek29 Thanks for posting that, it worked for me as well, though strangely didn't give the same error: I have the following versions installed on macOS 10.14.3: |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
|
Getting the same issue as @stek29 on High Sierra version 10.13.6 (17G5019). titan:~$ brew postinstall shared-mime-info
==> Postinstalling shared-mime-info
Warning: The post-install step did not complete successfully
You can try again using `brew postinstall shared-mime-info`
titan:~$ ls -ld /usr/local/share/mime
lrwxr-xr-x 1 thomascapote admin 34 Apr 14 13:18 /usr/local/share/mime -> ../Cellar/libheif/1.4.0/share/mime
titan:~$ brew unlink libheif
Unlinking /usr/local/Cellar/libheif/1.4.0... 12 symlinks removed
titan:~$ brew postinstall shared-mime-info
==> Postinstalling shared-mime-info
==> /usr/local/Cellar/shared-mime-info/1.12/bin/update-mime-database /usr/local/
titan:~$ brew link libheif
Linking /usr/local/Cellar/libheif/1.4.0...
Error: Could not symlink share/mime/XMLnamespaces
Target /usr/local/share/mime/XMLnamespaces
already exists. You may want to remove it:
rm '/usr/local/share/mime/XMLnamespaces'
To force the link and overwrite all conflicting files:
brew link --overwrite libheif
To list all files that would be deleted:
brew link --overwrite --dry-run libheifResult of titan:~$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!
Warning: You have the following deprecated, official taps tapped:
Homebrew/homebrew-fuse
Untap them with `brew untap`.
Warning: Unbrewed dylibs were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.
Unexpected dylibs:
/usr/local/lib/libnnz11.dylib
/usr/local/lib/libociei.dylib
/usr/local/lib/libocijdbc11.dylib
Warning: You have unlinked kegs in your Cellar.
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
libheif
titan:~$ |
|
in homebrew-kde/kde tap, i make a patch for any package generate the mimeinfo when run "make install" for avoid the creation the file for example: https://github.com/KDE-mac/homebrew-kde/blob/30a57ba1e2a197c417091a7c428cc3e27b78e351/Formula/kf5-kcoreaddons.rb edit: i've update it for more sane method instead off patch, but the fix is the same |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
|
I just ran into this issue on macOS Mojave 10.4.5: Here's the output from Manually running the post-install step doesn't appear to work: Here's the same command with more verbose output: |
|
This is the issue I'm having on mojave. Is |
|
Any updates on this? |
|
Has this issue been fixed? |
|
This is also blocking #42845. |
|
This is also blocking #43986. |
|
Just ran into this issue again with version 1.14 on Mojave: Here's the output from |
|
Same issue here, Mojave 10.14.6: Running That is odd. Looking more closely: The file Can the package maintenainers look into this? |
|
@stek29 @Say-XKCD and @thomascapote are right. I didn't read properly this issue.
The postinstall step of shared-mime-info creates a symlink at The content of /usr/local/share/mime seems better, even though we have the leftover mime link. But, I still have no clue which one is right and it is definitely not normal that both package symlink into the same location. |
|
I'm not going to rehash everything above, but is this a problem with shared-mime-info, or libheif? Agree with @pgrenaud that the symlink seems odd. |
|
I think the problem is shared-mime-info iself when is executed under the make install or cmake install process under the homebrew sandbox. I fix those errors in the KDE tap by editing the cmakefile scripts (all kde project is cmake based) avoiding the execution of shared-mime-info and do run it in the post-install function |
|
Just ran into this issue again with version 1.15 on Mojave: Here's the output from |
|
If you're seeing this issue in a reproducible fashion, can you try to apply #46307 and report whether it fixes your issue? |
|
This should be fixed |
|
Nice! ✨ Unfortunately, I just ran |
|
Can you post the debug output from |
|
Hmm…maybe. Here's the debug output: It looks like the error is now occurring with |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I ran
brew updateandbrew upgrade, and while the upgrade was running the shared mime-info package showed the following:I tried the command as suggested and got the same result. The other packages installed successfully, so I believe this is an issue with the shared-mime-info code in particular.
I tried removing the downloaded packages (from ~/Library/Caches/Homebrew/downloads/) and running
brew cleanupthen repeated my update and upgrade commands, however still get this error.The following is the output from
brew doctorI have not removed them because it looks like those might be for my sound card, and I get a warning about permissions when I try (and I don't want to break anything). Below is the output from
brew gist-logsI am able to reproduce this by running
brew reinstall shared-mime-infoThe text was updated successfully, but these errors were encountered: