severity 612502 important
stop
On 25.02.11 Thorsten Glaser (t...@mirbsd.de) wrote:
Hilmar Preu�e dixit:
Hi,
I applied the patch to our SVN, the next upload will have the fix.
Thanks a lot! (As I said, it probably doesn’t FTBFS in 99.9% of all
builds, across all architectures – but the
Processing commands for cont...@bugs.debian.org:
severity 612502 important
Bug #612502 [src:texinfo] texinfo: FTBFS due to running configure+build twice,
fix attached
Severity set to 'important' from 'serious'
stop
Stopping processing here.
Please contact me if you need assistance
On 09.02.11 Thorsten Glaser (t...@mirbsd.de) wrote:
Hilmar Preu�e dixit:
Hi,
Hm. I tried to build on Debian unstable, one time w/, one time w/o
the patch. The build logs did not show a difference. No, I
didn't found an evidence in the log, that something has been done
twice.
Hilmar Preu�e dixit:
I applied the patch to our SVN, the next upload will have the fix.
Thanks a lot! (As I said, it probably doesn’t FTBFS in 99.9% of
all builds, across all architectures – but the double-build is
wrong.)
--
sigmentation fault
How fitting ;-)
bye,
//mirabilos
--
On Di, 08 Feb 2011, Thorsten Glaser wrote:
Severity: serious
Justification: fails to build from source
[...]
to GNU autotools fsckup, this _can_ (but not necessarily does)
result in an FTBFS.
So *does* it FTBFS or not???
I *always* build in a clean chroot before uploading, so I am
a bit
On 08.02.11 Thorsten Glaser (t...@mirbsd.de) wrote:
Hi,
the debian/rules Makefile target patch is phony, that's why the
stamp file mechanism doesn't work and the build is run twice.
Hm. I tried to build on Debian unstable, one time w/, one time w/o the
patch. The build logs did not show a
Norbert Preining dixit:
So *does* it FTBFS or not???
I think it may depend on the moon phase. The second run of
configure, under fakeroot, had different results than the
first, which led to a failure.
Does building twice actually FTBFS?
The first build resulted in an FTBFS already.
(That
On 09.02.11 Thorsten Glaser (t...@mirbsd.de) wrote:
Norbert Preining dixit:
Hi,
Does building twice actually FTBFS?
The first build resulted in an FTBFS already.
Not here (i386). Do you still have the relevant error message you
got?
H.
--
sigmentation fault
--
To UNSUBSCRIBE, email
Hilmar Preu�e dixit:
Hm. I tried to build on Debian unstable, one time w/, one time w/o the
patch. The build logs did not show a difference. No, I didn't found
an evidence in the log, that something has been done twice.
Interesting. See below…
I used i386, is the problem limited to m86k and if
Source: texinfo
Version: 4.13a.dfsg.1-6
Severity: serious
Tags: patch
Justification: fails to build from source
Hi,
the debian/rules Makefile target patch is phony, that's why the
stamp file mechanism doesn't work and the build is run twice. Due
to GNU autotools fsckup, this _can_ (but not
10 matches
Mail list logo
