Giter Club home page Giter Club logo

dropcaster's Introduction

Dropcaster - Simple Podcast Publishing

Build Status

This project is developed with the readme-driven development method. This file describes the functionality that is actually implemented, whereas the vision reflects where the tool should go.

Dropcaster is a podcast feed generator for the command line. It works with any (static file) web hoster.

Author: Nicolas E. Rabenau [email protected]

What is the problem that Dropcaster is trying to solve?

You have a number of podcast episodes that you would like to publish as a feed. Nothing else - no fancy website, no stats, nothing but the pure podcast.

With Dropcaster, you simply put the mp3 files into the public_html folder of your web host. Then run dropcaster - it generates the feed and writes it to a file, e.g. index.rss. You can then take the RSS file's URL and publish it as the feed URL.

The feed URL can be consumed by any podcatcher, e.g. iTunes or Juice.

Installation

As a Ruby Gem

$ gem install dropcaster
$ dropcaster --help

libxml-ruby is a frequent offender with installation problems. As usual, Stack Overflow has the answer (at least for macOS with Homebrew):

$ gem install --no-document libxml-ruby -- --with-xml2-config="$(brew --prefix libxml2)/bin/xml2-config"

Docker

If you prefer Docker over a local installation, use

$ docker run -it --rm nerab/dropcaster dropcaster --help

The container will need access to the mp3 files on your workstation with a bind mount. For instance, running dropcaster with the test fixtures will look like this:

$ docker \
    run \
      -it \
      --rm \
      --mount type=bind,source="$(pwd)"/test/fixtures,target=/public_html \
    nerab/dropcaster

Replace "$(pwd)"/test/fixtures with your own folder of mp3s, and you can run the command above without even installing Ruby.

Basic Usage

Once Dropcaster is installed, the only two other things you will need are a channel definition and one or more mp3 files to publish.

Let's start with the channel definition. It is a simple YAML file that holds the general information about your podcast channel. According to the RSS 2.0 spec, the only mandatory information that your channel absolutely needs are a title, a description and a link to a web site where the channel belongs to.

The simplest channel file looks like this:

:title: 'All About Everything'
:description: 'A show about everything'
:url: 'http://www.example.com/podcasts/everything/index.html'

Store this file as channel.yml in the same directory where the mp3 files of your podcast reside. The channel definition is expected to be present in the same directory as your mp3 files, but this can be overridden using a command line switch. You can find a more elaborate example for the channel definition in the doc folder of the Dropcaster gem. You can find it by running gem open dropcaster.

Now that we have the podcast channel defined, we need at least one episode (an audio file) in it. From Dropcaster's perspective, it does not matter how the episode was produced, but the critical information is the meta data in the mp3 file, because that is the authoritative source for the episode information. Almost all audio editors can write metadata, usually called ID3 tags. Dropcaster reads these tags from the mp3 files and fills the item element in the feed (that's how an episode is defined, technically) from it.

With all required pieces in place, we could generate the podcast feed. Just before we do that, we will inspect the feed by running the following commands:

$ cd ~/public_html
$ dropcaster

