Downloads:

381

Downloads of v 1.5.0:

72

Last Update:

20 Aug 2021

Package Maintainer(s):

Software Author(s):

  • Beets Team.

Tags:

beets

Beets

  • 1
  • 2
  • 3

1.5.0 | Updated: 20 Aug 2021

Downloads:

381

Downloads of v 1.5.0:

72

Maintainer(s):

Software Author(s):

  • Beets Team.

Tags:

beets

  • 1
  • 2
  • 3
Beets 1.5.0

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Beets, run the following command from the command line or from PowerShell:

>

To upgrade Beets, run the following command from the command line or from PowerShell:

>

To uninstall Beets, run the following command from the command line or from PowerShell:

>

Deployment Method:

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

1. Enter Your Internal Repository Url

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


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • 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://community.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. Copy Your Script

choco upgrade beets -y --source="'INTERNAL REPO 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 beets -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install beets
  win_chocolatey:
    name: beets
    version: '1.5.0'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'beets' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.5.0'
end

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


cChocoPackageInstaller beets
{
    Name     = "beets"
    Version  = "1.5.0"
    Source   = "INTERNAL REPO URL"
}

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


package { 'beets':
  ensure   => '1.5.0',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

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


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

There are versions of this package awaiting moderation . See the Version History section below.

This package was approved by moderator TheCakeIsNaOH on 25 Aug 2021.

Description

Beets is the media library management system for obsessive music geeks.

The purpose of beets is to get your music collection right once and for all.
It catalogs your collection, automatically improving its metadata as it goes.
It then provides a bouquet of tools for manipulating and accessing your music.

Here's an example of beets' brainy tag corrector doing its thing:
``
$ beet import ~/music/ladytron
Tagging:
Ladytron - Witching Hour
(Similarity: 98.4%)

  • Last One Standing -> The Last One Standing
  • Beauty -> Beauty*2
  • White Light Generation -> Whitelightgenerator
  • All the Way -> All the Way...``

Because beets is designed as a library, it can do almost anything you can
imagine for your music collection. Via plugins, beets becomes a panacea:

  • Fetch or calculate all the metadata you could possibly need: album art,
    lyrics, genres, tempos, ReplayGain levels, or acoustic
    fingerprints
    .
  • Get metadata from MusicBrainz, Discogs, and Beatport. Or guess
    metadata using songs' filenames or their acoustic fingerprints.
  • Transcode audio to any format you like.
  • Check your library for duplicate tracks and albums_ or for albums that
    are missing tracks
    .
  • Clean up crufty tags left behind by other, less-awesome tools.
  • Embed and extract album art from files' metadata.
  • Browse your music library graphically through a Web browser and play it in any
    browser that supports HTML5 Audio.
  • Analyze music files' metadata from the command line.
  • Listen to your library with a music player that speaks the MPD protocol
    and works with a staggering variety of interfaces.

If beets doesn't do what you want yet, writing your own plugin is
shockingly simple if you know a little Python.


tools\chocolateyinstall.ps1
Update-SessionEnvironment
$version = '1.5.0'
 
$proxy = Get-EffectiveProxy
if ($proxy) {
  Write-Host "Setting CLI proxy: $proxy"
  $env:http_proxy = $env:https_proxy = $proxy
}
python -m pip install beets==$version
tools\chocolateyuninstall.ps1
$ErrorActionPreference = 'Stop'
python -m pip uninstall beets -y

Log in or click on link to see number of positives.

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.

Add to Builder Version Downloads Last Updated Status
Beets 1.6.0 10 Sunday, November 28, 2021 Ready
Beets 1.4.9 299 Saturday, March 21, 2020 Approved

Discussion for the Beets Package

Ground Rules:

  • This discussion is only about Beets and the Beets 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 Beets, 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