Re: Primary F20 perl update to 5.18.4 means F20 netinst is now broken
On Wednesday, February 18, 2015, 5:12:58 PM, I wrote:
On Sunday, February 15, 2015, 11:53:04 AM, I wrote:
> Folks,
> It's great to see the ppc64 builds are back up -
rawhide, and
> branches!
> I'm slowly working towards getting the ppc64 install
components
> updated to work with Mac G5s. Lots to learn!
> I went to set up a new build machine yesterday, and found
that an
> update to Perl 5.18.4 on the primary arch has resulted in new noarch
> Perl packages being copied from primary to ppc64 that have
> dependencies that can't be satisfied by the 5.18.2 current build for
> ppc64.
> I opened https://bugzilla.redhat.com/show_bug.cgi?id=1192824
> "F20 PPC64 Perl: Now 5.18.2 but primary is now 5.18.4 - updated noarch
> package deps prevent network installs".
> Because the F20 Anaconda keeps insisting on using the updates
during
> installs and the DVD install does not (yet) work for Macs, I can't
> really work around this until Perl gets built for the new level.
Karsten Hopp built a new perl-5.18.4-290.fc20 on 2015-02-17
at
23:57:37 that Koji believes is successful.
I attempted another install, but the error persists. The F20
updates
repo probably needs to be updated with the new version.
Peter did the update, and the Perl 5.18.4 files are now on the ppc64
F20 master and shadow disks.
Unfortunately, we have a case of "One step forward, one step back:.
Forward: The perl 5.18.4 issue is now resolved.
Backward: A new ppc64 F20 dependency issue.
I select the Mate desktop, and C development tools.
Anaconda is happy enough to reach the point of formatting the disks, and
begin the installation process. "Starting package installation process"
is displayed. I get a new pop-up with:
"glibc-2.18-11.fc20.ppc requires glibc-common = 2.18-11.fc20
It is annoying that this was not caught in the earlier dependency check,
but that is likely an anaconda or packaging issue.
http://dl.fedoraproject.org/pub/fedora-secondary/updates/20/ppc64/
has the following glibc packages:
glibc-2.18-16.fc20.ppc64.rpm 2015-02-24 18:47 4.7M
glibc-2.18-16.fc20.ppc64p7.rpm 2015-02-24 18:45 3.7M
glibc-common-2.18-16.fc20.ppc64.rpm 2015-02-24 19:05 11M
glibc-common-2.18-16.fc20.ppc64p7.rpm 2015-02-24 18:48 11M
glibc-devel-2.18-16.fc20.ppc64.rpm 2015-02-24 18:55 1.0M
glibc-devel-2.18-16.fc20.ppc64p7.rpm 2015-02-24 19:03 1.0M
glibc-headers-2.18-16.fc20.ppc64.rpm 2015-02-24 18:55 637K
glibc-headers-2.18-16.fc20.ppc64p7.rpm 2015-02-24 19:03 636K
glibc-static-2.18-16.fc20.ppc64.rpm 2015-02-24 19:01 1.6M
glibc-static-2.18-16.fc20.ppc64p7.rpm 2015-02-24 18:53 1.6M
glibc-utils-2.18-16.fc20.ppc64.rpm 2015-02-24 18:53 190K
glibc-utils-2.18-16.fc20.ppc64p7.rpm 2015-02-24 19:06 190K
These match the packages at:
http://ppc.koji.fedoraproject.org/tree/updates/20/ppc64/
http://dl.fedoraproject.org/pub/fedora-secondary/updates/testing/20/ppc64/
has no glibc packages
As this is no longer a Perl problem, I've mark this bz as closed
(With WORKSFORME as the resolution), and will follow up as required
to get this new problem resolved.
My first guess is we've got another package that needs to be rebuilt
to match the new glibc. I'll try the install later tonight with just
Mate (no C development group) and see what happens.