(The above lines assume that public_html is the web server's document root, and that there is at least one mp3 file in public_html).

Dropcaster will print the feed to standard-out, without writing it to disk. When you are happy with the results, call Dropcaster again, but redirect the output to a file, this time:

$ dropcaster > index.rss

If all went well, you will now have a valid podcast feed in public_html, listing all mp3 files as podcast episodes. Please see the section Publish Your Feed for details on how to find the public URL of your feed.

Use Cases

Publish a New Episode

  1. Drop the mp3 file into the public_html folder, and then run the following command in that directory:

    $ dropcaster > index.rss
  2. Sync the updated index.rss file to the public web server, and any podcast client will download the new episode as soon as it has loaded the updated index.rss.

Delete an Episode

  1. Remove the mp3 you want to delete from the public_html folder, and then run the following command in the directory where the remaining mp3 files reside:

    $ dropcaster > index.rss
  2. Sync the updated index.rss file to the public web server. Podcast clients will no longer download the removed episode.

Replace an Episode With an Updated File

  1. In the public_html folder, replace the mp3 you want to update with a new version, and then run the following command in the directory where the mp3 files reside:

    $ dropcaster > index.rss
  2. Sync the updated index.rss file to the public web server. Podcast clients detect the change and download the updated episode.

Generate a Podcast Feed for a Subset of the Available MP3 Files

Dropcaster accepts any number of files or directories as episodes. For directories, all files ending in .mp3 will be included. For advanced filtering, you can use regular shell patterns to further specify which files will be included. These patterns will be resolved by the shell itself (e.g. bash), and not by Dropcaster.

For example, in order to generate a feed that only publishes MP3 files where the name starts with 'A', call Dropcaster like this:

$ dropcaster A*.mp3 > index.rss

Publish More than One Feed

$ dropcaster project1 > project1.rss
$ dropcaster project2 > project2.rss

or

$ cd project1
$ dropcaster > index.rss
$ cd ../project2
$ dropcaster > index.rss

Include Episodes From Two Subdirectories Into a Single Feed

$ dropcaster project1 project2 > index.rss

Advanced features

Overriding defaults

Dropcaster is opinionated software. That means, it makes a number of assumptions about names, files, and directory structures. Dropcaster will be most simple to use if these assumptions and opinions apply to your way of using the program.

However, it is still possible to override Dropcaster's behavior in many ways. You can, for instance, host your episode files on a different URL than the channel. Instead of writing title, subtitle, etc. to a channel.yml, you may also spedify them on the command line.

In order to find out about all the options, simply run

$ dropcaster --help

Using custom channel templates

Dropcaster generates a feed that is suitable for most podcast clients, especially iTunes. By default, dropcaster follows Apple's podcast specs / recommendations.

It is also possible to customize the channel by supplying an alternative channel template on the command line. Start your own template by copying the default template, or look at the test directory of the dropcaster gem. You can get there by running gem open dropcaster.

Generate a HTML page for your podcast

Besides generating an RSS feed, dropcaster can also generate HTML that can be used as a home page for your podcast. The template directory contains a sample template that can be used to get started:

$ dropcaster --channel-template templates/channel.html.erb

As discussed above, the output of this command can be written to a file, too:

$ dropcaster --channel-template templates/channel.html.erb > ~/public_html/allabouteverything.html

Dropcaster works exactly the same, whether it generates an RSS feed or a HTML page. Therefore, all options discussed before also apply when generating HTML.

A Note on iTunes

The generated XML file contains all elements required for iTunes. However, Dropcaster will not notify the iTunes store about new episodes.

Using Dropcaster With S3 or Digital Ocean Spaces

If you set up an S3 bucket or Digital Ocean Space (or any other s3 compatible static asset host), you can easily sync your local podcast directory using a command line tool like s3cmd.

After installing s3cmd, make sure you have the right credentials to write to your bucket/space. Add your mp3 files to your folder, run dropcaster > index.rss and then s3cmd sync ./ s3://$your-bucket-name --acl public-read. S3cmd will now upload any new or changed files to your bucket.

Episode Identifier (uuid)

Dropcaster uses a rather simple approach to uniquely identify the episodes. It simply generates a SHA1 hash of the mp3 file. If it changes, for whatever reason (even if only a tag was changed), the episode will get a new UUID, and any podcatcher will fetch the episode again (which is what you want, in most cases).

I Don't Like the Output Format that Dropcaster produces

Dropcaster uses an ERB template to generate the XML feed. The template was written so that it is easy to understand, but not necessarily in a way that would make the output rather nice-looking. That should not be an issue, as long as the XML is correct.

It you prefer a more aesthetically pleasing output, just pipe the output of Dropcaster through xmllint, which is part of libxml:

$ dropcaster | xmllint --format -

For writing the output to a file, just redirect the ouput of the above command:

$ dropcaster | xmllint --format - > index.rss

Web site

Dropcaster uses Steve Klabnik's approach for publishing the site with Travis CI.

Copyright

Copyright (c) 2011-2021 Nicolas E. Rabenau. See LICENSE.txt for further details.

dropcaster's People

Contributors

dependabot-preview[bot] avatar dependabot-support avatar dependabot[bot] avatar dkhgh avatar hammady avatar miknight avatar nerab avatar stephenwade avatar suhlig avatar terotil avatar vitorgalvao avatar x0nic avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

dropcaster's Issues

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "bundler":
  In Gemfile:
    dropcaster was resolved to 1.1.0, which depends on
      bundler

    guard-bundler was resolved to 3.0.0, which depends on
      bundler (>= 2.1, < 3)

  Current Bundler version:
    bundler (1.17.3)
This Gemfile requires a different version of Bundler.
Perhaps you need to update Bundler by running `gem install bundler`?

Could not find gem 'bundler (>= 2.1, < 3)', which is required by gem 'guard-bundler', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "bundler":
  In Gemfile:
    dropcaster was resolved to 1.1.0, which depends on
      bundler

    guard-bundler was resolved to 3.0.0, which depends on
      bundler (>= 2.1, < 3)

  Current Bundler version:
    bundler (1.17.3)
This Gemfile requires a different version of Bundler.
Perhaps you need to update Bundler by running `gem install bundler`?

Could not find gem 'bundler (>= 2.1, < 3)', which is required by gem 'guard-bundler', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

Recording date typo

When pulling the recording date out of the ID3 tag, I believe thereโ€™s a typo here:

if tag2.TDR.blank?

TDR isnโ€™t a tag I can find mention of anywhere, though TRD is, when looking at the list from the dependent library here. Iโ€™ve tried setting any/all recording date fields, and pubDate always just ends up being today.

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "bundler":
  In Gemfile:
    dropcaster was resolved to 1.1.0, which depends on
      bundler

    guard-bundler was resolved to 3.0.0, which depends on
      bundler (>= 2.1, < 3)

  Current Bundler version:
    bundler (1.17.3)
This Gemfile requires a different version of Bundler.
Perhaps you need to update Bundler by running `gem install bundler`?

Could not find gem 'bundler (>= 2.1, < 3)', which is required by gem 'guard-bundler', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "activesupport":
  In Gemfile:
    dropcaster was resolved to 1.0.0, which depends on
      activesupport (>= 4.2.10, <= 5.2.3)

    github-pages was resolved to 197, which depends on
      activesupport (= 4.2.10)

Bundler could not find compatible versions for gem "rouge":
  In Gemfile:
    github-pages was resolved to 197, which depends on
      rouge (= 2.2.1)

    github-pages was resolved to 197, which depends on
      jekyll (= 3.7.4) was resolved to 3.7.4, which depends on
        rouge (>= 1.7, < 4)

Bundler could not find compatible versions for gem "ruby":
  In Gemfile:
    ruby

    github-pages was resolved to 197, which depends on
      activesupport (= 4.2.10) was resolved to 4.2.10, which depends on
        ruby (>= 1.9.3)

    libnotify was resolved to 0.9.4, which depends on
      ffi (>= 1.0.11) was resolved to 1.10.0, which depends on
        ruby (< 2.7.dev) x86-mingw32

    libnotify was resolved to 0.9.4, which depends on
      ffi (>= 1.0.11) was resolved to 1.10.0, which depends on
        ruby (>= 1.9)

    github-pages was resolved to 197, which depends on
      jekyll (= 3.7.4) was resolved to 3.7.4, which depends on
        ruby (>= 2.1.0)

    github-pages was resolved to 197, which depends on
      listen (= 3.1.5) was resolved to 3.1.5, which depends on
        ruby (>= 2.2.3)

    github-pages was resolved to 197, which depends on
      nokogiri (>= 1.8.5, < 2.0) was resolved to 1.10.2, which depends on
        ruby (>= 2.3) x86-mingw32

    github-pages was resolved to 197, which depends on
      nokogiri (>= 1.8.5, < 2.0) was resolved to 1.10.2, which depends on
        ruby (>= 2.3.0)

    rubocop was resolved to 0.66.0, which depends on
      parser (>= 2.5, != 2.5.1.1) was resolved to 2.6.2.1, which depends on
        ruby (>= 2.0.0)

    rubocop was resolved to 0.66.0, which depends on
      psych (>= 3.1.0) was resolved to 3.1.0, which depends on
        ruby (< 2.6) x86-mingw32

    rubocop was resolved to 0.66.0, which depends on
      psych (>= 3.1.0) was resolved to 3.1.0, which depends on
        ruby (>= 2.2.2)

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

You can mention @dependabot in the comments below to contact the Dependabot team.

Logger not working / improve error messages

Hello, I spent a lot of time today trying to track down the cause of an Mp3InfoEOFError. I figured this was due to a corrupted audio file, however I was working with a large number of files and needed to figure out which one was causing the error. Enabling --verbose and --trace didn't provide any useful diagnostics so I decided to try modifying the gem.

I see there is some sort of custom Logging class in use inside lib/dropcaster. However the only log messages I see actually getting logged are those coming from bin/dropcaster. All the other files containing logger.error etc. appear to just go into the void. I also tried adding print and puts inside these files and also did not see anything get logged to console.

I was evenutally able to track it down by adding a rescue block and raising a custom error like so (inside item.rb) which gets caught and logged by bin/dropcaster:

    def initialize(file_path, options=nil)
        logger.info("at file path " + file_path.to_s) # This doesn't work
        begin
              Mp3Info.open(file_path) { |mp3info|
                @file_path = Pathname.new(File.expand_path(file_path)).relative_path_from(Pathname.new(Dir.pwd)).cleanpath
                @tag = mp3info.tag
                @tag2 = mp3info.tag2
                @duration = mp3info.length
                if @tag2['ULT']
                  @lyrics = {}
                  @tag2['ULT'].split(/\x00/).drop(1).each_slice(2) { |k, v| @lyrics[k] = v }
                end
              }
        rescue Mp3InfoEOFError => error
            logger.error("Mp3InfoEOFError " + error.to_s) # This doesn't work
            raise "Mp3InfoEOFError at " + file_path.to_s
        end

This code was pretty rough so I didn't want to open a PR yet but I wanted to see why the logs might be getting swallowed first, as that seems like an easier solution to provide more useful diagnostics to the end user.

OS: macOS 10.13.6
Ruby Version: ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-darwin17] (installed via rbenv)
dropcaster gem version: 1.0.0

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "activesupport":
  In Gemfile:
    dropcaster was resolved to 1.0.0, which depends on
      activesupport

    github-pages was resolved to 197, which depends on
      activesupport (= 4.2.10)

