createOSXinstallPkg | Tools for packaging OS X installers | DevOps library

by munki Python Version: Current License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(10)Vulnerabilities Install Support

kandi X-RAY | createOSXinstallPkg Summary

createOSXinstallPkg is a Python library typically used in Devops, Ubuntu, Debian applications. createOSXinstallPkg has no bugs, it has no vulnerabilities and it has low support. However createOSXinstallPkg build file is not available and it has a Non-SPDX License. You can download it from GitHub.

This tool allows you to create an installer package from an "Install OS X.app" or an InstallESD.dmg. You can use this package to install OS X on an empty partition, but perhaps more interestingly, you can also use it to upgrade existing OS X installations to a newer version of the OS X. There are many tools and workflows that support the installation of Apple packages; you can use these together with an OS X installation package to upgrade machines to the latest version of OS X. This is especially interesting when used with tools like Munki -- you can automate the upgrade of a group of machines while still preserving user data, or offer an upgrade as a "Self-Service"-type option where a user can initiate an OS X upgrade themselves without needing to have administrative rights.

Support

Quality

Security

License

Reuse

Support

createOSXinstallPkg has a low active ecosystem.

It has 313 star(s) with 48 fork(s). There are 65 watchers for this library.

It had no major release in the last 6 months.

There are 7 open issues and 14 have been closed. On average issues are closed in 15 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of createOSXinstallPkg is current.

Quality

createOSXinstallPkg has 0 bugs and 0 code smells.

Security

createOSXinstallPkg has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

createOSXinstallPkg code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

createOSXinstallPkg has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

createOSXinstallPkg releases are not available. You will need to build from source code and install.

createOSXinstallPkg has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of createOSXinstallPkg

Get all kandi verified functions for this library.

createOSXinstallPkg Key Features

No Key Features are available at this moment for createOSXinstallPkg.

createOSXinstallPkg Examples and Code Snippets

No Code Snippets are available at this moment for createOSXinstallPkg.

Community Discussions

Trending Discussions on Devops

Windows gitlab runner stop execute job

Podman server API version is too old. Client "4.0.0" server "3.4.4"

Oracle docker container not working properly on Mac M1 BigSur

Gitlab pipeline - instead of 1, 2 are running

Azure Linux App Service : Installing packages after deploy from Devops pipeline

$CI_COMMIT_TAG in "if" statemets of regular job

What are the drawbacks to deploying web applications to Tomcat using the filesystem rather than an EAR file?

cypress command returns error in pipeline

Azure DevOps YAML Pipeline Error: While parsing a block mapping did not find expected key

How to commit and push to a private repo(A), from a different repo(B), in github actions workflow (B) , using personal access token

QUESTION

Windows gitlab runner stop execute job

Asked 2022-Mar-22 at 08:28

ci, and i-ve installed my gitlab-runner on a ec2 machine Ubuntu Server 18.04 LTS t2.micro, and when im pushing my code to start the build i get this

But it keeps stucked like this and after 1 hour it timeouts

I really don't know what to do about this problem knowing that i can clone successfully the project manually in my ec2 machine.

Any help is much appreciated if you ever encountered this problem and thanks in advance.

...

ANSWER

Answered 2022-Mar-22 at 08:28

check your job config or your timeout

Source https://stackoverflow.com/questions/71560799

QUESTION

Podman server API version is too old. Client "4.0.0" server "3.4.4"

Asked 2022-Mar-17 at 16:22

