Bug#782653: openmpi: (non-)reproducibility of build failure

2015-04-20 Thread Simon Kainz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512



Am 2015-04-20 um 20:39 schrieb Willi Mann:
 Hi!
 
 Am 2015-04-19 um 00:29 schrieb Mario Lang:
 Willi Mann wi...@debian.org writes:
 
 was anybody of you able to reproduce this build failure in a
 clear chroot environment?
 
 No.
 
 I failed to reproduce it in a jessie pbuilder environment, and
 also on an another machine (mixed jessie/wheezy).
 
 Hmm, for me, it works in a clean pbuilder, but fails on every
 normal installation box (sid and jessie) I tried (I tried
 three, two sid and one jessie box).  Simon tried a fresh
 VirutalBox jessie install, which also fails.  I am guessing we
 are missing a Build-Conflicts.  But I haven't been able to
 identify it yet.
 
 
 It seems that the problem is that timestamp on the libtool.m4 file
 is too old. My guess is that in MET, the timestamp somehow
 underflows. By setting the timestamp to 1980 (instead of 1970) the
 problem disappears, at least on my machine.
 
 In clean pbuilder environments, you probably do not have the
 timezone set, so the 1970 timestamp does not underflow...
 
 Attached patch fixes the problem for me. Mario, Simon, can you
 confirm?

Hello,

yes, i am now able to do a sucessful build outside a pbuilder
environment. Thank you for the hint.

Simon.


 
 WM
 
 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJVNWo0AAoJEBy08PeN7K/pz5wP/3lh6P/G3VlLoo/RDNjRv4zt
yf9H87dgpEW+X5dgxoZWFUJzxrY7R7lOjPpzSBk+o3NKOQ+mRKsxwHCh7rq4//87
XjtR7vNOza+8cwUZRTX6Ybl0s3U41BkLUywOoi9eEJz52HynZkbLAWo+vwfvsrL6
N3Gmp55MtVjuriyWs4xyA/prKBDFDY+I4fLXXb6ZKN04BPi4ovLOnS0a4RM4SHm1
B/96GSS0LK6UXN0liGNi+wy1Me78htmtxNtQgUuJ2ACXJApDbIWMI8wJZ5c0Zpyi
zsEtaP7oDwg648q9IqJvQFgnsT7RxisxqXmt2JZm8biaw5h1IbElEizEMWlHraKo
acZzv/yUsHaQlM1k0iw0SjX6JwQETQNb16VZu5yi3bx1Z3JFBcFCT8wQFuL9hqDw
dzA2phZnaERWN1wtobLupwLzJ6FjFRwDrcW8p0DxnplALcbUCWZVBIGde6pr0533
JS8xs6VrFLQOgoTjsESpuVr6QtfdN6Cd0eUzbC488SXeAmyXgHK7daCwowehIF6G
vp4Xe03geT6NrzTLKjxPJZsjSJIsLZ8fu6M5W3mPP0L7NoIrJJCQlJ1U6C7A6IWc
nPtiokt74PtNoOzBe09El8mzN9AX9y5bAyMhDP4sdQNZiRhmcwkY0QCr/pQs1Bwq
yHqLkEhyk5AYyVsN/X1A
=Ninp
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#782653: openmpi: (non-)reproducibility of build failure

2015-04-20 Thread Willi Mann
Hi!

Am 2015-04-19 um 00:29 schrieb Mario Lang:
 Willi Mann wi...@debian.org writes:
 
 was anybody of you able to reproduce this build failure in a clear
 chroot environment?
 
 No.
 
 I failed to reproduce it in a jessie pbuilder environment, and also on
 an another machine (mixed jessie/wheezy).
 
 Hmm, for me, it works in a clean pbuilder, but fails on every normal
 installation box (sid and jessie) I tried (I tried three, two sid and
 one jessie box).  Simon tried a fresh VirutalBox jessie install, which
 also fails.  I am guessing we are missing a Build-Conflicts.  But I
 haven't been able to identify it yet.


It seems that the problem is that timestamp on the libtool.m4 file is
too old. My guess is that in MET, the timestamp somehow underflows. By
setting the timestamp to 1980 (instead of 1970) the problem disappears,
at least on my machine.

In clean pbuilder environments, you probably do not have the timezone
set, so the 1970 timestamp does not underflow...

Attached patch fixes the problem for me. Mario, Simon, can you confirm?

WM


diff --git a/debian/patches/ompi_autogen_sh.patch b/debian/patches/ompi_autogen_sh.patch
index 0429388..7c655f3 100644
--- a/debian/patches/ompi_autogen_sh.patch
+++ b/debian/patches/ompi_autogen_sh.patch
@@ -5,7 +5,7 @@
  fi
  
 +# Ensure libtool.m4 is very old so that make does not rebuild aclocal.m4
-+touch -t 19700101.00 config/libtool.m4
++touch -t 19800101.00 config/libtool.m4
 +
  run_and_check $ompi_autoconf
  


signature.asc
Description: OpenPGP digital signature


Bug#782653: openmpi: (non-)reproducibility of build failure

2015-04-18 Thread Willi Mann
Hi,

was anybody of you able to reproduce this build failure in a clear
chroot environment? I failed to reproduce it in a jessie pbuilder
environment, and also on an another machine (mixed jessie/wheezy).

WM



signature.asc
Description: OpenPGP digital signature


Bug#782653: openmpi: (non-)reproducibility of build failure

2015-04-18 Thread Sylvestre Ledru
Le 18/04/2015 14:32, Willi Mann a écrit :
 Hi,

 was anybody of you able to reproduce this build failure in a clear
 chroot environment? I failed to reproduce it in a jessie pbuilder
 environment, and also on an another machine (mixed jessie/wheezy).

 WM

FYI, I am no longer actively maintaining openmpi, so, don't hesitate to
NMU it once
you have a fix!
(I don't expect too much from the maintainers)

Cheers,
Sylvestre




signature.asc
Description: OpenPGP digital signature


Bug#782653: openmpi: (non-)reproducibility of build failure

2015-04-18 Thread Mario Lang
Willi Mann wi...@debian.org writes:

 was anybody of you able to reproduce this build failure in a clear
 chroot environment?

No.

 I failed to reproduce it in a jessie pbuilder environment, and also on
 an another machine (mixed jessie/wheezy).

Hmm, for me, it works in a clean pbuilder, but fails on every normal
installation box (sid and jessie) I tried (I tried three, two sid and
one jessie box).  Simon tried a fresh VirutalBox jessie install, which
also fails.  I am guessing we are missing a Build-Conflicts.  But I
haven't been able to identify it yet.

-- 
CYa,
  ⡍⠁⠗⠊⠕


pgpXRd07UfpfP.pgp
Description: PGP signature


Bug#782653: openmpi: (non-)reproducibility of build failure

2015-04-18 Thread Mario Lang
Sylvestre Ledru sylves...@debian.org writes:

 FYI, I am no longer actively maintaining openmpi, so, don't hesitate to
 NMU it once you have a fix!
 (I don't expect too much from the maintainers)

:-(.  Torque and OpenMPI are rather important to us as users of Debian
in the HPC area.  It is sad to see Torque being kicked from jessie in
the last moment, and read that OpenMPI maintainance is a vague thing.
I will definitely have to maintain both packages locally for the next
stable release.  Maybe we can help in those areas, if the license issues
of Torque are managable.  Also, OpenMPI 1.6 looks rather old, sigh.

-- 
CYa,
  ⡍⠁⠗⠊⠕


pgprJ5QXpJ6b9.pgp
Description: PGP signature