Hi On Fri, Jul 20, 2012 at 09:00:26AM +0900, Satoru KURASHIKI wrote: > hi, > > On Tue, Jul 17, 2012 at 5:46 PM, Evgeni Golov <evg...@debian.org> wrote: > >> > for me, it fails with > >> > cp: cannot create regular file > >> > > >> > `/tmp/buildd/hyperestraier-1.4.13/debian/ruby-hyperestraier-doc/usr/share/doc/ruby-hyperestraier-doc/rubynativeapi/classes/Estraier/Result.src/M000034.html': > >> > No such file or directory > >> > > >> > When I build it with -j4, and builds fine with -j1. > >> > > >> > This is pretty sure due to bad dependencies in debian/rules. > >> > >> Could you confirm that this is not on i386? I tried to reproduce the FTBFS > >> last > >> week and it FTBFS for me on a i386 sbuild chroot. In amd64 sbuild it > >> builds fine > > > > Mhh, correct. Ignore what I have said in my previous mail. > > I built on amd64 -- on i386 it indeed fails as described (with -j1). > > Indeed I think my debian/rules has bad dependencies (arch/indep), > and it will be fixed with next upload. (ignoring indep target) > > But, I can't reproduce above in my environment (pbuilder). > I try to rebuild 1.4.13-5 (with tweaking perl rule) on i386, > pdebuild --debbuildopts "-j4" > it builds fine... > > Can you check git head whether it can build on your environment? > http://anonscm.debian.org/gitweb/?p=collab-maint/hyperestraier.git > (which I have fixed rules dependencies)
I'm sorry not coming back to you sooner. I just gived a try, but it fails due to unexpected upstream changes: dpkg-source: error: aborting due to unexpected upstream changes (but I haven't looked at it in detail now). Regards, Salvatore
signature.asc
Description: Digital signature