I'm trying to use Podman to build an image of a Spring Boot project in IntelliJ. Jetbrain's guide suggests to "Select TCP socket and specify the Podman API service URL in Engine API URL" within Build,Execution,Deployment > Docker (see https://www.jetbrains.com/help/idea/podman.html).

However, when giving the TCP socket found on Podman's documentation (see https://docs.podman.io/en/latest/markdown/podman-system-service.1.html), IntelliJ says it cannot connect.

Finally, when here is the error that appears in terminal:

...

ANSWER

Answered 2022-Mar-17 at 16:22

Facing the same problem due to podman version upgrade.

Seems like a version downgrade would be required to recover the containers, but haven't tried it yet.
This issue points on deleting the machine and creating it again, but the containers would be lost
https://github.com/containers/podman/issues/13510

Source https://stackoverflow.com/questions/71497349

QUESTION

Oracle docker container not working properly on Mac M1 BigSur

Asked 2022-Mar-05 at 20:46

I was recently trying to create a docker container and connect it with my SQLDeveloper but I started facing some strange issues. I downloaded the docker image using below pull request:

...

ANSWER

Answered 2021-Sep-19 at 21:17

There are two issues here:

Oracle Database is not supported on ARM processors, only Intel. See here: https://github.com/oracle/docker-images/issues/1814
Oracle Database Docker images are only supported with Oracle Linux 7 or Red Hat Enterprise Linux 7 as the host OS. See here: https://github.com/oracle/docker-images/tree/main/OracleDatabase/SingleInstance

Oracle Database ... is supported for Oracle Linux 7 and Red Hat Enterprise Linux (RHEL) 7. For more details please see My Oracle Support note: Oracle Support for Database Running on Docker (Doc ID 2216342.1)

The referenced My Oracle Support Doc ID goes on to say that the database binaries in their Docker image are built specifically for Oracle Linux hosts, and will also work on Red Hat. That's it.

Linux being what it is (flexible), lots of people have gotten the images to run on other flavors like Ubuntu with a bit of creativity, but only on x86 processors and even then the results are not guaranteed by Oracle: you won't be able to get support or practical advice when (and it's always when, not if in IT) things don't work as expected. You might not even be able to tell when things aren't working as they should. This is a case where creativity is not particularly rewarded; if you want it to work and get meaningful help, my advice is to use the supported hardware architecture and operating system version. Anything else is a complete gamble.

Source https://stackoverflow.com/questions/69069927

QUESTION

Gitlab pipeline - instead of 1, 2 are running

Asked 2022-Feb-15 at 12:54

I would like to add to Gitlab pipeline a stage which verifies that the person approving the MR is different from the person doing the creation/merge (for this to work, I checked the setting in Gitlab that says: "Pipelines must succeed").

...

ANSWER

Answered 2022-Feb-12 at 00:24

To avoid duplicate pipelines:

Source https://stackoverflow.com/questions/71083133

QUESTION

Azure Linux App Service : Installing packages after deploy from Devops pipeline

Asked 2022-Jan-26 at 16:26

I'm currently setuping a CI/CD pipeline in Azure Devops to deploy a NodeJS app on a linux hosted app service (not a VM).

My build and deploy both go smoothly, BUT I need to make sure some packages are installed in the environment after the app has been deployed.

The issue is: whatever apt-get script I create after the deploy, I have to run then manually for them to actually take effect. In the Pipeline log they seem to have been executed, though.

Here is the part of my yaml code responsible for the deploy, did I miss something?

...

ANSWER

Answered 2022-Jan-26 at 16:26

For now, went with a "startup.sh" file which I run manually after each deploy. Gonna go through docker later though

Source https://stackoverflow.com/questions/70807360

QUESTION

$CI_COMMIT_TAG in "if" statemets of regular job

Asked 2022-Jan-24 at 19:45

I try to make a pretty basic GitLab CI job.
I want:
When I push to develop, gitlab builds docker image with tag "develop"
When I push to main, gitlab checks that current commit has tag, and builds image with it or job is not triggered.

...

ANSWER

Answered 2022-Jan-24 at 19:45

Gitlab CI/CD has multiple 'pipeline sources', and some of the Predefined Variables only exist for certain sources.

For example, if you simply push a new commit to the remote, the value of CI_PIPELINE_SOURCE will be push. For push pipelines, many of the Predefined Variables will not exist, such as CI_COMMIT_TAG, CI_MERGE_REQUEST_SOURCE_BRANCH_NAME, CI_EXTERNAL_PULL_REQUEST_SOURCE_BRANCH_NAME, etc.

However if you create a Git Tag either in the GitLab UI or from a git push --tags command, it will create a Tag pipeline, and variables like CI_COMMIT_TAG will exist, but CI_COMMIT_BRANCH will not.

One variable that will always be present regardless what triggered the pipeline is CI_COMMIT_REF_NAME. For Push sources where the commit is tied to a branch, this variable will hold the branch name. If the commit isn't tied to a branch (ie, there was once a branch for that commit but now it's been deleted) it will hold the full commit SHA. Or, if the pipeline is for a tag, it will hold the tag name.

For more information, read through the different Pipeline Sources (in the description of the CI_PIPELINE_SOURCE variable) and the other variables in the docs linked above.

What I would do is move this check to the script section so we can make it more complex for our benefit, and either immediately exit 0 so that the job doesn't run and it doesn't fail, or run the rest of the script.

Source https://stackoverflow.com/questions/69199614

QUESTION

What are the drawbacks to deploying web applications to Tomcat using the filesystem rather than an EAR file?

Asked 2022-Jan-04 at 12:28

