I saw some issue, I forgot where, that pointed out both mpfr4 and mpfr6 were getting pulled into certain builds. You could check your sbuild logs to see if both are getting installed.
X Tobias Hansen: > Hi, > > yes, I think you can update cysignals in unstable. I applied upstream patches > for new mpfr and matplotlib versions to sagemath and built it with both > versions of cysignals yesterday and got the same problems: > > sage -t --long src/sage/rings/number_field/number_field.py # Bad exit: 1 > sage -t --long src/sage/rings/polynomial/plural.pyx # Killed due to > segmentation fault > sage -t --long src/sage/structure/factorization_integer.py # Killed due to > kill signal > sage -t --long src/sage/structure/sage_object.pyx # Killed due to abort > > I have had the failure with number_field.py on my computer for a while, but > it doesn't happen on buildds. The others are new, but I don't even know if > the libmpfr6 transition is finished... > > Best, > Tobias > > > On 01/28/2018 06:11 AM, Jerome BENOIT wrote: >> Hello, >> >> this issue was fixed in 1.6.6+ds-2 which is current in experimental: >> can we migrate cysingals 1.6.6+ds-2 to unstable ? >> >> Thanks, >> Jerome >> >> >> -------- Forwarded Message -------- >> Subject: Bug#888606: cysignals: FTBFS with debhelper/11.1 due to empty build >> target >> Resent-Date: Sat, 27 Jan 2018 17:51:02 +0000 >> Resent-From: Niels Thykier <ni...@thykier.net> >> Resent-To: debian-bugs-dist@lists.debian.org >> Resent-CC: Jerome Benoit <calcu...@rezozer.net> >> Date: Sat, 27 Jan 2018 18:44:34 +0100 >> From: Niels Thykier <ni...@thykier.net> >> Reply-To: Niels Thykier <ni...@thykier.net>, 888...@bugs.debian.org >> To: Debian Bug Tracking System <sub...@bugs.debian.org> >> >> Source: cysignals >> Version: 1.6.5+ds-2 >> Severity: serious >> Tags: patch >> >> Hi, >> >> The cysignals package FTBFS with debhelper/11.1 as it has an empty >> build target. This is caused by debhelper had a bug in its handling >> of "explicitly defined rules targets" that has now been fixed. >> >> Previously, this happened to work because dpkg-buildpackage would >> invoke "debian/rules build" (which would be a no-op) followed by >> "fakeroot debian/rules binary". During the binary target, dh's >> suboptimal handling would run the build commands. >> >> >> The solution is trivial but less pretty; explicitly define "build" >> with the same content as the "%:" target (or rename the "build" folder >> and drop the ".PHONY" target). I have attached a patch for this. >> >> >> More details can be found in: >> * #886901 comment #35 >> * #887688 comment #37 >> * #880840 >> >> Apologies for the inconvenience. >> >> Thanks, >> ~Niels >> >> >> >> _______________________________________________ >> Debian-science-sagemath mailing list >> debian-science-sagem...@lists.alioth.debian.org >> https://lists.alioth.debian.org/mailman/listinfo/debian-science-sagemath > > > > > > _______________________________________________ > Debian-science-sagemath mailing list > debian-science-sagem...@lists.alioth.debian.org > https://lists.alioth.debian.org/mailman/listinfo/debian-science-sagemath > -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git
