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.
[1] https://pagure.io/releng/
On Wed, Feb 21, 2018 at 3:18 PM, Sandro Mani 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 non
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.fc
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.
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
wil