Bundler could not find compatible versions for gem "rouge":
  In Gemfile:
    github-pages was resolved to 197, which depends on
      rouge (= 2.2.1)

    github-pages was resolved to 197, which depends on
      jekyll (= 3.7.4) was resolved to 3.7.4, which depends on
        rouge (>= 1.7, < 4)

Bundler could not find compatible versions for gem "ruby":
  In Gemfile:
    ruby

    github-pages was resolved to 197, which depends on
      activesupport (= 4.2.10) was resolved to 4.2.10, which depends on
        ruby (>= 1.9.3)

    libnotify was resolved to 0.9.4, which depends on
      ffi (>= 1.0.11) was resolved to 1.10.0, which depends on
        ruby (< 2.7.dev) x86-mingw32

    libnotify was resolved to 0.9.4, which depends on
      ffi (>= 1.0.11) was resolved to 1.10.0, which depends on
        ruby (>= 1.9)

    github-pages was resolved to 197, which depends on
      jekyll (= 3.7.4) was resolved to 3.7.4, which depends on
        ruby (>= 2.1.0)

    github-pages was resolved to 197, which depends on
      listen (= 3.1.5) was resolved to 3.1.5, which depends on
        ruby (>= 2.2.3)

    dropcaster was resolved to 1.0.0, which depends on
      nokogiri (>= 1.10.2, <= 1.10.3) was resolved to 1.10.3, which depends on
        ruby (>= 2.3) x86-mingw32

    dropcaster was resolved to 1.0.0, which depends on
      nokogiri (>= 1.10.2, <= 1.10.3) was resolved to 1.10.3, which depends on
        ruby (>= 2.3.0)

    rubocop was resolved to 0.66.0, which depends on
      parser (>= 2.5, != 2.5.1.1) was resolved to 2.6.2.1, which depends on
        ruby (>= 2.0.0)

    rubocop was resolved to 0.66.0, which depends on
      psych (>= 3.1.0) was resolved to 3.1.0, which depends on
        ruby (< 2.6) x86-mingw32

    rubocop was resolved to 0.66.0, which depends on
      psych (>= 3.1.0) was resolved to 3.1.0, which depends on
        ruby (>= 2.2.2)

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

You can mention @dependabot in the comments below to contact the Dependabot team.

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "bundler":
  In Gemfile:
    dropcaster was resolved to 1.1.0, which depends on
      bundler

    guard-bundler was resolved to 3.0.0, which depends on
      bundler (>= 2.1, < 3)

  Current Bundler version:
    bundler (1.17.3)
This Gemfile requires a different version of Bundler.
Perhaps you need to update Bundler by running `gem install bundler`?

Could not find gem 'bundler (>= 2.1, < 3)', which is required by gem 'dropcaster', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "activesupport":
  In Gemfile:
    dropcaster was resolved to 1.0.0, which depends on
      activesupport

    github-pages was resolved to 197, which depends on
      activesupport (= 4.2.10)

Bundler could not find compatible versions for gem "rouge":
  In Gemfile:
    github-pages was resolved to 197, which depends on
      rouge (= 2.2.1)

    github-pages was resolved to 197, which depends on
      jekyll (= 3.7.4) was resolved to 3.7.4, which depends on
        rouge (>= 1.7, < 4)

Bundler could not find compatible versions for gem "ruby":
  In Gemfile:
    ruby

    github-pages was resolved to 197, which depends on
      activesupport (= 4.2.10) was resolved to 4.2.10, which depends on
        ruby (>= 1.9.3)

    libnotify was resolved to 0.9.4, which depends on
      ffi (>= 1.0.11) was resolved to 1.10.0, which depends on
        ruby (< 2.7.dev) x86-mingw32

    libnotify was resolved to 0.9.4, which depends on
      ffi (>= 1.0.11) was resolved to 1.10.0, which depends on
        ruby (>= 1.9)

    github-pages was resolved to 197, which depends on
      jekyll (= 3.7.4) was resolved to 3.7.4, which depends on
        ruby (>= 2.1.0)

    github-pages was resolved to 197, which depends on
      listen (= 3.1.5) was resolved to 3.1.5, which depends on
        ruby (>= 2.2.3)

    github-pages was resolved to 197, which depends on
      nokogiri (>= 1.8.5, < 2.0) was resolved to 1.10.2, which depends on
        ruby (>= 2.3) x86-mingw32

    github-pages was resolved to 197, which depends on
      nokogiri (>= 1.8.5, < 2.0) was resolved to 1.10.2, which depends on
        ruby (>= 2.3.0)

    rubocop (>= 0.66.0, <= 0.67.2) was resolved to 0.67.2, which depends on
      parser (>= 2.5, != 2.5.1.1) was resolved to 2.6.2.1, which depends on
        ruby (>= 2.0.0)

    rubocop (>= 0.66.0, <= 0.67.2) was resolved to 0.67.2, which depends on
      psych (>= 3.1.0) was resolved to 3.1.0, which depends on
        ruby (< 2.6) x86-mingw32

    rubocop (>= 0.66.0, <= 0.67.2) was resolved to 0.67.2, which depends on
      ruby (>= 2.2.2)

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

