reopen 476054
thanks
also sprach Manoj Srivastava <[EMAIL PROTECTED]> [2008.04.14.1834 +0200]:
> I can explain why it is executed twice.
Thanks. That should now be fixed. I also found a million other
problems with the code, which was written pre-gcc-4, and will make
a new upstream release
On Mon, 14 Apr 2008 14:59:14 +0200, Raphael Hertzog <[EMAIL PROTECTED]> said:
--8<---cut here---start->8---
1 | ifeq "$(wildcard ../include/factory++.hpp)" ""
2 | CPPFLAGS=`pkg-config libfactory++ --cflags`
3 | else
4 | INCLUDE = .$(shell ln -sf ../include
also sprach Raphael Hertzog <[EMAIL PROTECTED]> [2008.04.14.1642 +0200]:
> Feel free to clone on coreutils if you believe ln to be at fault.
No cloned but filed anew.
Not sure the two are related anyway.
--
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' : proud Debian developer, author, a
On Mon, 14 Apr 2008, martin f krafft wrote:
> also sprach Raphael Hertzog <[EMAIL PROTECTED]> [2008.04.14.1459 +0200]:
> > However when I comment out the INCLUDE= line then it works. So it's
> > definitely related to this shell snippet. While stracing the whole
> > process, you'll discover that thi
also sprach Raphael Hertzog <[EMAIL PROTECTED]> [2008.04.14.1459 +0200]:
> I can reproduce it too but only when calling directly dpkg-buildpackage
> and not when calling "debuild". Because debuild has really forked
> dpkg-buildpackage from what I can see and does not set the same
> set of variables
also sprach Raphael Hertzog <[EMAIL PROTECTED]> [2008.04.14.1459 +0200]:
> However when I comment out the INCLUDE= line then it works. So it's
> definitely related to this shell snippet. While stracing the whole
> process, you'll discover that this shell snippet is executed twice... the
> first tim
also sprach Lucas Nussbaum <[EMAIL PROTECTED]> [2008.04.14.1526 +0200]:
> > I cannot reproduce this
>
> I can.
>
> > and it has nothing to do with GCC.
>
> What does it have to do with closing this bug?
You emphasised gcc 4.3 in your mail.
> > Thus closing.
>
> that's efficient bug triaging :
On Mon, 14 Apr 2008, Lucas Nussbaum wrote:
> > Thus closing.
>
> that's efficient bug triaging :-)
>
> Which version of dpkg-dev are you using in your build chroot? I suspect
> that it is caused by dpkg's last upload. (Ccing Raphael Hertzog)
I can reproduce it too but only when calling directly
Processing commands for [EMAIL PROTECTED]:
> reopen 476054
Bug#476054: libfactory++: FTBFS: dpkg-source: unrepresentable changes to source
Bug reopened, originator not changed.
> tags 476054 - unreproducible
Bug#476054: libfactory++: FTBFS: dpkg-source: unrepresentable changes to sourc
reopen 476054
tags 476054 - unreproducible
thanks
On 14/04/08 at 12:46 +0200, martin f krafft wrote:
> > > dpkg-source -b libfactory++-0.1.4
> > > dpkg-source: info: using source format `1.0'
> > > dpkg-source: info: building libfactory++ using existing
> > > libfactory++_0.1.4.orig.tar.gz
> > >
Processing commands for [EMAIL PROTECTED]:
> tags 476054 unreproducible
Bug#476054: libfactory++: FTBFS: dpkg-source: unrepresentable changes to source
There were no tags set.
Tags added: unreproducible
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debi
Package: libfactory++
Version: 0.1.4-1
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080413 qa-ftbfs
Justification: FTBFS on i386
Hi,
During a rebuild of all packages in sid, your package failed to build on i386.
This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc
12 matches
Mail list logo
