Bug#894905: fflas-ffpack: missing Depends: libgivaro-dev (>= 4.0.3)
On 04/05/2018 08:24 AM, Andreas Beckmann wrote:
Package: fflas-ffpack
Version: 2.3.2-1~exp1
Severity: serious
Hi,
noticed this while rebuilding linbox/experimental in sid+experimental:
...
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for FFLAS_FFPACK... no
configure: error: Package requirements (fflas-ffpack >= 2.3.0) were not met:
Package 'fflas-ffpack' requires 'givaro >= 4.0.3' but version of givaro is 4.0.2
You may find new versions of Givaro at http://givaro.forge.imag.fr
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables FFLAS_FFPACK_CFLAGS
and FFLAS_FFPACK_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
...
The pkg-config file contains:
/-- fflas-ffpack.pc
prefix=/usr
exec_prefix=/usr
libdir=/usr/lib
includedir=/usr/include
Name: fflas-ffpack
Description: Finite Field Linear Algebra Suroutines/Package
URL: http://github.com/linbox-team/fflas-ffpack
Version: 2.3.2
Requires: givaro >= 4.0.3
Libs: -fopenmp -lblas -llapack
Cflags: -I${prefix}/include-fopenmp -fabi-version=6
\---
Thanks for the report!
This would explain why I had to manually install givaro from
experimental in my sbuild when I was packaging the new upstream version
of linbox. It never occurred to me that the mistake was in fflas-ffpack...
Anyway, I've fixed the problem in git [1]. I've copied this message to
the Sage team -- would anyone be able to sponsor?
Doug
[1] https://salsa.debian.org/science-team/fflas-ffpack/commit/be453b1
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Accepted linbox 1.5.2-1~exp1 (source amd64 all) into experimental, experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 24 Mar 2018 18:41:34 -0400 Source: linbox Binary: liblinbox-dev liblinbox-1.5.2-0 liblinboxsage-dev liblinboxsage-1.5.2-0 liblinbox-doc Architecture: source amd64 all Version: 1.5.2-1~exp1 Distribution: experimental Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Doug Torrance Description: liblinbox-1.5.2-0 - Library for exact linear algebra - shared library liblinbox-dev - Library for exact linear algebra - development files liblinbox-doc - LinBox Documentation liblinboxsage-1.5.2-0 - SAGE interface of LinBox - shared library liblinboxsage-dev - SAGE interface of LinBox - development files Changes: linbox (1.5.2-1~exp1) experimental; urgency=medium . [ Doug Torrance ] * New upstream release. * Refresh patches for new upstream version * Bump version in library sonames. * Bump version of fflas-ffpack in Build-Depends and Depends. * Update VCS-* to Salsa * Bump Standards-Version to 4.1.3. * New patch replacing probabilistic CRA for charpoly by a deterministic one. . [ Tobias Hansen ] * Rename *.install files after packages have been renamed for SONAME bump. Checksums-Sha1: 30f7b4310d091df20298a8e455ebe09cd34bc82b 2473 linbox_1.5.2-1~exp1.dsc 5f0d7beb800fc2e582b4cfbaef39af1c0c893527 2272378 linbox_1.5.2.orig.tar.gz 42ef67d9071e87f3e87b0ad751c51e451774186d 9432 linbox_1.5.2-1~exp1.debian.tar.xz 59cac4f6640dce4d3b539650e5722718b851c19f 311272 liblinbox-1.5.2-0-dbgsym_1.5.2-1~exp1_amd64.deb cdb34386f78ef6e95165e57da2874e27d6405682 107116 liblinbox-1.5.2-0_1.5.2-1~exp1_amd64.deb 5f16be2cf53ab69c302d9a12d6846c89fb874597 1102760 liblinbox-dev_1.5.2-1~exp1_amd64.deb 31b2b68c43af7442526bde88cbf76b7cbe3a4fc2 65796296 liblinbox-doc_1.5.2-1~exp1_all.deb bb56c248cc62ca5ab7cb4161ac519d8dc46f662f 2908784 liblinboxsage-1.5.2-0-dbgsym_1.5.2-1~exp1_amd64.deb ddd4dbbc48d762a2185eb334a9750fc8c236405b 411412 liblinboxsage-1.5.2-0_1.5.2-1~exp1_amd64.deb 68d9e99c709c60502d9529d0c79ae8b4a36f9cf0 402128 liblinboxsage-dev_1.5.2-1~exp1_amd64.deb ecfa4b22089815012ee6aef6c25474fd079dbd19 11987 linbox_1.5.2-1~exp1_amd64.buildinfo Checksums-Sha256: 318dfe8a2c2c5161ac951afcb7fbce7f102c44864cd59b28a4f85eeb75503967 2473 linbox_1.5.2-1~exp1.dsc b5ac1e4e298d246f987af43500156ea5d53225b0322ec7017991d5574c327bce 2272378 linbox_1.5.2.orig.tar.gz 3fe904884f73b0e475326ce22e651798af351a151b3f54207f2f3c492afec1a2 9432 linbox_1.5.2-1~exp1.debian.tar.xz 509b75f581aac00251540380283472f21817814446b9239f754edc4077d076cb 311272 liblinbox-1.5.2-0-dbgsym_1.5.2-1~exp1_amd64.deb f999a990a8418640258fcdfed405102e25f2c9585bbd1f3de6fc133078997846 107116 liblinbox-1.5.2-0_1.5.2-1~exp1_amd64.deb 6763d42d3438614c2ac80de273158a6c3284b8d3a8f27d27b5137ac70077056f 1102760 liblinbox-dev_1.5.2-1~exp1_amd64.deb 92b989e8c8067810337620ddb6b439d1ebe784d1f619d6416650c54ec290b845 65796296 liblinbox-doc_1.5.2-1~exp1_all.deb 6c861eeeaa89adc9b6acb5a640a7d7f681d39da215dc09eef5d16060f25faa10 2908784 liblinboxsage-1.5.2-0-dbgsym_1.5.2-1~exp1_amd64.deb 57147c6a77e5ee94d4f556fcacdf696a99ee7428c93dcbd9139a808b34c9132e 411412 liblinboxsage-1.5.2-0_1.5.2-1~exp1_amd64.deb 818370e3ce572e0065150c50683887accd236c8419500ac03fcefab895a16489 402128 liblinboxsage-dev_1.5.2-1~exp1_amd64.deb f9a31fe529b67f06733703036c27e4b753ab70dee5367f6ac458c4f4266fc313 11987 linbox_1.5.2-1~exp1_amd64.buildinfo Files: 772b25239432936e8cf7987143c90684 2473 math optional linbox_1.5.2-1~exp1.dsc d881588a7b6c3ed1c4f9a621b4fd7a2c 2272378 math optional linbox_1.5.2.orig.tar.gz c1c9c061b51e950a6ec6e5a47c5e2301 9432 math optional linbox_1.5.2-1~exp1.debian.tar.xz ef755beed0733bf1327aaaf8481a9aed 311272 debug optional liblinbox-1.5.2-0-dbgsym_1.5.2-1~exp1_amd64.deb f26d7ac9d2f3bf1d63a272a63a5ad75d 107116 libs optional liblinbox-1.5.2-0_1.5.2-1~exp1_amd64.deb db7412f1fa9ca39a25b74a638636e609 1102760 libdevel optional liblinbox-dev_1.5.2-1~exp1_amd64.deb cab2b12718b5d56af3d36054abd628c6 65796296 doc optional liblinbox-doc_1.5.2-1~exp1_all.deb aaebe45bc402940b048a6adac260016c 2908784 debug optional liblinboxsage-1.5.2-0-dbgsym_1.5.2-1~exp1_amd64.deb c78e9f828c62358378c84d7da8553b6b 411412 libs optional liblinboxsage-1.5.2-0_1.5.2-1~exp1_amd64.deb e2c3b577f3f6ab6923eb03e1afe5953f 402128 libdevel optional liblinboxsage-dev_1.5.2-1~exp1_amd64.deb 5e7448814309978c7b4c01d010702e4c 11987 math optional linbox_1.5.2-1~exp1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoH46ol3M2u2mYo0kjIIWnY7OzSoFAlq3Zt4ACgkQjIIWnY7O zSpfaxAAhuPjrhfugc7bpI6LaCqaoSxpLJGzBFE4PD8SgcZySI7kDxI9iYDr6eb/ /OEodjm6VAEWAmrYZMpYNpxcA4eBGahDLEcMK6nAdZvYigPYTmZ8eV7q19Ha4Yc9 3Ulh0/nvH/U3G+CXU/VgOJ6kJNMT3RIioSZyvajfcjFa0KCKC8ZCMycWzoAozxaZ 2FMAYMbjVbSNsnhVblIWlBdq6KJlH4OmRsdrsXw4rMt8AA3t5e3y6LDc8RPNOsMZ rwrHnLqGIgEy42mgvT93GYlkf/+dsD+f7VYW5inQrzdg0Zv6nnmCQ/f0fUwDm0BD Nl+CGDGJLIY2dT93ei0g3G5J+/GS3sVqy0f78X+G9n3RaGRr6Bdi5sknniQ3Aupg cQT04
Re: cohomcalg_0.31d+ds-1_amd64.changes REJECTED
Hi Thorsten,
On 09/20/2017 02:00 PM, Thorsten Alteholz wrote:
Hi Doug,
according to manual.tex:
The lightbulb image used in the application logo was made by
\href{http://dragonartz.wordpress.com/}{DragonArt} and is
used under the
\href{http://creativecommons.org/licenses/by-nc-sa/3.0/}{Creative Commons
Attribution-Noncommercial-Share Alike 3.0} license.
Shouldn't that be mentioned in your debian/copyright?
This package was rejected from NEW several months ago for the same
reason, and I thought I'd fixed it prior to the re-upload, but maybe
not. :)
In particular, I removed the lightbulb image from the tarball using the
the Files-Excluded in d/copyright. I also added a patch
(d/patches/dfsg_manual.patch) which removes the image from the manual
and also removes the text you referenced regarding the licensing of the
image. This is documented in README.source.
Is there anything else that needs to be done?
Thanks!
Doug
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#862090: mathicgb FTBFS on big endian architectures: test fails
Control: forwarded -1 https://github.com/Macaulay2/mathicgb/issues/3 On 05/08/2017 07:15 AM, Radovan Birdic wrote: Package: mathicgb Version: 1.0~git20170104-1 Severity: important Tags: sid + patch Justification: FTBFS User: debian-m...@lists.debian.org Usertags: mips-patch Hello, Package mathicgb_1.0~git20170104-1 FTBFS on mips and other big endian architectures with following error: ... make check-TESTS make[2]: Entering directory '/«PKGBUILDDIR»' make[3]: Entering directory '/«PKGBUILDDIR»' FAIL: unittest mathicgb 1.0: ./test-suite.log # TOTAL: 1 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: unittest == ... Full build log: https://buildd.debian.org/status/fetch.php?pkg=mathicgb&arch=mips&ver=1.0~git20170104-1&stamp=1486639289&raw=0 On upstream this issue is resolved with proposed commit: https://github.com/Macaulay2/mathicgb/pull/9/commits/d8ae074c7f7655c3b85c2089cd7a05a98a70a46a I have attached the patch. With this patch package builds successfully on mips and mipsel. Thanks for your report! I've been aware of this for a while (I submitted the issue upstream back in 2015), but I suppose it's good to have it in the Debian BTS as well -- thanks! Upstream rejected the proposed patch as-is [1], which is why I've avoided applying it to the Debian package. However, I noticed that it has been applied to the Fedora package [2]. Perhaps I'll follow their lead and apply it to the Debian package as well for the time being. However, I'll wait until after the Stretch freeze. Doug [1] https://github.com/Macaulay2/mathicgb/pull/9#issuecomment-281349279 [2] http://pkgs.fedoraproject.org/cgit/rpms/mathicgb.git/commit/?id=0377aa73d04051c7b7c24c7ce28a054c31e66f52 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#853399: Fwd: Re: [linbox-team/fflas-ffpack] Fails to build with gcc 7 (#74)
Control: tags -1 fixed-upstream Forwarded Message Subject:Re: [linbox-team/fflas-ffpack] Fails to build with gcc 7 (#74) Resent-From:dtorra...@piedmont.edu Date: Fri, 10 Feb 2017 00:25:27 -0800 From: Clément Pernet Reply-To: linbox-team/fflas-ffpack To: linbox-team/fflas-ffpack CC: Doug Torrance , Author Closed #74 <https://github.com/linbox-team/fflas-ffpack/issues/74> via #75 <https://github.com/linbox-team/fflas-ffpack/pull/75>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/linbox-team/fflas-ffpack/issues/74#event-956913277>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB5mODxZAjPtWh_6YNuSl6X4itQ39zhmks5rbB73gaJpZM4Ly0Hl>. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#852995: Fwd: Re: [linbox-team/givaro] test-crt (sometimes) fails (#38)
Control: tags -1 fixed-upstream Forwarded Message Subject:Re: [linbox-team/givaro] test-crt (sometimes) fails (#38) Resent-From:dtorra...@piedmont.edu Date: Mon, 6 Feb 2017 06:28:06 -0800 From: Jean-Guillaume Dumas Reply-To: linbox-team/givaro To: linbox-team/givaro CC: Doug Torrance , Comment Closed #38 <https://github.com/linbox-team/givaro/issues/38>. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://github.com/linbox-team/givaro/issues/38#event-950372288>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB5mOEvCtki6ibgqbP3Rk2quh3LdUrlxks5rZy32gaJpZM4K1SPh>. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#852995: givaro: FTBFS randomly (failing tests)
Control: forwarded -1 https://github.com/linbox-team/givaro/issues/38 On 01/28/2017 01:49 PM, Santiago Vila wrote: I tried to build this package in stretch with "dpkg-buildpackage -A" but it failed: [...] debian/rules build-indep dh build-indep --with autoreconf dh_testdir -i dh_update_autotools_config -i dh_autoreconf -i libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'. libtoolize: copying file 'build-aux/ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'macros'. libtoolize: copying file 'macros/libtool.m4' libtoolize: copying file 'macros/ltoptions.m4' libtoolize: copying file 'macros/ltsugar.m4' libtoolize: copying file 'macros/ltversion.m4' libtoolize: copying file 'macros/lt~obsolete.m4' configure.ac:149: installing 'build-aux/compile' [... snipped ...] ERROR a4 != a6 ERROR a7 != a8 ERROR a9 != a10 ERROR a1 != a3 ERROR a4 != a7 ERROR a2 != a5 ERROR a1 != a9 FAIL test-crt (exit status: 1) Thanks for your report! This issue is apparently known already to upstream -- see the GitHub issue above. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#840458: [Debian-science-sagemath] linbox: FTBFS on i386: illegal instruction in test-{cra, charpoly}
Yes, please do. On Tue, Nov 29, 2016, 1:52 PM Tobias Hansen wrote: > On 11/29/2016 06:01 PM, Tobias Hansen wrote: > > On 11/29/2016 03:53 PM, Doug Torrance wrote: > >> Control: reassign -1 src:givaro > >> > >> On 11/29/2016 09:58 AM, Tobias Hansen wrote: > >>> I think I figured out at least the test failures with "Illegal > >>> instruction" on i386. The problem is that givaro is built using cpu > >>> extensions that are not allowed. > >>> > >>> Jerome figured out in [1] that the problem happens when givaro code is > >>> called. And sure enough: > >>> > >>> objdump -S /usr/lib/i386-linux-gnu/libgivaro.so.9.0.0 | grep > >>> '\b\(ymm\|zmm\|vfm\)' > >>> 15411:c4 e3 79 6b 8b a4 29 vfmaddsd > >>> %xmm2,-0x1d65c(%ebx),%xmm0,%xmm1 > >>> 154d1:c4 e3 69 6b 8b ac 29 vfmaddsd > >>> %xmm0,-0x1d654(%ebx),%xmm2,%xmm1 > >>> > >>> And in the i386 build logs for givaro there are these flags: > >>> -mmmx -mpopcnt -msse -msse2 -msse3 -msse4.1 -msse4.2 -msse4a -mavx > >>> -mfma4 -mfpmath=sse > >>> > >>> Do you have time in the next days to disable these flags? Otherwise I > >>> can do it. (I'm not sure if some of these flags (mmx, sse ?) are > allowed > >>> on i386 and didn't find that info. Ximin, do you know this?) > >> > >> Sure, I can take a look. I think it should be a simple --disable-simd > >> in d/rules (we did the same in fflas-ffpack). > >> > >> Doug > > > > Thanks! I tried building it but now there seems to be an issue similar > > to [1]: > > > > FAIL: test-ringarith > > > > > > 997167681959697!=997167682008849 failed (at line 123) > > x y failed ! > > MEDmax failed ! > > FAIL test-ringarith (exit status: 255) > > > > And it even fails when setting the flag -ffp-contract=off . > > Note that now the failure seems to be related to ModularExtended > > instead of ModularExtended (MEDmax instead of MEFmax in the error > > message). > > > > Best, > > Tobias > > > > [1] https://github.com/linbox-team/givaro/issues/25 > > Ok, a workaround is to set -ffloat-store (like the Fedora package). I > pushed this change to the git repo. Can I upload this? > > Best, > Tobias > -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#840458: linbox: FTBFS on i386: illegal instruction in test-{cra, charpoly}
Control: reassign -1 src:givaro On 11/29/2016 09:58 AM, Tobias Hansen wrote: I think I figured out at least the test failures with "Illegal instruction" on i386. The problem is that givaro is built using cpu extensions that are not allowed. Jerome figured out in [1] that the problem happens when givaro code is called. And sure enough: objdump -S /usr/lib/i386-linux-gnu/libgivaro.so.9.0.0 | grep '\b\(ymm\|zmm\|vfm\)' 15411: c4 e3 79 6b 8b a4 29vfmaddsd %xmm2,-0x1d65c(%ebx),%xmm0,%xmm1 154d1: c4 e3 69 6b 8b ac 29vfmaddsd %xmm0,-0x1d654(%ebx),%xmm2,%xmm1 And in the i386 build logs for givaro there are these flags: -mmmx -mpopcnt -msse -msse2 -msse3 -msse4.1 -msse4.2 -msse4a -mavx -mfma4 -mfpmath=sse Do you have time in the next days to disable these flags? Otherwise I can do it. (I'm not sure if some of these flags (mmx, sse ?) are allowed on i386 and didn't find that info. Ximin, do you know this?) Sure, I can take a look. I think it should be a simple --disable-simd in d/rules (we did the same in fflas-ffpack). Doug -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#835759: fflas-ffpack: FTBFS: unsatisfiable build-dependency: libgivaro-dev (< 4.0.2) but 4.0.2-1 is to be installed
On 08/28/2016 04:48 AM, Lucas Nussbaum wrote: During a rebuild of all packages in sid, your package failed to build on amd64. > ... > The following packages have unmet dependencies: sbuild-build-depends-fflas-ffpack-dummy : Depends: libgivaro-dev (< 4.0.2) but 4.0.2-1 is to be installed Thanks for your report! This is a known issue. The latest upstream version of fflas-ffpack (2.2.2) does work with givaro 4.0.2. Packaging work for this newer version is in progress. Doug -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#833846: fflas-ffpack: don't generate optimised code based on the build machine
Control: tags -1 pending On 08/09/2016 07:53 AM, Ximin Luo wrote: Control: severity -1 serious I was recommended by multiple people to bump the severity of this bug. Also to clarify that i386 should have no optimisation flags, and not "-msse -msse2". My earlier comment was based on a misunderstanding of what "i386 doesn't have mmx" meant; sse and sse2 build on top of mmx. X Ximin Luo: Package: fflas-ffpack Version: 2.2.1-1 Severity: important Dear Maintainer, fflas-ffpack on amd64 was built with "-msse4.1 -mfma -mavx2" as can be seen from the output of `pkg-config --cflags fflas-ffpack`. This unfortunately makes it crash on amd64 machines that don't support these instructions, and we are running into this issue whilst testing SageMath. Please disable any build options that set optimisations based on autodetection of the CPU features of the build machine. It should be OK to hard-code "-mmmx -msse -msse2" for amd64 and "-msse -msse2" for i386, according to wRAR on #debian-devel. This is somewhat based on information from [1]. There might be other optimisations you can make, but I haven't yet done the detailed research for that. X [1] https://lists.debian.org/debian-devel-announce/2016/05/msg1.html Thanks for your report! I had figured that there was an issue like this, as both the CI and reproducible build tasks have been failing. I've disabled the use of these extensions and a new version is in git [1] awaiting sponsorship. Doug [1] https://anonscm.debian.org/cgit/debian-science/packages/fflas-ffpack.git/commit/?id=88c339f745dc54351d4c437eedd38a5b83dca993 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#832539: Removed headervmodular-int32.h which is used by linbox
Control: reassign -1 linbox On Tue, 26 Jul 2016 18:11:27 +0100 Tobias Hansen wrote: > The package fflas-ffpack-common in version 1.6.0-1 contained the file > /usr/include/fflas-ffpack/field/modular-int32.h > > which is used by linbox. It is included for example in > /usr/include/linbox/field/Modular/modular-int32.h from the package > liblinbox-dev. > > I'm not sure if this file should still be there in fflas-ffpack-common > or if linbox needs to be updated. This header was actually moved from fflas-ffpack to givaro in a recent release. The latest upstream version of linbox properly includes the header from its new location. I've reassigned this bug to linbox, and it will be closed when the new version of linbox is uploaded. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#811847: givaro RC bug #811847
On 07/18/2016 01:53 AM, Julien Puydt wrote: On 17/07/2016 19:54, Doug Torrance wrote: I see that you've recently pushed some changes to git which close the RC bug #811847 [1]. Were you planning on uploading them? I ask because givaro is currently scheduled for auto-removal from testing. I'm also interested in givaro as it is a dependency for Macaulay2, which I'm trying to get into Debian. If you'd like, I'd be happy to help. I started a transition for NTL and wanted to get it through before starting a transition for givaro. If I'm the one asking for the transition, I'll first need to re-double-check the deps before RFS-ing to experimental and starting the ball rolling -- and I won't have time before a few days. Ah, makes sense! If you take over, you can do it right away : I'll consider you're helping, not stepping on my toes :-) Sounds good. Upstream actually switched to GitHub a few months ago and released a new version (4.0.1) [1]. I'd also like to backport a recent commit that's necessary for Macaulay2 to build. Doug [1] https://github.com/linbox-team/givaro -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#811847: givaro RC bug #811847
Hi Julien, I see that you've recently pushed some changes to git which close the RC bug #811847 [1]. Were you planning on uploading them? I ask because givaro is currently scheduled for auto-removal from testing. I'm also interested in givaro as it is a dependency for Macaulay2, which I'm trying to get into Debian. If you'd like, I'd be happy to help. Thanks! Doug [1] https://anonscm.debian.org/git/debian-science/packages/givaro.git -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#831109: mathic: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors
Control: tags -1 pending On 07/14/2016 04:06 AM, Lucas Nussbaum wrote: Source: mathic Version: 1.0~git20160320-3 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160713 qa-ftbfs Justification: FTBFS with GCC 6 on amd64 Hi, During a rebuild of all packages in sid using the gcc-defaults package available in experimental to make GCC default to version 6, your package failed to build on amd64. For more information about GCC 6 and Stretch, see: - https://wiki.debian.org/GCC6 - https://lists.debian.org/debian-devel-announce/2016/06/msg7.html Relevant part (hopefully): make[1]: Entering directory '/«PKGBUILDDIR»' dh_strip --dbgsym-migration='libmathic-dbg (<< 1.0~git20160320-1~)' make[1]: Leaving directory '/«PKGBUILDDIR»' dh_makeshlibs -a dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libmathic0v5/DEBIAN/symbols doesn't match completely debian/libmathic0v5.symbols --- debian/libmathic0v5.symbols (libmathic0v5_1.0~git20160320-3_amd64) +++ dpkg-gensymbols3hUTVg 2016-07-13 19:29:21.32400 + @@ -102,7 +102,7 @@ _ZNK6mathic10HelpAction5topicB5cxx11Ev@Base 1.0~git20160320 _ZNK6mathic11BitTriangle12getMemoryUseEv@Base 1.0~git20130827 _ZNK6mathic11NameFactoryINS_6ActionEE15namesWithPrefixERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt6vectorIS8_SaIS8_EE@Base 1.0~git20160320 - (optional)_ZNK6mathic11NameFactoryIPvE15namesWithPrefixERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt6vectorIS8_SaIS8_EE@Base 1.0~git20160320 +#MISSING: 1.0~git20160320-3# (optional)_ZNK6mathic11NameFactoryIPvE15namesWithPrefixERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt6vectorIS8_SaIS8_EE@Base 1.0~git20160320 _ZNK6mathic13BoolParameter12argumentTypeB5cxx11Ev@Base 1.0~git20160320 _ZNK6mathic13BoolParameter13valueAsStringB5cxx11Ev@Base 1.0~git20160320 _ZNK6mathic13ColumnPrinter14getColumnCountEv@Base 1.0~git20130827 @@ -118,15 +118,15 @@ _ZNK6mathic9CliParser29pushBackRegisteredActionNamesERSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS7_EE@Base 1.0~git20160320 _ZNSt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS2_EED1Ev@Base 1.0~git20160320 _ZNSt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS2_EED2Ev@Base 1.0~git20160320 - _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIIRKS5_EEEvDpOT_@Base 1.0~git20160320 +#MISSING: 1.0~git20160320-3# _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIIRKS5_EEEvDpOT_@Base 1.0~git20160320 _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIJRKS5_EEEvDpOT_@Base 1.0~git20160320 _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED1Ev@Base 1.0~git20160320 _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED2Ev@Base 1.0~git20160320 - _ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EE19_M_emplace_back_auxIIS6_EEEvDpOT_@Base 1.0~git20130827 +#MISSING: 1.0~git20160320-3# _ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EE19_M_emplace_back_auxIIS6_EEEvDpOT_@Base 1.0~git20130827 _ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EE19_M_emplace_back_auxIJS6_EEEvDpOT_@Base 1.0~git20130827 _ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EED1Ev@Base 1.0~git20130827 _ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EED2Ev@Base 1.0~git20130827 - _ZNSt6vectorISt4pairINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPFSt10unique_ptrIPvSt14default_deleteIS8_EEvEESaISE_EE19_M_emplace_back_auxIISE_EEEvDpOT_@Base 1.0~git20160320 +#MISSING: 1.0~git20160320-3# _ZNSt6vectorISt4pairINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPFSt10unique_ptrIPvSt14default_deleteIS8_EEvEESaISE_EE19_M_emplace_back_auxIISE_EEEvDpOT_@Base 1.0~git20160320 _ZNSt6vectorISt4pairINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPFSt10unique_ptrIPvSt14default_deleteIS8_EEvEESaISE_EE19_M_emplace_back_auxIJSE_EEEvDpOT_@Base 1.0~git20160320 _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED0Ev@Base 1.0~git20160320 _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED1Ev@Base 1.0~git20160320 dh_makeshlibs: failing due to earlier errors make: *** [binary-arch] Error 255 The full build log is available from: http://people.debian.org/~lucas/logs/2016/07/13/mathic_1.0~git20160320-3_unstable_gcc6.log Thanks for the report! I have pushed a fix to git marking the offending tags as optional [1] and have requested sponsorship for an upload of the new version. Doug [1] https://anonscm.debian.org/git/debian-science/packages/mathic.git/commit/?id=e0032
Bug#811805: gfan: FTBFS with GCC 6: error: reference is ambiguous
Control: tags -1 pending On Tue, 19 Jan 2016 18:08:29 -0800 Martin Michlmayr wrote: > This package fails to build with GCC 6. GCC 6 has not been released > yet, but it's expected that GCC 6 will become the default compiler for > stretch. This was fixed in Gentoo [1]. I have converted their patch to quilt and prepared a new release of the package. The new release also fixes a couple Lintian warnings and bumps to the latest Standards-Version. I've pushed it to git [2] and will request sponsorship. Doug [1] https://gitweb.gentoo.org/repo/gentoo.git/commit/sci-mathematics/gfan/files/gfan-0.5-gcc6.1-compat.patch [2] https://anonscm.debian.org/git/debian-science/packages/gfan.git -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#830811: mathic: Symbols file compatibility with -O3
Hi Steve, On 07/11/2016 03:08 PM, Steve Langasek wrote: The Ubuntu ppc64el port uses -O3 optimization for package builds by default. Under -O3, there are a number of template symbols that are not exported in libmathic because they wind up inlined instead. As a result, mathic fails to build with a mismatched symbols file error. The attached patch has been applied in Ubuntu to mark these additional symbols optional, since they are not part of the ABI, and allows the package to build wherever -O3 is used. Thanks for the report and patch! I've pushed a new version including the patch to git [1] and have requested sponsorship. Doug [1] http://anonscm.debian.org/cgit/debian-science/packages/mathic.git/commit/?id=1401c746239b54e6d773a37ccbe2995c9556cd32 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#807904: mathicgb: wrong spelling for Gröbner in package description
On Mon, 14 Dec 2015 12:16:37 +0100 Daniele Forsi wrote: > in the description for this package, I think that the name Groebner is > wrongly spelled twice as Grobner (without the "e"): > signature Grobner bases... > "Practical Grobner Basis Computation"... Thanks for the report! It's true that "Gröbner" (the original German spelling) is usually anglicized "Groebner" and not "Grobner". I'll upload a new version of this package soon with a corrected description. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Re: mathicgb upload
On 09/05/2015 04:50 PM, Anton Gladky wrote: > I think it is OK that the newer version with appended v5-name > to the library was uploaded. It should help to track the > migration process. Sounds good. Thanks again! Doug -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Re: mathicgb upload
Hi Anton! I noticed that you set mathic to Done on the SoB page. This was actually a new request, but I'm wondering if it was even necessary. A new RC bug [1] was filed against the version that you uploaded a couple days ago. I imagine they just grepped the exported symbols, saw that they included symbols that cause problems like the one that made mathicgb FTBFS, and filed the bug. What they probably didn't realize was that we had already taken care of it. However, I had neglected to append "v5" to the library name, so I pushed a new version to git with the requested change. What do you think? Should we upload the new version, or leave it as it is in unstable and close the bug by hand? Thanks! Doug [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797983 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Re: mathicgb upload
On 09/02/2015 02:22 PM, Anton Gladky wrote: Uploaded! Thanks! The powerpc build issue hasn't been fixed yet. I'm in contact with upstream and hope to have that fixed before too long. Doug -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Re: mathicgb upload
Hi Anton, On 09/01/2015 12:50 AM, Anton Gladky wrote: > your package mathicgb_1.0~git20131006-3 FTBFSs with the > following message: > > ... > > It can be connected to a current GCC-5 transition. Yeah, I had noticed this a few days ago. It's definitely because of the GCC-5 transition -- in particular the libstdc++ ABI change. While building, mathicgb is trying to use symbols that won't exist until its build dependency mathic is built with GCC-5. This was the reason I'd asked for an upload of memtailor a few days ago, since the build dependency chain is memtailor -> mathic -> mathicgb. Since that's been uploaded (thanks, by the way!), mathic is ready. I've pushed a new version to git and added a line to the SoB page. Even after the new mathic is uploaded, I still have to troubleshoot a few things with mathicgb before I upload a new version, as it was failing on a few archs even before the GCC-5 transition. Thanks! Doug -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Re: mathicgb build failed
On 07/18/2015 03:40 PM, Andreas Tille wrote: I think you need to update the symbols file (or remove it at all - I personally do not provide symbols files in my library packages since it makes maintainance hard). Thanks for the quick review, Andreas! I took your advice and removed the symbols file. It was quite a nightmare with this particular package. The git repository has been updated with the latest version. Thanks! Doug -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