Since Tomcat just unzips the ~~EAR~~ WAR to the filesystem to serve the app, what is the benefit of using an ~~EAR~~ WAR and what are the drawbacks to just pushing a filesystem to the Tomcat webapps filesystem?

...

ANSWER

Answered 2021-Dec-25 at 11:32

Tomcat supports WAR but not EAR. Anyways , I think your question is about why we normally deploy the application that is packaged as a single WAR rather than the exploded WAR (i.e exploded deployment).

The main advantages for me are :

It is more easy to handle the deployment when you just need to deploy one file versus deploying many files in the exploded WAR deployment.
Because there is only one file get deployed , we can always make sure the application is running in a particular version. If we allow to deploy individual files and someone just update several files to other version , it is difficult to tell what is the exact version that the application is running.

There are already some discussion about such topics before , you can refer this and this for more information.

Source https://stackoverflow.com/questions/70438632

QUESTION

cypress command returns error in pipeline

Asked 2021-Dec-30 at 16:53

I have a CI setup using github Action/workflow to run cypress automated test everytime when a merge is done on the repo. The installation steps works fine however i run into issue when executing cypress command, let me show you the code.

CI pipeline in .github/workflows

...

ANSWER

Answered 2021-Dec-30 at 16:53

After searching for some time turns out i was using cypress 8.7.0 which was causing the issue, i downgraded to cypress 8.5.0 and it started working, hope that helps anyone else having this issue

Source https://stackoverflow.com/questions/70518148

QUESTION

Azure DevOps YAML Pipeline Error: While parsing a block mapping did not find expected key

Asked 2021-Dec-07 at 10:42

I just created a pipeline using the YAML file and I am always getting the error "/_Azure-Pipelines/templates/webpart.yml: (Line: 41, Col: 27, Idx: 1058) - (Line: 41, Col: 60, Idx: 1091): While parsing a block mapping, did not find expected key.". I already verified the indentation of my YAML file and that looks fine.

Below is my YAML file.

...

ANSWER

Answered 2021-Dec-07 at 10:42

It was due to a missing quotation mark in the task PublishBuildArtifacts@1 for the PathtoPublish. I found this error by using a YAML extension provided by RedHat.

Once you enabled that extension and set the formatted for YAML (SHIFT + ALT + F), it should show you the errors in your YAML file.

Source https://stackoverflow.com/questions/70258702

QUESTION

How to commit and push to a private repo(A), from a different repo(B), in github actions workflow (B) , using personal access token

Asked 2021-Dec-05 at 10:05

name: deploy-me
on: [push]
jobs:
  deploys-me:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-node@v2
        with:
          node-version: '14'
      - run: npm install
      - run: npm run dev

     //Next  I want to copy some file from this repo and commit to a different repo and push it

...

ANSWER

Answered 2021-Dec-05 at 09:57

name: deploy-me
'on':
    - push
jobs:
    deploy-me:
        runs-on: ubuntu-latest
        steps:
            - uses: actions/checkout@v2
            - uses: actions/setup-node@v2
              with:
                  node-version: '14'
              env:
                  ACCESS_TOKEN: '${{ secrets.ACCESS_TOKEN }}'
            - run: npm install
            - run: npm run build
            - run: |
                  cd lib
                  git config --global user.email "xxx@gmail.com"
                  git config --global user.name "spark"
                  git config --global credential.helper cache
                  git clone https://${{secrets.ACCESS_TOKEN}}@github.com/sparkdevv/xxxxxx
                  cp index.js clonedFolder/ -f
                  cd clonedFolder
                  git add .
                  git commit -m "$(date)"
                  git push

Source https://stackoverflow.com/questions/70225077

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install createOSXinstallPkg

