Bug#349807: towitoko: [m68k, arm, s390] FTBFS: cp: cannot stat `./debian/tmp/usr/lib/libtowitoko.so': No such file or directory

2006-06-04 Thread Mohammed Adnène Trojette
On Fri, Mar 24, 2006, [EMAIL PROTECTED] wrote: FYI, this problem also occurs on i386 (according to pbuilder) and x86_64, see http://buildd.debian.org/build.php?pkg=towitokover=2.0.7-7arch=amd64file=log , so this is a totally RC bug. It currently builds fine on an i386 pbuilder. Does it still

Bug#349807: towitoko: [m68k, arm, s390] FTBFS: cp: cannot stat `./debian/tmp/usr/lib/libtowitoko.so': No such file or directory

2006-06-04 Thread Bill Allombert
tags 349807 patch quit On Sun, Jun 04, 2006 at 04:08:57PM +0200, Mohammed Adnène Trojette wrote: On Fri, Mar 24, 2006, [EMAIL PROTECTED] wrote: FYI, this problem also occurs on i386 (according to pbuilder) and x86_64, see

Bug#349807: towitoko: [m68k, arm, s390] FTBFS: cp: cannot stat `./debian/tmp/usr/lib/libtowitoko.so': No such file or directory

2006-03-24 Thread allomber
On Wed, Jan 25, 2006 at 02:04:00PM +0100, Simon Richter wrote: Hi, Christian T. Steigies wrote: cp: cannot stat `./debian/tmp/usr/lib/libtowitoko.so': No such file or directory dh_install: command returned error code 256 This appears to be the libtool bug with the missing .so,

Bug#349807: towitoko: [m68k, arm, s390] FTBFS: cp: cannot stat `./debian/tmp/usr/lib/libtowitoko.so': No such file or directory

2006-01-25 Thread Christian T. Steigies
Package: towitoko Severity: serious Justification: no longer builds from source Automatic build of towitoko_2.0.7-7 on garkin by sbuild/m68k 85 [...] ** Using build dependencies supplied by package: Build-Depends: debhelper (= 4.1.16) [...] dh_install cp: cannot stat

Bug#349807: towitoko: [m68k, arm, s390] FTBFS: cp: cannot stat `./debian/tmp/usr/lib/libtowitoko.so': No such file or directory

2006-01-25 Thread Simon Richter
Hi, Christian T. Steigies wrote: cp: cannot stat `./debian/tmp/usr/lib/libtowitoko.so': No such file or directory dh_install: command returned error code 256 This appears to be the libtool bug with the missing .so, probably a side-effect of the libtool version bump. Simon