© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hi Steve,
I was the community member from the Cinc Project that brought this to attention. This problem is even worse for users who currently pull in Chef from upstream as reported on our Slack earlier today:
"So not only is cinc-as-chef part of Ubuntu 20 as above, but I also can't get it to stop getting installed every ~night. sudo apt-get remove -y ohai chef chef-bin chef-zero ruby-chef-config ruby-chef-utils, then we install the stuff we want from our licensed packages, the next morning all of the Ubuntu cinc-as-chef stuff is back! I even tried sudo apt-mark hold chef and it all came back"
So from a user perspective, it looks like they are installing a proper Chef package from upstream when they are not. And even if they manually install the licensed Chef package, the Ubuntu package overrides it. This is a major issue not only from a licensing/trademark point of view, but also from a user point of view.
IMO the the chef package should be renamed to cinc and should have all of the proper trademark changes we include to be compliant with the Chef Trademark Policy [1]. The Debian maintainer has already opened up an issue on our upstream repository to work on providing a proper source package, however it's going to take a bit more work than that to get a proper package built the "Debian/Ubuntu Way".
Feel free to reach out to me as well as a community member of the Cinc Project.
[1] https:/