Bug#948195:
Hi jim_p, Same problem I reported in bug #948032 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948032 To downgrade I've written a dirty script for my personal use, if you need it You'll find it in attachment. nvidia-recovery.sh Description: application/shellscript
Bug#948195: nvidia-legacy-340xx-driver: Xorg fails to start with a kernel panic after the upgrade to 340.108-1
Package: nvidia-legacy-340xx-driver Followup-For: Bug #948195 I finally managed to install 340.107-8 from the snapshot repo and, as you can also see in the logs below, there is no issue with it. I am pinning it for now... -- Package-specific info: uname -a: Linux mitsos 5.4.0-1-amd64 #1 SMP Debian 5.4.6-1 (2019-12-27) x86_64 GNU/Linux /proc/version: Linux version 5.4.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 9.2.1 20191130 (Debian 9.2.1-21)) #1 SMP Debian 5.4.6-1 (2019-12-27) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191130 (Debian 9.2.1-21) lspci 'display controller [030?]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:8490] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidia dmesg: [0.315706] Console: colour VGA+ 80x25 [0.747348] pci :01:00.0: vgaarb: setting as boot VGA device [0.747348] pci :01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [0.747348] pci :01:00.0: vgaarb: bridge control possible [0.747348] vgaarb: loaded [0.932809] Linux agpgart interface v0.103 [3.333197] nvidia: loading out-of-tree module taints kernel. [3.333209] nvidia: module license 'NVIDIA' taints kernel. [3.347973] nvidia: module verification failed: signature and/or required key missing - tainting kernel [3.362057] nvidia :01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem [3.363352] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on minor 0 [3.363365] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 [3.849423] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [5.109339] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input17 [5.112939] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input22 [5.113029] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input24 [5.113105] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input25 [ 20.202050] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs Device node permissions: crw-rw+ 1 root video 226, 0 Jan 5 09:31 /dev/dri/card0 crw-rw-rw- 1 root root 195, 0 Jan 5 09:32 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Jan 5 09:32 /dev/nvidiactl /dev/dri/by-path: total 0 lrwxrwxrwx 1 root root 8 Jan 5 09:31 pci-:01:00.0-card -> ../card0 video:*:44:jim OpenGL and NVIDIA library files installed: lrwxrwxrwx 1 root root 15 Jan 5 09:29 /etc/alternatives/glx -> /usr/lib/nvidia lrwxrwxrwx 1 root root 44 Jan 5 09:29 /etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1 lrwxrwxrwx 1 root root 43 Jan 5 09:29 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Jan 5 09:29 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 54 Jan 5 09:29 /etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2 lrwxrwxrwx 1 root root 54 Jan 5 09:29 /etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2 lrwxrwxrwx 1 root root 25 Jan 5 09:29 /etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so lrwxrwxrwx 1 root root 42 Jan 5 09:29 /etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> /etc/nvidia/nvidia-blacklists-nouveau.conf lrwxrwxrwx 1 root root 36 Jan 5 09:29 /etc/alternatives/glx--nvidia-bug-report.sh -> /usr/lib/nvidia/nvidia-bug-report.sh lrwxrwxrwx 1 root root 39 Jan 5 09:29 /etc/alternatives/glx--nvidia-drm-outputclass.conf -> /etc/nvidia/nvidia-drm-outputclass.conf lrwxrwxrwx 1 root root 28 Jan 5 09:29 /etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf lrwxrwxrwx 1 root root 32 Jan 5 09:29 /etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf lrwxrwxrwx 1 root root 29 Jan 5 09:29 /etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so lrwxrwxrwx 1 root root 28 Jan 5 09:27 /etc/alternatives/nvidia -> /usr/lib/nvidia/legacy-340xx lrwxrwxrwx 1 root root 57 Jan 5 09:27 /etc/alternatives/nvidia--libEGL.so.1-x86_64-linux-gnu
Bug#947339: marked as done (RM: slingshot -- RoQA; python2-only; upstream dormant since 8+ years)
Your message dated Sun, 05 Jan 2020 07:27:22 + with message-id and subject line Bug#947339: Removed package(s) from unstable has caused the Debian Bug report #947339, regarding RM: slingshot -- RoQA; python2-only; upstream dormant since 8+ years 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.) -- 947339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: slingshot Severity: serious Hello, iI think there are several issues with slingshot: - python2-only package - upstream dormant since 8+ years - no updates on https://github.com/ryanakca/slingshot/issues/9 since Aug 9 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 slingshot depends on: ii fonts-freefont-ttf 20120503-9 ii python 2.7.16-1 pn python-pygame slingshot recommends no packages. slingshot 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: slingshot | 0.9-2 | source, all --- Reason --- RoQA; python2-only; upstream dormant since 8+ years -- 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 947...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/947339 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#936573: marked as done (fusionforge: Python2 removal in sid/bullseye)
Your message dated Sun, 05 Jan 2020 07:30:48 + with message-id and subject line Bug#947890: Removed package(s) from unstable has caused the Debian Bug report #936573, regarding fusionforge: 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.) -- 936573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936573 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:fusionforge Version: 6.0.5-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:fusionforge 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: 6.0.5-2+rm Dear submitter, as the package fusionforge 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/947890 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#884264: marked as done (fusionforge-web: fails to install: /usr/share/fusionforge/post-install.d/web/web.sh: line 126: /etc/httpd/conf.modules.d/00-macro.conf: No such file or directory)
Your message dated Sun, 05 Jan 2020 07:30:48 + with message-id and subject line Bug#947890: Removed package(s) from unstable has caused the Debian Bug report #884264, regarding fusionforge-web: fails to install: /usr/share/fusionforge/post-install.d/web/web.sh: line 126: /etc/httpd/conf.modules.d/00-macro.conf: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 884264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fusionforge-web Version: 6.0.5-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Selecting previously unselected package fusionforge-web. (Reading database ... (Reading database ... 13397 files and directories currently installed.) Preparing to unpack .../fusionforge-web_6.0.5-2_all.deb ... Unpacking fusionforge-web (6.0.5-2) ... Setting up fusionforge-web (6.0.5-2) ... PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; FFError has a deprecated constructor in /usr/share/fusionforge/common/include/FFError.class.php on line 36 PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; FFError has a deprecated constructor in /usr/share/fusionforge/common/include/FFError.class.php on line 36 PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; FFError has a deprecated constructor in /usr/share/fusionforge/common/include/FFError.class.php on line 36 PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; FFError has a deprecated constructor in /usr/share/fusionforge/common/include/FFError.class.php on line 36 PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; FFError has a deprecated constructor in /usr/share/fusionforge/common/include/FFError.class.php on line 36 PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; FFError has a deprecated constructor in /usr/share/fusionforge/common/include/FFError.class.php on line 36 PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; FFError has a deprecated constructor in /usr/share/fusionforge/common/include/FFError.class.php on line 36 PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; FFError has a deprecated constructor in /usr/share/fusionforge/common/include/FFError.class.php on line 36 PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; FFError has a deprecated constructor in /usr/share/fusionforge/common/include/FFError.class.php on line 36 PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; FFError has a deprecated constructor in /usr/share/fusionforge/common/include/FFError.class.php on line 36 PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; FFError has a deprecated constructor in /usr/share/fusionforge/common/include/FFError.class.php on line 36 PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; FFError has a deprecated constructor in /usr/share/fusionforge/common/include/FFError.class.php on line 36 PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; FFError has a deprecated constructor in /usr/share/fusionforge/common/include/FFError.class.php on line 36 PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; FFError has a deprecated constructor in /usr/share/fusionforge/common/include/FFError.class.php on line 36 PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; FFError has a deprecated constructor in /usr/share/fusionforge/common/include/FFError.class.php on line 36 PHP Deprecated: Methods with the same name as their class will not
Bug#941869: marked as done (cherrytree: Depends on unmaintained pygtk)
Your message dated Sun, 05 Jan 2020 07:26:53 + with message-id and subject line Bug#947338: Removed package(s) from unstable has caused the Debian Bug report #941869, regarding cherrytree: Depends on unmaintained pygtk to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 941869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cherrytree Version: 0.37.6-1.1 Severity: serious Control: block 885135 by -1 User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid bullseye pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. Also, it uses Python2 and Python2 is being removed from Debian. The way forward is to port your app to use GObject Introspection bindings. For more information on GObject Introspection see [1] and [2]. Please try to do this before the Debian 11 "Bullseye" release as we're going to remove pygtk this cycle. If you have any question don't hesitate to ask. [1] https://wiki.gnome.org/Projects/GObjectIntrospection [2] https://wiki.gnome.org/Projects/PyGObject On behalf of the Debian GNOME team, Jeremy Bicha --- End Message --- --- Begin Message --- Version: 0.37.6-1.1+rm Dear submitter, as the package cherrytree 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/947338 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#947338: marked as done (RM: cherrytree -- RoQA; python2-only; depends on pygtk/gtksourceview, deprecated; upstream is rewriting it in C++, so there's no hope for a py3k port)
Your message dated Sun, 05 Jan 2020 07:26:46 + with message-id and subject line Bug#947338: Removed package(s) from unstable has caused the Debian Bug report #947338, regarding RM: cherrytree -- RoQA; python2-only; depends on pygtk/gtksourceview, deprecated; upstream is rewriting it in C++, so there's no hope for a py3k port 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.) -- 947338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cherrytree Severity: serious Hello, i believe there are several issues with cherrytree: - python2-only application - depends on pygtk, deprecated - depends on gtksourceview, deprecated - upstream is rewriting it in C++, so there's no hope for a py3k port i think it's time to remove it (and eventuall re-introduce it in Debian once the C++ port is completed); if i dont hear back within a week with a good reason to keep this package in Debian, i'll file for it's 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 cherrytree depends on: ii p7zip-full 16.02+dfsg-6 ii python 2.7.16-1 ii python-chardet 3.0.4-3 ii python-dbus1.2.8-3 pn python-enchant ii python-gtk22.24.0-6 pn python-gtksourceview2 cherrytree recommends no packages. cherrytree 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: cherrytree | 0.37.6-1.1 | source, all --- Reason --- RoQA; python2-only; depends on pygtk/gtksourceview, deprecated; upstream is rewriting it in C++, so there's no hope for a py3k port -- 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 947...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/947338 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#937719: marked as done (python-duckduckgo2: Python2 removal in sid/bullseye)
Your message dated Sun, 05 Jan 2020 07:31:26 + with message-id and subject line Bug#947940: Removed package(s) from unstable has caused the Debian Bug report #937719, regarding python-duckduckgo2: 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.) -- 937719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-duckduckgo2 Version: 0.242+git20151019-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-duckduckgo2 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.242+git20151019-2+rm Dear submitter, as the package python-duckduckgo2 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/947940 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#946183: marked as done (Should fusionforge be removed?)
Your message dated Sun, 05 Jan 2020 07:30:48 + with message-id and subject line Bug#947890: Removed package(s) from unstable has caused the Debian Bug report #946183, regarding Should fusionforge be removed? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 946183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fusionforge Severity: serious There hasn't been an upload since two years and fusionforge missed the last two stable releases and has gathered five RC bugs at this point. Should it be removed? Cheers, Moritz --- End Message --- --- Begin Message --- Version: 6.0.5-2+rm Dear submitter, as the package fusionforge 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/947890 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#878698: marked as done (pygtksourceview: keep out of testing)
Your message dated Sun, 05 Jan 2020 07:30:00 + with message-id and subject line Bug#947854: Removed package(s) from unstable has caused the Debian Bug report #878698, regarding pygtksourceview: keep out of testing 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.) -- 878698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878698 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pygtksourceview Severity: serious It is high time that we remove pygtksourceview from testing. It's completely dead upstream in favor of the gobject-introspection bindings, gir1.2-gtksource-3.0. Remaining reverse dependencies should be ported to use that. Emilio -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.12.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Version: 2.10.1-3+rm Dear submitter, as the package pygtksourceview 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/947854 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#936297: marked as done (cherrytree: Python2 removal in sid/bullseye)
Your message dated Sun, 05 Jan 2020 07:26:53 + with message-id and subject line Bug#947338: Removed package(s) from unstable has caused the Debian Bug report #936297, regarding cherrytree: 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.) -- 936297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936297 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:cherrytree Version: 0.37.6-1.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:cherrytree 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.37.6-1.1+rm Dear submitter, as the package cherrytree 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/947338 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#789773: marked as done (fusionforge-shell: modifies conffiles (policy 10.7.3): /etc/pam.d/sshd)
Your message dated Sun, 05 Jan 2020 07:30:48 + with message-id and subject line Bug#947890: Removed package(s) from unstable has caused the Debian Bug report #789773, regarding fusionforge-shell: modifies conffiles (policy 10.7.3): /etc/pam.d/sshd 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.) -- 789773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789773 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fusionforge-shell Version: 6.0.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies conffiles. And this is not even a conffile shipped by your package. This is forbidden by the policy, see https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: "[...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time)." Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: "[...] must not ask unnecessary questions (particularly during upgrades) [...]" If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also https://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): 2m49.1s ERROR: FAIL: debsums reports modifications inside the chroot: /etc/pam.d/sshd cheers, Andreas fusionforge-shell_6.0.1-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Version: 6.0.5-2+rm Dear submitter, as the package fusionforge 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/947890 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#846219: marked as done (Missing runtime dependencies (former libarc-php, libgraphite-php and php-http))
Your message dated Sun, 05 Jan 2020 07:30:48 + with message-id and subject line Bug#947890: Removed package(s) from unstable has caused the Debian Bug report #846219, regarding Missing runtime dependencies (former libarc-php, libgraphite-php and php-http) 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.) -- 846219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:fusionforge Version: 6.0.4+20160504-1 Severity: grave Dear maintainers, fusionforge uses PHP5-only libraries that are orphaned and they are going to be removed as part of src:php5 removal from Debian: - libgraphite-php (RM #846073) - fusionforge-plugin-admssw - libarc-php (RM #846106) - libarc-php (RM #846106) - fusionforge-plugin-admssw (via libgraphite-php) - fusionforge-plugin-doaprdf - fusionforge-plugin-extsubproj You can either adopt those libraries and port them to PHP 7.0 (or just verify they work with PHP 7.0) or remove affected plugins. Cheers, Ondrej -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-rc5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_DK.utf8, LC_CTYPE=en_DK.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Version: 6.0.5-2+rm Dear submitter, as the package fusionforge 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/947890 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#937453: marked as done (pygtksourceview: Python2 removal in sid/bullseye)
Your message dated Sun, 05 Jan 2020 07:30:00 + with message-id and subject line Bug#947854: Removed package(s) from unstable has caused the Debian Bug report #937453, regarding pygtksourceview: 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.) -- 937453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pygtksourceview Version: 2.10.1-3 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:pygtksourceview 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.10.1-3+rm Dear submitter, as the package pygtksourceview 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/947854 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#822586: marked as done (cherrytree: depends on python-gtksourceview2 which is deprecated)
Your message dated Sun, 05 Jan 2020 07:26:53 + with message-id and subject line Bug#947338: Removed package(s) from unstable has caused the Debian Bug report #822586, regarding cherrytree: depends on python-gtksourceview2 which is deprecated 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.) -- 822586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cherrytree Severity: important Tags: sid stretch User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtksourceview Hi, cherrytree depends on python-gtksourceview2, which is long deprecated and going to be removed from the archive. cherrytree should switch to using the GObject Introspection bindings for gtksourceview, gir1.2-gtksource-3.0. This would mean switching to GObject Introspection for other bindings as well, e.g. GLib and GTK+ 3. For more information on GObject Introspection see [1] and [2]. Please try to do this before the Stretch release as we're going to try to remove it this cycle. If you have any question don't hesitate to ask. Emilio [1] https://wiki.gnome.org/action/show/Projects/GObjectIntrospection [2] https://wiki.gnome.org/action/show/Projects/PyGObject --- End Message --- --- Begin Message --- Version: 0.37.6-1.1+rm Dear submitter, as the package cherrytree 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/947338 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#867787: marked as done (cherrytree: Changes sometimes not saved)
Your message dated Sun, 05 Jan 2020 07:26:53 + with message-id and subject line Bug#947338: Removed package(s) from unstable has caused the Debian Bug report #867787, regarding cherrytree: Changes sometimes not saved 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.) -- 867787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867787 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cherrytree Version: 0.37.6-1 Severity: important Dear Maintainer, If more the one copy of Cherry Tree is open at a time - Auto save sometimes fails. - Changes to the the 2nd instance of Cherry Tree are not always saved to disk, even though the save button was clicked, and Cherry Tree was closed out. - Given the above, the program should not allow more then one instance of Cherry Tree per session. -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) 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 cherrytree depends on: ii p7zip-full 16.02+dfsg-3 ii python 2.7.13-2 ii python-appindicator0.4.92-4 ii python-chardet 2.3.0-2 ii python-dbus1.2.4-1+b1 ii python-enchant 1.6.7-1 ii python-gtk22.24.0-5.1 ii python-gtksourceview2 2.10.1-3 cherrytree recommends no packages. cherrytree suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 0.37.6-1.1+rm Dear submitter, as the package cherrytree 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/947338 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#789772: marked as done (fusionforge-mta-exim4: modifies conffiles (policy 10.7.3): /etc/exim4/exim4.conf.template /etc/exim4/conf.d/main/01_exim4-config_listmacrosdefs)
Your message dated Sun, 05 Jan 2020 07:30:48 + with message-id and subject line Bug#947890: Removed package(s) from unstable has caused the Debian Bug report #789772, regarding fusionforge-mta-exim4: modifies conffiles (policy 10.7.3): /etc/exim4/exim4.conf.template /etc/exim4/conf.d/main/01_exim4-config_listmacrosdefs 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.) -- 789772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789772 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fusionforge-mta-exim4 Version: 6.0.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies conffiles. And these are not even conffiles shipped by your package. This is forbidden by the policy, see https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: "[...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time)." Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: "[...] must not ask unnecessary questions (particularly during upgrades) [...]" If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also https://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): 0m52.1s ERROR: FAIL: debsums reports modifications inside the chroot: /etc/exim4/exim4.conf.template /etc/exim4/conf.d/main/01_exim4-config_listmacrosdefs cheers, Andreas fusionforge-mta-exim4_6.0.1-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Version: 6.0.5-2+rm Dear submitter, as the package fusionforge 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/947890 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 ---
Processed (with 1 error): fixed in 0.12.0+dfsg-2
Processing commands for cont...@bugs.debian.org: > fixed 945327 0.12.0+dfsg-2 Bug #945327 [src:python-pomegranate] python-pomegranate ftbfs in unstable Failed to add fixed on 945327: failed to get lock on /srv/bugs.debian.org/spool/debbugs.trace.lock -- Unable to lock /srv/bugs.debian.org/spool/debbugs.trace.lock Resource temporarily unavailable. Unable to lock /srv/bugs.debian.org/spool/debbugs.trace.lock Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/debbugs.trace.lock Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/debbugs.trace.lock Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/debbugs.trace.lock Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/debbugs.trace.lock Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/debbugs.trace.lock Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/debbugs.trace.lock Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/debbugs.trace.lock Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/debbugs.trace.lock Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. at /usr/local/lib/site_perl/Debbugs/Common.pm line 650. > -- Stopping processing here. Please contact me if you need assistance. -- Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#936605: marked as done (gevent-socketio: Python2 removal in sid/bullseye)
Your message dated Sun, 05 Jan 2020 07:22:19 + with message-id and subject line Bug#931404: Removed package(s) from unstable has caused the Debian Bug report #936605, regarding gevent-socketio: 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.) -- 936605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936605 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gevent-socketio Version: 0.3.6-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:gevent-socketio 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.3.6-4+rm Dear submitter, as the package gevent-socketio 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/931404 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#936660: marked as done (grib-api: Python2 removal in sid/bullseye)
Your message dated Sun, 05 Jan 2020 07:22:56 + with message-id and subject line Bug#932208: Removed package(s) from unstable has caused the Debian Bug report #936660, regarding grib-api: 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.) -- 936660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936660 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:grib-api Version: 1.28.0-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:grib-api 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.28.0-2+rm Dear submitter, as the package grib-api 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/932208 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#655465: marked as done (No thumbnails created in Gnome 3.2.1)
Your message dated Sun, 05 Jan 2020 07:21:54 + with message-id and subject line Bug#930248: Removed package(s) from unstable has caused the Debian Bug report #655465, regarding No thumbnails created in Gnome 3.2.1 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.) -- 655465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-xcf-thumbnailer Version: 1.0-1.1 Hello, I installed Gnome-xcf-thumbnailer-1.0-1.1, logged out and back in again. No xcf files were thumbnailed. I do not have Totem installed. There was a similar problem with Ffmpeg-thumbnailer in Wheezy as well and I used the same fix. I created a file in /usr/share/thumbnailers, called "gnome-xcf.thumbnailer". With: [Thumbnailer Entry] TryExec=gnome-xcf-thumbnailer Exec=gnome-xcf-thumbnailer %i %o MimeType=image/x-compressed-xcf;image/x-xcf; I'm not a programmer, but it seems to work ok. I hope this helps. Thank you Adamj Below I have included the results of running: $ reportbug --template reportbug. Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: adamj To: Debian Bug Tracking System Subject: gnome-xcf-thumbnailer: No thumbnails created in Gnome 3.2.1 Bcc: adamj Package: gnome-xcf-thumbnailer Version: 1.0-1.1 Severity: important Hello, I installed Gnome-xcf-thumbnailer-1.0-1.1, logged out and back in again. No xcf files were thumbnailed. There was a similar problem with Ffmpeg-thumbnailer in Wheezy as well and I used the same fix. I created a file in /usr/share/thumbnailers, called "gnome-xcf.thumbnailer". With: [Thumbnailer Entry] TryExec=gnome-xcf-thumbnailer Exec=gnome-xcf-thumbnailer %i %o MimeType=image/x-compressed-xcf;image/x-xcf; I'm not a programmer, but it seems to work ok. I hope this helps. Thank you Adamj -- System Information: Debian Release: wheezy/sid APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-xcf-thumbnailer depends on: ii gconf22.32.4-1 ii libc6 2.13-23 ii libglib2.0-0 2.30.2-4 ii libpng12-01.2.46-3 gnome-xcf-thumbnailer recommends no packages. gnome-xcf-thumbnailer suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 1.0-1.2+rm Dear submitter, as the package gnome-xcf-thumbnailer 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/930248 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#886072: marked as done (gnome-xcf-thumbnailer: Depends on gconf)
Your message dated Sun, 05 Jan 2020 07:21:54 + with message-id and subject line Bug#930248: Removed package(s) from unstable has caused the Debian Bug report #886072, regarding gnome-xcf-thumbnailer: Depends on gconf 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.) -- 886072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886072 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-xcf-thumbnailer Version: 1.0-1.2 Severity: important User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs gconf Tags: sid buster Your package depends or build-depends on gconf, but gconf will be removed from Debian soon. gconf's last release was about 5 years ago. It has been replaced by gsettings (provided in Debian by source glib2.0 ) References -- https://developer.gnome.org/gio/stable/ch34.html https://developer.gnome.org/gio/stable/GSettings.html On behalf of the Debian GNOME team, Jeremy Bicha --- End Message --- --- Begin Message --- Version: 1.0-1.2+rm Dear submitter, as the package gnome-xcf-thumbnailer 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/930248 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#925707: marked as done (grib-api: ftbfs with GCC-9)
Your message dated Sun, 05 Jan 2020 07:22:56 +
with message-id
and subject line Bug#932208: Removed package(s) from unstable
has caused the Debian Bug report #925707,
regarding grib-api: ftbfs with GCC-9
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
925707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925707
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:grib-api
Version: 1.28.0-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/grib-api_1.28.0-2_unstable_gcc9.log
The last lines of the build log are at the end of this report.
To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html
GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.
[...]
| fdopen
/<>/debian/build-python3.7/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8:19:
note: each undeclared identifier is reported only once for each function it
appears in
make[3]: *** [CMakeFiles/cmTC_f56bb.dir/build.make:66:
CMakeFiles/cmTC_f56bb.dir/CheckSymbolExists.c.o] Error 1
make[3]: Leaving directory
'/<>/debian/build-python3.7/CMakeFiles/CMakeTmp'
make[2]: *** [Makefile:121: cmTC_f56bb/fast] Error 2
make[2]: Leaving directory
'/<>/debian/build-python3.7/CMakeFiles/CMakeTmp'
File
/<>/debian/build-python3.7/CMakeFiles/CMakeTmp/CheckSymbolExists.c:
/* */
#include
int main(int argc, char** argv)
{
(void)argv;
#ifndef funopen
return ((int*)(&funopen))[argc];
#else
(void)argc;
return 0;
#endif
}
Performing C SOURCE FILE Test IEEE_BE failed with the following compile output:
Change Dir: /<>/debian/build-python3.7/CMakeFiles/CMakeTmp
Run Build Command:"/usr/bin/make" "cmTC_0cb99/fast"
make[2]: Entering directory
'/<>/debian/build-python3.7/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_0cb99.dir/build.make
CMakeFiles/cmTC_0cb99.dir/build
make[3]: Entering directory
'/<>/debian/build-python3.7/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_0cb99.dir/src.c.o
/usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -DIEEE_BE -fPIE -o
CMakeFiles/cmTC_0cb99.dir/src.c.o -c
/<>/debian/build-python3.7/CMakeFiles/CMakeTmp/src.c
Linking C executable cmTC_0cb99
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_0cb99.dir/link.txt
--verbose=1
/usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -DIEEE_BE
-Wl,-z,defs -Wl,--as-needed -Wl,-z,relro -rdynamic
CMakeFiles/cmTC_0cb99.dir/src.c.o -o cmTC_0cb99
make[3]: Leaving directory
'/<>/debian/build-python3.7/CMakeFiles/CMakeTmp'
make[2]: Leaving directory
'/<>/debian/build-python3.7/CMakeFiles/CMakeTmp'
...and run output:
Return value: 1
Source file was:
int compare(unsigned char* a,unsigned char* b) {
while(*a != 0) if (*(b++)!=*(a++)) return 1;
return 0;
}
int main(int argc,char** argv) {
unsigned char dc[]={0x30,0x61,0xDE,0x80,0x93,0x67,0xCC,0xD9,0};
double da=1.23456789e-75;
unsigned char* ca;
unsigned char fc[]={0x05,0x83,0x48,0x22,0};
float fa=1.23456789e-35;
if (sizeof(double)!=8) return 1;
ca=(unsigned char*)&da;
if (compare(dc,ca)) return 1;
if (sizeof(float)!=4) return 1;
ca=(uns
Bug#937625: marked as done (python-bz2file: Python2 removal in sid/bullseye)
Your message dated Sun, 05 Jan 2020 07:06:12 + with message-id and subject line Bug#937625: fixed in python-bz2file 0.98-3 has caused the Debian Bug report #937625, regarding python-bz2file: 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.) -- 937625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937625 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-bz2file Version: 0.98-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-bz2file 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-bz2file Source-Version: 0.98-3 We believe that the bug you reported is fixed in the latest version of python-bz2file, 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-bz2file package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 05 Jan 2020 01:16:02 -0500 Source: python-bz2file Architecture: source Version: 0.98-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Sandro Tosi Closes: 937625 Changes: python-bz2file (0.98-3) unstable; urgency=medium . * Team upload. * Drop python2 support; Closes: #937625 Checksums-Sha1: 23b4368bf50388fdbd7eb07e0bc87c77e2d34ead 2039 python-bz2file_0.98-3.dsc cba3b96387fd2f40f423b5974d255b6112d4c660 1856 python-bz2file_0.98-3.debian.tar.xz 0c260a8b490ee04d350556c9d7a7754140f8ca90 6159 python-bz2file_0.98-3_source.buildinfo Checksums-Sha256: 022588a5a0653181352b8ab140719b95d6c6d62dcb05be7d5afd989e99459bdc 2039 python-bz2file_0.98-3.dsc 1db0a83d128ca065286e3421f08294002a650a754accae5abe355f9c360fef1d 1856 python-bz2file_0.98-3.debian.tar.xz 9eed3834448f55fff2a5ea82b67cba8a6d90790503624f41409391a341f10795 6159 python-bz2file_0.98-3_source.buildinfo Files: 4547
Bug#936609: cblas / gsl hint needed (Was: Bug#936609: Ported ghmm to Python3 but issues with clapack)
Control: tags -1 help
Hi,
I was asking upstream about this issue[1] and an issue about gsl usage
is suspected. Any hint how this can be fixed?
> Finally I have a question about building with lapack. I get:
>
> ...
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -Wdate-time
> -D_FORTIFY_SOURCE=2 -DDTD_LOC=\"/usr/share/ghmm/ghmm.dtd.1.0\" -g -O2
> "-fdebug-prefix-map=/build/ghmm-0.9~rc3=." -fstack-protector-strong -
> Wformat -Werror=format-security -I/usr/include
> -I/usr/include/x86_64-linux-gnu -I/usr/include/libxml2 -c rng.c -fPIC -DPIC
> -o .libs/rng.o
> In file included from /usr/include/x86_64-linux-gnu/clapack.h:4,
> from matrixop.c:48:
> /usr/include/x86_64-linux-gnu/cblas.h:5:9: error: nested redefinition of
> 'enum CBLAS_ORDER'
> 5 |enum CBLAS_ORDER {CblasRowMajor=101, CblasColMajor=102 };
> | ^~~
> /usr/include/x86_64-linux-gnu/cblas.h:5:9: error: redeclaration of 'enum
> CBLAS_ORDER'
> In file included from /usr/include/gsl/gsl_blas_types.h:28,
> from /usr/include/gsl/gsl_blas.h:29,
> from /usr/include/gsl/gsl_linalg.h:30,
> from matrixop.c:44:
> /usr/include/gsl/gsl_cblas.h:46:6: note: originally defined here
>46 | enum CBLAS_ORDER {CblasRowMajor=101, CblasColMajor=102};
> | ^~~
> In file included from /usr/include/x86_64-linux-gnu/clapack.h:4,
> from matrixop.c:48:
> /usr/include/x86_64-linux-gnu/cblas.h:5:22: error: redeclaration of
> enumerator 'CblasRowMajor'
> 5 |enum CBLAS_ORDER {CblasRowMajor=101, CblasColMajor=102 };
> | ^
> In file included from /usr/include/gsl/gsl_blas_types.h:28,
> from /usr/include/gsl/gsl_blas.h:29,
> from /usr/include/gsl/gsl_linalg.h:30,
> from matrixop.c:44:
> /usr/include/gsl/gsl_cblas.h:46:19: note: previous definition of
> 'CblasRowMajor' was here
>46 | enum CBLAS_ORDER {CblasRowMajor=101, CblasColMajor=102};
> | ^
> In file included from /usr/include/x86_64-linux-gnu/clapack.h:4,
> from matrixop.c:48:
> /usr/include/x86_64-linux-gnu/cblas.h:5:41: error: redeclaration of
> enumerator 'CblasColMajor'
> 5 |enum CBLAS_ORDER {CblasRowMajor=101, CblasColMajor=102 };
> | ^
>
>
Kind regards
Andreas.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936609#19
--
http://fam-tille.de
Processed: cblas / gsl hint needed (Was: Bug#936609: Ported ghmm to Python3 but issues with clapack)
Processing control commands: > tags -1 help Bug #936609 [src:ghmm] ghmm: Python2 removal in sid/bullseye Ignoring request to alter tags of bug #936609 to the same tags previously set -- 936609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 936955 is forwarded to https://github.com/lizardfs/lizardfs/issues/665
Processing commands for cont...@bugs.debian.org: > forwarded 936955 https://github.com/lizardfs/lizardfs/issues/665 Bug #936955 [src:lizardfs] lizardfs: Python2 removal in sid/bullseye Set Bug forwarded-to-address to 'https://github.com/lizardfs/lizardfs/issues/665'. > thanks Stopping processing here. Please contact me if you need assistance. -- 936955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 936955
Processing commands for cont...@bugs.debian.org: > tags 936955 + upstream Bug #936955 [src:lizardfs] lizardfs: Python2 removal in sid/bullseye Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 936955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937625: python-bz2file: Python2 removal in sid/bullseye
patches, as i dont have access to that repo
From 905138c2115b8055b19f8e1f7374cfb0f741d441 Mon Sep 17 00:00:00 2001
From: Sandro Tosi
Date: Sun, 5 Jan 2020 01:16:04 -0500
Subject: [PATCH 2/2] releasing package python-bz2file version 0.98-3
---
debian/changelog | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 2a26a60..093d831 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,9 @@
-python-bz2file (0.98-3) UNRELEASED; urgency=medium
+python-bz2file (0.98-3) unstable; urgency=medium
* Team upload.
* Drop python2 support; Closes: #937625
- -- Sandro Tosi Sun, 05 Jan 2020 01:15:10 -0500
+ -- Sandro Tosi Sun, 05 Jan 2020 01:16:02 -0500
python-bz2file (0.98-2) unstable; urgency=medium
--
2.24.1
From 07bd423a58e539eff9322a4948589fe998c9c4de Mon Sep 17 00:00:00 2001
From: Sandro Tosi
Date: Sun, 5 Jan 2020 01:16:01 -0500
Subject: [PATCH 1/2] Drop python2 support; Closes: #937625
---
debian/changelog | 7 +++
debian/control | 16
debian/rules | 2 +-
3 files changed, 8 insertions(+), 17 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 4381d10..2a26a60 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+python-bz2file (0.98-3) UNRELEASED; urgency=medium
+
+ * Team upload.
+ * Drop python2 support; Closes: #937625
+
+ -- Sandro Tosi Sun, 05 Jan 2020 01:15:10 -0500
+
python-bz2file (0.98-2) unstable; urgency=medium
* Team upload.
diff --git a/debian/control b/debian/control
index fd3ed8b..361ef20 100644
--- a/debian/control
+++ b/debian/control
@@ -6,8 +6,6 @@ Testsuite: autopkgtest-pkg-python
Priority: optional
Build-Depends: debhelper (>= 11~),
dh-python,
- python,
- python-setuptools,
python3,
python3-setuptools
Standards-Version: 4.2.1
@@ -15,20 +13,6 @@ Vcs-Browser: https://salsa.debian.org/med-team/python-bz2file
Vcs-Git: https://salsa.debian.org/med-team/python-bz2file.git
Homepage: https://github.com/nvawda/bz2file
-Package: python-bz2file
-Architecture: all
-Depends: ${python:Depends},
- ${misc:Depends}
-Provides: ${python:Provides}
-Description: Python library for reading and writing bzip2-compressed files
- Bz2file is a Python library for reading and writing bzip2-compressed files.
- .
- It contains a drop-in replacement for the file interface in the standard
- library's bz2 module, including features from the latest development version
- of CPython that are not available in older releases.
- .
- Bz2file for Python2.
-
Package: python3-bz2file
Architecture: all
Depends: ${python3:Depends},
diff --git a/debian/rules b/debian/rules
index b945423..32cd64c 100755
--- a/debian/rules
+++ b/debian/rules
@@ -4,4 +4,4 @@ DH_VERBOSE := 1
export PYBUILD_NAME=bz2file
%:
- dh $@ --with python2,python3 --buildsystem=pybuild
+ dh $@ --with python3 --buildsystem=pybuild
--
2.24.1
Bug#948195: nvidia-legacy-340xx-driver: Xorg fails to start with a kernel panic after the upgrade to 340.108-1
Package: nvidia-legacy-340xx-driver Version: 340.108-1 Severity: grave Justification: renders package unusable Dear Maintainer, After todays upgrade to 340.108, the system fails to boot in the desktop enviroment and dmesg reports a kernel panic, as seen on the paste here https://paste.debian.net/1124712 The lockup is so bad that even ssh-ing to the machine and issuing a reboot does not work, so I had to reisub out of it every time. Disabling the display manager (lightdm) and booting to command line works, but the same happens as soon as I use startx. Downgrading to kernel 5.3 does not solve the problem and I had to complete remove nvidia and use nouveau to get back to the desktop and write this bug report. Now I am trying to install 340.107 from the snapshot repo, but it will take a lot of time as it seems because of the many dependencies. Thank you in advance. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nvidia-legacy-340xx-driver depends on: pn nvidia-installer-cleanup pn nvidia-legacy-340xx-alternative pn nvidia-legacy-340xx-driver-bin pn nvidia-legacy-340xx-driver-libs pn nvidia-legacy-340xx-kernel-dkms | nvidia-legacy-340xx-kernel-340.10 pn nvidia-legacy-340xx-kernel-dkms | nvidia-legacy-340xx-kernel-340.10 pn nvidia-legacy-340xx-vdpau-driver pn nvidia-support pn xserver-xorg-video-nvidia-legacy-340xx Versions of packages nvidia-legacy-340xx-driver recommends: pn nvidia-persistenced pn nvidia-settings-legacy-340xx Versions of packages nvidia-legacy-340xx-driver suggests: pn nvidia-legacy-340xx-kernel-dkms | nvidia-legacy-340xx-kernel-source
Bug#948119: marked as done ([schroot] does not work for non-root user)
Your message dated Sun, 05 Jan 2020 06:08:53 + with message-id and subject line Bug#948119: fixed in schroot 1.6.10-8 has caused the Debian Bug report #948119, regarding [schroot] does not work for non-root user 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.) -- 948119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: schroot Version: 1.6.10-7 Severity: important Hi, with today's update (1.6.10-7), schroot does not work anymore for non-root users (which are still authorized by mean of the "users" directive): > $ schroot -c sid > E: sid-e3acbcde-86df-4f46-a30a-8bbb72d1620e: Failed to lock chroot: > /var/lib/schroot/session/sid-e3acbcde-86df-4f46-a30a-8bbb72d1620e: Failed to > write session file: Permesso negato I suspect the problem might be related to the fact that /usr/bin/schroot is not set-uid anymore, while it was before. Executing # chmod u+s /usr/bin/schroot fixes the problem for me. Thanks, Giovanni. --- System information. --- Architecture: Kernel: Linux 5.4.0-1-amd64 Debian Release: bullseye/sid 500 xenial updates.signal.org 500 unstable-debug debug.mirrors.debian.org 500 unstabledeb.debian.org 500 testing deb.debian.org 500 stable repo.skype.com 500 stable dl.google.com 1 experimentaldeb.debian.org --- Package information. --- Depends(Version) | Installed -+-== lsb-base | 11.1.0 libboost-filesystem1.67.0| 1.67.0-16 libboost-iostreams1.67.0 | 1.67.0-16 libboost-program-options1.67.0 | 1.67.0-16 libboost-system1.67.0| 1.67.0-16 libc6 (>= 2.28) | libgcc1 (>= 1:3.0) | libpam0g (>= 0.99.7.1) | libstdc++6(>= 9) | libuuid1 (>= 2.16) | schroot-common (= 1.6.10-7) | Package's Recommends field is empty. Suggests (Version) | Installed ===-+-=== debootstrap | 1.0.116 lvm2| 2.03.02-3 btrfs-progs | 5.4-1 zfsutils-linux | aufs-tools | 1:4.14+20190211-1 OR unionfs-fuse| qemu-user-static| 1:4.2-1 -- Giovanni Mascellani Postdoc researcher - Université Libre de Bruxelles signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: schroot Source-Version: 1.6.10-8 We believe that the bug you reported is fixed in the latest version of schroot, 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. Steve Langasek (supplier of updated schroot package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 05 Jan 2020 05:36:58 + Source: schroot Binary: schroot schroot-common schroot-dbgsym Architecture: source all amd64 Version: 1.6.10-8 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Steve Langasek Description: schroot- Execute commands in a chroot environment schroot-common - common files for schroot Closes: 948119 Changes: schroot (1.6.10-8) unstable; urgency=medium . * QA upload. * Fix install target to call install-arch instead of bypassing the various overrides (such as setting the binary suid root, and calling the test suite). Closes: #948119. * debian/patches/zfs-snapshot-support.patch: fix the tests to match the implementation, overlooked due to the previous bug preventing the testsuite from being run during local test builds. Checksums-Sha1: fb867e3f1c225e8ce7740ed3bd61fcfe11e7597f 2200 schroot_1.6.10-8.dsc 780e0bee634c42c9bf84cb7c3c608d0f59e9c85e 82612 schroot_1.6.10-8.debian.tar.xz 2eea23b14e6c11376f8b70a691acce970343a8fa 244640 schroot-com
Processed: found 948180 in 4.1.2+dfsg-5, closing 948180
Processing commands for cont...@bugs.debian.org: > found 948180 4.1.2+dfsg-5 Bug #948180 [opencv] opencv: CVE-2019-5063 and CVE-2019-5064 There is no source info for the package 'opencv' at version '4.1.2+dfsg-5' with architecture '' Unable to make a source version for version '4.1.2+dfsg-5' Marked as found in versions 4.1.2+dfsg-5. > close 948180 4.2.0+dfsg-1 Bug #948180 [opencv] opencv: CVE-2019-5063 and CVE-2019-5064 There is no source info for the package 'opencv' at version '4.2.0+dfsg-1' with architecture '' Unable to make a source version for version '4.2.0+dfsg-1' Ignoring request to alter fixed versions of bug #948180 to the same values previously set Bug #948180 [opencv] opencv: CVE-2019-5063 and CVE-2019-5064 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 948180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948180 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921183: marked as done (python3-surfer: missing Breaks+Replaces: python-surfer (<< 0.9.0))
Your message dated Sun, 05 Jan 2020 05:45:44 + with message-id and subject line Bug#921183: fixed in pysurfer 0.9.0-3 has caused the Debian Bug report #921183, regarding python3-surfer: missing Breaks+Replaces: python-surfer (<< 0.9.0) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 921183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-surfer Version: 0.9.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces From the attached log (scroll to the bottom...): Preparing to unpack .../python3-surfer_0.9.0-1_all.deb ... Unpacking python3-surfer (0.9.0-1) ... dpkg: error processing archive /var/cache/apt/archives/python3-surfer_0.9.0-1_all.deb (--unpack): trying to overwrite '/usr/bin/pysurfer', which is also in package python-surfer 0.7-2.1 Errors were encountered while processing: /var/cache/apt/archives/python3-surfer_0.9.0-1_all.deb cheers, Andreas python-surfer=0.7-2.1_python3-surfer=0.9.0-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: pysurfer Source-Version: 0.9.0-3 We believe that the bug you reported is fixed in the latest version of pysurfer, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated pysurfer package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 04 Jan 2020 23:36:28 -0500 Source: pysurfer Architecture: source Version: 0.9.0-3 Distribution: unstable Urgency: medium Maintainer: NeuroDebian Team Changed-By: Sandro Tosi Closes: 921183 937551 Changes: pysurfer (0.9.0-3) unstable; urgency=medium . * Team upload. * Drop python2 support; Closes: #937551 * debian/control - update Breaks/Replaces to 0.7-2.1; Closes: #921183 Checksums-Sha1: c9ccb197310fd80d19583136223c8c5a07c9 2124 pysurfer_0.9.0-3.dsc 5af6f17b09cc8492b60331131a496bf085a98287 4168 pysurfer_0.9.0-3.debian.tar.xz 422483db1b627422d39891bc553581504cf4c546 16849 pysurfer_0.9.0-3_source.buildinfo Checksums-Sha256: f7a4124afdf9e3d96e4342b112645a574f826c23c074fc1fc2d9d597a0800df5 2124 pysurfer_0.9.0-3.dsc c252ed212435de839ef1b221daf32d28ab0a9de2705a028554656d2d4b9c876d 4168 pysurfer_0.9.0-3.debian.tar.xz b91bcc36886326aeafdd77c37430862795fee64c6e9dbf3ff23adf723202f90d 16849 pysurfer_0.9.0-3_source.buildinfo Files: fdfd319e1482e4cf516ffe2b320afd1c 2124 python optional pysurfer_0.9.0-3.dsc b5bb0a6341f87192bcd99a2a7fee5718 4168 python optional pysurfer_0.9.0-3.debian.tar.xz 9d13b8c64b52ad7c73a1672f6980fa62 16849 python optional pysurfer_0.9.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl4RcSMACgkQh588mTgB qU+Fcg/9Hw1E8cmjeFQbxSRd2p5Eq2dMy8DwPlWC6
Bug#948180: found 948180 in 4.1.2+dfsg-5, closing 948180
found 948180 4.1.2+dfsg-5 close 948180 4.2.0+dfsg-1 thanks
Bug#937551: marked as done (pysurfer: Python2 removal in sid/bullseye)
Your message dated Sun, 05 Jan 2020 05:45:44 + with message-id and subject line Bug#937551: fixed in pysurfer 0.9.0-3 has caused the Debian Bug report #937551, regarding pysurfer: 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.) -- 937551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937551 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pysurfer Version: 0.9.0-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:pysurfer 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: pysurfer Source-Version: 0.9.0-3 We believe that the bug you reported is fixed in the latest version of pysurfer, 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 pysurfer package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 04 Jan 2020 23:36:28 -0500 Source: pysurfer Architecture: source Version: 0.9.0-3 Distribution: unstable Urgency: medium Maintainer: NeuroDebian Team Changed-By: Sandro Tosi Closes: 921183 937551 Changes: pysurfer (0.9.0-3) unstable; urgency=medium . * Team upload. * Drop python2 support; Closes: #937551 * debian/control - update Breaks/Replaces to 0.7-2.1; Closes: #921183 Checksums-Sha1: c9ccb197310fd80d19583136223c8c5a07c9 2124 pysurfer_0.9.0-3.dsc 5af6f17b09cc8492b60331131a496bf085a98287 4168 pysurfer_0.9.0-3.debian.tar.xz 422483db1b627422d39891bc553581504cf4c546 16849 pysurfer_0.9.0-3_source.buildinfo Checksums-Sha256: f7a4124afdf9e3d96e4342b112645a574f826c23c074fc1fc2d9d597a0800df5 2124 pysurfer_0.9.0-3.dsc c252ed212435de839ef1b221daf32d28ab0a9de2705a028554656d2d4b9c876d 4168 pysurfer_0.9.0-3.debian.tar.xz b91bcc36886326aeafdd77c37430862795fee64c6e9dbf3ff23adf723202f90d 16849 pysurfer_0.9.0-3_source.buildinfo Files: fdfd319
Bug#948119: [schroot] does not work for non-root user
On Sat, Jan 04, 2020 at 12:06:41PM -0800, tony mancill wrote: > On Sat, Jan 04, 2020 at 09:35:27AM +0100, Giovanni Mascellani wrote: > > I suspect the problem might be related to the fact that /usr/bin/schroot > > is not set-uid anymore, while it was before. Executing > > ... > I ran into this as well and verified on another system running sid that > the binary update to 1.6.10-7 is when the setuid bit is removed - it's > simply not set in the binary package, while it is in . > I'm curious as to how this happened. I not seeing anything obvious in > the source package changes [1], and when I rebuild 1.6.10-6 or 1.6.10-7 > from source locally in a sid chroot, neither one of them results in a > setuid binary. In the build logs for those builds, the install-arch > target is no longer being called. > However, building 1.6.10-7 in a buster chroot does result in a setuid > binary, so it seems that a recent change in the packaging toolchain > could be the root cause (although I haven't found anything definitive > yet). It is a latent bug in debian/rules, which failed to run the install-arch: target when run under dpkg-buildpackage -b (instead of -B), which is how I did my test build for upload to the archive. I was surprised to find that the archive did not discard my binaries and rebuild them, which I understood was now the standard upload workflow in Debian, but instead published them as-is, which is how this bug made it out to the world. I have pushed a fix for this bug to the git repository; however, the other thing that was failing to happen due to this bug, aside from not setting the binary setuid root, was that the testsuite was not being run. So I'm in the process now of fixing various testsuite regressions. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#937551: marked as pending in pysurfer
Control: tag -1 pending Hello, Bug #937551 in pysurfer 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/neurodebian-team/pysurfer/commit/11e11aac7d7f5e0897338f26fc77d61daad00ae5 Drop python2 support; Closes: #937551 (this message was generated automatically) -- Greetings https://bugs.debian.org/937551
Bug#921183: marked as pending in pysurfer
Control: tag -1 pending Hello, Bug #921183 in pysurfer 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/neurodebian-team/pysurfer/commit/27d51980d9bd293a5a81dba6e0ac1e59cc8a32bf update Breaks/Replaces to 0.7-2.1; Closes: #921183 (this message was generated automatically) -- Greetings https://bugs.debian.org/921183
Processed: Bug#921183 marked as pending in pysurfer
Processing control commands: > tag -1 pending Bug #921183 [python3-surfer] python3-surfer: missing Breaks+Replaces: python-surfer (<< 0.9.0) Added tag(s) pending. -- 921183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#937551 marked as pending in pysurfer
Processing control commands: > tag -1 pending Bug #937551 [src:pysurfer] pysurfer: Python2 removal in sid/bullseye Added tag(s) pending. -- 937551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937551 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937168: marked as done (numpydoc: Python2 removal in sid/bullseye)
Your message dated Sun, 05 Jan 2020 04:10:10 + with message-id and subject line Bug#937168: fixed in numpydoc 0.7.0-2 has caused the Debian Bug report #937168, regarding numpydoc: 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.) -- 937168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:numpydoc Version: 0.7.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:numpydoc 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: numpydoc Source-Version: 0.7.0-2 We believe that the bug you reported is fixed in the latest version of numpydoc, 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 numpydoc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 04 Jan 2020 22:43:34 -0500 Source: numpydoc Architecture: source Version: 0.7.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Sandro Tosi Closes: 937168 Changes: numpydoc (0.7.0-2) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org * d/control: Remove ancient X-Python-Version field * d/control: Remove ancient X-Python3-Version field * Use debhelper-compat instead of debian/compat. . [ Sandro Tosi ] * Drop python2 support; Closes: #937168 Checksums-Sha1: 380d20ed48b2143bb864def42933f392275e26b5 2220 numpydoc_0.7.0-2.dsc e43cddaf9a37f7c561b7d4e45aa40426fbe3e1ed 3460 numpydoc_0.7.0-2.debian.tar.xz 05fb66286daddd4866658c6942fae4e94a7cab16 7655 numpydoc_0.7.0-2_source.buildinfo Checksums-Sha256: 74ae06c119895eec10509d9151c10cb4258d7933588b8cab3cc4f2f7f34ea07c 2220 numpydoc_0.7.0-2.dsc c2fd1e505c33d41f364c281f429dc4110b2a26d2ddcc0520fa2fdeb30f5461c7 3460
Bug#937168: marked as pending in numpydoc
Control: tag -1 pending Hello, Bug #937168 in numpydoc 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/numpydoc/commit/b13b014d9690f3d1808ff9f96a7b995e85ea19d4 Drop python2 support; Closes: #937168 (this message was generated automatically) -- Greetings https://bugs.debian.org/937168
Processed: Bug#937168 marked as pending in numpydoc
Processing control commands: > tag -1 pending Bug #937168 [src:numpydoc] numpydoc: Python2 removal in sid/bullseye Added tag(s) pending. -- 937168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: py2removal RC severity updates - 2020-01-05 03:36:25.066179+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 > # for more details on this severity bump > # python-numpydoc is a module and has 0 external rdeps or not in testing > severity 937168 serious Bug #937168 [src:numpydoc] numpydoc: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-bz2file is a module and has 0 external rdeps or not in testing > severity 937625 serious Bug #937625 [src:python-bz2file] python-bz2file: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 937168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937168 937625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937625 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938232: marked as done (python-txaio: Python2 removal in sid/bullseye)
Your message dated Sun, 05 Jan 2020 03:19:46 + with message-id and subject line Bug#938232: fixed in python-txaio 2.10.0-2 has caused the Debian Bug report #938232, regarding python-txaio: 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.) -- 938232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-txaio Version: 2.10.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-txaio 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-txaio Source-Version: 2.10.0-2 We believe that the bug you reported is fixed in the latest version of python-txaio, 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-txaio package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 04 Jan 2020 22:06:13 -0500 Source: python-txaio Architecture: source Version: 2.10.0-2 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Sandro Tosi Closes: 938232 Changes: python-txaio (2.10.0-2) unstable; urgency=medium . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat. . [ Sandro Tosi ] * Drop python2 support; Closes: #938232 Checksums-Sha1: f21058f04311c31d67e4be6944a9e067bb688cee 2275 python-txaio_2.10.0-2.dsc e2ad347a084e8653583cb30733f4f4a70d895d4a 4652 python-txaio_2.10.0-2.debian.tar.xz 0c35c1a5722850bda11cb78f081a435897b78d7a 7316 python-txaio_2.10.0-2_source.buildinfo Checksums-Sha256: 22a0755f9042a5abcdf2940dca38465df8784108f73d04efb8213626865ae225 2275 python-txaio_2.10.0-2.dsc aa3c2458337dadb112314d320e10c26eb61c4620fec44825cf34b5d96f3969c3 4652 python-txaio_2.10.0-2.debian.tar.xz ca2d5ed782ce45ea09bb99834d5786236f65da92e37beae484f8ff58e04ca09e
Bug#938232: marked as pending in python-txaio
Control: tag -1 pending Hello, Bug #938232 in python-txaio 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/openstack-team/python/python-txaio/commit/edc31b82d8a1b6c25e1ac889d0b2eae5000e4a23 Drop python2 support; Closes: #938232 (this message was generated automatically) -- Greetings https://bugs.debian.org/938232
Processed: Bug#938232 marked as pending in python-txaio
Processing control commands: > tag -1 pending Bug #938232 [src:python-txaio] python-txaio: Python2 removal in sid/bullseye Added tag(s) pending. -- 938232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 948074, tagging 948129, found 933631 in 2.6.1-1, tagging 948130, tagging 948128 ...
Processing commands for cont...@bugs.debian.org: > tags 948074 + sid bullseye Bug #948074 [src:din] din FTBFS: cannot find X11/X.h Added tag(s) bullseye and sid. > tags 948129 + sid bullseye Bug #948129 [src:gnome-pie] gnome-pie FTBFS: vala error: Creation method of abstract class cannot be public Added tag(s) bullseye and sid. > found 933631 2.6.1-1 Bug #933631 [src:kazoo] kazoo: test failures Marked as found in versions kazoo/2.6.1-1. > tags 948130 + sid bullseye Bug #948130 [src:timeshift] timeshift FTBFS: vala error: Creation method of abstract class cannot be public. Added tag(s) bullseye and sid. > tags 948128 + sid bullseye Bug #948128 [src:gnome-shell-mailnag] gnome-shell-mailnag FTBFS: vala error: syntax error, invalid array parameter declaration Added tag(s) sid and bullseye. > found 944820 1.16.3-1 Bug #944820 [simplesamlphp] SimpleSAMLphp fails when consuming assertion Marked as found in versions simplesamlphp/1.16.3-1. > fixed 944820 1.17.0-1 Bug #944820 [simplesamlphp] SimpleSAMLphp fails when consuming assertion Marked as fixed in versions simplesamlphp/1.17.0-1. > tags 944820 - buster Bug #944820 [simplesamlphp] SimpleSAMLphp fails when consuming assertion Removed tag(s) buster. > found 947327 0.81.0-1 Bug #947327 [src:poppler] FTBFS: /usr/bin/env: ‘python’: No such file or directory Marked as found in versions poppler/0.81.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 933631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933631 944820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944820 947327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947327 948074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948074 948128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948128 948129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948129 948130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948130 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#809997: emscripten not installable on Debian/testing...
Control: forwarded -1 https://github.com/emscripten-core/emscripten/issues/5488 Control > The problem is that emscripten uses a fork of LLVM and I am reluctant to add > yet-a-new-version of llvm in the archive... > I have been waiting for the changes to be merged upstream and, with the > recent progress on webassembly, we are getting there... I haven't tried it, but it appears they enabled using Web Assembly with upstream LLVM in October. signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#809997: emscripten not installable on Debian/testing...
Processing control commands: > forwarded -1 https://github.com/emscripten-core/emscripten/issues/5488 Bug #809997 [emscripten] emscripten: not installable in sid Set Bug forwarded-to-address to 'https://github.com/emscripten-core/emscripten/issues/5488'. -- 809997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809997 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#936481: Emscripten supports Python 3
Control: forwarded -1 https://github.com/emscripten-core/emscripten/issues/5950 Control: tags -1 fixed-upstream It appears it still supports Python 2 also for the time being https://github.com/emscripten-core/emscripten/issues/7198 signature.asc Description: This is a digitally signed message part.
Processed: Emscripten supports Python 3
Processing control commands: > forwarded -1 https://github.com/emscripten-core/emscripten/issues/5950 Bug #936481 [src:emscripten] emscripten: Python2 removal in sid/bullseye Set Bug forwarded-to-address to 'https://github.com/emscripten-core/emscripten/issues/5950'. > tags -1 fixed-upstream Bug #936481 [src:emscripten] emscripten: Python2 removal in sid/bullseye Added tag(s) fixed-upstream. -- 936481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936481 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Emscripten violates font license
Processing control commands: > forwarded -1 https://github.com/emscripten-core/emscripten/issues/10146 Bug #851109 [src:emscripten] emscripten: violates font license Set Bug forwarded-to-address to 'https://github.com/emscripten-core/emscripten/issues/10146'. > block 939477 by -1 Bug #939477 [src:emscripten] incomplete copyright file, and copyright file includes null characters 939477 was not blocked by any bugs. 939477 was not blocking any bugs. Added blocking bug(s) of 939477: 851109 -- 851109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851109 939477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#851109: Emscripten violates font license
Control: forwarded -1 https://github.com/emscripten-core/emscripten/issues/10146 Control: block 939477 by -1 I've reported this upstream since they're still using it. signature.asc Description: This is a digitally signed message part.
Processed: severity of 947927 is important
Processing commands for cont...@bugs.debian.org: > severity 947927 important Bug #947927 [mimedefang,spamassassin] mimedefang: Mimedefang is unable to start after upgrade of spamassassin Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 947927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948186: openvdb: FTBFS against python3.8
Source: openvdb Version: 6.2.1-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, openvdb/experimental FTBFS against python3.8: -- -- Configuring OpenVDBPython - -- CMake Error at /usr/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:137 (message): Could NOT find Python (missing: Development) (found suitable version "3.8.1", minimum required is "3.7") Call Stack (most recent call first): /usr/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE) /usr/share/cmake-3.15/Modules/FindPython/Support.cmake:1653 (find_package_handle_standard_args) /usr/share/cmake-3.15/Modules/FindPython.cmake:215 (include) openvdb/python/CMakeLists.txt:106 (find_package) -- Configuring incomplete, errors occurred! Andreas openvdb_6.2.1-3.log.gz Description: application/gzip
Bug#948165: marked as pending in ceph
On 04/01/2020 23.35, Bernd Zeimetz wrote: > https://salsa.debian.org/ceph-team/ceph/commit/c98ea073fc6ec1bfa2a15112616c8c04fb7b1a4b > > > Install bash-completion in /usr again. > > This change went missing somewhere during the import of the > changes done in Ubuntu between 12.2.11 and 14.2.4. > > Closes: #948165 > Thanks: Andreas Beckmann > Don't you need .maintscript files to rm_conffile the now (again) obsolete conffiles? Or if you already have them, bump the version? That crafted piuparts test should actually investigate missing B+R for the potential move of some files from ceph-mds 14.2.4-8 to ceph-common 14.2.5-1: usr/bin/cephfs-data-scan usr/bin/cephfs-journal-tool usr/bin/cephfs-table-tool but got stopped early when it stomped over the bash completions. Andreas
Bug#948165: marked as done (ceph-common: missing Breaks+Replaces: ceph-base (<< 14.2.5))
Your message dated Sat, 04 Jan 2020 23:53:26 + with message-id and subject line Bug#948165: fixed in ceph 14.2.5-2 has caused the Debian Bug report #948165, regarding ceph-common: missing Breaks+Replaces: ceph-base (<< 14.2.5) 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.) -- 948165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ceph-common Version: 14.2.5-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../10-ceph-common_14.2.5-1_amd64.deb ... Unpacking ceph-common (14.2.5-1) over (14.2.4-8) ... dpkg: error processing archive /tmp/apt-dpkg-install-zSzHB9/10-ceph-common_14.2.5-1_amd64.deb (--unpack): trying to overwrite '/etc/bash_completion.d/ceph', which is also in package ceph-base 14.2.4-8 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /tmp/apt-dpkg-install-zSzHB9/10-ceph-common_14.2.5-1_amd64.deb Why are you still shipping bash completions in /etc? These belong to /usr ... cheers, Andreas ceph-mds=14.2.4-8_ceph-common=14.2.5-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: ceph Source-Version: 14.2.5-2 We believe that the bug you reported is fixed in the latest version of ceph, 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. Bernd Zeimetz (supplier of updated ceph package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 05 Jan 2020 00:04:23 +0100 Source: ceph Architecture: source Version: 14.2.5-2 Distribution: experimental Urgency: medium Maintainer: Ceph Packaging Team Changed-By: Bernd Zeimetz Closes: 948021 948165 Changes: ceph (14.2.5-2) experimental; urgency=medium . * [8c74414] lower --max-parallel for >=16GB g++ loves to eat ram * [b15dcdd] Build-dep. on python3-dev instead python3-all-dev. Thanks to Graham Inggs (Closes: #948021) * [d481122] CI: build in experimental * [4303a75] 32bit: fix more size_t vs uint64_t issues. * [c98ea07] Install bash-completion in /usr again. This change went missing somewhere during the import of the changes done in Ubuntu between 12.2.11 and 14.2.4. Thanks to Andreas Beckmann (Closes: #948165) * [c7d90b9] Move manpages to ceph-common again. This also went missing during the import. * [3e5a680] Use a better way to check if we are on 32bit. * [c03cd06] rm d/p/boost-py37-compat.patch. Upstream renamed assert.h to ceph_assert.h, so this patch should not be necessary anymore. Checksums-Sha1: 7f8227c1d9727f1b051305807a0072c45f33942e 8762 ceph_14.2.5-2.dsc 9111f81a5940a5b1b72054133eac07c936e2bcb9 107176 ceph_14.2.5-2.debian.tar.xz 8b324ead287d15781389f959cedfab6ea315ee66 20740 ceph_14.2.5-2_source.buildinfo Checksums-Sha256: 39e2c518637c073a99f2fb03913322af5d3a94d16c02137c074cada8517115ea 8762 ceph_14.2.5-2.dsc d32a5be3dd59ce28a531083fa4259eafe4700abdf2a7ed440f45dda41c169f55 107176 ceph_14.2.5-2.debian.tar.xz ac63f2b6db0211de96ae94c46b9141f92e39e530c5a9f0d79b08dd3687684554 20740 ceph_14.2.5-2_source.buildinfo Files: cbd02912e3614db8c164309d85addbb7 8762 admin optional ceph_14.2.5-2.dsc 23bdccbea020c018e80870356083d800 107176 admin optional ceph_14.2.5-2.debian.tar.xz 71c6b8599ae237f3c583f0b5876389f3 20740 admin optional ceph_14.2.5-2_source.buildinfo Original-Maintainer: Ceph Packaging Team -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE7KHj8o4RJDLUhd2V6zYXGm/5Q18FAl4RIS0ACgkQ6zYXGm/5 Q181Yg/+IfvPfCGljyAMC5RFxitNOo9Qny8G0WoDh/7VTtM6ld7CS
Bug#948165: marked as done (ceph-common: missing Breaks+Replaces: ceph-base (<< 14.2.5))
Your message dated Sat, 04 Jan 2020 23:51:04 + with message-id and subject line Bug#948165: fixed in ceph 14.2.4-9 has caused the Debian Bug report #948165, regarding ceph-common: missing Breaks+Replaces: ceph-base (<< 14.2.5) 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.) -- 948165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ceph-common Version: 14.2.5-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../10-ceph-common_14.2.5-1_amd64.deb ... Unpacking ceph-common (14.2.5-1) over (14.2.4-8) ... dpkg: error processing archive /tmp/apt-dpkg-install-zSzHB9/10-ceph-common_14.2.5-1_amd64.deb (--unpack): trying to overwrite '/etc/bash_completion.d/ceph', which is also in package ceph-base 14.2.4-8 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /tmp/apt-dpkg-install-zSzHB9/10-ceph-common_14.2.5-1_amd64.deb Why are you still shipping bash completions in /etc? These belong to /usr ... cheers, Andreas ceph-mds=14.2.4-8_ceph-common=14.2.5-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: ceph Source-Version: 14.2.4-9 We believe that the bug you reported is fixed in the latest version of ceph, 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. Bernd Zeimetz (supplier of updated ceph package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 05 Jan 2020 00:22:21 +0100 Source: ceph Architecture: source Version: 14.2.4-9 Distribution: unstable Urgency: medium Maintainer: Ceph Packaging Team Changed-By: Bernd Zeimetz Closes: 948021 948165 Changes: ceph (14.2.4-9) unstable; urgency=medium . * [8c74414] lower --max-parallel for >=16GB g++ loves to eat ram * [b15dcdd] Build-dep. on python3-dev instead python3-all-dev. Thanks to Graham Inggs (Closes: #948021) * [c98ea07] Install bash-completion in /usr again. This change went missing somewhere during the import of the changes done in Ubuntu between 12.2.11 and 14.2.4. Thanks to Andreas Beckmann (Closes: #948165) * [c7d90b9] Move manpages to ceph-common again. This also went missing during the import. Checksums-Sha1: 223b4bd5fef0eb4c521aabb0badfd83061ee9281 8917 ceph_14.2.4-9.dsc f56f45bad6b5b3b0fa09b9ff312020893a5d5235 117620 ceph_14.2.4-9.debian.tar.xz b8889aae296a855b17d035ae16da21e50ab9859c 20912 ceph_14.2.4-9_source.buildinfo Checksums-Sha256: 4dda45a527d6d281f99a72df6069b93d7f8d9e5c0eef26737fa5715fe2d80677 8917 ceph_14.2.4-9.dsc 8062a4ad10b3693013237d7268a3f4ed98bcdc20b02d84414451cba2141e0e55 117620 ceph_14.2.4-9.debian.tar.xz 0b908ff253641f829eed4387ce284e6ca5357b475492a6e23f18bd8592b0d614 20912 ceph_14.2.4-9_source.buildinfo Files: f07d738ffaa4468c762b6247eb374c9e 8917 admin optional ceph_14.2.4-9.dsc 39a5c3eea04c8a939c925efa6b191e34 117620 admin optional ceph_14.2.4-9.debian.tar.xz 1d2a0fd71d0a15ca05dfce8a2d3881a0 20912 admin optional ceph_14.2.4-9_source.buildinfo Original-Maintainer: Ceph Packaging Team -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE7KHj8o4RJDLUhd2V6zYXGm/5Q18FAl4RH5YACgkQ6zYXGm/5 Q1+tsBAAu7SbQ8Htr7ylVI1wFltbrNHrIYoLbv1B1BoQBFTKKz+gsA1ImwGYfTP+ +MnMpNYG23lZKRuszfQoyg+ThOOo7frXcNL36gyobRkPDuby5wBdUJQBw/Fzrdr6 meqkwupuP2DI08XLvnu4kz671Tjk03MKP4EuCZuhq3rz/IAug1p7QdPmIYrOVlDh oeruLQfC0uelLJp0b/cYUwsBy9Uqt6AU/hCR7PP1COaTtAQMCUB2S8xIceygDYYa J9mWcoiZVbKAMNgjGcBLzLCt5sLlYu70vhB8iOCsWUa7W2eaS/rnTlGHgmWm54u0 a5g+k57yPkqOSulr2DnguawsKN0pZ5wSL02gUx7C2QX8
Bug#947969: marked as pending in ceph
Control: tag -1 pending Hello, Bug #947969 in ceph 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/ceph-team/ceph/commit/010db9a30458a6417ff667c3c11a3870edb8ee0c Fix ceph-mgr - indefinite queue growth hangs Applying the backport for the fix https://github.com/ceph/ceph/pull/32466 Closes: #947969 Thanks: Milan Kupcevic (this message was generated automatically) -- Greetings https://bugs.debian.org/947969
Processed: Bug#947969 marked as pending in ceph
Processing control commands: > tag -1 pending Bug #947969 [ceph-mgr] ceph-mgr: indefinite queue growth causing commands to hang Added tag(s) pending. -- 947969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948181: x2gothinclient-minidesktop: fails to install with lightdm installed
Package: x2gothinclient-minidesktop Version: 1.5.0.1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up x2gothinclient-minidesktop (1.5.0.1-2) ... Configuration file '/etc/lightdm/lightdm.conf' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** lightdm.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package x2gothinclient-minidesktop (--configure): end of file on stdin at conffile prompt Processing triggers for dictionaries-common (1.28.1) ... Processing triggers for libc-bin (2.29-7) ... Processing triggers for dbus (1.12.16-2) ... Errors were encountered while processing: x2gothinclient-minidesktop Are you trying to use dpkg-divert on conffiles? That does not work ... cheers, Andreas PS: If you tell me what exactly you want to achieve, I might think about it ... ;-) lightdm=1.26.0-6+b1_x2gothinclient-minidesktop=1.5.0.1-2.log.gz Description: application/gzip
Processed: Re: opencv: CVE-2019-5063 and CVE-2019-5064
Processing commands for cont...@bugs.debian.org: > fixed 948180 4.2.0+dfsg-1 Bug #948180 [opencv] opencv: CVE-2019-5063 and CVE-2019-5064 There is no source info for the package 'opencv' at version '4.2.0+dfsg-1' with architecture '' Unable to make a source version for version '4.2.0+dfsg-1' Marked as fixed in versions 4.2.0+dfsg-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 948180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948180 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: [debian-mysql] Bug#943974: Bug#943974: mariadb-server-10.3: as "service mysql stop" fails, system refuse to shut down
Processing control commands: > severity -1 normal Bug #943974 [mariadb-server-10.3] mariadb-server-10.3: as "service mysql stop" fails, system refuse to shut down Severity set to 'normal' from 'critical' > tags -1 moreinfo Bug #943974 [mariadb-server-10.3] mariadb-server-10.3: as "service mysql stop" fails, system refuse to shut down Added tag(s) moreinfo. -- 943974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943974 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#943974: [debian-mysql] Bug#943974: Bug#943974: mariadb-server-10.3: as "service mysql stop" fails, system refuse to shut down
Control: severity -1 normal Control: tags -1 moreinfo More info is needed if you want anybody to help out with this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943974
Bug#948179: gcc-8-doc: Build-Depends on no longer available texlive-generic-recommended
Source: gcc-8-doc Version: 8.3.0-2 Severity: serious Tags: ftbfs Justification: fails to build from source gcc-8-doc cannot be built in bullseye any longer since the obsolete package texlive-generic-recommended is no longer available in bullseye. Andreas
Bug#948180: opencv: CVE-2019-5063 and CVE-2019-5064
Package: opencv X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for opencv. CVE-2019-5064[0]: | An exploitable heap buffer overflow vulnerability exists in the data | structure persistence functionality of OpenCV, version 4.1.0. A | specially crafted JSON file can cause a buffer overflow, resulting in | multiple heap corruptions and potentially code execution. An attacker | can provide a specially crafted file to trigger this vulnerability. CVE-2019-5063[1]: | An exploitable heap buffer overflow vulnerability exists in the data | structure persistence functionality of OpenCV 4.1.0. A specially | crafted XML file can cause a buffer overflow, resulting in multiple | heap corruptions and potential code execution. An attacker can provide | a specially crafted file to trigger this vulnerability. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-5064 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5064 [1] https://security-tracker.debian.org/tracker/CVE-2019-5063 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5063 Please adjust the affected versions in the BTS as needed. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#945697: marked as pending in mariadb-10.3
Control: tag -1 pending Hello, Bug #945697 in mariadb-10.3 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/mariadb-team/mariadb-10.3/commit/ab2750ab6d6306a5c91a463cc2a790b42a7e1a81 Update Python dependencies and recommends to Python 3 (Closes: #945697) The RocksDB shell and some Mroonga tools and TokuDB tests still reference Python 2, but fixing those is outside the scope of packaging and they have anyway little effect on running MariaDB or it's engines and plugins as all Python code is just for tooling/testing. (this message was generated automatically) -- Greetings https://bugs.debian.org/945697
Processed: Bug#945697 marked as pending in mariadb-10.3
Processing control commands: > tag -1 pending Bug #945697 [src:mariadb-10.3] mariadb-10.3: Python2 removal in sid/bullseye Added tag(s) pending. -- 945697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945697 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937140: marked as done (nibabel: Python2 removal in sid/bullseye)
Your message dated Sat, 04 Jan 2020 23:20:03 + with message-id and subject line Bug#937140: fixed in nibabel 2.5.1-2 has caused the Debian Bug report #937140, regarding nibabel: 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.) -- 937140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:nibabel Version: 2.5.0-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. 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:nibabel 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: nibabel Source-Version: 2.5.1-2 We believe that the bug you reported is fixed in the latest version of nibabel, 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 nibabel package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 04 Jan 2020 16:52:40 -0500 Source: nibabel Architecture: source Version: 2.5.1-2 Distribution: unstable Urgency: medium Maintainer: NeuroDebian Team Changed-By: Sandro Tosi Closes: 937140 Changes: nibabel (2.5.1-2) unstable; urgency=medium . * Team upload. * Drop python2 support; Closes: #937140 Checksums-Sha1: b80a59050d12dabcbc61969f23bad2c6491c6621 2376 nibabel_2.5.1-2.dsc 07c8b6c3e9e0ee0a945797b6aae8cec228ad38f6 7532 nibabel_2.5.1-2.debian.tar.xz 500c021b23e067175d7f3e47cbf4b60eb56ebca5 8217 nibabel_2.5.1-2_source.buildinfo Checksums-Sha256: 44100294ae3aaf3a306abd9c4db0efc318d3f3339278d57f011d4ffd14dc974f 2376 nibabel_2.5.1-2.dsc 30e1b1a8fa2227fbde8fa4749be7b494f7c046420821a2b6ecaa24c289ec2b4d 7532 nibabel_2.5.1-2.debian.tar.xz e746a8139e0ca9c7fc047c3162ec72441595a2f9144b81384affdb509263e732 8217 nibabel_2.5.1-2_source.buildinfo Files: 63ac81a541e9d93e89329d89edab6cf8 2376 python extra nibabel_2.5.1-2.dsc 03ded2f0f7e0c8143be9c25cb8425346 7532
Bug#947874: libdmapsharing-3.0-2: apt-get source -b libdmapsharing failed with dh_missing errors
Control: reassign -1 src:libdmapsharing 2.9.39-4 Control: severity -1 important Control: tag -1 moreinfo unreproducible Hi, On Wed, 01 Jan 2020 16:02:26 +0530 crvi wrote: > Package: libdmapsharing-3.0-2 > Version: 2.9.39-4 >debian/rules override_dh_missing > make[1]: Entering directory '/home/user/deb- > src/libdmapsharing/libdmapsharing-2.9.39' > dh_missing --fail-missing > dh_missing: usr/lib/x86_64-linux-gnu/girepository-1.0/DMAP-3.0.typelib exists > in debian/tmp but is not installed to anywhere > dh_missing: usr/share/gir-1.0/DMAP-3.0.gir exists in debian/tmp but is not > installed to anywhere I cannot reproduce this behavior in minimal up-to-date buster and sid pbuilder chroots. You either have an older version of some build dependency installed or by building in a non-minimal chroot you pick up some optional tools that "generate more files". Andreas
Processed: Re: libdmapsharing-3.0-2: apt-get source -b libdmapsharing failed with dh_missing errors
Processing control commands: > reassign -1 src:libdmapsharing 2.9.39-4 Bug #947874 [src:libdmapsharing] libdmapsharing-3.0-2: apt-get source -b libdmapsharing failed with dh_missing errors Ignoring request to reassign bug #947874 to the same package Bug #947874 [src:libdmapsharing] libdmapsharing-3.0-2: apt-get source -b libdmapsharing failed with dh_missing errors Ignoring request to alter found versions of bug #947874 to the same values previously set > severity -1 important Bug #947874 [src:libdmapsharing] libdmapsharing-3.0-2: apt-get source -b libdmapsharing failed with dh_missing errors Severity set to 'important' from 'serious' > tag -1 moreinfo unreproducible Bug #947874 [src:libdmapsharing] libdmapsharing-3.0-2: apt-get source -b libdmapsharing failed with dh_missing errors Added tag(s) unreproducible and moreinfo. -- 947874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947874 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937550: marked as done (pysubnettree: Python2 removal in sid/bullseye)
Your message dated Sat, 04 Jan 2020 23:08:13 + with message-id and subject line Bug#937550: fixed in pysubnettree 0.31-2 has caused the Debian Bug report #937550, regarding pysubnettree: 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.) -- 937550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pysubnettree Version: 0.31-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:pysubnettree 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: pysubnettree Source-Version: 0.31-2 We believe that the bug you reported is fixed in the latest version of pysubnettree, 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 pysubnettree package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 04 Jan 2020 17:46:54 -0500 Source: pysubnettree Architecture: source Version: 0.31-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Sandro Tosi Closes: 937550 Changes: pysubnettree (0.31-2) unstable; urgency=medium . [ Ondřej Nový ] * Bump Standards-Version to 4.4.1. . [ Sandro Tosi ] * Drop python2 support; Closes: #937550 Checksums-Sha1: 48b698e864c7702fae10db3047e2b4db4e147149 2079 pysubnettree_0.31-2.dsc 629a214133616d077b28ce4b0205d68f8b19e1cd 4376 pysubnettree_0.31-2.debian.tar.xz 5a7f567db58d767271fb7976c7cdc0baec841b19 6705 pysubnettree_0.31-2_source.buildinfo Checksums-Sha256: e4ba1b1aa0ca79b7f15378cc4e23c1d299c393fd299bbcd0e89a4522950181b4 2079 pysubnettree_0.31-2.dsc 6b6331031c9fdf476d4061885798e05a26ecb7408e10b354bb511dd293039676 4376 pysubnettree_0.31-2.debian.tar.xz 5daa741ae89cbad18fd7ee34e444aad85d56a8c1bd1ec0fb6bd8fac81f0f5eaf 6705 pysubnettree_0.31-
Bug#937557: marked as done (pyte: Python2 removal in sid/bullseye)
Your message dated Sat, 04 Jan 2020 23:08:20 + with message-id and subject line Bug#937557: fixed in pyte 0.4.8-1.1 has caused the Debian Bug report #937557, regarding pyte: 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.) -- 937557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pyte Version: 0.4.8-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - 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:pyte 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: pyte Source-Version: 0.4.8-1.1 We believe that the bug you reported is fixed in the latest version of pyte, 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 pyte package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 04 Jan 2020 17:51:23 -0500 Source: pyte Architecture: source Version: 0.4.8-1.1 Distribution: unstable Urgency: medium Maintainer: Andrew Shadura Changed-By: Sandro Tosi Closes: 937557 Changes: pyte (0.4.8-1.1) unstable; urgency=medium . * Non-maintainer upload. * Drop python2 support; Closes: #937557 Checksums-Sha1: 2d65496b4e29ab6a0124cf41ebcf5a5f6fb08592 1841 pyte_0.4.8-1.1.dsc 71f1d2d5b2364a975bb9ba7d77a8a05ce986987d 2536 pyte_0.4.8-1.1.debian.tar.xz 5839b0da8625d633cbb08cc70bb993ff12f3bc7e 7470 pyte_0.4.8-1.1_source.buildinfo Checksums-Sha256: 1c9fa99be0ab290de27a95e7b5e5e195c8ec5b0666f9beda04727fa501c6d31a 1841 pyte_0.4.8-1.1.dsc 21662fcb8ed180ba06d4160a6ba928288dd7e9353ccdbe93cc7941e6df38053a 2536 pyte_0.4.8-1.1.debian.tar.xz ec380641c115d3cb94dd0fdb0a2d4d4f9e63c283a9be354ba8fc244f22986458 7470 pyte_0.4.8-1.1_source.buildinfo Files: 652f54398abe1afccf1918c12535d296 1841 python optional pyte_0.4.8-1.1.dsc da27453c5d6b2d7bc4038065919de2f0 2536 python optional
Bug#937501: marked as done (pypandoc: Python2 removal in sid/bullseye)
Your message dated Sat, 04 Jan 2020 23:08:07 + with message-id and subject line Bug#937501: fixed in pypandoc 1.4+ds0-2 has caused the Debian Bug report #937501, regarding pypandoc: 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.) -- 937501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pypandoc Version: 1.4+ds0-1.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:pypandoc 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: pypandoc Source-Version: 1.4+ds0-2 We believe that the bug you reported is fixed in the latest version of pypandoc, 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 pypandoc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 04 Jan 2020 17:40:55 -0500 Source: pypandoc Architecture: source Version: 1.4+ds0-2 Distribution: unstable Urgency: medium Maintainer: Elena Grandi Changed-By: Sandro Tosi Closes: 937501 Changes: pypandoc (1.4+ds0-2) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org * d/copyright: Use https protocol in Format field * d/watch: Use https protocol * Convert git repository from git-dpm to gbp layout * Use debhelper-compat instead of debian/compat. . [ Sandro Tosi ] * Drop python2 support; Closes: #937501 Checksums-Sha1: b4a83efd95a6eb1cc802c466773426f03337e342 2177 pypandoc_1.4+ds0-2.dsc 9cbc131e7c15787aeb5be5624af4ce47cc9c67fe 5868 pypandoc_1.4+ds0-2.debian.tar.xz b5483cbfe123cae5f601232aa90c3a3826e90bc6 8809 pypandoc_1.4+ds0-2_source.buildinfo Checksums-Sha256: 1b259373275c449cba95de617c749545d8985540e357b89e263ea18da1c0127e 2177 pypandoc_1.4+ds0-2.dsc 5d4440f9e74e6c9a28c2dd9437a9558a
Processed: pyte: diff for NMU version 0.4.8-1.1
Processing control commands: > tags 937557 + patch Bug #937557 [src:pyte] pyte: Python2 removal in sid/bullseye Added tag(s) patch. -- 937557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937557: pyte: diff for NMU version 0.4.8-1.1
Control: tags 937557 + patch
Dear maintainer,
I've prepared an NMU for pyte (versioned as 0.4.8-1.1). The diff
is attached to this message.
Regards.
diff -Nru pyte-0.4.8/debian/changelog pyte-0.4.8/debian/changelog
--- pyte-0.4.8/debian/changelog 2014-09-07 16:26:52.0 -0400
+++ pyte-0.4.8/debian/changelog 2020-01-04 17:51:23.0 -0500
@@ -1,3 +1,10 @@
+pyte (0.4.8-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop python2 support; Closes: #937557
+
+ -- Sandro Tosi Sat, 04 Jan 2020 17:51:23 -0500
+
pyte (0.4.8-1) unstable; urgency=low
* Initial release.
diff -Nru pyte-0.4.8/debian/control pyte-0.4.8/debian/control
--- pyte-0.4.8/debian/control 2014-09-07 16:32:41.0 -0400
+++ pyte-0.4.8/debian/control 2020-01-04 17:49:58.0 -0500
@@ -4,27 +4,14 @@
Maintainer: Andrew Shadura
Build-Depends:
dh-python,
-python-setuptools (>= 0.6.24),
python3-setuptools (>= 0.6.24),
-python-all (>= 2.6.6-3), python3-all,
-python-pytest, python3-pytest,
-python-sphinx (>= 1.0.7+dfsg) | python3-sphinx,
+python3-all,
+python3-pytest,
+python3-sphinx,
debhelper (>= 9)
Standards-Version: 3.9.5
Homepage: http://github.com/selectel/pyte
-Package: python-pyte
-Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
-Suggests: python-pyte-doc
-Provides: ${python:Provides}
-Description: simple VTXXX-compatible terminal emulator
- pyte is an in-memory VTXXX-compatible terminal emulator, where XXX stands
- for a series of video terminals, developed by DEC between 1970 and 1995.
- .
- pyte is as a fork of vt102, which was an incomplete pure Python
- implementation of VT100 terminal.
-
Package: python3-pyte
Architecture: all
Depends: ${misc:Depends}, ${python3:Depends}
diff -Nru pyte-0.4.8/debian/rules pyte-0.4.8/debian/rules
--- pyte-0.4.8/debian/rules 2014-09-07 16:16:15.0 -0400
+++ pyte-0.4.8/debian/rules 2020-01-04 17:51:18.0 -0500
@@ -1,14 +1,13 @@
#!/usr/bin/make -f
-export PYBUILD_DESTDIR_python2=debian/python-pyte/
export PYBUILD_DESTDIR_python3=debian/python3-pyte/
%:
- dh $@ --with python2,python3,sphinxdoc --buildsystem=pybuild
+ dh $@ --with python3,sphinxdoc --buildsystem=pybuild
override_dh_auto_build:
dh_auto_build
- sphinx-build -b html -d docs/build/doctrees docs docs/build/html
+ python3 -m sphinx -b html -d docs/build/doctrees docs docs/build/html
override_dh_auto_clean:
rm -rf docs/build/*
Processed (with 1 error): your mail
Processing commands for cont...@bugs.debian.org:
> tags 936215 +1 pending
Unknown tag/s: 1.
Recognized are: patch wontfix moreinfo unreproducible help security upstream
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye
bullseye-ignore bookworm bookworm-ignore.
Bug #936215 {Done: Sandro Tosi } [src:blessings] blessings:
Python2 removal in sid/bullseye
Added tag(s) pending.
> Thanks
Stopping processing here.
Please contact me if you need assistance.
--
936215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#937550: marked as pending in pysubnettree
Control: tag -1 pending Hello, Bug #937550 in pysubnettree 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/pysubnettree/commit/729029a423a749ed0bd72914cae742016d8edde5 Drop python2 support; Closes: #937550 (this message was generated automatically) -- Greetings https://bugs.debian.org/937550
Processed: Bug#937550 marked as pending in pysubnettree
Processing control commands: > tag -1 pending Bug #937550 [src:pysubnettree] pysubnettree: Python2 removal in sid/bullseye Added tag(s) pending. -- 937550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948165: marked as pending in ceph
Control: tag -1 pending Hello, Bug #948165 in ceph 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/ceph-team/ceph/commit/c98ea073fc6ec1bfa2a15112616c8c04fb7b1a4b Install bash-completion in /usr again. This change went missing somewhere during the import of the changes done in Ubuntu between 12.2.11 and 14.2.4. Closes: #948165 Thanks: Andreas Beckmann (this message was generated automatically) -- Greetings https://bugs.debian.org/948165
Bug#948165: marked as pending in ceph
Control: tag -1 pending Hello, Bug #948165 in ceph 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/ceph-team/ceph/commit/c98ea073fc6ec1bfa2a15112616c8c04fb7b1a4b Install bash-completion in /usr again. This change went missing somewhere during the import of the changes done in Ubuntu between 12.2.11 and 14.2.4. Closes: #948165 Thanks: Andreas Beckmann (this message was generated automatically) -- Greetings https://bugs.debian.org/948165
Bug#947718: marked as done (fplll ftbfs on armel and mipsel (and m68k, powerpc and sh4))
Your message dated Sat, 04 Jan 2020 22:34:14 + with message-id and subject line Bug#947718: fixed in fplll 5.3.1-2 has caused the Debian Bug report #947718, regarding fplll ftbfs on armel and mipsel (and m68k, powerpc and sh4) 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.) -- 947718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fplll Version: 5.3.1-1 Severity: serious Justification: ftbfs Tags: ftbfs sid bullseye Dear maintainer, Your package fails to build from source on armel and mipsel. Because it started a transition, this failure has more widespread impact than just your package. Please have a look. Paul PS: you'll need to do a source-only upload with the next upload, otherwise the package will not migrate to testing. https://buildd.debian.org/status/package.php?p=fplll Tail of log for fplll on armel: collect2: error: ld returned 1 exit status make[4]: *** [Makefile:1333: latsieve] Error 1 /usr/bin/ld: ./.libs/libfplll.so: undefined reference to `__atomic_store_8' /usr/bin/ld: ./.libs/libfplll.so: undefined reference to `__atomic_load_8' collect2: error: ld returned 1 exit status make[4]: *** [Makefile:1323: fplll] Error 1 make[4]: Leaving directory '/<>/fplll' make[3]: *** [Makefile:898: all] Error 2 make[3]: Leaving directory '/<>/fplll' make[2]: *** [Makefile:496: all-recursive] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [Makefile:384: all] Error 2 make[1]: Leaving directory '/<>' dh_auto_build: make -j4 returned exit code 2 make: *** [debian/rules:8: build-arch] Error 255 signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: fplll Source-Version: 5.3.1-2 We believe that the bug you reported is fixed in the latest version of fplll, 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. Julien Puydt (supplier of updated fplll package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 04 Jan 2020 23:10:06 +0100 Source: fplll Architecture: source Version: 5.3.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Julien Puydt Closes: 947718 Changes: fplll (5.3.1-2) unstable; urgency=medium . * Add workaround for missing -latomic on some arches (Closes: #947718). Checksums-Sha1: 8de5be1474ff2977ab7b15028545ad9a559ab3e0 2117 fplll_5.3.1-2.dsc bedef1040b1219bbc82ca4e2f6c538a833a0154c 8028 fplll_5.3.1-2.debian.tar.xz 22a71a69c84df42f76b6c0045ea619e35a924ec0 5241 fplll_5.3.1-2_source.buildinfo Checksums-Sha256: a7b80cfa7e684f527acd6b93873b98ae5c5945ebbd262269af89b44135e764db 2117 fplll_5.3.1-2.dsc f8c610cfad57e3a2dfe4f99683f6b50ef7de93da797b8cfffe0994679342c40f 8028 fplll_5.3.1-2.debian.tar.xz 6806de717aca514a6beae449220c24e49d8cfbbd1b65720eed4752a72fc3b160 5241 fplll_5.3.1-2_source.buildinfo Files: 8dd9331978c0f2897a3811e39786bc1c 2117 math optional fplll_5.3.1-2.dsc a6d53aa0b6e515cd9795e30907213275 8028 math optional fplll_5.3.1-2.debian.tar.xz b329f1968afa92bcdd013c652a9951a6 5241 math optional fplll_5.3.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAl4RDmkSHGpwdXlkdEBk ZWJpYW4ub3JnAAoJEATFO9f+AwVR4q8P/iq8DQdsqx/eX70cB7XlnSzEYZA5YFYB rSmqCxCj28r07/z7bka8dSb4tVB8pbm5ydXQBjq7P4AHKdzuNhWuW2M8N7lRKMGC T6Gut2ULhvDySwzL6kK1N5VYX0xFjW4fiAasDQKNvdMhZ8p3H2D2ZKLTT+FRyP8c BYm8YMqJVilDuEG9i1xQSCZegf1HzeYAILF36RVuDpnVW2PN8T01d3Il9GUAdLhk EMvxw271P3O7+uLGJrqGjbKZvlDv+C+tjLfKrpR22On4h3A4ufx2SsJr9GRLmvD+ xE/2+mNkfJs+HujKlFug3940W1eZkmf5aTRATSYubfHsZctP+RiEnmHBaI3kXPMs I2SXBHcD0xr/lxqn6x+1fv7fZun9LbfZDAWQUmN8GGsvvTk4GEviNLXPFY1ChgKF UfBmpz85G8FfgMOHcdnU7qXN3aqUCggQ06y1B/ziNTFEcUT6DSTctgLqj9HtrMPf qfacfkceLZyGqF7GJ5uLF2p6UaddTb+S/wEi6Mz3IZPiS/BhOh4b2/GsplUzpKpb TvXSgFlh8xlumpmsfaoreEe0zO210j987pThXOtK9xEA0wK2n+p40fbgVJ9ouiQq 9DCJDVxFMKWs5PRx51jPEQwyvOuERPifzRPqBnvJhdaqzLcC2TgzrJE70XOhYCl8 RWIKfZzlP9MU =wGbM -END PGP SIGNATURE End Message ---
Processed: Bug#948165 marked as pending in ceph
Processing control commands: > tag -1 pending Bug #948165 [ceph-common] ceph-common: missing Breaks+Replaces: ceph-base (<< 14.2.5) Added tag(s) pending. -- 948165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#948165 marked as pending in ceph
Processing control commands: > tag -1 pending Bug #948165 [ceph-common] ceph-common: missing Breaks+Replaces: ceph-base (<< 14.2.5) Ignoring request to alter tags of bug #948165 to the same tags previously set -- 948165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): your mail
Processing commands for cont...@bugs.debian.org:
> tags 936215 +1 peding
Unknown tag/s: 1, peding.
Recognized are: patch wontfix moreinfo unreproducible help security upstream
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye
bullseye-ignore bookworm bookworm-ignore.
Bug #936215 {Done: Sandro Tosi } [src:blessings] blessings:
Python2 removal in sid/bullseye
Requested to add no tags; doing nothing.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
936215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#937514: marked as done (pyquery: Python2 removal in sid/bullseye)
Your message dated Sat, 04 Jan 2020 22:22:07 + with message-id and subject line Bug#937514: fixed in pyquery 1.2.9-4 has caused the Debian Bug report #937514, regarding pyquery: 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.) -- 937514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pyquery Version: 1.2.9-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:pyquery 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: pyquery Source-Version: 1.2.9-4 We believe that the bug you reported is fixed in the latest version of pyquery, 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 pyquery package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 04 Jan 2020 17:00:25 -0500 Source: pyquery Architecture: source Version: 1.2.9-4 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Sandro Tosi Closes: 937514 Changes: pyquery (1.2.9-4) unstable; urgency=medium . [ Ondřej Nový ] * Convert git repository from git-dpm to gbp layout * Use debhelper-compat instead of debian/compat. . [ Sandro Tosi ] * Drop python2 support; Closes: #937514 Checksums-Sha1: b5581ebb5ed0609c15c1e448b678f0382ff8d11e 2003 pyquery_1.2.9-4.dsc bb38d8c757a0c545aa22e2d1d8041c5762feab05 3092 pyquery_1.2.9-4.debian.tar.xz a60c9619cf9b26c8908176960748cffab9f9c57d 6286 pyquery_1.2.9-4_source.buildinfo Checksums-Sha256: 36ef920725174ac9633a12f3447f0ead43cba292da77a197bd2c682cd86e81c8 2003 pyquery_1.2.9-4.dsc 88b98e7285c1f6477aa8e0f169b3e06a892a5ae2cd30c4004f36cf055b10bb55 3092 pyquery_1.2.9-4.debian.tar.xz 3b306da2e53931733eb369b4c1b09660b7ae178a313106d8b206f37ba1470f6d 6286 pyquery_1.
Bug#936215: marked as done (blessings: Python2 removal in sid/bullseye)
Your message dated Sat, 04 Jan 2020 22:21:23 + with message-id and subject line Bug#936215: fixed in blessings 1.6-3 has caused the Debian Bug report #936215, regarding blessings: 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.) -- 936215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:blessings Version: 1.6-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:blessings 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: blessings Source-Version: 1.6-3 We believe that the bug you reported is fixed in the latest version of blessings, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated blessings package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 04 Jan 2020 16:57:03 -0500 Source: blessings Architecture: source Version: 1.6-3 Distribution: unstable Urgency: medium Maintainer: David Villa Alises Changed-By: Sandro Tosi Closes: 936215 Changes: blessings (1.6-3) unstable; urgency=medium . [ Ondřej Nový ] * Fixed VCS URL (https) * d/control: Set Vcs-* to salsa.debian.org * d/watch: Use https protocol * Convert git repository from git-dpm to gbp layout . [ Sandro Tosi ] * Drop python2 support; Closes: #936215 Checksums-Sha1: b865edc015bd283d786734fc6f28cf78a5ef8189 1997 blessings_1.6-3.dsc ececc3b04e80b12ded92cfcbd071255e7e1ca0f0 2356 blessings_1.6-3.debian.tar.xz efc9a89d5298a8a5b32b0700e2941b6d969f4e72 6288 blessings_1.6-3_source.buildinfo Checksums-Sha256: e63f6a3a8e3765a784ba597d488981904ed51851d9eeea2bb0ab6c0f4b1a9cfd 1997 blessings_1.6-3.dsc bfc92ef0019a086c2fee842654a7ddeda93259c6bce1ff5fa561c7a4cb71a648 2356 blessings_1.6-3.debian.tar.xz 933e76423a285bc75ef2c20dee19
Bug#937514: marked as pending in pyquery
Control: tag -1 pending Hello, Bug #937514 in pyquery 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/pyquery/commit/beb1a07f0d8bda90f50d88d8e215c5a604999d62 Drop python2 support; Closes: #937514 (this message was generated automatically) -- Greetings https://bugs.debian.org/937514
Processed: Bug#937514 marked as pending in pyquery
Processing control commands: > tag -1 pending Bug #937514 [src:pyquery] pyquery: Python2 removal in sid/bullseye Added tag(s) pending. -- 937514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#936215 marked as pending in blessings
Processing control commands: > tag -1 pending Bug #936215 [src:blessings] blessings: Python2 removal in sid/bullseye Added tag(s) pending. -- 936215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#936215: marked as pending in blessings
Control: tag -1 pending Hello, Bug #936215 in blessings 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/blessings/commit/69f49a4b302187667ec2124be7714b65d2f2bf86 Drop python2 support; Closes: #936215 (this message was generated automatically) -- Greetings https://bugs.debian.org/936215
Bug#937140: marked as pending in pynifti
Control: tag -1 pending Hello, Bug #937140 in pynifti 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/neurodebian-team/nibabel/commit/fe855d7cf70bcbf61c942261012475a9e4739bbf Drop python2 support; Closes: #937140 (this message was generated automatically) -- Greetings https://bugs.debian.org/937140
Processed: Bug#937140 marked as pending in pynifti
Processing control commands: > tag -1 pending Bug #937140 [src:nibabel] nibabel: Python2 removal in sid/bullseye Added tag(s) pending. -- 937140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948085: marked as done (jengelman-shadow build depends on openjdk-8-jdk-headless)
Your message dated Sat, 04 Jan 2020 21:34:44 + with message-id and subject line Bug#948085: fixed in jengelman-shadow 4.0.3-2 has caused the Debian Bug report #948085, regarding jengelman-shadow build depends on openjdk-8-jdk-headless 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.) -- 948085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jengelman-shadow Version: 4.0.3-1 Severity: serious jengelman-shadow build depends on openjdk-8-jdk-headless that is not in buster and will not be in bullseye. If possible default-jdk-headless should be uised instead. --- End Message --- --- Begin Message --- Source: jengelman-shadow Source-Version: 4.0.3-2 We believe that the bug you reported is fixed in the latest version of jengelman-shadow, 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. tony mancill (supplier of updated jengelman-shadow package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 04 Jan 2020 13:07:14 -0800 Source: jengelman-shadow Architecture: source Version: 4.0.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: tony mancill Closes: 948085 Changes: jengelman-shadow (4.0.3-2) unstable; urgency=medium . * Team upload * Build-depend on default-jdk-headless (Closes: #948085) * Specify debhelper compat via debhelper-compat dependency * Bump Standards-Version to 4.4.1 * No longer set org.gradle.java.home in gradle.properties * Set "Rules-Requires-Root: no" in debian/control Checksums-Sha1: 633e2f6a10f40c998b45968f2cde06cc824cfd60 2231 jengelman-shadow_4.0.3-2.dsc d2f7bdd979d9fc02ce06ce211d5ae20abfa0e713 3480 jengelman-shadow_4.0.3-2.debian.tar.xz c453b9f76b288aec7ec98222b0ebf7bc4b59ee0b 11205 jengelman-shadow_4.0.3-2_amd64.buildinfo Checksums-Sha256: 7dd29046cc4eff807ccd50f4d096575b664f6684948760362a77d64bc8c224d8 2231 jengelman-shadow_4.0.3-2.dsc 22c350e1b3c2a486419b71513ddb04bef54f1d82ada382e189a95524aebdac38 3480 jengelman-shadow_4.0.3-2.debian.tar.xz 30c5b7b51f686a25a653bc8878e56a4e426e052395ecaac0efc70826dc8d855c 11205 jengelman-shadow_4.0.3-2_amd64.buildinfo Files: dd82ba7b6b407e388e4eddd0dee32920 2231 java optional jengelman-shadow_4.0.3-2.dsc 3918e66456699ac0f0a5c69ad32f1873 3480 java optional jengelman-shadow_4.0.3-2.debian.tar.xz ab7b7e00414a20ec21751ec1b6b78f2f 11205 java optional jengelman-shadow_4.0.3-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAl4RAQoUHHRtYW5jaWxs QGRlYmlhbi5vcmcACgkQIdIFiZdLPpYMehAAwHeHEIy6jQuV6ligg/rjGsED7R7W +KVbfJWt7RGzc5SErOobqXXyGBsIppTOpeg4iquhRUHjd4OD2t805s8CvnQLsxsD eXRVtGQCwKOaUpu2CdndhFlGn6/xSFQc7eZXqN114uD29HRwb7NB5SBk9Lr3uJHD 3dWVJkgcoxFVZ5Dlel7xu0TNn8MiXH4zwxaegr3M5Hh2lOtQPw6+Iu+CFPliOtu7 9r7vd5mcBgRqAN+D6b8useBBjJ/HGWP2g4arXY81yQiaotU+820G2O2xbKKHL+H3 WDOKvqZ5lb/l3I3BAxnvv5X8KRu5agpZGuyWtuW8pdLsuoh/+uriPDZ62Zjtq7EG tpYePSlTGVgjrzdVEqml0+BJAUSPdjVMu76HlLQnVSzQ2fDHRQNen4DX9tjIQCWK rQ1NgUKLD9q52OdX9m4BlLIN6rfl4H3nT3rVaUf5a8AEBPJ10EFr/MN7J1ATTDSw Dj9TLjYnHugeUecq5PeHxDl7gMWWGuf2YrvetEcFrLBDLrEqQuAfGB1vhpExWyLB Vykvkjf9nqJ4fvXjW2XMkgJ/fZ9fD/JRkU1DDl11UlJSVBl77mUo0/xzbyz+Cgrh mfN4TkvvfSwDtCb2loHYEJirStUODN3M9n1FVmvQ5fY5SXu2Mc0ZvSGeQtYIw4Y7 F669AmWjgFbf4uM= =7unt -END PGP SIGNATURE End Message ---
Processed: py2removal RC severity updates - 2020-01-04 21:36:06.254632+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 > # for more details on this severity bump > # python-blessings is a module and has 0 external rdeps or not in testing > severity 936215 serious Bug #936215 [src:blessings] blessings: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-pypandoc is a module and has 0 external rdeps or not in testing > severity 937501 serious Bug #937501 [src:pypandoc] pypandoc: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-pyquery is a module and has 0 external rdeps or not in testing > severity 937514 serious Bug #937514 [src:pyquery] pyquery: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-subnettree is a module and has 0 external rdeps or not in testing > severity 937550 serious Bug #937550 [src:pysubnettree] pysubnettree: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-pyte is a module and has 0 external rdeps or not in testing > severity 937557 serious Bug #937557 [src:pyte] pyte: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 936215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936215 937501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937501 937514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937514 937550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937550 937557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948085: marked as pending in jengelman-shadow
Control: tag -1 pending Hello, Bug #948085 in jengelman-shadow reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/jengelman-shadow/commit/1d553494f6780352b2945c9c87317756a46757e0 Build-depend on default-jdk-headless (Closes: #948085) (this message was generated automatically) -- Greetings https://bugs.debian.org/948085
Processed: Bug#948085 marked as pending in jengelman-shadow
Processing control commands: > tag -1 pending Bug #948085 [src:jengelman-shadow] jengelman-shadow build depends on openjdk-8-jdk-headless Added tag(s) pending. -- 948085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948159: mmdebstrap: autopkgtest issue: +libcrypt1:amd64 in chroot
Hi Paul, Quoting Paul Gevers (2020-01-04 20:24:50) > With a recent upload of mmdebstrap the autopkgtest of mmdebstrap fails > in testing when that autopkgtest is run with the binary packages of > mmdebstrap from unstable. It passes when run with only packages from > testing. In tabular form: >passfail > mmdebstrap from testing0.5.1-3 > all others from testingfrom testing > > I copied some of the output at the bottom of this report. It seems that > this apparent regression is actually a sensitivity of the test to what > is in the base system. Recently libcrypt got split of from gcc (but > hasn't migrated to testing yet). So, without changes to your test, it > can either pass in unstable, or in testing, but not both. Please > consider how you want to fix this, as currently your package can't > migrate to testing [1]. yes, I was aware of the introduction of libcrypt, that's why I uploaded 0.5.1-3 which addresses precisely this change. My naive assumption was, that once libcrypt migrates to testing, mmdebstrap would migrate just fine. Thanks a lot for opening this bug report because apparently I have a misunderstanding about how our CI and migration work together with automatic migration and maybe you can help me clear up my understanding of it? :) Thanks! cheers, josch signature.asc Description: signature
Processed: reassign 947927 to mimedefang,spamassassin, found 947927 in 3.4.2-1~deb9u2, found 947927 in 2.79-2
Processing commands for cont...@bugs.debian.org: > reassign 947927 mimedefang,spamassassin Bug #947927 [mimedefang] mimedefang: Mimedefang is unable to start after upgrade of spamassassin Bug reassigned from package 'mimedefang' to 'mimedefang,spamassassin'. No longer marked as found in versions mimedefang/2.79-2. Ignoring request to alter fixed versions of bug #947927 to the same values previously set > found 947927 3.4.2-1~deb9u2 Bug #947927 [mimedefang,spamassassin] mimedefang: Mimedefang is unable to start after upgrade of spamassassin There is no source info for the package 'mimedefang' at version '3.4.2-1~deb9u2' with architecture '' Marked as found in versions spamassassin/3.4.2-1~deb9u2. > found 947927 2.79-2 Bug #947927 [mimedefang,spamassassin] mimedefang: Mimedefang is unable to start after upgrade of spamassassin There is no source info for the package 'spamassassin' at version '2.79-2' with architecture '' Marked as found in versions mimedefang/2.79-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 947927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
