Your message dated Sat, 7 Jan 2017 13:02:19 +0100
with message-id <4fd2cc35-181b-6f74-6a7e-04754ee0a...@debian.org>
and subject line Re: cross-toolchain-base: FTBFS in testing (2 out of 2 hunks 
FAILED)
has caused the Debian Bug report #846334,
regarding cross-toolchain-base-ports: FTBFS in testing (2 out of 2 hunks FAILED)
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 ow...@bugs.debian.org
immediately.)


-- 
846334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846334
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cross-toolchain-base-ports
Version: 7
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:

--------------------------------------------------------------------------------
[...]
 debian/rules build-indep
linux: 4.8.7-1 / 4.8.7-1cross1
glibc: 2.24-5 / 2.24-5cross1

old linux version: 4.8.7-1 / 1
old glibc version: 2.24-5 / 1

new linux version: 4.8.7-1cross2
new glibc version: 2.24-5cross2
START stamp-dir/init-glibc
rm -rf glibc-2.24
tar -x -f  /usr/src/glibc/glibc-2.24.tar.xz
cp -a /usr/src/glibc/debian/ glibc-2.24
cd glibc-2.24 ; \
QUILT_PATCHES=/<<PKGBUILDDIR>>/debian/patches/glibc/debian quilt --quiltrc 
/dev/null push -a && \
rm -rf .pc/
Applying patch dpkg-shlibs.patch
patching file debian/rules.d/debhelper.mk
Hunk #1 succeeded at 81 (offset 2 lines).

Applying patch local-kill-locales.patch
patching file localedata/SUPPORTED

Now at patch local-kill-locales.patch
if dpkg --compare-versions 2.24-5 le 2.24-5; then \
  cd glibc-2.24; \
  patch -p1 < ../debian/patches/glibc/glibc-update.diff; \
fi
patching file iconv/gconv.h
patching file sysdeps/powerpc/powerpc32/power6/memset.S
patching file sysdeps/powerpc/powerpc64/power6/memset.S
cd glibc-2.24; \
        patch -p1 < ../debian/patches/glibc/glibc-depends.diff
patching file debian/rules.d/debhelper.mk
touch stamp-dir/init-glibc
START stamp-dir/init-gcc
set -e; \
mkdir gcc -p ; \
cd gcc ; \
ln -sf /usr/src/gcc-6/gcc-6.2.0.tar.xz gcc-6.2.0.tar.xz ;\
cp -a  /usr/src/gcc-6/debian/ . ; \
if [ -n "$(grep -v '^\#' /<<PKGBUILDDIR>>/debian/patches/gcc/series)" ]; then \
  QUILT_PATCHES=/<<PKGBUILDDIR>>/debian/patches/gcc quilt --quiltrc /dev/null  
push -a ; \
fi;
if dpkg --compare-versions 6.2.0-13 le 6.2.1-4; then \
  cd gcc; \
  patch -p1 < ../debian/patches/gcc/gcc-stage1.diff; \
fi
patching file debian/rules.patch
Hunk #1 FAILED at 151.
Hunk #2 FAILED at 187.
2 out of 2 hunks FAILED -- saving rejects to file debian/rules.patch.rej
debian/rules:213: recipe for target 'stamp-dir/init-gcc' failed
make: *** [stamp-dir/init-gcc] Error 1
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
--------------------------------------------------------------------------------

The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

--- End Message ---
--- Begin Message ---
This has nothing to do with -A builds.  Apparently you did that test rebuild for
testing, not unstable.  Please could you do such test rebuilds in unstable
instead?  Then you avoid filing issues which are non-issues.  You could detect
these as well by inspecting the Built-Using flag and using the very same
versions for your test builds.

Matthias

--- End Message ---

Reply via email to