How to solve 'macOS Package Authoring Error' - macos

I'm trying to install a new version of macOS. The only option I have is mojave. Despite that , when I click continue (the very first step in the installation wizard) it takes some time and says "the request to recovery server timed out".
Using a macbook pro 13inch, 2018 built.
The log says, Package Authoring Error,
access to path " /tmp/com.apple.pkg.testing" requires
and similar errors.
I do have a proper, uninterrupted Internet connection.
How to solve it?

Mac comes with a bunch of options, install new macos, update the current os, reinstall the os that came with the laptop. My solution was this,
shift+options+cmd+r on boot and it will reinstall the mac os that came along with the laptop.
Source : apple support

Related

How to uninstall the GlobalProtect App from Macbook?

Recently I have install GlobalProtect vpn on my Macbook and found it very difficult to uninstall it since it was opening on startup. Is there any specific way to do it ?
I have seen over the web that a lot of Apple Macbook users struggle with this, therefor I have decided to create a guide that shows two options on how to unistall the GLobalProtect App on macOS.
You need to download the initial GlobalProtect Installer, as you go through the steps shows an option for uninstall
Copy and paste the following code on the terminal window
sudo
/Applications/GlobalProtect.app/Contents/Resources/uninstall_gp.sh
You can find more here

Glassfish v4.0 cannot work on Mac OSX 10.6.8 + JDK 7.0 U40

I had been using 2010 Macbook Pro for a while and had updated the Mac OSX to the latest version, and I had been suffering the slow speed for a long time. So last night I googled and do some cleanup , such as fix disk permissions, but the Mac was still slow. And someone suggest to re-install MacOSX.
I was thinking it was the new version of Mac OSX's problem, I had the same kind of problems happen on the 1st version IPad either.
After I reinstalled, the computer became much more faster. But I encountered the following problems:
JDK 7 DMG does not support OSX 10.6.8, but ONLY OSX 10.7+
Github official client does not support OSX 10.7+
Gooooooogled again and again, to solve the 1st problem, there are mainly to suggestions:
A. Using PackageMaker to remove the OSX version condition.
B. Using a tool Pacifist to open the pkg file inside the DMG file downloaded from official.
Since I have PackageMaker installed on Mac OSX, so I choosed A.
Open it with PackageMaker, remove the limitation, and build it again, I installed with the new pkg file successfully at:
/Library/Java/JavaVirtualMachines/jdk1.7.0_40.jdk/Contents/Home
And then set JAVA_HOME on ~/.bash_profile.
Then I download the glassfish 4.0 multi-language version, unzipped, and start-domain successfully. and finally the problem killed me for now.
After glassfish v4 started, I try to login into web console at:
http://localhost:4848
then glassfish server instance "dies", the java process of glassfish is still there, but without any response, the web console starting icon keeps rolling all the time. And there are no error logs created, and the "generated" directory is not generated.
2013-10-15 14:05:20.928 java[797:903] * NSInvocation: warning: object 0x1083c8390 of class 'ThreadUtilities' does not implement methodSignatureForSelector: -- trouble ahead
2013-10-15 14:05:20.930 java[797:903] * NSInvocation: warning: object 0x1083c8390 of class 'ThreadUtilities' does not implement doesNotRecognizeSelector: -- abort
Command start-domain failed.
That is the 1st problem.
The 2nd problem is about github. Since github official does not support OSX 10.6.8, I found an old installer with version 1.0.3. I installed this version, with one ONLY problem for now, I cannot login into github with username and password,no error responses, just no responding, I suffered this once I was on Windows. But I can work with clicking the "Clone into Desktop" button on github.com.
Can someone help me out? I am working on JDK7 based projects.
Why everybody is leaving Snow Leopard, and does not support it anymore, but old Mac computers should be die without working software after 2~3 years, just 2~3 years. And OS upgrade to nex t level will DOWNGrade the performance. Why this things happen?
Is it the oracle from god?
I had the same error (NSInvocation...), on my 2006 Macbook Pro (OS X 10.6.8), onto which I had installed JDK7 to develop a Java/GWT application in Eclipse Kepler. After searching around, I learned that one possible solution was to downgrade to JDK 1.7.0u25 (instead of update 40 or higher), so I installed that version alongside 1.7.0u45 (which I already had), and that fixed the problem. So I would recommend installing that version of the JDK and see if that fixes your problem.

../include/wx/mac/carbon/private.h:1459: error: ‘Cursor’ does not name a type

