Comments (2)
Chef Infra Client's 17.1.35 (2021-05-11) and Chef Workstation's 21.8.555 (2021-08-03) were the first stable versions of the products to get built on RHEL 8. RHEL 8 systems store a package's build-id files in /usr/lib/.build-id
. Omnibus was packaging the build-id files into the rpm package. Chef Infra Client and Chef Workstation happen to have some identiacl build-ids which created the conflict. These files are only beneficial for debugging purposes so we don't need to include them in the rpm package. Once this omnibus PR gets merged and new versions of Chef Infra and Chef Workstation use it to build packages those build-id files won't be included in the rpm package so we shouldn't see this problem again.
from omnibus.
It might be possible to clean up that dotfile from the build, but somewhat more importantly we shouldn't be shipping anything at all in /usr/lib and the fact that gets picked up seems horribly wrong and smells like other bugs have crept into omnibus.
from omnibus.
Related Issues (20)
- Apple M1 Support HOT 1
- Mixlib::ShellOut::InvalidCommandOption: option ':lockdir' is not a valid option for Mixlib::ShellOut HOT 2
- HealthCheck is busted on FreeBSD, Solaris and AIX HOT 2
- Omnibus needs an integration environment with Solaris/FreeBSD/AIX/Windows that checks the healthcheck HOT 1
- Old code exceptions in HealthCheck should likely be deleted HOT 1
- Update Packager spec to avoid failures after March 2022
- macOS healthcheck checks dylib install ID as if it was a dependency HOT 1
- omnibus build certificate verify failed (certificate has expired)
- omnibus does not support rockylinux HOT 1
- Source code of chef-cleanroom gem not available
- Timestamp servers listed in \packagers are no longer available?
- Allow to add recommended dependencies
- Releases are not publishing to rubygems.org HOT 1
- Portable health checks
- `append_timestamp` doesn't really exist HOT 1
- omnibus always tries to mkdir /opt/$PROJECT
- kitchen docs are... not correct
- Fully deprecate the usage of chef-sugar HOT 1
- Concurrency issues if two software definitions have the same source directory HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from omnibus.