[bug-notifications] [gcc4core 0004955]: binutils build failed with checksum error.
Mantis Bug Tracker
noreply at opencsw.org
Mon Jun 11 23:07:58 CEST 2012
The following issue requires your FEEDBACK.
======================================================================
https://www.opencsw.org/mantis/view.php?id=4955
======================================================================
Reported By: tjyang
Assigned To: maciej
======================================================================
Project: gcc4core
Issue ID: 4955
Category: packaging
Reproducibility: always
Severity: block
Priority: normal
Status: feedback
======================================================================
Date Submitted: 2012-06-11 22:07 CEST
Last Modified: 2012-06-11 23:07 CEST
======================================================================
Summary: binutils build failed with checksum error.
Description:
please fix the checksum value in central repository.
bash-3.00# svn info
Path: .
Working Copy Root Path: /root/opencsw
URL:
https://gar.svn.sourceforge.net/svnroot/gar/csw/mgar/pkg/binutils/trunk
Repository Root: https://gar.svn.sourceforge.net/svnroot/gar
Repository UUID: d3b55034-1cff-0310-a425-aefe953e1e90
Revision: 18330
Node Kind: directory
Schedule: normal
Last Changed Author: dmichelsen
Last Changed Rev: 16916
Last Changed Date: 2012-01-26 07:25:13 -0600 (Thu, 26 Jan 2012)
bash-3.00#
cd /root/opencsw/binutils/trunk;mgar build
======================================================================
----------------------------------------------------------------------
(0009918) maciej (manager) - 2012-06-11 23:07
https://www.opencsw.org/mantis/view.php?id=4955#c9918
----------------------------------------------------------------------
I checked this file:
http://ftp.gnu.org/gnu/binutils/binutils-2.21.1.tar.bz2
And it indeed has a different checksum than the one from which we built the
packages.
bde820eac53fa3a8d8696667418557ad upstream at the moment
a22801a9cad45c85e9ff6afc10537d72 our archives
There are slight differences between the two files. In any case, I bumped
up the version to 2.22. I'll see if it builds if it does, I'll push it out
to unstable.
More information about the bug-notifications
mailing list