Processed: xevil: diff for NMU version 2.02r2-10.1
Processing control commands: > tags 831104 + pending Bug #831104 [src:xevil] xevil: FTBFS with GCC 6: stl_algobase.h:243:56: error: macro "min" passed 3 arguments, but takes just 2 Added tag(s) pending. -- 831104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#831104: xevil: diff for NMU version 2.02r2-10.1
Control: tags 831104 + pending
Dear maintainer,
I've prepared an NMU for xevil (versioned as 2.02r2-10.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer or cancel the NMU.
Regards,
Eriberto
--- xevil-2.02r2/debian/changelog
+++ xevil-2.02r2/debian/changelog
@@ -1,3 +1,11 @@
+xevil (2.02r2-10.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fixed FTBFS with GCC 6 and higher. Thanks to Javier Serrano
+Polo . (Closes: #831104)
+
+ -- Joao Eriberto Mota Filho Sun, 07 Jun 2020 02:11:06
-0300
+
xevil (2.02r2-10) unstable; urgency=low
* Fixed bug that sometimes prevented X resources from being read properly.
diff -u xevil-2.02r2/cmn/utils.h xevil-2.02r2/cmn/utils.h
--- xevil-2.02r2/cmn/utils.h
+++ xevil-2.02r2/cmn/utils.h
@@ -98,11 +98,11 @@
#define MSEC_PER_CLOCK (1.0e3 / CLOCKS_PER_SEC)
#endif
-#ifndef max
-#define max(a,b) (ab ? b : a)
+#ifndef MIN
+#define MIN(a,b) (a>b ? b : a)
#endif
#if X11
diff -u xevil-2.02r2/cmn/game.cpp xevil-2.02r2/cmn/game.cpp
--- xevil-2.02r2/cmn/game.cpp
+++ xevil-2.02r2/cmn/game.cpp
@@ -577,7 +577,7 @@
assert(maximums[weapons[n]->classId] == 0);
// Don't allow objectWorldPercent values that are too small.
- float objWPercent = (float)max(weapons[n]->objectWorldPercent,
+ float objWPercent = (float)MAX(weapons[n]->objectWorldPercent,
OBJECT_WORLD_PERCENT_MIN);
maximums[weapons[n]->classId] = (int)ceil(areaFactor * objWPercent);
@@ -590,7 +590,7 @@
for (n = 0; n < oItemsNum; n++) {
// Check not already set.
assert(maximums[oItems[n]->classId] == 0);
- float objWPercent = (float)max(oItems[n]->objectWorldPercent,
+ float objWPercent = (float)MAX(oItems[n]->objectWorldPercent,
OBJECT_WORLD_PERCENT_MIN);
maximums[oItems[n]->classId] = (int)ceil(areaFactor * objWPercent);
diff -u xevil-2.02r2/debian/changelog xevil-2.02r2/debian/changelog
Bug#962368: frogatto-data: Source-only upload not automatically built for non-free packages
Hi Martin, Martin Quinson 于2020年6月6日周六 下午7:11写道： > > Hello, > > thanks for pointing me to this, I didn't know. And even now, I'm not sure of > whether frogatto-data is auto-buildable. The reason why it's non-free is > because the licence file states: "The Frogatto game and all content is > available for download free of charge from http://www.frogatto.com. The game > may be redistributed for non-commercial purposes so long as the entire > package is kept in-tact and unmodified. This license must also be included > and kept in-tact. It is forbidden to distribute the game, or any portion > thereof for any commercial or revenue-generating purpose." > > Under this light, should I mark the package as auto-buildable? I tend to > think so but would appreciate your guidance. I don't have a firm answer for this. Maybe you can write an email to the buildd team (non-f...@buildd.debian.org or other email address) for answer? > In the meanwhile, I'll do a source+binary upload of the package. This should fall back to the old behavior and not introduce new problems. I have no idea if britney would influence testing migration though (probably not since this is of non-free). -- Thanks, Boyuan Yang
Bug#962095: marked as done (qosmic ftbfs with ICU 67)
Your message dated Sun, 07 Jun 2020 00:03:41 + with message-id and subject line Bug#962095: fixed in flam3 3.1.1-2 has caused the Debian Bug report #962095, regarding qosmic ftbfs with ICU 67 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.) -- 962095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:qosmic Version: 1.6.0-2 Severity: serious Tags: sid bullseye qosmic ftbfs with ICU 67: [...] In file included from /usr/include/unicode/uenum.h:23, from /usr/include/unicode/ucnv.h:53, from /usr/include/libxml2/libxml/encoding.h:31, from /usr/include/libxml2/libxml/parser.h:810, from /usr/include/flam3.h:24, from src/flam3util.h:27, from src/genomevector.h:24, from src/xfedit.h:32, from src/xfedit.cpp:26: /usr/include/unicode/ucnv.h:585:1: error: conflicting declaration of C function ‘void icu_67::swap(icu_67::LocalUConverterPointer&, icu_67::LocalUConverterPointer&)’ 585 | U_DEFINE_LOCAL_OPEN_POINTER(LocalUConverterPointer, UConverter, ucnv_close); | ^~~ /usr/include/unicode/uenum.h:68:1: note: previous declaration ‘void icu_67::swap(icu_67::LocalUEnumerationPointer&, icu_67::LocalUEnumerationPointer&)’ 68 | U_DEFINE_LOCAL_OPEN_POINTER(LocalUEnumerationPointer, UEnumeration, uenum_close); | ^~~ make[1]: *** [Makefile:1764: .obj/triangle.o] Error 1 make[1]: *** [Makefile:1854: .obj/renderthread.o] Error 1 make[1]: *** [Makefile:1866: .obj/genomecolorselector.o] Error 1 make[1]: *** [Makefile:1731: .obj/xfedit.o] Error 1 make[1]: Leaving directory '/packages/tmp/qosmic-1.6.0' dh_auto_build: error: make -j8 returned exit code 2 --- End Message --- --- Begin Message --- Source: flam3 Source-Version: 3.1.1-2 Done: Peter Blackman We believe that the bug you reported is fixed in the latest version of flam3, 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. Peter Blackman (supplier of updated flam3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 06 jun 2020 16:00:00 + Source: flam3 Architecture: source Version: 3.1.1-2 Distribution: unstable Urgency: medium Maintainer: Peter Blackman Changed-By: Peter Blackman Closes: 711285 949143 962095 Changes: flam3 (3.1.1-2) unstable; urgency=medium . * Adopt package (Closes: #711285) * Fix FTBFS from xml2-config removal (Closes: #949143) * Remove broken 'compile' symlink * Remove unused entry ljpeg in .pc file * Fix buffer overflow in flam.c * Include test.flam3 & vidres.flam3 * Include rendering fixes from upstream issue tracker * Standards now 4.5.0 rules-require-root & compat * Fix broken links in the README * Fix qosmic FTBFS with ICU 67 (Closes: #962095) Checksums-Sha1: 3cb3218195d43c5614832c8a3d9ec19148b7e950 1864 flam3_3.1.1-2.dsc c8febffd621c7b804d1bb3332584dad6ed7e9321 6108 flam3_3.1.1-2.debian.tar.xz d801cdb458d45de84c98b36c4a034538bffc16b3 5433 flam3_3.1.1-2_source.buildinfo Checksums-Sha256: 0743c3564bf8ccb7f8012f3718a719bc98c4d860467f23039635d8be5a59398c 1864 flam3_3.1.1-2.dsc 75cd68d27e371cf3b8b7d099981e3eb06c535d3d5a6b9d87c72db8868b90a564 6108 flam3_3.1.1-2.debian.tar.xz a36da6c6c109085fd5ec1f932190d3d07acda9df2acf1b4270cacf018ebcb37f 5433 flam3_3.1.1-2_source.buildinfo Files: 040b27bf5c7c9fdee47a0dbfae94b6ad 1864 graphics optional flam3_3.1.1-2.dsc 7f98b7cf3d0ed3561b333bf815a9221d 6108 graphics optional flam3_3.1.1-2.debian.tar.xz bb70679521ae4da5f400ab3b56901ecf 5433 graphics optional flam3_3.1.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl7cLK0ACgkQweDZLphv fH6Xzw//df+osw3dj7HCDc5rMIQnU4KRH2wC3RMtyAcUWS2hl+CFS8edZD68wj0r BgBKkjJAaMvnhqRklanqOJwmsqn81MxpA2ZrwOc6A9QCDcWMenbQrUPfXtZnWjJS Q2gIxnI8V/CPoBHNi4DldQIE2x3dmdNdm+xsyzE9B3+j3t/5gtZpLX/AXfazGnax dDb1asjWMAzMoiKhKVyA3NE/uhiSZHsY+pZnlpJ
Bug#962001: marked as done (austin: autopkgtest regression: src/austin: No such file or directory)
Your message dated Sun, 07 Jun 2020 00:03:36 + with message-id and subject line Bug#962001: fixed in austin 1.0.1-2 has caused the Debian Bug report #962001, regarding austin: autopkgtest regression: src/austin: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 962001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962001 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: austin Version: 1.0.1-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 austin the autopkgtest of austin fails in testing when that autopkgtest is run with the binary packages of austin from unstable. It passes when run with only packages from testing. In tabular form: passfail austin from testing1.0.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 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=austin https://ci.debian.net/data/autopkgtest/testing/amd64/a/austin/5721929/log.gz # not ok 11 Test Austin with Python 3.8 # # (from function `invoke_austin' in file test/test_fork.bats, line 65, # # in test file test/test_fork.bats, line 119) # # `invoke_austin "3.8"' failed with status 127 # # Python 3.8.3 # # > Run 1 of 3 # # :: Standard profiling # #Exit code: 127 # # > Run 2 of 3 # # :: Standard profiling # #Exit code: 127 # # > Run 3 of 3 # # :: Standard profiling # #Exit code: 127 # # # # Collected Output # # # # # # /usr/libexec/bats-core/bats-exec-test: line 62: src/austin: No such file or directory # # not ok 2 Test Austin: fork multi-process signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: austin Source-Version: 1.0.1-2 Done: phoenix1...@gmail.com (Gabriele N. Tornetta) We believe that the bug you reported is fixed in the latest version of austin, 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. Gabriele N. Tornetta (supplier of updated austin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 05 Jun 2020 17:24:00 +0100 Source: austin Architecture: source Version: 1.0.1-2 Distribution: unstable Urgency: medium Maintainer: Gabriele N. Tornetta Changed-By: Gabriele N. Tornetta Closes: 962001 Changes: austin (1.0.1-2) unstable; urgency=medium . Enhanced test sources. Closes: #962001. Checksums-Sha1: aa69ee6fa5e63b978497644e6dd8c080171f44bf 1892 austin_1.0.1-2.dsc 648b083bc2d80e8fe52dad8a850cbf83504b4f3c 7548 austin_1.0.1-2.debian.tar.xz c4fdf95e5e3c04eb7c45893100d210e949bee40e 5611 austin_1.0.1-2_source.buildinfo Checksums-Sha256: 97bc86fa124312a531078150f9ad4fb3eb365320644de98ccb5ec421468da41b 1892 austin_1.0.1-2.dsc 2d6962cd174c6908c8c112b175911ca4a739fe61604f20b656b34f2ef5a94c8c 7548 austin_1.0.1-2.debian.tar.xz a0a3e24c0fd8e7b0540b4c14e903a1b54ebc1ca59c8e5778d82852987b31b2b2 5611 austin_1.0.1-2_source.buildinfo Files: 69d016d49fc909ca2ee13ce31f3f5957 1892 devel optional austin_1.0.1-2.dsc bafc9fb537ff17420f8d6dbabe495456 7548 devel optional austin_1.0.1-2.debian.tar.xz abf4732964aacad602d57ef38f9c6a17 5611 devel optional austin_1.0.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl7cK1sACgkQweDZLphv fH7zKg/7B6demcu8qBdsqJXjuNV2OnToJuD7Ws/gThGa/FnnOJz4dAQJMWX+7xlx J+yzWmAPWWID7UYKq3SJTPsb5/AGV/fq7Uo9zXgliRPd1u2NgCa/1kb9+ddwtqKx ByXzbVqOO3+KBAhZ9PzdBOxqxzGTRKHALsPHCIte6Ex9PG8PMRk1c/cuTGlvU3zU +Ui4UitehtI1ehuOM6yXA9C0IybH0t0bYCxano1SDrhTFPv4e49F8s7J7dVy8MPL l46ybEhV23DnVFhUtQ5snCdhoCV7r5sp9o2BmAw4heMmhI51WrOzxSrzVkornt9f NeGzYOmRPdkfinoRDHv7L2RErrY1r9Zy
Bug#961907: (no subject)
Hi David, David Rosenstrauch wrote: > Is this fix for the expired AddTrust cert likely to get backported to older > versions of Debian? (E.g., stretch, buster) Already happened for Buster and Stretch: The packages are already available in the "buster-proposed-updates" and "stretch-proposed-updates", see e.g. https://packages.qa.debian.org/c/ca-certificates.html They will latest be published in the normal repos with the next minor updates for the mentioned release (unless other severe bugs show up). There's though a simple workaround to fix the issues caused with this quickly: Run "dpkg-reconfigure ca-certificates" (as root) and then unselect "mozilla/AddTrust_External_Root.crt". (For all other potential questions just press Enter to keep the previous values.) Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#962368: frogatto-data: Source-only upload not automatically built for non-free packages
Hello, thanks for pointing me to this, I didn't know. And even now, I'm not sure of whether frogatto-data is auto-buildable. The reason why it's non-free is because the licence file states: "The Frogatto game and all content is available for download free of charge from http://www.frogatto.com. The game may be redistributed for non-commercial purposes so long as the entire package is kept in-tact and unmodified. This license must also be included and kept in-tact. It is forbidden to distribute the game, or any portion thereof for any commercial or revenue-generating purpose." Under this light, should I mark the package as auto-buildable? I tend to think so but would appreciate your guidance. In the meanwhile, I'll do a source+binary upload of the package. Thanks again, Mt. - Le 7 Juin 20, à 0:05, Boyuan Yang by...@debian.org a écrit : > Source: frogatto-data > Severity: serious > Version: 1.3.1+dfsg-2 > X-Debbugs-CC: mquin...@debian.org > > Dear Debian frogatto-data maintainers, > > Thanks for updating package frogatto-data in Debian. However, you just > made a source-only upload against a non-free package, which would cause > problems. > > By default, Debian's buildd will not build non-free packages due to > licensing concerns. If your package has no licensing concerns, please > follow instructions as written in the Developers Reference [1] to mark > the package as auto-buildable. If not, please make a binary-only upload > (or a source+binary upload) to actually make sure that the deb package > exists in the archive. > > -- > Regards, > Boyuan Yang > > [1] > https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#marking-non-free-packages-as-auto-buildable
Bug#937378: purity-ng: Python2 removal in sid/bullseye
On Fri, Aug 30, 2019 at 07:32:38AM +, Matthias Klose wrote: > Package: src:purity-ng > Version: 0.2.0-2.1 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the distribution, as discussed in > https://lists.debian.org/debian-python/2019/07/msg00080.html Hi Luke/Simon, the last commits for purity-ng are from 2011, are you still interested in this? Let's remove? Cheers, Moritz
Bug#961907: (no subject)
Is this fix for the expired AddTrust cert likely to get backported to older versions of Debian? (E.g., stretch, buster)
Bug#937749: python-fcgi: Python2 removal in sid/bullseye
On Fri, Apr 24, 2020 at 11:12:26PM +0200, Moritz Mühlenhoff wrote: > On Fri, Aug 30, 2019 at 07:39:14AM +, Matthias Klose wrote: > > Package: src:python-fcgi > > Version: 19980130-1 > > Severity: normal > > Tags: sid bullseye > > User: debian-pyt...@lists.debian.org > > Usertags: py2removal > > > > Python2 becomes end-of-live upstream, and Debian aims to remove > > Python2 from the distribution, as discussed in > > https://lists.debian.org/debian-python/2019/07/msg00080.html > > > > Your package either build-depends, depends on Python2, or uses Python2 > > in the autopkg tests. Please stop using Python2, and fix this issue > > by one of the following actions. > > python-fcgi seems dead upstream and there are no reverse deps. Are you > planning to port it to Python 3 or should it be removed? Filed a removal bug now. Cheers, Moritz
Processed: Re: manaplus-data: depends on dummy transitional package ttf-dejavu-core
Processing control commands: > severity -1 grave Bug #962207 [manaplus-data] manaplus-data: depends on dummy transitional package ttf-dejavu-core Severity set to 'grave' from 'normal' > tags -1 +patch Bug #962207 [manaplus-data] manaplus-data: depends on dummy transitional package ttf-dejavu-core Added tag(s) patch. -- 962207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962368: frogatto-data: Source-only upload not automatically built for non-free packages
Source: frogatto-data Severity: serious Version: 1.3.1+dfsg-2 X-Debbugs-CC: mquin...@debian.org Dear Debian frogatto-data maintainers, Thanks for updating package frogatto-data in Debian. However, you just made a source-only upload against a non-free package, which would cause problems. By default, Debian's buildd will not build non-free packages due to licensing concerns. If your package has no licensing concerns, please follow instructions as written in the Developers Reference [1] to mark the package as auto-buildable. If not, please make a binary-only upload (or a source+binary upload) to actually make sure that the deb package exists in the archive. -- Regards, Boyuan Yang [1] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#marking-non-free-packages-as-auto-buildable signature.asc Description: This is a digitally signed message part
Bug#938587: sugar-etoys-activity: Python2 removal in sid/bullseye
[ sent again, with 7bit headers to please Debian MTAs ] Quoting Moritz Mühlenhoff (2020-06-06 22:16:18) > On Sat, Jun 06, 2020 at 05:03:08PM +0200, Jonas Smedegaard wrote: > > Hi Moritz, > > > > Quoting Moritz Mühlenhoff (2020-06-06 16:34:38) > > > sugar-etoys-activity seems dead upstream the last commit is from 2012, > > > shall we remove it? > > > > What a coincidence that you should ask today - same exact day that a new > > release of Squeak Etoys was released after 10 years of development: > > http://www.squeakland.org/download/ > > Haha, I jinxed it :-) Sorry, no, I was totally fooled: That web page simply shows todays date, and the 5.0 release happened about 10 years ago. :-/ That said, The Squeak community is still active, just not issuing tarball images: Codebase in now at version 5.3. live-updatable from inside a 5.x image. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Processed: tagging 960416
Processing commands for cont...@bugs.debian.org: > tags 960416 + confirmed pending Bug #960416 [src:leatherman] leatherman: FTBFS with boost 1.71 Added tag(s) confirmed and pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 960416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938587: sugar-etoys-activity: Python2 removal in sid/bullseye
On Sat, Jun 06, 2020 at 05:03:08PM +0200, Jonas Smedegaard wrote: > Hi Moritz, > > Quoting Moritz Mühlenhoff (2020-06-06 16:34:38) > > sugar-etoys-activity seems dead upstream the last commit is from 2012, > > shall we remove it? > > What a coincidence that you should ask today - same exact day that a new > release of Squeak Etoys was released after 10 years of development: > http://www.squeakland.org/download/ Haha, I jinxed it :-) Cheers, Moritz
Processed: Fixed upstream
Processing commands for cont...@bugs.debian.org: > forwarded 960416 https://github.com/puppetlabs/leatherman/pull/306 Bug #960416 [src:leatherman] leatherman: FTBFS with boost 1.71 Set Bug forwarded-to-address to 'https://github.com/puppetlabs/leatherman/pull/306'. > tags 960416 fixed-upstream patch Bug #960416 [src:leatherman] leatherman: FTBFS with boost 1.71 Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 960416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#906495: marked as done (nfqueue-bindings: FTBFS in buster/sid (add_custom_target cannot create target "nfqueue_swig_compilation"))
Your message dated Sat, 06 Jun 2020 18:31:40 + with message-id and subject line Bug#962351: Removed package(s) from unstable has caused the Debian Bug report #906495, regarding nfqueue-bindings: FTBFS in buster/sid (add_custom_target cannot create target "nfqueue_swig_compilation") 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.) -- 906495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:nfqueue-bindings Version: 0.6-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch dh build-arch --with=python2 dh_update_autotools_config -a dh_auto_configure -a debian/rules override_dh_auto_build make[1]: Entering directory '/<>' make BUILD_DIR="build2.7" PREFIX=/usr CMAKE_EXTRA_OPTIONS="-DPython_ADDITIONAL_VERSIONS=2.7 -DPythonInterp_FIND_VERSION=2.7" make[2]: Entering directory '/<>' [ -d build2.7 ] || mkdir build2.7; \ cd build2.7 && cmake -DDEBUG=1 -DCMAKE_VERBOSE_MAKEFILE=0 -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=/usr -DPython_ADDITIONAL_VERSIONS=2.7 -DPythonInterp_FIND_VERSION=2.7 .. && make -- The C compiler identification is GNU 8.2.0 -- The CXX compiler identification is GNU 8.2.0 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- Found SWIG: /usr/bin/swig3.0 (found version "3.0.12") -- Found PkgConfig: /usr/bin/pkg-config (found version "0.29") -- Checking for one of the modules 'libnetfilter_queue' -- Looking for nfq_set_verdict2 -- Looking for nfq_set_verdict2 - found -- Found PythonInterp: /usr/bin/python (found suitable version "2.7.15", minimum required is "2.7") -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found version "2.7.15") CMake Deprecation Warning at /usr/share/cmake-3.12/Modules/UseSWIG.cmake:492 (message): SWIG_ADD_MODULE is deprecated. Use SWIG_ADD_LIBRARY instead. Call Stack (most recent call first): python/CMakeLists.txt:19 (SWIG_ADD_MODULE) -- Found Perl: /usr/bin/perl (found version "5.26.2") -- Found PerlLibs: /usr/lib/x86_64-linux-gnu/libperl.so.5.26 (found version "5.26.2") CMake Deprecation Warning at /usr/share/cmake-3.12/Modules/UseSWIG.cmake:492 (message): SWIG_ADD_MODULE is deprecated. Use SWIG_ADD_LIBRARY instead. Call Stack (most recent call first): perl/CMakeLists.txt:20 (SWIG_ADD_MODULE) CMake Error at /usr/share/cmake-3.12/Modules/UseSWIG.cmake:627 (add_custom_target): add_custom_target cannot create target "nfqueue_swig_compilation" because another target with the same name already exists. The existing target is a custom target created in source directory "/<>/python". See documentation for policy CMP0002 for more details. Call Stack (most recent call first): /usr/share/cmake-3.12/Modules/UseSWIG.cmake:493 (swig_add_library) perl/CMakeLists.txt:20 (SWIG_ADD_MODULE) -- Configuring incomplete, errors occurred! See also "/<>/build2.7/CMakeFiles/CMakeOutput.log". make[2]: *** [Makefile:7: all] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:21: build-python2.7] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:16: build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 The build was made with "dpkg-buildpackage -B" in my autobuilder. Most probably, it also fails here in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/nfqueue-bindings.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Version: 0.6-1+rm Dear submitter, as the package nfqueue-bindings has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with
Bug#942980: marked as done (cvs2svn: Python2 removal in sid/bullseye)
Your message dated Sat, 06 Jun 2020 18:32:11 + with message-id and subject line Bug#962355: Removed package(s) from unstable has caused the Debian Bug report #942980, regarding cvs2svn: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 942980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942980 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cvs2svn Version: 2.5.0-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 2.5.0-1+rm Dear submitter, as the package cvs2svn has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/962355 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#937224: marked as done (ovirt-guest-agent: Python2 removal in sid/bullseye)
Your message dated Sat, 06 Jun 2020 18:32:36 + with message-id and subject line Bug#962356: Removed package(s) from unstable has caused the Debian Bug report #937224, regarding ovirt-guest-agent: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 937224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ovirt-guest-agent Version: 1.0.15.dfsg-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:ovirt-guest-agent If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.0.15.dfsg-1+rm Dear submitter, as the package ovirt-guest-agent has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/962356 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#950078: marked as done (ovirt-guest-agent: fails to install: useradd: invalid shell '/sbin/nologin')
Your message dated Sat, 06 Jun 2020 18:32:36 + with message-id and subject line Bug#962356: Removed package(s) from unstable has caused the Debian Bug report #950078, regarding ovirt-guest-agent: fails to install: useradd: invalid shell '/sbin/nologin' 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.) -- 950078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950078 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ovirt-guest-agent Version: 1.0.15.dfsg-1 Severity: serious Tags: sid bullseye User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Selecting previously unselected package ovirt-guest-agent. Preparing to unpack .../97-ovirt-guest-agent_1.0.15.dfsg-1_all.deb ... useradd: invalid shell '/sbin/nologin' dpkg: error processing archive /tmp/apt-dpkg-install-pGnFan/97-ovirt-guest-agent_1.0.15.dfsg-1_all.deb (--unpack): new ovirt-guest-agent package pre-installation script subprocess returned error exit status 3 Errors were encountered while processing: /tmp/apt-dpkg-install-pGnFan/97-ovirt-guest-agent_1.0.15.dfsg-1_all.deb cheers, Andreas ovirt-guest-agent_1.0.15.dfsg-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Version: 1.0.15.dfsg-1+rm Dear submitter, as the package ovirt-guest-agent has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/962356 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#949982: marked as done (ovirt-guest-agent: Build-Depends on pep8 which has been removed)
Your message dated Sat, 06 Jun 2020 18:32:36 + with message-id and subject line Bug#962356: Removed package(s) from unstable has caused the Debian Bug report #949982, regarding ovirt-guest-agent: Build-Depends on pep8 which has been removed 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.) -- 949982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949982 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ovirt-guest-agent Version: 1.0.15.dfsg-1 Severity: serious Tags: ftbfs sid bullseye ovirt-guest-agent Build-Depends on the pep8 transitional package, which has already been removed (see #940736). This makes ovirt-guest-agent unbuildable in unstable. Please build-depend on pycodestyle instead, and if necessary update any build scripts that run the 'pep8' executable so they run 'pycodestyle' instead. smcv --- End Message --- --- Begin Message --- Version: 1.0.15.dfsg-1+rm Dear submitter, as the package ovirt-guest-agent has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/962356 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#937136: marked as done (nfqueue-bindings: Python2 removal in sid/bullseye)
Your message dated Sat, 06 Jun 2020 18:31:40 + with message-id and subject line Bug#962351: Removed package(s) from unstable has caused the Debian Bug report #937136, regarding nfqueue-bindings: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 937136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:nfqueue-bindings Version: 0.6-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:nfqueue-bindings If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.6-1+rm Dear submitter, as the package nfqueue-bindings has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/962351 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#962348: kig: boost1.67 is being removed from testing
severity 962348 important thanks In data sabato 6 giugno 2020 16:26:34 CEST, Dimitri John Ledkov ha scritto: > Package: kig > Version: 4:20.04.1-1 > Severity: serious > > Hi, > > boost1.67 is being removed from testing and is transitioning to boost1.71. Yes, I know about the boost transition to 1.71.0, that the new boost does not provide Python 2 support, and that it is expected to not ship boost 1.67.0 in bullseye. > kig has just now switched from boost1.71 to boost1.67. Quoting what I wrote in the changelog entry of 4:20.04.1-1: * Temporarily switch from libboost-python-dev to libboost-python1.67-dev, as boost 1.67 is the latest version of boost in Debian that supports Python 2: kig < 20.08 is not ready for Python 3, so stil with Python 2 for now. As the version number hints, the new stable version will be released in (late) August; the development version already switched to Python 3 only, and it contains few Python 3 fixes. The current version does *not* work properly with Python 3, that is why I had to rollback to boost 1.67.0 (since boost 1.71.0 has no Python 2 bindings, sigh). > Thus I am opening this bug report to prevent kig from migrating. First of all, please do not abuse severities for things that are not critical yet. There is a catch here: the version in testing is the binNMU for the boost 1.71.0 rebuild, and apparently (to my surprise) it was detected and switched to Python 3. This is buggy though, so not letting this version migrate means having a buggy version in testing. > boost1.71 does not offer python2 bindings, as python2 is being removed to. Sure, I know this too. > I understand that kig is using boost-python2. Either please disable > python bindings usage at build time, or try to port to boost-python3? As I said, in ~3 months there will be a new upstream release fully supporting Python 3, and I will switch it when it is released. In the meanwhile, please: a) open a RM bug for boost 1.67.0, so it is clear that it will be removed b) make this bug block the RM bug I'm pretty sure boost 1.67.0 can stay 3 months more around, especially since I see it is still not the only package using the old boost. -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#962348: kig: boost1.67 is being removed from testing
Processing commands for cont...@bugs.debian.org: > severity 962348 important Bug #962348 [kig] kig: boost1.67 is being removed from testing Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 962348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960768: marked as done (prads: missing build dependency on python3-docutils)
Your message dated Sat, 06 Jun 2020 17:51:07 + with message-id and subject line Bug#960768: fixed in prads 0.3.3-1.2 has caused the Debian Bug report #960768, regarding prads: missing build dependency on python3-docutils 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.) -- 960768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: prads Version: 0.3.3-1.1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=prads&suite=sid ... debian/rules override_dh_auto_install make[1]: Entering directory '/<>' /usr/bin/make PREFIX=/usr CONFDIR=/etc/prads DESTDIR=/<>/debian/prads install make[2]: Entering directory '/<>' rst2man doc/prads.man >doc/prads.1 /bin/sh: 1: rst2man: not found make[2]: *** [Makefile:31: doc/prads.1] Error 127 --- End Message --- --- Begin Message --- Source: prads Source-Version: 0.3.3-1.2 Done: Moritz Muehlenhoff We believe that the bug you reported is fixed in the latest version of prads, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Moritz Muehlenhoff (supplier of updated prads package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 06 Jun 2020 19:18:00 +0200 Source: prads Architecture: source Version: 0.3.3-1.2 Distribution: unstable Urgency: medium Maintainer: Prads package developers Changed-By: Moritz Muehlenhoff Closes: 960768 Changes: prads (0.3.3-1.2) unstable; urgency=medium . * Add build dep on python3-docutils (Closes: #960768) Checksums-Sha1: 7e6debfbedcdaf6a53d8685adbd329967f59532b 1959 prads_0.3.3-1.2.dsc d62f5b2ec13dbf31dc059babbe2fe8eef4254484 4848 prads_0.3.3-1.2.debian.tar.xz 86f72705d0a8c0c6874c21e4dcf6a03e9237f4f1 6412 prads_0.3.3-1.2_amd64.buildinfo Checksums-Sha256: bb857f7dda5322b2ff8a712c4a748d9af00a9e62f882c3bb7941a1ba64da930b 1959 prads_0.3.3-1.2.dsc b1576ea5a10565d0ad48950299fdd9ec3db4ceda561a29595328036dafd5411b 4848 prads_0.3.3-1.2.debian.tar.xz 212334586b19ccadbac6372697feec427d171dd721fdd0a044f7a654c1c9c2da 6412 prads_0.3.3-1.2_amd64.buildinfo Files: 75eed5af5192bf934bf1ffbbfd55ba11 1959 utils extra prads_0.3.3-1.2.dsc 4a4b77e537a6b2858968d85acfa3d090 4848 utils extra prads_0.3.3-1.2.debian.tar.xz dfd66fb7bbb5bed022cf8c235a07c6dc 6412 utils extra prads_0.3.3-1.2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEtuYvPRKsOElcDakFEMKTtsN8TjYFAl7b0HEACgkQEMKTtsN8 TjbVcBAAuKm1zFxGVkajgBD/OJRC8zwFqGmbjjhnia4rHpWoTl1HGoEtWTYW29ZS VQ9FHjAS0j8xmAPQTjYefYhCVnRP2mJsOn/5apjPXMlbekRBoP/sjD6FwwfCaqhp vgZ+czaL5FsRRmikswHz8MXy/1ujJdKKKgBGsacdQqyzXkzJsjedbeCtO6X6Fd3M l0DzWwDMSIUlwDrQLADsP/Np5S2z38J8xYDvycXafsNhifk0+EyxGE2p9ZC7UYDO +JuRV2qUFwsajrrDhEZJa/WfO1h5bojyS0BamSC4noivabv9QcrTAWsEA72A+cbf pjZn9gHfWeubBvxIRpa6uAyqJoyGyELrxg/kD213VFgFryuh0L6kfe6Hp4/jItak Dh3b2N0weuHDCKVxNR2X10R3EvJmDjMWCkmuYGRD0sgGYPaJmiG2fdzAdn7yFAvx 6n0dpF2rMZWVcUGrFO4H85mFfa/0A77sbLweznnXcIbDG1nbtakgq1HjotoLLWJe RKvi1ds6tOHW90ysPHU0WtpqFqDgJ5waOLQNtQxrvWvjXop9uY1VAcDx1R7sjzoV bvZLM6hwnJ7/Co1PE/d93p+3jIWE11zi/U1AHtB5fu9tc/NydnECyh+D3ON9jBMK hV2xUbm7gjoECoU6IdZSLSa+5xMtlJmD0LeaEbzgegXuvIZ1F38= =B6dK -END PGP SIGNATURE End Message ---
Processed: found 958450 in 57.0.2987.98
Processing commands for cont...@bugs.debian.org: > found 958450 57.0.2987.98 Bug #958450 [chromium] chromium: Please update chromium to 81.0.4044.113 for security reasons There is no source info for the package 'chromium' at version '57.0.2987.98' with architecture '' Unable to make a source version for version '57.0.2987.98' Marked as found in versions 57.0.2987.98. > thanks Stopping processing here. Please contact me if you need assistance. -- 958450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958450 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 962095 by 962358
Processing commands for cont...@bugs.debian.org: > block 962095 by 962358 Bug #962095 [flam3] qosmic ftbfs with ICU 67 962095 was not blocked by any bugs. 962095 was blocking: 960193 Added blocking bug(s) of 962095: 962358 > End of message, stopping processing here. Please contact me if you need assistance. -- 962095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938587: marked as done (sugar-etoys-activity: Python2 removal in sid/bullseye)
Your message dated Sat, 06 Jun 2020 17:05:52 + with message-id and subject line Bug#938587: fixed in sugar-etoys-activity 116-8 has caused the Debian Bug report #938587, regarding sugar-etoys-activity: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 938587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938587 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sugar-etoys-activity Version: 116-7 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:sugar-etoys-activity If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: sugar-etoys-activity Source-Version: 116-8 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of sugar-etoys-activity, 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 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated sugar-etoys-activity package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 06 Jun 2020 18:33:45 +0200 Source: sugar-etoys-activity Architecture: source Version: 116-8 Distribution: unstable Urgency: medium Maintainer: Debian Sugar Team Changed-By: Jonas Smedegaard Closes: 938587 Changes: sugar-etoys-activity (116-8) unstable; urgency=medium . * simplify rules; do copyright-check in maintainer script (not during build) stop build-depend on licensecheck dh-buildinfo; relax to build-depend unversioned on cdbs * use debhelper compatibility level 10 (not 9) * remove Luke Faraone as uploader, thanks for your past contributions * declare compliance with Debian Policy 4.5.0 * (build-)depend on python3 modules (not python); build-depend on dh-python; closes: bug#938587, thanks to Matthias Klose and Moritz Mühlenhoff * watch: + use file format 4 + use https URL + use pattern st
Bug#938587: sugar-etoys-activity: Python2 removal in sid/bullseye
[ sent again, also to bugreport ] Quoting Jonas Smedegaard (2020-06-06 17:03:08) > Hi Moritz, > > Quoting Moritz Mühlenhoff (2020-06-06 16:34:38) > > sugar-etoys-activity seems dead upstream the last commit is from 2012, > > shall we remove it? > > What a coincidence that you should ask today - same exact day that a new > release of Squeak Etoys was released after 10 years of development: > http://www.squeakland.org/download/ > > So no, I think the package should not be removed but upgraded :-) > > Thanks for asking, though - it is tricky to keep track of the Etoys and > Squeak and Sugarlabs and OLPC resources, it is as if each fraction > considers itself the center piece and does not reference activities > happening at the other parts. I could easily have missed this > announcement if you hadn't asked about it. ...also, I see now that sugar-etoys-activity specifically (i.e. a thin wrapper to load Squeak Etoys itself) is just 2 lines of python. I think even I can manage to migrate that to Python3 ;-) - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#938587: sugar-etoys-activity: Python2 removal in sid/bullseye
[ sent again, with 7bit headers to please Debian MTAs ] Hi Moritz, Quoting Moritz Mühlenhoff (2020-06-06 16:34:38) > sugar-etoys-activity seems dead upstream the last commit is from 2012, > shall we remove it? What a coincidence that you should ask today - same exact day that a new release of Squeak Etoys was released after 10 years of development: http://www.squeakland.org/download/ So no, I think the package should not be removed but upgraded :-) Thanks for asking, though - it is tricky to keep track of the Etoys and Squeak and Sugarlabs and OLPC resources, it is as if each fraction considers itself the center piece and does not reference activities happening at the other parts. I could easily have missed this announcement if you hadn't asked about it. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#942980: cvs2svn: Python2 removal in sid/bullseye
Hi Moritz, On Sat, Jun 6, 2020 at 4:33 PM Moritz Mühlenhoff wrote: > On Wed, Oct 23, 2019 at 02:33:21AM +, mo...@debian.org wrote: > > Source: cvs2svn > > Usertags: py2removal [...] > http://cvs2svn.tigris.org/ vanished off the net and > https://pypi.org/project/cvs2svn > shows the last release from 2009. Indeed, the official page is taken down. > Let's remove? If there's really anyone who wants to migrate an old CVS repo > to SVN, > they can still do it in a VM using an older release. I got a promise from one of its developers that development will continue and it will be Python 3-ified. Its source was moved (mirrored) to GitHub [1] and it might have unreleased changes already. Still, I don't see any attempt to make it work with Python 3 so you are probably correct. If anyone wanted to migrate their CVS tree to Subversion or Git already had years for that. Going to ask for its removal. Regards, Laszlo/GCS [1] https://github.com/mhagger/cvs2svn
Bug#906765: libxsmm: baseline violation on amd64 and FTBFS everywhere else
On Mon, Aug 20, 2018 at 10:26:03PM +0300, Adrian Bunk wrote: > Source: libxsmm > Version: 1.9-1 > Severity: serious > Tags: ftbfs patch > > libxsmm builds with -msse4.2 on amd64 and FTBFS everywhere else: > https://buildd.debian.org/status/package.php?p=libxsmm&suite=sid > > Fix for the baseline violation: > > --- debian/rules.old 2018-08-19 15:06:38.277886761 + > +++ debian/rules 2018-08-19 15:08:40.141885599 + > @@ -3,6 +3,8 @@ > > export PREFIX=/usr > > +export TARGET=-"" > + > %: > dh $@ > > > > The FTBFS problems on !amd64 don't seem easily fixable, > and it is unclear whether this would be worth the effort. > If fixing is not easily possible, an option would be > Architecture: any-amd64 There was no followup to this since almost two years or any of the other bugs, should libxsmm be removed? Cheers, Moritz
Processed: Reassign 962095 to flam3 (flam3.h)
Processing commands for cont...@bugs.debian.org: > reassign 962095 flam3 Bug #962095 [src:qosmic] qosmic ftbfs with ICU 67 Bug reassigned from package 'src:qosmic' to 'flam3'. No longer marked as found in versions qosmic/1.6.0-2. Ignoring request to alter fixed versions of bug #962095 to the same values previously set > End of message, stopping processing here. Please contact me if you need assistance. -- 962095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#936503: Anybody volunteering to try to save falcon in Debian (Was: Bug#936503: falcon: Python2 removal in sid/bullseye)
Hi, On Sat, Jun 06, 2020 at 04:31:38PM +0200, Moritz Mühlenhoff wrote: > > Your package either build-depends, depends on Python2, or uses Python2 > > in the autopkg tests. Please stop using Python2, and fix this issue > > by one of the following actions. > > It appears this was turned non-free, they only distribute binaries and even > those are still dependant > on Python 2: https://github.com/PacificBiosciences/FALCON_unzip/wiki/Binaries Argh. > | Which binary do I need? > | > | That depends on your python2.7 Unicode size. Almost certainly, you want > "ucs4", but you can check this way: > | > | python2.7 -c 'import sysconfig,pprint; > pprint.pprint(sysconfig.get_config_vars()["Py_UNICODE_SIZE"])' > | > | (We do not support python3.) > > So let's remove it from the archive? Any reader of the Debian Med list who wants to spent time to discuss this with upstream to save falcon in Debian? Kind regards Andreas. -- http://fam-tille.de
Bug#962251: marked as done (hugin: libboost-signals-dev no longer exists with boost1.71)
Your message dated Sat, 06 Jun 2020 14:48:43 + with message-id and subject line Bug#962251: fixed in hugin 2019.2.0+dfsg-2 has caused the Debian Bug report #962251, regarding hugin: libboost-signals-dev no longer exists with boost1.71 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.) -- 962251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hugin Version: 2019.2.0+dfsg-1 Severity: serious Tags: ftbfs Control: block 961995 by -1 https://buildd.debian.org/status/package.php?p=hugin libboost-signals-dev no longer exists with boost1.71. --- End Message --- --- Begin Message --- Source: hugin Source-Version: 2019.2.0+dfsg-2 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of hugin, 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. Andreas Metzler (supplier of updated hugin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 06 Jun 2020 16:21:41 +0200 Source: hugin Architecture: source Version: 2019.2.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian PhotoTools Maintainers Changed-By: Andreas Metzler Closes: 962251 Changes: hugin (2019.2.0+dfsg-2) unstable; urgency=medium . * Clean up boost b-ds. Closes: #962251 Checksums-Sha1: 336b8382bfca9385c6b79be12fba0cf670d017f0 2571 hugin_2019.2.0+dfsg-2.dsc 7a43c2b6cb5ede622c0f3efb916d7e9f5f40e015 185456 hugin_2019.2.0+dfsg-2.debian.tar.xz Checksums-Sha256: 0012b5ecceea74e9baee16f5bf1c9282fd4cc411b21c5eb3b42fc370fffb4645 2571 hugin_2019.2.0+dfsg-2.dsc 362519fbcf1d44ec487092afd1c4cdb213de7be464d23565ab161d0fdd846ee7 185456 hugin_2019.2.0+dfsg-2.debian.tar.xz Files: 115030f8bb9d2a3daee087c31917bad2 2571 graphics optional hugin_2019.2.0+dfsg-2.dsc ddefdd122dbe9f140f991e0498bc 185456 graphics optional hugin_2019.2.0+dfsg-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAl7bp0QACgkQpU8BhUOC FIRiSQ//UhQDZ0gohjnTtpCtGJ/JigLL9vqOuaRFIre0gUsll/iEjFuIraaLbVxU 3owdEPoaTi8UvQf3tCpZ49e4ETiPxPWjxXXaHi+K0LtBlyY/sATui2jaZq9mNi3+ 7K75Iq5+QMnjW6vuGEq/7HrFt6ImWa7GxhIy1tz62k7LN6XzC+aKMZb8M4rF/+w1 6N/sUxX0WKq3trhlqF9wRT/H/oAjdQsqkyiYNy70EiIJ21yTHoSfpjo4xW6PatIM cVKxoFBhIdOHLRVNUfiE2NZ9KBbfc1aGR8l50cTMMcy3QSDd3wRgGbYN6XvaHcQR AWNpB+7Sx5ODgyTXgKq5yws/xTC6yqU9KBPJMP8CWoCGMnRo6XMca8NGWpMfJzT5 fKzF9lt608G1kcRCyomL1JNcrtsh+2bOJdcRJwQJLXXwScEyG6R/FOTIw+RpmrH2 DCBuRffI0skRTff9HGQPfEHODQWVRQm4Wf4P6Klx+3vHnbPtXNQXWpw9HB77nPrU S9+I1+O4195HcZGbZnI8VgAe3xYpB7gRcN7ikF1n6y+f0593dMpmRTcO67XaEPBl HjYfd5tjRa4exTsyXEXUf6xVENIUzegohawidOF1J1Ij1L/RTL4cWaLMev0wNqAD 2402BUIC4wYgZt6T8HWVSH/TJysnMdfThvLPb5tLSCeqn5ki3xg= =f1Xl -END PGP SIGNATURE End Message ---
Bug#962353: Build-depends on phantom, which is being removed
Source: django-js-reverse Severity: serious phantomjs is being removed (962061), but django-js-reverse currently build-depends on it. It doesn't actually appear to be used anyway: | override_dh_auto_test: |echo "tests require phantomjs harness which setup.py does not start" Cheers, Moritz
Bug#938587: sugar-etoys-activity: Python2 removal in sid/bullseye
On Fri, Aug 30, 2019 at 07:54:24AM +, Matthias Klose wrote: > Package: src:sugar-etoys-activity > Version: 116-7 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the distribution, as discussed in > https://lists.debian.org/debian-python/2019/07/msg00080.html Hi, sugar-etoys-activity seems dead upstream the last commit is from 2012, shall we remove it? Cheers, Moritz
Bug#942980: cvs2svn: Python2 removal in sid/bullseye
On Wed, Oct 23, 2019 at 02:33:21AM +, mo...@debian.org wrote: > Source: cvs2svn > Version: 2.5.0-1 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the distribution, as discussed in > https://lists.debian.org/debian-python/2019/07/msg00080.html Hi, http://cvs2svn.tigris.org/ vanished off the net and https://pypi.org/project/cvs2svn shows the last release from 2009. Let's remove? If there's really anyone who wants to migrate an old CVS repo to SVN, they can still do it in a VM using an older release. Cheers, Moritz
Bug#936503: falcon: Python2 removal in sid/bullseye
On Fri, Aug 30, 2019 at 07:16:54AM +, Matthias Klose wrote: > Package: src:falcon > Version: 1.8.8-1 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the distribution, as discussed in > https://lists.debian.org/debian-python/2019/07/msg00080.html > > Your package either build-depends, depends on Python2, or uses Python2 > in the autopkg tests. Please stop using Python2, and fix this issue > by one of the following actions. It appears this was turned non-free, they only distribute binaries and even those are still dependant on Python 2: https://github.com/PacificBiosciences/FALCON_unzip/wiki/Binaries | Which binary do I need? | | That depends on your python2.7 Unicode size. Almost certainly, you want "ucs4", but you can check this way: | | python2.7 -c 'import sysconfig,pprint; pprint.pprint(sysconfig.get_config_vars()["Py_UNICODE_SIZE"])' | | (We do not support python3.) So let's remove it from the archive? Cheers, Moritz
Bug#962348: kig: boost1.67 is being removed from testing
Package: kig Version: 4:20.04.1-1 Severity: serious Hi, boost1.67 is being removed from testing and is transitioning to boost1.71. kig has just now switched from boost1.71 to boost1.67. boost1.67 must not be shipped in testing. Thus I am opening this bug report to prevent kig from migrating. boost1.71 does not offer python2 bindings, as python2 is being removed to. I understand that kig is using boost-python2. Either please disable python bindings usage at build time, or try to port to boost-python3? Either way, introducing python2 & boost1.67 usage in testing is working against release goals of not shipping python2 or boost1.67. Also in Ubuntu, kig is the only package using boost1.67 -- System Information: Debian Release: bullseye/sid APT prefers groovy APT policy: (500, 'groovy'), (500, 'focal-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-33-generic (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kig depends on: ii libboost-python1.67.0 [libboost-python1.67.0-py27] 1.67.0-17ubuntu8 ii libc6 2.31-0ubuntu9 ii libgcc-s1 10.1.0-3ubuntu1 ii libkf5archive5 5.70.0-0ubuntu1 pn libkf5completion5 ii libkf5configcore5 5.70.0-0ubuntu1 ii libkf5configwidgets55.70.0-0ubuntu1 ii libkf5coreaddons5 5.70.0-0ubuntu1 ii libkf5crash55.70.0-0ubuntu1 ii libkf5i18n5 5.70.0-0ubuntu1 ii libkf5iconthemes5 5.70.0-0ubuntu1 pn libkf5parts5 pn libkf5service-bin pn libkf5service5 pn libkf5texteditor5 ii libkf5widgetsaddons55.70.0-0ubuntu1 pn libkf5xmlgui-bin pn libkf5xmlgui5 ii libpython2.72.7.18-1 ii libqt5core5a5.14.2+dfsg-2ubuntu1 ii libqt5gui5 5.14.2+dfsg-2ubuntu1 ii libqt5printsupport5 5.14.2+dfsg-2ubuntu1 ii libqt5svg5 5.14.2-1 ii libqt5widgets5 5.14.2+dfsg-2ubuntu1 ii libqt5xml5 5.14.2+dfsg-2ubuntu1 ii libqt5xmlpatterns5 5.14.2-1 ii libstdc++6 10.1.0-3ubuntu1 ii python3 3.8.2-0ubuntu2 kig recommends no packages. Versions of packages kig suggests: pn khelpcenter
Bug#961336: marked as done (prboom-plus FTBFS on big endian)
Your message dated Sat, 06 Jun 2020 13:35:50 + with message-id and subject line Bug#961336: fixed in prboom-plus 2:2.5.1.7um+git82-1 has caused the Debian Bug report #961336, regarding prboom-plus FTBFS on big endian 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.) -- 961336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: prboom-plus Version: 2:2.5.1.7um+git72-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=prboom-plus ... cd /<>/obj-s390x-linux-gnu/data && ./rdatawad -I /<>/prboom2/data -palette palette.rgb -lumps lumps/switches.lmp lumps/animated.lmp lumps/crbrick.lmp lumps/crtan.lmp lumps/crgray.lmp lumps/crgreen.lmp lumps/crbrown.lmp lumps/crgold.lmp lumps/crred.lmp lumps/crblue.lmp lumps/crblue2.lmp lumps/crorange.lmp lumps/cryellow.lmp -marker C_START -lumps lumps/watermap.lmp -marker C_END -marker B_START -lumps lumps/sinetabl.lmp lumps/tangtabl.lmp lumps/tantoang.lmp lumps/gammatbl.lmp lumps/chexdeh.lmp lumps/bfgbex.lmp lumps/nervebex.lmp lumps/glshadow.lmp lumps/glfp.lmp lumps/glvp.lmp lumps/-prbhud-.lmp lumps/m_ammo.lmp lumps/m_armour.lmp lumps/m_arrow.lmp lumps/m_health.lmp lumps/m_key.lmp lumps/m_normal.lmp lumps/m_shadow.lmp lumps/m_power.lmp lumps/m_weap.lmp lumps/m_mark.lmp -marker B_END -sounds sounds/dsdgsit.wav sounds/dsdgatk.wav sounds/dsdgact.wav sounds/dsdgdth.wav sounds/dsdgpain.wav -graphics graphics/dig0.ppm graphics/dig1.ppm graphics/dig2.ppm graphics/dig3.ppm graphics/dig4.ppm graphics/dig5.ppm graphics/dig6.ppm graphics/dig7.ppm graphics/dig8.ppm graphics/dig9.ppm graphics/diga.ppm graphics/digb.ppm graphics/digc.ppm graphics/digd.ppm graphics/dige.ppm graphics/digf.ppm graphics/digg.ppm graphics/digh.ppm graphics/digi.ppm graphics/digj.ppm graphics/digk.ppm graphics/digl.ppm graphics/digm.ppm graphics/dign.ppm graphics/digo.ppm graphics/digp.ppm graphics/digq.ppm graphics/digr.ppm graphics/digs.ppm graphics/digt.ppm graphics/digu.ppm graphics/digv.ppm graphics/digw.ppm graphics/digx.ppm graphics/digy.ppm graphics/digz.ppm graphics/dig45.ppm graphics/dig47.ppm graphics/dig58.ppm graphics/dig91.ppm graphics/dig93.ppm graphics/stbr123.ppm graphics/stbr124.ppm graphics/stbr125.ppm graphics/stbr126.ppm graphics/stbr127.ppm graphics/boxul.ppm graphics/boxuc.ppm graphics/boxur.ppm graphics/boxcl.ppm graphics/boxcc.ppm graphics/boxcr.ppm graphics/boxll.ppm graphics/boxlc.ppm graphics/boxlr.ppm graphics/stkeys6.ppm graphics/stkeys7.ppm graphics/stkeys8.ppm graphics/stcfn096.ppm graphics/m_butt1.ppm graphics/m_butt2.ppm graphics/m_colors.ppm graphics/m_palno.ppm graphics/m_palsel.ppm graphics/m_vbox.ppm graphics/cross1.ppm graphics/cross2.ppm graphics/cross3.ppm -marker FF_START -flats flats/-n0_tex-.ppm -marker FF_END -marker SS_START -sprites 0,0,sprites/tnt1a0.ppm 33,66,sprites/dogsa1.ppm 33,66,sprites/dogsa2.ppm 33,66,sprites/dogsa3.ppm 33,66,sprites/dogsa4.ppm 33,66,sprites/dogsa5.ppm 33,66,sprites/dogsa6.ppm 33,66,sprites/dogsa7.ppm 33,66,sprites/dogsa8.ppm 33,66,sprites/dogsb1.ppm 33,66,sprites/dogsb2.ppm 33,66,sprites/dogsb3.ppm 33,66,sprites/dogsb4.ppm 33,66,sprites/dogsb5.ppm 33,66,sprites/dogsb6.ppm 33,66,sprites/dogsb7.ppm 33,66,sprites/dogsb8.ppm 33,66,sprites/dogsc1.ppm 33,66,sprites/dogsc2.ppm 33,66,sprites/dogsc3.ppm 33,66,sprites/dogsc4.ppm 33,66,sprites/dogsc5.ppm 33,66,sprites/dogsc6.ppm 33,66,sprites/dogsc7.ppm 33,66,sprites/dogsc8.ppm 33,66,sprites/dogsd1.ppm 33,66,sprites/dogsd2.ppm 33,66,sprites/dogsd3.ppm 33,66,sprites/dogsd4.ppm 33,66,sprites/dogsd5.ppm 33,66,sprites/dogsd6.ppm 33,66,sprites/dogsd7.ppm 33,66,sprites/dogsd8.ppm 33,66,sprites/dogse1.ppm 33,66,sprites/dogse2.ppm 33,66,sprites/dogse3.ppm 33,66,sprites/dogse4.ppm 33,66,sprites/dogse5.ppm 33,66,sprites/dogse6.ppm 33,66,sprites/dogse7.ppm 33,66,sprites/dogse8.ppm 33,66,sprites/dogsf1.ppm 33,66,sprites/dogsf2.ppm 33,66,sprites/dogsf3.ppm 33,66,sprites/dogsf4.ppm 33,66,sprites/dogsf5.ppm 33,66,sprites/dogsf6.ppm 33,66,sprites/dogsf7.ppm 33,66,sprites/dogsf8.ppm 33,66,sprites/dogsg1.ppm 33,66,sprites/dogsg2.ppm 33,66,sprites/dogsg3.ppm 33,66,sprites/dogsg4.ppm 33,66,sprites/dogsg5.ppm 33,66,sprites/dogsg6.ppm 33,66,sprites/dogsg7.ppm 33,66,sprites/dogsg8.ppm 33,66,sprites/dogsh1.ppm 33,66,sprites/dogsh2.ppm 33,66,sprites/dogsh3.ppm 33,66,sprites/dogsh4.ppm 33,66,sprites/dogsh5.ppm 33,66,sprites/dogsh6.ppm 33,66,sprites/dogsh7.ppm 33,66,sprites/dogsh8.ppm 33,67,sprites/dogsi0.ppm 33,67,sprites/dogsj0.ppm 33,67,sprites/dogsk0.ppm 33,67,
Bug#962250: marked as done (monero: Please skip hash-variant2-int-sqrt on armel)
Your message dated Sat, 06 Jun 2020 13:19:31 + with message-id and subject line Bug#962250: fixed in monero 0.16.0.0-2 has caused the Debian Bug report #962250, regarding monero: Please skip hash-variant2-int-sqrt on armel 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.) -- 962250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: monero Version: 0.15.0.5-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=monero&arch=armel ... 16/17 Test #7: block_weight . Passed 274.59 sec E: Build killed with signal TERM after 300 minutes of inactivity The non-failing build of 0.15.0.5-2 was: 17/17 Test #17: hash-variant2-int-sqrt ... Passed 17893.94 sec 17893 seconds is narrowly below 5 hours, and this was on a faster buildd. For 0.16.0.0-1 the test passed on identical hardware as the armel failure on armhf - in slightly over an hour. armel has no FPU and no native atomics instructions in the baseline. Please disable this (passing) test on armel. --- End Message --- --- Begin Message --- Source: monero Source-Version: 0.16.0.0-2 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of monero, 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. Jonas Smedegaard (supplier of updated monero package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 06 Jun 2020 14:30:46 +0200 Source: monero Architecture: source Version: 0.16.0.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Cryptocoin Team Changed-By: Jonas Smedegaard Closes: 962250 Changes: monero (0.16.0.0-2) unstable; urgency=medium . * skip heavy test on architectures without FPU in baseline spec; closes: bug#962250, thanks to Adrian Bunk * fix support DEB_BUILD_OPTIONS=nocheck Checksums-Sha1: e968e1200a5984f3e90182902bb22d60a4c2fed2 2497 monero_0.16.0.0-2.dsc 9a6fc6056670f5031e6ae94e2d75da8a26b3da4d 22084 monero_0.16.0.0-2.debian.tar.xz f2e56959729d774fb34e15b09a12dc2787dd0746 11672 monero_0.16.0.0-2_amd64.buildinfo Checksums-Sha256: d1ab182683327a03fcce62abc3376521ad4e4166c52abbaf06568b1bf44201c3 2497 monero_0.16.0.0-2.dsc 9b8032f7a1e1c2de1a346807f400c4d3d1df0627ec03fb7dfa3dd32546e2afeb 22084 monero_0.16.0.0-2.debian.tar.xz e153321abf402d8ad715a6db6b820c298c688afc38d93a37cfcb231886ee9a5f 11672 monero_0.16.0.0-2_amd64.buildinfo Files: e498391475cc354a218efa75473a63cb 2497 utils optional monero_0.16.0.0-2.dsc 87d228e02a04c9c4d775ccd92aeff779 22084 utils optional monero_0.16.0.0-2.debian.tar.xz b9c4c3a85d0382a7845b6757bee1dae7 11672 utils optional monero_0.16.0.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl7bleMACgkQLHwxRsGg ASFfnBAAgK/d5HAdtyo9OSoUWpWBhPeddyn1F4dR6tqNWV1xtvivpAWnZVfF5h2q PIUThdPvO3ZNTueqNlfv6p2lpOIjSY77Kw4VP7FZtw8SpylBr8uvFrV/aYwxZwjz DYRs+t1xad/hHmDburJfGSyRTWNs+0jF8/LQa1Vz0WN7NHsAzZHnuxH7WD3RhrAH BxJpTpYI1d6B9RC6yIbsDmw55ikJIQkE5TxzOO+j0umjp0+E8ocmUO5+pbS3xp7/ c7sS/0UW4wx0K/a26YLu5MB1uo0BHsceAlnN9oqC3gW1oOERmOaqEKsU47GHOi7L 0PwM3lEZ/xp83KSGW1aJl9+g1etKZ2pCrD8pe+T9LuVcRT3LcTSnFrrtdnq8+7Ip hxdra/CpopeTjrm8rvwucg864tHAnDlmkjj3m9GgdkCoLGvqiNNQbj9WP41SGQg7 NKnjHOyr2cpyNqRkgu7x0atHEKuENmC2P5nsnHxBnw1z0KiovtF2tB+LQg36t1gr 4W9K/iVcB6NdL2Y3frGVvPtFjuTnXg+SRCAuuId3CW7xABU/I6R1NSZBsvddTKEq I0xtk939cibDkA+xlmN51ivkTyg5EQfqY5fPvb0POKzlhh7atj3oAtgkdXmHfnNa 8pvtf2N5teVSQIpKIwuG9De8MXNMxvpa9Ld+SFMncpqxkCPT66o= =UVT+ -END PGP SIGNATURE End Message ---
Bug#962289: marked as done (gnutls28: CVE-2020-13777: session resumption works without master key allowing MITM)
Your message dated Sat, 06 Jun 2020 12:49:02 + with message-id and subject line Bug#962289: fixed in gnutls28 3.6.14-1 has caused the Debian Bug report #962289, regarding gnutls28: CVE-2020-13777: session resumption works without master key allowing MITM 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.) -- 962289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnutls28 Version: 3.6.13-4 Severity: grave Tags: security upstream Forwarded: https://gitlab.com/gnutls/gnutls/-/issues/1011 Control: found -1 3.6.4-1 Control: found -1 3.6.7-4+deb10u3 Hi Andreas, The following vulnerability was published for gnutsl28, filling it as RC given the resulting in authentication bypass possibility, but if you do not agree please downgrade. CVE-2020-13777[0]: | GnuTLS 3.6.x before 3.6.14 uses incorrect cryptography for encrypting | a session ticket (a loss of confidentiality in TLS 1.2, and an | authentication bypass in TLS 1.3). The earliest affected version is | 3.6.4 (2018-09-24) because of an error in a 2018-09-18 commit. Until | the first key rotation, the TLS server always uses wrong data in place | of an encryption key derived from an application. If you want I can try to help preparing as well a corresponding buster-security update. The issue was introduced in 3.6.4 upstream, so stretch is not affected. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-13777 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13777 [1] https://gnutls.org/security-new.html#GNUTLS-SA-2020-06-03 [2] https://gitlab.com/gnutls/gnutls/-/issues/1011 Regards, Salvatore --- End Message --- --- Begin Message --- Source: gnutls28 Source-Version: 3.6.14-1 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of gnutls28, 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. Andreas Metzler (supplier of updated gnutls28 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 06 Jun 2020 14:11:30 +0200 Source: gnutls28 Architecture: source Version: 3.6.14-1 Distribution: unstable Urgency: high Maintainer: Debian GnuTLS Maintainers Changed-By: Andreas Metzler Closes: 962199 962218 962289 Changes: gnutls28 (3.6.14-1) unstable; urgency=high . * Drop debugging code added in -4, fixes nocheck profile build error. Closes: #962199 * Add Daiki Ueno 462225C3B46F34879FC8496CD605848ED7E69871 key to debian/upstream/signing-key.asc. * New upstream version. + Fixes insecure session ticket key construction. [GNUTLS-SA-2020-06-03, CVE-2020-13777] Closes: #962289 + Drop 50_Update-session_ticket.c-to-add-support-for-zero-leng.patch 51_01-_gnutls_pkcs11_verify_crt_status-check-validity-agai.patch 51_02-x509-trigger-fallback-verification-path-when-cert-is.patch 51_03-tests-add-test-case-for-certificate-chain-supersedin.patch * Drop guile-gnutls.lintian-overrides. * 40_fix_ipv6only_testsuite_AI_ADDRCONFIG.diff: In gnutls-serv do not pass AI_ADDRCONFIG to getaddrinfo. This broke the testsuite on systems without IPv4 on non-loopback addresses. (Thanks, Adrian Bunk and Julien Cristau!) Hopefully Closes: #962218 Checksums-Sha1: 7c9199a08f66d1d0431141be3a3ffe6ac6e376e5 3479 gnutls28_3.6.14-1.dsc bea1b5abcb691acf014e592f41d0a9580a41216a 6069088 gnutls28_3.6.14.orig.tar.xz 49cb57a9accb3a95a0c23605b2c8d76b21d90dd0 854 gnutls28_3.6.14.orig.tar.xz.asc 7c18ebbc0669216fa3ad82ba6539276cb0626a3d 62708 gnutls28_3.6.14-1.debian.tar.xz Checksums-Sha256: 9f85587356a29ceb26ba6d741348e190090b9f2c86b6352626eff2ea5cbe6dfd 3479 gnutls28_3.6.14-1.dsc 5630751adec7025b8ef955af4d141d00d252a985769f51b4059e5affa3d39d63 6069088 gnutls28_3.6.14.orig.tar.xz a3e05b531b68a4aca8fdc5dce83e7091b5aa859d76de7e8ba9992047272f04dd 854 gnutls28_3.6.14.orig.tar.xz.asc 1
Bug#962218: marked as done (gnutls28: build fails on IPv6-only buildds)
Your message dated Sat, 06 Jun 2020 12:49:02 + with message-id and subject line Bug#962218: fixed in gnutls28 3.6.14-1 has caused the Debian Bug report #962218, regarding gnutls28: build fails on IPv6-only buildds 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.) -- 962218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962218 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnutls28 Version: 3.6.13-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=gnutls28&ver=3.6.13-3 https://buildd.debian.org/status/logs.php?pkg=gnutls28&ver=3.6.13-4 ... SKIP: ssl30-server-kx-neg = SKIP ssl30-server-kx-neg (exit status: 77) SKIP: ssl30-cipher-neg == SKIP ssl30-cipher-neg (exit status: 77) SKIP: fips-mode-pthread === We are not in FIPS140 mode SKIP fips-mode-pthread (exit status: 77) SKIP: fips-test === Please note that if in FIPS140 mode, you need to assure the library's integrity prior to running this test We are not in FIPS140 mode SKIP fips-test (exit status: 77) SKIP: fips-override-test Please note that if in FIPS140 mode, you need to assure the library's integrity prior to running this test We are not in FIPS140 mode SKIP fips-override-test (exit status: 77) SKIP: ssl30-cert-key-exchange = SKIP ssl30-cert-key-exchange (exit status: 77) FAIL: dtls_hello_random_value = testing: default client:156: client: Handshake failed: Resource temporarily unavailable, try again. server:271: server: Handshake has failed: The TLS connection was non-properly terminated. FAIL dtls_hello_random_value (exit status: 1) SKIP: starttls.sh = SKIP starttls.sh (exit status: 77) SKIP: starttls-ftp.sh = SKIP starttls-ftp.sh (exit status: 77) SKIP: starttls-smtp.sh == SKIP starttls-smtp.sh (exit status: 77) SKIP: starttls-lmtp.sh == SKIP starttls-lmtp.sh (exit status: 77) SKIP: starttls-pop3.sh == SKIP starttls-pop3.sh (exit status: 77) SKIP: starttls-xmpp.sh == SKIP starttls-xmpp.sh (exit status: 77) SKIP: starttls-nntp.sh == SKIP starttls-nntp.sh (exit status: 77) SKIP: starttls-sieve.sh === SKIP starttls-sieve.sh (exit status: 77) SKIP: p11-kit-trust.sh == p11-kit trust module was not found SKIP p11-kit-trust.sh (exit status: 77) Testsuite summary for GnuTLS 3.6.13 # TOTAL: 471 # PASS: 455 # SKIP: 15 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See tests/test-suite.log Please report to b...@gnutls.org make[6]: *** [Makefile:8525: test-suite.log] Error 1 The conova buildds are IPv6-only, see #962019 for a similar problem in perl. --- End Message --- --- Begin Message --- Source: gnutls28 Source-Version: 3.6.14-1 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of gnutls28, 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. Andreas Metzler (supplier of updated gnutls28 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 06 Jun 2020 14:11:30 +0200 Source: gnutls28 Architecture: source Version: 3.6.14-1 Distribution: unstable Urgency: high Maintainer: Debian GnuTLS Maintainers Changed-By: Andreas Metzler Closes: 962199 962218 962289 Changes: gnutls28 (3.6.14-1) unstable; urgency=high . * Drop debugging code added in -4, fixes nocheck profile build error. Closes: #962199 * Add Daiki Ueno 462225C3B46F34879FC8496CD605848ED7E69871 key to debian/upstream/signing-key.asc. * New upstream version. + Fixes in
Bug#962335: FTBFS: new upstream version available with bug fixes
Source: pandas Version: 1.0.3+dfsg2-1 Severity: serious Justification: FTBFS pandas 1.0.3+dfsg2-1 fails to build from source, evidently due to new DeprecationWarnings from jedi 1.17.0 interfering with test_tab_complete_warning (tests/frame/test_api.py) Upstream has patched it with #8af5625 https://github.com/pandas-dev/pandas/commit/8af5625bbd69e0fd1d3e9ca7b23267aababdee94 but probably better to apply the whole new upstream release (1.0.4) than the individual patch.
Processed: tagging 962330
Processing commands for cont...@bugs.debian.org: > tags 962330 + ftbfs bullseye sid Bug #962330 [src:conky] conky: FTBFS in sid Added tag(s) sid, bullseye, and ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 962330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 962318 in 8.43+dfsg-1
Processing commands for cont...@bugs.debian.org: > # probably earlier as well > found 962318 8.43+dfsg-1 Bug #962318 [src:libmojolicious-perl] libmojolicious-perl: build fails on IPv6-only buildds Marked as found in versions libmojolicious-perl/8.43+dfsg-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 962318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962318 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961907: marked as done (ca-certificates: Remove expired mozilla/AddTrust_External_Root.crt)
Your message dated Sat, 06 Jun 2020 11:32:26 + with message-id and subject line Bug#961907: fixed in ca-certificates 20200601~deb9u1 has caused the Debian Bug report #961907, regarding ca-certificates: Remove expired mozilla/AddTrust_External_Root.crt 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.) -- 961907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ca-certificates Version: 20190110 Severity: important Dear Maintainer, The AddTrust_External_Root.crt certificate has expired, and its continued inclusion in the ca-certificates set is causing GnuTLS-based client applications (and OpenSSL 1.0.x) to barf on a lot of sites. It could probably be argued that this is a bug in GnuTLS rather than ca-certificates, but I don't see the point in keeping an expired certificate here. The problem is confirmed to affect Epiphany and VLC. See also: https://gitlab.com/gnutls/gnutls/-/issues/1008 https://www.agwa.name/blog/post/fixing_the_addtrust_root_expiration Best regards, -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fi_FI.UTF-8), LANGUAGE=fr:en_GB:fi (charmap=UTF-8) (ignored: LC_ALL set to fi_FI.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ca-certificates depends on: ii debconf [debconf-2.0] 1.5.74 ii openssl1.1.1g-1 ca-certificates recommends no packages. ca-certificates suggests no packages. -- debconf information excluded --- End Message --- --- Begin Message --- Source: ca-certificates Source-Version: 20200601~deb9u1 Done: Michael Shuler We believe that the bug you reported is fixed in the latest version of ca-certificates, 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 961...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Shuler (supplier of updated ca-certificates package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 05 Jun 2020 11:52:50 -0500 Source: ca-certificates Binary: ca-certificates ca-certificates-udeb Architecture: source Version: 20200601~deb9u1 Distribution: stretch Urgency: medium Maintainer: Michael Shuler Changed-By: Michael Shuler Description: ca-certificates - Common CA certificates ca-certificates-udeb - Common CA certificates - udeb (udeb) Closes: 721976 911289 916833 955038 956411 961907 Changes: ca-certificates (20200601~deb9u1) stretch; urgency=medium . * Rebuild for stretch. * Merge changes from 20200601 - d/control * This release updates the Mozilla CA bundle to 2.40, blacklists distrusted Symantec roots, and blacklists expired "AddTrust External Root". Closes: #956411, #955038, #911289, #961907 * Fix permissions on /usr/local/share/ca-certificates when using symlinks. Closes: #916833 * Remove email-only roots from mozilla trust store. Closes: #721976 Checksums-Sha1: d07b156c902860559fcd8a7b15ff32527146d2f1 1855 ca-certificates_20200601~deb9u1.dsc f035e1faac582fa3d7896ac9cc90e26bf554e3f1 245956 ca-certificates_20200601~deb9u1.tar.xz Checksums-Sha256: 81772ce188acf4ef93aface3dc9fc0516fb193d1e7242c23a6e18a002a455302 1855 ca-certificates_20200601~deb9u1.dsc 873a9eb9ec66db1d9bc7c6829ee789fe6b1ba4ed497745df699b35145a3c98cd 245956 ca-certificates_20200601~deb9u1.tar.xz Files: 8038cddc87c85e5fb59a877f7a2965c3 1855 misc optional ca-certificates_20200601~deb9u1.dsc 03cbc91dcc4fe1f2bd8a8ee6b035c6f3 245956 misc optional ca-certificates_20200601~deb9u1.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl7ap3wACgkQiNJCh6LY mLGr5hAAt3neYIqMBwy5MKVycOqUzkeSBg7LncihwJKqkqhZTIZ3JwOjHNIQc9WF 1ccJJXJwY1naiGCCDnJPtfJmOQB26TXZ18CsiW
Bug#962086: marked as done (freecad: FTBFS with boost 1.71)
Your message dated Sat, 06 Jun 2020 11:19:13 + with message-id and subject line Bug#962086: fixed in freecad 0.18.4+dfsg2-4 has caused the Debian Bug report #962086, regarding freecad: FTBFS with boost 1.71 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.) -- 962086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: freecad Version: 0.8.14+dfsg2-3 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) User: team+bo...@tracker.debian.org Usertags: boost1.71 Control: block 961995 by -1 libboost-signals-dev was dropped in 1.71 and so freecad no longer builds. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: freecad Source-Version: 0.18.4+dfsg2-4 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of freecad, 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. Gianfranco Costamagna (supplier of updated freecad package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 06 Jun 2020 12:07:18 +0200 Source: freecad Binary: freecad freecad-python3 freecad-runtime freecad-common libfreecad-python3-0.18 Architecture: source Version: 0.18.4+dfsg2-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Gianfranco Costamagna Description: freecad- Extensible Open Source CAx program freecad-common - Extensible Open Source CAx program - common files freecad-python3 - Extensible Open Source CAx program - Python 3 binaries freecad-runtime - Extensible Open Source CAx program - runtime files libfreecad-python3-0.18 - Extensible Open Source CAx program - Python 3 library files Closes: 962086 Changes: freecad (0.18.4+dfsg2-4) unstable; urgency=medium . * Team upload . [ Gianfranco Costamagna ] * [224b2c8a] Drop unused libboost-signals-dev (Closes: #962086) . [ Graham Inggs ] * [e3aa33cd] Fix TaperedHole test for OCCT 7.4 Checksums-Sha1: c97b5e3dcc907411bbf868285c9811b5c2b9f79b 3289 freecad_0.18.4+dfsg2-4.dsc bb8a4e4084602baa00936fc245f89ed4bd420015 36832 freecad_0.18.4+dfsg2-4.debian.tar.xz c432886818320fa298ab93f5971c5384020f33e7 18879 freecad_0.18.4+dfsg2-4_source.buildinfo Checksums-Sha256: b6584ad10836e2f4f7f7285fe45a6ae8ebfc99508cd78d1cb3abcd3fe938bad3 3289 freecad_0.18.4+dfsg2-4.dsc 11f9f4bb64e513af370e534ce1a86d34d0e0dd18a2f40b50138143fa11a44718 36832 freecad_0.18.4+dfsg2-4.debian.tar.xz 28081217fb40a8962c7dcb262eba0e769e1c9fc48762ed7cef02750f5dc71800 18879 freecad_0.18.4+dfsg2-4_source.buildinfo Files: 19055aa26ee39613845f3ad66f9bd079 3289 science optional freecad_0.18.4+dfsg2-4.dsc 20fb90db7a147923661c220f5138c523 36832 science optional freecad_0.18.4+dfsg2-4.debian.tar.xz 7df9545c6d4c1a6478cff9db58b68cdd 18879 science optional freecad_0.18.4+dfsg2-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl7bcIkACgkQ808JdE6f XdmfaBAAsWCLDZ5IZMVEpewI4EPmx3EEqkZveoisIyheXy4v2dWYBw27FGdmJP/u FMoQ4eQBucZ5VgnJSpHdwZPSgXkNQJT1FDVioH5OlXMha0A6nM1HdICojcroK/s5 jGGr/2iIO/LCLAdlx2YegIt2sGRot+tVNtQe59W4ZT4Xu5En0K/XUpwjtX+NswAX goUdqn4seDZ4g6j/GRzR9iqiWBl9/gZ+ki1+7vhew0E4RIzpIId13SgTKvvm0cLh 9+40t/d56qBVCz57MHbqJ3aR15lZGwXM9hjVJSJWD5wptQSYmD2S993uERyfYjpa AK1Y6dYmUAKLb4JjLoqrq+k/AqmFPWDzf7HyNsaIInU2xiUtyemS6bXkLoOJIJuW 35x4i8j7rykiMwVMFeMiDYdtMzOkIaELOPILVVi0nXSnYjEqaz8NNBpaRKZrikmf WK03LQea0UMFAzdng4wE6ERXP2jc8QAvBobApdbD5kQsRyC1gtIOhFxz8E3TA0x1 j/g6f1MjNdsVBskrk9sX4Re/5rvlCmFirQ6oPRWMHLNbp+jIN95/UbCx7ARcX9uZ r0YCNLrC8sG251mhApER5tblaw8B/zOokNLADj3P8nYfRUu/ytdqfVvmGh8RAmbG j/6D/NRj/NKVz3I/PpISjjN4tPlfccQF59QhjRJGbnPBG/gwXkU= =imec -END PGP SIGNATURE End Message ---
Processed: found 962323 in 2:2.2.12-1, found 962323 in 1:1.11.28-1~deb10u1, found 962323 in 1:1.10.7-2+deb9u8 ...
Processing commands for cont...@bugs.debian.org: > # Add some BTS metadata > found 962323 2:2.2.12-1 Bug #962323 [python-django] python-django: CVE-2020-13254 CVE-2020-13596 There is no source info for the package 'python-django' at version '2:2.2.12-1' with architecture '' Unable to make a source version for version '2:2.2.12-1' Marked as found in versions 2:2.2.12-1. > found 962323 1:1.11.28-1~deb10u1 Bug #962323 [python-django] python-django: CVE-2020-13254 CVE-2020-13596 Marked as found in versions python-django/1:1.11.28-1~deb10u1. > found 962323 1:1.10.7-2+deb9u8 Bug #962323 [python-django] python-django: CVE-2020-13254 CVE-2020-13596 Marked as found in versions python-django/1:1.10.7-2+deb9u8. > found 962323 1:1.10.7-2+deb9u7 Bug #962323 [python-django] python-django: CVE-2020-13254 CVE-2020-13596 Marked as found in versions python-django/1:1.10.7-2+deb9u7. > found 962323 1:1.10.7-2 Bug #962323 [python-django] python-django: CVE-2020-13254 CVE-2020-13596 Marked as found in versions python-django/1:1.10.7-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 962323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962319: marked as done (libextutils-hascompiler-perl: test failures with perl 5.30.3-2)
Your message dated Sat, 06 Jun 2020 10:48:37 +
with message-id
and subject line Bug#962319: fixed in libextutils-hascompiler-perl 0.021-3
has caused the Debian Bug report #962319,
regarding libextutils-hascompiler-perl: test failures with perl 5.30.3-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
962319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962319
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libextutils-hascompiler-perl
Version: 0.021-2
Severity: serious
This package fails its test suite with perl 5.30.3-2 from unstable.
The reasons are somewhat complicated. The failing test checks
that ExtUtils::HasCompiler and ExtUtils::MakeMaker give the
same result when trying to build a program that is statically linked
with libperl.a.
Up until perl 5.30.3-2, this test build failed with ExtUtils::HasCompiler:
it checked $Config{useshrplib} and bailed out because it concluded
that our libperl is built dynamically and we therefore don't support
static linking. On the other hand, the ExtUtils::MakeMaker reference
build failed because the package does not build depend on libperl-dev,
so libperl.a was not available.
With perl 5.30.3-2, #798626 is fixed and $Config{useshrplib} now
correctly indicates that static linking is supported. However, the
ExtUtils::HasCompiler check does not actually link, so it fails to detect
that libperl.a is missing. ExtUtils::MakeMaker still fails in the same
way, so the results now disagree.
I suggest that we fix this in a way that's compatible with both
older and newer perl versions, by adding a build dependency on
libperl-dev and patching away the check $Config{useshrplib} check in
ExtUtils::HasCompiler::can_compile_static_library() . On Debian we build
both static and dynamic versions of libperl, so static builds should
be supported.
Transcript of the failure below. Note that the warning about
perl and Config.pm having 'different ideas about the architecture'
is not the cause of this. It is just a warning that we'll handle
separately (cf. #962138)
# Failed test 'MakeMaker agrees we can compile static'
# at t/compare.t line 67.
# got: '1'
# expected: undef
# Couldn't run make test: make[2]: Entering directory '/tmp/BDk9YhPh04'
# make[2]: warning: jobserver unavailable: using -j1. Add '+' to parent make
rule.
# Writing "Makefile.aperl" for this perl
# Have /usr/lib/x86_64-linux-gnu/perl-base
# Want /usr/lib/x86_64-linux-gnu/perl/5.30
# Your perl and your Config.pm seem to have different ideas about the
# architecture they are running on.
# Perl thinks: [perl-base]
# Config says: [x86_64-linux-gnu-thread-multi]
# This may or may not cause problems. Please check your installation of perl
# if you have problems building this extension.
# Warning: /usr/lib/x86_64-linux-gnu/perl/5.30/../../libperl.a not found
# If you're going to build a static perl binary, make sure perl is installed
# otherwise ignore this warning
# Generating a Unix-style Makefile.aperl
# Writing Makefile.aperl for EUHC::Test
# Writing MYMETA.yml and MYMETA.json
# make -f Makefile.aperl perl
# make[3]: Entering directory '/tmp/BDk9YhPh04'
# Writing perlmain.c
# mv perlmain.ct perlmain.c
# x86_64-linux-gnu-gcc -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv
-fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -O2 -g -DVERSION=\"\" -DXS_VERSION=\"\" -fPIC
"-I/usr/lib/x86_64-linux-gnu/perl/5.30/CORE" perlmain.c
# make[3]: *** No rule to make target
'/usr/lib/x86_64-linux-gnu/perl/5.30/../../libperl.a', needed by 'perl'. Stop.
# make[3]: Leaving directory '/tmp/BDk9YhPh04'
# make[2]: *** [Makefile:956: perl] Error 2
# make[2]: Leaving directory '/tmp/BDk9YhPh04'
# Looks like you failed 1 test of 3.
--
Niko Tyni nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libextutils-hascompiler-perl
Source-Version: 0.021-3
Done: Niko Tyni
We believe that the bug you reported is fixed in the latest version of
libextutils-hascompiler-perl, 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.
Niko Tyni (supplier of updated libextutils-hascompiler-perl
package)
(This message was generated automatically at th
Bug#962317: marked as done (cgview: autopkgtest failure: readlink: missing operand)
Your message dated Sat, 06 Jun 2020 10:48:29 + with message-id and subject line Bug#962317: fixed in cgview 0.0.20100111-6 has caused the Debian Bug report #962317, regarding cgview: autopkgtest failure: readlink: missing operand 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.) -- 962317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cgview Version: 0.0.20100111-5 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 cgview, great. However, it fails. 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. 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=cgview https://ci.debian.net/data/autopkgtest/testing/amd64/c/cgview/5700999/log.gz autopkgtest [22:35:03]: test run-unit-test: [--- readlink: missing operand Try 'readlink --help' for more information. autopkgtest [22:35:04]: test run-unit-test: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: cgview Source-Version: 0.0.20100111-6 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of cgview, 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. Andreas Tille (supplier of updated cgview package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 06 Jun 2020 12:19:54 +0200 Source: cgview Architecture: source Version: 0.0.20100111-6 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 962317 Changes: cgview (0.0.20100111-6) unstable; urgency=medium . * Fix usage of java-wrappers Closes: #962317 Checksums-Sha1: 886dc926e92623261765eff4052d8aefb05079ee 2100 cgview_0.0.20100111-6.dsc 4508465c9eb91dd84d38da1540f0d4be4cea68a6 1803328 cgview_0.0.20100111-6.debian.tar.xz b4c513ffd8ccfa4a5658b4ce1b11369f2d51289b 10648 cgview_0.0.20100111-6_amd64.buildinfo Checksums-Sha256: e5c469202edf33dc1a1961777d896b4be491967315e53a08dc318edd59106eb4 2100 cgview_0.0.20100111-6.dsc 41e7f17cc9e01663277c2c561181cfe7ec41e4507ee86d356742581d94120ce6 1803328 cgview_0.0.20100111-6.debian.tar.xz c16ecfabb586318c5ba070535a1cc88208bc1900e492453cf2fe576c49300a58 10648 cgview_0.0.20100111-6_amd64.buildinfo Files: 34581e60440bf5fba899a66847bfec08 2100 science optional cgview_0.0.20100111-6.dsc f375a742b6503305b83a9f3d9efe8b73 1803328 science optional cgview_0.0.20100111-6.debian.tar.xz 58789e2209dd91071a439cf9f3206d25 10648 science optional cgview_0.0.20100111-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl7bb2ERHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtH7tA//UqVSDrsS6+oDJmAS2MF6oaNO0wrLeMGz qg0Z5j8oNZlYf2sRSt3yaLiLEMNxhr1OvuzaZ7OUO+gpJ8aiC14ZDlehFY4ZbKQv qAk0oHDbOj0xBv7LF5b/rQZMY3NAlAPBB7LcE5izawGBxBT/OXdPA65SR92tuQXN Ua4vnrCdyQ+FeIjCKOhIlmPvqi05UyJLFUuJXF+B7inoZD+DTqeh7n51GzjJS9L2 WlQ+stlPUYOTq84X1xVS8QV2eIyixhL5NpXZbXvzYSWNNnwpvQO4HOofjWz8v2IM el/SLsNBTxyFI+6ookylP5DnQw1wcBwtXJh1C9byGMUGerElJDWj1FR2wvuN5jvr CNy9RQbmI9JvBvqujGxPJPJuUnHyd0boSv8mCsO3dud4+MOl52okrcOspfIiXLy9 lG1Z8g8kxvBXR2CtUNVky4vrabJBW6cZmW90qF3uIkb8nkHJm46JtCp0GCtp0dI4 cOiVhV74ubRuygW/aCtf30OlAwsDJxsaq0MNJuAtGgKwgzuUqvCLGlHKRo7UODNB 3/W8nD3nmjTCMlgj/md6LVC4b5FNVP0QLpbH+hkIcr2OVTw2Tpas2HY10dV0SKAg fJr6sOms7luvTVgjGZcdYSljAjcWX5+auajGPqR26f1ACbqpFfrugMdRoq23mG1d 5tbAUldCVXQ= =+A6T -END PGP SIGNATURE End Message ---
Bug#953064: marked as done (FTBFS on i386)
Your message dated Sat, 06 Jun 2020 10:33:51 + with message-id and subject line Bug#953064: fixed in odin 2.0.4-0.1 has caused the Debian Bug report #953064, regarding FTBFS on i386 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.) -- 953064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: odin Severity: serious odin FTBFSes on i386. This also means that on i386 it still uses Qt4. Cheers, Moritz --- End Message --- --- Begin Message --- Source: odin Source-Version: 2.0.4-0.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of odin, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 953...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated odin 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: Wed, 20 May 2020 23:12:09 +0300 Source: odin Architecture: source Version: 2.0.4-0.1 Distribution: unstable Urgency: medium Maintainer: NeuroDebian Team Changed-By: Adrian Bunk Closes: 953064 Changes: odin (2.0.4-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream release. - Fixed the build on i386. (Closes: #953064) Checksums-Sha1: ea735ee7aff37fcea63ece871b7e0467166ec660 2200 odin_2.0.4-0.1.dsc 2962f1d96f236733b183355cbbcfd79b520436b8 2043474 odin_2.0.4.orig.tar.gz df368a9f087248127666471f67884a5f134e41dc 6868 odin_2.0.4-0.1.debian.tar.xz Checksums-Sha256: 27b59178279dd101131295baf3431ab85c6b9b3398df19b9ab6eaaa912004157 2200 odin_2.0.4-0.1.dsc b9a6eb865aff8c08d0dd260563377cc9e1734b90f5d8a08c4f650491a009 2043474 odin_2.0.4.orig.tar.gz 3970530f1f69dcd5134f4315d293b71b77bdeb9020bbd0be33d337e0f2e7a849 6868 odin_2.0.4-0.1.debian.tar.xz Files: d82e70fd149102ff178164c731c552fd 2200 science optional odin_2.0.4-0.1.dsc 371e62bfab0cbea6ddacc39d850849d4 2043474 science optional odin_2.0.4.orig.tar.gz 7119f735ff18bbcbbfb8d978a67dc81c 6868 science optional odin_2.0.4-0.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl7GMPYACgkQiNJCh6LY mLGp7BAAzcY06G8iO/xFXTpL2/O34Ay7/YjAqYDw86Y/K835BMIKcfaO3X+E60fF 2xK/01lVUDVliRHqG5SfQxX2hHya9lopToNc9ptWtConfY0doG95HlVgX1u2vWSl 9IBGYJA2304OwhsQQEnesTerCbrYBXOe3O95U8ggC9fATHsFv3DCs3H6oVhqZU6A zmBcQdIJIXIwUebHVSXCBlvRmYzRw0biEMTTr4DaQaz2wWRXjdWfe9Inc7W1Hyg5 dLFd0Wvxqdl6xLXUeQfUMvW5leQ5RXB8vnfxchUaC6w5DmaK05+vG3P/ZJHAj5K4 9VYnkN+giK0qRKQfq2kKciyXbKc2B+65LQFgRpKAFxUrnf3/CB84ep9dvNn2npE0 18+I9Cwp1M19m42T7KuBvNkZFhgvkttn3un3y4BQ/Eq6bjYRk/REd+0sCV9aBq4L ccgGysRQwZ8pUX3p1ASvd2A3ICxyX3nYmx2dFuA0zMjktgah81CgazriUZHiORgv WbasuR51oVk5J0jpvl5bs3S9YXauW5Kus9iY06JjLT0ZrNyHQ7YGfzPVj4ktUhrX D3u4lfTfD1CmKhpGB9EVHbBDyomK4Vp0IqR41hN3k++eSXHAJqrH2tXQARAVL4VA vPB4ixV9GKIS7EOb8/4GuyimnP2KYwaIAgutwST8Ph/pyOeJxHM= =eByw -END PGP SIGNATURE End Message ---
Bug#960422: marked as done (glob2: FTBFS with boost 1.71)
Your message dated Sat, 06 Jun 2020 10:33:37 + with message-id and subject line Bug#960422: fixed in glob2 0.9.4.4-4 has caused the Debian Bug report #960422, regarding glob2: FTBFS with boost 1.71 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.) -- 960422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glob2 Version: 0.9.4.4-3 Severity: important Tags: patch sid bullseye User: team+bo...@tracker.debian.org Usertags: boost1.71 glob2 fails to build with boost 1.71: | g++ -o src/AIEcho.o -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -DHAVE_CONFIG_H -D_GNU_SOURCE=1 -D_REENTRANT -Ilibgag/include -I. -I/usr/include/SDL src/AIEcho.cpp | src/AIEcho.cpp: In member function 'bool AIEcho::SearchTools::enemy_building_iterator::operator!=(const AIEcho::SearchTools::enemy_building_iterator&) const': | src/AIEcho.cpp:4390:102: error: cannot convert 'boost::logic::tribool' to 'bool' in return | 4390 | return is_end!=rhs.is_end || team!=rhs.team || building_type!=rhs.building_type || level!=rhs.level || construction_site!=rhs.construction_site; | | ~^~~ | | | | | boost::logic::tribool Patch at https://patches.ubuntu.com/g/glob2/glob2_0.9.4.4-3ubuntu1.patch Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: glob2 Source-Version: 0.9.4.4-4 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of glob2, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated glob2 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: Tue, 02 Jun 2020 13:56:20 +0300 Source: glob2 Architecture: source Version: 0.9.4.4-4 Distribution: unstable Urgency: low Maintainer: Debian QA Group Changed-By: Adrian Bunk Closes: 960422 Changes: glob2 (0.9.4.4-4) unstable; urgency=low . * QA upload. * Add patch for FTBFS with Boost >= 1.69. (Closes: #960422) Checksums-Sha1: e431775f960991fb044785f64197524b4fb8f994 2073 glob2_0.9.4.4-4.dsc 4d8f33d1f0e4d1d8b93062c04c035ff576767cb8 25772 glob2_0.9.4.4-4.debian.tar.xz Checksums-Sha256: 789637bf609d187973e6728f1e61d52fadefcdf1aefe030af32e08f8ee90cd12 2073 glob2_0.9.4.4-4.dsc c7447a747b6ac73a5493e2aa7708d29f0f530cb3869f6be5588bfb015023b702 25772 glob2_0.9.4.4-4.debian.tar.xz Files: 74e913c494b13fb338e7cd9ef30d3800 2073 games optional glob2_0.9.4.4-4.dsc 7452e720b8f84e7fc20f8ccdc33ac333 25772 games optional glob2_0.9.4.4-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl7bbKEACgkQiNJCh6LY mLETrQ/+Mf3GpHqBuTQZdECchnBu36mN4cvOMlkHBT/dQznNE4BRX0duYEqAECjS iQAXkinIbSdDokJMUND9Y9y/+0kZiPLppZ9PJtKzkbzNvONdOzdMApt3mryK2DAp v/PI5h4vkSPuuQ0v9FQJAYbbpwDQrXKdDQn6y7Thpl4jszSI21kOkfcP+GIG8ui4 5eUsQw4Eiep5An0dHO57U9VplPyew+EiGOSbzbF6zwMZLzCxhbySJLIczMz0zKzx A9QhuMkRWpYKZ4nFAG54CAAQB4+5y/ENh95bswMSXkN0ITperHmzCc+5O18TvJO6 ps03SMBgUwQ4Pn+5EMC2OdjVg3jfH6HBo62YKXFa7iKRySQz86PXrkoMs2+tLJmK M6U7hkaADIcelxVYB+eLXt01x2zLi0uccIuRNhtRR+loMiyJJV9slXp62RwY2Dil sOnM2jlOL1TpnP/sh2+HZ712Lvn61lvMGncsE8vR/HHXjw1mujGoRAMdeVGJZ4mZ w4TLh1TJ5xcW1DTqogS+Bo/QGYkRtTZN5mHuF7HZZtSLG2VZ9qZ9mtBRp9Vn0GEu YHmPA8PTENIx70ULqV3eR57qlvfqh4U82WFlJyP1h0ZyFimG9Ys1Go+clMBd14KJ F9RVhJ+eqF55gNFO4GvPgKqFnPdOO3HZmhP6xENW80NPoaae10g= =mt2e -END PGP SIGNATURE End Message ---
Bug#950654: marked as done (node-eslint-plugin-html seems unusable without eslint)
Your message dated Sat, 06 Jun 2020 09:48:52 + with message-id and subject line Bug#950654: fixed in node-eslint-plugin-html 5.0.5-1 has caused the Debian Bug report #950654, regarding node-eslint-plugin-html seems unusable without eslint 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.) -- 950654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950654 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-eslint-plugin-html Version: 3.2.1-1 Severity: serious This package seems unusable without eslint. See https://ci.debian.net/data/autopkgtest/unstable/amd64/n/node-eslint-plugin-html/3801441/log.gz --- End Message --- --- Begin Message --- Source: node-eslint-plugin-html Source-Version: 5.0.5-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of node-eslint-plugin-html, 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 950...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated node-eslint-plugin-html package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 06 Jun 2020 11:29:23 +0200 Source: node-eslint-plugin-html Architecture: source Version: 5.0.5-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jonas Smedegaard Closes: 950654 Changes: node-eslint-plugin-html (5.0.5-1) unstable; urgency=medium . [ upstream ] * new release(s) . [ Jonas Smedegaard ] * add myself as uploader * fix have autopkgtest depend on node-eslint; closes: bug#950654, thanks to Xavier Guimard * tighten (build-)dependencies on node-htmlparser2 node-semver Checksums-Sha1: 0d2163f0ab3fc5136956a00739cc0e420a00636a 2338 node-eslint-plugin-html_5.0.5-1.dsc 499a45ecf960509d12ce4e5e08710432ac1fdc49 68665 node-eslint-plugin-html_5.0.5.orig.tar.gz af643c06b3afafca6a0bb094eed934dfd4b674db 3428 node-eslint-plugin-html_5.0.5-1.debian.tar.xz b789141562ea9dfa3e177bd20cc0968057ed05c8 14388 node-eslint-plugin-html_5.0.5-1_amd64.buildinfo Checksums-Sha256: f8ce9a4a9fa71a23e6400132fa25db3bb341a8e289bbd38c7319f0c667bded21 2338 node-eslint-plugin-html_5.0.5-1.dsc a53a9cae841cb16240cecc3bdca8fd838ce15c44500c2aef907543324aa8366d 68665 node-eslint-plugin-html_5.0.5.orig.tar.gz eaf75dc47ae10ee0b077cfa57367d45738bb7ab642fdb8bf10bb446515c72bc6 3428 node-eslint-plugin-html_5.0.5-1.debian.tar.xz 2cae1696c478281f1720be2e094aadcf3272247ab52db132ce39440b4cd8334e 14388 node-eslint-plugin-html_5.0.5-1_amd64.buildinfo Files: 802d9a32516087d58d0ff5cc6ac31896 2338 javascript optional node-eslint-plugin-html_5.0.5-1.dsc 95be731c828dcba8a707104c5bf345c0 68665 javascript optional node-eslint-plugin-html_5.0.5.orig.tar.gz adcea42c7a09961bd7d9dd74f808006b 3428 javascript optional node-eslint-plugin-html_5.0.5-1.debian.tar.xz 5d81ecb0f6140c7b34d03239726dad15 14388 javascript optional node-eslint-plugin-html_5.0.5-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl7bZDYACgkQLHwxRsGg ASEBJQ/+PQduRFI8ZWukx5tcIi5fUyukIq+6NRm+L0tPSLIUrXmpO3z+ia9wYQpS LQvArlnFGQfo+olKr+YOd55O3ic7y+UIv+7hfagFHMep+jxCeoc3+0gCSYpXDiAp bUltnjjnApiWN8KVGLoLsGX3aSCRoYieORFZ33krmt44BwH4U9YkEVcxNt+iPqwn pV0DuF3BN4d2qUJfuFkMXOsc39d8oLJ5MUN/x9qssDpvmAQB/0UxefX1hIRnEqGs bWHu41boyESMkr7XaD1p+HULtIj2MBMBSbv+2bKR4/sI66cJpQUo6sQIKtV1+fnw yPucugcGoCeCMcJ0IYlXDmeDjjTJPwg3XBfwOYRtNfnFb98Wt0IWzicldUVn3O43 v3hRJcu8274gS6iA+Q6f5XIa2kbdui/StoQZC8UuDoPrLTYotKgkT4/MOtnAYJ69 Ce65BK5GKwny4NJA49FDkU84cO0G/wfBonBOb7fO0LsDTw1WYY6QSYCTrS+fNsIN NlqdiAJ/7XuUvI+Vpc8P7fLfOblXBpcJphw0sbEJ96pyZAOp3nugjBR3auSM/ekL fYwK99IrU+guJnI6H7O2blhMRhrtnq54PqVq1YTWbHaMo/FYrMeH64oB7g+CkKfS srLADjOnFEEuZwZrMKRBd2HM0ZUrW1jkaHHDEdkeSb4YXCIYGVQ= =mZzw -END PGP SIGNATURE End Message ---
Bug#950654: marked as pending in node-eslint-plugin-html
Control: tag -1 pending Hello, Bug #950654 in node-eslint-plugin-html reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-eslint-plugin-html/-/commit/27a2a281735f77b2e2615775a4dd36b2fdd167b6 fix have autopkgtest depend on node-eslint; closes: bug#950654, thanks to Xavier Guimard (this message was generated automatically) -- Greetings https://bugs.debian.org/950654
Processed: Bug#950654 marked as pending in node-eslint-plugin-html
Processing control commands: > tag -1 pending Bug #950654 [src:node-eslint-plugin-html] node-eslint-plugin-html seems unusable without eslint Added tag(s) pending. -- 950654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950654 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962323: python-django: CVE-2020-13254 CVE-2020-13596
Hi, > python-django: CVE-2020-13254 CVE-2020-13596 Security team, would you like an update for stretch and/or buster to address these issues? It's fixed in sid, experimental as well as jessie LTS. Bullseye is just pending migration time AFAICT. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Processed: Re: python-django: CVE-2020-13254 CVE-2020-13596
Processing commands for cont...@bugs.debian.org: > fixed 962323 1.7.11-1+deb8u9 Bug #962323 [python-django] python-django: CVE-2020-13254 CVE-2020-13596 There is no source info for the package 'python-django' at version '1.7.11-1+deb8u9' with architecture '' Unable to make a source version for version '1.7.11-1+deb8u9' Marked as fixed in versions 1.7.11-1+deb8u9. > fixed 962323 2:2.2.13-1 Bug #962323 [python-django] python-django: CVE-2020-13254 CVE-2020-13596 There is no source info for the package 'python-django' at version '2:2.2.13-1' with architecture '' Unable to make a source version for version '2:2.2.13-1' Marked as fixed in versions 2:2.2.13-1. > fixed 962323 2:3.0.7-1 Bug #962323 [python-django] python-django: CVE-2020-13254 CVE-2020-13596 There is no source info for the package 'python-django' at version '2:3.0.7-1' with architecture '' Unable to make a source version for version '2:3.0.7-1' Marked as fixed in versions 2:3.0.7-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 962323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962323: python-django: CVE-2020-13254 CVE-2020-13596
Package: python-django Version: 1.7.11-1+deb8u3 X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for python-django. CVE-2020-13254[0]: | An issue was discovered in Django 2.2 before 2.2.13 and 3.0 before | 3.0.7. In cases where a memcached backend does not perform key | validation, passing malformed cache keys could result in a key | collision, and potential data leakage. CVE-2020-13596[1]: | An issue was discovered in Django 2.2 before 2.2.13 and 3.0 before | 3.0.7. Query parameters generated by the Django admin | ForeignKeyRawIdWidget were not properly URL encoded, leading to a | possibility of an XSS attack. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-13254 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13254 [1] https://security-tracker.debian.org/tracker/CVE-2020-13596 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13596 Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#961782: marked as done (glue-sprite is not installable in unstable)
Your message dated Sat, 06 Jun 2020 08:48:34 + with message-id and subject line Bug#961782: fixed in glue 0.13-4 has caused the Debian Bug report #961782, regarding glue-sprite is not installable in unstable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 961782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961782 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: glue-sprite Version: 0.13-3 Severity: serious The following packages have unmet dependencies: glue-sprite : Depends: python3-jinja2 (< 2.11) but 2.11.1-1 is to be installed --- End Message --- --- Begin Message --- Source: glue Source-Version: 0.13-4 Done: Angel Abad We believe that the bug you reported is fixed in the latest version of glue, 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 961...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Angel Abad (supplier of updated glue package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 06 Jun 2020 10:35:01 +0200 Source: glue Architecture: source Version: 0.13-4 Distribution: unstable Urgency: medium Maintainer: Angel Abad Changed-By: Angel Abad Closes: 961782 Changes: glue (0.13-4) unstable; urgency=medium . * debian/rules: Use execute_before_ instead of override_ * Bump debhelper compatibility level to 13 * Bump Standards-Version to 4.5.0 (no changes) * debian/py3dist-overrides: Adjust for jinja2 versioned depends (Closes: #961782) * Add upstream metadata Checksums-Sha1: e1565cd6ea6b72b9d094ab98f4b19cc824120605 1851 glue_0.13-4.dsc 13a5fe26a02463fa95bd57efbbdbec3c257bc95a 4108 glue_0.13-4.debian.tar.xz 4149d13bc63905335a4d74ad1a2581bda0eea00c 6783 glue_0.13-4_amd64.buildinfo Checksums-Sha256: 72bacdb99b08abbe3c5ef1ae425c68fb97f2ca54f41d3c7d982d013633ecee0f 1851 glue_0.13-4.dsc e6e665931d4456d630d8b83346dd6e458b5325cf4268397935eb1cd1c9fb842a 4108 glue_0.13-4.debian.tar.xz c8e25b80915b3a280d302abf6b0dde91b33d06d27f428a1dafb210e9526df350 6783 glue_0.13-4_amd64.buildinfo Files: 1dd284a4c3b605face715a835798e61e 1851 graphics optional glue_0.13-4.dsc e4730e03a28a9c818b09f0f7ad22cfcb 4108 graphics optional glue_0.13-4.debian.tar.xz 424da3c89c0dc22c9b88faad687efb84 6783 graphics optional glue_0.13-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEESgiXGRYhzPf77vdSptWIFgEKEJYFAl7bVawRHGFuZ2VsQGRl Ymlhbi5vcmcACgkQptWIFgEKEJZKFhAAzOly1M657hr8ijVR24Z9JuHNZvZI9op1 nzOjgZWAZME5SndV0VGVV0y41P9r0ScyJHzR/u4qVCDZHJ/MKx0F/A+8bGoKeEFM Jcu/3W+gz/akuDQoAN7QAkJ/3Yj3XYjVvqeScHBnh6WVP9ph5gs/X5vB7Kfuk/JB 6bApdQzUw5+L9MYZrfNk5tKYW70awO0X9sa4oozy7u5x9+QBtUqcrq/DTBDwkcM4 IunePe5d5pl7Ar9qU/2uVygQQ/fy1b54vYAoXWWC/ZdxRk8BoNxRIx2msnjssaIr mtbfVqQcrJTIzz4wJBHvjSCWPvDRbS9bXyCeM1sDJT6JBlhVqT7Jzjdoe4V7EgkQ S/55IL7v+bxhtW07VnoYo7eDMYf3iTQ9isDL9PdBNnlHgSxow+JZEdCiwq5T0IwL PV1NrHSjKE/iMKJMnNjrfoxxjYZUZwZkDXCAu0uRMnf+runRirni7Fi2jD0WWDrw d6Eq7olipb04S6bk30CFfJooDti8/p0o9LEWsobvVC8DAk3/wR02vod8NqrHKLvI gJjtaDwUuO7wcg1ZOavksmKrNkD/HijAWpTcByXofo2Ur5DAyB/gkAju6fthen3A uMFH4vWtbTVedAgJuRMomIOep9a6euZxXRAzrJNFkPuW8dFcpzI3dlM+j5XUQvsx hqKZgR7GqLA= =/T0C -END PGP SIGNATURE End Message ---
Bug#947738: marked as done (inn2 postinst script needs libinn.so.6, but doesn't depend on it)
Your message dated Sat, 06 Jun 2020 08:35:23 + with message-id and subject line Bug#947738: fixed in inn2 2.6.3+20200601-1 has caused the Debian Bug report #947738, regarding inn2 postinst script needs libinn.so.6, but doesn't depend on it 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.) -- 947738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947738 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: inn2 Version: 2.6.3-1+deb10u2 During an upgrade from stretch to buster, the inn2 postinst script failed like this: | Setting up inn2 (2.6.3-1+deb10u2) ... | /usr/lib/news/bin/innconfval: error while loading shared libraries: libinn.so.6: cannot open shared object file: No such file or directory | dpkg: error processing package inn2 (--configure): | installed inn2 package post-installation script subprocess returned error exit status 127 The reason being that libinn.so.6 is in the new inn2-inews package, which was not upgraded yet. Manually upgrading inn2-inews solved the problem. --- End Message --- --- Begin Message --- Source: inn2 Source-Version: 2.6.3+20200601-1 Done: Marco d'Itri We believe that the bug you reported is fixed in the latest version of inn2, 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 947...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marco d'Itri (supplier of updated inn2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 06 Jun 2020 08:25:31 +0200 Source: inn2 Architecture: source Version: 2.6.3+20200601-1 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri Changed-By: Marco d'Itri Closes: 943851 947738 954414 954710 960249 Changes: inn2 (2.6.3+20200601-1) unstable; urgency=medium . * New upstream snapshot. Contains: + A fix for a FTCBFS. (Closes: #943851) + New option -b to rnews to save rejected articles. (Closes: #960249) * Implemented systemd integration and socket activation. * Enabled the Python filters. (Closes: #954710) * Changed the remaining references to gpg to gpg1. (Closes: #954414) * Versioned the "Pre-Depends: inn2-inews" in inn2, or else inn2 may not find the newer libinn on upgrades. (Closes: #947738) Checksums-Sha1: 4cdd8647819d38732175f9fd23d463caba2b5ec7 1490 inn2_2.6.3+20200601-1.dsc b7fb214e29037d5f8e6ad4e25f3ccebffa440be1 2586831 inn2_2.6.3+20200601.orig.tar.gz f0b5a7279a84f9dbf4a07ec60854a52fde0b955f 38112 inn2_2.6.3+20200601-1.debian.tar.xz fd37fea888e3a8f397748b8e27229cb0e002e790 7365 inn2_2.6.3+20200601-1_amd64.buildinfo Checksums-Sha256: 6356fec0b29af181c6c89159b442963259e17864c60c32db49835fe0a73983b3 1490 inn2_2.6.3+20200601-1.dsc 3e1db043ed47d7860a49f2d802ee168eddde19111471a5a19b4bee6d34d6ba51 2586831 inn2_2.6.3+20200601.orig.tar.gz d6fe3d287f0ab7d5791cd650dcc8653a1b10c8ff8fe4897e2eff9a095b42be2a 38112 inn2_2.6.3+20200601-1.debian.tar.xz 2475bec6dfcf4089608f57a43b1bb5ded7743cbb85f0d27f9c3ed43c68bebc5a 7365 inn2_2.6.3+20200601-1_amd64.buildinfo Files: d8dc2e7840c534dc3841efc3e977a6aa 1490 news optional inn2_2.6.3+20200601-1.dsc fbfb73559bc28b7c1dd06b0b1c9c7453 2586831 news optional inn2_2.6.3+20200601.orig.tar.gz 93cd9e31276e3f2579c045fe823cb053 38112 news optional inn2_2.6.3+20200601-1.debian.tar.xz 5c93d38a7952f8aedf721724f42f77b4 7365 news optional inn2_2.6.3+20200601-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQQnKUXNg20437dCfobLPsM64d7XgQUCXttNDwAKCRDLPsM64d7X gVlhAQDriqNo8sNxtclMGIeU+OrA0+rQro6JdOfjTgPlNf2UQgEAqCrc3/t7y/QV raQDRwZh6miPfiL9PPMqMK3vGB1/oQg= =727T -END PGP SIGNATURE End Message ---
Bug#961994: src:libcatmandu-perl: fails to migrate to testing for too long: causes autopkgtest regression
Quoting Niko Tyni (2020-06-06 09:33:03) > On Sat, Jun 06, 2020 at 09:18:36AM +0200, Paul Gevers wrote: > > Hi, > > > > On 03-06-2020 22:51, Paul Gevers wrote: > > >> However, > > >> if the test suite breakage is not just a technicality, the missing > > >> Breaks makes it possible for users to partially upgrade their systems > > >> to a broken combination. > > > > > > This is the interesting question. Is there something broken in the > > > combination that we're testing? If so, I would prefer the Breaks. > > > > > >> Paul, please correct me if I'm mistaken above :) > > > > > > If it's *only* the test that's broken, I can manually trigger the right > > > test. > > > > So, do you already know if I should do this, or will you resolve the > > issue without my intervention? > > Thanks for following up. I hope that somebody in the pkg-perl team who > knows what the modules actually do (probably Jonas? cc'd) could look > into this. Thanks, Niko and Paul - the issue seems to be a fault test in Catmandu::SRU fixed since release 0.422 - but to be on the safe side I have now added a Breaks. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#962138: perl-base: libperl5.30 version skew can break essential functionality
On Sat, Jun 06, 2020 at 10:03:15AM +0300, Niko Tyni wrote: > I think we need to move the perl-base between vendor and core, so after > /usr/lib/x86_64-linux-gnu/perl/5.30 but before /usr/share/perl/5.30. Sorry, that should have been 'after /usr/share/perl5 but before /usr/lib/x86_64-linux-gnu/perl/5.30'. So like this: @INC: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.3 /usr/local/share/perl/5.30.3 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl -- Niko Tyni nt...@debian.org
Processed: tagging 961839, found 938731 in 20.3.0-1, tagging 951271, tagging 956680, tagging 962232 ...
Processing commands for cont...@bugs.debian.org:
> tags 961839 + sid bullseye
Bug #961839 [src:closure-compiler] closure-compiler: FTBFS: is not
abstract and does not override abstract method test(Object) in Predicate
Added tag(s) bullseye and sid.
> found 938731 20.3.0-1
Bug #938731 {Done: Sandro Tosi } [src:twisted] twisted:
Python2 removal in sid/bullseye
Marked as found in versions twisted/20.3.0-1 and reopened.
> tags 951271 + sid bullseye
Bug #951271 [src:java-gnome] java-gnome: Please migration from enchant(1) to
enchant-2
Added tag(s) bullseye and sid.
> tags 956680 + sid bullseye
Bug #956680 [src:xneur] xneur: Please migrate to enchant-2
Added tag(s) bullseye and sid.
> tags 962232 + sid bullseye
Bug #962232 [vanguards] vanguards indirectly build-depends on cruft package.
Added tag(s) bullseye and sid.
> tags 962265 + sid bullseye
Bug #962265 [src:sword] sword silently loses ICU support when built with ICU
without icu-config
Added tag(s) sid and bullseye.
> found 962253 2.3.5+dfsg1-4
Bug #962253 [esys-particle] esys-particle: Broken section number in manpage
Marked as found in versions esys-particle/2.3.5+dfsg1-4.
> tags 960243 + experimental
Bug #960243 [src:zimlib] zimlib FTBFS with ICU 67.1
Added tag(s) experimental.
> tags 882267 + bullseye - buster
Bug #882267 {Done: David Prévot } [php-defaults] php-mockery
FTBFS: Class 'DOMDocument' not found
Added tag(s) bullseye.
Bug #882267 {Done: David Prévot } [php-defaults] php-mockery
FTBFS: Class 'DOMDocument' not found
Removed tag(s) buster.
> found 882267 69
Bug #882267 {Done: David Prévot } [php-defaults] php-mockery
FTBFS: Class 'DOMDocument' not found
There is no source info for the package 'php-defaults' at version '69' with
architecture ''
Unable to make a source version for version '69'
Marked as found in versions 69.
> found 960791 1:019-4
Bug #960791 {Done: Andreas Beckmann } [firmware-b43-installer]
firmware-b43-installer: when language is not English, install fails. Script
attempts to parse localized output
Ignoring request to alter found versions of bug #960791 to the same values
previously set
> tags 819136 + moreinfo
Bug #819136 [firmware-b43-installer] firmware-b43-installer: Desire packaging
script
Added tag(s) moreinfo.
> tags 898045 - wontfix
Bug #898045 {Done: Andreas Beckmann } [nvidia-cuda-gdb]
nvidia-cuda-gdb: depends on libncurses5
Removed tag(s) wontfix.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
819136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819136
882267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882267
898045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898045
938731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938731
951271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951271
956680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956680
960243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960243
960791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960791
961839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961839
962232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962232
962253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962253
962265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#951059: [debian-mysql] MariaDB 10.3.23 with a critical bug fix
Hello Alexandre! > I've searched the tracker (https://tracker.debian.org/pkg/mariadb-10.3) and > the BTS and couldn't find any trace of discussions for updating the > mariadb-10.3 version to the upstream one. > > > > For information, 10.3.23 does fix a critical bug that prevent mariadb to > startup, and hence prevents in turn to use any kde-pim applications since > akonadi won't start. There are no further uploads of 10.3 planned to Debian unstable or testing (and it is not possible, since it would end up in the NEW queue as 10.4 is already in Debian experimental). We will ship this fix in next stable release, but there are no dates yet: https://release.debian.org/ > Next point releases > stable (10.5) Not yet planned > oldstable (9.13) Not yet planned
Bug#962320: facter crashes with "free(): invalid pointer"
Package: libfacter3.11.0
Version: 3.11.0-4.1
Severity: grave
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
set = {__val = {0, 1431634051, 94476679444720, 139623352393688, 0,
94476679915560, 94476680133744, 139623355011525, 17, 94476679449080, 6481,
94476679118894, 272, 256, 4, 94476679118984}}
pid =
tid =
ret =
#1 0x7efc9e30f55b in __GI_abort () at abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction = 0x0},
sa_mask = {__val = {0, 511101108348, 390842024046, 140728013449808, 2, 44,
18446744073709551504, 140728013450096, 13742199053743279360, 0,
140728013450112, 94476682378416,
140728013450304, 140728013450096, 140728013449824, 0}}, sa_flags
= -1643662843, sa_restorer = 0x0}
sigs = {__val = {32, 0 }}
#2 0x7efc9e368038 in __libc_message (action=action@entry=do_abort,
fmt=fmt@entry=0x7efc9e474f3e "%s\n") at ../sysdeps/posix/libc_fatal.c:181
ap = {{gp_offset = 24, fp_offset = 32765, overflow_arg_area =
0x7ffdcb406b50, reg_save_area = 0x7ffdcb406ae0}}
fd =
list =
nlist =
cp =
written =
#3 0x7efc9e36f3da in malloc_printerr (str=str@entry=0x7efc9e4730e0
"free(): invalid pointer") at malloc.c:5339
No locals.
#4 0x7efc9e370dcc in _int_free (av=, p=,
have_lock=0) at malloc.c:4173
size = 0
fb =
nextchunk =
nextsize =
nextinuse =
prevsize =
bck =
fwd =
__PRETTY_FUNCTION__ = "_int_free"
#5 0x7efc9e7c75d4 in __gnu_cxx::new_allocator::deallocate
(this=0x7ffdcb406c60, __p=) at
/usr/include/c++/9/ext/new_allocator.h:119
No locals.
#6 std::allocator_traits >::deallocate (__a=...,
__n=, __p=) at
/usr/include/c++/9/bits/alloc_traits.h:470
No locals.
#7 std::__cxx11::basic_string,
std::allocator >::_M_destroy (__size=,
this=0x7ffdcb406c60) at /usr/include/c++/9/bits/basic_string.h:237
No locals.
#8 std::__cxx11::basic_string,
std::allocator >::_M_dispose (this=0x7ffdcb406c60) at
/usr/include/c++/9/bits/basic_string.h:232
No locals.
#9 std::__cxx11::basic_string,
std::allocator >::~basic_string (this=0x7ffdcb406c60,
__in_chrg=) at /usr/include/c++/9/bits/basic_string.h:658
No locals.
#10 facter::facts::collection::add_external_facts_dir (this=0x7ffdcb4071a0,
resolvers=std::vector of length 4, capacity 4 = {...}, dir=..., warn=) at ./lib/src/facts/collection.cc:160
msg = ""
found = false
ec = {m_val = 2, m_cat = 0x7efc9e093070}
search_dir = {static separator = 47 '/', static preferred_separator =
47 '/', static dot = 46 '.', m_pathname =
"/home/bernat/.puppetlabs/opt/facter/facts.d"}
#11 0x7efc9e7c7bd8 in facter::facts::collection::add_external_facts
(this=0x7ffdcb4071a0, directories=std::vector of length 0, capacity 0) at
./lib/src/facts/collection.cc:197
dir = "/home/bernat/.puppetlabs/opt/facter/facts.d"
__for_range = @0x7ffdcb406d80: std::vector of length 2, capacity 2 =
{"/home/bernat/.puppetlabs/opt/facter/facts.d", "/home/bernat/.facter/facts.d"}
__for_begin =
__for_end =
resolvers = std::vector of length 4, capacity 4 =
{std::unique_ptr = {get() = 0x55ed1117bbf0},
std::unique_ptr = {get() = 0x55ed1117bc30},
std::unique_ptr = {get() =
0x55ed1117bc10}, std::unique_ptr = {get() =
0x55ed1117bc50}}
found = false
#12 0x55ed1001f54c in main (argc=, argv=) at
./exe/facter.cc:350
inside_facter = ""
external_directories = std::vector of length 0, capacity 0
positional_options = {m_names = std::vector of length 0, capacity 0,
m_trailing = "query"}
ignore_cache =
vm =
lvl =
blocklist = std::set with 0 elements
custom_directories = std::vector of length 0, capacity 0
hidden_options = {static m_default_line_length = 80, m_caption = "",
m_line_length = 80, m_min_description_length = 40, m_options = std::vector of
length 1, capacity 1 = {{px = 0x55ed10eacd80, pn = {pi_ = 0x55ed10e6bae0}}},
belong_to_group = std::vector of length 1, capacity 64 =
{false}, groups = std::vector of length 0, capacity 0}
ruby =
ruby_cleanup = {_callback =
{> = {},
= {static _M_max_size = 16, static _M_max_align = 8,
_M_functor = {_M_unused = {_M_object = 0x55ed10e8fc01,
_M_const_object = 0x55ed10e8fc01, _M_function_pointer =
0x55ed10e8fc01, _M_member_pointer = &virtual table offset 94476679314432, this
adjustment 42}, _M_pod_data =
"\001\374\350\020\355U\000\000*\000\000\000\000\000\000"},
_M_manager = 0x55ed100200d0
>::_M_manager(std::_Any_data &, const std::_Any_data &,
std::_Manager_operation)>},
_M_invoker = 0x55ed10020100 >::_M_invoke(const std::_Any_data &)>}}
fmt =
ttls = std::unordered_map with 0 elem
Processed: retitle 962319 to libextutils-hascompiler-perl: test failures with perl 5.30.3-2
Processing commands for cont...@bugs.debian.org: > retitle 962319 libextutils-hascompiler-perl: test failures with perl 5.30.3-2 Bug #962319 [libextutils-hascompiler-perl] libextutils-hascompiler-perl: test failures perl 5.30.3-2 Changed Bug title to 'libextutils-hascompiler-perl: test failures with perl 5.30.3-2' from 'libextutils-hascompiler-perl: test failures perl 5.30.3-2'. > thanks Stopping processing here. Please contact me if you need assistance. -- 962319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961994: src:libcatmandu-perl: fails to migrate to testing for too long: causes autopkgtest regression
On Sat, Jun 06, 2020 at 09:18:36AM +0200, Paul Gevers wrote: > Hi, > > On 03-06-2020 22:51, Paul Gevers wrote: > >> However, > >> if the test suite breakage is not just a technicality, the missing > >> Breaks makes it possible for users to partially upgrade their systems > >> to a broken combination. > > > > This is the interesting question. Is there something broken in the > > combination that we're testing? If so, I would prefer the Breaks. > > > >> Paul, please correct me if I'm mistaken above :) > > > > If it's *only* the test that's broken, I can manually trigger the right > > test. > > So, do you already know if I should do this, or will you resolve the > issue without my intervention? Thanks for following up. I hope that somebody in the pkg-perl team who knows what the modules actually do (probably Jonas? cc'd) could look into this. -- Niko Tyni nt...@debian.org
Bug#962319: libextutils-hascompiler-perl: test failures perl 5.30.3-2
Package: libextutils-hascompiler-perl
Version: 0.021-2
Severity: serious
This package fails its test suite with perl 5.30.3-2 from unstable.
The reasons are somewhat complicated. The failing test checks
that ExtUtils::HasCompiler and ExtUtils::MakeMaker give the
same result when trying to build a program that is statically linked
with libperl.a.
Up until perl 5.30.3-2, this test build failed with ExtUtils::HasCompiler:
it checked $Config{useshrplib} and bailed out because it concluded
that our libperl is built dynamically and we therefore don't support
static linking. On the other hand, the ExtUtils::MakeMaker reference
build failed because the package does not build depend on libperl-dev,
so libperl.a was not available.
With perl 5.30.3-2, #798626 is fixed and $Config{useshrplib} now
correctly indicates that static linking is supported. However, the
ExtUtils::HasCompiler check does not actually link, so it fails to detect
that libperl.a is missing. ExtUtils::MakeMaker still fails in the same
way, so the results now disagree.
I suggest that we fix this in a way that's compatible with both
older and newer perl versions, by adding a build dependency on
libperl-dev and patching away the check $Config{useshrplib} check in
ExtUtils::HasCompiler::can_compile_static_library() . On Debian we build
both static and dynamic versions of libperl, so static builds should
be supported.
Transcript of the failure below. Note that the warning about
perl and Config.pm having 'different ideas about the architecture'
is not the cause of this. It is just a warning that we'll handle
separately (cf. #962138)
# Failed test 'MakeMaker agrees we can compile static'
# at t/compare.t line 67.
# got: '1'
# expected: undef
# Couldn't run make test: make[2]: Entering directory '/tmp/BDk9YhPh04'
# make[2]: warning: jobserver unavailable: using -j1. Add '+' to parent make
rule.
# Writing "Makefile.aperl" for this perl
# Have /usr/lib/x86_64-linux-gnu/perl-base
# Want /usr/lib/x86_64-linux-gnu/perl/5.30
# Your perl and your Config.pm seem to have different ideas about the
# architecture they are running on.
# Perl thinks: [perl-base]
# Config says: [x86_64-linux-gnu-thread-multi]
# This may or may not cause problems. Please check your installation of perl
# if you have problems building this extension.
# Warning: /usr/lib/x86_64-linux-gnu/perl/5.30/../../libperl.a not found
# If you're going to build a static perl binary, make sure perl is installed
# otherwise ignore this warning
# Generating a Unix-style Makefile.aperl
# Writing Makefile.aperl for EUHC::Test
# Writing MYMETA.yml and MYMETA.json
# make -f Makefile.aperl perl
# make[3]: Entering directory '/tmp/BDk9YhPh04'
# Writing perlmain.c
# mv perlmain.ct perlmain.c
# x86_64-linux-gnu-gcc -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv
-fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -O2 -g -DVERSION=\"\" -DXS_VERSION=\"\" -fPIC
"-I/usr/lib/x86_64-linux-gnu/perl/5.30/CORE" perlmain.c
# make[3]: *** No rule to make target
'/usr/lib/x86_64-linux-gnu/perl/5.30/../../libperl.a', needed by 'perl'. Stop.
# make[3]: Leaving directory '/tmp/BDk9YhPh04'
# make[2]: *** [Makefile:956: perl] Error 2
# make[2]: Leaving directory '/tmp/BDk9YhPh04'
# Looks like you failed 1 test of 3.
--
Niko Tyni nt...@debian.org
Bug#962318: libmojolicious-perl: build fails on IPv6-only buildds
Source: libmojolicious-perl Version: 8.52+dfsg-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=libmojolicious-perl&ver=8.52%2Bdfsg-1 ... Can't create listen socket: Address family for hostname not supported at /<>/blib/lib/Mojo/IOLoop.pm line 123. # Tests were run but no plan was declared and done_testing() was not seen. ... Failed 39/103 test programs. 0/6415 subtests failed. make[2]: *** [Makefile:1393: test_dynamic] Error 22 See #962019 as example of a similar problem in another package.
Bug#962250: monero: Please skip hash-variant2-int-sqrt on armel
Control: tags -1 patch On Fri, Jun 05, 2020 at 08:06:59AM +0300, Adrian Bunk wrote: >... > armel has no FPU and no native atomics instructions in the baseline. > Please disable this (passing) test on armel. Patch to implement this: --- debian/rules.old2020-06-06 05:13:52.735274009 + +++ debian/rules2020-06-06 05:15:10.362582776 + @@ -38,6 +38,11 @@ # skip tests possibly broken TEST_EXCLUDE += $(if $(DEB_SUITE_EXP),,cnv4-jit hash-slow-4) +# test takes >= 5 hours on armel +ifneq (,$(filter $(DEB_HOST_ARCH), armel)) +TEST_EXCLUDE += hash-variant2-int-sqrt +endif + override_dh_auto_configure: dh_auto_configure -- -DARCH=default -DNO_AES=ON -DBUILD_TESTS=ON -DPYTHON_EXECUTABLE=/usr/bin/python3
Processed: Re: Bug#962250: monero: Please skip hash-variant2-int-sqrt on armel
Processing control commands: > tags -1 patch Bug #962250 [src:monero] monero: Please skip hash-variant2-int-sqrt on armel Added tag(s) patch. -- 962250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961994: src:libcatmandu-perl: fails to migrate to testing for too long: causes autopkgtest regression
Hi, On 03-06-2020 22:51, Paul Gevers wrote: >> However, >> if the test suite breakage is not just a technicality, the missing >> Breaks makes it possible for users to partially upgrade their systems >> to a broken combination. > > This is the interesting question. Is there something broken in the > combination that we're testing? If so, I would prefer the Breaks. > >> Paul, please correct me if I'm mistaken above :) > > If it's *only* the test that's broken, I can manually trigger the right > test. So, do you already know if I should do this, or will you resolve the issue without my intervention? Paul signature.asc Description: OpenPGP digital signature
Bug#962317: cgview: autopkgtest failure: readlink: missing operand
Source: cgview Version: 0.0.20100111-5 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 cgview, great. However, it fails. 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. 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=cgview https://ci.debian.net/data/autopkgtest/testing/amd64/c/cgview/5700999/log.gz autopkgtest [22:35:03]: test run-unit-test: [--- readlink: missing operand Try 'readlink --help' for more information. autopkgtest [22:35:04]: test run-unit-test: ---] signature.asc Description: OpenPGP digital signature
Processed: src:psychtoolbox-3: fails to migrate to testing for too long: maintainer built arch:all
Processing control commands: > close -1 3.0.16.20200326.dfsg1-1 Bug #962316 [src:psychtoolbox-3] src:psychtoolbox-3: fails to migrate to testing for too long: maintainer built arch:all Marked as fixed in versions psychtoolbox-3/3.0.16.20200326.dfsg1-1. Bug #962316 [src:psychtoolbox-3] src:psychtoolbox-3: fails to migrate to testing for too long: maintainer built arch:all Marked Bug as done -- 962316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962316: src:psychtoolbox-3: fails to migrate to testing for too long: maintainer built arch:all
Source: psychtoolbox-3 Version: 3.0.16.20200130.dfsg1-2 Severity: serious Control: close -1 3.0.16.20200326.dfsg1-1 Tags: sid bullseye pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:psychtoolbox-3 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. Your package is only blocked because the binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=psychtoolbox-3 signature.asc Description: OpenPGP digital signature
Bug#962138: perl-base: libperl5.30 version skew can break essential functionality
On Wed, Jun 03, 2020 at 07:39:38PM +0300, Niko Tyni wrote:
> Package: perl-base
> Version: 5.30.2-1
> Severity: serious
>
> Our Perl package dependencies and search path arrangements allow
> for a suitably versioned libperl5.30 package to break perl-base
> functionality. This is bad as perl-base is Essential:yes and is therefore
> required to stay functional at all times.
[...]
> A) Move /usr/lib//perl-base up on the @INC search path. This is
>shipped in perl-base and includes the parts of the standard library
>we consider part of Essential:yes functionality. It's currently last
>on @INC. The libperl5.30 and perl-modules-5.30 packages include copies
>of these files, shipped in /usr/{lib,share}//perl/5.30,
>so that they can be used "standalone" for different architectures or
>major versions. The position of these copies higher on @INC makes this
>bug possible.
We did this for 5.30.3-2, moving /usr/lib//perl-base almost
to the top (right after /etc/perl). This caused a regression in the
libscalar-list-utils-perl package, because the older versions of the
Scalar-List-Utils modules in perl-base now take priority. So dual life
modules in perl-base can no longer be overridden by a separate package
with the current @INC ordering.
I think we need to move the perl-base between vendor and core, so after
/usr/lib/x86_64-linux-gnu/perl/5.30 but before /usr/share/perl/5.30.
> I think A) is currently my preferred way of fixing this, and I think
> the upstream "divergence" issue it creates is not very important. I
> can envision some corner case regressions where standard library
> modules expect other modules to be in the same directory, but those
> seem improbable.
Unfortunately one of these corner causes is rather prominent:
ExtUtils::MakeMaker checks that the Config.pm it has loaded is on
archlibexp (currently /usr/lib//perl/5.30), which is directly
contrary to our purposes here.
The check is only a warning, but it shows on every architecture specific
build. I'm not currently aware of any build failures or the like caused
by it. Nevertheless, I think we should patch the check to allow for the
perl-base specific path.
One more thing I've spotted in the 5.30.3-2 britney autopkgtest tests
is a regression in libextutils-hascompiler-perl. I think that needs
to be fixed in libextutils-hascompiler-perl and I'll file a separate
bug about it.
--
Niko Tyni nt...@debian.org
