First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 136553
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Toolchain Maintainers <toolchain@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Cory Grunden <cory.grunden@gmail.com>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 136553 depends on: Show dependency tree
Bug 136553 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2006-06-12 09:27 0000
Looks like binutils-2.17.05.02 was released a bit too early, because
binutils-2.16.94 was released this morning.  Wouldn't the version differences
cause a problem?  Also, it looks like the --as-needed fixes were merged into
2.16.94.

------- Comment #1 From SpanKY 2006-06-14 21:23:13 0000 -------
no, 2.17.xxx is taken from a different cvs branch than 2.16.9x

------- Comment #2 From SpanKY 2006-06-14 22:07:17 0000 -------
in portage

------- Comment #3 From Cory Grunden 2006-06-15 11:20:20 0000 -------
No, binutils-2.16.9x are the prereleases of binutils-2.17.  binutils-2.17.05.02
came from ftp.kernel.org long before binutils-2.16.94 was released.  So
logically binutils-2.17.05.02 version doesn't make any sense.

------- Comment #4 From Cory Grunden 2006-06-15 11:23:56 0000 -------
binutils-2.17.05.02 = binutils 2006 0526 in CVS on sources.redhat.com
binutils-2.16.94    = binutils 2006 0612 in CVS on sources.redhat.com

------- Comment #5 From SpanKY 2006-06-15 11:27:17 0000 -------
wrong

binutils-2.17.xx and 2.16.9x are taken from different cvs trees

------- Comment #6 From Harald van Dijk 2006-06-15 11:33:21 0000 -------
It's nice to have an ebuild for 2.16.94, but with the current eclass's SRC_URI
emerge can't find the sources. 2.16.94 isn't available on any GNU mirror (I had
to download it manually from sourceware.org), and the patchsets don't seem to
be available on any Gentoo mirrors, even distfiles.gentoo.org (and these I
don't even know where to get elsewhere)

------- Comment #7 From SpanKY 2006-06-15 12:36:11 0000 -------
looks like i uploaded the patchsets but forgot to move them out of my ~

should be available now

as for the binutils snapshot, ive mirrored that on gentoo infra already

------- Comment #8 From Harald van Dijk 2006-06-15 22:40:12 0000 -------
Okay, now binutils-2.16.94-patches-1.0.tar.bz2 can be downloaded, but...

>>> Downloading ftp://gentoo.mirrored.ca/distfiles/binutils-2.16.94-patches-1.0.tar.bz2
--07:40:20-- 
ftp://gentoo.mirrored.ca/distfiles/binutils-2.16.94-patches-1.0.tar.bz2
           => `/var/dist/binutils-2.16.94-patches-1.0.tar.bz2'
Resolving gentoo.mirrored.ca... 142.77.49.225
Connecting to gentoo.mirrored.ca|142.77.49.225|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done.    ==> PWD ... done.
==> TYPE I ... done.  ==> CWD /distfiles ... done.
==> PASV ... done.    ==> RETR binutils-2.16.94-patches-1.0.tar.bz2 ... done.
Length: 8,685 (8.5K) (unauthoritative)

100%[===================================================================>]
8,685         --.--K/s             

07:40:21 (66.33 KB/s) - `/var/dist/binutils-2.16.94-patches-1.0.tar.bz2' saved
[8685]

('Filesize does not match recorded size', 8685L, 7906)
!!! Fetched file: binutils-2.16.94-patches-1.0.tar.bz2 VERIFY FAILED!
!!! Reason: Filesize does not match recorded size
!!! Got:      Filesize does not match recorded size
!!! Expected: 8685
Removing corrupt distfile...

happens with all mirrors. (The error message is obviously incorrect, I'll file
a separate bug on that.)

------- Comment #9 From SpanKY 2006-06-17 00:13:04 0000 -------
looks like portage has problems updating digests properly ... fixed in cvs now

First Last Prev Next    No search results available      Search page      Enter new bug