I have been using RapidSVN on a Linux machine for the past few years - it has become an excellent tool for managing my source.
Yesterday my trusty Linux laptop had a couple of strokes so I decided it was time to replace it. Today I went out and purchased a new Mac Book Pro with the flashy display and solid state drives.
Then I went hunting for an SVN tool to run on Mac. I found that RapidSVN will run on a Mac as it was developed using wxWidgets (cross platform windowing).
So, I needed to install wxWidgets, however this doesn't come as an executable so I had to download the tar ball. To compile I realised I don't have a compiler installed yet... so, install Xcode 4.4, then learn that doesn't install a compiler either... find the Xcode preference to install the command line tools (compiler).
So, now I have Xcode installed, a gcc compiler, and tracking back up it comes to wxWidgets. It takes a little working out but I manage to extract the files into a directory in my home folder, (following instructions of course), and from the 'build' folder I run the ../configure command (which seems to work) and then the 'make' command which fails:
In file included from ../include/wx/mac/private.h:4,
from ../src/common/dynlib.cpp:48:
../include/wx/mac/carbon/private.h:1459: error: ‘Cursor’ does not name a type
../include/wx/mac/carbon/private.h:1488: error: ‘ClassicCursor’ does not name a type
make: *** [baselib_dynlib.o] Error 1
So I go hunting for a solution only to find this bug: http://trac.wxwidgets.org/ticket/14536 which unfortunately indicates this is not going to be fixed.
Changed 10 months ago by csomor
* status changed from new to closed
* resolution set to wontfix
A dismal day in the land of computers. I am now stuck for the next 5-6 years on a computer that will never be able to compile anything using wxWidgets - I rather feel like taking it back to Apple and getting my money back.
So where to from here? Is there a binary version of wxWidgets available? Is there a binary version of RapidSVN available? Should I downgrade to OSX 10.x something less than I am currently on? Should I upgrade to unstable wxWidgets?
This is an interesting but not very understandable read. What exactly are you trying to achieve? If you're looking to use the best available version of wxWidgets under OS X, get 2.9.4 or the current svn version and build it using the Xcode version you have already with Cocoa support. If you absolutely need to continue to use Carbon (why?), either install Xcode 3, available from Apple, or get 10.6 (or 10.5) SDK in some other way and pass it as the SDK to use to configure using --with-macosx-sdk option as explained in the documentation.
VZ is right. If you need to use wxWidgets 2.8 on OS X (and there are legitimate reasons for needing to do so), get the 10.6 SDK. Copy it alongside the already installed 10.7 and/or 10.8 , and select it in the project/target's build settings.
From here I have given up trying to compile anything on my current OSX. I am not going to downgrade or install multiple versions of different libraries in order to satisfy the lack of support for the latest current stable versions.
From here I will download and install binaries only.
I have Mac OSX Lion and just did this:
brew install wxmac
and was able to get through the install with no issues.

xcode 3.2.3 installation failed on Mac 10.6.3

First I have install Mac 10.6.3 on my system now I want to install xcode 3.2.3 .But I get error as "An unknown installation error occured. The installer encountered an error that caused installation to failed."
Please Help me with this issue.
change your system date to 1/1/2012.
then try to install... it works for me
Look at this thread:
Either make a new Admin user & try that account, or Software Update...
It seems the error stems from an expired certificate covering the iOS portion of the package. I assume you only need 3.2.6 to build universal binaries that support older PPC as well as Intel Macs right? That being the case, you can simply decline the second licence agreement covering iOS. The installer should then proceed to install only the Mac-related tools and SDKs.
Update: I see you were referring to 3.2.3 while I was referring to 3.2.6. I am not certain the installer works the same way, but imagine you would want 3.2.6 anyway?

Xcode failed to install

I am trying to install Xcode 4.2 on my Mac system having OS version 10.6.8.
Actually, I removed the Xcode from the system and tried to reinstall it.
I quit iTunes before installing it, and I have enough free space on disc (111 GB). Below is a screenshot of the error. What should I do?
Set your system time to 1st January 2012 or earlier (but not too early), as the certificate that signed the package has expired.
I had the same error message. In my case, it was solved by updating the OS software. There was an update waiting for "Apple installations software". After the update, Xcode installed perfectly well.
I found out I could download the installer directly from Apple instead of through the app store, and that the error described by the accepted answer could also be circumvented by installing the Mobile Development Framework manually.
See forum post Problems installing Xcode on Lion for more details.
I had the same trouble on Mac OS 10.8.5 when installing Xcode 4.4.1, Xcode 5.1.1, and Security_Update_2014-005. It turned out that the reason was the same in all these cases: an incompatibility with Vodafone/Huawei UMTS drivers. A workaround in this case is to temporarily move them away, e.g.
mv /System/Library/Extensions/{HuaweiDataCardDriver.kext,Vodafone.kext,VodafoneFilter.kext} ~
Then do the installation/update, and then restore those drivers, e.g.,
mv ~/{HuaweiDataCardDriver.kext,Vodafone.kext,VodafoneFilter.kext} /System/Library/Extensions/

Resources