Processed: severity of 955317 is normal, retitle 955317 to support multiple Python versions
Processing commands for cont...@bugs.debian.org: > severity 955317 normal Bug #955317 [src:ros-ros-comm] ros-ros-comm: autopkgtest regression: No rule to make target '/usr/lib/x86_64-linux-gnu/libpython3.8.so' Severity set to 'normal' from 'serious' > retitle 955317 support multiple Python versions Bug #955317 [src:ros-ros-comm] ros-ros-comm: autopkgtest regression: No rule to make target '/usr/lib/x86_64-linux-gnu/libpython3.8.so' Changed Bug title to 'support multiple Python versions' from 'ros-ros-comm: autopkgtest regression: No rule to make target '/usr/lib/x86_64-linux-gnu/libpython3.8.so''. > thanks Stopping processing here. Please contact me if you need assistance. -- 955317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954977: "Daily Limit Exceeded" connection error
Package: evolution Version: 3.36.0-1 Followup-For: Bug #954977 This is happening to me daily in evolution. When it does I am unable to use evolution email or calendar. The message I'm getting is: Daily Limit Exceeded. The quota will be reset at midnight Pacific Time (PT). You may monitor your quota usage and adjust limits in the API Console: https://console.developers.google.com/apis/api/caldav.googleapis.com/quotas?project=44438659992 Let me know if there is anything I can do to help troubleshoot this. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (800, 'testing'), (700, 'unstable'), (600, 'experimental'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages evolution depends on: ii dbus 1.12.16-2 ii evolution-common 3.36.0-1 ii evolution-data-server 3.36.0-1 ii libc6 2.30-2 ii libcamel-1.2-623.36.0-1 ii libclutter-gtk-1.0-0 1.8.4-4 ii libecal-2.0-1 3.36.0-1 ii libedataserver-1.2-24 3.36.0-1 ii libevolution 3.36.0-1 ii libglib2.0-0 2.64.1-1 ii libgtk-3-0 3.24.14-1 ii libical3 3.0.8-1 ii libnotify4 0.7.9-1 ii libsoup2.4-1 2.70.0-1 ii libwebkit2gtk-4.0-37 2.28.0-2 ii libxml22.9.10+dfsg-4 ii psmisc 23.3-1 Versions of packages evolution recommends: ii evolution-plugin-bogofilter 3.36.0-1 ii evolution-plugin-pstimport 3.36.0-1 ii evolution-plugins3.36.0-1 ii yelp 3.34.0-1 Versions of packages evolution suggests: pn evolution-ews pn evolution-plugins-experimental ii gnupg 2.2.20-1 ii network-manager 1.22.6-1 -- debconf-show failed
Bug#953086: marked as done (samba: uninstallable, depends on unavailable python3 version <3.8 while 3.8.2-1 is available)
Your message dated Tue, 31 Mar 2020 06:48:40 +0100 with message-id and subject line re: samba: uninstallable, depends on unavailable python3 version <3.8 while 3.8.2-1 is available has caused the Debian Bug report #953086, regarding samba: uninstallable, depends on unavailable python3 version <3.8 while 3.8.2-1 is available 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.) -- 953086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: samba Version: 2:4.11.5+dfsg-1 Severity: serious Hi, samba is currently uninstallable in unstable/sid, due to: | The following packages have unmet dependencies: | samba : Depends: python3 (< 3.8) but 3.8.2-1 is to be installed | Depends: python3-samba but it is not going to be installed | Depends: samba-common-bin (= 2:4.11.5+dfsg-1) but it is not going to be installed | Depends: samba-libs (= 2:4.11.5+dfsg-1) but it is not going to be installed | Recommends: attr but it is not going to be installed | Recommends: python3-markdown but it is not going to be installed | Recommends: samba-dsdb-modules but it is not going to be installed | Recommends: samba-vfs-modules but it is not going to be installed | E: Unable to correct problems, you have held broken packages. regards -mika- --- End Message --- --- Begin Message --- Samba has been rebuilt against python 3.8 on all Debian release architectures (and most of the debian-ports ones too)--- End Message ---
Bug#954582: samba: FTBFS glibc/stropts/python issue.
On Tue, 2020-03-31 at 02:09 +0100, peter green wrote: > The samba FTBFS is blocking the python 3.8 transition in raspbian > bullseye, so I decided to take a look. Thanks for digging into this. I've updated the Samba bug below, and I think this is a Python bug and needs to be fixed in Python. The correct fix is for Python not to leak these defines. Andrew Bartlett -- Andrew Bartlett https://samba.org/~abartlet/ Authentication Developer, Samba Team https://samba.org Samba Developer, Catalyst IT https://catalyst.net.nz/services/samba
Bug#951101: marked as done (cracklib2 FTBFS: debian/rules:6: /usr/share/python/python.mk: No such file or directory)
Your message dated Tue, 31 Mar 2020 05:18:29 + with message-id and subject line Bug#951101: fixed in cracklib2 2.9.6-3.2 has caused the Debian Bug report #951101, regarding cracklib2 FTBFS: debian/rules:6: /usr/share/python/python.mk: 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.) -- 951101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cracklib2 Version: 2.9.6-3.1 Severity: serious Tags: patch ftbfs cracklib2 fails to build from source, because debian/rules includes a non-existent python.mk file: | debian/rules:6: /usr/share/python/python.mk: No such file or directory The file should be /usr/share/python3/python.mk now and it should be conditional to the nopython profile. Please consider applying the attached patch. Helmut diff --minimal -Nru cracklib2-2.9.6/debian/changelog cracklib2-2.9.6/debian/changelog --- cracklib2-2.9.6/debian/changelog2019-11-19 16:14:51.0 +0100 +++ cracklib2-2.9.6/debian/changelog2020-02-11 07:09:52.0 +0100 @@ -1,3 +1,10 @@ +cracklib2 (2.9.6-3.2) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS with missing python.mk. (Closes: #-1) + + -- Helmut Grohne Tue, 11 Feb 2020 07:09:52 +0100 + cracklib2 (2.9.6-3.1) unstable; urgency=high * Non-maintainer upload. diff --minimal -Nru cracklib2-2.9.6/debian/rules cracklib2-2.9.6/debian/rules --- cracklib2-2.9.6/debian/rules2019-11-19 16:14:51.0 +0100 +++ cracklib2-2.9.6/debian/rules2020-02-11 07:09:50.0 +0100 @@ -3,13 +3,13 @@ DEB_BUILD_MAINT_OPTIONS = hardening=+all DPKG_EXPORT_BUILDFLAGS = 1 include /usr/share/dpkg/buildflags.mk -include /usr/share/python/python.mk # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 include /usr/share/dpkg/architecture.mk ifeq ($(filter stage1,$(DEB_STAGE))$(filter nopython,$(DEB_BUILD_PROFILES)),) +include /usr/share/python3/python.mk PY3VERS := $(shell py3versions -vs) DH_WITH_PARAMETERS := python3 else --- End Message --- --- Begin Message --- Source: cracklib2 Source-Version: 2.9.6-3.2 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of cracklib2, 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. Peter Michael Green (supplier of updated cracklib2 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, 31 Mar 2020 04:24:12 + Source: cracklib2 Architecture: source Version: 2.9.6-3.2 Distribution: unstable Urgency: medium Maintainer: Jan Dittberner Changed-By: Peter Michael Green Closes: 951101 Changes: cracklib2 (2.9.6-3.2) unstable; urgency=medium . * Non-maintainer upload. [Helmut Grohne] * Fix FTBFS with missing python.mk. (Closes: #951101) Checksums-Sha1: 6f759fc96f663f17bf22f97239506a0bb4875134 2480 cracklib2_2.9.6-3.2.dsc fd3da0b4c45923ed11965527951cefa5ff91eb9d 26988 cracklib2_2.9.6-3.2.debian.tar.xz 35cfda91042a48b69af67d1b89acdeb4ea616778 8938 cracklib2_2.9.6-3.2_source.buildinfo Checksums-Sha256: b61ea17de08a27ac377491691aad406468bc531be4fa21c4270d6938777c2bad 2480 cracklib2_2.9.6-3.2.dsc 60a848dfdbd848971201e5faadc0901b5599ee3b9be3ba136afb8d192ba5e0bd 26988 cracklib2_2.9.6-3.2.debian.tar.xz 1210bee9a27e046f565387a74d9ff770845facaa546192d8c9bbcbf99b29144d 8938 cracklib2_2.9.6-3.2_source.buildinfo Files: fec7615e43add512e7a4bf6ad992 2480 libs optional cracklib2_2.9.6-3.2.dsc b76dc91b674923a932c524f71d4f3dc4 26988 libs optional cracklib2_2.9.6-3.2.debian.tar.xz 5e52e3f357957c99181cae8cc148c1e8 8938 libs optional cracklib2_2.9.6-3.2_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAl6Czd4UHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/XtfNQ/+NpnQ4mg0Xndy+2nU7cuT/vLA93WA NluoTWaSs5DHePPpH+bcvFZuIVE8KBAtRaWetovA6pUxVocsGmdXGs+7eaUZjhm8 UucQt3+vPdN3SL47pmo4uzwSa3mAoxszNEuKif5N/fku2auX9WvGb/iqdaDGPU7b AAq/QDSCn5TsTsCD37m1/VjsO0gc31TE63E1I1QpAhym6vPJzhW+b8D8UmxDeclR Vz0rMe7nWJJCToDiyjwyEIecTsMDqDBLYAleNVc
Bug#951101: cracklib2 FTBFS: debian/rules:6: /usr/share/python/python.mk: No such file or directory
Since this bug had no maintainer response for a month I decided to go ahead with a NMU, the debdiff is attatched (same as helmuts other than changelog tweaks). diff -Nru cracklib2-2.9.6/debian/changelog cracklib2-2.9.6/debian/changelog --- cracklib2-2.9.6/debian/changelog2019-11-19 15:14:51.0 + +++ cracklib2-2.9.6/debian/changelog2020-03-31 04:24:12.0 + @@ -1,3 +1,11 @@ +cracklib2 (2.9.6-3.2) unstable; urgency=medium + + * Non-maintainer upload. + [Helmut Grohne] + * Fix FTBFS with missing python.mk. (Closes: #951101) + + -- Peter Michael Green Tue, 31 Mar 2020 04:24:12 + + cracklib2 (2.9.6-3.1) unstable; urgency=high * Non-maintainer upload. diff -Nru cracklib2-2.9.6/debian/rules cracklib2-2.9.6/debian/rules --- cracklib2-2.9.6/debian/rules2019-11-19 15:14:51.0 + +++ cracklib2-2.9.6/debian/rules2020-03-31 04:24:10.0 + @@ -3,13 +3,13 @@ DEB_BUILD_MAINT_OPTIONS = hardening=+all DPKG_EXPORT_BUILDFLAGS = 1 include /usr/share/dpkg/buildflags.mk -include /usr/share/python/python.mk # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 include /usr/share/dpkg/architecture.mk ifeq ($(filter stage1,$(DEB_STAGE))$(filter nopython,$(DEB_BUILD_PROFILES)),) +include /usr/share/python3/python.mk PY3VERS := $(shell py3versions -vs) DH_WITH_PARAMETERS := python3 else
Bug#953780: src:zip4j: fails to migrate to testing for too long
Hi Paul, On 2020-03-30 21:53, Paul Gevers wrote: > That assumption is wrong. Closure is done by either a "Closes" in the > changelog or by manual sending a message to bug-done, like I've done > now. Probably someone doing QA on the BTS would have closed it in due > time as the bug impacts no release anymore, but it's unnecessary to wait > for that. Thanks for explanation. I assumed there was a migration trigger for automatic bug closure which did not activate this time. I was wrong. Next time I will close the bug via "Closes" or bug-done. Best wishes, Andrius signature.asc Description: OpenPGP digital signature
Bug#951040: marked as done (python-yubico-tools: Depends: python3-argparse but it is not installable)
Your message dated Tue, 31 Mar 2020 04:36:02 + with message-id and subject line Bug#951040: fixed in python-yubico 1.3.3-0.3 has caused the Debian Bug report #951040, regarding python-yubico-tools: Depends: python3-argparse but it is not installable 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.) -- 951040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-yubico-tools Version: 1.3.3-0.2 Severity: serious Control: block 938283 by -1 The following packages have unmet dependencies: python-yubico-tools : Depends: python3-argparse but it is not installable --- End Message --- --- Begin Message --- Source: python-yubico Source-Version: 1.3.3-0.3 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of python-yubico, 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. Timo Aaltonen (supplier of updated python-yubico 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, 31 Mar 2020 07:00:00 +0300 Source: python-yubico Architecture: source Version: 1.3.3-0.3 Distribution: unstable Urgency: medium Maintainer: Debian Authentication Maintainers Changed-By: Timo Aaltonen Closes: 951040 Changes: python-yubico (1.3.3-0.3) unstable; urgency=medium . * Non-maintainer upload. * control: Drop python3-argparse from depends, it's provided by libpython. (Closes: #951040) Checksums-Sha1: 11a372883f077da13dca80e3051b0c7c56513fda 2464 python-yubico_1.3.3-0.3.dsc bfc0e9f74390f676015709710fdd1dda7c10ba24 8512 python-yubico_1.3.3-0.3.debian.tar.xz 88ed8910d72b3e1d6e76047b8467353d39ccebd0 7164 python-yubico_1.3.3-0.3_source.buildinfo Checksums-Sha256: 99e6d6db2469de9aaaf57b464a56bf8ef1e9cdcdf8a80d0aeb9d841a9273765b 2464 python-yubico_1.3.3-0.3.dsc cc0799891b4ce5beb01229c4d585e38fc1941ec2312b19d9a0c3fc4fad31c968 8512 python-yubico_1.3.3-0.3.debian.tar.xz 549e1140d691d47c556e4b0b303d4e9ee8f909c6885cf17292ecbd89e2937ef8 7164 python-yubico_1.3.3-0.3_source.buildinfo Files: 6e7a39f4864401b67d939a1e800ee0b6 2464 python optional python-yubico_1.3.3-0.3.dsc 530eb97c1c23a42d31e42cc586c841b1 8512 python optional python-yubico_1.3.3-0.3.debian.tar.xz f693fa56d7723ab638f72547f24567ae 7164 python optional python-yubico_1.3.3-0.3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAl6CxC0ACgkQy3AxZaiJ hNxRRw//ZrTE3v5FAvhFfkgtR/qed5u0/yOFpR6uPbv4NFuNgtq08Vba+9H3mmZV iK8O5xfmfM6WsJQaKwZBbrdeBi5OlQJx8b36lkm5bPvFmZ/S3cQi2VBb6qmwrQ1J /Qa4nr0LmyvfitsNzu9giW7AdUYxdh1862CMzMcVKrxS6mphA5UJCqBoTjYuVRkU TxUeUJCCE9wBkcT99WkRfsOMKEU3zWTzL2SoNKQOITLmWYqR2GtRjw1Ds2kqKMzX e4Pk6qw+Ar/2hT1Rm1S0nEIuKefCYJaW9kH7CpNzA0ZS0TH61eH/9c6FeaNdGcrw eK2Lh1knk+3Am6opLMcVyHMZziMEtzzilJxRV2CZQqlfdyJXL8QAXodFoX7WdvYD UeMSM4/fIhnNrQ00TGoYGi1JjnUEds+GDxitlh/mevq0KZFT3U1zP8zad4J7w6y7 3tT1/ouyc3J+7mjrWDm5drIgp+5FJ7Gu+lCI0g9lJZHVp7uVVjOpBcsgz/vsbt1m 5I5w7DYIwt3qUu/V1ySH8E95QMeQBHXPgGRNKjIz9ZxgH/nSis+0dRVSJDEFymyB es695vpGZO1RhdC88Kzr1WRV584g1VAwLqdhKW6fRMivP64r7rGZi6MhcNKU9KtW wzhw1uMTMsX4V5r2FROFbXEhf72P1f24sDJMEvZuattPf41dcM4= =mBi3 -END PGP SIGNATURE End Message ---
Bug#954582: samba: FTBFS glibc/stropts/python issue.
If my understanding is correct I see two possible ways forward. 1. Rebuild python3.8 against the new glibc. 2. Remove the stropts include from samba, it doesn't seem to actually be used for anything (at least I can't find any other references to HAVE_STROPTS_H in the code). I am currently testing a build in raspbian bullseye with the second approach. I will report back later on whether it results in a succesful build. This build was successful and I uploaded it to raspbian, a debdiff should appear soon at https://debdiffs.raspbian.org/main/s/samba . No intent to NMU in Debian.
Bug#954587: marked as done (yp-tools: FTBFS: nis-hosts.c:232:21: error: ‘RES_USE_INET6’ undeclared (first use in this function))
Your message dated Tue, 31 Mar 2020 03:50:14 + with message-id and subject line Bug#954587: fixed in yp-tools 3.3-5.3 has caused the Debian Bug report #954587, regarding yp-tools: FTBFS: nis-hosts.c:232:21: error: ‘RES_USE_INET6’ undeclared (first use in this function) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 954587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954587 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yp-tools Version: 3.3-5.2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200321 ftbfs-bullseye 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=compile gcc -DHAVE_CONFIG_H -I. -I.. > -I. -I../lib -I/usr/include/tirpc -Wdate-time -D_FORTIFY_SOURCE=2 > -D_REENTRANT=1 -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -c -o nis-hosts.lo > nis-hosts.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I. -I../lib > -I/usr/include/tirpc -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT=1 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c nis-hosts.c -fPIC -DPIC -o .libs/nis-hosts.o > In file included from nis-hosts.c:54: > nis-hosts.c: In function ‘parse_line’: > nis-hosts.c:70:5: warning: implicit declaration of function > ‘map_v4v6_address’ [-Wimplicit-function-declaration] >70 | map_v4v6_address ((char *) entdata->host_addr, > | ^~~~ > files-parse.c:110:3: note: in definition of macro ‘LINE_PARSER’ > 110 | BODY; \ > | ^~~~ > nis-hosts.c: In function ‘_nss_nis6_gethostent_r’: > nis-hosts.c:232:21: error: ‘RES_USE_INET6’ undeclared (first use in this > function) > 232 |((_res.options & RES_USE_INET6) ? AF_INET6 : AF_INET), > | ^ > nis-hosts.c:232:21: note: each undeclared identifier is reported only once > for each function it appears in > nis-hosts.c: In function ‘_nss_nis6_gethostbyname2_r’: > nis-hosts.c:352:21: error: ‘RES_USE_INET6’ undeclared (first use in this > function) > 352 |((_res.options & RES_USE_INET6) ? AI_V4MAPPED : 0)); > | ^ > nis-hosts.c: In function ‘_nss_nis6_gethostbyname_r’: > nis-hosts.c:360:22: error: ‘RES_USE_INET6’ undeclared (first use in this > function) > 360 | if (_res.options & RES_USE_INET6) > | ^ > nis-hosts.c: In function ‘_nss_nis6_gethostbyaddr_r’: > nis-hosts.c:434:27: error: ‘RES_USE_INET6’ undeclared (first use in this > function) > 434 | ((_res.options & RES_USE_INET6) > | ^ > make[3]: *** [Makefile:508: nis-hosts.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/03/21/yp-tools_3.3-5.2_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: yp-tools Source-Version: 3.3-5.3 Done: Sudip Mukherjee We believe that the bug you reported is fixed in the latest version of yp-tools, 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. Sudip Mukherjee (supplier of updated yp-tools 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: Mon, 30 Mar 2020 18:58:41 +0100 Source: yp-tools Architecture: source Version: 3.3-5.3 Distribution: unstable Urgency: medium Maintainer: Mark Brown Changed-By: Sudip Mukherjee Closes: 954587 Changes: yp-tools (3.3-5.3) unstable; urgency=medium . * Non-maintainer upload. * Fix FTBFS for RES_USE_INET6. (Closes: #954587) Checksums-Sha1: 14b2fa20aa2bc6330014182062b4369963fa
Bug#934949: marked as done (clips: build-depends on removed package pdf2htmlex)
Your message dated Tue, 31 Mar 2020 03:48:41 + with message-id and subject line Bug#934949: fixed in clips 6.30-4.1 has caused the Debian Bug report #934949, regarding clips: build-depends on removed package pdf2htmlex 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.) -- 934949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934949 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clips Version: pdf2htmlex Severity: serious Version: 6.30-4 User: trei...@debian.org Usertags: edos-uninstallable Hi, clips build-depends on pdf2htmlex which was removed from unstable on 2019-04-01. -Ralf --- End Message --- --- Begin Message --- Source: clips Source-Version: 6.30-4.1 Done: =?utf-8?q?H=C3=A5vard_Flaget_Aasen?= We believe that the bug you reported is fixed in the latest version of clips, 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 934...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Håvard Flaget Aasen (supplier of updated clips 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: Mon, 30 Mar 2020 20:51:48 +0200 Source: clips Architecture: source Version: 6.30-4.1 Distribution: unstable Urgency: medium Maintainer: Javier Fernández-Sanguino Peña Changed-By: Håvard Flaget Aasen Closes: 881009 934949 952621 Changes: clips (6.30-4.1) unstable; urgency=medium . * Non-maintainer upload. * Fix typo in maintainer address closes: #881009 * Don't build html files in doc package, so we can remove pdf2htmlex as build-dependency. closes: #952621, #934949 - Remove Format: HTML in *.doc-base files - Edit Makefile in clips_docs.diff Checksums-Sha1: 1554266a9610c281c57f871e5a56a5f53464459b 1961 clips_6.30-4.1.dsc 93307a8e46690410631a3f1c586602c3f05e67ba 21905444 clips_6.30-4.1.debian.tar.xz 2eff80fe4297aead194813babecfdbe1d9894ad3 5382 clips_6.30-4.1_source.buildinfo Checksums-Sha256: 17e5b6acb7bce0579cc094387ada5d56089d9035a70f9cce6181b5826fff9d00 1961 clips_6.30-4.1.dsc cf784ccd30e41668a64ba062183d99e47ba3c365caed80dcaabe880509a1ff8f 21905444 clips_6.30-4.1.debian.tar.xz d694d34b061b7f0f4d63f9b562bbf0b4790a4d569cb21390055129d4f9f4292d 5382 clips_6.30-4.1_source.buildinfo Files: 2c3327b87540a2625d1806478c437254 1961 interpreters optional clips_6.30-4.1.dsc 1e319b1c544adbdf29210eac76498a7e 21905444 interpreters optional clips_6.30-4.1.debian.tar.xz 4a60c86bfcc7c352091911e435271932 5382 interpreters optional clips_6.30-4.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl6CuEcACgkQweDZLphv fH5PJA/9HvQj/KD/WXtk+te6YOzsc+00kAKgVoVfj8cExd40AoM5YkM+8v0sTJ6w BrtvrboW/YDuXfPcD0IucPNW+j6MvfDpdw8Zo/fRdbKFNQcbvGR17jHJP2hT9oBy bpbisqdBxc6D6tFItPI2WZquOC8pyFK6LMCXQ7hzdqt9k3klABenV50pTJTz9TcF nS8uENBZPpSpoHhQD4QEihaDT6e+eeqIwb7Q4+UkvHhpKBaUWR9ks1nhxRZ2/yOi fsbmZLOqRF07+y+GHsULfSMbUhHT1JYDZffhFiWjZ+IT32FPqGy9firLivKgRDYy bVi1yjFm6I1Lx/8rMB9qlYkhPv4bQMzxCtBHBnlA2LBUVPic6OHaSgpwKhW6DqPj ruiw0RD5n9C1DQqJkTWa8irEFou4Aqwgvw6NTNdXn5u8rBC6pWdDeS3rHcmBEwzm 3E51KPh+ZsdGe/MqluQ9MDD6vml4LRvBHCu4p3v0zmGTvgFbkrUVQNpW03tnn84r QVbu4YviipQffiiqvjEOfXVin53hbV5JHUiVN5Cq8p5M5t+BciFHBqAVx1qN1qyR dvOmqZaL85Hsm+Z9PSyHEBUAYuCJAqVZ471sUEM5qlqmXxfLq9CVymfwBkxjNC2D ggekmkjoExeACnsILCveRO+w4HKYlxp38U+jR8BZa4qYSMDSMzw= =vnXa -END PGP SIGNATURE End Message ---
Bug#952621: marked as done (clips: FTBFS: build-dependency not installable: pdf2htmlex)
Your message dated Tue, 31 Mar 2020 03:48:41 + with message-id and subject line Bug#952621: fixed in clips 6.30-4.1 has caused the Debian Bug report #952621, regarding clips: FTBFS: build-dependency not installable: pdf2htmlex 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.) -- 952621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952621 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clips Version: 6.30-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200225 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules). Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: libncurses-dev, debhelper (>= 10~), pdf2htmlex, > sharutils, build-essential, fakeroot > Filtered Build-Depends: libncurses-dev, debhelper (>= 10~), pdf2htmlex, > sharutils, 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 [392 B] > Get:5 copy:/<>/apt_archive ./ Packages [477 B] > Fetched 1826 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: pdf2htmlex but it is not > installable > 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/25/clips_6.30-4_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: clips Source-Version: 6.30-4.1 Done: =?utf-8?q?H=C3=A5vard_Flaget_Aasen?= We believe that the bug you reported is fixed in the latest version of clips, 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. Håvard Flaget Aasen (supplier of updated clips 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: Mon, 30 Mar 2020 20:51:48 +0200 Source: clips Architecture: source Version: 6.30-4.1 Distribution: unstable Urgency: medium Maintainer: Javier Fernández-Sanguino Peña Changed-By: Håvard Flaget Aasen Closes: 881009 934949 952621 Changes: clips (6.30-4.1) unstable; urgency=medium . * Non-maintainer upload. * Fix typo in maintainer address closes: #881009 * Don't build html files in doc package, so we can remove pdf2htmlex as build-dependency. closes: #952621, #934949 - Remove Format: HTML in *.doc-base files - Edit Makefile in clips_docs.diff Checksums-Sha1: 1554266a9610c281c57f871e5a56a5f53464459b 1961 clips_6.30-4.1.dsc 93307a8e46690410631a3f1c586602c3f05e67ba 21905444 clips_6.
Bug#934949: marked as done (clips: build-depends on removed package pdf2htmlex)
Your message dated Tue, 31 Mar 2020 03:48:41 + with message-id and subject line Bug#952621: fixed in clips 6.30-4.1 has caused the Debian Bug report #952621, regarding clips: build-depends on removed package pdf2htmlex 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.) -- 952621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952621 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clips Version: pdf2htmlex Severity: serious Version: 6.30-4 User: trei...@debian.org Usertags: edos-uninstallable Hi, clips build-depends on pdf2htmlex which was removed from unstable on 2019-04-01. -Ralf --- End Message --- --- Begin Message --- Source: clips Source-Version: 6.30-4.1 Done: =?utf-8?q?H=C3=A5vard_Flaget_Aasen?= We believe that the bug you reported is fixed in the latest version of clips, 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. Håvard Flaget Aasen (supplier of updated clips 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: Mon, 30 Mar 2020 20:51:48 +0200 Source: clips Architecture: source Version: 6.30-4.1 Distribution: unstable Urgency: medium Maintainer: Javier Fernández-Sanguino Peña Changed-By: Håvard Flaget Aasen Closes: 881009 934949 952621 Changes: clips (6.30-4.1) unstable; urgency=medium . * Non-maintainer upload. * Fix typo in maintainer address closes: #881009 * Don't build html files in doc package, so we can remove pdf2htmlex as build-dependency. closes: #952621, #934949 - Remove Format: HTML in *.doc-base files - Edit Makefile in clips_docs.diff Checksums-Sha1: 1554266a9610c281c57f871e5a56a5f53464459b 1961 clips_6.30-4.1.dsc 93307a8e46690410631a3f1c586602c3f05e67ba 21905444 clips_6.30-4.1.debian.tar.xz 2eff80fe4297aead194813babecfdbe1d9894ad3 5382 clips_6.30-4.1_source.buildinfo Checksums-Sha256: 17e5b6acb7bce0579cc094387ada5d56089d9035a70f9cce6181b5826fff9d00 1961 clips_6.30-4.1.dsc cf784ccd30e41668a64ba062183d99e47ba3c365caed80dcaabe880509a1ff8f 21905444 clips_6.30-4.1.debian.tar.xz d694d34b061b7f0f4d63f9b562bbf0b4790a4d569cb21390055129d4f9f4292d 5382 clips_6.30-4.1_source.buildinfo Files: 2c3327b87540a2625d1806478c437254 1961 interpreters optional clips_6.30-4.1.dsc 1e319b1c544adbdf29210eac76498a7e 21905444 interpreters optional clips_6.30-4.1.debian.tar.xz 4a60c86bfcc7c352091911e435271932 5382 interpreters optional clips_6.30-4.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl6CuEcACgkQweDZLphv fH5PJA/9HvQj/KD/WXtk+te6YOzsc+00kAKgVoVfj8cExd40AoM5YkM+8v0sTJ6w BrtvrboW/YDuXfPcD0IucPNW+j6MvfDpdw8Zo/fRdbKFNQcbvGR17jHJP2hT9oBy bpbisqdBxc6D6tFItPI2WZquOC8pyFK6LMCXQ7hzdqt9k3klABenV50pTJTz9TcF nS8uENBZPpSpoHhQD4QEihaDT6e+eeqIwb7Q4+UkvHhpKBaUWR9ks1nhxRZ2/yOi fsbmZLOqRF07+y+GHsULfSMbUhHT1JYDZffhFiWjZ+IT32FPqGy9firLivKgRDYy bVi1yjFm6I1Lx/8rMB9qlYkhPv4bQMzxCtBHBnlA2LBUVPic6OHaSgpwKhW6DqPj ruiw0RD5n9C1DQqJkTWa8irEFou4Aqwgvw6NTNdXn5u8rBC6pWdDeS3rHcmBEwzm 3E51KPh+ZsdGe/MqluQ9MDD6vml4LRvBHCu4p3v0zmGTvgFbkrUVQNpW03tnn84r QVbu4YviipQffiiqvjEOfXVin53hbV5JHUiVN5Cq8p5M5t+BciFHBqAVx1qN1qyR dvOmqZaL85Hsm+Z9PSyHEBUAYuCJAqVZ471sUEM5qlqmXxfLq9CVymfwBkxjNC2D ggekmkjoExeACnsILCveRO+w4HKYlxp38U+jR8BZa4qYSMDSMzw= =vnXa -END PGP SIGNATURE End Message ---
Bug#925721: marked as done (jnettop: ftbfs with GCC-9)
Your message dated Tue, 31 Mar 2020 03:49:55 + with message-id and subject line Bug#925721: fixed in jnettop 0.13.0-1.1 has caused the Debian Bug report #925721, regarding jnettop: 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.) -- 925721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925721 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:jnettop Version: 0.13.0-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/jnettop_0.13.0-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. [...] /usr/bin/ld: /<>/jcursesdisplay.c:433: undefined reference to `g_mutex_new' /usr/bin/ld: jcursesdisplay.o: in function `jcursesdisplay_PreRun': /<>/jcursesdisplay.c:460: undefined reference to `g_free' /usr/bin/ld: jfilter.o: in function `freeGenericFilterData': /<>/jfilter.c:26: undefined reference to `g_free' /usr/bin/ld: jfilter.o: in function `filterHTTPFunc': /<>/jfilter.c:56: undefined reference to `g_strlcpy' /usr/bin/ld: jfilter.o: in function `assignHTTPFilter': /<>/jfilter.c:64: undefined reference to `g_malloc0_n' /usr/bin/ld: jfilter.o: in function `filterSMTPFunc': /<>/jfilter.c:88: undefined reference to `g_strncasecmp' /usr/bin/ld: /<>/jfilter.c:102: undefined reference to `g_strlcpy' /usr/bin/ld: /<>/jfilter.c:104: undefined reference to `g_strncasecmp' /usr/bin/ld: /<>/jfilter.c:117: undefined reference to `g_snprintf' /usr/bin/ld: jfilter.o: in function `assignSMTPFilter': /<>/jfilter.c:125: undefined reference to `g_malloc0_n' /usr/bin/ld: jnetdisplay.o: in function `g_string_append_c_inline': /usr/include/glib-2.0/glib/gstring.h:170: undefined reference to `g_string_insert_c' /usr/bin/ld: jnetdisplay.o: in function `readNextCommandLine': /<>/jnetdisplay.c:86: undefined reference to `g_string_sized_new' /usr/bin/ld: /<>/jnetdisplay.c:101: undefined reference to `g_string_free' /usr/bin/ld: /<>/jnetdisplay.c:106: undefined reference to `g_string_free' /usr/bin/ld: /<>/jnetdisplay.c:116: undefined reference to `g_string_free' /usr/bin/ld: /<>/jnetdisplay.c:121: undefined reference to `g_string_free' /usr/bin/ld: /<>/jnetdisplay.c:125: undefined reference to `g_string_append_len' /usr/bin/ld: /<>/jnetdisplay.c:126: undefined reference to `g_strdelimit' /usr/bin/ld: /<>/jnetdisplay.c:131: undefined reference to `g_string_free' /usr/bin/ld: jnetdisplay.o: in function `sendLine': /<>/jnetdisplay.c:135: undefined reference to `g_mutex_lock' /usr/bin/ld: /<>/jnetdisplay.c:138: undefined reference to `g_mutex_unlock' /usr/bin/ld: jnetdisplay.o: in function `sendLinef': /<>/jnetdisplay.c:144: undefined reference to `g_mutex_lock' /usr/bin/ld: /<>/jnetdisplay.c:147: undefined reference to `g_mutex_unlock' /usr/bin/ld: jnetdisplay.o: in function `parseNextToken': /<>/jnetdisplay.c:153: undefined reference to `g_scanner_get_next_token' /usr/bin/ld: jnetdisplay.o: in function `processNextCommand': /<>/jnetdisplay.c:173: undefined reference to `g_scanner_input_text' /usr/bin/ld: /<>/jnetdisplay.c:206: undefined reference to `g_strdup' /usr/bin/ld: /<>/jnetdisplay.c:260: undefined reference to `g_free' /usr/bin/ld: jnetdisplay.o: in function `sendDeleteStream': /<>/jnetdisplay.c:265: undefined reference to `g_string_append_printf' /usr/bin/ld: jnetdisp
Bug#952057: marked as done (kdocker: FTBFS: src/xlibutil.h:33:10: fatal error: X11/Xlib-xcb.h: No such file or directory)
Your message dated Tue, 31 Mar 2020 03:50:01 + with message-id and subject line Bug#952057: fixed in kdocker 5.0-1.1 has caused the Debian Bug report #952057, regarding kdocker: FTBFS: src/xlibutil.h:33:10: fatal error: X11/Xlib-xcb.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.) -- 952057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kdocker Version: 5.0-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): > g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -D_REENTRANT -Wall -W -fPIC > -DTRANSLATIONS_PATH=\"/usr/share/kdocker/i18n\" -DQT_NO_DEBUG > -DQT_X11EXTRAS_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB > -DQT_CORE_LIB -I. -I3rdparty/qtsingleapplication/src -I. -Isrc -isystem > /usr/include/X11 -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem > /usr/include/x86_64-linux-gnu/qt5/QtX11Extras -isystem > /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem > /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem > /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem > /usr/include/x86_64-linux-gnu/qt5/QtCore -Ibuild > -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o build/application.o > src/application.cpp > In file included from src/trayitem.h:32, > from src/trayitemmanager.h:31, > from src/kdocker.h:29, > from src/application.h:25, > from src/application.cpp:20: > src/xlibutil.h:33:10: fatal error: X11/Xlib-xcb.h: No such file or directory >33 | #include > | ^~~~ > compilation terminated. > make[1]: *** [Makefile:522: build/application.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/02/22/kdocker_5.0-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: kdocker Source-Version: 5.0-1.1 Done: =?utf-8?q?H=C3=A5vard_Flaget_Aasen?= We believe that the bug you reported is fixed in the latest version of kdocker, 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. Håvard Flaget Aasen (supplier of updated kdocker 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: Mon, 30 Mar 2020 11:38:07 +0200 Source: kdocker Architecture: source Version: 5.0-1.1 Distribution: unstable Urgency: medium Maintainer: Ignace Mouzannar Changed-By: Håvard Flaget Aasen Closes: 952057 Changes: kdocker (5.0-1.1) unstable; urgency=medium . * Non-maintainer upload. * Change build-dependency libx11-dev -> libx11-xcb-dev closes: #952057 Checksums-Sha1: 9cc26ec615eb0e818289bba917cca36f1bf4af98 1819 kdocker_5.0-1.1.dsc 473b6a6cd12b10054318566d77048f2073a5c6ac 4380 kdocker_5.0-1.1.debian.tar.xz 432e985e070947c3b595748d1384228af106fcee 9401 kdocker_5.0-1.1_source.buildinfo Checksums-Sha256: fd40a4ce5b96eca19a83b10a0ddc1046184ae5655dde7d6ab4e50748dfc5ec6a 1819 kdocker_5.0-1.1.dsc 02cf849d119e35d8b070c22bc9fae1633d57a83cf7bda5fab011529a2365aa92 4380 kdocker_5.0-1.1.debian.tar.xz ba9be9b16263799d75dd554ba6ef0b0866244a20de84d37613c797dd41e8c14b 9401 kdocker_5.0-1.1_source.buildinfo Files: 3a285ff2a3c8da2eef2e62b76a5b138c 1819 x11 optional kdocker_5.0-1.1.dsc 8d07fd4e3eeed3a0b4b52ec13bc30334 4380 x11 optional kdocker_5.0-1.1.debian.tar.xz 5dc9f279dacf385f1a642a66b80596b5 9401 x11 optional kdocker_5.0-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl6
Bug#951979: marked as done (antimony: FTBFS: datum.h:3:10: fatal error: Python.h: No such file or directory)
Your message dated Tue, 31 Mar 2020 03:48:26 + with message-id and subject line Bug#951979: fixed in antimony 0.9.3-1.2 has caused the Debian Bug report #951979, regarding antimony: FTBFS: datum.h:3:10: fatal error: Python.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.) -- 951979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951979 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: antimony Version: 0.9.3-1.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): > cd /<>/obj-x86_64-linux-gnu/lib/graph && /usr/bin/c++ > -I/<>/lib/graph/inc -Wall -Wextra -g -Werror=switch -O3 > -DRELEASE -std=gnu++11 -o CMakeFiles/SbGraph.dir/src/datum.cpp.o -c > /<>/lib/graph/src/datum.cpp > In file included from /<>/lib/graph/src/datum.cpp:1: > /<>/lib/graph/inc/graph/datum.h:3:10: fatal error: Python.h: No > such file or directory > 3 | #include > | ^~ > compilation terminated. > make[3]: *** [lib/graph/CMakeFiles/SbGraph.dir/build.make:66: > lib/graph/CMakeFiles/SbGraph.dir/src/datum.cpp.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/02/22/antimony_0.9.3-1.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: antimony Source-Version: 0.9.3-1.2 Done: =?utf-8?q?H=C3=A5vard_Flaget_Aasen?= We believe that the bug you reported is fixed in the latest version of antimony, 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. Håvard Flaget Aasen (supplier of updated antimony 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: Mon, 30 Mar 2020 18:27:18 +0200 Source: antimony Architecture: source Version: 0.9.3-1.2 Distribution: unstable Urgency: medium Maintainer: Tiago Bortoletto Vaz Changed-By: Håvard Flaget Aasen Closes: 951979 Changes: antimony (0.9.3-1.2) unstable; urgency=medium . * Non-maintainer upload. * Add 0003-Change-python-variable-in-cmake.patch closes: #951979 Checksums-Sha1: 8149a3144220e756a8f8f228da39aece30ed02d8 1958 antimony_0.9.3-1.2.dsc a97bbd1639d8950ea441a8099c1fcb497c9c84ad 9668 antimony_0.9.3-1.2.debian.tar.xz 8d54e5b04c23eff4e16654ea77f8ea24942ed4e8 16363 antimony_0.9.3-1.2_source.buildinfo Checksums-Sha256: ac0cde4643c4054a14c720980b4fc6562ef6d0994874e61fb74f66b155012807 1958 antimony_0.9.3-1.2.dsc ddfb43349b0631647bce2bc9d7bb1d28f78fc3b668e223d717a8194c1d8b52f5 9668 antimony_0.9.3-1.2.debian.tar.xz e565078389db13b86d98aea09784e979e86d1f8d5989ac2e03cacb2354686072 16363 antimony_0.9.3-1.2_source.buildinfo Files: 50decc5bd46fbf4eba07386c0809f972 1958 graphics optional antimony_0.9.3-1.2.dsc ac7f8d4aecbac3b79ddb9434bc3267f7 9668 graphics optional antimony_0.9.3-1.2.debian.tar.xz c8940576643eb490a6e3ee16a2e11ff5 16363 graphics optional antimony_0.9.3-1.2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl6CuEAACgkQweDZLphv fH6G3Q//XQH9UTyAx/x/OziPS+V4gYmHtNxENF+yh9py6fuH/3g83HutAriHuEPI fTXbZoz0UGP+JckOJTUvPaZjiWQB0WIh7HsgJjaYCLKDI9uVkeybeQZmrAMmsSCX lXVnNwsfjDGmZs/0oSE+O6zIl09gvcwQFMsi1HIfm08wdMrnIn2WNsLVHTRNcO3t BRmSQPiAtunhgs7YURBaK+aBa14cGPQCVQ3OkUcFtYTR0aK4lunFVgOynd/IKvR4 sTYn1vpfyi4/Ujk7B2dUq0tzSFEKnRWbBMd7ygLcc1yX9e7J3uBubdsu/U4enOO0 qymgq2NOiB7SVO39Ej+IZKaJzlSZRsYaPuwcqRbWX9yUI5RcD0D+T+Ua75FeUpiM HyAd/HQsbapdA+5+gAADRNptPfrFEanyKF5pg8NtSeKwOoRUs/O8+W5ZrvgqEN5M azJuNb3uYH1L5BfvLjnNGIWmvMuRMaTmCMpR3mRysNtW01tLAygGRdn/hPGPXSZv UNK2AgUDshS+XyHikBomjNZeN+uwV65hNP224RU6SaiCNNw5mvm7KZaQ/emv8aLv MofUMXOcbV4gA0dzMsjyC+6CRd/yvlMU3QUOfklsosJb/z
Bug#881009: marked as done (src:clips: typo in maintainer address (.og instead of .org))
Your message dated Tue, 31 Mar 2020 03:48:41 + with message-id and subject line Bug#881009: fixed in clips 6.30-4.1 has caused the Debian Bug report #881009, regarding src:clips: typo in maintainer address (.og instead of .org) 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.) -- 881009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clips Source-Version: 6.30-3 Tags: sid Severity: serious > Source: clips > Binary: clips libclips libclips-dev clips-common clips-doc [...] > Version: 6.30-4 [...] > Maintainer: Javier Fernández-Sanguino Peña > Changed-By: Javier Fernández-Sanguino Peña The maintainer has a typo (missing the "r" in ".org") and causes bounces. Ansgar --- End Message --- --- Begin Message --- Source: clips Source-Version: 6.30-4.1 Done: =?utf-8?q?H=C3=A5vard_Flaget_Aasen?= We believe that the bug you reported is fixed in the latest version of clips, 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 881...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Håvard Flaget Aasen (supplier of updated clips 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: Mon, 30 Mar 2020 20:51:48 +0200 Source: clips Architecture: source Version: 6.30-4.1 Distribution: unstable Urgency: medium Maintainer: Javier Fernández-Sanguino Peña Changed-By: Håvard Flaget Aasen Closes: 881009 934949 952621 Changes: clips (6.30-4.1) unstable; urgency=medium . * Non-maintainer upload. * Fix typo in maintainer address closes: #881009 * Don't build html files in doc package, so we can remove pdf2htmlex as build-dependency. closes: #952621, #934949 - Remove Format: HTML in *.doc-base files - Edit Makefile in clips_docs.diff Checksums-Sha1: 1554266a9610c281c57f871e5a56a5f53464459b 1961 clips_6.30-4.1.dsc 93307a8e46690410631a3f1c586602c3f05e67ba 21905444 clips_6.30-4.1.debian.tar.xz 2eff80fe4297aead194813babecfdbe1d9894ad3 5382 clips_6.30-4.1_source.buildinfo Checksums-Sha256: 17e5b6acb7bce0579cc094387ada5d56089d9035a70f9cce6181b5826fff9d00 1961 clips_6.30-4.1.dsc cf784ccd30e41668a64ba062183d99e47ba3c365caed80dcaabe880509a1ff8f 21905444 clips_6.30-4.1.debian.tar.xz d694d34b061b7f0f4d63f9b562bbf0b4790a4d569cb21390055129d4f9f4292d 5382 clips_6.30-4.1_source.buildinfo Files: 2c3327b87540a2625d1806478c437254 1961 interpreters optional clips_6.30-4.1.dsc 1e319b1c544adbdf29210eac76498a7e 21905444 interpreters optional clips_6.30-4.1.debian.tar.xz 4a60c86bfcc7c352091911e435271932 5382 interpreters optional clips_6.30-4.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl6CuEcACgkQweDZLphv fH5PJA/9HvQj/KD/WXtk+te6YOzsc+00kAKgVoVfj8cExd40AoM5YkM+8v0sTJ6w BrtvrboW/YDuXfPcD0IucPNW+j6MvfDpdw8Zo/fRdbKFNQcbvGR17jHJP2hT9oBy bpbisqdBxc6D6tFItPI2WZquOC8pyFK6LMCXQ7hzdqt9k3klABenV50pTJTz9TcF nS8uENBZPpSpoHhQD4QEihaDT6e+eeqIwb7Q4+UkvHhpKBaUWR9ks1nhxRZ2/yOi fsbmZLOqRF07+y+GHsULfSMbUhHT1JYDZffhFiWjZ+IT32FPqGy9firLivKgRDYy bVi1yjFm6I1Lx/8rMB9qlYkhPv4bQMzxCtBHBnlA2LBUVPic6OHaSgpwKhW6DqPj ruiw0RD5n9C1DQqJkTWa8irEFou4Aqwgvw6NTNdXn5u8rBC6pWdDeS3rHcmBEwzm 3E51KPh+ZsdGe/MqluQ9MDD6vml4LRvBHCu4p3v0zmGTvgFbkrUVQNpW03tnn84r QVbu4YviipQffiiqvjEOfXVin53hbV5JHUiVN5Cq8p5M5t+BciFHBqAVx1qN1qyR dvOmqZaL85Hsm+Z9PSyHEBUAYuCJAqVZ471sUEM5qlqmXxfLq9CVymfwBkxjNC2D ggekmkjoExeACnsILCveRO+w4HKYlxp38U+jR8BZa4qYSMDSMzw= =vnXa -END PGP SIGNATURE End Message ---
Bug#952621: marked as done (clips: FTBFS: build-dependency not installable: pdf2htmlex)
Your message dated Tue, 31 Mar 2020 03:48:41 + with message-id and subject line Bug#934949: fixed in clips 6.30-4.1 has caused the Debian Bug report #934949, regarding clips: FTBFS: build-dependency not installable: pdf2htmlex 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.) -- 934949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934949 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clips Version: 6.30-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200225 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules). Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: libncurses-dev, debhelper (>= 10~), pdf2htmlex, > sharutils, build-essential, fakeroot > Filtered Build-Depends: libncurses-dev, debhelper (>= 10~), pdf2htmlex, > sharutils, 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 [392 B] > Get:5 copy:/<>/apt_archive ./ Packages [477 B] > Fetched 1826 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: pdf2htmlex but it is not > installable > 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/25/clips_6.30-4_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: clips Source-Version: 6.30-4.1 Done: =?utf-8?q?H=C3=A5vard_Flaget_Aasen?= We believe that the bug you reported is fixed in the latest version of clips, 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 934...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Håvard Flaget Aasen (supplier of updated clips 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: Mon, 30 Mar 2020 20:51:48 +0200 Source: clips Architecture: source Version: 6.30-4.1 Distribution: unstable Urgency: medium Maintainer: Javier Fernández-Sanguino Peña Changed-By: Håvard Flaget Aasen Closes: 881009 934949 952621 Changes: clips (6.30-4.1) unstable; urgency=medium . * Non-maintainer upload. * Fix typo in maintainer address closes: #881009 * Don't build html files in doc package, so we can remove pdf2htmlex as build-dependency. closes: #952621, #934949 - Remove Format: HTML in *.doc-base files - Edit Makefile in clips_docs.diff Checksums-Sha1: 1554266a9610c281c57f871e5a56a5f53464459b 1961 clips_6.30-4.1.dsc 93307a8e46690410631a3f1c586602c3f05e67ba 21905444 clips_6.
Processed: py2removal bugs severity updates - 2020-03-31 02:42:37.359181+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-ipython is a module and has 0 external rdeps or not in testing > severity 947298 serious Bug #947298 [src:ipython-py2] ipython-py2: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 947298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947298 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954582: samba: FTBFS glibc/stropts/python issue.
The samba FTBFS is blocking the python 3.8 transition in raspbian bullseye, so I decided to take a look. error: Unable to determine origin of type `struct cli_credentials' I don't think this is the error that is causing the build failure. The same error can be seen in succesful build logs. e.g. https://buildd.debian.org/status/fetch.php?pkg=samba&arch=amd64&ver=2%3A4.11.5%2Bdfsg-1%2Bb1&stamp=1583775414&raw=0 Instead I think the real error is further down the log ../../lib/replace/system/network.h:91:10: fatal error: stropts.h: No such file or directory Some googling lead me to https://bugs.gentoo.org/699668 and https://bugzilla.samba.org/show_bug.cgi?id=14100 which suggests that the bug triggers if samba is built against a newer glibc while python was built against an older glibc. Specifically it seems python headers leak certain system feature defines including HAVE_STROPTS_H which cause network.h to think stropts.h is available when it isn't. If my understanding is correct I see two possible ways forward. 1. Rebuild python3.8 against the new glibc. 2. Remove the stropts include from samba, it doesn't seem to actually be used for anything (at least I can't find any other references to HAVE_STROPTS_H in the code). I am currently testing a build in raspbian bullseye with the second approach. I will report back later on whether it results in a succesful build.
Bug#954679: marked as done (mockery: FTBFS: src/golang.org/x/tools/internal/imports/mod.go:17:2: cannot find package "golang.org/x/mod/module")
Your message dated Tue, 31 Mar 2020 01:04:05 + with message-id and subject line Bug#954679: fixed in mockery 0.0~git20181123.e78b021-3 has caused the Debian Bug report #954679, regarding mockery: FTBFS: src/golang.org/x/tools/internal/imports/mod.go:17:2: cannot find package "golang.org/x/mod/module" 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.) -- 954679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mockery Version: 0.0~git20181123.e78b021-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200322 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package mockery > dpkg-buildpackage: info: source version 0.0~git20181123.e78b021-2 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Dmitry Smirnov > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean --builddirectory=_build --buildsystem=golang --with=golang >dh_auto_clean -O--builddirectory=_build -O--buildsystem=golang >dh_autoreconf_clean -O--builddirectory=_build -O--buildsystem=golang >dh_clean -O--builddirectory=_build -O--buildsystem=golang > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building mockery using existing > ./mockery_0.0~git20181123.e78b021.orig.tar.xz > dpkg-source: info: building mockery in > mockery_0.0~git20181123.e78b021-2.debian.tar.xz > dpkg-source: info: building mockery in mockery_0.0~git20181123.e78b021-2.dsc > debian/rules binary > dh binary --builddirectory=_build --buildsystem=golang --with=golang >dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang >dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang >dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang >dh_auto_build -O--builddirectory=_build -O--buildsystem=golang > cd _build && go install -trimpath -v -p 4 github.com/vektra/mockery > github.com/vektra/mockery/cmd/mockery github.com/vektra/mockery/mockery > github.com/vektra/mockery/mockery/fixtures > github.com/vektra/mockery/mockery/fixtures/buildtag/comment > github.com/vektra/mockery/mockery/fixtures/buildtag/filename > github.com/vektra/mockery/mockery/fixtures/http > github.com/vektra/mockery/mockery/fixtures/mocks > github.com/vektra/mockery/mockery/fixtures/test > src/golang.org/x/tools/internal/imports/mod.go:17:2: cannot find package > "golang.org/x/mod/module" in any of: > /usr/lib/go-1.14/src/golang.org/x/mod/module (from $GOROOT) > /<>/_build/src/golang.org/x/mod/module (from $GOPATH) > src/golang.org/x/tools/internal/imports/mod.go:18:2: cannot find package > "golang.org/x/mod/semver" in any of: > /usr/lib/go-1.14/src/golang.org/x/mod/semver (from $GOROOT) > /<>/_build/src/golang.org/x/mod/semver (from $GOPATH) > dh_auto_build: error: cd _build && go install -trimpath -v -p 4 > github.com/vektra/mockery github.com/vektra/mockery/cmd/mockery > github.com/vektra/mockery/mockery github.com/vektra/mockery/mockery/fixtures > github.com/vektra/mockery/mockery/fixtures/buildtag/comment > github.com/vektra/mockery/mockery/fixtures/buildtag/filename > github.com/vektra/mockery/mockery/fixtures/http > github.com/vektra/mockery/mockery/fixtures/mocks > github.com/vektra/mockery/mockery/fixtures/test returned exit code 1 > make: *** [debian/rules:14: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2020/03/22/mockery_0.0~git20181123.e78b021-2_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: mockery Source-Version: 0.0~git20181123.e78b021-3 Done: Dmitry Smirnov We believe that the bug you reported is fixed in the latest version of mockery, 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#954679: marked as pending in mockery
Control: tag -1 pending Hello, Bug #954679 in mockery 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/mockery/-/commit/be4d52ac1d425b503fd7ff48bfa822ccd2449346 Build-Depends += golang-golang-x-mod-dev (Closes: #954679). (this message was generated automatically) -- Greetings https://bugs.debian.org/954679
Processed: Bug#954679 marked as pending in mockery
Processing control commands: > tag -1 pending Bug #954679 [src:mockery] mockery: FTBFS: src/golang.org/x/tools/internal/imports/mod.go:17:2: cannot find package "golang.org/x/mod/module" Added tag(s) pending. -- 954679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938184: marked as done (python-socksipychain: Python2 removal in sid/bullseye)
Your message dated Mon, 30 Mar 2020 17:29:50 -0700 with message-id and subject line Fixed in latest version 2.1.0.5.geb5ee87-1 has caused the Debian Bug report #938184, regarding python-socksipychain: 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.) -- 938184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-socksipychain Version: 2.0.15-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-socksipychain 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 --- This should now be fixed (again :). Latest upstream contains fixes to make autopkgtests pass. Python2 dependency in tests has been removed. -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 31 Mar 2020 00:44:40 +0100 Source: python-socksipychain Architecture: source Version: 2.1.0.5.geb5ee87-1 Distribution: unstable Urgency: medium Maintainer: FreedomBox packaging team Changed-By: Federico Ceratto Changes: python-socksipychain (2.1.0.5.geb5ee87-1) unstable; urgency=medium . [ Sunil Mohan Adapa ] * New upstream release (from git due to missing release tag). * d/t/control: Replace a test dependency on python-all with python3-all. * d/copyright: Update copyright format URI * d/control: Set Rules-Requires-Root: no Checksums-Sha1: 155f0bf9cc79421715191f3e6fefe999115f165c 2362 python-socksipychain_2.1.0.5.geb5ee87-1.dsc d08304211a7807e50e8f636e2049cff0cbe62fb6 19091 python-socksipychain_2.1.0.5.geb5ee87.orig.tar.gz 889a4559ae180d4f0f40c007cdeadafeacc8163f 3024 python-socksipychain_2.1.0.5.geb5ee87-1.debian.tar.xz 1847cd7494ee7705e75da37d3cfea7b4613bcf1c 6369 python-socksipychain_2.1.0.5.geb5ee87-1_amd64.buildinfo Checksums-Sha256: 891c4d906431bb33520b103c2d89a9f170bbac43b1df16c0972b960e15e3657a 2362 python-socksipychain_2.1.0.5.geb5ee87-1.dsc a0672b6f0ee457ad3e004b59ceb986e136e5f88968b9d16581751528e0f32d32 19091 python-socksipychain_2.1.0.5.geb5ee87.orig.tar.gz 652e4b35a5442d6a4956d5ead519e98cec6c091c180542d943449dc192240d08 3024 python-socksipychain_2.1.0.5.geb5ee87-1.debian.tar.xz 14c2868ed11283aa4fe0bd13174ecad42bedfaadf2dae333fead6ecfb88d83bb 6369 python-socksipychain_2.1.0.5.geb5ee87-1_amd64.buildinfo Files: 5bcab28d0b75ab696c6f0f5565a3c133 2362 python optional python-socksipycha
Bug#952359: marked as done (strophejs: FTBFS: Error: ERROR: module path does not exist: /usr/lib/nodejs/almond/almond.js for module named: /usr/lib/nodejs/almond/almond.js. Path is relative to: /<
Your message dated Mon, 30 Mar 2020 23:40:53 + with message-id and subject line Bug#952359: fixed in strophejs 1.2.14+dfsg-5 has caused the Debian Bug report #952359, regarding strophejs: FTBFS: Error: ERROR: module path does not exist: /usr/lib/nodejs/almond/almond.js for module named: /usr/lib/nodejs/almond/almond.js. Path is relative to: /<> 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.) -- 952359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: strophejs Version: 1.2.14+dfsg-4 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): > debian/rules build > dh build >dh_update_autotools_config >dh_auto_configure >debian/rules override_dh_auto_build > make[1]: Entering directory '/<>' > node /usr/lib/nodejs/requirejs/r.js -o build.js > name=/usr/lib/nodejs/almond/almond.js insertRequire=strophe-polyfill > include=strophe-polyfill out=strophe.min.js > Error: Error: ERROR: module path does not exist: > /usr/lib/nodejs/almond/almond.js for module named: > /usr/lib/nodejs/almond/almond.js. Path is relative to: /<> > at /usr/lib/nodejs/requirejs/r.js:28446:35 > > make[1]: *** [debian/rules:17: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/02/22/strophejs_1.2.14+dfsg-4_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: strophejs Source-Version: 1.2.14+dfsg-5 Done: Martin We believe that the bug you reported is fixed in the latest version of strophejs, 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. Martin (supplier of updated strophejs 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: Mon, 30 Mar 2020 22:53:23 + Source: strophejs Architecture: source Version: 1.2.14+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Debian XMPP Maintainers Changed-By: Martin Closes: 952359 Changes: strophejs (1.2.14+dfsg-5) unstable; urgency=medium . * Team upload. [ Sunil Mohan Adapa ] * Fix path to almond.js, again. (Closes: #952359) Checksums-Sha1: 9357c17f6aa3568d2563267d8cb3621b3cda183a 2020 strophejs_1.2.14+dfsg-5.dsc 6d2cc01e8c9c2f6d31f64fbf2ce80be862afb238 4276 strophejs_1.2.14+dfsg-5.debian.tar.xz 25cc2b6e9796fe6658ee05c8caea3829046a5f3b 7480 strophejs_1.2.14+dfsg-5_amd64.buildinfo Checksums-Sha256: b3e76a898353f58e98913d66fed1d07663eb27bd0c22e03da549b626e67119e7 2020 strophejs_1.2.14+dfsg-5.dsc 6d97a4dac4c0c27ac64bab7da65f940771cd0cf6293699c9c996eef76d94271c 4276 strophejs_1.2.14+dfsg-5.debian.tar.xz ec1929029ffb803b22fc2b711304ba7cf9c606f86db374a8713718fc58c6b95d 7480 strophejs_1.2.14+dfsg-5_amd64.buildinfo Files: d370aeeb5e784543b18f80b55156abc0 2020 web optional strophejs_1.2.14+dfsg-5.dsc c783270f8fe871aefe97f3f464821083 4276 web optional strophejs_1.2.14+dfsg-5.debian.tar.xz c944aae9b8edd51feb7a236495ccbdaf 7480 web optional strophejs_1.2.14+dfsg-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEftHeo0XZoKEY1KdA4+Chwoa5Y+oFAl6Cey4ACgkQ4+Chwoa5 Y+pRAQ//RAsQiOrx+dkmLSN8eNofIpBjCQCWwQWKd50GUjtIv79vD8NHZ+kzeVkp KMP8EUfsr5RDe5UbBGH0At1lavzgOoaNcTYl3vlCSIq6TPXuUC7Ck2+w08DujKLb i+8oGCKsmq3lBKCeiKP+re1m9fr0TQmwXCg8Ynx0+Pb8PdlZOf48a/ZaFsbAnoVE BEkJe6BeZjgzbnhTv/HRsulK4J42rph5Vi7KXLZP/pKb1Xor/xqz9RWVoPk1Tp6r N82i3JSn+3vStnEDlQm3FFLXs1zHuGiW1NRsy5vj490fDqUvsXlGUK/DHGErs/Du kwwLToEosR/55sf8VXv+Pj310ZJCX3nNl/IWDxOK9drexrn0opcBVXMEENGrNYnG aQDkvzoEIwXL3bcgiIF2l3uCGqBIdDtlaKksOdFyUVml2wUsjfdqVY22ZTPtGxSD aBnvB6kL5Jyt3p7n25nN9
Bug#954698: serf: FTBFS: 1) test_ssltunnel_basic_auth_server_has_keepalive_off: test/test_context.c:2138: expected <0> but was <120199>
On Mon, Mar 30, 2020 at 02:53:40PM -0400, Justin Erenkrantz wrote: > Here's a tentative patch that causes the test cases to pass with OpenSSL > 1.1.1e+ for me on Debian Sid. > > James, can you please give it a go and confirm that it works for you? The package does build and pass tests with the patch. Thanks! > Before I commit, we'd also need to gate this based on the new OpenSSL > constant. We could gate based upon the OpenSSL version number, but I think > if we can confine to this one area, gating based on ifdef is likely prudent. +1 > I'd also like to get the scons patch you sent earlier into a new release. > I'm hopeful that I can cut a new 1.3 release sometime this week and have > others vote on it - that should make your downstream efforts a bit easier. That would be appreciated. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#952359: Please apply the patch and upload
Hello, Only a few days remain until the package is removed from testing because of this bug. As a consequence, libjs-jsxc, which is used in FreedomBox to provide a web-based XMPP client will also be removed. Please consider applying the attached simple patch and prevent removal this package and its reverse dependencies. Thanks, -- Sunil signature.asc Description: OpenPGP digital signature
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 952359 + patch Bug #952359 [src:strophejs] strophejs: FTBFS: Error: ERROR: module path does not exist: /usr/lib/nodejs/almond/almond.js for module named: /usr/lib/nodejs/almond/almond.js. Path is relative to: /<> Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 952359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925721: jnettop: diff for NMU version 0.13.0-1.1
Control: tags 925721 + patch Control: tags 925721 + pending Dear maintainer, I've prepared an NMU for jnettop (versioned as 0.13.0-1.1) and uploaded it mentors for sponsoring. Please feel free to tell me if I should remove it. -- Regards Sudip diff -Nru jnettop-0.13.0/debian/changelog jnettop-0.13.0/debian/changelog --- jnettop-0.13.0/debian/changelog 2010-10-05 02:04:14.0 +0100 +++ jnettop-0.13.0/debian/changelog 2020-03-30 22:37:51.0 +0100 @@ -1,3 +1,10 @@ +jnettop (0.13.0-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix ftbfs with GCC. (Closes: #925721) + + -- Sudip Mukherjee Mon, 30 Mar 2020 22:37:51 +0100 + jnettop (0.13.0-1) unstable; urgency=low * New upstream release diff -Nru jnettop-0.13.0/debian/patches/fix_gcc.patch jnettop-0.13.0/debian/patches/fix_gcc.patch --- jnettop-0.13.0/debian/patches/fix_gcc.patch 1970-01-01 01:00:00.0 +0100 +++ jnettop-0.13.0/debian/patches/fix_gcc.patch 2020-03-30 22:37:30.0 +0100 @@ -0,0 +1,26 @@ +Description: Fix ftbfs with GCC + +Author: Sudip Mukherjee + +--- + +--- jnettop-0.13.0.orig/Makefile.in jnettop-0.13.0/Makefile.in +@@ -135,7 +135,7 @@ am__depfiles_maybe = depfiles + COMPILE = $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) \ + $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) + CCLD = $(CC) +-LINK = $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@ ++LINK = $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(LDFLAGS) -o $@ + DIST_SOURCES = $(jnettop_SOURCES) + + NROFF = nroff +@@ -210,7 +210,7 @@ clean-binPROGRAMS: + -test -z "$(bin_PROGRAMS)" || rm -f $(bin_PROGRAMS) + jnettop$(EXEEXT): $(jnettop_OBJECTS) $(jnettop_DEPENDENCIES) + @rm -f jnettop$(EXEEXT) +- $(LINK) $(jnettop_LDFLAGS) $(jnettop_OBJECTS) $(jnettop_LDADD) $(LIBS) ++ $(LINK) $(jnettop_LDFLAGS) $(jnettop_OBJECTS) $(jnettop_LDADD) $(LIBS) $(AM_LDFLAGS) + dist_pkgdataSCRIPT_INSTALL = $(INSTALL_SCRIPT) + install-dist_pkgdataSCRIPTS: $(dist_pkgdata_SCRIPTS) + @$(NORMAL_INSTALL) diff -Nru jnettop-0.13.0/debian/patches/series jnettop-0.13.0/debian/patches/series --- jnettop-0.13.0/debian/patches/series2010-10-05 03:15:02.0 +0100 +++ jnettop-0.13.0/debian/patches/series2020-03-30 22:33:40.0 +0100 @@ -1,3 +1,4 @@ 0001-Use-64-bit-integers-for-byte-totals-support-bigger-u.patch 0002-Fix-up-some-help-text.patch 0003-Add-host-port-aggregation.patch +fix_gcc.patch
Processed: jnettop: diff for NMU version 0.13.0-1.1
Processing control commands: > tags 925721 + patch Bug #925721 [src:jnettop] jnettop: ftbfs with GCC-9 Added tag(s) patch. > tags 925721 + pending Bug #925721 [src:jnettop] jnettop: ftbfs with GCC-9 Added tag(s) pending. -- 925721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925721 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#955367: libdvdread7: crashes vlc when trying to read a DVD iso image
Processing control commands: > tags -1 + confirmed upstream Bug #955367 [libdvdread7] libdvdread7: crashes vlc when trying to read a DVD iso image Added tag(s) confirmed and upstream. > forwarded -1 https://code.videolan.org/videolan/libdvdread/issues/14 Bug #955367 [libdvdread7] libdvdread7: crashes vlc when trying to read a DVD iso image Set Bug forwarded-to-address to 'https://code.videolan.org/videolan/libdvdread/issues/14'. > severity -1 serious Bug #955367 [libdvdread7] libdvdread7: crashes vlc when trying to read a DVD iso image Severity set to 'serious' from 'normal' -- 955367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955367 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954676: [Pkg-pascal-devel] Bug#954676: pasdoc: FTBFS: dh_installman: error: Could not determine section for ./pasdoc.1
Paul Gevers napisał(a):
>
> Hi Michalis,
>
> On 30-03-2020 14:11, Michalis Kamburelis wrote:
> > Do we know what the message "Could not determine section for" means,
> > or how to investigate it? I mean, this manpage should go to section 1
> > ("User Commands"), which is indicated both by the filename "pasdoc.1"
> > and by text inside "pasdoc(1)". Why does the dh_installman not catch
> > it?
>
> I don't know but if nobody does, I'll figure it out. I consider this a
> stupid regression of help2man and/or dh_installman, but there's probably
> a reason.
>
> > If necessary, I can easily create a proper manpage upstream (that
> > would be available in our repository, without the need for help2man),
> > I just need to know what is exactly required / necessary to avoid :)
>
> Let's not go that route unless you as upstream really want to support a
> proper man page. I mean, apparently you never really consider the
> program to lack a dedicated man page. Obviously if you think otherwise
> because of this issue, feel free to draft (and maintain) a man page
> upstream, but otherwise I am totally happy to ship a man page created
> with help2man. I assume you do maintain the --help option.
>
Thank you for looking into this.
Indeed, as upstream it is easier for me to *not* maintain a dedicated
webpage, and instead rely on "pasdoc --help" and help2man. The manpage
generated this way looks satisfactory I think (at least for us, humans
-- it seems only some programs complain :) ). So if we can fix this
without adding a dedicated man page, that's great.
Regards,
Michalis
Bug#953747: marked as done (icu: CVE-2020-10531)
Your message dated Mon, 30 Mar 2020 21:32:33 + with message-id and subject line Bug#953747: fixed in icu 57.1-6+deb9u4 has caused the Debian Bug report #953747, regarding icu: CVE-2020-10531 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.) -- 953747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953747 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: icu Version: 63.2-2 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://github.com/unicode-org/icu/pull/971 Hi, The following vulnerability was published for icu. CVE-2020-10531[0]: | An issue was discovered in International Components for Unicode (ICU) | for C/C++ through 66.1. An integer overflow, leading to a heap-based | buffer overflow, exists in the UnicodeString::doAppend() function in | common/unistr.cpp. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-10531 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10531 [1] https://bugs.chromium.org/p/chromium/issues/detail?id=1044570 (not public) [2] https://unicode-org.atlassian.net/browse/ICU-20958 (private) [3] https://github.com/unicode-org/icu/pull/971 [4] https://github.com/unicode-org/icu/commit/b7d08bc04a4296982fcef8b6b8a354a9e4e7afca Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: icu Source-Version: 57.1-6+deb9u4 Done: Laszlo Boszormenyi (GCS) We believe that the bug you reported is fixed in the latest version of icu, 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. Laszlo Boszormenyi (GCS) (supplier of updated icu package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 14 Mar 2020 19:34:22 + Source: icu Binary: libicu57 libicu57-dbg libicu-dev icu-devtools icu-devtools-dbg icu-doc Architecture: source amd64 all Version: 57.1-6+deb9u4 Distribution: stretch-security Urgency: high Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Description: icu-devtools - Development utilities for International Components for Unicode icu-devtools-dbg - Development utilities for International Components for Unicode (d icu-doc- API documentation for ICU classes and functions libicu-dev - Development files for International Components for Unicode libicu57 - International Components for Unicode libicu57-dbg - International Components for Unicode (debug symbols) Closes: 953747 Changes: icu (57.1-6+deb9u4) stretch-security; urgency=high . * Backport upstream security fix for CVE-2020-10531: SEGV_MAPERR in UnicodeString::doAppend() (closes: #953747). Checksums-Sha1: ad8bb633ee33b11206c05c84e554855f10e1c8e3 2133 icu_57.1-6+deb9u4.dsc 5622b6175d2336d738b3becde49bae95e8219d96 36404 icu_57.1-6+deb9u4.debian.tar.xz e6777b5681684ccfe27cca221a88ca89afea5f3a 643000 icu-devtools-dbg_57.1-6+deb9u4_amd64.deb 4a04f7725a92db84fdf51b61b6029bc3d0bbf0d1 177818 icu-devtools_57.1-6+deb9u4_amd64.deb aee2ab7750617217ef46cd28846be3cafce9a72e 2397226 icu-doc_57.1-6+deb9u4_all.deb be66ee49a23a23504ed2e8c7c37333f82ca095b6 7698 icu_57.1-6+deb9u4_amd64.buildinfo b1269fd8c9a396401748358191b4da8061f90a6d 16489294 libicu-dev_57.1-6+deb9u4_amd64.deb 7c763566a6cdbb0eb1d29c06f41859dc09de351f 7372704 libicu57-dbg_57.1-6+deb9u4_amd64.deb 98388448b3b07dbbc94cb9028ebb2e1895a9fe05 7698670 libicu57_57.1-6+deb9u4_amd64.deb Checksums-Sha256: 80b9e9f411f713e7ba475959f083ba600cead528ab2c097448564f3ad9c0ffb5 2133 icu_57.1-6+deb9u4.dsc 37674a98793c0048ad8f7f8dc21d9ab14fd01b182c5ea764da3bae111f8afd63 36404 icu_57.1-6+deb9u4.debian.tar.xz cac15bf399ed715741e8bbedde97887d086207be68b609ccafb38d0f19ca913d 643000 icu-devtools-dbg_57.1-6+deb9u4_amd64.deb 937a8fafa36dc1e3f24b98fd8b10490b6de7e13e7224330b7fb77251215b0653 177818 icu-devtools_57.1-6+deb9u4_amd64.deb 3d11d4fa9fb2c7235d11324f04b23c0b9eefae60cb0b397a008
Bug#953770: marked as done (bluez: CVE-2020-0556)
Your message dated Mon, 30 Mar 2020 21:32:23 + with message-id and subject line Bug#953770: fixed in bluez 5.43-2+deb9u2 has caused the Debian Bug report #953770, regarding bluez: CVE-2020-0556 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.) -- 953770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953770 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bluez Version: 5.50-1 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 5.52-1 Hi, The following vulnerability was published for bluez. CVE-2020-0556[0]: | Improper access control in subsystem for BlueZ before version 5.53 may | allow an unauthenticated user to potentially enable escalation of | privilege and denial of service via adjacent access. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-0556 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-0556 [1] https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00352.html Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: bluez Source-Version: 5.43-2+deb9u2 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of bluez, 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. Salvatore Bonaccorso (supplier of updated bluez package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 22 Mar 2020 10:42:49 +0100 Source: bluez Architecture: source Version: 5.43-2+deb9u2 Distribution: stretch-security Urgency: high Maintainer: Debian Bluetooth Maintainers Changed-By: Salvatore Bonaccorso Closes: 953770 Changes: bluez (5.43-2+deb9u2) stretch-security; urgency=high . * Non-maintainer upload by the Security Team. * Address INTEL-SA-00352 (CVE-2020-0556) (Closes: #953770) - HOGP must only accept data from bonded devices - HID accepts bonded device connections only * input: hog: Attempt to set security level if not bonded * input: Add LEAutoSecurity setting to input.conf Checksums-Sha1: 7a264b6056fb3b369384cae4de6a8658251f35ce 2936 bluez_5.43-2+deb9u2.dsc 77eae3c847bb6eb5fb6cf9e3df07e9cbfaecad24 30480 bluez_5.43-2+deb9u2.debian.tar.xz Checksums-Sha256: 97be0c87939413d3566e7967e118fde4db1033cf7efa12155b2e02155292496f 2936 bluez_5.43-2+deb9u2.dsc 442c6f2f55194f496b86f394df77684c09a546b6e4a39feff111dd2403bd9eed 30480 bluez_5.43-2+deb9u2.debian.tar.xz Files: 34151ebe4c576cce276f1d3d24c0dfce 2936 admin optional bluez_5.43-2+deb9u2.dsc 1e2c4aef142c2fe1d95c89def1a216bd 30480 admin optional bluez_5.43-2+deb9u2.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAl53NQFfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89Eq9sP/2Wi9pIeZuw3kfGvgeR9gBMCOp8UKmyl PWVOG7xQBhTDJr7dfntPau511VQ1paqcZBrWG6xmS0S2Vw3UCXTo1rpU8p2U4YMD cIBaKbYdsEramqStnIIriQLCPVkz1K87RPNGXpSulUyuDNI9/KEtjSpr7xbxVUBZ sE76EDn92qPcRmdQ5/Hg9kqw9CxsKc+Y78nD+3UchCY7RJp8v+d9xSGwVzcPZgwI NLs22GCAiusYXKKqDzNiTyvsjuB3ZKtS5NCTjPq6dsOOhS554J0OZM9/Y7+XMQnj YQzQpegKejvZGdeQ5m3tB7RvSQnAHrupuiFcQxsPC4lylce7kmYig7uftGs/PtEy AG+s+PVEqKaIWTdR8wy+cMk8PDuSEWh3mErh4Vm5CroazjvbYLzf1RUsWjGtvLWq dFx9OVo4+CpzZL3XG9BE+XM/+H6OmwQPnbSFImmdOBETea9V1vtrlj4IK+8akwFQ DVzefeHhPP4BCmldyCGId08r23AABvNc7r9Gwa0E9/URLwAjn1HqPs0XhlYZ0tju x8E9XJq+UWwjGO+YEmgNdS4W+mH5uArvtlhXD5IyZeK/SIh1Oeag1iSeVqKEL9z9 Aw/QmOf6c+uBvirzrg6lmTuQxRJVeRLVBTcuqtv34z8a3Rn9HkfonLYhGCIKLcne EoI5eoQSZ2FI =hMa4 -END PGP SIGNATURE End Message ---
Processed: closing 953716
Processing commands for cont...@bugs.debian.org: > close 953716 Bug #953716 [src:libvirt] src:libvirt: fails to migrate to testing for too long Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 953716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953716 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955284: marked as done (gitinspector crashes: TypeError: 'bool' object is not iterable)
Your message dated Mon, 30 Mar 2020 20:48:37 +
with message-id
and subject line Bug#955284: fixed in gitinspector 0.4.4+dfsg-7
has caused the Debian Bug report #955284,
regarding gitinspector crashes: TypeError: 'bool' object is not iterable
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.)
--
955284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955284
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitinspector
Version: 0.4.4+dfsg-6
Severity: serious
File: /usr/bin/gitinspector
Any invocation of gitinspector results in:
$ gitinspector --help
Traceback (most recent call last):
File "/usr/bin/gitinspector", line 11, in
load_entry_point('gitinspector==0.4.4', 'console_scripts', 'gitinspector')()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 489, in
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2852,
in load_entry_point
return ep.load()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2443,
in load
return self.resolve()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2449,
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/usr/lib/python3/dist-packages/gitinspector/gitinspector.py", line 25,
in
localization.init()
File "/usr/lib/python3/dist-packages/gitinspector/localization.py", line 76,
in init
__translation__.install(True)
File "/usr/lib/python3.8/gettext.py", line 352, in install
for name in allowed & set(names):
TypeError: 'bool' object is not iterable
$
This seems to be a consequence of switching the default python version
to 3.8. Running gitinspector using 3.7 continues to work.
Helmut
--- End Message ---
--- Begin Message ---
Source: gitinspector
Source-Version: 0.4.4+dfsg-7
Done: Christian Kastner
We believe that the bug you reported is fixed in the latest version of
gitinspector, 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 955...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Christian Kastner (supplier of updated gitinspector 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: Mon, 30 Mar 2020 21:33:48 +0200
Source: gitinspector
Architecture: source
Version: 0.4.4+dfsg-7
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team
Changed-By: Christian Kastner
Closes: 914572 955284
Changes:
gitinspector (0.4.4+dfsg-7) unstable; urgency=medium
.
[ Louis-Philippe Véronneau ]
* d/control: use the right name for the PAPT.
.
[ Debian Janitor ]
* debian/copyright: use spaces rather than tabs to start continuation
lines.
* Set upstream metadata fields: Bug-Database, Bug-Submit.
.
[ Christian Kastner ]
* Add Drop-superfluous-argument-to-NullTranslations.install.patch.
Fixes instant crash with Python 3.8. (Closes: #955284)
* d/control: Set Rules-Requires-Root to no
* Bump Standards-Version to 4.5.0
* Add superficial autopkgtests
* Update Use-jQuery-libraries-from-the-Debian-archive.patch.
(Closes: #914572)
* Add Drop-bufsize-argument-to-Popen.patch
* Add Repository{,-Browse} to upstream metadata
Checksums-Sha1:
47478ea4be3f2adc6932194eb913ca2dc3e65d98 2199 gitinspector_0.4.4+dfsg-7.dsc
b86c4c8c02df433e9aff73eb4f944207f7e164ac 16620
gitinspector_0.4.4+dfsg-7.debian.tar.xz
a97ba2f054a2a9ff3f7790c0db7979feb2ffd915 5875
gitinspector_0.4.4+dfsg-7_source.buildinfo
Checksums-Sha256:
7f83361455e621d2ff1d7152bcfe20d6551bb0e2bbb05c6fd71ba52043b4b23c 2199
gitinspector_0.4.4+dfsg-7.dsc
8533b4ec848de259b246ac304caa535f0e187bf9f68d5c674dd418e7e7398645 16620
gitinspector_0.4.4+dfsg-7.debian.tar.xz
485ce85c844d21f9a65083a5069e59eba73aa3b0e34c72b6e4c5a51bede87994 5875
gitinspector_0.4.4+dfsg-7_source.buildinfo
Files:
eff54b370f650450d2ea03e7ba1040d5 2199 vcs optional
gitinspector_0.4.4+dfsg-7.dsc
21b90211a565ab8a7f5ae3aa3034cf6c 16620 vcs optional
gitinspector_0.4.4+dfsg-7.debian.tar.xz
bc64302cba9bc6e095111c3fa6ce9cd8 5875 vcs opt
Bug#954018: marked as done (src:refpolicy: fails to migrate to testing for too long)
Your message dated Mon, 30 Mar 2020 20:33:35 + with message-id and subject line Bug#954018: fixed in refpolicy 2:2.20190201-7.1 has caused the Debian Bug report #954018, regarding src:refpolicy: fails to migrate to testing for too long 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.) -- 954018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954018 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: refpolicy Version: 2:2.20190201-6 Severity: serious Control: fixed -1 2:2.20190201-7 Tags: sid bullseye pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:refpolicy in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=refpolicy signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: refpolicy Source-Version: 2:2.20190201-7.1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of refpolicy, 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. Paul Gevers (supplier of updated refpolicy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 15 Mar 2020 20:28:12 +0100 Source: refpolicy Architecture: source Version: 2:2.20190201-7.1 Distribution: unstable Urgency: medium Maintainer: Debian SELinux maintainers Changed-By: Paul Gevers Closes: 954018 Changes: refpolicy (2:2.20190201-7.1) unstable; urgency=medium . * Non-maintainer upload. * source only upload to enable migration (Closes: #954018) Checksums-Sha1: 42afba8184ef7deff02ca951a2bcee514571445f 2232 refpolicy_2.20190201-7.1.dsc 39448028e9bd420de6f2722fdc46d3dca16ae5b8 76516 refpolicy_2.20190201-7.1.debian.tar.xz Checksums-Sha256: acde8b08fc5f6c033af0c15e9fe45ad9d85744e2eae2a6a7819cc71d80cc3f82 2232 refpolicy_2.20190201-7.1.dsc 5e26b14d8163ca91b6762e906906d328bde0e3ba9e8acd992edd60a3a01ae00b 76516 refpolicy_2.20190201-7.1.debian.tar.xz Files: dfa50759cc95f62ab046ade392773612 2232 admin optional refpolicy_2.20190201-7.1.dsc 696c4c56066bc501f4acee8b81342695 76516 admin optional refpolicy_2.20190201-7.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl5uggQACgkQnFyZ6wW9 dQpvAQf+Nb5eyBWpTKO0/wgHNTJZ/29F8x2OhMy5JNBkQ4qUmkd61dZ5SDI6xDRO 5REWjqvalbGDy3R+TR3x/uKD6mXCxWGCy4o29jTY81M1joqveFt0M5UTgh8Z+C1C CdqHgupiYFQRPtdxC1HBfEsc7iGCFeaJqyx7IRpCTP0xrjubnaAsuQv2qBLZiQkn o7MZsauL2OdgZ1V9uztvm6fRguTT8tZZGCm4j30KUaMqf2/EDuCKYA/nXFi3SIsV 5p2uq3m3wWgCkV6BfSU4UdphmfFQ+G
Bug#954511: Can someone habe a look at bioperl-run in connection with kalign (was: bioperl-run is marked for autoremoval from testing]
Hi, Yes, Kalign is on v3 now. I've pushed some patches to fix this bug. All build-time tests pass now. Autopkgtests don't, however, but that issue seems to be unrelated. Please take a look at https://salsa.debian.org/med-team/bioperl-run and verify the patches. This is my first time working with quilt patches so apologies if I did something wrong. Regards, Pranav On Mon, Mar 30, 2020 at 8:23 PM Christopher Fields wrote: > I have seen per exit codes of 256 for other bioperl-run wrappers in the > past where the application API changed (constant game of playing catchup > unfortunately). That seems to be the case here based on the error. Is > kalign is now at v3? > > chris > > On 3/30/20, 2:57 AM, "Andreas Tille" wrote: > > Control: tags -1 help > > Hi, > > currently bioperl-run fails. I think the issue is: > > > > # Failed test 'Code tested only on kalign versions >= 2' > > # at t/Kalign.t line 23. > > # got: '' > > # expected: '1' > > [2020-03-22 03:18:02] : ERROR : Input alignment format could not > be detected. (rwalign.c line 314) > > [2020-03-22 03:18:02] : ERROR : Function > "detect_alignment_format(b, &type)" failed. (rwalign.c line 187) > > [2020-03-22 03:18:02] : ERROR : Function "tmp_msa = > read_input(param->infile[i],tmp_msa)" failed. (run_kalign.c line 383) > > [2020-03-22 03:18:02] : ERROR : Function "run_kalign(param)" > failed. (run_kalign.c line 353) > > > > - WARNING - > > MSG: Kalign call crashed: 256 [command /usr/bin/kalign -in > t/data/cysprot.fa -out /tmp/ilV8fEWBHj/nJrv_GQaDU] > > > but please double check. Could someone have a look please? > > Kind regards > >Andreas. > > - Forwarded message from Debian testing autoremoval watch < > nore...@release.debian.org> - > > Date: Mon, 30 Mar 2020 04:39:17 + > From: Debian testing autoremoval watch > To: bioperl-...@packages.debian.org > Subject: bioperl-run is marked for autoremoval from testing > > bioperl-run 1.7.3-3 is marked for autoremoval from testing on > 2020-05-05 > > It is affected by these RC bugs: > 954511: bioperl-run: FTBFS: dh_auto_test: error: perl Build test > --verbose 1 returned exit code 255 > > > ___ > Debian-med-packaging mailing list > debian-med-packag...@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging > > - End forwarded message - > > -- > http://fam-tille.de > > > ᐧ
Bug#934949: clips: diff for NMU version 6.30-4.1
Package: clips Version: 6.30-4 Severity: normal Tags: patch pending Dear maintainer, I've prepared an NMU for clips (versioned as 6.30-4.1) and uploaded it to mentors. Please feel free to tell me if I should remove it. Regards. Håvard diff -Nru clips-6.30/debian/changelog clips-6.30/debian/changelog --- clips-6.30/debian/changelog 2017-11-06 22:20:23.0 +0100 +++ clips-6.30/debian/changelog 2020-03-30 20:51:48.0 +0200 @@ -1,3 +1,14 @@ +clips (6.30-4.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix typo in maintainer address closes: #881009 + * Don't build html files in doc package, so we can remove pdf2htmlex +as build-dependency. closes: #952621, #934949 +- Remove Format: HTML in *.doc-base files +- Edit Makefile in clips_docs.diff + + -- Håvard Flaget Aasen Mon, 30 Mar 2020 20:51:48 +0200 + clips (6.30-4) unstable; urgency=medium * Move pdf2htmlex, sharutils to Build-Depends (Closes: #878841) diff -Nru clips-6.30/debian/clips-doc.doc-base.abstracts clips-6.30/debian/clips-doc.doc-base.abstracts --- clips-6.30/debian/clips-doc.doc-base.abstracts 2017-10-17 23:01:32.0 +0200 +++ clips-6.30/debian/clips-doc.doc-base.abstracts 2020-03-30 20:35:09.0 +0200 @@ -7,7 +7,3 @@ Format: PDF Files: /usr/share/doc/clips-doc/application_abstracts.pdf.gz - -Format: HTML -Index: /usr/share/doc/clips-doc/application_abstracts.html -Files: /usr/share/doc/clips-doc/application_abstracts.html diff -Nru clips-6.30/debian/clips-doc.doc-base.apg clips-6.30/debian/clips-doc.doc-base.apg --- clips-6.30/debian/clips-doc.doc-base.apg 2017-10-17 23:01:35.0 +0200 +++ clips-6.30/debian/clips-doc.doc-base.apg 2020-03-30 20:35:21.0 +0200 @@ -8,7 +8,3 @@ Format: PDF Files: /usr/share/doc/clips-doc/advanced_programming_guide.pdf.gz - -Format: HTML -Index: /usr/share/doc/clips-doc/advanced_programming_guide.html -Files: /usr/share/doc/clips-doc/advanced_programming_guide.html diff -Nru clips-6.30/debian/clips-doc.doc-base.architecture clips-6.30/debian/clips-doc.doc-base.architecture --- clips-6.30/debian/clips-doc.doc-base.architecture 2017-10-17 23:01:39.0 +0200 +++ clips-6.30/debian/clips-doc.doc-base.architecture 2020-03-30 20:35:31.0 +0200 @@ -10,7 +10,3 @@ Format: PDF Files: /usr/share/doc/clips-doc/architecture_manual_v5_1.pdf.gz - -Format: HTML -Index: /usr/share/doc/clips-doc/architecture_manual_v5_1.html -Files: /usr/share/doc/clips-doc/architecture_manual_v5_1.html diff -Nru clips-6.30/debian/clips-doc.doc-base.bpg clips-6.30/debian/clips-doc.doc-base.bpg --- clips-6.30/debian/clips-doc.doc-base.bpg 2017-10-17 23:01:41.0 +0200 +++ clips-6.30/debian/clips-doc.doc-base.bpg 2020-03-30 20:35:42.0 +0200 @@ -7,7 +7,3 @@ Format: PDF Files: /usr/share/doc/clips-doc/basic_programming_guide.pdf.gz - -Format: HTML -Index: /usr/share/doc/clips-doc/basic_programming_guide.html -Files: /usr/share/doc/clips-doc/basic_programming_guide.html diff -Nru clips-6.30/debian/clips-doc.doc-base.ig clips-6.30/debian/clips-doc.doc-base.ig --- clips-6.30/debian/clips-doc.doc-base.ig 2017-10-17 23:01:44.0 +0200 +++ clips-6.30/debian/clips-doc.doc-base.ig 2020-03-30 20:35:55.0 +0200 @@ -7,7 +7,3 @@ Format: PDF Files: /usr/share/doc/clips-doc/interfaces_guide.pdf.gz - -Format: HTML -Index: /usr/share/doc/clips-doc/interfaces_guide.html -Files: /usr/share/doc/clips-doc/interfaces_guide.html diff -Nru clips-6.30/debian/clips-doc.doc-base.usrguide clips-6.30/debian/clips-doc.doc-base.usrguide --- clips-6.30/debian/clips-doc.doc-base.usrguide 2017-10-17 23:01:47.0 +0200 +++ clips-6.30/debian/clips-doc.doc-base.usrguide 2020-03-30 20:36:08.0 +0200 @@ -8,7 +8,3 @@ Format: PDF Files: /usr/share/doc/clips-doc/users_guide.pdf.gz - -Format: HTML -Index: /usr/share/doc/clips-doc/users_guide.html -Files: /usr/share/doc/clips-doc/users_guide.html diff -Nru clips-6.30/debian/control clips-6.30/debian/control --- clips-6.30/debian/control 2017-11-06 22:20:18.0 +0100 +++ clips-6.30/debian/control 2020-03-30 20:01:40.0 +0200 @@ -1,8 +1,8 @@ Source: clips Section: interpreters Priority: optional -Maintainer: Javier Fernández-Sanguino Peña -Build-Depends: libncurses-dev, debhelper (>= 10~), pdf2htmlex, sharutils +Maintainer: Javier Fernández-Sanguino Peña +Build-Depends: libncurses-dev, debhelper (>= 10~), sharutils Standards-Version: 4.1.1 Homepage: http://www.clipsrules.net/ diff -Nru clips-6.30/debian/patches/clips_docs.diff clips-6.30/debian/patches/clips_docs.diff --- clips-6.30/debian/patches/clips_docs.diff 2017-10-17 00:34:21.0 +0200 +++ clips-6.30/debian/patches/clips_docs.diff 2020-03-30 20:51:48.0 +0200 @@ -27,7 +27,7 @@ +ENCODED_DOCS = $(PDF_DOCS:.pdf=.pdf.uu) +HTML_DOCS = $(PDF_DOCS:.pdf=.html) + -+all: $(PDF_DOCS) $(HTML_DOCS) ++all: $(PDF_DOCS) +all-encoded: $(ENCODED_DOCS) + +# Rule to update the documentation
Bug#954676: pasdoc: FTBFS: dh_installman: error: Could not determine section for ./pasdoc.1
Hi Michalis,
On 30-03-2020 14:11, Michalis Kamburelis wrote:
> Do we know what the message "Could not determine section for" means,
> or how to investigate it? I mean, this manpage should go to section 1
> ("User Commands"), which is indicated both by the filename "pasdoc.1"
> and by text inside "pasdoc(1)". Why does the dh_installman not catch
> it?
I don't know but if nobody does, I'll figure it out. I consider this a
stupid regression of help2man and/or dh_installman, but there's probably
a reason.
> If necessary, I can easily create a proper manpage upstream (that
> would be available in our repository, without the need for help2man),
> I just need to know what is exactly required / necessary to avoid :)
Let's not go that route unless you as upstream really want to support a
proper man page. I mean, apparently you never really consider the
program to lack a dedicated man page. Obviously if you think otherwise
because of this issue, feel free to draft (and maintain) a man page
upstream, but otherwise I am totally happy to ship a man page created
with help2man. I assume you do maintain the --help option.
Paul
signature.asc
Description: OpenPGP digital signature
Bug#955135: marked as done (TypeError: '<' not supported between instances of 'NotImplementedType' and 'int')
Your message dated Mon, 30 Mar 2020 19:33:41 +
with message-id
and subject line Bug#955135: fixed in unattended-upgrades 2.1
has caused the Debian Bug report #955135,
regarding TypeError: '<' not supported between instances of
'NotImplementedType' and 'int'
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.)
--
955135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955135
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: unattended-upgrades
Version: 2.0
Severity: normal
I've been seeing the following errors in my logs for a few days:
Mar 27 06:38:16 hostname apt.systemd.daily[1664925]: Traceback (most recent
call last):
Mar 27 06:38:16 hostname apt.systemd.daily[1664925]: File
"/usr/bin/unattended-upgrade", line 2512, in
Mar 27 06:38:16 hostname apt.systemd.daily[1664925]: sys.exit(main(options))
Mar 27 06:38:16 hostname apt.systemd.daily[1664925]: File
"/usr/bin/unattended-upgrade", line 1986, in main
Mar 27 06:38:16 hostname apt.systemd.daily[1664925]: res = run(options,
rootdir, mem_log, logfile_dpkg,
Mar 27 06:38:16 hostname apt.systemd.daily[1664925]: File
"/usr/bin/unattended-upgrade", line 2157, in run
Mar 27 06:38:16 hostname apt.systemd.daily[1664925]: pkgs_to_upgrade =
calculate_upgradable_pkgs(cache, options)
Mar 27 06:38:16 hostname apt.systemd.daily[1664925]: File
"/usr/bin/unattended-upgrade", line 1747, in calculate_upgradable_pkgs
Mar 27 06:38:16 hostname apt.systemd.daily[1664925]: try_to_upgrade(pkg,
Mar 27 06:38:16 hostname apt.systemd.daily[1664925]: File
"/usr/bin/unattended-upgrade", line 1706, in try_to_upgrade
Mar 27 06:38:16 hostname apt.systemd.daily[1664925]:
cache.mark_upgrade_adjusted(pkg, from_user=not pkg.is_auto_installed)
Mar 27 06:38:16 hostname apt.systemd.daily[1664925]: File
"/usr/bin/unattended-upgrade", line 438, in mark_upgrade_adjusted
Mar 27 06:38:16 hostname apt.systemd.daily[1664925]:
self.call_adjusted(apt.package.Package.mark_upgrade, pkg, **kwargs)
Mar 27 06:38:16 hostname apt.systemd.daily[1664925]: File
"/usr/bin/unattended-upgrade", line 405, in call_adjusted
Mar 27 06:38:16 hostname apt.systemd.daily[1664925]:
self.adjust_candidate(self[dep])
Mar 27 06:38:16 hostname apt.systemd.daily[1664925]: File
"/usr/bin/unattended-upgrade", line 345, in adjust_candidate
Mar 27 06:38:16 hostname apt.systemd.daily[1664925]: if new_cand <
pkg.candidate:
Mar 27 06:38:16 hostname apt.systemd.daily[1664925]: File
"/usr/lib/python3/dist-packages/apt/package.py", line 514, in __lt__
Mar 27 06:38:16 hostname apt.systemd.daily[1664925]: return
self._cmp(other) < 0
Mar 27 06:38:16 hostname apt.systemd.daily[1664925]: TypeError: '<' not
supported between instances of 'NotImplementedType' and 'int'
Francois
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_CA.utf8, LC_CTYPE=fr_CA.utf8 (charmap=UTF-8),
LANGUAGE=fr_CA.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages unattended-upgrades depends on:
ii debconf [debconf-2.0] 1.5.73
ii lsb-base 11.1.0
ii lsb-release11.1.0
ii python33.8.2-2
ii python3-apt1.9.10
ii python3-dbus 1.2.16-1
ii python3-distro-info0.23
ii ucf3.0038+nmu1
ii xz-utils 5.2.4-1+b1
Versions of packages unattended-upgrades recommends:
ii anacron 2.3-29
ii cron [cron-daemon] 3.0pl1-136
ii systemd-sysv245.2-1
Versions of packages unattended-upgrades suggests:
ii bsd-mailx 8.1.2-0.20180807cvs-1+b1
ii needrestart 3.4-6
ii postfix [mail-transport-agent] 3.5.0-1
ii powermgmt-base 1.36
ii python3-gi 3.36.0-1
-- debconf information:
unattended-upgrades/origins_pattern:
"origin=Debian,codename=${distro_codename},label=Debian-Security";
unattended-upgrades/enable_auto_updates: true
--
https://fmarier.org/
--- End Message ---
--- Begin Message ---
Source: unattended-upgrades
Source-Version: 2.1
Done: Balint Reczey
We believe that the bug you reported is fixed in the latest version of
unattended-upgrades, which is due to be installed in the Debian FTP archive.
A summary of the changes between
Bug#953970: Taking over DPMT (Was: python-boto: autopkgtest failure with Python 3.8 as default)
On Mon, Mar 30, 2020 at 11:18:34AM -0400, Noah Meyerhans wrote: > On Mon, Mar 30, 2020 at 11:44:23AM +0200, Andreas Tille wrote: > > I wonder whether we should take over python-boto into DPMT maintenance > > which would enable commits to Git way more easily. > > If it's going to move, might I suggest maintaining it within the > cloud-team instead? Among other things, the cloud team has an interest > in providing feature updates to cloud-oriented packages, such as > python-boto, in stable point releases. Having the team maintain these > packages, as we do with other packages such as cloud-init, would help us > with this goal. I personally don't mind about the team that takes over as long as its more than a single person. Salvaging criteria https://wiki.debian.org/PackageSalvaging are fulfilled but I personally prefer if the maintainer does the move and transfers the Salsa git repository (as described here[1]). Kind regards Andreas. [1] https://docs.gitlab.com/ee/user/project/settings/ -- http://fam-tille.de
Bug#954698: serf: FTBFS: 1) test_ssltunnel_basic_auth_server_has_keepalive_off: test/test_context.c:2138: expected <0> but was <120199>
Here's a tentative patch that causes the test cases to pass with OpenSSL
1.1.1e+ for me on Debian Sid.
James, can you please give it a go and confirm that it works for you?
Before I commit, we'd also need to gate this based on the new OpenSSL
constant. We could gate based upon the OpenSSL version number, but I think
if we can confine to this one area, gating based on ifdef is likely prudent.
I'd also like to get the scons patch you sent earlier into a new release.
I'm hopeful that I can cut a new 1.3 release sometime this week and have
others vote on it - that should make your downstream efforts a bit easier.
As I mentioned earlier, I may also try to add a new test case that confirms
that the client can handle a premature EOF from server-side without
erroring out as that is the more interesting case from Serf's
perspective...though, I think I may try to just get a new 1.3 out first.
If it does fail in that case (and I can get around to mocking it up), we
might have to do a fast-follow with another release if it doesn't alter the
API in any meaningful manner.
Cheers. -- justin
--- ../../serf-1.3.9/test/server/test_sslserver.c 2016-06-30
11:45:07.0 -0400
+++ test/server/test_sslserver.c2020-03-30 14:41:20.773365217 -0400
@@ -424,6 +424,11 @@
*len = 0;
return APR_EAGAIN;
case SSL_ERROR_SSL:
+ if (ERR_GET_REASON(ERR_peek_error()) ==
SSL_R_UNEXPECTED_EOF_WHILE_READING) {
+*len = 0;
+return APR_EOF;
+ }
+ /* Fallthrough */
default:
*len = 0;
serf__log(TEST_VERBOSE, __FILE__,
On Sat, Mar 28, 2020 at 9:49 AM Justin Erenkrantz
wrote:
> Ok, I was finally able to reproduce this with Debian sid's serf 1.3 source
> packages.
>
> In short, I went down a wild goose chase - as it's actually the test
> harness (our mock server) that is returning this SSL error - not serf
> itself.
>
> The test suite isn't handling the new SSL_ERROR_SSL return code when the
> *client* (eg serf) disconnects as the test case only wants to send one
> request and then closes the connection. So, we likely just need to ignore
> the returned SSL_ERROR_SSL in this case - I'm still trying to figure out
> how we can distinguish that EOF case from a general SSL (probably
> SSL_R_UNEXPECTED_EOF_WHILE_READING); but, I'm timing out on my cycles right
> now.
>
> I'd actually like to see if I can create a test case where the *server*
> disconnects abnormally over SSL and ensure that Serf handles it
> appropriately. (I haven't yet checked to confirm that we have this case
> already; but, it'd likely be relatively straightforward to do this.)
>
> Cheers. -- justin
>
> P.S. Note to future self and others:
> https://wiki.debian.org/HowToGetABacktrace and
> https://wiki.debian.org/BuildingTutorial#Get_the_source_package were
> useful. I ultimately needed the libssl1.1-dbgsym package; then I was able
> to break on the ssl3_read_n call and see the callstack.
>
> On Fri, Mar 27, 2020 at 5:56 PM Lucas Nussbaum wrote:
>
>> Hi Justin,
>>
>> Most likely, this is due to the new openssl version in unstable.
>>
>> Lucas
>>
>>
>> On 27/03/20 at 17:15 -0400, Justin Erenkrantz wrote:
>> > James,
>> >
>> > I finally got a Debian sid environment up. However, I'm seeing a
>> different
>> > sets of test failures right now against vanilla serf 1.4.x and trunk
>> (which
>> > works with the scons/python3 in sid without a patch AFAICT) - this is
>> with
>> > 1.4.x branch:
>> >
>> > ---
>> >
>> > == Running the unit tests ==
>> >
>> >
>> ...F..F..FFF.F.
>> >
>> > There were 6 failures:
>> >
>> > 1) test_ssl_handshake_nosslv2: test/test_ssl.c:589: Serf does not
>> disable
>> > SSLv2, but it should!
>> >
>> > 2) test_ssl_missing_client_certificate: test/test_ssl.c:1925: expected
>> > <120172> but was <120171>
>> >
>> > 3) test_ssl_server_cert_with_cn_nul_byte: test/test_util.c:551: expected
>> > <0> but was <120199>
>> >
>> > 4) test_ssl_server_cert_with_san_nul_byte: test/test_util.c:551:
>> expected
>> > <0> but was <120199>
>> >
>> > 5) test_ssl_server_cert_with_cnsan_nul_byte: test/test_util.c:551:
>> expected
>> > <0> but was <120199>
>> >
>> > 6) test_ssl_renegotiate: test/test_ssl.c:1881: expected <0> but was
>> <120199>
>> >
>> >
>> > !!!FAILURES!!!
>> >
>> > Runs: 127 Passes: 121 Fails: 6
>> > ---
>> >
>> > I'll try to dig into this more over the weekend, but I wonder if I'm
>> seeing
>> > something different than you (or the builder) are...I'll also try to
>> pull
>> > in your patch set against vanilla 1.3.x to see if I can match the
>> reported
>> > error.
>> >
>> > Cheers. -- justin
>> >
>> > On Wed, Mar 25, 2020 at 8:17 PM James McCoy
>> wrote:
>> >
>> > > On Wed, Mar 25, 2020 at 08:57:14AM -0400, Justin Erenkrantz wrote:
>> > > > James,
>> > > >
>>
Bug#953780: marked as done (src:zip4j: fails to migrate to testing for too long)
Your message dated Mon, 30 Mar 2020 20:53:58 +0200 with message-id <74ef34de-2a9f-408c-602d-4a5d8d18a...@debian.org> and subject line Re: Bug#953780: src:zip4j: fails to migrate to testing for too long has caused the Debian Bug report #953780, regarding src:zip4j: fails to migrate to testing for too long 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.) -- 953780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953780 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zip4j Version: 2.1.3-1 Severity: serious Control: fixed -1 2.2.8-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:zip4j in its current version in unstable has been trying to migrate for 74 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=zip4j signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Hi Andrius, On 30-03-2020 12:32, mer...@debian.org wrote: > I have uploaded a new version of zip4j, and this one has successfully > migrated. However, the bug remains open - I assume it should have been > closed automatically, or am I wrong? Should I close it manually? That assumption is wrong. Closure is done by either a "Closes" in the changelog or by manual sending a message to bug-done, like I've done now. Probably someone doing QA on the BTS would have closed it in due time as the bug impacts no release anymore, but it's unnecessary to wait for that. Paul signature.asc Description: OpenPGP digital signature --- End Message ---
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 955359 + help Bug #955359 [swi-prolog] swi-prolog: FTBFS on mips: error due to ATOMIC Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 955359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937273: marked as done (pepper: Python2 removal in sid/bullseye)
Your message dated Mon, 30 Mar 2020 18:48:46 + with message-id and subject line Bug#937273: fixed in pepper 0.3.3-4 has caused the Debian Bug report #937273, regarding pepper: 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.) -- 937273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937273 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pepper Version: 0.3.3-3 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:pepper 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: pepper Source-Version: 0.3.3-4 Done: =?utf-8?q?Antoine_Beaupr=C3=A9?= We believe that the bug you reported is fixed in the latest version of pepper, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antoine Beaupré (supplier of updated pepper package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 30 Mar 2020 13:44:24 -0400 Source: pepper Architecture: source Version: 0.3.3-4 Distribution: unstable Urgency: medium Maintainer: Antoine Beaupré Changed-By: Antoine Beaupré Closes: 937273 Changes: pepper (0.3.3-4) unstable; urgency=medium . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/control: Set Vcs-* to salsa.debian.org . [ Antoine Beaupré ] * remove python dependency, dropping mercurial support until it gets py3 support (Closes: #937273) Checksums-Sha1: 8170cbbdd3cf3ca51d48e2b5444705f7ca739079 1607 pepper_0.3.3-4.dsc 579e20030267dd52cb59ec73d40e82592b765394 3588 pepper_0.3.3-4.debian.tar.xz 10159040aff6acd8b1d63df732a920e5ad1eae81 12720 pepper_0.3.3-4_amd64.buildinfo Checksums-Sha256: 8585811e65b81adcd5920d3640f589fd148146775f05dabbe17f4c972635850e 1607 pepper_0.3.3-4.dsc 92ca176402d187b4cf0dd4e85baea7a1507f6e35550dcb7b27c1705676b69d2c 3588 pepper_0.3.3-4.debian.tar.xz
Processed: bug 954079 is forwarded to https://github.com/glyph/automat/issues/118
Processing commands for cont...@bugs.debian.org: > forwarded 954079 https://github.com/glyph/automat/issues/118 Bug #954079 [automat] magic-wormhole: Fails to send with a type error Set Bug forwarded-to-address to 'https://github.com/glyph/automat/issues/118'. > thanks Stopping processing here. Please contact me if you need assistance. -- 954079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: Bug#954079: magic-wormhole: Fails to send with a type error
Processing commands for cont...@bugs.debian.org: > reassign 954079 automat Bug #954079 [magic-wormhole] magic-wormhole: Fails to send with a type error Bug reassigned from package 'magic-wormhole' to 'automat'. No longer marked as found in versions magic-wormhole/0.11.2-1. Ignoring request to alter fixed versions of bug #954079 to the same values previously set > affects 954079 magic-wormhole Bug #954079 [automat] magic-wormhole: Fails to send with a type error Added indication that 954079 affects magic-wormhole > forward 954079 https://github.com/glyph/automat/issues/118 Unknown command or malformed arguments to command. > thanks Stopping processing here. Please contact me if you need assistance. -- 954079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: yp-tools: diff for NMU version 3.3-5.3
Processing control commands: > tags 954587 + patch Bug #954587 [src:yp-tools] yp-tools: FTBFS: nis-hosts.c:232:21: error: ‘RES_USE_INET6’ undeclared (first use in this function) Added tag(s) patch. > tags 954587 + pending Bug #954587 [src:yp-tools] yp-tools: FTBFS: nis-hosts.c:232:21: error: ‘RES_USE_INET6’ undeclared (first use in this function) Added tag(s) pending. -- 954587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954587 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954587: yp-tools: diff for NMU version 3.3-5.3
Control: tags 954587 + patch
Control: tags 954587 + pending
Dear maintainer,
I've prepared an NMU for yp-tools (versioned as 3.3-5.3) and
uploaded it to mentors for sponsoring. Please feel free to tell me if I
should remove it.
--
Regards
Sudip
diff -Nru yp-tools-3.3/debian/changelog yp-tools-3.3/debian/changelog
--- yp-tools-3.3/debian/changelog 2020-02-27 21:00:19.0 +
+++ yp-tools-3.3/debian/changelog 2020-03-30 18:58:41.0 +0100
@@ -1,3 +1,10 @@
+yp-tools (3.3-5.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTBFS for RES_USE_INET6. (Closes: #954587)
+
+ -- Sudip Mukherjee Mon, 30 Mar 2020 18:58:41
+0100
+
yp-tools (3.3-5.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru yp-tools-3.3/debian/patches/fix_inet6.patch
yp-tools-3.3/debian/patches/fix_inet6.patch
--- yp-tools-3.3/debian/patches/fix_inet6.patch 1970-01-01 01:00:00.0
+0100
+++ yp-tools-3.3/debian/patches/fix_inet6.patch 2020-03-30 18:58:41.0
+0100
@@ -0,0 +1,60 @@
+Description: Fix FTBFS with RES_USE_INET6
+ RES_USE_INET6 has been removed from glibc and according to:
+
https://gitlab.com/freedesktop-sdk/mirrors/sourceware/glibc/-/commit/3f8b44be0a658266adff5ece1e4bc3ce097a5dbe
+ (_res.options & DEPRECATED_RES_USE_INET6) will return false.
+
+Author: Sudip Mukherjee
+Bug-Debian: https://bugs.debian.org/954587
+
+---
+
+--- yp-tools-3.3.orig/nss_nis6/nis-hosts.c
yp-tools-3.3/nss_nis6/nis-hosts.c
+@@ -229,8 +229,7 @@ _nss_nis6_gethostent_r (struct hostent *
+ __libc_lock_lock (lock);
+
+ status = internal_nis6_gethostent_r (host, buffer, buflen, errnop, h_errnop,
+- ((_res.options & RES_USE_INET6) ? AF_INET6 : AF_INET),
+- ((_res.options & RES_USE_INET6) ? AI_V4MAPPED : 0 ));
++ AF_INET, 0 );
+
+ __libc_lock_unlock (lock);
+
+@@ -348,8 +347,7 @@ _nss_nis6_gethostbyname2_r (const char *
+ }
+
+ return internal_gethostbyname2_r (name, af, host, buffer, buflen, errnop,
+- h_errnop,
+- ((_res.options & RES_USE_INET6) ? AI_V4MAPPED : 0));
++ h_errnop, 0);
+ }
+
+
+@@ -357,16 +355,6 @@ enum nss_status
+ _nss_nis6_gethostbyname_r (const char *name, struct hostent *host, char
*buffer,
+ size_t buflen, int *errnop, int *h_errnop)
+ {
+- if (_res.options & RES_USE_INET6)
+-{
+- enum nss_status status;
+-
+- status = internal_gethostbyname2_r (name, AF_INET6, host, buffer,
buflen,
+-errnop, h_errnop, AI_V4MAPPED);
+- if (status == NSS_STATUS_SUCCESS)
+- return status;
+-}
+-
+ return internal_gethostbyname2_r (name, AF_INET, host, buffer, buflen,
+ errnop, h_errnop, 0);
+ }
+@@ -430,9 +418,7 @@ _nss_nis6_gethostbyaddr_r (const void *a
+ ++p;
+ free (result);
+
+- int parse_res = parse_line (p, host, data, buflen, errnop, af,
+-((_res.options & RES_USE_INET6)
+- ? AI_V4MAPPED : 0));
++ int parse_res = parse_line (p, host, data, buflen, errnop, af, 0);
+ if (__glibc_unlikely (parse_res < 1))
+ {
+ if (parse_res == -1)
diff -Nru yp-tools-3.3/debian/patches/series yp-tools-3.3/debian/patches/series
--- yp-tools-3.3/debian/patches/series 2020-02-27 20:57:30.0 +
+++ yp-tools-3.3/debian/patches/series 2020-03-23 22:19:26.0 +
@@ -4,3 +4,4 @@
gcc7.patch
do_ypcall_tr-cast-align.patch
fix_ftbfs.patch
+fix_inet6.patch
Bug#954079: magic-wormhole: Fails to send with a type error
reassign 954079 automat affects 954079 magic-wormhole forward 954079 https://github.com/glyph/automat/issues/118 thanks On 2020-03-16 13:49:58, Guillem Jover wrote: > Package: magic-wormhole > Version: 0.11.2-1 > Severity: serious > > Hi! > > This package does not work anymore in unstable. I guess due to the new > python-3.8 transition? Had to use a buster schroot to be able to send > some stuff today. :) > > ,--- > $ wormhole send somedir/ > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/wormhole/cli/cli.py", line 255, in > > return react(_dispatch_command, (cfg, lambda: f(cfg))) > File "/usr/lib/python3/dist-packages/wormhole/cli/cmd_send.py", line 36, > in send > return Sender(args, reactor).go() > File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line > 1613, in unwindGenerator > return _cancellableInlineCallbacks(gen) > File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line > 1529, in _cancellableInlineCallbacks > _inlineCallbacks(None, g, status) > --- --- > File "/usr/lib/python3/dist-packages/wormhole/cli/cli.py", line 122, in > _dispatch_command > yield maybeDeferred(command) > File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line > 1418, in _inlineCallbacks > result = g.send(result) > File "/usr/lib/python3/dist-packages/wormhole/cli/cmd_send.py", line 64, > in go > w = create( > File "/usr/lib/python3/dist-packages/wormhole/wormhole.py", line 271, in > create > b = Boss(w, side, relay_url, appid, wormhole_versions, client_version, > File "", line 21, in __init__ > self.__attrs_post_init__() > File "/usr/lib/python3/dist-packages/wormhole/_boss.py", line 49, in > __attrs_post_init__ > self._build_workers() > File "/usr/lib/python3/dist-packages/wormhole/_boss.py", line 59, in > _build_workers > self._RC = RendezvousConnector(self._url, self._appid, self._side, > File "", > line 18, in __init__ > self.__attrs_post_init__() > File "/usr/lib/python3/dist-packages/wormhole/_rendezvous.py", line 88, > in __attrs_post_init__ > d = self._connector.whenConnected(failAfterFailures=faf) > File "/usr/lib/python3/dist-packages/twisted/application/internet.py", > line 1121, in whenConnected > return self._machine.whenConnected(failAfterFailures) > File "/usr/lib/python3/dist-packages/automat/_methodical.py", line 126, > in __get__ > def doInput(*args, **kwargs): > File "/usr/lib/python3/dist-packages/automat/_introspection.py", line 39, > in decorator > return copyfunction(decorated, > File "/usr/lib/python3/dist-packages/automat/_introspection.py", line 31, > in copyfunction > return function(copycode(template.__code__, codechanges), *values) > File "/usr/lib/python3/dist-packages/automat/_introspection.py", line 19, > in copycode > return code(*values) > builtins.TypeError: an integer is required (got type bytes) > ERROR: an integer is required (got type bytes) > `--- This is actually a bug in automat, not magic-wormhole, see: https://github.com/warner/magic-wormhole/issues/377 I've reassigned this bug accordingly. It seems that upgrading the automat package would fix this. A. -- La mer, cette grande unificatrice, est l'unique espoir de l'homme. Aujourd'hui plus que jamais auparavant, ce vieux dicton dit littéralement ceci: nous sommes tous dans le même bateau. - Jacques Yves Cousteau - Océanographe
Processed: bug 952041 is forwarded to https://github.com/seattlerb/hoe/issues/106
Processing commands for cont...@bugs.debian.org: > forwarded 952041 https://github.com/seattlerb/hoe/issues/106 Bug #952041 [src:ruby-hoe] ruby-hoe: FTBFS: ERROR: Test "ruby2.7" failed. Set Bug forwarded-to-address to 'https://github.com/seattlerb/hoe/issues/106'. > thanks Stopping processing here. Please contact me if you need assistance. -- 952041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952041: more information
The expected date is the current date, whereas the actual date is the same as the how.gemspec's file date (in the package it is Feb. 6th; in Git it is March 2nd. I've opened an issue to clarify the situation: https://github.com/seattlerb/hoe/issues/106 signature.asc Description: This is a digitally signed message part
Processed: [bts-link] source package python3.8
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package python3.8 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #954416 (http://bugs.debian.org/954416) > # Bug title: python3.8: FTBFS since openssl 1.1.1e > # * https://bugs.python.org/issue40018 > # * remote status changed: open -> closed > # * remote resolution changed: (?) -> wont-fix > # * closed upstream > # * upstream said bug is wontfix > tags 954416 + fixed-upstream upstream wontfix Bug #954416 [python3.8] python3.8: FTBFS since openssl 1.1.1e Added tag(s) wontfix, fixed-upstream, and upstream. > usertags 954416 - status-open Usertags were: status-open. Usertags are now: . > usertags 954416 + status-closed resolution-wont-fix There were no usertags set. Usertags are now: status-closed resolution-wont-fix. > thanks Stopping processing here. Please contact me if you need assistance. -- 954416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package systemd
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package systemd > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #954174 (http://bugs.debian.org/954174) > # Bug title: login broken for usernames starting with a number (badname) > # * https://github.com/systemd/systemd/issues/15141 > # * remote status changed: open -> closed > # * closed upstream > tags 954174 + fixed-upstream Bug #954174 [systemd] login broken for usernames starting with a number (badname) Added tag(s) fixed-upstream. > usertags 954174 - status-open Usertags were: status-open. Usertags are now: . > usertags 954174 + status-closed There were no usertags set. Usertags are now: status-closed. > # remote status report for #954755 (http://bugs.debian.org/954755) > # Bug title: systemd-fstab-generator does not recognise davfs entries in > fstab as network mounts > # * https://github.com/systemd/systemd/issues/15198 > # * remote status changed: (?) -> closed > # * closed upstream > tags 954755 + fixed-upstream Bug #954755 [systemd] systemd-fstab-generator does not recognise davfs entries in fstab as network mounts Added tag(s) fixed-upstream. > usertags 954755 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 954174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954174 954755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954755 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package python2.7
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package python2.7 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #954418 (http://bugs.debian.org/954418) > # Bug title: python2.7: FTBFS since openssl 1.1.1e > # * https://bugs.python.org/issue40018 > # * remote status changed: open -> closed > # * remote resolution changed: (?) -> wont-fix > # * closed upstream > # * upstream said bug is wontfix > tags 954418 + fixed-upstream upstream wontfix Bug #954418 [python2.7] python2.7: FTBFS since openssl 1.1.1e Added tag(s) wontfix, upstream, and fixed-upstream. > usertags 954418 - status-open Usertags were: status-open. Usertags are now: . > usertags 954418 + status-closed resolution-wont-fix There were no usertags set. Usertags are now: status-closed resolution-wont-fix. > thanks Stopping processing here. Please contact me if you need assistance. -- 954418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954418 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954541: marked as done (cmark: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2)
Your message dated Mon, 30 Mar 2020 17:18:28 +
with message-id
and subject line Bug#954541: fixed in cmark 0.29.0-2
has caused the Debian Bug report #954541,
regarding cmark: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make
-j4 test ARGS\+=-j4 returned exit code 2
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.)
--
954541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cmark
Version: 0.29.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 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 '/<>/obj-x86_64-linux-gnu'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process -j4
> Test project /<>/obj-x86_64-linux-gnu
> Start 1: api_test
> Start 2: html_normalization
> Start 3: spectest_library
> Start 4: pathological_tests_library
> 1/9 Test #1: api_test . Passed0.00 sec
> Start 5: roundtriptest_library
> 2/9 Test #3: spectest_library . Passed0.11 sec
> Start 6: entity_library
> 3/9 Test #2: html_normalization ...***Failed0.13 sec
> **
> File "/<>/test/normalize.py", line 169, in
> normalize.normalize_html
> Failed example:
> normalize_html('x')
> Exception raised:
> Traceback (most recent call last):
> File "/usr/lib/python3.8/doctest.py", line 1329, in __run
> exec(compile(example.source, filename, "single",
> File "", line 1, in
> normalize_html('x')
> File "/<>/test/normalize.py", line 189, in normalize_html
> parser.feed(chunk.group(0))
> File "/usr/lib/python3.8/html/parser.py", line 111, in feed
> self.goahead(0)
> File "/usr/lib/python3.8/html/parser.py", line 171, in goahead
> k = self.parse_starttag(i)
> File "/usr/lib/python3.8/html/parser.py", line 345, in parse_starttag
> self.handle_starttag(tag, attrs)
> File "/<>/test/normalize.py", line 69, in handle_starttag
> self.output += ("=" + '"' + cgi.escape(v,quote=True) + '"')
> AttributeError: module 'cgi' has no attribute 'escape'
> **
> 1 items had failures:
>1 of 10 in normalize.normalize_html
> ***Test Failed*** 1 failures.
>
> Start 7: spectest_executable
> 4/9 Test #5: roundtriptest_library ***Failed0.14 sec
> Traceback (most recent call last):
> File "/<>/test/roundtrip_tests.py", line 45, in
> do_test(converter, test, args.normalize, result_counts)
> File "/<>/test/spec_tests.py", line 48, in do_test
> passed = normalize_html(actual_html) == normalize_html(expected_html)
> File "/<>/test/normalize.py", line 189, in normalize_html
> parser.feed(chunk.group(0))
> File "/usr/lib/python3.8/html/parser.py", line 111, in feed
> self.goahead(0)
> File "/usr/lib/python3.8/html/parser.py", line 171, in goahead
> k = self.parse_starttag(i)
> File "/usr/lib/python3.8/html/parser.py", line 345, in parse_starttag
> self.handle_starttag(tag, attrs)
> File "/<>/test/normalize.py", line 69, in handle_starttag
> self.output += ("=" + '"' + cgi.escape(v,quote=True) + '"')
> AttributeError: module 'cgi' has no attribute 'escape'
>
> Start 8: smartpuncttest_executable
> 5/9 Test #6: entity_library ... Passed0.08 sec
> Start 9: regressiontest_executable
> 6/9 Test #8: smartpuncttest_executable Passed0.11 sec
> 7/9 Test #9: regressiontest_executable Passed0.09 sec
> 8/9 Test #7: spectest_executable .. Passed0.80 sec
> 9/9 Test #4: pathological_tests_library ... Passed1.14 sec
>
> 78% tests passed, 2 tests failed out of 9
>
> Total Test time (real) = 1.14 sec
>
> The following tests FAILED:
> 2 - html_normalization (Failed)
> 5 - roundtriptest_library (Failed)
> Errors while running CTest
> make[1]: *** [Makefile:133: test] Error 8
> make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4
> returned exit code 2
The full build log is available from:
http://qa-logs.debian.net/2020/03/21/cmark_0.29.0-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.o
Processed: [bts-link] source package ruby-excon
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package ruby-excon > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #951889 (http://bugs.debian.org/951889) > # Bug title: ruby-excon 0.72 breaks ruby-vcr > # * https://github.com/vcr/vcr/issues/801 > # * remote status changed: open -> closed > # * closed upstream > tags 951889 + fixed-upstream Bug #951889 [ruby-excon] ruby-excon 0.72 breaks ruby-vcr Added tag(s) fixed-upstream. > usertags 951889 - status-open Usertags were: status-open. Usertags are now: . > usertags 951889 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 951889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package python3.7
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package python3.7 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #954417 (http://bugs.debian.org/954417) > # Bug title: python3.7: FTBFS since openssl 1.1.1e > # * https://bugs.python.org/issue40018 > # * remote status changed: open -> closed > # * remote resolution changed: (?) -> wont-fix > # * closed upstream > # * upstream said bug is wontfix > tags 954417 + fixed-upstream upstream wontfix Bug #954417 [python3.7] python3.7: FTBFS since openssl 1.1.1e Added tag(s) fixed-upstream, wontfix, and upstream. > usertags 954417 - status-open Usertags were: status-open. Usertags are now: . > usertags 954417 + status-closed resolution-wont-fix There were no usertags set. Usertags are now: resolution-wont-fix status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 954417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#951979: antimony: diff for NMU version 0.9.3-1.2
Control: tags 951979 + patch
Control: tags 951979 + pending
Dear maintainer,
I've prepared an NMU for antimony (versioned as 0.9.3-1.2) and
uploaded it to mentors. Please feel free to tell me if I
should remove it.
Regards.
Håvard
diff -Nru antimony-0.9.3/debian/changelog antimony-0.9.3/debian/changelog
--- antimony-0.9.3/debian/changelog 2020-01-06 10:39:41.0 +0100
+++ antimony-0.9.3/debian/changelog 2020-03-30 18:27:18.0 +0200
@@ -1,3 +1,10 @@
+antimony (0.9.3-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add 0003-Change-python-variable-in-cmake.patch closes: #951979
+
+ -- Håvard Flaget Aasen Mon, 30 Mar 2020 18:27:18 +0200
+
antimony (0.9.3-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru antimony-0.9.3/debian/patches/0003-Change-python-variable-in-cmake.patch antimony-0.9.3/debian/patches/0003-Change-python-variable-in-cmake.patch
--- antimony-0.9.3/debian/patches/0003-Change-python-variable-in-cmake.patch 1970-01-01 01:00:00.0 +0100
+++ antimony-0.9.3/debian/patches/0003-Change-python-variable-in-cmake.patch 2020-03-30 18:26:23.0 +0200
@@ -0,0 +1,67 @@
+From: =?utf-8?q?H=C3=A5vard_Flaget_Aasen?=
+Date: Fri, 27 Mar 2020 19:52:14 +0100
+Subject: Change python variable in cmake
+
+---
+ app/CMakeLists.txt | 2 +-
+ lib/fab/CMakeLists.txt | 4 ++--
+ lib/graph/CMakeLists.txt | 4 ++--
+ 3 files changed, 5 insertions(+), 5 deletions(-)
+
+diff --git a/app/CMakeLists.txt b/app/CMakeLists.txt
+index cf950d3..779 100644
+--- a/app/CMakeLists.txt
b/app/CMakeLists.txt
+@@ -175,7 +175,7 @@ add_definitions(-D'GITREV="${GITREV}${GITDIFF}"'
+
+
+ target_include_directories(${ANTIMONY_APP} SYSTEM PRIVATE
+-${Python_INCLUDE_DIR}
++${Python_INCLUDE_DIRS}
+ ${Boost_INCLUDE_DIRS}
+ ${AUTOGEN_TARGETS_FOLDER}
+ )
+diff --git a/lib/fab/CMakeLists.txt b/lib/fab/CMakeLists.txt
+index 2f21731..7c0596c 100644
+--- a/lib/fab/CMakeLists.txt
b/lib/fab/CMakeLists.txt
+@@ -67,7 +67,7 @@ add_library(SbFab STATIC
+ )
+
+ target_include_directories(SbFab SYSTEM PRIVATE
+-${Python_INCLUDE_DIR}
++${Python_INCLUDE_DIRS}
+ ${Boost_INCLUDE_DIRS}
+ ${PNG_INCLUDE_DIR}
+ )
+@@ -98,7 +98,7 @@ target_link_libraries(SbFabTest SbFab)
+ target_include_directories(SbFabTest SYSTEM PRIVATE
+ ../../vendor
+ ${Boost_INCLUDE_DIRS}
+-${Python_INCLUDE_DIR}
++${Python_INCLUDE_DIRS}
+ )
+
+
+diff --git a/lib/graph/CMakeLists.txt b/lib/graph/CMakeLists.txt
+index 31f7878..d04cc83 100644
+--- a/lib/graph/CMakeLists.txt
b/lib/graph/CMakeLists.txt
+@@ -15,7 +15,7 @@ add_library(SbGraph STATIC
+ )
+
+ target_include_directories(SbGraph SYSTEM PRIVATE
+-${Python_INCLUDE_DIR}
++${Python_INCLUDE_DIRS}
+ ${Boost_INCLUDE_DIRS}
+ )
+ target_link_libraries(SbGraph
+@@ -38,7 +38,7 @@ add_executable(SbGraphTest
+ target_link_libraries(SbGraphTest SbGraph)
+
+ target_include_directories(SbGraphTest SYSTEM PRIVATE
+-${Python_INCLUDE_DIR}
++${Python_INCLUDE_DIRS}
+ ${Boost_INCLUDE_DIRS}
+ ../../vendor
+ )
diff -Nru antimony-0.9.3/debian/patches/series antimony-0.9.3/debian/patches/series
--- antimony-0.9.3/debian/patches/series 2020-01-06 09:29:43.0 +0100
+++ antimony-0.9.3/debian/patches/series 2020-03-30 18:26:23.0 +0200
@@ -1,2 +1,3 @@
bugged_parsercheck
0002-Use-new-CMake-Python-discovery-with-matching-Boost-P.patch
+0003-Change-python-variable-in-cmake.patch
Bug#936366: marked as done (darkradiant: Python2 removal in sid/bullseye)
Your message dated Mon, 30 Mar 2020 17:03:31 + with message-id and subject line Bug#936366: fixed in darkradiant 2.7.0-1 has caused the Debian Bug report #936366, regarding darkradiant: 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.) -- 936366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:darkradiant Version: 2.6.0-3 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:darkradiant 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: darkradiant Source-Version: 2.7.0-1 Done: Tobias Frost We believe that the bug you reported is fixed in the latest version of darkradiant, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Frost (supplier of updated darkradiant package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 30 Mar 2020 18:47:45 +0200 Source: darkradiant Architecture: source Version: 2.7.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Tobias Frost Closes: 936366 Changes: darkradiant (2.7.0-1) unstable; urgency=medium . * New upstream release. * remove patches, all patches applied upstream: - 02_spelling_errors.patch - 03_c++17_filesystem.patch * Cherry-Pick python3 patch from upstream and B-D on python3-dev. Thanks to greebo for the hint! (Closes: #936366) * Install generated documents and register with doc-base. * Update d/copyright. * Bump S-V to 4.5.0 -- no changes required Checksums-Sha1: d0617bc9b77bfc163b31b6485a80248a8ed8330a 2381 darkradiant_2.7.0-1.dsc 346364f90380481857187bb490b754150b72f6ef 5733593 darkradiant_2.7.0.orig.tar.gz 8c2ebbf298d5d122d667ce2e7d514278ee3a8c3e 11760 darkradiant_2.7.0-1.debian.tar.xz 66d2b848abf059c5a3100956e8
Processed: antimony: diff for NMU version 0.9.3-1.2
Processing control commands: > tags 951979 + patch Bug #951979 [src:antimony] antimony: FTBFS: datum.h:3:10: fatal error: Python.h: No such file or directory Added tag(s) patch. > tags 951979 + pending Bug #951979 [src:antimony] antimony: FTBFS: datum.h:3:10: fatal error: Python.h: No such file or directory Added tag(s) pending. -- 951979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951979 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#936366: marked as pending in darkradiant
Control: tag -1 pending Hello, Bug #936366 in darkradiant 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/games-team/darkradiant/-/commit/3bcdf13fcbec29be1398f685d86d984628529505 Cherry-Pick python3 patch from upstream and B-D on python3-dev. Thanks to greebo for the hint! (Closes: #936366) Also use python3-config explicitly. (this message was generated automatically) -- Greetings https://bugs.debian.org/936366
Processed: Bug#936366 marked as pending in darkradiant
Processing control commands: > tag -1 pending Bug #936366 [src:darkradiant] darkradiant: Python2 removal in sid/bullseye Ignoring request to alter tags of bug #936366 to the same tags previously set -- 936366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952267: marked as done (fsplib: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Mon, 30 Mar 2020 16:33:37 + with message-id and subject line Bug#952267: fixed in fsplib 0.14-2 has caused the Debian Bug report #952267, regarding fsplib: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 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.) -- 952267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952267 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fsplib Version: 0.14-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 '/<>' > scons -c enable-shared=1 > scons: Reading SConscript files ... > Checking whether gcc supports -Wall... yes > Checking whether gcc supports -W... yes > Checking whether gcc supports -Wstrict-prototypes... yes > Checking whether gcc supports -Wmissing-prototypes... yes > Checking whether gcc supports -Wshadow... yes > Checking whether gcc supports -Wbad-function-cast... yes > Checking whether gcc supports -Wcast-qual... yes > Checking whether gcc supports -Wcast-align... yes > Checking whether gcc supports -Wwrite-strings... yes > Checking whether gcc supports -Waggregate-return... yes > Checking whether gcc supports -Wmissing-declarations... yes > Checking whether gcc supports -Wmissing-format-attribute... yes > Checking whether gcc supports -Wnested-externs... yes > Checking whether gcc supports -ggdb... yes > Checking whether gcc supports -fno-common... yes > Checking whether gcc supports -Wchar-subscripts... yes > Checking whether gcc supports -Wcomment... yes > Checking whether gcc supports -Wimplicit... yes > Checking whether gcc supports -Wsequence-point... yes > Checking whether gcc supports -Wreturn-type... yes > Checking whether gcc supports -Wfloat-equal... yes > Checking whether gcc supports -Wno-system-headers... yes > Checking whether gcc supports -Wredundant-decls... yes > Checking whether gcc supports -Wmissing-noreturn... yes > Checking whether gcc supports -pedantic... yes > Checking whether gcc supports -Wlong-long... yes > Checking whether gcc supports -Wundef... yes > Checking whether gcc supports -Winline... yes > Checking whether gcc supports -Wpointer-arith... yes > Checking whether gcc supports -Wno-unused-parameter... yes > Checking whether gcc supports -Wno-cast-align... yes > Checking for C type union semun... no > checking whether dirent structure has member d_namlen... no > checking whether dirent structure has member d_fileno... yes > checking whether dirent structure has member d_type... yes > Checking for C header file stdint.h... yes > Checking for C function lockf()... yes > Checking for C function semop()... yes > Checking for C function shmget()... yes > Checking for C function flock()... yes > Checking for FSP locking type... (cached) semop and shmget > Checking for user supplied lockprefix... (cached) no > Checking for user supplied prefix... (cached) no > checking whether to build shared library... (cached) yes > Checking whether to enable maintainer mode... (cached) no > scons: done reading SConscript files. > scons: Cleaning targets ... > scons: done cleaning targets. > Removing autogenerated file .sconsign.dblite > Removing autogenerated directory .sconf_temp > rm -rf .scon* config.log > make[1]: Leaving directory '/<>' >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building fsplib using existing ./fsplib_0.14.orig.tar.gz > dpkg-source: error: cannot represent change to > site_scons/__pycache__/buildshared.cpython-37.pyc: binary file contents > changed > dpkg-source: error: add site_scons/__pycache__/buildshared.cpython-37.pyc in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: cannot represent change to > site_scons/__pycache__/compilertest.cpython-37.pyc: binary file contents > changed > dpkg-source: error: add site_scons/__pycache__/compilertest.cpython-37.pyc in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: cannot represent change to > site_scons/__pycache__/dirent.cpython-37.pyc: binary file contents changed > dpkg-source: error: add site_scons/__pycache__/dirent.cpython-37.pyc in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: cannot represent c
Bug#936721: marked as done (idjc: Python2 removal in sid/bullseye)
Your message dated Mon, 30 Mar 2020 16:29:18 + with message-id and subject line Bug#955171: Removed package(s) from unstable has caused the Debian Bug report #936721, regarding idjc: 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.) -- 936721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936721 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:idjc Version: 0.8.17-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:idjc If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.8.17-1+rm Dear submitter, as the package idjc 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/955171 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#936634: marked as done (go2: Python2 removal in sid/bullseye)
Your message dated Mon, 30 Mar 2020 16:30:05 + with message-id and subject line Bug#955178: Removed package(s) from unstable has caused the Debian Bug report #936634, regarding go2: 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.) -- 936634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:go2 Version: 1.20121210-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:go2 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.20121210-1+rm Dear submitter, as the package go2 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/955178 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#928324: marked as done (crash: UnicodeEncodeError)
Your message dated Mon, 30 Mar 2020 16:30:05 + with message-id and subject line Bug#955178: Removed package(s) from unstable has caused the Debian Bug report #928324, regarding crash: UnicodeEncodeError 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.) -- 928324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928324 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: go2 Version: 1.20121210-1 Severity: grave Justification: renders package unusable Dear Maintainer, running "go2 folder" crashes here after yielding two useful results. --- Traceback (most recent call last): File "/usr/lib/go2/go2.py", line 554, in __call__ return self.func(*args) File "/usr/lib/go2/go2.py", line 925, in end_checker self.path_buffer.flush_alternate() File "/usr/lib/go2/go2.py", line 662, in flush_alternate add_paths_of_group(self.groups[level]) File "/usr/lib/go2/go2.py", line 652, in add_paths_of_group self.sink.add_entry(path) File "/usr/lib/go2/go2.py", line 719, in add_entry self.write_last() File "/usr/lib/go2/go2.py", line 731, in write_last self.out_write(line) File "/usr/lib/go2/go2.py", line 737, in out_write self.fd.write(text) UnicodeEncodeError: 'ascii' codec can't encode character u'\xfc' in position 37: ordinal not in range(128) Traceback (most recent call last): File "/usr/lib/go2/go2.py", line 1110, in sys.exit(config.engine().run()) File "/usr/lib/go2/go2.py", line 839, in run self.reactor.run() File "/usr/lib/go2/go2.py", line 602, in run raise self.exception UnicodeEncodeError: 'ascii' codec can't encode character u'\xfc' in position 37: ordinal not in range(128) -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages go2 depends on: ii python 2.7.16-1 ii tree1.8.0-1 go2 recommends no packages. go2 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 1.20121210-1+rm Dear submitter, as the package go2 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/955178 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#936158: marked as done (asterisk-testsuite: Python2 removal in sid/bullseye)
Your message dated Mon, 30 Mar 2020 16:30:28 + with message-id and subject line Bug#955253: Removed package(s) from unstable has caused the Debian Bug report #936158, regarding asterisk-testsuite: 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.) -- 936158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:asterisk-testsuite Version: 0.0.0+svn.5781-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:asterisk-testsuite If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.0.0+svn.5781-2+rm Dear submitter, as the package asterisk-testsuite 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/955253 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#935204: marked as done (go2: uninstalling go2 breaks "bash cd")
Your message dated Mon, 30 Mar 2020 16:30:05 + with message-id and subject line Bug#955178: Removed package(s) from unstable has caused the Debian Bug report #935204, regarding go2: uninstalling go2 breaks "bash cd" 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.) -- 935204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: go2 Severity: critical Justification: breaks unrelated software Dear Maintainer, uninstalling "go2" via "apt remove" forgets to correctly removing a "cd alias" in ~/.bashrc. Therefore, using "cd" in a terminal points to a nonexisting alias after uninstalling go2. Uncommenting the "cd alias" to go2 in ~/.bashrc by hand fixes the issue. -- System Information: Debian Release: 10.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Version: 1.20121210-1+rm Dear submitter, as the package go2 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/955178 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#937191: marked as done (openalpr: Python2 removal in sid/bullseye)
Your message dated Mon, 30 Mar 2020 16:28:56 + with message-id and subject line Bug#955163: Removed package(s) from unstable has caused the Debian Bug report #937191, regarding openalpr: 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.) -- 937191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:openalpr Version: 2.3.0-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:openalpr If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 2.3.0-1.1+rm Dear submitter, as the package openalpr 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/955163 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#908802: marked as done (asttest missing from asttest)
Your message dated Mon, 30 Mar 2020 16:30:28 + with message-id and subject line Bug#955253: Removed package(s) from unstable has caused the Debian Bug report #908802, regarding asttest missing from asttest 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.) -- 908802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: asttest Version: 0.0.0+svn.5781-2 Severity: grave The asttest package lacks the asttest binary mentioned in the package description. In fact the asttest package is empty beyond a changelog and a copyright file. It doesn't even have dependencies. It's useless as is. Helmut --- End Message --- --- Begin Message --- Version: 0.0.0+svn.5781-2+rm Dear submitter, as the package asterisk-testsuite 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/955253 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#937946: marked as done (python-nids: Python2 removal in sid/bullseye)
Your message dated Mon, 30 Mar 2020 16:29:39 + with message-id and subject line Bug#955177: Removed package(s) from unstable has caused the Debian Bug report #937946, regarding python-nids: 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.) -- 937946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937946 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-nids Version: 0.6.1-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-nids If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.6.1-1.1+rm Dear submitter, as the package python-nids 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/955177 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#922588: marked as done (FTBFS against opencv 4.0.1 (exp))
Your message dated Mon, 30 Mar 2020 16:28:56 + with message-id and subject line Bug#955163: Removed package(s) from unstable has caused the Debian Bug report #922588, regarding FTBFS against opencv 4.0.1 (exp) 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.) -- 922588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openalpr Version: 2.3.0-1.1 Severity: important build failed due to API change. openalpr_2.3.0-1.1_ppc64el-2019-02-15T11:21:44Z.build.zst Description: Binary data --- End Message --- --- Begin Message --- Version: 2.3.0-1.1+rm Dear submitter, as the package openalpr 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/955163 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#885308: marked as done (idjc: Depends on unmaintained pygtk)
Your message dated Mon, 30 Mar 2020 16:29:18 + with message-id and subject line Bug#955171: Removed package(s) from unstable has caused the Debian Bug report #885308, regarding idjc: Depends on unmaintained pygtk to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 885308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: idjc Version: 0.8.16-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject Introspection bindings. For more information on GObject Introspection see [1] and [2]. Please try to do this before the Buster release as we're going to try to remove pygtk this cycle. If you have any question don't hesitate to ask. [1] https://wiki.gnome.org/Projects/GObjectIntrospection [2] https://wiki.gnome.org/Projects/PyGObject On behalf of the Debian GNOME team, Jeremy Bicha --- End Message --- --- Begin Message --- Version: 0.8.17-1+rm Dear submitter, as the package idjc 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/955171 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#937916: marked as done (python-mhash: Python2 removal in sid/bullseye)
Your message dated Mon, 30 Mar 2020 16:22:05 + with message-id and subject line Bug#955162: Removed package(s) from unstable has caused the Debian Bug report #937916, regarding python-mhash: 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.) -- 937916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937916 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-mhash Version: 1.4-1.2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-mhash 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.4-1.2+rm Dear submitter, as the package python-mhash 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/955162 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#942623: marked as done (src:frevial: Maintainer email address not working)
Your message dated Mon, 30 Mar 2020 16:19:39 + with message-id and subject line Bug#955159: Removed package(s) from unstable has caused the Debian Bug report #942623, regarding src:frevial: 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.) -- 942623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942623 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:frevial 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 --- Version: 1.3-2.1+rm Dear submitter, as the package freevial 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/955159 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#936559: marked as done (freevial: Python2 removal in sid/bullseye)
Your message dated Mon, 30 Mar 2020 16:19:39 + with message-id and subject line Bug#955159: Removed package(s) from unstable has caused the Debian Bug report #936559, regarding freevial: 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.) -- 936559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936559 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:freevial Version: 1.3-2.1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:freevial 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.3-2.1+rm Dear submitter, as the package freevial 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/955159 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#912487: marked as done (pyntor: Please migrate to python3-pygame)
Your message dated Mon, 30 Mar 2020 16:17:35 + with message-id and subject line Bug#955148: Removed package(s) from unstable has caused the Debian Bug report #912487, regarding pyntor: Please migrate to python3-pygame 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.) -- 912487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912487 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pyntor Severity: wishlist User: python-modules-t...@lists.alioth.debian.org Usertags: python3-migration Dear maintainer, thanks for maintaining a pygame-based game in Debian! As you might have heard, Python 2 will be end of life in the not so far future. Thus, I would like to start to get the reverse dependencies of the Python 2 version of pygame down, so this can be done with some time and not in a hurried effort that probably makes us loose games from Debian. If you already know that your game will work with Python 3, please build against and depend on python3-pygame, which has long been available in sid and will migrate to buster shortly. If you do not yet know whether this will work, your chances that it will just work are still quite good, so please just give it a shot. If you find your package does not work with Python 3 yet, you can⦠a) â¦check what to do with upstream b) â¦try to patch it (and forward your patch upstream) c) â¦tag this bug report help - the next pygame-fluent kangaroo is reserved for you! Feel free to ask any questions if you are unsure what to do. Cheers, Nik --- End Message --- --- Begin Message --- Version: 0.6-4.1+rm Dear submitter, as the package pyntor 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/955148 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#937492: marked as done (pyntor: Python2 removal in sid/bullseye)
Your message dated Mon, 30 Mar 2020 16:17:35 + with message-id and subject line Bug#955148: Removed package(s) from unstable has caused the Debian Bug report #912487, regarding pyntor: 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.) -- 912487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912487 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pyntor Version: 0.6-4.1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. 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:pyntor If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.6-4.1+rm Dear submitter, as the package pyntor 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/955148 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#936267: marked as done (calabash: Python2 removal in sid/bullseye)
Your message dated Mon, 30 Mar 2020 16:20:14 + with message-id and subject line Bug#955160: Removed package(s) from unstable has caused the Debian Bug report #936267, regarding calabash: 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.) -- 936267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936267 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:calabash Version: 0.0.3-3 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:calabash If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.0.3-3+rm Dear submitter, as the package calabash 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/955160 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#954154: marked as done (src:salt: Requires a package outside of Main)
Your message dated Mon, 30 Mar 2020 16:19:13 +
with message-id
and subject line Bug#954154: fixed in salt 3000+dfsg1-4
has caused the Debian Bug report #954154,
regarding src:salt: Requires a package outside of Main
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.)
--
954154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: salt
Source-Version: 3000+dfsg1-4
Done: Benjamin Drung
We believe that the bug you reported is fixed in the latest version of
salt, 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.
Benjamin Drung (supplier of updated salt
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: Mon, 30 Mar 2020 11:29:56 +0200
Source: salt
Architecture: source
Version: 3000+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Salt Team
Changed-By: Benjamin Drung
Closes: 954154
Changes:
salt (3000+dfsg1-4) unstable; urgency=medium
.
* Let sphinx display the full traceback when an unhandled exception occurs
to help debugging #955057.
* autopkgtest: Skip tests that need Internet access (Clo
Bug#954541: cmark: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2
On Sun, 22 Mar 2020 08:53:46 +0100, Lucas Nussbaum said: > During a rebuild of all packages in sid, your package failed to build > on amd64. [...] It looks like the test failure would be fixed by this commit from upstream: https://github.com/commonmark/cmark/commit/68c3a91166347a32a57fb81223750a63cfd92105 (see also https://github.com/commonmark/cmark/issues/313)
Bug#943033: marked as done (dictclient: Python2 removal in sid/bullseye)
Your message dated Mon, 30 Mar 2020 16:12:12 + with message-id and subject line Bug#954456: Removed package(s) from unstable has caused the Debian Bug report #943033, regarding dictclient: 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.) -- 943033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dictclient Version: 1.0.3.2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.0.3.2+rm Dear submitter, as the package dictclient 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/954456 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#954456: marked as done (RM: dictclient -- RoQA; python2-only; no real development in 3 years; no rdeps; very low popcon)
Your message dated Mon, 30 Mar 2020 16:12:04 + with message-id and subject line Bug#954456: Removed package(s) from unstable has caused the Debian Bug report #954456, regarding RM: dictclient -- RoQA; python2-only; no real development in 3 years; no rdeps; very low popcon 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.) -- 954456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954456 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dictclient Severity: serious Tags: sid, bullseye Hello, this bug is to mark my intention to remove dictclient from debian: * python2-only * no real development in ~3 years * debian specific (why?) * no rdeps * very low popcon 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 --- End Message --- --- Begin Message --- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: dictclient |1.0.3.2 | source python-dictclient |1.0.3.2 | all --- Reason --- RoQA; python2-only; no real development in 3 years; no rdeps; very low popcon -- 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 954...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/954456 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processed: tagging 936366
Processing commands for cont...@bugs.debian.org: > tags 936366 + pending Bug #936366 [src:darkradiant] darkradiant: Python2 removal in sid/bullseye Added tag(s) pending. > thanks 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
Processed: Bug#954154 marked as pending in salt
Processing control commands: > tag -1 pending Bug #954154 [src:salt] src:salt: Requires a package outside of Main Added tag(s) pending. -- 954154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954154: marked as pending in salt
Control: tag -1 pending Hello, Bug #954154 in salt 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/salt-team/salt/-/commit/99a56cbd6582f99b8677e7f52b8bc5163e7f3a01 autopkgtest: Skip tests that need Internet access Closes: #954154 Signed-off-by: Benjamin Drung (this message was generated automatically) -- Greetings https://bugs.debian.org/954154
Bug#953970: Taking over DPMT (Was: python-boto: autopkgtest failure with Python 3.8 as default)
On Mon, Mar 30, 2020 at 11:44:23AM +0200, Andreas Tille wrote: > I wonder whether we should take over python-boto into DPMT maintenance > which would enable commits to Git way more easily. If it's going to move, might I suggest maintaining it within the cloud-team instead? Among other things, the cloud team has an interest in providing feature updates to cloud-oriented packages, such as python-boto, in stable point releases. Having the team maintain these packages, as we do with other packages such as cloud-init, would help us with this goal. noah
Bug#938212: marked as done (python-termcolor: Python2 removal in sid/bullseye)
Your message dated Mon, 30 Mar 2020 15:04:42 + with message-id and subject line Bug#938212: fixed in python-termcolor 1.1.0-3 has caused the Debian Bug report #938212, regarding python-termcolor: 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.) -- 938212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-termcolor Version: 1.1.0-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-termcolor 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-termcolor Source-Version: 1.1.0-3 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of python-termcolor, 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-termcolor package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 30 Mar 2020 10:11:00 -0400 Source: python-termcolor Architecture: source Version: 1.1.0-3 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Sandro Tosi Closes: 938212 Changes: python-termcolor (1.1.0-3) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Use team+openst...@tracker.debian.org as maintainer * Use debhelper-compat instead of debian/compat. . [ Sandro Tosi ] * Drop python2 support; Closes: #938212 Checksums-Sha1: 827dfc026d1d63013ab35059d32376c2bf87e899 2049 python-termcolor_1.1.0-3.dsc 1a179fd8b21397fb937c4800e17ae5fe891dbd28 2156 python-termcolor_1.1.0-3.debian.tar.xz 08a839fa8f703c5223a1e2108fef1cb2608e5d03 6509 python-termcolor_1.1.0-3_source.buildinfo Checksums-Sha256: dfd8c6f8dcf1136f1fe33cdcc9bdde9c5d2242fd14823f499d920463e9523659 2049 python-termcolor_1.1.0-3.dsc 296e63ddaeb038f051dda2470246a7f1b99d3883efd
Bug#930527: linux-image-4.19.0-5-amd64: when logging out, not the whole screen is erased, leaving private information
Control: severity -1 important Control: fixed -1 5.4.19-1 Control: retitle -1 linux-image-4.19.0-5-amd64: nouveau driver sometimes crashes Hi, Thanks for the clarification. On Mon, Mar 30, 2020 at 01:05:20PM +0200, Vincent Lefevre wrote: > On 2020-03-30 09:06:15 +0200, Ivo De Decker wrote: > > On Sun, Mar 29, 2020 at 09:43:42PM +0200, Vincent Lefevre wrote: > > > I don't think so, except the use of the nouveau driver, of course. > > > But there were no issues for years. I think that problems started > > > to occur after some kernel upgrade. Now, I haven't had any problem > > > since December, I think. > > > > Do you think the problem is gone with the kernel you are running now? > > I don't know. I don't use this machine often, except remotely > (via ssh). But problems with the nouveau driver were common > (and a crash could occur in the nouveau driver even when using > the machine remotely only), and I haven't seen any issue recently, > even the last few times I logged in physically. It seems the main issue you were seeing was (is?) that the nouveau driver wasn't always very stable. I suspect this wasn't limited to logout only. > > What version is that? > > linux-image-5.4.0-4-amd64 5.4.19-1 > > ypig:~> uname -a > Linux ypig 5.4.0-4-amd64 #1 SMP Debian 5.4.19-1 (2020-02-13) x86_64 GNU/Linux Ok, let's assume the issue is no longer present there. > > > > Also, I don't think this bug is really 'grave'. Even if private > > > > information remains on the screen, the user can see that, and > > > > take action to avoid it. > > > > > > Not if one logs out remotely. > > > > What do you mean by that? > > I sometimes log in physically, but go away without logging out first > (there are sometimes a good reason, e.g. if some computation program > hasn't finished yet and I had not started it in "screen"). I can > later log in via ssh and kill the X session. Oh. I assumed you were talking about a text console, but it seems you're talking about a graphical login. In any case, I don't think this qualifies as a grave bug, so I'm downgrading it. Cheers, Ivo
Bug#954511: Can someone habe a look at bioperl-run in connection with kalign (was: bioperl-run is marked for autoremoval from testing]
I have seen per exit codes of 256 for other bioperl-run wrappers in the past where the application API changed (constant game of playing catchup unfortunately). That seems to be the case here based on the error. Is kalign is now at v3? chris On 3/30/20, 2:57 AM, "Andreas Tille" wrote: Control: tags -1 help Hi, currently bioperl-run fails. I think the issue is: > # Failed test 'Code tested only on kalign versions >= 2' > # at t/Kalign.t line 23. > # got: '' > # expected: '1' > [2020-03-22 03:18:02] : ERROR : Input alignment format could not be detected. (rwalign.c line 314) > [2020-03-22 03:18:02] : ERROR : Function "detect_alignment_format(b, &type)" failed. (rwalign.c line 187) > [2020-03-22 03:18:02] : ERROR : Function "tmp_msa = read_input(param->infile[i],tmp_msa)" failed. (run_kalign.c line 383) > [2020-03-22 03:18:02] : ERROR : Function "run_kalign(param)" failed. (run_kalign.c line 353) > > - WARNING - > MSG: Kalign call crashed: 256 [command /usr/bin/kalign -in t/data/cysprot.fa -out /tmp/ilV8fEWBHj/nJrv_GQaDU] but please double check. Could someone have a look please? Kind regards Andreas. - Forwarded message from Debian testing autoremoval watch - Date: Mon, 30 Mar 2020 04:39:17 + From: Debian testing autoremoval watch To: bioperl-...@packages.debian.org Subject: bioperl-run is marked for autoremoval from testing bioperl-run 1.7.3-3 is marked for autoremoval from testing on 2020-05-05 It is affected by these RC bugs: 954511: bioperl-run: FTBFS: dh_auto_test: error: perl Build test --verbose 1 returned exit code 255 ___ Debian-med-packaging mailing list debian-med-packag...@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging - End forwarded message - -- http://fam-tille.de
Processed: Re: linux-image-4.19.0-5-amd64: when logging out, not the whole screen is erased, leaving private information
Processing control commands: > severity -1 important Bug #930527 [src:linux] linux-image-4.19.0-5-amd64: when logging out, not the whole screen is erased, leaving private information Severity set to 'important' from 'grave' > fixed -1 5.4.19-1 Bug #930527 [src:linux] linux-image-4.19.0-5-amd64: when logging out, not the whole screen is erased, leaving private information Marked as fixed in versions linux/5.4.19-1. > retitle -1 linux-image-4.19.0-5-amd64: nouveau driver sometimes crashes Bug #930527 [src:linux] linux-image-4.19.0-5-amd64: when logging out, not the whole screen is erased, leaving private information Changed Bug title to 'linux-image-4.19.0-5-amd64: nouveau driver sometimes crashes' from 'linux-image-4.19.0-5-amd64: when logging out, not the whole screen is erased, leaving private information'. -- 930527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955356: marked as done (shim-signed-* - Uninstallable)
Your message dated Mon, 30 Mar 2020 14:48:57 + with message-id and subject line Bug#955356: fixed in shim 15+1533136590.3beb971-9 has caused the Debian Bug report #955356, regarding shim-signed-* - Uninstallable 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.) -- 955356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: shim-helpers-amd64-signed Version: 1.33+15+1533136590.3beb971-7 Severity: grave Binary packages in shim-signed and shim-unsigned have = dependencies, leading to them being uninstallable: | The following information may help to resolve the situation: | | The following packages have unmet dependencies: | shim-helpers-amd64-signed : Depends: shim-unsigned (= 15+1533136590.3beb971-7) but 15+1533136590.3beb971-8 is to be installed | E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. Please fix this by removing those strict dependencies or move into a single source package. Bastian -- Spock: The odds of surviving another attack are 13562190123 to 1, Captain. --- End Message --- --- Begin Message --- Source: shim Source-Version: 15+1533136590.3beb971-9 Done: Steve McIntyre <93...@debian.org> We believe that the bug you reported is fixed in the latest version of shim, 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 955...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve McIntyre <93...@debian.org> (supplier of updated shim package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 30 Mar 2020 15:19:08 +0100 Source: shim Architecture: source Version: 15+1533136590.3beb971-9 Distribution: unstable Urgency: medium Maintainer: Debian EFI team Changed-By: Steve McIntyre <93...@debian.org> Closes: 955356 Changes: shim (15+1533136590.3beb971-9) unstable; urgency=medium . [ Steve McIntyre ] . * In the -helpers-ARCH-signed packages, change the version dependency on shim-unsigned to be >= and not =. This will allow for installation to still work in the window while we wait for the template package to do its second trip through the archive. Closes: #955356 Checksums-Sha1: d0122f66d95be0a46c525ff8e26ea93a4eb0f435 2391 shim_15+1533136590.3beb971-9.dsc 2ef42d526d2706f44f7a6139d616a2cadabe42e5 15584 shim_15+1533136590.3beb971-9.debian.tar.xz a2d7075a230442a5e89b22a34888db0f5636a840 6112 shim_15+1533136590.3beb971-9_source.buildinfo Checksums-Sha256: 64547f4c7d9abae0d0fe6e40ee5ecef23bca3f86df6e90adb86dcfcade5afe7a 2391 shim_15+1533136590.3beb971-9.dsc af22a4ee98adc6467baa1ed4c204db8b24fc35912169d2da520e24fa8601c9eb 15584 shim_15+1533136590.3beb971-9.debian.tar.xz 48f9c32fa0bd5da13b8616c823855902d1b8ce5f14cbc2d7fc720a543e8de584 6112 shim_15+1533136590.3beb971-9_source.buildinfo Files: 1170c05f5a2f6aea1c516e34a1471157 2391 admin optional shim_15+1533136590.3beb971-9.dsc 0ab02f691ff0c9052b91c0fc93be2965 15584 admin optional shim_15+1533136590.3beb971-9.debian.tar.xz 9831670597d9b2f9503bb289af64c0b0 6112 admin optional shim_15+1533136590.3beb971-9_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEEzrtSMB1hfpEDkP4WWHl5VzRCaE4FAl6CARARHDkzc2FtQGRl Ymlhbi5vcmcACgkQWHl5VzRCaE5/lxAAnG+wyZmwLohmPOXKGrEQB1bthjUUA81v gcjt1uueAUNRMWTEsGSbLRVCgdEMoYc2+EhrgrhCfKc79Dlo1lTSd3iMYy4B6uGk VRmj/3J5rrzS6geZIurEi6IE+YcJQf3BtItoby1SSKWxPNYmY9smOTW4LRT5x9N3 lZVGioNuM2jEotpma/6n998FoBl3NqY55v1IBF2VAxWhKs4c9sISPVv4+ota3keG XVg+1cL9wsS7XS3F7GJ8CDt2GxOYUslBwwLRLk7qs6vdpTeHT1tJtjmW7Jrhuk2e RBYju8cfCw+U4bxAH8EeqRW+hvNtBpaMtlr6pUvwD9ARIbitJoZOAk7ywXOqX1XR COHEwBBSzkQeG3alNwC0iuakFXrAcNPMCrCtGZ0zOnh+ES8IbiUJviqFEnD7RpyW wQv5LAIkW+N3TgQR4AZm52EsKDk8VhIJFT0rC0oJA/m4yccL9nMLUMTaN2e9c66v VyXrIU0LXAa3g22UM504ZSQebboOJjsu1Byyd0opeuEwhrQ1cXPRQO4e4YAv9rgG zsDbKi+gD8SSbHj+yjxze9uHAgEDXjCWy7pQINkFqy5JlA69Mlz60dHlx88X9mCM Ds/qyty/YpEoiFZnWPKUeXD2gU159mPi/jEWPynVONPTcsyFpd1dUlCT7lot2F48 imzsPAgqNGU= =PofW -END PGP SIGNATURE End Message ---
Bug#955360: phpmyadmin: depends on non-existing php-recode package
Source: phpmyadmin
Version: 4.9.5+dfsg1-1
Severity: serious
Tags: patch
Hello, looks like php-recode is now removed in new php-defaults_75
php-defaults (75) unstable; urgency=medium
* Remove the php-recode, as there's no php7.4-recode anymore
(Closes: #955027)
so, please drop it from depends and suggests
trivial diff:
--- phpmyadmin-4.9.5+dfsg1/debian/control 2020-03-25 22:07:16.0
+0100
+++ phpmyadmin-4.9.5+dfsg1/debian/control 2020-03-30 16:27:06.0
+0200
@@ -20,7 +20,6 @@
php-bz2,
php-zip,
php-gd,
-php-recode,
php-phpmyadmin-motranslator (>= 4.0),
php-phpmyadmin-sql-parser (>= 4.5.0),
php-phpmyadmin-shapefile (>= 2.0),
@@ -61,7 +60,6 @@
php-tcpdf
Suggests: default-mysql-server | virtual-mysql-server,
www-browser,
-php-recode,
${phpcomposer:Debian-suggest}
Description: MySQL web administration tool
This package allows administering of MySQL or MariaDB with a web interface.
(note: I just did a quick test build, no runtime testing at all)
http://debomatic-amd64.debian.net/distribution#unstable/phpmyadmin/4.9.5+dfsg1-1.1/autopkgtest
G.
Bug#938212: marked as pending in python-termcolor
Control: tag -1 pending Hello, Bug #938212 in python-termcolor reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/python-termcolor/-/commit/84c2ce09923ab8c589342142002ac91e7a6fbe9e Drop python2 support; Closes: #938212 (this message was generated automatically) -- Greetings https://bugs.debian.org/938212
Processed: Bug#938212 marked as pending in python-termcolor
Processing control commands: > tag -1 pending Bug #938212 [src:python-termcolor] python-termcolor: Python2 removal in sid/bullseye Added tag(s) pending. -- 938212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954635: golang-github-thecreeper-go-notify: FTBFS: Errors while processing: libdbus2.0-cil libglib2.0-cil libgtk2.0-cil libdbus-glib2.0-cil libnotify0.4-cil libnotify-cil-dev sbuild-build-depend
Your analysis is correct, Emilio. It’s related to that upstream bug, in that `gacutil` is used by packages to register their libraries to the system library cache, but `gacutil` does not work until `/etc/mono/config` exists and contains a mapping for System.Native. There’s a pre-depends from mono-gap on mono-runtime-common to make it fine, but as per the log in the bug, mono-gac isn’t being configured until after the packages actually consuming mono-gac, so it doesn’t help much for clean installs. I wonder why I never hit this before. I also wonder why the gac install isn’t done with triggers. On Thu, 26 Mar 2020 20:37:11 +0100 Emilio Pozuelo Monfort wrote: > Control: reassign -1 src:mono 6.8.0.105+dfsg-2 > Control: retitle -1 CLI binding packages fail to install: Unhandled > Exception: System.TypeInitializationException: The type initializer for 'Sys' > threw an exception > Control: affects -1 src:golang-github-thecreeper-go-notify libglib2.0-cil > libgdcm-cil > Control: severity -1 grave > > On Sun, 22 Mar 2020 08:45:16 +0100 Lucas Nussbaum wrote: > > Source: golang-github-thecreeper-go-notify > > Version: 0.0~git20160203.0.b5cd147-4 > > Severity: serious > > Justification: FTBFS on amd64 > > Tags: bullseye sid ftbfs > > Usertags: ftbfs-20200321 ftbfs-bullseye > > > > Hi, > > > > During a rebuild of all packages in sid, your package failed to build > > on amd64. > > > > Relevant part (hopefully): > [snip] > > Setting up librest-0.7-0:amd64 (0.8.1-1+b1) ... > > Setting up libgtk-3-0:amd64 (3.24.14-1) ... > > Setting up libgtk2.0-0:amd64 (2.24.32-4) ... > > Setting up libgtk-3-bin (3.24.14-1) ... > > Setting up notification-daemon (3.20.0-4) ... > > Setting up libmono-system-numerics4.0-cil (6.8.0.105+dfsg-2) ... > > Setting up libmono-system-core4.0-cil (6.8.0.105+dfsg-2) ... > > Setting up dh-autoreconf (19) ... > > Setting up libmono-system-security4.0-cil (6.8.0.105+dfsg-2) ... > > Setting up mono-runtime-sgen (6.8.0.105+dfsg-2) ... > > Setting up mono-runtime (6.8.0.105+dfsg-2) ... > > update-alternatives: using /usr/bin/mono to provide /usr/bin/cli (cli) in > > auto mode > > Setting up libmono-system-configuration4.0-cil (6.8.0.105+dfsg-2) ... > > Setting up debhelper (12.9) ... > > Setting up libmono-corlib4.5-cil (6.8.0.105+dfsg-2) ... > > Setting up libmono-cairo4.0-cil (6.8.0.105+dfsg-2) ... > > Setting up libmono-system-xml4.0-cil (6.8.0.105+dfsg-2) ... > > Setting up dh-golang (1.48) ... > > Setting up libmono-system4.0-cil (6.8.0.105+dfsg-2) ... > > Setting up libmono-posix4.0-cil (6.8.0.105+dfsg-2) ... > > Setting up libmono-system-drawing4.0-cil (6.8.0.105+dfsg-2) ... > > Setting up libdbus2.0-cil (0.8.1-2) ... > > * Installing 1 assembly from libdbus2.0-cil into Mono > > > > Unhandled Exception: > > System.TypeInitializationException: The type initializer for 'Sys' threw an > > exception. ---> System.DllNotFoundException: System.Native > > assembly: type: member:(null) > > at (wrapper managed-to-native) Interop+Sys.LChflagsCanSetHiddenFlag() > > at Interop+Sys..cctor () [0x0] in > > <12b418a7818c4ca0893feeaaf67f1e7f>:0 > >--- End of inner exception stack trace --- > > at System.IO.FileSystem.FileExists (System.ReadOnlySpan`1[T] fullPath, > > System.Int32 fileType, Interop+ErrorInfo& errorInfo) [0xf] in > > <12b418a7818c4ca0893feeaaf67f1e7f>:0 > > at System.IO.FileSystem.FileExists (System.ReadOnlySpan`1[T] fullPath) > > [0x6] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 > > at System.IO.File.Exists (System.String path) [0x00058] in > > <12b418a7818c4ca0893feeaaf67f1e7f>:0 > > at Mono.Tools.Driver.LoadConfig (System.Boolean quiet) [0x00031] in > > <3a4d36ecef0a47439a72108fe400486f>:0 > > at Mono.Tools.Driver.Main (System.String[] args) [0x00347] in > > <3a4d36ecef0a47439a72108fe400486f>:0 > > [ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: The > > type initializer for 'Sys' threw an exception. ---> > > System.DllNotFoundException: System.Native assembly: > > type: member:(null) > > at (wrapper managed-to-native) Interop+Sys.LChflagsCanSetHiddenFlag() > > at Interop+Sys..cctor () [0x0] in > > <12b418a7818c4ca0893feeaaf67f1e7f>:0 > >--- End of inner exception stack trace --- > > at System.IO.FileSystem.FileExists (System.ReadOnlySpan`1[T] fullPath, > > System.Int32 fileType, Interop+ErrorInfo& errorInfo) [0xf] in > > <12b418a7818c4ca0893feeaaf67f1e7f>:0 > > at System.IO.FileSystem.FileExists (System.ReadOnlySpan`1[T] fullPath) > > [0x6] in <12b418a7818c4ca0893feeaaf67f1e7f>:0
Bug#955359: swi-prolog: FTBFS on mips: error due to ATOMIC
Package: swi-prolog Version: 8.1.26+dfsg-2 Severity: serious Dear Maintainer, current development version of swi-prolog fails to build from source [log]: [ 84%] Building C object packages/xpce/CMakeFiles/plugin_pl2xpce.dir/swipl/pcecall.c.o cd /<>/build/packages/xpce && /usr/bin/cc -Dplugin_pl2xpce_EXPORTS -I/<>/build/packages/xpce -I/<>/packages/xpce/src -I/usr/include/freetype2 -I/<>/src/os -I/<>/src -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Wall -DHAVE_CONFIG_H -DSWI -D__SWI_PROLOG__ -o CMakeFiles/plugin_pl2xpce.dir/swipl/pcecall.c.o -c /<>/packages/xpce/swipl/pcecall.c [ 84%] Linking C shared module pl2xpce.so cd /<>/build/packages/xpce && /usr/bin/cmake -E cmake_link_script CMakeFiles/plugin_pl2xpce.dir/link.txt --verbose=1 /usr/bin/cc -fPIC -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -shared -o pl2xpce.so CMakeFiles/plugin_pl2xpce.dir/src/adt/area.c.o CMakeFiles/plugin_pl2xpce.dir/src/adt/atable.c.o CMakeFiles/plugin_pl2xpce.dir/src/adt/attribute.c.o CMakeFiles/plugin_pl2xpce.dir/src/adt/bool.c.o CMakeFiles/plugin_pl2xpce.dir/src/adt/chain.c.o CMakeFiles/plugin_pl2xpce.dir/src/adt/chaintable.c.o CMakeFiles/plugin_pl2xpce.dir/src/adt/constant.c.o CMakeFiles/plugin_pl2xpce.dir/src/adt/date.c.o CMakeFiles/plugin_pl2xpce.dir/src/adt/dict.c.o CMakeFiles/plugin_pl2xpce.dir/src/adt/dictitem.c.o CMakeFiles/plugin_pl2xpce.dir/src/adt/hashtable.c.o CMakeFiles/plugin_pl2xpce.dir/src/adt/number.c.o CMakeFiles/plugin_pl2xpce.dir/src/adt/point.c.o CMakeFiles/plugin_pl2xpce.dir/src/adt/real.c.o CMakeFiles/plugin_pl2xpce.dir/src/adt/region.c.o CMakeFiles/plugin_pl2xpce.dir/src/adt/sheet.c.o CMakeFiles/plugin_pl2xpce.dir/src/adt/size.c.o CMakeFiles/plugin_pl2xpce.dir/src/adt/tuple.c.o CMakeFiles/plugin_pl2xpce.dir/src/adt/vector.c.o CMakeFiles/plugin_pl2xpce.dir/src/ari/equation.c.o CMakeFiles/plugin_pl2xpce.dir/src/ari/expression.c.o CMakeFiles/plugin_pl2xpce.dir/src/evt/clickgesture.c.o CMakeFiles/plugin_pl2xpce.dir/src/evt/conngesture.c.o CMakeFiles/plugin_pl2xpce.dir/src/evt/event.c.o CMakeFiles/plugin_pl2xpce.dir/src/evt/eventnode.c.o CMakeFiles/plugin_pl2xpce.dir/src/evt/eventtree.c.o CMakeFiles/plugin_pl2xpce.dir/src/evt/gesture.c.o CMakeFiles/plugin_pl2xpce.dir/src/evt/handler.c.o CMakeFiles/plugin_pl2xpce.dir/src/evt/handlergroup.c.o CMakeFiles/plugin_pl2xpce.dir/src/evt/modifier.c.o CMakeFiles/plugin_pl2xpce.dir/src/evt/movegesture.c.o CMakeFiles/plugin_pl2xpce.dir/src/evt/mvolgesture.c.o CMakeFiles/plugin_pl2xpce.dir/src/evt/popupgesture.c.o CMakeFiles/plugin_pl2xpce.dir/src/evt/recogniser.c.o CMakeFiles/plugin_pl2xpce.dir/src/evt/resizegesture.c.o CMakeFiles/plugin_pl2xpce.dir/src/evt/rzolgesture.c.o CMakeFiles/plugin_pl2xpce.dir/src/evt/edittextgest.c.o CMakeFiles/plugin_pl2xpce.dir/src/evt/browserselgesture.c.o CMakeFiles/plugin_pl2xpce.dir/src/evt/resizetabslice.c.o CMakeFiles/plugin_pl2xpce.dir/src/gnu/getdate.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/arc.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/arrow.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/bitmap.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/box.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/circle.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/colour.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/connection.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/cursor.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/device.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/ellipse.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/figure.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/font.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/format.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/graphical.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/handle.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/image.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/joint.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/line.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/link.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/listbrowser.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/node.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/path.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/postscript.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/scrollbar.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/text.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/tree.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/visual.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/pixmap.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/elevation.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/pen.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/draw.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/colourmap.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/bezier.c.o CMakeFiles/plugin_pl2xpce.dir/src/gra/hsv.c.o CMakeFiles/plugin_pl2xpce.dir/src/itf/c.c.o CMakeFiles/plugin_pl2xpce.dir/src/itf/host.c.o CMakeFiles/plugin_pl2xpce.dir/src/itf/interface.c.o CMakeFiles/plugin_pl2xpce.dir/src/itf
Bug#954500: marked as done (pyqi: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Mon, 30 Mar 2020 13:34:35 + with message-id and subject line Bug#954500: fixed in pyqi 0.3.2+dfsg-5 has caused the Debian Bug report #954500, regarding pyqi: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 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.) -- 954500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyqi Version: 0.3.2+dfsg-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200321 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/doc' > rm -rf _build/* > make[2]: Leaving directory '/<>/doc' > make[1]: Leaving directory '/<>' >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building pyqi using existing ./pyqi_0.3.2+dfsg.orig.tar.xz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: local changes detected, the modified files are: > pyqi-0.3.2+dfsg/.pybuild/cpython3_3.8/.pydistutils.cfg > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/pyqi_0.3.2+dfsg-4.diff.b7yq6H > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2020-03-22T03:12:41Z The full build log is available from: http://qa-logs.debian.net/2020/03/21/pyqi_0.3.2+dfsg-4_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: pyqi Source-Version: 0.3.2+dfsg-5 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of pyqi, 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. Andreas Tille (supplier of updated pyqi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 30 Mar 2020 15:04:11 +0200 Source: pyqi Architecture: source Version: 0.3.2+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 954500 Changes: pyqi (0.3.2+dfsg-5) unstable; urgency=medium . [ Andreas Tille ] * Fix clean target, enable Python 3.8 in 2to3 patch Closes: #954500 * Standards-Version: 4.5.0 (routine-update) * Add salsa-ci file (routine-update) * Rules-Requires-Root: no (routine-update) * debian/copyright: use spaces rather than tabs to start continuation lines. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. . [ Nilesh Patra ] * Remove redundant cgi import line Checksums-Sha1: 5534c4061d00f632d7fa86c621cbe5dcbdc4ce73 2088 pyqi_0.3.2+dfsg-5.dsc 9d7d117616f93a92d1cc4a9bfaf9b761d92f566a 7712 pyqi_0.3.2+dfsg-5.debian.tar.xz 048f67a0c3d4011f9d30e4b9ff507fc94dbc3881 6910 pyqi_0.3.2+dfsg-5_amd64.buildinfo Checksums-Sha256: 7de3f902815e5599ea3cd49f3a5ccf60e3542781a7e4dfea744d3b54509cab60 2088 pyqi_0.3.2+dfsg-5.dsc 3c58e45a090a7947baa890e9109ef601bfd7b367d28358f38d78a9ec0403a756 7712 pyqi_0.3.2+dfsg-5.debian.tar.xz dc92bade87fbd08e14589b5db96f7d1f79b96b36abcc73171a9fd14d2bc1df4e 6910 pyqi_0.3.2+dfsg-5_amd64.buildinfo Files: d1f6c230a11ed6fed74c056600ba912a 2088 python optional pyqi_0.3.2+dfsg-5.dsc f2260b32f559f86da805637a3855dc94 7712 python optional pyqi_0.3.2+dfsg-5.debian.tar.xz 46b2d137c1e8d957e6696b83d1f635d8 6910 python optional pyqi_0.3.2+dfsg-5_amd64.buildinfo --
