Your message dated Tue, 4 Mar 2008 19:04:46 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#462226: coreutils: FTBFS on mips: tests failed:
rm/deep-1, rm/dangling-symlink, ...
has caused the Debian Bug report #462226,
regarding coreutils: FTBFS on mips: tests failed: rm/deep-1,
rm/dangling-symlink, ...
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
462226: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462226
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: coreutils
Version: 6.10-1
Severity: serious
Hi,
coreutils 6.10-1 failed to build on mips:
> Making check in rm
> make[3]: Entering directory
> `/build/buildd/coreutils-6.10/build-tree/coreutils-6.10/tests/rm'
> /usr/bin/make check-TESTS
> make[4]: Entering directory
> `/build/buildd/coreutils-6.10/build-tree/coreutils-6.10/tests/rm'
> make[5]: Entering directory
> `/build/buildd/coreutils-6.10/build-tree/coreutils-6.10/tests/rm'
> FAIL: deep-1.log
> SKIP: hash.log
> FAIL: dangling-symlink.log
> FAIL: v-slash.log
> PASS: i-never.log
> FAIL: fail-eacces.log
> SKIP: one-file-system.log
> PASS: ignorable.log
> FAIL: readdir-bug.log
> FAIL: empty-inacc.log
> PASS: dir-nonrecur.log
> FAIL: dot-rel.log
> FAIL: inaccessible.log
> FAIL: unread3.log
> SKIP: no-give-up.log
> FAIL: dir-no-w.log
> PASS: empty-name.log
> SKIP: fail-2eperm.log
> FAIL: cycle.log
> PASS: i-no-r.log
> PASS: fail-eperm.log
> FAIL: rm1.log
> FAIL: rm2.log
> FAIL: rm3.log
> PASS: rm4.log
> FAIL: rm5.log
> FAIL: unread2.log
> FAIL: r-1.log
> FAIL: r-2.log
> FAIL: r-3.log
> PASS: r-4.log
> PASS: i-1.log
> FAIL: ir-1.log
> PASS: f-1.log
> PASS: sunos-1.log
> FAIL: unreadable.log
> FAIL: interactive-always.log
> FAIL: interactive-once.log
> FAIL: isatty.log
>
> ===========================================
> 24 of 39 tests failed
> (4 tests were not run)
> See tests/rm/test-suite.log
> Please report it to [EMAIL PROTECTED]
> ===========================================
Log:
http://buildd.debian.org/fetch.cgi?pkg=coreutils;ver=6.10-1;arch=mips;stamp=1201066231
--
| Lucas Nussbaum
| [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |
--- End Message ---
--- Begin Message ---
On 06/02/08 at 11:48 +0000, Thiemo Seufer wrote:
> Michael Stone wrote:
> > On Thu, Jan 24, 2008 at 02:55:51PM +0000, Thiemo Seufer wrote:
> >> Michael Stone wrote:
> >>> Meaning that the buildd's will be upgraded then & I should just wait
> >>> for them to try to rebuild coreutils after that? (Just want to make
> >>> sure I understand the proper path forward.)
> >>
> >> Yes.
> >
> > Did the upgrade happen? (Last build was 2008-01-31, failed as before:
> > http://buildd.debian.org/fetch.cgi?&pkg=coreutils&ver=6.10-3&arch=mips&stamp=1201761341&file=log
> >
> > )
>
> Sorry, it did not happen. I'm still at kernel debugging.
Hi,
Thanks to the work of Thiemo (and others?), coreutils finally built on
mips*, so I guess we can close this bug!
--
| Lucas Nussbaum
| [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |
--- End Message ---
