Processed (with 1 error): Re: Bug#949703: thunderbird doesn' start on Sid
Processing control commands: > forcemerge 949703 949695 Bug #949703 [thunderbird] thunderbird doesn' start on Sid Unable to merge bugs because: package of #949695 is 'src:thunderbird' not 'thunderbird' Failed to forcibly merge 949703: Did not alter merged bugs. -- 949695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949695 949703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938478: marked as done (shortuuid: Python2 removal in sid/bullseye)
Your message dated Fri, 24 Jan 2020 05:36:10 + with message-id and subject line Bug#938478: fixed in shortuuid 0.5.0-1.1 has caused the Debian Bug report #938478, regarding shortuuid: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 938478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:shortuuid Version: 0.5.0-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:shortuuid If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: shortuuid Source-Version: 0.5.0-1.1 We believe that the bug you reported is fixed in the latest version of shortuuid, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated shortuuid 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, 24 Jan 2020 00:05:18 -0500 Source: shortuuid Architecture: source Version: 0.5.0-1.1 Distribution: unstable Urgency: medium Maintainer: Kouhei Maeda Changed-By: Sandro Tosi Closes: 938478 Changes: shortuuid (0.5.0-1.1) unstable; urgency=medium . * Non-maintainer upload. * Drop python2 support; Closes: #938478 Checksums-Sha1: 4f168055a7e54c882fc2a3f7c51fa98579d36c3c 1832 shortuuid_0.5.0-1.1.dsc cc1aa12ca3da8087a4dc5b0a3203d5c318a6cb52 3140 shortuuid_0.5.0-1.1.debian.tar.xz 2275107d7c23774e11ae9283110d1ed531ecde01 6418 shortuuid_0.5.0-1.1_source.buildinfo Checksums-Sha256: a0f93f2ffd8ed083b4a61945a96eda42d9b52594e91955fcbf7ae4c325b1a70e 1832 shortuuid_0.5.0-1.1.dsc 30e7a4171890c26b740e860a14f0e219947f1d22c99da4ed7e7886f924f57ce5 3140 shortuuid_0.5.0-1.1.debian.tar.xz e46e63ba50c5401ae932b1a661730b362a8f45f475be52976878c6b16f8086c9 6418 shortuuid_0.5.0-1.1_source.buildinfo Files: b05318f589fbce5595babd95b4508298 1832 python
Processed: shortuuid: diff for NMU version 0.5.0-1.1
Processing control commands: > tags 938478 + patch Bug #938478 [src:shortuuid] shortuuid: Python2 removal in sid/bullseye Added tag(s) patch. -- 938478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938478: shortuuid: diff for NMU version 0.5.0-1.1
Control: tags 938478 + patch
Dear maintainer,
I've prepared an NMU for shortuuid (versioned as 0.5.0-1.1). The diff
is attached to this message.
Consider maintaining this package with the DPMT
Regards.
diff -Nru shortuuid-0.5.0/debian/changelog shortuuid-0.5.0/debian/changelog
--- shortuuid-0.5.0/debian/changelog 2017-09-16 04:22:09.0 -0400
+++ shortuuid-0.5.0/debian/changelog 2020-01-24 00:05:18.0 -0500
@@ -1,3 +1,10 @@
+shortuuid (0.5.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop python2 support; Closes: #938478
+
+ -- Sandro Tosi Fri, 24 Jan 2020 00:05:18 -0500
+
shortuuid (0.5.0-1) unstable; urgency=medium
* New upstream release
diff -Nru shortuuid-0.5.0/debian/control shortuuid-0.5.0/debian/control
--- shortuuid-0.5.0/debian/control 2017-09-16 04:22:01.0 -0400
+++ shortuuid-0.5.0/debian/control 2020-01-24 00:01:34.0 -0500
@@ -4,29 +4,13 @@
Maintainer: Kouhei Maeda
Build-Depends: debhelper (>= 8.0.0),
dh-python,
- python-all (>= 2.6),
- python-setuptools,
- python-pep8,
python3-all (>= 3.2),
python3-setuptools,
python3-pep8,
quilt
Standards-Version: 4.0.0
-X-Python-Version: >= 2.6
-X-Python3-Version: >= 3.2
Homepage: https://github.com/stochastic-technologies/shortuuid/
-Package: python-shortuuid
-Architecture: all
-Provides: ${python:Provides}
-Depends: ${python:Depends}, ${misc:Depends}
-Description: generates concise, unambiguous, URL-safe UUIDs
- Often, one needs to use non-sequential IDs in places where users will see them,
- but the IDs must be as concise and easy to use as possible. shortuuid solves
- this problem by generating uuids using Python's built-in uuid module and then
- translating them to base57 using lowercase and uppercase letters and digits,
- and removing similar-looking characters such as l, 1, I, O and 0.
-
Package: python3-shortuuid
Architecture: all
Depends: ${python3:Depends}, ${misc:Depends}
diff -Nru shortuuid-0.5.0/debian/rules shortuuid-0.5.0/debian/rules
--- shortuuid-0.5.0/debian/rules 2017-09-16 04:07:56.0 -0400
+++ shortuuid-0.5.0/debian/rules 2020-01-24 00:00:31.0 -0500
@@ -1,35 +1,7 @@
#!/usr/bin/make -f
-# -*- makefile -*-
-# Uncomment this to turn on verbose mode.
-#export DH_VERBOSE=1
%:
- dh $@ --with python2,python3
-
-override_dh_auto_build:
- set -e ; \
- for py in 2.7 $(shell py3versions -vr); do \
- python$$py setup.py build --build-base=build$$py; \
- done
+ dh $@ --with python3 --buildsystem=pybuild
override_dh_auto_test:
- set -e ; \
- python2.7 build2.7/lib.*-2.7/shortuuid/tests.py
- for py in $(shell py3versions -vr); do \
- python$$py build$$py/lib/shortuuid/tests.py; \
- done
-
-override_dh_auto_install:
- python setup.py install --no-compile -O0 --install-layout=deb \
- --root $(CURDIR)/debian/python-shortuuid && \
- python3 setup.py install --no-compile -O0 --install-layout=deb \
- --root $(CURDIR)/debian/python3-shortuuid
-
-override_dh_auto_clean:
- dh_clean
- for py in 2.7 $(shell py3versions -vr); do \
- python$$py setup.py clean --build-temp=build && \
- python$$py setup.py clean --build-temp=build$$py; \
- done
- find $(CURDIR) -name "*.pyc" -delete
-
+PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS='{interpreter} {build_dir}/shortuuid/tests.py' dh_auto_test
diff -Nru shortuuid-0.5.0/debian/uscan.log shortuuid-0.5.0/debian/uscan.log
--- shortuuid-0.5.0/debian/uscan.log 2016-02-13 00:43:44.0 -0500
+++ shortuuid-0.5.0/debian/uscan.log 1969-12-31 19:00:00.0 -0500
@@ -1,4 +0,0 @@
-# uscan log
-# == shortuuid-0.4.3.tar.gz --> shortuuid_0.4.3.orig.tar.gz (same)
-4f70db8174c0b7b8cad36de48b529947 shortuuid-0.4.3.tar.gz
-4f70db8174c0b7b8cad36de48b529947 shortuuid_0.4.3.orig.tar.gz
Bug#936511: marked as done (feedparser: Python2 removal in sid/bullseye)
Your message dated Fri, 24 Jan 2020 04:19:45 + with message-id and subject line Bug#936511: fixed in feedparser 5.2.1-2 has caused the Debian Bug report #936511, regarding feedparser: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 936511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936511 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:feedparser Version: 5.2.1-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:feedparser If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: feedparser Source-Version: 5.2.1-2 We believe that the bug you reported is fixed in the latest version of feedparser, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated feedparser package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 23 Jan 2020 23:07:16 -0500 Source: feedparser Architecture: source Version: 5.2.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Sandro Tosi Closes: 936511 Changes: feedparser (5.2.1-2) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org * d/copyright: Use https protocol in Format field * d/changelog: Remove trailing whitespaces * d/control: Remove ancient X-Python-Version field * d/control: Remove ancient X-Python3-Version field * Use debhelper-compat instead of debian/compat. . [ Carl Suster ] * d/control: Remove myself from Uploaders . [ Debian Janitor ] * Bump debhelper from old 10 to 12. * Set upstream metadata fields: Bug-Database, Repository, Repository- Browse. . [ Sandro Tosi ] * Drop python2 support; Closes: #936511 Checksums-Sha1: 45b29b47d4f6a344dd0f26bc13f3a197b38f21f8 2019 feedparser_5.2.1-2.dsc
Bug#936511: marked as pending in feedparser
Control: tag -1 pending Hello, Bug #936511 in feedparser reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/feedparser/commit/32b25ec14dcb33fffa0ad693679638e215a7383a Drop python2 support; Closes: #936511 (this message was generated automatically) -- Greetings https://bugs.debian.org/936511
Processed: Bug#936511 marked as pending in feedparser
Processing control commands: > tag -1 pending Bug #936511 [src:feedparser] feedparser: Python2 removal in sid/bullseye Added tag(s) pending. -- 936511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936511 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#874915: heimdall-flash: package appears to be a salvaging candidate
Hi Moritz, Moritz Mühlenhoff writes: > On Tue, Dec 03, 2019 at 10:53:54PM +0100, Moritz Mühlenhoff wrote: >> >> I suggest that you go ahead with the salvaging, we're closing in on >> the Qt4 removal and we'll ask for removal of the remaining rdeps in >> about two months. > > Status update: Qt4 has now been droppped from testing, qt4 will be removed > from unstable by end of February (along with the remaining rdeps (currently > 15)). > > Nicholas, since you're a DM; if you need a sponsor for the initial upload > after adopting it, feel free to ping me. Yes, thank you, I would appreciate your review and sponsorship! This package is ready for an initial review. I have created a temporary repo here: https://salsa.debian.org/sten-guest/heimdall-flash and hope you will also be willing to create the project under debian namespace (the new collab-maint). Please don't create it before the package is ready for sponsorship though, because I haven't yet finalised the git repo format (see below for why). Here is the lint I believe may be a priority for this upload: W: heimdall-flash: appstream-metadata-missing-modalias-provide lib/udev/rules.d/60-heimdall-flash.rules W: heimdall-flash: appstream-metadata-missing-modalias-provide lib/udev/rules.d/60-heimdall-flash.rules match rule usb:v04E8p6601d* W: heimdall-flash: appstream-metadata-missing-modalias-provide lib/udev/rules.d/60-heimdall-flash.rules match rule usb:v04E8p685Dd* W: heimdall-flash: appstream-metadata-missing-modalias-provide lib/udev/rules.d/60-heimdall-flash.rules match rule usb:v04E8p68C3d* 1. I'm not sure what the correct approach is here, because we shouldn't suggest that a new user install a custom firmware to their device, just because they plugged it in. eg: a user who plugs in their phone or tablet to copy photos off of it shouldn't be presented (due to appstream) with software to replace their devices' OS! 2. I believe that many more devices are supported than this, and a list of USB manufacturer:product IDs feel like something that should be maintained upstream and not specifically in Debian. Moving forward, I suspect that a wiki page somewhere would be useful for collecting success/failure reports from users for a wider range of devices. W: heimdall-flash: manpage-has-bad-whatis-entry usr/share/man/man1/heimdall.1.gz I attempted to fix this with more comprehensive txt2man arguments, and concede that there are (arguably jarring) cosmetic issues with the resulting man page. I plan to work with upstream to provide the README in a format suitable for conversion to groff (eg: RST), so that one file can act as both README and man page source. OTTO upstream, I'm planning to also expand my CMake knowledge enough to fix the deficiencies in the existing CMakeLists.txt; Lisandro pointed me in the right direction for this :-) W: heimdall-flash source: source-contains-prebuilt-windows-binary Win32/Drivers/zadig.exe I haven't decided whether to go with a custom merge driver, gbp + d/copyright "Excluded-Files" + uscan, or something else. Please let me know what you'd prefer! I: heimdall-flash: hardening-no-bindnow usr/bin/heimdall I: heimdall-flash-frontend: hardening-no-bindnow usr/bin/heimdall-frontend In this case, I erred on the side of caution and left the "DEB_CFLAGS_MAINT_APPEND" added by Steve Langasek intact. I'd prefer to defer these changes to the next upload. Thank you for periodically asking me to check in, I appreciate the reminders and they motivate me to get the work done, and to do it well :-) Regards, Nicholas signature.asc Description: PGP signature
Processed: py2removal bugs severity updates - 2020-01-24 03:35:32.017793+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # and https://lists.debian.org/debian-python/2019/12/msg00076.html > # mail threads for more details on this severity update > # python-feedparser is a module and has 0 external rdeps or not in testing > severity 936511 serious Bug #936511 [src:feedparser] feedparser: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 936511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936511 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937969: marked as done (python-omemo-backend-signal: Python2 removal in sid/bullseye)
Your message dated Fri, 24 Jan 2020 02:51:54 + with message-id and subject line Bug#937969: fixed in python-omemo-backend-signal 0.2.3-1.1 has caused the Debian Bug report #937969, regarding python-omemo-backend-signal: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 937969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-omemo-backend-signal Version: 0.2.3-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-omemo-backend-signal If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-omemo-backend-signal Source-Version: 0.2.3-1.1 We believe that the bug you reported is fixed in the latest version of python-omemo-backend-signal, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated python-omemo-backend-signal package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 23 Jan 2020 21:04:01 -0500 Source: python-omemo-backend-signal Architecture: source Version: 0.2.3-1.1 Distribution: unstable Urgency: medium Maintainer: Debian XMPP Maintainers Changed-By: Sandro Tosi Closes: 937969 Changes: python-omemo-backend-signal (0.2.3-1.1) unstable; urgency=medium . * Non-maintainer upload. * Drop python2 support; Closes: #937969 Checksums-Sha1: b1de8f2192df5ae0ef04addfa72f8deaed4b563a 2284 python-omemo-backend-signal_0.2.3-1.1.dsc 0597d0539289b2f67786b6cd76753cf80780a63e 2308 python-omemo-backend-signal_0.2.3-1.1.debian.tar.xz 4900ef7582dcd2eeea4cdecb5cf532e769667e06 6408 python-omemo-backend-signal_0.2.3-1.1_source.buildinfo Checksums-Sha256: 41079ae4254808c42b6659cf80b05fc04cac43e70a0b6229cb7506656ec44fb7 2284 python-omemo-backend-signal_0.2.3-1.1.dsc
Bug#937969: python-omemo-backend-signal: diff for NMU version 0.2.3-1.1
Control: tags 937969 + patch
Dear maintainer,
I've prepared an NMU for python-omemo-backend-signal (versioned as 0.2.3-1.1).
The diff
is attached to this message.
Regards.
diff -Nru python-omemo-backend-signal-0.2.3/debian/changelog python-omemo-backend-signal-0.2.3/debian/changelog
--- python-omemo-backend-signal-0.2.3/debian/changelog 2019-01-16 12:27:58.0 -0500
+++ python-omemo-backend-signal-0.2.3/debian/changelog 2020-01-23 21:04:01.0 -0500
@@ -1,3 +1,10 @@
+python-omemo-backend-signal (0.2.3-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop python2 support; Closes: #937969
+
+ -- Sandro Tosi Thu, 23 Jan 2020 21:04:01 -0500
+
python-omemo-backend-signal (0.2.3-1) unstable; urgency=medium
* Initial package (Closes: #919367)
diff -Nru python-omemo-backend-signal-0.2.3/debian/control python-omemo-backend-signal-0.2.3/debian/control
--- python-omemo-backend-signal-0.2.3/debian/control 2019-01-16 12:27:58.0 -0500
+++ python-omemo-backend-signal-0.2.3/debian/control 2020-01-23 21:03:47.0 -0500
@@ -6,13 +6,6 @@
Build-Depends: debhelper (>= 11),
dh-python,
protobuf-compiler,
- python-all,
- python-cryptography,
- python-doubleratchet,
- python-omemo,
- python-protobuf,
- python-setuptools,
- python-x3dh,
python3-all,
python3-cryptography,
python3-doubleratchet,
@@ -26,17 +19,6 @@
Vcs-Git: https://salsa.debian.org/xmpp-team/python-omemo-backend-signal.git
Vcs-Browser: https://salsa.debian.org/xmpp-team/python-omemo-backend-signal
-Package: python-omemo-backend-signal
-Architecture: all
-Depends: ${misc:Depends},
- ${python:Depends},
-Description: Python 2 backend for python-omemo with libsignal compatibility
- This library implements a backend for python-omemo offering
- compatibility with libsignal (C, Java, JavaScript). Look at
- python-omemo for further usage information.
- .
- This package provides the Python 2.7 module.
-
Package: python3-omemo-backend-signal
Architecture: all
Depends: ${misc:Depends},
diff -Nru python-omemo-backend-signal-0.2.3/debian/rules python-omemo-backend-signal-0.2.3/debian/rules
--- python-omemo-backend-signal-0.2.3/debian/rules 2019-01-16 10:52:19.0 -0500
+++ python-omemo-backend-signal-0.2.3/debian/rules 2020-01-23 21:03:57.0 -0500
@@ -3,7 +3,7 @@
export PYBUILD_NAME=omemo_backend_signal
%:
- dh $@ --with python2,python3 --buildsystem=pybuild
+ dh $@ --with python3 --buildsystem=pybuild
override_dh_auto_build:
cd omemo_backend_signal && $(MAKE)
Processed: python-omemo-backend-signal: diff for NMU version 0.2.3-1.1
Processing control commands: > tags 937969 + patch Bug #937969 [src:python-omemo-backend-signal] python-omemo-backend-signal: Python2 removal in sid/bullseye Added tag(s) patch. -- 937969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937675: marked as done (python-csa: Python2 removal in sid/bullseye)
Your message dated Thu, 23 Jan 2020 20:42:39 -0500 with message-id and subject line Re: python-csa: Python2 removal in sid/bullseye has caused the Debian Bug report #937675, regarding python-csa: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 937675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-csa Version: 0.1.0-1.2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-csa If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.1.10-1 On Fri, 30 Aug 2019 07:37:58 + Matthias Klose wrote: > Package: src:python-csa > Version: 0.1.0-1.2 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal https://tracker.debian.org/news/1096155/accepted-python-csa-0110-1-source-amd64-into-unstable-unstable/--- End Message ---
Processed: severity of 949674 is grave
Processing commands for cont...@bugs.debian.org: > severity 949674 grave Bug #949674 [firefox] firefox: Firefox 72.0.2-1 crash on launch. Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 949674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949674 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#944774: marked as done (Support python 3.8)
Your message dated Thu, 23 Jan 2020 22:50:05 +
with message-id
and subject line Bug#944774: fixed in gpgme1.0 1.13.1-2
has caused the Debian Bug report #944774,
regarding Support python 3.8
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.)
--
944774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-gpg
Version: 1.13.1-1
--- End Message ---
--- Begin Message ---
Source: gpgme1.0
Source-Version: 1.13.1-2
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 944...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Kahn Gillmor (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: SHA256
Format: 1.8
Date: Thu, 23 Jan 2020 17:11:25 -0500
Source: gpgme1.0
Architecture: source
Version: 1.13.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuPG Maintainers
Changed-By: Daniel Kahn Gillmor
Closes: 943111 943390 944774
Changes:
gpgme1.0 (1.13.1-2) unstable; urgency=medium
.
* rebuild, pulling in python 3.8 (Closes: #944774)
- requires patching upstream, changes to cross-building logic
* Update standards version to 4.4.1, no changes needed.
* add buildtime and runtime tests for platform time limits
* remove python-gpg autopkgtest entirely (Closes: #943390, #943111)
* update lintian-overrides for untracked C++ symbols
* fix json tests
* d/control: drop unused ${shlibs:Depends} from libgpgmepp-dev
* d/control: added ${python3:Versions} to python3-gpg
Checksums-Sha1:
9bbddb05ec952566ee04383b0f6ef2ed73bff8b6 2258 gpgme1.0_1.13.1-2.dsc
1ca56c058541a8318bb988558664bb4a49efe6a4 19768 gpgme1.0_1.13.1-2.debian.tar.xz
04add7c3f8d33e76b90e135f95ba2cc467693a60 18420
gpgme1.0_1.13.1-2_amd64.buildinfo
Checksums-Sha256:
81d8a2db4746c8fdfb3b9ff2bf18ddc0e1df74d23f0cad6db3c992e4afd5a783 2258
gpgme1.0_1.13.1-2.dsc
bddc4d6725af83c38a1b9953683bb9c2e40049867bef205e428cea307207925d 19768
gpgme1.0_1.13.1-2.debian.tar.xz
2664dcdd10cd7de57f0a3c253f2b4c690f04a388cfb53065b480c6ca9493f40e 18420
gpgme1.0_1.13.1-2_amd64.buildinfo
Files:
9e98e39414139a0715bc591a009b5f1b 2258 libs optional gpgme1.0_1.13.1-2.dsc
edd5f7455ef8ec0f3fc1df0867f04fa1 19768 libs optional
gpgme1.0_1.13.1-2.debian.tar.xz
0973764309265760b6737b192e741bf8 18420 libs optional
gpgme1.0_1.13.1-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iHUEARYIAB0WIQQsv6x2UaqQJzY+dXHEDyVUMvKBDwUCXiog8wAKCRDEDyVUMvKB
D6+BAPwLZHTK7GdDRpAgA8qL2VYE0EB3xHIEtdFlW/L4J3pJjQEAnaLN3n8qUlR9
H3k2O0JEMxP/YxcSeyoSv7K3xlX1gQw=
=2R8I
-END PGP SIGNATURE End Message ---
Bug#943390: marked as done (gpgme1.0: please update test for python->python2 move)
Your message dated Thu, 23 Jan 2020 22:50:05 +
with message-id
and subject line Bug#943390: fixed in gpgme1.0 1.13.1-2
has caused the Debian Bug report #943390,
regarding gpgme1.0: please update test for python->python2 move
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.)
--
943390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gpgme1.0
Version: 1.13.1-1
tags: patch
Hello, in this commit [1] python stop being a thing, while python2 becomes
reality
patch:
diff -Nru gpgme1.0-1.12.0/debian/tests/python
gpgme1.0-1.12.0/debian/tests/python
--- gpgme1.0-1.12.0/debian/tests/python 2019-01-23 17:49:32.0 +0100
+++ gpgme1.0-1.12.0/debian/tests/python 2019-10-24 11:31:46.0 +0200
@@ -1,3 +1,3 @@
#!/bin/bash
-exec python debian/tests/python-gpg
+exec python2 debian/tests/python-gpg
[1]
https://salsa.debian.org/python-team/tools/dh-python/commit/0648189d7c20ad04cd939ff85dabca8d5a19fdd8
--- End Message ---
--- Begin Message ---
Source: gpgme1.0
Source-Version: 1.13.1-2
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 943...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Kahn Gillmor (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: SHA256
Format: 1.8
Date: Thu, 23 Jan 2020 17:11:25 -0500
Source: gpgme1.0
Architecture: source
Version: 1.13.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuPG Maintainers
Changed-By: Daniel Kahn Gillmor
Closes: 943111 943390 944774
Changes:
gpgme1.0 (1.13.1-2) unstable; urgency=medium
.
* rebuild, pulling in python 3.8 (Closes: #944774)
- requires patching upstream, changes to cross-building logic
* Update standards version to 4.4.1, no changes needed.
* add buildtime and runtime tests for platform time limits
* remove python-gpg autopkgtest entirely (Closes: #943390, #943111)
* update lintian-overrides for untracked C++ symbols
* fix json tests
* d/control: drop unused ${shlibs:Depends} from libgpgmepp-dev
* d/control: added ${python3:Versions} to python3-gpg
Checksums-Sha1:
9bbddb05ec952566ee04383b0f6ef2ed73bff8b6 2258 gpgme1.0_1.13.1-2.dsc
1ca56c058541a8318bb988558664bb4a49efe6a4 19768 gpgme1.0_1.13.1-2.debian.tar.xz
04add7c3f8d33e76b90e135f95ba2cc467693a60 18420
gpgme1.0_1.13.1-2_amd64.buildinfo
Checksums-Sha256:
81d8a2db4746c8fdfb3b9ff2bf18ddc0e1df74d23f0cad6db3c992e4afd5a783 2258
gpgme1.0_1.13.1-2.dsc
bddc4d6725af83c38a1b9953683bb9c2e40049867bef205e428cea307207925d 19768
gpgme1.0_1.13.1-2.debian.tar.xz
2664dcdd10cd7de57f0a3c253f2b4c690f04a388cfb53065b480c6ca9493f40e 18420
gpgme1.0_1.13.1-2_amd64.buildinfo
Files:
9e98e39414139a0715bc591a009b5f1b 2258 libs optional gpgme1.0_1.13.1-2.dsc
edd5f7455ef8ec0f3fc1df0867f04fa1 19768 libs optional
gpgme1.0_1.13.1-2.debian.tar.xz
0973764309265760b6737b192e741bf8 18420 libs optional
gpgme1.0_1.13.1-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iHUEARYIAB0WIQQsv6x2UaqQJzY+dXHEDyVUMvKBDwUCXiog8wAKCRDEDyVUMvKB
D6+BAPwLZHTK7GdDRpAgA8qL2VYE0EB3xHIEtdFlW/L4J3pJjQEAnaLN3n8qUlR9
H3k2O0JEMxP/YxcSeyoSv7K3xlX1gQw=
=2R8I
-END PGP SIGNATURE End Message ---
Bug#949711: Build-depends on sgmltools-lite, which is being removed
Source: aboot Severity: serious sgmltools-lite is scheduled for removal and aboot is the last package build depending on it. There hasn't been any aboot upload since 2013 and it's RC-buggy for a long time, should we simply remove it? Cheers, Moritz
Bug#949695: thunderbird does not start anymore
On Thu, 23 Jan 2020 20:15:20 +0100 Birger Schacht wrote: > I just had the same problem. For me, downgrading libsqlite3 to > libsqlite3-0_3.30.1+fossil191229-1 made thunderbird start again. Same for firefox, see: #949644 Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#936585: gbirthday: Python2 removal in sid/bullseye
On Sun, Dec 15, 2019 at 10:44:22PM +0100, Moritz Mühlenhoff wrote: > On Tue, Oct 22, 2019 at 10:04:35PM +0200, Jérôme wrote: > > Hi. > > > > Last gbirthday maintainer speaking. > > > > The gbirthday package is more or less dead upstream, unless someone > > volunteers to take it over. > > Hi Rolf, > are you planning to port it yourself or switch to the mentioned > qt port? Otherwise we should remove it from the archive. I've filed a removal bug now. Cheers, Moritz
Bug#937815: marked as done (python-html2text: Python2 removal in sid/bullseye)
Your message dated Thu, 23 Jan 2020 22:07:21 + with message-id and subject line Bug#937815: fixed in python-html2text 2019.8.11-2 has caused the Debian Bug report #937815, regarding python-html2text: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 937815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937815 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-html2text Version: 2019.8.11-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-html2text If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-html2text Source-Version: 2019.8.11-2 We believe that the bug you reported is fixed in the latest version of python-html2text, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated python-html2text package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 23 Jan 2020 16:47:33 -0500 Source: python-html2text Architecture: source Version: 2019.8.11-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Sandro Tosi Closes: 937815 Changes: python-html2text (2019.8.11-2) unstable; urgency=medium . [ Ondřej Nový ] * Bump Standards-Version to 4.4.1. . [ Debian Janitor ] * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. . [ Sandro Tosi ] * Drop python2 support; Closes: #937815 Checksums-Sha1: 35abe7db0902db6ff548ca7d7b5a2cbe8e3bebf4 2183 python-html2text_2019.8.11-2.dsc 1a0f8eb1ae2fd2a36caad6d4377f299e6ebdb6f0 6672 python-html2text_2019.8.11-2.debian.tar.xz 470d94ef85f12bf4f0b605ca781af32ecd13c8ac 6769 python-html2text_2019.8.11-2_source.buildinfo Checksums-Sha256: fd96cccee7444685b748bd9afc2faa2f3609624382a4b8d57768cea1e8e03e5e 2183
Bug#885505: bumping severity of pygtk bugs
On Wed, Dec 11, 2019 at 09:52:15AM +0100, Thibaut Paumard wrote: > Le 10/12/2019 à 19:59, Moritz Mühlenhoff a écrit : > > On Mon, Oct 07, 2019 at 04:51:09PM +0200, Thibaut Paumard wrote: > >> Dear Jeremy, > >> > >> Thanks, I have warned upstream that spydr will be removed if not updated > >> to Python 3 and Gtk 3. > > > > Was there any reaction? Otherwise let's go ahead with the removal from > > the archive. > > > > Cheers, > > Moritz > > Yes, upstream did say they would fix this. As this is a leaf package, I > would propose to wait until after the vacation and remove it on, say, > Jan. 15th. In the meantime I ill ping them and maybe they manage by then. > > Else, I can always reintroduce it later. Did you hear anything back? Shall we remove it? Cheers, Moritz
Processed: libidn2: binary-arch target depends on makeinfo (but texinfo is in Build-Depends-Indep)
Processing control commands: > found -1 2.0.5-1 Bug #949705 [src:libidn2] libidn2: binary-arch target depends on makeinfo (but texinfo is in Build-Depends-Indep) Marked as found in versions libidn2/2.0.5-1. -- 949705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949705 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949705: libidn2: binary-arch target depends on makeinfo (but texinfo is in Build-Depends-Indep)
Source: libidn2
Version: 2.2.0-2
Severity: serious
Justification: FTBFS
Control: found -1 2.0.5-1
Hi
The binary-arch target would depend on makeinfo, but texinfo is only
listed in Build-Depends-Indep.
When there is need to patch libidn2 and builds are then done by
buildds this would cause FTBFS on every architecture. How to
reproduce:
Install only the Build-Depends as done on buildds.
touch lib/lookup.c and only build the arch:any binary packages
(dpkg-buildpackage -G or debian/rules build-arch). From the build log:
> [...]
> mkdir -p `dirname texi/lookup.c.texi`
> ../doc/gdoc -texinfo ../lib/lookup.c > texi/lookup.c.texi
> mkdir -p `dirname texi/idn2_lookup_u8.texi`
> ../doc/gdoc -texinfo -function idn2_lookup_u8 ../lib/lookup.c >
> texi/idn2_lookup_u8.texi
> mkdir -p `dirname texi/idn2_lookup_ul.texi`
> ../doc/gdoc -texinfo -function idn2_lookup_ul ../lib/lookup.c >
> texi/idn2_lookup_ul.texi
> mkdir -p `dirname texi/idn2_to_ascii_4i.texi`
> ../doc/gdoc -texinfo -function idn2_to_ascii_4i ../lib/lookup.c >
> texi/idn2_to_ascii_4i.texi
> mkdir -p `dirname texi/idn2_to_ascii_4i2.texi`
> ../doc/gdoc -texinfo -function idn2_to_ascii_4i2 ../lib/lookup.c >
> texi/idn2_to_ascii_4i2.texi
> mkdir -p `dirname texi/idn2_to_ascii_4z.texi`
> ../doc/gdoc -texinfo -function idn2_to_ascii_4z ../lib/lookup.c >
> texi/idn2_to_ascii_4z.texi
> mkdir -p `dirname texi/idn2_to_ascii_8z.texi`
> ../doc/gdoc -texinfo -function idn2_to_ascii_8z ../lib/lookup.c >
> texi/idn2_to_ascii_8z.texi
> mkdir -p `dirname texi/idn2_to_ascii_lz.texi`
> ../doc/gdoc -texinfo -function idn2_to_ascii_lz ../lib/lookup.c >
> texi/idn2_to_ascii_lz.texi
> restore=: && backupdir=".am$$" && \
> am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
> rm -rf $backupdir && mkdir $backupdir && \
> if (/bin/bash /build/libidn2-2.2.0/build-aux/missing makeinfo --version)
> >/dev/null 2>&1; then \
> for f in libidn2.info libidn2.info-[0-9] libidn2.info-[0-9][0-9]
> libidn2.i[0-9] libidn2.i[0-9][0-9]; do \
> if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
> done; \
> else :; fi && \
> cd "$am__cwd"; \
> if /bin/bash /build/libidn2-2.2.0/build-aux/missing makeinfo -I . \
> -o libidn2.info libidn2.texi; \
> then \
> rc=0; \
> CDPATH="${ZSH_VERSION+.}:" && cd .; \
> else \
> rc=$?; \
> CDPATH="${ZSH_VERSION+.}:" && cd . && \
> $restore $backupdir/* `echo "./libidn2.info" | sed 's|[^/]*$||'`; \
> fi; \
> rm -rf $backupdir; exit $rc
> /build/libidn2-2.2.0/build-aux/missing: line 81: makeinfo: command not found
> WARNING: 'makeinfo' is missing on your system.
> You should only need it if you modified a '.texi' file, or
> any other file indirectly affecting the aspect of the manual.
> You might want to install the Texinfo package:
>
Processed: Bug#937815 marked as pending in python-html2text
Processing control commands: > tag -1 pending Bug #937815 [src:python-html2text] python-html2text: Python2 removal in sid/bullseye Added tag(s) pending. -- 937815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937815 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937815: marked as pending in python-html2text
Control: tag -1 pending Hello, Bug #937815 in python-html2text reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/python-html2text/commit/0e81c9e468cbc1e21fd0bede24f9d6bc96dfaa5f Drop python2 support; Closes: #937815 (this message was generated automatically) -- Greetings https://bugs.debian.org/937815
Bug#938041: marked as done (python-potr: Python2 removal in sid/bullseye)
Your message dated Thu, 23 Jan 2020 21:29:00 + with message-id and subject line Bug#938041: fixed in python-potr 1.0.2-2 has caused the Debian Bug report #938041, regarding python-potr: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 938041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-potr Version: 1.0.2-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-potr If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-potr Source-Version: 1.0.2-2 We believe that the bug you reported is fixed in the latest version of python-potr, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated python-potr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 23 Jan 2020 15:35:53 -0500 Source: python-potr Architecture: source Version: 1.0.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Sandro Tosi Closes: 938041 Changes: python-potr (1.0.2-2) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Remove ancient X-Python-Version field. * d/control: Remove ancient X-Python3-Version field. * Bump Standards-Version to 4.4.0. * d/control: Fix wrong Vcs-*. * Bump Standards-Version to 4.4.1. . [ Sandro Tosi ] * Drop python2 support; Closes: #938041 Checksums-Sha1: 44f6f2de1ca1b0e0d8a9ac950c70d00c10073219 2051 python-potr_1.0.2-2.dsc 953ffbd5acb784de0b699c8268885a9041cb8f60 120988 python-potr_1.0.2-2.debian.tar.xz 15a92d2626e5056c128df7210b3248cf98f67151 6377 python-potr_1.0.2-2_source.buildinfo Checksums-Sha256: 390df0bc38969cf2126b43e2a98c616ec62a27b56437bc572e6b9f70e59dda20 2051 python-potr_1.0.2-2.dsc
Processed: Re: Bug#949698: elogind: deletes users’ files under /dev/shm/ on logout
Processing control commands: > severity -1 grave Bug #949698 [elogind] elogind: deletes users’ files under /dev/shm/ on logout Severity set to 'grave' from 'important' -- 949698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949698 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949698: elogind: deletes users’ files under /dev/shm/ on logout
Control: severity -1 important Thorsten, On Thu, Jan 23, 2020 at 10:10:03PM +0100, Thorsten Glaser wrote: > > This behaviour is configurable via RemoveIPC in /etc/elogind/logind.conf. > > See > > > Perhaps you could confirm that this configuration change provides the > > behaviour > > you want? > > thanks, yes, this provides the behaviour necessary for proper system > operation. Please make it the default. Good! Downgrading severity to important. I will explore the implications of changing the default. Thanks. Mark
Processed: Re: Bug#949698: elogind: deletes users’ files under /dev/shm/ on logout
Processing control commands: > severity -1 important Bug #949698 [elogind] elogind: deletes users’ files under /dev/shm/ on logout Severity set to 'important' from 'critical' -- 949698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949698 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949677: mesa breaks build of kcrash, konsole and libkscreen as tested in autopkgtest migration setup
Hi Timo, On 23-01-2020 22:01, Timo Aaltonen wrote: > Look at the error above, the file shipped by qtbase5-dev requires > libEGL.so which the libegl-dev dependency provides. It used to be in > libglvnd-dev but moved to a new package when the EGL headers were added > upstream. So, libglvnd-dev should add a versioned breaks on the old qtbase5-dev, right? Paul
Bug#949698: elogind: deletes users’ files under /dev/shm/ on logout
Hi Mark, > This behaviour is configurable via RemoveIPC in /etc/elogind/logind.conf. See > Perhaps you could confirm that this configuration change provides the > behaviour > you want? thanks, yes, this provides the behaviour necessary for proper system operation. Please make it the default. Thanks, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Bug#949657: marked as done (firefox: Crashes on startup)
Your message dated Thu, 23 Jan 2020 20:58:28 +
with message-id
and subject line Bug#949644: fixed in sqlite3 3.31.0+really3.30.1+fossil191229-1
has caused the Debian Bug report #949644,
regarding firefox: Crashes on startup
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
949644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949644
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox
Version: 72.0.2-1
Severity: important
Dear maintainer,
Thank you for maintaining this great package!
Sadly, this morning, firefox starting crashing on startup, making it
unusable for me. I tried disabling all plugins, extensions etc.,
removing my profile, starting in safe mode, all to no avail.
Additionally, when reporting this bug, the bugreport script tried to
start firefox, resulting in another crash. I could reproduce that the
script /usr/share/bug/firefox/script caused that crash, and that the
command "firefox --dump-addons-info" fails. To give you at least some
information, here is the output of find /usr/{share,lib}/mozilla:
/usr/share/mozilla
/usr/share/mozilla/extensions
/usr/lib/mozilla
/usr/lib/mozilla/native-messaging-hosts
/usr/lib/mozilla/plugins
/usr/lib/mozilla/extensions
I have attached a (thankfully short) backtrace of a crash; it happens in
an interaction of libxul and libsqlite.
-- Package-specific info:
-- Addons package information
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages firefox depends on:
ii debianutils 4.9.1
ii fontconfig2.13.1-2+b1
ii libatk1.0-0 2.34.1-1
ii libc6 2.29-9
ii libcairo-gobject2 1.16.0-4
ii libcairo2 1.16.0-4
ii libdbus-1-3 1.12.16-2
ii libdbus-glib-1-2 0.110-5
ii libevent-2.1-72.1.11-stable-1
ii libffi7 3.3-3
ii libfontconfig12.13.1-2+b1
ii libfreetype6 2.10.1-2
ii libgcc1 1:9.2.1-24
ii libgdk-pixbuf2.0-02.40.0+dfsg-2
ii libglib2.0-0 2.62.4-1+b1
ii libgtk-3-03.24.13-1
ii libnspr4 2:4.24-1
ii libnss3 2:3.49.1-1
ii libpango-1.0-01.42.4-8
ii libsqlite3-0 3.31.0-1
ii libstartup-notification0 0.12-6
ii libstdc++69.2.1-24
ii libx11-6 2:1.6.8-1
ii libx11-xcb1 2:1.6.8-1
ii libxcb-shm0 1.13.1-3
ii libxcb1 1.13.1-3
ii libxcomposite11:0.4.4-2
ii libxdamage1 1:1.1.5-1
ii libxext6 2:1.3.3-1+b2
ii libxfixes31:5.0.3-1
ii libxrender1 1:0.9.10-1
ii libxt61:1.1.5-1+b3
ii procps2:3.3.15-2+b1
ii zlib1g1:1.2.11.dfsg-1+b1
Versions of packages firefox recommends:
ii libavcodec58 7:4.2.1-2+b1
Versions of packages firefox suggests:
ii fonts-lmodern 2.004.5-6
ii fonts-stix [otf-stix] 1.1.1-4
ii libcanberra0 0.30-7
ii libgssapi-krb5-2 1.17-6
ii libgtk2.0-02.24.32-4
ii pulseaudio 13.0-3
-- no debconf information
Reading symbols from firefox...
Reading symbols from
/usr/lib/debug/.build-id/eb/7f184c11a1ccca099367d4d8f4872b37739f31.debug...
(gdb) run
Starting program: /usr/bin/firefox
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x777ff700 (LWP 7489)]
[Thread 0x777ff700 (LWP 7489) exited]
[Detaching after fork from child process 7529]
[New Thread 0x777ff700 (LWP 7534)]
[New Thread 0x7fffec2be700 (LWP 7539)]
[New Thread 0x7fffeb5dc700 (LWP 7540)]
[New Thread 0x7fffe75f7700 (LWP 7541)]
[New Thread 0x7fffe75b6700 (LWP 7542)]
[New Thread 0x7fffe7575700 (LWP 7543)]
[New Thread 0x7fffe72ff700 (LWP 7544)]
[Detaching after fork from child process 7545]
[New Thread 0x7fffebabd700 (LWP 7546)]
[New Thread 0x7fffe6afe700 (LWP 7547)]
[New Thread 0x7fffe68ff700 (LWP 7548)]
[New Thread 0x7fffe6700700 (LWP 7549)]
[New Thread 0x7fffe6501700 (LWP 7550)]
[New Thread 0x7fffe5cff700 (LWP 7551)]
[New
Bug#949683: marked as done (libsqlite3-0: upgrade to 3.31.0-1 breaks iceweasel (makes it crash))
Your message dated Thu, 23 Jan 2020 20:58:28 + with message-id and subject line Bug#949644: fixed in sqlite3 3.31.0+really3.30.1+fossil191229-1 has caused the Debian Bug report #949644, regarding libsqlite3-0: upgrade to 3.31.0-1 breaks iceweasel (makes it crash) 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.) -- 949644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firefox-esr Version: 68.4.2esr-1 Severity: serious Justification: stops working I’ve just upgraded my system (Debian sid) and now cannot use iceweasel any more — after I start it and select the profile to use, it crashes; the normal main screen is never even drawn. -- Package-specific info: -- Addons package information -- System Information: Debian Release: bullseye/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages firefox-esr depends on: ii debianutils 4.9.1 ii fontconfig2.13.1-2+b1 ii libasound21.2.1.2-2 ii libatk1.0-0 2.34.1-1 ii libc6 2.29-9 ii libcairo-gobject2 1.16.0-4 ii libcairo2 1.16.0-4 ii libdbus-1-3 1.12.16-2 ii libdbus-glib-1-2 0.110-5 ii libevent-2.1-72.1.11-stable-1 ii libffi7 3.3-3 ii libfontconfig12.13.1-2+b1 ii libfreetype6 2.10.1-2 ii libgcc1 1:9.2.1-24 ii libgdk-pixbuf2.0-02.40.0+dfsg-2 ii libglib2.0-0 2.62.4-1+b1 ii libgtk-3-03.24.13-1 ii libjsoncpp1 1.7.4-3+b1 ii libnspr4 2:4.24-1 ii libnss3 2:3.49.1-1 ii libpango-1.0-01.42.4-8 ii libsqlite3-0 3.31.0-1 ii libstartup-notification0 0.12-6 ii libstdc++69.2.1-24 ii libx11-6 2:1.6.8-1 ii libx11-xcb1 2:1.6.8-1 ii libxcb-shm0 1.13.1-3 ii libxcb1 1.13.1-3 ii libxcomposite11:0.4.4-2 ii libxdamage1 1:1.1.5-1 ii libxext6 2:1.3.3-1+b2 ii libxfixes31:5.0.3-1 ii libxrender1 1:0.9.10-1 ii libxt61:1.1.5-1+b3 ii procps2:3.3.15-2+b1 ii zlib1g1:1.2.11.dfsg-1+b1 Versions of packages firefox-esr recommends: ii libavcodec57 7:3.2.14-1~deb9u1 ii libavcodec58 7:4.2.1-2+b1 Versions of packages firefox-esr suggests: ii fonts-lmodern 2.004.5-6 ii fonts-stix [otf-stix] 1.1.1-4 ii libcanberra0 0.30-7 ii libgssapi-krb5-2 1.17-6 ii libgtk2.0-02.24.32-4 pn pulseaudio -- no debconf information --- End Message --- --- Begin Message --- Source: sqlite3 Source-Version: 3.31.0+really3.30.1+fossil191229-1 We believe that the bug you reported is fixed in the latest version of sqlite3, 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 949...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated sqlite3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 23 Jan 2020 18:49:05 + Source: sqlite3 Architecture: source Version: 3.31.0+really3.30.1+fossil191229-1 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 949644 Changes: sqlite3 (3.31.0+really3.30.1+fossil191229-1) unstable; urgency=medium . * Revert to 3.30.1+fossil191229-1 until Firefox bug #1607902 is fixed (closes: #949644). * Remove 3.31.0 symbols. Checksums-Sha1: aca25dba64a21d8e5634a81c8f5cafb30150bdbd 2330 sqlite3_3.31.0+really3.30.1+fossil191229-1.dsc cc0e5d6aeda52dcf05e9c6bd759e6f5350c21b60
Bug#949646: marked as done (libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0)
Your message dated Thu, 23 Jan 2020 20:58:28 + with message-id and subject line Bug#949644: fixed in sqlite3 3.31.0+really3.30.1+fossil191229-1 has caused the Debian Bug report #949644, regarding libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-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.) -- 949644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libsqlite3-0 Version: 3.30.1+fossil191229-1 Severity: critical Justification: breaks unrelated software Dear Maintainer, With the update of libsqlite3-0 to version libsqlite3-0_3.30.1, Firefox (latest in Sid: 72.0.2) crashes immediately at start, even in safe mode and with a clean profile, and shows the "Sorry, Firefox has closed unexpectedly" dialog. Downgrading to libsqlite3-0_3.3> Firefox doesn't give any clear sign that it is a problem with libsqlite3-0. Terminal output: ``` ExceptionHandler::GenerateDump cloned child 10973 ExceptionHandler::WaitForContinueSignal waiting for continue signal... ExceptionHandler::SendContinueSignalToChild sent continue signal to child Exiting due to channel error. ``` Best regards, Lukas -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-3-amd64 (SMP w/8 CPU cores) 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=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libsqlite3-0 depends on: ii libc6 2.29-9 libsqlite3-0 recommends no packages. libsqlite3-0 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: sqlite3 Source-Version: 3.31.0+really3.30.1+fossil191229-1 We believe that the bug you reported is fixed in the latest version of sqlite3, 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 949...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated sqlite3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 23 Jan 2020 18:49:05 + Source: sqlite3 Architecture: source Version: 3.31.0+really3.30.1+fossil191229-1 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 949644 Changes: sqlite3 (3.31.0+really3.30.1+fossil191229-1) unstable; urgency=medium . * Revert to 3.30.1+fossil191229-1 until Firefox bug #1607902 is fixed (closes: #949644). * Remove 3.31.0 symbols. Checksums-Sha1: aca25dba64a21d8e5634a81c8f5cafb30150bdbd 2330 sqlite3_3.31.0+really3.30.1+fossil191229-1.dsc cc0e5d6aeda52dcf05e9c6bd759e6f5350c21b60 17399656 sqlite3_3.31.0+really3.30.1+fossil191229.orig.tar.xz 3308e5ffc8c63a176bc14b210425ad856fcea20c 19704 sqlite3_3.31.0+really3.30.1+fossil191229-1.debian.tar.xz Checksums-Sha256: 8baf5d40c566efbb474fa4a0aac682ae15ff4949649a3d707b77e4bce769a9ab 2330 sqlite3_3.31.0+really3.30.1+fossil191229-1.dsc 981e038dd2babe1628bd54c50e4bfc4bb9f794360dce8cc89a14eb5399bbdedc 17399656 sqlite3_3.31.0+really3.30.1+fossil191229.orig.tar.xz 3eaa29e7a65a9f1784fe955be4f5b2e1b2ccab02655eb343ef4f1aeb354786de 19704 sqlite3_3.31.0+really3.30.1+fossil191229-1.debian.tar.xz Files: ca7814f74fc9ebb068e0caa48a2d6ebe 2330 devel optional sqlite3_3.31.0+really3.30.1+fossil191229-1.dsc 6fb6933d1661a60a81e58ac52b85bb26 17399656 devel optional sqlite3_3.31.0+really3.30.1+fossil191229.orig.tar.xz 5093f004e3865b42e3ed4c98125639b6 19704 devel optional sqlite3_3.31.0+really3.30.1+fossil191229-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAl4p9dEACgkQ3OMQ54ZM yL9zZxAAmR2Hbi3+0IyoCalmrdvCQ3oyciDPrZ0TpuFaDMVKtnQ8Go8VJMFB9/uF gc/vUZjerKr+F7hGDrrNWNh+nqcuCkMnBDMCZtgz6OmKhN+yBeh0ZJZ7b8hXi7l7 r2/RmqG0U9hdfrwsBnoa1KqeAX1EmEQjFtIk/miY3r6u8gXVeCbBx2eRqjOPiSD4
Bug#885239: marked as done (xbindkeys: please migrate to guile-2.2)
Your message dated Thu, 23 Jan 2020 20:58:55 + with message-id and subject line Bug#885239: fixed in xbindkeys 1.8.6-2 has caused the Debian Bug report #885239, regarding xbindkeys: please migrate to guile-2.2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 885239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xbindkeys Severity: normal I'd like to remove guile-2.0 before the buster release, so please migrate to guile-2.2 when you can. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 --- End Message --- --- Begin Message --- Source: xbindkeys Source-Version: 1.8.6-2 We believe that the bug you reported is fixed in the latest version of xbindkeys, 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 885...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ricardo Mones (supplier of updated xbindkeys package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 23 Jan 2020 21:09:14 +0100 Source: xbindkeys Architecture: source Version: 1.8.6-2 Distribution: unstable Urgency: high Maintainer: Joerg Jaspert Changed-By: Ricardo Mones Closes: 885239 Changes: xbindkeys (1.8.6-2) unstable; urgency=high . * Build depend on Guile 2.2. Thanks to Martin Samuelsson for the original patch (Closes: #885239) * Update homepage URL * Update watch file to version 4 and expand regexp * Add manpage for xbindkeys_autostart * Update copyright to DEP 5 format * Set compatibility level to 12 * Update Standards-Version to 4.5.0, no other changes * Add Vcs-* headers for current repository Checksums-Sha1: 7a70d8e51a9654871c8c42d4c003ed2270fddc39 1888 xbindkeys_1.8.6-2.dsc dcc8733f37aeb836ad0017bbbc7bb9e78e9ffe96 10363 xbindkeys_1.8.6-2.diff.gz 17cb328a83589791d1366de97b7055641e4f862b 7061 xbindkeys_1.8.6-2_amd64.buildinfo Checksums-Sha256: 1b0fe14ea822f5ac1e66dc83bd5f09dd550a17781b1730aacb32568b9c606804 1888 xbindkeys_1.8.6-2.dsc 7eebeb1b7c4e4b7a3da49c33ba43d4acae0c5e0406a416cfddf9432578b64e61 10363 xbindkeys_1.8.6-2.diff.gz c4f5012e20b4e7e6f4239e433d727404d21fe8d01f43234a8b2883b17c116027 7061 xbindkeys_1.8.6-2_amd64.buildinfo Files: 63b947f8924395012ed767a4aee18a6f 1888 x11 optional xbindkeys_1.8.6-2.dsc 9c730d9a59e9272aa1733a9c191e00a6 10363 x11 optional xbindkeys_1.8.6-2.diff.gz 65c0ecc81c339217c9e2bb2970336867 7061 x11 optional xbindkeys_1.8.6-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEQ7w2SxbfDCBevXWSHw8KiN5bzKYFAl4qAJEACgkQHw8KiN5b zKaofw/+MGguNfY0SUlyeq1+F7ftj3PHRidy5bEfoz2mzOJ5bwh0+2jAMjftAkUz 8GweZo349CT1gRU3tzZiMJkBGSo57CHREahz7XwGUjNSffEKZLm6bEp5NOtUsS2u WLTRSiTb17hK02d6qZp6lOrBSCPX0s9nKW2e9NcmNlOHnkxC8z2lP/VqnnK+qBZP frLUTu2f2Ddc1P2f9/RGQ7GJ6Zzv4Z/VqJxAIRiZBW2BmCCg7mNWe0enF8tD9Jvh KHvic+OJX8QZqp+ln6y4fgfXyrObzvNkEWXyEHB+/55FnXoQdDG46RnWHtTjcsll cYWvHKn7Hij3tBnbSpTF5Cvfrv8xuI1Bu68M6P8qN9OR9c8yVYpxVJt8vCL27Sez maBkqDjpE4qgsoBeaNr4GirzJLhm8Y57fRLJnBHSrHn/PCs/6JEVMTvhS07UQbBg i/okW5Tk/dj20tUI4SvXJh971zb9+Ytz4qDNrCK0jxaQTRbisPkLO87LCh5j5BNb UQ0wgGcXPilPimpTeWQmN+rwRXDDAhVHoVG+ATusFvw1CxWC3S8vMEayeR8IsBwc 6W8H3ZNhrwpqhMQcIwbDVd92CoqowX4d//9hfBUI4cfZoJO+iLtn5btOXxnRR46e JaucjZdyPNCRu6iD2O9+NPVJhe7wBhUSBipD60yso6GriiHUBcU= =5NlS -END PGP SIGNATURE End Message ---
Bug#949677: mesa breaks build of kcrash, konsole and libkscreen as tested in autopkgtest migration setup
On 23.1.2020 22.07, Paul Gevers wrote: > Hi Timo, > > On 23-01-2020 19:32, Timo Aaltonen wrote: >> The relevant part of the build log was: >> >> CMake Error at >> /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfig.cmake:27 (message): >> The imported target "Qt5::Gui" references the file >> >> "/usr/lib/x86_64-linux-gnu/libEGL.so" >> >> but this file does not exist. >> >> >> So you need at least qtbase5-dev version 5.12.5+dfsg-3 which added >> libegl-dev to it's Depends. > > Which package (source or binary) do you refer here with "you"? As I > noted before, the interesting thing is that the autopkgtest passes both > in a pure testing environment and a pure unstable environment, but not > in testing with the following packages from unstable: > unstable/main amd64 libglvnd0 amd64 1.3.0-7 [51.5 kB] > unstable/main amd64 libglapi-mesa amd64 19.3.2-1 [69.9 kB] > unstable/main amd64 libgl1-mesa-dri amd64 19.3.2-1 [9,187 kB] > unstable/main amd64 libglx-mesa0 amd64 19.3.2-1 [182 kB] > unstable/main amd64 libglx0 amd64 1.3.0-7 [34.6 kB] > unstable/main amd64 libgl1 amd64 1.3.0-7 [88.8 kB] > unstable/main amd64 libglx-dev amd64 1.3.0-7 [16.2 kB] > unstable/main amd64 libgl-dev amd64 1.3.0-7 [100 kB] > unstable/main amd64 libgl1-mesa-dev amd64 19.3.2-1 [49.1 kB] > unstable/main amd64 libgbm1 amd64 19.3.2-1 [70.5 kB] > unstable/main amd64 libegl-mesa0 amd64 19.3.2-1 [139 kB] > unstable/main amd64 libegl1 amd64 1.3.0-7 [34.1 kB] > > A successful run in testing doesn't pull in libegl-dev either, so it > seems that the file is not a hard requirement. Look at the error above, the file shipped by qtbase5-dev requires libEGL.so which the libegl-dev dependency provides. It used to be in libglvnd-dev but moved to a new package when the EGL headers were added upstream. -- t
Bug#949644: marked as done (libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0)
Your message dated Thu, 23 Jan 2020 20:58:28 + with message-id and subject line Bug#949644: fixed in sqlite3 3.31.0+really3.30.1+fossil191229-1 has caused the Debian Bug report #949644, regarding libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-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.) -- 949644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libsqlite3-0 Version: 3.30.1+fossil191229-1 Severity: critical Justification: breaks unrelated software Dear Maintainer, With the update of libsqlite3-0 to version libsqlite3-0_3.30.1, Firefox (latest in Sid: 72.0.2) crashes immediately at start, even in safe mode and with a clean profile, and shows the "Sorry, Firefox has closed unexpectedly" dialog. Downgrading to libsqlite3-0_3.30.1 fixes the problem. Firefox doesn't give any clear sign that it is a problem with libsqlite3-0. Terminal output: ``` ExceptionHandler::GenerateDump cloned child 10973 ExceptionHandler::WaitForContinueSignal waiting for continue signal... ExceptionHandler::SendContinueSignalToChild sent continue signal to child Exiting due to channel error. ``` Best regards, Lukas -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-3-amd64 (SMP w/8 CPU cores) 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=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libsqlite3-0 depends on: ii libc6 2.29-9 libsqlite3-0 recommends no packages. libsqlite3-0 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: sqlite3 Source-Version: 3.31.0+really3.30.1+fossil191229-1 We believe that the bug you reported is fixed in the latest version of sqlite3, 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 949...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated sqlite3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 23 Jan 2020 18:49:05 + Source: sqlite3 Architecture: source Version: 3.31.0+really3.30.1+fossil191229-1 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 949644 Changes: sqlite3 (3.31.0+really3.30.1+fossil191229-1) unstable; urgency=medium . * Revert to 3.30.1+fossil191229-1 until Firefox bug #1607902 is fixed (closes: #949644). * Remove 3.31.0 symbols. Checksums-Sha1: aca25dba64a21d8e5634a81c8f5cafb30150bdbd 2330 sqlite3_3.31.0+really3.30.1+fossil191229-1.dsc cc0e5d6aeda52dcf05e9c6bd759e6f5350c21b60 17399656 sqlite3_3.31.0+really3.30.1+fossil191229.orig.tar.xz 3308e5ffc8c63a176bc14b210425ad856fcea20c 19704 sqlite3_3.31.0+really3.30.1+fossil191229-1.debian.tar.xz Checksums-Sha256: 8baf5d40c566efbb474fa4a0aac682ae15ff4949649a3d707b77e4bce769a9ab 2330 sqlite3_3.31.0+really3.30.1+fossil191229-1.dsc 981e038dd2babe1628bd54c50e4bfc4bb9f794360dce8cc89a14eb5399bbdedc 17399656 sqlite3_3.31.0+really3.30.1+fossil191229.orig.tar.xz 3eaa29e7a65a9f1784fe955be4f5b2e1b2ccab02655eb343ef4f1aeb354786de 19704 sqlite3_3.31.0+really3.30.1+fossil191229-1.debian.tar.xz Files: ca7814f74fc9ebb068e0caa48a2d6ebe 2330 devel optional sqlite3_3.31.0+really3.30.1+fossil191229-1.dsc 6fb6933d1661a60a81e58ac52b85bb26 17399656 devel optional sqlite3_3.31.0+really3.30.1+fossil191229.orig.tar.xz 5093f004e3865b42e3ed4c98125639b6 19704 devel optional sqlite3_3.31.0+really3.30.1+fossil191229-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAl4p9dEACgkQ3OMQ54ZM yL9zZxAAmR2Hbi3+0IyoCalmrdvCQ3oyciDPrZ0TpuFaDMVKtnQ8Go8VJMFB9/uF gc/vUZjerKr+F7hGDrrNWNh+nqcuCkMnBDMCZtgz6OmKhN+yBeh0ZJZ7b8hXi7l7 r2/RmqG0U9hdfrwsBnoa1KqeAX1EmEQjFtIk/miY3r6u8gXVeCbBx2eRqjOPiSD4
Bug#949647: marked as done (firefox: Unable to lounch)
Your message dated Thu, 23 Jan 2020 20:58:28 + with message-id and subject line Bug#949644: fixed in sqlite3 3.31.0+really3.30.1+fossil191229-1 has caused the Debian Bug report #949644, regarding firefox: Unable to lounch 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.) -- 949644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firefox Version: 72.0.2-1 Severity: grave Justification: renders package unusable Dear Maintainer, Starting firefox produces the error below and firefox informs me that it has crashed and cannot start: ExceptionHandler::GenerateDump cloned child ExceptionHandler::WaitForContinueSignal waiting for continue signal... 13819 ExceptionHandler::SendContinueSignalToChild sent continue signal to child I see exactly the same whether I am starting firefox with or without the option --safe-mode. -- Package-specific info: -- Addons package information -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-3-amd64 (SMP w/16 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages firefox depends on: ii debianutils 4.9.1 ii fontconfig2.13.1-2+b1 ii libatk1.0-0 2.34.1-1 ii libc6 2.29-9 ii libcairo-gobject2 1.16.0-4 ii libcairo2 1.16.0-4 ii libdbus-1-3 1.12.16-2 ii libdbus-glib-1-2 0.110-5 ii libevent-2.1-72.1.11-stable-1 ii libffi7 3.3-3 ii libfontconfig12.13.1-2+b1 ii libfreetype6 2.10.1-2 ii libgcc1 1:9.2.1-24 ii libgdk-pixbuf2.0-02.40.0+dfsg-2 ii libglib2.0-0 2.62.4-1+b1 ii libgtk-3-03.24.13-1 ii libnspr4 2:4.24-1 ii libnss3 2:3.49.1-1 ii libpango-1.0-01.42.4-8 ii libsqlite3-0 3.31.0-1 ii libstartup-notification0 0.12-6 ii libstdc++69.2.1-24 ii libx11-6 2:1.6.8-1 ii libx11-xcb1 2:1.6.8-1 ii libxcb-shm0 1.13.1-3 ii libxcb1 1.13.1-3 ii libxcomposite11:0.4.4-2 ii libxdamage1 1:1.1.5-1 ii libxext6 2:1.3.3-1+b2 ii libxfixes31:5.0.3-1 ii libxrender1 1:0.9.10-1 ii libxt61:1.1.5-1+b3 ii procps2:3.3.15-2+b1 ii zlib1g1:1.2.11.dfsg-1+b1 Versions of packages firefox recommends: ii libavcodec-extra57 7:3.4.3-1 ii libavcodec587:4.2.1-2+b1 Versions of packages firefox suggests: ii fonts-lmodern 2.004.5-6 pn fonts-stix | otf-stix ii libcanberra0 0.30-7 ii libgssapi-krb5-2 1.17-6 ii libgtk2.0-02.24.32-4 ii pulseaudio 13.0-3 -- no debconf information This mail was virus scanned and spam checked before delivery. This mail is also DKIM signed. See header dkim-signature. --- End Message --- --- Begin Message --- Source: sqlite3 Source-Version: 3.31.0+really3.30.1+fossil191229-1 We believe that the bug you reported is fixed in the latest version of sqlite3, 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 949...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated sqlite3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 23 Jan 2020 18:49:05 + Source: sqlite3 Architecture: source Version: 3.31.0+really3.30.1+fossil191229-1 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 949644 Changes:
Bug#949668: marked as done (firefox-esr: does not start after upgrade)
Your message dated Thu, 23 Jan 2020 20:58:28 + with message-id and subject line Bug#949644: fixed in sqlite3 3.31.0+really3.30.1+fossil191229-1 has caused the Debian Bug report #949644, regarding firefox-esr: does not start after upgrade 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.) -- 949644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firefox-esr Version: 68.4.2esr-1 Severity: grave Justification: renders package unusable hey, last night did a regular `apt upgrade` and amongst others, firefox, firefox- esr, thunderbird were updated.. (was using those during upgrade.. ) powered off a bit later, and today none of these applications open. message is the same as in #919769 : $ firefox-esr --safe-mode (firefox-esr:13795): Gtk-WARNING **: 12:16:17.843: Theme parsing error: gtk- widgets.css:1214:18: Not using units is deprecated. Assuming 'px'. ExceptionHandler::GenerateDump cloned child ExceptionHandler::WaitForContinueSignal waiting for continue signal...13826 ExceptionHandler::SendContinueSignalToChild sent continue signal to child tried to downgrade firefox-esr/testing but no luck. also downgraded some of the other packages that were upgraded last night (like gvfs*, libjavascriptcoregtk-4.0-18, libglib2.0-0, libwebkit2gtk-4.0-37), but still no luck. all mozilla products (ff, ff-esr, tb) that i'm using daily for work and personally, keep crashing with the same message. let me know if i can get more debug info somehow (there is no firefox-esr-gdb package as reportbug suggests...?). thanks in advance, d. -- Package-specific info: -- Addons package information -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.13-gnu (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages firefox-esr depends on: ii debianutils 4.9.1 ii fontconfig2.13.1-2+b1 ii libasound21.2.1.2-2 ii libatk1.0-0 2.34.1-1 ii libc6 2.29-9 ii libcairo-gobject2 1.16.0-4 ii libcairo2 1.16.0-4 ii libdbus-1-3 1.12.16-2 ii libdbus-glib-1-2 0.110-5 ii libevent-2.1-72.1.11-stable-1 ii libffi7 3.3-3 ii libfontconfig12.13.1-2+b1 ii libfreetype6 2.10.1-2 ii libgcc1 1:9.2.1-24 ii libgdk-pixbuf2.0-02.40.0+dfsg-2 ii libglib2.0-0 2.62.4-1+b1 ii libgtk-3-03.24.13-1 ii libjsoncpp1 1.7.4-3+b1 ii libnspr4 2:4.24-1 ii libnss3 2:3.49.1-1 ii libpango-1.0-01.42.4-8 ii libsqlite3-0 3.31.0-1 ii libstartup-notification0 0.12-6 ii libstdc++69.2.1-24 ii libx11-6 2:1.6.8-1 ii libx11-xcb1 2:1.6.8-1 ii libxcb-shm0 1.13.1-3 ii libxcb1 1.13.1-3 ii libxcomposite11:0.4.4-2 ii libxdamage1 1:1.1.5-1 ii libxext6 2:1.3.3-1+b2 ii libxfixes31:5.0.3-1 ii libxrender1 1:0.9.10-1 ii libxt61:1.1.5-1+b3 ii procps2:3.3.15-2+b1 ii zlib1g1:1.2.11.dfsg-1+b1 Versions of packages firefox-esr recommends: ii libavcodec-extra58 [libavcodec58] 7:4.2.1-2+b1 Versions of packages firefox-esr suggests: pn fonts-lmodern pn fonts-stix | otf-stix ii libcanberra0 0.30-7 ii libgssapi-krb5-2 1.17-6 ii libgtk2.0-02.24.32-4 ii pulseaudio 13.0-3 -- no debconf information --- End Message --- --- Begin Message --- Source: sqlite3 Source-Version: 3.31.0+really3.30.1+fossil191229-1 We believe that the bug you reported is fixed in the latest version of sqlite3, 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 949...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated
Bug#949645: marked as done (firefox: Firefox crashes immediate upon startup. safe-mode/disabling plugins has no effect.)
Your message dated Thu, 23 Jan 2020 20:58:28 + with message-id and subject line Bug#949644: fixed in sqlite3 3.31.0+really3.30.1+fossil191229-1 has caused the Debian Bug report #949644, regarding firefox: Firefox crashes immediate upon startup. safe-mode/disabling plugins has no effect. 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.) -- 949644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firefox Version: 72.0.2-1 Severity: important Dear Maintainer, As of upgrade to 72.0.2-1 firefox crashes immediately upon starting. Disabling safe mode by executing 'firefox -safe-mode' or by 'MOZILLA_DISABLE_PLUGINS=1 firefox' has no effect. Downgraded to 72.0.1-1+b1 and upon startup was forced by Firefox to create a new profile, but then it also crashed immediately. Subsequent attempts to launch it with plugins disabled also result in immediate crashes. -- Package-specific info: -- Addons package information -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores) 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= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages firefox depends on: ii debianutils 4.9.1 ii fontconfig2.13.1-2+b1 ii libatk1.0-0 2.34.1-1 ii libc6 2.29-9 ii libcairo-gobject2 1.16.0-4 ii libcairo2 1.16.0-4 ii libdbus-1-3 1.12.16-2 ii libdbus-glib-1-2 0.110-5 ii libevent-2.1-72.1.11-stable-1 ii libffi7 3.3-3 ii libfontconfig12.13.1-2+b1 ii libfreetype6 2.10.1-2 ii libgcc1 1:9.2.1-24 ii libgdk-pixbuf2.0-02.40.0+dfsg-2 ii libglib2.0-0 2.62.4-1+b1 ii libgtk-3-03.24.13-1 ii libnspr4 2:4.24-1 ii libnss3 2:3.49.1-1 ii libpango-1.0-01.42.4-8 ii libsqlite3-0 3.31.0-1 ii libstartup-notification0 0.12-6 ii libstdc++69.2.1-24 ii libx11-6 2:1.6.8-1 ii libx11-xcb1 2:1.6.8-1 ii libxcb-shm0 1.13.1-3 ii libxcb1 1.13.1-3 ii libxcomposite11:0.4.4-2 ii libxdamage1 1:1.1.5-1 ii libxext6 2:1.3.3-1+b2 ii libxfixes31:5.0.3-1 ii libxrender1 1:0.9.10-1 ii libxt61:1.1.5-1+b3 ii procps2:3.3.15-2+b1 ii zlib1g1:1.2.11.dfsg-1+b1 Versions of packages firefox recommends: ii libavcodec58 7:4.2.1-2+b1 Versions of packages firefox suggests: ii fonts-lmodern 2.004.5-6 pn fonts-stix | otf-stix ii libcanberra0 0.30-7 ii libgssapi-krb5-2 1.17-6 ii libgtk2.0-02.24.32-4 ii pulseaudio 13.0-3 -- no debconf information --- End Message --- --- Begin Message --- Source: sqlite3 Source-Version: 3.31.0+really3.30.1+fossil191229-1 We believe that the bug you reported is fixed in the latest version of sqlite3, 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 949...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated sqlite3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 23 Jan 2020 18:49:05 + Source: sqlite3 Architecture: source Version: 3.31.0+really3.30.1+fossil191229-1 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 949644 Changes: sqlite3 (3.31.0+really3.30.1+fossil191229-1) unstable; urgency=medium . * Revert to 3.30.1+fossil191229-1 until Firefox bug #1607902 is fixed (closes: #949644). * Remove 3.31.0 symbols.
Bug#949648: marked as done (firefox-esr: New version crash immediately at start)
Your message dated Thu, 23 Jan 2020 20:58:28 + with message-id and subject line Bug#949644: fixed in sqlite3 3.31.0+really3.30.1+fossil191229-1 has caused the Debian Bug report #949644, regarding firefox-esr: New version crash immediately at start 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.) -- 949644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firefox-esr Version: 68.4.2esr-1 Severity: grave Justification: renders package unusable Crash at startup sice yesterday upgrade. -- Package-specific info: -- Addons package information -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.13 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages firefox-esr depends on: ii debianutils 4.9.1 ii fontconfig2.13.1-2+b1 ii libasound21.2.1.2-2 ii libatk1.0-0 2.35.1-1 ii libc6 2.30-0experimental1 ii libcairo-gobject2 1.16.0-4 ii libcairo2 1.16.0-4 ii libdbus-1-3 1.13.12-2 ii libdbus-glib-1-2 0.110-5 ii libevent-2.1-72.1.11-stable-1 ii libffi7 3.3-3 ii libfontconfig12.13.1-2+b1 ii libfreetype6 2.10.1-2 ii libgcc1 1:9.2.1-24 ii libgdk-pixbuf2.0-02.40.0+dfsg-2 ii libglib2.0-0 2.63.3-3 ii libgtk-3-03.24.13-1 ii libjsoncpp1 1.7.4-3+b1 ii libnspr4 2:4.24-1 ii libnss3 2:3.49.1-1 ii libpango-1.0-01.44.7-1 ii libsqlite3-0 3.31.0-1 ii libstartup-notification0 0.12-6 ii libstdc++69.2.1-24 ii libx11-6 2:1.6.8-1 ii libx11-xcb1 2:1.6.8-1 ii libxcb-shm0 1.13.1-3 ii libxcb1 1.13.1-3 ii libxcomposite11:0.4.4-2 ii libxdamage1 1:1.1.5-1 ii libxext6 2:1.3.3-1+b2 ii libxfixes31:5.0.3-1 ii libxrender1 1:0.9.10-1 ii libxt61:1.1.5-1+b3 ii procps2:3.3.15-2+b1 ii zlib1g1:1.2.11.dfsg-1+b1 Versions of packages firefox-esr recommends: ii libavcodec58 10:4.2.2-dmo1 Versions of packages firefox-esr suggests: ii fonts-lmodern 2.004.5-6 ii fonts-stix [otf-stix] 1.1.1-4 ii libcanberra0 0.30-7 ii libgssapi-krb5-2 1.17-6 ii libgtk2.0-02.24.32-4 ii pulseaudio 13.0-3 -- no debconf information --- End Message --- --- Begin Message --- Source: sqlite3 Source-Version: 3.31.0+really3.30.1+fossil191229-1 We believe that the bug you reported is fixed in the latest version of sqlite3, 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 949...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated sqlite3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 23 Jan 2020 18:49:05 + Source: sqlite3 Architecture: source Version: 3.31.0+really3.30.1+fossil191229-1 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 949644 Changes: sqlite3 (3.31.0+really3.30.1+fossil191229-1) unstable; urgency=medium . * Revert to 3.30.1+fossil191229-1 until Firefox bug #1607902 is fixed (closes: #949644). * Remove 3.31.0 symbols. Checksums-Sha1: aca25dba64a21d8e5634a81c8f5cafb30150bdbd 2330 sqlite3_3.31.0+really3.30.1+fossil191229-1.dsc cc0e5d6aeda52dcf05e9c6bd759e6f5350c21b60 17399656 sqlite3_3.31.0+really3.30.1+fossil191229.orig.tar.xz 3308e5ffc8c63a176bc14b210425ad856fcea20c 19704
Bug#949650: marked as done (firefox: Crash at startup)
Your message dated Thu, 23 Jan 2020 20:58:28 + with message-id and subject line Bug#949644: fixed in sqlite3 3.31.0+really3.30.1+fossil191229-1 has caused the Debian Bug report #949644, regarding firefox: Crash at startup to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 949644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firefox Version: 72.0.2-1 Severity: normal Dear Maintainer, Firefox refuses to start. It shows crash report window to send crash report to Mozilla. No any revelant stacktrace in console and I gdb is unable to debug anything (sorry). -- Package-specific info: -- Addons package information -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-13.slh.2-aptosid-amd64 (SMP w/12 CPU cores; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages firefox depends on: ii debianutils 4.9.1 ii fontconfig2.13.1-2+b1 ii libatk1.0-0 2.34.1-1 ii libc6 2.29-9 ii libcairo-gobject2 1.16.0-4 ii libcairo2 1.16.0-4 ii libdbus-1-3 1.12.16-2 ii libdbus-glib-1-2 0.110-5 ii libevent-2.1-72.1.11-stable-1 ii libffi7 3.3-3 ii libfontconfig12.13.1-2+b1 ii libfreetype6 2.10.1-2 ii libgcc1 1:9.2.1-24 ii libgdk-pixbuf2.0-02.40.0+dfsg-2 ii libglib2.0-0 2.62.4-1+b1 ii libgtk-3-03.24.13-1 ii libnspr4 2:4.24-1 ii libnss3 2:3.49.1-1 ii libpango-1.0-01.42.4-8 ii libsqlite3-0 3.31.0-1 ii libstartup-notification0 0.12-6 ii libstdc++69.2.1-24 ii libx11-6 2:1.6.8-1 ii libx11-xcb1 2:1.6.8-1 ii libxcb-shm0 1.13.1-3 ii libxcb1 1.13.1-3 ii libxcomposite11:0.4.4-2 ii libxdamage1 1:1.1.5-1 ii libxext6 2:1.3.3-1+b2 ii libxfixes31:5.0.3-1 ii libxrender1 1:0.9.10-1 ii libxt61:1.1.5-1+b3 ii procps2:3.3.15-2+b1 ii zlib1g1:1.2.11.dfsg-1+b1 Versions of packages firefox recommends: ii libavcodec57 7:3.4.3-1 ii libavcodec58 7:4.2.1-2+b1 Versions of packages firefox suggests: pn fonts-lmodern pn fonts-stix | otf-stix ii libcanberra0 0.30-7 ii libgssapi-krb5-2 1.17-6 ii libgtk2.0-02.24.32-4 ii pulseaudio 13.0-3 -- no debconf information --- End Message --- --- Begin Message --- Source: sqlite3 Source-Version: 3.31.0+really3.30.1+fossil191229-1 We believe that the bug you reported is fixed in the latest version of sqlite3, 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 949...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated sqlite3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 23 Jan 2020 18:49:05 + Source: sqlite3 Architecture: source Version: 3.31.0+really3.30.1+fossil191229-1 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 949644 Changes: sqlite3 (3.31.0+really3.30.1+fossil191229-1) unstable; urgency=medium . * Revert to 3.30.1+fossil191229-1 until Firefox bug #1607902 is fixed (closes: #949644). * Remove 3.31.0 symbols. Checksums-Sha1: aca25dba64a21d8e5634a81c8f5cafb30150bdbd 2330 sqlite3_3.31.0+really3.30.1+fossil191229-1.dsc cc0e5d6aeda52dcf05e9c6bd759e6f5350c21b60 17399656 sqlite3_3.31.0+really3.30.1+fossil191229.orig.tar.xz 3308e5ffc8c63a176bc14b210425ad856fcea20c 19704
Bug#938830: marked as done (wokkel: Python2 removal in sid/bullseye)
Your message dated Thu, 23 Jan 2020 20:58:48 + with message-id and subject line Bug#938830: fixed in wokkel 18.0.0-2 has caused the Debian Bug report #938830, regarding wokkel: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 938830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938830 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:wokkel Version: 18.0.0-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:wokkel If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: wokkel Source-Version: 18.0.0-2 We believe that the bug you reported is fixed in the latest version of wokkel, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated wokkel package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 23 Jan 2020 15:22:57 -0500 Source: wokkel Architecture: source Version: 18.0.0-2 Distribution: unstable Urgency: medium Maintainer: Angel Abad Changed-By: Sandro Tosi Closes: 938830 Changes: wokkel (18.0.0-2) unstable; urgency=medium . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat. . [ Sandro Tosi ] * Drop python2 support; Closes: #938830 Checksums-Sha1: e9104132de51a328a6fb655da91ea2ee3f32b79f 2034 wokkel_18.0.0-2.dsc 65499530d774fe00a6cfd9684a21c7aff8a82de3 3460 wokkel_18.0.0-2.debian.tar.xz 4784e561b80b3d50e97875d6a7d84a4b79f7f7c1 6446 wokkel_18.0.0-2_source.buildinfo Checksums-Sha256: 0a8a77054321eb907dda418fd9aeebb89e12bfdd6120eecc31851a0fff1cb9e4 2034 wokkel_18.0.0-2.dsc 128e7d1de923f7ca8c2db3d2a37ce7b02db32b90bf064c109f6815537f169c9d 3460 wokkel_18.0.0-2.debian.tar.xz 955043f021bc8e2eaa0b62cf2e155c1d77a540bb82bd5b7ccf4b71c971c38b05 6446 wokkel_18.0.0-2_source.buildinfo Files: eea5cc694b1948e23f32ce8f3c403f4e 2034 python
Bug#949264: marked as done (nageru: FTBFS on arm/i386/mipsel architectures)
Your message dated Thu, 23 Jan 2020 20:55:23 + with message-id and subject line Bug#949264: fixed in movit 1.6.3-4 has caused the Debian Bug report #949264, regarding nageru: FTBFS on arm/i386/mipsel architectures 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.) -- 949264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nageru Severity: serious Version: 1.9.1-1.1 Recent source-only rebuild for nageru has mulitple FTBFS architectures on buildd: https://buildd.debian.org/status/package.php?p=nageru The tail log all reads like this: /usr/bin/ld: libcore.a(nageru_timecode_renderer.cpp.o): in function `TimecodeRenderer::TimecodeRenderer(movit::ResourcePool*, unsigned int, unsigned int)': ./obj-mipsel-linux-gnu/../nageru/timecode_renderer.cpp:51: undefined reference to `movit::generate_vbo(int, unsigned int, long, void const*)' /usr/bin/ld: ./obj-mipsel-linux-gnu/../nageru/timecode_renderer.cpp:51: undefined reference to `movit::generate_vbo(int, unsigned int, long, void const*)' /usr/bin/ld: libcore.a(nageru_chroma_subsampler.cpp.o): in function `ChromaSubsampler::ChromaSubsampler(movit::ResourcePool*)': ./obj-mipsel-linux-gnu/../nageru/chroma_subsampler.cpp:121: undefined reference to `movit::generate_vbo(int, unsigned int, long, void const*)' /usr/bin/ld: ./obj-mipsel-linux-gnu/../nageru/chroma_subsampler.cpp:121: undefined reference to `movit::generate_vbo(int, unsigned int, long, void const*)' collect2: error: ld returned 1 exit status ninja: build stopped: subcommand failed. Looks like further investigations are needed. -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: movit Source-Version: 1.6.3-4 We believe that the bug you reported is fixed in the latest version of movit, 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 949...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steinar H. Gunderson (supplier of updated movit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 23 Jan 2020 21:07:17 +0100 Source: movit Binary: libmovit-dev libmovit8 libmovit8-dbgsym Architecture: source amd64 Version: 1.6.3-4 Distribution: unstable Urgency: medium Maintainer: Steinar H. Gunderson Changed-By: Steinar H. Gunderson Description: libmovit-dev - GPU video filter library - development files libmovit8 - GPU video filter library Closes: 949264 Changes: movit (1.6.3-4) unstable; urgency=medium . * workaround-glsizeiptr-abi-change.diff: New patch, work around the fact that Mesa newly changed GLsizeiptr from int (ptrdiff_t) to long (khronos_ssize_t) on 32-bit platforms, causing different name mangling between builds. (Closes: #949264) Checksums-Sha1: 82c1f536e170392a257d96af5f6ed2e71e6a7e84 1831 movit_1.6.3-4.dsc ccc9f94767c18dc35cdb3fa58acaa9b8d21cb59a 3948 movit_1.6.3-4.debian.tar.xz 8df1dc3c273c9089e632f5413751e22f9c3dcb6d 258388 libmovit-dev_1.6.3-4_amd64.deb 6349d17c0c2683a97bf3710416753f73026e8e43 7564048 libmovit8-dbgsym_1.6.3-4_amd64.deb 11e31409eda6dad13224d768e2133694612e5e0e 175756 libmovit8_1.6.3-4_amd64.deb 0f64fbaaaedc3bc491cc911068433c9f9453bbcc 10897 movit_1.6.3-4_amd64.buildinfo Checksums-Sha256: a5ba7c9eb21ac58bdfb77557086e805830a47e9ed756272b2c03228b4214c3d8 1831 movit_1.6.3-4.dsc db62f30344b45dfd91a20463974195bc4bf5b3603af4f012cea58b9ed0b073f5 3948 movit_1.6.3-4.debian.tar.xz 6881eded6babe04d29679d67c816eb1c8d07863f1843a139bebb92f35c6de35a 258388 libmovit-dev_1.6.3-4_amd64.deb 1231849b5303c47e123c81dc01f91891f2c6715445898a396f6e5ff3901542e7 7564048 libmovit8-dbgsym_1.6.3-4_amd64.deb 7cf9870e25f8728d3c591874be9c1e0a5f6f563baf51e2ce8d3f038cc5a937a3 175756 libmovit8_1.6.3-4_amd64.deb 61cf3df966a079cc6408f3c0aeabbd30161564a4f0d3eaee0a0f2d9c04b7ae1e 10897 movit_1.6.3-4_amd64.buildinfo Files: 2bb1e57df115a000314c925eba9b5c4f 1831 libs optional movit_1.6.3-4.dsc f88d57132f92cc83cf073ac0de670e02 3948 libs optional movit_1.6.3-4.debian.tar.xz eb341f313063c7101a336b78749be98f 258388
Bug#949698: elogind: deletes users’ files under /dev/shm/ on logout
On Thu, Jan 23, 2020 at 08:32:46PM +0100, Thorsten Glaser wrote: > Package: elogind > Version: 241.3-1+debian2 > Severity: critical > Justification: breaks unrelated software > > I’m using a scheme in which I store ssh-agent and gpg-agent information > across all logins (local X session or ssh or xrdp) under /dev/shm/ since > I needed space that an unprivileged user can use and that doesn’t persist > across reboots. > > Since installing elogind, logging out from SSH sessions then on again > both breaks gpg-agent as well as makes ssh-agent instances multiply and, > thus, lose their loaded keys to the user. Thorsten, Thanks for this. This behaviour is configurable via RemoveIPC in /etc/elogind/logind.conf. See man logind.conf(5). I accept that the documentation for the behaviour is difficult to find (I had to search quite hard) and it may be that the default ought to be different. Perhaps you could confirm that this configuration change provides the behaviour you want? Many thanks. Mark
Bug#949698: elogind: deletes users’ files under /dev/shm/ on logout
On Thu, 23 Jan 2020, Dolphin Oracle wrote: > should you not be using /tmp for that rather that /dev/shm? No, /tmp is not guaranteed to be tmpfs and so can persist across boots. On a moderate wide scale of GNU/Linux installations /dev/shm is the (only) location that fits my (modest — we’re talking about several dozen bytes and a FIFO or two) needs. > I think /tmp should be set up as a tmpfs and will then not persist across Yes, but that’s a local admin choice, and it often is not because some “enterprise” software writes a lot into it and does not use /var/tmp for large content. But that’s besides the question. This behaviour is a grave bug because: > > logged out from all ssh sessions. In particular, this will also break > > software that runs as the user, dæmonised, that uses shared memory. This is inacceptable. In the meantime, someone told me… > > If you have to clean up after yourselves, keep a list and track of the > > files you created and will later need to delete. > > > > It might be a good idea to see whether systemd does the same and, if … that They don’t do that, au contraire, they often leave tons of crap around in /dev/shm… bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Processed: severity of 949700 is serious
Processing commands for cont...@bugs.debian.org: > severity 949700 serious Bug #949700 [mc] mc: extfs for .deb regression against 3:4.8.23-1 (makes it mostly unusable) Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 949700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949700 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 949682 is forwarded to https://github.com/SpiderLabs/ModSecurity/pull/2202
Processing commands for cont...@bugs.debian.org: > forwarded 949682 https://github.com/SpiderLabs/ModSecurity/pull/2202 Bug #949682 [libmodsecurity3] Denial of Service due to cooking handling Set Bug forwarded-to-address to 'https://github.com/SpiderLabs/ModSecurity/pull/2202'. > thanks Stopping processing here. Please contact me if you need assistance. -- 949682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949682 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 949682 in 3.0.4-1
Processing commands for cont...@bugs.debian.org: > fixed 949682 3.0.4-1 Bug #949682 [libmodsecurity3] Denial of Service due to cooking handling Marked as fixed in versions modsecurity/3.0.4-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 949682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949682 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949698: elogind: deletes users’ files under /dev/shm/ on logout
should you not be using /tmp for that rather that /dev/shm? I think /tmp should be set up as a tmpfs and will then not persist across reboots. /var/tmp is for tmp space that needs to persist across reboots. On Thu, Jan 23, 2020 at 2:36 PM Thorsten Glaser wrote: > Package: elogind > Version: 241.3-1+debian2 > Severity: critical > Justification: breaks unrelated software > > I’m using a scheme in which I store ssh-agent and gpg-agent information > across all logins (local X session or ssh or xrdp) under /dev/shm/ since > I needed space that an unprivileged user can use and that doesn’t persist > across reboots. > > Since installing elogind, logging out from SSH sessions then on again > both breaks gpg-agent as well as makes ssh-agent instances multiply and, > thus, lose their loaded keys to the user. > > Tons of searching and debugging eventuall led me, with strace as root on > it, to the culprit: elogind > > lrwxrwxrwx 1 root root 0 Jan 23 20:21 /proc/3061/exe -> > /lib/elogind/elogind* > > 3061 unlinkat(22, "info2", 0) = 0 > 3061 unlinkat(21, ".ssh-2339", AT_REMOVEDIR) = 0 > > > Cease that instantly. This breaks unrelated software on the system, > considering that the user’s processes are still running, even if they > logged out from all ssh sessions. In particular, this will also break > software that runs as the user, dæmonised, that uses shared memory. > > If you have to clean up after yourselves, keep a list and track of the > files you created and will later need to delete. > > It might be a good idea to see whether systemd does the same and, if > so, clone this bugreport and assign the clone to them. I’m not running > systemd, so I can’t do that myself easily. > > -- System Information: > Debian Release: bullseye/sid > APT prefers unreleased > APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, > 'unstable'), (100, 'experimental') > Architecture: x32 (x86_64) > Foreign Architectures: i386, amd64 > > Kernel: Linux 5.4.0-2-amd64 (SMP w/4 CPU cores) > Kernel taint flags: TAINT_FIRMWARE_WORKAROUND > Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C > (charmap=UTF-8) > Shell: /bin/sh linked to /bin/lksh > Init: sysvinit (via /sbin/init) > > Versions of packages elogind depends on: > ii dbus 1.12.16-2 > ii debconf 1.5.73 > ii libacl1 2.2.53-5 > ii libc62.29-9 > ii libcap2 1:2.27-1 > ii libelogind0 241.3-1+debian2 > ii libselinux1 3.0-1 > ii libudev1 244-3 > ii lsb-base 11.1.0 > > Versions of packages elogind recommends: > ii libpam-elogind 241.3-1+debian2 > ii policykit-1 0.105-26 > > elogind suggests no packages. > > -- no debconf information >
Bug#949677: mesa breaks build of kcrash, konsole and libkscreen as tested in autopkgtest migration setup
Hi Timo, On 23-01-2020 19:32, Timo Aaltonen wrote: > The relevant part of the build log was: > > CMake Error at > /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfig.cmake:27 (message): > The imported target "Qt5::Gui" references the file > > "/usr/lib/x86_64-linux-gnu/libEGL.so" > > but this file does not exist. > > > So you need at least qtbase5-dev version 5.12.5+dfsg-3 which added > libegl-dev to it's Depends. Which package (source or binary) do you refer here with "you"? As I noted before, the interesting thing is that the autopkgtest passes both in a pure testing environment and a pure unstable environment, but not in testing with the following packages from unstable: unstable/main amd64 libglvnd0 amd64 1.3.0-7 [51.5 kB] unstable/main amd64 libglapi-mesa amd64 19.3.2-1 [69.9 kB] unstable/main amd64 libgl1-mesa-dri amd64 19.3.2-1 [9,187 kB] unstable/main amd64 libglx-mesa0 amd64 19.3.2-1 [182 kB] unstable/main amd64 libglx0 amd64 1.3.0-7 [34.6 kB] unstable/main amd64 libgl1 amd64 1.3.0-7 [88.8 kB] unstable/main amd64 libglx-dev amd64 1.3.0-7 [16.2 kB] unstable/main amd64 libgl-dev amd64 1.3.0-7 [100 kB] unstable/main amd64 libgl1-mesa-dev amd64 19.3.2-1 [49.1 kB] unstable/main amd64 libgbm1 amd64 19.3.2-1 [70.5 kB] unstable/main amd64 libegl-mesa0 amd64 19.3.2-1 [139 kB] unstable/main amd64 libegl1 amd64 1.3.0-7 [34.1 kB] A successful run in testing doesn't pull in libegl-dev either, so it seems that the file is not a hard requirement. Paul
Bug#942146: koji: CVE-2019-17109
On Thu, Jan 23, 2020 at 08:42:03PM +0100, Moritz Muehlenhoff wrote: > Let's remove it in the upcoming stretch/buster point releases, then? seems reasonable to me. -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Bug#942146: koji: CVE-2019-17109
On Thu, Jan 23, 2020 at 04:37:15PM +, Holger Levsen wrote: > Hi Salvatore, > > On Sun, Jan 05, 2020 at 09:02:20PM +0100, Salvatore Bonaccorso wrote: > > Any news on this issue? AFAICT, the issue is fixed as well in 1.16.3, > > so the smaller jump should be possible. Once fixed in unstable, can > > you adress the issue as well via point release? > > I think it's pointless to have 1.16.x in unstable and newer koji needs > newer dnf (and some other stuff, iirc), which isnt packaged in Debian, > so this is not as straightforward as it seems. > > I'm also not sure there are many (or any?) users of koji from stable. If > I were to use it, I would use koji from Fedora... > https://qa.debian.org/popcon.php?package=koji seems to confirm this. Let's remove it in the upcoming stretch/buster point releases, then? Cheers, Moritz
Bug#949698: elogind: deletes users’ files under /dev/shm/ on logout
Package: elogind Version: 241.3-1+debian2 Severity: critical Justification: breaks unrelated software I’m using a scheme in which I store ssh-agent and gpg-agent information across all logins (local X session or ssh or xrdp) under /dev/shm/ since I needed space that an unprivileged user can use and that doesn’t persist across reboots. Since installing elogind, logging out from SSH sessions then on again both breaks gpg-agent as well as makes ssh-agent instances multiply and, thus, lose their loaded keys to the user. Tons of searching and debugging eventuall led me, with strace as root on it, to the culprit: elogind lrwxrwxrwx 1 root root 0 Jan 23 20:21 /proc/3061/exe -> /lib/elogind/elogind* 3061 unlinkat(22, "info2", 0) = 0 3061 unlinkat(21, ".ssh-2339", AT_REMOVEDIR) = 0 Cease that instantly. This breaks unrelated software on the system, considering that the user’s processes are still running, even if they logged out from all ssh sessions. In particular, this will also break software that runs as the user, dæmonised, that uses shared memory. If you have to clean up after yourselves, keep a list and track of the files you created and will later need to delete. It might be a good idea to see whether systemd does the same and, if so, clone this bugreport and assign the clone to them. I’m not running systemd, so I can’t do that myself easily. -- System Information: Debian Release: bullseye/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'), (100, 'experimental') Architecture: x32 (x86_64) Foreign Architectures: i386, amd64 Kernel: Linux 5.4.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages elogind depends on: ii dbus 1.12.16-2 ii debconf 1.5.73 ii libacl1 2.2.53-5 ii libc62.29-9 ii libcap2 1:2.27-1 ii libelogind0 241.3-1+debian2 ii libselinux1 3.0-1 ii libudev1 244-3 ii lsb-base 11.1.0 Versions of packages elogind recommends: ii libpam-elogind 241.3-1+debian2 ii policykit-1 0.105-26 elogind suggests no packages. -- no debconf information
Bug#949695: thunderbird does not start anymore
Hi, I just had the same problem. For me, downgrading libsqlite3 to libsqlite3-0_3.30.1+fossil191229-1 made thunderbird start again. cheers, Birger
Bug#943994: python3-zeitgeist not compatible with python3
在 2020-01-23四的 18:58 +0100，Laurent Bigonville写道： > IIRC upstream said that they were not bothering about the old binding > for python3 and that people should use the the GObject introspection > binding. > > The python3 package can and should completely be removed. > > Note that zeitgeist is completely dead upstream anyway so... Ack. At least we have a working zeitgeist v1.0.2 that will be able to migrate to Testing now. -- Thanks, Boyuan Yang
Bug#949696: (build)-dependency on python3-importlib-metadata missing
Package: src:python-jsonschema Version: 3.0.2-4 Severity: serious Tags: sid bullseye For python 3.7, the package still needs to (build)-depend on python3-importlib-metadata, see jsonschema/__init__.py
Bug#949695: thunderbird does not start anymore
Source: thunderbird Version: 1:68.4.1-1+b1 Severity: serious Hey, one of the last days testing and or unstable updates let thunderbird stop starting. I just get: $ thunderbird ExceptionHandler::GenerateDump cloned child 3482 ExceptionHandler::WaitForContinueSignal waiting for continue signal... ExceptionHandler::SendContinueSignalToChild sent continue signal to child me@gnu:~$ Exception ignored in: <_io.TextIOWrapper name='' mode='w' encoding='UTF-8'> BrokenPipeError: [Errno 32] Broken pipe Also with a new profile, also with the version from testing and unstable. So I think some dependecie crashes thunderbird -- System Information: Debian Release: 10.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#949677: mesa breaks build of kcrash, konsole and libkscreen as tested in autopkgtest migration setup
On 23.1.2020 17.01, Paul Gevers wrote: > Source: mesa, kcrash, konsole, libkscreen > Control: found -1 mesa/19.3.2-1 > Control: found -1 kcrash/5.62.0-1 > Control: found -1 konsole/4:19.08.1-2 > Control: found -1 libkscreen/4:5.14.5-1 > Severity: serious > Tags: sid bullseye > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > Usertags: breaks needs-update > > Dear maintainers, > > With a recent upload of mesa the autopkgtest of kcrash, konsole and > libkscreen fails in testing during building of the source package when > that autopkgtest is run with the binary packages of mesa from unstable. > It passes when run with only packages from testing. In tabular form (for > kcrash): >passfail > mesa from testing19.3.2-1 > kcrash from testing5.62.0-1 > versioned deps [0] from testingfrom unstable > all others from testingfrom testing The relevant part of the build log was: CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfig.cmake:27 (message): The imported target "Qt5::Gui" references the file "/usr/lib/x86_64-linux-gnu/libEGL.so" but this file does not exist. So you need at least qtbase5-dev version 5.12.5+dfsg-3 which added libegl-dev to it's Depends. -- t
Processed: Re: Bug#949647: firefox crashes on launch
Processing control commands: > tags -1 +confirmed patch pending upstream Bug #949647 [libsqlite3-0] firefox: Unable to lounch Bug #949644 [libsqlite3-0] libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0 Bug #949645 [libsqlite3-0] firefox: Firefox crashes immediate upon startup. safe-mode/disabling plugins has no effect. Bug #949646 [libsqlite3-0] libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0 Bug #949648 [libsqlite3-0] firefox-esr: New version crash immediately at start Bug #949650 [libsqlite3-0] firefox: Crash at startup Bug #949657 [libsqlite3-0] firefox: Crashes on startup Bug #949668 [libsqlite3-0] firefox-esr: does not start after upgrade Bug #949683 [libsqlite3-0] libsqlite3-0: upgrade to 3.31.0-1 breaks iceweasel (makes it crash) Added tag(s) patch, pending, confirmed, and upstream. Added tag(s) patch, pending, confirmed, and upstream. Added tag(s) pending, confirmed, upstream, and patch. Added tag(s) upstream, confirmed, pending, and patch. Added tag(s) patch, pending, confirmed, and upstream. Added tag(s) patch, confirmed, pending, and upstream. Added tag(s) pending, confirmed, upstream, and patch. Added tag(s) pending, confirmed, upstream, and patch. Added tag(s) confirmed, pending, upstream, and patch. > forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=1607902 Bug #949647 [libsqlite3-0] firefox: Unable to lounch Bug #949644 [libsqlite3-0] libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0 Bug #949645 [libsqlite3-0] firefox: Firefox crashes immediate upon startup. safe-mode/disabling plugins has no effect. Bug #949646 [libsqlite3-0] libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0 Bug #949648 [libsqlite3-0] firefox-esr: New version crash immediately at start Bug #949650 [libsqlite3-0] firefox: Crash at startup Bug #949657 [libsqlite3-0] firefox: Crashes on startup Bug #949668 [libsqlite3-0] firefox-esr: does not start after upgrade Bug #949683 [libsqlite3-0] libsqlite3-0: upgrade to 3.31.0-1 breaks iceweasel (makes it crash) Set Bug forwarded-to-address to 'https://bugzilla.mozilla.org/show_bug.cgi?id=1607902'. Set Bug forwarded-to-address to 'https://bugzilla.mozilla.org/show_bug.cgi?id=1607902'. Set Bug forwarded-to-address to 'https://bugzilla.mozilla.org/show_bug.cgi?id=1607902'. Set Bug forwarded-to-address to 'https://bugzilla.mozilla.org/show_bug.cgi?id=1607902'. Set Bug forwarded-to-address to 'https://bugzilla.mozilla.org/show_bug.cgi?id=1607902'. Set Bug forwarded-to-address to 'https://bugzilla.mozilla.org/show_bug.cgi?id=1607902'. Set Bug forwarded-to-address to 'https://bugzilla.mozilla.org/show_bug.cgi?id=1607902'. Set Bug forwarded-to-address to 'https://bugzilla.mozilla.org/show_bug.cgi?id=1607902'. Set Bug forwarded-to-address to 'https://bugzilla.mozilla.org/show_bug.cgi?id=1607902'. -- 949644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949644 949645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949645 949646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949646 949647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949647 949648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949648 949650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949650 949657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949657 949668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949668 949683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949683 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949693: Missing autoload.php
Package: php-guzzlehttp-psr7 Version: 1.4.2-0.1 Severity: serious Hi, Last NMU dropped the homemade autoload.php, and thus renders the package unusable. Regards David signature.asc Description: PGP signature
Bug#949647: firefox crashes on launch
Control: tags -1 +confirmed patch pending upstream Control: forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=1607902 On Thu, Jan 23, 2020 at 9:03 AM Peter Keel wrote: > Same for thunderbird, same on different debian unstable machines since > (yesterdays?) upgrade. Got several reports on this. :( Seems to be a Firefox / Thunderbird issue and their upstream know about it for some time now. See the forwarded URL. I'm going to revert the SQLite3 update until that issue is resolved - they have a proposed patch[1] at the moment. > (gdb) run > Starting program: /usr/bin/firefox Without debug symbols it doesn't help. But just for the record, it would be the following: Thread 18 "Cookie" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffe5cff700 (LWP 59805)] (anonymous namespace)::DatabasePathFromWALPath (zWALName=0x7fffeb8603a0 "/home/gcs/.mozilla/firefox/0m5v8o8f.default/cookies.sqlite-wal") at ./storage/TelemetryVFS.cpp:256 256 ./storage/TelemetryVFS.cpp: No such file or directory. (gdb) bt #0 (anonymous namespace)::DatabasePathFromWALPath (zWALName=0x7fffeb8603a0 "/home/gcs/.mozilla/firefox/0m5v8o8f.default/cookies.sqlite-wal") at ./storage/TelemetryVFS.cpp:256 #1 0x7fffee26c5a0 in (anonymous namespace)::MaybeEstablishQuotaControl (flags=524294, pFile=0x77815bc0, zName=0x7fffeb8603a0 "/home/gcs/.mozilla/firefox/0m5v8o8f.default/cookies.sqlite-wal") at ./build-browser/dist/include/mozilla/TimeStamp.h:452 #2 (anonymous namespace)::xOpen (vfs=, zName=0x7fffeb8603a0 "/home/gcs/.mozilla/firefox/0m5v8o8f.default/cookies.sqlite-wal", pFile=0x77815bc0, flags=524294, pOutFlags=0x7fffe5cfd654) at ./storage/TelemetryVFS.cpp:627 #3 0x7fffecc96a42 in sqlite3OsOpen (pFlagsOut=0x7fffe5cfd654, flags=524294, pFile=0x77815bc0, zPath=0x7fffeb8603a0 "/home/gcs/.mozilla/firefox/0m5v8o8f.default/cookies.sqlite-wal", pVfs=0x7fffec31fdf0) at sqlite3.c:60577 #4 sqlite3WalOpen (ppWal=0x7fffeb860120, mxWalSize=-1, bNoShm=, zWalName=, pDbFd=0x7fffeb860178, pVfs=0x7fffec31fdf0) at sqlite3.c:60577 #5 pagerOpenWal (pPager=pPager@entry=0x7fffeb86) at sqlite3.c:58991 #6 0x7fffecc96b8f in sqlite3PagerOpenWal (pbOpen=, pPager=0x7fffeb86) at sqlite3.c:59035 #7 sqlite3PagerOpenWal (pPager=0x7fffeb86, pbOpen=) at sqlite3.c:59017 #8 0x7fffeccdc650 in lockBtree (pBt=0x7fffe5e0bd30) at sqlite3.c:67210 #9 sqlite3BtreeBeginTrans (p=0x7fffe5ede1f0, wrflag=wrflag@entry=0, pSchemaVersion=pSchemaVersion@entry=0x0) at sqlite3.c:1996 #10 0x7fffecd10851 in sqlite3InitOne (db=0x7fffe755d800, iDb=iDb@entry=0, pzErrMsg=pzErrMsg@entry=0x7fffe5cfe498, mFlags=mFlags@entry=0) at sqlite3.c:127147 #11 0x7fffecd10a1c in sqlite3Init (db=db@entry=0x7fffe755d800, pzErrMsg=pzErrMsg@entry=0x7fffe5cfe498) at sqlite3.c:127332 #12 0x7fffecd10a5f in sqlite3ReadSchema (pParse=pParse@entry=0x7fffe5cfe490) at sqlite3.c:127358 #13 0x7fffecd1e075 in sqlite3Pragma (pParse=pParse@entry=0x7fffe5cfe490, pId1=pId1@entry=0x7fffe5cfdad8, pId2=pId2@entry=0x7fffe5cfdaf0, pValue=pValue@entry=0x7fffe5cfdb20, minusFlag=minusFlag@entry=1) at sqlite3.c:124785 #14 0x7fffecd205f7 in yy_reduce (yyLookahead=, pParse=0x7fffe5cfe490, yyLookaheadToken=..., yyruleno=242, yypParser=0x7fffe5cfda90) at sqlite3.c:156616 #15 sqlite3Parser (yyminor=..., yymajor=, yyp=0x7fffe5cfda90) at sqlite3.c:26101 #16 sqlite3RunParser (pParse=0x7fffe5cfe490, zSql=0x7fffe5edcded "", pzErrMsg=0x7fffe5cfe488) at sqlite3.c:27375 #17 0x7fffecd25493 in sqlite3Prepare (db=db@entry=0x7fffe755d800, zSql=zSql@entry=0x7fffe5edcd88 "/* /build/firefox-Ch5zq6/firefox-72.0.2/storage/mozStorageConnection.cpp */ PRAGMA cache_size = -2048", nBytes=nBytes@entry=-1, prepFlags=prepFlags@entry=128, pReprepare=pReprepare@entry=0x0, ppStmt=ppStmt@entry=0x7fffe5cfe750, pzTail=0x7fffe5cfe748) at sqlite3.c:127559 #18 0x7fffecd2582f in sqlite3LockAndPrepare (pzTail=0x7fffe5cfe748, ppStmt=0x7fffe5cfe750, pOld=0x0, prepFlags=128, nBytes=-1, zSql=0x7fffe5edcd88 "/* /build/firefox-Ch5zq6/firefox-72.0.2/storage/mozStorageConnection.cpp */ PRAGMA cache_size = -2048", db=0x7fffe755d800) at sqlite3.c:127631 #19 sqlite3LockAndPrepare (db=0x7fffe755d800, zSql=0x7fffe5edcd88 "/* /build/firefox-Ch5zq6/firefox-72.0.2/storage/mozStorageConnection.cpp */ PRAGMA cache_size = -2048", nBytes=-1, prepFlags=128, pOld=0x0, ppStmt=0x7fffe5cfe750, pzTail=0x7fffe5cfe748) at sqlite3.c:62070 #20 0x7fffecd25926 in sqlite3_prepare_v2 (db=db@entry=0x7fffe755d800, zSql=zSql@entry=0x7fffe5edcd88 "/* /build/firefox-Ch5zq6/firefox-72.0.2/storage/mozStorageConnection.cpp */ PRAGMA cache_size = -2048", nBytes=nBytes@entry=-1, ppStmt=ppStmt@entry=0x7fffe5cfe750, pzTail=pzTail@entry=0x7fffe5cfe748) at sqlite3.c:127715 #21 0x7fffecd0fecc in sqlite3_exec (db=db@entry=0x7fffe755d800, zSql=zSql@entry=0x7fffe5edcd88 "/* /build/firefox-Ch5zq6/firefox-72.0.2/storage/mozStorageConnection.cpp */ PRAGMA cache_size = -2048", xCallback=xCallback@entry=0x0,
Bug#943994: python3-zeitgeist not compatible with python3
Le 22/01/20 à 22:17, Boyuan Yang a écrit : No idea why. Looks like we need to have python3-zeitgeist removed eventually. However before that, I'm going for a workaround: Upload an experimental version with higher version string, e.g., 1.0.2+py3-0. After that, upload 1.0.2-3 onto Sid with python3-zeitgeist removed. This would keep binary package python3-zeitgeist in development repositories so that we do not need to go through NEW queue for another time if we really need that in the future. IIRC upstream said that they were not bothering about the old binding for python3 and that people should use the the GObject introspection binding. The python3 package can and should completely be removed. Note that zeitgeist is completely dead upstream anyway so...
Processed: [bts-link] source package src:python-pyepsg
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:python-pyepsg > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #949148 (http://bugs.debian.org/949148) > # Bug title: python-pyepsg: autopkgtest regression > # * https://github.com/rhattersley/pyepsg/issues/15 > # * remote status changed: (?) -> closed > # * closed upstream > tags 949148 + fixed-upstream Bug #949148 [src:python-pyepsg] python-pyepsg: autopkgtest regression Added tag(s) fixed-upstream. > usertags 949148 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 949148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949130: refind-install fails to determine the ESP partition
I'd like to add: the file system is vfat. The driver used to mount was not. To me it made a difference as I remember clearly to have created the partition. Am 23. Januar 2020 14:57:06 MEZ schrieb Rod Smith : >On 1/22/20 6:54 PM, Tianon Gravi wrote: >> On Sun, 19 Jan 2020 at 09:40, Pelzi wrote: >>> I found the cure for the problem: the ESP partition was listed as fs >type „msdos“ in fstab. Changing this to „vfat" made refind-install work >for me. >> >> Ah nice catch! So it sounds like at most, this should be an upstream >> feature request to have refind-install warn if fstab includes >> "/boot/efi" but it's not vfat or something like that? > >Sorry for not responding earlier, but I've been suffering from an ear >infection lately that's made it hard to do much of anything. > >In any event, refind-install already warns of this, and that warning >was >shown in the output presented earlier: > >> $ sudo refind-install >> ShimSource is none >> Installing rEFInd on Linux >> The ESP doesn't seem to be mounted! Trying to find it >> mount: /boot/efi: /dev/sda2 already mounted on /boot/efi. >> boot/efi doesn't seem to be on a VFAT filesystem. The ESP must be >> mounted at //boot or //boot/efi and it must be VFAT! Aborting! > >That said, the warning could admittedly be more explicit that msdos is >not an acceptable filesystem driver in this context. OTOH, presenting a >disseration on the differences between the Linux vfat and msdos drivers >in this warning would be overkill. Probably changing "...it must be >VFAT!" to "...it must be VFAT (not msdos)!" would help. I've just >pushed >that change to the rEFInd git repository. > >-- >Rod Smith >rodsm...@rodsbooks.com >http://www.rodsbooks.com
Bug#942146: koji: CVE-2019-17109
Hi Salvatore, On Sun, Jan 05, 2020 at 09:02:20PM +0100, Salvatore Bonaccorso wrote: > Any news on this issue? AFAICT, the issue is fixed as well in 1.16.3, > so the smaller jump should be possible. Once fixed in unstable, can > you adress the issue as well via point release? I think it's pointless to have 1.16.x in unstable and newer koji needs newer dnf (and some other stuff, iirc), which isnt packaged in Debian, so this is not as straightforward as it seems. I'm also not sure there are many (or any?) users of koji from stable. If I were to use it, I would use koji from Fedora... https://qa.debian.org/popcon.php?package=koji seems to confirm this. -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Processed: Re: [Debichem-devel] Bug#949669: votca-csg ftbfs with gromacs 2020-2
Processing commands for cont...@bugs.debian.org: > tags 949669 + pending Bug #949669 [src:votca-csg] votca-csg ftbfs with gromacs 2020-2 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 949669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949669 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949669: [Debichem-devel] Bug#949669: votca-csg ftbfs with gromacs 2020-2
tags 949669 + pending thanks On Thu, Jan 23, 2020 at 01:55:14PM +0100, Paul Gevers wrote: > Source: votca-csg > Version: 1.5.1-1 > Severity: serious > Justification: ftbfs > Tags: ftbfs sid bullseye > > Dear maintainer, > > gromacs started a transition and I scheduled binNMUs for votca-csg. > However, they failed. Please investigate. Known issue, I just needed to wait for votca-tools to clear NEW, which it did a few hours ago. (votca-csg needs it as an updated build-dep.) Will upload the fix shortly.
Bug#940839: openshot-qt crashes immidiately
I have the same bug in 2.4.3+dfsg1-1 for sid on nvidia gpu. console output (stack dump) for you: https://gist.github.com/sej7278/9f93234a949eeaeadf676016cb46115a -- Simon John deb...@the-jedi.co.uk
Processed: Re: Bug#949683: firefox-esr: crash after upgrade from 68.4.1esr-1 to 68.4.2esr-1 in sid
Processing commands for cont...@bugs.debian.org: > forcemerge 949644 949683 Bug #949644 [libsqlite3-0] libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0 Bug #949645 [libsqlite3-0] firefox: Firefox crashes immediate upon startup. safe-mode/disabling plugins has no effect. Bug #949646 [libsqlite3-0] libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0 Bug #949647 [libsqlite3-0] firefox: Unable to lounch Bug #949648 [libsqlite3-0] firefox-esr: New version crash immediately at start Bug #949650 [libsqlite3-0] firefox: Crash at startup Bug #949657 [libsqlite3-0] firefox: Crashes on startup Bug #949668 [libsqlite3-0] firefox-esr: does not start after upgrade Bug #949646 [libsqlite3-0] libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0 Removed indication that 949646 affects firefox-esr, firefox, and thunderbird Added indication that 949646 affects thunderbird,firefox-esr,firefox Removed indication that 949644 affects firefox-esr, thunderbird, and firefox Added indication that 949644 affects thunderbird,firefox-esr,firefox Removed indication that 949645 affects firefox-esr, firefox, and thunderbird Added indication that 949645 affects thunderbird,firefox-esr,firefox Removed indication that 949647 affects firefox, firefox-esr, and thunderbird Added indication that 949647 affects thunderbird,firefox-esr,firefox Removed indication that 949648 affects firefox, firefox-esr, and thunderbird Added indication that 949648 affects thunderbird,firefox-esr,firefox Removed indication that 949650 affects firefox, firefox-esr, and thunderbird Added indication that 949650 affects thunderbird,firefox-esr,firefox Removed indication that 949657 affects firefox, firefox-esr, and thunderbird Added indication that 949657 affects thunderbird,firefox-esr,firefox Removed indication that 949668 affects firefox-esr, firefox, and thunderbird Added indication that 949668 affects thunderbird,firefox-esr,firefox Bug #949683 [libsqlite3-0] libsqlite3-0: upgrade to 3.31.0-1 breaks iceweasel (makes it crash) Severity set to 'grave' from 'serious' Removed indication that 949683 affects firefox-esr Added indication that 949683 affects thunderbird,firefox-esr,firefox Bug #949645 [libsqlite3-0] firefox: Firefox crashes immediate upon startup. safe-mode/disabling plugins has no effect. Bug #949647 [libsqlite3-0] firefox: Unable to lounch Bug #949648 [libsqlite3-0] firefox-esr: New version crash immediately at start Bug #949650 [libsqlite3-0] firefox: Crash at startup Bug #949657 [libsqlite3-0] firefox: Crashes on startup Bug #949668 [libsqlite3-0] firefox-esr: does not start after upgrade Merged 949644 949645 949646 949647 949648 949650 949657 949668 949683 > thanks Stopping processing here. Please contact me if you need assistance. -- 949644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949644 949645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949645 949646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949646 949647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949647 949648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949648 949650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949650 949657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949657 949668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949668 949683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949683 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949683: firefox-esr: crash after upgrade from 68.4.1esr-1 to 68.4.2esr-1 in sid
forcemerge 949644 949683 thanks Dixi quod… > And indeed, downgrading libsqlite3-0 from 3.31.0-1 to > 3.30.1+fossil191229-1 makes iceweasel work again. And, of course, this is already known, but either not marked as affecting firefox-esr, or reportbug, again, not showing it (#544812)… bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Processed: Re: Bug#949683: firefox-esr: crash after upgrade from 68.4.1esr-1 to 68.4.2esr-1 in sid
Processing commands for cont...@bugs.debian.org: > reassign 949683 libsqlite3-0 Bug #949683 [firefox-esr] firefox-esr: crash after upgrade from 68.4.1esr-1 to 68.4.2esr-1 in sid Bug reassigned from package 'firefox-esr' to 'libsqlite3-0'. No longer marked as found in versions firefox-esr/68.4.2esr-1. Ignoring request to alter fixed versions of bug #949683 to the same values previously set > found 949683 3.31.0-1 Bug #949683 [libsqlite3-0] firefox-esr: crash after upgrade from 68.4.1esr-1 to 68.4.2esr-1 in sid Marked as found in versions sqlite3/3.31.0-1. > notfound 949683 3.30.1+fossil191229-1 Bug #949683 [libsqlite3-0] firefox-esr: crash after upgrade from 68.4.1esr-1 to 68.4.2esr-1 in sid Ignoring request to alter found versions of bug #949683 to the same values previously set > retitle 949683 libsqlite3-0: upgrade to 3.31.0-1 breaks iceweasel (makes it > crash) Bug #949683 [libsqlite3-0] firefox-esr: crash after upgrade from 68.4.1esr-1 to 68.4.2esr-1 in sid Changed Bug title to 'libsqlite3-0: upgrade to 3.31.0-1 breaks iceweasel (makes it crash)' from 'firefox-esr: crash after upgrade from 68.4.1esr-1 to 68.4.2esr-1 in sid'. > affects 949683 firefox-esr Bug #949683 [libsqlite3-0] libsqlite3-0: upgrade to 3.31.0-1 breaks iceweasel (makes it crash) Added indication that 949683 affects firefox-esr > thanks Stopping processing here. Please contact me if you need assistance. -- 949683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949683 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949683: firefox-esr: crash after upgrade from 68.4.1esr-1 to 68.4.2esr-1 in sid
reassign 949683 libsqlite3-0 found 949683 3.31.0-1 notfound 949683 3.30.1+fossil191229-1 retitle 949683 libsqlite3-0: upgrade to 3.31.0-1 breaks iceweasel (makes it crash) affects 949683 firefox-esr thanks Dixi quod… > But this gives me some idea as to the culprit… And indeed, downgrading libsqlite3-0 from 3.31.0-1 to 3.30.1+fossil191229-1 makes iceweasel work again. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Bug#949683: firefox-esr: crash after upgrade from 68.4.1esr-1 to 68.4.2esr-1 in sid
On Thu, 23 Jan 2020, Thorsten Glaser wrote: > I’ve just upgraded my system (Debian sid) and now cannot use iceweasel > any more — after I start it and select the profile to use, it crashes; This is reproducible on two machines, both amd64. Incidentally, downgrading just the firefox-esr package does NOT fix it ⚠ According to strace, one of the processes that result from clone gets SIGSEGV. A not very useful backtrace, I need to install the symbols, is: (gdb) bt #0 0x7fffeef69df0 in ?? () from /usr/lib/firefox-esr/libxul.so #1 0x7fffeef6dbe0 in ?? () from /usr/lib/firefox-esr/libxul.so #2 0x7fffeda1fa42 in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 #3 0x7fffeda1fb8f in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 #4 0x7fffeda65650 in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 #5 0x7fffeda99851 in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 #6 0x7fffeda99a1c in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 #7 0x7fffeda99a5f in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 #8 0x7fffedaa7075 in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 #9 0x7fffedaa95f7 in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 #10 0x7fffedaae493 in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 #11 0x7fffedaae82f in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 #12 0x7fffedaae926 in sqlite3_prepare_v2 () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 #13 0x7fffeda98ecc in sqlite3_exec () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 #14 0x7fffeef659b7 in ?? () from /usr/lib/firefox-esr/libxul.so #15 0x7fffeef65f24 in ?? () from /usr/lib/firefox-esr/libxul.so #16 0x7fffeef667f3 in ?? () from /usr/lib/firefox-esr/libxul.so #17 0x7fffeef77109 in ?? () from /usr/lib/firefox-esr/libxul.so #18 0x7fffee8218da in ?? () from /usr/lib/firefox-esr/libxul.so #19 0x7fffee8232a9 in ?? () from /usr/lib/firefox-esr/libxul.so #20 0x7fffee73b60b in ?? () from /usr/lib/firefox-esr/libxul.so #21 0x7fffee73db38 in ?? () from /usr/lib/firefox-esr/libxul.so #22 0x7fffeebe535a in ?? () from /usr/lib/firefox-esr/libxul.so #23 0x7fffeebb9045 in ?? () from /usr/lib/firefox-esr/libxul.so #24 0x7fffee73dddf in ?? () from /usr/lib/firefox-esr/libxul.so #25 0x77a49e08 in ?? () from /usr/lib/x86_64-linux-gnu/libnspr4.so #26 0x77f91fb7 in start_thread (arg=) at pthread_create.c:486 #27 0x77cca2cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 (gdb) But this gives me some idea as to the culprit… bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Bug#949683: firefox-esr: crash after upgrade from 68.4.1esr-1 to 68.4.2esr-1 in sid
Package: firefox-esr Version: 68.4.2esr-1 Severity: serious Justification: stops working I’ve just upgraded my system (Debian sid) and now cannot use iceweasel any more — after I start it and select the profile to use, it crashes; the normal main screen is never even drawn. -- Package-specific info: -- Addons package information -- System Information: Debian Release: bullseye/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages firefox-esr depends on: ii debianutils 4.9.1 ii fontconfig2.13.1-2+b1 ii libasound21.2.1.2-2 ii libatk1.0-0 2.34.1-1 ii libc6 2.29-9 ii libcairo-gobject2 1.16.0-4 ii libcairo2 1.16.0-4 ii libdbus-1-3 1.12.16-2 ii libdbus-glib-1-2 0.110-5 ii libevent-2.1-72.1.11-stable-1 ii libffi7 3.3-3 ii libfontconfig12.13.1-2+b1 ii libfreetype6 2.10.1-2 ii libgcc1 1:9.2.1-24 ii libgdk-pixbuf2.0-02.40.0+dfsg-2 ii libglib2.0-0 2.62.4-1+b1 ii libgtk-3-03.24.13-1 ii libjsoncpp1 1.7.4-3+b1 ii libnspr4 2:4.24-1 ii libnss3 2:3.49.1-1 ii libpango-1.0-01.42.4-8 ii libsqlite3-0 3.31.0-1 ii libstartup-notification0 0.12-6 ii libstdc++69.2.1-24 ii libx11-6 2:1.6.8-1 ii libx11-xcb1 2:1.6.8-1 ii libxcb-shm0 1.13.1-3 ii libxcb1 1.13.1-3 ii libxcomposite11:0.4.4-2 ii libxdamage1 1:1.1.5-1 ii libxext6 2:1.3.3-1+b2 ii libxfixes31:5.0.3-1 ii libxrender1 1:0.9.10-1 ii libxt61:1.1.5-1+b3 ii procps2:3.3.15-2+b1 ii zlib1g1:1.2.11.dfsg-1+b1 Versions of packages firefox-esr recommends: ii libavcodec57 7:3.2.14-1~deb9u1 ii libavcodec58 7:4.2.1-2+b1 Versions of packages firefox-esr suggests: ii fonts-lmodern 2.004.5-6 ii fonts-stix [otf-stix] 1.1.1-4 ii libcanberra0 0.30-7 ii libgssapi-krb5-2 1.17-6 ii libgtk2.0-02.24.32-4 pn pulseaudio -- no debconf information
Bug#949682: Denial of Service due to cooking handling
Package: libmodsecurity3 Version: 3.0.3-1 Severity: serious Tags: security upstream A security issue was discovered by Ervin Hegedüs in Modsecurity 3.0.3. More info: https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/modsecurity-denial-of-service-details-cve-2019-19886/ Fixed package is already in unstable. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#933993: marked as done (ocaml-usb FTBFS because it depends on lwt.syntax)
Your message dated Thu, 23 Jan 2020 15:49:29 + with message-id and subject line Bug#933993: fixed in ocaml-usb 1.3.1-1 has caused the Debian Bug report #933993, regarding ocaml-usb FTBFS because it depends on lwt.syntax 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.) -- 933993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933993 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ocaml-usb Version: 1.3.0-4 Severity: serious Hello, As lwt is a key package and because of [1], its camlp4 dependency has been removed, removing lwt.syntax. Now, ocaml-usb FTBFS because it depends on lwt.syntax. Please provide an ocaml-usb package that does not depend on lwt.syntax or, better, on camlp4. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933722 Cheers, -- Stéphane -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: ocaml-usb Source-Version: 1.3.1-1 We believe that the bug you reported is fixed in the latest version of ocaml-usb, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 933...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stéphane Glondu (supplier of updated ocaml-usb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 23 Jan 2020 09:12:14 +0100 Source: ocaml-usb Architecture: source Version: 1.3.1-1 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Stéphane Glondu Closes: 933993 Changes: ocaml-usb (1.3.1-1) unstable; urgency=medium . [ Stéphane Glondu ] * New upstream release (Closes: #933993) * Update Vcs-* * Update Homepage and debian/watch * Bump debhelper compat level to 12 * Bump Standards-Version to 4.4.1 * Add Rules-Requires-Root: no . [ Nicolas Dandrimont ] * d/control: remove myself from Uploaders Checksums-Sha1: 09855dd142774c3daf0a373018f35fb4d6bc 1880 ocaml-usb_1.3.1-1.dsc 7f7cc46c6fddb522d3c53fe997458c3d138b30c1 19976 ocaml-usb_1.3.1.orig.tar.gz 1c5dca2972decfa8e71ffb06799286279e21fa56 3632 ocaml-usb_1.3.1-1.debian.tar.xz Checksums-Sha256: d625a8a21597adfa4491ce055a44ea8627958eab20deb61f921cc73649d471f5 1880 ocaml-usb_1.3.1-1.dsc 1543e18e33cc7efa652370d5163e914858d5d8e5be496d2e6fbdbfe40e8cdff2 19976 ocaml-usb_1.3.1.orig.tar.gz 127cc35cd99a31472a1b536cadfc41867544f59b19e1a4016e1c5669888610a7 3632 ocaml-usb_1.3.1-1.debian.tar.xz Files: 5d034b5ba564859dae3e9de4db4b37d0 1880 ocaml optional ocaml-usb_1.3.1-1.dsc 395b8f1593e8cbb3e5c8472158b5331c 19976 ocaml optional ocaml-usb_1.3.1.orig.tar.gz d79c95ed964d12e1eea5aab7f9320d21 3632 ocaml optional ocaml-usb_1.3.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAl4puxQACgkQIbju8bGJ MIE3owf+N+OXPehPxXPew7FOGLPI0WLjlba6SilMShFo6sUsypsYg9mDub9OYRIy /M+K6OmdrjcVPV8eMoXcFmx/ih+JvNlKbArVpmryj7nHtaSXMCEAKDPhFtz4BpDe J0ozRps0RRdfoXQIWFTYe3m/yx3pbJNY/3MLyXd6xZTGwOwUHZqDr+KG4yNAJCr0 OGAN5XfSxRz6zQiYU3gS6UYe5hlm2YqWguvIGz9h7DhthaBMJWeXGNbzbvtIdZPU BDniDVL37SINV256xSriHbP6LQIIzsU8FdBRncb7UUOs7/ILcTnLmT495sLZNcaK buvQt5nEqR5Ifoe89TGL6XtDicPcNg== =E9pq -END PGP SIGNATURE End Message ---
Processed: py2removal bugs severity updates - 2020-01-23 15:35:25.132473+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # and https://lists.debian.org/debian-python/2019/12/msg00076.html > # mail threads for more details on this severity update > # sat-xmpp-core is an application, has low popcon (23 < 300), and has 0 > external rdeps or not in testing > # sat-xmpp-primitivus is an application, has low popcon (16 < 300), and has 0 > external rdeps or not in testing > # sat-xmpp-jp is an application, has low popcon (17 < 300), and has 0 > external rdeps or not in testing > severity 935358 serious Bug #935358 [src:salutatoi] salutatoi: Please port to Python 3 and/or drop Python 2 package (rdep of python-progressbar) Severity set to 'serious' from 'normal' > # python-netifaces is a module and has 0 external rdeps or not in testing > severity 937129 serious Bug #937129 [src:netifaces] netifaces: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-feed is a module and has 0 external rdeps or not in testing > severity 937437 serious Bug #937437 [src:pyfeed] pyfeed: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-html2text is a module and has 0 external rdeps or not in testing > severity 937815 serious Bug #937815 [src:python-html2text] python-html2text: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-omemo-backend-signal is a module and has 0 external rdeps or not in > testing > severity 937969 serious Bug #937969 [src:python-omemo-backend-signal] python-omemo-backend-signal: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-potr is a module and has 0 external rdeps or not in testing > severity 938041 serious Bug #938041 [src:python-potr] python-potr: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-shortuuid is a module and has 0 external rdeps or not in testing > severity 938478 serious Bug #938478 [src:shortuuid] shortuuid: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-wokkel is a module and has 0 external rdeps or not in testing > severity 938830 serious Bug #938830 [src:wokkel] wokkel: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 935358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935358 937129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937129 937437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937437 937815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937815 937969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937969 938041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938041 938478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938478 938830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938830 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949658: r-cran-rlang: autopkgtest regression
On Thu, Jan 23, 2020 at 03:44:44PM +0100, Andreas Tille wrote: > On Thu, Jan 23, 2020 at 12:10:51PM +0200, Graham Inggs wrote: > > However, when tested against other packages in unstable, its autopkgtests > > pass [2]. I think this suggests that either r-cran-rlang itself, or > > r-cran-rlang's autopkgtests, are missing a versioned dependency against > > another package in unstable. > > Experimentation in Ubuntu leads me to r-cran-testthat >= 2.3. > > Hmmm, I'd prefer that r-cran-testthat 2.3.1 would migrate to testing > which I'm just doing in another upload with > >Test-Depends: r-cran-rspectra, r-cran-igraph, r-cran-rann > > I hope this will solve both issues (testthat and rlang) in one shot. H, I think I was wrong the excuses is mentioning a regression in r-cran-recipes. While the log specifies a hint that the said test-depends are missing there the debci page says "PASS" so these are optional. I wonder what exactly might be the problem here. BTW, since you were mentioning your tests on Ubuntu: You are kindly invited to always do team uploads in r-pkg team if you think you have a fix for any issue. Kind regards Andreas. -- http://fam-tille.de
Bug#949644: libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0
I can also confirm, manually downgrading via dpkg fixes the instant crash issue. Am 23.01.20 um 16:16 schrieb Rastersoft: I can confirm it too: after downgrading to the version from testing, both firefox and thunderbird do work again.
Bug#949542: C++ help needed for pbdagcon
> On Jan 22, 2020, at 11:56, Andreas Tille wrote:
>
> Control: tags -1 help
>
> I have fixed Python2->Python3 migration as well as the FTBFS with
> pbseqlib 5.3.3+dfsg-1 issue in Git[1]. Unfortunately there is another
> build issue in the C++ code which I have no idea how to fix:
>
>
> ...
> g++ -g -O2 -fdebug-prefix-map=/build/pbdagcon-0.3+git20180411.c14c422+ds=.
> -fstack-protector-strong -Wformat -Werror=format-security -O3 -std=c++14
> -Wall -Wuninitialized -pedantic -Wdate-time -D_FORTIFY_SOURCE=2 -MMD -MP
> -I/build/pbdagcon-0.3+git20180411.c14c422+ds/DAZZ_DB
> -I/build/pbdagcon-0.3+git20180411.c14c422+ds/DALIGNER
> -I/usr/include/pbseq/alignment -I/usr/include/pbseq/pbdata
> -I/usr/include/pbseq/hdf -I/usr/include/pbseq -isystem.//third-party -c -o
> DazAlnProvider.o DazAlnProvider.cpp
> In file included from DazAlnProvider.cpp:10:
> DazAlnProvider.hpp:97:19: error: expected ')' before '&' token
> 97 | Target(DAZZ_DB& db, int tspace, int small);
> | ~ ^
> | )
> DazAlnProvider.hpp:122:5: error: 'DAZZ_DB' does not name a type
> 122 | DAZZ_DB db_;
> | ^~~
> DazAlnProvider.hpp:161:5: error: 'DAZZ_DB' does not name a type
> 161 | DAZZ_DB db_;
> | ^~~
> DazAlnProvider.cpp: In constructor 'DazAlnProvider::DazAlnProvider(const
> ProgramOpts&)':
> DazAlnProvider.cpp:34:33: error: 'db_' was not declared in this scope
> 34 | int status = Open_DB(path, _);
> | ^~~
> DazAlnProvider.cpp: In destructor 'virtual DazAlnProvider::~DazAlnProvider()':
> DazAlnProvider.cpp:74:15: error: 'db_' was not declared in this scope
> 74 | Close_DB(_);
> | ^~~
> DazAlnProvider.cpp: In member function 'virtual bool
> DazAlnProvider::nextTarget(std::string&, std::vector&)':
> DazAlnProvider.cpp:125:25: error: 'db_' was not declared in this scope
> 125 | seq = Load_Subread(_, trg_->id, 0, trg_->length, targSeqBuf_,
> 0);
> | ^~~
> DazAlnProvider.cpp: At global scope:
> DazAlnProvider.cpp:225:15: error: expected constructor, destructor, or type
> conversion before '(' token
> 225 | Target::Target(DAZZ_DB& db, int tspace, int small) :
> | ^
> DazAlnProvider.cpp: In member function 'void Target::firstRecord(Record&,
> bool)':
> DazAlnProvider.cpp:246:14: error: 'db_' was not declared in this scope
> 246 | length = db_.reads[id].rlen;
> | ^~~
Just taking some educated guesses here, but the way this variable is used
indicates to me that the code expects it to be a HITS_DB, declared in
DAZZ_DB/DB.h. The DAZZ_DB subdirectory looks like a copy of upstream project
https://github.com/thegenemyers/DAZZ_DB
. The latest revision of this calls
this type DAZZ_DB, not HITS_DB. So maybe the solution is to pull in the latest
revision of this?
Bug#949644: libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0
I can confirm it too: after downgrading to the version from testing, both firefox and thunderbird do work again.
Bug#943994: marked as done (python3-zeitgeist not compatible with python3)
Your message dated Thu, 23 Jan 2020 15:16:07 + with message-id and subject line Bug#943994: fixed in zeitgeist 1.0.2-3 has caused the Debian Bug report #943994, regarding python3-zeitgeist not compatible with python3 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 943994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-zeitgeist Version: 1.0.2-2 Severity: serious Hi, When installing python3-zeitgeist, the bytecompilation fails with the following error: Paramétrage de python3-zeitgeist (1.0.2-2) ... File "/usr/lib/python3/dist-packages/zeitgeist/client.py", line 121 except dbus.exceptions.DBusException, e: ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/zeitgeist/datamodel.py", line 144 except KeyError, e: ^ SyntaxError: invalid syntax dpkg: erreur de traitement du paquet python3-zeitgeist (--configure) : installed python3-zeitgeist package post-installation script subprocess returned error exit status 1 Looks like it's not compatible with python3. Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-1-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages python3-zeitgeist depends on: ii python3 3.7.5-1 ii python3-dbus 1.2.12-1 ii python3-gi3.34.0-1 ii python3-xdg 0.25-5 python3-zeitgeist recommends no packages. python3-zeitgeist suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: zeitgeist Source-Version: 1.0.2-3 We believe that the bug you reported is fixed in the latest version of zeitgeist, 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. Boyuan Yang (supplier of updated zeitgeist 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, 22 Jan 2020 17:54:33 -0500 Source: zeitgeist Architecture: source Version: 1.0.2-3 Distribution: unstable Urgency: high Maintainer: Debian QA Group Changed-By: Boyuan Yang Closes: 943994 Changes: zeitgeist (1.0.2-3) unstable; urgency=high . * QA upload. * debian/patches/backport: + Backport upstream patch to fix compatibility with gettext 0.20+. * debian/patches: Add patch to fix grammar error in python3-zeitgeist packages. (Closes: #943994) * debian/rules: Do not pass --exclude parameter to dh_missing. * debian/control: + Bump Standards-Version to 4.5.0. + Update package description for python3-zeitgeist and recommend users to use the GIR binding with python3. * debian/not-installed: Explicitly do not install libtool .la files. Checksums-Sha1: dfe142372432bc8d58052ab7494e663f7a4fa767 2726 zeitgeist_1.0.2-3.dsc 7829624bff958e7f3f882a7a101b48d66768f8f8 17404 zeitgeist_1.0.2-3.debian.tar.xz 7e15da0d4450a140009d1dfa01d4fc6e829c31bc 18501 zeitgeist_1.0.2-3_amd64.buildinfo Checksums-Sha256: 78aa5ec7f5b2a8f47a3e48c5cd78e9848712c4161ac4eb9974b7b9df1725cd54 2726 zeitgeist_1.0.2-3.dsc 855adc129bee558c0de372d26aee7a969beb2c270ed25400bcae7f2a0db3fe9e 17404 zeitgeist_1.0.2-3.debian.tar.xz 2815f8a8ae8f6ed30bc5b72e619701e3c27030d7761f636dde725c7061794e0a 18501 zeitgeist_1.0.2-3_amd64.buildinfo Files: 2d95309fbe220d00eeb91e4d2e5b1093 2726 utils optional zeitgeist_1.0.2-3.dsc b49be2d487f2b12d962abea774e194f6 17404 utils optional zeitgeist_1.0.2-3.debian.tar.xz 0e341afe44dc4f2b51205eab011f1f69 18501 utils optional zeitgeist_1.0.2-3_amd64.buildinfo -BEGIN PGP SIGNATURE-
Bug#949596: marked as done (mycli fails to run - sqlparse issue)
Your message dated Thu, 23 Jan 2020 15:05:57 +
with message-id
and subject line Bug#949596: fixed in mycli 1.20.1-3
has caused the Debian Bug report #949596,
regarding mycli fails to run - sqlparse issue
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.)
--
949596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mycli
Version: 1.20.1-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
This is a new install of mycli. On running the program and trying to connect to
a database the root user
can connect to with the mysql client the following error trace comes up:
root# mycli mythconverg
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 583, in
_build_master
ws.require(__requires__)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 900, in
require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 791, in
resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (sqlparse 0.2.4
(/usr/lib/python3/dist-packages), Requirement.parse('sqlparse<0.4.0,>=0.3.0'),
{'mycli'})
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/mycli", line 6, in
from pkg_resources import load_entry_point
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3251,
in
@_call_aside
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3235,
in _call_aside
f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3264,
in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 585, in
_build_master
return cls._build_from_requirements(__requires__)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 598, in
_build_from_requirements
dists = ws.resolve(reqs, Environment())
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 786, in
resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'sqlparse<0.4.0,>=0.3.0' distribution
was not found and is required by mycli
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.0-3-amd64 (SMP w/6 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages mycli depends on:
ii python3 3.7.5-3
ii python3-click 7.0-3
ii python3-configobj 5.0.6-3
ii python3-cryptography2.6.1-4
ii python3-pkg-resources 44.0.0-1
ii python3-prompt-toolkit 2.0.10-2
ii python3-pygments2.3.1+dfsg-1
ii python3-pymysql 0.9.3-2
ii python3-sqlparse0.2.4-3
ii python3-tabulate0.8.2-1.1
ii python3-terminaltables 3.1.0-3
mycli recommends no packages.
mycli suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mycli
Source-Version: 1.20.1-3
We believe that the bug you reported is fixed in the latest version of
mycli, 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 949...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Lennart Weller (supplier of updated mycli 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, 22 Jan 2020 17:40:08 +0100
Source: mycli
Binary: mycli
Architecture: source all
Version: 1.20.1-3
Distribution: unstable
Urgency: medium
Maintainer: Lennart Weller
Changed-By: Lennart Weller
Description:
mycli - CLI for MySQL/MariaDB
Closes: 949596
Changes:
mycli (1.20.1-3) unstable;
Processed: mesa breaks build of kcrash, konsole and libkscreen as tested in autopkgtest migration setup
Processing control commands: > found -1 mesa/19.3.2-1 Bug #949677 [src:mesa, src:kcrash, src:konsole, src:libkscreen] mesa breaks build of kcrash, konsole and libkscreen as tested in autopkgtest migration setup Marked as found in versions mesa/19.3.2-1. > found -1 kcrash/5.62.0-1 Bug #949677 [src:mesa, src:kcrash, src:konsole, src:libkscreen] mesa breaks build of kcrash, konsole and libkscreen as tested in autopkgtest migration setup Marked as found in versions kcrash/5.62.0-1. > found -1 konsole/4:19.08.1-2 Bug #949677 [src:mesa, src:kcrash, src:konsole, src:libkscreen] mesa breaks build of kcrash, konsole and libkscreen as tested in autopkgtest migration setup Marked as found in versions konsole/4:19.08.1-2. > found -1 libkscreen/4:5.14.5-1 Bug #949677 [src:mesa, src:kcrash, src:konsole, src:libkscreen] mesa breaks build of kcrash, konsole and libkscreen as tested in autopkgtest migration setup Marked as found in versions libkscreen/4:5.14.5-1. -- 949677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949677 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949677: mesa breaks build of kcrash, konsole and libkscreen as tested in autopkgtest migration setup
Source: mesa, kcrash, konsole, libkscreen Control: found -1 mesa/19.3.2-1 Control: found -1 kcrash/5.62.0-1 Control: found -1 konsole/4:19.08.1-2 Control: found -1 libkscreen/4:5.14.5-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainers, With a recent upload of mesa the autopkgtest of kcrash, konsole and libkscreen fails in testing during building of the source package when that autopkgtest is run with the binary packages of mesa from unstable. It passes when run with only packages from testing. In tabular form (for kcrash): passfail mesa from testing19.3.2-1 kcrash from testing5.62.0-1 versioned deps [0] from testingfrom unstable all others from testingfrom testing It also passes in unstable. Nearly always that points at missing versioned dependencies somewhere, so it would be good to track that down, such that the autopkgtest pass in our migration tests as well. I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of mesa to testing [1]. Due to the nature of this issue, I filed this bug report against all packages. Can you please investigate the situation and reassign the bug to the right package? 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 mesa/19.3.2-1. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=mesa https://ci.debian.net/data/autopkgtest/testing/amd64/k/kcrash/4071010/log.gz Determining if the function shmat exists passed with the following output: Change Dir: /tmp/autopkgtest-lxc.ov32kph5/downtmp/build.7JK/src/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp Run Build Command(s):/usr/bin/make cmTC_c5c84/fast && make[2]: Entering directory '/tmp/autopkgtest-lxc.ov32kph5/downtmp/build.7JK/src/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' /usr/bin/make -f CMakeFiles/cmTC_c5c84.dir/build.make CMakeFiles/cmTC_c5c84.dir/build make[3]: Entering directory '/tmp/autopkgtest-lxc.ov32kph5/downtmp/build.7JK/src/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' Building C object CMakeFiles/cmTC_c5c84.dir/CheckFunctionExists.c.o /usr/bin/cc -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -g -O2 -fdebug-prefix-map=/tmp/autopkgtest-lxc.ov32kph5/downtmp/build.7JK/src=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=iso9899:1990 -fno-common -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wmissing-format-attribute -Wwrite-strings -Werror=implicit-function-declaration -DCHECK_FUNCTION_EXISTS=shmat -o CMakeFiles/cmTC_c5c84.dir/CheckFunctionExists.c.o -c /usr/share/cmake-3.15/Modules/CheckFunctionExists.c Linking C executable cmTC_c5c84 /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_c5c84.dir/link.txt --verbose=1 /usr/bin/cc -g -O2 -fdebug-prefix-map=/tmp/autopkgtest-lxc.ov32kph5/downtmp/build.7JK/src=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=iso9899:1990 -fno-common -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wmissing-format-attribute -Wwrite-strings -Werror=implicit-function-declaration -DCHECK_FUNCTION_EXISTS=shmat -Wl,--enable-new-dtags -Wl,-z,relro -Wl,--as-needed CMakeFiles/cmTC_c5c84.dir/CheckFunctionExists.c.o -o cmTC_c5c84 make[3]: Leaving directory '/tmp/autopkgtest-lxc.ov32kph5/downtmp/build.7JK/src/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' make[2]: Leaving directory '/tmp/autopkgtest-lxc.ov32kph5/downtmp/build.7JK/src/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' dh_auto_configure: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_USE_QT_SYS_PATHS=ON -DBUILD_QCH=ON .. returned exit code 1 make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 2 make[1]: Leaving directory '/tmp/autopkgtest-lxc.ov32kph5/downtmp/build.7JK/src' make: *** [debian/rules:7: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 signature.asc Description: OpenPGP digital signature
Bug#949658: r-cran-rlang: autopkgtest regression
On Thu, Jan 23, 2020 at 12:10:51PM +0200, Graham Inggs wrote: > However, when tested against other packages in unstable, its autopkgtests > pass [2]. I think this suggests that either r-cran-rlang itself, or > r-cran-rlang's autopkgtests, are missing a versioned dependency against > another package in unstable. > Experimentation in Ubuntu leads me to r-cran-testthat >= 2.3. Hmmm, I'd prefer that r-cran-testthat 2.3.1 would migrate to testing which I'm just doing in another upload with Test-Depends: r-cran-rspectra, r-cran-igraph, r-cran-rann I hope this will solve both issues (testthat and rlang) in one shot. Kind regards Andreas. -- http://fam-tille.de
Bug#938445: sciscipy: Python2 removal in sid/bullseye
Hello, Le 20/01/2020 à 16:07, Stuart Prescott a écrit : Dear maintainer, sciscipy appears not to be under current upstream development and porting to Python 3 has not started. This is perhaps unlikely to be completed for a low popcon package where upstream is not driving the process. If python3-sciscipy is not likely to be ready for release with bullseye, is it then a candidate for removal from Debian now? (It would have to go through NEW regardless of whether it is removed then reintroduced or simply ported to have a new binary package.) yeah, we should remove it, i will take care of this S
Bug#949676: pyspread: autopkgtest failure: deprecation warnings on stderr
Source: pyspread Version: 1.99.0.1-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainers, With a recent upload of pyspread you added autopkgtest to your package, great. However, it fails. I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? Please either fix the deprecation warning, suppress deprecation warnings (preferred for autopkgtests) or allow output to stderr (via the allow-stderr restriction). More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=pyspread https://ci.debian.net/data/autopkgtest/testing/amd64/p/pyspread/4017003/log.gz autopkgtest [21:14:11]: test command1: sh debian/tests/runtests.sh autopkgtest [21:14:11]: test command1: [--- running pytest WARNING: Testing via this command is deprecated and will be removed in a future version. Users looking for a generic test entry point independent of test runner are encouraged to use tox. running egg_info writing pyspread.egg-info/PKG-INFO writing dependency_links to pyspread.egg-info/dependency_links.txt writing requirements to pyspread.egg-info/requires.txt writing top-level names to pyspread.egg-info/top_level.txt reading manifest file 'pyspread.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'LICENSE' under directory 'share' warning: no previously-included files matching '*.pyc' found under directory 'src' writing manifest file 'pyspread.egg-info/SOURCES.txt' running build_ext = test session starts == platform linux -- Python 3.7.6, pytest-4.6.7, py-1.8.0, pluggy-0.13.0 rootdir: /tmp/autopkgtest-lxc.89zt0u_p/downtmp/build.jT7/src plugins: xvfb-1.2.0 collected 157 items src/lib/test/test_hashing.py . [ 5%] src/lib/test/test_selection.py . [ 31%] ... [ 51%] src/lib/test/test_string_helpers.py .. [ 63%] src/model/test/test_model.py ... [ 90%] [ 92%] src/test/test_actions.py ... [100%] == 157 passed in 4.90 seconds == autopkgtest [21:14:17]: test command1: ---] autopkgtest [21:14:17]: test command1: - - - - - - - - - - results - - - - - - - - - - command1 FAIL stderr: WARNING: Testing via this command is deprecated and will be removed in a future version. Users looking for a generic test entry point independent of test runner are encouraged to use tox. autopkgtest [21:14:17]: test command1: - - - - - - - - - - stderr - - - - - - - - - - WARNING: Testing via this command is deprecated and will be removed in a future version. Users looking for a generic test entry point independent of test runner are encouraged to use tox. warning: no files found matching 'LICENSE' under directory 'share' signature.asc Description: OpenPGP digital signature
Bug#949659: r-cran-parameters: autopkgtest regression
Hi Graham, thanks for your bug report. On Thu, Jan 23, 2020 at 12:21:50PM +0200, Graham Inggs wrote: > > E: Package 'r-cran-brms' has no installation candidate The excuses page says: autopkgtest for r-cran-brms/2.11.0-1: amd64: Regression ♻ , arm64: Regression ♻ and refers in the Regression link to https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-brms/3988759/log.gz which has: ... Get:102 http://deb.debian.org/debian testing/main amd64 r-cran-loo all 2.1.0-1 [2,131 kB] ... Loading required package: Rcpp Error: package or namespace load failed for ‘brms’: object ‘.compute_point_estimate’ is not exported by 'namespace:loo' Execution halted That's pretty strange since r-cran-loo has 2.2.0-1 in unstable *and* testing. I think it would be wrong to force some versioned Depends here since r-cran-brms has no explicit dependency from r-cran-loo. IMHO this issue is caused by a not up to date debci environment for testing. > E: Package 'r-cran-caic4' has no installation candidate That's a bit unfortunate. The package was accepted but needs a source only upload to migrate. I intended to do this just with latest upstream version but its waiting for r-cran-rlrsim in new (#948264). Since I see other issues I don't intend to push things here and wait for ftpmaster some more days. > E: Package 'r-cran-nfactors' has no installation candidate Argh: Not built on buildd: arch all binaries uploaded by tille, a new source-only upload is needed to allow migration IMHO the fact that we can not do source uploads to new but source upload to testing is a real nuisance and will probably beat us several times. Just building and uploading ... > E: Package 'r-cran-rstanarm' has no installation candidate That's extremely strange. r-cran-rstanarm (2.19.2-1) unstable; urgency=medium ... * Test-Depends: r-cran-codetools -- Andreas Tille Mon, 07 Oct 2019 17:58:15 +0200 I verified that this was really uploaded and $ cat debian/tests/control Tests: run-unit-test Depends: @, r-cran-testthat, r-cran-stanheaders (>= 2.18.1-10-2), r-cran-bh, r-cran-codetools Restrictions: allow-stderr But it seems that codetools has an issue here: $ curl --silent https://ci.debian.net/data/autopkgtest/unstable/amd64/r/r-cran-rstanarm/4018302/log.gz | zcat | grep codetools r-cran-callr r-cran-checkmate r-cran-cli r-cran-codetools r-cran-colorspace r-cran-callr r-cran-checkmate r-cran-cli r-cran-codetools r-cran-colorspace Get:204 http://deb.debian.org/debian unstable/main amd64 r-cran-codetools all 0.2-16-1 [90.1 kB] Selecting previously unselected package r-cran-codetools. Preparing to unpack .../203-r-cran-codetools_0.2-16-1_all.deb ... Unpacking r-cran-codetools (0.2-16-1) ... Setting up r-cran-codetools (0.2-16-1) ... r-cran-tikzdevice r-cran-codetools r-cran-runit r-cran-sodium code for methods in class “Rcpp_model_bernoulli” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?) code for methods in class “Rcpp_model_bernoulli” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?) code for methods in class “Rcpp_model_binomial” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?) code for methods in class “Rcpp_model_binomial” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?) code for methods in class “Rcpp_model_continuous” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?) code for methods in class “Rcpp_model_continuous” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?) code for methods in class “Rcpp_model_count” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?) code for methods in class “Rcpp_model_count” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?) code for methods in class “Rcpp_model_jm” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?) code for methods in class “Rcpp_model_jm” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?) code for methods in class “Rcpp_model_lm” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?) code for methods in class “Rcpp_model_lm” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?) code for methods in class “Rcpp_model_mvmer” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?) code for methods in class “Rcpp_model_mvmer” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?) code for methods in class “Rcpp_model_polr” was not checked for suspicious field assignments (recommended package
Bug#949130: refind-install fails to determine the ESP partition
On 1/22/20 6:54 PM, Tianon Gravi wrote: > On Sun, 19 Jan 2020 at 09:40, Pelzi wrote: >> I found the cure for the problem: the ESP partition was listed as fs type >> „msdos“ in fstab. Changing this to „vfat" made refind-install work for me. > > Ah nice catch! So it sounds like at most, this should be an upstream > feature request to have refind-install warn if fstab includes > "/boot/efi" but it's not vfat or something like that? Sorry for not responding earlier, but I've been suffering from an ear infection lately that's made it hard to do much of anything. In any event, refind-install already warns of this, and that warning was shown in the output presented earlier: > $ sudo refind-install > ShimSource is none > Installing rEFInd on Linux > The ESP doesn't seem to be mounted! Trying to find it > mount: /boot/efi: /dev/sda2 already mounted on /boot/efi. > boot/efi doesn't seem to be on a VFAT filesystem. The ESP must be > mounted at //boot or //boot/efi and it must be VFAT! Aborting! That said, the warning could admittedly be more explicit that msdos is not an acceptable filesystem driver in this context. OTOH, presenting a disseration on the differences between the Linux vfat and msdos drivers in this warning would be overkill. Probably changing "...it must be VFAT!" to "...it must be VFAT (not msdos)!" would help. I've just pushed that change to the rEFInd git repository. -- Rod Smith rodsm...@rodsbooks.com http://www.rodsbooks.com
Processed: tagging 949620, severity of 949620 is important
Processing commands for cont...@bugs.debian.org: > tags 949620 - a11y Bug #949620 [src:linux] BUG: kernel NULL pointer dereference, address: 0040 Removed tag(s) a11y. > severity 949620 important Bug #949620 [src:linux] BUG: kernel NULL pointer dereference, address: 0040 Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 949620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949620 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925720: marked as done (isc-dhcp: ftbfs with GCC-9)
Your message dated Thu, 23 Jan 2020 13:04:48 + with message-id and subject line Bug#925720: fixed in isc-dhcp 4.4.1-2.1 has caused the Debian Bug report #925720, regarding isc-dhcp: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 925720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:isc-dhcp Version: 4.4.1-2 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-9 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc9-20190321/isc-dhcp_4.4.1-2_unstable_gcc9.log The last lines of the build log are at the end of this report. To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-9/porting_to.html GCC 9 also passes the linker option --as-needed by default; typical build issues are passing libraries before object files to the linker, or underlinking of convenience libraries built from the same source. [...] make[4]: Entering directory '/<>/common/tests' Making all in . make[5]: Entering directory '/<>/common/tests' make[5]: Nothing to be done for 'all-am'. make[5]: Leaving directory '/<>/common/tests' make[4]: Leaving directory '/<>/common/tests' make[3]: Leaving directory '/<>/common' Making all in omapip make[3]: Entering directory '/<>/omapip' gcc -DHAVE_CONFIG_H -I. -I../includes -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -I/usr/include/bind-export -DCALL_SCRIPT_ON_ONETRY_FAIL -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -D_PATH_DHCPD_CONF='"/etc/dhcp/dhcpd.conf"' -D_PATH_DHCPD_DB='"/var/lib/dhcp/dhcpd.leases"' -D_PATH_DHCPD6_DB='"/var/lib/dhcp/dhcpd6.leases"' -D_PATH_DHCLIENT_SCRIPT='"/sbin/dhclient-script"' -D_PATH_DHCLIENT_CONF='"/etc/dhcp/dhclient.conf"' -D_PATH_DHCLIENT_DB='"/var/lib/dhcp/dhclient.leases"' -D_PATH_DHCLIENT6_DB='"/var/lib/dhcp/dhclient6.leases"' -DNSUPDATE -I../includes -I/usr/include -MT test.o -MD -MP -MF .deps/test.Tpo -c -o test.o test.c mv -f .deps/test.Tpo .deps/test.Po gcc -DHAVE_CONFIG_H -I. -I../includes -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -I/usr/include/bind-export -DCALL_SCRIPT_ON_ONETRY_FAIL -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -D_PATH_DHCPD_CONF='"/etc/dhcp/dhcpd.conf"' -D_PATH_DHCPD_DB='"/var/lib/dhcp/dhcpd.leases"' -D_PATH_DHCPD6_DB='"/var/lib/dhcp/dhcpd6.leases"' -D_PATH_DHCLIENT_SCRIPT='"/sbin/dhclient-script"' -D_PATH_DHCLIENT_CONF='"/etc/dhcp/dhclient.conf"' -D_PATH_DHCLIENT_DB='"/var/lib/dhcp/dhclient.leases"' -D_PATH_DHCLIENT6_DB='"/var/lib/dhcp/dhclient6.leases"' -DNSUPDATE -I../includes -I/usr/include -MT protocol.o -MD -MP -MF .deps/protocol.Tpo -c -o protocol.o protocol.c mv -f .deps/protocol.Tpo .deps/protocol.Po gcc -DHAVE_CONFIG_H -I. -I../includes -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -I/usr/include/bind-export -DCALL_SCRIPT_ON_ONETRY_FAIL -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -D_PATH_DHCPD_CONF='"/etc/dhcp/dhcpd.conf"' -D_PATH_DHCPD_DB='"/var/lib/dhcp/dhcpd.leases"' -D_PATH_DHCPD6_DB='"/var/lib/dhcp/dhcpd6.leases"' -D_PATH_DHCLIENT_SCRIPT='"/sbin/dhclient-script"' -D_PATH_DHCLIENT_CONF='"/etc/dhcp/dhclient.conf"' -D_PATH_DHCLIENT_DB='"/var/lib/dhcp/dhclient.leases"' -D_PATH_DHCLIENT6_DB='"/var/lib/dhcp/dhclient6.leases"' -DNSUPDATE -I../includes -I/usr/include
Bug#949669: votca-csg ftbfs with gromacs 2020-2
Source: votca-csg Version: 1.5.1-1 Severity: serious Justification: ftbfs Tags: ftbfs sid bullseye Dear maintainer, gromacs started a transition and I scheduled binNMUs for votca-csg. However, they failed. Please investigate. Paul https://buildd.debian.org/status/package.php?p=votca-csg Tail of log for votca-csg on amd64: | ^~~~ In file included from /usr/include/gromacs/trajectory/trajectoryframe.h:50, from /<>/src/libcsg/modules/io/gmxtrajectorywriter.h:28, from /<>/src/libcsg/trajectorywriter.cc:30: /usr/include/gromacs/utility/arrayref.h:273:106: error: expected unqualified-id before ‘>’ token 273 | ArrayRef::value, const typename T::value_type, typename T::value_type>> | ^~ make[3]: *** [src/libcsg/CMakeFiles/votca_csg.dir/build.make:404: src/libcsg/CMakeFiles/votca_csg.dir/trajectorywriter.cc.o] Error 1 make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:396: src/libcsg/CMakeFiles/votca_csg.dir/all] Error 2 make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[1]: *** [Makefile:133: all] Error 2 make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu' dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j4 "INSTALL=install --strip-program=true" returned exit code 2 make: *** [debian/rules:29: binary-arch] Error 25 signature.asc Description: OpenPGP digital signature
Processed: more sqlite + firefox snafu merge
Processing commands for cont...@bugs.debian.org: > reassign 949650 libsqlite3-0 Bug #949650 [firefox] firefox: Crash at startup Bug reassigned from package 'firefox' to 'libsqlite3-0'. No longer marked as found in versions firefox/72.0.2-1. Ignoring request to alter fixed versions of bug #949650 to the same values previously set > reassign 949657 libsqlite3-0 Bug #949657 [firefox] firefox: Crashes on startup Bug reassigned from package 'firefox' to 'libsqlite3-0'. No longer marked as found in versions firefox/72.0.2-1. Ignoring request to alter fixed versions of bug #949657 to the same values previously set > reassign 949668 libsqlite3-0 Bug #949668 [firefox-esr] firefox-esr: does not start after upgrade Bug reassigned from package 'firefox-esr' to 'libsqlite3-0'. No longer marked as found in versions firefox-esr/68.4.2esr-1. Ignoring request to alter fixed versions of bug #949668 to the same values previously set > forcemerge 949644 949650 949657 949668 Bug #949644 [libsqlite3-0] libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0 Bug #949645 [libsqlite3-0] firefox: Firefox crashes immediate upon startup. safe-mode/disabling plugins has no effect. Bug #949646 [libsqlite3-0] libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0 Bug #949647 [libsqlite3-0] firefox: Unable to lounch Bug #949648 [libsqlite3-0] firefox-esr: New version crash immediately at start Bug #949645 [libsqlite3-0] firefox: Firefox crashes immediate upon startup. safe-mode/disabling plugins has no effect. Removed indication that 949645 affects firefox and firefox-esr Added indication that 949645 affects firefox-esr,firefox Removed indication that 949644 affects firefox-esr and firefox Added indication that 949644 affects firefox-esr,firefox Removed indication that 949646 affects firefox-esr and firefox Added indication that 949646 affects firefox-esr,firefox Removed indication that 949647 affects firefox and firefox-esr Added indication that 949647 affects firefox-esr,firefox Removed indication that 949648 affects firefox-esr and firefox Added indication that 949648 affects firefox-esr,firefox Bug #949657 [libsqlite3-0] firefox: Crashes on startup Severity set to 'grave' from 'important' Added indication that 949657 affects firefox-esr,firefox Marked as found in versions sqlite3/3.31.0-1. Bug #949650 [libsqlite3-0] firefox: Crash at startup Severity set to 'grave' from 'normal' Added indication that 949650 affects firefox-esr,firefox Marked as found in versions sqlite3/3.31.0-1. Bug #949668 [libsqlite3-0] firefox-esr: does not start after upgrade Added indication that 949668 affects firefox-esr,firefox Marked as found in versions sqlite3/3.31.0-1. Bug #949646 [libsqlite3-0] libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0 Bug #949647 [libsqlite3-0] firefox: Unable to lounch Bug #949648 [libsqlite3-0] firefox-esr: New version crash immediately at start Merged 949644 949645 949646 949647 949648 949650 949657 949668 > affects 949644 thunderbird Bug #949644 [libsqlite3-0] libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0 Bug #949645 [libsqlite3-0] firefox: Firefox crashes immediate upon startup. safe-mode/disabling plugins has no effect. Bug #949646 [libsqlite3-0] libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0 Bug #949647 [libsqlite3-0] firefox: Unable to lounch Bug #949648 [libsqlite3-0] firefox-esr: New version crash immediately at start Bug #949650 [libsqlite3-0] firefox: Crash at startup Bug #949657 [libsqlite3-0] firefox: Crashes on startup Bug #949668 [libsqlite3-0] firefox-esr: does not start after upgrade Added indication that 949644 affects thunderbird Added indication that 949645 affects thunderbird Added indication that 949646 affects thunderbird Added indication that 949647 affects thunderbird Added indication that 949648 affects thunderbird Added indication that 949650 affects thunderbird Added indication that 949657 affects thunderbird Added indication that 949668 affects thunderbird > End of message, stopping processing here. Please contact me if you need assistance. -- 949644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949644 949645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949645 949646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949646 949647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949647 949648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949648 949650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949650 949657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949657 949668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949668 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948877: marked as done (pydicom ftbfs in unstable (test failures))
Your message dated Thu, 23 Jan 2020 12:34:53 +
with message-id
and subject line Bug#948877: fixed in pydicom 1.4.1-1
has caused the Debian Bug report #948877,
regarding pydicom ftbfs in unstable (test failures)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
948877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pydicom
Version: 1.2.1-1
Severity: serious
Tags: sid bullseye
pydicom ftbfs in unstable (test failures)
[...]
fp =
dataset = <[RecursionError("With tag (3006, 0040) got exception: With tag (3006,
0048) got exception: maximum recursion depth ex...65 more times]
RecursionError: maximum recursion depth exceeded
") raised in repr()] Dataset object at 0x7fdffed318e0>
parent_encoding = ['iso8859']
def write_dataset(fp, dataset, parent_encoding=default_encoding):
"""Write a Dataset dictionary to the file. Return the total length
written.
Attempt to correct ambiguous VR elements when explicit little/big
encoding Elements that can't be corrected will be returned unchanged.
"""
_harmonize_properties(dataset, fp)
if not fp.is_implicit_VR and not dataset.is_original_encoding:
dataset = correct_ambiguous_vr(dataset, fp.is_little_endian)
dataset_encoding = dataset.get('SpecificCharacterSet', parent_encoding)
fpStart = fp.tell()
# data_elements must be written in tag order
tags = sorted(dataset.keys())
for tag in tags:
# do not write retired Group Length (see PS3.5, 7.2)
if tag.element == 0 and tag.group > 6:
continue
with tag_in_exception(tag):
> write_data_element(fp, dataset.get_item(tag), dataset_encoding)
pydicom/filewriter.py:521:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self =
type =
value = RecursionError('With tag (3006, 0048) got exception: maximum recursion
depth exceeded\nTraceback (most recent call las__str__(self) + "\\""\n
[Previous line repeated 467 more times]\nRecursionError: maximum recursion depth
exceeded\n')
traceback =
def __exit__(self, type, value, traceback):
if type is None:
try:
next(self.gen)
except StopIteration:
return False
else:
raise RuntimeError("generator didn't stop")
else:
if value is None:
# Need to force instantiation so we can reliably
# tell if we get the same exception back
value = type()
try:
> self.gen.throw(type, value, traceback)
/usr/lib/python3.8/contextlib.py:131:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
tag = (3006, 0040)
@contextmanager
def tag_in_exception(tag):
"""Use `tag` within a context.
Used to include the tag details in the traceback message when an
exception
is raised within the context.
Parameters
--
tag : pydicom.tag.Tag
The tag to use in the context.
"""
try:
yield
except Exception as ex:
stack_trace = traceback.format_exc()
msg = 'With tag {0} got exception: {1}\n{2}'.format(
tag,
str(ex),
stack_trace)
> raise type(ex)(msg)
E RecursionError: With tag (3006, 0040) got exception: With tag (3006,
0048) got exception: maximum recursion depth exceeded
E Traceback (most recent call last):
E File
"/<>/.pybuild/cpython3_3.8_pydicom/build/pydicom/tag.py", line 30,
in tag_in_exception
E yield
E File
"/<>/.pybuild/cpython3_3.8_pydicom/build/pydicom/filewriter.py",
line 521, in write_dataset
E write_data_element(fp, dataset.get_item(tag), dataset_encoding)
E File
"/<>/.pybuild/cpython3_3.8_pydicom/build/pydicom/filewriter.py",
line 471, in write_data_element
E writer_function(buffer, data_element)
E File
"/<>/.pybuild/cpython3_3.8_pydicom/build/pydicom/filewriter.py",
line 324, in write_number_string
E val = str(val)
E File
"/<>/.pybuild/cpython3_3.8_pydicom/build/pydicom/valuerep.py", line
507, in __repr__
E return "\"" + int.__str__(self) + "\""
E File
"/<>/.pybuild/cpython3_3.8_pydicom/build/pydicom/valuerep.py", line
507, in __repr__
E
Bug#949668: firefox-esr: does not start after upgrade
Package: firefox-esr Version: 68.4.2esr-1 Severity: grave Justification: renders package unusable hey, last night did a regular `apt upgrade` and amongst others, firefox, firefox- esr, thunderbird were updated.. (was using those during upgrade.. ) powered off a bit later, and today none of these applications open. message is the same as in #919769 : $ firefox-esr --safe-mode (firefox-esr:13795): Gtk-WARNING **: 12:16:17.843: Theme parsing error: gtk- widgets.css:1214:18: Not using units is deprecated. Assuming 'px'. ExceptionHandler::GenerateDump cloned child ExceptionHandler::WaitForContinueSignal waiting for continue signal...13826 ExceptionHandler::SendContinueSignalToChild sent continue signal to child tried to downgrade firefox-esr/testing but no luck. also downgraded some of the other packages that were upgraded last night (like gvfs*, libjavascriptcoregtk-4.0-18, libglib2.0-0, libwebkit2gtk-4.0-37), but still no luck. all mozilla products (ff, ff-esr, tb) that i'm using daily for work and personally, keep crashing with the same message. let me know if i can get more debug info somehow (there is no firefox-esr-gdb package as reportbug suggests...?). thanks in advance, d. -- Package-specific info: -- Addons package information -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.13-gnu (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages firefox-esr depends on: ii debianutils 4.9.1 ii fontconfig2.13.1-2+b1 ii libasound21.2.1.2-2 ii libatk1.0-0 2.34.1-1 ii libc6 2.29-9 ii libcairo-gobject2 1.16.0-4 ii libcairo2 1.16.0-4 ii libdbus-1-3 1.12.16-2 ii libdbus-glib-1-2 0.110-5 ii libevent-2.1-72.1.11-stable-1 ii libffi7 3.3-3 ii libfontconfig12.13.1-2+b1 ii libfreetype6 2.10.1-2 ii libgcc1 1:9.2.1-24 ii libgdk-pixbuf2.0-02.40.0+dfsg-2 ii libglib2.0-0 2.62.4-1+b1 ii libgtk-3-03.24.13-1 ii libjsoncpp1 1.7.4-3+b1 ii libnspr4 2:4.24-1 ii libnss3 2:3.49.1-1 ii libpango-1.0-01.42.4-8 ii libsqlite3-0 3.31.0-1 ii libstartup-notification0 0.12-6 ii libstdc++69.2.1-24 ii libx11-6 2:1.6.8-1 ii libx11-xcb1 2:1.6.8-1 ii libxcb-shm0 1.13.1-3 ii libxcb1 1.13.1-3 ii libxcomposite11:0.4.4-2 ii libxdamage1 1:1.1.5-1 ii libxext6 2:1.3.3-1+b2 ii libxfixes31:5.0.3-1 ii libxrender1 1:0.9.10-1 ii libxt61:1.1.5-1+b3 ii procps2:3.3.15-2+b1 ii zlib1g1:1.2.11.dfsg-1+b1 Versions of packages firefox-esr recommends: ii libavcodec-extra58 [libavcodec58] 7:4.2.1-2+b1 Versions of packages firefox-esr suggests: pn fonts-lmodern pn fonts-stix | otf-stix ii libcanberra0 0.30-7 ii libgssapi-krb5-2 1.17-6 ii libgtk2.0-02.24.32-4 ii pulseaudio 13.0-3 -- no debconf information
Bug#949664: libassuan: testsuite failure due to wrong flags being injected
Source: libassuan
Version: 2.5.3-7
Severity: serious
tags: patch
Hello, looks like we have 2 problems:
arm64 test failure because the compiler is not meant to run there (but the
package is installable)
amd64 -> w32 test failure because of wrong flags injected (the libgpg-error has
this fix, not sure why it hasn't been copied on this package).
The following patch fixes both, and "syncs" the build-windows file with the
correspondent libgpg-error one (so melding is easier to do)
(amd64 flags were used for w32 builds due to wrong pkg-config call)
diff -Nru libassuan-2.5.3/debian/changelog libassuan-2.5.3/debian/changelog
--- libassuan-2.5.3/debian/changelog2019-07-17 17:09:10.0 +0200
+++ libassuan-2.5.3/debian/changelog2019-07-19 10:24:16.0 +0200
@@ -1,3 +1,12 @@
+libassuan (2.5.3-7.1) unstable; urgency=medium
+
+ * Fix testsuite flags being incorrectly passed
+(patch taken from libgpg-error). (LP: #1856056
+Closes: #-1)
+ * Do not fail new test on arm64
+
+ -- Gianfranco Costamagna Fri, 19 Jul 2019
10:24:16 +0200
+
libassuan (2.5.3-7) unstable; urgency=medium
* export CPPFLAGS_FOR_BUILD as well
diff -Nru libassuan-2.5.3/debian/tests/build-windows
libassuan-2.5.3/debian/tests/build-windows
--- libassuan-2.5.3/debian/tests/build-windows 2019-07-16 19:49:54.0
+0200
+++ libassuan-2.5.3/debian/tests/build-windows 2019-07-19 10:24:16.0
+0200
@@ -2,35 +2,35 @@
set -e
-ARCH=$1
+ARCH="$1"
if [ "$ARCH" = x86_64 ]; then
-GCC=x86_64-w64-mingw32-gcc
WINE=/usr/lib/wine/wine64
export WINESERVER=/usr/lib/wine/wineserver64
elif [ "$ARCH" = i686 ]; then
-GCC=i686-w64-mingw32-gcc
WINE=/usr/lib/wine/wine
export WINESERVER=/usr/lib/wine/wineserver32
else
printf >&2 'Unknown Architecture: %s\n' "$ARCH"
exit 1
fi
+GCC="${ARCH}-w64-mingw32-gcc"
# get wine initialized, which normally spews logs to stderr
# (autopkgtest doesn't want stderr)
"$WINE" hostname 2>&1
-export PKG_CONFIG_PATH=/usr/x86_64-w64-mingw32/lib/pkgconfig
+if [ `dpkg --print-architecture` = 'arm64' ] ; then
+ echo "Don't fail testsuite on arm64, this test always failed there"
+ exit 0
+fi
-# see https://dev.gnupg.org/T4624 for why this is needed
-extralibs=(-lws2_32)
+export PKG_CONFIG_PATH="/usr/${ARCH}-w64-mingw32/lib/pkgconfig"
-"$GCC" -pedantic -Wall -Werror -o test-run.exe \
- -static \
- -Wl,--no-as-needed \
- debian/tests/simple-build.c \
- $(pkg-config --static --cflags --libs libassuan) "${extralibs[@]}"
+# see https://dev.gnupg.org/T4624 for why this is needed
+extra_libs=(-lws2_32)
+# build a static windows binary around libassuan and run it:
+"$GCC" -pedantic -Wall -Werror -static -o test-run.exe
debian/tests/simple-build.c $(pkg-config --cflags --static --libs libassuan)
"${extra_libs[@]}"
"$WINE" ./test-run.exe
-rm -f test-run.exe
+rm -f ./test-run.exe
diff -Nru libassuan-2.5.3/debian/changelog libassuan-2.5.3/debian/changelog
--- libassuan-2.5.3/debian/changelog2019-07-17 17:09:10.0 +0200
+++ libassuan-2.5.3/debian/changelog2019-07-19 10:24:16.0 +0200
@@ -1,3 +1,12 @@
+libassuan (2.5.3-7.1) unstable; urgency=medium
+
+ * Fix testsuite flags being incorrectly passed
+(patch taken from libgpg-error). (LP: #1856056
+Closes: #-1)
+ * Do not fail new test on arm64
+
+ -- Gianfranco Costamagna Fri, 19 Jul 2019
10:24:16 +0200
+
libassuan (2.5.3-7) unstable; urgency=medium
* export CPPFLAGS_FOR_BUILD as well
diff -Nru libassuan-2.5.3/debian/tests/build-windows
libassuan-2.5.3/debian/tests/build-windows
--- libassuan-2.5.3/debian/tests/build-windows 2019-07-16 19:49:54.0
+0200
+++ libassuan-2.5.3/debian/tests/build-windows 2019-07-19 10:24:16.0
+0200
@@ -2,35 +2,35 @@
set -e
-ARCH=$1
+ARCH="$1"
if [ "$ARCH" = x86_64 ]; then
-GCC=x86_64-w64-mingw32-gcc
WINE=/usr/lib/wine/wine64
export WINESERVER=/usr/lib/wine/wineserver64
elif [ "$ARCH" = i686 ]; then
-GCC=i686-w64-mingw32-gcc
WINE=/usr/lib/wine/wine
export WINESERVER=/usr/lib/wine/wineserver32
else
printf >&2 'Unknown Architecture: %s\n' "$ARCH"
exit 1
fi
+GCC="${ARCH}-w64-mingw32-gcc"
# get wine initialized, which normally spews logs to stderr
# (autopkgtest doesn't want stderr)
"$WINE" hostname 2>&1
-export PKG_CONFIG_PATH=/usr/x86_64-w64-mingw32/lib/pkgconfig
+if [ `dpkg --print-architecture` = 'arm64' ] ; then
+ echo "Don't fail testsuite on arm64, this test always failed there"
+ exit 0
+fi
-# see https://dev.gnupg.org/T4624 for why this is needed
-extralibs=(-lws2_32)
+export PKG_CONFIG_PATH="/usr/${ARCH}-w64-mingw32/lib/pkgconfig"
-"$GCC" -pedantic -Wall -Werror -o test-run.exe \
- -static \
- -Wl,--no-as-needed \
- debian/tests/simple-build.c \
- $(pkg-config --static --cflags --libs libassuan) "${extralibs[@]}"
+# see https://dev.gnupg.org/T4624 for why this is needed
+extra_libs=(-lws2_32)
Bug#948726: marked as done (uwsgi-plugin-rados, (build-)dependencies unsatisfiable on mipsel.)
Your message dated Thu, 23 Jan 2020 11:35:12 + with message-id and subject line Bug#948726: fixed in uwsgi 2.0.18-7 has caused the Debian Bug report #948726, regarding uwsgi-plugin-rados, (build-)dependencies unsatisfiable on mipsel. 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.) -- 948726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948726 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: uwsgi-plugin-rados Version: 2.0.18-6 Severity: serious The binary packages built from the ceph source package were recently removed from mipsel, because the new version of ceph runs out of address space during the build. Your package build-depends on librados-dev and depends on librados2 which are built from the ceph source package. So uwsgi-plugin-rados and uwsgi-infrastructure-plugins are now uninstallable and the uwsgi source package unbuildable on mipsel. The librados-dev build-dependency, the dependency of uwsgi-infrastructure plugins on uwsgi-plugin-rados and the building of the uwsgi-plugin-rados binary package are already architecture-qualified, so this should be a simple case of removing mipsel from the architecture lists. --- End Message --- --- Begin Message --- Source: uwsgi Source-Version: 2.0.18-7 We believe that the bug you reported is fixed in the latest version of uwsgi, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 948...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated uwsgi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 23 Jan 2020 11:52:29 +0100 Source: uwsgi Architecture: source Version: 2.0.18-7 Distribution: unstable Urgency: medium Maintainer: uWSGI packaging team Changed-By: Jonas Smedegaard Closes: 924586 925954 948726 949509 Changes: uwsgi (2.0.18-7) unstable; urgency=medium . * add patch cherry-picked upstream to fix php memory corruption for uwsgi_cache_* * exclude arch mipsel from rados build-dependencies; closes: bug#948726, thanks to Peter Green * have uwsgi only rotate logfiles below /var/log/uwsgi/app (avoid ones directly below /var/log/uwsgi) to not clash with uwsgi-emperor; closes: bug#925954, thanks to Laurent Bonnaud * add patch 1006 to use pkg-config with libxml2 (not deprecated xml2-config); closes: bug#949509, thanks to Mattia Rizzolo * stop buid-depend on libqdbm-dev (seems related to php plugin and even there apparently unneeded); closes: bug#924586, thanks to Andreas Hasenack Checksums-Sha1: 2e9c1d6ee4a11d0ae86118c2a5aff9cb4996bf46 7776 uwsgi_2.0.18-7.dsc 9b1d8fe778648db800d7590be4d72708e4ea2163 59516 uwsgi_2.0.18-7.debian.tar.xz 6d0512375777dd55ed57844643ec8e3ff155abce 39731 uwsgi_2.0.18-7_amd64.buildinfo Checksums-Sha256: 581467afe89b0da32c71c5f1672e6ff74832565b0bc9d9112325ab644769c9e0 7776 uwsgi_2.0.18-7.dsc c1811f0704a6089ac1e4ccebe9937de6835f8061bd67e71598dc3143fe5f646e 59516 uwsgi_2.0.18-7.debian.tar.xz fc688fbf709465c32b09436ddb3edad88387d0e5124d4b12dd9b94bfd08c8829 39731 uwsgi_2.0.18-7_amd64.buildinfo Files: 40cc24090764385c50e8950472cf3c43 7776 httpd optional uwsgi_2.0.18-7.dsc c91a63865dcd4f6c512b482f3298817b 59516 httpd optional uwsgi_2.0.18-7.debian.tar.xz 8043a18c4b5bcab06d0de5e00e3f1a4a 39731 httpd optional uwsgi_2.0.18-7_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl4pgkoACgkQLHwxRsGg ASHBwQ/9EyeH5a2s7bsU8jk7TJtetrE4lN98WBK9a7QFVQlptt4Izj6yY0uDvgXH Ax4PyScfLkecb+gbxUjJn24FuY8U9+aQal3nk6XqhWFUsL7IeywGqNF0ji8t3T2I scj5SbyBUntbaHFUMvdLGpSi+gwqES9ecCVkAp+dBa7HcQKJypfgpN+WHUUPNhzA kcQxm/3Np153Ww3OVX3hoBP+4WlTMwSPXkgdFFPzBkFjNOnFUjBo/YgmQkeGvj3q O3xkigRYIw9geoWZGgnKDuo3YKqBjGLr9hf5uTkIQdkWmemzJ+NpypEmMWNXFB3m c1e9yp1GwFDRFCYp+PqCBgnry2MrtjJSsUYkJCXDdOZ3jSeBSg8BbyuuDHXVRA7y 6Et9C5uGNDoJoV2CweMKZwyBqw4PNA7Y2mU9s3jlbn2Ej5NU8XtLIxxKvBxAa8jL t3PTyjMtHCnpfJFVqGQ8d/mmNdaQ5Q80Bs7rE1+Rd7YGrdo3xap93vVfuW03Kr12 TfdoldW4WqYSJ0jWCoGyHMWkww63Gc/JiwJhaU3kgVF+2j2JvVPYHCHAbQPV0hc6 bkrdvZU6qagqkxYAbX3mgXp00IPrGKb3TWIxvYMudYPlKOqNSg4Ju6AxXo8l9jMJ
Bug#949646: libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0
It also breaks thunderbird 1:68.4.1-1 which immediately crashes before any graphical component appears. Regards, Jörg.