You can mention @dependabot in the comments below to contact the Dependabot team.

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "bundler":
  In Gemfile:
    dropcaster was resolved to 1.1.0, which depends on
      bundler

    guard-bundler was resolved to 3.0.0, which depends on
      bundler (>= 2.1, < 3)

  Current Bundler version:
    bundler (1.17.3)
This Gemfile requires a different version of Bundler.
Perhaps you need to update Bundler by running `gem install bundler`?

Could not find gem 'bundler (>= 2.1, < 3)', which is required by gem 'dropcaster', in any of the sources.

Bundler could not find compatible versions for gem "pry":
  In snapshot (Gemfile.lock):
    pry (= 0.12.2)

  In Gemfile:
    pry

    pry-byebug (>= 3.8.0, <= 3.9.0) was resolved to 3.9.0, which depends on
      pry (~> 0.13.0)

Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "bundler":
  In Gemfile:
    dropcaster was resolved to 1.1.0, which depends on
      bundler

    guard-bundler was resolved to 3.0.0, which depends on
      bundler (>= 2.1, < 3)

  Current Bundler version:
    bundler (1.17.3)
This Gemfile requires a different version of Bundler.
Perhaps you need to update Bundler by running `gem install bundler`?

Could not find gem 'bundler (>= 2.1, < 3)', which is required by gem 'guard-bundler', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "bundler":
  In Gemfile:
    dropcaster was resolved to 1.1.0, which depends on
      bundler

    guard-bundler was resolved to 3.0.0, which depends on
      bundler (>= 2.1, < 3)

  Current Bundler version:
    bundler (1.17.3)
This Gemfile requires a different version of Bundler.
Perhaps you need to update Bundler by running `gem install bundler`?

Could not find gem 'bundler (>= 2.1, < 3)', which is required by gem 'dropcaster', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

Sidecar files

You may override the meta data for any episode by providing a YAML file with the same name as the mp3 file, but with an extension of yml or yaml (ususally refered to as sidecar file). Any attributes specified in this file override the ID tags in the mp3 file.

Dropcaster will only write the sidecar file if the appropriate command line option was passed, and it will use the information in it only for generating new files like the index.rss. It will not write back to mp3 files.

Sidecar files are also useful for referencing a (remote) enclosure without re-hosting it (which, besides wasted bandwidth, could also create copyright issues). If a sidecar file is present and it points to a remote media URL, dropcaster will generate an item in the feed, even if the media is not available locally.

Using Dropcaster for Archive.org files?

Hi all,

Does anyone have any experience using Dropcaster for Archive.org files?

Does that work well to create a podcast that hosts its files on Archive.org?

Yours,

Robert

Is there a way to support episode images for iTunes?

iTunes allows podcasts to have separate images per episode by setting the <itunes:image href=""/> tag within the episodes <item> tag.

Would be nice if Dropcaster would support something like this, for example by checking for image files with the same name as the episode mp3 file.

Encoding issue

Hi there,

I am unable to process files with unicode names when running in command line mode:

This works dropcaster > index.rss

This does not dropcaster somefilewithunicode*.mp3 and returns
ERROR: Invalid argument @ rb_sysopen - somefilewithunicode1.mp4

Thanks,Jonathan
ruby 2.3.3p222 (2016-11-21 revision 56859) [x64-mingw32] - Win10

else without rescue is useless

computer:~ jdoe$ cd /tmp/files
computer:files jdoe$ ls
channel.yml hpr1143.mp3
computer:files jdoe$
computer:files jdoe$ cat channel.yml
:title: 'All About Everything'
:subtitle: 'A show about everything'
:url: 'http://www.example.com/podcasts/everything/index.html'
computer:files jdoe$
computer:files jdoe$ gem install dropcaster
Fetching: ruby-mp3info-0.8.gem (100%)
Fetching: i18n-0.6.1.gem (100%)
Fetching: multi_json-1.7.2.gem (100%)
Fetching: activesupport-3.2.13.gem (100%)
Fetching: dropcaster-0.0.4.gem (100%)
Successfully installed ruby-mp3info-0.8
Successfully installed i18n-0.6.1
Successfully installed multi_json-1.7.2
Successfully installed activesupport-3.2.13
Successfully installed dropcaster-0.0.4
5 gems installed
Installing ri documentation for ruby-mp3info-0.8...
Installing ri documentation for i18n-0.6.1...
Installing ri documentation for multi_json-1.7.2...
Installing ri documentation for activesupport-3.2.13...
Installing ri documentation for dropcaster-0.0.4...
Installing RDoc documentation for ruby-mp3info-0.8...
Installing RDoc documentation for i18n-0.6.1...
Installing RDoc documentation for multi_json-1.7.2...
Installing RDoc documentation for activesupport-3.2.13...
Installing RDoc documentation for dropcaster-0.0.4...
computer:files jdoe$
computer:files jdoe$ dropcaster
/Users/jdoe/.rvm/gems/ruby-1.9.3-p327/gems/dropcaster-0.0.4/lib/dropcaster/channel.rb:156:
warning: else without rescue is useless
/Users/jdoe/.rvm/rubies/ruby-1.9.3-p327/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in
require': /Users/jdoe/.rvm/gems/ruby-1.9.3-p327/gems/dropcaster-0.0.4/lib/dropcaster/channel.rb:151: syntax error, unexpected ':', expecting keyword_then or ',' or ';' or '\n' (SyntaxError) when nil : nil ^ /Users/jdoe/.rvm/gems/ruby-1.9.3-p327/gems/dropcaster-0.0.4/lib/dropcaster/channel.rb:153: syntax error, unexpected keyword_when, expecting keyword_end when false : 'No' ^ /Users/jdoe/.rvm/gems/ruby-1.9.3-p327/gems/dropcaster-0.0.4/lib/dropcaster/channel.rb:159: syntax error, unexpected keyword_end, expecting $end from /Users/jdoe/.rvm/rubies/ruby-1.9.3-p327/lib/ruby/1.9.1/rubygems/custom_require.rb:36:inrequire'
from /Users/jdoe/.rvm/gems/ruby-1.9.3-p327/gems/dropcaster-0.0.4/lib/dropcaster.rb:15:in <top (required)>' from /Users/jdoe/.rvm/rubies/ruby-1.9.3-p327/lib/ruby/1.9.1/rubygems/custom_require.rb:36:inrequire'
from /Users/jdoe/.rvm/rubies/ruby-1.9.3-p327/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in require' from /Users/jdoe/.rvm/gems/ruby-1.9.3-p327/gems/dropcaster-0.0.4/bin/dropcaster:28:in<top (required)>'
from /Users/jdoe/.rvm/gems/ruby-1.9.3-p327/bin/dropcaster:19:in load' from /Users/jdoe/.rvm/gems/ruby-1.9.3-p327/bin/dropcaster:19:in