This toolset, which includes:. You may put the toolset anywhere you'd like, but keep the Resources folder and its contents in the same directory as createOSXinstallPkg. You'll also need an installation source for OS X (10.7 through 10.11 currently supported): a copy of the "Install Mac OS X Lion.app", "Install OS X Mountain Lion.app", "Install OS X Mavericks.app", etc, install application you can get from the Mac App Store. Finally, and most importantly, you'll need the rights to install the OS X version on the machines you manage. Just because this tool allows you to create an OS X installation package does not mean it is legal for your organization to install it on all your Macs. (Since Mavericks, Yosemite, and El Capitan are free, one assumes you can install them with abandon. However, I am not a lawyer, and this does not constitute advice or a recommendation.). You must run createOSXinstallPkg with root privileges. This creates an installation package in the current directory named InstallOSX_[version]_[build].pkg, where "version" and "build" are the version and build numbers of the OS X version that will be installed. Adding the --output option allows you to specify an alternate location and/or name for the output package. The --pkg option allows you to add one or more packages to be installed after the OS is installed. You may specify multiple packages. They will be installed in the order given at the command line. The --identifier option allows you to change the package identifier, which is by default 'com.googlecode.munki.installosx.pkg'. Options to createOSXinstallPkg can be stored in a plist file. This allows you to save the "ingredients" and "recipe" for a package for future reuse. If an option is specified in the plist and also explicitly at the command-line, the command-line "wins". (Note this means also that since multiple packages can be specified, that packages in a plist and packages at the command-line are not merged; the packages given at the command-line are the only packages used.). The package generated by createOSXinstallPkg is a 'payload-free' package -- that is, it does not install anything from the traditional Archive.pax.gz payload found in most packages. Instead, the real work is done as a package postflight script located at [PACKAGE]/Contents/Resources/postflight. The postflight script performs the actions that the GUI "Install Mac OS X Lion" or "Install OS X Mountain Lion" application does when you choose to install OS X. Since most of the work is done with a postflight script, and since that script may need to do a lengthy copy of around 4GB of data (if the package is not on the target volume), you may see a long delay at the "Running package scripts" stage of installation. This is normal. (Annoyingly, the Installer.app displays "Install time remaining: Less than a minute" for several minutes during this stage.). The next step would be to reboot, but the postflight script does not do this; it just exits. The package is marked as requiring a reboot, so whatever mechanism is used to install the package is responsible for rebooting as soon as possible after the install. Upon reboot, the machine boots and runs the OS X Installer just as if you had run the "Install Mac OS X Lion" or "Install OS X El Capitan" application manually. It creates or updates a "Recovery HD" partition and installs OS X on the target volume, displaying the OS X Installer GUI. When installation is complete, the machine reboots a second time, this time booting from the new OS X installation. A "Distribution" file, located at InstallOSX.pkg/Contents/distribution.dist controls the InstallCheck and VolumeCheck logic. createOSXinstallPkg copies InstallCheck and VolumeCheck logic from the OSInstall.mpkg found in the Install.app or InstallESD.dmg. This means that the resulting package will use the same logic as Apple when deciding if a machine/volume is a valid install destination. (One exception -- createOSXinstallPkg disables the check for command-line installs; without disabling this check you would not be able to install Lion or Mountain Lion using Munki or ARD or any other mechanism that uses the command-line /usr/sbin/installer.). The distribution.dist declares the install size is 8388608 KB (8* 1024 * 1024 KB, or 8GB), which should prevent attempted installation on volumes with less than 8GB free space. You can edit this number if you'd like.
Create an OS X Install Data directory at the root of the target volume.
Mount the InstallESD.dmg disk image.
Copy the kernelcache and boot.efi files from the disk image to the OS X Install Data directory. (The kernelcache is copied to the Recovery HD helper partition if the target volume is encrypted with FileVault 2.)
Unmount (eject) the InstallESD.dmg disk image.
If the InstallLion.pkg is on the same volume as the target volume, create a hard link to the InstallESD.dmg disk image in OS X Install Data, otherwise copy the InstallESD.dmg disk image to that directory.
Create a com.apple.Boot.plist file in the Mac OS X Install Data directory which tells the kernel how to mount the disk image to use for booting. (This file is instead created on the the Recovery HD helper partition if the target volume is encrypted with FileVault 2.)
Create a minstallconfig.xml file, which tells the OS X Installer what to install and to which volume to install it. It also provides a path to a MacOSXInstaller.choiceChanges file if one has been included in the package.
Create an index.sproduct file and an OSInstallAttr.plist in the OS X Install Data directory. These are also used by the OS X Installer.
Set a variable in nvram that the OS X Installer uses to find the product install info after reboot.
Use the bless command to cause the Mac to boot from the kernel files copied to the OS X Install Data directory.
If the target volume is a Core Storage or Apple RAID volume, setup/update boot helper partitions (these are the ones that show up as type "Apple_Boot" in the output of diskutil list).
You'll find a MacOSXInstaller.choiceChanges file at InstallOSX.pkg/Contents/Resources/OS X Install Data/MacOSXInstaller.choiceChanges. See man installer for more info on ChoiceChangesXML files. The most likely customization you will want to do is to add additional packages to be installed after the OS install. Some examples might include a package that keeps the Setup Assistant from running when the machine first starts up under Lion, or a package that triggers your software installation management system to run, check for, and install any updates on the first boot after OS X is installed.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: