Your message dated Sun, 20 May 2012 14:03:39 -0500 with message-id <20120520190339.GG3000@burratino> and subject line Re: Processed: FTBFS: tst-writev fails on amd64 due to changes in kernels >= 2.6.37 has caused the Debian Bug report #673596, regarding libc6: FTBFS on wheezy/sid amd64 (test suite failures) 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 owner@bugs.debian.org immediately.) -- 673596: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673596 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: libc6: FTBFS on wheezy/sid amd64 (test suite failures)
- From: Philip Ashmore <contact@philipashmore.com>
- Date: Sun, 20 May 2012 02:51:45 +0100
- Message-id: <[🔎] 20120520015145.9453.3989.reportbug@localhost.localdomain>
Package: libc6 Version: 2.13-32 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, * What led up to the situation? I wanted to build a debug/local version to see the source file/line number of a segfault in libc6 kdbg * What exactly did you do (or not do) that was effective (or ineffective)? apt-get source libc6 sudo apt-get build-dep libc6 cd eglibc-2.13 dch -l local 'buckyball' debuild -us -uc -b -j7 * What was the outcome of this action? make[2]: Target `check' not remade because of errors. make[2]: Leaving directory `/v3c/downloads/debian/eglibc-2.13' make[1]: *** [check] Error 2 make[1]: Leaving directory `/v3c/downloads/debian/eglibc-2.13/build- tree/amd64-libc' # # Testsuite failures, someone should be working towards # fixing these! They are listed here for the purpose of # regression testing during builds. # Format: <Failed test>, Error <Make error code> [(ignored)] # annexc.out, Error 1 (ignored) tst-eintr1.out, Error 1 tst-writev.out, Error 1 *************** Encountered regressions that don't match expected failures: tst-eintr1.out, Error 1 * What outcome did you expect instead? Binary package(s) to instsll. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libc6 depends on: ii libc-bin 2.13-32 ii libgcc1 1:4.7.0-7 libc6 recommends no packages. Versions of packages libc6 suggests: ii debconf [debconf-2.0] 1.5.43 ii glibc-doc 2.13-32 ii locales 2.13-32 -- debconf information: glibc/upgrade: true glibc/restart-services: libraries/restart-without-asking: false glibc/disable-screensaver: glibc/restart-failed:
--- End Message ---
--- Begin Message ---
- To: Philip Ashmore <contact@philipashmore.com>
- Cc: 673596-done@bugs.debian.org
- Subject: Re: Processed: FTBFS: tst-writev fails on amd64 due to changes in kernels >= 2.6.37
- From: Jonathan Nieder <jrnieder@gmail.com>
- Date: Sun, 20 May 2012 14:03:39 -0500
- Message-id: <20120520190339.GG3000@burratino>
- In-reply-to: <[🔎] handler.s.C.13375395229488.transcript@bugs.debian.org>
- References: <4FB93BBF.3030305@philipashmore.com> <[🔎] handler.s.C.13375395229488.transcript@bugs.debian.org>
Version: 2.13-6 notfound 629862 eglibc/2.13-32 quit Hi Philip, Philip Ashmore wrote: > reopen 629862 = > found 629862 eglibc/2.13-32 > #See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673596 > #libc6: FTBFS on wheezy/sid amd64 (test suite failures) This was fixed in version 2.13-6 by marking the test as an expected failure. The underlying problem was fixed upstream by modifying the test to require the new kernel behavior, but that fix is not suitable for Debian because some people build with older kernels. Since it is an expected failure, it doesn't change the build result, so it doesn't explain the build trouble you described at bug#673596. Your build failure is rather due to tst-eintr1 failing. Sorry for the lack of clarity. Jonathan
--- End Message ---