'
from /Users/jdoe/.rvm/gems/ruby-1.9.3-p327/bin/ruby_noexec_wrapper:14:in eval' from /Users/jdoe/.rvm/gems/ruby-1.9.3-p327/bin/ruby_noexec_wrapper:14:in'
computer:files jdoe$

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "bundler":
  In Gemfile:
    dropcaster was resolved to 1.1.0, which depends on
      bundler

    guard-bundler was resolved to 3.0.0, which depends on
      bundler (>= 2.1, < 3)

  Current Bundler version:
    bundler (1.17.3)
This Gemfile requires a different version of Bundler.
Perhaps you need to update Bundler by running `gem install bundler`?

Could not find gem 'bundler (>= 2.1, < 3)', which is required by gem 'dropcaster', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "bundler":
  In Gemfile:
    dropcaster was resolved to 1.1.0, which depends on
      bundler

    guard-bundler was resolved to 3.0.0, which depends on
      bundler (>= 2.1, < 3)

  Current Bundler version:
    bundler (1.17.3)
This Gemfile requires a different version of Bundler.
Perhaps you need to update Bundler by running `gem install bundler`?

Could not find gem 'bundler (>= 2.1, < 3)', which is required by gem 'dropcaster', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

Explain in ReadMe which ID3 tags to use

I'd like to be able to find in the Readme of this repo which ID3 tags dropcaster uses to generate XML tags for the RSS file.

For example, for my podcast, I want to set these tags for each item but I don't know which ID3 tags to use:

<description></description>
<itunes:summary></itunes:summary>
<itunes:subtitle></itunes:subtitle>

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "bundler":
  In Gemfile:
    dropcaster was resolved to 1.1.0, which depends on
      bundler

    guard-bundler was resolved to 3.0.0, which depends on
      bundler (>= 2.1, < 3)

  Current Bundler version:
    bundler (1.17.3)
This Gemfile requires a different version of Bundler.
Perhaps you need to update Bundler by running `gem install bundler`?

Could not find gem 'bundler (>= 2.1, < 3)', which is required by gem 'guard-bundler', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

Issue with new version of activesupport

After fresh install of dropcaster I get this error:

