fedora-ci / general

#335 libtool check-conflicts-x86_64 resolution
Opened by fberat. Modified

Open
Close Issue

Hello,

The libtool package has a permanently failing test from the CI, that we'd like to solve.
Specifically, we are looking at the following conflict "regressions" for libtool:

Undeclared file conflicts:
libtool-2.4.7-1.fc37.i686 provides /usr/bin/libtool which is also provided by libtool-2.4.7-1.fc37.x86_64
libtool-2.4.7-1.fc37.i686 provides /usr/bin/libtoolize which is also provided by libtool-2.4.7-1.fc37.x86_64
libtool-2.4.7-1.fc37.i686 provides /usr/share/man/man1/libtool.1.gz which is also provided by libtool-2.4.7-1.fc37.x86_64
libtool-2.4.7-1.fc37.x86_64 provides /usr/bin/libtool which is also provided by libtool-2.4.7-1.fc37.i686
libtool-2.4.7-1.fc37.x86_64 provides /usr/bin/libtoolize which is also provided by libtool-2.4.7-1.fc37.i686
libtool-2.4.7-1.fc37.x86_64 provides /usr/share/man/man1/libtool.1.gz which is also provided by libtool-2.4.7-1.fc37.i686

This can be solved with some effort. We are trying to decide if the effort is worth the value for Fedora. Today the packages are not co-installable on a normal system (dnf does not show libtool.i686 as installable, this may be a compose restriction).
Should the test be adjusted to check for dnf co-installability?
Should we exclude the test for libtool?
How do we verify that libtool is indeed being excluded from the repository composition such that it would be safe to turn the test off?

@msrb is now somebody looking more into rpmdeplint from OSCI?

Metadata Update from @mvadkert:
- Issue tagged with: rpmdeplint

@fberat sounds like the fact that dnf does not show libtool.i686 as installable, this may be a compose restriction should be something the tool should be able to work with.

@jkaluza any idea how this works in Fedora, is it similar to RHEL?

@msrb is now somebody looking more into rpmdeplint from OSCI?

Not actively.

This problem exists downstream as well. We query product listing for the information about shipped packages. But of course PL is populated only after compose has been created. It would be great if we could tell which RPMs will be shipped before we create a compose.
Or, if nothing else, we need to find some alternative to PL in Fedora. Let's wait for @jkaluza here.
Edited by msrb
Metadata
None

rpmdeplint

None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.