Conflicting gem dependencies on vanilla logstash 2.1.1 install

Open

#8 opened on Jan 6, 2016 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 35/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: ruby
Domain: devops

Research direction

Start by reproducing bin/plugin install logstash-input-github on the Logstash 2.1.1 tarball and review the reported Bundler conflicts for logstash-codec-plain and logstash. No files or tests are named; done means the plugin installs successfully on the affected vanilla Logstash version without incompatible dependency errors.

Written by the indexing model from the issue text.

Description

bug

When trying to install this plugin onto logstash 2.1.1 (other versions may be affected, haven't checked) bin/plugin install logstash-input-github fails with:

Validating logstash-input-github
Installing logstash-input-github
Plugin version conflict, aborting
ERROR: Installation Aborted, message: Bundler could not find compatible versions for gem "logstash-codec-plain":
  In snapshot (Gemfile.lock):
    logstash-codec-plain (= 2.0.2)

  In Gemfile:
    logstash-output-http (>= 0) java depends on
      logstash-mixin-http_client (< 3.0.0, >= 2.0.2) java depends on
        logstash-codec-plain (>= 0) java

... lots of lines truncated for readability ...

Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.
Bundler could not find compatible versions for gem "logstash":
  In Gemfile:
    logstash-input-github (>= 0) java depends on
      logstash (< 2.0.0, >= 1.4.0) java
Could not find gem 'logstash (< 2.0.0, >= 1.4.0) java', which is required by gem 'logstash-input-github (>= 0) java', in any of the sources.

To reproduce this, just download the 2.1.1 tarball and try the plugin install command, similar failures should follow.

Dominant language: Ruby
Stars: 18
Forks: 17
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

Gateway 3.16 Linux install: GPG key URL 404s (public_keys has no "316" entry, falls back to legacy key) Open

user-reported

Difficulty 2/5 1-3 hours Newbie friendliness 85/100

Kong/developer.konghq.com#7316 · Opened Sep 22, 2026
Semantic HTML: Further explain how landmark elements should be used Open

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

TheOdinProject/curriculum#31408 · Opened Sep 21, 2026
allow @haven.hackclub.com emails for `support_email` Open

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

hackclub/attend#144 · Opened Sep 21, 2026
CI: json 3.0.2 removed `quirks_mode`, breaking ActiveSupport's JSON encoder on every test job Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

bensheldon/good_job#1816 · 5 comments · Opened Sep 21, 2026
URI label indexer writes to _label_tesim instead of _tesim Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

notch8/utk_knapsack#148 · Opened Sep 21, 2026

More Ruby issues