Traceback (most recent call last):
	13: from /usr/local/lib/ruby/gems/2.7.0/bin/dropcaster:23:in `<main>'
	12: from /usr/local/lib/ruby/gems/2.7.0/bin/dropcaster:23:in `load'
	11: from /usr/local/lib/ruby/gems/2.7.0/gems/dropcaster-1.1.0/bin/dropcaster:29:in `<top (required)>'
	10: from /usr/local/Cellar/[email protected]/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in `require'
	 9: from /usr/local/Cellar/[email protected]/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in `require'
	 8: from /usr/local/lib/ruby/gems/2.7.0/gems/dropcaster-1.1.0/lib/dropcaster.rb:6:in `<top (required)>'
	 7: from /usr/local/Cellar/[email protected]/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in `require'
	 6: from /usr/local/Cellar/[email protected]/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in `require'
	 5: from /usr/local/lib/ruby/gems/2.7.0/gems/activesupport-6.1.0/lib/active_support/core_ext/date_time/conversions.rb:5:in `<top (required)>'
	 4: from /usr/local/Cellar/[email protected]/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in `require'
	 3: from /usr/local/Cellar/[email protected]/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in `require'
	 2: from /usr/local/lib/ruby/gems/2.7.0/gems/activesupport-6.1.0/lib/active_support/core_ext/time/conversions.rb:6:in `<top (required)>'
	 1: from /usr/local/lib/ruby/gems/2.7.0/gems/activesupport-6.1.0/lib/active_support/core_ext/time/conversions.rb:72:in `<class:Time>'
/usr/local/lib/ruby/gems/2.7.0/gems/activesupport-6.1.0/lib/active_support/core_ext/time/conversions.rb:72:in `alias_method': undefined method `xmlschema' for class `Time' (NameError)

If I manually uninstall activesupport-6.1.0 and install activesupport-6.0.0 all works fine. This issue here seems to be related: rails/rails#40861

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "activesupport":
  In Gemfile:
    dropcaster was resolved to 1.0.0, which depends on
      activesupport

    github-pages was resolved to 197, which depends on
      activesupport (= 4.2.10)

Bundler could not find compatible versions for gem "rouge":
  In Gemfile:
    github-pages was resolved to 197, which depends on
      rouge (= 2.2.1)

    github-pages was resolved to 197, which depends on
      jekyll (= 3.7.4) was resolved to 3.7.4, which depends on
        rouge (>= 1.7, < 4)

Bundler could not find compatible versions for gem "ruby":
  In Gemfile:
    ruby

    github-pages was resolved to 197, which depends on
      activesupport (= 4.2.10) was resolved to 4.2.10, which depends on
        ruby (>= 1.9.3)

    libnotify was resolved to 0.9.4, which depends on
      ffi (>= 1.0.11) was resolved to 1.10.0, which depends on
        ruby (< 2.7.dev) x86-mingw32

    libnotify was resolved to 0.9.4, which depends on
      ffi (>= 1.0.11) was resolved to 1.10.0, which depends on
        ruby (>= 1.9)

    github-pages was resolved to 197, which depends on
      jekyll (= 3.7.4) was resolved to 3.7.4, which depends on
        ruby (>= 2.1.0)

    github-pages was resolved to 197, which depends on
      listen (= 3.1.5) was resolved to 3.1.5, which depends on
        ruby (>= 2.2.3)

    github-pages was resolved to 197, which depends on
      nokogiri (>= 1.8.5, < 2.0) was resolved to 1.10.2, which depends on
        ruby (>= 2.3) x86-mingw32

    github-pages was resolved to 197, which depends on
      nokogiri (>= 1.8.5, < 2.0) was resolved to 1.10.2, which depends on
        ruby (>= 2.3.0)

    rubocop (>= 0.66.0, <= 0.67.2) was resolved to 0.67.2, which depends on
      parser (>= 2.5, != 2.5.1.1) was resolved to 2.6.2.1, which depends on
        ruby (>= 2.0.0)

    rubocop (>= 0.66.0, <= 0.67.2) was resolved to 0.67.2, which depends on
      psych (>= 3.1.0) was resolved to 3.1.0, which depends on
        ruby (< 2.6) x86-mingw32

    rubocop (>= 0.66.0, <= 0.67.2) was resolved to 0.67.2, which depends on
      ruby (>= 2.2.2)

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

You can mention @dependabot in the comments below to contact the Dependabot team.

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "bundler":
  In Gemfile:
    dropcaster was resolved to 1.1.0, which depends on
      bundler

    guard-bundler was resolved to 3.0.0, which depends on
      bundler (>= 2.1, < 3)

  Current Bundler version:
    bundler (1.17.3)
This Gemfile requires a different version of Bundler.
Perhaps you need to update Bundler by running `gem install bundler`?

Could not find gem 'bundler (>= 2.1, < 3)', which is required by gem 'dropcaster', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

enclosure url results in "404 cannot find" when podcatcher tries to download mp3 file

Hi @nerab,

Great tool, just what I was looking for!

I've got one problem: When my podcatcher (BeyondPod) tries to download the mp3 files, it basically receives an html file saying "404 cannot find what you are looking for". When I replace the enclosure urls in index.rss with public links generated by Dropbox (like you do to share index.rss), it does work however.
Am I doing something wrong with Dropbox so that the dropcaster generated enclosure urls don't work? Or did Dropbox change something?

I've attached the html file (as txt), but I guess you get what I mean.
podcast123.mp3.html.txt

Thanks!
Bart

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "bundler":
  In Gemfile:
    dropcaster was resolved to 1.1.0, which depends on
      bundler

    guard-bundler was resolved to 3.0.0, which depends on
      bundler (>= 2.1, < 3)

  Current Bundler version:
    bundler (1.17.3)
This Gemfile requires a different version of Bundler.
Perhaps you need to update Bundler by running `gem install bundler`?

Could not find gem 'bundler (>= 2.1, < 3)', which is required by gem 'dropcaster', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

Unexpected Keyword Syntax Error

I'm on Ubuntu 12. And I'm getting the following error in Dropcaster

$ dropcaster
/usr/local/bin/dropcaster:22:in `load': /var/lib/gems/2.3.0/gems/dropcaster-1.0.0/bin/dropcaster:56: syntax error, unexpected keyword_rescue, expecting keyword_end (SyntaxError)
  rescue StandardError
        ^
	from /usr/local/bin/dropcaster:22:in `<main>'
ygreif@ygreif-OptiPlex-3020:~/Dropbox/Public/hebrew$ dropcaster > index.rss
/usr/local/bin/dropcaster:22:in `load': /var/lib/gems/2.3.0/gems/dropcaster-1.0.0/bin/dropcaster:56: syntax error, unexpected keyword_rescue, expecting keyword_end (SyntaxError)
  rescue StandardError
        ^
	from /usr/local/bin/dropcaster:22:in `<main>'
ygreif@ygreif-OptiPlex-3020:~/Dropbox/Public/hebrew$ dropcaster > index.rss
/usr/local/bin/dropcaster:22:in `load': /var/lib/gems/2.3.0/gems/dropcaster-1.0.0/bin/dropcaster:56: syntax error, unexpected keyword_rescue, expecting keyword_end (SyntaxError)
  rescue StandardError
        ^
	from /usr/local/bin/dropcaster:22:in `<main>'

A warning and two syntax errors

pygmy โžœ ~ dropcaster
DEPRECATION WARNING: this file is deprecated and will be removed. (called from require at /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36)
/home/andrej/.rvm/gems/ruby-2.1.0/gems/dropcaster-0.0.4/lib/dropcaster/channel.rb:156: warning: else without rescue is useless
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in require': /home/andrej/.rvm/gems/ruby-2.1.0/gems/dropcaster-0.0.4/lib/dropcaster/channel.rb:151: syntax error, unexpected ':', expecting keyword_then or ',' or ';' or '\n' (SyntaxError) when nil : nil ^ /home/andrej/.rvm/gems/ruby-2.1.0/gems/dropcaster-0.0.4/lib/dropcaster/channel.rb:153: syntax error, unexpected keyword_when, expecting keyword_end when false : 'No' ^ /home/andrej/.rvm/gems/ruby-2.1.0/gems/dropcaster-0.0.4/lib/dropcaster/channel.rb:159: syntax error, unexpected keyword_end, expecting $end from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:inrequire'
from /home/andrej/.rvm/gems/ruby-2.1.0/gems/dropcaster-0.0.4/lib/dropcaster.rb:15:in <top (required)>' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:inrequire'
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in require' from /home/andrej/.rvm/gems/ruby-2.1.0/gems/dropcaster-0.0.4/bin/dropcaster:28:in<top (required)>'
from /home/andrej/.rvm/gems/ruby-2.1.0/bin/dropcaster:19:in load' from /home/andrej/.rvm/gems/ruby-2.1.0/bin/dropcaster:19:in

'
from /home/andrej/.rvm/gems/ruby-2.1.0/bin/ruby_executable_hooks1.9.1:15:in eval' from /home/andrej/.rvm/gems/ruby-2.1.0/bin/ruby_executable_hooks1.9.1:15:in'

pygmy โžœ ~ gem list

*** LOCAL GEMS ***

activesupport (4.0.2)
atomic (1.1.14)
bundler (1.5.2)
bundler-unload (1.0.2)
dropcaster (0.0.4)
executable-hooks (1.3.1)
gem-wrappers (1.2.4)
i18n (0.6.9)
minitest (4.7.5)
multi_json (1.8.4)
ruby-mp3info (0.8.3)
rubygems-bundler (1.4.2)
rvm (1.11.3.8)
thread_safe (0.1.3)
tzinfo (0.3.38)

Failed to load dropcaster, cannot load octokit

I setup a simple Gemfile

source 'https://rubygems.org' do
  gem 'dropcaster'
end

And installed with Bundler

$ bundle install

But, I get a failed to load error when running dropcaster

$ bundle exec dropcaster
bundler: failed to load command: dropcaster (/usr/local/bundle/bin/dropcaster)
LoadError: cannot load such file -- octokit
  /usr/local/bundle/gems/dropcaster-0.0.7/lib/dropcaster/contributors.rb:1:in `require'
  /usr/local/bundle/gems/dropcaster-0.0.7/lib/dropcaster/contributors.rb:1:in `<top (required)>'
  /usr/local/bundle/gems/dropcaster-0.0.7/lib/dropcaster.rb:13:in `require'
  /usr/local/bundle/gems/dropcaster-0.0.7/lib/dropcaster.rb:13:in `<top (required)>'
  /usr/local/bundle/gems/dropcaster-0.0.7/bin/dropcaster:27:in `require'
  /usr/local/bundle/gems/dropcaster-0.0.7/bin/dropcaster:27:in `<top (required)>'
  /usr/local/bundle/bin/dropcaster:17:in `load'
  /usr/local/bundle/bin/dropcaster:17:in `<top (required)>'

The contributors file in the command source requires a dependency that you currently have marked as a development dependency.

I think it just needs to be moved to the regular dependency set. If I add that specific gem to my Gemfile and reinstall and execute, it works fine.

Cannot require active_support/core_ext/logger

I'm using Ruby 2.2 and the dropcaster CLI command just doesn't seem to work.

$ dropcaster

/usr/local/var/rbenv/versions/2.2.0/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in require': cannot load such file -- active_support/core_ext/logger (LoadError) from /usr/local/var/rbenv/versions/2.2.0/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:inrescue in require'
from /usr/local/var/rbenv/versions/2.2.0/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:39:in require' from /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/dropcaster-0.0.4/lib/dropcaster.rb:10:in<top (required)>'
from /usr/local/var/rbenv/versions/2.2.0/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:69:in require' from /usr/local/var/rbenv/versions/2.2.0/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:69:inrequire'
from /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/dropcaster-0.0.4/bin/dropcaster:28:in <top (required)>' from /usr/local/var/rbenv/versions/2.2.0/bin/dropcaster:23:inload'
from /usr/local/var/rbenv/versions/2.2.0/bin/dropcaster:23:in `

