docker / docker/docker-ce-packaging
rpm: "Missing build-id" and "`%changelog` is missing" warnings
Open
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 209
- Forks
- 164
- Avg merge
- 2h 24m
- Merged PRs (30d)
- 4
Description
Seeing some warnings while building for Fedora 37 (using docker-ce-packaging at https://github.com/docker/docker-ce-packaging/commit/153875c148795fa5e266165dbf5cf328a4925ab7).
make DOCKER_CLI_REF=v23.0.0-rc.2 DOCKER_ENGINE_REF=v23.0.0-rc.2 VERSION=23.0.0-rc.2 fedora-37
...
RPM build warnings:
line 57: It's not recommended to have unversioned Obsoletes: Obsoletes: docker-ce-selinux
line 58: It's not recommended to have unversioned Obsoletes: Obsoletes: docker-engine-selinux
line 59: It's not recommended to have unversioned Obsoletes: Obsoletes: docker-engine
source_date_epoch_from_changelog set but %changelog is missing
Missing build-id in /root/rpmbuild/BUILDROOT/docker-ce-23.0.0~rc.2-1.fc37.aarch64/usr/bin/docker-proxy
source_date_epoch_from_changelog set but %changelog is missing
source_date_epoch_from_changelog set but %changelog is missing
source_date_epoch_from_changelog set but %changelog is missing
Missing build-id in /root/rpmbuild/BUILDROOT/docker-buildx-plugin-0.10.0-1.fc37.aarch64/usr/libexec/docker/cli-plugins/docker-buildx
source_date_epoch_from_changelog set but %changelog is missing
Missing build-id in /root/rpmbuild/BUILDROOT/docker-compose-plugin-2.15.1-1.fc37.aarch64/usr/libexec/docker/cli-plugins/docker-compose
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reproducing the Fedora 37 build with the reported make command and commit reference. Trace the RPM packaging inputs that produce the missing build-id and absent %changelog warnings, then verify any change by rebuilding the affected packages and checking whether the warnings remain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100