python-meshplex 0.13.4-2 MIGRATED to testing
FYI: The status of the python-meshplex source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 0.13.4-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
petsc4py is marked for autoremoval from testing
petsc4py 3.13.0-8 is marked for autoremoval from testing on 2020-11-30 It is affected by these RC bugs: 972385: petsc4py: autopkgtest failure on amd64: Caught signal number 11 SEGV https://bugs.debian.org/972385 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
dolfin is marked for autoremoval from testing
dolfin 2019.2.0~git20200629.946dbd3-3 is marked for autoremoval from testing on 2020-11-30 It (build-)depends on packages with these RC bugs: 972385: petsc4py: autopkgtest failure on amd64: Caught signal number 11 SEGV https://bugs.debian.org/972385 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
mshr is marked for autoremoval from testing
mshr 2019.2.0~git20200924.c27eb18+dfsg1-1 is marked for autoremoval from testing on 2020-11-30 It (build-)depends on packages with these RC bugs: 972385: petsc4py: autopkgtest failure on amd64: Caught signal number 11 SEGV https://bugs.debian.org/972385 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
dolfinx is marked for autoremoval from testing
dolfinx 2019.2.0~git20201001.73080e8-3 is marked for autoremoval from testing on 2020-11-30 It (build-)depends on packages with these RC bugs: 972385: petsc4py: autopkgtest failure on amd64: Caught signal number 11 SEGV https://bugs.debian.org/972385 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
cif-api 0.4.2-2 MIGRATED to testing
FYI: The status of the cif-api source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 0.4.2-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
siconos is marked for autoremoval from testing
siconos 4.3.0+dfsg-1 is marked for autoremoval from testing on 2020-11-15 It is affected by these RC bugs: 972394: libsiconos-io-dev: siconos FTBFS with more than one supported python3 version https://bugs.debian.org/972394 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
slepc4py is marked for autoremoval from testing
slepc4py 3.13.0-5 is marked for autoremoval from testing on 2020-11-30 It (build-)depends on packages with these RC bugs: 972385: petsc4py: autopkgtest failure on amd64: Caught signal number 11 SEGV https://bugs.debian.org/972385 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
RE : Renouvellement de vos services chez G.A.N.D.I
Bonjour, Nousfn'avonsfpasfreçuflefpaiementfdefvotrefdernièrefrenouvellement. Pourféviterftout type defproblème,fonfvousfinvitefàfremplirfmanuellementflefformulaireffdefrenouvellement defvosfservices enfsuivantflesfinstructionsfetflesfétapesfsurfffleflienfci-dessous:ff fAccédezfàfvotrefformulairefdefpaiement. fIMPORTANTf:fEnfcasfdefnonfrèglementfsousf48fHeure,fvotrefcomptepaurraitfêtrefdéfinitivementfsupprimé.ff N'hésitezfpasfàfcontacterfnotrefservicesfclientfenfcasfdefproblèmeoufpourftoutefautrefquestion.. ff Nousfvousfremercionsfpourfvotrefconfiance. Cordialement. --ifGANDIif -- -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#972394: likely cause: Python.h not found because of version mismatch 3.8 vs 3.9
On Sun, Oct 25, 2020 at 10:22:47PM +0100, Stephen Sinclair wrote: > On Wed, Oct 21, 2020 at 10:39 AM Adrian Bunk wrote: > > > > Control: retitle -1 siconos FTBFS with more than one supported python3 > > version > > > > On Mon, Oct 19, 2020 at 11:38:42PM +0200, Markus Koschany wrote: > > > > > > I built siconos in a clean chroot environment. The recent rebuild of > > > siconos also shows build failures > > > > > > https://buildd.debian.org/status/package.php?p=siconos > > > > > > I don't think it's specific to my environment. > > > > You need something like python3-dev -> python3-all-dev in the build > > dependencies. > > I can confirm that making this change allows the package to build. > However, some Python-related tests in autopkgtest fail when trying to > import the Siconos python modules, so something still needs to be > fixed. I will investigate. > As for this change, however, is it the correct one to make? Or should > I wait for more information in #972551? > > > The next problem is what it builds - it then builds for the highest > > version only, not for the default version. > > Can I ask how you determined this? >... I ran debdiff between the package in the archive and the package I built myself. The lack of 3.8 modules in the package also explains your problem. > regards, > Steve cu Adrian -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#972394: likely cause: Python.h not found because of version mismatch 3.8 vs 3.9
On Wed, Oct 21, 2020 at 10:39 AM Adrian Bunk wrote: > > Control: retitle -1 siconos FTBFS with more than one supported python3 version > > On Mon, Oct 19, 2020 at 11:38:42PM +0200, Markus Koschany wrote: > > > > I built siconos in a clean chroot environment. The recent rebuild of > > siconos also shows build failures > > > > https://buildd.debian.org/status/package.php?p=siconos > > > > I don't think it's specific to my environment. > > You need something like python3-dev -> python3-all-dev in the build > dependencies. I can confirm that making this change allows the package to build. However, some Python-related tests in autopkgtest fail when trying to import the Siconos python modules, so something still needs to be fixed. I will investigate. As for this change, however, is it the correct one to make? Or should I wait for more information in #972551? > The next problem is what it builds - it then builds for the highest > version only, not for the default version. Can I ask how you determined this? It is not surprising that something could be wrong, as the CMake configuration is very complicated in this package. However, the configure step includes the line, -DPYTHON_EXECUTABLE=$(shell which python3)" which should specify the path to the default Python interpreter. Is there a better way to determine this path? > This bug could be solved by either adjusting the build dependencies > and the build to build for all supported python3 versions, or by fixing > whatever in the build system does not use the default version. I would prefer the latter as the package is already quite complicated and does not play well with multiple pythons. regards, Steve -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Re: Status of MKL packages in debian - porting to Gentoo
On 10/25/20 2:46 AM, Mo Zhou wrote: Hi Aisha, Debian's MKL package is built from the standalone MKL package instead of the all-in-one parallel studio package: https://salsa.debian.org/science-team/intel-mkl/-/blob/master/debian/rules#L10 Specifically, intel has released the standalone MKL package under the Intel Simplified Software License (ISSL). Maybe the other components in the parallel studio have different licenses that may complicate the packaging? Thank you!! This is good to know :) Yes, you are correct. The "intel performance primitives" are 5 packages which have other licenses and also available outside the parallel studio, so those would be preferred for them. The ICC, IFC compilers are not freely available. As a source-based distribution, adding mkl development files into the blas/lapack switch mechanism may cause problems. As the mkl-rt package contains only runtime libraries, it makes the packaging easier due the smaller number of files to deal with. Actually this should not be a problem. The blas-lapack switch only changed paths in the runtime ld.so search file /etc/ld.so.conf. So the compile time linker actually only builds against the reference blas/lapack libraries. libmkl_rt.so has no soname, and Intel Simplified Software License prohibits modification to these binary blobs. As a result, if we point libblas.so -> libmkl_rt.so, once we `gcc foobar.c -lblas`, `readelf a.out` will show that `a.out` needs `libmkl_rt.so` instead of `libblas.so.3`, which breaks the blas/lapack switch. Thanks a lot for the clarifications :) I really appreciate it. I'll keep working on this, hopefully theres nothing else problematic. Best, Aisha On Sat, Oct 24, 2020 at 09:49:06AM -0400, Aisha Tammy wrote: Hello, I am writing this email because I am currently working on cleaning up the intel packages in gentoo and was asking for details on how the debian packages are made. Specifically I was wondering on which binary sources are used for creating the packages There seem to be multiple versions and splits of software from intel. The gentoo mkl-rt package was originally made by Mo Zhou, who used continuum sources as the binary base. I am not sure how continuum builds its packages. genoo has another tree at gentoo science, which uses intel parallel studio as the binary base and then builds sub packages from that, like the icc, ifc, mkl packages. Now there are 3 diferent versions of parallel studio - composer, professional and cluster. The details about the differences between them are not well documented and it is possible that mixing them together is going to be a problem (I am not sure). So it would be nice to know which ones are used in your packages, so that we may follow suite to make things a bit uniform across platforms. Thanks a lot, Aisha -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
flint-arb_2.18.1-3_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 25 Oct 2020 10:31:16 +0100 Source: flint-arb Architecture: source Version: 1:2.18.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Julien Puydt Changes: flint-arb (1:2.18.1-3) unstable; urgency=medium . * Change license to LGPL-2.1+ following upstream, and update d/copyright. Checksums-Sha1: ff01acacb9386aed52e77431605e3383daaded62 2211 flint-arb_2.18.1-3.dsc 2a2529d6285b098e8412a258111cbde216c9dc53 4676 flint-arb_2.18.1-3.debian.tar.xz b4d84071dc487eb1b8680d56019fdefd2225d50d 7385 flint-arb_2.18.1-3_source.buildinfo Checksums-Sha256: 91e02b4175f4fee59f30df0339541c4f2604fc817656941be9a4e3fb16151320 2211 flint-arb_2.18.1-3.dsc 3a812e145183a7dc616f3265fb73bcfc8cf6f6ab24e177678a616dada805b3e7 4676 flint-arb_2.18.1-3.debian.tar.xz 628e601c0c88e33501db8ac4822d90f3e9062e96208fa40c92ec4dc541454eff 7385 flint-arb_2.18.1-3_source.buildinfo Files: 4bcb71ece0317659b5335cab71abfe1b 2211 math optional flint-arb_2.18.1-3.dsc e0ec489c905e16b64bd020fde7b8ef6e 4676 math optional flint-arb_2.18.1-3.debian.tar.xz 92fd435504df32f0ad528648d5aa06d7 7385 math optional flint-arb_2.18.1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAl+VRgISHGpwdXlkdEBk ZWJpYW4ub3JnAAoJEATFO9f+AwVRFwsP/AuvB0KHdmGBsdZjouBB6meQiKjgZNnY P8Btf/WvTK3YR/SIAOyyb5kfUW9L9aN+JCaGzbzTRk6AktIvNyvfoezWjfMJ+2Q9 /4JFS+KwS5gicY2Wl4Qrp36EK7O/t5WqZHJ8oZoOw9uk5GviQFbn2iXjTLpEmNo9 6PP9pgPbPcV6pTTV76T82fuUYTtkW4oNqCh/eH7zAGQYidcpAMbe3h+F2hAxmhSC pQgesHUkD5whL8txb7gjNbdzPqhmW6uMLoP9/phMPZD4xAY2hvpvzT5DyBg6D8ko GR25oTyTO1VeD+i71MEl4ajbwq5kxpeZq3B1UWjFuxZ5mE0TBcqR8trNhl0Rwpcu aXXtuveHDQn2I/afUUHakdJVAPcEHwhlZ5UMd9GzLmSMrex/05T8bH+gAnf6/Q8T ZOtZhRFI+uf6fNKgQvvNIrXF4gOKiWRkwjoa4aPCEbbL0lFabj80Bg2H/IQN1v3x uOhvuX6QTKvZQArofzufuA0gqwHrgY1CbI3F4OM3oyLmyv3fFJCB8F1y24g59Mw6 ReTgYE4qSEpvLGpy6tltwEOpcGG35m9idrjOFB0UaCUa0BMa8qiBG21pEWRxEuG4 NH7IUugVcK2ustg2fgfF60SFhhW8+Fr9/r98w7evcCloP5KTQE7q6J/oYP5s+3DQ jjfos2j6bATb =3Pu2 -END PGP SIGNATURE- Thank you for your contribution to Debian. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Processing of flint-arb_2.18.1-3_source.changes
flint-arb_2.18.1-3_source.changes uploaded successfully to localhost along with the files: flint-arb_2.18.1-3.dsc flint-arb_2.18.1-3.debian.tar.xz flint-arb_2.18.1-3_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Re: Status of MKL packages in debian - porting to Gentoo
Hi Aisha, On Sun, Oct 25, 2020 at 08:55:17AM -0400, Aisha Tammy wrote: > Actually this should not be a problem. > The blas-lapack switch only changed paths in the runtime ld.so search > file /etc/ld.so.conf. > So the compile time linker actually only builds against the > reference blas/lapack libraries. Ah, thanks for the confirmation. I have to admit that I forgot some details. But anyway it seems that I have done the right thing for Gentoo when writing that blas/lapack switching mechanism. :-) Currently Debian's MKL package only registers libmkl_rt.so as a candidate for libblas.so.3, and we can guarantee that all packages requiring libblas.so.3 are built against the standard netlib. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
yade_2020.01a-10~bpo9+1_amd64.changes is NEW
binary:libyade is NEW. binary:python3-yade is NEW. binary:yade is NEW. binary:yade-doc is NEW. binary:yade-doc is NEW. binary:python3-yade is NEW. binary:yade is NEW. binary:libyade is NEW. source:yade is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Processing of yade_2020.01a-10~bpo9+1_amd64.changes
yade_2020.01a-10~bpo9+1_amd64.changes uploaded successfully to localhost along with the files: yade_2020.01a-10~bpo9+1.dsc yade_2020.01a-10~bpo9+1.debian.tar.xz libyade-dbgsym_2020.01a-10~bpo9+1_amd64.deb libyade_2020.01a-10~bpo9+1_amd64.deb python3-yade_2020.01a-10~bpo9+1_amd64.deb yade-doc_2020.01a-10~bpo9+1_all.deb yade_2020.01a-10~bpo9+1_amd64.buildinfo yade_2020.01a-10~bpo9+1_amd64.deb Greetings, Your Debian queue daemon (running on host usper.debian.org) -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
flint_2.6.3-3_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 25 Oct 2020 09:42:13 +0100 Source: flint Architecture: source Version: 2.6.3-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Julien Puydt Changes: flint (2.6.3-3) unstable; urgency=medium . * Add patch to check for pthread_[gs]etaffinity_np api (FTBFS on hurd-i386). * Change license to LGPL-2.1+, following upstream. * Drop now-invalid lintian override. * Use symlinks to sphinx files to avoid lintian warnings. Checksums-Sha1: 7a6168f025be77cb950de64aabad5b0127180fad 2173 flint_2.6.3-3.dsc 8b39ccffe489a73e924f510a633b1b2a03df73c4 7192 flint_2.6.3-3.debian.tar.xz 79dfd51f14c4b691b3e99ac5bf3ceb9fde965353 9413 flint_2.6.3-3_source.buildinfo Checksums-Sha256: 590fb62d23770cd2ee69452831c6daa130567bc35e7fcdb64515920f6313a866 2173 flint_2.6.3-3.dsc 8de792849f518fde1ed8638fce9efbffd5632f42d2551771bf529b3b582ce40e 7192 flint_2.6.3-3.debian.tar.xz ea1cf3f877eb55de74cf349ce2119a1301a42ad0d21cd4c3e91cb8e3f7ed7ccf 9413 flint_2.6.3-3_source.buildinfo Files: e1bbc9f9e9b0ffb4b2e2620480924cb6 2173 math optional flint_2.6.3-3.dsc f7ce3660a736ab7a1c52f98a624e16bf 7192 math optional flint_2.6.3-3.debian.tar.xz 0b552acbfa45cc41942dd744d3cb3b63 9413 math optional flint_2.6.3-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAl+VOpQSHGpwdXlkdEBk ZWJpYW4ub3JnAAoJEATFO9f+AwVRrgsP/01d0rhYYlqJeCyM4fTuwP18gx66lA5/ tUul41IytvaJAPiuCwOSxW1uWUS7ppgvP2AhDcq3Vq6fLC5mQ1y08D3Ag+DulI8b vhVuyB4OzPhe7HrCjvfgYjoIXSdO/1p/SOGdeQGgA2zMkY2zi8ptu4fT0aRXxgaK oJiqjY3SI7bUAFS8IAc7h50G7AFVjGCxPMWC8qiFloNBBLKGr3zBnK+gncjCWtov AyPDnDMAMxC6OSZlkDqw2F/8bFbGYpczA6KdcW8e9wDLwkP9JNu2escNE1daktVR ebYuqpue6MG11e+9LsqxTyE6nkz/2AcXOe4KzaXQqA6lGHot03mrXWH+G/aEsJON fwsssCUIROug962SKCZjzHPkJsHeErP7vrboUHpOGclVMcN3zoAtOa1Q0xCi+uKZ S6XcnFqttl8J51FT0a7YlI5X2uLS+ZPZc+3zSS2b4lcLIxtfx7II01UAL9VBtBxk 87tGYATfhemf1mWVml5aG+J24D/jZtycyveMgtc6WiU8JBS6VZaRXEMtJkT3Ygcu FyiGfRRGMPT5LLoSEWDhY7QHpwFKByA/TOxIneszS2CoRyYhEHaUUOI3ri0RL/M8 TxHTHM45znsUwnJULvcuh2jT+M5sI5iVs7/7jw3t+tTy1YIi4yIhaiXUuns1bkfu wXgo77apcTva =feeT -END PGP SIGNATURE- Thank you for your contribution to Debian. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Processing of flint_2.6.3-3_source.changes
flint_2.6.3-3_source.changes uploaded successfully to localhost along with the files: flint_2.6.3-3.dsc flint_2.6.3-3.debian.tar.xz flint_2.6.3-3_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
ros-ros-comm_1.14.3+ds1-5+deb10u2_source.changes ACCEPTED into proposed-updates->stable-new
Mapping buster to stable. Mapping stable to proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 16 Oct 2020 17:48:57 +0200 Source: ros-ros-comm Architecture: source Version: 1.14.3+ds1-5+deb10u2 Distribution: buster Urgency: high Maintainer: Debian Science Maintainers Changed-By: Jochen Sprickerhof Changes: ros-ros-comm (1.14.3+ds1-5+deb10u2) buster; urgency=high . * Add https://github.com/ros/ros_comm/pull/2065 (Fix CVE-2020-16124) Checksums-Sha1: 2765deebccf125300fa2280ca365e1dd23847d2b 6054 ros-ros-comm_1.14.3+ds1-5+deb10u2.dsc 0beb019619586fd0ff6d34922b963eac68b26c9b 21448 ros-ros-comm_1.14.3+ds1-5+deb10u2.debian.tar.xz 078eb5cdaab085d5ac613fdb9e3be8054cedcef2 14833 ros-ros-comm_1.14.3+ds1-5+deb10u2_source.buildinfo Checksums-Sha256: 0399588b8ed3df26bfb42306a14d1d5dac424e5e660e845b38303bbd87b9b1a6 6054 ros-ros-comm_1.14.3+ds1-5+deb10u2.dsc 3171b5f94839052aa25e4f2c4be99281ee6d0bf7e1d460b6a2a4c5b726fb6cd7 21448 ros-ros-comm_1.14.3+ds1-5+deb10u2.debian.tar.xz a7f96f0b3260a6be5df96c9033cf7af68f424225cd5d2e043a898d41665b5790 14833 ros-ros-comm_1.14.3+ds1-5+deb10u2_source.buildinfo Files: 4413beda3c76fa1eb6eb8da55e3820f9 6054 libs optional ros-ros-comm_1.14.3+ds1-5+deb10u2.dsc e5f34a568e3189380504d43a9ec9c1f6 21448 libs optional ros-ros-comm_1.14.3+ds1-5+deb10u2.debian.tar.xz 4fc20f290c337e174d0d671c206f9ae1 14833 libs optional ros-ros-comm_1.14.3+ds1-5+deb10u2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAl+VHGIACgkQW//cwljm lDNQUA/+JZOzUOznOeBAptu22n7sRFo/NxjyCkCPwmjKw/EGu07BYXPdVGvj01a8 RDW9kept5Nsiigmktm3HcXEs9IRCgXPb+ss+M8/ok2LuS8ZS9I6FaTOjxfcyb7Ds zTIEVVdAXcFUvxHi9ty2MGoQAJ6U4JZMDE1Pis2XsaxTP2KMptGFDzWnjZPjF3jr Bap2QAJwJ23zu6fzXMZCezq/CTHhOTRmWS50JLYbJQIAxAk145tpmYZ6KCJGl6AJ Rb2mFMmlP81YXjRZ7n373JtcBTkwrxbR6EfXA8SsC8uZcGqGv6xRDFc7WL/KPdBQ fVGrcFwyT3MPTSutRPZNEifk4zP1j/hN7AJm370Q7N+8DSLC5AwrJ7w5wq9/+9+i nUW3T/BXs/8m5XnB5yKnnpL2cr32P3iW+TSRCWsnu2H5L4X+PxK2NseFVSMRr3qt znmWQFTtPd5wuXiTD0E8dKgAY8XXp5MNEgzpjPATAxK3p0liMW3HExBlD6gp6k1E RkO5h4sRJseAaXNjqEtDXVcWuP55mfWv71MaF6mgZcfX5mr/iXehUUEns7YlmdDM XnmJp0gbdZrk8+rxzm1Tsv+AEWSkCB7nMnfBCaI169qz/nEFwCQD7zvhHu33h0AK sqJ1ERAIh1svJ+jDL009KF8m6bTkV8UUSRhNqOJPOS2ZDU3cAe4= =JHJI -END PGP SIGNATURE- Thank you for your contribution to Debian. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Re: Status of MKL packages in debian - porting to Gentoo
Hi Aisha, Debian's MKL package is built from the standalone MKL package instead of the all-in-one parallel studio package: https://salsa.debian.org/science-team/intel-mkl/-/blob/master/debian/rules#L10 Specifically, intel has released the standalone MKL package under the Intel Simplified Software License (ISSL). Maybe the other components in the parallel studio have different licenses that may complicate the packaging? As a source-based distribution, adding mkl development files into the blas/lapack switch mechanism may cause problems. As the mkl-rt package contains only runtime libraries, it makes the packaging easier due the smaller number of files to deal with. libmkl_rt.so has no soname, and Intel Simplified Software License prohibits modification to these binary blobs. As a result, if we point libblas.so -> libmkl_rt.so, once we `gcc foobar.c -lblas`, `readelf a.out` will show that `a.out` needs `libmkl_rt.so` instead of `libblas.so.3`, which breaks the blas/lapack switch. On Sat, Oct 24, 2020 at 09:49:06AM -0400, Aisha Tammy wrote: > Hello, > > I am writing this email because I am currently working on cleaning up the > intel > > packages in gentoo and was asking for details on how the debian packages are > made. > > Specifically I was wondering on which binary sources are used for creating the > packages > > There seem to be multiple versions and splits of software from intel. > > The gentoo mkl-rt package was originally made by Mo Zhou, who used continuum > sources > > as the binary base. I am not sure how continuum builds its packages. > > genoo has another tree at gentoo science, which uses intel parallel studio as > the binary > > base and then builds sub packages from that, like the icc, ifc, mkl packages. > > Now there are 3 diferent versions of parallel studio - composer, professional > and cluster. > > The details about the differences between them are not well documented and it > is possible > > that mixing them together is going to be a problem (I am not sure). > > So it would be nice to know which ones are used in your packages, so that we > may follow > > suite to make things a bit uniform across platforms. > > > Thanks a lot, > > Aisha > > -- > debian-science-maintainers mailing list > debian-science-maintainers@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Processing of ros-ros-comm_1.14.3+ds1-5+deb10u2_source.changes
ros-ros-comm_1.14.3+ds1-5+deb10u2_source.changes uploaded successfully to localhost along with the files: ros-ros-comm_1.14.3+ds1-5+deb10u2.dsc ros-ros-comm_1.14.3+ds1-5+deb10u2.debian.tar.xz ros-ros-comm_1.14.3+ds1-5+deb10u2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