'

links to mp3 files are relative to channel URL, not the dropbox links

Dropcaster sounds way cool - we were thinking it allowed us to host purely out of dropbox, but when we run it we get urls to the mp3s relative to channel URL, not the dropbox links that we were expecting. Are we doing something wrong?

:title: 'Agile Book Club Podcast'
:description: 'AgileVentures.org panelists discussion on selected books and topics relating to agile development, team collaboration, and software engineering.'
:url: 'https://www.agileventures.org'

example from index.rss:

   <item>
      <title>Ep. 5: Agile Book Club podcast - Fifty Quick Ideas to Improve your User Stories by Adzic/Evans</title>
      <itunes:author>AgileVentures.org</itunes:author>
    
      <itunes:subtitle>Episode 5: Sam and Michael discuss the following...</itunes:subtitle>
      <itunes:summary>Episode 5: Sam and Michael discuss the following sections of &quot;Fifty Quick Ideas to Improve your User Stories&quot; by Gojko Adzic and David Evans: 
 
-Put a best before date on stories 
-Set deadlines for addressing major risks</itunes:summary>
    
      <itunes:image href=""/>
      <enclosure url="https://www.agileventures.org/ep._5__agile_book_club_podcast_-_fifty_quick_ideas_to_improve_your_user_stories_by_adzic_evans.mp3" length="31059440" type="audio/mp3"/>
      <link>https://www.agileventures.org/ep._5__agile_book_club_podcast_-_fifty_quick_ideas_to_improve_your_user_stories_by_adzic_evans.mp3</link>
      <guid isPermaLink="false">1fcbf4022f1b93cef9750850b1c758ad54926b01</guid>
      <pubDate>Wed, 17 Jan 2018 13:08:47 +0000</pubDate>
      <itunes:duration>1756</itunes:duration>
    
    </item>

we thought that the link would be to the dropbox link to the mp3 https://www.dropbox.com/s/uc0bap0hjk070c7/ep._5__agile_book_club_podcast_-_fifty_quick_ideas_to_improve_your_user_stories_by_adzic_evans.mp3?dl=0 or is that not how the system works?

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "activesupport":
  In Gemfile:
    dropcaster was resolved to 1.0.0, which depends on
      activesupport (>= 4.2.10, <= 5.2.3)

    github-pages was resolved to 197, which depends on
      activesupport (= 4.2.10)

Bundler could not find compatible versions for gem "rouge":
  In Gemfile:
    github-pages was resolved to 197, which depends on
      rouge (= 2.2.1)

    github-pages was resolved to 197, which depends on
      jekyll (= 3.7.4) was resolved to 3.7.4, which depends on
        rouge (>= 1.7, < 4)

Bundler could not find compatible versions for gem "ruby":
  In Gemfile:
    ruby

    github-pages was resolved to 197, which depends on
      activesupport (= 4.2.10) was resolved to 4.2.10, which depends on
        ruby (>= 1.9.3)

    libnotify was resolved to 0.9.4, which depends on
      ffi (>= 1.0.11) was resolved to 1.10.0, which depends on
        ruby (< 2.7.dev) x86-mingw32

    libnotify was resolved to 0.9.4, which depends on
      ffi (>= 1.0.11) was resolved to 1.10.0, which depends on
        ruby (>= 1.9)

    github-pages was resolved to 197, which depends on
      jekyll (= 3.7.4) was resolved to 3.7.4, which depends on
        ruby (>= 2.1.0)

    github-pages was resolved to 197, which depends on
      listen (= 3.1.5) was resolved to 3.1.5, which depends on
        ruby (>= 2.2.3)

    github-pages was resolved to 197, which depends on
      nokogiri (>= 1.8.5, < 2.0) was resolved to 1.10.2, which depends on
        ruby (>= 2.3) x86-mingw32

    github-pages was resolved to 197, which depends on
      nokogiri (>= 1.8.5, < 2.0) was resolved to 1.10.2, which depends on
        ruby (>= 2.3.0)

    rubocop was resolved to 0.66.0, which depends on
      parser (>= 2.5, != 2.5.1.1) was resolved to 2.6.2.1, which depends on
        ruby (>= 2.0.0)

    rubocop was resolved to 0.66.0, which depends on
      psych (>= 3.1.0) was resolved to 3.1.0, which depends on
        ruby (< 2.6) x86-mingw32

    rubocop was resolved to 0.66.0, which depends on
      psych (>= 3.1.0) was resolved to 3.1.0, which depends on
        ruby (>= 2.2.2)

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

