![]() ![]() Rest assured, your existing pyenv environments that were based on the Python version which went wrong will not get affected, IMO, this is just re-installing the Python interpreter.Īnd that's pretty much it, I thought I should write a blog about this in the hope that it might help others in future so here we are. ![]() Luckily I was able to resolve this issue by re-installing the Python version that caused the problem. To give error: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available. Nice :-(Īnyway, I decided while I am at it, I should probably update a bunch of outdated softwares, starting with pyenv since I use that a LOT: $> brew upgrade pyenv And now pip don't work no more.Īpparently, after upgrading pyenv, it might cause pip (from previous Python installed by old pyenv) zshrc file, and the font and font size are all funny. So yeah, now I have upgraded gedit from 3.22.1 to 3.36.2 and what do I get? The auto-highlighting no longer works for. I wrote something with similar points in a previous blog: MacOS is a darn good system, until it drives you crazy. Because everything was running so smoothly right before I decided to do something stupid and unnecessary. The most significant changes since 3.2.0 are the migration from Homebrew/linuxbrew-core to Homebrew/homebrew-core for all Homebrew on Linux users, the official support of macOS Monterey (and, as usual, dropping the support for Mojave due to us only supporting 3 macOS versions) and the addition of an opt-in HOMEBREWINSTALLFROMAPI flag to avoid. Looks pretty good, let's now finally upgrade gedit! $> brew upgrade geditĪnd it downloaded a massive amount of dependencies of sort and made me wonder if I really need to upgrade gedit in the first place. Today I’d like to announce Homebrew 3.3.0. Here I saw my Homebrew version was 1.3.1! Yikes, that's probably from back in year 2017 or 2018!Īfter installation, my Homebrew version is $> brew -v The installation script will need admin password, then the installation process will start. So better run: $> /bin/bash -c "$(curl -fsSL )" No worries, let's reinstall it, oh by the way, if you run that ruby -e xxxx Homebrew installation command it will give you this warning: Warning: The Ruby Homebrew installer is now deprecated and has been rewritten inīash. That does not make sense since I use the latest version of Xcode and I did not have auto-discover-proxy enabled in network settings!Īfter some Google search, here is what works for me.įirst, run: $> cd "$(brew -repo)" & git fetch & git reset -hard origin/master & brew updateĪfter this, your shell may not be able to find Homebrew: $> brew -v Or like this: error: did not send all necessary objects Update them from Software Update in the App Store. Please update to Xcode 9.0 (or delete it).Įrror: Your Command Line Tools are too outdated. Such as: Error: Your Xcode (1) is too outdated. So, out of nowhere, today I just decided to upgrade gedit!Īnd in the process I decided to update Homebrew as well, cuz why not, what could possibly go wrong ) I never update Homebrew or the softwares installed using Homebrew (or maybe I did update them for a few times, but obviously chances were very close to 'never' since I cannot even remember the last time I used Homebrew!) I used it to install all kinds of softwares, like gedit, pyenv, and so on. I think the only few times I used Homebrew is back in macOS Sierra when I first installed it. MacOS High Sierra to now macOS Mojave, but that's probably because I don't use it that often! So, long story short, I've had no issues with Homebrew since upgrading from macOS Sierra to I also noticed a payload.Updating Homebrew from Sierra age in macOS Mojave merge, Use git merge to apply updates (rather than git rebase). If you are upgrading from another point release of Python 3 (for example, 3.8.10), the installer suggests to install Python 3.9. Click the Download Python button to download the installation file on your computer. I have several zip files in there, is there any reason to have zip files there? I assume I forgot to delete them after unpacking homebrew apps, but I want to make sure. In your browser, visit the Python Releases for Windows section on the official Python website. There is also some confusion with my Wiiu folder as well. I know that almost all of those are from a NAND dump backup and I can safely delete those (Going to make a new NAND backup anyway) but are there any files on the root there that are important? Or no? And I am assuming I can just delete the Haxchi folder once I uninstall Haxchi too right? This is what the root of my SDcard looks like: Can anyone please give me some advice on that? ![]() I assume several of these are related to Haxchi or older now outdated hacks, but I am not sure which and which ones I should or should not remove. I was looking over my SD card, and there are a lot of files on there over the years. I see, so I just simply uninstall Haxchi as if it was any other official app through the WiiU's uninstall option, thanks. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |