Bug 1658498 - glibc-headers.i686 update is broken in Fedora 28 x86-64
Summary: glibc-headers.i686 update is broken in Fedora 28 x86-64
Keywords:
Status: CLOSED DUPLICATE of bug 1652872
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: 28
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Carlos O'Donell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-12 10:04 UTC by Artem S. Tashkinov
Modified: 2018-12-12 10:31 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-12-12 10:31:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Artem S. Tashkinov 2018-12-12 10:04:29 UTC
dnf update 'glibc*'
Last metadata expiration check: 0:05:42 ago on Wed 12 Dec 2018 02:56:56 PM +05.
Dependencies resolved.

 Problem: cannot install both glibc-headers-2.27-35.fc28.x86_64 and glibc-headers-2.27-32.fc28.x86_64
  - glibc-headers-2.27-32.fc28.i686 has inferior architecture
  - cannot install the best update candidate for package glibc-headers-2.27-32.fc28.x86_64
  - problem with installed package glibc-headers-2.27-32.fc28.i686
================================================================================
 Package              Arch          Version                Repository      Size
================================================================================
Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
 glibc-headers        x86_64        2.27-35.fc28           updates        460 k

Transaction Summary
================================================================================
Skip  1 Package

Nothing to do.
Complete!

Comment 1 Artem S. Tashkinov 2018-12-12 10:05:31 UTC
I mentioned the issue a week ago: https://bugzilla.redhat.com/show_bug.cgi?id=1652872#c13

Comment 2 Florian Weimer 2018-12-12 10:31:17 UTC

*** This bug has been marked as a duplicate of bug 1652872 ***


Note You need to log in before you can comment on or make changes to this bug.