Bug#534013: zope2.10: FTBFS: /bin/sh: line 0: cd: z: No such file or directory

[Jonas Meurer]

Hello Lucas,

On 21/06/2009 Lucas Nussbaum wrote:
> Package: zope2.10
> Version: 2.10.8-1
> Severity: serious
> User: debian-qa at lists.debian.org
> Usertags: qa-ftbfs-20090620 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part:
> > tar xfz Zope-2.10.8-final.tgz
> > test -d debian/patched || install -d debian/patched
> > cd z && CFLAGS="-Wall -g -O2" ./configure \
> > 		--prefix=/build/user-zope2.10_2.10.8-1-amd64-315F5a/zope2.10-2.10.8/debian/zope2.10/usr/lib/zope2.10 \
> > 		--with-python=/usr/bin/python2.4
> > /bin/sh: line 0: cd: z: No such file or directory
> > make: *** [build-arch-stamp] Error 1
> 
> About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
> of the Grid'5000 platform, using a clean chroot.  Internet was not
> accessible from the build systems.

could you provide the exact command that your archive rebuild uses to
build a package? if you take a look at debian/rules, there are several
more commands in unpack-stamp than just the 'tar xfz'. According to your
logfile, the build-arch-stamp and patch-stamp targets are executed in
the middle of the unpack-stamp target.

I'm unable to reproduce that bug in a clean amd64 debian/unstable
pbuilder chroot.

here's the relevant parts of debian/rules:

> ZOPE      := zope$(ZVER)
> PACKAGE   := zope$(ZVER)
> DEBIAN    := $(shell pwd)/debian/$(PACKAGE)
> 
> [...]
> unpack: unpack-stamp
> unpack-stamp:
> 	tar xfz $(ZBASE).tgz
> 	mv $(ZBASE) z
> 	touch unpack-stamp
> 
> [...]
> build: build-arch build-indep
> 
> build-arch: unpack-stamp patch-stamp build-arch-stamp
> build-arch-stamp:
>         cd z && CFLAGS="$(CFLAGS)" ./configure \
>                 --prefix=$(DEBIAN)/usr/lib/$(ZOPE) \
>                 --with-python=$(PYTHONBIN)
>         cd z && make
>         touch build-arch-stamp
 

according to your logfile, the build system ran target build-arch-stamp
just in between of 'tar xfz $(ZBASE).tgz' and 'mv $(BASE) z':

> [...]
> dpkg-source: info: building zope2.10 in zope2.10_2.10.8-1.dsc
>  debian/rules build
> tar xfz Zope-2.10.8-final.tgz
> test -d debian/patched || install -d debian/patched
> cd z && CFLAGS="-Wall -g -O2" ./configure \
> 		--prefix=/build/user-zope2.10_2.10.8-1-amd64-315F5a/zope2.10-2.10.8/debian/zope2.10/usr/lib/zope2.10 \
> 		--with-python=/usr/bin/python2.4
> /bin/sh: line 0: cd: z: No such file or directory
> make: *** [build-arch-stamp] Error 1
> make: *** Waiting for unfinished jobs....
> dpatch  apply-all  
> applying patch deb-zopeconf to ./ ... failed.
> make: *** [patch-stamp] Error 1
> mv Zope-2.10.8-final z
> touch unpack-stamp
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
> [...]


the same applies to your bugreport #533975 against zope2.11.

greetings,
 jonas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-zope-developers/attachments/20090702/0606be0b/attachment.pgp>