Downloads:

28,573

Downloads of v 2017.03.09:

185

Last Update:

3/15/2017

Package Maintainer(s):

Software Author(s):

  • Dan Smith (KK7DS)

Tags:

admin chirp HAM amateur radio

CHIRP (Install)

This is not the latest version of CHIRP (Install) available.

2017.03.09 | Updated: 3/15/2017

Downloads:

28,573

Downloads of v 2017.03.09:

185

Maintainer(s):

Software Author(s):

  • Dan Smith (KK7DS)

Tags:

admin chirp HAM amateur radio

CHIRP (Install) 2017.03.09

This is not the latest version of CHIRP (Install) available.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed

Details

To install CHIRP (Install), run the following command from the command line or from PowerShell:

>

To upgrade CHIRP (Install), run the following command from the command line or from PowerShell:

>

To uninstall CHIRP (Install), run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade chirp.install -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade chirp.install -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode


- name: Ensure chirp.install installed
  win_chocolatey:
    name: chirp.install
    state: present
    version: 2017.03.09
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'chirp.install' do
  action    :install
  version  '2017.03.09'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: chirp.install,
    Version: 2017.03.09,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller chirp.install
{
   Name     = 'chirp.install'
   Ensure   = 'Present'
   Version  = '2017.03.09'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'chirp.install':
  provider => 'chocolatey',
  ensure   => '2017.03.09',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install chirp.install version="2017.03.09" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved as a trusted package on 3/16/2017.

Description

CHIRP is a free, open-source tool for programming your amateur radio. It supports a large number of manufacturers and models, as well as provides a way to interface with multiple data sources and formats.
CHIRP is distributed as a series of automatically-generated builds. Any time we make a change to CHIRP, a build is created for it the next day. Thus, CHIRP is versioned by the date on which it was created, which makes it easy to determine if you have an older build. We don't put experimental things into CHIRP before they are ready, except where specifically called out with a warning. Thus, you do not need to worry about finding a stable version to run. You should always be on the latest build available.

tools\chocolateyinstall.ps1 
$ErrorActionPreference = 'Stop';

$packageName= 'CHIRP.install'
$version	= '2017.03.09'
$url        = 'http://trac.chirp.danplanet.com/chirp_daily/daily-20170309/chirp-daily-20170309-installer.exe'
$fileType = 'exe'
$silentArgs = '/S'
$checksum = 'bb6893e7e6e5ab269304126e006707ece2738d5a'
$checksumType = 'sha1'

Install-ChocolateyPackage $packagename $fileType $silentArgs $url -checksum $checksum -checksumType $checksumType
tools\chocolateyuninstall.ps1 
$package = 'CHIRP.install'
$file = (Get-ItemProperty HKLM:SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\CHIRP UninstallString).UninstallString;
Uninstall-ChocolateyPackage $package 'EXE' -SilentArgs '/S' -file $file

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
CHIRP (Install) 2019.11.10 41 Sunday, November 10, 2019 Approved
CHIRP (Install) 2019.11.09 18 Saturday, November 9, 2019 Approved
CHIRP (Install) 2019.10.29 49 Tuesday, October 29, 2019 Approved
CHIRP (Install) 2019.10.22 51 Tuesday, October 22, 2019 Approved
CHIRP (Install) 2019.10.18 39 Friday, October 18, 2019 Approved
CHIRP (Install) 2019.09.25 94 Wednesday, September 25, 2019 Approved
CHIRP (Install) 2019.09.05 84 Thursday, September 5, 2019 Approved
CHIRP (Install) 2019.08.29 68 Thursday, August 29, 2019 Approved
CHIRP (Install) 2019.08.24 63 Saturday, August 24, 2019 Approved
CHIRP (Install) 2019.08.17 55 Saturday, August 17, 2019 Approved

This package has no dependencies.

Discussion for the CHIRP (Install) Package

Ground Rules:

  • This discussion is only about CHIRP (Install) and the CHIRP (Install) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or CHIRP (Install), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus