Bug#925411: Count me as happy user of make-kpkg
Hello, I'm quite "suprised" by todays dist-upgrade. I use make-kpkg (with some wrapper scripts) since I switched to Debian around 2000. I just build 5.0.7 last Sunday. So this is a bad suprise this late in the development cycle. I did not have a chance to read all details of all bugs/links in this bug report (I'm in a bit of rush at the moment). Hopefully the replacement works as flawlessly as make-kpkg did. Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: Digital signature
Bug#922733: Bumped to serious
This is a show stopper bug for any package that uses the functionality. Bumping to serious. Scott K
Processed: severity of 922733 is serious
Processing commands for cont...@bugs.debian.org:
> severity 922733 serious
Bug #922733 {Done: Daniel Kahn Gillmor }
[python3-milter] python3-milter: Milter.utils.parseaddr() fails:
AttributeError: module 'email' has no attribute 'utils'
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
922733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Processed: caffe: FTBFS: Fatal error occurred, no output PDF file produced!
Processing commands for cont...@bugs.debian.org: > tags 924829 - patch Bug #924829 [texlive-latex-extra] caffe: FTBFS: Fatal error occurred, no output PDF file produced! Bug #920459 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #920621 [texlive-latex-extra] texlive-base: breaks build of forthcoming doxygen 1.8.15 Bug #921272 [texlive-latex-extra] texlive-latex-extra: package tabu broken when xcolor is used Bug #921299 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921776 [texlive-latex-extra] bliss: FTBFS (LaTeX error) Bug #921779 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921783 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921789 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921802 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921838 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Removed tag(s) patch. Removed tag(s) patch. Removed tag(s) patch. Removed tag(s) patch. Removed tag(s) patch. Removed tag(s) patch. Removed tag(s) patch. Removed tag(s) patch. Removed tag(s) patch. Removed tag(s) patch. Removed tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459 920621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920621 921272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921272 921299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921299 921776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921776 921779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921779 921783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921783 921789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921789 921802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921802 921838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921838 924829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#828669: marked as done (FTBFS under Django 1.10)
Your message dated Fri, 12 Apr 2019 23:33:52 + with message-id and subject line Bug#828669: fixed in python-django-mptt 0.8.7-1 has caused the Debian Bug report #828669, regarding FTBFS under Django 1.10 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.) -- 828669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828669 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-django-mptt Version: 0.8.3-1 Severity: important User: python-dja...@packages.debian.org Usertags: django110 django110-ftbfs Hi, Whilst rebuilding all reverse build-dependencies of python-django with the latest beta, I noticed that python-django-mptt FTBFS with 1.10. Please update your package to work with Django 1.10 (in experimental) as I will uploading it to unstable once it is released (and at the same time raising the severity of this bug to RC). Upstream's release notes may be helpful in diagnosing the issue: https://docs.djangoproject.com/en/dev/releases/1.10/ The full build log is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- python-django-mptt_0.8.3-1.log.txt.gz Description: Binary data --- End Message --- --- Begin Message --- Source: python-django-mptt Source-Version: 0.8.7-1 We believe that the bug you reported is fixed in the latest version of python-django-mptt, 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 828...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro (supplier of updated python-django-mptt 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: SHA256 Format: 1.8 Date: Fri, 12 Apr 2019 19:50:05 -0300 Source: python-django-mptt Architecture: source Version: 0.8.7-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Antonio Terceiro Closes: 828669 Changes: python-django-mptt (0.8.7-1) unstable; urgency=medium . * Team upload. . [ Brian May ] * New upstream version. . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org * d/copyright: Use https protocol in Format field * d/changelog: Remove trailing whitespaces . [ Chris Lamb ] * Remove trailing whitespaces. . [ Antonio Terceiro ] * debian/watch: pull tarball from github - the releases uploaded to pypi do not containt the tests directory * Import a new copy of the 0.8.7, which includes the tests directory (now really Closes: #828669) * skip failing test * Run test suite under autopkgtest Checksums-Sha1: 60963e1c9a5761bed9c20e2fcffc1722fb21d29d 2359 python-django-mptt_0.8.7-1.dsc 7de4ee85554980a4ec8cff12c4d8a671aa328b35 289137 python-django-mptt_0.8.7.orig.tar.gz 216423626ffcd0e883682d176e9f73a614deab1a 4096 python-django-mptt_0.8.7-1.debian.tar.xz e0ba824169e04259198ce7f601cf4c116d317e9c 7721 python-django-mptt_0.8.7-1_source.buildinfo Checksums-Sha256: e51f66a52378dc596b40ca174eca78de835c2859f4fe2d77cbe54d992e41c652 2359 python-django-mptt_0.8.7-1.dsc 5253c691b1ea7defa0e15334bacff4e3c96ebcf7706d5cd7641f0e55172308b2 289137 python-django-mptt_0.8.7.orig.tar.gz a1741b5cf6e337270862f2a337a0bf84f8bfe2d57b177a04e29ad7c5b20d1236 4096 python-django-mptt_0.8.7-1.debian.tar.xz a0b263e3184b0c5c46cb8a470dfcbad301390fcbc3b0650f18b045c2a2160b4b 7721 python-django-mptt_0.8.7-1_source.buildinfo Files: c240ff959ce29fb595689a36dc6371f7 2359 python optional python-django-mptt_0.8.7-1.dsc a2396f7d2a284b16ce9102fa739a38d8 289137 python optional python-django-mptt_0.8.7.orig.tar.gz 879cfd4f92afa1dbe62f9add40a2cc92 4096 python optional python-django-mptt_0.8.7-1.debian.tar.xz fa34a27f8a9522c928c3bd9b48326892 7721 python optional python-django-mptt_0.8.7-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlyxHqMACgkQ/A2xu81G C95O6hAAjoAPspV+lQTeigScIurwpvhg0sEl1CZO1rqmscoL0XCwAByHwxMjltT9 GG4L9pRERHNgOJgxmJxoZtfO/FQSGZqrDxSco9IDmU8vKi66H0Sb1Zd1rZjR1lxQ JJRnkoH+vS0W41/xqFjHp1EY6U53QH/uP6kNVde4H03O4xf+OWBCDBjDcYHav9st OEuO9BSZBz0LYXOiWMOLEJ9SmVS3xlovW9G3clEF2nuPVpXxJ+zNC+6wquY5WebQ EogOyINw5eo/HQaxGn6vpHY2uJcLkurZvNqy
Bug#925471: marked as done (mokutil fails for all non-trivial operations)
Your message dated Fri, 12 Apr 2019 23:03:37 + with message-id and subject line Bug#925471: fixed in mokutil 0.3.0+1538710437.fb6250f-1 has caused the Debian Bug report #925471, regarding mokutil fails for all non-trivial operations 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.) -- 925471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mokutil Version: 0.2.0-1+b3 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? - Trying to test Secure Boot support, as in https://wiki.debian.org/SecureBoot/Testing. * What exactly did you do (or not do) that was effective (or ineffective)? - Follow the guide until step 5.1 (which is the step where mokutil fails). * What was the outcome of this action? - After prompting for a password twice, mokutil fails with the following error message: Failed to write MokAuth Failed to unset MokNew Failed to enroll new keys * What outcome did you expect instead? - mokutil does not fail. *** End of the template - remove these template lines *** The reason for the failure is that since some time ago, Linux started creating EFI variables as immutable. Our old version of mokutil does not care about this. Thus, when mokutil attempts to write a second time (MokAuth) or unlink (MokNew) a variable, the operation fails. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de:fr:en_US (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mokutil depends on: ii libc6 2.28-8 ii libssl1.1 1.1.1b-1 mokutil recommends no packages. mokutil suggests no packages. -- no debconf information immutable-variables Description: Binary data --- End Message --- --- Begin Message --- Source: mokutil Source-Version: 0.3.0+1538710437.fb6250f-1 We believe that the bug you reported is fixed in the latest version of mokutil, 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 925...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon Quigley (supplier of updated mokutil 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: SHA256 Format: 1.8 Date: Fri, 12 Apr 2019 17:45:52 -0500 Source: mokutil Architecture: source Version: 0.3.0+1538710437.fb6250f-1 Distribution: unstable Urgency: medium Maintainer: Simon Quigley Changed-By: Simon Quigley Closes: 925471 Changes: mokutil (0.3.0+1538710437.fb6250f-1) unstable; urgency=medium . * Upload to Debian (Closes: #925471). * Adopt the package; thanks to Steve Langasek for your work! * Update Vcs-* to reflect the move to Salsa. Checksums-Sha1: b5d7d453471cec0e9dec0497cba4240187afa556 2070 mokutil_0.3.0+1538710437.fb6250f-1.dsc 9e3546b75a4151e987ab96e585d562c66df01b6a 29184 mokutil_0.3.0+1538710437.fb6250f.orig.tar.xz 445a5a47c589f4fcfffbb2294929e35f093901cd 3004 mokutil_0.3.0+1538710437.fb6250f-1.debian.tar.xz 0d6dda9bf4eb0d00aa855812eb820dfc566340cb 6614 mokutil_0.3.0+1538710437.fb6250f-1_source.buildinfo Checksums-Sha256: 7d2d742cbdcee3b2266b5580381056b736e3564d3872c1691e189ca4c2ff3b3c 2070 mokutil_0.3.0+1538710437.fb6250f-1.dsc c9e7d4796986fc5079788c095363bd2d5f6c94e7fa6b810c02a146f96dbba52d 29184 mokutil_0.3.0+1538710437.fb6250f.orig.tar.xz 102e1c50270cb6331b79822d58fa2085e08639fe36ca40606ac37402c3ad534d 3004 mokutil_0.3.0+1538710437.fb6250f-1.debian.tar.xz 20cb3d08ab385adc3e1b4aca8327c70906a22a3459caaac9a5ed6f4c7e52c1d7 6614 mokutil_0.3.0+1538710437.fb6250f-1_source.buildinfo Files: 8e93901332015ecd9e191c7198c55070 2070 admin optional mokutil_0.3.0+1538710437.fb6250f-1.dsc 7f3c5f66f0db0f896a43f50b05a8d2da 29184 admin optional mokutil_0.3.0+1538710437.fb6250f.orig.tar.xz
Bug#887733: Should this bug be closed?
This bug is still open but has been marked as fixed in the versions currently in testing/unstable and stable. It also has been fixed in oldstable-security. Should it be closed or is there any reason to still keep it open? signature.asc Description: This is a digitally signed message part.
Processed: caffe: FTBFS: Fatal error occurred, no output PDF file produced!
Processing commands for cont...@bugs.debian.org:
> reopen 924829
Bug #924829 {Done: Norbert Preining }
[texlive-latex-extra] caffe: FTBFS: Fatal error occurred, no output PDF file
produced!
Bug #920459 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #920621 {Done: Norbert Preining }
[texlive-latex-extra] texlive-base: breaks build of forthcoming doxygen 1.8.15
Bug #921272 {Done: Norbert Preining }
[texlive-latex-extra] texlive-latex-extra: package tabu broken when xcolor is
used
Bug #921299 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #921776 {Done: Norbert Preining }
[texlive-latex-extra] bliss: FTBFS (LaTeX error)
Bug #921779 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #921783 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #921789 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #921802 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #921838 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions texlive-extra/2018.20190131-2 and
texlive-extra/2018.20190227-1.
No longer marked as fixed in versions texlive-extra/2018.20190131-2 and
texlive-extra/2018.20190227-1.
No longer marked as fixed in versions texlive-extra/2018.20190131-2 and
texlive-extra/2018.20190227-1.
No longer marked as fixed in versions texlive-extra/2018.20190227-1 and
texlive-extra/2018.20190131-2.
No longer marked as fixed in versions texlive-extra/2018.20190227-1 and
texlive-extra/2018.20190131-2.
No longer marked as fixed in versions texlive-extra/2018.20190131-2 and
texlive-extra/2018.20190227-1.
No longer marked as fixed in versions texlive-extra/2018.20190227-1 and
texlive-extra/2018.20190131-2.
No longer marked as fixed in versions texlive-extra/2018.20190131-2 and
texlive-extra/2018.20190227-1.
No longer marked as fixed in versions texlive-extra/2018.20190131-2 and
texlive-extra/2018.20190227-1.
No longer marked as fixed in versions texlive-extra/2018.20190131-2 and
texlive-extra/2018.20190227-1.
No longer marked as fixed in versions texlive-extra/2018.20190227-1 and
texlive-extra/2018.20190131-2.
> kthxbye
Stopping processing here.
Please contact me if you need assistance.
--
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
920621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920621
921272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921272
921299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921299
921776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921776
921779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921779
921783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921783
921789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921789
921802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921802
921838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921838
924829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#924829: caffe: FTBFS: Fatal error occurred, no output PDF file produced!
reopen 924829
kthxbye
caffe still doesn't build with unstable's texlive-extra, a quick tail:
Package longtable Warning: Column widths have changed
(longtable)in table 5.5 on input line 97.
! Improper \prevdepth.
\tabu@verticalspacing ...tempdimc \the \prevdepth
\@tempdima \dimexpr \ht \t...
l.136 \end{DoxyParams}
?
! Emergency stop.
\tabu@verticalspacing ...tempdimc \the \prevdepth
\@tempdima \dimexpr \ht \t...
l.136 \end{DoxyParams}
! ==> Fatal error occurred, no output PDF file produced!
A full log can be found at:
https://people.debian.org/~adconrad/caffe_1.0.0+git20180821.99bd997-2build2_amd64.build
... Adam
Processed: severity of 925172 is serious
Processing commands for cont...@bugs.debian.org: > # Regression from Stretch > severity 925172 serious Bug #925172 [g++-mingw-w64-i686] g++-mingw-w64-i686: libstdc++fs.a not included in the Debian package Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 925172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925172 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923003: marked as done (CVE-2018-19873 CVE-2018-19871 CVE-2018-19870)
Your message dated Fri, 12 Apr 2019 20:40:09 + with message-id and subject line Bug#923003: fixed in qt4-x11 4:4.8.7+dfsg-18 has caused the Debian Bug report #923003, regarding CVE-2018-19873 CVE-2018-19871 CVE-2018-19870 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.) -- 923003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qt4-x11 Severity: grave Tags: security Three security issues fixed in QT5 also affect qt4-x11: https://blog.qt.io/blog/2018/12/04/qt-5-11-3-released-important-security-updates/ CVE-2018-19873: https://github.com/qt/qtbase/commit/621ab8ab59901cc3f9bd98be709929c9eac997a8 CVE-2018-19871: https://github.com/qt/qtimageformats/commit/7cfe47a8fe2f987fb2a066a696fb3d9d0afe4d65 (qt4-x11 affected in src/plugins/imageformats/tga/qtgafile.cpp) CVE-2018-19870: https://github.com/qt/qtbase/commit/2841e2b61e32f26900bde987d469c8b97ea31999 (qt4-x11 affected in src/gui/image/qgifhandler.cpp) Cheers, Moritz --- End Message --- --- Begin Message --- Source: qt4-x11 Source-Version: 4:4.8.7+dfsg-18 We believe that the bug you reported is fixed in the latest version of qt4-x11, 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 923...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Shachnev (supplier of updated qt4-x11 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: Fri, 12 Apr 2019 23:10:28 +0300 Source: qt4-x11 Architecture: source Version: 4:4.8.7+dfsg-18 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Dmitry Shachnev Closes: 923003 Changes: qt4-x11 (4:4.8.7+dfsg-18) unstable; urgency=medium . * Team upload. . [ Edward Betts ] * debian/NEWS: Replace UNRELEASED with unstable. . [ Alexander Volkov ] * Backport some vulnerability fixes from Qt 5 (closes: #923003). - CVE-2018-15518: double free or corruption in QXmlStreamReader. - CVE-2018-19869: Qt Svg crash when parsing malformed url reference. - CVE-2018-19870: NULL pointer dereference in QGifHandler. - CVE-2018-19871: QTgaFile CPU exhaustion. - CVE-2018-19872: crash when parsing a malformed PPM image. - CVE-2018-19873: QBmpHandler segfault on malformed BMP file. Checksums-Sha1: 8c60ce5ccb9566790121d04454f740d1bf18a707 6050 qt4-x11_4.8.7+dfsg-18.dsc c36d8ec6dbf1ca0277df157bea2b8fa4006c31fb 328360 qt4-x11_4.8.7+dfsg-18.debian.tar.xz c281f877990f6fee9621140d562544ff6e3f6ccf 13480 qt4-x11_4.8.7+dfsg-18_source.buildinfo Checksums-Sha256: 094e2ec62f777e3377327c98d7d82274bff983b4a0bd1220143ba5ffd1bb3f39 6050 qt4-x11_4.8.7+dfsg-18.dsc 63eb69acb9b3cc57a2292e71e3affbf5d7378387e8f8ecd85bfee4e581c4fee9 328360 qt4-x11_4.8.7+dfsg-18.debian.tar.xz 2986770440eea9eb36e42a56fabb914ad335eba1ab9de38c0635d70adb29f27e 13480 qt4-x11_4.8.7+dfsg-18_source.buildinfo Files: 8f3ee3c876d971e8b1cdec5f19375c73 6050 oldlibs optional qt4-x11_4.8.7+dfsg-18.dsc 9ade800670d889ae4c91bfd54dc4c244 328360 oldlibs optional qt4-x11_4.8.7+dfsg-18.debian.tar.xz 80658a5f2f372848c0cccb7bfea4cfdb 13480 oldlibs optional qt4-x11_4.8.7+dfsg-18_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEE8kKZ/xu8kBi5BqTLYCaTbS8ciuAFAlyw8uQTHG1pdHlhNTdA ZGViaWFuLm9yZwAKCRBgJpNtLxyK4JH5D/4i/kDi6DgW3x13uloD7sx6Wsz5AIGT Ud5q3g3d3swaUOrfNgQWG693WM650CGIxDkw7ziUr7F4+yF0hP28xkAJbtAMsDcf TtGJj3hoDZYBBLpM+EUfL2N92cjFWsWGpodW5D5K/0Lvj2tBOV1df6U9FyJ2+RGB SZAOqnQJ5N0QNaXq6e5ux44z4phxEANMJtu5aRMazjiOs8CJt20OBv0PSVwAKn9O xwVIb68fyvsrOTj9zTi8VHi/nOI5RisEFH84Kevl4oLQEYnmelFBKfE7fSrhwtvl v5z7kF+8iTdt8fyBhRlHEfCopd8yTB9DdmZNfPthhu3SMythzz++7a3bbpW3OeXa oZ7THc3aJjMstDMaht7Fks72WU44JTTMpo4OSxUMsHYpDirv24bQbf2cQVFBPhHS 9RLL0tQrrU1XkPi1y9Ky7MO7NtNIOpp/IOoLUhmQwnV9S/H+NZPtWxDiLI7ebp7E 1fepFLA87BNkBQsr4/jj9RpNSvzg6aNl3kfr9+9SqZzcPk9iEMQNyaMOax7OOVru WqsJ8rB+NNRAm6QXQ+OGiBJ0TZRcjzDpBlgqU+FMZiFk8voDhk6aP9v3WGLzbmKN niP+xbV4vdADsWHKuHKQ4dkcuQhO4Xf2Ru2A3YuQBw+m96uXsnBaACyNG+gDxXpU tb7AiI3AzCyQ+g== =/zyv -END PGP SIGNATURE End Message ---
Bug#924591: e2fsprogs?
I quickly checked the versions of e2fsprogs used by Android vs what it is in buster. It seems that buster is as new as the Android version. So either this specific feature was added via a Google patch or it was not enabled in the Debian build of e2fsprogs. Do you have any more information on the specific missing features?
Processed: sa-exim: Unbuildable/uninstallable in sid
Processing control commands: > block -1 by 879687 Bug #926952 [sa-exim] sa-exim: Unbuildable/uninstallable in sid 926952 was not blocked by any bugs. 926952 was not blocking any bugs. Added blocking bug(s) of 926952: 879687 -- 926952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#926952: sa-exim: Unbuildable/uninstallable in sid
Package: sa-exim Version: 4.2.1-16 Severity: serious Control: block -1 by 879687 Hello, with exim4/4.92-5 I have dropped support for sa-exim: The dlopen localscan patch in exim4 has been nonfunctional in unstable for quite some time (4.92~RC2-1/experimental/18 Dec, 4.92~RC3-1 unstable/26 Dec and buster/03 Jan). The issue only popped up end of March on the upstream user support ML. At this time I opened a tracking bug in exim #925982 and looked at sa-exim. It is dead upstream since 2006 and buggy: * https://lists.exim.org/lurker/message/20180726.113354.6d03efde.en.html * #879687 (This might be same issue, I just do not know. Chunking is enabled by (upstream) default.) At this point we (exim4) decided that this was a good time to finally drop the dlopen localscan patch. We did that and adopted exim accordingly: - improve the example/docs for content-scanning in exim without sa-exim - drop the abovementioned patch and the virtual Provides for exim4-localscanapi-2.0 and also drop the exim-dev package (only needed for sa-exim). Exim now also Conflicts with sa-exim. However, what I did *not* do was consult you before I did this. I am sorry for that. It is still possible to reinstate exim-dev and try to fix exim to make sa-exim work again. But imho only if sa-exim is fixed in the first place and is tested and found to be working with current exim. What are your thoughts on this? TIA, cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' signature.asc Description: PGP signature
Bug#926930: marked as done (joblib: FTBFS (test_nested_parallelism_limit does not always work))
Your message dated Fri, 12 Apr 2019 17:18:39 +
with message-id
and subject line Bug#926930: fixed in joblib 0.13.0-2
has caused the Debian Bug report #926930,
regarding joblib: FTBFS (test_nested_parallelism_limit does not always work)
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.)
--
926930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:joblib
Version: 0.13.0-1
Severity: serious
Tags: ftbfs patch
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --buildsystem=python_distutils --with=python2,python3
dh_update_autotools_config -i -O--buildsystem=python_distutils
dh_auto_configure -i -O--buildsystem=python_distutils
dh_auto_configure: Please use the third-party "pybuild" build system instead of
python-distutils
dh_auto_configure: This feature will be removed in compat 12.
dh_auto_build -i -O--buildsystem=python_distutils
dh_auto_build: Please use the third-party "pybuild" build system instead of
python-distutils
dh_auto_build: This feature will be removed in compat 12.
python setup.py build --force
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.7
[... snipped ...]
joblib/test/test_testing.py::test_check_subprocess_call PASSED
joblib/test/test_testing.py::test_check_subprocess_call_non_matching_regex
PASSED
joblib/test/test_testing.py::test_check_subprocess_call_wrong_command PASSED
joblib/test/test_testing.py::test_check_subprocess_call_non_zero_return_code
PASSED
joblib/test/test_testing.py::test_check_subprocess_call_timeout
/<>/joblib/testing.py:50: UserWarning: Timeout running
['/usr/bin/python2.7', '-c', 'import time\nimport sys\nprint("before sleep on
stdout")\nsys.stdout.flush()\nsys.stderr.write("before sleep on
stderr")\nsys.stderr.flush()\ntime.sleep(1.1)\nprint("process should have be
killed before")\nsys.stdout.flush()']
warnings.warn("Timeout running {}".format(cmd))
PASSED
joblib/test/data/create_numpy_pickle.py::joblib.test.data.create_numpy_pickle.get_joblib_version
PASSED
=== FAILURES ===
_ test_nested_parallelism_limit[loky] __
backend = 'loky'
@with_multiprocessing
@parametrize('backend', ['loky', 'threading'])
def test_nested_parallelism_limit(backend):
with parallel_backend(backend, n_jobs=2):
backend_types_and_levels = _recursive_backend_info()
if cpu_count() == 1:
second_level_backend_type = 'SequentialBackend'
max_level = 1
else:
second_level_backend_type = 'ThreadingBackend'
max_level = 2
top_level_backend_type = backend.title() + 'Backend'
expected_types_and_levels = [
(top_level_backend_type, 0),
(second_level_backend_type, 1),
('SequentialBackend', max_level),
('SequentialBackend', max_level)
]
> assert backend_types_and_levels == expected_types_and_levels
E AssertionError: assert [('LokyBacken...lBackend', 2)] ==
[('LokyBackend...lBackend', 1)]
E At index 1 diff: ('ThreadingBackend', 1) != ('SequentialBackend', 1)
E Full diff:
E [('LokyBackend', 0),
E - ('ThreadingBackend', 1),
E - ('SequentialBackend', 2),
E ?^
E + ('SequentialBackend', 1),...
E
E ...Full output truncated (7 lines hidden), use '-vv' to show
joblib/test/test_parallel.py:1452: AssertionError
___ test_nested_parallelism_limit[threading] ___
backend = 'threading'
@with_multiprocessing
@parametrize('backend', ['loky', 'threading'])
def test_nested_parallelism_limit(backend):
with parallel_backend(backend, n_jobs=2):
backend_types_and_levels = _recursive_backend_info()
if cpu_count() == 1:
second_level_backend_type = 'SequentialBackend'
max_level = 1
else:
second_level_backend_type = 'ThreadingBackend'
max_level = 2
top_level_backend_type = backend.title() + 'Backend'
expected_types_and_levels = [
(top_level_backend_type, 0),
(second_level_backend_type, 1),
('SequentialBackend', max_level),
('SequentialBackend', max_lev
Bug#926946: marked as done (tracker-miner-fs SIGSEGV in process_func_start())
Your message dated Fri, 12 Apr 2019 15:49:38 + with message-id and subject line Bug#926946: fixed in tracker 2.1.8-2 has caused the Debian Bug report #926946, regarding tracker-miner-fs SIGSEGV in process_func_start() 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.) -- 926946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926946 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:tracker Version: 2.1.8-1 Severity: serious Tags: patch upstream fixed-upstream Hi, Just filing so I have a bug reference for the unblock. In Ubuntu's error tracker we noticed reports of a crash in tracker-miner that looks like this: #0 0x7f1a2c1db676 in process_func_start (crawler=0x0) at tracker-crawler.c:713 No locals. #1 0x7f1a2c1db9d0 in enumerate_next_cb (object=, result=, user_data=0x7f19ec0886f0) at tracker-crawler.c:930 dpd = 0x7f19ec0886f0 info = error = 0x0 #2 0x7f1a2c030df6 in next_async_callback_wrapper (source_object=0x55d54803ccd0, res=0x55d547f2e1b0, user_data=0x7f19ec0886f0) at ../../../gio/gfileenumerator.c:305 enumerator = 0x55d54803ccd0 #3 0x7f1a2c070059 in g_task_return_now (task=0x55d547f2e1b0) at ../../../gio/gtask.c:1209 No locals. #4 0x7f1a2c070099 in complete_in_idle_cb (task=0x55d547f2e1b0) at ../../../gio/gtask.c:1223 No locals. #5 0x7f1a2be98958 in ?? () No symbol table info available. #6 0x7ffecede7820 in ?? () No symbol table info available. #7 0x7f1a in ?? () No symbol table info available. #8 0x in ?? () No symbol table info available. Andrea Azzarone from the Canonical team fixed this upstream[0]. I'm proposing to include the fix in buster, and I'm uploading to unstable now to hopefully achieve this. These are automated reports and I don't have steps to reproduce I'm afraid. You can see from frame #0 that process_func_start() is passed NULL. The fix avoids calling this if the operation has been cancelled, in which case data_provider_end() will be called, which frees the data. That's how we get NULL there. Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] [0] https://gitlab.gnome.org/GNOME/tracker/merge_requests/86 --- End Message --- --- Begin Message --- Source: tracker Source-Version: 2.1.8-2 We believe that the bug you reported is fixed in the latest version of tracker, 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 926...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Iain Lane (supplier of updated tracker 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: Fri, 12 Apr 2019 16:20:46 +0100 Source: tracker Architecture: source Version: 2.1.8-2 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Iain Lane Closes: 926946 Changes: tracker (2.1.8-2) unstable; urgency=medium . * gbp.conf: Update debian-branch for buster * Cherry-pick upstream patch to fix crash (Closes: #926946) Checksums-Sha1: 2ecbbfdd792b3be1931152cf0aed36d19e8fe4b7 3295 tracker_2.1.8-2.dsc 17604f76cc0ee74e544fb2181456747a2515dd0b 24664 tracker_2.1.8-2.debian.tar.xz c90a1eb66f9255b3127b072b36232312f45400ad 15107 tracker_2.1.8-2_source.buildinfo Checksums-Sha256: 0c093610d2eff51686e9046bb4a74947d6d8c92fad5c25acae23887ee062d24f 3295 tracker_2.1.8-2.dsc 119321912afc7bac0dbfc1d553a844f928f82e460b30e2ab97c9edd1f42a3bee 24664 tracker_2.1.8-2.debian.tar.xz 22990c2eae049190359a3b591daef60f3fcb0b967a261dea46262969ac01eeac 15107 tracker_2.1.8-2_source.buildinfo Files: 9e55f9fe54bebb877b445d0832fbcf9d 3295 utils optional tracker_2.1.8-2.dsc 0b816c54dd20446ee29f022d01bb070a 24664 utils optional tracker_2.1.8-2.debian.tar.xz 1a3875a1b6c36d7bf29b6daeb0ec453f 15107 utils optional tracker_2.1.8-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEPQ77lee1I38W6CJY41LVxRxQQdQFAlywsDoACgkQ41LVxRxQ QdQoGg//bHKNbeBHAbdqym6vCY51d2SZ1Gv1qiZ4j1sAI3ya1qBleFavu3q98Ip6 eip
Bug#926946: tracker-miner-fs SIGSEGV in process_func_start()
Package: src:tracker Version: 2.1.8-1 Severity: serious Tags: patch upstream fixed-upstream Hi, Just filing so I have a bug reference for the unblock. In Ubuntu's error tracker we noticed reports of a crash in tracker-miner that looks like this: #0 0x7f1a2c1db676 in process_func_start (crawler=0x0) at tracker-crawler.c:713 No locals. #1 0x7f1a2c1db9d0 in enumerate_next_cb (object=, result=, user_data=0x7f19ec0886f0) at tracker-crawler.c:930 dpd = 0x7f19ec0886f0 info = error = 0x0 #2 0x7f1a2c030df6 in next_async_callback_wrapper (source_object=0x55d54803ccd0, res=0x55d547f2e1b0, user_data=0x7f19ec0886f0) at ../../../gio/gfileenumerator.c:305 enumerator = 0x55d54803ccd0 #3 0x7f1a2c070059 in g_task_return_now (task=0x55d547f2e1b0) at ../../../gio/gtask.c:1209 No locals. #4 0x7f1a2c070099 in complete_in_idle_cb (task=0x55d547f2e1b0) at ../../../gio/gtask.c:1223 No locals. #5 0x7f1a2be98958 in ?? () No symbol table info available. #6 0x7ffecede7820 in ?? () No symbol table info available. #7 0x7f1a in ?? () No symbol table info available. #8 0x in ?? () No symbol table info available. Andrea Azzarone from the Canonical team fixed this upstream[0]. I'm proposing to include the fix in buster, and I'm uploading to unstable now to hopefully achieve this. These are automated reports and I don't have steps to reproduce I'm afraid. You can see from frame #0 that process_func_start() is passed NULL. The fix avoids calling this if the operation has been cancelled, in which case data_provider_end() will be called, which frees the data. That's how we get NULL there. Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] [0] https://gitlab.gnome.org/GNOME/tracker/merge_requests/86
Bug#926930: joblib: FTBFS (test_nested_parallelism_limit does not always work)
TL;DR summary:
interesting... in my case reliably fails locally on python 3.6 and 3.7 but not
2.7 even with fresh release of 0.13.0
reported upstream https://github.com/joblib/joblib/issues/870
Thanks for the patch -- I will xfail it in 0.13.0-1 with this, upload to
unstable, and then upload 0.13.2-1 with it to experimental
Some notes collected:
1. I think it is the same issue as
https://github.com/joblib/joblib/issues/758 which was addressed upstream in
commit f58e833df6802bbc2120a9eb2c608a8c35dbc099
Author: Olivier Grisel
Date: Mon Aug 27 11:34:30 2018 +0200
Fix a bug in nesting level computation with
FallbackToBackend(SequentialBackend()) (#759)
which is
$> git describe --contains f58e833df6802bbc2120a9eb2c608a8c35dbc099
0.12.3~5
so might have been regression in
Version: 0.13.0-1
where (on upstream)
taskset -c 0 python -m pytest -v -k test_nested_parallelism_limit
passes just ok, so probably not a straight regression.
2. Could trigger "reliably" for the second (python 3.7) test run while
passing for 2.7
with change
$> git diff
diff --git a/debian/rules b/debian/rules
index 0ede50a..dd4d8ef 100755
--- a/debian/rules
+++ b/debian/rules
@@ -22,7 +22,7 @@ override_dh_auto_test: ${PYVERS:%=python-test%}
${PY3VERS:%=python-test%}
python-test%:
ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
- PYTHONPATH=$(CURDIR) python$* /usr/bin/py.test -s -v joblib;
+ PYTHONPATH=$(CURDIR) python$* /usr/bin/py.test -s -v -k
test_nested_parallelism_limit joblib;
else
: # Skip unittests due to nocheck
endif
and running
taskset -c 0 fakeroot debian/rules binary
> Note: I've checked and this failure may be reproduced easily on any
> system by doing "taskset -c 0 dpkg-buildpackage", but if for whatever
> reason you need a single-CPU system to test, please contact me
> privately and I will gladly provide one.
> Thanks.
> --- a/joblib/test/test_parallel.py
> +++ b/joblib/test/test_parallel.py
> @@ -1429,6 +1429,7 @@ def _recursive_backend_info(limit=3, **kwargs):
> return this_level + results[0]
> +@pytest.mark.xfail
> @with_multiprocessing
> @parametrize('backend', ['loky', 'threading'])
> def test_nested_parallelism_limit(backend):
Cheers,
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
Bug#865967: backport to stretch
Is it possible to back port this fix to debian stretch, stretch backports? As far as I can tell, this package simply won't work in Debian Stretch if you are using the postgres backend (maybe it works with other backends, not entirely sure). Thanks for your work packaging it! jamie signature.asc Description: OpenPGP digital signature
Bug#926932: libdbd-mysql-perl: FTBFS (autobuilder hangs)
severity 926932 important thanks Sorry, didn't spot the out of memory message. I'm making this not RC for now. I'd like to investigate this a little bit more on my side. Thanks a lot.
Processed: Re: Bug#926932: libdbd-mysql-perl: FTBFS (autobuilder hangs)
Processing commands for cont...@bugs.debian.org: > severity 926932 important Bug #926932 [src:libdbd-mysql-perl] libdbd-mysql-perl: FTBFS (autobuilder hangs) Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 926932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#926932: libdbd-mysql-perl: FTBFS (autobuilder hangs)
On Fri, 12 Apr 2019 11:51:53 +, Santiago Vila wrote: > I tried to build this package in buster but it failed: > Out of memory! > Out of memory! > # Looks like your test exited with 1 just after 25. > t/40server_prepare.t > 1..31 > ok 1 - connecting > ok 2 - making slate clean > ok 3 - creating table > ok 4 - loading data > ok 5 > ok 6 > ok 7 - binding parameter > ok 8 - fetching data > ok 9 > ok 10 > ok 11 - cleaning up > ok 12 - making slate clean > ok 13 - creating test table > ok 14 > ok 15 - binding int > ok 16 - binding smallint > ok 17 - binding tinyint > ok 18 - binding bigint > ok 19 - inserting data > ok 20 > ok 21 - cleaning up > ok 22 - making slate clean > ok 23 - creating test table > ok 24 > ok 25 - insert t3 > Dubious, test returned 1 (wstat 256, 0x100) > Failed 6/31 subtests > Out of memory! > Out of memory! > # Looks like your test exited with 1 just after 16. > t/40server_prepare_crash.t .. > 1..39 > ok 1 > ok 2 > ok 3 > ok 4 > ok 5 > ok 6 > ok 7 > ok 8 > ok 9 > ok 10 > ok 11 > ok 12 > ok 13 > ok 14 > ok 15 > ok 16 > Dubious, test returned 1 (wstat 256, 0x100) > Failed 23/39 subtests > Out of memory! > Out of memory! > # Tests were run but no plan was declared and done_testing() was not seen. > # Looks like your test exited with 1 just after 106. > t/50chopblanks.t > ok 1 - drop table if exists dbd_mysql_t50chopblanks > ok 2 - create table dbd_mysql_t50chopblanks > ok 3 > ok 4 > ok 5 - insert into dbd_mysql_t50chopblanks values (1 , '', '', '', '', '', > '', '', '', '') > ok 6 - select c_varchar, c_text, c_tinytext, c_mediumtext, c_longtext, > b_blob, b_tinyblob, b_mediumblob, b_longblob from dbd_mysql_t50chopblanks > where id = 1 > ok 7 > ok 8 - NoChopBlanks: c_varchar should not have blanks chopped > ok 9 - NoChopBlanks: c_text should not have blanks chopped > ok 10 - NoChopBlanks: c_tinytext should not have blanks chopped > ok 11 - NoChopBlanks: c_mediumtext should not have blanks chopped > ok 12 - NoChopBlanks: c_longtext should not have blanks chopped > ok 13 - NoChopBlanks: b_blob should not have blanks chopped > ok 14 - NoChopBlanks: b_tinyblob should not have blanks chopped > ok 15 - NoChopBlanks: b_mediumblob should not have blanks chopped > ok 16 - NoChopBlanks: b_longblob should not have blanks chopped > ok 17 > ok 18 > ok 19 - ChopBlanks: c_varchar should have blanks chopped > ok 20 - ChopBlanks: c_text should have blanks chopped > ok 21 - ChopBlanks: c_tinytext should have blanks chopped > ok 22 - ChopBlanks: c_mediumtext should have blanks chopped > ok 23 - ChopBlanks: c_longtext should have blanks chopped > ok 24 - ChopBlanks: b_blob should not have blanks chopped > ok 25 - ChopBlanks: b_tinyblob should not have blanks chopped > ok 26 - ChopBlanks: b_mediumblob should not have blanks chopped > ok 27 - ChopBlanks: b_longblob should not have blanks chopped > ok 28 - insert into dbd_mysql_t50chopblanks values (2 , ' ', ' ', ' ', ' ', ' > ', ' ', ' ', ' ', ' ') > ok 29 - select c_varchar, c_text, c_tinytext, c_mediumtext, c_longtext, > b_blob, b_tinyblob, b_mediumblob, b_longblob from dbd_mysql_t50chopblanks > where id = 2 > ok 30 > ok 31 - NoChopBlanks: c_varchar should not have blanks chopped > ok 32 - NoChopBlanks: c_text should not have blanks chopped > ok 33 - NoChopBlanks: c_tinytext should not have blanks chopped > ok 34 - NoChopBlanks: c_mediumtext should not have blanks chopped > ok 35 - NoChopBlanks: c_longtext should not have blanks chopped > ok 36 - NoChopBlanks: b_blob should not have blanks chopped > ok 37 - NoChopBlanks: b_tinyblob should not have blanks chopped > ok 38 - NoChopBlanks: b_mediumblob should not have blanks chopped > ok 39 - NoChopBlanks: b_longblob should not have blanks chopped > ok 40 > ok 41 > ok 42 - ChopBlanks: c_varchar should have blanks chopped > ok 43 - ChopBlanks: c_text should have blanks chopped > ok 44 - ChopBlanks: c_tinytext should have blanks chopped > ok 45 - ChopBlanks: c_mediumtext should have blanks chopped > ok 46 - ChopBlanks: c_longtext should have blanks chopped > ok 47 - ChopBlanks: b_blob should not have blanks chopped > ok 48 - ChopBlanks: b_tinyblob should not have blanks chopped > ok 49 - ChopBlanks: b_mediumblob should not have blanks chopped > ok 50 - ChopBlanks: b_longblob should not have blanks chopped > ok 51 - insert into dbd_mysql_t50chopblanks values (3 , ' a b c ', ' a b c ', > ' a b c ', ' a b c ', ' a b c ', ' a b c ', ' a b c ', ' a b c ', ' a b c ') > ok 52 - select c_varchar, c_text, c_tinytext, c_mediumtext, c_longtext, > b_blob, b_tinyblob, b_mediumblob, b_longblob from dbd_mysql_t50chopblanks > where id = 3 > ok 53 > ok 54 - NoChopBlanks: c_varchar should not have blanks chopped > ok 55 - NoChopBlanks: c_text should not have blanks chopped > ok 56 - NoChopBlanks: c_tinytext should not have blanks chopped > ok 57 - NoChopBlanks: c_mediumtext should not have blanks chopped > ok 58 - NoChopBlanks: c_longtext should not have bla
Bug#917203: marked as done (FTBFS on at least two architectures: test failure in the enigma algorithm)
Your message dated Fri, 12 Apr 2019 13:18:55 +
with message-id
and subject line Bug#917203: fixed in libmcrypt 2.5.8-3.4
has caused the Debian Bug report #917203,
regarding FTBFS on at least two architectures: test failure in the enigma
algorithm
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.)
--
917203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917203
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libmcrypt
Version: 2.5.8-3.3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi!
I've been doing a full rebuild of the Debian archive, building all
source packages targeting armel and armhf using arm64 hardware. We are
planning in future to move all of our 32-bit armel/armhf builds to
using arm64 machines, so this rebuild is to identify packages that
might have problems with this configuration.
While doing this, I found that libmcrypt failed its test suite for
armel running on arm64:
...
Algorithm: enigma... failed compatibility
Expected: f3edda7da20f8975884600f014d32c7a08e59d7b
Got: 216540d5d71ec2d57f626a5609a3ebedbb9b32e4
...
I've tested on amd64 and things look fine, but building for arm64 on
arm64 also fails with exactly the same test failure as armel-on-arm64.
Full log at
https://www.einval.com/debian/arm/rebuild-logs/armel/FAIL/libmcrypt_2.5.8-3.3_armel.log
-- System Information:
Debian Release: 9.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: libmcrypt
Source-Version: 2.5.8-3.4
We believe that the bug you reported is fixed in the latest version of
libmcrypt, 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 917...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Chris Lamb (supplier of updated libmcrypt 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: SHA256
Format: 1.8
Date: Sun, 07 Apr 2019 14:38:10 +0200
Source: libmcrypt
Binary: libmcrypt-dev libmcrypt4 libmcrypt4-dbgsym
Architecture: source amd64
Version: 2.5.8-3.4
Distribution: unstable
Urgency: medium
Maintainer: RISKO Gergely
Changed-By: Chris Lamb
Description:
libmcrypt-dev - De-/Encryption Library development files
libmcrypt4 - De-/Encryption Library
Closes: 917203
Changes:
libmcrypt (2.5.8-3.4) unstable; urgency=medium
.
* Non-maintainer upload.
* Fix FTBFS on at least two architectures due to test failures in the
"enigma". Thanks to Göran Weinholt (weinholt) for the patch.
(Closes: #917203)
* Update Vcs-{Git,Browser} to point to salsa.debian.org.
Checksums-Sha1:
b6bc0f928cab3462498424cf10009bbf83ca8852 1899 libmcrypt_2.5.8-3.4.dsc
9a426532e9087dd7737aabccff8b91abf9151a7a 1335178 libmcrypt_2.5.8.orig.tar.gz
44409303d0a745a1c8c90f472db0c5e8767646d3 5733 libmcrypt_2.5.8-3.4.diff.gz
f4a49b3a43bbe3600e38d5710237918166d9602e 94328
libmcrypt-dev_2.5.8-3.4_amd64.deb
6f423e61cceb23a1d12245ab00c03f5d4862882d 146452
libmcrypt4-dbgsym_2.5.8-3.4_amd64.deb
ec0666ad7ea2141c8c83550a5dd341527186a251 72864 libmcrypt4_2.5.8-3.4_amd64.deb
81c113ac929c3f5d3e6f163f05ff3eb299cec4ea 5828
libmcrypt_2.5.8-3.4_amd64.buildinfo
Checksums-Sha256:
d35b4c92600d1b7e58d6c76259df454babfea27ec3c28163a1bc078ecf675fdf 1899
libmcrypt_2.5.8-3.4.dsc
e4eb6c074bbab168ac47b947c195ff8cef9d51a211cdd18ca9c9ef34d27a373e 1335178
libmcrypt_2.5.8.orig.tar.gz
004599f4310cc46bdc9699096ff17df1620bfd00bbfaaa3034c04815e89798bc 5733
libmcrypt_2.5.8-3.4.diff.gz
dbe078addd1c2880f142976b85c826c71a1d315f15c3115835d7f180a3431e34 94328
libmcrypt-dev_2.5.8-3.4_amd64.deb
3764148089d1f07d94a81e6f406d311c2f3ddfcacc27444dea025022a089dc4e 146452
libmcrypt4-dbgsym_2.5.8-3.4_amd64.deb
6b4df7113028c4a9e0e378f615023861868555e3b0354d7dd9af7842c3392025 72864
libmcrypt4_2.5.8-3.4_amd64.deb
989baf49ba9
Bug#926935: arpack: FTBFS (does not honor parallel=n in DEB_BUILD_OPTIONS)
Package: src:arpack Version: 3.7.0-1 Severity: serious Tags: ftbfs patch Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch dh build-arch dh_update_autotools_config -a dh_autoreconf -a libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'. libtoolize: copying file 'build-aux/ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. libtoolize: copying file 'm4/libtool.m4' libtoolize: copying file 'm4/ltoptions.m4' libtoolize: copying file 'm4/ltsugar.m4' libtoolize: copying file 'm4/ltversion.m4' libtoolize: copying file 'm4/lt~obsolete.m4' configure.ac:12: installing 'build-aux/compile' configure.ac:17: installing 'build-aux/config.guess' [... snipped ...] make[4]: Leaving directory '/<>/PARPACK/SRC/MPI' Making check in . make[4]: Entering directory '/<>/PARPACK' make[4]: Nothing to be done for 'check-am'. make[4]: Leaving directory '/<>/PARPACK' Making check in TESTS/MPI make[4]: Entering directory '/<>/PARPACK/TESTS/MPI' make issue46 make[5]: Entering directory '/<>/PARPACK/TESTS/MPI' mpif77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -c -o issue46.o issue46.f /bin/bash ../../../libtool --tag=F77 --mode=link mpif77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wl,-z,relro -o issue46 issue46.o ../../../PARPACK/SRC/MPI/libparpack.la -llapack -lblas libtool: link: mpif77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wl,-z -Wl,relro -o .libs/issue46 issue46.o ../../../PARPACK/SRC/MPI/.libs/libparpack.so -llapack -lblas make[5]: Leaving directory '/<>/PARPACK/TESTS/MPI' make check-TESTS make[5]: Entering directory '/<>/PARPACK/TESTS/MPI' make[6]: Entering directory '/<>/PARPACK/TESTS/MPI' FAIL: issue46 Testsuite summary for ARPACK-NG 3.7.0 # TOTAL: 1 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See PARPACK/TESTS/MPI/test-suite.log Please report to https://github.com/opencollab/arpack-ng/issues/ make[6]: *** [Makefile:830: test-suite.log] Error 1 make[6]: Leaving directory '/<>/PARPACK/TESTS/MPI' make[5]: *** [Makefile:938: check-TESTS] Error 2 make[5]: Leaving directory '/<>/PARPACK/TESTS/MPI' make[4]: *** [Makefile:1026: check-am] Error 2 make[4]: Leaving directory '/<>/PARPACK/TESTS/MPI' make[3]: *** [Makefile:387: check-recursive] Error 1 make[3]: Leaving directory '/<>/PARPACK' make[2]: *** [Makefile:509: check-recursive] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:15: override_dh_auto_test] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:7: build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 This used to work ok in all my autobuilders in version 3.5.0+real-2, but it started to fail in some of them in version 3.6.3-1. I've put a bunch of build logs here: https://people.debian.org/~sanvila/build-logs/arpack/ The problem seems to be that the Makefiles wrongly assume that the system has at least 2 CPUs, which may or may not be the case. A simple solution that seems to work is to set 'LOG_FLAGS = -n 1' in both PARPACK/EXAMPLES/MPI/Makefile.am and PARPACK/TESTS/MPI/Makefile.am, but it would be even better to honor parallel=n setting in DEB_BUILD_OPTIONS when there is one, as in the patch below. I did not find a simple way to reproduce this in any system. The usual recipe is to try "taskset -c 0 dpkg-buildpackage" but this does not seem to work here, so if you need a test machine to reproduce the failure please contact me privately and I will gladly provide one. Thanks. --- a/PARPACK/EXAMPLES/MPI/Makefile.am +++ b/PARPACK/EXAMPLES/MPI/Makefile.am @@ -12,7 +12,7 @@ check_PROGRAMS = $(SNDRV) $(DNDRV) $(SSDRV) $(DSDRV) $(CNDRV) $(ZNDRV) # Run MPI tests with "mpirun -n 2" LOG_COMPILER = mpirun -LOG_FLAGS = -n 2 +LOG_FLAGS = -n $(NUMJOBS) TESTS = $(check_PROGRAMS) --- a/PARPACK/TESTS/MPI/Makefile.am +++ b/PARPACK/TESTS/MPI/Makefile.am @@ -3,7 +3,7 @@ LDADD = $(top_builddir)/PARPACK/SRC/MPI/libparpack$(LIBSUFFIX).la $(LAPACK_LIBS) # Run MPI tests with "mpirun -n 2" LOG_COMPILER = mpirun -LOG_FLAGS = -n 2 +LOG_FLAGS = -n $(NUMJOBS) SISS = issue46 --- a/debian/rules +++ b/debian/rules @@ -6,6 +6,12 @@ %: dh $@ +export NUMJOBS = $(shell nproc) + +ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) + NUMJOBS = $(patsubst parallel=%,%,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) +endif + override_dh_auto_configure: # Enforce generic BLAS (to avoid tying to ATLAS
Bug#926932: libdbd-mysql-perl: FTBFS (autobuilder hangs)
Package: src:libdbd-mysql-perl
Version: 4.050-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch --with perl_dbi
dh_update_autotools_config -a
dh_autoreconf -a
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
LC_ALL=C.UTF-8 dh_auto_configure
perl Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2"
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro
-Wl,-z,now"
PLEASE NOTE:
For 'make test' to run properly, you must ensure that the
database user 'buildd' can connect to your MySQL server
and has the proper privileges that these tests require such
as 'drop table', 'create table', 'drop procedure', 'create procedure'
as well as others.
mysql> grant all privileges on test.* to 'buildd'@'localhost' identified by
's3kr1t';
You can also optionally set the user to run 'make test' with:
perl Makefile.PL --testuser=username
mysql_config: unrecognized option '--embedded'
I will use the following settings for compiling and testing:
cflags(mysql_config) = -I/usr/include/mariadb
-I/usr/include/mariadb/mysql
embedded (guessed ) =
ldflags (guessed ) =
libs (mysql_config) = -L/usr/lib/x86_64-linux-gnu/ -lmariadb -lz
-ldl -lm -lpthread -lgnutls
mysql_config (guessed ) = mysql_config
nocatchstderr (default ) = 0
nofoundrows (default ) = 0
nossl (default ) = 0
testdb(default ) = test
testhost (default ) =
testpassword (default ) =
testport (default ) =
testsocket(default ) =
testuser (guessed ) = buildd
To change these settings, see 'perl Makefile.PL --help' and
'perldoc DBD::mysql::INSTALL'.
Checking if libs are available for compiling...
Looks good.
Checking if your kit is complete...
Looks good
Using DBI 1.642 (for perl 5.028001 on x86_64-linux-gnu-thread-multi) installed
in /usr/lib/x86_64-linux-gnu/perl5/5.28/auto/DBI/
Generating a Unix-style Makefile
Writing Makefile for DBD::mysql
Writing MYMETA.yml and MYMETA.json
make[1]: Leaving directory '/<>'
dh_auto_build -a
make -j1
make[1]: Entering directory '/<>'
cp lib/DBD/mysql/GetInfo.pm blib/lib/DBD/mysql/GetInfo.pm
cp lib/DBD/mysql.pm blib/lib/DBD/mysql.pm
cp lib/DBD/mysql/INSTALL.pod blib/lib/DBD/mysql/INSTALL.pod
cp lib/Bundle/DBD/mysql.pm blib/lib/Bundle/DBD/mysql.pm
Running Mkbootstrap for mysql ()
chmod 644 "mysql.bs"
"/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- mysql.bs
blib/arch/auto/DBD/mysql/mysql.bs 644
x86_64-linux-gnu-gcc -c -I/usr/lib/x86_64-linux-gnu/perl5/5.28/auto/DBI
-I/usr/include/mariadb -I/usr/include/mariadb/mysql -DDBD_MYSQL_WITH_SSL -g
-D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe
-I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DVERSION=\"4.050\"
-DXS_VERSION=\"4.050\" -fPIC "-I/usr/lib/x86_64-linux-gnu/perl/5.28/CORE"
dbdimp.c
In file included from /usr/lib/x86_64-linux-gnu/perl5/5.28/auto/DBI/DBIXS.h:38,
from dbdimp.h:20,
from dbdimp.c:15:
/usr/lib/x86_64-linux-gnu/perl5/5.28/auto/DBI/dbipport.h:4471: warning:
"WIDEST_UTYPE" redefined
# define WIDEST_UTYPE U64TYPE
In file included from /usr/lib/x86_64-linux-gnu/perl/5.28/CORE/perl.h:2465,
from /usr/lib/x86_64-linux-gnu/perl5/5.28/auto/DBI/DBIXS.h:23,
from dbdimp.h:20,
from dbdimp.c:15:
/usr/lib/x86_64-linux-gnu/perl/5.28/CORE/handy.h:1064: note: this is the
location of the previous definition
# define WIDEST_UTYPE U64
dbdimp.c: In function 'mysql_st_prepare':
dbdimp.c:3207:24: warning: assignment to 'my_bool *' {aka 'char *'} from
incompatible pointer type '_Bool *' [-Wincompatible-pointer-types]
bind->is_null= (_Bool*) &(fbind->is_null);
^
"/usr/bin/perl" -p -e "s/~DRIVER~/mysql/g"
/usr/lib/x86_64-linux-gnu/perl5/5.28/auto/DBI/Driver.xst > mysql.xsi
"/usr/bin/perl" "/usr/share/perl/5.28/ExtUtils/xsubpp" -typemap
'/usr/share/perl/5.28/ExtUtils/typemap' mysql.xs > mysql.xsc
Warning: duplicate function definition 'do' detected in mysql.xs, line 247
Warning: duplicate function definition 'rows' detected in mysql.xs, line 683
mv mysql.xsc mysql.c
x86_64-linux-gnu-gcc -c -I/usr/lib/x86_64-linux-gnu/perl5/5.28/auto/DBI
-I/usr/include/mariadb -I/usr/include/mariadb/mysql -DDBD_MYSQL_WITH_SSL -g
-D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe
-I/usr/local/include -D_LARG
Processed: retitle 924392 to fakemachine: execution fails due to missing shared lib
Processing commands for cont...@bugs.debian.org:
> retitle 924392 fakemachine: execution fails due to missing shared lib
Bug #924392 {Done: Héctor Orón Martínez } [fakemachine]
debos: fakemachine execution fails due to missing shared lib
Changed Bug title to 'fakemachine: execution fails due to missing shared lib'
from 'debos: fakemachine execution fails due to missing shared lib'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
924392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924392
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#926930: joblib: FTBFS (test_nested_parallelism_limit does not always work)
Package: src:joblib
Version: 0.13.0-1
Severity: serious
Tags: ftbfs patch
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --buildsystem=python_distutils --with=python2,python3
dh_update_autotools_config -i -O--buildsystem=python_distutils
dh_auto_configure -i -O--buildsystem=python_distutils
dh_auto_configure: Please use the third-party "pybuild" build system instead of
python-distutils
dh_auto_configure: This feature will be removed in compat 12.
dh_auto_build -i -O--buildsystem=python_distutils
dh_auto_build: Please use the third-party "pybuild" build system instead of
python-distutils
dh_auto_build: This feature will be removed in compat 12.
python setup.py build --force
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.7
[... snipped ...]
joblib/test/test_testing.py::test_check_subprocess_call PASSED
joblib/test/test_testing.py::test_check_subprocess_call_non_matching_regex
PASSED
joblib/test/test_testing.py::test_check_subprocess_call_wrong_command PASSED
joblib/test/test_testing.py::test_check_subprocess_call_non_zero_return_code
PASSED
joblib/test/test_testing.py::test_check_subprocess_call_timeout
/<>/joblib/testing.py:50: UserWarning: Timeout running
['/usr/bin/python2.7', '-c', 'import time\nimport sys\nprint("before sleep on
stdout")\nsys.stdout.flush()\nsys.stderr.write("before sleep on
stderr")\nsys.stderr.flush()\ntime.sleep(1.1)\nprint("process should have be
killed before")\nsys.stdout.flush()']
warnings.warn("Timeout running {}".format(cmd))
PASSED
joblib/test/data/create_numpy_pickle.py::joblib.test.data.create_numpy_pickle.get_joblib_version
PASSED
=== FAILURES ===
_ test_nested_parallelism_limit[loky] __
backend = 'loky'
@with_multiprocessing
@parametrize('backend', ['loky', 'threading'])
def test_nested_parallelism_limit(backend):
with parallel_backend(backend, n_jobs=2):
backend_types_and_levels = _recursive_backend_info()
if cpu_count() == 1:
second_level_backend_type = 'SequentialBackend'
max_level = 1
else:
second_level_backend_type = 'ThreadingBackend'
max_level = 2
top_level_backend_type = backend.title() + 'Backend'
expected_types_and_levels = [
(top_level_backend_type, 0),
(second_level_backend_type, 1),
('SequentialBackend', max_level),
('SequentialBackend', max_level)
]
> assert backend_types_and_levels == expected_types_and_levels
E AssertionError: assert [('LokyBacken...lBackend', 2)] ==
[('LokyBackend...lBackend', 1)]
E At index 1 diff: ('ThreadingBackend', 1) != ('SequentialBackend', 1)
E Full diff:
E [('LokyBackend', 0),
E - ('ThreadingBackend', 1),
E - ('SequentialBackend', 2),
E ?^
E + ('SequentialBackend', 1),...
E
E ...Full output truncated (7 lines hidden), use '-vv' to show
joblib/test/test_parallel.py:1452: AssertionError
___ test_nested_parallelism_limit[threading] ___
backend = 'threading'
@with_multiprocessing
@parametrize('backend', ['loky', 'threading'])
def test_nested_parallelism_limit(backend):
with parallel_backend(backend, n_jobs=2):
backend_types_and_levels = _recursive_backend_info()
if cpu_count() == 1:
second_level_backend_type = 'SequentialBackend'
max_level = 1
else:
second_level_backend_type = 'ThreadingBackend'
max_level = 2
top_level_backend_type = backend.title() + 'Backend'
expected_types_and_levels = [
(top_level_backend_type, 0),
(second_level_backend_type, 1),
('SequentialBackend', max_level),
('SequentialBackend', max_level)
]
> assert backend_types_and_levels == expected_types_and_levels
E AssertionError: assert [('ThreadingB...lBackend', 2)] ==
[('ThreadingBa...lBackend', 1)]
E At index 1 diff: ('ThreadingBackend', 1) != ('SequentialBackend', 1)
E Full diff:
E [('ThreadingBackend', 0),
E - ('ThreadingBackend', 1),
E - ('SequentialBackend', 2),
E ?^
E + ('SequentialBackend', 1),...
E
E ...Full output truncated (7 lines hidden), use '-vv' to show
joblib/test/test_parallel.py:1452: AssertionError
== 2 failed, 1099 passed, 19 skipped in 70.93 seconds ==
[INFO:MainProcess:Dummy-463] process shutting down
[DEBUG:MainProcess:Dummy-463] running all "atexit" finalizers with priority >= 0
[DEBUG:MainP
Bug#926928: fetchmail: Server CommonName mismatch
Package: fetchmail Version: 6.4.0~beta4-3 Severity: grave Justification: renders package unusable Dear Maintainer, I use ferchmail for a while and I have seen in syslog that fetchmail returns errors: fetchmail: Loaded OpenSSL library 0x1010102f newer than headers 0x1010101f, trying to continue. fetchmail: SSL verify callback depth 0: preverify_ok == 0, err = 62, Hostname mismatch fetchmail: Server certificate: fetchmail: Issuer Organization: DigiCert Inc fetchmail: Issuer CommonName: RapidSSL RSA CA 2018 fetchmail: Subject CommonName: *.nerim.net fetchmail: Subject Alternative Name: *.nerim.net fetchmail: Subject Alternative Name: nerim.net fetchmail: Server CommonName mismatch: *.nerim.net != pop.nerim.fr fetchmail: pop.nerim.fr key fingerprint: D8:9B:28:28:4C:DF:07:5E:BC:87:6C:11:7C:A1:8E:BE fetchmail: Server certificate verification error: Hostname mismatch fetchmail: OpenSSL reported: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed fetchmail: pop.nerim.fr: upgrade to TLS failed. and, of course, fetchmail stops transaction. I haven't find a solution to fix this issue. Best regards, JB -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fetchmail depends on: ii adduser 3.118 ii debianutils 4.8.6.1 ii libc6 2.28-8 ii libcom-err2 1.44.5-1 ii libgssapi-krb5-2 1.17-2 ii libk5crypto3 1.17-2 ii libkrb5-3 1.17-2 ii libssl1.1 1.1.1b-1 ii lsb-base 10.2019031300 Versions of packages fetchmail recommends: ii ca-certificates 20190110 Versions of packages fetchmail suggests: pn fetchmailconf pn resolvconf ii sendmail-bin [mail-transport-agent] 8.15.2-12 -- Configuration Files: /etc/default/fetchmail [Errno 13] Permission non accordée: '/etc/default/fetchmail' /etc/init.d/fetchmail changed [not included] -- no debconf information
Bug#924392: marked as done (debos: fakemachine execution fails due to missing shared lib)
Your message dated Fri, 12 Apr 2019 10:18:37 + with message-id and subject line Bug#924392: fixed in golang-github-go-debos-fakemachine 0.0~git20181105.9316584-2 has caused the Debian Bug report #924392, regarding debos: fakemachine execution fails due to missing shared lib 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.) -- 924392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debos Version: 1.0.0+git20190123.d6e16be-1 Severity: important Dear maintainers, busybox has been updated in buster and now needs libresolv.so.2, which is not included in fakemachine's initramfs. When executing debos, it returns with the following error message: > open /tmp/fakemachine-x/result: no such file or directory This has been fixed upstream (https://github.com/go- debos/fakemachine/commit/f014deb1e83ca6b47f0e244a06133206372b6846) but not yet in debian. As a workaround, installing busybox-static fixes the problem. Regards, Arnaud -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debos depends on: ii busybox-static [busybox] 1:1.30.1-2 ii debootstrap 1.0.114 ii libc6 2.28-8 ii libglib2.0-0 2.58.3-1 ii libostree-1-1 2019.1-1 ii qemu-system-x86 1:3.1+dfsg-4 ii qemu-user-static 1:3.1+dfsg-4 ii systemd-container 241-1 Versions of packages debos recommends: ii bmap-tools 3.5-2 ii bzip2 1.0.6-9 ii e2fsprogs 1.44.5-1 ii linux-image-amd64 4.19+102 ii mount 2.33.1-0.1 ii ovmf 0~20181115.85588389-2 ii parted 3.2-24 ii udev 241-1 ii xz-utils 5.2.4-1 ii zip3.0-11+b1 debos suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: golang-github-go-debos-fakemachine Source-Version: 0.0~git20181105.9316584-2 We believe that the bug you reported is fixed in the latest version of golang-github-go-debos-fakemachine, 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 924...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Héctor Orón Martínez (supplier of updated golang-github-go-debos-fakemachine 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: Fri, 12 Apr 2019 11:53:04 +0200 Source: golang-github-go-debos-fakemachine Architecture: source Version: 0.0~git20181105.9316584-2 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Héctor Orón Martínez Closes: 924392 Changes: golang-github-go-debos-fakemachine (0.0~git20181105.9316584-2) unstable; urgency=medium . * fakemachine: execution fails due to missing shared lib (Closes: #924392) Checksums-Sha1: 504b90b44842f67d10e10a5130abfefec879cf71 2652 golang-github-go-debos-fakemachine_0.0~git20181105.9316584-2.dsc a836b507ce0fc224a93c08058dcc32aa2ed4d108 4020 golang-github-go-debos-fakemachine_0.0~git20181105.9316584-2.debian.tar.xz b75c68fa480096613ca92fadb8863caf7ab669bb 6500 golang-github-go-debos-fakemachine_0.0~git20181105.9316584-2_source.buildinfo Checksums-Sha256: df997fb494a28563a22a6434e442a81754523a66caf307c6b1bb736b19de414d 2652 golang-github-go-debos-fakemachine_0.0~git20181105.9316584-2.dsc fd909cdbe0edf68998fbaec9d6a2e6d4d80252df709205ece51da92d99dbfb97 4020 golang-github-go-debos-fakemachine_0.0~git20181105.9316584-2.debian.tar.xz ceba9eba5c79701b26076e1edeb5e9d4b2677fbb3b54cd368403f82bd87f34d9 6500 golang-github-go-debos-fakemachine_0.0~git20181105.9316584-2_source.buildinfo Files: 44fbb340c5631208485b1e9dbb166b6a 2652 devel optional golang
Processed: reassign 924392 to fakemachine
Processing commands for cont...@bugs.debian.org: > reassign 924392 fakemachine Bug #924392 [debos] debos: fakemachine execution fails due to missing shared lib Bug reassigned from package 'debos' to 'fakemachine'. No longer marked as found in versions debos/1.0.0+git20190123.d6e16be-1. Ignoring request to alter fixed versions of bug #924392 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 924392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#926923: Acknowledgement (gradle: CVE-2019-11065)
control: severity -1 important thanks
Processed: Re: Bug#926923: Acknowledgement (gradle: CVE-2019-11065)
Processing control commands: > severity -1 important Bug #926923 [gradle] gradle: CVE-2019-11065 Severity set to 'important' from 'grave' -- 926923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#926923: gradle: CVE-2019-11065
Package: gradle Version: 4.4.1-5 X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for gradle. CVE-2019-11065[0]: | Gradle versions from 1.4 to 5.3.1 use an insecure HTTP URL to download | dependencies when the built-in JavaScript or CoffeeScript Gradle | plugins are used. Dependency artifacts could have been maliciously | compromised by a MITM attack against the ajax.googleapis.com web site. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-11065 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11065 https://github.com/gradle/gradle/pull/8927 Cheers! Sylvain Beucler
Processed: severity of 924392 is serious
Processing commands for cont...@bugs.debian.org: > severity 924392 serious Bug #924392 [debos] debos: fakemachine execution fails due to missing shared lib Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 924392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923749: Potential bug in jh_build (Was: fannj: FTBFS in buster/sid)
Hi, I'd like to make some noise again about this issue. I'm concerned about the fact that jh_build --javadoc-opts='-link /usr/share/doc/default-jdk-doc/api' was creating a JAR file until some point in time but it does not any more. Is this a bug in jh_build? Kind regards Andreas. On Thu, Apr 04, 2019 at 01:36:18PM +0200, Andreas Tille wrote: > Hi, > > On Tue, Apr 02, 2019 at 03:35:58PM +0200, Andreas Tille wrote: > > Daniel, if I do not hear from you I assume you agree that I inject > > fannj into Debian Science Git and do a team upload. > > As I said I assumed agreement and have moved fannj to Salsa[1]. > Unfortunately the build is not only failing for the docs when I try to > build it is just doing nothing in override_jh_build. > > I'd appreciate any helpful hint from the Java team to finalise > a fix for this package. > > Kind regards > >Andreas. > > [1] https://salsa.debian.org/science-team/fannj > > -- > http://fam-tille.de > > -- http://fam-tille.de
Bug#926917: openjdk-13-doc: ships usr/share/doc/openjdk-12-jre-headless/api/jquery/*
Package: openjdk-13-doc Version: 13~12-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files. Looks like a hardcoded package name/path somewhere ... >From the attached log (scroll to the bottom...): Preparing to unpack .../openjdk-13-doc_13~12-1_all.deb ... Unpacking openjdk-13-doc (13~12-1) ... dpkg: error processing archive /var/cache/apt/archives/openjdk-13-doc_13~12-1_all.deb (--unpack): trying to overwrite '/usr/share/doc/openjdk-12-jre-headless/api/jquery/external/jquery/jquery.js', which is also in package openjdk-12-doc 12.0.0-3 Errors were encountered while processing: /var/cache/apt/archives/openjdk-13-doc_13~12-1_all.deb This is the list of clashing files: usr/share/doc/openjdk-12-jre-headless/api/jquery/external/jquery/jquery.js usr/share/doc/openjdk-12-jre-headless/api/jquery/jquery-3.3.1.js usr/share/doc/openjdk-12-jre-headless/api/jquery/jquery-ui.css usr/share/doc/openjdk-12-jre-headless/api/jquery/jquery-ui.js usr/share/doc/openjdk-12-jre-headless/api/jquery/jquery-ui.min.css usr/share/doc/openjdk-12-jre-headless/api/jquery/jquery-ui.min.js cheers, Andreas openjdk-12-doc=12.0.0-3_openjdk-13-doc=13~12-1.log.gz Description: application/gzip
Bug#926916: python3-dotenv-cli: /usr/bin/dotenv is already provided by ruby-dotenv
Package: python3-dotenv-cli Version: 1.0.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: Architecture: amd64 Distribution: Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package python3-dotenv-cli. Preparing to unpack .../python3-dotenv-cli_1.0.0-1_all.deb ... Unpacking python3-dotenv-cli (1.0.0-1) ... dpkg: error processing archive /var/cache/apt/archives/python3-dotenv-cli_1.0.0-1_all.deb (--unpack): trying to overwrite '/usr/bin/dotenv', which is also in package ruby-dotenv 2.4.0-1 Errors were encountered while processing: /var/cache/apt/archives/python3-dotenv-cli_1.0.0-1_all.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/bin/dotenv cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html ruby-dotenv=2.4.0-1_python3-dotenv-cli=1.0.0-1.log.gz Description: application/gzip
