Bug 1410811 - ppc64 gcc package deps screwy
Summary: ppc64 gcc package deps screwy
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: 25
Hardware: ppc64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-06 14:46 UTC by Jeremy Harris
Modified: 2017-01-06 15:34 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-06 15:05:12 UTC
Type: Bug


Attachments (Terms of Use)

Description Jeremy Harris 2017-01-06 14:46:14 UTC
Description of problem:

$ uname -a
Linux localhost.localdomain 4.8.6-300.fc25.ppc64 #1 SMP Wed Nov 2 16:26:34 UTC 2016 ppc64 ppc64 ppc64 GNU/Linux

$ sudo dnf install gcc-6.2.1-2.fc25.ppc64
Last metadata expiration check: 1:12:24 ago on Fri Jan  6 13:31:33 2017.
Error: nothing provides glibc-devel >= 2.2.90-12 needed by gcc-6.2.1-2.fc25.ppc64

Comment 1 Jakub Jelinek 2017-01-06 14:51:43 UTC
There is nothing wrong on that dependency.  Should be satisfied by
glibc-devel-2.24-*.ppc64, e.g.
https://ppc.koji.fedoraproject.org/packages/glibc/2.24/4.fc25/ppc64/
whatever is the latest.

Comment 2 Jeremy Harris 2017-01-06 15:00:00 UTC
Excuse me?  The whole point is the "Error: nothing provides glibc-devel".


If I ask for the toplevel version you suggest:
$ sudo dnf install glibc-devel-2.24 
Last metadata expiration check: 1:26:25 ago on Fri Jan  6 13:31:33 2017.
No package glibc-devel-2.24 available.
Error: Unable to find a match.
$

Comment 3 Jakub Jelinek 2017-01-06 15:05:12 UTC
Then something screwed up the metadata or you are using some broken mirror.  glibc-devel package certainly is in:
https://download.fedoraproject.org/pub/fedora-secondary/releases/25/Server/ppc64/os/Packages/g/

Comment 4 Jeremy Harris 2017-01-06 15:06:37 UTC
gosh, what a pleasant experience

Comment 5 Jonathan Wakely 2017-01-06 15:25:03 UTC
What are you expecting? There's no bug in the GCC package. glibc 2.2.90-12 is *ancient* and will be satisfied by any glibc in the past decade. So if it can't be resolved then either your repo is borked and doesn't have any glibc-devel at all, or DNF is having issues. Neither is a problem with the gcc package deps.

Comment 6 Jeremy Harris 2017-01-06 15:27:47 UTC
I'm expecting to be able to install a fresh ppc VM, install a gcc on it, and
use it for development.  It doesn't work.  Oh well, I'll try elsewhere then.
Please note: I did not change any repo settings.  What was installed is what I
have.

Comment 7 Jakub Jelinek 2017-01-06 15:34:08 UTC
Package maintainers don't have access to the Fedora release infrastructure, nor mirrors, the CLOSED NOTABUG means there is no bug on the side of the gcc package (nor glibc).  If there is a problem with some mirror, try using a different mirror, if you get the same bug even when using the mirror master, file a ticket with fedora release engineering, or wait a day if it isn't resolved during next update of the metadata?


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