inconsistent/absent chef packages in jammy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chef (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Hi,
There is no chef package in jammy. To install chef I've kept a focal sources.list file around.
$ apt-cache policy chef
chef:
Installed: 15.8.25.
Candidate: 15.8.25.
Version table:
*** 15.8.25.
500 http://
100 /var/lib/
But there is a ruby-chef-config package
$ apt-cache policy ruby-chef-config
ruby-chef-config:
Installed: 15.8.25.
Candidate: 16.12.3-2
Version table:
16.12.3-2 500
500 http://
500 http://
*** 15.8.25.
500 http://
100 /var/lib/
But this gets a bit in the way because chef from focal is not compatible with the ruby-chef-config package from jammy. So in fact the ruby-chef-config package in jammy should be removed as long as there is no chef package. Also ohai
(Related but tangential: I had to downgrade some chef related package to the focal versions and put them on old to get the focal chef to work:
ohai hold
ruby-chef-config hold
ruby-chef-utils hold
ruby-net-sftp hold
ruby-uuidtools hold
)
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chef 15.8.25.
ProcVersionSign
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: KDE
Date: Thu Apr 28 10:18:33 2022
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-07-18 (1744 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitec
SourcePackage: chef
UpgradeStatus: Upgraded to jammy on 2022-04-28 (0 days ago)
Thanks for reporting.
It looks like the chef package was removed from Debian (and in turn Ubuntu) due to trademark issues. See https:/ /launchpad. net/ubuntu/ +source/ chef/+publishin ghistory and https:/ /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 963750 for more details.