Processed: fixed 957636 in 5.2.0+dfsg1-1, fixed 960258 in 5.2.0+dfsg1-1
Processing commands for cont...@bugs.debian.org:
> fixed 957636 5.2.0+dfsg1-1
Bug #957636 {Done: Alec Leamas } [src:opencpn] opencpn:
ftbfs with GCC-10
Marked as fixed in versions opencpn/5.2.0+dfsg1-1.
> fixed 960258 5.2.0+dfsg1-1
Bug #960258 {Done: Alec Leamas } [src:opencpn] opencpn:
build current sources into unstable/testing
Marked as fixed in versions opencpn/5.2.0+dfsg1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
957636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957636
960258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#958635: marked as done (lsm: Build-Depends on deprecated dh-systemd which is going away)
Your message dated Tue, 15 Sep 2020 04:48:45 + with message-id and subject line Bug#958635: fixed in lsm 1.0.4-2 has caused the Debian Bug report #958635, regarding lsm: Build-Depends on deprecated dh-systemd which is going away 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.) -- 958635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958635 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lsm Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: dh-systemd-removal Hi, your package lsm declares a build dependency on dh-systemd. dh-systemd was merged into debhelper in version 9.20160709 [1] and since stretch, dh-systemd is an empty transitional package. For bullseye we intend to drop this empty transitional package. Once we drop dh-systemd, this bug report will become RC. Please update your package accordingly. The change should be as simple as replacing the build dependency on dh-systemd with a build dependency on debhelper (>= 9.20160709). Regards, Michael [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822670 --- End Message --- --- Begin Message --- Source: lsm Source-Version: 1.0.4-2 Done: Lucas de Castro Borges We believe that the bug you reported is fixed in the latest version of lsm, 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 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lucas de Castro Borges (supplier of updated lsm 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, 13 Sep 2020 15:13:02 + Source: lsm Architecture: source Version: 1.0.4-2 Distribution: unstable Urgency: medium Maintainer: Lucas de Castro Borges Changed-By: Lucas de Castro Borges Closes: 958635 Changes: lsm (1.0.4-2) unstable; urgency=medium . * Updated build-depends (Closes: #958635) * Bumped Standards-Version to 5.4.0. * Updated DH compat version to 12. * Updated maintainer e-mail address. * Removed unused patch, scripts_path.path file. Checksums-Sha1: 37521e74c789f0a32a39b30aa90132deb54b87d5 1706 lsm_1.0.4-2.dsc 5c402a94d0c26c3beeb38107c5db1e4926b6ca0c 13780 lsm_1.0.4-2.debian.tar.xz b6a14cf9b3e9520130bf08ef19c3a08524fb5da8 5217 lsm_1.0.4-2_source.buildinfo Checksums-Sha256: 6c3c7633151020e6819eeebcca3a883222a96f67da024c742c9da88ae3c85afc 1706 lsm_1.0.4-2.dsc bdc1bcd74ff02569514b9c5a83944ee525e390ee92c863370e5ca91cc2e015a1 13780 lsm_1.0.4-2.debian.tar.xz 88ec9418e2bc368cccda220d85d367f0466d8ae76f23c35c75cc9b52429a8181 5217 lsm_1.0.4-2_source.buildinfo Files: 2a0ae0586140499a2128c3fe04f78a78 1706 utils optional lsm_1.0.4-2.dsc 8c04f0bdd45f329f3b7780438092808d 13780 utils optional lsm_1.0.4-2.debian.tar.xz 52833f7305319230f84d14a493a4fd8b 5217 utils optional lsm_1.0.4-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl9gQuQACgkQweDZLphv fH78Zg/7BEr0tlNSTJNzjSlCadJtCvyAz809QvL4QRVJYLU9lkUN8FczANq6Abl0 evkIJ30P5hBUqFqUtwMKIKEN7WvltcIDWgRKr/t4/+KBinihxsgR+Hbd1Jbt5PeV V4fK+WEi9PQ8MtJVojaFBIyLZ7Se7qXEDFk7Uc8pTyyCXt6yxdFM5zDTbPCrUA8x 9xhTFNZBmr3Or5hE5X79MD49lsf7B2L4wQZCSSW5bafPmmKGyAb4qdYAg3gJlWWS PbxkKUtViuCA7wqGSmgJaCSGcimpObyZhWfsRSDkpMmRas6sG7BpH0jBjMpyu/lp wI2zj8SkP9+oNKfK/MlNAqH3j1iTAILJYPV4+6kDz/wCPiA8a6wxbUoM5p/ltv47 6UPtVxJTVfM/+Z6RtBYrJcG/L59ibdlBzEXn8eDpGGdyDbakZt0rmmR5QroH7Top 4ZAvIeLig1uVdcIHJZ1IWgSU0jUDqPmynVYXYQD7EEX4/s3lU+IoJJ9Snky16O3e UYpsAdE/xgurKL+tAA+m8Wxa22VXD9SRoJCbdJJRb9jZcYFsN0OR9W1V+Y6Ydn0t DZTaxuTWYrl+TstL7FtSo6HoIURmgtLi5BptWtenGwAKFxMf+egzJ9eBBqeu/Eok o4O+KsfFOUCJFwdAya2HIBleMtKAl8Ylp/626QlOhy3M3HNUXmE= =u2uO -END PGP SIGNATURE End Message ---
Bug#969834: marked as done (ipmitool: autopkgtest should be marked superficial)
Your message dated Tue, 15 Sep 2020 04:33:39 + with message-id and subject line Bug#969834: fixed in ipmitool 1.8.18-10 has caused the Debian Bug report #969834, regarding ipmitool: autopkgtest should be marked superficial 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.) -- 969834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969834 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ipmitool Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'ipmitool' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.package-tests.html Examples of tests which are not significant includes (its not a complete list): 1) Executing the binary to check version Test-Command: foo -v Test-Command: foo -V Test-Command: foo --version 2) Executing the binary to check help (foo -h) Test-Command: foo -h Test-Command: foo --help 3) checking for files installed with 'ls'. Test-Command: ls -l /usr/lib/*/foo.so 4) A Python or Perl library runs import foo or require Foo; but does not attempt to use the library beyond that. Test-Command: python3 -c "import foo" Please add "Restrictions: superficial" to 'debian/tests/control' of 'ipmitool'. -- Sudip --- End Message --- --- Begin Message --- Source: ipmitool Source-Version: 1.8.18-10 Done: =?utf-8?q?J=C3=B6rg_Frings-F=C3=BCrst?= We believe that the bug you reported is fixed in the latest version of ipmitool, 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 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jörg Frings-Fürst (supplier of updated ipmitool 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: Mon, 14 Sep 2020 14:35:04 +0200 Source: ipmitool Architecture: source Version: 1.8.18-10 Distribution: unstable Urgency: medium Maintainer: Jörg Frings-Fürst Changed-By: Jörg Frings-Fürst Closes: 969834 Changes: ipmitool (1.8.18-10) unstable; urgency=medium . * Add "Restrictions: superficial" to debian/tests/control (Closes: #969834). Checksums-Sha1: 2bd61c340f4dd4714e9c642dbc019b6e508d8156 1962 ipmitool_1.8.18-10.dsc ab462d58576acbb6ece67f14178ed1fb63290a5c 18548 ipmitool_1.8.18-10.debian.tar.xz dbd58714878ddcdeef41b2eca1b2fb5c662125f8 5380 ipmitool_1.8.18-10_source.buildinfo Checksums-Sha256: 054645eab0f9077183cd7b1d93feb375000fd29f9c6eed5dcd9a4346b10a8306 1962 ipmitool_1.8.18-10.dsc 3b9f2b4382c7cf8c5b3e2015d63eebe6933eadd8bcbfb7b4c5c9d943cab9e021 18548 ipmitool_1.8.18-10.debian.tar.xz 9798a895748d7e2504e59ea4c588c172eaac7a941e79b953a1bcb15122ab5390 5380 ipmitool_1.8.18-10_source.buildinfo Files: 5268f680b669f503ab06099642557218 1962 utils optional ipmitool_1.8.18-10.dsc 366b1689385eb06b7c9820111b572f3e 18548 utils optional ipmitool_1.8.18-10.debian.tar.xz f55ef802cef796e481aa6f1c9b7e159d 5380 utils optional ipmitool_1.8.18-10_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl9gP1wACgkQweDZLphv fH51kQ//V21hm+SwuagT8GmmyuVgilSyqys8a5BSzX38O8Ax32w3+XuZV2yvP/a+ fT5SfNK5KURvy8wWwF7PG/Brwr1IhfqebjahX5L8yxqGWv4Y/CDCXVbTHbGH4ZXd zKcbmicroH+inMCsTtfTfQ+6LK1C7s/FRp0HVZGQynzTYzhYdrUBsRw65/kUQtfx 6epCyFA8pegw4C6YzVLELfLBPRJO9c7K8RtepONyxfIm4WEGQhh3ywPLS7NJR8Q+ nMkRbxkcKFpVJLNWULZr3tgEk+dR3fyvfogD8+kWM463rd+e4XHWHObKOENYsGfN nctcVAde4DEcDBlgaspZ7bVeltcWoJxTrDcjyrFd0iTY56K99F1Vsf27i2gOTMWP OEmOxuHyZakaNKTbYQkPgLSVqLz6dxiMk5NbxTpAVwjzI8SldsgPoEt50GygAqSP HfMKrtSRDvv7UReHTu0bt7I4Lv+FAWI8srMxFYOafJf5YDiic6nHO9yurGpEmKDJ IgxkjbI7qOzFAFYsxmuDQEIvOOOQUO22IejhGY97qm2tOeGV6DZfy6Ax2RJ8Wzfs Sb83SrpvnwrZkrpbntKYX1rsOVxEb7PXN8WqEDn/QGwSeJBccoE9UUi1WWJR2K2u jpAjFjc7Of1TvRxklKE0HmUUB4U5UFgkbazetSNgXGzaxKfeF+E= =sJBa -END PGP SIGNATURE End Message ---
Bug#968714: marked as done (extractpdfmark FTBFS with poppler 0.85)
Your message dated Tue, 15 Sep 2020 04:33:33 + with message-id and subject line Bug#968714: fixed in extractpdfmark 1.1.0-1.1 has caused the Debian Bug report #968714, regarding extractpdfmark FTBFS with poppler 0.85 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.) -- 968714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968714 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: extractpdfmark Version: 1.1.0-1 Severity: serious Tags: patch extractpdfmark FTBFS with poppler 0.85 destname.cc:85:62: error: no matching function for call to ‘PDFDoc::findPage(int&, int&)’ 85 | pagenum = doc->findPage (page_ref.num, page_ref.gen); Doing a bit of poking around in poppler's git repository I deduced that the call should be changed to pagenum = doc->findPage(page_ref); I have whipped up a patch and uploaded it to raspbian, a debdiff should appear soon at https://debdiffs.raspbian.org/main/e/extractpdfmark I may or may not NMU this in Debian later. --- End Message --- --- Begin Message --- Source: extractpdfmark Source-Version: 1.1.0-1.1 Done: Francois Mazen We believe that the bug you reported is fixed in the latest version of extractpdfmark, 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 968...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Francois Mazen (supplier of updated extractpdfmark 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, 13 Sep 2020 22:28:49 +0200 Source: extractpdfmark Architecture: source Version: 1.1.0-1.1 Distribution: unstable Urgency: high Maintainer: Dr. Tobias Quathamer Changed-By: Francois Mazen Closes: 968714 Changes: extractpdfmark (1.1.0-1.1) unstable; urgency=high . * Non-maintainer upload. * Fix FTBFS with poppler 0.85 (Closes: #968714). Checksums-Sha1: 81cbdfdf1f9fe7b27a2f9e3c5707b0f4af5c3771 1984 extractpdfmark_1.1.0-1.1.dsc 70183a903eea00db24a0b1dfa77fbcbb9a0a72f8 3440 extractpdfmark_1.1.0-1.1.debian.tar.xz 2b91fbc9072db6880cbf7f674cf5405ef1e1f7a8 7493 extractpdfmark_1.1.0-1.1_source.buildinfo Checksums-Sha256: 02275793d0f8374447e6bd3b4f5139182bd130dcfe339e2bc5bc246ce1b29838 1984 extractpdfmark_1.1.0-1.1.dsc d6e7cb579830ce6ad00d033f254ce889101c7ed1ed68ff6395fb3d1c5b3ff4c3 3440 extractpdfmark_1.1.0-1.1.debian.tar.xz 5ffcd70e1de5c83f69f65bb430676e374858d0c3c7239bffc1aeb6fdc1b2b70a 7493 extractpdfmark_1.1.0-1.1_source.buildinfo Files: f6f25347c90cbd402e89654606fc4cdf 1984 tex optional extractpdfmark_1.1.0-1.1.dsc 248f1c5a8e967b742c62b838c9896564 3440 tex optional extractpdfmark_1.1.0-1.1.debian.tar.xz b59b83069cecf59698fc97ffb04b031a 7493 tex optional extractpdfmark_1.1.0-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl9gQNMACgkQweDZLphv fH72thAAw74REfNqDjs77x1QL5bw9/29T6RjiTpRLi6GHFELVomKOaUr8kkk4/hJ zyhLEbrMpJx/z9ktWtDhqmqD+7lnM5iL29UcYLzxe0HodEKvhi93tNgbxQIhX74G BwWpeigx30ruuJyRKabNrPNjtUYOIa4HRc24A8wg8YKbzXjhr+r+6JZmCTpAvKRV 4pft+RYunjrMrJcxaxiiomuLlNd18Brb4RIhoSiqfFNo7zh1jUhVSl6ruefWTH5Q Rux7542jB2DDwwukCSUeUb/nK38x5USLITu1h7pjuOY+WhoKk6ziv73OH15iSh0S 0oZMrBXOSjlhQKFgNBVRfdvhlZVBwCLxfcDI16EMvuHNH+GLGQJT+6cBwK6qbhKb 40mikljlv+p2ZfrhTb14p4c5KTn+t4GjVzqd92krbirSEFGglcrQTYsitUI4OQK7 obMup//42YIG11B5rcVwHMF6eLFbbEv6FBXCtTWJscId4UpM1ZsrliUEqqhpw/1e 8FSF2TyO9S7mD8K8WZP5PS83khx2+oRWTTO+1QkBUBvzC/FrO8hdjG1dIRPRFPUN 6lRQzP0eWv34xZk1iQsA2YiOiUEtVmHIiwD09AjMBsYDIEqMGR3K3KfYpoZH26PO gabaWh81KjOt+JI+WLlPRIfNWNHhBN2N7PxRzwWDXSL0JuVZzn8= =mJqM -END PGP SIGNATURE End Message ---
Bug#969819: marked as done (dmidecode: autopkgtest should be marked superficial)
Your message dated Tue, 15 Sep 2020 04:33:28 + with message-id and subject line Bug#969819: fixed in dmidecode 3.2-4 has caused the Debian Bug report #969819, regarding dmidecode: autopkgtest should be marked superficial 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.) -- 969819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dmidecode Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'dmidecode' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.package-tests.html Examples of tests which are not significant includes (its not a complete list): 1) Executing the binary to check version Test-Command: foo -v Test-Command: foo -V Test-Command: foo --version 2) Executing the binary to check help (foo -h) Test-Command: foo -h Test-Command: foo --help 3) checking for files installed with 'ls'. Test-Command: ls -l /usr/lib/*/foo.so 4) A Python or Perl library runs import foo or require Foo; but does not attempt to use the library beyond that. Test-Command: python3 -c "import foo" Please add "Restrictions: superficial" to 'debian/tests/control' of 'dmidecode'. -- Sudip --- End Message --- --- Begin Message --- Source: dmidecode Source-Version: 3.2-4 Done: =?utf-8?q?J=C3=B6rg_Frings-F=C3=BCrst?= We believe that the bug you reported is fixed in the latest version of dmidecode, 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 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jörg Frings-Fürst (supplier of updated dmidecode 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: Mon, 14 Sep 2020 14:18:46 +0200 Source: dmidecode Architecture: source Version: 3.2-4 Distribution: unstable Urgency: medium Maintainer: Jörg Frings-Fürst Changed-By: Jörg Frings-Fürst Closes: 969819 Changes: dmidecode (3.2-4) unstable; urgency=medium . * Add "Restrictions: superficial" to debian/tests/control (Closes: #969819). Checksums-Sha1: 5f84c00337380676ca0224b8829fe9d95b5e439e 2245 dmidecode_3.2-4.dsc 6dda0039be07094d96ec462877d822cd48f0b7af 16116 dmidecode_3.2-4.debian.tar.xz 8a3813d171261b0fe13864c101b54a65b9b3bd06 5071 dmidecode_3.2-4_source.buildinfo Checksums-Sha256: c2afea1c2e53c1474400ec625d4c13897374f2ea1ce3fe0ba6b1a4fce21bd24d 2245 dmidecode_3.2-4.dsc 2268f6ec3f203eef89bd0a691ff2861d189a7fbf7eb52d437f4913f7c9f8232c 16116 dmidecode_3.2-4.debian.tar.xz 2ddec4c363bb6b3ce4c037fcb429efdc86d59fb366169c7b1bf4e6c529873809 5071 dmidecode_3.2-4_source.buildinfo Files: 844f75efbf4a31d3f86bb590ed11b36a 2245 utils optional dmidecode_3.2-4.dsc c3e6ec981d08f03442afe7e25db45a31 16116 utils optional dmidecode_3.2-4.debian.tar.xz 6135cb71d283f95b78a6291ca2ce914f 5071 utils optional dmidecode_3.2-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl9gPnkACgkQweDZLphv fH6ewA//UWktjdOZNpLfbcSh+gmfS1BA1fZ3v1qP93oCztj1VfxnFW20b2LaOalF x/O+tq2RPUF+RpjBTS4DM1k7dRsru3BHYesplBgqOfkR8Mcx50ek11ckvqOzXeny uDtELWnMja2AGf6HcCna+x0KNoEkRI/gakAQbyTojIi2EIEQ+sFt+3QwnL19Jw2u jx6vidcO/ZjxcNlQzsHzePVAeShqz5He6P6jhyonGzTRlQ/wGx5YTES6tO8AMKTx OUydqMQzszaziowFrFaB70/jGMaULHcAgjaUzJWj6zRjUpKCidtDuZoskM/MpNUD xzVGPe8wfHRG98ELPs3V1Gh0WZ7AUyJDXNeZ0XMdIG39ES9dtaAF6x05G4g592Zp Ymra9WUr1WweYxrXU8OWN3NXKbJnwbmrYBMgEukAzmm6QC4hzh1R3cWCyu1Amikx vyDonlmRmTtsKYIhDf9vaMs/Eo1kc78zITLQpssesJqmfGgq4ZZAcxZuBhaG+rfE 7ZWqVSM0IUETkgD1279N/4kH22vNGH+A7JjfdfRIKBwrCElU0yR+HtRt/u6Ak6p8 XhmFko1nGP5UWHnCCMsbBmPxb/WFb+f6TzZw6bfG5xu6fTC5xDWoyJOzK3zmpCI2 jY5I8AAd7YhIqDJvrZcSi7BksF8Ol8IsUxjOeRC3BBCJM8A2aJE= =BEq0 -END PGP SIGNATURE End Message ---
Bug#962844: mdadm: Assembling RAID using IMSM in initrd fails due to lack of module efivarfs
Hi Colin, > The efivarfs module was not found in the initrd I would like to make sure any new module requirements are also compatible with systems booting in legacy BIOS mode. The Wikipedia article for Intel RST states: > When booting in a BIOS environment (legacy) and some / EFI, the RST option > ROM is used. When booting in a true UEFI environment the Option ROM is not > used as a SataDriver with the RST version takes over. In BIOS mode the > legacy/BIOS booting is under CSMCORE. In true UEFI mode the RST is > controlled under SataDriver in BIOS. [1] The article suggests that some people use IMSM arrays in legacy BIOS mode. Does mdadm support IMSM only when the system is booted in UEFI mode? Sorry that I do not know the answer to that question. I just assumed maintenance of mdadm and do not use IMSM. At this point, I am reading code. Thank you! Kind regards Felix Lechner [1] https://en.wikipedia.org/wiki/Intel_Rapid_Storage_Technology#Matrix_Storage_Manager_option_ROM
Bug#969596:
The attached patch appears to fix the build in Ubuntu.
diff -Nru minimap2-2.17+dfsg/debian/changelog minimap2-2.17+dfsg/debian/changelog
--- minimap2-2.17+dfsg/debian/changelog 2020-07-07 21:32:26.0 +1200
+++ minimap2-2.17+dfsg/debian/changelog 2020-09-15 12:34:50.0 +1200
@@ -1,3 +1,10 @@
+minimap2 (2.17+dfsg-11ubuntu1) groovy; urgency=medium
+
+ * d/patches/python-sse4-arch.patch: Only pass -msse4.1 to the compiler on
+amd64.
+
+ -- Michael Hudson-Doyle Tue, 15 Sep 2020 12:34:50 +1200
+
minimap2 (2.17+dfsg-11) unstable; urgency=medium
* Add lintian-override
diff -Nru minimap2-2.17+dfsg/debian/control minimap2-2.17+dfsg/debian/control
--- minimap2-2.17+dfsg/debian/control 2020-07-07 21:32:26.0 +1200
+++ minimap2-2.17+dfsg/debian/control 2020-09-15 12:34:50.0 +1200
@@ -1,5 +1,6 @@
Source: minimap2
-Maintainer: Debian Med Packaging Team
+Maintainer: Ubuntu Developers
+XSBC-Original-Maintainer: Debian Med Packaging Team
Uploaders: Andreas Tille
Section: science
Priority: optional
diff -Nru minimap2-2.17+dfsg/debian/patches/python-sse4-arch.patch minimap2-2.17+dfsg/debian/patches/python-sse4-arch.patch
--- minimap2-2.17+dfsg/debian/patches/python-sse4-arch.patch 1970-01-01 12:00:00.0 +1200
+++ minimap2-2.17+dfsg/debian/patches/python-sse4-arch.patch 2020-09-15 12:34:50.0 +1200
@@ -0,0 +1,11 @@
+--- a/setup.py
b/setup.py
+@@ -26,7 +26,7 @@
+ if platform.machine() in ["aarch64", "arm64"]:
+ include_dirs.append("sse2neon/")
+ extra_compile_args.extend(['-ftree-vectorize', '-DKSW_SSE2_ONLY', '-D__SSE2__'])
+-else:
++elif platform.machine() == "x86_64":
+ extra_compile_args.append('-msse4.1') # WARNING: ancient x86_64 CPUs don't have SSE4
+
+ def readme():
diff -Nru minimap2-2.17+dfsg/debian/patches/series minimap2-2.17+dfsg/debian/patches/series
--- minimap2-2.17+dfsg/debian/patches/series 2020-07-07 21:32:26.0 +1200
+++ minimap2-2.17+dfsg/debian/patches/series 2020-09-15 12:34:42.0 +1200
@@ -3,3 +3,4 @@
simde
ar.patch
link_mappy_to_libminimap.patch
+python-sse4-arch.patch
Bug#969448: marked as done (bind9: dies with assertion and does not restart)
Your message dated Mon, 14 Sep 2020 23:03:41 + with message-id and subject line Bug#969448: fixed in bind9 1:9.16.6-3 has caused the Debian Bug report #969448, regarding bind9: dies with assertion and does not restart 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.) -- 969448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969448 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bind9 Version: 1:9.16.6-2 Severity: critical X-Debbugs-Cc: none, Francesco Potortì This happened twice in the last days. Here are the logs Cycle 1/2 Aug 31 16:46:29 tucano named[786855]: starting BIND 9.16.6-Debian (Stable Release) Aug 31 16:46:29 tucano named[786855]: running on Linux x86_64 5.6.0-2-amd64 #1 SMP Debian 5.6.14-1 (2020-05-23) Aug 31 16:46:29 tucano named[786855]: built with '--build=x86_64-linux-gnu' '--prefix=/usr' '--includedir=/usr/include' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc' '--localstatedir=/var' '--disable-option-checking' '--disable-silent-rules' '--libdir=/usr/lib/x86_64-linux-gnu' '--runstatedir=/run' '--disable-maintainer-mode' '--disable-dependency-tracking' '--libdir=/usr/lib/x86_64-linux-gnu' '--sysconfdir=/etc/bind' '--with-python=python3' '--localstatedir=/' '--enable-threads' '--enable-largefile' '--with-libtool' '--enable-shared' '--enable-static' '--with-gost=no' '--with-openssl=/usr' '--with-gssapi=/usr' '--with-libidn2' '--with-libjson-c' '--with-lmdb=/usr' '--with-gnu-ld' '--with-maxminddb' '--with-atf=no' '--enable-ipv6' '--enable-rrl' '--enable-filter-' '--disable-native-pkcs11' '--enable-dnstap' 'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2 -fdebug-prefix-map=/build/bind9-LHdBnU/bind9-9.16.6=. -fstack-protector-strong -Wformat -Werror=forma t-security -fno-strict-aliasing -fno-delete-null-pointer-checks -DNO_VERSION_DATE -DDIG_SIGCHASE' 'LDFLAGS=-Wl,-z,relro -Wl,-z,now' 'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2' Aug 31 16:46:29 tucano named[786855]: running as: named -f -u bind Aug 31 16:46:29 tucano named[786855]: compiled by GCC 10.2.0 Aug 31 16:46:29 tucano named[786855]: compiled with OpenSSL version: OpenSSL 1.1.1g 21 Apr 2020 Aug 31 16:46:29 tucano named[786855]: linked to OpenSSL version: OpenSSL 1.1.1g 21 Apr 2020 Aug 31 16:46:29 tucano named[786855]: compiled with libxml2 version: 2.9.10 Aug 31 16:46:29 tucano named[786855]: linked to libxml2 version: 20910 Aug 31 16:46:29 tucano named[786855]: compiled with json-c version: 0.15 Aug 31 16:46:29 tucano named[786855]: linked to json-c version: 0.15 Aug 31 16:46:29 tucano named[786855]: compiled with zlib version: 1.2.11 Aug 31 16:46:29 tucano named[786855]: linked to zlib version: 1.2.11 Aug 31 16:46:29 tucano named[786855]: Aug 31 16:46:29 tucano named[786855]: BIND 9 is maintained by Internet Systems Consortium, Aug 31 16:46:29 tucano named[786855]: Inc. (ISC), a non-profit 501(c)(3) public-benefit Aug 31 16:46:29 tucano named[786855]: corporation. Support and training for BIND 9 are Aug 31 16:46:29 tucano named[786855]: available at https://www.isc.org/support Aug 31 16:46:29 tucano named[786855]: Aug 31 16:46:29 tucano named[786855]: adjusted limit on open files from 524288 to 1048576 Aug 31 16:46:29 tucano named[786855]: found 4 CPUs, using 4 worker threads Aug 31 16:46:29 tucano named[786855]: using 4 UDP listeners per interface Aug 31 16:46:29 tucano named[786855]: using up to 21000 sockets Aug 31 16:46:29 tucano named[786855]: loading configuration from '/etc/bind/named.conf' Aug 31 16:46:29 tucano named[786855]: /etc/bind/named.conf.options:32: option 'dnssec-enable' is obsolete and should be removed Aug 31 16:46:29 tucano named[786855]: reading built-in trust anchors from file '/etc/bind/bind.keys' Aug 31 16:46:29 tucano named[786855]: looking for GeoIP2 databases in '/usr/share/GeoIP' Aug 31 16:46:29 tucano named[786855]: using default UDP/IPv4 port range: [32768, 60999] Aug 31 16:46:29 tucano named[786855]: using default UDP/IPv6 port range: [32768, 60999] Aug 31 16:46:29 tucano named[786855]: listening on IPv4 interface lo, 127.0.0.1#53 Aug 31 16:46:29 tucano named[786855]: listening on IPv4 interface eth0, 146.48.81.102#53 Aug 31 16:46:29 tucano named[786855]: IPv6 socket API is incomplete; explicitly binding to each IPv6 address separately Aug 31 16:46:29 tucano named[786855]: listening on IPv6 interface lo, ::1#53 Aug 31 16:46:29 tucano named[786855]: listening
Processed: Re: undertow: should not be part of Debian 11
Processing commands for cont...@bugs.debian.org: > severity 970346 serious Bug #970346 [src:undertow] undertow: should not be part of Debian 11 Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 970346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: cups-browsed.service Hangs on Shutdown
Processing control commands: > severity -1 critical Bug #969355 [cups-browsed] cups-browsed.service Hangs on Shutdown Severity set to 'critical' from 'normal' -- 969355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#912889: tinyca: Depends on libgtk2-perl, that won't be part of Bullseye
It appears that porting TinyCA to Gtk3 is doable and I have a working version. Before publishing the code on Salsa I'd like to clean it up a bit, though. I hope to get that done in the next week.
Bug#970333: marked as done (abseil: autopkgtest needs update for new version of cmake: warning on stderr)
Your message dated Mon, 14 Sep 2020 22:03:29 + with message-id and subject line Bug#970333: fixed in abseil 0~20200225.2-4 has caused the Debian Bug report #970333, regarding abseil: autopkgtest needs update for new version of cmake: warning on stderr 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.) -- 970333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970333 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: abseil Version: 0~20200225.2-3 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, cm...@packages.debian.org Tags: sid bullseye User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:cmake Dear maintainer(s), With a recent upload of cmake the autopkgtest of abseil fails in testing when that autopkgtest is run with the binary packages of cmake from unstable. It passes when run with only packages from testing. In tabular form: passfail cmake from testing3.18.2-1 abseil from testing0~20200225.2-3 all others from testingfrom testing I copied some of the output at the bottom of this report. The output contains a warning that's written to stderr. By default that fails a test. If you can't fix the underlaying cause, you can have the output to stderr ignored by adding an allow-stderr restriction to the test specification. Currently this regression is blocking the migration of cmake to testing [1]. Of course, cmake shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in cmake was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from cmake should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=cmake https://ci.debian.net/data/autopkgtest/testing/amd64/a/abseil/7009726/log.gz autopkgtest [22:32:41]: test cmake: - - - - - - - - - - results - - - - - - - - - - cmakeFAIL stderr: CMake Warning (dev) at /usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:273 (message): autopkgtest [22:32:41]: test cmake: - - - - - - - - - - stderr - - - - - - - - - - CMake Warning (dev) at /usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:273 (message): The package name passed to `find_package_handle_standard_args` (Threads) does not match the name of the calling package (absl). This can lead to problems in calling code that expects `find_package` result variables (e.g., `_FOUND`) to follow a certain pattern. Call Stack (most recent call first): /usr/share/cmake-3.18/Modules/FindThreads.cmake:234 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) /usr/lib/x86_64-linux-gnu/cmake/absl/abslConfig.cmake:3 (include) CMakeLists.txt:5 (find_package) This warning is for project developers. Use -Wno-dev to suppress it. signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: abseil Source-Version: 0~20200225.2-4 Done: Benjamin Barenblat We believe that the bug you reported is fixed in the latest version of abseil, 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 970...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Benjamin Barenblat (supplier of updated abseil 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: Mon, 14 Sep 2020 17:40:05 -0400 Source: abseil Architecture: source Version: 0~20200225.2-4 Distribution: unstable Urgency: medium Maintainer: Benjamin Barenblat Changed-By: Benjamin Barenblat Closes: 970333 Changes: abseil (0~20200225.2-4) unstable; urgency=medium . * Fix "autopkgtest needs update for new
Bug#969559: curl segmentation fauls on any https URL
On Fri, Sep 11, 2020 at 06:28:20PM +0200, Bernhard Übelacker wrote: > Dear Maintainer, hello Bruce Momjian, > with the last informations the issue is perfectly reproducible. > > It looks like a use after free caused by statically stored > function pointers in libengine-pkcs11-openssl / libp11. > > That led to following upstream bug: > https://github.com/OpenSC/libp11/issues/328 > > This got fixed in this commit: > > https://github.com/OpenSC/libp11/commit/e64496a198d4d2eb0310a22dc21be8b81367d319 > > This commit is not yet included in an upstream release tag. > Therefore this error is also visible in current testing. > > I hope it is ok to reassign to libengine-pkcs11-openssl. Yes, thank you for researching this and closing it. -- Bruce Momjian https://momjian.us EnterpriseDB https://enterprisedb.com The usefulness of a cup is in its emptiness, Bruce Lee
Bug#969608: makeblastdb 2.10.x on 32-bit architectures
Étienne Mollier writes: > I worked within an arm64 schroot built with sbuild-createchroot, > on a native amd64 machine. Thanks for clarifying. AFAICT, this environment imposes a tighter limit than native arm64 hardware, and versions 2.10.0-1 and 2.10.0-3 both hit it. Rough bisection via the BLASTDB_LMDB_MAP_SIZE environment variable gives an empirical limit of 20,073,607,168 bytes (4,900,783 4K pages). This number isn't particularly round, so it presumably reflects what remains of some cumulative limit. As such, the default should probably be at most 20,000,000,000 bytes (4,882,812½ pages ;-) to build in more of a margin. That's 1/15 upstream's default, but with any luck should be plenty in practice, so I'm open to making that adjustment. Also, this reduced limit would still be well more than we (can) allow on 32-bit architectures, which is in turn much more than upstream's trunk allows on Windows: https://www.ncbi.nlm.nih.gov/IEB/ToolBox/CPP_DOC/lxr/source/include/objtools/blast/seqdb_writer/writedb_lmdb.hpp#L51 -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#970333: abseil: autopkgtest needs update for new version of cmake: warning on stderr
Control: owner 970333 ! Control: tags 970333 + pending upstream fixed-upstream Control: forwarded 970333 https://github.com/abseil/abseil-cpp/issues/668 This is a bug in upstream’s CMake support. I’ll patch in their fix (https://github.com/abseil/abseil-cpp/commit/68494aae959dfbbf781cdf03a988d2f5fc7e4802).
Processed: Re: Bug#970333: abseil: autopkgtest needs update for new version of cmake: warning on stderr
Processing control commands: > owner 970333 ! Bug #970333 [src:abseil] abseil: autopkgtest needs update for new version of cmake: warning on stderr Owner recorded as Benjamin Barenblat . > tags 970333 + pending upstream fixed-upstream Bug #970333 [src:abseil] abseil: autopkgtest needs update for new version of cmake: warning on stderr Added tag(s) upstream, pending, and fixed-upstream. > forwarded 970333 https://github.com/abseil/abseil-cpp/issues/668 Bug #970333 [src:abseil] abseil: autopkgtest needs update for new version of cmake: warning on stderr Set Bug forwarded-to-address to 'https://github.com/abseil/abseil-cpp/issues/668'. -- 970333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970333 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970339: libobject-pad-perl breaks libtickit-widget-tabbed-perl autopkgtest: Failed test 'all modules in libtickit-widget-tabbed-perl pass the syntax check'
Control: reassign -1 libobject-pad-perl 0.32-1 Control: reassign 970338 libobject-pad-perl 0.32-1 Control: merge -1 970338 Control: affects -1 libtickit-widget-tabbed-perl libtickit-console-perl Control: forwarded -1 https://rt.cpan.org/Public/Bug/Display.html?id=133190 On Mon, 14 Sep 2020 22:00:02 +0200, Paul Gevers wrote: > With a recent upload of libobject-pad-perl the autopkgtest of > libtickit-widget-tabbed-perl fails in testing when that autopkgtest is > run with the binary packages of libobject-pad-perl from unstable. It > passes when run with only packages from testing. In tabular form: Thanks for the bug report. Looking at the upstream tickets, I think this is Object::Pad's fault and probably the same problem. Tracked upstream at https://rt.cpan.org/Public/Bug/Display.html?id=133190 (or maybe (also) https://rt.cpan.org/Public/Bug/Display.html?id=133258 ) Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Neil Young: Alabama signature.asc Description: Digital Signature
Processed: Re: Bug#970339: libobject-pad-perl breaks libtickit-widget-tabbed-perl autopkgtest: Failed test 'all modules in libtickit-widget-tabbed-perl pass the syntax check'
Processing control commands: > reassign -1 libobject-pad-perl 0.32-1 Bug #970339 [src:libobject-pad-perl, src:libtickit-widget-tabbed-perl] libobject-pad-perl breaks libtickit-widget-tabbed-perl autopkgtest: Failed test 'all modules in libtickit-widget-tabbed-perl pass the syntax check' Bug reassigned from package 'src:libobject-pad-perl, src:libtickit-widget-tabbed-perl' to 'libobject-pad-perl'. No longer marked as found in versions libtickit-widget-tabbed-perl/0.023-1 and libobject-pad-perl/0.32-1. Ignoring request to alter fixed versions of bug #970339 to the same values previously set Bug #970339 [libobject-pad-perl] libobject-pad-perl breaks libtickit-widget-tabbed-perl autopkgtest: Failed test 'all modules in libtickit-widget-tabbed-perl pass the syntax check' Marked as found in versions libobject-pad-perl/0.32-1. > reassign 970338 libobject-pad-perl 0.32-1 Bug #970338 [src:libobject-pad-perl, src:libtickit-console-perl] libobject-pad-perl breaks libtickit-console-perl autopkgtest: Failed test 'all modules in libtickit-console-perl pass the syntax check' Bug reassigned from package 'src:libobject-pad-perl, src:libtickit-console-perl' to 'libobject-pad-perl'. No longer marked as found in versions libtickit-console-perl/0.09-1 and libobject-pad-perl/0.32-1. Ignoring request to alter fixed versions of bug #970338 to the same values previously set Bug #970338 [libobject-pad-perl] libobject-pad-perl breaks libtickit-console-perl autopkgtest: Failed test 'all modules in libtickit-console-perl pass the syntax check' Marked as found in versions libobject-pad-perl/0.32-1. > merge -1 970338 Bug #970339 [libobject-pad-perl] libobject-pad-perl breaks libtickit-widget-tabbed-perl autopkgtest: Failed test 'all modules in libtickit-widget-tabbed-perl pass the syntax check' Bug #970338 [libobject-pad-perl] libobject-pad-perl breaks libtickit-console-perl autopkgtest: Failed test 'all modules in libtickit-console-perl pass the syntax check' Merged 970338 970339 > affects -1 libtickit-widget-tabbed-perl libtickit-console-perl Bug #970339 [libobject-pad-perl] libobject-pad-perl breaks libtickit-widget-tabbed-perl autopkgtest: Failed test 'all modules in libtickit-widget-tabbed-perl pass the syntax check' Bug #970338 [libobject-pad-perl] libobject-pad-perl breaks libtickit-console-perl autopkgtest: Failed test 'all modules in libtickit-console-perl pass the syntax check' Added indication that 970339 affects libtickit-widget-tabbed-perl and libtickit-console-perl Added indication that 970338 affects libtickit-widget-tabbed-perl and libtickit-console-perl > forwarded -1 https://rt.cpan.org/Public/Bug/Display.html?id=133190 Bug #970339 [libobject-pad-perl] libobject-pad-perl breaks libtickit-widget-tabbed-perl autopkgtest: Failed test 'all modules in libtickit-widget-tabbed-perl pass the syntax check' Bug #970338 [libobject-pad-perl] libobject-pad-perl breaks libtickit-console-perl autopkgtest: Failed test 'all modules in libtickit-console-perl pass the syntax check' Set Bug forwarded-to-address to 'https://rt.cpan.org/Public/Bug/Display.html?id=133190'. Set Bug forwarded-to-address to 'https://rt.cpan.org/Public/Bug/Display.html?id=133190'. -- 970338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970338 970339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952026: marked as done (ruby-handlebars-assets: FTBFS with current libjs-handlebars version: ERROR: ExecJS::ProgramError: ReferenceError: Handlebars is not defined)
Your message dated Mon, 14 Sep 2020 21:04:21 + with message-id and subject line Bug#952026: fixed in node-handlebars 3:4.7.6-2 has caused the Debian Bug report #952026, regarding ruby-handlebars-assets: FTBFS with current libjs-handlebars version: ERROR: ExecJS::ProgramError: ReferenceError: Handlebars is not defined 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.) -- 952026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-handlebars-assets Version: 2:0.23.3+dfsg-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Invalid gemspec in [handlebars_assets.gemspec]: No such file or directory - > git > GEM_PATH=/<>/debian/ruby-handlebars-assets/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/ruby/gems/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0 > ruby2.5 -e gem\ \"handlebars_assets\" > > ┌──┐ > │ Run tests for ruby2.5 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=. > GEM_PATH=/<>/debian/ruby-handlebars-assets/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/ruby/gems/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0 > ruby2.5 -S rake -f debian/ruby-tests.rake > Run options: --seed 61834 > > # Running: > > .EEE.E.E > > Finished in 23.198956s, 1.2070 runs/s, 0.3448 assertions/s. > > 1) Error: > HandlebarsAssets::CompilingTest#test_patching_handlebars: > ExecJS::ProgramError: ReferenceError: Handlebars is not defined > (execjs):2:71486 > (execjs):19:14 > (execjs):1:40 > Object. ((execjs):1:58) > Module._compile (internal/modules/cjs/loader.js:778:30) > Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) > Module.load (internal/modules/cjs/loader.js:653:32) > tryModuleLoad (internal/modules/cjs/loader.js:593:12) > Function.Module._load (internal/modules/cjs/loader.js:585:3) > Function.Module.runMain (internal/modules/cjs/loader.js:831:12) > /usr/lib/ruby/vendor_ruby/execjs/external_runtime.rb:39:in `exec' > /usr/lib/ruby/vendor_ruby/execjs/external_runtime.rb:14:in `initialize' > /usr/lib/ruby/vendor_ruby/execjs/runtime.rb:44:in `new' > /usr/lib/ruby/vendor_ruby/execjs/runtime.rb:44:in `compile' > /usr/lib/ruby/vendor_ruby/execjs/module.rb:27:in `compile' > /<>/lib/handlebars_assets/handlebars.rb:31:in `context' > /<>/lib/handlebars_assets/handlebars.rb:10:in `precompile' > /<>/test/handlebars_assets/compiling_test.rb:26:in > `test_patching_handlebars' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method' > /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method' > /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each' > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' > /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run' > /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun' > > 2) Error: > HandlebarsAssets::HamlbarsTest#test_render_haml: > ExecJS::ProgramError: ReferenceError: Handlebars is not
Processed: Fwd: fix found version
Processing commands for cont...@bugs.debian.org: > notfound 952026 3:4.7.6-2 Bug #952026 [node-handlebars] ruby-handlebars-assets: FTBFS with current libjs-handlebars version: ERROR: ExecJS::ProgramError: ReferenceError: Handlebars is not defined There is no source info for the package 'node-handlebars' at version '3:4.7.6-2' with architecture '' Unable to make a source version for version '3:4.7.6-2' No longer marked as found in versions 3:4.7.6-2. > End of message, stopping processing here. Please contact me if you need assistance. -- 952026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957388: marked as done (jeex: ftbfs with GCC-10)
Your message dated Mon, 14 Sep 2020 20:39:49 + with message-id and subject line Bug#957388: fixed in jeex 12.0.4-1.1 has caused the Debian Bug report #957388, regarding jeex: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:jeex Version: 12.0.4-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/jeex_12.0.4-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] /usr/bin/ld: html-export.o:(.bss+0x0): multiple definition of `notebook'; edit.o:(.bss+0x0): first defined here /usr/bin/ld: html-export.o:(.bss+0x20): multiple definition of `byte_info'; edit.o:(.bss+0x20): first defined here /usr/bin/ld: html-export.o:(.bss+0x80): multiple definition of `textview'; edit.o:(.bss+0x80): first defined here /usr/bin/ld: html-export.o:(.bss+0x88): multiple definition of `bar'; edit.o:(.bss+0x88): first defined here /usr/bin/ld: html-export.o:(.bss+0x90): multiple definition of `viewport'; edit.o:(.bss+0x90): first defined here /usr/bin/ld: html-export.o:(.bss+0x98): multiple definition of `table_info'; edit.o:(.bss+0x98): first defined here /usr/bin/ld: html-export.o:(.bss+0xa0): multiple definition of `sysicon'; edit.o:(.bss+0xa0): first defined here /usr/bin/ld: html-export.o:(.bss+0xa8): multiple definition of `ac'; edit.o:(.bss+0xa8): first defined here /usr/bin/ld: logging.o:(.bss+0x0): multiple definition of `notebook'; edit.o:(.bss+0x0): first defined here /usr/bin/ld: logging.o:(.bss+0x20): multiple definition of `byte_info'; edit.o:(.bss+0x20): first defined here /usr/bin/ld: logging.o:(.bss+0x80): multiple definition of `textview'; edit.o:(.bss+0x80): first defined here /usr/bin/ld: logging.o:(.bss+0x88): multiple definition of `bar'; edit.o:(.bss+0x88): first defined here /usr/bin/ld: logging.o:(.bss+0x90): multiple definition of `viewport'; edit.o:(.bss+0x90): first defined here /usr/bin/ld: logging.o:(.bss+0x98): multiple definition of `table_info'; edit.o:(.bss+0x98): first defined here /usr/bin/ld: logging.o:(.bss+0xa0): multiple definition of `sysicon'; edit.o:(.bss+0xa0): first defined here /usr/bin/ld: logging.o:(.bss+0xa8): multiple definition of `ac'; edit.o:(.bss+0xa8): first defined here /usr/bin/ld: search.o:(.bss+0x0): multiple definition of `notebook'; edit.o:(.bss+0x0): first defined here /usr/bin/ld: search.o:(.bss+0x20): multiple definition of `byte_info'; edit.o:(.bss+0x20): first defined here /usr/bin/ld: search.o:(.bss+0x80): multiple definition of `textview'; edit.o:(.bss+0x80): first defined here /usr/bin/ld: search.o:(.bss+0x88): multiple definition of `bar'; edit.o:(.bss+0x88): first defined here /usr/bin/ld: search.o:(.bss+0x90): multiple definition of `viewport'; edit.o:(.bss+0x90): first defined here /usr/bin/ld: search.o:(.bss+0x98): multiple definition of `table_info'; edit.o:(.bss+0x98): first defined here /usr/bin/ld: search.o:(.bss+0xa0): multiple definition of `sysicon'; edit.o:(.bss+0xa0): first defined here /usr/bin/ld: search.o:(.bss+0xa8): multiple definition of `ac'; edit.o:(.bss+0xa8): first defined here /usr/bin/ld: terminal-actions.o:(.bss+0x0): multiple definition of `notebook'; edit.o:(.bss+0x0): first defined here /usr/bin/ld: terminal-actions.o:(.bss+0x20): multiple definition of `byte_info'; edit.o:(.bss+0x20): first defined here /usr/bin/ld:
Processed: fix found version
Processing commands for cont...@bugs.debian.org: > found 952026 3:4.7.6-1 Bug #952026 [node-handlebars] ruby-handlebars-assets: FTBFS with current libjs-handlebars version: ERROR: ExecJS::ProgramError: ReferenceError: Handlebars is not defined There is no source info for the package 'node-handlebars' at version '3:4.7.6-1' with architecture '' Unable to make a source version for version '3:4.7.6-1' Marked as found in versions 3:4.7.6-1. > End of message, stopping processing here. Please contact me if you need assistance. -- 952026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952026: fixed in node-handlebars
Control: reassign -1 node-handlebars
Control: affects -1 ruby-handlebars-assets
Control: found -1 3:4.7.6-2
> I debugged this case and looked into the FTBFS of
ruby-handlebas-assets. I
> checked out the upstream git repository and it tests just fine even
when I
> raise the haml and rake gem versions to match the ones in Debian.
But it fails
> with exactly the same error if I replace the javascript files in
> vendor/assets/javascript by the javascript files provided by
libjs-handlebars.
> So there seems to be some incompatbility or difference with these
files
> actually causing the build issue (and I don't believe it's the
version
> difference of 4.7.2 vs 4.7.3).
> Regards, Daniel
Hi Daniel,
Thanks for this information. It gave me an idea to diff between the two
files and I found the embedded handlebars files were using 'this' and
our builds were using 'window'.
@@ -33,5178 +7,476 @@ THE SOFTWARE.
exports["Handlebars"] = factory();
else
root["Handlebars"] = factory();
-})(this, function() {
+})(window, function() {
return /**/ (function(modules) { // webpackBootstrap
/**/ // The module cache
/**/ var installedModules = {};
Looking around I found webpack option to pass globalObject: 'this' to
match this format. This option allows the code to run same code on both
node and browser.
Fixed node-handlebars and will upload now.
Processed: fixed in node-handlebars
Processing control commands: > reassign -1 node-handlebars Bug #952026 [src:ruby-handlebars-assets] ruby-handlebars-assets: FTBFS with current libjs-handlebars version: ERROR: ExecJS::ProgramError: ReferenceError: Handlebars is not defined Bug reassigned from package 'src:ruby-handlebars-assets' to 'node-handlebars'. No longer marked as found in versions ruby-handlebars-assets/2:0.23.3+dfsg-2. Ignoring request to alter fixed versions of bug #952026 to the same values previously set > affects -1 ruby-handlebars-assets Bug #952026 [node-handlebars] ruby-handlebars-assets: FTBFS with current libjs-handlebars version: ERROR: ExecJS::ProgramError: ReferenceError: Handlebars is not defined Added indication that 952026 affects ruby-handlebars-assets > found -1 3:4.7.6-2 Bug #952026 [node-handlebars] ruby-handlebars-assets: FTBFS with current libjs-handlebars version: ERROR: ExecJS::ProgramError: ReferenceError: Handlebars is not defined There is no source info for the package 'node-handlebars' at version '3:4.7.6-2' with architecture '' Unable to make a source version for version '3:4.7.6-2' Marked as found in versions 3:4.7.6-2. -- 952026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970341: rampler: autopkgtest failure on arm64:
Source: rampler Version: 1.1.1-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package rampler, great. However, it fails on arm64. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The test could be a bit more verbose? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=rampler https://ci.debian.net/data/autopkgtest/testing/amd64/r/rampler/6794192/log.gz autopkgtest [03:14:35]: test run-unit-test: [--- [93m[1mPreparation[0m [92m[1mPassed[0m [93m[1mTest 1[0m autopkgtest [03:14:35]: test run-unit-test: ---] signature.asc Description: OpenPGP digital signature
Bug#970340: rna-star: autopkgtest regression: --genomeSAindexNbases 8 is too large for the genome size=99940
Source: rna-star Version: 2.7.5c+dfsg-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of rna-star the autopkgtest of rna-star fails in testing when that autopkgtest is run with the binary packages of rna-star from unstable. It passes when run with only packages from testing. In tabular form: passfail rna-star from testing2.7.5c+dfsg-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=rna-star https://ci.debian.net/data/autopkgtest/testing/amd64/r/rna-star/7008363/log.gz autopkgtest [20:08:01]: test command1: [--- Sep 13 20:08:01 . started STAR run Sep 13 20:08:01 ... starting to generate Genome files Sep 13 20:08:01 . processing annotations GTF ! WARNING: --genomeSAindexNbases 8 is too large for the genome size=99940, which may cause seg-fault at the mapping step. Re-run genome generation with recommended --genomeSAindexNbases 7 Sep 13 20:08:01 ... starting to sort Suffix Array. This may take a long time... Sep 13 20:08:01 ... sorting Suffix Array chunks and saving them to disk... Sep 13 20:08:01 ... loading chunks from disk, packing SA... Sep 13 20:08:01 ... finished generating suffix array Sep 13 20:08:01 ... generating Suffix Array index Sep 13 20:08:01 ... completed Suffix Array index Sep 13 20:08:01 ... writing Genome to disk ... Sep 13 20:08:01 ... writing Suffix Array to disk ... Sep 13 20:08:01 ... writing SAindex to disk Sep 13 20:08:01 . finished successfully Sep 13 20:08:01 . started STAR run Sep 13 20:08:01 . loading genome Sep 13 20:08:01 . started mapping Sep 13 20:08:02 . finished mapping Sep 13 20:08:02 . finished successfully autopkgtest [20:08:02]: test command1: ---] autopkgtest [20:08:02]: test command1: - - - - - - - - - - results - - - - - - - - - - command1 FAIL stderr: ! WARNING: --genomeSAindexNbases 8 is too large for the genome size=99940, which may cause seg-fault at the mapping step. Re-run genome generation with recommended --genomeSAindexNbases 7 signature.asc Description: OpenPGP digital signature
Processed: libobject-pad-perl breaks libtickit-widget-tabbed-perl autopkgtest: Failed test 'all modules in libtickit-widget-tabbed-perl pass the syntax check'
Processing control commands: > found -1 libobject-pad-perl/0.32-1 Bug #970339 [src:libobject-pad-perl, src:libtickit-widget-tabbed-perl] libobject-pad-perl breaks libtickit-widget-tabbed-perl autopkgtest: Failed test 'all modules in libtickit-widget-tabbed-perl pass the syntax check' Marked as found in versions libobject-pad-perl/0.32-1. > found -1 libtickit-widget-tabbed-perl/0.023-1 Bug #970339 [src:libobject-pad-perl, src:libtickit-widget-tabbed-perl] libobject-pad-perl breaks libtickit-widget-tabbed-perl autopkgtest: Failed test 'all modules in libtickit-widget-tabbed-perl pass the syntax check' Marked as found in versions libtickit-widget-tabbed-perl/0.023-1. -- 970339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970339: libobject-pad-perl breaks libtickit-widget-tabbed-perl autopkgtest: Failed test 'all modules in libtickit-widget-tabbed-perl pass the syntax check'
Source: libobject-pad-perl, libtickit-widget-tabbed-perl Control: found -1 libobject-pad-perl/0.32-1 Control: found -1 libtickit-widget-tabbed-perl/0.023-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of libobject-pad-perl the autopkgtest of libtickit-widget-tabbed-perl fails in testing when that autopkgtest is run with the binary packages of libobject-pad-perl from unstable. It passes when run with only packages from testing. In tabular form: passfail libobject-pad-perl from testing0.32-1 libtickit-widget-tabbed-perl from testing0.023-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of libobject-pad-perl to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=libobject-pad-perl https://ci.debian.net/data/autopkgtest/testing/amd64/libt/libtickit-widget-tabbed-perl/7009729/log.gz Test Summary Report --- /usr/share/pkg-perl-autopkgtest/runtime-deps-and-recommends.d/syntax.t (Wstat: 256 Tests: 4 Failed: 1) Failed test: 4 Non-zero exit status: 1 Files=1, Tests=4, 0 wallclock secs ( 0.01 usr 0.01 sys + 0.18 cusr 0.03 csys = 0.23 CPU) Result: FAIL signature.asc Description: OpenPGP digital signature
Bug#970338: libobject-pad-perl breaks libtickit-console-perl autopkgtest: Failed test 'all modules in libtickit-console-perl pass the syntax check'
Source: libobject-pad-perl, libtickit-console-perl Control: found -1 libobject-pad-perl/0.32-1 Control: found -1 libtickit-console-perl/0.09-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of libobject-pad-perl the autopkgtest of libtickit-console-perl fails in testing when that autopkgtest is run with the binary packages of libobject-pad-perl from unstable. It passes when run with only packages from testing. In tabular form: passfail libobject-pad-perl from testing0.32-1 libtickit-console-perl from testing0.09-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of libobject-pad-perl to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=libobject-pad-perl https://ci.debian.net/data/autopkgtest/testing/amd64/libt/libtickit-console-perl/7008360/log.gz Test Summary Report --- /usr/share/pkg-perl-autopkgtest/runtime-deps-and-recommends.d/syntax.t (Wstat: 256 Tests: 4 Failed: 1) Failed test: 4 Non-zero exit status: 1 Files=1, Tests=4, 0 wallclock secs ( 0.02 usr 0.00 sys + 0.12 cusr 0.04 csys = 0.18 CPU) Result: FAIL signature.asc Description: OpenPGP digital signature
Processed: libobject-pad-perl breaks libtickit-console-perl autopkgtest: Failed test 'all modules in libtickit-console-perl pass the syntax check'
Processing control commands: > found -1 libobject-pad-perl/0.32-1 Bug #970338 [src:libobject-pad-perl, src:libtickit-console-perl] libobject-pad-perl breaks libtickit-console-perl autopkgtest: Failed test 'all modules in libtickit-console-perl pass the syntax check' Marked as found in versions libobject-pad-perl/0.32-1. > found -1 libtickit-console-perl/0.09-1 Bug #970338 [src:libobject-pad-perl, src:libtickit-console-perl] libobject-pad-perl breaks libtickit-console-perl autopkgtest: Failed test 'all modules in libtickit-console-perl pass the syntax check' Marked as found in versions libtickit-console-perl/0.09-1. -- 970338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970336: ecl breaks cl-contextl autopkgtest: not of the expected type SYMBOL
Source: ecl, cl-contextl Control: found -1 ecl/20.4.24+ds-1 Control: found -1 cl-contextl/1:20160313.git5894fba-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of ecl the autopkgtest of cl-contextl fails in testing when that autopkgtest is run with the binary packages of ecl from unstable. It passes when run with only packages from testing. In tabular form: passfail eclfrom testing20.4.24+ds-1 cl-contextlfrom testing1:20160313.git5894fba-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of ecl to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=ecl https://ci.debian.net/data/autopkgtest/testing/amd64/c/cl-contextl/7008359/log.gz ;;; ;;; Compiling figure-editor-2.lisp. ;;; OPTIMIZE levels: Safety=2, Space=0, Speed=3, Debug=0 ;;; ;;; End of Pass 1. ;;; Finished compiling figure-editor-2.lisp. ;;; real time : 17.420 secs run time : 20.101 secs gc count : 612 times consed: 2707204576 bytes real time : 18.996 secs run time : 21.757 secs gc count : 652 times consed: 2886437424 bytes :DONE :DONE An error occurred during initialization: In function SYMBOL-VALUE, the value of the only argument is "Dr. Jekyll" which is not of the expected type SYMBOL. signature.asc Description: OpenPGP digital signature
Processed: ecl breaks cl-contextl autopkgtest: not of the expected type SYMBOL
Processing control commands: > found -1 ecl/20.4.24+ds-1 Bug #970336 [src:ecl, src:cl-contextl] ecl breaks cl-contextl autopkgtest: not of the expected type SYMBOL Marked as found in versions ecl/20.4.24+ds-1. > found -1 cl-contextl/1:20160313.git5894fba-1 Bug #970336 [src:ecl, src:cl-contextl] ecl breaks cl-contextl autopkgtest: not of the expected type SYMBOL Marked as found in versions cl-contextl/1:20160313.git5894fba-1. -- 970336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970335: ecl breaks cffi autopkgtest: Don't know how to REQUIRE rt..
Source: ecl, cffi Control: found -1 ecl/20.4.24+ds-1 Control: found -1 cffi/1:0.22.1-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of ecl the autopkgtest of cffi fails in testing when that autopkgtest is run with the binary packages of ecl from unstable. It passes when run with only packages from testing. In tabular form: passfail eclfrom testing20.4.24+ds-1 cffi from testing1:0.22.1-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of ecl to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=ecl https://ci.debian.net/data/autopkgtest/testing/amd64/c/cffi/7008137/log.gz ;;; Compiling /usr/share/common-lisp/source/bordeaux-threads/src/impl-ecl.lisp. ;;; OPTIMIZE levels: Safety=2, Space=0, Speed=3, Debug=0 ;;; ;;; End of Pass 1. ;;; Finished compiling /usr/share/common-lisp/source/bordeaux-threads/src/impl-ecl.lisp. ;;; ;;; ;;; Compiling /usr/share/common-lisp/source/bordeaux-threads/src/default-implementations.lisp. ;;; OPTIMIZE levels: Safety=2, Space=0, Speed=3, Debug=0 ;;; ;;; End of Pass 1. ;;; Finished compiling /usr/share/common-lisp/source/bordeaux-threads/src/default-implementations.lisp. ;;; An error occurred during initialization: Module error: Don't know how to REQUIRE rt.. signature.asc Description: OpenPGP digital signature
Processed: ecl breaks cffi autopkgtest: Don't know how to REQUIRE rt..
Processing control commands: > found -1 ecl/20.4.24+ds-1 Bug #970335 [src:ecl, src:cffi] ecl breaks cffi autopkgtest: Don't know how to REQUIRE rt.. Marked as found in versions ecl/20.4.24+ds-1. > found -1 cffi/1:0.22.1-1 Bug #970335 [src:ecl, src:cffi] ecl breaks cffi autopkgtest: Don't know how to REQUIRE rt.. Marked as found in versions cffi/1:0.22.1-1. -- 970335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970335 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: wslay: autopkgtest needs update for new version of cmake: warning on stderr
Processing control commands: > affects -1 src:cmake Bug #970334 [src:wslay] wslay: autopkgtest needs update for new version of cmake: warning on stderr Added indication that 970334 affects src:cmake -- 970334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970334: wslay: autopkgtest needs update for new version of cmake: warning on stderr
Source: wslay Version: 1.1.1-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, cm...@packages.debian.org Tags: sid bullseye User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:cmake Dear maintainer(s), With a recent upload of cmake the autopkgtest of wslay fails in testing when that autopkgtest is run with the binary packages of cmake from unstable. It passes when run with only packages from testing. In tabular form: passfail cmake from testing3.18.2-1 wslay from testing1.1.1-1 all others from testingfrom testing I copied some of the output at the bottom of this report. The output contains a warning that's written to stderr. By default that fails a test. If you can't fix the underlying cause, you can have the output to stderr ignored by adding an allow-stderr restriction to the test specification. Currently this regression is blocking the migration of cmake to testing [1]. Of course, cmake shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in cmake was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from cmake should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=cmake https://ci.debian.net/data/autopkgtest/testing/amd64/w/wslay/7008132/log.gz autopkgtest [18:08:26]: test build1: - - - - - - - - - - results - - - - - - - - - - build1 FAIL stderr: CMake Warning (dev) at /usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:273 (message): autopkgtest [18:08:26]: test build1: - - - - - - - - - - stderr - - - - - - - - - - CMake Warning (dev) at /usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:273 (message): The package name passed to `find_package_handle_standard_args` (NETTLE) does not match the name of the calling package (Nettle). This can lead to problems in calling code that expects `find_package` result variables (e.g., `_FOUND`) to follow a certain pattern. Call Stack (most recent call first): FindNettle.cmake:15 (find_package_handle_standard_args) CMakeLists.txt:10 (find_package) This warning is for project developers. Use -Wno-dev to suppress it. signature.asc Description: OpenPGP digital signature
Bug#970333: abseil: autopkgtest needs update for new version of cmake: warning on stderr
Source: abseil Version: 0~20200225.2-3 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, cm...@packages.debian.org Tags: sid bullseye User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:cmake Dear maintainer(s), With a recent upload of cmake the autopkgtest of abseil fails in testing when that autopkgtest is run with the binary packages of cmake from unstable. It passes when run with only packages from testing. In tabular form: passfail cmake from testing3.18.2-1 abseil from testing0~20200225.2-3 all others from testingfrom testing I copied some of the output at the bottom of this report. The output contains a warning that's written to stderr. By default that fails a test. If you can't fix the underlaying cause, you can have the output to stderr ignored by adding an allow-stderr restriction to the test specification. Currently this regression is blocking the migration of cmake to testing [1]. Of course, cmake shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in cmake was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from cmake should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=cmake https://ci.debian.net/data/autopkgtest/testing/amd64/a/abseil/7009726/log.gz autopkgtest [22:32:41]: test cmake: - - - - - - - - - - results - - - - - - - - - - cmakeFAIL stderr: CMake Warning (dev) at /usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:273 (message): autopkgtest [22:32:41]: test cmake: - - - - - - - - - - stderr - - - - - - - - - - CMake Warning (dev) at /usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:273 (message): The package name passed to `find_package_handle_standard_args` (Threads) does not match the name of the calling package (absl). This can lead to problems in calling code that expects `find_package` result variables (e.g., `_FOUND`) to follow a certain pattern. Call Stack (most recent call first): /usr/share/cmake-3.18/Modules/FindThreads.cmake:234 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) /usr/lib/x86_64-linux-gnu/cmake/absl/abslConfig.cmake:3 (include) CMakeLists.txt:5 (find_package) This warning is for project developers. Use -Wno-dev to suppress it. signature.asc Description: OpenPGP digital signature
Processed: abseil: autopkgtest needs update for new version of cmake: warning on stderr
Processing control commands: > affects -1 src:cmake Bug #970333 [src:abseil] abseil: autopkgtest needs update for new version of cmake: warning on stderr Added indication that 970333 affects src:cmake -- 970333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970333 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957636: marked as done (opencpn: ftbfs with GCC-10)
Your message dated Mon, 14 Sep 2020 21:18:01 +0200 with message-id and subject line opencpn builds using gcc-10 has caused the Debian Bug report #957636, regarding opencpn: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957636 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:opencpn Version: 5.0.0+dfsg-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/opencpn_5.0.0+dfsg-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] /usr/bin/ld: libGARMINHOST.a(gpsusbcommon.c.o):./obj-x86_64-linux-gnu/./src/garmin/jeeps/gpsprot.h:202: multiple definition of `gps_run_transfer'; libGARMINHOST.a(garmin_wrapper.cpp.o):./obj-x86_64-linux-gnu/./src/garmin/jeeps/gpsprot.h:202: first defined here /usr/bin/ld: libGARMINHOST.a(gpsusbcommon.c.o):./obj-x86_64-linux-gnu/./src/garmin/jeeps/gpsprot.h:196: multiple definition of `gps_lap_transfer'; libGARMINHOST.a(garmin_wrapper.cpp.o):./obj-x86_64-linux-gnu/./src/garmin/jeeps/gpsprot.h:196: first defined here /usr/bin/ld: libGARMINHOST.a(gpsusbcommon.c.o):./obj-x86_64-linux-gnu/./src/garmin/jeeps/gpsprot.h:190: multiple definition of `gps_pvt_transfer'; libGARMINHOST.a(garmin_wrapper.cpp.o):./obj-x86_64-linux-gnu/./src/garmin/jeeps/gpsprot.h:190: first defined here /usr/bin/ld: libGARMINHOST.a(gpsusbcommon.c.o):./obj-x86_64-linux-gnu/./src/garmin/jeeps/gpsprot.h:183: multiple definition of `gps_position_transfer'; libGARMINHOST.a(garmin_wrapper.cpp.o):./obj-x86_64-linux-gnu/./src/garmin/jeeps/gpsprot.h:183: first defined here /usr/bin/ld: libGARMINHOST.a(gpsusbcommon.c.o):./obj-x86_64-linux-gnu/./src/garmin/jeeps/gpsprot.h:171: multiple definition of `gps_date_time_transfer'; libGARMINHOST.a(garmin_wrapper.cpp.o):./obj-x86_64-linux-gnu/./src/garmin/jeeps/gpsprot.h:171: first defined here /usr/bin/ld: libGARMINHOST.a(gpsusbcommon.c.o):./obj-x86_64-linux-gnu/./src/garmin/jeeps/gpsprot.h:164: multiple definition of `gps_almanac_transfer'; libGARMINHOST.a(garmin_wrapper.cpp.o):./obj-x86_64-linux-gnu/./src/garmin/jeeps/gpsprot.h:164: first defined here /usr/bin/ld: libGARMINHOST.a(gpsusbcommon.c.o):./obj-x86_64-linux-gnu/./src/garmin/jeeps/gpsprot.h:158: multiple definition of `gps_prx_waypt_transfer'; libGARMINHOST.a(garmin_wrapper.cpp.o):./obj-x86_64-linux-gnu/./src/garmin/jeeps/gpsprot.h:158: first defined here /usr/bin/ld: libGARMINHOST.a(gpsusbcommon.c.o):./obj-x86_64-linux-gnu/./src/garmin/jeeps/gpsprot.h:152: multiple definition of `gps_trk_transfer'; libGARMINHOST.a(garmin_wrapper.cpp.o):./obj-x86_64-linux-gnu/./src/garmin/jeeps/gpsprot.h:152: first defined here /usr/bin/ld: libGARMINHOST.a(gpsusbcommon.c.o):./obj-x86_64-linux-gnu/./src/garmin/jeeps/gpsprot.h:143: multiple definition of `gps_route_transfer'; libGARMINHOST.a(garmin_wrapper.cpp.o):./obj-x86_64-linux-gnu/./src/garmin/jeeps/gpsprot.h:143: first defined here /usr/bin/ld: libGARMINHOST.a(gpsusbcommon.c.o):./obj-x86_64-linux-gnu/./src/garmin/jeeps/gpsprot.h:136: multiple definition of `gps_category_transfer'; libGARMINHOST.a(garmin_wrapper.cpp.o):./obj-x86_64-linux-gnu/./src/garmin/jeeps/gpsprot.h:136: first defined here /usr/bin/ld: libGARMINHOST.a(gpsusbcommon.c.o):./obj-x86_64-linux-gnu/./src/garmin/jeeps/gpsprot.h:130: multiple definition of `gps_waypt_transfer';
Processed: src:r-cran-mice: fails to migrate to testing for too long: autopkgtest regression
Processing control commands:
> close -1 3.10.0-1
Bug #970330 [src:r-cran-mice] src:r-cran-mice: fails to migrate to testing for
too long: autopkgtest regression
Marked as fixed in versions r-cran-mice/3.10.0-1.
Bug #970330 [src:r-cran-mice] src:r-cran-mice: fails to migrate to testing for
too long: autopkgtest regression
Marked Bug as done
> block -1 by 969494
Bug #970330 {Done: Paul Gevers } [src:r-cran-mice]
src:r-cran-mice: fails to migrate to testing for too long: autopkgtest
regression
970330 was not blocked by any bugs.
970330 was not blocking any bugs.
Added blocking bug(s) of 970330: 969494
--
970330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#970330: src:r-cran-mice: fails to migrate to testing for too long: autopkgtest regression
Source: r-cran-mice Version: 3.9.0-2 Severity: serious Control: close -1 3.10.0-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 969494 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:r-cran-mice 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 immediately closed this bug with the version in unstable, 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=r-cran-mice signature.asc Description: OpenPGP digital signature
Bug#969608: makeblastdb 2.10.x on 32-bit architectures
Hi Aaron, Aaron M. Ucko, on 2020-09-13 22:44:00 -0400: > Étienne Mollier writes: > > > regression looks still there in version 2.10.0-3, at least on > > arm64 architecture. > > How can I reproduce it? I worked within an arm64 schroot built with sbuild-createchroot, on a native amd64 machine. The reproducer is the test from Biopython stored in Tests/test_NCBI_BLAST_tools.py, which boils down to running the command: makeblastdb \ -in NC_005816.faa \ -dbtype prot \ -hash_index \ -max_file_sz 20MB \ -parse_seqids \ -taxid 10 where NC_005816.faa can be obtained from the Biopython test suite on Salsa: https://salsa.debian.org/med-team/python-biopython/-/raw/master/Tests/GenBank/NC_005816.faa When I run it within that arm64 environment, I get the following output, and the error code 255 sent back to the shell: Building a new DB, current time: 09/14/2020 18:35:05 New DB name: /tmp/NC_005816.faa New DB title: NC_005816.faa Sequence type: Protein Keep MBits: T Maximum file size: 2000B No volumes were created. Error: mdb_env_open: Cannot allocate memory while specifying "-blastdb_version 4" in additions restores the former behavior: Building a new DB, current time: 09/14/2020 18:44:51 New DB name: /tmp/NC_005816.faa New DB title: NC_005816.faa Sequence type: Protein Deleted existing Protein BLAST database named /tmp/NC_005816.faa Keep MBits: T Maximum file size: 2000B Adding sequences from FASTA; added 10 sequences in 0.0821829 seconds. I haven't straced the execution of the program to check the amount of memory in map, so maybe the issue is different but with similar symptoms as previously? > AFAICT python-biopython's autopkgtest boils > down to the upstream test suite, which runs fine as part of a build of > revision 15084ca (immediately preceding your patch to drop back to > version 4 on selected architectures) on the porterbox amdahl. Perhaps > system limits come into play in some other environments, but then I > expect they would have done the same on 2.10.0-1. Also, the telltale > warning > > > /<>/c++/include/objtools/blast/seqdb_writer/writedb_lmdb.hpp:52:59: > warning: integer overflow in expression of type ‘int’ results in > ‘-647710720’ [-Woverflow] > > occurs only in the logs for 2.10.0-2. Ouch, looks good to know, thank you for the warning. Kind Regards, -- Étienne Mollier Old rsa/3072: 5ab1 4edf 63bb ccff 8b54 2fa9 59da 56fe fff3 882d New rsa/4096: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity. signature.asc Description: PGP signature
Bug#962213: marked as done (package ftbfs on arm64 and armhf)
Your message dated Mon, 14 Sep 2020 16:48:41 + with message-id and subject line Bug#962213: fixed in opencpn 5.2.0+dfsg1-1 has caused the Debian Bug report #962213, regarding package ftbfs on arm64 and 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.) -- 962213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: opencpn Version: 5.0.0+dfsg-1 Severity: serious Tags: sid bullseye patch The package ftbfs on arm64 and armhf, trying to link with -ldrm. Apparently libdrm-dev is an implicit b-d for x86 targets, but used explicitly. Fixed by b-d on libdrm-dev everywhere. --- End Message --- --- Begin Message --- Source: opencpn Source-Version: 5.2.0+dfsg1-1 Done: Alec Leamas We believe that the bug you reported is fixed in the latest version of opencpn, 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 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alec Leamas (supplier of updated opencpn 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, 13 Sep 2020 21:51:16 +0200 Source: opencpn Architecture: source Version: 5.2.0+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Alec Leamas Changed-By: Alec Leamas Closes: 948702 962213 Changes: opencpn (5.2.0+dfsg1-1) unstable; urgency=medium . * New upstream release including plugin downloader. Closes: #948702 * Add Build-Depends libdrm-dev. Closes: #962213 * Adjust libcurl b-d, add libcurl4-openssl-dev alternative. * Update Replace/Break to match actual release. * Update debian/copyright due to new upstream source layout. * Drop opencpn-plugins transition package. * Bump Standards-Version to 4.5.0, no changes. * Replace override_dh_install with declarative stuff. * Move debian source hosting to https://gitlab.com/leamas/opencpn. * Drop upstreamed patches and rebase remaining one. * New patches: - Add a warning for downloaded, binary plugin contents -- 0008-pluginmanager-conditional-warning-for-plugin-binary-.patch - Add udev rule installation patch - opencpn#1988. - Add metadata installation patch - opencpn#1989. - Remove bogus svg file - opencpn#1990. - Fix cmake parallel execution problem - opencpn#1991. - Add two plugin compatibility patches - opencpn#1997. - Drop pdf file without source -- 0010-build-Drop-CoC-909_2013-InlandECDIS_20170308s.pdf.patch Checksums-Sha1: ceaaf03779c8e9af46b5002f5021b510cd756a07 2215 opencpn_5.2.0+dfsg1-1.dsc bcb6c90b9d88637013b7e04cd1320ec1908cd688 18230328 opencpn_5.2.0+dfsg1.orig.tar.xz 58642d791d6dc05b9dd4a26b6013f78fb30505bf 26536 opencpn_5.2.0+dfsg1-1.debian.tar.xz 4c7c61adb3f923c2c6288928aabb41698a1223ea 12493 opencpn_5.2.0+dfsg1-1_source.buildinfo Checksums-Sha256: 5fadc84fe88dc6aac2405ea0cd145d2e85ef1e6a9702f7189cfcbfaa5978d084 2215 opencpn_5.2.0+dfsg1-1.dsc 7d715d3bbb0f990fe42b8ee4839f8abb40d98ce1f2efa2c1ead6e4f91d5528cd 18230328 opencpn_5.2.0+dfsg1.orig.tar.xz 5153541c86b27b70c5f67c4e9079658e7cef3ff9d1f59a0b40b41533dded569f 26536 opencpn_5.2.0+dfsg1-1.debian.tar.xz d56eb53c064117df8070680867d31731af2f7e2be955a24c7b0dab8ae78dbe10 12493 opencpn_5.2.0+dfsg1-1_source.buildinfo Files: f407703915fb3d668298fbf950659d9d 2215 misc optional opencpn_5.2.0+dfsg1-1.dsc d6d22a22d5f1ea0c295208e19e5323a2 18230328 misc optional opencpn_5.2.0+dfsg1.orig.tar.xz e81bcce82132b41e1df7a58dda699565 26536 misc optional opencpn_5.2.0+dfsg1-1.debian.tar.xz 0d824a86e054c8f5876767ac033b157b 12493 misc optional opencpn_5.2.0+dfsg1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAl9fmV0ACgkQkWT6HRe9 XTZS3BAAvaL4Ak1QOLkUYGWjZsgewhTUaTtbHJ+UewTwzIvnaQyHV2XPmGKM2xUv t0eNzxHDPABN+oiQP8nyeO0NPBkpfGUbSqY1p5Sm4j+e6d4sGa5WJlZA11WuwpUf LSgvYotxSzbC96k40wcNh+72nq4XyX9o1tt2nKNqdTpaebtuLa6QoGGxppw86QzR +3yD0q4wRQvVYqk8z6D+aB6h0ibZJelk9aHH3F6wtHfIYQtm6oCfsPmcfbDQ6OBv AGvvrCuarcCgniSLId+sUDifjiB+nz+dDj4rGuQ1SGJZhYocE54zFdUHL6qb1WTy wQ1s35ZB5be8DJko97wY8eTar7ancDwjAsVKCo99E6/qH/8bqYIGUP6Yt+qBgaen
Bug#969092: marked as done (spoa: Either FTBFS or baseline violation on all architectures)
Your message dated Mon, 14 Sep 2020 15:33:53 + with message-id and subject line Bug#969092: fixed in spoa 3.4.0+ds-2 has caused the Debian Bug report #969092, regarding spoa: Either FTBFS or baseline violation on all architectures 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.) -- 969092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969092 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spoa Version: 3.4.0+ds-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=spoa=3.4.0%2Bds-1 Please disable spoa_optimize_for_native again. --- End Message --- --- Begin Message --- Source: spoa Source-Version: 3.4.0+ds-2 Done: Shayan Doust We believe that the bug you reported is fixed in the latest version of spoa, 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 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Shayan Doust (supplier of updated spoa 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: Mon, 14 Sep 2020 12:43:15 +0100 Source: spoa Architecture: source Version: 3.4.0+ds-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Shayan Doust Closes: 969092 Changes: spoa (3.4.0+ds-2) unstable; urgency=medium . * Team upload. * Disable use of native code generation (Closes: #969092) * Update symbols file Checksums-Sha1: 9852dc321d30f38a6611691d0c123c34706f5515 2153 spoa_3.4.0+ds-2.dsc 9c0ce21f734be52191d13b2af0c96223545fedc1 7924 spoa_3.4.0+ds-2.debian.tar.xz 34900bda8854f5e589f58278cc2bf6f876d2c82d 7549 spoa_3.4.0+ds-2_amd64.buildinfo Checksums-Sha256: dc2ed3576292e02fe78614f9250ad4bd8ed461ed6dc936d1c3098a8b6a8c0cdf 2153 spoa_3.4.0+ds-2.dsc 069007af75a08c1563515bf40bee0728c636d4772e9e1684828f25c758c6f6d9 7924 spoa_3.4.0+ds-2.debian.tar.xz 6d83e28b37d6ac89c4741b6155ccf2ea17b1782d3680679a82babb4c4d1d3acd 7549 spoa_3.4.0+ds-2_amd64.buildinfo Files: 42c5d35a02a4560e5869d579a886cae5 2153 science optional spoa_3.4.0+ds-2.dsc 1481a65f7095bfa9d8d0191f90a40e52 7924 science optional spoa_3.4.0+ds-2.debian.tar.xz cd1a934064e5f732b4acd97fc7472e9b 7549 science optional spoa_3.4.0+ds-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJUBAEBCgA+FiEEBAGoEKbyQwMeo5dZbX1EGRnQI5UFAl9fh9ogHHMuZG91c3RA c3R1ZGVudC5saXZlcnBvb2wuYWMudWsACgkQbX1EGRnQI5XwFw/7B34GV0Nb7IWo 2zTwj93fFgqB+Sh9Qfayk3MW6jawBHJke51h9GsKntIjYYzWo2tc90a/Bl2nbrw3 /S6mDhr525DKSV6QwhFo8LEkcobPXST6lEmcd/gr08H8RLmwETYoOATzhwpswEhs LC2OJ6BUVITUGpmI8NhLygIejmSsHN0xy8Ol5ShZx4GKIULKQ1IF9V88Qoukvwet qGaJNGBclYRrf33TTt40TuM8k/8JgWQYaBzSRYyRhPgJP37cImgmrkD4MTujh/Qa oHj2BP5O/hpctfXuSExEm34hZ8GX9JXau/6L9dE391NMrQ0C0zlkk6QWVkB3ho0Q rbCJ3tYSWOMzZfcAyIhD0mXzkVMLZtMD3a1VLZFvNmbCLIgHxBzYhFrdPE8wSdtl gLNJaFjx9bNX9c2JeZZB6doYrVs78vcxAJbIXnTD9J15XhXQ3Dfumt63Kxd59phb n7PlhvHETvGqPfMcE8ToUxEjn8Vzflf9DhzV65reB9+qZxq5Oe8jq87Y0nBYnY1g NcPySIsvUq5IpscstALLKrjClRS3DoMpY9hk2vP7Rtp33Vuy9yTd+/51y3Nduf1H lh9XJrzXbGhPOl6e54r+PdHLdMVoPvyzEVAAnT9tNJwfs5ldsmszr4zs3W8snH/A GNsOB6xTtlnE9z36ntTt3TX6c1KolEo= =+DgY -END PGP SIGNATURE End Message ---
Bug#966436: marked as done (scrambled property in identify -verbose output)
Your message dated Mon, 14 Sep 2020 14:37:51 + with message-id and subject line Bug#966436: fixed in ruby-mini-magick 4.10.1-1 has caused the Debian Bug report #966436, regarding scrambled property in identify -verbose output 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.) -- 966436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966436 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-mini-magick Version: 4.9.5-2 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-mini-magick.html ... Failures: 1) With ImageMagick MiniMagick::Image#details when verbose information includes a clipping path does not hang when parsing verbose data Failure/Error: details_hash[last_key] << line NoMethodError: undefined method `<<' for # Did you mean? < # ./lib/mini_magick/image/info.rb:139:in `block in details' # ./lib/mini_magick/image/info.rb:128:in `each' # ./lib/mini_magick/image/info.rb:128:in `each_with_object' # ./lib/mini_magick/image/info.rb:128:in `details' # ./lib/mini_magick/image/info.rb:31:in `[]' # ./lib/mini_magick/image.rb:141:in `block in attribute' # ./spec/lib/mini_magick/image_spec.rb:478:in `block (7 levels) in ' # ./spec/lib/mini_magick/image_spec.rb:477:in `block (6 levels) in ' # ./spec/spec_helper.rb:19:in `block (3 levels) in ' Finished in 1 minute 34.34 seconds (files took 21.52 seconds to load) 76 examples, 1 failure ... --- End Message --- --- Begin Message --- Source: ruby-mini-magick Source-Version: 4.10.1-1 Done: Utkarsh Gupta We believe that the bug you reported is fixed in the latest version of ruby-mini-magick, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Utkarsh Gupta (supplier of updated ruby-mini-magick 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, 13 Sep 2020 01:00:27 +0530 Source: ruby-mini-magick Architecture: source Version: 4.10.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Utkarsh Gupta Closes: 966436 966936 Changes: ruby-mini-magick (4.10.1-1) unstable; urgency=medium . [ Cédric Boutillier ] * Refresh packaging with dh-make-ruby * Refresh remove-deprecated-test.patch * Add epoch for imagemagick dependency * Skip a test using details method to circumvent possible bogus output of `identify -verbose` command (see #966436) * Drop skip-tests-temporarily.patch, not needed anymore * TODO: several tests are failing in sbuild because of new imagemagick * Add a patch to fix 'identify' parsing (Closes: #966436) * drop remove-deprecated-test.patch * don't fail fast * Revert "drop remove-deprecated-test.patch" . [ Utkarsh Gupta ] * New upstream version 4.10.1 (Closes: #966936) * Update package wrt cme * Use @d.o address Checksums-Sha1: ae7dcced77c23660ad93e913c615d9a178d5a211 2259 ruby-mini-magick_4.10.1-1.dsc 9111eb72ccc95e82ac3058388f3e635c2e4cf74d 1192455 ruby-mini-magick_4.10.1.orig.tar.gz 5f93c9c00098e2172d730b0832b7193187f82c3e 5928 ruby-mini-magick_4.10.1-1.debian.tar.xz 1424321a9bedb8dd5b095aa5a09534aedc720df1 10355 ruby-mini-magick_4.10.1-1_amd64.buildinfo Checksums-Sha256: 64ff54942ea4750473b93d6919890eb539e5f3fafb74c21ad7f5059efc41092d 2259 ruby-mini-magick_4.10.1-1.dsc e0b50247b84b56b1ceb169fccaacc906367a3e91d8a67db0e5983e31c0beb08c 1192455 ruby-mini-magick_4.10.1.orig.tar.gz 9d5f429ce05369d62e8975853514120aa9e366528d0535077e77fb944da8 5928 ruby-mini-magick_4.10.1-1.debian.tar.xz 6a0daf8fdc1375385213ba4fb5756c3a3cc1dcd6a28aaabf02114e4e2e670542 10355 ruby-mini-magick_4.10.1-1_amd64.buildinfo Files: 976d5aef625f0442fcbe858c4927ca1a 2259 ruby optional ruby-mini-magick_4.10.1-1.dsc d56b7dacf037fc29843db673a17a3c2d 1192455 ruby optional ruby-mini-magick_4.10.1.orig.tar.gz 217a378bb1c44832f38a8458a13521c1 5928 ruby optional ruby-mini-magick_4.10.1-1.debian.tar.xz fdff687a980579dbc33cda7ed10247fe 10355 ruby optional
Bug#966936: marked as done (ruby-mini-magick: FTBFS: ERROR: Test "ruby2.7" failed: NoMethodError:)
Your message dated Mon, 14 Sep 2020 14:37:51 + with message-id and subject line Bug#966936: fixed in ruby-mini-magick 4.10.1-1 has caused the Debian Bug report #966936, regarding ruby-mini-magick: FTBFS: ERROR: Test "ruby2.7" failed: NoMethodError: 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.) -- 966936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966936 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-mini-magick Version: 4.9.5-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > NoMethodError: >undefined method `<<' for # >Did you mean? < > # ./lib/mini_magick/image/info.rb:139:in `block in details' > # ./lib/mini_magick/image/info.rb:128:in `each' > # ./lib/mini_magick/image/info.rb:128:in `each_with_object' > # ./lib/mini_magick/image/info.rb:128:in `details' > # ./lib/mini_magick/image/info.rb:31:in `[]' > # ./lib/mini_magick/image.rb:141:in `block in attribute' > # ./spec/lib/mini_magick/image_spec.rb:478:in `block (7 levels) in (required)>' > # ./spec/lib/mini_magick/image_spec.rb:477:in `block (6 levels) in (required)>' > # ./spec/spec_helper.rb:19:in `block (3 levels) in ' > > Finished in 1.67 seconds (files took 0.47683 seconds to load) > 76 examples, 1 failure > > Failed examples: > > rspec './spec/lib/mini_magick/image_spec.rb[1:1:19:3:1]' # With ImageMagick > MiniMagick::Image#details when verbose information includes a clipping path > does not hang when parsing verbose data > > /usr/bin/ruby2.7 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb failed > ERROR: Test "ruby2.7" failed: The full build log is available from: http://qa-logs.debian.net/2020/08/02/ruby-mini-magick_4.9.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: ruby-mini-magick Source-Version: 4.10.1-1 Done: Utkarsh Gupta We believe that the bug you reported is fixed in the latest version of ruby-mini-magick, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Utkarsh Gupta (supplier of updated ruby-mini-magick 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, 13 Sep 2020 01:00:27 +0530 Source: ruby-mini-magick Architecture: source Version: 4.10.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Utkarsh Gupta Closes: 966436 966936 Changes: ruby-mini-magick (4.10.1-1) unstable; urgency=medium . [ Cédric Boutillier ] * Refresh packaging with dh-make-ruby * Refresh remove-deprecated-test.patch * Add epoch for imagemagick dependency * Skip a test using details method to circumvent possible bogus output of `identify -verbose` command (see #966436) * Drop skip-tests-temporarily.patch, not needed anymore * TODO: several tests are failing in sbuild because of new imagemagick * Add a patch to fix 'identify' parsing (Closes: #966436) * drop remove-deprecated-test.patch * don't fail fast * Revert "drop remove-deprecated-test.patch" . [ Utkarsh Gupta ] * New upstream version 4.10.1 (Closes: #966936) * Update package wrt cme * Use @d.o address Checksums-Sha1: ae7dcced77c23660ad93e913c615d9a178d5a211 2259 ruby-mini-magick_4.10.1-1.dsc 9111eb72ccc95e82ac3058388f3e635c2e4cf74d 1192455 ruby-mini-magick_4.10.1.orig.tar.gz
Bug#970086: marked as done (Unversioned Python removal in sid/bullseye)
Your message dated Mon, 14 Sep 2020 12:18:33 + with message-id and subject line Bug#970086: fixed in android-platform-build 1:8.1.0+r23-4.1 has caused the Debian Bug report #970086, regarding Unversioned Python 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.) -- 970086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:android-platform-build Version: 1:8.1.0+r23-4 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned 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 We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. 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: android-platform-build Source-Version: 1:8.1.0+r23-4.1 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of android-platform-build, 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 970...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated android-platform-build package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 11 Sep 2020 13:37:07 +0200 Source: android-platform-build Architecture: source Version: 1:8.1.0+r23-4.1 Distribution: unstable Urgency: medium Maintainer: Android Tools Maintainers Changed-By: Matthias Klose Closes: 970086 Changes: android-platform-build (1:8.1.0+r23-4.1) unstable; urgency=medium . * Non-maintainer upload. * Explicitly build using dh-python and python2. Closes: #970086. Checksums-Sha1: daf2bc85b20b013f0e811257e4aa89adbda44d68 2911 android-platform-build_8.1.0+r23-4.1.dsc 1dcd34f49bd5b87314afdd7ab2ff5dcbdc4d6554 11620 android-platform-build_8.1.0+r23-4.1.debian.tar.xz b880c4297499979384ce393f5a1a53971853fcac 8454 android-platform-build_8.1.0+r23-4.1_source.buildinfo Checksums-Sha256: 42eb4984f7f8b0ad0fce38da68d715384eac0c29cb558eb7593097b3f6fa92ab 2911 android-platform-build_8.1.0+r23-4.1.dsc 17adba09a36d327cd9ee257bb1b47caad019891a256fcbca7d32432e4471d019 11620 android-platform-build_8.1.0+r23-4.1.debian.tar.xz 567a6e7122cd7a19cf1c0b543da13306f43b57d97a8d40078354ba231db642c2 8454 android-platform-build_8.1.0+r23-4.1_source.buildinfo Files: f8381a35119741fb21c1ef4c8faf59f0 2911 devel optional android-platform-build_8.1.0+r23-4.1.dsc 129fe6b73acb83c1c08ddea8fd91bf56 11620 devel optional android-platform-build_8.1.0+r23-4.1.debian.tar.xz f57dd25df05a9cfc16fec56a3d260553 8454 devel optional android-platform-build_8.1.0+r23-4.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl9bZMEQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9fcIEADOAC7PwmKgZiSLpkm/Fq95Oz2HlaeWyHow le1lzMgnOKopdWDHUdTQp5ANAhTUoyFTlFJTG15uKoeO5+xE7uQe1w8LUzoiG6FK lJ4c93aJ5i/TPzrQdpOsULNX07ZypsMFX3XgM7tqXz20kTtw/JfhG5BlAH6AH6l5 9hdhbt4NZVSy4m8VcUHjY4CaTjognnwOgoldYD2JNOOmYuMzCMSMf5Dcyf9zVJxk gyRi6X0UUmZoX8nz1oAsf9rFQqWU+Jz3mG2PSjgPy/f6OIm/b8NhGkA707iPdFsX HgulC9e2mevO0pwJauruGEXG+NBY9UXE6j1Q0ck/y2Jw91tILfqSMR9vGA1UWaM7 hjFnSlhCyRSNajC8uLpbbk1IHJwVJpqdcpotpoXNZOkg4mfpco0YwOhYy/tgki2k OC+3QFFvoBFfWq/M2hstzsXxNoHquC4aB9Er8tK16nA4+irQIuaf4JQQidLb86qo mvNBxjnk5Yz+4G0hU/FqL4GlkC0q3nqjiWYNP4mYZi98gDCWE7VUR//9PxIPRh6i
Bug#920261: marked as done (ocsinventory-reports doesn't depend on php-zip)
Your message dated Mon, 14 Sep 2020 11:18:52 + with message-id and subject line Bug#920261: fixed in ocsinventory-server 2.8+dfsg1-1 has caused the Debian Bug report #920261, regarding ocsinventory-reports doesn't depend on php-zip 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.) -- 920261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ocsinventory-reports Version: 2.6~RC+dfsg-3 Severity: normal In version 2.6 of ocsinventory-reports, the php-zip package is needed to be able to edit deployment packages after they have already been built. ocsinventory-reports should depend on php-zip -- System Information: Debian Release: 9.6 APT prefers stable APT policy: (500, 'stable'), (10, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/1 CPU core) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ocsinventory-reports depends on: ii default-mysql-client1.0.2 ii ieee-data 20160613.1 ii javascript-common 11 ii libapache2-mod-php 1:7.0+49 ii libapache2-mod-php7.0 [libapache2-mod-php] 7.0.33-0+deb9u1 ii libjs-bootstrap 3.3.7+dfsg-2 ii libjs-jquery3.1.1-2 ii libjs-jquery-datatables 1.10.13+dfsg-2 ii libjs-jquery-file-upload9.25.0-1 ii libjs-jquery-migrate-1 1.4.1-1 ii libjs-jquery-ui 1.12.1+dfsg-4 ii libjs-select2.js4.0.1~dfsg1-1 ii mariadb-client-10.1 [virtual-mysql-client] 10.1.37-0+deb9u1 ii perl5.28.1-3 ii php 1:7.0+49 ii php-cas 1.3.3-4 ii php-gd 1:7.0+49 ii php-imap1:7.0+49 ii php-ldap1:7.0+49 ii php-mbstring1:7.0+49 ii php-mysql 1:7.0+49 ii php-pclzip 2.8.2-4 ii php-soap1:7.0+49 ii php-xml 1:7.0+49 ii php7.0 [php]7.0.33-0+deb9u1 ii php7.0-cli [php-cli]7.0.33-0+deb9u1 ii php7.0-gd [php-gd] 7.0.33-0+deb9u1 ii php7.0-imap [php-imap] 7.0.33-0+deb9u1 ii php7.0-ldap [php-ldap] 7.0.33-0+deb9u1 ii php7.0-mbstring [php-mbstring] 7.0.33-0+deb9u1 ii php7.0-soap [php-soap] 7.0.33-0+deb9u1 ii php7.0-xml [php-xml]7.0.33-0+deb9u1 ii phpqrcode 1.1.4-2 Versions of packages ocsinventory-reports recommends: ii apache2 [httpd] 2.4.25-3+deb9u6 pn libdbd-mysql-perl pn libdbi-perl ii libnet-ip-perl 1.26-1 ii libxml-simple-perl 2.22-1 pn nmap pn ocsinventory-server pn samba-common ocsinventory-reports suggests no packages. --- End Message --- --- Begin Message --- Source: ocsinventory-server Source-Version: 2.8+dfsg1-1 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of ocsinventory-server, 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 920...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated ocsinventory-server 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: Mon, 14 Sep 2020 12:58:39 +0200 Source: ocsinventory-server Architecture: source Version: 2.8+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: Xavier Guimard Closes: 920261 Changes: ocsinventory-server (2.8+dfsg1-1) unstable; urgency=medium . [ gregor herrmann ] * debian/copyright: replace tabs with spaces / remove
Bug#944018: marked as done (ocsinventory-reports: depends on no longer available libjs-select2.js)
Your message dated Mon, 14 Sep 2020 12:52:17 +0200 with message-id and subject line libjs-select2.js is now available has caused the Debian Bug report #944018, regarding ocsinventory-reports: depends on no longer available libjs-select2.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.) -- 944018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944018 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ocsinventory-reports Version: 2.6~RC+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in experimental: The following packages have unmet dependencies: ocsinventory-reports : Depends: libjs-select2.js but it is not installable Cheers, Andreas --- End Message --- --- Begin Message --- X-CrossAssassin-Score: 19560--- End Message ---
Bug#966850: iverilog: bison 3.7 fix available
I think the pull request below fixes the issue: https://github.com/steveicarus/iverilog/pull/349
Processed: retitle 970265 to python3.8: FTBFS on arch:all, causing python3.8-doc to be unavailable and python3-doc uninstallable
Processing commands for cont...@bugs.debian.org: > retitle 970265 python3.8: FTBFS on arch:all, causing python3.8-doc to be > unavailable and python3-doc uninstallable Bug #970265 [src:python3.8] python3.8-doc has been removed, causing python3-doc to be uninstallable Changed Bug title to 'python3.8: FTBFS on arch:all, causing python3.8-doc to be unavailable and python3-doc uninstallable' from 'python3.8-doc has been removed, causing python3-doc to be uninstallable'. > thanks Stopping processing here. Please contact me if you need assistance. -- 970265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970271: marked as done (blender: Change compile to -std=c++14)
Your message dated Mon, 14 Sep 2020 09:03:48 + with message-id and subject line Bug#970271: fixed in blender 2.83.5+dfsg-2 has caused the Debian Bug report #970271, regarding blender: Change compile to -std=c++14 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.) -- 970271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openvdb Version: 7.1.0-2 Upload of openvdb 7.1.0 breaks compilation of blender as seen on buildds amd64|i386: cd /<>/obj-x86_64-linux-gnu/source/blender/makesrna/intern && /usr/bin/cc -DGLEW_NO_GLU -DWITH_ASSERT_ABORT -DWITH_AUDASPACE -DWITH_BULLET -DWITH_CINEON -DWITH_COLLADA -DWITH_CYCLES -DWITH_DDS -DWITH_FFMPEG -DWITH_FFTW3 -DWITH_FLUID -DWITH_FREESTYLE -DWITH_GL_PROFILE_CORE -DWITH_HDR -DWITH_INPUT_NDOF -DWITH_INTERNATIONAL -DWITH_JACK -DWITH_OCEANSIM -DWITH_OPENAL -DWITH_OPENEXR -DWITH_OPENGL -DWITH_OPENIMAGEIO -DWITH_OPENJPEG -DWITH_OPENSUBDIV -DWITH_OPENVDB -DWITH_OPENVDB_BLOSC -DWITH_PYTHON -DWITH_SDL -DWITH_TIFF -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -D__LITTLE_ENDIAN__ -D__MMX__ -D__SSE2__ -D__SSE__ -I/<>/source/blender/makesrna/intern -I/<>/source/blender/makesrna -I/<>/source/blender/blenfont -I/<>/source/blender/blenkernel -I/<>/source/blender/blenlib -I/<>/source/blender/blentranslation -I/<>/source/blender/bmesh -I/<>/source/blender/depsgraph -I/<>/source/blender/draw -I/<>/source/blender/gpu -I/<>/source/blender/ikplugin -I/<>/source/blender/imbuf -I/<>/source/blender/makesdna -I/<>/source/blender/nodes -I/<>/source/blender/physics -I/<>/source/blender/windowmanager -I/<>/source/blender/editors/include -I/<>/source/blender/render/extern/include -I/<>/intern/cycles/blender -I/<>/intern/atomic -I/<>/intern/glew-mx -I/<>/intern/guardedalloc -I/<>/intern/memutil -I/<>/intern/mantaflow/extern -I/<>/intern/clog -I/<>/source/blender/blenloader -I/<>/obj-x86_64-linux-gnu/source/blender/makesdna/intern -I/<>/source/blender/python -I/<>/intern/ffmpeg -I/<>/intern/rigidbody -I/<>/source/blender/freestyle -I/<>/intern/opensubdiv -isystem /<>/extern/audaspace/bindings/C -isystem /<>/obj-x86_64-linux-gnu/extern/audaspace -Wall -Wcast-align -Werror=implicit-function-declaration -Werror=return-type -Werror=vla -Wstrict-prototypes -Wmissing-prototypes -Wno-char-subscripts -Wno-unknown-pragmas -Wpointer-arith -Wunused-parameter -Wwrite-strings -Wlogical-op -Wundef -Winit-self -Wmissing-include-dirs -Wno-div-by-zero -Wtype-limits -Wformat-signedness -Wrestrict -Wnonnull -Wabsolute-value -Wuninitialized -Wredundant-decls -Wshadow -Wno-error=unused-but-set-variable -Wimplicit-fallthrough=5 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -fuse-ld=gold -fopenmp -std=gnu11 -msse -pipe -fPIC -funsigned-char -fno-strict-aliasing -msse2 -Werror=implicit-function-declaration -Wno-missing-prototypes -o CMakeFiles/bf_rna.dir/rna_scene_gen.c.o -c /<>/obj-x86_64-linux-gnu/source/blender/makesrna/intern/rna_scene_gen.c In file included from /<>/source/blender/blenkernel/intern/volume.cc:68: /usr/include/openvdb/points/PointDataGrid.h: In member function ‘openvdb::v7_1::points::AttributeSet::UniquePtr openvdb::v7_1::points::PointDataLeafNode::stealAttributeSet()’: /usr/include/openvdb/points/PointDataGrid.h:751:40: error: ‘make_unique’ is not a member of ‘std’ 751 | AttributeSet::UniquePtr ptr = std::make_unique(); |^~~ /usr/include/openvdb/points/PointDataGrid.h:751:40: note: ‘std::make_unique’ is only available from C++14 onwards /usr/include/openvdb/points/PointDataGrid.h:751:64: error: expected primary-expression before ‘>’ token 751 | AttributeSet::UniquePtr ptr = std::make_unique(); |^ /usr/include/openvdb/points/PointDataGrid.h:751:66: error: expected primary-expression before ‘)’ token 751 | AttributeSet::UniquePtr ptr = std::make_unique(); | ref: * https://buildd.debian.org/status/fetch.php?pkg=blender=amd64=2.83.5%2Bdfsg-1%2Bb1=1599809838=0 --- End Message --- --- Begin Message --- Source: blender Source-Version: 2.83.5+dfsg-2 Done: Mathieu Malaterre We believe that the bug you reported is fixed in the latest version of blender, 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
Bug#967020: marked as done (dogecoin: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Mon, 14 Sep 2020 08:22:38 +
with message-id
and subject line Bug#967020: fixed in dogecoin 1.14.2-1
has caused the Debian Bug report #967020,
regarding dogecoin: FTBFS: dpkg-gensymbols: error: some symbols or patterns
disappeared in the symbols file: see diff output below
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.)
--
967020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967020
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dogecoin
Version: 1.14.0-1.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_install
> cp /<>/share/pixmaps/bitcoin128.png
> /<>/debian/dogecoin/usr/share/pixmaps/dogecoin128.png
> make[1]: Leaving directory '/<>'
>dh_installdocs
>dh_installchangelogs
>dh_installman
>dh_perl
>dh_link
>dh_strip_nondeterminism
>dh_compress
>dh_fixperms
>dh_missing
> dh_missing: warning: usr/lib/x86_64-linux-gnu/libdogecoinconsensus.a exists
> in debian/tmp but is not installed to anywhere
> The following debhelper tools have reported what they installed (with
> files per package)
>* dh_install: dogecoin (7), libdogecoinconsensus-dev (3),
> libdogecoinconsensus0 (2)
>* dh_installdocs: dogecoin (0), libdogecoinconsensus-dev (0),
> libdogecoinconsensus0 (0)
>* dh_installman: dogecoin (0), libdogecoinconsensus-dev (0),
> libdogecoinconsensus0 (0)
> If the missing files are installed by another tool, please file a bug
> against it.
> When filing the report, if the tool is not part of debhelper itself,
> please reference the
> "Logging helpers and dh_missing" section from the "PROGRAMMING" guide
> for debhelper (10.6.3+).
> (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
> Be sure to test with dpkg-buildpackage -A/-B as the results may vary
> when only a subset is built
> If the omission is intentional or no other helper can take care of this
> consider adding the
> paths to debian/not-installed.
>
> Remember to be careful with paths containing "x86_64-linux-gnu", where
> you might need to
> use a wildcard or (assuming compat 13+) e.g. ${DEB_HOST_MULTIARCH} in
> debian/not-installed
> to ensure it works on all architectures (see #961104).
>dh_strip
>dh_makeshlibs
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see
> diff output below
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols
> file: see diff output below
> dpkg-gensymbols: warning: debian/libdogecoinconsensus0/DEBIAN/symbols doesn't
> match completely debian/libdogecoinconsensus0.symbols.amd64
> --- debian/libdogecoinconsensus0.symbols.amd64
> (libdogecoinconsensus0_1.14.0-1.1_amd64)
> +++ dpkg-gensymbolsRZVh_N 2020-08-02 17:02:18.681900167 +
> @@ -33,8 +33,8 @@
> _Z14ArithToUint256RK13arith_uint256@Base 1.14.0
> _Z14GetBlockWeightRK6CBlock@Base 1.14.0
>
> _Z14SanitizeStringRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEi@Base
> 1.14.0
> - _Z14Serialize_implI11CHashWriterLj28EhEvRT_RK9prevectorIXT0_ET1_jiERKh@Base
> 1.14.0
> -
> _Z14Serialize_implI13CSizeComputerSt10shared_ptrIK12CTransactionESaIS4_ES4_EvRT_RKSt6vectorIT0_T1_ERKT2_@Base
> 1.14.0
> +#MISSING: 1.14.0-1.1#
> _Z14Serialize_implI11CHashWriterLj28EhEvRT_RK9prevectorIXT0_ET1_jiERKh@Base
> 1.14.0
> +#MISSING: 1.14.0-1.1#
> _Z14Serialize_implI13CSizeComputerSt10shared_ptrIK12CTransactionESaIS4_ES4_EvRT_RKSt6vectorIT0_T1_ERKT2_@Base
> 1.14.0
> _Z14SipHashUint256mmRK7uint256@Base 1.14.0
> _Z14UintToArith256RK7uint256@Base 1.14.0
> _Z15BlockMerkleRootRK6CBlockPb@Base 1.14.0
> @@ -55,16 +55,19 @@
> _Z30scrypt_1024_1_1_256_sp_genericPKcPcS1_@Base 1.14.0
> _Z4atoiRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.14.0
> _Z5IsHexRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.14.0
> +
> _Z6HexStrI7CScriptENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKT_b@Base
> 1.14.0-1.1
> _Z6atoi64PKc@Base 1.14.0
> _Z6atoi64RKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.14.0
> _Z6itostrB5cxx11i@Base 1.14.0
> - _Z7Hash160IPKhE7uint160T_S3_@Base 1.14.0
> +#MISSING: 1.14.0-1.1# _Z7Hash160IPKhE7uint160T_S3_@Base 1.14.0
> _Z8HexDigitc@Base 1.14.0
> _Z8ParseHexPKc@Base 1.14.0
>
Bug#967129: marked as done (dogecoin: Unversioned Python removal in sid/bullseye)
Your message dated Mon, 14 Sep 2020 08:22:38 + with message-id and subject line Bug#967129: fixed in dogecoin 1.14.2-1 has caused the Debian Bug report #967129, regarding dogecoin: Unversioned Python 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.) -- 967129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:dogecoin Version: 1.14.0-1.1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned 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 We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. 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: dogecoin Source-Version: 1.14.2-1 Done: Keng-Yu Lin We believe that the bug you reported is fixed in the latest version of dogecoin, 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 967...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Keng-Yu Lin (supplier of updated dogecoin 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, 13 Sep 2020 15:42:30 +0800 Source: dogecoin Architecture: source Version: 1.14.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Cryptocoin Team Changed-By: Keng-Yu Lin Closes: 967020 967129 Changes: dogecoin (1.14.2-1) unstable; urgency=medium . * New upstream release * Change Python to Python3 in Build-Depends (Closes: #967129) * Update debian/libdogecoinconsensus0.symbols.amd64 (Closes: #967020) * Update Standards-Version to 4.5.0.3 Checksums-Sha1: a31c1fd480f4fbfa71c7821bf5e64288d8d1177f 2280 dogecoin_1.14.2-1.dsc 336a06428c803b9c1099cbf21241a04e5bf9ae57 7207891 dogecoin_1.14.2.orig.tar.gz bb6e9981558dbba630478f0209c18574cf27fc5f 11592 dogecoin_1.14.2-1.debian.tar.xz 0e23d1c7e9fbe0d623e45f1722c41c5fde38d2f2 14170 dogecoin_1.14.2-1_source.buildinfo Checksums-Sha256: 4bf83d470ec4a4938d876fa2c7a259da84a6e8109ca3187aa0019df51f18fdc0 2280 dogecoin_1.14.2-1.dsc 416581d0af2df05ededb400b9434765eeaeb1396c9f3ef80a7b59a88c74a90cc 7207891 dogecoin_1.14.2.orig.tar.gz 779fac39d50474fbd27c1e0508135029c473df8da93dc8f040561cfe847b5665 11592 dogecoin_1.14.2-1.debian.tar.xz e242a58a09bf6899518a3c98a74159342ece62cb9d940440fd33b6823790862c 14170 dogecoin_1.14.2-1_source.buildinfo Files: eef606138f0504147a75c28667e71e30 2280 utils optional dogecoin_1.14.2-1.dsc 364742bab650110dd3f95ee1937bfdd6 7207891 utils optional dogecoin_1.14.2.orig.tar.gz 5c86db4cf343ed0d139875d50df09155 11592 utils optional dogecoin_1.14.2-1.debian.tar.xz e5325763e52520c7bb41d4a7e2001a4b 14170 utils optional dogecoin_1.14.2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEdwtc2/tLhothQ0hFxheGnxR4UE4FAl9eRYwSHGtlbmd5dUBk ZWJpYW4ub3JnAAoJEMYXhp8UeFBOlR0QAJ1be93oV6bIBTN3NMtMp4mCgfh4MWkR NR36re4+TXhG+76AY/c3/odWZSgpN4HqOljrUdQP7wpoa6jQ5k1oBd0pwngb743+ 1zpHlPCwox0qJ1OXlxbp3LTg1AQznpHlLWfyFfYuxuwwcyh83R2VLZXi+NPYCNk/ YfCOzHGTvkMK+SRIFV0nOt9qeD8pb2x7n6UDJdCpJHa4Ee2kl1E0z1SBVBWuJhu8 McLRnLwfFAD0m5WV9etvQg83kUpgdvNu22wp9/h2HfFb02TQNvjIFLDSNOnW+kmC OX2/YMkWVGnlp252CKfte4R7WzjkHMRr/nTVukQBv2HWJltbHck4jFwvOU2v7BrY Tp7D0EYIL8gkor8aTHmtYL9qogW/ct062oVLRoZPEE8Yej+xEJHTBrh7GdJPC8jg VFwe+8f9ewY6AyboeYhNW3rUqXAQ91lBvVGV8ojPmEDJlypCp1aKGZI0NqBfIP0q
Processed: Bug#970271 marked as pending in blender
Processing control commands: > tag -1 pending Bug #970271 [src:blender] blender: Change compile to -std=c++14 Ignoring request to alter tags of bug #970271 to the same tags previously set -- 970271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970271: marked as pending in blender
Control: tag -1 pending Hello, Bug #970271 in blender 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/blender/-/commit/47ac40bef35a5e1af7ce29a31ef133cd132649bf d/patches: Fix compilation with OpenVDB. Closes: #970271 (this message was generated automatically) -- Greetings https://bugs.debian.org/970271
Processed: Bug#955125 marked as pending in subliminal
Processing control commands: > tag -1 pending Bug #955125 [subliminal-nautilus] subliminal-nautilus is broken Added tag(s) pending. -- 955125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961338: marked as pending in subliminal
Control: tag -1 pending Hello, Bug #961338 in subliminal 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/subliminal/-/commit/36ce7176e412170da8d44c37679096861d18a20b New upstream version and rebase patches Closes: #961338 (this message was generated automatically) -- Greetings https://bugs.debian.org/961338
Processed: Bug#961338 marked as pending in subliminal
Processing control commands: > tag -1 pending Bug #961338 [subliminal] subliminal: update to 2.1 required to fix discarded provider problem Added tag(s) pending. -- 961338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955125: marked as pending in subliminal
Control: tag -1 pending Hello, Bug #955125 in subliminal 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/subliminal/-/commit/e1aa2b272e05d07eaffdf65074f47f66e06b0839 d/patches: Update 0001-Examples-directory.patch Closes: #955125 (this message was generated automatically) -- Greetings https://bugs.debian.org/955125
Bug#963341: cfengine3: New cfengine 3.15.2 package is broken and non-functional
On Fri, Sep 11, 2020 at 09:54:19AM +0200, Gian Piero Carrubba wrote: > Package: cfengine3 > Followup-For: Bug #963341 > > Hi, > > just a friendly ping that > https://salsa.debian.org/cfengine-team/cfengine3/-/merge_requests/2 > fixes this (admittely also includes not strictly needed changes, tho). > > Ciao, > Gian Piero. Thanks for the ping, these are merged now. I will prepare a release.
Processed: add tag
Processing commands for cont...@bugs.debian.org: > tags 961338 bullseye sid Bug #961338 [subliminal] subliminal: update to 2.1 required to fix discarded provider problem Added tag(s) sid and bullseye. > tags 964190 stretch Bug #964190 [subliminal] subliminal (stretch) is not working with current providers Added tag(s) stretch. > End of message, stopping processing here. Please contact me if you need assistance. -- 961338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961338 964190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964190 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re:
Processing commands for cont...@bugs.debian.org: > severity 970271 grave Bug #970271 [src:blender] blender: Change compile to -std=c++14 Severity set to 'grave' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 970271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
