Bug#943990: Fails to upgrade
Package: openvswitch-common Version: 2.11.0+2019.06.25+git.9ebe795035+ds1-6 Severity: serious Hi, Recent packaging changes makes the package fails to upgrade: $ LC_ALL=C sudo apt upgrade [sudo] password for taffit: Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up openvswitch-common (2.11.0+2019.06.25+git.9ebe795035+ds1-6) ... update-alternatives: error: alternative path /usr/lib/openvswitch-common/ovs-vswitchd doesn't exist dpkg: error processing package openvswitch-common (--configure): installed openvswitch-common package post-installation script subprocess returned error exit status 2 dpkg: dependency problems prevent configuration of openvswitch-switch: openvswitch-switch depends on openvswitch-common (= 2.11.0+2019.06.25+git.9ebe795035+ds1-6); however: Package openvswitch-common is not configured yet. dpkg: error processing package openvswitch-switch (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.29-3) ... Errors were encountered while processing: openvswitch-common openvswitch-switch needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) Regards David -- System Information: Debian Release: bullseye/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-1-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR:fr (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openvswitch-common depends on: ii iproute2 5.3.0-1 ii libc62.29-3 ii libcap-ng0 0.7.9-2.1 ii libssl1.11.1.1d-2 ii libunbound8 1.9.4-2 ii openssl 1.1.1d-2 ii python3 3.7.5-1 ii python3-six 1.12.0-2 openvswitch-common recommends no packages. Versions of packages openvswitch-common suggests: ii ethtool 1:4.19-1 -- no debconf information signature.asc Description: PGP signature
Bug#933407: marked as done (codeblocks: Please rebuild against wxWidgets GTK 3 package)
Your message dated Sat, 02 Nov 2019 03:04:07 + with message-id and subject line Bug#933407: fixed in codeblocks 17.12+dfsg-1 has caused the Debian Bug report #933407, regarding codeblocks: Please rebuild against wxWidgets GTK 3 package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 933407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933407 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: codeblocks Severity: normal Hi, Your package appears to be using the wxWidgets GTK 2 implementation. In Debian, we have had a GTK 3 implementation of wxWidgets for some time. For the bullseye release, the wxWidgets package maintainers plan to remove the GTK 2 version, so we kindly request that you switch your package to use the GTK 3 version. We have a transition tracker [1] setup to track progress. Switching to the GTK 3 version may be as simple as: 1) Update your Build-Depends libwxgtk3.0-dev -> libwxgtk3.0-gtk3-dev libwxgtk-media3.0-dev -> libwxgtk-media3.0-gtk3-dev 2) Rebuild 3) Test If everything seems to be working fine, that's probably all you need to do. There are a couple of known issues: 1) If your package uses wxGLCanvas, this doesn't currently work when running under Wayland. As a workaround, you can force use of X. See bug: [2] 2) If your package uses graphics contexts, it may encounter a problem with coordinate overflow. See bug: [3] If you have any questions, or need assistance with the conversion, please contact the wxWidgets team, team...@tracker.debian.org. [1] https://release.debian.org/transitions/html/wxwidgets3.0-gtk3.html [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900678 [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906060 --- End Message --- --- Begin Message --- Source: codeblocks Source-Version: 17.12+dfsg-1 We believe that the bug you reported is fixed in the latest version of codeblocks, 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. David Prévot (supplier of updated codeblocks package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Oct 2019 16:10:57 -1000 Source: codeblocks Architecture: source Version: 17.12+dfsg-1 Distribution: unstable Urgency: medium Maintainer: David Paleino Changed-By: David Prévot Closes: 841466 886062 933407 Changes: codeblocks (17.12+dfsg-1) unstable; urgency=medium . New upstream release (Closes: #886062) . [ Vincent Cheng ] * Remove Michael Casadevall from Uploaders in d/control. (Closes: #841466) . [ David Prévot ] * Use secure copyright file specification URI. * Transition to automatic debug package (from: codeblocks-dbg). * Use secure URI in debian/watch. * Bump debhelper from old 9 to 12. + debian/rules: Call dh_missing rather than using dh_install --list-missing. * debian/copyright: Use spaces rather than tabs in continuation lines. * Update Vcs-* headers to use salsa repository. * Upstream renamed (lib)astyle as (lib)Astyle * d/control + Build-Depends: - Use libwxgtk3.0-gtk3-dev instead of libwxgtk3.0-dev (Closes: #933407) - Use libgtk-3-dev instead of libgtk2.0-dev - Add libboost-system-dev and libtinyxml-dev - Drop dh-autoreconf + Drop versioned dependency satisfied in (old)stable + Add self to Uploaders + Add Multi-Arch hints * d/rules + drop useless dh options (default since dh 10) + include /usr/share/dpkg/default.mk + Drop SOURCE_DATE_EPOCH assignment + Drop /usr/share/dpkg/buildflags.mk inclusion * Use debian/clean instead of override_dh_auto_clean * Drop lintian-overrides about tinyxml since the system library is now used * Install upstream appdata * Move more architecture-independent files to codeblocks-common * Remove unused files from debian/ directory * Update Standards-Version to 4.4.1 * Update copyright Checksums-Sha1: 8618bbc473ba17d2ed6a8eb30f804c342db2b1a5 2164 codeblocks_17.12+dfsg-1.dsc 020512cc10a1bbfac0991982031369c6be497363 13277536 codeblocks_17.12+dfsg.orig.tar.xz
Bug#943900: marked as done (twolame breaks ffmpeg autopkgtest: twolame_init_params(): 384kbps is an invalid bitrate for mono encoding.)
Your message dated Sat, 02 Nov 2019 01:34:19 + with message-id and subject line Bug#943900: fixed in ffmpeg 7:4.2.1-2 has caused the Debian Bug report #943900, regarding twolame breaks ffmpeg autopkgtest: twolame_init_params(): 384kbps is an invalid bitrate for mono encoding. 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.) -- 943900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943900 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: twolame, ffmpeg Control: found -1 twolame/0.4.0-2 Control: found -1 ffmpeg/7:4.2.1-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 twolame the autopkgtest of ffmpeg fails in testing when that autopkgtest is run with the binary packages of twolame from unstable. It passes when run with only packages from testing. In tabular form: passfail twolamefrom testing0.4.0-2 ffmpeg from testing7:4.2.1-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of twolame to testing [1]. Due to the nature of this issue, I filed this bug report against both 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 [1] https://qa.debian.org/excuses.php?package=twolame https://ci.debian.net/data/autopkgtest/testing/amd64/f/ffmpeg/3300508/log.gz Test 95: trying muxer 'asf' with 'a' encoder 'libtwolame' for codec 'mp2' ffmpeg -f lavfi -i sine=d=0.1 -strict -2 -c:a libtwolame -f asf /tmp/autopkgtest-lxc.m3tk853a/downtmp/autopkgtest_tmp/test/libtwolame.asf -y -hide_banner -nostdin Input #0, lavfi, from 'sine=d=0.1': Duration: N/A, start: 0.00, bitrate: 705 kb/s Stream #0:0: Audio: pcm_s16le, 44100 Hz, mono, s16, 705 kb/s Stream mapping: Stream #0:0 -> #0:0 (pcm_s16le (native) -> mp2 (libtwolame)) twolame_init_params(): 384kbps is an invalid bitrate for mono encoding. Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height Conversion failed! FAILED: asf;a=mp2:libtwolame; encoding return code: 1 signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: ffmpeg Source-Version: 7:4.2.1-2 We believe that the bug you reported is fixed in the latest version of ffmpeg, 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. James Cowgill (supplier of updated ffmpeg package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 02 Nov 2019 01:17:31 + Source: ffmpeg Architecture: source Version: 7:4.2.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: James Cowgill Closes: 943900 Changes: ffmpeg (7:4.2.1-2) unstable; urgency=medium . * d/patches: - avcodec/libtwolame: fix mono default bitrate. (Closes: #943900) * d/tests: - Replace remaining occurrences of ADTTMP. Checksums-Sha1: c3ef13290ff1e210fb5f5b7282256bfd2ba0760d 5318 ffmpeg_4.2.1-2.dsc 2f61cf469a8a8ca76443b76eb1942077dbb7cd51 50692 ffmpeg_4.2.1-2.debian.tar.xz Checksums-Sha256: dcef9a847ac997f4105878842c7795a8b8fe00ddfa93bb8e634c98f214af1458 5318 ffmpeg_4.2.1-2.dsc 9b88da4951b735a4a98856566b543f4193ff066201bf4a844ce27b53650addf0 50692 ffmpeg_4.2.1-2.debian.tar.xz Files: cd6bb1dd0aefe1ba8906706645bdd24f 5318 video optional ffmpeg_4.2.1-2.dsc b156b4fdb7e088fe746322583927bed7 50692 video optional ffmpeg_4.2.1-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEE+Ixt5DaZ6POztUwQx/FnbeotAe8FAl282iUUHGpjb3dnaWxs QGRlYmlhbi5vcmcACgkQx/FnbeotAe/+FhAAuN35l/EzvTcYFqOeKKHcU91bfr7d
Processed: Bug#943900 marked as pending in ffmpeg
Processing control commands: > tag -1 pending Bug #943900 [src:ffmpeg] twolame breaks ffmpeg autopkgtest: twolame_init_params(): 384kbps is an invalid bitrate for mono encoding. Added tag(s) pending. -- 943900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943900 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#943900: marked as pending in ffmpeg
Control: tag -1 pending Hello, Bug #943900 in ffmpeg 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/multimedia-team/ffmpeg/commit/4ba7b1b195575e013381bb9fbf552d6a7216095d d/patches: avcodec/libtwolame: fix mono default bitrate Add patch to fix the mono default bitrate when using libtwolame. This fixes various autopkgtest failures when using libtwolame 0.4.0 Closes: #943900 (this message was generated automatically) -- Greetings https://bugs.debian.org/943900
Bug#943987: non-free file in "debian/missing-sources"
Package: gitlab Version: 12.2.9-1 Severity: serious Usertags: dfsg In most recent upload Utkarsh Gupta circumvented legitimate Lintian error E: gitlab source: source-is-missing vendor/assets/javascripts/snowplow/sp.js line length is 32154 characters (>512) by adding source-less pre-minified non-DFSG-compliant "sp.js" to "debian/ missing-sources". -- Regards, Dmitry Smirnov --- signature.asc Description: This is a digitally signed message part.
Bug#943986: wrong shared linkage position of mv's library dependency
Package: coreutils Version: 8.30-3 Severity: serious cp and mv have a runtime linkage to libacl and libattr which are installed in /usr/lib/x86_64-linux-gnu/. This means that a single-user booted system without mounted /usr, is not able to cp or mv files! Either the dependancy should be dropped, or the libacl and libattr shared libraries should be moved into /lib. Thanks, David -- System Information: Debian Release: 10.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=english (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages coreutils depends on: ii libacl1 2.2.53-4 ii libattr1 1:2.4.48-4 ii libc62.28-10 ii libselinux1 2.8-1+b1 coreutils recommends no packages. coreutils suggests no packages. -- no debconf information Mit freundlichen Grüssen, David Frey --
Bug#943985: Depends on volti, which is scheduled for removal
Package: parl-desktop Severity: serious volti is scheduled for removal from the archive, the dependency needs to be removed.
Bug#943870: Fix
This started happening with some change to Qt, maybe by... 5.12? where having "phonon4qt5" in the QT += line stopped generating the Makefile correctly. The workaround, assuming they don't re-enable that behavior in Qt, is to add the line: LIBS += -lphonon4qt5 somewhere in Auralquiz.pro; right after the other LIBS line, or at the end, would work. -- Development blog: https://jancoding.wordpress.com
Processed: ganeti-instance-debootstrap: diff for NMU version 0.16-6.1
Processing control commands: > tags 942114 + pending Bug #942114 [ganeti-instance-debootstrap] cache fails to store capabilities correctly Added tag(s) pending. -- 942114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942114: ganeti-instance-debootstrap: diff for NMU version 0.16-6.1
Control: tags 942114 + pending
Dear maintainer,
I've prepared an NMU for ganeti-instance-debootstrap (versioned as 0.16-6.1) and
uploaded it to DELAYED/02. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru ganeti-instance-debootstrap-0.16/debian/changelog ganeti-instance-debootstrap-0.16/debian/changelog
--- ganeti-instance-debootstrap-0.16/debian/changelog 2018-06-20 06:57:18.0 -0400
+++ ganeti-instance-debootstrap-0.16/debian/changelog 2019-11-01 19:01:50.0 -0400
@@ -1,3 +1,10 @@
+ganeti-instance-debootstrap (0.16-6.1) unstable; urgency=medium
+
+ * Non-maintainer upload
+ * add patch to respect linux caps (Closes: #942114)
+
+ -- Antoine Beaupré Fri, 01 Nov 2019 19:01:50 -0400
+
ganeti-instance-debootstrap (0.16-6) unstable; urgency=medium
* Bump Standards-Version to 4.1.4; no changes needed
diff -Nru ganeti-instance-debootstrap-0.16/debian/patches/respect-Linux-capabilities-7-in-cache.patch ganeti-instance-debootstrap-0.16/debian/patches/respect-Linux-capabilities-7-in-cache.patch
--- ganeti-instance-debootstrap-0.16/debian/patches/respect-Linux-capabilities-7-in-cache.patch 1969-12-31 19:00:00.0 -0500
+++ ganeti-instance-debootstrap-0.16/debian/patches/respect-Linux-capabilities-7-in-cache.patch 2019-11-01 19:01:50.0 -0400
@@ -0,0 +1,48 @@
+From cd34bcc48a2af92f484535b81fba2d46dad1dbb6 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?=
+Date: Thu, 10 Oct 2019 11:07:51 -0400
+Subject: [PATCH] respect Linux capabilities(7) in cache
+
+The default GNU tar configuration does not carry fancy extended
+attributes and that is where, among other things, stuff like Linux
+capabilities(7) are stored. This is kind of important because that's
+how ping(8) works for regular users.
+
+We shove --selinux and --acls in there while we're at it, because why
+not. We never know what the future might bring, and it seems
+silly *not* to create a complete archive.
+
+Note that --xattrs-include='*' is important because, by default, GNU
+tar will not include capabilities /even/ if --xattrs is specified on
+the commandline, see this bug report for details:
+
+https://bugzilla.redhat.com/show_bug.cgi?id=771927
+---
+ create | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/create b/create
+index 607bab2..7526e71 100755
+--- a/create
b/create
+@@ -83,7 +83,7 @@ if [ "$CLEAN_CACHE" -a -d "$CACHE_DIR" ]; then
+ fi
+
+ if [ -f "$CACHE_FILE" ]; then
+- tar xf "$CACHE_FILE" -C $TMPDIR
++ tar --acls --selinux --xattrs --xattrs-include='*' -x -f "$CACHE_FILE" -C $TMPDIR
+ else
+ if [ "$PROXY" ]; then
+ export http_proxy="$PROXY"
+@@ -109,7 +109,7 @@ else
+
+ if [ "$GENERATE_CACHE" = "yes" ]; then
+ TMP_CACHE=`mktemp "${CACHE_FILE}.XX"`
+-tar cf "$TMP_CACHE" -C $TMPDIR .
++tar --acls --selinux --xattrs --xattrs-include='*' -c -f "$TMP_CACHE" -C $TMPDIR .
+ mv -f "$TMP_CACHE" "$CACHE_FILE"
+ fi
+ fi
+--
+2.20.1
+
diff -Nru ganeti-instance-debootstrap-0.16/debian/patches/series ganeti-instance-debootstrap-0.16/debian/patches/series
--- ganeti-instance-debootstrap-0.16/debian/patches/series 2018-06-20 06:57:18.0 -0400
+++ ganeti-instance-debootstrap-0.16/debian/patches/series 2019-11-01 19:01:50.0 -0400
@@ -1 +1,2 @@
+respect-Linux-capabilities-7-in-cache.patch
fix-sfdisk-BLKRRPART.patch
signature.asc
Description: PGP signature
Bug#938816: webtest: Python2 removal in sid/bullseye
Package: webtest
Followup-For: Bug #938816
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch
Hello,
Here is a patch, based on webtest 2.0.28-1, that drops python2 support.
This has been verified to build successfully, and has been uploaded to
Ubuntu on account of the removal of python-waitress.
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru webtest-2.0.28/debian/control webtest-2.0.28/debian/control
--- webtest-2.0.28/debian/control 2017-09-29 03:52:31.0 -0700
+++ webtest-2.0.28/debian/control 2019-11-01 13:43:27.0 -0700
@@ -4,33 +4,17 @@
Maintainer: Debian Python Modules Team
Uploaders: Piotr Ożarowski
Build-Depends: debhelper (>= 9)
-Build-Depends-Indep: dh-python, python-all, python3-all,
- python-setuptools, python-webob,
+Build-Depends-Indep: dh-python, python3-all,
python3-setuptools, python3-webob,
# docs & tests
python3-sphinx, python3-six, python3-bs4, python3-waitress,
# tests
# python-unittest2, python-pyquery
Standards-Version: 4.1.1
-X-Python-Version: >=2.6
Homepage: http://pythonpaste.org/webtest/
Vcs-Git: https://anonscm.debian.org/git/python-modules/packages/webtest.git
Vcs-Browser:
https://anonscm.debian.org/cgit/python-modules/packages/webtest.git
-Package: python-webtest
-Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}, python-webob (>= 1.2),
- python-six, python-waitress (>= 0.8.5), python-bs4,
- python-paste (>= 1.7.1), python-pastedeploy
-Recommends: python-lxml, python-pyquery
-Suggests: python-webtest-doc
-Description: wraps any WSGI application and makes it easy to test
- WebTest helps you test your WSGI-based web applications. This can be any
- application that has a WSGI (Web Server Gateway Interface) interface,
- including an application written in a framework that supports WSGI (which
- includes most actively developed Python web frameworks – almost anything
- that even nominally supports WSGI should be testable).
-
Package: python3-webtest
Architecture: all
Depends: ${python3:Depends}, ${misc:Depends}, python3-webob,
diff -Nru webtest-2.0.28/debian/python-webtest-doc.links
webtest-2.0.28/debian/python-webtest-doc.links
--- webtest-2.0.28/debian/python-webtest-doc.links 2017-09-29
03:52:16.0 -0700
+++ webtest-2.0.28/debian/python-webtest-doc.links 2019-11-01
13:43:27.0 -0700
@@ -1,4 +1,2 @@
-/usr/share/doc/python-webtest-doc/ /usr/share/doc/python-webtest/html
-/usr/share/doc/python-webtest-doc/_sources /usr/share/doc/python-webtest/rst
/usr/share/doc/python-webtest-doc/ /usr/share/doc/python3-webtest/html
/usr/share/doc/python-webtest-doc/_sources /usr/share/doc/python3-webtest/rst
diff -Nru webtest-2.0.28/debian/rules webtest-2.0.28/debian/rules
--- webtest-2.0.28/debian/rules 2017-09-29 03:52:31.0 -0700
+++ webtest-2.0.28/debian/rules 2019-11-01 13:43:27.0 -0700
@@ -5,7 +5,7 @@
export PYBUILD_DISABLE=test
%:
- dh $@ --with python2,python3,sphinxdoc --buildsystem=pybuild
+ dh $@ --with python3,sphinxdoc --buildsystem=pybuild
override_dh_auto_install:
dh_auto_install --buildsystem=pybuild
Bug#941018: ibus 1.5.21-1 does not work with qt5 applications
On 2019-10-30 16:04, Simon McVittie wrote: I was hoping to let glib2.0 get some testing in unstable before backporting anything. That makes sense, of course. OTOH backporting takes time, so preparing for that in the meantime can't hurt. Want to mention that we have started the backporting work on the Ubuntu side. We chose to include gcredentialsprivate-Document-the-various-private-macros.patch. As regards Add-a-test-for-GDBusServer-authentication.patch we failed, at least so far, to apply it on glib 2.48 (Ubuntu 16.04), but it's included in proposed uploads for more recent Ubuntu releases. -- Gunnar Hjalmarsson https://launchpad.net/~gunnarhj
Bug#943976: Should smart be removed?
Source: smart Severity: serious Should smart be removed? It depends on Python 2 and pygtk, which are going away, and it's dead upstream (last release from 2011). Cheers, Moritz
Bug#943974: mariadb-server-10.3: as "service mysql stop" fails, system refuse to shut down
Package: mariadb-server-10.3 Version: 1:10.3.18-1 Severity: critical Justification: breaks the whole system after upgrade, each time I want to shut down, I get stuck in the shutdown of mariadb database, that hangs forever. Manually calling service stop for this service also hangs, as well as removal propcedure as it aslo contains a service stop. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.81 (SMP w/2 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/bash Init: systemd (via /run/systemd/system) Versions of packages mariadb-server-10.3 depends on: ii adduser 3.118 ii debconf [debconf-2.0] 1.5.73 pn galera-3 ii gawk 1:4.2.1+dfsg-1.1 ii iproute2 5.3.0-1 ii libc6 2.29-3 ii libdbi-perl 1.642-1+b2 ii libgnutls30 3.6.10-3 ii libpam0g 1.3.1-5 ii libstdc++69.2.1-16 ii lsb-base 11.1.0 ii lsof 4.93.2+dfsg-1 pn mariadb-client-10.3 ii mariadb-common1:10.3.18-1 pn mariadb-server-core-10.3 ii passwd1:4.7-2 ii perl 5.30.1~rc1-1 ii psmisc23.2-1+b1 ii rsync 3.1.3-8 ii socat 2.0.0~beta9-1 ii zlib1g1:1.2.11.dfsg-1+b1 Versions of packages mariadb-server-10.3 recommends: ii libhtml-template-perl 2.97-1 Versions of packages mariadb-server-10.3 suggests: ii bsd-mailx [mailx] 8.1.2-0.20180807cvs-1+b1 ii mailutils [mailx] 1:3.7-2 pn mariadb-test pn netcat-openbsd pn tinyca
Bug#943972: akonadi-backend-sqlite: expermental version impossible to install due to old qt dependency
Package: akonadi-backend-sqlite Version: 4:18.08.3-10 Severity: grave Justification: renders package unusable apt-get -t experimental install akonadi-backend-sqlite Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Certains paquets ne peuvent être installés. Ceci peut signifier que vous avez demandé l'impossible, ou bien, si vous utilisez la distribution unstable, que certains paquets n'ont pas encore été créés ou ne sont pas sortis d'Incoming. L'information suivante devrait vous aider à résoudre la situation : Les paquets suivants contiennent des dépendances non satisfaites : akonadi-backend-sqlite : Dépend: qtbase-abi-5-11-3 mais il n'est pas installable -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.81 (SMP w/2 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/bash Init: systemd (via /run/systemd/system) Versions of packages akonadi-backend-sqlite depends on: ii libc6 2.29-3 ii libgcc1 1:9.2.1-16 ii libqt5core5a [qtbase-abi-5-12-5] 5.12.5+dfsg-2 ii libqt5sql55.12.5+dfsg-2 ii libqt5sql5-sqlite 5.12.5+dfsg-2 ii libsqlite3-0 3.30.1-1 ii libstdc++69.2.1-16 Versions of packages akonadi-backend-sqlite recommends: ii akonadi-server 4:18.08.3-7+b1 akonadi-backend-sqlite suggests no packages. -- no debconf information
Bug#749991: debian-installer: Wrong kernel in debian-installer package
Hi,
Ben Hutchings wrote:
> > That looks reasonable.
> > I have prepared a proposal for this:
>
> The new text looks good to me.
>
> [...]
> > > Also, this should be an error message, not a question.
> >
> > For this, I would need some help, since I'm lacking the needed skills there.
> > The relevant part of anna.c seems to be:
> []
> > if (!kernel_packages_present) {
> > di_log(DI_LOG_LEVEL_WARNING, "no packages matching running
> > kernel %s in archive", running_kernel);
> > #ifdef __GNU__
> > /* GNU Mach does not have modules */
> > #else
> > debconf_input(debconf, "critical", "anna/no_kernel_modules");
> > if (debconf_go(debconf) == 30)
> > return 0;
> > debconf_get(debconf, "anna/no_kernel_modules");
> > if (strcmp(debconf->value, "false") == 0)
> > return 0;
>
> I think that for an error message the above 5 lines (after
> debconf_input(...)) can be changed to:
>
> debconf_go(debconf);
> return 0;
A patch is attached.
Holger
--
Holger Wansing
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
diff --git a/anna.c b/anna.c
index e03d34a..3e4552f 100644
--- a/anna.c
+++ b/anna.c
@@ -57,11 +57,8 @@ int packages_ok (di_packages *packages) {
/* GNU Mach does not have modules */
#else
debconf_input(debconf, "critical", "anna/no_kernel_modules");
- if (debconf_go(debconf) == 30)
- return 0;
- debconf_get(debconf, "anna/no_kernel_modules");
- if (strcmp(debconf->value, "false") == 0)
- return 0;
+ debconf_go(debconf);
+ return 0;
#endif
}
diff --git a/debian/anna.templates b/debian/anna.templates
index 66677ee..1c95573 100644
--- a/debian/anna.templates
+++ b/debian/anna.templates
@@ -63,17 +63,16 @@ _Description: Failed to load installer component
Loading ${PACKAGE} failed for unknown reasons. Aborting.
Template: anna/no_kernel_modules
-Type: boolean
-Default: false
+Type: error
# :sl2:
-_Description: Continue the install without loading kernel modules?
+_Description: No kernel modules found
No kernel modules were found. This probably is due to a mismatch between
the kernel used by this version of the installer and the kernel version
available in the archive.
.
- If you're installing from a mirror, you can work around this problem by
- choosing to install a different version of Debian. The install will probably
- fail to work if you continue without kernel modules.
+ You should make sure that your installation image is current (check if you
+ are using an up-to-date netboot image), or - if that's the case - try a
+ different mirror, preferably deb.debian.org.
Template: anna/retriever
Type: string
diff --git a/debian/changelog b/debian/changelog
index 806f59e..b2671e2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+anna (1.73) UNRELEASED; urgency=medium
+
+ * Change template, to give a senseful message to the user, when no kernel
+modules can be found with netboot image. Also, turn that from a question
+into an error message.
+
+ -- Holger Wansing Fri, 01 Nov 2019 22:52:30 +0100
+
anna (1.72) unstable; urgency=medium
* Team upload
Bug#925703: marked as done (gr-hpsdr: ftbfs with GCC-9)
Your message dated Fri, 1 Nov 2019 14:11:32 -0700 with message-id <20191101211132.ga21...@virgil.dodds.net> and subject line Re: gr-hpsdr: ftbfs with GCC-9 has caused the Debian Bug report #925703, regarding gr-hpsdr: 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.) -- 925703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gr-hpsdr Version: 1.2-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-9 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc9-20190321/gr-hpsdr_1.2-1_unstable_gcc9.log The last lines of the build log are at the end of this report. To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-9/porting_to.html GCC 9 also passes the linker option --as-needed by default; typical build issues are passing libraries before object files to the linker, or underlinking of convenience libraries built from the same source. [...] CMAKE_EXPORT_NO_PACKAGE_REGISTRY CMAKE_INSTALL_LIBDIR CMAKE_INSTALL_LOCALSTATEDIR CMAKE_INSTALL_SYSCONFDIR -- Build files have been written to: /<>/obj-x86_64-linux-gnu make[1]: Leaving directory '/<>' dh_auto_build -a cd obj-x86_64-linux-gnu && make -j1 make[1]: Entering directory '/<>/obj-x86_64-linux-gnu' /usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /<>/obj-x86_64-linux-gnu/CMakeFiles /<>/obj-x86_64-linux-gnu/CMakeFiles/progress.marks make -f CMakeFiles/Makefile2 all make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' make -f lib/CMakeFiles/gnuradio-hpsdr.dir/build.make lib/CMakeFiles/gnuradio-hpsdr.dir/depend make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/lib /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/lib /<>/obj-x86_64-linux-gnu/lib/CMakeFiles/gnuradio-hpsdr.dir/DependInfo.cmake --color= Scanning dependencies of target gnuradio-hpsdr make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f lib/CMakeFiles/gnuradio-hpsdr.dir/build.make lib/CMakeFiles/gnuradio-hpsdr.dir/build make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' [ 4%] Building CXX object lib/CMakeFiles/gnuradio-hpsdr.dir/hermesNB_impl.cc.o cd /<>/obj-x86_64-linux-gnu/lib && /usr/bin/c++ -Dgnuradio_hpsdr_EXPORTS -I/<>/lib -I/<>/include -I/<>/obj-x86_64-linux-gnu/lib -I/<>/obj-x86_64-linux-gnu/include -std=c++11 -fPIC -fvisibility=hidden -o CMakeFiles/gnuradio-hpsdr.dir/hermesNB_impl.cc.o -c /<>/lib/hermesNB_impl.cc [ 8%] Building CXX object lib/CMakeFiles/gnuradio-hpsdr.dir/HermesProxy.cc.o cd /<>/obj-x86_64-linux-gnu/lib && /usr/bin/c++ -Dgnuradio_hpsdr_EXPORTS -I/<>/lib -I/<>/include -I/<>/obj-x86_64-linux-gnu/lib -I/<>/obj-x86_64-linux-gnu/include -std=c++11 -fPIC -fvisibility=hidden -o CMakeFiles/gnuradio-hpsdr.dir/HermesProxy.cc.o -c /<>/lib/HermesProxy.cc [ 13%] Building CXX object lib/CMakeFiles/gnuradio-hpsdr.dir/metis.cc.o cd /<>/obj-x86_64-linux-gnu/lib && /usr/bin/c++ -Dgnuradio_hpsdr_EXPORTS -I/<>/lib -I/<>/include -I/<>/obj-x86_64-linux-gnu/lib -I/<>/obj-x86_64-linux-gnu/include -std=c++11 -fPIC -fvisibility=hidden -o CMakeFiles/gnuradio-hpsdr.dir/metis.cc.o -c /<>/lib/metis.cc [ 17%] Building CXX object lib/CMakeFiles/gnuradio-hpsdr.dir/hermesWB_impl.cc.o cd /<>/obj-x86_64-linux-gnu/lib && /usr/bin/c++ -Dgnuradio_hpsdr_EXPORTS -I/<>/lib -I/<>/include -I/<>/obj-x86_64-linux-gnu/lib -I/<>/obj-x86_64-linux-gnu/include -std=c++11 -fPIC -fvisibility=hidden -o
Bug#943963: twisted 18.9.0-4 breaks multiple autopkgtests: pkg_resources.DistributionNotFound: The 'PyHamcrest>=1.9.0' distribution was not found and is required by Twisted
Source: twisted Version: 18.9.0-4 Severity: serious X-Debbugs-CC: debian...@lists.debian.org Tags: sid bullseye User: debian...@lists.debian.org Usertags: breaks Control: affects -1 src:incremental src:automat src:nevow src:txsocksx Dear maintainers, With a recent upload of twisted the autopkgtest of incremental (and three others) fails in testing when that autopkgtest is run with the binary packages of twisted from unstable. It passes when run with only packages from testing. In tabular form: passfail twistedfrom testing18.9.0-4 incrementalfrom testing16.10.1-3 all others from testingfrom testing I copied some of the output at the bottom of this report. The error is very similar in all four reports, hence it looks like an issue on the twisted side. Feel free to clone and reassign to all the affected packages if I judged this wrongly. Currently this regression is blocking the migration of twisted to testing [1]. 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=twisted https://ci.debian.net/data/autopkgtest/testing/amd64/i/incremental/3308991/log.gz Traceback (most recent call last): File "/usr/bin/trial", line 6, in from pkg_resources import load_entry_point File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3250, in @_call_aside File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3234, in _call_aside f(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3263, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 583, in _build_master ws.require(__requires__) File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 900, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 786, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'PyHamcrest>=1.9.0' distribution was not found and is required by Twisted signature.asc Description: OpenPGP digital signature
Processed: twisted 18.9.0-4 breaks multiple autopkgtests: pkg_resources.DistributionNotFound: The 'PyHamcrest>=1.9.0' distribution was not found and is required by Twisted
Processing control commands: > affects -1 src:incremental src:automat src:nevow src:txsocksx Bug #943963 [src:twisted] twisted 18.9.0-4 breaks multiple autopkgtests: pkg_resources.DistributionNotFound: The 'PyHamcrest>=1.9.0' distribution was not found and is required by Twisted Added indication that 943963 affects src:incremental, src:automat, src:nevow, and src:txsocksx -- 943963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943963 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#943961: ceph: autopkgtest needs update for new version of python3.7: deprecation warning
Source: ceph Version: 12.2.11+dfsg1-2.1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, python...@packages.debian.org Tags: sid bullseye User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:python3.7 Dear maintainers, With a recent upload of python3.7 the autopkgtest of ceph fails in testing when that autopkgtest is run with the binary packages of python3.7 from unstable. It passes when run with only packages from testing. In tabular form: passfail python3.7 from testing3.7.5-2 ceph from testing12.2.11+dfsg1-2.1 all others from testingfrom testing I copied some of the output at the bottom of this report, the failure is on a deprecation *warning*. Please disable warnings like that, or enable the allow-stderr restriction in your test as we don't want autopkgtest to fail on warning in the Debian setup. Currently this regression is blocking the migration of python3.7 to testing [1]. Of course, python3.7 shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in python3.7 was intended and your package needs to update to the new situation. I'll mark your test as allowed to fail to enable python3.7 to migrate. 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=python3.7 https://ci.debian.net/data/autopkgtest/testing/amd64/c/ceph/3308028/log.gz autopkgtest [02:14:20]: test python3-ceph: [--- /tmp/autopkgtest-lxc.w6gyq64p/downtmp/build.p0D/src/debian/tests/python3-ceph:8: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated since Python 3.3,and in 3.9 it will stop working import rbd python3-ceph: OK autopkgtest [02:14:20]: test python3-ceph: ---] signature.asc Description: OpenPGP digital signature
Processed: ceph: autopkgtest needs update for new version of python3.7: deprecation warning
Processing control commands: > affects -1 src:python3.7 Bug #943961 [src:ceph] ceph: autopkgtest needs update for new version of python3.7: deprecation warning Added indication that 943961 affects src:python3.7 -- 943961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943961 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#874878: [freemat] Future Qt4 removal from Buster
Removal requested: #943958 Anton
Processed: your mail
Processing commands for cont...@bugs.debian.org: > owner 930057 ! Bug #930057 [src:alot] alot: FTBFS because of expired keys Owner recorded as "Chris Lamb" . > owner 943956 ! Bug #943956 [src:snakemake] snakemake: please make the build reproducible Owner recorded as "Chris Lamb" . > thanks Stopping processing here. Please contact me if you need assistance. -- 930057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930057 943956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943956 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#943955: pcb-rnd: /usr/lib/lib*.so.* symlinks point to (absolute) build directory
Package: pcb-rnd Version: 2.1.4-1 Severity: serious User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Hi, It looks like the pcb-rnd binary package ships with symlinks pointing to the absolute build directory which, of course, does not exist on the installed/runtime system: $ dget pcb-rnd dget: using existing pcb-rnd_2.1.4-1_amd64.deb $ dpkg -c pcb-rnd_2.1.4-1_amd64.deb | grep -- '->' lrwxrwxrwx root/root 0 2019-10-29 21:17 ./usr/lib/librnd-3rd.so.2 -> /build/pcb-rnd-luR6aw/pcb-rnd-2.1.4/debian/pcb-rnd/usr/lib/librnd-3rd.so.2.1.4 lrwxrwxrwx root/root 0 2019-10-29 21:17 ./usr/lib/librnd-hid.so.2 -> /build/pcb-rnd-luR6aw/pcb-rnd-2.1.4/debian/pcb-rnd/usr/lib/librnd-hid.so.2.1.4 lrwxrwxrwx root/root 0 2019-10-29 21:17 ./usr/lib/librnd-poly.so.2 -> /build/pcb-rnd-luR6aw/pcb-rnd-2.1.4/debian/pcb-rnd/usr/lib/librnd-poly.so.2.1.4 Discovered as the package is not reproducible too due to this, but solving this obviously-worse problem will implicitly fix this. Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#942276: marked as done (libmessage-passing-perl: test failure)
Your message dated Fri, 1 Nov 2019 19:17:10 +0100 with message-id <20191101181710.gs7...@jadzia.comodo.priv.at> and subject line Re: Bug#942276: libmessage-passing-perl: test failure has caused the Debian Bug report #942276, regarding libmessage-passing-perl: test failure 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.) -- 942276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942276 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libmessage-passing-perl Version: 0.116-4 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As seen on https://ci.debian.net/data/autopkgtest/unstable/amd64/libm/libmessage-passing-perl/3150247/log.gz we have a test failure which also happens at build time and makes the package FTBFS: t/configfile.t .. ok 1 - use Message::Passing; Can't locate object method "_options_prog_name" via package "Message::Passing" at /usr/share/perl5/MooX/Options/Role.pm line 348. # Tests were run but no plan was declared and done_testing() was not seen. # Looks like your test exited with 25 just after 1. Dubious, test returned 25 (wstat 6400, 0x1900) All 1 subtests passed Cheers, gregor -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl2jWdFfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgapGA//UnAloNglGDbKd6YCFqojZkoe690l2Nxkiv9g2Y1vnGxVD+X8kU3jaWb8 btnYiy2j5IUG6hfZkrK8beDaB9zozu3/UOg/QgARYI+n2WXnqhufNqS7XRBrmg6e RupIB5Yi/c3lmPzzW2rNG7QyjudvjeoncNX05uxGK98tS7Rv9cGyVOLB3AHBnxPD /WkQPtJu0myhOF0SrQMZ2mzbw5+JQlXAUNs3bi20mDP6YG5ISJB108cOnFe6lfRt OX8Gwl0ZeHLeoVrbqo9wOVtDxU4qtFJH4v6hItM7271NpFv76PDEpdhIGi1xsTx3 51uH/lLvfSuKV5xKCb2RevgG8q5JCqzXoqtov0JOtu7eO8kGCCOOLAUvlDtjyW7i zZlxj/Z2IhPUwvG1xitMGMu2/t37jXfRxoSTW532RlHrMf2UqOxlv9wgY/ygexwT arzWOvGX5fFfiHuyULYiP7Fxis/5KttCd2wnICe+I8u9dVURlFWRSUDnoQ1PC9my fw8KNF7/J9a+LkrHsb3rFwEVzDy8sizAimYnJyuz63SeEzBnnavEuFLLsmf6Bqdw akeXO28zlwN3PC8RlkrOmPzZPH+F1wuC+L6SzTH2A97fG8eKlogkczs8UXSA5PsI IEynKsJPZSbEUz/tRNJUPuE5v63vLK2scganIuXGwMoj+KDOeGE= =Yfoi -END PGP SIGNATURE- --- End Message --- --- Begin Message --- On Mon, 14 Oct 2019 18:01:01 +0200, gregor herrmann wrote: > > t/configfile.t .. > > ok 1 - use Message::Passing; > > Can't locate object method "_options_prog_name" via package > > "Message::Passing" at /usr/share/perl5/MooX/Options/Role.pm line 348. > > # Tests were run but no plan was declared and done_testing() was not seen. > > # Looks like your test exited with 25 just after 1. > > Dubious, test returned 25 (wstat 6400, 0x1900) > > All 1 subtests passed > > Cf. #942275 This was indeed #942275, and autopkgtests are passing again: https://ci.debian.net/packages/libm/libmessage-passing-perl/unstable/amd64/ Hence closing this bug. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Peter Ratzenbeck: Lichterloh signature.asc Description: Digital Signature --- End Message ---
Bug#931944: marked as done (vtk7: FTBFS with PROJ 6)
Your message dated Fri, 01 Nov 2019 16:36:58 + with message-id and subject line Bug#931944: fixed in vtk7 7.1.1+dfsg2-1 has caused the Debian Bug report #931944, regarding vtk7: FTBFS with PROJ 6 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.) -- 931944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vtk7 Version: 7.1.1+dfsg1-12 Severity: important Tags: upstream User: debian-...@lists.debian.org Usertags: proj-6 Dear Maintainer, Your package FTBFS with PROJ 6 from experimental. Disabling the PROJ support was not an option as it was for vtk6. You may want to reinstate the embedded copy and use that instead. Upstream is aware of the issue, see: https://github.com/eclipse/sumo/issues/5299 Kind Regards, Bas --- End Message --- --- Begin Message --- Source: vtk7 Source-Version: 7.1.1+dfsg2-1 We believe that the bug you reported is fixed in the latest version of vtk7, 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 931...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gert Wollny (supplier of updated vtk7 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, 01 Nov 2019 09:19:22 +0100 Source: vtk7 Architecture: source Version: 7.1.1+dfsg2-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Gert Wollny Closes: 931944 Changes: vtk7 (7.1.1+dfsg2-1) unstable; urgency=medium . * Upload to unstable, Closes: #931944 Checksums-Sha1: 503253dd664a584773e0e428216cf6fde9468212 3661 vtk7_7.1.1+dfsg2-1.dsc 38ef0132f4e587f23bba2576c0f684a55d8ec14f 26796 vtk7_7.1.1+dfsg2-1.debian.tar.xz 2d56bec6194c0906ecbe09f09bbca55cd6026f92 32065 vtk7_7.1.1+dfsg2-1_source.buildinfo Checksums-Sha256: bd0c19e5649f2558254c4f23b0b0b13380924b184b47075dbbf8cd8c9e0228bb 3661 vtk7_7.1.1+dfsg2-1.dsc 5822286eec19e4f0ef21f534d5ea3f04c80208ccada7379b89bfa52e8955ed3d 26796 vtk7_7.1.1+dfsg2-1.debian.tar.xz 7cd8051f562fa5af5c7d4d4f43c5f86e9fc1e58309521154c36577572714d9ff 32065 vtk7_7.1.1+dfsg2-1_source.buildinfo Files: 3e61ee1c42eac3ceff9749144333aa61 3661 graphics optional vtk7_7.1.1+dfsg2-1.dsc 7f564a7c41cb203b834e2bfd7b5dd240 26796 graphics optional vtk7_7.1.1+dfsg2-1.debian.tar.xz 2f17342b2e6d09e842c49e64d737acfb 32065 graphics optional vtk7_7.1.1+dfsg2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEELtRZww6NuKjZPKd6l/LU/KCfME4FAl28W98ACgkQl/LU/KCf ME7S3g//S5e4jyvLteOg1ctCskxpwCqqIY1x6vpx+zXRRsDIgp5vNGoV6M/S3Ekf 9ESqVYzRPjHAquLr9jNbYGs6MmQ/Nel4ZE5W6Hw0utxhZLb0cDs10lnbZ7zvKX8K 5nRK06LNOp05tfGDAyRouMAo2B0z+w5qZJJ3yO8CekbNjUIgvGZ0a/OTXp4pBmpt cezLhBihk1V1V03/z8gKkunLKSLJWYBHWUTpWQBy7d7pVxfykQV/55uX2DEIg4iI 5ouZRcRHQo8PqJsi6V9QPrL460Ko26z4xC8dAcCCz45HhEEQSrj55rosqy5tXXTn izxxThK+WUBKBT6E7+aZ2iqLmNU27QIPyil5g80RT6diknQH742LAFP8zsqeRdoi sfsTreLfvu3eZ9zQnVAhrEtuBmbEEhRMCCWGldaApLFmjBqsZzfpizUY43m0PqPj yNAWUrSefusv6QJ5VQTLSSmSnpVWfuSwiSXHpyZmy8yuNCH+4s0OsWfX/XbjV7yq l6JGeLj1/0UxHbdW4GAcmm1eAbSWXL01NCLyQkJN/fBbIV2Lhg9d1hPj1dhj8L9n 8DFTX3zMJw1GV7P/nUVj2zELS5fu3El9hEF5R6H9fBmAkA9MHVDL1K8efdsqdf8r gT8jlw3yT+q2XZjsCFVmBu0QY1Qo7bW2TXLxjQNfsmnIdI4R+KY= =4PiX -END PGP SIGNATURE End Message ---
Bug#943664: xserver-xorg-video-radeon: Same behaviour on Thinkpad T41
On Thu 31 Oct 2019 at 20:39:18 +0100 Michel Dänzer wrote: > We'd again need to see the corresponding Xorg log file. 1. Modified /etc/X11/xorg.conf : # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "de" # Option"XkbVariant""nodeadkeys" Option"XkbOptions" "compose:caps" # P. R.-P., Mo., 25. Mai 2009 EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" EndSection Section "Device" Identifier "Configured Video Device" Driver"modesetting" EndSection Section "Monitor" Identifier "Configured Monitor" EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" EndSection 2. /home/petra/.local/share/xorg/Xorg.0.log : [ 451.063] X.Org X Server 1.20.4 X Protocol Version 11, Revision 0 [ 451.063] Build Operating System: Linux 4.9.0-8-amd64 i686 Debian [ 451.064] Current Operating System: Linux netty 5.2.0-3-686 #1 SMP Debian 5.2.17-1 (2019-09-26) i686 [ 451.064] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.2.0-3-686 root=UUID=496e0e0a-6e7c-46c2-9132-315243394a2d ro framebuffer=false quiet fb=false systemd.show_status=true [ 451.065] Build Date: 05 March 2019 08:11:12PM [ 451.065] xorg-server 2:1.20.4-1 (https://www.debian.org/support) [ 451.065] Current version of pixman: 0.36.0 [ 451.066]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 451.066] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 451.068] (==) Log file: "/home/petra/.local/share/xorg/Xorg.0.log", Time: Thu Oct 31 21:08:45 2019 [ 451.098] (==) Using config file: "/etc/X11/xorg.conf" [ 451.106] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 451.232] (==) No Layout section. Using the first Screen section. [ 451.232] (**) |-->Screen "Default Screen" (0) [ 451.232] (**) | |-->Monitor "Configured Monitor" [ 451.268] (==) No device specified for screen "Default Screen". Using the first device section listed. [ 451.268] (**) | |-->Device "Configured Video Device" [ 451.268] (==) Automatically adding devices [ 451.268] (==) Automatically enabling devices [ 451.268] (==) Automatically adding GPU devices [ 451.268] (==) Max clients allowed: 256, resource mask: 0x1f [ 451.369] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 451.369]Entry deleted from font path. [ 451.509] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 451.509] (==) ModulePath set to "/usr/lib/xorg/modules" [ 451.509] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 451.509] (II) Loader magic: 0x6eb740 [ 451.509] (II) Module ABI versions: [ 451.509]X.Org ANSI C Emulation: 0.4 [ 451.509]X.Org Video Driver: 24.0 [ 451.509]X.Org XInput driver : 24.1 [ 451.509]X.Org Server Extension : 10.0 [ 451.512] (++) using VT number 1 [ 451.519] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_35 [ 451.522] (II) xfree86: Adding drm device (/dev/dri/card0) [ 451.524] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0 [ 451.531] (--) PCI:*(1@0:0:0) 1002:4c57:1014:0530 rev 0, Mem @ 0xe000/134217728, 0xc010/65536, I/O @ 0x3000/256, BIOS @ 0x/131072 [ 451.551] (II) LoadModule: "glx" [ 451.589] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 452.136] (II) Module glx: vendor="X.Org Foundation" [ 452.136]compiled for 1.20.4, module version = 1.0.0 [ 452.136]ABI class: X.Org Server Extension, version 10.0 [ 452.136] (II) LoadModule: "modesetting" [
Bug#943509: libsqlite3 (Re: Bug#943509: python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4)
Hi Chiaki, On Thu, Oct 31, 2019 at 9:09 PM ISHIKAWA,chiaki wrote: > I vouch that there seems to be a serious issue in libsqlite3 3.30.1-1. It's not that fatal like it may seem so. > I came here because it seems that I have an issue with sqlite3 on my > linux installation. > The problem manifested as database operation failures during thunderbird > mail client regression testing (called mach xcpshell-tests|) Is there a documented way to get and run it locally? > I looks someone on Ubuntu did not see it this month and mozilla's > compilation and testing farm machines do not seem to see it. They run > CentOs if I am not mistaken. Which version of CentOS? Its latest release, versioned 8 has SQLite3 3.26.0 if I'm not mistaken. > https://bugzilla.mozilla.org/show_bug.cgi?id=1589779 > > So I thought maybe the current installation of libsqlite3 on my linux PC > was to blame. Might be, but SQLite3 3.30.1 should be safe. > Well, it looks that is the case if I read the exchanges here correctly. > My libsqlite3 seems to be affected: the version is 3.30.1-1 > (The problem was not observed in August. I am not sure if the upgrade of > libsqlite3 happened during then and now.) > > What do people suggest that best course of action under the circumstances? > > Downgrade (to which version and how) or install newer libsqlite3 (where)? All uploaded SQLite3 Debian packages should be archived[1]. Try downgrading it to 3.29.0-2 first and see if it helps. > All I can say is that the same tests that deal with database that worked > for years suddenly broke in the last several weeks. So my bug report > would not be that useful :-( May you have a date when you first experienced it? As sqlite3 3.30.0 is in the Debian archives since the fifth of October, this may narrow down the issue a bit. Regards, Laszlo/GCS [1] http://snapshot.debian.org/package/sqlite3/
Bug#874878: [freemat] Future Qt4 removal from Buster
Yes, I think the package should be removed. Also the package has no active uploader and nobody in science group identified such an interest [1]. I will take care about it. [1] https://lists.debian.org/debian-science/2019/09/msg00018.html Anton
Bug#943597: marked as done (Seems to be missing required dependencies)
Your message dated Fri, 01 Nov 2019 13:48:54 + with message-id and subject line Bug#943597: fixed in libsys-info-base-perl 0.7807-3 has caused the Debian Bug report #943597, regarding Seems to be missing required dependencies 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.) -- 943597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libsys-info-base-perl Version: 0.7807-2 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tried to use Sys::Info::Device::CPU today, and first the Synopsis from the perldoc doesn't work — it starts with 'use Sys::Info', which isn't installed. Nor packaged, AFAICT. So tried to use it directly: $ perl -MSys::Info::Device::CPU -E 'my $info = Sys::Info::Device::CPU->new' Operating system identified as: 'Linux'. Native driver can not be loaded: Error loading Sys::Info::Driver::Linux::Device::CPU: Can't locate Sys/Info/Driver/Linux/Device/CPU.pm in @INC (you may need to install the Sys::Info::Driver::Linux::Device::CPU module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Sys/Info/Base.pm line 45. at /usr/share/perl5/Sys/Info/Device/CPU.pm line 9. . Falling back to compatibility mode Error loading Sys::Info::Driver::Unknown::Device::CPU: Can't locate Sys/Info/Driver/Unknown/Device/CPU.pm in @INC (you may need to install the Sys::Info::Driver::Unknown::Device::CPU module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Sys/Info/Base.pm line 45. at /usr/share/perl5/Sys/Info/Device/CPU.pm line 9. BEGIN failed--compilation aborted at /usr/share/perl5/Sys/Info/Device/CPU.pm line 9. Compilation failed in require. BEGIN failed--compilation aborted. Those come from the Sys-Info-Driver-Linux and Sys-Info-Driver-Unknown packages on CPAN, also AFAIK not packaged. Sys::Info::OS similarly does not work. It doesn't seem like libsys-info-base-perl have any functionality w/o the related packages. - -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (130, 'unstable-debug'), (130, 'unstable'), (120, 'experimental-debug'), (120, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 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/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libsys-info-base-perl depends on: ii perl 5.30.0-8 libsys-info-base-perl recommends no packages. libsys-info-base-perl suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iHMEARECADMWIQTlAc7j4DAtSNRJJ0z7P4jCVepZ/gUCXbVCvhUcYW50aG9ueUBk ZXJvYmVydC5uZXQACgkQ+z+IwlXqWf7bYACeNgNe4JBivWCyGfXrZSwxvyUGVZwA n3dkH76BmyphAJmsIS+gjvlyA/UN =ZM5j -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: libsys-info-base-perl Source-Version: 0.7807-3 We believe that the bug you reported is fixed in the latest version of libsys-info-base-perl, 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. gregor herrmann (supplier of updated libsys-info-base-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 01 Nov 2019 14:29:24 +0100 Source: libsys-info-base-perl Architecture: source Version: 0.7807-3 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 943597 Changes:
Processed (with 1 error): unarchiving 701076, reopening 701076, notfixed 701076 in 4.8.1-0.1+rm, unarchiving 762827 ...
Processing commands for cont...@bugs.debian.org:
> unarchive 701076
Bug #701076 {Done: Debian FTP Masters }
[tortoisehg] tortoisehg raises exceptions on close
Unarchived Bug 701076
> reopen 701076
Bug #701076 {Done: Debian FTP Masters }
[tortoisehg] tortoisehg raises exceptions on close
Bug reopened
Ignoring request to alter fixed versions of bug #701076 to the same values
previously set
> notfixed 701076 4.8.1-0.1+rm
Bug #701076 [tortoisehg] tortoisehg raises exceptions on close
There is no source info for the package 'tortoisehg' at version '4.8.1-0.1+rm'
with architecture ''
Unable to make a source version for version '4.8.1-0.1+rm'
Ignoring request to alter fixed versions of bug #701076 to the same values
previously set
> unarchive 762827
Bug #762827 {Done: Debian FTP Masters }
[tortoisehg] tortoisehg exits almost immidiatly after startup
Unarchived Bug 762827
> reopen 762827
Bug #762827 {Done: Debian FTP Masters }
[tortoisehg] tortoisehg exits almost immidiatly after startup
Bug reopened
Ignoring request to alter fixed versions of bug #762827 to the same values
previously set
> notfixed 762827 4.8.1-0.1+rm
Bug #762827 [tortoisehg] tortoisehg exits almost immidiatly after startup
There is no source info for the package 'tortoisehg' at version '4.8.1-0.1+rm'
with architecture ''
Unable to make a source version for version '4.8.1-0.1+rm'
Ignoring request to alter fixed versions of bug #762827 to the same values
previously set
> unarchive 921704
Bug #921704 {Done: Debian FTP Masters }
[src:tortoisehg] tortoisehg: uninstallable with mercurial 4.9
Unarchived Bug 921704
> reopen 921704
Bug #921704 {Done: Debian FTP Masters }
[src:tortoisehg] tortoisehg: uninstallable with mercurial 4.9
Bug reopened
Ignoring request to alter fixed versions of bug #921704 to the same values
previously set
> notfixed 921704 4.8.1-0.1+rm
Bug #921704 [src:tortoisehg] tortoisehg: uninstallable with mercurial 4.9
The source 'tortoisehg' and version '4.8.1-0.1+rm' do not appear to match any
binary packages
Ignoring request to alter fixed versions of bug #921704 to the same values
previously set
> unarchive 935660
Bug #935660 {Done: Debian FTP Masters }
[src:tortoisehg] tortoisehg: Obsolete libs (python2) - depends python-pyqt5.qsci
Unarchived Bug 935660
> reopen 935660
Bug #935660 {Done: Debian FTP Masters }
[src:tortoisehg] tortoisehg: Obsolete libs (python2) - depends python-pyqt5.qsci
Bug reopened
Ignoring request to alter fixed versions of bug #935660 to the same values
previously set
> notfixed 935660 4.8.1-0.1+rm
Bug #935660 [src:tortoisehg] tortoisehg: Obsolete libs (python2) - depends
python-pyqt5.qsci
The source 'tortoisehg' and version '4.8.1-0.1+rm' do not appear to match any
binary packages
Ignoring request to alter fixed versions of bug #935660 to the same values
previously set
> unarchive 938679
Bug #938679 {Done: Debian FTP Masters }
[src:tortoisehg] tortoisehg: Python2 removal in sid/bullseye
Unarchived Bug 938679
> reopen 938679
Bug #938679 {Done: Debian FTP Masters }
[src:tortoisehg] tortoisehg: Python2 removal in sid/bullseye
Bug reopened
Ignoring request to alter fixed versions of bug #938679 to the same values
previously set
> notfixed 938679 4.8.1-0.1+rm
Bug #938679 [src:tortoisehg] tortoisehg: Python2 removal in sid/bullseye
The source 'tortoisehg' and version '4.8.1-0.1+rm' do not appear to match any
binary packages
Ignoring request to alter fixed versions of bug #938679 to the same values
previously set
> unarchive 922565
> reopen 922565
Bug #922565 [wnpp] ITA: tortoisehg -- Graphical tool for working with Mercurial
Bug 922565 is not marked as done; doing nothing.
> notfixed 922565 4.8.1-0.1+rm
Bug #922565 [wnpp] ITA: tortoisehg -- Graphical tool for working with Mercurial
There is no source info for the package 'wnpp' at version '4.8.1-0.1+rm' with
architecture ''
Unable to make a source version for version '4.8.1-0.1+rm'
Ignoring request to alter fixed versions of bug #922565 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
701076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701076
762827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762827
921704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921704
922565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922565
935660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935660
938679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#749991: debian-installer: Wrong kernel in debian-installer package
On Fri, 2019-11-01 at 00:09 +0100, Holger Wansing wrote:
> Hi,
>
> Ben Hutchings wrote:
> > On Sun, 2019-10-27 at 20:18 +0100, Holger Wansing wrote:
> > > Bugreport against kernel version mismatch, when using outdated or broken
> > > netboot images:
> > >
> > >
> > > Since it's unlikely that we completely prevent this issue to happen,
> > > maybe we
> > > could at least change the error message, saying that the user should try
> > > another / a newer installation image?
> > > (as already suggested in bug#367515)
> > >
> > > It would be a good time for such template changing now...
> > > Patch attached.
> >
> > I feel that we ought to give a more definite answer, instead of "you
> > can try" and "will probably fail". I don't think that "choosing to
> > install a different version of Debian" is likely to be a useful answer
> > very often, and continuing without kernel modules is definitely going
> > to fail.
> >
> > If I understood correctly, this message can only appear when using a
> > netboot image, and can be caused by either (a) old netboot image or (b)
> > broken mirror. If that's right, we should recommend (a) make sure your
> > netboot image is current (b) if it is, then try another mirror,
> > recommending deb.debian.org.
>
> That looks reasonable.
> I have prepared a proposal for this:
The new text looks good to me.
[...]
> > Also, this should be an error message, not a question.
>
> For this, I would need some help, since I'm lacking the needed skills there.
> The relevant part of anna.c seems to be:
[]
> if (!kernel_packages_present) {
> di_log(DI_LOG_LEVEL_WARNING, "no packages matching running
> kernel %s in archive", running_kernel);
> #ifdef __GNU__
> /* GNU Mach does not have modules */
> #else
> debconf_input(debconf, "critical", "anna/no_kernel_modules");
> if (debconf_go(debconf) == 30)
> return 0;
> debconf_get(debconf, "anna/no_kernel_modules");
> if (strcmp(debconf->value, "false") == 0)
> return 0;
I think that for an error message the above 5 lines (after
debconf_input(...)) can be changed to:
debconf_go(debconf);
return 0;
[...]
> I assume, just turning
>
> = snip
> Template: anna/no_kernel_modules
> Type: boolean
> Default: false
> # :sl2:
> _Description: Continue the install without loading kernel modules?
> = snap
>
> into
>
> = snip
> Template: anna/no_kernel_modules
> Type: error
> # :sl2:
> _Description: No kernel modules found
> = snap
>
> is not enough here?
Right, because there will no longer be any answer for the code to get.
Ben.
--
Ben Hutchings
Reality is just a crutch for people who can't handle science fiction.
signature.asc
Description: This is a digitally signed message part
Bug#943597: marked as pending in libsys-info-base-perl
Control: tag -1 pending Hello, Bug #943597 in libsys-info-base-perl 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/perl-team/modules/packages/libsys-info-base-perl/commit/e368b44aaafb13e291c9cadc5a0ac69fffdde83e Add libsys-info-driver-linux-perl to recommends. Closes: #943597 (this message was generated automatically) -- Greetings https://bugs.debian.org/943597
Processed: Bug#943597 marked as pending in libsys-info-base-perl
Processing control commands: > tag -1 pending Bug #943597 [libsys-info-base-perl] Seems to be missing required dependencies Added tag(s) pending. -- 943597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#939571: Found one clue about this bug
I do not know exactly why this bug arises, but here are the facts:
- when I download
http://ftp.de.debian.org/debian/pool/main/p/python-pyqtgraph/python3-pyqtgraph_0.10.0-4_all.deb
and inspect this package, it misses the directory
/usr/lib/python3/pyqtgraph/widget, hence the error message reported in
the bug report: "ModuleNotFoundError: No module named 'pyqtgraph.widgets'"
- when I tried to know why this directory is missing from the package, I
cloned the fork https://salsa.debian.org/georgesk/python-pyqtgraph and
built the package again with debuild: then, the same bug happens:
/usr/lib/python3/pyqtgraph/widget is missing again
- I patched the file setup.py, in order to view better le list of
packages and sub-packages which were to install, and added a single
line to print a message with the value of the variable allPackages:
[line 68] print("Hello, allPackages =", allPackages)
it happens that 'pyqtgraph.widget' is part of the list allPackages
sometimes, and sometimes, not. THIS IS WEIRD!
- it seems that the function listAllPackages from the module
tools.setupHelpers is not completely reliable, though I have no
precise idea why. I could get a valid list of packages by calling this
function from Python3 in interactive mode. I have no time to create a
minimal example which can raise that buggy behavior, I just suspect
that is come from Python's internals.
- here is attached a patch which provides the right list of packages as
a hard-coded list. This list has been returned by the function
listAllPackages() in interactive mode, and contains
"pyqtgraph.widgets"; with that patch, the package is effective again.
I propose a pull request for this patch, in Salsa.
Best regards, Georges.
--
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70
Index: python-pyqtgraph/setup.py
===
--- python-pyqtgraph.orig/setup.py
+++ python-pyqtgraph/setup.py
@@ -63,8 +63,8 @@ sys.path.insert(0, os.path.join(path, 't
import setupHelpers as helpers
## generate list of all sub-packages
-allPackages = (helpers.listAllPackages(pkgroot='pyqtgraph') +
- ['pyqtgraph.'+x for x in helpers.listAllPackages(pkgroot='examples')])
+allPackages = ['pyqtgraph', 'pyqtgraph.GraphicsScene', 'pyqtgraph.util', 'pyqtgraph.util.colorama', 'pyqtgraph.tests', 'pyqtgraph.parametertree', 'pyqtgraph.opengl', 'pyqtgraph.opengl.items', 'pyqtgraph.pixmaps', 'pyqtgraph.graphicsItems', 'pyqtgraph.graphicsItems.PlotItem', 'pyqtgraph.graphicsItems.ViewBox', 'pyqtgraph.flowchart', 'pyqtgraph.flowchart.library', 'pyqtgraph.metaarray', 'pyqtgraph.widgets', 'pyqtgraph.dockarea', 'pyqtgraph.canvas', 'pyqtgraph.multiprocess', 'pyqtgraph.imageview', 'pyqtgraph.exporters', 'pyqtgraph.exporters.tests', 'pyqtgraph.console'] + ['pyqtgraph.'+x for x in helpers.listAllPackages(pkgroot='examples')]
+
## Decide what version string to use in the build
version, forcedVersion, gitVersion, initVersion = helpers.getVersionStrings(pkg='pyqtgraph')
signature.asc
Description: PGP signature
Bug#943812: marked as done (libsopt-dev: missing dependency on libopenmpi-dev)
Your message dated Fri, 01 Nov 2019 12:19:54 + with message-id and subject line Bug#943812: fixed in sopt 3.0.1-8 has caused the Debian Bug report #943812, regarding libsopt-dev: missing dependency on libopenmpi-dev 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.) -- 943812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943812 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libsopt-dev Version: 3.0.1-7 Severity: serious Justification: missing required dependency User: debian-cr...@lists.debian.org Usertags: ftcbfs Control: affects -1 + src:purify The headers shipped in libsopt-dev #include , but they fail depending on an mpi implementation. This is a bug. Moreover, /usr/share/cmake/sopt/SoptCPPTargets.cmake declares an imported library "sopt" whose INTERFACE_INCLUDE_DIRECTORIES contain /usr/lib/arm-linux-gnueabi/openmpi/include/openmpi. Any use of this target fails at the cmake level unless libopenmpi-dev is installed. Here is an example of how it breaks purify. | CMake Error in cpp/purify/CMakeLists.txt: | Imported target "sopt" includes non-existent path | | "/usr/lib/arm-linux-gnueabi/openmpi/include/openmpi" | | in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons include: | | * The path was deleted, renamed, or moved to another location. | | * An install or uninstall procedure did not complete successfully. | | * The installation package was faulty and references files it does not | provide. A quick glimpse at the package also suggests that libeigen3-dev very likely should also be a dependency. Helmut --- End Message --- --- Begin Message --- Source: sopt Source-Version: 3.0.1-8 We believe that the bug you reported is fixed in the latest version of sopt, 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. Ole Streicher (supplier of updated sopt package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 01 Nov 2019 12:50:31 +0100 Source: sopt Architecture: source Version: 3.0.1-8 Distribution: unstable Urgency: medium Maintainer: Debian Astro Team Changed-By: Ole Streicher Closes: 943812 Changes: sopt (3.0.1-8) unstable; urgency=medium . * Add libopenmpi-dev build dependency (Closes: #943812) Checksums-Sha1: c387e35196958334b4c6e5913140e8d04759fe64 2097 sopt_3.0.1-8.dsc fdf66a8dda914f5759adcad37462f0858c08dbbe 7620 sopt_3.0.1-8.debian.tar.xz Checksums-Sha256: 4785f628f57a7a03fec3f9276354261385e713e91704419d2a608abbe5db4021 2097 sopt_3.0.1-8.dsc 48f144ca8c4d1607766f211640e07655ee0816587badc85090509a9219f69362 7620 sopt_3.0.1-8.debian.tar.xz Files: aaf66ccf50b1ab5baae4fdce5bd017c8 2097 science optional sopt_3.0.1-8.dsc a98bae1cf4340d2ca12ccd558f8e8fd7 7620 science optional sopt_3.0.1-8.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAl28H7AACgkQcRWv0HcQ 3PcBaQ//UIx7sQpHTzHVgqp68VbpSyrhl+V2Lrt2NqeON8TJSKVGmdfzWxBgnzsh TVSJ9S/by4DezHK/GKXBEkqB/YreY9ihA08fd8L6l33IUbhwOB/gkINfPodmTc6k FZtmiCCM+FbTF11sRT4CKIEu+3PqVOb7t7Ecr5HBP74J1vvOiTCeFtLnPbFH1Xx7 gB1OPjWupsC54NSVRC/j+Jk8LUjHz/2jNsKCUy6YlM5Y8Bhf/SchH0M+T+wK6GcI U8X9GzUV1fCu/9Bs60EhzGsIOK4gZsnUtlj+69LtZrICuaUauT+AD2ui3tpeTX4Q YlSGw3n7tzXD5AYWf4RExgNAR2IOn/UuD2bieDeZiOBUv57WVG2jgSAPgvQn2gwR K8WyrOWsajoFzjGinMpvXs/aGJQ71dLRYD3gEfBwm8i777OAP7wW01J0GW4Pnolt DsTYaZIs+9Q9Fk4MdsNsCd/zZylDhpPgnHe7xHKQAbV8SIrdg1dBKVBwoVwYsEWh 0edb9B0OlxeAiBDp5cQGJ2KpxSJjkw0bjrkgEKgpzwXtn0ovCKo/7qhuQWWIMXGs 0dLl8KY9GJLiJUVGWloDWbqtjiRVZwcoCL+Iln66zKJCwg+7cjDNuJv70Sq9sj/4 dRhlkUX5qaxP0zzkO/YVYxwpA7Om1cGp28N4eRPXMOmuVYMMMAs= =4bhh -END PGP SIGNATURE End Message ---
Processed: 938425.2
Processing commands for cont...@bugs.debian.org: > user debian-pyt...@lists.debian.org Setting user to debian-pyt...@lists.debian.org (was li...@jcf.pm). > usertag 938425 + py2keep Usertags were: py2removal. Usertags are now: py2removal py2keep. > severity 938425 normal Bug #938425 [src:sabnzbdplus] sabnzbdplus: Python2 removal in sid/bullseye Severity set to 'normal' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 938425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919058: its-tools: crashes
On Mon, Oct 28, 2019 at 12:55:13PM +0100, Santiago Vila wrote: > I can reproduce this as well, randomly, while building debmake-doc. > > (Changing affects because FTBFS bugs are better categorized as being > bugs in the source). There's a patch here to libxml2 that purports to fix this bug: https://github.com/void-linux/void-packages/blob/884ef902190645863c97b29af5cfc2d4104c2078/srcpkgs/libxml2-python/patches/python3-utf8.patch which has been linked in my original itstool bug report at https://github.com/itstool/itstool/issues/36 I'll see one of these days whether applying it helps. /Lars
Bug#938425: 938425.1
control: user debian-pyt...@lists.debian.org control: usertags -1 py2keep control: severity: -1 normal See my prior comment. pgp5AZp_Lo547.pgp Description: OpenPGP digital signature
Bug#943943: getfem++ ftbfs on s390x where it built before
Package: src:getfem++ Version: 5.3+dfsg1-1 Severity: serious Tags: sid bullseye getfem++ ftbfs on s390x where it built before, test failures. https://buildd.debian.org/status/package.php?p=getfem%2B%2B shows that all other 64bit big endian targets also fail.
Processed: retitle 942877 to goattracker silently quits with exit code 1 on Debian Bullseye
Processing commands for cont...@bugs.debian.org: > retitle 942877 goattracker silently quits with exit code 1 on Debian Bullseye Bug #942877 [goattracker] goattracker sliently quits wiht exit code 1 on Debian Bullseye Changed Bug title to 'goattracker silently quits with exit code 1 on Debian Bullseye' from 'goattracker sliently quits wiht exit code 1 on Debian Bullseye'. > thanks Stopping processing here. Please contact me if you need assistance. -- 942877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: raising severity of py2removal issues for pygtk rdeps which is scheduled for removal in bullseye (https://lists.debian.org/debian-gtk-gnome/2019/10/msg00001.html)
Processing commands for cont...@bugs.debian.org: > severity 942977 serious Bug #942977 [src:disk-manager] disk-manager: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 937453 serious Bug #937453 [src:pygtksourceview] pygtksourceview: Python2 removal in sid/bullseye Ignoring request to change severity of Bug 937453 to the same value. > severity 942938 serious Bug #942938 [src:cylc] cylc: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 938784 serious Bug #938784 [src:virtualbricks] virtualbricks: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 936843 serious Bug #936843 [src:libayatana-appindicator] libayatana-appindicator: Python2 removal in sid/bullseye Ignoring request to change severity of Bug 936843 to the same value. > severity 938823 serious Bug #938823 [src:wicd] wicd: Python2 removal in sid/bullseye Severity set to 'serious' from 'important' > severity 936658 serious Bug #936658 [src:gr-gsm] gr-gsm: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 936672 serious Bug #936672 [src:gtklick] gtklick: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 943230 serious Bug #943230 [src:pythoncad] pythoncad: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 936978 serious Bug #936978 [src:magicor] magicor: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 938556 serious Bug #938556 [src:sqlkit] sqlkit: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 936442 serious Bug #936442 [src:d-rats] d-rats: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 938867 serious Bug #938867 [src:yorick-spydr] yorick-spydr: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 938731 serious Bug #938731 [src:twisted] twisted: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 938604 serious Bug #938604 [src:sushi] sushi: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 938520 serious Bug #938520 [src:sozi] sozi: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 936608 serious Bug #936608 [src:gextractwinicons] gextractwinicons: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 937422 serious Bug #937422 [src:pyenchant] pyenchant: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 937179 serious Bug #937179 [src:obmenu] obmenu: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 943202 serious Bug #943202 [src:olsrd] olsrd: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 936513 serious Bug #936513 [src:ffrenzy] ffrenzy: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 936221 serious Bug #936221 [src:blueproximity] blueproximity: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 936788 serious Bug #936788 [src:key-mon] key-mon: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 936674 serious Bug #936674 [src:gtk-recordmydesktop] gtk-recordmydesktop: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 936721 serious Bug #936721 [src:idjc] idjc: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 936297 serious Bug #936297 [src:cherrytree] cherrytree: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 938582 serious Bug #938582 [src:sugar-base] sugar-base: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 937066 serious Bug #937066 [src:monkeysign] monkeysign: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 936585 serious Bug #936585 [src:gbirthday] gbirthday: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 939111 serious Bug #939111 [src:screenkey] screenkey: Python2 removal in sid/bullseye -- drop python-distutils-extra build dependency Severity set to 'serious' from 'normal' > severity 936707 serious Bug #936707 [src:hocr] hocr: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 937175 serious Bug #937175 [src:nxt-python] nxt-python: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 937324 serious Bug #937324 [src:prey] prey: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 936601 serious Bug #936601 [src:gespeaker] gespeaker: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 936680 serious Bug #936680 [src:gwakeonlan] gwakeonlan: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 936228 serious Bug #936228
Bug#936307: claws-mail: Python2 removal in sid/bullseye
control: user debian-pyt...@lists.debian.org control: usertags -1 - py2keep On 30.10.19 17:54, Ricardo Mones wrote: control: block -1 by 943308 On Wed, Oct 30, 2019 at 05:24:42PM +0100, Matthias Klose wrote: Control: tags -1 + moreinfo The python-gtk2 dependency has an RC issue now. https://bugs.debian.org/937452 It looks like nobody wants to step up to maintain that. What are you planning to do? It's already done... :-) Thanks!
Bug#943566: marked as done (FTBFS with nettle 3.5.1)
Your message dated Fri, 1 Nov 2019 11:21:50 +0100 with message-id <95c5cd25-4d92-f882-08a0-808f6e6e3...@debian.org> and subject line Re: Bug#943566: FTBFS with nettle 3.5.1 has caused the Debian Bug report #943566, regarding FTBFS with nettle 3.5.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 943566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943566 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pktanon Version: 2~git20160407.0.2bde4f2+dfsg-5 Severity: serious Tags: ftbfs Justification: ftbfs Control: block 941150 by -1 Dear maintainer, Currently the nettle 3.5.1 transition is going on. I tried to binNMU your package but it fails to build from source on all architectures. Paul https://buildd.debian.org/status/package.php?p=pktanon Tail of log for pktanon on amd64: 65 |__SOCKADDR_ARG __addr, socklen_t *__restrict __addr_len) | ^ In file included from RawSocketRecordsHandler.cpp:20: /usr/include/net/if.h:90:12: note: class type ‘sockaddr’ is incomplete 90 | struct sockaddr ifa_addr; /* Address of interface. */ |^~~~ g++ -DPACKAGE_NAME=\"pktanon\" -DPACKAGE_TARNAME=\"pktanon\" -DPACKAGE_VERSION=\"2.0-beta\" -DPACKAGE_STRING=\"pktanon\ 2.0-beta\" -DPACKAGE_BUGREPORT=\"bl...@kit.edu\" -DPACKAGE_URL=\"\" -DPACKAGE=\"pktanon\" -DVERSION=\"2.0-beta\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_STDDEF_H=1 -DHAVE_CXX11=1 -DHAVE_SOCKET=1 -DHAVE_SYS_SOCKET_H=1 -DHAVE_ARPA_INET_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_NETINET_IN_H=1 -DHAVE_LINUX_IF_ETHER_H=1 -DHAVE_NETPACKET_PACKET_H=1 -DHAVE_NET_IF_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_FCNTL_H=1 -DHAVE_PCAP_PCAP_H=1 -I. -O2 -pipe -Werror=return-type -I../include -g -DTRACE_ENABLED -DHAVE_LIBPCAP -I../libpktanon -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o SocketOutput.o SocketOutput.cpp g++ -DPACKAGE_NAME=\"pktanon\" -DPACKAGE_TARNAME=\"pktanon\" -DPACKAGE_VERSION=\"2.0-beta\" -DPACKAGE_STRING=\"pktanon\ 2.0-beta\" -DPACKAGE_BUGREPORT=\"bl...@kit.edu\" -DPACKAGE_URL=\"\" -DPACKAGE=\"pktanon\" -DVERSION=\"2.0-beta\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_STDDEF_H=1 -DHAVE_CXX11=1 -DHAVE_SOCKET=1 -DHAVE_SYS_SOCKET_H=1 -DHAVE_ARPA_INET_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_NETINET_IN_H=1 -DHAVE_LINUX_IF_ETHER_H=1 -DHAVE_NETPACKET_PACKET_H=1 -DHAVE_NET_IF_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_FCNTL_H=1 -DHAVE_PCAP_PCAP_H=1 -I. -O2 -pipe -Werror=return-type -I../include -g -DTRACE_ENABLED -DHAVE_LIBPCAP -I../libpktanon -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o LibpcapRecordsHandler.o LibpcapRecordsHandler.cpp make[2]: *** [Makefile:446: RawSocketRecordsHandler.o] Error 1 make[2]: *** Waiting for unfinished jobs make[2]: Leaving directory '/<>/src' make[1]: *** [Makefile:487: all-recursive] Error 1 make[1]: Leaving directory '/<>' dh_auto_build: make -j4 returned exit code 2 make: *** [debian/rules:18: build-arch] Error 255 - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-debug') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Hi, >> Currently the nettle 3.5.1 transition is going on. I tried to binNMU >> your package but it fails to build from source on all architectures. [...] > Utils.h includes inside the pktannon namespace. This causes the > sockaddr definition to be incorrectly placed in the pktannon namespace > which causes problems later. > > The fix is to move the include of outside the namespace. Thanks, that would have taken me quite some time to find on my own. > I have uploaded my fix to Raspbian, A debdiff should appear soon at > https://debdiffs.raspbian.org/main/p/pktanon , no intent to NMU in Debian. I have included your
Bug#943868: marked as done (rust-chrono: issues in d/copyright)
Your message dated Fri, 01 Nov 2019 09:49:32 + with message-id and subject line Bug#943868: fixed in rust-chrono 0.4.9-2 has caused the Debian Bug report #943868, regarding rust-chrono: issues in d/copyright 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.) -- 943868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943868 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-chrono Version: 0.4.7-1 Severity: serious Dear maintainer, There are some inaccuracies in d/copyright. I'm filing this bug at RC severity because the MIT license requires all copyright claims to be collated in d/copyright. (The package is dual-licensed under Apache-2.0, which the FTP team considers a license which does not require that all claims of copyright be collated in d/copyright, but it seems easier to just fix d/copyright rather than try to rely on the dual-licensing...) - `Files: *` stanza has incorrect copyright information. It should be "Kang Seonghoon and contributors" not just "Kang Seonghoon". - `Files: ./src/div.rc` stanza looks to be copyright both Kang Seonghoon and contributors, and also the Rust Project Developers. - Similarly `Files: ./src/format/parse.rs` is only /portions/ copyrighted by John Nagle, so Kang Seonghoon and contributors would appear to hold copyright too. -- Sean Whitton signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: rust-chrono Source-Version: 0.4.9-2 We believe that the bug you reported is fixed in the latest version of rust-chrono, 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. Wolfgang Silbermayr (supplier of updated rust-chrono package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 01 Nov 2019 10:32:20 +0100 Source: rust-chrono Architecture: source Version: 0.4.9-2 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Wolfgang Silbermayr Closes: 943868 Changes: rust-chrono (0.4.9-2) unstable; urgency=medium . * Package chrono 0.4.9 from crates.io using debcargo 2.4.0 . [kpcyrd] * Fix issues in debian/copyright (closes: #943868) Checksums-Sha1: 4ceb04160555ee3344799500e705ae2e0d5cd0da 3093 rust-chrono_0.4.9-2.dsc 071584659cef67d09718d52fe091a7099f1a5f8d 3368 rust-chrono_0.4.9-2.debian.tar.xz c0112a930c0335144cb9483d871cabd3de4afc34 7759 rust-chrono_0.4.9-2_source.buildinfo Checksums-Sha256: 4e86f4381e97dbc09f8fa5a1f851c892875a0d4b6b118481d5de00c0baf33857 3093 rust-chrono_0.4.9-2.dsc ea17dc9230ef6ece937bf6d5a010f5e691a8f65b73c2ae4ecf1e4d1d9d99e36d 3368 rust-chrono_0.4.9-2.debian.tar.xz d07979f6573bb3ce730b59a6bbf275c12a44f74f32d293bb19c1c093728c0e52 7759 rust-chrono_0.4.9-2_source.buildinfo Files: 4823922d015be8cf66aa3b61769795a0 3093 rust optional rust-chrono_0.4.9-2.dsc f599af85f3c6e6088da774ec6a60bae8 3368 rust optional rust-chrono_0.4.9-2.debian.tar.xz ef68a20234a599935c391bbeec9af205 7759 rust optional rust-chrono_0.4.9-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJLBAEBCgA1FiEEhWSUk7LYy5Yue0UiITeAY1BXOwQFAl27+8oXHHdvbGZnYW5n QHNpbGJlcm1heXIuYXQACgkQITeAY1BXOwSXShAAxd+VWJE0fqEhviwDMR3HmC40 uOv80PnZU7uXFGZvTG/Pwd3D8TJaALEM2KOn124KlsonPSTum7usDJWyGTrggrWX dhGN3hI1fcDv37R6aTqTkKslMzW2iasFAPZfvhnudAMurgs0hQEf0yUNALD+3PUu ZIAND/ZM1A5v+SSLoG0FLK8CmjACjoE1EzdAR9cKEkD+0QmsBwZF/Ba14SQVUpeL 3ZutCkjldRjtspftN/5IqPxnEULyR1ZjmAHJ1N0xI5FmVIzkAOijXK7lYKQHR33y k80osAAGmgnfhEWD6kLgzdH50YSxb8iDFUrpmt73LGw5bTMBIroU5XEc7UWCQBNY r/B7MiezX4z+EJP4cjUAGtZBuOgA6cGxYLbTiKychJiqG34SgLa/NAD6Y45Ze4aL dLTcywu+Y64l9y3fZVrEasIEsgfG7MOYHJIfQBhixUy950kD4UNjtl/rj4ABkVmi zdEvLSlvDtYbdr6u61+MkozsCENiAznr9Iq0QRVontwxz7pAmgMoooxCcvt+KspO iFDL2h8Sqn2G6I9Ymje9AuxfuCI0+2FIGg7EZNPTzpv0w/zTIML4WJuRPiiaLSw2 qyKAL1rQKjl+ZXagy61sB+g1rk70dbsgDBpmH8rVm9Np6yQSVui53LkURl2wPKpb oRy53NkTL6Pxc3i+7KI= =a7/v -END PGP SIGNATURE End Message ---
Processed: Re: Bug#943900: twolame breaks ffmpeg autopkgtest: twolame_init_params(): 384kbps is an invalid bitrate for mono encoding.
Processing control commands: > reassign -1 src:ffmpeg 7:4.1.4-1 Bug #943900 [src:twolame, src:ffmpeg] twolame breaks ffmpeg autopkgtest: twolame_init_params(): 384kbps is an invalid bitrate for mono encoding. Bug reassigned from package 'src:twolame, src:ffmpeg' to 'src:ffmpeg'. No longer marked as found in versions ffmpeg/7:4.2.1-1. Ignoring request to alter fixed versions of bug #943900 to the same values previously set Bug #943900 [src:ffmpeg] twolame breaks ffmpeg autopkgtest: twolame_init_params(): 384kbps is an invalid bitrate for mono encoding. Marked as found in versions ffmpeg/7:4.1.4-1. > tags -1 upstream Bug #943900 [src:ffmpeg] twolame breaks ffmpeg autopkgtest: twolame_init_params(): 384kbps is an invalid bitrate for mono encoding. Added tag(s) upstream. > forwarded -1 > https://ffmpeg.org/pipermail/ffmpeg-devel/2019-November/252392.html Bug #943900 [src:ffmpeg] twolame breaks ffmpeg autopkgtest: twolame_init_params(): 384kbps is an invalid bitrate for mono encoding. Set Bug forwarded-to-address to 'https://ffmpeg.org/pipermail/ffmpeg-devel/2019-November/252392.html'. -- 943900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943900 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#943900: twolame breaks ffmpeg autopkgtest: twolame_init_params(): 384kbps is an invalid bitrate for mono encoding.
Control: reassign -1 src:ffmpeg 7:4.1.4-1 Control: tags -1 upstream Control: forwarded -1 https://ffmpeg.org/pipermail/ffmpeg-devel/2019-November/252392.html Hi, On 31/10/2019 21:18, Sebastian Ramacher wrote: > On 2019-10-31 16:37:11, Paul Gevers wrote: >> Source: twolame, ffmpeg >> Control: found -1 twolame/0.4.0-2 >> Control: found -1 ffmpeg/7:4.2.1-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 twolame the autopkgtest of ffmpeg fails in >> testing when that autopkgtest is run with the binary packages of twolame >> from unstable. It passes when run with only packages from testing. In >> tabular form: >>passfail >> twolamefrom testing0.4.0-2 >> ffmpeg from testing7:4.2.1-1 >> all others from testingfrom testing >> >> I copied some of the output at the bottom of this report. >> >> Currently this regression is blocking the migration of twolame to >> testing [1]. Due to the nature of this issue, I filed this bug report >> against both packages. Can you please investigate the situation and >> reassign the bug to the right package? > > This is an issue in ffmpeg. The change in twolame is deliberate: > https://github.com/njh/twolame/pull/32. The defaults in ffmpeg produce > invalid files. I submitted the above patch. I'll give it a few days to see what upstream says about it before I upload it. James signature.asc Description: OpenPGP digital signature
Bug#943401: marked as done (libreoffice C++ Unit tests failing when built with gcc >= 9.2.1-12 (Failure instantiating exceptionprotector))
Your message dated Fri, 1 Nov 2019 11:50:33 +0300 with message-id <20191101085033.ga19...@mitya57.me> and subject line Re: Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector) has caused the Debian Bug report #943401, regarding libreoffice C++ Unit tests failing when built with gcc >= 9.2.1-12 (Failure instantiating exceptionprotector) 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.) -- 943401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libreoffice Version: 1:6.3.3~rc1-1 Severity: important Control: block 941093 by -1 Dear Maintainer, As can be seen on [1], the autopkgtests started failing this Monday and succeeded only once since then. This blocks the Qt transition [2]. From one of the logs [3], it can be seen that one of the tests (test_format_paragraph_transparency) is failing. However, in the latest log the failure reason is different. [1]: https://ci.debian.net/packages/libr/libreoffice/unstable/amd64/ [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941093 [3]: https://ci.debian.net/data/autopkgtest/testing/amd64/libr/libreoffice/3243766/log.gz -- Dmitry Shachnev signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Version: 9.2.1-16 On Thu, Oct 31, 2019 at 10:32:05PM +0100, Rene Engelhard wrote: > > The fix is now in -16. > > Good. Can confirm. You can close the bug. Doing that now to let gcc-9 migrate (when it is built on mips*). Thanks everyone for your work! -- Dmitry Shachnev signature.asc Description: PGP signature --- End Message ---
Bug#943938: tpm2-tss FTBFS: Makefile:15030: *** missing separator. Stop.
Source: tpm2-tss Version: 2.1.0-4 Severity: serious Tags: ftbfs tpm2-tss fails to build from source: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/tpm2-tss_2.1.0-4.rbuild.log.gz | dh_auto_build | make -j15 | make[2]: Entering directory '/build/1st/tpm2-tss-2.1.0' | Makefile:15030: *** missing separator. Stop. | make[2]: Leaving directory '/build/1st/tpm2-tss-2.1.0' | dh_auto_build: make -j15 returned exit code 2 | make[1]: *** [debian/rules:22: override_dh_auto_build] Error 255 | make[1]: Leaving directory '/build/1st/tpm2-tss-2.1.0' | make: *** [debian/rules:7: build] Error 2 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 This is also reproduced by crossqa: http://crossqa.debian.net/build/tpm2-tss_2.1.0-4_ppc64el_20190906172018.log Line 15030 of the Makefile contains "@CODE_COVERAGE_RULES@". Very likely, this line should have been substituted from Makefile.in, but the generate configure does not contain any substitutions for it. Hope this helps with diagnosing the issue Helmut
