Troubleshooting on Shafiq Alibhai

Fix casks with `depends_on` that reference pre-Mavericks

Mon, 18 May 2020 10:01:16 +0000

If you get an error of the type Error: Cask 'hex-fiend-beta' definition is invalid: invalid 'depends_on macos' value: ":lion", where hex-fiend-beta can be any cask name, and :lion any macOS release name, run the following command:

/usr/bin/find "$(brew --prefix)/Caskroom/"*'/.metadata' -type f -name '*.rb' -print0 | /usr/bin/xargs -0 /usr/bin/perl -i -pe 's/depends_on macos: \[.*?\]//gsm;s/depends_on macos: .*//g'

This will remove all depends_on macos references of installed casks.

Decoding the Error: StatusCode=0 "ReferencedResourceNotProvisioned" in Azure

Sat, 22 Dec 2018 09:38:39 +0000

Introduction#

If you’re working with Azure, you might have encountered an error that looks something like this:

“Failure sending request: StatusCode=0 — Original Error: Code=‘ReferencedResourceNotProvisioned’ Message=‘Cannot proceed with operation because resource used by resource is not in Succeeded state. Resource is in Updating state and the last operation that updated/is updating the resource is PutSubnetOperation.’”

Though the error message can seem intimidating and cryptic at first, don’t worry. In this post, we’ll delve into what this error means and how you can resolve it.

How to Fix the "RPC failed; HTTP 413 curl 22" Error in Nginx

Fri, 12 Oct 2018 09:49:17 +0000

Understanding the Issue: ‘RPC failed; HTTP 413 curl 22’#

If you’ve stumbled upon the error message “RPC failed; HTTP 413 curl 22 The requested URL returned error: 413 Request Entity Too Large,” you’re probably trying to push a rather hefty commit over HTTP to your server running Nginx. This error means that the size of the request you’re trying to send exceeds the limit that the server is willing to accept. So, how do you fix it?

scripts/extract-cert.c:21:10: fatal error: openssl/bio.h: No such file or directory

Wed, 19 Sep 2018 15:44:02 +0000

sudo apt-get install -y libssl-dev

/bin/sh: 1: bison: not found

Wed, 19 Sep 2018 15:33:07 +0000

sudo apt-get install bison

/bin/sh: 1: flex: not found

Wed, 19 Sep 2018 15:32:11 +0000

sudo apt-get install flex

[solved] xcrun: error: active developer path ("/Applications/Xcode.app/Contents/Developer") does not exist

Thu, 06 Sep 2018 09:43:25 +0000

Error:

xcrun: error: active developer path ("/Applications/Xcode.app/Contents/Developer") does not exist
Use sudo xcode-select --switch path/to/Xcode.app to specify the Xcode that you wish to use for command line developer tools, or use xcode-select --install to install the standalone command line developer tools.
See man xcode-select for more details.
xcrun: error: active developer path ("/Applications/Xcode.app/Contents/Developer") does not exist
Use sudo xcode-select --switch path/to/Xcode.app to specify the Xcode that you wish to use for command line developer tools, or use xcode-select --install to install the standalone command line developer tools.
See man xcode-select for more details.

Merging Unrelated Git Histories - A Simple Guide

Tue, 04 Sep 2018 13:48:55 +0000

Are you stuck with two Git repositories or branches that have completely different histories, but you need to merge them? You may be hitting a roadblock because Git is designed to prevent this kind of operation by default. However, there’s a workaround for this, and it’s simpler than you might think.

The Problem: Unrelated Git Histories#

Imagine you’re working on a project where you have a main branch, and someone else has a completely separate project with its own history. Now, you want to combine both projects into a single repository. If you try to perform a regular git merge or git rebase, Git will likely stop you with an error message, something like:

Puppet Error – Could not file class in namespace – [solved]

Tue, 18 Jan 2011 07:03:39 +0000

How to Solve the Puppet Error: Could not find class in namespace#

Sometimes, when working with Puppet, you may encounter an error message that does not accurately reflect the actual problem. For example, if you see this error:

err: Could not retrieve catalogue: Could not find class php in namespaces standardbuild at /etc/puppet/manifests/templates.pp:15 on domain.internal.com

One of the possible causes could be a missing curly bracket in your code. This can be hard to spot and can waste a lot of your time. To avoid this, make sure you check your syntax carefully and use a code editor that can highlight any errors for you.

ERROR: phpize failed [solved]

Mon, 17 Jan 2011 06:51:05 +0000

How to install PHP development files

If you want to run phpize on your system, you need to install the development files of PHP first. Otherwise, you might get an error message like this:

sh: phpize: not found
ERROR: `phpize' failed

To install the PHP development files on Ubuntu/Debian, you can use the following command in the terminal:

apt-get install php5-dev

That should solve the problem. 🙂