Bug#473960: marked as done (kdeedu: FTBFS: make: *** [common-build-arch] Error 1)
Your message dated Wed, 9 Apr 2008 12:52:59 +0200
with message-id <20080409105259.GA3663@pryan.sytes.net>
and subject line Re: Bug#473960: kdeedu: FTBFS: make: *** [common-build-arch] Error 1
has caused the Debian Bug report #473960,
regarding kdeedu: FTBFS: make: *** [common-build-arch] Error 1
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.)
--
473960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473960
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: kdeedu
Version: 4:3.5.9-1
Severity: serious
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20080401 qa-ftbfs
Justification: FTBFS on i386
Hi,
During a rebuild of all packages in sid, your package failed to build on i386.
Relevant part:
> make[3]: Entering directory `/build/user/kdeedu-3.5.9/obj-i486-linux-gnu'
> make[3]: Nothing to be done for `all-am'.
> make[3]: Leaving directory `/build/user/kdeedu-3.5.9/obj-i486-linux-gnu'
> make[2]: Leaving directory `/build/user/kdeedu-3.5.9/obj-i486-linux-gnu'
> make[1]: Leaving directory `/build/user/kdeedu-3.5.9/obj-i486-linux-gnu'
> touch debian/stamp-makefile-build
> DEB_MAKE_CHECK_TARGET unset, not running checks
> touch debian/stamp-kde-apidox
> if ! test -d debian/man/out; then mkdir -p debian/man/out; fi
> for f in $(find debian/man -name '*.sgml'); do \
> docbook-to-man $f > debian/man/out/`basename $f .sgml`.1; \
> done
> for f in $(find debian/man -name '*.man'); do \
> soelim -I debian/man $f \
> > debian/man/out/`basename $f .man`.`head -n1 $f | awk '{print $NF}'`; \
> done
> touch debian/stamp-man-pages
> test -e obj-i486-linux-gnu/kig/scripting/libscripting.la
> make: *** [common-build-arch] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2008/04/01
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment. Internet was not accessible from the build systems.
--
| Lucas Nussbaum
| lucas@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr GPG: 1024D/023B3F4F |
--- End Message ---
--- Begin Message ---
On Wed, Apr 02, 2008 at 12:48:27PM +0200, Lucas Nussbaum wrote:
> Package: kdeedu
> Version: 4:3.5.9-1
> Severity: serious
> User: debian-qa@lists.debian.org
> Usertags: qa-ftbfs-20080401 qa-ftbfs
> Justification: FTBFS on i386
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on i386.
>
> Relevant part:
> > make[3]: Entering directory `/build/user/kdeedu-3.5.9/obj-i486-linux-gnu'
> > make[3]: Nothing to be done for `all-am'.
> > make[3]: Leaving directory `/build/user/kdeedu-3.5.9/obj-i486-linux-gnu'
> > make[2]: Leaving directory `/build/user/kdeedu-3.5.9/obj-i486-linux-gnu'
> > make[1]: Leaving directory `/build/user/kdeedu-3.5.9/obj-i486-linux-gnu'
> > touch debian/stamp-makefile-build
> > DEB_MAKE_CHECK_TARGET unset, not running checks
> > touch debian/stamp-kde-apidox
> > if ! test -d debian/man/out; then mkdir -p debian/man/out; fi
> > for f in $(find debian/man -name '*.sgml'); do \
> > docbook-to-man $f > debian/man/out/`basename $f .sgml`.1; \
> > done
> > for f in $(find debian/man -name '*.man'); do \
> > soelim -I debian/man $f \
> > > debian/man/out/`basename $f .man`.`head -n1 $f | awk '{print $NF}'`; \
> > done
> > touch debian/stamp-man-pages
> > test -e obj-i486-linux-gnu/kig/scripting/libscripting.la
> > make: *** [common-build-arch] Error 1
>
I just built kdeedu in both i386 and amd64 without problems. This looks like
some kind of transient problem in your build.
Ana
--- End Message ---
Reply to: