Processing of flint_2.7.0-1_source.changes
flint_2.7.0-1_source.changes uploaded successfully to localhost along with the files: flint_2.7.0-1.dsc flint_2.7.0.orig.tar.gz flint_2.7.0-1.debian.tar.xz flint_2.7.0-1_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
flint_2.7.0-1_source.changes ACCEPTED into experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 Dec 2020 22:17:17 +0100 Source: flint Architecture: source Version: 2.7.0-1 Distribution: experimental Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Julien Puydt Changes: flint (2.7.0-1) experimental; urgency=medium . * New upstream release. * Bump std-vers to 4.5.1. Checksums-Sha1: 9cd45e3be44a3e58d973d731ca899b994268981d 2173 flint_2.7.0-1.dsc 86bf1e3e8722f60b0cf5170f5e27ebb1a96b373d 4943210 flint_2.7.0.orig.tar.gz 52537258776a70cdeb9f795493167ab2c5ab1981 6916 flint_2.7.0-1.debian.tar.xz 43d90e8061b31fa3e8408c0bb2f943487c5ba48e 9400 flint_2.7.0-1_source.buildinfo Checksums-Sha256: 6f294eb0b62b9ec9d5acbeac7290d146924c408ceb64d2b0c7ae32407ceaa518 2173 flint_2.7.0-1.dsc 919a722e33b83bb8dad2231fee97caaa40d028ff9c88ee2be645667f3c472f3a 4943210 flint_2.7.0.orig.tar.gz f2e93fc547a65944345c5f522497e221f909a78bb0295e7b9ed38ac8829258b4 6916 flint_2.7.0-1.debian.tar.xz e2d014e3580f3b4b0bd819c770910bd2dd1c9a66decbfc6c331b29293a27 9400 flint_2.7.0-1_source.buildinfo Files: 16e97dcc52a81198dd742422b9c6877c 2173 math optional flint_2.7.0-1.dsc 2e5026afad78b2690267379b75efa492 4943210 math optional flint_2.7.0.orig.tar.gz 24b5235d338d44638065fc974eeb13ab 6916 math optional flint_2.7.0-1.debian.tar.xz 72790a9745cbe02f241038887e007d81 9400 math optional flint_2.7.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAl/mVwoSHGpwdXlkdEBk ZWJpYW4ub3JnAAoJEATFO9f+AwVRWT0QAKbRcV45tQZJ6/rhg6D1fxrJpcBYoMqK xSnGaZKR3Y1JmZgftpp2Ty9Tw1SkZtGUGBVwNWJGcxoq8nW1iH3GkMotE2y/cwYW pB6htv7FCCZHFrBvtHPuVRdzOVDdlAJcfj7DVpBJM9JBSysxf51J3lfg9Mqp2Nkb u7UERGwG+khzakUi/XwITkM3CHhW1TjRrlTZbOOZrJmkzZZSEUfV2gnnr4nmkEMj aqxomYaoWhudtdwhMzaVMwwA3kegX8Jh3c7iBv7bSS2lHipOiBpFZSzE9ZNaeBe4 89To4LvFPDrtxDdwts1QtRf7WNa3P3dJrLDjYBWxTf1TfDTRo0dryCTICKMSvndb LHHV7e6BfIeRyXr4na7js4+DgHFav4u8ctQ7hvgLBsH41yMoqY3vLX0NbUu/dUNK RJxOkkqgxuUgc3uN3zm+o97LOBqGmgJFccyVbT1XKXTYv8sr3hJkpijkUhxAwFEP EQAYXFPLiSEa/8wrCUXZiv68HtPDMu4uwti09/2/3jDartjM8tE3bSDNJKUnVQOG AorFFnsAKuqg/7OsRhopU9vg8ebdNnSAevNly7ITRi3TZn8r1tTnNCMzi8fUXoHb 41NOc8QQ8cj2mgDZrZffLxvKHN1e38FW6/r8i3cvJQWrhw642cADKm48Ten1VyJQ xlystdPBZ6Zr =5w8b -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 libgtkdatabox_0.9.3.1-2_source.changes
libgtkdatabox_0.9.3.1-2_source.changes uploaded successfully to localhost along with the files: libgtkdatabox_0.9.3.1-2.dsc libgtkdatabox_0.9.3.1-2.debian.tar.xz 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
Bug#978017: opencascade: please, make dependency on libvtk7 optional
Hello Daniel, On Thursday, December 24, 2020 7:43:47 AM CST you wrote: > Source: opencascade > Version: 7.5.0+dfsg1-2 > Severity: wishlist > > Dear maintainer, > > Most applications depending on libocct-* libraries do not need the Vtk > visualization > (for example Kicad) and Vtk adds about 220MB of extra disk space. > > It would be great if the dependency to Vtk could be made optional (or a > recomends), so > that users that does not need the visuzalization can omit it. > > Regards, > > Daniel. > Indeed I see that libocct-data-exchange-dev, the dependency KiCad uses, has increased its install size on a base system +550 MB due to this dependency, even pulling in MySQL now. I will revert it with the next upload until a better solution can be found -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
libgtkdatabox_0.9.3.1-2_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 26 Dec 2020 15:40:57 + Source: libgtkdatabox Architecture: source Version: 1:0.9.3.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Graham Inggs Closes: 857776 977202 977405 Changes: libgtkdatabox (1:0.9.3.1-2) unstable; urgency=medium . * Team upload * Thanks Laurent Bigonville for the NMU (Closes: #977202) * Only ship AUTHORS, README in libgtkdatabox-doc (Closes: #977405) * Ship examples in libgtkdatabox-doc instead of libgtkdatabox-dev, fix symlinks (Closes: #857776) * Update Breaks+Replaces for relocated files * Do not patch generated files, fixes FTBFSx2 * Explicitly link libgtkdatabox against libm to avoid dpkg-shlibdeps warnings * Switch to debhelper 13 * Set Rules-Requires-Root: no * Add Build-Depends-Package: libgtkdatabox-dev to symbols file * Set Multi-Arch fields as per Multiarch hinter * Bump Standards-Version to 4.5.1, no changes Checksums-Sha1: eef52ffab0981c7115ba15c3fa339ba1ba793557 2277 libgtkdatabox_0.9.3.1-2.dsc 85c1ac50130064641605ca34a2218e89aa83d21f 10824 libgtkdatabox_0.9.3.1-2.debian.tar.xz Checksums-Sha256: 4ca3fcd22c7b1be9eabb32fd77bffb93e9da54c7d99869300ba1b7712523ce2b 2277 libgtkdatabox_0.9.3.1-2.dsc 50e84daac66bba9fe0812bb4d42411c0935dc2be00be6771351039754ff5da1f 10824 libgtkdatabox_0.9.3.1-2.debian.tar.xz Files: bee016a619b444a4c30a51061e046fe6 2277 science optional libgtkdatabox_0.9.3.1-2.dsc be6b38840d8003e4d00957091d4dee8d 10824 science optional libgtkdatabox_0.9.3.1-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAl/nWoEACgkQr8/sjmac 4cIX1RAAhAVtcY/k3ls+8/QAOoAtj0NLJZDxaDlCqW86m0fZogQ+M7jGWx8HAnl2 3OO18kWWkvoYZ6zS+sp4aq2bpLqJ4FuhyYhd86WPlGBNatUYFz6pDXh6NE2e/kNq lVWzwyu0KJW7v12h/J6brShpykajlSPsSns8dDrpZvEkwX+05JblyU2ct2bvsfDC VmvKAVfKXYk8dMI60UKsqy1vh8H+RiVNCWE7E4bVNVCmIf54aqkQ0ynL3kbSUsvY mVkqwtI++Iy89cVmhBlZXv4pbzaRmM7xD4GYD8kUz/fNs5uwDLbqrG66NIrhCyPU sYbLMFzBjR1NdXBF1ZnjY6DAyWfbucQBhV7k0eYHy36BMzvr3lm5orJahnsL+ADf wLPZ/0RQdxswXqNc0HyCwLjWkL7L5hXmS1Cq7WRLQUk36Uy4l69f8PTkGe4+7EBa kn6aZ7jt526HJ1Kswy/iCb+LoWW7HbbgFB/0/45ts1lH6Lt6cFZDftP+CSLMgmKu 7yfftPq0K7cOFRf4OwPtNjFQ3fLBqlEvEjgdLxIDEgr0trB9VNb3o7VOPSCJdAla ypgR9yV3JqDmRr3B/O2xbvhoV6xTyAoc/CXoVwyBbRjKqI2wWaxTiRuEImjOMUTS XJZK5Yz6n+tcl9YbUGBj32f+8gGviMsZJQG0dupHZEIK8TpHdTQ= =EJvp -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
Bug#857776: marked as done (libgtkdatabox-dev: broken symlink: /usr/share/gtk-doc/html/gtkdatabox -> ../../doc/libgtkdatabox-dev/html)
Your message dated Sat, 26 Dec 2020 16:05:34 + with message-id and subject line Bug#857776: fixed in libgtkdatabox 1:0.9.3.1-2 has caused the Debian Bug report #857776, regarding libgtkdatabox-dev: broken symlink: /usr/share/gtk-doc/html/gtkdatabox -> ../../doc/libgtkdatabox-dev/html to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 857776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgtkdatabox-dev Version: 1:0.9.3.0+dfsg-3 Severity: normal User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 2m24.5s ERROR: FAIL: Broken symlinks: /usr/share/gtk-doc/html/gtkdatabox -> ../../doc/libgtkdatabox-dev/html There is no /usr/share/doc/libgtkdatabox-dev/html in any package in Debian unstable. cheers, Andreas libgtkdatabox-dev_1:0.9.3.0+dfsg-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: libgtkdatabox Source-Version: 1:0.9.3.1-2 Done: Graham Inggs We believe that the bug you reported is fixed in the latest version of libgtkdatabox, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 857...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Graham Inggs (supplier of updated libgtkdatabox package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 26 Dec 2020 15:40:57 + Source: libgtkdatabox Architecture: source Version: 1:0.9.3.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Graham Inggs Closes: 857776 977202 977405 Changes: libgtkdatabox (1:0.9.3.1-2) unstable; urgency=medium . * Team upload * Thanks Laurent Bigonville for the NMU (Closes: #977202) * Only ship AUTHORS, README in libgtkdatabox-doc (Closes: #977405) * Ship examples in libgtkdatabox-doc instead of libgtkdatabox-dev, fix symlinks (Closes: #857776) * Update Breaks+Replaces for relocated files * Do not patch generated files, fixes FTBFSx2 * Explicitly link libgtkdatabox against libm to avoid dpkg-shlibdeps warnings * Switch to debhelper 13 * Set Rules-Requires-Root: no * Add Build-Depends-Package: libgtkdatabox-dev to symbols file * Set Multi-Arch fields as per Multiarch hinter * Bump Standards-Version to 4.5.1, no changes Checksums-Sha1: eef52ffab0981c7115ba15c3fa339ba1ba793557 2277 libgtkdatabox_0.9.3.1-2.dsc 85c1ac50130064641605ca34a2218e89aa83d21f 10824 libgtkdatabox_0.9.3.1-2.debian.tar.xz Checksums-Sha256: 4ca3fcd22c7b1be9eabb32fd77bffb93e9da54c7d99869300ba1b7712523ce2b 2277 libgtkdatabox_0.9.3.1-2.dsc 50e84daac66bba9fe0812bb4d42411c0935dc2be00be6771351039754ff5da1f 10824 libgtkdatabox_0.9.3.1-2.debian.tar.xz Files: bee016a619b444a4c30a51061e046fe6 2277 science optional libgtkdatabox_0.9.3.1-2.dsc be6b38840d8003e4d00957091d4dee8d 10824 science optional libgtkdatabox_0.9.3.1-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAl/nWoEACgkQr8/sjmac 4cIX1RAAhAVtcY/k3ls+8/QAOoAtj0NLJZDxaDlCqW86m0fZogQ+M7jGWx8HAnl2 3OO18kWWkvoYZ6zS+sp4aq2bpLqJ4FuhyYhd86WPlGBNatUYFz6pDXh6NE2e/kNq lVWzwyu0KJW7v12h/J6brShpykajlSPsSns8dDrpZvEkwX+05JblyU2ct2bvsfDC VmvKAVfKXYk8dMI60UKsqy1vh8H+RiVNCWE7E4bVNVCmIf54aqkQ0ynL3kbSUsvY mVkqwtI++Iy89cVmhBlZXv4pbzaRmM7xD4GYD8kUz/fNs5uwDLbqrG66NIrhCyPU sYbLMFzBjR1NdXBF1ZnjY6DAyWfbucQBhV7k0eYHy36BMzvr3lm5orJahnsL+ADf wLPZ/0RQdxswXqNc0HyCwLjWkL7L5hXmS1Cq7WRLQUk36Uy4l69f8PTkGe4+7EBa kn6aZ7jt526HJ1Kswy/iCb+LoWW7HbbgFB/0/45ts1lH6Lt6cFZDftP+CSLMgmKu 7yfftPq0K7cOFRf4OwPtNjFQ3fLBqlEvEjgdLxIDEgr0trB9VNb3o7VOPSCJdAla ypgR9yV3JqDmRr3B/O2xbvhoV6xTyAoc/CXoVwyBbRjKqI2wWaxTiRuEImjOMUTS XJZK5Yz6n+tcl9YbUGBj32f+8gGviMsZJQG0dupHZEIK8TpHdTQ= =EJvp -END PGP SIGNATURE End Message --- -- 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#977405: marked as done (libgtkdatabox-dev,libgtkdatabox-doc: both ship /usr/share/doc/libgtkdatabox-dev/{AUTHORS,README})
Your message dated Sat, 26 Dec 2020 16:05:34 +
with message-id
and subject line Bug#977405: fixed in libgtkdatabox 1:0.9.3.1-2
has caused the Debian Bug report #977405,
regarding libgtkdatabox-dev,libgtkdatabox-doc: both ship
/usr/share/doc/libgtkdatabox-dev/{AUTHORS,README}
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
977405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977405
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgtkdatabox-dev,libgtkdatabox-doc
Version: 1:0.9.3.1-1.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
>From the attached log (scroll to the bottom...):
Preparing to unpack .../libgtkdatabox-doc_1%3a0.9.3.1-1.1_all.deb ...
Unpacking libgtkdatabox-doc (1:0.9.3.1-1.1) ...
dpkg: error processing archive
/var/cache/apt/archives/libgtkdatabox-doc_1%3a0.9.3.1-1.1_all.deb (--unpack):
trying to overwrite '/usr/share/doc/libgtkdatabox-dev/AUTHORS', which is
also in package libgtkdatabox-dev 1:0.9.3.1-1.1+b1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/libgtkdatabox-doc_1%3a0.9.3.1-1.1_all.deb
cheers,
Andreas
libgtkdatabox-dev=1:0.9.3.1-1.1+b1_libgtkdatabox-doc=1:0.9.3.1-1.1.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libgtkdatabox
Source-Version: 1:0.9.3.1-2
Done: Graham Inggs
We believe that the bug you reported is fixed in the latest version of
libgtkdatabox, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Graham Inggs (supplier of updated libgtkdatabox package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 26 Dec 2020 15:40:57 +
Source: libgtkdatabox
Architecture: source
Version: 1:0.9.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Graham Inggs
Closes: 857776 977202 977405
Changes:
libgtkdatabox (1:0.9.3.1-2) unstable; urgency=medium
.
* Team upload
* Thanks Laurent Bigonville for the NMU (Closes: #977202)
* Only ship AUTHORS, README in libgtkdatabox-doc (Closes: #977405)
* Ship examples in libgtkdatabox-doc instead of libgtkdatabox-dev,
fix symlinks (Closes: #857776)
* Update Breaks+Replaces for relocated files
* Do not patch generated files, fixes FTBFSx2
* Explicitly link libgtkdatabox against libm to avoid
dpkg-shlibdeps warnings
* Switch to debhelper 13
* Set Rules-Requires-Root: no
* Add Build-Depends-Package: libgtkdatabox-dev to symbols file
* Set Multi-Arch fields as per Multiarch hinter
* Bump Standards-Version to 4.5.1, no changes
Checksums-Sha1:
eef52ffab0981c7115ba15c3fa339ba1ba793557 2277 libgtkdatabox_0.9.3.1-2.dsc
85c1ac50130064641605ca34a2218e89aa83d21f 10824
libgtkdatabox_0.9.3.1-2.debian.tar.xz
Checksums-Sha256:
4ca3fcd22c7b1be9eabb32fd77bffb93e9da54c7d99869300ba1b7712523ce2b 2277
libgtkdatabox_0.9.3.1-2.dsc
50e84daac66bba9fe0812bb4d42411c0935dc2be00be6771351039754ff5da1f 10824
libgtkdatabox_0.9.3.1-2.debian.tar.xz
Files:
bee016a619b444a4c30a51061e046fe6 2277 science optional
libgtkdatabox_0.9.3.1-2.dsc
be6b38840d8003e4d00957091d4dee8d 10824 science optional
libgtkdatabox_0.9.3.1-2.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAl/nWoEACgkQr8/sjmac
4cIX1RAAhAVtcY/k3ls+8/QAOoAtj0NLJZDxaDlCqW86m0fZogQ+M7jGWx8HAnl2
3OO18kWWkvoYZ6zS+sp4aq2bpLqJ4FuhyYhd86WPlGBNatUYFz6pDXh6NE2e/kNq
lVWzwyu0KJW7v12h/J6brShpykajlSPsSns8dDrpZvEkwX+05JblyU2ct2bvsfDC
VmvKAVfKXYk8dMI60UKsqy1vh8H+RiVNCWE7E4bVNVCmIf54aqkQ0ynL3kbSUsvY
mVkqwtI++Iy89cVmhBlZXv4pbzaRmM7xD4GYD8kUz/fNs5uwDLbqrG66NIrhCyPU
sYbLMFzBjR1NdXBF1ZnjY6DAyWfbucQBhV7k0eYHy36BMzvr3lm5orJahnsL+ADf
wLPZ/0RQdxswXqNc0HyCwLjWkL7L5hXmS1Cq7WRLQUk36Uy4l69f8PTkGe4+7EBa
kn6aZ7jt526HJ1Kswy/iCb+LoWW7HbbgFB/0/45ts1lH6Lt6cFZDftP+CSLMgmKu
7yfftPq0K7cOFRf4OwPtNjFQ3fLBqlEvEjgdLxIDEgr0trB9VNb3o7VOPSCJdAla
yp
Bug#977202: marked as done (libgtkdatabox: diff for NMU version 1:0.9.3.1-1.1)
Your message dated Sat, 26 Dec 2020 16:05:34 +
with message-id
and subject line Bug#977202: fixed in libgtkdatabox 1:0.9.3.1-2
has caused the Debian Bug report #977202,
regarding libgtkdatabox: diff for NMU version 1:0.9.3.1-1.1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
977202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977202
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgtkdatabox
Version: 1:0.9.3.1-1
Severity: normal
Tags: patch pending
Dear maintainer,
I've prepared an NMU for libgtkdatabox (versioned as 1:0.9.3.1-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru libgtkdatabox-0.9.3.1/debian/changelog
libgtkdatabox-0.9.3.1/debian/changelog
--- libgtkdatabox-0.9.3.1/debian/changelog 2019-01-13 12:50:01.0
+0100
+++ libgtkdatabox-0.9.3.1/debian/changelog 2020-12-12 14:19:46.0
+0100
@@ -1,3 +1,18 @@
+libgtkdatabox (1:0.9.3.1-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop libgtkdatabox0-libglade package and stop using ancient libglade2
+(Closes: #653827, #967875)
+ * Drop libgtkdatabox0-glade package, there is a mix between GTK+2.0 and
+GTK+3.0 headers when compiled with the newer version of glade. This fix a
+FTBFS with glade 3.38 (Closes: #977184)
+ * Remove Ramakrishnan Muthukrishnan from the Uploaders list, thanks to him
+for his past work on the package (Closes: #859284)
+ * debian/patches/cross.patch: Fix cross-compilation, thanks Helmut Grohne
+for the patch (Closes: #894046)
+
+ -- Laurent Bigonville Sat, 12 Dec 2020 14:19:46 +0100
+
libgtkdatabox (1:0.9.3.1-1) unstable; urgency=medium
* New upstream version
diff -Nru libgtkdatabox-0.9.3.1/debian/control
libgtkdatabox-0.9.3.1/debian/control
--- libgtkdatabox-0.9.3.1/debian/control2019-01-13 12:50:01.0
+0100
+++ libgtkdatabox-0.9.3.1/debian/control2020-12-12 14:19:46.0
+0100
@@ -1,7 +1,6 @@
Source: libgtkdatabox
Maintainer: Debian Science Maintainers
-Uploaders: Ramakrishnan Muthukrishnan ,
- Andreas Tille ,
+Uploaders: Andreas Tille ,
Daniele E. Domenichelli
Section: science
Priority: optional
@@ -10,9 +9,7 @@
libgtk2.0-dev,
libcairo2-dev,
libpango1.0-dev,
- gtk-doc-tools,
- libglade2-dev,
- libgladeui-dev
+ gtk-doc-tools
Standards-Version: 4.3.0
Vcs-Browser: https://salsa.debian.org/science-team/libgtkdatabox
Vcs-Git: https://salsa.debian.org/science-team/libgtkdatabox.git
@@ -67,56 +64,6 @@
coordinates, thus allowing you to easily create powerful applications for
data analysis.
-Package: libgtkdatabox0-glade
-Architecture: any
-Depends: ${shlibs:Depends},
- ${misc:Depends}
-Conflicts: libgtkdatabox-0.9.2-0-glade,
- libgtkdatabox-0.9.3-0-glade
-Replaces: libgtkdatabox-0.9.2-0-glade,
- libgtkdatabox-0.9.3-0-glade
-Description: Gtk+ library to display large amounts of numerical data (glade
API)
- One or more data sets of thousands of data points (X and Y coordinate) may be
- displayed and updated in split seconds. The widget is therefore used in many
- scientific and private projects that need to show quickly changing data live.
- GtkDatabox offers the ability to zoom into and out of the data and to navigate
- through your data by scrolling.
- .
- In addition to rulers and a simple coordinate cross, GtkDatabox now also
allows
- you to add one (or even more) configurable grids like on an oscilloscope.
- .
- Data may be presented as dots, lines connecting the data, or vertical bars.
- The widget allows you to easily transform pixel coordinates into data
- coordinates, thus allowing you to easily create powerful applications for
- data analysis.
- .
- Modules for GUI development with Glade3
-
-Package: libgtkdatabox0-libglade
-Architecture: any
-Depends: ${shlibs:Depends},
- ${misc:Depends}
-Conflicts: libgtkdatabox-0.9.2-0-libglade,
- libgtkdatabox-0.9.3-0-libglade
-Replaces: libgtkdatabox-0.9.2-0-libglade,
- libgtkdatabox-0.9.3-0-libglade
-Description: Gtk+ library to display large amounts of numerical data (glade
lib)
- One or more data sets of thousands of data points (X and Y coordinate) may be
- displayed and updated in split seconds. The widget is therefore used in many
- scientific and private projects that need to show quickly changing data live.
- GtkDatabox offers the ability to zoom into and out of the data and
Processing of ipe_7.2.23+dfsg1-1_amd64.changes
ipe_7.2.23+dfsg1-1_amd64.changes uploaded successfully to localhost along with the files: ipe_7.2.23+dfsg1-1.dsc ipe_7.2.23+dfsg1.orig.tar.xz ipe_7.2.23+dfsg1-1.debian.tar.xz ipe-dbgsym_7.2.23+dfsg1-1_amd64.deb ipe_7.2.23+dfsg1-1_amd64.buildinfo ipe_7.2.23+dfsg1-1_amd64.deb libipe-dev_7.2.23+dfsg1-1_amd64.deb libipe7.2.23-dbgsym_7.2.23+dfsg1-1_amd64.deb libipe7.2.23_7.2.23+dfsg1-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
Bug#810659: is hardened1-linux-any still a thing?
Hi Bálint, is hardened1-linux-any still a thing? I haven't seen any activity nor bootstrapping efforts on this in a while. If this is a dead end, I suggest closing the Cced gmp bug #810659. Helmut -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
ipe_7.2.23+dfsg1-1_amd64.changes is NEW
binary:libipe7.2.23 is NEW. binary:libipe7.2.23 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
Bug#810659: is hardened1-linux-any still a thing?
Control: close -1 Hi Helmut, Helmut Grohne ezt írta (időpont: 2020. dec. 26., Szo, 17:40): > > Hi Bálint, > > is hardened1-linux-any still a thing? I haven't seen any activity nor > bootstrapping efforts on this in a while. If this is a dead end, I > suggest closing the Cced gmp bug #810659. I think hardened1-linux-any could still be useful but I'm not working on it at the moment or in the foreseeable future. I agree that there is little point in keeping this bug open. Cheers, Balint -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Processed: Re: is hardened1-linux-any still a thing?
Processing control commands: > close -1 Bug #810659 [libgmp10] libgmp10: Please allow building on hardened1-linux-amd64 Marked Bug as done -- 810659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810659 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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 skimage_0.18.1-1_source.changes
skimage_0.18.1-1_source.changes uploaded successfully to localhost along with the files: skimage_0.18.1-1.dsc skimage_0.18.1.orig.tar.gz skimage_0.18.1-1.debian.tar.xz 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
skimage_0.18.1-1_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 26 Dec 2020 13:42:34 +0100 Source: skimage Architecture: source Version: 0.18.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Ole Streicher Changes: skimage (0.18.1-1) unstable; urgency=medium . * New upstream version 0.18.1 Checksums-Sha1: f8e9e0be12b51630fc9b485338e0bcb52030d9cf 2905 skimage_0.18.1-1.dsc 25e70a731e417af7c3b9982d63f64cf36f2a881b 22750803 skimage_0.18.1.orig.tar.gz c197cdc4aa4dcbb04625f2c53408bd19c7413d52 23964 skimage_0.18.1-1.debian.tar.xz Checksums-Sha256: 7f61ffef038e007c5b8a9fb6a76564bc86b450731877ddd5f753b8c96b34955e 2905 skimage_0.18.1-1.dsc f9a603d3f5b451ac2e6b9e09bb896396067aba9faa12cdeee77225a47a736d48 22750803 skimage_0.18.1.orig.tar.gz d2bd066f59e43d0cd813144d160e21702d80b10d7af20ec7864e2e819bac5dc1 23964 skimage_0.18.1-1.debian.tar.xz Files: 134a9aca511d22a02cda934e80c51c32 2905 python optional skimage_0.18.1-1.dsc 145a465ee5c679f3ebb03abe5079d779 22750803 python optional skimage_0.18.1.orig.tar.gz ec6b5c5bbee2a93ed1e6f010616fdc5e 23964 python optional skimage_0.18.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAl/ngkIACgkQcRWv0HcQ 3PcPuhAAgi1VDPiQxDICOO8J+wYh90gWm+R+hnnmJ4Pjmp587r4m1h+3OGewdHNo /y9fo/xDTqMlEocit3O0CKuhFKY1t4/H5+X229s8hVP+dqM5WbLMj+g3h1GKuaHl 6lWvUq6qvuG0yhdtD7OJwnoxMF0IxBtYvshpbGG8S7FVIP85Ey3RvIXjGELW55Hv cVDkGzwXl/145jPP9WvGQABaEuB5PmZqVmD8yJfJMyxSnjejGr1FzLyha2Rk/ch0 ue1jVpNBaGO9s3ufg6ZjLkIbU6DjkJ1SDRWfZCKWEdyAKa/WMlPVMTcxdHosLCTk ipqykTf9JFSRd2o39A/ddPrZ6VR40/pUDZeF9oTSCJfvwIJhyuv/zbYYQquCrJE4 VO81wATd3ns4My/3HkjJANragqWzL4jHBGA1Q84Dpxbd8TZ65PCI+zV18oFXvrph Abj5IAE7bvpFqCva+zQrk4HD73l8rGNt8eXzkQ7PNtOwYXBdCEgds7W8um0Cum8u zyEoY+CA+MTp+kKbE1llkFqlBjMZxf6J9TA39HytAE4HVk42XJk+XdnSjLSdZvmD unlGhVz9tP4Fa0HSgFYh7IFiafMjVn3wkCuL1zygby818xs8xywfnjZ51ZAO+h52 tk4GIWWn0+ZIvz8uzBTM+5FcfkQZvCTXukytQlCodTVli9PB6ac= =Bsl6 -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
Bug#973154: marked as done (apertium-kaz-tat: FTBFS: hfst-concatenate: .deps/any-symbol.hfst is not a valid transducer file)
Your message dated Sat, 26 Dec 2020 21:32:15 +0100 with message-id <20201226203215.ga...@xanadu.blop.info> and subject line Re: Bug#973154: apertium-kaz-tat: FTBFS: hfst-concatenate: .deps/any-symbol.hfst is not a valid transducer file has caused the Debian Bug report #973154, regarding apertium-kaz-tat: FTBFS: hfst-concatenate: .deps/any-symbol.hfst is not a valid transducer file to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 973154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-kaz-tat Version: 0.2.1~r57554-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > apertium-validate-dictionary apertium-kaz-tat.kaz-tat.dix > apertium-validate-dictionary apertium-kaz-tat.kaz-tat.dix > /bin/mkdir -p .deps > apertium-validate-dictionary apertium-kaz-tat.post-kaz.dix > touch .deps/.d > cp /usr/share/apertium/apertium-tat/tat.autogen.bin kaz-tat.autogen.bin > apertium-validate-transfer apertium-kaz-tat.kaz-tat.t1x > lt-comp lr apertium-kaz-tat.post-kaz.dix kaz-tat.autopgen.bin > apertium-preprocess-transfer apertium-kaz-tat.kaz-tat.t1x kaz-tat.t1x.bin > apertium-validate-transfer apertium-kaz-tat.kaz-tat.t2x > apertium-preprocess-transfer apertium-kaz-tat.kaz-tat.t2x kaz-tat.t2x.bin > apertium-validate-dictionary apertium-kaz-tat.post-tat.dix > lt-comp lr apertium-kaz-tat.post-tat.dix tat-kaz.autopgen.bin > main@standard 16 356 > cp /usr/share/apertium/apertium-kaz/kaz.autogen.bin tat-kaz.autogen.bin > apertium-validate-transfer apertium-kaz-tat.tat-kaz.t1x > apertium-preprocess-transfer apertium-kaz-tat.tat-kaz.t1x tat-kaz.t1x.bin > apertium-validate-transfer apertium-kaz-tat.tat-kaz.t2x > apertium-preprocess-transfer apertium-kaz-tat.tat-kaz.t2x tat-kaz.t2x.bin > main@standard 10 149 > cg-comp /usr/share/apertium/apertium-kaz/apertium-kaz.kaz.rlx kaz-tat.rlx.bin > cg-comp /usr/share/apertium/apertium-tat/apertium-tat.tat.rlx tat-kaz.rlx.bin > apertium-kaz.kaz.rlx: Warning: Expected closing ; on line 305 after previous > rule! > apertium-kaz.kaz.rlx: Warning: Expected closing ; on line 937 after previous > rule! > apertium-kaz.kaz.rlx: Warning: Expected closing ; on line 1031 after previous > rule! > Sections: 10, Rules: 109, Sets: 136, Tags: 177 > Sections: 2, Rules: 125, Sets: 163, Tags: 193 > 1 rules cannot be skipped by index. > lrx-comp apertium-kaz-tat.kaz-tat.lrx kaz-tat.lrx.bin > lrx-comp apertium-kaz-tat.tat-kaz.lrx tat-kaz.lrx.bin > 3: 49@52 > lt-comp lr apertium-kaz-tat.kaz-tat.dix kaz-tat.autobil.bin > lt-comp rl apertium-kaz-tat.kaz-tat.dix tat-kaz.autobil.bin > apertium-validate-modes modes.xml > 41: 961@1068 > apertium-gen-modes modes.xml > main@standard 18624 27929 > lt-print kaz-tat.autobil.bin | sed 's/ /@_SPACE_@/g' > > .deps/kaz-tat.autobil.att > main@standard 18604 27876 > lt-print tat-kaz.autobil.bin | sed 's/ /@_SPACE_@/g' > > .deps/tat-kaz.autobil.att > hfst-txt2fst -e ε < .deps/kaz-tat.autobil.att > .deps/kaz-tat.autobil.hfst > hfst-txt2fst -e ε < .deps/tat-kaz.autobil.att > .deps/tat-kaz.autobil.hfst > hfst-project -p upper .deps/kaz-tat.autobil.hfst > .deps/kaz-tat.autobil.upper > hfst-project -p upper .deps/tat-kaz.autobil.hfst > .deps/tat-kaz.autobil.upper > echo " ?* " | hfst-regexp2fst > .deps/any-symbol.hfst > hfst-concatenate -1 .deps/kaz-tat.autobil.upper -2 .deps/any-symbol.hfst -o > .deps/kaz-tat.autobil.prefixes > echo " ?* " | hfst-regexp2fst > .deps/any-symbol.hfst > hfst-concatenate: .deps/any-symbol.hfst is not a valid transducer file > make[1]: *** [Makefile:725: .deps/kaz-tat.autobil.prefixes] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/10/27/apertium-kaz-tat_0.2.1~r57554-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Hi, On 24/12/20 at 14:53 +0200, Graham Inggs wrote: > HI Nilesh > > On Thu, 24 Dec 2020 at 10:48, Nilesh wrote: > > > > I can't seem to reproduce this, can you initiate a rebuild for this? > > > > I suspect if new apertium upload fixed this s
Bug#978175: petsc4py: FTBFS: src/petsc4py.PETSc.c:330930:43: error: ‘MATDAAD’ undeclared (first use in this function)
Source: petsc4py Version: 3.14.0-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > PYBUILD_NAME=petsc4py_real3.14 > PETSC_DIR=/usr/lib/petscdir/petsc3.14/x86_64-linux-gnu-real dh_auto_build > -ppython3-petsc4py-real3.14 -- --build-args=--force > I: pybuild base:232: /usr/bin/python3 setup.py build --force > running build > running build_src > cythonizing 'petsc4py.PETSc.pyx' -> 'petsc4py.PETSc.c' > /usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning: > Cython directive 'language_level' not set, using 2 for now (Py2). This will > change in a later release! File: include/petsc4py/PETSc.pxd > tree = Parsing.p_module(s, pxd, full_module_name) > cythonizing 'libpetsc4py/libpetsc4py.pyx' -> 'libpetsc4py/libpetsc4py.c' > /usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning: > Cython directive 'language_level' not set, using 2 for now (Py2). This will > change in a later release! File: > /<>/src/libpetsc4py/libpetsc4py.pyx > tree = Parsing.p_module(s, pxd, full_module_name) > running build_py > creating > /<>/.pybuild/cpython3_3.9_petsc4py_real3.14/build/petsc4py > copying src/__init__.py -> > /<>/.pybuild/cpython3_3.9_petsc4py_real3.14/build/petsc4py > copying src/__main__.py -> > /<>/.pybuild/cpython3_3.9_petsc4py_real3.14/build/petsc4py > copying src/PETSc.py -> > /<>/.pybuild/cpython3_3.9_petsc4py_real3.14/build/petsc4py > creating > /<>/.pybuild/cpython3_3.9_petsc4py_real3.14/build/petsc4py/lib > copying src/lib/__init__.py -> > /<>/.pybuild/cpython3_3.9_petsc4py_real3.14/build/petsc4py/lib > creating > /<>/.pybuild/cpython3_3.9_petsc4py_real3.14/build/petsc4py/include > creating > /<>/.pybuild/cpython3_3.9_petsc4py_real3.14/build/petsc4py/include/petsc4py > copying src/include/petsc4py/petsc4py.PETSc_api.h -> > /<>/.pybuild/cpython3_3.9_petsc4py_real3.14/build/petsc4py/include/petsc4py > copying src/include/petsc4py/petsc4py.h -> > /<>/.pybuild/cpython3_3.9_petsc4py_real3.14/build/petsc4py/include/petsc4py > copying src/include/petsc4py/numpy.h -> > /<>/.pybuild/cpython3_3.9_petsc4py_real3.14/build/petsc4py/include/petsc4py > copying src/include/petsc4py/petsc4py.PETSc.h -> > /<>/.pybuild/cpython3_3.9_petsc4py_real3.14/build/petsc4py/include/petsc4py > copying src/include/petsc4py/petsc4py.i -> > /<>/.pybuild/cpython3_3.9_petsc4py_real3.14/build/petsc4py/include/petsc4py > copying src/include/petsc4py/__init__.pxd -> > /<>/.pybuild/cpython3_3.9_petsc4py_real3.14/build/petsc4py/include/petsc4py > copying src/include/petsc4py/PETSc.pxd -> > /<>/.pybuild/cpython3_3.9_petsc4py_real3.14/build/petsc4py/include/petsc4py > copying src/include/petsc4py/__init__.pyx -> > /<>/.pybuild/cpython3_3.9_petsc4py_real3.14/build/petsc4py/include/petsc4py > copying src/PETSc.pxd -> > /<>/.pybuild/cpython3_3.9_petsc4py_real3.14/build/petsc4py > copying src/lib/petsc.cfg -> > /<>/.pybuild/cpython3_3.9_petsc4py_real3.14/build/petsc4py/lib > running build_ext > PETSC_DIR:/usr/lib/petscdir/petsc3.14/x86_64-linux-gnu-real > PETSC_ARCH: > version: 3.14.2 release > integer-size: 32-bit > scalar-type: real > precision:double > language: CONLY > compiler: mpicc > linker: mpicc > building 'PETSc' extension > creating build > creating build/temp.linux-x86_64-3.9 > creating build/temp.linux-x86_64-3.9/src > mpicc -pthread -g -O2 -fstack-protector-strong -Wformat > -Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -I/usr/include/hdf5/openmpi -I/usr/include/scotch > -I/usr/include/superlu-dist -I/usr/include/superlu -I/usr/include/suitesparse > -I/usr/include/hypre > -I/usr/lib/petscdir/petsc3.14/x86_64-linux-gnu-real/include -Isrc/include > -I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include/python3.9 > -c src/PETSc.c -o build/temp.linux-x86_64-3.9/src/PETSc.o > In file included from src/PETSc.c:4: > src/petsc4py.PETSc.c: In function ‘__pyx_pymod_exec_PETSc’: > src/petsc4py.PETSc.c:330930:43: error: ‘MATDAAD’ undeclared (first use in > this function) > 330930 | __pyx_t_7 = __pyx_f_8petsc4py_5PETSc_S_(MATDAAD); if > (unlikely(!__pyx_t_7)) __PYX_ERR(38, 49, __pyx_L1_error)
Bug#978180: dune-functions: FTBFS: tests failed
Source: dune-functions Version: 2.7.0-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[5]: Entering directory '/<>/build' > make[5]: Nothing to be done for 'CMakeFiles/build_tests.dir/build'. > make[5]: Leaving directory '/<>/build' > [100%] Built target build_tests > make[4]: Leaving directory '/<>/build' > /usr/bin/cmake -E cmake_progress_start /<>/build/CMakeFiles 0 > make[3]: Leaving directory '/<>/build' > make[2]: Leaving directory '/<>/build' > cd build; PATH=/<>/debian/tmp-test:$PATH /usr/bin/dune-ctest >Site: ip-172-31-9-132 >Build name: Linux-c++ > Create new tag: 20201226-1834 - Experimental > Test project /<>/build > Start 1: istlvectorbackendtest > 1/17 Test #1: istlvectorbackendtest .***Failed0.04 sec > [ip-172-31-9-132:11006] [[23070,0],0] ORTE_ERROR_LOG: Not found in file > ../../../../../../orte/mca/ess/hnp/ess_hnp_module.c at line 320 > -- > It looks like orte_init failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during orte_init; some of which are due to configuration or > environment problems. This failure appears to be an internal failure; > here's some additional information (which may only be relevant to an > Open MPI developer): > > opal_pmix_base_select failed > --> Returned value Not found (-13) instead of ORTE_SUCCESS > -- > [ip-172-31-9-132:11005] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start a > daemon on the local node in file > ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 716 > [ip-172-31-9-132:11005] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start a > daemon on the local node in file > ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 172 > -- > It looks like orte_init failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during orte_init; some of which are due to configuration or > environment problems. This failure appears to be an internal failure; > here's some additional information (which may only be relevant to an > Open MPI developer): > > orte_ess_init failed > --> Returned value Unable to start a daemon on the local node (-127) > instead of ORTE_SUCCESS > -- > -- > It looks like MPI_INIT failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during MPI_INIT; some of which are due to configuration or environment > problems. This failure appears to be an internal failure; here's some > additional information (which may only be relevant to an Open MPI > developer): > > ompi_mpi_init: ompi_rte_init failed > --> Returned "Unable to start a daemon on the local node" (-127) instead of > "Success" (0) > -- > *** An error occurred in MPI_Init > *** on a NULL communicator > *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort, > ***and potentially your MPI job) > [ip-172-31-9-132:11005] Local abort before MPI_INIT completed completed > successfully, but am not able to aggregate error messages, and not able to > guarantee that all other processes were killed! > > Start 2: differentiablefunctiontest > 2/17 Test #2: differentiablefunctiontest ***Failed0.02 sec > [ip-172-31-9-132:11008] [[23520,0],0] ORTE_ERROR_LOG: Not found in file > ../../../../../../orte/mca/ess/hnp/ess_hnp_module.c at line 320 > -- > It looks like orte_init failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during orte_init; some of which are due to configuration or > environment problems. This failure appears to be an internal failure; > here's some additional information (which may only be relevant to an > Open MPI developer): > > opal_pmix_base_select failed > --> Return
Bug#978193: mpi4py: FTBFS: ld: cannot find -llmpe
Source: mpi4py Version: 3.0.3-7 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build override_dh_auto_build-arch -- \ > --build-args "--mpicc=/usr/bin/mpicc --mpicxx=/usr/bin/mpicxx" > I: pybuild base:232: /usr/bin/python3 setup.py build --mpicc=/usr/bin/mpicc > --mpicxx=/usr/bin/mpicxx > running build > running build_src > running build_py > creating /<>/.pybuild/cpython3_3.9/build/mpi4py > copying src/mpi4py/bench.py -> > /<>/.pybuild/cpython3_3.9/build/mpi4py > copying src/mpi4py/__init__.py -> > /<>/.pybuild/cpython3_3.9/build/mpi4py > copying src/mpi4py/__main__.py -> > /<>/.pybuild/cpython3_3.9/build/mpi4py > copying src/mpi4py/run.py -> > /<>/.pybuild/cpython3_3.9/build/mpi4py > creating /<>/.pybuild/cpython3_3.9/build/mpi4py/futures > copying src/mpi4py/futures/__init__.py -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/futures > copying src/mpi4py/futures/__main__.py -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/futures > copying src/mpi4py/futures/_base.py -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/futures > copying src/mpi4py/futures/pool.py -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/futures > copying src/mpi4py/futures/aplus.py -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/futures > copying src/mpi4py/futures/_lib.py -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/futures > copying src/mpi4py/futures/server.py -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/futures > copying src/mpi4py/libmpi.pxd -> > /<>/.pybuild/cpython3_3.9/build/mpi4py > copying src/mpi4py/__init__.pxd -> > /<>/.pybuild/cpython3_3.9/build/mpi4py > copying src/mpi4py/MPI.pxd -> > /<>/.pybuild/cpython3_3.9/build/mpi4py > creating /<>/.pybuild/cpython3_3.9/build/mpi4py/include > creating /<>/.pybuild/cpython3_3.9/build/mpi4py/include/mpi4py > copying src/mpi4py/include/mpi4py/mpi4py.h -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/include/mpi4py > copying src/mpi4py/include/mpi4py/mpi4py.MPI_api.h -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/include/mpi4py > copying src/mpi4py/include/mpi4py/mpi4py.MPI.h -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/include/mpi4py > copying src/mpi4py/include/mpi4py/mpi4py.i -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/include/mpi4py > copying src/mpi4py/include/mpi4py/mpi.pxi -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/include/mpi4py > running build_clib > MPI configuration: [mpi] from 'mpi.cfg' > MPI C compiler:/usr/bin/mpicc > MPI C++ compiler: /usr/bin/mpicxx > checking for library 'lmpe' ... > /usr/bin/mpicc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv > -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g > -fwrapv -O2 -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -fPIC -c _configtest.c -o _configtest.o > /usr/bin/mpicc -pthread -Wl,-z,relro -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 _configtest.o -llmpe > -o _configtest > /usr/bin/ld: cannot find -llmpe > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/12/26/mpi4py_3.0.3-7_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- 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#978206: dolfin: FTBFS: MixedLinearVariationalSolver.cpp:240:23: error: variable ‘dolfin::PETScNestMatrix A’ has initializer but incomplete type
Source: dolfin
Version: 2019.2.0~git20200629.946dbd3+lfs-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd "/<>/obj-x86_64-linux-gnu/dolfin" && /usr/bin/c++
> -DDOLFIN_VERSION=\"2019.2.0.dev0\" -DHAS_CHOLMOD -DHAS_HDF5 -DHAS_MPI
> -DHAS_UMFPACK -DHAS_ZLIB -DNDEBUG -Ddolfin_EXPORTS -I"/<>"
> -I"/<>/obj-x86_64-linux-gnu" -isystem
> /usr/lib/python3/dist-packages/ffc/backends/ufc -isystem /usr/include/eigen3
> -isystem /usr/include/hdf5/openmpi -isystem /usr/include/suitesparse -isystem
> /usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -isystem
> /usr/lib/x86_64-linux-gnu/openmpi/include -fpermissive -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -O2 -g -DNDEBUG
> -fPIC -std=c++11 -o
> CMakeFiles/dolfin.dir/fem/MixedLinearVariationalSolver.cpp.o -c
> "/<>/dolfin/fem/MixedLinearVariationalSolver.cpp"
> /<>/dolfin/fem/MixedLinearVariationalSolver.cpp: In member
> function ‘void
> dolfin::MixedLinearVariationalSolver::solve(dolfin::MixedLinearVariationalSolver::assembled_system_type)’:
> /<>/dolfin/fem/MixedLinearVariationalSolver.cpp:240:23: error:
> variable ‘dolfin::PETScNestMatrix A’ has initializer but incomplete type
> 240 | PETScNestMatrix A(As);
> | ^
> /<>/dolfin/fem/MixedLinearVariationalSolver.cpp:281:5: error:
> ‘PETScLUSolver’ was not declared in this scope
> 281 | PETScLUSolver solver(comm, solver_type);
> | ^
> /<>/dolfin/fem/MixedLinearVariationalSolver.cpp:285:5: error:
> ‘solver’ was not declared in this scope; did you mean ‘solve’?
> 285 | solver.set_operator(A);
> | ^~
> | solve
> /<>/dolfin/fem/MixedLinearVariationalSolver.cpp:290:5: error:
> ‘PETScKrylovSolver’ was not declared in this scope
> 290 | PETScKrylovSolver solver(comm, solver_type, pc_type);
> | ^
> /<>/dolfin/fem/MixedLinearVariationalSolver.cpp:291:5: error:
> ‘solver’ was not declared in this scope; did you mean ‘solve’?
> 291 | solver.parameters.update(parameters("krylov_solver"));
> | ^~
> | solve
> /<>/dolfin/fem/MixedLinearVariationalSolver.cpp:303:13: error:
> ‘PETScVector’ was not declared in this scope
> 303 | as_type(u)->update_ghost_values();
> | ^~~
> /<>/dolfin/fem/MixedLinearVariationalSolver.cpp:303:27: error:
> no matching function for call to ‘as_type<
> >(std::shared_ptr&)’
> 303 | as_type(u)->update_ghost_values();
> | ^
> In file included from /<>/dolfin/la/GenericTensor.h:38,
> from /<>/dolfin/la/GenericMatrix.h:34,
> from
> /<>/dolfin/fem/MixedLinearVariationalSolver.cpp:27:
> /<>/dolfin/la/LinearAlgebraObject.h:64:8: note: candidate:
> ‘template Y& dolfin::as_type(X&)’
>64 | Y& as_type(X& x)
> |^~~
> /<>/dolfin/la/LinearAlgebraObject.h:64:8: note: template
> argument deduction/substitution failed:
> /<>/dolfin/fem/MixedLinearVariationalSolver.cpp:303:27: error:
> template argument 1 is invalid
> 303 | as_type(u)->update_ghost_values();
> | ^
> In file included from /<>/dolfin/la/GenericTensor.h:38,
> from /<>/dolfin/la/GenericMatrix.h:34,
> from
> /<>/dolfin/fem/MixedLinearVariationalSolver.cpp:27:
> /<>/dolfin/la/LinearAlgebraObject.h:84:24: note: candidate:
> ‘template std::shared_ptr<_Tp>
> dolfin::as_type(std::shared_ptr<_Tp>)’
>84 | std::shared_ptr as_type(std::shared_ptr x)
> |^~~
> /<>/dolfin/la/LinearAlgebraObject.h:84:24: note: template
> argument deduction/substitution failed:
> /<>/dolfin/fem/MixedLinearVariationalSolver.cpp:303:27: error:
> template argument 1 is invalid
> 303 | as_type(u)->update_ghost_values();
> | ^
> make[4]: *** [dolfin/CMakeFiles/dolfin.dir/build.make:618:
> dolfin/CMakeFiles/dolfin.dir/fem/MixedLinearVariationalSolver.cpp.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/12/26/dolfin_2019.2.0~git20200629.946dbd3+lfs-4_unstable.log
A list of current com
Bug#978211: dune-common: FTBFS: tests failed
Source: dune-common Version: 2.7.0-5 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[5]: Entering directory '/<>/build' > make[5]: Nothing to be done for 'CMakeFiles/build_tests.dir/build'. > make[5]: Leaving directory '/<>/build' > [100%] Built target build_tests > make[4]: Leaving directory '/<>/build' > /usr/bin/cmake -E cmake_progress_start /<>/build/CMakeFiles 0 > make[3]: Leaving directory '/<>/build' > make[2]: Leaving directory '/<>/build' > cd build; PATH=/<>/debian/tmp-test:$PATH > /<>/bin/dune-ctest >Site: ip-172-31-8-9 >Build name: Linux-c++ > Create new tag: 20201226-1836 - Experimental > Test project /<>/build > Start 1: indexsettest > 1/112 Test #1: indexsettest ... Passed0.00 > sec > Start 2: remoteindicestest > 2/112 Test #2: remoteindicestest ..***Failed0.04 > sec > [ip-172-31-8-9:13404] [[33605,0],0] ORTE_ERROR_LOG: Not found in file > ../../../../../../orte/mca/ess/hnp/ess_hnp_module.c at line 320 > -- > It looks like orte_init failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during orte_init; some of which are due to configuration or > environment problems. This failure appears to be an internal failure; > here's some additional information (which may only be relevant to an > Open MPI developer): > > opal_pmix_base_select failed > --> Returned value Not found (-13) instead of ORTE_SUCCESS > -- > [ip-172-31-8-9:13403] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start a > daemon on the local node in file > ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 716 > [ip-172-31-8-9:13403] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start a > daemon on the local node in file > ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 172 > -- > It looks like orte_init failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during orte_init; some of which are due to configuration or > environment problems. This failure appears to be an internal failure; > here's some additional information (which may only be relevant to an > Open MPI developer): > > orte_ess_init failed > --> Returned value Unable to start a daemon on the local node (-127) > instead of ORTE_SUCCESS > -- > -- > It looks like MPI_INIT failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during MPI_INIT; some of which are due to configuration or environment > problems. This failure appears to be an internal failure; here's some > additional information (which may only be relevant to an Open MPI > developer): > > ompi_mpi_init: ompi_rte_init failed > --> Returned "Unable to start a daemon on the local node" (-127) instead of > "Success" (0) > -- > *** An error occurred in MPI_Init > *** on a NULL communicator > *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort, > ***and potentially your MPI job) > [ip-172-31-8-9:13403] Local abort before MPI_INIT completed completed > successfully, but am not able to aggregate error messages, and not able to > guarantee that all other processes were killed! > > Start 3: remoteindicestest-mpi-2 > 3/112 Test #3: remoteindicestest-mpi-2 ***Failed0.01 > sec > [ip-172-31-8-9:13405] [[33604,0],0] ORTE_ERROR_LOG: Not found in file > ../../../../../../orte/mca/ess/hnp/ess_hnp_module.c at line 320 > -- > It looks like orte_init failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during orte_init; some of which are due to configuration or > environment problems. This failure appears to be an internal failure; > here&#x
Bug#978216: liborigin2: FTBFS: OriginObj.h:702:27: error: ‘find_if’ was not declared in this scope; did you mean ‘boost::mpl::find_if’?
Source: liborigin2 Version: 2:20110117-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > g++ -c -pipe -O2 -D_REENTRANT -Wall -Wextra -fPIC -DQT_NO_DEBUG -I. > -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o tmp/Origin600Parser.o > Origin600Parser.cpp > In file included from /usr/include/boost/bind.hpp:30, > from OriginObj.h:37, > from OriginParser.h:32, > from OriginDefaultParser.h:33, > from OriginDefaultParser.cpp:30: > /usr/include/boost/bind.hpp:36:1: note: ‘#pragma message: The practice of > declaring the Bind placeholders (_1, _2, ...) in the global namespace is > deprecated. Please use + using namespace > boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the > current behavior.’ >36 | BOOST_PRAGMA_MESSAGE( > | ^~~~ > In file included from /usr/include/boost/bind.hpp:30, > from OriginObj.h:37, > from OriginParser.h:32, > from Origin750Parser.h:34, > from Origin800Parser.h:32, > from Origin610Parser.h:32, > from Origin600Parser.h:32, > from Origin600Parser.cpp:29: > /usr/include/boost/bind.hpp:36:1: note: ‘#pragma message: The practice of > declaring the Bind placeholders (_1, _2, ...) in the global namespace is > deprecated. Please use + using namespace > boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the > current behavior.’ >36 | BOOST_PRAGMA_MESSAGE( > | ^~~~ > In file included from /usr/include/boost/bind.hpp:30, > from OriginObj.h:37, > from OriginFile.h:37, > from OriginFile.cpp:30: > /usr/include/boost/bind.hpp:36:1: note: ‘#pragma message: The practice of > declaring the Bind placeholders (_1, _2, ...) in the global namespace is > deprecated. Please use + using namespace > boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the > current behavior.’ >36 | BOOST_PRAGMA_MESSAGE( > | ^~~~ > In file included from /usr/include/boost/bind.hpp:30, > from OriginObj.h:37, > from OriginParser.h:32, > from OriginParser.cpp:29: > /usr/include/boost/bind.hpp:36:1: note: ‘#pragma message: The practice of > declaring the Bind placeholders (_1, _2, ...) in the global namespace is > deprecated. Please use + using namespace > boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the > current behavior.’ >36 | BOOST_PRAGMA_MESSAGE( > | ^~~~ > In file included from OriginParser.h:32, > from OriginDefaultParser.h:33, > from OriginDefaultParser.cpp:30: > OriginObj.h: In constructor ‘Origin::SpreadColumn::SpreadColumn(const > string&, unsigned int)’: > OriginObj.h:166:16: warning: ‘Origin::SpreadColumn::index’ will be > initialized after [-Wreorder] > 166 | unsigned int index; > |^ > OriginObj.h:163:10: warning: ‘std::string Origin::SpreadColumn::command’ > [-Wreorder] > 163 | string command; > | ^~~ > OriginObj.h:170:3: warning: when initialized here [-Wreorder] > 170 | SpreadColumn(const string& _name = "", unsigned int _index = 0) > | ^~~~ > OriginObj.h:164:10: warning: ‘Origin::SpreadColumn::comment’ will be > initialized after [-Wreorder] > 164 | string comment; > | ^~~ > OriginObj.h:158:13: warning: ‘Origin::ValueType > Origin::SpreadColumn::valueType’ [-Wreorder] > 158 | ValueType valueType; > | ^ > OriginObj.h:170:3: warning: when initialized here [-Wreorder] > 170 | SpreadColumn(const string& _name = "", unsigned int _index = 0) > | ^~~~ > OriginObj.h:165:7: warning: ‘Origin::SpreadColumn::width’ will be initialized > after [-Wreorder] > 165 | int width; > | ^ > OriginObj.h:162:22: warning: ‘Origin::NumericDisplayType > Origin::SpreadColumn::numericDisplayType’ [-Wreorder] > 162 | NumericDisplayType numericDisplayType; > | ^~ > OriginObj.h:170:3: warning: when initialized here [-Wreorder] > 170 | SpreadColumn(const string& _name = "", unsigned int _index = 0) > | ^~~~ > In file included from OriginFile.h:37, > from Ori
Bug#978260: xmds2: FTBFS: AssertionError: False is not true : Failed to execute compiled simulation correctly. Got returnCode 1;
Source: xmds2 Version: 3.0.0+dfsg-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > debian/tests/run-tests -b > xmds2 version 3.0.0 "Release the Kraken" (Debian package 3.0.0+dfsg-4) > Copyright 2000-2019 Graham Dennis, Joseph Hope, Mattias Johnsson > and the xmds team > > Configuring for single-process scripts... > Checking for 'g++' (C++ compiler): /usr/bin/g++ > Checking whether the compiler works : yes > Checking that we have a C++ compiler : yes > Checking whether we are cross-compiling : no > Checking whether we can link to only static libraries : yes > Trying to make compiler optimise for this machine : yes > Trying to make compiler tune for this machine : yes > Checking for compiler flags -O3 : yes > Checking for compiler flags -ffast-math : yes > Checking for compiler flags -funroll-all-loops: yes > Checking for compiler flags -fomit-frame-pointer : yes > Checking for compiler flags -falign-loops : yes > Checking for compiler flags -fstrict-aliasing : yes > Checking for compiler flags -momit-leaf-frame-pointer : yes > Checking for cautious math flags : yes > Checking for Autovectorisation: yes > Checking for OpenMP : yes > Checking for pthreads : yes > Checking for compiler debug flags : yes > Checking for srandomdev : yes > Checking for /dev/urandom : yes > Checking for program 'h5cc' : /usr/bin/h5cc > Checking for HDF5 (static library): yes > Checking for HDF5 High-level library (static library) : yes > Checking for header hdf5.h: yes > Checking for libxmds (static library) : no (will try dynamic > library instead) > Checking for libxmds (dynamic library): no (it's optional > anyway) > Checking for Intel's Vector Math Library (static library) : no (will try > dynamic library instead) > Checking for Intel's Vector Math Library (dynamic library) : no (it's > optional anyway) > Checking safer dSFMT compile flags : yes > Checking for Intel's Math Kernel Library (static library) : no (will try > dynamic library instead) > Checking for Intel's Math Kernel Library (dynamic library) : no (it's > optional anyway) > Checking for ATLAS's CBLAS. (static library) : no (will try > dynamic library instead) > Checking for ATLAS's CBLAS. (dynamic library) : yes > Checking for GSL (static library) : yes > Checking for FFTW3 (static library): yes > Checking for single-precision FFTW3 (static library) : yes > Checking for threading support in FFTW3 (static library) : yes > Checking for OpenMP support in FFTW3 (static library) : yes > Checking for threading support in single-precision FFTW3 (static library) : > yes > Checking for OpenMP support in single-precision FFTW3 (static library): > yes > > Configuring for MPI scripts... > Checking for program 'mpic++' : > /usr/bin/mpic++ > Checking for 'g++' (C++ compiler) : > /usr/bin/mpic++ > Checking whether the compiler works : > yes > Checking that we have a C++ compiler : > yes > Checking whether we are cross-compiling : > no > Checking whether we can link to only static libraries : > yes > Trying to make compiler optimise for this machine : > yes > Trying to make compiler tune for this machine : > yes > Checking for compiler flags -O3 : > yes > Checking for compiler flags -ffast-math : > yes > Checking for compiler flags -funroll-all-loops: > yes > Checking for compiler flags -fomit-frame-pointer : > yes > Checking for compiler flags -falign-loops : > yes
Bug#978261: swiglpk: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.9 returned exit code 13
Source: swiglpk
Version: 4.65.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py config
> /usr/lib/python3.9/distutils/dist.py:274: UserWarning: Unknown distribution
> option: 'test_suite'
> warnings.warn(msg)
> /usr/lib/python3.9/distutils/dist.py:274: UserWarning: Unknown distribution
> option: 'include_package_data'
> warnings.warn(msg)
> Trying to determine glpk.h location
> glpk.h found at /usr/include/glpk.h
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:232: /usr/bin/python3 setup.py build
> /usr/lib/python3.9/distutils/dist.py:274: UserWarning: Unknown distribution
> option: 'test_suite'
> warnings.warn(msg)
> /usr/lib/python3.9/distutils/dist.py:274: UserWarning: Unknown distribution
> option: 'include_package_data'
> warnings.warn(msg)
> Trying to determine glpk.h location
> glpk.h found at /usr/include/glpk.h
> running build
> running build_ext
> building 'swiglpk._swiglpk' extension
> swigging swiglpk/glpk.i to swiglpk/glpk_wrap.c
> swig -python -o swiglpk/glpk_wrap.c swiglpk/glpk.i
> swiglpk/glpk_clean.h:1000: Warning 314: 'in' is a python keyword, renaming to
> '_in'
> swiglpk/glpk_clean.h:201: Warning 451: Setting a const char * variable may
> leak memory.
> creating build
> creating build/temp.linux-x86_64-3.9
> creating build/temp.linux-x86_64-3.9/swiglpk
> x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g
> -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat
> -Werror=format-security -g -fwrapv -O2 -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -I/usr/include/python3.9 -c swiglpk/glpk_wrap.c -o
> build/temp.linux-x86_64-3.9/swiglpk/glpk_wrap.o
> In file included from /usr/include/python3.9/pytime.h:6,
> from /usr/include/python3.9/Python.h:85,
> from swiglpk/glpk_wrap.c:154:
> swiglpk/glpk_wrap.c: In function ‘wrap_glp_term_hook_cb’:
> /usr/include/python3.9/object.h:422:13: warning: ‘r’ may be used
> uninitialized in this function [-Wmaybe-uninitialized]
> 422 | if (--op->ob_refcnt != 0) {
> | ~~^~~
> swiglpk/glpk_wrap.c:2732:31: note: ‘r’ was declared here
> 2732 | PyObject *callback, *args, *r;
> | ^
> creating /<>/.pybuild/cpython3_3.9_swiglpk/build/swiglpk
> x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
> -Wl,-z,relro -g -fwrapv -O2 -Wl,-z,relro -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
> build/temp.linux-x86_64-3.9/swiglpk/glpk_wrap.o -lglpk -o
> /<>/.pybuild/cpython3_3.9_swiglpk/build/swiglpk/_swiglpk.cpython-39-x86_64-linux-gnu.so
> running build_py
> copying swiglpk/__init__.py ->
> /<>/.pybuild/cpython3_3.9_swiglpk/build/swiglpk
> copying swiglpk/swiglpk.py ->
> /<>/.pybuild/cpython3_3.9_swiglpk/build/swiglpk
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9_swiglpk/build;
> python3.9 -m nose -v
> Failure: ImportError
> (/<>/.pybuild/cpython3_3.9_swiglpk/build/swiglpk/_swiglpk.cpython-39-x86_64-linux-gnu.so:
> undefined symbol: glp_netgen_prob) ... ERROR
>
> ==
> ERROR: Failure: ImportError
> (/<>/.pybuild/cpython3_3.9_swiglpk/build/swiglpk/_swiglpk.cpython-39-x86_64-linux-gnu.so:
> undefined symbol: glp_netgen_prob)
> --
> Traceback (most recent call last):
> File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest
> raise self.exc_val.with_traceback(self.tb)
> File "/usr/lib/python3/dist-packages/nose/loader.py", line 416, in
> loadTestsFromName
> module = self.importer.importFromPath(
> File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in
> importFromPath
> return self.importFromDir(dir_path, fqname)
> File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in
> importFrom
Bug#978286: python-vispy: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
Source: python-vispy Version: 0.6.4-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_clean > I: pybuild base:232: python3.9 setup.py clean > setup.py entered > $PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games > /usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning: > Cython directive 'language_level' not set, using 2 for now (Py2). This will > change in a later release! File: > /<>/vispy/visuals/text/_sdf_cpu.pyx > tree = Parsing.p_module(s, pxd, full_module_name) > Compiling vispy/visuals/text/_sdf_cpu.pyx because it changed. > [1/1] Cythonizing vispy/visuals/text/_sdf_cpu.pyx > running clean > removing '/<>/.pybuild/cpython3_3.9_vispy/build' (and everything > under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.9' does not exist -- can't clean it > rm -rf vispy/visuals/text/_sdf_cpu.c > make[1]: Leaving directory '/<>' >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building python-vispy using existing > ./python-vispy_0.6.4.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: warning: ignoring deletion of directory vispy.egg-info > dpkg-source: warning: ignoring deletion of file vispy.egg-info/SOURCES.txt, > use --include-removal to override > dpkg-source: warning: ignoring deletion of file vispy.egg-info/top_level.txt, > use --include-removal to override > dpkg-source: warning: ignoring deletion of file > vispy.egg-info/dependency_links.txt, use --include-removal to override > dpkg-source: warning: ignoring deletion of file vispy.egg-info/PKG-INFO, use > --include-removal to override > dpkg-source: warning: ignoring deletion of file vispy.egg-info/requires.txt, > use --include-removal to override > dpkg-source: warning: ignoring deletion of file vispy.egg-info/not-zip-safe, > use --include-removal to override > dpkg-source: info: local changes detected, the modified files are: > python-vispy-0.6.4/vispy/version.py > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/python-vispy_0.6.4-1.diff.01JT6X > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2020-12-26T18:39:29Z The full build log is available from: http://qa-logs.debian.net/2020/12/26/python-vispy_0.6.4-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- 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#978292: superlu-dist: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=-j1 returned exit code 2
Source: superlu-dist Version: 6.2.0+dfsg1-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' > Running tests... > /usr/bin/ctest --force-new-ctest-process -j1 > Test project /<>/obj-x86_64-linux-gnu > Start 1: pdtest_1x1_1_2_8_20_SP > 1/14 Test #1: pdtest_1x1_1_2_8_20_SP ...***Failed0.04 sec > [ip-172-31-12-139:00795] [[25331,0],0] ORTE_ERROR_LOG: Not found in file > ../../../../../../orte/mca/ess/hnp/ess_hnp_module.c at line 320 > -- > It looks like orte_init failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during orte_init; some of which are due to configuration or > environment problems. This failure appears to be an internal failure; > here's some additional information (which may only be relevant to an > Open MPI developer): > > opal_pmix_base_select failed > --> Returned value Not found (-13) instead of ORTE_SUCCESS > -- > > Start 2: pdtest_1x1_3_2_8_20_SP > 2/14 Test #2: pdtest_1x1_3_2_8_20_SP ...***Failed0.02 sec > [ip-172-31-12-139:00796] [[25332,0],0] ORTE_ERROR_LOG: Not found in file > ../../../../../../orte/mca/ess/hnp/ess_hnp_module.c at line 320 > -- > It looks like orte_init failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during orte_init; some of which are due to configuration or > environment problems. This failure appears to be an internal failure; > here's some additional information (which may only be relevant to an > Open MPI developer): > > opal_pmix_base_select failed > --> Returned value Not found (-13) instead of ORTE_SUCCESS > -- > > Start 3: pdtest_1x2_1_2_8_20_SP > 3/14 Test #3: pdtest_1x2_1_2_8_20_SP ...***Failed0.02 sec > [ip-172-31-12-139:00797] [[25333,0],0] ORTE_ERROR_LOG: Not found in file > ../../../../../../orte/mca/ess/hnp/ess_hnp_module.c at line 320 > -- > It looks like orte_init failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during orte_init; some of which are due to configuration or > environment problems. This failure appears to be an internal failure; > here's some additional information (which may only be relevant to an > Open MPI developer): > > opal_pmix_base_select failed > --> Returned value Not found (-13) instead of ORTE_SUCCESS > -- > > Start 4: pdtest_1x2_3_2_8_20_SP > 4/14 Test #4: pdtest_1x2_3_2_8_20_SP ...***Failed0.02 sec > [ip-172-31-12-139:00798] [[25334,0],0] ORTE_ERROR_LOG: Not found in file > ../../../../../../orte/mca/ess/hnp/ess_hnp_module.c at line 320 > -- > It looks like orte_init failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during orte_init; some of which are due to configuration or > environment problems. This failure appears to be an internal failure; > here's some additional information (which may only be relevant to an > Open MPI developer): > > opal_pmix_base_select failed > --> Returned value Not found (-13) instead of ORTE_SUCCESS > -- > > Start 5: pdtest_2x1_1_2_8_20_SP > 5/14 Test #5: pdtest_2x1_1_2_8_20_SP ...***Failed0.02 sec > [ip-172-31-12-139:00799] [[25335,0],0] ORTE_ERROR_LOG: Not found in file > ../../../../../../orte/mca/ess/hnp/ess_hnp_module.c at line 320 > -- > It looks like orte_init failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during orte_init; some of which are due to configuration or > environment problems. This failure appears to be an internal failure; > here's some additional information (which may only be relev
Bug#978306: med-fichier: FTBFS: dh_auto_test: error: cd build.python3.9 && make -j1 check VERBOSE=1 returned exit code 2
Source: med-fichier Version: 4.1.0+repack-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[6]: Entering directory '/<>/build.python3.9/tests/parallel' > Launching filterBlockOfentities with 1 processes > [ip-172-31-4-110:13972] [[31075,0],0] ORTE_ERROR_LOG: Not found in file > ../../../../../../orte/mca/ess/hnp/ess_hnp_module.c at line 320 > -- > It looks like orte_init failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during orte_init; some of which are due to configuration or > environment problems. This failure appears to be an internal failure; > here's some additional information (which may only be relevant to an > Open MPI developer): > > opal_pmix_base_select failed > --> Returned value Not found (-13) instead of ORTE_SUCCESS > -- > Can't launch filterBlockOfentities with 1 processes > FAIL: filterBlockOfentities.sh > > 1 of 1 test failed > Please report to eric.fayo...@edf.fr > > make[6]: *** [Makefile:840: check-TESTS] Error 1 > make[6]: Leaving directory '/<>/build.python3.9/tests/parallel' > make[5]: *** [Makefile:992: check-am] Error 2 > make[5]: Leaving directory '/<>/build.python3.9/tests/parallel' > make[4]: *** [Makefile:747: check-recursive] Error 1 > make[4]: Leaving directory '/<>/build.python3.9/tests/parallel' > make[3]: *** [Makefile:487: check-recursive] Error 1 > make[3]: Leaving directory '/<>/build.python3.9/tests' > make[2]: *** [Makefile:519: check-recursive] Error 1 > make[2]: Leaving directory '/<>/build.python3.9' > dh_auto_test: error: cd build.python3.9 && make -j1 check VERBOSE=1 returned > exit code 2 The full build log is available from: http://qa-logs.debian.net/2020/12/26/med-fichier_4.1.0+repack-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- 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#978307: scalapack: FTBFS: dh_auto_test: error: cd build-openmpi && make -j4 test ARGS\+=-j4 returned exit code 2
Source: scalapack Version: 2.1.0-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/build-openmpi' > Running tests... > /usr/bin/ctest --force-new-ctest-process -j4 > Test project /<>/build-openmpi > Start 1: xCbtest > Start 2: xFbtest > Start 3: spb1tst > Start 4: dpb1tst > 1/96 Test #4: dpb1tst ..***Failed0.03 sec > [ip-172-31-9-140:01450] [[25943,0],0] ORTE_ERROR_LOG: Not found in file > ../../../../../../orte/mca/ess/hnp/ess_hnp_module.c at line 320 > -- > It looks like orte_init failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during orte_init; some of which are due to configuration or > environment problems. This failure appears to be an internal failure; > here's some additional information (which may only be relevant to an > Open MPI developer): > > opal_pmix_base_select failed > --> Returned value Not found (-13) instead of ORTE_SUCCESS > -- > > Start 5: cpb1tst > 2/96 Test #2: xFbtest ..***Failed0.04 sec > Running BLACS TESTS > -- /usr/bin/mpiexec -n 4 --allow-run-as-root --oversubscribe ./xFbtest > -- Output out_xFbtest.txt > -- Error in error_xFbtest.txt > [ip-172-31-9-140:01451] [[25942,0],0] ORTE_ERROR_LOG: Not found in file > ../../../../../../orte/mca/ess/hnp/ess_hnp_module.c at line 320 > -- > It looks like orte_init failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during orte_init; some of which are due to configuration or > environment problems. This failure appears to be an internal failure; > here's some additional information (which may only be relevant to an > Open MPI developer): > > opal_pmix_base_select failed > --> Returned value Not found (-13) instead of ORTE_SUCCESS > -- > CMake Error at /<>/BLACS/TESTING/runtest.cmake:22 (message): > Test failed - Test did not reach DONE BLACS_GRIDEXIT > > > > Start 6: zpb1tst > 3/96 Test #1: xCbtest ..***Failed0.04 sec > Running BLACS TESTS > -- /usr/bin/mpiexec -n 4 --allow-run-as-root --oversubscribe ./xCbtest > -- Output out_xCbtest.txt > -- Error in error_xCbtest.txt > [ip-172-31-9-140:01452] [[25937,0],0] ORTE_ERROR_LOG: Not found in file > ../../../../../../orte/mca/ess/hnp/ess_hnp_module.c at line 320 > -- > It looks like orte_init failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during orte_init; some of which are due to configuration or > environment problems. This failure appears to be an internal failure; > here's some additional information (which may only be relevant to an > Open MPI developer): > > opal_pmix_base_select failed > --> Returned value Not found (-13) instead of ORTE_SUCCESS > -- > CMake Error at /<>/BLACS/TESTING/runtest.cmake:22 (message): > Test failed - Test did not reach DONE BLACS_GRIDEXIT > > > > Start 7: spb2tst > 4/96 Test #3: spb1tst ..***Failed0.05 sec > [ip-172-31-9-140:01449] [[25940,0],0] ORTE_ERROR_LOG: Not found in file > ../../../../../../orte/mca/ess/hnp/ess_hnp_module.c at line 320 > -- > It looks like orte_init failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during orte_init; some of which are due to configuration or > environment problems. This failure appears to be an internal failure; > here's some additional information (which may only be relevant to an > Open MPI developer): > > opal_pmix_base_select failed > --> Returned value Not found (-13) instead of ORTE_SUCCESS > -- > > Start 8: dpb2tst > 5/96 Test #6: zpb1tst ..***Failed0.02 sec &g
Bug#978308: pyzoltan: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Source: pyzoltan Version: 1.0.1-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package pyzoltan > dpkg-buildpackage: info: source version 1.0.1-2 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Anton Gladky > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean --with python3 --buildsystem=pybuild >dh_auto_clean -O--buildsystem=pybuild > I: pybuild base:232: python3.9 setup.py clean > /usr/lib/python3.9/distutils/extension.py:131: UserWarning: Unknown Extension > options: 'cython_compile_time_env' > warnings.warn(msg) > running clean > removing '/<>/.pybuild/cpython3_3.9_pyzoltan/build' (and > everything under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.9' does not exist -- can't clean it >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building pyzoltan using existing > ./pyzoltan_1.0.1.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building pyzoltan in pyzoltan_1.0.1-2.debian.tar.xz > dpkg-source: info: building pyzoltan in pyzoltan_1.0.1-2.dsc > debian/rules binary > dh binary --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:232: python3.9 setup.py config > /usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning: > Cython directive 'language_level' not set, using 2 for now (Py2). This will > change in a later release! File: /<>/pyzoltan/core/zoltan.pxd > tree = Parsing.p_module(s, pxd, full_module_name) > /usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning: > Cython directive 'language_level' not set, using 2 for now (Py2). This will > change in a later release! File: > /<>/pyzoltan/core/zoltan_comm.pxd > tree = Parsing.p_module(s, pxd, full_module_name) > /usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning: > Cython directive 'language_level' not set, using 2 for now (Py2). This will > change in a later release! File: /<>/pyzoltan/core/zoltan_dd.pxd > tree = Parsing.p_module(s, pxd, full_module_name) > -- > Using Zoltan from: > /usr/include/trilinos > /usr/lib > -- > Compiling pyzoltan/core/zoltan.pyx because it changed. > Compiling pyzoltan/core/zoltan_dd.pyx because it changed. > Compiling pyzoltan/core/zoltan_comm.pyx because it changed. > [1/3] Cythonizing pyzoltan/core/zoltan.pyx > [2/3] Cythonizing pyzoltan/core/zoltan_comm.pyx > [3/3] Cythonizing pyzoltan/core/zoltan_dd.pyx > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:232: /usr/bin/python3 setup.py build > -- > Using Zoltan from: > /usr/include/trilinos > /usr/lib > -- > running build > running build_py > creating /<>/.pybuild/cpython3_3.9_pyzoltan/build/pyzoltan > copying pyzoltan/api.py -> > /<>/.pybuild/cpython3_3.9_pyzoltan/build/pyzoltan > copying pyzoltan/__init__.py -> > /<>/.pybuild/cpython3_3.9_pyzoltan/build/pyzoltan > creating > /<>/.pybuild/cpython3_3.9_pyzoltan/build/pyzoltan/czoltan > copying pyzoltan/czoltan/__init__.py -> > /<>/.pybuild/cpython3_3.9_pyzoltan/build/pyzoltan/czoltan > creating /<>/.pybuild/cpython3_3.9_pyzoltan/build/pyzoltan/core > copying pyzoltan/core/zoltan_utils.py -> > /<>/.pybuild/cpython3_3.9_pyzoltan/build/pyzoltan/core > copying pyzoltan/core/__init__.py -> > /<>/.pybuild/cpython3_3.9_pyzoltan/build/pyzoltan/core > creating /<>/.pybuild/cpython3_3.9_pyzoltan/build/pyzoltan/tools > copying pyzoltan/tools/__init__.py -> > /<>/.pybuild/cpython3_3.9_pyzoltan/build/pyzoltan/tools > copying pyzoltan/tools/run_parallel_script.py -> > /<>/.pybuild/cpython3_3.9_
Bug#978311: glpk-java: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
Source: glpk-java Version: 1.12.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/swig' > cd ../examples/java;/usr/bin/javac -source 1.8 -target 1.8 \ > -classpath ../../swig/glpk-java.jar Gmpl.java > warning: [options] bootstrap class path not set in conjunction with -source 8 > 1 warning > cd ../examples/java;java -Djava.library.path=../../swig/.libs \ > -classpath ../../swig/glpk-java.jar:. Gmpl marbles.mod > Reading model section from marbles.mod... > 51 lines were read > The smallest bag contains 3 marbles > The largest bag contains 42 marbles > 857 colors are used > Generating obj... > Generating nBags... > Generating fCol... > Model has been successfully generated > GLPK Integer Optimizer 5.0 > 1002 rows, 1100 columns, 4140 non-zeros > 100 integer variables, all of which are binary > Preprocessing... > 858 rows, 957 columns, 2997 non-zeros > 100 integer variables, all of which are binary > Scaling... > A: min|aij| = 1.000e+00 max|aij| = 1.000e+00 ratio = 1.000e+00 > Problem data seem to be well scaled > Constructing initial basis... > Size of triangular part is 858 > Solving LP relaxation... > GLPK Simplex Optimizer 5.0 > 858 rows, 957 columns, 2997 non-zeros > * 0: obj = -0.0e+00 inf = 0.000e+00 (857) > Perturbing LP to avoid stalling [472]... > Removing LP perturbation [1157]... > * 1157: obj = 3.27500e+02 inf = 7.824e-13 (0) 2 > OPTIMAL LP SOLUTION FOUND > Integer optimization begins... > Long-step dual simplex will be used > + 1157: mip = not found yet <= +inf(1; 0) > + 1303: >>>>> 3.17000e+02 <= 3.26500e+02 3.0% (9; 0) > Better solution found > + 1713: >>>>> 3.18000e+02 <= 3.21000e+02 0.9% (9; 8) > Better solution found > + 1784: >>>>> 3.19000e+02 <= 3.19500e+02 0.2% (5; 20) > Better solution found > + 1793: mip = 3.19000e+02 <= tree is empty 0.0% (0; 37) > INTEGER OPTIMAL SOLUTION FOUND > Bags chosen: > bag 7, bag 12, bag 23, bag 28, bag 36, bag 45, bag 75, bag 82, bag 83, bag 99. > Colors retrieved: 319 > Model has been successfully processed > cd ../examples/java;/usr/bin/javac -source 1.8 -target 1.8 -classpath \ > ../../swig/glpk-java.jar Lp.java > warning: [options] bootstrap class path not set in conjunction with -source 8 > 1 warning > cd ../examples/java;java -Djava.library.path=../../swig/.libs \ > -classpath ../../swig/glpk-java.jar:. Lp > Problem created > GLPK Simplex Optimizer 5.0 > 2 rows, 3 columns, 4 non-zeros > * 0: obj = 1.0e+00 inf = 0.000e+00 (2) > * 3: obj = 4.25000e-01 inf = 0.000e+00 (0) > OPTIMAL LP SOLUTION FOUND > z = 0.42504 > x1 = 0.25 > x2 = 0.09998 > x3 = 0.5 > cd ../examples/java;/usr/bin/javac -source 1.8 -target 1.8 -classpath \ > ../../swig/glpk-java.jar Mip.java > warning: [options] bootstrap class path not set in conjunction with -source 8 > 1 warning > cd ../examples/java;java -Djava.library.path=../../swig/.libs \ > -classpath ../../swig/glpk-java.jar:. Mip > Problem created > GLPK Integer Optimizer 5.0 > 2 rows, 2 columns, 4 non-zeros > 2 integer variables, none of which are binary > Preprocessing... > 2 rows, 2 columns, 4 non-zeros > 2 integer variables, none of which are binary > Scaling... > A: min|aij| = 1.000e+00 max|aij| = 1.000e+01 ratio = 1.000e+01 > Problem data seem to be well scaled > Constructing initial basis... > Size of triangular part is 2 > Solving LP relaxation... > GLPK Simplex Optimizer 5.0 > 2 rows, 2 columns, 4 non-zeros > * 0: obj = -0.0e+00 inf = 0.000e+00 (2) > * 3: obj = 6.8e+01 inf = 0.000e+00 (0) > OPTIMAL LP SOLUTION FOUND > Integer optimization begins... > Long-step dual simplex will be used > + 3: mip = not found yet <= +inf(1; 0) > Solution found by heuristic: 63 > + 4: >>>>> 6.8e+01 <= 6.8e+01 0.0% (3; 0) > + 4: mip = 6.8e+01 <= tree is empty 0.0% (0; 5) > INTEGER OPTIMAL SOLUTION FOUND > obj = 68.0 > x1 = 4.0 > x2 = 0.0 > cd ../examples/java;/usr/bin/javac -source 1.8 -target 1.8 \ >-classpath ../../swig/glpk-java.jar OutOfMemory.java > warning: [options] bootstrap class path not set in conjunction with -source 8 > 1 warning > cd ../examples/java;java -Djava.library.path=../../swig/.libs \ >-classpath ../.
Bug#978329: p4est: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
Source: p4est Version: 2.2-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/sc' > FAIL: test/sc_test_builtin > FAIL: test/sc_test_darray_work > FAIL: test/sc_test_arrays > FAIL: test/sc_test_allgather > FAIL: test/sc_test_dmatrix > FAIL: test/sc_test_dmatrix_pool > FAIL: test/sc_test_io_sink > FAIL: test/sc_test_keyvalue > FAIL: test/sc_test_notify > FAIL: test/sc_test_reduce > FAIL: test/sc_test_node_comm > FAIL: test/sc_test_search > FAIL: test/sc_test_sort > FAIL: test/sc_test_sortb > = >libsc 2.2: ./test-suite.log > = > > # TOTAL: 14 > # PASS: 0 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 14 > # XPASS: 0 > # ERROR: 0 > > .. contents:: :depth: 2 > > FAIL: test/sc_test_allgather > > > [ip-172-31-4-110:22553] [[6126,0],0] ORTE_ERROR_LOG: Not found in file > ../../../../../../orte/mca/ess/hnp/ess_hnp_module.c at line 320 > -- > It looks like orte_init failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during orte_init; some of which are due to configuration or > environment problems. This failure appears to be an internal failure; > here's some additional information (which may only be relevant to an > Open MPI developer): > > opal_pmix_base_select failed > --> Returned value Not found (-13) instead of ORTE_SUCCESS > -- > FAIL test/sc_test_allgather (exit status: 1) > > FAIL: test/sc_test_arrays > = > > [ip-172-31-4-110:22556] [[6123,0],0] ORTE_ERROR_LOG: Not found in file > ../../../../../../orte/mca/ess/hnp/ess_hnp_module.c at line 320 > -- > It looks like orte_init failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during orte_init; some of which are due to configuration or > environment problems. This failure appears to be an internal failure; > here's some additional information (which may only be relevant to an > Open MPI developer): > > opal_pmix_base_select failed > --> Returned value Not found (-13) instead of ORTE_SUCCESS > -- > FAIL test/sc_test_arrays (exit status: 1) > > FAIL: test/sc_test_builtin > == > > [ip-172-31-4-110:22555] [[6124,0],0] ORTE_ERROR_LOG: Not found in file > ../../../../../../orte/mca/ess/hnp/ess_hnp_module.c at line 320 > -- > It looks like orte_init failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during orte_init; some of which are due to configuration or > environment problems. This failure appears to be an internal failure; > here's some additional information (which may only be relevant to an > Open MPI developer): > > opal_pmix_base_select failed > --> Returned value Not found (-13) instead of ORTE_SUCCESS > -- > FAIL test/sc_test_builtin (exit status: 1) > > FAIL: test/sc_test_darray_work > == > > [ip-172-31-4-110:22554] [[6125,0],0] ORTE_ERROR_LOG: Not found in file > ../../../../../../orte/mca/ess/hnp/ess_hnp_module.c at line 320 > -- > It looks like orte_init failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during orte_init; some of which are due to configuration or > environment problems. This failure appears to be an internal failure; > here's some additional information (which may only be relevant to an > Open MPI developer): > > opal_pmix_base_select failed > --> Returned value Not found (-13) instead of ORTE_SUCCESS > -- > FAIL test/sc_test_darray_work (exit status: 1) > > FAIL: test/sc_test_dmatrix > == > > [ip-172-31-4-110:22568] [[6111,0],0] ORTE_ERROR_LOG: Not found in file > ../../../.
Processing of macaulay2_1.16.99+git40.3a512e5+ds-1~exp1_source.changes
macaulay2_1.16.99+git40.3a512e5+ds-1~exp1_source.changes uploaded successfully to localhost along with the files: macaulay2_1.16.99+git40.3a512e5+ds-1~exp1.dsc macaulay2_1.16.99+git40.3a512e5+ds.orig.tar.xz macaulay2_1.16.99+git40.3a512e5+ds-1~exp1.debian.tar.xz macaulay2_1.16.99+git40.3a512e5+ds-1~exp1_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
Processing of clasp_3.3.5-2_amd64.changes
clasp_3.3.5-2_amd64.changes uploaded successfully to localhost along with the files: clasp_3.3.5-2.dsc clasp_3.3.5-2.debian.tar.xz clasp_3.3.5-2_amd64.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
Bug#978352: gftl-shared: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTAT
Source: gftl-shared Version: 1.0.7-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package gftl-shared > dpkg-buildpackage: info: source version 1.0.7-2 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Ole Streicher > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building gftl-shared using existing > ./gftl-shared_1.0.7.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building gftl-shared in gftl-shared_1.0.7-2.debian.tar.xz > dpkg-source: info: building gftl-shared in gftl-shared_1.0.7-2.dsc > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr > -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. > -- The Fortran compiler identification is GNU 10.2.1 > -- Detecting Fortran compiler ABI info > -- Detecting Fortran compiler ABI info - done > -- Check for working Fortran compiler: /usr/bin/f95 - skipped > -- Checking whether /usr/bin/f95 supports Fortran 90 > -- Checking whether /usr/bin/f95 supports Fortran 90 - yes > -- Performing Test _LOGICAL_DEFAULT_KIND: SUCCESS (value=4) > -- Performing Test _INT_DEFAULT_KIND: SUCCESS (value=4) > -- Performing Test _ISO_INT8: SUCCESS (value=1) > -- Performing Test _ISO_INT16: SUCCESS (value=2) > -- Performing Test _ISO_INT32: SUCCESS (value=4) > -- Performing Test _ISO_INT64: SUCCESS (value=8) > -- Performing Test _REAL_DEFAULT_KIND: SUCCESS (value=4) > -- Performing Test _DOUBLE_DEFAULT_KIND: SUCCESS (value=8) > -- Performing Test _ISO_REAL32: SUCCESS (value=4) > -- Performing Test _ISO_REAL64: SUCCESS (value=8) > -- Performing Test _ISO_REAL128: SUCCESS (value=16) > CMake Error at /usr/share/cmake/gftl/GFTLConfig.cmake:29 (include): > include could not find load file: > > /GFTL.cmake > Call Stack (most recent call first): > cmake/build_submodule.cmake:10 (find_package) > extern/CMakeLists.txt:5 (build_submodule) > > > CMake Error at cmake/build_submodule.cmake:30 (add_subdirectory): > The source directory > > /<>/extern/gFTL > > does not contain a CMakeLists.txt file. > Call Stack (most recent call first): > extern/CMakeLists.txt:5 (build_submodule) > > > -- Configuring incomplete, errors occurred! > See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log". > cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt > ==> CMakeCache.txt <== > # This is the CMakeCache file. > # For build in directory: /<>/obj-x86_64-linux-gnu > # It was generated by CMake: /usr/bin/cmake > # You can edit this file to change values found and used by cmake. > # If you do not want to change any of the values, simply exit the editor. > # If you do want to change a value, simply edit, save, and exit the editor. > # The syntax for the file is as follows: > # KEY:TYPE=VALUE > # KEY is the name of a variable in the cache. > # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. > # VALUE is the current value for the KEY. > > > # EXTERNAL cache entries > > > //Path to a program. > CMAKE_ADDR2LINE:FILEPATH=/usr/bin/addr2line > > //Path to a program. > CMAKE_AR:FILEPATH=/usr/bin/ar > > //Choose the type of build, options are: None Debug Release RelWithDebInfo > // MinSizeRel ... > CMAKE_BUILD_TYPE:STRING=None > > //Enable/Disable color output during build. > CMAKE_COLOR_MAKEFILE:BOOL=ON > > //Path to a program. > CMAKE_DLLTOOL:FILEPATH=CMAKE_DLLTOOL-NOTFOUND > > //Flags used by the linker during all build types. > CMAKE_EXE_LINKER_FLAGS:STRING=-Wl,-z,relro > > //Flags used by the linker during DEBUG builds. > CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING= > > //Flags used by the linker during MINSIZE
Bug#978364: apertium-ukr: FTBFS: Error: Invalid dictionary (hint: the left side of an entry is empty)
Source: apertium-ukr Version: 0.1.0~r82563-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > apertium-validate-dictionary apertium-ukr.ukr.dix > /bin/mkdir -p .deps > lt-comp lr apertium-ukr.post-ukr.dix ukr.autopgen.bin > /usr/bin/cg-comp apertium-ukr.ukr.rlx ukr.rlx.bin > touch .deps/.d > apertium-validate-modes modes.xml > main@standard 6 14 > apertium-validate-dictionary apertium-ukr.ukr.dix > Sections: 1, Rules: 29, Sets: 67, Tags: 138 > 10 rules cannot be skipped by index. > apertium-gen-modes modes.xml > lt-comp lr apertium-ukr.ukr.dix ukr.automorf.bin apertium-ukr.ukr.acx > lt-comp rl apertium-ukr.ukr.dix ukr.autogen.bin apertium-ukr.ukr.acx > final@inconditional 34 301 > gci@standard 583 789 > main@standard 16515 38654 > lt-print ukr.autogen.bin | gzip -9 -c -n > ukr.autogen.att.gz > Error: Invalid dictionary (hint: the left side of an entry is empty) > make[1]: *** [Makefile:729: ukr.automorf.bin] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/12/26/apertium-ukr_0.1.0~r82563-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- 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#978359: apertium-br-fr: FTBFS: Error: Invalid dictionary (hint: entry on the right beginning with whitespace)
Source: apertium-br-fr Version: 0.5.0~r61325-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > apertium-validate-dictionary apertium-br-fr.br.dix > if [ ! -d .deps ]; then mkdir .deps; fi > apertium-validate-dictionary apertium-br-fr.br-fr.dix > xsltproc lexchoicebil.xsl apertium-br-fr.br-fr.dix > > .deps/apertium-br-fr.br-fr.dix > apertium-br-fr.br.dix:951: element pardef: Schemas validity error : Element > 'pardef': Duplicate key-sequence ['war/-lerc’h__pr'] in unique > identity-constraint 'pardef-unique'. > apertium-br-fr.br.dix:2009: element pardef: Schemas validity error : Element > 'pardef': Duplicate key-sequence ['bug/el__n'] in unique identity-constraint > 'pardef-unique'. > apertium-br-fr.br.dix:2024: element pardef: Schemas validity error : Element > 'pardef': Duplicate key-sequence ['itron__n'] in unique identity-constraint > 'pardef-unique'. > lt-comp lr apertium-br-fr.br.dix br-fr.automorf.bin apertium-br-fr.br.acx > apertium-validate-dictionary apertium-br-fr.br.dix > lt-comp rl apertium-br-fr.br-fr.dix fr-br.autobil.bin > apertium-validate-dictionary apertium-br-fr.post-fr.dix > lt-comp lr apertium-br-fr.post-fr.dix br-fr.autopgen.bin > apertium-br-fr.br.dix:951: element pardef: Schemas validity error : Element > 'pardef': Duplicate key-sequence ['war/-lerc’h__pr'] in unique > identity-constraint 'pardef-unique'. > apertium-br-fr.br.dix:2009: element pardef: Schemas validity error : Element > 'pardef': Duplicate key-sequence ['bug/el__n'] in unique identity-constraint > 'pardef-unique'. > apertium-br-fr.br.dix:2024: element pardef: Schemas validity error : Element > 'pardef': Duplicate key-sequence ['itron__n'] in unique identity-constraint > 'pardef-unique'. > main@standard 276 536 > cg-comp apertium-br-fr.br-fr.rlx br-fr.rlx.bin > Sections: 5, Rules: 264, Sets: 248, Tags: 331 > 47 rules cannot be skipped by index. > apertium-validate-transfer apertium-br-fr.br-fr.t1x > apertium-preprocess-transfer apertium-br-fr.br-fr.t1x br-fr.t1x.bin > lt-comp rl apertium-br-fr.br.dix fr-br.autogen.bin > Warning (13642): Paths to rule 83 blocked by rule 78. > Warning (13642): Paths to rule 83 blocked by rule 78. > Warning (13642): Paths to rule 83 blocked by rule 78. > Warning (13642): Paths to rule 83 blocked by rule 78. > Warning (13642): Paths to rule 83 blocked by rule 78. > Warning (13642): Paths to rule 83 blocked by rule 78. > Warning (13642): Paths to rule 83 blocked by rule 78. > apertium-validate-interchunk apertium-br-fr.br-fr.t2x > apertium-preprocess-transfer apertium-br-fr.br-fr.t2x br-fr.t2x.bin > apertium-validate-postchunk apertium-br-fr.br-fr.t3x > apertium-preprocess-transfer apertium-br-fr.br-fr.t3x br-fr.t3x.bin > apertium-validate-transfer apertium-br-fr.pre-xfer-br.t1x > apertium-preprocess-transfer apertium-br-fr.pre-xfer-br.t1x > br-fr.pre-xfer.t1x.bin > apertium-validate-modes modes.xml > apertium-gen-modes modes.xml > apertium-validate-dictionary apertium-br-fr.fr.dix > apertium-br-fr.fr.dix:665: element pardef: Schemas validity error : Element > 'pardef': Duplicate key-sequence ['Carrefour__np'] in unique > identity-constraint 'pardef-unique'. > apertium-br-fr.fr.dix:7920: element pardef: Schemas validity error : Element > 'pardef': Duplicate key-sequence ['fa/illir__vblex'] in unique > identity-constraint 'pardef-unique'. > apertium-br-fr.fr.dix:9598: element pardef: Schemas validity error : Element > 'pardef': Duplicate key-sequence ['mou/dre__vblex'] in unique > identity-constraint 'pardef-unique'. > lt-comp lr apertium-br-fr.fr.dix fr-br.automorf.bin > apostrophe2@preblank 67 82 > apostrophe@postblank 67 92 > final@inconditional 168 2775 > main@standard 51022 93872 > unchecked@standard 100 140 > apertium-validate-dictionary .deps/apertium-br-fr.br-fr.dix > apostrophe2@preblank 19 19 > apostrophe@postblank 67 80 > final@inconditional 163 2757 > main@standard 41380 70226 > unchecked@standard 101 122 > apertium-validate-dictionary apertium-br-fr.fr.dix > apertium-br-fr.fr.dix:665: element pardef: Schemas validity error : Element > 'pardef': Duplicate key-sequence ['Carrefour__np'] in unique > identity-constraint 'pardef-unique'. > apertium-br-fr.fr.dix:7920: element pardef: Schemas validity er
Bug#978369: apertium-eo-ca: FTBFS: Error: Invalid dictionary (hint: entry on the right beginning with whitespace)
Source: apertium-eo-ca Version: 1:0.9.1~r60655-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > apertium-validate-dictionary apertium-eo-ca.ca.dix > apertium-validate-dictionary apertium-eo-ca.eo-ca.dix > ./transliterate.sh apertium-eo-ca.eo-ca.dix >apertium-eo-ca.eo-ca.dix.translit > apertium-validate-dictionary apertium-eo-ca.eo.dix > ./transliterate.sh apertium-eo-ca.eo.dix >apertium-eo-ca.eo.dix.translit > lt-comp rl apertium-eo-ca.eo.dix ca-eo.autogen.bin > apertium-validate-dictionary apertium-eo-ca.post-eo.dix > lt-comp lr apertium-eo-ca.post-eo.dix ca-eo.autopgen.bin > main@standard 29 45 > ./transliterate.sh apertium-eo-ca.post-eo.dix > >apertium-eo-ca.post-eo.dix.translit > apertium-validate-transfer apertium-eo-ca.ca-eo.t1x > apertium-eo-ca.ca.dix:867: element pardef: Schemas validity error : Element > 'pardef': Duplicate key-sequence ['/ampli__adj'] in unique > identity-constraint 'pardef-unique'. > apertium-eo-ca.ca.dix:3606: element pardef: Schemas validity error : Element > 'pardef': Duplicate key-sequence ['angl/ès__n'] in unique identity-constraint > 'pardef-unique'. > apertium-eo-ca.ca.dix:8883: element pardef: Schemas validity error : Element > 'pardef': Duplicate key-sequence ['fo/ndre__vblex'] in unique > identity-constraint 'pardef-unique'. > apertium-eo-ca.ca.dix:15192: element pardef: Schemas validity error : Element > 'pardef': Duplicate key-sequence ['concórr/er__vblex'] in unique > identity-constraint 'pardef-unique'. > apertium-preprocess-transfer apertium-eo-ca.ca-eo.t1x ca-eo.t1x.bin > lt-comp lr apertium-eo-ca.ca.dix ca-eo.automorf.bin apertium-eo-ca.ca.acx > Warning (3135): Paths to rule 25 blocked by rule 7. > Warning (4174): Paths to rule 33 blocked by rule 27. > Warning (4174): Paths to rule 33 blocked by rule 27. > lt-comp rl apertium-eo-ca.eo-ca.dix ca-eo.autobil.bin > Warning (7438): Paths to rule 61 blocked by rule 60. > Warning (7438): Paths to rule 61 blocked by rule 60. > Warning (7438): Paths to rule 61 blocked by rule 60. > Warning (7438): Paths to rule 61 blocked by rule 60. > Warning (11728): Paths to rule 94 blocked by rule 93. > Warning (11728): Paths to rule 94 blocked by rule 93. > Warning (11728): Paths to rule 94 blocked by rule 93. > Warning (11728): Paths to rule 94 blocked by rule 93. > Warning (11728): Paths to rule 94 blocked by rule 93. > Warning (11728): Paths to rule 94 blocked by rule 93. > Warning (12094): Paths to rule 97 blocked by rule 96. > Warning (12094): Paths to rule 97 blocked by rule 96. > Warning (12094): Paths to rule 97 blocked by rule 96. > Warning (12094): Paths to rule 97 blocked by rule 96. > Warning (12094): Paths to rule 97 blocked by rule 96. > Warning (12094): Paths to rule 97 blocked by rule 96. > Warning (12094): Paths to rule 97 blocked by rule 96. > Warning (12094): Paths to rule 97 blocked by rule 96. > Warning (12094): Paths to rule 97 blocked by rule 96. > Warning (12094): Paths to rule 97 blocked by rule 96. > Warning (12094): Paths to rule 97 blocked by rule 96. > Warning (12094): Paths to rule 97 blocked by rule 96. > Warning (12094): Paths to rule 97 blocked by rule 96. > Warning (12094): Paths to rule 97 blocked by rule 96. > Warning (12094): Paths to rule 97 blocked by rule 96. > Warning (12094): Paths to rule 97 blocked by rule 96. > Warning (12094): Paths to rule 97 blocked by rule 96. > Warning (12094): Paths to rule 97 blocked by rule 96. > Warning (13173): Paths to rule 109 blocked by rule 24. > Warning (13173): Paths to rule 109 blocked by rule 24. > Warning (13173): Paths to rule 109 blocked by rule 24. > Warning (13173): Paths to rule 109 blocked by rule 24. > final@inconditional 15 60 > main@standard 45269 82925 > apertium-validate-interchunk apertium-eo-ca.ca-eo.antaux_t2x > apertium-preprocess-transfer apertium-eo-ca.ca-eo.antaux_t2x > ca-eo.antaux_t2x.bin > apertium-validate-interchunk apertium-eo-ca.ca-eo.antaux2_t2x > apertium-preprocess-transfer apertium-eo-ca.ca-eo.antaux2_t2x > ca-eo.antaux2_t2x.bin > apertium-validate-interchunk apertium-eo-ca.ca-eo.t2x > apertium-preprocess-transfer apertium-eo-ca.ca-eo.t2x ca-eo.t2x.bin > Warning (2020): Paths to rule 29 blocked by rule 26. > Warning (2020): Paths to rule 29 blocked by rule 26. > Warning (2020): Paths to rule 29 blocked by rule 26. > Warning (2020): Paths to rule 29 blocked by rule 26. > Warning (2020): Paths to rule 29 blocked by rule 26. >
Bug#978374: sundials: FTBFS: tests failed
Source: sundials Version: 4.1.0+dfsg-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > (cd debian/build; OMPI_MCA_rmaps_base_oversubscribe=1 ../nofakeroot ctest) > Test project /<>/debian/build > Start 1: ark_analytic > 1/76 Test #1: ark_analytic .. Passed > 0.00 sec > Start 2: cvRoberts_dns > 2/76 Test #2: cvRoberts_dns . Passed > 0.00 sec > Start 3: cvsRoberts_dns > 3/76 Test #3: cvsRoberts_dns Passed > 0.00 sec > Start 4: idaRoberts_dns > 4/76 Test #4: idaRoberts_dns Passed > 0.00 sec > Start 5: idasRoberts_dns > 5/76 Test #5: idasRoberts_dns ... Passed > 0.00 sec > Start 6: kinRoberts_fp > 6/76 Test #6: kinRoberts_fp . Passed > 0.00 sec > Start 7: test_nvector_serial_1000_0 > 7/76 Test #7: test_nvector_serial_1000_0 Passed > 0.00 sec > Start 8: test_nvector_serial_1_0 > 8/76 Test #8: test_nvector_serial_1_0 ... Passed > 0.04 sec > Start 9: test_nvector_mpi_1000_0 > 9/76 Test #9: test_nvector_mpi_1000_0 ...***Failed > 0.03 sec > Start 10: test_nvector_mpi_4_1000_0 > 10/76 Test #10: test_nvector_mpi_4_1000_0 .***Failed > 0.01 sec > Start 11: test_nvector_parhyp_1000_0 > 11/76 Test #11: test_nvector_parhyp_1000_0 ***Failed > 0.02 sec > Start 12: test_nvector_parhyp_4_1000_0 > 12/76 Test #12: test_nvector_parhyp_4_1000_0 ..***Failed > 0.01 sec > Start 13: test_nvector_openmp_1000_1_0 > 13/76 Test #13: test_nvector_openmp_1000_1_0 .. Passed > 0.01 sec > Start 14: test_nvector_openmp_1000_2_0 > 14/76 Test #14: test_nvector_openmp_1000_2_0 .. Passed > 0.01 sec > Start 15: test_nvector_openmp_1000_4_0 > 15/76 Test #15: test_nvector_openmp_1000_4_0 .. Passed > 0.01 sec > Start 16: test_nvector_openmp_1_1_0 > 16/76 Test #16: test_nvector_openmp_1_1_0 . Passed > 0.05 sec > Start 17: test_nvector_openmp_1_2_0 > 17/76 Test #17: test_nvector_openmp_1_2_0 . Passed > 0.03 sec > Start 18: test_nvector_openmp_1_4_0 > 18/76 Test #18: test_nvector_openmp_1_4_0 . Passed > 0.03 sec > Start 19: test_nvector_petsc_1000_0 > 19/76 Test #19: test_nvector_petsc_1000_0 .***Failed > 0.02 sec > Start 20: test_nvector_petsc_4_1000_0 > 20/76 Test #20: test_nvector_petsc_4_1000_0 ...***Failed > 0.01 sec > Start 21: test_sunmatrix_dense_100_100_0 > 21/76 Test #21: test_sunmatrix_dense_100_100_0 Passed > 0.00 sec > Start 22: test_sunmatrix_dense_200_1000_0 > 22/76 Test #22: test_sunmatrix_dense_200_1000_0 ... Passed > 0.01 sec > Start 23: test_sunmatrix_dense_2000_100_0 > 23/76 Test #23: test_sunmatrix_dense_2000_100_0 ... Passed > 0.01 sec > Start 24: test_sunmatrix_band_10_2_3_0 > 24/76 Test #24: test_sunmatrix_band_10_2_3_0 .. Passed > 0.00 sec > Start 25: test_sunmatrix_band_300_7_4_0 > 25/76 Test #25: test_sunmatrix_band_300_7_4_0 . Passed > 0.00 sec > Start 26: test_sunmatrix_band_1000_8_8_0 > 26/76 Test #26: test_sunmatrix_band_1000_8_8_0 Passed > 0.00 sec > Start 27: test_sunmatrix_band_5000_3_20_0 > 27/76 Test #27: test_sunmatrix_band_5000_3_20_0 ... Passed > 0.02 sec > Start 28: test_sunmatrix_sparse_400_400_0_0 > 28/76 Test #28: test_sunmatrix_sparse_400_400_0_0 . Passed > 0.02 sec > Start 29: test_sunmatrix_sparse_450_450_1_0 > 29/76 Test #29: test_sunmatrix_sparse_450_450_1_0 . Passed > 0.02 sec > Start 30: test_sunmatrix_sparse_200_1000_0_0 > 30/76 Test #30: test_sunmatrix_sparse_200_1000_0_0 Passed > 0.01 sec > Start 31: test_sunmatrix_sparse_6000_350_0_0 > 31/76 Test #31: test_sunmatrix_sparse_6000_350_0_0
Bug#978377: apertium-eo-fr: FTBFS: Error: Invalid dictionary (hint: entry on the right beginning with whitespace)
Source: apertium-eo-fr Version: 0.9.0~r57551-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > apertium-validate-dictionary apertium-eo-fr.fr.dix > apertium-eo-fr.fr.dix:4195: element pardef: Schemas validity error : Element > 'pardef': Duplicate key-sequence ['fa/illir__vblex'] in unique > identity-constraint 'pardef-unique'. > apertium-eo-fr.fr.dix:6615: element pardef: Schemas validity error : Element > 'pardef': Duplicate key-sequence ['épou/x__n'] in unique identity-constraint > 'pardef-unique'. > lt-comp lr apertium-eo-fr.fr.dix fr-eo.automorf.bin apertium-eo-fr.fr.acx > apostrophes@postblank 3758 5345 > final@inconditional 69 424 > main@standard 92977 155700 > negations@standard 35117 49188 > negations_apost@postblank 3334 4708 > unstandard_orth@standard 4572 6896 > unstandard_orth_apost@postblank 139 180 > apertium-validate-dictionary apertium-eo-fr.eo-fr.dix > lt-comp rl apertium-eo-fr.eo-fr.dix fr-eo.autobil.bin > Error: Invalid dictionary (hint: entry on the right beginning with whitespace) > make[2]: *** [Makefile:783: fr-eo.autobil.bin] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/12/26/apertium-eo-fr_0.9.0~r57551-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
clasp_3.3.5-2_amd64.changes ACCEPTED into experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 26 Dec 2020 21:25:44 + Source: clasp Architecture: source Version: 3.3.5-2 Distribution: experimental Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Thomas Krennwallner Changes: clasp (3.3.5-2) experimental; urgency=medium . [ Debian Janitor ] * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Fix day-of-week for changelog entry 1.3.2-2. . [ Thomas Krennwallner ] * debian/control: bump Build-Depends to debhelper-compat 13 * debian/control: bump Standards-version to 4.5.1 (no changes required) * compile with g++-10 >= 10.2.1 * Set upstream metadata fields: Changelog, Contact, FAQ, Name, Other-References, Reference Checksums-Sha1: 4b761212faa2220ad7cb1fe37d29683f22680cfb 2017 clasp_3.3.5-2.dsc 78c95ab3be81a6868670e2d9eadd47dfde22938c 8748 clasp_3.3.5-2.debian.tar.xz e555076d9aa4a19f3fa60cb64175d7943cc4e96e 7511 clasp_3.3.5-2_amd64.buildinfo Checksums-Sha256: e7b3691668ef8f025963a40f812318d176684d7e85ad1b39d925818138e7704d 2017 clasp_3.3.5-2.dsc 8efb95429901d4cbcb0b57397f37a89e82099c2628e43edd1a1cf22cc6a6a9eb 8748 clasp_3.3.5-2.debian.tar.xz b6ec54d4f8c5c133edbffbd954541ec2532660417f8460c4bcba2ec3348ecc9f 7511 clasp_3.3.5-2_amd64.buildinfo Files: cd962a8287641316382b0fbb15785304 2017 interpreters optional clasp_3.3.5-2.dsc d114f569c3222c4ad53eaf6d7afa3beb 8748 interpreters optional clasp_3.3.5-2.debian.tar.xz 7ac8a2f207c47c330cc7d0cccf39c88d 7511 interpreters optional clasp_3.3.5-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEzH7vLECGZFUde0TKJ5ffdKZmmqkFAl/nsxYACgkQJ5ffdKZm mqls6g/+PjQOZFt/8r3B2WIHsBvAdtt40dYW9rrw7HugFlLVgPkhvkMSadrcGk/s V4QxKfDACmPBUCSxN2qt/qJLdWUoII6pnrimit2HTCtAc618tx05l58HrhNmKcU/ u2N8g9EZpenrBRpCysMrQYaxcIo3VCylvpFtpLwUrYgQVfP3JjuoaGsy+Lr7Kcrl CDWL9xEM7WwC8RMPjtlgxFMOvxXR5XjaJuqq4JJGDLpCpor0ZRxD9WslO5krSP8e D0lxCd5d4hAq+z4iunDyD28TnqGzYQfg3vlGa/ckrS0xgJWGnFKt7T4b5fgS7HGI CiNtt96abH405+F7t9Qlfk++LaUU/D2vbaei8gmW96/L5hsN9bAbQnsZ3NYXR6mL JLrMzGiINQU4wDoLSeZ++ZYPaIsmxavr5CX6g1KhGRlTkH66x0Zfn6K36kWHirl+ etKbRMAsJ03saZ2PKNJkFV403thF36+vvby/PUVyz8Hhy5Iekf/iPdln/d6Wm3k7 r0H0DQh/ie2ShERBaQE7298G7ldrd1C+QPSRz4g4vUUNmZT4b5JTyoInnuKLkVHH MQsgK/UG/Bmijd0+TQz7YzQXV9jA86Cw/DVbUIyYmWbaEH+zmmKHDxUi5wAiYrhK qiaqQzDH6arSE72BpibnMetXLmevgf8RdJewUuEaaEADN9zaLrk= =yrQ1 -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
macaulay2_1.16.99+git40.3a512e5+ds-1~exp1_source.changes ACCEPTED into experimental
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 26 Dec 2020 00:29:42 -0500
Source: macaulay2
Architecture: source
Version: 1.16.99+git40.3a512e5+ds-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Doug Torrance
Changes:
macaulay2 (1.16.99+git40.3a512e5+ds-1~exp1) experimental; urgency=medium
.
* New upstream beta release.
* debian/control
- Add packages to Build-Depends.
+ dh-linktree: We now use this debhelper addon to create symbolic
links to Debian copies of GPL licenses and various Javascript
libraries instead of patching the files directly to point to
them.
+ libboost-regex-dev: Replaces embedded copy of GNU regex library
used in previous releases.
+ libboost-stacktrace-dev: Improves readability of stack traces.
- Add Build-Depends-Indep.
+ jdupes: Moved from Build-Depends; only needed for building
documentation.
+ Various fonts and Javascript libraries; needed during build
by dh_linktree.
+ w3c-markup-validator: Used to validate html in documentation.
- Bump Standards-Version to 4.5.1.
- Remove Javascript libraries from Recommends. They will now be
pulled in by ${misc:Depends} thanks to dh_linktree.
- Add emacs to Recommends for elpa-macaulay2.
* debian/copyright
- Add KaTeX files to Files-Excluded.
- Add paragraph for KaTeX files.
- Remove paragraph for embedded GNU regex library.
- Add licensing information for new packages added since previous
release.
* debian/copyright-helper.m2
- New Macaulay2 script to help generate debian/copyright paragraphs
for new packages.
* debian/macaulay2-common.linktrees
- New file; tell dh_linktree where Debian copies of GPL licenses
and Javascript libraries are located.
* debian/macaulay2-common.lintian-overrides
- Update package-contains-documentation-outside-usr-share-doc
overrides for files that have changed since previous release.
* debian/missing-source/render-a11y-string.js
- Add source for minified KaTeX file that isn't in Debian yet.
* debian/patches
- Remove patches applied (or otherwise made unnecessary) upstream.
+ fix-*.patch
+ hardening.patch
+ remove-build-paths-from-cached-files.patch
+ remove-build-paths-from-docs.patch (Patch remains, but only
increases the default print width of examples.)
+ use-debian-{4ti2,cohomcalg,csdp,gfan,nauty,normaliz,topcom}.patch
- Refresh remaining patches for new upstream version.
* debian/patches/skip-computations-book-test.patch
- Rename from fix-computations-book-test.patch; the behavior of the
test is too unpredictable between different architectures, so
we skip it entirely instead of trying to fix it.
* debian/patches/skip-*-{example,test}.patch
- Skip some additional examples and tests that have been known
to fail on various architectures.
* debian/patches/use-debian-{gpl,javascript}.patch
- Remove patches; we use dh_linktree for the same purpose instead.
* debian/README.Debian
- Add information about KaTeX to "Javascript libraries" section.
- Add section on using dwww to view the Macaulay2 documentation.
* debian/rules
- Use dh_linktree addon.
- New execute_before_dh_auto_build target; touch KaTeX files to
prevent html-check-links test from failing.
- Drop check for "nocheck" in DEB_BUILD_OPTIONS from
override_dh_auto_test rule; not necessary in debhelper 13.
We also append "-arch" to this target.
- New override_dh_auto_test-indep rule to validate html docs.
- Switch override_dh_link target that calls jdupes to
execute_before_dh_link-indep target.
- Switch override_dh_elpa target that generates -pkg.el file
to execute_before_dh_elpa target.
* debian/tests/check.m2
- Remove file; no longer needed.
* debian/tests/control
- Use upstream's updated --check command line argument to run
continuous integration tests.
* debian/upstream/metadata
- Add recent NSF grants to Funding.
- Add new Macaulay2Web interface to Webservice.
Checksums-Sha1:
44f88c8aafc9e9c5f270cb1612392720c53f8779 3070
macaulay2_1.16.99+git40.3a512e5+ds-1~exp1.dsc
a3e79a9fba7e0c933273fd0e993fa43fe4c63f73 8760572
macaulay2_1.16.99+git40.3a512e5+ds.orig.tar.xz
4233f9fa8fa92d0486c508153f85754634f91580 53824
macaulay2_1.16.99+git40.3a512e5+ds-1~exp1.debian.tar.xz
fc2bdd3e9b6a0c590899899550f5d7a9afaeb14d 9097
macaulay2_1.16.99+git40.3a512e5+ds-1~exp1_source.buildinfo
Checksums-Sha256:
379c8b49dd65076a11fc542ea7c81006d26509cc639eb1b48d0e8ab18209641d 3070
macaulay2_1.16.99+git40.3a512e5+ds-1~exp1.dsc
235e5836f7a88fd7541527f1838fb2a05d50cf68ff394344aba84bc949dad6bc 8760572
macaulay2_1.16.99+git40.3a512e5+ds.orig.tar.xz
841d12ba
Processed: Re: Bug#978359: apertium-br-fr: FTBFS: Error: Invalid dictionary (hint: entry on the right beginning with whitespace)
Processing commands for cont...@bugs.debian.org: > forwarded 978359 https://github.com/apertium/apertium-br-fr/issues/4 Bug #978359 [src:apertium-br-fr] apertium-br-fr: FTBFS: Error: Invalid dictionary (hint: entry on the right beginning with whitespace) Set Bug forwarded-to-address to 'https://github.com/apertium/apertium-br-fr/issues/4'. > thanks Stopping processing here. Please contact me if you need assistance. -- 978359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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#978359: apertium-br-fr: FTBFS: Error: Invalid dictionary (hint: entry on the right beginning with whitespace)
forwarded 978359 https://github.com/apertium/apertium-br-fr/issues/4 thanks Fixed in upstream. -- Tino Didriksen -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Processed: Re: Bug#978369: apertium-eo-ca: FTBFS: Error: Invalid dictionary (hint: entry on the right beginning with whitespace)
Processing commands for cont...@bugs.debian.org: > forwarded 978369 https://github.com/apertium/apertium-eo-ca/issues/2 Bug #978369 [src:apertium-eo-ca] apertium-eo-ca: FTBFS: Error: Invalid dictionary (hint: entry on the right beginning with whitespace) Set Bug forwarded-to-address to 'https://github.com/apertium/apertium-eo-ca/issues/2'. > thanks Stopping processing here. Please contact me if you need assistance. -- 978369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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#978369: apertium-eo-ca: FTBFS: Error: Invalid dictionary (hint: entry on the right beginning with whitespace)
forwarded 978369 https://github.com/apertium/apertium-eo-ca/issues/2 thanks Fixed in upstream. -- Tino Didriksen -- 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 clasp_3.3.5-3_amd64.changes
clasp_3.3.5-3_amd64.changes uploaded successfully to localhost along with the files: clasp_3.3.5-3.dsc clasp_3.3.5-3.debian.tar.xz clasp_3.3.5-3_amd64.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
clasp_3.3.5-3_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 27 Dec 2020 01:15:36 + Source: clasp Architecture: source Version: 3.3.5-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Thomas Krennwallner Changes: clasp (3.3.5-3) unstable; urgency=medium . * Upload to unstable Checksums-Sha1: 1c6688a1600f42824104efd251810a3af9029824 2017 clasp_3.3.5-3.dsc ca771fd3e12e6d518e2098ecefe5e8e4dab49325 8776 clasp_3.3.5-3.debian.tar.xz 716727016661594e18394513a570afeb626d5505 7511 clasp_3.3.5-3_amd64.buildinfo Checksums-Sha256: ef29a511556e6a2f77ad078f54aaa41a59b65252b7f84d8685000ada338371a9 2017 clasp_3.3.5-3.dsc dbbd962a9a3b1f1b64a483888114cd8780ba5e7fa3e79036232dabe2edce867d 8776 clasp_3.3.5-3.debian.tar.xz 9360002c0ddca00097d5f8102bcc01da473e0986caf2a7ccf9849182f2a89e08 7511 clasp_3.3.5-3_amd64.buildinfo Files: b4d640e10f11ff07d25fb4a48daabfe5 2017 interpreters optional clasp_3.3.5-3.dsc 552c97e2e3e3297063aa3b35b595a597 8776 interpreters optional clasp_3.3.5-3.debian.tar.xz f9df63951d50e323195b780b569b99ec 7511 interpreters optional clasp_3.3.5-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEzH7vLECGZFUde0TKJ5ffdKZmmqkFAl/n4rUACgkQJ5ffdKZm mqmfyQ//WKEjH9y/+skiQ8KR7/yQZxuNUFeWe80jSu8635MprM+R4kskEYQD8VTm BViGfdS3r5DrvsfMZ2pgmXUA/Cku/WzLteSFUbtzZAKDwvi5XKRvrcUUw/bEXJfw jQti8vA+A+JMdg/K6L3Fq/OL/NQrsjToPx7pNvIyLv1+dp43mtfXBTL/rDGGFQFf oLeQ/cr8wSfs8PCgBbhmDw6W/9gJWs/+00/52jQYQiu45aLqqdqsJ42QxnnLFBZ/ HXfQJmDzgecxyHR0KeGPCUw47hU86g06oPoebmfgKpJhPgTxnlzXzhRdbO7KIyXa 7Qzz6+9YZds+6yQcU5VgV3f4HoUYdvBgXMEzRSTb9tgDeZpV2761+IQHeMjhPe+0 XUv9bx+oYczaTrADEhdpbe0zjfMxFNiDYizbKhzKDQGlxC6HYtts5zipvHSzCPYQ zJ1sGkGGbiJPgNe/dvLMmiKuFn8VWZbWZDpe3gz+M7AEAEFfKr+s7UUla1ikolPS HzlPXeIU+0pIVUwy0ML3wXIpyzrOZFQCoV5MLZxrBX9ol4iuRYjAM65mcLpFK3wQ tIUeeq9uNqaVZ6JapH76uW/Agu/uSYTTipefww5cYqEGBoXwWMKmavA/k5U/ejik G2q6Z+KPHV7f5eihMLtwmHJFrbjDAqbLttVDjmXn00T44KVMa0M= =6oEQ -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 opencascade_7.5.0+dfsg1-3_source.changes
opencascade_7.5.0+dfsg1-3_source.changes uploaded successfully to localhost along with the files: opencascade_7.5.0+dfsg1-3.dsc opencascade_7.5.0+dfsg1-3.debian.tar.xz opencascade_7.5.0+dfsg1-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
opencascade_7.5.0+dfsg1-3_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 26 Dec 2020 19:01:29 -0600 Source: opencascade Architecture: source Version: 7.5.0+dfsg1-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Kurt Kremitzki Closes: 978017 Changes: opencascade (7.5.0+dfsg1-3) unstable; urgency=medium . * [c688fcc] Undo adding VTK integration for now (Closes: #978017) Checksums-Sha1: 919625ecdee176ffe1fc2c902d33809ca7aff8ae 3516 opencascade_7.5.0+dfsg1-3.dsc 545425ff741ffb477c64ce83d3a15a1b838a9263 66004 opencascade_7.5.0+dfsg1-3.debian.tar.xz 103c0d05d4597f8efadefc3249fb8b4d075cb28f 11301 opencascade_7.5.0+dfsg1-3_source.buildinfo Checksums-Sha256: 28ffe4fee8e42994292210cca2c1b4bd6c9bd5e562d67e7d83ad9bd77bcc91b7 3516 opencascade_7.5.0+dfsg1-3.dsc 422c94994882085abe3fd4f684988030fc347ea9ff206f73cd88cbd000b2e6d9 66004 opencascade_7.5.0+dfsg1-3.debian.tar.xz 0a8eecc403619e4e00a49c4a6e226d747f0b841b0f750d3b3b4d14605dc144b8 11301 opencascade_7.5.0+dfsg1-3_source.buildinfo Files: f6f61a098d3df7e041b132ccfe0aece7 3516 science optional opencascade_7.5.0+dfsg1-3.dsc cbc2c38d3c24390a22e48f7aebc0e073 66004 science optional opencascade_7.5.0+dfsg1-3.debian.tar.xz 6f3cdabcadda405eff1e2ae88f94ff35 11301 science optional opencascade_7.5.0+dfsg1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEEh8RU7HmiYTD5HEfrKUghB0bfc8AFAl/oBT4WHGtrcmVtaXR6 a2lAZGViaWFuLm9yZwAKCRApSCEHRt9zwAAlEAC7zURzrUEwn6Ndeu+7n4Mzhw7t Zgpjb/ohs3/Eiwi9ClXp6arHALu/l5gevwxJ1V2ZnnF14uMt7w9yUgqrebHJczyl sWsmNXqoNVFvDfX+nVZ5+Ur/gjT7wOaXx8ic4o/6ZwtDZDjkfgnZG38XQRQncNIO 0CcDZMBlwVXwg+B86+Lk5bFgtrn6Nfr9AKXSNfV7w83mqYhmQxP0BqdrTRHsSo1m hQuLChIjMNPbLVQtCv7tQLZ+OpNqWTivdimKsZXPd9Jt/VGQaofMytSn+FidVjwf sRw3P0htx8CJOze8Oqb+yOLChnnKwDdr3UOXcu47SOVeEx4ofrFhhjWKTZKvQoXr //USKXlEsKF7CP0HEbVugAYcZy7jS03LNgo41lNLQvRiGvIT+nUhg+tIFmIQ9Qlt AZReKATLB/zz+SpRhkxkkwp7IseSt/laKRUAbYLLRoKPBf+VgoiM4JO3fZRSfm1q zyewVroYp74Qr7kS5dQYNZmzOMga7ESWfNUkt8702wBD/CvhS2320agVZp04qOoG SoZBxIyBdiJCP5X0emXJ3Yn6yTyucgCDy52j9KaLbrpPQ4kX1qquL7995ji9Q7vh NqvfObrCAFLPgs4L2kE10eDrCfhjnMM140P2chslg2h/C6GeBwJx84FD1IHEQbmy iCoAvZn3XAf1+KjeHw== =Zfht -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
Bug#978017: marked as done (opencascade: please, make dependency on libvtk7 optional)
Your message dated Sun, 27 Dec 2020 04:18:58 + with message-id and subject line Bug#978017: fixed in opencascade 7.5.0+dfsg1-3 has caused the Debian Bug report #978017, regarding opencascade: please, make dependency on libvtk7 optional to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 978017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: opencascade Version: 7.5.0+dfsg1-2 Severity: wishlist Dear maintainer, Most applications depending on libocct-* libraries do not need the Vtk visualization (for example Kicad) and Vtk adds about 220MB of extra disk space. It would be great if the dependency to Vtk could be made optional (or a recomends), so that users that does not need the visuzalization can omit it. Regards, Daniel. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: opencascade Source-Version: 7.5.0+dfsg1-3 Done: Kurt Kremitzki We believe that the bug you reported is fixed in the latest version of opencascade, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 978...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kurt Kremitzki (supplier of updated opencascade package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 26 Dec 2020 19:01:29 -0600 Source: opencascade Architecture: source Version: 7.5.0+dfsg1-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Kurt Kremitzki Closes: 978017 Changes: opencascade (7.5.0+dfsg1-3) unstable; urgency=medium . * [c688fcc] Undo adding VTK integration for now (Closes: #978017) Checksums-Sha1: 919625ecdee176ffe1fc2c902d33809ca7aff8ae 3516 opencascade_7.5.0+dfsg1-3.dsc 545425ff741ffb477c64ce83d3a15a1b838a9263 66004 opencascade_7.5.0+dfsg1-3.debian.tar.xz 103c0d05d4597f8efadefc3249fb8b4d075cb28f 11301 opencascade_7.5.0+dfsg1-3_source.buildinfo Checksums-Sha256: 28ffe4fee8e42994292210cca2c1b4bd6c9bd5e562d67e7d83ad9bd77bcc91b7 3516 opencascade_7.5.0+dfsg1-3.dsc 422c94994882085abe3fd4f684988030fc347ea9ff206f73cd88cbd000b2e6d9 66004 opencascade_7.5.0+dfsg1-3.debian.tar.xz 0a8eecc403619e4e00a49c4a6e226d747f0b841b0f750d3b3b4d14605dc144b8 11301 opencascade_7.5.0+dfsg1-3_source.buildinfo Files: f6f61a098d3df7e041b132ccfe0aece7 3516 science optional opencascade_7.5.0+dfsg1-3.dsc cbc2c38d3c24390a22e48f7aebc0e073 66004 science optional opencascade_7.5.0+dfsg1-3.debian.tar.xz 6f3cdabcadda405eff1e2ae88f94ff35 11301 science optional opencascade_7.5.0+dfsg1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEEh8RU7HmiYTD5HEfrKUghB0bfc8AFAl/oBT4WHGtrcmVtaXR6 a2lAZGViaWFuLm9yZwAKCRApSCEHRt9zwAAlEAC7zURzrUEwn6Ndeu+7n4Mzhw7t Zgpjb/ohs3/Eiwi9ClXp6arHALu/l5gevwxJ1V2ZnnF14uMt7w9yUgqrebHJczyl sWsmNXqoNVFvDfX+nVZ5+Ur/gjT7wOaXx8ic4o/6ZwtDZDjkfgnZG38XQRQncNIO 0CcDZMBlwVXwg+B86+Lk5bFgtrn6Nfr9AKXSNfV7w83mqYhmQxP0BqdrTRHsSo1m hQuLChIjMNPbLVQtCv7tQLZ+OpNqWTivdimKsZXPd9Jt/VGQaofMytSn+FidVjwf sRw3P0htx8CJOze8Oqb+yOLChnnKwDdr3UOXcu47SOVeEx4ofrFhhjWKTZKvQoXr //USKXlEsKF7CP0HEbVugAYcZy7jS03LNgo41lNLQvRiGvIT+nUhg+tIFmIQ9Qlt AZReKATLB/zz+SpRhkxkkwp7IseSt/laKRUAbYLLRoKPBf+VgoiM4JO3fZRSfm1q zyewVroYp74Qr7kS5dQYNZmzOMga7ESWfNUkt8702wBD/CvhS2320agVZp04qOoG SoZBxIyBdiJCP5X0emXJ3Yn6yTyucgCDy52j9KaLbrpPQ4kX1qquL7995ji9Q7vh NqvfObrCAFLPgs4L2kE10eDrCfhjnMM140P2chslg2h/C6GeBwJx84FD1IHEQbmy iCoAvZn3XAf1+KjeHw== =Zfht -END PGP SIGNATURE End Message --- -- 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-bond-core 1.8.6-3 MIGRATED to testing
FYI: The status of the ros-bond-core source package in Debian's testing distribution has changed. Previous version: 1.8.6-2 Current version: 1.8.6-3 -- 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
ros-image-common 1.12.0-3 MIGRATED to testing
FYI: The status of the ros-image-common source package in Debian's testing distribution has changed. Previous version: 1.12.0-2 Current version: 1.12.0-3 -- 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
ros-catkin 0.8.9-2 MIGRATED to testing
FYI: The status of the ros-catkin source package in Debian's testing distribution has changed. Previous version: 0.8.9-1 Current version: 0.8.9-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
ros-navigation-msgs 1.14.1-2 MIGRATED to testing
FYI: The status of the ros-navigation-msgs source package in Debian's testing distribution has changed. Previous version: 1.14.1-1 Current version: 1.14.1-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
ros-roscpp-core 0.7.2-6 MIGRATED to testing
FYI: The status of the ros-roscpp-core source package in Debian's testing distribution has changed. Previous version: 0.7.2-4 Current version: 0.7.2-6 -- 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
ros-laser-geometry 1.6.5-3 MIGRATED to testing
FYI: The status of the ros-laser-geometry source package in Debian's testing distribution has changed. Previous version: 1.6.5-2 Current version: 1.6.5-3 -- 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
ros-ros-comm-msgs 1.11.3-2 MIGRATED to testing
FYI: The status of the ros-ros-comm-msgs source package in Debian's testing distribution has changed. Previous version: 1.11.3-1 Current version: 1.11.3-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
ros-geometric-shapes 0.7.0-4 MIGRATED to testing
FYI: The status of the ros-geometric-shapes source package in Debian's testing distribution has changed. Previous version: 0.7.0-3 Current version: 0.7.0-4 -- 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
ros-pcl-msgs 0.3.0-2 MIGRATED to testing
FYI: The status of the ros-pcl-msgs source package in Debian's testing distribution has changed. Previous version: 0.3.0-1 Current version: 0.3.0-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
ros-genpy 0.6.14-2 MIGRATED to testing
FYI: The status of the ros-genpy source package in Debian's testing distribution has changed. Previous version: 0.6.14-1 Current version: 0.6.14-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
ppl is marked for autoremoval from testing
ppl 1:1.2-8.1 is marked for autoremoval from testing on 2021-01-31 It (build-)depends on packages with these RC bugs: 977657: swi-prolog: FTBFS with OpenSSL 1.1.1i https://bugs.debian.org/977657 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
ros-genmsg 0.5.16-4 MIGRATED to testing
FYI: The status of the ros-genmsg source package in Debian's testing distribution has changed. Previous version: 0.5.16-3 Current version: 0.5.16-4 -- 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
ros-ros-environment 1.3.2-2 MIGRATED to testing
FYI: The status of the ros-ros-environment source package in Debian's testing distribution has changed. Previous version: 1.3.2-1 Current version: 1.3.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
ros-ros 1.15.7-2 MIGRATED to testing
FYI: The status of the ros-ros source package in Debian's testing distribution has changed. Previous version: 1.15.7-1 Current version: 1.15.7-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
ros-angles 1.9.13-2 MIGRATED to testing
FYI: The status of the ros-angles source package in Debian's testing distribution has changed. Previous version: 1.9.13-1 Current version: 1.9.13-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
ros-eigen-stl-containers 0.1.8-4 MIGRATED to testing
FYI: The status of the ros-eigen-stl-containers source package in Debian's testing distribution has changed. Previous version: 0.1.8-3 Current version: 0.1.8-4 -- 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
ros-python-qt-binding 0.4.3-3 MIGRATED to testing
FYI: The status of the ros-python-qt-binding source package in Debian's testing distribution has changed. Previous version: 0.4.3-2 Current version: 0.4.3-3 -- 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
urdfdom-headers 1.0.5-3 MIGRATED to testing
FYI: The status of the urdfdom-headers source package in Debian's testing distribution has changed. Previous version: 1.0.5-1 Current version: 1.0.5-3 -- 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
ros-actionlib 1.13.2-6 MIGRATED to testing
FYI: The status of the ros-actionlib source package in Debian's testing distribution has changed. Previous version: 1.13.2-5 Current version: 1.13.2-6 -- 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
ros-gencpp 0.6.5-2 MIGRATED to testing
FYI: The status of the ros-gencpp source package in Debian's testing distribution has changed. Previous version: 0.6.5-1 Current version: 0.6.5-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
ros-message-runtime 0.4.13-5 MIGRATED to testing
FYI: The status of the ros-message-runtime source package in Debian's testing distribution has changed. Previous version: 0.4.13-4 Current version: 0.4.13-5 -- 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
ros-rospack 2.6.2-5 MIGRATED to testing
FYI: The status of the ros-rospack source package in Debian's testing distribution has changed. Previous version: 2.6.2-3 Current version: 2.6.2-5 -- 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
pplpy is marked for autoremoval from testing
pplpy 0.8.4-4 is marked for autoremoval from testing on 2021-01-31 It (build-)depends on packages with these RC bugs: 977657: swi-prolog: FTBFS with OpenSSL 1.1.1i https://bugs.debian.org/977657 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
ros-dynamic-reconfigure 1.7.1-3 MIGRATED to testing
FYI: The status of the ros-dynamic-reconfigure source package in Debian's testing distribution has changed. Previous version: 1.7.1-2 Current version: 1.7.1-3 -- 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
ros-message-generation 0.4.1-4 MIGRATED to testing
FYI: The status of the ros-message-generation source package in Debian's testing distribution has changed. Previous version: 0.4.1-3 Current version: 0.4.1-4 -- 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
ros-roslisp 1.9.24-3 MIGRATED to testing
FYI: The status of the ros-roslisp source package in Debian's testing distribution has changed. Previous version: 1.9.24-2 Current version: 1.9.24-3 -- 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
ros-interactive-markers 1.12.0-5 MIGRATED to testing
FYI: The status of the ros-interactive-markers source package in Debian's testing distribution has changed. Previous version: 1.12.0-4 Current version: 1.12.0-5 -- 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
ros-rviz 1.14.4+dfsg-3 MIGRATED to testing
FYI: The status of the ros-rviz source package in Debian's testing distribution has changed. Previous version: 1.14.4+dfsg-2 Current version: 1.14.4+dfsg-3 -- 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
ros-rosconsole 1.14.3-2 MIGRATED to testing
FYI: The status of the ros-rosconsole source package in Debian's testing distribution has changed. Previous version: 1.14.3-1 Current version: 1.14.3-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
ros-genlisp 0.4.18-2 MIGRATED to testing
FYI: The status of the ros-genlisp source package in Debian's testing distribution has changed. Previous version: 0.4.18-1 Current version: 0.4.18-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
ros-nodelet-core 1.10.0-3 MIGRATED to testing
FYI: The status of the ros-nodelet-core source package in Debian's testing distribution has changed. Previous version: 1.10.0-2 Current version: 1.10.0-3 -- 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
ros-std-msgs 0.5.13-2 MIGRATED to testing
FYI: The status of the ros-std-msgs source package in Debian's testing distribution has changed. Previous version: 0.5.13-1 Current version: 0.5.13-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
ros-random-numbers 0.3.2-3 MIGRATED to testing
FYI: The status of the ros-random-numbers source package in Debian's testing distribution has changed. Previous version: 0.3.2-2 Current version: 0.3.2-3 -- 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
ros-pluginlib 1.13.0-3 MIGRATED to testing
FYI: The status of the ros-pluginlib source package in Debian's testing distribution has changed. Previous version: 1.13.0-1 Current version: 1.13.0-3 -- 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
ros-rosconsole-bridge 0.5.4-2 MIGRATED to testing
FYI: The status of the ros-rosconsole-bridge source package in Debian's testing distribution has changed. Previous version: 0.5.4-1 Current version: 0.5.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
ros-common-msgs 1.13.0-2 MIGRATED to testing
FYI: The status of the ros-common-msgs source package in Debian's testing distribution has changed. Previous version: 1.13.0-1 Current version: 1.13.0-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
ros-resource-retriever 1.12.6-3 MIGRATED to testing
FYI: The status of the ros-resource-retriever source package in Debian's testing distribution has changed. Previous version: 1.12.6-2 Current version: 1.12.6-3 -- 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
