Bug#945047: marked as done (Needs dependency for Crypt/Digest/SHA256.pm)
Your message dated Tue, 19 Nov 2019 07:49:54 + with message-id and subject line Bug#945047: fixed in extrepo 0.3 has caused the Debian Bug report #945047, regarding Needs dependency for Crypt/Digest/SHA256.pm 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.) -- 945047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: extrepo Version: 0.2 Severity: serious Attempting to run extrepo produces: Can't locate Crypt/Digest/SHA256.pm in @INC (you may need to install the Crypt::Digest::SHA256 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/Debian/ExtRepo/Commands/Enable.pm line 9. BEGIN failed--compilation aborted at /usr/share/perl5/Debian/ExtRepo/Commands/Enable.pm line 9. Compilation failed in require at /usr/share/perl5/Debian/ExtRepo/Commands/Update.pm line 3. BEGIN failed--compilation aborted at /usr/share/perl5/Debian/ExtRepo/Commands/Update.pm line 3. Compilation failed in require at /usr/bin/extrepo line 7. BEGIN failed--compilation aborted at /usr/bin/extrepo line 7. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages extrepo depends on: ii gpgv 2.2.17-3 ii libwww-perl 6.41-1 ii libyaml-perl 1.29-1 ii perl 5.30.0-9 extrepo recommends no packages. extrepo suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: extrepo Source-Version: 0.3 We believe that the bug you reported is fixed in the latest version of extrepo, 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 945...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Wouter Verhelst (supplier of updated extrepo 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, 19 Nov 2019 09:31:46 +0200 Source: extrepo Architecture: source Version: 0.3 Distribution: unstable Urgency: medium Maintainer: Wouter Verhelst Changed-By: Wouter Verhelst Closes: 945047 945053 945054 Changes: extrepo (0.3) unstable; urgency=medium . * Add man page for extrepo * Fix bug in extrepo search introduced after change of metadata format. * Lintian fixes to package description and debian/copyright * debian/source/format: Mark as 3.0 (native) package * debian/control: add dependency on libcryptx-perl. Closes: #945047. * Sync config directory in binary with installed directory from packaging. Closes: #945053. * Rework comments in config.yaml slightly. Closes: #945054 * Ship config for bullseye, not buster. Checksums-Sha1: 751506680b4092010e0ed5ab7a0a0e11e1a8c2b6 1513 extrepo_0.3.dsc 26c5b053b6772c5e82d190e0bcf25648545cc9ef 19436 extrepo_0.3.tar.xz 7fc2f3a9595d3c7f9c166429e1ef511475f9842d 10783 extrepo_0.3_source.buildinfo Checksums-Sha256: 6b2a42c361bf3ccfdc3d7ec9a3c0a2beba9be7521bead0a2b508b1d149001f27 1513 extrepo_0.3.dsc a0b3e4adeff1f1072179a45229cd4eb2b4fe12ab24f56e1d488a468ea123c04d 19436 extrepo_0.3.tar.xz d5eb96a30295b5852ce8773c5a6682335586f492afbbec565c86d0accbc989bf 10783 extrepo_0.3_source.buildinfo Files: 63b4314a5e4cc4fbc3271e7b0d59a88b 1513 admin optional extrepo_0.3.dsc addfe2703ec4bf488b79b8ab58163bd1 19436 admin optional extrepo_0.3.tar.xz ecc7723a638d807451afd5a8e0bab47e 10783 admin optional extrepo_0.3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEm2n98/DaCUgGYSn3LfxRmVQYEpYFAl3TmvIACgkQLfxRmVQY Epbb2Q//YbZtorkpW6uMWOFMx6QN+Gz55+g7hDVm7kOVm+1lDuqrwHs9crOr/DFf BzJxmTanhwNxWY2EQeVGJa1JVs3io2aw1lG4UG5k1WoVucosCK0h35oXtSccCAZf
Bug#945053: marked as done (extrepo: Binary references /etc/extrepos but package installs to /etc/extrepo)
Your message dated Tue, 19 Nov 2019 07:49:54 + with message-id and subject line Bug#945053: fixed in extrepo 0.3 has caused the Debian Bug report #945053, regarding extrepo: Binary references /etc/extrepos but package installs to /etc/extrepo 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.) -- 945053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: extrepo Version: 0.2 Severity: important Tags: upstream Dear Maintainer, Running "extrepo update" fails with a message about a missing /etc/extrepos/config.yaml. The package installs this file to /etc/extrepo/config.yaml (note the missing 's'). Unless the user is supposed to copy/move this directory over, this seems a bug. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (300, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.3.11nlb (SMP w/20 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.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages extrepo depends on: ii gpgv 2.2.17-3 ii libwww-perl 6.41-1 ii libyaml-perl 1.29-1 ii perl 5.30.0-9 extrepo recommends no packages. extrepo suggests no packages. -- Configuration Files: /etc/extrepo/config.yaml changed: --- url: http://extrepo-team.pages.debian.net/extrepo-data dist: debian version: buster enabled_policies: - main contrib non-free -- no debconf information --- End Message --- --- Begin Message --- Source: extrepo Source-Version: 0.3 We believe that the bug you reported is fixed in the latest version of extrepo, 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 945...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Wouter Verhelst (supplier of updated extrepo 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, 19 Nov 2019 09:31:46 +0200 Source: extrepo Architecture: source Version: 0.3 Distribution: unstable Urgency: medium Maintainer: Wouter Verhelst Changed-By: Wouter Verhelst Closes: 945047 945053 945054 Changes: extrepo (0.3) unstable; urgency=medium . * Add man page for extrepo * Fix bug in extrepo search introduced after change of metadata format. * Lintian fixes to package description and debian/copyright * debian/source/format: Mark as 3.0 (native) package * debian/control: add dependency on libcryptx-perl. Closes: #945047. * Sync config directory in binary with installed directory from packaging. Closes: #945053. * Rework comments in config.yaml slightly. Closes: #945054 * Ship config for bullseye, not buster. Checksums-Sha1: 751506680b4092010e0ed5ab7a0a0e11e1a8c2b6 1513 extrepo_0.3.dsc 26c5b053b6772c5e82d190e0bcf25648545cc9ef 19436 extrepo_0.3.tar.xz 7fc2f3a9595d3c7f9c166429e1ef511475f9842d 10783 extrepo_0.3_source.buildinfo Checksums-Sha256: 6b2a42c361bf3ccfdc3d7ec9a3c0a2beba9be7521bead0a2b508b1d149001f27 1513 extrepo_0.3.dsc a0b3e4adeff1f1072179a45229cd4eb2b4fe12ab24f56e1d488a468ea123c04d 19436 extrepo_0.3.tar.xz d5eb96a30295b5852ce8773c5a6682335586f492afbbec565c86d0accbc989bf 10783 extrepo_0.3_source.buildinfo Files: 63b4314a5e4cc4fbc3271e7b0d59a88b 1513 admin optional extrepo_0.3.dsc addfe2703ec4bf488b79b8ab58163bd1 19436 admin optional extrepo_0.3.tar.xz ecc7723a638d807451afd5a8e0bab47e 10783 admin optional extrepo_0.3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEm2n98/DaCUgGYSn3LfxRmVQYEpYFAl3TmvIACgkQLfxRmVQY Epbb2Q//YbZtorkpW6uMWOFMx6QN+Gz55+g7hDVm7kOVm+1lDuqrwHs9crOr/DFf BzJxmTanhwNxWY2EQeVGJa1JVs3io2aw1lG4UG5k1WoVucosCK0h35oXtSccCAZf qYPCEY7YLYpsMSBeO40NXlfh6SNmpiOVcM7cH/wASdnr4yot1paVJyzwBGc8FbGO Z9iU8PuuMoutt1oTthlh+As9W5LjZtfnbkjB63VO8PixixPxOpMVZDGK7WVl2jFf SVeaQe6Z/bmScg2qBJehCDwlS9QRbFemxPq7W3aWe+ElzsWppcUek3sbui5xEGHR vw7o9ZGCMiqQCDO4QnjAFGQ8Dvy7pVcbiaw8ACRub/UlNDLIPPg+GqhpgqJwWCBh
Bug#945061: uninstallable due to Thunderbird security update to version 68
Package: xul-ext-sogo-connector Severity: grave Hi, due to the security update introducing Thunderbird 68, xul-ext-sogo-connector has become uninstallable and thus unusable in all suites from oldstable to unstable. Could you please package sogo-connector 68? (old-)stable updates would also be greatly appreciated. I'd be happy to help test updated packages. Best wishes Philipp
Processed: severity of 945053 is serious
Processing commands for cont...@bugs.debian.org: > severity 945053 serious Bug #945053 [extrepo] extrepo: Binary references /etc/extrepos but package installs to /etc/extrepo Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 945053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: re: ipywidgets: Python2 removal in sid/bullseye
Processing commands for cont...@bugs.debian.org: > unblock 936745 by 936995 Bug #936745 [src:ipywidgets] ipywidgets: Python2 removal in sid/bullseye 936745 was blocked by: 936995 936775 936745 was blocking: 936742 936743 936775 937119 937156 937558 937665 937695 937926 938168 938528 938545 938716 Removed blocking bug(s) of 936745: 936995 > severity 936745 serious Bug #936745 [src:ipywidgets] ipywidgets: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 936745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936745 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#945047 marked as pending in extrepo
Processing control commands: > tag -1 pending Bug #945047 [extrepo] Needs dependency for Crypt/Digest/SHA256.pm Added tag(s) pending. -- 945047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945047: marked as pending in extrepo
Control: tag -1 pending Hello, Bug #945047 in extrepo 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/extrepo-team/extrepo/commit/186af85fbe96e9142554f07693cc5581c1b4eea4 debian/control: add dependency on libcryptx-perl. Closes: #945047. (this message was generated automatically) -- Greetings https://bugs.debian.org/945047
Bug#942708: marked as pending in python-nacl
Control: tag -1 pending Hello, Bug #942708 in python-nacl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/python-nacl/commit/be73985c7a9314dcc4c7e0e907e066a1d0dc1052 Fix build with new hypothesis version (add d/p/480.patch from upstream) (Closes: #942708) - Thanks to Matthias Klose for providing the patch (this message was generated automatically) -- Greetings https://bugs.debian.org/942708
Processed: Bug#942708 marked as pending in python-nacl
Processing control commands: > tag -1 pending Bug #942708 [src:python-nacl] update pynacl for recent hypothesis version Added tag(s) pending. -- 942708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942708 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945047: Needs dependency for Crypt/Digest/SHA256.pm
Package: extrepo Version: 0.2 Followup-For: Bug #945047 Just confirming that libcryptx-perl does indeed fix the issue. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (300, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.3.11nlb (SMP w/20 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.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages extrepo depends on: ii gpgv 2.2.17-3 ii libwww-perl 6.41-1 ii libyaml-perl 1.29-1 ii perl 5.30.0-9 extrepo recommends no packages. extrepo suggests no packages. -- Configuration Files: /etc/extrepo/config.yaml changed [not included] -- no debconf information
Processed: reassign 945046 to src:linux, severity of 945046 is important
Processing commands for cont...@bugs.debian.org: > reassign 945046 src:linux 5.2.17-1 Bug #945046 [linux-image-5.2.0-0.bpo.3-amd64] linux-image-5.2.0-0.bpo.3-amd64: Kernel crashes / system reboots constantly Bug reassigned from package 'linux-image-5.2.0-0.bpo.3-amd64' to 'src:linux'. Ignoring request to alter found versions of bug #945046 to the same values previously set Ignoring request to alter fixed versions of bug #945046 to the same values previously set Bug #945046 [src:linux] linux-image-5.2.0-0.bpo.3-amd64: Kernel crashes / system reboots constantly Marked as found in versions linux/5.2.17-1. > severity 945046 important Bug #945046 [src:linux] linux-image-5.2.0-0.bpo.3-amd64: Kernel crashes / system reboots constantly Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 945046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945046 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#941685: libspring-java: FTBFS package org.hibernate.validator.method does not exist
Control: tag -1 ftbfs upstream fixed-upstream patch
The cleanest way to fix this would be upgrading Spring to 5.0 or later,
which drops the build-dependency on hibernate-validator 4.x and strictly
requires validation-api 1.1 and hibernate-validator 5.x.
In case that's not possible in the near term, I attach here a patch
consisting of changes backported from upstream to remove the code
depending on hibernate-validator 4.x.
I did successfully run the unit tests of o.s.validation.beanvalidation.*
with my patch applied, but it needed so much hacking that I don't
entirely trust the result. I have not yet tested an actual application
using the bean validation feature from the installed package, and I
won't open an MR until I've done that.
>From db567eaf8d24df19d5667b0477db42ad46246c86 Mon Sep 17 00:00:00 2001
From: Ryan Tandy
Date: Mon, 18 Nov 2019 21:50:19 +
Subject: [PATCH] Fix FTBFS with Hibernate Validator 5.x
---
debian/changelog | 7 +
debian/control| 4 +-
debian/maven.rules| 2 +-
.../0054-disable-hibernate-validator-4.patch | 315 ++
debian/patches/series | 1 +
5 files changed, 326 insertions(+), 3 deletions(-)
create mode 100644 debian/patches/0054-disable-hibernate-validator-4.patch
diff --git a/debian/changelog b/debian/changelog
index addf891d..a58e294d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+libspring-java (4.3.22-4.1) UNRELEASED; urgency=medium
+
+ * Fix FTBFS with libhibernate-validator-java 5.x: Upgrade to Bean Validation
+1.1 and remove Hibernate Validator 4.x support. (Closes: #941685)
+
+ -- Ryan Tandy Mon, 18 Nov 2019 19:48:22 +
+
libspring-java (4.3.22-4) unstable; urgency=medium
* Team upload.
diff --git a/debian/control b/debian/control
index b7d5a178..ba1cdd91 100644
--- a/debian/control
+++ b/debian/control
@@ -43,7 +43,7 @@ Build-Depends-Indep: bsh,
libgeronimo-jcache-1.0-spec-java,
libgeronimo-jms-1.1-spec-java,
libgeronimo-jta-1.2-spec-java,
- libgeronimo-validation-1.0-spec-java,
+ libgeronimo-validation-1.1-spec-java,
libhessian-java,
libhibernate-validator-java (>= 4.3.2),
libhibernate3-java (>= 3.5),
@@ -156,7 +156,7 @@ Recommends: libasm-java (>= 5.0),
libcglib-java (>= 3.1),
libgeronimo-ejb-3.2-spec-java,
libgeronimo-jms-1.1-spec-java,
-libgeronimo-validation-1.0-spec-java,
+libgeronimo-validation-1.1-spec-java,
libjodatime-java,
libspring-instrument-java (= ${source:Version}),
libtomcat9-java
diff --git a/debian/maven.rules b/debian/maven.rules
index c5658212..00a46097 100644
--- a/debian/maven.rules
+++ b/debian/maven.rules
@@ -10,7 +10,7 @@ javax.portlet portlet-api * * * *
s/javax.resource/org.apache.geronimo.specs/ s/connector-api/geronimo-j2ee-connector_1.5_spec/ * s/.*/debian/ * *
s/javax.servlet.jsp.jstl/org.apache.taglibs/ s/javax.servlet.jsp.jstl-api/taglibs-standard-spec/ * s/.*/debian/ * *
s/javax.transaction/org.apache.geronimo.specs/ s/javax.transaction-api/geronimo-jta_1.2_spec/ * s/.*/debian/ * *
-s/javax.validation/org.apache.geronimo.specs/ s/validation-api/geronimo-validation_1.0_spec/ * s/.*/debian/ * *
+s/javax.validation/org.apache.geronimo.specs/ s/validation-api/geronimo-validation_1.1_spec/ * s/.*/debian/ * *
junit junit * s/.*/4.x/ * *
log4j log4j * s/.*/1.2.x/ * *
org.apache.tomcat s/catalina/tomcat-catalina/ * s/.*/9.x/ * *
diff --git a/debian/patches/0054-disable-hibernate-validator-4.patch b/debian/patches/0054-disable-hibernate-validator-4.patch
new file mode 100644
index ..59927894
--- /dev/null
+++ b/debian/patches/0054-disable-hibernate-validator-4.patch
@@ -0,0 +1,315 @@
+Description: Fix compilation failure with Hibernate Validator 5.x
+ Backport parts of upstream commit 54004e0d78dd92c6242b77befbc9d9fcdb68
+ to remove Hibernate Validator 4.x dependency and use Bean Validation 1.1
+ directly.
+Author: Ryan Tandy
+Forwarded: not-needed
+Bug-Debian: https://bugs.debian.org/941685
+--- a/spring-context/src/main/java/org/springframework/validation/beanvalidation/LocalValidatorFactoryBean.java
b/spring-context/src/main/java/org/springframework/validation/beanvalidation/LocalValidatorFactoryBean.java
+@@ -24,11 +24,13 @@
+ import java.lang.reflect.Proxy;
+ import java.util.Arrays;
+ import java.util.HashMap;
++import java.util.List;
+ import java.util.Map;
+ import java.util.Properties;
+ import javax.validation.Configuration;
+ import javax.validation.ConstraintValidatorFactory;
+ import javax.validation.MessageInterpolator;
++import javax.validation.ParameterNameProvider;
+ import javax.validation.TraversableResolver;
+ import
Processed: Re: libspring-java: FTBFS package org.hibernate.validator.method does not exist
Processing control commands: > tag -1 ftbfs upstream fixed-upstream patch Bug #941685 [src:libspring-java] libspring-java: FTBFS package org.hibernate.validator.method does not exist Added tag(s) fixed-upstream, upstream, patch, and ftbfs. -- 941685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941685 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: gpgme1.0: please update test for python->python2 move
Processing control commands: > severity -1 serious Bug #943390 [src:gpgme1.0] gpgme1.0: please update test for python->python2 move Severity set to 'serious' from 'normal' -- 943390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943390 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#944949: marked as done (dbus-python: needs an explicit build dependency on dh-python)
Your message dated Tue, 19 Nov 2019 02:40:52 +0100 with message-id <1a0d2e3e-32f7-989b-f129-83ff806b6...@debian.org> and subject line Re: Bug#944949: dbus-python: needs an explicit build dependency on dh-python has caused the Debian Bug report #944949, regarding dbus-python: needs an explicit build dependency on dh-python 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.) -- 944949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944949 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:dbus-python Version: 1.2.12-1 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python. --- End Message --- --- Begin Message --- On 17.11.19 20:53, Simon McVittie wrote: > Control: tags 944949 + moreinfo > > On Sun, 17 Nov 2019 at 19:07:39 +, Matthias Klose wrote: >> Please add an explicit build dependency on dh-python. > > As far as I can see it's been explicit since 2015. Is anything more > needed here? > > Note that the FTBFS with > > dh_python2 > make[1]: dh_python2: Command not found > > seems to be because /usr/bin/dh_python2 is a #!/usr/bin/python script in > a package that doesn't depend on python (#944894). The misleading > "Command not found" is similar to this: > > $ cat > Makefile > all: > ./script > $ cat > script > #!/usr/bin/does-not-exist > $ chmod +x script > $ make > ./script > make: ./script: Command not found > make: *** [Makefile:2: all] Error 127 > > I have a workaround which I believe should still be harmless after > dh_python2 moves out of python2 (presumably into dh-python?), which I'll > upload soon. > > If that doesn't work, I'll temporarily re-add the python B-D so the > python3.8 transition can go through, and remove it after #944894 is > resolved. > > It's unfortunate that the python3.8 transition, the effort to replace > references to python2 with python, and the migration of dh_python2 from > python2 to dh-python (?) are happening at the same time and affect > overlapping sets of packages. Perhaps one (or more) of these could be > deferred until one of the others has been done? now closing. The dh_python2 now uses python2 as the shebang, until it gets removed from python-defaults.--- End Message ---
Bug#944949: dbus-python: needs an explicit build dependency on dh-python
On 17.11.19 20:53, Simon McVittie wrote: > Control: tags 944949 + moreinfo > > On Sun, 17 Nov 2019 at 19:07:39 +, Matthias Klose wrote: >> Please add an explicit build dependency on dh-python. > > As far as I can see it's been explicit since 2015. Is anything more > needed here? > > Note that the FTBFS with > > dh_python2 > make[1]: dh_python2: Command not found > > seems to be because /usr/bin/dh_python2 is a #!/usr/bin/python script in > a package that doesn't depend on python (#944894). The misleading > "Command not found" is similar to this: > > $ cat > Makefile > all: > ./script > $ cat > script > #!/usr/bin/does-not-exist > $ chmod +x script > $ make > ./script > make: ./script: Command not found > make: *** [Makefile:2: all] Error 127 > > I have a workaround which I believe should still be harmless after > dh_python2 moves out of python2 (presumably into dh-python?), which I'll > upload soon. > > If that doesn't work, I'll temporarily re-add the python B-D so the > python3.8 transition can go through, and remove it after #944894 is > resolved. > > It's unfortunate that the python3.8 transition, the effort to replace > references to python2 with python, and the migration of dh_python2 from > python2 to dh-python (?) are happening at the same time and affect > overlapping sets of packages. Perhaps one (or more) of these could be > deferred until one of the others has been done? now closing. The dh_python2 now uses python2 as the shebang, until it gets removed from python-defaults.
Processed: Re: libxml2: please update tests for python->python2 move
Processing control commands: > severity -1 serious Bug #943386 [src:libxml2] libxml2: please update tests for python->python2 move Severity set to 'serious' from 'normal' -- 943386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943386 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#944675: udev: Keyboard and mouse not working in X.org with udev 243-5
Am 19.11.19 um 00:56 schrieb Klaumi Klingsporn: > That leaves me with the question: Why the hell on my > amd64-system (with i386 enabled only as > foreign-architecture) the i386 version of libinput-bin was > installed? I'm puzzled as well how so many users ended up with a non-native libinput-bin:i386. This is not good. Imho apt should be much more careful when installing non-native packages and prefer the native version. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#944935: deltarpm: diff for NMU version 3.6+dfsg-1.1
On Mon, Nov 18, 2019 at 20:06:44 -0500, Boyuan Yang wrote: > I've prepared an NMU for deltarpm (versioned as 3.6+dfsg-1.1) and > uploaded it to DELAYED/1. Please feel free to tell me if I > should delay it longer. No, please continue, thank you for taking care of it. Also feel free to push a branch to salsa if you have permission. -- mike signature.asc Description: PGP signature
Processed: deltarpm: diff for NMU version 3.6+dfsg-1.1
Processing control commands: > tags 944935 + patch Bug #944935 [src:deltarpm] deltarpm: needs an explicit build dependency on dh-python Added tag(s) patch. > tags 944935 + pending Bug #944935 [src:deltarpm] deltarpm: needs an explicit build dependency on dh-python Added tag(s) pending. -- 944935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#944935: deltarpm: diff for NMU version 3.6+dfsg-1.1
Control: tags 944935 + patch Control: tags 944935 + pending Dear maintainer, I've prepared an NMU for deltarpm (versioned as 3.6+dfsg-1.1) and uploaded it to DELAYED/1. Please feel free to tell me if I should delay it longer. Regards, Boyuan Yang diff -Nru deltarpm-3.6+dfsg/debian/changelog deltarpm- 3.6+dfsg/debian/changelog --- deltarpm-3.6+dfsg/debian/changelog 2013-08-04 00:04:21.0 -0400 +++ deltarpm-3.6+dfsg/debian/changelog 2019-11-18 19:59:25.0 -0500 @@ -1,3 +1,19 @@ +deltarpm (3.6+dfsg-1.1) unstable; urgency=high + + * Non-maintainer upload. + + [ Boyuan Yang ] + * debian/control: Add explicit build-dependency on dh-python. +(Closes: #944935) + + [ Mike Miller ] + * Add DEP-3 headers and refresh all patches. + * Set maintainer to RPM packaging team, add myself as uploader. + * Update debian/copyright for 2019. + * d/control: Update Vcs-* to salsa.debian.org. + + -- Boyuan Yang Mon, 18 Nov 2019 19:59:25 -0500 + deltarpm (3.6+dfsg-1) unstable; urgency=low * New upstream version. diff -Nru deltarpm-3.6+dfsg/debian/control deltarpm- 3.6+dfsg/debian/control --- deltarpm-3.6+dfsg/debian/control2013-07-17 21:30:13.0 -0400 +++ deltarpm-3.6+dfsg/debian/control2019-11-18 19:59:17.0 -0500 @@ -1,20 +1,22 @@ Source: deltarpm Section: admin Priority: extra -Maintainer: Mike Miller +Maintainer: RPM packaging team +Uploaders: Mike Miller Build-Depends: debhelper (>= 9), + dh-python, libbz2-dev, liblzma-dev, pkg-config, python-all-dev (>= 2.6.6-3~), python3-all-dev (>= 3.2), - zlib1g-dev + zlib1g-dev, Standards-Version: 3.9.4 X-Python-Version: >= 2.4 X-Python3-Version: >= 3.2 Homepage: http://gitorious.org/deltarpm/deltarpm -Vcs-Browser: http://anonscm.debian.org/gitweb/?p=users/mtmiller-guest/deltarpm.git -Vcs-Git: git://anonscm.debian.org/users/mtmiller-guest/deltarpm.git +Vcs-Browser: https://salsa.debian.org/pkg-rpm-team/deltarpm +Vcs-Git: https://salsa.debian.org/pkg-rpm-team/deltarpm.git Package: deltarpm Architecture: any diff -Nru deltarpm-3.6+dfsg/debian/copyright deltarpm- 3.6+dfsg/debian/copyright --- deltarpm-3.6+dfsg/debian/copyright 2013-07-17 21:30:13.0 -0400 +++ deltarpm-3.6+dfsg/debian/copyright 2019-11-18 19:58:24.0 -0500 @@ -36,12 +36,12 @@ Changes by Jonathan Dieter are also in the public domain Files: debian/* -Copyright: 2013 Mike Miller +Copyright: 2013-2019 Mike Miller License: BSD-3-clause License: BSD-2-clause Redistribution and use in source and binary forms, with or without - modification, are permitted providing that the following conditions + modification, are permitted providing that the following conditions are met: . 1. Redistributions of source code must retain the above copyright diff -Nru deltarpm-3.6+dfsg/debian/patches/04_omit-rpmdumpheader.patch deltarpm-3.6+dfsg/debian/patches/04_omit-rpmdumpheader.patch --- deltarpm-3.6+dfsg/debian/patches/04_omit-rpmdumpheader.patch 2013-07-17 21:30:13.0 -0400 +++ deltarpm-3.6+dfsg/debian/patches/04_omit-rpmdumpheader.patch 2019-11-18 19:58:24.0 -0500 @@ -1,13 +1,15 @@ -Author: Mike Miller Description: Omit building and installing the rpmdumpheader helper utility This patch removes rpmdumpheader from the 'all' and 'install' targets. The only purpose of this utility is to query the system RPM database for an installed package, so it will always fail on a Debian system. +Author: Mike Miller Forwarded: not-needed - +Last-Update: 2019-03-08 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ --- a/Makefile +++ b/Makefile -@@ -14,7 +14,7 @@ LDLIBS = -lbz2 $(zlibldflags) -llzma +@@ -14,7 +14,7 @@ LDFLAGS = PYTHONS = python python3 @@ -16,7 +18,7 @@ python: _deltarpmmodule.so -@@ -59,7 +59,6 @@ install: +@@ -59,7 +59,6 @@ install -m 755 makedeltarpm $(DESTDIR)$(bindir) install -m 755 applydeltarpm $(DESTDIR)$(bindir) install -m 755 combinedeltarpm $(DESTDIR)$(bindir) signature.asc Description: This is a digitally signed message part
Bug#942794: marked as done (scipy ftbfs trying to build the docs with python3.8)
Your message dated Tue, 19 Nov 2019 00:49:46 + with message-id and subject line Bug#942794: fixed in python-scipy 1.2.2-8 has caused the Debian Bug report #942794, regarding scipy ftbfs trying to build the docs with python3.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 942794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-scipy Version: 1.2.2-4 Severity: important Tags: sid bullseye patch User: debian-pyt...@lists.debian.org Usertags: python3.8 with both 3.7 and 3.8 as supported py3 versions, the docs ftbfs, apparently scipy isn't yet ready for 3.8? Otoh it builds itself, just not the docs. So this is a work around to build the docs with 3.7, not 3.8. IMO you shouldn't add both builddirs to the path when building the documentation. http://launchpadlibrarian.net/447851510/python-scipy_1.2.2-4build1_1.2.2-4ubuntu1.diff.gz --- End Message --- --- Begin Message --- Source: python-scipy Source-Version: 1.2.2-8 We believe that the bug you reported is fixed in the latest version of python-scipy, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated python-scipy 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, 19 Nov 2019 02:32:19 +0800 Source: python-scipy Architecture: source Version: 1.2.2-8 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Drew Parsons Closes: 942794 Changes: python-scipy (1.2.2-8) unstable; urgency=medium . * Team upload. . [ Ondřej Nový ] * Bump Standards-Version to 4.4.1. . [ Drew Parsons ] * only build docs for default python3. Closes: #942794. - apply dh_auto_install to arch-dependent packages only Checksums-Sha1: 2bfd257a75844d2d84fd4a9907e6d4132797d031 3242 python-scipy_1.2.2-8.dsc 0c13004ab769b4b8b7a49074888620d397398356 33040 python-scipy_1.2.2-8.debian.tar.xz 572a0f50518eff62c079fb76c8fc2ccf3c60c72d 10085 python-scipy_1.2.2-8_source.buildinfo Checksums-Sha256: 7c830f8d4e7ecb69185c4f6685f67edbd8fc43edae4c271025491db22b284a32 3242 python-scipy_1.2.2-8.dsc 35035cb14872be8bbd5dab6ab8b2da10086d66929c2cdb0b51f0d1bc46b83b22 33040 python-scipy_1.2.2-8.debian.tar.xz a2041f8c965c971f0e8ed528aa5ecedbce818b1326998eda60c3340c3b2bd331 10085 python-scipy_1.2.2-8_source.buildinfo Files: 1c398a4243fc3404a4993378b95a1988 3242 python optional python-scipy_1.2.2-8.dsc d6451d7fcf7c97ad03e6c03f11dcff3b 33040 python optional python-scipy_1.2.2-8.debian.tar.xz d18f0e294626dfd15523d46a8c409b94 10085 python optional python-scipy_1.2.2-8_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAl3TNkQUHGRwYXJzb25z QGRlYmlhbi5vcmcACgkQVz7x5L1aAfoScg//f3ipTh64Byb9nJUxTxYZvwNzLWCs 2t7vp9De2zKQRWJcbaqR14/5PsMac9Wan3d/KhUTYWlNS5nSilOtyIwM2nlIcQ7a OCtHGXsbAUOFUGLTEaxHnb8CM/LGn+P3S8jEQloWTfKz+ewrxDE8gnP2snV7xVX9 QUjY5NtOVM+Q7OX+8wWHpJzBqIclUMa3EYib0+L6wClTu42JLqzSDnjhq7CZfRzf 8OanrkQlLgygT7UY4XziQvE10ugexH0IpkCMhQ8v3z1N9f+mPusth8hK9LSJH7Nr QnyutOvm/BKJZDM8p7zefUxYxsW1tsktG2Kl2BAgNsbxSRuuVO1dfDqzRjDojVIr BRW8zdqbMpfO/XiUhn9zthOB9tQ68eqNBFeA7q7sj65XIgmEXUUgUMjI0J2Y2kkJ U/Nxg5QO6U4/lGf0uY7cZX7RlXXL6s5V308RMrf9Qf18PoPNM+CNY3MPaqHQt7oC PXq43h8asXfCWAK9V2lBz8/0X20SagUqTQgyumACOcz9MfUwTHjmsOmVG76RPNFQ Wtw+c2lzk+H+TzzWJWXG8wkUMkdyIh2ZkklNX5EkHM+5UnH7vT06z+bD/5rCg59z sBR3FNDXfdyAH/0nQbiqr/3c8WdziEAnz58eBWjxA3Si2TwAJnuOd84oVco653zq XaWjrI4XnnXSIqY= =TliB -END PGP SIGNATURE End Message ---
Bug#942794: marked as pending in python-scipy
Control: tag -1 pending Hello, Bug #942794 in python-scipy reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/python-scipy/commit/e72f93236ce82639b3a11468dd078093170f0330 only build docs for default python3 not for all supported python3 versions. Closes: #942794. (this message was generated automatically) -- Greetings https://bugs.debian.org/942794
Processed: Bug#942794 marked as pending in python-scipy
Processing control commands: > tag -1 pending Bug #942794 [src:python-scipy] scipy ftbfs trying to build the docs with python3.8 Ignoring request to alter tags of bug #942794 to the same tags previously set -- 942794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#942794 marked as pending in python-scipy
Processing control commands: > tag -1 pending Bug #942794 [src:python-scipy] scipy ftbfs trying to build the docs with python3.8 Added tag(s) pending. -- 942794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942794: marked as pending in python-scipy
Control: tag -1 pending Hello, Bug #942794 in python-scipy reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/python-scipy/commit/e72f93236ce82639b3a11468dd078093170f0330 only build docs for default python3 not for all supported python3 versions. Closes: #942794. (this message was generated automatically) -- Greetings https://bugs.debian.org/942794
Bug#944675: udev: Keyboard and mouse not working in X.org with udev 243-5
Am / On Mon, 18 Nov 2019 11:37:32 +0100
schrieb / wrote Michael Biebl :
> Can you all check if you have the i386 version of
> libinput-bin installed (by accident) on your amd64
> system?
> .. and if installing the amd64 version via
> apt install libinput-bin:amd64
> helps
Dear Michael,
thanks, this did the trick for me too!
There was libinput-bin:i386 and only the
i386-version of it installed. Installing the amd64-version
removed the i386-version together with libevdev2:i386{u}
libgudev-1.0-0:i386{u} libwacom2:i386{u} which were
all already installed as amd64-versions as well.
After installing udev and systemd 243-7 which is now in
testing - voila, all works fine again.
That leaves me with the question: Why the hell on my
amd64-system (with i386 enabled only as
foreign-architecture) the i386 version of libinput-bin was
installed?
Must have been installed as dependeny. And my only idea is
this:
udev depends on libudev1, which has set "Multi-Arch: same".
wine32 (which is recommended by wine64) also depends on
libudev1 but of course on the i386-version of the library
(Multi.Arch: same). So maybe installing wine on an
amd64-system installs wine32 which installs libudev1:i386
which (because of "Multi-Arch: same") installs the
i386-version of libinput-bin which itself has set
"Multi-Arch: foreign"?
But maybe I'm wrong, I'm not a packaging expert!
Klaumi
---
Klaus-Michael Klingsporn
mail: klaumi...@gmx.de
web: www.klaumikli.de
pgpDNoHtkEcGw.pgp
Description: Digitale Signatur von OpenPGP
Bug#941634: marked as done (thawab depends on python-okasha which isn't provided by src:okasha anymore)
Your message dated Mon, 18 Nov 2019 18:41:48 -0500 with message-id and subject line Re: thawab: Python2 removal in sid/bullseye has caused the Debian Bug report #941634, regarding thawab depends on python-okasha which isn't provided by src:okasha anymore 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.) -- 941634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: thawab Version: 4.1-1 Severity: serious Justification: non-installable -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear maintainer, You package depends on python-okasha. However the maintainers of src:okasha have desided to drop that package as Debian is try to get rid of Python 2 before the release of bullseye. This move makes your package non-installable. So either fix the dependency you have on that package by upgrading your package towards Python 3, or have the maintainer of src:okasha (temporarily) revert the removal of the python2 package for now if the solution to this issue takes more time. In that case please align with the maintainers of okasha for a plan forward. Paul - -- 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-2-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages thawab depends on: ii gir1.2-gtk-3.0 3.24.11-1 pn gir1.2-webkit2-4.0 pn mdbtools ii python 2.7.16-1 ii python-gi 3.34.0-1 pn python-okasha pn python-othman pn python-paste pn python-whoosh Versions of packages thawab recommends: pn islamic-menus thawab suggests no packages. -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl2VpxcACgkQnFyZ6wW9 dQowVQf/Uoi+ePq054LXj2tMQZ8dmPfr2dP639qkmEqWE8TMTnQvprSc2yujsJza bTJru9ituK+ZvdhftQbafcDsWOgLbD09nRJ5sWRBe8Ck5Ggove3vIu/w7669uLhc XDktOTeYetDZwyoklrjaH7G6Drmp1yugBo/76JHkehePr60Hucnc5hC+PkIe1tTE hDeFOklK2FDyhxG/pLLBZikdvSHqmsZL0mibv54fOzh0oSXQ9xdxhwpbm75S7dii Y+FqmI/mzKCem8RvuwBXQ5m4h6QoyjLDGYzN/GNA2c0LDmDgat7EeR6d6LZmvKJs cPsGErr4JYM/Js6dCtUWpUNCLU4QmQ== =d7yL -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Version: 4.1-2 On Wed, 23 Oct 2019 02:33:34 + mo...@debian.org wrote: > Source: thawab > Version: 4.1-1 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal https://tracker.debian.org/news/1080898/accepted-thawab-41-2-source-all-into-unstable/--- End Message ---
Bug#945047: Needs dependency for Crypt/Digest/SHA256.pm
Package: extrepo Version: 0.2 Severity: serious Attempting to run extrepo produces: Can't locate Crypt/Digest/SHA256.pm in @INC (you may need to install the Crypt::Digest::SHA256 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/Debian/ExtRepo/Commands/Enable.pm line 9. BEGIN failed--compilation aborted at /usr/share/perl5/Debian/ExtRepo/Commands/Enable.pm line 9. Compilation failed in require at /usr/share/perl5/Debian/ExtRepo/Commands/Update.pm line 3. BEGIN failed--compilation aborted at /usr/share/perl5/Debian/ExtRepo/Commands/Update.pm line 3. Compilation failed in require at /usr/bin/extrepo line 7. BEGIN failed--compilation aborted at /usr/bin/extrepo line 7. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages extrepo depends on: ii gpgv 2.2.17-3 ii libwww-perl 6.41-1 ii libyaml-perl 1.29-1 ii perl 5.30.0-9 extrepo recommends no packages. extrepo suggests no packages. -- no debconf information
Bug#945046: linux-image-5.2.0-0.bpo.3-amd64: Kernel crashes / system reboots constantly
Package: linux-image-5.2.0-0.bpo.3-amd64 Severity: critical Justification: breaks the whole system Dear Maintainer, My DMI: Dell Inc. PowerEdge R710/00NH4P, BIOS 2.1.9 05/21/2010 reboots / crashes constantly, in recovery mode later, in normal mode almost immediately after boot / often before the login. I do not have crash logs and could not retrieve some yet. -- System Information: Debian Release: 10.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-5.2.0-0.bpo.3-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.133+deb10u1 ii kmod26-1 ii linux-base 4.6 Versions of packages linux-image-5.2.0-0.bpo.3-amd64 recommends: ii apparmor 2.13.2-10 ii firmware-linux-free 3.4 Versions of packages linux-image-5.2.0-0.bpo.3-amd64 suggests: pn debian-kernel-handbook ii grub-efi-amd64 2.02+dfsg1-20 pn linux-doc-5.2
Processed: limit source to ldh-gui-suite, tagging 942703, tagging 943568, tagging 942657, tagging 943533
Processing commands for cont...@bugs.debian.org: > limit source ldh-gui-suite Limiting to bugs with field 'source' containing at least one of 'ldh-gui-suite' Limit currently set to 'source':'ldh-gui-suite' > tags 942703 + pending Bug #942703 [ldh-gui-suite] ldh-gui-suite: : French debconf templates translation Added tag(s) pending. > tags 943568 + pending Bug #943568 [ldh-gui-suite] ldh-gui-suite: [INTL:de] initial German debconf translation Added tag(s) pending. > tags 942657 + pending Bug #942657 [ldh-gui-suite] ldh-gui-suite: [INTL:pt] Updated Portuguese translation - debconf messages Added tag(s) pending. > tags 943533 + pending Bug #943533 [ldh-gui-suite] ldh-gui-suite: fails to install: mv: cannot move '/tmp/debconf_SxQLyd2wY8' to '/var/lib/one.liberty/deckhost.conf': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 942657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942657 942703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942703 943533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943533 943568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#944760: ghostscript: CVE-2019-14869
Control: severity -1 important Quoting Salvatore Bonaccorso (2019-11-14 22:47:49) > Source: ghostscript > Version: 9.50~dfsg-2 > Severity: grave > Tags: security upstream > Control: found -1 9.26a~dfsg-0+deb9u5 > Control: found -1 9.26a~dfsg-0+deb9u1 > Control: found -1 9.27~dfsg-2+deb10u2 > Control: found -1 9.27~dfsg-1 > Control: found -1 9.27~dfsg-3.1 > Control: fixed -1 9.26a~dfsg-0+deb9u6 > Control: fixed -1 9.27~dfsg-2+deb10u3 > > Hi, > > The following vulnerability was published for ghostscript. I can agree > the severity is not exaclty matching, as for 9.50 itself, it's not > anymore directly exploitable (unless with -dOLDSAFER). Still it cannot > be considred fixed, only after applying [1]. Lowering severity to avoid this blocking more grave security fixes entering testing. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Processed: Re: Bug#944760: ghostscript: CVE-2019-14869
Processing control commands: > severity -1 important Bug #944760 [src:ghostscript] ghostscript: CVE-2019-14869 Severity set to 'important' from 'grave' -- 944760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944760 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#843324: marked as done (ghostscript crashes on some machines, much of the time)
Your message dated Mon, 18 Nov 2019 22:30:07 +0100
with message-id <157411260768.238883.8182046441171275...@auryn.jones.dk>
and subject line Re: Bug#843324: ghostscript crashes on some machines, much of
the time
has caused the Debian Bug report #843324,
regarding ghostscript crashes on some machines, much of the time
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.)
--
843324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ghostscript
Version: 9.06~dfsg-2+deb8u4
Tags: patch
Severity: serious
Control: fixed -1 9.19~dfsg-3.1
On some machines, with recent jessie libcs, on amd64 Linux (at least),
ghostscript crashes because it unlocks an already-unlocked pthread
DEFAULT mutex. (Well, actually, in my test case, it locks it twice,
and then unlocks it twice.)
This is the upstream bug:
http://bugs.ghostscript.com/show_bug.cgi?id=695862
It can be fixed by cherry-picking the corresponding upstream patch,
444e0bf9c43b "Bug 695862: use PTHREAD_MUTEX_RECURSIVE(_NP) if available"
Please find attached a suitable backport. I threw away the changes to
the configure and build system. We do not need these because we
always have recursive mutexes available: so instead, I just definen
the appropriate preprocessor symbol in the file which uses it.
Thanks.
Ian.
>From f96eb410d8c1b6f7660638c39c9add82be158d94 Mon Sep 17 00:00:00 2001
From: Chris Liddell
Date: Mon, 16 Mar 2015 12:52:49 +
Subject: [PATCH] Bug 695862: use PTHREAD_MUTEX_RECURSIVE(_NP) if available
or properly emulate recursive mutexes ourselves.
No cluster differences
(cherry picked from commit 444e0bf9c43bae0261660e6318ba0e514c18d41e)
Conflicts:
config.mak.in
configure.ac
gs/Makefile.in
gs/configure.ac
[ Dropped all the buildsystem and configure changes. Instead,
we just hardcode GS_RECURSIVE_MUTEXATTR since it will
always be available on Debian. -iwj ]
---
base/gp_psync.c | 71 +++--
1 file changed, 59 insertions(+), 12 deletions(-)
diff --git a/base/gp_psync.c b/base/gp_psync.c
index 60f6977..d09871b 100644
--- a/base/gp_psync.c
+++ b/base/gp_psync.c
@@ -13,6 +13,7 @@
CA 94903, U.S.A., +1(415)492-9861, for further information.
*/
+#define GS_RECURSIVE_MUTEXATTR 1 /* always, on Debian */
/* POSIX pthreads threads / semaphore / monitor implementation */
#include "std.h"
@@ -128,13 +129,20 @@ gp_semaphore_signal(gp_semaphore * sema)
/* Monitor supports enter/leave semantics */
/*
- * We need PTHREAD_MUTEX_RECURSIVE behavior, but this isn't totally portable
- * so we implement it in a more portable fashion, keeping track of the
- * owner thread using 'pthread_self()'
+ * We need PTHREAD_MUTEX_RECURSIVE behavior, but this isn't
+ * supported on all pthread platforms, so if it's available
+ * we'll use it, otherwise we'll emulate it.
+ * GS_RECURSIVE_MUTEXATTR is set by the configure script
+ * on Unix-like machines to the attribute setting for
+ * PTHREAD_MUTEX_RECURSIVE - on linux this is usually
+ * PTHREAD_MUTEX_RECURSIVE_NP
*/
typedef struct gp_pthread_recursive_s {
pthread_mutex_t mutex; /* actual mutex */
+#ifndef GS_RECURSIVE_MUTEXATTR
pthread_t self_id;/* owner */
+int lcount;
+#endif
} gp_pthread_recursive_t;
uint
@@ -148,12 +156,32 @@ gp_monitor_open(gp_monitor * mona)
{
pthread_mutex_t *mon;
int scode;
+pthread_mutexattr_t attr;
+pthread_mutexattr_t *attrp = NULL;
if (!mona)
return -1; /* monitors are not movable */
-mon = &((gp_pthread_recursive_t *)mona)->mutex;
+
+
+#ifdef GS_RECURSIVE_MUTEXATTR
+attrp =
+scode = pthread_mutexattr_init(attrp);
+if (scode < 0) goto done;
+
+scode = pthread_mutexattr_settype(attrp, GS_RECURSIVE_MUTEXATTR);
+if (scode < 0) {
+goto done;
+}
+#else
((gp_pthread_recursive_t *)mona)->self_id = 0; /* Not valid unless
mutex is locked */
-scode = pthread_mutex_init(mon, NULL);
+((gp_pthread_recursive_t *)mona)->lcount = 0;
+#endif
+
+mon = &((gp_pthread_recursive_t *)mona)->mutex;
+scode = pthread_mutex_init(mon, attrp);
+if (attrp)
+(void)pthread_mutexattr_destroy(attrp);
+done:
return SEM_ERROR_CODE(scode);
}
@@ -173,29 +201,48 @@ gp_monitor_enter(gp_monitor * mona)
pthread_mutex_t * const mon = (pthread_mutex_t *)mona;
int scode;
+#ifdef GS_RECURSIVE_MUTEXATTR
+scode = pthread_mutex_lock(mon);
+#else
if ((scode =
Processed: Re: Bug#940127: ghostscript makes c2esp autopkgtest timeout
Processing control commands: > severity -1 important Bug #940127 [src:ghostscript, src:c2esp] gs segfaults in c2esp filter chain Severity set to 'important' from 'serious' -- 940127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940127 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#940127: ghostscript makes c2esp autopkgtest timeout
Control: severity -1 important Quoting Jonas Smedegaard (2019-11-14 14:28:35) > @Didier: Since you reassigned this to (only) ghostscript, would you > please consider re-reassigning to (only) c2esp instead? > > Reason I ask is that ghostscript is now security-buggy in testing > since a month, seemingly blocked only by this issue. If reassigning > does not seem sensible, then how about lowering severity (maybe only > temporarily)? Lowering severity to prioritize general security over use with c2esp. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#944938: marked as done (ltt-control: needs an explicit build dependency on dh-python)
Your message dated Mon, 18 Nov 2019 21:21:00 + with message-id and subject line Bug#944938: fixed in ltt-control 2.11.0-3 has caused the Debian Bug report #944938, regarding ltt-control: needs an explicit build dependency on dh-python 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.) -- 944938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944938 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ltt-control Version: 2.11.0-2 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python. --- End Message --- --- Begin Message --- Source: ltt-control Source-Version: 2.11.0-3 We believe that the bug you reported is fixed in the latest version of ltt-control, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 944...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Jeanson (supplier of updated ltt-control package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 18 Nov 2019 15:58:58 -0500 Source: ltt-control Architecture: source Version: 2.11.0-3 Distribution: unstable Urgency: medium Maintainer: Jon Bernard Changed-By: Michael Jeanson Closes: 944938 Changes: ltt-control (2.11.0-3) unstable; urgency=medium . * [e8b29e1] Add build dependency on dh-python (Closes: #944938) Checksums-Sha1: f3914f997b3badeb2001bc9a4570b0a268fdd89a 2618 ltt-control_2.11.0-3.dsc 43da24c506c7f42095625216b1df1c29d63a7d63 20604 ltt-control_2.11.0-3.debian.tar.xz 1d9c6f2b37e4430c35db644a0946f480a8049ac2 7676 ltt-control_2.11.0-3_source.buildinfo Checksums-Sha256: 805318a164835c9bdb57d19cce2333718356910ebab5fa89f4abc348e1ed2873 2618 ltt-control_2.11.0-3.dsc 4d899dd9cd4c70a03502f70ca1dc4814f239b53631dfdd70c2bfa25a10a9d797 20604 ltt-control_2.11.0-3.debian.tar.xz a78e638e754faf4f12dd391159123866efd48244ab84435d9eca5e9c1a574afa 7676 ltt-control_2.11.0-3_source.buildinfo Files: 10452aca9231d15a13f9d6f4ca570748 2618 libs optional ltt-control_2.11.0-3.dsc 340342c298fe9afbd2907e1f660ccc4b 20604 libs optional ltt-control_2.11.0-3.debian.tar.xz 782e4dac128c5c285c59928a8b94c7c2 7676 libs optional ltt-control_2.11.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEmGYkMkK2Qid54gtihlYfRSGA/P4FAl3TBmcUHG1qZWFuc29u QGRlYmlhbi5vcmcACgkQhlYfRSGA/P62KA/8ChUxolt2uTRG8QdDISwAEvSaEYQW 21Jsv7P9R9tn4wc6HLNEnRwRmKwJeDWrD0givFUCO4E+zZt7/RQrWF99Ny6oalWq FuPKa747rB7ax7B/CbM6izD5QWBII5RLvem416/L1t6u1U33ryo8OlEui2iySjTB o9HqqZtoWIzIYqDSPzvWBLrWdnpWAix7TGozQOOger1SluSoG0R5qZ7wSYG/kpHk kdCjZizGpRe7YlPfZ6MEzcHUuPNmqU/8x3qbY+N8IflIeCzo4Uwvwt3BSHPR0owv V+fO9r9pOboj/fQSAkKDOSCTYLgOsQtOL+KoMAoRaE9zZRqudE+Pu2G7z93sqPsQ NsvErsxX24JW9SwCnT3uiHahmmKrG2ZNaoIsTmtEdACNADPWqu1vLsB/BvM2Q88U 8Cv+KrDtD4pG1SB0EY8Pf61g7GJRK1N7Yu0JNURpUHUgWr4FlylxEHVsv3gh6Mss UraB5cBlgH99ApCXSl+nV+yJ5WR79rOT+dtGpb/WHKL6MJihG/l1VK9BrUpdnDo6 Y5pR5+m1DN0xEEjXupBteYzk0O0WttLv0NSmA4GtBd/E0KuJjx9d/Q9gcoZO1GrM BpiVNnM28thnWsR3Ib3SX5oTBvHq9kwTxHB5fjJlY2I/aozc+I+8AWbsCWa+nEWm Nt+9Kc8LEFToqBE= =dTrO -END PGP SIGNATURE End Message ---
Bug#944933: marked as done (babeltrace: needs an explicit build dependency on dh-python)
Your message dated Mon, 18 Nov 2019 21:19:59 + with message-id and subject line Bug#944933: fixed in babeltrace 1.5.7-2 has caused the Debian Bug report #944933, regarding babeltrace: needs an explicit build dependency on dh-python 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.) -- 944933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:babeltrace Version: 1.5.7-1 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python. --- End Message --- --- Begin Message --- Source: babeltrace Source-Version: 1.5.7-2 We believe that the bug you reported is fixed in the latest version of babeltrace, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 944...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Jeanson (supplier of updated babeltrace package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 18 Nov 2019 15:51:11 -0500 Source: babeltrace Architecture: source Version: 1.5.7-2 Distribution: unstable Urgency: medium Maintainer: Jon Bernard Changed-By: Michael Jeanson Closes: 944933 Changes: babeltrace (1.5.7-2) unstable; urgency=medium . * [1062de0] Add build dependency on dh-python (Closes: #944933) Checksums-Sha1: 0c1ed69fd1f908b8934dbd52558fa09f314e2a03 2408 babeltrace_1.5.7-2.dsc 3cb65b620082ea5c85ef8a2eb03cd5322019b455 11612 babeltrace_1.5.7-2.debian.tar.xz 98be65e3ba77b608c5ed261d4e95a699f3c1b50b 7964 babeltrace_1.5.7-2_source.buildinfo Checksums-Sha256: c36b0fe2510d5306c8b9357f86bac7db0a4f3ee9fd7024f5090be1bc339a538e 2408 babeltrace_1.5.7-2.dsc 249f14bc7708ef8033f9bc62172afa3bfabd5006b5e5563ea43e0e6a81e47301 11612 babeltrace_1.5.7-2.debian.tar.xz a60f6cfd871da6cf3e57f6d115a4290c6b7c85bf16af682945f3e4bb17b16d58 7964 babeltrace_1.5.7-2_source.buildinfo Files: 587602dd9f24ed71fa89120269a8c13d 2408 libs optional babeltrace_1.5.7-2.dsc 9a591a1da8241ca29f41149f94d60e67 11612 libs optional babeltrace_1.5.7-2.debian.tar.xz 88458d2512178dec2a0634c4d7a4e116 7964 libs optional babeltrace_1.5.7-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEmGYkMkK2Qid54gtihlYfRSGA/P4FAl3TBVkUHG1qZWFuc29u QGRlYmlhbi5vcmcACgkQhlYfRSGA/P6dNA/+OeKTWuiTDe5LPX3C9gINkvLkBgeF 2o6JEn4098C0CsntQL0v/YivRmi7u3iQ+OuFSnJ2K5BFnK+cM6OynyuP/5EitbBO iaR/IhmbsYBUrJhBCygujqigbohtSJFsesqFMoM85Cx/6Hlb70O3qWuFlsFx4Snu hYtNLWZpKxvOa6iU4BRDScnF2qgdrtPNNO4PfRHm9AWtY/aiaAIRrp1LAHAH8JEt dFPbf3GTeSEa8HASm7Kqee7Z6AzEW6DhcwVDGAnsUnIADVKOEywJ3EbLm0Pndvqw bSc9OzP9CLIUxdh3RRzxnmOQCbnmzp0JyhLSmxF0xt8B1kxRYiDW123o72jtsDMT OHObOlTl/dy6AXu1nY9mQbi1PwFrwqcff01kBMJ8pUtvOswdxK1WHU+EBGd4wf9P VTd10mRMHNXpKUJapEQNHzoSXQ996jWohrqa5ekX+9E28F1EuOxRCCM+oCnIXxXm R3wjmso3PD7EGD25um39h//3xxm4OXNFANLJHe69jXXhlNFP89mWORj34OKsIoxQ XGdbL1zECHcbXMiCejMNRP8C7Vd/rXVrRHiqyKLsaZ/F7fpt1hCr4/7OuWhcbaSa ZEbLpOKvprtwjaO2N5j4gUTEt944CHU2BospgKroZ4RoyX+MUiw8x5T9vx8o1dz9 aztcJLRHtQmjbx4= =91f5 -END PGP SIGNATURE End Message ---
Bug#945041: openfoam: severe build time regression
Source: openfoam Version: 1906+dfsg1-1 Severity: serious Hi, Looking at https://buildd.debian.org/status/logs.php?pkg=openfoam the build time for your package increased unreasonably in this version. Cheers, Julien
Bug#942235:
Hi,
Running autopkgtest I have this error:
autopkgtest [17:27:31]: test command1: set -e ; for py in
$(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo
"Testing with $py:" ; http_proxy= $py -m pytest -v --pyargs dask ;
done
autopkgtest [17:27:31]: test command1: [---
Testing with python3.8:
= test session starts ==
platform linux -- Python 3.8.0, pytest-4.6.6, py-1.8.0, pluggy-0.13.0
-- /usr/bin/python3.8
cachedir: .pytest_cache
rootdir: /tmp/autopkgtest.ZwzvJ1/autopkgtest_tmp
collecting ... collected 2144 items / 39 errors / 8 skipped / 2097 selected
ERRORS
___ ERROR collecting array/tests/test_array_core.py
ImportError while importing test module
'/usr/lib/python3/dist-packages/dask/array/tests/test_array_core.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3/dist-packages/pandas/__init__.py:30: in
from pandas._libs import hashtable as _hashtable, lib as _lib,
tslib as _tslib
/usr/lib/python3/dist-packages/pandas/_libs/__init__.py:3: in
from .tslibs import (
/usr/lib/python3/dist-packages/pandas/_libs/tslibs/__init__.py:3: in
from .conversion import localize_pydatetime, normalize_date
E ModuleNotFoundError: No module named 'pandas._libs.tslibs.conversion'
During handling of the above exception, another exception occurred:
/usr/lib/python3/dist-packages/dask/dataframe/__init__.py:2: in
from .core import (
/usr/lib/python3/dist-packages/dask/dataframe/core.py:10: in
import pandas as pd
/usr/lib/python3/dist-packages/pandas/__init__.py:34: in
raise ImportError(
E ImportError: C extension: No module named
'pandas._libs.tslibs.conversion' not built. If you want to import
pandas from the source directory, you may need to run 'python setup.py
build_ext --inplace --force' to build the C extensions first.
During handling of the above exception, another exception occurred:
/usr/lib/python3/dist-packages/dask/array/tests/test_array_core.py:21:
in
import dask.dataframe
/usr/lib/python3/dist-packages/dask/dataframe/__init__.py:55: in
raise ImportError(str(e) + "\n\n" + msg)
E ImportError: C extension: No module named
'pandas._libs.tslibs.conversion' not built. If you want to import
pandas from the source directory, you may need to run 'python setup.py
build_ext --inplace --force' to build the C extensions first.
E
E Dask dataframe requirements are not installed.
E
E Please either conda or pip install as follows:
E
E conda install dask # either conda install
E pip install dask[dataframe] --upgrade # or pip install
__ ERROR collecting array/tests/test_image.py __
/usr/lib/python3/dist-packages/skimage/__init__.py:162: in
from ._shared import geometry
E ImportError: cannot import name 'geometry' from 'skimage._shared'
(/usr/lib/python3/dist-packages/skimage/_shared/__init__.py)
During handling of the above exception, another exception occurred:
/usr/lib/python3/dist-packages/dask/array/tests/test_image.py:6: in
pytest.importorskip("skimage")
/usr/lib/python3/dist-packages/skimage/__init__.py:165: in
_raise_build_error(e)
/usr/lib/python3/dist-packages/skimage/__init__.py:138: in _raise_build_error
local_dir = osp.split(__file__)[0]
E NameError: name 'osp' is not defined
___ ERROR collecting bag/tests/test_avro.py
ImportError while importing test module
'/usr/lib/python3/dist-packages/dask/bag/tests/test_avro.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3/dist-packages/dask/bag/__init__.py:2: in
from .core import (
/usr/lib/python3/dist-packages/dask/bag/core.py:67: in
from ..bytes import open_files
/usr/lib/python3/dist-packages/dask/bytes/__init__.py:9: in
raise ImportError(
E ImportError: fsspec is required to use any file-system
functionality. Please install using
E conda install -c conda-forge 'fsspec>=0.3.3'
E or
E pip install 'fsspec>=0.3.3'
I will work on fsspec now and try to solve the pandas issues
Cheers,
Arias Emmanuel
@eamanu
http://eamanu.com
Bug#941669: python3-rpi.gpio fails to work on aarch64 (upgrade needed)
Hello, On Thu, Oct 03, 2019 at 03:36:26PM +, André Draszik wrote: > Package: python3-rpi.gpio > Version: 0.6.5-1 > Severity: grave > Tags: upstream > Justification: renders package unusable > > > Hi, > > python3-rpi.gpio 0.6.5 as is current in sid, doesn't support > aarch64: > > Traceback (most recent call last): > File "./server.py", line 8, in > import RPi.GPIO as GPIO > File "/usr/lib/python3/dist-packages/RPi/GPIO/__init__.py", line 23, in > > from RPi._GPIO import * > RuntimeError: This module can only be run on a Raspberry Pi! > > > Upstream has fixed this in the 0.7.0 release, see here > https://sourceforge.net/p/raspberry-gpio-python/tickets/161/ > > I am kindly asking to please update the Debian package. It seems it is necessary to cherry pick change 129:03be41933c1b from upstream. Best regards Uwe signature.asc Description: PGP signature
Bug#943442: reprozip needs a new upstream version for Python 3.8
Upstream version 1.0.16 supports Python 3.8. 1.0.15 and below won't work because of the removed platform.linux_distribution() function in Python 3.8.
Processed: forcibly merging 945014 945033
Processing commands for cont...@bugs.debian.org: > forcemerge 945014 945033 Bug #945014 [enigmail] enigmail removed after installing thunderbird 68.2.2-1~deb10u1 Bug #945014 [enigmail] enigmail removed after installing thunderbird 68.2.2-1~deb10u1 There is no source info for the package 'enigmail' at version '2.0.12+ds1-1~deb10u1' with architecture '' Unable to make a source version for version '2.0.12+ds1-1~deb10u1' Marked as found in versions enigmail/2:2.0.12+ds1-1~deb10u1. Bug #945033 [enigmail] enigmail in Buster uninstallable due to thunderbird 1:68.2.2-1~deb10u1 Severity set to 'important' from 'grave' There is no source info for the package 'enigmail' at version '2.0.12+ds1-1~deb10u1' with architecture '' Unable to make a source version for version '2.0.12+ds1-1~deb10u1' Marked as found in versions 2.0.12+ds1-1~deb10u1. Merged 945014 945033 > thanks Stopping processing here. Please contact me if you need assistance. -- 945014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945014 945033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945033: enigmail in Buster uninstallable due to thunderbird 1:68.2.2-1~deb10u1
Package: enigmail Version: 2:2.0.12+ds1-1~deb10u1 Severity: grave Hello, unfortunately, the latest security update of thunderbird (to 1:68.2.2-1~deb10u1) rendered enigmail uninstallable in Buster. That's because thunderbird 1:68.2.2-1~deb10u1 has `enigmail (<< 2:2~)` listed in its `Breaks` header. Probably an upload of newer enigmail to stable or stable-security is needed to resolve this issue. Thanks a lot for maintaining enigmail in Debian! Cheers jonas
Bug#944431: Segfault on startup
Hello Markus, hello Enrico,
I am sorry to be late, but I guess I have found the issue.
The function SetThreadPriority does not return properly
therefore the following function gets executed which writes
to somewhere, that causes later the crash below.
The build logs show a warning for this issue:
tmp/compat_mini.cpp: In function ‘int SetThreadPriority(THREAD_HANDLE,
int)’:
tmp/compat_mini.cpp:106:1: warning: no return statement in function
returning non-void [-Wreturn-type]
106 | }
| ^
Attached patch adds return statements for all functions
currently triggering this warning.
Kind regards,
Bernhard
(gdb) bt
#0 0x562c7679292e in flip () at komat/Berusky3d_ini.cpp:46
#1 0x562c767ea5e4 in ddxPublish () at tmp/compat.cpp:196
#2 0x562c767ea6a9 in DisplayFrame () at tmp/compat.cpp:120
#3 0x562c76737374 in RunMenu (p_File_Name=p_File_Name@entry=0x562c76888c8b
"mainmenu.txt", hWnd=hWnd@entry=0x0, p_ad=, cpu=cpu@entry=8304)
at kofola/Menu.cpp:5810
#4 0x562c767771b7 in winmain_Game_Run (p_Level_Name=0x562c76bf3148
"") at kofola/game_main.cpp:252
#5 0x562c7671b293 in main (argc=, argv=) at
komat/Berusky3d_ini.cpp:360
Description: Avoid 'no return statement in function returning non-void'
Author: Bernhard Ãbelacker
Bug-Debian: https://bugs.debian.org/944431
Forwarded: no
Last-Update: 2019-11-18
--- berusky2-0.10.orig/src/tmp/compat_mini.cpp
+++ berusky2-0.10/src/tmp/compat_mini.cpp
@@ -92,7 +92,7 @@ THREAD_HANDLE CreateThread(void *lpThrea
int CloseHandle(THREAD_HANDLE handle)
{
-
+ return 1;
}
void ExitThread(dword dwExitCode)
@@ -103,10 +103,12 @@ void ExitThread(dword dwExitCode)
int SetThreadPriority(THREAD_HANDLE hThread, int nPriority)
{
+ return 1;
}
int GetThreadPriority(THREAD_HANDLE hThread)
{
+ return 0/*THREAD_PRIORITY_NORMAL*/;
}
int GetExitCodeThread(THREAD_HANDLE hThread, dword *lpExitCode)
# Buster/stable amd64 qemu VM 2019-11-15
apt update
apt dist-upgrade
apt install systemd-coredump dpkg-dev devscripts xserver-xorg lightdm openbox
xterm gdb valgrind rr berusky2 berusky2-dbgsym
apt build-dep berusky2
reboot
echo 1 > /proc/sys/kernel/perf_event_paranoid
mkdir /home/benutzer/source/berusky2/orig -p
cd/home/benutzer/source/berusky2/orig
apt source berusky2
cd
export DISPLAY=:0
export LANG=C
berusky2
# crashes
rr berusky2
# does not crash
valgrind berusky2
# crashes
valgrind --track-origins=yes berusky2
# crashes
gdb -q --args berusky2
# crashes
$ berusky2
Berusky 2 v.0.10 (C) Anakreon 2011, http://www.anakreon.cz/
...
Kofola: - Load bitmap pro herni menu
--Total load time 0.2 s -
APAK: font_en.pak
Velikost AFAT: 2.6KB
Velikost Archivu: 0.4MB
Souboru: 7
Adresaru: 0
Uzlu: 2
b2_2d_font.pTTable = 0x563f6ddc1160
set font = font_en.pak
APAK: font_system_en.pak
Velikost AFAT: 2.6KB
Velikost Archivu: 0.1MB
Souboru: 7
Adresaru: 0
Uzlu: 2
b2_2d_font.pTTable = 0x563f70bd40f0
set font = font_system_en.pak
Segmentation fault (core dumped)
#
Nov 15 17:22:58 debian systemd-coredump[647]: Process 627 (berusky2) of user
1000 dumped core.
Stack trace of thread 627:
#0 0x563f6b62b92e n/a
(berusky2)
#1 0x563f6b6835e4 n/a
(berusky2)
#2 0x563f6b6836a9 n/a
(berusky2)
#3 0x563f6b5d0374 n/a
(berusky2)
#4 0x563f6b6101b7 n/a
(berusky2)
#5 0x563f6b5b4293 main
(berusky2)
#6 0x7f2f6423a09b
__libc_start_main (libc.so.6)
#7 0x563f6b5b450a n/a
(berusky2)
Stack trace of thread 642:
#0 0x7f2f64304819 __poll
(libc.so.6)
#1 0x7f2f63bdd9af n/a
(libasound.so.2)
#2 0x7f2f63bddccb
snd_pcm_wait (libasound.so.2)
#3 0x7f2f6498d2ff n/a
(libopenal.so.1)
#4 0x7f2f6499bb67 n/a
(libopenal.so.1)
#5 0x7f2f64701fa3
start_thread (libpthread.so.0)
#6 0x7f2f6430f4cf __clone
(libc.so.6)
Stack trace of thread 643:
#0 0x7f2f6470a896
do_futex_wait.constprop.1 (libpthread.so.0)
Bug#944249: [Pkg-emacsen-addons] Bug#944249: gnuplot-mode does not work with emacs26
On Mon, Nov 18, 2019 at 08:30:46AM -0400, David Bremner wrote:
> Agustin Martin writes:
>
> > Hi, David,
> >
> >> That's not loaded by elpa packages.
> >
> > But AFAIK it should be loaded by Emacs,
>
> Perhaps. Team packages don't use these startup files anymore. Most of
> the content (updating load paths in particular) is handled more reliably
> by package.el generated autoload files.
>
> >> The general approach is to add an autoload cookie to set
> >> auto-mode-alist. See "HINTS" in dh_elpa(1).
> >
> > I was looking at it and noticed the autoloads part, but nothing about
> > `auto-mode-alist'. Where is it?
> >
>
> See "Other customizations"
Thanks for insisting, it was not clear to me after a quick read.
I am attaching a patch to replace
[0003-elpa-gnuplot-mode.emacsen-startup-Add-auto-mode-alis.patch]
doing things the elpa way.
--
Agustin
>From 74c09c964923c9119546aba0cd59cd56b40acb76 Mon Sep 17 00:00:00 2001
From: Agustin Martin Domingo
Date: Mon, 18 Nov 2019 16:07:16 +0100
Subject: [PATCH] debian/debian-autoloads.el: Handle auto-mode-alist stuff the
elpa way.
---
debian/debian-autoloads.el| 2 ++
debian/elpa-gnuplot-mode.elpa | 1 +
2 files changed, 3 insertions(+)
create mode 100644 debian/debian-autoloads.el
diff --git a/debian/debian-autoloads.el b/debian/debian-autoloads.el
new file mode 100644
index 000..e2c1d6d
--- /dev/null
+++ b/debian/debian-autoloads.el
@@ -0,0 +1,2 @@
+;;;###autoload
+(setq auto-mode-alist (append '(("\\.gp\\'" . gnuplot-mode)) auto-mode-alist))
diff --git a/debian/elpa-gnuplot-mode.elpa b/debian/elpa-gnuplot-mode.elpa
index cd726c7..3e61da9 100644
--- a/debian/elpa-gnuplot-mode.elpa
+++ b/debian/elpa-gnuplot-mode.elpa
@@ -2,3 +2,4 @@ gnuplot.el
gnuplot-gui.el
gnuplot-context.el
debian/gnuplot-mode-pkg.el
+debian/debian-autoloads.el
--
2.24.0
Bug#867694: netsurf-fb: Completely unusable due to missing dependencies, symlinks and documentation
Hi Vincent and Daniel, Are you still interested in maintaining NetSurf officially for Debian? Reason I ask is that this release-critical bug#867694 has triggerd no action or comment from any of you since it was filed in July 2017, more than two years ago. I notice that the packaging git at http://source.netsurf-browser.org/packaging/debian.git/ has received commits from Vincent as recent as June 2019. If you are still interested in maintaining NetSurf officially for Debian, then please share your thoughts on current status - even if there is no solution in sight then simply a life sign from you is helpful now. Kind regards, and hoping you are both well and in good spirit, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#944993: marked as done (gnome-shell-extension-show-ip: primary-interface patch broke loading the extension)
Your message dated Mon, 18 Nov 2019 15:21:39 +
with message-id
and subject line Bug#944993: fixed in gnome-shell-extension-show-ip 8-5~exp1
has caused the Debian Bug report #944993,
regarding gnome-shell-extension-show-ip: primary-interface patch broke loading
the extension
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.)
--
944993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944993
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-show-ip
Version: 8-4
Severity: serious
Tags: patch
The primary-interface patch I proposed had a serious issue:
JS ERROR: Extension show...@sgaraud.github.com: ReferenceError: device is not
defined
I've fixed the issue upstream and in the attached patch.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing-debug
APT policy: (900, 'testing-debug'), (900, 'testing'), (800,
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700,
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gnome-shell-extension-show-ip depends on:
ii gnome-shell 3.34.1+git20191024-1
gnome-shell-extension-show-ip recommends no packages.
gnome-shell-extension-show-ip suggests no packages.
-- no debconf information
--
bye,
pabs
https://wiki.debian.org/PaulWise
From 626ff48b7e29cf4178a2f439b85340e7b1e25774 Mon Sep 17 00:00:00 2001
From: Paul Wise
Date: Thu, 2 Mar 2017 18:07:14 +0800
Subject: [PATCH] Show the primary IP address when no interface was chosen
Makes it easier to see all IP addresses at a glance.
Uses NM to get which interface(s) are in the default route.
---
README.md| 1 +
extension.js | 53 +---
2 files changed, 43 insertions(+), 11 deletions(-)
diff --git a/README.md b/README.md
index 0fafb7a..eec47e3 100644
--- a/README.md
+++ b/README.md
@@ -83,6 +83,7 @@ issues](https://github.com/sgaraud/gnome-extension-show-ip/issues).
### License
Copyright (C) 2015 Sylvain Garaud
+Copyright 2017 Paul Wise
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
diff --git a/extension.js b/extension.js
index d9a7940..5dc7d9a 100644
--- a/extension.js
+++ b/extension.js
@@ -3,6 +3,7 @@
* https://github.com/sgaraud/gnome-extension-show-ip
*
* Copyright (C) 2015 Sylvain Garaud
+ * Copyright 2017 Paul Wise
*
* This file is part of Show-IP GNOME extension.
* Show IP GNOME extension is free software: you can redistribute it and/or modify
@@ -170,17 +171,30 @@ const IpMenuBase = new Lang.Class({
}
});
+this._getPrimaryDevices(this.client);
+let selectedIp = '';
+let primaryIp = '';
+let firstIp = '';
for (let device of this._devices) {
-if (device.ifc == this.selectedDevice) {
-if (Schema.get_boolean("menu")) {
-this.label.set_text(_("IP: %s").format(device.ip));
-} else {
-this.label.set_text(device.ip);
-}
-break;
+if (!selectedIp && device.ifc == this.selectedDevice) {
+selectedIp = device.ip;
+}
+if (!primaryIp && device.primary) {
+primaryIp = device.ip;
+}
+if (!firstIp) {
+firstIp = device.ip;
}
}
-if ('' == this.selectedDevice) {
+let ip = selectedIp ? selectedIp : primaryIp ? primaryIp : firstIp;
+if (ip) {
+if (Schema.get_boolean("menu")) {
+this.label.set_text(_("IP: %s").format(ip));
+} else {
+this.label.set_text(ip);
+}
+this.label.set_text(ip);
+} else {
this.label.set_text(NOT_CONNECTED);
}
},
@@ -207,6 +221,26 @@ const IpMenuBase = new Lang.Class({
this._createPopupMenu();
},
+_getPrimaryDevices: function (nmc) {
+let primary_conn = nmc.get_primary_connection();
+let primary_devices = primary_conn.get_devices();
+let primary_ifcs = [];
+
Bug#935759: marked as pending in postgresql
Control: tag -1 pending Hello, Bug #935759 in postgresql 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/postgresql/postgresql/commit/e179187ee3f0ea240280bdc4e420f20f04a206bd New upstream version. * New upstream version. This is the next-to-last release of the 9.4 series. Please upgrade to a newer PostgreSQL major version. * Register debconf templates in postinst. (Closes: #935759) (this message was generated automatically) -- Greetings https://bugs.debian.org/935759
Processed: Bug#935759 marked as pending in postgresql
Processing control commands: > tag -1 pending Bug #935759 [postgresql-9.4] postgresql-9.4: fails to purge: RET=10 postgresql-9.4/postrm_purge_data doesn't exist Added tag(s) pending. -- 935759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935759 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#936015: marked as done (ceph: CVE-2019-10222)
Your message dated Mon, 18 Nov 2019 15:35:48 +0100 with message-id and subject line Fixed in 14.2.4-1 has caused the Debian Bug report #936015, regarding ceph: CVE-2019-10222 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.) -- 936015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936015 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ceph Version: 12.2.11+dfsg1-2.1 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://github.com/ceph/ceph/pull/2996 Hi, The following vulnerability was published for ceph. CVE-2019-10222[0]: unauthenticated clients can crash RGW For the 12.2.x series this is only triggerable if an experimental feature is enabled. Thus I think this does not warrant a DSA but would be potentially nice to have fixed in the next point release. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-10222 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10222 [1] https://github.com/ceph/ceph/pull/2996 [2] https://www.openwall.com/lists/oss-security/2019/08/28/9 Regards, Salvatore --- End Message --- --- Begin Message --- Version: 14.2.4-1 Forgot to mention that bug in the changelog unfortunately. ceph (14.2.4-1) unstable; urgency=medium * Uploading 14.2.4 to Debian. (Closes: #936282, #943961, #940854, #942733) * Adding myself to Uploaders * Merging the work done in Ubuntu. [ Dariusz Gadomski ] * d/p/issue37490.patch: Cherry pick fix to optimize LVM queries in ceph-volume, resolving performance issues in systems under heavy load or with large numbers of disks (LP: #1850754). [ James Page ] * d/p/issue40114.patch: Cherry pick endian fixes to resolve issues using Ceph on big-endian architectures such as s390x (LP: #1851290). * New upstream release (LP: #1850901): - d/p/more-py3-compat.patch,ceph-volume-wait-for-lvs.patch, ceph-volume-wait-for-lvs.patch: Drop, included upstream. - d/p/bluefs-use-uint64_t-for-len.patch: Cherry pick fix to resolve FTBFS on 32 bit architectures. * d/rules: Disable SPDK support as this generates a build which has a minimum CPU baseline of 'corei7' on x86_64 which is not compatible with older CPU's (LP: #1842020). * d/p/issue40781.patch: Cherry pick fix for py3 compatibility in ceph- crash. [ Eric Desrochers ] * Ensure that daemons are not automatically restarted during package upgrades (LP: #1840347): - d/rules: Use "--no-restart-after-upgrade" and "--no-stop-on-upgrade" instead of "--no-restart-on-upgrade". - d/rules: Drop exclusion for ceph-[osd,mon,mds] for restarts. [ Jesse Williamson ] * d/p/civetweb-755-1.8-somaxconn-configurable*.patch: Backport changes to civetweb to allow tuning of SOMAXCONN in Ceph RADOS Gateway deployments (LP: #1838109). [ James Page ] * d/p/ceph-volume-wait-for-lvs.patch: Cherry pick inflight fix to ensure that required wal and db devices are present before activating OSD's (LP: #1828617). [ Steve Beattie ] * SECURITY UPDATE: RADOS gateway remote denial of service - d/p/CVE-2019-10222.patch: rgw: asio: check the remote endpoint before processing requests. - CVE-2019-10222 [ James Page ] * New upstream release. * d/p/fix-py3-encoding-fsid.patch: Drop, no longer required. * d/p/pybind-auto-encode-decode-cstr.patch: Drop, reverted upstream. * d/p/fix-py3-encoding-fsid.patch: Cherry pick correct fix to resolve FSID encoding issues under Python 3 (LP: #1833079). * d/p/pybind-auto-encode-decode-cstr.patch: Cherry pick fix to ensure that encoding/decoding of strings is correctly performed under Python 3 (LP: #1833079). * New upstream release. * d/p/misc-32-bit-fixes.patch: Drop, included upstream. * d/p/py37-compat.patch: Drop, included upstream. * d/p/collections.abc-compat.patch: Drop, included in release. * d/p/*: Refresh. * d/*: Re-sync packaging with upstream for Nautilus release. * d/control,ceph-test.*,rules: Disable build of test binaries, drop ceph-test binary package (reduce build size). * d/control,rules: Use system boost libraries (reduce build time). * d/control:
Bug#944675: udev: Keyboard and mouse not working in X.org with udev 243-5
> > Can you all check if you have the i386 version of libinput-bin installed > > (by accident) on your amd64 system? > > > > .. and if installing the amd64 version via > apt install libinput-bin:amd64 > helps > Looking into aptitude logs and yes, at some point during investigation I replaced i386 version of libinput-bin with amd64 version. I tried to reproduce the issue (with udev 243-7): 1. aptitude install libinput:i386 (conflicting with amd64 version, confirmed that I want to replace it) 2. reboot 3. test - keyboard and mouse not working in lightdm 4. aptitude install libinput:amd64 (again conflict with i386 version) 5. reboot 6. test - everything works fine -- Peter
Bug#942804: marked as done (fix build with python3.8)
Your message dated Mon, 18 Nov 2019 13:04:49 + with message-id and subject line Bug#942804: fixed in petsc4py 3.11.0-3 has caused the Debian Bug report #942804, regarding fix build with python3.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 942804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942804 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:petsc4py Version: 3.11.0-2 Severity: important Tags: sid bullseye patch User: debian-pyt...@lists.debian.org Usertags: python3.8 fix petsc4py for python 3.8, patch at http://launchpadlibrarian.net/447877062/petsc4py_3.11.0-2build1_3.11.0-2ubuntu1.diff.gz upstream 3.12 also has the fix. --- End Message --- --- Begin Message --- Source: petsc4py Source-Version: 3.11.0-3 We believe that the bug you reported is fixed in the latest version of petsc4py, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated petsc4py package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Nov 2019 17:31:02 +0800 Source: petsc4py Architecture: source Version: 3.11.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Drew Parsons Closes: 942804 Changes: petsc4py (3.11.0-3) unstable; urgency=medium . * drop patch demo-wrap-swig-compile.patch: HDF5 handling fixed by PETSc upstream commit 6a0bd75 (in petsc 3.11.3+dfsg1-2) * debian patch python3.8-fix.diff fixes build for Python 3.8. Closes: #942804. Checksums-Sha1: ed2a646b3472f1bb4315de8d72f9dc6ea46b5a70 2516 petsc4py_3.11.0-3.dsc 82586f7d32c98ecde5b10c1f6338b34eea898402 10120 petsc4py_3.11.0-3.debian.tar.xz Checksums-Sha256: 22718428f283479089eb9a5e41cfad77066e05c0afbc87be835ae2c05e946d45 2516 petsc4py_3.11.0-3.dsc ebbd9c92cc6c0e8e0d9f6628920f61ff1391d614cc687a5e1cebad7ebed003b7 10120 petsc4py_3.11.0-3.debian.tar.xz Files: 699e8ab34448c4093e68ab3fcf47440a 2516 python optional petsc4py_3.11.0-3.dsc 6f6d46b8020fd7d98f77165fc888df32 10120 python optional petsc4py_3.11.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAl3SkpQACgkQVz7x5L1a Afp6PBAAtDIxJGyU+bGdHte/06kXazs+7URX22CakpEL2SK5cRAAUuOIxL//6Q30 sEJSVagVETXrPYX/qJAOF0WmIxM2chaLifyIJiWX39D999lDvZDU6WAXpnRyVEk9 6xp10/che8yJVMXUq3tDA0Cb6tmhTritwRnvOaHhR1KzEZgRKYgJLPHATIVoL0tc n5Uk9L3hsqvjGXDnswgcefaTYyfdGnmcMGn+KVJYCpQG6N3R/3hPyebNLoHHIsgC A49QS6zX8lJdBDbE5+zLZYanJbp44lMGJzFF8hA2ciF3B/O4714+JTTHRafFk80v Fx53M0BaagwqFYOUsBMsMKIyvb9v8Dkop+9aP41bJMNTBrBL34giVrSjEohdi0rs 8DAkf4f+mwz/eoUEubHrr2lj5pAXaiYS+KWYdr1B8z/vz8uVe/DT64nW1RwgE2yU Hf9bNkeRX+q1rhb1aFAennG7LL9otQwvgXoltYEQfDbBZIoA1qo/Or2Ylce01AKw 7pdqyOnIUolnxjZUjlz1fJVN0V+5AZmMJ/T6c8JUepb8smQ213imTV4sVItEtAJe aWIw9gIFcQaAUblA/JNd5IkM/5Y1kGgjE6aUIXbsz8p459X1wmcwRo+EM++EeJL3 XE5OT3YytE4yeOJqvndy25FKRzg6UfjqkD+pxN+nCkD2h+Dn8Cc= =1Vr6 -END PGP SIGNATURE End Message ---
Bug#944249: [Pkg-emacsen-addons] Bug#944249: gnuplot-mode does not work with emacs26
Agustin Martin writes: > > Hi, David, > >> That's not loaded by elpa packages. > > But AFAIK it should be loaded by Emacs, Perhaps. Team packages don't use these startup files anymore. Most of the content (updating load paths in particular) is handled more reliably by package.el generated autoload files. > >> The general approach is to add an autoload cookie to set >> auto-mode-alist. See "HINTS" in dh_elpa(1). > > I was looking at it and noticed the autoloads part, but nothing about > `auto-mode-alist'. Where is it? > See "Other customizations"
Bug#933832: enigmail now broken in stable due to release of thunderbird 68 through security
Package: enigmail Version: 2.0.12+ds1-1~deb10u1 Followup-For: Bug #933832 Dear Maintainer, today I upgraded my system and thunderbird was going to be upgraded to version 68 through security. This broke the dependency for the current enigmail version in stable. I read in the referred bug 933832 that a new version of enigmail is soon to get released. However I think the severity changed now since it's affecting stable, I'd like to raise the attention and asking when will the new version of enigmail be available through upgrading stable. Thanks - Alex -- System Information: Debian Release: 10.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages enigmail depends on: ii gnupg2.2.12-1+deb10u1 ii gnupg-agent 2.2.12-1+deb10u1 ii gpg-agent [gnupg-agent] 2.2.12-1+deb10u1 ii thunderbird 1:68.2.2-1~deb10u1 Versions of packages enigmail recommends: ii pinentry-gnome3 [pinentry-x11] 1.1.0-2 enigmail suggests no packages.
Bug#945013: haskell-gnuidn: Removal notice: unmaintained
Source: haskell-gnuidn Severity: serious This package seems to be unmaintained upstream[1]. Its last upload was at 2015, and the home page[2] returns 404. [1] https://hackage.haskell.org/package/gnuidn [2] https://john-millikin.com/software/haskell-gnuidn/ It is also not on Stackage and has no reverse dependencies (other than haskell-network-protocol-xmpp, but see #945012). I intend to remove this package. If there is a good reason to keep it, please close the bug. -- Ilias
Bug#944249: [Pkg-emacsen-addons] Bug#944249: gnuplot-mode does not work with emacs26
On Mon, Nov 18, 2019 at 07:28:45AM -0400, David Bremner wrote: > Dima Kogan writes: > > > Thanks for the patches, Agustin. I just tried it out. Works for the most > > part. One thing that doesn't work for me is (gnuplot-mode) being > > executed when opening a .gp file. You added this to the package, and the > > dh-elpa machinery is creating the appropriate file: > > > > /etc/emacs/site-start.d/50elpa-gnuplot-mode.el > > > > I don't think this is being evaluated, however. Is it working for you? > Hi, David, > That's not loaded by elpa packages. But AFAIK it should be loaded by Emacs, > The general approach is to add an autoload cookie to set > auto-mode-alist. See "HINTS" in dh_elpa(1). I was looking at it and noticed the autoloads part, but nothing about `auto-mode-alist'. Where is it? > Of course the usual cautions > about auto-mode-alist apply, in particular there's no nice way to resolve > conflicts with other packages (e.g. pari-gp) that might want to use the > same suffix. By the way, previous emacsen-startup file also used the .gnuplot extension. Regards, -- Agustin
Bug#945012: haskell-network-protocol-xmpp: Removal notice: unmaintained
Source: haskell-network-protocol-xmpp Severity: serious This package seems to be unmaintained upstream[1]. Its last upload was at 2015, and the home page[2] returns 404. [1] https://hackage.haskell.org/package/network-protocol-xmpp [2] https://john-millikin.com/software/haskell-xmpp/ It is also not on Stackage and has no reverse dependencies. I intend to remove this package. If there is a good reason to keep it, please close the bug. -- Ilias
Bug#945011: haskell-cabal-helper: Removal notice: unused Haskell library
Source: haskell-cabal-helper Severity: serious This Haskell library is not part of Buster, is not on Stackage and is already ignored on our package-plan. I intend to remove this package. If there is a good reason to keep it, please close the bug. -- Ilias
Bug#944249: gnuplot-mode does not work with emacs26
On Sun, Nov 17, 2019 at 10:52:47PM -0800, Dima Kogan wrote: > Thanks for the patches, Agustin. I just tried it out. Works for the most > part. One thing that doesn't work for me is (gnuplot-mode) being > executed when opening a .gp file. You added this to the package, and the > dh-elpa machinery is creating the appropriate file: > > /etc/emacs/site-start.d/50elpa-gnuplot-mode.el > > I don't think this is being evaluated, however. Is it working for you? Hello, thanks for looking at this. It is working for me. I reviewed again my ~/.emacs file and did not see anything active that may mess up with this. > Do you know at which point in the emacs startup sequence this is > sourced? In my box, Emacs messages buffer shows ... Loading /etc/emacs/site-start.d/50dictionaries-common.el (source)...done Loading /etc/emacs/site-start.d/50elpa-gnuplot-mode.el (source)...done Loading /etc/emacs/site-start.d/50flim.el (source)...done ... > Is it always supposed to be sourced? What about 'emacs -q'? Or > 'emacs -Q'? That snippet will not always be sourced, It will not be sourced with "emacs -Q" or "emacs --no-site-file" It will be sourced with "emacs --q", but I get an error here ... Loading /etc/emacs/site-start.d/50dictionaries-common.el (source)...done Loading /etc/emacs/site-start.d/50elpa-gnuplot-mode.el (source)...done Loading /etc/emacs/site-start.d/50flim.el (source)...done ... File mode specification error: (void-function gnuplot-mode) ... Another thing. It is probably too late for this, but I tried gnuplot-mode for XEmacs (unsupported by elpa). Just needed to add a couple of lines with a compatibility function (eval-and-compile ;; Protect against declare-function undefined in XEmacs (unless (fboundp 'declare-function) (defmacro declare-function ( r and load .el files manually to have it working. No apparent problems in my quick test (plotting sin(x)). I wonder if gnuplot-mode should have preserved XEmacs compatibility and thus not migrate to elpa. Anyhow, seems that nobody complained and even I had to install XEmacs just for this check, so this seems no longer an issue. Regards, -- Agustin
Bug#945010: ghc-mod: Removal notice: unmaintained
Source: ghc-mod Severity: serious This package is no longer maintained upstream. For more information see: https://github.com/DanielG/ghc-mod#legacy I intend to remove this package. If there is a good reason to keep it, please close the bug. -- Ilias
Bug#945007: haskell-hmt: Removal notice: unused Haskell library
Source: haskell-hmt Severity: serious This Haskell library is not part of Buster, has no reverse dependencies, is not on Stackage and is already ignored on our package-plan. I intend to remove this package. If there is a good reason to keep it, please close the bug. -- Ilias
Bug#944249: [Pkg-emacsen-addons] Bug#944249: gnuplot-mode does not work with emacs26
Dima Kogan writes: > Thanks for the patches, Agustin. I just tried it out. Works for the most > part. One thing that doesn't work for me is (gnuplot-mode) being > executed when opening a .gp file. You added this to the package, and the > dh-elpa machinery is creating the appropriate file: > > /etc/emacs/site-start.d/50elpa-gnuplot-mode.el > > I don't think this is being evaluated, however. Is it working for you? That's not loaded by elpa packages. The general approach is to add an autoload cookie to set auto-mode-alist. See "HINTS" in dh_elpa(1). Of course the usual cautions about auto-mode-alist apply, in particular there's no nice way to resolve conflicts with other packages (e.g. pari-gp) that might want to use the same suffix.
Bug#944675: udev: Keyboard and mouse not working in X.org with udev 243-5
Am 18.11.19 um 11:24 schrieb Michael Biebl: > Can you all check if you have the i386 version of libinput-bin installed > (by accident) on your amd64 system? > .. and if installing the amd64 version via apt install libinput-bin:amd64 helps -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#944675: udev: Keyboard and mouse not working in X.org with udev 243-5
Can you all check if you have the i386 version of libinput-bin installed (by accident) on your amd64 system? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: python-iptables ftbfs in unstable: segfault
Processing commands for cont...@bugs.debian.org:
> fixed 941650 3.7.5~rc1-2
Bug #941650 {Done: Matthias Klose } [src:python3.7]
python-iptables ftbfs in unstable: segfault
Marked as fixed in versions python3.7/3.7.5~rc1-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
941650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#944946: marked as done (python-fuse: needs an explicit build dependency on dh-python)
Your message dated Mon, 18 Nov 2019 10:05:57 + with message-id and subject line Bug#944946: fixed in python-fuse 2:1.0.0-2 has caused the Debian Bug report #944946, regarding python-fuse: needs an explicit build dependency on dh-python 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.) -- 944946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944946 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-fuse Version: 2:1.0.0-1 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python. --- End Message --- --- Begin Message --- Source: python-fuse Source-Version: 2:1.0.0-2 We believe that the bug you reported is fixed in the latest version of python-fuse, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 944...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastien Delafond (supplier of updated python-fuse package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 18 Nov 2019 10:45:39 +0100 Source: python-fuse Architecture: source Version: 2:1.0.0-2 Distribution: unstable Urgency: medium Maintainer: Sebastien Delafond Changed-By: Sebastien Delafond Closes: 944946 Changes: python-fuse (2:1.0.0-2) unstable; urgency=medium . * Add explicit build dependency on dh-python (Closes: #944946) * Bump-up Standards-Version Checksums-Sha1: e958a04afd43dbdb41750d3a42f7456eb8da36e9 1684 python-fuse_1.0.0-2.dsc 4a60fd511e7ccbe0832ec6e492cd4b77b9aef886 4412 python-fuse_1.0.0-2.debian.tar.xz de20975bade1f36e0261f47ca94121885893e7d4 8117 python-fuse_1.0.0-2_amd64.buildinfo Checksums-Sha256: 6663440c4b41db01a0feb02b63d3acaf8c822ecc87396163b0df1919029a6a2a 1684 python-fuse_1.0.0-2.dsc c0642ebbf0d25344388bf6e048ad56a89b94bb6d5ce69ba5b4d67d87e6ad5788 4412 python-fuse_1.0.0-2.debian.tar.xz 477fcbfdb4f3a666e64b8f3089468038f657215d0969f91f5f532bada57e9cd6 8117 python-fuse_1.0.0-2_amd64.buildinfo Files: d1d794fe90cd6f2e46262dfd54cfec13 1684 python optional python-fuse_1.0.0-2.dsc 777fd5d7966eee3ef8faf0dc859609ae 4412 python optional python-fuse_1.0.0-2.debian.tar.xz 77cc97eaa389c2b2f8ead91844de523e 8117 python optional python-fuse_1.0.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEAqSkbVtrXP4xJMh3EL6Jg/PVnWQFAl3SaTAACgkQEL6Jg/PV nWRHHQgAu7jkqgKEWQHhgNqbHWYp5Y4UwyiR5YjblHla9iDijFzmad34LlrFif+m anxSFqBhPy0/VP5WCmCwbpF95Mq1f7K6eKknwmRuizoOCcnLome7JjzTXyvaewuZ Cve9iaRCk4YOnnxArDJcaJ6AUkVbT23z2E4MfyjQXS650TtZoQRZOt0tP7aVIvbM sXAy+RhQNvLGBHF/ciz9dSQi60OauhxlLJnALcGwYmSpqjozI9s5dHKyyHgSHaL1 jHiow9tLl1gV96i1N+cfkEANlMSem5ZYeJLfg7/8AoWpzB9vzXscc/RgYhlCura8 Z5quLbSUOxeATdqbmsqzrTa0SOxIiw== =iXlg -END PGP SIGNATURE End Message ---
Processed: python-iptables ftbfs in unstable: segfault
Processing commands for cont...@bugs.debian.org:
> fixed 941650 3.7.5~rc1-2thanks
Bug #941650 {Done: Matthias Klose } [src:python3.7]
python-iptables ftbfs in unstable: segfault
The source 'python3.7' and version '3.7.5~rc1-2thanks' do not appear to match
any binary packages
Marked as fixed in versions python3.7/3.7.5~rc1-2thanks.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
941650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#944949: dbus-python: needs an explicit build dependency on dh-python
I've given back dbus-python now that python-defaults 2.7.17-2 has built, and all seem fine.
Processed: python-iptables ftbfs in unstable: segfault
Processing commands for cont...@bugs.debian.org:
> reassign 941650 src:python3.7 3.7.5~rc1-1
Bug #941650 {Done: Matthias Klose } [src:python-iptables]
python-iptables ftbfs in unstable: segfault
Bug reassigned from package 'src:python-iptables' to 'src:python3.7'.
No longer marked as found in versions python-iptables/0.14.0~ds-1.
No longer marked as fixed in versions python3.7/3.7.5~rc1-2.
Bug #941650 {Done: Matthias Klose } [src:python3.7]
python-iptables ftbfs in unstable: segfault
Marked as found in versions python3.7/3.7.5~rc1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
941650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#945001: grub-efi-amd64: GRUB-EFI messes up boot variables
Package: grub-efi-amd64
Version: 2.04-4
Severity: critical
Dear Maintainer,
I have multiple disk with different operating systems each with its own
bootloader.
Updating GRUB delete all existing UEFI variables BOOT and put in
some values that do not make any sense for my system. I had a lot of
trouble to get my system running again.
As this "makes unrelated software on the system (or the whole system)
break" I mark this error as critical.
One of the deleted entries was my second instance of Debian Buster
installed on device /dev/sda. GRUB did neither create a BOOT
variable for it nor did it add an entry to grub.conf.
I do not expect GRUB to ever touch my UEFI variables without my explicit
consent. Please, provide a dialogue.
Bug report 913916 seems to be related but I am not sure if it is
reporting the same issue.
Best regards
Heinrich Schuchardt
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/mapper/LVM1-root / ext4 rw,relatime,errors=remount-ro 0 0
/dev/nvme0n1p2 /boot ext2 rw,relatime 0 0
/dev/mapper/LVM1-home /home ext4 rw,relatime 0 0
/dev/nvme0n1p1 /boot/efi vfat
rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
0 0
*** END /proc/mounts
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod lvm
insmod ext2
set
root='lvmid/z7Vz2e-hUSn-2wTk-3QEB-n2Eu-642O-EFG8XU/GuEKrb-SY50-1B2I-zLFX-pZef-iGBh-joFZ5o'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
--hint='lvmid/z7Vz2e-hUSn-2wTk-3QEB-n2Eu-642O-EFG8XU/GuEKrb-SY50-1B2I-zLFX-pZef-iGBh-joFZ5o'
b7e77dc3-85a0-4768-b18f-2774d561e90b
else
search --no-floppy --fs-uuid --set=root
b7e77dc3-85a0-4768-b18f-2774d561e90b
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod lvm
insmod ext2
set
root='lvmid/z7Vz2e-hUSn-2wTk-3QEB-n2Eu-642O-EFG8XU/GuEKrb-SY50-1B2I-zLFX-pZef-iGBh-joFZ5o'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
--hint='lvmid/z7Vz2e-hUSn-2wTk-3QEB-n2Eu-642O-EFG8XU/GuEKrb-SY50-1B2I-zLFX-pZef-iGBh-joFZ5o'
b7e77dc3-85a0-4768-b18f-2774d561e90b
else
search --no-floppy --fs-uuid --set=root
b7e77dc3-85a0-4768-b18f-2774d561e90b
fi
insmod png
if background_image
/usr/share/desktop-base/futureprototype-theme/grub/grub-4x3.png; then
set color_normal=white/black
set color_highlight=black/white
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class
gnu --class os $menuentry_id_option
'gnulinux-simple-b7e77dc3-85a0-4768-b18f-2774d561e90b' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
1a42361e-b451-4f35-8bcc-4af14900c379
else
search --no-floppy --fs-uuid --set=root
1a42361e-b451-4f35-8bcc-4af14900c379
fi
echo'Loading Linux 5.2.0-3-amd64 ...'
linux /vmlinuz-5.2.0-3-amd64 root=/dev/mapper/LVM1-root ro
Bug#891493: marked as done (numix-gtk-theme: Undocumented and very likely also broken Breaks against murrine-themes since 2.6.7-2)
Your message dated Mon, 18 Nov 2019 09:04:28 + with message-id and subject line Bug#891493: fixed in numix-gtk-theme 2.6.7-5 has caused the Debian Bug report #891493, regarding numix-gtk-theme: Undocumented and very likely also broken Breaks against murrine-themes since 2.6.7-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 891493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: numix-gtk-theme Version: 2.6.7-2 Since 2.6.7-2, numix-gtk-theme has a "Breaks: murrine-themes (<= 0.98.11)" without any mentioning (and especially without giving a reason) in debian/changelog. According to the commit message in https://salsa.debian.org/desktop-themes-team/numix-gtk-theme/commit/6eb0c14fb93ef740ef13e59551178726d4efd9b5 it's because of https://bugs.debian.org/623783 and https://bugs.debian.org/838994. But besides "Ugly workaround for #623783 and #838994" there's no real reason given, why this Breaks should workaround any of these two bugs. And I don't find any reason for this change in #623783. In #838994 there is the following dicussion, citing from the mail of Yves-Alexis Perez of 28 Sep 2016 at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838994#20: > > > > NB! I notice the recommendation is versioned. If reason for > > > > that is to avoid older versions being outright broken (e.g. due > > > > to bug#827134), then it does not work as intended (only > > > > versioned _depends_ is certain to be obeyed). Use a versioned > > > > _breaks_ instead. > > > > > > so something like: > > > > > > Recommends: murrine-themes > > > Breaks: murrine-themes (<< 0.98.1) ^^ > > > > Specifically addressing the versioning, yes. Does not address the issue > > on topic for this bugreport. > > In any case, I really don't believe that's something important enough > to lose time on it (specifically, I won't). As already stated, just > remove the packages you don't want. Please note that there is no talk about 0.98.11 but 0.98.1! Additionally, the mentioned Recommends of gtk2-engines-murrine on murrine-themes (which the suggested Breaks should complement) is versioned as ">= 0.98". Currently installing numix-gtk-theme wants to uninstall the _current_ version of murrine-themes from unstable which does not have any RC bug and which I hence does not consider broken enough to be kicked out by such a Breaks. This all leads me to the assumption that someone indeed did not "lose enough time on it" and added a Breaks against the wrong version (0.98.11 instead of 0.98.1) _and_ forgot to document it properly, too. If I'm right with this assumption, this would be a bug of severity serious and it should be fixed as follows: Fix the Breaks against murrine-themes themes to be versioned as "(<< 0.98)" or "(<<0.98.1)" and retro-actively add the missing changelog entry to 2.6.7-2. Or just drop it all again, as murrine-themes 0.98.1 and 0.98 were uploads from 2011 (and even wheezy/oldoldstable has 0.98.4) and there's probably no reason to add a Breaks against them nowadays. Or explain indepth why this Breaks should actually fix or workaround anything. It's not obvious at all and seems to do more harm than good. (If just the explaination is missing, it's probably of severity normal or minor.) -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), (111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), (105, 'experimental-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages numix-gtk-theme depends on: ii gtk2-engines-murrine 0.98.2-2 ii numix-icon-theme 0~20171225-1 numix-gtk-theme recommends no packages. numix-gtk-theme suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: numix-gtk-theme Source-Version: 2.6.7-5 We believe that the bug you reported is fixed in the latest version of numix-gtk-theme, 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 891...@bugs.debian.org, and the maintainer will
Bug#944828: marked as done (salt-pylint (build-)depends on cruft package.)
Your message dated Mon, 18 Nov 2019 09:04:53 + with message-id and subject line Bug#944828: fixed in salt-pylint 2019.6.7-2 has caused the Debian Bug report #944828, regarding salt-pylint (build-)depends on cruft 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.) -- 944828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: salt-pylint Version: 0.14.1-1 Severity: serious Tags: bullseye, sid, patch python3-saltpylint depends on and the salt-pylint source package build-depends on the pylint3 binary package which is no longer built by the pylint source package. The python 3 pylint functionality is now in the pylint binary package. The build-dependency needs to be fixed manually, the binary dependency seems to follow along automatically once the built-dependency is fixed and the package rebuilt. Debdiff attatched, no intent to NMU. diff -Nru salt-pylint-2019.6.7/debian/changelog salt-pylint-2019.6.7/debian/changelog --- salt-pylint-2019.6.7/debian/changelog 2019-09-05 08:33:00.0 + +++ salt-pylint-2019.6.7/debian/changelog 2019-11-16 02:19:38.0 + @@ -1,3 +1,10 @@ +salt-pylint (2019.6.7-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Update build-dependency for pylint3->pylint package rename. + + -- Peter Michael Green Sat, 16 Nov 2019 02:19:38 + + salt-pylint (2019.6.7-1) unstable; urgency=medium * New upstream release. diff -Nru salt-pylint-2019.6.7/debian/control salt-pylint-2019.6.7/debian/control --- salt-pylint-2019.6.7/debian/control 2019-09-05 08:32:07.0 + +++ salt-pylint-2019.6.7/debian/control 2019-11-16 02:19:35.0 + @@ -5,7 +5,7 @@ Priority: optional Build-Depends: debhelper-compat (= 12), dh-python, - pylint3, + pylint (>= 2.2.2-2), python3-all, python3-libmodernize, python3-pycodestyle (>= 2.4), --- End Message --- --- Begin Message --- Source: salt-pylint Source-Version: 2019.6.7-2 We believe that the bug you reported is fixed in the latest version of salt-pylint, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 944...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Benjamin Drung (supplier of updated salt-pylint package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 18 Nov 2019 09:43:09 +0100 Source: salt-pylint Architecture: source Version: 2019.6.7-2 Distribution: unstable Urgency: medium Maintainer: Debian Salt Team Changed-By: Benjamin Drung Closes: 944828 Changes: salt-pylint (2019.6.7-2) unstable; urgency=medium . * Rename build dependency pylint3 to pylint (Closes: #944828) * Bump Standards-Version to 4.4.1 * Set Rules-Requires-Root: no Checksums-Sha1: f0a040e88d7ba114eb20a6795f03c6dcc15b1980 2144 salt-pylint_2019.6.7-2.dsc dae606828681b2b2ffd518a84cee3ef1f1e924d2 2932 salt-pylint_2019.6.7-2.debian.tar.xz a5318a8d08ba15379c5902bcc3c48be7d2965916 6950 salt-pylint_2019.6.7-2_source.buildinfo Checksums-Sha256: 485c6bbc136acd98f3c7a983a5a8098d090ed8745056274ae35da35da74d2abb 2144 salt-pylint_2019.6.7-2.dsc 45081c36373cb963e30d7af648e8c1725e22979148b6e03f4a7e14019b702a48 2932 salt-pylint_2019.6.7-2.debian.tar.xz 0497db54e79d90620ea6e2827182eb0ada5df80937f7ebd6c37133fb74003478 6950 salt-pylint_2019.6.7-2_source.buildinfo Files: 44e1bc93e47f478e436078c911ec60ff 2144 python optional salt-pylint_2019.6.7-2.dsc fa70bb9baaa789c08beb66a70c625360 2932 python optional salt-pylint_2019.6.7-2.debian.tar.xz 2027ca9c867bc36ae69805aa31d7fb4b 6950 python optional salt-pylint_2019.6.7-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE5/q3CzlQJ15towl13YzVpd6MfnoFAl3SWeIACgkQ3YzVpd6M fnpquw/9HUdQZzRoaMnqmCOoYGYbWiaigQN+1AeclKwFN9hFuwlupWkjLqA2iQf7 NuZK+qkGUcl6ktVwvZgj0WOaHqZFuoJzxneKfUpaIsGXUZ9tNeROGMTeR/DVJAX5 n1lTGOsJtUVKJF2l3WJYtBcQXwLS5pRQ6yPaDn0Q72xejBThjHaGI/6L+iFDbEPm joU33aZtKoS6zB723tRlW43QyIOJb/Zut8b2dcCruL0oNuTdBACNF4wLkUVwtHT/
Bug#838994: unresolved gtk2-engines-murrine situation (was: numix-gtk-theme: Undocumented and very likely also broken Breaks against murrine-themes since 2.6.7-2)
Hi Yves-Alexis, On So 17 Nov 2019 20:43:40 CET, Yves-Alexis Perez wrote: On Sun, 2019-11-17 at 11:00 +, Mike Gabriel wrote: If you plan to drop maintenance sooner or later anyway, then please state that asap (packages are in deferred-15 from today again), so that I can change the uploads and make these bugs go away without introducing a virtual package. Let's be realistic, I won't have time / priority for those themes, so I'm ok with dropping maintenance even right now. So go ahead with your preferred plan. I have moved maintenance for the gtk2-engines-murrine theme to the Debian Desktop Themes Team now. Thanks for stepping back on this. Thanks for all the previous contributions. If there are more theming packages, that you maintainer-only maintain and that you have no time for doing this with sufficient priority, please consider orphaning them (or list them in a reply to this mail, and I will move the listed src:pkgs over to the themes team context). Thanks+Greets, Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgp9JvnXD7CkW.pgp Description: Digitale PGP-Signatur
Bug#944949: dbus-python: needs an explicit build dependency on dh-python
On Sun, 17 Nov 2019 at 19:07:39 +, Matthias Klose wrote: >* Remove dh-python dependency from python3-all and python3-dev packages. > Packages should build depend on dh-python or dh-sequence-python3 instead. > > Please add an explicit build dependency on dh-python. On Sun, 17 Nov 2019 at 19:53:48 +, Simon McVittie wrote: > As far as I can see it's been explicit since 2015. Is anything more > needed here? More detail: dbus-python has: Build-Depends: ... dh-python, dh-sequence-python2 , dh-sequence-python3, so I think everything is as it should be. Is this bug report a false positive that can be closed? If not, I must be missing something: please clarify what is wrong? Thanks, smcv
Bug#838994: marked as done (gtk2-engines-murrine: wrongly recommends murrine-themes)
Your message dated Mon, 18 Nov 2019 08:49:33 +
with message-id
and subject line Bug#838994: fixed in gtk2-engines-murrine 0.98.2-3
has caused the Debian Bug report #838994,
regarding gtk2-engines-murrine: wrongly recommends murrine-themes
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.)
--
838994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gtk2-engines-murrine
Version: 0.98.1.1-6
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I want to install greybird-gtk-theme, and only that theme. But due to
gtk2-engines-murrine recommending murrine-themes, effectively I get a
bunch of themes when I wanted only one.
Package relationships are _directional_:
Having murrine-themes recommend greybird-gtk-theme is sensible, because
(some of) its contents has little use without the contents of that other
package.
Having gtk2-engines-murrine recommend recommend murrine-themes is less
sensible, as its contents is perfectly usable without the contents of
that other package.
What would be sensible is to a) drop gtk2-engines-murrine recommends on
murrine-themes, and b) have murrine-themes declare that it _enhances_
gtk2-engines-murrine (i.e. a reverse suggestion).
NB! I notice the recommendation is versioned. If reason for that is to
avoid older versions being outright broken (e.g. due to bug#827134),
then it does not work as intended (only versioned _depends_ is certain
to be obeyed). Use a versioned _breaks_ instead.
- Jonas
-BEGIN PGP SIGNATURE-
iQIcBAEBCAAGBQJX6oAuAAoJECx8MUbBoAEhj5cP/0307iXZ8YPIJkIS/4A4PgHV
y2i4wWUo9gmcsR6NMA/MdoD05bCvv7sizb31uDvpSLEzC0sMa9rsKB3DT1qYIPMY
zP1DrdSjw9RaZRjzjJmESHGx9o9F5xFAXlv/rW+yVWy55o5UMBpty27UP70lap4E
tr0a9+P8KYnLUDmqXCSttLwc7ZGyYnQ4XcFcge1ToTCdPwCmUTBeVLSlZHCqTjpM
ACpuEhyc8gOied0o5DsYiTEy4vBBHWzZgB/IZ5Ces2XcWe13i+R+sz2RNFK9UrCS
27mh98Tfw+PpZ22xbKSx0B/GHNAPojo1s5GrtKlmQFGa7euq/qPbl2V49mAYYXvb
g36ycQWXeeEybhvR95xOYF6y9JMoB3QLG1cl/dxcGNKlR1bqqXacgGXMfnMzECW6
PG7FNsBgRf7jmN6tQ+LpOp9trAupzOe4YbpiSw4meIFk8Tk7l7qK3isVYAT8TcJj
ynmgE21ueq+w4erJ8m1INVVXGi8+B1wDTsBY0ku6bdQf8ng7/PMUpCK6u/FtQKJx
MF9iLFz1tyNtPziNCMrVlS6zKC3emrnTrX9tqmP3fz0WBOCjahifADJrIMna0Bfi
a0ieNSpuCKjA94wNV4TxfEZFycr4jqqN2mBeH2JSbDRk8uIzJ6rTkkxOpDKhVoCF
2GvIntr5fxzkzXdoU7h9
=WvlS
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: gtk2-engines-murrine
Source-Version: 0.98.2-3
We believe that the bug you reported is fixed in the latest version of
gtk2-engines-murrine, 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 838...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mike Gabriel (supplier of updated gtk2-engines-murrine
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 18 Nov 2019 09:32:18 +0100
Source: gtk2-engines-murrine
Architecture: source
Version: 0.98.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Desktop Theme Team
Changed-By: Mike Gabriel
Closes: 838994 883411
Changes:
gtk2-engines-murrine (0.98.2-3) unstable; urgency=medium
.
[ Mike Gabriel ]
* debian/{control,compat}:
+ Migrate to debhelper-compat notation. Bump DH compat level to version 12.
* debian/control:
+ New maintainer. Move maintenance over to Debian Desktop Themes Team.
Add myself as uploader.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838994#73
+ Downgrade from R to S (gtk2-engine-themes): murrine-themes. (Closes:
#838994).
+ Drop explicit D (gtk2-engines-murrine) on libgtk2.0-0. Thanks to Jeremy
Bicha for working on this. (Closes: #883411).
+ Add Rules-Requires-Root: field and set it to "no".
+ Bump Standards-Version: to 4.4.1. No changes needed.
+ Update Vcs-*: fields. Packaging Git has been resurrected on
salsa.debian.org.
* debian/*: White-space cleanup.
.
[ Jeremy Bicha ]
* debian/rules:
+ Exclude libgtk2.0-0 from dh_shlibdeps.
Checksums-Sha1:
97e8575c27269e000c130ca775dd1eca53775347 2065 gtk2-engines-murrine_0.98.2-3.dsc
4e9d1073ab99920d75e0db955561830303b8f6e8 3800
Bug#623783: marked as done (gtk2-engines-murrine: recommends murrine-themes needlessly)
Your message dated Mon, 18 Nov 2019 08:49:33 +
with message-id
and subject line Bug#838994: fixed in gtk2-engines-murrine 0.98.2-3
has caused the Debian Bug report #838994,
regarding gtk2-engines-murrine: recommends murrine-themes needlessly
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.)
--
838994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gtk2-engines-murrine
Severity: normal
gtk2-engines-murrine recommends murrine-themes, but murrine-themes depends on
gtk2-engines-murrine.
this seems like an unnecesary recommendation, and prevents another theme from
depending/recommending gtk2-engines-murrine without pulling in a very large
recommended package.
i'd think suggests might be more appropriate.
live well,
vagrant
--- End Message ---
--- Begin Message ---
Source: gtk2-engines-murrine
Source-Version: 0.98.2-3
We believe that the bug you reported is fixed in the latest version of
gtk2-engines-murrine, 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 838...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mike Gabriel (supplier of updated gtk2-engines-murrine
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 18 Nov 2019 09:32:18 +0100
Source: gtk2-engines-murrine
Architecture: source
Version: 0.98.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Desktop Theme Team
Changed-By: Mike Gabriel
Closes: 838994 883411
Changes:
gtk2-engines-murrine (0.98.2-3) unstable; urgency=medium
.
[ Mike Gabriel ]
* debian/{control,compat}:
+ Migrate to debhelper-compat notation. Bump DH compat level to version 12.
* debian/control:
+ New maintainer. Move maintenance over to Debian Desktop Themes Team.
Add myself as uploader.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838994#73
+ Downgrade from R to S (gtk2-engine-themes): murrine-themes. (Closes:
#838994).
+ Drop explicit D (gtk2-engines-murrine) on libgtk2.0-0. Thanks to Jeremy
Bicha for working on this. (Closes: #883411).
+ Add Rules-Requires-Root: field and set it to "no".
+ Bump Standards-Version: to 4.4.1. No changes needed.
+ Update Vcs-*: fields. Packaging Git has been resurrected on
salsa.debian.org.
* debian/*: White-space cleanup.
.
[ Jeremy Bicha ]
* debian/rules:
+ Exclude libgtk2.0-0 from dh_shlibdeps.
Checksums-Sha1:
97e8575c27269e000c130ca775dd1eca53775347 2065 gtk2-engines-murrine_0.98.2-3.dsc
4e9d1073ab99920d75e0db955561830303b8f6e8 3800
gtk2-engines-murrine_0.98.2-3.debian.tar.xz
80735b20726303abdbceaf3330a35a0b3ad8677d 12483
gtk2-engines-murrine_0.98.2-3_source.buildinfo
Checksums-Sha256:
f02e58b01803b1ff31c1bf9f6ae541a73c51da0839201e5213aa440f82f6f48e 2065
gtk2-engines-murrine_0.98.2-3.dsc
a9463234bbcfaba672c4c2d18dcda5e47fdd2c8342c1159b30b069881d9d3ed4 3800
gtk2-engines-murrine_0.98.2-3.debian.tar.xz
c30bd094509374d1de040e7571a21b1f2b916da13b2f00f5448c97a55a00a4f9 12483
gtk2-engines-murrine_0.98.2-3_source.buildinfo
Files:
23182763ffd70dd8dcc930726ba62c89 2065 x11 optional
gtk2-engines-murrine_0.98.2-3.dsc
6d474388753c54942dd7426394550936 3800 x11 optional
gtk2-engines-murrine_0.98.2-3.debian.tar.xz
d28a1157558c043c3594a2c96b289317 12483 x11 optional
gtk2-engines-murrine_0.98.2-3_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl3SWGwVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxMGIP/05SBAgxDYqfuYmakj0nq8AhSmLN
trTJ1B/PsZaKtymIbSvgoVWYQ00LJ+jdb2OSNDdxF9nYCT6Bi3c/H+qTzBjziEb+
cQrwjZwyPaP2F//JsZqwwkG0iY2Fm9ZpF2z4skRqc42jc5evFjNknvUfY5UBF1Nh
ai4qXTlV1hxv4fgJnOVjOGzxAzpukn21bLpnLEk78Aw+RalH7z9fowScg+sjzZS6
AorE+9Y9d/DSIhCSokZwdZIlR241O5mYkY9WxbVsFZG7bBHnZiuQm4ah2XUYiRTC
NJehmg1j4BzToIzvhm6cQ2vycuccG3sNPkhGPKpiZDD7NaAnzs/rM0UGKR5oB/v6
fX3NkfJHF1xWEXWOOap0u6z5RsPbfnPhVXKe5PDIiaTg6S7AQUtM6SOXj/Ws94Rv
3p8IzJqy7KlOq0eo2OFo6n8RIw+9zdod3+P9al/iDaOefrT+mjH3MeAcDx8W8f8t
DeRslKvfQhMxfW7Qwz57fr91oFMPhVSdJJ2fl8IMAzteR+5g1Yzwy8J9zvpagt9Y
Bug#944160: marked as done (Fix time.clock import for python3.8)
Your message dated Mon, 18 Nov 2019 08:41:30 + with message-id and subject line Bug#944160: fixed in python-pulp 1.6.0+dfsg1-5 has caused the Debian Bug report #944160, regarding Fix time.clock import for python3.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 944160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-pulp Version: 1.6.0+dfsg1-4 Severity: important Tags: sid bullseye patch User: debian-pyt...@lists.debian.org Usertags: python3.8 Fix time.clock import for python3.8 patch at http://launchpadlibrarian.net/449968380/python-pulp_1.6.0+dfsg1-4_1.6.0+dfsg1-4ubuntu1.diff.gz --- End Message --- --- Begin Message --- Source: python-pulp Source-Version: 1.6.0+dfsg1-5 We believe that the bug you reported is fixed in the latest version of python-pulp, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 944...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated python-pulp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Nov 2019 08:54:23 +0100 Source: python-pulp Architecture: source Version: 1.6.0+dfsg1-5 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Closes: 944160 Changes: python-pulp (1.6.0+dfsg1-5) unstable; urgency=medium . [ Ondřej Nový ] * Bump Standards-Version to 4.4.1. . [ Matthias Klose] * Fix time.clock import for python3.8 (Closes: #944160). Checksums-Sha1: 63f13474d999bd13df9476463532116d00a543b8 2160 python-pulp_1.6.0+dfsg1-5.dsc 383ca338f1d533c505bf280243115770c54110d3 12284 python-pulp_1.6.0+dfsg1-5.debian.tar.xz 4471c85586892c24c9199fb35a2bfc88da8ea191 6520 python-pulp_1.6.0+dfsg1-5_amd64.buildinfo Checksums-Sha256: bc609ddc829c815a8c95a8224905d98a3b1ab6b6da0819479c04bb58ef2e2428 2160 python-pulp_1.6.0+dfsg1-5.dsc 4ffc862c77b447d6ef9cede9590cf0323cfdb8bd0847ca1fb768a88b400688fc 12284 python-pulp_1.6.0+dfsg1-5.debian.tar.xz 0c45d9abe62c6f33d5e6fa94a9fdcb8a4a7f6810d3e4827dcb53a797e2c1884d 6520 python-pulp_1.6.0+dfsg1-5_amd64.buildinfo Files: a11f838f7bf347e88a672146ab668271 2160 python optional python-pulp_1.6.0+dfsg1-5.dsc bb4c5c6ecf15632c734284726bab58d9 12284 python optional python-pulp_1.6.0+dfsg1-5.debian.tar.xz 9e7fdb3706fd491b0a6b1ffa08f0608f 6520 python optional python-pulp_1.6.0+dfsg1-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl3STrMACgkQ1BatFaxr Q/79fQ//WZbByHLSuW18LcQsuZ6+OIpvQOKNrXw/yv9gJDzUraRyoQw5nZNnUSCQ xASJS8d3+B5x13kylM3MWssRAwnAbwh7+0wSsGapvppSW+oATJE8j/2LgrNDaRfG aQHTUBUIPF+i1FvwafOVf5IlqM7PvGCVPKdQomG2EFguRYmJ3uRJg9d6PpRTx+7k K4JuDGJ/EQF5k5ObU0nSel2Tz+nrABUHPIyyWdStxp01ZnbsjESY2fmaNETq1gBF vUPZNE4TWJu19MN85y69Rw2vlncW+qoQVRsIFPYQg1GGos6mRpiIU5fwGI/dw186 Qc/RJSgHDJSEdisrB5YJtVirvHkMbbsg0hVlTmKiZ2AkRXsacf98P9C1tlS4F0ID bWQyrf8Jcb16OBKEsPs9n8vH/xz54OufA6fJCPQtI1AaC9l44KgLD7QEHnIi6Xur rb+pP21P8WN48ovAkypw9WT9H9F6cbxGa4tel/3vC81WLm4Vho2uSvmZ26Ax+ABk ND08teCLZ8S7QaL8pAt2YWFh2ujY4weTUs8KfKuklWo5nYoKbhRjHbdEMjTxbb6J NnTlrQ1ViiPXMbVhQKvvlNBvRFdxHKmia3DssuKRuKJiqK041Ys8beh/bph0ARGt EFbukiXekC80BsT0JG9A7/ZB1UUZ7Ps6qNT6axBuTKRnaEGpVK8= =wh5r -END PGP SIGNATURE End Message ---
Bug#942235: Adding Python 3.8 as a supported Python3 version
On 18/11/2019 07:07, Matthias Klose wrote: On 18.11.19 07:52, Alastair McKinstry wrote: So I've uploaded a python-xarray 0.14.0-2 which passes on python3.7. Its failing on python 3.8 but apparently due to pandas not ready on 3.8, so it should be ok to pass as the transition completes. I think that error is just pandas *not being built* for 3.8 yet: a Python version transition is ~500 binNMUs and that takes time. xarray really needs dask >= 2.0 but version 1 is in unstable; I've disabled some functionality (dask='parallelize') and marked some tests xfail until this is done. Alastair yes, people are aware of a needed dask update, see #942235. There's now also a dask 2.8 release available, I didn't look at that yet. dask is itself failing autopkgtests, and this is blocking pandas and pytest, so is a problem independently of xarray. (The breakage was originally caused by pytest 4, but pandas 0.25 Build-Depends: on that.)
Bug#944705: Wrong patch for mako?
Hi Steve, Thanks for this, however, the patch you've provided for this bug is for Alembic, not for Mako. Do you have a patch available for Mako? Has a bug correctly been filled for Alembic? Cheers, Thomas Goirand (zigo)
Bug#944160: marked as pending in python-pulp
Control: tag -1 pending Hello, Bug #944160 in python-pulp reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/python-pulp/commit/b41ad4d380319ed967615f61c1fdf9aac8ff519d Fix time.clock import for python3.8 (Closes: #944160). (this message was generated automatically) -- Greetings https://bugs.debian.org/944160
Processed: Bug#944160 marked as pending in python-pulp
Processing control commands: > tag -1 pending Bug #944160 [src:python-pulp] Fix time.clock import for python3.8 Added tag(s) pending. -- 944160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
