As an example of rust-antidote being built:
rust-antidote
[ 66s] ... running 50-check-packaged-twice [ 66s] found conflict of rust-antidote+default-devel-1.0.0-1.1.noarch with rust-antidote-devel-1.0.0-1.1.noarch: [ 66s] - /usr/share/cargo/registry/antidote-1.0.0/Cargo.toml [mode mismatch: g -644 root:root, -644 root:root -> ]
Why are we doing this in the first place? Do we need it? If not, can we get rid of it?
Interesting, it doesn't break on fedora. And I would vote that this is the bug in OBS.
So the %ghost is used to "own" the file which means that dependency generator in this subpackage will run and pull all dependencies. We could just s/%ghost // and it will work, but I don't see point of shipping that files twice or as many times as number of subpackages.
s/%ghost //
This is not specifically an OBS bug, but rather something enforced by openSUSE's build-root policy package (brp-suse) from the post-build-checks package.
brp-suse
post-build-checks
FTR, here's is upstream bug: https://github.com/openSUSE/post-build-checks/issues/24
openSUSE bug was resolved, let's close this here.
Metadata Update from @zbyszek: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.