Bug#955740: kdenlive crash on startup - no longer crashing after machine reboot
Package: kdenlive Followup-For: Bug #955740 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? crashing on startup. * What exactly did you do (or not do) that was effective (or ineffective)? rebooted the machine. * What was the outcome of this action? kdenlive running as normal * What outcome did you expect instead? wasn't expecting this would solve the problem! *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kdenlive depends on: ii ffmpeg 7:4.2.2-1+b1 ii kded5 5.62.0-1+b1 ii kdenlive-data 19.12.3-1 ii kinit 5.62.0-1+b1 ii kio5.62.1-2+b1 ii libc6 2.30-4 ii libkf5archive5 5.62.0-1 ii libkf5bookmarks5 5.62.0-1+b1 ii libkf5completion5 5.62.0-1+b1 ii libkf5configcore5 5.62.0-1+b1 ii libkf5configgui5 5.62.0-1+b1 ii libkf5configwidgets5 5.62.0-1+b1 ii libkf5coreaddons5 5.62.0-1 ii libkf5crash5 5.62.0-1+b1 ii libkf5dbusaddons5 5.62.0-1 ii libkf5declarative5 5.62.0-1+b2 ii libkf5filemetadata35.62.0-1+b1 ii libkf5guiaddons5 5.62.0-2 ii libkf5i18n55.62.0-1 ii libkf5iconthemes5 5.62.0-1+b1 ii libkf5itemviews5 5.62.0-1+b1 ii libkf5jobwidgets5 5.62.0-1+b1 ii libkf5kiocore5 5.62.1-2+b1 ii libkf5kiofilewidgets5 5.62.1-2+b1 ii libkf5kiowidgets5 5.62.1-2+b1 ii libkf5newstuff55.62.0-1+b1 ii libkf5notifications5 5.62.0-1+b1 ii libkf5notifyconfig55.62.0-1+b1 ii libkf5purpose-bin 5.62.0-2+b1 ii libkf5purpose5 5.62.0-2+b1 ii libkf5service-bin 5.62.0-1 ii libkf5service5 5.62.0-1 ii libkf5solid5 5.62.0-2 ii libkf5widgetsaddons5 5.62.0-1+b1 ii libkf5xmlgui5 5.62.0-1+b1 ii libmlt++3 6.20.0-2+b1 ii libmlt66.20.0-2+b1 ii libqt5concurrent5 5.12.5+dfsg-9 ii libqt5core5a 5.12.5+dfsg-9 ii libqt5dbus55.12.5+dfsg-9 ii libqt5gui5 5.12.5+dfsg-9 ii libqt5multimedia5 5.12.5-1+b1 ii libqt5network5 5.12.5+dfsg-9 ii libqt5qml5 5.12.5-5 ii libqt5quick5 5.12.5-5 ii libqt5quickwidgets55.12.5-5 ii libqt5svg5 5.12.5-2 ii libqt5webkit5 5.212.0~alpha4-1 ii libqt5widgets5 5.12.5+dfsg-9 ii libqt5xml5 5.12.5+dfsg-9 ii librttr-core0.9.6 0.9.6+dfsg1-3 ii libstdc++6 10-20200324-1 ii melt 6.20.0-2+b1 ii qml-module-qtgraphicaleffects 5.12.5-2+b1 ii qml-module-qtqml-models2 5.12.5-5 ii qml-module-qtquick-controls5.12.5-1+b1 ii qml-module-qtquick-controls2 5.12.5+dfsg-2+b1 ii qml-module-qtquick-dialogs 5.12.5-1+b1 ii qml-module-qtquick-layouts 5.12.5-5 ii qml-module-qtquick-window2 5.12.5-5 ii qml-module-qtquick25.12.5-5 Versions of packages kdenlive recommends: ii breeze-icon-theme 4:5.62.0-1 pn dvdauthor pn dvgrab ii frei0r-plugins 1.7.0-1 pn genisoimage pn oxygen-icon-theme pn recordmydesktop ii swh-plugins0.4.17-2 Versions of packages kdenlive suggests: ii khelpcenter 4:18.04.0-1+b1 -- no debconf information
Bug#955777: marked as done (forensics-all: depends on neopi which was removed from unstable)
Your message dated Sun, 05 Apr 2020 04:03:27 + with message-id and subject line Bug#955777: fixed in forensics-all 3.18 has caused the Debian Bug report #955777, regarding forensics-all: depends on neopi which was removed from unstable 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.) -- 955777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955777 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: forensics-all Version: 3.17 Severity: serious Tags: sid bullseye neopi was removed from unstable (see #955518). Please drop it from forensics-all's Depends. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: forensics-all Source-Version: 3.18 Done: Joao Eriberto Mota Filho We believe that the bug you reported is fixed in the latest version of forensics-all, 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 955...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joao Eriberto Mota Filho (supplier of updated forensics-all 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: Sun, 05 Apr 2020 00:00:36 -0300 Source: forensics-all Architecture: source Version: 3.18 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Joao Eriberto Mota Filho Closes: 955777 Changes: forensics-all (3.18) unstable; urgency=medium . * list-of-packages: - Removed bbqsql and pyrit, no longer in Debian. - Removed neopi, no longer in Debian. Thanks to Sebastian Ramacher . (Closes: #955777) * debian/control: updated. * debian/forensics-all.README.Debian: updated. Checksums-Sha1: 22a1d38367f4f9ca19a4f11b0d3b22c4f1a7ccca 1854 forensics-all_3.18.dsc 14f945cffd6b4fcf87d26b33603319ce906d94b7 14204 forensics-all_3.18.tar.xz f04b04f4bf4cdd1a3890ee46b9d29d238ca05bdc 5233 forensics-all_3.18_source.buildinfo Checksums-Sha256: e87c4c991547aae7207b3c1d29df90757b81f6c02fe2c0b08a337e00fcb817b8 1854 forensics-all_3.18.dsc e2471d3a48053c543d4f7f061750464a4203455c5e2ffa754ee5d364dbc868b2 14204 forensics-all_3.18.tar.xz c1f6752f82c059a90706903d8489d50961717cfc8617b50014884f445e5fb4c6 5233 forensics-all_3.18_source.buildinfo Files: a225a6c6de95a532fc27f90d3bdb926e 1854 metapackages optional forensics-all_3.18.dsc 4374eaef31e1182e13cdb103235f4339 14204 metapackages optional forensics-all_3.18.tar.xz 06d4da3b02b41701ff10c9540868b72e 5233 metapackages optional forensics-all_3.18_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAl6JVHAACgkQ3mO5xwTr 6e99xBAAo7BNZqboVHdP+u2tshAvyn2CoclUiD6S2GK45/8dcaScJB0HXSA+uOsF KhV1Y7zFgR00QsbtqIVumAZI2tF7QcrRT5J7QC8if4bMSs9U1qRcQ9E1yayfEZof PlOHofRLliUGyPj0+dUKKJiZuAfCVs0fPOffYShauK36jkY7e7+J3txNk0ckXZ0H tLy/aT70rGXDG/VdeOeUNlDRiQcsW71XLVYefqm3EW9HWVW7m2aSwiVPHzTeCL/P x4k6xCuG34zTB4CZABwxIjrMTDrJwKjdKiw5KBFblY8LWh6O6/+s35o49Dh1Dj39 F2VLYCMdqC7IAs9eJL+gZ8mpCspZnb7A/BatyP3lPGNLEw1XyviIXPr43zxFOysi u1ESAFN1xzSQN9WlqNoAgVZIdeUqFlO+jWw33mlBtzgtLS9BuB8MxI7Bwo+oIt09 Dp6gur3bfs+n7YuNXfCQj9TIk+5BbvrzhHR53M+GZsRPjSuRnh/RgfEz1CVPQtKe lIZ0neN3wqUI7+snBrt1f6NwsXqV4ud/A4OW2GOdOAaofghO+P3logJujOi4EdIC usxZxWKDX+yjQpDqw2suOc4fubrl/upFw2fZVRxGOH6vkG1n2f9tWdFeby/mDYqP mLvGzZeys4TXG8Vl/0q2GUBXB1YrYK+y6lVbKFKMYDgWAscrVlc= =QgeX -END PGP SIGNATURE End Message ---
Processed: py2removal bugs severity updates - 2020-04-05 02:36:13.477928+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # and https://lists.debian.org/debian-python/2019/12/msg00076.html > # and https://lists.debian.org/debian-python/2020/03/msg00087.html > # mail threads for more details on this severity update > # python-iso8601 is a module and has 0 external rdeps or not in testing > severity 937847 serious Bug #937847 [src:python-iso8601] python-iso8601: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 937847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937847 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955636: marked as done (build dependency on python-doc)
Your message dated Sun, 05 Apr 2020 02:33:57 + with message-id and subject line Bug#955636: fixed in python-pykka 2.0.2-6 has caused the Debian Bug report #955636, regarding build dependency on python-doc 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.) -- 955636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955636 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-pykka Severity: serious Tags: sid bullseye patch User: debian-pyt...@lists.debian.org Usertags: py2removal the package still build-depends on python-doc, while it depends on python3 for everything else. patch at http://launchpadlibrarian.net/472673858/python-pykka_2.0.2-5_2.0.2-5ubuntu1.diff.gz --- End Message --- --- Begin Message --- Source: python-pykka Source-Version: 2.0.2-6 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of python-pykka, 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 955...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated python-pykka 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: Sat, 04 Apr 2020 21:59:01 -0400 Source: python-pykka Architecture: source Version: 2.0.2-6 Distribution: unstable Urgency: medium Maintainer: Stein Magnus Jodal Changed-By: Sandro Tosi Closes: 955636 Changes: python-pykka (2.0.2-6) unstable; urgency=medium . * Drop b-d-i on python-doc; Closes: #955636 Checksums-Sha1: 6b55a56abaad2d87ba14e3b258014dc16c6ccba4 2126 python-pykka_2.0.2-6.dsc c7134c8a757f8b4ab4f63a8eea5897791f616cba 4812 python-pykka_2.0.2-6.debian.tar.xz 60d5b7a473716e76481c9ad18cbdfa7b692843c2 9078 python-pykka_2.0.2-6_amd64.buildinfo Checksums-Sha256: b40623cce5c8639e137ba641346f50d4f801acb444660d94eb4443c3bd3f2e7e 2126 python-pykka_2.0.2-6.dsc 70c9bc059eadc28882e33c10d733c3014fbeee1bdfb5be42892a282699f53f79 4812 python-pykka_2.0.2-6.debian.tar.xz abfb8f5d4d935b8c944b3d51eb7d912b6c5d4f2d28341eccf573993978501062 9078 python-pykka_2.0.2-6_amd64.buildinfo Files: b97341ad724a8f702bd2b48870758d2d 2126 python optional python-pykka_2.0.2-6.dsc cdbc91800912b3fd776a2fff04c4b468 4812 python optional python-pykka_2.0.2-6.debian.tar.xz e61444d9d416fa4066b17ce140a68b08 9078 python optional python-pykka_2.0.2-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl6JO74ACgkQh588mTgB qU/SrRAAvqBuHFqafUGh/fJT8uKqbqCk05ZVa4lWblYEf7bCTHiUMdI6he0Gmjyj GBShUKr8oxDxUrOXD0j9X+vAMKMfVtSFVf8NsQRjtElSzOKq99gfl6zhjGmH8J1W pAGVrK+GETmupvMiKTxy8seo/ggOeFimHZctCPdrQXShUhcOTmtSMBbZe2zCBFWQ t0vB/Z5WsmfpGnBF8vgX4saO9tWfMjP82cHStzsFzKoOOTPPt5AN8rRF8hTm67Kh cLd3JDyBjoSAJiFq9vsiLYOOgn+pIPZkdBSuOIn44kxQjpYCl2ShZuIcNSEZw56x TSA9Rb+XUXMr/aio8Q+nTqsRYHlnaANHRytSC0VVTYgFAGfDeVxlXDzWuwidt6Tf TlXlCtKKrUeYJUYn2H6bIEyNEF6R+SUlE/+69wfK9qkGzcg1oCuRYUrNV5iHbQ7z VEQTIcnhQbuih4zI1uJdqeMiKifxJtxMUpnI9YtsXNK4WqbuZs111cKnJKZIFMbg LZBOeN99gANhgQtbTFmiwz4RO4xffJy5uiqO1XMKbi3Wc3+aDyrdH7xupUzXqNBe Jwi5N6DGeTFoAGrqBC4qKEMJtYD3UK2BVBd5NjJQMVgyZX4MHKfyzXvBgnuBaLh0 xC4VFNMsKNwdY93DDeNBBQ+aindyfxnoiO5IAc+4CQX9q9xpBrc= =Qsje -END PGP SIGNATURE End Message ---
Bug#955636: marked as pending in python-pykka
Control: tag -1 pending Hello, Bug #955636 in python-pykka reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/python-pykka/-/commit/c9fddef1e077d2a93c62f7f3cfaf8c969db9a97b Drop b-d-i on python-doc; Closes: #955636 (this message was generated automatically) -- Greetings https://bugs.debian.org/955636
Processed: Bug#955636 marked as pending in python-pykka
Processing control commands: > tag -1 pending Bug #955636 [python-pykka] build dependency on python-doc Added tag(s) pending. -- 955636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955636 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954520: marked as done (yiyantang: FTBFS: setty.c:31:10: fatal error: stropts.h: No such file or directory)
Your message dated Sun, 05 Apr 2020 00:49:32 + with message-id and subject line Bug#954520: fixed in yiyantang 0.7.0-6 has caused the Debian Bug report #954520, regarding yiyantang: FTBFS: setty.c:31:10: fatal error: stropts.h: No such file or directory 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.) -- 954520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954520 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yiyantang Version: 0.7.0-5 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200321 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely due to the upgrade to glibc 2.30. >From https://lists.gnu.org/archive/html/info-gnu/2019-08/msg0.html: > * The obsolete and never-implemented XSI STREAMS header files > and have been removed. Relevant part (hopefully): > gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include > -DG_LOG_DOMAIN=\"yyt\" -I../intl -I../intl -Wdate-time > -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -c setty.c > setty.c:31:10: fatal error: stropts.h: No such file or directory >31 | #include > | ^~~ > compilation terminated. > make[3]: *** [Makefile:201: setty.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/03/21/yiyantang_0.7.0-5_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 --- Source: yiyantang Source-Version: 0.7.0-6 Done: Sudip Mukherjee We believe that the bug you reported is fixed in the latest version of yiyantang, 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 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sudip Mukherjee (supplier of updated yiyantang 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: Sun, 05 Apr 2020 00:15:30 +0100 Source: yiyantang Architecture: source Version: 0.7.0-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Sudip Mukherjee Closes: 954520 Changes: yiyantang (0.7.0-6) unstable; urgency=medium . * QA upload. * Update Standards-Version to 4.5.0 * Fix FTBFS. (Closes: #954520) * Update compat level to 12. - Remove dependency on autotools_dev. - configure without using autoreconf. * Add version in d/watch. * Add Vcs link to salsa. Checksums-Sha1: 11c7c7a3b4bafbd043c9c0e1e79f6a61cd6f34a2 1814 yiyantang_0.7.0-6.dsc 34b268e48f6b4896f71b796353664120b6b6edf1 3696 yiyantang_0.7.0-6.debian.tar.xz bc28179fb6e9c2604ddc0e97e04c98e4287bd8f4 5806 yiyantang_0.7.0-6_amd64.buildinfo Checksums-Sha256: 6fb1ff431709e782dc77b9ef874724b8474330d95ddc5c27d013fd55bae19d6a 1814 yiyantang_0.7.0-6.dsc d16729ab03933f732742c1c09773265c875902cd6a5f029756aa548fc760f71f 3696 yiyantang_0.7.0-6.debian.tar.xz d912106e3c37a5548d1a7c8550b7848589b2530b2b948bd46ceb1bcf15ca 5806 yiyantang_0.7.0-6_amd64.buildinfo Files: 264d697b986b85e5ade72f2159b69fee 1814 text optional yiyantang_0.7.0-6.dsc fe55d15074d676b9b166a122fff99980 3696 text optional yiyantang_0.7.0-6.debian.tar.xz 083caac7a423d4d1bdd5382b9ad54fbd 5806 text optional yiyantang_0.7.0-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl6JJH0ACgkQwpPntGGC Ws6hNA//cbMGvspK2Ytp5lvydKfeMXsYjq2K4pCezHith+HsQnkb1JVT+SAdVx7D 5L6olTtW8fv3GwEfo3UDD02ag3jVcP55tZK4WERPI1k+INiskW+pruqzMu97tIiM VaiA4JtEF/36QarY8+ZaYEZ42/MK6VAU26x+8rDZXSZYr2NvaarsS+zb2zkvFkXm s4REkMPm9dwTuPDX2XdvTQSrwkmTd3Wmzzi1hQc6J3REcFTFpHkUMk2YOALCqfAE 9MipLCCfUIoHYmMlwmpTEfnNcDGQSNYM49bHegChiD3f6h9oQteTjHnaHiBLwaF2 nKK96Kmbvw5ctyvpLp7GMKcjn/w7YoQ62fSULHepkJjHN7xayIwqsoIErTyAc23E
Bug#953952: kmod: libkmod2-udeb contains binary instead of libraries
On Mar 15, Aurelien Jarno wrote: > The kmod binaries are actually the one being used, so yes please add a > kmod-udeb. Does it look good to you? https://salsa.debian.org/md/kmod/-/commit/801ce705d39efdae9411192b1c33aee8ad522cc7 drwxr-xr-x root/root 0 2020-04-05 02:14 ./ drwxr-xr-x root/root 0 2020-04-05 02:14 ./bin/ -rwxr-xr-x root/root121656 2020-04-05 02:14 ./bin/kmod drwxr-xr-x root/root 0 2020-04-05 02:14 ./etc/ drwxr-xr-x root/root 0 2020-04-05 02:14 ./etc/modprobe.d/ -rw-r--r-- root/root 246 2020-04-05 02:14 ./etc/modprobe.d/aliases.conf drwxr-xr-x root/root 0 2020-04-05 02:14 ./sbin/ lrwxrwxrwx root/root 0 2020-04-05 02:14 ./bin/lsmod -> kmod lrwxrwxrwx root/root 0 2020-04-05 02:14 ./sbin/depmod -> /bin/kmod lrwxrwxrwx root/root 0 2020-04-05 02:14 ./sbin/insmod -> /bin/kmod lrwxrwxrwx root/root 0 2020-04-05 02:14 ./sbin/lsmod -> /bin/kmod lrwxrwxrwx root/root 0 2020-04-05 02:14 ./sbin/modinfo -> /bin/kmod lrwxrwxrwx root/root 0 2020-04-05 02:14 ./sbin/modprobe -> /bin/kmod lrwxrwxrwx root/root 0 2020-04-05 02:14 ./sbin/rmmod -> /bin/kmod drwxr-xr-x root/root 0 2020-04-05 02:14 ./ drwxr-xr-x root/root 0 2020-04-05 02:14 ./usr/ drwxr-xr-x root/root 0 2020-04-05 02:14 ./usr/lib/ -rw-r--r-- root/root 76504 2020-04-05 02:14 ./usr/lib/libkmod.so.2.3.5 lrwxrwxrwx root/root 0 2020-04-05 02:14 ./usr/lib/libkmod.so.2 -> libkmod.so.2.3.5 Package: kmod-udeb Source: kmod Version: 27-3 Architecture: amd64 Maintainer: Marco d'Itri Installed-Size: 133 Depends: libc6-udeb (>= 2.30) Section: debian-installer Priority: important Description: libkmod shared library This is a minimal version of kmod, only for use in the installation system. Package: libkmod2-udeb Source: kmod Version: 27-3 Architecture: amd64 Maintainer: Marco d'Itri Installed-Size: 80 Depends: libc6-udeb (>= 2.30) Section: debian-installer Priority: important Description: libkmod shared library This is a minimal version of libkmod2, only for use in the installation system. -- ciao, Marco signature.asc Description: PGP signature
Bug#944425: marked as done (sat-xmpp-primitivus depends on python-urwid-satext which has been dropped)
Your message dated Sun, 05 Apr 2020 00:19:47 + with message-id and subject line Bug#944425: fixed in salutatoi 0.8.0~hg3247.f981c0e99220-1 has caused the Debian Bug report #944425, regarding sat-xmpp-primitivus depends on python-urwid-satext which has been dropped 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.) -- 944425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sat-xmpp-primitivus Version: 0.7.0a4-1 Severity: serious Justification: not installable -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear maintainer, Your package sat-xmpp-primitivus depends on python-urwid-satext. However, the maintainer of src:urwid-satext, the source package that used to build that binary package has removed python-urwid-satext due to process of removing Python 2 from Debian. Please update your package to handle the new situation. Paul - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-debug') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/2 CPU cores) 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 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sat-xmpp-primitivus depends on: ii python 2.7.17-1 pn python-dbus ii python-gi3.34.0-1 pn python-urwid pn python-urwid-satext pn sat-xmpp-core Versions of packages sat-xmpp-primitivus recommends: pn python-xlib sat-xmpp-primitivus suggests no packages. -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3HJtoACgkQnFyZ6wW9 dQqiFggAgAptBalFmJB67ZC0d1+P08wnSBN/c8ETuEwDWsoQeqRomdilSsQXm2ip K59xvul6H20ZpIhmWvxCVZanZpr5revf2Qe4UquMcQRIDBIQdvLsKw/f/SdQzdrm +GkUqP3z9jSxjdbQukVY0GW4Uv0LY9GdxN/RezAlKIwHOp/VLRyLkAErZAiiNKUt qvwztx/jvKy5ARrPbW1LJLaM74cQ8URdThRRvC3ye+KmtzUFlJqUn6ScsmR9Yj8F CzTM4OVReX6j1maUpLKQMBVq0Ab1ftMQhhI2LL3YdZENvEy28+opG927yvWJH9Ti AAg8A03JS5OPgobe+GPYlaqGU0bzEw== =ZCI0 -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: salutatoi Source-Version: 0.8.0~hg3247.f981c0e99220-1 Done: Martin We believe that the bug you reported is fixed in the latest version of salutatoi, 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 944...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin (supplier of updated salutatoi 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, 04 Apr 2020 23:46:37 + Source: salutatoi Architecture: source Version: 0.8.0~hg3247.f981c0e99220-1 Distribution: unstable Urgency: medium Maintainer: Debian XMPP Maintainers Changed-By: Martin Closes: 944425 Changes: salutatoi (0.8.0~hg3247.f981c0e99220-1) unstable; urgency=medium . * New upstream snaphost, move to Python 3 (Closes: #944425) Checksums-Sha1: cd4a1f4c1eb92a204219100770e56cd2b17cd3cd 2375 salutatoi_0.8.0~hg3247.f981c0e99220-1.dsc 8d206b4656c98838f702c3f2c44aa6de121a3ede 657063 salutatoi_0.8.0~hg3247.f981c0e99220.orig.tar.bz2 1e50ba4bdf04fe935794b2a15cd67359d0ab02ea 56140 salutatoi_0.8.0~hg3247.f981c0e99220-1.debian.tar.xz 5d32129422c622ee38b6f3de62bf7a2438b8d0a6 7888 salutatoi_0.8.0~hg3247.f981c0e99220-1_amd64.buildinfo Checksums-Sha256: 1daf06a6031cca925efd9e8214676a9acb3a23c1afe836f1e67472582f199689 2375 salutatoi_0.8.0~hg3247.f981c0e99220-1.dsc 5bedb17a6c26cd0c9b8a80624a7561e2b88bed185045219e69b50fd2b6fa332b 657063 salutatoi_0.8.0~hg3247.f981c0e99220.orig.tar.bz2 c19487bfb0f3b17c33329f23450a532c81da2dc708d36d19043fecc1cb95e55c 56140 salutatoi_0.8.0~hg3247.f981c0e99220-1.debian.tar.xz b6604538a6befbcd0fcaf7e3d2068e7fb32fc586cbf5c41066d2b3e8f6d6c3c3 7888 salutatoi_0.8.0~hg3247.f981c0e99220-1_amd64.buildinfo Files: 9d021024a020a6453197d63abcdbf2c2 2375 net optional salutatoi_0.8.0~hg3247.f981c0e99220-1.dsc 4a8b0ea10cc0ec9ed9d56a9331d8f42c 657063 net optional
Bug#954037: marked as done (openwince-jtag: FTBFS against glibc 2.30)
Your message dated Sun, 05 Apr 2020 00:04:09 + with message-id and subject line Bug#954037: fixed in openwince-jtag 0.5.1-8 has caused the Debian Bug report #954037, regarding openwince-jtag: FTBFS against glibc 2.30 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.) -- 954037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954037 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openwince-jtag Version: 0.5.1-7 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu focal ubuntu-patch Hi, openwince-jtag FTBFS against glibc 2.30 in unstable due to the removal of stropts.h. In Ubuntu, the attached patch was applied to achieve the following: * d/p/glibc-2.30.patch: Fix FTBFS against glibc 2.30 by checking for existence of stropts.h. Thanks for considering the patch. Logan -- System Information: Debian Release: bullseye/sid APT prefers focal APT policy: (500, 'focal') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-14-generic (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru openwince-jtag-0.5.1/debian/patches/glibc-2.30.patch openwince-jtag-0.5.1/debian/patches/glibc-2.30.patch --- openwince-jtag-0.5.1/debian/patches/glibc-2.30.patch1969-12-31 19:00:00.0 -0500 +++ openwince-jtag-0.5.1/debian/patches/glibc-2.30.patch2020-03-15 20:39:50.0 -0400 @@ -0,0 +1,14 @@ +--- a/src/tap/parport/ppdev.c b/src/tap/parport/ppdev.c +@@ -28,7 +28,11 @@ + #ifdef HAVE_LINUX_PPDEV_H + + #include ++ ++#ifdef HAVE_STROPTS_H + #include ++#endif ++ + #include + #include + #include diff -Nru openwince-jtag-0.5.1/debian/patches/series openwince-jtag-0.5.1/debian/patches/series --- openwince-jtag-0.5.1/debian/patches/series 2016-12-10 06:26:15.0 -0500 +++ openwince-jtag-0.5.1/debian/patches/series 2020-03-15 20:39:25.0 -0400 @@ -1,2 +1,3 @@ 0.5.1-6.patch format-security.patch +glibc-2.30.patch --- End Message --- --- Begin Message --- Source: openwince-jtag Source-Version: 0.5.1-8 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of openwince-jtag, 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 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated openwince-jtag 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, 05 Apr 2020 01:42:49 +0200 Source: openwince-jtag Architecture: source Version: 0.5.1-8 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 954037 Changes: openwince-jtag (0.5.1-8) unstable; urgency=medium . [ Andreas Beckmann ] * QA upload. * Switch to debhelper-compat (= 9). * Set Rules-Requires-Root: no. . [ Logan Rosen ] * d/p/glibc-2.30.patch: Fix FTBFS against glibc 2.30 by checking for existence of stropts.h. (Closes: #954037) Checksums-Sha1: a08c0d3e8637feb7c284860ddde6a828d3ea2236 1849 openwince-jtag_0.5.1-8.dsc 435921a858fc43efbb80e06be94deb42519f5c05 4060 openwince-jtag_0.5.1-8.debian.tar.xz 62afae0d4dec468c8af512c2c5f500b709b0dbe6 5440 openwince-jtag_0.5.1-8_source.buildinfo Checksums-Sha256: 4df7d2834f4ef6c36225dfc2a350745f42dcf36072e95c154fa44738488bde5a 1849 openwince-jtag_0.5.1-8.dsc 89b9d9aacd72e1c0a53945263e88992e891004743be2c2b71d28369e7962488e 4060 openwince-jtag_0.5.1-8.debian.tar.xz e71837d49a68a7f83d95db2d350a9caea4dc3159808f08296109fb524ae59a2b 5440 openwince-jtag_0.5.1-8_source.buildinfo Files: a8420331cbf24735890677025536769d 1849 embedded optional openwince-jtag_0.5.1-8.dsc a3cfc208394e68529f0143c4ae2e8eb1 4060 embedded optional openwince-jtag_0.5.1-8.debian.tar.xz 8214b6fb8de3f7f2b10d71ef26834ace 5440 embedded optional
Bug#936293: marked as done (cheetah: Python2 removal in sid/bullseye)
Your message dated Sat, 04 Apr 2020 23:48:42 + with message-id and subject line Bug#936293: fixed in cheetah 3.2.4-2 has caused the Debian Bug report #936293, regarding cheetah: Python2 removal in sid/bullseye 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.) -- 936293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936293 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:cheetah Version: 3.1.0-3 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:cheetah If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: cheetah Source-Version: 3.2.4-2 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of cheetah, 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 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated cheetah 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: Sat, 04 Apr 2020 19:24:19 -0400 Source: cheetah Architecture: source Version: 3.2.4-2 Distribution: unstable Urgency: medium Maintainer: JCF Ploemen (jcfp) Changed-By: Sandro Tosi Closes: 936293 Changes: cheetah (3.2.4-2) unstable; urgency=medium . * Drop python2 support; Closes: #936293 Checksums-Sha1: 61f928b0ff11c7630f63809f0544c40fdae99500 2199 cheetah_3.2.4-2.dsc 64047663d3d27cc9d6c3b38d79c5155baaae966d 46232 cheetah_3.2.4-2.debian.tar.xz 0c308aeda60b8c79a707658bcf3f799492324a06 7760 cheetah_3.2.4-2_source.buildinfo Checksums-Sha256: 82571ea70067167748988a63992a9d32b97ba30868ac8c9c96862bf0c94e273a 2199 cheetah_3.2.4-2.dsc efc20d45bd7953af2b9ad4a817cbde95fa2a06ef7683d2de51368b15454fd325 46232 cheetah_3.2.4-2.debian.tar.xz 9c3f115c46c7072c5ecc76f3dd23891be6a631e0b0391b35a578bb3965a73d46 7760 cheetah_3.2.4-2_source.buildinfo Files: 95249644b5ef48577f3f0daaab8110e6 2199 python optional cheetah_3.2.4-2.dsc
Bug#953958: marked as done (libcrypt1: Wrong soname on ia64)
Your message dated Sat, 04 Apr 2020 23:33:44 + with message-id and subject line Bug#953958: fixed in libxcrypt 1:4.4.16-1 has caused the Debian Bug report #953958, regarding libcrypt1: Wrong soname on ia64 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.) -- 953958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953958 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libcrypt1 Severity: serious libcrypt1 currently ships the file in /usr/lib, whereas libc6 shipped it in /lib, meaning that the Replaces relationship to libc6 is not doing anything on usrmerged systems. Please move it back to /lib until after bullseye, so that the Replaces actually work, and ownership of libcrypt1 is properly transferred from libc6 to libcrypt1. It likely works out fine in practice in most cases, but let's be safe, k? -- System Information: Debian Release: bullseye/sid APT prefers focal APT policy: (991, 'focal'), (500, 'focal') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-18-generic (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libcrypt1 depends on: ii libc6 2.30-0ubuntu3 libcrypt1 recommends no packages. libcrypt1 suggests no packages. -- no debconf information -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en --- End Message --- --- Begin Message --- Source: libxcrypt Source-Version: 1:4.4.16-1 Done: Marco d'Itri We believe that the bug you reported is fixed in the latest version of libxcrypt, 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 953...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marco d'Itri (supplier of updated libxcrypt 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, 05 Apr 2020 01:12:05 +0200 Source: libxcrypt Architecture: source Version: 1:4.4.16-1 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri Changed-By: Marco d'Itri Closes: 953538 953958 Changes: libxcrypt (1:4.4.16-1) unstable; urgency=medium . * New upstream release. * Rename back the library to libcrypt.so.1 on ia64. (Closes: #953958) * Add an autopkg test contributed by Matthias Klose. (Closes: #953538) Checksums-Sha1: bec1e91cc270cbd334ba26e2c8ce58ca1771b5f3 1463 libxcrypt_4.4.16-1.dsc a8e2c572f55b7e24e525a6615705e81a0c7096b5 354788 libxcrypt_4.4.16.orig.tar.xz e158134110734f79c4291d72206a8d39d5ba36c6 5484 libxcrypt_4.4.16-1.debian.tar.xz eeca5e490e366358880e5f86dc75b0946be5ce4d 6154 libxcrypt_4.4.16-1_amd64.buildinfo Checksums-Sha256: 764d1087763b0098781e74a33071131cb01719b97635296184365fcac37f397b 1463 libxcrypt_4.4.16-1.dsc 6a675b4ef1adde90b07ebc2f45eb9cd26702fbf87aa625d5aae9f68581d34fa6 354788 libxcrypt_4.4.16.orig.tar.xz e1409ed7e800b98f62a13f8775db0a7a146d2d96a19b371bbfd3bbd73d05abb3 5484 libxcrypt_4.4.16-1.debian.tar.xz f91a69126e4002dabaf4e49f77791497434edaffd3175e18028d694251569036 6154 libxcrypt_4.4.16-1_amd64.buildinfo Files: 65e283631f363090e13c55c831c80c71 1463 admin optional libxcrypt_4.4.16-1.dsc bf9943a6bee2d2e48b9b7827a94f1981 354788 admin optional libxcrypt_4.4.16.orig.tar.xz 51f1b3c4b6ee79486743304add934179 5484 admin optional libxcrypt_4.4.16-1.debian.tar.xz ab6c32635f626e550a546b80aabf2e3e 6154 admin optional libxcrypt_4.4.16-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQQnKUXNg20437dCfobLPsM64d7XgQUCXokVQgAKCRDLPsM64d7X gYuiAQCn0IHoivpMBfjdw68VG1pvg4PyQLJiW9cB2+n2qEQQKQEA0/b6xUvDqTRK R+CyHKimQJ6e9dIDXah+0Ttc/6BntgY= =XYqf -END PGP SIGNATURE End Message ---
Processed: Bug#936293 marked as pending in cheetah
Processing control commands: > tag -1 pending Bug #936293 [src:cheetah] cheetah: Python2 removal in sid/bullseye Added tag(s) pending. -- 936293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936293 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#936293: marked as pending in cheetah
Control: tag -1 pending Hello, Bug #936293 in cheetah reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/cheetah/-/commit/d25577f7a1808df43ff0e8d6156549f0af411524 Drop python2 support; Closes: #936293 (this message was generated automatically) -- Greetings https://bugs.debian.org/936293
Bug#937672: marked as done (python-cryptography: Python2 removal in sid/bullseye)
Your message dated Sat, 04 Apr 2020 23:18:58 + with message-id and subject line Bug#937672: fixed in python-cryptography 2.8-4 has caused the Debian Bug report #937672, regarding python-cryptography: Python2 removal in sid/bullseye 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.) -- 937672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937672 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-cryptography Version: 2.6.1-3 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-cryptography If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-cryptography Source-Version: 2.8-4 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of python-cryptography, 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 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated python-cryptography 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: Sat, 04 Apr 2020 18:53:59 -0400 Source: python-cryptography Architecture: source Version: 2.8-4 Distribution: unstable Urgency: medium Maintainer: Tristan Seligmann Changed-By: Sandro Tosi Closes: 937672 Changes: python-cryptography (2.8-4) unstable; urgency=medium . * Drop python2 support; Closes: #937672 * Add myself to Uploaders (with Maintainer's permission) Checksums-Sha1: 31dd4bbb351cd08a8da2e46205d8df7c111c014d 2903 python-cryptography_2.8-4.dsc 1a28045ee553872f56b4dfb373e8e3833af9b87e 11284 python-cryptography_2.8-4.debian.tar.xz 38d82261c77c38cd6af8c983519cb379df82d110 8655 python-cryptography_2.8-4_source.buildinfo Checksums-Sha256: c067c0b314af27fbf3b8f7b3f4a0fe71f196a3ebc61d42cabc0d32365a3a6fa2 2903 python-cryptography_2.8-4.dsc 40f104fcea6a5b49d6e93c91ce0389e37909e2c6aceaf8143f981f147ac3d04d 11284 python-cryptography_2.8-4.debian.tar.xz
Bug#936325: marked as done (configobj: Python2 removal in sid/bullseye)
Your message dated Sat, 04 Apr 2020 23:18:34 + with message-id and subject line Bug#936325: fixed in configobj 5.0.6-4 has caused the Debian Bug report #936325, regarding configobj: Python2 removal in sid/bullseye 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.) -- 936325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936325 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:configobj Version: 5.0.6-3 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:configobj If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: configobj Source-Version: 5.0.6-4 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of configobj, 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 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated configobj 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: Sat, 04 Apr 2020 18:57:38 -0400 Source: configobj Architecture: source Version: 5.0.6-4 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Sandro Tosi Closes: 936325 Changes: configobj (5.0.6-4) unstable; urgency=medium . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat. . [ Debian Janitor ] * Bump debhelper from old 11 to 12. * Set upstream metadata fields: Contact, Name. * Remove obsolete fields Name, Contact from debian/upstream/metadata. * Set upstream metadata fields: Repository. . [ Sandro Tosi ] * Drop python2 support; Closes: #936325 Checksums-Sha1: 4e924449c5077aee5a566e52465c76b86907682d 2246 configobj_5.0.6-4.dsc 103bc7d1fe3c41c755b38866396c7e8faab4c174 6916 configobj_5.0.6-4.debian.tar.xz 100c628f2fe2dd760a6a681fec42d8173701fdf9 7677 configobj_5.0.6-4_source.buildinfo Checksums-Sha256:
Bug#936325: marked as pending in configobj
Control: tag -1 pending Hello, Bug #936325 in configobj reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/configobj/-/commit/cdb997bee6541d89b009e8ac6d85b3912b498c30 Drop python2 support; Closes: #936325 (this message was generated automatically) -- Greetings https://bugs.debian.org/936325
Processed: Bug#936325 marked as pending in configobj
Processing control commands: > tag -1 pending Bug #936325 [src:configobj] configobj: Python2 removal in sid/bullseye Added tag(s) pending. -- 936325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936325 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#937672 marked as pending in python-cryptography
Processing control commands: > tag -1 pending Bug #937672 [src:python-cryptography] python-cryptography: Python2 removal in sid/bullseye Added tag(s) pending. -- 937672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937672 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937672: marked as pending in python-cryptography
Control: tag -1 pending Hello, Bug #937672 in python-cryptography reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/python-cryptography/-/commit/44213d2e1aded56b2a3042534da73079b07dbc6f Drop python2 support; Closes: #937672 (this message was generated automatically) -- Greetings https://bugs.debian.org/937672
Processed: py2removal bugs severity updates - 2020-04-04 22:36:27.552756+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # and https://lists.debian.org/debian-python/2019/12/msg00076.html > # and https://lists.debian.org/debian-python/2020/03/msg00087.html > # mail threads for more details on this severity update > # python-cheetah is a module and has 0 external rdeps or not in testing > severity 936293 serious Bug #936293 [src:cheetah] cheetah: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-configobj is a module and has 0 external rdeps or not in testing > severity 936325 serious Bug #936325 [src:configobj] configobj: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-sabyenc is a module and has 0 external rdeps or not in testing > severity 938154 serious Bug #938154 [src:python-sabyenc] python-sabyenc: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-cryptography is a module and has 0 external rdeps or not in testing > severity 937672 serious Bug #937672 [src:python-cryptography] python-cryptography: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 936293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936293 936325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936325 937672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937672 938154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955792: python-imaging-doc-handbook: Please remove this package
Source: python-imaging-doc-handbook Version: 1.1.2-1.2 Severity: serious Tags: sid bullseye X-Debbugs-CC: s...@debian.org Dear Debian python-imaging-doc-handbook maintainer, Since the Python Imaging Library is no longer part of Debian (it has long been replaced by Pillow) and that PIL upstream has been dead for 11 years, it doesn't make sense for this package to be still left in the Debian archive. Please consider removing it. I will consider filing a Removal bug 28 days later (after May 02, 2020) myself if there's no response. If you have any thoughts, please let me know ASAP. -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Processed: tagging 955650
Processing commands for cont...@bugs.debian.org: > tags 955650 + unreproducible Bug #955650 [src:python-tablib] python-tablib: FTBFS: E NotImplementedError: DataFrame Format requires `pandas` to be installed. Try `pip install tablib[pandas]`. Added tag(s) unreproducible. > severity 955650 normal Bug #955650 [src:python-tablib] python-tablib: FTBFS: E NotImplementedError: DataFrame Format requires `pandas` to be installed. Try `pip install tablib[pandas]`. Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 955650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955777: forensics-all: depends on neopi which was removed from unstable
Em sáb., 4 de abr. de 2020 às 17:59, Sebastian Ramacher escreveu: > > neopi was removed from unstable (see #955518). Please drop it from > forensics-all's Depends. Thanks Sebastian! I will fix it today. Regards, Eriberto
Bug#955690: marked as done (wine-development: FTBFS: configure: error: MinGW compiler not found, cross-compiling PE files won't be supported.)
Your message dated Sat, 04 Apr 2020 21:35:43 + with message-id and subject line Bug#955690: fixed in wine-development 5.5-3 has caused the Debian Bug report #955690, regarding wine-development: FTBFS: configure: error: MinGW compiler not found, cross-compiling PE files won't be supported. 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.) -- 955690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wine-development Version: 5.5-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200402 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for amd64-w64-mingw32-gcc... no > checking for x86_64-mingw32msvc-gcc... no > checking for amd64-mingw32msvc-gcc... no > checking for x86_64-w64-mingw32-clang... no > checking for amd64-w64-mingw32-clang... no > configure: error: MinGW compiler not found, cross-compiling PE files won't be > supported. > This is an error since --with-mingw was requested. > make[1]: *** [debian/rules:150: override_dh_auto_configure] Error 1 > make[1]: Leaving directory '/<>' The full build log is available from: http://qa-logs.debian.net/2020/04/02/wine-development_5.5-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 --- Source: wine-development Source-Version: 5.5-3 Done: Michael Gilbert We believe that the bug you reported is fixed in the latest version of wine-development, 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 955...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Gilbert (supplier of updated wine-development 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: Thu, 02 Apr 2020 22:32:21 + Source: wine-development Architecture: source Version: 5.5-3 Distribution: unstable Urgency: medium Maintainer: Debian Wine Party Changed-By: Michael Gilbert Closes: 955690 Changes: wine-development (5.5-3) unstable; urgency=medium . * Drop libsane from the build dependencies. * Do not build with mingw on arm architectures. * Support building with mingw on amd64 (closes: #955690). Checksums-Sha1: 3997566d7b10ad1ba2575aa307296a53a8e587ae 4622 wine-development_5.5-3.dsc 3eea8af2a466cd3be222b1d371f433b50ddb8aee 5701908 wine-development_5.5-3.debian.tar.xz 6cec5cef28257838649a6e3e7573f92b9e72161e 19255 wine-development_5.5-3_source.buildinfo Checksums-Sha256: a13a7e5ab8842d879d9dbc483cf41b32ab218ab7326f7cee55dc98df55343f5e 4622 wine-development_5.5-3.dsc f69c7b4ec9046bcf0605005d81a248b3760e8d4cfd026e499bc82048a28dfb7c 5701908 wine-development_5.5-3.debian.tar.xz 5b1f1dc6a5647210511adf8eb841830fc65a9dbd95973c3cdffb0fd6cae104af 19255 wine-development_5.5-3_source.buildinfo Files: 8971f1ecc9f074b6936d89b761633a5e 4622 otherosfs optional wine-development_5.5-3.dsc 02b42f2b42b5d7e3014e92ed8417a10a 5701908 otherosfs optional wine-development_5.5-3.debian.tar.xz 2d5fc22f1325e0414efbd3e9ac565b4a 19255 otherosfs optional wine-development_5.5-3_source.buildinfo -BEGIN PGP SIGNATURE- iQQzBAEBCgAdFiEEIwTlZiOEpzUxIyp4mD40ZYkUaygFAl6I+XAACgkQmD40ZYkU ayijPSAAz+1vqCGblpNx2+0Jimd72v6NiUlgSEOX267GlQzPOCPwrb+LxvvXwMl9 LFFrEX8bk0bQ1hmiqniDwPEopHObGFIrxyBsCj3r0zG6d5u4xD9nbS77y3tB/iSq T3dOY2ZTvinX33eWyOpVgJz34qSr5FyZDoxv5OozNNelNWpXk1dp22aqgtHgHlFS u/4Q/l0VnYj6tG3AL7udMFBkEWJIfMEcr+iw4kk/S/XTl05QXE80bW5Mxp6CubE4 vjubEm0u+sSN2ItocqhpOTQO4Fwy7OJYwV4itcQU01RKK84ems1W3gCCnGJ+h+Gj rXSp0p/tiZ+2zf0MlrH3Xo9e0qJZK2gn+pz+Y0YRxRciqJeruBQG8QlXKvfHOw9f kbUZCyYnbysqQkunptty3YSE3y+A7sIrNUoB35WBJRXJwDFHcxJYex00LFAMw1ZD unEcH2Xv+MxB1dcNn4wrQ7za/gFZZsFq2NBL1+t6YBZKT+VZ5ptTxviSD68/7+GP
Bug#955698: marked as done (src:haskell-brick: fails to migrate to testing for too long: ftbfs on armhf)
Your message dated Sat, 4 Apr 2020 23:04:11 +0200 with message-id <3e25b307-27f3-bbe1-589f-7d84232bf...@debian.org> and subject line Re: src:haskell-brick: fails to migrate to testing for too long: ftbfs on armhf has caused the Debian Bug report #955698, regarding src:haskell-brick: fails to migrate to testing for too long: ftbfs on armhf 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.) -- 955698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955698 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-brick Version: 0.46-2 Severity: serious Control: fixed -1 0.47.1-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:haskell-brick in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=haskell-brick signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- On Fri, 3 Apr 2020 22:24:14 +0200 Paul Gevers wrote: > Source: haskell-brick > Version: 0.46-2 > Severity: serious > Control: fixed -1 0.47.1-1 > Tags: sid bullseye > User: release.debian@packages.debian.org > Usertags: out-of-sync > > Dear maintainer(s), > > As recently announced [1], the Release Team now considers packages that > are out-of-sync between testing and unstable for more than 60 days as > having a Release Critical bug in testing. Your package src:haskell-brick > in its current version in unstable has been trying to migrate for 60 > days [2]. Hence, I am filing this bug. > > If a package is out of sync between unstable and testing for a longer > period, this usually means that bugs in the package in testing cannot be > fixed via unstable. Additionally, blocked packages can have impact on > other packages, which makes preparing for the release more difficult. > Finally, it often exposes issues with the package and/or > its (reverse-)dependencies. We expect maintainers to fix issues that > hamper the migration of their package in a timely manner. > > This bug will trigger auto-removal when appropriate. As with all new > bugs, there will be at least 30 days before the package is auto-removed. > > I have marked the version in unstable as fixing this bug, so if that > version or a later version migrates, this bug will no longer affect > testing. I have also tagged this bug to only affect sid and bullseye, so > it doesn't affect (old-)stable. > > If you believe your package is unable to migrate to testing due to > issues beyond your control, don't hesitate to contact the Release Team. > > Paul > > [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html > [2] https://qa.debian.org/excuses.php?package=haskell-brick > > /usr/bin/ld.gold: error: cannot open /usr/lib/gcc/arm-linux-gnueabihf/9/libgcc_s.so.1: No such file or directory /usr/bin/ld.gold: error: cannot open /usr/lib/gcc/arm-linux-gnueabihf/9/libgcc_s.so.1: No such file or directory collect2: error: ld returned 1 exit status `arm-linux-gnueabihf-gcc' failed in phase `Linker'. (Exit code: 1) . /usr/share/haskell-devscripts/Dh_Haskell.sh && \ Looks like we just need to gb it. Graham did it. G.--- End Message ---
Bug#954789: marked as done (weechat FTBFS against ruby 2.7)
Your message dated Sat, 04 Apr 2020 20:54:57 + with message-id and subject line Bug#954789: fixed in weechat 2.8-1 has caused the Debian Bug report #954789, regarding weechat FTBFS against ruby 2.7 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.) -- 954789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: weechat Version: 2.7.1-1 Severity: serious User pkg-ruby-extras-maintain...@lists.alioth.debian.org Usertags: ruby2.7-transition Dear Maintainer, We are removing ruby 2.5 support and src:weechat FTBFS against ruby 2.7, check this build log: https://buildd.debian.org/status/fetch.php?pkg=weechat=amd64=2.7.1-1%2Bb1=1584640456=0 The attached debdiff adds ruby 2.7 support, fixing the FTBFS. Thanks for considering the patch! -- Lucas Kanashiro diff -Nru weechat-2.7.1/debian/changelog weechat-2.7.1.new/debian/changelog --- weechat-2.7.1/debian/changelog 2020-03-09 11:59:31.0 -0300 +++ weechat-2.7.1.new/debian/changelog 2020-03-23 11:27:09.117206831 -0300 @@ -1,3 +1,11 @@ +weechat (2.7.1-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add ruby2.7 support ++ Add patch to allow cmake to search for ruby2.7 + + -- Lucas Kanashiro Mon, 23 Mar 2020 11:19:34 -0300 + weechat (2.7.1-1) unstable; urgency=medium * New upstream release diff -Nru weechat-2.7.1/debian/patches/04_ruby_27_support.patch weechat-2.7.1.new/debian/patches/04_ruby_27_support.patch --- weechat-2.7.1/debian/patches/04_ruby_27_support.patch 1969-12-31 21:00:00.0 -0300 +++ weechat-2.7.1.new/debian/patches/04_ruby_27_support.patch 2020-03-23 11:19:32.396243241 -0300 @@ -0,0 +1,25 @@ +Description: Add detection for Ruby 2.7 +Author: Lucas Kanashiro +Forwarded: https://github.com/weechat/weechat/pull/1455 +Last-Updated: 2020-03-03 + +--- a/cmake/FindRuby.cmake b/cmake/FindRuby.cmake +@@ -33,7 +33,7 @@ + + find_package(PkgConfig) + if(PKG_CONFIG_FOUND) +- pkg_search_module(RUBY ruby-2.6 ruby-2.5 ruby-2.4 ruby-2.3 ruby-2.2 ruby-2.1 ruby-2.0 ruby-1.9) ++ pkg_search_module(RUBY ruby-2.7 ruby-2.6 ruby-2.5 ruby-2.4 ruby-2.3 ruby-2.2 ruby-2.1 ruby-2.0 ruby-1.9) + endif() + + if(RUBY_FOUND) +@@ -41,7 +41,7 @@ + mark_as_advanced(RUBY_LIB) + else() + find_program(RUBY_EXECUTABLE +-NAMES ruby2.6.0 ruby260 ruby2.6 ruby2.5.0 ruby250 ruby2.5 ruby2.4.0 ruby240 ruby2.4 ruby2.3.0 ruby230 ruby2.3 ruby23 ruby2.2.3 ruby223 ruby2.2.2 ruby222 ruby2.2.1 ruby221 ruby2.2.0 ruby220 ruby2.2 ruby22 ruby2.1.7 ruby217 ruby2.1.6 ruby216 ruby2.1.5 ruby215 ruby2.1.4 ruby214 ruby2.1.3 ruby213 ruby2.1.2 ruby212 ruby2.1.1 ruby211 ruby2.1.0 ruby210 ruby2.1 ruby21 ruby2.0 ruby20 ruby1.9.3 ruby193 ruby1.9.2 ruby192 ruby1.9.1 ruby191 ruby1.9 ruby19 ruby ++NAMES ruby2.7.0 ruby270 ruby2.7 ruby2.6.0 ruby260 ruby2.6 ruby2.5.0 ruby250 ruby2.5 ruby2.4.0 ruby240 ruby2.4 ruby2.3.0 ruby230 ruby2.3 ruby23 ruby2.2.3 ruby223 ruby2.2.2 ruby222 ruby2.2.1 ruby221 ruby2.2.0 ruby220 ruby2.2 ruby22 ruby2.1.7 ruby217 ruby2.1.6 ruby216 ruby2.1.5 ruby215 ruby2.1.4 ruby214 ruby2.1.3 ruby213 ruby2.1.2 ruby212 ruby2.1.1 ruby211 ruby2.1.0 ruby210 ruby2.1 ruby21 ruby2.0 ruby20 ruby1.9.3 ruby193 ruby1.9.2 ruby192 ruby1.9.1 ruby191 ruby1.9 ruby19 ruby + PATHS /usr/bin /usr/local/bin /usr/pkg/bin + ) + if(RUBY_EXECUTABLE) diff -Nru weechat-2.7.1/debian/patches/series weechat-2.7.1.new/debian/patches/series --- weechat-2.7.1/debian/patches/series 2020-03-09 11:59:31.0 -0300 +++ weechat-2.7.1.new/debian/patches/series 2020-03-23 11:18:42.728134596 -0300 @@ -1,3 +1,4 @@ 01_fix_asciidoctor_options.patch 02_fix_iconv_detection 03_fix_php_crash.patch +04_ruby_27_support.patch --- End Message --- --- Begin Message --- Source: weechat Source-Version: 2.8-1 Done: Emmanuel Bouthenot We believe that the bug you reported is fixed in the latest version of weechat, 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 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bouthenot (supplier of updated weechat 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
Bug#954701: marked as done (weechat: FTBFS: Ruby not found)
Your message dated Sat, 04 Apr 2020 20:54:57 + with message-id and subject line Bug#954701: fixed in weechat 2.8-1 has caused the Debian Bug report #954701, regarding weechat: FTBFS: Ruby not found 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.) -- 954701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954701 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: weechat Version: 2.7.1-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200322 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 '/<>' > mkdir -p builddir > cd builddir && \ > cmake .. \ > -DCMAKE_INSTALL_PREFIX:FILEPATH=/usr \ > -DLIBDIR=/usr/lib/x86_64-linux-gnu \ > -DENABLE_JAVASCRIPT:BOOL=OFF \ > -DENABLE_DOC:BOOL=ON \ > -DENABLE_MAN:BOOL=ON \ > -DCMAKE_BUILD_TYPE:STRING=RelWithDebInfo \ > -DCMAKE_C_FLAGS_RELWITHDEBINFO:STRING="-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -D_FORTIFY_SOURCE=2" \ > -DCMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING="-Wl,-z,relro > -Wl,-z,now" \ > -DCMAKE_SKIP_RPATH:BOOL=ON \ > -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON > -- The C compiler identification is GNU 9.3.0 > -- Check for working C compiler: /usr/bin/cc > -- Check for working C compiler: /usr/bin/cc -- works > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Detecting C compile features > -- Detecting C compile features - done > -- Looking for include file langinfo.h > -- Looking for include file langinfo.h - found > -- Looking for include file sys/resource.h > -- Looking for include file sys/resource.h - found > -- Looking for mallinfo > -- Looking for mallinfo - found > -- Looking for eat_newline_glitch > -- Looking for eat_newline_glitch - found > -- Looking for include file libintl.h > -- Looking for include file libintl.h - found > -- Looking for dgettext > -- Looking for dgettext - found > -- Found Intl: /usr/include > -- Found GCRYPT: -L/usr/lib/x86_64-linux-gnu -lgcrypt > -- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.11") > -- Looking for iconv_open > -- Looking for iconv_open - found > -- Performing Test ICONV_2ARG_IS_CONST > -- Performing Test ICONV_2ARG_IS_CONST - Success > -- Found CURL: /usr/lib/x86_64-linux-gnu/libcurl.so (found version "7.68.0") > -- Looking for flock > -- Looking for flock - found > -- Looking for backtrace > -- Looking for backtrace - found > -- Found PkgConfig: /usr/bin/pkg-config (found version "0.29") > -- Checking for module 'python3-embed' > -- Found python3-embed, version 3.8 > -- Checking for one of the modules > 'ruby-2.6;ruby-2.5;ruby-2.4;ruby-2.3;ruby-2.2;ruby-2.1;ruby-2.0;ruby-1.9' > CMake Error at src/plugins/CMakeLists.txt:116 (message): > Ruby not found > > > -- Checking for one of the modules > 'lua5.3;lua-5.3;lua53;lua5.2;lua-5.2;lua52;lua5.1;lua-5.1;lua51;lua-5.0;lua5.0;lua50;lua' > -- Found Tclsh: /usr/bin/tclsh8.6 (found version "8.6") > -- Found TCL: /usr/lib/x86_64-linux-gnu/libtcl8.6.so > -- Could NOT find TCLTK (missing: TK_LIBRARY TK_INCLUDE_PATH) > -- Could NOT find TK (missing: TK_LIBRARY TK_INCLUDE_PATH) > -- Checking for one of the modules 'guile-2.2;guile-2.0' > -- Looking for scm_install_gmp_memory_functions > -- Looking for scm_install_gmp_memory_functions - found > -- Checking for one of the modules 'php7' > -- Looking for aspell_version_string > -- Looking for aspell_version_string - found > -- Checking for one of the modules 'ncursesw' > -- Looking for include file ncursesw/ncurses.h > -- Looking for include file ncursesw/ncurses.h - found > -- Configuring incomplete, errors occurred! > See also "/<>/builddir/CMakeFiles/CMakeOutput.log". > make[1]: *** [debian/rules:9: builddir/Makefile] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/03/22/weechat_2.7.1-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! 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 --- Source: weechat Source-Version: 2.8-1 Done: Emmanuel Bouthenot We believe that the bug you reported is fixed in the latest version of weechat, which
Processed: Re: Bug#955726: kodi: fails to connect to DLNA server
Processing control commands: > severity -1 important Bug #955726 [kodi] kodi: fails to connect to DLNA server Severity set to 'important' from 'grave' > forwarded -1 https://github.com/xbmc/xbmc/issues/16335 Bug #955726 [kodi] kodi: fails to connect to DLNA server Set Bug forwarded-to-address to 'https://github.com/xbmc/xbmc/issues/16335'. -- 955726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955726 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955726: kodi: fails to connect to DLNA server
Control: severity -1 important Control: forwarded -1 https://github.com/xbmc/xbmc/issues/16335 Hi Peter, Peter ezt írta (időpont: 2020. ápr. 4., Szo, 10:57): > > Package: kodi > Version: 2:18.6+dfsg1-1 > Severity: grave > Tags: upstream > Justification: renders package unusable > > Dear Maintainer, > >* What led up to the situation? > Updating Kodi to 18.6 >* What exactly did you do (or not do) that was effective (or > ineffective)? > Removing set up DLNA server and trying to connect again >* What was the outcome of this action? > DLNA server is not available >* What outcome did you expect instead? > Succesfull connection to DLNA server and playing video \ audio > > Note: this bug is reported upstream long time ago: > https://github.com/xbmc/xbmc/issues/16335 Thanks for reporting the bug. I agree that this is an important use case, but there are many other ways kodi can still be used thus I'm downgrading the severity [1]. Thanks for finding the upstream bug report. I hope upstream finds a solution that may be backportable to 18.x as well. Cheers, Balint [1] https://www.debian.org/Bugs/Developer#severities
Bug#955777: forensics-all: depends on neopi which was removed from unstable
Package: forensics-all Version: 3.17 Severity: serious Tags: sid bullseye neopi was removed from unstable (see #955518). Please drop it from forensics-all's Depends. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#952062: marked as pending in openjfx
Control: tag -1 pending Hello, Bug #952062 in openjfx reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/openjfx/-/commit/73412f16343b07d15b2f27e25d5cbc1b3505e520 Fix FTBFS due to -Werror=deprecated-declarations. Closes: #952062 Thanks: Bas Couwenberg for the patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/952062
Processed: Bug#952062 marked as pending in openjfx
Processing control commands: > tag -1 pending Bug #952062 [src:openjfx] openjfx: FTBFS: gtktypeutils.h:236:64: error: ‘GTypeDebugFlags’ is deprecated [-Werror=deprecated-declarations] Ignoring request to alter tags of bug #952062 to the same tags previously set -- 952062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952062 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:pillow: fails to migrate to testing for too long
Processing control commands: > fixed -1 7.0.0-4 Bug #955776 [src:pillow] src:pillow: fails to migrate to testing for too long Marked as fixed in versions pillow/7.0.0-4. -- 955776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955776: src:pillow: fails to migrate to testing for too long
Source: pillow Version: 6.2.1-2 Severity: serious Control: fixed -1 7.0.0-4 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:pillow in its current version in unstable has been trying to migrate for 66 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=pillow signature.asc Description: OpenPGP digital signature
Processed: tagging 954189, fixed 954189 in 0.2.1-1
Processing commands for cont...@bugs.debian.org: > tags 954189 + buster Bug #954189 [acmetool] acmetool: Buster acmetool stops working in June 1, 2020 Added tag(s) buster. > fixed 954189 0.2.1-1 Bug #954189 [acmetool] acmetool: Buster acmetool stops working in June 1, 2020 Marked as fixed in versions acmetool/0.2.1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 954189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945961: xz-utils: FTBFS: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*'
On 2019-12-03 20:18:20 [-0800], Jonathan Nieder wrote: > Hi, Hi, > Let's track down the cause first, before pursuing workarounds. Nothing happened here so far and I almost forgot about it. xz 5.2.5 has been released in the meantime. Do you want me to help you out in anyway? I could add the fix I suggested and prepare the new release. > Thanks much, > Jonathan Sebastian
Bug#955661: marked as done (drms: FTBFS: E ModuleNotFoundError: No module named 'matplotlib')
Your message dated Sat, 4 Apr 2020 20:49:19 +0100 with message-id and subject line already fixed has caused the Debian Bug report #955661, regarding drms: FTBFS: E ModuleNotFoundError: No module named 'matplotlib' 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.) -- 955661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955661 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: drms Version: 0.5.7-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200402 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:217: python3.7 setup.py config > running config > I: pybuild base:217: python3.8 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:217: /usr/bin/python3.7 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.7_drms/build/drms > copying drms/error.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms > copying drms/__init__.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms > copying drms/json.py -> /<>/.pybuild/cpython3_3.7_drms/build/drms > copying drms/__main__.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms > copying drms/_version.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms > copying drms/client.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms > copying drms/config.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms > copying drms/utils.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms > creating /<>/.pybuild/cpython3_3.7_drms/build/drms/tests > copying drms/tests/__init__.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms/tests > copying drms/tests/__main__.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms/tests > copying drms/tests/test_utils.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms/tests > copying drms/tests/test_to_datetime.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms/tests > copying drms/tests/test_config.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms/tests > copying drms/tests/test_init.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms/tests > copying drms/tests/conftest.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms/tests > copying drms/tests/test_exceptions.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms/tests > copying drms/tests/test_client.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms/tests > copying drms/tests/_runner.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms/tests > creating /<>/.pybuild/cpython3_3.7_drms/build/drms/tests/online > copying drms/tests/online/test_jsoc_email.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms/tests/online > copying drms/tests/online/__init__.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms/tests/online > copying drms/tests/online/test_jsoc_query.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms/tests/online > copying drms/tests/online/test_jsoc_info.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms/tests/online > copying drms/tests/online/test_kis_basic.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms/tests/online > copying drms/tests/online/test_jsoc_export.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms/tests/online > copying drms/tests/online/test_jsoc_basic.py -> > /<>/.pybuild/cpython3_3.7_drms/build/drms/tests/online > UPDATING /<>/.pybuild/cpython3_3.7_drms/build/drms/_version.py > set /<>/.pybuild/cpython3_3.7_drms/build/drms/_version.py to > '0.5.7' > I: pybuild base:217: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.8_drms/build/drms > copying drms/error.py -> > /<>/.pybuild/cpython3_3.8_drms/build/drms > copying drms/__init__.py -> > /<>/.pybuild/cpython3_3.8_drms/build/drms > copying drms/json.py -> /<>/.pybuild/cpython3_3.8_drms/build/drms > copying drms/__main__.py -> > /<>/.pybuild/cpython3_3.8_drms/build/drms > copying drms/_version.py -> > /<>/.pybuild/cpython3_3.8_drms/build/drms > copying drms/client.py -> > /<>/.pybuild/cpython3_3.8_drms/build/drms > copying drms/config.py -> > /<>/.pybuild/cpython3_3.8_drms/build/drms > copying drms/utils.py -> > /<>/.pybuild/cpython3_3.8_drms/build/drms > creating /<>/.pybuild/cpython3_3.8_drms/build/drms/tests > copying drms/tests/__init__.py -> > /<>/.pybuild/cpython3_3.8_drms/build/drms/tests > copying drms/tests/__main__.py
Bug#955772: dask.distributed: flaky autopkgtest: timeout reached in test_robust_to_bad_sizeof_estimates
Source: dask.distributed
Version: 2.10.0+ds.1-3
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
You package has an autopkgtest, great. However, until recently it always
failed. With the upload of 2.10.0+ds.1-3 it now *sometimes* passes.
Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests. Please either fix the test to be more robust, or or use the
"flaky" restriction for the offending test until a solution has been found.
I copied the output at the bottom of this report. All the failing tests
that I inspected look like it.
I'll have the migration software ignore the results of your autopkgtest
until this bug is fixed.
Paul
https://ci.debian.net/data/autopkgtest/testing/amd64/d/dask.distributed/4801510/log.gz
=== FAILURES
===
_ test_robust_to_bad_sizeof_estimates
__
def test_func():
result = None
workers = []
with clean(timeout=active_rpc_timeout, **clean_kwargs) as loop:
async def coro():
with dask.config.set(config):
s = False
for i in range(5):
try:
s, ws = await start_cluster(
nthreads,
scheduler,
loop,
security=security,
Worker=Worker,
scheduler_kwargs=scheduler_kwargs,
worker_kwargs=worker_kwargs,
)
except Exception as e:
logger.error(
"Failed to start gen_cluster, retrying",
exc_info=True,
)
else:
workers[:] = ws
args = [s] + workers
break
if s is False:
raise Exception("Could not start cluster")
if client:
c = await Client(
s.address,
loop=loop,
security=security,
asynchronous=True,
**client_kwargs
)
args = [c] + args
try:
future = func(*args)
if timeout:
future = asyncio.wait_for(future, timeout)
result = await future
if s.validate:
s.validate_state()
finally:
if client and c.status not in ("closing", "closed"):
await c._close(fast=s.status == "closed")
await end_cluster(s, workers)
await asyncio.wait_for(cleanup_global_workers(), 1)
try:
c = await default_client()
except ValueError:
pass
else:
await c._close(fast=True)
for i in range(5):
if all(c.closed() for c in Comm._instances):
break
else:
await asyncio.sleep(0.05)
else:
L = [c for c in Comm._instances if not c.closed()]
Comm._instances.clear()
# raise ValueError("Unclosed Comms", L)
print("Unclosed Comms", L)
return result
result = loop.run_sync(
> coro, timeout=timeout * 2 if timeout else timeout
)
/usr/lib/python3/dist-packages/distributed/utils_test.py:957:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
/usr/lib/python3/dist-packages/tornado/ioloop.py:576: in run_sync
return future_cell[0].result()
/usr/lib/python3/dist-packages/distributed/utils_test.py:927: in coro
result = await future
/usr/lib/python3.7/asyncio/tasks.py:442: in wait_for
return fut.result()
/usr/lib/python3/dist-packages/tornado/gen.py:1162: in run
yielded = self.gen.send(value)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
c =
s =
a =
@gen_cluster(
nthreads=[("127.0.0.1", 1)],
client=True,
Processed: Re: openjfx: Patch to use -Wno-error=deprecated-declarations
Processing commands for cont...@bugs.debian.org: > tags 952062 pending Bug #952062 [src:openjfx] openjfx: FTBFS: gtktypeutils.h:236:64: error: ‘GTypeDebugFlags’ is deprecated [-Werror=deprecated-declarations] Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 952062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952062 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955771: rust-env-logger, (build-)depends unsatisfiable
Package: rust-env-logger Version: 0.7.1-1 Severity: serious Tags: patch The rust-env-logger source package build-depends on and the librust-env-logger+default-dev and librust-env-logger+humantime-dev binary packages depend on librust-humantime-1+default-dev which is no longer provided by librust-humantime-dev After changing the dependencies in the debian packaging and in Cargo.toml to version 2 the package built succesfully. I also did a test rebuild of rust-bindgen (in raspbian bullseye-staging) with the new rust-env-logger which was also succesful. As such I decided to go ahead and upload to raspbian. A debdiff should appear soon at https://debdiffs.raspbian.org/main/r/rust-env-logger . No intent to NMU in Debian.
Bug#955661: Reassign to pandas
Control: reassign -1 python3-pandas 0.25.3+dfsg-9 Control: affects -1 src:drms That seems a missing dependency in Pandas. Cheers Ole
Processed: Reassign to pandas
Processing control commands: > reassign -1 python3-pandas 0.25.3+dfsg-9 Bug #955661 [src:drms] drms: FTBFS: E ModuleNotFoundError: No module named 'matplotlib' Bug reassigned from package 'src:drms' to 'python3-pandas'. No longer marked as found in versions drms/0.5.7-1. Ignoring request to alter fixed versions of bug #955661 to the same values previously set Bug #955661 [python3-pandas] drms: FTBFS: E ModuleNotFoundError: No module named 'matplotlib' Marked as found in versions pandas/0.25.3+dfsg-9. > affects -1 src:drms Bug #955661 [python3-pandas] drms: FTBFS: E ModuleNotFoundError: No module named 'matplotlib' Added indication that 955661 affects src:drms -- 955661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955661 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937400: pycaml: Python2 removal in sid/bullseye
On Tue, Jan 14, 2020 at 11:06:22AM +0100, Stéphane Glondu wrote: > Le 21/11/2019 à 15:26, Stéphane Glondu a écrit : > > pycaml is deprecated in favour of pyml (in NEW). The only reverse > > dependency, coccinelle, is supposed to switch to pyml. Once it's done, > > we can remove pycaml. > > pyml is now in testing. > > Emmanuel Arias (in CC) has shown interest in adopting coccinelle (#886679). > > Emmanuel, what is the status of packaging a new version of coccinelle? A new version of coccinelle has been uploaded, so let's remove pycaml now? Cheers, Moritz
Bug#955764: librust-cargo-dev: dependencies unsatisfiable
Package: librust-cargo-dev Version: 0.41.0-2 Severity: serious Tags: fixed-upstream librust-cargo-dev depends on librust-humantime-1+default-dev but rust-humantime in debian is now at version 2.0.0. This seems to have been fixed upstream.
Bug#955727: marked as pending in fotoxx
Control: tag -1 pending Hello, Bug #955727 in fotoxx reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/fotoxx/-/commit/dc10511c428c84fcb3acfda284fe3c939eaaceb6 debian/control: Add dcraw to depends. (closes: #955727) Thanks to Alberto Luaces for the bug report and patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/955727
Processed: Bug#955727 marked as pending in fotoxx
Processing control commands: > tag -1 pending Bug #955727 [src:fotoxx] fotoxx: dcraw is required, but it is not yet a dependency Added tag(s) pending. -- 955727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955760: librust-plist-dev: dependencies unsatisfiable.
Package: librust-plist-dev Version: 0.5.1-1 Severity: serious Tags: fixed-upstream librust-plist-dev depends on and the rust-plist source package build-depends on librust-humantime-1+default-dev , which is no longer available. Upstream seems to have moved to humantime 2 which should fix this.
Bug#955690: wine-development: FTBFS: configure: error: MinGW compiler not found, cross-compiling PE files won't be supported.
On Fri, 3 Apr 2020 23:42:10 +0200, Gianfranco Costamagna wrote: > Can you please also add this patch to fix arm64 build failures with default > clang-10? The arm64 build no longer uses clang, so I don’t think this is necessary (and it should be handled differently anyway AFAICT, see the extra build flags in debian/rules). Regards, Stephen pgp5DPGSogNPs.pgp Description: OpenPGP digital signature
Bug#955690: wine-development: FTBFS: configure: error: MinGW compiler not found, cross-compiling PE files won't be supported.
On Sat, 4 Apr 2020 12:08:35 -0400, Michael Gilbert wrote: > On Fri, Apr 3, 2020 at 5:28 PM Stephen Kitt wrote: > > Thanks for the report, the package is missing a build-dependency on > > gcc-mingw-w64-x86-64. > > There is more to it than this. I am working on it now. Yes, so far I’ve run into the 16-bit PE binaries (only on i386), and the wine64-development.1 manpage. I’ll leave you to it! > > Michael, I can take care of fixing this, doing a rebuild to make sure and > > uploading, if you could push your git repo ;-). > > Done. Thanks! Regards, Stephen pgpq2Df033NGD.pgp Description: OpenPGP digital signature
Bug#955751: marked as done (gap-atlasrep: package is broken)
Your message dated Sat, 04 Apr 2020 16:04:08 + with message-id and subject line Bug#955751: fixed in gap-atlasrep 2.1.0-2 has caused the Debian Bug report #955751, regarding gap-atlasrep: package is broken 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.) -- 955751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gap-atlasrep Version: 2.1.0-1 Severity: grave Hi Bill, during a test build of sage I noticed that the newly updated gap-atlasrep package seems to be seriously broken. Trying the first commands from the atlasrep tutorial yields this: $ gap ┌───┐ GAP 4.10.2 of 19-Jun-2019 │ GAP │ https://www.gap-system.org └───┘ Architecture: x86_64-pc-linux-gnu-default64-kv3 Configuration: gmp 6.2.0, readline Loading the library and packages ... Error, AppendList: must be a small list (not a boolean or fail) in Append( res, arg[i] ); at /usr/share/gap/lib/list.gi:2011 called from Concatenation( "core|", Filename( DirectoriesPackageLibrary( "atlasrep", "" ), "atlasprm.json" ) ) at /usr/share/gap/pkg/AtlasRep/gap/userpref.g:154 called from record.default( ) at /usr/share/gap/lib/userpref.g:274 called from ( ) called from read-eval loop at /usr/share/gap/pkg/AtlasRep/gap/userpref.g:208 you can replace via 'return ;' brk> LoadPackage( "AtlasRep", false ); true brk> DisplayAtlasInfo(); Syntax warning: Unbound global variable in *errin*:2 DisplayAtlasInfo(); ^ Error, Variable: 'DisplayAtlasInfo' must have a value in called from Concatenation( "core|", Filename( DirectoriesPackageLibrary( "atlasrep", "" ), "atlasprm.json" ) ) at /usr/share/gap/pkg/AtlasRep/gap/userpref.g:154 called from record.default( ) at /usr/share/gap/lib/userpref.g:274 called from ( ) called from read-eval loop at *errin*:2 brk> g:= AtlasGroup( "M24" ); Syntax warning: Unbound global variable in *errin*:3 g:= AtlasGroup( "M24" ); ^^ Syntax warning: Unbound global variable in *errin*:3 g:= AtlasGroup( "M24" ); ^ Error, Variable: 'AtlasGroup' must have a value in called from Concatenation( "core|", Filename( DirectoriesPackageLibrary( "atlasrep", "" ), "atlasprm.json" ) ) at /usr/share/gap/pkg/AtlasRep/gap/userpref.g:154 called from record.default( ) at /usr/share/gap/lib/userpref.g:274 called from ( ) called from read-eval loop at *errin*:3 Downgrading gap-atlasrep to 1.5.1-2 fixes the problem. Best, Tobias --- End Message --- --- Begin Message --- Source: gap-atlasrep Source-Version: 2.1.0-2 Done: Bill Allombert We believe that the bug you reported is fixed in the latest version of gap-atlasrep, 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 955...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bill Allombert (supplier of updated gap-atlasrep 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, 04 Apr 2020 16:44:04 +0200 Source: gap-atlasrep Architecture: source Version: 2.1.0-2 Distribution: unstable Urgency: low Maintainer: Bill Allombert Changed-By: Bill Allombert Closes: 955751 Changes: gap-atlasrep (2.1.0-2) unstable; urgency=low . * debian/rules: install atlasprm.json. Closes: #955751 Checksums-Sha1: c98380699f8025724e35f4cde2283de79aff00c8 1891 gap-atlasrep_2.1.0-2.dsc b7935f99717e0c23d83e6adae1c47c35c2662dd1 12664 gap-atlasrep_2.1.0-2.debian.tar.xz 770f6486686630b87e93cdb1bf78c6c53bc4cff1 8086 gap-atlasrep_2.1.0-2_source.buildinfo Checksums-Sha256: b16e2d87e16b8781867a1e947379488ee3b99a9f4ef970067f17fb27692c1fa2 1891 gap-atlasrep_2.1.0-2.dsc 8ffac380c265ac7932526bfd3089e6ca936af9e424b41d6f5f49f78a4ec5b0ad 12664 gap-atlasrep_2.1.0-2.debian.tar.xz 35bf1dcb9fafa7c615b738cbf985b80faf890a9a2bc6947b8744807f81939861 8086 gap-atlasrep_2.1.0-2_source.buildinfo Files: abca6ed186cfa7b5aca9b404a2d4e39d 1891 math optional gap-atlasrep_2.1.0-2.dsc d83cbab29efa3de6b7d6a1370f2306ac 12664 math optional gap-atlasrep_2.1.0-2.debian.tar.xz f263add25b5cfc7840c9fca03b828ef4 8086 math optional gap-atlasrep_2.1.0-2_source.buildinfo -BEGIN PGP SIGNATURE-
Bug#955690: wine-development: FTBFS: configure: error: MinGW compiler not found, cross-compiling PE files won't be supported.
On Fri, Apr 3, 2020 at 5:28 PM Stephen Kitt wrote: > Thanks for the report, the package is missing a build-dependency on > gcc-mingw-w64-x86-64. There is more to it than this. I am working on it now. > Michael, I can take care of fixing this, doing a rebuild to make sure and > uploading, if you could push your git repo ;-). Done. Best wishes, Mike
Bug#946104: marked as done (autopkgtest fails with "Failed to retrieve max realtime priority: Input/output error")
Your message dated Sat, 04 Apr 2020 15:50:19 + with message-id and subject line Bug#946104: fixed in rtkit 0.12-5 has caused the Debian Bug report #946104, regarding autopkgtest fails with "Failed to retrieve max realtime priority: Input/output error" 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.) -- 946104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rtkit Version: 0.12-4 Severity: normal Hi Felipe, today I was investigating why an update of systemd (v244) was blocked by a failing autopkgtest in rtkit from testing migration. When trying to investigate the issue, I could reproduce the failure with both systemd v243 and v244 locally. So I assume it's the rtkit autopkgtest which is flaky since [1] shows autopkgtest passing. I've attached logs for both sid and bullseye. The tests are run on Debian sid. Regards, Michael [1] https://ci.debian.net/packages/r/rtkit/unstable/amd64/ -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.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_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information autopkgtest [21:32:06]: version 5.11 autopkgtest [21:32:06]: host pluto; command line: /usr/bin/autopkgtest rtkit -- lxc -s autopkgtest-bullseye autopkgtest [21:32:13]: testbed dpkg architecture: amd64 autopkgtest [21:32:13]: testbed running kernel: Linux 5.3.0-2-amd64 #1 SMP Debian 5.3.9-3 (2019-11-19) autopkgtest [21:32:13]: apt-source rtkit gpgv: unknown type of key resource 'trustedkeys.kbx' gpgv: Schlüsselblockhilfsmittel`/root/.gnupg/trustedkeys.kbx': General error gpgv: Signatur vom Sa 23 Mär 2019 23:24:36 UTC gpgv:mittels RSA-Schlüssel 218EE0362033C87B6C135FA4A3BABAE2408DD6CF gpgv:Aussteller "fsate...@debian.org" gpgv: Signatur kann nicht geprüft werden: No public key dpkg-source: warning: failed to verify signature on ./rtkit_0.12-4.dsc autopkgtest [21:32:15]: testing package rtkit version 0.12-4 autopkgtest [21:32:15]: build not needed autopkgtest [21:32:15]: test installed-tests: preparing testbed Paketlisten werden gelesen... Abhängigkeitsbaum wird aufgebaut Statusinformationen werden eingelesen Abhängigkeiten werden korrigiert ...Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Fertig Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Die folgenden zusätzlichen Pakete werden installiert: libglib2.0-0 libpolkit-agent-1-0 libpolkit-gobject-1-0 policykit-1 rtkit Empfohlene Pakete: libglib2.0-data shared-mime-info xdg-user-dirs Die folgenden NEUEN Pakete werden installiert: libglib2.0-0 libpolkit-agent-1-0 libpolkit-gobject-1-0 policykit-1 rtkit 0 aktualisiert, 5 neu installiert, 0 zu entfernen und 0 nicht aktualisiert. 1 nicht vollständig installiert oder entfernt. Es müssen 1.525 kB an Archiven heruntergeladen werden. Nach dieser Operation werden 4.698 kB Plattenplatz zusätzlich benutzt. Holen:1 http://deb.debian.org/debian bullseye/main amd64 libglib2.0-0 amd64 2.62.3-1 [1.320 kB] Holen:2 http://deb.debian.org/debian bullseye/main amd64 libpolkit-gobject-1-0 amd64 0.105-26 [47,5 kB] Holen:3 http://deb.debian.org/debian bullseye/main amd64 libpolkit-agent-1-0 amd64 0.105-26 [27,4 kB] Holen:4 http://deb.debian.org/debian bullseye/main amd64 policykit-1 amd64 0.105-26 [96,0 kB] Holen:5 http://deb.debian.org/debian bullseye/main amd64 rtkit amd64 0.12-4 [34,3 kB] debconf: delaying package configuration, since apt-utils is not installed Es wurden 1.525 kB in 1 s geholt (2.163 kB/s). Vormals nicht ausgewähltes Paket libglib2.0-0:amd64 wird gewählt. (Lese Datenbank ... (Lese Datenbank ... 5% (Lese Datenbank ... 10% (Lese Datenbank ... 15% (Lese Datenbank ... 20% (Lese Datenbank ... 25% (Lese Datenbank ... 30% (Lese Datenbank ... 35% (Lese Datenbank ... 40% (Lese Datenbank ... 45% (Lese Datenbank ... 50% (Lese Datenbank ... 55% (Lese Datenbank ... 60% (Lese Datenbank ... 65% (Lese Datenbank ... 70% (Lese Datenbank ... 75% (Lese Datenbank ... 80% (Lese Datenbank ... 85% (Lese Datenbank ... 90% (Lese Datenbank ... 95% (Lese Datenbank ... 100% (Lese Datenbank ... 12390 Dateien und Verzeichnisse
Bug#955675: marked as done (expeyes: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Sat, 04 Apr 2020 15:34:57 + with message-id and subject line Bug#955675: fixed in expeyes 4.7.7+repack-1 has caused the Debian Bug report #955675, regarding expeyes: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 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.) -- 955675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: expeyes Version: 4.7.6+repack-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200402 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 '/<>/eyesjunior/helpFiles/ml' > rm -rf build/* > cd cover; rm -f *.aux *.log *~ > make[4]: Leaving directory '/<>/eyesjunior/helpFiles/ml' > make[3]: Leaving directory '/<>/eyesjunior/helpFiles' > [ ! -d clib ] || (cd clib/expeyes-clib && sh clean-all.sh) > Cleaning every autotool-generated stuff ... Done. > > For autotool generation: > invoke "libtoolize; autoreconf --install". > make[2]: Leaving directory '/<>' > # the clean process compiles a few Python scripts > find. -name __pycache__ | xargs rm -rf > /bin/sh: 1: find.: not found > rm -rf /<>/debian/build > make[1]: Leaving directory '/<>' >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building expeyes using existing > ./expeyes_4.7.6+repack.orig.tar.xz > dpkg-source: error: cannot represent change to > eyes17/helpFiles/en/_sources/__pycache__/conf.cpython-38.pyc: binary file > contents changed > dpkg-source: error: add > eyes17/helpFiles/en/_sources/__pycache__/conf.cpython-38.pyc in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: cannot represent change to > eyes17/helpFiles/es/_sources/__pycache__/conf.cpython-38.pyc: binary file > contents changed > dpkg-source: error: add > eyes17/helpFiles/es/_sources/__pycache__/conf.cpython-38.pyc in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: cannot represent change to > eyes17/helpFiles/fr/_sources/__pycache__/conf.cpython-38.pyc: binary file > contents changed > dpkg-source: error: add > eyes17/helpFiles/fr/_sources/__pycache__/conf.cpython-38.pyc in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: cannot represent change to > eyes17/helpFiles/ml/_sources/__pycache__/conf.cpython-38.pyc: binary file > contents changed > dpkg-source: error: add > eyes17/helpFiles/ml/_sources/__pycache__/conf.cpython-38.pyc in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: unrepresentable changes to source > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2020-04-03T17:26:40Z The full build log is available from: http://qa-logs.debian.net/2020/04/02/expeyes_4.7.6+repack-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! 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 --- Source: expeyes Source-Version: 4.7.7+repack-1 Done: Georges Khaznadar We believe that the bug you reported is fixed in the latest version of expeyes, 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 955...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georges Khaznadar (supplier of updated expeyes 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: Sat, 04 Apr 2020 16:09:19 +0200 Source: expeyes Architecture: source
Processed: Bug#946104 marked as pending in rtkit
Processing control commands: > tag -1 pending Bug #946104 [src:rtkit] autopkgtest fails with "Failed to retrieve max realtime priority: Input/output error" Added tag(s) pending. -- 946104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#946104: marked as pending in rtkit
Control: tag -1 pending Hello, Bug #946104 in rtkit reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/multimedia-team/rtkit/-/commit/46ece9aa4dc416b7880310d7b0333ff360ba411a Mark installed-tests as having isolation-machine restriction Turns out that depending on the container manager, realtime operations might not be allowed. Thus, let's require a machine for it' Closes: #946104 (this message was generated automatically) -- Greetings https://bugs.debian.org/946104
Bug#955751: gap-atlasrep: package is broken
On Sat, Apr 04, 2020 at 04:42:57PM +0200, Tobias Hansen wrote: > Source: gap-atlasrep > Version: 2.1.0-1 > Severity: grave > > Hi Bill, > > during a test build of sage I noticed that the newly updated gap-atlasrep > package seems to be seriously broken. Trying the first commands from the > atlasrep tutorial yields this: > > Downgrading gap-atlasrep to 1.5.1-2 fixes the problem. I know, it is missing the file atlasprm.json, I am uploading a fix as I write this. Thanks for testing this! I ill upload GAP 4.11.0 to experimental soon. Cheers, -- Bill. Imagine a large red swirl here.
Bug#955751: gap-atlasrep: package is broken
Source: gap-atlasrep Version: 2.1.0-1 Severity: grave Hi Bill, during a test build of sage I noticed that the newly updated gap-atlasrep package seems to be seriously broken. Trying the first commands from the atlasrep tutorial yields this: $ gap ┌───┐ GAP 4.10.2 of 19-Jun-2019 │ GAP │ https://www.gap-system.org └───┘ Architecture: x86_64-pc-linux-gnu-default64-kv3 Configuration: gmp 6.2.0, readline Loading the library and packages ... Error, AppendList: must be a small list (not a boolean or fail) in Append( res, arg[i] ); at /usr/share/gap/lib/list.gi:2011 called from Concatenation( "core|", Filename( DirectoriesPackageLibrary( "atlasrep", "" ), "atlasprm.json" ) ) at /usr/share/gap/pkg/AtlasRep/gap/userpref.g:154 called from record.default( ) at /usr/share/gap/lib/userpref.g:274 called from ( ) called from read-eval loop at /usr/share/gap/pkg/AtlasRep/gap/userpref.g:208 you can replace via 'return ;' brk> LoadPackage( "AtlasRep", false ); true brk> DisplayAtlasInfo(); Syntax warning: Unbound global variable in *errin*:2 DisplayAtlasInfo(); ^ Error, Variable: 'DisplayAtlasInfo' must have a value in called from Concatenation( "core|", Filename( DirectoriesPackageLibrary( "atlasrep", "" ), "atlasprm.json" ) ) at /usr/share/gap/pkg/AtlasRep/gap/userpref.g:154 called from record.default( ) at /usr/share/gap/lib/userpref.g:274 called from ( ) called from read-eval loop at *errin*:2 brk> g:= AtlasGroup( "M24" ); Syntax warning: Unbound global variable in *errin*:3 g:= AtlasGroup( "M24" ); ^^ Syntax warning: Unbound global variable in *errin*:3 g:= AtlasGroup( "M24" ); ^ Error, Variable: 'AtlasGroup' must have a value in called from Concatenation( "core|", Filename( DirectoriesPackageLibrary( "atlasrep", "" ), "atlasprm.json" ) ) at /usr/share/gap/pkg/AtlasRep/gap/userpref.g:154 called from record.default( ) at /usr/share/gap/lib/userpref.g:274 called from ( ) called from read-eval loop at *errin*:3 Downgrading gap-atlasrep to 1.5.1-2 fixes the problem. Best, Tobias
Bug#954620: marked as done (apertium-es-gl: FTBFS: mkdir: cannot create directory ‘/<>/debian/apertium-es-gl/usr/share/apertium/modes/’: No such file or directory)
Your message dated Sat, 04 Apr 2020 13:03:27 + with message-id and subject line Bug#954620: fixed in apertium-es-gl 1.0.8~r57542-4 has caused the Debian Bug report #954620, regarding apertium-es-gl: FTBFS: mkdir: cannot create directory ‘/<>/debian/apertium-es-gl/usr/share/apertium/modes/’: No such file or directory 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.) -- 954620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954620 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-es-gl Version: 1.0.8~r57542-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200321 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 '/<>' > make[2]: Nothing to be done for 'install-exec-am'. > apertium-gen-modes modes.xml > apertium-gen-modes modes.xml > apertium-gen-modes modes.xml apertium-es-gl > test -d /<>/debian/apertium-es-gl/usr/share/apertium/modes/ || > mkdir /<>/debian/apertium-es-gl/usr/share/apertium/modes/ > mkdir: cannot create directory > ‘/<>/debian/apertium-es-gl/usr/share/apertium/modes/’: No such > file or directory > make[2]: *** [Makefile:806: install-data-local] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/03/21/apertium-es-gl_1.0.8~r57542-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! 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 --- Source: apertium-es-gl Source-Version: 1.0.8~r57542-4 Done: Kartik Mistry We believe that the bug you reported is fixed in the latest version of apertium-es-gl, 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 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kartik Mistry (supplier of updated apertium-es-gl 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: Sat, 04 Apr 2020 17:54:31 +0530 Source: apertium-es-gl Architecture: source Version: 1.0.8~r57542-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Kartik Mistry Closes: 954620 Changes: apertium-es-gl (1.0.8~r57542-4) unstable; urgency=medium . * Fix FTBFS: mkdir: cannot create directory. (Closes: 954620) * Added debian/gitlab-ci.yml file. * debian/control: + Updated to Standards-Version 4.5.0 + Switched to debhelper-compat. + Added 'Rules-Requires-Root' field. * Added debian/upstream/metadata file. Checksums-Sha1: dce19e321f5e61251f28ebc4aa09d5e9116f807f 2112 apertium-es-gl_1.0.8~r57542-4.dsc 32f7065dc7735aa19096efeea143eda1271d0203 3248 apertium-es-gl_1.0.8~r57542-4.debian.tar.xz Checksums-Sha256: 8d32b2f76eb86daf032ed6243f71825411ecbad8c937e26deda54c4c0343085f 2112 apertium-es-gl_1.0.8~r57542-4.dsc b955804fa5ff1fe55eda128e4e6dc6fe028808e5f89155eb11baac677211a229 3248 apertium-es-gl_1.0.8~r57542-4.debian.tar.xz Files: 7ede1f07206d3e7ec6a3e957d5463fc1 2112 science optional apertium-es-gl_1.0.8~r57542-4.dsc ef0abc86cb7d9fcffdc38e8cf41c3489 3248 science optional apertium-es-gl_1.0.8~r57542-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEa2MbXvVUr2sRlmKSAsHT8ng6pN4FAl6IgIMACgkQAsHT8ng6 pN5rPRAAiyGO8l9MW4PThJBgeuf+tw4sBd/aKFhLnUq07n3bqv+X9OLzxJseMncc L7aZ2a0A2LYdg6kwOE+IUAFMq7t+am6ash+D6tl9/EIV4lb6TgFlD/YM4/EXHJ3o OwiqcLBPcDsF223PmefUC74u0zB8DugsZlfPHfu8NbQd8KNBMudzu9RAruzzZR6O DKx4Gy93zS5ipVlJy+2bDACh/PcnAG53hw4DJz0+NMb+hMkxCMTttOg8y8ci2T34 bUl0OOvL+Tkdmjp2AzwbhYMdD3NVlYSDLynEKkMJmeskPH2SMCTLeZZ4mBV/w/yY wzrLQCZ37/tAuRLoHGJUmhtNYrHixniQ9zWLisx5QIvkTs1ZWt1prPttH5w9ziob t8P85ftct3BYfBKZ1K+tfSZSdSKyOPipv57Jf3M3VWehZYaw85LimVe60c5iBhJY AKlWjBzkMcXGOKW2a8VmZeLROB6CK/tAvMFseeuenCEsU2hx1+DoyNhBbFfQSSXd UDYpo6EdKge4GfyzvAXPju14xqOXCSDsK4JM4ECN3rhSi0qagYeLT04NCTQ/9EMH
Bug#955740: kdenlive crash on startup
Package: kdenlive Version: 19.12.3-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? trying to run kdenlive * What exactly did you do (or not do) that was effective (or ineffective)? typed kdenlive at the bash prompt. * What was the outcome of this action? run aborted * What outcome did you expect instead? I expected kdenlive to run as normal *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kdenlive depends on: ii ffmpeg 7:4.2.2-1+b1 ii kded5 5.62.0-1+b1 ii kdenlive-data 19.12.3-1 ii kinit 5.62.0-1+b1 ii kio5.62.1-2+b1 ii libc6 2.30-4 ii libkf5archive5 5.62.0-1 ii libkf5bookmarks5 5.62.0-1+b1 ii libkf5completion5 5.62.0-1+b1 ii libkf5configcore5 5.62.0-1+b1 ii libkf5configgui5 5.62.0-1+b1 ii libkf5configwidgets5 5.62.0-1+b1 ii libkf5coreaddons5 5.62.0-1 ii libkf5crash5 5.62.0-1+b1 ii libkf5dbusaddons5 5.62.0-1 ii libkf5declarative5 5.62.0-1+b2 ii libkf5filemetadata35.62.0-1+b1 ii libkf5guiaddons5 5.62.0-2 ii libkf5i18n55.62.0-1 ii libkf5iconthemes5 5.62.0-1+b1 ii libkf5itemviews5 5.62.0-1+b1 ii libkf5jobwidgets5 5.62.0-1+b1 ii libkf5kiocore5 5.62.1-2+b1 ii libkf5kiofilewidgets5 5.62.1-2+b1 ii libkf5kiowidgets5 5.62.1-2+b1 ii libkf5newstuff55.62.0-1+b1 ii libkf5notifications5 5.62.0-1+b1 ii libkf5notifyconfig55.62.0-1+b1 ii libkf5purpose-bin 5.62.0-2+b1 ii libkf5purpose5 5.62.0-2+b1 ii libkf5service-bin 5.62.0-1 ii libkf5service5 5.62.0-1 ii libkf5solid5 5.62.0-2 ii libkf5widgetsaddons5 5.62.0-1+b1 ii libkf5xmlgui5 5.62.0-1+b1 ii libmlt++3 6.20.0-2+b1 ii libmlt66.20.0-2+b1 ii libqt5concurrent5 5.12.5+dfsg-9 ii libqt5core5a 5.12.5+dfsg-9 ii libqt5dbus55.12.5+dfsg-9 ii libqt5gui5 5.12.5+dfsg-9 ii libqt5multimedia5 5.12.5-1+b1 ii libqt5network5 5.12.5+dfsg-9 ii libqt5qml5 5.12.5-5 ii libqt5quick5 5.12.5-5 ii libqt5quickwidgets55.12.5-5 ii libqt5svg5 5.12.5-2 ii libqt5webkit5 5.212.0~alpha4-1 ii libqt5widgets5 5.12.5+dfsg-9 ii libqt5xml5 5.12.5+dfsg-9 ii librttr-core0.9.6 0.9.6+dfsg1-3 ii libstdc++6 10-20200324-1 ii melt 6.20.0-2+b1 ii qml-module-qtgraphicaleffects 5.12.5-2+b1 ii qml-module-qtqml-models2 5.12.5-5 ii qml-module-qtquick-controls5.12.5-1+b1 ii qml-module-qtquick-controls2 5.12.5+dfsg-2+b1 ii qml-module-qtquick-dialogs 5.12.5-1+b1 ii qml-module-qtquick-layouts 5.12.5-5 ii qml-module-qtquick-window2 5.12.5-5 ii qml-module-qtquick25.12.5-5 Versions of packages kdenlive recommends: ii breeze-icon-theme 4:5.62.0-1 pn dvdauthor pn dvgrab ii frei0r-plugins 1.7.0-1 pn genisoimage pn oxygen-icon-theme pn recordmydesktop ii swh-plugins0.4.17-2 Versions of packages kdenlive suggests: ii khelpcenter 4:18.04.0-1+b1 -- no debconf information WARNING : Fails to parse "jack" "jackrack" is blacklisted "resample" is blacklisted "qtext" is blacklisted "videostab" is blacklisted "videostab2" is blacklisted "gtkrescale" is blacklisted "motion_est" is blacklisted WARNING : Fails to parse "crop_detect" "frei0r.3dflippo" is blacklisted "frei0r.bluescreen0r" is blacklisted "frei0r.bw0r" is blacklisted "frei0r.gamma" is blacklisted "frei0r.invert0r" is blacklisted "frei0r.rgbsplit0r" is blacklisted "frei0r.transparency" is blacklisted "frei0r.vertigo" is blacklisted WARNING : Fails to parse "deinterlace" "burningtv" is blacklisted WARNING : Fails to parse "telecide" "rgblut" is blacklisted "spot_remover" is
Bug#955692: marked as done (freeboard: FTBFS: dpkg-query: no path found matching pattern /usr/lib/nodejs/knockout/build/output/knockout-latest.js)
Your message dated Sat, 04 Apr 2020 12:18:30 + with message-id and subject line Bug#955692: fixed in freeboard 1.1.0+dfsg.1-4 has caused the Debian Bug report #955692, regarding freeboard: FTBFS: dpkg-query: no path found matching pattern /usr/lib/nodejs/knockout/build/output/knockout-latest.js 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.) -- 955692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955692 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: freeboard Version: 1.1.0+dfsg.1-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200402 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules binary > dh binary --with linktree,apache2 >dh_testroot >dh_prep >dh_installdirs >dh_install >dh_apache2 >dh_installdocs >dh_installchangelogs >dh_perl >dh_link >dh_linktree > dpkg-query: no path found matching pattern > /usr/lib/nodejs/knockout/build/output/knockout-latest.js > dh_linktree: error: dpkg --search -- > /usr/lib/nodejs/knockout/build/output/knockout-latest.js > /usr/share/javascript/caret.js/jquery.caret.js > /usr/share/javascript/codemirror/codemirror.css > /usr/share/javascript/codemirror/codemirror.js > /usr/share/javascript/codemirror/theme/ambiance.css > /usr/share/javascript/headjs/head.js > /usr/share/javascript/jquery-ui/jquery-ui.js > /usr/share/javascript/jquery.sparkline/jquery.sparkline.min.js > /usr/share/javascript/jquery/jquery.js > /usr/share/javascript/raphael/raphael.min.js > /usr/share/javascript/underscore/underscore.js subprocess returned exit > status 1 > make: *** [debian/rules:8: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2020/04/02/freeboard_1.1.0+dfsg.1-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! 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 --- Source: freeboard Source-Version: 1.1.0+dfsg.1-4 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of freeboard, 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 955...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated freeboard 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, 04 Apr 2020 20:06:56 +0800 Source: freeboard Architecture: source Version: 1.1.0+dfsg.1-4 Distribution: unstable Urgency: low Maintainer: Ying-Chun Liu (PaulLiu) Changed-By: Ying-Chun Liu (PaulLiu) Closes: 955692 Changes: freeboard (1.1.0+dfsg.1-4) unstable; urgency=low . * Fix FTBFS for node-knockout (>= 3.4.2-3) (Closes: #955692) Checksums-Sha1: c4bb3c038fe737e5572f3d2eba19539f8200688c 2012 freeboard_1.1.0+dfsg.1-4.dsc 2c08fe5b32fea43ac56ff1deca66e414321be3ab 3580 freeboard_1.1.0+dfsg.1-4.debian.tar.xz a096b7b2b19adfb2377935d7f0149936907013ab 7404 freeboard_1.1.0+dfsg.1-4_source.buildinfo Checksums-Sha256: 5bbb7a0174c11a3270f6b8135b39771cd7ae4b2732c82a56a5496710dbfaf910 2012 freeboard_1.1.0+dfsg.1-4.dsc 4ba27ea575f5fe022794883d1b0938821212a90ea075d0a0fb9b0709d46c89ab 3580 freeboard_1.1.0+dfsg.1-4.debian.tar.xz 79cb5e2b2794b1f328c11070e7100a0be7745faed2d65aa30974f9a425735bc2 7404 freeboard_1.1.0+dfsg.1-4_source.buildinfo Files: 238b6e4e395fef1120801e62b2e64a4d 2012 web optional freeboard_1.1.0+dfsg.1-4.dsc 6566d0b52bdcc335736e28d3275b7bf3 3580 web optional freeboard_1.1.0+dfsg.1-4.debian.tar.xz 5022a7f998b23d4fe9422efd34b2b1fb 7404 web optional freeboard_1.1.0+dfsg.1-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAl6IeOgTHHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiEowD/wIzYsY1m30gzIkVcS4IH19P+CHJolP
Processed: merge all FTBFS caused by #954681
Processing commands for cont...@bugs.debian.org: > tags 954681 + pending Bug #954681 [src:gcc-9] [gnat-9] crash caused by SOURCE_DATE_EPOCH patch Added tag(s) pending. > reassign 955646 src:gcc-9 Bug #955646 [src:liblog4ada] liblog4ada: FTBFS: gprbuild: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgnatprj.so.7: undefined symbol: system__os_lib__get_os_time_from_string Bug reassigned from package 'src:liblog4ada' to 'src:gcc-9'. No longer marked as found in versions liblog4ada/1.3.1.b6dafb49-2. Ignoring request to alter fixed versions of bug #955646 to the same values previously set > reassign 955647 src:gcc-9 Bug #955647 [src:libxmlezout] libxmlezout: FTBFS: gprbuild: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgnatprj.so.7: undefined symbol: system__os_lib__get_os_time_from_string Bug reassigned from package 'src:libxmlezout' to 'src:gcc-9'. No longer marked as found in versions libxmlezout/1.06.2-2. Ignoring request to alter fixed versions of bug #955647 to the same values previously set > reassign 955653 src:gcc-9 Bug #955653 [src:ahven] ahven: FTBFS: gprbuild: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgnatprj.so.7: undefined symbol: system__os_lib__get_os_time_from_string Bug reassigned from package 'src:ahven' to 'src:gcc-9'. No longer marked as found in versions ahven/2.7-4. Ignoring request to alter fixed versions of bug #955653 to the same values previously set > reassign 955654 src:gcc-9 Bug #955654 [src:adacgi] adacgi: FTBFS: gprbuild: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgnatprj.so.7: undefined symbol: system__os_lib__get_os_time_from_string Bug reassigned from package 'src:adacgi' to 'src:gcc-9'. No longer marked as found in versions adacgi/1.6-24. Ignoring request to alter fixed versions of bug #955654 to the same values previously set > reassign 955658 src:gcc-9 Bug #955658 [src:libalog] libalog: FTBFS: gprbuild: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgnatprj.so.7: undefined symbol: system__os_lib__get_os_time_from_string Bug reassigned from package 'src:libalog' to 'src:gcc-9'. No longer marked as found in versions libalog/0.6.1-2. Ignoring request to alter fixed versions of bug #955658 to the same values previously set > reassign 955667 src:gcc-9 Bug #955667 [src:adabrowse] adabrowse: FTBFS: gprbuild: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgnatprj.so.7: undefined symbol: system__os_lib__get_os_time_from_string Bug reassigned from package 'src:adabrowse' to 'src:gcc-9'. No longer marked as found in versions adabrowse/4.0.3-12. Ignoring request to alter fixed versions of bug #955667 to the same values previously set > reassign 955671 src:gcc-9 Bug #955671 [src:dbusada] dbusada: FTBFS: gprbuild: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgnatprj.so.7: undefined symbol: system__os_lib__get_os_time_from_string Bug reassigned from package 'src:dbusada' to 'src:gcc-9'. No longer marked as found in versions dbusada/0.5.0-3. Ignoring request to alter fixed versions of bug #955671 to the same values previously set > reassign 955681 src:gcc-9 Bug #955681 [src:anet] anet: FTBFS: gprbuild: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgnatprj.so.7: undefined symbol: system__os_lib__get_os_time_from_string Bug reassigned from package 'src:anet' to 'src:gcc-9'. No longer marked as found in versions anet/0.4.2-2. Ignoring request to alter fixed versions of bug #955681 to the same values previously set > reassign 955683 src:gcc-9 Bug #955683 [src:libtexttools] libtexttools: FTBFS: gprbuild: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgnatprj.so.7: undefined symbol: system__os_lib__get_os_time_from_string Bug reassigned from package 'src:libtexttools' to 'src:gcc-9'. No longer marked as found in versions libtexttools/2.1.0-16. Ignoring request to alter fixed versions of bug #955683 to the same values previously set > reassign 955688 src:gcc-9 Bug #955688 [src:libflorist] libflorist: FTBFS: gprbuild: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgnatprj.so.7: undefined symbol: system__os_lib__get_os_time_from_string Bug reassigned from package 'src:libflorist' to 'src:gcc-9'. No longer marked as found in versions libflorist/2017-7. Ignoring request to alter fixed versions of bug #955688 to the same values previously set > reassign 955691 src:gcc-9 Bug #955691 [src:pcscada] pcscada: FTBFS: gprbuild: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgnatprj.so.7: undefined symbol: system__os_lib__get_os_time_from_string Bug reassigned from package 'src:pcscada' to 'src:gcc-9'. No longer marked as found in versions pcscada/0.7.5-2. Ignoring request to alter fixed versions of bug #955691 to the same values previously set > # So that the merges are possible > affects 954681 = Bug #954681 [src:gcc-9] [gnat-9] crash caused by SOURCE_DATE_EPOCH patch Removed indication that 954681 affects gprbuild > merge 954681 955646 955647 955653 955654 955658 955667 955671 955681 955683 > 955685 955688 955691 955693 Bug
Bug#955677: marked as done (node-tippex: FTBFS: build-dependency not installable: rollup (< 1.0.0~))
Your message dated Sat, 04 Apr 2020 12:03:42 + with message-id and subject line Bug#955677: fixed in node-tippex 3.0.0+ds-5 has caused the Debian Bug report #955677, regarding node-tippex: FTBFS: build-dependency not installable: rollup (< 1.0.0~) 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.) -- 955677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955677 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-tippex Version: 3.0.0+ds-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200402 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 12), mocha, node-console-group, > node-rollup-plugin-buble, node-rollup-plugin-node-resolve, > node-source-map-support, pkg-js-tools (>= 0.9.16~), rollup (<< 1.0.0~), > build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 12), mocha, node-console-group, > node-rollup-plugin-buble, node-rollup-plugin-node-resolve, > node-source-map-support, pkg-js-tools (>= 0.9.16~), rollup (<< 1.0.0~), > build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [463 B] > Get:5 copy:/<>/apt_archive ./ Packages [537 B] > Fetched 1957 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: rollup (< 1.0.0~) but it is not > going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2020/04/02/node-tippex_3.0.0+ds-4_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 --- Source: node-tippex Source-Version: 3.0.0+ds-5 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of node-tippex, 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 955...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-tippex 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, 04 Apr 2020 13:40:37 +0200 Source: node-tippex Architecture: source Version: 3.0.0+ds-5 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 955677 Changes: node-tippex (3.0.0+ds-5) unstable; urgency=medium . * Team upload . [ Pirate Praveen ] * Update build depends to build with rollup 1.x (Closes: #955677) . [ Xavier Guimard ] * Declare compliance with policy 4.5.0 * Add debian/gbp.conf Checksums-Sha1:
Processed (with 3 errors): avoid duplicate FTBFS reports
Processing commands for cont...@bugs.debian.org:
> reassign 955685 src:gcc-9
Bug #955685 [src:libncursesada] libncursesada: FTBFS: configure: error: No
usable Ada compiler found
Bug reassigned from package 'src:libncursesada' to 'src:gcc-9'.
No longer marked as found in versions libncursesada/6.1.20180127-5.
Ignoring request to alter fixed versions of bug #955685 to the same values
previously set
> reassign 955693 src:gcc-9
Bug #955693 [src:dh-ada-library] dh-ada-library: FTBFS: error:
"dh_ada_library.adb" must be recompiled ("s-os_lib.ads" has been modified)
Bug reassigned from package 'src:dh-ada-library' to 'src:gcc-9'.
No longer marked as found in versions dh-ada-library/6.19.
Ignoring request to alter fixed versions of bug #955693 to the same values
previously set
> merge 955685 955693 954681
Bug #955685 [src:gcc-9] libncursesada: FTBFS: configure: error: No usable Ada
compiler found
Unable to merge bugs because:
affects of #954681 is 'gprbuild' not ''
Failed to merge 955685: Did not alter merged bugs.
> tags 954681 +pending
Failed to alter tags of Bug 954681: failed to get lock on
/srv/bugs.debian.org/spool/lock/954681 -- Unable to lock
/srv/bugs.debian.org/spool/lock/954681 Resource temporarily unavailable.
Unable to lock /srv/bugs.debian.org/spool/lock/954681 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/954681 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/954681 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/954681 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/954681 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/954681 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/954681 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/954681 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/954681 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.
> affects 954681 + ada-reference-manual ghdl music123 topal adasockets plplot
> libxmlada gprbuild dh-ada-library adacgi libaunit libflorist libgmpada
> libgtkada libncursesada libtexttools ahven dbusada libalog pcscada anet
> libtemplates-parser libgnatcoll libgnatcoll-bindings libgnatcoll-db
> libxmlezout liblog4ada asis adabrowse adacontrol libaws gnat-gps
Failed to mark 954681 as affecting package(s): failed to get lock on
/srv/bugs.debian.org/spool/lock/954681 -- Unable to lock
/srv/bugs.debian.org/spool/lock/954681 Resource temporarily unavailable.
Unable to lock /srv/bugs.debian.org/spool/lock/954681 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/954681 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/954681 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/954681 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/954681 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/954681 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/954681 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/954681 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/954681 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
954681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954681
955685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955685
955693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#954552: marked as done (nn: FTBFS: term.c:29:10: fatal error: stropts.h: No such file or directory)
Your message dated Sat, 04 Apr 2020 11:48:28 + with message-id and subject line Bug#954552: fixed in nn 6.7.3-11 has caused the Debian Bug report #954552, regarding nn: FTBFS: term.c:29:10: fatal error: stropts.h: No such file or directory 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.) -- 954552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954552 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nn Version: 6.7.3-10 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200321 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely due to the upgrade to glibc 2.30. >From https://lists.gnu.org/archive/html/info-gnu/2019-08/msg0.html: > * The obsolete and never-implemented XSI STREAMS header files > and have been removed. Relevant part (hopefully): > cc -Iconf -O2 -fno-strength-reduce -fomit-frame-pointer -pipe -O2 -Wdate-time > -D_FORTIFY_SOURCE=2 -c -o term.o term.c > term.c:29:10: fatal error: stropts.h: No such file or directory >29 | #include > | ^~~ > compilation terminated. > make[2]: *** [: term.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/03/21/nn_6.7.3-10_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 --- Source: nn Source-Version: 6.7.3-11 Done: Cord Beermann We believe that the bug you reported is fixed in the latest version of nn, 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 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cord Beermann (supplier of updated nn 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, 04 Apr 2020 12:58:38 +0200 Source: nn Architecture: source Version: 6.7.3-11 Distribution: unstable Urgency: medium Maintainer: Cord Beermann Changed-By: Cord Beermann Closes: 954552 Changes: nn (6.7.3-11) unstable; urgency=medium . * Rebuild package + Bump Standard to 4.5.0 - Rules-Requires-Root: no + Split patches to separate files + Don't install unneeded manpages + Reworked copyright-file, but abusing lintian-ignores. + Fix FTBFS with hardening * Fix FTBFS with missing stropts.h in glibc 2.30 (closes: #954552) Checksums-Sha1: a39770496b7fde60b07f7234f1aafa6f05d2afbe 1678 nn_6.7.3-11.dsc f8ad7b34b7758e0879dd08c7d9dac9fc9c935b41 29896 nn_6.7.3-11.debian.tar.xz a93ded22b2bd18992ee60adb617ad20f35a86746 5655 nn_6.7.3-11_amd64.buildinfo Checksums-Sha256: 43889d495f1ffe6fba15d797279fe5c724f65239d16694ac9f1f70b6cbdb4700 1678 nn_6.7.3-11.dsc c6d43f4dd0f1c3991a64a2f402e42082dd007a8c7aafe0866103b043f0741c88 29896 nn_6.7.3-11.debian.tar.xz efbdc6b5c526aa7bb2af0df160b3956b06e309e1b7d917c16692f9353a083b95 5655 nn_6.7.3-11_amd64.buildinfo Files: 7b113098373a378f9e64018b1ee1d75f 1678 news optional nn_6.7.3-11.dsc a47c7d38c0fb6fcc685f497d21db951f 29896 news optional nn_6.7.3-11.debian.tar.xz 4dcf8fa3480bd8aacefd1b159350cc10 5655 news optional nn_6.7.3-11_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEEs9WBfeo2KZ4m5tTmFYdLSUC/jkFAl6IckcACgkQmFYdLSUC /jlBdBAAiwTxgmWOj+Sak42TRsp224Uz93SvtPMpet6TBvgJI3wiuN9iSP1EYcj8 4UynkJMoDVz9UmgxhCEsa75GNLh2fbCxryIauEjTQ6+AfMGIWHBO9RNBdLZGSWiw jW7y3v4I+CxT2mS7bcvO/4vXZpJ2DmRmiDy2y9/8hgjZl9nQZQHnKW5aPrzWFMtF 0njsnSIywnFLbQ3qoRnVKsrw8fvHNsz08zxBtunqKoKPIZjhkRCI3cXfn6YjZmZF I/JC2qz2KQy7HYOgB9Wf4SLpd6GLIL4PF5gwBh6IjsEGWAonbG9kMpZ+SpP6+2k3 LkddeHgVJ7xVCGh5wNKNozSHbyNQpIUTDj+WsYpWsoVozBRUUf+hCH+7tcvcadkZ FKtT4HHMuT1jFWZTzy/yHXr5TIOR7GIb8fpxo4eCr5loQJrRyCxbKPqIa6Y4QJr5 OkIsD79gTTPl2vjSWwbh9VYR+md9t7LX/2VT2KeMrHssMXhBzUZrQvdNJFPlL/oT Au9m4NHg0u1Td/Ginq+BdrcFh4jYg/ZVJa0FeKRqETgEwfZxdT/PmHn6piPnvy23
Bug#954681: [gnat-9] crash caused by SOURCE_DATE_EPOCH patch
Hello. Commit 2e5e37249f09e54bb62e3ab87508e43ff709a4fb should improve the situation. It reverts the part affecting s-os_lib.adb. A GCC build produces the same checksum for it than 9.3.0-8 in libgnat-9, hopefully making gnat usable again by existing packaged libraries (I don't know how to test this on a porterbox). The remaining part, slightly adapted, passes the regression tests for this specific bug. If all goes well, please lower the severity of this bug, but keep it open as a reminder. * Unless an objection arises, the gcc-10 branch should eventually cherry-pick c1d276b0e2cb60140389aa4c23ac3addb7a77af3. * Ludovic has noticed that the initial error message CONSTRAINT_ERROR : uintp.adb:1959 overflow check failed probably reveals a bug that should be investigated by itself. No time computation is supposed to trigger a range overflow in an unrelated package.
Bug#955596: marked as done (python-h5netcdf: h5py.File needs access mode specified)
Your message dated Sat, 04 Apr 2020 11:33:36 + with message-id and subject line Bug#955596: fixed in python-h5netcdf 0.8.0-1 has caused the Debian Bug report #955596, regarding python-h5netcdf: h5py.File needs access mode specified 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.) -- 955596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-h5netcdf Version: 0.7.1-1 Severity: serious Justification: debci h5py.File opens 'r' by default, so you need to specify other modes such as 'w' if needed e.g. test_optional_netcdf4_attrs[testfile.nc] with h5.File(tmp_local_or_remote_netcdf, 'w') as f: instead of with h5.File(tmp_local_or_remote_netcdf) as f: if needed for writing. -- 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.4.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: python-h5netcdf Source-Version: 0.8.0-1 Done: Drew Parsons We believe that the bug you reported is fixed in the latest version of python-h5netcdf, 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 955...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated python-h5netcdf 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: Sat, 04 Apr 2020 19:14:40 +0800 Source: python-h5netcdf Architecture: source Version: 0.8.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Drew Parsons Closes: 955596 Changes: python-h5netcdf (0.8.0-1) unstable; urgency=medium . * Team upload. * New upstream release. * Standards-Version: 4.5.0 * mark debhelper compatibility with Build-Depends: debhelper-compat (= 12) * debian patch h5py_File_mode.patch fixes a couple more h5py File modes missed in the new release. Closes: #955596. Checksums-Sha1: ff2a2d55e70c359c63b4edadd38f21dfdbbc9516 2249 python-h5netcdf_0.8.0-1.dsc 5b715fa6365f7486e9157fb8fa9ccd4715162ca6 27939 python-h5netcdf_0.8.0.orig.tar.gz 011b8912c07173b9cc80e8d1ea8d4f8bd9bf94bc 5520 python-h5netcdf_0.8.0-1.debian.tar.xz Checksums-Sha256: 54e4c1366a360e32ac502c4ec4cde519fc11367b5dd8397374d10e95953dce38 2249 python-h5netcdf_0.8.0-1.dsc b0df12f4692817cf6d8e2fca95f689e61aa68f2f39aea90fd1790fe5ac8d2cbb 27939 python-h5netcdf_0.8.0.orig.tar.gz e408c1b26a04023acab05722e47c962f1679468e0ab279ee5ca1775e28a9000e 5520 python-h5netcdf_0.8.0-1.debian.tar.xz Files: ac2ca51207d1a0d65b8da4473fade844 2249 python optional python-h5netcdf_0.8.0-1.dsc af2b6d72a33491f9f0a3fb30a5aa4577 27939 python optional python-h5netcdf_0.8.0.orig.tar.gz 8db207efe3def3617bbcc4fbf64acd01 5520 python optional python-h5netcdf_0.8.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAl6IbN0ACgkQVz7x5L1a AfrgxA/9EKp5Zra4kmHYIkMjQP2LQjIN40PXNc7FJb0eqnaS/JNdig0VIRu2tKom G/lziSMN5WJT6b1H1p4xmgNr8RfSr39ueR2xGtE4rsSWFqhsQYQG6bJ+2buwIqDu oycB7q+2RucvwGRPOYJGULrQHaTNDy2h9LwsheKjCvF49tQU9XDqVLqQx+nnG7oC nOnen6LKmEY7By0uizZTA2G6m7X3hHpVOSmh+B9J9cyvyq3C5YzzZaSM5fY2G+lr rcVss4OMN0NmbWbWGeEvi4D2SCA7Sn96PFIAJ7BEP0oswPFSWXPAXw8jGxkKX8oE OMsXZkcVedqTWcB6Hvu50p9RqyJnytLOTck3jIBwExkcsw6Dpme6cX9Pcnvk9kLY u2Mv/ca4QWHFY/bxDq/KSdd1AD9gsBETuiOMhoWmK44jWPRVaTD69dojnvPOYoLi gMw6bb3PXdBeDbKQbsLdQpM86wNvYchQCg4Pk+bMHZU5p9TNjKEMpnkiDSw43Uej xKNyaNBSnlFVlLBveakpk8kMhrWn0tlwTEwmt2VnMk6FHtGeLMkf4+8eE4DZAyKd qKOYNVXRaWeeTZImPH+okpRX5PUnaHTVu6CzVU20m/AnM2iOUGEAxN2MZuClVG65 Qk+VNAuvzghA/R7Z/2RIjxhmvPZY0NiaXotKtBxa4SOGw44tNE0= =pude -END PGP SIGNATURE End Message ---
Bug#955716: marked as done (pegjs -- New upstream version available since 4 years. No human maintainer listed.)
Your message dated Sat, 04 Apr 2020 11:19:12 + with message-id and subject line Bug#955716: fixed in pegjs 0.10.0-1 has caused the Debian Bug report #955716, regarding pegjs -- New upstream version available since 4 years. No human maintainer listed. 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.) -- 955716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955716 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pegjs Severity: serious Dear Maintainer, pegjs seems to be unmaintained, the only human maintainer listed has been removed from Debian, which violates a must criteria in the Debian policy. Debian is way years behind upstream (last release Apr. 2016; the one in Debian was 2012.) It would be great if the JS team could fix that bug or orphan the package so that other people can more easily do the upload of the new version. Thanks for considering. (CC'ing theano maintainers, as they are the only reverse dependency.. Maybe they are interested in ITSing the package ;-) Cheers, -- tobi --- End Message --- --- Begin Message --- Source: pegjs Source-Version: 0.10.0-1 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of pegjs, 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 955...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated pegjs 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, 04 Apr 2020 12:58:52 +0200 Source: pegjs Architecture: source Version: 0.10.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 953505 955716 Changes: pegjs (0.10.0-1) unstable; urgency=medium . * Bump debhelper compatibility level to 12 * Declare compliance with policy 4.5.0 * Add "Rules-Requires-Root: no" * Change section to javascript * Add debian/gbp.conf * Add upstream/metadata * Update VCS fields to salsa * Fix copyright * New upstream version 0.10.0 (Closes: #955716) * Set myself as uploader (Closes: #953505) * refresh patches * Use pkg-js-tools auto install * Install browser files (See: #722488) * Fix homepage * Update lintian overrides Checksums-Sha1: bc2a1ec80b131b5cf9e78fc1b66152c353672348 1990 pegjs_0.10.0-1.dsc 6bb0f291dd5a2ae4c1b2c7fe9282cd7a7036bd22 188813 pegjs_0.10.0.orig.tar.gz 6d2c77b95b6f6f14c5ab481b0f15e1b50e419f42 3972 pegjs_0.10.0-1.debian.tar.xz Checksums-Sha256: 68bfa0749c81f71c2bbb763f2f2625db4c47e198b908c5d9350075ba9e3e25c8 1990 pegjs_0.10.0-1.dsc 96837ce95fe7331bf31adb6ab4def6c6dfb72b5909fce42919919d3e790159be 188813 pegjs_0.10.0.orig.tar.gz 0c128b6f52671fb67f04cf8e007feed06997ae87c4724886ca3cad1188dde62a 3972 pegjs_0.10.0-1.debian.tar.xz Files: 0eeeb6926ccae657634658f357534bb8 1990 javascript optional pegjs_0.10.0-1.dsc d1f2833ddcd4f32a9a74626256599274 188813 javascript optional pegjs_0.10.0.orig.tar.gz 4d5be3583b9b348b12251ac553559ade 3972 javascript optional pegjs_0.10.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl6Iam4ACgkQ9tdMp8mZ 7ukUpg//YSA+KJ4DOmaVqV+DpfgYg33Eo3WgUZUgqDXS1v0zJCDK8VUZkaIjdo69 OlOuG9oje6x4W5AvruCDqri/uDm81NZYptw8PcNgszXBNTpnFcB3PhXFTXPkrHpu nQUdvpHr2M4ly6xi2RVMvGq9/psHqgudFs5R4IAI/7oQ13tjDnXJu1ZVYHIMnbyE qY4s3pGkHA8r/XxX2Y5K3BrZAY9xzVQwpzQPITrzYckPDQs6GQCH2Z7r1p1nDie0 QRP3r+Kti6Hch4rX5VRIgr4wKLDHXt/hDseE12rpM/aDN663u59aSi0LD6czHrxd MsZyaxDVaRV2said7D65KBTQ718vH/sjNIdB9eJCX7Mjozo/uNvz4oRy5cFpgCz9 1fKtBFQyu+DARHiDYdVimzUCRIYDKPxAZV6ilgAFVj1iAfmaHvN1CcV7JfdnfDzF jRc1ncohumP1ty7pNDxDkWzIgVGoQx5btOOHK+CbuCMj4e00BpblOgBXagf+EFLV +qrTh9+HYRiWaON6NfJSwRK5W1KYAYg0jOMgZFL/G4Pq4jTENXKBXzYglBhXi5DQ 9PEmt/aFkeK/8j18UKtKHQIl1sswAAXZ+8YRlW8cEyoYwHavormYoYEOhehrrsHq D0+Ic1gVUsPw69IR0UrCCQc3xdJGsW5jPoZhQk9oFUZ9wh7srOc= =JbSE -END PGP SIGNATURE End Message ---
Processed: Bug#955716 marked as pending in pegjs
Processing control commands: > tag -1 pending Bug #955716 [src:pegjs] pegjs -- New upstream version available since 4 years. No human maintainer listed. Added tag(s) pending. -- 955716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955716 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955716: marked as pending in pegjs
Control: tag -1 pending Hello, Bug #955716 in pegjs reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/pegjs/-/commit/98630baa0bb4201593a8ad0fbbcd02177a3a015f Set myself as uploader Closes: #955716 (this message was generated automatically) -- Greetings https://bugs.debian.org/955716
Bug#955664: marked as done (lemonldap-ng: FTBFS: failed test exit code 2)
Your message dated Sat, 04 Apr 2020 10:48:55 + with message-id and subject line Bug#955664: fixed in lemonldap-ng 2.0.7+ds-5 has caused the Debian Bug report #955664, regarding lemonldap-ng: FTBFS: failed test exit code 2 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.) -- 955664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955664 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lemonldap-ng Version: 2.0.7+ds-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200402 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 '/<>/lemonldap-ng-portal' > PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" > "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', > 'blib/arch')" t/*.t > t/99-pod.t . ok > All tests successful. > Files=11, Tests=189, 1 wallclock secs ( 0.07 usr 0.01 sys + 1.49 cusr > 0.21 csys = 1.78 CPU) > Result: PASS > make[2]: Leaving directory '/<>/lemonldap-ng-common' > t/01-Lemonldap-NG-Handler-Main.t ok > t/02-HTML-template.t ok > Bad logLevel value '', switching to 'info' > t/05-Lemonldap-NG-Handler-Reload.t .. ok > t/03-HTML-forms.t ... ok > # Waiting > t/12-Lemonldap-NG-Handler-Jail.t ok > t/13-Lemonldap-NG-Handler-Fake-Safe.t ... ok > t/50-Lemonldap-NG-Handler-SecureToken.t . ok > t/05-rest-api.t . ok > t/51-Lemonldap-NG-Handler-Zimbra.t .. ok > t/60-Lemonldap-NG-Handler-PSGI.t skipped: Heavy developer > tests > t/61-Lemonldap-NG-Handler-PSGI-Server.t . skipped: Heavy developer > tests > t/62-Lemonldap-NG-Handler-Nginx.t ... skipped: Heavy developer > tests > t/63-Lemonldap-NG-Handler-PSGI-Try.t ok > t/06-rest-api.t . ok > t/64-Lemonldap-NG-Handler-PSGI-DevOps.t . ok > [Fri Apr 3 16:37:13 2020] [LLNG:30976] [error] > Lemonldap::NG::Handler::PSGI::Main: Unable to load configuration: > Lemonldap::NG::Common::Conf::Backends::Timeout loaded. > Get remote configuration (localStorage unavailable). > TIMEOUT > # Waiting > t/07-utf8.t . ok > [Fri Apr 3 16:42:43 2020] [LLNG:30995] [error] test3.example.com not > authorized in token (test1.example.com, test2.example.com, *.example.com) > [Fri Apr 3 16:42:43 2020] [LLNG:30995] [error] Bad service token > t/65-Lemonldap-NG-Handler-Nginx-ServiceToken.t .. ok > [Fri Apr 3 16:42:43 2020] [LLNG:30998] [error] test3.example.com not > authorized in token (test1.example.com, test2.example.com, *.example.com) > [Fri Apr 3 16:42:43 2020] [LLNG:30998] [error] Bad service token > t/65-Lemonldap-NG-Handler-PSGI-ServiceToken.t ... ok > t/66-Lemonldap-NG-Handler-PSGI-wildcard.t ... ok > t/10-save-unchanged-conf.t .. ok > t/67-Lemonldap-NG-Handler-PSGI-vhostoptions.t ... ok > t/68-Lemonldap-NG-Handler-PSGI-Zimbra.t . ok > t/11-save-appCat-changed-conf.t . ok > t/69-Lemonldap-NG-Handler-PSGI-SecureToken.t ok > t/70-Lemonldap-NG-Handler-PSGI-AuthBasic.t .. ok > t/99-pod.t .. ok > All tests successful. > Files=19, Tests=232, 3 wallclock secs ( 0.08 usr 0.02 sys + 2.18 cusr > 0.29 csys = 2.57 CPU) > Result: PASS > make[2]: Leaving directory '/<>/lemonldap-ng-handler' > t/11-save-changed-conf-with-confirmation.t .. ok > t/12-save-changed-conf.t ok > t/14-bad-changes-in-conf.t .. ok > t/15-combination.t .. ok > t/16-cli.t .. ok > t/17-extra2f.t .. ok > t/20-test-coverage.t ok > t/40-sessions.t . ok > t/50-notifications-DBI.t ok > t/50-notifications.t ok > t/60-2ndfa.t ok > t/70-viewer.t ... ok > t/71-viewer-with-no-diff.t .. ok > t/80-attributes.t ... ok > t/90-translations.t . ok > t/99-pod.t .. ok > All tests successful. > Files=23, Tests=4993, 7 wallclock secs ( 0.23 usr 0.03 sys + 5.13 cusr > 0.72 csys = 6.11 CPU) > Result: PASS > make[2]: Leaving directory '/<>/lemonldap-ng-manager' >
Bug#955732: marked as done (issues page of existing projects are broken with 12.8.8 update)
Your message dated Sat, 04 Apr 2020 11:05:55 +
with message-id
and subject line Bug#955732: fixed in gitlab 12.8.8-6
has caused the Debian Bug report #955732,
regarding issues page of existing projects are broken with 12.8.8 update
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.)
--
955732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955732
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 12.8.8-5+fto10+2
Severity: grave
production.log has this and the issues page gives 500.
ActionView::Template::Error (undefined local variable or method
`attributes_changed_
by_setter' for #
Did you mean? attribute_change):
2:
3: %aside.issues-bulk-update.js-right-sidebar.right-sidebar{
"aria-live" => "pol
ite", data: { 'signed-in': current_user.present? } }
4: .issuable-sidebar.hidden
5: = form_tag [:bulk_update, @project.namespace.becomes(Namespace),
@project, type], method: :post, class: "bulk-update" do
6: .block.issuable-sidebar-header
7: .filter-item.inline.update-issues-btn.float-left
8: = button_tag "Update all", class: "btn update-selected-issues
btn-info", disabled: true
config/initializers/active_record_becomes.rb:22:in `becomes'
app/views/shared/issuable/_bulk_update_sidebar.html.haml:5
app/views/projects/issues/index.html.haml:16
app/controllers/application_controller.rb:122:in `render'
app/controllers/application_controller.rb:478:in `set_current_admin'
lib/gitlab/session.rb:11:in `with_session'
app/controllers/application_controller.rb:469:in `set_session_storage'
--- End Message ---
--- Begin Message ---
Source: gitlab
Source-Version: 12.8.8-6
Done: Pirate Praveen
We believe that the bug you reported is fixed in the latest version of
gitlab, 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 955...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pirate Praveen (supplier of updated gitlab 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, 04 Apr 2020 16:11:16 +0530
Source: gitlab
Architecture: source
Version: 12.8.8-6
Distribution: experimental
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
Changed-By: Pirate Praveen
Closes: 955732
Changes:
gitlab (12.8.8-6) experimental; urgency=medium
.
* Start nginx after letsencrypt configuration
* Drop dependency on libjs-pdf (not needed anymore)
* Remove obsolete initializer: active_record_becomes.rb (Closes: #955732)
Checksums-Sha1:
144057bc6173afd2d5439bb1d8e3fc9ffdb9525e 3827 gitlab_12.8.8-6.dsc
2fa2b7f9bdbe3c89171ff4e7f46da35d01d08c06 84412 gitlab_12.8.8-6.debian.tar.xz
518b1e077b5277fba7c41fdf23c336864c27f0d9 8923 gitlab_12.8.8-6_amd64.buildinfo
Checksums-Sha256:
eea7aeeaa6c1df60b80a03329e5e997a215ff2154c8535cd4ea902624a3dbd16 3827
gitlab_12.8.8-6.dsc
a784cec7f41a6898d9f6dae920170fffb5438578f3913e92b42771400d11ae93 84412
gitlab_12.8.8-6.debian.tar.xz
0f9b571e75cffc6783afc68c56c1f4c551a4ddde6872f33fcd08cd8e9219c7ac 8923
gitlab_12.8.8-6_amd64.buildinfo
Files:
6972e6ae67c5706a2b2c8c82d50f4fab 3827 net optional gitlab_12.8.8-6.dsc
776011538a7cc2ae4f9fccf67487659a 84412 net optional
gitlab_12.8.8-6.debian.tar.xz
4a60d6c975f4a9966aa9fd2f5596cb56 8923 net optional
gitlab_12.8.8-6_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEE0whj4mAg5UP0cZqDj1PgGTspS3UFAl6IZcQACgkQj1PgGTsp
S3Vg9A//ZZ0y6ADiRaNjQnZv0mAVE1269BTxCVJgN+/ikPlvtBBX+ADUbwNcUIs1
egfeYvsPvFwTylyznGW4rksgCaLnpQ0+vF5JA/FC3I7B7v0Nox58VMxCiVgUJ0mi
rkpFkHp2aMxmpgWKW2UgkuBcyUWt9+Zgg5JbCPrEzHQnB4LYi67YMUc14Fu9C6TY
YcYaR12Cc7W01cYm8pcGyD5byigSyfL8QUVKUPpoCsAoCGL2fn5pLSZ+X29DfMj6
NPHqh2sCJWjFUrSc6305Ig7PnijNsbUTDV5vk2yajrnIwuaCGRV4nd52tHv3b8Fy
K3vjSF8YtJ3Aa/iZEKBXg8qUzx3G9+pXy2djU+PsmqOsn6pOfuNrfcWue4KiXMBE
OXaQm/bPIHSDVgsIzKopICy+Y8LGZMb+16jPeHVgccKRiT2RchSw8W6Qgdqklb4T
Om/7jZaV24Y1fmukmqMxse4bBjd+iIY/6+HZNZwldap6J6uRWlOMRbr2NheH8ZK2
EVcva+tQFz4kEZRwedTUu2irVnLdpKSnp808X8wK6JjrjNA+Vt42vgDvdlzhtnpo
5BEcMWB+4n0WJfhoBQY8KaMvJ8cj3nXK24ky0FTOIOt0b52SvBq7I61/aW2nuv64
osNkeYjWN1WoXRvo7u3x2bHC4I2o8wKP/EbBt8PQH8nDQE9o3T4=
=E9P0
-END PGP SIGNATURE End Message ---
Processed: affects 937400
Processing commands for cont...@bugs.debian.org: > affects 937400 - src:coccinelle Bug #937400 [src:pycaml] pycaml: Python2 removal in sid/bullseye Removed indication that 937400 affects src:coccinelle > thanks Stopping processing here. Please contact me if you need assistance. -- 937400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937400 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954681: [gnat-9] crash caused by SOURCE_DATE_EPOCH patch
On 4/3/20 9:47 PM, Nicolas Boulenguez wrote: > Package: src:gcc-9 > Followup-For: Bug #954681 > Control: reopen -1 > > Hello. > > The initial symptom is cured, but the fix lets > debian/patches/ada-lib-info-source-date-epoch.diff modify > gcc/ada/libgnat/s-os_lib.ad[bs]. > > This invalidates the checksums embedded in the .ali files of > libgnat-9, causing a failure in all Ada compilations involving > packaged dependencies. Especially, all run time tests for packaged > libraries fail. > > Ludovic suggests to revert the fix (commit > c1d276b0e2cb60140389aa4c23ac3addb7a77af3 )in the gcc-9 branch. > > I suggest to cherry-pick the commit in the gcc-10 branch, so that it > is part of the future gnat-10 transition. > > Matthias, do you agree with these two actions? > > Then, we will search for a less intrusive work-around for this bug in > gcc-9. soounds fine. Please note that I also see gnat cross build failures on arm64. I'll check if this is related.
Processed: fix fixed version
Processing commands for cont...@bugs.debian.org:
> fixed 955684 0.8.0-2
Bug #955684 {Done: Pirate Praveen }
[src:ruby-fakeredis] ruby-fakeredis: FTBFS: ERROR: Test "ruby2.7" failed:
ArgumentError: invalid value for Float(): "Infinity"
Marked as fixed in versions ruby-fakeredis/0.8.0-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
955684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#955732: issues page of existing projects are broken with 12.8.8 update
Package: gitlab
Version: 12.8.8-5+fto10+2
Severity: grave
production.log has this and the issues page gives 500.
ActionView::Template::Error (undefined local variable or method
`attributes_changed_
by_setter' for #
Did you mean? attribute_change):
2:
3: %aside.issues-bulk-update.js-right-sidebar.right-sidebar{
"aria-live" => "pol
ite", data: { 'signed-in': current_user.present? } }
4: .issuable-sidebar.hidden
5: = form_tag [:bulk_update, @project.namespace.becomes(Namespace),
@project, type], method: :post, class: "bulk-update" do
6: .block.issuable-sidebar-header
7: .filter-item.inline.update-issues-btn.float-left
8: = button_tag "Update all", class: "btn update-selected-issues
btn-info", disabled: true
config/initializers/active_record_becomes.rb:22:in `becomes'
app/views/shared/issuable/_bulk_update_sidebar.html.haml:5
app/views/projects/issues/index.html.haml:16
app/controllers/application_controller.rb:122:in `render'
app/controllers/application_controller.rb:478:in `set_current_admin'
lib/gitlab/session.rb:11:in `with_session'
app/controllers/application_controller.rb:469:in `set_session_storage'
Bug#955595: marked as done (python-fabio: h5py.File needs access mode specified)
Your message dated Sat, 04 Apr 2020 09:48:52 +
with message-id
and subject line Bug#955595: fixed in python-fabio 0.10.0+dfsg-1
has caused the Debian Bug report #955595,
regarding python-fabio: h5py.File needs access mode specified
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.)
--
955595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955595
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-fabio
Version: 0.9.0+dfsg-4
Severity: serious
Justification: debci
h5py.File opens in 'r' mode by default. So you need to specify 'w' or
other if needed to write, etc.
e.g. /usr/lib/python3/dist-packages/fabio/nexus.py, line 140
self.h5 = h5py.File(self.filename.split("::")[0], 'w')
instead of
self.h5 = h5py.File(self.filename.split("::")[0])
-- 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.4.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: python-fabio
Source-Version: 0.10.0+dfsg-1
Done: =?utf-8?q?Picca_Fr=C3=A9d=C3=A9ric-Emmanuel?=
We believe that the bug you reported is fixed in the latest version of
python-fabio, 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 955...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel (supplier of updated python-fabio
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, 04 Apr 2020 11:26:33 +0200
Source: python-fabio
Architecture: source
Version: 0.10.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Picca Frédéric-Emmanuel
Closes: 888092 955595
Changes:
python-fabio (0.10.0+dfsg-1) unstable; urgency=medium
.
* New upstream version 0.10.0+dfsg (Closes: #955595)
* d/t/control: using -v during test (Closes: #888092)
Checksums-Sha1:
256f7cf067c6c02786c824e292954e84035199a9 2930 python-fabio_0.10.0+dfsg-1.dsc
8f3e50c87326533bf32f610f769e10b7e90bdaa1 713364
python-fabio_0.10.0+dfsg.orig.tar.xz
4fd5fb96d1f54d675888d63436dd11e8818229c5 8196
python-fabio_0.10.0+dfsg-1.debian.tar.xz
Checksums-Sha256:
4dd0c5fe84c4c992fdab9028c266cb2b7876fa99490e4d115afb21200e0150b9 2930
python-fabio_0.10.0+dfsg-1.dsc
c22a835591cbfe484ac1b622a69c25363c01e2deed7d3a1c614a09ae9ff007b6 713364
python-fabio_0.10.0+dfsg.orig.tar.xz
4814bfc5f145dcd24a7fb5e4d123fbdcb4a05062779a5aeb7177482117b1368d 8196
python-fabio_0.10.0+dfsg-1.debian.tar.xz
Files:
56ad756465294d9d8135e9188267c21b 2930 science optional
python-fabio_0.10.0+dfsg-1.dsc
bdaf3aa1d4b7d5b93c48f4268594aa8b 713364 science optional
python-fabio_0.10.0+dfsg.orig.tar.xz
1880e520d89b0e7ea650f456f10a5739 8196 science optional
python-fabio_0.10.0+dfsg-1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQJFBAEBCgAvFiEE2bRTt5m4gw2UXmoKW/VOXhK5ALsFAl6IU0oRHHBpY2NhQGRl
Ymlhbi5vcmcACgkQW/VOXhK5ALszpg//TTSiitxLFIrFd+LaKSHOGq6+bD/hGcU5
AV/PtmHwoIjPpOPEX1lmIfFcGl+EkWJwMENuEnJ4vX6YOU4qTbc5tza6YOI8/Jzg
hsLtYEbDgR0HpmtpoIcm0sMeCBJ/wCMYVgli0+IpfgDG95lP5Za0KOs7pTXw/mYh
Y1g5glucKQ6SgXHQCinGa7xciW6oroz8rZGWWIipMAd92bZDlf/HYm0K3ZfUHVt5
bPM+1v7q48zeMGf65b31cJv/4hsZDcXhir6/07EI3Sr7ClSfyrlICu7Z3tDhO2tz
PWtslQ1QpCD+3ZKZN6rF6oXd3bQAxuggEuCKLmCR865tpacxpia2GOUK6fHh1VWS
3lW2Xj0eLIWc0g5PWNr6fmmv5xhoNyvpBDdVHzInvA7eHimN3S8iMZPZ5IhuLTSG
f+/TOXWeYq6aI+yaRSN0T1WX/aJX1gjwp3fPkCMDSZGuhD/j+6Rs7zeLjw2DK1ud
HdB8bYvVxm0DWVc/ydQGgEPt/NT6BfHV1tJd0ccwhYWy0m2i5d3x4bC70hvUX/q8
97by/K8C8hEnMwtvqZ5Dody94MJSKGABdfEst2a8S0Q764JM5F6UPujyKXDMrLWe
26cfxqgCznc6RUOU1CQ/D6s/29quCBBaVyKgYyDTIPqLnptrITaxcoquSP6ETRkx
mx0lzbTo4Ec=
=JKOq
-END PGP SIGNATURE End Message ---
Bug#953970: Taking over DPMT (Was: python-boto: autopkgtest failure with Python 3.8 as default)
On 3/30/20 11:44 AM, Andreas Tille wrote: > I wonder whether we should take over python-boto into DPMT maintenance > which would enable commits to Git way more easily. I'd very much be in the favor of this, especially considering the package history. Cheers, Thomas Goirand (zigo)
Bug#936314: marked as done (coccinelle: Python2 removal in sid/bullseye)
Your message dated Sat, 04 Apr 2020 09:18:56 + with message-id and subject line Bug#936314: fixed in coccinelle 1.0.8.deb-1 has caused the Debian Bug report #936314, regarding coccinelle: Python2 removal in sid/bullseye 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.) -- 936314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936314 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:coccinelle Version: 1.0.4.deb-4 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:coccinelle If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: coccinelle Source-Version: 1.0.8.deb-1 Done: Ralf Treinen We believe that the bug you reported is fixed in the latest version of coccinelle, 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 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ralf Treinen (supplier of updated coccinelle 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: Sat, 04 Apr 2020 10:37:51 +0200 Source: coccinelle Architecture: source Version: 1.0.8.deb-1 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Ralf Treinen Closes: 885267 886679 936314 952461 Changes: coccinelle (1.0.8.deb-1) unstable; urgency=medium . * Team upload . [ Emmanuel Arias ] * New upstream version 1.0.8.deb * New Maintainer (Closes: #886679) - Add myself to Uploaders field on d/control * Update d/control file - Bump debhelper to debhelper-compat (=12) * Remove d/compat * Run wrap-and-sort * Bump Standards-Versions to 4.4.1 * Update no-bundles.patch * Remove unnecessary line on d/gbp.conf * Apply patch to remove pygtk dependencies (Closes: #885267). * d/patches: Fix no-bundles.diff patch. * d/salsa-ci.yml: enable salsa-ci . [ Ralf Treinen ] * Drop patch no-stdcompat.diff, build-depend on libstdcompat-ocaml-dev
Bug#952461: marked as done (coccinelle: build-depend on python instead of python2)
Your message dated Sat, 04 Apr 2020 09:18:56 + with message-id and subject line Bug#952461: fixed in coccinelle 1.0.8.deb-1 has caused the Debian Bug report #952461, regarding coccinelle: build-depend on python instead of python2 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.) -- 952461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: coccinelle Version: 1.0.4.deb-5 Severity: serious tags: patch Hello, your package depends on python instead of python2. Please update the dependency accordingly. (or port to python3 if possible) trivial patch: diff -Nru coccinelle-1.0.4.deb/debian/changelog coccinelle-1.0.4.deb/debian/changelog --- coccinelle-1.0.4.deb/debian/changelog 2020-02-16 16:13:10.0 + +++ coccinelle-1.0.4.deb/debian/changelog 2020-02-24 18:44:58.0 + @@ -1,3 +1,9 @@ +coccinelle (1.0.4.deb-5.1) unstable; urgency=medium + + * Depend on python2 (Closes: #-1) + + -- Gianfranco Costamagna Mon, 24 Feb 2020 19:44:58 +0100 + coccinelle (1.0.4.deb-5) unstable; urgency=medium * Team upload diff -Nru coccinelle-1.0.4.deb/debian/control coccinelle-1.0.4.deb/debian/control --- coccinelle-1.0.4.deb/debian/control 2020-02-16 16:13:10.0 + +++ coccinelle-1.0.4.deb/debian/control 2020-02-24 18:43:36.0 + @@ -8,7 +8,7 @@ dh-ocaml (>= 1.0.3~), ocaml-nox (>= 3.11.1-3~), libpycaml-ocaml-dev (>= 0.82-13~), - python (>= 2.6.6-3~), + python2 (>= 2.6.6-3~), menhir (>= 20090204.dfsg), libmenhir-ocaml-dev (>= 20090204.dfsg), ocaml-findlib, --- End Message --- --- Begin Message --- Source: coccinelle Source-Version: 1.0.8.deb-1 Done: Ralf Treinen We believe that the bug you reported is fixed in the latest version of coccinelle, 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 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ralf Treinen (supplier of updated coccinelle 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: Sat, 04 Apr 2020 10:37:51 +0200 Source: coccinelle Architecture: source Version: 1.0.8.deb-1 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Ralf Treinen Closes: 885267 886679 936314 952461 Changes: coccinelle (1.0.8.deb-1) unstable; urgency=medium . * Team upload . [ Emmanuel Arias ] * New upstream version 1.0.8.deb * New Maintainer (Closes: #886679) - Add myself to Uploaders field on d/control * Update d/control file - Bump debhelper to debhelper-compat (=12) * Remove d/compat * Run wrap-and-sort * Bump Standards-Versions to 4.4.1 * Update no-bundles.patch * Remove unnecessary line on d/gbp.conf * Apply patch to remove pygtk dependencies (Closes: #885267). * d/patches: Fix no-bundles.diff patch. * d/salsa-ci.yml: enable salsa-ci . [ Ralf Treinen ] * Drop patch no-stdcompat.diff, build-depend on libstdcompat-ocaml-dev * Create directory usr/lib/coccinelle/python/coccilib * debian/rules: drop --parallel argument to dh which is now the default * Drop override of dh_dwz which is no longer needed * Drop override of dh_clean, put extra files to remove into debian/clean * Dropped some build-dependencies: - dh-autoreconf (not needed with debhelper compat level 12) - libpycaml-ocaml-dev (as indicated by upstream's install.txt) - camlp4 (no longer needed, according to the upstream team) - hevea (we are not building documentation in html format) - latexmk (not needed to build the documentation) - ocaml-best-compilers (which is now purely virtual) * Move texlive-* build-dependencies to Build-Depends-Indep * Dropped some dependencies of the coccinelle binary package as they are no run-time dependencies according to upstream: - libpycaml-ocaml (python2 removal) - python-glade2 (python2 removal) - python-gobject-2 (deprecated) * Bump build-dependency on python to python3, switch dh plugin from python2 to python3 (closes: #936314, #952461) * Simplify build: - in the
Bug#885267: marked as done (coccinelle: Depends on unmaintained pygtk)
Your message dated Sat, 04 Apr 2020 09:18:55 + with message-id and subject line Bug#885267: fixed in coccinelle 1.0.8.deb-1 has caused the Debian Bug report #885267, regarding coccinelle: Depends on unmaintained pygtk 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.) -- 885267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885267 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: coccinelle Version: 1.0.4.deb-3 Severity: important User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject Introspection bindings. For more information on GObject Introspection see [1] and [2]. Please try to do this before the Buster release as we're going to try to remove pygtk this cycle. If you have any question don't hesitate to ask. [1] https://wiki.gnome.org/Projects/GObjectIntrospection [2] https://wiki.gnome.org/Projects/PyGObject On behalf of the Debian GNOME team, Jeremy Bicha --- End Message --- --- Begin Message --- Source: coccinelle Source-Version: 1.0.8.deb-1 Done: Ralf Treinen We believe that the bug you reported is fixed in the latest version of coccinelle, 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 885...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ralf Treinen (supplier of updated coccinelle 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: Sat, 04 Apr 2020 10:37:51 +0200 Source: coccinelle Architecture: source Version: 1.0.8.deb-1 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Ralf Treinen Closes: 885267 886679 936314 952461 Changes: coccinelle (1.0.8.deb-1) unstable; urgency=medium . * Team upload . [ Emmanuel Arias ] * New upstream version 1.0.8.deb * New Maintainer (Closes: #886679) - Add myself to Uploaders field on d/control * Update d/control file - Bump debhelper to debhelper-compat (=12) * Remove d/compat * Run wrap-and-sort * Bump Standards-Versions to 4.4.1 * Update no-bundles.patch * Remove unnecessary line on d/gbp.conf * Apply patch to remove pygtk dependencies (Closes: #885267). * d/patches: Fix no-bundles.diff patch. * d/salsa-ci.yml: enable salsa-ci . [ Ralf Treinen ] * Drop patch no-stdcompat.diff, build-depend on libstdcompat-ocaml-dev * Create directory usr/lib/coccinelle/python/coccilib * debian/rules: drop --parallel argument to dh which is now the default * Drop override of dh_dwz which is no longer needed * Drop override of dh_clean, put extra files to remove into debian/clean * Dropped some build-dependencies: - dh-autoreconf (not needed with debhelper compat level 12) - libpycaml-ocaml-dev (as indicated by upstream's install.txt) - camlp4 (no longer needed, according to the upstream team) - hevea (we are not building documentation in html format) - latexmk (not needed to build the documentation) - ocaml-best-compilers (which is now purely virtual) * Move texlive-* build-dependencies to Build-Depends-Indep * Dropped some dependencies of the coccinelle binary package as they are no run-time dependencies according to upstream: - libpycaml-ocaml (python2 removal) - python-glade2 (python2 removal) - python-gobject-2 (deprecated) * Bump build-dependency on python to python3, switch dh plugin from python2 to python3 (closes: #936314, #952461) * Simplify build: - in the build-indep override, just invoke "$(MAKE) docs/manual pdf" - drop the build-arch override - consequently, drop the patch pdf-docs-build which is no longer useful * Add as-installed test * Adjust doc-base files as documentation is now installed into /usr/share/doc/coccinelle * Standards-Version 4.5.0 (no change) * Set "Multi-Arch: foreign" for coccinelle-doc Checksums-Sha1: 0e7412ad71b342fd7232cc4d66629717811a1cbc 2460 coccinelle_1.0.8.deb-1.dsc 5eb00adab241eb8388088248f08fe455b35b849a 2670961
Bug#955684: marked as done (ruby-fakeredis: FTBFS: ERROR: Test "ruby2.7" failed: ArgumentError: invalid value for Float(): "Infinity")
Your message dated Sat, 04 Apr 2020 14:44:25 +0530 with message-id <10b98q.yxi1mgn65l...@onenetbeyond.org> and subject line fixed in 0.8.0-2 has caused the Debian Bug report #955684, regarding ruby-fakeredis: FTBFS: ERROR: Test "ruby2.7" failed: ArgumentError: invalid value for Float(): "Infinity" 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.) -- 955684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955684 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-fakeredis Version: 0.7.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200402 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > ArgumentError: >invalid value for Float(): "Infinity" > # > /usr/share/rubygems-integration/all/gems/redis-4.1.2/lib/redis.rb:3357:in > `Float' > # > /usr/share/rubygems-integration/all/gems/redis-4.1.2/lib/redis.rb:3357:in > `block in ' > # > /usr/share/rubygems-integration/all/gems/redis-4.1.2/lib/redis/client.rb:129:in > `call' > # > /usr/share/rubygems-integration/all/gems/redis-4.1.2/lib/redis.rb:1602:in > `block in zincrby' > # > /usr/share/rubygems-integration/all/gems/redis-4.1.2/lib/redis.rb:52:in > `block in synchronize' > # /usr/lib/ruby/2.7.0/monitor.rb:202:in `synchronize' > # /usr/lib/ruby/2.7.0/monitor.rb:202:in `mon_synchronize' > # > /usr/share/rubygems-integration/all/gems/redis-4.1.2/lib/redis.rb:52:in > `synchronize' > # > /usr/share/rubygems-integration/all/gems/redis-4.1.2/lib/redis.rb:1601:in > `zincrby' > # ./spec/sorted_sets_spec.rb:139:in `block (2 levels) in > ' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/example.rb:257:in > `instance_exec' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/example.rb:257:in > `block in run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/example.rb:503:in > `block in with_around_and_singleton_context_hooks' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/example.rb:460:in > `block in with_around_example_hooks' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/hooks.rb:472:in > `block in run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/hooks.rb:610:in > `run_around_example_hooks_for' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/hooks.rb:472:in > `run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/example.rb:460:in > `with_around_example_hooks' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/example.rb:503:in > `with_around_and_singleton_context_hooks' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/example.rb:254:in > `run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/example_group.rb:633:in > `block in run_examples' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/example_group.rb:629:in > `map' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/example_group.rb:629:in > `run_examples' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/example_group.rb:595:in > `run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/runner.rb:121:in > `block (3 levels) in run_specs' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/runner.rb:121:in > `map' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/runner.rb:121:in > `block (2 levels) in run_specs' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/configuration.rb:2031:in > `with_suite_hooks' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/runner.rb:116:in > `block in run_specs' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/reporter.rb:74:in > `report' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/runner.rb:115:in > `run_specs' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/runner.rb:89:in > `run' > # >
Bug#955726: kodi: fails to connect to DLNA server
Package: kodi Version: 2:18.6+dfsg1-1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, * What led up to the situation? Updating Kodi to 18.6 * What exactly did you do (or not do) that was effective (or ineffective)? Removing set up DLNA server and trying to connect again * What was the outcome of this action? DLNA server is not available * What outcome did you expect instead? Succesfull connection to DLNA server and playing video \ audio Note: this bug is reported upstream long time ago: https://github.com/xbmc/xbmc/issues/16335 -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_USER Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kodi depends on: ii kodi-bin 2:18.6+dfsg1-1 ii kodi-data 2:18.6+dfsg1-1 Versions of packages kodi recommends: ii kodi-repository-kodi [kodi-repository] 2:18.6+dfsg1-1 ii kodi-visualization-spectrum 3.0.3-1 kodi suggests no packages. -- no debconf information
Bug#809997: emscripten
On Sat, Apr 04, 2020 at 09:13:27AM +0100, Rebecca N. Palmer wrote: > It was left un-updated because upstream started using a patched LLVM, and > packaging that was considered inappropriate and/or too much work. > > Upstream stopped doing that ~6 months ago, so there is currently no obvious > reason for not updating it, but I haven't actually tried to do so. > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809997 > https://github.com/emscripten-core/emscripten/issues/5488 > > Sébastien Jodogne wrote: > > As the package has not been updated for more than 5 years, I fear this > > package should actually be considered as orphaned > > https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging I've *only* fixed importing new upstream version by turning d/get-orig-source into Files-Excludes + debian/missing-sources in https://salsa.debian.org/pkg-llvm-team/emscripten I do not intend to do much more since it would distract me to much from current tasks. Kind regards Andreas. -- http://fam-tille.de
Bug#955727: fotoxx: dcraw is required, but it is not yet a dependency
Source: fotoxx Version: 20.08-1 Severity: grave Justification: renders package unusable When starting the program, it checks if "dcraw" executable is found, and if that it not the case, the program is closed, hence the severity of the bug report. The solution is to add the package "dcraw" to the list of dependencies. A patch is submitted as a MR in salsa. Regards.
Bug#943078: marked as done (fonts-lohit-deva-marathi: Python2 removal in sid/bullseye)
Your message dated Sat, 04 Apr 2020 08:33:53 + with message-id and subject line Bug#943078: fixed in fonts-lohit-deva-marathi 2.94.2-3 has caused the Debian Bug report #943078, regarding fonts-lohit-deva-marathi: Python2 removal in sid/bullseye 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.) -- 943078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943078 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fonts-lohit-deva-marathi Version: 2.94.2-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: fonts-lohit-deva-marathi Source-Version: 2.94.2-3 Done: Kartik Mistry We believe that the bug you reported is fixed in the latest version of fonts-lohit-deva-marathi, 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 943...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kartik Mistry (supplier of updated fonts-lohit-deva-marathi 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: Sat, 04 Apr 2020 12:36:20 +0530 Source: fonts-lohit-deva-marathi Architecture: source Version: 2.94.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Fonts Task Force Changed-By: Kartik Mistry Closes: 943078 Changes: fonts-lohit-deva-marathi (2.94.2-3) unstable; urgency=medium . [ Hideki Yamane ] * Use fontforge-nox * debian/control: + Use fontforge-nox. + Use python3 (Closes: #943078) + Use python3-fontforge. * debian/patches: + Added 0002-specify-to-use-python3.patch . [ Kartik Mistry ] * Added debian/gitlab-ci.yml file. * debian/control: + Updated Standards-Version to 4.5.0 + Switched to debhelper-compat. Checksums-Sha1: c93d2cb1d3d658720c0bf78c54a7b8c5cdecf815 2116 fonts-lohit-deva-marathi_2.94.2-3.dsc f5b0815640daf93fc8927165c33ed78ce01fc774 6848 fonts-lohit-deva-marathi_2.94.2-3.debian.tar.xz Checksums-Sha256: 5d5e0a581fb83fb927f350f4b628c8cee19d756cfa1e6c9ba82a18c66842de73 2116 fonts-lohit-deva-marathi_2.94.2-3.dsc
Bug#954547: sipxtapi: FTBFS: os/linux/OsTaskLinux.cpp:52:19: error: ‘int gettid()’ was declared ‘extern’ and later ‘static’ [-fpermissive]
sipxtapi has no reverse dependencies and a very low popcon (3). So I asked myself: Should it be removed from Debian instead of fixing this bug? (I will check back in 3 months and if the bug is still open, I will request RM for this package. If you disagree, leave a comment here.) -- tobi
Processed: Re: Bug#955656: python-cobra: FTBFS: E ModuleNotFoundError: No module named 'matplotlib'
Processing control commands: > tags -1 help Bug #955656 [src:python-cobra] python-cobra: FTBFS: E ModuleNotFoundError: No module named 'matplotlib' Added tag(s) help. -- 955656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955656: python-cobra: FTBFS: E ModuleNotFoundError: No module named 'matplotlib'
Control: tags -1 help
Hi,
this bug is fixed in Git. Unfortunately there is an issue with python3-libsbml
which prevents successful building:
ERROR collecting test session _
/usr/lib/python3/dist-packages/_pytest/config/__init__.py:440: in
_importconftest
return self._conftestpath2mod[conftestpath]
E KeyError:
local('/build/python-cobra-0.18.0/.pybuild/cpython3_3.7_cobra/build/cobra/test/conftest.py')
During handling of the above exception, another exception occurred:
/usr/lib/python3/dist-packages/_pytest/config/__init__.py:446: in
_importconftest
mod = conftestpath.pyimport()
/usr/lib/python3/dist-packages/py/_path/local.py:701: in pyimport
__import__(modname)
cobra/__init__.py:40: in
from cobra import io
cobra/io/__init__.py:8: in
from cobra.io.sbml import read_sbml_model, write_sbml_model, \
cobra/io/sbml.py:41: in
import libsbml
/usr/lib/python3/dist-packages/libsbml/libsbml.py:22: in
import _libsbml
E ModuleNotFoundError: No module named '_libsbml'
During handling of the above exception, another exception occurred:
/usr/lib/python3/dist-packages/py/_path/common.py:383: in visit
for x in Visitor(fil, rec, ignore, bf, sort).gen(self):
/usr/lib/python3/dist-packages/py/_path/common.py:435: in gen
for p in self.gen(subdir):
/usr/lib/python3/dist-packages/py/_path/common.py:424: in gen
dirs = self.optsort([p for p in entries
/usr/lib/python3/dist-packages/py/_path/common.py:425: in
if p.check(dir=1) and (rec is None or rec(p))])
/usr/lib/python3/dist-packages/_pytest/main.py:667: in _recurse
ihook = self.gethookproxy(dirpath)
/usr/lib/python3/dist-packages/_pytest/main.py:482: in gethookproxy
my_conftestmodules = pm._getconftestmodules(fspath)
/usr/lib/python3/dist-packages/_pytest/config/__init__.py:424: in
_getconftestmodules
mod = self._importconftest(conftestpath.realpath())
/usr/lib/python3/dist-packages/_pytest/config/__init__.py:463: in
_importconftest
raise ConftestImportFailure(conftestpath, sys.exc_info())
E _pytest.config.ConftestImportFailure:
(local('/build/python-cobra-0.18.0/.pybuild/cpython3_3.7_cobra/build/cobra/test/conftest.py'),
(, ModuleNotFoundError("No module named
'_libsbml'"), ))
=== warnings summary ===
Any help is really welcome
Andreas.
--
http://fam-tille.de
Bug#955716: pegjs -- New upstream version available since 4 years. No human maintainer listed.
Source: pegjs Severity: serious Dear Maintainer, pegjs seems to be unmaintained, the only human maintainer listed has been removed from Debian, which violates a must criteria in the Debian policy. Debian is way years behind upstream (last release Apr. 2016; the one in Debian was 2012.) It would be great if the JS team could fix that bug or orphan the package so that other people can more easily do the upload of the new version. Thanks for considering. (CC'ing theano maintainers, as they are the only reverse dependency.. Maybe they are interested in ITSing the package ;-) Cheers, -- tobi
Bug#943020: marked as done (fonts-lohit-deva-nepali: Python2 removal in sid/bullseye)
Your message dated Sat, 04 Apr 2020 07:18:35 + with message-id and subject line Bug#943020: fixed in fonts-lohit-deva-nepali 2.94.2-3 has caused the Debian Bug report #943020, regarding fonts-lohit-deva-nepali: Python2 removal in sid/bullseye 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.) -- 943020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fonts-lohit-deva-nepali Version: 2.94.2-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: fonts-lohit-deva-nepali Source-Version: 2.94.2-3 Done: Kartik Mistry We believe that the bug you reported is fixed in the latest version of fonts-lohit-deva-nepali, 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 943...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kartik Mistry (supplier of updated fonts-lohit-deva-nepali 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: Sat, 04 Apr 2020 12:07:18 +0530 Source: fonts-lohit-deva-nepali Architecture: source Version: 2.94.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Fonts Task Force Changed-By: Kartik Mistry Closes: 943020 Changes: fonts-lohit-deva-nepali (2.94.2-3) unstable; urgency=medium . [ Hideki Yamane ] * Use python3-fontforge (Closes: #943020) * Update Build-Depends to fontforge-nox. . [ Kartik Mistry ] * Added debian/gitlab-ci.yml file. * debian/control: + Updated Standards-Version to 4.5.0 + Switched to debhelper-compat. Checksums-Sha1: 78fd90eb94f6ee5856250c36b0d6db2b83600a39 2105 fonts-lohit-deva-nepali_2.94.2-3.dsc 7076bd740e5f01be2f17efe3af53aa55f08a2694 6456 fonts-lohit-deva-nepali_2.94.2-3.debian.tar.xz Checksums-Sha256: 92bfc8eaa0ce5772ef022d7632cae4f45e02bf1ce26d1e9bdea4727db2a2896a 2105 fonts-lohit-deva-nepali_2.94.2-3.dsc 055073410f5703152e0550dc0015de96df17b4fe5d2579126efcf06cc1bf1254 6456 fonts-lohit-deva-nepali_2.94.2-3.debian.tar.xz Files:
Bug#955679: marked as done (python-geotiepoints: FTBFS: ModuleNotFoundError: No module named 'matplotlib')
Your message dated Sat, 4 Apr 2020 07:53:36 +0100 with message-id <44f5b185-6067-e801-0816-e8a4b9fe7...@zoho.com> and subject line Fixed Re: Bug#955679: python-geotiepoints: FTBFS: ModuleNotFoundError: No module named 'matplotlib' has caused the Debian Bug report #955679, regarding python-geotiepoints: FTBFS: ModuleNotFoundError: No module named 'matplotlib' 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.) -- 955679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-geotiepoints Version: 1.1.8-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200402 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:217: python3.7 setup.py config > Cython will not be used. Use environment variable 'USE_CYTHON=True' to use it > running config > I: pybuild base:217: python3.8 setup.py config > Cython will not be used. Use environment variable 'USE_CYTHON=True' to use it > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:217: /usr/bin/python3.7 setup.py build > Cython will not be used. Use environment variable 'USE_CYTHON=True' to use it > running build > running build_py > creating > /<>/.pybuild/cpython3_3.7_geotiepoints/build/geotiepoints > copying geotiepoints/basic_interpolator.py -> > /<>/.pybuild/cpython3_3.7_geotiepoints/build/geotiepoints > copying geotiepoints/__init__.py -> > /<>/.pybuild/cpython3_3.7_geotiepoints/build/geotiepoints > copying geotiepoints/geointerpolator.py -> > /<>/.pybuild/cpython3_3.7_geotiepoints/build/geotiepoints > copying geotiepoints/modisinterpolator.py -> > /<>/.pybuild/cpython3_3.7_geotiepoints/build/geotiepoints > copying geotiepoints/version.py -> > /<>/.pybuild/cpython3_3.7_geotiepoints/build/geotiepoints > copying geotiepoints/multilinear.py -> > /<>/.pybuild/cpython3_3.7_geotiepoints/build/geotiepoints > copying geotiepoints/interpolator.py -> > /<>/.pybuild/cpython3_3.7_geotiepoints/build/geotiepoints > creating > /<>/.pybuild/cpython3_3.7_geotiepoints/build/geotiepoints/tests > copying geotiepoints/tests/test_geointerpolator.py -> > /<>/.pybuild/cpython3_3.7_geotiepoints/build/geotiepoints/tests > copying geotiepoints/tests/__init__.py -> > /<>/.pybuild/cpython3_3.7_geotiepoints/build/geotiepoints/tests > copying geotiepoints/tests/test_modis.py -> > /<>/.pybuild/cpython3_3.7_geotiepoints/build/geotiepoints/tests > copying geotiepoints/tests/test_multilinear.py -> > /<>/.pybuild/cpython3_3.7_geotiepoints/build/geotiepoints/tests > copying geotiepoints/tests/test_interpolator.py -> > /<>/.pybuild/cpython3_3.7_geotiepoints/build/geotiepoints/tests > copying geotiepoints/tests/test_satelliteinterpolator.py -> > /<>/.pybuild/cpython3_3.7_geotiepoints/build/geotiepoints/tests > copying geotiepoints/tests/test_modisinterpolator.py -> > /<>/.pybuild/cpython3_3.7_geotiepoints/build/geotiepoints/tests > running build_ext > building 'geotiepoints.multilinear_cython' extension > creating build > creating build/temp.linux-x86_64-3.7 > creating build/temp.linux-x86_64-3.7/geotiepoints > 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.7m -I/usr/lib/python3/dist-packages/numpy/core/include > -c geotiepoints/multilinear_cython.c -o > build/temp.linux-x86_64-3.7/geotiepoints/multilinear_cython.o -O3 > In file included from /usr/include/python3.7m/numpy/ndarraytypes.h:1830, > from /usr/include/python3.7m/numpy/ndarrayobject.h:12, > from /usr/include/python3.7m/numpy/arrayobject.h:4, > from geotiepoints/multilinear_cython.c:584: > /usr/include/python3.7m/numpy/npy_1_7_deprecated_api.h:17:2: warning: > #warning "Using deprecated NumPy API, disable it with " "#define > NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp] >17 | #warning "Using deprecated NumPy API, disable it with " \ > | ^~~ > x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions >
Bug#943011: marked as done (fonts-lohit-gujr: Python2 removal in sid/bullseye)
Your message dated Sat, 04 Apr 2020 06:48:36 + with message-id and subject line Bug#943011: fixed in fonts-lohit-gujr 2.92.4-4 has caused the Debian Bug report #943011, regarding fonts-lohit-gujr: Python2 removal in sid/bullseye 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.) -- 943011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fonts-lohit-gujr Version: 2.92.4-3 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: fonts-lohit-gujr Source-Version: 2.92.4-4 Done: Kartik Mistry We believe that the bug you reported is fixed in the latest version of fonts-lohit-gujr, 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 943...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kartik Mistry (supplier of updated fonts-lohit-gujr 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: Sat, 04 Apr 2020 11:33:09 +0530 Source: fonts-lohit-gujr Architecture: source Version: 2.92.4-4 Distribution: unstable Urgency: medium Maintainer: Debian Fonts Task Force Changed-By: Kartik Mistry Closes: 943011 Changes: fonts-lohit-gujr (2.92.4-4) unstable; urgency=medium . [ Hideki Yamane ] * Use python3-fontforge (Closes: #943011) * Update Build-Depends to fontforge-nox. . [ Kartik Mistry ] * Added debian/gitlab-ci.yml file. * debian/control: + Updated Standards-Version to 4.5.0 + Switched to debhelper-compat. Checksums-Sha1: f445edc4c729fe1b77183ac55ec9f057075f37d5 2052 fonts-lohit-gujr_2.92.4-4.dsc a6802dd93c6da1966a8f28dca5168f54408ae26a 7016 fonts-lohit-gujr_2.92.4-4.debian.tar.xz Checksums-Sha256: 03761ce394ec2bd206303b58d1087122d8ac722dbaf3e14e31420ac3d3b34499 2052 fonts-lohit-gujr_2.92.4-4.dsc b4cdae46e4f976fc9a639210423c45ddb673c90b32dbf7227459657d173279f5 7016 fonts-lohit-gujr_2.92.4-4.debian.tar.xz Files: 569cfb4c9e8889d4984e9d2d82a1a4f3 2052 fonts optional fonts-lohit-gujr_2.92.4-4.dsc
Bug#955295: photofilmstrip: incompatible with python 3.8?
Hi, this is already fixed in master branch, see https://github.com/PhotoFilmStrip/PFS/issues/68. I'll trigger a new bugfix release... Thanks, Jens Zitat von Clint Adams (So 29 Mär 2020 15:29:49 CEST): Package: photofilmstrip Version: 3.7.2-2 Severity: serious % photofilmstrip Traceback (most recent call last): File "/usr/bin/photofilmstrip", line 8, in main() File "/usr/lib/python3/dist-packages/photofilmstrip/GUI.py", line 46, in main guiApp.Start() File "/usr/lib/python3/dist-packages/photofilmstrip/AppMixin.py", line 41, in Start self.InitI18N() File "/usr/lib/python3/dist-packages/photofilmstrip/AppMixin.py", line 31, in InitI18N ActionI18N().Execute() File "/usr/lib/python3/dist-packages/photofilmstrip/action/ActionI18N.py", line 43, in Execute lang.install(True) File "/usr/lib/python3.8/gettext.py", line 352, in install for name in allowed & set(names): TypeError: 'bool' object is not iterable % photofilmstrip-cli Traceback (most recent call last): File "/usr/bin/photofilmstrip-cli", line 8, in main() File "/usr/lib/python3/dist-packages/photofilmstrip/CLI.py", line 44, in main exitCode = cliApp.Start() File "/usr/lib/python3/dist-packages/photofilmstrip/AppMixin.py", line 41, in Start self.InitI18N() File "/usr/lib/python3/dist-packages/photofilmstrip/AppMixin.py", line 31, in InitI18N ActionI18N().Execute() File "/usr/lib/python3/dist-packages/photofilmstrip/action/ActionI18N.py", line 43, in Execute lang.install(True) File "/usr/lib/python3.8/gettext.py", line 352, in install for name in allowed & set(names): TypeError: 'bool' object is not iterable
Processed (with 5 errors): reopen with new error message
Processing commands for cont...@bugs.debian.org:
> reopen 954195
Bug #954195 {Done: Laurent Bigonville } [gnome-music]
gnome-music fails to start
'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 gnome-music/3.36.0-2.
> exists in version 3.36.1-1 as well
Unknown command or malformed arguments to command.
> Traceback (most recent call last):
Unknown command or malformed arguments to command.
> File "/usr/lib/python3/dist-packages/gnomemusic/scrobbler.py", line
Unknown command or malformed arguments to command.
> 81, in _new_client_callback
Unknown command or malformed arguments to command.
> manager.call_is_supported_provider(
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.
Please contact me if you need assistance.
--
954195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
