Bug#942702: marked as done (bs1770gain --help misspells --suppress-progress)
Your message dated Sat, 18 Sep 2021 06:33:32 + with message-id and subject line Bug#942702: fixed in bs1770gain 0.8.3-1 has caused the Debian Bug report #942702, regarding bs1770gain --help misspells --suppress-progress 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.) -- 942702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942702 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bs1770gain Version: 0.6.5-1 Severity: minor $ bs1770gain --help [...] --suppress-progess: suppress printing processing progress The correct spelling is --suppress-progress. --- End Message --- --- Begin Message --- Source: bs1770gain Source-Version: 0.8.3-1 Done: Petter Reinholdtsen We believe that the bug you reported is fixed in the latest version of bs1770gain, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petter Reinholdtsen (supplier of updated bs1770gain package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 18 Sep 2021 08:10:56 +0200 Source: bs1770gain Architecture: source Version: 0.8.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Petter Reinholdtsen Closes: 942702 Changes: bs1770gain (0.8.3-1) unstable; urgency=medium . * New upstream version 0.8.3 - Fixes typo in --help output (Closes: #942702). * Refreshed patches and d/rules to work with new upstream source * Changed Build-depends to Build-Depends to satisfy pedantic lintian. * Updated Standards-Version from 4.5.0 to 4.6.0 * Added new autopkgtest check for XML output. Currently failing. Checksums-Sha1: 132e2eabccb5ea36b906ffaca4f2c9077a73e230 2127 bs1770gain_0.8.3-1.dsc b64c40569199aadb15d893e3d38104ab9adfc8ca 236271 bs1770gain_0.8.3.orig.tar.gz 87a6e18e6fa4e1c27fa48f0f049aaba8a51bf94b 522676 bs1770gain_0.8.3-1.debian.tar.xz b7625c18544897e0fe5269fc255fad8a47b4247b 13032 bs1770gain_0.8.3-1_source.buildinfo Checksums-Sha256: 02b1ea2e28795af45f0ca1b4f60082702268839498d35b9dfc5933784d864b22 2127 bs1770gain_0.8.3-1.dsc 6d2799e60f61dc0c7eab69b9561688c3f4c6fe83249871f98e3fb59feaf2 236271 bs1770gain_0.8.3.orig.tar.gz 1aa2c6c6c485080dfd6f14092428187818c665dc8e16fa14e6cbaa85e470b725 522676 bs1770gain_0.8.3-1.debian.tar.xz 87e1a474903b5c2de43fba4d8de9fe3c31557a4986fff0809e05ec411c01bb7c 13032 bs1770gain_0.8.3-1_source.buildinfo Files: 85799f69dccea4ba1dbe596ece21a3e9 2127 sound optional bs1770gain_0.8.3-1.dsc fa702551f7a77f020648b12690bb903c 236271 sound optional bs1770gain_0.8.3.orig.tar.gz efb4f52c1c056ced8f70367c9faa65f1 522676 sound optional bs1770gain_0.8.3-1.debian.tar.xz e826b2ef4645ff09288c8a434f2eb945 13032 sound optional bs1770gain_0.8.3-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmFFgywACgkQgSgKoIe6 +w5olhAAtqTKPhA38m7mCDUYWgx/eHXm71eRPoXrt3StKrj76XhBVfUYdJPxCZLx AECmjTh8gXesasuFFgP/vy0LFWT7RgoiGAMBS69la1YrmAdUFCKZft9SMm4hO2kx oqtGBxFJAzLTKyp5/3IuA5fUn6KqbMJfJZ9t4OE9GMO1h4Il+asJ3M+38b1NUEN2 vXc3eKGnsWDJBe/ysikYNlBV6Sf1l6SEV/DmiX6RXhw9g5z0YowPuYwdHeLFd7YS V+p/aOY0r6bzLaT5p5vz6eQlPrTx4Q4AE+oYTRmumoRWIrSP/gUy0P0uahI0hBN3 WoyHI2I0I14Yt9/7QwaP4LuaTBpSHe3bc3fsG35q8KGhSWt67xAAWNkwiDzbXDLI Hg4YkimdVPj320T+bj09Vog9PyQu6FF5weXFbQdcPbFUfzmdOLG8nsvuexzQKGJr BssGOt6Py2Lne7NxY4jC1V+oePFgyQTMYLHXXrqkphWoVgrs+lXPCrWBm1eliOUJ XqmopwKmyWno5azabVnfAC76+9+AxI0N0bxB8Tx8xJQ21VKpBy4yeYSMrLsQaboU bXD8qeTgIZpuKF/WSO+ajAbluHITYn5IRb4tOTAGFtBwwXZZlK9PfXsXhX24CXj/ Ds4326WetpJyFN4p33MvEMVBRfwF5feD+hgrcUgu7AmxR4rwbMg= =0XfT -END PGP SIGNATURE End Message ---
Bug#993202: marked as done (gnome-shell-extension-weather: does not declare compatibility with GNOME Shell 40)
Your message dated Sat, 18 Sep 2021 06:18:37 + with message-id and subject line Bug#993202: fixed in gnome-shell-extension-weather 0.0~git20210509.d714eb1-1 has caused the Debian Bug report #993202, regarding gnome-shell-extension-weather: does not declare compatibility with GNOME Shell 40 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.) -- 993202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993202 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell-extension-weather Version: 0.0~git20201103.d8be50f-1 Severity: important The metadata.json for this extension doesn't declare compatibility with GNOME 40. I don't know whether the actual code will need changes. In many versions of GNOME Shell, metadata.json didn't matter much, because validation of extensions' metadata against the installed Shell version was disabled by default; but in GNOME 40 the default has changed back to enabling the version check by default, in an effort to avoid issues caused by outdated extensions remaining enabled. When we do the GNOME 40 transition, hopefully soon, we will have to either update this extension or remove it from testing. It would be useful to get a fixed version into experimental. Thanks, smcv --- End Message --- --- Begin Message --- Source: gnome-shell-extension-weather Source-Version: 0.0~git20210509.d714eb1-1 Done: Anthony Fok We believe that the bug you reported is fixed in the latest version of gnome-shell-extension-weather, 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 993...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anthony Fok (supplier of updated gnome-shell-extension-weather 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: Fri, 17 Sep 2021 23:19:51 -0600 Source: gnome-shell-extension-weather Architecture: source Version: 0.0~git20210509.d714eb1-1 Distribution: unstable Urgency: medium Maintainer: Anthony Fok Changed-By: Anthony Fok Closes: 990418 990907 993202 Changes: gnome-shell-extension-weather (0.0~git20210509.d714eb1-1) unstable; urgency=medium . * New upstream version 0.0~git20210509.d714eb1 (gnome40 branch) * Set debian/watch to track upstream "gnome40" branch * Bump gnome-shell dependency to (>= 40) (Closes: #993202) * Fix upstream URL in debian/control and debian/copyright as the project was moved from GitHub to GitLab back in June 2018 (Closes: #990907) * Add dependency on ca-certificates to prevent SSL handshake failure when loading openweathermap data. Thanks to Alexei Ustyuzhaninov for the report and Adrian Bunk for the fix (Closes: #990418) * Bump Standards-Version to 4.6.0 (no change) Checksums-Sha1: f630f20e6efec1d91d7abc80aaa6b50b31bb2a9e 2257 gnome-shell-extension-weather_0.0~git20210509.d714eb1-1.dsc 8b998e2686d70692a7a7a85bc7696365416a0b93 515940 gnome-shell-extension-weather_0.0~git20210509.d714eb1.orig.tar.xz 1d94b3d43dd3b158396ea7625bc73ac79cae8680 5696 gnome-shell-extension-weather_0.0~git20210509.d714eb1-1.debian.tar.xz cb207ef40879138d69f6b8727c9ec44bdc31b47a 8057 gnome-shell-extension-weather_0.0~git20210509.d714eb1-1_amd64.buildinfo Checksums-Sha256: 8aeec60e5b0c2e29a81831f59763290c27c1823ad27fa416c6c3cac67ee5ef89 2257 gnome-shell-extension-weather_0.0~git20210509.d714eb1-1.dsc ac355fc9f1fc92e8a95b370936b79582ea4c5f045d1a26c2768bf8fe43f8fae6 515940 gnome-shell-extension-weather_0.0~git20210509.d714eb1.orig.tar.xz ed59f549b49c3f1e8b0a52500ae62012d7a0937d06c854ca46cb293175fdfc86 5696 gnome-shell-extension-weather_0.0~git20210509.d714eb1-1.debian.tar.xz 8388adde975a426824282705a0a696a11bfea69549794a35ac90fb3ab9e0eb89 8057 gnome-shell-extension-weather_0.0~git20210509.d714eb1-1_amd64.buildinfo Files: cf67dd22fdb7ce2d267b9597c172fb1b 2257 gnome optional gnome-shell-extension-weather_0.0~git20210509.d714eb1-1.dsc 1cadff8e906a74d1113c9fc01f563a8c 515940 gnome optional gnome-shell-extension-weather_0.0~git20210509.d714eb1.orig.tar.xz 8642ee633f6f32d6f1f90a44194142b3 5696 gnome optional gnome-shell-extension-weather_0.0~git20210509.d714eb1-1.debian.tar.xz bd759a82915541
Bug#983222: marked as done (python-cartopy: FTBFS with PROJ 8.0.0)
Your message dated Sat, 18 Sep 2021 06:18:58 +
with message-id
and subject line Bug#983222: fixed in python-cartopy 0.20.0+dfsg-1~exp1
has caused the Debian Bug report #983222,
regarding python-cartopy: FTBFS with PROJ 8.0.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
983222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cartopy
Version: 0.18.0+dfsg-2
Severity: important
Tags: upstream ftbfs
User: debian-...@lists.debian.org
Usertags: proj-8.0
Control: forwarded -1 https://github.com/SciTools/cartopy/issues/1140
Dear Maintainer,
Your package FTBFS with PROJ 8.0.0:
lib/cartopy/trace.cpp:632:10: fatal error: proj_api.h: No such file or
directory
632 | #include "proj_api.h"
| ^~~~
It needs to be ported to use proj.h instead of proj_api.h which has been
removed.
Kind Regards,
Bas
dpkg-checkbuilddeps: error: Unmet build dependencies: python3-filelock
python3-fiona python3-matplotlib python3-pykdtree python3-pyshp python3-scipy
python3-tk xvfb
[1;33mW: Unmet build-dependency in source[0m
dh clean --with python3 --buildsystem=pybuild
debian/rules override_dh_auto_clean
make[1]: Entering directory '/home/bas/tmp/debian/python-cartopy-0.18.0+dfsg'
dh_auto_clean || true
I: pybuild base:217: python3.7 setup.py clean
running clean
removing
'/home/bas/tmp/debian/python-cartopy-0.18.0+dfsg/.pybuild/cpython3_3.7_cartopy/build'
(and everything under it)
'build/bdist.linux-amd64' does not exist -- can't clean it
'build/scripts-3.7' does not exist -- can't clean it
rm -f -r .pybuild
rm -f -r __pycache__
make[1]: Leaving directory '/home/bas/tmp/debian/python-cartopy-0.18.0+dfsg'
dh_autoreconf_clean -O--buildsystem=pybuild
dh_clean -O--buildsystem=pybuild
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building python-cartopy using existing
./python-cartopy_0.18.0+dfsg.orig.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: building python-cartopy in
python-cartopy_0.18.0+dfsg-3.debian.tar.xz
dpkg-source: info: building python-cartopy in python-cartopy_0.18.0+dfsg-3.dsc
[0mI: Generating source changes file for original dsc[0m
dpkg-genchanges: info: not including original source code in upload
[0mI: Copying COW directory[0m
[0mI: forking: rm -rf /var/cache/pbuilder/build/cow.14726[0m
[0mI: forking: cp -al /var/cache/pbuilder/base-sid+rebuild.cow
/var/cache/pbuilder/build/cow.14726[0m
[0mI: removed stale ilistfile /var/cache/pbuilder/build/cow.14726/.ilist[0m
[0mI: forking: chroot /var/cache/pbuilder/build/cow.14726
cowdancer-ilistcreate /.ilist 'find . -xdev -path ./home -prune -o \( \( -type
l -o -type f \) -a -links +1 -print0 \) | xargs -0 stat --format '%d %i ''[0m
[0mI: Invoking pbuilder[0m
[0mI: forking: pbuilder build --debbuildopts --debbuildopts --buildplace
/var/cache/pbuilder/build/cow.14726 --buildresult /var/cache/pbuilder/result/
--mirror http://ftp.nl.debian.org/debian/ --distribution sid --no-targz
--internal-chrootexec 'chroot /var/cache/pbuilder/build/cow.14726 cow-shell'
/home/bas/tmp/debian/python-cartopy_0.18.0+dfsg-3.dsc[0m
[0mI: Running in no-targz mode[0m
[0mI: pbuilder: network access will be disabled during build[0m
[0mI: Current time: Sun Feb 21 10:37:46 CET 2021[0m
[0mI: pbuilder-time-stamp: 1613900266[0m
[0mI: copying local configuration[0m
[1;33mW: --override-config is not set; not updating apt.conf Read the manpage
for details.[0m
[0mI: mounting /proc filesystem[0m
[0mI: mounting /sys filesystem[0m
[0mI: creating /{dev,run}/shm[0m
[0mI: mounting /dev/pts filesystem[0m
[0mI: redirecting /dev/ptmx to /dev/pts/ptmx[0m
[0mI: policy-rc.d already exists[0m
[0mI: Obtaining the cached apt archive contents[0m
[0mI: Copying source file[0m
[0mI: copying [/home/bas/tmp/debian/python-cartopy_0.18.0+dfsg-3.dsc][0m
[0mI: copying [/home/bas/tmp/debian/python-cartopy_0.18.0+dfsg.orig.tar.xz][0m
[0mI: copying
[/home/bas/tmp/debian/python-cartopy_0.18.0+dfsg-3.debian.tar.xz][0m
[0mI: Extracting source[0m
dpkg-source: warning: extracting unsigned source package
(python-cartopy_0.18.0+dfsg-3.dsc)
dpkg-source: info: extracting python-cartopy in python-cartopy-0.18.0+dfsg
dpkg-source: info: unpacking python-cartopy_0.18.0+dfsg.orig.tar.xz
dpkg-source: info: unpacking python-cartopy_0.18.0+dfsg-3.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying 0001-Skip-tests-failing-on-i386-architect
Bug#990907: marked as done (gnome-shell-extension-weather: Homepage in debian/control points to defunct location)
Your message dated Sat, 18 Sep 2021 06:18:37 + with message-id and subject line Bug#990907: fixed in gnome-shell-extension-weather 0.0~git20210509.d714eb1-1 has caused the Debian Bug report #990907, regarding gnome-shell-extension-weather: Homepage in debian/control points to defunct location 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.) -- 990907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-shell-extension-weather Version: 0.0~git20201103.d8be50f-1 Severity: minor The new upstream location seems to be https://gitlab.com/jenslody/gnome-shell-extension-openweather --- End Message --- --- Begin Message --- Source: gnome-shell-extension-weather Source-Version: 0.0~git20210509.d714eb1-1 Done: Anthony Fok We believe that the bug you reported is fixed in the latest version of gnome-shell-extension-weather, 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 990...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anthony Fok (supplier of updated gnome-shell-extension-weather 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: Fri, 17 Sep 2021 23:19:51 -0600 Source: gnome-shell-extension-weather Architecture: source Version: 0.0~git20210509.d714eb1-1 Distribution: unstable Urgency: medium Maintainer: Anthony Fok Changed-By: Anthony Fok Closes: 990418 990907 993202 Changes: gnome-shell-extension-weather (0.0~git20210509.d714eb1-1) unstable; urgency=medium . * New upstream version 0.0~git20210509.d714eb1 (gnome40 branch) * Set debian/watch to track upstream "gnome40" branch * Bump gnome-shell dependency to (>= 40) (Closes: #993202) * Fix upstream URL in debian/control and debian/copyright as the project was moved from GitHub to GitLab back in June 2018 (Closes: #990907) * Add dependency on ca-certificates to prevent SSL handshake failure when loading openweathermap data. Thanks to Alexei Ustyuzhaninov for the report and Adrian Bunk for the fix (Closes: #990418) * Bump Standards-Version to 4.6.0 (no change) Checksums-Sha1: f630f20e6efec1d91d7abc80aaa6b50b31bb2a9e 2257 gnome-shell-extension-weather_0.0~git20210509.d714eb1-1.dsc 8b998e2686d70692a7a7a85bc7696365416a0b93 515940 gnome-shell-extension-weather_0.0~git20210509.d714eb1.orig.tar.xz 1d94b3d43dd3b158396ea7625bc73ac79cae8680 5696 gnome-shell-extension-weather_0.0~git20210509.d714eb1-1.debian.tar.xz cb207ef40879138d69f6b8727c9ec44bdc31b47a 8057 gnome-shell-extension-weather_0.0~git20210509.d714eb1-1_amd64.buildinfo Checksums-Sha256: 8aeec60e5b0c2e29a81831f59763290c27c1823ad27fa416c6c3cac67ee5ef89 2257 gnome-shell-extension-weather_0.0~git20210509.d714eb1-1.dsc ac355fc9f1fc92e8a95b370936b79582ea4c5f045d1a26c2768bf8fe43f8fae6 515940 gnome-shell-extension-weather_0.0~git20210509.d714eb1.orig.tar.xz ed59f549b49c3f1e8b0a52500ae62012d7a0937d06c854ca46cb293175fdfc86 5696 gnome-shell-extension-weather_0.0~git20210509.d714eb1-1.debian.tar.xz 8388adde975a426824282705a0a696a11bfea69549794a35ac90fb3ab9e0eb89 8057 gnome-shell-extension-weather_0.0~git20210509.d714eb1-1_amd64.buildinfo Files: cf67dd22fdb7ce2d267b9597c172fb1b 2257 gnome optional gnome-shell-extension-weather_0.0~git20210509.d714eb1-1.dsc 1cadff8e906a74d1113c9fc01f563a8c 515940 gnome optional gnome-shell-extension-weather_0.0~git20210509.d714eb1.orig.tar.xz 8642ee633f6f32d6f1f90a44194142b3 5696 gnome optional gnome-shell-extension-weather_0.0~git20210509.d714eb1-1.debian.tar.xz bd759a82915541d465dfbb175871c2de 8057 gnome optional gnome-shell-extension-weather_0.0~git20210509.d714eb1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEEFCQhsZrUqVmW+VBy6iUAtBLFms8FAmFFgNAQHGZva2FAZGVi aWFuLm9yZwAKCRDqJQC0EsWaz+29D/sGaG0m6IO3//ouUBrfKcxwEYeNZUh9jo96 jVCwIAFw73tluSLAs3nInqGDZv+/03mAfCAuSZLnBrUym7TcphRIduKLGwhgqu97 X5rnEE7Ckzb9sEXdEuU462yDsw1G/xa3Odkkwv5Y/Ta8C6LrdTB8o04KrHplXBw1 ZwP0uOBEGu4nrIlaY6TDrIPOqghGqlL+z35gXyX8Fe9OaEy4B4GsEBxvjFtMRW0q yMIu6q/QJQOSQ0XC1bCOh92Z6QV3ZkGKokWTb/8rhlxE002/XqU1oZnd/ywQRYUw nFejazJksOzvbcuf/Ee0CGvpH8FcEt2vEXrpCjgJeON3
Bug#990418: marked as done (SSL handshake failed when loading openweathermap data)
Your message dated Sat, 18 Sep 2021 06:18:37 + with message-id and subject line Bug#990418: fixed in gnome-shell-extension-weather 0.0~git20210509.d714eb1-1 has caused the Debian Bug report #990418, regarding SSL handshake failed when loading openweathermap data 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.) -- 990418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990418 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell-extension-weather Version: 0.0~git20201103.d8be50f-1 Severity: important The extensiond doesn't show the weather information for me. A quick debuging shows that it can't access the openweathermap api with error "SSL handshake failed". The sasame url (https://api.openweathermap.org/data/2.5/weather?lon=60.6082502&lat=56.8391034&units=metric&APPID=) is opened in a browser without a problem. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.9 (SMP w/6 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8), LANGUAGE=ru:en_US:en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages gnome-shell-extension-weather depends on: pn dconf-gsettings-backend | gsettings-backend ii gir1.2-clutter-1.0 1.26.4+dfsg-1 ii gir1.2-glib-2.0 1.66.1-1+b1 ii gir1.2-gtk-3.0 3.24.23-3 ii gir1.2-soup-2.4 2.72.0-2 ii gnome-shell 3.38.3-2 Versions of packages gnome-shell-extension-weather recommends: ii gnome-tweaks 3.34.0-4 gnome-shell-extension-weather suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: gnome-shell-extension-weather Source-Version: 0.0~git20210509.d714eb1-1 Done: Anthony Fok We believe that the bug you reported is fixed in the latest version of gnome-shell-extension-weather, 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 990...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anthony Fok (supplier of updated gnome-shell-extension-weather 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: Fri, 17 Sep 2021 23:19:51 -0600 Source: gnome-shell-extension-weather Architecture: source Version: 0.0~git20210509.d714eb1-1 Distribution: unstable Urgency: medium Maintainer: Anthony Fok Changed-By: Anthony Fok Closes: 990418 990907 993202 Changes: gnome-shell-extension-weather (0.0~git20210509.d714eb1-1) unstable; urgency=medium . * New upstream version 0.0~git20210509.d714eb1 (gnome40 branch) * Set debian/watch to track upstream "gnome40" branch * Bump gnome-shell dependency to (>= 40) (Closes: #993202) * Fix upstream URL in debian/control and debian/copyright as the project was moved from GitHub to GitLab back in June 2018 (Closes: #990907) * Add dependency on ca-certificates to prevent SSL handshake failure when loading openweathermap data. Thanks to Alexei Ustyuzhaninov for the report and Adrian Bunk for the fix (Closes: #990418) * Bump Standards-Version to 4.6.0 (no change) Checksums-Sha1: f630f20e6efec1d91d7abc80aaa6b50b31bb2a9e 2257 gnome-shell-extension-weather_0.0~git20210509.d714eb1-1.dsc 8b998e2686d70692a7a7a85bc7696365416a0b93 515940 gnome-shell-extension-weather_0.0~git20210509.d714eb1.orig.tar.xz 1d94b3d43dd3b158396ea7625bc73ac79cae8680 5696 gnome-shell-extension-weather_0.0~git20210509.d714eb1-1.debian.tar.xz cb207ef40879138d69f6b8727c9ec44bdc31b47a 8057 gnome-shell-extension-weather_0.0~git20210509.d714eb1-1_amd64.buildinfo Checksums-Sha256: 8aeec60e5b0c2e29a81831f59763290c27c1823ad27fa416c6c3cac67ee5ef89 2257 gnome-shell-extension-weather_0.0~git20210509.d714eb1-1.dsc ac355fc9f1fc92e8a95b370936b79582ea4c5f045d1a26c2768bf8fe43f8fae6 515940 gnome-shell-extension-weather_0.0~git20210509.d714eb1.orig.tar.xz ed59f
Bug#950897: marked as done (gopher FTCBFS: does not pass --host to ./configure)
Your message dated Sat, 18 Sep 2021 06:18:50 +
with message-id
and subject line Bug#950897: fixed in gopher 3.0.17.3+nmu1
has caused the Debian Bug report #950897,
regarding gopher FTCBFS: does not pass --host to ./configure
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.)
--
950897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gopher
Version: 3.0.17.3
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
gopher fails to cross build from source, because it does not pass --host
to ./configure. The easiest way of doing so - using dh_auto_configure -
makes gopher cross buildable. Please consider applying the attached
patch.
Helmut
diff --minimal -Nru gopher-3.0.17.3/debian/changelog
gopher-3.0.17.3+nmu1/debian/changelog
--- gopher-3.0.17.3/debian/changelog2019-10-11 18:09:18.0 +0200
+++ gopher-3.0.17.3+nmu1/debian/changelog 2020-02-07 17:10:55.0
+0100
@@ -1,3 +1,10 @@
+gopher (3.0.17.3+nmu1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTCBFS: Let dh_auto_configure pass --host to ./configure. (Closes: #-1)
+
+ -- Helmut Grohne Fri, 07 Feb 2020 17:10:55 +0100
+
gopher (3.0.17.3) unstable; urgency=medium
* Remove empty directories. Closes: #942181.
diff --minimal -Nru gopher-3.0.17.3/debian/rules
gopher-3.0.17.3+nmu1/debian/rules
--- gopher-3.0.17.3/debian/rules2019-10-11 18:09:07.0 +0200
+++ gopher-3.0.17.3+nmu1/debian/rules 2020-02-07 17:10:54.0 +0100
@@ -19,10 +19,7 @@
autoconf
autoheader
ln -vs /usr/share/gnulib/lib/getloadavg.c .
- ./configure --prefix=/usr --mandir=\$${prefix}/share/man \
- --infodir=\$${prefix}/share/info --disable-auth \
- --sysconfdir=/etc
-
+ dh_auto_configure -- --disable-auth
touch configure-stamp
build: build-stamp
--- End Message ---
--- Begin Message ---
Source: gopher
Source-Version: 3.0.17.3+nmu1
Done: Boyuan Yang
We believe that the bug you reported is fixed in the latest version of
gopher, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 950...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Boyuan Yang (supplier of updated gopher 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, 18 Sep 2021 01:57:34 -0400
Source: gopher
Architecture: source
Version: 3.0.17.3+nmu1
Distribution: unstable
Urgency: high
Maintainer: John Goerzen
Changed-By: Boyuan Yang
Closes: 950897 978822
Changes:
gopher (3.0.17.3+nmu1) unstable; urgency=high
.
* Non-maintainer upload.
* debian/source/format: Explicitly use "3.0 (native)" format.
* debian/changelog: Remove trailing spaces.
* debian/rules: Provide recommended targets: build-arch, build-indep.
* debian/rules: Use dh_autoreconf and dh_auto_configure to fix FTBFS
with autoconf 2.70+. (Closes: #978822)
+ Also fixes FTCBFS. (Closes: #950897)
Checksums-Sha1:
dbcad90fa2a4d7157139f7e7dc051c848581560d 1448 gopher_3.0.17.3+nmu1.dsc
12523020272971c3dc37a719f4b01e9ada321241 241268 gopher_3.0.17.3+nmu1.tar.xz
8984a3c0283a25e52a490347a81a1ea96ddc4eea 6105
gopher_3.0.17.3+nmu1_amd64.buildinfo
Checksums-Sha256:
83b68dd8312500065e8b91d804e1bbe782272313a35bfc3703316db43c04f901 1448
gopher_3.0.17.3+nmu1.dsc
0236e6be76cd1e5e0ed51f54d92bbca29dbd63a33f23ab12d0e8fa2d9f7a1804 241268
gopher_3.0.17.3+nmu1.tar.xz
0b956559e0d56e2b62a03170646c8c868698e40f4cbb9a93332da6dfea00f7d6 6105
gopher_3.0.17.3+nmu1_amd64.buildinfo
Files:
23beb95ef6f5c25d52244688217bdf37 1448 net optional gopher_3.0.17.3+nmu1.dsc
9039b70fe38ac01865771e4cbb189a99 241268 net optional
gopher_3.0.17.3+nmu1.tar.xz
b5f4864507e1d004b8f646b99214159d 6105 net optional
gopher_3.0.17.3+nmu1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmFFgB8ACgkQwpPntGGC
Ws4eERAAroTu8rZsfNrJfAuj/wYLg+CacVXJBzmMOoDtQ80/Tp0wHfWXBSZAL2xd
xUcg76Y9Pt4DWPbLik+wqHRqRxKcYVVUik1KTcm+R6TPZbTVXsbyTvE/eOk4AbN8
R2i0C1CLH3J07YFYStSqoHk31Ok8NC53/YJT/IPjAKUkbIl9C42BQ9qYUd6r5aXZ
2DCiJ/xAUti2wGtrVdykO
Bug#978822: marked as done (gopher: ftbfs with autoconf 2.70)
Your message dated Sat, 18 Sep 2021 06:18:50 + with message-id and subject line Bug#978822: fixed in gopher 3.0.17.3+nmu1 has caused the Debian Bug report #978822, regarding gopher: ftbfs with autoconf 2.70 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.) -- 978822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978822 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gopher Version: 3.0.17.3 Severity: normal Tags: sid bookworm User: d...@debian.org Usertags: ftbfs-ac270 [This bug report is not targeted to the upcoming bullseye release] The package fails to build in a test rebuild on at least amd64 with autoconf 2.70, but succeeds to build with autoconf 2.69. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://qa-logs.debian.net/2020/09/26.ac270/gopher_3.0.17.3_unstable_ac270.log The last lines of the build log are at the end of this report. To build with autoconf 2.70, please install the autoconf package from experimental: apt-get -t=experimental install autoconf [...] -- checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether the compiler supports GNU C... yes checking whether gcc accepts -g... yes checking for gcc option to enable C11 features... none needed checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for ranlib... ranlib checking whether make sets $(MAKE)... yes checking for main in -lm... yes checking for connect... yes checking for gethostname... yes checking for re_comp in -lcompat... no checking for main in -lmalloc... no checking for main in -lcurses... yes checking for main in -ltermcap... yes checking for dirent.h that defines DIR... yes checking for library containing opendir... none required checking for sys/types.h... yes checking for sys/stat.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for sys/time.h... yes checking for sys/param.h... yes checking for vfork.h... no checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for sys/wait.h that is POSIX.1 compatible... yes checking for strings.h... (cached) yes checking for string.h... yes checking for sys/param.h... (cached) yes checking for term.h... yes checking for re_comp.h... yes checking for regex.h... yes checking for crypt.h... yes checking for fcntl.h... yes checking for time.h... yes checking for ctype.h... yes checking for limits.h... yes checking for locale.h... yes checking for sys/types.h... (cached) yes checking for sys/stat.h... (cached) yes checking for sys/file.h... yes checking for sys/ioctl.h... yes checking for sys/time.h... (cached) yes checking for syslog.h... yes checking for unistd.h... (cached) yes checking for malloc.h... yes checking for stdlib.h... yes checking for libgen.h... yes checking for regexp.h... no checking for an ANSI C-conforming const... yes checking how to run the C preprocessor... gcc -E checking for uid_t in sys/types.h... yes checking for pid_t... yes checking for size_t... yes checking whether struct tm is in sys/time.h or time.h... time.h checking whether gcc needs -traditional... no checking build system type... Invalid configuration `x86_64-unknown-linuxoldld': machine `x86_64-unknown' not recognized configure: error: /bin/bash ./config.sub x86_64-unknown-linuxoldld failed make: *** [debian/rules:22: configure-stamp] Error 1 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 --- End Message --- --- Begin Message --- Source: gopher Source-Version: 3.0.17.3+nmu1 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of gopher, 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 978...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated gopher package) (This message was generated automatically at their r
Processed: closing 994585
Processing commands for cont...@bugs.debian.org: > close 994585 Bug #994585 [release.debian.org] nmu: ricochet-im_1.1.4-3+b5 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 994585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#994256: marked as done (django-axes: autopkgtest needs update for new version of python-django: warnings changed)
Your message dated Sat, 18 Sep 2021 03:18:43 +
with message-id
and subject line Bug#994256: fixed in django-axes 5.24.0-1
has caused the Debian Bug report #994256,
regarding django-axes: autopkgtest needs update for new version of
python-django: warnings changed
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.)
--
994256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-axes
Version: 5.4.3-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, python-dja...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python-django
Dear maintainer(s),
With a recent upload of python-django the autopkgtest of django-axes
fails in testing when that autopkgtest is run with the binary packages
of python-django from unstable. It passes when run with only packages
from testing. In tabular form:
passfail
python-django from testing2:3.2.7-4
django-axesfrom testing5.4.3-1
versioned deps [0] from testingfrom unstable
all others from testingfrom testing
I copied some of the output at the bottom of this report. It seems to me
that some warnings were added and updated.
Currently this regression is blocking the migration of python-django to
testing [1]. Of course, python-django shouldn't just break your
autopkgtest (or even worse, your package), but it seems to me that the
change in python-django was intended and your package needs to update to
the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from python-django should
really add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
python-django/2:3.2.7-4. I.e. due to versioned dependencies or
breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=python-django
https://ci.debian.net/data/autopkgtest/testing/amd64/d/django-axes/15232617/log.gz
=== FAILURES
===
_ CacheCheckTestCase.test_cache_check
__
self =
@override_settings(
AXES_HANDLER="axes.handlers.cache.AxesCacheHandler",
CACHES={
"default": {
"BACKEND": "django.core.cache.backends.db.DatabaseCache",
"LOCATION": "axes_cache",
}
},
)
def test_cache_check(self):
warnings = run_checks()
> self.assertEqual(warnings, [])
E AssertionError: Lists differ: [, id='models.W042'>
E
E Diff is 739 characters long. Set self.maxDiff to None to see it.
axes/tests/test_checks.py:21: AssertionError
_
CacheCheckTestCase.test_cache_check_does_not_produce_check_warnings_with_database_handler
_
self =
@override_settings(
AXES_HANDLER="axes.handlers.database.AxesDatabaseHandler",
CACHES={
"default": {"BACKEND":
"django.core.cache.backends.locmem.LocMemCache"}
},
)
def
test_cache_check_does_not_produce_check_warnings_with_database_handler(self):
warnings = run_checks()
> self.assertEqual(warnings, [])
E AssertionError: Lists differ: [, id='models.W042'>
E
E Diff is 739 characters long. Set self.maxDiff to None to see it.
axes/tests/test_checks.py:45: AssertionError
_ CacheCheckTestCase.test_cache_check_warnings
_
self =
@override_settings(
AXES_HANDLER="axes.handlers.cache.AxesCacheHandler",
CACHES={
"default": {"BACKEND":
"django.core.cache.backends.locmem.LocMemCache"}
},
)
def test_cache_check_warnings(self):
warnings = run_checks()
warning = Warning(
msg=Messages.CACHE_INVALID, hint=Hints.CACHE_INVALID,
id=Codes.CACHE_INVALID
)
> self.assertEqual(warnings, [warning])
E AssertionError: Lists differ: [, , id='models.W042'>
E
E Diff is 2408
Bug#956354: marked as done (libuser: Please stop using deprecated and headers)
Your message dated Sat, 18 Sep 2021 02:35:12 + with message-id and subject line Bug#956354: fixed in libuser 1:0.63~dfsg-1 has caused the Debian Bug report #956354, regarding libuser: Please stop using deprecated and headers 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.) -- 956354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libuser Version: 1:0.62~dfsg-0.3 Severity: important Tags: sid bullseye User: selinux-de...@lists.alioth.debian.org Usertags: selinux flask-removal Dear Maintainer, Your package is using either and/or and hardcoded SELinux security classes or permissions. This is deprecated for about 5 years and upstream has now decided to remove these completely in the upcoming 3.1 release. Your package should be ported to dynamically query the security classes and permissions instead of relying on the hardcoded ones and remove these headers. I will bump the severity of this bug to serious when libselinux 3.1 is finally released as your package will FTBFS. Don't hesitate to contact me if you have any questions. Kind regards, Laurent Bigonville --- End Message --- --- Begin Message --- Source: libuser Source-Version: 1:0.63~dfsg-1 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of libuser, 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 956...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated libuser 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: Fri, 17 Sep 2021 21:59:16 -0400 Source: libuser Architecture: source Version: 1:0.63~dfsg-1 Distribution: unstable Urgency: medium Maintainer: Boyuan Yang Changed-By: Boyuan Yang Closes: 956354 984732 Changes: libuser (1:0.63~dfsg-1) unstable; urgency=medium . * New upstream release. (Closes: #984732) + No longer uses deprecated SELinux headers. (Closes: #956354) * debian/control: Mark libuser1 and libuser1-dev as Multi-Arch: same. Checksums-Sha1: b1e8336cf45221425c25879b36d600d4b24f47fa 2067 libuser_0.63~dfsg-1.dsc 8ed6c51e39946f333b1d76b8b17e8fec8b984b5e 359192 libuser_0.63~dfsg.orig.tar.xz a3f0aa4052e12169ca4b3873fc9ad08953e427cb 6816 libuser_0.63~dfsg-1.debian.tar.xz fc5b7ee6c1526d90088ffcc5b51e7e7809dc950d 9019 libuser_0.63~dfsg-1_amd64.buildinfo Checksums-Sha256: 71c76667b9d4dda9fddce80c07cbe6f5065d2faf2aa4ec63a46b3fc3f9ed088c 2067 libuser_0.63~dfsg-1.dsc 1cbc26afd631b224a4548e6aa4d7f14f5585838290fb368a2027007c08b3b27a 359192 libuser_0.63~dfsg.orig.tar.xz a5b6bf1063ae6971c62224e819eeff4f6bf8de3b06f5b98835246c7fd0e65493 6816 libuser_0.63~dfsg-1.debian.tar.xz 53aa9cddebe894c48150aff1888d1ec1095c180fed93fd8725efb4b6f79424b4 9019 libuser_0.63~dfsg-1_amd64.buildinfo Files: aaf536657ab7bf7a3c98d573212c2be2 2067 admin optional libuser_0.63~dfsg-1.dsc 38c006a26d208101c3d15926b7122579 359192 admin optional libuser_0.63~dfsg.orig.tar.xz abc4c9e1ac916bf16dc2261ce0a9a01c 6816 admin optional libuser_0.63~dfsg-1.debian.tar.xz 86d9f291bdc52200a2cabc014667a15b 9019 admin optional libuser_0.63~dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmFFSHUACgkQwpPntGGC Ws6Mag/9EYUjilZGkwCSDMP0a6OmU+4ufmLniRGw6O8OHtPN86x19dUi7pp5tRHA rmralu9WegCVgqGKft3Ju2MJxyPZrq8FZ/lzQ1HegCnXu4zlQ09kOk2X4Q2CwJR9 AEdKJT+s2tBH1zfoXxc1yMDAfrDnmlbHyh+A0YHaxJMVUJQZyulrpVWgaxp6J0ED xG45YT9MBbH1tLlUlwE4pI08xYTIBVv2mCpE2mNzTqNVkAiFKpDJCmL6+UZ0GNfs 0vVPCV78rtmzVdKP2rAuSXxgpVq308me74iwdR65wYDrIYjZ2fs7nYFIOIlqLUfr 3TAD1N7o5F90zw03yYV6eR4OT/kWMy73I28OP0Bze2z+BIUa00Sq3vnuiRz+h09g WgkPI8ez050RqitZaUxh+Lny/AfYRQryp5pi8tkkY0z9/ApzYLmWb7yXRZat/oKR T0BgtZqnwOx1TBULqfRm8rmGdAy3qG4M8NtLkhODf5MudojiaPvBiuboL5hI8DG7 fL4+lcTKBn0GFBM2Y0bXMkWP6YIwdfjeX6J86UZrqNHMyR0letCC0ek52URxWKXu y3KQcmEDorX3xSK2x5hhbs0kpPwR1iFvIk3t78FZdb+kRIeIjCLjHSSWyh3Gm8Gb u+rjOpyTfW083mnbeLeECGS/3cqDf3O+qpsq+a2EAjLGEdQNdKY= =L9nL -END PGP SIGNATURE End Message ---
Bug#984732: marked as done (libuser: Please package new upstream release (0.63))
Your message dated Sat, 18 Sep 2021 02:35:12 + with message-id and subject line Bug#984732: fixed in libuser 1:0.63~dfsg-1 has caused the Debian Bug report #984732, regarding libuser: Please package new upstream release (0.63) 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.) -- 984732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libuser Version: 1:0.62~dfsg-0.4 Severity: normal X-Debbugs-CC: tzaf...@debian.org g...@debian.org Dear Debian libuser package maintainers, The upstream of libuser has released a new version v0.63. Please consider packaging it in Debian. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: libuser Source-Version: 1:0.63~dfsg-1 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of libuser, 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 984...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated libuser 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: Fri, 17 Sep 2021 21:59:16 -0400 Source: libuser Architecture: source Version: 1:0.63~dfsg-1 Distribution: unstable Urgency: medium Maintainer: Boyuan Yang Changed-By: Boyuan Yang Closes: 956354 984732 Changes: libuser (1:0.63~dfsg-1) unstable; urgency=medium . * New upstream release. (Closes: #984732) + No longer uses deprecated SELinux headers. (Closes: #956354) * debian/control: Mark libuser1 and libuser1-dev as Multi-Arch: same. Checksums-Sha1: b1e8336cf45221425c25879b36d600d4b24f47fa 2067 libuser_0.63~dfsg-1.dsc 8ed6c51e39946f333b1d76b8b17e8fec8b984b5e 359192 libuser_0.63~dfsg.orig.tar.xz a3f0aa4052e12169ca4b3873fc9ad08953e427cb 6816 libuser_0.63~dfsg-1.debian.tar.xz fc5b7ee6c1526d90088ffcc5b51e7e7809dc950d 9019 libuser_0.63~dfsg-1_amd64.buildinfo Checksums-Sha256: 71c76667b9d4dda9fddce80c07cbe6f5065d2faf2aa4ec63a46b3fc3f9ed088c 2067 libuser_0.63~dfsg-1.dsc 1cbc26afd631b224a4548e6aa4d7f14f5585838290fb368a2027007c08b3b27a 359192 libuser_0.63~dfsg.orig.tar.xz a5b6bf1063ae6971c62224e819eeff4f6bf8de3b06f5b98835246c7fd0e65493 6816 libuser_0.63~dfsg-1.debian.tar.xz 53aa9cddebe894c48150aff1888d1ec1095c180fed93fd8725efb4b6f79424b4 9019 libuser_0.63~dfsg-1_amd64.buildinfo Files: aaf536657ab7bf7a3c98d573212c2be2 2067 admin optional libuser_0.63~dfsg-1.dsc 38c006a26d208101c3d15926b7122579 359192 admin optional libuser_0.63~dfsg.orig.tar.xz abc4c9e1ac916bf16dc2261ce0a9a01c 6816 admin optional libuser_0.63~dfsg-1.debian.tar.xz 86d9f291bdc52200a2cabc014667a15b 9019 admin optional libuser_0.63~dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmFFSHUACgkQwpPntGGC Ws6Mag/9EYUjilZGkwCSDMP0a6OmU+4ufmLniRGw6O8OHtPN86x19dUi7pp5tRHA rmralu9WegCVgqGKft3Ju2MJxyPZrq8FZ/lzQ1HegCnXu4zlQ09kOk2X4Q2CwJR9 AEdKJT+s2tBH1zfoXxc1yMDAfrDnmlbHyh+A0YHaxJMVUJQZyulrpVWgaxp6J0ED xG45YT9MBbH1tLlUlwE4pI08xYTIBVv2mCpE2mNzTqNVkAiFKpDJCmL6+UZ0GNfs 0vVPCV78rtmzVdKP2rAuSXxgpVq308me74iwdR65wYDrIYjZ2fs7nYFIOIlqLUfr 3TAD1N7o5F90zw03yYV6eR4OT/kWMy73I28OP0Bze2z+BIUa00Sq3vnuiRz+h09g WgkPI8ez050RqitZaUxh+Lny/AfYRQryp5pi8tkkY0z9/ApzYLmWb7yXRZat/oKR T0BgtZqnwOx1TBULqfRm8rmGdAy3qG4M8NtLkhODf5MudojiaPvBiuboL5hI8DG7 fL4+lcTKBn0GFBM2Y0bXMkWP6YIwdfjeX6J86UZrqNHMyR0letCC0ek52URxWKXu y3KQcmEDorX3xSK2x5hhbs0kpPwR1iFvIk3t78FZdb+kRIeIjCLjHSSWyh3Gm8Gb u+rjOpyTfW083mnbeLeECGS/3cqDf3O+qpsq+a2EAjLGEdQNdKY= =L9nL -END PGP SIGNATURE End Message ---
Bug#992922: marked as done (gpgme1.0 FTBFS on 32bit: segfault during tests)
Your message dated Sat, 18 Sep 2021 01:33:53 +
with message-id
and subject line Bug#992922: fixed in gpgme1.0 1.16.0-1.1
has caused the Debian Bug report #992922,
regarding gpgme1.0 FTBFS on 32bit: segfault during tests
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.)
--
992922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992922
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gpgme1.0
Version: 1.16.0-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=gpgme1.0&ver=1.16.0-1
...
[-- Response --]
pub:-:1024:17:FE180B1DA9E3B0B2:920888034:0::-:::sca
fpr:D695676BDCEDCC2CDD6152BCFE180B1DA9E3B0B2:
sub:-:1024:16:5381EA4EE29BA37F:920888071:0:e
fpr:FA23A4BE04E938CF921EDE7E5381EA4EE29BA37F:
uid:-Bob (demo key):::S10 S3 H3 H2 Z2 Z1,no-ks-modify:1,p::
uid:-Bravo Test (demo key) :::S10 S3 H3 H2 Z2
Z1,no-ks-modify:2,::
pub:-:1024:17:FE180B1DA9E3B0B2:920888034:0::-:::sca
fpr:D695676BDCEDCC2CDD6152BCFE180B1DA9E3B0B2:
sub:-:1024:16:5381EA4EE29BA37F:920888071:0:e
fpr:FA23A4BE04E938CF921EDE7E5381EA4EE29BA37F:
uid:-Bob (demo key):::S10 S3 H3 H2 Z2 Z1,no-ks-modify:1,ps::
uid:-Bravo Test (demo key) :::S10 S3 H3 H2 Z2
Z1,no-ks-modify:2,::
pub:-:1024:17:FE180B1DA9E3B0B2:920888034:0::-:::sca
fpr:D695676BDCEDCC2CDD6152BCFE180B1DA9E3B0B2:
sub:-:1024:16:5381EA4EE29BA37F:920888071:0:e
fpr:FA23A4BE04E938CF921EDE7E5381EA4EE29BA37F:
uid:-Bob (demo key):::S10 S3 H3 H2 Z2 Z1,no-ks-modify:1,psm::
uid:-Bravo Test (demo key) :::S10 S3 H3 H2 Z2
Z1,no-ks-/bin/bash: line 6: 591523 Segmentation fault
GNUPGHOME=/<>/build/tests/gpg LC_ALL=C GPG_AGENT_INFO=
top_srcdir=../../.. ${dir}$tst
FAIL: t-edit-sign
...
===
1 of 27 tests failed
Please report to https://bugs.gnupg.org
===
make[6]: *** [Makefile:894: check-TESTS] Error 1
--- End Message ---
--- Begin Message ---
Source: gpgme1.0
Source-Version: 1.16.0-1.1
Done: Norbert Preining
We believe that the bug you reported is fixed in the latest version of
gpgme1.0, 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 992...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Norbert Preining (supplier of updated gpgme1.0 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 15 Sep 2021 14:31:55 +0900
Source: gpgme1.0
Architecture: source
Version: 1.16.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuPG Maintainers
Changed-By: Norbert Preining
Closes: 992922
Changes:
gpgme1.0 (1.16.0-1.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Cherry-pick upstream fixes for test failures on 32bit archs:
- d/patches/upstream-e0494c54-fix-use-after-free-in-test.patch
- d/patches/upstream-72a2487a-expiration-date-as-unsigned.patch
(Closes: #992922)
Checksums-Sha1:
f0093bcd1f53532a2306ff5aff6c62fb2d5966e1 2538 gpgme1.0_1.16.0-1.1.dsc
d7d310dd8b1e458114303c7b46ff3143b5d05446 20444
gpgme1.0_1.16.0-1.1.debian.tar.xz
a7221019159ac517a31bf88cda90437e255cc7c6 13944
gpgme1.0_1.16.0-1.1_source.buildinfo
Checksums-Sha256:
1f043def7acf1e0d1a1efcb1a03a372992f5912d950e493af280b09275d93645 2538
gpgme1.0_1.16.0-1.1.dsc
61a66db3494e6bf80a8d9735490b39da0ce22ce1851c65122d60a3af45d0088f 20444
gpgme1.0_1.16.0-1.1.debian.tar.xz
c493edb56e2518d93623f250cb2e169e9d18afb0821b73075fde27bcb112d358 13944
gpgme1.0_1.16.0-1.1_source.buildinfo
Files:
93ff144e97fc8dd6c4b4daf81c928088 2538 libs optional gpgme1.0_1.16.0-1.1.dsc
f6b4b231b826f605a5652a73fcd281e6 20444 libs optional
gpgme1.0_1.16.0-1.1.debian.tar.xz
36c712e6196927b809986917359a64ba 13944 libs optional
gpgme1.0_1.16.0-1.1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQEzBAEBCgAdFiEE68ws0vrA2voQX53I2A4JsIcUAGYFAmFBhv4ACgkQ2A4JsIcU
AGZ4dAf6A1WAA5+1PmusfZ4Ek36Ehry3sDKvymALNoE4vInYelHpMDA2ru0RF+RJ
MsjUU4qe4iVschzBDwCbgD/qzl/C+TR85kUWJFgygvNSRxcVAt6J2sClartiBmwu
DYkth74f8xKe9zK3wdn4zF+3NSFCL2LK38DvIBV1FEcyh2ZGCUfXLjoC/W14DVrS
CuuPRVFdqv9mitoAB4tgQkZWthDbw3+36yMerQjo6XuWsFzHERvRz6rkmjDXGc0S
Bug#994543: marked as done (Workaround glibc bug BZ#26401 (regression in lchmod and fchmodat when /proc is not mounted))
Your message dated Fri, 17 Sep 2021 23:48:42 + with message-id and subject line Bug#994543: fixed in rsync 3.2.3-7 has caused the Debian Bug report #994543, regarding Workaround glibc bug BZ#26401 (regression in lchmod and fchmodat when /proc is not mounted) 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.) -- 994543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994543 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glibc Version: 2.32-3 Severity: important Tags: upstream Forwarded: https://sourceware.org/bugzilla/show_bug.cgi?id=26401 X-Debbugs-Cc: car...@debian.org Control: affects -1 rsync Control: clone -1 -2 Control: reassing -2 src:rsync 3.2.3-6 Control: retitle -2 rsync: Workaround glibc bug BZ#26401 (regression in lchmod and fchmodat when /proc is not mountet) Control: forwarded -2 https://github.com/WayneD/rsync/issues/109 Hi There is a regression in lchmod and fchmodat when /proc is not mounted, the upstream report about it is at [1] and affects as well e.g. rsync[2]. It relates to #951191. [1] https://sourceware.org/bugzilla/show_bug.cgi?id=26401 [2] https://github.com/WayneD/rsync/issues/109 For rsync the following where applied: https://github.com/WayneD/rsync/commit/85b8dc8abaca96fc3ea7421e09101b6ac41b6718 https://github.com/WayneD/rsync/commit/9dd62525f3b98d692e031f22c02be8f775966503 Regards, Salvatore --- End Message --- --- Begin Message --- Source: rsync Source-Version: 3.2.3-7 Done: Samuel Henrique We believe that the bug you reported is fixed in the latest version of rsync, 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 994...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Henrique (supplier of updated rsync 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, 18 Sep 2021 00:25:13 +0100 Source: rsync Architecture: source Version: 3.2.3-7 Distribution: unstable Urgency: medium Maintainer: Paul Slootman Changed-By: Samuel Henrique Closes: 994543 Changes: rsync (3.2.3-7) unstable; urgency=medium . * Bump Standards-Version to 4.6.0 * d/p/workaround_glibc_lchmod_regression.patch: New patch from upstream (closes: #994543) * debian/rsync.NEWS: Fix typo in last entry Checksums-Sha1: 9e9c36db4c67c9db18d86312598cc5768dd2cd8f 2231 rsync_3.2.3-7.dsc 9ec2337213ead389041f79a12129fc43c0f1ebb2 28460 rsync_3.2.3-7.debian.tar.xz d77f73533df643e00ad68ae2176ee7d9f7a1f6d2 6317 rsync_3.2.3-7_amd64.buildinfo Checksums-Sha256: 3be638224a5dde265e2190ae51380041ec3a32d5938703a5a746fa422c73056f 2231 rsync_3.2.3-7.dsc 1c2b50e9df3ef841fcf86c75dccbedfcadf90ec7d9c6d54d6ee80ef9f38fe5c2 28460 rsync_3.2.3-7.debian.tar.xz 72811c18c6dd953d57a5068f45506517b1178003858f6ddfbfc9083a0c380cc9 6317 rsync_3.2.3-7_amd64.buildinfo Files: 30ddda87cc2cf544814918c97dfea8bf 2231 net optional rsync_3.2.3-7.dsc 3c96a3d46d283bc612ae61fc2d63e478 28460 net optional rsync_3.2.3-7.debian.tar.xz 8cd90a1e82dc7ff05b21f835636b6e96 6317 net optional rsync_3.2.3-7_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEBdtqg34QX0sdAsVfu6n6rcz7RwcFAmFFJJIACgkQu6n6rcz7 RwdrkRAAm//giHR0+4vJFAqU6mNlixabsrkDGnuv0FcqSfK54LzVguwtwH1Q5nJv p9rZU8kVNkesgt0i2Y/dCDqEMZpzzVoE1uXOKnzDJWuafVg65AeKZsTvtSe85INT ttcPLJWGGKYx9CtkbqRD8s6tPHlAyZv/8UUDgPADqCNAEpbc/O7nQbUehQzMae1e Fb62yAiuTOyAd0BGAyg5S4Srvkr61AypfkHNbftSF1HyUyrjI3SY6gaQUbeRnMoH m2LsWSCStK5IhFqHIvzUQL/8P2cAp4wnmhFeWa/JXNwhy8FMabRSk6cMmkuhPi1o 2em7TJMJ8W2TffiL8DYrXWHqa4rbCfEErCprA7GGf//t+UvVgeXRjRIWLUsOMu/D jg5GWqlN+LPK2zcT9IS6wf+WveloyomXCOhMQ3YdYACMshfSYPvk5SZ0t0iSleGH h5X6L6lWAttn3vjzNBonv3ORRSS6AwhexMvYipyaUXPuCxDR6mW8NJXhnCOvkyOr g8BtfEOg/bdwYzjgqHi+GK9L963h4aUANiyTIpS/ABJONnqhqBLbNb5+Jkm0vKjd owNMO/eChsSN1ZLotJGqzNT3qcS7vqSVqgaFsq6ah9Trsj++WNY/nKsCAjSutR3u K4PkOUZbDfn3igfrnEOUzJN7NYpYMAKsirtsuuLgl+GPL6MPZfw= =7OLr -END PGP SIGNATURE End Message ---
Bug#970680: marked as done (vim/indent|syntax/cmake.vim)
Your message dated Sat, 18 Sep 2021 01:01:02 +0200 with message-id <20210917230102.yc3us7dnmvmk6...@mail.gaussglocke.de> and subject line Re: vim/indent|syntax/cmake.vim has caused the Debian Bug report #970680, regarding vim/indent|syntax/cmake.vim 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.) -- 970680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cmake Version: 3.13.4-1 It would be nice when I install cmake-data that the greatest & latest of cmake.vim override anything from my vim81 install. Typically: /usr/share/vim/vim81/syntax/cmake.vim -> /usr/share/cmake-3.16/editors/vim/syntax/cmake.vim /usr/share/vim/vim81/indent/cmake.vim -> /usr/share/cmake-3.16/editors/vim/indent/cmake.vim It seems that something smart is being done for emacs $ grep editor cmake-data.install usr/share/cmake-*/editors/emacs/cmake-mode.el usr/share/emacs/site-lisp Thanks --- End Message --- --- Begin Message --- Control: fixed 3.21.2-1 On Mon, 21 Sep 2020 13:43:42 +0200 Mathieu Malaterre wrote: Source: cmake Version: 3.13.4-1 It would be nice when I install cmake-data that the greatest & latest of cmake.vim override anything from my vim81 install. cmake-data installs those files to /usr/share/vim/vimfiles, where they take precedence over the vim default ones. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature --- End Message ---
Bug#994389: marked as done (openimageio: building against OpenVDB 8 silently drops OpenVDB aupport)
Your message dated Fri, 17 Sep 2021 23:04:45 + with message-id and subject line Bug#994389: fixed in openimageio 2.2.18.0+dfsg-1 has caused the Debian Bug report #994389, regarding openimageio: building against OpenVDB 8 silently drops OpenVDB aupport 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.) -- 994389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994389 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openimageio Version: 2.2.17.0+dfsg-2 Severity: important Tags: patch fixed-upstream Forwarded: https://github.com/OpenImageIO/oiio/commit/867c25cbd15c4c56fa809162d71286b6aaf8896b https://buildd.debian.org/status/fetch.php?pkg=openimageio&arch=amd64&ver=2.2.17.0%2Bdfsg-2%2Bb1&stamp=1631691993&raw=0 ... -- [32mFound OpenVDB 8.1.0 [m CMake Warning at src/cmake/externalpackages.cmake:219 (message): [33mOpenVDB 8.0+ requires C++14 or higher (was 11). To build against this OpenVDB 8.1.0, you need to set build option CMAKE_CXX_STANDARD=14 (or higher). The minimum requirements for that are gcc >= 5.1, clang >= 3.5, Apple clang >= 7, icc >= 7, MSVS >= 2017. If you must use C++11, you need to build against OpenVDB 7 or earlier. [m Call Stack (most recent call first): CMakeLists.txt:121 (include) -- [31mNot using OpenVDB -- OpenVDB 8.1.0 requires C++14 or later. [m ... This can be fixed with the oneline change to src/cmake/compiler.cmake in the commit linked above. --- End Message --- --- Begin Message --- Source: openimageio Source-Version: 2.2.18.0+dfsg-1 Done: Matteo F. Vescovi We believe that the bug you reported is fixed in the latest version of openimageio, 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 994...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matteo F. Vescovi (supplier of updated openimageio 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, 18 Sep 2021 00:26:48 +0200 Source: openimageio Architecture: source Version: 2.2.18.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian PhotoTools Maintainers Changed-By: Matteo F. Vescovi Closes: 994389 Changes: openimageio (2.2.18.0+dfsg-1) unstable; urgency=medium . * New upstream release * d/rules: minimal C++ version bumped to 14 (Closes: #994389) * d/control: S-V bump 4.5.0 -> 4.6.0 (no changes needed) Checksums-Sha1: 0eb23e8b8c46efc108650b0f30430e74bbfedbf3 3005 openimageio_2.2.18.0+dfsg-1.dsc 1fd8e362666cf23b34e0d47c9ce1d2c7c68148a6 26401960 openimageio_2.2.18.0+dfsg.orig.tar.xz ff45a5ba9d57d5413bba741777656ce0f0ae6889 17724 openimageio_2.2.18.0+dfsg-1.debian.tar.xz 6cf456244365062356bd0cc1dac29236a91dd7ba 6883 openimageio_2.2.18.0+dfsg-1_source.buildinfo Checksums-Sha256: 33e33ca9a46e0dc6fdf02a1536ca76afe5947402a1529c7ec0c1a96b2fd53cf6 3005 openimageio_2.2.18.0+dfsg-1.dsc 4e0f0f88a6024197f74452784e5fde8da3c9af5c544c7a7fb600e0272815f73d 26401960 openimageio_2.2.18.0+dfsg.orig.tar.xz 6ac3e979ed26f1fb488697b7b6f7a3bea90c6233e5cabe294ed9f46c605697c1 17724 openimageio_2.2.18.0+dfsg-1.debian.tar.xz 680df5155ced5af248f8fa761ca2aaa0be1d399523780bf33987a4deb8e0043c 6883 openimageio_2.2.18.0+dfsg-1_source.buildinfo Files: 5b5e30e78b693118c0c069983d3b33aa 3005 libs optional openimageio_2.2.18.0+dfsg-1.dsc 0ee5aa38d394b07eddb5907ec8ab4ac5 26401960 libs optional openimageio_2.2.18.0+dfsg.orig.tar.xz 7e30dc2a1a132be4488f362ed3dbc65f 17724 libs optional openimageio_2.2.18.0+dfsg-1.debian.tar.xz 38c91cee447073fac2f46d556fcaac65 6883 libs optional openimageio_2.2.18.0+dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- Comment: Debian powered! iQKTBAEBCgB9FiEE890J+NqH0d9QRsmbBhL0lE7NzVoFAmFFFl1fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEYz REQwOUY4REE4N0QxREY1MDQ2Qzk5QjA2MTJGNDk0NEVDRENENUEACgkQBhL0lE7N zVo1Aw/+Jin1jmA3ucBXHdNYKv3rdSWSDNl3FI8MVZhwMG5uUbdzK+zm0CY0suTG n/pLzzEBwJhSgOk6DuBvECLAeYtnnKJKsQ4PhYdUuO1Fp6Ln5nYIg2/YmsOzAe5X FvZ9zrGg6CuaSLHx2nbhIT4BwN7yUQtTOjVJg/0yRBbW2p+mAYBvDG7eJmBKbn+1 9ws0+O6JUW9mhjobEvXiF0MEMAKL6ZHVXPLR04fU7Ux7v+FIRunAsYDZeMHUc0Cv ExxIg0dSMNEdlHOKsgCKbmhKKqgZ/buQcoB/FO+6OCM/yxC3wP3IlD2Y
Bug#948505: marked as done (devhelp: GTKMM 3.0 doc not working on devhelp)
Your message dated Fri, 17 Sep 2021 18:55:02 -0400 with message-id and subject line Re: devhelp: GTKMM 3.0 doc not working on devhelp has caused the Debian Bug report #948505, regarding devhelp: GTKMM 3.0 doc not working on devhelp 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.) -- 948505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: devhelp Version: 3.34.0-1 Severity: normal Dear Maintainer, I installed libgtkmm-3.0-doc on my system for reference purposes. Enabled "Group by language" on devhelp preferences so I could easily jump to C++ APIs only. Clicking on one of the manual page from C++ category produces only blank page. Both glibmm and gtkmm reference manual do not work on devhelp program at all. Expected outcome is the docs displayed instead of empty page. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages devhelp depends on: ii libamtk-5-0 5.0.0-3 ii libc6 2.29-3 ii libdevhelp-3-63.34.0-1 ii libglib2.0-0 2.62.4-1 ii libgtk-3-03.24.13-1 ii libpango-1.0-01.42.4-7 ii libwebkit2gtk-4.0-37 2.26.2-1 ii python3 3.7.5-1 Versions of packages devhelp recommends: ii libglib2.0-doc 2.62.4-1 ii libgtk-3-doc 3.24.13-1 ii libpango1.0-doc 1.42.4-7 devhelp suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- X-CrossAssassin-Score: 29788--- End Message ---
Bug#722279: marked as done (devhelp: Error accessing gtkmm-3.0 reference manual)
Your message dated Fri, 17 Sep 2021 18:55:02 -0400 with message-id and subject line Re: devhelp: GTKMM 3.0 doc not working on devhelp has caused the Debian Bug report #948505, regarding devhelp: Error accessing gtkmm-3.0 reference manual 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.) -- 948505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: devhelp Version: 3.8.2-2 Severity: important Dear Maintainer, When clicking on item gtkmm Reference Manual Modules | Namespaces | Classes an error dialog shows with the content "Fehler beim Öffnen des angeforderten Verweises" but not the expected Documentation. Georg -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.10-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages devhelp depends on: ii libatk1.0-0 2.8.0-2 ii libc6 2.17-92+b1 ii libcairo-gobject2 1.12.14-5 ii libcairo2 1.12.14-5 ii libdevhelp-3-2 3.8.2-2 ii libgdk-pixbuf2.0-0 2.28.2-1 ii libglib2.0-02.36.4-1 ii libgtk-3-0 3.8.4-1 ii libjavascriptcoregtk-3.0-0 2.0.4-4 ii libpango-1.0-0 1.32.5-5+b1 ii libpangocairo-1.0-0 1.32.5-5+b1 ii libsoup2.4-12.42.2-6 ii libwebkitgtk-3.0-0 2.0.4-4 Versions of packages devhelp recommends: ii libglib2.0-doc 2.36.4-1 ii libgtk-3-doc 3.8.4-1 ii libpango1.0-doc 1.32.5-5 devhelp suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- X-CrossAssassin-Score: 29788--- End Message ---
Bug#935852: marked as done (linux-image-5.2.0-2-amd64: Heavy static noise on headphone jack snd_hda_intel)
Your message dated Fri, 17 Sep 2021 14:42:53 -0700 (PDT) with message-id <61450bdd.1c69fb81.55c71.5...@mx.google.com> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #935852, regarding linux-image-5.2.0-2-amd64: Heavy static noise on headphone jack snd_hda_intel 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.) -- 935852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 5.2.9-2 Severity: normal I am experiencing heavy static noise through the headphone jack, while the issue is completely absent when booting with linux-image-4.19.0-5-amd64. When the media stops the static noise persists for a few seconds, I guess until the driver goes into powersaving mode or something. It is worth noting that there is no static noise through the speakers whatsoever. -- Package-specific info: ** Version: Linux version 5.2.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-21)) #1 SMP Debian 5.2.9-2 (2019-08-21) ** Command line: BOOT_IMAGE=/vmlinuz-5.2.0-2-amd64 root=/dev/mapper/cryptovg-root ro rootflags=subvol=master loglevel=3 net.ifnames=0 biosdevname=0 ** Tainted: OE (12288) * Out-of-tree module has been loaded. * Unsigned module has been loaded. ** Kernel log: [ 32.536765] lxcbr0: port 1(veth1000_J11B6) entered forwarding state [ 32.589116] audit: type=1400 audit(1566847450.760:43): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="/usr/bin/lxc-start" name="/proc/sys/kernel/random/boot_id" pid=2284 comm="lxc-start" srcname="/dev/.lxc-boot-id" flags="rw, bind" [ 32.590874] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist. [ 43.843543] lxcbr0: port 1(veth1000_J11B6) entered disabled state [ 43.844668] device veth1000_J11B6 left promiscuous mode [ 43.844670] lxcbr0: port 1(veth1000_J11B6) entered disabled state [ 66.479348] lxcbr0: port 1(veth1000_R5T1V) entered blocking state [ 66.479352] lxcbr0: port 1(veth1000_R5T1V) entered disabled state [ 66.479677] device veth1000_R5T1V entered promiscuous mode [ 66.500279] eth0: renamed from veth1000_R5T1Vp [ 66.536554] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 66.536640] IPv6: ADDRCONF(NETDEV_CHANGE): veth1000_R5T1V: link becomes ready [ 66.536709] lxcbr0: port 1(veth1000_R5T1V) entered blocking state [ 66.536712] lxcbr0: port 1(veth1000_R5T1V) entered forwarding state [ 66.536819] IPv6: ADDRCONF(NETDEV_CHANGE): lxcbr0: link becomes ready [ 66.586965] audit: type=1400 audit(1566847485.253:44): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="/usr/bin/lxc-start" name="/proc/sys/kernel/random/boot_id" pid=3170 comm="lxc-start" srcname="/dev/.lxc-boot-id" flags="rw, bind" [ 66.587804] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist. [ 69.831073] audit: type=1400 audit(1566847488.497:45): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-cgns" name="/" pid=3399 comm="(install)" flags="rw, rslave" [ 69.841293] audit: type=1400 audit(1566847488.509:46): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-cgns" name="/" pid=3406 comm="(tor)" flags="rw, rslave" [ 69.901493] audit: type=1400 audit(1566847488.569:47): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-cgns" name="/" pid=3411 comm="(tor)" flags="rw, rslave" [ 73.695579] lxcbr0: port 1(veth1000_R5T1V) entered disabled state [ 73.800087] lxcbr0: port 1(veth1000_R5T1V) entered disabled state [ 73.802697] device veth1000_R5T1V left promiscuous mode [ 73.802700] lxcbr0: port 1(veth1000_R5T1V) entered disabled state [ 124.718063] PM: suspend entry (deep) [ 127.498003] Filesystems sync: 2.779 seconds [ 127.499477] (NULL device *): firmware: direct-loading firmware iwlwifi-8000C-36.ucode [ 127.500746] (NULL device *): firmware: direct-loading firmware i915/skl_dmc_ver1_27.bin [ 127.500838] Freezing user space processes ... (elapsed 0.023 seconds) done. [ 127.524843] OOM killer disabled. [ 127.524844] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 127.526390] printk: Suspending console(s) (use no_console_suspend to debug) [ 127.629485] wlan0: deauthenticating from 78:81:02:54:1d:c5 by local choice (Reason: 3=DEAUTH_LEAVING) [ 127.944709] psmouse serio1: Faile
Bug#984733: marked as done (ITS: libuser)
Your message dated Fri, 17 Sep 2021 19:34:20 + with message-id and subject line Bug#984733: fixed in libuser 1:0.62~dfsg-1 has caused the Debian Bug report #984733, regarding ITS: libuser 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.) -- 984733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libuser Version: 1:0.62~dfsg-0.4 Severity: important X-Debbugs-CC: tzaf...@debian.org g...@debian.org Dear package libuser maintainers in Debian, After looking into the package you maintain (libuser, https://tracker.debian.org/pkg/libuser), I found that this package received no maintainer updates in the past 6 years. As a result, I am filing an ITS (Intent to Salvage) request against your package according to section 5.12 in Debian's Developers' Reference [1]. My current plan is to package the latest upstream release (0.63), clean up packaging and orphan this package to allow possible external contribution. Please let me know whether you are still willing to maintain this package. According to the criteria listed at [2], I will upload a Non- maintainer Upload (NMU) of this package onto experimental with DELAYED/7 after 21 days (Mar 28, 2021) to continue with the package salvaging. If you find it necessary to pause the ITS process, please let me know immediately by replying this bug report. [1] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging [2] https://wiki.debian.org/PackageSalvaging -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: libuser Source-Version: 1:0.62~dfsg-1 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of libuser, 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 984...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated libuser 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: Fri, 17 Sep 2021 15:06:44 -0400 Source: libuser Architecture: source Version: 1:0.62~dfsg-1 Distribution: unstable Urgency: medium Maintainer: Boyuan Yang Changed-By: Boyuan Yang Closes: 984733 Changes: libuser (1:0.62~dfsg-1) unstable; urgency=medium . * Rebuild after Debian 11 release. * Take over package maintenance. (Closes: #984733) * Bump Standards-Version to 4.6.0. Checksums-Sha1: e32d343e40dc3b86a44a613b8de6370c6e242d01 2035 libuser_0.62~dfsg-1.dsc 6ce429ed085d0798510ae539b419ed668d674e31 743616 libuser_0.62~dfsg.orig.tar.xz 2af17af32a9e6ff506a61e908d736f0fcc0e0349 7588 libuser_0.62~dfsg-1.debian.tar.xz 30845a1cdecd4536c46447bfa521fdfb43d29bef 8874 libuser_0.62~dfsg-1_amd64.buildinfo Checksums-Sha256: 24bc57ebb747a6d48509293f8d07a5a740cbda342fc30a9d6e18a0b86444b7a1 2035 libuser_0.62~dfsg-1.dsc 30c40e6dceffa3c67065cb86f62262f297e3398528faef7e770c46e093cfa15e 743616 libuser_0.62~dfsg.orig.tar.xz 89a84f34dce2a692d915af5d4d1df1cb1d26f46a366ec3b85b51d817f74bdfd6 7588 libuser_0.62~dfsg-1.debian.tar.xz deef7e37367fe602bd411d94d3f0317c0ddcbb4483cb670e8723f55197bda936 8874 libuser_0.62~dfsg-1_amd64.buildinfo Files: 755dd896fc03230c67c6458ffe5f5395 2035 admin optional libuser_0.62~dfsg-1.dsc 08daadb21f017c0b1dc8a2f1a81abca8 743616 admin optional libuser_0.62~dfsg.orig.tar.xz 532f5ac6af5867a3a8ce816cae44e630 7588 admin optional libuser_0.62~dfsg-1.debian.tar.xz 6b60ed5e56d93b31e43e733ccdd28d92 8874 admin optional libuser_0.62~dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmFE59UACgkQwpPntGGC Ws4Kkw//TMM61dyh/81vIQ9T70QPEimAaI5EGOGnDJLDzdACexxyEDf+Iopw7/mN HiONBvOMPInnOOA+zsWsMIagNgWfT0fYyaAGUEyMcJKzGTcG6GYzTNgyS56qiYLM 2TeL07DGEZ3gv/ebGSdXzQU8PAUsUfXtHUTGH09nQ+ZxONq59qnLPpWkOlNevKOd Q9zyKoeUZgVvmRYrmhHbq5MAOwYF5d9A9qI/hdYfM02Q91WPDYCi6qMXPB3mxlKp WVXoyLFIExVutQyoGJW/ZGwP/eFqu1SclQTjy17FPN3iCAuzXvtKCMiOQFM6x6Dj 15sAZBAQRBrVyEt0QKe354c2Y1yGUMRisaIQJcVANWif2mjyUuCZ2UPgGv+KIw9j AYDGgFNqOviyxNpEVILGqDtERZJ9lhpJNbfUtNtByr28f1fhf/13OBtxFpw10hmk Paoq4GUH7znEeHjB4o8WhXXPK
Bug#918049: marked as done (psi: main window is empty when restored after being hidden)
Your message dated Fri, 17 Sep 2021 21:57:37 +0300 with message-id <219011631905...@mail.yandex.ru> and subject line Re: psi: main window is empty when restored after being hidden has caused the Debian Bug report #918049, regarding psi: main window is empty when restored after being hidden 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.) -- 918049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: psi Version: 1.3-5 Severity: important Tags: patch Dear Maintainer, The debian package suffers from this upstream bug: "With Qt 5.11, when tray is enabled and application is configured not to quit on contacts list closing, if contacts list window (main window) is closed via 'close' button on window's header, and after that shown again using tray icon, reappearing window is empty." -- https://github.com/psi-im/psi/pull/389 Imho this makes psi very hard to use beckuse you have to remember not to hide it. Afaik the problem is fixed in the newest upstream version (1.4), alternatively there is a patch in above pull request. Thanks -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (490, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages psi depends on: ii libc6 2.28-2 ii libenchant1c2a1.6.0-11.1+b1 ii libgcc1 1:8.2.0-13 ii libidn11 1.33-2.2 ii libminizip1 1.1-8+b1 ii libqca-qt5-2 2.1.3-2 ii libqca-qt5-2-plugins 2.1.3-2 ii libqt5concurrent5 5.11.2+dfsg-7 ii libqt5core5a 5.11.2+dfsg-7 ii libqt5dbus5 5.11.2+dfsg-7 ii libqt5gui55.11.2+dfsg-7 ii libqt5network55.11.2+dfsg-7 ii libqt5widgets55.11.2+dfsg-7 ii libqt5x11extras5 5.11.2-2 ii libqt5xml55.11.2+dfsg-7 ii libstdc++68.2.0-13 ii libx11-6 2:1.6.7-1 ii libxcb1 1.13.1-2 ii libxss1 1:1.2.3-1 ii zlib1g1:1.2.11.dfsg-1 Versions of packages psi recommends: ii sox 14.4.2-3 Versions of packages psi suggests: pn psi-translations ii xdg-utils 1.1.3-1 -- no debconf information --- End Message --- --- Begin Message --- Bug is fixed.--- End Message ---
Bug#994524: marked as done (pycurl accesses the internet during the build)
Your message dated Fri, 17 Sep 2021 18:33:34 +
with message-id
and subject line Bug#994524: fixed in pycurl 7.44.1-3
has caused the Debian Bug report #994524,
regarding pycurl accesses the internet during the build
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.)
--
994524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994524
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pycurl
Version: 7.44.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=pycurl&arch=amd64&ver=7.44.1-2&stamp=1631841618&raw=0
https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/pycurl.html
...
=== FAILURES ===
SshKeyCbTest.test_keyfunction _
self =
@util.min_libcurl(7, 19, 6)
# curl compiled with libssh doesn't support
# CURLOPT_SSH_KNOWNHOSTS and CURLOPT_SSH_KEYFUNCTION
@util.guard_unknown_libcurl_option
def test_keyfunction(self):
# with keyfunction returning ok
def keyfunction(known_key, found_key, match):
return pycurl.KHSTAT_FINE
self.curl.setopt(pycurl.SSH_KNOWNHOSTS, '.known_hosts')
self.curl.setopt(pycurl.SSH_KEYFUNCTION, keyfunction)
try:
> self.curl.perform()
E pycurl.error: (6, 'Could not resolve host: web.sourceforge.net')
tests/ssh_key_cb_test.py:40: error
During handling of the above exception, another exception occurred:
self =
@util.min_libcurl(7, 19, 6)
# curl compiled with libssh doesn't support
# CURLOPT_SSH_KNOWNHOSTS and CURLOPT_SSH_KEYFUNCTION
@util.guard_unknown_libcurl_option
def test_keyfunction(self):
# with keyfunction returning ok
def keyfunction(known_key, found_key, match):
return pycurl.KHSTAT_FINE
self.curl.setopt(pycurl.SSH_KNOWNHOSTS, '.known_hosts')
self.curl.setopt(pycurl.SSH_KEYFUNCTION, keyfunction)
try:
self.curl.perform()
self.fail('should have raised')
except pycurl.error as e:
> self.assertEqual(pycurl.E_LOGIN_DENIED, e.args[0])
E AssertionError: 67 != 6
tests/ssh_key_cb_test.py:43: AssertionError
- Captured stderr call -
* Could not resolve host: web.sourceforge.net
* Closing connection 0
__ SshKeyCbTest.test_keyfunction_bogus_return __
self =
@util.min_libcurl(7, 19, 6)
@util.guard_unknown_libcurl_option
def test_keyfunction_bogus_return(self):
def keyfunction(known_key, found_key, match):
return 'bogus'
self.curl.setopt(pycurl.SSH_KNOWNHOSTS, '.known_hosts')
self.curl.setopt(pycurl.SSH_KEYFUNCTION, keyfunction)
try:
> self.curl.perform()
E pycurl.error: (6, 'Could not resolve host: web.sourceforge.net')
tests/ssh_key_cb_test.py:69: error
During handling of the above exception, another exception occurred:
self =
@util.min_libcurl(7, 19, 6)
@util.guard_unknown_libcurl_option
def test_keyfunction_bogus_return(self):
def keyfunction(known_key, found_key, match):
return 'bogus'
self.curl.setopt(pycurl.SSH_KNOWNHOSTS, '.known_hosts')
self.curl.setopt(pycurl.SSH_KEYFUNCTION, keyfunction)
try:
self.curl.perform()
self.fail('should have raised')
except pycurl.error as e:
> self.assertEqual(pycurl.E_PEER_FAILED_VERIFICATION, e.args[0])
E AssertionError: 60 != 6
tests/ssh_key_cb_test.py:72: AssertionError
- Captured stderr call -
* Could not resolve host: web.sourceforge.net
* Closing connection 0
...
--- End Message ---
--- Begin Message ---
Source: pycurl
Source-Version: 7.44.1-3
Done: Scott Talbert
We believe that the bug you reported is fixed in the latest version of
pycurl, 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 994...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Scott Talbert (supplier of updated pycurl package)
(This message was generated automatically at their request; if you
believe that there is a problem with it
Bug#986208: marked as done (wireless-regdb: Please update wireless-regdb to 2020-11-20)
Your message dated Fri, 17 Sep 2021 17:33:50 + with message-id and subject line Bug#986208: fixed in wireless-regdb 2021.08.28-1 has caused the Debian Bug report #986208, regarding wireless-regdb: Please update wireless-regdb to 2020-11-20 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.) -- 986208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wireless-regdb Version: 2020.04.29-2 Severity: normal X-Debbugs-Cc: amribrahim1...@hotmail.com Dear Maintainer, Please update wireless-regdb to 2020-11-20. It has regulatory rules updates to countries that I care about: US, UK and Egypt. It would be great to have it in Bullseye for the long-living Debian 11. -- System Information: Debian Release: bullseye/sid APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-5-amd64 (SMP w/8 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled wireless-regdb depends on no packages. wireless-regdb recommends no packages. Versions of packages wireless-regdb suggests: pn crda -- no debconf information --- End Message --- --- Begin Message --- Source: wireless-regdb Source-Version: 2021.08.28-1 Done: Romain Perier We believe that the bug you reported is fixed in the latest version of wireless-regdb, 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 986...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Romain Perier (supplier of updated wireless-regdb 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: Fri, 17 Sep 2021 18:30:37 +0200 Source: wireless-regdb Architecture: source Version: 2021.08.28-1 Distribution: unstable Urgency: medium Maintainer: Debian kernel team Changed-By: Romain Perier Closes: 986208 Changes: wireless-regdb (2021.08.28-1) unstable; urgency=medium . * New upstream version (Closes: #986208): - Update regulatory rules for Egypt (EG), Croatia (HR), Pakistan (PK) on 5GHz, Great Britain (GB), Kazakhstan (KZ), Ukraine (UA), Cuba (CU) on 5Ghz, Germany (DE) on 6GHz, Norway (NO) on 6 and 60 GHz, Ecuador (EC) - US: restore channel 12 & 13 limitation - US: remove PTMP-ONLY from 5850-5895 MHz - US: reduce bandwidth for 5730-5850 and 5850-5895 MHz - ES: Update CNAF regulation url Checksums-Sha1: 0beec3a523c6f44eeec4fb4f4ba6eb1f7cec5fd3 2196 wireless-regdb_2021.08.28-1.dsc 986a3de9f3c7dc970317cdfce911fa343795d0aa 25392 wireless-regdb_2021.08.28.orig.tar.xz 6baa1e30e75b2c2e70ed23d578509a8ae1e4becb 17984 wireless-regdb_2021.08.28-1.debian.tar.xz acd01b53acf23806e37ad22c64dac472f21fa18f 6486 wireless-regdb_2021.08.28-1_amd64.buildinfo Checksums-Sha256: 69ebcba2284d116724a9d93efebb69fc93d7e45dd2daa304983b389edc945bb9 2196 wireless-regdb_2021.08.28-1.dsc 4a4c47c9c314cd845a73768670f5dc4866cd8d74b98614391015406e531c1cf0 25392 wireless-regdb_2021.08.28.orig.tar.xz 95c32f01823c1ae32494fcca2a17f6410dd021fe789c306eab4f51f42e4a9ebf 17984 wireless-regdb_2021.08.28-1.debian.tar.xz f704059dcff780cb772248d044c239d24be0052ab8738d5e93a1ecc9f2aaae22 6486 wireless-regdb_2021.08.28-1_amd64.buildinfo Files: e2c4e7737cb0ad78190a9b0bb465dc74 2196 net optional wireless-regdb_2021.08.28-1.dsc 57bc92309d2e963e1441663f066e401b 25392 net optional wireless-regdb_2021.08.28.orig.tar.xz 6694f47533428ab93b4ea2d5b0b99278 17984 net optional wireless-regdb_2021.08.28-1.debian.tar.xz 689e575ce469787011e3eb89808fa3ad 6486 net optional wireless-regdb_2021.08.28-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEbpWHxyX/nlEWTnf8WhIh6CKeimAFAmFEyfUACgkQWhIh6CKe imBz1hAAgSuBRie8UNBe4C8vlWj9D127xsJX7LOTfUa0iPlX7OM8iGXH2vpXjwBT wXm8n9aC7nPpf0FRgFqfJgiDecU+iX5zjQfHlx9xKwr8zi9ULUxor8BlpQI+xt77 iYfidPGK1M23UF9sDgPOCCvXEOjmtQ3RL86aaTEEq90eZgwxXA6l1IdkHLpChdX7 bCxjoRRiT+kTqiAY4P27skc87hNablWNVcQchjL1v+sdg5IXc2arLxAS6gUI/ZiT ep1ex16RaXtIfVire8hHz9WDuyyrgFaftvCW+qs9mvS/CCd
Bug#992207: marked as done (Freeradius postgresql mod broken in Bullseye)
Your message dated Fri, 17 Sep 2021 17:32:08 +
with message-id
and subject line Bug#992207: fixed in freeradius 3.0.21+dfsg-2.2+deb11u1
has caused the Debian Bug report #992207,
regarding Freeradius postgresql mod broken in 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.)
--
992207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: freeradius
Version: 3.0.21+dfsg-2.2 amd64
I just built a new Bullseye VM to replace my Buster freeradius VM. Upon trying
to configure it for a postgres backend, 'freeradius -X' fails out with the
following:
...
including configuration file /etc/freeradius/3.0/mods-enabled/mschap
including configuration file /etc/freeradius/3.0/mods-enabled/sql
including configuration file
/etc/freeradius/3.0/mods-config/sql/main/postgresql/queries.conf
/etc/freeradius/3.0/mods-config/sql/main/postgresql/queries.conf[505]: Parse
error: Unterminated string
Errors reading or parsing /etc/freeradius/3.0/radiusd.conf
Looking at line 505 of
/etc/freeradius/3.0/mods-config/sql/main/postgresql/queries.conf, it does seem
to be missing a line-extending terminator '\' that is present on surrounding
lines (the context is that this is in the middle of a ~15-line SQL query):
...
504:AcctUpdateTime =
${event_timestamp}, \
505:AcctSessionTime =
COALESCE(%{%{Acct-Session-Time}:-NULL},
506:
(${event_timestamp_epoch} - EXTRACT(EPOCH FROM(AcctStartTime, \
...
Adding the '\' in at the end of the line seems to fix it.
This is a fully stable Bullseye installation, built from the official ISOs
released yesterday.
--- End Message ---
--- Begin Message ---
Source: freeradius
Source-Version: 3.0.21+dfsg-2.2+deb11u1
Done: Bernhard Schmidt
We believe that the bug you reported is fixed in the latest version of
freeradius, 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 992...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bernhard Schmidt (supplier of updated freeradius 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: Fri, 03 Sep 2021 16:47:35 +0200
Source: freeradius
Architecture: source
Version: 3.0.21+dfsg-2.2+deb11u1
Distribution: bullseye
Urgency: medium
Maintainer: Debian FreeRADIUS Packaging Team
Changed-By: Bernhard Schmidt
Closes: 992036 992207
Changes:
freeradius (3.0.21+dfsg-2.2+deb11u1) bullseye; urgency=medium
.
* Cherry-Pick upstream fix for a crash bug (Closes: #992036)
* Cherry-pick upstream fix to add missing continuation in postgresql
sample config (Closes: #992207)
* d/gbp.conf for the debian/bullseye branch
Checksums-Sha1:
ca012e4eb587aed91f7df45cf055dfc4d8bc4a36 3675
freeradius_3.0.21+dfsg-2.2+deb11u1.dsc
da62c18c0e5e4f321eaf1941621c0845fadc22e3 68984
freeradius_3.0.21+dfsg-2.2+deb11u1.debian.tar.xz
62adb9640db1fb58ec1d4fd4b9bbba354ed397a7 20118
freeradius_3.0.21+dfsg-2.2+deb11u1_amd64.buildinfo
Checksums-Sha256:
2442c83c75536f9e62cd5074b32afc195fe31858733bf45ad4472bbfb62ee6ca 3675
freeradius_3.0.21+dfsg-2.2+deb11u1.dsc
83fa444f0145fd4d5b77b592608a0960fd9232540402e137931c6e996622f3c0 68984
freeradius_3.0.21+dfsg-2.2+deb11u1.debian.tar.xz
c6e51578571c466dee1aa7e39a4f89efad27799f77a47f007deb38f3ef9a057a 20118
freeradius_3.0.21+dfsg-2.2+deb11u1_amd64.buildinfo
Files:
f08cc78974e8132d597e866dd2b9f036 3675 net optional
freeradius_3.0.21+dfsg-2.2+deb11u1.dsc
a1dd45baf29d5e17844310f0efec2467 68984 net optional
freeradius_3.0.21+dfsg-2.2+deb11u1.debian.tar.xz
268f565310626ddd8fc2e5f0009bc014 20118 net optional
freeradius_3.0.21+dfsg-2.2+deb11u1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCgAvFiEE1uAexRal3873GVbTd1B55bhQvJMFAmFDE1YRHGJlcm5pQGRl
Ymlhbi5vcmcACgkQd1B55bhQvJOTFg/+N9R/WBmVBeWx5yLfersxl0M3ST5kgq6X
76FrMddBqQHKibiYXaU2wl9sONU8ncFP9C7olrl6lG7zE5A+XEECeP2zmwCZJ9mC
BCq1OXfTe02VJ53a8Jc87VYxY5sSH3Ek2fCvPrFEXsg256sHPBVlGSdS/r0V220L
f+KAa+VmuLY2SK2DsdXgMaMZcYDMCzJtaE6lXsv7r7lDLtZfdVKRL2/eUv86Yk1F
obCG5YxfUUF4Kx0tnVdeqj
Bug#992036: marked as done (freeradius 3.0.x crashes with "attempting double-free")
Your message dated Fri, 17 Sep 2021 17:32:08 + with message-id and subject line Bug#992036: fixed in freeradius 3.0.21+dfsg-2.2+deb11u1 has caused the Debian Bug report #992036, regarding freeradius 3.0.x crashes with "attempting double-free" 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.) -- 992036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992036 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:freeradius Version: 3.0.17+dfsg-1 Severity: important Tags: patch At $dayjob we tried migrating our central radius proxy from FreeRADIUS 2.x to FreeRADIUS 3.x and have experienced several crashes under high load. A colleague worked closely together with upstream in https://github.com/FreeRADIUS/freeradius-server/issues/3188 and it looks like there is a two-line patch (already committed) that is fixing these crashes. This bug is open for tracking, we are going to test whether 3.0.21+patch works as well. In this case it might be included in a future stable update. --- End Message --- --- Begin Message --- Source: freeradius Source-Version: 3.0.21+dfsg-2.2+deb11u1 Done: Bernhard Schmidt We believe that the bug you reported is fixed in the latest version of freeradius, 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 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bernhard Schmidt (supplier of updated freeradius 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: Fri, 03 Sep 2021 16:47:35 +0200 Source: freeradius Architecture: source Version: 3.0.21+dfsg-2.2+deb11u1 Distribution: bullseye Urgency: medium Maintainer: Debian FreeRADIUS Packaging Team Changed-By: Bernhard Schmidt Closes: 992036 992207 Changes: freeradius (3.0.21+dfsg-2.2+deb11u1) bullseye; urgency=medium . * Cherry-Pick upstream fix for a crash bug (Closes: #992036) * Cherry-pick upstream fix to add missing continuation in postgresql sample config (Closes: #992207) * d/gbp.conf for the debian/bullseye branch Checksums-Sha1: ca012e4eb587aed91f7df45cf055dfc4d8bc4a36 3675 freeradius_3.0.21+dfsg-2.2+deb11u1.dsc da62c18c0e5e4f321eaf1941621c0845fadc22e3 68984 freeradius_3.0.21+dfsg-2.2+deb11u1.debian.tar.xz 62adb9640db1fb58ec1d4fd4b9bbba354ed397a7 20118 freeradius_3.0.21+dfsg-2.2+deb11u1_amd64.buildinfo Checksums-Sha256: 2442c83c75536f9e62cd5074b32afc195fe31858733bf45ad4472bbfb62ee6ca 3675 freeradius_3.0.21+dfsg-2.2+deb11u1.dsc 83fa444f0145fd4d5b77b592608a0960fd9232540402e137931c6e996622f3c0 68984 freeradius_3.0.21+dfsg-2.2+deb11u1.debian.tar.xz c6e51578571c466dee1aa7e39a4f89efad27799f77a47f007deb38f3ef9a057a 20118 freeradius_3.0.21+dfsg-2.2+deb11u1_amd64.buildinfo Files: f08cc78974e8132d597e866dd2b9f036 3675 net optional freeradius_3.0.21+dfsg-2.2+deb11u1.dsc a1dd45baf29d5e17844310f0efec2467 68984 net optional freeradius_3.0.21+dfsg-2.2+deb11u1.debian.tar.xz 268f565310626ddd8fc2e5f0009bc014 20118 net optional freeradius_3.0.21+dfsg-2.2+deb11u1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE1uAexRal3873GVbTd1B55bhQvJMFAmFDE1YRHGJlcm5pQGRl Ymlhbi5vcmcACgkQd1B55bhQvJOTFg/+N9R/WBmVBeWx5yLfersxl0M3ST5kgq6X 76FrMddBqQHKibiYXaU2wl9sONU8ncFP9C7olrl6lG7zE5A+XEECeP2zmwCZJ9mC BCq1OXfTe02VJ53a8Jc87VYxY5sSH3Ek2fCvPrFEXsg256sHPBVlGSdS/r0V220L f+KAa+VmuLY2SK2DsdXgMaMZcYDMCzJtaE6lXsv7r7lDLtZfdVKRL2/eUv86Yk1F obCG5YxfUUF4Kx0tnVdeqjsZxHzQ+nN9u/sAVZGIi7M9KhQD07ATRHvxRu5oE+4I 1k7ov/dHIoAozEfWo0IbatbFz96UyysqYZczzXCxyNbSHEATpg2hS2VeKFyS8ksS BgmJhOj22K3vWXyuxGDa8NPaZP33gJnu4myrPWBZ4SZu2BI5XoUmIjNLWYgN5wqW Dfd2iVX9P8W7jts8xgHv/+Zpwo6Q7EMWVjB8ekHgHKDbDcIOc2gYsmsIcqF0/VIn cE2EOFATvqaAxeDoodrP9T+2ok32TTVQt6arV4VrtlpEA+YaqOkfY+CdlWtTmVTa +VlzFJpbXlP6W5sWMlbiu5strxB9YgQ6c4Au11sm0MqB+3OJXS5S9XJELtz+9vPA Dj3fnl9MaNfUfWpJJH2rYfJaUdMWFHEBYG/bW8C56NZ1y07k7MY5TN8Sdx8SKaST midTkVeLSao= =Y8Tq -END PGP SIGNATURE End Message ---
Bug#994474: marked as done (please update recommends on openblas)
Your message dated Fri, 17 Sep 2021 16:48:27 + with message-id and subject line Bug#994474: fixed in altree 1.3.2-1 has caused the Debian Bug report #994474, regarding please update recommends on openblas 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.) -- 994474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994474 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: altree Version: 1.3.1-10 Severity: normal Tags: patch Dear Maintainer, altree recommends libopenblas-base, which is a transitional dummy package. Please replace it by libopenblas0. Best, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org --- End Message --- --- Begin Message --- Source: altree Source-Version: 1.3.2-1 Done: Vincent Danjean We believe that the bug you reported is fixed in the latest version of altree, 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 994...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vincent Danjean (supplier of updated altree 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: Fri, 17 Sep 2021 18:26:18 +0200 Source: altree Architecture: source Version: 1.3.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Vincent Danjean Closes: 994474 Changes: altree (1.3.2-1) unstable; urgency=medium . [ Andreas Tille ] * Replace dummy package libopenblas-base by libopenblas0 Closes: #994474 * Fix watch file * Standards-Version: 4.6.0 (routine-update) * Set upstream metadata fields: Repository, Repository-Browse. * Apply multi-arch hints. + altree-examples: Add Multi-Arch: foreign. * Do not fail in clean target if latex-make is not installed on local machine . [ Vincent Danjean ] * New upstream version - debian patches applied - XS files refreshed Checksums-Sha1: 041c26a68718e505d9fe0e20ffd138188fe95987 2270 altree_1.3.2-1.dsc 095d136e5ffbeeb2f0e0da550a8a06e8ff5ca7f0 610823 altree_1.3.2.orig.tar.gz 0812c31cd285b088d8124b84e4ba1ebbadb79d11 7108 altree_1.3.2-1.debian.tar.xz f341817894b8b05a89471735375e77670896e95d 9779 altree_1.3.2-1_source.buildinfo Checksums-Sha256: b122ec50dfc9ec454892fc4c34157cd68b229306541749676dc603d5352fd260 2270 altree_1.3.2-1.dsc f9d5beda91aaab219e1397b4c19e0649788a871c8c29fa1e8343a53c5f710b8e 610823 altree_1.3.2.orig.tar.gz c5e7c21820a06a37517dd0b557fe79b53a1482aa4cbe084acacb339220d08947 7108 altree_1.3.2-1.debian.tar.xz a2a9f95d1eb35c12a2ce4ceecc88962379ae722bfebfe8f6391228224675379a 9779 altree_1.3.2-1_source.buildinfo Files: a051f5a1b8def45e7cc22cd38be1e433 2270 science optional altree_1.3.2-1.dsc fd17066d7f6bc07baacf526ff3ee1c3b 610823 science optional altree_1.3.2.orig.tar.gz a05f550b2d6ad5132d8c5da466190bb7 7108 science optional altree_1.3.2-1.debian.tar.xz e4635f063f3e5f9bddbe6ca25ad9c0c4 9779 science optional altree_1.3.2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEE+JeSXDEY4vnrLgRlkfeY37Ht1EFAmFEwjsACgkQlkfeY37H t1HbkRAAnmBoXnlW9eoabgXvNm9lIlF2EovcqGo7QIXKg1haEsQLGe+FkBYoej9z OS6eUCPjxFnYnStFJ6zoKO2skZ+nbdUmEUecfJjhQ+eZ+gJ1ToqpbTyi9lMW3hPF J02dQLMI3DuT7B8Pu+JEmgD8pwdZyJVGquxD8TrUtDgpfOI5Nns5TNra5YxGSVe9 17mxjxCfFtMhTMCTfkbSA5CNNQg8+5XMWmhaffnr0HRnRSlUfiAztGX7se6bFbbN aRECR6v6HY3yAVJZa0w26WF7LK0i9HVwRNXJElDfbLzXF7eDjd+M88E4K1yFCaKt R86n2ALFUcbZKdrAdONbKkMV23kcEYxkLpvF4elJEf8QRdiUagzpIMYEhy4rsdwL W33ix15XNVjuDYH/3DCpx00MOuAYEluobI8rGQW2wOXwvrxf7RseLe2iwB1CCvPR w0sHs+swbx83uq1W1XA+ptNudSsFFpnBSzMFtAsvGNr1aBX1p0WbKKyYQtVvMaHC JvjONLWOChQDjr7ilk3vICQoJmAQB5i6yceRxYy2tNFZOeXYF36s1/cXCPPmaG23 OjVye1kFYPickS43Uj3sQzXR3BY3AMQOvPqMqkPsgLpWpGeNQM6XL88W8m6OuZK2 eihpyTGOwwfUwCioEFulfVhAPLpRaywlhHeT0dBublclapti/Hw= =pw4h -END PGP SIGNATURE End Message ---
Bug#968935: marked as done (Syntax warnings printed to stdout when importing python3-xlsxwriter in Python 3.8.5...)
Your message dated Fri, 17 Sep 2021 16:03:43 + with message-id and subject line Bug#976862: fixed in xlsxwriter 3.0.1-1 has caused the Debian Bug report #976862, regarding Syntax warnings printed to stdout when importing python3-xlsxwriter in Python 3.8.5... to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 976862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-xlsxwriter Version: 1.1.2-0.2 Hi! I'm having issues with python3-xlsxwriter printing syntax warnings to standard out. These can be reproduced by running this one-liner: python3 --version && python3 -Walways -c 'from xlsxwriter import Workbook' When I run it I see: $ python3 --version && python3 -Walways -c 'from xlsxwriter import Workbook' Python 3.8.5 /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:358: SyntaxWarning: "is" with a literal. Did you mean "=="? if token is '': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:2437: SyntaxWarning: "is" with a literal. Did you mean "=="? if options['min_type'] is 'min' and options['min_value'] == 0: /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:2440: SyntaxWarning: "is" with a literal. Did you mean "=="? if options['max_type'] is 'max' and options['max_value'] == 0: /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:4999: SyntaxWarning: "is" with a literal. Did you mean "=="? if props[i]['type'] is 'number': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:6827: SyntaxWarning: "is not" with a literal. Did you mean "!="? if data_bar['bar_axis_position'] is not 'none': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:6862: SyntaxWarning: "is" with a literal. Did you mean "=="? if data_bar['bar_direction'] is 'left': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:6865: SyntaxWarning: "is" with a literal. Did you mean "=="? if data_bar['bar_direction'] is 'right': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:6875: SyntaxWarning: "is" with a literal. Did you mean "=="? if data_bar['bar_axis_position'] is 'middle': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:6878: SyntaxWarning: "is" with a literal. Did you mean "=="? if data_bar['bar_axis_position'] is 'none': /usr/lib/python3/dist-packages/xlsxwriter/chart.py:2497: SyntaxWarning: "is" with a literal. Did you mean "=="? if val is 'right': /usr/lib/python3/dist-packages/xlsxwriter/chart.py:2500: SyntaxWarning: "is" with a literal. Did you mean "=="? if val is 'left': $ I believe that this has been fixed in python-xlsxwriter 1.2.2 according to: https://github.com/jmcnamara/XlsxWriter/issues/660 Please consider upgrading to at least version 1.2.2. Perhaps version 1.3.3 mentioned as a High prio action here might be an even better upgrade path (if it is considered a stable version): https://tracker.debian.org/pkg/xlsxwriter Thanks for the help and the hard work. :) / Sebastian --- End Message --- --- Begin Message --- Source: xlsxwriter Source-Version: 3.0.1-1 Done: Scott Talbert We believe that the bug you reported is fixed in the latest version of xlsxwriter, 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 976...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Talbert (supplier of updated xlsxwriter 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: Fri, 17 Sep 2021 11:43:16 -0400 Source: xlsxwriter Architecture: source Version: 3.0.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Scott Talbert Closes: 966164 968935 976862 Changes: xlsxwriter (3.0.1-1) unstable; urgency=medium . * Team Upload. . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org * d/copyright: Use https protocol in Format field * d/watch: Use https protocol * d/changelog: Remove trailing whitespaces * d/control: Remove ancient X-Python-Version field * d/control: Remove ancient X-Python3-Version field * Convert git repository from git-dpm to gbp layout * Use debhelper-compat instead of debian/compat. * d/control: Update
Bug#976862: marked as done (python3-plaso: log2timeline.py and image_export.py throw many Python 3.9 SyntaxWarnings)
Your message dated Fri, 17 Sep 2021 16:03:43 + with message-id and subject line Bug#976862: fixed in xlsxwriter 3.0.1-1 has caused the Debian Bug report #976862, regarding python3-plaso: log2timeline.py and image_export.py throw many Python 3.9 SyntaxWarnings 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.) -- 976862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-plaso Version: 20190131-3 Severity: normal Since the upgrade to Python 3.9, log2timeline.py and image_export.py throw the following SyntaxWarnings from the files included by both tools: /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:358: SyntaxWarning: "is" with a literal. Did you mean "=="? if token is '': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:2437: SyntaxWarning: "is" with a literal. Did you mean "=="? if options['min_type'] is 'min' and options['min_value'] == 0: /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:2440: SyntaxWarning: "is" with a literal. Did you mean "=="? if options['max_type'] is 'max' and options['max_value'] == 0: /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:4999: SyntaxWarning: "is" with a literal. Did you mean "=="? if props[i]['type'] is 'number': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:6827: SyntaxWarning: "is not" with a literal. Did you mean "!="? if data_bar['bar_axis_position'] is not 'none': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:6862: SyntaxWarning: "is" with a literal. Did you mean "=="? if data_bar['bar_direction'] is 'left': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:6865: SyntaxWarning: "is" with a literal. Did you mean "=="? if data_bar['bar_direction'] is 'right': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:6875: SyntaxWarning: "is" with a literal. Did you mean "=="? if data_bar['bar_axis_position'] is 'middle': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:6878: SyntaxWarning: "is" with a literal. Did you mean "=="? if data_bar['bar_axis_position'] is 'none': /usr/lib/python3/dist-packages/xlsxwriter/chart.py:2497: SyntaxWarning: "is" with a literal. Did you mean "=="? if val is 'right': /usr/lib/python3/dist-packages/xlsxwriter/chart.py:2500: SyntaxWarning: "is" with a literal. Did you mean "=="? if val is 'left': -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-4-amd64 (SMP w/4 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages python3-plaso depends on: ii python33.9.0-4 ii python3-artifacts 20190320-3 ii python3-biplist1.0.3-2 ii python3-certifi2020.6.20-1 ii python3-chardet3.0.4-7 ii python3-crypto 2.6.1-13.1+b3 ii python3-dateutil 2.8.1-4 ii python3-dfdatetime 20200824-1 ii python3-dfvfs 20190128-2.1 ii python3-dfwinreg 20190122-1.1 ii python3-dtfabric 20200621-1 ii python3-efilter1.5-2.1 ii python3-elasticsearch 7.1.0-3 ii python3-fsapfs 20201107-1 ii python3-future 0.18.2-4 ii python3-idna 2.10-1 ii python3-libbde 20190102-1.1+b2 ii python3-libesedb 20181229-3.1+b2 ii python3-libevt 20181227-1.1+b2 ii python3-libevtx20181227-1.1+b2 ii python3-libewf 20140807-2+b2 ii python3-libfsntfs 20200921-1+b1 ii python3-libfvde20190104-1.1+b2 ii python3-libfwnt20181227-1.1+b2 ii python3-libfwsi20181227-1.1+b2 ii python3-liblnk 20181227-1.1+b2 ii python3-libmsiecf 20181227-1.1+b2 ii python3-libolecf 20181231-1.1+b2 ii python3-libqcow20181227-1.1+b2 ii python3-libregf20201007-1 ii python3-libscca20181227-1.1+b2 ii python3-libsigscan 20201117-1 ii python3-libsmdev 20190315-1.1+b2 ii python3-libsmraw 20181227-1.1+b2 ii python3-libvhdi20181227-1.1+b2 ii python3-libvmdk20200926-1+b1 ii python3-libvshadow 20190323-1.1+b2 ii python3-libvslvm 20181227-1.1+b2 ii python3-lz43.1.1+dfsg-1+b1 ii python3-pefile 2019.4.18-1.1 ii python3-psutil
Bug#976862: marked as done (python3-plaso: log2timeline.py and image_export.py throw many Python 3.9 SyntaxWarnings)
Your message dated Fri, 17 Sep 2021 16:03:43 + with message-id and subject line Bug#968935: fixed in xlsxwriter 3.0.1-1 has caused the Debian Bug report #968935, regarding python3-plaso: log2timeline.py and image_export.py throw many Python 3.9 SyntaxWarnings 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.) -- 968935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-plaso Version: 20190131-3 Severity: normal Since the upgrade to Python 3.9, log2timeline.py and image_export.py throw the following SyntaxWarnings from the files included by both tools: /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:358: SyntaxWarning: "is" with a literal. Did you mean "=="? if token is '': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:2437: SyntaxWarning: "is" with a literal. Did you mean "=="? if options['min_type'] is 'min' and options['min_value'] == 0: /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:2440: SyntaxWarning: "is" with a literal. Did you mean "=="? if options['max_type'] is 'max' and options['max_value'] == 0: /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:4999: SyntaxWarning: "is" with a literal. Did you mean "=="? if props[i]['type'] is 'number': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:6827: SyntaxWarning: "is not" with a literal. Did you mean "!="? if data_bar['bar_axis_position'] is not 'none': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:6862: SyntaxWarning: "is" with a literal. Did you mean "=="? if data_bar['bar_direction'] is 'left': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:6865: SyntaxWarning: "is" with a literal. Did you mean "=="? if data_bar['bar_direction'] is 'right': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:6875: SyntaxWarning: "is" with a literal. Did you mean "=="? if data_bar['bar_axis_position'] is 'middle': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:6878: SyntaxWarning: "is" with a literal. Did you mean "=="? if data_bar['bar_axis_position'] is 'none': /usr/lib/python3/dist-packages/xlsxwriter/chart.py:2497: SyntaxWarning: "is" with a literal. Did you mean "=="? if val is 'right': /usr/lib/python3/dist-packages/xlsxwriter/chart.py:2500: SyntaxWarning: "is" with a literal. Did you mean "=="? if val is 'left': -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-4-amd64 (SMP w/4 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages python3-plaso depends on: ii python33.9.0-4 ii python3-artifacts 20190320-3 ii python3-biplist1.0.3-2 ii python3-certifi2020.6.20-1 ii python3-chardet3.0.4-7 ii python3-crypto 2.6.1-13.1+b3 ii python3-dateutil 2.8.1-4 ii python3-dfdatetime 20200824-1 ii python3-dfvfs 20190128-2.1 ii python3-dfwinreg 20190122-1.1 ii python3-dtfabric 20200621-1 ii python3-efilter1.5-2.1 ii python3-elasticsearch 7.1.0-3 ii python3-fsapfs 20201107-1 ii python3-future 0.18.2-4 ii python3-idna 2.10-1 ii python3-libbde 20190102-1.1+b2 ii python3-libesedb 20181229-3.1+b2 ii python3-libevt 20181227-1.1+b2 ii python3-libevtx20181227-1.1+b2 ii python3-libewf 20140807-2+b2 ii python3-libfsntfs 20200921-1+b1 ii python3-libfvde20190104-1.1+b2 ii python3-libfwnt20181227-1.1+b2 ii python3-libfwsi20181227-1.1+b2 ii python3-liblnk 20181227-1.1+b2 ii python3-libmsiecf 20181227-1.1+b2 ii python3-libolecf 20181231-1.1+b2 ii python3-libqcow20181227-1.1+b2 ii python3-libregf20201007-1 ii python3-libscca20181227-1.1+b2 ii python3-libsigscan 20201117-1 ii python3-libsmdev 20190315-1.1+b2 ii python3-libsmraw 20181227-1.1+b2 ii python3-libvhdi20181227-1.1+b2 ii python3-libvmdk20200926-1+b1 ii python3-libvshadow 20190323-1.1+b2 ii python3-libvslvm 20181227-1.1+b2 ii python3-lz43.1.1+dfsg-1+b1 ii python3-pefile 2019.4.18-1.1 ii python3-psutil
Bug#968935: marked as done (Syntax warnings printed to stdout when importing python3-xlsxwriter in Python 3.8.5...)
Your message dated Fri, 17 Sep 2021 16:03:43 + with message-id and subject line Bug#968935: fixed in xlsxwriter 3.0.1-1 has caused the Debian Bug report #968935, regarding Syntax warnings printed to stdout when importing python3-xlsxwriter in Python 3.8.5... to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 968935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-xlsxwriter Version: 1.1.2-0.2 Hi! I'm having issues with python3-xlsxwriter printing syntax warnings to standard out. These can be reproduced by running this one-liner: python3 --version && python3 -Walways -c 'from xlsxwriter import Workbook' When I run it I see: $ python3 --version && python3 -Walways -c 'from xlsxwriter import Workbook' Python 3.8.5 /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:358: SyntaxWarning: "is" with a literal. Did you mean "=="? if token is '': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:2437: SyntaxWarning: "is" with a literal. Did you mean "=="? if options['min_type'] is 'min' and options['min_value'] == 0: /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:2440: SyntaxWarning: "is" with a literal. Did you mean "=="? if options['max_type'] is 'max' and options['max_value'] == 0: /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:4999: SyntaxWarning: "is" with a literal. Did you mean "=="? if props[i]['type'] is 'number': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:6827: SyntaxWarning: "is not" with a literal. Did you mean "!="? if data_bar['bar_axis_position'] is not 'none': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:6862: SyntaxWarning: "is" with a literal. Did you mean "=="? if data_bar['bar_direction'] is 'left': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:6865: SyntaxWarning: "is" with a literal. Did you mean "=="? if data_bar['bar_direction'] is 'right': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:6875: SyntaxWarning: "is" with a literal. Did you mean "=="? if data_bar['bar_axis_position'] is 'middle': /usr/lib/python3/dist-packages/xlsxwriter/worksheet.py:6878: SyntaxWarning: "is" with a literal. Did you mean "=="? if data_bar['bar_axis_position'] is 'none': /usr/lib/python3/dist-packages/xlsxwriter/chart.py:2497: SyntaxWarning: "is" with a literal. Did you mean "=="? if val is 'right': /usr/lib/python3/dist-packages/xlsxwriter/chart.py:2500: SyntaxWarning: "is" with a literal. Did you mean "=="? if val is 'left': $ I believe that this has been fixed in python-xlsxwriter 1.2.2 according to: https://github.com/jmcnamara/XlsxWriter/issues/660 Please consider upgrading to at least version 1.2.2. Perhaps version 1.3.3 mentioned as a High prio action here might be an even better upgrade path (if it is considered a stable version): https://tracker.debian.org/pkg/xlsxwriter Thanks for the help and the hard work. :) / Sebastian --- End Message --- --- Begin Message --- Source: xlsxwriter Source-Version: 3.0.1-1 Done: Scott Talbert We believe that the bug you reported is fixed in the latest version of xlsxwriter, 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 968...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Talbert (supplier of updated xlsxwriter 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: Fri, 17 Sep 2021 11:43:16 -0400 Source: xlsxwriter Architecture: source Version: 3.0.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Scott Talbert Closes: 966164 968935 976862 Changes: xlsxwriter (3.0.1-1) unstable; urgency=medium . * Team Upload. . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org * d/copyright: Use https protocol in Format field * d/watch: Use https protocol * d/changelog: Remove trailing whitespaces * d/control: Remove ancient X-Python-Version field * d/control: Remove ancient X-Python3-Version field * Convert git repository from git-dpm to gbp layout * Use debhelper-compat instead of debian/compat. * d/control: Update
Bug#966164: marked as done (python3-xlsxwriter: Homepage URL is not working.)
Your message dated Fri, 17 Sep 2021 16:03:43 + with message-id and subject line Bug#966164: fixed in xlsxwriter 3.0.1-1 has caused the Debian Bug report #966164, regarding python3-xlsxwriter: Homepage URL is 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.) -- 966164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966164 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-xlsxwriter Version: 1.1.2-0.2 Severity: normal X-Debbugs-Cc: witold.bary...@gmail.com Dear Maintainer, packages points to homepage URL: https://xlsxwriter.readthedocs.io/en/latest/ but this URL doesn't work (404 error). It should be replaced with https://xlsxwriter.readthedocs.io/ Best regards, Witold -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-1-amd64 (SMP w/32 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-xlsxwriter depends on: ii python3 3.8.2-3 python3-xlsxwriter recommends no packages. python3-xlsxwriter suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: xlsxwriter Source-Version: 3.0.1-1 Done: Scott Talbert We believe that the bug you reported is fixed in the latest version of xlsxwriter, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Talbert (supplier of updated xlsxwriter 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: Fri, 17 Sep 2021 11:43:16 -0400 Source: xlsxwriter Architecture: source Version: 3.0.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Scott Talbert Closes: 966164 968935 976862 Changes: xlsxwriter (3.0.1-1) unstable; urgency=medium . * Team Upload. . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org * d/copyright: Use https protocol in Format field * d/watch: Use https protocol * d/changelog: Remove trailing whitespaces * d/control: Remove ancient X-Python-Version field * d/control: Remove ancient X-Python3-Version field * Convert git repository from git-dpm to gbp layout * Use debhelper-compat instead of debian/compat. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. . [ Sandro Tosi ] * Use the new Debian Python Team contact name and address . [ Scott Talbert ] * Remove Checkbox developers from Maintainer/Uploaders * Update Homepage location (Closes: #966164) * Update Standards-Version to 4.6.0 (no changes needed) * Update to new upstream version 3.0.1 (Closes: #968935, #976862) * Remove now-unused section in d/copyright * Add lintian override for non-UTF-8 file * Rules-Requires-Root: no * Update debhelper-compat to 13 * Update d/watch version to 4 Checksums-Sha1: 93da2300624e566961690ca40fb291e789947600 1949 xlsxwriter_3.0.1-1.dsc b432461d7c7c7b8487954208d53376ecbcd7b8c6 263628 xlsxwriter_3.0.1.orig.tar.gz 88054c3c27127d833e77b1c8db7f60085a19976f 3916 xlsxwriter_3.0.1-1.debian.tar.xz 365d432c4bf21b22ac7fd2a460e3fac43ca11806 6488 xlsxwriter_3.0.1-1_amd64.buildinfo Checksums-Sha256: 1ecee1838764d99a76ebb6bc8134987b0d550b43143fae77db1f20e722d393de 1949 xlsxwriter_3.0.1-1.dsc 3f39bf581c55f3ad1438bc170d7f4c4649cee8b6b7a80d21f79508118eeea52a 263628 xlsxwriter_3.0.1.orig.tar.gz 4bd06d60868046bbdea517858a329275b2ba1d701218ed22aee1780f02e27d55 3916 xlsxwriter_3.0.1-1.debian.tar.xz 25295317605ce62f4c65c9be0d5327c3d30b93c14fe36798486e43d501e98aee 6488 xlsxwriter_3.0.1-1_amd64.buildinfo Files: 5f368c0d17298e92e67358b85ef21667 1949 python optional xlsxwriter_3.0.1-1.dsc 5f759dccf222e8f2a9924e90c4afaf84 263628 python optional xlsxwriter_3.0.1.orig.tar.gz 2fe856ad6813d6b5255cada3a134b756 3916 python optional xlsxwriter_3.0.1-
Bug#989769: marked as done (libstatgen FTCBFS: debian/rules uses the build architecture compiler as a make default)
Your message dated Fri, 17 Sep 2021 15:34:22 + with message-id and subject line Bug#989769: fixed in libstatgen 1.0.15-1 has caused the Debian Bug report #989769, regarding libstatgen FTCBFS: debian/rules uses the build architecture compiler as a make default 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.) -- 989769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libstatgen Version: 1.0.14-7 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs libstatgen fails to cross build from source (for amd64 when built on arm64), because debian/rules uses $(CXX) without initializing it. The easiest way of fixing that - using dpkg's buildtools.mk - makes libstatgen cross buildable. Please consider applying the attached patch. Helmut diff -Nru libstatgen-1.0.14/debian/changelog libstatgen-1.0.14/debian/changelog --- libstatgen-1.0.14/debian/changelog 2020-08-03 21:32:36.0 +0100 +++ libstatgen-1.0.14/debian/changelog 2021-06-12 07:51:24.0 +0100 @@ -1,3 +1,10 @@ +libstatgen (1.0.14-7.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Let dpkg's buildtools.mk supply $(CC). (Closes: #-1) + + -- Helmut Grohne Sat, 12 Jun 2021 07:51:24 +0100 + libstatgen (1.0.14-7) unstable; urgency=medium * Team upload. diff -Nru libstatgen-1.0.14/debian/rules libstatgen-1.0.14/debian/rules --- libstatgen-1.0.14/debian/rules 2020-08-03 21:32:36.0 +0100 +++ libstatgen-1.0.14/debian/rules 2021-06-12 06:36:27.0 +0100 @@ -1,6 +1,7 @@ #!/usr/bin/make -f export DEB_BUILD_MAINT_OPTIONS = hardening=+all +-include /usr/share/dpkg/buildtools.mk # Define SONAME for shared library LIBNAME=libStatGen --- End Message --- --- Begin Message --- Source: libstatgen Source-Version: 1.0.15-1 Done: Dylan Aïssi We believe that the bug you reported is fixed in the latest version of libstatgen, 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 989...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dylan Aïssi (supplier of updated libstatgen 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: Fri, 17 Sep 2021 17:14:18 +0200 Source: libstatgen Architecture: source Version: 1.0.15-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Dylan Aïssi Closes: 989769 Changes: libstatgen (1.0.15-1) unstable; urgency=medium . [ Helmut Grohne ] * Fix FTCBFS: Let dpkg's buildtools.mk supply $(CC). (Closes: #989769) . [ Dylan Aïssi ] * New upstream version * Remove merged patches * Standards-Version: 4.6.0 * Disable dh_auto_test * Update symbols file Checksums-Sha1: 6d29888bafc5058844883fbebf8d8ac3f89bc596 2151 libstatgen_1.0.15-1.dsc ae8fc23f436aa9cb251fa997e96f79e49996c6d3 560782 libstatgen_1.0.15.orig.tar.gz f4dbc5d1b446e5a2bb32faa4ed5b1fe2497cd97d 19932 libstatgen_1.0.15-1.debian.tar.xz 8c77d5eb7fbf62fc850f7eca997be772aed7173c 7226 libstatgen_1.0.15-1_amd64.buildinfo Checksums-Sha256: 43e0b8777adb226c3c725e56f2318a47b18221f3c5fba11c93ab290195fb3791 2151 libstatgen_1.0.15-1.dsc 075dcd891409c48d76c0c66186c0cc479bc3cd50bba093e7f318e1d1d19961ff 560782 libstatgen_1.0.15.orig.tar.gz 71a226250729397fc03b8269e7754240b508a3618363b5845e5158b12fbac4a9 19932 libstatgen_1.0.15-1.debian.tar.xz 2f584bb17fc55d37a287579667df557435ac1be420abc0aa05e9eceaebe93971 7226 libstatgen_1.0.15-1_amd64.buildinfo Files: 77e8fda4ed2e87300941c99fc78bb74f 2151 science optional libstatgen_1.0.15-1.dsc e26eaeb3cdb938328c7b0b43b674a1c8 560782 science optional libstatgen_1.0.15.orig.tar.gz ec7864a8a08fb62ad5899c8a4e2edbaa 19932 science optional libstatgen_1.0.15-1.debian.tar.xz 62065c121ddc548799e377c3287d2c40 7226 science optional libstatgen_1.0.15-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAmFEsY8ACgkQYS7xYT4F D1Rzvw/+MPB7RrIJeln/jcuJEAjfgemvZEddWJ59Oq5zfQS5LN6KX8+AtGc58Xbz s2IWyJjgq+qA71EYxj3DoPkUqGv4pEmo8eku/Z80IF0M1R3mbgHF6NIc5rPF16GW pJh72ojIkhYl5PxASQ2pLNEQdJLJfnhGtppIBhqpn8+ck0qU1Rh2eUgyEV4
Bug#993843: marked as done (zsh-static segfaults immediately)
Your message dated Fri, 17 Sep 2021 15:19:33 + with message-id and subject line Bug#993843: fixed in zsh 5.8-10 has caused the Debian Bug report #993843, regarding zsh-static segfaults immediately 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.) -- 993843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993843 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: zsh-static Version: 5.8-7 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** I recently upgraded zsh-static:amd64 from 5.8-6+b2 to 5.8-7. With version 5.8-7, /bin/zsh-static segfaults immediately upon execution. The previous 5.8-6+b2 version was fine. Here is an example attempt to run zsh-static: tensor(pts/3):~> /bin/zsh-static zsh: segmentation fault /bin/zsh-static tensor(pts/3):~> echo $? 139 A side effect of this is that any user relying on zsh-static as their login shell cannot login via ssh any more, since their shell immediately crashes. -- Package-specific info: Packages which provide vendor completions: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++--=--=== ii bubblewrap 0.5.0-1 amd64utility for unprivileged chroot and namespace manipulation ii curl 7.74.0-1.3+b1 amd64command line tool for transferring data with URL syntax ii mercurial-common 5.9-3 all easy-to-use, scalable distributed version control system (common files) ii systemd 247.9-1 amd64system and service manager ii udev 247.9-1 amd64/dev/ and hotplug management daemon dpkg-query: no path found matching pattern /usr/share/zsh/vendor-functions/ -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/1 CPU thread) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages zsh-static depends on: ii zsh 5.8-7 zsh-static recommends no packages. Versions of packages zsh-static suggests: pn zsh-doc -- no debconf information --- End Message --- --- Begin Message --- Source: zsh Source-Version: 5.8-10 Done: Axel Beckert We believe that the bug you reported is fixed in the latest version of zsh, 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 993...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Axel Beckert (supplier of updated zsh 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: Fri, 17 Sep 2021 15:48:52 +0200 Source: zsh Architecture: source Version: 5.8-10 Distribution: unstable Urgency: medium Maintainer: Debian Zsh Maintainers Changed-By: Axel Beckert Closes: 993843 Changes: zsh (5.8-10) unstable; urgency=medium . * [130801d2,92b60e43] Fix segfaults in zsh-static after glibc upgrades by making sure nothing is loaded dynamically anymore. (Closes: #993843 and fixes autopkgtest failures in not or too up to date chroots.) Checksums-Sha1: b34061eb58a1f6f383498ec237f8be46138fbdb8 2842 zsh_5.8-10.dsc dbee283880571865dc3af21ee14456a19f9cd518 93460 zsh_5.8-10.debian.tar.xz 5b71363d650183de21e3f879e3fe90253c2fb69b 6841 zsh_5.8-10_source.buildinfo Checksums-Sha256: 3b7ffa66c636b75ca8ea57c407898644e2a9a00f694dad4262ae4572e72369a9 2842 zsh_5.8-10.dsc 4257459dd44ca9966f6c3b86e7d3ca1d2373f85d2d0cf6439eb73b1feaa2ed9a 93460 zsh_5.8-10.debian.tar.xz 09b73618927bc8d1ebb1198c466bebe4ddb169193be0df2f2fc2d2d1eabecb22 6841 zsh_5.8-10_source.buildinfo Files: 9331d3683f3714fde5876999056b3010 2842 shells optional zsh_5.8-10.dsc 10f01a61cfe4805495b39f5e46ec4bb2 93460 shells optional zsh_5.8-10.de
Bug#978913: marked as done (uisp: ftbfs with autoconf 2.70)
Your message dated Fri, 17 Sep 2021 15:19:23 +
with message-id
and subject line Bug#978913: fixed in uisp 20050207-4.4
has caused the Debian Bug report #978913,
regarding uisp: ftbfs with autoconf 2.70
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.)
--
978913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978913
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:uisp
Version: 20050207-4.3
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270
[This bug report is not targeted to the upcoming bullseye release]
The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.
The full build log can be found at:
http://qa-logs.debian.net/2020/09/26.ac270/uisp_20050207-4.3_unstable_ac270.log
The last lines of the build log are at the end of this report.
To build with autoconf 2.70, please install the autoconf package from
experimental: apt-get -t=experimental install autoconf
[...]
configure.ac:27: You should run autoupdate.
./lib/autoconf/status.m4:719: AC_CONFIG_HEADER is expanded from...
configure.ac:27: the top level
configure.ac:28: warning: The macro `AC_FOREACH' is obsolete.
configure.ac:28: You should run autoupdate.
./lib/autoconf/general.m4:190: AC_FOREACH is expanded from...
aclocal.m4:203: _AM_SET_OPTIONS is expanded from...
aclocal.m4:56: AM_INIT_AUTOMAKE is expanded from...
configure.ac:28: the top level
configure.ac:37: warning: The macro `AC_HEADER_STDC' is obsolete.
configure.ac:37: You should run autoupdate.
./lib/autoconf/headers.m4:657: AC_HEADER_STDC is expanded from...
configure.ac:37: the top level
configure.ac:44: warning: The macro `AC_HEADER_TIME' is obsolete.
configure.ac:44: You should run autoupdate.
./lib/autoconf/headers.m4:696: AC_HEADER_TIME is expanded from...
configure.ac:44: the top level
/bin/bash ./config.status --recheck
running /bin/bash ./configure --host=x86_64-linux-gnu --build=x86_64-linux-gnu
--prefix=/usr --mandir=${prefix}/share/man --infodir=${prefix}/share/info
CXXFLAGS=-g -Wall -Wno-narrowing -O2 build_alias=x86_64-linux-gnu
host_alias=x86_64-linux-gnu --no-create --no-recursion
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for x86_64-linux-gnu-g++... x86_64-linux-gnu-g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C++... yes
checking whether x86_64-linux-gnu-g++ accepts -g... yes
checking for x86_64-linux-gnu-g++ option to enable C++11 features... none needed
checking for style of include used by make... GNU
checking dependency style of x86_64-linux-gnu-g++... gcc3
checking for x86_64-linux-gnu-gcc... x86_64-linux-gnu-gcc
checking whether the compiler supports GNU C... yes
checking whether x86_64-linux-gnu-gcc accepts -g... yes
checking for x86_64-linux-gnu-gcc option to enable C11 features... none needed
checking dependency style of x86_64-linux-gnu-gcc... gcc3
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for sys/time.h... yes
checking for sys/select.h... yes
checking for sys/socket.h... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fcntl.h... yes
checking for inttypes.h... (cached) yes
checking for stdlib.h... yes
checking for string.h... yes
checking for sys/ioctl.h... yes
checking for sys/time.h... (cached) yes
checking for termios.h... yes
checking for unistd.h... (cached) yes
checking for stdbool.h that conforms to C99... yes
checking for _Bool... yes
checking for an ANSI C-conforming const... yes
checking for size_t... yes
checking how to run the C preprocessor... x86_64-linux-gnu-gcc -E
checking whether x86_64-linux-gnu-gcc needs -traditional... no
configure: error: cannot run /bin/sh ./config.sub
make[1]: *** [Makefile:200: config.status] Error 127
make[1]: Leaving directory '/<>'
make: *** [debian/rules:29: build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit st
Bug#965856: marked as done (uisp: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Fri, 17 Sep 2021 15:19:23 + with message-id and subject line Bug#965856: fixed in uisp 20050207-4.4 has caused the Debian Bug report #965856, regarding uisp: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965856 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: uisp Version: 20050207-4.3 Severity: normal Usertags: compat-5-6-removal Hi, The package uisp uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: uisp Source-Version: 20050207-4.4 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of uisp, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated uisp 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: Fri, 17 Sep 2021 10:59:52 -0400 Source: uisp Architecture: source Version: 20050207-4.4 Distribution: unstable Urgency: high Maintainer: Margarita Manterola Changed-By: Boyuan Yang Closes: 529148 965856 978913 Changes: uisp (20050207-4.4) unstable; urgency=high . * Non-maintainer upload. * Replace obsolete Priority: extra with Priority: optional. * debian/rules: Rewrite with dh sequencer. + Also invoke autoreconf before configure. * debian/compat: Dropped, not needed. * debian/control: + Bump Standards-Version to 4.6.0. + Bump debhelper compat to v13. (Closes: #965856) * debian/patches; Refresh patches. * debian/patches/0006-fix-configure.ac.patch: Make configure.ac compatible with autoconf 2.69+. (Closes: #978913) * debian/watch: Update to v4 format. (Closes: #529148) * debian/not-installed: Remove duplicated installation entry. * debian/dirs: Dropped, useless. * Apply patch from Ubuntu: . [ Ilya Barygin ] * Build with -Wno-error as some warn_unused_result warnings are generated. Fixes FTBFS. Checksums-Sha1: 10236673d6dab8ee5426ef0c54c3b2064ee06643 1711 uisp_20050207-4.4.dsc f1b5bf5bdd9597ae7fd8d8ae733d6f5cd31f9cf7 166745 uisp_20050207.orig.tar.gz 748c79d22dd606f7b4ec75f95698c729dd2f3e7a 5864 uisp_20050207-4.4.debian.tar.xz 5ba8be18b7994b1f1e391ddd52bac39bdf05383b 5921 uisp_20050207-4.4_amd64.buildinfo Checksums-Sha256: 5ba3b343f872a28cce34f841e3a6bb0c7144950e39422ec9ab5bad7512ba3df3 1711 uisp_20050207-4.4.dsc 7c43c5f34f00a7243bda87457e43dc9122b5a3837b1370b30f39c1eecbedccae 166745 uisp_20050207.orig.tar.gz 1d9e6ac4b5de5768cc6fae35c6342b7b31bbe079d29edf6590a26d1abbb6ee0b 5864 uisp_20050207-4.4.debian.tar.xz 065e495277ab462756edc5257076355172c4ac238dfd85434c3fa31cf3a3d9eb 5921 uisp_20050207-4.4_amd64.buildinfo Files: 886e6131ea77069a61ebb5d9651ff196 1711 electronics optional uisp_20050207-4.4.dsc b1e499d5a1011489635c1a0e482b1627 166745 electronics optional uisp_20050207.orig.tar.gz c9edfde5325a669c61b3825b022326ba 5864 electronics optional uisp_20050207-4.4.debian.tar.xz 6ced6ae6c08019e8033417909054cacd 5921
Bug#529148: marked as done (uisp: please upgrade your watch file)
Your message dated Fri, 17 Sep 2021 15:19:23 + with message-id and subject line Bug#529148: fixed in uisp 20050207-4.4 has caused the Debian Bug report #529148, regarding uisp: please upgrade your watch file 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.) -- 529148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: uisp Version: 20050207-4 Severity: minor Usertags: versionless-watch Hi, Your package ships a version 1 debian/watch file, but this is deprecated and support for it is going to be removed soon from uscan. It is strongly recommended that you rewrite it in the version 3 format, as described by uscan's man page, since it brings more flexibility and support for it will not be dropped any time soon. If you need help rewriting it don't hesitate to reply to this message, or tag the bug as 'help'. Kind regards, Raphael Geissert --- End Message --- --- Begin Message --- Source: uisp Source-Version: 20050207-4.4 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of uisp, 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 529...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated uisp 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: Fri, 17 Sep 2021 10:59:52 -0400 Source: uisp Architecture: source Version: 20050207-4.4 Distribution: unstable Urgency: high Maintainer: Margarita Manterola Changed-By: Boyuan Yang Closes: 529148 965856 978913 Changes: uisp (20050207-4.4) unstable; urgency=high . * Non-maintainer upload. * Replace obsolete Priority: extra with Priority: optional. * debian/rules: Rewrite with dh sequencer. + Also invoke autoreconf before configure. * debian/compat: Dropped, not needed. * debian/control: + Bump Standards-Version to 4.6.0. + Bump debhelper compat to v13. (Closes: #965856) * debian/patches; Refresh patches. * debian/patches/0006-fix-configure.ac.patch: Make configure.ac compatible with autoconf 2.69+. (Closes: #978913) * debian/watch: Update to v4 format. (Closes: #529148) * debian/not-installed: Remove duplicated installation entry. * debian/dirs: Dropped, useless. * Apply patch from Ubuntu: . [ Ilya Barygin ] * Build with -Wno-error as some warn_unused_result warnings are generated. Fixes FTBFS. Checksums-Sha1: 10236673d6dab8ee5426ef0c54c3b2064ee06643 1711 uisp_20050207-4.4.dsc f1b5bf5bdd9597ae7fd8d8ae733d6f5cd31f9cf7 166745 uisp_20050207.orig.tar.gz 748c79d22dd606f7b4ec75f95698c729dd2f3e7a 5864 uisp_20050207-4.4.debian.tar.xz 5ba8be18b7994b1f1e391ddd52bac39bdf05383b 5921 uisp_20050207-4.4_amd64.buildinfo Checksums-Sha256: 5ba3b343f872a28cce34f841e3a6bb0c7144950e39422ec9ab5bad7512ba3df3 1711 uisp_20050207-4.4.dsc 7c43c5f34f00a7243bda87457e43dc9122b5a3837b1370b30f39c1eecbedccae 166745 uisp_20050207.orig.tar.gz 1d9e6ac4b5de5768cc6fae35c6342b7b31bbe079d29edf6590a26d1abbb6ee0b 5864 uisp_20050207-4.4.debian.tar.xz 065e495277ab462756edc5257076355172c4ac238dfd85434c3fa31cf3a3d9eb 5921 uisp_20050207-4.4_amd64.buildinfo Files: 886e6131ea77069a61ebb5d9651ff196 1711 electronics optional uisp_20050207-4.4.dsc b1e499d5a1011489635c1a0e482b1627 166745 electronics optional uisp_20050207.orig.tar.gz c9edfde5325a669c61b3825b022326ba 5864 electronics optional uisp_20050207-4.4.debian.tar.xz 6ced6ae6c08019e8033417909054cacd 5921 electronics optional uisp_20050207-4.4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmFErY0ACgkQwpPntGGC Ws5uthAAr6jCELshKLzPLX3T+z2k0oavo9wuz4y7/YpRqKaoPXDlUZ+vMCCmrQ6y rWBmkJodITmuV0cqthZ7vMIGxbFiRCoHxy4xng4/D6ptMYVWgAYGkSJxljT0T7W5 Le8jB1v6F7y6d3Tx4HCT4Qm70PoHt7LhKve3pAzK37XcTBwgxm38rvsg3Orm+Fs2 kpM49fWunh5KSy5gI5eagRWpkNDIZuVyFS60rmEMfdSHoR3brfOGF+bEagQWWB+C 3wZIBOf8IZzHT+/s8Jg9HfUUS/iSG3zZJrfoql4h61FASuXWiHohDPkzzO9ZVMvP RwIMZOR1xvteXXzD/B6Y5UXAOl6ca6BAKd5UuddJ2d+aKnruDxdArnfqFDE68biL rM48L+HXIgUjy7TcTI3sd0Xwiu8A2zARfOrhTy9v+tTVCre1Zy2cnncFiioyD334 DXNBLNlYp8JUDKMJGiHRstKvsP5Nc06R1oHsS7dfX
Bug#984363: marked as done (therion: ftbfs with GCC-11)
Your message dated Fri, 17 Sep 2021 14:37:43 + with message-id and subject line Bug#984363: fixed in therion 6.0.2ds1-1 has caused the Debian Bug report #984363, regarding therion: ftbfs with GCC-11 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.) -- 984363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984363 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:therion Version: 5.5.7ds1-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/therion_5.5.7ds1-1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -DTHLINUX -O2 -DPROJ_VER=7 -I/usr/include -std=c++14 -o thtexfonts.o thtexfonts.cxx g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -DTHLINUX -O2 -DPROJ_VER=7 -I/usr/include -std=c++14 -o thsymbolset.o thsymbolset.cxx g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -DTHLINUX -O2 -DPROJ_VER=7 -I/usr/include -std=c++14 -o thlang.o thlang.cxx g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -DTHLINUX -O2 -DPROJ_VER=7 -I/usr/include -std=c++14 -o thmapstat.o thmapstat.cxx g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -DTHLINUX -O2 -DPROJ_VER=7 -I/usr/include -std=c++14 -o thexpdb.o thexpdb.cxx g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -DTHLINUX -O2 -DPROJ_VER=7 -I/usr/include -std=c++14 -o thpic.o thpic.cxx g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -DTHLINUX -O2 -DPROJ_VER=7 -I/usr/include -std=c++14 -o thsketch.o thsketch.cxx g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -DTHLINUX -O2 -DPROJ_VER=7 -I/usr/include -std=c++14 -o thproj.o thproj.cxx g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -DTHLINUX -O2 -DPROJ_VER=7 -I/usr/include -std=c++14 -o ./extern/lxMath.o loch/lxMath.cxx g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -DTHLINUX -O2 -DPROJ_VER=7 -I/usr/include -std=c++14 -o ./extern/lxFile.o loch/lxFile.cxx g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -DTHLINUX -O2 -DPROJ_VER=7 -I/usr/include -std=c++14 -o thdb3d.o thdb3d.cxx g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -DTHLINUX -O2 -DPROJ_VER=7 -I/usr/include -std=c++14 -o
Processed (with 1 error): closing 988219
Processing commands for cont...@bugs.debian.org: > Version: 0.59.1-1 Unknown command or malformed arguments to command. > close 988219 Bug #988219 [meson] meson: Move package into unstable Marked Bug as done > End of message, stopping processing here. Please contact me if you need assistance. -- 988219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 951191
Processing commands for cont...@bugs.debian.org: > close 951191 2.32-3 Bug #951191 [src:glibc] Backport /proc-based lchmod/fchmodat emulation Marked as fixed in versions glibc/2.32-3. Bug #951191 [src:glibc] Backport /proc-based lchmod/fchmodat emulation Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 951191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993511: marked as done (spdlog: FTBFS with glibc 2.34)
Your message dated Fri, 17 Sep 2021 13:20:13 + with message-id and subject line Bug#993511: fixed in spdlog 1:1.8.5+ds-3 has caused the Debian Bug report #993511, regarding spdlog: FTBFS with glibc 2.34 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.) -- 993511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993511 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spdlog Version: 1:1.8.5+ds-2 Severity: important Hi Maintainer Your package uses a vendored copy of catch.hpp. It will FTBFS once glibc is upgraded to 2.34 due to MINSIGSTKSZ and SIGSTKSZ no longer being defined. You could take this opportunity to switch to using the catch2 package [1] in Debian where this is already fixed. Regards Graham [1] https://tracker.debian.org/pkg/catch2 --- End Message --- --- Begin Message --- Source: spdlog Source-Version: 1:1.8.5+ds-3 Done: Michael R. Crusoe We believe that the bug you reported is fixed in the latest version of spdlog, 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 993...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael R. Crusoe (supplier of updated spdlog 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: Fri, 17 Sep 2021 14:59:55 +0200 Source: spdlog Architecture: source Version: 1:1.8.5+ds-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Michael R. Crusoe Closes: 993511 Changes: spdlog (1:1.8.5+ds-3) unstable; urgency=medium . * Ignore vendored copy of catch.hpp; use the one from the catch2 package instead. Closes: #993511 Checksums-Sha1: 3fe8a3387548cc5f74c4e52770acab938d307266 2131 spdlog_1.8.5+ds-3.dsc 65ffb8604c64b5965f30788f6315e7a33e8f1f7f 6544 spdlog_1.8.5+ds-3.debian.tar.xz 276d7d9ad33c0ceadb030d8e870739eb304a0365 7602 spdlog_1.8.5+ds-3_source.buildinfo Checksums-Sha256: 89160542c631a8dceafdf5445addb6183b1e183e3b02b8ff8240cff04e527772 2131 spdlog_1.8.5+ds-3.dsc efd021c3e26545e4c0272c4be76fe98e969008c0e9df2fcd1074ab3eed7bf314 6544 spdlog_1.8.5+ds-3.debian.tar.xz e0a7b7caf7d205a8d0f0e4634472148fd6f63e02badd8617a040d584515eb336 7602 spdlog_1.8.5+ds-3_source.buildinfo Files: bbb03bcc0fb68044350c623ea5c36393 2131 libdevel optional spdlog_1.8.5+ds-3.dsc 6d6aae2d2f10b5295cbfd9671a4c3e04 6544 libdevel optional spdlog_1.8.5+ds-3.debian.tar.xz 7e4f6bb722cf1bb2ade01973dfe22724 7602 libdevel optional spdlog_1.8.5+ds-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAmFEkVcACgkQPCZ2P2xn 5uI3jw/6AnfJI+3x0+CRZ+oMQ5yqdVuEddDJau4hyDA+yKP41UOO/70PVPx5OVK3 Kv1b5N3QtV0OmbhyzVoCcUwQiMcTIp3nv8qT6HvJYjmdxAu9y5e3fl64mc46Z0m6 itchwJsDpOD3DORDEZk4Z8ickOaSIwk1BlBd9DeuCO1X0iv2PLwyeYhem1v+ifeH fQfvjHtDCPKkvUHwlBrMwEQGPBrbpUPO9SnrMZjeC6caqoWROiwDB/TaL8nDctye aTZ7L5tAmYjLRA9uLs5b3tnqc6S16Po2QWSEn84RLinuC4KzT6nP/x3R4kH1xvLM 7pEKU9PXZukU8dfO2hkaztK25YGZCQ0tZR6Hp6O8HDr+XEk8m+6i8d4Yt0tEtZJJ ZRXi+9scQk0cWobh9uB76RGNcKGoV8SyRK5RapoTY/KZ1WeywMs1lqQj+PqYHkmp okSjrDD71f1AHOtt1q2T7UyfEoCl1DBsbIpOWqQZhDngNHmqpWbXxMlxf6l+szBp 9kUHrU59weGW4xf6eFAAu+YP8h1MkezLKt3ez2nMgoZOKGSe3GjKmKNzd8Rpd6Vv c050BRBwcPKwnotAZJXX/nC79DRCAQgPgQppMAGFU6IZQi3IURMse7yfKvqzZzl0 gp9pa9m7/TUSg6RatrNk+89QqwfAWNLuF+YFV9L2ZEphYLKhE8w= =+CWA -END PGP SIGNATURE End Message ---
Bug#989021: marked as done (rxvt-unicode: new usptream version available: 9.26)
Your message dated Fri, 17 Sep 2021 09:11:25 -0400 with message-id <20210917131125.kxw25yocq5gwo...@zeta.rak.ac> and subject line Re: Bug#989021: rxvt-unicode: new usptream version available: 9.26 has caused the Debian Bug report #989021, regarding rxvt-unicode: new usptream version available: 9.26 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.) -- 989021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rxvt-unicode Severity: normal X-Debbugs-Cc: rharw...@club.cc.cmu.edu Dear Maintainer, Version 9.26 is available upstream: http://dist.schmorp.de/rxvt-unicode/ (This isn't particularly high priority for me since you've already patched the recent CVE.) Thanks, --Robbie --- End Message --- --- Begin Message --- 9.26 is available in Debian unstable--- End Message ---
Bug#994475: marked as done (wannier90 autopkgtest needs to be adapted for lapack 3.10)
Your message dated Fri, 17 Sep 2021 12:35:37 + with message-id and subject line Bug#994475: fixed in wannier90 3.1.0+ds-5 has caused the Debian Bug report #994475, regarding wannier90 autopkgtest needs to be adapted for lapack 3.10 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.) -- 994475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994475 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wannier90 Version: 3.1.0+ds-4 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: needs-update Dear Maintainer, Since the upload of lapack 3.10.0-1, the autopkgtest of wannier90 fails in unstable. See for example: https://ci.debian.net/data/autopkgtest/testing/amd64/w/wannier90/15283094/log.gz It seems that it’s only a matter of slightly increasing a test tolerance, most likely because some lapack algorithm is now implemented in a different way. However, if you think that this is a bug in lapack, feel free to reassign it, ideally with the details of your analysis. N.B. : when trying to reproduce the problem, please ensure that your lapack alternative (as given by “update-alternatives --display liblapack.so.3-x86_64-linux-gnu) points to /usr/lib/x86_64-linux- gnu/lapack/liblapack.so.3, and not to the binary provided by either openblas or atlas (because these two have not yet been recompiled against lapack 3.10, and thus do not expose the problem). Best regards, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: wannier90 Source-Version: 3.1.0+ds-5 Done: Andrius Merkys We believe that the bug you reported is fixed in the latest version of wannier90, 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 994...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrius Merkys (supplier of updated wannier90 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: Fri, 17 Sep 2021 07:03:14 -0400 Source: wannier90 Architecture: source Version: 3.1.0+ds-5 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Andrius Merkys Closes: 994475 Changes: wannier90 (3.1.0+ds-5) unstable; urgency=medium . * Skipping a test case failing with lapack 3.10 (Closes: #994475). * Updating description of skip_flaky_tests.patch. Checksums-Sha1: 214c8d8bfc1c0fecfdb0bf5acd0f0bee9fe6b041 2365 wannier90_3.1.0+ds-5.dsc 7b6635316e75f32c693d813fe1196fcaca7fde6f 13924 wannier90_3.1.0+ds-5.debian.tar.xz fdda64132366345a4a5fb215e897d7a032e3f5ac 9481 wannier90_3.1.0+ds-5_source.buildinfo Checksums-Sha256: 39c1a0442984ab067805fac28d7db24ee915d2517ad84658e9f39512dd452180 2365 wannier90_3.1.0+ds-5.dsc af5a719f59836b0d5b7557f196a000c868d92c27a3e7e2fd0f6d64df414cd412 13924 wannier90_3.1.0+ds-5.debian.tar.xz 5350a8c67169e639cc7ce2f3a4f8ad9118ba24c00e4702ce693f610ef9bb69f4 9481 wannier90_3.1.0+ds-5_source.buildinfo Files: 1f86a6ab84078eaa04065195d95b4fd4 2365 science optional wannier90_3.1.0+ds-5.dsc 790f9ee0ec24fbaad6b266959d988395 13924 science optional wannier90_3.1.0+ds-5.debian.tar.xz 5df4d322ffc6c417ca4b28c1c8337e7e 9481 science optional wannier90_3.1.0+ds-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAmFEhcwSHG1lcmt5c0Bk ZWJpYW4ub3JnAAoJEOX0P5wnNPKHWQsP/3F4l1vfwNlHA1wTfWfrTsy8E3o/PH+0 91jmkUIB3ol3Lbw67G9z7ZADHQL9IKLxaV+JQvDMaTkLorYQcpqfoIetjS5Hya0O Iz65D5uuWY3+u1ABzhpo0I9VAGQ99wrkLXQ3B9W+MiNTPmx+nGuMu5ZwQuVEd4s+ VyfLhbRLIRwxXYJde5ubJQLweA/ctvTUC/6ecZ4aA/zHg/czv34PCndeICmiGLqz /Lymbk+piHAMx20mfAwnIlrBsK/N3bi+EIFx5RwLP5FJ4J9vMPRdC19Q6nGI0lfr 1B9EdCK6tEZES54PkPldnboJa/tve6Zvm4BfBjJ/24ozEtGWRa9eY+mdRA0q31EK 3xyNV3f0AksBxXOYUtIlfafQDP5UgxUCo1aYFyLYN/VIbdcY95ddvj0duKpJ5gy7 dnfn7fKzEs4J4hU/Y1CdhoXpe420B49Pr0ybgvcpmn6KXVczwCcLHFEs6ciSZ539 qXdlwHVPL0YMo5kre5ueux7nlGORNKVqPR5cwHKVBZvuRQ/aiZFSKH9kFjEUDyf4 3M7CFrnrFvpcufTSiEtipVDnxG0kckz2JLTBdIYyd5t53YaHxeAhzbZaMPSWN5F0 U+3y3G
Bug#994522: marked as done (crash in rendering strikethroughs)
Your message dated Fri, 17 Sep 2021 11:05:19 + with message-id and subject line Bug#994522: fixed in pango1.0 1.48.10+ds1-1 has caused the Debian Bug report #994522, regarding crash in rendering strikethroughs 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.) -- 994522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpango-1.0-0 Version: 1.48.9+ds1-2 Hello, when using the "Zim" application, it unexpectedly "crashes" with this error message: kernel: traps: zim[280987] trap divide error ip:7fd5a4f96f7b sp:7fff88fa0bf0 error:0 in libpango-1.0.so.0.4800.9[7fd5a4f75000+27000] Searching on the net I found that it was a bug in the libpango-1.0-0 package : https://github.com/zim-desktop-wiki/zim-desktop-wiki/issues/1548 https://gitlab.gnome.org/GNOME/pango/-/commit/71e39443b5e97fd5e8952c42369c9f59b3f393e3 This bug seems to be fixed in version 1.49 : https://gitlab.gnome.org/GNOME/pango/-/blob/main/NEWS#L43 is it possible to upgrade the debian package? Thank you in advance for your help. I'm using Debian unstable - kernel 5.10.0-8-amd64 -- Pascal --- End Message --- --- Begin Message --- Source: pango1.0 Source-Version: 1.48.10+ds1-1 Done: Simon McVittie We believe that the bug you reported is fixed in the latest version of pango1.0, 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 994...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated pango1.0 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: Fri, 17 Sep 2021 10:54:40 +0100 Source: pango1.0 Architecture: source Version: 1.48.10+ds1-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Simon McVittie Closes: 994522 Changes: pango1.0 (1.48.10+ds1-1) unstable; urgency=medium . * Team upload * New upstream release - Fix division by zero when rendering strikethrough (Closes: #994522) - pango-view: Support antialiasing freetype - pango-view: Use graphicsmagick instead of imagemagick to convert between formats * pango1.0-tools Suggests graphicsmagick for optional functionality Checksums-Sha1: 6f03591a56d8e7697ade091bb3bea69abc55be88 3765 pango1.0_1.48.10+ds1-1.dsc 013e476611c35990b7555c344623c97c13ad0403 721676 pango1.0_1.48.10+ds1.orig.tar.xz dfcae3c2cc928afa9ccc9ef570eb3765f651 46588 pango1.0_1.48.10+ds1-1.debian.tar.xz 519f56becab52fb18f9639078934fb1d19b80449 9122 pango1.0_1.48.10+ds1-1_source.buildinfo Checksums-Sha256: 1ac8a65a0b95998e6865a83a1169fbf0984aace60d0fd9e4a1d84730f270cfac 3765 pango1.0_1.48.10+ds1-1.dsc a91eccbeca5350c1eb32b06d0de9389f89ac9ec41345abf3ef1198d1ed22a10d 721676 pango1.0_1.48.10+ds1.orig.tar.xz 541a26b833fdb41f29aa9d2f912f12759eb655534a3d089791e457d26fc33fb2 46588 pango1.0_1.48.10+ds1-1.debian.tar.xz e8468ec7bca9a04bbc60a40aad0147785882536955b9e8ff6a0329025f02c1da 9122 pango1.0_1.48.10+ds1-1_source.buildinfo Files: 2f95289466aba99674467a842802f7cf 3765 libs optional pango1.0_1.48.10+ds1-1.dsc dfeef6f0c1c46e6888ed7eae68e023e1 721676 libs optional pango1.0_1.48.10+ds1.orig.tar.xz c0a9690466af2b475ba603aefa1e5a54 46588 libs optional pango1.0_1.48.10+ds1-1.debian.tar.xz f012fe07766906274e4833bb5ed784de 9122 libs optional pango1.0_1.48.10+ds1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmFEczoACgkQ4FrhR4+B TE9T1Q//YTfNfzD2zznOK60B5T6uT5Kw8NMzRKcqx80LXC++moR6D1k2ad+7N3yG vJ1k4RF1DBDbMNx43jEOkL2WCpnHidJ3khsuEl+bPiHKrZUbDn/WbXRd7hMUBAIB MlSo9tnn9/bH4XMyHOH3bBg2QK3I5j9zDFt3NZ2rNmX+djHr3RNsybFtZD2mqdcd c0KPc9A3fBiF10Kspy5VPCdG2D6uGx8EQH1f6/VUvJtXIwyWiA3lOxytP/XKPK4X Edth5lGwgXPjUDoeYL9VvxuUz9Vb496iuY6XRkvU398qY1aQodLNo+UZt1SgHNp2 dEXW4jGiIhcLnnWw4Bz2gVhfTAHmltMmbHbzKHrEmGRSOV7kxo6sxVPkTV8W7uL6 ILjiMT8yeNURgZgspdIr04qtkU59GBMnAV8exo6yHWjB16ryDnirKA8D5WuuBedf wr/7ENpWyqGXZVj7EwCdG1nXYQqBhJoW8U7DqmID0asv3rRaKrg8V6WacYbecmvy XAvQtL+G4mng62gY4MQpBSzw4uAZ6X90lLOo70vLQEgxnn05kD/XLVyG25yLNR5x SkuxrRyF90hi6ElXOdO7Msd3EhQg4Z46Qn0wTfXxScap3f7PHgUogboCJ6vI/b9K hkNHYYDm8LBgqQV1juQu
Bug#677824: marked as done (cmake-data: fails to find libgtest; libgtest-dev package no longer distributes statically compiled libraries)
Your message dated Fri, 17 Sep 2021 12:51:13 +0200 with message-id <20210917105113.2652775lpofoz...@mail.gaussglocke.de> and subject line Re: cmake-data: fails to find libgtest; libgtest-dev package no longer distributes statically compiled libraries has caused the Debian Bug report #677824, regarding cmake-data: fails to find libgtest; libgtest-dev package no longer distributes statically compiled libraries 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.) -- 677824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cmake-data Version: 2.8.8-3 Severity: important Dear Maintainer, * What led up to the situation? After the removal of static libraries in the libgtest-dev packages, /usr/share/cmake-2.8/Modules/FindGTest.cmake can no longer find the GTest libraries. find_package(GTest) does not find libgtest * What exactly did you do (or not do) that was effective (or ineffective)? Temporarily, I compiled the GTest libraries myself and put them in /usr/lib, but CMake should be able to detect the presence of the source directories and compile the library as needed * What was the outcome of this action? This fixed the problem temporarily, but it is not ideal, as GTest is a dependency of many build testing systems that rely on cmake to find the library. There is a similar bug for Ubuntu posted here: https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/969891 Thank you. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages cmake-data depends on: ii emacsen-common 2.0.3 cmake-data recommends no packages. cmake-data suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Control: notfound 3.21.2-1 Hi, On Sat, 18 Aug 2012 23:13:10 +0300 Modestas Vainius wrote: This is not easy to fix. Since 1.6.0, GTest has to be built from source (in /usr/src/) each time your application is built. However, since obviously CMake is used to build your application, it won't find GTest library at configure stage since it has not been built yet. At least since GTest 1.10.0, the static binaries are back in the libgtest-dev package, and the GTest detection code has been signifincantly overhauled. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature --- End Message ---
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> close #994526
Bug #994526 {Done: 4epteh...@list.ru} [celluloid] celluloid: Request new 0.21
upstream version
Bug 994526 is already marked as done; not doing anything.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
994526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#994526: marked as done (celluloid: Request new 0.21 upstream version)
Your message dated Fri, 17 Sep 2021 13:34:17 +0300 with message-id <1631874857.696365...@f126.i.mail.ru> and subject line has caused the Debian Bug report #994526, regarding celluloid: Request new 0.21 upstream version 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.) -- 994526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: celluloid Version: 0.20-2 Severity: important Dear Maintainer, new upstream 0.21 release version available on https://github.com/celluloid-player/celluloid.git. Please update the package for future versions (like a debian sid, ubuntu 21.10 impish). Thanks. -- System Information: Debian Release: 11.0 APT prefers impish APT policy: (500, 'impish') Architecture: amd64 (x86_64) Kernel: Linux 5.13.0-14-generic (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages celluloid depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-1 ii libc62.34-0ubuntu2 ii libcairo21.16.0-5ubuntu1 ii libepoxy01.5.7-1 ii libglib2.0-0 2.68.3-1ubuntu1 ii libgtk-3-0 3.24.30-1ubuntu1 ii libmpv1 0.32.0-3ubuntu1 ii libpango-1.0-0 1.48.9+ds1-1 ii libpangocairo-1.0-0 1.48.9+ds1-1 Versions of packages celluloid recommends: ii youtube-dl 2021.06.06-1 celluloid suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- It is very terrible that you publish personal data without permission. --- End Message ---
Bug#984351: marked as done (squid: ftbfs with GCC-11)
Your message dated Fri, 17 Sep 2021 10:22:17 + with message-id and subject line Bug#984351: fixed in squid 5.1-2 has caused the Debian Bug report #984351, regarding squid: ftbfs with GCC-11 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.) -- 984351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:squid Version: 4.13-5 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/squid_4.13-5_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] /bin/bash ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\"/etc/squid/squid.conf\" -DDEFAULT_SQUID_DATA_DIR=\"/usr/share/squid\" -DDEFAULT_SQUID_CONFIG_DIR=\"/etc/squid\" -I../.. -I../../include -I../../lib -I../../src -I../../include -isystem /usr/include/mit-krb5 -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libxml2 -Wall -Wpointer-arith -Wwrite-strings -Wcomments -Wshadow -Woverloaded-virtual -Werror -pipe -D_REENTRANT -I/usr/include/libxml2 -I/usr/include/p11-kit-1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o IntRange.lo IntRange.cc libtool: compile: g++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\"/etc/squid/squid.conf\" -DDEFAULT_SQUID_DATA_DIR=\"/usr/share/squid\" -DDEFAULT_SQUID_CONFIG_DIR=\"/etc/squid\" -I../.. -I../../include -I../../lib -I../../src -I../../include -isystem /usr/include/mit-krb5 -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libxml2 -Wall -Wpointer-arith -Wwrite-strings -Wcomments -Wshadow -Woverloaded-virtual -Werror -pipe -D_REENTRANT -I/usr/include/libxml2 -I/usr/include/p11-kit-1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c Address.cc -o Address.o >/dev/null 2>&1 libtool: compile: g++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\"/etc/squid/squid.conf\" -DDEFAULT_SQUID_DATA_DIR=\"/usr/share/squid\" -DDEFAULT_SQUID_CONFIG_DIR=\"/etc/squid\" -I../.. -I../../include -I../../lib -I../../src -I../../include -isystem /usr/include/mit-krb5 -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libxml2 -Wall -Wpointer-arith -Wwrite-strings -Wcomments -Wshadow -Woverloaded-virtual -Werror -pipe -D_REENTRANT -I/usr/include/libxml2 -I/usr/include/p11-kit-1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c IntRange.cc -fPIC -DPIC -o .libs/IntRange.o libtool: compile: g++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\"/etc/squid/squid.conf\" -DDEFAULT_SQUID_DATA_DIR=\"/usr/share/squid\" -DDEFAULT_SQUID_CONFIG_DIR=\"/etc/squid\" -I../.. -I../../include -I../../lib -I../../src -I../../include -isystem /usr/include/mit-krb5 -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libxml2 -Wall -Wpointer-arith -Wwrite-strings -Wcomments -Wshadow -Woverloaded-virtual -Werror -pipe -D_REENTRANT -I/usr/include/libxml2 -I/usr/include/p11-kit-1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c FilledChecklist.cc -o FilledChecklist.o >/dev/null 2>&1 /bin/bash ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -DDEFAULT_CONF
Bug#944442: marked as done (squid: Crashes when listening to audio stream over the Squid proxy)
Your message dated Fri, 17 Sep 2021 10:22:17 + with message-id and subject line Bug#943692: fixed in squid 5.1-2 has caused the Debian Bug report #943692, regarding squid: Crashes when listening to audio stream over the Squid proxy 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.) -- 943692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943692 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: squid Version: 4.6-1+deb10u1 Severity: normal Dear Maintainer, * What led up to the situation? Listen to an audio stream over the Squid proxy * What exactly did you do (or not do) that was effective (or ineffective)? Listening to audio streams using Parole on the same host as the Squid proxy * What was the outcome of this action? After ten or fifteen minutes of listening to an audio stream the Squid proxy crashes and restarts itself * What outcome did you expect instead? Working Squid proxy while listening to audio streams in current Debian/testing I discovered that listening to audio streams over the Squid network proxy using Parole on the same host let's Squid crash after ten or fifteen minutes of having the audio stream connection alive. Due to Squid crashes and restarts itself as seen in the Syslog all active network connections are dropped. That's how it came to my attention. I found the corresponding error message in /var/log/syslog and is as follows: Nov 10 05:01:14 g6 squid[27759]: assertion failed: stmem.cc:98: "lowestOffset () <= target_offset" Nov 10 05:01:14 g6 squid[2309]: Squid Parent: squid-1 process 27759 exited due to signal 6 with status 0 After this message Squid exists and starts up again. This bug is affecting the Debian version 4.6-1+deb10u1 of Squid. Here the Syslog entries: Nov 10 04:41:32 g6 squid[27759]: NETDB state saved; 120 entries, 12 msec Nov 10 04:59:12 g6 systemd[1]: /lib/systemd/system/squid.service:7: PIDFile= references a path below legacy directory /var/run/, updating /var/run/squid.pid → /run/squid.pid; please update the unit file accordingly. Nov 10 04:59:22 g6 systemd[1]: /lib/systemd/system/squid.service:7: PIDFile= references a path below legacy directory /var/run/, updating /var/run/squid.pid → /run/squid.pid; please update the unit file accordingly. Nov 10 04:59:33 g6 systemd[1]: /lib/systemd/system/squid.service:7: PIDFile= references a path below legacy directory /var/run/, updating /var/run/squid.pid → /run/squid.pid; please update the unit file accordingly. Nov 10 04:59:33 g6 systemd[1]: /lib/systemd/system/squid.service:7: PIDFile= references a path below legacy directory /var/run/, updating /var/run/squid.pid → /run/squid.pid; please update the unit file accordingly. Nov 10 05:01:14 g6 squid[27759]: assertion failed: stmem.cc:98: "lowestOffset () <= target_offset" Nov 10 05:01:14 g6 squid[2309]: Squid Parent: squid-1 process 27759 exited due to signal 6 with status 0 Nov 10 05:01:14 g6 squid[2309]: Squid Parent: (squid-1) process 18931 started Nov 10 05:01:14 g6 squid[18931]: Set Current Directory to /var/spool/squid Nov 10 05:01:14 g6 squid[18931]: Starting Squid Cache version 4.6 for x86_64-pc-linux-gnu... In all other use cases besides audio streams I could not find any error or bugs. It just happens by listening to an audio stream with Parole over the Squid network proxy. Thank you for your kind attention and reading this. Yours sincerely, Adrian Immanuel Kiess -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages squid depends on: ii adduser 3.118 ii libc62.29-2 ii libcap2 1:2.27-1 ii libcom-err2 1.45.4-1 ii libdb5.3 5.3.28+dfsg1-0.6 ii libdbi-perl 1.642-1+b2 ii libecap3 1.0.1-3.2+b1 ii libexpat12.2.9-1 ii libgcc1 1:9.2.1-17 ii libgnutls30 3.6.10-4 ii libgssapi-krb5-2 1.17-6 ii libkrb5-31.17-6 ii libldap-2.4-22.4.48+dfsg-1+b2 ii libltdl7 2.4.6-11 ii libnetfilter-conntrack3 1.0.7-2 ii libnettle6 3.4.1-1+b1 ii libpam0g 1.3.1
Bug#970025: marked as done (squid: configuration reads *~ files from /etc/squid/conf.d)
Your message dated Fri, 17 Sep 2021 10:22:17 + with message-id and subject line Bug#970025: fixed in squid 5.1-2 has caused the Debian Bug report #970025, regarding squid: configuration reads *~ files from /etc/squid/conf.d 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.) -- 970025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: squid Version: 4.6-1+deb10u4 Severity: normal Dear Maintainer, in /etc/squid/squid.conf the directive include /etc/squid/conf.d/* also loads backup files created by editors (files ending with "~"). That's at least surprising, to avoid unintended results it shouldd be changed to something like include /etc/squid/conf.d/*.conf Otherwise it's necessary to always check if the editor created a backup file and delete it before squid reads it's configuration. The location to patch would be in: debian/patches/0001-Default-configuration-file-for-debian.patch As the fix is trivial, I'm not including a patch. Regards, Carsten -- System Information: Debian Release: 10.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-10-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages squid depends on: ii adduser 3.118 ii libc62.28-10 ii libcap2 1:2.25-2 ii libcom-err2 1.44.5-1+deb10u3 ii libdb5.3 5.3.28+dfsg1-0.5 ii libdbi-perl 1.642-1+b1 ii libecap3 1.0.1-3.2 ii libexpat12.2.6-2+deb10u1 ii libgcc1 1:8.3.0-6 ii libgnutls30 3.6.7-4+deb10u5 ii libgssapi-krb5-2 1.17-3 ii libkrb5-31.17-3 ii libldap-2.4-22.4.47+dfsg-3+deb10u2 ii libltdl7 2.4.6-9 ii libnetfilter-conntrack3 1.0.7-1 ii libnettle6 3.4.1-1 ii libpam0g 1.3.1-5 ii libsasl2-2 2.1.27+dfsg-1+deb10u1 ii libstdc++6 8.3.0-6 ii libxml2 2.9.4+dfsg1-7+b3 ii logrotate3.14.0-4 ii lsb-base 10.2019051400 ii netbase 5.6 ii squid-common 4.6-1+deb10u4 Versions of packages squid recommends: ii ca-certificates 20200601~deb10u1 ii libcap2-bin 1:2.25-2 Versions of packages squid suggests: pn resolvconf pn smbclient pn squid-cgi pn squid-purge pn squidclient pn ufw pn winbind -- no debconf information --- End Message --- --- Begin Message --- Source: squid Source-Version: 5.1-2 Done: Luigi Gangitano We believe that the bug you reported is fixed in the latest version of squid, 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 970...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luigi Gangitano (supplier of updated squid 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: Fri, 17 Sep 2021 09:27:54 +0200 Source: squid Architecture: source Version: 5.1-2 Distribution: unstable Urgency: medium Maintainer: Luigi Gangitano Changed-By: Luigi Gangitano Closes: 943692 970025 984351 Changes: squid (5.1-2) unstable; urgency=medium . [ Amos Jeffries ] * New Upstream Release (Closes: #984351, #943692) . * debian/control - switch build-dep to libtdb-dev. libdb is deprecated - Bumped Standards-Version to 4.6.0, no change needed . * debian/patches/ - refresh patches for new version - fix 0001-Default-configuration-file-for-debian.patch (Closes: #970025) - add 0004-Change-default-Makefiles-for-debian.patch to fix FTBFS 'cp: cannot create regular file tests/stub_*.cc' . * debian/rules - remove basic_nis_auth helper . * Drop squid3 upgrade compatibility. Debian has not contained a squid3 package for at least two full release cycles. Checksums-Sha1: 98
Bug#943692: marked as done (squid: crash on bug #4823 : assertion failed: stmem.cc:98: "lowestOffset () <= target_offset")
Your message dated Fri, 17 Sep 2021 10:22:17 + with message-id and subject line Bug#943692: fixed in squid 5.1-2 has caused the Debian Bug report #943692, regarding squid: crash on bug #4823 : assertion failed: stmem.cc:98: "lowestOffset () <= target_offset" 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.) -- 943692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943692 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: squid Version: 4.6-1+deb10u1 Severity: important Tags: patch Dear Maintainer, Shortly after buster came out I updated the machines to it and after a little time we found out that squid had crashed with owestOffset () <= target_offset Amos was so kind to point me to bug #4823 on squid: https://bugs.squid-cache.org/show_bug.cgi?id=4823 And after adding the patch from http://www.squid-cache.org/Versions/v4/changesets/squid-4-10b699c30ef575d97e093d344ff85771654e7d8c.patch to the Debian source package and compiling it the system became stable and hasn't crashed anymore. I suggest we add that for the next point release. Thanks. -- System Information: Debian Release: 10.1 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'oldoldstable'), (500, 'unstable'), (500, 'oldstable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=gl_ES.UTF-8, LC_CTYPE=gl_ES.UTF-8 (charmap=UTF-8), LANGUAGE=gl_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages squid depends on: ii adduser 3.118 ii libc62.28-10 ii libcap2 1:2.25-2 ii libcom-err2 1.44.5-1+deb10u2 ii libdb5.3 5.3.28+dfsg1-0.5 ii libdbi-perl 1.642-1+b1 ii libecap3 1.0.1-3.2 ii libexpat12.2.6-2+deb10u1 ii libgcc1 1:8.3.0-6 ii libgnutls30 3.6.7-4 ii libgssapi-krb5-2 1.17-3 ii libkrb5-31.17-3 ii libldap-2.4-22.4.47+dfsg-3+deb10u1 ii libltdl7 2.4.6-9 ii libnetfilter-conntrack3 1.0.7-1 ii libnettle6 3.4.1-1 ii libpam0g 1.3.1-5 ii libsasl2-2 2.1.27+dfsg-1 ii libstdc++6 8.3.0-6 ii libxml2 2.9.4+dfsg1-7+b3 ii logrotate3.14.0-4 ii lsb-base 10.2019051400 ii netbase 5.6 ii squid-common 4.6-1+deb10u1 Versions of packages squid recommends: ii ca-certificates 20190110 ii libcap2-bin 1:2.25-2 Versions of packages squid suggests: pn resolvconf ii smbclient2:4.9.5+dfsg-5+deb10u1 pn squid-cgi pn squid-purge pn squidclient pn ufw pn winbind -- no debconf information --- End Message --- --- Begin Message --- Source: squid Source-Version: 5.1-2 Done: Luigi Gangitano We believe that the bug you reported is fixed in the latest version of squid, 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 943...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luigi Gangitano (supplier of updated squid 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: Fri, 17 Sep 2021 09:27:54 +0200 Source: squid Architecture: source Version: 5.1-2 Distribution: unstable Urgency: medium Maintainer: Luigi Gangitano Changed-By: Luigi Gangitano Closes: 943692 970025 984351 Changes: squid (5.1-2) unstable; urgency=medium . [ Amos Jeffries ] * New Upstream Release (Closes: #984351, #943692) . * debian/control - switch build-dep to libtdb-dev. libdb is deprecated - Bumped Standards-Version to 4.6.0, no change needed . * debian/patches/ - refresh patches for new version - fix 0001-Default-configuration-file-for-debian.patch (Closes: #970025) - add 0004-Change-default-Makefiles-for-debian.patch to fix FTBFS 'cp: cannot create regular file tests/stub_*.cc' . * debian/rules
Bug#993372: marked as done (atomicparsley: CVE-2021-37231 - stack-buffer overflow in APar_readX in src/extract.cpp)
Your message dated Fri, 17 Sep 2021 09:34:13 +
with message-id
and subject line Bug#993372: fixed in atomicparsley 20210715.151551.e7ad03a-1
has caused the Debian Bug report #993372,
regarding atomicparsley: CVE-2021-37231 - stack-buffer overflow in APar_readX
in src/extract.cpp
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.)
--
993372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: atomicparsley
Version: 0.9.6-2
Severity: important
Tags: patch security
https://github.com/wez/atomicparsley/issues/30
See also #993366
AtomicParsley, at the version in buster, bullseye, bookworm and sid causes a
stack
overflow when tested with the data file from the upstream bug report for
CVE-2021-37231
The upstream change can be backported to the version in Debian and the supplied
data file
no longer produces the crash with the attached patch.
-- System Information:
Debian Release: 10.10
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-17-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages atomicparsley depends on:
ii libc6 2.28-10
ii libgcc1 1:8.3.0-6
ii libstdc++6 8.3.0-6
ii zlib1g 1:1.2.11.dfsg-1
atomicparsley recommends no packages.
atomicparsley suggests no packages.
-- no debconf information
--- a/src/extracts.cpp
+++ b/src/extracts.cpp
@@ -1014,8 +1014,9 @@
track_info->type_of_track = VIDEO_TRACK;
}
if ( parsedAtoms[track->track_atom].AtomicLength > 34) {
- memset(track_info->track_hdlr_name, 0, 100);
- APar_readX(track_info->track_hdlr_name, isofile,
parsedAtoms[track->track_atom].AtomicStart + 32,
parsedAtoms[track->track_atom].AtomicLength - 32);
+ memset(track_info->track_hdlr_name, 0,
sizeof(track_info->track_hdlr_name));
+ APar_readX(track_info->track_hdlr_name, isofile,
parsedAtoms[track->track_atom].AtomicStart + 32,
+
std::min(sizeof(track_info->track_hdlr_name),parsedAtoms[track->track_atom].AtomicLength
- 32));
}
//codec section
--- a/src/AtomicParsley.h
+++ b/src/AtomicParsley.h
@@ -145,6 +145,7 @@
#endif
#include "util.h"
+#include
#define MAX_ATOMS 1024
#define MAXDATA_PAYLOAD 1256
--- End Message ---
--- Begin Message ---
Source: atomicparsley
Source-Version: 20210715.151551.e7ad03a-1
Done: Jonas Smedegaard
We believe that the bug you reported is fixed in the latest version of
atomicparsley, 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 993...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonas Smedegaard (supplier of updated atomicparsley 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: Fri, 17 Sep 2021 11:26:19 +0200
Source: atomicparsley
Architecture: source
Version: 20210715.151551.e7ad03a-1
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard
Changed-By: Jonas Smedegaard
Closes: 782187 987034 993366 993372
Changes:
atomicparsley (20210715.151551.e7ad03a-1) unstable; urgency=medium
.
[ upstream ]
* new release(s);
closes: bug#782187, thanks to Mathieu Malaterre;
closes: bug#993366, #993372, thanks to Neil Williams,
CVE-2021-37231 CVE-2021-37232
.
[ Jonas Smedegaard ]
* move maintenance to the Debian team on Salsa
* update git-buildpackage config:
+ use DEP-14 branches upstream/latest debian/latest
+ stop set explicit compression method
+ avoid any .git* files
* update watch file: track GitHub source
* update copyright info:
+ list GitHub as source
+ list GitHub issue tracker as preferred upstream contact
+ use Reference field (not License-Reference);
tighten lintian overrides
+ update coverage
* declare compliance with Debian Policy 4.6.0
* use debhelp
Bug#993366: marked as done (atomicparsley: CVE-2021-37232 - stack overflow in APar_read64 in src/extract.cpp)
Your message dated Fri, 17 Sep 2021 09:34:13 + with message-id and subject line Bug#993366: fixed in atomicparsley 20210715.151551.e7ad03a-1 has caused the Debian Bug report #993366, regarding atomicparsley: CVE-2021-37232 - stack overflow in APar_read64 in src/extract.cpp 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.) -- 993366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: atomicparsley Version: 0.9.6-2 Severity: important Tags: security upstream AtomicParsley at the version in buster, bullseye, bookworm and sid causes a stack overflow when tested with the data file from the upstream bug report for CVE-2021-37232: https://github.com/wez/atomicparsley/issues/32 The upstream specified in the Homepage and copyright information in the Debian package is no longer active and the CVE was reported against the new upstream. However, the vulnerable code still exists in the version of AtomicParsely in Debian and running the Debian package using the data file from the bug report does cause a stack overflow in the same way. (See #987034 which gives the updated location for the upstream.) Note that the fix applied to the new upstream does **not** fix the issue in the version in Debian, so more investigation will be required to get a fix. There is no uploader specified in the packaging at salsa, only the team alias. Maybe this package should be formally orphaned or removed? -- System Information: Debian Release: 10.10 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-17-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages atomicparsley depends on: ii libc6 2.28-10 ii libgcc1 1:8.3.0-6 ii libstdc++6 8.3.0-6 ii zlib1g 1:1.2.11.dfsg-1 atomicparsley recommends no packages. atomicparsley suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: atomicparsley Source-Version: 20210715.151551.e7ad03a-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of atomicparsley, 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 993...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated atomicparsley 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: Fri, 17 Sep 2021 11:26:19 +0200 Source: atomicparsley Architecture: source Version: 20210715.151551.e7ad03a-1 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Jonas Smedegaard Closes: 782187 987034 993366 993372 Changes: atomicparsley (20210715.151551.e7ad03a-1) unstable; urgency=medium . [ upstream ] * new release(s); closes: bug#782187, thanks to Mathieu Malaterre; closes: bug#993366, #993372, thanks to Neil Williams, CVE-2021-37231 CVE-2021-37232 . [ Jonas Smedegaard ] * move maintenance to the Debian team on Salsa * update git-buildpackage config: + use DEP-14 branches upstream/latest debian/latest + stop set explicit compression method + avoid any .git* files * update watch file: track GitHub source * update copyright info: + list GitHub as source + list GitHub issue tracker as preferred upstream contact + use Reference field (not License-Reference); tighten lintian overrides + update coverage * declare compliance with Debian Policy 4.6.0 * use debhelper compatibility level 13 (not 9); build-depend on debhelper-compat (not debhelper); stop build-depend explicitly on dh-autoreconf * simplify source helper script copyright-check * list GitHub as Homepage; closes: bug#987034, thanks to Brian Sammon * stop explicitly install executable; build-depend on cmake Checksums-Sha1: 3e8ebb05d06204237e844bbac910f54f2881da8a 2019 atomicp
Bug#987034: marked as done (display github page in Homepage tag)
Your message dated Fri, 17 Sep 2021 09:34:13 + with message-id and subject line Bug#987034: fixed in atomicparsley 20210715.151551.e7ad03a-1 has caused the Debian Bug report #987034, regarding display github page in Homepage tag 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.) -- 987034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: atomicparsley Version: 0.9.6-2 I'm basing this bug report primarily on the information seen at https://packages.debian.org/sid/atomicparsley That debian page says the homepage for atomicparsley is at http://atomicparsley.sourceforge.net/ but it would be better to point at https://github.com/wez/atomicparsley/releases, I think, especially considering that that is where you get the upstream for the dpkg. Best would be to point at both pages, but if you can only point at one, I think the github would be better. --- End Message --- --- Begin Message --- Source: atomicparsley Source-Version: 20210715.151551.e7ad03a-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of atomicparsley, 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 987...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated atomicparsley 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: Fri, 17 Sep 2021 11:26:19 +0200 Source: atomicparsley Architecture: source Version: 20210715.151551.e7ad03a-1 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Jonas Smedegaard Closes: 782187 987034 993366 993372 Changes: atomicparsley (20210715.151551.e7ad03a-1) unstable; urgency=medium . [ upstream ] * new release(s); closes: bug#782187, thanks to Mathieu Malaterre; closes: bug#993366, #993372, thanks to Neil Williams, CVE-2021-37231 CVE-2021-37232 . [ Jonas Smedegaard ] * move maintenance to the Debian team on Salsa * update git-buildpackage config: + use DEP-14 branches upstream/latest debian/latest + stop set explicit compression method + avoid any .git* files * update watch file: track GitHub source * update copyright info: + list GitHub as source + list GitHub issue tracker as preferred upstream contact + use Reference field (not License-Reference); tighten lintian overrides + update coverage * declare compliance with Debian Policy 4.6.0 * use debhelper compatibility level 13 (not 9); build-depend on debhelper-compat (not debhelper); stop build-depend explicitly on dh-autoreconf * simplify source helper script copyright-check * list GitHub as Homepage; closes: bug#987034, thanks to Brian Sammon * stop explicitly install executable; build-depend on cmake Checksums-Sha1: 3e8ebb05d06204237e844bbac910f54f2881da8a 2019 atomicparsley_20210715.151551.e7ad03a-1.dsc 5754ceff7859e41f3fa70d8c4471c0160bbb61fa 230214 atomicparsley_20210715.151551.e7ad03a.orig.tar.gz 57a9a3c1f3986fbfbcb9154e3d58e5017ced24e3 6192 atomicparsley_20210715.151551.e7ad03a-1.debian.tar.xz b149065041166268bc6eb2c8881d0c4b30178631 6973 atomicparsley_20210715.151551.e7ad03a-1_amd64.buildinfo Checksums-Sha256: 5a59bba7e13578c201d8206f81cff31cc8f54f4cd23fb5a0bd54bf92b6f27f31 2019 atomicparsley_20210715.151551.e7ad03a-1.dsc 546dcb5f3b625aff4f6bf22d27a0a636d15854fd729402a6933d31f3d0417e0d 230214 atomicparsley_20210715.151551.e7ad03a.orig.tar.gz f5f695784cdcef063ca304247be8bd2ad56629fdf2a257791594e851da1f1ac1 6192 atomicparsley_20210715.151551.e7ad03a-1.debian.tar.xz 76f30a27d54d17190b75629ea69578b5b5be236dff5ac12f5ba6b094954ccbc6 6973 atomicparsley_20210715.151551.e7ad03a-1_amd64.buildinfo Files: cdad9e09c2f4f2bb8b1f8edaec85 2019 video optional atomicparsley_20210715.151551.e7ad03a-1.dsc ff5fae0901aac980085b6ec6edf2f57d 230214 video optional atomicparsley_20210715.151551.e7ad03a.orig.tar.gz db6dcf1be352576dff969aeecf549b5f 6192 video optional atomicparsley_20210715.151551.e7ad03a-1.debian.tar.xz 3e55f83efde3e51782a597de63c0648a 6973 video
Bug#782187: marked as done (atomicparsley build on kFreeBSD)
Your message dated Fri, 17 Sep 2021 09:34:13 + with message-id and subject line Bug#782187: fixed in atomicparsley 20210715.151551.e7ad03a-1 has caused the Debian Bug report #782187, regarding atomicparsley build on kFreeBSD 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.) -- 782187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: atomicparsley Version: 0.9.2~svn110-4 Tags: patch upstream Forwarded: https://bitbucket.org/wez/atomicparsley/issue/27/high-cpu-on-freebsd user debian-...@lists.debian.org usertag -1 kfreebsd atomicparsley cannot be build on kFreeBSD because there is no definition for CDROM_LEADOUT. As per other reference it should simply be set to 0xAA. --- End Message --- --- Begin Message --- Source: atomicparsley Source-Version: 20210715.151551.e7ad03a-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of atomicparsley, 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 782...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated atomicparsley 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: Fri, 17 Sep 2021 11:26:19 +0200 Source: atomicparsley Architecture: source Version: 20210715.151551.e7ad03a-1 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Jonas Smedegaard Closes: 782187 987034 993366 993372 Changes: atomicparsley (20210715.151551.e7ad03a-1) unstable; urgency=medium . [ upstream ] * new release(s); closes: bug#782187, thanks to Mathieu Malaterre; closes: bug#993366, #993372, thanks to Neil Williams, CVE-2021-37231 CVE-2021-37232 . [ Jonas Smedegaard ] * move maintenance to the Debian team on Salsa * update git-buildpackage config: + use DEP-14 branches upstream/latest debian/latest + stop set explicit compression method + avoid any .git* files * update watch file: track GitHub source * update copyright info: + list GitHub as source + list GitHub issue tracker as preferred upstream contact + use Reference field (not License-Reference); tighten lintian overrides + update coverage * declare compliance with Debian Policy 4.6.0 * use debhelper compatibility level 13 (not 9); build-depend on debhelper-compat (not debhelper); stop build-depend explicitly on dh-autoreconf * simplify source helper script copyright-check * list GitHub as Homepage; closes: bug#987034, thanks to Brian Sammon * stop explicitly install executable; build-depend on cmake Checksums-Sha1: 3e8ebb05d06204237e844bbac910f54f2881da8a 2019 atomicparsley_20210715.151551.e7ad03a-1.dsc 5754ceff7859e41f3fa70d8c4471c0160bbb61fa 230214 atomicparsley_20210715.151551.e7ad03a.orig.tar.gz 57a9a3c1f3986fbfbcb9154e3d58e5017ced24e3 6192 atomicparsley_20210715.151551.e7ad03a-1.debian.tar.xz b149065041166268bc6eb2c8881d0c4b30178631 6973 atomicparsley_20210715.151551.e7ad03a-1_amd64.buildinfo Checksums-Sha256: 5a59bba7e13578c201d8206f81cff31cc8f54f4cd23fb5a0bd54bf92b6f27f31 2019 atomicparsley_20210715.151551.e7ad03a-1.dsc 546dcb5f3b625aff4f6bf22d27a0a636d15854fd729402a6933d31f3d0417e0d 230214 atomicparsley_20210715.151551.e7ad03a.orig.tar.gz f5f695784cdcef063ca304247be8bd2ad56629fdf2a257791594e851da1f1ac1 6192 atomicparsley_20210715.151551.e7ad03a-1.debian.tar.xz 76f30a27d54d17190b75629ea69578b5b5be236dff5ac12f5ba6b094954ccbc6 6973 atomicparsley_20210715.151551.e7ad03a-1_amd64.buildinfo Files: cdad9e09c2f4f2bb8b1f8edaec85 2019 video optional atomicparsley_20210715.151551.e7ad03a-1.dsc ff5fae0901aac980085b6ec6edf2f57d 230214 video optional atomicparsley_20210715.151551.e7ad03a.orig.tar.gz db6dcf1be352576dff969aeecf549b5f 6192 video optional atomicparsley_20210715.151551.e7ad03a-1.debian.tar.xz 3e55f83efde3e51782a597de63c0648a 6973 video optional atomicparsley_20210715.151551.e7ad03a-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmFEX6oACgkQLHwxRsGg ASGjOg/+JdHWd24TumMe
Bug#994525: marked as done (rubberband FTBFS on armel: selected processor does not support `fmrx r3,fpscr' in ARM mode)
Your message dated Fri, 17 Sep 2021 09:12:00 + with message-id and subject line Bug#994525: fixed in rubberband 1.9.2-3 has caused the Debian Bug report #994525, regarding rubberband FTBFS on armel: selected processor does not support `fmrx r3,fpscr' in ARM mode 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.) -- 994525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994525 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rubberband Version: 1.9.2-1 Severity: serious Tags: ftbfs patch https://buildd.debian.org/status/fetch.php?pkg=rubberband&arch=armel&ver=1.9.2-2&stamp=1631846256&raw=0 ... FAILED: librubberband.a.p/src_system_sysutils.cpp.o c++ -Ilibrubberband.a.p -I. -I.. -I../rubberband -I../src -fdiagnostics-color=always -DNDEBUG -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -std=c++14 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -DUSE_BUILTIN_FFT -DHAVE_LIBSAMPLERATE -DUSE_PTHREADS -DHAVE_POSIX_MEMALIGN -MD -MQ librubberband.a.p/src_system_sysutils.cpp.o -MF librubberband.a.p/src_system_sysutils.cpp.o.d -o librubberband.a.p/src_system_sysutils.cpp.o -c ../src/system/sysutils.cpp /tmp/ccANy3Ml.s: Assembler messages: /tmp/ccANy3Ml.s:295: Error: selected processor does not support `fmrx r3,fpscr' in ARM mode /tmp/ccANy3Ml.s:298: Error: selected processor does not support `fmxr fpscr,r3' in ARM mode ... Fix is attached. Description: Fix FTBFS on armel Don't initialise the FPU when it is not available. Author: Adrian Bunk --- rubberband-1.9.2.orig/src/system/sysutils.cpp +++ rubberband-1.9.2/src/system/sysutils.cpp @@ -189,7 +189,7 @@ void system_specific_initialise() fesetenv(FE_DFL_DISABLE_DENORMS_ENV); #endif #endif -#if defined __ARMEL__ +#if defined(__ARMEL__) && !defined(__SOFTFP__) // ARM32 static const unsigned int x = 0x04086060; static const unsigned int y = 0x0300; --- End Message --- --- Begin Message --- Source: rubberband Source-Version: 1.9.2-3 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of rubberband, 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 994...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated rubberband 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: Fri, 17 Sep 2021 10:29:13 +0200 Source: rubberband Architecture: source Version: 1.9.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 994525 Changes: rubberband (1.9.2-3) unstable; urgency=medium . * debian/patches: Fix FTBFS on armel. Thanks to Adrian Bunk for the patch (Closes: 994525) Checksums-Sha1: b74fcc9c651506773dbde97dd81617190fe98172 2401 rubberband_1.9.2-3.dsc 2ad39759a2e689004681b68df17b07d5236ce69b 8868 rubberband_1.9.2-3.debian.tar.xz Checksums-Sha256: 036a671d6f3684754bd4cf5c974ae957ecc80918b20beb82237c1dbbd3bf2376 2401 rubberband_1.9.2-3.dsc 628ed671a7b47ba5b29eb99a9bac8196e267bdc80ef505dfb3ac8f7758d8ac28 8868 rubberband_1.9.2-3.debian.tar.xz Files: 123eacbcf45a3045c271beb0d2615dab 2401 sound optional rubberband_1.9.2-3.dsc ad2731e7ae7fe419b628e3be8217e797 8868 sound optional rubberband_1.9.2-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmFEUp4VHHNyYW1hY2hl ckBkZWJpYW4ub3JnAAoJEGny/FFupxmTqE8P/3L4c1Ctm/apkDi08Rqv8Qhh3x/7 86Rkvx+p3P3jTlIF84bxI2+QKi+7bSOl2nUKpUE4P2ALrzV/ab8PtBKB8k+EwL8X FZbMJ0aG8yEXLmWUQLraHhEGto5j4ofoeZ4QwZK+a3wZDmMlTnV7E37vkAJeI26W eKrJMo3ojNJFG/dEm8jTQAZ6GYFNrMN5ko6GGK2Id8qy/Jc91VOexJxCz8vIxg1y 33ji7nwNAM0aK1ITA3OniSFt53GceHZZOhMS5YGXk/kb0rRBd6DyDZUjSsd3H5tU /GRF9cDDqOztv6nBQogtnxwmqMln3i1bhcS1StpVk/q4SgvEKl2hq1zk+zOCQeCZ 2dK/xQjIvPzO+4/1aKZEVfByobgFIxH7qb4y9bu/yYReJuLVq5R/HkoQ3FtAAZd/ mYdVlqUjd/YuA+44KtLytZLxYj9cCLkINh5B3xyF8tG+qKWSrCUGJyp8YbKE7PRL BzVmromPE8h3U12izWObKT9ZZ3dWd6moM0haeQ9k5PQW7+nnTLk9W/kQd+ZcOeMT eqOrQPxMvtPS1onBC37qtjxUR0wh2T16+eNsEtsK0djRrz0Tdd1RT4QuqXBj1ak5 F7XzlpeJAIRBCXdYEXgq
Bug#888096: marked as done (archive.debian.org: add wheezy to archive.d.o)
Your message dated Fri, 17 Sep 2021 11:10:26 +0200 with message-id and subject line Re: Bug#888096: archive.debian.org: add wheezy to archive.d.o has caused the Debian Bug report #888096, regarding archive.debian.org: add wheezy to archive.d.o 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.) -- 888096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mirrors Severity: normal Please import the wheezy suites from ftp.d.o to archive.d.o: - wheezy - wheezy-backports - wheezy-backports-sloppy - wheezy-proposed-updates - wheezy-updates This would allow us to remove the non-LTS architectures from the main archive, freeing a bit space on the main mirror network. Do *not* import the wheezy suite from security.d.o yet as it still gets updates for a few more months. Ansgar --- End Message --- --- Begin Message --- 19:29 < jcristau> ansgar: what's the status of #888096? should that be closed? 20:30 < ansgar> jcristau: Yes, wheezy should be done (since 2 years). Closing. On Mon, Apr 20, 2020 at 05:22:21PM +0200, Julien Cristau wrote: > Control: tag -1 moreinfo > > On Tue, Jan 23, 2018 at 11:10:50AM +0100, Ansgar Burchardt wrote: > > Package: mirrors > > Severity: normal > > > > Please import the wheezy suites from ftp.d.o to archive.d.o: > > > > - wheezy > > - wheezy-backports > > - wheezy-backports-sloppy > > - wheezy-proposed-updates > > - wheezy-updates > > > > This would allow us to remove the non-LTS architectures from the main > > archive, freeing a bit space on the main mirror network. > > > > Do *not* import the wheezy suite from security.d.o yet as it still > > gets updates for a few more months. > > > Hi, > > in the mean time this has happened for the first 3 suites. AFAICT > -updates and -proposed-updates are gone though, do we need to do > something there? > > Cheers, > Julien--- End Message ---
Bug#980859: marked as done (sylpheed: Hang when displaying specific message)
Your message dated Fri, 17 Sep 2021 09:26:33 +0200 with message-id and subject line Re: Bug #980859 has caused the Debian Bug report #980859, regarding sylpheed: Hang when displaying specific message 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.) -- 980859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980859 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sylpheed Version: 3.7.0-8 Severity: important X-Debbugs-Cc: wojciech_m...@poczta.onet.pl Dear Maintainer, * What led up to the situation? Tried to read a typical Github notification email. * What exactly did you do (or not do) that was effective (or ineffective)? Clicked on the unread message in the message list window. * What was the outcome of this action? Sylpheed became unreportable at all, CPU usage was 100%. I had to kill the program manually from a command line. * What outcome did you expect instead? Just displaying a mail. The message which caused this strange behaviour is a regular Github notification. What I did before reporting the bug: 1. I found that message in the mail folder and tried to distill the minimal example by removing headers or body lines, but didn't found any obvious pattern. 2. I compiled Sylpheed from Debian sources and then run inside gdb. Seems it's some bug inside GTK, like endless loop of signals. I can break the program (Ctrl-C), inspect the backtrace and continue, and then break again. Please see the sample backtrace below: the last function from Sylpheed is `summary_select_row`, then only GTK functions are being called. What I observed is that rarely the mail is displayed on the screen, and then program stops responding. Usually there's blank message window. I have a custom GTK theme set via `export GTK_THEME=Blackbird`. Please drop me a line and I'll share with the maintainer & developers the problematic message. It contains mails, logins, names, etc., don't want to publish them in the bug report. best regards Wojciech Muła Thread 1 "sylpheed" received signal SIGINT, Interrupt. 0x7791e6e4 in pango_script_iter_next () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 (gdb) bt #0 0x7791e6e4 in pango_script_iter_next () at /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 #1 0x7791e8b6 in () at /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 #2 0x77909994 in () at /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 #3 0x7790b124 in pango_itemize_with_base_dir () at /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 #4 0x77914366 in () at /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 #5 0x77916249 in () at /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 #6 0x77d3d858 in gtk_text_layout_get_line_display () at /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #7 0x77d3e4e2 in () at /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #8 0x77d22e03 in () at /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #9 0x77d3ce48 in gtk_text_layout_validate_yrange () at /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #10 0x77d4d5bb in () at /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #11 0x77d4e61c in () at /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #12 0x77d4ec31 in () at /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #13 0x778a3fc4 in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #14 0x778b609a in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #15 0x778bc69f in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #16 0x778bcc0f in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #17 0x77db3163 in gtk_widget_size_allocate () at /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #18 0x77cf2d7a in () at /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #19 0x778a3fc4 in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #20 0x778b609a in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #21 0x778bc69f in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #22 0x778bcc0f in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #23 0x77db3163 in gtk_widget_size_allocate () at /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #24 0x77bdb6e4 in () at /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #25 0x778a3fc4 in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #26 0x778b60
