Processed: severity of 936505 is normal
Processing commands for cont...@bugs.debian.org: > severity 936505 normal Bug #936505 [src:faulthandler] faulthandler: Python2 removal in sid/bullseye Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 936505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948449: marked as done (garmin-plugin might be useless now)
Your message dated Sun, 12 Jan 2020 06:53:27 + with message-id and subject line Bug#948693: Removed package(s) from unstable has caused the Debian Bug report #948449, regarding garmin-plugin might be useless now 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.) -- 948449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: garmin-plugin Version: 0.3.23-5 Severity: serious This package provides an NPAPI plugin. All major browsers have dropped support for NPAPI. --- End Message --- --- Begin Message --- Version: 0.3.23-6+rm Dear submitter, as the package garmin-plugin has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/948693 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#948160: marked as done (RM: python-id3 -- RoQA; python2-only; no upstream update in years; similar functionalities from mutagen)
Your message dated Sun, 12 Jan 2020 06:49:41 + with message-id and subject line Bug#948160: Removed package(s) from unstable has caused the Debian Bug report #948160, regarding RM: python-id3 -- RoQA; python2-only; no upstream update in years; similar functionalities from mutagen 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.) -- 948160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-id3 Severity: serious Hello, recently python-id3 became a leaf package; ID3 is python2-only, and upstream hasnt updated this project in years; it looks like mutagen has the same functionality of python-id3, so i believe we can safely remove python-id3 from Debian without losing funtionalities. If i dont hear back within a week with a good reason to keep this package in Debian, i'll file for its removal. Regards, Sandro -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 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= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python-id3 depends on: ii python 2.7.16-1 python-id3 recommends no packages. python-id3 suggests no packages. --- End Message --- --- Begin Message --- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: python-id3 |1.2-6.3 | source, all --- Reason --- RoQA; python2-only; no upstream update in years; similar functionalities from mutagen -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 948...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/948160 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#937825: marked as done (python-id3: Python2 removal in sid/bullseye)
Your message dated Sun, 12 Jan 2020 06:49:46 + with message-id and subject line Bug#948160: Removed package(s) from unstable has caused the Debian Bug report #937825, regarding python-id3: 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.) -- 937825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937825 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-id3 Version: 1.2-6.3 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-id3 If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.2-6.3+rm Dear submitter, as the package python-id3 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/948160 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#937244: marked as done (paste: Python2 removal in sid/bullseye)
Your message dated Sun, 12 Jan 2020 04:49:16 + with message-id and subject line Bug#937244: fixed in paste 3.2.4+dfsg1-2 has caused the Debian Bug report #937244, regarding paste: 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.) -- 937244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937244 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:paste Version: 3.1.0+dfsg1-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:paste 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: paste Source-Version: 3.2.4+dfsg1-2 We believe that the bug you reported is fixed in the latest version of paste, 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 paste package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 11 Jan 2020 23:23:53 -0500 Source: paste Architecture: source Version: 3.2.4+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Sandro Tosi Closes: 937244 Changes: paste (3.2.4+dfsg1-2) unstable; urgency=medium . * Team upload. * Drop python2 support; Closes: #937244 Checksums-Sha1: 1375b4f95b969a32e53825ac841135d0881a44bb 2188 paste_3.2.4+dfsg1-2.dsc d8292de1d02b00302777c4305453e3edf838996e 8176 paste_3.2.4+dfsg1-2.debian.tar.xz ef2a81bbc46a84f90c9d974b25d964de103a817b 6095 paste_3.2.4+dfsg1-2_source.buildinfo Checksums-Sha256: eb29d87ee5c66896fd8d9d25bbe534cffa7bffbdfa0126be82ceec21625749d6 2188 paste_3.2.4+dfsg1-2.dsc dacdfde9f1a68cca4e546d2a9a732524ff8b84ef7256e45ef22a0a2b18efc53d 8176 paste_3.2.4+dfsg1-2.debian.tar.xz 6313a9988e54188ef1fe95fcd5893a59ce19bb7efe589bbc19a5c1e938b8ee7b 6095 paste_3.2.4+dfsg1-2_source.buildinfo Files: 857bb2bbf4b31a1a90dcbad09620220e 2188 python optional paste_3.
Bug#937244: marked as pending in paste
Control: tag -1 pending Hello, Bug #937244 in paste reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/paste/commit/4ed6b15ddd69ba0189d7a2a6b023fec3746d4217 Drop python2 support; Closes: #937244 (this message was generated automatically) -- Greetings https://bugs.debian.org/937244
Processed: Bug#937244 marked as pending in paste
Processing control commands: > tag -1 pending Bug #937244 [src:paste] paste: Python2 removal in sid/bullseye Added tag(s) pending. -- 937244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937244 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: py2removal bugs severity updates - 2020-01-12 03:36:08.391963+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # and https://lists.debian.org/debian-python/2019/12/msg00076.html > # mail threads for more details on this severity update > # python-paste is a module and has 0 external rdeps or not in testing > severity 937244 serious Bug #937244 [src:paste] paste: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 937244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937244 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 946995 is grave
Processing commands for cont...@bugs.debian.org: > severity 946995 grave Bug #946995 [youtube-dl] No sound (YouTube) Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 946995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947208: Need new version
As noted in #946995, sound is stripped.
Processed: severity of 947208 is grave
Processing commands for cont...@bugs.debian.org: > severity 947208 grave Bug #947208 [youtube-dl] youtube-dl 2019.11.28 is available Severity set to 'grave' from 'wishlist' > thanks Stopping processing here. Please contact me if you need assistance. -- 947208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948533: marked as done (datalad: FTBFS in unstable)
Your message dated Sun, 12 Jan 2020 02:38:07 + with message-id and subject line Bug#948533: fixed in datalad 0.12.0-1 has caused the Debian Bug report #948533, regarding datalad: FTBFS in unstable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 948533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: datalad Version: 0.11.8-1 Severity: serious User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu focal Dear maintainers, The datalad package again fails to build in unstable: [...] == ERROR: datalad.metadata.extractors.tests.test_audio.test_audio -- Traceback (most recent call last): File "/tmp/datalad-0.11.8/.pybuild/cpython3_3.8_datalad/build/datalad/metadata/metadata.py", line 516, in _get_metadata extractor_cls = extractors[mtype_key].load() File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2442, in load self.require(*args, **kwargs) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2465, in require items = working_set.resolve(reqs, env, installer, extras=self.extras) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 786, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'distro' distribution was not found and is required by the application During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/tmp/datalad-0.11.8/.pybuild/cpython3_3.8_datalad/build/datalad/tests/utils.py", line 615, in newfunc return t(*(arg + (filename,)), **kw) File "/tmp/datalad-0.11.8/.pybuild/cpython3_3.8_datalad/build/datalad/metadata/extractors/tests/test_audio.py", line 53, in test_audio res = ds.aggregate_metadata() File "/usr/lib/python3/dist-packages/wrapt/wrappers.py", line 602, in __call__ return self._self_wrapper(self.__wrapped__, self._self_instance, File "/tmp/datalad-0.11.8/.pybuild/cpython3_3.8_datalad/build/datalad/distribution/dataset.py", line 527, in apply_func return f(**kwargs) File "/usr/lib/python3/dist-packages/wrapt/wrappers.py", line 563, in __call__ return self._self_wrapper(self.__wrapped__, self._self_instance, File "/tmp/datalad-0.11.8/.pybuild/cpython3_3.8_datalad/build/datalad/interface/utils.py", line 499, in eval_func return return_func(generator_func)(*args, **kwargs) File "/usr/lib/python3/dist-packages/wrapt/wrappers.py", line 563, in __call__ return self._self_wrapper(self.__wrapped__, self._self_instance, File "/tmp/datalad-0.11.8/.pybuild/cpython3_3.8_datalad/build/datalad/interface/utils.py", line 487, in return_func results = list(results) File "/tmp/datalad-0.11.8/.pybuild/cpython3_3.8_datalad/build/datalad/interface/utils.py", line 431, in generator_func for r in _process_results( File "/tmp/datalad-0.11.8/.pybuild/cpython3_3.8_datalad/build/datalad/interface/utils.py", line 529, in _process_results for res in results: File "/tmp/datalad-0.11.8/.pybuild/cpython3_3.8_datalad/build/datalad/metadata/aggregate.py", line 1009, in __call__ errored = _dump_extracted_metadata( File "/tmp/datalad-0.11.8/.pybuild/cpython3_3.8_datalad/build/datalad/metadata/aggregate.py", line 379, in _dump_extracted_metadata return _extract_metadata( File "/tmp/datalad-0.11.8/.pybuild/cpython3_3.8_datalad/build/datalad/metadata/aggregate.py", line 460, in _extract_metadata dsmeta, contentmeta, errored = _get_metadata( File "/tmp/datalad-0.11.8/.pybuild/cpython3_3.8_datalad/build/datalad/metadata/metadata.py", line 526, in _get_metadata raise ValueError( ValueError: Failed to load metadata extractor for 'datalad_core', broken dataset configuration ()?: The 'distro' distribution was not found and is required by the application [__init__.py:resolve:786] == The failures appear to all be related to the introduction of python3.8 as a supported python version in unstable. Please find a full build log attached. -- 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.o
Bug#946242: fatal: privsep_preauth: preauth child terminated by signal 31
On Sat, Jan 11, 2020 at 01:20:49PM +, Colin Watson wrote: > I have some other things to do this weekend, but I'll chase this up with > upstream and arrange for this to get into appropriate Debian packages. It turned out that upstream had committed a fix a few days ago [1], so I cherry-picked that into unstable and have filed a stable update request as https://bugs.debian.org/948695. [1] https://anongit.mindrot.org/openssh.git/commit/?id=30f704ebc0e9e32b3d12f5d9e8c1b705fdde2c89 -- Colin Watson [cjwat...@debian.org]
Bug#946242: marked as done (fatal: privsep_preauth: preauth child terminated by signal 31)
Your message dated Sun, 12 Jan 2020 00:19:37 + with message-id and subject line Bug#946242: fixed in openssh 1:8.1p1-5 has caused the Debian Bug report #946242, regarding fatal: privsep_preauth: preauth child terminated by signal 31 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.) -- 946242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946242 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openssh-server Version: 1:7.9p1-10+deb10u1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? apt upgrade lead to openssh-server * being unusable. * What exactly did you do (or not do) that was effective (or ineffective)? bug #941663 supposedly fixed this issue in the version I upgraded to but the symptom remains. Also tried installing 8.1 version but that did not fix the issue either. I am running a 3.16 kernel because a 4.x kernel is not supported on my hardware (AMD Geode LX processor). * What was the outcome of this action? no change * What outcome did you expect instead? to login *** End of the template - remove these template lines *** -- System Information: Debian Release: 10.2 APT prefers stable-debug APT policy: (500, 'stable-debug'), (500, 'stable') Architecture: i386 (i586) Kernel: Linux 3.16.0-4-586 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages openssh-server depends on: ii adduser3.118 ii debconf [debconf-2.0] 1.5.71 ii dpkg 1.19.7 ii libaudit1 1:2.8.4-3 ii libc6 2.28-10 ii libcom-err21.44.5-1+deb10u2 ii libgssapi-krb5-2 1.17-3 ii libkrb5-3 1.17-3 ii libpam-modules 1.3.1-5 ii libpam-runtime 1.3.1-5 ii libpam0g 1.3.1-5 ii libselinux12.8-1+b1 ii libssl1.1 1.1.1d-0+deb10u2 ii libsystemd0241-7~deb10u2 ii libwrap0 7.6.q-28 ii lsb-base 10.2019051400 ii openssh-client 1:7.9p1-10+deb10u1 ii openssh-sftp-server1:7.9p1-10+deb10u1 ii procps 2:3.3.15-2 ii ucf3.0038+nmu1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages openssh-server recommends: ii libpam-systemd [logind] 241-7~deb10u2 ii ncurses-term 6.1+20181013-2+deb10u2 ii xauth1:1.0.10-1 Versions of packages openssh-server suggests: pn molly-guard pn monkeysphere pn rssh pn ssh-askpass pn ufw -- Configuration Files: /etc/default/ssh changed: SSHD_OPTS=-4 -- debconf information: * ssh/use_old_init_script: true * openssh-server/permit-root-login: true ssh/encrypted_host_key_but_no_keygen: openssh-server/password-authentication: false ssh/vulnerable_host_keys: ssh/new_config: true ssh/disable_cr_auth: false --- End Message --- --- Begin Message --- Source: openssh Source-Version: 1:8.1p1-5 We believe that the bug you reported is fixed in the latest version of openssh, 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 946...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin Watson (supplier of updated openssh package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 11 Jan 2020 23:55:03 + Source: openssh Architecture: source Version: 1:8.1p1-5 Distribution: unstable Urgency: medium Maintainer: Debian OpenSSH Maintainers Changed-By: Colin Watson Closes: 946242 Changes: openssh (1:8.1p1-5) unstable; urgency=medium . * Apply upstream patches to allow clock_nanosleep() and variants in the seccomp sandbox, fixing failures with glibc 2.31. * Apply upstream patch to deny (non-fatally) ipc in the seccomp sandbox, fixing failures with OpenSSL 1.1.1d and Linux < 3.19 on some architectures (closes: #946242). Checksums-Sha1: 416b9a792df5167
Bug#937771: marked as done (python-fuse: Python2 removal in sid/bullseye)
Your message dated Sun, 12 Jan 2020 00:04:38 + with message-id and subject line Bug#937771: fixed in python-fuse 2:1.0.0-3 has caused the Debian Bug report #937771, regarding python-fuse: 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.) -- 937771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937771 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-fuse Version: 2:1.0.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:python-fuse 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-fuse Source-Version: 2:1.0.0-3 We believe that the bug you reported is fixed in the latest version of python-fuse, 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-fuse package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 11 Jan 2020 17:03:03 -0500 Source: python-fuse Architecture: source Version: 2:1.0.0-3 Distribution: unstable Urgency: medium Maintainer: Sebastien Delafond Changed-By: Sandro Tosi Closes: 937771 Changes: python-fuse (2:1.0.0-3) unstable; urgency=medium . * Team upload. * Drop python2 support; Closes: #937771 Checksums-Sha1: 3536e884192e48ba27cacb2106e4ed6cf3b262fc 1939 python-fuse_1.0.0-3.dsc bab69fbc1f3ab49d8935b6b9b59d573bca09e97b 4464 python-fuse_1.0.0-3.debian.tar.xz b7c26d89c4ecf2cfabccbe5075dcf106541394e4 6919 python-fuse_1.0.0-3_source.buildinfo Checksums-Sha256: b147fc31184d1de1695d2e6c5f8ed70f81e6038f9c8eac7616cad14c95729946 1939 python-fuse_1.0.0-3.dsc 5fe481a8ff6564b1549f0e0189f11f1f983484b197033f65fd893ab263b1d9ab 4464 python-fuse_1.0.0-3.debian.tar.xz fb9be32bb26be923d6590d7667cb7d0b059ba92a37e0ff5121d0c3db40a49e11 6919 python-fuse_1.0.0-3_source.buildinfo Files: a5b9f7fba94619a55c6c9ba8f312a5c6 1939
Processed: Set forwarded address for bug 918953
Processing commands for cont...@bugs.debian.org:
> forwarded 918953 https://github.com/itstool/itstool/issues/35
Bug #918953 {Done: Boyuan Yang } [itstool] itstool: Messed up
with encoding when output is redirected (regression?)
Set Bug forwarded-to-address to 'https://github.com/itstool/itstool/issues/35'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
918953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#948682: marked as done (libparse-win32registry-perl FTBFS in the year 2020)
Your message dated Sat, 11 Jan 2020 23:49:17 +
with message-id
and subject line Bug#948682: fixed in libparse-win32registry-perl 1.0-3
has caused the Debian Bug report #948682,
regarding libparse-win32registry-perl FTBFS in the year 2020
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.)
--
948682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948682
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libparse-win32registry-perl
Version: 1.0-2
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/stretch/amd64/libparse-win32registry-perl.html
...
Test Summary Report
---
t/entry.t (Wstat: 6144 Tests: 536 Failed: 24)
Failed tests: 120, 132, 144, 162, 168, 174, 252, 258
264, 270, 276, 282, 331, 343, 355, 373
379, 385, 463, 469, 475, 481, 487, 493
Non-zero exit status: 24
t/file.t(Wstat: 512 Tests: 16 Failed: 2)
Failed tests: 14-15
Non-zero exit status: 2
t/key.t (Wstat: 18432 Tests: 613 Failed: 72)
Failed tests: 314-315, 317, 322, 331-332, 334, 339, 348-349
351, 356, 365-366, 368, 373, 382-383, 385
390, 399-400, 402, 407, 416-417, 419, 424
433-434, 436, 441, 450-451, 453, 458, 467-468
470, 475, 484-485, 487, 492, 501-502, 504
509, 518-519, 521, 526, 535-536, 538, 543
552-553, 555, 560, 569-570, 572, 577, 586-587
589, 594, 603-604, 606, 611
Non-zero exit status: 72
t/misc.t(Wstat: 14592 Tests: 217 Failed: 57)
Failed tests: 65-66, 68-70, 72-74, 76-78, 80-82, 84-86
88-90, 92-94, 96-98, 100-102, 104-106, 108-110
112-114, 116-118, 120-122, 124-126, 128-130
132-134, 136-138, 140
Non-zero exit status: 57
Files=13, Tests=4079, 3 wallclock secs ( 0.58 usr 0.04 sys + 1.90 cusr 0.26
csys = 2.78 CPU)
Result: FAIL
Failed 4/13 test programs. 155/4079 subtests failed.
Makefile:1000: recipe for target 'test_dynamic' failed
make[1]: *** [test_dynamic] Error 255
--- End Message ---
--- Begin Message ---
Source: libparse-win32registry-perl
Source-Version: 1.0-3
We believe that the bug you reported is fixed in the latest version of
libparse-win32registry-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 948...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
gregor herrmann (supplier of updated
libparse-win32registry-perl package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 12 Jan 2020 00:22:34 +0100
Source: libparse-win32registry-perl
Architecture: source
Version: 1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group
Changed-By: gregor herrmann
Closes: 948682
Changes:
libparse-win32registry-perl (1.0-3) unstable; urgency=medium
.
* Team upload.
.
[ Salvatore Bonaccorso ]
* debian/control: Use HTTPS transport protocol for Vcs-Git URI
* Update Vcs-* headers for switch to salsa.debian.org
.
[ gregor herrmann ]
* debian/*: update URLs from {search,www}.cpan.org to MetaCPAN.
* Add patch to fix Y2K20 problem.
Thanks to Adrian Bunk for the bug report. (Closes: #948682)
* debian/rules: remove empty directory.
* debian/copyright: use Copyright-Format 1.0.
* Mark package as autopkgtest-able.
* Declare compliance with Debian Policy 4.4.1.
* Drop unneeded version constraints from (build) dependencies.
* Bump debhelper-compat to 12.
* debian/watch: use uscan version 4.
* Drop Suggests: libgtk2-perl, which is about to go away.
Checksums-Sha1:
c51a970eeb75464b71628b168492fd5add74c961 2464
libparse-win32registry-perl_1.0-3.dsc
bea5d9759d4d45e6461b1dd7d029d0b730dc0b87 3200
libparse-win32registry-perl_1.0-3.debian.tar.xz
Checksums-Sha256:
e19420cd081d3d712c4fed36e691c70a0be385e04110e54eb58606e37bac4afa 2464
libparse-win32registry-perl_1.0-3.dsc
c8ae3b66f06f36fb01802103bd9ead5f8fa47dec17786cbb1b538380efa2d313 3200
libparse-win32registry-perl_1.0-3.debian.tar.xz
Files:
681a6bc9805994ed387535aeeb900ecc 2464 perl optional
libparse-win32registry-per
Processed: Bug#946242 marked as pending in openssh
Processing control commands: > tag -1 pending Bug #946242 [openssh-server] fatal: privsep_preauth: preauth child terminated by signal 31 Added tag(s) pending. -- 946242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946242 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#946242: marked as pending in openssh
Control: tag -1 pending Hello, Bug #946242 in openssh 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/ssh-team/openssh/commit/1e27566efe47a292e9401251f6b27a5eac1a63b1 Deny (non-fatal) ipc in preauth privsep child Closes: #946242 (this message was generated automatically) -- Greetings https://bugs.debian.org/946242
Processed: Bug#948682 marked as pending in libparse-win32registry-perl
Processing control commands: > tag -1 pending Bug #948682 [src:libparse-win32registry-perl] libparse-win32registry-perl FTBFS in the year 2020 Added tag(s) pending. -- 948682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948682 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948682: marked as pending in libparse-win32registry-perl
Control: tag -1 pending Hello, Bug #948682 in libparse-win32registry-perl 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/perl-team/modules/packages/libparse-win32registry-perl/commit/7fe6359700103bae6276cff61109775aecbd0d46 Add patch to fix Y2K20 problem. Thanks: Adrian Bunk for the bug report. Closes: #948682 (this message was generated automatically) -- Greetings https://bugs.debian.org/948682
Bug#948680: marked as done (libtimedate-perl FTBFS in the year 2020)
Your message dated Sat, 11 Jan 2020 23:19:14 + with message-id and subject line Bug#948680: fixed in libtimedate-perl 2.3000-3 has caused the Debian Bug report #948680, regarding libtimedate-perl FTBFS in the year 2020 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.) -- 948680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libtimedate-perl Version: 2.3000-2 Severity: serious Tags: ftbfs patch Forwarded: https://github.com/gbarr/perl-TimeDate/pull/19 https://tests.reproducible-builds.org/debian/rb-pkg/stretch/amd64/libtimedate-perl.html ... t/getdate.t .. 1..146 # offset = 315576 -- FAIL 1 1995-01-24 Diff:-315576 Expect: 3946665600.00 Sun Jan 23 12:00:00 2095 Got:790905600.00 Mon Jan 23 12:00:00 1995 -- ... Test Summary Report --- t/getdate.t (Wstat: 0 Tests: 0 Failed: 0) Parse errors: Bad plan. You planned 146 tests but ran 0. Files=5, Tests=362, 1 wallclock secs ( 0.13 usr 0.02 sys + 0.27 cusr 0.04 csys = 0.46 CPU) Result: FAIL Failed 1/5 test programs. 0/362 subtests failed. Makefile:942: recipe for target 'test_dynamic' failed make[1]: *** [test_dynamic] Error 255 --- End Message --- --- Begin Message --- Source: libtimedate-perl Source-Version: 2.3000-3 We believe that the bug you reported is fixed in the latest version of libtimedate-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 948...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libtimedate-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 12 Jan 2020 00:03:06 +0100 Source: libtimedate-perl Architecture: source Version: 2.3000-3 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 868838 948680 Changes: libtimedate-perl (2.3000-3) unstable; urgency=medium . [ Salvatore Bonaccorso ] * Update Vcs-Browser URL to cgit web frontend * debian/control: Use HTTPS transport protocol for Vcs-Git URI . [ gregor herrmann ] * debian/copyright: change Copyright-Format 1.0 URL to HTTPS. * Remove Christian Hammers from Uploaders. Thanks for your work! Closes: #868838 * Remove Jonathan Yu from Uploaders. Thanks for your work! . [ Salvatore Bonaccorso ] * Update Vcs-* headers for switch to salsa.debian.org . [ Debian Janitor ] * Trim trailing whitespace. * Bump debhelper from deprecated 8 to 12. * Set debhelper-compat version in Build-Depends. * Set upstream metadata fields: Bug-Database, Repository, Repository- Browse. . [ gregor herrmann ] * Add patch from upstream pull request to fix Y2K20 test failure. Thanks to Adrian Bunk for the bug report. (Closes: #948680) * Update years of packaging copyright. * Declare compliance with Debian Policy 4.4.1. * debian/watch: use uscan version 4. * Set upstream metadata fields: Bug-Submit. * Add debian/tests/pkg-perl/use-name for more autopkgtests. Checksums-Sha1: b9983bd051d7ac7e381310fdf0cd83ec607dc3c9 2384 libtimedate-perl_2.3000-3.dsc 94bab8dd955b5f7ad2467783d706afe4414cba02 5340 libtimedate-perl_2.3000-3.debian.tar.xz Checksums-Sha256: ea42b0a01b743c3f564d1a0fede58805e04820b92c820eb8587602c5e48b9efe 2384 libtimedate-perl_2.3000-3.dsc 7a0d962b618c3c043165a27a5c8b8f03dc8208c13c43795a7b9763852856 5340 libtimedate-perl_2.3000-3.debian.tar.xz Files: 5aeaa2a5991f076bdf148184b687c6c3 2384 perl optional libtimedate-perl_2.3000-3.dsc 6c5b13874369de4c8d929839396f97b6 5340 perl optional libtimedate-perl_2.3000-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl4aVLdfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgZnIQ//bENm/ayjgJZovLT6bXZQobi1qO73enxzXDrxx8THUXs92qKzv+TuNVZZ +jHSUc1reWprnCdigfLZFELg46vscVU0etJaEouEyltlkN7dMIN5IR+nmXCL64zW XEDsYYUtzg
Bug#948680: marked as pending in libtimedate-perl
Control: tag -1 pending Hello, Bug #948680 in libtimedate-perl 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/perl-team/modules/packages/libtimedate-perl/commit/d59b5b35293bf9876df831640583aae244685578 Add patch from upstream pull request to fix Y2K20 test failure. Thanks: Adrian Bunk for the bug report. Closes: #948680 (this message was generated automatically) -- Greetings https://bugs.debian.org/948680
Processed: Bug#948680 marked as pending in libtimedate-perl
Processing control commands: > tag -1 pending Bug #948680 [src:libtimedate-perl] libtimedate-perl FTBFS in the year 2020 Added tag(s) pending. -- 948680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 948682 is forwarded to https://rt.cpan.org/Public/Bug/Display.html?id=124514
Processing commands for cont...@bugs.debian.org: > forwarded 948682 https://rt.cpan.org/Public/Bug/Display.html?id=124514 Bug #948682 [src:libparse-win32registry-perl] libparse-win32registry-perl FTBFS in the year 2020 Set Bug forwarded-to-address to 'https://rt.cpan.org/Public/Bug/Display.html?id=124514'. > thanks Stopping processing here. Please contact me if you need assistance. -- 948682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948682 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947124: marked as done (apache-log4j1.2: CVE-2019-17571)
Your message dated Sat, 11 Jan 2020 22:34:14 + with message-id and subject line Bug#947124: fixed in apache-log4j1.2 1.2.17-9 has caused the Debian Bug report #947124, regarding apache-log4j1.2: CVE-2019-17571 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.) -- 947124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947124 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apache-log4j1.2 Version: 1.2.17-8 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 1.2.17-7 Control: found -1 1.2.17-5 Hi, The following vulnerability was published for apache-log4j1.2. CVE-2019-17571[0]: | Included in Log4j 1.2 is a SocketServer class that is vulnerable to | deserialization of untrusted data which can be exploited to remotely | execute arbitrary code when combined with a deserialization gadget | when listening to untrusted network traffic for log data. This affects | Log4j versions up to 1.2 up to 1.2.17. Note that this issue correponds to the old CVE-2017-5645 for the 2.x branch codebasis[1]. 1.2 reached end of life in 2015 accordingly, and the "right move" would be to switch to 2.x. Which raises a question from security support point of view: We would need to fade out apache-log4j1.2 for bullseye at least now right? From a quick check via a simulated dak rm, it looks right now impossible to actually remove it. Are there current plans from the Debian Java Maintainers for that? Or is there something I currently just miss from the big picture? 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-17571 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17571 [1] https://www.openwall.com/lists/oss-security/2019/12/19/2 Regards, Salvatore --- End Message --- --- Begin Message --- Source: apache-log4j1.2 Source-Version: 1.2.17-9 We believe that the bug you reported is fixed in the latest version of apache-log4j1.2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 947...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated apache-log4j1.2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 11 Jan 2020 23:06:27 +0100 Source: apache-log4j1.2 Architecture: source Version: 1.2.17-9 Distribution: unstable Urgency: high Maintainer: Debian Java Maintainers Changed-By: Markus Koschany Closes: 947124 Changes: apache-log4j1.2 (1.2.17-9) unstable; urgency=high . * Team upload. * Fix CVE-2019-17571. (Closes: #947124) Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. * Switch to debhelper-compat = 12. * Declare compliance with Debian Policy 4.4.1. * Use canonical VCS URI. Checksums-Sha1: 7509b3e1b006af179cb8fbe4f80e9c87702fcfc8 2456 apache-log4j1.2_1.2.17-9.dsc 473a6d296a4cb7d6a73a5dbea95aa9ef6615cf22 9892 apache-log4j1.2_1.2.17-9.debian.tar.xz c6137a1443683270b7a06a61e8337c46de1d125a 9175 apache-log4j1.2_1.2.17-9_amd64.buildinfo Checksums-Sha256: 94af9dc41077911b2a9f18cd01efe56996cfe5dcabaf8541e48718c0cddb9569 2456 apache-log4j1.2_1.2.17-9.dsc 303485eef0bc8c6c1de0b60e89aec879a34df74af74f2a136052c9c93c983363 9892 apache-log4j1.2_1.2.17-9.debian.tar.xz 69da4f0f1303822592f03e22badb875917c2e7b61eab97e817eb4463d2e6a012 9175 apache-log4j1.2_1.2.17-9_amd64.buildinfo Files: 5b207c7553c7131833d170819c11c22f 2456 java optional apache-log4j1.2_1.2.17-9.dsc df3445aecf28c89eaf78d5e6e20be69d 9892 java optional apache-log4j1.2_1.2.17-9.debian.tar.xz e2c0334016aa0217f7f0ba039e6ad53f 9175 java optional apache-log4j1.2_1.2.17-9_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAl4aR8tfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4R
Bug#938219: marked as done (python-tktreectrl: Python2 removal in sid/bullseye)
Your message dated Sat, 11 Jan 2020 22:21:31 + with message-id and subject line Bug#938219: fixed in python-tktreectrl 2.0.2-2 has caused the Debian Bug report #938219, regarding python-tktreectrl: 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.) -- 938219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-tktreectrl Version: 2.0.2-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html 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-tktreectrl 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-tktreectrl Source-Version: 2.0.2-2 We believe that the bug you reported is fixed in the latest version of python-tktreectrl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated python-tktreectrl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 11 Jan 2020 16:55:18 -0500 Source: python-tktreectrl Architecture: source Version: 2.0.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Sandro Tosi Closes: 938219 Changes: python-tktreectrl (2.0.2-2) unstable; urgency=medium . [ Ondřej Nový ] * d/watch: Use https protocol * Use debhelper-compat instead of debian/compat. . [ Sandro Tosi ] * Drop python2 support; Closes: #938219 Checksums-Sha1: 74546893eb2dc2bf03a9a6ab2135ac1e25d45f0c 2201 python-tktreectrl_2.0.2-2.dsc 96120844a5e0ce76927f46e7b4b794aed8fa2186 2280 python-tktreectrl_2.0.2-2.debian.tar.xz a87e3094d3896133d377860f73b7624f80028518 7027 python-tktreectrl_2.0.2-2_source.buildinfo Checksums-Sha256: 0fb60b0fbfca387fcff2e0611f56aea7a3eaea0671d5002855b84de361b5d7d3 2201 python-tktreectrl_2.0.2-2.dsc e0f7ee825462606b03c51f9bc0ba1a4af12befed9647dcb6f85c984bddb76990 2280 py
Processed: py2removal bugs severity updates - 2020-01-11 21:35:36.650541+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # and https://lists.debian.org/debian-python/2019/12/msg00076.html > # mail threads for more details on this severity update > # mgltools-vision is an application, has low popcon (6 < 300), and has 0 > external rdeps or not in testing > severity 937039 serious Bug #937039 [src:mgltools-vision] mgltools-vision: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # mgltools-webservices is an application, has low popcon (11 < 300), and has > 0 external rdeps or not in testing > severity 937042 serious Bug #937042 [src:mgltools-webservices] mgltools-webservices: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-fuse is a module and has 0 external rdeps or not in testing > severity 937771 serious Bug #937771 [src:python-fuse] python-fuse: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-tktreectrl is a module and has 0 external rdeps or not in testing > severity 938219 serious Bug #938219 [src:python-tktreectrl] python-tktreectrl: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 937039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937039 937042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937042 937771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937771 938219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 944026
Processing commands for cont...@bugs.debian.org: > tags 944026 - patch Bug #944026 [python3-freezegun] freezegun: failing tests with python3.8 Bug #943966 [python3-freezegun] cookiecutter: failing tests with python3.8 Removed tag(s) patch. Removed tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 943966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943966 944026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org: > unblock 943966 by 944026 Bug #943966 [cookiecutter] cookiecutter: failing tests with python3.8 943966 was blocked by: 944026 943966 was not blocking any bugs. Removed blocking bug(s) of 943966: 944026 > reassign 943966 python3-freezegun Bug #943966 [cookiecutter] cookiecutter: failing tests with python3.8 Bug reassigned from package 'cookiecutter' to 'python3-freezegun'. No longer marked as found in versions cookiecutter/1.6.0-4. Ignoring request to alter fixed versions of bug #943966 to the same values previously set > forcemerge 944026 943966 Bug #944026 [python3-freezegun] freezegun: failing tests with python3.8 Bug #943966 [python3-freezegun] cookiecutter: failing tests with python3.8 Marked as found in versions freezegun/0.3.11-0.1. Added tag(s) sid and bullseye. Merged 943966 944026 > affects 944026 src:cookiecutter Bug #944026 [python3-freezegun] freezegun: failing tests with python3.8 Bug #943966 [python3-freezegun] cookiecutter: failing tests with python3.8 Added indication that 944026 affects src:cookiecutter Added indication that 943966 affects src:cookiecutter > thanks Stopping processing here. Please contact me if you need assistance. -- 943966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943966 944026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948683: ruby-aws-sdk: pakage is broken
Package: ruby-aws-sdk
Version: 2.9.32-2
Severity: grave
Justification: renders package unusable
Hi,
The current version in experimental is broken, Running the tests on it
gives:
/usr/bin/ruby2.5 /usr/bin/rspec
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/aws-sdk-core/spec
-I /usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib -I
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/aws-sdk-core/spec
Warning: Error occurred while trying to load
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/.simplecov. Error
message: cannot load such file -- coveralls
An error occurred while loading
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/aws-sdk-core/spec/aws/partitions_spec.rb.
Failure/Error: self.load(File.open(path, 'r', encoding: 'UTF-8') { |f|
f.read })
Errno::ENOENT:
No such file or directory @ rb_sysopen -
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/../../endpoints.json
#
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/json.rb:32:in
`initialize'
#
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/json.rb:32:in
`open'
#
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/json.rb:32:in
`load_file'
#
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions.rb:148:in
`defaults'
#
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions.rb:155:in
`default_list'
#
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core.rb:388:in
`partitions'
#
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/aws-sdk-core/spec/aws/partitions_spec.rb:204:in
`block (2 levels) in '
#
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/aws-sdk-core/spec/aws/partitions_spec.rb:203:in
`block in '
#
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/aws-sdk-core/spec/aws/partitions_spec.rb:5:in
`'
#
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/aws-sdk-core/spec/aws/partitions_spec.rb:4:in
`'
#
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/aws-sdk-core/spec/aws/partitions_spec.rb:3:in
`'
sh: 1: unsigns: not found
sh: 1: signs: not found
sh: 1: signs: not found
Finished in 0.00064 seconds (files took 1.23 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples
---
Updating this file
(/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/../../endpoints.json)
by hand gives:
/usr/bin/ruby2.5 /usr/bin/rspec
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/aws-sdk-core/spec
-I /usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib -I
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/aws-sdk-core/spec
Warning: Error occurred while trying to load
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/.simplecov. Error
message: cannot load such file -- coveralls
An error occurred while loading
/home/deiv/dev-dinamic/debian/pkgs/ruby/ruby-aws-sdk/aws-sdk-core/spec/aws/partitions_spec.rb.
Failure/Error: self.load(File.open(path, 'r', encoding: 'UTF-8') { |f|
f.read })
Errno::ENOENT:
No such file or directory @ rb_sysopen -
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/../../service-models.json
#
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/json.rb:32:in
`initialize'
#
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/json.rb:32:in
`open'
#
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/json.rb:32:in
`load_file'
#
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions.rb:164:in
`service_ids'
#
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions/region.rb:49:in
`region_services'
#
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions/region.rb:42:in
`build'
#
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions/partition.rb:72:in
`block in build_regions'
#
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions/partition.rb:70:in
`each'
#
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions/partition.rb:70:in
`inject'
#
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions/partition.rb:70:in
`build_regions'
#
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions/partition.rb:60:in
`build'
#
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions/partition_list.rb:52:in
`block in build'
#
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions/partition_list.rb:51:in
`each'
#
/usr/share/rubygems-integration/all/gems/aws-sdk-core-2.9.32/lib/aws-sdk-core/partitions/partition_list.rb:51:in
Bug#948682: libparse-win32registry-perl FTBFS in the year 2020
Source: libparse-win32registry-perl Version: 1.0-2 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/stretch/amd64/libparse-win32registry-perl.html ... Test Summary Report --- t/entry.t (Wstat: 6144 Tests: 536 Failed: 24) Failed tests: 120, 132, 144, 162, 168, 174, 252, 258 264, 270, 276, 282, 331, 343, 355, 373 379, 385, 463, 469, 475, 481, 487, 493 Non-zero exit status: 24 t/file.t(Wstat: 512 Tests: 16 Failed: 2) Failed tests: 14-15 Non-zero exit status: 2 t/key.t (Wstat: 18432 Tests: 613 Failed: 72) Failed tests: 314-315, 317, 322, 331-332, 334, 339, 348-349 351, 356, 365-366, 368, 373, 382-383, 385 390, 399-400, 402, 407, 416-417, 419, 424 433-434, 436, 441, 450-451, 453, 458, 467-468 470, 475, 484-485, 487, 492, 501-502, 504 509, 518-519, 521, 526, 535-536, 538, 543 552-553, 555, 560, 569-570, 572, 577, 586-587 589, 594, 603-604, 606, 611 Non-zero exit status: 72 t/misc.t(Wstat: 14592 Tests: 217 Failed: 57) Failed tests: 65-66, 68-70, 72-74, 76-78, 80-82, 84-86 88-90, 92-94, 96-98, 100-102, 104-106, 108-110 112-114, 116-118, 120-122, 124-126, 128-130 132-134, 136-138, 140 Non-zero exit status: 57 Files=13, Tests=4079, 3 wallclock secs ( 0.58 usr 0.04 sys + 1.90 cusr 0.26 csys = 2.78 CPU) Result: FAIL Failed 4/13 test programs. 155/4079 subtests failed. Makefile:1000: recipe for target 'test_dynamic' failed make[1]: *** [test_dynamic] Error 255
Bug#948680: libtimedate-perl FTBFS in the year 2020
Source: libtimedate-perl Version: 2.3000-2 Severity: serious Tags: ftbfs patch Forwarded: https://github.com/gbarr/perl-TimeDate/pull/19 https://tests.reproducible-builds.org/debian/rb-pkg/stretch/amd64/libtimedate-perl.html ... t/getdate.t .. 1..146 # offset = 315576 -- FAIL 1 1995-01-24 Diff:-315576 Expect: 3946665600.00 Sun Jan 23 12:00:00 2095 Got:790905600.00 Mon Jan 23 12:00:00 1995 -- ... Test Summary Report --- t/getdate.t (Wstat: 0 Tests: 0 Failed: 0) Parse errors: Bad plan. You planned 146 tests but ran 0. Files=5, Tests=362, 1 wallclock secs ( 0.13 usr 0.02 sys + 0.27 cusr 0.04 csys = 0.46 CPU) Result: FAIL Failed 1/5 test programs. 0/362 subtests failed. Makefile:942: recipe for target 'test_dynamic' failed make[1]: *** [test_dynamic] Error 255
Processed: reassign 948160 to ftp.debian.org ...
Processing commands for cont...@bugs.debian.org: > reassign 948160 ftp.debian.org Bug #948160 [python-id3] python-id3: should this package be removed? Bug reassigned from package 'python-id3' to 'ftp.debian.org'. No longer marked as found in versions python-id3/1.2-6.3. Ignoring request to alter fixed versions of bug #948160 to the same values previously set > retitle 948160 RM: python-id3 -- RoQA; python2-only; no upstream update in > years; similar functionalities from mutagen Bug #948160 [ftp.debian.org] python-id3: should this package be removed? Changed Bug title to 'RM: python-id3 -- RoQA; python2-only; no upstream update in years; similar functionalities from mutagen' from 'python-id3: should this package be removed?'. > thanks Stopping processing here. Please contact me if you need assistance. -- 948160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: py2removal bugs severity updates - 2020-01-11 17:35:37.613886+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # and https://lists.debian.org/debian-python/2019/12/msg00076.html > # mail threads for more details on this severity update > # zomg is an application, has low popcon (18 < 300), and has 0 external rdeps > or not in testing > severity 945729 serious Bug #945729 [src:zomg] zomg: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 945729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945729 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> tags 938485 + pending
Bug #938485 {Done: Debian FTP Masters }
[src:simpletal] simpletal: Python2 removal in sid/bullseye
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
938485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#947463: marked as done (bio-tradis: autopkgtest regression: Use of uninitialized value $total_uis (and lots of mv: cannot stat '/tmp/aut.....))
Your message dated Sat, 11 Jan 2020 16:19:14 + with message-id and subject line Bug#947463: fixed in bio-tradis 1.4.5+dfsg2-1 has caused the Debian Bug report #947463, regarding bio-tradis: autopkgtest regression: Use of uninitialized value $total_uis (and lots of mv: cannot stat '/tmp/aut.) 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.) -- 947463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bio-tradis Version: 1.4.5+dfsg-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Control: affects -1 src:samtools Dear maintainers, With a recent upload of bio-tradis the autopkgtest of bio-tradis fails in testing when that autopkgtest is run with the binary packages of bio-tradis from unstable. It passes when run with only packages from testing. In tabular form: passfail bio-tradis from testing1.4.5+dfsg-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? Additionally, looking at the failure mode in unstable, it seems some package (samtools?) made your (test?) dependencies non-installable in unstable. You probably need to fix that as well, or raise the issue with the samtools maintainer. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=bio-tradis https://ci.debian.net/data/autopkgtest/testing/amd64/b/bio-tradis/3765198/log.gz t/Bio/Tradis/CommandLine/TradisAnalysis.t .. ok 1 - use Bio::Tradis::CommandLine::TradisAnalysis; ok 2 - creating object Use of uninitialized value $total_uis in concatenation (.) or string at /usr/share/perl5/Bio/Tradis/RunTradis.pm line 468. Use of uninitialized value $total_uis in numeric gt (>) at /usr/share/perl5/Bio/Tradis/RunTradis.pm line 470. mv: cannot stat '/tmp/autopkgtest-lxc.sfremfei/downtmp/autopkgtest_tmp/smokezkXJAM/tmp_TradisAnalysis_tests_lTLCo/tmp_run_tradis_MG155/test_1.out*': No such file or directory Use of uninitialized value $total_uis in concatenation (.) or string at /usr/share/perl5/Bio/Tradis/RunTradis.pm line 468. Use of uninitialized value $total_uis in numeric gt (>) at /usr/share/perl5/Bio/Tradis/RunTradis.pm line 470. mv: cannot stat '/tmp/autopkgtest-lxc.sfremfei/downtmp/autopkgtest_tmp/smokezkXJAM/tmp_TradisAnalysis_tests_lTLCo/tmp_run_tradis_xXbiS/test_2.out*': No such file or directory ok 3 - testing run ok 4 - both files have reads with tag mv: cannot stat '/tmp/autopkgtest-lxc.sfremfei/downtmp/autopkgtest_tmp/smokezkXJAM/tmp_TradisAnalysis_tests_K2kqu/tmp_run_tradis_AFhbT/test_2.out*': No such file or directory ok 5 - testing run with tag only found in one fastq not ok 6 - one warning raised # Failed test 'one warning raised' # at t/Bio/Tradis/CommandLine/TradisAnalysis.t line 58. # got: '3' # expected: '1' [...] Test Summary Report --- t/Bio/Tradis/CommandLine/TradisAnalysis.t (Wstat: 256 Tests: 10 Failed: 1) Failed test: 6 Non-zero exit status: 1 t/Bio/Tradis/Map.t (Wstat: 1536 Tests: 21 Failed: 6) Failed tests: 11-15, 18 Non-zero exit status: 6 t/Bio/Tradis/RunTradisBWA.t (Wstat: 2304 Tests: 45 Failed: 9) Failed tests: 18, 27-28, 30-31, 34-35, 38, 41 Non-zero exit status: 9 t/Bio/Tradis/RunTradisTaglessBwa.t (Wstat: 1280 Tests: 22 Failed: 5) Failed tests: 5, 14-15, 17-18 Non-zero exit status: 5 Files=16, Tests=310, 14 wallclock secs ( 1.33 usr 0.03 sys + 6.97 cusr 1.19 csys = 9.52 CPU) Result: FAIL signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: bio-tradis Source-Version: 1.4.5+dfsg2-1 We believe that the bug you reported is fixed in the latest version of bio-tradis, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 947...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael R. Crusoe (supplier of updated bio-tradis package) (This message was generated automatically at thei
Processed: fixing ftbfs/ftcbfs bug metadata
Processing commands for cont...@bugs.debian.org: > # affect source packages, not binary packages. add src:bolt > affects 948611 = src:bolt src:systemd src:virglrenderer src:libdrm Bug #948611 [meson] meson fails to cross build anything with the cross file from debcrossgen Removed indication that 948611 affects systemd, libdrm, and virglrenderer Added indication that 948611 affects src:libdrm, src:systemd, src:virglrenderer, and src:bolt > # reassign to source package > reassign 933285 src:knot Bug #933285 [knot] BD on texlive-generic-extra which isn't build anymore and isn't in bullseye Bug reassigned from package 'knot' to 'src:knot'. No longer marked as found in versions knot/2.7.6-2. Ignoring request to alter fixed versions of bug #933285 to the same values previously set > # restore found version after reassign > found 933285 2.7.6-2 Bug #933285 [src:knot] BD on texlive-generic-extra which isn't build anymore and isn't in bullseye Marked as found in versions knot/2.7.6-2. > # reassign to source package > reassign 932533 src:gtkperf Bug #932533 [gtkperf] gtkperf: Uses manual dh sequence operations that are going to be removed Bug reassigned from package 'gtkperf' to 'src:gtkperf'. No longer marked as found in versions gtkperf/0.40+ds-2. Ignoring request to alter fixed versions of bug #932533 to the same values previously set > # restore found version after reassign > found 932533 0.40+ds-2 Bug #932533 [src:gtkperf] gtkperf: Uses manual dh sequence operations that are going to be removed Marked as found in versions gtkperf/0.40+ds-2. > # reassign to source package > reassign 932532 src:getlive Bug #932532 [getlive] getlive: Uses manual dh sequence operations that are going to be removed Bug reassigned from package 'getlive' to 'src:getlive'. No longer marked as found in versions getlive/2.4+cvs20120801-1. Ignoring request to alter fixed versions of bug #932532 to the same values previously set > # restore found version after reassign > found 932532 2.4+cvs20120801-1 Bug #932532 [src:getlive] getlive: Uses manual dh sequence operations that are going to be removed Marked as found in versions getlive/2.4+cvs20120801-1. > # reassign to source package > reassign 932526 src:daa2iso Bug #932526 [daa2iso] daa2iso: Uses manual dh sequence operations that are going to be removed Bug reassigned from package 'daa2iso' to 'src:daa2iso'. No longer marked as found in versions daa2iso/0.1.7e-1. Ignoring request to alter fixed versions of bug #932526 to the same values previously set > # restore found version after reassign > found 932526 0.1.7e-1 Bug #932526 [src:daa2iso] daa2iso: Uses manual dh sequence operations that are going to be removed Marked as found in versions daa2iso/0.1.7e-1. > # reassign to source package > reassign 930332 src:coyim Bug #930332 [coyim] FTBFS on arm64: FAIL: peer_test.go:79: PeerSuite.Test_NameForPresentation_returnsTheNameIfItExistsButJidOtherwise Bug reassigned from package 'coyim' to 'src:coyim'. No longer marked as found in versions coyim/0.3.8+ds-6. Ignoring request to alter fixed versions of bug #930332 to the same values previously set > # restore found version after reassign > found 930332 0.3.8+ds-6 Bug #930332 [src:coyim] FTBFS on arm64: FAIL: peer_test.go:79: PeerSuite.Test_NameForPresentation_returnsTheNameIfItExistsButJidOtherwise Marked as found in versions coyim/0.3.8+ds-6. > # reassign to source package > reassign 929531 src:grub2 Bug #929531 [grub-pc] grub-pc: grub2 fat_test fails with 4.19.0-5-amd64 kernel if one ensure it does not gets auto-skipped Bug reassigned from package 'grub-pc' to 'src:grub2'. No longer marked as found in versions grub2/2.02+dfsg1-18. Ignoring request to alter fixed versions of bug #929531 to the same values previously set > # restore found version after reassign > found 930332 2.02+dfsg1-18 Bug #930332 [src:coyim] FTBFS on arm64: FAIL: peer_test.go:79: PeerSuite.Test_NameForPresentation_returnsTheNameIfItExistsButJidOtherwise The source 'coyim' and version '2.02+dfsg1-18' do not appear to match any binary packages Marked as found in versions coyim/2.02+dfsg1-18. > thanks Stopping processing here. Please contact me if you need assistance. -- 929531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929531 930332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930332 932526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932526 932532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932532 932533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932533 933285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933285 948611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948611 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 945920 + patch Bug #945920 [chromium] Chromium randomly crashes in the latest version. Bug #946648 [chromium] crashes within a few minutes Added tag(s) patch. Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 945920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945920 946648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947004: marked as done (Tests segfaults (since the r-base-core update?))
Your message dated Sat, 11 Jan 2020 15:51:19 + with message-id and subject line Bug#947004: fixed in r-bioc-s4vectors 0.24.1-2 has caused the Debian Bug report #947004, regarding Tests segfaults (since the r-base-core update?) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 947004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947004 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: r-bioc-s4vectors Version: 0.24.1-1 The autopkgtest started failing on a segfault https://ci.debian.net/packages/r/r-bioc-s4vectors/unstable/amd64/ It seems to have started with the r-base update -r-base-core 3.6.1-7 +r-base-core 3.6.1.20191206-1 --- End Message --- --- Begin Message --- Source: r-bioc-s4vectors Source-Version: 0.24.1-2 We believe that the bug you reported is fixed in the latest version of r-bioc-s4vectors, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 947...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dylan Aïssi (supplier of updated r-bioc-s4vectors package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 11 Jan 2020 16:21:03 +0100 Source: r-bioc-s4vectors Architecture: source Version: 0.24.1-2 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Dylan Aïssi Closes: 947004 Changes: r-bioc-s4vectors (0.24.1-2) unstable; urgency=medium . * Team upload. * Fix autopkgtests (Closes: #947004). Checksums-Sha1: 7a1eba9d1c4bf03835a33c8d2c61d2487304e7d3 2182 r-bioc-s4vectors_0.24.1-2.dsc 8677b20c0b386183da56d24c3370a90c64a6b9a8 4548 r-bioc-s4vectors_0.24.1-2.debian.tar.xz 20875e5013e107b63cfbc3c8de9c60b6f362affe 8986 r-bioc-s4vectors_0.24.1-2_amd64.buildinfo Checksums-Sha256: 79131f11ab03f41bad3c1aa9bc68094eb2dde4ef0720d3260f92dae8519a0dd5 2182 r-bioc-s4vectors_0.24.1-2.dsc 41a4ae7e123c714073c3b0dc7bdce601211dc6ac5f145d6f2bb8e09bb4802466 4548 r-bioc-s4vectors_0.24.1-2.debian.tar.xz fef96667df88bb6565b20d6218dda9c81d885936ccbce3c11f4cc789a5cb6471 8986 r-bioc-s4vectors_0.24.1-2_amd64.buildinfo Files: f2c440cde0bd1aca838c85e73b133a84 2182 gnu-r optional r-bioc-s4vectors_0.24.1-2.dsc 251ad391c8d2c7695ba61b82d6a0ee94 4548 gnu-r optional r-bioc-s4vectors_0.24.1-2.debian.tar.xz 484769bdf4f4d8467ced043c9ac61b9b 8986 gnu-r optional r-bioc-s4vectors_0.24.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAl4Z6VYSHGRhaXNzaUBk ZWJpYW4ub3JnAAoJEGEu8WE+BQ9UQ/0P/3LUfpEtZhT/LZdDsFvJHpfKM6JfxCLe MtVQGUxCGKNtMvJVTHDVctmBUaf+zNrv9BrcaMFUWRkKOWXZgBml3/3WCbPzhH2p Bu6jkEF4Zy1ojen10bnGxVNSVNddwUrV8G1Kx46UhyXwsZihDuge1FbO/m0YNfrj NjKZUMhjE1QgNiSWweLr4NlhVl8C1IsXI7NB7zHYqI67JqL2wHnWEcUPr1xpAQWj trPPOxVooB6BbkTelClyRD6piJh2E+7RQ6PnfZ/viy9jNAXJ0szleZfycLtwtoWJ nAG4CdatI7mfwGkh17eY4oWq0zxUsRqGli2qw2En7divyoN4E/gm8LUEaPrdUalA dvqwSqtCBSBC0SbaoJXW9PGMecUqSVhNoxPHA48tgr5llSqkYhD2GfEWAxTSrj75 dv0GR+zvkLOyb3RzRdgUUasYkIitXdWI7LN6BCglh8pmOteKLagBovLr+0PMjcg9 Y5CzqoRSFf1JPA6PbqG5r2K3V7Z6JVJ4DTJm0WJWZ9bNQ2xkE0BZWVUHJImOE5o8 CLaB6r1iNVqZNGa4UQYIDucmmgZGXItFsLuy4Uer0uxO84hfvvpYiQ45iwi9r4CU 6cKL5MifC4mT9F+2ue18yDkn1LFplexkovo6/UIJjlBEhTeQ0HrIrwrVamQ8tTCT PHAm7TX43fuc =xsWs -END PGP SIGNATURE End Message ---
Bug#948669: libtest-mocktime-perl: test fails in 2020
Source: libtest-mocktime-perl Version: 0.15-1 Severity: serious Tags: ftbfs Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=124508 Control: close -1 0.16-1 https://tests.reproducible-builds.org/debian/rb-pkg/stretch/amd64/libtest-mocktime-perl.html ... # Failed test 'localtime seems ok' # at t/test.t line 43. # Looks like you failed 1 test of 11. t/test.t . ...
Processed: libtest-mocktime-perl: test fails in 2020
Processing control commands: > close -1 0.16-1 Bug #948669 [src:libtest-mocktime-perl] libtest-mocktime-perl: test fails in 2020 Marked as fixed in versions libtest-mocktime-perl/0.16-1. Bug #948669 [src:libtest-mocktime-perl] libtest-mocktime-perl: test fails in 2020 Marked Bug as done -- 948669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948669 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libole-storage-lite-perl: y2k20 problem
Processing control commands: > close -1 0.20-1 Bug #948668 [src:libole-storage-lite-perl] libole-storage-lite-perl: y2k20 problem Marked as fixed in versions libole-storage-lite-perl/0.20-1. Bug #948668 [src:libole-storage-lite-perl] libole-storage-lite-perl: y2k20 problem Marked Bug as done -- 948668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948668 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948668: libole-storage-lite-perl: y2k20 problem
Source: libole-storage-lite-perl Version: 0.19-1 Severity: serious Tags: ftbfs Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=124513 Control: close -1 0.20-1 https://tests.reproducible-builds.org/debian/rb-pkg/stretch/amd64/libole-storage-lite-perl.html ... # Failed test ' LocalDate2OLE: Thu Jan 1 00:00:00 1970 ' # at t/01_date_conversion.t line 40. # got: '0040352757CF0D02' # expected: '00803ED5DEB19D01' # Failed test ' LocalDate2OLE: Thu Jan 1 00:00:01 1970 ' # at t/01_date_conversion.t line 40. # got: '80D6CD2757CF0D02' # expected: '8016D7D5DEB19D01' # Failed test ' LocalDate2OLE: Mon Feb 16 06:28:15 1970 ' # at t/01_date_conversion.t line 40. # got: '80A91C03B3F30D02' # expected: '80E925B13AD69D01' # Failed test ' LocalDate2OLE: Fri Dec 11 08:49:03 1970 ' # at t/01_date_conversion.t line 40. # got: '80A99C0DF2DD0E02' # expected: '80E9A5BB79C09E01' # Looks like you failed 4 tests of 198. t/01_date_conversion.t .. ... libole-storage-lite-perl (0.20-1) unstable; urgency=medium * Import upstream version 0.20. Fixes y2k20 problem, as seen also on ci.debian.net. ... -- gregor herrmann Thu, 02 Jan 2020 17:26:42 +0100
Bug#948666: libperl4-corelibs-perl: Y2K20 problem in t/timelocal.t
Source: libperl4-corelibs-perl Version: 0.003-2 Severity: serious Tags: ftbfs Control: close -1 0.004-2 https://tests.reproducible-builds.org/debian/rb-pkg/stretch/amd64/libperl4-corelibs-perl.html ... # Failed test 'timelocal year for 1970 1 2 0 0 0' # at t/timelocal.t line 36. # got: '170' # expected: '70' # Failed test 'timegm year for 1970 1 2 0 0 0' # at t/timelocal.t line 49. # got: '170' # expected: '70' # Looks like you failed 2 tests of 135. t/timelocal.t ... ... libperl4-corelibs-perl (0.004-2) unstable; urgency=medium ... * Add t/timelocal.t to fix Y2K20 problem in t/timelocal.t. ... -- gregor herrmann Fri, 03 Jan 2020 05:09:21 +0100
Processed: libperl4-corelibs-perl: Y2K20 problem in t/timelocal.t
Processing control commands: > close -1 0.004-2 Bug #948666 [src:libperl4-corelibs-perl] libperl4-corelibs-perl: Y2K20 problem in t/timelocal.t Marked as fixed in versions libperl4-corelibs-perl/0.004-2. Bug #948666 [src:libperl4-corelibs-perl] libperl4-corelibs-perl: Y2K20 problem in t/timelocal.t Marked Bug as done -- 948666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947001: Bug#947004: S4Vectors Segmentation fault after r-base-core update (Was: Bug#947004: Tests segfaults (since the r-base-core update?))
On Sat, Jan 11, 2020 at 10:12:48AM +0100, Dylan Aïssi wrote:
> Le ven. 10 janv. 2020 à 00:30, Pages, Herve a écrit :
> > Based on the traceback the error happens during evaluation of the 1st
> > argument ('target') passed to checkEqualsNumeric(), that is, during
> > evaluation of 'runmed(y, 7)'. Since this involves base R code only
> > (runmed() is implemented in the stats package) I would say that it's not
> > immediately obvious that the problem is in my court.
>
> Thanks Hervé for this.
+1
> I just updated how to run Debian autopkgtests [1-2] by replacing:
>
> > LC_ALL=C R --no-save < > require("S4Vectors")
> > S4Vectors:::.test()
> > EOT
>
> with
>
> > LC_ALL=C.UTF-8 R --no-save -e 'BiocGenerics:::testPackage("S4Vectors")'
>
> which seems to be the recommended way to run tests for bioconductor
> packages. And now, there is no segfault anymore for S4vectors but
> IRanges is still crashing. Should we upload these fixes into
> Debian/unstable?
Thanks for the fix - IMHO it makes sense to upload in any way if we
are doing something differently than it should be done. Would you
mind checking other BioConductor packages as well?
Kind regards and thanks for your investigation
Andreas.
> [1]
> https://salsa.debian.org/r-pkg-team/r-bioc-s4vectors/commit/51b8ca2571dac1685e748679568edf4463cbfd59
> [2]
> https://salsa.debian.org/r-pkg-team/r-bioc-iranges/commit/06a76a22fa236f919fc0038c5c01aec35ec2ecda
> [3]
> https://bioconductor.org/developers/how-to/unitTesting-guidelines/#RUnitConventions
--
http://fam-tille.de
Processed: closing 948641
Processing commands for cont...@bugs.debian.org: > close 948641 Bug #948641 [src:rust-extprim] rust-extprim: Build-depends on older rust-rand than is in unstable Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 948641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948641 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 948640
Processing commands for cont...@bugs.debian.org: > close 948640 Bug #948640 [src:rust-migrations-internals] rust-migrations-internals: depends on older rust-barrel than is in unstable Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 948640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948640 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 948640 in 1.4.0-2
Processing commands for cont...@bugs.debian.org: > fixed 948640 1.4.0-2 Bug #948640 [src:rust-migrations-internals] rust-migrations-internals: depends on older rust-barrel than is in unstable The source 'rust-migrations-internals' and version '1.4.0-2' do not appear to match any binary packages Marked as fixed in versions rust-migrations-internals/1.4.0-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 948640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948640 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 948639
Processing commands for cont...@bugs.debian.org: > close 948639 Bug #948639 [src:rust-log] rust-log depends on non-existent librust-sval-0.4+fmt-dev Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 948639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 948641 in 0.4.1-2
Processing commands for cont...@bugs.debian.org: > fixed 948641 0.4.1-2 Bug #948641 [src:rust-extprim] rust-extprim: Build-depends on older rust-rand than is in unstable The source 'rust-extprim' and version '0.4.1-2' do not appear to match any binary packages Marked as fixed in versions rust-extprim/0.4.1-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 948641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948641 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 948642
Processing commands for cont...@bugs.debian.org: > close 948642 Bug #948642 [src:rust-cookie] rust-cookie: Depends on older rust-ring than is in unstable Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 948642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 948647
Processing commands for cont...@bugs.debian.org: > close 948647 Bug #948647 [src:rust-backtrace] rust-backtrace depends on non-existent librust-compiler-builtins Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 948647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948647 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 948639 in 0.4.8-3
Processing commands for cont...@bugs.debian.org: > fixed 948639 0.4.8-3 Bug #948639 [src:rust-log] rust-log depends on non-existent librust-sval-0.4+fmt-dev The source 'rust-log' and version '0.4.8-3' do not appear to match any binary packages Marked as fixed in versions rust-log/0.4.8-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 948639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 948642 in 0.12.0-4
Processing commands for cont...@bugs.debian.org: > fixed 948642 0.12.0-4 Bug #948642 [src:rust-cookie] rust-cookie: Depends on older rust-ring than is in unstable Marked as fixed in versions rust-cookie/0.12.0-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 948642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 948642 in 0.12.0-5
Processing commands for cont...@bugs.debian.org: > fixed 948642 0.12.0-5 Bug #948642 [src:rust-cookie] rust-cookie: Depends on older rust-ring than is in unstable The source 'rust-cookie' and version '0.12.0-5' do not appear to match any binary packages Marked as fixed in versions rust-cookie/0.12.0-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 948642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfixed 948642 in 0.12.0-4
Processing commands for cont...@bugs.debian.org: > notfixed 948642 0.12.0-4 Bug #948642 [src:rust-cookie] rust-cookie: Depends on older rust-ring than is in unstable No longer marked as fixed in versions rust-cookie/0.12.0-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 948642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948647: [Pkg-rust-maintainers] Bug#948647: rust-backtrace depends on non-existent librust-compiler-builtins
Steve Langasek: > [..] > > There is no rust-compiler-builtins package in the Debian archive or in the > NEW queue. It's in NEW. We're aware of all of these issues you're filing bug reports for, and in fact there are many more than the ones you're filing for. These reports are not actually helpful, they just increase the amount of work we have to do fixing the packages. Therefore, I'm going to close all of these bugs now to save time. All of them are getting fixed as part of the normal migration process. They are also redundant, britney is already preventing these packages from migration, adding a "serious" bug therefore achieves nothing except extra paperwork for packagers in closing bug reports. X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git
Processed: fixed 948647 in 0.3.40-3
Processing commands for cont...@bugs.debian.org: > fixed 948647 0.3.40-3 Bug #948647 [src:rust-backtrace] rust-backtrace depends on non-existent librust-compiler-builtins The source 'rust-backtrace' and version '0.3.40-3' do not appear to match any binary packages Marked as fixed in versions rust-backtrace/0.3.40-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 948647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948647 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 948438
Processing commands for cont...@bugs.debian.org: > tags 948438 + ftbfs Bug #948438 [src:ball] ball ftbfs in unstable Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 948438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#936238: marked as done (brial: Python2 removal in sid/bullseye)
Your message dated Sat, 11 Jan 2020 13:49:28 + with message-id and subject line Bug#936238: fixed in brial 1.2.6-1 has caused the Debian Bug report #936238, regarding brial: 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.) -- 936238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:brial Version: 1.2.4-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:brial 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: brial Source-Version: 1.2.6-1 We believe that the bug you reported is fixed in the latest version of brial, 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. Julien Puydt (supplier of updated brial package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 11 Jan 2020 14:01:01 +0100 Source: brial Architecture: source Version: 1.2.6-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Julien Puydt Closes: 896218 936238 Changes: brial (1.2.6-1) unstable; urgency=medium . * New upstream release. * Drop the Python 2 package (Closes: #936238). * Make the autopkgtest depend on sagemath (Closes: #896218). * Add a patch for a tighter config.h.in (makes lintian happier). * Enable hardening flags. Checksums-Sha1: 466a4621a7ba79ca1ada12525d2971ada0cddf02 2418 brial_1.2.6-1.dsc f31ff413f94ed0d1091f4a0d80589345b82de07b 1721693 brial_1.2.6.orig.tar.gz 63c4c4ca1efbfd56c74cda9977bcc8599859346c 7128 brial_1.2.6-1.debian.tar.xz 67b7a1bba741b730951f7a16e64efcf60bb3a1f9 8657 brial_1.2.6-1_source.buildinfo Checksums-Sha256: 1ff6ba50162468a8b34bc21bc370840baf5b97aa9e4fe6badda67ccd64264eed 2418 brial_1.2.6-1.dsc b64d6f0ad75925d7860ccdd142441e90fcb1d3ebef0d9dc8fd619dc73531febd 1721693 brial
Bug#945602: closed by Gürkan Myczko (Bug#945602: fixed in qwinff 0.2.1+git20191128-1)
Dear Gürkan, can you confirm the proposed patch is working? And confirm an upload to proposed-updates would be ok? I really hope to see this fix land in proposed-updates/the next point release. Thank you Le jeu. 28 nov. 2019 à 14:57, Debian Bug Tracking System a écrit : > > This is an automatic notification regarding your Bug report > which was filed against the qwinff package: > > #945602: wrong path for constants.xml/presets.xml prevent the program from > starting > > It has been closed by Gürkan Myczko . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Gürkan Myczko > by > replying to this email. > > > -- > 945602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945602 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > > -- Forwarded message -- > From: "Gürkan Myczko" > To: 945602-cl...@bugs.debian.org > Cc: > Bcc: > Date: Thu, 28 Nov 2019 14:53:00 + > Subject: Bug#945602: fixed in qwinff 0.2.1+git20191128-1 > Source: qwinff > Source-Version: 0.2.1+git20191128-1 > > We believe that the bug you reported is fixed in the latest version of > qwinff, 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. > Gürkan Myczko (supplier of updated qwinff package) > > (This message was generated automatically at their request; if you > believe that there is a problem with it please contact the archive > administrators by mailing ftpmas...@ftp-master.debian.org) > > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Format: 1.8 > Date: Thu, 28 Nov 2019 10:31:49 +0100 > Source: qwinff > Architecture: source > Version: 0.2.1+git20191128-1 > Distribution: unstable > Urgency: medium > Maintainer: Gürkan Myczko > Changed-By: Gürkan Myczko > Closes: 945602 > Changes: > qwinff (0.2.1+git20191128-1) unstable; urgency=medium > . >* New upstream version. (Closes: #945602) >* Bump standards version to 4.4.1. > Checksums-Sha1: > c435f8e800a824d82f2a63f8e7d48accae887ec3 1822 qwinff_0.2.1+git20191128-1.dsc > a695f1968edd8cf234e45ff9aad42f74e46e16b1 640284 > qwinff_0.2.1+git20191128.orig.tar.gz > 5d2639a410564a41aeff5e905b7b8d5d2f9cdb83 66484 > qwinff_0.2.1+git20191128-1.debian.tar.xz > f916869c629b06ba198e1a3b088e0136d9fc47cf 5512 > qwinff_0.2.1+git20191128-1_source.buildinfo > Checksums-Sha256: > 9461b39731c0a8dd591d9d2ed5ce538e336baee05a913e7cd35bd843de143499 1822 > qwinff_0.2.1+git20191128-1.dsc > a4eb6143ed1e407df8d23766ba254aa6bee0471c53d3a4ba42cbef2b7ab6a3b4 640284 > qwinff_0.2.1+git20191128.orig.tar.gz > 0987db200a7b5d12cf81e4f453bcafae2925dc9ff434412953900440ee54bf04 66484 > qwinff_0.2.1+git20191128-1.debian.tar.xz > 50134b28e5aab8adf6ea553c9288314b5234112232eedceec6711043f2f33b21 5512 > qwinff_0.2.1+git20191128-1_source.buildinfo > Files: > 08d0bea0f7ca208f85c03652c2e13190 1822 video optional > qwinff_0.2.1+git20191128-1.dsc > 0307673249ac65c683206226f88f13b2 640284 video optional > qwinff_0.2.1+git20191128.orig.tar.gz > 49af85a9edea7adfbec7f9ac654439ae 66484 video optional > qwinff_0.2.1+git20191128-1.debian.tar.xz > 6fbc2f216a9c4dc746ce5c48c2299ed2 5512 video optional > qwinff_0.2.1+git20191128-1_source.buildinfo > > -BEGIN PGP SIGNATURE- > > iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl3f0H0ACgkQweDZLphv > fH7ZYg//aZae+iZMxu8xrsn4QgYXdOQD+ZkS2FjFYCxkJyhM0Dg94+hhqKl9oqzI > vhcuBioNWTPnzgmMYhXYyTgoExsmqxbGyCIuUwWBC+kkPpXew2rEW0k3c7S0GILo > CLhTCqZYuy0KW8VPB9ibDNYk4MGZHBSaDDeI9dMfhAwYOn0509/KqPcx8/Cp9jyh > UPHcgYeCN3YarGA3USRRxzlMHTs9x/VbjbBsoUwvJ+yrfnYHJnCTWZKWJ1+ZgFPW > f6m27oRCllAKP4QO7p4hOO5SwpCzaxLk+riGqup+6X6n2A3N1MiJGysam4JV3/VV > Qj6kAhGg7OjkNbRIu+fJulAVHfgpfQLgWhlGAvAfMZWYJhHhHUQUhaBh0IM70Mbj > 8R1q1MOc2ydRLF8HMOCIprQd9kNAQ9JGZGFcn2Yae8qsHIqNk6qPy9v2rgZxD83M > 2zIJXHJ1hA0UszCL1XZO6DKZQEZV8kEAi643MjyJJ3Fpv12L2mz1pK6BMhfdiy5V > trXjV6ixsHbfNXhFVkxAXswIn3w9XvM+mYEAHBrEE3hXFBX1TSPhtkQyLh0gX3vn > OrDq5nbqC00/DhKympwxf1Z2hhWO0xyFGXgAZjDBPFra/RFEv/MRQOJrE3+5UftT > Bk52I++lRxi0YkAtNLdCq6S7Wf6y1MpZPa8UuNVwH+vK0a/W8v4= > =7dsM > -END PGP SIGNATURE- > > > -- Forwarded message -- > From: nodiscc > To: sub...@bugs.debian.org > Cc: > Bcc: > Date: Wed, 27 Nov 2019 20:06:40 + > Subject: wrong path for constants.xml/presets.xml prevent the program from > starting > Package: qwinff > Version: 0.2.1-1 > Severity: grave > > Steps to reproduce the problem: > - run qwinff from the desktop launcher of from a terminal emulator > > What happens: > - An error dialog is shown with the message "Cannot load > /home/user/
Bug#937040: marked as done (mgltools-visionlibraries: Python2 removal in sid/bullseye)
Your message dated Sat, 11 Jan 2020 13:42:37 + with message-id and subject line Bug#948580: Removed package(s) from unstable has caused the Debian Bug report #937040, regarding mgltools-visionlibraries: 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.) -- 937040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mgltools-visionlibraries Version: 1.5.7-3 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:mgltools-visionlibraries If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.5.7-3+rm Dear submitter, as the package mgltools-visionlibraries has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/948580 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#937644: marked as done (python-cherrypy: Python2 removal in sid/bullseye)
Your message dated Sat, 11 Jan 2020 13:44:46 + with message-id and subject line Bug#948644: Removed package(s) from unstable has caused the Debian Bug report #937644, regarding python-cherrypy: 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.) -- 937644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-cherrypy Version: 2.3.0-5 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-cherrypy If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 2.3.0-5+rm Dear submitter, as the package python-cherrypy has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/948644 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#937036: marked as done (mgltools-symserv: Python2 removal in sid/bullseye)
Your message dated Sat, 11 Jan 2020 13:42:14 + with message-id and subject line Bug#948578: Removed package(s) from unstable has caused the Debian Bug report #937036, regarding mgltools-symserv: 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.) -- 937036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937036 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mgltools-symserv Version: 1.5.7-3 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:mgltools-symserv If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.5.7-3+rm Dear submitter, as the package mgltools-symserv has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/948578 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#938485: marked as done (simpletal: Python2 removal in sid/bullseye)
Your message dated Sat, 11 Jan 2020 13:44:12 + with message-id and subject line Bug#948628: Removed package(s) from unstable has caused the Debian Bug report #938485, regarding simpletal: 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.) -- 938485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938485 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:simpletal Version: 4.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:simpletal If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 4.3-1+rm Dear submitter, as the package simpletal has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/948628 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#947901: marked as done (gnome-js-common: unmaintained upstream since around 2010)
Your message dated Sat, 11 Jan 2020 13:40:01 + with message-id and subject line Bug#948484: Removed package(s) from unstable has caused the Debian Bug report #947901, regarding gnome-js-common: unmaintained upstream since around 2010 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.) -- 947901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947901 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-js-common Version: 0.1.2-2 Severity: serious Tags: upstream wontfix User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs unmaintained-upstream gnome-js-common doesn't appear to be depended on by any other package, and its upstream git repository has been archived, with no significant commits since 2010: https://gitlab.gnome.org/Archive/gnome-js-common It probably shouldn't be in future Debian stable releases without someone taking over upstream maintenance. Does anyone object to me opening a RM: RoM bug? Thanks, smcv --- End Message --- --- Begin Message --- Version: 0.1.2-2+rm Dear submitter, as the package gnome-js-common has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/948484 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#948538: marked as done (ldm: CVE-2019-20373)
Your message dated Sat, 11 Jan 2020 13:41:21 + with message-id and subject line Bug#948535: Removed package(s) from unstable has caused the Debian Bug report #948538, regarding ldm: CVE-2019-20373 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.) -- 948538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ldm Version: 2:2.18.06-1 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://bugs.launchpad.net/ubuntu/+source/ldm/+bug/1839431 Control: found -1 2:2.2.18-2 Control: fixed -1 2:2.2.18-2+deb9u1 Control: fixed -1 2:2.18.06-1+deb10u1 For easier tracking of the issue, as there is no CVE assigned (yet). https://bugs.launchpad.net/ubuntu/+source/ldm/+bug/1839431 (not yet public) fixed via https://git.launchpad.net/~ltsp-upstream/ltsp/+git/ldm/commit/?id=c351ac69ef63ed6c84221cef73e409059661b8ba . DSA-4601-1 got released for the issue. Regards, Salvatore --- End Message --- --- Begin Message --- Version: 2:2.18.06-1+rm Dear submitter, as the package ldm has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/948535 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#948369: marked as done (RM: fw4spl -- ROM; fw4spl is replaced by sight)
Your message dated Sat, 11 Jan 2020 13:39:21 + with message-id and subject line Bug#948369: Removed package(s) from unstable has caused the Debian Bug report #948369, regarding RM: fw4spl -- ROM; fw4spl is replaced by sight 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.) -- 948369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fw4spl Version: 17.2.0-2 Severity: serious Tags: bullseye sid fw4spl seems to be replaced by sight, should this package get removed? --- End Message --- --- Begin Message --- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: fw4spl | 17.2.0-2 | source, amd64, i386 --- Reason --- ROM; fw4spl is replaced by sight -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 948...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/948369 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#937020: marked as done (mgltools-cadd: Python2 removal in sid/bullseye)
Your message dated Sat, 11 Jan 2020 13:41:47 + with message-id and subject line Bug#948577: Removed package(s) from unstable has caused the Debian Bug report #937020, regarding mgltools-cadd: 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.) -- 937020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mgltools-cadd Version: 1.5.7-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:mgltools-cadd If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.5.7-4+rm Dear submitter, as the package mgltools-cadd has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/948577 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#938730: marked as done (twill: Python2 removal in sid/bullseye)
Your message dated Sat, 11 Jan 2020 13:33:36 + with message-id and subject line Bug#920398: Removed package(s) from unstable has caused the Debian Bug report #938730, regarding twill: 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.) -- 938730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938730 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:twill Version: 0.9-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:twill If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.9-4+rm Dear submitter, as the package twill has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/920398 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#946242: fatal: privsep_preauth: preauth child terminated by signal 31
Ian Jackson (CCed) just ran into this and we debugged it together on
IRC. This turns out to be a variant of https://bugs.debian.org/941663
that only affects certain architectures, because glibc implements
shmget/shmat/shmdt using the ipc syscall on certain architectures. For
example, shmget is:
int
shmget (key_t key, size_t size, int shmflg)
{
#ifdef __ASSUME_DIRECT_SYSVIPC_SYSCALLS
return INLINE_SYSCALL_CALL (shmget, key, size, shmflg, NULL);
#else
return INLINE_SYSCALL_CALL (ipc, IPCOP_shmget, key, size, shmflg, NULL);
#endif
}
And:
sysdeps/unix/sysv/linux/i386/kernel-features.h:#undef
__ASSUME_DIRECT_SYSVIPC_SYSCALLS
sysdeps/unix/sysv/linux/kernel-features.h:#define
__ASSUME_DIRECT_SYSVIPC_SYSCALLS 1
sysdeps/unix/sysv/linux/m68k/kernel-features.h:#undef
__ASSUME_DIRECT_SYSVIPC_SYSCALLS
sysdeps/unix/sysv/linux/mips/kernel-features.h:# undef
__ASSUME_DIRECT_SYSVIPC_SYSCALLS
sysdeps/unix/sysv/linux/powerpc/kernel-features.h:#undef
__ASSUME_DIRECT_SYSVIPC_SYSCALLS
sysdeps/unix/sysv/linux/s390/kernel-features.h:#undef
__ASSUME_DIRECT_SYSVIPC_SYSCALLS
sysdeps/unix/sysv/linux/sh/kernel-features.h:#undef
__ASSUME_DIRECT_SYSVIPC_SYSCALLS
sysdeps/unix/sysv/linux/sparc/kernel-features.h:#undef
__ASSUME_DIRECT_SYSVIPC_SYSCALLS
I think a fix for this that applies to buster would be:
diff --git a/sandbox-seccomp-filter.c b/sandbox-seccomp-filter.c
index e8f31555e..121760418 100644
--- a/sandbox-seccomp-filter.c
+++ b/sandbox-seccomp-filter.c
@@ -134,6 +134,9 @@ static const struct sock_filter preauth_insns[] = {
#ifdef __NR_fstat64
SC_DENY(__NR_fstat64, EACCES),
#endif
+#ifdef __NR_ipc
+ SC_DENY(__NR_ipc, EACCES),
+#endif
#ifdef __NR_open
SC_DENY(__NR_open, EACCES),
#endif
I have some other things to do this weekend, but I'll chase this up with
upstream and arrange for this to get into appropriate Debian packages.
--
Colin Watson [cjwat...@debian.org]
Bug#948660: python3-ns3 depends/suggests on Python2 modules
Package: python3-ns3 Version: 3.30+dfsg-3 Severity: serious Tags: sid bullseye python3-ns3 depends/suggests on Python2 modules, python-pygraphviz and python-kiwi.
Processed: ping-pong
Processing commands for cont...@bugs.debian.org: > severity 945729 normal Bug #945729 [src:zomg] zomg: Python2 removal in sid/bullseye Severity set to 'normal' from 'serious' > quit Stopping processing here. Please contact me if you need assistance. -- 945729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945729 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947176: libiptc.pc non-functional
Hi Arturo On Sun, 22 Dec 2019 15:06:02 +0100 Michael Biebl wrote: > > 1/ Have a single libiptc-dev package which contains all development files > 2/ Have a libip6tc-dev package which contains all development files > related to libip6tc, have a libip4tc-dev package which contains all > development files related to libip4tc and have libiptc-dev (convenience) > package which contains libiptc.pc and depends on both libip6tc-dev and > libip4tc-dev > Have you decided how you want to proceed from here? Would welcome your feedback. Regards, Michael signature.asc Description: OpenPGP digital signature
Bug#947463: bio-tradis: autopkgtest regression: Use of uninitialized value $total_uis (and lots of mv: cannot stat '/tmp/aut.....)
Yes, I have a fix for that at https://salsa.debian.org/med-team/bio-tradis/commit/8b810e2d293ce99653b899337da3aa8d413fae48 I need someone to either upload 1.4.5+dfsg2-1 or give me upload privileges: gbp clone g...@salsa.debian.org:med-team/bio-tradis or dcut dm --uid 724D609337113C710550D7473C26763F6C67E6E2 --allow bio-tradis On Wed, Jan 8, 2020 at 9:15 PM Paul Gevers wrote: > Hi Micheal, > > On Fri, 3 Jan 2020 09:31:43 +0100 Michael Crusoe > wrote: > > > With a recent upload of bio-tradis the autopkgtest of bio-tradis fails > > > in testing when that autopkgtest is run with the binary packages of > > > bio-tradis from unstable. It passes when run with only packages from > > > testing. > > > > Why are we mixing testing scripts and binaries? > > We're not, at least not most of the time. What I meant was that we > tested the autopkgtest of src:bio-tradis from unstable with the > src:bio-tradis binaries from unstable in testing. The idea is to see > what happens if the package in unstable would migrate. > > Paul > > -- Michael R. Crusoe
Bug#948643: apt-file: fails to update
Control: severity -1 important On Sat, Jan 11, 2020 at 01:23:34AM -0500, Anthony M.R. Alvis wrote: > Package: apt-file > Version: 3.2.2 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > I have attached a text file containing what happens after i run sudo apt-file > update; Yup, there is not support in command-not-found for third party repositories using different component naming schemes than Debian or Ubuntu. Needs a workaround. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Processed: Re: Bug#948643: apt-file: fails to update
Processing control commands: > severity -1 important Bug #948643 [command-not-found] apt-file: fails to update Severity set to 'important' from 'grave' -- 948643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948643 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893735: fixed in paraview 5.4.1+dfsg4-2
control: tags -1 patch
Hello, looks like I crafted a patch that builds at least on amd64 arm64 armhf
i386 ppc64el and s390x
Changes:
- disable parallel builds again
- use -g1 to minimize the size of the binaries, to avoid gcc going ICE on armhf
(this might be done only on armhf and where this happens, I did it globally)
- restore and refactor the armhf patch to fix the build.
changes attached:
G.
diff -Nru paraview-5.7.0/debian/changelog paraview-5.7.0/debian/changelog
--- paraview-5.7.0/debian/changelog 2019-12-28 17:21:57.0 +0100
+++ paraview-5.7.0/debian/changelog 2020-01-08 10:20:00.0 +0100
@@ -1,3 +1,16 @@
+paraview (5.7.0-4ubuntu6) focal; urgency=medium
+
+ * Fix build on armhf by restoring a reworked fix_opengl_arm.patch
+
+ -- Gianfranco Costamagna Wed, 08 Jan 2020
10:20:00 +0100
+
+paraview (5.7.0-4ubuntu3) focal; urgency=medium
+
+ * Minimize debug symbols to -g1
+ * Disable parallel builds
+
+ -- Gianfranco Costamagna Mon, 06 Jan 2020
23:16:56 +0100
+
paraview (5.7.0-4) unstable; urgency=medium
[ Gilles Filippini ]
diff -Nru paraview-5.7.0/debian/patches/fix_opengl_arm.patch
paraview-5.7.0/debian/patches/fix_opengl_arm.patch
--- paraview-5.7.0/debian/patches/fix_opengl_arm.patch 2019-12-28
17:21:57.0 +0100
+++ paraview-5.7.0/debian/patches/fix_opengl_arm.patch 2020-01-08
10:20:00.0 +0100
@@ -2,3 +2,119 @@
Description: Use QOpenGLExtraFunctions instead of *3_2, because the
latter is not available on ARM.
Debian-Bug: https://bugs.debian.org/893735
+Reworked by: Gianfranco Costamagna
+Last-Update: 2020-01-08
+
+Index: paraview-5.7.0/VTK/GUISupport/Qt/QVTKOpenGLNativeWidget.cxx
+===
+--- paraview-5.7.0.orig/VTK/GUISupport/Qt/QVTKOpenGLNativeWidget.cxx
paraview-5.7.0/VTK/GUISupport/Qt/QVTKOpenGLNativeWidget.cxx
+@@ -19,7 +19,7 @@
+ #include
+ #include
+ #include
+-#include
++#include
+ #include
+ #include
+ #include
+@@ -232,9 +232,9 @@
+ // before proceeding with blit-ing.
+ this->makeCurrent();
+
+-QOpenGLFunctions_3_2_Core* f =
+-
QOpenGLContext::currentContext()->versionFunctions();
+-if (f)
++QOpenGLFunctions *f = QOpenGLContext::currentContext()->functions();
++QOpenGLExtraFunctions *fx =
QOpenGLContext::currentContext()->extraFunctions();
++if (f && fx)
+ {
+ const QSize deviceSize = this->size() * this->devicePixelRatioF();
+ this->RenderWindowAdapter->blit(
+Index: paraview-5.7.0/VTK/GUISupport/Qt/QVTKOpenGLWindow.cxx
+===
+--- paraview-5.7.0.orig/VTK/GUISupport/Qt/QVTKOpenGLWindow.cxx
paraview-5.7.0/VTK/GUISupport/Qt/QVTKOpenGLWindow.cxx
+@@ -19,7 +19,8 @@
+ #include
+ #include
+ #include
+-#include
++#include
++#include
+ #include
+ #include
+ #include
+@@ -225,9 +225,10 @@
+ // before proceeding with blit-ing.
+ this->makeCurrent();
+
+-QOpenGLFunctions_3_2_Core* f =
+-
QOpenGLContext::currentContext()->versionFunctions();
+-if (f)
++QOpenGLFunctions *f = QOpenGLContext::currentContext()->functions();
++QOpenGLExtraFunctions *fx =
QOpenGLContext::currentContext()->extraFunctions();
++
++if (f && fx)
+ {
+ const QSize deviceSize = this->size() * this->devicePixelRatioF();
+ const auto fmt = this->context()->format();
+Index: paraview-5.7.0/VTK/GUISupport/Qt/QVTKRenderWindowAdapter.cxx
+===
+--- paraview-5.7.0.orig/VTK/GUISupport/Qt/QVTKRenderWindowAdapter.cxx
paraview-5.7.0/VTK/GUISupport/Qt/QVTKRenderWindowAdapter.cxx
+@@ -30,7 +30,7 @@
+ #include
+ #include
+ #include
+-#include
++#include
+ #include
+ #include
+ #include
+@@ -332,17 +332,20 @@
+ {
+ return false;
+ }
+-QOpenGLFunctions_3_2_Core* f =
this->Context->versionFunctions();
+-if (!f)
++QOpenGLFunctions *f = this->Context->functions();
++QOpenGLExtraFunctions *fx = this->Context->extraFunctions();
++if (!f || !fx)
+ {
+ return false;
+ }
+
+ f->glBindFramebuffer(GL_DRAW_FRAMEBUFFER, targetId);
+-f->glDrawBuffer(targetAttachement);
++
++GLenum buffers[] = {targetAttachement};
++fx->glDrawBuffers(1, buffers);
+
+ f->glBindFramebuffer(GL_READ_FRAMEBUFFER, this->FBO->handle());
+-f->glReadBuffer(
++fx->glReadBuffer(
+ left ? this->RenderWindow->GetFrontLeftBuffer() :
this->RenderWindow->GetFrontRightBuffer());
+
+ GLboolean scissorTest = f->glIsEnabled(GL_SCISSOR_TEST);
+@@ -352,7 +355,7 @@
+ }
+
+ auto sourceSize = this->FBO->size();
+-f->glBlitFramebuffer(0, 0, sourceSize.width(), sourceSize.height(),
targetRect.x(),
++fx->glBlitFramebuffer(0, 0, sourceSize.width(), sourceSize.height(),
targetRect.x(),
+ targetRect.y(), targetRect.width(), targetRect.height(),
GL_COLOR_BUFFER_BIT, GL_NEAREST);
+
+ this->clea
Processed: Re: Bug#893735: fixed in paraview 5.4.1+dfsg4-2
Processing control commands: > tags -1 patch Bug #893735 [src:paraview] paraview FTBFS on armel/armhf: QVTKOpenGLWidget.cxx:458:3: error: 'QOpenGLFunctions_3_2_Core' was not declared in this scope Added tag(s) patch. -- 893735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#936872: Fixed in unstable, still debugging build issues
Although this bug has been fixed in unstable for some time, the package isn't migrating due to OCaml-related FTBFS issues on several architectures which I haven't been able to reproduce on porterboxes so far. Cheers, -Hilko
Bug#947001: Bug#947004: S4Vectors Segmentation fault after r-base-core update (Was: Bug#947004: Tests segfaults (since the r-base-core update?))
Hi,
Le ven. 10 janv. 2020 à 00:30, Pages, Herve a écrit :
> Based on the traceback the error happens during evaluation of the 1st
> argument ('target') passed to checkEqualsNumeric(), that is, during
> evaluation of 'runmed(y, 7)'. Since this involves base R code only
> (runmed() is implemented in the stats package) I would say that it's not
> immediately obvious that the problem is in my court.
Thanks Hervé for this.
I just updated how to run Debian autopkgtests [1-2] by replacing:
> LC_ALL=C R --no-save < require("S4Vectors")
> S4Vectors:::.test()
> EOT
with
> LC_ALL=C.UTF-8 R --no-save -e 'BiocGenerics:::testPackage("S4Vectors")'
which seems to be the recommended way to run tests for bioconductor
packages. And now, there is no segfault anymore for S4vectors but
IRanges is still crashing. Should we upload these fixes into
Debian/unstable?
Best,
Dylan
[1]
https://salsa.debian.org/r-pkg-team/r-bioc-s4vectors/commit/51b8ca2571dac1685e748679568edf4463cbfd59
[2]
https://salsa.debian.org/r-pkg-team/r-bioc-iranges/commit/06a76a22fa236f919fc0038c5c01aec35ec2ecda
[3]
https://bioconductor.org/developers/how-to/unitTesting-guidelines/#RUnitConventions
Bug#925749: Debug means -O0
The default mode is -O2, what I mean of release mode is -O0. The debug symbol does not matter.
Bug#947497: marked as done (caffe: depends on python3-leveldb whose removal has been requested)
Your message dated Sat, 11 Jan 2020 08:37:39 + with message-id and subject line Bug#947497: fixed in caffe 1.0.0+git20180821.99bd997-5 has caused the Debian Bug report #947497, regarding caffe: depends on python3-leveldb whose removal has been requested 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.) -- 947497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947497 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: caffe Version: 1.0.0+git20180821.99bd997-4 Severity: serious Justification: uninstallable in testing Control: block 945894 by -1 In #945894, the maintainer of src:python-leveldb writes: > Please remove src:python-leveldb from unstable. Its upstream > discontinued for a long time and there's already an other, maintained > alternative in the archive. --- End Message --- --- Begin Message --- Source: caffe Source-Version: 1.0.0+git20180821.99bd997-5 We believe that the bug you reported is fixed in the latest version of caffe, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 947...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mo Zhou (supplier of updated caffe package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 11 Jan 2020 15:48:56 +0800 Source: caffe Architecture: source Version: 1.0.0+git20180821.99bd997-5 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Mo Zhou Closes: 947497 Changes: caffe (1.0.0+git20180821.99bd997-5) unstable; urgency=medium . * Remove the deprecated python3-leveldb from B-D. (Closes: #947497) * Remove leveldb from python requirements: pyrequire-no-leveldb.patch Checksums-Sha1: 5d875011932ff81d2fc0e3d5c76d577d9ba93125 3112 caffe_1.0.0+git20180821.99bd997-5.dsc ac65b41c4c8361a46423a77631ee5e97e1a5c8cb 15568 caffe_1.0.0+git20180821.99bd997-5.debian.tar.xz a6ad12019e02fe20f5cf3c8896ce19e817f4e13a 19924 caffe_1.0.0+git20180821.99bd997-5_source.buildinfo Checksums-Sha256: b2a218eb016051ded85837fba490b77867c5e3a1f495c28fd366b37b2df00ae1 3112 caffe_1.0.0+git20180821.99bd997-5.dsc e0b9511fc0c12eb69c4148e5ffadb5a5c276027dbe8b8d79c823e7cf7a870cff 15568 caffe_1.0.0+git20180821.99bd997-5.debian.tar.xz 9e056da4fedc77e20e24976e2213feefe76fde7a3681f68a62fe8ffdd51019a9 19924 caffe_1.0.0+git20180821.99bd997-5_source.buildinfo Files: 3f7bee4ffb2d224796819a469f03e10b 3112 science optional caffe_1.0.0+git20180821.99bd997-5.dsc 0fa53af3588f9a5d3d834e1dfb9c6b64 15568 science optional caffe_1.0.0+git20180821.99bd997-5.debian.tar.xz c1b4e2424cd988939c18b09cdac1640a 19924 science optional caffe_1.0.0+git20180821.99bd997-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAl4ZfioRHGx1bWluQGRl Ymlhbi5vcmcACgkQYmRes19oaooynQ//a/r83iIkOCne4b+0be0tfRZUG+JvolqA tR54N6YKIZ84Vbc/GizSRS0I54jcWz5WByzN4j1tBB+fWDCjCMAXizDF7xVILy2y 1SSFnRaqThGFJnuE+ojPni2ljJdj5ConcRR8tTh+Ih6KCGYf4n0Dxj/4QMc2D/JK 5j5Dk0dKftxxphpKq//7S8SNnJVcHf+gRamodV7HAa93fdesBBoU4QXfSMrgSnw2 vm95iIhyppeGnVIeNKqgc4h0z28DhjUq0I+iHvhmjUVGVlm+pTxbkqt5nXfQOlsw Fn5WguJHx1+D053OmqAKMYgsmMAJAVGN92GGkemJNzHsvhQN1RR29dd5suw9brUT eFP0Eive/rCf7vwKu4qsCCLNpUFiCNjqepuMQ+QPiz6QAhT7pQOsbe2N9I+8x1cR Iy7rqUmPn2pQSE54q2u9vmabWt64kaYuMvbpiifDEi+lecrHThQEstkLGItp+QnE eUbKFZmFwbMAZ7h5jXFN0yEsjoYS15hAKqKI1yYCHlLyK4dr3hJWAHE2Xj/bmvFj XJ7Y/qPdWjsSiEP5BD68JdhkVJKN9frTEwUmaP7X7oQmkI1YXhkkkivDlOEW8SRR tjc8nBvIAoT/YWm+SGicpGd8fNK69FffUrnFZnSfDNSal6aJS3XhnNprJk2VImdS 9HpYJQ+/4D0= =WGpp -END PGP SIGNATURE End Message ---
Bug#948643: apt-file: fails to update
Control: reassign -1 command-not-found Control: affects -1 apt-file Anthony M.R. Alvis: > Package: apt-file > Version: 3.2.2 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > I have attached a text file containing what happens after i run sudo apt-file > update; > > [...] The error comes from command-not-found's hook into the apt update process - reassigning accordingly. @Julian: There is a log file in the original report. Note the report appears to come from a "Raspbian GNU/Linux 10 (buster)" in case that helps. Thanks, ~Niels
Processed: Re: Bug#948643: apt-file: fails to update
Processing control commands: > reassign -1 command-not-found Bug #948643 [apt-file] apt-file: fails to update Bug reassigned from package 'apt-file' to 'command-not-found'. No longer marked as found in versions apt-file/3.2.2. Ignoring request to alter fixed versions of bug #948643 to the same values previously set > affects -1 apt-file Bug #948643 [command-not-found] apt-file: fails to update Added indication that 948643 affects apt-file -- 948643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948643 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
