Hi
I've received a bug report from a user reporting broken dependencies when updating apitrace in F27. Upon closer investigation I found out that on F27
# dnf install --refresh apitrace-libs.i686
will give you apitrace-libs-7.1-7.fc27.i686, whereas
# dnf install --refresh apitrace-libs
will give you apitrace-libs-7.1-9.fc27.x86_64. This means that a user with currently installed apitrace-7.1-7.x84_64, apitrace-libs-7.1-7.x86_64 and apitrace-libs-7.1-7.i686 is currently getting broken dependencies when updating:
# dnf update [...] Problem 1: package apitrace-libs-7.1-7.fc27.i686 requires apitrace = 7.1-7.fc27, but none of the providers can be installed - cannot install both apitrace-7.1-9.fc27.x86_64 and apitrace-7.1-7.fc27.x86_64 - cannot install both apitrace-7.1-7.fc27.x86_64 and apitrace-7.1-9.fc27.x86_64 - cannot install the best update candidate for package apitrace-libs-7.1-7.fc27.i686 - cannot install the best update candidate for package apitrace-7.1-7.fc27.x86_64 Problem 2: problem with installed package apitrace-libs-7.1-7.fc27.i686 - apitrace-libs-7.1-7.fc27.i686 has inferior architecture - cannot install both apitrace-libs-7.1-9.fc27.x86_64 and apitrace-libs-7.1-7.fc27.x86_64 - cannot install both apitrace-libs-7.1-7.fc27.x86_64 and apitrace-libs-7.1-9.fc27.x86_64 - cannot install the best update candidate for package apitrace-libs-7.1-7.fc27.x86_64 [...]
Where should I submit a ticket for this?
Thanks Sandro
On Wednesday, February 21, 2018 1:34:48 PM CET Sandro Mani wrote:
# dnf update [...] Problem 1: package apitrace-libs-7.1-7.fc27.i686 requires apitrace = 7.1-7.fc27, but none of the providers can be installed
- cannot install both apitrace-7.1-9.fc27.x86_64 and
apitrace-7.1-7.fc27.x86_64 .... Where should I submit a ticket for this?
$ rpm -qi apitrace-libs | grep -i source Source RPM : apitrace-7.1-9.fc27.src.rpm
-> open a bug against apitrace component.
Pavel
On 21.02.2018 15:16, Pavel Raiskup wrote:
On Wednesday, February 21, 2018 1:34:48 PM CET Sandro Mani wrote:
# dnf update [...] Problem 1: package apitrace-libs-7.1-7.fc27.i686 requires apitrace = 7.1-7.fc27, but none of the providers can be installed - cannot install both apitrace-7.1-9.fc27.x86_64 and apitrace-7.1-7.fc27.x86_64 .... Where should I submit a ticket for this?
$ rpm -qi apitrace-libs | grep -i source Source RPM : apitrace-7.1-9.fc27.src.rpm
-> open a bug against apitrace component.
Uhm I'm the maintainer of apitrace, forgot to mention that. But this highlights my point I suppose, the newest SRPM in F27 is -9, but apitrace-libs.i686 is still at -7.
Thanks Sandro
On Wed, Feb 21, 2018 at 3:18 PM, Sandro Mani manisandro@gmail.com wrote:
On 21.02.2018 15:16, Pavel Raiskup wrote:
On Wednesday, February 21, 2018 1:34:48 PM CET Sandro Mani wrote:
# dnf update [...] Problem 1: package apitrace-libs-7.1-7.fc27.i686 requires apitrace = 7.1-7.fc27, but none of the providers can be installed - cannot install both apitrace-7.1-9.fc27.x86_64 and apitrace-7.1-7.fc27.x86_64 .... Where should I submit a ticket for this?
$ rpm -qi apitrace-libs | grep -i source Source RPM : apitrace-7.1-9.fc27.src.rpm
-> open a bug against apitrace component.
Uhm I'm the maintainer of apitrace, forgot to mention that. But this highlights my point I suppose, the newest SRPM in F27 is -9, but apitrace-libs.i686 is still at -7.
I believe this means the compose wasn't done correctly (apitrace-libs was considered multilib initially, and is not considered multilib now). You can file a ticket for releng: https://pagure.io/releng
On 26.02.2018 13:06, Kamil Paral wrote:
I believe this means the compose wasn't done correctly (apitrace-libs was considered multilib initially, and is not considered multilib now). You can file a ticket for releng: https://pagure.io/releng
Done [1], thanks.
devel@lists.stg.fedoraproject.org