Project

General

Profile

Actions

Bug #34840

open

debian 11 ruby-msgpack conflict

Added by rjhornsby - almost 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Having some trouble adding the Chef capability to Foreman via foreman-installer on a debian bullseye box. This might be an issue with Foreman itself, but it only came up when I tried to add the chef plugin to an already installed Foreman. First, the command:

sudo foreman-installer --enable-foreman-plugin-chef --enable-foreman-plugin-tasks --enable-foreman-proxy-plugin-chef --foreman-proxy-plugin-chef-server-url https://chef.mycorp.com/organizations/mycorp --foreman-proxy-plugin-chef-private-key /etc/foreman/chef.pem --foreman-proxy-plugin-chef-client-name foreman --no-enable-puppet

The error, which repeats a few times with small variations:

2022-04-28 12:59:45 [ERROR ] [configure] Building dependency tree...
2022-04-28 12:59:45 [ERROR ] [configure] Reading state information...
2022-04-28 12:59:45 [ERROR ] [configure] Some packages could not be installed. This may mean that you have
2022-04-28 12:59:45 [ERROR ] [configure] requested an impossible situation or if you are using the unstable
2022-04-28 12:59:45 [ERROR ] [configure] distribution that some required packages have not yet been created
2022-04-28 12:59:45 [ERROR ] [configure] or been moved out of Incoming.
2022-04-28 12:59:45 [ERROR ] [configure] The following information may help to resolve the situation:
2022-04-28 12:59:45 [ERROR ] [configure]
2022-04-28 12:59:45 [ERROR ] [configure] The following packages have unmet dependencies:
2022-04-28 12:59:45 [ERROR ] [configure] ruby-msgpack : Depends: libruby2.5 (>= 2.5.0~preview1) but it is not installable
2022-04-28 12:59:45 [ERROR ] [configure] Depends: ruby (< 1:2.6~) but 1:2.7+2 is to be installed
2022-04-28 12:59:45 [ERROR ] [configure] E: Unable to correct problems, you have held broken packages.
2022-04-28 12:59:45 [ERROR ] [configure] /Stage[main]/Foreman::Plugin::Tasks/Foreman::Plugin[tasks]/Package[ruby-foreman-tasks]/ensure: change from 'purged' to 'present' failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install ruby-foreman-tasks' returned 100: Reading package lists...

Digging into it a bit, there seems to be a conflict or issue with the foreman-provided repo/package. Looking at what versions of ruby-msgpack are available and what repos they call home:

$ apt-cache showpkg ruby-msgpack
Package: ruby-msgpack
Versions:
1.4.2-1 (/var/lib/apt/lists/deb.theforeman.org_dists_buster_3.2_binary-amd64_Packages)
 Description Language:
                 File: /var/lib/apt/lists/deb.theforeman.org_dists_buster_3.2_binary-amd64_Packages
                  MD5: 86998bd8d920b80295c0c648705c6a7d

1.1.0-2+b1 (/var/lib/apt/lists/http.us.debian.org_debian_dists_bullseye_main_binary-amd64_Packages)
 Description Language:
                 File: /var/lib/apt/lists/http.us.debian.org_debian_dists_bullseye_main_binary-amd64_Packages
                  MD5: 474edfed036cd285dcb54ad2f766082e
 Description Language: en
                 File: /var/lib/apt/lists/http.us.debian.org_debian_dists_bullseye_main_i18n_Translation-en
                  MD5: 474edfed036cd285dcb54ad2f766082e

ruby-msgpack=1.1.0-2+b1 installs fine, but trying to apt install ruby-msgpack (regardless of 1.1.0 installed or not) without a specific version target (assumes latest?) fails with the same error message as above.

No data to display

Actions

Also available in: Atom PDF