Bug#938073: fssync marked for autoremoval due to python-pylibacl?
With this bug fixed, fssync has just been marked for autoremoval because it would depend (transitively) on python-pylibacl. I don't understand why. fssync only depends on python3-pylibacl.
Processed: Transition started, raising severity
Processing control commands: > severity -1 serious Bug #951656 [src:r-cran-lwgeom] r-cran-lwgeom: FTBFS with PROJ 7.0.0 (ERROR: lazy loading failed for package 'lwgeom') Severity set to 'serious' from 'important' -- 951656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Transition started, raising severity
Processing control commands: > severity -1 serious Bug #951655 [src:r-cran-sf] r-cran-sf: FTBFS with PROJ 7.0.0 (configure: error: proj_api.h not found in standard or given locations.) Severity set to 'serious' from 'important' -- 951655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951655 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938622: tahoe-lafs: Python2 removal in sid/bullseye
Sorry for the delayed response here. I let the package to fall of from testing as upstream does not yet any support for building python3. Though currently there is some work going on for supporting python3 in upstream, I'm not sure of ETA of the procedure. Will reintroduce the package once upstream provides python3 support Cheers,
Bug#953942: marked as done (RM: jack -- RoQA; python2-only; no new upstream code since 2005; better alternatives exist; blocking py2removal effort)
Your message dated Wed, 18 Mar 2020 02:48:51 + with message-id and subject line Bug#953942: Removed package(s) from unstable has caused the Debian Bug report #953942, regarding RM: jack -- RoQA; python2-only; no new upstream code since 2005; better alternatives exist; blocking py2removal effort 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.) -- 953942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953942 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: jack Severity: serious Hello, I believe this package should be removed: * python2-only * no upstream release since 2004 (!) or svn update since 2005 (!) * it's keeping several python2 modules in debian that could be dropped if jack is removed too * several alternatives exist that are much more populare than jack if i dont hear back within a week with a good reason to keep this package, i'll file for its removal. Regards, Sandro -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages jack depends on: pn cdparanoia | cdda2wav ii python 2.7.16-1 pn python-cddb pn python-eyed3 ii python-mutagen 1.40.0-2 ii python-pyvorbis 1.5-5 ii sensible-utils 0.0.12 pn vorbis-tools | flac | lame jack recommends no packages. jack suggests no packages. --- End Message --- --- Begin Message --- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: jack | 3.1.1+cvs20050801-31 | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x --- Reason --- RoQA; python2-only; no new upstream code since 2005; better alternatives exist; blocking py2removal effort -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 953...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/953942 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#953610: marked as done (RM: spambayes -- RoQA; python2-only; no progress in python3 port upstream; no rdeps; low popcon; blocks other python2 removal activities)
Your message dated Wed, 18 Mar 2020 02:48:15 + with message-id and subject line Bug#953610: Removed package(s) from unstable has caused the Debian Bug report #953610, regarding RM: spambayes -- RoQA; python2-only; no progress in python3 port upstream; no rdeps; low popcon; blocks other python2 removal activities 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.) -- 953610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: spambayes Severity: serious Hello, i believe spambayes should be removed from debian: * python2-only and upstream shows no progress in porting to python3 * low popcon * no reverse dependencies * blocks python2 removal effort in Debian. if i dont hear back within a week with a good reason to keep this packaeg in Debian, i'll file for its removal. Regards, Sandro -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages spambayes depends on: ii python 2.7.16-1 pn python-dns pn python-lockfile spambayes recommends no packages. spambayes suggests no packages. --- End Message --- --- Begin Message --- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: spambayes | 1.1b1+git20190201.1335ca8-1 | source, all --- Reason --- RoQA; python2-only; no progress in python3 port upstream; no rdeps; low popcon; blocks other python2 removal activities -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 953...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/953610 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#950290: marked as done (bley: Port to use publicsuffix2, missing depends)
Your message dated Wed, 18 Mar 2020 02:47:52 + with message-id and subject line Bug#953609: Removed package(s) from unstable has caused the Debian Bug report #950290, regarding bley: Port to use publicsuffix2, missing depends 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.) -- 950290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bley Severity: serious Justification: Policy 3.5 The python-publicsuffix package was deprecated by upstream and has been replaced in Debian by python-publicsuffix2. If bley is ported to Python 3 so it can stay in Debian, it also needs to be ported to publicsuffix2. Scott K Versions of packages bley depends on: ii adduser3.118 pn dbconfig-common ii debconf [debconf-2.0] 1.5.71 ii init-system-helpers1.56+nmu1 ii python 2.7.16-1 pn python-dns pn python-ipaddr ii python-publicsuffix1.1.0-2 pn python-spf pn python-twisted-core pn python-twisted-names Versions of packages bley recommends: ii postfix 3.4.8-0+10debu1 pn postgresql-client | mysql-client | sqlite3 pn python-psycopg2 | python-mysqldb bley suggests no packages. --- End Message --- --- Begin Message --- Version: 2.0.0-2+rm Dear submitter, as the package bley 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/953609 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#953609: marked as done (RM: bley -- RoQA; python2-only; no rdeps; extremely low popcon; no release since 2014; RC-buggy)
Your message dated Wed, 18 Mar 2020 02:47:42 + with message-id and subject line Bug#953609: Removed package(s) from unstable has caused the Debian Bug report #953609, regarding RM: bley -- RoQA; python2-only; no rdeps; extremely low popcon; no release since 2014; RC-buggy 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.) -- 953609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bley Severity: serious Hello, i believe bley should be removed from Debian: * python2-only * no reverse dependencies * extremely low popcon * 3 RC bugs already pending * last upstream release in 2014 (ok, upstream and DD coincide) if i dont hear back within a week with a good reason to keep this package in Debian, i'll file for its removal. Regards, Sandro -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bley depends on: ii adduser3.118 pn dbconfig-common ii debconf [debconf-2.0] 1.5.72 ii init-system-helpers1.57 ii python 2.7.16-1 pn python-dns pn python-ipaddr pn python-publicsuffix pn python-spf ii python-twisted-core18.9.0-3 pn python-twisted-names Versions of packages bley recommends: pn postfix | exim4 pn postgresql-client | mysql-client | sqlite3 ii python-mysqldb 1.3.10-2 bley suggests no packages. --- End Message --- --- Begin Message --- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: bley |2.0.0-2 | source, all --- Reason --- RoQA; python2-only; no rdeps; extremely low popcon; no release since 2014; RC-buggy -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 953...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/953609 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#936216: marked as done (bley: Python2 removal in sid/bullseye)
Your message dated Wed, 18 Mar 2020 02:47:52 + with message-id and subject line Bug#953609: Removed package(s) from unstable has caused the Debian Bug report #936216, regarding bley: 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.) -- 936216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936216 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:bley Version: 2.0.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:bley If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 2.0.0-2+rm Dear submitter, as the package bley 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/953609 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#937712: marked as done (Should not be released with bullsye: Python2 removal in sid/bullseye)
Your message dated Wed, 18 Mar 2020 02:49:25 + with message-id and subject line Bug#952500: Removed package(s) from unstable has caused the Debian Bug report #937712, regarding Should not be released with bullsye: 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.) -- 937712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937712 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-dns Version: 2.3.6-4 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-dns If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 2.3.6-4+rm Dear submitter, as the package python-dns 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/952500 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#938522: marked as done (spambayes: Python2 removal in sid/bullseye)
Your message dated Wed, 18 Mar 2020 02:48:27 + with message-id and subject line Bug#953610: Removed package(s) from unstable has caused the Debian Bug report #938522, regarding spambayes: 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.) -- 938522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:spambayes Version: 1.1b1+git20190201.1335ca8-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:spambayes 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.1b1+git20190201.1335ca8-1+rm Dear submitter, as the package spambayes 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/953610 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#927100: marked as done (bley: Please port to python3)
Your message dated Wed, 18 Mar 2020 02:47:52 + with message-id and subject line Bug#953609: Removed package(s) from unstable has caused the Debian Bug report #927100, regarding bley: Please port to python3 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.) -- 927100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927100 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bley Version: 2.0.0-2 Severity: important Python2.7 will go out of upstream security support during the Bullseye development cycle. It is not safe to assume it will be included in the next release, so if you want to be sure bley can stay in Debian, please port it to python3. Personally, I want to remove some packages I maintain, particularly python- ipaddr, which bley depends on during the Bullseye cycle, regardless of what happens to python2.7, so please update (python3 includes the ipaddress module, which was developed from ipaddr, in the standard library). Scott K --- End Message --- --- Begin Message --- Version: 2.0.0-2+rm Dear submitter, as the package bley 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/953609 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#950081: marked as done (vim-tlib: modifies shipped file: /usr/share/vim/addons/doc/tags)
Your message dated Wed, 18 Mar 2020 02:43:19 + with message-id and subject line Bug#950081: fixed in vim-tlib 1.27-3 has caused the Debian Bug report #950081, regarding vim-tlib: modifies shipped file: /usr/share/vim/addons/doc/tags 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.) -- 950081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vim-tlib Version: 1.27-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies files it has shipped. >From the attached log (scroll to the bottom...): 0m24.4s ERROR: FAIL: debsums reports modifications inside the chroot: /usr/share/vim/addons/doc/tags cheers, Andreas vim-tlib_1.27-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: vim-tlib Source-Version: 1.27-3 Done: Andrea Capriotti We believe that the bug you reported is fixed in the latest version of vim-tlib, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 950...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrea Capriotti (supplier of updated vim-tlib 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, 18 Mar 2020 03:00:06 +0100 Source: vim-tlib Architecture: source Version: 1.27-3 Distribution: unstable Urgency: medium Maintainer: Andrea Capriotti Changed-By: Andrea Capriotti Closes: 949263 950081 Changes: vim-tlib (1.27-3) unstable; urgency=medium . * Do not ship docs/tags file (Closes: #950081) * New source upload (Closes: #949263) Checksums-Sha1: 9f97ccd4e678478587d2f8ccd288405efd503900 1840 vim-tlib_1.27-3.dsc b70d7825d382d926fe14df393f953718e820088c 3348 vim-tlib_1.27-3.debian.tar.xz 8e9ec2f4b5c65b21aa20ab69e9121601f94ece29 5591 vim-tlib_1.27-3_source.buildinfo Checksums-Sha256: 739d9baac403ea52ec1bfa22a7921b70505a92ea300301b5ea4d37281216e730 1840 vim-tlib_1.27-3.dsc 3744b21645168de647a58a2ea4fd6e88bcf431a97f09a972062bb69029fb474a 3348 vim-tlib_1.27-3.debian.tar.xz 96f6c5fd1504582c6b2bed7a9ebd843ee20c00bf5f778bcb629d12d1b1c33eed 5591 vim-tlib_1.27-3_source.buildinfo Files: 7442f8e9d1f0f5a248f0447edc575921 1840 editors optional vim-tlib_1.27-3.dsc 3139164b9c1616d02d8bc0a41f08acfc 3348 editors optional vim-tlib_1.27-3.debian.tar.xz 44ff36c54b9dd6d7f455124fc61f9c29 5591 editors optional vim-tlib_1.27-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEGvhvgTlGG2tOSvezC6/u7+lpvVQFAl5xgh0ACgkQC6/u7+lp vVTH8A//flOTM8sWlkL6uSdN7Xf+wvZ5WRmhZFm7c57+CARCHC9cujfnEb4fHlzy AebSLx7dUqPrWss8ov1o86TFewDoHpGE1YvwIwtY5XG5IluSemTQEG4rZP9zhG7O b4T/6M2xqXhee0dd0Y+7fV6Fu2ggIujkztQlv052CvBchYDd9QIba4kngB5cxIKS GGqa2mUzwss/C28mLrtZ8OBvhQesHNggN8ImI5pWp5YfdSeas5MjHF6gbgOsoLky i1pLApd5Wq0yVQRxamst6+H/XfV6KJCk1Jjj6ojCnMo1jgWjuOe5NucnUXkUtjxi aD1SvoWlwITcq7YU+8eQ3zRyUF2q1ECNurCnpKGg+GdGp1IVgzzRkLLGkNWMqo/Q Iu7nehqX+B6sqPSf5x6dVNDIaaYkHmyprOWaPIuLW0yS7iT/BjP7oPXEYWa/BDQm U8bj9gdm69OoY2tSzSbyl8C/GZTFUtVJCgegyIXa3dTfMU9ak1DFuu87xqPe+fRA RwWlHsONqxkwWoMfAWhH++FXUQxQzwUXu8c8TJMqaAhuRpwCmX0wII69WQsB7kKq JtAY1+xpoopR+TVx/AffvRVoQaFb4TLfRtUrJH8uU32twuHzG8AppckLxTAmQDjo JZjVLw1YI6vcIZtBvwbR51lSkisZue8VQBPiym0dX1j+K31rI5s= =iuBZ -END PGP SIGNATURE End Message ---
Bug#954187: marked as done (vault: FTBFS with iam_handle.go:9:2: cannot find package "google.golang.org/api/gensupport")
Your message dated Wed, 18 Mar 2020 01:19:47 +
with message-id
and subject line Bug#954187: fixed in vault 1.0.2+dfsg2-4
has caused the Debian Bug report #954187,
regarding vault: FTBFS with iam_handle.go:9:2: cannot find package
"google.golang.org/api/gensupport"
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.)
--
954187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vault
Version: 1.0.2+dfsg2-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
vault recently started to FTBFS (IIRC it was building fine shortly after
the upload happened).
This error may contain a clue:
src/github.com/hashicorp/vault/vendor/github.com/hashicorp/vault-plugin-secrets-gcp/plugin/iamutil/iam_handle.go:9:2:
cannot find package "google.golang.org/api/gensupport" in any of:
/build/vault-1.0.2+dfsg2/_build/src/github.com/hashicorp/vault/vendor/google.golang.org/api/gensupport
(vendor tree)
/usr/lib/go-1.14/src/google.golang.org/api/gensupport (from $GOROOT)
/build/vault-1.0.2+dfsg2/_build/src/google.golang.org/api/gensupport
(from $GOPATH)
(The full build log is attached.)
Andreas
vault_1.0.2+dfsg2-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: vault
Source-Version: 1.0.2+dfsg2-4
Done: Dmitry Smirnov
We believe that the bug you reported is fixed in the latest version of
vault, 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 954...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dmitry Smirnov (supplier of updated vault 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, 18 Mar 2020 11:34:11 +1100
Source: vault
Architecture: source
Version: 1.0.2+dfsg2-4
Distribution: experimental
Urgency: medium
Maintainer: Dmitry Smirnov
Changed-By: Dmitry Smirnov
Closes: 954187
Changes:
vault (1.0.2+dfsg2-4) experimental; urgency=medium
.
* Un-vendored "golang-github-oklog-run-dev".
* New patch to fix FTBFS with "golang-google-api-dev (>= 0.15.0)"
(Closes: #954187).
* control: added "Pre-Depends: ${misc:Pre-Depends}".
* Standards-Version: 4.5.0.
* Rules-Requires-Root: no.
Checksums-Sha1:
1a1a5af8e172eec2b4afd30990b25f5138cea000 6069 vault_1.0.2+dfsg2-4.dsc
ec3822b04841b99a641cc547003ca4d98ff7bab5 19440
vault_1.0.2+dfsg2-4.debian.tar.xz
9c660b797db39f9bd068cba75ed530c64bb2413b 24966
vault_1.0.2+dfsg2-4_amd64.buildinfo
Checksums-Sha256:
626c386843aed10a38769bf7bdcf9890986ee5e223eae41c1c0294b51a146ad3 6069
vault_1.0.2+dfsg2-4.dsc
e8240cc78518526f93e7979c81aabf73307b0d5e28250fb66e01f67ae8dd0ed7 19440
vault_1.0.2+dfsg2-4.debian.tar.xz
26f40c870bf94cc9c3d336591a9a8bdbf9cbaef9b2f349bbce4ef21d456e461c 24966
vault_1.0.2+dfsg2-4_amd64.buildinfo
Files:
1fce2908d7e8ec556db1b94914d2472a 6069 devel optional vault_1.0.2+dfsg2-4.dsc
573ce40fed6c07a5e63785f60433e535 19440 devel optional
vault_1.0.2+dfsg2-4.debian.tar.xz
3c881be565a75e98d733295710d822d0 24966 devel optional
vault_1.0.2+dfsg2-4_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAl5xdA4ACgkQUra72VOW
jRssWhAAhiNbrL0qWN+biutyC8OfvJqquOAYvgk/DI7CiI+Fww07AMVXTO8R2kCj
g4kDMZ4NjZoA5T6HTuXrmHPvXLv3RX/o0Bph6BynATfy77/qRkPcvsFuW+Ml5umh
2ZU3Sdy86SokUCTZjwo/JHFJwWjc9RzfrkTlr81Yk/vthpSVxFY4KrptHT1I8Qt+
MHlP7zJfGF4BQ20ugCJyYKONuCTnyW36LEGL3tk4i52b/nIYJZaUx7/bpLU2Qt8l
fM9CEsYrk7OGGmnfFpZVimeQnwmkwI9Fu21QeZRI/cvjJQ1rITh54ll1Xfa1Ls57
JfTpfoQRl6V783VwK3gsQePPS22ZuLiUqCQsu+smQ9a8il2K6yScy1vHptrjbvpZ
72MV01GaENJ2mz9JhsFj0GnfyR4x9pYs3SyuhcVP7t0Wzq+V6iSvmpN/xQspnK1c
WM/eW/0n8CDbH0AY/fMwoHz+NjJPuCaoUP2098negLWzZRdLDfxMyKUtO9f6P4A9
cM8zrV2wE1cNR7kJsW6v8nNePzjHDcWVeMJSSoFtgJ63cp28b7ofY7WsADbJ/pNL
wNd3DoQ20SmSB1a+0SUAiIv6sCUsqOyaKOF6Yyo0kj46JmBRD1/6nrDjHrXL0n5t
ljRtTWqvnh8D4ejvb3UrBoAnLt2YKi8AZl4feOX8bqB5/GvWrU4=
=NzvB
-END PGP SIGNATURE End Message ---
Bug#954190: dh-runit: FTBFS on armhf due to shake testsuite failure
Package: dh-runit
Version: 2.8.15
Severity: serious
Tags: ftbfs
Justification: fails to build from source
According to build logs dh-runit FTBFS, but only on armhf. This is because
the testsuite exits nonzero. I can reproduce the error in the log [1]
inside an armhf chroot (created with debootstrap), but not on other
architectures (amd64).
To reproduce there is no need to build the package, just download dh-runit
source inside
the chroot, make sure build-dep are installed, then do
root@lorenz:/home/extra/dh-runit-2.8.15# ghc testrunner.hs
[1 of 1] Compiling Main ( testrunner.hs, testrunner.o )
Linking testrunner ...
root@lorenz:/home/extra/dh-runit-2.8.15# ./testrunner
Error when reading Shake database .shake/.shake.database
Witness type has disappeared, StepKey {4f23698ed1fc9a1a}
CallStack (from HasCallStack):
error, called at src/Development/Shake/Internal/Core/Storage.hs:191:40 in
shake-0.16.4-1RhwnB79ZHh8eiw92e7jMZ:Development.Shake.Internal.Core.Storage
All files will be rebuilt
# tar (for t/out/935997.tar)
# mv (for t/out/935997.tar)
# rm (for t/out/935997.log)
# mkdir (for t/out/935997.log)
[ and the test continue till the end]
Dear libghc-shake-dev maintainer,
I'm not knowledgeble of shake: is this likely a bug in shake or a bug that
need a fix on dh-runit side?
Thanks,
Lorenzo
[1]
https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/armhf/dh-runit.html
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.5.9-van (SMP w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)
Versions of packages dh-runit depends on:
ii debhelper12.9
ii libfile-copy-recursive-perl 0.45-1
ii libfile-slurp-perl .29-1
ii libtext-hogan-perl 2.01-1
dh-runit recommends no packages.
dh-runit suggests no packages.
-- no debconf information
Bug#952083: marked as done (pry: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(@str_output.string).not_to match(/SyntaxError/))
Your message dated Wed, 18 Mar 2020 00:49:17 + with message-id and subject line Bug#952083: fixed in pry 0.12.2-2 has caused the Debian Bug report #952083, regarding pry: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(@str_output.string).not_to match(/SyntaxError/) 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.) -- 952083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pry Version: 0.12.2-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Failure/Error: expect(@str_output.string).not_to match(/SyntaxError/) > >expected "SyntaxError: (eval):2: unterminated list meets end of > file\nissue = %W/\n ^\n" not to match /SyntaxError/ >Diff: >@@ -1,2 +1,4 @@ >-/SyntaxError/ >+SyntaxError: (eval):2: unterminated list meets end of file >+issue = %W/ >+ ^ > # ./spec/syntax_checking_spec.rb:22:in `block (3 levels) in (required)>' > > Finished in 4.71 seconds (files took 0.45738 seconds to load) > 1195 examples, 1 failure, 5 pending > > Failed examples: > > rspec './spec/syntax_checking_spec.rb[1:6]' # Pry should not raise an error > on broken lines: issue = %W/\n343/ > > /usr/bin/ruby2.7 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby2.7" failed: The full build log is available from: http://qa-logs.debian.net/2020/02/22/pry_0.12.2-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: pry Source-Version: 0.12.2-2 Done: Lucas Kanashiro We believe that the bug you reported is fixed in the latest version of pry, 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 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lucas Kanashiro (supplier of updated pry 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: Tue, 17 Mar 2020 21:17:05 -0300 Source: pry Architecture: source Version: 0.12.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Lucas Kanashiro Closes: 952083 Changes: pry (0.12.2-2) unstable; urgency=medium . * Team upload. . [ Utkarsh Gupta ] * Add salsa-ci.yml . [ Lucas Kanashiro ] * Add patch to skip failing test against Ruby 2.7 for now (Closes: #952083) * Bump debhelper compatibility level to 12 * Declare compliance with Debian Policy 4.5.0 * d/control: rules does not require root Checksums-Sha1: 222482951d101da3d3f1cfadaf8b9051206b444d 2097 pry_0.12.2-2.dsc d29bcaed27f74272a851216494b249fe73a17861 8116 pry_0.12.2-2.debian.tar.xz Checksums-Sha256: ac8b2905553cc3d0b22c6223a3b351b6d9af1b650af75bfcc4b1deb9dc34fe79 2097 pry_0.12.2-2.dsc 33706bcfb27864fd5df4c86e75cc551ced68beb54e8d24bad76471801b361506 8116 pry_0.12.2-2.debian.tar.xz Files: 21c5e839bb2d87dbce270c6b8d447441 2097 ruby optional pry_0.12.2-2.dsc e098259e97faed48ec215d26133ab206 8116 ruby optional pry_0.12.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJSBAEBCAA8FiEEjtbD+LrJ23/BMKhw+COicpiDyXwFAl5xaXceHGx1Y2FzLmth bmFzaGlyb0BjYW5vbmljYWwuY29tAAoJEPgjonKYg8l85F4QAJHKSsMvP8qJvbOK au265rqZ8Acg3abX21+Coym4Xw/99UlVUWXVjEtB8LDoELZDQ2v6CT5YF+c7Y7Dv 4Jif5KsCFi6LzBbcoHqHRAbQVX5Y40rB1O0Gd/Zf9z/4QEa99D/gQ1OhrmCU5pNd L/7Ar7ExHEMe7Rartn7NO8NPISlv5Nay6wyP4PBBbggc7OBlsyNA+Yu3KpaAXmqI E3LyGK7IsJHaP2KPKjGfJ0DithRGx7Gd/TOQgFZ8S52
Processed: Bug#954187 marked as pending in vault
Processing control commands: > tag -1 pending Bug #954187 [src:vault] vault: FTBFS with iam_handle.go:9:2: cannot find package "google.golang.org/api/gensupport" Added tag(s) pending. -- 954187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954187: marked as pending in vault
Control: tag -1 pending Hello, Bug #954187 in vault reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/vault/-/commit/8a6566304a2116a71ca2c7a294d06aea52fe51e7 New patch to fix FTBFS with "golang-google-api-dev (>= 0.15.0)" (Closes: #954187). (this message was generated automatically) -- Greetings https://bugs.debian.org/954187
Processed: Bug#952083 marked as pending in pry
Processing control commands: > tag -1 pending Bug #952083 [src:pry] pry: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(@str_output.string).not_to match(/SyntaxError/) Added tag(s) pending. -- 952083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952083: marked as pending in pry
Control: tag -1 pending Hello, Bug #952083 in pry reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/pry/-/commit/81f79754a50877b47840f6c4e581854f29521fac Add patch to skip failing test against Ruby 2.7 for now (Closes: #952083) (this message was generated automatically) -- Greetings https://bugs.debian.org/952083
Bug#954114: marked as done (wine-development: build-dependencies unsatisfiable.)
Your message dated Tue, 17 Mar 2020 23:51:30 + with message-id and subject line Bug#954114: fixed in wine-development 5.3-1 has caused the Debian Bug report #954114, regarding wine-development: build-dependencies unsatisfiable. 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.) -- 954114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wine-development Version: 5.2-3 Severity: serious wine-development build-depends on unicode-data (<< 13) but the version of unicode-data in testing is 13.0.0-1 and the version in unstable is 13.0.0-2 --- End Message --- --- Begin Message --- Source: wine-development Source-Version: 5.3-1 Done: Michael Gilbert We believe that the bug you reported is fixed in the latest version of wine-development, 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 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Gilbert (supplier of updated wine-development package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 17 Mar 2020 23:42:09 + Source: wine-development Architecture: source Version: 5.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Wine Party Changed-By: Michael Gilbert Closes: 954114 Changes: wine-development (5.3-1) unstable; urgency=medium . * New upstream release 5.3, released Feb 28, 2020. - More work towards Ucrtbase runtime support. - Full support for Unicode normalization. - Improvements in Shell Folders handling. - Various bug fixes. * Drop disable/folder-reset.patch, fixed upstream. * Support building with unicode-data 13 (closes: #954114). Checksums-Sha1: 153953284be94cbce2eb5db2303c0cb8b151eaca 4809 wine-development_5.3-1.dsc 8a5195a746183856290e782817e8598fd9d4c71c 20758036 wine-development_5.3.orig.tar.xz 6fef0276c57b1a0cfeda38d28225ba41c3c759b7 3617544 wine-development_5.3-1.debian.tar.xz f49870a8cc5ee3f5659821983d298820603652e1 19537 wine-development_5.3-1_source.buildinfo Checksums-Sha256: 702e676e098d0c18e7bbcd5f92348580ba4f51ec9583ed8ae694325ad813e82f 4809 wine-development_5.3-1.dsc e10098d5ad63f2a25daebc79bfa429887c933852741a1d58c52894067e26ac30 20758036 wine-development_5.3.orig.tar.xz 12476f7e678a57cc00d0d8d1aa5152a892af0001826ca6b1fef02474c21f4a8d 3617544 wine-development_5.3-1.debian.tar.xz fbb736f64e0a2667599768d997f1efa131a326ca00381394fdd97d5940cd6018 19537 wine-development_5.3-1_source.buildinfo Files: 78a783b2dcc8566bee5ff5c6dcae2ba3 4809 otherosfs optional wine-development_5.3-1.dsc 9f50bce891c507016036b78fd9d67d3a 20758036 otherosfs optional wine-development_5.3.orig.tar.xz 072e1a4384d098293861ffda38d4b85c 3617544 otherosfs optional wine-development_5.3-1.debian.tar.xz d9d5cf93c94f1d2fb5919d5559090015 19537 otherosfs optional wine-development_5.3-1_source.buildinfo -BEGIN PGP SIGNATURE- iQQzBAEBCgAdFiEEIwTlZiOEpzUxIyp4mD40ZYkUaygFAl5xYL8ACgkQmD40ZYkU aygJoiAAsmdz2BzOOLLqgsWBqQ/4FQVrfeNmDuD4Emyu7+LPr+q+N5zOJa5NAoeD V/i3WWYuINHD5c+hppdj4BFv6LbpPGEHNCa5bWbrj7zckQ2U+SH9FAa0KkQ+NiVt +yBDPF5HCnL5dfDEVUoePUAp9VbaRcCEqDm6hAL7QJ8vtPrDcN8CSpvn9EbRz5DD ZKG9LODLAcg2RR+4EI4mFGa5ldQrEHAbIYzsMuHCFVtnC4hDDIGIpk5afAIXWYCW OwxZJKjNj+jvd3AK5Rh4mvwDk2v9rbcIsBwmSPqCQLrcgq3erjVZpNRrfAYR5NYK ppbRp9Dqmiky6g5IIkfEO5nDdfUlwYZUtz5GFNpMhGgrPCSrh/7u0NtzxKsIQCgg dwCfCfEkemGKKv4wIB9tw+q7erv4cFYSgkJ+4WtwFZHbShkHVeJ1AT2Ac+7xLQ8K eAwZZZpE99uiEz/FEZrdLqxbnRfBs9ghGSAIiZYs1689gJQdCdE6xd75LIFwW6zK ZZmbfWoZy1nDFHHnKVCKQ4kGBllXg+s40TqXL/jYpzxIabdkKOsEOrJT+4XPwVQI SkrbwJgcFzueK1w7OcZPucROgHELGWj1nVSKnTzZ5M9pTtwoUNO1zq0aH1Ry33r6 mkTZXmUSwzLp2aGFvyIwu0eY0S70PeDIAvxYzMWRimLpfEQp+AmUQCPaFTUlfrJV Ysp5nWGpNJPck3okEJMCPLmM86fLoNIBEMUO8DhKZk87XwUg6lUMECf6ZPzNtM6j jJ1jyGE6sZz/oYe1B3QkpfO/N3xSMmPGuaTwLUcdBtPPogzDDTUaAcCMcp3oEVJU z6AOK2W7A3/vZpDy/tcI2DJJE/Pw5kk2HnMDX2cUzRZ6+hIKrqKW0gmpdkehbj1N kgiehz4kyAaNogdnzww+e3YUtrPQYN7kquZxEQOQ9cEbdsN3GBx/MdIP7b0p6z0a 05cb3Ie2C92sEm6u4O8qXt1Zg5L4tW0YnmCCJt/H1epUxZp7jQO+V8UQorTZAWd5 4I5y3kwuRerpGIl2BNM0hMqox26TjtUIUKR8jBKXmlIUjFUDv9Qc/wG7W4gWw2V+ PH0VqZjEukoMFa7RVjo4fpUPTj/EBduW6OfPFKT5E4bBtn5x4
Bug#954189: acmetool: Buster acmetool stops working in June 1, 2020
Package: acmetool Version: 0.0.62-3+b11 Severity: grave Hello! I'm using Debian Buster 10.3 on servers with acmetool for updating Let's encrypt certificates and I got following email from letsencrypt: According to our records, the software client you're using to get Let's Encrypt TLS/SSL certificates issued or renewed at least one HTTPS certificate in the past two weeks using the ACMEv1 protocol. Here are the details of one recent ACMEv1 request from each of your account(s): ... User agent: acmetool acmeapi Go-http-client/1.1 linux/amd64 ... Beginning June 1, 2020, we will stop allowing new domains to validate using the ACMEv1 protocol. You should upgrade to an ACMEv2 compatible client before then, or certificate issuance will fail. For most people, simply upgrading to the latest version of your existing client will suffice. You can view the client list at: https://letsencrypt.org/docs/client-options/ It means that acmetool package which is in Debian Buster stops working in June 1, 2020. So please update this package in Debian Buster repository to a new version which supports ACMEv2 protocol. Also I would suggest to put acmetool version number into User agent string so it could be easier to identify exact version which is used. I'm marking this issue with severity grave as it matches that description "makes the package in question unusable", which really happens in two months and few days. -- Pali Rohár pali.ro...@gmail.com
Bug#951934: marked as done (autoradio: FTBFS: ImportError: cannot import name 'permalink' from 'django.db.models' (/usr/lib/python3/dist-packages/django/db/models/__init__.py))
Your message dated Tue, 17 Mar 2020 23:19:18 +
with message-id
and subject line Bug#951934: fixed in autoradio 3.4-1
has caused the Debian Bug report #951934,
regarding autoradio: FTBFS: ImportError: cannot import name 'permalink' from
'django.db.models' (/usr/lib/python3/dist-packages/django/db/models/__init__.py)
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.)
--
951934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: autoradio
Version: 3.1-6
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_clean
> I: pybuild base:217: python3.7 setup.py clean
> django_extensions is not installed; I do not use it
> Traceback (most recent call last):
> File "setup.py", line 17, in
> django.setup()
> File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, in setup
> apps.populate(settings.INSTALLED_APPS)
> File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 114, in
> populate
> app_config.import_models()
> File "/usr/lib/python3/dist-packages/django/apps/config.py", line 211, in
> import_models
> self.models_module = import_module(models_module_name)
> File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> File "", line 1006, in _gcd_import
> File "", line 983, in _find_and_load
> File "", line 967, in _find_and_load_unlocked
> File "", line 677, in _load_unlocked
> File "", line 728, in exec_module
> File "", line 219, in _call_with_frames_removed
> File "/<>/autoradio/programs/models.py", line 9, in
> from django.db.models import permalink
> ImportError: cannot import name 'permalink' from 'django.db.models'
> (/usr/lib/python3/dist-packages/django/db/models/__init__.py)
> E: pybuild pybuild:341: clean: plugin distutils failed with: exit code=1:
> python3.7 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.7 returned exit
> code 13
> make[1]: *** [debian/rules:10: override_dh_auto_clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/autoradio_3.1-6_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: autoradio
Source-Version: 3.4-1
Done: Andrea Capriotti
We believe that the bug you reported is fixed in the latest version of
autoradio, 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 951...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andrea Capriotti (supplier of updated autoradio 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: Tue, 17 Mar 2020 23:20:05 +0100
Source: autoradio
Binary: autoradio
Architecture: source all
Version: 3.4-1
Distribution: unstable
Urgency: medium
Maintainer: Andrea Capriotti
Changed-By: Andrea Capriotti
Description:
autoradio - radio automation software
Closes: 951934
Changes:
autoradio (3.4-1) unstable; urgency=medium
.
* New upstream release (Closes: #951934)
* d/watch: Use debian only release
* Update Standards-Version to 4.5.0
* Switch to debhelper level 12
Checksums-Sha1:
0fef673f7938c58c20533cbf08e4d6c60d7b50d7 1996 autoradio_3.4-1.dsc
b9ae0e67a92f3eaaac36e200d37f812589f3679b 575024 autoradio_3.4.orig.tar.gz
b4774f6b2f8e17cf487b69493589e195c980832d 4952 autoradio_3.4-1.debian.tar.xz
0eacca0ab404dfeef48caba6ce5eef154a685085 965636 autoradio_3.4-1_all.deb
47f6e3ab193344c70539fb9bd21f6fc29bc78de6 6739 autoradio_3.4-1_amd64.buildinfo
Checksums-Sha256:
aabbdbe0a4083fe6831955952a8d7
Bug#954187: vault: FTBFS with iam_handle.go:9:2: cannot find package "google.golang.org/api/gensupport"
Source: vault Version: 1.0.2+dfsg2-3 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, vault recently started to FTBFS (IIRC it was building fine shortly after the upload happened). This error may contain a clue: src/github.com/hashicorp/vault/vendor/github.com/hashicorp/vault-plugin-secrets-gcp/plugin/iamutil/iam_handle.go:9:2: cannot find package "google.golang.org/api/gensupport" in any of: /build/vault-1.0.2+dfsg2/_build/src/github.com/hashicorp/vault/vendor/google.golang.org/api/gensupport (vendor tree) /usr/lib/go-1.14/src/google.golang.org/api/gensupport (from $GOROOT) /build/vault-1.0.2+dfsg2/_build/src/google.golang.org/api/gensupport (from $GOPATH) (The full build log is attached.) Andreas vault_1.0.2+dfsg2-3.log.gz Description: application/gzip
Bug#953540: [Aspectc-developers] Fwd: Bug#953540: aspectc++: FTBFS on armel
Control: forwarded -1 aspectc-develop...@aspectc.org Hi Adrian, Olaf, the upstream developer, has a question regarding your patch to aspectc++. Would you mind having a look and ideally sharing your reply to everyone? Thank you! -rt On 3/17/20 11:05 AM, Olaf Spinczyk wrote: > Hi Reinhard! > > Do you understand the reasons behind the patch? > > The difference is the following addition for linking: > > -Wl,--as-needed -latomic -Wl,--no-as-needed > > (1) I wonder why the atomics (e.g. __atomic_fetch_add_4) are not > available by default in armel. They seem to be on most other platforms. > > (2) Why is "--as-needed ... --no-as-needed" necessary? > > (3) Could -latomic also be placed at the end of the list of libraries > (behind the additional libraries needed for Clang 9.0.x)? > > Cheers, > > Olaf > > Am 17.03.20 um 14:10 schrieb Reinhard Tartler: >> Hi aspect c++ developers, >> >> Would the attached patch be acceptable for svn trunk? >> >> Please have a look at the Debian bug for context. I'm happy to clarify any >> questions. >> >> Best >> Rt >> >> >> Original Message >> From: Adrian Bunk >> Sent: March 17, 2020 7:04:58 AM EDT >> To: Ivo De Decker , 953...@bugs.debian.org >> Subject: Bug#953540: aspectc++: FTBFS on armel >> >> Control: tags -1 patch >> >> On Tue, Mar 10, 2020 at 11:12:16AM +, Ivo De Decker wrote: >>> package: src:aspectc++ >>> version: 1:2.2+git20200229-1 >>> severity: serious >>> tags: ftbfs >>> >>> Hi, >>> >>> The latest upload of aspectc++ to unstable fails on armel: >>> >>> https://buildd.debian.org/status/package.php?p=aspectc%2B%2B >> >> Fix attached. >> >>> Cheers, >>> >>> Ivo >> >> cu >> Adrian >> >> >> ___ >> aspectc-developers mailing list >> aspectc-develop...@aspectc.org >> http://aspectc.org/listinfo/aspectc-developers >> > ___ > aspectc-developers mailing list > aspectc-develop...@aspectc.org > http://aspectc.org/listinfo/aspectc-developers >
Processed: Re: [Aspectc-developers] Fwd: Bug#953540: aspectc++: FTBFS on armel
Processing control commands: > forwarded -1 aspectc-develop...@aspectc.org Bug #953540 [src:aspectc++] aspectc++: FTBFS on armel Set Bug forwarded-to-address to 'aspectc-develop...@aspectc.org'. -- 953540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952097: marked as done (spice-gtk: FTBFS: spice-widget-egl.c:29:10: fatal error: libdrm/drm_fourcc.h: No such file or directory)
Your message dated Tue, 17 Mar 2020 22:06:04 + with message-id and subject line Bug#952097: fixed in spice-gtk 0.37-2 has caused the Debian Bug report #952097, regarding spice-gtk: FTBFS: spice-widget-egl.c:29:10: fatal error: libdrm/drm_fourcc.h: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 952097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952097 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spice-gtk Version: 0.37-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wl,-z,relro -o libspice-client-glib-impl.la > bio-gio.lo spice-audio.lo spice-gstaudio.lo spice-util.lo spice-option.lo > spice-client.lo spice-session.lo spice-channel.lo spice-file-transfer-task.lo > gio-coroutine.lo channel-base.lo channel-webdav.lo channel-cursor.lo > channel-display.lo channel-display-gst.lo channel-inputs.lo channel-main.lo > channel-playback.lo channel-port.lo channel-record.lo channel-smartcard.lo > channel-usbredir.lo qmp-port.lo smartcard-manager.lo spice-uri.lo > usb-device-manager.lo usbutil.lo usb-acl-helper.lo vmcstream.lo > decode-glz.lo decode-jpeg.lo decode-zlib.lo client_sw_canvas.lo > spice-glib-main.lo spice-pulse.lo channel-display-mjpeg.lo giopipe.lo > continuation.lo coroutine_ucontext.lospice-glib-enums.lo spice-marshal.lo > ../subprojects/spice-common/common/libspice-common.la > ../subprojects/spice-common/common/libspice-common-client.la -lglib-2.0 > -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lgobject-2.0 -lglib-2.0 -ljpeg > -ljson-glib-1.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lz -llz4 -lpixman-1 -lssl > -lcrypto -lpulse-mainloop-glib -lpulse -lglib-2.0 -lgstapp-1.0 -lgstaudio-1.0 > -lgstbase-1.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lgstapp-1.0 > -lgstvideo-1.0 -lgstbase-1.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lsasl2 > -lcacard -lglib-2.0 -lusb-1.0 -lusbredirhost -lusbredirparser -lphodav-2.0 > -lsoup-2.4 -lgio-2.0 -lgobject-2.0 -lglib-2.0 > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. > -DLOCALE_DIR=\"/usr/share/locale\" -DSPICE_COMPILATION > -DG_LOG_DOMAIN=\"GSpice\" -DUSB_IDS=\"\" -I.. -I../subprojects/spice-common/ > -I../subprojects/spice-common/ -I/usr/include/spice-1 -I/usr/include/pixman-1 > -D_REENTRANT -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-3.0 > -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 > -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include > -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo > -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 > -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo > -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 > -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount > -I/usr/include/blkid -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -DGDK_VERSION_MIN_REQUIRED=GDK_VERSION_3_22 > -DGDK_VERSION_MAX_ALLOWED=GDK_VERSION_3_22 -I/usr/include/cairo > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 > -I/usr/include/libpng16 -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_46 > -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_46 -pthread > -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread > -I/usr/include/json-glib-1.0 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread > -I/usr/include/gstreamer-1.0 -I/usr/include/orc-0.4 > -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread > -I/usr/include/gstreamer-1.0 -I/usr/include/orc-0.4 > -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/cacard > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/lib
Bug#954180: pillow-python2: has failing autopkgtests for python3
package: pillow-python2 version: 6.2.1-3 severity: serious Hi, The autopkgtests for pillow-python2 fail with "selftest-py3 FAIL non-zero exit status 1" I suspect the python 3 tests need to be removed (as the rest of the python3 packaging is in src:pillow). Note that pillow-python2 currently doesn't migrate to testing, also blocking the migration of src:pillow. Ivo
Bug#952309: marked as done (cysignals: FTBFS: help2man: can't get `--help' info from /<>/debian/adhoc/wrappers/cysignals-CSI)
Your message dated Tue, 17 Mar 2020 20:36:26 + with message-id and subject line Bug#952309: fixed in cysignals 1.10.2+ds-4 has caused the Debian Bug report #952309, regarding cysignals: FTBFS: help2man: can't get `--help' info from /<>/debian/adhoc/wrappers/cysignals-CSI 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.) -- 952309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cysignals Version: 1.10.2+ds-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules binary > dh binary --with python3 --with sphinxdoc --buildsystem=pybuild >dh_testroot -O--buildsystem=pybuild >debian/rules override_dh_prep-indep > make[1]: Entering directory '/<>' > help2man --manual="CySIgnals Cython package" --source="CySIgnals (Debian > 1.10.2+ds-3)" --version-string="cysignals-CSI - 1.10.2+ds-3" --locale=C.UTF-8 > --no-info -s 1 \ > -n "debugger information extractor for Python processes" \ > -o cysignals-CSI.1 \ > /<>/debian/adhoc/wrappers/cysignals-CSI > help2man: can't get `--help' info from > /<>/debian/adhoc/wrappers/cysignals-CSI > Try `--no-discard-stderr' if option outputs to stderr > make[1]: *** [debian/rules:43: override_dh_prep-indep] Error 255 The full build log is available from: http://qa-logs.debian.net/2020/02/22/cysignals_1.10.2+ds-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: cysignals Source-Version: 1.10.2+ds-4 Done: Jerome Benoit We believe that the bug you reported is fixed in the latest version of cysignals, 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 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jerome Benoit (supplier of updated cysignals package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 17 Mar 2020 20:01:51 + Source: cysignals Architecture: source Version: 1.10.2+ds-4 Distribution: unstable Urgency: medium Maintainer: Jerome Benoit Changed-By: Jerome Benoit Closes: 952309 Changes: cysignals (1.10.2+ds-4) unstable; urgency=medium . [ Julien Puydt ] * Mark the -doc package M-A: foreign following hinter. * Bump std-vers to 4.5.0. . [ Jerome Benoit ] * Explicitly python3 shebang for cysignals-CSI (Closes: #952309). * Rules-Requires-Root set to no. Checksums-Sha1: e5d7cbefc82007c130cfacf5d792d317c47e88d5 3377 cysignals_1.10.2+ds-4.dsc f8b527e4a3a2038ba314ea108808e09cfc495815 12868 cysignals_1.10.2+ds-4.debian.tar.xz d9c63c6d564237f7dfae55ba9b23cc3a8d0c80bc 8552 cysignals_1.10.2+ds-4_source.buildinfo Checksums-Sha256: e75c909cd792071e8331caafadb0953ca8fcbe9519ce09b6c14cca52adc471d2 3377 cysignals_1.10.2+ds-4.dsc 018f8cf6b73d2a76d327e6974e50cb59e3162141f7c62e11073e9ddd84b5f8b9 12868 cysignals_1.10.2+ds-4.debian.tar.xz 75ced7ae87c2cf8baa006e46d6283de917bf9bd62418868132de39da1aae24ef 8552 cysignals_1.10.2+ds-4_source.buildinfo Files: 2dceb4938e02f493fc74be560561971c 3377 python optional cysignals_1.10.2+ds-4.dsc 491cb8ff28d610490e663dbf53f8e8f9 12868 python optional cysignals_1.10.2+ds-4.debian.tar.xz 2550db7480fe7ef0c8be855aee1ef345 8552 python optional cysignals_1.10.2+ds-4_source.buildinfo -BEGIN PGP SIGNATURE- iQRJBAEBCgAzFiEEriiuFXEN/x2H5adiP5IZpn82xosFAl5xLykVHGNhbGN1bHVz QHJlem96ZXIubmV0AAoJED+SGaZ/NsaL0pcgAJ3SRYINyxmGbKKIvRrwPcfQgrqf +98r7QlvDnEEGg8vw6CIh5ZHBgqBSTVgyIGbcZ7vV9VjX3yuluPJKAzntFqKxwLX rTv5rCAAx6rxG/C1OuAfyNpdf/PjQr2usc1DRDxJZtAfDkn/mmQzj1idp8G5LwBm tYdy8+myGG6vFLnTLDOp+tr3p1q6V1/K/peDFkijilaFhsvgj9VxUrkxLte9GadM v1KgApb36sdNDHXC
Processed: Re: Bug#954158: tightvncserver output a blank screen with gray color under gnome
Processing commands for cont...@bugs.debian.org: > tags 954158 + moreinfo Bug #954158 [tightvncserver] tightvncserver output a blank screen with gray color under gnome Added tag(s) moreinfo. > severity 954158 minor Bug #954158 [tightvncserver] tightvncserver output a blank screen with gray color under gnome Severity set to 'minor' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 954158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954158: tightvncserver output a blank screen with gray color under gnome
tags 954158 + moreinfo severity 954158 minor thanks Hi Have you checked your vnc startup script in ~/.vnc/xstartup or alternatively the startup script in ~/.vncstartup This is the set of commands used to start the window manager and other stuff. When reading the manual I can see that this is not really clear. This could be improved. // Ola On Tue, 17 Mar 2020 at 16:33, gulfstream wrote: > Package: tightvncserver > Version: 1:1.3.9-9.1 > Severity: grave > > > Hello, I want to use tightvnc under the gnome desktop, but only a blank > screen was got in the client. Nothing is on the screen except a cursor. > > What is the matter? Would you please resolve it? > > Thank you very much! > > > > Best regards, > Gulfstream > > > > -- System Information: > Debian Release: bullseye/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.4.0-4-amd64 (SMP w/12 CPU cores) > Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), > LANGUAGE=zh_CN.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages tightvncserver depends on: > ii libc62.29-10 > ii libjpeg62-turbo 1:1.5.2-2+b1 > ii libx11-6 2:1.6.9-2 > ii perl 5.30.0-9 > ii x11-common 1:7.7+20 > ii x11-utils7.7+5 > ii xauth1:1.0.10-1 > ii xserver-common 2:1.20.7-4 > ii zlib1g 1:1.2.11.dfsg-2 > > Versions of packages tightvncserver recommends: > ii x11-xserver-utils 7.7+8 > ii xfonts-base1:1.0.5 > > Versions of packages tightvncserver suggests: > pn tightvnc-java > > -- no debconf information > -- --- Inguza Technology AB --- MSc in Information Technology | o...@inguza.como...@debian.org| | http://inguza.com/Mobile: +46 (0)70-332 1551 | ---
Processed: py2removal bugs severity updates - 2020-03-17 20:28:21.500259+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # and https://lists.debian.org/debian-python/2019/12/msg00076.html > # mail threads for more details on this severity update > # darkradiant is an application, has low popcon (22 < 300), and has 0 > external rdeps or not in testing > severity 936366 serious Bug #936366 [src:darkradiant] darkradiant: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 936366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954174: login broken for usernames starting with a number (badname)
Package: systemd Version: 245-2 Severity: serious Forwarded: https://github.com/systemd/systemd/issues/15141 Usernames that contain a number (or digit) as first character are rejected by v245: https://github.com/systemd/systemd/blob/v245/src/basic/user-util.c#L710 This will lead to login failures. By default, adduser will not allow such usernames to be created, but can be forced to do so via --force-badname. While a leading dot is really questionable, the validation should be relaxed for a leading number. -- Package-specific info: -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemd depends on: ii adduser 3.118 ii libacl1 2.2.53-6 ii libapparmor1 2.13.3-7 ii libaudit11:2.8.5-2+b1 ii libblkid12.34-0.1 ii libc62.30-2 ii libcap2 1:2.32-1 ii libcrypt11:4.4.15-1 ii libcryptsetup12 2:2.3.0-1 ii libgcrypt20 1.8.5-5 ii libgnutls30 3.6.12-2 ii libgpg-error01.37-1 ii libidn2-02.3.0-1 ii libip4tc21.8.4-3 ii libkmod2 27-2 ii liblz4-1 1.9.2-2 ii liblzma5 5.2.4-1+b1 ii libmount12.34-0.1 ii libpam0g 1.3.1-5 ii libpcre2-8-0 10.34-7 ii libseccomp2 2.4.3-1 ii libselinux1 3.0-1+b1 ii libsystemd0 245-2 ii mount2.34-0.1 ii util-linux 2.34-0.1 Versions of packages systemd recommends: ii dbus 1.12.16-2 Versions of packages systemd suggests: ii policykit-10.105-26 ii systemd-container 245-2 Versions of packages systemd is related to: ii dracut 048+80-2 pn initramfs-tools ii libnss-systemd 245-2 ii libpam-systemd 245-2 ii udev 245-2 -- no debconf information
Bug#950568: marked as done (node-copy-webpack-plugin FTBFS: test failures)
Your message dated Tue, 17 Mar 2020 19:04:26 + with message-id and subject line Bug#950568: fixed in node-copy-webpack-plugin 4.3.0-7 has caused the Debian Bug report #950568, regarding node-copy-webpack-plugin FTBFS: test failures 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.) -- 950568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-copy-webpack-plugin Version: 4.3.0-6 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-copy-webpack-plugin.html ... 5 passing (81ms) 65 failing 1) apply function with glob in from can use a glob to move a file to the root directory: TypeError: pathType.dir is not a function at Promise.all.arrify.map.x (/usr/lib/nodejs/globby/node_modules/dir-glob/index.js:40:53) at Array.map () at module.exports (/usr/lib/nodejs/globby/node_modules/dir-glob/index.js:40:35) at globDirs (/usr/lib/nodejs/globby/index.js:64:9) at getPattern (/usr/lib/nodejs/globby/index.js:67:64) at Promise.all.globTasks.map.task (/usr/lib/nodejs/globby/index.js:78:69) at Array.map () at module.exports (/usr/lib/nodejs/globby/index.js:78:41) at processPattern (dist/processPattern.js:51:33) at /build/1st/node-copy-webpack-plugin-4.3.0/dist/index.js:114:57 ... --- End Message --- --- Begin Message --- Source: node-copy-webpack-plugin Source-Version: 4.3.0-7 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of node-copy-webpack-plugin, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 950...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-copy-webpack-plugin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 17 Mar 2020 19:17:34 +0100 Source: node-copy-webpack-plugin Architecture: source Version: 4.3.0-7 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 950568 Changes: node-copy-webpack-plugin (4.3.0-7) unstable; urgency=medium . * Team upload * Embed some little modules for test only * Fix test (Closes: #950568) * Update copyright * Declare compliance with policy 4.5.0 * Add "Rules-Requires-Root: no" Checksums-Sha1: 31d8f577eecc15eb23ee3acb4b0f41ca92ecbc61 2903 node-copy-webpack-plugin_4.3.0-7.dsc 7022b4f09a18cd5b9f8ecaf7d7d723f7df16a5ca 11632 node-copy-webpack-plugin_4.3.0-7.debian.tar.xz Checksums-Sha256: 1f3cc5c26ddd49ece8a18eedefab3777f2855594436106497c3b79000bc91d9c 2903 node-copy-webpack-plugin_4.3.0-7.dsc b5317ba5518cf1d6a980deb5cea796c452cbcb573b29f2f87b2961467fc92dea 11632 node-copy-webpack-plugin_4.3.0-7.debian.tar.xz Files: e2489ab9b7c65bb03f16412c93ed28e2 2903 javascript optional node-copy-webpack-plugin_4.3.0-7.dsc 6d8d3815a190f10e407d51a0d131b4eb 11632 javascript optional node-copy-webpack-plugin_4.3.0-7.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl5xG1EACgkQ9tdMp8mZ 7ukRnw/8CFCxuDmo2qMpALV4hZ63z77ZEuRZfVksCPjxpdjxaUCGfb7Hes+bx6FX twPy4bTud2xy2rDzc8BApHy/ObgWDf/2PldoJvaq0En/FexyFbifcesRfHc+JPiv tIw/zikIXscNBZQmas/D9vrxaf7KbJdkvYo3Xrr5TiUwYZlEAubIh9GMFJwpibuT E4mi1CrUA6FZHNDmeKwvz4YLknuVgnZS3yLTQHC/GXn14PRTG6f92sp/RonTWbfC ZmVTZ4+tHLpr5Oyn0i5nbtbSoHlO3Bcfsb/StXK7uafx5KHLq2EEE6OpUu3TyB2m PMwggXxawdqAyFGROLV4cCdExk/8nRZ8fQ348l2BIbbdGiXgNghOMuWKENuXmkLO 2Nh0uq2KfqJpimkkG9jU0QXnjtu/YZ3DA2b5Pz5JkBVk0lHBVNBq73oUcCGGNgto XJ77wkOwq5BT8Tj0G7ktkhUqVAKxW5L2WaGd3FNB9SQCfBXmk86txtTA7qIw1C9d qApFxrzYL82PiKg4efxIKBzhcs3OHmpSaHv8O9zHtHmQbXjUDS13rPIHw1+nPtcx UlojIhkYUczoM7eTX9EVA/ET5SIoiaQV/m/Vif+WrUW57d+EYBkfHYD2ybUPFB2Z pmrderkhw8ebQy50u4R+iWYybbdisHLBahRbyNo1PO/YPxOsd4g= =umSz -END PGP SIGNATURE End Message ---
Bug#952375: marked as done (node-jsonld: FTBFS: Module not found: Error: Can't resolve 'rdf-canonize' in '/<>/lib')
Your message dated Tue, 17 Mar 2020 18:19:32 + with message-id and subject line Bug#952375: fixed in node-jsonld 1.6.2-3 has caused the Debian Bug report #952375, regarding node-jsonld: FTBFS: Module not found: Error: Can't resolve 'rdf-canonize' in '/<>/lib' 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.) -- 952375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-jsonld Version: 1.6.2-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > BROWSERSLIST='node 6' babeljs \ > --no-babelrc --presets=env \ > --out-dir dist/node6/lib \ > -- lib > lib/ActiveContextCache.js -> dist/node6/lib/ActiveContextCache.js > lib/DocumentCache.js -> dist/node6/lib/DocumentCache.js > lib/JsonLdError.js -> dist/node6/lib/JsonLdError.js > lib/JsonLdProcessor.js -> dist/node6/lib/JsonLdProcessor.js > lib/NQuads.js -> dist/node6/lib/NQuads.js > lib/Rdfa.js -> dist/node6/lib/Rdfa.js > lib/RequestQueue.js -> dist/node6/lib/RequestQueue.js > lib/compact.js -> dist/node6/lib/compact.js > lib/constants.js -> dist/node6/lib/constants.js > lib/context.js -> dist/node6/lib/context.js > lib/documentLoaders/node.js -> dist/node6/lib/documentLoaders/node.js > lib/documentLoaders/xhr.js -> dist/node6/lib/documentLoaders/xhr.js > lib/expand.js -> dist/node6/lib/expand.js > lib/flatten.js -> dist/node6/lib/flatten.js > lib/frame.js -> dist/node6/lib/frame.js > lib/fromRdf.js -> dist/node6/lib/fromRdf.js > lib/graphTypes.js -> dist/node6/lib/graphTypes.js > lib/index.js -> dist/node6/lib/index.js > lib/jsonld.js -> dist/node6/lib/jsonld.js > lib/nodeMap.js -> dist/node6/lib/nodeMap.js > lib/toRdf.js -> dist/node6/lib/toRdf.js > lib/types.js -> dist/node6/lib/types.js > lib/url.js -> dist/node6/lib/url.js > lib/util.js -> dist/node6/lib/util.js > webpack --progress > 0% [0] compiling[0] building > modules[0] building modules > [1] compiling[1] building > modules[1] building modules[0] > building modules[1] building > modules[0] building modules[1] > building modules[0] building > modules[1] building modules[0] > building modules[0] building > modules[0] building modules[0] > building modules[0] building > modules[0] building modules[0] > building modules[0] building > modules[0] building modules[0] > building modules[0] building > modules[0] building modules[0] > building modules[0] building > modules[0] building modules[0] > building modules[0] building > modules[1] building modules[1] > building modules[1] building > modules[1] building modules[1] > building modules[1] building > modules[1] building modules[1] > building modules[1] building > modules[1] building modules[1] > building modules[1] building > modules[1] building modules[1] > building modules[1] building > modules[1] building modules[1] > building modules[0] building > modules[0] building modules[1] > building modules[1] building > modules[0] building modules[1] > building modules[0] building > modules[0] building modules[0] > building modules[0] building > modules[0] building modules[0] > building modules[0] building > modules[0] building modules
Processed: Bug#952375 marked as pending in node-jsonld
Processing control commands: > tag -1 pending Bug #952375 [src:node-jsonld] node-jsonld: FTBFS: Module not found: Error: Can't resolve 'rdf-canonize' in '/<>/lib' Added tag(s) pending. -- 952375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952375: marked as pending in node-jsonld
Control: tag -1 pending Hello, Bug #952375 in node-jsonld reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-jsonld/-/commit/554246f2fa6f907909c53383a3e3ece38ad24762 include suspicious node-babel-runtime subpath to webpack resolver path; closes: bug#952375 (this message was generated automatically) -- Greetings https://bugs.debian.org/952375
Bug#952374: marked as done (node-rdf-canonize: FTBFS: Module not found: Error: Can't resolve 'babel-runtime/core-js/get-iterator' in '/<>/lib')
Your message dated Tue, 17 Mar 2020 18:04:35 + with message-id and subject line Bug#952374: fixed in node-rdf-canonize 1.1.0-1 has caused the Debian Bug report #952374, regarding node-rdf-canonize: FTBFS: Module not found: Error: Can't resolve 'babel-runtime/core-js/get-iterator' in '/<>/lib' 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.) -- 952374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-rdf-canonize Version: 1.0.3-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > BROWSERSLIST='node 6' babeljs \ > --no-babelrc --presets=env \ > --out-dir dist/node6/lib \ > -- lib > lib/AsyncAlgorithm.js -> dist/node6/lib/AsyncAlgorithm.js > lib/IdentifierIssuer.js -> dist/node6/lib/IdentifierIssuer.js > lib/MessageDigest-browser.js -> dist/node6/lib/MessageDigest-browser.js > lib/MessageDigest.js -> dist/node6/lib/MessageDigest.js > lib/NQuads.js -> dist/node6/lib/NQuads.js > lib/Permutator.js -> dist/node6/lib/Permutator.js > lib/URDNA2015.js -> dist/node6/lib/URDNA2015.js > lib/URDNA2015Sync.js -> dist/node6/lib/URDNA2015Sync.js > lib/URGNA2012.js -> dist/node6/lib/URGNA2012.js > lib/URGNA2012Sync.js -> dist/node6/lib/URGNA2012Sync.js > lib/index.js -> dist/node6/lib/index.js > lib/util.js -> dist/node6/lib/util.js > webpack --progress > 0% [0] compiling[0] building > modules[0] building modules > [1] compiling[1] building > modules[1] building modules[0] > building modules[1] building > modules[0] building modules[0] > building modules[0] building > modules[1] building modules[1] > building modules[1] building > modules[0] building modules[0] > building modules[0] building > modules[0] building modules[0] > building modules[0] building > modules[0] building modules[1] > building modules[1] building > modules[1] building modules[1] > building modules[1] building > modules[1] building modules[1] > building modules[0] building > modules[0] building modules[0] > building modules[0] building > modules[1] building modules[1] > building modules[1] building > modules[1] building modules[0] > building modules[1] building > modules[0] building modules[0] > building modules[1] building > modules[1] building modules[0] > building modules[1] building > modules[0] building modules[1] > building modules[0] building > modules[0] building modules[1] > building modules[1] building > modules[0] building modules[0] > building modules[1] building > modules[1] building modules[0] finish > module graph[0] finish module graph > [0] sealing[0] sealing[0] > basic dependencies optimization > [0] dependencies > optimization[0] advanced dependencies > optimization [0] after > dependencies optimization > [0] optimizing[0] basic module > optimization [0] module > optimization[0] advanced module optimization > [0] aft
Processed: Bug#952374 marked as pending in node-rdf-canonize
Processing control commands: > tag -1 pending Bug #952374 [src:node-rdf-canonize] node-rdf-canonize: FTBFS: Module not found: Error: Can't resolve 'babel-runtime/core-js/get-iterator' in '/<>/lib' Added tag(s) pending. -- 952374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952374: marked as pending in node-rdf-canonize
Control: tag -1 pending Hello, Bug #952374 in node-rdf-canonize reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-rdf-canonize/-/commit/45ed73ffd26289f356004c5114369b60d7512d06 extend patch 2002 to include path /usr/share/nodejs and suspicious node-babel-runtime subpath; closes: bug#952374 (this message was generated automatically) -- Greetings https://bugs.debian.org/952374
Processed: Re: runit - default installation wants to remove systemd
Processing control commands: > retitle -1 runit - default installation can force init switch Bug #953875 [src:runit] runit - default installation wants to remove systemd Changed Bug title to 'runit - default installation can force init switch' from 'runit - default installation wants to remove systemd'. > tag -1 moreinfo Bug #953875 [src:runit] runit - default installation can force init switch Added tag(s) moreinfo. -- 953875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953875: runit - default installation wants to remove systemd
Control: retitle -1 runit - default installation can force init switch Control: tag -1 moreinfo Hi, Bastian Blank: > An installation attempt on a default system (with recommends enabled) of > runit wants to replace the installed init: thanks for reporting this, however I can't reproduce. I'm testing in a chroot freshly build with debootstrap as following # debootstrap --arch amd64 sid ./amd64Sid http://deb.debian.org/debian then chroot into it, make sure systemd and systemd-sysv are installed inside the chroot= root@lorenz:/# dpkg -l | grep systemd ii libnss-systemd:amd64 245-2 amd64 nss module providing dynamic user and group name resolution ii libpam-systemd:amd64 245-2 amd64 system and service manager - PAM module ii libsystemd0:amd64 245-2 amd64 systemd utility library ii systemd 245-2 amd64 system and service manager ii systemd-sysv 245-2 amd64 system and service manager - SysV links root@lorenz:/# apt-config dump | grep Recommends APT::Install-Recommends "1"; #first attempt# root@lorenz:/# apt install runit Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: sysuser-helper Recommended packages: runit-sysv | runit-init | runit-systemd The following NEW packages will be installed: runit sysuser-helper 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 131 kB of archives. After this operation, 503 kB of additional disk space will be used. Do you want to continue? [Y/n] #second attempt, try to force the install of runit-sysv# root@lorenz:/# apt install runit runit-sysv Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: runit-sysv : Depends: sysvinit-core but it is not going to be installed E: Unable to correct problems, you have held broken packages. #third attempt, really try harder# root@lorenz:/# apt install runit runit-sysv sysvinit-core Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libnss-systemd Use 'apt autoremove' to remove it. The following additional packages will be installed: initscripts insserv psmisc startpar sysuser-helper sysv-rc Suggested packages: bootchart2 bootlogd The following packages will be REMOVED: libpam-systemd systemd-sysv The following NEW packages will be installed: initscripts insserv psmisc runit runit-sysv startpar sysuser-helper sysv-rc sysvinit-core 0 upgraded, 9 newly installed, 2 to remove and 0 not upgraded. Need to get 696 kB of archives. After this operation, 1339 kB of additional disk space will be used. Do you want to continue? [Y/n] To remove systemd-sysv you need to specify a Recommend of runit and a dependency of the Recommend: it looks pretty safe to me. I've tested also in a Vbox machine with Debian Sid and systemd as init, and I got the same result, except the list of removed packages in the third attempt is huge. Bastian, do you have any idea of why there is this difference? Are you able to reproduce an output like in message#5 within a a minimal chroot install as I have done above? Regards, Lorenzo
Bug#952152: marked as done (node-immutable-tuple: FTBFS: build-dependency not installable: node-rollup-plugin-buble)
Your message dated Tue, 17 Mar 2020 18:38:42 +0100 with message-id <085fe77d-bcf5-c02c-0a4f-f37497e91...@debian.org> and subject line Fixed by buble* updates has caused the Debian Bug report #952152, regarding node-immutable-tuple: FTBFS: build-dependency not installable: node-rollup-plugin-buble 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.) -- 952152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952152 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-immutable-tuple Version: 0.4.10-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 12), mocha, node-yallist, > node-semver, nodejs (>= 6), rollup, node-rollup-plugin-buble, uglifyjs, > pkg-js-tools (>= 0.8.11), build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 12), mocha, node-yallist, > node-semver, nodejs (>= 6), rollup, node-rollup-plugin-buble, uglifyjs, > pkg-js-tools (>= 0.8.11), build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [447 B] > Get:5 copy:/<>/apt_archive ./ Packages [519 B] > Fetched 1923 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: node-rollup-plugin-buble but it > is not going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2020/02/22/node-immutable-tuple_0.4.10-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- X-CrossAssassin-Score: 15515--- End Message ---
Bug#925816: marked as done (qxw: ftbfs with GCC-9)
Your message dated Tue, 17 Mar 2020 17:34:08 + with message-id and subject line Bug#925816: fixed in qxw 20140331-1.1 has caused the Debian Bug report #925816, regarding qxw: 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.) -- 925816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:qxw Version: 20140331-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/qxw_20140331-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. [...] | ^~~~ gui.c:2072:94: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'else' 2072 | else strcpy (s," Mean length: -"); gtk_label_set_text(GTK_LABEL(st_r[1]),s); | ^~ gui.c:2074:3: warning: this 'else' clause does not guard... [-Wmisleading-indentation] 2074 | else strcpy (s," Checked light letters: -"); gtk_label_set_text(GTK_LABEL(st_r[2]),s); | ^~~~ gui.c:2074:95: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'else' 2074 | else strcpy (s," Checked light letters: -"); gtk_label_set_text(GTK_LABEL(st_r[2]),s); | ^~ gui.c:2076:3: warning: this 'else' clause does not guard... [-Wmisleading-indentation] 2076 | else strcpy (s," Checked grid cells: -"); gtk_label_set_text(GTK_LABEL(st_r[3]),s); | ^~~~ gui.c:2076:95: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'else' 2076 | else strcpy (s," Checked grid cells: -"); gtk_label_set_text(GTK_LABEL(st_r[3]),s); | ^~ gui.c: In function 'updatefeas': gui.c:2241:45: warning: '%s' directive writing up to 999 bytes into a region of size between 978 and 979 [-Wformat-overflow=] 2241 | else sprintf(p1," Feasible character%s: %s",(strlen(p0)==1)?"":"s",p0); | ^~ ~~ gui.c:2241:10: note: 'sprintf' output between 22 and 1022 bytes into a destination of size 1000 2241 | else sprintf(p1," Feasible character%s: %s",(strlen(p0)==1)?"":"s",p0); | ^ gcc -Wall -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security `pkg-config --cflags glib-2.0` `pkg-config --cflags gtk+-2.0` -I/opt/local/include -O9 -c draw.c -o draw.o draw.c: In function 'draw_finit': draw.c:460:3: warning: this 'if' clause does not guard... [-Wmisleading-indentation] 460 | if(sfb) cairo_surface_destroy(sfb); sfb=0; | ^~ draw.c:460:40: note: ...this statement, but the latter is misleadingly in
Bug#954134: [d-i bullseye alpha2] installing grub fails
Hi, Am Dienstag, 17. März 2020 schrieb Steve McIntyre: > On Tue, Mar 17, 2020 at 12:06:45PM +, Steve McIntyre wrote: > > > >I can see from your log that you're just using ext4 for the new > >system, and you're booting in BIOS mode. Any other disks attached to > >the system? > > > >Testing at the weekend didn't show any problems for me or Andy. I'm > >doing an explicit re-test now so I can check for any of the above > >messages in my log.s > > I don't see any mention of "corrupted size" in my log and thinks > seemed to run just fine. > > Is this problem repeatable for you? I'm wondering if it might be a > hardware problem or something... Yes, I had it with alpha2, then tested with alpha1 (everything fine) and then again tested with alpha2 to be able to provide logs. I can do further tests though, with different partitioning scheme or filesystem type... Holger -- Sent from my Jolla phone http://www.jolla.com/
Bug#938107: marked as done (python-pyxattr: Python2 removal in sid/bullseye)
Your message dated Tue, 17 Mar 2020 16:50:21 + with message-id and subject line Bug#938107: fixed in python-pyxattr 0.6.1-2 has caused the Debian Bug report #938107, regarding python-pyxattr: 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.) -- 938107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-pyxattr Version: 0.6.1-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-pyxattr 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-pyxattr Source-Version: 0.6.1-2 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of python-pyxattr, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated python-pyxattr 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: Tue, 17 Mar 2020 12:25:10 -0400 Source: python-pyxattr Architecture: source Version: 0.6.1-2 Distribution: unstable Urgency: medium Maintainer: Iustin Pop Changed-By: Sandro Tosi Closes: 938107 Changes: python-pyxattr (0.6.1-2) unstable; urgency=medium . * Drop python2 support; Closes: #938107 * debian/patches/easy-doc.patch - remove dependency between building ext and building doc Checksums-Sha1: ec8822396ef904493c302f136d2460399f08a07b 2154 python-pyxattr_0.6.1-2.dsc 758619d7dd6bb5519a8897aa5e57d43d3b9ae371 8852 python-pyxattr_0.6.1-2.debian.tar.xz 365eeb50a74f4cf4e2d86eed7ca62a3e7138783c 7874 python-pyxattr_0.6.1-2_source.buildinfo Checksums-Sha256: 7c7eea6b750e9abe48662aa159183a4d273e548a15277db5cbd2fb1603695994 2154 python-pyxattr_0.6.1-2.dsc b83ead6574b005885bf786913f593ab97a1f94e425d7a37f926a7053a9581f41 8852 python-pyxattr_0.6.1-2.debian.tar.xz 898c482cb87923b807abd280a2a5c
Bug#938073: marked as done (python-pylibacl: Python2 removal in sid/bullseye)
Your message dated Tue, 17 Mar 2020 16:50:13 + with message-id and subject line Bug#938073: fixed in python-pylibacl 0.5.4-2 has caused the Debian Bug report #938073, regarding python-pylibacl: 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.) -- 938073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938073 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-pylibacl Version: 0.5.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. 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-pylibacl 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-pylibacl Source-Version: 0.5.4-2 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of python-pylibacl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated python-pylibacl 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: Tue, 17 Mar 2020 11:54:20 -0400 Source: python-pylibacl Architecture: source Version: 0.5.4-2 Distribution: unstable Urgency: medium Maintainer: Iustin Pop Changed-By: Sandro Tosi Closes: 938073 Changes: python-pylibacl (0.5.4-2) unstable; urgency=medium . * Drop python2 support; Closes: #938073 Checksums-Sha1: 6319ff0efedecb73d04ef6cfa0e86bd64876a32f 2205 python-pylibacl_0.5.4-2.dsc 1ca5a7615b10d14803fc0008bd6927b334e5d820 8584 python-pylibacl_0.5.4-2.debian.tar.xz fbbcd7327b79202e256451a305107b5ab7518d22 10004 python-pylibacl_0.5.4-2_amd64.buildinfo Checksums-Sha256: 8d26543c39e588c013050c7bd3e6f627cee6718e23b95fe7d4185caecf136aec 2205 python-pylibacl_0.5.4-2.dsc 43df5a94e2f23f4f4db456af2eb9ff59508e5c03a87e3375a35ca3bb6d6e68e7 8584 python-pylibacl_0.5.4-2.debian.tar.xz 1c66a7aa826ebac2f02da356c0cbdda21467bbdc14db61546530d0a0de21eb3b 10004 python-pylibacl_0.5.4-2_amd64.buildinfo F
Processed: reassign 953609 to ftp.debian.org ..., reassign 953610 to ftp.debian.org ..., tagging 952500
Processing commands for cont...@bugs.debian.org: > reassign 953609 ftp.debian.org Bug #953609 [bley] bley: should this package be removed? Bug reassigned from package 'bley' to 'ftp.debian.org'. No longer marked as found in versions bley/2.0.0-2. Ignoring request to alter fixed versions of bug #953609 to the same values previously set > retitle 953609 RM: bley -- RoQA; python2-only; no rdeps; extremely low > popcon; no release since 2014; RC-buggy Bug #953609 [ftp.debian.org] bley: should this package be removed? Changed Bug title to 'RM: bley -- RoQA; python2-only; no rdeps; extremely low popcon; no release since 2014; RC-buggy' from 'bley: should this package be removed?'. > reassign 953610 ftp.debian.org Bug #953610 [spambayes] spambayes: should this package be removed? Bug reassigned from package 'spambayes' to 'ftp.debian.org'. No longer marked as found in versions spambayes/1.1b1+git20190201.1335ca8-1. Ignoring request to alter fixed versions of bug #953610 to the same values previously set > retitle 953610 RM: spambayes -- RoQA; python2-only; no progress in python3 > port upstream; no rdeps; low popcon; blocks other python2 removal activities Bug #953610 [ftp.debian.org] spambayes: should this package be removed? Changed Bug title to 'RM: spambayes -- RoQA; python2-only; no progress in python3 port upstream; no rdeps; low popcon; blocks other python2 removal activities' from 'spambayes: should this package be removed?'. > tags 952500 - moreinfo Bug #952500 [ftp.debian.org] RM: python-dns -- ROM; Obsolete, python2 only, python3 port is in py3dns package Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 952500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952500 953609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953609 953610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953739: marked as done (aac-tactics: FTBFS in sid)
Your message dated Tue, 17 Mar 2020 16:19:15 +
with message-id
and subject line Bug#953739: fixed in aac-tactics 8.11.0-1
has caused the Debian Bug report #953739,
regarding aac-tactics: FTBFS in sid
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.)
--
953739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aac-tactics
Version: 8.9.0-1
Severity: serious
Hello, looks like some changes in sid made aac-tactics FTBFS in sid, log is
available here:
http://debomatic-amd64.debian.net/distribution#unstable/aac-tactics/8.9.0-1/buildlog
I: Running cd /build/aac-tactics-8.9.0/ && env
PATH="/usr/sbin:/usr/bin:/sbin:/bin" HOME="/nonexistent" dpkg-buildpackage -us
-uc
dpkg-buildpackage: info: source package aac-tactics
dpkg-buildpackage: info: source version 8.9.0-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Stéphane Glondu
dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
debian/rules clean
dh clean --with ocaml
debian/rules override_dh_auto_clean
make[1]: Entering directory '/build/aac-tactics-8.9.0'
/usr/bin/make clean
make[2]: Entering directory '/build/aac-tactics-8.9.0'
coq_makefile -f _CoqProject -o Makefile.coq
camlp5 macro files not supported anymore, please port src/aac.ml4 to coqpp
Usage summary:
coq_makefile [file.v] ... [file.ml[ig]?] ... [file.ml{lib,pack}]
... [any] ... [-extra[-phony] result dependencies command]
... [-I dir] ... [-R physicalpath logicalpath]
... [-Q physicalpath logicalpath] ... [VARIABLE = value]
... [-arg opt] ... [-opt|-byte] [-no-install] [-f file] [-o file]
[-h] [--help]
Full list of options:
[file.v]: Coq file to be compiled
[file.ml[ig]?]: Objective Caml file to be compiled
[file.ml{lib,pack}]: ocamlbuild-style file that describes a Objective Caml
library/module
[any] : subdirectory that should be "made" and has a Makefile itself
to do so. Very fragile and discouraged.
[-extra result dependencies command]: add target "result" with command
"command" and dependencies "dependencies". If "result" is not
generic (do not contains a %), "result" is built by _make all_ and
deleted by _make clean_.
[-extra-phony result dependencies command]: add a PHONY target "result"
with command "command" and dependencies "dependencies". Note that
_-extra-phony foo bar ""_ is a regular way to add the target "bar" as
as a dependencies of an already defined target "foo".
[-I dir]: look for Objective Caml dependencies in "dir"
[-R physicalpath logicalpath]: look for Coq dependencies recursively
starting from "physicalpath". The logical path associated to the
physical path is "logicalpath".
[-Q physicalpath logicalpath]: look for Coq dependencies starting from
"physicalpath". The logical path associated to the physical path
is "logicalpath".
[VARIABLE = value]: Add the variable definition "VARIABLE=value"
[-byte]: compile with byte-code version of coq
[-opt]: compile with native-code version of coq
[-arg opt]: send option "opt" to coqc
[-install opt]: where opt is "user" to force install into user directory,
"none" to build a makefile with no install target or
"global" to force install in $COQLIB directory
[-f file]: take the contents of file as arguments
[-o file]: output should go in file file (recommended)
Output file outside the current directory is forbidden.
[-h]: print this usage summary
[--help]: equivalent to [-h]
make[2]: *** [Makefile:9: Makefile.coq] Error 1
make[2]: Leaving directory '/build/aac-tactics-8.9.0'
make[1]: *** [debian/rules:21: override_dh_auto_clean] Error 2
make[1]: Leaving directory '/build/aac-tactics-8.9.0'
make: *** [debian/rules:18: clean] Error 2
dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2
I: copying local configuration
Can you please have a look?
G.
--- End Message ---
--- Begin Message ---
Source: aac-tactics
Source-Version: 8.11.0-1
Done: Ralf Treinen
We believe that the bug you reported is fixed in the latest version of
aac-tactics, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 953...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ralf Treinen (supplier of updated aac-tactics package)
(This message was generated automatical
Bug#952309: cysignals: FTBFS: help2man: can't get `--help' info from /<>/debian/adhoc/wrappers/cysignals-CSI
The reason for this is that src/scripts/cysignals-CSI calls python which is not installed. The script has to be ported to python3. Best, Tobias On 2/23/20 2:37 PM, Lucas Nussbaum wrote: > Source: cysignals > Version: 1.10.2+ds-3 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200222 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): >> fakeroot debian/rules binary >> dh binary --with python3 --with sphinxdoc --buildsystem=pybuild >>dh_testroot -O--buildsystem=pybuild >>debian/rules override_dh_prep-indep >> make[1]: Entering directory '/<>' >> help2man --manual="CySIgnals Cython package" --source="CySIgnals (Debian >> 1.10.2+ds-3)" --version-string="cysignals-CSI - 1.10.2+ds-3" >> --locale=C.UTF-8 --no-info -s 1 \ >> -n "debugger information extractor for Python processes" \ >> -o cysignals-CSI.1 \ >> /<>/debian/adhoc/wrappers/cysignals-CSI >> help2man: can't get `--help' info from >> /<>/debian/adhoc/wrappers/cysignals-CSI >> Try `--no-discard-stderr' if option outputs to stderr >> make[1]: *** [debian/rules:43: override_dh_prep-indep] Error 255 > > The full build log is available from: >http://qa-logs.debian.net/2020/02/22/cysignals_1.10.2+ds-3_unstable.log > > A list of current common problems and possible solutions is available at > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! > > About the archive rebuild: The rebuild was done on EC2 VM instances from > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every > failed build was retried once to eliminate random failures. >
Processed: py2removal bugs severity updates - 2020-03-17 15:35:30.330726+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # and https://lists.debian.org/debian-python/2019/12/msg00076.html > # mail threads for more details on this severity update > # python-pylibacl is a module and has 0 external rdeps or not in testing > severity 938073 serious Bug #938073 [src:python-pylibacl] python-pylibacl: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-pyxattr is a module and has 0 external rdeps or not in testing > severity 938107 serious Bug #938107 [src:python-pyxattr] python-pyxattr: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 938073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938073 938107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#951975: marked as done (fava: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" returned exit code 13)
Your message dated Tue, 17 Mar 2020 16:29:48 +0100
with message-id
and subject line This bug is fixed
has caused the Debian Bug report #951975,
regarding fava: FTBFS: dh_auto_test: error: pybuild --test -i python{version}
-p "3.8 3.7" returned exit code 13
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.)
--
951975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fava
Version: 1.11-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:217: /usr/bin/python3.8 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_fava/build/fava
> copying fava/application.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava
> copying fava/cli.py -> /<>/.pybuild/cpython3_3.8_fava/build/fava
> copying fava/__init__.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava
> copying fava/template_filters.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava
> copying fava/serialisation.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava
> copying fava/json_api.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava
> creating /<>/.pybuild/cpython3_3.8_fava/build/fava/util
> copying fava/util/__init__.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/util
> copying fava/util/date.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/util
> copying fava/util/ranking.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/util
> copying fava/util/excel.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/util
> creating /<>/.pybuild/cpython3_3.8_fava/build/fava/core
> copying fava/core/extensions.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/core
> copying fava/core/ingest.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/core
> copying fava/core/watcher.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/core
> copying fava/core/__init__.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/core
> copying fava/core/tree.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/core
> copying fava/core/fava_options.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/core
> copying fava/core/helpers.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/core
> copying fava/core/misc.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/core
> copying fava/core/budgets.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/core
> copying fava/core/query_shell.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/core
> copying fava/core/attributes.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/core
> copying fava/core/file.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/core
> copying fava/core/number.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/core
> copying fava/core/charts.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/core
> copying fava/core/filters.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/core
> copying fava/core/inventory.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/core
> creating /<>/.pybuild/cpython3_3.8_fava/build/fava/ext
> copying fava/ext/__init__.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/ext
> copying fava/ext/auto_commit.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/ext
> creating /<>/.pybuild/cpython3_3.8_fava/build/fava/help
> copying fava/help/__init__.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/help
> creating
> /<>/.pybuild/cpython3_3.8_fava/build/fava/ext/portfolio_list
> copying fava/ext/portfolio_list/__init__.py ->
> /<>/.pybuild/cpython3_3.8_fava/build/fava/ext/portfolio_list
> running egg_info
> writing fava.egg-info/PKG-INFO
> writing dependency_links to fava.egg-info/dependency_links.txt
> writing entry points to fava.egg-info/entry_points.txt
> writing requirements to fava.egg-info/requires.txt
> writing top-level names to fava.egg-info/top_level.txt
> reading manifest file 'fava.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files found matching '.editorconfig'
> warning: no previously-included files found matching '.gitignore'
> warning: no previously-included files found matching '.travis.yml'
> warning: no previously-included files found matching 'appveyor.yml'
> warning: no previously-included files found matching
> 'fava/translations/babel.conf'
> warning: no previously-included files matching '*.po' found anywhere in
> distribution
> warning: no previously-included files matching '*.py[co]
Bug#954158: tightvncserver output a blank screen with gray color under gnome
Package: tightvncserver Version: 1:1.3.9-9.1 Severity: grave Hello, I want to use tightvnc under the gnome desktop, but only a blank screen was got in the client. Nothing is on the screen except a cursor. What is the matter? Would you please resolve it? Thank you very much! Best regards, Gulfstream -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE=zh_CN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tightvncserver depends on: ii libc62.29-10 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libx11-6 2:1.6.9-2 ii perl 5.30.0-9 ii x11-common 1:7.7+20 ii x11-utils7.7+5 ii xauth1:1.0.10-1 ii xserver-common 2:1.20.7-4 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages tightvncserver recommends: ii x11-xserver-utils 7.7+8 ii xfonts-base1:1.0.5 Versions of packages tightvncserver suggests: pn tightvnc-java -- no debconf information
Bug#954095: marked as done (gimp: fatal error: Segmentation fault on startup)
Your message dated Tue, 17 Mar 2020 15:20:46 +
with message-id
and subject line Bug#953880: fixed in gimp 2.10.14-3
has caused the Debian Bug report #953880,
regarding gimp: fatal error: Segmentation fault on startup
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.)
--
953880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gimp
Version: 2.10.14-2+b1
Severity: grave
--- Please enter the report below this line. ---
When launching GIMP, it fails with a segmentation fault and opens a
window with this text:
```
GNU Image Manipulation Program version 2.10.14
git-describe: GIMP_2_10_12-511-ga4f55d6c7e
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian
9.2.1-31' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2
--prefix=/usr --with-gcc-major-version-only --program-suffix=-9
--program-prefix=x86_64-linux-gnu- --enable-shared
--enable-linker-build-id --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix --libdir=/usr/lib
--enable-nls --enable-bootstrap --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-plugin --enable-default-pie
--with-system-zlib --with-target-system-zlib=auto --enable-objc-gc=auto
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none,hsa --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
--with-build-config=bootstrap-lto-lean --enable-link-mutex
Thread model: posix
gcc version 9.2.1 20200306 (Debian 9.2.1-31)
using babl version 0.1.74 (compiled against version 0.1.74)
using GEGL version 0.4.22 (compiled against version 0.4.22)
using GLib version 2.64.1 (compiled against version 2.64.0)
using GdkPixbuf version 2.40.0 (compiled against version 2.40.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> fatal error: Violación de segmento
Stack trace:
```
# Stack traces obtained from PID 17161 - Thread 17161 #
[New LWP 17162]
[New LWP 17163]
[New LWP 17164]
[New LWP 17165]
[New LWP 17166]
[New LWP 17167]
[New LWP 17168]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7ffe6551d450, fd=16) at
../sysdeps/unix/sysv/linux/read.c:26
Id Target Id Frame
* 1 Thread 0x7f53f5be3e80 (LWP 17161) "gimp" __libc_read
(nbytes=256, buf=0x7ffe6551d450, fd=16) at
../sysdeps/unix/sysv/linux/read.c:26
2 Thread 0x7f53f5643700 (LWP 17162) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
3 Thread 0x7f53f4e42700 (LWP 17163) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
4 Thread 0x7f53e700 (LWP 17164) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
5 Thread 0x7f53ee673700 (LWP 17165) "gmain" 0x7f53f77dfb0f in
__GI___poll (fds=0x560c07512a20, nfds=1, timeout=4482) at
../sysdeps/unix/sysv/linux/poll.c:29
6 Thread 0x7f53ede72700 (LWP 17166) "gdbus" 0x7f53f77dfb0f in
__GI___poll (fds=0x560c0751eac0, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
7 Thread 0x7f53d3fff700 (LWP 17167) "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
8 Thread 0x7f53d37fe700 (LWP 17168) "pool-gimp" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 8 (Thread 0x7f53d37fe700 (LWP 17168)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x7f53f7ab9ae2 in g_cond_wait_until
(cond=cond@entry=0x560c074e9128, mutex=mutex@entry=0x560c074e9120,
end_time=end_time@entry=25537426028) at ../../../glib/gthread-posix.c:1588
now = {tv_sec = 25522, tv_nsec = 426028438}
span = {tv_sec = 14, tv_nsec = 99562}
sampled = 0
res =
Bug#953880: marked as done (gimp: fatal error: Segmentation fault on startup)
Your message dated Tue, 17 Mar 2020 15:20:46 + with message-id and subject line Bug#953880: fixed in gimp 2.10.14-3 has caused the Debian Bug report #953880, regarding gimp: fatal error: Segmentation fault on startup 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.) -- 953880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953880 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gimp Version: 2.10.14-2+b1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? unknown - perhaps sid update * What exactly did you do (or not do) that was effective (or ineffective)? reinstalled - no change * What was the outcome of this action? same problem * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-rc5-siduction-amd64 (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gimp depends on: ii gimp-data2.10.14-2 ii libaa1 1.4p5-46+b1 ii libbabl-0.1-00.1.74-1 ii libbz2-1.0 1.0.8-2 ii libc62.30-2 ii libcairo21.16.0-4 ii libfontconfig1 2.13.1-2+b1 ii libfreetype6 2.10.1-2 ii libgcc-s110-20200304-1 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-3 ii libgegl-0.4-00.4.22-1 ii libgexiv2-2 0.12.0-2 ii libgimp2.0 2.10.14-2+b1 ii libglib2.0-0 2.64.0-2 ii libgs9 9.51~dfsg-1 ii libgtk2.0-0 2.24.32-4 ii libgudev-1.0-0 233-1 ii libharfbuzz0b2.6.4-1 ii libheif1 1.6.1-1 ii libilmbase24 2.3.0-6 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-2 2.9-4+b1 ii liblzma5 5.2.4-1+b1 ii libmng1 1.0.10+dfsg-3.1+b5 ii libmypaint-1.5-1 1.5.1-1 ii libopenexr24 2.3.0-6 ii libopenjp2-7 2.3.1-1 ii libpango-1.0-0 1.42.4-8 ii libpangocairo-1.0-0 1.42.4-8 ii libpangoft2-1.0-01.42.4-8 ii libpng16-16 1.6.37-2 ii libpoppler-glib8 0.71.0-6 ii librsvg2-2 2.46.4-1 ii libstdc++6 10-20200304-1 ii libtiff5 4.1.0+git191117-2 ii libwebp6 0.6.1-2+b1 ii libwebpdemux20.6.1-2+b1 ii libwebpmux3 0.6.1-2+b1 ii libwmf0.2-7 0.2.8.4-17 ii libx11-6 2:1.6.9-2 ii libxcursor1 1:1.2.0-2 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxmu6 2:1.1.2-2+b3 ii libxpm4 1:3.5.12-1 ii xdg-utils1.1.3-1 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages gimp recommends: ii ghostscript 9.51~dfsg-1 Versions of packages gimp suggests: pn gimp-data-extras pn gimp-help-en | gimp-help pn gvfs-backends ii libasound21.2.2-2.1 ``` GNU Image Manipulation Program version 2.10.14 git-describe: GIMP_2_10_12-511-ga4f55d6c7e C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 9.2.1-31' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none,hsa --without-cuda-driver --enable-chec
Bug#942618: marked as done (vilistextum: Maintainer email address not working)
Your message dated Tue, 17 Mar 2020 15:21:57 + with message-id and subject line Bug#942618: fixed in vilistextum 2.6.9-1.2 has caused the Debian Bug report #942618, regarding vilistextum: Maintainer email address not working 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.) -- 942618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vilistextum Version: 2.6.9-1.1 Severity: serious Justification: Policy 3.3 Policy requires a maintainer email address that accepts mail. Mail for this maintainer has been failing for some time: This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: rai...@ubuntu.com host mx.canonical.com [91.189.95.10] SMTP error from remote mail server after RCPT TO:: 550 5.1.1 : Recipient address rejected: User unknown in virtual alias table Scott K --- End Message --- --- Begin Message --- Source: vilistextum Source-Version: 2.6.9-1.2 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of vilistextum, 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 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated vilistextum package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 10 Mar 2020 10:22:28 -0400 Source: vilistextum Architecture: source Version: 2.6.9-1.2 Distribution: unstable Urgency: medium Maintainer: Siegfried-Angel Gevatter Pujals Changed-By: Boyuan Yang Closes: 783279 942618 Changes: vilistextum (2.6.9-1.2) unstable; urgency=medium . * Non-maintainer upload. * debian/control: + Use the maintainer's Debian email address. (Closes: #942618) + Update homepage information. (Closes: #783279) * debian/copyright: Update copyright format. Checksums-Sha1: 62c05c9840c9719609392f681f09b1a66a73 1760 vilistextum_2.6.9-1.2.dsc 32e5f3223b444cd04ba1a8a3af19803743b9451f 1809 vilistextum_2.6.9-1.2.diff.gz 4ccee004db2d42db7ec60caec3290968d5885789 5882 vilistextum_2.6.9-1.2_amd64.buildinfo Checksums-Sha256: 0094c20bd27e398ab7fb165d1ed08a8465a110b099dbf33715ff60ebc6108e10 1760 vilistextum_2.6.9-1.2.dsc 1ca6d3a8329fd64647d159ff37a3b150f843fa7d7e7d39e707991d2e435e016b 1809 vilistextum_2.6.9-1.2.diff.gz 96d20aa0bcef373c6f037f66777d397468bbd99dc9c3d43772d026803560fa39 5882 vilistextum_2.6.9-1.2_amd64.buildinfo Files: be252a736009ce6a23c2255f2485ef01 1760 text optional vilistextum_2.6.9-1.2.dsc c33a42db5ec4c2b632f7c5e2f2f685c1 1809 text optional vilistextum_2.6.9-1.2.diff.gz 0fb0246c7164169f5a5f828fb4e0ad2c 5882 text optional vilistextum_2.6.9-1.2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl5no/cACgkQwpPntGGC Ws7ETw//dCMVU+dI2drJ7yWD3Xv7wKWPNA02sJSRY8Nqw92MnnYoi+Skngo9gVwy i0CSPReQoeCX5vUTD9SFKzFLsITyxYG/mqSyIIQW/zTAZyhlWyq2JeR/J29OK33h nkrjt8VQWzj/e/NKI6GRzwtaSXbPXllOJ/nurQ8ZxsqoWS9Zp3VksRgTSa1ft9NA oNi2neeewFeIp3nRya6A6QGkCRBD4Mhg3tk9avWbpTDQmIJ6DJ3+IeggQsalSNNa viEqOi7gpmAtnUQahLoWhsoga2ruYC+LK9tsQYAvKjPPGxMUPiOxGTPp7fbHkmWe ahz7CJvDdl5C6PpS9BgMleZeUdnqitEAZpefcQQBCxTHtEiJlSXQYhcwTJxjkFvY /mgCq9phKHqvVla0FLeKHqmw4S8pFehSIJvzIkq8An2OLCFrMtiGCz2AA1ZWNGiS vu/RCzSD2MyGN2LNc5KtdI1wnGtFIL16x+y50GXIu9aqY9cYeiRjTIEkfiqA35hI VIkhq2OegPZing0NFIwGAe9+IN89YuCXo25avwF+zfz7og2v2XZrzZhosRkqrS/S S+UnNZtYPK+DZxtu4GgREKdAhkhQQRuGmoRvFmKgskqDzLDFrOKJE1DEyP0oKhZ8 BD1ECq3guzg8RKBJ7ufRZSmWJPN9TfVek3CvZFy+EFbyLrbqqCM= =OUs9 -END PGP SIGNATURE End Message ---
Bug#950147: sagemath ftbfs with python 3.8
Control: block -1 by 953633 We have a patch for this but I'm waiting for a fix of a bug in pari that causes test failures and a test timeout. Best, Tobias On Wed, 29 Jan 2020 17:46:47 +0100 Tobias Hansen wrote: > It does if applied first. But ok, the ipython 7 patch needed some small > changes. I applied it in the branch python3.8 on salsa. > > Best, > Tobias > > On 1/29/20 5:35 PM, Matthias Klose wrote: > > On 1/29/20 5:20 PM, Tobias Hansen wrote: > >> Hi, > >> > >> Arch Linux has a patch for that: > >> https://git.archlinux.org/svntogit/community.git/tree/trunk/sagemath-python-3.8.patch?h=packages/sagemath > >> > >> We plan to apply it when the default Python switches to 3.8. If we apply > >> it now, the doctests will fail with Python 3.7. I haven't yet tried > >> building with Python 3.8 though. > > yes, I'm aware of that patch. It doesn't apply cleanly. Could you help > > updating it? > > > > > >> Best, > >> Tobias > >> > >> On 1/29/20 3:07 PM, Matthias Klose wrote: > >>> Package: src:sagemath > >>> Version: 9.0-1 > >>> Severity: important > >>> Tags: sid bullseye > >>> User: debian-pyt...@lists.debian.org > >>> Usertags: python3.8 > >>> > >>> sagemath ftbfs with python 3.8. Not sure if you already can check that in > >>> Debian, however in Ubuntu, there seem to be a lot of failing tests, plus > >>> the > >>> tests failing because of too many open files (googling about that, I > >>> found some > >>> hints, but just for MacOSX). > >>> > >>> Build logs at > >>> https://launchpad.net/ubuntu/+source/sagemath/9.0-1build1 > >>> > >>> Any help would be appreciated. > >>> > > >
Processed: Re: Bug#950147: sagemath ftbfs with python 3.8
Processing control commands: > block -1 by 953633 Bug #950147 [src:sagemath] sagemath ftbfs with python 3.8 950147 was not blocked by any bugs. 950147 was not blocking any bugs. Added blocking bug(s) of 950147: 953633 -- 950147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950147 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#950154: marked as done (apertium-eo-ca FTBFS with apertium 3.6.1)
Your message dated Tue, 17 Mar 2020 15:04:10 + with message-id and subject line Bug#950154: fixed in apertium-eo-ca 1:0.9.1~r60655-4 has caused the Debian Bug report #950154, regarding apertium-eo-ca FTBFS with apertium 3.6.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 950154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-eo-ca Version: 1:0.9.1~r60655-3 Severity: serious Tags: ftbfs bullseye sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-eo-ca.html ... lt-comp rl apertium-eo-ca.eo.dix ca-eo.autogen.bin apertium-eo-ca.ca.dix:867: element pardef: Schemas validity error : Element 'pardef': Duplicate key-sequence ['/ampli__adj'] in unique identity-constraint 'pardef-unique'. apertium-eo-ca.ca.dix:3606: element pardef: Schemas validity error : Element 'pardef': Duplicate key-sequence ['angl/ès__n'] in unique identity-constraint 'pardef-unique'. apertium-eo-ca.ca.dix:8883: element pardef: Schemas validity error : Element 'pardef': Duplicate key-sequence ['fo/ndre__vblex'] in unique identity-constraint 'pardef-unique'. apertium-eo-ca.ca.dix:15192: element pardef: Schemas validity error : Element 'pardef': Duplicate key-sequence ['concórr/er__vblex'] in unique identity-constraint 'pardef-unique'. lt-comp lr apertium-eo-ca.ca.dix ca-eo.automorf.bin apertium-eo-ca.ca.acx Warning (3135): Paths to rule 25 blocked by rule 7. Warning (4174): Paths to rule 33 blocked by rule 27. Warning (4174): Paths to rule 33 blocked by rule 27. Warning (7438): Paths to rule 61 blocked by rule 60. Warning (7438): Paths to rule 61 blocked by rule 60. Warning (7438): Paths to rule 61 blocked by rule 60. Warning (7438): Paths to rule 61 blocked by rule 60. Warning (11728): Paths to rule 94 blocked by rule 93. Warning (11728): Paths to rule 94 blocked by rule 93. Warning (11728): Paths to rule 94 blocked by rule 93. Warning (11728): Paths to rule 94 blocked by rule 93. Warning (11728): Paths to rule 94 blocked by rule 93. Warning (11728): Paths to rule 94 blocked by rule 93. Warning (12094): Paths to rule 97 blocked by rule 96. Warning (12094): Paths to rule 97 blocked by rule 96. Warning (12094): Paths to rule 97 blocked by rule 96. Warning (12094): Paths to rule 97 blocked by rule 96. Warning (12094): Paths to rule 97 blocked by rule 96. Warning (12094): Paths to rule 97 blocked by rule 96. Warning (12094): Paths to rule 97 blocked by rule 96. Warning (12094): Paths to rule 97 blocked by rule 96. Warning (12094): Paths to rule 97 blocked by rule 96. Warning (12094): Paths to rule 97 blocked by rule 96. Warning (12094): Paths to rule 97 blocked by rule 96. Warning (12094): Paths to rule 97 blocked by rule 96. Warning (12094): Paths to rule 97 blocked by rule 96. Warning (12094): Paths to rule 97 blocked by rule 96. Warning (12094): Paths to rule 97 blocked by rule 96. Warning (12094): Paths to rule 97 blocked by rule 96. Warning (12094): Paths to rule 97 blocked by rule 96. Warning (12094): Paths to rule 97 blocked by rule 96. Warning (13173): Paths to rule 109 blocked by rule 24. Warning (13173): Paths to rule 109 blocked by rule 24. Warning (13173): Paths to rule 109 blocked by rule 24. Warning (13173): Paths to rule 109 blocked by rule 24. lt-comp rl apertium-eo-ca.eo-ca.dix ca-eo.autobil.bin final@inconditional 15 60 main@standard 45269 82925 main@standard 75370 111593 apostrophes@postblank 698 1033 final@inconditional 14 59 main@standard 63897 120001 make[2]: Leaving directory '/build/1st/apertium-eo-ca-0.9.1~r60655' make[1]: *** [Makefile:309: all] Error 2 --- End Message --- --- Begin Message --- Source: apertium-eo-ca Source-Version: 1:0.9.1~r60655-4 Done: Kartik Mistry We believe that the bug you reported is fixed in the latest version of apertium-eo-ca, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 950...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kartik Mistry (supplier of updated apertium-eo-ca 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: Tue, 17 Mar 2020 19:46:44 +0530 Sour
Bug#954033: marked as done (pdfarranger: The package should depend on python3-gi-cairo. Otherwise the application will not render pages.)
Your message dated Tue, 17 Mar 2020 14:49:39 + with message-id and subject line Bug#954033: fixed in pdfarranger 1.4.2-1 has caused the Debian Bug report #954033, regarding pdfarranger: The package should depend on python3-gi-cairo. Otherwise the application will not render pages. 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.) -- 954033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pdfarranger Version: 1.1.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, I tried using the application. It rendered empty pages and wrote a lot of TypeError: Couldn't find foreign struct converter for 'cairo.Context' to stderr. I searched the net on the error message and found suggestions to install python3-gi-cairo. The application stared working properly. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8), LANGUAGE=sv:en_GB (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pdfarranger depends on: ii gir1.2-glib-2.0 1.62.0-5 ii gir1.2-gtk-3.0 3.24.13-1 ii gir1.2-poppler-0.18 0.71.0-6 ii python3 3.7.5-3 ii python3-cairo1.16.2-2 ii python3-gi 3.34.0-6 ii python3-pypdf2 1.26.0-4 pdfarranger recommends no packages. pdfarranger suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: pdfarranger Source-Version: 1.4.2-1 Done: to...@debian.org (Dr. Tobias Quathamer) We believe that the bug you reported is fixed in the latest version of pdfarranger, 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 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dr. Tobias Quathamer (supplier of updated pdfarranger 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: Tue, 17 Mar 2020 14:44:57 +0100 Source: pdfarranger Architecture: source Version: 1.4.2-1 Distribution: unstable Urgency: medium Maintainer: Python Applications Packaging Team Changed-By: Dr. Tobias Quathamer Closes: 954033 Changes: pdfarranger (1.4.2-1) unstable; urgency=medium . * Team upload. * New upstream version 1.4.2 - Drop patches, both have been applied upstream * Depend on python3-gi-cairo. Thanks to Jacob Hallén (Closes: #954033) Checksums-Sha1: e6feb229a16115c438509906a42b46a78f25b792 2185 pdfarranger_1.4.2-1.dsc d4731b73fe475c37db50b7d748675860140843f8 121515 pdfarranger_1.4.2.orig.tar.gz 8ae2fae00f8232e45aafaaecdbc1ec1e724cc278 4372 pdfarranger_1.4.2-1.debian.tar.xz 9cc57890ead296335f6804344f4c5c18061c01b3 7307 pdfarranger_1.4.2-1_amd64.buildinfo Checksums-Sha256: 2de9a692521b8a70fd6419d4b1cb1dff88e1b2529b31a3d2fb3f2c04551aea63 2185 pdfarranger_1.4.2-1.dsc 7fcf7bb3cc4a093a17013bac3c3857e9dcfd46aa3814d17287b58bac9ae90772 121515 pdfarranger_1.4.2.orig.tar.gz e1dd4d3a7295d3851bbb55425f855020fa8b9ec53265f4487e26af6502840b1f 4372 pdfarranger_1.4.2-1.debian.tar.xz b5ad704fb48da5bdedcf390ece1b2393cad402cfaccc9a127bda1c1e5dda39d1 7307 pdfarranger_1.4.2-1_amd64.buildinfo Files: 05845542ad8c15ab4ecd394edc4921d6 2185 graphics optional pdfarranger_1.4.2-1.dsc 961646f8b2569eb7790e08abbac9767f 121515 graphics optional pdfarranger_1.4.2.orig.tar.gz 6e873c418f6136e44f662aaf5c0ce7e9 4372 graphics optional pdfarranger_1.4.2-1.debian.tar.xz 9883b3059df44e0f2d8eacc3620231b7 7307 graphics optional pdfarranger_1.4.2-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAl5w1cUACgkQEwLx8Dbr 6xlbRA//aI2i1h0P6EmNLpL+WK3LMUAbfkdjwbUCrWgMtnVIHz9h2LGJBZCUoYU2 13h2SmPxuQPQNTcF+ZB57Z42MBuWlkUyf4sNi8/2NDbQBhdpQ7F+/l4Zpw3CdozY 4LImZYBWplo0fpTlxhKTXroGpsw6SDUdNxN6sB4zcxWJSWQr/ck+Sx+9JpR0E7vR TRn5mrXqAikgP5WvlHLYORR7XtmTmNVx1MvPDRCfBPP6HUDctTJ1uy597EsILL6/ IpyBdPk1KnOKTZ92X0XT1NdtVrjQH5F6BC52zbkFmc+DuZv63EU3l63+Ixzr0gHg SR8D4+Wf+
Bug#953880: marked as pending in gimp
Control: tag -1 pending Hello, Bug #953880 in gimp reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/gimp/-/commit/26eed4e96e753f0b12f37d54df1351225b598f5b Fix crashes with GLib 2.64 Closes: #953880 Closes: #953854 Closes: #953794 (this message was generated automatically) -- Greetings https://bugs.debian.org/953880
Processed: Bug#953880 marked as pending in gimp
Processing control commands: > tag -1 pending Bug #953880 [gimp] gimp: fatal error: Segmentation fault on startup Bug #954095 [gimp] gimp: fatal error: Segmentation fault on startup Added tag(s) pending. Added tag(s) pending. -- 953880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953880 954095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954147: src:dateparser: Requires a package outside of Main
On 2020-03-17 09:14:03, Scott Kitterman wrote: > Package: src:dateparser > Version: 0.7.2-1 > Severity: serious > Justification: Policy 2.2.1 > > This package uses python pip to download and install packages from outside the > Debian archive to run autopkgtests. Main is required to be self-contained, > including for tests. See the FTP Master's reject FAQ [1] item Non-Main II. > > An excerpt from a recent autpkgtest log is included below to demonstrate the > issue with this package. I believe this is only a problem because autopkgtest isn't configured to install the build-deps of the package, not that it requires packages outside of main per se. I would be happy to take a patch or NMU to do this, but i'm a bit busy to take care of this myself right now.
Processed: tagging 954079, notfound 954100 in 3.0.4, found 954100 in 3.0.4-1, found 954134 in 20200314
Processing commands for cont...@bugs.debian.org: > tags 954079 + sid bullseye Bug #954079 [magic-wormhole] magic-wormhole: Fails to send with a type error Added tag(s) bullseye and sid. > notfound 954100 3.0.4 Bug #954100 [src:gdcm] Error: A deprecated csdestruct_derived typemap was found for vtkGDCMTesting The source 'gdcm' and version '3.0.4' do not appear to match any binary packages No longer marked as found in versions gdcm/3.0.4. > found 954100 3.0.4-1 Bug #954100 [src:gdcm] Error: A deprecated csdestruct_derived typemap was found for vtkGDCMTesting Marked as found in versions gdcm/3.0.4-1. > found 954134 20200314 Bug #954134 [debian-installer] [d-i bullseye alpha2] installing grub fails Marked as found in versions debian-installer/20200314. > thanks Stopping processing here. Please contact me if you need assistance. -- 954079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954079 954100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954100 954134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#954033 marked as pending in pdfarranger
Processing control commands: > tag -1 pending Bug #954033 [pdfarranger] pdfarranger: The package should depend on python3-gi-cairo. Otherwise the application will not render pages. Added tag(s) pending. -- 954033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954033: marked as pending in pdfarranger
Control: tag -1 pending Hello, Bug #954033 in pdfarranger reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/applications/pdfarranger/-/commit/5930995b64f2bc2c9db0ae6628ade8b964ce40ba Depend on python3-gi-cairo. Closes: #954033 Thanks: Jacob Hallén (this message was generated automatically) -- Greetings https://bugs.debian.org/954033
Bug#954154: src:salt: Requires a package outside of Main
Package: src:salt
Version: 3000+dfsg1-3
Severity: serious
Justification: Policy 2.2.1
This package uses python pip to download and install packages from outside the
Debian archive to run autopkgtests. Main is required to be self-contained,
including for tests. See the FTP Master's reject FAQ [1] item Non-Main II.
An excerpt from a recent autpkgtest log is included below to demonstrate the
issue with this package. Note that while there is a tracback that looks
like a pip issue, installing pep8 with pip works outside the salt
autopkgtest. It's not enough that something be available from Main, you
actually have to use it.
In any case, the autopkgtest fails, so this has to be addressed
regardless.
Scott K
[1] https://ftp-master.debian.org/REJECT-FAQ.html
==
ERROR: test_install_requirements_parsing
(unit.states.test_pip_state.PipStateTest)
[CPU:0.0%|MEM:15.7%]
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.hrrvw95w/downtmp/autopkgtest_tmp/tests/unit/states/test_pip_state.py",
line 66, in test_install_requirements_parsing
ret = pip_state.installed('pep8=1.3.2')
File "/usr/lib/python3/dist-packages/salt/states/pip_state.py", line 794, in
installed
out = _check_pkg_version_format(pkg)
File "/usr/lib/python3/dist-packages/salt/states/pip_state.py", line 211, in
_check_pkg_version_format
install_req = _from_line(pkg)
File "/usr/lib/python3/dist-packages/salt/states/pip_state.py", line 147, in
_from_line
import pip._internal.req.constructors # pylint: disable=E0611,E0401
File "/usr/lib/python3/dist-packages/pip/_internal/req/__init__.py", line 11,
in
from .req_file import parse_requirements
File "/usr/lib/python3/dist-packages/pip/_internal/req/req_file.py", line 19,
in
from pip._internal.cli import cmdoptions
File "/usr/lib/python3/dist-packages/pip/_internal/cli/cmdoptions.py", line
28, in
from pip._internal.models.target_python import TargetPython
File "/usr/lib/python3/dist-packages/pip/_internal/models/target_python.py",
line 3, in
from pip._internal.pep425tags import get_supported, version_info_to_nodot
File "/usr/lib/python3/dist-packages/pip/_internal/pep425tags.py", line 7, in
from pip._vendor.packaging.tags import (
ImportError: cannot import name 'compatible_tags' from
'pip._vendor.packaging.tags' (/usr/lib/python3/dist-packages/packaging/tags.py)
--
Ran 8922 tests in 2132.334s
FAILED (errors=1, skipped=989, expected failures=1)
autopkgtest [06:37:27]: test unittest: ---]
autopkgtest [06:37:27]: test unittest: - - - - - - - - - - results - - - - - -
- - - -
unittest FAIL non-zero exit status 1
Bug#954033: Fixed in new upload
Hi Jacob, thanks for filing this bug, it slipped through my testing. A new package is on its way to unstable. Regards, Tobias signature.asc Description: OpenPGP digital signature
Bug#932659: node: modules are not getting detected in a fresh sid chroot environment
Hi,
This still occurs for me. I have a armhf chroot of Sid. It seems to be
using a node path relative to the current directory (as far as I can
tell). These paths should probably be /usr prefixed (and not relative to
cwd), but I wouldn't know where to begin fixing this.
See my tests below:
root@sid-armhf:/# node -p "require.resolve.paths('y18n')"
[ '/node_modules',
'/root/.node_modules',
'/root/.node_libraries',
'/lib/arm-linux-gnueabihf/nodejs',
'/share/nodejs',
'/lib/nodejs' ]
root@sid-armhf:/# su user
$ pwd
/
$ node -p "require.resolve.paths('y18n')"
[ '/node_modules',
'/home/user/.node_modules',
'/home/user/.node_libraries',
'/lib/arm-linux-gnueabihf/nodejs',
'/share/nodejs',
'/lib/nodejs' ]
$ cd
$ pwd
/home/user
$ node -p "require.resolve.paths('y18n')"
[ '/home/user/node_modules',
'/home/node_modules',
'/node_modules',
'/home/user/.node_modules',
'/home/user/.node_libraries',
'/home/lib/arm-linux-gnueabihf/nodejs',
'/home/share/nodejs',
'/home/lib/nodejs' ]
$
--
Josh
Bug#954134: [d-i bullseye alpha2] installing grub fails
On Tue, Mar 17, 2020 at 12:06:45PM +, Steve McIntyre wrote: > >I can see from your log that you're just using ext4 for the new >system, and you're booting in BIOS mode. Any other disks attached to >the system? > >Testing at the weekend didn't show any problems for me or Andy. I'm >doing an explicit re-test now so I can check for any of the above >messages in my log.s I don't see any mention of "corrupted size" in my log and thinks seemed to run just fine. Is this problem repeatable for you? I'm wondering if it might be a hardware problem or something... -- Steve McIntyre, Cambridge, UK.st...@einval.com "We're the technical experts. We were hired so that management could ignore our recommendations and tell us how to do our jobs." -- Mike Andrews
Bug#954153: src:python-virtualenv: Please drop python-virtualenv tests
Package: src:python-virtualenv Version: 15.1.0+ds-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) This is really an autopkgtest failure bug, but I think ftbfs is the closest tag we have. Please drop the autopkgtests for python-virtualenv (python2). The python-pip package has dropped support for python2 ad these tests now fail. It looks pretty trivial to address, so not bothering with a patch. Scott K
Bug#954151: src:logbook: Requires a package outside of Main
Package: src:logbook Version: 1.5.3-2 Severity: serious Justification: Policy 2.2.1 This package uses python pip to download and install packages from outside the Debian archive to run autopkgtests. Main is required to be self-contained, including for tests. See the FTP Master's reject FAQ [1] item Non-Main II. An excerpt from a recent autpkgtest log is included below to demonstrate the issue with this package. Scott K [1] https://ftp-master.debian.org/REJECT-FAQ.html Collecting riemann-client Downloading https://files.pythonhosted.org/packages/48/0e/13b4b8a23515bedc3f51d1a184affe3d996777eeb0485921e9b74ec8c516/riemann_client-6.5.0-py3-none-any.whl Collecting click>=3.1 (from riemann-client) Downloading https://files.pythonhosted.org/packages/dd/c0/4d8f43a9b16e289f36478422031b8a63b54b6ac3b1ba605d602f10dd54d6/click-7.1.1-py2.py3-none-any.whl (82kB) Collecting protobuf<4.0.0,>=3.2.0 (from riemann-client) Downloading https://files.pythonhosted.org/packages/ff/f1/8dcd4219bbae8aa44fe8871a89f05eca2dca9c04f8dbfed8a82b7be97a88/protobuf-3.11.3-cp37-cp37m-manylinux1_x86_64.whl (1.3MB) Requirement already satisfied: six>=1.9 in /usr/lib/python3/dist-packages (from protobuf<4.0.0,>=3.2.0->riemann-client) (1.14.0) Requirement already satisfied: setuptools in /usr/lib/python3/dist-packages (from protobuf<4.0.0,>=3.2.0->riemann-client) (44.0.0) Installing collected packages: click, protobuf, riemann-client Successfully installed click-7.1.1 protobuf-3.11.3 riemann-client-6.5.0 Obtaining file:///tmp/autopkgtest-lxc.equsj9no/downtmp/build.Szw/src Collecting Jinja2 (from Logbook==1.5.3) Downloading https://files.pythonhosted.org/packages/27/24/4f35961e5c669e96f6559760042a55b9bcfcdb82b9bdb3c8753dbe042e35/Jinja2-2.11.1-py2.py3-none-any.whl (126kB) Collecting brotli (from Logbook==1.5.3) Downloading https://files.pythonhosted.org/packages/93/d9/1afb3a964cf4564748a8fbd8e5ca4a2d585269d421e4d773982d27c158ba/Brotli-1.0.7-cp37-cp37m-manylinux1_x86_64.whl (352kB) Collecting cython (from Logbook==1.5.3) Downloading https://files.pythonhosted.org/packages/17/49/5a2834a373417130b77d43b39a5a9a117d528e8d63ecb439555afef8b33d/Cython-0.29.15-cp37-cp37m-manylinux1_x86_64.whl (2.1MB) Collecting execnet>=1.0.9 (from Logbook==1.5.3) Downloading https://files.pythonhosted.org/packages/d3/2e/c63af07fa471e0a02d05793c7a56a9f7d274a8489442a5dc4fb3b2b3c705/execnet-1.7.1-py2.py3-none-any.whl Collecting pytest-cov>=2.6 (from Logbook==1.5.3) Downloading https://files.pythonhosted.org/packages/b9/54/3673ee8be482f81527678ac894276223b9814bb7262e4f730469bb7bf70e/pytest_cov-2.8.1-py2.py3-none-any.whl Requirement already satisfied: pytest>4.0 in /usr/lib/python3/dist-packages (from Logbook==1.5.3) (4.6.9) Collecting pyzmq (from Logbook==1.5.3) Downloading https://files.pythonhosted.org/packages/37/d3/46dd789cf7be91d7acd7d6fe0b683b6527ef6f276fb0700a035c37baae27/pyzmq-19.0.0-cp37-cp37m-manylinux1_x86_64.whl (1.1MB) Collecting redis (from Logbook==1.5.3) Downloading https://files.pythonhosted.org/packages/f0/05/1fc7feedc19c123e7a95cfc9e7892eb6cdd2e5df4e9e8af6384349c1cc3d/redis-3.4.1-py2.py3-none-any.whl (71kB) Collecting sqlalchemy (from Logbook==1.5.3) Downloading https://files.pythonhosted.org/packages/8c/30/4134e726dd5ed13728ff814fa91fc01c447ad8700504653fe99d91fdd34b/SQLAlchemy-1.3.15.tar.gz (6.1MB) Installing build dependencies: started Installing build dependencies: finished with status 'done' Collecting MarkupSafe>=0.23 (from Jinja2->Logbook==1.5.3) Downloading https://files.pythonhosted.org/packages/98/7b/ff284bd8c80654e471b769062a9b43cc5d03e7a615048d96f4619df8d420/MarkupSafe-1.1.1-cp37-cp37m-manylinux1_x86_64.whl Collecting apipkg>=1.4 (from execnet>=1.0.9->Logbook==1.5.3) Downloading https://files.pythonhosted.org/packages/67/08/4815a09603fc800209431bec5b8bd2acf2f95abdfb558a44a42507fb94da/apipkg-1.5-py2.py3-none-any.whl Collecting coverage>=4.4 (from pytest-cov>=2.6->Logbook==1.5.3) Downloading https://files.pythonhosted.org/packages/9a/08/7fa92679a903cac0e01a7fee2cadd92089d96a3002c34e8f2295b80d6b68/coverage-5.0.3-cp37-cp37m-manylinux1_x86_64.whl (227kB) Requirement already satisfied: importlib-metadata>=0.12 in /usr/lib/python3/dist-packages (from pytest>4.0->Logbook==1.5.3) (1.5.0) Requirement already satisfied: more-itertools>=4.0.0 in /usr/lib/python3/dist-packages (from pytest>4.0->Logbook==1.5.3) (4.2.0) Building wheels for collected packages: sqlalchemy Running setup.py bdist_wheel for sqlalchemy: started Running setup.py bdist_wheel for sqlalchemy: finished with status 'done' Stored in directory: /root/.cache/pip/wheels/24/7f/c8/8d776916c91c613d593f39a98cad373442c7f77027340eb1ec Successfully built sqlalchemy Installing collected packages: MarkupSafe, Jinja2, brotli, cython, apipkg, execnet, coverage, pytest-cov, pyzmq, redis, sqlalchemy, Logbook Running setup.py develop for Logbook Successfully installed Jinja2-2.11.1 Logbook MarkupSafe-1.1.1 apipkg-1.5 brotli-1.0.7 cove
Bug#954150: src:ffc: Requires a package outside of Main
Package: src:ffc Version: 2019.1.0.post0-2 Severity: serious Justification: Policy 2.2.1 This package uses python pip to download and install packages from outside the Debian archive to run autopkgtests. Main is required to be self-contained, including for tests. See the FTP Master's reject FAQ [1] item Non-Main II. An excerpt from a recent autpkgtest log is included below to demonstrate the issue with this package. Scott K [1] https://ftp-master.debian.org/REJECT-FAQ.html autopkgtest [09:47:53]: test test-ffc: [--- Processing /tmp/autopkgtest-lxc.td_b983u/downtmp/build.hYv/src/libs/ffc-factory Building wheels for collected packages: fenics-ffc-factory Running setup.py bdist_wheel for fenics-ffc-factory: started Running setup.py bdist_wheel for fenics-ffc-factory: finished with status 'done' Stored in directory: /home/debci/.cache/pip/wheels/2d/bd/a7/594a35b5121cbc9e0d2b3beaa2f60a7743b517526a828aa000 Successfully built fenics-ffc-factory Installing collected packages: fenics-ffc-factory Successfully installed fenics-ffc-factory-0.0.1
Bug#954148: src:doit: Requires a package outside of Main
Package: src:doit Version: 0.31.1-3.2 Severity: serious Justification: Policy 2.2.1 This package uses python pip to download and install packages from outside the Debian archive to run autopkgtests. Main is required to be self-contained, including for tests. See the FTP Master's reject FAQ [1] item Non-Main II. An excerpt from a recent autpkgtest log is included below to demonstrate the issue with this package. Scott K [1] https://ftp-master.debian.org/REJECT-FAQ.html autopkgtest [09:47:11]: test unittests: [--- Requirement already satisfied: pyflakes in /usr/lib/python3/dist-packages (from -r dev_requirements.txt (line 4)) (2.1.1) Requirement already satisfied: pytest>=4.0 in /usr/lib/python3/dist-packages (from -r dev_requirements.txt (line 5)) (4.6.9) Collecting pytest-ignore-flaky (from -r dev_requirements.txt (line 6)) Downloading https://files.pythonhosted.org/packages/9b/ea/4264700ace0298cac8b78ae21e6328ba9da5106257af816aecf958b0981e/pytest_ignore_flaky-1.0.0-py3-none-any.whl Requirement already satisfied: coverage>=4.0 in /usr/lib/python3/dist-packages (from -r dev_requirements.txt (line 7)) (4.5.2) Collecting doit-py>=0.4.0 (from -r dev_requirements.txt (line 8)) Downloading https://files.pythonhosted.org/packages/ed/75/725220e25308fb7e91080d62d532b9e5eb530f7570d8afd6d89dc26461dc/doit-py-0.4.0.tar.gz Requirement already satisfied: importlib-metadata>=0.12 in /usr/lib/python3/dist-packages (from pytest>=4.0->-r dev_requirements.txt (line 5)) (1.5.0) Requirement already satisfied: more-itertools>=4.0.0 in /usr/lib/python3/dist-packages (from pytest>=4.0->-r dev_requirements.txt (line 5)) (4.2.0) Collecting configclass (from doit-py>=0.4.0->-r dev_requirements.txt (line 8)) Downloading https://files.pythonhosted.org/packages/8d/bd/c408897e93e150f1108bdca05cd1e19fac96ab4c6f41c138fc2be93397c3/configclass-0.1.0.tar.gz Requirement already satisfied: doit in /usr/lib/python3/dist-packages (from doit-py>=0.4.0->-r dev_requirements.txt (line 8)) (0.31.1) Collecting mergedict>=0.2.0 (from configclass->doit-py>=0.4.0->-r dev_requirements.txt (line 8)) Downloading https://files.pythonhosted.org/packages/b4/f2/98a8757575ae9eb2d2ac8a7dbced7da3214f394b4c7f0716abc8e3292569/mergedict-1.0.0-py3-none-any.whl Requirement already satisfied: pyinotify in /usr/lib/python3/dist-packages (from doit->doit-py>=0.4.0->-r dev_requirements.txt (line 8)) (0.9.6) Building wheels for collected packages: doit-py, configclass Running setup.py bdist_wheel for doit-py: started Running setup.py bdist_wheel for doit-py: finished with status 'done' Stored in directory: /home/debci/.cache/pip/wheels/ea/b1/ec/63ec025da799f4ff1005d1d55bb6bff4b4687a1868f57f58e1 Running setup.py bdist_wheel for configclass: started Running setup.py bdist_wheel for configclass: finished with status 'done' Stored in directory: /home/debci/.cache/pip/wheels/0c/54/70/1ca35a8e24061cc30d138377cbf1e20d33c12fc58e2dd4f401 Successfully built doit-py configclass Installing collected packages: pytest-ignore-flaky, mergedict, configclass, doit-py Successfully installed configclass-0.1.0 doit-py-0.4.0 mergedict-1.0.0 pytest-ignore-flaky-1.0.0
Bug#954147: src:dateparser: Requires a package outside of Main
Package: src:dateparser Version: 0.7.2-1 Severity: serious Justification: Policy 2.2.1 This package uses python pip to download and install packages from outside the Debian archive to run autopkgtests. Main is required to be self-contained, including for tests. See the FTP Master's reject FAQ [1] item Non-Main II. An excerpt from a recent autpkgtest log is included below to demonstrate the issue with this package. Scott K [1] https://ftp-master.debian.org/REJECT-FAQ.html autopkgtest [11:23:23]: test command1: pip3 install -U -rrequirements.txt -rtests/requirements.txt ; nosetests3 tests autopkgtest [11:23:23]: test command1: [--- Collecting convertdate==2.1.3 (from -r requirements.txt (line 1)) Downloading https://files.pythonhosted.org/packages/74/83/d0fa07078f4d4ae473a89d7d521aafc66d82641ea0af0ef04a47052e8f17/convertdate-2.1.3-py2.py3-none-any.whl Collecting jdatetime==3.1.0 (from -r requirements.txt (line 2)) Downloading https://files.pythonhosted.org/packages/c6/9d/1391454b7afdf8d35b85a7658598ad2e363b74b723cdf75431e040f1c010/jdatetime-3.1.0.tar.gz Collecting python-dateutil==2.7.5 (from -r requirements.txt (line 3)) Downloading https://files.pythonhosted.org/packages/74/68/d87d9b36af36f44254a8d512cbfc48369103a3b9e474be9bdfe536abfc45/python_dateutil-2.7.5-py2.py3-none-any.whl (225kB) Collecting pytz==2018.9 (from -r requirements.txt (line 4)) Downloading https://files.pythonhosted.org/packages/61/28/1d3920e4d1d50b19bc5d24398a7cd85cc7b9a75a490570d5a30c57622d34/pytz-2018.9-py2.py3-none-any.whl (510kB) Collecting regex==2019.01.24 (from -r requirements.txt (line 5)) Downloading https://files.pythonhosted.org/packages/aa/eb/8a56aaf3a0a2a70cf2e017a8fb1ac5b6bad64a143d3096b0c0282b17ead1/regex-2019.01.24.tar.gz (647kB) Collecting tzlocal==1.5.1 (from -r requirements.txt (line 6)) Downloading https://files.pythonhosted.org/packages/cb/89/e3687d3ed99bc882793f82634e9824e62499fdfdc4b1ae39e211c5b05017/tzlocal-1.5.1.tar.gz Collecting umalqurra==0.2 (from -r requirements.txt (line 7)) Downloading https://files.pythonhosted.org/packages/59/d7/d57cfbf2ef0fd5f79c94bb4cc1fdb9af49eba592556e4e6891e2d5522fba/umalqurra-0.2.tar.gz Collecting mock (from -r tests/requirements.txt (line 1)) Downloading https://files.pythonhosted.org/packages/30/6a/9bde648117ec7087c89a45de0a8b25aba21d54d3defd08cb24eacded875f/mock-4.0.1-py3-none-any.whl Requirement already up-to-date: nose in /usr/lib/python3/dist-packages (from -r tests/requirements.txt (line 2)) (1.3.7) Collecting parameterized (from -r tests/requirements.txt (line 3)) Downloading https://files.pythonhosted.org/packages/a3/bf/6ef8239028beae8298e0806b4f79c2466b1b16ca5b85dc13d631c5ea92c4/parameterized-0.7.1-py2.py3-none-any.whl Requirement already up-to-date: six in /usr/lib/python3/dist-packages (from -r tests/requirements.txt (line 4)) (1.14.0) Collecting coverage (from -r tests/requirements.txt (line 5)) Downloading https://files.pythonhosted.org/packages/9a/08/7fa92679a903cac0e01a7fee2cadd92089d96a3002c34e8f2295b80d6b68/coverage-5.0.3-cp37-cp37m-manylinux1_x86_64.whl (227kB) Requirement already satisfied, skipping upgrade: ephem<3.8,>=3.7.5.3 in /usr/lib/python3/dist-packages (from convertdate==2.1.3->-r requirements.txt (line 1)) (3.7.7.0) Building wheels for collected packages: jdatetime, regex, tzlocal, umalqurra Running setup.py bdist_wheel for jdatetime: started Running setup.py bdist_wheel for jdatetime: finished with status 'done' Stored in directory: /home/debci/.cache/pip/wheels/94/3f/63/156126007a5089d65f62ee4e7576ec70200a037b094708322e Running setup.py bdist_wheel for regex: started Running setup.py bdist_wheel for regex: finished with status 'done' Stored in directory: /home/debci/.cache/pip/wheels/ff/8d/55/2ccfa47df2bc65ea83c605075f690c6338a2da89f82c171133 Running setup.py bdist_wheel for tzlocal: started Running setup.py bdist_wheel for tzlocal: finished with status 'done' Stored in directory: /home/debci/.cache/pip/wheels/15/ae/df/a67bf1ed84e9bf230187d36d8dcfd30072bea0236cb059ed91 Running setup.py bdist_wheel for umalqurra: started Running setup.py bdist_wheel for umalqurra: finished with status 'done' Stored in directory: /home/debci/.cache/pip/wheels/d3/e1/d7/d926e5fd2e0cdac728b59661b203670da0b3036f7f096c5324 Successfully built jdatetime regex tzlocal umalqurra Installing collected packages: pytz, convertdate, jdatetime, python-dateutil, regex, tzlocal, umalqurra, mock, parameterized, coverage The scripts coverage, coverage-3.7 and coverage3 are installed in '/home/debci/.local/bin' which is not on PATH. Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location. Successfully installed convertdate-2.1.3 coverage-5.0.3 jdatetime-3.1.0 mock-4.0.1 parameterized-0.7.1 python-dateutil-2.7.5 pytz-2018.9 regex-2019.1.24 tzlocal-1.5.1 umalqurra-0.2
Bug#954134: [d-i bullseye alpha2] installing grub fails
Hi, Am Dienstag, 17. März 2020 schrieb Steve McIntyre: > >Mar 16 09:55:43 main-menu[285]: (process:1258): grub-probe: error: unknown > >filesystem. > > I can see from your log that you're just using ext4 for the new > system, and you're booting in BIOS mode. Any other disks attached to > the system? No, just one SSD. Holger -- Sent from my Jolla phone http://www.jolla.com/
Bug#953832: cannot allocate memory in static TLS block
Hi Faidon, On Tue, Mar 17, 2020 at 01:29:59PM +0200, Faidon Liambotis wrote: > Hi Andreas, > > Thanks for reaching out. It sounds like this is already reported as > #951704 (Cc'ed now). OK. > I'll need to give this a closer look, but I hope I > can have an update within the next couple of weeks. Does this work? Well, drmaa is certainly not the most important package inside Debian so I see no reason to push you. But it would be great to have all those Python3 issues from the table sooner or later since it generated noise for the most active Python 2->3 migrators. Just take the time you need. See you Andreas. -- http://fam-tille.de
Bug#954134: [d-i bullseye alpha2] installing grub fails
Hi Holger, On Tue, Mar 17, 2020 at 11:13:27AM +0100, Holger Wansing wrote: > >Holger Wansing wrote: >> > >> > I will sent installation logs shortly. >> >> Logs attached. > >The relevant part seems to be: ... >Mar 16 09:55:43 main-menu[285]: (process:1258): corrupted size vs. prev_size >Mar 16 09:55:43 main-menu[285]: (process:1258): Aborted Ooh, that's not good. >Mar 16 09:55:43 main-menu[285]: (process:1258): File descriptor 3 >(pipe:[11552]) leaked on lvdisplay invocation. >Mar 16 09:55:43 main-menu[285]: (process:1258): Parent PID 1549: /bin/sh >Mar 16 09:55:43 main-menu[285]: (process:1258): File descriptor 4 (/dev/pts/0) >leaked on lvdisplay invocation. >Mar 16 09:55:43 main-menu[285]: (process:1258): Parent PID 1549: /bin/sh >Mar 16 09:55:43 main-menu[285]: (process:1258): File descriptor 5 (/dev/pts/0) >leaked on lvdisplay invocation. >Mar 16 09:55:43 main-menu[285]: (process:1258): Parent PID 1549: /bin/sh >Mar 16 09:55:43 main-menu[285]: (process:1258): File descriptor 6 (/dev/pts/0) >leaked on lvdisplay invocation. >Mar 16 09:55:43 main-menu[285]: (process:1258): Parent PID 1549: /bin/sh >Mar 16 09:55:43 main-menu[285]: (process:1258): >Mar 16 09:55:43 main-menu[285]: (process:1258): Volume group "sda" not found >Mar 16 09:55:43 main-menu[285]: (process:1258): Cannot process volume group >sda >Mar 16 09:55:43 main-menu[285]: (process:1258): dpkg-divert: warning: >diverting file '/sbin/start-stop-daemon' from an Essential package with rename >is dangerous, use --no-rename >Mar 16 09:55:43 main-menu[285]: (process:1258): corrupted size vs. prev_size >Mar 16 09:55:43 main-menu[285]: (process:1258): Aborted >Mar 16 09:55:43 main-menu[285]: (process:1258): dpkg-divert: warning: >diverting file '/sbin/start-stop-daemon' from an Essential package with rename >is dangerous, use --no-rename >Mar 16 09:55:43 main-menu[285]: (process:1258): grub-probe: error: unknown >filesystem. I can see from your log that you're just using ext4 for the new system, and you're booting in BIOS mode. Any other disks attached to the system? Testing at the weekend didn't show any problems for me or Andy. I'm doing an explicit re-test now so I can check for any of the above messages in my log.s -- Steve McIntyre, Cambridge, UK.st...@einval.com < liw> everything I know about UK hotels I learned from "Fawlty Towers"
Bug#954134: [d-i bullseye alpha2] installing grub fails
On 3/17/20 12:49 PM, Holger Wansing wrote: > However: > >> Mar 16 09:55:43 main-menu[285]: (process:1258): grub-probe: error: unknown >> filesystem. > [...] >> Mar 16 09:55:43 main-menu[285]: (process:1258): corrupted size vs. prev_size >> Mar 16 09:55:43 main-menu[285]: (process:1258): Aborted >> Mar 16 09:55:43 main-menu[285]: WARNING **: Configuring 'grub-installer' >> failed with error code 134 >> Mar 16 09:55:43 main-menu[285]: WARNING **: Menu item 'grub-installer' >> failed. Yes, I have seen that. However, grub-installer is basically a script which invokes grub-install, so I'm not sure where that crash should come from. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#953832: cannot allocate memory in static TLS block
Hi Andreas, Thanks for reaching out. It sounds like this is already reported as #951704 (Cc'ed now). I'll need to give this a closer look, but I hope I can have an update within the next couple of weeks. Does this work? Thanks! Faidon On Sun, Mar 15, 2020 at 10:33:20AM +0100, Andreas Tille wrote: > Hi Faidon, > > could you imagine to build jemalloc with --disable-initial-exec-tls > as Sergio suggests below to fix the issue in drmaa (and possibly other > packages)? > > Should I open a separate bug report against jemalloc to request this? > > Kind regards > > Andreas. > > On Sat, Mar 14, 2020 at 05:18:49PM -0400, Sergio Durigan Junior wrote: > > > $ python3 > > > Python 3.7.6 (default, Jan 19 2020, 22:34:52) > > > [GCC 9.2.1 20200117] on linux > > > Type "help", "copyright", "credits" or "license" for more information. > > import drmaa > > > Traceback (most recent call last): > > > File "", line 1, in > > > File > > > "/home/andreas/debian-maintain/salsa/med-team/python-drmaa/drmaa/__init__.py", > > > line 65, in > > > from .session import JobInfo, JobTemplate, Session > > > File > > > "/home/andreas/debian-maintain/salsa/med-team/python-drmaa/drmaa/session.py", > > > line 39, in > > > from drmaa.helpers import (adapt_rusage, Attribute, > > > attribute_names_iterator, > > > File > > > "/home/andreas/debian-maintain/salsa/med-team/python-drmaa/drmaa/helpers.py", > > > line 36, in > > > from drmaa.wrappers import (drmaa_attr_names_t, drmaa_attr_values_t, > > > File > > > "/home/andreas/debian-maintain/salsa/med-team/python-drmaa/drmaa/wrappers.py", > > > line 58, in > > > _lib = CDLL(libpath, mode=RTLD_GLOBAL) > > > File "/usr/lib/python3.7/ctypes/__init__.py", line 364, in __init__ > > > self._handle = _dlopen(self._name, mode) > > > OSError: /usr/lib/x86_64-linux-gnu/libjemalloc.so.2: cannot allocate > > > memory in static TLS block > > > > This is an issue with jemalloc's handling of the TLS model when being > > dlopened.. See: > > > > https://github.com/jemalloc/jemalloc/issues/1237 > > > > The recommended way to build a libjemalloc that is suitable for being > > dlopened is to use '--disable-initial-exec-tls' when building it. Take > > a look at the INSTALL.md file, and look for this option: > > > > https://github.com/jemalloc/jemalloc/blob/dev/INSTALL.md > > > > There is a way to workaround this bug by doing an LD_PRELOAD of > > libjemalloc when invoking python, but this will only mask the problem > > and we can't expect users to do/know this. > > > > The way I see it, you can try to convince jemalloc's maintainer to > > enable that flag. > > > > BTW, the reason 'find_library' can't find drmaa's library is because the > > .so is being installed in a non-standard directory. I don't know why > > the package was made like this, though. > > > > Thanks, > > > > -- > > Sergio > > GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 > > Please send encrypted e-mail if possible > > http://sergiodj.net/ > > > > -- > http://fam-tille.de >
Bug#954134: [d-i bullseye alpha2] installing grub fails
Hi, Am Dienstag, 17. März 2020 schrieb John Paul Adrian Glaubitz: > On 3/17/20 11:05 AM, Holger Wansing wrote: > > Logs attached. > > grub-installer did not report any problems: > > Mar 16 09:55:41 grub-installer: info: Installing grub on '/dev/sda' > Mar 16 09:55:41 grub-installer: info: grub-install does not support > --no-floppy > Mar 16 09:55:41 grub-installer: info: Running chroot /target grub-install > --force "/dev/sda" > Mar 16 09:55:41 grub-installer: Installing for i386-pc platform. > Mar 16 09:55:42 grub-installer: Installation finished. No error reported. > Mar 16 09:55:42 grub-installer: info: grub-install ran successfully However: > Mar 16 09:55:43 main-menu[285]: (process:1258): grub-probe: error: unknown > filesystem. [...] > Mar 16 09:55:43 main-menu[285]: (process:1258): corrupted size vs. prev_size > Mar 16 09:55:43 main-menu[285]: (process:1258): Aborted > Mar 16 09:55:43 main-menu[285]: WARNING **: Configuring 'grub-installer' > failed with error code 134 > Mar 16 09:55:43 main-menu[285]: WARNING **: Menu item 'grub-installer' failed. -- Sent from my Jolla phone http://www.jolla.com/
Bug#951778: marked as done (libva2: NULL vtable when querying nvidia render device)
Your message dated Tue, 17 Mar 2020 11:19:21 +
with message-id
and subject line Bug#951778: fixed in libva 2.7.0~pre1-1
has caused the Debian Bug report #951778,
regarding libva2: NULL vtable when querying nvidia render device
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.)
--
951778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libva2
Version: 2.6.1-1
Severity: grave
Hi,
It seems that after a recent full-upgrade, querying certain render nodes fails,
crashing my program; it is easily reproducible using vainfo:
gruessi:~> vainfo --display drm --device /dev/dri/renderD129
libva info: VA-API version 1.6.0
vainfo: VA-API version: 1.6 (libva 2.6.0)
vainfo: Driver version:
zsh: segmentation fault vainfo --display drm --device /dev/dri/renderD129
The crash is in
Program received signal SIGSEGV, Segmentation fault.
0x77e254f2 in vaQueryConfigProfiles (dpy=0xd2d0,
profile_list=0xdc10,
num_profiles=0x7fffe92c) at va.c:903
903 va.c: Ingen slik fil eller filkatalog.
(gdb) bt
#0 0x77e254f2 in vaQueryConfigProfiles (dpy=0xd2d0,
profile_list=0xdc10,
num_profiles=0x7fffe92c) at va.c:903
#1 0x64e3 in ?? ()
#2 0x77c73bbb in __libc_start_main (main=0x6370, argc=5,
argv=0x7fffea48,
init=, fini=, rtld_fini=,
stack_end=0x7fffea38)
at ../csu/libc-start.c:308
#3 0x68aa in ?? ()
It seems that somehow, the device is opened but gets a NULL vtable:
(gdb) print *ctx
$2 = {pDriverData = 0x0, vtable = 0x0, vtable_glx = 0x0, vtable_egl = 0x0,
vtable_tpi = 0x0,
native_dpy = 0x0, x11_screen = 0, version_major = 0, version_minor = 0,
max_profiles = 0,
max_entrypoints = 0, max_attributes = 0, max_image_formats = 0,
max_subpic_formats = 0,
max_display_attributes = 0, str_vendor = 0x0, handle = 0x0, drm_state =
0xd2a0, glx = 0x0,
display_type = 49, vtable_wayland = 0x0, vtable_vpp = 0x0,
override_driver_name = 0x0,
pDisplayContext = 0xd2d0, error_callback = 0x77e23540
,
info_callback = 0x77e23560 , reserved = {0
}}
I can query renderD128, which corresponds to my Intel iGPU just fine.
renderD129 corresponds to my RTX 2070:
gruessi:~> cat /sys/class/drm/renderD129/device/vendor
0x10de
gruessi:~> cat /sys/class/drm/renderD129/device/device
0x1f02
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'),
(500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf
Kernel: Linux 5.4.0-4-amd64 (SMP w/6 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8),
LANGUAGE=nb_NO:nb:no_NO:no (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libva2 depends on:
ii libc6 2.29-10
Versions of packages libva2 recommends:
ii i965-va-driver-shaders [va-driver] 2.4.0-1
ii intel-media-va-driver-non-free [va-driver] 19.4.0+ds1-1
ii mesa-va-drivers [va-driver] 19.3.3-1
ii va-driver-all 2.6.1-1
libva2 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libva
Source-Version: 2.7.0~pre1-1
Done: Sebastian Ramacher
We believe that the bug you reported is fixed in the latest version of
libva, 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 951...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sebastian Ramacher (supplier of updated libva package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 17 Mar 2020 11:45:44 +0100
Source: libva
Architecture: source
Version: 2.7.0~pre1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Sebastian Ramacher
Processed: Re: gimp: segmentation fault on startup
Processing control commands: > forcemerge 953880 954095 Bug #953880 [gimp] gimp: segmentation fault on startup Bug #954095 [gimp] [gimp] GIMP fails to boot, with a segmentation fault Merged 953880 954095 > retitle -1 gimp: fatal error: Segmentation fault on startup Bug #953880 [gimp] gimp: segmentation fault on startup Bug #954095 [gimp] [gimp] GIMP fails to boot, with a segmentation fault Changed Bug title to 'gimp: fatal error: Segmentation fault on startup' from 'gimp: segmentation fault on startup'. Changed Bug title to 'gimp: fatal error: Segmentation fault on startup' from '[gimp] GIMP fails to boot, with a segmentation fault'. -- 953880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953880 954095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953880: gimp: segmentation fault on startup
Package: gimp
Version: 2.10.14-2+b1
Followup-For: Bug #953880
Control: forcemerge 953880 954095
Control: retitle -1 gimp: fatal error: Segmentation fault on startup
(gimp:19053): GLib-GObject-CRITICAL **: 12:14:27.292: g_param_spec_internal:
assertion 'is_valid_property_name (name)' failed
gimp: fatal error: Segmentation fault
26 ../sysdeps/unix/sysv/linux/read.c: No such file or directory.
(pagecurl:19083): LibGimpBase-WARNING **: 12:14:29.010: pagecurl:
gimp_wire_read(): error
The workaround to delete /usr/lib/gimp/2.0/plug-ins/pagecurl/pagecurl
(which is shipped by the gimp binary package) works for me.
Full bug info:
```
GNU Image Manipulation Program version 2.10.14
git-describe: GIMP_2_10_12-511-ga4f55d6c7e
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 9.2.1-31'
--with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr
--with-gcc-major-version-only --program-suffix=-9
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib
--with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch
--disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none,hsa --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu --with-build-config=bootstrap-lto-lean
--enable-link-mutex
Thread model: posix
gcc version 9.2.1 20200306 (Debian 9.2.1-31)
using babl version 0.1.74 (compiled against version 0.1.74)
using GEGL version 0.4.22 (compiled against version 0.4.22)
using GLib version 2.64.1 (compiled against version 2.64.0)
using GdkPixbuf version 2.40.0 (compiled against version 2.40.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> fatal error: Segmentation fault
Stack trace:
```
# Stack traces obtained from PID 19053 - Thread 19053 #
[New LWP 19054]
[New LWP 19055]
[New LWP 19057]
[New LWP 19058]
[New LWP 19060]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7ffc401f2c90, fd=13) at
../sysdeps/unix/sysv/linux/read.c:26
Id Target Id Frame
* 1Thread 0x7f12bcbb1e80 (LWP 19053) "gimp" __libc_read (nbytes=256,
buf=0x7ffc401f2c90, fd=13) at ../sysdeps/unix/sysv/linux/read.c:26
2Thread 0x7f12bc8ee700 (LWP 19054) "worker"syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
3Thread 0x7f12b6cd2700 (LWP 19055) "gmain" 0x7f12be7adb0f in
__GI___poll (fds=0x56345c9257c0, nfds=1, timeout=3977) at
../sysdeps/unix/sysv/linux/poll.c:29
4Thread 0x7f12b64d1700 (LWP 19057) "gdbus" 0x7f12be7adb0f in
__GI___poll (fds=0x56345c992720, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
5Thread 0x7f12a8a52700 (LWP 19058) "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
6Thread 0x7f129700 (LWP 19060) "pool-gimp" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 6 (Thread 0x7f129700 (LWP 19060)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7f12bea87ae2 in g_cond_wait_until () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7f12bea0c5d1 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3 0x7f12bea0cbc2 in g_async_queue_timeout_pop () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7f12bea64e19 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5 0x7f12bea6450d in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#6 0x7f12be888f27 in start_thread (arg=) at
pthread_create.c:479
ret =
pd =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139717970491136,
-585757835856207808, 140721384273710, 140721384273711, 139717970487424,
139717970491136, 719388080248954944, 719315122949562432}, mask_was_saved = 0}},
priv = {pad = {0x0, 0x0, 0x0, 0x0}, data =
Processed: Re: Bug#953540: aspectc++: FTBFS on armel
Processing control commands: > tags -1 patch Bug #953540 [src:aspectc++] aspectc++: FTBFS on armel Added tag(s) patch. -- 953540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953540: aspectc++: FTBFS on armel
Control: tags -1 patch On Tue, Mar 10, 2020 at 11:12:16AM +, Ivo De Decker wrote: > package: src:aspectc++ > version: 1:2.2+git20200229-1 > severity: serious > tags: ftbfs > > Hi, > > The latest upload of aspectc++ to unstable fails on armel: > > https://buildd.debian.org/status/package.php?p=aspectc%2B%2B Fix attached. > Cheers, > > Ivo cu Adrian Description: Link with libatomic when needed Author: Adrian Bunk Bug-Debian: https://bugs.debian.org/953540 --- aspectc++-2.2+git20200229.orig/AspectC++/Makefile +++ aspectc++-2.2+git20200229/AspectC++/Makefile @@ -63,7 +63,7 @@ endif LDFLAGS += $(LIBXML2_LIB) ifneq ($(FRONTEND),Puma) ifneq ($(_TARGET),macosx_x86_64) - LDFLAGS += -lclangRewriteFrontend -lclangRewrite -lclangFrontend -lclangSerialization -lclangDriver -lclangParse -lclangSema -lclangAnalysis -lclangEdit -lclangAST -lclangLex -lclangBasic -lLLVMAsmParser -lLLVMMCParser -lLLVMBitReader -lLLVMTransformUtils -lLLVMCore -lLLVMMC -lLLVMOption -lLLVMSupport + LDFLAGS += -lclangRewriteFrontend -lclangRewrite -lclangFrontend -lclangSerialization -lclangDriver -lclangParse -lclangSema -lclangAnalysis -lclangEdit -lclangAST -lclangLex -lclangBasic -lLLVMAsmParser -lLLVMMCParser -lLLVMBitReader -lLLVMTransformUtils -lLLVMCore -lLLVMMC -lLLVMOption -lLLVMSupport -Wl,--as-needed -latomic -Wl,--no-as-needed ifneq ($(filter 9.0%, $(LLVM_VERSION)),) LDFLAGS += -lLLVMBitstreamReader -lLLVMBinaryFormat -lLLVMRemarks -lLLVMProfileData -lLLVMSupport -lLLVMDemangle endif
Bug#954134: [d-i bullseye alpha2] installing grub fails
On 3/17/20 11:05 AM, Holger Wansing wrote: > Logs attached. grub-installer did not report any problems: Mar 16 09:55:41 grub-installer: info: Installing grub on '/dev/sda' Mar 16 09:55:41 grub-installer: info: grub-install does not support --no-floppy Mar 16 09:55:41 grub-installer: info: Running chroot /target grub-install --force "/dev/sda" Mar 16 09:55:41 grub-installer: Installing for i386-pc platform. Mar 16 09:55:42 grub-installer: Installation finished. No error reported. Mar 16 09:55:42 grub-installer: info: grub-install ran successfully Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#954134: [d-i bullseye alpha2] installing grub fails
Hi, Holger Wansing wrote: > > > > I will sent installation logs shortly. > > Logs attached. The relevant part seems to be: Mar 16 09:55:41 grub-installer: info: Installing grub on '/dev/sda' Mar 16 09:55:41 grub-installer: info: grub-install does not support --no-floppy Mar 16 09:55:41 grub-installer: info: Running chroot /target grub-install --force "/dev/sda" Mar 16 09:55:41 grub-installer: Installing for i386-pc platform. Mar 16 09:55:42 grub-installer: Installation finished. No error reported. Mar 16 09:55:42 grub-installer: info: grub-install ran successfully Mar 16 09:55:42 in-target: Reading package lists... Mar 16 09:55:42 in-target: Mar 16 09:55:42 in-target: Building dependency tree... Mar 16 09:55:42 in-target: Mar 16 09:55:42 in-target: Reading state information... Mar 16 09:55:42 in-target: Mar 16 09:55:42 in-target: grub-common is already the newest version (2.04-5). Mar 16 09:55:42 in-target: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Mar 16 09:55:43 main-menu[285]: (process:1258): dpkg-divert: warning: diverting file '/sbin/start-stop-daemon' from an Essential package with rename is dangerous, use --no-rename Mar 16 09:55:43 main-menu[285]: (process:1258): dpkg-divert: warning: diverting file '/sbin/start-stop-daemon' from an Essential package with rename is dangerous, use --no-rename Mar 16 09:55:43 main-menu[285]: (process:1258): corrupted size vs. prev_size Mar 16 09:55:43 main-menu[285]: (process:1258): Aborted Mar 16 09:55:43 main-menu[285]: (process:1258): File descriptor 3 (pipe:[11552]) leaked on lvdisplay invocation. Mar 16 09:55:43 main-menu[285]: (process:1258): Parent PID 1549: /bin/sh Mar 16 09:55:43 main-menu[285]: (process:1258): File descriptor 4 (/dev/pts/0) leaked on lvdisplay invocation. Mar 16 09:55:43 main-menu[285]: (process:1258): Parent PID 1549: /bin/sh Mar 16 09:55:43 main-menu[285]: (process:1258): File descriptor 5 (/dev/pts/0) leaked on lvdisplay invocation. Mar 16 09:55:43 main-menu[285]: (process:1258): Parent PID 1549: /bin/sh Mar 16 09:55:43 main-menu[285]: (process:1258): File descriptor 6 (/dev/pts/0) leaked on lvdisplay invocation. Mar 16 09:55:43 main-menu[285]: (process:1258): Parent PID 1549: /bin/sh Mar 16 09:55:43 main-menu[285]: (process:1258): Mar 16 09:55:43 main-menu[285]: (process:1258): Volume group "sda" not found Mar 16 09:55:43 main-menu[285]: (process:1258): Cannot process volume group sda Mar 16 09:55:43 main-menu[285]: (process:1258): dpkg-divert: warning: diverting file '/sbin/start-stop-daemon' from an Essential package with rename is dangerous, use --no-rename Mar 16 09:55:43 main-menu[285]: (process:1258): corrupted size vs. prev_size Mar 16 09:55:43 main-menu[285]: (process:1258): Aborted Mar 16 09:55:43 main-menu[285]: (process:1258): dpkg-divert: warning: diverting file '/sbin/start-stop-daemon' from an Essential package with rename is dangerous, use --no-rename Mar 16 09:55:43 main-menu[285]: (process:1258): grub-probe: error: unknown filesystem. Mar 16 09:55:43 main-menu[285]: (process:1258): dpkg-divert: warning: diverting file '/sbin/start-stop-daemon' from an Essential package with rename is dangerous, use --no-rename Mar 16 09:55:43 main-menu[285]: (process:1258): dpkg-divert: warning: diverting file '/sbin/start-stop-daemon' from an Essential package with rename is dangerous, use --no-rename Mar 16 09:55:43 main-menu[285]: (process:1258): corrupted size vs. prev_size Mar 16 09:55:43 main-menu[285]: (process:1258): Aborted Mar 16 09:55:43 main-menu[285]: WARNING **: Configuring 'grub-installer' failed with error code 134 Mar 16 09:55:43 main-menu[285]: WARNING **: Menu item 'grub-installer' failed. Mar 16 09:55:44 main-menu[285]: INFO: Modifying debconf priority limit from 'high' to 'medium' Mar 16 09:55:44 debconf: Setting debconf/priority to medium -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#954134: [d-i bullseye alpha2] installing grub fails
Holger Wansing wrote: > > I will sent installation logs shortly. Logs attached. -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076 installer.tar.gz Description: application/gzip
Processed: Re: Bug#954129: gucharmap: build depends on unicode-data (< 12.2) but 13.0.0-2 is to be installed
Processing control commands: > tags -1 + fixed-upstream Bug #954129 [src:gucharmap] gucharmap: build depends on unicode-data (< 12.2) but 13.0.0-2 is to be installed Added tag(s) fixed-upstream. -- 954129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954129: gucharmap: build depends on unicode-data (< 12.2) but 13.0.0-2 is to be installed
Control: tags -1 + fixed-upstream On Tue, 17 Mar 2020 at 11:48:16 +0200, Adrian Bunk wrote: > The following packages have unmet dependencies: > builddeps:gucharmap : Depends: unicode-data (< 12.2) but 13.0.0-2 is to be > installed gucharmap needs to be upgraded in lockstep with unicode-data. There's a new upstream version available, but it hasn't been packaged yet (the GNOME team has been busy with the rest of GNOME 3.36). smcv
Bug#954133: python-acme build depends on python3-idna (< 2.8) but 2.8-1 is to be installed
Source: python-acme Version: 1.1.0-1 Severity: serious Tags: ftbfs The following packages have unmet dependencies: builddeps:python-acme : Depends: python3-idna (< 2.8) but 2.8-1 is to be installed
Bug#954134: [d-i bullseye alpha2] installing grub fails
Package: debian-installer Severity: grave While testing the alpha2 netinst image on a spare Thinkpad, I found that grub cannot be installed successfully (and rebooting into the new installation fails as well). This was ok in alpha1. This might look like an grub-installer issue, however there were only trivial installation update releases since alpha1, so I suspect it's not in issue in grub-installer. Therefore I file this against debian-installer. I will sent installation logs shortly. Holger -- Holger Wansing PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#954132: wine build depends on unicode-data (< 13) but 13.0.0-2 is to be installed
Source: wine Version: 5.0-3 Severity: serious Tags: ftbfs The following packages have unmet dependencies: builddeps:wine : Depends: unicode-data (< 13) but 13.0.0-2 is to be installed
Bug#953958: Bug#953562: libcrypt1 should ship file in /usr, breaks is useless
On Tue, 17 Mar 2020 10:26:17 +0100 Markus Steinko wrote: > Dear maintainer, > > downgrading a system from bullseye to buster (via apt-pinning) was kind > of impossible (due to removal of libcrypt.so.1 and unresolved > dependencies of libc-bin and libc6, I think) when I was facing the bug > for the first time and I was not being logged in as root within an active > terminal. Copying the content of the extracted > libcrypt1_4.4.15-1_amd64.deb file to its destination helped to get it > fixed. > > `cp /libcrypt1_4.4.15-1_amd64/data/usr/lib/x86_64-linux-gnu/. > /usr/lib/x86_64-linux-gnu/` > > Regards, > > Markus > > > Oops, I made a mistake when posting this, due to reading through two open browser tabs: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953562 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953958 That's why the subject is not set correct. Sorry.
Processed: tagging 954114
Processing commands for cont...@bugs.debian.org: > tags 954114 + ftbfs Bug #954114 [src:wine-development] wine-development: build-dependencies unsatisfiable. Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 954114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954130: libxmlada build depends on unicode-data (< 13~) but 13.0.0-2 is to be installed
Source: libxmlada Version: 19-2 Severity: serious Tags: ftbfs The following packages have unmet dependencies: builddeps:libxmlada : Depends: unicode-data (< 13~) but 13.0.0-2 is to be installed
Bug#954131: utf8proc build depends on unicode-data (< 12.2) but 13.0.0-2 is to be installed
Source: utf8proc Version: 2.4.0-2 Severity: serious Tags: ftbfs The following packages have unmet dependencies: builddeps:utf8proc : Depends: unicode-data (< 12.2) but 13.0.0-2 is to be installed
Bug#954129: gucharmap: build depends on unicode-data (< 12.2) but 13.0.0-2 is to be installed
Source: gucharmap Version: 1:12.0.1-2 Severity: serious Tags: ftbfs The following packages have unmet dependencies: builddeps:gucharmap : Depends: unicode-data (< 12.2) but 13.0.0-2 is to be installed
Bug#953958: Bug#953562: libcrypt1 should ship file in /usr, breaks is useless
Dear maintainer, downgrading a system from bullseye to buster (via apt-pinning) was kind of impossible (due to removal of libcrypt1.so and unresolved dependencies of libc-bin and libc6, I think) when I was facing the bug for the first time and I not being logged in as root within an active terminal. Copying the content of the extracted libcrypt1_4.4.15-1_amd64.deb file to its destination helped to get it fixed. `cp /libcrypt1_4.4.15-1_amd64/data/usr/lib/x86_64-linux-gnu/. /usr/lib/x86_64-linux-gnu/` Regards, Markus
