Processed: critical bluestore data corruption
Processing commands for cont...@bugs.debian.org: > owner 947457 ! Bug #947457 [ceph-osd] critical bluestore data corruption Owner recorded as Milan Kupcevic . > tags 947457 + pending Bug #947457 [ceph-osd] critical bluestore data corruption Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 947457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938243: marked as done (python-uritools: Python2 removal in sid/bullseye)
Your message dated Fri, 27 Dec 2019 07:04:47 + with message-id and subject line Bug#938243: fixed in python-uritools 3.0.0-1 has caused the Debian Bug report #938243, regarding python-uritools: 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.) -- 938243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-uritools Version: 2.2.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-uritools 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-uritools Source-Version: 3.0.0-1 We believe that the bug you reported is fixed in the latest version of python-uritools, 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. Stein Magnus Jodal (supplier of updated python-uritools 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: Wed, 25 Dec 2019 09:06:43 +0100 Source: python-uritools Architecture: source Version: 3.0.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Stein Magnus Jodal Closes: 938243 Changes: python-uritools (3.0.0-1) unstable; urgency=medium . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat. * Bump Standards-Version to 4.4.1. . [ Stein Magnus Jodal ] * New upstream release * Drop Python 2 support (Closes: #938243) Checksums-Sha1: 7402e50088c55d6225b52763fd2ecc935f94438d 2109 python-uritools_3.0.0-1.dsc 6929b4109b1bc8b1734bf9c2a512201a2dd33edd 22936 python-uritools_3.0.0.orig.tar.gz 6e41ae976d9d71759dfa75375d266a5c0e11ae8c 2792 python-uritools_3.0.0-1.debian.tar.xz 32aa5005aca0a6ccb697ab661de648f30d3e5d24 7276 python-uritools_3.0.0-1_amd64.buildinfo Checksums-Sha256:
Bug#947457: critical bluestore data corruption
Package: ceph-osd Version: 14.2.4-4 Severity: grave Tags: upstream fixed-upstream A critical bluestore data corruption bug[0][1] affecting OSDs configured with separate db and/or wal devices has been introduced in 14.2.3 and is affecting both 14.2.3 and 14.2.4 upstream releases[2]. This bug has been fixed in upstream version 14.2.5. Fix is simple[4] and can be easily applied/backported to Debian release 14.2.4. [0] https://tracker.ceph.com/issues/42223 [1] https://github.com/ceph/ceph/pull/31621 [2] https://lists.ceph.io/hyperkitty/list/ceph-annou...@ceph.io/message/X6TNSDQK5DVKO6XFJW3DMJAJV63PLDYM/ [3] https://ceph.io/releases/v14-2-5-nautilus-released/ [4] https://github.com/ceph/ceph/commit/117c8b5ca0130e02be98848b6c323812e271af27
Bug#936110: marked as done (aff4: Python2 removal in sid/bullseye)
Your message dated Fri, 27 Dec 2019 06:37:46 + with message-id and subject line Bug#947417: Removed package(s) from unstable has caused the Debian Bug report #936110, regarding aff4: 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.) -- 936110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:aff4 Version: 0.24.post1-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:aff4 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.24.post1-4+rm Dear submitter, as the package aff4 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/947417 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#938525: marked as done (spectacle: Python2 removal in sid/bullseye)
Your message dated Fri, 27 Dec 2019 06:34:01 + with message-id and subject line Bug#947353: Removed package(s) from unstable has caused the Debian Bug report #938525, regarding spectacle: 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.) -- 938525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938525 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:spectacle Version: 0.25-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:spectacle 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.25-1+rm Dear submitter, as the package spectacle 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/947353 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#938277: marked as done (python-xmlbuilder: Python2 removal in sid/bullseye)
Your message dated Fri, 27 Dec 2019 06:35:10 + with message-id and subject line Bug#947359: Removed package(s) from unstable has caused the Debian Bug report #938277, regarding python-xmlbuilder: 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.) -- 938277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938277 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-xmlbuilder Version: 1.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-xmlbuilder If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.0-1+rm Dear submitter, as the package python-xmlbuilder 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/947359 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#935212: marked as done (python-apns-client: Please port to Python 3 and/or drop Python 2 package)
Your message dated Fri, 27 Dec 2019 06:34:27 + with message-id and subject line Bug#947358: Removed package(s) from unstable has caused the Debian Bug report #935212, regarding python-apns-client: Please port to Python 3 and/or drop Python 2 package 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.) -- 935212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-apns-client Severity: normal User: debian-pyt...@lists.debian.org Usertags: py2removal Hello, please port python-apns-client to Python3 and/or drop the python 2 package. This will help the goal of removing Python 2 from Debian, and would also (more immediately) allow to remove packages currently dependencies of this one. More info at: https://wiki.debian.org/Python/2Removal Thanks, Sandro --- End Message --- --- Begin Message --- Version: 0.1.8-2+rm Dear submitter, as the package python-apns-client 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/947358 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#945681: marked as done (gvb: Python2 removal in sid/bullseye)
Your message dated Fri, 27 Dec 2019 05:19:14 + with message-id and subject line Bug#945681: fixed in gvb 1.4-1.1 has caused the Debian Bug report #945681, regarding gvb: 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.) -- 945681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gvb Version: 1.4-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: gvb Source-Version: 1.4-1.1 We believe that the bug you reported is fixed in the latest version of gvb, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 945...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated gvb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 26 Dec 2019 15:00:50 +0200 Source: gvb Architecture: source Version: 1.4-1.1 Distribution: unstable Urgency: medium Maintainer: Pietro Battiston Changed-By: Adrian Bunk Closes: 945681 Changes: gvb (1.4-1.1) unstable; urgency=medium . * Non-maintainer upload. * Correct dependency from python-gi to python3-gi. (Closes: #945681) Checksums-Sha1: c42c618153ee71edc6bbe855712743014c7f8477 1863 gvb_1.4-1.1.dsc dcc67a45a7f3183a7763ed0b74f24e554ea12a90 9652 gvb_1.4-1.1.debian.tar.xz Checksums-Sha256: 2640251e7c240043eb692e8d3f1435ce40fe005f0a5ab6899395d485f77a5dd2 1863 gvb_1.4-1.1.dsc 7b8c11dfbf635b42319e9cac1f486a03354b5182fe4dadbbc0ff498801279f9b 9652 gvb_1.4-1.1.debian.tar.xz Files: 7e1cfb89c3c67679ee4c456c27c25ad3 1863 science optional gvb_1.4-1.1.dsc 9859be480b9d83bebe1b98823e465b4f 9652 science optional gvb_1.4-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl4Er8oACgkQiNJCh6LY mLEWJA//eSehqwPmlgtH4ooaWe8OE2+aev+9GKIoYZMQClPUhqfFoYjgbU2zWpT2 eHmmLkHfobN3H+CYREunfTCUj2cuWtyhiYn/AjRvTJb/I6MUCt2XZh03SRJuZHM+ YQPbjoFK8TXXM28kq5ehnqCQelel6PtUtJK47WLNJAIl+gxKVz7YLx4rs4Nw5yqM
Processed: tagging 936251
Processing commands for cont...@bugs.debian.org: > tags 936251 + upstream Bug #936251 [src:bup] bup: Python2 removal in sid/bullseye Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 936251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945681: gvb: diff for NMU version 1.4-1.1
On Thu, Dec 26, 2019 at 04:18:36PM +0100, Pietro Battiston wrote: > Dear Adrian, Dear Pietro, > thank you, I really appreciate. I was planning to fix that packaging > mistake, but as you might have noticed, I have really slow reactions > lately no worries, everyone has sometimes more urgent things in life. > - and then, I still need to go through a sponsor. So if you > prefer, feel free to re-upload the package without delay. Thanks, done. > Pietro cu Adrian
Bug#945605: python-neovim: diff for NMU version 0.3.0-1.1
On Mon, Dec 23, 2019 at 12:36:25PM +0200, Adrian Bunk wrote: > I've prepared an NMU for python-neovim (versioned as 0.3.0-1.1) and > uploaded it to DELAYED/15. Please feel free to tell me if I should > cancel it. I've uploaded the new upstream version (0.4.0) which contains these fixes. It's going through NEW though, since I also followed upstream's rename (now src:python-pynvim, python3-pynvim). Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#947148: libltdl7: lt_dlopen() returns handle but lt_dlerror() returns non-NULL with OpenMPI4
Followup-For: Bug #947148
Control: reassign -1 libltdl7 2.4.6-11
Control: retitle -1 libltdl7: lt_dlopen() returns handle but lt_dlerror()
returns non-NULL with OpenMPI4
Hi,
the bug does not manifest with plain dlopen() (see test_dlopen.c), so
this seems to be rather a ltdl problem:
If OpenMPI4 is loaded, attempting to lt_dlopen() some kernel generated
by pocl yields an inconsistent result:
* the returned lt_dlhandle is *not NULL*
* the error string returned by subsequent lt_dlerror() is *not NULL*
Andreas
// mpicc -o test_dlopen test_dlopen.c -ldl
#include
#include
#include
int main(int argc, char **argv)
{
MPI_Init(, );
void * handle = dlopen ("./foo.so", RTLD_NOW | RTLD_LOCAL);
const char * dl_error = dlerror ();
printf("%p %s\n", handle, dl_error ? dl_error : "(null)");
}
Processed: Re: libltdl7: lt_dlopen() returns handle but lt_dlerror() returns non-NULL with OpenMPI4
Processing control commands: > reassign -1 libltdl7 2.4.6-11 Bug #947148 [src:openmpi] openmpi: causes lt_dlopen() to fail with 'can't close resident module' Bug reassigned from package 'src:openmpi' to 'libltdl7'. No longer marked as found in versions openmpi/4.0.2-4. Ignoring request to alter fixed versions of bug #947148 to the same values previously set Bug #947148 [libltdl7] openmpi: causes lt_dlopen() to fail with 'can't close resident module' Marked as found in versions libtool/2.4.6-11. > retitle -1 libltdl7: lt_dlopen() returns handle but lt_dlerror() returns > non-NULL with OpenMPI4 Bug #947148 [libltdl7] openmpi: causes lt_dlopen() to fail with 'can't close resident module' Changed Bug title to 'libltdl7: lt_dlopen() returns handle but lt_dlerror() returns non-NULL with OpenMPI4' from 'openmpi: causes lt_dlopen() to fail with 'can't close resident module''. -- 947148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947448: pyfeed: missing Build-Depends: dh-python
Source: pyfeed Version: 1.0~prerelease-2 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, pyfeed/experimental FTBFS with fakeroot debian/rules clean dh clean --with=python2,python3 dh: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 13) line 1. BEGIN failed--compilation aborted at (eval 13) line 1. make: *** [debian/rules:35: clean] Error 255 Andreas
Bug#947446: libreoffice: ure split lacks proper versioned Breaks+Replaces
Source: libreoffice Version: 1:6.4.0~rc1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi Rene, the ure package was split recently but this lacks proper versioned Breaks+Replaces in the new packages. This allows for unwanted partial upgrades mixing a pre-split ure package with post-split e.g. libjuh-java which will leave a crippled ure package installed (but apt/dpkg think everything is fine) if libjuh-java gets removed again. Replaces should always be used with a matching Breaks. (Taking away a file from a replaced package "Breaks" that version. Ownership has changed, but the replaced package does not know about it.) The Breaks+Replaces should be versioned unless the replaced package does no longer exist. (The package version that no longer ships the moved file does not need to get replaced) There were some more package splits needeing proper B+R, too. These packages seem to be affected (but I may have missed some), versions according to changelog entries where I found them: missing Breaks+Replaces: ure (<< 1:6.4.0~beta1-1) * libjuh-java * libjurt-java * libridl-java * libunoloader-java missing Breaks+Replaces: libreoffice-java-common (<< 1:6.4.0~beta1-2) * libreoffice-smoketest-data missing Breaks+Replaces: libreoffice-java-common (<< ???) * libunoil-java missing Breaks+Replaces: libreoffice-officebean (<< ???) * libofficebean-java Cheers, Andreas
Bug#937293: [Piuparts-devel] Bug#919170: Bug#919170: Please update dependency to python3-debianbts
On 26.12.2019 17.11, Holger Levsen wrote: > many thanks, merged and deployed, now this is left: > File > "/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/__init__.py", > line 58, in readline > empty = not self._refill() > File > "/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/__init__.py", > line 49, in _refill > chunk = chunk.decode() > UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc3 in position 14159: > unexpected end of data This did not happen in my test setup, but I have a theory of what is causing this. Could you check if https://salsa.debian.org/debian/piuparts/merge_requests/18 fixes it?
Bug#937627: marked as done (python-cachetools: Python2 removal in sid/bullseye)
Your message dated Thu, 26 Dec 2019 22:19:55 + with message-id and subject line Bug#937627: fixed in python-cachetools 3.1.1-3 has caused the Debian Bug report #937627, regarding python-cachetools: 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.) -- 937627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-cachetools Version: 3.1.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:python-cachetools 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-cachetools Source-Version: 3.1.1-3 We believe that the bug you reported is fixed in the latest version of python-cachetools, 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-cachetools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 26 Dec 2019 16:54:38 -0500 Source: python-cachetools Architecture: source Version: 3.1.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Sandro Tosi Closes: 937627 Changes: python-cachetools (3.1.1-3) unstable; urgency=medium . * Team upload. * Drop python2 support; Closes: #937627 Checksums-Sha1: 7910af3a57e9173c5002c6a37bb119e7cd9c7cfa 2102 python-cachetools_3.1.1-3.dsc c4378445b2ab1a6715ba6f2a7ba324dced97b8ce 3428 python-cachetools_3.1.1-3.debian.tar.xz 929987f26f623a575aceca1f5c8f6b78c7ad10b3 6329 python-cachetools_3.1.1-3_source.buildinfo Checksums-Sha256: 9817b4091e40906479c47d50be6e069a5753cdfa4182627281cda1cf7904b957 2102 python-cachetools_3.1.1-3.dsc d819288fd4ac08abd3dae75b3617ceab971e7d4fe104254ee9c3d5600911482d 3428 python-cachetools_3.1.1-3.debian.tar.xz 665608808ba8c0948c080c7a5a0adc24892607b27e942695ea66d695f86ef138
Bug#947444: flatzinc: ships a copy of minizinc: /usr/share/minizinc/gecode/*
Package: flatzinc Version: 6.2.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 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Preparing to unpack .../flatzinc_6.2.0-1_amd64.deb ... Unpacking flatzinc (6.2.0-1) over (6.1.0-2+b2) ... dpkg: error processing archive /var/cache/apt/archives/flatzinc_6.2.0-1_amd64.deb (--unpack): trying to overwrite '/usr/share/minizinc/gecode/all_different_int.mzn', which is also in package minizinc 2.1.7+dfsg1-1+b1 Errors were encountered while processing: /var/cache/apt/archives/flatzinc_6.2.0-1_amd64.deb cheers, Andreas minizinc=2.1.7+dfsg1-1+b1_flatzinc=6.2.0-1.gz Description: application/gzip
Bug#947443: nvidia-texture-tools: FTBFS: undefined reference to symbol '_ZN2nv3Fit37computePrincipalComponent_EigenSolverEiPKNS_7Vector4E'
Source: nvidia-texture-tools Version: 2.1.0-git20160229+dfsg-2~exp1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, nvidia-texture-tools/experimental FTBFS in a current sid/experimental environment: https://buildd.debian.org/status/package.php?p=nvidia-texture-tools=experimental [ 90%] Linking CXX executable imperativeapi cd /<>/obj-x86_64-linux-gnu/src/nvtt/tests && /usr/bin/cmake -E cmake_link_script CMakeFiles/imperativeapi.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fopenmp -O3 -DNDEBUG -Wl,-z,relro -Wl,-z,now -rdynamic CMakeFiles/imperativeapi.dir/imperativeapi.cpp.o -o imperativeapi -Wl,-rpath,/<>/obj-x86_64-linux-gnu/src/nvtt:/<>/obj-x86_64-linux-gnu/src/nvimage:/<>/obj-x86_64-linux-gnu/src/nvmath:/<>/obj-x86_64-linux-gnu/src/nvcore ../libnvtt.so.2.1.0 ../../nvimage/libnvimage.so.2.1.0 ../../nvmath/libnvmath.so.2.1.0 ../../../extern/poshlib/libposh.a ../../bc6h/libbc6h.a ../../bc7/libbc7.a ../../nvthread/libnvthread.a ../../nvcore/libnvcore.so.2.1.0 -ldl ../squish/libsquish.a /usr/bin/ld: ../../bc7/libbc7.a(avpcl_mode6.cpp.o): undefined reference to symbol '_ZN2nv3Fit37computePrincipalComponent_EigenSolverEiPKNS_7Vector4E' /usr/bin/ld: ../../nvmath/libnvmath.so.2.1.0: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status make[3]: *** [src/nvtt/tests/CMakeFiles/imperativeapi.dir/build.make:96: src/nvtt/tests/imperativeapi] Error 1 This could be related to GCC 9 being the default compiler nowadays. Cheers, Andreas
Processed: limit source to esys-particle, tagging 936489
Processing commands for cont...@bugs.debian.org: > limit source esys-particle Limiting to bugs with field 'source' containing at least one of 'esys-particle' Limit currently set to 'source':'esys-particle' > tags 936489 + pending Bug #936489 [src:esys-particle] esys-particle: Python2 removal in sid/bullseye Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 936489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947441: libignition-cmake2-dev: file conflicts with libignition-cmake-dev: /usr/share/ignition/ignition-cmake0/doxygen/*
Package: libignition-cmake2-dev Version: 2.1.1+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install 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 .../libignition-cmake2-dev_2.1.1+dfsg-2_amd64.deb ... Unpacking libignition-cmake2-dev:amd64 (2.1.1+dfsg-2) ... dpkg: error processing archive /var/cache/apt/archives/libignition-cmake2-dev_2.1.1+dfsg-2_amd64.deb (--unpack): trying to overwrite '/usr/share/ignition/ignition-cmake0/doxygen/doxygen.css', which is also in package libignition-cmake-dev:amd64 0.6.1-1+b1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libignition-cmake2-dev_2.1.1+dfsg-2_amd64.deb The following files are shipped by both packages: usr/share/ignition/ignition-cmake0/doxygen/doxygen.css usr/share/ignition/ignition-cmake0/doxygen/dynsections.js usr/share/ignition/ignition-cmake0/doxygen/google_material_icons.css usr/share/ignition/ignition-cmake0/doxygen/ignition_logo.svg usr/share/ignition/ignition-cmake0/doxygen/ignition_logo_white.svg usr/share/ignition/ignition-cmake0/doxygen/material.deep_orange-blue.min.css usr/share/ignition/ignition-cmake0/doxygen/material.js You either need to move them to a different location or add Breaks+Replaces. cheers, Andreas libignition-cmake-dev=0.6.1-1+b1_libignition-cmake2-dev=2.1.1+dfsg-2.log.gz Description: application/gzip
Processed: py2removal RC severity updates - 2019-12-26 21:36:57.419682+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-cachetools is a module and has 0 external rdeps or not in testing > severity 937627 serious Bug #937627 [src:python-cachetools] python-cachetools: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-uritools is a module and has 0 external rdeps or not in testing > severity 938243 serious Bug #938243 [src:python-uritools] python-uritools: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 937627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937627 938243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947433: waitress: CVE-2019-16789
Source: waitress Version: 1.3.1-4 Severity: grave Tags: security upstream Hi, The following vulnerability was published for waitress, filling a distinct bug for that as the already filled #947306 for two other CVEs as this one is only fixed in 1.4.1 upstream. CVE-2019-16789[0]: | In Waitress through version 1.4.0, if a proxy server is used in front | of waitress, an invalid request may be sent by an attacker that | bypasses the front-end and is parsed differently by waitress leading | to a potential for HTTP request smuggling. Specially crafted requests | containing special whitespace characters in the Transfer-Encoding | header would get parsed by Waitress as being a chunked request, but a | front-end server would use the Content-Length instead as the Transfer- | Encoding header is considered invalid due to containing invalid | characters. If a front-end server does HTTP pipelining to a backend | Waitress server this could lead to HTTP request splitting which may | lead to potential cache poisoning or unexpected information | disclosure. This issue is fixed in Waitress 1.4.1 through more strict | HTTP field validation. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-16789 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16789 [1] https://github.com/Pylons/waitress/commit/11d9e138125ad46e951027184b13242a3c1de017 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Processed: tigervnc: CVE-2019-15691 CVE-2019-15692 CVE-2019-15693 CVE-2019-15694 CVE-2019-15695
Processing control commands: > found -1 1.9.0+dfsg-3 Bug #947428 [src:tigervnc] tigervnc: CVE-2019-15691 CVE-2019-15692 CVE-2019-15693 CVE-2019-15694 CVE-2019-15695 Marked as found in versions tigervnc/1.9.0+dfsg-3. -- 947428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947428: tigervnc: CVE-2019-15691 CVE-2019-15692 CVE-2019-15693 CVE-2019-15694 CVE-2019-15695
Source: tigervnc Version: 1.9.0+dfsg-4 Severity: grave Tags: security upstream Control: found -1 1.9.0+dfsg-3 Hi, The following vulnerabilities were published for tigervnc. CVE-2019-15691[0]: | TigerVNC version prior to 1.10.1 is vulnerable to stack use-after- | return, which occurs due to incorrect usage of stack memory in | ZRLEDecoder. If decoding routine would throw an exception, ZRLEDecoder | may try to access stack variable, which has been already freed during | the process of stack unwinding. Exploitation of this vulnerability | could potentially result into remote code execution. This attack | appear to be exploitable via network connectivity. CVE-2019-15692[1]: | TigerVNC version prior to 1.10.1 is vulnerable to heap buffer | overflow. Vulnerability could be triggered from CopyRectDecoder due to | incorrect value checks. Exploitation of this vulnerability could | potentially result into remote code execution. This attack appear to | be exploitable via network connectivity. CVE-2019-15693[2]: | TigerVNC version prior to 1.10.1 is vulnerable to heap buffer | overflow, which occurs in TightDecoder::FilterGradient. Exploitation | of this vulnerability could potentially result into remote code | execution. This attack appear to be exploitable via network | connectivity. CVE-2019-15694[3]: | TigerVNC version prior to 1.10.1 is vulnerable to heap buffer | overflow, which could be triggered from DecodeManager::decodeRect. | Vulnerability occurs due to the signdness error in processing | MemOutStream. Exploitation of this vulnerability could potentially | result into remote code execution. This attack appear to be | exploitable via network connectivity. CVE-2019-15695[4]: | TigerVNC version prior to 1.10.1 is vulnerable to stack buffer | overflow, which could be triggered from CMsgReader::readSetCursor. | This vulnerability occurs due to insufficient sanitization of | PixelFormat. Since remote attacker can choose offset from start of the | buffer to start writing his values, exploitation of this vulnerability | could potentially result into remote code execution. This attack | appear to be exploitable via network connectivity. 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-15691 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15691 [1] https://security-tracker.debian.org/tracker/CVE-2019-15692 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15692 [2] https://security-tracker.debian.org/tracker/CVE-2019-15693 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15693 [3] https://security-tracker.debian.org/tracker/CVE-2019-15694 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15694 [4] https://security-tracker.debian.org/tracker/CVE-2019-15695 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15695 Please adjust the affected versions in the BTS as needed. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-3-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Processed: bug 947425 is forwarded to https://github.com/ar-/incron/issues/36
Processing commands for cont...@bugs.debian.org: > forwarded 947425 https://github.com/ar-/incron/issues/36 Bug #947425 [incron] incron crashes in IncronTabEntry::GetSafePath due to use-after-free bug Set Bug forwarded-to-address to 'https://github.com/ar-/incron/issues/36'. > thanks Stopping processing here. Please contact me if you need assistance. -- 947425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947426: python-pysam ftbfs with htslib 1.10.2
Source: python-pysam Version: 0.15.2+ds-2 Severity: serious Justification: ftbfs Tags: ftbfs sid bullseye Dear maintainer, Your package is part of the htslib 1.10.2 transition. I tried to binNMU your package but it fails to build from source. Please have a look. Paul https://buildd.debian.org/status/package.php?p=python-pysam Tail of log for python-pysam on amd64: 24840 | __pyx_t_12 = PyFloat_FromDouble(__pyx_v_qual); if (unlikely(!__pyx_t_12)) __PYX_ERR(0, 873, __pyx_L1_error) |^~~~ x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 build/temp.linux-amd64-3.7/pysam/libcvcf.o -L/<>/pysam -L/<>/.pybuild/cpython3_3.7_pysam/build/pysam -L/<>/.pybuild/cpython3_3.7_pysam/build/pysam -L/<>/.pybuild/cpython3_3.7_pysam/build/pysam -L/<>/.pybuild/cpython3_3.7_pysam/build/pysam -L/<>/.pybuild/cpython3_3.7_pysam/build/pysam -L/<>/.pybuild/cpython3_3.7_pysam/build/pysam -L/<>/.pybuild/cpython3_3.7_pysam/build/pysam -L/<>/.pybuild/cpython3_3.7_pysam/build/pysam -L/<>/.pybuild/cpython3_3.7_pysam/build/pysam -L/<>/.pybuild/cpython3_3.7_pysam/build/pysam -L/<>/.pybuild/cpython3_3.7_pysam/build/pysam -L/<>/.pybuild/cpython3_3.7_pysam/build/pysam -L/<>/.pybuild/cpython3_3.7_pysam/build/pysam -lz -lhts -lchtslib.cpython-37m-x86_64-linux-gnu -lcutils.cpython-37m-x86_64-linux-gnu -o /<>/.pybuild/cpython3_3.7_pysam/build/pysam/libcvcf.cpython-37m-x86_64-linux-gnu.so -Wl,-rpath,$ORIGIN debian/rules override_dh_auto_test make[1]: Entering directory '/<>' cd tests/pysam_data && /usr/bin/make all make[2]: Entering directory '/<>/tests/pysam_data' samtools faidx ex1.fa samtools import ex1.fa.fai ex1.sam.gz ex1.bam make[2]: *** [Makefile:56: ex1.bam] Segmentation fault make[2]: *** Deleting file 'ex1.bam' make[2]: Leaving directory '/<>/tests/pysam_data' make[1]: *** [debian/rules:51: pysam_data.all] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:24: build-arch] Error 2 signature.asc Description: OpenPGP digital signature
Bug#947425: incron crashes in IncronTabEntry::GetSafePath due to use-after-free bug
Package: incron
Version: 0.5.12-1
Severity: grave
Tags: security patch upstream
Hi,
incron crashes for me frequently. As incron runs as root, but is controllable
by users, this bug might be security-relevant, so I'm reporting it a severity
grave and tagging it security. Please downgrade if you can rule out this
concern.
Further investigation shows that the problem is caused by the creation of new
directories within watched paths: these trigger a reload of the inotify watch
target, rendering the old watch structure invalid. Only after the reload,
potential commands are executed. This may require to get path of the event, but
the corresponding pointer is invalid after the reload.
Attached is a patch that extracts the path before the reload, making this
problem disappear for me. Note that the patch assumes that LOOPER is not
defined, which seems to be the case for the Debian package.
Backtrace for reference:
bt full
#0 0x004ba484 in IncronTabEntry::GetSafePath (rPath=) at /usr/include/c++/8/bits/basic_string.h:1046
i = 0
stream =
len = 1919509615
#1 0x004c43f3 in UserTable::OnEvent (this=, rEvt=...) at
inotify-cxx.h:428
px = 40
pW = 0x1fbde40
pE = 0x1fbc920
events = "IN_CREATE,IN_ISDIR"
cmd = "/home/user/autoscripts/imageresize.sh "
cs = "/home/user/autoscripts/imageresize.sh $@/$# $# $%"
pos = 39
oldpos = 0
len =
pid =
#2 0x004c4767 in EventDispatcher::ProcessEvents (this=) at
usertable.cpp:110
pIn = 0x1fc7d24
it = {first = 1702521203, second = 0x1fc0072}
i = 2
pipe = false
evt = {m_uMask = 1073742080, m_uCookie = 0, m_name = "Neuer Ordner",
m_pWatch = 0x1fbde40}
#3 0x004b8650 in main (argc=, argv=) at
icd-main.cpp:458
res =
wm = 10184
in = {m_fd = 6, m_watches = std::map with 2 elements = {[1] =
0xbfc8ab40, [2] = 0xbfc8ab68}, m_paths = std::map with 2 elements = {
["/etc/incron.d"] = 0xbfc8ab40, ["/var/spool/incron"] =
0xbfc8ab68}, m_buf = '\000' ..., m_events = std::deque
with 0 elements}
stw = {m_path = "/etc/incron.d", m_uMask = 10184, m_wd = 1, m_pInotify
= 0xbfc8ab90, m_fEnabled = true}
utw = {m_path = "/var/spool/incron", m_uMask = 10184, m_wd = 2,
m_pInotify = 0xbfc8ab90, m_fEnabled = true}
ed = {m_iPipeFd = 4, m_iMgmtFd = 6, m_pIn = 0xbfc8ab90, m_pSys =
0xbfc8ab40, m_pUser = 0xbfc8ab68, m_maps = std::map with 1 element = {[8] =
0x1fc7d20},
m_size = 3, m_pPoll = 0x1fbe080}
cfg = "/etc/incron.conf"
lckdir = "/var/run"
lckfile = "incrond"
app = {m_path = "/var/run/incrond.pid", m_fLocked = true}
ret = 0
sysBase = "/etc/incron.d"
userBase = "/var/spool/incron"
-- System Information:
Debian Release: 10.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 4.19.0-6-686-pae (SMP w/4 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8),
LANGUAGE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages incron depends on:
ii adduser 3.118
ii init-system-helpers 1.56+nmu1
ii libc62.28-10
ii libgcc1 1:8.3.0-6
ii libstdc++6 8.3.0-6
ii lsb-base 10.2019051400
incron recommends no packages.
incron suggests no packages.
-- Configuration Files:
/etc/incron.allow [Errno 13] Keine Berechtigung: '/etc/incron.allow'
/etc/incron.deny [Errno 13] Keine Berechtigung: '/etc/incron.deny'
-- no debconf information
diff --git a/usertable.cpp b/usertable.cpp
index 3f1ef4a..bdc7f29 100644
--- a/usertable.cpp
+++ b/usertable.cpp
@@ -370,6 +370,8 @@ void UserTable::OnEvent(InotifyEvent& rEvt)
{
InotifyWatch* pW = rEvt.GetWatch();
IncronTabEntry* pE = FindEntry(pW);
+
+ std::string pWPath = pW->GetPath();
// no entry found - this shouldn't occur
if (pE == NULL)
@@ -422,7 +424,7 @@ void UserTable::OnEvent(InotifyEvent& rEvt)
else {
cmd.append(cs.substr(oldpos, pos-oldpos));
if (cs[px] == '@') { // base path
- cmd.append(IncronTabEntry::GetSafePath(pW->GetPath()));
+ cmd.append(IncronTabEntry::GetSafePath(pWPath));
oldpos = pos + 2;
}
else if (cs[px] == '#') { // file name
Bug#947424: qtltools 1.2+dfsg-1 ftbfs on mipsel
Source: qtltools Version: 1.2+dfsg-1 Severity: serious Justification: ftbfs Tags: ftbfs sid bullseye Dear maintainer, Your last upload failed to build on mipsel. Your package is part of the htslib 1.10.2 transition, but I can't binNMU it on mipsel. Please have a look. Paul https://buildd.debian.org/status/package.php?p=qtltools (I am warned against a big log file, I am restricted in my bandwidth at the moment so I don't copy in the end of the log file). signature.asc Description: OpenPGP digital signature
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 947328 + unreproducible Bug #947328 [src:xca] FTBFS: dh_installman: mv debian/xca/usr/share/man/man1/xca.1.dh-new: No such file or directory Added tag(s) unreproducible. > End of message, stopping processing here. Please contact me if you need assistance. -- 947328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947328: FTBFS Not Reproducible in multiple build test envs (sbuild, pbuilder, etc.)
I ran this exact package through a rebuild in an sbuild environment just now, and cannot reproduce your FTBFS. Automated build(s) failed to reproduce this in a pbuilder environment as well. Did you do anything to the package to make it trigger this FTBFS? What Arch and Distro did you build against, in what environment? (Because this doesn't FTBFS from anything I can tell thus far.) Thomas
Bug#947423: kallisto ftbfs with htslib 1.10.2
Source: kallisto Version: 0.46.1+dfsg-1 Severity: serious Justification: ftbfs Tags: ftbfs sid bullseye Dear maintainer, Your package is part of the htslib 1.10.2 transition. I tried to binNMU your package but it fails to build from source. Please have a look. Paul https://buildd.debian.org/status/package.php?p=kallisto Tail of log for kallisto on amd64: 86 | } kstring_t; | ^ [ 66%] Building CXX object src/CMakeFiles/kallisto_core.dir/common.cpp.o cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -I/<>/src -I/usr/include/hdf5/serial -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -o CMakeFiles/kallisto_core.dir/common.cpp.o -c /<>/src/common.cpp [ 71%] Building CXX object src/CMakeFiles/kallisto_core.dir/h5utils.cpp.o cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -I/<>/src -I/usr/include/hdf5/serial -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -o CMakeFiles/kallisto_core.dir/h5utils.cpp.o -c /<>/src/h5utils.cpp make[3]: *** [src/CMakeFiles/kallisto_core.dir/build.make:209: src/CMakeFiles/kallisto_core.dir/ProcessReads.cpp.o] Error 1 make[3]: *** Waiting for unfinished jobs make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:131: src/CMakeFiles/kallisto_core.dir/all] Error 2 make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[1]: *** [Makefile:133: all] Error 2 make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu' dh_auto_build: cd obj-x86_64-linux-gnu && make -j4 "INSTALL=install --strip-program=true" returned exit code 2 make: *** [debian/rules:14: build-arch] Error 255 signature.asc Description: OpenPGP digital signature
Bug#947421: delly ftbfs with htslib 1.10.2
Source: delly Version: 0.8.1-2 Severity: serious Justification: ftbfs Tags: ftbfs sid bullseye Dear maintainer, Your package is part of the htslib 1.10.2 transition. I tried to binNMU your package but it fails to build from source. Please have a look. Paul https://buildd.debian.org/status/package.php?p=delly Tail of log for delly on amd64: | ~^ src/merge.h:330:24: warning: ignoring return value of ‘int bcf_hdr_set_samples(bcf_hdr_t*, const char*, int)’, declared with attribute warn_unused_result [-Wunused-result] 330 | bcf_hdr_set_samples(hdr[file_c], NULL, false); // Do not read the sample information | ~~~^~ In file included from src/delly.cpp:40: src/merge.h: In function ‘void torali::mergeBCFs(torali::MergeConfig&, const std::vector&)’: src/merge.h:592:16: warning: ignoring return value of ‘int bcf_hdr_write(htsFile*, bcf_hdr_t*)’, declared with attribute warn_unused_result [-Wunused-result] 592 | bcf_hdr_write(fp, hdr_out); | ~^ make[2]: *** [Makefile:61: src/delly] Error 1 make[2]: Leaving directory '/<>' dh_auto_build: make -j4 "INSTALL=install --strip-program=true" "BUILT_PROGRAMS=src/delly src/dpe" returned exit code 2 make[1]: *** [debian/rules:12: override_dh_auto_build] Error 255 make[1]: Leaving directory '/<>' make: *** [debian/rules:9: build-arch] Error 2 signature.asc Description: OpenPGP digital signature
Bug#936110: aff4: Python2 removal in sid/bullseye
On Fri, 30 Aug 2019 07:09:56 + Matthias Klose wrote: > Package: src:aff4 > Version: 0.24.post1-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 The python3 version of this package is in a new source, pyaff4. This source should be removed since it has no more rdepends now that rekall has been upgraded.. Filed as #947417. Scott K signature.asc Description: This is a digitally signed message part.
Processed: [bts-link] source package src:weevely
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:weevely > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #945723 (http://bugs.debian.org/945723) > # Bug title: weevely: Python2 removal in sid/bullseye > # * https://github.com/epinna/weevely3/issues/102 > # * remote status changed: open -> closed > # * closed upstream > tags 945723 + fixed-upstream Bug #945723 [src:weevely] weevely: Python2 removal in sid/bullseye Added tag(s) fixed-upstream. > usertags 945723 - status-open Usertags were: status-open. Usertags are now: . > usertags 945723 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 945723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945723 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: py2removal RC severity updates - 2019-12-26 17:37:05.950355+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 > # i3lock-fancy is an application, has low popcon (185 < 300), and has 0 > external rdeps or not in testing > severity 945652 serious Bug #945652 [src:i3lock-fancy] i3lock-fancy should stop listing python-tomahawk as alternative dependency Severity set to 'serious' from 'minor' > # pyconfigure is an application, has low popcon (19 < 300), and has 0 > external rdeps or not in testing > severity 945730 serious Bug #945730 [src:pyconfigure] pyconfigure: Please drop alternative recommends of python-setuptools Severity set to 'serious' from 'minor' > End of message, stopping processing here. Please contact me if you need assistance. -- 945652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945652 945730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945730 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:goldeneye
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:goldeneye > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #945648 (http://bugs.debian.org/945648) > # Bug title: goldeneye: Python2 removal in sid/bullseye > # * https://github.com/jseidl/GoldenEye/pull/25 > # * remote status changed: open -> closed > # * closed upstream > tags 945648 + fixed-upstream Bug #945648 [src:goldeneye] goldeneye: Python2 removal in sid/bullseye Added tag(s) fixed-upstream. > usertags 945648 - status-open Usertags were: status-open. Usertags are now: . > usertags 945648 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 945648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945683: marked as done (peony-extensions: Python2 removal in sid/bullseye)
Your message dated Thu, 26 Dec 2019 16:50:16 +
with message-id
and subject line Bug#945683: fixed in peony-extensions 1.1.4-1
has caused the Debian Bug report #945683,
regarding peony-extensions: 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.)
--
945683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945683
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: peony-extensions
Version: 1.1.3-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal
Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html
Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.
- Convert your Package to Python3. This is the preferred option. In
case you are providing a Python module foo, please consider dropping
the python-foo package, and only build a python3-foo package. Please
don't drop Python2 modules, which still have reverse dependencies,
just document them.
This is the preferred option.
- If the package is dead upstream, cannot be converted or maintained
in Debian, it should be removed from the distribution. If the
package still has reverse dependencies, raise the severity to
"serious" and document the reverse dependencies with the BTS affects
command. If the package has no reverse dependencies, confirm that
the package can be removed, reassign this issue to ftp.debian.org,
make sure that the bug priority is set to normal and retitle the
issue to "RM: PKG -- removal triggered by the Python2 removal".
- If the package has still many users (popcon >= 300), or is needed to
build another package which cannot be removed, document that by
adding the "py2keep" user tag (not replacing the py2remove tag),
using the debian-pyt...@lists.debian.org user. Also any
dependencies on an unversioned python package (python, python-dev)
must not be used, same with the python shebang. These have to be
replaced by python2/python2.7 dependencies and shebang.
This is the least preferred option.
If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: peony-extensions
Source-Version: 1.1.4-1
We believe that the bug you reported is fixed in the latest version of
peony-extensions, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 945...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
handsome_feng (supplier of updated
peony-extensions package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 26 Dec 2019 22:49:18 +0800
Source: peony-extensions
Architecture: source
Version: 1.1.4-1
Distribution: unstable
Urgency: medium
Maintainer: Kylin Team
Changed-By: handsome_feng
Closes: 945683
Changes:
peony-extensions (1.1.4-1) unstable; urgency=medium
.
* New upstream release. (Closes: #945683)
* Debian/control:
- Drop peony-admin.
* Debian/{compat,control}:
- Use debhelper-compat notation. Bump to DH compat level version 12.
Checksums-Sha1:
b4d364dfb0d25cc01c4ea8ab54cf8b0f2f2cf7c0 2730 peony-extensions_1.1.4-1.dsc
a8457b5fa2b26aa802cfc4e7b76fa9721eb21150 1950719
peony-extensions_1.1.4.orig.tar.gz
d520dfb4a1af524a47689578dd17add8048531ce 6888
peony-extensions_1.1.4-1.debian.tar.xz
82fb232f9567f903ba7173652dd21f12f12d257a 15503
peony-extensions_1.1.4-1_source.buildinfo
Checksums-Sha256:
80904b13c285e02d2f53d049dc0cf32559d40945752c08261ffb75f1160d2cea 2730
peony-extensions_1.1.4-1.dsc
f4a09626aefd874b175a59fc5bc9c4982b0a3fc1f85cbde71eadade7dc873dd8 1950719
peony-extensions_1.1.4.orig.tar.gz
Bug#937730: Bug#934264: Please update (4.6.2?) and provide/switch to python3
On Tue, Dec 24, 2019 at 10:07:02AM +0100, Andreas Tille wrote: > > python-envisage has not yet been converted to Python3 and seems to be > > required: > > $ mayavi2 > > Traceback (most recent call last): > > File "/usr/bin/mayavi2", line 464, in > > from mayavi.plugins.app import Mayavi, setup_logger > > File "/usr/lib/python3/dist-packages/mayavi/plugins/app.py", line 19, in > > > > from .mayavi_workbench_application import MayaviWorkbenchApplication > > File > > "/usr/lib/python3/dist-packages/mayavi/plugins/mayavi_workbench_application.py", > > line 13, in > > from envisage.ui.workbench.api import WorkbenchApplication > > ModuleNotFoundError: No module named 'envisage' > > That's recorded as TODO item in d/changelog now. FYI, I just worked on converting envisage to python3: https://salsa.debian.org/python-team/modules/python-envisage I asked Dmitry S. to upload it. Scott
Bug#937293: [Piuparts-devel] Bug#919170: Bug#919170: Please update dependency to python3-debianbts
On Thu, Dec 26, 2019 at 03:59:54PM +0100, Nis Martensen wrote: > > TypeError: mynext() takes 1 positional argument but 2 were given > > again, help very welcome! > A new merge request has the next set of fixups: > https://salsa.debian.org/debian/piuparts/merge_requests/17 many thanks, merged and deployed, now this is left: ceback (most recent call last): File "/srv/piuparts.debian.org/share/piuparts/piuparts-master-backend", line 433, in main() File "/srv/piuparts.debian.org/share/piuparts/piuparts-master-backend", line 425, in main while m.do_transaction(): File "/srv/piuparts.debian.org/share/piuparts/piuparts-master-backend", line 268, in do_transaction self._commands[command](command, args) File "/srv/piuparts.debian.org/share/piuparts/piuparts-master-backend", line 323, in _reserve self._init_db() File "/srv/piuparts.debian.org/share/piuparts/piuparts-master-backend", line 202, in _init_db self._load_package_database(self._section) File "/srv/piuparts.debian.org/share/piuparts/piuparts-master-backend", line 232, in _load_package_database config.get_arch())) File "/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/packagesdb.py", line 455, in load_alternate_versions_from_packages_urls pf2.load_packages_urls(urls) File "/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/packagesdb.py", line 183, in load_packages_urls self._read_file(stream, restrict_packages=restrict_packages) File "/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/packagesdb.py", line 190, in _read_file headers = rfc822_like_header_parse(input) File "/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/packagesdb.py", line 53, in rfc822_like_header_parse line = input.readline() File "/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/__init__.py", line 58, in readline empty = not self._refill() File "/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/__init__.py", line 49, in _refill chunk = chunk.decode() UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc3 in position 14159: unexpected end of data -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Bug#938618: marked as done (syslog-ng: Python2 removal in sid/bullseye)
Your message dated Thu, 26 Dec 2019 15:36:12 + with message-id and subject line Bug#938618: fixed in syslog-ng 3.25.1-1 has caused the Debian Bug report #938618, regarding syslog-ng: 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.) -- 938618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:syslog-ng Version: 3.19.1-6 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:syslog-ng 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: syslog-ng Source-Version: 3.25.1-1 We believe that the bug you reported is fixed in the latest version of syslog-ng, 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. Laszlo Boszormenyi (GCS) (supplier of updated syslog-ng 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, 21 Dec 2019 08:42:10 + Source: syslog-ng Architecture: source Version: 3.25.1-1 Distribution: unstable Urgency: medium Maintainer: syslog-ng maintainers Changed-By: Laszlo Boszormenyi (GCS) Closes: 924264 938618 Changes: syslog-ng (3.25.1-1) unstable; urgency=medium . * New upstream release. * Merge in syslog-ng-mod-journal (closes: #924264). * Remove syslog-ng-mod-geoip module. * Python3ify syslog-ng-mod-python (closes: #938618). * Add upstream persist-tool manpage. * Backport upstream bison update. * Install all SCL files. * Update configuration version. * Update self-tests. * Update Standards-Version to 4.4.1 . Checksums-Sha1: d31812ea7f87354d24d314aec0edc7409b8ba5fe 4391 syslog-ng_3.25.1-1.dsc 69911c90abba13cbe6d587976680623c2d69a4bd 1597239 syslog-ng_3.25.1.orig.tar.gz 72f29522bc027e14b06b28ad0559521a0f7a81c2 57088 syslog-ng_3.25.1-1.debian.tar.xz Checksums-Sha256:
Bug#947043: marked as done (cyrus-sasl2: CVE-2019-19906: Off-by-one in _sasl_add_string function)
Your message dated Thu, 26 Dec 2019 15:34:26 + with message-id and subject line Bug#947043: fixed in cyrus-sasl2 2.1.27+dfsg-2 has caused the Debian Bug report #947043, regarding cyrus-sasl2: CVE-2019-19906: Off-by-one in _sasl_add_string function 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.) -- 947043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cyrus-sasl2 Version: 2.1.27+dfsg-1 Severity: grave Tags: security upstream Forwarded: https://github.com/cyrusimap/cyrus-sasl/issues/587 Control: found -1 2.1.27~101-g0780600+dfsg-3 Hi, The following vulnerability was published for cyrus-sasl2. CVE-2019-19906[0]: Off by one in _sasl_add_string function If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-19906 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19906 [1] https://github.com/cyrusimap/cyrus-sasl/issues/587 Regards, Salvatore --- End Message --- --- Begin Message --- Source: cyrus-sasl2 Source-Version: 2.1.27+dfsg-2 We believe that the bug you reported is fixed in the latest version of cyrus-sasl2, 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. Roberto C. Sanchez (supplier of updated cyrus-sasl2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 26 Dec 2019 09:48:32 -0500 Source: cyrus-sasl2 Architecture: source Version: 2.1.27+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Cyrus Team Changed-By: Roberto C. Sanchez Closes: 947043 Changes: cyrus-sasl2 (2.1.27+dfsg-2) unstable; urgency=medium . [ Salvatore Bonaccorso ] * Off-by-one in _sasl_add_string function (CVE-2019-19906) (Closes: #947043) Checksums-Sha1: 7eded1a6b91f448e68da0731631a56d336cba9f7 3393 cyrus-sasl2_2.1.27+dfsg-2.dsc 7894a977b1e783c67167be32c53626ad35790544 99956 cyrus-sasl2_2.1.27+dfsg-2.debian.tar.xz 59466b10c2ec027f7efeb52a5a8e21456181d736 15254 cyrus-sasl2_2.1.27+dfsg-2_amd64.buildinfo Checksums-Sha256: e7e09491a1c2589c9947164db091d0f9b21b7d122f128841b6eac1adfc51b6c2 3393 cyrus-sasl2_2.1.27+dfsg-2.dsc ee894aeee645e842e39b434d5130e1bd15ea24b84c8a3f5077511a87341a 99956 cyrus-sasl2_2.1.27+dfsg-2.debian.tar.xz 7370bc46893f9fb0f0e0e0bd28a8196d02b3699ec78a7ae8b09f6889ac3dd17a 15254 cyrus-sasl2_2.1.27+dfsg-2_amd64.buildinfo Files: 330dae7ecb6168f4062d82c31a21e822 3393 libs standard cyrus-sasl2_2.1.27+dfsg-2.dsc 2bfce9f9e38b8b804b4390057f67833d 99956 libs standard cyrus-sasl2_2.1.27+dfsg-2.debian.tar.xz b97c48f54e5ac0f84c955f4ae33f217d 15254 libs standard cyrus-sasl2_2.1.27+dfsg-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEIYZ1DR4ae5UL01q7ldFmTdL1kUIFAl4EzbkACgkQldFmTdL1 kUJB/A//e4nEpB+rK3oENGSgb44ECqZEpwa9rN3fMPBbObDovfRNm3Q3eCeEahh/ k29Shl/f0bvWkHUdhz1tiaqSUPd6cvUh0idSPjg8dUZmcbb1yUe1nEOm5oHII4MX 63KbjEsLgiMXvZaNddkVxPtOpTqv/PxYNTLYGc31lNLwF9ooI3B1tduC5zs6XOgb qe2W15oj8v6ej5/inQOY3kZ6jh3MKVuRoBnKI4UnD0+F1+RlMnndiSqO+RSlbfWo jqpWdC56L/aYbrPjHzV5OF/vptNaPIM11YoHMAo1I5AP1uR5U0kNqhUkjxHil0yk cGWweZ2SfuCnJIIBSX22KCWlJUQDm3MCum7tBmAwogdf11Umj9mv9MnvyJ7zU3yy Xn3wsTrm+y5yPiaMZHSDrodiA1/mXB4HSPngnABPx1hgVq3bRT4K2g6gXhD1YAA5 O8K5MHyw/n4XNNHmh4YnSpv0JxaY4OwubRYY6cL2d8GKJa9Pssc1xopYWW3LOAZt FCCWkcGqDX/juRVxzRtWvfJMITU6AEVs3mhbdxsZV30/XyFPBSTxlpfbbt9KtTjQ 2/EwXYUJh6mlSw2nuGa0/vJupi/EyeZVC1y9zFu2BA5rC/VSZQveXpRw1XvzK5pr P0xNsFPcm4ERyxJ88kEwGTZtC3Lj5c9XzYOf1ouCxM2ZygYzOKI= =up/F -END PGP SIGNATURE End Message ---
Bug#947043: cyrus-sasl2: CVE-2019-19906: Off by one in _sasl_add_string function
On Fri, Dec 20, 2019 at 10:24:20PM +0100, Salvatore Bonaccorso wrote: > > And released as DSA 4591-1. Note: The patch was not upstream commited > at point of writing this. And I see Mike did as well release for LTS. > I saw that Mike did updates for jessie (LTS) and wheezy (ELTS). > > > unstable would need an update as well yet. > > > > > Of course. > > Ideally this happen soon, but the RC bug is enough to mark the > 'stable' -> 'testing' regression. Just let me know if any of you can > do it or if you would prefer a NMU with same patch (both approaches > works for me). > I have made an upload to unstable of version 2.1.27+dfsg-2 with the patch that fixes the CVE. > > > Can you later import then the changes in the packaging repository in > > > the appropriate branches? > > > > > I could manage that in the coming days. Unless Ondrej or someone else > > gets to it first. > > Thanks! > As a summary, here is the state of cyrus-sasl2 in the various release and the associated Git branches in Salsa: sid: up to date on master branch, Debian version 2.1.27+dfsg-2 has been uploaded bullseye: waiting on transition of package from sid, no associated branch in Salsa buster: new branch, master-buster*, contains new commit representing Debian version 2.1.27+dfsg-1+deb10u1 stretch: new branch, master-stretch*, contains two (2) new commits representing Debian versions 2.1.27~101-g0780600+dfsg-3 (NMU in 2017 which as not recorded follwing 2.1.27~101-g0780600+dfsg-2) and Debian version 2.1.27~101-g0780600+dfsg-3+deb9u1 with the patch for this CVE jessie: history has diverged; there is already an old commit and tag for Debian version 2.1.26.dfsg1-13+deb8u2 from 2016 which collides with Mike's recent 2.1.26.dfsg1-13+deb8u2 jessie update, so I have not done anything with this wheezy: up to date on existing master-wheezy branch based on Mike's 2.1.25.dfsg1-6+deb7u2 ELTS updates * As far as the new master-buster and master-stretch branches, I only made those branches to record the changes which have already been uploaded. In particular, I did not update debian/gbp.conf to note the new branch names; such a change will be required if we decide to make further revisions along either of the new branches and then build from the Git repository. I have pushed tags for each of the above versions as well (except the jessie version, as noted). I include all of this information so that the cyrus-sasl2 in particular is made aware of all the changes I have pushed. Regards, -Roberto -- Roberto C. Sánchez
Bug#945681: gvb: diff for NMU version 1.4-1.1
Dear Adrian, thank you, I really appreciate. I was planning to fix that packaging mistake, but as you might have noticed, I have really slow reactions lately - and then, I still need to go through a sponsor. So if you prefer, feel free to re-upload the package without delay. Pietro Il giorno gio, 26/12/2019 alle 15.04 +0200, Adrian Bunk ha scritto: > Control: tags 945681 + patch > Control: tags 945681 + pending > > Dear maintainer, > > I've prepared an NMU for gvb (versioned as 1.4-1.1) and uploaded it > to DELAYED/14. Please feel free to tell me if I should cancel it. > > cu > Adrian
Bug#937269: peframe: Python2 removal in sid/bullseye
Just an update: Python 3 compatibility is indeed introduced in the latest upstream version, however, that version also adds some new dependencies that would need to be packaged and pass NEW. For example, python-virustotal-api, which has been in NEW for quite some time. I have also looked at adding python-oletools, but that will also need new dependencies of its own. I’ll try work on this eventually, unless someone else is interested and has some spare time. Sascha
Bug#937293: [Piuparts-devel] Bug#919170: Bug#919170: Please update dependency to python3-debianbts
> TypeError: mynext() takes 1 positional argument but 2 were given > > again, help very welcome! A new merge request has the next set of fixups: https://salsa.debian.org/debian/piuparts/merge_requests/17
Bug#937082: marked as done (mopidy-tunein: Python2 removal in sid/bullseye)
Your message dated Thu, 26 Dec 2019 14:49:32 + with message-id and subject line Bug#937082: fixed in mopidy-tunein 1.0.0-1 has caused the Debian Bug report #937082, regarding mopidy-tunein: 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.) -- 937082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937082 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mopidy-tunein Version: 0.4.1-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:mopidy-tunein 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: mopidy-tunein Source-Version: 1.0.0-1 We believe that the bug you reported is fixed in the latest version of mopidy-tunein, 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. Stein Magnus Jodal (supplier of updated mopidy-tunein package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 26 Dec 2019 15:34:23 +0100 Source: mopidy-tunein Architecture: source Version: 1.0.0-1 Distribution: unstable Urgency: medium Maintainer: Stein Magnus Jodal Changed-By: Stein Magnus Jodal Closes: 937082 Changes: mopidy-tunein (1.0.0-1) unstable; urgency=medium . * New upstream release * Switch from Python 2 to 3 (Closes: #937082) * Bump debhelper from 10 to 12 * Disable tests because of pkg_resurces usage * d/control: Bump Standards-Version to 4.4.1, no changes * d/control: Require mopidy >= 3 * d/control: Update Description * d/copyright: Update copyright years * d/copyright: Use HTTPS for the copyright spec * d/rules: Install changelog Checksums-Sha1: 5d4160a28bc62df7e22d365b53923e3209313211 2240 mopidy-tunein_1.0.0-1.dsc a460a24f1a5c8d335c174b892f6ccf0d4422ad38 16473 mopidy-tunein_1.0.0.orig.tar.gz a31accc3d203638dfb80e6a484d5b92c7eab4b42 488 mopidy-tunein_1.0.0.orig.tar.gz.asc
Bug#937081: marked as done (mopidy-soundcloud: Python2 removal in sid/bullseye)
Your message dated Thu, 26 Dec 2019 14:39:54 + with message-id and subject line Bug#937081: fixed in mopidy-soundcloud 3.0.0-1 has caused the Debian Bug report #937081, regarding mopidy-soundcloud: 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.) -- 937081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mopidy-soundcloud Version: 2.1.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:mopidy-soundcloud 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: mopidy-soundcloud Source-Version: 3.0.0-1 We believe that the bug you reported is fixed in the latest version of mopidy-soundcloud, 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. Stein Magnus Jodal (supplier of updated mopidy-soundcloud package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 26 Dec 2019 14:58:13 +0100 Source: mopidy-soundcloud Architecture: source Version: 3.0.0-1 Distribution: unstable Urgency: medium Maintainer: Stein Magnus Jodal Changed-By: Stein Magnus Jodal Closes: 937081 Changes: mopidy-soundcloud (3.0.0-1) unstable; urgency=medium . * New upstream release * Switch from Python 2 to 3 (Closes: #937081) * Bump debhelper from 10 to 12 * d/control: Bump Standards-Version to 4.4.1, no changes * d/control: Require mopidy >= 3 * d/control: Update Description * d/copyright: Update copyright years * d/copyright: Use HTTPS for the copyright spec * d/rules: Install changelog Checksums-Sha1: 35f486167e28033a979e2042fb72d46eedb7f7ff 2021 mopidy-soundcloud_3.0.0-1.dsc d361e0cc8b623255b1225a2ebe01bb7a55368c3e 60089 mopidy-soundcloud_3.0.0.orig.tar.gz a1c35baadeae0cf712037fff3d6caf9f64a35ceb 3156
Bug#936932: libvigraimpex: Python2 removal in sid/bullseye
Control: block -1 by 947365 On 2019-12-23 Andreas Metzler wrote: [...] > I will do a QA upload. I have opened a request for a transition slot. cu Andreas signature.asc Description: PGP signature
Processed: Re: Bug#936932: libvigraimpex: Python2 removal in sid/bullseye
Processing control commands:
> block -1 by 947365
Bug #936932 {Done: Andreas Metzler } [src:libvigraimpex]
libvigraimpex: Python2 removal in sid/bullseye
936932 was blocked by: 945659
936932 was blocking: 936227 937156 937695 937960 938114
Added blocking bug(s) of 936932: 947365
--
936932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#939401: nvidia-driver: Xorg crashing in an endless loop after upgrade to version 430
On Thu, 21 Nov 2019 at 15:30, Andreas Beckmann wrote: > > Hi Luca, > > On Sun, 08 Sep 2019 11:50:28 +0100 Luca Boccassi wrote: > > Ok scratch that, I can reproduce - it's because of the non-glvnd > > libraries. With the glvnd one there's no issue, and that's why 435 > > works - non-glvnd was removed. > > Can you check 430.64-1? If that still does not work, I'll remove the > non-glvnd binaries like in 435. And with the RC bugs gone, I might do a > buster-backports upload as well. > > Could you also verify that the latest 418.xx releases still do work in > non-glvnd mode? > > https://people.debian.org/~anbe/418.113/amd64/ > > That's the latest 418.xx upstream release. (branch 418) > > https://people.debian.org/~anbe/418.87.01/amd64/ > > That's the latest tesla driver release packaged as a regular 418.xx > release (i.e. without any "*-tesla-*" package renaming that may still > have some bugs in corner cases) (branch 418-tesla) > > > Andreas Hi, Sorry, didn't have time till now. I've done some work to make bumblebee+primus viable with either glvnd or non-glvnd (for the legacy drivers), based on a suggestion from Felipe. See: https://github.com/Bumblebee-Project/Bumblebee/pull/1050 https://salsa.debian.org/nvidia-team/bumblebee/merge_requests/2 There are many ways to approach this, I picked the separate package with a different config file and a systemd drop-in to use it. I don't particularly mind which solution we choose and have time over the holidays to do some more work and testing if required. Thanks! Kind regards, Luca Boccassi
Bug#946563: there is no need for a versioned libxcrypt1-dev package
On 2019-12-11 Marco d'Itri wrote: > On Dec 11, Matthias Klose wrote: > > there is really no need for a versioned libxcrypt1-dev package. > > Please rename that properly to libxcrypt-dev. > Can you be more specific in why this would not be allowed? > Currently I am not building libxcrypt2 and libxcrypt2-dev, but the > package is ready to do it. > libxcrypt1-dev and libxcrypt2-dev cannot be installed at the same time, > but libxcrypt1 and libxcrypt2 can. Hello Marco, Imho the major point is that dev packages should not be versioned to allow migrating from 1 to 2 (at some point) without having to change all rdep source packages. Debian usually tries to avoid shipping multiple versions of a shared library in a release. Are libxcrypt[12]-dev API compatible in some way? cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org: > reassign 912495 src:pydxcluster Bug #912495 [pydxcluster] pydxcluster: Please migrate to python3-pygame Bug reassigned from package 'pydxcluster' to 'src:pydxcluster'. Ignoring request to alter found versions of bug #912495 to the same values previously set Ignoring request to alter fixed versions of bug #912495 to the same values previously set > forcemerge 945731 912495 Bug #945731 [src:pydxcluster] pydxcluster: Python2 removal in sid/bullseye Bug #945731 [src:pydxcluster] pydxcluster: Python2 removal in sid/bullseye Added tag(s) patch and pending. Bug #912495 [src:pydxcluster] pydxcluster: Please migrate to python3-pygame Severity set to 'serious' from 'wishlist' 937441 was blocked by: 945671 912487 937621 945731 936550 936513 945699 938509 936577 943075 945632 937330 938497 938592 937743 937726 936148 936298 938488 937553 937492 943027 936559 937431 936978 938328 936945 937441 was blocking: 937695 937960 938168 938528 Added blocking bug(s) of 937441: 912495 938355 was blocked by: 936988 938270 937562 938307 936712 937725 938008 938181 938261 937074 936806 936950 938348 936775 938408 936954 938358 937850 937593 937383 938438 936188 942936 937080 938231 938877 938226 937619 937778 937714 936498 937072 937339 936235 937069 937421 936450 937618 938611 936282 936968 937082 937788 938528 937330 937081 942920 938141 937617 936120 945731 937078 937648 937071 937444 936214 938227 937300 938355 was blocking: 936289 937499 937638 937672 937695 937826 938168 938183 938244 Added blocking bug(s) of 938355: 912495 938198 was blocked by: 943287 938507 937498 937236 943143 937440 938174 946928 937569 937145 938735 937606 937044 937170 938513 936629 938036 938859 936790 936546 938327 937525 943120 938680 938458 938568 937291 938081 936669 945732 943169 938846 937033 937099 943243 947232 934870 936173 936995 938775 937433 938451 938351 936467 943123 936723 936343 937675 937695 934852 937290 938731 937657 945731 943161 938795 938198 was blocking: 937695 Added blocking bug(s) of 938198: 912495 938278 was blocked by: 945731 938278 was blocking: 937156 937665 937695 938168 Added blocking bug(s) of 938278: 912495 937695 was blocked by: 938754 942966 937498 937290 936870 936788 937459 937485 938795 937711 936266 943207 942972 937260 937400 937468 936938 938272 937552 937114 936765 942996 937914 936951 938375 936247 937425 937453 937892 936728 939109 936385 945743 942982 937068 937000 937157 936820 943193 936398 936282 938359 943124 936652 937241 936805 938385 943046 937053 937025 945646 938300 936880 938222 939103 943163 936325 938006 937826 937085 945667 937475 938353 943067 937059 936717 936778 883145 943184 936222 936485 937266 937406 937788 936862 938498 942990 943061 938290 936459 945661 943033 938862 936498 938459 937870 945736 938485 938711 938400 938260 937138 936892 938468 942960 943091 937728 936914 938114 938604 943039 937247 936425 936876 945639 937296 937151 936114 938425 936208 936468 938892 937938 938306 936886 937398 938068 936957 937504 938157 936241 942941 938241 937385 938053 937717 938702 937300 937778 943201 938098 937222 937006 938826 936702 938059 937880 945640 943040 937029 936809 938389 937473 937083 936508 938171 936560 938355 937064 938394 937572 936323 938560 938682 937187 937596 938809 937547 938252 936774 938383 936803 937023 937055 938329 937089 937927 938850 937479 936329 937737 943195 936850 938622 938774 945745 937094 938364 938803 938590 937079 936758 937489 945716 938799 938373 938763 936921 943232 937455 937423 938731 937494 938784 938921 936731 938666 938758 936799 938793 938541 937483 937942 937073 936981 938181 934870 936724 936672 937429 935450 938769 938379 937118 937177 938672 937660 936769 947027 936793 938647 936934 937204 936181 938696 938724 936187 936596 938029 938641 937389 938473 938856 938083 937171 936572 937323 936473 937508 938572 937971 937560 926244 937682 938596 937809 936641 937252 937383 938055 937329 936737 936566 937850 936127 938479 938737 936927 937622 938127 938094 937803 937364 936690 938489 936522 946929 943102 938455 943244 938423 937784 938522 936455 937666 938690 937758 936489 938483 937541 937793 938073 945710 936464 937181 936608 936118 936177 936660 937769 937379 938608 936977 937672 936918 938177 945635 938660 943035 936483 936942 937647 938204 933775 938464 938582 937696 937724 946849 936428 936919 943034 938465 937135 937725 936465 937286 937768 943081 937700 937378 937317 936119 936609 937841 938428 938220 937785 936913 934852 936454 936706 937411 937759 938280 938488 942980 943021 938650 946928 936495 936113 938706 937890 937503 938095 945732 937011 938866 937550 938054 936866 938270 937402 942970 937262 938478 937328 938065 938847 938311 937808 937860 936556 936872 937388 945671 938556 936847 937276 936311 945642 936768 936700 936317 936841 937609 937119 943042 945677 936935 937465 943018 938753 938656 942986 936725 936753 938378 938700 937302
Bug#945730: pyconfigure: Python2 removal in sid/bullseye
Control: retitle -1 pyconfigure: Please drop alternative recommends of python-setuptools Control: unblock 938168 by -1 Control: severity -1 minor On Wed, Nov 27, 2019 at 11:58:52PM +, Sandro Tosi wrote: > Source: pyconfigure > Version: 0.2.3-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 (the specific reason can be found searching this > source package in > https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ). >... pyconfigure 0.2.3-2 ['(binary:pyconfigure)Recommends->python-setuptools'] Recommends: python3-setuptools | python-setuptools As alternative that is not the first alternative this is not a problem for the Python 2 removal. cu Adrian
Processed: Re: Bug#945730: pyconfigure: Python2 removal in sid/bullseye
Processing control commands: > retitle -1 pyconfigure: Please drop alternative recommends of > python-setuptools Bug #945730 [src:pyconfigure] pyconfigure: Python2 removal in sid/bullseye Changed Bug title to 'pyconfigure: Please drop alternative recommends of python-setuptools' from 'pyconfigure: Python2 removal in sid/bullseye'. > unblock 938168 by -1 Bug #938168 [src:python-setuptools] python-setuptools: Python2 removal in sid/bullseye 938168 was blocked by: 936570 945691 936293 938222 938711 937144 936525 938156 936561 937465 937267 937501 937547 937700 938340 938814 943801 93 937421 938694 936975 937413 936731 936742 937167 938259 938400 937860 936485 936526 938809 938212 938713 938351 936528 937069 937757 938155 937066 937244 937011 937831 947297 937581 936800 937658 936529 938808 937503 938256 938084 938470 938418 937533 937312 938070 937911 936797 938227 937627 937847 938416 937968 936819 938061 937883 938461 937140 936816 938690 936985 938019 937356 937726 937969 936818 937715 936870 938810 937153 937290 938653 936701 936649 938463 937162 937803 936282 943068 937617 937719 937897 938004 938015 936420 938428 937730 937253 937592 937718 936804 936815 937770 937571 937784 935657 937725 942996 942945 938029 936914 938367 936988 937560 938394 937240 937952 936789 937809 938871 938069 938757 938469 936643 938167 938734 937644 938068 937961 938503 936714 937256 937885 937925 938244 938011 943217 937806 937768 937480 937074 938622 937080 937539 937156 937576 936821 936709 943052 936433 937889 942943 937711 936997 937538 938013 937694 937255 937457 937667 936473 937769 937904 937536 937159 936724 938700 938065 937926 938294 937888 937814 937404 936973 937835 938864 937428 936569 936196 943256 936779 937463 937585 938719 937508 938716 937429 936739 938560 936637 936246 938718 936566 937640 937875 936710 936523 938355 936511 938729 937836 937461 937514 937061 934870 937838 937070 938251 937586 937425 936332 938704 938715 936720 937117 936521 938358 938153 938290 934852 936775 938573 938763 938542 937419 936242 936743 938759 937100 938545 938094 937621 936335 938712 943270 936273 937665 936772 943284 936605 938315 938680 936995 938111 937422 938328 943104 938674 942906 938363 937502 938756 938546 936793 943017 938211 938044 937891 938444 938223 937843 936999 938268 937554 937611 937456 936606 942986 936996 936339 943229 939111 937412 937850 937832 937012 937577 937157 938755 937959 936498 936309 937323 937252 937230 938661 943055 938051 937593 937427 936678 938845 936181 938300 936610 938625 937129 935212 938684 937507 937740 937751 937170 936495 937550 937184 943012 938727 936544 936448 937116 938040 936702 937263 938380 938848 938374 942978 936147 936305 936388 937587 937119 937837 937417 938053 938663 938180 938554 938611 935358 937548 936114 936188 938887 936450 936660 937444 938058 938458 937330 936189 937318 938412 938850 936206 938157 937269 937600 938059 938794 937962 937213 936289 937634 937598 947298 937596 937759 938100 936124 937657 937329 937265 937467 938621 947296 938234 942992 938807 937168 936214 937599 937326 936954 937304 937166 938022 936527 937680 937758 938365 938116 938229 936799 943165 936235 938184 938751 938532 937727 938125 936110 938877 937849 943223 938204 937895 937663 938130 938790 936275 937053 938152 937848 947302 938543 936745 938263 936179 938226 937615 936120 937717 936392 938366 936972 936683 937619 936749 938753 936279 938219 937899 938216 937845 937300 937625 937618 938261 938541 937684 937051 938270 937451 937944 938427 938369 936522 937616 936950 938027 938301 936180 938188 938671 937609 943049 938209 938450 937271 938032 943046 936577 937998 936767 938043 939109 937606 938087 937945 937339 938285 938487 938289 936665 938124 937562 938108 937787 937867 943045 937894 938441 938407 938041 937551 937605 937614 937688 938054 937448 938697 936161 938556 936170 937389 936751 938437 937446 938235 938558 938373 938178 937544 936125 936215 938220 937049 937386 938275 936790 938559 937675 937314 937620 938683 937498 937851 938392 93 936311 938555 937445 938236 936219 937638 938360 937678 937610 936956 937181 936216 938402 938276 937385 937499 938239 938002 936270 937639 937737 938522 937890 938331 936427 938278 943002 937673 943239 936596 936329 938689 936712 937364 937822 937642 938131 936169 938273 938688 938233 938171 936304 936123 936328 937527 937286 938375 937937 936111 936680 938686 943236 936599 937441 936326 937288 937209 938271 937660 937432 936266 936444 936268 938379 942957 937902 938336 938707 938540 937692 937383 936319 937443 938376 936962 936113 938685 938378 937072 942974 936269 938310 936325 938231 937236 936462 938567 938283 937392 937238 938498 942929 937827 938737 938676 943106 937331 937210 937932 938164 937950 938306 938862 938181 937402 937276 937437 938046 937817 938095 937681 937993 937558 937664 937941 937907 938448 937176 943043 938702 937559 937796 936994 938183 938388 937082
Processed: tagging 945728
Processing commands for cont...@bugs.debian.org: > tags 945728 + fixed-upstream Bug #945728 [src:zypper] zypper: Python2 removal in sid/bullseye Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 945728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945728 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#933348: marked as done (mopidy-scrobbler: depends on removed package)
Your message dated Thu, 26 Dec 2019 13:35:19 + with message-id and subject line Bug#933348: fixed in mopidy-scrobbler 2.0.0-1 has caused the Debian Bug report #933348, regarding mopidy-scrobbler: depends on removed package 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.) -- 933348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mopidy-scrobbler Version: 1.2.1-1 Severity: serious Hello, your package depends on python-pylast package, that has been removed from unstable. Please port to python3, or ask to reintroduce it. G. --- End Message --- --- Begin Message --- Source: mopidy-scrobbler Source-Version: 2.0.0-1 We believe that the bug you reported is fixed in the latest version of mopidy-scrobbler, 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 933...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stein Magnus Jodal (supplier of updated mopidy-scrobbler package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 26 Dec 2019 12:08:32 +0100 Source: mopidy-scrobbler Architecture: source Version: 2.0.0-1 Distribution: unstable Urgency: medium Maintainer: Stein Magnus Jodal Changed-By: Stein Magnus Jodal Closes: 933348 937079 Changes: mopidy-scrobbler (2.0.0-1) unstable; urgency=medium . * New upstream release * Switch from Python 2 to 3 (Closes: #937079, #933348) * Disable tests because of pkg_resurces usage * Bump debhelper from 9 to 12 * d/clean: Remove custom clean rules * d/control: Bump Standards-Version to 4.4.1, no changes * d/control: Require mopidy >= 3 * d/control: Update Description * d/control: Update Homepage * d/copyright: Update copyright years * d/copyright: Use HTTPS for the copyright spec * d/rules: Install changelog Checksums-Sha1: 3b64e302dcefd93f8ce0c41c452d04eb9d2a99f8 2002 mopidy-scrobbler_2.0.0-1.dsc 1a8ce1f3c88a11e38e43c0c56eac11472457e068 10149 mopidy-scrobbler_2.0.0.orig.tar.gz b811b09e2f572e5c778c9f8f28b63f789b8c3405 2584 mopidy-scrobbler_2.0.0-1.debian.tar.xz Checksums-Sha256: 43df16cef4b39f9e6eb7936c7915a45513fac1c7584b3cedc8f4224107fa9a1e 2002 mopidy-scrobbler_2.0.0-1.dsc 2411e92303cd5950f5a24ef476638bffc066b43f79e7422b3727b7e120e91d69 10149 mopidy-scrobbler_2.0.0.orig.tar.gz 727aa243c2c57c410d9173f5b93ae06f127d4cfcf26f647ddf5f321677fba6ee 2584 mopidy-scrobbler_2.0.0-1.debian.tar.xz Files: e30f99a5f0cd65b38e38c1336014a675 2002 sound optional mopidy-scrobbler_2.0.0-1.dsc 252f45a329215c4d7b0e2db3fe54dade 10149 sound optional mopidy-scrobbler_2.0.0.orig.tar.gz 29f9b65d535221cd865724ac01efe88a 2584 sound optional mopidy-scrobbler_2.0.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEgKr0kHY4JR8IscpGILTH9aF8WPYFAl4EsT8RHGpvZGFsQGRl Ymlhbi5vcmcACgkQILTH9aF8WPYOWQ/7B3/S5yyjVBZscSghXFIsd335NEV6rrXj +fb2YkEgmKbJb6+2Ip3Rytp39u2j125GnYAQuoe4IxNC2EuNUhziJAXsLDki6Ocx 1gtyzXpo4NmRO5G2cIDbKjc7S1zrSqepCaJWHV8ysck1L2RR983J9bueFWfTdyFR g2kjHLesEdic0hsZUOIVtTa+hDG7Axr6cENmBXEJXpeGG2FKnndOcFIwxyBF39bI BuJDMfDqbDxoiAewbC5PG+8ud5SBxxXBqq8dqC/h2ouYdXub7LtGc9qDVtJ/ycfw 40SOZBxYBmE8YlqRGygvucDV+LlrEgNW9ujHTZxziRDuE5JVnUUB9ktwfKzomr/H Tr0NV2qXNyz5SADV6SWWpzeRmJDgDaSZETUBJzVVdAlpPaRrtJyEp1UyeVmRLMpd mfW2iX2BtCOlAoeNHN6dYGL4VCiBV+uFZ3/NqcXcHNN07dHJ7ajqCE/6iTruDg3C WeScfjkWwFooW5/1Ohmxkc+bcMumHOfgztTH+2K5ZubduVtN5nGgDTEPV93G0mxl +8RuBvi5C1yyphdelTnnJlPenlVguuhf5r0HCNwh2NIEqaLGJjyQeRrsugwfkJlP HyqlXkCjWbyNqTBYNbwD6IYnih5L8qx/YX42BBGOjzfjgzkIaYVJjiWmYVG9eEHu tkGJLNuA/Ao= =g7HZ -END PGP SIGNATURE End Message ---
Bug#937079: marked as done (mopidy-scrobbler: Python2 removal in sid/bullseye)
Your message dated Thu, 26 Dec 2019 13:35:20 + with message-id and subject line Bug#937079: fixed in mopidy-scrobbler 2.0.0-1 has caused the Debian Bug report #937079, regarding mopidy-scrobbler: 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.) -- 937079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mopidy-scrobbler Version: 1.2.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:mopidy-scrobbler 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: mopidy-scrobbler Source-Version: 2.0.0-1 We believe that the bug you reported is fixed in the latest version of mopidy-scrobbler, 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. Stein Magnus Jodal (supplier of updated mopidy-scrobbler package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 26 Dec 2019 12:08:32 +0100 Source: mopidy-scrobbler Architecture: source Version: 2.0.0-1 Distribution: unstable Urgency: medium Maintainer: Stein Magnus Jodal Changed-By: Stein Magnus Jodal Closes: 933348 937079 Changes: mopidy-scrobbler (2.0.0-1) unstable; urgency=medium . * New upstream release * Switch from Python 2 to 3 (Closes: #937079, #933348) * Disable tests because of pkg_resurces usage * Bump debhelper from 9 to 12 * d/clean: Remove custom clean rules * d/control: Bump Standards-Version to 4.4.1, no changes * d/control: Require mopidy >= 3 * d/control: Update Description * d/control: Update Homepage * d/copyright: Update copyright years * d/copyright: Use HTTPS for the copyright spec * d/rules: Install changelog Checksums-Sha1: 3b64e302dcefd93f8ce0c41c452d04eb9d2a99f8 2002 mopidy-scrobbler_2.0.0-1.dsc 1a8ce1f3c88a11e38e43c0c56eac11472457e068
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org: > reassign 942777 src:nitroshare Bug #942777 [nitroshare-nautilus] nitroshare-nautilus: Please port to python3-nautlius Bug reassigned from package 'nitroshare-nautilus' to 'src:nitroshare'. No longer marked as found in versions nitroshare/0.3.3-1.1. Ignoring request to alter fixed versions of bug #942777 to the same values previously set > forcemerge 945712 942777 Bug #945712 [src:nitroshare] nitroshare: Python2 removal in sid/bullseye Bug #942777 [src:nitroshare] nitroshare-nautilus: Please port to python3-nautlius Severity set to 'serious' from 'important' 937628 was blocked by: 936266 945718 938614 945712 945683 945674 942914 945863 936265 937628 was blocking: 937448 937569 937695 943104 945674 Added blocking bug(s) of 937628: 942777 945863 was blocked by: 936266 942914 945718 936265 945674 945712 945683 945863 was blocking: 937448 937569 937628 937695 945674 Added blocking bug(s) of 945863: 942777 Marked as found in versions nitroshare/0.3.3-1.1. Added tag(s) sid and bullseye. Merged 942777 945712 > affects 945712 nitroshare-nautilus Bug #945712 [src:nitroshare] nitroshare: Python2 removal in sid/bullseye Bug #942777 [src:nitroshare] nitroshare-nautilus: Please port to python3-nautlius Added indication that 945712 affects nitroshare-nautilus Added indication that 942777 affects nitroshare-nautilus > thanks Stopping processing here. Please contact me if you need assistance. -- 937628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937628 942777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942777 945712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945712 945863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 917840 is serious
Processing commands for cont...@bugs.debian.org: > severity 917840 serious Bug #917840 [nitroshare-nautilus] nitroshare-nautilus expansion not working because of unmet python2 dependency Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 917840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: gvb: diff for NMU version 1.4-1.1
Processing control commands: > tags 945681 + patch Bug #945681 [src:gvb] gvb: Python2 removal in sid/bullseye Added tag(s) patch. > tags 945681 + pending Bug #945681 [src:gvb] gvb: Python2 removal in sid/bullseye Added tag(s) pending. -- 945681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945681: gvb: diff for NMU version 1.4-1.1
Control: tags 945681 + patch
Control: tags 945681 + pending
Dear maintainer,
I've prepared an NMU for gvb (versioned as 1.4-1.1) and uploaded it
to DELAYED/14. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru gvb-1.4/debian/changelog gvb-1.4/debian/changelog
--- gvb-1.4/debian/changelog 2014-10-26 23:28:48.0 +0200
+++ gvb-1.4/debian/changelog 2019-12-26 15:00:50.0 +0200
@@ -1,3 +1,10 @@
+gvb (1.4-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Correct dependency from python-gi to python3-gi. (Closes: #945681)
+
+ -- Adrian Bunk Thu, 26 Dec 2019 15:00:50 +0200
+
gvb (1.4-1) unstable; urgency=medium
* Imported Upstream version 1.4
diff -Nru gvb-1.4/debian/control gvb-1.4/debian/control
--- gvb-1.4/debian/control 2014-10-26 23:42:32.0 +0200
+++ gvb-1.4/debian/control 2019-12-26 15:00:48.0 +0200
@@ -11,7 +11,7 @@
Package: gvb
Architecture: all
-Depends: ${misc:Depends}, ${python3:Depends}, python3-scipy, python-gi, python3-gi-cairo
+Depends: ${misc:Depends}, ${python3:Depends}, python3-scipy, python3-gi, python3-gi-cairo
Suggests: libav-tools
Description: visual simulator of 1 and 2-dimensional vibrations
Good ViBrations (gvb) is a small program that aims at providing a nice
Processed: tagging 945673
Processing commands for cont...@bugs.debian.org: > tags 945673 + fixed-upstream Bug #945673 [src:fvwm-crystal] fvwm-crystal: Python2 removal in sid/bullseye Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 945673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#945652: i3lock-fancy: Python2 removal in sid/bullseye
Processing control commands: > retitle -1 i3lock-fancy should stop listing python-tomahawk as alternative > dependency Bug #945652 [src:i3lock-fancy] i3lock-fancy: Python2 removal in sid/bullseye Changed Bug title to 'i3lock-fancy should stop listing python-tomahawk as alternative dependency' from 'i3lock-fancy: Python2 removal in sid/bullseye'. > unblock 938676 by -1 Bug #938676 [src:tomahawk] tomahawk: Python2 removal in sid/bullseye 938676 was blocked by: 945652 938676 was blocking: 937275 937558 937665 937695 937762 938168 938492 Removed blocking bug(s) of 938676: 945652 > severity -1 minor Bug #945652 [src:i3lock-fancy] i3lock-fancy should stop listing python-tomahawk as alternative dependency Severity set to 'minor' from 'serious' -- 938676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938676 945652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945652 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 945663
Processing commands for cont...@bugs.debian.org: > tags 945663 + fixed-upstream Bug #945663 [src:drbdlinks] drbdlinks: Python2 removal in sid/bullseye Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 945663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945652: i3lock-fancy: Python2 removal in sid/bullseye
Control: retitle -1 i3lock-fancy should stop listing python-tomahawk as alternative dependency Control: unblock 938676 by -1 Control: severity -1 minor On Wed, Nov 27, 2019 at 11:58:49PM +, Sandro Tosi wrote: > Source: i3lock-fancy > Version: 0.0~git20160228.0.0fcb933-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 (the specific reason can be found searching this > source package in > https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ). >... i3lock-fancy 0.0~git20160228.0.0fcb933-2 ['(binary:i3lock-fancy)Depends->python-tomahawk'] Depends: i3lock, imagemagick, scrot, gawk | cpl-plugin-hawki-calib | cpl-plugin-hawki-doc | mawk | original-awk | python-tomahawk Non-existing dependencies that are not the first option of alternatives listed are not RC bugs, it is even permitted to intentionally list packages outside Debian main there. cu Adrian
Bug#946217: marked as done (CVE-2019-19333 & CVE-2019-19334 in libyang)
Your message dated Thu, 26 Dec 2019 12:34:39 + with message-id and subject line Bug#946217: fixed in libyang 0.16.105-2 has caused the Debian Bug report #946217, regarding CVE-2019-19333 & CVE-2019-19334 in libyang 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.) -- 946217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libyang0.16 Version: 0.16.105-1 Tags: security Severity: grave This is a security issue tracking bug for CVEs: - CVE-2019-19333 - CVE-2019-19334 Both issues are bugs in processing YANG models and may affect users loading or validating untrusted YANG models. This is a relatively rare use case as normal application use of libyang would rely on application supplied models. Fixes are available upstream. As the package maintainer, my plan for unstable is to ship a 0.16.105-2 quickly, followed by actually bringing 1.0.x into unstable. I've contacted the Debian security team wrt. fixing this for buster. -David --- End Message --- --- Begin Message --- Source: libyang Source-Version: 0.16.105-2 We believe that the bug you reported is fixed in the latest version of libyang, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 946...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Lamparter (supplier of updated libyang 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, 22 Dec 2019 14:27:01 +0100 Source: libyang Architecture: source Version: 0.16.105-2 Distribution: unstable Urgency: medium Maintainer: David Lamparter Changed-By: David Lamparter Closes: 925764 946217 Changes: libyang (0.16.105-2) unstable; urgency=medium . * fix CVE-2019-19333 & CVE-2019-19334 (Closes: #946217) * fix cache corruption crash (upstream bug 752) * fix some gcc & swig version dependent build failures (Closes: #925764) Checksums-Sha1: 1f011145ba8c06f150ab7aa9623152e402baa7bb 2467 libyang_0.16.105-2.dsc 06969415317fc2a8d0e594cd8ba54b4c908c713f 19948 libyang_0.16.105-2.debian.tar.xz fded76b744d65ac8ec24ee82ea3ea5ee7b200f90 10647 libyang_0.16.105-2_amd64.buildinfo Checksums-Sha256: 3f1c42ddde2203992c00dee4b1f3bb53064537cbda3535d29adaf7dafa14c821 2467 libyang_0.16.105-2.dsc 3555409be5c31fd652e32f494d00b33bfea659bacc99e22b29a8d946f2b90ad7 19948 libyang_0.16.105-2.debian.tar.xz 2a0290a223b3a04f7b8bee0193da2642891389fc41461aabd7716c520015abab 10647 libyang_0.16.105-2_amd64.buildinfo Files: 7f63bff3764470b896f34bf868bcc0be 2467 libs optional libyang_0.16.105-2.dsc bfe63808f58e4ff5ea5c93422308f056 19948 libs optional libyang_0.16.105-2.debian.tar.xz 935a8d8de399b1e1e19a08fcf3754c1c 10647 libs optional libyang_0.16.105-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAl4Eof8QHGJlcm5hdEBs dWZmeS5jeAAKCRCVpC/oNTUl+e/FD/4uRutMui0DmXefGh0hupQdLorlvTTKzAvX Cb56wUkWpneA1+pMdapv81wLT5D4zBD/pcOhRGRm4IrqwxNsxy9Dp7x7PbVZJIoq j5jSKJUjmY9445rgdcvHwTTv5Yp0hlM1jqi6XYnfc1VTRGoToQge0vr0TiInP4BV e876UySWKIDP/hzMlUyztmcg0k39OeH1AZw/SLPcWGy/29PENKeOgGZE9f/Q/v// qvjSZ5eClCEffqDdpTVEDxvdtsTYxNSwojPLBkZiT8cW+JZqkqEVloJ2DrC4mrSh b83pwsacsvp9Mxn+YW4aqugey0tjauOM2ZtceyvS7GVKuO+049d0qtHLy442Ev3x hTiwsXP6uxF5Jn61ZRZLO8acsojmQg9Ld6GzdZ8kXe9SLSZPV3j2iyUTklVo1Vgw zvPjGlWaerasdDFh+EMDLy4pugwZddvQA6JJKxXV4+fngdYwmN0SgAveUBMuovel fyYjcBdwSo+FQTvx0garhGyai/Bbntb4DAaiVqGi/f+WnXzgo0lqNOkqEgS1iTRV rYqWKt/9DUOeuKgm2NRCWhrN8Fst7FQ11HE9+UEO84PPEQ/YLxkC7yCFwQcKlkm8 yaVrR6PtFvgrjILnfUdzDWPxyxP/JdrbTi9XOgiSrmvfF9J1BW1Y5yT4u6/ICJP7 txQtXOzLlA== =qqkF -END PGP SIGNATURE End Message ---
Bug#925764: marked as done (libyang: ftbfs with GCC-9)
Your message dated Thu, 26 Dec 2019 12:34:39 + with message-id and subject line Bug#925764: fixed in libyang 0.16.105-2 has caused the Debian Bug report #925764, regarding libyang: 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.) -- 925764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libyang Version: 0.16.105-1 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/libyang_0.16.105-1_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. [...] +#MISSING: 0.16.105-1# (optional)_ZNSt6vectorISt10shared_ptrIN7libyang4TypeEESaIS3_EED2Ev@Base 0.16.52 (optional)_ZNSt6vectorISt10shared_ptrIN7libyang5ErrorEESaIS3_EE17_M_realloc_insertIJS3_EEEvN9__gnu_cxx17__normal_iteratorIPS3_S5_EEDpOT_@Base 0.16.52 (optional)_ZNSt6vectorISt10shared_ptrIN7libyang5IdentEESaIS3_EE12emplace_backIJS3_EEEvDpOT_@Base 0.16.52 (optional)_ZNSt6vectorISt10shared_ptrIN7libyang5IdentEESaIS3_EE17_M_realloc_insertIJS3_EEEvN9__gnu_cxx17__normal_iteratorIPS3_S5_EEDpOT_@Base 0.16.52 @@ -801,18 +801,18 @@ (optional)_ZNSt6vectorISt10shared_ptrIN7libyang6UniqueEESaIS3_EED1Ev@Base 0.16.52 (optional)_ZNSt6vectorISt10shared_ptrIN7libyang6UniqueEESaIS3_EED2Ev@Base 0.16.52 (optional)_ZNSt6vectorISt10shared_ptrIN7libyang7DeviateEESaIS3_EE17_M_realloc_insertIJS3_EEEvN9__gnu_cxx17__normal_iteratorIPS3_S5_EEDpOT_@Base 0.16.52 - (optional)_ZNSt6vectorISt10shared_ptrIN7libyang7DeviateEESaIS3_EED1Ev@Base 0.16.52 - (optional)_ZNSt6vectorISt10shared_ptrIN7libyang7DeviateEESaIS3_EED2Ev@Base 0.16.52 - (optional)_ZNSt6vectorISt10shared_ptrIN7libyang7FeatureEESaIS3_EE17_M_realloc_insertIJS3_EEEvN9__gnu_cxx17__normal_iteratorIPS3_S5_EEDpOT_@Base 0.16.52 - (optional)_ZNSt6vectorISt10shared_ptrIN7libyang7FeatureEESaIS3_EED1Ev@Base 0.16.52 - (optional)_ZNSt6vectorISt10shared_ptrIN7libyang7FeatureEESaIS3_EED2Ev@Base 0.16.52 +#MISSING: 0.16.105-1# (optional)_ZNSt6vectorISt10shared_ptrIN7libyang7DeviateEESaIS3_EED1Ev@Base 0.16.52 +#MISSING: 0.16.105-1# (optional)_ZNSt6vectorISt10shared_ptrIN7libyang7DeviateEESaIS3_EED2Ev@Base 0.16.52 +#MISSING: 0.16.105-1# (optional)_ZNSt6vectorISt10shared_ptrIN7libyang7FeatureEESaIS3_EE17_M_realloc_insertIJS3_EEEvN9__gnu_cxx17__normal_iteratorIPS3_S5_EEDpOT_@Base 0.16.52 +#MISSING: 0.16.105-1# (optional)_ZNSt6vectorISt10shared_ptrIN7libyang7FeatureEESaIS3_EED1Ev@Base 0.16.52 +#MISSING: 0.16.105-1# (optional)_ZNSt6vectorISt10shared_ptrIN7libyang7FeatureEESaIS3_EED2Ev@Base 0.16.52 (optional)_ZNSt6vectorISt10shared_ptrIN7libyang8Type_BitEESaIS3_EE17_M_realloc_insertIJS3_EEEvN9__gnu_cxx17__normal_iteratorIPS3_S5_EEDpOT_@Base 0.16.52 - (optional)_ZNSt6vectorISt10shared_ptrIN7libyang8Type_BitEESaIS3_EED1Ev@Base 0.16.52 - (optional)_ZNSt6vectorISt10shared_ptrIN7libyang8Type_BitEESaIS3_EED2Ev@Base 0.16.52 - (optional)_ZNSt6vectorISt10shared_ptrIN7libyang8Xml_ElemEESaIS3_EE12emplace_backIJS3_EEEvDpOT_@Base 0.16.52 - (optional)_ZNSt6vectorISt10shared_ptrIN7libyang8Xml_ElemEESaIS3_EE17_M_realloc_insertIJS3_EEEvN9__gnu_cxx17__normal_iteratorIPS3_S5_EEDpOT_@Base 0.16.52 - (optional)_ZNSt6vectorISt10shared_ptrIN7libyang8Xml_ElemEESaIS3_EED1Ev@Base 0.16.52 -
Processed: block 945637 with 945840
Processing commands for cont...@bugs.debian.org:
> block 945637 with 945840
Bug #945637 {Done: Alastair McKinstry } [src:ecflow]
ecflow: Python2 removal in sid/bullseye
945637 was not blocked by any bugs.
945637 was not blocking any bugs.
Added blocking bug(s) of 945637: 945840 and 946036
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
945637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945637
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: hkl FTBFS on arm64: sirius segfaults
Processing control commands:
> block 939950 by -1
Bug #939950 {Done: Picca Frédéric-Emmanuel } [src:hkl] hkl:
fails to build with gtk-doc 1.32
939950 was not blocked by any bugs.
939950 was blocking: 939500
Added blocking bug(s) of 939950: 947400
--
939950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939950
947400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#947400: hkl FTBFS on arm64: sirius segfaults
Source: hkl Version: 5.0.0.2569-1 Severity: serious Tags: ftbfs Control: block 939950 by -1 https://buildd.debian.org/status/fetch.php?pkg=hkl=arm64=5.0.0.2569-1=1576087153=0 Making all in figures make[4]: Entering directory '/<>/Documentation/figures' gcc -DHAVE_CONFIG_H -I. -I../.. -Wextra -D_DEFAULT_SOURCE -I../.. -I../../hkl -I/usr/include/glib-2.0 -I/usr/lib/aarch64-linux-gnu/glib-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/aarch64-linux-gnu/glib-2.0/include -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o sirius.o sirius.c sirius.c:244:1: warning: return type defaults to ‘int’ [-Wimplicit-int] 244 | main(void) | ^~~~ /bin/bash ../../libtool --tag=CC --mode=link gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,--whole-archive,../../hkl/.libs/libhkl.a,--no-whole-archive -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o sirius sirius.o ../../hkl/libhkl.la ../../hkl/api2/libhkl2.la -lglib-2.0 -lgobject-2.0 -lglib-2.0 -L/usr/lib/aarch64-linux-gnu -lgsl -lgslcblas -lm -lyaml libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,--whole-archive -Wl,../../hkl/.libs/libhkl.a -Wl,--no-whole-archive -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o .libs/sirius sirius.o ../../hkl/.libs/libhkl.so ../../hkl/api2/.libs/libhkl2.a -lgobject-2.0 -lglib-2.0 -L/usr/lib/aarch64-linux-gnu -lgsl -lgslcblas -lm -lyaml cd . && ./sirius make[4]: *** [Makefile:739: sirius-stamp] Segmentation fault
Bug#937076: marked as done (mopidy-mpris: Python2 removal in sid/bullseye)
Your message dated Thu, 26 Dec 2019 11:06:28 + with message-id and subject line Bug#937076: fixed in mopidy-mpris 3.0.1-1 has caused the Debian Bug report #937076, regarding mopidy-mpris: 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.) -- 937076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937076 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mopidy-mpris Version: 2.0.0-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:mopidy-mpris 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: mopidy-mpris Source-Version: 3.0.1-1 We believe that the bug you reported is fixed in the latest version of mopidy-mpris, 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. Stein Magnus Jodal (supplier of updated mopidy-mpris package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 26 Dec 2019 11:41:59 +0100 Source: mopidy-mpris Architecture: source Version: 3.0.1-1 Distribution: unstable Urgency: medium Maintainer: Stein Magnus Jodal Changed-By: Stein Magnus Jodal Closes: 937076 Changes: mopidy-mpris (3.0.1-1) unstable; urgency=medium . * New upstream release * Switch from Python 2 to 3 (Closes: #937076) * Disable tests because of pkg_resurces usage * Bump debhelper from 9 to 12 * d/control: Bump Standards-Version to 4.4.1, no changes * d/control: Require mopidy >= 3 * d/control: Update Description * d/copyright: Update copyright years * d/copyright: Use HTTPS for the copyright spec Checksums-Sha1: 239909ddee2e48f87140736c26a32a0fd106865a 1962 mopidy-mpris_3.0.1-1.dsc aabd186b7903d0065c15333cd0d72cf84b460f0c 26939 mopidy-mpris_3.0.1.orig.tar.gz ed0bfeb6f100a32eb7ada01ffb78455b4c13fb82 3124 mopidy-mpris_3.0.1-1.debian.tar.xz 9ebee8a2f2c57d300ec97fccc6bc5d4bf13bca2e
Processed: re: pysph: Python2 removal in sid/bullseye
Processing commands for cont...@bugs.debian.org:
> severity 937543 serious
Bug #937543 {Done: Antonio Valentino }
[src:pysph] pysph: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
937543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#947297: Bug#947397: transition: cppunit
On Thu, Dec 26, 2019 at 10:59:32AM +0100, Rene Engelhard wrote: > Most packages just build-depend on it. A rebuild using ratt just works, > except some totally unrelated failures: The builds are still running but as said look good, siconos failed in its tests but with something which looks more like some test needing adapting than a cppunit change Regards, Rene
Processed: limit source to python-demgengeo, tagging 937697
Processing commands for cont...@bugs.debian.org: > limit source python-demgengeo Limiting to bugs with field 'source' containing at least one of 'python-demgengeo' Limit currently set to 'source':'python-demgengeo' > tags 937697 + pending Bug #937697 [src:python-demgengeo] python-demgengeo: Python2 removal in sid/bullseye Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 937697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937697 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: re: actor-framework: Python2 removal in sid/bullseye
Processing commands for cont...@bugs.debian.org: > Severity 942907 serious Bug #942907 [src:actor-framework] actor-framework: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 942907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947387: marked as done (python3-pcapy: missing Breaks+Replaces: python-pcapy)
Your message dated Thu, 26 Dec 2019 09:19:42 + with message-id and subject line Bug#947387: fixed in pcapy 0.11.4-2 has caused the Debian Bug report #947387, regarding python3-pcapy: missing Breaks+Replaces: python-pcapy 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.) -- 947387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-pcapy Version: 0.11.4-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', 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 This test intentionally skipped 'testing' to find file overwrite problems before packages migrate from 'unstable' to 'testing'. >From the attached log (scroll to the bottom...): Preparing to unpack .../python3-pcapy_0.11.4-1_amd64.deb ... Unpacking python3-pcapy (0.11.4-1) ... dpkg: error processing archive /var/cache/apt/archives/python3-pcapy_0.11.4-1_amd64.deb (--unpack): trying to overwrite '/usr/share/doc-base/pcapy', which is also in package python-pcapy 0.10.8-1+b1 Errors were encountered while processing: /var/cache/apt/archives/python3-pcapy_0.11.4-1_amd64.deb cheers, Andreas python-pcapy=0.10.8-1+b1_python3-pcapy=0.11.4-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: pcapy Source-Version: 0.11.4-2 We believe that the bug you reported is fixed in the latest version of pcapy, 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. Emmanuel Arias (supplier of updated pcapy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 25 Dec 2019 23:01:59 -0300 Source: pcapy Architecture: source Version: 0.11.4-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Emmanuel Arias Closes: 947387 Changes: pcapy (0.11.4-2) unstable; urgency=medium . * Add Break+Replaces for python-pcapy (Closes: #947387) Checksums-Sha1: 81bb123505e8bf97c189d6dbc1a137be33fafcfe 1798 pcapy_0.11.4-2.dsc c32a9c1eb5d61fb6fc800381e765f398b9cd6208 5500 pcapy_0.11.4-2.debian.tar.xz 9f26e0f6500fe1e52117cacb0ccc5c0332612666 6463 pcapy_0.11.4-2_source.buildinfo Checksums-Sha256: 20b77cf4b1de973ff1926572d8341bc0e8baeff272207ae0d95062f79a371822 1798 pcapy_0.11.4-2.dsc 3c513db9de4a33a0d48a81426dae05e06b9cfeee44dae30e316122f7c3fbf996 5500 pcapy_0.11.4-2.debian.tar.xz f5233c5f0ac1522622a64f0988854a907994595449aae47d6f826aa8a49c3c83 6463 pcapy_0.11.4-2_source.buildinfo Files: d421127931c649d08fba673a173b087d 1798 python optional pcapy_0.11.4-2.dsc 0d38572772eeda1c3668c114997fc6c3 5500 python optional pcapy_0.11.4-2.debian.tar.xz 8a450f90191ba052a821d04cf163156a 6463 python optional pcapy_0.11.4-2_source.buildinfo -BEGIN PGP SIGNATURE- Comment: Signed by Raphael Hertzog iQEzBAEBCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAl4EdogACgkQA4gdq+vC mrnibggAixTxyLbfbcEm1HumMsOvInzABRsfNqftzcOlUlYz+fXPTPqbNT5rxjI2 TkM+saHZdjPUCxuYb+6hCD/inj+RbTQAI3aiJcuIYzrl7LQju0RUwpDr0sgb29td v4YmnUhhoPmxzxctj9e7BD+YlyJUmCGmYBv4Ccgbc9YKGT8qznmmY05G04tXSGYh hfEyaLp51iC82K9jiE2G3msZu7qW2Cc1EBS65F2x63oomx/w0E705nnLIzkOHx6i 5yJvz3gZQfd29nSdm3WxXCC3vrpTLqxcuOzpIUkqee/O+XysgUCV65C0XxU2z4r8 ANdeovhLg/fOJVRKmvlxyYqEbqMEGg== =7vKs -END PGP SIGNATURE End Message ---
Bug#939260: websploit: Python2 removal in sid/bullseye
On Mon, 16 Dec 2019 14:28:33 +0100 Raphael Hertzog wrote: > Great. Looking forward to it. Do you have any idea how much time you need > to complete this Python 3 port of websploit? On the 21th, I got a private reply saying that he might need 20 days to complete the Python 3 port. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄ Debian Long Term Support: https://deb.li/LTS
Processed: tagging 938660
Processing commands for cont...@bugs.debian.org: > tags 938660 + fixed-upstream Bug #938660 [src:tftpy] tftpy: Python2 removal in sid/bullseye Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 938660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938660 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Tagging 944705 as fixed upstream
Processing commands for cont...@bugs.debian.org: > tag 944705 + fixed-upstream Bug #944705 [python3-mako] alembic: failing tests with python3.8 Added tag(s) fixed-upstream. > forwarded 944705 https://github.com/sqlalchemy/mako/issues/287 Bug #944705 [python3-mako] alembic: failing tests with python3.8 Set Bug forwarded-to-address to 'https://github.com/sqlalchemy/mako/issues/287'. > affects 944705 + pysph Bug #944705 [python3-mako] alembic: failing tests with python3.8 Added indication that 944705 affects pysph > thanks Stopping processing here. Please contact me if you need assistance. -- 944705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944705 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 938649 is forwarded to https://github.com/brunobraga/termsaver/issues/34
Processing commands for cont...@bugs.debian.org: > forwarded 938649 https://github.com/brunobraga/termsaver/issues/34 Bug #938649 [src:termsaver] termsaver: Python2 removal in sid/bullseye Set Bug forwarded-to-address to 'https://github.com/brunobraga/termsaver/issues/34'. > thanks Stopping processing here. Please contact me if you need assistance. -- 938649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938649 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947387: [Python-modules-team] Bug#947387: python3-pcapy: missing Breaks+Replaces: python-pcapy
On Wed, 25 Dec 2019, Emmanuel Arias wrote: > Raphaël, please could you review my patch? Reviewed and uploaded. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄ Debian Long Term Support: https://deb.li/LTS
Bug#945723: Upstream progress on python 3 port
Hello, upstream seems to be close to release a Python 3 version, current WIP is in https://github.com/epinna/weevely3/tree/Debian-master according to https://github.com/epinna/weevely3/pull/119#issuecomment-568770367 Sending this mail to reset the auto-rm clock, hoping that Samuel will upload a fixed version once this is ready at the upstream level. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄ Debian Long Term Support: https://deb.li/LTS
Processed: tagging 938544
Processing commands for cont...@bugs.debian.org: > tags 938544 + fixed-upstream Bug #938544 [src:sphinx-patchqueue] sphinx-patchqueue: Python2 removal in sid/bullseye Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 938544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938544 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Blocking issue for PySPH
Processing commands for cont...@bugs.debian.org: > block 945326 by 944705 Bug #945326 [src:pysph] pysph ftbfs in unstable 945326 was not blocked by any bugs. 945326 was not blocking any bugs. Added blocking bug(s) of 945326: 944705 > thanks Stopping processing here. Please contact me if you need assistance. -- 945326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#944705: Wrong patch for mako?
Dear Thomas, dear Steve, On Wed, 20 Nov 2019 22:24:18 -0800 Steve Langasek wrote: > On Mon, Nov 18, 2019 at 09:07:14AM +0100, Thomas Goirand wrote: > > Hi Steve, > > > Thanks for this, however, the patch you've provided for this bug is for > > Alembic, not for Mako. Do you have a patch available for Mako? > > Sorry, I have no patch for mako; which is why I did not tag this bug > 'patch'. The patch to alembic is a workaround for mako's python3.8 > incompatibility. I think that the issue has been fixed upstream [1,2] so a update of mako to the latest version should fix the problem. The fix seems to be quite easy, the patch is just one line [2]. If Piotr has not time to dedicate to it I could contribute the fix (updated debian package for mako), but I'm not a DD so I will need a sponsor to upload the package for me. Please let me know if you are interested. [1] https://github.com/sqlalchemy/mako/issues/287 [2] https://github.com/sqlalchemy/mako/pull/292 kind regards -- Antonio Valentino
Bug#938489: sinntp: diff for NMU version 1.6-0.1
Control: tags 783971 + patch Control: tags 783971 + pending Control: tags 827146 + pending Control: tags 938489 + patch Control: tags 938489 + pending Dear maintainer, I've prepared an NMU for sinntp (versioned as 1.6-0.1) and uploaded it to DELAYED/15. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru sinntp-1.5/COPYING sinntp-1.6/COPYING --- sinntp-1.5/COPYING 2012-04-18 23:38:05.0 +0300 +++ sinntp-1.6/COPYING 1970-01-01 02:00:00.0 +0200 @@ -1,339 +0,0 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 - - Copyright (C) 1989, 1991 Free Software Foundation, Inc., - 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - - Preamble - - The licenses for most software are designed to take away your -freedom to share and change it. By contrast, the GNU General Public -License is intended to guarantee your freedom to share and change free -software--to make sure the software is free for all its users. This -General Public License applies to most of the Free Software -Foundation's software and to any other program whose authors commit to -using it. (Some other Free Software Foundation software is covered by -the GNU Lesser General Public License instead.) You can apply it to -your programs, too. - - When we speak of free software, we are referring to freedom, not -price. Our General Public Licenses are designed to make sure that you -have the freedom to distribute copies of free software (and charge for -this service if you wish), that you receive source code or can get it -if you want it, that you can change the software or use pieces of it -in new free programs; and that you know you can do these things. - - To protect your rights, we need to make restrictions that forbid -anyone to deny you these rights or to ask you to surrender the rights. -These restrictions translate to certain responsibilities for you if you -distribute copies of the software, or if you modify it. - - For example, if you distribute copies of such a program, whether -gratis or for a fee, you must give the recipients all the rights that -you have. You must make sure that they, too, receive or can get the -source code. And you must show them these terms so they know their -rights. - - We protect your rights with two steps: (1) copyright the software, and -(2) offer you this license which gives you legal permission to copy, -distribute and/or modify the software. - - Also, for each author's protection and ours, we want to make certain -that everyone understands that there is no warranty for this free -software. If the software is modified by someone else and passed on, we -want its recipients to know that what they have is not the original, so -that any problems introduced by others will not reflect on the original -authors' reputations. - - Finally, any free program is threatened constantly by software -patents. We wish to avoid the danger that redistributors of a free -program will individually obtain patent licenses, in effect making the -program proprietary. To prevent this, we have made it clear that any -patent must be licensed for everyone's free use or not licensed at all. - - The precise terms and conditions for copying, distribution and -modification follow. - - GNU GENERAL PUBLIC LICENSE - TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION - - 0. This License applies to any program or other work which contains -a notice placed by the copyright holder saying it may be distributed -under the terms of this General Public License. The "Program", below, -refers to any such program or work, and a "work based on the Program" -means either the Program or any derivative work under copyright law: -that is to say, a work containing the Program or a portion of it, -either verbatim or with modifications and/or translated into another -language. (Hereinafter, translation is included without limitation in -the term "modification".) Each licensee is addressed as "you". - -Activities other than copying, distribution and modification are not -covered by this License; they are outside its scope. The act of -running the Program is not restricted, and the output from the Program -is covered only if its contents constitute a work based on the -Program (independent of having been made by running the Program). -Whether that is true depends on what the Program does. - - 1. You may copy and distribute verbatim copies of the Program's -source code as you receive it, in any medium, provided that you -conspicuously and appropriately publish on each copy an appropriate -copyright notice and disclaimer of warranty; keep intact all the -notices that refer to this License and to the absence of any warranty; -and give any other recipients of the Program a copy of this License -along with the Program. - -You may charge a fee for the
Processed: sinntp: diff for NMU version 1.6-0.1
Processing control commands: > tags 783971 + patch Bug #783971 [sinntp] sinntp: please update Homepage field Ignoring request to alter tags of bug #783971 to the same tags previously set > tags 783971 + pending Bug #783971 [sinntp] sinntp: please update Homepage field Ignoring request to alter tags of bug #783971 to the same tags previously set > tags 827146 + pending Bug #827146 [src:sinntp] sinntp: please update debian/watch Ignoring request to alter tags of bug #827146 to the same tags previously set > tags 938489 + patch Bug #938489 [src:sinntp] sinntp: Python2 removal in sid/bullseye Ignoring request to alter tags of bug #938489 to the same tags previously set > tags 938489 + pending Bug #938489 [src:sinntp] sinntp: Python2 removal in sid/bullseye Ignoring request to alter tags of bug #938489 to the same tags previously set -- 783971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783971 827146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827146 938489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: sinntp: diff for NMU version 1.6-0.1
Processing control commands: > tags 783971 + patch Bug #783971 [sinntp] sinntp: please update Homepage field Ignoring request to alter tags of bug #783971 to the same tags previously set > tags 783971 + pending Bug #783971 [sinntp] sinntp: please update Homepage field Ignoring request to alter tags of bug #783971 to the same tags previously set > tags 827146 + pending Bug #827146 [src:sinntp] sinntp: please update debian/watch Ignoring request to alter tags of bug #827146 to the same tags previously set > tags 938489 + patch Bug #938489 [src:sinntp] sinntp: Python2 removal in sid/bullseye Ignoring request to alter tags of bug #938489 to the same tags previously set > tags 938489 + pending Bug #938489 [src:sinntp] sinntp: Python2 removal in sid/bullseye Ignoring request to alter tags of bug #938489 to the same tags previously set -- 783971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783971 827146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827146 938489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: sinntp: diff for NMU version 1.6-0.1
Processing control commands: > tags 783971 + patch Bug #783971 [sinntp] sinntp: please update Homepage field Added tag(s) patch. > tags 783971 + pending Bug #783971 [sinntp] sinntp: please update Homepage field Added tag(s) pending. > tags 827146 + pending Bug #827146 [src:sinntp] sinntp: please update debian/watch Added tag(s) pending. > tags 938489 + patch Bug #938489 [src:sinntp] sinntp: Python2 removal in sid/bullseye Added tag(s) patch. > tags 938489 + pending Bug #938489 [src:sinntp] sinntp: Python2 removal in sid/bullseye Added tag(s) pending. -- 783971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783971 827146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827146 938489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#947367: lebiniou breaks lebiniou-data arm64 autopkgtest: ALSA lib confmisc.c:767:(parse_card) cannot find card '0'
Processing commands for cont...@bugs.debian.org: > reassign 947367 src:lebiniou Bug #947367 [src:lebiniou, src:lebiniou-data] lebiniou breaks lebiniou-data arm64 autopkgtest: ALSA lib confmisc.c:767:(parse_card) cannot find card '0' Bug reassigned from package 'src:lebiniou, src:lebiniou-data' to 'src:lebiniou'. No longer marked as found in versions lebiniou-data/3.28-2 and lebiniou/3.32-1. Ignoring request to alter fixed versions of bug #947367 to the same values previously set > found 947367 3.32-1 Bug #947367 [src:lebiniou] lebiniou breaks lebiniou-data arm64 autopkgtest: ALSA lib confmisc.c:767:(parse_card) cannot find card '0' Marked as found in versions lebiniou/3.32-1. > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was elb...@debian.org). > usertags 947367 - needs-update Usertags were: needs-update breaks. Usertags are now: breaks. > thanks Stopping processing here. Please contact me if you need assistance. -- 947367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947367 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
