This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug build/19813] Failure when cross-testing using cross-test-ssh.sh
- From: "joseph at codesourcery dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 15 Mar 2016 16:08:20 +0000
- Subject: [Bug build/19813] Failure when cross-testing using cross-test-ssh.sh
- Auto-submitted: auto-generated
- References: <bug-19813-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19813
--- Comment #8 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Tue, 15 Mar 2016, martin.galvan at tallertechnologies dot com wrote:
> Odd. I was using the 2.23 release from http://ftp.gnu.org/gnu/libc/; I thought
> it would stay in sync with the 2.23 branch. In any case, I'll test it with
> master and let you know what happens. Thanks.
A release tarball should always be a fixed byte sequence; it should never
change after release. glibc doesn't do point releases, such as 2.23.1, at
present.
--
You are receiving this mail because:
You are on the CC list for the bug.