Bug#945870: Unmet Dependency on libgegl-common
Package: libgegl-0.4-0 Version: 0.4.18-2 Severity: grave Dear Maintainer, I attempted to use GIMP, but got this error in return: gimp: symbol lookup error: gimp: undefined symbol: gegl_rectangle_subtract The libgegl-0.4-0 package was the issue, as I wasn't able to install it because of it's dependency on an available package. It requires libgegl-common (>= 0.4.18-2) but 1:0.4.16-dmo2 is all that's to be installed. What I find odd is the apt policy for libgegl-common: libgegl-common: Installed: 1:0.4.16-dmo2 Candidate: 1:0.4.16-dmo2 Version table: *** 1:0.4.16-dmo2 100 100 /var/lib/dpkg/status 0.4.18-2 500 500 http://deb.debian.org/debian unstable/main amd64 Packages 500 http://deb.debian.org/debian unstable/main i386 Packages So I tried installing the available version using package=version, and APT considered it a downgrade. Should be easy to fix the candidate, but unusable at the moment if you don't force "downgrade" it.
Bug#943259: [PATCH 1/1] Swap dependency of python-autopep8 for python3-autopep8 (>> 1.4.4-1)
Signed-off-by: Nicholas D Steeves
---
debian/changelog | 8
debian/control | 2 +-
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/debian/changelog b/debian/changelog
index 25adec3..00ef84e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+vim-autopep8 (1.0.7-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Swap dependency of python-autopep8 for python3-autopep8 (>> 1.4.4-1),
+which now provides /usr/bin/autopep8.
+
+ -- Nicholas D Steeves Fri, 29 Nov 2019 23:34:59 -0500
+
vim-autopep8 (1.0.7-1) unstable; urgency=low
* Initial release (Closes: #806573)
diff --git a/debian/control b/debian/control
index 8222523..942a765 100644
--- a/debian/control
+++ b/debian/control
@@ -10,7 +10,7 @@ Vcs-Browser:
https://anonscm.debian.org/gitweb/?p=collab-maint/vim-autopep8.git;
Package: vim-autopep8
Architecture: all
-Depends: python-autopep8,
+Depends: python3-autopep8 (>> 1.4.4-1),
vim,
vim-addon-manager,
${misc:Depends},
--
2.20.1
Bug#943259: [PATCH 0/1] Re: vim-autopep8: Python2 removal in sid/bullseye
Hi Balasankar, I'm not sure if you noticed this bug earlier this year, but it's RC now, so I took the liberty to fix it, because the autopep8 fix it blocks affects one of my packages. 'hope that's ok with you, since the package used to be collab-maint and hasn't been updated in many years. If you don't want me to NMU it, please let me know at your earliest convenience :-) The email that follows this one has the patch attached. Nicholas D Steeves (1): Swap dependency of python-autopep8 for python3-autopep8 (>> 1.4.4-1) debian/changelog | 8 debian/control | 2 +- 2 files changed, 9 insertions(+), 1 deletion(-) -- 2.20.1
Processed: tagging 943259
Processing commands for cont...@bugs.debian.org: > tags 943259 + patch pending Bug #943259 [src:vim-autopep8] vim-autopep8: Python2 removal in sid/bullseye Added tag(s) pending and patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 943259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937666: marked as done (python-coverage-test-runner: Python2 removal in sid/bullseye)
Your message dated Sat, 30 Nov 2019 04:04:21 + with message-id and subject line Bug#937666: fixed in python-coverage-test-runner 1.13.1-3 has caused the Debian Bug report #937666, regarding python-coverage-test-runner: 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.) -- 937666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-coverage-test-runner Version: 1.13.1-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-coverage-test-runner If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-coverage-test-runner Source-Version: 1.13.1-3 We believe that the bug you reported is fixed in the latest version of python-coverage-test-runner, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated python-coverage-test-runner package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 29 Nov 2019 22:44:36 -0500 Source: python-coverage-test-runner Architecture: source Version: 1.13.1-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Sandro Tosi Closes: 937666 Changes: python-coverage-test-runner (1.13.1-3) unstable; urgency=medium . * QA upload. * Drop python2 support; Closes: #937666 Checksums-Sha1: 6c0916c2e77c900423dafd6e6ffd2bc659885218 1935 python-coverage-test-runner_1.13.1-3.dsc f91ddfb781a4465a583b753f4b7f46607720f675 2316 python-coverage-test-runner_1.13.1-3.debian.tar.xz 35a887ba3d37db986bc50434fedf7d5d78b0e9e7 6390 python-coverage-test-runner_1.13.1-3_source.buildinfo Checksums-Sha256: c171d7930a91685b6290f7a333a7fd6b798ef9e011726541d81abad4aa44f7e3 1935 python-coverage-test-runner_1.13.1-3.dsc 7b0afb573495361606a64789f2c682e64a5953da7c563427acc6
Bug#939311: monero: FTBFS on arm64: final link failed: file in wrong format
Hi, This bug is related to https://sourceware.org/bugzilla/show_bug.cgi?id=25210 -- Bertrand signature.asc Description: Digital signature
Bug#945763: gcc-9 ftbfs on mipsel
YunQiang Su 于2019年11月29日周五 下午2:21写道： > > 在 2019-11-29五的 07:00 +0100，Matthias Klose写道： > > On 28.11.19 18:09, YunQiang Su wrote: > > > Matthias Klose 于2019年11月28日周四 下午5:51写道： > > > > On 28.11.19 10:44, Matthias Klose wrote: > > > > > Package: src:gcc-9 > > > > > Version: 9.2.1-20 > > > > > Severity: serious > > > > > Tags: sid bullseye > > > > > > > > > > gcc-9 ftbfs on mipsel with a bootstrap comparison failure, most > > > > > likely triggered > > > > > by the LTO build enabled in -20. > > > > > > > > > > bootstrap comparison failure! > > > > > libbacktrace/elf.o differs > > > > > libbacktrace/.libs/elf.o differs > > > > > make[4]: *** [Makefile:24878: compare] Error 1 > > > > > > > > Please could you have a look? > > > > > > sure. I will look at it tomorrow > > > > hmm, that also fails in gcc-7, which didn't see any code changes from > > 7.5.0-1 to > > 7.5.0-2. > > Maybe, it meets a buggy machine? due to the Loongson's patch to add sync? > -- YunQiang Su
Processed: reassign 945840 to libboost-python1.67.0, severity of 945840 is serious
Processing commands for cont...@bugs.debian.org: > reassign 945840 libboost-python1.67.0 Bug #945840 [ledger] /usr/bin/ledger: error while loading shared libraries: libboost_python27.so.1.67.0: cannot open shared object file: No such file or directory Bug reassigned from package 'ledger' to 'libboost-python1.67.0'. No longer marked as found in versions ledger/3.1.2+dfsg1-1. Ignoring request to alter fixed versions of bug #945840 to the same values previously set > severity 945840 serious Bug #945840 [libboost-python1.67.0] /usr/bin/ledger: error while loading shared libraries: libboost_python27.so.1.67.0: cannot open shared object file: No such file or directory Severity set to 'serious' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 945840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: py2removal blocks updates - 2019-11-30 01:37:11.591200+00:00
Processing commands for cont...@bugs.debian.org: > # Part of the effort for the removal of python from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # pygobject > block 937448 by 945863 Bug #937448 [src:pygobject] pygobject: Python2 removal in sid/bullseye 937448 was blocked by: 938884 936833 936841 938329 939112 936748 936601 943123 939104 937181 943186 936758 938614 936214 936539 936265 938665 938593 936981 945717 883161 937803 937422 936531 936166 938780 939106 943270 943131 939115 938084 938327 936718 936221 937115 938160 93 938590 945683 943230 938511 936371 939109 942904 937628 943216 942966 938583 937339 943093 926244 936789 938837 938582 943110 937419 937447 938803 936225 937457 936900 938885 936632 937388 936624 938293 938584 943300 938799 937405 943252 942956 943023 936995 943129 937703 938591 943291 936717 937454 938361 942941 938596 943178 943151 938604 938623 945681 945674 936266 937114 935358 938464 936721 943108 937956 936813 937099 945718 942919 939114 943103 943146 937688 942988 938586 938637 936398 938789 943245 943294 936619 943117 942916 936670 943076 936173 937448 was blocking: 936371 937397 937439 937447 937558 937579 937695 938168 942941 943104 Added blocking bug(s) of 937448: 945863 > # python-defaults > block 937695 by 945863 Bug #937695 [src:python-defaults] python-defaults: Python2 removal in sid/bullseye 937695 was blocked by: 937492 942909 943008 937304 938457 942950 936153 937635 936714 938489 937114 938715 937514 938909 943197 937654 936437 937072 937476 936738 936816 938285 945647 937138 936284 935358 937538 937664 938010 936293 938375 938758 936243 939641 943257 938467 942960 937435 938517 937811 938657 938799 938380 936803 942928 936366 937692 938307 936637 938270 945688 945748 937454 937642 938689 937212 943040 937923 938336 936606 939491 938720 943090 937453 938699 938757 938340 945698 938468 943258 943036 937792 937941 936176 945648 937137 936737 937776 937742 937682 938831 936804 938649 936262 938390 938789 937874 936706 943198 938219 938329 937463 943007 943148 939481 943268 938458 938232 936501 936535 936101 938499 937513 937701 938555 937902 936221 936614 936311 943075 938615 943100 937086 937482 938155 943159 936154 938565 945747 936638 938308 936564 936972 936946 936164 937764 938518 937171 936996 937030 936283 937571 938877 943299 938295 936294 938420 937663 937194 937439 936794 938795 936783 938029 936643 936271 935208 937264 937016 937412 937544 936693 937144 936744 938745 938685 937254 938470 942977 937521 938827 938040 937956 939104 936721 936872 938188 937201 938588 936323 938147 938008 936443 936526 942931 937841 936951 937639 936126 937726 936752 938485 937891 938719 936206 937330 936484 943133 937552 936493 936904 936762 938289 943285 937162 945734 937562 938670 937276 938379 937003 937386 936483 937911 936539 938632 945665 938587 943134 938310 938220 937061 938445 938559 936652 936444 942978 938828 938100 943079 938500 937712 938249 937004 937823 938299 943295 945733 937051 937263 937426 937022 936830 938695 938432 938036 936743 937143 936683 938850 936793 937193 936341 937184 938419 937593 938785 936238 938809 938645 938860 938598 936916 936886 938198 945717 936462 936214 938007 937253 943232 939103 938268 936158 937758 943292 936558 938763 943003 937467 936829 811180 937960 936979 943276 938361 936665 936298 937715 937950 936840 938114 937489 938476 938072 938654 938351 938442 936733 938046 937768 938492 938096 936305 938753 936890 937457 938601 936634 936418 943201 937667 937720 938873 936120 943235 938239 945644 936520 936465 938464 943254 945694 938212 938322 943121 945743 938923 936377 937336 938642 942981 939179 938782 936269 936455 943016 937307 938676 937270 937749 936149 943144 936434 937657 943194 938811 936599 938692 937025 937117 936717 943183 936167 938463 943253 937620 938226 936247 937232 945684 938924 945744 937458 936875 936297 938874 942924 937329 945643 942941 938682 936433 938742 943193 936189 937831 943184 937415 937757 945721 936557 942991 938792 943143 937468 937658 938171 938663 937420 936718 937295 937118 937245 937927 937565 938764 938856 943282 943004 936765 936880 937615 883157 937079 937449 938754 938866 936910 937534 936288 938653 938735 943061 937499 938513 938701 938235 936788 937090 936936 937588 937827 937040 938521 937470 936459 938412 938016 938544 936810 936328 938439 942966 938583 936595 938594 945706 938183 937029 937379 939478 942974 936448 936825 938386 938003 937257 936498 936975 945713 943138 938276 936669 938562 936119 938330 937719 938152 937597 943114 937485 937931 938612 936797 943046 937905 936659 937197 936132 943096 936687 883145 938639 936532 936309 938841 937547 937267 936217 936908 938051 938372 938346 936570 937249 942973 938823 939260 937770 936170 936769 938004 937169 937619 937100 936700 937559 937445 945671 938712 937500 942911 936759 943303 937159 936787 943113 94573
Bug#945864: unhide[208429]: segfault at 7ffd06cfec58 ip 000055c15aa077d3 sp 00007ffd06cfec60 error 6 in unhide-linux[55c15aa07000+6000]
Package: unhide Version: 20130526-3 Severity: grave Justification: renders package unusable Since 1-3 weeks unhide segfaults every time: Nov 30 01:39:48 heisenberg kernel: unhide[208429]: segfault at 7ffd06cfec58 ip 55c15aa077d3 sp 7ffd06cfec60 error 6 in unhide-linux[55c15aa07000+6000] Nov 30 01:39:48 heisenberg kernel: Code: 00 48 89 45 c8 31 c0 48 63 05 5d 98 00 00 48 8d 04 85 0f 00 00 00 48 83 e0 f0 48 29 c4 48 89 65 98 48 29 c4 31 c0 48 89 65 90 d8 3e 00 00 31 c0 66 0f 1f 44 00 00 48 8b 4d 98 48 8b 55 90 c7 Cheers, Chris. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages unhide depends on: ii libc6 2.29-3 unhide recommends no packages. Versions of packages unhide suggests: ii rkhunter 1.4.6-7 -- no debconf information
Processed: unblock 945674 by 937448
Processing commands for cont...@bugs.debian.org: > unblock 945674 by 937448 Bug #945674 [src:nextcloud-desktop] nextcloud-desktop: Python2 removal in sid/bullseye 945674 was blocked by: 937628 945863 945674 was blocking: 937448 937628 Removed blocking bug(s) of 945674: 937448 > thanks Stopping processing here. Please contact me if you need assistance. -- 945674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945674 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#936558: freeradius: Python2 removal in sid/bullseye
Processing control commands: > tags -1 + pending Bug #936558 [src:freeradius] freeradius: Python2 removal in sid/bullseye Added tag(s) pending. -- 936558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936558 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#936558: freeradius: Python2 removal in sid/bullseye
Control: tags -1 + pending The change replacing freeradius-python2 with freeradius-python3 has been staged in the py2removal branch at https://salsa.debian.org/debian/freeradius/commits/py2removal and uploaded to experimental in 3.0.20+dfsg-2. It is now waiting in NEW.
Bug#944627: marked as done (chromium: FTBFS on armhf)
Your message dated Fri, 29 Nov 2019 18:54:26 -0500 with message-id and subject line Re: Bug#944627: Removal of chromium from testing has caused the Debian Bug report #944627, regarding chromium: FTBFS on armhf to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 944627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: src:chromium version: 78.0.3904.97-1 severity: serious tags: ftbfs Hi, The latest upload of chromium to unstable fails on armhf: https://buildd.debian.org/status/package.php?p=chromium Cheers, Ivo --- End Message --- --- Begin Message --- version: 79.0.3945.56-1--- End Message ---
Bug#925726: marked as done (kf5-messagelib: ftbfs with GCC-9)
Your message dated Sat, 30 Nov 2019 00:25:31 +0100 with message-id <1851378.yEFuQpiVaj@tuxin> and subject line Re: Bug#925726: kf5-messagelib: ftbfs with GCC-9 has caused the Debian Bug report #925726, regarding kf5-messagelib: ftbfs with GCC-9 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.) -- 925726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925726 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:kf5-messagelib Version: 4:18.08.3-2 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-9 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc9-20190321/kf5-messagelib_18.08.3-2_unstable_gcc9.log The last lines of the build log are at the end of this report. To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-9/porting_to.html GCC 9 also passes the linker option --as-needed by default; typical build issues are passing libraries before object files to the linker, or underlinking of convenience libraries built from the same source. [...] dh_link # [-a] dh_compress '-X.dcl' '-X.docbook' '-X-license' '-X.tag' '-X.sty' '-X.el' # [-a] dh_fixperms # [-a] make[1]: Leaving directory '/<>' # "install-arch" target is done /usr/bin/make -f debian/rules dhmk_run_binary-arch_commands DHMK_TARGET="binary-arch" make[1]: Entering directory '/<>' dh_strip # [-a] dh_makeshlibs '-Xusr/lib/libkdeinit5_*' # [-a] dpkg-gensymbols: warning: debian/libkf5messagecomposer5abi1/DEBIAN/symbols doesn't match completely debian/libkf5messagecomposer5abi1.symbols --- debian/libkf5messagecomposer5abi1.symbols (libkf5messagecomposer5abi1_4:18.08.3-2_amd64) +++ dpkg-gensymbolstjoKZs 2019-03-26 15:33:29.977247635 + @@ -1182,7 +1182,7 @@ (optional=templinst)_ZNSt6vectorIN5GpgME3KeyESaIS1_EE15_M_range_insertIN9__gnu_cxx17__normal_iteratorIPS1_S3_vS8_T_S9_St20forward_iterator_tag@ABI_5_1 4:18.07.90 (optional=templinst)_ZNSt6vectorIN5GpgME3KeyESaIS1_EE17_M_realloc_insertIJRKS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@ABI_5_1 4:18.07.90 (optional=templinst)_ZNSt6vectorIN5GpgME3KeyESaIS1_EE8_M_eraseEN9__gnu_cxx17__normal_iteratorIPS1_S3_EES7_@ABI_5_1 4:18.07.90 - (optional=templinst)_ZNSt6vectorIN5GpgME3KeyESaIS1_EE9push_backERKS1_@ABI_5_1 4:18.07.90 +#MISSING: 4:18.08.3-2# (optional=templinst)_ZNSt6vectorIN5GpgME3KeyESaIS1_EE9push_backERKS1_@ABI_5_1 4:18.07.90 (optional=templinst)_ZNSt6vectorIN5GpgME3KeyESaIS1_EEC1ERKS3_@ABI_5_1 4:18.07.90 (optional=templinst)_ZNSt6vectorIN5GpgME3KeyESaIS1_EEC2ERKS3_@ABI_5_1 4:18.07.90 (optional=templinst)_ZNSt6vectorIN5GpgME3KeyESaIS1_EED1Ev@ABI_5_1 4:18.07.90 dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libkf5messagelist5abi1/DEBIAN/symbols doesn't match completely debian/libkf5messagelist5abi1.symbols --- debian/libkf5messagelist5abi1.symbols (libkf5messagelist5abi1_4:18.08.3-2_amd64) +++ dpkg-gensymbols2WTmDc 2019-03-26 15:33:30.337247760 + @@ -349,7 +349,7 @@ _ZN11MessageList6WidgetD1Ev@ABI_5_1 4:18.07.90 _ZN11MessageList6WidgetD2Ev@ABI_5_1 4:18.07.90 (optional=templinst)_ZN12KConfigGroup10writeEntryIiEEvPKcRKT_6QFlagsIN11KConfigBase15WriteConfigFlagEE@ABI_5_1 4:18.07.90 - _ZN9QHashData9hasShrunkEv@ABI_5_1 4:18.07.90 +#MISSING: 4:18.08.3-2# _ZN9QHashData9hasShrunkEv@ABI_5_1 4:18.07.90 _ZNK11MessageList12StorageModel10itemForRowEi@ABI_5_1 4:18.07.90 _ZNK11MessageList12StorageModel10metaObjectEv@ABI_5_1 4:18.07.90 _ZNK11MessageList12StorageModel11columnCountERK11QModelIndex@ABI_5_1 4:18.07.90 dpkg-gensymbols: warning: debian/libkf5messageviewer5abi1/DEBIAN/symbols doesn't match
Bug#945330: yt ftbfs in unstable
The issue seems similar to https://github.com/yt-project/yt/issues/2313 and due to numpy 1.17 Which has been fixed with that commit https://github.com/yt-project/unyt/commit/27894c1e Cheers,
Bug#945857: rust-tiff: (build-)depends on cruft package.
Package: rust-tiff Version: 0.3.1-2 Severity: serious Tags: bullseye, sid librust-tiff-dev depends on and the rust-tiff source package build-depends on librust-num-derive-0.2+default-dev which is no longer provided by librust-tiff-dev. It seems to have been replaced by librust-num-derive-0.3+default-dev
Bug#937952: marked as done (python-nose-parameterized: Python2 removal in sid/bullseye)
Your message dated Fri, 29 Nov 2019 22:19:46 + with message-id and subject line Bug#937952: fixed in python-nose-parameterized 0.3.4-5 has caused the Debian Bug report #937952, regarding python-nose-parameterized: 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.) -- 937952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-nose-parameterized Version: 0.3.4-4 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-nose-parameterized If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-nose-parameterized Source-Version: 0.3.4-5 We believe that the bug you reported is fixed in the latest version of python-nose-parameterized, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated python-nose-parameterized package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 13 Sep 2019 13:22:15 +0200 Source: python-nose-parameterized Architecture: source Version: 0.3.4-5 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Closes: 937952 Changes: python-nose-parameterized (0.3.4-5) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Use team+openst...@tracker.debian.org as maintainer * Use debhelper-compat instead of debian/compat. * d/control: Set Vcs-* to salsa.debian.org * d/watch: Use https protocol . [ Daniel Baumann ] * Updating copyright format url. * Updating maintainer field. * Running wrap-and-sort -bast. * Removing gbp.conf, not used anymore or should be specified in the developers dotfiles. * Updating standards version to 4.1.0. . [ Thomas Goirand ] * Removed Python 2 support (Closes: #937952). Checksu
Bug#945851: libnum-ocaml-dev: missing Breaks+Replaces: ocaml-nox (<< 4.08)
Package: libnum-ocaml-dev Version: 1.2-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + libreins-ocaml-dev Hi, during a test with piuparts I noticed your package fails to upgrade from 'buster'. It installed fine in 'buster', then the upgrade to 'bullseye' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): [...] Selecting previously unselected package libnum-ocaml-dev. Preparing to unpack .../27-libnum-ocaml-dev_1.2-2_amd64.deb ... Unpacking libnum-ocaml-dev (1.2-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-LYjFx6/27-libnum-ocaml-dev_1.2-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/ocaml/arith_flags.cmx', which is also in package ocaml-nox 4.05.0-11 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../28-libreins-ocaml-dev_0.1a-9+b1_amd64.deb ... Unpacking libreins-ocaml-dev (0.1a-9+b1) over (0.1a-7+b1) ... Preparing to unpack .../29-ocaml-compiler-libs_4.08.1-4_amd64.deb ... Unpacking ocaml-compiler-libs (4.08.1-4) over (4.05.0-11) ... dpkg: considering deconfiguration of ocaml-base-nox, which would be broken by installation of ocaml-nox ... dpkg: yes, will deconfigure ocaml-base-nox (broken by ocaml-nox) Preparing to unpack .../30-ocaml-nox_4.08.1-4_amd64.deb ... De-configuring ocaml-base-nox (4.05.0-11) ... Unpacking ocaml-nox (4.08.1-4) over (4.05.0-11) ... Replacing files in old package ocaml-base-nox (4.05.0-11) ... Preparing to unpack .../31-ocaml-base-nox_4.08.1-4_amd64.deb ... Unpacking ocaml-base-nox (4.08.1-4) over (4.05.0-11) ... Preparing to unpack .../32-ocaml-interp_4.08.1-4_amd64.deb ... Unpacking ocaml-interp (4.08.1-4) over (4.05.0-11) ... Selecting previously unselected package libnum-ocaml. Preparing to unpack .../33-libnum-ocaml_1.2-2_amd64.deb ... Unpacking libnum-ocaml (1.2-2) ... Preparing to unpack .../34-libss2_1.45.4-1_amd64.deb ... Unpacking libss2:amd64 (1.45.4-1) over (1.44.5-1+deb10u2) ... Errors were encountered while processing: /tmp/apt-dpkg-install-LYjFx6/27-libnum-ocaml-dev_1.2-2_amd64.deb cheers, Andreas libreins-ocaml-dev_0.1a-9+b1.log.gz Description: application/gzip
Processed: libnum-ocaml-dev: missing Breaks+Replaces: ocaml-nox (<< 4.08)
Processing control commands: > affects -1 + libreins-ocaml-dev Bug #945851 [libnum-ocaml-dev] libnum-ocaml-dev: missing Breaks+Replaces: ocaml-nox (<< 4.08) Added indication that 945851 affects libreins-ocaml-dev -- 945851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945851 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: owner 938785
Processing commands for cont...@bugs.debian.org: > owner 938785 ! Bug #938785 [src:virtualenv-clone] virtualenv-clone: Python2 removal in sid/bullseye Owner recorded as Nicholas D Steeves . > thanks Stopping processing here. Please contact me if you need assistance. -- 938785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938785 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#939869: marked as done (qemu: CVE-2019-15890)
Your message dated Fri, 29 Nov 2019 21:06:22 +0300 with message-id <3e483a16-1e63-bcbf-cf7b-3827db958...@msgid.tls.msk.ru> and subject line Bug#939869: CVE-2019-15890 has caused the Debian Bug report #939869, regarding qemu: CVE-2019-15890 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.) -- 939869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: slirp4netns Version: 0.3.2-1 Severity: grave Tags: security upstream Justification: user security hole Control: clone -1 -2 Control: reassign -2 src:qemu 1:4.1-1 Control: retitle -2 qemu: CVE-2019-15890 Hi, The following vulnerability was published for slirp4netns. CVE-2019-15890[0]: | libslirp 4.0.0, as used in QEMU 4.1.0, has a use-after-free in | ip_reass in ip_input.c. I'm filling this with higher serverity as you proably would have expected, but for buster and older I guess we can follow this as no-dsa and schedule fixes via point releases or include in future DSAs. As unprivileged user namespaces are not enabled by default the former holds surely for slirp4netns itself. The bug is cloned as well for qemu. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-15890 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15890 [1] https://www.openwall.com/lists/oss-security/2019/09/06/3 [2] https://gitlab.freedesktop.org/slirp/libslirp/commit/c59279437eda91841b9d26079c70b8a540d41204 Please adjust the affected versions in the BTS as needed, only looked at the respective unstable versions. Regards, Salvatore --- End Message --- --- Begin Message --- Version: 1:4.1-2 This is fixed in 4.1-2, which switched to a separate libslirp (where this bug has been fixed a while ago). I forgot to mention this bug in the changelog. /mjt--- End Message ---
Bug#945747: marked as done (xastir: Python2 removal in sid/bullseye)
Your message dated Fri, 29 Nov 2019 17:50:46 + with message-id and subject line Bug#945747: fixed in xastir 2.1.4+git20191127.bb66a77-1 has caused the Debian Bug report #945747, regarding xastir: 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.) -- 945747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945747 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xastir Version: 2.1.4-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_take3.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: xastir Source-Version: 2.1.4+git20191127.bb66a77-1 We believe that the bug you reported is fixed in the latest version of xastir, 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 945...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill (supplier of updated xastir 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, 29 Nov 2019 09:06:38 -0800 Source: xastir Architecture: source Version: 2.1.4+git20191127.bb66a77-1 Distribution: unstable Urgency: medium Maintainer: Debian Hamradio Maintainers Changed-By: tony mancill Closes: 945747 Changes: xastir (2.1.4+git20191127.bb66a77-1) unstable; urgency=medium . * Team upload. . [ Christoph Berg ] * Mark xastir-data as Multi-Arch: foreign. . [ tony mancill ] * New snapshot upstream version 2.1.4+git20191127.bb66a77 * Remove Recommends on python (Closes: #945747) * Bump Standards-Version to 4.4.1 * Use https URL for Homepage * Update Source field in debian/copyright * Refresh patches for new upstream release * Add patch to no longer attempt to install .py files * Add patch to set snapshot version 2.1.4+bb66a77 * Add patch for typos in upstream source * Set "Rules-Requires-Root: no" in debian/control * Remove reference to Xastir_tigerpoly.py in debian/copyright * Thank you to Dave Aitcheson, KB3EFS Checksums-Sha1: 646a08b64d7fa2fb3a61829e38b684d43fe7e55c 2506 xastir_2.1.4+git20191127.bb66a77-1.dsc f6dae692bac
Bug#936968: marked as done (lqa: Python2 removal in sid/bullseye)
Your message dated Fri, 29 Nov 2019 17:50:36 + with message-id and subject line Bug#936968: fixed in lqa 20191129~git41a4806-1 has caused the Debian Bug report #936968, regarding lqa: 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.) -- 936968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lqa Version: 20180702.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. 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:lqa 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: lqa Source-Version: 20191129~git41a4806-1 We believe that the bug you reported is fixed in the latest version of lqa, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrej Shadura (supplier of updated lqa package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 29 Nov 2019 18:43:33 +0100 Source: lqa Architecture: source Version: 20191129~git41a4806-1 Distribution: unstable Urgency: medium Maintainer: Andrew Lee (李健秋) Changed-By: Andrej Shadura Closes: 936968 Changes: lqa (20191129~git41a4806-1) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Remove ancient X-Python-Version field. . [ Andrej Shadura ] * New upstream snapshot. * Add a watch file. * Update gbp.conf. * Drop Python 2 support (Closes: #936968). * Bump debhelper from old 9 to 12. * d/control: Add .git to Vcs-Git. * Bump Standards-Version to 4.4.1. Checksums-Sha1: 8ddc730bd2a0d3a5e994af278836e871786a9bfb 1845 lqa_20191129~git41a4806-1.dsc 877524626aec62579d210fa2124a899f89edcfe9 26316 lqa_20191129~git41a4806.orig.tar.xz 6413c073507a2a4c9312dc70bd2134cf1d22ab08 2180 lqa_20191129~git41a4806-1.debian.tar.xz Checksums-Sha256: 0ab758ed4099e163556f8172e81076a41ff29b627b0b6
Processed: Bug#945747 marked as pending in xastir
Processing control commands: > tag -1 pending Bug #945747 [src:xastir] xastir: Python2 removal in sid/bullseye Added tag(s) pending. -- 945747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945747 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945747: marked as pending in xastir
Control: tag -1 pending Hello, Bug #945747 in xastir reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian-hamradio-team/xastir/commit/970611f959116eaac388bddaa225ffbd9972d2ad Remove Recommends on python (Closes: #945747) (this message was generated automatically) -- Greetings https://bugs.debian.org/945747
Bug#945751: marked as done (openafs-modules-dkms: openafs-dkms kernel module does not build for kernel 5.3.0-2-amd64)
Your message dated Fri, 29 Nov 2019 09:20:31 -0800 with message-id <20191129172031.gx32...@mit.edu> and subject line Re: Bug#945751: openafs-modules-dkms: openafs-dkms kernel module does not build for kernel 5.3.0-2-amd64 has caused the Debian Bug report #945751, regarding openafs-modules-dkms: openafs-dkms kernel module does not build for kernel 5.3.0-2-amd64 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.) -- 945751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openafs-modules-dkms Version: 1.8.4~pre1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, The openafs-dkms kernel module fails to build on kernel 5.3.0-2 on buster. In file included from /var/lib/dkms/openafs/1.8.4pre1/build/src/libafs/MODLOAD-5.3.0-2-amd64-SP/rx_kmutex.c:24: /var/lib/dkms/openafs/1.8.4pre1/build/src/afs/LINUX/osi_compat.h: In function ‘afs_linux_search_keyring’: /var/lib/dkms/openafs/1.8.4pre1/build/src/afs/LINUX/osi_compat.h:225:12: error: too few arguments to function ‘keyring_search’ 225 | key_ref = keyring_search( |^~ In file included from /usr/src/linux- headers-5.3.0-2-common/include/linux/cred.h:13, from /usr/src/linux- headers-5.3.0-2-common/include/linux/seq_file.h:12, from /usr/src/linux- headers-5.3.0-2-common/include/linux/seq_file_net.h:5, from /usr/src/linux- headers-5.3.0-2-common/include/net/net_namespace.h:177, from /usr/src/linux- headers-5.3.0-2-common/include/linux/netdevice.h:38, from /usr/src/linux- headers-5.3.0-2-common/include/net/inet_sock.h:19, from /usr/src/linux- headers-5.3.0-2-common/include/linux/udp.h:16, from /var/lib/dkms/openafs/1.8.4pre1/build/src/libafs/MODLOAD-5.3.0-2-amd64-SP/./netinet/udp.h:1, from /var/lib/dkms/openafs/1.8.4pre1/build/src/rx/rx_kcommon.h:110, from /var/lib/dkms/openafs/1.8.4pre1/build/src/libafs/MODLOAD-5.3.0-2-amd64-SP/rx_kmutex.c:20: /usr/src/linux-headers-5.3.0-2-common/include/linux/key.h:387:18: note: declared here 387 | extern key_ref_t keyring_search(key_ref_t keyring, | ^~ make[5]: *** [/usr/src/linux-headers-5.3.0-2-common/scripts/Makefile.build:286: /var/lib/dkms/openafs/1.8.4pre1/build/src/libafs/MODLOAD-5.3.0-2-amd64-SP/rx_kmutex.o] Fehler 1 make[4]: *** [/usr/src/linux-headers-5.3.0-2-common/Makefile:1639: _module_/var/lib/dkms/openafs/1.8.4pre1/build/src/libafs/MODLOAD-5.3.0-2-amd64-SP] Fehler 2 make[3]: *** [/usr/src/linux-headers-5.3.0-2-common/Makefile:179: sub-make] Fehler 2 make[3]: Verzeichnis „/usr/src/linux-headers-5.3.0-2-amd64“ wird verlassen FAILURE: make exit code 2 make[2]: *** [Makefile.afs:280: openafs.ko] Fehler 1 make[2]: Verzeichnis „/var/lib/dkms/openafs/1.8.4pre1/build/src/libafs/MODLOAD-5.3.0-2-amd64-SP“ wird verlassen make[1]: *** [Makefile:187: linux_compdirs] Fehler 2 make[1]: Verzeichnis „/var/lib/dkms/openafs/1.8.4pre1/build/src/libafs“ wird verlassen make: *** [Makefile:15: all] Fehler 2 -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openafs-modules-dkms depends on: ii dkms 2.8.1-3 ii libc6-dev 2.29-3 ii perl 5.30.0-9 Versions of packages openafs-modules-dkms recommends: ii openafs-client 1.8.4~pre1-1 openafs-modules-dkms suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- control -1 fixed 1.8.5-1 On Thu, Nov 28, 2019 at 02:35:48AM +0100, Robert Senger wrote: > Package: openafs-modules-dkms > Version: 1.8.4~pre1-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > > Dear Maintainer, > > The openafs-dkms kernel module fails to build on kernel 5.3.0-2 on buster. > > In file included from > /var/lib/dkms/openafs/1.8.4pre1/build/src/libafs/MODLOAD-5.3.0-2-amd64-SP/rx_kmutex.c:24: > /var/lib/dkms/openafs/1.8.4pre1/build/src/afs/LINUX/osi_compat.h: In function > ‘afs_linux_s
Bug#943298: marked as done (xlsx2csv: Python2 removal in sid/bullseye)
Your message dated Fri, 29 Nov 2019 17:04:39 + with message-id and subject line Bug#943298: fixed in xlsx2csv 1:0.7.6-1 has caused the Debian Bug report #943298, regarding xlsx2csv: 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.) -- 943298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943298 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xlsx2csv Version: 1:0.7.4+git20181115.89ffd7d-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 --- Source: xlsx2csv Source-Version: 1:0.7.6-1 We believe that the bug you reported is fixed in the latest version of xlsx2csv, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 943...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated xlsx2csv 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, 29 Nov 2019 16:00:07 +0100 Source: xlsx2csv Architecture: source Version: 1:0.7.6-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Andreas Tille Closes: 920073 943298 Changes: xlsx2csv (1:0.7.6-1) unstable; urgency=medium . * Take over package into Debian Science team Closes: #920073 * New upstream version supporting Python3 Closes: #943298 * Standards-Version: 4.4.1 * Respect DEB_BUILD_OPTIONS in override_dh_auto_test target * Do not parse d/changelog * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Provide upstream test suite as examples * Add autopkgtest Checksums-Sha1: fa688e0deae2fe5c0176bf83a0592d9510bb 2000 xlsx2csv_0.7.6-1.dsc 7a068e343c4f27f9051e5a6b9a758540bfd16c58 218817 xlsx2csv_0.7.6.orig.tar.gz 3201b0d9a8f75c79c242d32a2c3a4d912fa9d47a 3916 xlsx2csv_0.7.6-1.debian.tar.xz 00d16861ba5ae69cb2e02ce9609e008c53981e07 6019 xlsx2csv_0.7.6-1_amd64.buildinfo Checksums-Sha256: 0a4c07d01085270913659d357c2998c8b309a925f7341a3d1d239325a392810a 2000 xlsx2csv_0.7.6-
Bug#945840: /usr/bin/ledger: error while loading shared libraries: libboost_python27.so.1.67.0: cannot open shared object file: No such file or directory
Package: ledger Version: 3.1.2+dfsg1-1 Severity: grave Justification: renders package unusable The subject really says it all. Invoking ledger fails with the mentioned error: /usr/bin/ledger: error while loading shared libraries: libboost_python27.so.1.67.0: cannot open shared object file: No such file or directory ldd shows the missing library: $ ldd /usr/bin/ledger linux-vdso.so.1 (0x7fffa1958000) libledger.so.3 => /usr/lib/ledger/libledger.so.3 (0x7f745af4) libboost_filesystem.so.1.67.0 => /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.67.0 (0x7f745af08000) libboost_system.so.1.67.0 => /usr/lib/x86_64-linux-gnu/libboost_system.so.1.67.0 (0x7f745af01000) libpython2.7.so.1.0 => /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 (0x7f745ab95000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7f745a9bc000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7f745a9a2000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f745a7e) libmpfr.so.6 => /usr/lib/x86_64-linux-gnu/libmpfr.so.6 (0x7f745a75e000) libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 (0x7f745a6db000) libboost_iostreams.so.1.67.0 => /usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.67.0 (0x7f745a6bd000) libboost_regex.so.1.67.0 => /usr/lib/x86_64-linux-gnu/libboost_regex.so.1.67.0 (0x7f745a587000) libboost_python27.so.1.67.0 => not found libicuuc.so.63 => /usr/lib/x86_64-linux-gnu/libicuuc.so.63 (0x7f745a3b5000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f745a27) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f745a24f000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f745a232000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f745a22d000) libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x7f745a228000) /lib64/ld-linux-x86-64.so.2 (0x7f745b54) libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x7f745a213000) libicui18n.so.63 => /usr/lib/x86_64-linux-gnu/libicui18n.so.63 (0x7f7459f38000) libicudata.so.63 => /usr/lib/x86_64-linux-gnu/libicudata.so.63 (0x7f7458547000) Please, reassign the bug to whatever package it belongs (if it’s not ledger). Thanks. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_USER Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ledger depends on: ii libboost-filesystem1.67.0 1.67.0-15 ii libboost-iostreams1.67.0 1.67.0-15 ii libboost-python1.67.0 1.67.0-15 ii libboost-regex1.67.0 1.67.0-15 ii libboost-system1.67.0 1.67.0-15 ii libc6 2.29-3 ii libgcc11:9.2.1-20 ii libgmp10 2:6.1.2+dfsg-4 ii libicu63 63.2-2 ii libmpfr6 4.0.2-1 ii libpython2.7 2.7.17-1 ii libstdc++6 9.2.1-20 ledger recommends no packages. Versions of packages ledger suggests: pn elpa-ledger pn python-ledger -- no debconf information
Processed: Re: Bug#945775: python-sponge: should this package be removed.
Processing control commands: > reassign -1 ftp.debian.org Bug #945775 [python-sponge] python-sponge: should this package be removed. Bug reassigned from package 'python-sponge' to 'ftp.debian.org'. No longer marked as found in versions python-sponge/0.3.1-1.1. Ignoring request to alter fixed versions of bug #945775 to the same values previously set > severity -1 normal Bug #945775 [ftp.debian.org] python-sponge: should this package be removed. Severity set to 'normal' from 'serious' > retitle -1 RM: python-sponge -- RoQA; RC buggy, unmaintained, low popcon Bug #945775 [ftp.debian.org] python-sponge: should this package be removed. Changed Bug title to 'RM: python-sponge -- RoQA; RC buggy, unmaintained, low popcon' from 'python-sponge: should this package be removed.'. -- 945775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945775 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945775: python-sponge: should this package be removed.
Control: reassign -1 ftp.debian.org Control: severity -1 normal Control: retitle -1 RM: python-sponge -- RoQA; RC buggy, unmaintained, low popcon On Thu, Nov 28, 2019 at 01:33:25PM +, peter green wrote: > To me this adds up to a package that is not in a fit state to remain > in Debian, if noone disagrees I will likely convert this bug to a > removal request in the not too distant future. Sure, let's do this already! -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#945258: marked as done (qemu: Filesystem corruption caused by qemu in qcow2 images)
Your message dated Fri, 29 Nov 2019 14:40:50 + with message-id and subject line Bug#945258: fixed in qemu 1:4.1-2 has caused the Debian Bug report #945258, regarding qemu: Filesystem corruption caused by qemu in qcow2 images 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.) -- 945258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qemu Severity: important Dear Maintainer, Currently qemu 4.1 periodically corrupts vm images (qcow2), due to this bug: https://bugs.launchpad.net/qemu/+bug/1846427 Please temporarily apply the provided patches, until upstream will release the fixed version: https://patchwork.kernel.org/cover/11207161/ https://patchwork.kernel.org/patch/11207167/ https://patchwork.kernel.org/patch/11207139/ https://patchwork.kernel.org/patch/11207171/ Thanks! -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-rc7+ (SMP w/24 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: qemu Source-Version: 1:4.1-2 We believe that the bug you reported is fixed in the latest version of qemu, 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 945...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Tokarev (supplier of updated qemu 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: Mon, 25 Nov 2019 12:54:05 +0300 Source: qemu Architecture: source Version: 1:4.1-2 Distribution: unstable Urgency: medium Maintainer: Debian QEMU Team Changed-By: Michael Tokarev Closes: 944623 945072 945258 Changes: qemu (1:4.1-2) unstable; urgency=medium . * build sgabios in build-indep, conflict with sgabios package * qemu-system-ppc: build and install canyonlands.dtb in addition to bamboo.dtb * remove duplicated CVE-2018-20123 & CVE-2018-20124 in prev changelog * move s390 firmware build rules to debian/s390fw.mak, build s390-netboot.img * imported v4.1.1.diff - upstream stable branch Closes: CVE-2019-12068 Closes: #945258, #945072 * enable-pschange-mc-no.patch: i386: add PSCHANGE_MC_NO feature to allow disabling ITLB multihit mitigations in nested hypervisors Closes: #944623 * build-depend on nettle-dev, enable nettle, and clarify --enable-lzo * switch to system libslirp, build-depend on libslirp-dev Closes: CVE-2019-15890 Checksums-Sha1: c6616decfcf478a56091d720a5cdd3c28d7e0557 6131 qemu_4.1-2.dsc dbf587c286d953719ffe955c01d1af10ecd76f59 157252 qemu_4.1-2.debian.tar.xz ca2d35af9a67c6fc54f44db4c7fa5802509e568e 8182 qemu_4.1-2_source.buildinfo Checksums-Sha256: fb3b4d21168e694a1ebd8e570470264f6a20c3f602ba32dcf060a5615bdc171e 6131 qemu_4.1-2.dsc e5a0eaf83ea8c093e6d22178fce7a6716f82ed5fd85ba4cf57957dbb258d35f7 157252 qemu_4.1-2.debian.tar.xz e42d95e4dd65da8647ea3b79f7be7a223a0b54d43c8cba4f7be70589572654a9 8182 qemu_4.1-2_source.buildinfo Files: c34dd7ddb3a4f5d724308f31c06ee7f3 6131 otherosfs optional qemu_4.1-2.dsc 4a4a3af160c8b817e0b9c06fa28d5282 157252 otherosfs optional qemu_4.1-2.debian.tar.xz 93aecd6133f3d2d0ab99e6f35a759be0 8182 otherosfs optional qemu_4.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQFDBAEBCAAtFiEEe3O61ovnosKJMUsicBtPaxppPlkFAl3hJj0PHG1qdEB0bHMu bXNrLnJ1AAoJEHAbT2saaT5Zw9UH/2RJW790E2H/ivHq3L/6xi7lbkBZdF85q71B g2Rx6ETZB/Ru6V1jcW+jlxr2lsZhMmMRoP8fbDnSVAO1fXPlVdVbK6c+35Zcqb2z DuWuALoKIu9/CuD32bdNXkUiNDfcgsGhPkVOQa0MG8DGbhnaeW6CDMUg1EM6Y0XG I6elERR9CUxftC/+CCNav+Hin/iD0gwq+CmawOr6ZUW+kWPvsg2ZySio2Vk6jx8m 2hzIGpy0+IKWWoZU7Q5MBGapMCu5o8gb8bODXwJo6FVhk6kJxlKrYggtZjyopxSA C8/+1vLe/Y3bf6L12HWkScEg4NNubKwor+XWkf6PPa8W+TXwZmY= =0MlX -END PGP SIGNATURE End Message ---
Bug#936815: marked as done (landslide: Python2 removal in sid/bullseye)
Your message dated Fri, 29 Nov 2019 14:38:12 + with message-id and subject line Bug#936815: fixed in landslide 1.1.3-2 has caused the Debian Bug report #936815, regarding landslide: 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.) -- 936815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936815 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:landslide Version: 1.1.3-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:landslide 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: landslide Source-Version: 1.1.3-2 We believe that the bug you reported is fixed in the latest version of landslide, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrej Shadura (supplier of updated landslide package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 29 Nov 2019 14:55:55 +0100 Source: landslide Architecture: source Version: 1.1.3-2 Distribution: unstable Urgency: medium Maintainer: Andrej Shadura Changed-By: Andrej Shadura Closes: 936815 Changes: landslide (1.1.3-2) unstable; urgency=medium . * Remove the shipped Python 2 module (Closes: #936815). Checksums-Sha1: d71c46ee5994a76ee692eb165a41ddcd3036be75 1624 landslide_1.1.3-2.dsc 9a6387881c5a5c1d3a405d76a3e42b180f251e2e 2640 landslide_1.1.3-2.debian.tar.xz Checksums-Sha256: 59f400a072fcb91a5350a23a0c24291d4dcf4ddc8a330ff058f0b9c3fc49846f 1624 landslide_1.1.3-2.dsc e8eb3f4350b9adf29c235271be2a6d07a9c0114c113520464fb1235dbe24c305 2640 landslide_1.1.3-2.debian.tar.xz Files: fb65d6acd749ebb475dcf2b72d29f64d 1624 oldlibs optional landslide_1.1.3-2.dsc 4571c85fbfc024ace0fd247bdbf10e8d 2640 oldlibs optional landslide_1.1.3-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl3hI7MACgkQXkCM2RzY OdKn
Processed (with 2 errors): bug reassignment
Processing commands for cont...@bugs.debian.org: > reassign 945453 insighttoolkit4 4.13.2-dfsg1-1 Bug #945453 [src:camitk] camitk: FTBFS, uninstallable build-deps in unstable Bug reassigned from package 'src:camitk' to 'insighttoolkit4'. No longer marked as found in versions camitk/4.1.2-3. Ignoring request to alter fixed versions of bug #945453 to the same values previously set Bug #945453 [insighttoolkit4] camitk: FTBFS, uninstallable build-deps in unstable There is no source info for the package 'insighttoolkit4' at version '4.13.2-dfsg1-1' with architecture '' Unable to make a source version for version '4.13.2-dfsg1-1' Marked as found in versions 4.13.2-dfsg1-1. > merge 944636 945453 Bug #944636 [src:insighttoolkit4] insighttoolkit4: CMake missing files for imported targets Unable to merge bugs because: affects of #945453 is '' not 'elastix,ginkgocadx,src:otb' package of #945453 is 'insighttoolkit4' not 'src:insighttoolkit4' Failed to merge 944636: Did not alter merged bugs. > affects 944636 camitk Failed to mark 944636 as affecting package(s): failed to get lock on /srv/bugs.debian.org/spool/lock/944636 -- Unable to lock /srv/bugs.debian.org/spool/lock/944636 Resource temporarily unavailable. Unable to lock /srv/bugs.debian.org/spool/lock/944636 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/944636 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/944636 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/944636 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/944636 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/944636 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/944636 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/944636 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/944636 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. at /usr/local/lib/site_perl/Debbugs/Common.pm line 650. > End of message, stopping processing here. Please contact me if you need assistance. -- 944636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944636 945453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#945826: Server fails for missing boost library
Processing control commands: > severity -1 grave Bug #945826 [freeorion] Server fails for missing boost library Severity set to 'grave' from 'normal' -- 945826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945826 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#944007: marked as done (libobject-remote-perl: test failure with Moo 2.003006)
Your message dated Fri, 29 Nov 2019 13:19:48 + with message-id and subject line Bug#944007: fixed in libobject-remote-perl 0.004001-1 has caused the Debian Bug report #944007, regarding libobject-remote-perl: test failure with Moo 2.003006 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.) -- 944007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944007 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libobject-remote-perl Version: 0.004000-1 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As first seen on ci.debian.net, libobject-remote-perl's test fail: https://ci.debian.net/packages/libo/libobject-remote-perl/unstable/amd64/ https://ci.debian.net/data/autopkgtest/unstable/amd64/libo/libobject-remote-perl/3296702/log.gz Test Summary Report - --- t/await.t (Wstat: 65280 Tests: 1 Failed: 1) Failed test: 1 Non-zero exit status: 255 Parse errors: No plan found in TAP output t/basic.t (Wstat: 65280 Tests: 0 Failed: 0) Non-zero exit status: 255 Parse errors: No plan found in TAP output t/basic_data.t (Wstat: 65280 Tests: 0 Failed: 0) Non-zero exit status: 255 Parse errors: No plan found in TAP output t/bridged.t (Wstat: 256 Tests: 1 Failed: 1) Failed test: 1 Non-zero exit status: 1 t/chained.t (Wstat: 65280 Tests: 0 Failed: 0) Non-zero exit status: 255 Parse errors: No plan found in TAP output t/fatnode.t (Wstat: 65280 Tests: 0 Failed: 0) Non-zero exit status: 255 Parse errors: Bad plan. You planned 1 tests but ran 0. t/not_found.t (Wstat: 65280 Tests: 0 Failed: 0) Non-zero exit status: 255 Parse errors: No plan found in TAP output t/objects.t (Wstat: 65280 Tests: 0 Failed: 0) Non-zero exit status: 255 Parse errors: No plan found in TAP output t/sender.t (Wstat: 65280 Tests: 0 Failed: 0) Non-zero exit status: 255 Parse errors: No plan found in TAP output t/tied.t(Wstat: 65280 Tests: 0 Failed: 0) Non-zero exit status: 255 Parse errors: No plan found in TAP output t/timeout.t (Wstat: 256 Tests: 2 Failed: 1) Failed test: 2 Non-zero exit status: 1 t/transfer.t(Wstat: 1536 Tests: 6 Failed: 6) Failed tests: 1-6 Non-zero exit status: 6 t/watchdog.t(Wstat: 65280 Tests: 0 Failed: 0) Non-zero exit status: 255 Parse errors: No plan found in TAP output t/watchdog_fatnode.t (Wstat: 65280 Tests: 0 Failed: 0) Non-zero exit status: 255 Parse errors: No plan found in TAP output Files=19, Tests=76, 9 wallclock secs ( 0.06 usr 0.02 sys + 4.98 cusr 0.55 csys = 5.61 CPU) Result: FAIL The same happens during a local build. The same can be seen on cpantesters (for perl 5.13.6): http://matrix.cpantesters.org/?dist=Object-Remote%200.004000;os=linux;perl=5.31.6;reports=1 Looking at the logs both from ci.debian.net and cpantesters.org indicates that to upgrade of Moo / libmoo-perl from 2.003004 to 2.003006 caused the breakage; so this may well be a bug in Moo. Cheers, gregor -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl29uslfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgZNMg/9EWK1vlkVZBEIKFfi8G9l5iN6NBMY4mD7ZYpQgKqccUPrcRXAfA5KzvjB fWZhTENm2c9xr0CC3cy3Q2AP8/CalZxwIDQzDHouSkozZF/3DwmynDhRRMyhCyXm VAiaASEyByOWTLMvDhAGVqlt3SWYjUpaESWkPfGA0DjTno3Pg9M3C0YnTjL7VNr0 N5yj/TA01/noPraO23VY1KUrSQf7YvNcDkwr8NmnYw3ZJWLXIonKlaYS4m8l0X12 JTDVWCwDp5+qx6E/FhGxZGhweI4rgUQkZwXmxGKJ2AXwbnylpfQkK0gqHDQtwrf6 x4TJk+v434CboWjhGWXFr24z2YbIC0xV3PgPlJgEZC4Mi8keROHOLMLeh8Zf8W/K NAJS5f3OJLw3BDg216VXWpUBiSrrb9V3lzLSAzCsSRVd6H0hwMxQheLJzNpKU2Pm cErphYd6knyU4XhB+wPjsmabYtwYgsYwbfSmt5i8DnoIvTExdl8dzRIh5l+DW760 AoCnfSgGFAmjiEQqUNFoZc4iNruieQuc9jYXcbZtkRQreB/Cm6paehjrJ7IaA+VR Trkiq2/uRdq/nRqX2M47fI4BgGihjiGX5V0k/PHF/X3smCxQPD4pnF4JyTiFxwLv 6jyklkw9DKds0E09xBs5sKPqY6iNnMoTNkUuyrYa5XYLRWAgbgY= =TrL4 -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: libobject-remote-perl Source-Version: 0.004001-1 We believe that the bug you reported is fixed in the latest version of libobject-remote-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 944...@bugs.debian.org, and the maintainer will reopen the bug report
Bug#945830: FTBFS on multiple architectures
Package: tracker Version: 2.3.1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, Looks like tracker FTBFS on multiple architectures due to a/some test(s). Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages tracker depends on: ii dbus-user-session [default-dbus-session-bus] 1.13.12-2bigon1 ii dbus-x11 [dbus-session-bus] 1.13.12-2bigon1 ii dconf-gsettings-backend [gsettings-backend] 0.34.0-1 ii libc6 2.29-3 ii libglib2.0-0 2.62.3-1 ii libglib2.0-bin2.62.3-1 ii libicu63 63.2-2 ii libsqlite3-0 3.30.1-1 ii libstemmer0d 0+svn585-1.1 ii libtracker-control-2.0-0 2.3.1-1 ii libtracker-sparql-2.0-0 2.3.1-1 ii shared-mime-info 1.10-1 Versions of packages tracker recommends: ii tracker-miner-fs 2.3.1-1 tracker suggests no packages. -- no debconf information
Bug#944718: marked as done (octave-dicom Build-Depends on libgdcm2-dev which isn't build from source anymore)
Your message dated Fri, 29 Nov 2019 12:50:22 + with message-id and subject line Bug#944718: fixed in octave-dicom 0.2.2-4 has caused the Debian Bug report #944718, regarding octave-dicom Build-Depends on libgdcm2-dev which isn't build from source anymore 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.) -- 944718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: octave-dicom Version: 0.2.2-3 Severity: serious Tags: ftbfs sid bullseye -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear maintainers, Your package Build-Depends on libgdcm2-dev, but the src:gdcm package transitioned to 3 and dropped that package. Please fix your package to use the new version of gdcm. Paul - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-debug') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3NHwkACgkQnFyZ6wW9 dQqEkgf+MhxngdDuUVTIaqVr7jICIwuHHc8cO8K7ZjP1hMV4aY5BS3YSQyqMsI+B /SbQ6UvhE2yCxhzlpgVbthGtISwmmMBQNNWY/qshN8WUagHVaZw59ndUEvDTNjYP QQNXkvBq+cMHZJxu84zecjxqlDqBFs1J78c6HdFeTlMfIOhb8RBMY+LfRbQA0xzI ZbjJ2nmBDq1eMea/PMNsNsiNqTDnATqT/4RVVKIZnxyrhemEfzdsGmZZWmHU6PB4 o1psninSsCQNSrlWHz3V6JDwviQLVdIWBQRWJdjT3C/96bF3N5UBeOD7ZmwLzryM Ys0hOBp/zBjCvyCQTsfyCdxachlCWA== =pxx5 -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: octave-dicom Source-Version: 0.2.2-4 We believe that the bug you reported is fixed in the latest version of octave-dicom, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 944...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rafael Laboissière (supplier of updated octave-dicom package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 29 Nov 2019 05:48:57 -0300 Source: octave-dicom Architecture: source Version: 0.2.2-4 Distribution: unstable Urgency: medium Maintainer: Debian Octave Group Changed-By: Rafael Laboissière Closes: 944718 Changes: octave-dicom (0.2.2-4) unstable; urgency=medium . * d/control: Build-depend on libgdcm-dev. Thanks to Steve Langasek, for the patch (Closes: #944718) Checksums-Sha1: 30a4ff471f4ec4803297c8485d7f8ded21ee7c7b 2040 octave-dicom_0.2.2-4.dsc ecb23f19addd3efec1d84698785e4f7927544d82 3824 octave-dicom_0.2.2-4.debian.tar.xz a8d71c92c9634c9ec1cecb0f0a52b2bd6c8b302e 16947 octave-dicom_0.2.2-4_amd64.buildinfo Checksums-Sha256: 184dac565ceed35fd6e998893efd58939f47a4e59e9a64f3b0192f6e82e64ea1 2040 octave-dicom_0.2.2-4.dsc 86eec505eca13d2b9748394a604be681a6d7e13cf2203c91b67e845ce95c3d07 3824 octave-dicom_0.2.2-4.debian.tar.xz 5051531ca2fae4a73d5ff8a4730733ae853848e8c6be888a80c743ef710aa5c8 16947 octave-dicom_0.2.2-4_amd64.buildinfo Files: f0690846f5feef5657aa6b218d8acf5c 2040 math optional octave-dicom_0.2.2-4.dsc f2a11f4d6a4fa461f4fd17c6067968d6 3824 math optional octave-dicom_0.2.2-4.debian.tar.xz a5b3ac8d6e24adcdcc104be8fdf10786 16947 math optional octave-dicom_0.2.2-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEP0ZDkUmP6HS9tdmPISSqGYN4XJAFAl3hCS0ACgkQISSqGYN4 XJBvwA/9ERgf9fsoZUnpOQtFLy5tntsmaWRQZJ1wnguzoJWYeBcWOSmANVYla8fd TAfHMunv7EWILH+FSY45sAsvVVNQxI+cURa2ln8luuGr0U1pNWG1G3s1SbvITg8J LlDIjP3PrFv105s7skJKMxuT4832X+ekTBZGk1VNeH1JorQ24/y0ROCy0OYEtrHc y+tnyDHrr0zTSPNXQGzpqbbY5ZGX6VXHhOzqdzbSX42F3xknT+d08tY3z+oXIVaI 6WEMKVAldREPQZg7r5XyP9EgSQEOMWSxfT5EA1d/qb6VtcKX6EZ91nEMzk3kD5em TXs2+6b9XiZZgzgCQCyV0ydqMvmenBKmAFAC5lcmAR5goqFM4eW/cP5ZnKCzmw/o NVbi6HeIf2bhH/5+mwUYw2lFi0XvdSraEcDpzjcKR4WkeIAqBmN/FtXByweNBJ6n rmS/BGnurSYoccejOGM/QBmA/KJpLEbPaQXIJoI4ZzjR+cZ75T66ntLUQBpoIkwi aWhMK1QXAim+51FBp1TJzZpw90rO9f+K2DnU3da2TOtDWukuqDITMp7FXwQFYip2 xRSsobx7vwEx4h52SjcgPNv1y9cE92pYUpYlo3VTcJ
Processed: Bug#944718 marked as pending in octave-dicom
Processing control commands: > tag -1 pending Bug #944718 [src:octave-dicom] octave-dicom Build-Depends on libgdcm2-dev which isn't build from source anymore Added tag(s) pending. -- 944718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#944718: marked as pending in octave-dicom
Control: tag -1 pending Hello, Bug #944718 in octave-dicom 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/pkg-octave-team/octave-dicom/commit/3eee9cf27b1d7fbcab981e868f75ff72655a0974 d/control: Build-depend on cmake and libgdcm-dev Closes: #944718 Thanks: Steve Langasek, for the patch (this message was generated automatically) -- Greetings https://bugs.debian.org/944718
Bug#936810: marked as done (kvirc: Python2 removal in sid/bullseye)
Your message dated Fri, 29 Nov 2019 12:34:33 + with message-id and subject line Bug#936810: fixed in kvirc 4:5.0.0+dfsg-2 has caused the Debian Bug report #936810, regarding kvirc: 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.) -- 936810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936810 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:kvirc Version: 4:5.0.0+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:kvirc 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: kvirc Source-Version: 4:5.0.0+dfsg-2 We believe that the bug you reported is fixed in the latest version of kvirc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrey Rahmatullin (supplier of updated kvirc 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, 29 Nov 2019 15:33:30 +0500 Source: kvirc Architecture: source Version: 4:5.0.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian KDE Extras Team Changed-By: Andrey Rahmatullin Closes: 936810 Changes: kvirc (4:5.0.0+dfsg-2) unstable; urgency=medium . * Switch bindings to Python 3 (Closes: #936810). * Bump Standards-Version to 4.4.1 (no change needed). Checksums-Sha1: ef820fa10cb31c9f75508fc6d127757f521ec40b 2600 kvirc_5.0.0+dfsg-2.dsc ac413d9c5c70cd811768d94564844fad07e6a131 26896 kvirc_5.0.0+dfsg-2.debian.tar.xz 8bcdf5560caeda30f1c68ae7b42c8e013fe36129 22613 kvirc_5.0.0+dfsg-2_amd64.buildinfo Checksums-Sha256: ffb7240f8635d414284946454fde2eab6e02862d3e6c75f05026af5eacd188e3 2600 kvirc_5.0.0+dfsg-2.dsc 455991ef829b95ec6f04fc1a9f52e86c0768a2665349ed64c2a1864707a29a49 26896 kvirc_5.0.0+dfsg-2.debian.tar.xz 3dc657f3f43ce374214a62840bc1bee99012bd791fc8a402a40f84c207ea6d0a 22613 kvirc_5.0.0+dfsg-2_amd64.buildinfo Files: 843c
Processed: Re: [Pkg-rust-maintainers] Bug#945542: debcargo -- Randomly adds and removes binary packages
Processing control commands: > severity -1 normal Bug #945542 [debcargo] Rust packages add and remove binary packages Severity set to 'normal' from 'serious' > tags -1 + wontfix unreproducible Bug #945542 [debcargo] Rust packages add and remove binary packages Added tag(s) unreproducible and wontfix. -- 945542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945542: [Pkg-rust-maintainers] Bug#945542: debcargo -- Randomly adds and removes binary packages
Control: severity -1 normal Control: tags -1 + wontfix unreproducible Bastian Blank: > Hi Ximin > > On Tue, Nov 26, 2019 at 10:25:51PM +, Ximin Luo wrote: >> Control: severity -1 normal > > Please stop fiddling with severities. > The maintainer of a package decides the severities and whether things are bugs or not. Neither have you provided a justification for "serious", it is not breaking anything. >> The more precise reason, as I have explained many times already, is because >> the cargo package manager supports crates having optional dependencies. It >> is not feasible to automatically merge optional-dependency-sets together >> because it results in dependency loops that would not otherwise exist. It is >> not economically feasible to manually merge these sets together either, >> because it is boring and time-consuming work, error-prone (hard to manually >> tell if you did or did not introduce a cycle) and of questionable benefit. > > Yes, I got that. And it seems cargo does not support recursive > dependencies. > > However Debian does not use cargo, it uses dpkg and apt. apt and dpkg > actually support recursive dependencies. Due to some downsides in > regards of the handling of maintainer scripts they are discuraged. But > as long as you don't have any of those, which all those packages don't > have, that's not much of a problem. > Manual cost, nobody is going to want to do this work. Do you want to do this work? >> I do not see any users complaining about this behaviour of our automatic >> tooling. We would be happy to work towards a patch on any Debian >> infrastructure to make these processes smoother. There is no reason why >> adding and removing empty metadata-only packages should require manual >> oversight, and if one is (and one should be) interested in automating the >> amount of manual work involved in maintaining Debian infrastructure, this is >> one obvious tedious task to automate away. > > Sylvestre as rust team member asked the ftp team, which is responsible > for the archive content, to change their handling of binary-NEW. So you > expect the ftp team to do the work you don't want to do. > > This bug is about members of the ftp team asking you to change your > solution to that problem. Re-iterating why it's not possible does not > help. > >> We are all volunteers, there is no "job security" here, why are we manually >> reviewing empty packages and we are we trying to conserve a process that >> involves manually reviewing empty packages? > > Because the ftp team is responsible for the content of the archive, > including package names etc. > Your proposed solution involves us doing more manual work, our suggested solution involves you doing less manual work. So, no thanks. X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git
Bug#945827: ssvnc: fix libvncclient bundle security issues
Package: ssvnc Severity: grave X-Debbugs-CC: t...@security.debian.org Version: 1.0.29-4 Tags: security patch The following vulnerabilites have recently been discovered in ssvnc's bundled (and rather old) version of libvncclient code: CVE-2018-20020[0]: | LibVNC before commit 7b1ef0ffc4815cab9a96c7278394152bdc89dc4d contains | heap out-of-bound write vulnerability inside structure in VNC client | code that can result remote code execution CVE-2018-20021[1]: | LibVNC before commit c3115350eb8bb635d0fdb4dbbb0d0541f38ed19c contains | a CWE-835: Infinite loop vulnerability in VNC client code. | Vulnerability allows attacker to consume excessive amount of resources | like CPU and RAM CVE-2018-20022[2]: | LibVNC before 2f5b2ad1c6c99b1ac6482c95844a84d66bb52838 contains | multiple weaknesses CWE-665: Improper Initialization vulnerability in | VNC client code that allows attacker to read stack memory and can be | abuse for information disclosure. Combined with another vulnerability, | it can be used to leak stack memory layout and in bypassing ASLR CVE-2018-20024[3]: | LibVNC before commit 4a21bbd097ef7c44bb000c3bd0907f96a10e4ce7 contains | null pointer dereference in VNC client code that can result DoS. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. As I have worked on a fix for these issues for ssvnc in Debian jessie LTS (with my LTS team member hat on, that is), I have attached the proposed .debdiff (that applies against ssvnc 1.0.29-2) to this mail. It should be easy to forward-port the security fixes to ssvnc in stretch, buster and testing/unstable. Regarding the upload to jessie LTS, please let me know, if I can proceed with the upload asap or if you want to take a closer look at the proposed changeset. Thanks. Regards, Mike For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-20020 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20020 [1] https://security-tracker.debian.org/tracker/CVE-2018-20021 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20021 [2] https://security-tracker.debian.org/tracker/CVE-2018-20022 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20022 [3] https://security-tracker.debian.org/tracker/CVE-2018-20024 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20024 -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de diff -Nru ssvnc-1.0.29/debian/changelog ssvnc-1.0.29/debian/changelog --- ssvnc-1.0.29/debian/changelog 2011-11-11 08:11:09.0 +0100 +++ ssvnc-1.0.29/debian/changelog 2019-11-29 12:15:33.0 +0100 @@ -1,3 +1,15 @@ +ssvnc (1.0.29-2+deb8u1) jessie-security; urgency=medium + + * Non-maintainer upload by the LTS team. + * Porting of libvncclient security patches: +- CVE-2018-20020: heap out-of-bound write vulnerability inside structure + in VNC client code. +- CVE-2018-20021: CWE-835: Infinite loop vulnerability in VNC client code. +- CVE-2018-20022: CWE-665: Improper Initialization vulnerability. +- CVE-2018-20024: null pointer dereference that can result DoS. + + -- Mike Gabriel Fri, 29 Nov 2019 12:15:33 +0100 + ssvnc (1.0.29-2) unstable; urgency=low * Also get CPPFLAGS from dpkg-buildflags. Pass it as EXTRA_DEFINES to diff -Nru ssvnc-1.0.29/debian/patches/libvncclient_CVE-2018-20020.patch ssvnc-1.0.29/debian/patches/libvncclient_CVE-2018-20020.patch --- ssvnc-1.0.29/debian/patches/libvncclient_CVE-2018-20020.patch 1970-01-01 01:00:00.0 +0100 +++ ssvnc-1.0.29/debian/patches/libvncclient_CVE-2018-20020.patch 2019-11-29 12:15:33.0 +0100 @@ -0,0 +1,22 @@ +Description: CVE-2018-20020 + heap out-of-bound write vulnerability inside structure in VNC client code that + can result remote code execution +--- + +Author: Abhijith PA +Origin: https://github.com/LibVNC/libvncserver/commit/7b1ef0ffc4815cab9a96c7278394152bdc89dc4d +Bug: https://github.com/LibVNC/libvncserver/issues/250 +Bug-Debian: https://bugs.debian.org/916941 +Last-Update: 2018-12-23 + +--- a/vnc_unixsrc/vncviewer/corre.c b/vnc_unixsrc/vncviewer/corre.c +@@ -76,7 +76,7 @@ + FillRectangle(rx, ry, rw, rh, gcv.foreground); + #endif + +-if (!ReadFromRFBServer(buffer, hdr.nSubrects * (4 + (BPP / 8 ++if (hdr.nSubrects > BUFFER_SIZE / (4 + (BPP / 8)) || !ReadFromRFBServer(buffer, hdr.nSubrects * (4 + (BPP / 8 + return False; + + ptr = (CARD8 *)buffer; diff -Nru ssvnc-1.0.29/debian/patches/libvncclient_CVE-2018-20021.patch ssvnc-1.0.29/debian/patches/libvncclient_CVE-2018-20021.patch --- ssvnc-1.0.29/debian/patches/libvncclient_CVE-2018-20021.patch
Bug#944944: marked as done (python-kyotocabinet: needs an explicit build dependency on dh-python)
Your message dated Fri, 29 Nov 2019 11:04:22 + with message-id and subject line Bug#944944: fixed in python-kyotocabinet 1.22-3 has caused the Debian Bug report #944944, regarding python-kyotocabinet: needs an explicit build dependency on dh-python 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.) -- 944944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-kyotocabinet Version: 1.22-2 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python. --- End Message --- --- Begin Message --- Source: python-kyotocabinet Source-Version: 1.22-3 We believe that the bug you reported is fixed in the latest version of python-kyotocabinet, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 944...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Graham Inggs (supplier of updated python-kyotocabinet 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, 29 Nov 2019 10:20:56 + Source: python-kyotocabinet Architecture: source Version: 1.22-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Graham Inggs Closes: 735302 944944 Changes: python-kyotocabinet (1.22-3) unstable; urgency=medium . * Team upload . [ Shawn Landden ] * Fix typo in python3-kyotocabinet-dbg description * Drop custom compression settings from debian/rules * Mark packages Multi-arch: same . [ Graham Inggs ] * Move VCS to DPMT on Salsa (Closes: #735302) * Add build dependency on dh-python (Closes: #944944) * Drop obsolete DM-Upload-Allowed field * Drop ancient X-Python3-Version * Remove Priority for python3-kyotocabinet-dbg * Switch to debhelper 12 * Set Rules-Requires-Root: no * Remove trailing whitespace from debian/changelog * Use HTTPS for upstream URLs * Enable all hardening build flags * Bump Standards-Version to 4.4.1, no changes Checksums-Sha1: 744a074d40cc38a2ab7e4832667638ccdb45b50a 2191 python-kyotocabinet_1.22-3.dsc b7dbdfede5ab302ed3b3b1f0ece6b6d39b0543de 3664 python-kyotocabinet_1.22-3.debian.tar.xz Checksums-Sha256: 7f973a09ad6e3ab99359b879c03cb5f5782d15dbe9b5dcff69b228f5400e96db 2191 python-kyotocabinet_1.22-3.dsc 62b411c8026c9ac61b848fbe2f1359bacd1ad0b16b98c882c2c237068ec8a20d 3664 python-kyotocabinet_1.22-3.debian.tar.xz Files: c8943ea96e3721e6fe9063bb5ffaf149 2191 devel optional python-kyotocabinet_1.22-3.dsc af309c27713a349b7c1376f87bde8018 3664 devel optional python-kyotocabinet_1.22-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAl3g93YACgkQr8/sjmac 4cI2vhAAs2ewp5VidQq5y68UUM3sYZjBGhh52sQab0zGIdNpXDh8LeTx2UM7Pkyy uMDDieKk5ocV84Ztd/p2Vg6bwBPwubCSJLcALdFM8g8UvJeqpQBssD00r376+Udo 7lKtQxIppGuYjnYEut7TeiUQc1zfPG7A/aiXaUdtw11gvKyRomSgKivu7PkR3n27 sD0KoGn6nZQrO9LX27XlV+WzKGbghMzBQBffiJf3QyAfy29KmPKuOIzp5QYDRDB7 IRUPx+uaufNT3uglDaXAazJACkGLZuswpwypShbg5yjc3BbmpT64EyIlApaCME04 MzXNpibO/Pa8eAvTWHI2RtnlMuaNLElvN005sbq9enWRTtN5aeCbOy0l2URAXQ4t 4E3bM+YAK5qct6a5IPb42fRfO5LpyAE48qKuR38/CXI+/9MacSK8+uIOYTtHeahB IcAM8nJN23NVEfoEbNPAPXJ+TuabmIcgKmStUhoiKh6aCD6OocSRCLcqDWYO76VY eohni8vtzpMhKcEPPAMET1excibtUQgqaEbcDKw2DeHRPLTTo7RtlD7lFHeuRElk QUw1IlKgNRiOUKcJm36j8n4+ctg4ngssUec4tcLCSiMS0DdCpHDZy9Me8JTCKKGZ BPkPGGdqNbmIEi0f9GCKQYkGkdCMPohzjkfGIEHTT3yB8gGeV0s= =vfj5 -END PGP SIGNATURE End Message ---
Bug#945796: [Pkg-rust-maintainers] Bug#945796: rust-url-serde: (build-)depends on obsolete virtual package.
Wolfgang Silbermayr wrote on 29/11/2019: > On 11/28/19 9:04 PM, peter green wrote: >> Package: rust-url-serde >> Version: 0.2.0-1 >> Severity: serious >> Tags: bullseye, sid >> >> librust-url-serde-dev depends on and rust-url-serde build-depends on >> librust-url-1+default-dev which is no longer provided by rust-url. It >> seems to have been replaced by librust-url-2+default-dev > > The url_serde crate has been updated the last time to 0.2.0 on April 30, > 2017. It lived in the servo rust-url repository, where it got removed on > July 15, 2019. To me it seems to be obsolete. Nothing (build-)depends on > it yet. I assume it got packaged as a dependency for something else, but > either that something didn't get packaged yet, or it doesn't require > this crate any more. > > @paride can you please check and file a ROM if no longer needed? Hi Wolfgang, I packaged url-serde as it was a (possibly indirect) dependency of another rust package, but at the moment I can't recall of which one exactly, most likely fd-find or bat. It seems that is has been dropped as a dependency; I will check later today or over the weekend and file a removal request for the ftpmasters. Paride
Processed: tagging 945742, tagging 945686, tagging 945660, found 935209 in 0.4.4-1, tagging 935209 ...
Processing commands for cont...@bugs.debian.org: > tags 945742 + experimental Bug #945742 [src:urjtag] urjtag: Python2 removal in sid/bullseye Added tag(s) experimental. > tags 945686 + experimental Bug #945686 [src:petsc4py] petsc4py: Python2 removal in sid/bullseye Added tag(s) experimental. > tags 945660 + experimental Bug #945660 [src:llvm-defaults] llvm-defaults: Python2 removal in sid/bullseye Added tag(s) experimental. > found 935209 0.4.4-1 Bug #935209 [servefile] servefile: Please port to Python 3 and/or drop Python 2 package Marked as found in versions servefile/0.4.4-1. > tags 935209 + sid bullseye Bug #935209 [servefile] servefile: Please port to Python 3 and/or drop Python 2 package Added tag(s) sid and bullseye. > found 935208 1.4.8-4.4 Bug #935208 [spkproxy] spkproxy: Please port to Python 3 and/or drop Python 2 package There is no source info for the package 'spkproxy' at version '1.4.8-4.4' with architecture '' Unable to make a source version for version '1.4.8-4.4' Marked as found in versions 1.4.8-4.4. > tags 935208 + sid bullseye Bug #935208 [spkproxy] spkproxy: Please port to Python 3 and/or drop Python 2 package Added tag(s) bullseye and sid. > tags 938709 + experimental Bug #938709 [src:trac-tags] trac-tags: Python2 removal in sid/bullseye Added tag(s) experimental. > found 935212 0.1.8-2 Bug #935212 [python-apns-client] python-apns-client: Please port to Python 3 and/or drop Python 2 package Marked as found in versions python-apns-client/0.1.8-2. > tags 935212 + sid bullseye Bug #935212 [python-apns-client] python-apns-client: Please port to Python 3 and/or drop Python 2 package Added tag(s) bullseye and sid. > found 945775 0.3.1-1.1 Bug #945775 [python-sponge] python-sponge: should this package be removed. Marked as found in versions python-sponge/0.3.1-1.1. > tags 945775 + sid bullseye Bug #945775 [python-sponge] python-sponge: should this package be removed. Added tag(s) bullseye and sid. > found 945542 2.2.10-1 Bug #945542 [debcargo] Rust packages add and remove binary packages Marked as found in versions rust-debcargo/2.2.10-1. > tags 945542 + sid bullseye Bug #945542 [debcargo] Rust packages add and remove binary packages Added tag(s) sid and bullseye. > found 945802 1.2.2-6 Bug #945802 [sshfp] sshfp: should this package be removed? Marked as found in versions sshfp/1.2.2-6. > tags 945802 + sid bullseye Bug #945802 [sshfp] sshfp: should this package be removed? Added tag(s) sid and bullseye. > thanks Stopping processing here. Please contact me if you need assistance. -- 935208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935208 935209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935209 935212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935212 938709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938709 945542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945542 945660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945660 945686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945686 945742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945742 945775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945775 945802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945705: selenium-firefoxdriver: Python2 removal in sid/bullseye
Source: selenium-firefoxdriver Version: 3.14.1-1 Severity: normal Tags: sid bullseye Hi, the firefoxdriver supports only firefox version up to 52.0 and does not work with the current version of firefox anymore. That's why the removal is fine. I'm sorry, i thought that the removal is already done but for some reasons the package is still there. Regards Sascha signature.asc Description: OpenPGP digital signature
Processed: jupyter-notebook block
Processing commands for cont...@bugs.debian.org: > block 944743 by 945328 Bug #944743 [jupyter-notebook] jupyter-notebook: systemd user unit enabled by default, despite per-system TCP port 944743 was not blocked by any bugs. 944743 was not blocking any bugs. Added blocking bug(s) of 944743: 945328 > End of message, stopping processing here. Please contact me if you need assistance. -- 944743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#944548: marked as done (visp ftbfs on armel/armhf where it built before)
Your message dated Fri, 29 Nov 2019 09:04:56 + with message-id and subject line Bug#944548: fixed in visp 3.2.0-2 has caused the Debian Bug report #944548, regarding visp ftbfs on armel/armhf where it built before 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.) -- 944548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:visp Version: 3.2.0-1 Severity: serious Tags: sid bullseye visp ftbfs on armel/armhf where it built before /<>/modules/ar/src/coin-simulator/vpViewer.cpp:93:9: error: ‘glDrawPixels’ was not declared in this scope; did you mean ‘glReadPixels’? 93 | glDrawPixels((GLsizei)simu->getInternalWidth(), (GLsizei)simu->getInternalHeight(), (GLenum)GL_LUMINANCE, | ^~~~ | glReadPixels /<>/modules/ar/src/coin-simulator/vpViewer.cpp:96:9: error: ‘glDrawPixels’ was not declared in this scope; did you mean ‘glReadPixels’? 96 | glDrawPixels((GLsizei)simu->getInternalWidth(), (GLsizei)simu->getInternalHeight(), (GLenum)GL_RGB, | ^~~~ | glReadPixels /<>/modules/ar/src/coin-simulator/vpViewer.cpp:101:7: error: ‘glClearDepth’ was not declared in this scope; did you mean ‘glClearDepthf’? 101 | glClearDepth(100.0); // Profondeur du Z-Buf | ^~~~ | glClearDepthf --- End Message --- --- Begin Message --- Source: visp Source-Version: 3.2.0-2 We believe that the bug you reported is fixed in the latest version of visp, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 944...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabien Spindler (supplier of updated visp 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: Thu, 28 Nov 2019 12:37:06 +0100 Source: visp Architecture: source Version: 3.2.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Fabien Spindler Closes: 944548 Changes: visp (3.2.0-2) unstable; urgency=medium . * Mute lintian warning privacy-breach-generic * Remove useless SoQt 3rd party usage (Closes: #944548) * Upgrade debhelper compat version as suggested by lintian Checksums-Sha1: 6de2564f8945c351e0b8d023aadf9270dd4c9772 4540 visp_3.2.0-2.dsc b0ccf53ee02fbc227b96f43c99f885ec517ba9af 15388 visp_3.2.0-2.debian.tar.xz 1a63f5e7466bc3dd3f799c2a823b9519b5626ee3 34020 visp_3.2.0-2_amd64.buildinfo Checksums-Sha256: 3eeb85f941e0ca1010af5dcc2a01fdc4c9a247c2e4395737552e5fd373317e83 4540 visp_3.2.0-2.dsc 3128bdd4072b46e72d056ef001a03b7597bbc8a183002ed8fcbd6daa377cb063 15388 visp_3.2.0-2.debian.tar.xz f8230061258e282bcdaf7c4353d1c01a5ae0c391aa20e82227b446704993133e 34020 visp_3.2.0-2_amd64.buildinfo Files: 8070f68d3b8ab788a15815ea1a84244f 4540 devel optional visp_3.2.0-2.dsc a994b5b5a95550ce2f9486c982d9f175 15388 devel optional visp_3.2.0-2.debian.tar.xz d738dd419c57dbe319233b5fe22a40ac 34020 devel optional visp_3.2.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCAAxFiEEX7Rvg9O5UgRjNdJteNxo2zJthDgFAl3g1+sTHG9zYWxsb3VA ZGViaWFuLm9yZwAKCRB43GjbMm2EODKGD/9EBVTjdgAb0hd77kqJfxAxCUS6Mpq/ sahc3WpCUl1gjoDW6oOsC6qfMXC9GXy+yKV3RopYKP5Wvkj/hIFSSIlImTPui7fj tWmZQssmQ2q3AsNiHy/oGoxoSMsZBL6jLK8GPXLScaaCEByXwi025Kb3PdhmYYZD na2UoMmsHwj/giLuF01I8SmzBOOR8kMnPh9Xs3pRjJh3GkdD8BueyBgMFW+ji4bD 9IuXt0i+6Ig21gdOXO/TGsCLOpQ+TxULwbCFY0hqzBfo5frBKzpmkcRu9sDpDGCw ARMj96L9gxby4ZenHbV8uzZcNgLzSGtB6ln113sXET6K3ob4c/kwBm3tPzzqJJAO II36y60l5k93PMPKAVatQwgLQ6WYXpfCt/frSgNm8dJYrPtXh7il1iGcOHyGyU9W X+cjKZ018nDQLJK8ESNFHVDAJ3vcPvqo+yg/x+wja89riKsdzHxYXxa8wmjHKoB6 iKh+y0ji2WrznUO9KIBuXArvLXlih0pxSD+o9O40I91pD3buAOB3zgr2NalOIKXW 0V/ec4om31Ng6t1uAFtsLJGgn0sNdLhG/VP3ANx+suRp6p09kpW5ZDVIn0RdOzju YXQ07flSc//pmHXAiS+/pn7tLeRtMsNznLj/WA3XAfIl7DoGQQHt1BvJhxfNyLBl JDxOuzrbvh/67g== =GLoB -END PGP SIGNATURE End Message ---
Bug#945542: debcargo -- Randomly adds and removes binary packages
Hi Ximin On Tue, Nov 26, 2019 at 10:25:51PM +, Ximin Luo wrote: > Control: severity -1 normal Please stop fiddling with severities. > The more precise reason, as I have explained many times already, is because > the cargo package manager supports crates having optional dependencies. It is > not feasible to automatically merge optional-dependency-sets together because > it results in dependency loops that would not otherwise exist. It is not > economically feasible to manually merge these sets together either, because > it is boring and time-consuming work, error-prone (hard to manually tell if > you did or did not introduce a cycle) and of questionable benefit. Yes, I got that. And it seems cargo does not support recursive dependencies. However Debian does not use cargo, it uses dpkg and apt. apt and dpkg actually support recursive dependencies. Due to some downsides in regards of the handling of maintainer scripts they are discuraged. But as long as you don't have any of those, which all those packages don't have, that's not much of a problem. > I do not see any users complaining about this behaviour of our automatic > tooling. We would be happy to work towards a patch on any Debian > infrastructure to make these processes smoother. There is no reason why > adding and removing empty metadata-only packages should require manual > oversight, and if one is (and one should be) interested in automating the > amount of manual work involved in maintaining Debian infrastructure, this is > one obvious tedious task to automate away. Sylvestre as rust team member asked the ftp team, which is responsible for the archive content, to change their handling of binary-NEW. So you expect the ftp team to do the work you don't want to do. This bug is about members of the ftp team asking you to change your solution to that problem. Re-iterating why it's not possible does not help. > We are all volunteers, there is no "job security" here, why are we manually > reviewing empty packages and we are we trying to conserve a process that > involves manually reviewing empty packages? Because the ftp team is responsible for the content of the archive, including package names etc. Regards, Bastian -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0
Bug#945820: sysvinit_2.96-2_amd64.changes REJECTED
Source: sysvinit Version: 2.96-2 Severity: serious On 2019-11-28 22:04, Debian FTP Masters wrote: > > > sysvinit-core_2.96-2_amd64.deb: has 2 file(s) with a timestamp too far in the > past: > usr/share/doc/sysvinit-core/copyright (Thu Jan 1 00:00:01 1970) > usr/share/doc/sysvinit-core/changelog.Debian.gz (Thu Jan 1 00:00:01 1970) > > > > === > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > > -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#874880: [freemedforms-project] Future Qt4 removal from Buster
On Fri, Nov 29, 2019 at 08:08:05AM +0100, Eric Maeker wrote: > Ok, I already spent three hours yesterday to run a Debian at home. > I'm not able to have my old macbook 5,1 running Debian 10 for now. Jessie > was working perfectly... Even a Jessie machine could do fine if you are using a pbuilder environment with unstable. > For the patch, it is include in my previous mail (not a patch file as I do > not have a working Debian). > > Le ven. 29 nov. 2019 à 06:09, Andreas Tille a écrit : > > > > Nevertheless, can you try to add > > > #include > > > in the > > > servercreation/servercreationwidget.cpp > > > This should do the trick. This actually brought me over this hurdle. Thanks a lot. Unfortunately I'm running into: ... g++ -c -pipe -g -O2 -fdebug-prefix-map=/build/freemedforms-project-1.0.0=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT -Wall -W -fPIC -DFREEMEDFORMS - DWITH_AGENDA -DWITH_ALERTS -DWITH_FEEDBACK -DWITH_PAD -DWITH_PMH -DWITH_PATIENTIMPORT -DDRUGS_DATABASE_VERSION=0x000804 -DWITH_EPISODE_REMOVAL -DWITH_CHEQUE_PRINTING -DWITH_FRENCH_FSP - DWITH_FRENCH_HPRIM_INTEGRATOR -DFULLAPPLICATION_BUILD -DBINARY_NAME="\"Core\"" -DBUILD_PATH_POSTFIXE="\"FreeMedForms\"" -DPACKAGE_VERSION="\"1.0.0\"" -DSOURCES_ROOT_PATH="\"/build/freemedforms-project-1.0. 0\"" -DLINUX_INTEGRATED -DLINUX_QT_PATH="\"/usr/lib/x86_64-linux-gnu\"" -DLINUX_QT_PLUGINS_PATH="\"/usr/lib/x86_64-linux-gnu/qt5/plugins\"" -DLIBRARY_BASENAME="\"lib/x86_64-linux-gnu\"" -DLINUX_PLUGIN_PATH="\"/usr//lib/x86_64-linux-gnu/Core\"" -DGIT_REVISION_HASH="\"DEBR1.0.0-1\"" -DQT_NO_CAST_TO_ASCII -DQT_USE_FAST_OPERATOR_PLUS -DQT_USE_FAST_CONCATENATION -DRELEASE -DQT_DISABLE_DEPRECATED_BEFORE=0x040900 - DCORE_LIBRARY -DQT_NO_DEBUG -DQT_PLUGIN -DQT_SVG_LIB -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CONCURRENT_LIB -DQT_SQL_LIB -DQT_XML_LIB -DQT_NETWORK_LIB -DQT_SCRIPT_LIB -DQT_CORE_LIB -I. -I/ build/freemedforms-project-1.0.0/plugins -I/build/freemedforms-project-1.0.0/libs -I/build/freemedforms-project-1.0.0/contrib -I/build/freemedforms-project-1.0.0/contrib/quazip -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/x86_64-linux- gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem /usr/include/x86_64-linux-gnu/qt5/QtSql -isystem /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem /usr/include/x86_64-linux-gnu/ qt5/QtNetwork -isystem /usr/include/x86_64-linux-gnu/qt5/QtScript -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -I/build/freemedforms-project-1.0.0/build/Qt5_linux-gpp/FreeMedForms/Core/.moc -isystem /usr/ include/libdrm -I/build/freemedforms-project-1.0.0/build/Qt5_linux-gpp/FreeMedForms/.ui -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o /build/freemedforms-project-1.0.0/build/Qt5_linux-gpp/FreeMedForms/ Core/.obj/unix/commondebugpages.o /build/freemedforms-project-1.0.0/plugins/coreplugin/dialogs/commondebugpages.cpp /build/freemedforms-project-1.0.0/plugins/coreplugin/dialogs/commonaboutpages.cpp: At global scope: /build/freemedforms-project-1.0.0/plugins/coreplugin/dialogs/commonaboutpages.cpp:176:17: error: no matching function for call to 'Team::Team(QString, QString, const char [17], QString)' 176 | ) | ^ /build/freemedforms-project-1.0.0/plugins/coreplugin/dialogs/commonaboutpages.cpp:113:5: note: candidate: 'Team::Team(const QString&, const QString&, const QString&, const QString&, const QString&)' 113 | Team( const QString &cat, const QString& n, const QString& p, const QString& e, const QString& c ) | ^~~~ /build/freemedforms-project-1.0.0/plugins/coreplugin/dialogs/commonaboutpages.cpp:113:5: note: candidate expects 5 arguments, 4 provided /build/freemedforms-project-1.0.0/plugins/coreplugin/dialogs/commonaboutpages.cpp:111:8: note: candidate: 'Team::Team(const Team&)' 111 | struct Team |^~~~ /build/freemedforms-project-1.0.0/plugins/coreplugin/dialogs/commonaboutpages.cpp:111:8: note: candidate expects 1 argument, 4 provided /build/freemedforms-project-1.0.0/plugins/coreplugin/dialogs/commonaboutpages.cpp:111:8: note: candidate: 'Team::Team(Team&&)' /build/freemedforms-project-1.0.0/plugins/coreplugin/dialogs/commonaboutpages.cpp:111:8: note: candidate expects 1 argument, 4 provided Could you give some hint what additional argument might be needed? I'm fine with iterating over this kind of issues if you can give hints for a patch and I'll try it here. Kind regards Andreas. -- http://fam-tille.de
Bug#945244: marked as done (r-cran-sf: upstream regression, unaligned access on armhf)
Your message dated Fri, 29 Nov 2019 08:43:50 +
with message-id
and subject line Bug#945244: fixed in r-cran-sf 0.8-0+dfsg-3
has caused the Debian Bug report #945244,
regarding r-cran-sf: upstream regression, unaligned access on armhf
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
945244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945244
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-sf
Version: 0.8-0+dfsg-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal
Hi Andreas,
With the upload of r-cran-sf 0.8-0+dfsg-1, the autopkgtests are failing in
Ubuntu only on armhf due to a regression in alignment handling:
[...]
Attribute-geometry relationship: 0 constant, 1 aggregate, 1 identity
geometry type: MULTIPOLYGON
dimension: XY
bbox: xmin: 0 ymin: 0 xmax: 1 ymax: 1
epsg (SRID):NA
proj4string:NA
Group.1 a geometry
1 1 1.5 MULTIPOLYGON (((0 0, 1 0, 1...
> (a = aggregate(s, list(c(1,1)), mean, do_union = TRUE))
Bus error (core dumped)
autopkgtest [11:32:17]: test run-unit-test: ---]
[...]
(https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/armhf/r/r-cran-sf/20191109_113707_4303b@/log.gz)
Since Debian only runs autopkgtests on amd64, this did not block migration
of the new version of the package to Debian testing; nevertheless this is a
serious failure of the package on armhf. I have grabbed a backtrace which
points to a problem in r-cran-sf itself, not in any of its dependencies:
Program received signal SIGBUS, Bus error.
0xf47431cc in wkb_read (wkb=, wkb=)
at wkb.cpp:201
201 double d = wkb_read(wkb);
(gdb) bt
#0 0xf47431cc in wkb_read (wkb=, wkb=)
at wkb.cpp:201
#1 read_numeric_matrix (wkb=wkb@entry=0xfffe7ddc, n_dims=n_dims@entry=2,
swap=swap@entry=false, cls=..., empty=empty@entry=0x0) at wkb.cpp:201
#2 0xf47434b0 in read_matrix_list (wkb=wkb@entry=0xfffe7ddc,
n_dims=n_dims@entry=2, swap=swap@entry=false, cls=...,
empty=empty@entry=0xfffe7d27) at /usr/include/c++/9/ext/new_allocator.h:89
#3 0xf474430c in read_data (wkb=wkb@entry=0xfffe7ddc, EWKB=EWKB@entry=true,
spatialite=spatialite@entry=false, endian=endian@entry=1,
addclass=addclass@entry=true, type=type@entry=0xfffe7dd4,
srid=srid@entry=0xfffe7dd8)
at /usr/lib/R/site-library/Rcpp/include/Rcpp/vector/generic_proxy.h:37
#4 0xf474590a in CPL_read_wkb (wkb_list=..., EWKB=EWKB@entry=true,
spatialite=spatialite@entry=false)
at /usr/lib/R/site-library/Rcpp/include/Rcpp/vector/generic_proxy.h:37
#5 0xf472d5da in sfc_from_geometry(GEOSContextHandle_HS*,
std::vector >,
std::allocator >
> >&, int, bool) (
hGEOSCtxt=hGEOSCtxt@entry=0x2154c48,
geom=std::vector of length 1, capacity 1 = {...}, dim=,
free=free@entry=true)
at /usr/lib/R/site-library/Rcpp/include/Rcpp/vector/traits.h:65
#6 0xf472f542 in CPL_geos_union (sfc=..., by_feature=)
at geos.cpp:600
#7 0xf47100d8 in _sf_CPL_geos_union (sfcSEXP=0x1f0d988,
by_featureSEXP=0x419568)
at /usr/lib/R/site-library/Rcpp/include/Rcpp/as.h:151
#8 0xf7ce238c in ?? () from /usr/lib/R/lib/libR.so
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: r-cran-sf
Source-Version: 0.8-0+dfsg-3
We believe that the bug you reported is fixed in the latest version of
r-cran-sf, 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 945...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated r-cran-sf package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 29 Nov 20
Bug#945817: dolfin: FTBFS on mips64el
Source: dolfin Version: 2019.1.0-8 Severity: serious Tags: sid ftbfs Hi Maintainer Recent builds of dolfin have been failing on mips64el [1] in unstable, where it built previously. Regards Graham [1] https://buildd.debian.org/status/logs.php?pkg=dolfin&arch=mips64el
Processed: Re: Bug#945542: debcargo -- Randomly adds and removes binary packages
Processing control commands: > severity -1 serious Bug #945542 [debcargo] Rust packages add and remove binary packages Severity set to 'serious' from 'normal' -- 945542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Patch & NMU suggestion
Processing commands for cont...@bugs.debian.org: > tags 936678 + patch Bug #936678 [src:gumbo-parser] gumbo-parser: Python2 removal in sid/bullseye Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 936678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936678 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#936678: Patch & NMU suggestion
tags 936678 + patch thanks Hi Onur, I'd like to suggest a patch which removes the Python 2 support from gumbo-parser. It contains minimal changes I came up with to remove Python 2 and leave anything untouched. If you don't mind, I could do NMU with this patch. Cheers! -- Sergei Golovan
Bug#936678: Attachment
Hi Onur, Actually attaching the patch. Cheers! -- Sergei Golovan gumbo-parser_0.10.1+dfsg-2.4.diff Description: Binary data