You can mention @dependabot in the comments below to contact the Dependabot team.

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "activesupport":
  In Gemfile:
    dropcaster was resolved to 1.0.0, which depends on
      activesupport

    github-pages was resolved to 197, which depends on
      activesupport (= 4.2.10)

Bundler could not find compatible versions for gem "rouge":
  In Gemfile:
    github-pages was resolved to 197, which depends on
      rouge (= 2.2.1)

    github-pages was resolved to 197, which depends on
      jekyll (= 3.7.4) was resolved to 3.7.4, which depends on
        rouge (>= 1.7, < 4)

Bundler could not find compatible versions for gem "ruby":
  In Gemfile:
    ruby

    github-pages was resolved to 197, which depends on
      activesupport (= 4.2.10) was resolved to 4.2.10, which depends on
        ruby (>= 1.9.3)

    libnotify was resolved to 0.9.4, which depends on
      ffi (>= 1.0.11) was resolved to 1.10.0, which depends on
        ruby (< 2.7.dev) x86-mingw32

    libnotify was resolved to 0.9.4, which depends on
      ffi (>= 1.0.11) was resolved to 1.10.0, which depends on
        ruby (>= 1.9)

    github-pages was resolved to 197, which depends on
      jekyll (= 3.7.4) was resolved to 3.7.4, which depends on
        ruby (>= 2.1.0)

    github-pages was resolved to 197, which depends on
      listen (= 3.1.5) was resolved to 3.1.5, which depends on
        ruby (>= 2.2.3)

    github-pages was resolved to 197, which depends on
      nokogiri (>= 1.8.5, < 2.0) was resolved to 1.10.2, which depends on
        ruby (>= 2.3) x86-mingw32

    github-pages was resolved to 197, which depends on
      nokogiri (>= 1.8.5, < 2.0) was resolved to 1.10.2, which depends on
        ruby (>= 2.3.0)

    rubocop was resolved to 0.66.0, which depends on
      parser (>= 2.5, != 2.5.1.1) was resolved to 2.6.2.1, which depends on
        ruby (>= 2.0.0)

    rubocop was resolved to 0.66.0, which depends on
      psych (>= 3.1.0) was resolved to 3.1.0, which depends on
        ruby (< 2.6) x86-mingw32

    rubocop was resolved to 0.66.0, which depends on
      psych (>= 3.1.0) was resolved to 3.1.0, which depends on
        ruby (>= 2.2.2)

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

You can mention @dependabot in the comments below to contact the Dependabot team.

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "activesupport":
  In Gemfile:
    dropcaster was resolved to 1.0.0, which depends on
      activesupport

    github-pages was resolved to 197, which depends on
      activesupport (= 4.2.10)

Bundler could not find compatible versions for gem "rouge":
  In Gemfile:
    github-pages was resolved to 197, which depends on
      rouge (= 2.2.1)

    github-pages was resolved to 197, which depends on
      jekyll (= 3.7.4) was resolved to 3.7.4, which depends on
        rouge (>= 1.7, < 4)

Bundler could not find compatible versions for gem "ruby":
  In Gemfile:
    ruby

    github-pages was resolved to 197, which depends on
      activesupport (= 4.2.10) was resolved to 4.2.10, which depends on
        ruby (>= 1.9.3)

    libnotify was resolved to 0.9.4, which depends on
      ffi (>= 1.0.11) was resolved to 1.10.0, which depends on
        ruby (< 2.7.dev) x86-mingw32

    libnotify was resolved to 0.9.4, which depends on
      ffi (>= 1.0.11) was resolved to 1.10.0, which depends on
        ruby (>= 1.9)

    github-pages was resolved to 197, which depends on
      jekyll (= 3.7.4) was resolved to 3.7.4, which depends on
        ruby (>= 2.1.0)

    github-pages was resolved to 197, which depends on
      listen (= 3.1.5) was resolved to 3.1.5, which depends on
        ruby (>= 2.2.3)

    github-pages was resolved to 197, which depends on
      nokogiri (>= 1.8.5, < 2.0) was resolved to 1.10.2, which depends on
        ruby (>= 2.3) x86-mingw32

    github-pages was resolved to 197, which depends on
      nokogiri (>= 1.8.5, < 2.0) was resolved to 1.10.2, which depends on
        ruby (>= 2.3.0)

    rubocop (>= 0.66.0, <= 0.67.2) was resolved to 0.67.2, which depends on
      parser (>= 2.5, != 2.5.1.1) was resolved to 2.6.2.1, which depends on
        ruby (>= 2.0.0)

    rubocop (>= 0.66.0, <= 0.67.2) was resolved to 0.67.2, which depends on
      psych (>= 3.1.0) was resolved to 3.1.0, which depends on
        ruby (< 2.6) x86-mingw32

    rubocop (>= 0.66.0, <= 0.67.2) was resolved to 0.67.2, which depends on
      ruby (>= 2.2.2)

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

You can mention @dependabot in the comments below to contact the Dependabot team.

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "jekyll-paginate":
  In Gemfile:
    github-pages was resolved to 193, which depends on
      jekyll-paginate (= 1.1.0)

Could not find gem 'jekyll-paginate (= 1.1.0)', which is required by gem 'github-pages', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

You can mention @dependabot in the comments below to contact the Dependabot team.

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "bundler":
  In Gemfile:
    dropcaster was resolved to 1.1.0, which depends on
      bundler

    guard-bundler was resolved to 3.0.0, which depends on
      bundler (>= 2.1, < 3)

  Current Bundler version:
    bundler (1.17.3)
This Gemfile requires a different version of Bundler.
Perhaps you need to update Bundler by running `gem install bundler`?

Could not find gem 'bundler (>= 2.1, < 3)', which is required by gem 'guard-bundler', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.